diff --git a/.agents/skills/hardware-device-research/SKILL.md b/.agents/skills/hardware-device-research/SKILL.md
index 228b0db..a9f0830 100644
--- a/.agents/skills/hardware-device-research/SKILL.md
+++ b/.agents/skills/hardware-device-research/SKILL.md
@@ -7,41 +7,9 @@ description: Build or audit a source-traceable hardware knowledge base. Use when
 
 Research a hardware device recursively: document the complete product, identify its functional components, create a reusable record for each component or interface, preserve relevant artifacts, and verify the resulting knowledge base.
 
-> **Read this file once, end to end, before starting a research pass.** It is ~870 lines and the
-> parts interlock — the workflow assumes the evidence rules, the verification list assumes the
-> manifest format, and the failure modes explain why several steps exist. Skimming for the step
-> you think you need is how passes end up with unsourced claims and stranded artifacts.
->
-> After that first full read, use this table to jump back to what you need.
-
-## Contents
-
-| Section | Why it matters |
-|---|---|
-| [What makes this different](#what-makes-this-different-from-summarising-a-datasheet) | **Core.** Five habits that do most of the work |
-| [Where research is written](#where-research-is-written) | **Core.** Repo layout, the two sibling directories, path resolution |
-| [Required Inputs](#required-inputs) | What to establish before starting |
-| **[Workflow](#workflow)** — 18 steps | **Core.** The pass itself, in order |
-| [1. Inspect the repository](#1-inspect-the-repository) · [2. Identify the device](#2-identify-the-exact-device) · [3. Source-priority research](#3-research-in-source-priority-order) | orientation and evidence ranking |
-| [4. Gather artifacts](#4-gather-device-artifacts) | **Core.** Acquisition, validation, archiving, placeholders |
-|   ↳ [Mine before archiving](#mine-the-artifact-before-it-leaves--write-the-findings-up-as-their-own-document) | **Core.** When to archive, what to extract, writing custom docs |
-| [5. Visual/product/market dossier](#5-build-the-visual-product-community-and-market-dossier) · [6. Inventory hardware](#6-inventory-the-complete-hardware) · [7. Recurse into components](#7-research-every-component-recursively) | breadth |
-| [8. Pinouts and architecture](#8-document-pinouts-and-architecture) · [9. Development and recovery](#9-document-development-and-recovery) · [10. Audit vendor source](#10-audit-vendor-firmware-and-driver-source-against-the-primary-documents) | the technically load-bearing steps |
-| [11. Examples](#11-survey-and-select-examples) · [12. Feature guides](#12-write-feature-oriented-development-guides) · [13. Common guides](#13-reuse-common-development-knowledge) · [14. Vendor sourcing](#14-record-vendor-documentation-sourcing-knowledge) | reusable output |
-| [15. Coverage/conflicts](#15-map-coverage-resources-and-compatibility) · [16. Performance](#16-characterize-performance-by-workload) | mapping and measurement |
-| [17. Licensing as metadata](#17-record-licensing-as-metadata) · [18. Vendored deps and large artifacts](#18-analyze-vendored-dependencies-near-duplicates-and-large-artifacts) | **Core.** What may be kept, moved or omitted |
-| [Required Device README Content](#required-device-readme-content) | The output template |
-| [Artifact and Acquisition Manifests](#artifact-and-acquisition-manifests) | **Core.** Provenance schema and the downloader contract |
-| [Research stopping criteria](#research-stopping-criteria) | When a pass is done |
-| [Conflict Protocol](#conflict-protocol) | **Core.** What to do when sources disagree |
-| [Evidence discipline and known failure modes](#evidence-discipline-and-known-failure-modes) | **Core.** The mistakes this skill exists to prevent |
-| [Working alongside other sessions](#working-alongside-other-sessions) | concurrency |
-| [Verification](#verification) | **Core.** The checklist a pass must survive |
-| [Completion Standard](#completion-standard) | What "done" means |
-
 ## What makes this different from summarising a datasheet
 
-Six habits do most of the work. If you internalise nothing else, internalise these.
+Five habits do most of the work. If you internalise nothing else, internalise these.
 
 **Prefer primary evidence, and say which kind you used.** Vendor prose is the weakest source in the stack and is frequently wrong. Published EDA files, parsed firmware images and vendor board-support headers are authoritative and usually available. Label every consequential claim: `executed-success` · `reported-working` · `inferred` · `not-tested`, and never present an untested command as though it were verified.
 
@@ -51,8 +19,6 @@ Six habits do most of the work. If you internalise nothing else, internalise the
 
 **Preserve failures and negative results.** A URL that 404s, an HTML error page saved with a `.pdf` extension, a search that returned nothing, a translation that added nothing — each saves the next agent from repeating the work. They belong in the record.
 
-**Mine the artifact, then write it up.** The download is raw material; the Markdown is the deliverable. Extract what matters *before* a file is archived, and give a real finding its own document rather than burying it in a template section. See [Mine the artifact before it leaves](#mine-the-artifact-before-it-leaves--write-the-findings-up-as-their-own-document).
-
 **Nothing useful may exist in only one place.** Every artifact is either in the repository, or archived with a placeholder carrying its hash and reacquisition instructions. Scratch is not storage.
 
 ## Where research is written
@@ -76,62 +42,23 @@ Use lowercase, filesystem-safe slugs and exact manufacturer and part numbers. Pu
 
 This taxonomy is open: add a category when material genuinely fits none of the four, and say in the index why it exists.
 
-### The two sibling directories, and how to write paths
+### The two sibling directories
 
 ```
 <repo-parent>/
-├── hardware-doc/     ← this repository
-└── repo-archive/     ← bulk artifacts moved out of it (own repo, usually unpublished)
-    ├── hardware-doc/          artifacts, mirroring this repo's own paths
-    └── scratch/hardware-doc/  working files
+├── hardware-doc/            ← this repository
+└── hardware-doc-archive/    ← bulk artifacts moved out of it (separate repo, usually unpublished)
 ```
 
-**In records, always write `archive/…` and `scratch/…`.** Those are tracked symlinks at the
-root of this repository pointing at its own slice of the archive:
-
-| Write this | Resolves to |
-|---|---|
-| `archive/devices/<vendor>/<board>/artifacts/x.step` | `../repo-archive/hardware-doc/devices/…` |
-| `scratch/<subject>/…` | `../repo-archive/scratch/hardware-doc/<subject>/…` |
-
-The path after `archive/` is **the same path the artifact had in this repository** — nothing to
-recompute, and the archive can be renamed or moved by changing two symlinks instead of every
-record. Paths are relative to the repository root, so run restore commands from there.
-
-Do **not** write `../repo-archive/…` into a record, and do not write an absolute path. The
-sibling form appears in this skill only because it is explaining the layout.
-
-In a script, resolve the root rather than assuming a location:
+Write `../hardware-doc-archive` — **relative to the repository root**, never `~/…`. The home-directory form is correct only when the repo happens to sit at `~/hardware-doc`, and is wrong under worktrees. Resolve it properly with the git *common* directory:
 
 ```bash
-ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/repo-archive"
+ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
 ```
 
-`--git-common-dir` rather than `--show-toplevel`: inside a linked worktree the toplevel is the
-worktree, whose parent is the wrong directory.
+`--git-common-dir` rather than `--show-toplevel`: inside a linked worktree the toplevel is the worktree, whose parent is the wrong directory; the common dir always points at the main repository's `.git`.
 
-#### Working from a consuming repository
-
-When this repo is symlinked into another as `doc/hardware`, **you can navigate the whole
-structure from that repo directly** — the consumer carries its own shortcuts, and they resolve
-to exactly the same bytes:
-
-| From the consuming repo | Resolves to | Same as, from here |
-|---|---|---|
-| `doc/hardware/…` | the repository root | `./…` |
-| `archive/…` *or* `doc/archive/…` | `repo-archive/hardware-doc/…` | `archive/…` |
-| `scratch/…` *or* `doc/scratch/…` | `repo-archive/scratch/hardware-doc/…` | `scratch/…` |
-
-So an agent working out of the consumer can read, write, download into and archive from those
-paths without resolving anything by hand — `archive/devices/foo/bar.step` reaches the same
-file from either side. Use whichever root you are already standing in.
-
-Two things still hold regardless of where you are working:
-
-- **Records are written here**, in `hardware-doc`, and committed here — not in the consumer.
-- **Inside a record, write the path as this repository sees it**: `archive/…`, `scratch/…`,
-  and repo-relative links. A consumer-relative path such as `doc/hardware/devices/…` is
-  correct from over there and broken from here, and this repo is also read standalone.
+> **When invoked from a consuming repository** (this repo symlinked in as `doc/hardware`), resolve the symlink and work at the real root. Records are written here, not in the consumer.
 
 ## Required Inputs
 
@@ -153,7 +80,7 @@ Do not confuse enclosure colors, battery bundles, language suffixes, or sales bu
 - Check documentation conventions, symlinks, ignore rules, existing device/component records, and unrelated working-tree changes.
 - Preserve unrelated changes.
 - Do not commit unless explicitly requested.
-- Stage the research, manifests, tooling and artifacts as you go. Very large additions are worth mentioning in your summary so the user knows what landed, but they do not need pre-approval.
+- Staging is allowed as part of organizing the research, but keep large or licensing-uncertain artifacts unstaged until the user reviews the categorized artifact report. Prefer staging authored research, manifests, acquisition tooling, and artifacts with clear terms.
 - Add or update umbrella, device, and component indexes.
 
 ### 2. Identify the exact device
@@ -273,7 +200,7 @@ A worked example of the full chain, using strikethrough to show the file is no l
 
 ```markdown
 | ~~esp-dev-kits-en-master-esp32p4.pdf~~ **archived 2026-08-24** | 30 482 003 |
-  `04d75d2a…` | Offline user guides — archive record (`devices/espressif/shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md`) |
+  `04d75d2a…` | Offline user guides — [archive record](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) |
 ```
 
 Where several devices share one component, the placeholder is written **once** in the component directory and cited by **every** device that uses it. Do not copy the artifact per device.
@@ -307,21 +234,16 @@ For repository content, a branch name is not identity — branches move. Cite th
 The archive has exactly **two** states. Keep it that way — a third invites stranding.
 
 ```
-<archive-root>/                        ../repo-archive
-  <source-repo>/<repo-relative-path>   # DECIDED: mirrors the repo, placeholder left behind
-  scratch/<source-repo>/<subject>/     # UNDECIDED: raw fetches, intermediates, working files
+<archive-root>/
+  doc/<repo-relative-path>     # DECIDED: mirrors the repository, placeholder in repo
+  scratch/<subject-slug>/      # UNDECIDED: raw fetches, intermediates, working files
 ```
 
-Both tiers are **namespaced by source repository**, so material archived out of a second repo
-sits beside this one rather than colliding. From inside the repository they are reachable as the
-tracked symlinks **`archive/`** and **`scratch/`**, which already point at this repo's own slice —
-so `archive/devices/foo/…` is the same path the artifact had here.
-
-**The moment a file's home is known, move it to `archive/` at its repo-relative path** and write the placeholder. Mirroring the repository's own path inside the archive means the mapping needs no lookup table and survives reorganisation. Do not add a staging tier inside `scratch/` that mirrors repo paths — it would only give work somewhere to stall. *(Measured on an ~11,000-file archive: every file with a decided path was already under the repo namespace; none of the ~5,800 scratch files had one.)*
+**The moment a file's home is known, move it to `doc/` at its repo-relative path** and write the placeholder. Mirroring the repository's own path inside the archive means the mapping needs no lookup table and survives reorganisation. Do not add a staging tier inside `scratch/` that mirrors repo paths — it would only give work somewhere to stall. *(Measured on an ~11,000-file archive: every file with a decided path was already in `doc/`; none of the ~5,800 scratch files had one.)*
 
 **Download into `scratch/` directly; do not stage in `/tmp` and copy later.** The files must reach the archive regardless, so `/tmp` adds a mandatory step that can fail. `/tmp` is also not dependable — it is cleared between sessions on many hosts, and has been observed losing an agent's files mid-task. Use it only for work you will discard: peeking inside an archive, probing a URL, checking magic bytes. If you do put something there you may want, `mv` it immediately — on a shared filesystem that is a rename, not a copy. *(In one session a 230-file wiki corpus, FCC exhibits and vendor headers vanished from `/tmp` mid-task. On that host `/tmp` was a bind mount of the same filesystem as `$HOME`, so it was neither faster nor cheaper than writing straight to the archive.)*
 
-**Inside `scratch/<subject>/`, organise however the subject needs.** No layout is prescribed. Reusable material needs no special place: a chip datasheet is a *component* artifact, so once recognised it belongs in `components/…`, which is where a parallel agent will look for it.
+**Inside `scratch/<subject-slug>/`, organise however the subject needs.** No layout is prescribed. Reusable material needs no special place: a chip datasheet is a *component* artifact, so once recognised it belongs in `components/…`, which is where a parallel agent will look for it.
 
 **Namespace by subject, never by agent** — agents are concurrent and ephemeral; the subject outlives them. **List the parent before creating any directory**; a convention probably exists. *(Three agents in one session independently created `workspace/`, `tmp-workspace/` and `_tmp-sweep-*/` for the same job — 363 MB of duplication, reconciled by hand.)*
 
@@ -329,7 +251,7 @@ so `archive/devices/foo/…` is the same path the artifact had here.
 
 **Do not tidy other agents' scratch.** It is working space; its mess is not a defect.
 
-When a fetched file resembles one you already hold — same name, same version, a vendored copy of a known library, or the same document in another language — see [step 17](#18-analyze-vendored-dependencies-near-duplicates-and-large-artifacts) before discarding either.
+When a fetched file resembles one you already hold — same name, same version, a vendored copy of a known library, or the same document in another language — see [step 17](#17-analyze-vendored-dependencies-near-duplicates-and-large-artifacts) before discarding either.
 
 #### What to collect, and where it lands
 
@@ -389,80 +311,15 @@ devices/<manufacturer>/<product>/
 
 Err toward downloading, validating, inspecting, and preserving potentially useful artifacts rather than omitting them because their size or license is initially unclear. Vendor useful artifacts by default unless they are excessively large for the repository after measured analysis or explicit terms very clearly forbid repository redistribution. Retain original archives and extract useful contents for direct access. Preserve upstream directory structure, licenses, copyright notices, and filenames unless a filename is unsafe or nonportable. Record any rename.
 
-Extract useful facts from downloaded material into authored research documents so future development does not depend on reopening the artifact — see [Mine the artifact before it leaves](#mine-the-artifact-before-it-leaves--write-the-findings-up-as-their-own-document). This includes pin mappings, register details, build settings, toolchain versions, firmware metadata, example structure, dependency versions, revision identifiers, and recovery procedures.
+Extract useful facts from downloaded material into authored research documents so future development does not depend on reopening the artifact. This includes pin mappings, register details, build settings, toolchain versions, firmware metadata, example structure, dependency versions, revision identifiers, and recovery procedures.
 
 Record the retrieval date and all available immutable identity information: document version/revision, release/tag, repository commit hash, archive checksum, file build identifier, and upstream publication/update date.
 
-At completion, no useful or uniquely acquired information may exist only in `/tmp`. Promote the artifact into the repository tree, move it to an ignored persistent cache under the knowledge-base root, or create complete reacquisition metadata and derived documentation before removing temporary files.
-
-#### Mine the artifact before it leaves — write the findings up as their own document
-
-**The artifact is raw material. The write-up is the deliverable.** A 50 MB PDF sitting in the
-tree that nobody has read is not research; it is a download. Before an artifact is archived —
-and ideally as soon as it is acquired — pull what matters out of it and write that up in
-Markdown, in your own words, organised for the reader rather than mirroring the source.
-
-**Archive only after the extraction exists.** Once a file moves to `../repo-archive` most
-readers will never open it: they have a placeholder and, if they are lucky, a URL. Whatever
-you did not extract is effectively lost to them.
-
-##### When to archive
-
-Move an artifact out when **all** of these hold:
-
-- Its content has been mined into repository Markdown, or it demonstrably carries nothing
-  worth mining (a 3D mesh, a panelised gerber, a generated doc build)
-- It is **derived, bulky, or off-topic** — regenerable output, a duplicate, examples for a
-  different board, prebuilt images that are also published upstream
-- A placeholder can carry enough provenance to reacquire it
-
-Keep it in the repository when it is **primary and irreplaceable**: schematics, netlist
-sources, BOMs, firmware images that are not byte-reproducible, and datasheets whose source
-URLs are already dead or likely to rot. Size alone is not a reason to archive; *derivedness*
-is.
-
-[`SIZE-AUDIT.md`](../../../SIZE-AUDIT.md) works this through on the real tree — which
-categories proved reproducible, which are irreplaceable, and how much each costs. Read it
-before a large archiving pass; it will usually tell you the answer without re-deriving it.
-
-##### What extraction looks like
-
-Not a summary of the document — the **facts a future reader needs**, restructured:
-
-| Source artifact | What to write |
-|---|---|
-| Schematic / PCB (KiCad, EAGLE) | Parsed netlist as pin tables, connector pinouts, BOM with roles, and the **conflicts and shared pins** that a table alone hides |
-| Firmware image | Parsed headers, build metadata, partition map, embedded strings, and what the device therefore *does* on power-up |
-| Datasheet | The handful of numbers this board actually depends on, plus errata and the traps — not a spec dump |
-| Compliance / regulatory PDFs | SKUs, barcodes, tariff codes, certification dates, and the constraints they imply |
-| Vendor doc corpus (wiki, `.rst`, HTML) | The API/behaviour that is load-bearing, and the places the vendor contradicts itself |
-| Campaign updates, blogs, forum threads | **Design rationale** — why the hardware is the way it is. Usually the only place this exists |
-
-##### Write custom documents, not just the template
-
-The required README sections are a floor, not a ceiling. **When a subject has a story, give it
-its own file** and link it from the README's task index. Documents that earned their place in
-past passes:
-
-- `development-history.md` — why the design changed, drawn from campaign updates
-- `inter-board-wiring.md` — connector pinouts recovered from PCB files
-- `keymap-format.md` — a file format nobody had documented
-- `regulatory-and-skus.md` — extracted from compliance PDFs
-- `peripheral-mode.md` — a protocol the vendor documents in an obsolete form
-- `arduino-api.md` — the ~5 % of a 4,500-line API reference that is actually load-bearing
-
-Name them for what a reader would search for. A finding buried in a section of a long README
-is a finding nobody will locate.
-
-##### The test
-
-For every artifact you archive, ask: **if the archive were deleted tomorrow, what would the
-repository still know?** If the answer is "only that a file used to exist", the extraction was
-not done.
+At completion, no useful or uniquely acquired information may exist only in `/tmp`. Promote the artifact into the repository tree, move it to an ignored persistent cache under ``, or create complete reacquisition metadata and derived documentation before removing temporary files.
 
 #### Placeholders must stand alone
 
-When an artifact is moved out of the repository, the placeholder left in its place is the **only** thing most readers will ever see. The archive is machine-local: someone cloning the repository has no `../repo-archive/` and never will. A placeholder that merely says "moved to the archive" is useless to them.
+When an artifact is moved out of the repository, the placeholder left in its place is the **only** thing most readers will ever see. The archive is machine-local: someone cloning the repository has no `~/…-archive/` and never will. A placeholder that merely says "moved to the archive" is useless to them.
 
 **A placeholder must be sufficient to reacquire the file without the archive.** It is the same provenance the [acquisition manifest](#artifact-and-acquisition-manifests) already records for every artifact — SHA-256, byte size, canonical URL, retrieval date, upstream version/date, and commit hash or release tag where applicable — written for a human instead of a parser. Keep the two consistent; if they disagree, the manifest is authoritative and the placeholder is stale.
 
@@ -475,29 +332,11 @@ Beyond those shared fields, a placeholder also states:
 
 Record failed or blocked reacquisition honestly (`automatic`, `manual`, `blocked`, `lost`) rather than omitting the instructions.
 
-**A placeholder is the minimum, not the limit.** Every archived artifact needs one. Beyond
-that, add whatever helps a reader:
-
-- **Extraction documents** — the write-up mined from the artifact before it left
-  ([see above](#mine-the-artifact-before-it-leaves--write-the-findings-up-as-their-own-document)).
-  These are the real reason the archive can be absent without loss.
-- **Several placeholders for one move** — a per-file note plus a directory-level `ARCHIVED-*.md`
-  summarising the set is often clearer than either alone.
-- **Cross-references** from the records that care. A pinout page should link the schematic
-  placeholder; a firmware page should link the image it parsed.
-- **Symlinks into the archive**, where a stable in-repo path is genuinely useful. `archive/`
-  and `scratch/` already exist for this; a deeper convenience link is fine as long as it is
-  relative and the placeholder still stands alone without it. Remember a symlink into an
-  absent archive dangles — it is a convenience, never the record.
-
-What must not happen is the reverse: an artifact moved out with *only* a path in a manifest,
-or a placeholder that assumes the reader holds the archive.
-
 **The archive path is a convenience, not the contract.** It should be kept accurate — if you reorganise the archive, grep the repository and repair the references in the same change, exactly as you would a breaking rename — but a reader without the archive must still be able to recover the file from the placeholder alone. Verification therefore tests the placeholder's completeness, not whether the path resolves on this machine.
 
 **Placeholder conventions vary** (`*.ARCHIVED.md`, `*.REMOVED.md`, `*.DUPLICATE.md`, `ARCHIVED-*.md`, directory `README.md`). When auditing coverage, walk **all ancestor directories** — a directory-level placeholder shadows everything beneath it, and checking only a file's immediate parent reports large numbers of false gaps.
 
-**Use one archive root.** Do not create a near-identical sibling (`repo-archive` vs `repo-archive`); check for existing roots before creating one, and prefer a symlink over a second directory.
+**Use one archive root.** Do not create a near-identical sibling (`hardware-doc-archive` vs `hardware-docs-archive`); check for existing roots before creating one, and prefer a symlink over a second directory.
 
 Never save an error page or HTML response with a `.pdf`, `.zip`, or firmware extension. Validate file type from content, not just URL or suffix.
 
@@ -507,7 +346,7 @@ Create custom prose and structured evidence describing the device as a physical
 
 #### Visual identification
 
-Find useful front, back, side, port/label, enclosure-open, teardown-stage, PCB front/back, revision-marking, component close-up and representative-use images. Retain and embed useful images when practical. Every image must record creator/rightsholder when known, source page and direct URL, publication/retrieval dates, applicable device/revision, license/permission evidence, redistribution status, modifications, local path, caption and alt text. Captions explain what the image demonstrates and any crop, annotation, rotation or processing. Do not remove watermarks or present an image-search result as provenance.
+Find useful front, back, side, port/label, enclosure-open, teardown-stage, PCB front/back, revision-marking, component close-up and representative-use images. Retain and embed useful images when practical; if rights are unclear, they may remain unstaged pending user review. Every image must record creator/rightsholder when known, source page and direct URL, publication/retrieval dates, applicable device/revision, license/permission evidence, redistribution status, modifications, local path, caption and alt text. Captions explain what the image demonstrates and any crop, annotation, rotation or processing. Do not remove watermarks or present an image-search result as provenance.
 
 #### Identity, history, family and culture
 
@@ -738,39 +577,35 @@ For network/VPN/container results include interfaces/link rates, peers, protocol
 
 Explain what results mean for real workloads and cumulative feature combinations. Distinguish official claims, silicon limits, independent measurements, isolated owner reports, locally reproduced results and estimates. If evidence cannot support a comparison, mark it unresolved rather than inventing precision.
 
-### 17. Record licensing as metadata
-
-**Gather the artifact first.** Licensing is a field on the record, not a gate on acquisition.
-A datasheet you did not download is a gap in the research; a datasheet with an unrecorded
-licence is a record you can complete later in five seconds.
-
-Download it, keep it, and note what the terms appear to be. That is the whole of it.
+### 17. Handle licensing and storage honestly
 
-**Note, per artifact:**
+- Public availability does not imply redistribution permission, and a user request cannot grant third-party redistribution rights.
+- Identify applicable terms from authoritative license text, download terms, publisher policy, and license/notice files found inside downloaded artifacts. Record the exact license expression/name, evidence URL or retained license path, scope, and obligations. Do not infer that one license covers unrelated neighboring files.
+- Preserve license files, copyright notices, source offers, and required attribution.
+- Treat an archive as mixed-license when its members have different or incomplete terms. A bundled dependency's license does not cover the surrounding archive.
+- Distinguish official source, bundled dependencies, opaque binaries, proprietary tools, and community code.
+- Avoid treating installers or unrelated toolchains as normal repository content, but download them to temporary inspection space when they are relevant to understanding versions, bundled files, recovery procedures, or license terms.
+- Record intentional duplication caused by retaining archives beside extracted contents.
+- Repository size policy and Git LFS do not replace a licensing decision.
 
-- The licence expression or name if one is stated (`MIT`, `TAPR OHL v1.0`, `LGPL-3.0`, …)
-- Where you saw it — a `LICENSE` file, a page footer, a notice inside the PDF
-- `restricted` if the document itself carries wording limiting redistribution, `unknown` if
-  nothing was stated
+Record two independent fields for every artifact:
 
-**Redistribution status** — a descriptive label, not a verdict:
+**Redistribution status** describes known legal permission, not where the file is stored:
 
-- `allowed` — an explicit permissive licence
-- `conditional` — permissive with obligations worth preserving (attribution, notices, source offer)
-- `restricted` — the document states a limitation
-- `unknown` — nothing stated. **This is the common case and is entirely fine.**
+- `allowed`: explicit evidence permits repository redistribution with no unmet artifact-specific obligation.
+- `conditional`: redistribution is permitted only after recorded obligations are satisfied, such as preserving notices, attribution, source availability, or no-modification requirements.
+- `prohibited`: applicable terms prohibit the intended repository redistribution.
+- `unknown`: applicable terms were not found, conflict, or have unclear scope.
 
-**Disposition** — where the bytes live:
+**Disposition** describes the current or proposed storage behavior and may change after user review:
 
-- `repository` — in the tree
-- `archive` — moved to `../repo-archive` with a placeholder, usually for size
-- `reference-only` — metadata and URL kept because the file could not be obtained
+- `repository`: retained in the repository tree; separately record whether it is `unstaged`, `staged`, or already tracked.
+- `local-cache`: downloaded under an ignored, untracked path for local use and reproducible through the acquisition manifest.
+- `reference-only`: normally retain metadata and a URL rather than the artifact in the repository; it may still be downloaded temporarily or into a local inspection cache to validate content, hashes, metadata, and embedded license terms.
 
-Keep vendored `LICENSE` files, copyright headers and notices when they come bundled — they
-are part of the artifact and cost nothing.
+Treat these fields as research findings and planning aids, not automatic legal judgments. Absence of a discovered license is not a reason to skip acquisition or prevent the artifact from being placed in the repository tree. Unless explicit terms prominently forbid copying or sharing, a useful datasheet, PDF, archive, image, binary, or source tree may be downloaded into the repository but should remain unstaged when its terms are strict or unclear. Explain the evidence, uncertainty, obligations, size, and practical options, then ask the user whether to stage it, move it to local cache, compress it, or keep only acquisition metadata. Record the user's decision.
 
-**What not to do:** do not delete artifacts over licensing, do not stall a pass waiting for a
-ruling, and do not turn a research record into a legal analysis. Note it and move on.
+When the choice materially affects clone size, offline use, access requirements, or uncertain/strict terms, present the user with a grouped list containing license evidence, uncertainty or obligations, original and compressed size where useful, development value, recommendation, and all practical alternatives. Ask what to stage or retain. Categorize at least: clear/common licenses; strict/conditional terms; unknown terms; unusually large files/directories; opaque binaries; vendored source/dependencies; and explicit copying/sharing restrictions. Do not repeatedly ask about routine small artifacts covered by an explicit repository policy.
 
 ### 18. Analyze vendored dependencies, near-duplicates and large artifacts
 
@@ -830,7 +665,7 @@ Maintain:
 1. An auditable artifact manifest covering files intended for the repository.
 2. A committed machine-readable acquisition manifest covering every useful artifact not tracked in Git, including ignored repository files, local-cache files, reference-only records, temporarily inspected files, inaccessible artifacts and failed acquisitions.
 3. A committed downloader driven only by the acquisition manifest.
-4. A short licence summary in the manifest: what each artifact's terms appear to be, grouped so obligations worth preserving (attribution, notices) are visible at a glance.
+4. A concise license-and-decisions report grouping known permissive licenses, conditional/strict licenses and obligations, prohibited terms, and unknown terms requiring user input.
 5. Reproduction instructions for large omitted/ignored vendored trees and binaries.
 
 Each source-artifact record must include:
@@ -962,7 +797,7 @@ Before completion:
 17. Spot-check claim-to-source coverage for identity, specifications, pinouts, fitted parts and firmware/recovery claims.
 18. Confirm every `local-cache` path is ignored and absent from Git's index.
 19. Validate the acquisition-manifest schema and run the downloader in verify-only mode.
-20. Confirm each artifact carries a licence field, even if the value is `unknown`.
+20. Confirm license reporting separately lists known licenses, conditional/strict obligations, prohibited terms, and unknown terms requiring user decisions.
 21. Verify vendored dependency identity, version/tag/commit/date, modification status, and reconstruction instructions where applicable. Where a vendored tree differs from upstream, confirm the **delta is retained as a patch**, its hunks are characterised (local modification versus merely stale upstream), and **the pinned upstream revision the patch applies to is retained** so the patch stays reproducible.
 22. Measure major directory/file contributors and test useful compression options for large binaries or archives.
 23. Confirm the user-facing decision report lists all unstaged uncertain/strict artifacts, unusually large paths, binaries, and explicit restrictions with recommendations.
@@ -1000,7 +835,7 @@ Before completion:
 50. Confirm useful comparative/performance datasets have reproducible charts where visualization adds value, with sourced data, units, configurations, dates, uncertainty and generation scripts.
 51. Confirm multi-language material follows policy: English retained in the repository where size allows, other languages archived with a placeholder, and an explicit statement of whether translations are substantively equivalent — or, where no English version exists, that the non-English document is the primary source.
 
-Store a concise verification report at the knowledge-base root and link it from the umbrella README.
+Store a concise verification report under `` and link it from the umbrella README.
 
 ## Completion Standard
 
diff --git a/.agents/skills/web-retrieval-fallback/SKILL.md b/.agents/skills/web-retrieval-fallback/SKILL.md
index d279649..24d6543 100644
--- a/.agents/skills/web-retrieval-fallback/SKILL.md
+++ b/.agents/skills/web-retrieval-fallback/SKILL.md
@@ -16,9 +16,6 @@ Read both before retrying if you haven't already in this session — prior findi
 
 ## Ladder
 
-0. **On GitHub, authenticate first** — `-H "Authorization: Bearer $(gh auth token)"`, or use
-   `gh api`. The API limit is per-identity, so UA rotation cannot help. See
-   [below](#github-authenticate-before-rotating-user-agents).
 1. **Default request** with normal headers.
 2. On 403, 429, bot-challenge page, or obvious filtering: retry with a modern browser UA:
    `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36`
@@ -29,52 +26,11 @@ Read both before retrying if you haven't already in this session — prior findi
 4. Check the doc's *Sites* section for the domain you are hitting — there may be a known working path, mirror, archive link, or rate-limit note.
 5. If content still won't come via direct fetch: try mirrors (`web.archive.org`, GitHub mirrors/repos), alternate endpoints (`.json` APIs, `old.reddit.com/.json` style variants), or clone-and-search locally.
 
-## GitHub: authenticate before rotating user agents
-
-For anything on `api.github.com`, UA rotation is the wrong tool — the limit is **per-identity,
-not per-agent**, so no header will help. Authenticate instead:
-
-```bash
-TOKEN="$(gh auth token)"
-curl -fsSL -H "Authorization: Bearer $TOKEN" https://api.github.com/...
-```
-
-| | Unauthenticated | With `gh auth token` |
-|---|---|---|
-| `api.github.com` core | **60 / hour** | **5 000 / hour** |
-| Search API | 10 / min | 30 / min |
-
-Measured, not quoted from docs — check yours with:
-
-```bash
-curl -s -H "Authorization: Bearer $(gh auth token)" https://api.github.com/rate_limit
-```
-
-Notes:
-
-- 60/hour is easy to exhaust: one recursive tree listing of a large repo can do it in a single
-  call, and you will then see 403s with `X-RateLimit-Remaining: 0` that look like bot-blocking
-  but are not. **Check the header before reaching for a UA.**
-- `raw.githubusercontent.com` is not the API and is far more permissive, so prefer it for
-  fetching file contents. The same `Authorization` header works there and is required for
-  private repos.
-- `gh api` handles auth and pagination itself — `gh api repos/OWNER/REPO/git/trees/BRANCH?recursive=1`
-  is usually better than hand-rolling `curl`.
-- If `gh auth token` is empty, the user is not logged in. Say so rather than silently falling
-  back to unauthenticated requests and blaming rate limits later.
-- Never print the token, echo it into a file, or paste it into a commit. Reference it as
-  `$(gh auth token)` at the point of use.
-
-The same principle generalises: where a host offers authentication the user already has, use
-it before pretending to be a different client.
-
 ## Rules
 
 - Do not use altered User-Agent headers when testing/debugging actual HTTP behaviour of an app, API, auth flow, or client — it hides genuine access-control problems.
 - A success via alternate UA is not evidence the resource works normally for ordinary clients.
 - Never use UA substitution to bypass authentication, account permissions, or explicit access controls.
-- Prefer real credentials the user already holds (`gh auth token`) over UA substitution. It is
-  not a workaround — it is the supported path, and it raises the GitHub limit 83x.
 
 ## Document findings
 
diff --git a/.gitignore b/.gitignore
index c2dc08f..c9dcd12 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,13 +1,5 @@
-# Bulk artifacts live in the sibling ../repo-archive - its own git repository,
-# but normally unpublished/private because of its size. Each artifact moved there leaves
-# a *.ARCHIVED.md placeholder here carrying size, SHA-256 and recovery URLs.
-#
-# `archive` is a tracked symlink to it (relative: ../repo-archive), so the
-# archive is reachable as ./archive/... when present. This entry stops the archive's
-# CONTENTS being committed here if the link is ever replaced by a real directory; it
-# does not (and cannot) affect the tracked symlink itself - .gitignore never applies to
-# tracked paths. See AGENTS.md "Symlinks and --skip-worktree".
-archive/*
+# Bulk artifacts live in the sibling ../hardware-doc-archive (not a git repo).
+# Each one leaves a *.ARCHIVED.md placeholder here with hashes and recovery URLs.
 
 __pycache__/
 *.pyc
diff --git a/AGENTS.md b/AGENTS.md
index 85fbc92..6204a5e 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -7,9 +7,9 @@ consumes it, and symlinked into place from there.
 ```
 <repo-parent>/
 ├── code/                     ← consuming repo (config, infra, …)
-│   └── doc/hardware  ──────────┐   symlink
+│   └── the repository root  ──────┐   symlink
 ├── hardware-doc/     ←─────┘   THIS REPO
-└── repo-archive/       bulk artifacts moved out of this repo (separate repo, usually unpublished)
+└── hardware-doc-archive/       bulk artifacts moved out of this repo (separate repo, usually unpublished)
 ```
 
 ## Paths — always resolve, never hardcode
@@ -20,7 +20,7 @@ root**, not the working directory and not `~`.
 | What | Location |
 |---|---|
 | This repo | `<repo-parent>/hardware-doc` |
-| Bulk artifact archive | `<repo-parent>/repo-archive` |
+| Bulk artifact archive | `<repo-parent>/hardware-doc-archive` |
 
 The archive is **its own git repository**, typically **unpublished/private** because of its
 size (multiple GB). It is not a submodule of this repo and is not required — every archived
@@ -31,95 +31,26 @@ artifact leaves a placeholder here carrying hashes and recovery URLs.
 ```bash
 ROOT="$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")"
 PARENT="$(dirname "$ROOT")"
-ARCHIVE="$PARENT/repo-archive"
+ARCHIVE="$PARENT/hardware-doc-archive"
 ```
 
 `--git-common-dir` matters: inside a linked worktree, `--git-dir` points at
 `.git/worktrees/<name>` while `--git-common-dir` still points at the main `.git`. Using
 `--show-toplevel` would give you the *worktree* root, which is the wrong parent.
 
-Historically the archive was referred to as `../repo-archive`. That happens to be
+Historically the archive was referred to as `../hardware-doc-archive`. That happens to be
 correct when the repo lives at `~/hardware-doc`, but it is wrong under worktrees and on
-any machine with a different layout. **Write `../repo-archive` relative to the
+any machine with a different layout. **Write `../hardware-doc-archive` relative to the
 repo root, or resolve it with the command above.**
 
-## Symlinks and `--skip-worktree`
-
-Two symlinks are **tracked**, both committed in **relative** form:
-
-| Link | Committed target | Points at |
-|---|---|---|
-| `archive` (this repo) | `../repo-archive` | the bulk-artifact archive |
-| `doc/hardware` (consuming repo) | `../../hardware-doc` | this repo |
-
-Relative is right for the normal sibling layout and keeps every clone identical to
-`HEAD`. It breaks only where `../..` does not reach the target — most often a linked
-worktree parked outside the repo parent. There, `hardware-doc-init.sh` substitutes an
-**absolute** path derived from the git common dir.
-
-Substituting makes the worktree differ from `HEAD`, so the script then marks the path
-`--skip-worktree`.
-
-> **`.gitignore` cannot do this.** It applies only to *untracked* paths. A tracked file
-> keeps reporting modifications no matter what `.gitignore` says. `--skip-worktree` is the
-> only thing that suppresses it. The `archive/*` and `doc/hardware/*` ignore entries exist
-> to stop the link *contents* being committed if a link is replaced by a real directory.
-
-### Reference archived artifacts as `archive/…` and `scratch/…`
-
-Two tracked symlinks point into this repo's **own slice** of the shared archive:
-
-| Link | Target | Contains |
-|---|---|---|
-| `archive` | `../repo-archive/hardware-doc` | bulky artifacts moved out of here |
-| `scratch` | `../repo-archive/scratch/hardware-doc` | raw fetches, provenance snapshots, working files |
-
-So a placeholder reads:
-
-```
-| Archived to | `archive/devices/<vendor>/<board>/artifacts/…` |
-```
-
-— the path after `archive/` is **the same path it had in this repository**. No prefix to
-remember, nothing to recompute.
-
-The archive is namespaced by source repository:
-
-```
-repo-archive/
-├── hardware-doc/          ← what `archive` points at
-└── scratch/hardware-doc/  ← what `scratch` points at
-```
-
-A second repository's material would sit beside these rather than colliding. Paths are
-relative to the repository root, so run restore commands from there.
-
-The indirection is the point: **if the archive moves or is renamed, two symlinks change** and
-every reference keeps working.
-
-> Prose that explains the layout keeps the real sibling path (`../repo-archive`),
-> because it describes where the directory actually is. Only followable paths use the links.
-
-**Caveat.** While `--skip-worktree` is set, git refuses to update that path. If a committed
-link target ever legitimately changes upstream, a clone carrying the flag will **not** pick
-it up on pull, and merges or checkouts touching it can fail with `Entry ... not uptodate`.
-Clear it with:
-
-```bash
-git update-index --no-skip-worktree archive        # or doc/hardware in the consumer
-```
-
-The script prints that exact command whenever it sets the flag, and only sets it when the
-relative default genuinely does not work.
-
 ## What belongs where
 
 | Content | Goes in |
 |---|---|
 | Authored research — device records, component records, feature guides, vendor guides | **this repo** |
 | Small primary artifacts — schematics, datasheets, BOMs, firmware images, EDA sources | **this repo**, under `devices/**/artifacts/` or `components/**/artifacts/` |
-| Bulky derived output — 3D STEP models, panelisation files, generated doc builds, enclosure meshes, prebuilt binaries already published upstream | **`../repo-archive/`**, with a `*.ARCHIVED.md` placeholder left behind |
-| Scratch downloads, raw HTML fetches, working files | `../hardware-doc-scratch/` |
+| Bulky derived output — 3D STEP models, panelisation files, generated doc builds, enclosure meshes, prebuilt binaries already published upstream | **`../hardware-doc-archive/`**, with a `*.ARCHIVED.md` placeholder left behind |
+| Scratch downloads, raw HTML fetches, working files | `../hardware-doc-archive/scratch/` |
 
 Never delete an acquired artifact. Move it to the archive and leave a placeholder that
 records size, SHA-256, upstream commit/author/licence and **multiple recovery URLs**.
@@ -161,23 +92,6 @@ When retrieving public web content with `curl`, `wget`, Python HTTP clients, or
 9. **Preserve scarce sources.** If a URL was genuinely useful and hard to acquire — very few copies online, or hosted somewhere unlikely to persist — submit it to `https://web.archive.org/save/<url>` (works unauthenticated). This applies to the kind of thing that has no mirror: datasheets/whitepaper/manual PDFs, technical docs on fragile personal or CMS-hosted pages, demo/example projects that exist only to illustrate how some code works, hard-to-find header files or source snippets not in any repo or package manager, one-off benchmark posts. It does **not** apply to widely-mirrored content (Wikipedia, MDN, popular repos) or anything already covered elsewhere — you can't and shouldn't archive every page you visit. Anonymous saves are rate-limited to roughly a few per minute; don't hammer it.
    - **Rare case:** if you are confident the site is still up but you are blocked or rate-limited, and you already know from some other source that the URL is valuable (a citation, an API doc you need, source code relevant to the task), you may submit it unseen and record that it wasn't directly accessible but was submitted on `<date>` — e.g. in the relevant *Sites* subsection of `ai-crawler-site-access-table.md` — so a future agent can check `web.archive.org` for the capture. Only do this when there's a concrete reason the page matters, not speculatively.
 
-### GitHub: authenticate rather than rotate agents
-
-`api.github.com` limits **per identity**, so no User-Agent helps. Use the token the user
-already has — it takes the core limit from **60/hour to 5 000/hour**:
-
-```bash
-curl -fsSL -H "Authorization: Bearer $(gh auth token)" https://api.github.com/...
-gh api repos/OWNER/REPO/git/trees/BRANCH?recursive=1   # handles auth + pagination itself
-```
-
-This matters here specifically: several vendor "wikis" are really GitHub repos — Seeed's is
-`Seeed-Studio/wiki-documents` on branch `docusaurus-version` — and one recursive tree listing
-can exhaust 60 requests in a single call. The resulting 403s carry
-`X-RateLimit-Remaining: 0` and look exactly like bot-blocking; check that header before
-rotating agents. Prefer `raw.githubusercontent.com` for file contents; it is not the API and is
-far more permissive. Never print or commit the token.
-
 ## Size discipline
 
 This repo is large by nature — see [`SIZE-AUDIT.md`](SIZE-AUDIT.md). Before adding
@@ -195,236 +109,10 @@ Duplicate content is pooled into `shared-assets/` as relative symlinks by
 duplicate-detection script must skip symlinks** or it will double-count ~154 files and
 report phantom waste.
 
-## Pins, hashes and identifiers are append-only
-
-**Never overwrite or delete a commit SHA, content hash, URL, version or artifact
-identifier that is already recorded. Add the new one; mark the old deprecated.**
-
-This applies to `examples/catalog.json`, `artifact-manifest.md`, every
-`*.ARCHIVED.md` placeholder, `sources.md` tables, and any inline `@ <sha>`
-citation in prose.
-
-### Why
-
-A recorded pin is evidence for a claim made *at that ref*. If you replace
-`67ee512` with today's HEAD, every sentence in the tree that was written from
-`67ee512` silently becomes unsourced — and nothing flags it. The old ref usually
-still resolves on the host, and if the repo is later deleted, renamed or
-force-pushed, the superseded SHA is the only thing that lets a future reader find
-it in a fork or an archive.
-
-This was learned the expensive way: a 2026-09-11 enrichment pass overwrote three
-pins with current HEADs, breaking the link between three device-record findings
-and the code they were actually read from.
-
-### The rule, concretely
-
-| Situation | Do |
-|---|---|
-| Upstream moved | Add the new SHA to `commit`; push the old into `prior_refs[]` |
-| A claim was read at an older ref | Set `analysed_at_commit` and say so |
-| A URL 404s | Keep it, add `status: dead` and the date; add the replacement alongside |
-| A project is renamed | Keep the old `canonical_url` as a `prior_refs[]` entry |
-| A hash changes | **Stop.** A changed hash for the same name+version is itself a finding — record both |
-| An entry is incomplete | Keep it. Mark the unknown fields `null` with a `_note_*` explaining why |
-
-**Incomplete entries are never deleted for being incomplete.** An entry with three
-verified fields is strictly better than no entry, because it records that the
-thing exists.
-
-### Catalog schema for this
-
-```jsonc
-"commit":            "06e1e5ed…",   // current pin
-"commit_date":       "2026-09-20",
-"commit_subject":    "Merge pull request #1 …",
-"analysed_at_commit":"67ee512024de", // what our prose was actually read from
-"analysed_at_note":  "⚠ documentation claims were read at this earlier ref …",
-"prior_refs": [
-  { "commit": "67ee512024de", "date": "2026-09-06", "subject": "docs: audit …",
-    "provenance": "handoff 03-new-projects.md, 2026-09-11",
-    "resolves": true, "verified": "2026-09-11",
-    "url": "https://github.com/…/tree/67ee512024de" }
-]
-```
-
-Set `resolves` by actually checking (`GET /repos/{o}/{r}/commits/{sha}`), and
-record the date you checked. `resolves: false` is valuable — it means the ref is
-gone and only a fork or the Wayback Machine will have it.
-
-### Check before you commit
-
-```bash
-./scripts/check-pins.py            # fails if a pin was dropped or rewritten
-```
-
-It compares the working tree against `HEAD` and reports any SHA, hash or URL that
-was **removed or changed in place** rather than appended.
-
-## Archived artifacts: three files, one artifact
-
-When an artifact is moved into `archive/`, its original path does **not** go empty. Three
-things sit together, and all three are committed:
-
-| Path | What it is |
-|---|---|
-| `foo.step` | **symlink** into `archive/`, so the file still resolves in place |
-| `foo.step.ARCHIVED.md` | **placeholder** — the required record: hash, size, sourcing, recovery URLs |
-| `foo.step.ARCHIVED.link` | symlink to `foo.step`, for a predictable naming scheme |
-
-The symlink target is always relative and always routes through this repo's **own**
-`archive/` symlink — `../../../archive/devices/foo/bar.step`, never `../../repo-archive/…`
-directly. That leaves a single indirection point: if the archive moves, the top-level
-`archive` link is the only thing that changes and every artifact link follows it.
-
-Run `./scripts/init.sh --link-archived` to create or refresh them. `archive_artifact.py`
-creates them itself when it archives something, so this is only needed to repair a tree.
-
-**Git's own control files are never linked** — `.gitignore`, `.gitattributes`, `.gitmodules`.
-Git reads those as configuration rather than content, so a symlinked one makes it print
-`Too many levels of symbolic links` on every command, and would in principle let a vendored
-upstream's ignore rules take effect here. They stay covered by their directory's record.
-
-### The placeholder is mandatory
-
-**Every archived artifact must have a `*.ARCHIVED.md`.** No exceptions — it is what a reader
-without the archive sees, and the only thing standing between a removed file and a lost one.
-The symlinks are convenience; the placeholder is the contract.
-
-Each placeholder must carry, or explicitly point at, the following:
-
-- **Two or more independent re-acquisition URLs.** One host disappearing should not strand the
-  artifact. If only one exists — or genuinely none — the placeholder says so in as many words
-  rather than leaving a silent gap that reads like an oversight.
-- **Sourcing detail**: version, tag, release, author, publication date, licence, how hard it was
-  to obtain, and any access quirks. Whatever is known. Nothing is not an option; *unknown,
-  recorded as unknown* is.
-
-### Detail may live elsewhere, but must be findable
-
-Bulk archiving often cannot establish per-file provenance, and repeating the same twenty lines
-across forty placeholders is worse than not repeating it. So the detail may live in:
-
-- a **directory-level record** — `README.md` or an `ARCHIVED.md` in the containing or parent
-  directory, prose or structured, describing the set as a whole;
-- the **acquisition manifest** for that device, which is the machine-readable form.
-
-When it does, the placeholder must **name where it lives** (`documented_in`). The rule is not
-"every placeholder repeats everything" — it is *no fact is absent without a pointer to it*. A
-placeholder that silently omits sourcing is a defect; one that says "see
-`../ACQUISITION.md`" is correct.
-
-The **acquisition manifest is a required part of research**, not an optional extra. It is the
-backstop that keeps a bulk operation from quietly producing forty under-documented files.
-
-### Write the prose, not just the fields
-
-Hashes and URLs make an artifact *recoverable*; they do not make it *understandable*. A
-directory-level `README.md` or `ARCHIVED-<TOPIC>.md` is the right place for the things that
-have no field to live in, and it is actively encouraged to write it at length:
-
-- **What** was archived, in plain terms — "the vendor demo bundle, all seventeen ESP-IDF
-  example projects and their vendored components".
-- **Why** it went out — size, redundancy, a vendored copy of an upstream library, a duplicate
-  of something already held, or material that turned out to be the wrong part.
-- **Why it is safe to have moved it** — reproducible from a named upstream at a named commit,
-  regenerable by a documented command, or simply held elsewhere. If it is *not* reproducible,
-  say that too; that artifact is the one to guard.
-- **What was learned from it** before it was moved, so the reasoning survives even if the file
-  never comes back.
-- **How hard it was to obtain** — dead vendor links, a login wall, a UA-blocked CDN, a forum
-  attachment that exists in one place. This is often the most valuable line in the file.
-
-A set record covering forty files well is worth more than forty thin placeholders. Prefer it
-when the material moved as a set, and have the placeholders point at it.
-
-### Check your work
-
-Two tools, both safe to re-run:
-
-```bash
-python3 tools/audit_archive.py     # markers, and records short of two independent sources
-python3 tools/link_archived.py     # dry run; --apply creates the symlinks
-```
-
-`audit_archive.py` reports two different failures. It exits non-zero when something in the
-archive is mentioned **nowhere** in the repo, which is the one that actually loses things. It
-also lists records carrying fewer than two URLs, and records whose URLs all point at a **single
-host** — five links to one vendor CDN are one outage from useless, so that is tracked separately.
-Neither is a hard gate: two sources is the rule *where it is possible*, and where it is not, the
-record should say so plainly instead of leaving a silent gap.
-
-Run it after any bulk archive operation. Nothing runs it automatically.
-
-
-### Patched or derived artifacts
-
-An artifact that is *upstream at some commit, plus changes* is meaningless without its base.
-Record a `base` block — repository, commit, tag, the patches applied in order, and the sibling
-artifacts sharing that base — and it is rendered into **every** placeholder derived from it.
-
-State it on each file rather than once in a README. Placeholders get read one at a time, by
-someone who found only that file, and "this is a two-line patch over `abc123`" is exactly the
-fact that makes the difference between recoverable and not.
-
 ## Git conventions
 
-### Commit from inside the symlinks
-
-`archive/` and `scratch/` are symlinks into a **different repository** (`../repo-archive`).
-Git will not cross a symlink boundary, so from this repo:
-
-```
-$ git add archive/devices/foo/bar.step
-fatal: pathspec 'archive/...' is beyond a symbolic link
-```
-
-Writing through the link works fine — it is only `git` that refuses. To commit archived or
-scratch material, `cd` into the link (or use `git -C`) so you are inside the archive repo:
-
-```bash
-cd archive && git add -A && git commit -m "..."      # or: git -C archive add -A
-```
-
-**Both links land in the same repository**, so you do not need to do it twice:
-
-| From `archive/` or `scratch/` | Stages |
-|---|---|
-| `git add -A` | **the whole archive repo — both tiers.** This is what you want |
-| `git add .` | only the directory you are standing in |
-| `git add -A :/` | explicit whole-repo, same as `-A` |
-
-So one `cd archive && git add -A && git commit` covers scratch material too.
-
-### Commit freely inside `archive/` and `scratch/`
-
-These are working stores, not a curated tree. **Stage and commit everything you see there**,
-including half-finished downloads, undecided material and obvious temporaries. An uncommitted
-artifact is the one that gets lost; a scruffy commit is not a problem.
-
-The same applies here in `hardware-doc`: staging and committing all files you can see is
-fine and expected.
-
-### Don't worry about other agents' files
-
-These checkouts are shared, but this needs no ceremony: **`git add -A` and commit.** It
-respects `.gitignore`, and sweeping up another session's in-progress files is harmless — a
-scruffy commit is not a problem, and an uncommitted artifact is the one that gets lost.
-
-What *is* worth avoiding:
-
-- **Don't `reset`, `stash`, `checkout --`, or `clean`** — those discard work irrecoverably.
-  Committing someone else's file is fine; deleting it is not.
-- **Don't stage deletions in `archive/`** unless they are renames. The archive is the last copy
-  of things; a rename is fine, an outright removal usually isn't. In `scratch/`, don't care.
-
-That's the whole rule. Add everything, commit, don't delete.
-
-### Other conventions
-
-- Do not amend or push **in this repository** unless asked.
+- Do not commit, amend or push unless asked.
 - Never stage a deletion as part of an archive operation: stage the file's content, then
-  move it. With the artifact symlinks in place the original path stays populated anyway, so
-  an archive operation should show up as *added symlink + added placeholder*, not a delete.
+  move it, and leave the resulting worktree deletion **unstaged**.
 - Filenames contain spaces (vendor EDA exports). Use `-z`/NUL-delimited git plumbing when
   scripting over `git status`.
diff --git a/README.md b/README.md
index 283cafa..805a4c3 100644
--- a/README.md
+++ b/README.md
@@ -13,9 +13,9 @@ It is normally checked out **beside** the repo that consumes it and symlinked in
 ```
 <repo-parent>/
 ├── code/                        consuming repo (config, infra, …)
-│   └── doc/hardware  ───────────┐ symlink, created by scripts/hardware-doc-init.sh
-├── hardware-doc/         ←──────┘ THIS REPO
-└── repo-archive/        bulk artifacts moved out of here (separate repo, usually unpublished)
+│   └── the repository root  ─────────┐ symlink, created by scripts/hardware-doc-init.sh
+├── hardware-doc/         ←────┘ THIS REPO
+└── hardware-doc-archive/        bulk artifacts moved out of here (separate repo, usually unpublished)
 ```
 
 It is **not a submodule and not vendored** into the consuming repo: at ~440 MB it would
@@ -23,21 +23,15 @@ make every clone of that repo roughly 6.5× larger. Consumers clone it on demand
 
 ```bash
 git clone https://github.com/developing-today/hardware-doc.git
-./scripts/init.sh        # only needed if the archive is not already a sibling
 ```
 
-`scripts/init.sh` points `archive/` and `scratch/` at the sibling artifact archive. A fresh
-clone usually needs nothing — the symlinks are committed relative, so they already resolve when
-`repo-archive/` sits beside this repo. Run it when the archive is elsewhere, newly added, or
-this repo is a linked worktree. It never clones and never deletes.
-
 ### Resolving the sibling archive
 
-`../repo-archive` is a sibling of the **real repository root** — not of your working
+`../hardware-doc-archive` is a sibling of the **real repository root** — not of your working
 directory, and not `~`. Under a git worktree resolve it via the *common* dir:
 
 ```bash
-ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/repo-archive"
+ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
 ```
 
 `--git-common-dir` rather than `--show-toplevel`: inside a linked worktree the toplevel is the
@@ -46,24 +40,11 @@ out of this repo; every one leaves a `*.ARCHIVED.md` placeholder here carrying s
 upstream commit/author/licence and multiple recovery URLs, so **the archive is optional** —
 its absence costs you convenience, not information.
 
-`repo-archive` is **itself a git repository**, but it is normally **unpublished or
+`hardware-doc-archive` is **itself a git repository**, but it is normally **unpublished or
 private** — at multiple gigabytes it is impractical to host alongside this one. Treat it as a
 local companion: if you have it, placeholders resolve to real bytes; if you do not, they
 resolve to recovery URLs.
 
-### The `archive/` symlink
-
-When the archive is present locally it is reachable at **`./archive/`** — a tracked symlink
-to `../repo-archive`. That gives `*.ARCHIVED.md` placeholders a stable in-repo path
-to point at.
-
-Both tracked symlinks in this project (`archive` here, `doc/hardware` in a consuming repo)
-are committed **relative**, and `hardware-doc-init.sh` swaps in an **absolute** path only
-where the relative form cannot resolve — then marks the path `--skip-worktree`, because
-`.gitignore` has no effect on tracked files. See
-[`AGENTS.md` § Symlinks and `--skip-worktree`](AGENTS.md#symlinks-and---skip-worktree) for
-the caveat that matters: while the flag is set, git will not update that path.
-
 See [`AGENTS.md`](AGENTS.md) for working conventions and
 [`.agents/skills/hardware-device-research/SKILL.md`](.agents/skills/hardware-device-research/SKILL.md)
 for the research method.
@@ -71,7 +52,7 @@ for the research method.
 - [Devices](devices/README.md)
 - [Components and interfaces](components/README.md)
 - [Vendor documentation-sourcing guides](vendors/README.md)
-- [Cross-cutting guides](guides/README.md) — [Espressif](guides/espressif/README.md) · [hardware subsystems](guides/hardware/README.md) · [NFC](guides/nfc/README.md) · [LoRa](guides/lora/README.md) · [markets and sourcing](guides/markets/README.md) · [reverse engineering](guides/reverse-engineering/netlists-from-vendor-eda-files.md) · [research technique](guides/research/finding-projects-that-use-a-board.md) · [NixOS host](guides/nixos/README.md)
+- [Cross-cutting guides](guides/README.md) — [Espressif](guides/espressif/README.md) · [hardware subsystems](guides/hardware/README.md) · [markets and sourcing](guides/markets/README.md) · [reverse engineering](guides/reverse-engineering/netlists-from-vendor-eda-files.md) · [research technique](guides/research/finding-projects-that-use-a-board.md) · [NixOS host](guides/nixos/README.md)
 - [Artifact manifest](artifact-manifest.md)
 - [Inventory](inventory.txt)
 - [Verification report](verification.json)
@@ -90,26 +71,15 @@ All research in this initial set was retrieved 2026-08-21. Downloaded files are
 | **Espressif ESP32-P4 and its official development boards** | **2026-08-21** | [ESP32-P4 component record](components/espressif/esp32-p4/README.md) plus **five** board records under [devices/espressif/](devices/espressif/). Established the real P4 board lineup (no Korvo board exists on P4); corrected three claims in the [Espressif vendor guide](vendors/espressif/README.md#8-change-log-for-this-guide) |
 | **Cross-link completion, vendor guides and market docs** | **2026-08-24** | **17 new [vendor sourcing guides](vendors/README.md)** (10 for manufacturers whose parts we document, 7 anticipatory), each with product lines, part-numbering conventions, distribution channels, URL patterns verified by live probe **with negative controls**, and an explicit evidence boundary. Added manufacturer back-links to every manufacturer-specific component record. New [markets and sourcing](guides/markets/README.md) guides and the [Espressif ecosystem map](guides/espressif/ecosystem-and-product-lines.md). **Corrected a WCH finding**: the `downloads/<PART>DS1_PDF.html` URLs return an identical 4,305-byte SPA shell for every path, existing or not |
 | **Host toolchain: NixOS embedded development** | **2026-08-30** | New [`guides/nixos/`](guides/nixos/README.md) covering ESP-IDF on NixOS (5.5.2 and 6.0.1 side by side, and why installing the package alone yields no `idf.py`), package availability in the locked nixpkgs with dated absences, and why LVGL/sensor libraries are project dependencies. New [SquareLine vendor guide](vendors/squareline/README.md) — the Linux build is **a ZIP, not an AppImage**, and the CDN **returns HTTP 206 for non-existent paths**. The 172 MiB proprietary editor ZIP is archived out of the repository with a [reacquisition record](vendors/squareline/artifacts/ARCHIVED-SQUARELINE-STUDIO-LINUX.md). ⚠ **Nothing in this pass was built or rebuilt** |
-| **Seven-session sweep: Xteink, M5Stack DinMeter / Cardputer / LoRa expansions, LilyGO K230 and T-Display-S3, LoRa generations** | **2026-09-04 → 2026-09-07** | ~40 device records and ~90 component records across seven parallel sessions, indexed here on 2026-09-07. New device families: [Xteink](devices/README.md#xteink-阅星瞳--星瞳-star-pupil) pocket e-readers (6), [LilyGO](devices/README.md#lilygo-shenzhen-xin-yuan-electronic-technology-also-trades-as-ttgo) (16, including the repository's **first RISC-V device**, the K230), and the expanded [M5Stack](devices/README.md#m5stack) family — DinMeter ×2, five Cardputers and eight Cardputer radio expansions. Three new vendor guides ([Canaan](vendors/canaan/README.md), [LilyGO](vendors/lilygo/README.md), [Semtech](vendors/semtech/README.md)) and three cross-cutting guides ([LoRa radio generations](guides/hardware/lora-radio-generations.md), [parallel 8080 LCD buses](guides/hardware/parallel-8080-lcd-buses.md), [RISC-V and vendor-SDK toolchains on NixOS](guides/nixos/riscv-and-vendor-sdk-toolchains.md)). ⚠ **Nothing in this pass was verified on physical hardware**, and each session was forbidden from editing shared indexes — the merge, its deferrals and its parked corrections are recorded in [`scratch/index-merge/README.md`](scratch/index-merge/README.md) |
-| **Round two: Xteink re-survey, schematic net-tracing, certification and market** | **2026-09-11** | Three parallel sessions, integrated the same day. ⭐ **Overturned the sweep's Xteink certification finding**: Xteink holds **five FCC Original Equipment grants** under grantee code `2BTR9`, and enumerating that code surfaced a **sixth device the vendor has never announced** — the [X4 Light](devices/xteink/x4-light/README.md). Dated the **X4 Classic launch** (2026-09-06, USD 79) and the **X4's withdrawal**. **291 schematic PDFs assessed** and five boards net-traced from PDF alone — Altium exports embed `CO`/`PI`/`NL` tokens at item coordinates, which is what made it possible ([guide](guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md)). **32 device records gained a `certification-and-compliance.md`**, each carrying its positive and negative controls. **174 FCC exhibits split**: 59 retained in-repo (57.8 MiB — internal photographs, including the **first public teardown of the Xteink X4**), 106 archived with self-sufficient placeholders (130.6 MiB); FCC exhibits are **US Government public records, redistribution `allowed`**. New guides: [finding certification records](guides/research/finding-certification-records.md), [tracing nets from schematic PDFs](guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md); new [Xteink vendor guide](vendors/xteink/README.md). ⚠ **Still nothing verified on physical hardware.** ⚠ `devices/m5stack/papermono/**` was owned by a live session throughout and was **not touched** — its deferrals are in [`scratch/index-merge/deferred-round2.md`](scratch/index-merge/deferred-round2.md) |
-
-| **Preprint repositories and the wider literature** | **2026-09-01 → 2026-09-11** | All 78 entries on Wikipedia's [List of preprint repositories][wpl] **plus what that list omits**, in [`research/preprint-repositories/`](research/preprint-repositories/README.md) — 40 records, ~23,000 lines. Deep records for the servers carrying hardware/software/systems work ([arXiv](research/preprint-repositories/arxiv.md), [Cryptology ePrint](research/preprint-repositories/cryptology-eprint-archive.md), [HAL](research/preprint-repositories/hal.md), [Zenodo](research/preprint-repositories/zenodo.md), [TechRxiv](research/preprint-repositories/techrxiv.md), [ECSarXiv](research/preprint-repositories/ecsarxiv.md)); grouped records for the rest. **160 landmark papers and theses individually verified** by fetching each identifier and machine-checking its title — [collected by field](research/preprint-repositories/landmark-papers.md). ⭐ **Corrected six Wikipedia claims by measurement** (OSF Preprints `>1,000,000` → **200,519** hosted; ScienceOpen → **~3,584**; [Synthical hosts nothing at all](research/preprint-repositories/synthical.md)). Extended beyond preprints to the [lawful full-text ladder](research/preprint-repositories/open-access-full-text-sources.md) (**USENIX has been paywall-free since 2008** — the real home of the systems literature), [government and university technical reports](research/preprint-repositories/government-and-institutional-technical-reports.md) (**the RISC-V ISA specs are six Berkeley EECS reports**, verified), the [computing servers Wikipedia omits](research/preprint-repositories/additional-preprint-servers.md) (**ECCC**, **OpenReview**), [theses and dissertations](research/preprint-repositories/theses-and-dissertations.md) (**the global ETD discovery layer collapsed in 2025–26**; EThOS is metadata-only since the British Library cyberattack), [dead-site recovery](research/preprint-repositories/recovering-dead-technical-sites.md) (**the DEC SRC/WRL/CRL series survives only as a 2007 bitsavers mirror**), and [bulk libraries and their copyright status](research/preprint-repositories/bulk-libraries-and-shadow-archives.md). ⚠ **No artifacts retained; no shadow-library service probed and no mirror domains recorded anywhere** |
-
-[wpl]: https://en.wikipedia.org/wiki/List_of_preprint_repositories
 
 ## Quick entry points
 
 - **How do I build firmware from this machine?** — [NixOS as an embedded development host](guides/nixos/README.md)
-- **Where is the paper for this, and can I trust it?** — [preprint repositories](research/preprint-repositories/README.md) · [landmark papers by field](research/preprint-repositories/landmark-papers.md) · [reliability and durability](research/preprint-repositories/reliability-and-durability.md)
-- **I have a citation and want the PDF, legally** — [open-access full-text ladder](research/preprint-repositories/open-access-full-text-sources.md)
-- **A vendor doc portal or datasheet host has died** — [recovering dead technical sites](research/preprint-repositories/recovering-dead-technical-sites.md)
 
 - **Which Espressif chip should this be?** — [ecosystem and product lines](guides/espressif/ecosystem-and-product-lines.md)
 - **Which of these boards should I use?** — [device comparison matrix](guides/markets/device-comparison-matrix.md) — all fourteen documented devices side by side
 - **How many PCNT units / DMA channels / UARTs does this chip have?** — [SoC peripheral reference](guides/espressif/soc-peripheral-reference.md)
 - **How do I drive this display?** — [display interfaces](guides/hardware/display-interfaces.md) · e-paper specifically — [e-paper displays](guides/hardware/e-paper-displays.md)
-- **How do I bring up an NFC reader, and why does it read nothing?** — [NFC guide](guides/nfc/README.md) — standards, antenna matching, and symptom-to-cause debugging
-- **What do SF, BW and CR actually cost me?** — [LoRa guide](guides/lora/README.md) — airtime, battery and duty-cycle arithmetic, LoRa vs LoRaWAN vs Meshtastic, and honest range estimation
 - **Where should I buy this, and will the docs survive?** — [vendor and marketplace comparison](guides/markets/vendor-comparison.md)
 - **Is this board a clone, and what differs?** — [clones, siblings and variants](guides/markets/clones-and-variants.md)
 - **How do I recover a pinout the vendor never published?** — [netlists from vendor EDA files](guides/reverse-engineering/netlists-from-vendor-eda-files.md)
@@ -117,27 +87,7 @@ All research in this initial set was retrieved 2026-08-21. Downloaded files are
 - **Espressif ESP32-S3** — [ESP32-S3R8](components/espressif/esp32-s3r8/README.md), including the [Bluetooth Classic limitation](components/espressif/esp32-s3r8/README.md#radio-capabilities-and-the-classic-bluetooth-limitation)
 - **How to obtain any Espressif document** — [vendor guide](vendors/espressif/README.md)
 - **Espressif framework knowledge** — [ESP-IDF peripheral capabilities](guides/espressif/esp-idf-peripheral-capabilities.md) · [ESP-ADF audio pipelines](guides/espressif/esp-adf-audio-pipelines.md) · [ESP-IoT-Solution components](guides/espressif/esp-iot-solution-components.md)
-- **Which LoRa chip is this, and what breaks if I swap it?** — [LoRa radio generations](guides/hardware/lora-radio-generations.md) — the four generations of Semtech silicon, and the migration cost. ⚠ The **LLCC68 is pin-compatible with the SX1262 and 19 dB worse**; the **SX1268 cannot reach 868/915 MHz** at all
-- **My display is black and the library says it initialised** — [parallel Intel-8080 LCD buses on ESP32](guides/hardware/parallel-8080-lcd-buses.md) — why the display-library choice matters more than the board, and a debugging checklist
-- **How do I build for a RISC-V board with a vendor SDK?** — [RISC-V and vendor-SDK toolchains on NixOS](guides/nixos/riscv-and-vendor-sdk-toolchains.md) — why `pkgsCross.riscv64-*` is not a substitute for XuanTie GCC
-- **I want a cheap pocket e-reader I can reflash** — [Xteink family](devices/README.md#xteink-阅星瞳--星瞳-star-pupil) — six products, four ESP32-based. ⚠ **The X4 Pro is not an enhanced X4**; firmware for one will not run on the other
-- **Which LilyGO T-Display-S3 is this actually?** — [LilyGO family index](devices/README.md#lilygo-shenzhen-xin-yuan-electronic-technology-also-trades-as-ttgo) — one *name* covering eleven boards, eight display controllers and four chargers. Sourcing: [LilyGO vendor guide](vendors/lilygo/README.md)
-- **How do I add LoRa, sub-GHz or NFC to a Cardputer?** — [M5Stack Cardputer expansions](devices/README.md#cardputer-expansions--lora-sub-ghz-and-nfc--added-2026-09-04) — and note that only the **ADV + Cap LoRa-1262** combination has an upstream Meshtastic variant
-- **How do I obtain a Semtech, Canaan or LilyGO document?** — [Semtech](vendors/semtech/README.md) · [Canaan](vendors/canaan/README.md) · [LilyGO](vendors/lilygo/README.md) vendor guides
-- **Is this thing certified, and how would I even check?** — [finding certification records](guides/research/finding-certification-records.md) — FCC grantee-code enumeration, which regulatory databases are actually reachable, and **the positive/negative controls that make an absence finding mean anything**. ⚠ `fccid.io` serves **403 to a Chrome UA and 200 to `curl`** — the honest user agent is the one that works
-- **The vendor published a schematic PDF and nothing else** — [tracing nets from schematic PDFs](guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md) — Altium exports embed invisible `CO`/`PI`/`NL` tokens at item coordinates, which is what makes a net list recoverable with poppler alone. ⚠ **KiCad and EAGLE exports often outline their text to vector paths** and are then untraceable — but a usable second export often sits in the same directory
-- **What has this vendor certified that it never announced?** — [Xteink vendor guide](vendors/xteink/README.md) — the worked example: enumerating grantee code `2BTR9` surfaced the [X4 Light](devices/xteink/x4-light/README.md), a device with no announcement, no listing and no price
 
 ## Verification reports
 
-- [Preprint and scholarly-literature repositories](research/preprint-repositories/VERIFICATION.md) — 2026-09-11 re-probe of a 2026-09-01 → 07 pass: 40 records, 78/78 list coverage, 160 identifiers verified, 0 broken links. **Five findings corrected** (Berkeley EECS restored at a new path; Anubis answers HTTP 200 not 403; CERN CDS and ETH no longer walled; OpenReview's API block was transient; CogPrints' recovery route degraded) and **one dating error flagged**.
 - [Seeed XIAO ESP32S3 Sense](VERIFICATION-xiao-esp32s3-sense.md) — 2026-08-24: 1,092 files, 42 artifacts validated, 0 broken links, 0 hardware-tested claims.
-- [M5Stack PaperMono](VERIFICATION-m5stack-papermono.md) — 2026-09-01: 50 authored files (~14,700 lines), 23 artifacts validated, 0 broken links, 0 hardware-tested claims; 5 hypotheses refuted, 10 conflicts left open.
-- [**Seven-session device sweep**](VERIFICATION-sweep-2026-09-04.md) — 2026-09-04 → 2026-09-07: the umbrella report for the whole pass. 469 authored files, **10 387 relative links checked / 1 broken** (pre-existing, in a vendored upstream README), 61 artifacts magic-byte validated / 0 mismatches, 0 device-record orphans, 0 deletions on any shared file, `HEAD` unchanged. ⚠ **Zero on-device claims.**
-- [Xteink device family](VERIFICATION-xteink.md) — 2026-09-04: Xteink X3, X4, X4 Pro, X4 Classic, S4 and Nano.
-- [M5Stack DinMeter](VERIFICATION-m5stack-dinmeter.md) — 2026-09-04: DinMeter (K134) and DinMeter v1.1 (K134-V11).
-- [M5Stack Cardputer family](VERIFICATION-m5stack-cardputer.md) — 2026-09-04: 48 authored files, 331/331 links, 6/6 artifact hashes, 0 protected files touched.
-- [LilyGO T-Display K230](VERIFICATION-lilygo-t-display-k230.md) — 2026-09-04: T-Display K230 and K230 Kit, the repository's first RISC-V device.
-- [**Xteink family, round two**](VERIFICATION-xteink-round2.md) — 2026-09-11: the **X4 Classic launch** at USD 79 and the X4's withdrawal, the **undocumented X4 Light** found by FCC grantee enumeration, and three new custodians for the X4 Pro.
-- [Certification, market and adjudication pass](scratch/market-and-certification/README.md) — 2026-09-11: closes two of the [2026-09-04 sweep](VERIFICATION-sweep-2026-09-04.md) §6 gaps and **overturns its Xteink certification finding**. 26 FCC filings, 174 exhibits, with positive and negative controls.
-- [Schematic net-tracing pass](scratch/schematic-tracing/README.md) — 2026-09-11: **291 schematic PDFs assessed**, five boards fully traced from PDF alone; per-file verdicts in [`traceability-census.md`](scratch/schematic-tracing/traceability-census.md).
diff --git a/SIZE-AUDIT.md b/SIZE-AUDIT.md
index b746804..bef12d8 100644
--- a/SIZE-AUDIT.md
+++ b/SIZE-AUDIT.md
@@ -1,21 +1,7 @@
-# Size audit — `hardware-doc`
+# Size audit — ``
 
 > Where the megabytes are, what can be regenerated, and what must stay.
-> Measured **2026-08-24**, re-checked **2026-08-30** after the repository split — still 442 MB.
-> Total: **442 MB on disk / 429.5 MB in 3,322 files**.
->
-> Paths below are relative to this repository's root. When this audit was first written the tree
-> lived at `doc/hardware/` inside the config repo; it is now the root of its own repository, and
-> bulky artifacts sit in the sibling `../repo-archive` reachable as `archive/` and `scratch/`.
-
-> **This audit is the worked example; the rule lives in the method.**
-> [`SKILL.md` § *When to archive*](.agents/skills/hardware-device-research/SKILL.md#when-to-archive)
-> states the test an artifact must pass before it may be moved out — content already mined into
-> Markdown, genuinely derived/bulky/off-topic, and a placeholder able to carry enough provenance to
-> reacquire it. **Size alone is not a reason to archive; *derivedness* is.**
-> This page applies that test to the real tree, category by category, so a future pass can usually
-> read off the answer instead of re-deriving it. If the two ever disagree, the method wins and this
-> page needs re-measuring.
+> Measured **2026-08-24**. Total: **442 MB on disk / 429.5 MB in 3,322 files**.
 
 ## Executive summary
 
diff --git a/VERIFICATION-lilygo-t-display-k230.md b/VERIFICATION-lilygo-t-display-k230.md
deleted file mode 100644
index eff21c8..0000000
--- a/VERIFICATION-lilygo-t-display-k230.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Verification — LilyGO T-Display K230 / Canaan Kendryte K230
-
-**Date: 2026-09-04.** Single research pass, **no hardware in hand**. Nothing was staged or
-committed. No shared index file was edited.
-
-## 1. Scope of what was created
-
-| Path | Files |
-|---|---:|
-| `devices/lilygo/t-display-k230/` | 42 (README + 16 supporting docs + 17 feature guides + 3 example files + 2 acquisition files + artifact placeholders + 14 images + 1 media manifest) |
-| `components/canaan/k230/` | 1 README + 10 artifact files |
-| `components/{raydium,goodix,galaxycore,realtek×2,nordic-semiconductor×2,texas-instruments,semtech,analog-devices,asair,lontium,xlsemi,unidentified}/` | 15 component READMEs |
-| `vendors/canaan/README.md` | 1 |
-| `guides/nixos/riscv-and-vendor-sdk-toolchains.md` | 1 (**new file**; `guides/nixos/README.md` unmodified) |
-| `scratch/lilygo-k230/` | working files + `README.md`, `index-fragments.md`, `vendor-guide-additions.md` |
-
-## 2. Checks run and results
-
-| # | Check | Result |
-|---|---|---|
-| 1 | **Authored relative Markdown links resolve** | **398 links across 65 authored files. 0 broken.** |
-| 2 | **Bundled upstream Markdown excluded from the link check** | Yes — the 7 Canaan documents contain **80** upstream-relative image links that do not resolve locally. Excluded deliberately; stated in [`components/canaan/k230/artifacts/README.md`](components/canaan/k230/artifacts/README.md). Rewriting them would break byte-identity with the pinned commit. |
-| 3 | `index-fragments.md` links | ~30 unresolved **by design** — they are relative to each snippet's *destination*, not to the scratch file. Annotated in the file itself. |
-| 4 | **SHA-256 of retained chip documents** | `sha256sum -c SHA256SUMS` → **7 / 7 OK** |
-| 5 | **SHA-256 + byte size of every retained image** | **14 / 14 match** the manifest |
-| 6 | **File type validated from magic bytes, not extension** | All 14 images start `FF D8 FF` (JPEG). `file(1)` is absent on this host; the magic was checked directly. |
-| 7 | **Duplicate-hash detection** | **0 duplicate groups** across all new artifacts and media |
-| 8 | **JSON schema validity** | `media/manifest.json`, `examples/catalog.json`, `acquisition/manifest.json` all parse |
-| 9 | **Filenames portable ASCII** | Yes, no exceptions |
-| 10 | **Failed downloads not retained under misleading extensions** | Two 404 responses saved as `.html`; correct. Recorded in `scratch/lilygo-k230/README.md`. |
-| 11 | **Bidirectional device ↔ component links** | Every component record cited by the device has a **Used By** entry naming the device; every component in the key-spec table links out. Four `Used By` rows for **pre-existing** records were **not applied** (see §4) and are parked in `index-fragments.md`. |
-| 12 | **Every URL has a retrieval date** | Yes — all `2026-09-04` unless a document date is given |
-| 13 | **Every source row has class + medium + date** | Yes, `sources.md` |
-| 14 | **Artifact provenance complete** | Yes; unknown values written as unknown with a reason (e.g. firmware SHA-256 "enumerated from the tree API, not downloaded") |
-| 15 | **Redistribution status + disposition on every artifact** | Yes; 19 acquisition records |
-| 16 | **Downloader verify-only mode** | ⚠ **Not implemented.** `acquisition/README.md` gives ordered clean-clone commands and a verification recipe, but no committed downloader script exists. Recorded as a gap rather than claimed. |
-| 17 | **`local-cache` paths ignored and absent from the index** | N/A — no `local-cache` artifacts were created |
-| 18 | **Coverage: every fitted capability appears with a task link** | 32 capabilities in `coverage.md`; 16 feature guides; every one reachable from the README's *Common tasks* index |
-| 19 | **Vendor driver audited against datasheets** | **Partially.** Audited: the TCA8418 register usage, the PMU power-key flow, the Goodix driver *choice*, the LVGL and Serial-LTE-Modem patch sets. **Not audited: `vvcam/src/gc2093.c`** — no GalaxyCore datasheet is public, so there was nothing to decode against. Recorded as `GC-6`, not skipped silently. |
-| 20 | **No component record built from a candidate or near-miss** | Confirmed. Every part number was read from LilyGO's pin map, product listing, or a source-tree census. The `K230` ↔ T-Embed CC1101 SKU collision and the `RC01812` string were both flagged rather than promoted. |
-| 21 | **Refuted hypotheses recorded with evidence and date** | Yes — nine negative results in `gaps-and-conflicts.md`, plus refuted candidate names (`T-Deck K230`, `T-K230`, `T-Deck Pro K230`, `K230 Cardputer`) and the Bruce-firmware association |
-| 22 | **PDF text-layer validation** | N/A — no PDF was retrieved. All chip documentation is upstream Markdown. |
-| 23 | **Tree digests record their recipe** | N/A — no tree digest was taken |
-| 24 | **Prevalence claims backed by a stated sample** | Yes — "four firsthand-ownership reports across 26 comments in the two largest threads, six threads total" |
-| 25 | **Launch vs current pricing kept separate** | Yes; launch price for the bare board is explicitly recorded as **not established** |
-| 26 | **Repository status** | Only intended paths changed (§1). No shared index touched. |
-
-## 3. Evidence honesty
-
-**Zero commands were executed against hardware. Zero examples were built. Zero measurements were
-taken.** The highest evidence class anywhere in this pass is `reported-working`. This is stated at
-the top of `development.md`, `factory-firmware.md`, `performance.md`, `coverage.md`,
-`compatibility-and-status.md` and every feature guide, and `coverage.md` carries an explicit
-"build-tested: 0 / hardware-tested: 0" row.
-
-## 4. Shared files deliberately not edited
-
-Per this session's constraints, and confirmed with `find <file> -mmin -30`:
-
-| File | Why not edited |
-|---|---|
-| `components/semtech/sx1262/README.md` | modified within 30 min — another session active |
-| `components/texas-instruments/tca8418/README.md` | same |
-| `components/texas-instruments/bq27220/README.md` | same |
-| `components/espressif/esp32-s3r8/README.md` | same **and** the claim is unverified (`GC-2`) — no Used-By added on purpose |
-| `components/generic/micro-sd-sdmmc/README.md` | quiet, but batched with the others for a single reviewed paste |
-| `README.md`, `devices/README.md`, `components/README.md`, `vendors/README.md`, `software/README.md`, `artifact-manifest.md`, `guides/markets/*`, `devices/m5stack/**`, `guides/nixos/README.md` | out of scope for this session |
-| `vendors/lilygo/README.md` | **did not exist**; a sibling session documenting T-Display-S3 may own it. Findings parked in `scratch/lilygo-k230/vendor-guide-additions.md`. |
-
-All additions for these are ready to paste in
-[`scratch/lilygo-k230/index-fragments.md`](scratch/lilygo-k230/index-fragments.md).
-
-## 5. Open gaps
-
-Nine tracked conflicts (`GC-1`…`GC-9`) and six unidentified parts (`U1`…`U6`). The three that
-would resolve the most:
-
-1. **A PCB photograph** — settles `GC-2` (ESP32-S3), `GC-4` (LT9611), `GC-9` (16 MB flash) and
-   four of the six unidentified parts at once.
-2. **One session with hardware** — `commands.md` §5 lists the exact commands; most of `GC-1`,
-   `GC-3`, `GC-7`, `GC-8` fall in an afternoon, and it would produce the **first published
-   performance data for this board**.
-3. **`Xinyuan-LilyGO/T-Display-K230_canmv_rt`** — 745 MB, 25 stars, unexamined. The largest
-   unexplored artifact.
-
-## 6. Decisions needed from the user
-
-| Item | Question |
-|---|---|
-| 7 Canaan documents (~256 KB) | Repository licence is BSD-2-Clause; the documents carry a conflicting "shall not disseminate" notice. **Stage, local-cache, or metadata-only?** Currently unstaged. |
-| 14 product/wiki images (~3.0 MB) | No licence statement on either LilyGO host. **Stage or keep unstaged?** Currently unstaged. |
-| LilyGO repositories and prebuilt firmware | No licence file on any of them. Currently `reference-only`, not downloaded. **Leave as-is?** |
-| An acquisition downloader script | Not written. **Worth adding?** |
diff --git a/VERIFICATION-m5stack-cardputer.md b/VERIFICATION-m5stack-cardputer.md
deleted file mode 100644
index 4de683c..0000000
--- a/VERIFICATION-m5stack-cardputer.md
+++ /dev/null
@@ -1,67 +0,0 @@
-# Verification — M5Stack Cardputer family pass
-
-**Date 2026-09-04.** Subject: [Cardputer ADV](devices/m5stack/cardputer-adv/README.md) (full
-depth) plus [v1.0](devices/m5stack/cardputer-v1.0/README.md),
-[v1.1](devices/m5stack/cardputer-v1.1/README.md),
-[Mesh Kit](devices/m5stack/cardputer-mesh-kit/README.md),
-[CardputerZero](devices/m5stack/cardputer-zero/README.md).
-
-*(This file follows the convention of `VERIFICATION-m5stack-papermono.md` and
-`VERIFICATION-xiao-esp32s3-sense.md`. A line linking it from the umbrella `README.md` is staged
-in [`scratch/m5stack-cardputer/index-fragments.md`](scratch/m5stack-cardputer/index-fragments.md)
-because that file was out of scope for this session.)*
-
-## Result
-
-| Check | Result |
-|---|---|
-| Authored Markdown files | **48** across 5 device records and 10 component records |
-| Relative links resolving | **331 / 331** ✅ (one batch of 3 fixed during verification) |
-| JSON schemas valid | 3 / 3 ✅ (`acquisition/manifest.json`, `media/manifest.json`, `examples/catalog.json`) |
-| Artifact SHA-256 + byte size vs manifest | **6 / 6 OK, 0 failures** ✅ |
-| File type validated by **magic bytes** | ✅ `%PDF-1` ×2, `<!doct` ×2 (this host has no `file`) |
-| Failed downloads retained under a misleading extension | **none** — the one dead PNG URL was checked by magic bytes and deleted, and is recorded as dead in three places |
-| PDF text layer validated before transcription | ✅ positive control: ADV layer yields `TCA8418RTWR`/`ES8311`/`NS4150B`/`BMI270`, v1.1 layer yields `74HC138`/`NS4168`/`SPM1423HM4H-B`, both matching the corresponding product pages' PinMap tables |
-| Every transcribed value also read from a **rendered** sheet crop | ✅ 10 crops, arguments recorded so each is reproducible |
-| Protected files modified | **none** (root `README.md`, `devices/README.md`, `components/README.md`, `vendors/README.md`, `artifact-manifest.md`, `software/README.md`, `guides/markets/*`, `devices/m5stack/papermono*` all untouched by this session) |
-| Concurrent sessions' trees modified | **none** — proposed additions staged in `index-fragments.md` |
-| Anything staged or committed | **no** — everything is untracked, awaiting review |
-
-## Findings that survived verification
-
-* **The ADV keyboard matrix is electrically identical to the v1.0/v1.1 matrix.** Same 56
-  switches, same `Y0..Y7` nets, same `R27`–`R34` 22 Ω. Only the scanner changed (74HC138 →
-  TCA8418), and the two drivers' coordinate maths were shown algebraically equivalent.
-* **The v1.0 and v1.1 mainboard schematics are byte-identical** — `6016c1fe…`, served under both
-  product ids `481` and `1127`.
-* **Cardputer v1.1 already uses Stamp-S3A**, not StampS3. A widely repeated community belief
-  refuted from M5Stack's own comparison table.
-* **`G13` is host TX and `G15` is host RX** on the CAP header. Four sources agree; the Cardputer
-  Mesh Kit page's EXT table is wrong and contradicts its own Cap-Bus table.
-* **The Stamp-S3A's `U4` is labelled `JW5712`** on the published sheet — correcting a concurrent
-  session's "part number not established". Verified against a hash-matched vendor render.
-* Two **live driver defects** in `M5Unified`'s ES8311 callbacks, one of which has already
-  propagated into Bruce.
-
-## Deliberate limitations, stated rather than hidden
-
-* **No hardware.** Every build/run status in `examples/catalog.json` is `not-tested`, and no
-  measurement of any kind appears in `performance.md`.
-* **Certification is "not established", not "absent"** — `/en/certification` was not fetched with
-  the positive control the vendor guide requires.
-* **Chinese and Japanese sources were not searched.** For a Shenzhen vendor with a large Japanese
-  community, that is the largest single gap.
-* Three unresolved items are recorded in
-  [`gaps-and-conflicts.md`](devices/m5stack/cardputer-adv/gaps-and-conflicts.md): the Grove
-  SCL/SDA orientation, the BMI270 interrupt routing, and a `+3.3V` feedback divider whose
-  arithmetic does not resolve. Each names what would settle it.
-
-## Two lessons worth carrying forward
-
-1. **Altium PDFs hide the readable text in a Form XObject.** A parser that reads only the
-   `CO`/`PI`/`NL` marker layer returns hundreds of plausible-looking "words" and **none** of the
-   part numbers. It fails silently. This cost two sessions independently — see
-   `gaps-and-conflicts.md` §C7.
-2. **`sha256sum` embeds the path you give it**, so the same 33 files produced three different
-   tree digests from three working directories during this very verification. The recorded recipe
-   now pins the working directory as well as the locale.
diff --git a/VERIFICATION-m5stack-dinmeter.md b/VERIFICATION-m5stack-dinmeter.md
deleted file mode 100644
index 7e875c3..0000000
--- a/VERIFICATION-m5stack-dinmeter.md
+++ /dev/null
@@ -1,245 +0,0 @@
-# Verification — M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-**Research pass date: 2026-09-04.** Records verified:
-[`devices/m5stack/dinmeter`](devices/m5stack/dinmeter/README.md),
-[`devices/m5stack/dinmeter-v1.1`](devices/m5stack/dinmeter-v1.1/README.md), and the 15 component
-records they cite.
-
----
-
-## 0. The headline, stated first
-
-> **Zero claims in these records are hardware-tested. No DinMeter of either revision was
-> available at any point.**
-
-This is a documentary and source-code analysis: vendor documentation, three Altium-published
-schematics parsed at the marker layer, four independent board-support source trees, and a broad
-public-source sweep. It is thorough about what published artefacts can establish and it is worth
-**nothing** as evidence of how a physical unit behaves. Every claim carries an evidence label and
-every untested command says so.
-
-| Claim category | Count |
-|---|---:|
-| Hardware-tested claims | **0** |
-| Commands executed successfully (acquisition, extraction, analysis) | ~45 |
-| Commands presented as untested (`not-tested`) | 14 |
-| `reported-working` (vendor- or CI-published, not run here) | 9 |
-| Examples built or run here | **0 of 22 catalogued** |
-| Features with a hardware test status | **0 of 20** |
-
-## 1. File and byte inventory — recomputed from disk
-
-| Metric | Value |
-|---|---:|
-| Regular files across both device records + 15 component records | **124** |
-| Symlinks (3 archived artifacts × 2 links each) | 6 |
-| Markdown files authored | **69** |
-| Bytes in repository (excluding symlink targets) | **13 396 847** (13.4 MB) |
-| Bytes archived out of the repository | **21 625 485** (21.6 MB) |
-| Downloads attempted | 28 |
-| **Downloads failed** | **0** |
-| HTML/error pages retained under a misleading extension | **0** |
-
-Breakdown of the two device records:
-
-| Record | Files | Notes |
-|---|---:|---|
-| `devices/m5stack/dinmeter` | 61 | full record: 34 authored `.md`, 10 images, 7 derived analyses, 5 source snapshots, 3 primary artifacts |
-| `devices/m5stack/dinmeter-v1.1` | 34 | scoped revision record: 21 authored `.md` incl. `stamp-s3-to-s3a-delta.md`, 5 images, 2 deliberately-duplicated artifacts |
-
-## 2. Binary validation by magic bytes
-
-Every non-text artifact was validated by content, not by extension.
-
-| Extension | Files | Detected type | Mismatches |
-|---|---:|---|---:|
-| `.pdf` | 10 | `%PDF-` | **0** |
-| `.webp` | 10 | `RIFF`…`WEBP` | **0** |
-| `.jpg` | 6 | `ff d8 ff` | **0** |
-| `.tar.gz` | 2 | gzip | **0** |
-| `.stl` / `.kicad_mod` | 5 | ASCII text (expected) | **0** |
-| **Total** | **33** | | **0** |
-
-### ⚠ One mismatch was found and corrected during acquisition
-
-Four images fetched from `cdn.shopify.com` have canonical URLs ending **`.webp`** but returned
-**JPEG** bytes (`ff d8 ff e1 … Exif`) — Shopify content-negotiates the format and ignores the
-path extension. They were **renamed locally to `.jpg`** so the extension matches the content;
-bytes are unmodified and the URLs are recorded exactly as served, each with a
-`format_mismatch_note`. Recorded in
-[`devices/m5stack/dinmeter-v1.1/media.md`](devices/m5stack/dinmeter-v1.1/media.md) and as a
-durable vendor trap in [`vendors/m5stack/README.md`](vendors/m5stack/README.md) §11.8.
-
-## 3. Link integrity
-
-| Metric | Value |
-|---|---:|
-| Markdown files checked | **71** (69 authored + 2 additively edited shared files) |
-| Relative links resolved | **563** |
-| **Broken links** | **0** |
-
-Four were broken on the first pass and were fixed: three pointed at
-`components/nxp/pcf8563/README.md`, which does **not exist** (that component directory holds only
-`artifacts/`), and one had an incorrect `../` depth. Absolute `http(s)://` links were not
-fetched during verification.
-
-**Archive paths are excluded from the "must resolve" requirement** per the repository convention —
-the archive is machine-local. All three archived artifacts nonetheless resolve on this machine
-and each satisfies the placeholder contract (§4).
-
-## 4. Archived artifacts — the three-link chain
-
-| Artifact | Bytes | SHA-256 (16) | Placeholder | Cited by owner | Cited by consuming device |
-|---|---:|---|---|---|---|
-| `devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf` | 7 459 888 | `8b3db00abbc7e317` | ✔ | ✔ device README artifact layout | ✔ `sources.md` S-02 |
-| `devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf` | 11 261 000 | `617a9ea8039ed1fc` | ✔ | ✔ device README artifact layout | ✔ `sources.md` V-02 |
-| `components/m5stack/stamp-s3/artifacts/Stamp-S3.step` | 2 904 597 | `7f29337cdac90c80` | ✔ | ✔ component README §5, §6 | ✔ **both** device records, via the component |
-
-Each placeholder carries hash, byte size, media type, retrieval date, licence status,
-redistribution status, disposition, reason for archiving, reproducibility, and **two or more
-independent reacquisition URLs**. All three symlinks and their `.ARCHIVED.link` companions
-resolve.
-
-## 5. Bidirectional device ↔ component links
-
-| Check | Result |
-|---|---|
-| Component records created or extended | **15** |
-| With a `Used By` section | **15 / 15** |
-| Naming DinMeter and/or DinMeter v1.1 and its role | **15 / 15** |
-| Device READMEs linking every component they mention | ✔ verified — the key-specification table links all 14 functional parts |
-
-Records: `m5stack/stamp-s3`, `m5stack/stamp-s3a`, `sitronix/st7789v2`, `sitronix/st7789p3`,
-`generic/bm8563`, `generic/tp4057`, `microne/me3116am6g`, `silergy/sy7088`, `belling/bl8075`,
-`murata/mun3cad01-sc`, `sgmicro/sgm2578`, `unidentified/m5stack-dinmeter/rotary-encoder`,
-`unidentified/m5stack-dinmeter/buzzer`, `unidentified/m5stack-stamp-s3a/dcdc-u4`, and
-`awinic/aw35122` (**additively extended**, not created).
-
-Five are `unidentified` or schematic-only because no datasheet exists. **No part number was
-guessed anywhere**, and no candidate from a comparison shortlist was promoted to a finding.
-
-## 6. Manifests and structured data
-
-| File | Valid JSON | Contents |
-|---|---|---|
-| `devices/m5stack/dinmeter/acquisition/manifest.json` | ✔ | 27 records — 20 downloaded, 7 derived, 1 archived, **0 failed** |
-| `devices/m5stack/dinmeter-v1.1/acquisition/manifest.json` | ✔ | 9 records — 8 downloaded, 1 derived, 1 archived, **0 failed**, 2 flagged byte-identical to v1.0 |
-| `devices/m5stack/dinmeter/media/manifest.json` | ✔ | 10 images, full provenance, 0 teardown/PCB |
-| `devices/m5stack/dinmeter-v1.1/media/manifest.json` | ✔ | 5 images, **4 URL-extension mismatches recorded** |
-| `devices/m5stack/dinmeter/examples/catalog.json` | ✔ | 22 examples — 8 official, 10 community, 2 rejected, 2 inaccessible, 7 selected, 3 vendored, **0 built** |
-
-Every artifact record carries expected SHA-256, byte size, canonical URL, retrieval date,
-licence, licence evidence, redistribution status, disposition and repository state.
-
-## 7. Duplicate hashes — intentional, and quantified
-
-| Pair | SHA-256 | Redundant bytes | Why kept |
-|---|---|---:|---|
-| v1.0 ↔ v1.1 schematic | `03ec3353…` | 433 658 | **The duplication is the finding.** Deduplicating would erase the evidence that M5Stack published one file under two URLs and two SKU names |
-| `DinMeter.stl` ↔ `DinMeter_v1.1.stl` | `90f04d6a…` | 573 284 | same |
-| `Stamp-S3.stl` ↔ `Stamp-S3A.stl` | `f72c1af2…` | 158 484 | same |
-| **Total intentional redundancy** | | **1 165 426** (1.17 MB) | |
-
-**One duplicate was deduplicated:** the ESP32-S3 datasheet fetched from
-`m5stack-doc…/472/esp32-s3_datasheet_en.pdf` (SHA-256 `b6db403d…`) is byte-identical to
-`components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf` already
-held. **Not re-added**; the additional URL is recorded in the source table instead.
-
-## 8. Source-table completeness
-
-| Check | Result |
-|---|---|
-| Source rows | 37 (v1.0 record) + 16 (v1.1 record) = **53** |
-| Rows with `Class` | 53 / 53 |
-| Rows with a retrieval date | 53 / 53 |
-| Rows with version/date **or an explicit `unknown`** | 53 / 53 |
-| Rows stating what they establish | 53 / 53 |
-| Rows stating scope/limitations | 53 / 53 |
-
-## 9. Shared files — what was and was not touched
-
-**Not edited** (as instructed): `README.md`, `devices/README.md`, `components/README.md`,
-`vendors/README.md`, `artifact-manifest.md`, `software/README.md`, `guides/markets/*`,
-`devices/m5stack/papermono*`. Proposed additions are staged as ready-to-paste Markdown in
-[`scratch/m5stack-dinmeter/index-fragments.md`](scratch/m5stack-dinmeter/index-fragments.md).
-
-**Two files additively edited**, each after confirming `find <file> -mmin -30` returned empty
-immediately beforehand:
-
-| File | Change | Existing content altered? |
-|---|---|---|
-| `vendors/m5stack/README.md` | **Appended** §11 (14 live-probed findings + change-log addendum) strictly after §10 | **No** |
-| `components/awinic/aw35122/README.md` | **Inserted** one `###` subsection inside the existing `## 4. Used By` | **No** |
-
-**No state-changing git command was run at any point.** `git status` was read-only.
-
-## 10. Evidence discipline — specific checks
-
-| Check | Result |
-|---|---|
-| PDF text layer validated before transcription | ✔ page-frame zone letters `A`–`D`, numbers `1`–`4`, and seven known part strings verified at expected coordinates; 84 of 85 marker-derived designators match visible text |
-| A legible-but-wrong extraction was caught and discarded | ✔ Altium draws its marker layer **twice**; the first parse produced `PPIIJJ110011` for `PIJ10101`. Output discarded, glyph dedup added, failure preserved in `commands.md` §4 |
-| Absence proven by enumeration, not by searching for the expected | ✔ complete `CO`/`PI`/`NL` census; `COS1`/`COR20`/`COY1` etc. searched in both single **and** double-struck forms — zero hits |
-| Extraction incompleteness disclosed | ✔ ~20 of ~260 `PI` markers unrecovered, stated with the cause; no published table rests on a missing marker |
-| Document metadata read | ✔ the BM8563 datasheet carries a stray `MAX1937` header string — a derived document — recorded in its component record |
-| Candidates never promoted to findings | ✔ five parts left `unidentified`; the repo's existing Alps encoder record explicitly **not** claimed for this device |
-| Refuted/negative results recorded | ✔ ESPHome/Tasmota/Meshtastic/Bruce-upstream all **0 hits**, recorded; 8 confirmed-already-correct claims listed in `gaps-and-conflicts.md` §10 |
-| Conflicts recorded rather than resolved by preference | ✔ **9** open conflicts across the two records |
-| Blocked sources reported honestly | ✔ `community.m5stack.com` 401 — and **no UA rotation attempted**, since it is authentication, not bot-blocking |
-
-## 11. Open conflicts carried forward
-
-| # | Conflict | Where |
-|---|---|---|
-| 1 | PORT.A/B wire colours — vendor PinMap vs schematic + M5Unified | `dinmeter/gaps-and-conflicts.md` §1 |
-| 2 | `S1`, `R20`, `Y1` — designator text with no marker layer | §2 |
-| 3 | v1.1 assets are byte-identical v1.0 assets | §3, v1.1 V2 |
-| 4 | ST7789P3 — named 3×, documented nowhere | §4, v1.1 V3 |
-| 5 | Stamp-S3A 24 mm vs 26 mm | §5, v1.1 V5 |
-| 6 | Grove rail: 5.00 V spec vs ≈5.38 V from the schematic's own formula | §6 |
-| 7 | Stamp-S3A DC-DC: page says MUN3CAD01-SC, schematic says otherwise | v1.1 V4 |
-| 8 | Backlight PWM: 200 Hz (M5Stack's firmware) vs 5 kHz (Espressif) | `compatibility-and-status.md` §6 |
-| 9 | Rear FPC pin numbering reversed between Stamp revisions | v1.1 V6 |
-
-## 12. The one prediction that most needs testing
-
-**DinMeter v1.1's RGB LED almost certainly will not light with stock M5Unified.** The Stamp-S3A
-moves the WS2812B-2020 onto a switched rail gated by GPIO38, and M5Unified at master
-`8530f5377d782e4a25a6c482de2e71c3f75ca8eb` has no GPIO38 enable step for any board.
-
-**Status: `inferred`** — vendor documentation + schematic net reading + source grep. **Not
-reproduced on hardware.** Two lines of code on a real v1.1 unit would settle it:
-
-```cpp
-pinMode(38, OUTPUT); digitalWrite(38, HIGH); delay(1);   // then drive GPIO21
-```
-
-## 13. Verification verdict
-
-| Property | Status |
-|---|---|
-| Inventory recomputed from disk | ✔ |
-| SHA-256 computed for every retained artifact | ✔ |
-| Binary types validated by magic bytes | ✔ 33/33, **0 mismatches** |
-| Failed downloads retained under misleading extensions | ✔ none |
-| Authored relative links resolve | ✔ 563/563 |
-| Archived artifacts satisfy the placeholder contract | ✔ 3/3, ≥2 reacquisition URLs each |
-| Three-link chain intact for archived artifacts | ✔ 3/3 |
-| Bidirectional device ↔ component links | ✔ 15/15 |
-| Manifests valid and complete | ✔ 5/5 |
-| Duplicate bytes quantified and justified | ✔ 1.17 MB intentional; 1 cross-repo duplicate avoided |
-| Source rows complete | ✔ 53/53 |
-| Shared index files untouched | ✔ |
-| State-changing git commands | ✔ **none run** |
-| **Hardware-tested claims** | **0 — stated plainly throughout** |
-
-**Verdict: the records are internally consistent, fully cross-linked, honestly labelled, and
-verifiable from a clean clone.** Their limitation is singular and stated on every page: no
-hardware was in hand, so nothing here is a measurement.
-
----
-
-*Report generated 2026-09-04 as part of the DinMeter research pass. Bulk archive:
-`archive/devices/m5stack/dinmeter{,-v1.1}/` and `archive/components/m5stack/stamp-s3/`.
-Working store and proposed index additions:
-[`scratch/m5stack-dinmeter/`](scratch/m5stack-dinmeter/README.md).*
diff --git a/VERIFICATION-m5stack-papermono.md b/VERIFICATION-m5stack-papermono.md
deleted file mode 100644
index 3b99e32..0000000
--- a/VERIFICATION-m5stack-papermono.md
+++ /dev/null
@@ -1,263 +0,0 @@
-# Verification report — M5Stack PaperMono research pass
-
-**Date:** 2026-09-01 · **Subject:** `devices/m5stack/papermono`,
-`devices/m5stack/papermono-lite`, 21 component records, 2 vendor guides,
-3 reusable tools.
-
-**Headline caveat, stated once and plainly: there was no PaperMono hardware in
-this pass.** No command was executed against a device, nothing was flashed,
-nothing was measured. Every behavioural claim in the record is `inferred`,
-`reported-working` (vendor-documented), or read from vendor source at a cited
-`file:line`. Nothing is `executed-success` except operations on files.
-
-## Result
-
-| Check | Result |
-|---|---|
-| Authored Markdown | 60+ files, ~25,000 lines |
-| Artifacts retained | 23 files, 55,405,315 bytes |
-| Broken relative links in authored records | **0** |
-| PDF/binary magic validation | **23/23 pass** (`%PDF-` / `0xE9`) |
-| SHA-256 computed for retained artifacts | **23/23** |
-| Acquisition manifest entries | 24 |
-| `fetch.py --verify-only` | **pass**, 14 cached, 0 failed, exit 0 |
-| Duplicate content among new artifacts | **none** |
-| `tools/audit_archive.py` — losable artifacts | **0** |
-| Filenames portable ASCII | yes |
-| Failed downloads saved under misleading extensions | **none** — `fetch.py` refuses this structurally |
-
-Bundled upstream Markdown was **excluded** from link checking, as the method
-allows. A repo-wide check found 67 broken links, all inside vendored upstream
-trees (`waveshare/.../source-snapshots/`, `seeed-studio/.../wiki-snapshot/`,
-`nicolai-electronics/tanmatsu/artifacts/`) that predate this pass. **Zero broken
-links exist in authored records anywhere in the repository.**
-
-## What the evidence actually rests on
-
-The most load-bearing source is the official schematic PDF. Because M5Stack's
-`M5_Hardware` repository contains **no C153 entry** (verified at commit
-`a240115c`, 2026-08-17), there is no published netlist, so the schematic is the
-only primary machine-readable-ish evidence available.
-
-It was mined by recovering Altium's invisible `CO`/`PI`/`NL` marker text from
-the PDF and pairing it by coordinate — three reusable tools now in
-[`tools/`](tools/): `altium_pdf_netlist.py`, `altium_pdf_pin_table.py`,
-`altium_pdf_render_sheet.py`. This yielded a **230-designator census** and full
-pin tables for the ESP32-S3, both custom chips, the flash and every connector.
-
-**The method's limits were hit and are recorded.** Adjacency is not
-connectivity: unlabelled wire-only nets are invisible to it, and on the dense
-power sheet it produced readings that were wrong (it initially mis-attributed
-the charger designator). Every pin assertion was therefore cross-checked either
-by rendering the sheet at 200 dpi and reading it, or against a second
-independent source — vendor firmware, the vendor product page, or the DKE panel
-manual's own pinout, which matched the schematic's e-paper FPC position for
-position. A parser bug that silently ate pin names (`GPIO0` parsed as a marker)
-was found and fixed before any table was published.
-
-## Claims examined and refuted during the pass
-
-Recorded because a refuted hypothesis that is not written down gets
-re-investigated:
-
-1. **"The vendor's PaperMono page is wrong about `PYG3_BL_PWM`."** Refuted by
-   schematic sheets 2 and 4. Both vendor pages are correct; they quote different
-   layers of the drawing. See
-   [`pin-naming-and-the-pyg-ambiguity.md`](devices/m5stack/papermono/pin-naming-and-the-pyg-ambiguity.md).
-2. **"The NFC matching network is undocumented."** Refuted — the released NFC
-   sheet `2/2` carries the complete front end. Sheet `1/2` is genuinely absent.
-3. **"The RTC is on `3V3_L1`."** This is what M5Stack's own block diagram says.
-   Refuted by reading sheet 4: `VBAT`/`VIO`/`VDD`/`VOUT` are all on `3V3_L0`.
-   The vendor block diagram is wrong; the board is right.
-4. **"The restock delay is an e-ink driver IC shortage."** The cited post and
-   its full reply chain were retrieved; the reason does not appear in them.
-   Hearsay.
-5. **"PaperMono supersedes PaperS3."** Contradicted by the vendor's own
-   specifications — fewer pixels, fewer grey levels, smaller battery, no
-   expansion port.
-
-Equally recorded: the vendor's product-page pin tables were checked exhaustively
-and found **correct**, with two omissions and no errors. Confirming existing
-documentation is a result.
-
-## Conflicts left open
-
-Ten unresolved conflicts and ten gaps are itemised in
-[`gaps-and-conflicts.md`](devices/m5stack/papermono/gaps-and-conflicts.md). The
-ones most worth someone's attention:
-
-- **C1** panel manual says `2Grey Level`; M5Stack markets and ships 4-level grey
-- **C3** M5GFX drives the panel at 40 MHz against a 20 MHz maximum stated
-  independently by both Solomon Systech and DKE — the best candidate for the
-  refresh instability M5Stack itself warns about
-- **C4** the M5IOE1's actual I²C address `0x4F` is absent from its own manual
-- **C13** M5Unified `getVoltLow()` reads `VBLF`, not `VLF` — returns `false` on
-  exactly the occasion it is used for
-- **G7** no power or battery-life figure exists anywhere, vendor or independent
-
-## Known incompleteness
-
-Honest gaps in this pass, not oversights discovered later:
-
-- **No imagery.** No product, teardown or PCB photograph is retained. Vendor
-  imagery is not licensed for redistribution and no independent teardown existed
-  at the snapshot date. Recorded rather than filled with unattributed images.
-- **Closed since first writing.** `performance.md` and the `examples/`
-  catalogue now exist. All 43 third-party repositories are pinned to a commit,
-  which closes the recorded defect that citations could not be re-resolved.
-  Still true: **no example was built, flashed or run**, and none can be until
-  hardware exists.
-- **Three datasheets are unobtainable** (`CN4040M000157A530001`,
-  `LMD4737T261-AC02`, `RS-C1415MBAR`), recorded `lost` with search ledgers.
-- ~~Third-party repository citations are unpinned~~ — **fixed 2026-09-01**:
-  43 of 43 repositories resolved and pinned to a full commit SHA in
-  `examples/catalog.json`. None were gone, private or archived.
-- **`scratch/m5stack-papermono/` is uncommitted** at the time of writing: raw
-  page captures, 200 dpi sheet renders, panel-manual page images, per-designator
-  pin tables and the three subagent FINDINGS files. It belongs in the archive
-  repository.
-
-## Scope statement
-
-This is a **reproducible broad-coverage snapshot dated 2026-09-01**, not a claim
-that no other resource exists. Search cutoff 2026-09-01; 140 distinct queries
-across 7 passes are logged in
-[`research-log.md`](devices/m5stack/papermono/research-log.md). The stopping
-criterion was met: two consecutive broad passes returned only vendor marketing
-copy and duplicates. The product was eleven days old, out of stock since launch
-day, and had attracted zero written independent reviews — so the ceiling here is
-set by the world, not by the search.
-
-
-## Second review pass — 2026-09-01
-
-A review pass after the initial write-up found and fixed **four factual errors in
-documents written during the first pass**, all discovered by reading the
-schematic more carefully rather than by new retrieval:
-
-| Was | Is | Where it was wrong |
-|---|---|---|
-| Battery "NTC-sensed" at `J2` | `J2` is 2-contact, power only. The `100K-RNTC` is **`R15` on the mainboard** at the IP2315's `NTC` pin | `README.md`, `pinouts-and-buses.md`, `power-architecture.md` |
-| One CC pulldown (`R14`) | **Two** — `R4` on CC1 *and* `R14` on CC2 | `power-architecture.md` |
-| USB-C receptacle is `U1` sheet 2 | Its designator is the bare string **`USB`** | `pinouts-and-buses.md` |
-| `J6` has 16 pins | **12 contacts + 4 tabs** | `pinouts-and-buses.md` |
-
-Two open questions closed: the IP2315 charge-programming resistor is **`R17` =
-15 kΩ**, and the reported missing `N1` designator was a **parser artifact** —
-`N`-series designators do not exist on this board, and the only genuine gaps are
-`R46`, `R48`, `R55`–`R57`.
-
-Seven new conflicts were recorded (C18–C24), including that this record's own
-`README.md` recommends a Waveshare e-paper alternative the knowledge base cannot
-support — all four Waveshare records here are LCD boards.
-
-**The correction rate is the finding.** Four errors in the first pass's own
-output, all in tables that looked authoritative, all caught only by re-reading
-the primary artifact. The automated schematic extraction is a reading aid; where
-this record's claims rest on it alone they are marked `inferred`, and that
-marking should be taken seriously.
-
-
-## Third review pass — 2026-09-01/02
-
-### Closed
-- **C24 (Waveshare recommendation unbacked)** — closed by writing
-  [`devices/waveshare/esp32-s3-epaper-3.97`](devices/waveshare/esp32-s3-epaper-3.97/README.md),
-  the knowledge base's first Waveshare **e-paper** board. Same SoC, same 8 MB/16 MB
-  memory, same 3.97" 4-grey panel, **active area matching the PaperMono's DKE panel
-  to 0.01 mm** — the two boards plausibly share a panel (`inferred`, not
-  established: Waveshare names neither supplier nor controller).
-- **Example survey** — `examples/{catalog.json,best.md,search-log.md}` written.
-  **43 of 43 repositories resolved and pinned to full commit SHAs**; none gone or
-  private. Ten selected, including one deliberate negative
-  (`free-ink-on-paper-mono`: demonstrates FreeInk on this board, carries a
-  relevant partial-refresh patch, and has **no LICENSE file** — all rights
-  reserved, must not be copied).
-
-### Added
-- **Device-independent guides** at [`guides/nfc`](guides/nfc/README.md) and
-  [`guides/lora`](guides/lora/README.md), filling the layer the method calls for
-  between component records and device feature guides. Both bidirectionally
-  linked to `papermono/features/{nfc,lora}.md` with explicit applicability
-  statements ("applies with deltas", deltas enumerated).
-- [`software/`](software/README.md) tree with a taxonomy (libraries / frameworks
-  / applications / tooling / ecosystems) and its first record,
-  [CrossPlay](software/applications/crossplay/README.md) — a CrossPoint Reader
-  fork that **carries `papermono` build environments**, now cross-referenced from
-  the PaperMono project population as Class P (support present in build config,
-  **nobody has reported running it**).
-
-### New vendor trap recorded
-Waveshare's **MediaWiki `api.php` and `index.php` return a PHP fatal parse error
-with HTTP 200**. This breaks the `action=parse&prop=wikitext` route that this
-knowledge base's own Waveshare vendor guide recommends, and it fails in the worst
-way — a success status with an error body. Rendered pretty URLs still work; the
-storefront search is the working enumeration route. Dated and recorded in
-[`vendors/waveshare`](vendors/waveshare/README.md).
-
-### Ledger state
-15 resolved (R), 25 open conflicts (C), 10 gaps (G). Record: 41 markdown files,
-11,620 lines. `acquisition/fetch.py --verify-only` passes, 0 failed.
-Link check: 457 authored markdown files, **0 broken links** — the six remaining
-repository-wide are all inside vendored upstream trees and are excluded by the
-method.
-
-### Still open, and honestly so
-- **No hardware.** Nothing in this record has been built, flashed or measured.
-- **NFC and LoRa each rest on a single artifact** — the vendor's own demo. No
-  independent implementation of either exists for this board, so an error there
-  propagates here uncontradicted.
-- **No imagery retained**; no power, battery-life or thermal figure exists from
-  any source.
-- **Chinese-language platforms (Gitee, Bilibili, CSDN) were never searched** —
-  the largest known hole in the project survey, and the first place a later pass
-  should look.
-
-## Fourth review pass — 2026-09-04
-
-### Carried-over technical followups, all three closed
-
-| Followup | Outcome |
-|---|---|
-| **SX1262 G4** — are RadioLib's SX126x §15 errata workarounds applied at the *pinned* 7.2.1, not just master? | **Resolved: all four are.** `rxGain`/sensitivity ×4, `fixPaClamping` ×1 (+×3 in `SX1262.cpp`, **×0 in `SX1261.cpp`**, matching the datasheet's "SX1262 only" note), `fixImplicitTimeout` ×3, `fixInvertedIQ` ×2. Read from tag `7.2.1`, tag object `b91c6af1…` |
-| **RadioLib licence** — "LGPL-3.0 upstream" vs MIT | **Resolved: MIT**, and has been since 2018. `license.txt` (1,068 B) and `library.json` both say MIT at 7.2.1. The LGPL claim is withdrawn |
-| **ST25R3916 matching network** | **Recorded as an open observation.** The inferred `L1/L2`+`C6/C8` pairing gives a ≈11.7 MHz corner — *below* the 13.56 MHz carrier, the wrong side for an EMC low-pass. Pairing with the 220 pF group gives ≈20.6 MHz, which is conventional. Most likely the inference is wrong, not the board |
-
-The RadioLib licence case is a lesson worth keeping: it survived two passes
-because a probe for a file named `LICENSE` returned 404 — the file is
-`license.txt`, lowercase. **A 404 on a guessed filename is not evidence of
-absence.** The same mistake produced the Waveshare "no documentation" error
-recorded in the third pass.
-
-### Software tree — three records now written
-
-`software/` gained a taxonomy (libraries / frameworks / applications / tooling /
-ecosystems) and its first substantive records:
-
-- [**CrossPoint Reader**](software/applications/crosspoint-reader/README.md) — ★7,538, 1,621 forks
-- [**FreeInk SDK**](software/frameworks/freeink-sdk/README.md) — its submodule dependency
-- [**CrossPlay**](software/applications/crossplay/README.md) — a fork, with patch-portability analysis
-
-**Two findings bear directly on this device record:**
-
-1. **Upstream CrossPoint ships `[env:papermono]`** (plus `-gh_release` and
-   `-gh_release_rc`). PaperMono support is not fork-only — the 7,500-star upstream
-   builds for this board.
-2. **A CrossPoint plugin could not implement NFC or LoRa.** Per a carried-over
-   analysis, the plugin system is browser JavaScript plus JSON manifests with no
-   code running on the MCU and no peripheral access at all. Adding radios would
-   require a fork or an upstream feature, not a plugin. Flagged for
-   re-verification; the finding is `reported-working`, not confirmed in this pass.
-
-### Also settled
-
-`crosspoint-reader/.gitmodules` proves **CrossPoint consumes FreeInk SDK as a git
-submodule** — the dependency direction question is closed. The chronology is the
-counterintuitive part: **CrossPoint (2025-12-03) predates FreeInk (2026-06-03)**;
-FreeInk is a re-architecture of the SDK CrossPoint already used, itself derived
-from `open-x4-epaper/community-sdk` with SSD1677/UC8253 LUTs credited to
-CidVonHighwind.
-
-### State
-Link check across my scope: **57 files, 0 broken.** `fetch.py --verify-only`
-passes. Conflict ledger: C23 closed this session alongside the three above.
diff --git a/VERIFICATION-sweep-2026-09-04.md b/VERIFICATION-sweep-2026-09-04.md
deleted file mode 100644
index 61b1759..0000000
--- a/VERIFICATION-sweep-2026-09-04.md
+++ /dev/null
@@ -1,316 +0,0 @@
-# Verification — seven-session device sweep, 2026-09-04 → 2026-09-07
-
-Umbrella report for the parallel research pass covering **Xteink**, **M5Stack DinMeter /
-Cardputer / Cardputer radio expansions**, **LilyGO T-Display K230**, **LilyGO T-Display-S3 and
-variants**, and the **Semtech LoRa generation lineage**.
-
-Per-session reports carry the detail and are authoritative for their own subject:
-[Xteink](VERIFICATION-xteink.md) ·
-[M5Stack DinMeter](VERIFICATION-m5stack-dinmeter.md) ·
-[M5Stack Cardputer](VERIFICATION-m5stack-cardputer.md) ·
-[LilyGO T-Display K230](VERIFICATION-lilygo-t-display-k230.md).
-The index merge and its parked corrections are in
-[`scratch/index-merge/README.md`](scratch/index-merge/README.md).
-
----
-
-## 1. The headline caveat
-
-⚠ **No claim in this sweep was verified on physical hardware.** No board was purchased,
-powered, flashed or probed. Every build, flash, pinout and behavioural claim is labelled
-`reported-working`, `inferred` or `not-tested` in its own record; the count of
-`executed-success` **on-device** claims across all seven sessions is **zero**, and each session
-states this in its own words.
-
-What *was* executed locally: HTTP retrieval, checksum and magic-byte validation, PDF text
-extraction, repository cloning and log/tree inspection via the GitHub API, and the link and
-deletion audits below.
-
-## 2. Scope delivered
-
-| | Count |
-|---|---|
-| Device records created | **38** across 3 new manufacturer trees (`xteink/` 6, `lilygo/` 16, `m5stack/` 16 — of which 2 pre-existed) |
-| Authored Markdown files added (excl. `artifacts/`, excl. `scratch/`) | **469** |
-| Component records in the library after the sweep | **201** |
-| Vendor sourcing guides after the sweep | **37**, incl. new `canaan/`, `lilygo/`, `semtech/` |
-| Cross-cutting guides added | **6** — [LoRa radio generations](guides/hardware/lora-radio-generations.md), [parallel 8080 LCD buses](guides/hardware/parallel-8080-lcd-buses.md), [RISC-V and vendor-SDK toolchains on NixOS](guides/nixos/riscv-and-vendor-sdk-toolchains.md), [adding LoRa/NFC/sidelight to e-ink firmware](guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md), [SoC choice for battery e-ink devices](guides/hardware/soc-choice-for-battery-eink-devices.md), [handheld and e-ink device landscape](guides/markets/handheld-and-eink-device-landscape-2026-09.md) |
-| Binary artifacts retained under `artifacts/` | **161** |
-
-## 3. Machine-checked results
-
-| Check | Method | Result |
-|---|---|---|
-| Relative-link integrity | Every inline Markdown link in every authored `.md` outside `artifacts/`, `archive/` and `scratch/`, fenced code blocks stripped, anchors ignored, percent-decoded | **10 387 links checked · 1 broken** |
-| The one broken link | `devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO_Webcam/README.md → docs/xiao-esp32s3-sense.jpg?raw=true` | **Pre-existing and out of scope** — vendored upstream README, preserved as supplied. The root [`README.md`](README.md) already states bundled upstream Markdown is not claimed to be link-clean. Not introduced by this sweep and deliberately not "fixed", since editing it would diverge the vendored copy from upstream |
-| Artifact type validation | Magic bytes compared against extension for every typed artifact added in the sweep (`%PDF`, `PK`, `\x89PNG`, `\xff\xd8\xff`, `RIFF`, `\x1f\x8b`) | **61 typed artifacts · 0 mismatches** — no HTML error page saved under a document extension |
-| Device-record orphans | Every `devices/<vendor>/<board>/` directory grepped for an inbound link from [`devices/README.md`](devices/README.md) | **0 orphans.** One was found and fixed: `nicolai-electronics/tanmatsu`, orphaned since the 2026-08-24 pass — see §5 |
-| Deletion audit on shared files | `git diff -- <file> \| grep -c '^-[^-]'` for all 25 shared files touched by the merge and cross-link passes | **0 deletions on every file** |
-| Git state | `git rev-parse HEAD` before and after | **`4aa02e1030b3b0861e6fc34f23fa2113ec80d324`, unchanged.** 91 pre-existing staged paths from a concurrent session left intact; nothing added, committed, stashed or reset |
-
-## 4. Concurrency discipline
-
-Seven research sessions plus two integration sessions ran in parallel against this repository
-while a separate session worked on the PaperMono and `software/` trees.
-
-- Every research session was **forbidden from editing shared indexes** and instead wrote
-  ready-to-paste Markdown to `scratch/<subject>/index-fragments.md`. Those seven fragment files
-  are retained as the audit trail.
-- Every edit to a pre-existing file was **append-only** and preceded by a `find <file> -mmin -15`
-  liveness check. One file (`vendors/lilygo/README.md`) was found live, deferred, and applied
-  18 minutes later.
-- Where a session found another session's record to be **wrong**, it did not overwrite it. It
-  added a dated note beneath the original line, leaving the original visible, and filed the
-  item in [`scratch/index-merge/corrections-requiring-review.md`](scratch/index-merge/corrections-requiring-review.md)
-  for a human to adjudicate. **Six corrections are parked there and none has been applied.**
-
-## 5. The one repository defect fixed in passing
-
-`devices/nicolai-electronics/tanmatsu/` — a substantial record from the 2026-08-24 pass — had
-**never been linked from [`devices/README.md`](devices/README.md)** and was unreachable by
-navigation. A `## Nicolai Electronics` section was added on 2026-09-07, written only from the
-record's own opening paragraphs. **The record itself was neither reviewed nor modified**, and it
-remains the authority on its own contents.
-
-## 6. What this sweep does not establish
-
-- **No hardware.** See §1. In particular, no pinout, no flash command and no current-draw figure
-  has been confirmed against a physical board.
-- **No net-level schematic tracing** for the LilyGO family — `poppler` was unavailable, and the
-  session names this as the largest cheap improvement available.
-- **The Xteink X4 Pro record traces substantially to one commit.** No teardown, no firmware dump
-  and no price-independent corroboration were obtained for the family's flagship.
-- **`components/canaan/k230`** documents a SoC whose vendor SDK the sessions read but never
-  built; the NixOS toolchain routes in
-  [`guides/nixos/riscv-and-vendor-sdk-toolchains.md`](guides/nixos/riscv-and-vendor-sdk-toolchains.md)
-  are `inferred`, all three of them.
-- **Marketplace, clone and used-market price sampling** was not done for most devices. The
-  landscape guide's own evidence boundary states this.
-- **Certification and regulatory records** were checked only for Xteink (where the finding was
-  that no external CE/FCC marking exists on the devices at all). No positive control was run, so
-  the absence is weaker evidence than it looks.
-
----
-
-*Compiled 2026-09-07. Method: [`.agents/skills/hardware-device-research/SKILL.md`](.agents/skills/hardware-device-research/SKILL.md).*
-
----
----
-
-# Round two — 2026-09-11
-
-**Nothing above this line has been edited.** Three further sessions ran on 2026-09-11 — Xteink
-round two, schematic net-tracing, and certification / market — and their results were integrated
-on the same date. Where round two refutes round one, a dated correction is added; the original
-sentence stays visible. **A verification report that quietly rewrites itself is worthless.**
-
-Per-session detail: [`VERIFICATION-xteink-round2.md`](VERIFICATION-xteink-round2.md) ·
-[`scratch/schematic-tracing/README.md`](scratch/schematic-tracing/README.md) ·
-[`scratch/market-and-certification/README.md`](scratch/market-and-certification/README.md).
-The round-two merge, its deferrals and its corrections:
-[`scratch/index-merge/deferred-round2.md`](scratch/index-merge/deferred-round2.md) ·
-[`scratch/index-merge/corrections-requiring-review.md`](scratch/index-merge/corrections-requiring-review.md).
-
-## R1. ⚠ §6 is wrong about Xteink certification — corrected, not rewritten
-
-§6 records:
-
-> **Certification and regulatory records** were checked only for Xteink (where the finding was
-> that no external CE/FCC marking exists on the devices at all). No positive control was run, so
-> the absence is weaker evidence than it looks.
-
-**The self-doubt in that last sentence was justified. The finding is refuted.**
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**,
-grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment
-authorisations** — one for every ESP32-based device in the tree:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | **2026-08-13** | XTEINK X4 Light — **never announced** |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-**The error was a category error**, and it is worth naming precisely: the pass confused *"no mark
-visible in a product photograph"* with *"no grant exists"*. Only the first was ever tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits a software **e-label** instead of a printed mark — ordinary for a device
-with a screen. **Likely, and not verified.**
-
-**This time the controls were run.** Positives `2BTR9-XTEINKX4`, `2AC7Z-ESPS3WROOM1`,
-`2AN3WM5CARDPUTER` → **200**. Negatives `2AN3WM5CARDPUTERZERO`, `2ASYE-T-DISPLAY-K230`,
-`2ZZZZNOSUCHGRANTEE` → **404**. The grantee was **enumerated in full** (`2BTR9` → exactly five
-IDs), so the absence of an S4 or Nano grant is an absence against a complete listing.
-
-**Transferable lesson:** round one searched by *product name*. Xteink files under model codes a
-name search never reaches. **Enumerate the vendor's FCC grantee code** and you get its complete
-certified product list, including unannounced devices. Written up in
-[`guides/research/finding-certification-records.md`](guides/research/finding-certification-records.md).
-
-Corrections are appended beneath the stale claim in **13 Xteink records** and in
-[`VERIFICATION-xteink.md`](VERIFICATION-xteink.md) §C1–C4. Five new
-`certification-and-compliance.md` records carry the full evidence.
-
-## R2. The X4 Classic launched; the X4 was withdrawn
-
-**X4 Classic**, marketed **"XTEINK X4 Classic (X4 V2)"**, listed **2026-09-06** at **USD 79**
-(95 with base). It **replaced the X4**, whose product record **and all four dedicated
-accessories** are now gone from the catalogue — on 2026-09-04 the accessories were still listed
-but sold out, which was an end-of-life *signature*; a week later it is a completed withdrawal.
-
-Two independent sessions enumerated `xteink.com/products.json` on 2026-09-11 (25 products) and
-returned identical figures. The FCC succession corroborates the replacement. The stale rows in
-[`devices/README.md`](devices/README.md) are **unedited**, with a dated correction beneath them.
-
-## R3. A sixth Xteink device, found by enumeration rather than by name
-
-[**X4 Light**](devices/xteink/x4-light/README.md) — FCC **`2BTR9-X4L`**, granted **2026-08-13**.
-Never announced, listed, priced or reviewed. No `x4-light` collection handle exists, so unlike the
-X4 Classic there is **no pre-launch signal** in the storefront either.
-
-⚠ Its SoC, panel, feature set and price are **all unknown**. *"Light"* is a marketing word the
-filing does not define. Internal photographs unlock **2027-02-09**; external photographs are
-already public and held in the record.
-
-This directly qualifies round one's *"Models that do not exist"* finding. That finding was correct
-about `X4 Plus / Air / Pro Max` and remains correct. It was **not** correct that the family was
-closed — and it could not have known, because it had no grantee code to enumerate.
-
-## R4. Schematic net-tracing — 291 PDFs assessed
-
-Every `artifacts/**/*.pdf` in the repository — **291 files** — was assessed for traceability.
-Per-file verdicts: [`scratch/schematic-tracing/traceability-census.md`](scratch/schematic-tracing/traceability-census.md).
-
-**The enabling finding: Altium exports embed invisible `CO` / `PI` / `NL` marker tokens at item
-coordinates** — component outlines, pins and net labels — so a net list is recoverable from the
-PDF text layer alone, with poppler and no EDA sources. That is what made the traces below
-possible. Method: [`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-
-**Five boards fully traced**, each gaining a `schematic-netlist.md`: LilyGO T-Display-S3 (shared),
-M5Stack Cardputer ADV (4 sheets), DinMeter, Cap LoRa-1262 and Cap CC1101. Two also gained a
-`driver-vs-document-audit.md` — the vendor driver read against the schematic and the datasheet.
-**8 schematic crops** were added across five `media/` directories, each with a **separate sibling
-manifest**, because `media/manifest.json` is not append-safe as JSON.
-
-Two traps worth more than the traces:
-
-- ⚠ **KiCad and EAGLE exports frequently outline schematic text to vector paths.** `pdftotext`
-  then yields **zero words** and the file is permanently untraceable. **For ZeroWriter Ink and the
-  Seeed XIAO ESP32S3 a usable second export of the same design sits in the same directory** — the
-  `Eeschema` copies. Without that check both designs look undocumented and are not.
-- ⚠ **Non-Altium exports carry no `CO`/`PI`/`NL` tokens**, so every binding must be geometric.
-  That applies to the Espressif ESP32-P4 board schematics.
-
-⚠ **The richest untraced sheet in the repository is the M5Stack PaperMono's** —
-`PaperMono_SCH_V0.6.2`, 6 pages, **144 `NL` tokens**, fully traceable, obtainable in about an
-hour. It was **not traced**, because that record was owned by a live session throughout both
-rounds.
-
-## R5. Unidentified parts — three resolved or advanced, none deleted
-
-| Record | Outcome |
-|---|---|
-| `unidentified/m5stack-stamp-s3a/dcdc-u4` | ✅ **Resolved — `JW5712`.** Confirmed independently by two round-two sessions. Retained for linkage, not retired |
-| `unidentified/lilygo-t-display-s3-family/axpm65611` | ⚠ **Function established** — AMOLED bipolar display-bias supply, 12-pin — **identity still unknown**. No real record is possible without a manufacturer |
-| `unidentified/m5stack-dinmeter/rotary-encoder` | Topology established: 5-terminal, A/COM/B + switch. Identity unknown |
-| `unidentified/m5stack-dinmeter/buzzer` | Topology established: magnetic, AC-coupled drive. Identity unknown |
-
-`JW5712` is now known to be fitted on **three** M5Stack boards. ⚠ Its only datasheet is a **raster
-scan** — 0 extractable words — so it cannot be text-searched.
-
-**No `unidentified/*` record was deleted, and none should be.** Other records link to them and
-they are the stable landing place for a search on the unknown string.
-
-## R6. Artifacts — 174 FCC exhibits, decided
-
-Round one left **174 exhibit PDFs from 26 filings** in `scratch/`, outside the repository **with
-no placeholders**, which the method forbids for anything useful. Round two applied the rules.
-
-| | Files | Size |
-|---|---:|---:|
-| **Retained in the repository** — internal photographs and ID-label exhibits, ≤ 4 MiB each | **59** | **57.80 MiB** (60.61 MB) |
-| **Archived**, each with a self-sufficient placeholder at its former repo path | **106** | **130.59 MiB** (136.93 MB) |
-| **Parked** — PaperMono, live session | 11 | 10.27 MiB |
-| Not copied — byte-identical to bytes already present | 5 | — |
-
-Internal photographs were prioritised because for several of these boards they are the **only
-public internal imagery that exists**, and `2BTR9-XTEINKX4`'s are the **first public teardown of
-the Xteink X4**. Licensing is stated plainly: FCC exhibits are **US Government public records**,
-redistribution **`allowed`** — correcting the `unknown` recorded earlier.
-
-⚠ **The "281 MB" figure for that corpus is the whole scratch subject directory.** The PDFs are
-**195.48 MiB / 204.97 MB**; the rest is text extractions, filing HTML and logs.
-
-## R7. Machine-checked results — re-run, not copied
-
-Every figure below was measured on **2026-09-11** by
-[`scratch/index-merge/verify-round2.py`](scratch/index-merge/verify-round2.py). Round one's
-numbers are **not** reused.
-
-| Check | Round one (2026-09-07) | **Round two (2026-09-11)** |
-|---|---|---|
-| Relative links checked / broken | 10 387 / **1** | **10 970 / 1** |
-| Typed artifacts / magic-byte mismatches | 61 / **0** | **1 219 / 3** |
-| Device records / orphans | 38 created / **0** | **60 / 0** |
-| Component records | 201 | **194** *(counted at `components/<mfr>/<part>/README.md`; round one's figure used a different rule)* |
-| Vendor guides | 37 | **38** — new [`vendors/xteink/`](vendors/xteink/README.md) |
-| Authored `.md` (excl. `artifacts/`, `archive/`, `scratch/`) | 469 *added* | **958** *total* |
-| Binary artifacts under `artifacts/` | 161 *added* | **2 380** *total* |
-| Archive placeholders / incomplete | not measured | **155 / 2** |
-| `certification-and-compliance.md` records | 0 | **32** |
-| `schematic-netlist.md` records | 0 | **5** |
-| Deletions on any file edited by the merge | **0** | **0** |
-| `HEAD` | `4aa02e10…` | **`4aa02e10…`, unchanged** — 91 staged paths intact |
-
-**The three new deltas are scope, not regression.** Round one validated only the artifacts *it
-added* and counted only the links it could reach; round two checked the whole tree.
-
-- **The one broken link is the same one round one reported** — the vendored upstream
-  `XIAO_Webcam/README.md → docs/…jpg?raw=true`, preserved as supplied and deliberately not
-  fixed, for the reason round one gave. **The round-two merge introduced no broken link**: an
-  intermediate check caught one forward reference of its own (to `deferred-round2.md`, written
-  later in the pass) and it was resolved before completion.
-- **All 3 magic-byte mismatches are pre-existing and benign**: three files named `*.png` in
-  `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/…/images/` are **JPEGs**
-  (`ff d8 ff db`), tracked since commit `cbfbff3`, vendored from a community example. They are
-  real images with the wrong extension — **not** an HTML error page saved as a document, which is
-  the failure this check exists to catch. Renaming them would be a delete-plus-add in a vendored
-  tree, so they are **reported, not repaired**.
-- **2 archive placeholders are incomplete**, both pre-existing:
-  `software/applications/crosspoint-reader/plugins/source-snapshots.ARCHIVED.md` (no hash, no
-  size, no original path — **in the live `software/` tree, not touched**) and
-  `devices/seeed-studio/…/TRANSLATIONS.ARCHIVED.md` (hash and size present, original path never
-  stated). **All 106 placeholders written by this pass are complete.**
-
-## R8. What round two still does not establish
-
-- **Still zero hardware claims.** §1's headline caveat is unchanged and applies to round two in
-  full. No board was purchased, powered, flashed or probed.
-- **CE, UKCA, SRRC, CCC, MIC and ISED remain unestablished for every device.** CE has no database
-  to search; the Chinese registers failed to connect (`000`); the Japanese register was reachable
-  (200) but form-driven and **not queried**; ISED returned 503. ⚠ **Those are method failures, not
-  absence findings**, and must not be read as "not approved".
-- **The `ID Label` exhibits were downloaded but never visually inspected for secondary marks.**
-  Whether a CE mark appears on Xteink artwork is open, and cheap to close.
-- **Schematics are permanently withheld on all 26 filings examined.** The FCC is not a route to a
-  schematic for any of these vendors.
-- **Marketplace, clone and used-market pricing is still unsampled.** AliExpress, eBay, Amazon,
-  Taobao and JD were all bot-walled or JS-shelled on 2026-09-11. ⚠ **A 200 response containing no
-  prices is a failure, not a data point** — §6's marketplace gap is **unchanged**.
-- **`fccid.io` is a mirror, not the FCC.** `apps.fcc.gov` returned 403 to all five user agents
-  tried, so none of the above was confirmed against the primary host.
-- **PaperMono was untouched in both rounds.** Its certification claims are now known to be stale
-  (`2AN3WM5PAPERMONO` exists, granted 2025-07-09), its richest-in-repository schematic is
-  untraced, and 11 of its FCC exhibits sit in scratch with no placeholder. All parked in
-  [`deferred-round2.md`](scratch/index-merge/deferred-round2.md) §1.
-- **§6's remaining bullets stand**: no net-level tracing was attempted for most of the LilyGO
-  family, and `components/canaan/k230`'s toolchain routes are still all `inferred`.
-
----
-
-*Round two compiled 2026-09-11. Method: [`.agents/skills/hardware-device-research/SKILL.md`](.agents/skills/hardware-device-research/SKILL.md).*
diff --git a/VERIFICATION-xiao-esp32s3-sense.md b/VERIFICATION-xiao-esp32s3-sense.md
index fdb1356..1eaa2a6 100644
--- a/VERIFICATION-xiao-esp32s3-sense.md
+++ b/VERIFICATION-xiao-esp32s3-sense.md
@@ -18,7 +18,7 @@ Research pass **2026-08-24**. All figures recomputed from the files on disk at c
 | Component records created | **9** (+1 updated); 1 unidentified part **resolved** |
 | Tools written | **9** Python scripts |
 | Media catalogued | 14 images |
-| Relocated to `../repo-archive` | **110 MiB** |
+| Relocated to `../hardware-doc-archive` | **110 MiB** |
 
 ## Automated checks
 
@@ -65,10 +65,10 @@ Four **exact-duplicate PDFs** were removed and replaced with `*.DUPLICATE.md` po
 |---|---|
 | `allowed` (CC BY-SA 4.0 — all schematics/KiCad) | 14 |
 | `conditional` | 1 |
-| **`restricted`** | **4** — OV3660/OV5640 datasheets and module specs |
+| **`prohibited`** | **4** — OV3660/OV5640 datasheets and module specs |
 | `unknown` | 23 |
 
-**13 artifacts >1 MB are flagged `review_required`** in `acquisition/manifest.json`. They remain staged per the user's explicit instruction to keep documents in place. The four `restricted` items carry OmniVision's clause *"Individuals and/or organizations are not allowed to re-distribute said information."*
+**13 artifacts >1 MB are flagged `review_required`** in `acquisition/manifest.json`. They remain staged per the user's explicit instruction to keep documents in place. The four `prohibited` items carry OmniVision's clause *"Individuals and/or organizations are not allowed to re-distribute said information."*
 
 ## Known limitations
 
diff --git a/VERIFICATION-xteink-round2.md b/VERIFICATION-xteink-round2.md
deleted file mode 100644
index ab4cadf..0000000
--- a/VERIFICATION-xteink-round2.md
+++ /dev/null
@@ -1,258 +0,0 @@
-# Verification — Xteink family, round 2
-
-> Research session **2026-09-11**. Scope: `devices/xteink/**`, the Xteink-specific
-> component records, and one append to `ai-crawler-site-access-table.md`.
-> Verifier: the authoring session (**self-audit**, as in round 1).
->
-> Supplements [`VERIFICATION-xteink.md`](VERIFICATION-xteink.md) (2026-09-04),
-> which is **not** modified by this pass.
-
-## Headline
-
-**The evidence position changed materially. The hardware-verification position
-did not.**
-
-Round 1's verdict named **source concentration** as this tree's principal
-weakness: for the X4 Pro and X4 Classic, essentially every technical claim traced
-to one repository at one commit, with no teardown, schematic or regulatory filing.
-
-| Device | Custodians 2026-09-04 | Custodians 2026-09-11 |
-|---|---:|---|
-| X4 Pro | **1** | **4** — FreeInk · a physically dumped unit · an on-hardware-tested firmware · **FCC `2BTR9-X4PRO`** |
-| X4 Classic | **1** | **3** — FreeInk · vendor listing + spec block · **FCC `2BTR9-X4C`**. Still **no board-level** second custodian |
-| X3 | teardowns + BOM | **+ public FCC internal photographs** |
-| X4 | teardown-free, one dump | **+ public FCC internal photographs** |
-
-**Still zero claims in this tree have been verified on hardware by this
-repository.** No Xteink device has been in anyone's hands here, in either pass.
-Every "confirmed" means *confirmed by a cited third party*.
-
-## 1. The primary question, answered
-
-**"Is there a new model between the X4 and the X4 Pro?"** — **Yes: the X4
-Classic, and it is the device already in this tree.** It launched
-internationally on **2026-09-06 19:57:20 −0700** at **US$79**, SKUs
-`X4Classic-gray` / `X4Classic-black`, read from the vendor's own
-`products.json`.
-
-**"X4 v2" is not a separate SKU.** The vendor's own product title is
-`XTEINK X4 Classic (X4 V2) Pocket eReader`; four accessory titles carry the same
-parenthetical; the product FAQ uses "X4 V2" in prose; and the vendor's Reddit
-announcement of 2026-09-03 reads *"X4 Classic (X4 V2) is coming soon."*
-
-**No other SKU exists between them.** `enum class Board` in the FreeInk SDK at
-HEAD (`9f4d3f9`, 2026-09-10) still contains exactly five Xteink entries;
-`"X4R1_CLA"` returns `total_count: 0` on GitHub code search; the vendor's
-device-only `machine` collection contains exactly X3, X4 Classic and X4 Pro.
-
-**A different new product was found**: **XTEINK X4 Light**, FCC ID `2BTR9-X4L`,
-granted 2026-08-13, unannounced and unlisted → [`devices/xteink/x4-light/`](devices/xteink/x4-light/README.md).
-
-## 2. Inventory
-
-| Area | Files added | Files extended |
-|---|---:|---:|
-| `devices/xteink/x4-classic/` | **13** | 9 |
-| `devices/xteink/x4-light/` | **2** (+3 PDFs) | — |
-| `devices/xteink/x4-pro/` | 1 (+2 PDFs) | 4 |
-| `devices/xteink/x3/` | 1 (+1 PDF) | 2 |
-| `devices/xteink/x4/` | (+1 PDF) | 1 |
-| `devices/xteink/README.md` | — | 1 |
-| `components/` | **1 new record** (`generic/kh3216-a35-chip-antenna`) + 6 PDFs | 7 |
-| `scratch/xteink/` | 4 authored + ~90 raw | 1 |
-| repository root | **1** (this file) | 1 (`ai-crawler-site-access-table.md`) |
-
-`devices/xteink/x4-classic/` went from **13 files to 26**: added
-`research-log.md`, `commands.md`, `community.md`, `projects-and-community.md`,
-`comparisons-and-recommendations.md`, `performance.md`,
-`product-history-and-family.md`, `resources-and-conflicts.md`,
-`examples/{catalog.json,search-log.md,best.md}`, `media/manifest.json`,
-`artifacts/certification/README.md` — and 5 FCC exhibit PDFs.
-
-## 3. Artifacts — validated by content, not extension
-
-**18 files, 26,856,032 bytes.** Every one validated `%PDF` by reading the first
-four bytes, and every PDF's own `Title` metadata checked against what it was
-believed to be.
-
-| Artifact | Bytes | SHA-256 (first 16) | Doc revision / date |
-|---|---:|---|---|
-| `2BTR9-XTEINKX3-internal-photos.pdf` | 869,708 | `b3affd56115e9c3e` | filed 2025-12-26, public 2026-06-24 |
-| `2BTR9-XTEINKX4-internal-photos.pdf` | 770,254 | `fd1623a7c9df42ba` | filed 2026-01-05, public 2026-07-04 |
-| `2BTR9-X4C-label.pdf` | 189,803 | `605b978782399a0f` | 2026-07-20 |
-| `2BTR9-X4C-test-report.pdf` | 3,214,822 | `ce40d2300f5ac63c` | 2026-07-20, 51 pp |
-| `2BTR9-X4C-antenna-report.pdf` | 1,548,468 | `720ce021f0d403a6` | spec V1.2 |
-| `2BTR9-X4C-rf-exposure.pdf` | 144,966 | `7004f25d9c721f88` | 2026-07-20 |
-| `2BTR9-X4C-confidentiality-request.pdf` | 121,559 | `6930195fcd9a7b0f` | 2026-07-20 |
-| `2BTR9-X4L-external-photos.pdf` | 3,485,136 | `c6457651f19b4cac` | 2026-08-13, 9 images |
-| `2BTR9-X4L-label.pdf` | 1,262,117 | `c5be3415bb656997` | 2026-08-13 |
-| `2BTR9-X4L-test-report.pdf` | 1,547,812 | `cbe8fc7409534f49` | `BKC26074010GE-2` |
-| `2BTR9-X4PRO-external-photos.pdf` | **5,317,690** | `2565de437321171c` | 2026-06-16, 7 images |
-| `2BTR9-X4PRO-label.pdf` | 1,169,828 | `3d404d1cefbfc39f` | 2026-06-16 |
-| `uc8253c-a-datasheet-rev0.6-…-elecrow-mirror.pdf` | 1,294,916 | `bee25538177b8cc6` | **`UC8253c_A` rev 0.6, 2020-10-13** |
-| `uc8179c-c-datasheet-rev0.6-…-crystalfontz-mirror.pdf` | 1,202,516 | `bf1dcef76e0d02a5` | **`UC8179c_C` rev 0.6, 2019-11-26** |
-| `esp32-c3-datasheet-en-v2.4.pdf` | 900,158 | `833fc000b4b3c3d3` | **Datasheet v2.4** |
-| `bq27220-datasheet-sluscb7a-rev-a.pdf` | 570,379 | `9fffe0b632cd287c` | **`SLUSCB7A` Rev A** |
-| `bq27220-technical-reference-manual-sluubd4-rev-a.pdf` | 2,768,446 | `44779f229423d649` | **`SLUUBD4` Rev A** |
-| `gt911-programming-guide-rev00-…-crystalfontz-mirror.pdf` | 477,454 | `60c6c2284b482a7a` | **Rev.00, 2014-08-04** |
-
-- **18 of 18 validated `%PDF`. 0 invalid.**
-- **0 HTML error pages retained under a `.pdf` extension** — two were caught
-  during retrieval and deleted (`uc8179-gooddisplay`, `uc8179-cf-517`).
-- **2 valid PDFs retrieved that were the wrong document** and were caught by
-  reading their `Title` metadata:
-  - `crystalfontz.com/controllers/UltraChip/UC8179/478/` → **GOODiX GT911
-    Programming Guide.** *Retained, refiled under `components/goodix/gt911/`,
-    because it is the right document for a different component.*
-  - `ti.com/lit/ug/sluubd2/sluubd2.pdf` → *"Using the TPS53317AEVM-726"*.
-    **Discarded.** The correct literature number is `SLUUBD4`.
-
-**Text-layer validation.** Every value transcribed from a PDF was cross-checked
-against a heading visible in the rendered page — the IC version and datasheet
-revision lines on the UltraChip covers, the `SLUSCB7A – MARCH 2016` stamp on the
-TI datasheet, the `Datasheet Version 2.4` line on the ESP32-C3 cover, and the
-`FCC ID: 2BTR9-X4C` header stamped on every page of the X4C exhibits. **No value
-was taken from an unvalidated text layer.**
-
-### One artifact fetched, verified and deliberately not retained
-
-The X3 CN OTA stock image, 6,254,064 B. Its SHA-256 **matched the Git-LFS oid
-exactly**, its first byte is `0xE9`, and its ESP header reads **`chip_id = 5` =
-ESP32-C3**. Not retained (proprietary, unknown licence); a **self-sufficient
-placeholder** carrying all four images' hashes, sizes and a verified
-no-`git-lfs` download recipe is at
-`devices/xteink/x3/artifacts/firmware/zocs-x3-stock-images.NOT-FETCHED.md`.
-
-## 4. Links
-
-| Check | Result |
-|---|---|
-| Markdown files walked | **138** |
-| Relative links resolved | **763** |
-| **Broken** | **0** |
-
-JSON: `examples/catalog.json` and `media/manifest.json` both parse.
-
-## 5. Append-only compliance
-
-**`devices/xteink/` is entirely untracked in git** (`??`), so
-`git diff -- <file> | grep -c '^-[^-]'` returns 0 trivially and proves nothing.
-A real check was therefore run against a pre-edit tar snapshot:
-
-```
-for f in <every pre-existing .md>:
-    n = wc -l < baseline/$f
-    diff <(head -n $n live/$f) baseline/$f
-→ append-only violations: 0
-```
-
-`scratch/xteink/round2-baseline/` holds the tar and the pre-edit line counts, and
-documents one caveat honestly: the tar was made *after* the first append to
-`devices/xteink/x4-classic/README.md`, whose pre-edit state is fixed instead by
-its captured line count (239) and the `---` rule at line 240.
-
-For the one **tracked** file appended to:
-
-```
-$ git diff -- ai-crawler-site-access-table.md | grep -c '^-[^-]'
-0
-```
-
-## 6. Git state
-
-| Check | Result |
-|---|---|
-| `HEAD` | **`4aa02e1030b3b0861e6fc34f23fa2113ec80d324`** — unchanged |
-| Staged paths | **91** — unchanged, and the sorted list hashes to the same `md5` as at session start |
-| State-changing git commands run | **none** — only `status`, `diff`, `log`, `rev-parse`, `ls-files`, `check-ignore` |
-| Protected files modified | **none** — `README.md`, `devices/README.md`, `components/README.md`, `vendors/README.md`, `artifact-manifest.md`, `software/README.md`, `guides/**`, `devices/m5stack/**`, `devices/lilygo/**`, `components/semtech/**` all untouched |
-
-Proposed edits to those files are staged, unapplied, in
-[`scratch/xteink/index-fragments-round2.md`](scratch/xteink/index-fragments-round2.md).
-
-## 7. Claim-to-source spot checks
-
-| Claim | Independent sources |
-|---|---|
-| X4 Classic launched 2026-09-06 at $79 | vendor `published_at` · vendor product page · 13 same-day community posts · a dated store review — **4** |
-| "X4 V2" = X4 Classic | vendor announcement · product title · 4 accessory titles · product FAQ · third-party firmware header · FCC product code — **6** |
-| X4 Classic has no frontlight | vendor spec block · vendor FAQ · FreeInk profile · 2 owner reviews — **4** |
-| X4 Classic charges by pogo, not USB-C | vendor spec block · FCC label photograph · accessory renaming · owner review — **4** |
-| X4 Classic has a QMI8658 IMU | FreeInk profile · **vendor "Shake-to-Flip"** · owner *"Shake to turn page"* — **3** |
-| X4 Pro is an ESP32-S3 with 8 MB PSRAM | FreeInk · **`esptool chip-id` on a physical unit** · **eFuse `PSRAM_CAP=8M`** · boot log — **4** |
-| X4 Pro I²C map (0x51, 0x5D, 0x63) | FreeInk · **live I²C trace on a physical unit** · Draftling — **3** |
-| X4 Light exists | **FCC grant `2BTR9-X4L`** · test report EUT name · external photographs — **3, all one filing** |
-| X3 is an ESP32-C3 | FreeInk · X4 dump chip-id · **X3 OTA image `chip_id = 5`** · teardown · BOM — **5** |
-| X4 Classic panel density unchanged at 219 PPI | vendor spec block · 2 owners, one correcting the other — **3** |
-| **`R2` in `ESP32S3_X4R2_CLA`** | **narrowed, not resolved** — three converging lines of evidence, no proof |
-
-## 8. Conflicts recorded rather than resolved
-
-| # | Conflict | Where |
-|---|---|---|
-| R2-C1 | The X4C product page lists two **different** supported-format sets, in the spec block and the FAQ | `x4-classic/gaps-and-conflicts.md` |
-| R2-C2 | Vendor says "4.3 inch"; everything else says 4.26″ | same |
-| R2-C3 | The FAQ refers to an *"E-ink secondary screen on the back"* that does not exist | same |
-| R2-C4 | Two reviewers report better contrast; density is provably unchanged; mechanism unknown | same |
-| R2-C5 | US$79 store price vs €89 reported by an EU buyer the same week — not normalised | same |
-| **R2-C6/P1** | **X4 Pro touch orientation**: FreeInk says "confirmed by corner-tap"; Draftling says the same values put touches **180° out** and corrected them **on hardware**; the emulator repeats FreeInk | `x4-pro/gaps-and-conflicts.md` |
-| R2-P-ver | **Four** stock-firmware version numbers for one X4 Pro: 7.2.4 (hardware-read), 7.4.4, V7.4.5, 7.5.4 | `x4-pro/factory-firmware.md` |
-
-## 9. Refuted, narrowed and confirmed
-
-| Hypothesis | Outcome |
-|---|---|
-| "A new SKU sits between the X4 and the X4 Pro" | **True, and it is the X4 Classic** — already in this tree, now launched |
-| "X4 v2 is a separate future product" | **Refuted.** It is the vendor's own alias for the X4 Classic |
-| "X4 Plus / Air / Lite / X4S / X4 Max" | **No evidence for Plus, Air, S or Max.** "Light" **exists** — as `2BTR9-X4L`, a *sixth* device, not a name for the X4 Classic |
-| "`R2` implies an undocumented X4C revision 1" | **Narrowed.** The tags are a shared-codebase enum; `"X4R1_CLA"` returns 0 hits; there is no earlier X4C grant; vendor and owners both call the plain X4 "V1" |
-| "The X4 Classic has a frontlight" (community, June–September) | **Refuted by the vendor's own spec block.** Round 1's firmware-based claim was right |
-| "Shopify collection handles are the tightest available product list" | **Superseded.** The **FCC grantee code** is tighter, and it found a device the handles did not |
-
-## 10. Known gaps in this verification
-
-- **Self-audit.** No independent verifier.
-- **Nothing built, nothing measured, no hardware.** `examples/catalog.json`
-  contains zero locally-built entries.
-- **31 retained board photographs were not read.** One image of 31 was opened.
-  Four unidentified parts and the X3 RTC three-way conflict are waiting on them.
-- **Three datasheets remain genuinely unobtainable**: UC8279 (12 sources tried),
-  CW2017 (**absent from CellWise's own catalogue**), BL8075 (vendor site dead).
-- **Chinese marketplaces were not searched.** The X4 Classic's Chinese launch
-  date and price are unknown, and no figure in this tree claims otherwise.
-- **The X4 Classic has no `features/` guides.** Its `features/` directory holds
-  only a `README.md`. Called out in `coverage.md` rather than quietly left.
-- **`web.archive.org` CDX was not retried**; the withdrawn X4 pages are still
-  unrecovered.
-
-## 11. User decisions still needed
-
-Listed in full in
-[`scratch/xteink/index-fragments-round2.md`](scratch/xteink/index-fragments-round2.md) §5.
-
-1. **`gt911-programming-guide-*.pdf`** declares itself *"GOODIX CONFIDENTIAL …
-   distribution … strictly prohibited"*. Keep unstaged, archive with a
-   placeholder, or delete the bytes?
-2. **UC8253 / UC8179 datasheets** are marked *"for TFT module use only"*.
-3. **`2BTR9-X4PRO-external-photos.pdf`, 5.3 MB** — largest file added.
-4. **12 FCC exhibits, 17.9 MB**, all redistribution status `unknown`.
-5. **X3 stock images, 56.6 MB** — currently `reference-only` with a verified
-   recipe.
-
-**Nothing was staged or committed by this session.**
-
-## 12. Verdict
-
-The primary question is answered from the vendor's own API and a federal
-regulatory record, with the date, price and SKUs read from machine-readable
-fields rather than prose. The X4 Classic record is now the depth of the X3
-record. The X4 Pro's single-source weakness is substantially repaired — though
-its **panel pinout specifically** is still single-source, and that is stated in
-the record rather than glossed.
-
-The tree's honest limitation is unchanged and worth repeating: **nothing here has
-been verified on hardware by this repository, and the three most decisive
-documents in the whole subject — the internal photographs of the X4 Pro, the X4
-Classic and the X4 Light — are embargoed until 2026-12-12, 2027-01-16 and
-2027-02-09 respectively.** Those dates are recorded in each record so the next
-session can simply re-check.
diff --git a/VERIFICATION-xteink.md b/VERIFICATION-xteink.md
deleted file mode 100644
index 9656784..0000000
--- a/VERIFICATION-xteink.md
+++ /dev/null
@@ -1,285 +0,0 @@
-# Verification — Xteink device family
-
-> Research session **2026-09-04**. Scope: `devices/xteink/**` plus the component
-> records created or extended for it. Verifier: the authoring session (self-audit).
-
-## Headline
-
-**Zero claims in this tree were verified on hardware by this session.** No Xteink
-device was available. Every hardware statement is either reverse-engineering
-evidence produced by a third party (the FreeInk SDK), a teardown photograph, a
-parsed firmware image, a vendor API response, or a labelled community report.
-
-That is stated first because it is the most important limitation of the whole
-body of work.
-
-## 1. Inventory
-
-| Area | Files |
-|---|---:|
-| `devices/xteink/` | **112** |
-| `components/ultrachip/` (index + uc8253, uc8179, uc8279) | 4 |
-| `components/cellwise/` (index + cw2017) | 2 |
-| `components/espressif/esp32-c3/` | 1 |
-| `components/texas-instruments/bq27220/` | 1 |
-| `components/unidentified/xteink-x3-x4/` (index + 4 parts) | 5 |
-| **Total authored** | **125** |
-
-Per device: `x4-pro` 33 · `x3` 29 · `x4` 28 · `x4-classic` 13 · `s4` 7 ·
-`nano` 1 · family index 1.
-
-Byte total for `devices/xteink/`: **536,576 B** of authored Markdown/JSON
-(excludes symlinks into the archive).
-
-## 2. Artifacts — validated by content, not extension
-
-| Artifact | Bytes | Magic | SHA-256 | Result |
-|---|---:|---|---|---|
-| `xteink-x4-oem-full-flash-16mb.bin` | 16,777,216 | first byte `0xE9` = ESP image | `b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245` | **valid** |
-| X3 teardown, Imgur set | 19,513,196 | 13 files, all `FF D8 FF` | per-file, in placeholder + `manifest.json` | **valid** |
-| X3 teardown, `sunwoods` set | 5,034,272 | 10 files, all `FF D8 FF` | per-file, in placeholder | **valid** |
-
-- **23 of 23 JPEGs** validated by magic bytes. **0 invalid.**
-- **0 files** found to be HTML saved under a `.bin` / `.jpg` / `.pdf` extension.
-- The flash image's chip-id field independently reads **5 = ESP32-C3**,
-  corroborating the SoC family from a second, machine-readable direction.
-
-### Archive integrity
-
-```
-python3 tools/archive_artifact.py --repo-root . --manifest … --verify
-  → verified 3, missing 0, drifted 0
-```
-
-Three-link chain confirmed for all three archived artifacts: placeholder at the
-former path ✅ · symlink resolving through this repo's own `archive/` link ✅ ·
-cited from the owning device record ✅.
-
-`tools/audit_archive.py` flags the Imgur set as **"[no repo]"** — correct and
-expected: it is an Imgur album, not a repository. Its placeholder carries **two
-independent hosts** (`imgur.com` and `old.reddit.com`), satisfying the two-source
-rule.
-
-## 3. Links
-
-| Check | Result |
-|---|---|
-| Markdown files checked | 123 |
-| Relative links resolved | **650** |
-| **Broken** | **0** |
-
-Two broken links were found and fixed during verification
-(`x4-pro/acquisition/README.md` → `../gaps-and-conflicts.md`;
-`x4-pro/features/buttons.md` → a non-existent `x3/features/buttons.md`).
-
-**One pre-existing broken link was found and deliberately not fixed:**
-`components/generic/bm8563/README.md` links twice to
-`../../nxp/pcf8563/README.md`, which does not exist — `components/nxp/pcf8563/`
-contains only an `artifacts/` directory. That file belongs to a concurrent
-session; the breakage predates this work and repairing another session's prose was
-out of scope. **Reported, not repaired** — see
-`scratch/xteink/index-fragments.md`.
-
-## 4. JSON
-
-All 6 machine-readable manifests parse: five `acquisition/manifest.json` and one
-`examples/catalog.json`.
-
-## 5. Evidence-label census
-
-Occurrences of each status label across the tree:
-
-| Label | Count |
-|---|---:|
-| `hardware-confirmed` (**by a cited third party**, never by this session) | 39 |
-| `reported-working` | 52 |
-| `inferred` | 38 |
-| `executed-success` (**research commands only** — fetches, parses, hashes) | 27 |
-| `not-attempted` | 19 |
-| `PENDING` (carried from the source's own annotation) | 13 |
-| `not-tested` | 6 |
-| `executed-failed` (preserved with diagnosis) | 3 |
-
-**Claims hardware-tested by this session: 0.** Every `executed-success` refers to
-a network fetch, a file parse, a hash or an archive operation — none touched an
-Xteink device.
-
-## 6. Claim-to-source spot checks
-
-| Claim | Independent sources |
-|---|---|
-| X3/X4 SoC is ESP32-C3 | FreeInk profile · **flash-image chip-id 5** · English teardown caption · Chinese BOM — **4** |
-| 16 MB flash | FreeInk · **exact image length** · both teardowns — **4** |
-| X3 ~257 PPI | vendor *"250+ PPI"* · **arithmetic from 792×528 / 3.7″** — **2, one derivable** |
-| X4 ~219 PPI | owner-measured *"220 ppi"* · **arithmetic from 800×480 / 4.26″** — **2** |
-| QMI8658 @ 0x6B | `BoardConfig.h` · `XteinkDetect.cpp` · Chinese BOM — **3** |
-| BQ27220 @ 0x55 | `BoardConfig.h` · `XteinkDetect.cpp` · Chinese BOM — **3** |
-| X4 delisted | vendor API absence · **all 4 accessory SKUs sold out** · owner statement — **3** |
-| X3 NFC tag is a writable passive tag | CrossInk maintainer statement · 3 firsthand owner reports · Chinese BOM — **5** |
-| **X3 RTC part** | **3 sources, 3 different answers — recorded as unresolved, not resolved by preference** |
-
-## 7. Conflicts recorded rather than resolved
-
-| # | Conflict | Where |
-|---|---|---|
-| 1 | X3 RTC: `DS3231` (firmware) vs `DS1307` (teardown caption) vs `DS-series` (Chinese BOM) | `x3/gaps-and-conflicts.md` |
-| 2 | X3 GPIO0 and GPIO20 each assigned **two** roles in the same SDK commit | `x3/gaps-and-conflicts.md` |
-| 3 | X4 Pro touch `flipY`: the SDK header says "confirmed", its own doc says "pending" — **twice** | `x4-pro/gaps-and-conflicts.md` |
-| 4 | X4 Pro firmware version: app descriptor `7.4.4` vs package metadata `V7.4.5` | `x4-pro/factory-firmware.md` |
-| 5 | X4 dimensions: 74 g / 5.9 mm (2025) vs 80 g / ~7 mm (2026) | `x4/gaps-and-conflicts.md` |
-| 6 | S4 price: ¥339 ≈ US$47 vs an AliExpress *"~$99"* | `s4/gaps-and-conflicts.md` |
-| 7 | S4 owner reports *"running crosspoint"* — impossible on Android | `s4/gaps-and-conflicts.md` |
-| 8 | X4 Classic reported with a frontlight by the community; firmware says none | `x4-classic/gaps-and-conflicts.md` |
-| 9 | X3 community price $79 vs vendor API $69 | `x3/gaps-and-conflicts.md` |
-
-## 8. Refuted hypotheses, preserved with their evidence
-
-| Hypothesis | Refuted by |
-|---|---|
-| I²C `0x63` on the X4 Pro is a display PMIC with dead rails | A register dump showing the CW2017's BATINFO curve |
-| The X4 Pro uses an ADC button ladder | A pull-up edge test; the ladder matcher is vestigial firmware |
-| X4 Pro GPIO7 is a display enable | It reads `INPUT_PULLUP` — it is the Right button |
-| An "X5" exists | 8 mentions, all speculation; one author self-corrected to "X4" |
-| "X4 Mini" is a SKU | 6 uses, all colloquial; a video so titled names *"the XTEINK X4"* in its body |
-| The X4 "runs Linux" | The dump is an Arduino/ESP-IDF 4.4.7 image on an MMU-less RISC-V core |
-| A UC8179 always reports `CHIP_VER != 0` | A shipping X4 Pro returned `VER = 00 00 01 FF FF` |
-
-## 9. Confirmed-correct existing documentation
-
-- `software/applications/crossplay/README.md` correctly identified the X4 Pro as
-  ESP32-S3 with 480×800 touch and a frontlight, and correctly identified the
-  C3-image-onto-S3 OTA hazard. **Verified against the board profile; no
-  correction needed.**
-- **One prior statement is superseded:** the PaperMono record described the X4 Pro
-  as a device on which *"You cannot put your own application on it."* That is
-  incorrect — see `x4-pro/comparisons-and-recommendations.md`. The correction is
-  recorded in the Xteink tree and, because `devices/m5stack/**` is owned by
-  another session, is **proposed** in `scratch/xteink/index-fragments.md` rather
-  than edited in place.
-
-## 10. Shared files
-
-**No shared or protected file was modified.** Confirmed by path-scoped
-`git status` and by mtime: `README.md`, `devices/README.md`,
-`components/README.md`, `vendors/README.md`, `artifact-manifest.md`,
-`software/README.md`, `guides/markets/*` and `devices/m5stack/**` carry **no
-modification from this session**. Proposed additions to them are staged as
-ready-to-paste Markdown in `scratch/xteink/index-fragments.md`.
-
-Five **existing** component records were **appended to** (Used By sections only,
-no existing text altered), each after confirming `find <file> -mmin -30` was
-empty: `solomon-systech/ssd1677`, `goodix/gt911`, `qst/qmi8658a`,
-`espressif/esp32-s3r8`, `generic/bm8563`.
-
-## 11. Known gaps in this verification
-
-- **No example was built or statically validated.** No toolchain was installed.
-- **Component datasheets were not retrieved** for the UC8253/UC8179/UC8279,
-  CW2017, BQ27220 or ESP32-C3. Each record marks its datasheet
-  `not-attempted` and gives the URL where known.
-- **Bundled upstream Markdown was not link-checked** — none is vendored.
-- Chinese marketplaces, Xiaohongshu, Bilibili and regulatory databases were
-  **declared exclusions**, not exhausted searches.
-- This is a **self-audit**. No independent verifier reviewed the work.
-
-## 12. Verdict
-
-The tree is internally consistent, fully cross-linked, artifact-validated and
-honest about its evidence class. Its principal weakness is **source
-concentration**: for the X4 Pro and X4 Classic, essentially every technical claim
-traces to one repository at one commit
-(`Free-Ink/freeink-sdk` @ `24003795381a6c23630a26472ae3b06550333e71`), with no
-teardown, schematic or regulatory filing to corroborate it. That is stated in each
-of those records rather than papered over.
-
----
-
-# ⚠ Round-two correction, 2026-09-11 — the regulatory findings are refuted
-
-**Nothing above this line has been edited.** A verification report that quietly rewrites itself
-is worthless; the original text stands and this section supersedes the parts named below.
-
-Round two of this sweep ran on **2026-09-11**. Full report:
-[`VERIFICATION-xteink-round2.md`](VERIFICATION-xteink-round2.md). Certification detail, with
-controls: `devices/xteink/<record>/certification-and-compliance.md`.
-
-## C1 — "regulatory databases were declared exclusions" (§11)
-
-> *"Chinese marketplaces, Xiaohongshu, Bilibili and regulatory databases were **declared
-> exclusions**, not exhausted searches."*
-
-Accurately stated at the time, and the exclusion has now been lifted. The US FCC database **was**
-searched on 2026-09-11, with positive and negative controls. Result below.
-
-## C2 — "no … regulatory filing to corroborate it" (§12)
-
-> *"…with no teardown, schematic or regulatory filing to corroborate it."*
-
-**Refuted on two of three counts.**
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**,
-grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment
-authorisations** — one for every ESP32-based device in this tree, plus one for a device this
-repository did not know existed:
-
-| FCC ID | Granted | Device | Record |
-|---|---|---|---|
-| `2BTR9-X4L` | **2026-08-13** | XTEINK X4 Light | [`x4-light`](devices/xteink/x4-light/README.md) — **new, found by grantee enumeration** |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic | [`x4-classic`](devices/xteink/x4-classic/README.md) |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro | [`x4-pro`](devices/xteink/x4-pro/README.md) |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 | [`x4`](devices/xteink/x4/README.md) |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 | [`x3`](devices/xteink/x3/README.md) |
-
-- **Regulatory filing: exists.** Five of them.
-- **Teardown: exists.** The `2BTR9-XTEINKX4` filing's **Internal Photos** were never withheld.
-  They are the **first public teardown of the Xteink X4** and are now held at
-  [`devices/xteink/x4/artifacts/certification/`](devices/xteink/x4/artifacts/certification/README.md).
-  The X3's are public too. The X4 Pro's unlock **2026-12-12**.
-- **Schematic: still absent, permanently.** All five filings hold Schematics, Block Diagram and
-  Operational Description under **long-term** confidentiality. **The FCC is not a route to an
-  Xteink schematic**, and never will be.
-
-So §12's source-concentration verdict is **half repaired**: the X4 Pro still traces
-substantially to one commit, but it now has an independent regulatory record and a dated
-teardown release.
-
-## C3 — the underlying error, stated plainly
-
-The 2026-09-04 pass confused **"no mark visible in a product photograph"** with **"no grant
-exists"**. Only the first was ever tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark — ordinary for a
-device with a screen. **Likely, and not verified.**
-
-**Why it was missed, and the transferable lesson:** the 2026-09-04 pass searched by *product
-name*. Xteink's grants are filed under model codes (`XTEINKX3`, `X4PRO`, `X4C`) that a product
-search does not reach. **Enumerating the vendor's FCC grantee code returns its complete
-certified product list, including devices it has never announced** — which is how the X4 Light
-was found. That technique generalises to every vendor in this repository and is written up in
-[`guides/research/finding-certification-records.md`](guides/research/finding-certification-records.md).
-
-## C4 — what is *not* corrected
-
-The controls that make these findings meaningful, and the limits that remain:
-
-| ID probed | HTTP | Role |
-|---|---|---|
-| `2BTR9-XTEINKX4` · `2AC7Z-ESPS3WROOM1` · `2AN3WM5CARDPUTER` | **200** | positive |
-| `2AN3WM5CARDPUTERZERO` · `2ASYE-T-DISPLAY-K230` · `2ZZZZNOSUCHGRANTEE` | **404** | negative, invented |
-
-- **Still zero hardware claims.** §5's "Claims hardware-tested by this session: 0" is unchanged
-  and remains true of round two.
-- **CE, UKCA, SRRC, CCC, MIC and ISED are still not established.** CE has no database to search;
-  the Chinese registers failed to connect; the Japanese one was reachable but not queried.
-  **Those are not negative results.**
-- **`fccid.io` is a mirror, not the FCC.** `apps.fcc.gov` returned 403 to all five user agents
-  tried, so no confirmation against the primary host was obtained.
-- **No FCC grant exists for the [S4](devices/xteink/s4/README.md) or the
-  [Nano](devices/xteink/nano/README.md)** — an absence against a *complete* grantee enumeration
-  with passing controls, which is the strongest form this evidence takes.
-
-Every correction above is listed in
-[`scratch/index-merge/corrections-requiring-review.md`](scratch/index-merge/corrections-requiring-review.md).
diff --git a/ai-crawler-site-access-table.md b/ai-crawler-site-access-table.md
index ec9dd70..8aa5b96 100644
--- a/ai-crawler-site-access-table.md
+++ b/ai-crawler-site-access-table.md
@@ -380,36 +380,14 @@ Tested 2026-08-21 while researching the Espressif ESP32-U4WDH.
 | `shopkits.eink.com` | ✅ 200 | ⚠️ **The only E Ink property that emits real data.** E Ink's own kit store: per-part specification tables (resolution, active area, pixel pitch, outline, weight, grey levels, ppi, backplane) plus downloadable user manuals. Patterns: `/en/product`, `/en/product?cate=Black%26White`, `/en/product/detail/<desc>(<PART>)`, `/en/download/<opaque-id>/<file>.pdf`, `/en/product/detail/CompatibilityTable`. **~91 SKUs, evaluation kits only** — most production AMEPD panels are absent. Business accounts only for purchase |
 | `www.panelook.com` | ❌ **slider CAPTCHA** | Tested 2026-08-24, with and without a Chrome 131 UA: both a direct parameter URL and `modelsearch.php?keyword=` returned **HTTP 200 with an 11,210-byte drag-slider challenge page** ("Please hold down the left slider and drag it to the right"). ⚠ **200 + a plausible size, so a naive scraper records success.** This is the database that indexes E Ink/LCD panel part numbers with parameters, so its loss is expensive — no workaround found |
 | `inkplate.readthedocs.io` | ✅ 200 (**useless**) | ⚠️ **Deprecated — every page is a JavaScript redirect shim** to `soldered.com/documentation/inkplate`. `curl` returns 200 and almost no content. **Use the `.rst` source** in `github.com/SolderedElectronics/Inkplate-documentation` (`source/*.rst`, ~10,000 lines) instead |
-| `www.awinic.com` (Shanghai Awinic) | ✅ 200 | **Works with a plain Chrome UA, no login.** Datasheets are not linked directly. Recipe: `GET /{cn,en}/productDetail/<FULL-ORDERING-PART>` (⚠ the **full** part — `AW35122FDR`, not `AW35122`, which silently returns the home page at 244,993 bytes); read `data-file-url="doc/<YYYYMM>/<uuid>.pdf"` and `data-doc-title="DS_…"` out of the HTML; then fetch `/{cn,en}/download?file=<urlencoded>&fileName=<urlencoded>`. Four datasheets retrieved this way 2026-09-01, all `%PDF`. The page's *Technical documentation* table also shows the document version and date, so you can confirm the revision before downloading |
-| `www.joulwatt.com` (Joulwatt / 杰华特) | ✅ 200 (**HTTPS only**) | ⚠ `http://www.joulwatt.com/` **times out**; `https://` works. Site is a JS SPA, but the backend is wide open: `GET https://www.joulwatt.com/jwt/web/product/list?pageSize=3000` returns **all 1,564 products** as one 4.4 MB JSON, with bilingual descriptions, a parametric `cols` field, and a `datesheetFileSite` path per part. Files resolve at `https://www.joulwatt.com/jwt/profile/<datesheetFileSite>` — the path contains Chinese characters (`规格书`) and must be percent-encoded. ⚠ **The served datasheet may be an image-only scan** (JW5712: 4 pages, zero text layer) |
-| `www.xmcwh.com` (XMC / Wuhan Xinxin) | ✅ 200 | Product table is JS-rendered and the search parameters are ignored. `POST /product/getProductList` with `page=1&limit=500` returns **the entire 519-part catalogue** as JSON regardless of any keyword; filter client-side. Each record's `form_data.picture` holds either a direct path (`/uploads/<id>/<PART>_VerX.Y.pdf`) or a `/site/support?...` link. ⚠ The page's own JavaScript carries a **commented-out** branch that would suppress downloads for the `XM25UH` family — availability has evidently changed before |
-| `www.siproin.com`, `www.siproin-ic.com` (Shanghai Siproin) | ✅ 200 | **Two independent hosts serve byte-identical datasheets** — `siproin.com/uploads/Datasheets/<category>/<PART>_DATASHEET_V<x.y>_E.pdf` and `siproin-ic.com/wp-content/uploads/<YYYY>/<MM>/<same-file>`. Unusually good redundancy for a small Chinese vendor. Plain Chrome UA, no login |
-| `www.awinic.com` doc CDN, `m5stack-doc.oss-cn-shenzhen.aliyuncs.com`, `m5stack.oss-cn-shenzhen.aliyuncs.com` | ✅ 200 | M5Stack's Aliyun OSS asset buckets. Fully open, `application/pdf`, plain Chrome UA. ⚠ **Asset folders are numeric and shared across products** — the PaperMono's BMI270 datasheet is served out of `/resource/docs/products/app/Stamp Fly/`, and the Puya PY32L020 datasheet sits in `/1205/` beside `ST25R3916_EN.pdf` **without being linked from any PaperMono page**. Worth listing a folder's siblings when you find one useful file |
-| `www.orientdisplay.com` | ❌ **403 to everything tried** | Chrome 131, Safari 17, WhatsApp **and** ClaudeBot UAs all returned 403 on `/wp-content/uploads/2022/08/FT6336G_v1.0.pdf` (2026-09-01) |
-| `focuslcds.com` | ⚠️ **403 to browsers, 200 to ClaudeBot** | ⚠️ **Inverted block, and the inversion is UA-specific in an unusual direction.** Tested 2026-09-01 on `/wp-content/uploads/Drivers/FT6336G.pdf`: Chrome 131 → 403, WhatsApp → 403, Safari 17 → 403, **`Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ClaudeBot/1.0; +claudebot@anthropic.com` → 200, `application/pdf`, 477,869 B, `%PDF` ✓.** A WordPress WAF that allows declared crawlers while blocking generic desktop agents — the opposite of the usual pattern. **Rotate to the declared-crawler UAs before giving up on a display-vendor mirror** |
-| `www.lcsc.com`, `datasheet.lcsc.com`, `wmsc.lcsc.com`, `so.szlcsc.com` | ⚠️ **200 + HTML for `.pdf` URLs** | ⚠️ Re-confirmed 2026-09-01. `www.lcsc.com/search?q=<anything>` returns an **identical 97,240-byte JS shell for every query**, so search is unusable. `www.lcsc.com/datasheet/<file>.pdf` returns **HTTP 200 with `text/html`** (47,427 B for the IP2315). `wmsc.lcsc.com/ftps/wm/search/global` → **403**. `so.szlcsc.com` → **203 + a JS anti-bot challenge**. `item.szlcsc.com/search` → `{"code":500}`. **Check `%PDF` magic bytes, never the status code**, and prefer the manufacturer's own host — Awinic, Joulwatt, XMC and Siproin all served their own datasheets directly this session |
-| `www.semtech.com` | ✅ 200 | **Open, and the standard UA fallback is *wrong* here.** Tested 2026-09-04: Chrome 131 → 200; **bare `curl/8.0.1` → 200**; ClaudeBot → 200; ⚠ **`WhatsApp/2.23.20.0` → 403 (919 B).** Honest hard 404s (103,374 B) for missing product pages and sitemaps, so paths are safely probeable. ⚠ **But one subtree soft-404s:** `/uploads/documents/<anything>.pdf` returns **HTTP 200 with 21,149 B of HTML** titled *"Find Product Documentation"* — for real *and* invented filenames alike. That is the retired legacy datasheet store, so **every `semtech.com/uploads/documents/DS_*.pdf` link in older blogs, READMEs and citations is dead and none of them looks dead.** `/uploads/common/` and `/uploads/technology/` are live and 404 honestly |
-| **`semtech.my.salesforce.com`** | ⚠️ **200 for everything, bytes for nothing** | ⚠️ **Where every Semtech datasheet, app note, errata and reference design actually lives — and it is `blocked` for automated clients.** `GET /sfc/p/<org>/a/<rec>/<token>` → 200 + a 1,359-byte self-POSTing shell; reproducing the POST to bare `/sfc/p/` (⚠ the form action contains a `#`, so the fragment is stripped) → 200 + a 53,747-byte **Lightning Out** bootstrap; `/sfc/ld/…` → 550 B *"Unable to Process Request"* by GET, POST, `/app.js` and `/aura`; `/sfc/dist/version/download/?oid=…&d=…` → **200 `application/json`, zero bytes** (wants an `ids=<ContentVersionId>` only the Aura round-trip yields). **The decisive negative control: an invented token also returns HTTP 200**, 1,363 B — four bytes different from a valid one. This endpoint cannot be probed at all. **Use a distributor mirror.** Full trace: `vendors/semtech/README.md` §4 |
-| `semtech.my.site.com` / ⚠ `semtech.force.com` | ✅ 200 / ❌ **404** | The **mySemtech Document Portal** login wall. `my.site.com/DP/DP_CommunityLogin?docId=<18-char SF Id>` → 200 + a login page for valid **and** bogus ids (322,432 vs 322,006 B), so it tells you nothing about existence either. ⚠ **`semtech.force.com` is dead** — 404 *"URL No Longer Exists"* (1,972 B) for every `docId` — yet **103 entries in Semtech's own document catalogue still point at it**. **Recovery: swap the host, keep the `docId`** (`sed 's/semtech\.force\.com/semtech.my.site.com/'`), verified 2026-09-04. Scope of the wall: 223 of 1,984 catalogue entries, overwhelmingly Reliability Reports (48 of 54) and Signal-Integrity parts. ⭐ **Zero LoRa documents are behind it** |
-| ⭐ `www.semtech.com/design-support/development-support-documents/` | ✅ 200 | **The enumeration key for this whole vendor.** An 805,220-byte page carrying an inline `var doc_portal = {…}` JSON object with **1,984 document entries** — platform, category, description, `DatePosted` (2018-11-14 … 2026-08-25) and URL for everything Semtech publishes. Server-rendered, no JS needed, one request. Parse with `json.JSONDecoder().raw_decode()` (there is trailing JS, so a naive `json.loads` of a regex capture fails). ⚠ Duplicate rows are normal — one datasheet appears 3× with different tokens, one per platform tag — and **one row has a description string in its `URL` field**, so validate `URL.startswith('http')` |
-| **`mm.digikey.com`** | ✅ 200 | ⚠️ **Corrects the blanket "digikey.com ❌ 403" row above — it is host-specific, not domain-wide.** Digi-Key's *media* host serves manufacturer datasheets openly to **any** UA: `mm.digikey.com/Volume0/opasdata/d220001/medias/docus/<dir>/<num>_<Name>.pdf` → 200, `application/pdf`, `%PDF` (5,809,234 B for the Semtech LR20xx datasheet, 2026-09-04). **Negative control → real 404** (3,340 B), so this host is honest and probeable. ⚠ `<dir>`/`<num>` are opaque Digi-Key ids and are **not derivable** — harvest the full URL from a search engine or a Digi-Key product page. **Best-behaved semiconductor-datasheet mirror found to date** |
-| **`www.mouser.com/pdfDocs/`** | ⚠️ **403 to Chrome, 200 to WhatsApp** | ⚠️ **Inverted block, and it partially corrects the "mouser.com — no working UA found" row above.** `www.mouser.com/c/?q=` is still Access-Denied (13,895 B) to every agent, **but the `pdfDocs` endpoint serves `WhatsApp/2.23.20.0`**: `pdfDocs/61979758LR2021_V1_1_datasheet.pdf` → Chrome **200 + 13,895 B of HTML** (⚠ a captcha page with a `.pdf` URL — the classic silent corruption), WhatsApp → **200, `application/pdf`, 5,158,757 B, `%PDF` ✓** (2026-09-04). Negative control: a guessed filename → **403, 1,140 B**. The numeric filename prefix is Mouser's opaque doc id and must be found via a search index |
 
 - Findings:
   - **2026-08-24 — always probe a deliberately bogus path as a negative control before trusting a 200.** Vendor hosts fall into three classes, and you cannot tell which from a single successful request: (a) **honest** — real 404s, so a 200 means the document exists (TI, AOS, Bosch); (b) **soft-404** — 200 with a smaller body for missing pages (SGMicro: 590 KB real vs 69 KB missing); (c) **uniform SPA shell** — byte-identical 200 for every path, existing or not (WCH: 4,305 bytes). Class (c) will make you record "datasheet retrieved" for a file you never got. One bogus-path request settles it.
   - **2026-08-24 — the standard UA-substitution fallback is not universally safe.** `nxp.com` inverts it: the default `curl` UA is allowed and every browser and bot UA tried returns 404. When a *major* vendor 404s its own homepage, suspect UA filtering in **either** direction and try the bare default before escalating.
   - **2026-08-24 — some manufacturers publish no part data at all, and their website will not tell you so.** `eink.com` returns a byte-identical 204 KB SPA shell for every path including invented part URLs, which reads as "the page exists, my extractor is broken." It is neither. E Ink distributes panel specifications only under NDA — their own leaked spec documents say so on page 1 — and the corporate site contains **zero** part numbers. When a vendor's site looks like it should have a catalogue and does not, consider that the absence is the business model, and go to (a) the **board vendor's open design files** for the connector pinout, (b) the **board vendor's driver source** for the protocol, and (c) the manufacturer's own **evaluation-kit store** (`shopkits.eink.com`), which is often the one place real numbers are published.
   - **2026-08-24 — check `archive.org/wayback/available` BEFORE submitting a save.** `web.archive.org/save/<url>` timed out at 120 s and then returned **HTTP 503** on retry, which reads as "archival failed." But the one-line JSON API `https://archive.org/wayback/available?url=<url>` answered instantly and showed a snapshot **already existed** — and fetching it returned a **byte-identical** file (same SHA-256) to the live one. The availability API is fast, unauthenticated and never rate-limited in the way `save/` is. Query it first; only submit a save if it comes back empty.
-  - **2026-09-11 — ⚠ CORRECTION to the bullet above: `archive.org/wayback/available` returns FALSE NEGATIVES. Never trust an empty result.** It reported `{"archived_snapshots": {}}` for `cs.helsinki.fi/u/kutvonen/index_files/linus.pdf` (Linus Torvalds' 1997 master's thesis) in two separate sessions — while the **CDX API, queried the same minute, listed continuous captures from 2018-05-11 to 2026-08-07**. The advice to "query it first" still holds for speed, but **a negative from it means nothing**: confirm absence with `https://web.archive.org/cdx/search/cdx?url=<url>&output=json` before concluding a URL is unarchived or submitting a save. This failure mode is especially bad because it fails *toward* phantom link-rot — it will have you "rescuing" documents that were never at risk.
-  - **2026-09-11 — the CDX `length` field is the WARC record length, not the payload size.** Three captures of one unchanged file reported 422,587 / 418,490 / 438,660 bytes. **Never compare `length` to a file size.** Compare the `digest` instead — it is a base32 SHA-1 of the payload, directly checkable against a local copy: `python3 -c "import hashlib,base64;print(base64.b32encode(hashlib.sha1(open('f.pdf','rb').read()).digest()).decode())"`. This proved the archived Torvalds thesis byte-identical to the live file (`ZVCIUY5JU6PJW3CN37K277F2Z4HLXYPV`).
-  - **2026-09-11 — `web.archive.org` throttling flaps, and rotating UAs during a flap records phantom "working agents".** There is no fixed quota: one run blocked after ~3 requests, another made 16 consecutive 200s. 429 and outright TCP refusal are *alternative* modes, not an escalation — one 60-request run emitted zero 429s. Worst of all, identical requests 1 s apart alternate: `200 200 000 000 000 200 200 000 000 000`. A bulk fetch through a throttle window silently mixes retrieved and missing files with nothing distinguishing "not archived" from "refused". **CDX does not stay open either** — same host, degrades with it. What survives is the **`archive.org`** host: `wayback/available`, `metadata/<id>` and `advancedsearch.php` all answered 200 during a live block of `web.archive.org`. **Route around by host, not by agent**, and retry a CDX query twice before recording "no captures".
   - **2026-08-24 — public web search is currently unusable from this environment for obscure part numbers.** DuckDuckGo's `html/` and `lite/` endpoints both return a bot-challenge page ("select all squares containing a duck") with and without a browser UA. Bing returned **entirely unrelated German CRM-software results** for a quoted `"ED052TC4"` query — not zero results, *wrong* results, which is more dangerous. **Do not treat a search-engine miss as evidence a document does not exist**; probe candidate hosts directly instead.
   - **2026-08-24 — a 200 on a site's root does not mean the site is accessible.** `zerowriter.ink` serves the root to a Chrome UA but 403s every documentation and product path; the ClaudeBot UA gets 200 on all of them. Probe an actual content page, not just the homepage, before concluding a site works.
-  - **2026-09-04 — "the distributor is blocked" is usually too coarse; probe the *media* host and the *document* endpoint separately.** The table above recorded `digikey.com` and `mouser.com` as 403 to every UA, which is true of their **storefronts** and false of their **document CDNs**. `mm.digikey.com/Volume0/opasdata/...` is open to any UA with honest 404s, and `www.mouser.com/pdfDocs/...` serves the **WhatsApp** UA while 403-ing Chrome. Both were the only route to a current Semtech datasheet this session. **Before writing off a distributor, try its file host.**
-  - **2026-09-04 — a vendor can be *findable* and *undownloadable* at the same time, and the two need separate verdicts.** Semtech publishes an exhaustive, machine-readable, unauthenticated catalogue of all 1,984 of its documents (`design-support/development-support-documents/`, inline JSON) while making the documents themselves unobtainable to any non-browser client (a Salesforce Lightning content-distribution shell). **Enumeration: trivial. Retrieval: blocked.** Record those separately — "Semtech blocks crawlers" would be wrong in both directions.
-  - **2026-09-04 — an endpoint that returns 200 for an *invented* identifier is not merely a soft-404; it is unprobeable.** Semtech's `/sfc/p/<org>/a/<rec>/<token>` returns 1,359 B for a valid token and 1,363 B for a fabricated one. There is no request you can make that distinguishes "this document exists" from "I made this up". **Always fire the bogus-identifier control at the *document* endpoint, not just at the site root** — a host can be honest about pages and opaque about files.
-  - **2026-09-04 — Bing's failure mode is still returning *wrong* results, not zero, and it degrades mid-session.** The first query of the session (`LR2021 datasheet pdf Semtech`) returned exactly the Digi-Key and Mouser URLs that unlocked the whole task. Subsequent queries in the same session returned **thesaurus pages for "LR1121 datasheet"**, **package-tracking sites for "LR1121 datasheet filetype:pdf"** and **Xbox pages for "SX1268 datasheet pdf semtech"**. DuckDuckGo's `html/` and `lite/` endpoints returned **HTTP 202** to Chrome and, after one success, to WhatsApp too. **Budget for exactly one or two good search queries per session, spend them on the hardest lookup first, and switch to direct host probing the moment results turn irrelevant.**
-  - **2026-09-04 — `web.archive.org` cannot reach anything behind a JS content-distribution shell, and that is a permanent gap rather than a retry.** The CDX index for `semtech.com` holds 6,000 PDFs from the 2011–2019 `images/datasheet/` and `uploads/documents/` eras — enough to recover the entire first and second LoRa generations — but **zero LR11xx and zero LR20xx documents**, because those have only ever lived on `semtech.my.salesforce.com`, of which Wayback has captured only the bare host root. **Wayback is the recovery route for a vendor's *past* document store, never for its current one.**
   - **2026-08-24 — the WhatsApp UA is the one that works on Reddit.** Chrome, bare `curl` and Googlebot all 403; ClaudeBot gets 429. `WhatsApp/2.23.20.0` returns 200 on `old.reddit.com` JSON endpoints. Reddit's JSON API needs no key: `/r/<sub>/top.json?t=all&limit=N`, `/r/<sub>/search.json?q=…&restrict_sr=1`, and `<permalink>.json` for a whole thread with nested comments.
   - **2026-08-24 — a large 403 body can look like a successful fetch.** Kickstarter returns **294 KB** of HTML with a 403 status, including real project prose, so any check based on response size will pass. Check the status code and the `<title>`.
   - **2026-08-24 — when a vendor's website looks dead, grep their repository for the domain.** `zerowriter.com` is a parked for-sale page and is what the Crowd Supply campaign and every press article link to, which reads as an abandoned project. The live site (`zerowriter.ink`) was found only in a URL inside `firmware_releases/updates-readme.txt` in their GitHub repo. Release notes, installers, `howto.txt` files and firmware readmes routinely carry the current domain long after marketing pages go stale.
@@ -432,43 +410,6 @@ Tested 2026-08-21 while researching the Espressif ESP32-U4WDH.
   - **Re-verified 2026-08-24 (CH340 pass):** the API and download endpoints still work with a **plain default UA**. A full enumeration of ids **1–400 at 12-way `xargs -P 12`** completed with no silent truncation, consistent with the ≤ ~24 ceiling above. `id=79` = `CH340DS1.PDF` v3.4, uploaded 2025-03-12, `scope` = `CH340G, CH340C, CH340B, CH340N, CH340K, CH340E, CH340X, CH340T, CH340R`. Note the **version mismatch that is not an error**: the API reports version `3.4` while the PDF's own cover page reads `Version: 3D`. Both name the same file — do not "correct" a local filename on the strength of one or the other.
   - **Vendor *driver bundles* can be primary sources.** WCH's macOS `CH34xVCPDriver` embeds an `IOKitPersonalities` dictionary listing every VID/PID the vendor claims — better evidence than any web page. Extraction recipe (pure Python, no `hdiutil`): `bsdtar` the `.7z`; the `.dmg` is **UDZO**, so scan for `0x78 0x01/0x9c/0xda` zlib chunk starts and decompress each with `zlib.decompressobj()`, using `.unused_data` to locate the next chunk; then find `bplist00` markers in the concatenated output and brute-force `plistlib.loads()` over increasing end offsets. The sibling `.pkg` is a `xar` archive whose payload `bsdtar` rejects with "Decompressed size error" — **use the `.dmg`**. The same idea generalises: Windows `.inf` files, Linux kernel driver sources and macOS `Info.plist`s are all vendor-authored ID tables.
   - **Caveat on the +29 offset trick:** it is not as clean as recorded above. The shift is applied to letters, digits and punctuation but the extractor emits *some* characters unshifted, so shifted ranges collide with literal ones (a raw `3` is either the digit `3` or an encoded `P`). Mechanical decoding yields human-legible but machine-useless text like `bpmPO peries po` brrataK` for *"ESP32 Series SoC Errata."* Fine for reading an 8-page guide by eye; do not build a parser on it.
-  - **2026-09-01 — the "go to LCSC first for Chinese vendors" advice above has aged badly; go to the manufacturer.** In one session, **four** Chinese vendors served their own datasheets to a plain Chrome UA with no login — Awinic, Joulwatt, XMC and Siproin — while every LCSC path failed (search is a uniform JS shell, `www.lcsc.com/datasheet/*.pdf` returns `text/html` with HTTP 200, `wmsc.lcsc.com` 403s, `so.szlcsc.com` serves a slider challenge). The LCSC-first heuristic remains right for parts whose manufacturer publishes nothing; it is now the *second* thing to try, not the first.
-  - **2026-09-01 — Chinese vendor sites are JS SPAs, but their backends are usually wide open and return the whole catalogue.** Three separate vendors this session exposed an unauthenticated endpoint that dumps every product in one request: Joulwatt `GET /jwt/web/product/list?pageSize=3000` (1,564 products, 4.4 MB JSON), XMC `POST /product/getProductList` with `limit=500` (519 products), Awinic `GET /cn/searchProductListByNameForMall?type=1&page=1` (full mall listing). **All three ignore keyword parameters** — request everything and filter locally. Find the endpoint by fetching the site's own `request.js` / `common.js`, which typically contains the API base and the download-URL builder in plain text (`downloadFielValiy()` on `awinic.com`; `baseUrl = "https://www.joulwatt.com/jwt/web/"` on `joulwatt.com`).
-  - **2026-09-01 — a vendor datasheet can be a 4-page image scan with no text layer, and it will still validate as `%PDF`.** Joulwatt's `JW5712_JW5712A_Datasheet.pdf` is 2.5 MB of 300 dpi RGB page images. `%PDF` magic, correct `content-type`, plausible size — and `pdftotext` returns zero characters. **Add `pdfimages -list` (or a zero-length text check) to artifact validation**, and record the fact in the artifact table so the next agent does not re-download it hoping for a better copy.
-  - **2026-09-01 — declared-crawler User-Agents can be the *only* ones allowed.** `focuslcds.com` returns 403 to Chrome 131, Safari 17 and WhatsApp, and **200 to ClaudeBot**, on the same PDF URL. This inverts the usual assumption that a browser UA is the most permissive. When rotating agents, do not stop at the browser and link-preview UAs — the declared AI-crawler strings are a distinct class and are sometimes explicitly allowlisted by WordPress WAF rules.
-  - **2026-09-01 — public web search remains largely unusable from this environment, but Brave is the exception worth trying first.** Results this session: `search.brave.com` **worked** and produced the winning URLs for the IP2315, PY32L020, FT6336G, SSP7615 and XM25QH — but rate-limits to HTTP 429 after roughly three queries, with a long cooldown. `search.naver.com` returned parseable HTML and is a usable fallback. `www.google.com` returns 200 but is JavaScript-gated with no links in the HTML. DuckDuckGo (`html/` and `lite/`) → HTTP 202 challenge. Mojeek → 403 after two queries. `api.qwant.com/v3/search/web` → 403. All public SearxNG instances tried (`searx.be`, `search.inetol.net`, `priv.au`, `searxng.site`, `opnxng.com`) → 429 or empty. **Budget Brave queries deliberately and space them; do not burn them on parts you can reach by constructing a vendor URL.**
-  - **2026-09-01 — a part number that appears *only* on the board vendor's own pages is a real signal, not a search failure.** `LMD4737T261-AC02` and `RS-C1415MBAR` were each searched across eleven services; the only hits were M5Stack's own documentation and shop pages plus sites that copy them. No manufacturer, no distributor, no datasheet. That pattern — the string exists on the web solely because one board vendor published it — is consistent with a house part number or a domestic-channel-only part, and is worth recording as a finding rather than as an unfinished search.
-
-
-### Scholarly / preprint / archival
-
-Probed across 2026-09-01 → 2026-09-11 while building [`research/preprint-repositories/`](research/preprint-repositories/README.md) (~120 hosts). Full detail and per-host evidence in that directory's [`retrieval-notes.md`](research/preprint-repositories/retrieval-notes.md).
-
-**Block fingerprints — identify the product by body size, then decide whether to retry or reroute:**
-
-| Body size | Product | Hosts |
-|---|---|---|
-| **~5.2–6.1 kB**, HTTP 403 | Cloudflare managed challenge (`cf-mitigated: challenge`) | `techrxiv.org` 5,620 · `authorea.com` 5,620 · `essopenarchive.org` 5,622 · `scienceopen.com` 5,602 · `chemrxiv.org` 5,595 · `advance.sagepub.com` 5,623 · `papers.ssrn.com` 5,731 · `africarxiv.pubpub.org` 5,583 · `oatd.org` (incl. `robots.txt`) · `alldatasheet` 5,603 |
-| **~2.1–7.8 kB, HTTP 200** | ⚠ **Anubis proof-of-work — answers 200, not 403** | `rcaap.pt` 4,511 · `portal.dnb.de` 4,475 · `base-search.net` 7,846 · `scipost.org` 3,903 · `helda.helsinki.fi` 2,123 · `econstor.eu` · `theses.hal.science` · `archive.softwareheritage.org` |
-| **~651 kB**, 403 | SHERPA / OpenDOAR | `v2.sherpa.ac.uk` |
-| **1,337 B**, 403 | ETH custom block — **IP/provider-scoped, not UA-scoped** | `research-collection.ethz.ch` (lifted by 2026-09-11) |
-| **283 B**, 403 | origin UA filter | `bitsavers.org` — blocks `Wget` and default `curl`, serves Chrome |
-| **369 B**, 403 | minimal, non-Cloudflare | `preprints.org` |
-
-- Findings:
-  - **2026-09-11 — Anubis proof-of-work returns HTTP 200 with a challenge body, so a status check reads it as success.** Detect it by `<title>Making sure you're not a bot!</title>` (or `<title>Oh noes!</title>` for its error page), **not** by status code or byte size. **No user-agent defeats it** — it is a JS proof-of-work, so the UA ladder in this document is useless by construction. Anubis spread to the national-library layer during this survey (nine hosts, versions 1.23.0–1.27.0). **The escape is to change protocol, not agent:** OAI-PMH, Crossref, DataCite, Handle.net and DSpace REST were open behind the wall on eight of nine hosts. `rcaap.pt` is the sole exception — its OAI endpoint is behind the wall too.
-  - **2026-09-11 — `hdl.handle.net/api/handles/<prefix>/<suffix>` is the best existence oracle found.** Returns JSON `responseCode: 1` (exists) or `100` (does not), **served by the Handle System rather than the target repository, so it works straight through Cloudflare and Anubis.** Verified against walled TDX (prefix `10803`) and MIT DSpace (`1721.1`). Most DSpace/EPrints repositories mint handles, so this covers most institutional repositories. Strictly better than the `doi.org` trick below.
-  - **2026-09-04 — `doi.org` is a usable existence oracle behind a bot wall.** It returns **404 for an unregistered DOI**, but for a **registered** one it redirects and passes through the target's **403**. So a 403 from a `doi.org` redirect *confirms the record exists* even when the page cannot be read. This made PeerJ Preprints, ChemRxiv and TechRxiv measurable while all three were unreadable.
-  - **2026-09-01 — `osf.io` returns HTTP 200 and a byte-identical 4,207-byte SPA shell for preprint providers that do not exist.** Status code *and* body size are both uninformative, so the usual negative-control test fails here. Use `https://api.osf.io/v2/preprints/?filter[provider]=<slug>` and read `meta.total`; the API 404s correctly (61-byte body). This affects every OSF-hosted preprint server. `unpaywall.org` does the same at 1,421 bytes; `eccc.weizmann.ac.il` at 17,041; `openreview.net/forum?id=<bogus>` at 4,787.
-  - **2026-09-11 — `www.biorxiv.org` 429s Chrome, default `curl` and ClaudeBot but returns 200 to `WhatsApp/2.23.20.0`.** Corroborates the existing workspace note that the WhatsApp link-preview agent slips through where browser agents do not.
-  - **2026-09-01 — `philsci-archive.pitt.edu` runs the ladder backwards**: default `curl` succeeds where Chrome 131 is refused. Same for `archive.softwareheritage.org`, where a `curl`-style request gets JSON (1,643 B) and a browser UA gets the Anubis interstitial (4,667 B). **Try the bare default before escalating.**
-  - **2026-09-11 — `archive.ph/timemap/<url>` works and is scriptable.** A valid RFC 7089 Memento TimeMap, HTTP 200 / ~1,497 B, plain Chrome UA, no CAPTCHA (5/5 attempts). Only `/newest/` is CAPTCHA-walled (429, 63,290 B). With **Memento Aggregator dead**, this is the one remaining scriptable way to ask archive.today what it holds — correcting an earlier note in this repo that said archive.today has no API.
-  - **2026-09-11 — `bitsavers.org` serves a zero-byte `robots.txt` at HTTP 200**, so a naive crawler reads an open invitation and then gets 403/283 B on every fetch. It blocks `Wget/1.21.4` and default `curl` but serves Chrome. **The sanctioned route is `rsync://bitsavers.org/`**, or a mirror — mirrors do not apply the origin's block, which is the correct answer here rather than UA substitution (AGENTS.md rule 7). bitsavers holds the **only surviving copy of the DEC SRC/WRL/CRL research-report series** (521 reports + a 236,085,636-byte 2007 HP Labs mirror ZIP) now that `hpl.hp.com` resolves in DNS but is TCP-dead.
-  - **2026-09-11 — `search.ndltd.org` 503s, DART-Europe closed permanently (2025-02-03), and `oatd.org` 403s every client** — the global thesis discovery layer has collapsed, and NDLTD now redirects its flagship search to the one service that blocks robots. **CORE (`api.core.ac.uk`) and OpenAIRE are the only open machine routes left** for theses.
-  - **2026-09-11 — `ethos.bl.uk` is metadata-only since the 2023 British Library cyberattack, and its legacy URLs lie.** `OrderDetails.do?uin=<bogus>` returns **HTTP 200 and the home page** (62,214 B), so a link-checker reports 100% success on any legacy EThOS bibliography. The ~650,000-record dataset survives openly: DOI `10.23636/rcm4-zk44`, CC-BY, a 709,733,446-byte CSV including a `Supervisor(s)` column.
-  - **2026-09-11 — `eprint.iacr.org` needs no UA fallback but enforces a hard Cloudflare "20 per 1 minute" per-path limit with no `Retry-After`.** Its `robots.txt` is `Disallow: /` by default while whitelisting `Claude-User`/`Claude-SearchBot` for metadata and banning all PDFs; **TDM is explicitly reserved despite the PDFs being CC-BY**. OAI-PMH returns all 27,552 identifiers in one 3.34 MB response.
-  - **2026-09-11 — hosts that block every agent tried** (including Googlebot where tested): `papers.ssrn.com`, `peerj.com`, `dl.acm.org/opentoc`, `doabooks.org`, `science.org` (which also has **no Wayback snapshot** of the article wanted), `cell.com`, `cabidigitallibrary.org`, `hrbopenresearch.org`, `amrcopenresearch.org`. For these, go to Crossref/DataCite metadata or the `doi.org` 403-passthrough test above.
-  - **2026-09-11 — a site can be a working archive that presents as a dead one.** `cogprints.org` fails over HTTPS with a **TLS SAN mismatch** (its certificate is `CN=web-archive.southampton.ac.uk`) — `curl` reports a connection error and no HTTP status at all. Over **plain HTTP** it 301s to Southampton's static archive. ⚠ That fallback has since degraded: as of 2026-09-11 the redirect lands on **HTTP 401** (7,493 B, BotStopper). **Always try `http://` before declaring a host dead on a TLS error.**
 
 ### Developer / media (all ✓)
 
@@ -480,17 +421,10 @@ github.com, news.ycombinator.com, substack.com, tumblr.com, bsky.app, joinmastod
 
 Tips for acquiring data are not strictly limited to user agents — whatever works when the normal path doesn't is worth documenting here.
 
-- **An empty or wildcard query means "nothing", not "everything"** — verified independently on **NASA NTRS**, **OSTI.GOV** and **CiNii Dissertations** (2026-09-11). All three return `0`/`totalResults: 0` for an empty `q=`, rather than the full corpus. Three unrelated implementations share this trap, so assume it by default and cross-check any "total" against a known-populated facet.
-- **Follow redirects when probing APIs.** `zenodo.org/api/*` and `export.arxiv.org` over HTTP both return 301; omitting `curl -L` yields an empty body that reads exactly like a block. Two false "we are being rate-limited" conclusions in one session traced to precisely this — check for a 3xx before blaming the host.
-- **An API can return two plausible totals and the obvious one can be wrong.** `api.biorxiv.org` exposes both `total` (479,561 — every *version*) and `count_new_papers` (348,506 — distinct preprints) in the same object. Picking the obvious field overstated the corpus by 38%. Read the field list before trusting a count.
-- **Repositories usually count versions, not works.** Measured inflation ran from +1.6% to +50% across OSF providers; TechRxiv reports 30,954 DOI records for 18,890 actual items; Zenodo software is 284,518 concepts across 712,318 versions. Always establish which a number is.
-- **OAI-PMH signals errors in the body with HTTP 200** — an invalid verb returned 200 with a 488-byte error document. **Never status-check an OAI-PMH endpoint**; parse the response.
-- **Search-tokenisation can inflate a count by orders of magnitude.** Zenodo's API returns 422,778 hits for unquoted `RISC-V` against **495** quoted — an ~850× difference from hyphen tokenisation. Quote any term containing punctuation, and sanity-check surprising totals.
-- **When a scholarly or library site blocks you, look for a machine interface before concluding it is unreachable.** OAI-PMH, Crossref, DataCite, Handle.net and DSpace/REST were open on eight of nine proof-of-work-walled hosts tested in 2026-09. `econstor.eu` is the clearest case: the website is behind Anubis while its OAI-PMH endpoint is wide open, so an HTTP-only probe wrongly concludes the service is down.
 - **Rate limiting:** if the first couple of downloads succeed and then requests start failing, don't switch strategies immediately — slow down, wait a bit, and retry a single download. If that works, update this doc: note that the site has a rate limiter, which UA eventually worked, and any inferred limits (requests per minute, seconds between downloads, burst size). Even a rough guess ("~10 docs/min then 429s") is useful for future sessions.
 - **Mirrors and archives:** some sites move or delete resources, so a dead URL isn't always a block. If a URL is unreachable entirely (down, moved, deleted) — not just bot-blocked — someone may already have captured it. See *Finding copies of inaccessible URLs* below before giving up. GitHub repos/mirrors also often hold copies of documentation and datasets.
 - **Finding copies of inaccessible URLs** (dead, moved, or blocked):
-  - **Wayback capture list:** `https://web.archive.org/web/*/<url>*` shows the capture timeline in the UI. Programmatically use the availability API: `https://archive.org/wayback/available?url=<url>` (returns the closest snapshot as JSON). ⚠ **But see the 2026-09-11 correction under *Vendor documentation portals* — this API returns false negatives. An empty result does not mean unarchived; confirm with CDX.**
+  - **Wayback capture list:** `https://web.archive.org/web/*/<url>*` shows the capture timeline in the UI. Programmatically use the availability API: `https://archive.org/wayback/available?url=<url>` (returns the closest snapshot as JSON).
   - **Wayback CDX API** — the power tool. Lists every capture with status codes, timestamps, and original URLs, supporting wildcards: e.g. `https://web.archive.org/cdx/search/cdx?url=example.com/docs/&matchType=prefix&filter=statuscode:200&collapse=urlkey&output=json`. Use it to find captures of moved paths (`matchType=prefix` over the old directory), to pick the best snapshot (200s only), or to discover sibling URLs you didn't know existed. Add `&limit=` and paginate.
   - **Other archives:** `archive.today` (mirrors at archive.ph etc.) often has captures Wayback lacks, especially JS-heavy pages; **Memento Aggregator** (`http://timetravel.mementoweb.org/api/json/<timestamp>/<url>`) searches many archives (Wayback, Arquivo, etc.) at once.
   - **Software Heritage** (`softwareheritage.org`) — archival store for source code; if a repo vanished, its origins/directory tree may be preserved there. Wayback rarely preserves whole repos well.
@@ -523,98 +457,3 @@ Provenance studies with similar methodology:
 - [Vidern: We Tested the World's Top 1,000 Websites](https://vidern.com/blog/top-1000-websites-ai-crawler-study)
 - [HasData: The AI Crawler Block Index](https://hasdata.com/blog/ai-crawler-block-index)
 - [agentmarkup: 500-company AI-crawler audit](https://agentmarkup.dev/blog/ai-crawler-audit-500-companies/)
-
----
-
-## Appended 2026-09-11 — regulatory databases, datasheet mirrors, GitHub LFS
-
-Added by the Xteink round-2 research pass. **Append-only; nothing above was
-changed.** Full working notes, including the queries that failed, are in
-[`scratch/xteink/crawler-findings-round2.md`](scratch/xteink/crawler-findings-round2.md).
-
-### Regulatory / FCC databases
-
-| Host | Chrome 131 UA | `WhatsApp/2.23.20.0` | ChatGPT-User | ClaudeBot | Safari 17.4 |
-|---|---|---|---|---|---|
-| **`fccid.io`** | **✗ 403** | **✓ 200** | ✓ 200 | ✓ 200 | ✓ 200 |
-| `fcc.report` | ✗ 403 | ✗ 403 | ✗ 403 | ✗ 403 | ✗ 403 |
-| `apps.fcc.gov/oetcf/eas/…` | ✗ 403 | — | — | — | — |
-
-**`fccid.io` inverts the usual ladder**: the desktop-Chrome UA is the one that is
-blocked, and every bot / link-preview UA is served. An agent that starts with
-Chrome and stops on a 403 will wrongly conclude the site is inaccessible.
-
-Two URL patterns worth keeping:
-
-- **Exhibit PDFs:** `https://fccid.io/<FCC-ID>/<Type>/<Slug>-<DocumentID>.pdf`.
-  `<DocumentID>` is the numeric suffix in the `href`s on the FCC ID page.
-  **12/12 fetches returned HTTP 200 with `%PDF` magic bytes**, 2026-09-11.
-- **Grantee enumeration:** `https://fccid.io/<GRANTEE-CODE>` lists **every** FCC
-  ID a company holds. This is how to find products a vendor has certified but
-  never announced — it found one on this pass.
-
-Exhibits marked *"Metadata only"* with a future date are under a confidentiality
-order; requesting their `.pdf` URL does not return the document.
-
-### `crystalfontz.com` — serves controller datasheets, and the URL lies
-
-`https://www.crystalfontz.com/controllers/<Vendor>/<Part>/<id>/` returns a real
-PDF with a plain UA. **The `<Vendor>` and `<Part>` path segments are decorative —
-only the trailing `<id>` selects a document.**
-
-Observed: `…/controllers/UltraChip/UC8179/478/` returns a valid 477 KB PDF that
-is the **GOODiX GT911 Programming Guide**. The correct UC8179 id is **517**, read
-from the page's own `datasheet-viewer.php?id=517` link — and requesting
-`datasheet-viewer.php?id=517` directly returns HTML, not the PDF.
-
-**Magic-byte validation is not sufficient here.** Check `pdfinfo`'s `Title`
-before filing anything from this host.
-
-### Electronics distributors / parts catalogues — additions
-
-| Host | Result, 2026-09-11 |
-|---|---|
-| `wmsc.lcsc.com/ftps/wm/search/global` (JSON API) | **✗ 403** on Chrome, WhatsApp **and** ClaudeBot UAs |
-| `www.lcsc.com/search?q=…` (HTML) | **✓ 200** with `WhatsApp/2.23.20.0` — use the HTML storefront, not the API |
-| `alldatasheet.com` | ✗ 403 |
-| `buydisplay.com/download/ic/*.pdf` | ✗ 403 |
-| `good-display.com` · `v4.cecdn.yun300.cn` | ✗ 403 / JS shell |
-| `waveshare.com` wiki upload paths | ✗ 403; `waveshare.net` returns an HTML page under a `.pdf` URL |
-| `e-paper-display.com` / `.cn` | ✗ 404 |
-| `www.szbelling.com` | ✗ **connection failure, HTTP 000** |
-| `cellwise-semi.com` (CN and `en.` subdomain) | **✓ 200, live** — but the part being sought (CW2017) is **absent from its own catalogue**, which is itself the finding |
-| `elecrow.com/download/product/<code>/<Part>_Datasheet.pdf` | **✓ 200, `%PDF`** — a module vendor that mirrors controller datasheets |
-
-### Search engines
-
-`html.duckduckgo.com/html/?q=…` returned **HTTP 202** bot-check pages with zero
-results on four consecutive queries with a Chrome UA. Not usable as a fallback
-for part-number searches this session.
-
-### GitHub LFS blobs without installing `git lfs`
-
-Verified end-to-end 2026-09-11 on a 6,254,064-byte object, unauthenticated:
-
-```bash
-# 1. Read the ~130-byte pointer to get the oid and size
-gh api "repos/<O>/<R>/contents/<path>?ref=<sha>" --jq .content | base64 -d
-
-# 2. Ask the batch API for a signed URL (no auth needed)
-curl -s -X POST "https://github.com/<O>/<R>.git/info/lfs/objects/batch" \
-  -H "Accept: application/vnd.git-lfs+json" \
-  -H "Content-Type: application/vnd.git-lfs+json" \
-  -d '{"operation":"download","transfers":["basic"],
-       "objects":[{"oid":"<sha256>","size":<bytes>}]}'
-
-# 3. Follow .objects[0].actions.download.href  (expires in 3600 s)
-```
-
-**The LFS `oid` is the file's SHA-256**, so a pointer file alone is enough to
-write a complete, self-sufficient artifact placeholder — hash, byte size and
-reacquisition recipe — without ever downloading the blob.
-
-### `old.reddit.com` — re-confirmed
-
-`WhatsApp/2.23.20.0` returned **200 on 23/23 requests** across `search.json`,
-`r/<sub>/search.json?restrict_sr=1&t=year` and `<permalink>.json?limit=200`.
-Unchanged from the earlier entry.
diff --git a/archive b/archive
deleted file mode 120000
index ac7c081..0000000
--- a/archive
+++ /dev/null
@@ -1 +0,0 @@
-../repo-archive/hardware-doc
\ No newline at end of file
diff --git a/artifact-manifest.md b/artifact-manifest.md
index 984afe1..7683a94 100644
--- a/artifact-manifest.md
+++ b/artifact-manifest.md
@@ -1935,331 +1935,3 @@ All three validated on 2026-08-24 by `%PDF` magic, `sha256sum`, and
 **No manufacturer datasheet exists publicly for the `ED052TC4` or `ED052TC2`.** That is a property of
 E Ink's business model, not a retrieval failure; the probes are recorded in
 `component-download-failures.txt` §12 and the vendor-level analysis in `vendors/e-ink/README.md`.
-
----
-
-## Waveshare ESP32-S3-ePaper-3.97 pass, 2026-09-01
-
-Six PDFs totalling **6 779 870 bytes**, plus three HTML page snapshots (324 780 B) and
-one derived TSV (27 638 B). **Not reflected in the file/byte totals at the head of
-this document — regenerate before quoting them.**
-
-All six PDFs were validated by `%PDF` magic bytes on retrieval, **never by HTTP
-status**. Two further candidate downloads failed this check and were **deleted rather
-than kept under a misleading extension**: `files.waveshare.com/wiki/common/AXP2101.pdf`
-returned XML, and a guessed `AXP2101_Datasheet_V1.0_en.pdf` path on
-`lewisxhe/XPowersLib` returned **267 330 bytes of HTML** — a size large enough to pass
-any naive length check. Both are recorded in
-`devices/waveshare/esp32-s3-epaper-3.97/sources.md`.
-
-| Path | Bytes | SHA-256 | Version | Source |
-|---|---:|---|---|---|
-| `devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf` | 257 550 | `b12031451374e2333e8eca2b8290c40b4c67955b1f12df17b96f3ee479e6f0be` | `unknown` — no revision block in the text layer | `files.waveshare.com/wiki/ESP32-S3-ePaper-3.97/` |
-| `components/waveshare/3.97inch-e-paper/artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf` | 2 774 287 | `4f756734dbfa7485c57e7ab7124f59f0afb00ca2600cda24a2285f02e4ab05cf` | **Rev 1.0, 2025-04-24** | `files.waveshare.com/wiki/3.97inch_e-Paper_HAT+/` |
-| `components/x-powers/axp2101/artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf` | 1 554 740 | `9e51d16d84d905c32a001a123be8e6c58213ee21e42d5bdb1458b731dba10f6d` | **V1.4 EN** | `lewisxhe/XPowersLib` — community mirror; **no primary X-Powers URL located** |
-| `components/everest-semiconductor/es8311/artifacts/es8311-datasheet-waveshare-mirror.pdf` | 729 315 | `be42a2cb09093378feaccf55c227be579edc5a17786a11cc34254ea91264538a` | `unknown` | `files.waveshare.com/wiki/common/` |
-| `components/sensirion/shtc3/artifacts/shtc3-datasheet-waveshare-mirror.pdf` | 928 256 | `d315fe3d00282ece1d8901c0936f8bcbaa87b159bcd0e71f9002d1f03b57a8f1` | `unknown` | `files.waveshare.com/wiki/common/` |
-| `components/nxp/pcf85063a/artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf` | 535 722 | `93b384873539e770305b8982bcfa6387eac695650063b6a11279beae7a20602a` | **NXP Rev. 6, 2015** | `files.waveshare.com/wiki/common/` |
-
-**Licences: all six `unknown`.** None states terms. Disposition `repository` for all
-six. Nothing was omitted over licensing.
-
-### Deliberate near-duplicate — not an accident
-
-`pcf85063a-datasheet-rev6-waveshare-mirror.pdf` sits beside the existing
-`pcf85063a-datasheet.pdf` (726 288 B, `a09223db…`, **NXP Rev. 7, 2018**). **Different
-revision, different size, different hash** — kept per the rule that same-document,
-different-hash means retain both and investigate. Waveshare ships its customers a copy
-**three years and one revision stale**. This is the *third* part for which that has now
-been measured; see `vendors/waveshare/README.md` §9.6.
-
-A repo-wide hash sweep over all PDFs after this pass found **one** duplicate-hash group,
-and it is pre-existing and intentional (the Panasonic A4S connector document shared by
-`axe512127d` and `axe612124d`). None of the artifacts above duplicates anything.
-
-### Not downloaded, recorded for reacquisition
-
-~104 MB deliberately left upstream, fully manifested in
-`devices/waveshare/esp32-s3-epaper-3.97/acquisition/manifest.json` with URLs, expected
-sizes, flash offsets and target MCU:
-
-| Artifact | Bytes | Why not fetched |
-|---|---:|---|
-| `260314.bin`, `260304.bin` — full-flash factory images | 2 × 16 777 216 | Not needed for the questions this pass answered; offset `0x0` recorded from the vendor's own `ReadMe_EN.txt` |
-| `…_xiaozhi-xs.bin`, `…_xiaozhi.bin` — third-party AI-voice firmware | 11 179 471 + 9 920 235 | ditto; upstream project `github.com/78/xiaozhi-esp32` recorded |
-| `waveshareteam/ESP32-S3-ePaper-3.97` repository @ `9b12d40` | ~50 MB | Metadata, full tree listing and four individual files read via the API instead. **No `LICENSE` file — licence `unknown`** |
-
----
-
-## Seven-session sweep, 2026-09-04 — 2026-09-07
-
-Artifacts added by the Xteink, M5Stack DinMeter, M5Stack Cardputer, M5Stack LoRa-expansion,
-LilyGO T-Display K230, LilyGO T-Display-S3 and LoRa-generation passes, transcribed from each
-session's `index-fragments.md` on 2026-09-07. **None of these figures has been recomputed
-here** — they are as each session measured them. Regenerate before quoting repository totals.
-
-Several sessions also maintain authoritative machine-readable manifests, which win over this
-summary where they disagree:
-
-- `devices/m5stack/dinmeter/acquisition/manifest.json` — 27 records
-- `devices/m5stack/dinmeter-v1.1/acquisition/manifest.json` — 9 records
-- `devices/m5stack/cardputer-adv/acquisition/manifest.json`
-- `devices/lilygo/t-display-s3/acquisition/manifest.json`
-- `devices/lilygo/t-display-k230/media/manifest.json`
-
-### Xteink — 2026-09-04
-
-| Path | Bytes | SHA-256 | Note |
-|---|---:|---|---|
-| `devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin` | 16,777,216 | `b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245` | Xteink X4 OEM full-flash dump (ESP32-C3). Licence **none declared**, redistribution **unknown/probably prohibited**. Archived 2026-09-04, **unstaged pending review** — [placeholder](devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md) |
-| `devices/xteink/x3/artifacts/teardown/imgur-2026-07-01/` | 19,513,196 (13 files) | per-file, in placeholder | Xteink X3 teardown, 13 captioned images. Licence **unknown**. Archived 2026-09-04, **unstaged** — [placeholder](devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.md) |
-| `devices/xteink/x3/artifacts/teardown/sunwoods-cn/` | 5,034,272 (11 files) | per-file, in placeholder | Xteink X3 Chinese teardown **including a hand-drawn schematic sketch** — the only schematic-like document for any Xteink device. Licence **none declared**. Archived 2026-09-04, **unstaged** — [placeholder](devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.md) |
-
-### M5Stack DinMeter (K134 / K134-V11) — 2026-09-04
-
-| Summary | Manifest |
-|---|---|
-| 36 artifacts, 0 failed downloads. 2 archived (doc-export PDFs, 18.7 MB) + 1 archived component STEP. ~3.2 MB retained in-repo across the two device records plus component artifacts. **Intentional duplication:** the v1.1 schematic and STL are byte-identical to v1.0's and both are retained, because the duplication under two URLs is itself the finding. **Deduplicated against the repo:** the ESP32-S3 datasheet fetched from M5Stack matched `components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf` (`b6db403d…`) and was not re-added. | [manifest](devices/m5stack/dinmeter/acquisition/manifest.json) |
-
-### M5Stack Cardputer family — 2026-09-04
-
-| Path | Bytes | SHA-256 | Source | Licence | Redist. | Note |
-|---|---:|---|---|---|---|---|
-| `devices/m5stack/cardputer-adv/artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf` | 878 155 | `9553f5ee22b6e5f29a385388192e42c5ff76f16281b6f7ea9418f7b62a2d48b0` | M5Stack | no licence stated | unknown | Cardputer ADV schematic, 4 sheets, file-stamped 2025-06-20 |
-| `devices/m5stack/cardputer-adv/artifacts/mechanical/K132-Adv-cardputer-ADV.pdf` | 127 977 | `6c937ca05e0894e54a3e47abb57e91de1b755dea032fd3f7438ea7a3e34550da` | M5Stack | no licence stated | unknown | Cardputer ADV dimension drawing |
-| `devices/m5stack/cardputer-adv/artifacts/docs/docs-en-core-Cardputer-Adv.html` | 147 339 | `f05bbb70ca0964ebcd465e866bf25302f24cd29ecada5099803c7786c3b54fec` | M5Stack | no licence stated | unknown | product page snapshot, EN, 2026-09-04 |
-| `devices/m5stack/cardputer-adv/artifacts/docs/docs-zh_CN-core-Cardputer-Adv.html` | 146 690 | `4a285b0281f21864e394554161976786ac4846abfd7021f2422a3f4cced2ac61` | M5Stack | no licence stated | unknown | product page snapshot, zh_CN, 2026-09-04 |
-| `devices/m5stack/cardputer-v1.1/artifacts/schematic/Sch_M5Cardputer.pdf` | 717 743 | `6016c1fe6099b9e3f0d0c88f07a3fba1aa44a3da8a7a91dd7040ad0fffa2041e` | M5Stack | no licence stated | unknown | **also served as the v1.0 schematic under product id `481` — byte-identical** |
-| `devices/m5stack/cardputer-v1.1/artifacts/schematic/M5Cardputer_Base.pdf` | 24 076 | `29542fe18b8687e4bd5fe7c533decd6a21e434cac8ac4b3f4cb1a6dd407be2cc` | M5Stack | no licence stated | unknown | base board; likewise served under both ids |
-| `devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/` | 117 087 (33 files) | tree `b0f20d35d31d24514320a0263b51aeb33a01a50a4f68c7f341f172d3c2f232d7` | M5Stack | **MIT** | allowed | `M5Cardputer` 1.1.1 @ `f1392858`. **Digest recipe — run from *inside* the snapshot directory**, because `sha256sum` embeds the path it is given: `cd <snapshot> && LC_ALL=C find . -type f \| LC_ALL=C sort \| xargs sha256sum \| sha256sum` |
-| `devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/` | 4 658 (5 files) | — | M5Stack | MIT ⚠ repo pins LGPL-3.0 RadioLib | conditional | build configuration only. ⚠ **The LGPL-3.0 attribution is contested — RadioLib is MIT**; see [`scratch/index-merge/corrections-requiring-review.md`](scratch/index-merge/corrections-requiring-review.md) |
-
-Device HTML snapshots also exist at `devices/m5stack/cardputer-v1.0/artifacts/`,
-`cardputer-v1.1/artifacts/`, `cardputer-zero/artifacts/` and `cardputer-mesh-kit/artifacts/`;
-hashes are in each device's record and in
-`devices/m5stack/cardputer-adv/acquisition/manifest.json`.
-
-### M5Stack LoRa, sub-GHz and NFC expansions — 2026-09-04
-
-| Path | Bytes | SHA-256 | Source URL | Retrieved | Version/date | Licence | Redistribution | Disposition |
-|---|---:|---|---|---|---|---|---|---|
-| `devices/m5stack/cap-lora-1262/artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf` | 155 866 | `dbc5266d7015cf2e71f2a7ebe13fd88732bf260febced1659f42712fcd94ac8c` | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-sche-Cap-LoRa1262_SCH_V1.1_20251029_2025_11_07_22_53_19.pdf` | 2026-09-04 | V1.1, 2025-10-29 | unknown | unknown | repository, unstaged |
-| `devices/m5stack/cap-lora-1262/artifacts/mechanical/U214-cap1262-model-size.pdf` | 90 950 | `54f765a2f74bf922d65c9c6b38e7354e008a7ff4c7a96426c4d02259b6c3cb8e` | `…/1208/U214-00-cap1262-model-size.pdf` | 2026-09-04 | undated | unknown | unknown | repository, unstaged |
-| `devices/m5stack/cap-cc1101/artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf` | 485 518 | `2c24e78ff5fff44ca2ddb274ad4a514fb736caefb5c8969dacf57f481a965e0b` | `…/1250/SCH_Cap_CC1101_SCH_V0.3_20260528.pdf` | 2026-09-04 | V0.3, 2026-05-28 | unknown | unknown | repository, unstaged |
-| `devices/m5stack/cap-cc1101/artifacts/mechanical/U219-Cap_CC1101_model_size.pdf` | 41 925 | `f0e6e622847ef5546501b7ca937a16daa0b57b89cec21c85251f6752c6c766e4` | `…/1250/U219_Cap_CC1101_model_size.pdf` | 2026-09-04 | undated | unknown | unknown | repository, unstaged |
-| `devices/m5stack/stamp-c6lora/artifacts/S012-Stamp_C6LoRa_SCH_v0.2.3.pdf` | 489 288 | `2dafe92c5090a01aa948c1ce88b17d1237421d09701c1e0a15a122bd9d844d35` | `…/1223/S012-SCH_Sch_M5_C6_Lora_v0.2.3_2025_12_02_19_14_35.pdf` | 2026-09-04 | v0.2.3, 2025-12-02 | unknown | unknown | repository, unstaged |
-| `components/m5stack/stamp-lora-1262/artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf` | 184 442 | `6ec29a9240fc8dc41fbe699e74a9f645b9753d7932efc1de28b049fe58e8f03b` | `…/1208/NEW-1262-SCH_A1-Lora_2025_08_27_10_58_52.pdf` | 2026-09-04 | rev A1, 2025-08-27 | unknown | unknown | repository, unstaged |
-| `components/texas-instruments/cc1101/artifacts/cc1101-datasheet-m5stack-mirror.pdf` | 2 718 663 | `0c5cdadd06a9f8de6776dda8c8fb29c5029baa2838413335270e223e55a4e169` | `…/1188/CC1101_Datasheet.pdf` | 2026-09-04 | rev unverified | TI notices | unknown | repository, unstaged |
-| `components/zhongkewei/atgm336h-6n/artifacts/atgm336h-6n-datasheet-m5stack-mirror.pdf` | 752 259 | `7b1c10193709d7600e0234445a1c15603bf3443e14780ecde4818091ec2eda32` | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/unit/Unit-GPS%20v1.1/ATGM336H-6N.pdf` | 2026-09-04 | undated | unknown | unknown | repository, unstaged |
-| **archived** `components/zhongkewei/at6668/artifacts/CASIC_…Protocol_Specification.pdf` | 2 899 191 | `61e2567dcf04b0d8e4d5ec6c9c841f8ac0caa846f5b54645a64b7704d800fe04` | `…/1173/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf` | 2026-09-04 | unknown | unknown | unknown | **archived**, placeholder in place |
-| `devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_{01,02,03,05}.webp` | 152 404 / 58 502 / 40 210 / 66 312 | `2a7e969b…` / `6a256af9…` / `6ce70ea4…` / `d9d2622f…` | `…/1208/U214-Cap-LoRa-1262-main-pictures_NN.webp` | 2026-09-04 | undated | unknown | unknown | repository, unstaged |
-| `devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_{01,02,03,05}.webp` | 265 534 / 137 082 / 62 126 / 75 184 | `29ea3e3c…` / `29af4203…` / `8e066761…` / `b6d642c3…` | `…/1250/U219_Cap_CC1101_main_pictures_NN.webp` | 2026-09-04 | undated | unknown | unknown | repository, unstaged |
-
-**Duplicate detected and deliberately not added:**
-`https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1229/st25r3916_datasheet.pdf` is
-**byte-identical** to the existing
-`components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf`
-(`sha256 1170f4d7…`, 2 241 765 B). M5Stack serves the same bytes from two OSS paths. The
-extra URL is recorded in that component's source table instead. **Any future pass filing an
-M5Stack-mirrored datasheet should hash-check first** — this will recur.
-
-**Totals for that pass, measured 2026-09-04:**
-
-| Category | Files | Bytes |
-|---|---:|---:|
-| PDFs (schematics, mechanical drawings, datasheets) | 8 | **4 918 911** |
-| WebP product photographs | 8 | **857 354** |
-| Authored Markdown (new device + component records) | 51 | **329 979** |
-| **Repository total added** | **67** | **≈ 6.1 MB** |
-| Archived out of the repository, placeholder in place | 1 | 2 899 191 |
-| Scratch working set (in `../repo-archive/scratch/`) | — | ≈ 24 MB |
-
-**Duplicate-hash scan across everything added: 0 duplicates.** All 8 PDFs verified `%PDF-1.x`
-by magic bytes; all 8 images verified `RIFF…WEBP`. No HTML error page was retained under a
-document extension.
-
-### LoRa silicon generations — Semtech — 2026-09-04
-
-| Path | Bytes | SHA-256 | Document | Provenance | Retrieved | Licence / disposition |
-|---|---:|---|---|---|---|---|
-| `components/semtech/lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf` | 5 809 234 | `0d9051db78b243bf89db7ff00bc549ff1fe3ffedc6e08649c9081e8393ef00b7` | Semtech `DS.LR20xx` LR2021/LR2022/LR2012 Final Datasheet **Rev 2.1**, 13/04/26, 243 pp | primary via Digi-Key `mm.digikey.com/Volume0/opasdata/d220001/medias/docus/8924/600_62785538.LR20xxDatasheet_V2_1.pdf` | 2026-09-04 | licence `unknown` (© Semtech, "Proprietary & Confidential") · redistribution `unknown` · disposition `repository`, unstaged |
-| `components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf` | 5 158 757 | `926b88cbfb6434e3954569b3f0d96e47c3ca2952245ebc1d01f65ab52d382ff7` | Semtech `DS.LR2021` **Rev 1.1**, 10/14/25, 236 pp — superseded, retained because it differs in substance | primary via Mouser `mouser.com/pdfDocs/61979758LR2021_V1_1_datasheet.pdf` ⚠ **WhatsApp UA required** | 2026-09-04 | **ARCHIVED** — placeholder at `…pdf.ARCHIVED.md` |
-| `components/semtech/lr2021/artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz` | 106 656 | `f1f172ce871a183d8d6431c157e0d44b457057ccd0c9e4d0e1c98bf76a3493ee` | Semtech `lr20xx_driver` **v2.0.2** subtree + USP licences, from `LoRa-Net/usp` @ `512a095e303872f900021361a619b7b1e6e29469`, release `v1.1.2-feature-202604` | primary, GitHub | 2026-09-04 | **BSD-3-Clause-Clear** · redistribution `allowed` (preserve notices) · disposition `repository` |
-| `components/semtech/sx1276/artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf` | 2 152 983 | `ec4e2fb67736b5d706e60ffb84fc0a22ca25a4eed33c58aa62e52580a59f7b2b` | Semtech SX1276/77/78/79 Datasheet **Rev. 5, August 2016**, 132 pp | credible mirror — Internet Archive capture `20180903190247` of `semtech.com/uploads/documents/DS_SX1276-7-8-9_W_APP_V5.pdf` (⚠ that path now soft-404s) | 2026-09-04 | licence `unknown` · redistribution `unknown` · disposition `repository`, unstaged |
-| `components/semtech/sx1276/artifacts/sx1276-77-78-errata-wayback.pdf` | 173 175 | `d31cd91430b1ba04cc237e38895fd210a3a33aaa15a30077eb10d7cf79e0c010` | SX1276/77/78 Errata Note, **Revision 1, Sept 2013** (⚠ internal `/Title` says 1.1) | credible mirror — IA capture `20150902061654` of `semtech.com/images/datasheet/sx1276_77_78-errata.pdf` | 2026-09-04 | as above |
-| `components/semtech/sx1276/artifacts/sx1272-73-errata-wayback.pdf` | 140 550 | `a15152c7fdeb31fbebdfeb027157ed54b9badaf26a5adbc0532e67e0f2866242` | SX1272/73 Errata Note | credible mirror — IA capture `20150412001918` of `semtech.com/images/datasheet/sx1272_73_errata.pdf` | 2026-09-04 | as above |
-
-### LilyGO T-Display K230 — 2026-09-04
-
-| Path | Bytes | SHA-256 | Document | Licence / disposition |
-|---|---:|---|---|---|
-| `components/canaan/k230/artifacts/K230_datasheet-v1.0-2023-07-06.md` | 83 002 | `f0bd20a600be373b8b5ca605d65215651ccb29e7d2c09cfdf26a74bec8ebc556` | Canaan K230 datasheet V1.0 (2023-07-06), `kendryte/k230_docs` @ `f8e3021` | licence **conflict** — repo BSD-2-Clause vs restrictive document notice; **unstaged** |
-| `components/canaan/k230/artifacts/K230_brief_datasheet.md` | 7 781 | `5cb684cf593698defe9b2d0044ec54fbcd2e0045efe6afd3961fe2157edd30ed` | Canaan K230 brief datasheet | as above |
-| `components/canaan/k230/artifacts/K230_Hardware_Design_Guide.md` | 49 061 | `19e7243c50197a4835b9f85ca51c3fc9abd52ca9d353c6a92ddc8eaf9a3384f4` | Canaan K230 hardware design guide | as above |
-| `components/canaan/k230/artifacts/K230_PMU_User_Guide.md` | 10 039 | `91a057dbc885f9761392f57c67c6e06bbf2a53cd96de558b8de3b58a5e9829d1` | Canaan K230 PMU user guide | as above |
-| `components/canaan/k230/artifacts/K230_nncase_Development_Guide.md` | 81 128 | `c2b297c9a615e0b67e9bd2c443d7c218a9d3ec4feab33a129e3e8f6ce4132ee5` | Canaan nncase development guide | as above |
-| `components/canaan/k230/artifacts/K230_RVV_In_Action.md` | 12 528 | `6dc416406711b5490b2dcc927f77997aaa861436a345801116c9f552789a186a` | Canaan RVV tutorial | as above |
-| `components/canaan/k230/artifacts/K230_RVV_optimization_performance_description.md` | 12 004 | `77a7facbfab8cff717f3305635cb1f9f0965dab90431fc98aeb60119152c4cb0` | Canaan RVV optimisation notes | as above |
-| `devices/lilygo/t-display-k230/media/*.jpg` (14 files, ~3.0 MB) | see `media/manifest.json` | see manifest | LilyGO product and wiki imagery incl. the 40-pin diagram and keyboard-extension diagram | licence **unknown**; **unstaged** |
-
-### LilyGO T-Display-S3 family — 2026-09-07
-
-30 artifacts. Per-device machine-readable manifests already exist at
-`devices/lilygo/t-display-s3/acquisition/manifest.json`; **the umbrella rows should be
-generated from those rather than retyped**, which is why only the group summary is recorded
-here.
-
-| Group | Count | Bytes | Note |
-|---|---:|---|---|
-| Board schematics (PDF) | 14 | ~5.7 MB | across 8 boards |
-| Factory firmware (ESP32-S3 merged images) | 6 | ~5.7 MB | **two are byte-identical** — intentional duplication, it *is* the finding |
-| Vendor source files (headers, board JSON, `platformio.ini`, TFT_eSPI setup) | 4 | ~23 KB | |
-| Org/enumeration metadata (TSV) | 1 | ~25 KB | |
-| Chip datasheets → `components/**/artifacts/` | 14 | ~40 MB | 1 archived (CO5300, 12.6 MiB) |
-
-**Licence flags for review — these should stay unstaged:**
-
-| Artifact | Reason |
-|---|---|
-| `components/axs-technology/axs15231b/artifacts/axs15231-datasheet-v0.4-*.pdf` | explicit **no-distribution notice** on the cover |
-| `components/shenghe-microelectronics/sh8601z/artifacts/*.pdf` | marked **CONFIDENTIAL** |
-| `components/shenghe-microelectronics/sh8501b/artifacts/*.pdf` | marked **CONFIDENTIAL** |
-| All schematics from `T-Display-S3-Long` and `T-Display-S3-Pro` | those repositories declare **no licence at all** |
-| All mirrored chip datasheets | third-party copyright regardless of the repository licence |
-
-> **Merge note, 2026-09-07.** The T-Display-S3 session was still writing when this section was
-> transcribed; its fragment (SHA-256 `2f3acf08…`) may have grown since. Re-diff before treating
-> the group counts as final. See [`scratch/index-merge/README.md`](scratch/index-merge/README.md).
-
----
-
-## Round-two sweep, 2026-09-11 — FCC exhibits, datasheets and the artifact split
-
-Three sessions ran on 2026-09-11: Xteink round two, schematic net-tracing, and certification /
-market. This section records what they acquired and **where it was decided to live**. No row
-above was altered.
-
-### 1. The decision: 174 FCC exhibits, split by value and size
-
-The certification pass harvested **174 exhibit PDFs from 26 filings** into
-`scratch/market-and-certification/fcc/`. Scratch is the archive, not the repository, so they sat
-outside the repo **with no placeholders** — which the research method forbids for anything
-useful. The round-two merge applied the method's rules in order.
-
-**Whose is it?** An FCC exhibit describes a specific board or module, so it is a **device** or
-**component** artifact: `devices/<vendor>/<board>/artifacts/certification/` for boards,
-`components/<vendor>/<part>/artifacts/certification/` for the module grants (Stamp-S3A, Stamp
-LoRa-1262, ESP32-S3-WROOM-1/1U).
-
-**Small or large?** **Internal Photos** and **ID Label / Location Info** stay in the repository,
-subject to a **4 MiB per-file cap**. They are the identification and teardown evidence — for
-several of these boards the internal photographs are the only public imagery of the PCB that
-exists anywhere, and `2BTR9-XTEINKX4`'s are the **first public teardown of the Xteink X4**.
-Everything else — full test reports, RF-exposure annexes, antenna reports, users manuals,
-external-photo sets — is bulk, and is archived with a placeholder.
-
-| | Files | Size |
-|---|---:|---:|
-| **Retained in the repository** (incl. 12 already placed by the Xteink pass) | **59** | **57.80 MiB** (60.61 MB) |
-| **Archived**, each with a placeholder at its former repo path | **106** | **130.59 MiB** (136.93 MB) |
-| **Parked** — PaperMono, live session, not written | **11** | **10.27 MiB** |
-| Not copied — byte-identical to bytes already in the repository | 5 | — |
-
-⚠ **The "281 MB" figure quoted for this corpus is the whole scratch subject directory.** The 174
-PDFs themselves are **195.48 MiB / 204.97 MB**; the remaining ~85 MiB is `pdftotext`
-extractions, harvested filing HTML and run logs. Both numbers are correct about different things.
-
-⚠ **The exhibits were copied out of scratch, not moved.** 24 authored records already cite
-`scratch/market-and-certification/fcc/<FCC-ID>/` as their local path, and the method forbids
-tidying another session's scratch. That corpus stays as that session left it, intact as an audit
-trail.
-
-### 2. Per-record split
-
-| Record | In repo | | Archived | | Placeholders |
-|---|---:|---:|---:|---:|---|
-| `components/espressif/esp32-s3-wroom-1` | 5 | 5.23 MiB | 13 | 25.18 MiB | ✅ 13 |
-| `components/espressif/esp32-s3-wroom-1u` | 3 | 0.77 MiB | 4 | 6.26 MiB | ✅ 4 |
-| `components/m5stack/stamp-lora-1262` | 2 | 1.19 MiB | 4 | 3.76 MiB | ✅ 4 |
-| `components/m5stack/stamp-s3a` | 2 | 2.72 MiB | 4 | 5.33 MiB | ✅ 4 |
-| `devices/lilygo/t-display-s3` | 2 | 0.44 MiB | 3 | 2.13 MiB | ✅ 3 |
-| `devices/lilygo/t-display-s3-amoled` | 4 | 4.08 MiB | 8 | 8.91 MiB | ✅ 8 |
-| `devices/lilygo/t-display-s3-long` | 2 | 1.46 MiB | 5 | 3.24 MiB | ✅ 5 |
-| `devices/lilygo/t-display-s3-pro` | 2 | 0.51 MiB | 7 | 17.29 MiB | ✅ 7 |
-| `devices/lilygo/t-display-ttgo` | 3 | 1.70 MiB | 5 | 7.25 MiB | ✅ 5 |
-| `devices/lilygo/t-dongle-s3` | 2 | 4.04 MiB | 5 | 8.35 MiB | ✅ 5 |
-| `devices/lilygo/t-qt` | 2 | 2.57 MiB | 4 | 2.11 MiB | ✅ 4 |
-| `devices/lilygo/t4-s3` | 2 | 1.29 MiB | 5 | 3.38 MiB | ✅ 5 |
-| `devices/m5stack/cap-cc1101` | 2 | 2.16 MiB | 4 | 6.01 MiB | ✅ 4 |
-| `devices/m5stack/cap-lora-1262` | 2 | 0.90 MiB | 4 | 2.34 MiB | ✅ 4 |
-| `devices/m5stack/cardputer-adv` | 2 | 1.94 MiB | 4 | 2.55 MiB | ✅ 4 |
-| `devices/m5stack/cardputer-v1.0` | 2 | 1.96 MiB | 4 | 5.65 MiB | ✅ 4 |
-| `devices/m5stack/dinmeter` | 2 | 3.85 MiB | 4 | 4.86 MiB | ✅ 4 |
-| `devices/m5stack/stamp-c6lora` | 2 | 0.59 MiB | 4 | 5.46 MiB | ✅ 4 |
-| `devices/m5stack/unit-c6l` | 2 | 1.10 MiB | 4 | 2.15 MiB | ✅ 4 |
-| `devices/xteink/x3` | 2 | 1.18 MiB | 4 | 2.87 MiB | ✅ 4 |
-| `devices/xteink/x4` | 2 | 0.98 MiB | 4 | 3.73 MiB | ✅ 4 |
-| `devices/xteink/x4-classic` | 1 | 1.48 MiB | 0 | 0.00 MiB | — |
-| `devices/xteink/x4-light` | 1 | 3.32 MiB | 2 | 1.63 MiB | ✅ 2 |
-| `devices/xteink/x4-pro` | 1 | 5.07 MiB | 1 | 0.14 MiB | ✅ 1 |
-| **Total** | **52** | **50.51 MiB** | **106** | **130.59 MiB** | **106** |
-
-`devices/m5stack/papermono` is **absent from this table by design** — see §4.
-
-### 3. Licensing — stated plainly
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** |
-| Basis | FCC equipment-authorisation exhibits are **US Government public records**, published by the Commission under 47 CFR §2.1033. The agency asserts no copyright and the exhibits are routinely republished by mirrors |
-| Scope | every FCC exhibit in this repository |
-| Disposition | `repository` (**unstaged**) for retained files; `archive` + placeholder for the rest |
-
-This **supersedes** the `unknown` recorded by the Xteink round-two pass on its twelve exhibits.
-Dated corrections are appended to the three `artifacts/certification/README.md` files that
-carried it; the original rows are unchanged.
-
-⚠ **Confidentiality embargoes are a separate matter and are unaffected.** Exhibits the applicant
-withheld were never published, so there is nothing to redistribute until their release dates —
-X4 Pro **2026-12-12**, X4 Classic **2027-01-16**, X4 Light **2027-02-09**. Schematics, block
-diagrams and operational descriptions are withheld **permanently** on all 26 filings examined.
-
-### 4. Placeholder contract
-
-Each of the 106 placeholders is a `<file>.pdf.ARCHIVED.md` at the archived file's former repo
-path, carrying **SHA-256, byte size, retrieval date, upstream publication date, FCC ID, exhibit
-type, FCC document id, grant date, applicant, test firm, licence, and five reacquisition URLs**
-ordered by measured reliability. **A reader with no archive can recover the file from the
-placeholder alone**; the archive path is recorded as a convenience only.
-
-⚠ Reacquisition requires a **non-browser User-Agent** — `fccid.io` serves 403 to Chrome and 200
-to `curl/8.5.0` — and the **`.pdf` suffix is mandatory**. Both are stated in every placeholder.
-
-### 5. Non-FCC artifacts acquired 2026-09-11
-
-| Path | Bytes | SHA-256 | Redistribution | Disposition |
-|---|---:|---|---|---|
-| `components/ultrachip/uc8253/artifacts/uc8253c-a-datasheet-rev0.6-2020-10-13-elecrow-mirror.pdf` | 1,294,916 | `bee25538177b8cc6f67c1ffe696d8fd09bda7842b42e021fb9bd41a3da91c125` | ⚠ **conditional** — cover marked *"for TFT module use only"* | repository, **unstaged** |
-| `components/ultrachip/uc8179/artifacts/uc8179c-c-datasheet-rev0.6-2019-11-26-crystalfontz-mirror.pdf` | 1,202,516 | `bf1dcef76e0d02a5683814e5f2b525bb7079e57509bf9a0754235b24fa587f50` | ⚠ **conditional** — same marking | repository, **unstaged** |
-| `components/espressif/esp32-c3/artifacts/esp32-c3-datasheet-en-v2.4.pdf` | 900,158 | `833fc000b4b3c3d39c496fcbd597fed5806956503ce7390b19cc8ae82f19f968` | unknown | repository, unstaged |
-| `components/texas-instruments/bq27220/artifacts/bq27220-datasheet-sluscb7a-rev-a.pdf` | 570,379 | `9fffe0b632cd287c9210aa1d2e71af1816b31764c11f1b62425de3a4a7cfe5f4` | unknown | repository, unstaged |
-| `components/texas-instruments/bq27220/artifacts/bq27220-technical-reference-manual-sluubd4-rev-a.pdf` | 2,768,446 | `44779f229423d649e410439d1d1a3a65026d5919cdd43112ee3a3d8d9811ead9` | unknown | repository, unstaged |
-| `components/goodix/gt911/artifacts/gt911-programming-guide-rev00-2014-08-04-crystalfontz-mirror.pdf` | 477,454 | `60c6c2284b482a7acdcd2747c47a9a7d25283235ccda8c688c10e2fd3216a98b` | ⚠⚠ **prohibited as written** — *"GOODIX CONFIDENTIAL … strictly prohibited without written consent"* | repository, **unstaged — user decision required** |
-
-Schematic-crop PNGs were added to five device `media/` directories, each with a **separate
-sibling manifest** (`manifest-schematic-crops.json`) because the existing `media/manifest.json`
-is not append-safe as JSON. 8 images across 5 records.
-
-### 6. ⚠ Decisions still requiring a user
-
-| # | Item | Question |
-|---|---|---|
-| 1 | `gt911-programming-guide-rev00-*.pdf` | Its own page 1 forbids reproduction and distribution without written consent. Keep unstaged / archive with a placeholder / keep only the metadata block? |
-| 2 | UC8253 and UC8179 datasheets | *"For TFT module use only"* is a use restriction of unclear scope, not a licence. Stage, or hold? |
-| 3 | X3 stock firmware images, 56.6 MB across 4 files | `reference-only` with a verified download recipe. Fetch and archive, or leave as a placeholder? |
-| 4 | `components/espressif/esp32-s3-wroom-1{,u}/` | These directories now hold certification evidence for a module with **no component record**. Write the records, or fold the evidence into an existing one? |
-
-Items 1–3 are carried forward from
-[`scratch/xteink/index-fragments-round2.md`](scratch/xteink/index-fragments-round2.md) §5; its
-items 3 and 4 (the 5.3 MB X4 Pro external photos, and FCC exhibits generally) are **now decided**
-by §1 and §3 above.
diff --git a/component-download-failures.txt b/component-download-failures.txt
index 79d733a..8e5d76c 100644
--- a/component-download-failures.txt
+++ b/component-download-failures.txt
@@ -970,7 +970,7 @@ normand/sk6805-ec20/sk6805-ec20-datasheet.pdf: *** RESOLVED 2026-08-30 via wmsc.
          occurrences of "SK6805". It passes every automated check. MAGIC-BYTE VALIDATION
          IS NECESSARY BUT NOT SUFFICIENT -- grep the extracted text for the part number.
          Archived, not deleted:
-         ../repo-archive/doc/hardware/components/normand/sk6805-ec20/artifacts/
+         ../hardware-doc-archive/doc/hardware/components/normand/sk6805-ec20/artifacts/
              WRONG-PART-ipixel-catalog-adafruit-4492.pdf
     https://datasheet.lcsc.com/lcsc/2110250930_Normand-SK6805-EC20_C2890036.pdf
       -> 200 but text/html anti-bot interstitial, 56572 B. Rejected.
@@ -1086,7 +1086,7 @@ omnivision/ov5640 software application notes: RESOLVED 2026-08-30 -- NEW to the
   components/omnivision/ov2640/artifacts/ov2640-camera-module-software-application-notes.pdf
     was byte-identical (4460f2f1...) to the OV2640 datasheet -- uctronics serves the same
     file from OV2640DS.pdf and OV2640_DS.pdf. There is no separate OV2640 app-notes doc.
-    Archived to ../repo-archive/doc/hardware/components/omnivision/ov2640/artifacts/
+    Archived to ../hardware-doc-archive/doc/hardware/components/omnivision/ov2640/artifacts/
       DUPLICATE-of-ov2640-datasheet.pdf
 
 ## TOOLING (this shell, 2026-08-30)
@@ -1103,7 +1103,7 @@ GD25Q64E with a GUESSED filename:
       -> 200, VALID %PDF, 1062428 B, 4 pages ... AND IT IS AN NPN TRANSISTOR DATASHEET
          (MMUN2211/2212/2213/... bias-resistor transistors). Nothing to do with flash.
   Archived, not deleted:
-    ../repo-archive/doc/hardware/components/gigadevice/gd25q64e/artifacts/
+    ../hardware-doc-archive/doc/hardware/components/gigadevice/gd25q64e/artifacts/
         WRONG-PART-mmun22xx-transistor-lcsc-C2919772.pdf
 
   *** LESSON, and this is the SECOND instance today (see the SK6805/Adafruit case above):
diff --git a/components/README.md b/components/README.md
index 805e596..c287390 100644
--- a/components/README.md
+++ b/components/README.md
@@ -26,12 +26,6 @@ Every manufacturer-specific record links back to its **[vendor sourcing guide](.
 | OmniVision Technologies | — | [OV2640](omnivision/ov2640/README.md) · [OV3660](omnivision/ov3660/README.md) · [OV5640](omnivision/ov5640/README.md) |
 | GigaDevice | — | [GD25Q64E](gigadevice/gd25q64e/README.md) |
 | Hirose Electric | — | [DF40C-30DP-0.4V(51)](hirose/df40c-30dp-0.4v/README.md) |
-| **Shanghai Awinic Technology** | — | [AW32901FCR](awinic/aw32901/README.md) · [AW35122FDR](awinic/aw35122/README.md) · [AW39112DNR](awinic/aw39112/README.md) · [AW9967DNR](awinic/aw9967/README.md) — *added 2026-09-01* |
-| **Injoinic Technology** | — | [IP2315](injoinic/ip2315/README.md) — ⚠ I²C pins shared with the LED driver; see the record |
-| **Joulwatt Technology** | — | [JW5712](joulwatt/jw5712/README.md) — ⚠ the public datasheet is a 4-page image-only scan |
-| **Puya Semiconductor** | — | [PY32L020F15U6](puya/py32l020f15u6/README.md) — the silicon behind M5Stack's M5PM1 and M5IOE1 |
-| **XMC (Wuhan Xinxin)** | — | [XM25UH128DHIQT](xmc/xm25uh128dhiqt/README.md) |
-| **FocalTech Systems** | — | [FT6336G](focaltech/ft6336g/README.md) — ⚠ datasheet omits the I²C address and the register map |
 | *unresolved / generic* | — | everything under `generic/`, below |
 
 ## All records
@@ -108,82 +102,6 @@ Also display-related: [Sitronix ST77916](sitronix/st77916/README.md) (QSPI, 360
 | [PH1.27 10-pin expansion connectors](generic/ph1.27-expansion-connectors/README.md) | board expansion interfaces |
 | [Power button](generic/power-button/README.md) | device power control interface |
 | [ESP32-S3 BOOT button](generic/esp32-s3-boot-button/README.md) | ESP32-S3 download-mode control interface |
-| [Ebyte E22-900M22S](ebyte/e22-900m22s/README.md) | LoRa transceiver module — Semtech SX1262 plus PA, LNA, RF switch and matching, stamp-hole SMD. Tanmatsu `U23` |
-| [Espressif ESP32-C6-WROOM-1-N8](espressif/esp32-c6-wroom-1/README.md) | Wi-Fi 6 / BLE 5.3 / IEEE 802.15.4 module |
-| [Goodix GT9271](goodix/gt9271/README.md) | multi-point projected-capacitive touch controller, I²C — driven through the **GT911-compatible** driver API |
-| [OPSCO SK6805-EC20](normand/sk6805-ec20/README.md) | 2020-package addressable RGB LED, NeoPixel-class single-wire, 2.0 × 2.0 mm. Filed under "Normand". Tanmatsu `U27`–`U32` |
-| [Texas Instruments BQ25895](texas-instruments/bq25895/README.md) | single-cell Li-ion switch-mode charger — NVDC power path, ADC telemetry, 3.1 A boost (OTG). Tanmatsu `U15` |
-| [Texas Instruments TPS63020](texas-instruments/tps63020/README.md) | single-inductor buck-boost, 4 A switches — holds output as input crosses it. Tanmatsu `U17` |
-| [WCH CH32V203C8T6](wch/ch32v203c8t6/README.md) | 32-bit RISC-V microcontroller, LQFP-48 — always-on management coprocessor |
-| [WCH CH334R](wch/ch334r/README.md) | 4-port USB 2.0 high-speed hub controller, QSOP-16. Tanmatsu `U5` |
-
----
-
-## M5Stack PaperMono (SKU C153) and PaperMono-Lite
-
-Records created **2026-09-01** from the published schematic PDF (`PaperMono_SCH_V0.6.2_20260522.pdf`), M5Stack's source repositories and the shipped factory firmware. No hardware was in the loop for any of them.
-
-### Power chain
-
-| Record | Category | Fitted as |
-|---|---|---|
-| [Awinic AW32901FCR](awinic/aw32901/README.md) | USB-input **OVP load switch with surge protection**, 5.95 V threshold, 120 V surge clamp | `U2`, sheet 2 |
-| [Injoinic IP2315](injoinic/ip2315/README.md) | 1S Li-ion **synchronous buck charger** with input fast-charge protocols, I²C `0x75` | `U1`, sheet 2 |
-| [Joulwatt JW5712](joulwatt/jw5712/README.md) | 600 mA **buck**, 360 nA I<sub>Q</sub> — produces `3V3_L2`, the main system rail | `U10`, sheet 2 |
-| [SSP7615-33DFR](generic/ssp7615-33dfr/README.md) | 400 mA 3.3 V **LDO** (Shanghai Siproin) — **4 instances**: `3V3_L0`, `3V3_L1`, `3V3_L2_LoRa`, `EPD_3V3_L3B` | `U4`, `U6`, `U5`, `U9`, sheet 2 |
-| [Awinic AW35122FDR](awinic/aw35122/README.md) | 1.5 A **load switch** — **4 instances**, the `L3B` domain: microSD, touch, microphone, NFC rails | `U8` · `U18` · `U21` · sheet-6 `U1` |
-| [Awinic AW39112DNR](awinic/aw39112/README.md) | 2-bit **level translator / bus gate** — **2 instances**: the charger's I²C gate and the touch bus isolator | `U3`, sheet 2 · `U19`, sheet 4 |
-| [Awinic AW9967DNR](awinic/aw9967/README.md) | Boost **WLED driver** — the e-paper frontlight, `BL_15V_L3B` | `U11`, sheet 2 |
-
-### Compute, storage and clock
-
-| Record | Category | Fitted as |
-|---|---|---|
-| [Espressif ESP32-S3R8](espressif/esp32-s3r8/README.md) | application SoC, 8 MB in-package octal PSRAM | `U12`, sheet 3 |
-| [XMC XM25UH128DHIQT](xmc/xm25uh128dhiqt/README.md) | 128 Mbit (16 MB) SPI NOR flash — **resolves the board's QIO-vs-DIO documentation conflict** | `U13`, sheet 3 |
-| [40 MHz crystal `CN4040M000157A530001`](generic/cn4040m000157a530001-40mhz-crystal/README.md) | ESP32-S3 main oscillator — ⚠ **no datasheet found** | `X1`, sheet 3 |
-| [Puya PY32L020F15U6](puya/py32l020f15u6/README.md) | Cortex-M0+ MCU, 24 KB flash / 3 KB SRAM — **the silicon behind both M5Stack custom chips** | `U7` and `U17` |
-| [M5Stack M5PM1](m5stack/m5pm1/README.md) | power-management coprocessor, I²C `0x6E` | `U7`, sheet 2 |
-| [M5Stack M5IOE1](m5stack/m5ioe1/README.md) | I/O expander coprocessor, I²C `0x4F` | `U17`, sheet 4 |
-
-### Human interface and sensing
-
-| Record | Category | Fitted as |
-|---|---|---|
-| [FocalTech FT6336G](focaltech/ft6336g/README.md) | capacitive touch controller, I²C `0x38` — ⚠ effective area inset 5 px on every edge | on the touch FPC at `J4`, sheet 4 |
-| [Bosch Sensortec BMI270](bosch-sensortec/bmi270/README.md) | 6-axis IMU, I²C `0x68`/`0x69` at 100 kHz — **`INT1` wakes the M5PM1 from full power-down** | `U15`, sheet 4 |
-| [LMD4737T261-AC02](generic/lmd4737t261-ac02-pdm-microphone/README.md) | PDM MEMS microphone — ⚠ **no datasheet found**; ⚠ both signals on ESP32-S3 strapping pins | `U1`, sheet 5 |
-| [RS-C1415MBAR](generic/rs-c1415mbar-rgb-led/README.md) | side RGB indicator — ⚠ **no datasheet found**; ⚠ **red is on/off only**, no PWM | `LED1`, sheet 5 |
-| [DKE DEPG0397BBS770F3](dke/depg0397bbs770f3/README.md) | 3.97" 4-level-greyscale e-paper panel | FPC `J5`, sheet 4 |
-
-### Display controller, radios and clock — *added 2026-09-01*
-
-| Record | Category | Fitted as | On the Lite? |
-|---|---|---|---|
-| [Solomon Systech SSD1677](solomon-systech/ssd1677/README.md) | e-paper display driver + controller, 4-wire SPI — ⚠ the only mirror is **Rev 1.0, Nov 2018, "Advance Information"**, re-processed through `PDFill` | on the panel FPC at `J5`, sheet 4 | ✅ yes |
-| [M5Stack Stamp LoRa-1262](m5stack/stamp-lora-1262/README.md) | plug-in LoRa module (Semtech SX1262), 868–923 MHz, FPC antenna — ⚠ **no module datasheet exists anywhere** | `U14`, sheet 4 | ❌ **no** |
-| [Semtech SX1262](semtech/sx1262/README.md) | the transceiver inside that module; datasheet **Rev 2.2, Dec 2024** held at `semtech/sx1262/artifacts/` | inside `U14` | ❌ **no** |
-| [STMicroelectronics ST25R3916](stmicroelectronics/st25r3916/README.md) | NFC reader/writer + card emulation, I²C `0x50`; datasheet **DS12484 Rev 8** held at `stmicroelectronics/st25r3916/artifacts/` | NFC sub-board, sheet 6 | ❌ **no** |
-| [Seiko Epson RX8130CE](seiko-epson/rx8130ce/README.md) | RTC with alarm and timer, I²C `0x32` — **its interrupt wakes the M5PM1, not the ESP32-S3**; manual **ETM50E-09** held at `seiko-epson/rx8130ce/artifacts/` | `U16`, sheet 4 | ✅ yes |
-
-> Records for all three were written on 2026-09-01 and the rows above link them.
-> Their datasheets are hashed in
-> [`devices/m5stack/papermono/sources.md`](../devices/m5stack/papermono/sources.md)
-> (S22, S23, S24). Note the RX8130CE manual M5Stack mirrors is **Epson's English
-> `ETM50E-09` served under a `_cn` filename** — `_cn` denotes Epson's China
-> site, not a Chinese-language edition; no Chinese edition exists.
-
-The **On the Lite?** column is the whole difference between the two SKUs: the
-[PaperMono-Lite](../devices/m5stack/papermono-lite/README.md) drops NFC and LoRa
-and nothing else. See that record for what does and does not carry over.
-
-Three findings from this set are worth surfacing at index level because they are easy to hit and hard to diagnose:
-
-- **The IP2315 charger is deliberately kept *off* the shared I²C bus** and connected only for the duration of a transaction. A bus scan will not find `0x75`. The reason is in the [IP2315 record](injoinic/ip2315/README.md#3--the-ic-pins-are-the-led-driver-pins--this-is-the-whole-hazard): its I²C pins are the battery-level LED driver pins, its mode selection depends on them being pulled to V<sub>BAT</sub>, and a read that fails to NACK its last byte can hold the bus.
-- **M5GFX drives the frontlight dimming input at 5 kHz, below the AW9967's specified 10 kHz minimum.** [Details](awinic/aw9967/README.md#62--m5gfx-drives-the-dimming-input-at-half-the-datasheets-minimum-frequency). Both numbers are direct reads; the consequence is unmeasured.
-- **The board is wired for QIO flash even though the shipped image says DIO.** All four data lines are routed and the flash ships with `QE = 1` set at the factory. [Resolution](xmc/xm25uh128dhiqt/README.md#5--resolving-the-qiodio-conflict).
-
-Four parts on this board could not be attributed to a manufacturer despite systematic searching. Their records carry full search ledgers so the work is not repeated: the [crystal](generic/cn4040m000157a530001-40mhz-crystal/README.md#6-datasheet-search--negative-result), the [PDM microphone](generic/lmd4737t261-ac02-pdm-microphone/README.md#5-datasheet-search--negative-result) and the [RGB LED](generic/rs-c1415mbar-rgb-led/README.md#6-datasheet-search--negative-result); the [JW5712](joulwatt/jw5712/README.md#8-datasheet-status--read-this-before-relying-on-a-number-here) has a datasheet that is an image-only scan.
 
 ---
 
@@ -193,456 +111,3 @@ Four parts on this board could not be attributed to a manufacturer despite syste
 - [Vendor sourcing guides](../vendors/README.md) — per-manufacturer document retrieval
 - [Espressif ecosystem map](../guides/espressif/ecosystem-and-product-lines.md) — choosing between ESP32 family parts
 - [Clones and variants](../guides/markets/clones-and-variants.md) — when the fitted part is not the documented one
-
----
-
-## M5Stack PaperMono — component coverage completed *(added 2026-09-01)*
-
-A **290-component, 230-designator census** of `PaperMono_SCH_V0.6.2_20260522.pdf`
-is published as
-[`devices/m5stack/papermono/bill-of-materials.md`](../devices/m5stack/papermono/bill-of-materials.md).
-The sixteen records below close the gap between that census and this index. Every
-one is schematic-derived; **no hardware was in the loop for any of them.**
-
-### New manufacturers
-
-| Manufacturer | Sourcing guide | Parts here |
-|---|---|---|
-| **Panasonic Industry** | — | [AXE512127D](panasonic/axe512127d/README.md) · [AXE612124D](panasonic/axe612124d/README.md) — an A4S 0.4 mm socket/header **pair** |
-| **ROHM** | — | [RB162VAM-20TR](rohm/rb162vam-20tr/README.md) — ⚠ **Not Recommended for New Designs** |
-| **Jiangsu Changjing (CJ)** | — | [CJ2310](changjing/cj2310/README.md) · [CJ3439KDW](changjing/cj3439kdw/README.md) |
-| **XUNPU** | — | [TYPEC-302-BRP16SC08](generic/typec-302-brp16sc08/README.md) · [BTB0.408-10PLBDR-G41](generic/btb0.408-10plbdr-g41/README.md) — ⚠ the latter has **no datasheet at all** |
-| **Shikues** | — | [SK2301AAT](generic/sk2301aat/README.md) · [SK2302AAT](generic/sk2302aat/README.md) |
-| **TECH PUBLIC** | — | [ESD5311](generic/esd5311/README.md) |
-| **YXC Crystal Oscillators** | — | [XL7EL89CMI-111YLC 27.12 MHz](generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md) |
-
-### Connectors — published interfaces, so the pinouts are the point
-
-| Record | Category | Fitted as | On the Lite? |
-|---|---|---|---|
-| [XUNPU TYPEC-302-BRP16SC08](generic/typec-302-brp16sc08/README.md) | USB-C 3.1 receptacle, 16 contacts, 5 A / **5 V** | **`USB`**, sheet 2 | ✅ yes |
-| [FPC0.5-SMT-24P-B](generic/fpc0.5-smt-24p-b/README.md) | 24-way 0.5 mm FPC — the e-paper panel connector; **manufacturer unidentified** | `J5`, sheet 4 | ✅ yes |
-| [Panasonic AXE512127D](panasonic/axe512127d/README.md) | A4S **socket**, 0.4 mm pitch, 12 contacts, 0.8 mm mated height | `J6`, sheet 4 | ✅ yes |
-| [Panasonic AXE612124D](panasonic/axe612124d/README.md) | A4S **header** — the mating half | `J1`, sheet 5 | ✅ yes |
-| [BTB0.408-10PLBDR-G41](generic/btb0.408-10plbdr-g41/README.md) | 0.4 mm board-to-board to the NFC sub-board, **both halves** | `J3` sheet 4 · `J1` sheet 6 | ❌ **no** |
-
-### Protection and discretes
-
-| Record | Category | Instances | On the Lite? |
-|---|---|---|---|
-| [ESD5311](generic/esd5311/README.md) | bidirectional ESD suppressor, 0.3 pF, DFN1006-2 | **12** — `TVS1`/`TVS2` (USB), `TVS3`–`TVS9` (microSD, **every line**), `DR1`–`DR3` (buttons) | ✅ yes |
-| [Shikues SK2301AAT](generic/sk2301aat/README.md) | **P-channel** MOSFET, −20 V, SOT-523 | `Q5` sheet 2 — the USB-gated `VBAT_DET` high-side switch | ✅ yes |
-| [Shikues SK2302AAT](generic/sk2302aat/README.md) | **N-channel** MOSFET, 20 V, SOT-523 | `Q2` sheet 2 (USB-presence inverter) · `Q3` sheet 4 (**buzzer driver**) | ✅ yes |
-| [Changjing CJ2310](changjing/cj2310/README.md) | N-channel MOSFET, **60 V**, SOT-23 | `Q4` sheet 4 — the **e-paper bias-converter switch** | ✅ yes |
-| [Changjing CJ3439KDW](changjing/cj3439kdw/README.md) | **complementary N+P pair**, SOT-363 | `Q1` sheet 2 — the **gated battery-sense divider** | ✅ yes |
-| [ROHM RB162VAM-20TR](rohm/rb162vam-20tr/README.md) | Schottky, 20 V / 1 A, **ultra-low V<sub>F</sub> 0.36 V** | `D2` sheet 2 — frontlight boost rectifier | ✅ yes |
-| [1N4148WS](generic/1n4148ws/README.md) | switching diode, SOD-323 | `D3` sheet 4 — buzzer flyback clamp | ✅ yes |
-| [1N5819WS](generic/1n5819ws/README.md) | Schottky, 40 V / 1 A, SOD-323 | `D4`, `D5`, `D6` sheet 4 — e-paper boost + inverting charge pump | ✅ yes |
-
-### Crystal, sensor and cell
-
-| Record | Category | Fitted as | On the Lite? |
-|---|---|---|---|
-| [XL7EL89CMI-111YLC 27.12 MHz](generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md) | NFC carrier reference — **27.12 MHz = 2 × 13.56 MHz, fixed by ISO 14443** | `X1`, sheet 6 | ❌ **no** |
-| [`100K-RNTC` thermistor](generic/100k-rntc-thermistor/README.md) | charger temperature qualification; **part unidentified, B constant unknown** | `R15`, sheet 2 | ✅ yes |
-| [PaperMono 1150 mAh Li-ion cell](generic/papermono-1150mah-liion-cell/README.md) | the shipped battery; maker unidentified | at `J2`, sheet 2 | ✅ yes — **same capacity on both SKUs** |
-
-### Five findings worth surfacing at index level
-
-- **⚠ The NTC does not measure the cell.** `J2` is a **2-pin** connector carrying
-  only + and −, and `100K-RNTC` is `R15`, a **mainboard** part on the charger's
-  `NTC` pin. Several places in the device record say the battery is "NTC-sensed
-  at `J2`"; the schematic does not support a thermistor in the pack. Recorded as
-  a conflict, **not resolved** — `R15` may be thermally coupled to the cell by
-  layout, which no schematic can show.
-  [Detail](generic/100k-rntc-thermistor/README.md#4--conflict-this-does-not-measure-the-cell) ·
-  [BOM §11](../devices/m5stack/papermono/bill-of-materials.md#11--conflict-raised-by-this-pass--the-ntc-does-not-measure-the-cell)
-- **`R17` = 15 kΩ is on `ICHGSET`, `R18` = `NC` is on `LED3`** — resolving an
-  open question in the [IP2315 record](injoinic/ip2315/README.md). The conflict it
-  raises gets sharper, not softer: **15 kΩ is not a tabulated `ICHGSET` value.**
-- **There is no `N1` gap, because there is no `N` series.** `CON2_SMD` (`J2`'s
-  footprint label) and `PIN1`…`PIN24` (`J5`'s pin-name labels) are mis-read as
-  markers by the Altium PDF parser. Separately, `pdftotext` **drops a glyph from
-  eight `CO` markers on sheet 6**, hiding eight capacitors that are really there.
-  Third, a designator with **no digits** — the USB-C receptacle is **`USB`**, not
-  a second `U1` — is dropped by a `[A-Z]+[0-9]+` filter. The only genuine gaps on
-  the whole board are **`R46`, `R48`, `R55`, `R56`, `R57`**.
-  [Detail](../devices/m5stack/papermono/bill-of-materials.md#21--two-parser-artefacts-had-to-be-repaired--and-one-of-them-refutes-a-claim)
-- **⚠ The two halves of the NFC board-to-board connector disagree about pin
-  numbering** — `J3` puts every signal on an even pin, `J1` on an odd pin, and
-  both carry the *same* part string. Taken literally, pin-for-pin mating would
-  short 3V3 to ground. Unresolved; **do not assume `J3` pin *N* = `J1` pin *N***.
-  [Detail](generic/btb0.408-10plbdr-g41/README.md#33--unresolved-conflict--the-two-halves-do-not-agree-on-pin-numbering)
-- **USB-C has 5.1 kΩ R<sub>d</sub> on *both* CC lines** (`R4` on `CC1`, `R14` on
-  `CC2`) while the IP2315's own CC pins are depopulated. Two independent reasons
-  there is no USB-PD, plus a third: the AW32901 OVP trips at 5.95 V.
-  [Detail](generic/typec-302-brp16sc08/README.md#32--the-cc-arrangement-a-plain-sink-and-no-usb-pd--twice-over)
-
-### Retrieval note that will recur
-
-**`www.lcsc.com/datasheet/*.pdf` returns HTTP 200 with `text/html`.** Five of the
-nine datasheets acquired for this pass failed there and succeeded after a
-mechanical host rewrite:
-
-```
-www.lcsc.com/datasheet/lcsc_datasheet_<stamp>_<name>_<code>.pdf
-  ->  wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/<stamp>_<name>_<code>.pdf
-```
-
-**Check the `%PDF` magic bytes; neither the status code nor the `.pdf` extension
-proves anything.** No user-agent rotation helps — it is the wrong host, not
-bot-blocking. Also: **DuckDuckGo-lite, Mojeek and searx.be all blocked or
-captcha'd `curl` on 2026-09-01**, and the only search channel that worked for
-these Chinese-market discretes was **JLCPCB's SMT parts API**. ROHM's own CDN
-404s for its NRND parts; **Octopart's mirror served the document under the same
-numeric ID that IBS Electronics 403s on**. All of this belongs in
-[`ai-crawler-site-access-table.md`](../ai-crawler-site-access-table.md).
-
-**Three parts have no datasheet and no maker, and the search ledgers are
-recorded so the work is not repeated:**
-[`FPC0.5-SMT-24P-B`](generic/fpc0.5-smt-24p-b/README.md#5-datasheet-search--negative-result) (a library designation, not an orderable part),
-[`BTB0.408-10PLBDR-G41`](generic/btb0.408-10plbdr-g41/README.md#5-datasheet-search--negative-result) (XUNPU identified, `dataManualUrl` is `None`),
-and the [`100K-RNTC`](generic/100k-rntc-thermistor/README.md#11--100k-rntc-is-a-description-not-a-part-number) and
-[1150 mAh cell](generic/papermono-1150mah-liion-cell/README.md#11-what-is-not-established), whose schematic strings carry no vendor token to search on.
-
----
-
-## Waveshare ESP32-S3-ePaper-3.97 — component coverage *(added 2026-09-01)*
-
-Six records reached from the
-[ESP32-S3-ePaper-3.97](../devices/waveshare/esp32-s3-epaper-3.97/README.md) pass —
-the knowledge base's first Waveshare **e-paper** board. Four are new, one is a stub
-written over an artifact that had been sitting here unattached since 2026-08-23, and
-one is an identity-only record with no datasheet yet.
-
-### New manufacturers
-
-| Manufacturer | Part | Datasheet held | Note |
-|---|---|---|---|
-| **X-Powers** | [AXP2101](x-powers/axp2101/README.md) | **V1.4 EN**, 1 554 740 B | Single-cell PMIC — charger, multi-rail regulator, power-key controller, backup-cell charger |
-| **Sensirion** | [SHTC3](sensirion/shtc3/README.md) | yes, revision `unknown` | Humidity/temperature. **Fixed I²C address `0x70`** — two cannot share a bus |
-| **Nsiway** | [NS4150B](nsiway/ns4150b/README.md) | **none — `reference-only`** | Class-D amplifier. Part number read from the schematic; *everything else about it is unestablished* |
-| **Waveshare** *(as a part maker, not a board vendor)* | [3.97inch e-Paper panel](waveshare/3.97inch-e-paper/README.md) | **manual Rev 1.0, 2025-04-24** | The panel itself, filed as a component because it is sold standalone too |
-
-### Extended or newly written
-
-| Part | What changed |
-|---|---|
-| [ES8311](everest-semiconductor/es8311/README.md) | **New record.** Mono voice codec, joins the existing [ES8156](everest-semiconductor/es8156/README.md) |
-| [QMI8658A](qst/qmi8658a/README.md) | **New stub over a pre-existing artifact.** The Rev A datasheet had been held since 2026-08-23 with no record page beside it |
-| [SSD1677](solomon-systech/ssd1677/README.md) | Second **Used By** entry — a board from a *different vendor* with a *different panel supplier* at the same 3.97" size |
-| [PCF85063A](nxp/pcf85063a/README.md) | Second **Used By** entry, plus a **second copy of the datasheet** |
-| [ESP32-S3R8](espressif/esp32-s3r8/README.md) | Third **Used By** entry — fitted here as an `ESP32-S3-WROOM-1-N16R8` module |
-
-### Four findings worth surfacing at index level
-
-**1 — The vendor names a chip that does not appear to exist.** Waveshare's storefront
-*and* its official documentation call the board's PMIC a **"TG28"**. The schematic
-labels it **`AXP2101`** with X-Powers pin names throughout, and Waveshare's own
-firmware drives it through XPowersLib's AXP2101 path. No datasheet or product page for
-a "TG28" was found. **No `tg28` record was created** — that would be a part number
-promoted from marketing copy.
-
-**2 — Two 3.97-inch e-paper panels from different vendors match to 0.01 mm.**
-[Waveshare's](waveshare/3.97inch-e-paper/README.md) and
-[DKE's DEPG0397BBS770F3](dke/depg0397bbs770f3/README.md) share active area, DPI (235),
-resolution and **the same SSD1677 controller**. Whether they are the same panel is
-[unresolved](../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws8--is-this-the-same-panel-as-the-papermonos)
-— Waveshare publishes no panel part number. The two manuals also state the
-gate/source orientation **opposite ways round**.
-
-**3 — A third confirmation that Waveshare's `common/` mirrors run stale.** Its
-PCF85063A copy is **Rev. 6 (2015)** against NXP's **Rev. 7 (2018)** — different size,
-different hash. Both kept. Always hash a `files.waveshare.com/wiki/common/` PDF
-against the manufacturer's copy.
-
-**4 — A panel datasheet with a text layer that lies.** The 3.97-inch manual embeds two
-subset fonts at uniform code-point offsets (+29 and +26), so naive extraction produces
-text that is *human-legible but wrong* — the most dangerous PDF failure mode. Decoded
-and validated against a known cover heading before any value was transcribed; that is
-what recovered `Driver IC: SSD1677`. Method and tooling in
-[the device's `commands.md`](../devices/waveshare/esp32-s3-epaper-3.97/commands.md)
-and [`vendors/waveshare` §9.3](../vendors/waveshare/README.md).
-
----
-
-## Seven-pass component sweep *(added 2026-09-04 — 2026-09-07)*
-
-Records added by the Xteink, M5Stack DinMeter, M5Stack Cardputer, M5Stack LoRa-expansion,
-LilyGO T-Display K230, LilyGO T-Display-S3 and LoRa-generation-lineage passes. **No hardware
-was in the loop for any of them**; every claim is schematic-, datasheet- or source-derived.
-Where two passes reached the same manufacturer the entry below is merged.
-
-### New manufacturers
-
-| Manufacturer | Sourcing guide | Parts here |
-|---|---|---|
-| **UltraChip** | — | [UC8253](ultrachip/uc8253/README.md) · [UC8179](ultrachip/uc8179/README.md) · [UC8279](ultrachip/uc8279/README.md) — e-paper display controllers |
-| **CellWise** | — | [CW2017](cellwise/cw2017/README.md) — battery fuel gauge |
-| **Canaan Creative (Kendryte)** | [vendors/canaan](../vendors/canaan/README.md) | [K230](canaan/k230/README.md) — RISC-V AIoT SoC. **This repository's first RISC-V part** |
-| **Raydium Semiconductor** | — | [RM69A10](raydium/rm69a10/README.md) · [RM67162](raydium/rm67162/README.md) · [RM690B0](raydium/rm690b0/README.md) — AMOLED display drivers |
-| **GalaxyCore** | — | [GC2093](galaxycore/gc2093/README.md) — CMOS image sensor |
-| **Realtek Semiconductor** | — | [RTL8189FS](realtek/rtl8189fs/README.md) · [RTL8152B](realtek/rtl8152b/README.md) — Wi-Fi and USB Ethernet |
-| **Nordic Semiconductor** | — | [nRF52840](nordic-semiconductor/nrf52840/README.md) · [nRF9151](nordic-semiconductor/nrf9151/README.md) — BLE and cellular IoT |
-| **ASAIR / Guangzhou Aosong** | — | [AHT20](asair/aht20/README.md) — environmental sensor |
-| **Lontium Semiconductor** | — | [LT9611](lontium/lt9611/README.md) — display bridge |
-| **AXS Technology** | — | [AXS15231B](axs-technology/axs15231b/README.md) — display driver **and** touch controller in one die |
-| **Chipone** | — | [CO5300](chipone/co5300/README.md) — AMOLED driver, also referenced as ICNA3311 |
-| **Shenghe Microelectronics** | — | [SH8601Z](shenghe-microelectronics/sh8601z/README.md) · [SH8501B](shenghe-microelectronics/sh8501b/README.md) — **settles who makes the SH86xx parts** |
-| **Nanjing Top Power** | — | [TP4065](nanjing-top-power/tp4065/README.md) — linear Li-ion charger |
-| **Semtech** | [vendors/semtech](../vendors/semtech/README.md) | six new transceiver records — see *LoRa silicon generations* below |
-| **M5Stack** *(as a module maker)* | [vendors/m5stack](../vendors/m5stack/README.md) | [Stamp-S3](m5stack/stamp-s3/README.md) · [Stamp-S3A](m5stack/stamp-s3a/README.md) |
-| **Microne** | — | [ME3116AM6G](microne/me3116am6g/README.md) — 6–36 V → 5 V buck. ⚠ schematic-only, **no datasheet located** |
-| **Belling** | — | [BL8075CB5TR33](belling/bl8075/README.md) — 3.3 V LDO. ⚠ schematic-only |
-| **Murata** | — | [MUN3CAD01-SC](murata/mun3cad01-sc/README.md) — 1 A µPOL module, the Stamp-S3's regulator |
-| **Knowles** | — | [SPM1423HM4H-B](knowles/spm1423hm4h-b/README.md) — PDM MEMS microphone |
-| **Worldsemi** | — | [WS2812](worldsemi/ws2812/README.md) — addressable RGB LED |
-| **Consonance** *(inferred)* | — | [CN809](consonance/cn809/README.md) — voltage supervisor / reset generator |
-| **NSIWAY** | — | [NS4168](nsiway/ns4168/README.md) — I²S-input class-D amplifier |
-| **ZhongKeWei** | — | [ATGM336H-6N](zhongkewei/atgm336h-6n/README.md) · [AT6668](zhongkewei/at6668/README.md) — GNSS module and the chipset inside it |
-| **Infineon** | — | [BGS13SN8](infineon/bgs13sn8/README.md) — SP3T RF switch |
-| **Ebyte** | — | [E220 series](ebyte/e220-400t22s/README.md) — LLCC68 **UART modem** modules |
-
-### Xteink pocket e-readers — *added 2026-09-04*
-
-| Part | Where |
-|---|---|
-| [`ultrachip/uc8253`](ultrachip/uc8253/README.md) | Xteink X3, original production |
-| [`ultrachip/uc8179`](ultrachip/uc8179/README.md) | Xteink X4 / X4 Pro / X4 Classic, newer batches |
-| [`ultrachip/uc8279`](ultrachip/uc8279/README.md) | Xteink X3 (as UC8279d) and the X4 family; EEGO A4 as UC8279C |
-| [`cellwise/cw2017`](cellwise/cw2017/README.md) | Xteink X4 Pro, X4 Classic |
-| [`espressif/esp32-c3`](espressif/esp32-c3/README.md) | Xteink X3, X4. **Family-level identification only** — the exact package variant has never been read |
-| [`texas-instruments/bq27220`](texas-instruments/bq27220/README.md) | Xteink X3. The family's best battery instrumentation — no profile upload needed |
-| [`unidentified/xteink-x3-x4/`](unidentified/xteink-x3-x4/README.md) | Four evidenced-but-unidentified parts on the ESP32-C3 Xteink boards: a Puya 128 Mbit flash, a DS-series RTC (**three sources disagree**), an ISO 14443A NFC tag (**purpose established, part not**), and a TP4056-class charger |
-
-Family trait worth knowing: **UC81xx parts answer `VER (0x70)` and `FLG (0x71)` register reads;
-the Solomon Systech SSD16xx family does not.** That asymmetry is what makes runtime
-panel-controller detection possible on boards shipping more than one variant. And the CW2017
-**reports 0 % until the host uploads an 80-byte BATINFO profile**, and has **no current
-register**, so charge state must come from a separate GPIO.
-
-### M5Stack DinMeter (K134 / K134-V11) — *added 2026-09-04*
-
-| Part | Record | Function |
-|---|---|---|
-| **Stamp-S3** | [`m5stack/stamp-s3`](m5stack/stamp-s3/README.md) | ESP32-S3FN8 core module, SKU `S007`, board rev v0.2. 8 MB flash, **no PSRAM**, 23 GPIOs, USB-C, WS2812B-2020 on GPIO21, rear 8/12-pin LCD FPC. **`[EOL]`** |
-| **Stamp-S3A** | [`m5stack/stamp-s3a`](m5stack/stamp-s3a/README.md) | The successor, SKU `S007-V033`, board rev **v0.3.3**. Same SoC/flash/PSRAM/pinout; new regulator, rebuilt antenna match, and the **RGB LED moved to a switched rail needing GPIO38** |
-| **ST7789V2** | [`sitronix/st7789v2`](sitronix/st7789v2/README.md) | 240×320 TFT controller; the DinMeter's 1.14" 135×240 panel. Datasheet v1.0 (2016/11) retained. GRAM gap +52/+40, `INVON` required |
-| **ST7789P3** | [`sitronix/st7789p3`](sitronix/st7789p3/README.md) | DinMeter v1.1's controller. ⚠ **No datasheet exists anywhere**; command-compatibility with ST7789V2 is inferred, not verified |
-| **BM8563** | [`generic/bm8563`](generic/bm8563/README.md) | I²C RTC, 0x51, PCF8563-equivalent. CN-only datasheet — and it carries a stray `MAX1937` string, i.e. a derived document |
-| **TP4057** | [`generic/tp4057`](generic/tp4057/README.md) | 500 mA linear Li-ion charger, SOT23-6, **4.24 V float** |
-| **ME3116AM6G** | [`microne/me3116am6g`](microne/me3116am6g/README.md) | 6–36 V → 5 V buck. ⚠ Schematic-only; **no datasheet located** |
-| **SY7088** | [`silergy/sy7088`](silergy/sy7088/README.md) | Battery → 5 V boost. ⚠ Schematic-only. Its own divider computes to **≈5.38 V** against a "5 V" spec |
-| **BL8075CB5TR33** | [`belling/bl8075`](belling/bl8075/README.md) | 3.3 V LDO. ⚠ Schematic-only |
-| **MUN3CAD01-SC** | [`murata/mun3cad01-sc`](murata/mun3cad01-sc/README.md) | 1 A µPOL module — the **Stamp-S3's** regulator. ⚠ Still listed on the Stamp-S3**A** page, where it is not fitted |
-| **SGM2578** | [`sgmicro/sgm2578`](sgmicro/sgm2578/README.md) | Load switch, Stamp-S3 backlight rail. ⚠ Schematic-only |
-| [`unidentified/m5stack-dinmeter/rotary-encoder`](unidentified/m5stack-dinmeter/rotary-encoder/README.md) | — | **The orange knob.** No part number in the schematic or on either product page. Quadrature GPIO41/40 + switch GPIO42 on a 7-pad connector `J5` |
-| [`unidentified/m5stack-dinmeter/buzzer`](unidentified/m5stack-dinmeter/buzzer/README.md) | — | `LS1` carries no part number or value. Magnetic (flyback diode fitted), passive, GPIO3 via an SS8050 |
-| [`unidentified/m5stack-stamp-s3a/dcdc-u4`](unidentified/m5stack-stamp-s3a/dcdc-u4/README.md) | — | The Stamp-S3A's regulator. 8 balls, `IOUT: 0~0.6A`, external 2.2 µH inductor. ⚠ **A later pass identifies this as a [JoulWatt JW5712](joulwatt/jw5712/README.md)** — see [`scratch/index-merge/corrections-requiring-review.md`](../scratch/index-merge/corrections-requiring-review.md) |
-
-### M5Stack Cardputer family — *added 2026-09-04*
-
-| Part | Manufacturer | Function | Used by |
-|---|---|---|---|
-| [TCA8418](texas-instruments/tca8418/README.md) | Texas Instruments | I²C keypad scanner, 8×10 matrix, event FIFO | Cardputer ADV (`0x34`, 7×8), CardputerZero (`0x34`, 46 keys) |
-| [74HC138](generic/74hc138/README.md) | generic logic | 3-to-8 decoder used as a keyboard column driver | Cardputer v1.0, v1.1 |
-| [ESP32-S3FN8](espressif/esp32-s3fn8/README.md) | Espressif | ESP32-S3 with 8 MB in-package flash and **no PSRAM** | Stamp-S3 / Stamp-S3A, all ESP32 Cardputers |
-| [MSM381A3729H9BP](memsensing/msm381a3729h9bp/README.md) | MEMSensing | analog MEMS microphone | Cardputer ADV |
-| [SPM1423HM4H-B](knowles/spm1423hm4h-b/README.md) | Knowles | PDM MEMS microphone | Cardputer v1.0, v1.1 |
-| [NS4168](nsiway/ns4168/README.md) | NSIWAY | I²S-input class-D amplifier | Cardputer v1.0, v1.1 |
-| [WS2812](worldsemi/ws2812/README.md) | Worldsemi | addressable RGB LED | Stamp-S3, Stamp-S3A |
-| [CN809](consonance/cn809/README.md) | Consonance (*inferred*) | voltage supervisor / reset generator | all Cardputer mainboards |
-| [SY8089](silergy/sy8089/README.md) | Silergy | 2 A synchronous buck, the 3.3 V rail | all Cardputer mainboards |
-| [LP3218DT1G](unidentified/cardputer/lp3218dt1g/README.md) | **unidentified** | power-path MOSFET ×3 | all Cardputer mainboards |
-
-### M5Stack LoRa, sub-GHz and NFC expansions — *added 2026-09-04*
-
-| Record | Category |
-|---|---|
-| [Texas Instruments CC1101](texas-instruments/cc1101/README.md) | Sub-1 GHz FSK/OOK transceiver, QFN-20. Datasheet held (M5Stack mirror) |
-| [ST STM32WLE5](stmicroelectronics/stm32wle5/README.md) | Cortex-M4 + Semtech sub-GHz radio on one die; used as an AT-command LoRaWAN modem |
-| [ZhongKeWei ATGM336H-6N](zhongkewei/atgm336h-6n/README.md) | 18-pad multi-constellation GNSS module. Datasheet held (M5Stack mirror) |
-| [ZhongKeWei AT6668](zhongkewei/at6668/README.md) | The chipset inside the ATGM336H; CASIC binary protocol (spec archived) |
-| [Diodes PI4IOE5V6408](diodes-incorporated/pi4ioe5v6408/README.md) | I²C GPIO expander @ 0x43 — controls the RF switch on three M5Stack LoRa products |
-| [Analog Devices MAX2659](analog-devices/max2659/README.md) | GNSS low-noise amplifier |
-| [Infineon BGS13SN8](infineon/bgs13sn8/README.md) | SP3T RF switch — two of them do the Cap CC1101's band selection |
-| [Ebyte E220 series](ebyte/e220-400t22s/README.md) | LLCC68 **UART modem** modules — explicitly *not* SPI-attached, therefore not Meshtastic-capable |
-| [RF balun B0310J50100AHF](generic/rf-balun-b0310j50100ahf/README.md) | Wideband balun on the CC1101's differential port — manufacturer unidentified |
-| [GNSS ceramic patch antenna (ANT1818-04)](generic/gnss-ceramic-patch-antenna/README.md) | 18×18×4 mm L1 patch — distinct from the 2.4 GHz `generic/ceramic-antenna` record |
-| [RP-SMA vs SMA antenna connectors](generic/rp-sma-and-sma-antenna-connectors/README.md) | The `SMA-KE` designation, and M5Stack's unresolved self-contradiction about Cap connectors |
-
-Five **existing** records were extended rather than added by that pass: `semtech/sx1262` (four
-new Used By entries and the **1.8 V vs 3.0 V TCXO conflict**), `m5stack/stamp-lora-1262` (§6A
-names module pins 11–13 `GND`/`ANT`/`GND`, and a module schematic is now held),
-`stmicroelectronics/st25r3916` (the same chip strapped to **SPI** rather than I²C),
-`joulwatt/jw5712` (the **same regulator, host-enabled on one Cap and always-on on the other**)
-and `generic/xl7el89cmi-111ylc-27.12mhz-crystal`.
-
-### LoRa silicon generations — Semtech — *added 2026-09-04*
-
-Six new records under `components/semtech/`, supporting
-[`guides/hardware/lora-radio-generations.md`](../guides/hardware/lora-radio-generations.md).
-
-| Record | Category |
-|---|---|
-| [`semtech/lr2021`](semtech/lr2021/README.md) | **LoRa Plus™ LR2021 — the fourth-generation LoRa transceiver.** Dual-band (150–960 MHz + 1.5–2.5 GHz), FLRC to 2.6 Mbps, multi-SF receive, BLE/802.15.4/Z-Wave/Sigfox PHYs, SATCOM. ⚠ Not a drop-in for anything: 16-bit opcodes, 24-bit registers, two FIFOs, mandatory boot-time PRAM upload |
-| [`semtech/lr1121`](semtech/lr1121/README.md) | Gen 3, LoRa Connect. Multi-band + **AES-128 crypto engine and secure key store**. ⚠ **No GNSS or Wi-Fi scanner** despite the LoRa Edge part number — light record, datasheet gated |
-| [`semtech/lr11x0`](semtech/lr11x0/README.md) | Gen 3, LoRa Edge — **LR1110 and LR1120**. GNSS + passive Wi-Fi scanning, resolved by a **cloud solver**, plus the crypto engine. Light record, datasheet gated |
-| [`semtech/sx1276`](semtech/sx1276/README.md) | **Gen 1 (2013).** Register-mapped SPI, no `BUSY`, two overlapping register maps. The *before* picture for the SX127x → SX126x break. Rev 5 datasheet + both errata notes retained |
-| [`semtech/llcc68`](semtech/llcc68/README.md) | Gen 2, **pin-to-pin compatible with the SX1262** — ⚠ and 19 dB worse link budget. **Cannot do SF12 at all**; no bandwidth below 100 kHz. The real substitution trap |
-| [`semtech/sx1268`](semtech/sx1268/README.md) | Gen 2, pin-compatible with the SX1262, ⚠ **410–810 MHz only** — 868 and 915 MHz are out of range |
-
-⚠ **The LR2021's interrupt DIO is `DIO11`, not `DIO1`.** Firmware that hard-codes `DIO1`
-silently sees no interrupts on an LR2021 board — which matters because at least one board
-([LilyGO T-Display K230](../devices/lilygo/t-display-k230/README.md)) ships either radio on the
-same host GPIO. **No board documented here uses the LR2021 as its default radio yet.**
-
-### LilyGO T-Display K230 — *added 2026-09-04*
-
-| Record | Note |
-|---|---|
-| [`canaan/k230`](canaan/k230/README.md) | Kendryte K230 RISC-V AIoT SoC — **this repository's first RISC-V part** |
-| [`raydium/rm69a10`](raydium/rm69a10/README.md) | 4.1″ AMOLED display driver |
-| [`galaxycore/gc2093`](galaxycore/gc2093/README.md) | 2 MP MIPI CMOS image sensor |
-| [`realtek/rtl8189fs`](realtek/rtl8189fs/README.md) · [`realtek/rtl8152b`](realtek/rtl8152b/README.md) | SDIO Wi-Fi and USB Ethernet |
-| [`nordic-semiconductor/nrf52840`](nordic-semiconductor/nrf52840/README.md) · [`nordic-semiconductor/nrf9151`](nordic-semiconductor/nrf9151/README.md) | BLE companion, and the LTE-M/GNSS modem on the keyboard base |
-| [`asair/aht20`](asair/aht20/README.md) | Temperature/humidity sensor at `0x38` on the base board's I²C4 |
-| [`lontium/lt9611`](lontium/lt9611/README.md) | MIPI-DSI → HDMI bridge |
-| [`goodix/gt9895`](goodix/gt9895/README.md) | Goodix "Berlin" touch controller. **Not** compatible with the GT911/GT9271 driver |
-| [`texas-instruments/bq25896`](texas-instruments/bq25896/README.md) | I²C charger; **sibling of the existing BQ25895, not the same part** |
-| [`analog-devices/max98357a`](analog-devices/max98357a/README.md) | I²S Class-D amplifier |
-| [`xlsemi/xl9555`](xlsemi/xl9555/README.md) | 16-bit I²C GPIO expander. **README added 2026-09-04** over an `artifacts/` directory that predates the pass |
-| [`unidentified/t-display-k230`](unidentified/t-display-k230/README.md) | Six unresolved parts on that board |
-
-⚠ **`espressif/esp32-s3r8` was deliberately *not* given a Used-By row for this board**, even
-though LilyGO's wiki claims an ESP32-S3-R8 co-processor. The claim is unverified and
-contradicted by the board's own BSP; see that device record's `GC-2`.
-
-### LilyGO T-Display-S3 family — *added 2026-09-07*
-
-| Record | Category | Used by | Note |
-|---|---|---|---|
-| [AXS Technology AXS15231B](axs-technology/axs15231b/README.md) | combined AMOLED/LCD driver **and** capacitive touch controller in one die; QSPI + I²C `0x3B` | LilyGO T-Display-S3 Long | ⚠ datasheet carries an explicit no-redistribution notice — keep unstaged |
-| [Chipone CO5300](chipone/co5300/README.md) | AMOLED driver, QSPI; also referenced as ICNA3311 | LilyGO 1.64″ / 1.43″ / 1.75″ AMOLED | datasheet **archived** (12.6 MiB) with placeholder |
-| [Raydium RM67162](raydium/rm67162/README.md) | 240×536 AMOLED driver, QSPI | LilyGO T-Display-S3 AMOLED, AMOLED Plus | |
-| [Raydium RM690B0](raydium/rm690b0/README.md) | 480×600 AMOLED driver, QSPI | LilyGO T4-S3 | |
-| [Shenghe SH8601Z](shenghe-microelectronics/sh8601z/README.md) | 480×480 AMOLED driver | LilyGO 1.43″ AMOLED (`DO0143FAT01`) | ⚠ marked CONFIDENTIAL — keep unstaged. **Settles who makes the SH86xx parts** |
-| [Shenghe SH8501B](shenghe-microelectronics/sh8501b/README.md) | 240-column AMOLED driver, 1.8 V | LilyGO T-Display AMOLED Lite | ⚠ marked CONFIDENTIAL — keep unstaged |
-| [Sitronix ST7789V](sitronix/st7789v/README.md) | 240×320 TFT controller; 8-bit Intel-8080 here | LilyGO T-Display-S3 / Touch | |
-| [Sitronix ST7796S](sitronix/st7796s/README.md) | 320×480 TFT controller, 4-wire SPI | LilyGO T-Display-S3 Pro | ⚠ vendor README says ST7796**U** — unresolved |
-| [Hynitron CST328](hynitron/cst328/README.md) | mutual-capacitance touch, I²C `0x1A` | LilyGO T-Display-S3 Touch (later) | Chinese-only datasheet ⇒ **primary source** |
-| [Hynitron CST3530](hynitron/cst3530/README.md) | capacitive touch, I²C | LilyGO T-Display-S3 Long (later) | address unknown |
-| [Hynitron CST226SE](hynitron/cst226se/README.md) | multi-point touch, I²C `0x5A` | LilyGO T-Display-S3 Pro, T4-S3 | no datasheet obtained |
-| [FocalTech FT3168](focaltech/ft3168/README.md) | capacitive touch for small AMOLED, I²C | LilyGO 1.64″ / 1.43″ AMOLED | address not verified |
-| [Silergy SY6970](silergy/sy6970/README.md) | I²C switch-mode Li-ion charger/PMIC with OTG + ADC, `0x6A` | LilyGO Long, Pro, T4-S3, 1.64″, 1.43/1.75″ | |
-| [Awinic AW9364](awinic/aw9364/README.md) | 4-channel LED backlight boost, one-wire brightness | LilyGO T-Display-S3 | **no datasheet located** |
-| [TP4065 (charger, as documented)](nanjing-top-power/tp4065/README.md) | linear Li-ion charger | LilyGO T-Display-S3, 1.91″ AMOLED | ⚠ **schematic disagrees with a shipping board** |
-| [Diodes AP2112K-3.3](diodes-incorporated/ap2112k/README.md) | 600 mA 3.3 V LDO; RT9013 named as a second source | LilyGO T-Display-S3 | |
-| [Bosch BHI260AP](bosch-sensortec/bhi260ap/README.md) | 6-axis IMU + Fuser2 sensor-hub core | LilyGO T-Display-S3 Pro (**some units**) | |
-| [MEMSensing MSM261S4030H0R](memsensing/msm261s4030h0r/README.md) | MEMS microphone | LilyGO T-Display-S3 Pro MVSRBoard | datasheet retained, not read |
-| [NXP PCF8563](nxp/pcf8563/README.md) | I²C RTC | LilyGO 1.43″/1.75″ AMOLED | **record created to fill a gap** — the artifact existed with no README |
-| [Unidentified `AXPM65611` / `65b311`](unidentified/lilygo-t-display-s3-family/axpm65611/README.md) | unknown; probably an AMOLED bipolar supply and/or the real charger | LilyGO AMOLED, AMOLED Plus, T-Display-S3 | records what would resolve it |
-
-Ten existing records gained a **Used By** row from the same pass, each preceded by an `mmin -30`
-check: `espressif/esp32-s3r8` · `winbond/w25q128jv` · `hynitron/cst816d` · `silergy/sy8089` ·
-`texas-instruments/bq25896` · `nxp/pcf85063a` · `x-powers/axp2101` · `chipsemi/chsc5816` ·
-`lite-on/ltr-553als-01` · `analog-devices/max98357a`.
-
-> **Merge note, 2026-09-07.** The LilyGO T-Display-S3 fragment
-> (`scratch/lilygo-t-display-s3/index-fragments.md`, SHA-256 `2f3acf08…`) was still being
-> written when this index was updated. The rows above are as that fragment stood at 06:23;
-> re-diff it before treating this section as final. See
-> [`scratch/index-merge/README.md`](../scratch/index-merge/README.md).
-
-### One pre-existing defect, reported not repaired
-
-`components/generic/bm8563/README.md` contains **two links to `../../nxp/pcf8563/README.md`**.
-That record **now exists** (created by the T-Display-S3 pass on 2026-09-07), so the links
-resolve — but they were broken when the Xteink pass reported them on 2026-09-04, and
-[`nxp/pcf85063a/README.md`](nxp/pcf85063a/README.md) still flags the directory as
-*"Artifacts-only directory; no record page yet"*. Both are logged in
-[`scratch/index-merge/corrections-requiring-review.md`](../scratch/index-merge/corrections-requiring-review.md).
-
-## Round-two component work *(added 2026-09-11)*
-
-Three sessions ran on 2026-09-11 — Xteink round two, schematic net-tracing, and certification /
-market. This section indexes what they produced. It is **additive to** the seven-pass sweep
-section above; no row there was changed.
-
-### One new record
-
-| Record | Category | Used by | Note |
-|---|---|---|---|
-| [Shenzhen Jinhangbiao KH3216-A35](generic/kh3216-a35-chip-antenna/README.md) | 2.4 GHz SMD chip antenna — **2.30 dBi peak, VSWR ≤ 2.0, 50 Ω** | [Xteink X4 Classic](../devices/xteink/x4-classic/README.md) | ⚠ **Identified from an FCC exhibit, not a vendor datasheet.** The source document is the `2BTR9-X4C` antenna report, so the part's identity, integrity and parameters rest on a test-lab filing — see the record's own caveat. It is the **first antenna part in this library identified from a regulatory record** |
-
-### Datasheets acquired for existing records
-
-Five records that previously had no primary document now have one. Each was magic-byte
-validated; the record carries the hash.
-
-| Record | Acquired |
-|---|---|
-| [`ultrachip/uc8253`](ultrachip/uc8253/README.md) | datasheet `UC8253c_A` rev 0.6 (2020-10-13), 1,294,916 B, `bee25538…` — ⚠ cover marked *"for TFT module use only"*, a **use restriction of unclear scope**, not a licence. Kept **unstaged** |
-| [`ultrachip/uc8179`](ultrachip/uc8179/README.md) | datasheet `UC8179c_C` rev 0.6 (2019-11-26), 1,202,516 B, `bf1dcef7…` — same marking, same treatment |
-| [`espressif/esp32-c3`](espressif/esp32-c3/README.md) | datasheet **v2.4**, 900,158 B, `833fc000…` |
-| [`texas-instruments/bq27220`](texas-instruments/bq27220/README.md) | datasheet `SLUSCB7A` Rev A **and** technical reference manual `SLUUBD4` Rev A — this closes the acquisition gap the schematic-tracing pass flagged for the sibling TCA8418 |
-| [`goodix/gt911`](goodix/gt911/README.md) | **Programming Guide Rev.00**, 477,454 B, `60c6c228…` — ⚠⚠ **page 1 reads *"GOODIX CONFIDENTIAL … Reproduction and/or distribution … is strictly prohibited without written consent of GOODIX."*** Redistribution status **`prohibited` as written**. Held **unstaged pending a user decision** |
-
-Two records still have **no datasheet**, and both absences were re-tested rather than assumed:
-
-- [`ultrachip/uc8279`](ultrachip/uc8279/README.md) — **12 sources tried, all failed.** The record lists them.
-- [`cellwise/cw2017`](cellwise/cw2017/README.md) — no datasheet, **and the part is not in CellWise's public catalogue at all.** That is a stronger negative than a failed download.
-
-### `unidentified/*` — three resolved or advanced, none deleted
-
-**No `components/unidentified/*` record was deleted, and none should be.** Other records link to
-them, and they are the stable landing place for a search on the unknown string.
-
-| Record | Status after round two | Points at |
-|---|---|---|
-| [`unidentified/m5stack-stamp-s3a/dcdc-u4`](unidentified/m5stack-stamp-s3a/dcdc-u4/README.md) | ✅ **Resolved — the sheet prints `JW5712`.** Retained for linkage | [`joulwatt/jw5712`](joulwatt/jw5712/README.md), which already existed with a datasheet |
-| [`unidentified/lilygo-t-display-s3-family/axpm65611`](unidentified/lilygo-t-display-s3-family/axpm65611/README.md) | ⚠ **Function established, identity still unknown.** Better described as *"AMOLED bipolar display-bias supply, 12-pin, manufacturer unknown"* than as *"unidentified"* | no real record possible — `components/<manufacturer>/<part>/` cannot be created without a manufacturer |
-| [`unidentified/m5stack-dinmeter/rotary-encoder`](unidentified/m5stack-dinmeter/rotary-encoder/README.md) | topology established — 5-terminal, A/COM/B plus switch; identity unknown | — |
-| [`unidentified/m5stack-dinmeter/buzzer`](unidentified/m5stack-dinmeter/buzzer/README.md) | topology established — magnetic, AC-coupled drive; identity unknown | — |
-| [`unidentified/xteink-x3-x4`](unidentified/xteink-x3-x4/README.md) | extended by the Xteink round-two pass | — |
-
-⚠ **The `dcdc-u4` row in the seven-pass section above carries a `⚠` pointing at
-[`corrections-requiring-review.md`](../scratch/index-merge/corrections-requiring-review.md).**
-It is now **adjudicated**: the part is `JW5712`, the schematic PNG was re-fetched and
-hash-matched, and two sessions agree independently — the certification/market pass in
-[`corrections-adjudicated.md` §1](../scratch/index-merge/corrections-adjudicated.md) and the
-schematic-tracing pass from the sheet text. The original row is unchanged.
-
-[`joulwatt/jw5712`](joulwatt/jw5712/README.md) accordingly deserves **three** *Used by* rows —
-`components/m5stack/stamp-s3a` (`U4`), [`devices/m5stack/cap-lora-1262`](../devices/m5stack/cap-lora-1262/README.md) (`U3`)
-and [`devices/m5stack/cap-cc1101`](../devices/m5stack/cap-cc1101/README.md) (`U1`). Three M5Stack
-boards fit the same part. ⚠ That record's datasheet is a **raster scan** — 4 pages, one full-page
-image each, `pdftotext` yields 0 words — so it cannot be text-searched and OCR would be needed
-for any register or parametric work. The `-scanned` filename suffix is accurate.
-
-### Named on a schematic, no record yet
-
-The net-tracing pass read these part numbers directly off vendor sheets but did not create
-records, because none of the boards fitting them was in its scope. Listed so the next reader does
-not re-derive them. **Create one only when working the relevant board.**
-
-| Part | Fitted as | Source sheet |
-|---|---|---|
-| `PI4IOE5V6408ZTAEX` I²C GPIO expander · `MAX2659` GNSS LNA · `GP-02` GNSS module | `U2` · `U1` · `M2` | Cap LoRa-1262 `U214_SCH_V1.1_20251029` |
-| `BL8075CB5TR33` 3.3 V regulator · `ME3116AM6G` wide-input buck · `CN809J` reset supervisor · `AP40P05` P-FET · `LN2324DT2AG` | `U4` · `U1` · `U7` · `Q3`/`Q6` · `Q4` | DinMeter `K134_DIN_Meter_v1.0` |
-| `AW9364DNR` backlight boost · `AP2112K-3.3V` / `RT9013` LDO | `U4` · `U7` | `T_Display_S3.pdf` |
-| `MSM381A3729H9BPC` PDM microphone · `PESDNC2FD3V3B` / `PESDNC2FD5VB` ESD arrays | `U8` · `D6`–`D8` | Cardputer ADV sheets 3 and 1 |
-| `DFP252012TF-100M` 10 µH inductor | `L6`/`L7`, `L3`/`L4` | the AMOLED sheets |
-
-A [`belling/bl8075`](belling/bl8075/README.md) record **does** now exist, written by the Xteink
-round-two pass for a different board.
-
-### Two findings for records this pass did not own
-
-- ⚠ [`nanjing-top-power/tp4065`](nanjing-top-power/tp4065/README.md) — **the schematic symbol is
-  5-pin, not SOP-8.** If that record states or implies SOP-8 it needs a dated correction. **Not
-  applied** — outside every round-two session's scope. Flagged in
-  [`corrections-requiring-review.md`](../scratch/index-merge/corrections-requiring-review.md).
-- [`silergy/sy8089`](silergy/sy8089/README.md) — no datasheet retained. Its feedback reference is
-  now **derived** as 0.6 V from the Cardputer ADV divider. **That is inference, not primary
-  evidence**, and the record says so.
diff --git a/components/analog-devices/max2659/README.md b/components/analog-devices/max2659/README.md
deleted file mode 100644
index d908251..0000000
--- a/components/analog-devices/max2659/README.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# Maxim / Analog Devices MAX2659
-
-- **Category:** **GNSS low-noise amplifier** (single-stage, high-gain LNA for 1.575 GHz L1)
-- **Package as fitted:** 6-pin (`GND` 1, `GND` 2, `RFIN` 3, `VCC` 4, `SHDN` 5, `RFOUT` 6)
-- **Research status:** **no datasheet retrieved.** Identity and integration come from an
-  M5Stack schematic symbol. Performance figures below are the *board's* claims, not the
-  part's.
-- **Retrieved:** 2026-09-04
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | Maxim Integrated, now **Analog Devices** | part-number lineage, `inferred` |
-| Part | **`MAX2659`** | schematic comment, Cap LoRa-1262 `U1` |
-| Function | GNSS/GPS **low-noise amplifier** | function follows from the pinout and its position between a patch antenna and a GNSS receiver |
-| Pinout as fitted | 1 `GND`, 2 `GND`, 3 `RFIN`, 4 `VCC`, 5 `SHDN`, 6 `RFOUT` | schematic |
-
-⚠ **Gain, noise figure, current and supply range are not stated here** because no datasheet
-was retrieved. The MAX2659 family is widely cited as a ~+20 dB, sub-1 dB-NF GNSS LNA, but
-**this record does not assert that** — it is exactly the kind of remembered number that
-should be checked against the datasheet before use.
-
-## 2. Why a board fits one
-
-A passive ceramic patch antenna feeding a GNSS receiver directly loses sensitivity to trace
-loss and to the receiver's own noise figure. Putting a high-gain, low-noise amplifier
-**immediately at the antenna** sets the system noise figure to (approximately) the LNA's
-own, which is what buys the last several dB of tracking sensitivity.
-
-That is visible in the Cap LoRa-1262's claimed figures: **tracking −162 dBm**, acquisition
-−160 dBm, cold start −148 dBm — numbers a bare ATGM336H module typically does not reach.
-
-## 3. Used By
-
-### [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) — designator `U1`
-
-| Pin | Net |
-|---:|---|
-| 1, 2 `GND` | `GND` |
-| **3 `RFIN`** | ← `J1` ceramic patch antenna (`ANT1818-04`, 18 × 18 × 4 mm) via **`L1` 6.8 nH ±5 %** |
-| 4 `VCC` | `+3.3V` |
-| **5 `SHDN`** | **tied — the host cannot shut the LNA down** |
-| **6 `RFOUT`** | → `M2` `ATGM336H-6N` pin 11 `ANT`, via **`C5` 470 pF** |
-
-Decoupling: `C6` 100 nF, `C7` 33 nF.
-Supply routing: the GNSS module's `VCC_RF` (pin 14) reaches `+3.3V` through **`FB2`
-120 Ω/MB**, and its digital `VCC` (pin 8) through **`FB3`** — M5Stack isolates the RF supply
-from the digital one and both from the LoRa module's rail.
-
-**Consequence worth stating:** because `SHDN` is tied, the LNA's quiescent current is paid
-whenever the Cap is powered, even with the GNSS receiver asleep. The predecessor board's
-published *"GPS sleep, LoRa standby: DC 5 V @ 3.16 mA"* is therefore a floor that includes
-an always-on LNA. Contrast **[Stamp C6LoRa](../../../devices/m5stack/stamp-c6lora/README.md)**,
-where an I/O expander *does* gate the LNA enable — the better design for battery life.
-
-## 4. Related components
-
-- [`components/zhongkewei/atgm336h-6n`](../../zhongkewei/atgm336h-6n/README.md) — what it feeds
-- [`components/generic/gnss-ceramic-patch-antenna`](../../generic/gnss-ceramic-patch-antenna/README.md) — what feeds it
-
-## 5. Local artifacts
-
-**None.** Analog Devices publishes the MAX2659 datasheet; it was not fetched by this pass.
-Doing so would let §1 be filled in properly.
-
-## 6. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| M-1 | Cap LoRa-1262 schematic V1.1 | M5Stack | primary | schematic | [`devices/m5stack/cap-lora-1262/artifacts/schematic/`](../../../devices/m5stack/cap-lora-1262/artifacts/schematic/) | 2026-09-04 | Part identity, six-pin net list, `SHDN` tied |
-| M-2 | Cap LoRa-1262 documentation | M5Stack | primary | official page | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` | 2026-09-04 | The −162 dBm tracking claim the LNA enables |
diff --git a/components/analog-devices/max98357a/README.md b/components/analog-devices/max98357a/README.md
deleted file mode 100644
index fe7a685..0000000
--- a/components/analog-devices/max98357a/README.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# Analog Devices (Maxim) MAX98357A — I²S 3.2 W Class-D mono amplifier with integrated DAC
-
-- **Category:** digital audio power amplifier — PCM I²S input, Class-D speaker output, **no I²C control interface**
-- **Manufacturer:** Maxim Integrated, now **Analog Devices**
-- **Retrieved:** 2026-09-04
-
-## 1. Core facts
-
-| Property | Value |
-|---|---|
-| Input | **I²S / left-justified / TDM** PCM, 8 – 96 kHz |
-| Output | mono Class-D, **3.2 W into 4 Ω** at 5 V, 10 % THD |
-| Supply | 2.5 – 5.5 V |
-| Control | **none — no I²C, no SPI.** Configuration is by resistor strapping on `SD_MODE` and `GAIN_SLOT` |
-| Channel select | `SD_MODE` resistor divider selects Left / Right / (L+R)/2 **and** shutdown |
-| Gain | `GAIN_SLOT` resistor selects 3 / 6 / 9 / 12 / 15 dB |
-| Datasheet | `https://www.analog.com/media/en/technical-documentation/data-sheets/MAX98357A-MAX98357B.pdf` |
-
-**The thing that bites people:** `SD_MODE` is not a plain enable pin. It is an analogue
-threshold input whose *voltage* selects the channel as well as switching the amplifier on. A
-firmware author who drives it as a GPIO gets on/off correctly and gets whichever channel the
-board's resistor happens to select. On the LilyGO board LilyGO documents it as a plain
-"shutdown control … high enables the amplifier, low shuts it down" (S1), which is the correct
-*usage* but hides the mechanism.
-
-## 2. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-Fitted on the **nRF52840 base board** as an **external** I²S amplifier — the K230 already has
-an on-die audio codec with two DAC channels, so this is an added speaker path rather than the
-only one.
-
-| MAX98357A | K230 |
-|---|---|
-| `DIN` | **`GPIO35`** / I²S data |
-| `BCLK` | **`GPIO32`** / I²S bit clock |
-| `LRCK`/`WS` | **`GPIO33`** / I²S word select |
-| shutdown | **`GPIO34`** — high = enabled |
-
-Because the on-chip codec and this amplifier are two different sinks, the BSP adds an explicit
-route switch: `0059-asoc-canaan-add-external-i2s-output-switch.patch`, plus
-`0058-riscv-dts-rm69a10-add-audio-fan-sensor-pins.patch` for the pin muxing. The launcher
-exposes it through `ui_i2s_test.c` and the audio settings page.
-
-
-### [LilyGO T-Display-S3 Pro MVSRBoard](../../../devices/lilygo/t-display-s3-pro-mvsrboard/README.md) — *added 2026-09-07*
-
-The **S** (speaker) in *MVSR* — LilyGO's Microphone/Vibration/Speaker/RTC backplate for the [T-Display-S3 Pro](../../../devices/lilygo/t-display-s3-pro/README.md). Unlike the K230 board above, this is the **only** audio output path on that platform; the ESP32-S3 has no on-die codec.
-
-LilyGO mirrors `MAX98357AETE+T.pdf` in the `T-Display-S3-Pro` repository @ `08b8b2bbcb8b263131af119476403080cd30224f`. It was **not retrieved**, since this record already holds the part; whether LilyGO's mirror is the same revision as the copy held here is **unknown**.
-
-On the same backplate: a [MEMSensing MSM261S4030H0R](../../memsensing/msm261s4030h0r/README.md) microphone and a [PCF85063ATL](../../nxp/pcf85063a/README.md) RTC. **The I²S pin assignment on the backplate was not established** — its schematic (`T-Display-S3-Pro-MVSRBoard_V1.0_20241109.pdf`) was retrieved but not traced, and no MVSRBoard pin header exists in the vendor source. Note also that **two sheets both declare version `V1.0`** with different dates and sizes.
-## 3. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | I²S pin mapping, shutdown polarity |
-| S2 | `0059-asoc-canaan-add-external-i2s-output-switch.patch` | LILYGO | primary | source | same repo | 2026-09-04 | Route switching between on-chip codec and external amp |
-| S3 | MAX98357A/MAX98357B datasheet | Analog Devices | primary | datasheet | `https://www.analog.com/media/en/technical-documentation/data-sheets/MAX98357A-MAX98357B.pdf` | not retrieved | Electrical specification, SD_MODE behaviour |
diff --git a/components/asair/aht20/README.md b/components/asair/aht20/README.md
deleted file mode 100644
index 2566555..0000000
--- a/components/asair/aht20/README.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# ASAIR (Aosong) AHT20 — I²C temperature and relative-humidity sensor
-
-- **Category:** digital temperature + relative-humidity sensor
-- **Manufacturer:** **Guangzhou Aosong Electronics / ASAIR** (广州奥松电子)
-- **Retrieved:** 2026-09-04
-
-## 1. Core facts
-
-| Property | Value |
-|---|---|
-| Interface | I²C, **fixed 7-bit address `0x38`** (not configurable) |
-| Humidity | 0 – 100 % RH, typical accuracy ±2 % RH |
-| Temperature | −40 … +85 °C, typical accuracy ±0.3 °C |
-| Supply | 2.2 – 5.5 V |
-| Protocol | trigger-measurement command `0xAC 0x33 0x00`, wait ≥ 80 ms, read 6 bytes + CRC8 |
-| Predecessor | **AHT10** — same address, *different* init sequence. Not interchangeable without a driver check. |
-
-**Fixed address is the operational constraint.** Two AHT20s cannot share a bus. On any board
-where `0x38` already appears, an AHT20 cannot be added without a mux.
-
-## 2. Used By
-
-### [LilyGO T-Display K230 Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-Fitted on the **nRF52840 base board**. I²C4 — the shared expansion bus — on **`GPIO46` SCL /
-`GPIO47` SDA**, address **`0x38`**. Treated by the launcher as optional, detected at runtime,
-surfaced in the sensor settings page.
-
-The LilyGO tree references `AHT10` twice alongside `AHT20`, which suggests a probe that accepts
-either; do not assume the fitted part from source alone.
-
-## 3. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | `0x38`, GPIO46/47, base-board placement |
-| S2 | AHT20 product datasheet | ASAIR | primary | datasheet | `http://www.aosong.com/en/products-32.html` | not retrieved | Electrical and protocol specification |
diff --git a/components/awinic/aw32901/README.md b/components/awinic/aw32901/README.md
deleted file mode 100644
index 131002b..0000000
--- a/components/awinic/aw32901/README.md
+++ /dev/null
@@ -1,187 +0,0 @@
-# Awinic AW32901FCR
-
-> Over-voltage-protection **load switch with surge protection** — an integrated low-R<sub>DS(on)</sub> nFET in series with the USB input, which opens in ~50 ns when the input exceeds a fixed 5.95 V threshold, and survives 120 V surges and 29 V DC.
-> Research snapshot **2026-09-01**. Fitted as **`U2`** on sheet 2 of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), in the sheet block labelled `PROTECTION`. **No hardware was available.**
-
-> ⚠ **This is not a battery-protection IC.** It is an *input* over-voltage protection switch, sitting between the USB-C connector and the charger. The distinction matters: it protects the board from the adapter, not the cell from the board. Cell protection on this design is whatever is inside the pack, plus the charger's own limits.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Awinic `AW329XX` datasheet **V1.3**, December 2021 — local copy `artifacts/aw329xx-datasheet-en-v1.3.pdf` | `not-tested` |
-| **[VP]** | Awinic product page for `AW32901FCR`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Ordering part | **`AW32901FCR`** | **[SCH]** sheet 2, `U2`; **[VP]** |
-| Manufacturer | **Shanghai Awinic Technology Co., Ltd.** (上海艾为电子) | **[DS]** |
-| Product-page category | *"OVP with surge protection"* → *"Over-Voltage Protection Load Switch with Surge Protection"* | **[VP]** |
-| Package | **FCQFN-12, 1.3 mm × 1.8 mm** (12 balls, A1–A4 / B1–B4 / C1–C4) | **[VP]**, **[DS]** |
-| Datasheet | **`DS_AW329XX_EN_V1.3`**, December 2021, 19 pp — covers the whole AW329xx family | **[DS]** cover |
-| Lifecycle | Active | **[VP]** |
-
-### 1.1 Family — the suffix *is* the OVP threshold **[DS Device Comparison Table]**
-
-The parts are identical apart from the default over-voltage trip point, so a substitution changes the protection level and nothing else:
-
-| Part | V<sub>IN_OVLO</sub> min | **typ** | max | Hysteresis |
-|---|---:|---:|---:|---:|
-| **AW32901** | 5.83 V | **5.95 V** | 6.07 V | 130 mV |
-| AW32902 | 6.08 V | 6.20 V | 6.32 V | 130 mV |
-| AW32905 | 6.66 V | 6.80 V | 6.94 V | 140 mV |
-| AW32909 | 9.78 V | 9.98 V | 10.18 V | 210 mV |
-| AW32910 | 10.29 V | 10.50 V | 10.71 V | 210 mV |
-| AW32912 | 13.7 V | 14.0 V | 14.3 V | 280 mV |
-
-The threshold is additionally **adjustable from 4 V to 24 V** through the `OVLO` pin. **[DS]**
-
----
-
-## 2. Key limits **[DS Absolute Maximum Ratings, VP Parameters]**
-
-| Parameter | Value |
-|---|---|
-| `IN` absolute maximum | **29 V** DC |
-| `OUT`, `OVLO`, `ACOK`, `EN` absolute maximum | 6 V |
-| Surge withstand (internal clamp) | **> 120 V**, IEC 61000-4-5 |
-| Continuous switch current `IN`→`OUT` | **5 A** |
-| Peak current (10 ms) | 8 A |
-| Body-diode continuous forward current | 1.5 A |
-| R<sub>DS(on)</sub> typical | **27 mΩ** |
-| OVP response time | **≈50 ns** typical |
-| System ESD | ±8 kV contact, ±15 kV air (IEC 61000-4-2) |
-| Ambient / junction temperature | −40 to +85 °C / −40 to +150 °C |
-| Other protections | Over-temperature (OTP), under-voltage lockout (UVLO) |
-
----
-
-## 3. Pinout **[DS Pin Configuration, FCQFN-12]**
-
-|  | 1 | 2 | 3 | 4 |
-|---|---|---|---|---|
-| **A** | `EN` | `OUT` | `OUT` | `GND` |
-| **B** | `ACOK` | `OUT` | `IN` | `GND` |
-| **C** | `OVLO` | `IN` | `IN` | `GND` |
-
-| Pin | Function **[DS Pin Definition]** |
-|---|---|
-| `EN` (A1) | Enable, **active low** |
-| `ACOK` (B1) | Open-drain status: pulled **low** while V<sub>IN_UVLO</sub> < V<sub>IN</sub> < V<sub>IN_OVLO</sub>; otherwise Hi-Z |
-| `OVLO` (C1) | OVP threshold adjustment |
-| `IN` / `OUT` / `GND` | Power path |
-
-> ⚠ **`OVLO` must not float.** To use the default threshold the datasheet requires **`R2 = 0 Ω`, `R1 = NC`, `OVLO` connected directly to GND**, and states explicitly *"OVLO pin cannot be left floating."* **[DS]** The two-resistor divider is only for a custom threshold.
-
-The datasheet also notes that if an external TVS is fitted, its **clamping voltage must be below 34 V**, and that a design relying on the AW329xx alone must account for the 29 V `IN` rating. **[DS]**
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`U2`**, schematic sheet 2, in the block silkscreened `PROTECTION`. The sheet carries the annotation **`OVP = 5.95V`** next to it, confirming the default threshold is in use. **[SCH]**
-
-**Position in the power chain:**
-
-```
-USB-C  ──►  VUSB_IN  ──►  [ AW32901FCR  U2 ]  ──►  5V_IN  ──►  [ IP2315  U1 ]  ──►  VBAT_L0
-                              OVP 5.95 V                          charger
-                                                     VBAT_L0 ──(R20 = 0 Ω)──► VBUS_L0  ──► all downstream rails
-```
-
-**Net-by-net [SCH]:**
-
-| Ball | Name | Net |
-|---|---|---|
-| B3, C2, C3 | `IN` | `VUSB_IN` (from the USB-C connector, behind `TVS1` = `ESD5311`) |
-| A2, A3, B2 | `OUT` | **`5V_IN`** → [IP2315](../../injoinic/ip2315/README.md) `VIN` (pins 20/21) |
-| A1 | `EN` (active low) | local network with `R10` = `0 Ω/1%` |
-| B1 | `ACOK` | local network with `R6` = `NC/1%` — status **not routed to any processor** |
-| C1 | `OVLO` | network with `R10`/`R11`/`R12`; default threshold in use per the sheet annotation |
-| A4, B4, C4 | `GND` | `GND` |
-| — | decoupling | `C5` = `1 µF/25 V` input, `C6` = `1 µF/25 V` output |
-
-**Consequences for this board — both worth knowing before debugging a charge fault:**
-
-1. **`ACOK` goes nowhere.** No MCU can read "input present and in range". Firmware infers input state from the [M5PM1](../../m5stack/m5pm1/README.md)'s `5VIN_ADC` / `BAT_ADC` measurements instead. If the AW32901 has tripped, the symptom is simply "no charging" with no dedicated flag. **[INF]**
-2. **The 5.95 V threshold makes the IP2315's fast-charge feature unreachable.** The charger downstream advertises 9 V and 12 V PD/FCP/AFC/PE+ negotiation, but this switch opens above ~5.95 V, so those voltages could never reach it. The PaperMono also leaves the IP2315's CC series resistors (`R1`, `R2`) unpopulated, so negotiation is disabled at both ends. See [IP2315 §4.1](../../injoinic/ip2315/README.md#41--pd-is-depopulated--this-is-a-5-v-charger-in-practice). **[INF]**
-3. **A 5 A-rated switch on a ~1 A path** — the part is heavily over-specified for a 1150 mAh device, and is presumably chosen for the surge/ESD spec and the small FCQFN footprint rather than the current rating. **[INF]**
-
----
-
-## 5. Drivers and libraries
-
-**Not applicable — this is a passive-control analogue part.** It has no bus interface and no registers. Its only host-visible signal, `ACOK`, is unconnected on the PaperMono (§4).
-
----
-
-## 6. Integration pitfalls
-
-1. **`OVLO` must be tied — never floated** (§3). With the default threshold, tie it to GND directly or through 0 Ω.
-2. **`EN` is active low.** An accidentally floating or pulled-high `EN` leaves the switch off, presenting as "the board will not charge and draws nothing from USB."
-3. **The part number encodes the threshold** (§1.1). Substituting an AW32905 for an AW32901 raises the trip point from 5.95 V to 6.8 V — a silent, board-level safety change.
-4. **A downstream TVS must clamp below 34 V** to stay inside the `IN` rating (§3).
-5. **The body diode conducts backwards at up to 1.5 A** even when the switch is off; this is not a reverse-current blocker.
-
----
-
-## 7. Alternatives
-
-| Part | vs. AW32901FCR | When |
-|---|---|---|
-| AW32902 / AW32905 / AW32909 / AW32910 / AW32912 | Same silicon, higher OVP threshold | When the design *does* want 9 V or 12 V fast charge |
-| TI **TPD4S014** / **TPS2596** | Comparable OVP/eFuse class, US-vendor documentation | Where Awinic sourcing or documentation is a problem |
-| Discrete PMOS + comparator | Cheaper in BOM cost only | Loses the 120 V surge clamp and the 50 ns response |
-
----
-
-## 8. Open questions
-
-- Exactly which of `R10`/`R11`/`R12` sits on `OVLO` versus `EN` on the PaperMono was not resolved from the PDF text layer; the sheet's `OVP = 5.95V` annotation establishes that the **default** (grounded `OVLO`) configuration is in use, which is the fact that matters.
-- Whether `ACOK` is intentionally unused or a lost opportunity; the vendor has not commented.
-- No hardware measurement of the trip point or of R<sub>DS(on)</sub>.
-
----
-
-## Manufacturer
-
-**Shanghai Awinic Technology Co., Ltd.** No vendor sourcing guide exists in this repository yet. The retrieval recipe that worked on 2026-09-01, recorded because Awinic's site gives no obvious download link:
-
-1. `https://www.awinic.com/{cn|en}/productDetail/<FULL-ORDERING-PART>` — the **full** ordering part number (`AW32901FCR`), not the base part (`AW32901`), which silently returns the home page.
-2. The page contains `data-file-url="doc/<YYYYMM>/<uuid>.pdf"` and `data-doc-title="DS_..."`.
-3. Download via `https://www.awinic.com/en/download?file=<urlencoded file>&fileName=<urlencoded title>`.
-
-Plain `curl` with a Chrome 131 User-Agent was sufficient; no fallback User-Agent was needed, and no login is required.
-
-## Related pages
-
-- [Injoinic IP2315](../../injoinic/ip2315/README.md) — the charger immediately downstream
-- [Awinic AW35122](../aw35122/README.md) · [AW39112](../aw39112/README.md) · [AW9967](../aw9967/README.md) — the other Awinic parts on this board
-- [Generic charger / power-path record](../../generic/charger-power-path/README.md)
-- [Generic USB-C interface record](../../generic/usb-c-interface/README.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | AW329XX datasheet | Awinic | primary | datasheet | `https://www.awinic.com/en/download?file=doc/20230609wm/6a5a084d-01eb-4146-9a40-a6e6608f0e79.pdf&fileName=DS_AW329XX_EN_V1.3` | 2026-09-01 | **V1.3**, Dec 2021, 19 pp, 575 578 B | Threshold table, absolute maxima, pin map, `OVLO` grounding requirement, TVS clamp limit | `artifacts/aw329xx-datasheet-en-v1.3.pdf` |
-| D2 | AW32901FCR product page | Awinic | primary | official page | <https://www.awinic.com/en/productDetail/AW32901FCR> | 2026-09-01 | — | Category, package `FCQFN 1.3X1.8-12L`, 27 mΩ R<sub>DS(on)</sub>, 5 A, 120 V surge, 50 ns, 29 V DC | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `U2` net assignments, `OVP = 5.95V` annotation, `R6`/`R10` values | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/aw329xx-datasheet-en-v1.3.pdf` | 575 578 | `2dfda61d8aadf8ef8655ede785eb92f38979e1260e68d295ed9756645208b2d1` | 19 |
-
-**Method note.** D1 validated as `%PDF`, 19 pages, text layer intact. The document is watermarked *"Awinic Confidential"* in the page background but is served publicly from the vendor's own site without login.
diff --git a/components/awinic/aw32901/artifacts/aw329xx-datasheet-en-v1.3.pdf b/components/awinic/aw32901/artifacts/aw329xx-datasheet-en-v1.3.pdf
deleted file mode 100644
index d0d848b..0000000
Binary files a/components/awinic/aw32901/artifacts/aw329xx-datasheet-en-v1.3.pdf and /dev/null differ
diff --git a/components/awinic/aw35122/README.md b/components/awinic/aw35122/README.md
deleted file mode 100644
index 36c697e..0000000
--- a/components/awinic/aw35122/README.md
+++ /dev/null
@@ -1,269 +0,0 @@
-# Awinic AW35122 (AW35122FDR)
-
-> Ultra-small **P-channel load switch** with controlled output slew rate, quick output discharge and an internal 7.1 MΩ enable pull-down, in a 1 mm × 1 mm × 0.55 mm four-ball package.
-> Research snapshot **2026-09-01**. Fitted **at least four times** on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) as the switch element of the `L3B` power domain. **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Awinic `AW3512, AW35122` datasheet **V1.0**, July 2019 — local copy `artifacts/aw3512-aw35122-datasheet-en-v1.0.pdf` | `not-tested` |
-| **[VP]** | Awinic product page for `AW35122FDR`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Ordering part | **`AW35122FDR`** | **[SCH]**, **[VP]** |
-| Manufacturer | **Shanghai Awinic Technology Co., Ltd.** | **[DS]** |
-| Category | *"Single-Channel load switches"* — *"1.5 A Ultra-small Load Switch with Slew Rate Control"* | **[VP]** |
-| Package | **FCDFN-4L, 1.00 × 1.00 × 0.55 mm** (balls A1, A2, B1, B2) | **[DS]**, **[VP]** |
-| Datasheet | **`DS_AW35122_EN_V1.0`**, July 2019, 18 pp | **[DS]** cover |
-| Lifecycle | Active | **[VP]** |
-
-### 1.1 ⚠ `AW3512` vs `AW35122` — the difference is one resistor, and it matters
-
-The datasheet covers both under one document **[DS Device Comparison Table]**:
-
-| Part | Top mark | `EN` pull-down |
-|---|---|---|
-| **AW3512** | `SV` | **None.** The datasheet says explicitly: *"do not leave floating"* |
-| **AW35122** | `UJ` | **Internal 7.1 MΩ pull-down** |
-
-A board designed around the AW35122's internal pull-down that is later populated with an AW3512 has **four floating enable inputs**. The rails would come up indeterminate. The parts are otherwise identical and share a footprint, so this substitution is easy to make and hard to see.
-
-On the PaperMono this is directly relevant: `U8`'s external enable pull-down `R25` is marked **`NC/1%`** — not fitted — because the AW35122's internal 7.1 MΩ is doing the job. **[SCH]** **[INF]**
-
----
-
-## 2. Key limits **[DS Absolute Maximum Ratings, VP Parameters]**
-
-| Parameter | Value |
-|---|---|
-| Input voltage `VIN` | **1.2 V – 5.5 V** (abs. max −0.3 to 6 V) |
-| `EN`, `OUT` abs. max | −0.3 to 6 V |
-| Max continuous switch current (V<sub>IN</sub> ≥ 2 V) | **1.5 A** |
-| Max peak switch current (V<sub>IN</sub> ≥ 2.5 V) | 2 A |
-| Enable logic | **Active high** |
-| Output discharge | Yes (quick discharge on disable) |
-| Slew-rate control | Yes — limits inrush at turn-on |
-| Turn-on time t<sub>R</sub> | ≈165 µs **[VP]** |
-| Reverse-current blocking | **No** |
-| θ<sub>JA</sub> | 166 °C/W |
-| Operating temperature | −40 to +85 °C |
-| Max T<sub>J</sub> | 150 °C |
-| Logic level | 1.8 V compatible **[VP]** |
-
-**R<sub>DS(on)</sub> is strongly supply-dependent [DS]:**
-
-| V<sub>IN</sub> | R<sub>DS(on)</sub> typ. |
-|---|---:|
-| 5.5 V | 52 mΩ |
-| 4.2 V | 58 mΩ |
-| **3.3 V** | **66 mΩ** |
-| 2.5 V | 80 mΩ |
-| 1.8 V | 110 mΩ |
-| 1.2 V | 222 mΩ |
-
-At the PaperMono's 3.3 V the switch drop is ≈66 mV per amp — negligible for the microphone and touch rails, but worth a thought on the microSD rail during a write burst. **[INF]**
-
----
-
-## 3. Pinout **[DS Pin Definition]**
-
-| Ball | Name | Function |
-|---|---|---|
-| **A1** | `OUT` | Switch output |
-| **A2** | `IN` | Switch input and device supply |
-| **B1** | `GND` | Ground |
-| **B2** | `EN` | Control input, **active high**. On AW35122, internal 7.1 MΩ pull-down |
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-
-The PaperMono's power architecture (sheet 1) defines five states — **L0 Shipping, L1 Standby, L2 DeepSleep, L3A CORE ACTIVE, L3B All ACTIVE** — and the `L3B` rails are the ones that exist only while the whole device is awake. **The AW35122 is the switch element of `L3B`**, and every instance is enabled from an [M5IOE1](../../m5stack/m5ioe1/README.md) GPIO rather than from the ESP32-S3. Sheet 1's legend annotates the `L3B Power Control` block with `AW35122` for both the PDM and TF branches. **[SCH]**
-
-#### 4.1 Every instance found
-
-Three instances carry the string `AW35122FDR` beside the designator in the schematic text layer; a fourth is a footprint- and pin-name-identical part on the NFC sub-board whose value string was not recovered.
-
-| # | Ref | Sheet | Input | **Controlled rail** | **Enable net** | Enable source | Evidence |
-|---|---|---|---|---|---|---|---|
-| 1 | **`U8`** | 2 | `3V3_L2` | **`TF_3V3_L3B`** — microSD card slot (`U20`, `AXE512127D`) | `PYB_TF_EN` | M5IOE1 **`PYG14`** (`U17` pin 3/18) → `M5IOE1_PIN_14`, enum value 13 | **[SCH]**; **[SRC]** `hal_tf_card.cpp:15` |
-| 2 | **`U18`** | 4 | `3V3_L2` | **`TP_VDD`** — FT6336G touch controller on FPC `J4`, and the `AW39112DNR` (`U19`) bus translator's A-side supply and `OE` | `PYB_TP_EN` | M5IOE1 **`PYG13`** (`U17` pin 6/15) → `M5IOE1_PIN_13`, enum value 12 | **[SCH]**; **[SRC]** `app_sleep_wake.cpp:81` |
-| 3 | **`U21`** | 4 | `3V3_L2` | **`PDM_VDD`** — LMD4737T261-AC02 PDM microphone (`U1`, sheet 5, via `J6`/`J1`) | `PYB_PDM_EN` | M5IOE1 **`PYG12`** (`U17` pin 5/16) → `M5IOE1_PIN_12`, enum value 11 | **[SCH]**; **[SRC]** `hal_mic.cpp:13`, `hal_board.cpp:30` |
-| 4 | **`U1` (sheet 6)** | 6 | `3V3_L2` | **`VCC_3V3`** — the NFC sub-board rail feeding the ST25R3916 (`U2`, sheet 6) | **`PYB_RFID_RST`** (arriving on BTB `J1` pin 9) | not resolved on the main-board sheets | **[SCH]**; part number **[INF]** — see §4.2 |
-
-Passive complement, from the schematic text layer **[SCH]**:
-
-| Ref | Input cap | Output cap | EN pull-down |
-|---|---|---|---|
-| `U8` | — | `C21` 10 µF/10 V | `R25` **`NC/1%`** (relies on the internal 7.1 MΩ) |
-| `U18` | `C66` 10 µF/10 V | `C68` 10 µF/10 V | — |
-| `U21` | — | `C85` 10 µF/10 V | — |
-| `U1` (sheet 6) | — | `C1` 10 µF | `R1` 0 Ω, `R2` `NC` |
-
-#### 4.2 ⚠ Instance 4 is inferred, not confirmed
-
-Sheet 6 (the NFC sub-board, a separate Altium document, `02 Paper Mono NFC.SchDoc`, rev V0.2, 2026-07-28) draws `U1` with pin names `IN` / `OUT` / `EN` / `GND` on balls A2 / A1 / B2 / B1 — **identical to the AW35122FDR pinout in §3** — but the value string is not present in the extracted text near that symbol. Every other four-ball load switch on this board is an AW35122FDR. That is suggestive, not conclusive. **`inferred`.** Reading sheet 6 graphically would settle it.
-
-Note also that this instance's enable is `PYB_RFID_RST`, **not** `PYB_NFC_EN`. Sheet 4 carries the annotation *"PYB_NFC_EN is a spare GPIO pin"*, while M5Stack's firmware and documentation both describe M5IOE1 `PYG4` / `M5IOE1_PIN_4` as "NFC power enable" (`hal_board.cpp:29`). **This is a genuine conflict between the schematic and the vendor's software, and it is recorded here rather than resolved.** It belongs primarily in the device record; it is noted here because it determines which signal actually switches this instance.
-
-#### 4.3 What this architecture buys, and what it costs
-
-- **Rails that cost nothing in sleep.** Touch, microSD and the microphone all disappear in `L2 DeepSleep` without any leakage path, because a load switch has no quiescent draw worth naming when off.
-- **Every one of them is behind an I²C transaction.** Turning the microphone on means talking to the M5IOE1 at `0x4F` first. There is no GPIO shortcut, and the 165 µs turn-on time is dwarfed by the bus transaction. **[INF]**
-- **⚠ M5Unified already owns three of these four rails.** M5Stack's own warning: *"The pins associated with the e-paper display, touch controller, microSD, and PDM microphone are already used by M5Unified. Before modifying them, ensure that the corresponding peripheral has stopped, or the peripheral may stop working or require reinitialization."* Cutting `TP_VDD` under a running touch driver leaves the driver holding a handle to a dead device.
-- **Not every `L3B` rail is a load switch.** `EPD_3V3_L3B` is produced by an [SSP7615-33DFR](../../generic/ssp7615-33dfr/README.md) LDO (`U5`, sheet 2) from `VBUS_L0`, not by an AW35122 from `3V3_L2`, and `BL_15V_L3B` comes from the [AW9967DNR](../aw9967/README.md) boost. Do not assume the whole domain is switched the same way.
-
-### `devices/m5stack/dinmeter` and `devices/m5stack/dinmeter-v1.1`
-
-→ [M5Stack DinMeter (K134)](../../../devices/m5stack/dinmeter/README.md) ·
-→ [M5Stack DinMeter v1.1 (K134-V11)](../../../devices/m5stack/dinmeter-v1.1/README.md)
-
-*Added 2026-09-04 by the DinMeter research pass. Evidence: `K134_DIN_Meter_v1.0-schematic.pdf`
-(byte-identical for v1.0 and v1.1, SHA-256 `03ec3353…`) and `Sch_StampS3_v0.3.3.pdf`, both
-Altium marker layers parsed.*
-
-Two entirely separate roles, one on the carrier and one inside the core module:
-
-| Where | Designator | Input | `EN` from | Output | Load |
-|---|---|---|---|---|---|
-| **DinMeter carrier** (both revisions) | `U6` | `+3.3V` | `LCD_BL` = **GPIO9** | `FPC_LCD_BL` | 1.14 in ST7789 panel backlight LEDs via `FPC1` pin 8 |
-| **Stamp-S3A module only** (rev v0.3.3) | `U2` | `VDD_3V3` | `DISP_BL` = **GPIO38** (internal to the module) | `BL_3V3` | rear LCD-FPC backlight rail **and** the module's WS2812B-2020 RGB LED |
-
-**Carrier `U6`.** The schematic value string is `AW35122FDR`, at (597, 521.3) beside the `U6`
-outline; ball labels `A1`, `A2`, `B1`, `B2` and the pin names `VIN`, `VOUT`, `EN`, `GND` are all
-recovered from the marker layer. It is driven as a **PWM-dimmed** backlight switch —
-`espressif/esp-board-manager` models GPIO9 as an LEDC channel (`ledc_backlight`, channel 0,
-timer 0, 5 kHz, 10-bit), so the part is being switched at 5 kHz rather than used as a static
-enable. Its 165 µs typical rise time is far shorter than a 200 µs LEDC period, so dimming works,
-but the *linearity* of the resulting brightness curve is a function of that rise time and has
-not been characterised here.
-
-**Stamp-S3A `U2` — the interesting one.** On the previous Stamp-S3 (board rev v0.2) this switch
-was an [SGM2578](../../sgmicro/sgm2578/README.md) (second value string `WS4622C-4/TR`) gating only
-the rear FPC backlight rail, while the WS2812B RGB LED sat on the always-on `VDD_3V3`. On rev
-v0.3.3 the part became an AW35122FDR **and the RGB LED was moved onto its output**. That is the
-single firmware-visible difference between Stamp-S3 and Stamp-S3A, and therefore between
-DinMeter v1.0 and v1.1: on v1.1, **GPIO38 must be driven high before the RGB LED will light**.
-M5Stack states this explicitly on the DinMeter v1.1 page; the schematic confirms the net change.
-Full treatment: [`components/m5stack/stamp-s3a/README.md` §3](../../m5stack/stamp-s3a/README.md).
-
-**Integration note specific to these boards.** The AW35122's `EN` has an internal ~7.1 MΩ
-pull-down (§1.1), so both rails default **off** at reset — the panel backlight is dark and the
-RGB LED is unlit until firmware acts. On the DinMeter that is desirable (no flash of a
-white backlight during boot); on a Stamp-S3A it is the reason a straight port of Stamp-S3 LED
-code appears to do nothing.
-
----
-
-### M5Stack Stamp-S3A, and every board that uses it
-
-Designator **U2** on `Sch_StampS3_v0.3.3.pdf`. `VIN` ← `VDD_3V3`, `VOUT` → **`BL_3V3`**,
-**`EN` ← `DISP_BL` = GPIO 38**.
-
-`BL_3V3` supplies the **LCD backlight *and* the [WS2812](../../worldsemi/ws2812/README.md) RGB
-LED**. On the older **StampS3 v0.2** the WS2812 was fed from the always-on `VDD_3V3` and this
-part was an [SGM2578](../../sgmicro/sgm2578/README.md) doing a different job — verified by
-diffing U3's `VDD` net across the two schematics.
-
-**Consequence, and it is documented behaviour:** PWM-dimming the backlight chops the LED's
-supply. M5Stack states on the Cardputer v1.1 page — *"when the LCD backlight brightness is below
-100%, RGB will not be powered properly"* — and **omits the same warning from the Cardputer ADV
-page**, which inherits the identical arrangement.
-
-Boards affected: [Cardputer v1.1](../../../devices/m5stack/cardputer-v1.1/README.md),
-[Cardputer ADV](../../../devices/m5stack/cardputer-adv/README.md),
-[Cardputer Mesh Kit](../../../devices/m5stack/cardputer-mesh-kit/README.md). **Not** the
-[Cardputer v1.0](../../../devices/m5stack/cardputer-v1.0/README.md), which is therefore the only
-Cardputer whose RGB LED is independent of the backlight.
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.4.*
-
-## 5. Drivers and libraries
-
-**Not applicable at the component level** — the part has no bus interface. On the PaperMono the control path is:
-
-```cpp
-// Arduino / ESP-IDF, via the M5IOE1 library
-ioe1.pinMode(M5IOE1_PIN_12, OUTPUT);       // PDM_VDD  (PYG12)
-ioe1.digitalWrite(M5IOE1_PIN_12, HIGH);    // enable the microphone rail
-```
-
-> ⚠ **Pin-numbering trap.** M5IOE1 labels are 1-based but the enum *values* are 0-based — `M5IOE1_PIN_3 == 2` (`M5IOE1/src/M5IOE1.h:34`). Passing a documentation "PYG*n*" number straight into a raw register write targets pin *n* + 1. Use the enum. **[SRC]**
-
----
-
-## 6. Integration pitfalls
-
-1. **Confirm you have AW35122, not AW3512** (§1.1). If the board omits an external `EN` pull-down, the substitution is a live hazard.
-2. **No reverse-current blocking.** If the downstream rail can be back-driven (a card inserted with its own supply, an FPC shorted to another rail), current flows back through the body diode.
-3. **R<sub>DS(on)</sub> triples between 3.3 V and 1.2 V** (§2). Budget the drop at your actual supply, not at 5.5 V.
-4. **The output discharges on disable.** Convenient for clean power cycling, but it means you cannot use the switch to "park" a rail at its last value.
-5. **1.5 A continuous is a thermal figure too** — θ<sub>JA</sub> is 166 °C/W in a 1 mm² package.
-
----
-
-## 7. Alternatives
-
-| Part | vs. AW35122 | When |
-|---|---|---|
-| **AW3512** | Same part, **no internal `EN` pull-down** | Only when the board provides its own pull-down |
-| TI **TPS22918** / **TPS22916** | Comparable class, with reverse-current blocking on some variants, US-vendor documentation | When back-drive is possible, or Awinic sourcing is a problem |
-| **[SGM40567](../../sgmicro/sgm40567/README.md)**-class discrete PMOS + gate resistor | Cheaper BOM | Loses slew-rate control and output discharge; inrush becomes your problem |
-| An **enable-pin LDO** (e.g. [SSP7615-33DFR](../../generic/ssp7615-33dfr/README.md)) | Regulates as well as switches | When the downstream rail needs its own regulation — which is why the PaperMono uses one for `EPD_3V3_L3B` |
-
----
-
-## 8. Open questions
-
-- Whether sheet 6's `U1` is genuinely an AW35122FDR (§4.2).
-- Whether the `PYB_NFC_EN` "spare GPIO" annotation on sheet 4 contradicts M5Stack's firmware, or whether the net is repurposed somewhere not visible in the extracted text (§4.2).
-- No hardware measurement of turn-on slew, inrush or rail settling on any of the four instances.
-
----
-
-## Manufacturer
-
-**Shanghai Awinic Technology Co., Ltd.** No vendor sourcing guide exists in this repository yet; the working retrieval recipe is recorded in the [AW32901 record](../aw32901/README.md#manufacturer) and applies unchanged here — use the **full ordering part number** in `https://www.awinic.com/en/productDetail/<PART>`, read `data-file-url`, then fetch through `https://www.awinic.com/en/download?file=…&fileName=…`.
-
-## Related pages
-
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — drives all four enable lines
-- [Awinic AW39112DNR](../aw39112/README.md) — the touch-bus translator powered from `TP_VDD`, instance 2's rail
-- [Awinic AW9967DNR](../aw9967/README.md) — the other `L3B` rail, produced by a boost rather than a switch
-- [SSP7615-33DFR](../../generic/ssp7615-33dfr/README.md) — the LDO used for `EPD_3V3_L3B`
-- [FocalTech FT6336G](../../focaltech/ft6336g/README.md) — powered by instance 2
-- [LMD4737T261-AC02 PDM microphone](../../generic/lmd4737t261-ac02-pdm-microphone/README.md) — powered by instance 3
-- [microSD / SDMMC interface](../../generic/micro-sd-sdmmc/README.md) — powered by instance 1
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | AW3512 / AW35122 datasheet | Awinic | primary | datasheet | `https://www.awinic.com/en/download?file=doc/20230609wm/b56e7f1e-10ba-4096-aa95-2339ccbad7cc.pdf&fileName=DS_AW35122_EN_V1.0` | 2026-09-01 | **V1.0**, July 2019, 18 pp, 1 329 728 B | Pin definition, R<sub>DS(on)</sub> table, absolute maxima, the AW3512/AW35122 `EN` pull-down difference | `artifacts/aw3512-aw35122-datasheet-en-v1.0.pdf` |
-| D2 | AW35122FDR product page | Awinic | primary | official page | <https://www.awinic.com/en/productDetail/AW35122FDR> | 2026-09-01 | — | Category, `FCDFN 1X1-4L` package, t<sub>R</sub> 165 µs, active-high enable, output discharge, no reverse-current block | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | Every instance, rail and enable net in §4 | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | `M5PaperMono-UserDemo` HAL — `hal_tf_card.cpp`, `hal_mic.cpp`, `hal_board.cpp`, `app_sleep_wake.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | `main` @ `c1099107271d31a0678d661a896e2b04dbb331ea`, MIT | The M5IOE1 pin assignments in §4.1 | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-| S3 | `M5IOE1/src/M5IOE1.h` | M5Stack | primary | repository | <https://github.com/m5stack/M5IOE1> | 2026-09-01 | `main` @ `846eec7d05e25c09013be2acdb8804487f48a62e`, MIT | The 1-based label / 0-based enum trap in §5 | `scratch/m5stack-papermono/repos/M5IOE1/` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/aw3512-aw35122-datasheet-en-v1.0.pdf` | 1 329 728 | `35871c05ae81890b29f1223deca01ce8da5203539e72dbd826d473b3b1e925ee` | 18 |
-
-**Method note.** D1 validated as `%PDF`, 18 pages, text layer intact. Retrieved with plain `curl` and a Chrome 131 User-Agent; no fallback needed and no login required.
diff --git a/components/awinic/aw35122/artifacts/aw3512-aw35122-datasheet-en-v1.0.pdf b/components/awinic/aw35122/artifacts/aw3512-aw35122-datasheet-en-v1.0.pdf
deleted file mode 100644
index 3e250eb..0000000
Binary files a/components/awinic/aw35122/artifacts/aw3512-aw35122-datasheet-en-v1.0.pdf and /dev/null differ
diff --git a/components/awinic/aw39112/README.md b/components/awinic/aw39112/README.md
deleted file mode 100644
index ad23503..0000000
--- a/components/awinic/aw39112/README.md
+++ /dev/null
@@ -1,212 +0,0 @@
-# Awinic AW39112 (AW39112DNR)
-
-> 2-bit **bidirectional voltage-level translator with no direction-control pin**, for open-drain and push-pull signals, with integrated pull-ups on both ports and a single `OE` that can take the whole part into an ultra-low-power state.
-> Research snapshot **2026-09-01**. Fitted **twice** on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — once as the gate that keeps the IP2315 charger off the shared I²C bus, once as the touch controller's bus interface. **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Awinic `AW39112` datasheet **V1.6**, December 2025 — local copy `artifacts/aw39112dnr-datasheet-en-v1.6.pdf` | `not-tested` |
-| **[VP]** | Awinic product page for `AW39112DNR`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Ordering part | **`AW39112DNR`** | **[SCH]**, **[VP]** |
-| Manufacturer | **Shanghai Awinic Technology Co., Ltd.** | **[DS]** |
-| Category | *"Voltage level translators"* — *"2-Bit Bidirectional Voltage-Level Translator for Open-Drain and Push-Pull Applications"* | **[VP]**, **[DS]** |
-| Package (`DNR` suffix) | **DFN-8L, 1.4 mm × 1.0 mm × 0.37 mm** | **[DS]** |
-| Package (`FOR` suffix) | FOWLP-8B, 0.928 × 1.928 × 0.463 mm | **[DS]** |
-| Datasheet | **`DS_AW39112DNR_FOR_EN_V1.6`**, December 2025, 27 pp | **[DS]** cover; **[VP]** lists the document dated **2025-12-19** |
-| Lifecycle | Active | **[VP]** |
-
----
-
-## 2. Key limits and capability **[DS Features]**
-
-| Parameter | Value |
-|---|---|
-| Channels | **2**, bidirectional, non-inverting |
-| Direction control | **None** — auto-sensing |
-| A port / `VCCA` | **1.1 V – 3.6 V** |
-| B port / `VCCB` | **1.65 V – 5.5 V** |
-| Constraint | **V<sub>CCA</sub> ≤ V<sub>CCB</sub>** |
-| Max data rate, push-pull | **24 Mbps** |
-| Max data rate, open-drain | **2 Mbps** |
-| Pull-up resistors | **Integrated on both A and B ports** |
-| Power-supply sequencing | **None required** — either rail may ramp first |
-| `OE` supply domain | **`VCCA`** |
-| Low-power state | `OE` low → ultra-low consumption |
-| Latch-up | > ±200 mA, JESD 78 |
-| Supported nodes | 1.2 / 1.8 / 2.5 / 3.3 / 5 V |
-| Applications named by the vendor | **I²C / SMBus**, UART, GPIO |
-
-> ⚠ **2 Mbps is the open-drain figure, and I²C is open-drain.** A 400 kHz I²C bus is comfortably inside that, but this part is not a general-purpose high-speed translator when used on an open-drain bus.
-
-> ⚠ **`OE` is supplied from `VCCA`.** The datasheet recommends tying it to GND through an external pull-down so that all I/O default to their supply rails, and states the sequencing rule plainly: *"OE should be enabled after both VCCA and VCCB are established."* **[DS]** Asserting `OE` before both rails exist is a documented misuse.
-
----
-
-## 3. Pinout **[DS Pin Definition]**
-
-| Pin (DNR) | Pin (FOR) | Name |
-|---:|---|---|
-| 1 | C1 | `VCCA` |
-| 2 | D2 | `A1` |
-| 3 | D1 | `A2` |
-| 4 | B1 | `GND` |
-| 5 | C2 | `OE` |
-| 6 | A1 | `B2` |
-| 7 | A2 | `B1` |
-| 8 | B2 | `VCCB` |
-
-Recommended decoupling: 0.1 µF on each of `VCCA` and `VCCB`. **[DS Typical Application Circuit]**
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md). Two instances, both on the **shared system I²C bus** (ESP32-S3 `GPIO47` SDA / `GPIO48` SCL), and both used as *switches* as much as translators.
-
-#### 4.1 `U3` (sheet 2) — the IP2315 charger gate
-
-| Pin | Name | Net | Domain |
-|---:|---|---|---|
-| 1 | `VCCA` | `VBUS_L0` | system logic side |
-| 2 | `A1` | `G48_SYS_SCL` | ESP32-S3 GPIO48 |
-| 3 | `A2` | `G47_SYS_SDA` | ESP32-S3 GPIO47 |
-| 4 | `GND` | `GND` | |
-| **5** | **`OE`** | **`PYB_CHG_IIC`** | from M5IOE1 `PYG11_PWM3` (`U17` pin 10/11, sheet 4) |
-| 6 | `B2` | `CHG_SYS_SDA` | → [IP2315](../../injoinic/ip2315/README.md) pin 9 (`LED2`/`SDA`) |
-| 7 | `B1` | `CHG_SYS_SCL` | → IP2315 pin 8 (`LED1`/`SCL`) |
-| 8 | `VCCB` | **`VBAT_L0`** | battery side |
-
-**This is the single most consequential use of the part on the board**, and both halves of the design are deliberate:
-
-- **`VCCB = VBAT_L0`** means the charger-side bus idles at battery voltage. The IP2315 selects I²C mode at power-up *based on those pins being pulled to V<sub>BAT</sub>* — see [IP2315 §3](../../injoinic/ip2315/README.md#3--the-ic-pins-are-the-led-driver-pins--this-is-the-whole-hazard). The translator's integrated B-port pull-ups (§2) tracking `VCCB` are what supply that condition.
-- **`OE = PYB_CHG_IIC`** turns the charger's presence on the shared bus into a firmware decision. M5Stack's driver connects it only for the duration of a transaction and disconnects afterwards (`M5Unified/src/utility/Power_Class.cpp:78–80, 85`, with a 64-attempt scan loop at `:88–96` and disconnects at `:2399`, `:2724`). **[SRC]**
-
-M5Stack's own product-page warning is the reason: *"do not keep the IP2315 mounted on the I2C bus for extended periods; disconnect it promptly after communication to avoid reducing bus communication stability."* **[DOC]**
-
-Adjacent parts on this net that the text-layer extraction identified but did not fully resolve: `Q5` (`SK2301AAT`, P-channel), `Q2` (`SK2302AAT`, N-channel) with `R9` = 100 kΩ, `R19` = 10 kΩ, `R21` = 10 kΩ, `R45`, `C12` = 100 nF. `VBAT_DET` appears in the same cluster. Their exact roles were **not** resolved and are not asserted here. **[SCH]**
-
-#### 4.2 `U19` (sheet 4) — the touch-controller bus branch
-
-| Pin | Name | Net | Domain |
-|---:|---|---|---|
-| 1 | `VCCA` | `TP_VDD` | touch rail (switched — see below) |
-| 2 | `A1` | `TP_SYS_SCL` | → FPC `J4` |
-| 3 | `A2` | `TP_SYS_SDA` | → FPC `J4` |
-| 4 | `GND` | `GND` | |
-| **5** | **`OE`** | **`TP_VDD`** | tied to the touch rail itself |
-| 6 | `B2` | `G47_SYS_SDA` | ESP32-S3 GPIO47 |
-| 7 | `B1` | `G48_SYS_SCL` | ESP32-S3 GPIO48 |
-| 8 | `VCCB` | `3V3_L2` | system logic rail |
-
-Here the translator is used as an **automatic isolator**: `TP_VDD` is switched by [`U18` (AW35122FDR)](../aw35122/README.md) under M5IOE1 `PYG13`, and both `VCCA` **and** `OE` hang off that rail. When the touch controller is powered down, `OE` falls with it and the [FT6336G](../../focaltech/ft6336g/README.md) branch drops off the system bus by construction — no separate control signal, no firmware step, no possibility of forgetting.
-
-That is a neat piece of design and worth stating explicitly, because it is easy to misread the schematic as "a redundant translator between two 3.3 V rails". It is not a level shift; **it is a fail-safe bus isolator that costs one part.** **[INF]**
-
-`R58` = 10 kΩ (to `TP_VDD`) and `R59` = 1.2 Ω sit on the `J4` side; `C68` = 10 µF/10 V decouples `TP_VDD`. **[SCH]**
-
-#### 4.3 Both instances honour the datasheet's sequencing rule — one by accident of topology
-
-The datasheet requires `OE` to be asserted only after both supplies are up (§2).
-
-- **`U19` satisfies this structurally**: `OE` *is* `VCCA`, so it cannot lead `VCCA`. `VCCB` (`3V3_L2`) is up long before `TP_VDD` is switched on, because the M5IOE1 that switches it runs from `3V3_L2`. **[INF]**
-- **`U3` depends on firmware**: `PYB_CHG_IIC` comes from the M5IOE1, which itself runs from `3V3_L2` = `VBUS_L0`-derived, while `VCCB` is `VBAT_L0` — present whenever there is a battery at all. So `OE` cannot be asserted before either rail exists. **[INF]**
-
-Note the `VCCA ≤ VCCB` constraint (§2) is also satisfied in both cases: `VBUS_L0 ≤ VBAT_L0` (they are joined through the 0 Ω `R20`, so equal), and `TP_VDD ≤ 3V3_L2` (`TP_VDD` is `3V3_L2` through a load switch, so slightly lower).
-
----
-
-## 5. Drivers and libraries
-
-**Not applicable at the component level** — no bus interface, no registers. On the PaperMono the only software that touches it is whatever drives the `OE` nets:
-
-```cpp
-// U3's OE — via M5IOE1 pin 11 (label PYG11_PWM3), enum value 10
-ioe1.pinMode(M5IOE1_PIN_11, OUTPUT);
-ioe1.digitalWrite(M5IOE1_PIN_11, HIGH);   // charger onto the bus
-// ... transaction at 0x75 ...
-ioe1.digitalWrite(M5IOE1_PIN_11, LOW);    // and off again
-```
-
-M5Unified wraps this as `set_papermono_ip2315_enabled()`. **[SRC]** `U19` has no software at all.
-
-Awinic publishes an **evaluation board**, `AW39112DNR_EVB_V1.0`, listed on the product page. **[VP]**
-
----
-
-## 6. Integration pitfalls
-
-1. **`VCCA ≤ VCCB` is a hard constraint** (§2), not a recommendation. The A side is the *lower* voltage domain.
-2. **Assert `OE` only after both rails are up** (§2). Tying `OE` to `VCCA` — as `U19` does — makes this impossible to get wrong.
-3. **Pull-ups are integrated.** Adding external I²C pull-ups on a translated branch changes the bus's effective pull-up strength on that side; check before copying a pull-up value from another design.
-4. **2 Mbps open-drain ceiling** (§2). Fine for 400 kHz I²C, not for a fast SPI-like open-drain link.
-5. **This part hides a device from a bus scan.** A shared-bus device behind an `OE` that firmware has not asserted is simply absent. Budget for that in your enumeration code rather than treating a missing address as a hardware fault — the PaperMono's charger is exactly this case.
-
----
-
-## 7. Alternatives
-
-| Part | vs. AW39112 | When |
-|---|---|---|
-| TI **TXS0102** | The classic 2-bit auto-direction translator; very well documented | When you want the reference part and its extensive app notes |
-| TI **PCA9306** | 2-bit I²C-specific translator, no `OE` low-power state on some variants | Pure I²C level shifting |
-| NXP **NTS0102** | Comparable | Second source |
-| **Discrete dual N-FET translator** (the classic Philips AN97055 circuit) | Two FETs and four resistors | Cheapest; loses the `OE` gate, which is the entire point on this board |
-| **[SGM40567](../../sgmicro/sgm40567/README.md)**-class analogue switch | Switches without translating | When both sides are already the same voltage and you only need the gate |
-
----
-
-## 8. Open questions
-
-- The exact roles of `Q2`/`Q5`/`R9`/`R19`/`R21`/`R45` around `U3`, and where `VBAT_DET` is generated (§4.1).
-- Whether the integrated pull-ups alone hold `CHG_SYS_SCL/SDA` at V<sub>BAT</sub>, or whether one of the discrete parts above supplies additional pull-up. This determines how robust the IP2315's mode detection actually is on a partly-discharged cell.
-- No hardware measurement of bus rise times on either translated branch.
-
----
-
-## Manufacturer
-
-**Shanghai Awinic Technology Co., Ltd.** No vendor sourcing guide exists in this repository yet; see the [AW32901 record](../aw32901/README.md#manufacturer) for the working retrieval recipe (full ordering part number → `productDetail` page → `data-file-url` → `/en/download`).
-
-Worth noting for this part specifically: the product page's **Technical documentation** table exposes the document title and date directly (`Datasheet | DS_AW39112DNR_FOR_EN_V1.6 | 英文 | 2025-12-19`), which is the cleanest way to confirm you have the current revision before downloading.
-
-## Related pages
-
-- [Injoinic IP2315](../../injoinic/ip2315/README.md) — the device `U3` gates
-- [Awinic AW35122](../aw35122/README.md) — switches `TP_VDD`, which powers and enables `U19`
-- [FocalTech FT6336G](../../focaltech/ft6336g/README.md) — the device behind `U19`
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — drives `U3`'s `OE`
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | AW39112 datasheet | Awinic | primary | datasheet | `https://www.awinic.com/en/download?file=doc/202512/460d535f-8aa2-4946-862a-131be2e3fb79.pdf&fileName=DS_AW39112DNR_FOR_EN_V1.6` | 2026-09-01 | **V1.6**, Dec 2025, 27 pp, 673 762 B | Pin definition, supply ranges, `VCCA ≤ VCCB` rule, data rates, `OE` sequencing requirement, integrated pull-ups | `artifacts/aw39112dnr-datasheet-en-v1.6.pdf` |
-| D2 | AW39112DNR product page | Awinic | primary | official page | <https://www.awinic.com/en/productDetail/AW39112DNR> | 2026-09-01 | doc dated 2025-12-19 | Category, package options, EVB availability | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | Both instances' net assignments in §4 | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | `M5Unified/src/utility/Power_Class.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5Unified> | 2026-09-01 | `master` @ `8530f537…`, MIT | The gating discipline in §4.1 | `scratch/m5stack-papermono/repos/M5Unified/` |
-| S3 | PaperMono product page | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | The verbatim bus-stability warning | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono.html` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/aw39112dnr-datasheet-en-v1.6.pdf` | 673 762 | `c248668d7cf5fc2ab59a4ae67a7a15c9fc84c7be520571a04542217fe71b9151` | 27 |
-
-**Method note.** D1 validated as `%PDF`, 27 pages, text layer intact. Retrieved with plain `curl` and a Chrome 131 User-Agent; no fallback needed and no login required.
diff --git a/components/awinic/aw39112/artifacts/aw39112dnr-datasheet-en-v1.6.pdf b/components/awinic/aw39112/artifacts/aw39112dnr-datasheet-en-v1.6.pdf
deleted file mode 100644
index 4538790..0000000
Binary files a/components/awinic/aw39112/artifacts/aw39112dnr-datasheet-en-v1.6.pdf and /dev/null differ
diff --git a/components/awinic/aw9364/README.md b/components/awinic/aw9364/README.md
deleted file mode 100644
index 4eea778..0000000
--- a/components/awinic/aw9364/README.md
+++ /dev/null
@@ -1,84 +0,0 @@
-# Awinic AW9364 (AW9364DNR)
-
-- **Category:** LED backlight **boost driver** with a one-wire (pulse-count) brightness
-  interface; typically 4 parallel LED strings.
-- **Manufacturer:** Shanghai Awinic Technology Co., Ltd.
-- **Retrieved:** 2026-09-07
-- **Sibling Awinic records here:** [`aw32901`](../aw32901/README.md) ·
-  [`aw35122`](../aw35122/README.md) · [`aw39112`](../aw39112/README.md) ·
-  [`aw9967`](../aw9967/README.md)
-
-The backlight driver of the **LilyGO T-Display-S3**, designator `U4`.
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part marking on the schematic | **`AW9364DNR`** | designator/part string `EP 9 U4 AW9364DNR LEDK1 LEDK2 LEDK3 LEDK4` recovered from `T_Display_S3.pdf` @ `ec889e7` |
-| Package pins visible | `EP` (exposed pad), plus `LEDK1`–`LEDK4` — **four LED cathode channels** | same |
-| Datasheet | **not retrieved.** Awinic does not publish AW9364 on an open portal, and LilyGO does not mirror it | — |
-| Local artifact | **none** | — |
-
-> **This record is built from a schematic part string and general knowledge of the AW936x
-> family, not from a datasheet.** That is stated up front because it is unusual for this
-> repository. Nothing below is transcribed from a primary document.
-
-## 2. What the four LEDK pins mean for the board
-
-Four cathode channels means the panel's backlight is **four LED strings in parallel**, each
-current-regulated. That is a normal arrangement for a 1.9″ strip and it explains why the
-board's backlight is bright and reasonably even.
-
-## 3. The control interface, and why PWM behaves oddly
-
-The AW936x family accepts brightness in two ways:
-
-1. **Enable/PWM.** Hold the control pin high for on; PWM it for crude dimming. This is what
-   every LilyGO example and every community sketch does — `ledcAttach(38, …); ledcWrite(38, d)`.
-2. **One-wire pulse count.** Pull the pin low and back high *N* times within a timeout window
-   to select one of 16 brightness steps, then hold high. The chip counts edges.
-
-**These two mechanisms interact.** A PWM waveform *is* a pulse train, so at some frequencies
-and duties the driver can interpret PWM edges as brightness commands. The practical symptom is
-brightness that steps rather than ramps, or that changes when the PWM frequency changes.
-
-**Evidence status: `inferred`.** The mechanism is the documented behaviour of one-wire LED
-drivers of this class; **it has not been verified on an AW9364 datasheet or on hardware**, and
-no LilyGO document mentions it. It is recorded because it is the only available explanation for
-the non-linear dimming behaviour users describe, and because the alternative — assuming linear
-PWM dimming — silently produces a bad UI.
-
-**What would settle it:** obtain the AW9364 datasheet, or measure backlight luminance against
-PWM duty at two PWM frequencies.
-
-## 4. Board integration notes
-
-- The driver sits on the **gated `V3V` rail**, so it is dead until GPIO15 is high. A board with
-  GPIO38 high and GPIO15 low shows **no backlight at all** — which people read as a dead
-  backlight rather than a dead rail.
-- Conversely GPIO38 high with GPIO15 high but no panel initialisation gives a **lit but blank**
-  screen, the classic "backlight on, nothing displayed" report.
-- Arduino core 3.x renamed `ledcSetup`/`ledcAttachPin` to `ledcAttach`/`ledcDetach`; LilyGO's
-  dimming snippets predate that.
-  ([firsthand report](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/),
-  2026-05-25)
-
-## 5. Gaps
-
-- **No datasheet.** Awinic's public site does not list AW9364; no vendor mirror was found in
-  any LilyGO repository. Two acquisition routes worth trying next: LCSC's product page for the
-  `AW9364DNR` order code, and Awinic's `datasheet` subdomain used by the four sibling records
-  in this repository.
-- The one-wire timing window, step count and the exact PWM frequency at which the two
-  mechanisms collide are all **unknown**.
-- Not verified on hardware.
-
-## 6. Used by
-
-### LilyGO T-Display-S3 / T-Display-S3 Touch
-→ [`devices/lilygo/t-display-s3`](../../../devices/lilygo/t-display-s3/README.md)
-
-Designator `U4`. Drives the 1.9″ panel's backlight from **GPIO38** (`PIN_LCD_BL`,
-`TFT_BL` in `Setup206`, `TFT_BACKLIGHT_ON HIGH`). Four LED channels, `LEDK1`–`LEDK4`.
-Powered from the GPIO15-gated `V3V` rail. Practical guidance:
-[`features/display.md`](../../../devices/lilygo/t-display-s3/features/display.md).
diff --git a/components/awinic/aw9967/README.md b/components/awinic/aw9967/README.md
deleted file mode 100644
index ca35a53..0000000
--- a/components/awinic/aw9967/README.md
+++ /dev/null
@@ -1,273 +0,0 @@
-# Awinic AW9967 (AW9967DNR)
-
-> High-efficiency **boost WLED driver** with an integrated 40 V switch FET, 1.1 MHz fixed switching frequency, single-pin PWM dimming down to 0.3 % duty, and a 200 mV feedback reference that sets full-scale LED current through one resistor.
-> Research snapshot **2026-09-01**. Fitted as **`U11`** on sheet 2 of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), where it generates **`BL_15V_L3B`** — the e-paper **frontlight** supply. **No hardware was available.**
-
-> **Headline finding:** M5Stack's own display library drives this part's dimming input at **5 kHz**, while the datasheet specifies a PWM dimming range of **10 kHz – 100 kHz**. See [§6.2](#62--m5gfx-drives-the-dimming-input-at-half-the-datasheets-minimum-frequency).
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Awinic `AW9967` datasheet **V1.8**, March 2025 — local copy `artifacts/aw9967-datasheet-en-v1.8.pdf` | `not-tested` |
-| **[VP]** | Awinic product page for `AW9967DNR`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Ordering part | **`AW9967DNR`** | **[SCH]** sheet 2, `U11`; **[VP]** |
-| Manufacturer | **Shanghai Awinic Technology Co., Ltd.** | **[DS]** |
-| Category | *"Series backlight LED drivers"* — *"High Efficiency, Support 0.3 % PWM Dimming Boost WLED Driver"* | **[VP]** |
-| Package (`DNR`) | **DFN-6L, 2.0 mm × 2.0 mm × 0.75 mm**, θ<sub>JA</sub> **84 °C/W** | **[DS]**, **[VP]** |
-| Package (`FSR`) | SOT23-5L, θ<sub>JA</sub> 120 °C/W | **[DS]** |
-| Datasheet | **`DS_AW9967_EN_V1.8`**, March 2025, 23 pp | **[DS]** cover |
-| Lifecycle | Active | **[VP]** |
-
-The datasheet notes the DNR package has materially better thermal dissipation than the SOT23 variant — 84 vs 120 °C/W — which is the stated reason the DFN part exists. **[DS]**
-
----
-
-## 2. Key limits and capability **[DS]**
-
-| Parameter | Value |
-|---|---|
-| Input voltage `VIN` | **2.7 V – 5.5 V** (abs. max −0.3 to 6 V) |
-| `FB`, `CTRL` abs. max | −0.3 to 6 V |
-| **`SW` abs. max** | **−0.3 to 40 V** |
-| Internal switch FET | 40 V, current limit **2.3 / 2.7 A** (min/typ) |
-| Switching frequency | **800 / 1100 / 1400 kHz** (min/typ/max) — fixed, not spread-spectrum |
-| Maximum duty cycle | 90 / 93 % (min/typ) |
-| String capability | up to **10 LEDs in series**, parallel strings supported |
-| **Open-LED OVP** | **36 – 38 V** |
-| Efficiency | up to 89 % for 2P7S |
-| Per-channel current | up to **20 mA** **[VP]** |
-| R<sub>DS(on)</sub> | 0.25 Ω @ V<sub>IN</sub> = 3.6 V |
-| Other protections | over-current, over-temperature, LED-open; built-in soft start |
-| Temperature | −40 to +85 °C |
-| ESD | ±2 kV HBM, ±1.5 kV CDM |
-
-### 2.1 Current setting and dimming — the numbers that matter **[DS Electrical Characteristics]**
-
-Full-scale LED current is **`I = V_REF / R_SET`**, where `R_SET` is a single resistor from `FB` to GND:
-
-| Parameter | Condition | Min | **Typ** | Max |
-|---|---|---:|---:|---:|
-| `V_REF` | PWM duty **100 %** | 194 mV | **200 mV** | 205 mV |
-| `V_REF_PWM` | PWM duty 1 % | 1.575 mV | 2.25 mV | 2.925 mV |
-| `V_REF_PWM` | PWM duty 0.5 % | 0.5 mV | 1.25 mV | 2 mV |
-| `V_REF_PWM` | PWM duty 0.3 % | — | — | — (minimum supported duty) |
-| **`f_PWM1`** — **PWM dimming frequency** | — | **10 kHz** | — | **100 kHz** |
-| `D_PWM` — dimming duty range | — | 0.3 % | — | 100 % |
-| `t_MIN_ON` | minimum on-pulse width | — | — | 50 ns |
-| `I_Q` | operating quiescent, `V_FB` = 1 V | — | 100 µA | 250 µA |
-| Shutdown current | `V_CTRL` = GND, V<sub>IN</sub> = 4.2 V | — | 0.1 µA | 1 µA |
-
-The datasheet states the dimming range in prose too: *"The current of WLED can also be set with duty cycle of PWM signal applied to the CTRL pin with 10 kHz ~ 100 kHz."* **[DS §General Description]**
-
-Note the strong non-linearity at the bottom of the range: at 1 % duty the reference is 2.25 mV rather than the 2.0 mV a linear law would give, and at 0.5 % it is 1.25 mV rather than 1.0 mV. Low-brightness behaviour is not simply proportional to duty.
-
----
-
-## 3. Pinout **[DS Pin Description]**
-
-| Pin (DNR) | Pin (FSR) | Name | Function |
-|---:|---:|---|---|
-| **1** | 6 | `FB` | Feedback. **Connect `R_SET` from `FB` to GND** |
-| 2 | — | `NC` | No connection |
-| **3**, **7** | 2 | `GND` | Ground. **Pin 7 is the exposed pad and must be soldered to the board and connected to GND** |
-| **4** | 1 | `SW` | Switching node |
-| **5** | 4 | `CTRL` | **Enable pin — also the PWM digital-dimming input** |
-| **6** | 5 | `VIN` | Power |
-
-> ⚠ **`CTRL` is both enable and dimming.** A duty of zero is a shutdown command, not "0 % brightness". There is no separate enable, so a driver that writes duty = 0 to dim to black also collapses the boost output and pays the soft-start cost on the way back up.
-
-### 3.1 Reference application circuit **[DS Typical Application Circuits]**
-
-```
-        L1 = 10 µH            Schottky
- VIN ───────UUUU──────┬──────►|──────► LED string (e.g. 3P10S)
-  │                   │                     │
- CIN1 10 µF        SW │                  COUT1 1 µF/50 V
- CIN2 100 nF (opt) ───┤                  COUT2 33 pF/50 V (opt)
-                 AW9967                      │
-              VIN  CTRL  FB ─── R_SET ───────┴─── (string return)
-                                  │
-                                 GND
-```
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`U11`**, schematic sheet 2, in the block labelled `EINK_BL`.
-
-It produces **`BL_15V_L3B`**, the e-paper frontlight supply — one of the `L3B` rails, i.e. present only in the **L3B All ACTIVE** power state defined on sheet 1.
-
-#### 4.1 Exact wiring **[SCH]**
-
-| Pin | Name | Net / part |
-|---:|---|---|
-| 1 | `FB` | **`BL_FB`** → **`R29` = 18 Ω / 1 %** to GND; also returns from the frontlight connector `J1` |
-| 2 | `NC` | not connected |
-| 3, 7 | `GND` / `EPAD` | `GND` |
-| 4 | `SW` | **`L3` = `FTC201610S100MBCA`, 10 µH** → **`D2` = `RB162VAM-20TR`** Schottky → `BL_15V_L3B` |
-| 5 | `CTRL` | **`PYG3_BL_PWM`** |
-| 6 | `VIN` | **`3V3_L2`** |
-
-Output network: `C25` = **1 µF/50 V**, `C24` = **33 pF/50 V**, `C26` = **`NC`/50 V**. **[SCH]**
-
-**The board uses Awinic's reference circuit essentially verbatim** — 10 µH inductor, Schottky, 1 µF/50 V `COUT1`, 33 pF/50 V `COUT2`, one `R_SET`. `C26` is the depopulated third position. That is a good sign for the analogue design and means the datasheet's characterisation curves should apply directly. **[INF]**
-
-#### 4.2 ⚠ `PYG3_BL_PWM` comes from the **M5PM1**, not the M5IOE1
-
-The net name uses the `PYG` prefix that M5Stack's documentation otherwise reserves for M5IOE1 pins, but the schematic wires it to **`U7` pin 13**, which is the [M5PM1](../../m5stack/m5pm1/README.md) — the pin is labelled `G3_WAKEin(INT3/4)_IRQout_PWM`. **[SCH]** sheet 2
-
-This corroborates, from the schematic, a documentation defect already recorded from the vendor's web pages: the PaperMono product page says *"the frontlight brightness is controlled via `PYG3_BL_PWM` of the M5PM1"* while the PaperMono-**Lite** page says *"`G3_WAKEin` of M5PM1"* — the Lite page is right, and both pages carry an identical PinMap row confirming M5PM1 GPIO3. **[DOC]**
-
-> ⚠ **This one is dangerous, not cosmetic.** `PYG3` **is** also a real and different pin: **M5IOE1 IO3 is the e-paper 3.3 V power enable.** A developer who trusts the PaperMono page's prose and writes to M5IOE1 pin 3 expecting a backlight instead **cuts power to the display panel.**
-
-#### 4.3 ⚠ `R_SET` = 18 Ω gives ≈11 mA, and the schematic's own design note disagrees with itself
-
-Sheet 2 carries a hand-written design note next to the boost:
-
-> *"I set max = Vfb / Rset ≤ 20 mA"*
-> *"if Duty = 100 %, Vfb = Duty × 200 mV + 0.2 mV, Iset = 15 mA，即 Rset = 11R"*
-
-Three numbers, and they do not agree:
-
-| Source | `R_SET` | Resulting full-scale current (V<sub>REF</sub> = 200 mV typ) |
-|---|---:|---:|
-| **Fitted BOM value `R29`** | **18 Ω / 1 %** | **≈ 11.1 mA** |
-| Design note's stated target | — | 15 mA |
-| Design note's stated resistor | 11 Ω | ≈ 18.2 mA |
-
-The note's own arithmetic is inconsistent — 200 mV / 11 Ω is 18.2 mA, not 15 mA; 15 mA would need ≈13.3 Ω. Whatever the intent, **the part actually fitted is 18 Ω**, which puts full-scale frontlight current at roughly **11 mA**, comfortably inside the ≤20 mA ceiling the note sets and well inside the AW9967's 20 mA per-channel rating. **[INF]**, from `executed-success` reads of the fitted value and the datasheet reference voltage.
-
-If you are estimating frontlight power budget for this board, use ~11 mA at full brightness, not 15 or 20.
-
-#### 4.4 How M5GFX actually programs the brightness **[SRC]**
-
-The frontlight is not driven by an ESP32-S3 PWM peripheral. It is driven by the M5PM1's own PWM0 block, configured over I²C at `0x6E`. `M5GFX/src/M5GFX.cpp:819–856` (`struct Light_M5PaperMono`):
-
-| Step | M5PM1 register | Value written | Meaning | Line |
-|---|---|---|---|---|
-| Bring up I²C | — | SDA 47 / SCL 48 | shared system bus | `:823` |
-| `GPIO_DRV` | **`0x13`** | `bitOff 1<<3` | M5PM1 GPIO3 → **push-pull** | `:826` |
-| `GPIO_FUNC0` | **`0x16`** | `bitOn 0xC0` | M5PM1 GPIO3 → **PWM** alternate function | `:829` |
-| `PWM_FREQ_L` / `_H` | **`0x34` / `0x35`** | **5000** | **5 kHz** dimming frequency | `:833–836` |
-| Brightness off | **`0x31`** | `0` | `PWM0_HC` = 0 | `:845` |
-| Brightness on | **`0x30`** (+ `0x31`) | `br = brightness × brightness`; writes `(br>>4)&0xFF`, then `(br>>12) \| 0x10` | **squared / gamma** duty, `0x10` = enable | `:850–853` |
-
-A **linear** brightness write exists in the same file but is **commented out** at `:847`, superseded by the squared curve at `:848–853`. The same 5 kHz figure is used for the RGB LED PWM elsewhere (`RGB_PWM_FREQ_HZ = 5000`, `hal_board.cpp:24`), which suggests it is a house default rather than a value chosen for this driver. **[INF]**
-
----
-
-## 5. Drivers and libraries
-
-**The AW9967 has no bus interface** — it is controlled entirely by the duty cycle on `CTRL`. On the PaperMono the software stack is therefore:
-
-```
-M5GFX  Light_M5PaperMono  ──I²C 0x6E──►  M5PM1 firmware  ──PWM0/GPIO3──►  AW9967 CTRL
-```
-
-| Layer | Where |
-|---|---|
-| Application API | `M5.Display.setBrightness(0–255)` |
-| Panel light class | `M5GFX/src/M5GFX.cpp:819–856` |
-| PMIC register access | [M5PM1 library](../../m5stack/m5pm1/README.md), registers `0x13`, `0x16`, `0x30`, `0x31`, `0x34`, `0x35` |
-
-Awinic publishes a **"Series Backlight Driver Hardware Design Guide" (EN V1.0)** alongside the datasheet on the product page; it was **not** retrieved this session (the filename on the vendor CDN contains the marker `加密` — "encrypted" — and was not tested). **[VP]**
-
----
-
-## 6. Integration pitfalls, in priority order
-
-### 6.1 `CTRL` at 0 % duty is a shutdown, not a dim
-
-See §3. Expect a soft-start ramp when coming back from zero.
-
-### 6.2 ⚠ M5GFX drives the dimming input at half the datasheet's minimum frequency
-
-- **Datasheet:** `f_PWM1` = **10 kHz min, 100 kHz max** (§2.1), stated twice — once in the electrical table, once in the general description. **[DS]**
-- **M5GFX:** writes **5000** to the M5PM1's `PWM_FREQ_L`/`_H` (`M5GFX.cpp:833–836`). **[SRC]**
-
-Both readings are `executed-success`. The **consequence** is `inferred` and unmeasured: below the specified minimum, the internal `V_REF` filter (the datasheet lists a `t_REF` filter time constant) has proportionally longer to droop between pulses, so the plausible symptoms are **visible flicker, audible inductor whine, and a brightness-versus-setting curve that departs from the datasheet's characterisation** — most likely at low duty, where the reference is already only 1–2 mV and non-linear (§2.1).
-
-This is worth flagging for two reasons beyond this board:
-
-1. It compounds with the **squared brightness curve** (§4.4). A setting of 16/255 becomes a duty of roughly (16/255)² ≈ 0.4 % — right at the AW9967's 0.3 % floor, at a switching frequency it is not specified for.
-2. It is a **software-only defect**, if it is one. Writing `10000` instead of `5000` at `M5GFX.cpp:833–836` would bring the part inside spec with no hardware change.
-
-Recorded as a conflict, not resolved: no hardware was available to measure flicker or the actual brightness curve. Anyone with a PaperMono and an oscilloscope or a photodiode can settle it in minutes.
-
-### 6.3 Other pitfalls
-
-3. **`SW` is rated 40 V and OVP trips at 36–38 V.** An open LED string is protected, but a probe or a scope ground clip on `SW` sees a 40 V node.
-4. **The exposed pad is a required electrical connection**, not just thermal (§3).
-5. **`R_SET` is the only current control.** Get it wrong and no amount of firmware fixes the full-scale current — see §4.3 for how easily the intent and the fitted value diverge.
-6. **1.1 MHz fixed frequency, no spread spectrum.** If the board has an AM/LF-sensitive receiver, this is a fixed tone plus harmonics.
-
----
-
-## 7. Alternatives
-
-| Part | vs. AW9967 | When |
-|---|---|---|
-| TI **TPS61165** / **LM3414** | Comparable boost WLED drivers, extensive documentation and app notes | When you want a well-trodden reference design |
-| TI **LM3697** / **LP8556** | I²C-controlled backlight drivers | When you want brightness in registers rather than a PWM pin — removes the whole §6.2 class of problem |
-| **AW9967FSR** | Same silicon, SOT23-5L | When board area beats thermal performance (θ<sub>JA</sub> 120 vs 84 °C/W) |
-| Charge-pump WLED driver | No inductor | Only for very short strings; a 15 V frontlight rail is out of reach |
-
-The AW9967's distinguishing feature is the **0.3 % minimum dimming duty**, which is what lets an e-paper frontlight go genuinely dim for night reading. That capability is exactly what §6.2 puts at risk.
-
----
-
-## 8. Open questions
-
-- Whether 5 kHz on `CTRL` produces observable flicker or brightness non-linearity on real hardware (§6.2). **This is the highest-value open question in this record.**
-- Whether the frontlight LED string is series, parallel or a mix, and how many dies — `J1` on sheet 2 is the frontlight connector, but the panel-side arrangement is not in the schematic. The 10 µH / 1 µF reference values and a `BL_15V` net name suggest a single series string of four or five white LEDs. **[INF]**, unconfirmed.
-- Why the fitted `R_SET` (18 Ω) differs from the design note's own figure (11 Ω) (§4.3).
-- The Awinic "Series Backlight Driver Hardware Design Guide" was not retrieved.
-- No hardware measurement of efficiency, ripple or the actual frontlight current.
-
----
-
-## Manufacturer
-
-**Shanghai Awinic Technology Co., Ltd.** No vendor sourcing guide exists in this repository yet; see the [AW32901 record](../aw32901/README.md#manufacturer) for the working retrieval recipe.
-
-## Related pages
-
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — supplies `CTRL` from its GPIO3/PWM0, and holds registers `0x13`/`0x16`/`0x30`/`0x31`/`0x34`/`0x35`
-- [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) — the e-paper panel this frontlight illuminates
-- [Awinic AW35122](../aw35122/README.md) — the load switches for the other `L3B` rails
-- [Joulwatt JW5712](../../joulwatt/jw5712/README.md) — produces `3V3_L2`, this part's input rail
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | AW9967 datasheet | Awinic | primary | datasheet | `https://www.awinic.com/en/download?file=doc/202603/d34b36c0-c0a6-4467-b148-72495c1a386a.pdf&fileName=DS_AW9967_EN_V1.8` | 2026-09-01 | **V1.8**, Mar 2025, 23 pp, 788 507 B | Pin description, `f_PWM1` 10–100 kHz, `V_REF` 200 mV, OVP 36–38 V, absolute maxima, reference application circuit | `artifacts/aw9967-datasheet-en-v1.8.pdf` |
-| D2 | AW9967DNR product page | Awinic | primary | official page | <https://www.awinic.com/en/productDetail/AW9967DNR> | 2026-09-01 | — | Category, `DFN 2X2-6L`, 20 mA/ch, 0.3 % min duty, 1.1 MHz; names the Hardware Design Guide | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `U11` wiring, `R29` = 18 Ω, `L3`/`D2`/`C24`/`C25`/`C26`, the design note in §4.3, `PYG3_BL_PWM` → M5PM1 `U7` pin 13 | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | `M5GFX/src/M5GFX.cpp` — `Light_M5PaperMono` | M5Stack | primary | repository | <https://github.com/m5stack/M5GFX> | 2026-09-01 | `master` @ `d91077b9a607b59404e4e4a49f775c792bfae382`, MIT | The register writes and the 5 kHz frequency in §4.4 and §6.2 | `scratch/m5stack-papermono/repos/M5GFX/` |
-| S3 | PaperMono / PaperMono-Lite product pages | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/PaperMono> · <https://docs.m5stack.com/en/core/PaperMono-Lite> | 2026-09-01 | — | The `PYG3_BL_PWM` vs `G3_WAKEin` documentation conflict in §4.2 | `scratch/m5stack-papermono/docs/pages/` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/aw9967-datasheet-en-v1.8.pdf` | 788 507 | `f5fa2acb88084735a932ec4e68c2d35db83f1fe474c43b20a18a320ac1d4aa5b` | 23 |
-
-**Method note.** D1 validated as `%PDF`, 23 pages, text layer intact. Retrieved with plain `curl` and a Chrome 131 User-Agent; no fallback needed and no login required. The §6.2 conflict was found by decoding the M5GFX register writes against the datasheet's electrical table, per [`hardware-device-research` §10](../../../.agents/skills/hardware-device-research/SKILL.md).
diff --git a/components/awinic/aw9967/artifacts/aw9967-datasheet-en-v1.8.pdf b/components/awinic/aw9967/artifacts/aw9967-datasheet-en-v1.8.pdf
deleted file mode 100644
index b92f3e0..0000000
Binary files a/components/awinic/aw9967/artifacts/aw9967-datasheet-en-v1.8.pdf and /dev/null differ
diff --git a/components/axs-technology/axs15231b/README.md b/components/axs-technology/axs15231b/README.md
deleted file mode 100644
index 4e31edb..0000000
--- a/components/axs-technology/axs15231b/README.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# AXS Technology AXS15231 / AXS15231B
-
-- **Category:** **combined display driver and capacitive touch controller in one die** —
-  the display side takes pixels over QSPI/SPI/MIPI; the touch side answers over I²C.
-- **Manufacturer:** **AXS Technology Corp.** — established from the datasheet's own cover page
-  and copyright notice, not inferred.
-- **Retrieved:** 2026-09-07
-
-The controller of the **LilyGO T-Display-S3 Long**'s 3.4″ 180 × 640 bar display. Integrating
-the digitiser into the display driver is unusual and is the board's defining characteristic.
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **AXS15231** (LilyGO and every driver write it **AXS15231B**) | datasheet title page |
-| Datasheet version | **V0.4**, dated **2022-11-08** | cover page, read directly |
-| Copyright notice | *"The information contained herein is the exclusive property of **AXS Technology Corp.** and shall not be distributed, reproduced, or disclosed in whole or in part without prior written permission of AXS Technology Corp."* | cover page, read directly |
-| Local artifact | [`artifacts/axs15231-datasheet-v0.4-20221108-lilygo-mirror.pdf`](artifacts/axs15231-datasheet-v0.4-20221108-lilygo-mirror.pdf) — 8 808 542 B, SHA-256 `61281aff757afeda3ae6fd75267439b8b841d5019e0190e47380be9eb613cff4` |
-| Mirror source | `Xinyuan-LilyGO/T-Display-S3-Long` → `datasheet/AXS15231_Datasheet_V0.4_20221108.pdf` @ `37a7e83af79a98bb395012200f811777e52b9cfc` |
-| Touch note | [`artifacts/axs15231b-touch-register-note-20240719-lilygo.pdf`](artifacts/axs15231b-touch-register-note-20240719-lilygo.pdf) — 63 044 B, SHA-256 `7e9d8c3fa2302fed51b60bd08c9f3ac65cdee7625db7c98cf15a8f46fcff50ef` |
-
-> ⚠ **Redistribution.** The cover page carries an explicit no-distribution notice, quoted above.
-> The copy is retained here because it is a **unique, hard-to-obtain document** — AXS Technology
-> publishes no open portal and no other copy was located — and because the research method
-> requires acquiring before judging. **Redistribution status: `prohibited` on the face of the
-> document.** It should remain **unstaged** pending a decision by the repository owner.
-> The [`components/README.md`](../../README.md) index should not link it as freely
-> redistributable.
-
-## 2. The touch interface — command-framed, not a register map
-
-LilyGO ships a two-page note, `T-Display-S3-Long_AXS15231B_Touch_Register.pdf`
-("Modified on: 2024.07.19"), whose text reads (extracted and cross-checked two ways):
-
-> "Initialize touch IIC: IIC device **`0x3B`**, touch reset, set external interrupt. …
-> Waiting for external interrupt to trigger. … Write touch commands and read touch data. …
-> Processing touch data (**take touching the fingers to count 1 and event `0x08` together as
-> the trigger flag**). …
-> Write the command to read touch information: continuously write the following formatted
-> command data to the touch IIC address `0x3B`."
-
-Three things follow, and all three catch people:
-
-1. **The I²C address is `0x3B`.**
-2. **You do not read a register — you write a formatted command block and then read a
-   response.** This is why generic touch libraries do not work with it.
-3. **A valid touch requires *both* a finger count of 1 *and* event code `0x08`.** Treating
-   either alone as a touch produces spurious events. This is stated once, in a two-page PDF,
-   in slightly awkward English, and it is the single most important line about this part.
-
-## 3. Display interface as used
-
-| Property | Value | Source |
-|---|---|---|
-| Bus | **QSPI** | `pins_config.h` @ `37a7e83` |
-| Clock | 32 MHz, mode 0, `SPI2_HOST` | same |
-| Resolution | 180 × 640 | vendor README |
-| Transfer chunk | `SEND_BUF_SIZE (28800/2)` RGB565 | `pins_config.h` |
-| Driver | `Arduino_GFX` with an AXS15231B init; the repo vendors `Arduino_GFX-1.3.7` | tree listing |
-| `TFT_eSPI` | **cannot drive it** — no QSPI transport | — |
-| ESPHome | **no model exists** for this controller as of 2026-09-07 | `esphome/components/mipi_spi/models/` |
-
-## 4. What was verified, and how
-
-The cover page **was** read, and the extraction was validated: two independent extraction
-routes (a WinAnsi/Form-XObject reader and a Type0/ToUnicode CMap reader) were run against the
-family's PDFs, and the AXS15231 cover produced consistent, legible English through the first.
-That matters because a sibling document in this pass (Chipone's CO5300) has a **uniform +0x1D
-code-point offset** that yields human-legible but wrong text — see
-[`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md).
-
-**Not read:** the register map, timing specifications, electrical characteristics, or the
-display command set. No numeric value beyond the I²C address and event code is transcribed
-into this record.
-
-## 5. Gaps
-
-- Register map and display command set not extracted.
-- Whether **AXS15231** (datasheet) and **AXS15231B** (every driver and LilyGO) are the same die
-  or a revision is **not established**.
-- The full touch command block format is described only by prose and a flowchart in the
-  two-page note; the byte-level format was not transcribed.
-- No hardware.
-
-## 6. Used by
-
-### LilyGO T-Display-S3 Long
-→ [`devices/lilygo/t-display-s3-long`](../../../devices/lilygo/t-display-s3-long/README.md)
-
-Sole display driver **and** the original touch controller. QSPI on GPIO 12 (CS), 17 (SCK),
-13/18/21/14 (D0–D3), 16 (RST); backlight GPIO1 via a PT4103B23F boost. Touch I²C on
-GPIO15 (SDA) / GPIO10 (SCL) at address `0x3B`, with `TP_RST` GPIO2 and `TP_IRQ` GPIO11.
-
-**Later production adds or substitutes a discrete
-[Hynitron CST3530](../../hynitron/cst3530/README.md)** — the repository's default branch is
-`T-Display-S3-Long-cst3530` and two factory images ship. See
-[R5](../../../devices/lilygo/t-display-s3-shared/board-revision-drift.md#r5--t-display-s3-long-cst3530-touch-appears-mid-life-in-a-branch).
diff --git a/components/axs-technology/axs15231b/artifacts/axs15231-datasheet-v0.4-20221108-lilygo-mirror.pdf b/components/axs-technology/axs15231b/artifacts/axs15231-datasheet-v0.4-20221108-lilygo-mirror.pdf
deleted file mode 100644
index 5cf132b..0000000
Binary files a/components/axs-technology/axs15231b/artifacts/axs15231-datasheet-v0.4-20221108-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/axs-technology/axs15231b/artifacts/axs15231b-touch-register-note-20240719-lilygo.pdf b/components/axs-technology/axs15231b/artifacts/axs15231b-touch-register-note-20240719-lilygo.pdf
deleted file mode 100644
index 9ae0a49..0000000
Binary files a/components/axs-technology/axs15231b/artifacts/axs15231b-touch-register-note-20240719-lilygo.pdf and /dev/null differ
diff --git a/components/belling/bl8075/README.md b/components/belling/bl8075/README.md
deleted file mode 100644
index d4ad3bd..0000000
--- a/components/belling/bl8075/README.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# Belling BL8075 (BL8075CB5TR33) — 3.3 V LDO regulator
-
-- **Category:** low-dropout linear regulator, fixed output, with enable.
-- **Manufacturer:** **Shanghai Belling Co., Ltd** (上海贝岭) — inferred from the `BL8xxx`
-  part-number family. **No datasheet located**; attribution is `inferred`.
-- **Research status:** ⚠ **Schematic-only.**
-- **Retrieved:** 2026-09-04
-
-The 3.3 V rail of the M5Stack DinMeter carrier board.
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part string | **`BL8075CB5TR33`** | DinMeter schematic, value text at (606, 308.6), associated with `U4` |
-| Suffix reading | `…33` → **3.3 V fixed output**; `B5` → 5-pin package; `TR` → tape-and-reel | conventional Chinese-vendor suffix grammar — `inferred`, not read from a datasheet |
-| Pins | **5**: `VIN`, `VOUT`, `GND`, `EN`, `NC` | DinMeter schematic `U4`, `PIU401`–`PIU405` |
-| Input on this board | `VBAT_IN` | schematic |
-| Output on this board | `+3.3V` | schematic |
-| Capacitors | `C30` 22 µF, `C31` 100 nF, `C32` 100 nF, `C33` 22 µF | schematic |
-
-Current rating, dropout, quiescent current, PSRR, `EN` threshold and thermal behaviour are all
-**unknown**. No chip-marking confirmation.
-
-## 2. Artifacts
-
-**None.** Establishing evidence:
-[`devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf`](../../../devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf).
-
----
-
-## Used By
-
-### M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-`U4`. Produces the carrier's `+3.3V`, which supplies the [BM8563 RTC](../../generic/bm8563/README.md)
-(`U5`), the PORT.A I²C pull-ups `R2`/`R3`, the encoder pull-ups `R1`, and the LCD FPC `FPC1`.
-Note it is fed from `VBAT_IN`, i.e. the battery/charger node, not from `+5VIN` — which is why
-the RTC keeps time while the board is latched off.
-
-→ [`devices/m5stack/dinmeter/pinouts-and-buses.md` §4](../../../devices/m5stack/dinmeter/pinouts-and-buses.md#4-power-tree-and-the-latch)
-
----
-
-## Datasheet — **not obtained**, 2026-09-11
-
-The record above states *"No datasheet located; attribution is `inferred`."*
-**Still true.** What was tried this pass:
-
-| Source tried | Result |
-|---|---|
-| `http://www.szbelling.com/` | **connection failure (HTTP 000)** — no response |
-| GitHub code search, `BL8075` | no datasheet artefacts |
-| LCSC JSON API | **403 on every UA** |
-| DuckDuckGo HTML | **202 bot-check** |
-
-**The attribution to Belling (上海贝岭 / Shanghai Belling) remains `inferred` from
-the part-number family and the conventional suffix grammar.** Nothing in this
-pass raised or lowered that confidence.
-
-### What would settle it
-
-1. **Read the top marking off a board photograph.** This is now newly possible:
-   the **FCC internal photographs of the X3 and X4 are public and retained** in
-   this repository —
-   [`devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf`](../../../devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf)
-   (16 images) and
-   [`devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf`](../../../devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf)
-   (15 images). **They have not been read at marking level by this pass.** That
-   is the cheapest next step for this record and for every part in
-   [`components/unidentified/xteink-x3-x4/`](../../unidentified/xteink-x3-x4/README.md).
-2. Chinese search: `BL8075 规格书`, `上海贝岭 BL8075`.
-3. LCSC HTML storefront with UA `WhatsApp/2.23.20.0`.
-
-**Do not promote the Belling attribution to a finding until a marking is read.**
-A part number differing by one character from a real part on a different board is
-a documented trap in this repository's own conventions.
diff --git a/components/bosch-sensortec/bhi260ap/README.md b/components/bosch-sensortec/bhi260ap/README.md
deleted file mode 100644
index 2e437fd..0000000
--- a/components/bosch-sensortec/bhi260ap/README.md
+++ /dev/null
@@ -1,80 +0,0 @@
-# Bosch Sensortec BHI260AP
-
-- **Category:** smart sensor hub — a 6-axis IMU (3-axis accel + 3-axis gyro) with an integrated
-  programmable **Fuser2** 32-bit microcontroller running Bosch's sensor-fusion firmware.
-  I²C/SPI host interface.
-- **Manufacturer:** Bosch Sensortec GmbH.
-- **Retrieved:** 2026-09-07
-- **Siblings here:** [`bmi270`](../bmi270/README.md) · [`bma423`](../bma423/) *(artifacts only; no record yet)*
-
-Fitted to **some** LilyGO **T-Display-S3 Pro** boards. Which IMU any given Pro carries is
-**not determined by the product name** — see §2.
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **BHI260AP** | `schematic/T-BHI260.pdf` and `T-BHI260_V1.1.pdf` in `Xinyuan-LilyGO/T-Display-S3-Pro` @ `08b8b2bbcb8b263131af119476403080cd30224f` |
-| KiCad footprint | `schematic/kicad_sensor.pretty/T-BHI260.kicad_mod` (4 541 B) | same |
-| Firmware naming it | `firmware/v1.1/UnitTest_V1.1_DisChg_BHI260_241111.bin` | same |
-| Datasheet | **not retrieved.** Bosch publishes BHI260AP openly at `bosch-sensortec.com`; acquisition is straightforward and simply was not done | — |
-| Local artifact | **none** | — |
-
-**What distinguishes a BHI260AP from an ordinary IMU** is that it is a *sensor hub*: the
-on-chip Fuser2 core runs downloadable firmware that performs orientation fusion, step counting,
-activity recognition and gesture detection **without waking the host**. That is why it appears
-on a handheld board — it is the part that lets the ESP32-S3 sleep.
-
-The corollary is that a BHI260AP is useless without its firmware image. Bosch's
-`BHY2-Sensor-API` and a `.fw` blob must be flashed to it (from host RAM or an external EEPROM)
-at every boot or from a dedicated flash. Anyone expecting a BMI270-style register interface will
-be surprised.
-
-## 2. Which IMU is on your Pro?
-
-The repository ships schematics and footprints for **two** sensors:
-
-| Document | Part |
-|---|---|
-| `T-BHI260.pdf`, `T-BHI260_V1.1.pdf`, `T-BHI260.kicad_mod` | **BHI260AP** |
-| `T-ICM29048.pdf`, `T-CIM29048.kicad_mod` | an **ICM-20948**-class TDK part (LilyGO spells it `ICM29048` / `CIM29048`) |
-
-Two schematics, two footprints, one product name. **Scan I²C to find out what you have.**
-Recorded as [board-revision-drift R7](../../../devices/lilygo/t-display-s3-shared/board-revision-drift.md#r7--t-display-s3-pro-two-different-imu-daughter-boards).
-
-Note also that the sensor appears to sit on a **daughter-board or module** (the schematics are
-separate sheets named `T-BHI260`, `T-ICM29048`, with their own footprints) rather than on the
-mainboard — which is how a single product can ship either.
-
-## 3. Board integration
-
-`BOARD_SENSOR_IRQ` is **GPIO21** (`examples/factory/utilities.h` @ `08b8b2b`). The sensor shares
-the board's single I²C bus — SDA **GPIO5**, SCL **GPIO6** — with the
-[CST226SE touch](../../hynitron/cst226se/README.md) at `0x5A`, the
-[SY6970 PMIC](../../silergy/sy6970/README.md) at `0x6A`, the
-[LTR-553ALS](../../lite-on/ltr-553als-01/README.md) at `0x23` and the camera. The file's own
-comment says so: `// LTR553 , TOUCH , SY6970 , Camera share I2C Bus`.
-
-**The BHI260AP's I²C address is not stated by LilyGO** and is not recorded here.
-
-## 4. Software
-
-`lewisxhe/SensorLib` — the same author's library that covers the CST touch parts — is what
-LilyGO uses across its boards. Bosch's own `BHY2-Sensor-API` is the reference implementation.
-
-## 5. Gaps
-
-- Datasheet not retrieved; no register, address or electrical value here.
-- **Which board revisions carry which sensor is unknown.**
-- The ICM-209xx alternative has no record in this repository.
-- Whether the sensor is on the mainboard or a module is inferred from the schematic file
-  structure, not confirmed.
-- Not verified on hardware.
-
-## 6. Used by
-
-### LilyGO T-Display-S3 Pro (some units)
-→ [`devices/lilygo/t-display-s3-pro`](../../../devices/lilygo/t-display-s3-pro/README.md)
-
-Interrupt GPIO21; I²C shared with touch, PMIC, ambient-light sensor and camera on GPIO5/6.
-**Presence is not guaranteed by the product name.**
diff --git a/components/bosch-sensortec/bmi270/README.md b/components/bosch-sensortec/bmi270/README.md
index e9aad0e..0f2006c 100644
--- a/components/bosch-sensortec/bmi270/README.md
+++ b/components/bosch-sensortec/bmi270/README.md
@@ -392,132 +392,6 @@ If your application is "which way up is the device", **an accelerometer-only par
 | Device | Ref | Role |
 |---|---|---|
 | [Nicolai Electronics Tanmatsu](../../../devices/nicolai-electronics/tanmatsu/README.md) | `U33` | Device orientation, at I²C **0x68** on the internal bus (`BSP_BMI270_I2C_ADDRESS`). Used by `badge_bsp_orientation.c` to auto-rotate the 800×480 display between landscape and portrait. **Polled — neither interrupt pin is routed to a processor (§6.1).** See [`bom.md`](../../../devices/nicolai-electronics/tanmatsu/bom.md), [`pinouts-and-buses.md`](../../../devices/nicolai-electronics/tanmatsu/pinouts-and-buses.md) §1.1 |
-| [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md) | `U15` | Orientation **and low-power wake source**. I²C **0x68** (alternate **0x69** also probed), on the shared system bus at **100 kHz**. `INT1` **is** routed — to the M5PM1 coprocessor, not to the application CPU. See §12 |
-
-### M5Stack PaperMono (SKU C153)
-
-*Added 2026-09-01.* Fitted as **`U15`** on schematic sheet 4 of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) and its Lite sibling. Evidence: the published schematic PDF, M5Stack's source, M5Stack's documentation, and strings recovered from the shipped factory firmware image. **No hardware was available.**
-
-This board is the useful counterexample to the Tanmatsu: it does exactly what §6.1 says the Tanmatsu cannot.
-
-#### 12.1 Addressing and bus
-
-| Property | Value | Evidence |
-|---|---|---|
-| Primary I²C address | **`0x68`** | `app_sleep_wake.cpp:59`; `M5GFX.cpp:1937`; M5Stack PinMap |
-| **Alternate address probed** | **`0x69`** | `app_sleep_wake.cpp:60` — the firmware tries both, so `SDO` strapping is not assumed |
-| Bus | Shared system I²C, ESP32-S3 **GPIO47 SDA / GPIO48 SCL**, pull-ups `R36`/`R37` = 2.2 kΩ to `3V3_L2` | schematic sheet 3 |
-| **Bus speed for this device** | **100 kHz** — `BMI270_I2C_FREQ_HZ = 100000` | `app_sleep_wake.cpp:58` |
-| Bus speed for its neighbours | **400 kHz** for the RX8130CE RTC and the ST25R3916 NFC reader | `hal_board.cpp:19`, `:21` |
-| Series resistors | `R43`, `R44` = 22 Ω on `SCx`/`INT1`; `R42` = 10 Ω | schematic sheet 4 |
-
-> ⚠ **The BMI270 is clocked at a quarter the speed of its bus neighbours.** That is a per-transaction choice, legal on a shared bus, and it matters because of §4: **the 8 KB configuration upload happens at whatever rate the master uses.** At 100 kHz that upload is roughly **800 ms**, not the ~200 ms §4 quotes for 400 kHz. On this board the config upload is a substantial chunk of boot time and belongs firmly in a background task.
->
-> Why 100 kHz was chosen is not documented. It is the same rate M5Stack uses for its two coprocessors (`hal_board.cpp:15`), so it may simply be a house default rather than a BMI270-specific decision. `inferred`.
-
-Address neighbours on the same bus — no conflict: FT6336G `0x38`, RX8130CE `0x32`, M5IOE1 `0x4F`, ST25R3916 `0x50`, M5PM1 `0x6E`, IP2315 `0x75` (gated off the bus).
-
-#### 12.2 Wiring **[schematic sheet 4, `U15`]**
-
-| Pin | Name | Net | Note |
-|---:|---|---|---|
-| 1 | `SDO` | local network with `R50` = 10 kΩ | strapping resistor; the firmware probes both `0x68` and `0x69` regardless |
-| 2 | `ASDX` | *unconnected* | no auxiliary magnetometer |
-| 3 | `ASCX` | *unconnected* | |
-| **4** | **`INT1`** | **`PYG4_IMU_INT`** → **M5PM1 `U7` pin 12** | ⚠ §12.3 |
-| 5 | `VDDIO` | `3V3_L1` | |
-| 6, 7 | `GNDIO`, `GND` | `GND` | |
-| 8 | `VDD` | **`3V3_L1`** | ⚠ §12.4 |
-| **9** | **`INT2`** | *unconnected* | as on the Tanmatsu |
-| 10 | `OCSB` | *unconnected* | OIS unused |
-| 11 | `OSDO` | *unconnected* | |
-| 12 | `CSB` | pull-up network | ⇒ I²C mode |
-| 13 | `SCX` (SCL) | `G48_SYS_SCL` via `R44` = 22 Ω | |
-| 14 | `SDX` (SDA) | `G47_SYS_SDA` | |
-| — | decoupling | `C58` = 10 µF/10 V, `C59` = 10 µF/10 V, `C61`–`C64` = 1 µF/25 V and 100 nF/25 V | |
-
-#### 12.3 ⚠ `INT1` is a wake source — and it goes to the coprocessor, not the CPU
-
-`INT1` reaches **M5PM1 GPIO4**, whose schematic pin name is `G4_WAKEin(INT3/4)_IRQout_PWM`. The sheet annotates that pin `唤醒源二选一` — *"choose one of two wake sources"*, shared with the M5PM1's `G3`. **[SCH]**
-
-**Configuration, from M5Stack's own published sketch:**
-
-```cpp
-pm1.gpioSetWakeEnable(M5PM1_GPIO_NUM_4, true);
-pm1.gpioSetWakeEdge(M5PM1_GPIO_NUM_4, M5PM1_GPIO_WAKE_FALLING);   // falling edge
-...
-intPinConfig.pin_type             = BMI2_INT1;
-intPinConfig.int_latch            = BMI2_INT_NON_LATCH;
-intPinConfig.pin_cfg[0].lvl       = BMI2_INT_ACTIVE_LOW;
-intPinConfig.pin_cfg[0].od        = BMI2_INT_PUSH_PULL;
-intPinConfig.pin_cfg[0].output_en = BMI2_INT_OUTPUT_ENABLE;
-imu.setInterruptPinConfig(intPinConfig);
-imu.mapInterruptToPin(BMI2_ANY_MOTION_INT, BMI2_INT1);
-```
-
-So: **`ANY_MOTION` → `INT1`, active-low, push-pull, non-latched → M5PM1 GPIO4, falling edge.** The interrupt registers written are `INT1_IO_CTRL` (`0x53`) and `INT1_MAP_FEAT` (`0x56`) per §5.
-
-**Third-party confirmation from the shipped binary** (`strings`, `executed-success`):
-
-```
-I (%lu) %s: PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge
-I (%lu) %s: Configure BMI270 any-motion wake addr=0x%02X
-```
-
-> ⚠ **A documentation conflict, resolved.** M5Stack's power-management page says in prose that *"Rotating the device then triggers the **active-high** IMU interrupt to wake the M5PM1."* The code on the same page says `BMI2_INT_ACTIVE_LOW` and `M5PM1_GPIO_WAKE_FALLING`, the narrative later on that page says *"maps the interrupt to **active-low** INT1"*, and the shipped firmware string says *falling edge*. **The prose is the sole outlier and is wrong: it is active-low, falling edge.**
-
-**Why this matters architecturally.** The ESP32-S3 is not in this path at all. The sequence is: system shut down → `3V3_L1` held up by `pm1.ldoSetPowerHold(true)` → BMI270 stays alive and scanning for motion → `INT1` falls → M5PM1 wakes → M5PM1 restores the rails and boots the ESP32-S3. **The IMU can wake a fully powered-down device.** That is exactly the feature-engine capability that §6.1 records as unavailable on the Tanmatsu, and it is the reason the 8 KB config upload earns its keep here.
-
-The M5PM1 can also be left awake and used as an interrupt *router*, re-emitting the event on its `G1` (`G1_PY_IRQ`) to ESP32-S3 **GPIO1**, which is then usable as an `ext0` deep-sleep wake source. Both patterns are documented by M5Stack.
-
-#### 12.4 `3V3_L1` exists for this chip
-
-`VDD` and `VDDIO` are both on **`3V3_L1`**, a rail produced by its own [SSP7615-33DFR](../../generic/ssp7615-33dfr/README.md) LDO (`U6`) from `VBUS_L0`, enabled by the M5PM1's `LDO3V3_EN_PP` and exposed as `pm1.setLdoEnable(bool)` / `pm1.ldoSetPowerHold(bool)`.
-
-**The BMI270 is the only load on that rail.** M5Stack's power-tree table lists `L1` as powering the IMU and nothing else. The whole point of having a separate `L1` level is to keep this one chip alive while everything else — including the ESP32-S3 — is off (§12.3). That is a real design decision worth naming: **a dedicated regulator exists on this board solely so that a 3.5 µA suspend-mode IMU can act as a wake source.**
-
-Per §3, the relevant current in that state is **~4 µA accel-only low-power mode** or **3.5 µA suspend**, plus the LDO's 0.5 µA quiescent — a few microamps total against a 1150 mAh pack.
-
-#### 12.5 Driver
-
-The vendor **does not** use Bosch's `BMI270-Sensor-API` directly. M5Stack's published example uses **SparkFun's** `SparkFun_BMI270_Arduino_Library`, and the UserDemo pins **`arduino-libraries/Arduino_BMI270_BMM150` at tag `1.2.3`, commit `a599119044554015e06735f9d7187fc56295b9b6`**, with a local patch applied by its `fetch_repos.py`.
-
-Both wrap the Bosch API, so the §4 initialisation sequence — including the mandatory 8 KB upload and the `INTERNAL_STATUS` check — is handled correctly. The §8 rule still applies if you swap in something else: **grep for `0x59`, `0x5E` or an 8 KB array.**
-
-Commented-out tuning constants in M5Stack's own sketch, worth recording because they are the only published values for this board: `any_motion.threshold` — 1 LSB = 0.48 mg, default 83 mg; `any_motion.duration` — 1 LSB = 20 ms, default 100 ms.
-
-#### 12.6 Open questions specific to this board
-
-- Why 100 kHz (§12.1), and whether the ~800 ms config upload is on the boot critical path.
-- What `R50` (10 kΩ) on `SDO` actually strapped to; the firmware's dual-address probe means nobody has had to know.
-- Whether the M5PM1's `G3`/`G4` *"choose one of two wake sources"* annotation implies the frontlight PWM and the IMU interrupt are mutually exclusive. `G3` is `PYG3_BL_PWM`, the [AW9967](../../awinic/aw9967/README.md) frontlight dimming input — if the two genuinely share one wake block, then **arming IMU wake may preclude frontlight PWM, or vice versa**. This is unresolved and would be a significant constraint if true.
-- No hardware measurement of wake latency or standby current.
-
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-Designator **U7** on schematic sheet 3. I²C **`0x69`** — the schematic prints
-**"7-bit Address 69H"** beside the symbol, and R43 (3.3 kΩ) pulls `SDO` high to select it.
-`SDX` (pin 14) ← G8, `SCX` (pin 13) ← G9, on the internal bus shared with the TCA8418 (`0x34`)
-and the ES8311 (`0x18`). Decoupling C25 10 µF/10 V, C27 100 nF, ferrite FB7 120 Ω.
-
-⚠ **`INT1` (pin 4) and `INT2` (pin 9) were not resolved to any GPIO**, no vendor document
-mentions a BMI270 interrupt on this board, and M5Unified polls. Recorded as *not established*
-rather than *absent* — the difference matters, because a routed interrupt would make IMU
-motion-wake from deep sleep possible.
-
-The auxiliary interface (`ASDX`/`ASCX`/`OSDO`/`OCSB`) is present on the symbol with **no
-magnetometer fitted** — contrast the CardputerZero below.
-
-The **Cardputer v1.0 and v1.1 have no IMU at all**; this is one of the ADV's headline additions.
-
-### M5Stack CardputerZero (C154 / C155) — [`devices/m5stack/cardputer-zero`](../../../devices/m5stack/cardputer-zero/README.md)
-
-Same part at **`0x68`** (not `0x69` — `SDO` strapped the other way), on the CM0's `I2C1`
-(`G2`/`G3`), and here it **does** carry a **BMM150 magnetometer at `0x10` on its auxiliary
-interface**. Vendor page marked *work in progress*.
-
-*Both added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.3.*
 
 ## Related pages
 
@@ -534,40 +408,5 @@ interface**. Vendor page marked *work in progress*.
 | D3 | BMI270-Sensor-API | Bosch Sensortec | primary | repository | <https://github.com/BoschSensortec/BMI270-Sensor-API> | 2026-08-30 | BSD-3-Clause; commit not pinned | **The `bmi270_config_file[]` blob**, cited normatively by D1 footnote 3 | not vendored |
 | S1 | `badge_bsp_orientation.c` (212 lines) | Nicolai Electronics / Badge.Team | primary | repository | in-tree snapshot | 2026-08-30 | MIT, SPDX 2025 | All §7 findings; ODR/range choices; polling model | `devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/badge-bsp/tanmatsu/badge_bsp_orientation.c` |
 | S2 | `tanmatsu.kicad_pcb` | Nicolai Electronics | primary | repository | in-tree snapshot | 2026-08-24 | `tanmatsu-hardware` @ `640805dd`, CERN-OHL-P | Every net in §6, including the unrouted interrupts and `R86`/`TP22` | `devices/nicolai-electronics/tanmatsu/artifacts/schematics/kicad/` |
-| **D4** | **BMI270 Datasheet — M5Stack mirror** | Bosch Sensortec, mirrored by M5Stack | **credible mirror** | datasheet | <https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/app/Stamp%20Fly/BMI270.PDF> | **2026-09-01** | **revision 1.3, Nov 2020, BST-BMI270-DS000-05, 162 pp, 3 830 973 B** | The revision M5Stack ships to PaperMono users — see [Mirror lag](#mirror-lag-m5stack-serves-a-five-year-old-revision--added-2026-09-01) | `artifacts/bst-bmi270-ds000-05-rev1.3-m5stack-mirror.pdf` |
-| S3 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 2026-05-22, 6 sheets | The §12.2 pin/net table, `INT1` → M5PM1 GPIO4, `3V3_L1` supply, `R42`/`R43`/`R44`/`R50` | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S4 | `M5PaperMono-UserDemo` — `app_sleep_wake.cpp`, `hal_board.cpp`, `repos.json` | M5Stack | primary | repository | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | `main` @ `c1099107271d31a0678d661a896e2b04dbb331ea`, MIT | `0x68`/`0x69` dual probe, `BMI270_I2C_FREQ_HZ = 100000`, the pinned `Arduino_BMI270_BMM150` commit | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-| S5 | PaperMono M5PM1 & M5IOE1 power-management page | M5Stack | primary | official page | <https://docs.m5stack.com/en/arduino/papermono/m5pm1_m5ioe1> | 2026-09-01 | — | The verbatim wake sketch in §12.3, the SparkFun driver reference, the L0–L3B table placing the IMU alone on `L1`, and the active-high/active-low prose conflict | `scratch/m5stack-papermono/docs/pages/en-arduino-papermono-m5pm1_m5ioe1.html` |
-| S6 | `C153-PaperMono-UserDemo-v1.2.bin` — recovered strings | M5Stack | primary | firmware | M5Burner API, firmware id `2089640807996628993` | 2026-09-01 | v1.2, 2 868 208 B, SHA-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | `PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge`, settling the polarity conflict | `scratch/m5stack-papermono/docs/firmware/` |
-
-### Local artifacts
-
-| File | Bytes | SHA-256 | Pages | Document number | Revision | Release date |
-|---|---:|---|---:|---|---|---|
-| `artifacts/bst-bmi270-ds000.pdf` | 2 636 042 | `f68ce3c74f011a80bbe4b0279c4abe9609a71a5dcda75a951381d77112e005fb` | **150** | **BST-BMI270-DS000-08** | **1.6** | **March 2026** |
-| `artifacts/bst-bmi270-ds000-05-rev1.3-m5stack-mirror.pdf` | 3 830 973 | `3ab915ed1d81d0eaa5ff1d1aed62b2b491260c9d59afbf79bb23fb477e015612` | **162** | **BST-BMI270-DS000-05** | **1.3** | **Nov 2020** |
-
-### Mirror lag: M5Stack serves a five-year-old revision — *added 2026-09-01*
-
-Both files above are genuine Bosch documents. They are **five years and four months apart** — three document revisions (1.3 → 1.6) and three document numbers (`-05` → `-08`).
-
-| | Repository's Bosch copy | M5Stack's mirror |
-|---|---|---|
-| Document number | **BST-BMI270-DS000-08** | **BST-BMI270-DS000-05** |
-| **Document revision** | **1.6** | **1.3** |
-| **Release date** | **March 2026** | **November 2020** |
-| Pages | 150 | **162** |
-| Bytes | 2 636 042 | 3 830 973 |
-| Source | `bosch-sensortec.com` direct | `m5stack.oss-cn-shenzhen.aliyuncs.com` |
-
-**This is a finding, not an inconvenience.** Three things follow from it:
-
-1. **Revision 1.3 is the document the PaperMono was designed and written against.** It is linked from the product page, it is what M5Stack's engineers had, and when the board's behaviour or M5Stack's firmware disagrees with revision 1.6, **check 1.3 before assuming a bug.** Register descriptions, reset defaults, timing minima and errata wording all change between Bosch revisions.
-2. **The older document is 12 pages *longer*.** Bosch has removed material as well as added it across those three revisions. A reader who only holds 1.6 has lost whatever those pages contained. This is why the mirror is retained rather than deduplicated away — "it's an old revision" is not a reason to discard it, it is the reason to keep it.
-3. **Note where M5Stack hosts it.** The PaperMono product page links the BMI270 datasheet out of the **Stamp Fly** product's asset folder (`/resource/docs/products/app/Stamp Fly/BMI270.PDF`), not from a PaperMono folder. The document is a shared asset across M5Stack products, which is exactly the mechanism by which a mirror goes stale: nobody refreshes it when a new board ships, because it does not belong to that board.
-
-**Which to read.** For what the silicon does, **revision 1.6** is authoritative and is the default reference for everything in §§1–11 above. Use revision 1.3 when you are trying to understand M5Stack's design or firmware choices.
-
-Both files were validated as `%PDF`, retrieved with plain `curl` and a Chrome 131 User-Agent, and their revisions read from page 1 of each. The mirror's byte size and hash were re-verified against the live URL on 2026-09-01.
 
 **Method note.** D1 was fetched with `curl` and a Chrome 131 User-Agent and validated as `%PDF` (150 pages). Bosch Sensortec serves datasheets to automated clients without difficulty; no User-Agent fallback was required. The §6 pin table was produced by parsing pad→net assignments out of `tanmatsu.kicad_pcb` directly rather than reading the schematic graphically, so it reflects the manufactured netlist.
diff --git a/components/bosch-sensortec/bmi270/artifacts/bst-bmi270-ds000-05-rev1.3-m5stack-mirror.pdf b/components/bosch-sensortec/bmi270/artifacts/bst-bmi270-ds000-05-rev1.3-m5stack-mirror.pdf
deleted file mode 100644
index 1d89f18..0000000
Binary files a/components/bosch-sensortec/bmi270/artifacts/bst-bmi270-ds000-05-rev1.3-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/canaan/k230/README.md b/components/canaan/k230/README.md
deleted file mode 100644
index 6051c2a..0000000
--- a/components/canaan/k230/README.md
+++ /dev/null
@@ -1,413 +0,0 @@
-# Canaan Kendryte K230
-
-- **Category:** dual-core 64-bit **RISC-V** AIoT application SoC with a KPU/NPU, 3D DPU, 2.5D GPU, H.264/H.265 VPU, ISP and MIPI DSI/CSI — **no radio, no Ethernet MAC, no on-die flash**
-- **Manufacturer:** Canaan Creative Co., Ltd (嘉楠科技, NASDAQ: **CAN**), Kendryte® product line
-- **Research status:** written from Canaan's own datasheet and brief datasheet (Markdown sources in the official `kendryte/k230_docs` repository, pinned commit) plus vendor BSP source. **No K230 hardware was executed or measured in this pass.**
-- **Retrieved:** 2026-09-04
-- **First RISC-V part in this repository.** Nothing in the repo's ESP-IDF/Xtensa toolchain guidance applies to it — see [§14](#14-software-toolchain-and-os-support).
-
----
-
-## 1. Identity, family and variants
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | **Kendryte K230** | C1, C2 |
-| Vendor | Canaan Creative (Kendryte brand) | C1 |
-| Announced / datasheet V1.0 | **2023-07-06** (document revision date) | C1 |
-| CPU cores | **two** XuanTie **C908** RISC-V 64-bit cores | C1, C2 |
-| Package — K230 | **BGA, 0.65 mm pitch, 13 × 13 mm**, single die, external DRAM | C2 |
-| Package — K230D | **BGA, 0.65 mm pitch, 11 × 11 mm**, SiP with **128 MB (1 Gb) 16-bit LPDDR4 @ 3200 Mbps** in package | C1, C2 |
-| Max external DRAM | **2 GB** | C1, C2 |
-| On-die SRAM | **2 MB shared + 2 MB KPU-default** | C1 |
-| Embedded flash | **none** — boots from SD/eMMC or SPI NOR/NAND | C1 |
-| Radio | **none** | C1 (no RF block in the feature list or block diagram) |
-| Ethernet MAC | **none** | C1, C2 (negative result — see [§7](#7-what-the-k230-does-not-have)) |
-| Operating temperature | **−40 … +85 °C** | C1, C2 |
-| Deep-sleep standby | **≤ 20 µW** (vendor figure) | C2 |
-
-### Naming and lineage
-
-`K230` sits in Canaan's Kendryte AIoT line: **K210** (2018, dual RV64GC @ 400 MHz, 0.23 TOPS-class KPU, 8 MB on-die SRAM, no DDR) → **K510** (2021, *tri*-core RISC-V, up to 3 TOPS, C4) → **K230** (2023, dual C908, RVV 1.0). K230 is the successor to K210 in positioning and to K510 in capability; it is **not** a K510 derivative and shares no software with K210 beyond the "CanMV" MicroPython branding.
-
-**Variant trap.** `K230` and `K230D` are different *packages of the same die*, distinguished only by whether an LPDDR4 die is co-packaged. A `K230D` board is memory-capped at **128 MB**; a `K230` board can carry up to 2 GB externally. Do not read a "K230" board specification as implying the D part or vice versa — the GPIO count also differs (**64 GPIO + 8 PMU GPIO** on K230 versus **50 GPIO + 6 PMU GPIO** in SiP form, C2).
-
-`K256` appears in LilyGO's SKU strings for K230 boards (`K256`, `K256-A`, `K256-03`). **`K256` is a LilyGO stock code, not a Canaan part number** — see the [device record](../../../devices/lilygo/t-display-k230/README.md#1-identity-skus-and-variants).
-
----
-
-## 2. The two C908 cores — which one has the vector unit
-
-This is the single most misquoted fact about the part, so it is stated exactly as Canaan states it.
-
-| | **CPU 1** ("big core") | **CPU 0** ("little/small core") |
-|---|---|---|
-| Max frequency | **1.6 GHz** | **800 MHz** |
-| ISA | RV64 with **RISC-V Vector Extension **v1.0** | **RV64GCB** (G + Compressed + **B**itmanip) |
-| Vector unit | **Yes — 128-bit VPU** | **No** |
-| FPU | Yes | Yes |
-| L1 | 32 KB I + 32 KB D | 32 KB I + 32 KB D |
-| L2 | **256 KB** | **128 KB** |
-| MMU | Yes | Yes |
-| PLIC | own, 208 external sources | own, 208 external sources |
-| JTAG | Yes | Yes |
-| Canaan's intended OS | **RTOS** (RT-Thread / RT-Smart) | **Linux** | 
-
-Evidence: C1 §"CPU subsystem", C2 §"CPU".
-
-> **Only CPU1 has RVV 1.0.** Vector-optimised libraries (OpenBLAS RVV kernels, nncase runtime paths, the `-mcpu=c908v` build target) are meaningful only on CPU1. Code compiled with vector instructions will trap on CPU0.
-
-### This is *not* a big.LITTLE cluster, and there is no third core
-
-Two structural points that catch people coming from Arm SoCs or from the ESP32-P4:
-
-1. **The two cores are separate subsystems, not a coherent cluster.** Each has its own L2 and its own PLIC with its own 208 interrupt sources. Canaan's own SDK runs *two different operating systems* simultaneously — RT-Smart on CPU1, Linux on CPU0 — with an explicit inter-processor communication API (`K230_Inter_Processer_Communication_API_Reference`) and a `sharefs` mechanism to share a filesystem between them. You do not schedule a Linux thread onto CPU1.
-2. **There is no third CPU.** The datasheet's feature list contains exactly two CPU subsystems (C1). The **PMU** is a hardware block — 32 kHz RTC, 6 inputs / 2 outputs, long/short-press detection, edge/level detection with debounce, 512 bits of shutdown log — **not a programmable core** (C1 §PMU, C2 §PMU). Where the K230 is described as having "two cores plus a small core", the "small core" being referred to is **CPU0 itself**, which Canaan and its SDK call the *small core* (小核) in contrast to CPU1, the *big core* (大核). This is a naming collision, not a third processor.
-
-   Contrast with **[ESP32-P4](../../espressif/esp32-p4/README.md)**, which genuinely does have a third, separate low-power RISC-V core (single-core, 40 MHz, retained LP power domain, LP peripherals and an LP mailbox). K230 has no equivalent: there is no retained programmable core, and the only always-on logic is the PMU's fixed-function RTC and key-detect state machine.
-
-### Which core runs Linux — a live source conflict
-
-| Source | Claim |
-|---|---|
-| Canaan brief datasheet (C2) | "CPU 1 … **runs RTOS** system"; "CPU 0 … **runs LINUX** system" |
-| LilyGO wiki, T-Display K230 Quick Start FAQ, retrieved 2026-09-04 (D5) | "**big core runs Linux, little core runs RT-Thread** or bare-metal" |
-
-Canaan's document is primary and its statement matches the SDK's own configuration names. **Treat the LilyGO wiki FAQ as wrong.** Recorded as conflict `GC-1` in the device record's [gaps-and-conflicts.md](../../../devices/lilygo/t-display-k230/gaps-and-conflicts.md). A third arrangement exists too: `kendryte/k230_linux_sdk` builds a **Linux-only** image, which is what the LilyGO T-Display K230 BSP is built from.
-
----
-
-## 3. KPU / NPU — capability and supported operators
-
-| Item | Value | Evidence |
-|---|---|---|
-| Precision | **INT8 and INT16** | C1, C2 |
-| Weight sparsity | supported ("weight sparse compression") | C1, C2 |
-| ResNet-50 | **≥ 85 fps @ INT8** | C1, C2 |
-| MobileNet v2 | **≥ 670 fps @ INT8** | C1, C2 |
-| YOLOv5s | **≥ 38 fps @ INT8** | C1, C2 |
-| Frameworks | TensorFlow, PyTorch, TFLite, PaddlePaddle, ONNX (C1); C2 lists TVM instead of TFLite/Paddle | C1, C2 |
-| Quantisation loss | **< 1 %** (vendor claim) | C1, C2 |
-| Dedicated SRAM | 2 MB (the second 2 MB block defaults to KPU) | C1 |
-
-### The TOPS number is a marketing figure, not a datasheet figure
-
-**Neither the K230 full datasheet nor the brief datasheet states a TOPS rating.** They state the three network throughputs above and nothing else. The commonly repeated numbers come from downstream sources and they disagree:
-
-- LilyGO's own wiki: "**up to 1.6 TOPS NPU**" (D5).
-- A Reddit commenter, 2025-07-08: "the k230 has abt **17 tops**" — unsupported assertion, contradicted by every vendor figure; recorded here only because it circulates.
-
-Use the fps figures. They are the ones Canaan is prepared to write down, and they are workload-defined.
-
-### Supported ONNX operators (verbatim from C1)
-
-Abs, Acos, Acosh, And, ArgMax, ArgMin, Asin, Asinh, Add, AveragePool, BatchNormalization, Cast, Ceil, Celu, Clip, Concat, Constant, ConstantOfShape, Conv, ConvTranspose, Cos, Cosh, CumSum, DepthToSpace, DequantizeLinear, Div, Dropout, Elu, Equal, Exp, Erf, Expand, Flatten, Floor, Gather, GatherElements, GatherND, Gemm, GlobalAveragePool, GlobalMaxPool, Greater, GreaterOrEqual, Hardmax, HardSigmoid, HardSwish, Identity, InstanceNormalization, LpNormalization, LeakyRelu, Less, LessOrEqual, Log, LogSoftmax, LRN, LSTM, MatMul, MaxPool, Max, Min, Mod, Mul, Neg, Not, OneHot, Pad, Pow, PRelu, QuantizeLinear, QLinearConv, QLinearMatmul, RandomNormal, RandomNormalLike, RandomUniform, RandomUniformLike, Range, ReduceL1, ReduceL2, ReduceLogSum, ReduceLogSumExp, ReduceMax, ReduceMean, ReduceMin, ReduceProd, ReduceSum, ReduceSumSquare, Relu, Reshape, Resize, ReverseSequence, Round, ScatterND, Selu, Shape, Sin, Sinh, Sigmoid, Sign, Size, Slice, Softmax, Softplus, Softsign, SpaceToDepth, Split, Sqrt, Squeeze, Sub, Sum, Tanh, Tile, TopK, Transpose, Upsample, Unsqueeze, Where.
-
-Operators outside this list fall back to CPU through nncase, which is where most real-world "the model runs but it is slow" reports originate. The compiler is **nncase**; see `K230_nncase_Development_Guide.md` in the [artifacts](#16-local-artifacts).
-
----
-
-## 4. Other accelerators
-
-| Block | What it is | Headline numbers (C1) |
-|---|---|---|
-| **2D GDMA engine** | mirror / rotate 90-180-270, linked-list DMA, 64-bit AXI | 2 × 1080×1280 YUV400 @15 fps **+** 1 × 1080×1920 YUV420 @30 fps; max image 64K×64K; 8/16/24/32-bit pixels |
-| **Non-AI 2D** | OSD, colour-space conversion, border draw, crop | — |
-| **AI 2D engine** (independent) | affine / crop / resize / pad / shift / CSC, OpenCV-compatible rounding | source images up to 4K; can access the 2 MB system SRAM; DDR addresses want 16-byte alignment |
-| **DPU** | 3D **structured-light** depth engine (Img_check / LCN / SAD / Post_proc / Align / Disptodepth) | 1280×800@30, 1280×1080@15, 1920×1080@9 fps; max 1920×1080 landscape, 1080×1440 portrait |
-| **2.5D GPU** (VeriSilicon-style, VGLite driver) | tessellation, 16× MSAA at no throughput cost, 4 texels/cycle bilinear, alpha blend, frame-buffer compression, path/gradient draw | RGBA8888/BGRA8888/ABGR8888, RGBA5551, RGB565, A8/L8/RGB332, A4/L4, A2/L2, A1/L1, 1/2/4/8-bit indexed |
-| **Decompression** | hardware **GZIP/DEFLATE** | **≥ 400 MB/s**, 32 KB dictionary, dynamic-Huffman only, CRC32, 32 KB max per DMA request |
-| **FFT/IFFT** | up to **4096-point**, INT16 | 4096-point round trip **≤ 1 ms** including data movement and interrupt |
-
-The GZIP block and the FFT block are unusual for this class and are easy to miss. The decompression engine is what makes Canaan's "fastboot: 3A first picture ≤ 400 ms" claim (C1, C2) achievable — boot images are shipped compressed and expanded in hardware.
-
----
-
-## 5. Video, camera and display subsystems
-
-| Subsystem | Capability | Evidence |
-|---|---|---|
-| **MIPI CSI-2 in** | **3 × CSI**, arranged as (1 × 4-lane + 1 × 2-lane) **or** 3 × 2-lane | C2 |
-| **ISP** | total throughput **8 MP @ 30 fps**; 3A, 2DNR, 3DNR, WDR, HDR, local tone mapping, sharpen, BLS, LSC, de-warping, **RGB-IR 4×4** | C2 |
-| **MIPI DSI out** | **1 × DSI**, 4-lane or 2-lane; **2 MP @ 60 fps** | C2 |
-| **Video encode** | H.264 BP/MP/HP, H.265 MP, JPEG/MJPEG; **8 MP @ 20 fps**; CBR/VBR/CQP/ROI | C2 |
-| **Video decode** | H.264 BP/MP/HP, H.265 MP, JPEG/MJPEG; **8 MP @ 40 fps** | C2 |
-
-The RGB-IR 4×4 pattern support and the structured-light DPU together are the give-away that this part was designed for **face-unlock door locks and payment terminals** — Canaan's own application list leads with exactly that (C1).
-
----
-
-## 6. Audio, memory and peripherals
-
-**Audio (on-die codec — no external codec required for basic use):**
-- **2 DAC channels**, stereo playback, **8–192 kHz**
-- **2 ADC channels**, stereo mic capture, 8–192 kHz, with **ALC** (automatic level control)
-- up to **8 PDM DMIC** inputs (1–4 IO pins, 32×/64×/128× oversampling, clocks 0.256–24.576 MHz)
-- **I2S** with 2×2 expansion, master mode, full duplex; PDM-in, I2S-in and I2S-out can run simultaneously
-- PCM over PDMA; APB2.0 register interface, PCLK default 100 MHz
-
-**Memory controller:**
-- **LPDDR4** 16-bit per channel × **2 channels** (so 32-bit total), max **3200 Mbps** per C1; C2 quotes **LPDDR4 @ 2667 Mbps** and the SiP at **3200 Mbps** — a vendor-internal inconsistency, recorded rather than resolved
-- **LPDDR3** 32-bit @ 2133 Mbps; **DDR3L** @ 1600 Mbps (C2)
-- max **2 GB**, up to 2 ranks, 1:2 clock ratio as configured by Canaan
-- 5 AXI host ports, out-of-order execution, write combining, automatic power-down/clock-stop, periodic retraining, firmware 2D eye-mapping diagnostic
-
-**Flash:** SPI NOR **and** SPI NAND, internal-DMA read/write, dual/quad/octal, DDR with read data strobe, **XIP from SPI NOR**.
-
-**Low-speed peripherals (C2):** 5 × UART (16550-compatible, 32-deep FIFOs, fractional baud), 5 × I²C (standard/fast/fast+/**high-speed 3.4 Mb/s**, 7- and 10-bit), 6 × PWM, 64 GPIO + 8 PMU GPIO (50 + 6 on the SiP), WDT, RTC, timers.
-
-**High-speed peripherals (C2):** 2 × **USB 2.0 OTG**, 2 × **SDxC** (SD 3.01 / eMMC 5.0, 4/8-bit, HS200/HS400, boot operation), 3 × SPI (1 × OSPI + 2 × QSPI, 256-deep FIFOs, 4–32-bit frames).
-
-**Security (C1):** PUF, **32 kbit OTP** with protection, TRNG (160 Mbps @ 20 MHz, ≤ 50 µs stabilisation), AES-128/192/256, CMAC, SM4-128, RSA-1024…4096, ECC/ECDSA/ECDH across the usual curve set, SM2, HMAC, SHA-224…512 and the SHA-512/t truncations, SM3, and **secure boot with signature verification**.
-
-**PMU (C1, C2):** 32 kHz RTC; default 6 inputs / 2 outputs, IO-configurable and reusable as GPIO up to 25 MHz; one long/short-press detector usable as shutdown or wake; one edge counter with periodic clear; two edge+level detectors with debounce; four edge/level detect groups; **two output IOs specifically for controlling an external PMIC and system reset**; 512 bits of retained shutdown log.
-
-That last item matters at board level: **K230 expects an external PMIC**, and the PMU's job is to sequence it.
-
----
-
-## 7. What the K230 does *not* have
-
-Stated as positive negative results, each checked against the full feature list in C1 and the summary list in C2 on 2026-09-04:
-
-| Absent | Consequence |
-|---|---|
-| **Any radio** — no Wi-Fi, no Bluetooth, no 802.15.4, no cellular | Every K230 board needs an external radio. On the LilyGO board that is an SDIO Wi-Fi module + a **USB** Bluetooth dongle. |
-| **Ethernet MAC** | An RJ45 on a K230 board is a **USB**-attached Ethernet controller, not a MAC+PHY pair. This is exactly what LilyGO did (RTL8152B, [§Used By](#17-used-by)). |
-| **On-die or in-package flash** | Boot media is external: SD, eMMC, SPI NOR or SPI NAND. |
-| **A third / low-power programmable core** | No always-on core to hand sensor polling to. Compare ESP32-P4's LP core. |
-| **CAN / TWAI** | Not in the peripheral list. |
-| **A published TOPS figure** | See [§3](#the-tops-number-is-a-marketing-figure-not-a-datasheet-figure). |
-| **A public errata document** | None located in `kendryte/k230_docs` or on the developer portal as of 2026-09-04. Absence of published errata is not absence of errata. |
-
----
-
-## 8. Electrical and thermal
-
-The full datasheet (C1) carries Absolute Maximum Ratings, Recommended Operating Conditions, general-IO DC characteristics, PLL characteristics, and separate electrical sections for **DDR, MIPI DSI, MIPI CSI, USB and SD/eMMC**. Working environment temperature is **−40 … +85 °C** (C1, C2). Deep-sleep standby is quoted at **≤ 20 µW** (C2).
-
-**IO bank voltages are software-selected and can destroy the chip.** The board device tree sets a per-bank `MSC` field, and Canaan's own reference DTS carries the comment *"Please pay attention to the bank voltage! will damage the chip."* Banks are grouped `IO0–IO1` (fixed 1.8 V on the reference design), `IO2–IO13`, `IO14–IO25`, `IO26–IO37`, `IO38–IO49`, `IO50–IO61`, `IO62–IO63`. Getting a bank's `K230_MSC_1V8` / `K230_MSC_3V3` selection wrong against the external circuit is a documented hardware-damage path, not a soft failure. See the device record's [pinouts-and-buses.md](../../../devices/lilygo/t-display-k230/pinouts-and-buses.md).
-
-Detailed numeric tables are in the retained datasheet artifact rather than copied here, because they are long and because the text layer of the Markdown source is trustworthy only for what has been cross-checked against the published HTML build.
-
----
-
-## 9. Boot media and boot-ROM behaviour
-
-| Mechanism | Detail | Evidence |
-|---|---|---|
-| Boot sources | SD (SDIO/SDMMC), eMMC (with boot and alternative-boot operation), SPI NOR, SPI NAND | C1 |
-| Boot strapping | **`IO0` = BOOT0, `IO1` = BOOT1** on Canaan's reference DTS (both configured 1.8 V, output, pull-up in the reference pinmux) | C3 |
-| USB recovery | Boot ROM can be driven over USB; Canaan ships **`k230_burntool`** (`K230_SDK_Burntool_User_Guide.md`) | C1 docs set |
-| Third-party recovery | **oreboot** supports K230 and boots Linux **from mask ROM over USB in ~3 s**; author also publishes `kendryte_boot` | R1 |
-| Secure boot | signature-verified, backed by OTP and PUF | C1 |
-
-**The practical failure mode.** Selecting the wrong boot medium is recoverable *only* through the boot ROM's USB path. A T-Display K230 owner reported on 2026-08-21/28 that after flashing "into mmc mode vs sd card" the board was "**still unresponsive to boot pin and term**" (R2, firsthand ownership). If you are going to change boot configuration on a K230 board, know the USB boot-ROM path **before** you do it.
-
----
-
-## 10. Documentation set and where it lives
-
-Canaan publishes K230 documentation as **Markdown in a Git repository**, not as PDFs on a portal. This is unusual and it is the single most useful sourcing fact about the vendor.
-
-| What | Where |
-|---|---|
-| Canonical repository | `github.com/kendryte/k230_docs`, branch `main` |
-| Rendered HTML | `https://www.kendryte.com/k230/en/main/00_hardware/K230_datasheet.html` |
-| Developer portal | `https://developer.canaan-creative.com/` (SDK images under *K230 → Images*, resources under `/resource`) |
-| Language split | Everything exists twice: `en/…` and `zh/…`. **The `zh/` tree carries binary hardware artifacts the `en/` tree does not** — schematics (`.DSN`, PDF), Gerbers, PCB, DXF, SMT and BOM `.xlsx` for the K230 LP3 demo board, the LP4 USIP EVB and the K230D SIP EVB, plus `CanMV-K230-V1.0_2023-09-15.pdf`. If you only read `en/`, you will conclude no schematics are published. They are — under `zh/00_hardware/`. |
-| Pinout | `《K230_PINOUT_V1.0_20230524》` is **referenced by the datasheet but not present in the repository** (C1 §"Pin information description"). Negative result, verified 2026-09-04 against the full recursive tree listing. |
-| Licence | Repository is **BSD-2-Clause**; the datasheet body carries a **restrictive Canaan copyright notice** forbidding redistribution without written permission. The two disagree — see [§18](#18-licensing). |
-
-Sourcing procedure and traps are written up once, reusably, in [`vendors/canaan/README.md`](../../../vendors/canaan/README.md).
-
----
-
-## 11. Competing and substitute parts
-
-Compared for the workload this part actually appears in: a battery-powered handheld or fixed appliance with a MIPI panel, a MIPI camera, on-device inference and a Linux userspace.
-
-| Part | Cores | Vector/DSP | NPU | RAM | Display | Camera | Video codec | Radio | Ethernet MAC | Notes |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **Canaan K230** | 2 × RV64 C908 @ 1.6 GHz + 0.8 GHz | **RVV 1.0, 128-bit, CPU1 only** | KPU INT8/INT16; ResNet-50 ≥ 85 fps | ext. LPDDR4 ≤ 2 GB (K230) / 128 MB SiP (K230D) | 1 × MIPI DSI, 2 MP@60 | **3 × MIPI CSI** | H.264 **and H.265** enc+dec, 8 MP@20/40 | **none** | **none** | 3D structured-light DPU, GZIP engine, FFT unit |
-| **[Espressif ESP32-P4](../../espressif/esp32-p4/README.md)** | 2 × RV32 HP @ 400 MHz **+ 1 × RV32 LP @ 40 MHz** | Espressif PIE (AI/DSP ext.) | **none** | 16/32 MB **in-package PSRAM** | 1 × MIPI DSI | 1 × MIPI CSI | **H.264 encode only** | **none** | **yes** (RMII, ext. PHY) | Genuine third LP core; MCU-class RAM; ESP-IDF ecosystem |
-| Allwinner V853 | 1 × Cortex-A7 @ 1 GHz + RISC-V E907 | NEON | 1 TOPS NPU | 64/128 MB DDR3 in-package | RGB/LVDS/MIPI DSI | 2 × MIPI CSI | H.264/H.265 enc | none | yes | Arm; mature Tina/Linux BSP; weaker vector story |
-| Rockchip RV1106 | 1 × Cortex-A7 + RISC-V | NEON | 0.5 TOPS | 64/128/256 MB DDR3L in-package | MIPI DSI | 1 × MIPI CSI | H.264/H.265 enc | none | **yes** (10/100) | The IP-camera default; huge community; single A7 |
-| Sophgo/CVITEK **CV1800B** | 1 × C906 @ 1 GHz + 1 × C906 @ 700 MHz | **no RVV** (C906 here is RV64GC) | 0.5 TOPS TPU | 64 MB DDR2 in-package | MIPI DSI | MIPI CSI | H.264/H.265 enc | none | yes | Milk-V Duo; cheapest RISC-V Linux; far less memory and no vector |
-| Sophgo **SG2002** | C906 @ 1 GHz + C906 @ 700 MHz + 8051 | no RVV | 1 TOPS | 256 MB in-package | MIPI DSI | MIPI CSI | H.264/H.265 | none | yes | CV1800B successor, Arm-or-RISC-V selectable big core |
-
-### K230 versus ESP32-P4, stated precisely
-
-They are not the same class of part and the comparison is worth doing only because they are both "RISC-V, MIPI DSI + CSI, no radio" and land in similar handheld designs.
-
-- **K230 is an application processor; ESP32-P4 is a high-end MCU.** K230 runs a full Linux distribution against gigabytes of external LPDDR4 with an MMU per core and 64-bit addressing. ESP32-P4 runs FreeRTOS against 768 KB of L2MEM plus 16–32 MB of in-package PSRAM and has no external DRAM interface at all. The step from 32 MB PSRAM to 1 GB LPDDR4 is roughly 30×, and it is what makes a browser, a Python stack or a general-purpose launcher possible on one and not the other.
-- **K230 has a real NPU and a real H.265 codec; ESP32-P4 has neither.** The P4 has an H.264 *encoder* only, no decoder and no neural accelerator; K230 encodes and decodes H.264 and H.265 at 8 MP and adds an INT8/INT16 KPU quoted at ResNet-50 ≥ 85 fps.
-- **ESP32-P4 wins on the things K230 omitted**: a genuine always-on low-power core with its own peripheral set, an Ethernet MAC, USB 2.0 High-Speed device *and* the ESP-IDF ecosystem with first-party Wi-Fi companion-chip support. K230's answer to all three is "add another chip on USB or SDIO".
-- **Toolchain maturity is not close.** ESP-IDF is a single, versioned, well-documented SDK with a `nixpkgs-esp-dev` flake ([`guides/nixos/README.md`](../../../guides/nixos/README.md)). K230 requires a vendor XuanTie GCC tarball unpacked at a hard-coded `/opt/toolchain` path, Buildroot, a submodule SDK and — per Canaan's own instructions — Docker or Ubuntu 20.04/22.04. See [§14](#14-software-toolchain-and-os-support).
-
-**Two-sentence summary.** The K230 is an application-class RISC-V SoC — gigabyte-scale external LPDDR4, MMU-backed Linux, a real INT8/INT16 NPU, H.264 *and* H.265 encode and decode, three MIPI CSI inputs and a structured-light depth engine — where the ESP32-P4 is a high-end microcontroller with 16–32 MB of in-package PSRAM, no NPU and H.264 encode only. In exchange the P4 gives you a genuine always-on low-power third core, an Ethernet MAC and the mature ESP-IDF toolchain, none of which the K230 has; K230's software story is a vendor Buildroot tree pinned to a hard-coded toolchain path.
-
----
-
-## 12. Availability and pricing
-
-**Bare-chip pricing was not established in this pass.** Canaan does not publish K230 unit pricing, no authorised-distributor line-card entry was located on Digi-Key, Mouser or LCSC on 2026-09-04, and the sales channel published on the datasheet is an email address (`salesAI@canaan-creative.com`). Treat any TR/tray price you find as unverified.
-
-Board-level prices give the only usable floor, dated 2026-09-04 (see the device record's [market-and-pricing.md](../../../devices/lilygo/t-display-k230/market-and-pricing.md) for full observations):
-
-| Board | Part | Observed | Date | Source |
-|---|---|---|---|---|
-| Banana Pi **BPI-CanMV-K230D-Zero** | K230**D** (SiP, 128 MB) | **$29** at announcement | 2024-11-18 | N2 |
-| **CanMV-K230** | K230 + 512 MB | listed at launch, repeatedly out of stock | 2023-10 onward | N1, R3 |
-| LilyGO **T-Display K230** | K230 + 1 GB | **$98.79** | 2026-09-04 | D1 |
-| LilyGO **T-Display K230 Kit** | + keyboard base | **$150.31 / $153.01** | 2026-09-04 | D2 |
-
-Community reports of purchasing difficulty are persistent and old: r/RISCV, 2024-05-08, "**Where do people buy CANMV K230 from?**" (R3); LilyGO's first T-Display K230 announcement thread, 2025-03-26, "**Already sold out**" (R4).
-
----
-
-## 13. Notable K230 boards
-
-| Board | Vendor | K230 variant | RAM | Distinguishing |
-|---|---|---|---|---|
-| **CanMV-K230** | Canaan | K230 | 512 MB | Reference board; 3 × camera; the board the SDK targets by default |
-| K230 DEMO BOARD (LP3) / K230 USIP EVB (LP4) | Canaan | K230 | — | Full EDA source published under `zh/00_hardware/` |
-| K230-SIP-EVB | Canaan | K230D | 128 MB | SiP evaluation board, EDA source published |
-| **BPI-CanMV-K230D-Zero** | Banana Pi | K230D | 128 MB | $29 Zero-form-factor |
-| **T-Display K230 / K230 Kit** | LilyGO | K230 | **1 GB** | 4.1″ AMOLED handheld, LoRa, keyboard base — [device record](../../../devices/lilygo/t-display-k230/README.md) |
-| MaixCAM-derived K230 boards | Sipeed | K230 | varies | MaixPy runtime |
-
----
-
-## 14. Software, toolchain and OS support
-
-| Stack | Repository | Status |
-|---|---|---|
-| **k230_sdk** (dual-OS: RT-Smart on CPU1 + Linux on CPU0) | `kendryte/k230_sdk`, BSD-2-Clause, 273★, last push **2025-09-12** | The original, full-feature SDK. Docker image `ghcr.io/kendryte/k230_sdk` is the supported build environment. |
-| **k230_linux_sdk** (Linux-only) | `kendryte/k230_linux_sdk`, branch `dev`, BSD-2-Clause, 62★, last push **2026-09-03** | Actively maintained; **this is what the LilyGO BSP builds on**, pinned at `22d02c6b6783a57a3aca7eb3160e313e772cb710`. |
-| **CanMV / canmv_k230** (MicroPython) | `kendryte/canmv_k230`, 119★, last push 2026-09-03 | MicroPython on K230, the K210 "CanMV" lineage continued. |
-| **MaixPy** | `sipeed/MaixPy`, 843★, last push 2026-08-28 | Sipeed's Python runtime; K230 is a supported target. |
-| **nncase** | Canaan | Model compiler; version must match the SDK — Canaan publishes an explicit `K230_SDK_nncase_version_correspondence` table. Mismatched nncase/runtime pairs are a common failure. |
-| **oreboot** | `oreboot/oreboot`, GPL-2.0, 1795★ | Third-party open firmware **with K230 support**; boots Linux from mask ROM over USB in ~3 s (R1). |
-| **k230-debian** | `intx82/k230-debian`, BSD-2-Clause, kernel 6.6 branch, last push 2024-12-03, 1★ | Debian userspace experiment. Low activity — treat as a starting point, not a distribution. |
-| **RT-Thread / RT-Smart** | upstream RT-Thread | The CPU1 OS in `k230_sdk`. |
-| **Zephyr** | — | **No K230 board or SoC support found upstream** as of 2026-09-04. Negative result. |
-
-### Toolchain reality
-
-The compiler is **T-Head/XuanTie GCC**, not upstream RISC-V GCC. LilyGO's Buildroot defconfig pins it exactly:
-
-```
-BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/toolchain/Xuantie-900-gcc-linux-6.6.0-glibc-x86_64-V3.0.2/"
-BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX="riscv64-unknown-linux-gnu"
-BR2_TARGET_OPTIMIZATION="-mcpu=c908v -mtune=c908 -mrvv-v0p10-compatible -mrvv-auto-vectorize"
-```
-
-Three things follow. First, `-mcpu=c908v` is a **XuanTie-specific** `-mcpu` value; mainline GCC does not know it. Second, `-mrvv-v0p10-compatible` means the shipped userspace is built for the **draft RVV 0.10** encoding even though the core implements ratified **RVV 1.0** — vendor toolchains carry this compatibility mode and binaries built with a mainline RVV-1.0 GCC are not interchangeable with it. Third, the path is **hard-coded to `/opt/toolchain/…`**, which is the specific detail that breaks NixOS and any non-FHS host.
-
-The kernel is **not** mainline either: `BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/ruyisdk/linux-xuantie-kernel.git"` at commit `7d4e1f444f461dbe3833bd99a4640e7b6c2cd529`, defconfig `k230`.
-
-NixOS-specific analysis, including why `pkgsCross.riscv64-embedded` does not substitute: [`guides/nixos/riscv-and-vendor-sdk-toolchains.md`](../../../guides/nixos/riscv-and-vendor-sdk-toolchains.md).
-
----
-
-## 15. Known caveats and unsafe assumptions
-
-1. **Do not assume RVV on CPU0.** Only CPU1 has the vector unit.
-2. **Do not assume a coherent SMP pair.** Two OSes, two PLICs, IPC in between.
-3. **Do not assume "K230" means "K230D"** or that a K230D board can be given more RAM. The DRAM is in the package.
-4. **Do not assume a TOPS figure.** Canaan does not publish one.
-5. **Do not assume Ethernet or any radio.** Neither exists on the die.
-6. **Do not set IO bank voltages casually.** Canaan's own DTS warns this damages the chip.
-7. **Do not mix nncase versions.** Canaan publishes a correspondence table because mismatches fail at runtime, not at build time.
-8. **Do not treat `-mrvv-v0p10-compatible` binaries as RVV-1.0 binaries.**
-9. **`K230_PINOUT_V1.0_20230524` is cited by the datasheet but not published.** Ball assignments must come from a board schematic.
-10. **No errata document is published.** Plan verification accordingly.
-
----
-
-## 16. Local artifacts
-
-All retrieved 2026-09-04 from `github.com/kendryte/k230_docs` at commit **`f8e30213963e0ed5cf995c3cd4701218a45e4793`** (2025-09-12), raw path `https://raw.githubusercontent.com/kendryte/k230_docs/main/<path>`. Permalink form: `https://github.com/kendryte/k230_docs/blob/f8e30213963e0ed5cf995c3cd4701218a45e4793/<path>`.
-
-| File | Upstream path | Bytes | SHA-256 | Establishes |
-|---|---|---|---|---|
-| `artifacts/K230_datasheet-v1.0-2023-07-06.md` | `en/00_hardware/K230_datasheet.md` | 83 002 | see [`artifacts/SHA256SUMS`](artifacts/SHA256SUMS) | Full feature list, packages, electrical sections |
-| `artifacts/K230_brief_datasheet.md` | `en/K230_brief_datasheet.md` | 7 781 | ″ | Core roles, package sizes, peripheral counts, SiP memory |
-| `artifacts/K230_Hardware_Design_Guide.md` | `en/00_hardware/K230_Hardware_Design_Guide.md` | 49 061 | ″ | Board-design rules |
-| `artifacts/K230_PMU_User_Guide.md` | `en/01_software/board/osdrv/K230_PMU_User_Guide.md` | 10 039 | ″ | PMU register flow, power key, shutdown |
-| `artifacts/K230_nncase_Development_Guide.md` | `en/01_software/board/ai/K230_nncase_Development_Guide.md` | 81 128 | ″ | KPU model compilation |
-| `artifacts/K230_RVV_In_Action.md` | `en/02_applications/tutorials/K230_RVV_In_Action.md` | 12 528 | ″ | Practical RVV use on CPU1 |
-| `artifacts/K230_RVV_optimization_performance_description.md` | `en/02_applications/tutorials/K230_RVV_optimization_performance_description.md` | 12 004 | ″ | Vector speed-up figures |
-
-**Not retrieved, and why.** The binary hardware set under `zh/00_hardware/` — `CanMV-K230-V1.0_2023-09-15.pdf` (3.1 MB), `K230-SIP-EVB-V1.0-A.1-20230317.pdf` (967 KB), `K230-DEMO-BOARD-SCH.pdf` (969 KB), the `.DSN` OrCAD sources (1.7–1.85 MB each), and the Gerber/PCB/DXF/SMT/BOM archives — is **Canaan reference-board** material, not K230 die documentation, and none of it describes the LilyGO board. It is enumerated in [`artifacts/CANAAN-EDA-SET.md`](artifacts/CANAAN-EDA-SET.md) with exact paths, sizes and two reacquisition URLs each, so it can be fetched on demand without re-deriving the listing. Reacquisition status: **automatic**.
-
----
-
-## 17. Used By
-
-### [LilyGO T-Display K230 / T-Display K230 Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-The main SoC. **K230 (13 × 13 mm, non-SiP) with 1 GB of external LPDDR4** — LilyGO's own kit specification reads "32 LPDDR4, Capacity: 8 Gb", i.e. a 32-bit-wide bus (both 16-bit channels populated) and an 8 Gb = 1 GB device. This is four times the CanMV-K230 reference board and eight times a K230D.
-
-How the board resolves each of the SoC's absences:
-
-| K230 lacks | LilyGO's answer on this board |
-|---|---|
-| Wi-Fi | **RTL8189FS** over SDIO ([component](../../realtek/rtl8189fs/README.md)); the BSP also builds RTL8723DS and RTL8733BS drivers |
-| Bluetooth | **USB dongle** — the BSP force-enables a CSR8510/8891 workaround and builds BlueZ; there is *no* on-board BT radio. LilyGO's wiki additionally claims an ESP32-S3-R8 co-processor, which the BSP does not corroborate — conflict `GC-2` |
-| Ethernet MAC | **RTL8152B USB 10/100** ([component](../../realtek/rtl8152b/README.md)) behind the RJ45 |
-| Cellular / GNSS | **nRF9151** on the keyboard base, over UART3 |
-| BLE central | **nRF52840** on the expansion base, over UART1 |
-| PMIC | present but unidentified — [`components/unidentified/t-display-k230`](../../unidentified/t-display-k230/README.md) |
-
-K230 signals used, from LilyGO's own BSP pin map (D3): MIPI DSI → RM69A10 AMOLED with `GPIO22` reset and `GPIO25` enable; MIPI CSI + I²C0 (`GPIO48/49`) → GC2093; I²C3 (`GPIO36/37`) → GT9895 touch at `0x5D`, `GPIO23` IRQ, `GPIO24` reset; MMC1 (`GPIO54–59`) → microSD, which is also the boot medium; SDIO → Wi-Fi; SPI (`GPIO14–17`, `19`, `20`, `44`) → SX1262/LR2021 LoRa; UART1 (`GPIO3/4`) → nRF52840; UART3 (`GPIO28/29`) → nRF9151; I²C4 (`GPIO46/47`) → the whole keyboard-base I²C bus; I2S (`GPIO32–35`) → MAX98357A; PWM4 (`GPIO52`) → keyboard backlight; `GPIO0` = BOOT0 button; `GPIO64` = PMU INT0 power key. Full table: [pinouts-and-buses.md](../../../devices/lilygo/t-display-k230/pinouts-and-buses.md).
-
-LilyGO ships a Linux-only image built from `k230_linux_sdk`, so on this board **Linux runs on CPU0 and CPU1 is not running RT-Smart** in the default configuration.
-
----
-
-## 18. Licensing
-
-| Artifact class | Terms | Evidence | Disposition |
-|---|---|---|---|
-| `kendryte/k230_docs` repository as a whole | **BSD-2-Clause** (GitHub-detected licence on the repository) | C4 | `repository`, unstaged |
-| The datasheet *text* | "**without the written permission of the company, any unit or individual shall not disseminate part or all of the content of this document in any form**" | C1 §Trademark Notice | **conditional / conflicting** |
-
-These two are in direct conflict: the repository is published under a permissive licence that grants redistribution, while the document inside it carries a notice forbidding it. **Recorded, not resolved.** The retained copies are held unstaged pending a user decision. The safe reading is that Canaan applied a boilerplate corporate notice to a document it then published under BSD-2-Clause and did not reconcile the two.
-
-Redistribution status: **unknown/conflicting**. Disposition: **repository (unstaged)**.
-
----
-
-## 19. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Published/updated | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| C1 | K230 Product Full Datasheet, **V1.0** | Canaan Creative | primary | datasheet (Markdown) | `https://github.com/kendryte/k230_docs/blob/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/00_hardware/K230_datasheet.md` | 2026-09-04 | doc **2023-07-06**; repo commit 2025-09-12 | Complete feature list, KPU operators, packages, electrical sections, security, PMU |
-| C2 | K230 Brief Datasheet | Canaan Creative | primary | datasheet (Markdown) | `https://github.com/kendryte/k230_docs/blob/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/K230_brief_datasheet.md` | 2026-09-04 | repo commit 2025-09-12 | Core roles and frequencies, package dimensions, SiP memory, peripheral counts |
-| C3 | `k230_canmv_v3.dts` (U-Boot, Canaan copyright 2023) | Canaan / LilyGO overlay | primary | source | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/overlay/buildroot-overlay/boot/uboot/u-boot-2022.10-overlay/arch/riscv/dts/k230_canmv_v3.dts` | 2026-09-04 | commit 2026-09-03 | IO bank voltage warning, BOOT0/BOOT1 on IO0/IO1, per-pin mux |
-| C4 | `kendryte/k230_docs` repository metadata | Canaan Creative | primary | repository | `https://github.com/kendryte/k230_docs` | 2026-09-04 | HEAD `f8e3021…`, 2025-09-12 | Licence field BSD-2-Clause; full file inventory incl. `zh/00_hardware` EDA set |
-| C5 | `kendryte/k230_linux_sdk` repository metadata | Canaan Creative | primary | repository | `https://github.com/kendryte/k230_linux_sdk` | 2026-09-04 | pushed 2026-09-03 | Active Linux-only SDK, BSD-2-Clause |
-| D1 | T-Display K230 product page + `/products/t-display-k230.js` | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230` | 2026-09-04 | published 2025-03-21 | SKUs K256/-A/-B/-C, $98.79, SoC/display specification |
-| D2 | T-Display K230 Kit product page + `.js` | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230-kit` | 2026-09-04 | published 2026-08-20 | Kit SKUs, prices, full component list incl. RTL8189, GC2093, 8 Gb LPDDR4 |
-| D3 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | commit 2026-09-03 | Complete K230 pin/bus/peripheral map |
-| D4 | `k230_canmv_t_display_rm69a10_defconfig` | LILYGO | primary | source | same repo, `k230_bsp/overlay/buildroot-overlay/configs/` | 2026-09-04 | commit 2026-09-03 | XuanTie toolchain path and flags, kernel repo/commit, Wi-Fi packages |
-| D5 | T-Display K230 wiki page | LILYGO | primary | official wiki | `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/` | 2026-09-04 | undated | 1.6 TOPS claim, ESP32-S3-R8 claim, RTL8152B Ethernet, big/little-core FAQ error |
-| N1 | "CanMV-K230 AI development board features Kendryte K230 dual-core 64-bit RISC-V processor" | CNX-Software | community | blog | `https://www.cnx-software.com/2023/10/24/canmv-k230-ai-development-board-features-kendryte-k230-dual-core-64-bit-risc-v-processor/` | 2026-09-04 | 2023-10-24 | Launch-era independent coverage |
-| N2 | "$29 Banana Pi BPI-CanMV-K230D-Zero features Kendryte K230D RISC-V SoC" | CNX-Software | community | blog | `https://www.cnx-software.com/2024/11/18/29-banana-pi-bpi-canmv-k230d-zero-features-kendryte-k230d-risc-v-soc-for-aiot-applications/` | 2026-09-04 | 2024-11-18 | K230D board pricing datum |
-| N3 | "Kendryte K510 tri-core RISC-V AI processor deliver up to 3 TOPS" | CNX-Software | community | blog | `https://www.cnx-software.com/2021/07/09/kendryte-k510-tri-core-risc-v-ai-processor-3-tops/` | 2026-09-04 | 2021-07-09 | K510 lineage datum |
-| R1 | r/LilyGO comment by u/CyReVolt | Reddit | community | forum (**demonstrable project** — oreboot maintainer) | `https://old.reddit.com/r/LilyGO/comments/1jgb4kn/tdisplay_k230_is_available/` | 2026-09-04 | 2025-03-26 | oreboot K230 support; Linux from mask ROM over USB in ~3 s; `kendryte_boot` tool |
-| R2 | r/LilyGO comments by u/phirzcolru | Reddit | community | forum (**firsthand ownership**) | `https://old.reddit.com/r/LilyGO/comments/1vtcjuj/the_tdisplay_k230_kit_is_finally_here/` | 2026-09-04 | 2026-08-21 / 2026-08-28 | Bricked by boot-medium change; unresponsive to boot pin |
-| R3 | "Where do people buy CANMV K230 from?" | Reddit r/RISCV | community | forum | `https://old.reddit.com/r/RISCV/comments/1cmyur9/where_do_people_buy_canmv_k230_from/` | 2026-09-04 | 2024-05-08 | Availability difficulty |
-| R4 | "T-Display K230 is available!" thread | Reddit r/LilyGO | community | forum | `https://old.reddit.com/r/LilyGO/comments/1jgb4kn/` | 2026-09-04 | 2025-03-21 | Launch date, immediate sell-out |
-| R5 | "Kendryte K230 (RVV1.0 supported) available for remote access" | Reddit r/RISCV | community | forum | `https://old.reddit.com/r/RISCV/comments/1cnsdlh/kendryte_k230_rvv10_supported_available_for/` | 2026-09-04 | 2024-05-09 | RVV 1.0 interest; remote-access offer |
-
----
-
-## 20. Related records
-
-- Device using this part: [LilyGO T-Display K230](../../../devices/lilygo/t-display-k230/README.md)
-- Nearest comparable in this repository: [Espressif ESP32-P4](../../espressif/esp32-p4/README.md)
-- Vendor sourcing guide: [`vendors/canaan/README.md`](../../../vendors/canaan/README.md)
-- Host toolchain notes: [`guides/nixos/riscv-and-vendor-sdk-toolchains.md`](../../../guides/nixos/riscv-and-vendor-sdk-toolchains.md)
diff --git a/components/canaan/k230/artifacts/CANAAN-EDA-SET.md b/components/canaan/k230/artifacts/CANAAN-EDA-SET.md
deleted file mode 100644
index 94bbf7e..0000000
--- a/components/canaan/k230/artifacts/CANAAN-EDA-SET.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# Canaan K230 reference-board EDA and PDF set — enumerated, not retrieved
-
-**Status:** `reference-only` · **Reacquisition:** `automatic` · **Enumerated 2026-09-04**
-
-## What this is
-
-Canaan publishes the complete electrical design of its own K230 evaluation boards inside the
-documentation repository — but only under the **Chinese** tree (`zh/00_hardware/`). The English
-tree (`en/00_hardware/`) contains no binary hardware artifacts at all. An agent reading only
-`en/` will conclude that Canaan publishes no schematics. **It does.** That is the single most
-useful fact in this file.
-
-## Why it was not pulled into the repository
-
-None of it describes the **K230 die**, and none of it describes the **LilyGO T-Display K230**.
-It is board-level design data for three Canaan reference boards. The set totals roughly
-**19 MB** across 20 files, dominated by OrCAD `.DSN` sources and Gerber/PCB archives that are
-only useful with the matching EDA tool. The die-level documents that *are* relevant
-(`K230_datasheet`, `K230_brief_datasheet`, `K230_Hardware_Design_Guide`) are retained beside
-this file in Markdown form.
-
-## What was learned before deciding not to retain it
-
-- `K230_datasheet.md` §"Pin information description" defers ball assignments to a document
-  called **`K230_PINOUT_V1.0_20230524`**. A full recursive listing of the repository tree on
-  2026-09-04 confirms **that document is not published anywhere in the repository**, in either
-  language. The board schematics below are therefore the only public route to K230 ball
-  assignments.
-- Three distinct reference designs exist and they are *not* interchangeable: `K230_LP3`
-  (LPDDR3 demo board), `K230_LP4` (LPDDR4 USIP EVB) and `K230D` (SiP EVB). The LilyGO
-  T-Display K230 is an LPDDR4, non-SiP design, so `K230_LP4` is the closest reference.
-
-## Inventory
-
-Repository: `github.com/kendryte/k230_docs`, branch `main`, commit
-**`f8e30213963e0ed5cf995c3cd4701218a45e4793`** (2025-09-12). Licence on the repository:
-**BSD-2-Clause**; the documents themselves carry a restrictive Canaan notice (see the
-component README §18 — the two conflict).
-
-| Upstream path (under `zh/00_hardware/`) | Bytes |
-|---|---:|
-| `CanMV_K230/CanMV-K230-V1.0_2023-09-15.pdf` | 3 100 623 |
-| `CanMV_K230/CanMV-K230_2023-10-11.html` | 11 309 206 |
-| `K230D/K230-SIP-EVB-V1.0-A.1-20230317.pdf` | 967 009 |
-| `K230D/K230-SIP-EVB-V1_0-A_1-20230316.DSN` | 1 700 864 |
-| `K230D/K230-SIP-EVB-V1_0-A_1-20230322-DXF.zip` | 119 817 |
-| `K230D/K230-SIP-EVB-V1_0-A_1-20230322-GERBER.zip` | 411 727 |
-| `K230D/K230-SIP-EVB-V1_0-A_1-20230322-PCB.zip` | 2 444 898 |
-| `K230D/K230-SIP-EVB-V1_0-A_1-20230322-SMT.zip` | 691 376 |
-| `K230D/K230-SIP-EVB-V1_0-A_1_20230316-BOM.xlsx` | 22 658 |
-| `K230_LP3/K230-DEMO-BOARD-BOM-20230510.xlsx` | 21 132 |
-| `K230_LP3/K230-DEMO-BOARD-SCH.DSN` | 1 852 416 |
-| `K230_LP3/K230-DEMO-BOARD-SCH.pdf` | 969 203 |
-| `K230_LP3/K230_DEMO_BOARD-20230427-DXF.zip` | 168 246 |
-| `K230_LP3/K230_DEMO_BOARD-20230427-GERBER.zip` | 472 714 |
-| `K230_LP3/K230_DEMO_BOARD-20230427-PCB.zip` | 2 533 161 |
-| `K230_LP3/K230_DEMO_BOARD-20230427-SMT.zip` | 653 967 |
-| `K230_LP4/K230-USIP-EVB-LP4-SCH-V1.1-A.1-20230330.DSN` | 1 792 512 |
-| `K230_LP4/K230-USIP-EVB-LP4-SCH-V1.1-A.1-20230330.xlsx` | 19 378 |
-| `K230_LP4/K230-USIP-EVB-LP4-V1_1-A_1-20230412-DXF.zip` | 110 961 |
-| `K230_LP4/K230-USIP-EVB-LP4-V1_1-A_1-20230412-GERBER.zip` | 463 329 |
-| `K230_LP4/K230-USIP-EVB-LP4-V1_1-A_1-20230412-PCB.zip` | 1 934 860 |
-| `K230_LP4/K230-USIP-EVB-LP4-V1_1-A_1-20230412-SMT.zip` | 687 585 |
-
-Sizes are as reported by the Git tree API at the pinned commit and are exact. **SHA-256 is
-unknown** because the files were not downloaded — recorded as unknown rather than omitted.
-
-## Reacquisition — two independent URLs per file
-
-1. **Pinned permalink (preferred, immutable):**
-   `https://github.com/kendryte/k230_docs/raw/f8e30213963e0ed5cf995c3cd4701218a45e4793/zh/00_hardware/<path>`
-2. **Raw host (branch-tracking, mutable):**
-   `https://raw.githubusercontent.com/kendryte/k230_docs/main/zh/00_hardware/<path>`
-3. **Rendered documentation site (PDFs only, different host):**
-   `https://www.kendryte.com/k230/zh/main/00_hardware/`
-
-Whole-set command, verified as the working enumeration method on 2026-09-04:
-
-```sh
-gh api repos/kendryte/k230_docs/git/trees/f8e30213963e0ed5cf995c3cd4701218a45e4793?recursive=1 \
-  | python3 -c 'import json,sys; [print(e["size"], e["path"]) for e in json.load(sys.stdin)["tree"] if e["path"].startswith("zh/00_hardware")]'
-```
-
-`gh api` is required rather than anonymous `curl` — one recursive tree listing can exhaust the
-60/hour anonymous limit, and the resulting 403 looks exactly like a bot block.
diff --git a/components/canaan/k230/artifacts/K230_Hardware_Design_Guide.md b/components/canaan/k230/artifacts/K230_Hardware_Design_Guide.md
deleted file mode 100644
index 7aa0612..0000000
--- a/components/canaan/k230/artifacts/K230_Hardware_Design_Guide.md
+++ /dev/null
@@ -1,880 +0,0 @@
-# K230 Hardware Design Guide
-
-![cover](../../zh/00_hardware/images/HDG/canaan-cover.png)
-
-Copyright © 2023 Beijing Canaan Creative Information Technology Co., Ltd.
-
-<div style="page-break-after:always"></div>
-
-## Disclaimer
-
-The products, services, or features you purchase are subject to the commercial contracts and terms of Beijing Canaan Creative Information Technology Co., Ltd. ("the Company", hereinafter referred to as such) and its affiliates. All or part of the products, services, or features described in this document may not fall within the scope of your purchase or usage. Unless otherwise agreed in the contract, the Company does not provide any express or implied statements or warranties regarding the accuracy, reliability, completeness, merchantability, fitness for a particular purpose, or non-infringement of any statements, information, or content in this document. Unless otherwise agreed, this document is provided only as a reference guide.
-
-Due to product version upgrades or other reasons, the content of this document may be updated or modified periodically without any prior notice.
-
-## Trademark Statement
-
-![logo](../../zh/00_hardware/images/HDG/logo.png) "Canaan" and other Canaan trademarks are trademarks of Beijing Canaan Creative Information Technology Co., Ltd. and its affiliates. All other trademarks or registered trademarks mentioned in this document are owned by their respective owners.
-
-**Copyright © 2023 Beijing Canaan Creative Information Technology Co., Ltd. All rights reserved.**
-Without the written permission of the Company, no unit or individual is allowed to excerpt, copy any part or all of the content of this document, and it may not be transmitted in any form.
-
-<div style="page-break-after:always"></div>
-
-## Table of Contents
-
-[toc]
-
-## Preface
-
-### Overview
-
-This document mainly introduces the key points and precautions of the K230 processor hardware design, aiming to help customers shorten the product design cycle, improve product design stability, and reduce the failure rate. Please refer to the requirements of this guide for hardware design and try to use the relevant core templates released by K230. If changes are necessary due to special reasons, please strictly follow the requirements of high-speed digital circuit design.
-
-### Target Audience
-
-This document (guide) is mainly applicable to the following personnel:
-
-- Hardware Development Engineers
-- Technical Support Engineers
-- Test Engineers
-
-### Glossary
-
-| Abbreviation | Description                           |
-| ------------ | ------------------------------------- |
-| DDR          | Double Data Rate                      |
-| SDRAM        | Synchronous Dynamic Random Access Memory |
-| LPDDR        | Low Power Double Data Rate            |
-| MIPI         | Mobile Industry Processor Interface   |
-| OTG          | On the Go                             |
-| APB          | Advanced Peripheral Bus               |
-| SPI          | Serial Peripheral Interface           |
-| DMA          | Direct Memory Access                  |
-| AHB          | Advanced High Performance Bus         |
-| PCM          | Pulse Code Modulation                 |
-| PDM          | Pulse Density Modulation              |
-| PCLK         | Peripheral High-speed Clock           |
-| CLK          | Clock                                 |
-| DQS          | Bi-directional Data Strobe            |
-| GPIO         | General-purpose Input/Output          |
-| eMMC         | Embedded Multi-media Card             |
-| SIP          | System In a Package                   |
-| PMU          | Power Management Unit                 |
-
-### Revision History
-
-| Document Version | Modification Description | Modifier | Date       |
-| ---------------- | ------------------------ | -------- | ---------- |
-| V1.0             | Initial Version          | Zhao Ruixin | 2023-06-14 |
-
-## Chip Overview
-
-### Chip Block Diagram
-
-![Figure 1-1 K230 Block Diagram](../../zh/00_hardware/images/HDG/image002.jpg)
-Figure 1-1 K230 Block Diagram
-
-### Application Block Diagram
-
-Figure 1-2 is the K230 door lock application block diagram
-![Figure 1-2 K230 Door Lock Solution Application Block Diagram](../../zh/00_hardware/images/HDG/image003.jpg)
-Figure 1-2 K230 Door Lock Solution Application Block Diagram
-Figure 1-3 is the dictionary pen solution application block diagram
-![Figure 1-3 K230 Dictionary Pen Solution Application Block Diagram](../../zh/00_hardware/images/HDG/image004.jpg)
-Figure 1-3 K230 Dictionary Pen Solution Application Block Diagram
-
-## Packaging and Pins
-
-### Packaging
-
-#### Information
-
-The packaging information of K230 is shown in Table 2-1:
-
-| Device | Package  | Size          | Pitch |
-| ------ | -------- | ------------- | ----- |
-| K230   | VFBGA390 | 13mm x 13mm   | 0.65  |
-| K230D  | LFBGA256 | 11mm x 11mm   | 0.65  |
-
-#### Package Dimensions
-
-##### K230 Dimensions
-
-![Figure 2-1](../../zh/00_hardware/images/HDG/image005.png)
-Figure 2-1
-![Figure 2-2](../../zh/00_hardware/images/HDG/image006.png)
-Figure 2-2
-![Figure 2-3](../../zh/00_hardware/images/HDG/image007.png)
-Figure 2-3
-
-Ball Solder Mask Opening: 0.270mm
-
-Primary datum C and bottom are solder balls
-
-Dimension b is the maximum solder ball diameter, parallel to primary datum C
-
-##### K230D Dimensions
-
-![Figure 2-4](../../zh/00_hardware/images/HDG/image008.png)
-Figure 2-4
-![Figure 2-5](../../zh/00_hardware/images/HDG/image009.png)
-Figure 2-5
-
-Ball Solder Mask Opening: 0.270mm
-
-Primary datum C and bottom are solder balls
-
-Dimension b is the maximum solder ball diameter, parallel to primary datum C
-
-#### Pin Definition Diagram
-
-The pin distribution diagram of K230 is as follows:
-![Figure 2-6 K230 Package Pin Distribution](../../zh/00_hardware/images/HDG/image010.png)
-Figure 2-6 K230 Package Pin Distribution
-![Figure 2-7 K230D Package Pin Distribution](../../zh/00_hardware/images/HDG/image011.png)
-Figure 2-7 K230D Package Pin Distribution
-For pin details, see table [K230_PINOUT_V1.2_20240822.xlsx](https://kendryte-download.canaan-creative.com/developer/k230/HDK/K230%E7%A1%AC%E4%BB%B6%E6%96%87%E6%A1%A3/K230_PINOUT_V1.2_20240822.xlsx).
-
-## Schematic Design Recommendations
-
-### Minimum System Design
-
-#### Clock Requirements
-
-The main system of K230 requires a 24MHz high-speed clock, and the RTC of the PMU subsystem requires a 32.768kHz low-speed clock.
-
-Table 3-1 shows the parameters of the allowable clock sources for K230.
-
-| Frequency | Accuracy | Level |
-| --------- | -------- | ----- |
-| 32.768KHz | 20ppm    | 1.8V  |
-| 24MHz     | 20ppm    | 1.8V  |
-
-It is recommended to use clock sources with an accuracy of 20ppm or higher.
-
-##### High-Speed Clock
-
-The recommended passive crystal connection method is shown in Figure 3-1.
-![Figure 3-1 K230 Crystal Circuit](../../zh/00_hardware/images/HDG/image012.png)
-Figure 3-1 K230 Crystal Circuit
-Note:
-
-- The selected capacitors need to match the load capacitance of the crystal, and it is recommended to use NPO material.
-- It is recommended to use a 4-pin SMD crystal, with 2 GND pins fully connected to the ground to enhance the system clock's ESD interference resistance.
-- To improve the startup speed, a 1MΩ resistor can be added between the IN pin and the OUT pin.
-
-The recommended active crystal connection method is shown in Figure 3-2.
-![Figure 3-2 K230 Active Crystal Circuit](../../zh/00_hardware/images/HDG/image013.png)
-Figure 3-2 K230 Active Crystal Circuit
-During operation, the crystal output is connected to the CLK24M_XIN pin of K230, and the CLK24M_XOUT pin is left floating.
-
-##### Low-Speed Clock
-
-The K230 chip has a built-in PMU circuit, and the single board needs to provide a clock for the PMU circuit. The recommended circuit is shown in Figure 3-3.
-![Figure 3-3 K230 RTC Clock Passive Crystal Circuit](../../zh/00_hardware/images/HDG/image014.png)
-Figure 3-3 K230 RTC Clock Passive Crystal Circuit
-The recommended active crystal connection method is shown in Figure 3-4.
-![Figure 3-4 K230 RTC Clock Active Crystal Circuit](../../zh/00_hardware/images/HDG/image015.png)
-Figure 3-4 K230 RTC Clock Active Crystal Circuit
-
-During operation, the crystal output is connected to the CLK32K768_XIN pin of K230, and the CLK32K768_XOUT pin is left floating.
-Note:
-
-- When using an active crystal, the NC places in the above active crystal circuits need to be connected with a 0Ω resistor.
-
-#### Reset Circuit
-
-The hardware reset of K230 is achieved through the RSTN pin, which is active low.
-If using a button reset, it is recommended to add a 100nF capacitor to the reset signal pin to eliminate reset signal jitter, enhance anti-interference ability, and prevent system abnormal reset caused by mis-triggering.
-The reset circuit schematic is shown in Figure 3-5.
-![Figure 3-5 K230 Reset Circuit](../../zh/00_hardware/images/HDG/image016.png)
-Figure 3-5 K230 Reset Circuit
-
-#### System Boot Sequence
-
-The K230 chip provides four boot modes, which can be configured through the BOOT0 and BOOT1 pins.
-Table 3-2 shows the boot modes of K230 under different configurations.
-
-| BOOT0 | BOOT1 | K230       | K230D      |
-| ----- | ----- | ---------- | ---------- |
-| 0     | 0     | NOR FLASH  | NOR FLASH  |
-| 1     | 0     | NAND FLASH | NAND FLASH |
-| 0     | 1     | MMC0       | MMC0       |
-| 1     | 1     | MMC1       | MMC1       |
-
-Table 3-2 Boot Mode Description
-
-Note:
-
-- When all four boot modes fail, it will jump to USB/UART boot.
-
-Figure 3-6 shows the recommended BOOT circuit
-![Figure 3-6 K230 BOOT Circuit](../../zh/00_hardware/images/HDG/image017.png)
-Figure 3-6 K230 BOOT Circuit
-
-#### JTAG Debug Circuit
-
-The recommended JTAG interface circuit for the K230 chip is shown in Figure 3-7.
-![Figure 3-7 K230 JTAG Download Circuit](../../zh/00_hardware/images/HDG/image018.png)
-Figure 3-7 K230 JTAG Download Circuit
-Among them, JTAG_TCK, JTAG_TDI, JTAG_TMS, and JTAG_RST are recommended to be pulled up with 10kΩ, and JTAG_TDO is left floating.
-K230 must use the CKLink series debugger provided by Pingtouge Semiconductor Co., Ltd., otherwise, the chip cannot be debugged.
-
-#### DDR Controller
-
-The K230 chip has two versions, K230 and K230D. The K230 version requires a separate DDR circuit design. The K230D version has the DDR Die packaged together and does not require an external DDR circuit design.
-The K230 DDR controller has the following features:
-
-- Supports LPDDR3/LPDDR4
-- Supports 2 ranks
-- Supports 16-bit, 32-bit DDR data bus width
-- Verified models:
-
-  | Type  | Model            | Manufacturer | Capacity |
-  | ------ | ---------------- | ------------ | -------- |
-  | LPDDR3 | NT6CL128M32DM-H0 | Nanya     | 4Gb  |
-  | LPDDR3 | RS128M32LD3D1LMZ-125BT | Rayson     | 4Gb  |
-  | LPDDR4 | W66AP6NBUAF/G/HI | Winbond     | 4Gb  |
-  | LPDDR4 | K4F8E304HB-MGCJ  | Samsung     | 8Gb  |
-  | LPDDR4 | EM6LF32MBAJB-62SH  | EtronTech   | 8Gb  |
-    | LPDDR4 | RS256M32LS4D1BNR-46BT | Rayson   | 8Gb  |
-    | LPDDR4 | RS512M3LO4D1BDS-53BT  | Rayson   | 16Gb  |
-    | LPDDR4 | GDB4CBQN-MK  | GigaDevice  | 16Gb  |
-
-The schematic of the K230 DDR PHY and each DRAM chip must be consistent with the reference schematic, including power decoupling capacitors.
-
-##### LPDDR3
-
-The circuit design of LPDDR3 refers to Figures 3-8, 3-9, 3-10, and 3-11.
-![Figure 3-8 K230 LPDDR3 Circuit](../../zh/00_hardware/images/HDG/image019.png)
-Figure 3-8 K230 LPDDR3 Circuit
-![Figure 3-9 K230 LPDDR3 Power Circuit](../../zh/00_hardware/images/HDG/image020.png)
-Figure 3-9 K230 LPDDR3 Power Circuit
-![Figure 3-10 LPDDR3 Chip Power Circuit](../../zh/00_hardware/images/HDG/image021.png)
-Figure 3-10 LPDDR3 Chip Power Circuit
-![Figure 3-11 LPDDR3 Chip Circuit](../../zh/00_hardware/images/HDG/image022.png)
-Figure 3-11 LPDDR3 Chip Circuit
-
-When using LPDDR3:
-
-- The schematic of the DDR PHY and each DRAM chip needs to be consistent with the reference design, including power decoupling capacitors.
-- The DDR_ZN pin needs to be connected to a 240Ω (1%) calibration resistor to ground.
-- The DDR_RESET pin is left floating.
-- The chip has a built-in VREF circuit for the DDR controller, so the DDR_VREF pin needs to be left floating.
-- The LP3_VREFDQ voltage of the LP3 chip is 0.8V, and it is recommended to use 100Ω and 200Ω (1%) resistors for voltage division.
-- The LP3_VREFCA voltage is 0.6V, and it is recommended to use 1kΩ (1%) resistors for voltage division.
-- The CA, CS, CKE, CLK, and ODT pins of the LP3 need to use 100Ω resistors to pull up to DDR_VDDQ_1V2 and ground.
-
-##### LPDDR4
-
-The circuit design of LPDDR4 refers to Figures 3-12, 3-13, 3-14, 3-15, and 3-16.
-![Figure 3-12 K230 LPDDR4 Circuit](../../zh/00_hardware/images/HDG/image023.png)
-Figure 3-12 K230 LPDDR4 Circuit
-![Figure 3-13 K230 LPDDR4 Power Circuit](../../zh/00_hardware/images/HDG/image024.png)
-Figure 3-13 K230 LPDDR4 Power Circuit
-![Figure 3-14 K230 LPDDR4 Reference Voltage Circuit](../../zh/00_hardware/images/HDG/image025.png)
-Figure 3-14 K230 LPDDR4 Reference Voltage Circuit
-![Figure 3-15 LPDDR4 Chip Circuit](../../zh/00_hardware/images/HDG/image026.png)
-![Figure 3-16 LPDDR4 Chip Power Circuit](../../zh/00_hardware/images/HDG/image027.png)
-Figure 3-16 LPDDR4 Chip Power Circuit
-
-When using LPDDR4, note:
-
-- The schematic of the DDR PHY and each DRAM chip needs to be consistent with the reference design, including power decoupling capacitors.
-- The DDR_ZN pin needs to be connected to a 240Ω (1%) calibration resistor to ground.
-- The RESRT_N pin is directly connected to the corresponding pin of the chip.
-- When using LPDDR4 chips with K230, the VREF voltage is 0.6V, and it is recommended to use 1kΩ (1%) resistors for voltage division.
-
-##### K230D DDR Module
-
-K230D has a built-in DDR Die, so only the reference voltage and calibration resistor need to be connected.
-Reference circuits are shown in Figures 3-17 and 3-18.
-
-![Figure 3-17 K230D DDR Peripheral Circuit](../../zh/00_hardware/images/HDG/image028.png)
-Figure 3-17 K230D DDR Peripheral Circuit
-![Figure 3-18 K230D DDR Reference Voltage](../../zh/00_hardware/images/HDG/image029.png)
-Figure 3-18 K230D DDR Reference Voltage
-
-When using the K230D DDR module, note:
-
-- The VREF voltage is 0.55V, it is recommended to use 100Ω (1%) resistors for voltage division.
-- The calibration resistor should be 240Ω (1%).
-
-#### FLASH
-
-The K230 has an OSPI/QSPI controller that can be used to connect FLASH memory chips, with the following features:
-
-- OSPI supports 4/8-bit mode NOR FLASH.
-- OSPI supports NOR FLASH up to DDR200, SDR166.
-- QSPI supports 1/2/4-bit mode NAND & NOR FLASH.
-- QSPI supports NOR FLASH up to SDR100.
-
-##### OSPI
-
-The OSPI reference schematic is shown in Figures 3-19 and 3-20.
-![Figure 3-19 K230 OSPI Circuit](../../zh/00_hardware/images/HDG/image030.png)
-Figure 3-19 K230 OSPI Circuit
-![Figure 3-20 OSPI FLASH Circuit](../../zh/00_hardware/images/HDG/image031.png)
-Figure 3-20 OSPI FLASH Circuit
-
-Please place pull-up resistors according to the requirements of the FLASH chip.
-
-##### QSPI NOR
-
-In the QSPI signals, the CS, CLK, D0, D1, D2, and D3 pins are multiplexed with the corresponding OSPI signal pins, as shown in Table 3-3.
-
-| QSPI Pin | OSPI Pin |
-| -------- | -------- |
-| QSPI_CS  | OSPI_CS  |
-| QSPI_CLK | OSPI_CLK |
-| QSPI_D0  | OSPI_D0  |
-| QSPI_D1  | OSPI_D1  |
-| QSPI_D2  | OSPI_D2  |
-| QSPI_D3  | OSPI_D3  |
-
-Table 3-3 QSPI and OSPI Corresponding Pins
-
-The reference circuit is shown in Figure 3-21.
-![Figure 3-21 QSPI NOR FLASH Chip Circuit](../../zh/00_hardware/images/HDG/image032.png)
-Figure 3-21 QSPI NOR FLASH Chip Circuit
-Please place pull-up resistors according to the requirements of the FLASH chip.
-
-##### QSPI NAND
-
-The reference circuit for QSPI NAND is shown in Figure 3-22.
-![Figure 3-22 QSPI NAND FLASH Chip Circuit](../../zh/00_hardware/images/HDG/image033.png)
-Figure 3-22 QSPI NAND FLASH Chip Circuit
-Please place pull-up resistors according to the requirements of the FLASH chip.
-
-### MMC Circuit
-
-The K230 eMMC control circuit has two controllers, MMC0 and MMC1.
-
-#### MMC0
-
-The MMC0 controller has the following features:
-
-- Supports SDIO3.0, operating in 4/1-bit mode, up to SDR104.
-- Supports eMMC5.0, operating in 8/4/1-bit mode, supports HS200.
-- Supports voltage switching required by SD cards, 3.3V and 1.8V.
-
-MMC0 is generally used to control eMMC circuits. The recommended eMMC reference circuit is shown in Figures 3-23 and 3-24.
-
-![Figure 3-23 K230 eMMC Circuit](../../zh/00_hardware/images/HDG/image034.png)
-Figure 3-23 K230 eMMC Circuit
-![Figure 3-24 eMMC Chip Circuit](../../zh/00_hardware/images/HDG/image035.png)
-Figure 3-24 eMMC Chip Circuit
-
-Please connect the corresponding pins according to the eMMC manufacturer's requirements. If there are no special requirements, connect the corresponding pins directly.
-
-#### MMC1
-
-The MMC1 controller has the following features:
-
-- Supports SDIO3.0, operating in 4/1-bit mode, up to SDR104.
-- Supports voltage switching required by SD cards, 3.3V and 1.8V.
-
-The MMC1 interface's performance and pin count cannot meet the requirements for controlling eMMC circuits, so it can only be used to control SD/TF card circuits. The reference schematics are shown in Figures 3-25, 3-26, and 3-27.
-
-![Figure 3-25 K230 SD Card Interface Circuit](../../zh/00_hardware/images/HDG/image036.png)
-Figure 3-25 K230 SD Card Interface Circuit
-![Figure 3-26 SD Card Pull-up Circuit](../../zh/00_hardware/images/HDG/image037.png)
-Figure 3-26 SD Card Pull-up Circuit
-![Figure 3-27 SD Card Slot Circuit](../../zh/00_hardware/images/HDG/image038.png)
-Figure 3-27 SD Card Slot Circuit
-
-When designing the SD card circuit, note:
-
-- The decoupling capacitors for SD card pins should not be omitted and should be placed close to the card slot.
-- ESD devices should be placed near the SD card slot for each signal.
-- Pull-up resistors are required for each signal.
-- It is recommended to design according to the reference circuit.
-
-### USB Circuit
-
-The K230 chip has two built-in USB2.0 OTG controllers with the following features:
-
-- Supports USB2.0 protocol, backward compatible with USB 1.1 protocol.
-- Supports Host mode or Device mode, can be dynamically switched.
-- Host mode supports 480Mbps, 12Mbps, 1.5Mbps transfer rates.
-- Device mode supports 480Mbps, 12Mbps transfer modes.
-
-The USB reference schematics are shown in Figures 3-28 and 3-29.
-
-![Figure 3-28 K230 USB Circuit](../../zh/00_hardware/images/HDG/image039.png)
-Figure 3-28 K230 USB Circuit
-![Figure 3-29 USB Interface Circuit](../../zh/00_hardware/images/HDG/image040.png)
-Figure 3-29 USB Interface Circuit
-
-Note:
-
-- ESD devices should be placed near the USB port for each signal.
-- The USB_VBUS power of K230 must be connected to a 5V power supply through a 30kΩ (1%) resistor and cannot be directly connected to the power supply.
-- To ensure signal quality, the USB_TXRTUNE pin of K230 must be connected to a 200Ω (1%) resistor to ground.
-- The USB_ID can be used for OTG device identification. When grounded, K230 acts as a HOST; when floating or pulled high, K230 acts as a SLAVE.
-
-### Audio Circuit
-
-#### I2S
-
-The K230 chip has an I2S controller with the following features:
-
-- Two input and output channels.
-- Supports PHILIP I2S standard.
-- Supports left/right, PCM formats.
-- Synchronous operation mode.
-- Selectable master or slave mode.
-- Adjustable interface voltage.
-- Sampling rates from 8kHz to 384kHz.
-
-The I2S interface has three pins: I2S_CLK, I2S_WS, and I2S_SD. I2S_CLK is the serial clock signal, I2S_WS is the data frame control signal, and I2S_SD is the serial data signal. The I2S interface is typically used to connect to decoders and other audio peripherals. Figures 3-30 and 3-31 show the K230 I2S interface circuit and some peripheral circuits.
-![Figure 3-30 K230 I2S Interface Circuit](../../zh/00_hardware/images/HDG/image041.png)
-Figure 3-30 K230 I2S Interface Circuit
-![Figure 3-31 K230 I2S Reference Peripheral](../../zh/00_hardware/images/HDG/image042.png)
-Figure 3-31 K230 I2S Reference Peripheral
-
-#### PDM
-
-The K230 supports 4 channels of PDM signal input. Sampling rates range from 8kHz to 384kHz. The PDM interface is typically used to connect to digital microphones and other audio devices with PDM interfaces. Figure 3-32 shows the K230 PDM peripheral circuit.
-![Figure 3-32 K230 PDM Peripheral Circuit](../../zh/00_hardware/images/HDG/image043.png)
-Figure 3-32 K230 PDM Peripheral Circuit
-
-#### Analog Audio Interface
-
-The analog audio section of the K230 chip has the following features:
-
-- Supports 2 DAC channels and 2 ADC channels.
-- DAC supports differential and single-ended output, ADC supports differential and single-ended input.
-- Supports low-noise analog microphone bias output.
-
-The reference circuit for analog audio is shown in Figures 3-33 and 3-34.
-![Figure 3-33 K230 Analog Audio Interface Circuit](../../zh/00_hardware/images/HDG/image044.png)
-Figure 3-33 K230 Analog Audio Interface Circuit
-![Figure 3-34 Audio Interface Circuit](../../zh/00_hardware/images/HDG/image045.png)
-Figure 3-34 Audio Interface Circuit
-
-Note, to achieve better audio quality, consider the following measures:
-
-- Use both large and small capacitance low-ESR ceramic capacitors for power pins.
-- Place a large capacitance low-ESR capacitor on the MICBIAS pin.
-- Place the DC blocking capacitors for audio input close to the K230 chip.
-- Place filter circuits or DC blocking capacitors on the output pins.
-
-### Video Circuit
-
-#### MIPI DSI
-
-The MIPI DSI controller of the K230 has the following features:
-
-- Supports 1 signal output.
-- Supports 1/2/4-lane mode.
-- Maximum rate up to 1.5Gbps.
-
-All MIPI DSI signals are directly connected. The reference hardware design is shown in Figures 3-35 and 3-36.
-
-![Figure 3-35 K230 MIPI DSI Interface Circuit](../../zh/00_hardware/images/HDG/image046.png)
-![Figure 3-35 K230 MIPI DSI Interface Circuit](../../zh/00_hardware/images/HDG/image047.png)
-Figure 3-35 K230 MIPI DSI Interface Circuit
-![Figure 3-36 Screen Interface Circuit](../../zh/00_hardware/images/HDG/image048.png)
-Figure 3-36 Screen Interface Circuit
-
-Note:
-
-- The MIPI_ATB pin must be left floating.
-- The MIPI_REXT pin must be connected to a 200Ω (1%) resistor to ground.
-- The connector circuit pins are only suitable for the JinZhaoHui screen; please design the circuit according to your own screen module.
-
-### Camera Circuit
-
-#### MIPI CSI
-
-The MIPI CSI controller of the K230 has the following features:
-
-- Supports up to 3 MIPI signal inputs, supports 1/2/4-lane mode.
-- Can be configured as 3 channels of 2-lane signal input or 1 channel of 4-lane and 1 channel of 2-lane signal input.
-- Maximum rate up to 1.5Gbps.
-
-It is recommended to directly connect MIPI CSI signals. The reference hardware design is shown in Figures 3-37 and 3-38.
-![Figure 3-37 K230 MIPI CSI Interface Circuit](../../zh/00_hardware/images/HDG/image049.png)
-Figure 3-37 K230 MIPI CSI Interface Circuit
-![Figure 3-38 Camera Connector Circuit](../../zh/00_hardware/images/HDG/image050.png)
-Figure 3-38 Camera Connector Circuit
-
-Note:
-
-- This connector circuit is for internal testing only; please design the circuit according to your needs for actual use.
-
-### Low-Speed Subsystem Circuit
-
-#### I2C Circuit
-
-The K230 chip supports 5 I2C interfaces with the following features:
-
-- Supports I2C bus master mode.
-- Supports 7/10-bit addresses.
-- Supports I2C rates up to 3.4Mbit/s.
-
-When using I2C peripherals, pay attention to the corresponding power domain supply, which must be consistent. The SCL and SDA signals of the I2C need external pull-up resistors. Choose different resistor values based on bus load and bus rate.
-
-- For systems not exceeding 400kb/s, the recommended resistor value is 4.7kΩ.
-- For systems exceeding 400kb/s but less than 3.4Mb/s, the recommended pull-up resistor is 2.2kΩ.
-
-#### UART Circuit
-
-The K230 supports 5 UART signals with the following features:
-
-- Supports 2-wire UART and 4-wire UART.
-- Supports RS485 interface.
-- Supports baud rates up to 3.125M.
-- Supports software and hardware flow control, compliant with the 16750 standard.
-- Supports IrDA 1.0 SIR reception.
-
-When using UART peripherals, pay attention to the corresponding power domain supply, which must be consistent.
-
-#### PWM Circuit
-
-The K230 supports 6 PWM signals with the following features:
-
-- Supports arbitrary duty cycle.
-- Supports programmable output waveform.
-- Supports generating periodic pulse signals and one-time pulse signals.
-- Can be used as a periodic accurate interrupt generator.
-- Supports output glitch elimination.
-
-#### MCLK Circuit
-
-The K230 supports outputting 3 MCLK signals. This signal can be used as the driving clock for cameras.
-
-### MCLK Circuit
-
-Supports output clock frequencies as shown in Table 3-4:
-
-|        |        |      |      |      |      |      |      |
-| :----: | :----: | :---: | :---: | :---: | :---: | :---: | :---: |
-|  792   |  132   | 66.67 | 46.59 |  36  | 28.57 | 23.76 | 18.56 |
-|  594   | 118.8  |  66   | 45.69 | 34.94 | 28.29 | 23.53 | 18.18 |
-|  400   | 113.14 |  66   | 44.44 | 34.43 | 28.29 | 22.85 | 17.39 |
-|  396   |  100   | 60.92 |  44   | 33.33 | 27.31 | 22.22 | 16.67 |
-|  297   |   99   | 59.4  | 42.43 |  33  |  27   |  22   |  16   |
-|  264   |   99   | 57.14 | 41.68 |  33  | 26.67 | 21.21 | 15.38 |
-|  200   |   88   | 56.57 |  40   | 31.68 | 26.4  | 21.05 | 14.81 |
-|  198   | 84.86  |  54   | 39.6  | 31.26 | 25.83 | 20.48 | 14.29 |
-|  198   |   80   | 52.8  | 39.6  | 30.77 | 25.55 |  20   | 13.79 |
-| 158.4  |  79.2  |  50   | 37.71 | 30.46 |  25   | 19.8  | 13.33 |
-| 148.5  | 74.25  | 49.5  | 37.13 | 29.7  | 24.75 | 19.16 | 12.9  |
-| 133.33 |   72   | 49.5  | 36.36 | 29.33 | 24.75 | 19.05 | 12.5  |
-
-Table 3-4 MCLK Output Clock Frequencies (in MHz)
-
-#### ADC Circuit
-
-The K230 integrates an 11-bit (effective resolution) SAR ADC with a maximum sampling rate of no less than 1MHz. It has the following features:
-
-- Signal input range: 0-1.8V
-- Supports 6-channel input
-- Supports single sampling and continuous sampling
-- Internally integrated signal conditioning circuit with a cutoff frequency at half the bandwidth. The ADC can directly sample signals or design peripheral circuits as needed.
-
-#### PMU Circuit
-
-The PMU module of the K230 is used to control and manage internal and external power supplies of the chip. It has a built-in RTC circuit and supports 6 input channels. Its functions are shown in the table below:
-
-| Interrupt Source | Edge Trigger | Level Trigger | Debounce | Edge Count Detection | Long/Short Press Detection |
-| :--------------: | :----------: | :-----------: | :------: | :------------------: | :-----------------------: |
-|      INT_0       |     Yes      |      Yes      |    Yes   |          -           |           Yes             |
-|      INT_1       |     Yes      |      Yes      |    Yes   |         Yes          |            -              |
-|      INT_2       |     Yes      |      Yes      |     -    |          -           |            -              |
-|      INT_3       |     Yes      |      Yes      |     -    |          -           |            -              |
-|      INT_4       |      -       |      Yes      |     -    |          -           |            -              |
-|      INT_5       |      -       |      Yes      |     -    |          -           |            -              |
-
-Supports two output channels OUT0 and OUT1, which can be used to enable power supplies. In a cold start state, the PMU only enables the long press interrupt of INT0 and the high-level input interrupt of INT4 as triggers for PMU module startup. OUT0 and OUT1 default to low level with an initial pull-down resistance of about 40Ω. Upon receiving either of these two interrupts, OUT0 is pulled high, and OUT1 is pulled high after approximately 50ms. OUT0 and OUT1 can be used to control the enable pins of external PMICs or for other purposes.
-
-### Power Design
-
-#### K230 Power Requirements
-
-| Module         | Power Pin         | Description                                                   |
-| -------------- | ----------------- | ------------------------------------------------------------- |
-| CORE           | VDD0P8_CORE       | Power for CPU0 and other units                                |
-| CPU            | VDD0P8_CPU        | Power for CPU1                                                |
-| KPU            | VDD0P8_KPU        | Power for KPU                                                 |
-| DDR Controller | VDD0P8_DDR_CORE   | Digital CORE power for DDR, can be powered off                |
-|                | VDD1P1_DDR_IO     | IO power for DDR                                              |
-|                | VAA_DDR           | PLL power for DDR                                             |
-| USB            | AVDD3P3_USB       | 3.3V power for USB PHY, can be left unpowered if not in use   |
-|                | AVDD1P8_USB       | 1.8V power for USB PHY, can be left unpowered if not in use   |
-| PLL            | AVDD0P8_PLL       | Power for PLL                                                 |
-| MIPI           | AVDD0P8_MIPI      | 0.8V power for MIPI, can be left unpowered if not in use      |
-|                | AVDD1P8_MIPI      | 1.8V power for MIPI, can be left unpowered if not in use      |
-| VDD1P8         | VDD1P8            | 1.8V module power                                             |
-| ADC            | AVDD1P8_ADC       | Power for ADC, can be left unpowered if not in use            |
-| CODEC          | AVDD1P8_CODEC     | Power for CODEC, can be left unpowered if not in use          |
-| PMU            | AVDD1P8_RTC       | RTC power for PMU, can be left unpowered if not in use        |
-|                | AVDD1P8_LDO       | LDO power for PMU, can be left unpowered if not in use        |
-| MMC            | VDD3P3_SD         | 3.3V output buffer and pre-buffer IO power, can be left unpowered if not in use |
-| IO             | VDDIO3P3_0        | IO power for IO_2-IO_13, voltage selectable between 1.8V or 3.3V, can be left unpowered if not in use |
-|                | VDDIO3P3_1        | IO power for IO_14-IO_25, voltage selectable between 1.8V or 3.3V, can be left unpowered if not in use |
-|                | VDDIO3P3_2        | IO power for IO_26-IO_37, voltage selectable between 1.8V or 3.3V, can be left unpowered if not in use |
-|                | VDDIO3P3_3        | IO power for IO_38-IO_49, voltage selectable between 1.8V or 3.3V, can be left unpowered if not in use |
-|                | VDDIO3P3_4        | IO power for IO_50-IO_61, voltage selectable between 1.8V or 3.3V, can be left unpowered if not in use |
-|                | VDDIO3P3_5        | IO power for IO_62-IO_63, voltage selectable between 1.8V or 3.3V, can be left unpowered if not in use |
-| K230D DDR Part | VDD1P8_DDR_VDD1   | DDR power in K230D, not present in K230                       |
-|                | VDD1P1_DDR_VDD2   | DDR power in K230D, not present in K230, cannot be powered off |
-|                | VDD1P1_DDR_VDDQ   | DDR power in K230D, not present in K230, can be powered off   |
-
-Table 3-6 K230 Power Requirements
-
-#### Power-Up Sequence
-
-VDD0P8_CORE must be powered up earlier than VDD1P8 and VDDIO3P3_0 to VDDIO3P3_5 IO interfaces. AVDD0P8_MIPI must be powered up earlier than AVDD1P8_MIPI, and AVDD1P8_RTC must not be powered up later than AVDD1P8_LDO. There are no other specific power-up sequence requirements.
-
-#### Power Design Recommendations
-
-##### PMU
-
-| Module Name | Pin          | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                      |
-| ----------- | ------------ | --------------- | ------------------- | --------------- | ------------ | ------------------------- |
-| PMU         | AVDD1P8_RTC  | 1.674            | 1.8                 | 1.98            | 10           | Recommended to use LDO    |
-|             | AVDD1P8_LDO  | 1.674            | 1.8                 | 1.98            | 10           | Recommended to use LDO    |
-
-##### Core Modules
-
-| Module Name | Pin          | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                                              |
-| ----------- | ------------ | --------------- | ------------------- | --------------- | ------------ | -------------------------------------------------- |
-| CORE        | VDD0P8_CORE  | 0.72             | 0.8                 | 0.88            | 2250         | Recommended to use a DC/DC with at least 3A capacity and low ripple noise |
-| CPU         | VDD0P8_CPU   | 0.72             | 0.8                 | 0.88            | 1000         | Recommended to use a DC/DC with at least 2A capacity and low ripple noise |
-| KPU         | VDD0P8_KPU   | 0.72             | 0.8                 | 0.88            | 3000         | Recommended to use a DC/DC with at least 4A capacity and low ripple noise |
-
-##### DDR
-
-| Module Name | Pin                  | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                                              |
-| ----------- | -------------------- | --------------- | ------------------- | --------------- | ------------ | -------------------------------------------------- |
-| DDR         | VDD0P8_DDR_CORE      | 0.744            | 0.8                 | 0.88            | 400          | Power ripple requirement within 4%, recommended to use a low noise LDO capable of high current output |
-|             | VDD1P1_DDR_IO (LPDDR4) | 1.06             | 1.1                 | 1.17            | 800          | LP4 ripple requirement within 5%, recommended to use a low noise LDO capable of high current output |
-|             | VDD1P1_DDR_IO (LPDDR3) | 1.14             | 1.2                 | 1.3             | 800          | LP3 ripple requirement within 10%, recommended to use a low noise LDO capable of high current output |
-|             | VAA_DDR              | 1.674            | 1.8                 | 1.98            | 10           | Ripple requirement within 5% of typical voltage    |
-
-##### K230D DDR Die
-
-| Module Name      | Pin            | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                                                        |
-| ---------------- | -------------- | --------------- | ------------------- | --------------- | ------------ | ------------------------------------------------------------ |
-| K230D DDR die    | VDD1P8_DDR_VDD1 | 1.7              | 1.8                 | 1.95            | 75           | Ripple requirement within 5% of typical voltage, same power network as DDR controller |
-|                  | VDD1P1_DDR_VDD2 | 1.06             | 1.1                 | 1.17            | 450          | Same power network as VDD1P1_DDR_IO                          |
-|                  | VDD1P1_DDR_VDDQ | 1.06             | 1.1                 | 1.17            | 300          | Recommended to use a low noise LDO capable of high current output |
-
-##### I/O
-
-| Module Name | Pin         | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                                                                                                               |
-| ----------- | ----------- | --------------- | ------------------- | --------------- | ------------ | -------------------------------------------------------------------------------------------------------------------- |
-| IO          | VDDIO3P3_0  | 1.62/2.97       | 1.8/3.3             | 1.98/3.63       | 50           | IO units have 5 voltage groups, each configurable to 1.8V or 3.3V. Each group controls the output and input voltage of the corresponding I/O ports and their multiplexed functions. The IO voltage should match the connected peripherals; if not, level shifting is required. |
-|          | VDDIO3P3_1 | 1.62/2.97   | 1.8/3.3      | 1.98/3.63   | 50        |                                                                                                                                                                                            |
-|          | VDDIO3P3_2 | 1.62/2.97   | 1.8/3.3      | 1.98/3.63   | 50        |                                                                                                                                                                                            |
-|          | VDDIO3P3_3 | 1.62/2.97   | 1.8/3.3      | 1.98/3.63   | 50        |                                                                                                                                                                                            |
-|          | VDDIO3P3_4 | 1.62/2.97   | 1.8/3.3      | 1.98/3.63   | 50        |                                                                                                                                                                                            |
-|          | VDDIO3P3_5 | 1.62/2.97   | 1.8/3.3      | 1.98/3.63   | 50        |                                                                                                                                                                                            |
-
-##### USB
-
-| Module Name | Pin          | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                     |
-| ----------- | ------------ | --------------- | ------------------- | --------------- | ------------ | ------------------------- |
-| USB         | AVDD3P3_USB  | 3.07            | 3.3                 | 3.63            | 50           | Recommended to use LDO    |
-|             | AVDD1P8_USB  | 1.674           | 1.8                 | 1.98            | 60           | Recommended to use LDO    |
-
-##### PLL
-
-| Module Name | Pin          | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                             |
-| ----------- | ------------ | --------------- | ------------------- | --------------- | ------------ | --------------------------------- |
-| PLL         | AVDD0P8_PLL  | 0.72            | 0.8                 | 0.88            | 120          | Recommended to use high-precision LDO |
-
-##### MIPI
-
-| Module Name | Pin           | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                     |
-| ----------- | ------------- | --------------- | ------------------- | --------------- | ------------ | ------------------------- |
-| MIPI        | AVDD0P8_MIPI  | 0.744           | 0.8                 | 0.88            | 100          | Recommended to use LDO    |
-|             | AVDD1P8_MIPI  | 1.674           | 1.8                 | 1.98            | 30           | Recommended to use LDO    |
-
-##### ADC
-
-| Module Name | Pin          | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                             |
-| ----------- | ------------ | --------------- | ------------------- | --------------- | ------------ | --------------------------------- |
-| ADC         | AVDD1P8_ADC  | 1.62            | 1.8                 | 1.98            | 10           | Recommended to use high-precision LDO |
-
-##### CODEC
-
-| Module Name | Pin            | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes                             |
-| ----------- | -------------- | --------------- | ------------------- | --------------- | ------------ | --------------------------------- |
-| CODEC       | AVDD1P8_CODEC  | 1.62            | 1.8                 | 1.98            | 100          | Recommended to use high-precision LDO |
-
-##### Others
-
-| Module Name | Pin         | Min Voltage (V) | Typical Voltage (V) | Max Voltage (V) | Current (mA) | Notes |
-| ----------- | ----------- | --------------- | ------------------- | --------------- | ------------ | ----- |
-| Others      | VDD3P3_SD   | 2.7             | 3.3                 | 3.63            | 50           |       |
-|             | VDD1P8      | 1.62            | 1.8                 | 1.98            | 500          |       |
-
-Note:
-
-- For the DDR chips used by the K230, the power supply must be on the same power network as the main chip.
-- Modules with the same voltage requirements can use the same power source if the voltage accuracy and current requirements are met. For applications with low precision requirements, analog modules like ADCs can also be connected to the power source used by digital modules after isolation.
-- The K230 integrates a DDR_Vref power supply for the chip's DDR controller. For external chips, the reference design for the LPDDR3 VREF power supply is shown in Figure 3-39.
-
-![Figure 3-39 LPDDR3 Chip Vref Circuit](../../zh/00_hardware/images/HDG/image051.png)
-Figure 3-39 LPDDR3 Chip Vref Circuit
-
-It is recommended to use resistors with an accuracy of ±1%. The reference design for the external LPDDR4 VREF power supply is shown in Figure 3-40.
-
-![Figure 3-40 LPDDR4 Chip Vref Circuit](../../zh/00_hardware/images/HDG/image052.png)
-Figure 3-40 LPDDR4 Chip Vref Circuit
-
-The reference design for the K230D DDR module VREF power supply is shown in Figure 3-41.
-
-![Figure 3-41 K230D Version DDR Vref Circuit](../../zh/00_hardware/images/HDG/image053.png)
-Figure 3-41 K230D Version DDR Vref Circuit
-
-#### Dynamic Voltage Scaling
-
-The power supplies for the CPU and KPU in the K230 support dynamic voltage scaling to ensure high performance and low power consumption. The adjustable voltage nodes for the CPU are shown in Table 3-7.
-
-| Voltage Node | Voltage (V) |
-| ------------ | ----------- |
-| V_typical    | 0.8         |
-| V_high       | 0.9         |
-| V_ultrahigh  | 1.0         |
-| V_low        | 0.7         |
-| V_retention  | 0.48        |
-
-Table 3-7 CPU Adjustable Voltage Nodes
-
-Among them, V_retention is the voltage node for the DDR retention function. The adjustable voltage nodes for the KPU are shown in Table 3-8.
-
-| Voltage Node | Voltage (V) |
-| ------------ | ----------- |
-| V_typical    | 0.8         |
-| V_high       | 0.9         |
-| V_ultrahigh  | 1.0         |
-| V_low        | 0.7         |
-
-Table 3-8 KPU Adjustable Voltage Nodes
-
-## PCB Design Recommendations
-
-### High-Speed PCB Design Recommendations
-
-#### DDR Design
-
-Impedance Control: Single-ended DDR 50Ω, Differential (clock clk, data dqs) 100Ω;
-Crosstalk Requirements: Follow the 3W rule;
-Length Matching Requirements: Ensure the same number of vias for the same type of signal lines, and avoid more than 2 layer changes for vias;
-The internal DDR routing length of the chip is shown in Table 4-1. When routing on the PCB, ensure that the total length of internal and external routing meets the length matching requirements.
-It is strongly recommended to refer to the design of the K230 EVB, including routing and capacitor selection and placement.
-
-**Pin Length Table**:
-
-| Pin Number | Pin Name           | Length (μm) | Length (mil) |
-|------------|--------------------|-------------|--------------|
-| N17        | DDR_CKE0_CKEA0     | 3725.8      | 146.8        |
-| P18        | DDR_CKE1_CKEA1     | 4338.56     | 170.94       |
-| T20        | DDR_CS0_CSA0       | 5839.03     | 230.06       |
-| T19        | DDR_CS1_CSA1       | 5528.07     | 217.81       |
-| R19        | DDR_CKP_CKAP       | 6252.24     | 246.34       |
-| R20        | DDR_CKN_CKAN       | 6050.13     | 238.38       |
-| P19        | DDR_CA9_CAA5       | 5809.3      | 228.89       |
-| M18        | DDR_CA8_CAA4       | 4033.87     | 158.93       |
-| N20        | DDR_CA7_CAA3       | 4888.23     | 192.6        |
-| N19        | DDR_CA6_CAA2       | 4415.08     | 173.95       |
-| L16        | DDR_CA5_CAA1       | 2171.4      | 85.55        |
-| M19        | DDR_CA4_CAA0       | 4599.65     | 181.23       |
-| L17        | DDR_CA3_NC         | 2258.98     | 89           |
-| M20        | DDR_CA2_NC         | 4190.42     | 165.1        |
-| L20        | DDR_CA1_NC         | 5108.55     | 201.28       |
-| K20        | DDR_CA0_NC         | 4832.33     | 190.39       |
-| L18        | DDR_ODT_NC         | 3849.11     | 151.65       |
-| J18        | DDR_NC_CKEB0       | 2599.43     | 102.42       |
-| J17        | DDR_NC_CKEB1       | 2792.84     | 110.04       |
-| J19        | DDR_NC_CSB1        | 4018.49     | 158.33       |
-| J20        | DDR_NC_CSB0        | 4941.35     | 194.69       |
-| G20        | DDR_NC_CLKBP       | 5403.63     | 212.9        |
-| F20        | DDR_NC_CLKBN       | 5418.33     | 213.48       |
-| E20        | DDR_NC_CAB0        | 5468.25     | 215.45       |
-| G19        | DDR_NC_CAB1        | 4067.91     | 160.28       |
-| G18        | DDR_NC_CAB2        | 3807.29     | 150.01       |
-| H17        | DDR_NC_CAB3        | 3113.45     | 122.67       |
-| F17        | DDR_NC_CAB4        | 2757.73     | 108.65       |
-| F19        | DDR_NC_CAB5        | 4558.27     | 179.6        |
-| U17        | DDR_DQ24_DQA7      | 4829.45     | 190.28       |
-| Y18        | DDR_DQ25_DQA6      | 6467.43     | 254.82       |
-| V18        | DDR_DQ26_DQA5      | 5047.5      | 198.87       |
-| W18        | DDR_DQ27_DQA4      | 5267.44     | 207.54       |
-| Y16        | DDR_DQ28_DQA3      | 5846.86     | 230.37       |
-| V16        | DDR_DQ29_DQA2      | 4311.64     | 169.88       |
-| T16        | DDR_DQ30_DQA1      | 3576.39     | 140.91       |
-| U16        | DDR_DQ31_DQA0      | 3132.83     | 123.43       |
-| V17        | DDR_DM3_DMIA0      | 4110.44     | 161.95       |
-| W17        | DDR_DQS3P_DQSA0P   | 6342.48     | 249.89       |
-| Y17        | DDR_DQS3N_DQSA0N   | 6135.17     | 241.73       |
-| R17        | DDR_DQ8_DQA8       | 4018.24     | 158.32       |
-| T18        | DDR_DQ9_DQA9       | 5760.1      | 226.95       |
-| R18        | DDR_DQ10_DQA10     | 4540.62     | 178.9        |
-| U20        | DDR_DQ11_DQA11     | 5625.11     | 221.63       |
-| W19        | DDR_DQ12_DQA12     | 6897.92     | 271.78       |
-| U18        | DDR_DQ13_DQA13     | 4908.14     | 193.38       |
-| P16        | DDR_DQ14_DQA14     | 2036.92     | 80.25        |
-| T17        | DDR_DQ15_DQA15     | 4492.07     | 176.99       |
-| P17        | DDR_DM1_DMIA1      | 4129.14     | 162.69       |
-| V20        | DDR_DQS1P_DQSA1P   | 7005.11     | 276          |
-| V19        | DDR_DQS1N_DQSA1N   | 6768.98     | 266.7        |
-| C17        | DDR_DQ0_DQB15      | 4038.16     | 159.1        |
-| D16        | DDR_DQ1_DQB14      | 3663.33     | 144.34       |
-| D17        | DDR_DQ2_DQB13      | 4242.29     | 167.15       |
-| C18        | DDR_DQ3_DQB12      | 5598.19     | 220.57       |
-| E18        | DDR_DQ4_DQB11      | 3830.51     | 150.92       |
-| E17        | DDR_DQ5_DQB10      | 4273.06     | 168.36       |
-| B19        | DDR_DQ6_DQB9       | 6879.01     | 271.03       |
-| C19        | DDR_DQ7_DQB8       | 6640.84     | 261.65       |
-| D18        | DDR_DM0_DMIB0      | 5275.38     | 207.85       |
-| B18        | DDR_DQS0P_DQSB1P   | 6516.79     | 256.76       |
-| A18        | DDR_DQS0N_DQSB1N   | 6628.66     | 261.17       |
-| C14        | DDR_DQ16_DQB0      | 2966.98     | 116.9        |
-| D14        | DDR_DQ17_DQB1      | 2708.03     | 106.7        |
-| B14        | DDR_DQ18_DQB2      | 4486.79     | 176.78       |
-| A14        | DDR_DQ19_DQB3      | 5608.52     | 220.98       |
-| A17        | DDR_DQ20_DQB4      | 5037.71     | 198.49       |
-| B16        | DDR_DQ21_DQB5      | 4419.48     | 174.13       |
-| C16        | DDR_DQ22_DQB6      | 4381.95     | 172.65       |
-| B17        | DDR_DQ23_DQB7      | 5515.88     | 217.33       |
-| C15        | DDR_DM2_DMIB1      | 4509.87     | 177.69       |
-| B15        | DDR_DQS2P_DQSB1P   | 4623.9      | 182.18       |
-| A15        | DDR_DQS2N_DQSB1N   | 4942.59     | 194.74       |
-
-Table 4-1 Internal DDR Trace Lengths
-
-Within LPDDR3 byte groups, DQ can be swapped, but DQ swapping is not supported between bytes or between byte groups. For LPDDR4, DQ can be swapped within byte groups, DQ swapping is not supported between bytes, but byte swapping within channel groups is supported.
-
-It is recommended to follow the EVB swap order for routing. If you modify the swap during your own design, you need to adjust the DDR training code. Please contact FAE in advance.
-
-![Figure 4-1 DDR Trace Spacing Design Rules](../../zh/00_hardware/images/HDG/image054.png)
-Figure 4-1 DDR Trace Spacing Design Rules
-
-Figures 4-2 and 4-3 show the length matching design requirements for LPDDR3 and LPDDR4 respectively. To ensure stable operation at higher speeds, it is recommended to design according to the requirements listed under "Recommended Routed Skew Limits".
-
-**LPDDR3 Section**:
-
-![Figure 4-2 LPDDR3 Length Matching Design Rules](../../zh/00_hardware/images/HDG/image055.png)
-Figure 4-2 LPDDR3 Length Matching Design Rules
-
-**LPDDR4 Section**:
-
-![Figure 4-3 LPDDR4 Length Matching Design Rules](../../zh/00_hardware/images/HDG/image056.png)
-Figure 4-3 LPDDR4 Length Matching Design Rules
-
-#### USB 2.0 Design
-
-- Impedance Control: Differential 90Ω.
-- Skew within the differential pair should not exceed 4ps, with a maximum of 6 vias allowed.
-
-#### MIPI Design
-
-- Impedance Control: MIPI_DSI differential 100Ω, MIPI_CSI differential 100Ω.
-- Length matching within the pair should be controlled within 0.3mm.
diff --git a/components/canaan/k230/artifacts/K230_PMU_User_Guide.md b/components/canaan/k230/artifacts/K230_PMU_User_Guide.md
deleted file mode 100644
index c5c184d..0000000
--- a/components/canaan/k230/artifacts/K230_PMU_User_Guide.md
+++ /dev/null
@@ -1,283 +0,0 @@
-# K230 PMU User Guide
-
-![cover](../../../../zh/images/canaan-cover.png)
-
-Copyright 2023 Canaan Inc. ©
-
-<div style="page-break-after:always"></div>
-
-## Disclaimer
-
-The products, services or features you purchase should be subject to Canaan Inc. ("Company", hereinafter referred to as "Company") and its affiliates are bound by the commercial contracts and terms and conditions of all or part of the products, services or features described in this document may not be covered by your purchase or use. Unless otherwise agreed in the contract, the Company does not provide any express or implied representations or warranties as to the correctness, reliability, completeness, merchantability, fitness for a particular purpose and non-infringement of any statements, information, or content in this document. Unless otherwise agreed, this document is intended as a guide for use only.
-
-Due to product version upgrades or other reasons, the content of this document may be updated or modified from time to time without any notice.
-
-## Trademark Notice
-
-![The logo](../../../../zh/images/logo.png), "Canaan" and other Canaan trademarks are trademarks of Canaan Inc. and its affiliates. All other trademarks or registered trademarks that may be mentioned in this document are owned by their respective owners.
-
-**Copyright 2023 Canaan Inc.. © All Rights Reserved.**
-Without the written permission of the company, no unit or individual may extract or copy part or all of the content of this document without authorization, and shall not disseminate it in any form.
-
-<div style="page-break-after:always"></div>
-
-## Directory
-
-[TOC]
-
-## preface
-
-### Overview
-
-This document describes the specific usage methods of PMU modules and SDK configuration compilation methods, including the construction of software and hardware environments, and introduces the control interface.
-
-### Reader object
-
-This document (this guide) is intended primarily for:
-
-- Technical Support Engineer
-- Software Development Engineer
-
-### Definition of acronyms
-
-| abbreviation | illustrate |
-| --- | --- |
-| PMU | Power Management Unit |
-
-### Revision history
-
-| Document version number | Modify the description | Author | date |
-| --- | --- | --- | --- |
-| V1.0 | Initial edition | Zhang Tao | 2023/05/19 |
-
-## Function introduction
-
-The PMU module provides 6 input and 2 output ports, each with the following functions:
-
-1. INT0 is used as the power on and off button by default, supporting long press to power on, long press shutdown event reporting, long press forced shutdown, level or edge event reporting, support debounce, two long press times can be matched
-1. INT1 supports level or edge detection, edge count detection, both support triggering boot and reporting events, support debounce, and edge count values can be configured (it is recommended not to open both detection modes at the same time, the edge detection function will be overridden)
-1. INT2 supports level or edge detection, triggers power-on and report events, and debounces
-1. INT3 supports level or edge detection, triggers power-on and escalation events, and debounces
-1. INT4 supports level or edge detection, triggering power-on and reporting events (edge detection recommended)
-1. INT5 supports level or edge detection, triggering power-on and reporting events (edge detection recommended)
-1. OUTPUT0 is used to control PMICs
-1. OUTPUT1 not used yet
-
-The PMU module also provides a log storage function of 64Byte, of which the last 4Byte is used by the driver and the remaining 60Byte is left to the user
-
-## User Control
-
-The PMU can be controlled by the user through the device tree and sysfs, the PMU can be configured through the device tree at system startup, and the PMU can be dynamically configured through sysfs after startup
-
-### PMU Device Tree Configuration
-
-```c
-pmu: pmu@0x91000000 {
-    compatible = "kendryte, k230-pmu";
-    reg = <0x0 0x91000000 0x0 0xb0>;
-    interrupt-parent = <&intc>;
-    interrupts = <175>;
-    status = "disabled";
-    /*
-    int0 {
-        force-powerdown-value = <320000>;
-        power-event-value = <96000>;
-        debounce-value = <256>;
-        type = <IRQ_TYPE_EDGE_RISING>;
-        wakeup;
-        event;
-    };
-    int1 {
-        debounce-value = <256>;
-        edge-cnt-type = <IRQ_TYPE_EDGE_RISING>;
-        edge-cnt-value = <1>;
-        edge-cnt-wakeup;
-        edge-cnt-event;
-        type = <IRQ_TYPE_EDGE_RISING>;
-        wakeup;
-        event;
-    };
-    int2 {
-        debounce-value = <256>;
-        type = <IRQ_TYPE_EDGE_RISING>;
-        wakeup;
-        event;
-    };
-    int3 {
-        debounce-value = <256>;
-        type = <IRQ_TYPE_EDGE_RISING>;
-        wakeup;
-        event;
-    };
-    int4 {
-        type = <IRQ_TYPE_EDGE_FALLING>;
-        wakeup;
-        event;
-    };
-    int5 {
-        type = <IRQ_TYPE_EDGE_RISING>;
-        wakeup;
-        event;
-    };
-    rtc {
-        alarm-wakeup;
-        alarm-event;
-        tick-wakeup;
-        tick-event;
-    };
-    */
-};
-```
-
-Key field meanings:
-
-- `force-powerdown-value` Long press to force shutdown time
-- `power-event-value` Long press on and long press on the shutdown event time
-- `debounce-value` Debounce time
-- `type` Detection type, support rising edge, falling edge, high level, low level
-- `wakeup` Enable power-on to wake up red energy
-- `event` Enable event reporting
-- `edge-cnt-type` Detection type, support rising edge, falling edge
-- `edge-cnt-value` Edge count value
-
-All times are measured in (1/32768) seconds, e.g. 327680 for 10 seconds
-
-### PMU file control
-
-PMU sysfs is located in `/sys/devices/platform/soc/91000000.pmu`the directory and the file structure is as follows:
-
-```sh
-.
-|-- driver -> ../../../../bus/platform/drivers/k230-pmu
-|-- driver_override
-|-- int0
-|   |-- debounce_value
-|   |-- event
-|   |-- force_powerdown_value
-|   |-- power_event_value
-|   |-- type
-|   `-- wakeup
-|-- int1
-|   |-- debounce_value
-|   |-- edge_cnt_event
-|   |-- edge_cnt_type
-|   |-- edge_cnt_value
-|   |-- edge_cnt_wakeup
-|   |-- event
-|   |-- type
-|   `-- wakeup
-|-- int2
-|   |-- debounce_value
-|   |-- event
-|   |-- type
-|   `-- wakeup
-|-- int3
-|   |-- debounce_value
-|   |-- event
-|   |-- type
-|   `-- wakeup
-|-- int4
-|   |-- event
-|   |-- type
-|   `-- wakeup
-|-- int5
-|   |-- event
-|   |-- type
-|   `-- wakeup
-|-- modalias
-|-- of_node -> ../../../../firmware/devicetree/base/soc/pmu@0x91000000
-|-- pmu
-|   |-- pmu_logs
-|   |-- pmu_regs
-|   |-- pmu_status
-|   `-- wakeup_source
-|-- rtc
-|   |-- alarm_event
-|   |-- alarm_wakeup
-|   |-- tick_event
-|   `-- tick_wakeup
-|-- subsystem -> ../../../../bus/platform
-`-- uevent
-```
-
-Main file features:
-
-- `pmu/pmu_status` PMU Status (read-only)
-  - `PMU_RESET` The PMU is powered off
-  - `SOC_FORCE_PD` The SoC is forced to power down
-  - `SOC_NORMAL_PD` The SoC is powered off normally
-  - `SOC_RESET` The SoC is reset
-- `pmu/wakeup_source` system wakeup source (read-only)
-  INT0,INT1,INT2,INT3,INT4,INT5,RTC_ALARM,RTC_TICK
-- `pmu/pmu_logs` User LOG file (binary file, 4-byte alignment required for read and write)
-- `pmu/pmu_regs` PMU debugging (binary, 4-byte alignment required for read and write)
-- `int0/force_powerdown_value` Long press to force shutdown time
-- `int0/power_event_value` Long press on and long press on the shutdown event time
-- `int1/edge_cnt_type` Detection type, valid values "rising", "falling"
-- `int1/edge_cnt_value` Edge count value
-- `*/debounce_value` Debounce time
-- `*/type` Detection type, valid values "rising", "falling", "low", "high"
-- `*/*wakeup` Wake up, valid values "enabled", "disabled"
-- `*/*event` Event reported, valid values "enabled", "disabled"
-
-For example, enable INT1 rising edge to wake up:
-
-```sh
-cd /sys/devices/platform/soc/91000000.pmu/int1
-echo rising > type
-echo enabled > wakeup
-```
-
-For example, enable INT2 falling edge events to be reported:
-
-```sh
-cd /sys/devices/platform/soc/91000000.pmu/int2
-echo falling > type
-echo enabled > event
-```
-
-### PMU events are reported
-
-PMU uses the input subsystem to report events, and the reported event code is so `EV_KEY`that users can perform business processing after receiving the corresponding events. For example, after receiving`KEY_POWER` the key value, the user can perform shutdown preparation and invoke the`poweroff` shutdown command
-
-You can use the `evtest`tool for testing with the following event table:
-| action | Key value |
-| :-: | :-: |
-| INT0 Press and hold to shut down | KEY_POWER |
-| INT0 level or edge | BTN_0 |
-| INT1 level or edge or edge count | BTN_1 |
-| INT2 level or edge | BTN_2 |
-| INT3 level or edge | BTN_3 |
-| INT4 level or edge | BTN_4 |
-| INT5 level or edge | BTN_5 |
-| RTC_ALARM | BTN_6 |
-| RTC_TICK | BTN_7 |
-
-### PMU shutdown control
-
-1. Use `poweroff`the command shutdown
-1. Force shutdown by pressing the INT0 button long (not recommended unless the system is down. *Forced shutdown after system downtime will cause PMU to wake up*).
-
-## Hardware connection
-
-When using a PMU, you need to set up the EVB board as follows
-
-1. Use the jumper cap to connect PIN13(OUT0) and PIN14(PW_EN) of the J1 interface, taking care to disconnect PIN15(SYS_SW) and PIN16(PW_EN)
-1. Depending on the different wake-up source, PIN2 (SYS_ON_OFF) is connected to the corresponding PIN using a jumper, and the button K1 can control the state of INT, press the button to go high, and release it to low
-   | Wake source | PIN | label |
-   | :-: | :-: | :-: |
-   | INT0 | 1 | INT0 |
-   | INT1 | 3 | INT1 |
-   | INT2 | 5 | INT2 |
-   | INT3 | 7 | INT3 |
-   | INT4 | 9 | INT4 |
-   | INT5 | 11 | INT5 |
-
-Connection diagram using INT0 as a wake-up source:
-![top_view](../../../../zh/01_software/board/osdrv/images/pmu_hw_top_view.jpg)
-![bottom_view](../../../../zh/01_software/board/osdrv/images/pmu_hw_bottom_view.jpg)
-
-## Precautions
-
-1. The PMU module is not enabled by default in the device tree, if you need to use it, enable it in the device tree
-1. When using the PMU module, be sure to wake up the PMU module through any INT, otherwise the kernel will be stuck when initializing the driver
diff --git a/components/canaan/k230/artifacts/K230_RVV_In_Action.md b/components/canaan/k230/artifacts/K230_RVV_In_Action.md
deleted file mode 100644
index 0b699fb..0000000
--- a/components/canaan/k230/artifacts/K230_RVV_In_Action.md
+++ /dev/null
@@ -1,307 +0,0 @@
-# K230 RVV Practical Guide
-
-![cover](../../../zh/02_applications/tutorials/images/canaan-cover.png)
-
-Copyright © 2023 Canaan Creative Information Technology Co., Ltd.
-
-<div style="page-break-after:always"></div>
-
-## Disclaimer
-
-Your purchase of products, services, or features is subject to the commercial contracts and terms of Canaan Creative Information Technology Co., Ltd. (hereinafter referred to as "the Company") and its affiliates. All or part of the products, services, or features described in this document may not be within the scope of your purchase or use. Unless otherwise agreed in the contract, the Company does not provide any express or implied representations or warranties regarding the accuracy, reliability, completeness, merchantability, fitness for a particular purpose, or non-infringement of any statements, information, or content in this document. Unless otherwise agreed, this document is only for reference as a usage guide.
-
-Due to product version upgrades or other reasons, the content of this document may be updated or modified periodically without any notice.
-
-## Trademark Statement
-
-![logo](../../../zh/02_applications/tutorials/images/logo.png), "Canaan", and other Canaan trademarks are trademarks of Canaan Creative Information Technology Co., Ltd. and its affiliates. All other trademarks or registered trademarks mentioned in this document are owned by their respective owners.
-
-**Copyright © 2023 Canaan Creative Information Technology Co., Ltd. All rights reserved.**
-Without written permission from the Company, no unit or individual is allowed to excerpt, copy, or disseminate any part or all of the content of this document in any form.
-
-<div style="page-break-after:always"></div>
-
-## Overview
-
-RVV (RISC-V Vector Extension) refers to the vector extension of the RISC-V instruction set architecture. RISC-V is an open-source instruction set architecture known for its simplicity, scalability, and wide range of applications. RVV, as an optional extension of RISC-V, aims to support vector processing and parallel computing. RVV defines a set of new instructions for executing vector operations. These instructions allow multiple data elements to be processed simultaneously, thereby improving computational efficiency and throughput. Vector operations can be executed in a single instruction without needing loops or individual operations for each data element. RVV supports different vector lengths, which can be fixed or configurable based on application requirements. It also supports various data types, including integers, floating-point numbers, and fixed-point numbers.
-
-The introduction of RVV provides processors with vector processing and parallel computing capabilities, accelerating various applications such as image processing, signal processing, machine learning, and scientific computing. The openness and scalability of RVV also enable manufacturers and developers to customize and optimize according to their needs. The K230 uses the XuanTie C908 dual-core processor, with the larger core C908 featuring the RVV1.0 extension. This document describes how to use the RVV functionality on the larger core rt-smart and experience the performance acceleration brought by RVV.
-
-## Environment Preparation
-
-### Hardware Environment
-
-- K230-UNSIP-LP3-EVB-V1.0/K230-UNSIP-LP3-EVB-V1.1
-
-### Software Environment
-
-k230_SDK
-
-## Using RVV Functionality
-
-### Source Code Writing
-
-To experience the advantages of RVV in vector computation, we will use image scaling as an application scenario and write a demo. Create a folder in the following path of the SDK:
-
-`k230_sdk/src/big/rt-smart/userapps/testcases/scale`
-
-Note that running `make` or `make rt-smart` in the k230_sdk directory may overwrite your changes. You can copy the completed source code to the following directory:
-
-`k230_sdk/src/big/unittest/testcases`
-
-#### Source Code
-
-Create a C source file named `scale.c` in the scale directory:
-
-```c
-#include <stdio.h>
-#include <stdlib.h>
-#include <stddef.h>
-#include <stdint.h>
-#include <time.h>
-
-#pragma pack(push, 1)
-typedef struct {
-    unsigned short signature;
-    unsigned int fileSize;
-    unsigned short reserved1;
-    unsigned short reserved2;
-    unsigned int dataOffset;
-} BitmapFileHeader;
-
-typedef struct {
-    unsigned int headerSize;
-    int width;
-    int height;
-    unsigned short planes;
-    unsigned short bitsPerPixel;
-    unsigned int compression;
-    unsigned int imageSize;
-    int xPixelsPerMeter;
-    int yPixelsPerMeter;
-    unsigned int colorsUsed;
-    unsigned int colorsImportant;
-} BitmapInfoHeader;
-#pragma pack(pop)
-
-void __attribute__((optimize(3)))
-scaleBMP(const char* inputPath, const char* outputPath, float scaleFactor) {
-    // Read input BMP file
-    FILE* inputFile = fopen(inputPath, "rb");
-    if (inputFile == NULL) {
-        printf("Failed to open input BMP file.\n");
-        return;
-    }
-
-    BitmapFileHeader fileHeader;
-    BitmapInfoHeader infoHeader;
-    fread(&fileHeader, sizeof(BitmapFileHeader), 1, inputFile);
-    fread(&infoHeader, sizeof(BitmapInfoHeader), 1, inputFile);
-
-    int originalWidth = infoHeader.width;
-    int originalHeight = infoHeader.height;
-    int originalImageSize = infoHeader.imageSize;
-
-    unsigned char* originalImageData = (unsigned char*) malloc(originalImageSize);
-    fread(originalImageData, originalImageSize, 1, inputFile);
-    fclose(inputFile);
-
-    // Calculate scaled image dimensions
-    int scaledWidth = (int)(originalWidth * scaleFactor);
-    int scaledHeight = (int)(originalHeight * scaleFactor);
-    int scaledImageSize = scaledWidth * scaledHeight * 3;
-
-    // Create output BMP file
-    FILE* outputFile = fopen(outputPath, "wb");
-    if (outputFile == NULL) {
-        printf("Failed to create output BMP file.\n");
-        free(originalImageData);
-        return;
-    }
-
-    // Update BMP file header information
-    fileHeader.fileSize = sizeof(BitmapFileHeader) + sizeof(BitmapInfoHeader) + scaledImageSize;
-    infoHeader.width = scaledWidth;
-    infoHeader.height = scaledHeight;
-    infoHeader.imageSize = scaledImageSize;
-    fwrite(&fileHeader, sizeof(BitmapFileHeader), 1, outputFile);
-    fwrite(&infoHeader, sizeof(BitmapInfoHeader), 1, outputFile);
-
-    clock_t start, finish;
-    start = clock();
-    // Scale image data
-    unsigned char* scaledImageData = (unsigned char*) malloc(scaledImageSize);
-    for (int y = 0; y < scaledHeight; y++) {
-        for (int x = 0; x < scaledWidth; x++) {
-            int originalX = (int)(x / scaleFactor);
-            int originalY = (int)(y / scaleFactor);
-            scaledImageData[(y * scaledWidth + x) * 3 + 0] = originalImageData[(originalY * originalWidth + originalX) * 3 + 0];
-            scaledImageData[(y * scaledWidth + x) * 3 + 1] = originalImageData[(originalY * originalWidth + originalX) * 3 + 1];
-            scaledImageData[(y * scaledWidth + x) * 3 + 2] = originalImageData[(originalY * originalWidth + originalX) * 3 + 2];
-        }
-    }
-    finish = clock();
-    printf("scale calc use time:%f ms\n", (double)(finish - start) / CLOCKS_PER_SEC);
-
-    // Write the scaled image data
-    fwrite(scaledImageData, scaledImageSize, 1, outputFile);
-    fclose(outputFile);
-
-    free(originalImageData);
-    free(scaledImageData);
-
-    printf("BMP image scaling completed.\n");
-}
-
-int main() 
-{
-    const char* inputPath = "input.bmp";
-    const char* outputPath = "output.bmp";
-    float scaleFactor = 0.5; // Scaling factor
-    scaleBMP(inputPath, outputPath, scaleFactor);
-    return 0;
-}
-```
-
-#### SCONS Configuration File
-
-- Create SConscript file
-
-```python
-# RT-Thread building script for component
-
-from building import *
-
-cwd = GetCurrentDir()
-src = Glob('*.c')
-CPPPATH = [cwd]
-
-CPPDEFINES = [
-    'HAVE_CCONFIG_H',
-]
-group = DefineGroup('scale', src, depend = [''], CPPPATH = CPPPATH, CPPDEFINES = CPPDEFINES)
-
-Return('group')
-```
-
-- Create SConstruct file
-
-```python
-import os
-import sys
-
-# add building.py path
-sys.path = sys.path + [os.path.join('..','..','..','tools')]
-from building import *
-
-BuildApplication('scale', 'SConscript', usr_root = '../../..')
-```
-
-### Compilation
-
-Enter the directory `src/big/rt-smart` and run the script `source smart-env.sh riscv64` to configure the environment variables.
-
-```shell
-$ source smart-env.sh riscv64
-Arch         => riscv64
-CC           => gcc
-PREFIX       => riscv64-unknown-linux-musl-
-EXEC_PATH    => /home/testUser/k230_sdk/src/big/rt-smart/../../../toolchain/riscv64-linux-musleabi_for_x86_64-pc-linux-gnu/bin
-```
-
-Enter the `userapps/testcases/scale` directory and run `scons --release` to compile.
-
-```shell
-$ cd userapps/testcases/scale
-$ scons --release
-scons: Reading SConscript files ...
-scons: done reading SConscript files.
-scons: Building targets ...
-scons: building associated VariantDir targets: build/scale
-CC build/scale/scale.o
-LINK scale.elf
-/home/haohaibo/work/k230_sdk/toolchain/riscv64-linux-musleabi_for_x86_64-pc-linux-gnu/bin/../lib/gcc/riscv64-unknown-linux-musl/12.0.1/../../../../riscv64-unknown-linux-musl/bin/ld: warning: scale.elf has a LOAD segment with RWX permissions
-scons: done building targets.
-```
-
-Rename the compiled program
-
-```shell
-mv scale.elf scale_with_rvv.elf
-```
-
-Edit the `k230_sdk/src/big/rt-smart/tools/riscv64.py` file to remove the v extension from the compilation options.
-
-```diff
-$:k230_sdk/src/big/rt-smart/userapps/testcases/scale$ git diff
-diff --git a/tools/riscv64.py b/tools/riscv64.py
-index 16fc9b2..c045bf5 100644
---- a/tools/riscv64.py
-+++ b/tools/riscv64.py
-@@ -44,7 +44,7 @@ class ARCHRISCV64():
-                 EXT_CFLAGS = ''
-                 EXT_LFLAGS = ''
-
--            DEVICE = ' -mcmodel=medany -march=rv64imafdcv -mabi=lp64d'
-+            DEVICE = ' -mcmodel=medany -march=rv64imafdc -mabi=lp64d'
-             self.CFLAGS    = configuration.get('CFLAGS', DEVICE + ' -Werror -Wall' + EXT_CFLAGS)
-             self.AFLAGS    = configuration.get('AFLAGS', ' -c' + DEVICE + ' -x assembler-with-cpp -D__ASSEMBLY__ -I.' + EXT_CFLAGS)
-             LINK_SCRIPT    = configuration.get('LINK_SCRIPT', os.path.join(USR_ROOT, 'linker_scripts', 'riscv64', 'link.lds'))
-haohaibo@develop:~/work/k230_sdk/src/big/rt-smart/userapps/testcases/scale$
-```
-
-Recompile the source code, then copy both compiled `scale.elf` and `scale_with_rvv.elf` to the sharefs directory for execution.
-
-### Execution
-
-Prepare a 24-bit BMP image named `input.bmp` (you can use PC drawing software to save and generate it), place it in the same directory as the program, and then run these two programs on the large core through sharefs.
-
-```shell
-msh /sharefs>scale.elf
-scale calc use time:0.013952 ms
-BMP image scaling completed.
-msh /sharefs>scale.elf
-scale calc use time:0.013960 ms
-BMP image scaling completed.
-msh /sharefs>scale.elf
-scale calc use time:0.013941 ms
-BMP image scaling completed.
-msh /sharefs>scale.elf
-scale calc use time:0.013936 ms
-BMP image scaling completed.
-msh /sharefs>scale.elf
-scale calc use time:0.013945 ms
-BMP image scaling completed.
-msh /sharefs>scale.elf
-scale calc use time:0.013957 ms
-BMP image scaling completed.
-msh /sharefs>scale_with_rvv.elf
-scale calc use time:0.010139 ms
-BMP image scaling completed.
-msh /sharefs>scale_with_rvv.elf
-scale calc use time:0.010133 ms
-BMP image scaling completed.
-msh /sharefs>scale_with_rvv.elf
-scale calc use time:0.010135 ms
-BMP image scaling completed.
-msh /sharefs>scale_with_rvv.elf
-scale calc use time:0.010144 ms
-BMP image scaling completed.
-msh /sharefs>scale_with_rvv.elf
-scale calc use time:0.010142 ms
-BMP image scaling completed.
-```
-
-From the printed information, it is evident that using the V extension instructions significantly speeds up array calculations. If the image resolution is increased to 4K, the contrast will be even more apparent.
-
-### Disassembly
-
-You can use the objdump tool in the source directory to disassemble and confirm whether vector instructions are generated.
-
-```text
-$ riscv64-unknown-linux-musl-objdump scale_with_rvv.elf -S | grep 'vadd'
-   200002c7e:03bf4dd7          vadd.vx v27,v27,t5
-   200002c94:03834c57          vadd.vx v24,v24,t1
-$ riscv64-unknown-linux-musl-objdump scale_with_rvv.elf -S | grep 'vmul'
-   200002c98:97856c57          vmul.vx v24,v24,a0
-```
diff --git a/components/canaan/k230/artifacts/K230_RVV_optimization_performance_description.md b/components/canaan/k230/artifacts/K230_RVV_optimization_performance_description.md
deleted file mode 100644
index 6077f61..0000000
--- a/components/canaan/k230/artifacts/K230_RVV_optimization_performance_description.md
+++ /dev/null
@@ -1,214 +0,0 @@
-# K230 RVV Performance Optimization Description
-
-![cover](../../../zh/02_applications/tutorials/images/canaan-cover.png)
-
-Copyright © 2023 Beijing Canaan Creative Information Technology Co., Ltd.
-
-<div style="page-break-after:always"></div>
-
-## Disclaimer
-
-The products, services, or features you purchase are subject to the commercial contracts and terms of Beijing Canaan Creative Information Technology Co., Ltd. ("the Company", hereinafter the same) and its affiliates. All or part of the products, services, or features described in this document may not be within the scope of your purchase or use. Unless otherwise agreed in the contract, the Company does not provide any express or implied statements or warranties regarding the correctness, reliability, completeness, merchantability, fitness for a particular purpose, and non-infringement of any statements, information, or content in this document. Unless otherwise agreed, this document is for reference only.
-
-Due to product version upgrades or other reasons, the content of this document may be updated or modified periodically without any notice.
-
-## Trademark Statement
-
-![logo](../../../zh/02_applications/tutorials/images/logo.png) "Canaan" and other Canaan trademarks are trademarks of Beijing Canaan Creative Information Technology Co., Ltd. and its affiliates. All other trademarks or registered trademarks mentioned in this document are owned by their respective owners.
-
-**Copyright © 2023 Beijing Canaan Creative Information Technology Co., Ltd. All rights reserved.**
-Without the written permission of the Company, no organization or individual may excerpt, copy, or disseminate any part or all of the content of this document in any form.
-
-<div style="page-break-after:always"></div>
-
-## Table of Contents
-
-[toc]
-
-<div style="page-break-after:always"></div>
-
-## Preface
-
-### Overview
-
-This document mainly introduces the impact of RVV on model inference performance.
-
-### Audience
-
-This document (this guide) is mainly intended for the following personnel:
-
-- Technical Support Engineers
-- Software Development Engineers
-
-### Revision History
-
-| Document Version | Modification Description | Modifier | Date       |
-| ---------------- | ------------------------ | -------- | ---------- |
-| V1.0             | Initial Version          | Yang Haoqi | 2023/08/04 |
-
-## Overview
-
-In recent years, the rapid development of the AI field has led to the emergence of various neural network models and new operators. However, the iteration cycle of AI chips is much longer compared to AI models, and many of these new operators cannot directly use AI chips for inference acceleration. At the same time, some old operators are also not suitable for inference acceleration using AI chips. Therefore, the CPU becomes the execution carrier for these operators, which means that the performance of the CPU will become a factor affecting the final performance during model deployment. The RVV extension is an important means to improve the performance of RISC-V CPUs. The K230 uses the Xuantie C908 dual-core processor, where the large core has the RVV1.0 extension feature, which can significantly improve the performance during CPU operator inference.
-
-To perform model inference on the K230, a model in the `.kmodel` format is required. The `.kmodel` format is a compiled model format by [nncase](https://github.com/kendryte/nncase) for `ONNX` and `TFLite` models, suitable for development boards produced by the Company and related cooperative enterprises. nncase supports common neural network operators, but some operators cannot be accelerated for inference by the K230 and must use the CPU for inference.
-
-## RVV Application Scenarios
-
-Currently, the most widely researched and applied neural network is the `Transformer`, which has a model structure significantly different from `CNN`. Many AI chips designed based on `CNN` cannot fully accelerate the `Transformer`. Below is the execution of operators in the `Decoder` model of `Transformer` with and without RVV optimization enabled.
-
-### Without RVV Optimization
-
-| stackvm tensor op | count | time consumption(ms) | percentage(%) |
-| ----------------- | ----- | -------------------- | ------------- |
-| softmax           | 5     | 1749.61              | 88.6574       |
-| where             | 4     | 199.432              | 10.1058       |
-| EXTCALL           | 65    | 16.099               | 0.815779      |
-| layer_norm        | 7     | 5.81                 | 0.294408      |
-| gather            | 2     | 0.393                | 0.0199144     |
-| STLOCAL           | 212   | 0.391                | 0.019813      |
-| LDC_I4            | 241   | 0.388                | 0.019661      |
-| reduce_arg        | 1     | 0.336                | 0.017026      |
-| reshape           | 26    | 0.281                | 0.014239      |
-| LDLOCAL           | 149   | 0.26                 | 0.0131749     |
-| LDNULL            | 106   | 0.166                | 0.00841166    |
-| LDTENSOR          | 29    | 0.103                | 0.00521929    |
-| LEA_GP            | 58    | 0.097                | 0.00491525    |
-| LDDATATYPE        | 29    | 0.07                 | 0.00354709    |
-| LDARG             | 5     | 0.008                | 0.000405381   |
-| RET               | 1     | 0.004                | 0.000202691   |
-| LDTUPLE           | 1     | 0.003                | 0.000152018   |
-| total             | 941   | 1973.45              | 100           |
-
-### With RVV Optimization
-
-| stackvm tensor op | count | time consumption(ms) | percentage(%) |
-| ----------------- | ----- | -------------------- | ------------- |
-| softmax           | 5     | 25.722               | 55.6175       |
-| EXTCALL           | 65    | 16.179               | 34.9831       |
-| layer_norm        | 7     | 0.967                | 2.0909        |
-| where             | 4     | 0.912                | 1.97198       |
-| gather            | 2     | 0.39                 | 0.84328       |
-| LDC_I4            | 241   | 0.386                | 0.834631      |
-| STLOCAL           | 212   | 0.379                | 0.819495      |
-| reduce_arg        | 1     | 0.34                 | 0.735167      |
-| LDLOCAL           | 149   | 0.259                | 0.560024      |
-| reshape           | 26    | 0.243                | 0.525428      |
-| LDNULL            | 106   | 0.17                 | 0.367583      |
-| LEA_GP            | 58    | 0.103                | 0.222712      |
-| LDTENSOR          | 29    | 0.103                | 0.222712      |
-| LDDATATYPE        | 29    | 0.076                | 0.164331      |
-| LDARG             | 5     | 0.011                | 0.0237848     |
-| RET               | 1     | 0.005                | 0.0108113     |
-| LDTUPLE           | 1     | 0.003                | 0.00648677    |
-| total             | 941   | 46.248               | 100           |
-
-### Performance Analysis and Description
-
-In the model inference above, the KPU unit of K230 does not support hardware inference acceleration for `softmax`, `layer_norm`, `where`, `gather`, `reduce_arg`, and `reshape`, so the C908 is used for inference. RVV optimization has been completed for `softmax`, `layer_norm`, and `where`, with significant performance improvement.
-
-Below are the pie charts showing the proportion of each operator's time consumption in model inference before and after RVV optimization.
-
-<div class="mermaid">
-pie
-    title Without RVV Optimization
-    "softmax" : 88.6574
-    "where" : 10.1058
-    "EXTCALL" : 0.815779
-    "layer_norm" : 0.294408
-    "gather" : 0.0199144
-    "STLOCAL" : 0.019813
-    "LDC_I4" : 0.019661
-    "reduce_arg" : 0.017026
-    "reshape" : 0.014239
-    "LDLOCAL" : 0.0131749
-    "LDNULL" : 0.00841166
-    "LDTENSOR" : 0.00521929
-    "LEA_GP" : 0.00491525
-    "LDDATATYPE" : 0.00354709
-    "LDARG" : 0.000405381
-    "RET" : 0.000202691
-    "LDTUPLE" : 0.000152018
-</div>
-
-<div class="mermaid">
-pie
-    title With RVV Optimization
-    "softmax" : 55.6175
-    "EXTCALL" : 34.9831
-    "layer_norm" : 2.0909
-    "where" : 1.97198
-    "gather" : 0.84328
-    "LDC_I4" : 0.834631
-    "STLOCAL" : 0.819495
-    "reduce_arg" : 0.735167
-    "LDLOCAL" : 0.560024
-    "reshape" : 0.525428
-    "LDNULL" : 0.367583
-    "LEA_GP" : 0.222712
-    "LDTENSOR" : 0.222712
-    "LDDATATYPE" : 0.164331
-    "LDARG" : 0.0237848
-    "RET" : 0.0108113
-    "LDTUPLE" : 0.00648677
-</div>
-
-Below is the performance comparison of related operators before and after RVV optimization.
-
-![RVV](../../../zh/02_applications/tutorials/images/RVV_optimize_performance.jpg)
-
-From the comparison results above, it can be seen that enabling RVV optimization can greatly improve the inference performance of CPU operators, significantly reducing the overall model inference time (1973 ms to 46 ms). After RVV optimization, the `softmax` operator time is reduced to 25 ms, the `layer_norm` operator time is reduced to 0.97 ms, and the `where` operator time is reduced to 0.91 ms. The overall model inference time is shortened by 97.6%, which has high application value in actual model deployment.
-
-### RVV Optimization Example
-
-#### RVV Code
-
-For specific implementation, please refer to `layer_norm` in `nncase` [here](https://github.com/kendryte/nncase/blob/master/src/Native/src/kernels/stackvm/optimized/riscv64/layer_norm.cpp). It requires some knowledge of RV instructions and V extension instructions.
-
-The calculation formula for `layer_norm` is as follows:
-
-```plaintext
-y= (x−E[x])/sqrt(Var[x]+ϵ)∗γ+β
-```
-
-The overall calculation process can be found in the `layernorm_impl` function. For better readability, the RVV optimized code in this process is split into three parts:
-
-1. Calculate `E[x]`, refer to the `get_mean` function.
-1. Calculate `Var[x]`, refer to the `get_var` function.
-1. Perform layer_norm calculation according to the formula above, refer to the `layer_norm_update1` function.
-
-Since multiplication is less time-consuming than division, the formula in step 3 is transformed to use `rsqrt` instead of `sqrt` and multiplication instead of division.
-
-#### Core Code Explanation
-
-Below is an explanation of the core code in `get_mean`. This code segment implements the loop load and summation of the array at a1, stores the summation result in v0, and finally stores the average value in ret. It uses RVV's vector load and vector accumulate instructions to achieve summation, thereby improving computational performance.
-
-```plaintext
-"vle32.v v8, (a1);"   // Load 32-bit vector at a1 address into v8 register
-"sub a0,a0, t0;"      // a0 -= t0, used for loop control count
-"slli t1, t0, 2;"     // t1 = t0 << 2, as each float32 is 4 bytes, so address increases by 4*t0
-"vfredsum.vs v0,v8,v0;"  // v0 += v8, vector accumulate sum into v0
-
-"add a1, a1, t1;"      // a1 += t1, update load address
-"bnez a0, XXXXXX%=;"   // If a0 != 0, jump to loop start address
-"vfmv.f.s f0, v0;"     // Move vector accumulate result from v0 to f0
-"fcvt.s.w f1, %[avl];"  // Convert avl to float and save to f1
-"fdiv.s %[ret], f0, f1;" // ret = f0/f1, i.e., calculate average
-```
-
-#### Adding RVV Operator Process
-
-In the following process, paths are based on [nncase](https://github.com/kendryte/nncase) as the root directory
-
-1. Function Declaration: src/Native/src/kernels/stackvm/optimized/opt_ops.h
-1. Operator Implementation:
-   - General Optimization: src/Native/src/kernels/stackvm/optimized
-   - x86 Optimization: src/Native/src/kernels/stackvm/optimized/x86_64
-   - RVV Optimization: src/Native/src/kernels/stackvm/optimized/riscv64
-1. Logical Call: src/Native/src/kernels/stackvm/tensor_ops.cpp
-1. Modify CMakeLists: src/Native/src/kernels/stackvm/optimized/CMakeLists.txt
-   - General Optimization: Add source file name in line 15
-   - Platform-specific Optimization: Add source file name in line 44
-
-### Tips
-
-If you encounter operators that are not yet supported by RVV optimization and need support, feel free to raise issues and PRs on [nncase](https://github.com/kendryte/nncase/issues).
diff --git a/components/canaan/k230/artifacts/K230_brief_datasheet.md b/components/canaan/k230/artifacts/K230_brief_datasheet.md
deleted file mode 100644
index 95ee756..0000000
--- a/components/canaan/k230/artifacts/K230_brief_datasheet.md
+++ /dev/null
@@ -1,221 +0,0 @@
-# K230 Product Brief
-
-![cover](images/canaan-cover.png)
-
-Document version: V1.0
-Release date: 2023-6-10
-
-<div style="page-break-after:always"></div>
-
-## Disclaimer
-
-The products, services or features you purchase shall be subject to the commercial contracts and terms of Canaan Creative CO., LTD. (the "Company") and its affiliates, and all or part of the products, services or features described in this document may not be within the scope of your purchase or use. Unless otherwise agreed in the contract, the Company does not provide any express or implied representations or warranties as to the correctness, reliability, completeness, merchantability, fitness for a particular purpose and non-aggression of any statements, information, or content in this document.Unless otherwise agreed, this document is intended as a guide for use only.
-
-Due to product version upgrades or other reasons, the content of this document may be updated or modified from time to time without any notice.
-
-## Trademark Notice
-
-![logo](images/logo.png)
-"Canaan" and other Canaan trademarks are trademarks of Canaan Creative CO., LTD. and its affiliates. All other trademarks or registered trademarks that may be mentioned in this document are owned by their respective owners.
-
-Copyright©2023 Canaan Creative CO., LTD.
-This document is only suitable for the development and design of K230 platform, without the written permission of the company, any unit or individual shall not disseminate part or all of the content of this document in any form.
-
-Canaan Creative CO., LTD.
-Website：canaan-creative.com
-Business Email：<salesAI@canaan-creative.com>
-
-<div style="page-break-after:always"></div>
-
-## Menu
-
-[TOC]
-
-## Preface
-
-### Purpose
-
-This document is intended to provide a general overview of the K230 platform and its features.
-
-### Intended Audience
-
-The main people to whom this document (this guide) applies:
-
-- Design and maintenance personnel for electronic products
-- Sales personnel for electronic products
-- Technical support personnel
-
-### Terms
-
-### Revision history
-
-| Version Number | Author    | Revision Date | Revision Notes                                                    |
-|----------------|----------------|--------------|-------------------------------------------------------------------|
-| V1.0           | Zhenming Huang | 2023-6-10    | Re-format to markdown document based on K230 Brief Datasheet_Complete_Apr_2023_v1 |
-|                |                |              |           |
-
-## Overview
-
-The K230 chip is the latest generation SoC product in Canaan Technology's (NASDAQ: CAN) Kendryte® series of AIOT chips. The chip adopts a brand-new multi-heterogeneous unit acceleration computing architecture, integrates two RISC-V C908 computing cores, and has a built-in new generation KPU (Knowledge Process Unit) intelligent computing unit. Multi-precision AI computing power with INT8 and INT16. Supports general AI computing framework. The chip also has a variety of peripheral interfaces, as well as multiple scalar, vector, graphics, and other dedicated hardware acceleration units such as image 2D engine, AI 2D engine, 2.5D GPU, and 3D depth engine. K230 provides full-process computing acceleration for various computing tasks such as images, videos, audio, AI, etc. The chip has many features such as low latency, high performance, low power consumption, fast startup, and high security.
-K230 can be used in various smart hardware products, such as smart door locks, home smart security cameras, dictionary pens, payment recognition, 3D structured light vision modules, drones, interactive robots, smart home appliances, smart toys, and smart manufacturing, intelligent vehicle cockpit and many other fields.
-
-## General Specifications
-
-### CPU
-
-- CPU 1: 64bit, RISC-V processor, 1.6GHz, supports RISC-V Vector Extension 1.0 specification, with floating-point units (FPUs), 128bits vector-process-unit, runs RTOS system
-
-- CPU 0: 64bit, RISC-V processor, 800MHz, supports RISC-V 64GCB instruction set, runs LINUX system
-
-### KPU
-
-- Support INT8 and INT16
-
-- Support weight sparse compression
-- Typical network performance：
-  - Resnet 50 ≥ 85fps @INT8
-  - Mobilenet_v2 ≥ 670fps @INT8
-  - YoloV5S ≥ 38fps @INT8
-- Support TVM / TensorFlow / Pytorch / ONNX
-- Support quantitative tool chain and profiling tools
-- Loss of quantization accuracy <1%
-
-### D Engine
-
-- 2D(GDMA) Engine:
-  - OSD/CSC/X-Mirror/Y-Mirror/Rotation（90/180/270）
-  - Typical image rotation capability：
-    - 2 x 1080\*1280 YUV400 @15fps + 1 x 1080\*1920 YUV420 @30fps
-
-- Independent AI 2D Engine:
-  - Affine/Crop/Resize/Padding/Shift
-
-### DPU (Depth Computing Unit)
-
-- Using 3D structured light depth calculation
-
-- Support multiple operators, including Img_check / LCN / SAD / Post_proc / Align
-/ Disptodepth
-- The maximum resolution of the landscape image is 1920\*1080, and the maximum resolution of the portrait image is 1080\*1440
-- Typical performance is 1280\*800@30fps, 1280\*1080@15fps,1920\*1080@9fps
-
-### Memory
-
-- DRAM: DDR3L / LPDDR4 with 16/32bit,
-LPDDR3 with 32bit
-
-- DRAM frequency：
-  - DDR3L@1600Mbps / LPDDR3@2133Mbps
-  - LPDDR4@2667Mbps
-- Maximum capacity: 2GB
-- SIP mode: 128MB 16bit LPDDR4@3200Mbps
-- SRAM：2MB+2MB (default for KPU)
-
-### Video Input
-
-- 3 x MIPI CSI
-
-- (1 x 4lane+1 x 2lane) or 3 x 2lane
-
-### ISP
-
-- Total throughput：8MP@30fps
-
-- Image 3A / 2DNR / 3DNR / WDR / HDR
-- Local Tone Mapping
-- Sharpen / BLS / LSC / De-warping
-- RGB-IR 4x4 pattern
-
-### Video Output
-
-- 1 x MIPI DSI, 1 x 4 lane or 1 x 2 lane
-
-- Resolution: 2MP@60fps
-
-### Video Codec
-
-- Video encoding
-  - H.264 Baseline / Main Profile / High Profile
-  - H.265 Main Profile
-  - JPEG / MJPEG
-  - Maximum encoding performance:
-    - 8MP@20fps
-  - CBR / VBR / CQP / ROI encoding
-
-- Video decoding
-  - H.264 Baseline, Main Profile, High Profile
-  - H.265 Main Profile
-  - JPEG / MJPEG
-  - Maximum decoding performance:
-    - 8MP@40fps
-
-### D GPU
-
-- Highly optimized Tessellation Engine, cooperates with the VGlite driver to provide vector graphics drawing functions
-
-- Support rotation, scaling, translation, and format conversion of the input image
-- The drawn picture can perform operations such as blending, compression, etc., with the picture in video memory
-
-### Audio
-
-- 2 x DAC: 8-192Khz
-
-- 2 x ADC: 8-192Khz
-- Support ALC
-- Maximum 8 x PDM DMIC inputs
-- I2S interface supports 2x2 expansion
-
-### Peripherals
-
-- Low-speed interface
-  - 5 x UART / 5 x I2C / 6 x PWM
-  - GPIO (multiplexed with function pins):
-    - 64 x GPIO + 8 x PMU GPIO
-    - 50 x GPIO + 6 x PMU GPIO(SIP)
-
-- High-speed interface
-  - 2 x USB 2.0 OTG
-  - 2 x SDxC: SD3.01, eMMC 5.0
-  - 3 x SPI: 1 x OSPI + 2 x QSPI
-- WDT / RTC / Timer
-
-### Security
-
-- PUF / OTP / TRNG
-
-- Support AES, SHA, RSA, SM2/3/4, ECC
-
-### PMU
-
-- Ultra-low power consumption: in deep sleep mode, standby power consumption ≤ 20uW
-- Support RTC function in 32KHz
-- Support long and short press detection as system shutdown or wakeup signal
-- Support IO edge and level detection to generate interrupts
-- Support two output IOs to control PMIC and system reset
-- Support 512 bits system log when shutdown
-
-### Other Features
-
-- Decompression module:
-  - decompression bandwidth ≥ 400MB/s, GZIP format
-
-- 4096-point FFT / IFFT unit
-- Fastboot: 3A first picture ≤ 400ms
-- Working environment temperature: -40 ~ 85°C
-- Package：BGA, 0.65mm pitch
-  - 13 x 13mm
-  - 11 x 11mm (SIP 128MB 16bit LPDDR4)
-
-## Block Diagram
-
-![K230_block_diagram.png](images/K230_block_diagram.png)
-
-## Typical Applications　　
-
-- 3D Face Lock Integrated Application Solution　　
-
-![K230_application_1.png](images/K230_application_1.png)
-
-- Smart Dictionary Pen Application Solution　　
-
-![K230_application_2.png](images/K230_application_2.png)
diff --git a/components/canaan/k230/artifacts/K230_datasheet-v1.0-2023-07-06.md b/components/canaan/k230/artifacts/K230_datasheet-v1.0-2023-07-06.md
deleted file mode 100644
index e45aa9e..0000000
--- a/components/canaan/k230/artifacts/K230_datasheet-v1.0-2023-07-06.md
+++ /dev/null
@@ -1,1254 +0,0 @@
-# K230 Product Full Datasheet
-
-![cover](../../zh/images/canaan-cover.png)
-
-Document version: V1.0
-Release date: 2023-7-6
-
-<div style="page-break-after:always"></div>
-
-## Disclaimer
-
-The products, services or features you purchase shall be subject to the commercial contracts and terms of Canaan Creative CO., LTD. (the "Company") and its affiliates, and all or part of the products, services or features described in this document may not be within the scope of your purchase or use. Unless otherwise agreed in the contract, the Company does not provide any express or implied representations or warranties as to the correctness, reliability, completeness, merchantability, fitness for a particular purpose and non-aggression of any statements, information, or content in this document.Unless otherwise agreed, this document is intended as a guide for use only.
-
-Due to product version upgrades or other reasons, the content of this document may be updated or modified from time to time without any notice.
-
-## Trademark Notice
-
-![logo](../../zh/images/logo.png)
-"Canaan" and other Canaan trademarks are trademarks of Canaan Creative CO., LTD. and its affiliates. All other trademarks or registered trademarks that may be mentioned in this document are owned by their respective owners.
-
-Copyright©2023 Canaan Creative CO., LTD.
-This document is only suitable for the development and design of K230 platform, without the written permission of the company, any unit or individual shall not disseminate part or all of the content of this document in any form.
-
-Canaan Creative CO., LTD.
-Website：canaan-creative.com
-Business Email：<salesAI@canaan-creative.com>
-
-<div style="page-break-after:always"></div>
-
-## Preface
-
-### Purpose
-
-This document is intended to provide a full description of the K230 platform and its features.
-
-### Intended Audience
-
-The main people to whom this document (this guide) applies:
-
-- Design and maintenance personnel for electronic products
-- Sales personnel for electronic products
-- Technical support personnel
-
-### Terms
-
-### Revision history
-
-| Version Number | Modified by    | Revision Date | Revision Notes                                                                    |
-| -------------- | -------------- | ------------- | --------------------------------------------------------------------------------- |
-| V1.0           | Ruizheng Li,Heng Wen | 2023-7-6     | Revised version |
-|                |                |              |           |
-
-<div style="page-break-after:always"></div>
-
-## Index
-
-[TOC]
-
-<div style="page-break-after:always"></div>
-
-## Chapter 1 Introduction
-
-### Overview
-
-The K230 chip is the latest generation SoC product in Canaan Technology's (NASDAQ: CAN) Kendryte® series of AIOT chips. The chip adopts a brand-new multi-heterogeneous unit acceleration computing architecture, integrates two RISC-V C908 computing cores, and has a built-in new generation KPU (Knowledge Process Unit) intelligent computing unit. Multi-precision AI computing power with INT8 and INT16. Supports general AI computing framework. The chip also has a variety of peripheral interfaces, as well as multiple scalar, vector, graphics, and other dedicated hardware acceleration units such as image 2D engine, AI 2D engine, 2.5D GPU, and 3D depth engine. K230 provides full-process computing acceleration for various computing tasks such as images, videos, audio, AI, etc. The chip has many features such as low latency, high performance, low power consumption, fast startup, and high security.
-K230 can be used in various smart hardware products, such as smart door locks, home smart security cameras, dictionary pens, payment recognition, 3D structured light vision modules, drones, interactive robots, smart home appliances, smart toys, and smart manufacturing, intelligent vehicle cockpit and many other fields.
-
-### Feature
-
-#### CPU subsystem
-
-- CPU0 subsystem
-
-  - 64bit RISC-V processor
-  - Supports maximum 800 MHz working frequency
-  - Supports RISC-V 64GCB instruction set
-  - Cpu contains floating-point units (FPUs)
-  - L1 cache contains 32 KB instruction cache (I-cache) and 32 KB data cache (D-cache)
-  - Integrates with 128 KB L2 cache
-  - Supports memory management unit (MMU)
-  - Integrates with the interrupt controller (PLIC), which can process 208 interrupt external sources
-  - Supports the Joint Test Action Group (JTAG) debugging interface
-  - Supports WFI
-
-- CPU1 subsystem
-
-  - 64bit RISC-V processor
-  - Supports maximum 1.6 GHz working frequency
-  - Supports RISC-V Vector Extension 1.0 specification
-  - Cpu contains floating-point units (FPUs)
-  - 128bits vector-process-unit
-  - L1 cache contains 32 KB instruction cache (I-cache) and 32 KB data cache (D-cache)
-  - Integrates with 256 KB L2 cache
-  - Supports memory management unit (MMU)
-  - Integrates with the interrupt controller (PLIC), which can process 208 interrupt external sources
-  - Supports the Joint Test Action Group (JTAG) debugging interface
-  - Supports WFI
-
-#### KPU subsystem
-
-- Support INT8 and INT16
-- Support weight sparse compression
-- Typical network performance：
-  - Resnet 50 ≥ 85fps @INT8
-  - Mobilenet_v2 ≥ 670fps @INT8
-  - YoloV5S ≥ 38fps @INT8
-- Support TensorFlow / PyTorch / TFLite / PaddlePaddle / ONNX
-- Support quantization toolchain and profiling tools
-- Loss of quantization accuracy <1%
-- Support Abs, Acos, Acosh, And, ArgMax, ArgMin, Asin, Asinh, Add, AveragePool, BatchNormalization, Cast, Ceil, Celu, Clip, Concat, Constant, ConstantOfShape, Conv, ConvTranspose, Cos, Cosh, CumSum, DepthToSpace, DequantizeLinear, Div, Dropout, Elu, Equal, Exp, Erf, Expand, Flatten, Floor, Gather, GatherElements, GatherND, Gemm, GlobalAveragePool, GlobalMaxPool, Greater, GreaterOrEqual, Hardmax, HardSigmoid, HardSwish, Identity, InstanceNormalization, LpNormalization, LeakyRelu, Less, LessOrEqual, Log, LogSoftmax, LRN, LSTM, MatMul, MaxPool, Max, Min, Mod, Mul, Neg, Not, OneHot, Pad, Pow, PRelu, QuantizeLinear, QLinearConv, QLinearMatmul, RandomNormal, RandomNormalLike, RandomUniform, RandomUniformLike, Range, ReduceL1, ReduceL2, ReduceLogSum, ReduceLogSumExp, ReduceMax, ReduceMean, ReduceMin, ReduceProd, ReduceSum, ReduceSumSquare, Relu, Reshape, Resize, ReverseSequence, Round, ScatterND, Selu, Shape, Sin, Sinh, Sigmoid, Sign, Size, Slice, Softmax, Softplus, Softsign, SpaceToDepth, Split, Sqrt, Squeeze, Sub, Sum, Tanh, Tile, TopK, Transpose, Upsample, Unsqueeze, Where
-
-#### D Engine
-
-- 2D GDMA Engine
-
-  - X-Mirror/Y-Mirror/Rotation（90/180/270）
-  - Typical image rotation capability：
-    - 2 x 1080\*1280 YUV400 @15fps + 1 x 1080\*1920 YUV420 @30fps
-  - Provides one physical DMA channel
-  - The axi data width is 64-bit
-  - Supports configurable axi transaction outstanding numbers: the max outstanding number is 8
-  - Supports data transfer with the linked list
-  - Supports configurable weight-based channel priority arbitration
-  - Supports lowpower mode：each channel supports auto clock gate
-  - Supports configurable image row stride
-  - The maximum image resolution supports 64Kx64K
-  - The data width of the image pixel supports 8/16/24/32bits
-  - Max Burst length can be set to 8 or 4 for non-24bit width pixel, and 12 for 24bit pixel
-
-- Non AI 2D
-  - Support OSD mode
-  - Support CSC mode
-  - Support draw border mode
-  - Support corp operation
-
-- Independent AI 2D Engine
-  - Affine/Crop/Resize/Padding/Shift
-  - Resize
-  - Crop
-  - Affine
-  - The calculation of resize and affine coordinates supports opencv's round, as well as ceil and floor
-  - Pad
-    - Support four edge parts to complement constant pads, the pad value can be specified, and the maximum number of pads on a single side is 1023
-  - CSC
-    - Both input and output images support the following formats
-    - YUV420_NV12
-    - YUV420_NV12
-    - YUV420_I420
-    - YUV400
-    - RGB_packed
-    - NCHW
-
-  - Shift
-
-    - RAW16 input   -> shift to RAW8 output
-
-  - Support CPU to read internal registers
-
-  - The accelerator can access the system SRAM(2MB).
-
-  - Support software reset through configuration register
-
-  - Support clk gating
-
-    **NOTE**
-
-  - Note1: The highest source image resolution supports 4K
-
-  - Note2: All configured ddr addresses follow 16B align, which is friendly to performance
-
-  - Note3: A configuration register cannot exceed 1KB
-
-  - Note4: When configuring cpu, configure 32bit each time, and configure 4 times for each 128bit, and must configure 4 times, the order is from low to high; when configuring GNNE, configure 128bit at a time
-
-#### DPU (Depth Processing Unit)
-
-- Using 3D structured light depth calculation
-- The maximum resolution of the landscape image is 1920\*1080, and the maximum resolution of the portrait image is 1080\*1440
-- Typical performance is 1280\*800@30fps, 1280\*1080@15fps,1920\*1080@9fps
-- Both read and write AXI bus support crop
-- Support standard axi-4 protocol, data bit width 64bit, address bit width 32bit, burst_length up to 16, read and write outstanding up to 8
-- Support standard apb3.0 protocol, data bit width 32bit, address bit width 32bit
-- Img_check: The precision of the input speckle image is int8, the precision of the output calculation result is int1, and it supports output after downsampling
-- LCN: The precision of the input speckle image is int8, and the precision of the output calculation result is int12, which supports normalized calculation of the source image
-- SAD: Input the normalized speckle image/reference image, the accuracy is int12, the output row and column parallax accuracy is int16, support Init_SAD single/double layer enable, support SAD double layer enable, and support the first layer input of Init_SAD/SAD is involved in the calculation after 1/2 downsampling
-- Post_proc: The precision of the input column parallax is int16, the precision of the output calculation result is int1, supports Post_proc enable, and supports Post_proc inner mask denoising enable
-- Align: The precision of input column parallax is int16, the precision of mask is int1, the precision of output depth/disparity map is int16, the precision of input/output infrared map is int8, supports height block processing parallax/infrared alignment, supports parallax/infrared Alignment enable, support Align inner parallax denoising enable, support parallax/infrared up and down sampling enable, support Disp2depth enable
-- Support normal calculation end interrupt, timeout interrupt, instruction exception interrupt, configuration instruction overflow interrupt, AXI write response exception interrupt
-- Support independent soft reset, interrupt clear operation
-
-#### Memory
-
-- DDR
-
-  - 16-bit per channel LPDDR4, two channels, the max speed is 3200Mbps
-  - 32-bit LPDDR3 supported,the max speed is 2133Mbps
-  - Maximum capacity: 2GB
-  - Scalable 1:1/1:2 frequency ratio architecture. We setting 1:2 frequency ratio
-  - For LPDDR3 configurations, direct software request control or programmable internal control for ZQ short calibration cycles
-  - For LPDDR3 configurations, support for ZQ long calibration after self-refresh exit
-  - For LPDDR4 configurations, direct software request control or programmable internal control for ZQ calibration cycles
-  - For LPDDR4 configurations, support for ZQ calibration after SR-Powerdown exit
-  - Dynamic scheduling to optimize bandwidth and latency
-  - For maximum SDRAM efficiency, commands are executed out-of-order
-  - Hardware configurable and software programmable Quality of Service (QoS) support
-  - Programmable support for all of the following SDRAM data-bus widths: Full data-bus width or Half of the full data-bus width
-  - Supports max to 2 ranks
-  - Control options to avoid starvation of lower priorities
-  - Guaranteed coherency for write-after-read (WAR) and read-after-write (RAW) hazards (always on the HIF interface and on the AXI interface only if appropriate hardware configuration parameter and software register are set)
-  - Write combine to allow multiple writes to the same address to be combined into a single write to SDRAM; supported for same starting address
-  - Supports automatic SDRAM power-down entry and exit caused by lack of transaction arrival for a programmable time
-  - Supports automatic Clock Stop (LPDDR3/LPDDR4) entry and exit caused by lack transaction arrival
-  - Supports automatic low power mode operation caused by lack of transaction arrival for a rogrammable time through the Hardware Low Power Interface
-  - Flexible address mapper logic to allow application specific mapping of row, column, bank, and rank bits
-  - Leverages out of order requests with CAM to maximize throughput
-  - APB interface for the software accessible registers
-  - 5 host ports using AMBA AXI
-  - Automatic periodic retraining through PHY MASTER Interface
-  - Support for:
-    1. (LPDDR3, LPDDR4) Command Bus eye training relative to CK
-    1. Write Leveling to compensate for CK-DQS timing skew
-    1. Write Training: DQS to DQ
-       Two modes of training are available in LPDDR4:
-       - Command-based FIFO WR/RD with user patterns
-       - An internal DQS clock tree oscillator, to determine the need for, and the magnitude of, required periodic training
-    1. Data bus VREFDQ training
-    1. Read training( DQ bit deskew training using DRAM mode registers and DQS to DQ eye centering training using DRAM array)
-  - LVSTL IO calibration and ODT calibration
-  - Support for a SW controllable DQ bit and AC bit swizzling
-  - Firmware-based 2D eye mapping diagnostic tool allows measuring 2D eye for every bit of the bus at both DRAM and host receivers
-  - Direct override programming available for all VREF, ODT, drive strength, and timing delays to facilitate debug and characterization
-
-- SRAM
-  - SRAM：2MB (shared sram)+2MB (default for KPU)
-  - The shared 2MB sram provides access to CPU/KPU/decompression and other modules
-  - The shared 2MB sram has two independent 128bit AXI4 Slave buses. Burst supports incremental, fixed, and wrap. The maximum burst length is 16. Exclusive transmission is not supported. The maximum outstanding read and write are 16 respectively
-  - The shared 2MB sram is divided into two groups. The first group is shared by KPU port0, axi slave0, axi slave1, and decompression module. When decompression does not work, KPU port0 has the highest priority, followed by axi slave0/axi slave1. The other group of KPU port1, axi slave 0, and axi slave 1 are shared. KPU port1 has the highest priority
-  - The decompression module shares 768KB SRAM to cache the decompression process data
-
-- Flash
-
-  - Supports the SPI NOR flash and SPI NAND flash
-  - Supports the read and write operations in internal DMA mode for the SPI NAND flash and the SPI NOR flash.
-  - Support Enhanced (Dual/Quad/Octal) SPI features:
-    - Programmble address,instruction,wait cycles,and data frame size
-    - Dual Data Rate(DDR) support
-    - Read Data Strobe support for DDR transfer
-  - Data item size(4 to 32bits)-Item size of each data transfer under control of the programmer
-  - Execute In Place(XIP) mode support:
-    - AHB address is mapped to SPI NOR flash address directly
-    - Read and write SPI NOR flash directly
-  - Read and write SPI NAND flash need to operate according to the NAND flash operation requirement
-  - Except XIP mode, all operations need to operate according to the flash operation requirement
-  - Programmable delay on the sample time of received serial data bit(rxd)
-  - Programmable clock bit rate
-  - The latency of strb can be adjusted
-
-    **Note:**
-
-    If data frame size is set to 8bit and DDR mode is selected, one clock pulse corresponds to two byte data. So total data length must be set to an even number.
-
-#### system component
-
-- RMU
-
-  - Reset management module (RMU) is responable for power on reset deglitch, manage wdt reset，chip soft reset and generate sub-module reset
-  - Reset glitch length less than 8ms will be filtered
-  - Manage two watchdog reset and generate soc reset
-  - Manage software soc reset request and generate soc reset
-  - Manage sub-module software reset request and generate sub-module reset
-
-- CMU
-
-  - Clock management module (CMU) is designed to manage generation of sub-module and system clock、clock division、clock switch and clock gating
-  - The clock source include external 24MHz OSC and four internal PLLs
-  - CPU1 and KPU module support DVFS. Their frequency should meet current voltage
-  - When CPU1 and KPU use the same clock source, their frequency can be changed synchronously
-  - When CPU1 and KPU use different clock source, their frequency can be changed independently
-
-- PWR
-
-  - Power control module (PWR) is used for power control of SOC and sub-module
-  - There are five power mode : Power on, sleep0, sleep1, standby, powerdown
-  - There are three kinds of wakeup source : GPIO, PMU and timer
-  - Each power domain can be controlled to power down、power up 、clock gating according to defferent application
-
-- Interrupt
-
-  - K230 supports 208 interrupt sources
-
-- PDMA
-
-  - PDMA (Peripheral Direct Memory Access) supports the data transfer between peripheral ports and DDR/SRAM
-  - PDMA provides 8 channels to transfer different transactions, with 64-byte data buffer per channel
-  - It supports up to 35 peripheral ports through channel configuration
-  - Low power IDLE state of each channel can be set by shutting down corresponding clock
-  - A 64-bit AXI4 master is used to transfer different channel transactions
-  - The priority of each transaction is configured with each channel. Transactions with high priority gets high chance to be transferred
-  - Peripheral data address can only be accessed in 4 bytes aligned with strobe signal to indicate the lower 1/2/4 byte(s) are used, and only fixed address is supported
-
-- SDMA
-
-  - Provides four DMA channels：ch0,ch1,ch2 and ch3
-  - The axi data width is 64-bit
-  - The max axi burst length is 16
-  - Supports configurable axi transaction outstanding numbers: the max outstanding number of ch0,ch2,ch3 is 2, the max outstanding number of ch1 is 16
-  - Supports configurable data endian
-  - Supports data transfer with the linked list
-  - Supports configurable weight-based channel priority arbitration
-  - Supports lowpower mode：each channel supports auto clock gate
-  - Supports specified data transfer for decompression module using ch0 and ch1
-
-- General-puspose timers
-
-  - APB interface supports APB3
-  - Up to six programmable timers
-  - Configurable timer width: 8 to 32 bits
-  - Support for two operation modes: free-running and user-defined count
-  - Support for independent clocking of timers
-  - Configurable polarity for each individual interrupt
-  - Configurable option for a single or combined interrupt output flag
-  - Configurable option to have read/write coherency registers for each timer
-  - connfigurable option to include timer toggle output, which toggles whenever timer counter reloads
-  - Configurable option to enable programmable pulse-width modulation of timer toggle outputs
-  - Configurable option to include pulse width modulation of timer toggle output with 0% and 100%
-    duty cycle.
-  - Can be used to count external input signal with frequency less than 1MHz and ducy cycle from 0~100%
-
-- Stc timer
-
-  - 64 bit timer width
-  - 3 configurable timescale : 27MHz, 1MHz, 90KHz
-  - Configurable enable、load、clear control register
-  - Apb 3.0 interface
-  - One timer can be used for video-input/video-output and audio synchronization.
-  - One timer is used for cpu0 and one timer is used for cpu1.
-  - Timer used for video/audio synchronization provides two sets of timer value, one is old value and the other is latest value
-
-- Watchdog
-
-  - APB3 interface support
-  - Watchdog counter width of 32 bits
-  - Counter counts down from a preset value to 0 to indicate the occurrence of a timeout
-  - If a timeout occurs the watchdog can perform one of the following operations:
-    - Generate a system reset
-    - First generate an interrupt and even if it is cleared (or not) by the service routine by the time a second timeout occurs then generate a system reset
-  - Programmable reset pulse length
-
-- RTC
-
-  - Typical working frequency: external clock source 32768 Hz
-  - Involved in the work mode: normal working mode, independent power supply working mode
-  - Interface type: APB3.0 interface
-  - Support calendar initial value configuration, configuration items including year, month, day, week, when, minutes and seconds
-  - Can read less than 1 second counter count, and the initial values can be configured, minimum scale unit for each calibration cycle of the crystals
-  - Support disruption: a timer interrupt (configurable project includes year, month, day, week,, minutes and seconds), the interrupt for level interrupts, need to register to clear; Periodic interruption (including annual, monthly, daily, weekly, every hour, every minute, every second, every 1/8 of a second, 1/64 of a second trigger interrupt) the interrupts for pulse, pulse width is two 32768 hz clock cycles
-  - Typical application scenario: calendar, timing interrupt trigger interrupt trigger, cycle
-  - Other features: a regular in the system domain, need external power supply; A low speed clock of 32768Hz is required
-
-- Mailbox
-
-  - Bus interface: Mailbox with APB 3.0 interface
-  - Data bit width: 32bit, configurable via APB bus
-  - Configuring the clock: configuring the clock to be the pclk clock
-  - Support for hardware locks
-  - Support for cpu0_sys and cpu1_sys to send interrupts to each other
-  - Support for register configuration and status reading of submodules
-
-- Temperature Sensor
-
-  - ±3°C Accuracy Without Trimming
-  - Supply voltages: VDD 0.72-0.88V, VDDA 1.62-1.98V
-  - Temperature Measurement Range: -40 ~ 125℃
-
-#### Video input
-
-- Compatible with MIPI 1.2 RX protocol, max up to three 2lane sensors or one 4lane sensor and one 2lane sensor
-- 3 x MIPI CSI
-- Support sensor slave mode
-- Support flash trigger mode which support both follow-strobe mode and pwm mode
-- Support structured light sensor and can separate the IR data and speckle data to different DVP interface.
-- Support timestamp
-- Support HDR sensor
-- Support hardware discard frame
-- 8/10/12/16 Bit Bayer RAW
-
-#### ISP
-
-- Total throughput：8MP@30fps
-- Auto Focus measurement (AF)
-- Auto White Balance measurement (AWB)
-- Auto Exposure measurement (AE)
-- Advanced 2DNR spatial noise reduction
-- Advanced 3DNR: spatial and temporal noise reduction
-- WDR in single wide dynamic frame
-- Multi-exposure HDR (Native/Built-in HDR interface, 12~16-bit HDR input). The performance is up to 2960x1666@60fps for DOL2 and 1920x1080@90fps for DOL3 HDR.
-- CPD, compand function to support native HDR sensor which performs HDR merging in sensor
-- Variable sensor interface for RGB-Bayer Sensors, DOL or stagger HDR sensors
-- 20-bit HDR Processing, includes multi exposure stitching and local tone mapping
-- Test Pattern Generator (TPG)
-- Black level Compensation
-- Sensor Linear Correction
-- Defect Pixel Cluster Correction (DPCC)
-- Green Equalization
-- Lens Shade Correction (De-Vignetting)
-- De-warping, including fisheye correction, wide field of view (FOV) correction, keystone correction and scaling and 4PTZ view
-- Digital Gain
-- 2-Stage Adaptive Noise Filter (Noise reduction, Sharpness, Blurring)
-- Enhanced Color Interpolation (Bayer De-mosaic filter)
-- Chromatic Aberration Correction (CAC)
-- Color Correction (Xtalk) Matrix (CCM)
-- Color Space Conversion (CSC)
-- Programmable gamma correction for sensor adaptation and display correction
-- Histogram Calculation
-- Anti-flicker
-- Cropping of the output picture (to crop interpolation artifacts), also used for windowing
-- Color Processing: Contrast, Saturation, Brightness, Hue (CPROC)
-- Sharpen/Blur Filter
-- Flash light control
-- Mechanical shutter control
-- Image size: horizontal size multiple of 8 and vertical size multiple of 4
-- Enhanced Chroma Noise Reduction (CNR)
-- Video Stabilization (VSM)
-- Multi-Context Management to support three sensors within a single ISP Core (MCM). In MCM mode, only DVP0 supports HDR
-
-#### Video output
-
-- 1 x MIPI DSI, 1 x 4 lane or 1 x 2 lane
-- Resolution: 2MP@60fps
-- Support up to 13 layers, including 4 video layers, 8 OSD layers and 1 background layer.
-- Support all common output picture formats: UXVGA (1600x1200), SXVGA (1280x1024), 1080p, 720p
-- Video Layer 0:
-  - support scaling up and scaling down function
-  - support 2-plane, YUV420 data format input
-  - support configurable start pixel & start line input
-  - Support 90 °, 180 °, 270 ° rotation
-  - Support x-mirror/y-mirror function.
-- Video Layer 1:
-  - support 2-plane, YUV420 data format input
-  - support configurable start pixel & start line input
-  - support 90 °, 180 °, 270 ° rotation
-  - Support x-mirror/y-mirror function.
-- Video Layer 2 & Layer 3:
-  - Support 2-plane, YUV420 & YUV422 data format input
-  - Support configurable start pixel & start line input
-  - Do not support scaling function
-- 8 OSD layers support 1 or 2 plane ARGB formats:
-  - RGB888 with separate alpha channel
-  - RGB565 with separate alpha channel
-  - ARGB8888
-  - ARGB4444
-  - ARGB1555
-  - Monochrome(8-bit)
-- Display mix:
-  - OSD layer support configurable global alpha blending or pixel by pixel alpha mode
-  - Video layer only support configurable global alpha
-  - Configurable output size and position for each layer
-- Support vsync interrupt, DPI interface underrun interrupt and configurable output line number interrupt
-- Support configurable color space conversion, yuv2rgb or rgb2yuv
-- Support gamma correction on RGB data before output
-- Support dither function
-
-  **Note**
-- When not using scaling, it is recommended to use layer1 (supports rotation but not scaling)/layer2 (does not support rotation and scaling)/layer3 (does not support rotation and scaling). The video layer can only use three layers
-- When scaling is necessary and layer0 is required, the maximum frame rate at 1080p is 20fps, and 30 frames can be supported at 720p
-
-#### video codec
-
-  **video encoding**
-  General encoding features
-
-- Maximum encoding performance up to 8MP@20fps
-- Stride support.
-- Horizontal and vertical mirroring.
-- CBR / VBR / CQP / ROI encoding
-- Support for optional rotation of the source frame in 90 degree steps before encoding. Note If YUV422 is rotated by 90 degrees or 270 degrees and not converted to YUV420, the result is encoded as YUV440.
-
-The video processor supports encoding the following source-frame input formats:
-
-- 1-plane YUV422, scan-line format, interleaved in YUYV or UYVY order. Note YUV422 inputs can be converted to YUV420 format.
-- 1-plane RGB, 8-bit, byte address order RGBA, BGRA, ARGB, or ABGR.
-- 2-plane YUV420, scan-line format, chroma interleaved in UV or VU order.
-- 3-plane YUV420, scan-line format.
-- 3-plane YUV420 10-in-16 bit scan line format. Note Support for 3-plane formats is included to help you with testing. Do not use these for maximum performance.
-- YUV420 10-bit, P010, little endian, MSB aligned.
-- YUV420 10-bit, 2 × 2 tile format.
-
-Supported codecs
-
-The following codec standards are supported for encoding:
-
-- HEVC (H.265) Main.
-- HEVC (H.265) Main 10 Profile.
-- H.264 Baseline Profile (BP).
-- H.264 Main Profile (MP).
-- H.264 High Profile (HP).
-- H.264 High 10 Profile.
-- JPEG, baseline sequential, YUV420 and YUV422. Note Only the JPEG codec can encode YUV422.
-- MJPEG
-
-HEVC (H.265) encoding features
-
-- The encoded bitstream complies with the HEVC (H.265) Main Profile.
-- Maximum frame width of 4,096 pixels.
-- Maximum frame height of 4,096 pixels.
-- 8-bit or 10-bit sample depth with I and P frames.
-- Progressive encoding with 64 × 64 CTU size.
-- Tiled mode, up to four tiles, horizontal splits only.
-- Wavefront parallel encoding.
-- The Motion Estimation (ME) search window is ±128 pixels horizontally, ±64 pixels vertically. - ME search down to Quarter Picture ELement (QPEL) resolution.
-- 8 × 8, 16 × 16, and 32 × 32 luma intra-modes.
-- 4 × 4, 8 × 8, and 16 × 16 chroma intra-modes.
-- 8 × 8, 16 × 16, and 32 × 32 inter-modes.
-- 8 × 8, 16 × 16, and 32 × 32 transform size for luma.
-- 4 × 4, 8 × 8, and 16 × 16 transform size for chromas.
-- Skipped CUs, Merge modes.
-- Deblocking.
-- Sample Adaptive Offset (SAO).
-- Constrained intra-prediction selectable.
-- Fixed Quantization Parameters (QP) operation or rate-controlled operation.
-- Rate controlled based on bitrate and buffer size settings. This is also known as leaky bucket.
-- Long term reference frame.
-- Selectable intra-frame refresh interval.
-- Encoders do not prevent the output from exceeding the maximum number of bits per CTU.
-
-H.264 encoding features
-
-- The encoded bitstream complies with the Baseline, Main, High, and High 10 Profiles.
-- Maximum frame width of 4,096 pixels.
-- Maximum frame height of 4,096 pixels.
-- I and P frames.
-- Progressive encoding.
-- Context Adaptive Binary Arithmetic Coding (CABAC) or Context Adaptive Variable Length Coding (CAVLC) entropy coding. Note B frames are not supported with CAVLC entropy coding.
-- The Motion Estimation (ME) search window is ±128 pixels horizontally, ±64 pixels vertically.
-- ME search down to Quarter Picture Element (QPEL) resolution.
-- All 4 × 4, 8 × 8, 16 × 16 luma, and 8 × 8 chroma intra-modes evaluated.
-- 8 × 8, and 16 × 16 inter-modes.
-- 4 × 4 and 8 × 8 transform.
-- Skipped macroblocks.
-- Deblocking.
-- Constrained intra-prediction selectable.
-- Fixed QP operation or rate-controlled operation.
-- Rate controlled based on bitrate and buffer size settings. This is also known as leaky bucket.
-- Long term reference frame.
-- Selectable intra-frame refresh interval.
-- Escaping to prevent Network Abstraction Layer (NAL) unit start code emulation. This is always enabled and is independent of the NAL packet format setting. For more information, see ITU-T H.264 Annex B. Note Encoders do not prevent the output from exceeding the maximum number of bits per macroblock.
-
-  **video decoding**
-  General decoding features
-
-- Maximum decoding performance up to 8MP@40fps
-- Supported source frame output formats are:
-  - 2 plane YUV420 scan line format, chroma interleaved in UV or VU order.
-  - 3 plane YUV420 scan line format. Note Support for 3-plane formats is included to help you with testing. Do not use these for maximum performance.
-  - YUV420 10 bit, P010, little endian, MSB aligned.
-  - YUV420 10 bit, 2 × 2 tile format. Note The YUV buffer and stride must have correct alignment for maximum performance.
-- Stride support for scan-line formats only.
-- Support for rotation of the decoded frame in 90 degree steps before output.
-- Support for downscaling the decoded frame horizontally and vertically by a factor of 2 or 4.
-- Support for downscaling the decoded frame horizontally and vertically by any factor individually. The smallest resolution can be 2 x 2 pixels.
-- Support for output of average frame luminance and chrominance for each 32 x 32 pixel block, for every output display frame.
-
-Supported codecs
-
-The following codec standards are supported for decoding:
-
-- HEVC (H.265) Main/Main10.
-- H.264 Baseline, Main, High, and High10 Progressive Profile.
-- JPEG, baseline sequential, YUV420 and YUV422. Note Only the JPEG codec can decode YUV422.
-
-HEVC (H.265) decoding features
-
-- The decoder is fully compliant to the Main and Main10 Profiles.
-- Maximum frame width is 4,096 pixels.
-- Maximum frame height is 4,096 pixels.
-- Error concealment is performed in case of bit errors.
-- Stream parameter information is output.
-
-H.264 decoding features
-
-- Baseline, Main, High, and High 10 progressive Profiles.
-- For progressive streams
-  - Average bitrates up to 100MBit/s.
-  - Maximum frame width is 4,096 pixels.
-  - Maximum frame height is 4,096 pixels.
-- For interlaced streams
-  - Average bitrates up to 50MBit/s.
-  - A maximum frame width of 2,048 pixels.
-  - A maximum frame height of 4,096 pixels.
-- Error concealment is performed in case of bit errors.
-- Stream parameter information is output. Escaping to prevent NAL unit start code emulation is always expected. This is independent of the NAL packet format setting. For more information, see ITU T H.264 Annex B.
-
-JPEG decoding features
-
-- Average bitrates up to 20MBit/s.
-- Support for 4:2:0 output by the video encoder, baseline sequential YYYYCbCr interleaved MCU format only.
-- Support for 4:2:2 output by the video encoder, baseline sequential YYCbCr interleaved MCU format only.
-- Maximum frame width is 8,192 pixels.
-- Maximum frame height is 8,192 pixels.
-- Error concealment is performed in case of bit errors.
-
-#### D GPU
-
-- Support following Hardware Components
-  - Command list based DMAs, Fire and Forgot Control mechanism to minimize CPU overhead
-  - Primitive Rasterizer, 16x Anti-aliasing without performance drop.
-  - Texture Mapping Unit, 4 Texel/cycle in Bi-linear filter
-  - Hardware composition, Frame buffer compression
-  - Tessellation, No CPU Involved in Bezier Curve generation
-  - Alpha blending
-- Support Image Transformation
-  - Texture mapping, Point sampling, Bilinear filtering
-  - Blit support, Stretch (independently on x and y axis)
-  - Rotation any angle, Mirroring, FP24 coordinate precision, no precision difference in any degree rotation
-  - 2.5D Perspective Correct Projections
-  - Configurable Coordinate Systems and Transformations (3x3 matrix)
-  - Scissoring and viewport clipping,  Mage Interpolation, Paint
-  - Odd/even and non-zero fill rules
-- Support draw engine
-  - Pixel / Line drawing with any degree
-  - Gradient Filled rectangles
-  - Triangles, Polygon
-  - Path Generation
-  - Linear gradient paint paths
-- Support following Color Formats
-  - 32-bit RGBA8888 / BGRA8888 / ABGR8888
-  - 16-bit RGBA5551 / RGB565
-  - 8-bit Α8 / L8 / RGB332,  4-bit A4 / L4 & 2-bit A2 / L2 & 1-bit A1 / L1
-  - 1/2/4/8-bit index format
-- Support Antialiasing
-  - 16x MSAA(4x4), no quality difference betwwen horizon and vertical direction
-  - 8x MSAA(4x2), low cost version, horizon quality is better than veritical directon
-
-#### Audio
-
-K230 audio supports the following features:
-
-- Audio codec inside
-- 2 DAC channels for stereo playback with sample rate 8-192Khz
-- 2 ADC channels for stereo recording from microphone with sample rate 8-192Khz
-- Audio codec support Automatic Level Control (ALC) function to adjust the signal level,which is input into ADC
-- Maximum 8 x PDM DMIC inputs
-- I2S interface supports 2x2 expansion
-- Support master mode, which means clock(pdm_clk and i2s_sclk) and ws(only I2S) are output from audio.
-- I2S input, pdm input and I2s output audio modes can work simultaneously
-- APB2.0 interface is used to configure registers, and read/write PCM data. The default frequency of configurable APB working clock PCLK is 100MHz, and the data interface is 32 bits
-- PCM data can be transferred by PDMA. Burst length in PDMA is configurable
-- The audio module can start working again after being disabled and re-enabled
-- The audio module can start working again after asserting reset and de-asserting reset
-- PDM audio
-  - PDM audio input with data sampling rate of 2.048/2.8224 MHz, 1-bit data width, sampling clock rate of 0.256MHz/0.384MHz/0.512MHz/0.768MHz/1.024MHz/1.4112MHz/1.536MHz/2.048MHz/2.8224MHz/3.072MHz/4.096MHz/5.6448MHz/6.144MHz/12.288MHz/24.576MHz, corresponding PCM sampling rate of 8kHz/12kHz/16kHz/24kHz/32kHz/44.1kHz/48kHz/96kHz/192kHz
-  - Oversampling rate is configurable with x128, x64 and x32
-  - 1-4 IOs are used for input PDM audio
-  - The input can be configured with 1-8 PDM channels. It supports left/right mono mode and dual mode of PDM. All IO channel modes are unified. The maximum number of IO in dual mode is 4
-  - The serial numbers of enabled channels are from small to big. Random enabling of each channel is not supported
-  - The skew between PDM input data and pdm_clk is up to 18 PCLK cycles
-  - Conversion from input PDM audio data to PCM audio data
-- I2S audio
-  - PCM audio in I2S Phillips, left-aligned and right-aligned format
-  - I2S audio input/output with data sampling rate of 8kHz/12kHz/16kHz/24kHz/32kHz/44.1kHz/48kHz/96kHz/192kHz, and data width of 32 bits. The valid data width(32/24/20/16/12bits) needs to be customized. The sampling clock rate supports 2×32(data width)×data sampling rate
-  - 1-2 IO to input, and 1-2 IO to output I2S audio data. The full-duplex mode is supported
-  - Connect to on-chip or off-chip i2s codec to input and output audio data
-  - Each RX/TX channel FIFO depth is 8. FIFO threshold can be configured
-  - DMA mode enable and disable
-  - IO number and left/right channel flag can be fetched from higher bits of data when valid data width is less than 32bits in DMA mode
-
-#### peripheral
-
-- UART
-  - Support 5 UART interface
-  - 9-bit serial data support
-  - False start bit detection
-  - Programmable fractional baud rate support
-  - APB data bus widths of 32
-  - Additional DMA interface signals for compatibility with DMA interface, DMA interface signal active low
-  - Transmit and receive FIFO depths of 32, Supports 32x32-bit transmit first-in, first-out (FIFO) and 32x32-bit RX FIFO, Internal FIFO (RAM)
-  - Busy functionality
-  - Functionality based on the 16550 industry standard
-    - Programmable character properties, such as:
-      - Number of data bits per character (5-8)
-      - Optional parity bit (with odd, even select or Stick Parity)
-      - Number of stop bits (1, 1.5 or 2)
-    - Line break generation and detection
-    - DMA signaling with two programmable modes
-    - Prioritized interrupt identification
-  - Programmable FIFO enable/disable
-  - Separate system resets for each clock domain to prevent metastability
-
-- I2C
-  - Support 5 I2C interface
-  - Two-wire I2C serial interface–consists of a serial data line (SDA) and a serial clock (SCL)
-  - Three speeds:
-    - Standard mode (0 to 100 Kb/s)
-    - Fast mode (≤400 Kb/s) or fast mode plus (≤1000 Κb/s)
-    - High-speed mode (≤3.4 Mb/s)
-  - Clock synchronization
-  - Master I2C
-  - 7- or 10-bit addressing
-  - 7- or 10-bit combined format transfers
-  - Bulk transmit mode
-  - Transmit and receive buffers
-    - 32x32 bits TX FIFOs and 64x8 bits RX FIFOs
-  - Interrupt or polled-mode operation
-  - Handles Bit and Byte waiting at all bus speeds
-  - DMA operation.
-  - Programmable SDA hold time (tHD;DAT)
-  - Bus clear feature
-  - Device ID feature
-  - Support for APB data bus widths of 32 bits
-
-- PWM
-
-  - Support 6 channel
-  - Interface of APB 3.0, width 32 bit data; Slave Error response is not supported
-  - Support arbitrary duty ratio
-  - Support programmable output waveform (support two adjacent channel output waveform and even)
-  - Support produce periodic pulse signal of pulse signal and one-time
-  - Precise interruption generator can be used as a cycle
-  - Support output burr elimination
-
-- GPIO (multiplexed with function pins):
-  - 64 x GPIO + 8 x PMU GPIO
-  - 50 x GPIO + 6 x PMU GPIO(SIP)
-  - Separate data registers and data direction registers for each signal
-  - Configurable hardware and software control for each signal, or for each bit of each signal Separate auxiliary data input, data output, and data control for each I/O in Hardware Control mode. As output, each GPIO can be set to 0 or 1 separately.
-  - Independently controllable signal bits
-  - Configurable interrupt mode for GPIO group0 and GPIO group1. As input, each GPIO pin can act as an interrupt source.  IO both edge interrupts.
-  - Configurable debounce logic with an external slow clock to debounce interrupts
-  - Option to generate single or multiple interrupts
-  - Configurable reset values on output signals
-  - Configurable synchronization of interrupt signals
-  - 32-bit APB width
-
-- USB
-
-  - Support 2 USB 2.0 OTG
-  - Support for the following speeds:High-Speed (HS, 480-Mbps),Full-Speed (FS, 12-Mbps) and Low-Speed (LS, 1.5-Mbps) modes
-  - Multiple options available for low power operations
-  - DMA mode access support on the application side
-  - Supports up to 6 bidirectional endpoints, including control endpoint 0
-  - Supports the Keep-Alive in Low-Speed mode and SOFs in High/Full-Speed modes
-  - The USB 2.0 modules supports the following transfer types:Control transfer,Bulk transfer,Interrupt transfer,isochronous transfer
-  - Internal DMA mode has two modes of operation: Buffer DMA mode and Scatter/Gather DMA mode
-  - Total Data FIFO RAM Depth is 3072
-  - Not support ADP/HNP/SRP/Battery Charger
-
-- SD/EMMC
-  - Support 2 SDxC: SD3.01, eMMC 5.0
-  - The eMMC/SD/SDIO controller features as below.
-
-    - Supports SD memory and SD Input/Output (SDIO) digital interface protocol, and compliant with SD HCI specification
-    - Uses the same SD-HCI register set for eMMC transfers
-    - Supports eMMC protocols including eMMC 5.1
-    - Supports SD-HCI Host version 3 mode or less
-    - Supports the following data transfer types for SD, eMMC modes:
-      - CPU
-      - SDMA
-      - ADMA2
-      - ADMA3
-    - Supports independent controller, AMBA Slave interface and Master Interface clocks
-    - Supports gating of controller base clock if Host Controller is inactive
-    - Support context aware functional clock gates
-    - Applications can gate the slave interface clock if Host Controller is inactive
-    - Supports interrupt enabling and masking
-    - Supports Command Queuing Engine (CQE) and compliant with eMMC CQ HCI
-    - Programmable scheduler algorithm selection of task execution
-    - Supports data prefetch for back-to-back WRITE operations
-    - Supports auto-tuning
-    - Support clock gating
-
-  - Support features for interfaces
-
-    - SD
-      - Supports 4-bit interface
-      - Supports UHS-I mode
-      - Supports Default Speed (DS), high-speed (HS), SDR12, SDR25, SDR50 and SDR104 speed modes
-      - Supports SDIO read wait
-      - Supports SDIO card interrupts in both 1-bit and 4-bit modes
-      - Wake up on card interrupt
-    - eMMC
-      - Supports 4-bit/8-bit interface
-      - Supports legacy, high-speed SDR, high-speed DDR, HS200, and HS400 speed modes
-      - Supports boot operation and alternative boot operation
-
-- SPI
-  - Support 3 SPI interface : 1 x OSPI + 2 x QSPI
-  - Supports AHB Slave Interface for software programming(AMBA 3)
-  - Supports AXI Master Interface for Internal DMA transfers
-    - AMBA 3 AXI
-    - AXI data width : 64
-    - AXI address width : 32
-  - Supports two separate FIFOs. One acts as an RX FIFO and the other one acts as a TX FIFO. Each of them is 256-location deep
-  - Enhanced SPI features (Dual/Quad/Octal for OSPI, Dual/Quad for QSPI)
-  - Programmble address,instruction,wait cycles,and data frame size
-  - Supports programmable serial data frame length: 4 bits to 32 bits
-  - Programmable delay on the sample time of received serial data bit(rxd)
-  - Programmable clock bit rate
-
-#### security
-
-- Support PUF / OTP / TRNG
-- Support following symmetric algorithm
-  - AES128/192/256
-  - CMAC128/192/256
-  - SM4-128
-
-- Support following asymmetric algorithm
-  - RSA-1024/2048/3072/4096
-  - RSA encrypt/decrypt/signature/verify
-  - ECC-163/233/283/409/571/192/224/256/384/521
-  - ECDSA-233/283/409/571/224/256/384/521
-  - ECC CDH-163/233/283/409/571/192/224/256/384/521
-  - SM2 encrypt/decrypt/signature/verify
-
-- Support following hash algorithm
-  - HMAC
-  - SHA224/256/384/512, SHA_512/224, SHA_512/256
-  - SM3
-
-- TRNG
-  - 160Mbps@20Mhz
-  - Stabilization time minimum than 50us
-
-- OTP program region has raw OTP density 32Kbits, with security protection
-- Support security boot with signature
-
-#### PMU
-
-- Support RTC function in 32Khz
-- Support the default 6 inputs and 2 outputs
-- Support IO configurable, reusable as GPIOs, the highest rate of up to 25 MHZ
-- Support a set of long and short press detection function which can be used as system shutdown or wakeup signal
-- Support a set of edge number counter which can be regularly cleared
-- Support two sets of edge and level detection with debounce function
-- Support four groups of edge and level detection
-- Support configurable interrupt operation
-- Support 512 bits system log when it is been shutdown
-- Support two sets of output IOs with configurable delay time
-
-#### Others
-
-- decompression
-
-  - Decompression accelerator is mainly used to implement hardware GZIP decompression function.
-  - Decompression bandwidth ≥ 400MB/s
-  - Support GZIP file format version 4.3
-  - Support DEFLATE compressed file version 1.3
-  - The maximum dictionary size is 32KB
-  - Support the minimum word matching length of 3Byte and the maximum word matching length of 258Byte
-  - Only dynamic huffman compression mode is supported
-  - Support data stream CRC32 verification
-  - Support hardware to automatically generate dynamic huffman tree
-  - The APB3 register interface is used to configure the startup decompression accelerator
-  - Request the DMA controller to transfer large blocks through hardware, and request to transfer 32Kbyte at most once
-
-- FFT/IFFT
-
-  - Support maximum 4096 point fft, ifft calculation
-  - Support int16 calculation accuracy, the real and imaginary parts of input and output are both in int16 format
-  - Support the standard axi4 slave interface, which is used for parameter configuration and data transfer.
-  - The input supports RIRI...., RRRR.... (singal real part), RRRR...IIII... format arrangement, and the output supports RIRI...., RRRR...IIII... format arrangement
-  - It adopts the calculation method of base 2-time decimation, and there is only one butterfly operator inside
-  - A single clock domain design is adopted, and the bus clock is also used as the operation clock
-  - The calculation time of 4096-point fft/ifft is controlled within 1ms, including the total overhead of data movement, calculation, and interrupt interaction
-  - Support interrupt mask, original interrupt query
-
-- Fastboot: 3A first picture ≤ 400ms
-- Working environment temperature: -40 ~ 85°C
-
-### Block Diagram
-
-<div align=center>Figure 1-3-1 K230 block diagram</div>
-
-![K230_block_diagram.png](../../zh/00_hardware/images/K230_block_diagram.png)
-
-## Chapter 2 Package Information
-
-K230 have two types of package, one is K230 that has a single die, the other is K230D that merges a 1Gb LPDDR4.
-
-## K230
-
-<div align=center>Figure 2-1-1 K230 Package</div>
-
-![K230_package](../../zh/00_hardware/images/K230_package.png)
-
-### K230D
-
-<div align=center>Figure 2-2-1 K230D Package</div>
-
-![K230_package](../../zh/00_hardware/images/K230D_package.png)
-
-### Pin information description
-
-This part please refer to《K230_PINOUT_V1.0_20230524》document.
-
-## chapter 3 Electrical Specification
-
-### Absolute Max Rating
-
-<div align=center>Table 3-1-1 Absolute Max Rating</div>
-
-|              | Power Parameter | Min  | Max             | Units |
-| ------------ |:--------------- | ---- | --------------- | ----- |
-| PMU          | AVDD1P8_RTC     | -0.1 | 1.98            | V     |
-| PMU          | AVDD1P8_LDO     | -0.1 | 1.98            | V     |
-| CORE         | VDD0P8_CORE     | -0.1 | 0.88            | V     |
-| CPU          | VDD0P8_CPU      | -0.1 | 0.88            | V     |
-| KPU          | VDD0P8_KPU      | -0.1 | 0.88            | V     |
-| DDR          | VDD0P8_DDR_CORE | -0.1 | 0.88            | V     |
-| DDR          | VDD1P1_DDR_IO   | -0.1 | 1.21/1.32/1.485 | V     |
-| DDR          | VAA_DDR         | -0.1 | 1.98            | V     |
-| IO           | VDDIO3P3_0      | -0.1 | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_1      | -0.1 | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_2      | -0.1 | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_3      | -0.1 | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_4      | -0.1 | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_5      | -0.1 | 1.98/3.63       | V     |
-| USB          | AVDD3P3_USB     | -0.1 | 3.63            | V     |
-| USB          | AVDD1P8_USB     | -0.1 | 1.98            | V     |
-| PLL          | AVDD0P8_PLL     | -0.1 | 0.88            | V     |
-| MIPI         | AVDD0P8_MIPI    | -0.1 | 0.88            | V     |
-| MIPI         | AVDD1P8_MIPI    | -0.1 | 1.98            | V     |
-| ADC          | AVDD1P8_ADC     | -0.1 | 1.98            | V     |
-| AUDIO CODEC  | AVDD1P8_CODEC   | -0.1 | 1.98            | V     |
-| MMC          | VDD3P3_SD       | -0.1 | 3.63            | V     |
-| SYSTEM       | VDD1P8          | -0.1 | 1.98            | V     |
-| K230D LPDDR4 | VDD1P8_DDR_VDD1 | -0.1 | 1.98            | V     |
-| K230D LPDDR4 | VDD1P1_DDR_VDD2 | -0.1 | 1.21            | V     |
-| K230D LPDDR4 | VDD1P1_DDR_VDDQ | -0.1 | 1.21            | V     |
-
-### Recommended Operating Condition
-
-<div align=center>Table 3-2-1 Recommended operating conditions for power supplies</div>
-
-| Module       | Parameter       | Min             | Typical      | Max             | Units |
-| ------------ |:--------------- | --------------- | ------------ | --------------- | ----- |
-| PMU          | AVDD1P8_RTC     | 1.674           | 1.8          | 1.98            | V     |
-| PMU          | AVDD1P8_LDO     | 1.674           | 1.8          | 1.98            | V     |
-| CORE         | VDD0P8_CORE     | 0.72            | 0.8          | 0.88            | V     |
-| CPU          | VDD0P8_CPU      | 0.72            | 0.8          | 0.88            | V     |
-| KPU          | VDD0P8_KPU      | 0.72            | 0.8          | 0.88            | V     |
-| DDR          | VDD0P8_DDR_CORE | 0.744           | 0.8          | 0.88            | V     |
-| DDR          | VDD1P1_DDR_IO   | 1.06/1.14/1.283 | 1.1/1.2/1.35 | 1.21/1.32/1.485 | V     |
-| DDR          | VAA_DDR         | 1.674           | 1.8          | 1.98            | V     |
-| IO           | VDDIO3P3_0      | 1.62/2.97       | 1.8/3.3      | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_1      | 1.62/2.97       | 1.8/3.3      | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_2      | 1.62/2.97       | 1.8/3.3      | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_3      | 1.62/2.97       | 1.8/3.3      | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_4      | 1.62/2.97       | 1.8/3.3      | 1.98/3.63       | V     |
-| IO           | VDDIO3P3_5      | 1.62/2.97       | 1.8/3.3      | 1.98/3.63       | V     |
-| USB          | AVDD3P3_USB     | 3.07            | 3.3          | 3.63            | V     |
-| USB          | AVDD1P8_USB     | 1.674           | 1.8          | 1.98            | V     |
-| PLL          | AVDD0P8_PLL     | 0.72            | 0.8          | 0.88            | V     |
-| MIPI         | AVDD0P8_MIPI    | 0.744           | 0.8          | 0.88            | V     |
-| MIPI         | AVDD1P8_MIPI    | 1.674           | 1.8          | 1.98            | V     |
-| ADC          | AVDD1P8_ADC     | 1.62            | 1.8          | 1.98            | V     |
-| AUDIO CODEC  | AVDD1P8_CODEC   | 1.62            | 1.8          | 1.98            | V     |
-| MMC          | VDD3P3_SD       | 2.7             | 3.3          | 3.63            | V     |
-| SYSTEM       | VDD1P8          | 1.62            | 1.8          | 1.98            | V     |
-| K230D LPDDR4 | VDD1P8_DDR_VDD1 | 1.7             | 1.8          | 1.98            | V     |
-| K230D LPDDR4 | VDD1P1_DDR_VDD2 | 1.06            | 1.1          | 1.21            | V     |
-| K230D LPDDR4 | VDD1P1_DDR_VDDQ | 1.06            | 1.1          | 1.21            | V     |
-
-### DC Characteristics
-
-#### Electrical Characteristics for General IO
-
-<div align=center>Table 3-3-1 Electrical Characteristics for General IO</div>
-
-![GPIO_ecectric](../../zh/00_hardware/images/GPIO_electric.png)
-
-#### Electrical Characteristics for PLL
-
-<div align=center>Table 3-3-2 Electrical Characteristics for PLL</div>
-
-| Parameter | Description                       | Min  | Type | Max | Units                     |
-| --------- | --------------------------------- | ---- | ---- | --- | ------------------------- |
-| Fref      | Divided reference frequency range | 488K |      | 4G  | Hz                        |
-| Fout      | Total output frequency range      | 50M  | NA   | 4G  | Hz                        |
-| Fvco      | VCO frequency range               | 800M | NA   | 4G  | Hz                        |
-| Tlt       | Lock time                         | 500  |      |     | div referency clock cycle |
-| Ijitter   | input jitter                      |      | 2%   |     | div referency clock cycle |
-
-### Electrical Characteristics for DDR
-
-<div align=center>Table 3-3-3 common DC input conditions </div>
-
-| Parameter                                         | Symbol | Unit | Minimum   | Typical | Maximum   |
-| ------------------------------------------------- | ------ | ---- | --------- | ------- | --------- |
-| Vref input leakage current                        | IIZ    | uA   |           |         | 50        |
-| BP_DAT input leakage current                      | IIZ    | uA   |           |         | 50        |
-| Input high voltage for BP_DAT*                    | VIH-DC | V    | Vref+0.02 |         |           |
-| Input low voltage for BP_DAT*                     | VIL-DC | V    |           |         | Vref-0.02 |
-| Differential input voltage for abs(DQS_t – DQS_c) | VID-DC | V    | 0.1       |         |           |
-|                                                   |        |      |           |         |           |
-| Note：                                             |        |      |           |         |           |
-
-1. BP_DAT *represent the DDR_DQ* Pins
-1. BP_A *represent the DDR_CA* Pins
-
-<div align=center>Table 3-3-4 common AC input conditions </div>
-
-| Parameter                     | Symbol  | Unit | Minimum | Typical | Maximum |
-| ----------------------------- | ------- | ---- | ------- | ------- | ------- |
-| Input capacitance DQ          | CpadDQ  | pF   | 1.54    | 1.62    | 1.76    |
-| Input capacitance DQS         | CpadDQS | pF   | 1.44    | 1.56    | 1.66    |
-| Input capacitance,address/cmd | CpadAC  | pF   | 1.71    | 1.81    | 1.94    |
-|                               |         |      |         |         |         |
-| Note：                         |         |      |         |         |         |
-
-1. This is specified at the top level of the DBYTE and ACX4 blocks. It does not include any customer-supplied routing between these blocks and the C4 bump.
-1. Effective parallel capacitance when ODT of 60ohm is enabled。
-
-<div align=center>Table 3-3-5 common input conditions </div>
-
-| Parameter                                    | Symbol         | Unit | Minimum | Maximum |
-| -------------------------------------------- | -------------- | ---- | ------- | ------- |
-| M_DQ edge arrival relative to M_DQS,800MT/s  | tDQSDQRead800  | UI   | -0.39   | 0.39    |
-| M_DQ edge arrival relative to M_DQS,1066MT/s | tDQSDQRead1066 | UI   | -0.38   | 0.38    |
-| M_DQ edge arrival relative to M_DQS,1333MT/s | tDQSDQRead1333 | UI   | -0.37   | 0.37    |
-| M_DQ edge arrival relative to M_DQS,1600MT/s | tDQSDQRead1600 | UI   | -0.36   | 0.36    |
-| M_DQ edge arrival relative to M_DQS,1866MT/s | tDQSDQRead1866 | UI   | -0.35   | 0.35    |
-| M_DQ edge arrival relative to M_DQS,2133MT/s | tDQSDQRead2133 | UI   | -0.34   | 0.34    |
-| M_DQ edge arrival relative to M_DQS,2400MT/s | tDQSDQRead2400 | UI   | -0.33   | 0.33    |
-| M_DQ edge arrival relative to M_DQS,2667MT/s | tDQSDQRead2667 | UI   | -0.32   | 0.32    |
-| M_DQ edge arrival relative to M_DQS,3200MT/s | tDQSDQRead3200 | UI   | -0.31   | 0.31    |
-
-Note：
-
-1. This timing parameter applies to all BP_DAT DQ bits within a related DQ byte
-1. A larger range implies more margin for channel and DRAM timing effects
-1. Per lane deskew training can correct for static skew, up to deskew limits
-1. Refer to the receiver timing budget in the Signal and Power Integrity Application Note for more information
-
-<div align=center>Table 3-3-6 LPDDR3 DC input conditions </div>
-
-| Parameter                                         | Symbol     | Unit | Minimum                      | Typical  | Maximum |
-| ------------------------------------------------- | ---------- | ---- | ---------------------------- | -------- | ------- |
-| Reference voltage                                 | Vref       | V    |                              | Variable |         |
-| DC reference voltage error                        | VrefDC-err | VDDQ | -0.75%                       |          | 0.75%   |
-| On-die termination (ODT) programmable resistances | RTT        | ohm  | open, 240,120, 80, 60,48, 40 |          |         |
-| ODT low-level (0.5*VDDQ) largesignal resistance   | RODT-L/RTT |      | 0.9                          | 1.0      | 1.1     |
-| ODT mid-level (0.8*VDDQ) largesignal resistance   | RODT-M/RTT |      | 0.8                          |          | 1.05    |
-| ODT high-level (1.1*VDDQ) largesignal resistance  | RODT-H/RTT |      | 0.75                         |          | 1.05    |
-
-<div align=center>Table 3-3-7 LPDDR3 AC input conditions </div>
-
-| Parameter                                            | Symbol        | Unit | Minimum      | Typical | Maximum      |
-| ---------------------------------------------------- | ------------- | ---- | ------------ | ------- | ------------ |
-| Reference voltage                                    | VrefAC-err    | VDDQ | -0.25%       |         | 0.25%        |
-| Low-speed Input high voltage for BP_DAT (logic 1)    | VIH-ACLS      | V    | Vref + 0.070 |         | VDDQ +0.15   |
-| Low-speed Input low voltage for BP_DAT (logic 0)     | VIL-ACLS      | V    | -0.15        |         | Vref - 0.070 |
-| High-speed input high voltage for BP_DAT (logic 1)   | VIH-ACHS      | V    | Vref + 0.070 |         | Vref + 0.440 |
-| High-speed input low voltage for BP_DAT (logic 0)    | VIL-ACHS      | V    | Vref - 0.440 |         | Vref - 0.070 |
-| ODT low-level (0.5*VDDQ) smallsignal resistance      | RODTss-M /RTT |      | 0.95         |         | 1.75         |
-| ODT mid-level (0.8*VDDQ) smallsignal resistance      | RODTss-M /RTT |      | 0.85         |         | 1.05         |
-| ODT high-level (1.1*VDDQ) smallsignal resistance     | RODTss-H /RTT |      | 0.75         |         | 1.05         |
-| Input crossing voltage for differential signals DQS* | VIX           | mV   | VDQSavg-75   | VDQSavg | VDQSavg +75  |
-
-<div align=center>Table 3-3-8 LPDDR4 DC input conditions </div>
-
-| Parameter                                         | Symbol     | Unit | Minimum                      | Typical  | Maximum |
-| ------------------------------------------------- | ---------- | ---- | ---------------------------- | -------- | ------- |
-| Reference voltage                                 | Vref       | V    |                              | Variable |         |
-| DC reference voltage error                        | VrefDC-err | VDDQ | -0.75%                       |          | 0.75%   |
-| On-die termination (ODT) programmable resistances | RTT        | ohm  | open, 240,120, 80, 60,48, 40 |          |         |
-| ODT mid-level (0.25*VDDQ) largesignal resistance  | RODT-M/RTT |      | 0.8                          |          | 1.1     |
-| ODT high-level (0.5*VDDQ) largesignal resistance  | RODT-H/RTT |      | 0.9                          | 1.0      | 1.1     |
-
-<div align=center>Table 3-3-9 LPDDR4 AC input conditions </div>
-
-| Parameter                                            | Symbol        | Unit | Minimum      | Typical | Maximum      |
-| ---------------------------------------------------- | ------------- | ---- | ------------ | ------- | ------------ |
-| Reference voltage                                    | VrefAC-err    | VDDQ | -0.25%       |         | 0.25%        |
-| Low-speed Input high voltage for BP_DAT (logic 1)    | VIH-ACLS      | V    | Vref + 0.070 |         | VDDQ +0.15   |
-| Low-speed Input low voltage for BP_DAT (logic 0)     | VIL-ACLS      | V    | -0.15        |         | Vref - 0.070 |
-| High-speed input high voltage for BP_DAT (logic 1)   | VIH-ACHS      | V    | Vref + 0.070 |         | Vref + 0.440 |
-| High-speed input low voltage for BP_DAT (logic 0)    | VIL-ACHS      | V    | Vref - 0.440 |         | Vref - 0.070 |
-| ODT mid-level (0.25*VDDQ) smallsignal resistance     | RODTss-M /RTT |      | 0.9          |         | 1.1          |
-| ODT high-level (0.5*VDDQ) smallsignal resistance     | RODTss-H /RTT |      | 0.95         |         | 1.75         |
-| Input crossing voltage for differential signals DQS* | VIX           | mV   | VDQSavg-75   | VDQSavg | VDQSavg +75  |
-
-#### Electrical Characteristics for MIPI DSI
-
-<div align=center>Table 3-3-10 Supply Requirements</div>
-
-| Symbol | Parameter          | Condition | Minimum | Typical | Maximum | Unit |
-| ------ | ------------------ | --------- | ------- | ------- | ------- | ---- |
-| Vslew  | Supplies slew rate |           |         |         | 0.1     | V/μs |
-
-<div align=center>Table 3-3-11 Input DC Specifications</div>
-
-| Symbol                             | Parameter                                | Condition                                                                   | Minimum | Typical | Maximum | Unit |
-| ---------------------------------- | ---------------------------------------- | --------------------------------------------------------------------------- | ------- | ------- | ------- | ---- |
-| Apply to CLKP/N and DATAP/N Inputs |                                          |                                                                             |         |         |         |      |
-| VI                                 | Input signal voltage range               |                                                                             | -50     |         | 1350    | mV   |
-| ILEAK                              | Input leakage current                    | VGNDSH(min) ≤ VI ≤ VGNDSH(max) + VOH(absmax) Lane module in LP receive mode | -10     |         | 10      | μA   |
-| VGNDSH                             | Ground shift                             |                                                                             | -50     |         | 50      | mV   |
-| VOH(absmax)                        | Maximum transient output voltage level   |                                                                             | -0.15   |         | 1.45    | V    |
-| tVOH(absmax)                       | Maximum transient time above VOH(absmax) |                                                                             |         |         | 20      | ns   |
-
-<div align=center>Table 3-3-12 HS Line Drivers DC Specifications</div>
-
-| Symbol           | Parameter                                                               | Condition                                                                                          | Minimum | Typical | Maximum | Unit |
-| ---------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ------- | ------- | ------- | ---- |
-| &#124;VOD&#124;  | HS Transmit Differential output voltage magnitude                       | 80 Ω ≤ RL ≤ 125 Ω Note: can be programmed using test control register 0x24(cb_sel_v400_prog[2:0]). | 140     | 200     | 270     | mV   |
-| ∆&#124;VOD&#124; | Change in Differential output voltage magnitude between logic states    | 80 Ω ≤ RL ≤ 125 Ω                                                                                  |         |         | 14      | mV   |
-| VCMTX            | Steady-state common-mode output voltage                                 | 80 Ω ≤ RL ≤ 125 Ω                                                                                  | 150     | 200     | 250     | mV   |
-| ∆VCMTX(1,0)      | Changes in steady-state common-mode output voltage between logic states | 80 Ω ≤ RL ≤ 125 Ω                                                                                  |         |         | 5       | mV   |
-| VOHHS            | HS output high voltage                                                  | 80 Ω ≤ RL ≤ 125 Ω                                                                                  |         |         | 360     | mV   |
-| ZOS              | Single-ended output impedance                                           |                                                                                                    | 40      | 50      | 62.5    | Ω    |
-| ∆ZOS             | Single-ended output impedance mismatch                                  |                                                                                                    |         |         | 10      | %    |
-
-<div align=center>Table 3-3-13 LP Line Drivers DC Specifications</div>
-
-| Symbol       | Parameter                                                     | Minimum | Typical | Maximum | Unit |
-| ------------ | ------------------------------------------------------------- | ------- | ------- | ------- | ---- |
-| VOL          | Output low-level SE voltage                                   | -50     |         | 50      | mV   |
-| VOH          | Output high-level SE voltage                                  | 1.1     | 1.2     | 1.3     | V    |
-| ZOLP         | Single-ended output impedance                                 | 110     |         |         | Ω    |
-| ∆ZOLP(01,10) | Single-ended output impedance mismatch driving opposite level |         |         | 20      | %    |
-| ∆ZOLP(00,11) | Single-ended output impedance mismatch driving same level     |         |         | 5       | %    |
-
-<div align=center>Table 3-3-14 LP Line Receiver DC Specifications</div>
-
-| Symbol   | Parameter                      | Minimum | Typical | Maximum | Unit |
-| -------- | ------------------------------ | ------- | ------- | ------- | ---- |
-| VIL      | Input low voltage, not in ULPS |         |         | 550     | mV   |
-| VIL-ULPS | Logic 0 input voltage, ULPS    |         |         | 300     | mV   |
-| VIH      | Input high voltage             | 740     |         |         | mV   |
-| VHYST    | Input hysteresis               | 25      |         |         | mV   |
-
-<div align=center>Table 3-3-15 Contention Line Receiver DC Specifications</div>
-
-| Symbol | Parameter                  | Minimum | Typical | Maximum | Unit |
-| ------ | -------------------------- | ------- | ------- | ------- | ---- |
-| VILF   | Input low fault threshold  |         |         | 200     | mV   |
-| VIHF   | Input high fault threshold | 450     |         |         | mV   |
-
-#### Electrical Characteristics for MIPI CSI
-
-<div align=center>Table 3-3-16 Supply Requirements</div>
-
-| Symbol | Parameter          | Condition | Minimum | Typical | Maximum | Unit |
-| ------ | ------------------ | --------- | ------- | ------- | ------- | ---- |
-| Vslew  | Supplies slew rate | --        | --      | --      | 0.1     | V/μs |
-
-<div align=center>Table 3-3-17 Input DC Specifications</div>
-
-| Symbol                             | Parameter                                | Minimum | Typical | Maximum | Unit | Notes                                                                                                                                                                                                                                             |
-| ---------------------------------- | ---------------------------------------- | ------- | ------- | ------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Apply to CLKP/N and DATAP/N Inputs |                                          |         |         |         |      |                                                                                                                                                                                                                                                   |
-| VPIN                               | Pin signal voltage range                 | -50     |         | 1350    | mV   |                                                                                                                                                                                                                                                   |
-| ILEAK                              | Pin leakage current                      | -10     |         | 10      | µA   | VGNDSH(min) ≤ VPIN ≤ VGNDSH(max) + VOH(absmax) Lane module in LP receive mode                                                                                                                                                                     |
-| VGNDSH                             | Ground shift                             | -50     |         | 50      | mV   |                                                                                                                                                                                                                                                   |
-| VPIN(absmax)                       | Maximum transient output voltage level   | -0.15   |         | 1.45    | V    |                                                                                                                                                                                                                                                   |
-| VPIN(absmax)                       | Maximum transient time above VOH(absmax) |         |         | 20      | ns   | The voltage overshoot and undershoot beyond the VPIN is only allowed during a single 20ns window after any LP-0 to LP-1  transition or vice versa. For all other situations the voltage overshoot and undershoot must stay within the VPIN range. |
-
-<div align=center>Table 3-3-18 HS Line Receiver DC Specifications</div>
-
-| Symbol  | Parameter                                 | Minimum | Typical | Maximum | Unit | Notes                                                                                                                                                                                                                                                   |
-| ------- | ----------------------------------------- | ------- | ------- | ------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| VIDTH   | Differential input high voltage threshold |         |         | 70      | mV   | D-PHY spec 1.1 compatibility mode (<=1.5Gbps)                                                                                                                                                                                                           |
-| VIDTH   | Differential input high voltage threshold |         |         | 40      | mV   | In case of High-Speed deskew calibration (>1.5Gbps)                                                                                                                                                                                                     |
-| VIDTL   | Differential input low voltage threshold  | -70     |         |         | mV   | D-PHY spec 1.1 compatibility mode (<=1.5Gbps)                                                                                                                                                                                                           |
-| VIDTL   | Differential input low voltage threshold  | -40     |         |         | mV   | In case of High-Speed deskew calibration (>1.5Gbps)                                                                                                                                                                                                     |
-| VIHHS   | Single ended input high voltage           |         |         | 460     | mV   | Excluding possible additional RF interference of 100mV peak sine wave beyond 450MHz                                                                                                                                                                     |
-| VILHS   | Single ended input low voltage            | -40     |         |         | mV   | Excluding possible additional RF interference of 100mV peak sine wave beyond 450MHz                                                                                                                                                                     |
-| VCMRXDC | Input common mode voltage                 | 70      |         | 330     | mV   | Excluding possible additional RF interference of 100mV peak sine wave beyond 450MHz. This table value includes a ground difference of 50mV between the transmitter and the receiver, the static common-mode level tolerance and variations below 450MHz |
-| ZID     | Differential input impedance              | 80      | 100     | 125     | Ω    |                                                                                                                                                                                                                                                         |
-
-<div align=center>Table 3-3-19 LP Line Drivers DC Specifications</div>
-
-| Symbol       | Parameter                                                     | Minimum | Typical | Maximum | Unit |
-| ------------ | ------------------------------------------------------------- | ------- | ------- | ------- | ---- |
-| VOL          | Output low-level SE voltage                                   | -50     |         | 50      | mV   |
-| VOH          | Output high-level SE voltage                                  | 1.1     | 1.2     | 1.3     | V    |
-| ZOLP         | Single-ended output impedance                                 | 110     |         |         | Ω    |
-| ∆ZOLP(01,10) | Single-ended output impedance mismatch driving opposite level |         |         | 20      | %    |
-| ∆ZOLP(00,11) | Single-ended output impedance mismatch driving same level     |         |         | 5       | %    |
-
-<div align=center>Table 3-3-20 LP Line Receiver DC Specifications</div>
-
-| Symbol   | Parameter                   | Minimum | Typical | Maximum | Unit |
-| -------- | --------------------------- | ------- | ------- | ------- | ---- |
-| VIL      | Input low voltage           |         |         | 550     | mV   |
-| VIH      | Input high voltage          | 740     |         |         | mV   |
-| VIL-ULPS | Logic 0 input voltage, ULPS |         |         | 300     | mV   |
-| VHYST    | Input hysteresis            | 25      |         |         | mV   |
-
-<div align=center>Table 3-3-21 Contention Line Receiver DC Specifications</div>
-
-| Symbol | Parameter                  | Minimum | Typical | Maximum | Unit |
-| ------ | -------------------------- | ------- | ------- | ------- | ---- |
-| VILF   | Input low fault threshold  |         |         | 200     | mV   |
-| VIHF   | Input high fault threshold | 450     |         |         | mV   |
-
-### Electrical Characteristics for USB
-
-<div align=center>Table 3-3-22 Electrical Characteristics for USB</div>
-
-| Parameter                                                                    | Symbol  | Test Condition                                        | Min       | Max   | Unit |
-| ---------------------------------------------------------------------------- | ------- | ----------------------------------------------------- | --------- | ----- | ---- |
-| High-power Port                                                              | VBUS    |                                                       | 4.75      | 5.25  | V    |
-| Low-power Port                                                               | VBUS    |                                                       | 4.4       | 5.25  | V    |
-| High-power Hub Port (out)                                                    | ICCPRT  |                                                       | 500       |       | mA   |
-| Low-power Hub Port (out)                                                     | ICCUPT  |                                                       | 100       |       | mA   |
-| High-power Function (in)                                                     | ICCHPF  |                                                       |           | 500   | mA   |
-| Low-power Function (in)                                                      | ICCLPF  |                                                       |           | 100   | mA   |
-| Unconfigured Function/Hub (in)                                               | ICCINIT |                                                       |           | 100   | mA   |
-| Suspended High-power Device                                                  | ICCSH   |                                                       |           | 2.5   | mA   |
-| Suspended Low-power Device                                                   | ICCSL   |                                                       |           | 500   | uA   |
-| High (driven)                                                                | VIH     |                                                       | 2         |       | V    |
-| High (floating)                                                              | VIHZ    |                                                       | 2.7       | 3.6   | V    |
-| Low                                                                          | VIL     |                                                       | 0.8       |       | V    |
-| Differential Input Sensitivity                                               | VDI     |                                                       | (D+)-(D-) |       | 0.2  |
-| Differential Common Mode Range                                               | VCM     | Includes VDI range;                                   | 0.8       | 2.5   | V    |
-| High-speed squelch detection threshold (differential signal amplitude)       | VHSSQ   | specification refers to differential signal amplitude | 100       | 150   | mV   |
-| High speed disconnect detection threshold (differential signal amplitude)    | VHSDSC  | specification refers to differential signal amplitude | 525       | 625   | mV   |
-| High-speed differential input signaling levels                               |         | Specified by eye pattern templates                    |           |       |      |
-| High-speed data signaling common mode voltage range (guideline for receiver) | VHSCM   |                                                       | -50       | 500   | mV   |
-| Low                                                                          | VOL     |                                                       | 0         | 0.3   | V    |
-| High (Driven)                                                                | VOH     |                                                       | 2.8       | 3.6   | V    |
-| SE1                                                                          | VOSE1   |                                                       | 0.8       |       | V    |
-| Output Signal Crossover Voltage                                              | VCRS    |                                                       | 1.3       | 2     | V    |
-| High-speed idle level                                                        | VHSOI   |                                                       | -10       | 10    | mV   |
-| High-speed data signaling high                                               | VHSOH   |                                                       | 360       | 440   | mV   |
-| High-speed data signaling low                                                | VHSOL   |                                                       | -10       | 10    | mV   |
-| Chirp J level (differential voltage)                                         | VCHIRPJ |                                                       | 700       | 1100  | mV   |
-| Chirp K level (differential voltage)                                         | VCHIRPK |                                                       | -900      | -500  | mV   |
-| Downstream Facing Port Bypass Capacitance (per hub)                          | CHPB    | VBUS to GND,                                          | 120       |       | uF   |
-| Upstream Facing Port Bypass Capacitance                                      | CRPB    | VBUS to GND                                           | 1         | 10    | uF   |
-| Downstream Facing Port                                                       | CIND    |                                                       | 150       |       | pF   |
-| Upstream Facing Port (w/o cable)                                             | CINUB   |                                                       | 100       |       | pF   |
-| Transceiver edge rate control capacitance                                    | CEDGE   |                                                       | 75        |       | pF   |
-| TDR spec for high-speed termination                                          |         |                                                       |           |       |      |
-| Bus Pull-up Resistor on Upstream Facing Port                                 | RPU     | 1.5 kΩ ±5%                                            | 1.425     | 1.575 | kΩ   |
-| Bus Pull-down Resistor on Downstream Facing Port                             | RPD     | 15 kΩ±5%                                              | 14.25     | 15.75 | kΩ   |
-| Input impedance exclusive of pullup/pulldown (for low-/full speed)           | ZINP    |                                                       | 300       |       | kΩ   |
-| Termination voltage for upstream facing port pullup (RPU)                    | VTERM   |                                                       | 3         | 3.6   | V    |
-| Termination voltage in high speed                                            | VHSTERM |                                                       | -10       | 10    | mV   |
-
-#### Electrical Characteristics for SD/eMMC
-
-<div align=center>Table 3-3-23 SD/eMMC electrical specifications</div>
-
-| Parameter                    | Test conditions | Min          | Max           | Units |
-| ---------------------------- | --------------- | ------------ | ------------- | ----- |
-| MMC0_* signals               | Relative to VSS | -0.3         | 3.63          | V     |
-| Input High Voltage(ViH)      | Relative to VSS | 1.68         | -             | V     |
-| Input Low Voltage(ViL)       | Relative to VSS | -            | 0.9           | V     |
-| VOH                          | Relative to VSS | 0.75*VDDIO33 | -             | V     |
-| VOL                          | Relative to VSS | -            | 0.125*VDDIO33 | V     |
-| Operating temprature rang TJ | -               | -40          | 125           | C     |
diff --git a/components/canaan/k230/artifacts/K230_nncase_Development_Guide.md b/components/canaan/k230/artifacts/K230_nncase_Development_Guide.md
deleted file mode 100644
index 8d4ab06..0000000
--- a/components/canaan/k230/artifacts/K230_nncase_Development_Guide.md
+++ /dev/null
@@ -1,2421 +0,0 @@
-# K230 nncase Development Guide
-
-![cover](../../../../zh/01_software/board/ai/images/canaan-cover.png)
-
-Copyright © 2023 Beijing Canaan Creative Information Technology Co., Ltd.
-
-<div style="page-break-after:always"></div>
-
-## Disclaimer
-
-The products, services, or features you purchase are subject to the commercial contracts and terms of Beijing Canaan Creative Information Technology Co., Ltd. ("the Company" hereinafter) and its affiliates. All or part of the products, services, or features described in this document may not be within the scope of your purchase or use. Unless otherwise agreed in the contract, the Company does not provide any express or implied statements or warranties regarding the correctness, reliability, completeness, merchantability, fitness for a particular purpose, and non-infringement of any representations, information, or content in this document. Unless otherwise agreed, this document is for reference only.
-
-Due to product version upgrades or other reasons, the content of this document may be updated or modified periodically without any notice.
-
-## Trademark Statement
-
-![logo](../../../../zh/01_software/board/ai/images/logo.png), "Canaan," and other Canaan trademarks are trademarks of Beijing Canaan Creative Information Technology Co., Ltd. and its affiliates. All other trademarks or registered trademarks mentioned in this document are owned by their respective owners.
-
-**Copyright © 2023 Beijing Canaan Creative Information Technology Co., Ltd. All rights reserved.**
-Without the written permission of the Company, no unit or individual may excerpt, copy part or all of the content of this document, or disseminate it in any form.
-
-<div style="page-break-after:always"></div>
-
-## Table of Contents
-
-[TOC]
-
-## Preface
-
-### Overview
-
-This document is the user guide for K230 nncase, providing users with instructions on how to install nncase, how to call compiler APIs to compile neural network models, and how to write AI inference programs using runtime APIs.
-
-### Target Audience
-
-This document (this guide) is mainly intended for the following personnel:
-
-- Technical support engineers
-- Software development engineers
-
-### Abbreviation Definitions
-
-| Abbreviation | Description                               |
-| ------------ | ----------------------------------------- |
-| PTQ          | Post-training quantization                |
-| MSE          | Mean-square error                         |
-
-### Revision History
-
-| Document Version | Modification Description                            | Modifier          | Date       |
-| ---------------- | --------------------------------------------------- | ----------------- | ---------- |
-| V1.0             | Initial version                                     | Zhang Yang/Huo Chenghai | 2023/4/7  |
-| V1.1             | Unified to Word format, improved ai2d               | Zhang Yang/Huo Chenghai | 2023/5/5  |
-| V1.2             | New architecture for nncase v2                      | Zhang Yang/Zheng Qihang/Huo Chenghai | 2023/6/2  |
-| V1.3             | nncase_k230_v2.1.0, ai2d/runtime_tensor supports physical address | Zhang Yang | 2023/7/3  |
-| V1.4             | Document description updated                        | Yang Haoqi        | 2024/5/15  |
-
-## Overview
-
-### What is nncase
-
-nncase is a neural network compiler designed for AI accelerators. Currently supported targets include CPU/K210/K510/K230, etc.
-
-Features provided by nncase:
-
-- Supports multi-input multi-output networks and multi-branch structures
-- Static memory allocation, no heap memory required
-- Operator fusion and optimization
-- Supports float and uint8/int8 quantized inference
-- Supports post-training quantization using floating-point models and quantization calibration sets
-- Flat model, supports zero-copy loading
-
-Supported neural network model formats by nncase:
-
-- TFLite
-- ONNX
-
-### nncase Architecture
-
-![nncase architecture](../../../../zh/01_software/board/ai/images/185762ac17039d6c4961faa2fba0d66e.png)
-
-The nncase software stack includes two parts: compiler and runtime.
-
-Compiler: Used to compile neural network models on a PC, ultimately generating kmodel files. It mainly includes modules such as importer, IR, Evaluator, Quantize, Transform optimization, Tiling, Partition, Schedule, and Codegen.
-
-- Importer: Imports models from other neural network frameworks into nncase
-- IR: Intermediate Representation, divided into Neutral IR (device-independent) imported by the importer and Target IR (device-specific) generated by lowering the Neutral IR
-- Evaluator: Provides interpretation execution capabilities for IR, often used in scenarios such as Constant Folding/PTQ Calibration
-- Transform: Used for IR transformation and graph traversal optimization
-- Quantize: Post-training quantization, adds quantization tags to the tensors to be quantized, collects tensor data ranges by calling the Evaluator for interpretation execution based on the input calibration set, inserts quantization/dequantization nodes, and finally optimizes to eliminate unnecessary quantization/dequantization nodes
-- Tiling: Due to the limited memory capacity of NPU, large computations need to be split. Additionally, choosing Tiling parameters when there is a large amount of data reuse in computations can impact latency and bandwidth
-- Partition: Splits the graph according to ModuleType, each subgraph corresponds to a RuntimeModule, and different types of RuntimeModules correspond to different Devices (CPU/K230)
-- Schedule: Generates the computation order and allocates buffers based on the data dependency relationships in the optimized graph
-- Codegen: Calls the codegen corresponding to each subgraph's ModuleType to generate RuntimeModules
-
-Runtime: Integrated into the user's App, providing functions such as loading kmodel, setting input data, executing KPU, and retrieving output data.
-
-### Development Environment
-
-#### Operating System
-
-Supported operating systems include Ubuntu 18.04/Ubuntu 20.04
-
-#### Software Environment
-
-| No. | Software         | Version              |
-| --- | ---------------- | -------------------- |
-| 1   | python           | 3.6/3.7/3.8/3.9/3.10 |
-| 2   | pip              | \>=20.3              |
-| 3   | numpy            | 1.19.5               |
-| 4   | onnx             | 1.9.0                |
-| 5   | onnx-simplifier  | 0.3.6                |
-| 6   | Onnxoptimizer    | 0.2.6                |
-| 7   | Onnxruntime      | 1.8.0                |
-| 8   | dotnet-runtime   | 7.0                  |
-
-#### Hardware Environment
-
-K230 evb
-
-## Model Compilation APIs (Python)
-
-nncase provides Python APIs for compiling neural network models on a PC
-
-### Supported Operators
-
-#### TFLite Operators
-
-| Operator                | Is Supported |
-| ----------------------- | ------------ |
-| ABS                     | Yes          |
-| ADD                     | Yes          |
-| ARG_MAX                 | Yes          |
-| ARG_MIN                 | Yes          |
-| AVERAGE_POOL_2D         | Yes          |
-| BATCH_MATMUL            | Yes          |
-| CAST                    | Yes          |
-| CEIL                    | Yes          |
-| CONCATENATION           | Yes          |
-| CONV_2D                 | Yes          |
-| COS                     | Yes          |
-| CUSTOM                  | Yes          |
-| DEPTHWISE_CONV_2D       | Yes          |
-| DIV                     | Yes          |
-| EQUAL                   | Yes          |
-| EXP                     | Yes          |
-| EXPAND_DIMS             | Yes          |
-| FLOOR                   | Yes          |
-| FLOOR_DIV               | Yes          |
-| FLOOR_MOD               | Yes          |
-| FULLY_CONNECTED         | Yes          |
-| GREATER                 | Yes          |
-| GREATER_EQUAL           | Yes          |
-| L2_NORMALIZATION        | Yes          |
-| LEAKY_RELU              | Yes          |
-| LESS                    | Yes          |
-| LESS_EQUAL              | Yes          |
-| LOG                     | Yes          |
-| LOGISTIC                | Yes          |
-| MAX_POOL_2D             | Yes          |
-| MAXIMUM                 | Yes          |
-| MEAN                    | Yes          |
-| MINIMUM                 | Yes          |
-| MUL                     | Yes          |
-| NEG                     | Yes          |
-| NOT_EQUAL               | Yes          |
-| PAD                     | Yes          |
-| PADV2                   | Yes          |
-| MIRROR_PAD              | Yes          |
-| PACK                    | Yes          |
-| POW                     | Yes          |
-| REDUCE_MAX              | Yes          |
-| REDUCE_MIN              | Yes          |
-| REDUCE_PROD             | Yes          |
-| RELU                    | Yes          |
-| PRELU                   | Yes          |
-| RELU6                   | Yes          |
-| RESHAPE                 | Yes          |
-| RESIZE_BILINEAR         | Yes          |
-| RESIZE_NEAREST_NEIGHBOR | Yes          |
-| ROUND                   | Yes          |
-| RSQRT                   | Yes          |
-| SHAPE                   | Yes          |
-| SIN                     | Yes          |
-| SLICE                   | Yes          |
-| SOFTMAX                 | Yes          |
-| SPACE_TO_BATCH_ND       | Yes          |
-| SQUEEZE                 | Yes          |
-| BATCH_TO_SPACE_ND       | Yes          |
-| STRIDED_SLICE           | Yes          |
-| SQRT                    | Yes          |
-| SQUARE                  | Yes          |
-| SUB                     | Yes          |
-| SUM                     | Yes          |
-| TANH                    | Yes          |
-| TILE                    | Yes          |
-| TRANSPOSE               | Yes          |
-| TRANSPOSE_CONV          | Yes          |
-| QUANTIZE                | Yes          |
-| FAKE_QUANT              | Yes          |
-| DEQUANTIZE              | Yes          |
-| GATHER                  | Yes          |
-| GATHER_ND               | Yes          |
-| ONE_HOT                 | Yes          |
-| SQUARED_DIFFERENCE      | Yes          |
-| LOG_SOFTMAX             | Yes          |
-| SPLIT                   | Yes          |
-| HARD_SWISH              | Yes          |
-
-#### ONNX Operators
-
-| Operator              | Is Supported |
-| --------------------- | ------------ |
-| Abs                   | Yes          |
-| Acos                  | Yes          |
-| Acosh                 | Yes          |
-| And                   | Yes          |
-| ArgMax                | Yes          |
-| ArgMin                | Yes          |
-| Asin                  | Yes          |
-| Asinh                 | Yes          |
-| Add                   | Yes          |
-| AveragePool           | Yes          |
-| BatchNormalization    | Yes          |
-| Cast                  | Yes          |
-| Ceil                  | Yes          |
-| Celu                  | Yes          |
-| Clip                  | Yes          |
-| Compress              | Yes          |
-| Concat                | Yes          |
-| Constant              | Yes          |
-| ConstantOfShape       | Yes          |
-| Conv                  | Yes          |
-| ConvTranspose         | Yes          |
-| Cos                   | Yes          |
-| Cosh                  | Yes          |
-| CumSum                | Yes          |
-| DepthToSpace          | Yes          |
-| DequantizeLinear      | Yes          |
-| Div                   | Yes          |
-| Dropout               | Yes          |
-| Elu                   | Yes          |
-| Exp                   | Yes          |
-| Expand                | Yes          |
-| Equal                 | Yes          |
-| Erf                   | Yes          |
-| Flatten               | Yes          |
-| Floor                 | Yes          |
-| Gather                | Yes          |
-| GatherElements        | Yes          |
-| GatherND              | Yes          |
-| Gemm                  | Yes          |
-| GlobalAveragePool     | Yes          |
-| GlobalMaxPool         | Yes          |
-| Greater               | Yes          |
-| GreaterOrEqual        | Yes          |
-| GRU                   | Yes          |
-| Hardmax               | Yes          |
-| HardSigmoid           | Yes          |
-| HardSwish             | Yes          |
-| Identity              | Yes          |
-| InstanceNormalization | Yes          |
-| LayerNormalization    | Yes          |
-| LpNormalization       | Yes          |
-| LeakyRelu             | Yes          |
-| Less                  | Yes          |
-| LessOrEqual           | Yes          |
-| Log                   | Yes          |
-| LogSoftmax            | Yes          |
-| LRN                   | Yes          |
-| LSTM                  | Yes          |
-| MatMul                | Yes          |
-| MaxPool               | Yes          |
-| Max                   | Yes          |
-| Min                   | Yes          |
-| Mul                   | Yes          |
-| Neg                   | Yes          |
-| Not                   | Yes          |
-| OneHot                | Yes          |
-| Pad                   | Yes          |
-| Pow                   | Yes          |
-| PRelu                 | Yes          |
-| QuantizeLinear        | Yes          |
-| RandomNormal          | Yes          |
-| RandomNormalLike      | Yes          |
-| RandomUniform         | Yes          |
-| RandomUniformLike     | Yes          |
-| ReduceL1              | Yes          |
-| ReduceL2              | Yes          |
-| ReduceLogSum          | Yes          |
-| ReduceLogSumExp       | Yes          |
-| ReduceMax             | Yes          |
-| ReduceMean            | Yes          |
-| ReduceMin             | Yes          |
-| ReduceProd            | Yes          |
-| ReduceSum             | Yes          |
-| ReduceSumSquare       | Yes          |
-| Relu                  | Yes          |
-| Reshape               | Yes          |
-| Resize                | Yes          |
-| ReverseSequence       | Yes          |
-| RoiAlign              | Yes          |
-| Round                 | Yes          |
-| Rsqrt                 | Yes          |
-| Selu                  | Yes          |
-| Shape                 | Yes          |
-| Sign                  | Yes          |
-| Sin                   | Yes          |
-| Sinh                  | Yes          |
-| Sigmoid               | Yes          |
-| Size                  | Yes          |
-| Slice                 | Yes          |
-| Softmax               | Yes          |
-| Softplus              | Yes          |
-| Softsign              | Yes          |
-| SpaceToDepth          | Yes          |
-| Split                 | Yes          |
-| Sqrt                  | Yes          |
-| Squeeze               | Yes          |
-| Sub                   | Yes          |
-| Sum                   | Yes          |
-| Tanh                  | Yes          |
-| Tile                  | Yes          |
-| TopK                  | Yes          |
-| Transpose             | Yes          |
-| Trilu                 | Yes          |
-| ThresholdedRelu       | Yes          |
-| Upsample              | Yes          |
-| Unsqueeze             | Yes          |
-| Where                 | Yes          |
-
-### APIs
-
-Currently, the model compilation APIs support deep learning models in TFLite/ONNX formats.
-
-#### CompileOptions
-
-**Description**:
-
-The `CompileOptions` class is used to configure nncase compilation options. The descriptions of each attribute are as follows:
-
-| Attribute Name              |        Type         | Required | Description                                                                                                           |
-| --------------------------- | :-----------------: | :------: | --------------------------------------------------------------------------------------------------------------------- |
-| target                      |       string        |    Yes   | Specifies the compilation target, such as 'cpu' or 'k230'                                                             |
-| dump_ir                     |        bool         |    No    | Specifies whether to dump IR, defaults to False                                                                       |
-| dump_asm                    |        bool         |    No    | Specifies whether to dump asm assembly files, defaults to False                                                       |
-| dump_dir                    |       string        |    No    | Specifies the directory to dump files when dump_ir or other dump options are enabled, defaults to ""                  |
-| input_file                  |       string        |    No    | Specifies the parameter file path when the ONNX model exceeds 2GB, defaults to ""                                     |
-|                             |                     |          |                                                                                                                       |
-| preprocess                  |        bool         |    No    | Specifies whether to enable preprocessing, defaults to False. The following parameters are effective only when `preprocess=True` |
-| input_type                  |       string        |    No    | Specifies the input data type when preprocessing is enabled, defaults to "float". When `preprocess` is `True`, must be "uint8" or "float32" |
-| input_shape                 |      list[int]      |    No    | Specifies the shape of the input data when preprocessing is enabled, defaults to []. When `preprocess` is `True`, must be specified |
-| input_range                 |     list[float]     |    No    | Specifies the floating-point range of the input data after dequantization when preprocessing is enabled, defaults to []. When `preprocess` is `True` and `input_type` is `uint8`, must be specified |
-| input_layout                |       string        |    No    | Specifies the layout of the input data, defaults to ""                                                                |
-| swapRB                      |        bool         |    No    | Specifies whether to reverse the data in the `channel` dimension, defaults to False                                   |
-| mean                        |     list[float]     |    No    | Mean value for preprocessing normalization, defaults to [0,0,0]                                                       |
-| std                         |     list[float]     |    No    | Standard deviation for preprocessing normalization, defaults to [1,1,1]                                               |
-| letterbox_value             |       float         |    No    | Specifies the fill value for letterbox preprocessing, defaults to 0                                                   |
-| output_layout               |       string        |    No    | Specifies the layout of the output data, defaults to ""                                                               |
-|                             |                     |          |                                                                                                                       |
-| shape_bucket_enable         |        bool         |    Yes   | Specifies whether to enable ShapeBucket functionality, defaults to False. Effective when `dump_ir=True`               |
-| shape_bucket_range_info     | Dict[str, [int, int]] |    Yes   | Specifies the range of variables in each dimension of the input shape, minimum value must be greater than or equal to 1 |
-| shape_bucket_segments_count |         int         |    Yes   | Specifies the number of segments to divide the input variable's range                                                 |
-| shape_bucket_fix_var_map    |   Dict[str, int]    |    No    | Specifies fixed values for variables in the shape dimension information                                               |
-
-##### Preprocessing Workflow
-
-Currently, custom preprocessing order is not supported. You can configure the required preprocessing parameters based on the following workflow diagram.
-
-<div class="mermaid">
-graph TD;
-    NewInput("NewInput<br>(shape = input_shape<br>dtype = input_type)") -->a(input_layout != ' ')-.Y.->Transpose1["transpose"] -.->b("SwapRB == True")-.Y.->SwapRB["SwapRB"]-.->c("input_type != float32")-.Y.->Dequantize["Dequantize"]-.->d("input_HW != model_HW")-.Y.->LetterBox["LetterBox"] -.->e("std not empty<br>mean not empty")-.Y.->Normalization["Normalization"]-.->OldInput-->Model_body-->OldOutput-->f("output_layout != ' '")-.Y.->Transpose2["Transpose"]-.-> NewOutput;
-    a--N-->b--N-->c--N-->d--N-->e--N-->OldInput; f--N-->NewOutput;
-    subgraph origin_model
-        OldInput; Model_body ; OldOutput;
-    end
-</div>
-
-Parameter explanations:
-
-1. `input_range` specifies the floating-point range after dequantization when the input data type is fixed-point.
-
-   a. If the input data type is uint8 and the range is [0,255], setting `input_range` to [0,255] means dequantization only converts the data type from uint8 to float32. The `mean` and `std` parameters should still be specified based on data in the range [0,255].
-
-   b. If the input data type is uint8 and the range is [0,255], setting `input_range` to [0,1] means dequantization will convert fixed-point data to floating-point data in the range [0,1]. The `mean` and `std` parameters should be specified based on data in the range [0,1].
-
-   <div class="mermaid">
-    graph TD;
-        NewInput_uint8("NewInput_uint8 <br>[input_type:uint8]") --input_range:0,255 -->dequantize_0["Dequantize"]--float range:0,255--> OldInput_float32
-        NewInput_uint81("NewInput_uint8 <br>[input_type:uint8]") --input_range:0,1 -->dequantize_1["Dequantize"]--float range:0,1--> OldInput_float32
-   </div>
-
-1. `input_shape` specifies the shape of the input data, and `input_layout` specifies its layout. It currently supports both string (e.g., `"NHWC"`, `"NCHW"`) and index formats. Non-4D data processing is also supported. When configured as a string, `input_layout` specifies the layout of the input data. When configured as an index, `input_layout` specifies the permutation parameter for a `Transpose` operation.
-
-<div class="mermaid">
-graph TD;
-    subgraph B
-        NewInput1("NewInput: 1,4,10") --"input_layout:"0,2,1""-->Transpose2("Transpose perm: 0,2,1") --> OldInput2("OldInput: 1,10,4");
-    end
-    subgraph A
-        NewInput --"input_layout:"NHWC""--> Transpose0("Transpose: NHWC2NCHW") --> OldInput;
-        NewInput("NewInput: 1,224,224,3 (NHWC)") --"input_layout:"0,3,1,2""--> Transpose1("Transpose perm: 0,3,1,2") --> OldInput("OldInput: 1,3,224,224 (NCHW)");
-    end
-</div>
-
-Similarly, `output_layout` can be configured as shown below.
-
-<div class="mermaid">
-graph TD;
-subgraph B
-    OldOutput1("OldOutput: 1,10,4,5,2") --"output_layout: "0,2,3,1,4""--> Transpose5("Transpose perm: 0,2,3,1,4") --> NewOutput1("NewOutput: 1,4,5,10,2");
-    end
-subgraph A
-    OldOutput --"output_layout: "NHWC""--> Transpose3("Transpose: NCHW2NHWC") --> NewOutput("NewOutput<br>NHWC");
-    OldOutput("OldOutput: (NCHW)") --"output_layout: "0,2,3,1""--> Transpose4("Transpose perm: 0,2,3,1") --> NewOutput("NewOutput<br>NHWC");
-    end
-</div>
-
-##### Dynamic Shape Parameters
-
-ShapeBucket is a solution for dynamic shapes that optimizes based on the range of input lengths and the specified number of segments. This feature is disabled by default and needs to be enabled through the corresponding option. Apart from specifying the relevant field information, the rest of the compilation process is the same as compiling a static model.
-
-- ONNX
-
-In the shape information of a model, some dimensions may be variable names. For example, consider an ONNX model with the following inputs:
-
-> tokens: int64[batch_size, tgt_seq_len]  
-> step: float32[seq_len, batch_size]
-
-The shape information contains three variables: `seq_len`, `tgt_seq_len`, and `batch_size`. Although `batch_size` is a variable, it is fixed to 3 in actual use. Therefore, add `batch_size = 3` to **fix_var_map** to fix this dimension to 3 during runtime. The variables `seq_len` and `tgt_seq_len` are dynamic and need to be configured with their actual ranges in **range_info**. **segments_count** specifies the number of segments to divide the range into, which will proportionally increase the compilation time.
-
-Here is an example of the corresponding compilation parameters:
-
-```python
-compile_options = nncase.CompileOptions()
-compile_options.shape_bucket_enable = True
-compile_options.shape_bucket_range_info = {"seq_len": [1, 100], "tgt_seq_len": [1, 100]}
-compile_options.shape_bucket_segments_count = 2
-compile_options.shape_bucket_fix_var_map = {"batch_size": 3}
-```
-
-- TFLite
-
-Unlike ONNX models, TFLite models do not currently label dimension names in the shape. Currently, only one dimension in the input can be dynamic, and it is uniformly named as -1. The configuration is as follows:
-
-```python
-compile_options = nncase.CompileOptions()
-compile_options.shape_bucket_enable = True
-compile_options.shape_bucket_range_info = {"-1":[1, 100]}
-compile_options.shape_bucket_segments_count = 2
-compile_options.shape_bucket_fix_var_map = {"batch_size" : 3}
-```
-
-After configuring these options, the entire compilation process is the same as for a static shape model.
-
-##### Parameter Configuration Example
-
-Instantiate `CompileOptions` and configure the attribute values.
-
-```python
-compile_options = nncase.CompileOptions()
-
-compile_options.target = "cpu"  # "k230"
-compile_options.dump_ir = True  # if False, will not dump the compile-time result.
-compile_options.dump_asm = True
-compile_options.dump_dir = "dump_path"
-compile_options.input_file = ""
-
-# preprocess args
-compile_options.preprocess = False
-if compile_options.preprocess:
-    compile_options.input_type = "uint8"  # "uint8" "float32"
-    compile_options.input_shape = [1,224,320,3]
-    compile_options.input_range = [0,1]
-    compile_options.input_layout = "NHWC"  # "NHWC" "NCHW"
-    compile_options.swapRB = False
-    compile_options.mean = [0,0,0]
-    compile_options.std = [1,1,1]
-    compile_options.letterbox_value = 0
-    compile_options.output_layout = "NHWC"  # "NHWC" "NCHW"
-
-# Dynamic shape args
-compile_options.shape_bucket_enable = False
-if compile_options.shape_bucket_enable:
-    compile_options.shape_bucket_range_info = {"seq_len": [1, 100], "tgt_seq_len": [1, 100]}
-    compile_options.shape_bucket_segments_count = 2
-    compile_options.shape_bucket_fix_var_map = {"batch_size": 3}
-```
-
-#### ImportOptions
-
-**Description**:
-
-The `ImportOptions` class is used to configure nncase import options.
-
-**Definition**:
-
-```python
-class ImportOptions:
-    def __init__(self) -> None:
-        pass
-```
-
-**Example**:
-
-Instantiate `ImportOptions` and configure attribute values.
-
-```python
-#import_options
-import_options = nncase.ImportOptions()
-```
-
-#### PTQTensorOptions
-
-**Description**:
-
-The `PTQTensorOptions` class is used to configure nncase PTQ options.
-
-| Name                            | Type   | Required | Description |
-| ------------------------------- | ------ | -------- | ----------- |
-| samples_count                   | int    |    No    | Specifies the number of samples used for the quantization calibration set |
-| calibrate_method                | string |    No    | Specifies the quantization method, options are 'NoClip' and 'Kld', default is 'Kld' |
-| finetune_weights_method         | string |    No    | Specifies whether to fine-tune weights, options are 'NoFineTuneWeights' and 'UseSquant', default is 'NoFineTuneWeights' |
-| quant_type                      | string |    No    | Specifies the data quantization type, options are 'uint8', 'int8', 'int16' |
-| w_quant_type                    | string |    No    | Specifies the weight quantization type, options are 'uint8', 'int8', 'int16' |
-|                                 |        |    No    | The above two types cannot both be 'int16' |
-| quant_scheme                    | string |    No    | Path to the quantization parameter configuration file |
-| quant_scheme_strict_mode        | bool   |    No    | Whether to strictly follow quant_scheme for quantization |
-| export_quant_scheme             | bool   |    No    | Whether to export the quantization parameter configuration file |
-| export_weight_range_by_channel  | bool   |    No    | Whether to export weights quantization parameters in `bychannel` form, it is recommended to set this parameter to `True` |
-
-For detailed usage of mixed quantization, see [MixQuant Guide](https://github.com/kendryte/nncase/blob/release/2.0/docs/MixQuant.md)
-
-**Example**:
-
-```python
-# ptq_options
-ptq_options = nncase.PTQTensorOptions()
-ptq_options.samples_count = 6
-ptq_options.finetune_weights_method = "NoFineTuneWeights"
-ptq_options.quant_type = "uint8"
-ptq_options.w_quant_type = "uint8"
-ptq_options.set_tensor_data(generate_data(input_shape, ptq_options.samples_count, args.dataset))
-
-ptq_options.quant_scheme = ""
-ptq_options.quant_scheme_strict_mode = False
-ptq_options.export_quant_scheme = True
-ptq_options.export_weight_range_by_channel = True
-
-compiler.use_ptq(ptq_options)
-```
-
-#### set_tensor_data
-
-**Description**:
-
-Sets tensor data.
-
-**Definition**:
-
-```python
-def set_tensor_data(self, data: List[List[np.ndarray]]) -> None:
-    reshape_data = list(map(list, zip(*data)))
-    self.cali_data = [RuntimeTensor.from_numpy(
-        d) for d in itertools.chain.from_iterable(reshape_data)]
-```
-
-**[Parameters]**
-
-| Name | Type                  | Description      |
-| ---- | --------------------- | ---------------- |
-| data | List[List[np.ndarray]] | Calibration data |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-```shell
-# ptq_options
-ptq_options = nncase.PTQTensorOptions()
-ptq_options.samples_count = 6
-ptq_options.set_tensor_data(generate_data(input_shape, ptq_options.samples_count, args.dataset))
-compiler.use_ptq(ptq_options)
-```
-
-#### Compiler
-
-**Description**:
-
-The `Compiler` class is used to compile neural network models.
-
-**Definition**:
-
-```python
-class Compiler:
-    _target: _nncase.Target
-    _session: _nncase.CompileSession
-    _compiler: _nncase.Compiler
-    _compile_options: _nncase.CompileOptions
-    _quantize_options: _nncase.QuantizeOptions
-    _module: IRModule
-```
-
-#### import_tflite
-
-**Description**:
-
-Imports a TFLite model.
-
-**Definition**:
-
-```python
-def import_tflite(self, model_content: bytes, options: ImportOptions) -> None:
-    self._compile_options.input_format = "tflite"
-    self._import_module(model_content)
-```
-
-**[Parameters]**
-
-| Name           | Type          | Description                |
-| -------------- | ------------- | -------------------------- |
-| model_content  | byte[]        | The content of the model   |
-| import_options | ImportOptions | Import options             |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-```python
-model_content = read_model_file(model)
-compiler.import_tflite(model_content, import_options)
-```
-
-#### import_onnx
-
-**Description**:
-
-Imports an ONNX model.
-
-**Definition**:
-
-```python
-def import_onnx(self, model_content: bytes, options: ImportOptions) -> None:
-    self._compile_options.input_format = "onnx"
-    self._import_module(model_content)
-```
-
-**[Parameters]**
-
-| Name           | Type          | Description                |
-| -------------- | ------------- | -------------------------- |
-| model_content  | byte[]        | The content of the model   |
-| import_options | ImportOptions | Import options             |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-```python
-model_content = read_model_file(model)
-compiler.import_onnx(model_content, import_options)
-```
-
-#### use_ptq
-
-**Description**:
-
-Sets PTQ configuration options.
-
-- Quantization is mandatory for K230 by default.
-
-**Definition**:
-
-`use_ptq(ptq_options)`
-
-**[Parameters]**
-
-| Name        | Type             | Description          |
-| ----------- | ---------------- | -------------------- |
-| ptq_options | PTQTensorOptions | PTQ configuration options |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-`compiler.use_ptq(ptq_options)`
-
-#### compile
-
-**Description**:
-
-Compiles the neural network model.
-
-**Definition**:
-
-`compile()`
-
-**[Parameters]**
-
-None
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-`compiler.compile()`
-
-#### gencode_tobytes
-
-**Description**:
-
-Generates kmodel byte stream.
-
-**Definition**:
-
-`gencode_tobytes()`
-
-**[Parameters]**
-
-None
-
-**[Return Value]**
-
-`bytes[]`
-
-**Example**:
-
-```python
-kmodel = compiler.gencode_tobytes()
-with open(os.path.join(infer_dir, 'test.kmodel'), 'wb') as f:
-    f.write(kmodel)
-```
-
-### Examples
-
-The following examples use models and Python compilation scripts.
-
-- The original model files are located in `/path/to/k230_sdk/src/big/nncase/examples/models`
-- The Python compilation scripts are located in `/path/to/k230_sdk/src/big/nncase/examples/scripts`
-
-#### Compiling a TFLite Model
-
-The `mbv2_tflite.py` script is as follows:
-
-```python
-import os
-import argparse
-import numpy as np
-from PIL import Image
-import nncase
-
-def read_model_file(model_file):
-    with open(model_file, 'rb') as f:
-        model_content = f.read()
-    return model_content
-
-def generate_data(shape, batch, calib_dir):
-    img_paths = [os.path.join(calib_dir, p) for p in os.listdir(calib_dir)]
-    data = []
-    for i in range(batch):
-        assert i < len(img_paths), "calibration images not enough."
-        img_data = Image.open(img_paths[i]).convert('RGB')
-        img_data = img_data.resize((shape[3], shape[2]), Image.BILINEAR)
-        img_data = np.asarray(img_data, dtype=np.uint8)
-        img_data = np.transpose(img_data, (2, 0, 1))
-        data.append([img_data[np.newaxis, ...]])
-    return data
-
-def main():
-    parser = argparse.ArgumentParser(prog="nncase")
-    parser.add_argument("--target", type=str, help='target to run')
-    parser.add_argument("--model", type=str, help='model file')
-    parser.add_argument("--dataset", type=str, help='calibration_dataset')
-    args = parser.parse_args()
-
-    input_shape = [1, 3, 224, 224]
-    dump_dir = 'tmp/mbv2_tflite'
-
-    # compile_options
-    compile_options = nncase.CompileOptions()
-    compile_options.target = args.target
-    compile_options.preprocess = True
-    compile_options.swapRB = False
-    compile_options.input_shape = input_shape
-    compile_options.input_type = 'uint8'
-    compile_options.input_range = [0, 255]
-    compile_options.mean = [127.5, 127.5, 127.5]
-    compile_options.std = [127.5, 127.5, 127.5]
-    compile_options.input_layout = 'NCHW'
-    compile_options.dump_ir = True
-    compile_options.dump_asm = True
-    compile_options.dump_dir = dump_dir
-
-    # compiler
-    compiler = nncase.Compiler(compile_options)
-
-    # import
-    model_content = read_model_file(args.model)
-    import_options = nncase.ImportOptions()
-    compiler.import_tflite(model_content, import_options)
-
-    # ptq_options
-    ptq_options = nncase.PTQTensorOptions()
-    ptq_options.samples_count = 6
-    ptq_options.set_tensor_data(generate_data(input_shape, ptq_options.samples_count, args.dataset))
-    compiler.use_ptq(ptq_options)
-
-    # compile
-    compiler.compile()
-
-    # kmodel
-    kmodel = compiler.gencode_tobytes()
-    with open(os.path.join(dump_dir, 'test.kmodel'), 'wb') as f:
-        f.write(kmodel)
-
-if __name__ == '__main__':
-    main()
-```
-
-Run the following command to compile the mobilenetv2 TFLite model with the target set to k230:
-
-```sh
-root@c285a41a7243:/mnt/# cd src/big/nncase/examples
-root@c285a41a7243:/mnt/src/big/nncase/examples# python3 ./scripts/mbv2_tflite.py --target k230 --model models/mbv2.tflite --dataset calibration_dataset
-```
-
-#### Compiling an ONNX Model
-
-For ONNX models, it is recommended to use the [ONNX Simplifier](https://github.com/daquexian/onnx-simplifier) to simplify the model before using nncase to compile it.
-
-The `yolov5s_onnx.py` script is as follows:
-
-```python
-import os
-import argparse
-import numpy as np
-from PIL import Image
-import onnxsim
-import onnx
-import nncase
-
-def parse_model_input_output(model_file):
-    onnx_model = onnx.load(model_file)
-    input_all = [node.name for node in onnx_model.graph.input]
-    input_initializer = [node.name for node in onnx_model.graph.initializer]
-    input_names = list(set(input_all) - set(input_initializer))
-    input_tensors = [
-        node for node in onnx_model.graph.input if node.name in input_names]
-
-    # input
-    inputs = []
-    for _, e in enumerate(input_tensors):
-        onnx_type = e.type.tensor_type
-        input_dict = {}
-        input_dict['name'] = e.name
-        input_dict['dtype'] = onnx.mapping.TENSOR_TYPE_TO_NP_TYPE[onnx_type.elem_type]
-        input_dict['shape'] = [(i.dim_value if i.dim_value != 0 else d) for i, d in zip(
-            onnx_type.shape.dim, [1, 3, 224, 224])]
-        inputs.append(input_dict)
-
-    return onnx_model, inputs
-
-
-def onnx_simplify(model_file, dump_dir):
-    onnx_model, inputs = parse_model_input_output(model_file)
-    onnx_model = onnx.shape_inference.infer_shapes(onnx_model)
-    input_shapes = {}
-    for input in inputs:
-        input_shapes[input['name']] = input['shape']
-
-    onnx_model, check = onnxsim.simplify(onnx_model, input_shapes=input_shapes)
-    assert check, "Simplified ONNX model could not be validated"
-
-    model_file = os.path.join(dump_dir, 'simplified.onnx')
-    onnx.save_model(onnx_model, model_file)
-    return model_file
-
-
-def read_model_file(model_file):
-    with open(model_file, 'rb') as f:
-        model_content = f.read()
-    return model_content
-
-def generate_data_ramdom(shape, batch):
-    data = []
-    for i in range(batch):
-        data.append([np.random.randint(0, 256, shape).astype(np.uint8)])
-    return data
-
-
-def generate_data(shape, batch, calib_dir):
-    img_paths = [os.path.join(calib_dir, p) for p in os.listdir(calib_dir)]
-    data = []
-    for i in range(batch):
-        assert i < len(img_paths), "calibration images not enough."
-        img_data = Image.open(img_paths[i]).convert('RGB')
-        img_data = img_data.resize((shape[3], shape[2]), Image.BILINEAR)
-        img_data = np.asarray(img_data, dtype=np.uint8)
-        img_data = np.transpose(img_data, (2, 0, 1))
-        data.append([img_data[np.newaxis, ...]])
-    return data
-
-def main():
-    parser = argparse.ArgumentParser(prog="nncase")
-    parser.add_argument("--target", type=str, help='target to run')
-    parser.add_argument("--model", type=str, help='model file')
-    parser.add_argument("--dataset", type=str, help='calibration_dataset')
-
-    args = parser.parse_args()
-
-    input_shape = [1, 3, 320, 320]
-
-    dump_dir = 'tmp/yolov5s_onnx'
-    if not os.path.exists(dump_dir):
-        os.makedirs(dump_dir)
-
-    # onnx simplify
-    model_file = onnx_simplify(args.model, dump_dir)
-
-    # compile_options
-    compile_options = nncase.CompileOptions()
-    compile_options.target = args.target
-    compile_options.preprocess = True
-    compile_options.swapRB = False
-    compile_options.input_shape = input_shape
-    compile_options.input_type = 'uint8'
-    compile_options.input_range = [0, 255]
-    compile_options.mean = [0, 0, 0]
-    compile_options.std = [255, 255, 255]
-    compile_options.input_layout = 'NCHW'
-    compile_options.output_layout = 'NCHW'
-    compile_options.dump_ir = True
-    compile_options.dump_asm = True
-    compile_options.dump_dir = dump_dir
-
-    # compiler
-    compiler = nncase.Compiler(compile_options)
-
-    # import
-    model_content = read_model_file(model_file)
-    import_options = nncase.ImportOptions()
-    compiler.import_onnx(model_content, import_options)
-
-    # ptq_options
-    ptq_options = nncase.PTQTensorOptions()
-    ptq_options.samples_count = 6
-    ptq_options.set_tensor_data(generate_data(input_shape, ptq_options.samples_count, args.dataset))
-    compiler.use_ptq(ptq_options)
-
-    # compile
-    compiler.compile()
-
-    # kmodel
-    kmodel = compiler.gencode_tobytes()
-    with open(os.path.join(dump_dir, 'test.kmodel'), 'wb') as f:
-        f.write(kmodel)
-
-if __name__ == '__main__':
-    main()
-```
-
-Run the following command to compile the ONNX model with the target set to k230:
-
-```sh
-root@c285a41a7243:/mnt/# cd src/big/nncase/examples
-root@c285a41a7243:/mnt/src/big/nncase/examples# python3 ./scripts/yolov5s_onnx.py --target k230 --model models/yolov5s.onnx --dataset calibration_dataset
-```
-
-## Simulator APIs (Python)
-
-In addition to model compilation APIs, nncase also provides inference APIs that allow you to run compiled kmodel on a PC to verify if the nncase inference results are consistent with the runtime results of the corresponding deep learning framework.
-
-### APIs
-
-#### MemoryRange
-
-**Description**:
-
-The `MemoryRange` class is used to represent a memory range.
-
-**Definition**:
-
-```python
-py::class_<memory_range>(m, "MemoryRange")
-    .def_readwrite("location", &memory_range::memory_location)
-    .def_property(
-        "dtype", [](const memory_range &range) { return to_dtype(range.datatype); },
-        [](memory_range &range, py::object dtype) { range.datatype = from_dtype(py::dtype::from_args(dtype)); })
-    .def_readwrite("start", &memory_range::start)
-    .def_readwrite("size", &memory_range::size);
-```
-
-**[Attributes]**
-
-| Name     | Type           | Description                                                                |
-| -------- | -------------- | -------------------------------------------------------------------------- |
-| location | int            | Memory location: 0 for input, 1 for output, 2 for rdata, 3 for data, 4 for shared_data |
-| dtype    | Python data type | Data type                                                                 |
-| start    | int            | Memory start address                                                       |
-| size     | int            | Memory size                                                                 |
-
-**Example**:
-
-`mr = nncase.MemoryRange()`
-
-### RuntimeTensor
-
-**Description**:
-
-The `RuntimeTensor` class is used to represent a runtime tensor.
-
-**Definition**:
-
-```python
-py::class_<runtime_tensor>(m, "RuntimeTensor")
-    .def_static("from_numpy", [](py::array arr) {
-        auto src_buffer = arr.request();
-        auto datatype = from_dtype(arr.dtype());
-        auto tensor = host_runtime_tensor::create(
-            datatype,
-            to_rt_shape(src_buffer.shape),
-            to_rt_strides(src_buffer.itemsize, src_buffer.strides),
-            gsl::make_span(reinterpret_cast<gsl::byte *>(src_buffer.ptr), src_buffer.size * src_buffer.itemsize),
-            [=](gsl::byte *) { arr.dec_ref(); })
-                          .unwrap_or_throw();
-        arr.inc_ref();
-        return tensor;
-    })
-    .def("copy_to", [](runtime_tensor &from, runtime_tensor &to) {
-        from.copy_to(to).unwrap_or_throw();
-    })
-    .def("to_numpy", [](runtime_tensor &tensor) {
-        auto host = tensor.as_host().unwrap_or_throw();
-        auto src_map = std::move(hrt::map(host, hrt::map_read).unwrap_or_throw());
-        auto src_buffer = src_map.buffer();
-        return py::array(
-            to_dtype(tensor.datatype()),
-            tensor.shape(),
-            to_py_strides(runtime::get_bytes(tensor.datatype()), tensor.strides()),
-            src_buffer.data());
-    })
-    .def_property_readonly("dtype", [](runtime_tensor &tensor) {
-        return to_dtype(tensor.datatype());
-    })
-    .def_property_readonly("shape", [](runtime_tensor &tensor) {
-        return to_py_shape(tensor.shape());
-    });
-```
-
-**[Attributes]**
-
-| Name  | Type             | Description          |
-| ----- | ---------------- | -------------------- |
-| dtype | Python data type | Data type of the tensor |
-| shape | list             | Shape of the tensor  |
-
-#### from_numpy
-
-**Description**:
-
-Constructs a `RuntimeTensor` object from a `numpy.ndarray`.
-
-**Definition**:
-
-`from_numpy(py::array arr)`
-
-**[Parameters]**
-
-| Name | Type          | Description            |
-| ---- | ------------- | ---------------------- |
-| arr  | numpy.ndarray | `numpy.ndarray` object |
-
-**[Return Value]**
-
-`RuntimeTensor`
-
-**Example**:
-
-`tensor = nncase.RuntimeTensor.from_numpy(self.inputs[i]['data'])`
-
-#### copy_to
-
-**Description**:
-
-Copies a `RuntimeTensor`.
-
-**Definition**:
-
-`copy_to(RuntimeTensor to)`
-
-**[Parameters]**
-
-| Name | Type          | Description            |
-| ---- | ------------- | ---------------------- |
-| to   | RuntimeTensor | `RuntimeTensor` object |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-`sim.get_output_tensor(i).copy_to(to)`
-
-#### to_numpy
-
-**Description**:
-
-Converts a `RuntimeTensor` to a `numpy.ndarray` object.
-
-**Definition**:
-
-`to_numpy()`
-
-**[Parameters]**
-
-None
-
-**[Return Value]**
-
-`numpy.ndarray` object
-
-**Example**:
-
-`arr = sim.get_output_tensor(i).to_numpy()`
-
-#### Simulator
-
-**Description**:
-
-The `Simulator` class is used to run kmodel inference on a PC.
-
-**Definition**:
-
-```python
-py::class_<interpreter>(m, "Simulator")
-    .def(py::init())
-    .def("load_model", [](interpreter &interp, gsl::span<const gsl::byte> buffer) { interp.load_model(buffer).unwrap_or_throw(); })
-    .def_property_readonly("inputs_size", &interpreter::inputs_size)
-    .def_property_readonly("outputs_size", &interpreter::outputs_size)
-    .def("get_input_desc", &interpreter::input_desc)
-    .def("get_output_desc", &interpreter::output_desc)
-    .def("get_input_tensor", [](interpreter &interp, size_t index) { return interp.input_tensor(index).unwrap_or_throw(); })
-    .def("set_input_tensor", [](interpreter &interp, size_t index, runtime_tensor tensor) { return interp.input_tensor(index, tensor).unwrap_or_throw(); })
-    .def("get_output_tensor", [](interpreter &interp, size_t index) { return interp.output_tensor(index).unwrap_or_throw(); })
-    .def("set_output_tensor", [](interpreter &interp, size_t index, runtime_tensor tensor) { return interp.output_tensor(index, tensor).unwrap_or_throw(); })
-    .def("run", [](interpreter &interp) { interp.run().unwrap_or_throw(); });
-```
-
-**[Attributes]**
-
-| Name         | Type | Description     |
-| ------------ | ---- | --------------- |
-| inputs_size  | int  | Number of inputs |
-| outputs_size | int  | Number of outputs |
-
-**Example**:
-
-`sim = nncase.Simulator()`
-
-#### load_model
-
-**Description**:
-
-Loads a kmodel.
-
-**Definition**:
-
-`load_model(model_content)`
-
-**[Parameters]**
-
-| Name          | Type     | Description         |
-| ------------- | -------- | ------------------- |
-| model_content | byte\[\] | kmodel byte stream  |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-`sim.load_model(kmodel)`
-
-#### get_input_desc
-
-**Description**:
-
-Gets the description of the input at the specified index.
-
-**Definition**:
-
-`get_input_desc(index)`
-
-**[Parameters]**
-
-| Name  | Type | Description       |
-| ----- | ---- | ----------------- |
-| index | int  | Index of the input |
-
-**[Return Value]**
-
-`MemoryRange`
-
-**Example**:
-
-`input_desc_0 = sim.get_input_desc(0)`
-
-#### get_output_desc
-
-**Description**:
-
-Gets the description of the output at the specified index.
-
-**Definition**:
-
-`get_output_desc(index)`
-
-**[Parameters]**
-
-| Name  | Type | Description       |
-| ----- | ---- | ----------------- |
-| index | int  | Index of the output |
-
-**[Return Value]**
-
-`MemoryRange`
-
-**Example**:
-
-`output_desc_0 = sim.get_output_desc(0)`
-
-#### get_input_tensor
-
-**Description**:
-
-Gets the `RuntimeTensor` of the input at the specified index.
-
-**Definition**:
-
-`get_input_tensor(index)`
-
-**[Parameters]**
-
-| Name  | Type | Description            |
-| ----- | ---- | ---------------------- |
-| index | int  | Index of the input tensor |
-
-**[Return Value]**
-
-`RuntimeTensor`
-
-**Example**:
-
-`input_tensor_0 = sim.get_input_tensor(0)`
-
-#### set_input_tensor
-
-**Description**:
-
-Sets the `RuntimeTensor` of the input at the specified index.
-
-**Definition**:
-
-`set_input_tensor(index, tensor)`
-
-**[Parameters]**
-
-| Name   | Type          | Description            |
-| ------ | ------------- | ---------------------- |
-| index  | int           | Index of the input tensor |
-| tensor | RuntimeTensor | Input tensor           |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-`sim.set_input_tensor(0, nncase.RuntimeTensor.from_numpy(self.inputs[0]['data']))`
-
-#### get_output_tensor
-
-**Description**:
-
-Gets the `RuntimeTensor` of the output at the specified index.
-
-**Definition**:
-
-`get_output_tensor(index)`
-
-**[Parameters]**
-
-| Name  | Type | Description            |
-| ----- | ---- | ---------------------- |
-| index | int  | Index of the output tensor |
-
-**[Return Value]**
-
-`RuntimeTensor`
-
-**Example**:
-
-`output_arr_0 = sim.get_output_tensor(0).to_numpy()`
-
-#### set_output_tensor
-
-**Description**:
-
-Sets the `RuntimeTensor` of the output at the specified index.
-
-**Definition**:
-
-`set_output_tensor(index, tensor)`
-
-**[Parameters]**
-
-| Name   | Type          | Description            |
-| ------ | ------------- | ---------------------- |
-| index  | int           | Index of the output tensor |
-| tensor | RuntimeTensor | Output tensor           |
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-`sim.set_output_tensor(0, tensor)`
-
-#### run
-
-**Description**:
-
-Runs kmodel inference.
-
-**Definition**:
-
-`run()`
-
-**[Parameters]**
-
-None
-
-**[Return Value]**
-
-None
-
-**Example**:
-
-`sim.run()`
-
-### Examples
-
-**Precondition**: The `yolov5s_onnx.py` script has already compiled the `yolov5s.onnx` model.
-
-The `yolov5s_onnx_simu.py` script is located in the `/path/to/k230_sdk/src/big/nncase/examples/scripts` subdirectory and contains the following content:
-
-```python
-import os
-import copy
-import argparse
-import numpy as np
-import onnx
-import onnxruntime as ort
-import nncase
-
-def read_model_file(model_file):
-    with open(model_file, 'rb') as f:
-        model_content = f.read()
-    return model_content
-
-def cosine(gt, pred):
-    return (gt @ pred) / (np.linalg.norm(gt, 2) * np.linalg.norm(pred, 2))
-
-def main():
-    parser = argparse.ArgumentParser(prog="nncase")
-    parser.add_argument("--model", type=str, help='original model file')
-    parser.add_argument("--model_input", type=str, help='input bin file for original model')
-    parser.add_argument("--kmodel", type=str, help='kmodel file')
-    parser.add_argument("--kmodel_input", type=str, help='input bin file for kmodel')
-    args = parser.parse_args()
-
-    # cpu inference
-    ort_session = ort.InferenceSession(args.model)
-    output_names = []
-    model_outputs = ort_session.get_outputs()
-    for i in range(len(model_outputs)):
-        output_names.append(model_outputs[i].name)
-    model_input = ort_session.get_inputs()[0]
-    model_input_name = model_input.name
-    model_input_type = np.float32
-    model_input_shape = model_input.shape
-    model_input_data = np.fromfile(args.model_input, model_input_type).reshape(model_input_shape)
-    cpu_results = []
-    cpu_results = ort_session.run(output_names, { model_input_name : model_input_data })
-
-    # create simulator
-    sim = nncase.Simulator()
-
-    # read kmodel
-    kmodel = read_model_file(args.kmodel)
-
-    # load kmodel
-    sim.load_model(kmodel)
-
-    # read input.bin
-    # input_tensor=sim.get_input_tensor(0).to_numpy()
-    dtype = sim.get_input_desc(0).dtype
-    input = np.fromfile(args.kmodel_input, dtype).reshape([1, 3, 320, 320])
-
-    # set input for simulator
-    sim.set_input_tensor(0, nncase.RuntimeTensor.from_numpy(input))
-
-    # simulator inference
-    nncase_results = []
-    sim.run()
-    for i in range(sim.outputs_size):
-        nncase_result = sim.get_output_tensor(i).to_numpy()
-        nncase_results.append(copy.deepcopy(nncase_result))
-
-    # compare
-    for i in range(sim.outputs_size):
-        cos = cosine(np.reshape(nncase_results[i], (-1)), np.reshape(cpu_results[i], (-1)))
-        print('output {0} cosine similarity : {1}'.format(i, cos))
-
-if __name__ == '__main__':
-    main()
-```
-
-Run the inference script:
-
-```shell
-root@5f718e19f8a7:/mnt/# cd src/big/nncase/examples
-root@5f718e19f8a7:/mnt/src/big/nncase/examples # export PATH=$PATH:/usr/local/lib/python3.8/dist-packages/
-root@5f718e19f8a7:/mnt/src/big/nncase/examples # python3 scripts/yolov5s_onnx_simu.py --model models/yolov5s.onnx --model_input object_detect/data/input_fp32.bin --kmodel tmp/yolov5s_onnx/test.kmodel --kmodel_input object_detect/data/input_uint8.bin
-```
-
-Comparison of `nncase` simulator and CPU inference results:
-
-```sh
-output 0 cosine similarity : 0.9997244477272034
-output 1 cosine similarity : 0.999757707118988
-output 2 cosine similarity : 0.9997308850288391
-```
-
-## KPU Runtime APIs (C++)
-
-### Introduction
-
-KPU Runtime APIs are used to load kmodel on AI devices, set input data, execute KPU/CPU computation, and get output data, etc.
-
-Currently, only C++ APIs are provided. The relevant header files and static libraries are located in the `/path/to/k230_sdk/src/big/nncase/riscv64` directory.
-
-```shell
-$ tree -L 3 riscv64/
-riscv64/
-├── gsl
-│   └── gsl-lite.hpp
-├── nncase
-│   ├── include
-│   │   └── nncase
-│   └── lib
-│       ├── cmake
-│       ├── libfunctional_k230.a
-│       ├── libnncase.rt_modules.k230.a
-│       └── libNncase.Runtime.Native.a
-└── rvvlib
-    ├── include
-    │   ├── k230_math.h
-    │   ├── nms.h
-    │   └── rvv_math.h
-    └── librvv.a
-
-8 directories, 8 files
-```
-
-### APIs
-
-#### hrt::create
-
-**Description**:
-
-Creates a `runtime_tensor`.
-
-**Definition**:
-
-```cpp
-(1) NNCASE_API result<runtime_tensor> create(typecode_t datatype, dims_t shape, memory_pool_t pool = pool_shared_first) noexcept;
-(2) NNCASE_API result<runtime_tensor> create(typecode_t datatype, dims_t shape, gsl::span<gsl::byte> data, bool copy,
-       memory_pool_t pool = pool_shared_first) noexcept;
-(3) NNCASE_API result<runtime_tensor> create(typecode_t datatype, dims_t shape, strides_t strides, gsl::span<gsl::byte> data, bool copy, memory_pool_t pool = pool_shared_first, uintptr_t physical_address = 0) noexcept;
-```
-
-**[Parameters]**
-
-| Name             | Type                   | Description                            |
-| ---------------- | ---------------------- | -------------------------------------- |
-| datatype         | typecode_t             | Data type, e.g., dt_float32, dt_uint8  |
-| shape            | dims_t                 | Shape of the tensor                    |
-| data             | gsl::span\<gsl::byte\> | User data buffer                       |
-| copy             | bool                   | Whether to copy                        |
-| pool             | memory_pool_t          | Memory pool type, default is pool_shared_first |
-| physical_address | uintptr_t              | Physical address specified by the user |
-
-**[Return Value]**
-
-`result<runtime_tensor>`
-
-**Example**:
-
-```cpp
-// create input tensor
-auto input_desc = interp.input_desc(0);
-auto input_shape = interp.input_shape(0);
-auto input_tensor = host_runtime_tensor::create(input_desc.datatype, input_shape, hrt::pool_shared).expect("cannot create input tensor");
-```
-
-#### hrt::sync
-
-**Description**:
-
-Synchronizes the cache of the tensor.
-
-- For user input data, this interface's `sync_write_back` should be called to ensure the data is flushed to DDR.
-- For GNNE/AI2D computation output data, the GNNE/AI2D runtime has already performed `sync_invalidate` by default.
-
-**Definition**:
-
-`NNCASE_API result<void> sync(runtime_tensor &tensor, sync_op_t op, bool force = false) noexcept;`
-
-**Parameters**:
-
-| Name   | Type           | Description                                                                                 |
-| ------ | -------------- | ------------------------------------------------------------------------------------------- |
-| tensor | runtime_tensor | The tensor to operate on                                                                    |
-| op     | sync_op_t      | `sync_invalidate` (invalidate the tensor cache) or `sync_write_back` (write the tensor cache to DDR) |
-| force  | bool           | Whether to force execution                                                                  |
-
-**Return Value**:
-
-`result<void>`
-
-**Example**:
-
-```cpp
-hrt::sync(input_tensor, sync_op_t::sync_write_back, true).expect("sync write_back failed");
-```
-
-#### interpreter::load_model
-
-**Description**：
-
-Loads a kmodel.
-
-**Definition**：
-
-`NNCASE_NODISCARD result<void> load_model(gsl::span<const gsl::byte> buffer) noexcept;`
-
-**Parameters**:
-
-| Name   | Type                          | Description        |
-| ------ | ----------------------------- | ------------------ |
-| buffer | gsl::span \<const gsl::byte\>    | kmodel buffer      |
-
-**Return Value**:
-
-`result<void>`
-
-**Example**:
-
-```cpp
-interpreter interp;
-auto model = read_binary_file<unsigned char>(kmodel);
-interp.load_model({(const gsl::byte *)model.data(), model.size()}).expect("cannot load model.");
-```
-
-#### interpreter::inputs_size
-
-**Description**:
-
-Gets the number of model inputs.
-
-**Definition**:
-
-`size_t inputs_size() const noexcept;`
-
-**Parameters**:
-
-None
-
-**Return Value**：
-
-`size_t`
-
-**Example**:
-
-`auto inputs_size = interp.inputs_size();`
-
-#### interpreter::outputs_size
-
-**Description**:
-
-Gets the number of model outputs.
-
-**Definition**:
-
-`size_t outputs_size() const noexcept;`
-
-**Parameters**:
-
-None
-
-**Return Value**：
-
-`size_t`
-
-**Example**：
-
-`auto outputs_size = interp.outputs_size();`
-
-#### interpreter::input_shape
-
-**Description**：
-
-Gets the shape of the specified input.
-
-**Definition**：
-
-`const runtime_shape_t &input_shape(size_t index) const noexcept;`
-
-**Parameters**：
-
-| Name  | Type   | Description     |
-| ----- | ------ | --------------- |
-| index | size_t | Index of the input |
-
-**Return Value**:
-
-`runtime_shape_t`
-
-**Example**:
-
-`auto shape = interp.input_shape(0);`
-
-#### interpreter::output_shape
-
-**Description**:
-
-Gets the shape of the specified output.
-
-**Definition**:
-
-`const runtime_shape_t &output_shape(size_t index) const noexcept;`
-
-**Parameters**:
-
-| Name  | Type   | Description     |
-| ----- | ------ | --------------- |
-| index | size_t | Index of the output |
-
-**Return Value**：
-
-`runtime_shape_t`
-
-**Example**：
-
-`auto shape = interp.output_shape(0);`
-
-#### interpreter::input_tensor
-
-**Description**:
-
-Gets/Sets the input tensor at the specified index.
-
-**Definition**：
-
-```cpp
-(1) result<runtime_tensor> input_tensor(size_t index) noexcept;
-(2) result<void> input_tensor(size_t index, runtime_tensor tensor) noexcept;
-```
-
-**Parameters**：
-
-| Name   | Type           | Description                   |
-| ------ | -------------- | ----------------------------- |
-| index  | size_t         | Index of the input            |
-| tensor | runtime_tensor | The runtime tensor for input  |
-
-**Return Value**:
-
-```cpp
-(1) result<runtime_tensor>
-(2) result<void>
-```
-
-**Example**:
-
-```cpp
-// set input
-interp.input_tensor(0, input_tensor).expect("cannot set input tensor");
-```
-
-#### interpreter::output_tensor
-
-**Description**:
-
-Gets/Sets the output tensor at the specified index.
-
-**Definition**:
-
-```cpp
-(1) result<runtime_tensor> output_tensor(size_t index) noexcept;
-(2) result<void> output_tensor(size_t index, runtime_tensor tensor) noexcept;
-```
-
-**Parameters**:
-
-| Name   | Type           | Description                   |
-| ------ | -------------- | ----------------------------- |
-| index  | size_t         | Index of the output           |
-| tensor | runtime_tensor | The runtime tensor for output |
-
-**Return Value**:
-
-```cpp
-(1) result<runtime_tensor>
-(2) result<void>
-```
-
-**Example**:
-
-```cpp
-// get output
-auto output_tensor = interp.output_tensor(0).expect("cannot get output tensor");
-```
-
-#### interpreter::run
-
-**Description**:
-
-Executes KPU computation.
-
-**Definition**:
-
-`result<void> run() noexcept;`
-
-**Parameters**:
-
-None
-
-**Return Value**:
-
-`result<void>`
-
-**Example**:
-
-```cpp
-// run
-interp.run().expect("error occurred in running model");
-```
-
-### Example
-
-```cpp
-#include <chrono>
-#include <fstream>
-#include <iostream>
-#include <nncase/runtime/interpreter.h>
-#include <nncase/runtime/runtime_op_utility.h>
-
-#define USE_OPENCV 1
-#define preprocess 1
-
-#if USE_OPENCV
-#include <opencv2/highgui.hpp>
-#include <opencv2/imgcodecs.hpp>
-#include <opencv2/imgproc.hpp>
-#endif
-
-using namespace nncase;
-using namespace nncase::runtime;
-using namespace nncase::runtime::detail;
-
-#define INPUT_HEIGHT 224
-#define INPUT_WIDTH 224
-#define INPUT_CHANNELS 3
-
-template <class T>
-std::vector<T> read_binary_file(const std::string &file_name)
-{
-    std::ifstream ifs(file_name, std::ios::binary);
-    ifs.seekg(0, ifs.end);
-    size_t len = ifs.tellg();
-    std::vector<T> vec(len / sizeof(T), 0);
-    ifs.seekg(0, ifs.beg);
-    ifs.read(reinterpret_cast<char *>(vec.data()), len);
-    ifs.close();
-    return vec;
-}
-
-void read_binary_file(const char *file_name, char *buffer)
-{
-    std::ifstream ifs(file_name, std::ios::binary);
-    ifs.seekg(0, ifs.end);
-    size_t len = ifs.tellg();
-    ifs.seekg(0, ifs.beg);
-    ifs.read(buffer, len);
-    ifs.close();
-}
-
-static std::vector<std::string> read_txt_file(const char *file_name)
-{
-    std::vector<std::string> vec;
-    vec.reserve(1024);
-
-    std::ifstream fp(file_name);
-    std::string label;
-
-    while (getline(fp, label))
-    {
-        vec.push_back(label);
-    }
-
-    return vec;
-}
-
-template<typename T>
-static int softmax(const T* src, T* dst, int length)
-{
-    const T alpha = *std::max_element(src, src + length);
-    T denominator{ 0 };
-
-    for (int i = 0; i < length; ++i) {
-        dst[i] = std::exp(src[i] - alpha);
-        denominator += dst[i];
-    }
-
-    for (int i = 0; i < length; ++i) {
-        dst[i] /= denominator;
-    }
-
-    return 0;
-}
-
-#if USE_OPENCV
-std::vector<uint8_t> hwc2chw(cv::Mat &img)
-{
-    std::vector<uint8_t> vec;
-    std::vector<cv::Mat> rgbChannels(3);
-    cv::split(img, rgbChannels);
-    for (auto i = 0; i < rgbChannels.size(); i++)
-    {
-        std::vector<uint8_t> data = std::vector<uint8_t>(rgbChannels[i].reshape(1, 1));
-        vec.insert(vec.end(), data.begin(), data.end());
-    }
-
-    return vec;
-}
-#endif
-
-static int inference(const char *kmodel_file, const char *image_file, const char *label_file)
-{
-    // load kmodel
-    interpreter interp;
-    
-    // Load kmodel from memory
-    auto kmodel = read_binary_file<unsigned char>(kmodel_file);
-    interp.load_model({ (const gsl::byte *)kmodel.data(), kmodel.size() }).expect("cannot load kmodel.");
-    // Load kmodel from file stream
-    std::ifstream ifs(kmodel_file, std::ios::binary);
-    interp.load_model(ifs).expect("cannot load kmodel");
-    
-
-    // create input tensor
-    auto input_desc = interp.input_desc(0);
-    auto input_shape = interp.input_shape(0);
-    auto input_tensor = host_runtime_tensor::create(input_desc.datatype, input_shape, hrt::pool_shared).expect("cannot create input tensor");
-    interp.input_tensor(0, input_tensor).expect("cannot set input tensor");
-
-    // create output tensor
-    // auto output_desc = interp.output_desc(0);
-    // auto output_shape = interp.output_shape(0);
-    // auto output_tensor = host_runtime_tensor::create(output_desc.datatype, output_shape, hrt::pool_shared).expect("cannot create output tensor");
-    // interp.output_tensor(0, output_tensor).expect("cannot set output tensor");
-
-    // set input data
-    auto dst = input_tensor.impl()->to_host().unwrap()->buffer().as_host().unwrap().map(map_access_::map_write).unwrap().buffer();
-#if USE_OPENCV
-    cv::Mat img = cv::imread(image_file);
-    cv::resize(img, img, cv::Size(INPUT_WIDTH, INPUT_HEIGHT), cv::INTER_NEAREST);
-    auto input_vec = hwc2chw(img);
-    memcpy(reinterpret_cast<char *>(dst.data()), input_vec.data(), input_vec.size());
-#else
-    read_binary_file(image_file, reinterpret_cast<char *>(dst.data()));
-#endif
-    hrt::sync(input_tensor, sync_op_t::sync_write_back, true).expect("sync write_back failed");
-
-    // run
-    size_t counter = 1;
-    auto start = std::chrono::steady_clock::now();
-    for (size_t c = 0; c < counter; c++)
-    {
-        interp.run().expect("error occurred in running model");
-    }
-    auto stop = std::chrono::steady_clock::now();
-    double duration = std::chrono::duration<double, std::milli>(stop - start).count();
-    std::cout << "interp.run() took: " << duration / counter << " ms" << std::endl;
-
-    // get output data
-    auto output_tensor = interp.output_tensor(0).expect("cannot set output tensor");
-    dst = output_tensor.impl()->to_host().unwrap()->buffer().as_host().unwrap().map(map_access_::map_read).unwrap().buffer();
-    float *output_data = reinterpret_cast<float *>(dst.data());
-    auto out_shape = interp.output_shape(0);
-    auto size = compute_size(out_shape);
-
-    // postprocess softmax by cpu
-    std::vector<float> softmax_vec(size, 0);
-    auto buf = softmax_vec.data();
-    softmax(output_data, buf, size);
-    auto it = std::max_element(buf, buf + size);
-    size_t idx = it - buf;
-
-    // load label
-    auto labels = read_txt_file(label_file);
-    std::cout << "image classify result: " << labels[idx] << "(" << *it << ")" << std::endl;
-
-    return 0;
-}
-
-int main(int argc, char *argv[])
-{
-    std::cout << "case " << argv[0] << " built at " << __DATE__ << " " << __TIME__ << std::endl;
-    if (argc != 4)
-    {
-        std::cerr << "Usage: " << argv[0] << " <kmodel> <image> <label>" << std::endl;
-        return -1;
-    }
-
-    int ret = inference(argv[1], argv[2], argv[3]);
-    if (ret)
-    {
-        std::cerr << "inference failed: ret = " << ret << std::endl;
-        return -2;
-    }
-
-    return 0;
-}
-```
-
-## AI2D Runtime APIs (C++)
-
-### Introduction
-
-AI2D Runtime APIs are used to configure AI2D parameters on AI devices, generate related register configurations, execute AI2D computations, etc. Please read the last section [Precautions](./K230_nncase_Development_Guide.md#54-Precautions) before use.
-
-#### Supported Format Conversions
-
-| Input Format       | Output Format           | Remarks               |
-| ------------------ | ----------------------- | --------------------- |
-| YUV420_NV12        | RGB_planar/YUV420_NV12  |                       |
-| YUV420_NV21        | RGB_planar/YUV420_NV21  |                       |
-| YUV420_I420        | RGB_planar/YUV420_I420  |                       |
-| YUV400             | YUV400                  |                       |
-| NCHW(RGB_planar)   | NCHW(RGB_planar)        |                       |
-| RGB_packed         | RGB_planar/RGB_packed   |                       |
-| RAW16              | RAW16/8                 | Depth map, performs shift operation |
-
-#### Function Descriptions
-
-| Function              | Description                                                                                     | Remarks           |
-| --------------------- | ----------------------------------------------------------------------------------------------- | ----------------- |
-| Affine Transformation | Supports input formats YUV420, YUV400, RGB (planar/packed); supports depth map RAW16 format; supports output formats YUV400, RGB, depth map |                   |
-| Crop/Resize/Padding   | Supports input YUV420, YUV400, RGB; supports depth map RAW16 format; Resize supports intermediate NCHW arrangement format; supports output formats YUV420, YUV400, RGB | Only supports constant padding |
-| Shift                 | Supports input format Raw16; supports output format Raw8                                        |                   |
-| Sign Bit              | Supports signed and unsigned input                                                              |                   |
-
-### APIs
-
-#### ai2d_format
-
-**Description**:
-
-`ai2d_format` is used to configure the optional data formats for input and output.
-
-**Definition**:
-
-```cpp
-enum class ai2d_format
-{
-    YUV420_NV12 = 0,
-    YUV420_NV21 = 1,
-    YUV420_I420 = 2,
-    NCHW_FMT = 3,
-    RGB_packed = 4,
-    RAW16 = 5,
-};
-```
-
-#### ai2d_interp_method
-
-**Description**:
-
-`ai2d_interp_method` is used to configure the optional interpolation methods.
-
-**Definition**:
-
-```cpp
-enum class ai2d_interp_method
-{
-    tf_nearest = 0,
-    tf_bilinear = 1,
-    cv2_nearest = 2,
-    cv2_bilinear = 3,
-};
-```
-
-#### ai2d_interp_mode
-
-**Description**:
-
-`ai2d_interp_mode` is used to configure the optional interpolation modes.
-
-**Definition**:
-
-```cpp
-enum class ai2d_interp_mode
-{
-    none = 0,
-    align_corner = 1,
-    half_pixel = 2,
-};
-```
-
-#### ai2d_pad_mode
-
-**Description**:
-
-`ai2d_pad_mode` is used to configure the optional padding modes. Currently, only constant padding is supported.
-
-**Definition**:
-
-```cpp
-enum class ai2d_pad_mode
-{
-    constant = 0,
-    copy = 1,
-    mirror = 2,
-};
-```
-
-#### ai2d_datatype_t
-
-**Description**:
-
-`ai2d_datatype_t` is used to set the data types during the AI2D computation process.
-
-**Definition**:
-
-```cpp
-struct ai2d_datatype_t
-{
-    ai2d_format src_format;
-    ai2d_format dst_format;
-    datatype_t src_type;
-    datatype_t dst_type;
-    ai2d_data_loc src_loc = ai2d_data_loc::ddr;
-    ai2d_data_loc dst_loc = ai2d_data_loc::ddr;
-}
-```
-
-**Parameters**:
-
-| Name       | Type          | Description              |
-| ---------- | ------------- | ------------------------ |
-| src_format | ai2d_format   | Input data format        |
-| dst_format | ai2d_format   | Output data format       |
-| src_type   | datatype_t    | Input data type          |
-| dst_type   | datatype_t    | Output data type         |
-| src_loc    | ai2d_data_loc | Input data location, default is DDR |
-| dst_loc    | ai2d_data_loc | Output data location, default is DDR |
-
-**Example**:
-
-```cpp
-ai2d_datatype_t ai2d_dtype { ai2d_format::RAW16, ai2d_format::NCHW_FMT, datatype_t::dt_uint16, datatype_t::dt_uint8 };
-```
-
-#### ai2d_crop_param_t
-
-**Description**:
-
-`ai2d_crop_param_t` is used to configure parameters related to cropping.
-
-**Definition**:
-
-```cpp
-struct ai2d_crop_param_t
-{
-    bool crop_flag = false;
-    int32_t start_x = 0;
-    int32_t start_y = 0;
-    int32_t width = 0;
-    int32_t height = 0;
-}
-```
-
-**Parameters**:
-
-| Name      | Type | Description           |
-| --------- | ---- | --------------------- |
-| crop_flag | bool | Whether to enable cropping |
-| start_x   | int  | Starting pixel in the width direction |
-| start_y   | int  | Starting pixel in the height direction |
-| width     | int  | Crop length in the width direction |
-| height    | int  | Crop length in the height direction |
-
-**Example**:
-
-```cpp
-ai2d_crop_param_t crop_param { true, 40, 30, 400, 600 };
-```
-
-#### ai2d_shift_param_t
-
-**Description**:
-
-`ai2d_shift_param_t` is used to configure parameters related to shifting.
-
-**Definition**:
-
-```cpp
-struct ai2d_shift_param_t
-{
-    bool shift_flag = false;
-    int32_t shift_val = 0;
-}
-```
-
-**Parameters**:
-
-| Name       | Type | Description             |
-| ---------- | ---- | ----------------------- |
-| shift_flag | bool | Whether to enable shifting |
-| shift_val  | int  | Number of bits to shift right |
-
-**Example**:
-
-`ai2d_shift_param_t shift_param { true, 2 };`
-
-#### ai2d_pad_param_t
-
-**Description**:
-
-`ai2d_pad_param_t` is used to configure parameters related to padding.
-
-**Definition**:
-
-```cpp
-struct ai2d_pad_param_t
-{
-    bool pad_flag = false;
-    runtime_paddings_t paddings;
-    ai2d_pad_mode pad_mode = ai2d_pad_mode::constant;
-    std::vector<int32_t> pad_val; // by channel
-}
-```
-
-**Parameters**:
-
-| Name     | Type                   | Description                                                                                                  |
-| -------- | ---------------------- | ------------------------------------------------------------------------------------------------------------ |
-| pad_flag | bool                   | Whether to enable padding                                                                                    |
-| paddings | runtime_paddings_t     | Padding for each dimension, shape=`[4, 2]`, representing the padding count for the front and back of dim0 to dim4, with dim0/dim1 fixed at {0, 0} |
-| pad_mode | ai2d_pad_mode          | Padding mode, only constant padding is supported                                                             |
-| pad_val  | std::vector\<int32_t\> | Padding value for each channel                                                                               |
-
-**Example**:
-
-```cpp
-ai2d_pad_param_t pad_param { false, { { 0, 0 }, { 0, 0 }, { 0, 0 }, { 60, 60 } }, ai2d_pad_mode::constant, { 255 } };
-```
-
-#### ai2d_resize_param_t
-
-**Description**:
-
-`ai2d_resize_param_t` is used to configure parameters related to resizing.
-
-**Definition**:
-
-```cpp
-struct ai2d_resize_param_t
-{
-    bool resize_flag = false;
-    ai2d_interp_method interp_method = ai2d_interp_method::tf_bilinear;
-    ai2d_interp_mode interp_mode = ai2d_interp_mode::none;
-}
-```
-
-**Parameters**:
-
-| Name          | Type               | Description           |
-| ------------- | ------------------ | --------------------- |
-| resize_flag   | bool               | Whether to enable resizing |
-| interp_method | ai2d_interp_method | Interpolation method for resizing |
-| interp_mode   | ai2d_interp_mode   | Resize mode            |
-
-**Example**:
-
-```cpp
-ai2d_resize_param_t resize_param { true, ai2d_interp_method::tf_bilinear, ai2d_interp_mode::half_pixel };
-```
-
-#### ai2d_affine_param_t
-
-**Description**:
-
-`ai2d_affine_param_t` is used to configure parameters related to affine transformations.
-
-**Definition**:
-
-```cpp
-struct ai2d_affine_param_t
-{
-    bool affine_flag = false;
-    ai2d_interp_method interp_method = ai2d_interp_method::cv2_bilinear;
-    uint32_t cord_round = 0;
-    uint32_t bound_ind = 0;
-    int32_t bound_val = 0;
-    uint32_t bound_smooth = 0;
-    std::vector<float> M;
-}
-```
-
-**Parameters**:
-
-| Name          | Type                 | Description                                                                                                                         |
-| ------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| affine_flag   | bool                 | Whether to enable affine transformations                                                                                           |
-| interp_method | ai2d_interp_method   | Interpolation method used for affine transformations                                                                                |
-| cord_round    | uint32_t             | Integer boundary, 0 or 1                                                                                                            |
-| bound_ind     | uint32_t             | Boundary pixel mode, 0 or 1                                                                                                         |
-| bound_val     | uint32_t             | Boundary fill value                                                                                                                 |
-| bound_smooth  | uint32_t             | Boundary smoothing, 0 or 1                                                                                                          |
-| M             | std::vector\<float\> | Vector corresponding to the affine transformation matrix. For affine transformation $Y=\[a_0, a_1; a_2, a_3\] \cdot X + \[b_0, b_1\]$, $M=\{a_0,a_1,b_0,a_2,a_3,b_1\}$ |
-
-**Example**:
-
-```cpp
-ai2d_affine_param_t affine_param { true, ai2d_interp_method::cv2_bilinear, 0, 0, 127, 1, { 0.5, 0.1, 0.0, 0.1, 0.5, 0.0 } };
-```
-
-#### ai2d_builder::ai2d_builder
-
-**Description**:
-
-Constructor for `ai2d_builder`.
-
-**Definition**:
-
-```cpp
-ai2d_builder(dims_t &input_shape, dims_t &output_shape, ai2d_datatype_t ai2d_dtype, ai2d_crop_param_t crop_param, ai2d_shift_param_t shift_param, ai2d_pad_param_t pad_param, ai2d_resize_param_t resize_param, ai2d_affine_param_t affine_param);
-```
-
-**Parameters**:
-
-| Name         | Type                | Description       |
-| ------------ | ------------------- | ----------------- |
-| input_shape  | dims_t              | Input shape       |
-| output_shape | dims_t              | Output shape      |
-| ai2d_dtype   | ai2d_datatype_t     | AI2D data type    |
-| crop_param   | ai2d_crop_param_t   | Crop parameters   |
-| shift_param  | ai2d_shift_param_t  | Shift parameters  |
-| pad_param    | ai2d_pad_param_t    | Pad parameters    |
-| resize_param | ai2d_resize_param_t | Resize parameters |
-| affine_param | ai2d_affine_param_t | Affine parameters |
-
-**Return Value**：
-
-None
-
-**Example**：
-
-```cpp
-dims_t in_shape { 1, ai2d_input_c_, ai2d_input_h_, ai2d_input_w_ };          
-auto out_span = ai2d_out_tensor_.shape();                                    
-dims_t out_shape { out_span.begin(), out_span.end() };                       
-ai2d_datatype_t ai2d_dtype { ai2d_format::NCHW_FMT, ai2d_format::NCHW_FMT, typecode_t::dt_uint8, typecode_t::dt_uint8 };
-ai2d_crop_param_t crop_param { false, 0, 0, 0, 0 };                          
-ai2d_shift_param_t shift_param { false, 0 };                                 
-ai2d_pad_param_t pad_param { true, { { 0, 0 }, { 0, 0 }, { 0, 0 }, { 70, 70 } }, ai2d_pad_mode::constant, { 0, 0, 0 } };
-ai2d_resize_param_t resize_param { true, ai2d_interp_method::tf_bilinear, ai2d_interp_mode::half_pixel };
-ai2d_affine_param_t affine_param { false };                                  
-ai2d_builder_.reset(new ai2d_builder(in_shape, out_shape, ai2d_dtype, crop_param, shift_param, pad_param, resize_param, affine_param));
-```
-
-#### ai2d_builder::build_schedule
-
-**Description**：
-
-Generates the parameters required for AI2D computation.
-
-**Definition**：
-
-```c++
-result<void> build_schedule();
-```
-
-**Parameters**：
-
-None
-
-**Return Value**：
-
-`result<void>`
-
-**Example**：
-
-```c++
-ai2d_builder_->build_schedule();
-```
-
-#### ai2d_builder::invoke
-
-**Description**：
-
-Configures the registers and starts the AI2D computation.
-
-**Definition**：
-
-```c++
-result<void> invoke(runtime_tensor &input, runtime_tensor &output);
-```
-
-**Parameters**：
-
-| Name   | Type           | Description       |
-| ------ | -------------- | ----------------- |
-| input  | runtime_tensor | Input tensor      |
-| output | runtime_tensor | Output tensor     |
-
-**Return Value**：
-
-`result<void>`
-
-**Example**：
-
-```c++
-// run ai2d                                                                  
-ai2d_builder_->invoke(ai2d_in_tensor, ai2d_out_tensor_).expect("error occurred in ai2d running");
-```
-
-### Example
-
-```cpp
-static void test_pad_mini_test(const char *gmodel_file, const char *expect_file)
-{
-    // input tensor
-    dims_t in_shape { 1, 100, 150, 3 };
-    auto in_tensor = host_runtime_tensor::create(dt_uint8, in_shape, hrt::pool_shared).expect("cannot create input tensor");
-    auto mapped_in_buf = std::move(hrt::map(in_tensor, map_access_t::map_write).unwrap());
-    read_binary_file(gmodel_file, reinterpret_cast<char *>(mapped_in_buf.buffer().data()));
-    mapped_in_buf.unmap().expect("unmap input tensor failed");
-    hrt::sync(in_tensor, sync_op_t::sync_write_back, true).expect("write back input failed");
-
-    // output tensor
-    dims_t out_shape { 1, 100, 160, 3 };
-    auto out_tensor = host_runtime_tensor::create(dt_uint8, out_shape, hrt::pool_shared).expect("cannot create output tensor");
-
-    // config ai2d
-    ai2d_datatype_t ai2d_dtype { ai2d_format::RGB_packed, ai2d_format::RGB_packed, dt_uint8, dt_uint8 };
-    ai2d_crop_param_t crop_param { false, 0, 0, 0, 0 };
-    ai2d_shift_param_t shift_param { false, 0 };
-    ai2d_pad_param_t pad_param { true, { { 0, 0 }, { 0, 0 }, { 0, 0 }, { 10, 0 } }, ai2d_pad_mode::constant, { 255, 10, 5 } };
-    ai2d_resize_param_t resize_param { false, ai2d_interp_method::tf_bilinear, ai2d_interp_mode::half_pixel };
-    ai2d_affine_param_t affine_param { false };
-
-    // run
-    ai2d_builder builder { in_shape, out_shape, ai2d_dtype, crop_param, shift_param, pad_param, resize_param, affine_param };
-    auto start = std::chrono::steady_clock::now();
-    builder.build_schedule().expect("error occurred in ai2d build_schedule");
-    builder.invoke(in_tensor, out_tensor).expect("error occurred in ai2d invoke");
-    auto stop = std::chrono::steady_clock::now();
-    double duration = std::chrono::duration<double, std::milli>(stop - start).count();
-    std::cout << "ai2d run: duration = " << duration << " ms, fps = " << 1000 / duration << std::endl;
-
-    // compare
-    auto mapped_out_buf = std::move(hrt::map(out_tensor, map_access_t::map_read).unwrap());
-    auto actual = mapped_out_buf.buffer().data();
-    auto expected = read_binary_file<unsigned char>(expect_file);
-    int ret = memcmp(reinterpret_cast<void *>(actual), reinterpret_cast<void *>(expected.data()), expected.size());
-    if (!ret)
-    {
-        std::cout << "compare output succeed!" << std::endl;
-    }
-    else
-    {
-        auto cos = cosine(reinterpret_cast<const uint8_t *>(actual), reinterpret_cast<const uint8_t *>(expected.data()), expected.size());
-        std::cerr << "compare output failed: cosine similarity = " << cos << std::endl;
-    }
-}
-```
-
-### Notes
-
-1. Affine and Resize functions are mutually exclusive and cannot be enabled simultaneously.
-1. The input format for the Shift function can only be Raw16.
-1. The pad value is configured per channel, and the number of elements in the list should be equal to the number of channels.
-1. In the current version, when only one AI2D function is needed, other parameters also need to be configured, with the flag set to false, and other fields do not need to be configured.
-1. When configuring multiple functions, the execution order is Crop->Shift->Resize/Affine->Pad. Ensure the parameters match accordingly.
diff --git a/components/canaan/k230/artifacts/README.md b/components/canaan/k230/artifacts/README.md
deleted file mode 100644
index 777f2c0..0000000
--- a/components/canaan/k230/artifacts/README.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# Canaan Kendryte K230 — retained chip documents
-
-Seven Markdown documents retrieved **2026-09-04** from `github.com/kendryte/k230_docs` at commit
-**`f8e30213963e0ed5cf995c3cd4701218a45e4793`** (2025-09-12). Hashes and sizes: `SHA256SUMS`.
-
-```sh
-sha256sum -c SHA256SUMS       # expect 7 × OK
-```
-
-| File | Bytes | Upstream path (under `en/`) |
-|---|---:|---|
-| `K230_datasheet-v1.0-2023-07-06.md` | 83 002 | `00_hardware/K230_datasheet.md` |
-| `K230_brief_datasheet.md` | 7 781 | `K230_brief_datasheet.md` — **tree root, not `00_hardware/`** |
-| `K230_Hardware_Design_Guide.md` | 49 061 | `00_hardware/K230_Hardware_Design_Guide.md` |
-| `K230_PMU_User_Guide.md` | 10 039 | `01_software/board/osdrv/K230_PMU_User_Guide.md` |
-| `K230_nncase_Development_Guide.md` | 81 128 | `01_software/board/ai/K230_nncase_Development_Guide.md` |
-| `K230_RVV_In_Action.md` | 12 528 | `02_applications/tutorials/K230_RVV_In_Action.md` |
-| `K230_RVV_optimization_performance_description.md` | 12 004 | `02_applications/tutorials/K230_RVV_optimization_performance_description.md` |
-
-Renames: only `K230_datasheet.md` → `K230_datasheet-v1.0-2023-07-06.md`, to carry the document
-revision and date in the filename. Contents are byte-identical to upstream.
-
-## ⚠ These are bundled upstream Markdown — their image links do not resolve here
-
-Every one of these files contains image references written **relative to the upstream repository
-layout**, mostly pointing into the **`zh/`** tree (Canaan keeps one copy of the images and both
-language trees reference it):
-
-```
-../../zh/00_hardware/images/K230_block_diagram.png
-../../../../zh/01_software/board/osdrv/images/pmu_hw_top_view.jpg
-images/K230_application_1.png
-```
-
-**80 such links exist across the seven files and none of them resolves locally.** That is
-expected, not a defect: the images were not retrieved, and rewriting upstream Markdown would
-break byte-identity with the pinned commit and invalidate `SHA256SUMS`.
-
-**Link checks over this repository must exclude `components/canaan/k230/artifacts/*.md`**, or
-report 80 false positives. Authored files in this repository are link-checked; bundled upstream
-Markdown is not.
-
-To view the images, use the rendered build:
-`https://www.kendryte.com/k230/en/main/00_hardware/K230_datasheet.html`, or fetch them from
-`https://github.com/kendryte/k230_docs/raw/f8e30213963e0ed5cf995c3cd4701218a45e4793/zh/00_hardware/images/…`.
-
-## Licence
-
-The repository is **BSD-2-Clause**; the documents inside carry a Canaan notice reading "without
-the written permission of the company, any unit or individual shall not disseminate part or all
-of the content of this document in any form." **These conflict.** Recorded, not resolved. All
-seven files are held **unstaged** pending a user decision — see the
-[component README §18](../README.md#18-licensing).
-
-## Not retained
-
-[`CANAAN-EDA-SET.md`](CANAAN-EDA-SET.md) — 22 Canaan **reference-board** EDA and PDF files
-(~19 MB) enumerated with exact byte sizes and reacquisition URLs. They are only in the `zh/`
-tree, and they describe Canaan's own boards, not the LilyGO one.
diff --git a/components/canaan/k230/artifacts/SHA256SUMS b/components/canaan/k230/artifacts/SHA256SUMS
deleted file mode 100644
index 64cbb48..0000000
--- a/components/canaan/k230/artifacts/SHA256SUMS
+++ /dev/null
@@ -1,7 +0,0 @@
-5cb684cf593698defe9b2d0044ec54fbcd2e0045efe6afd3961fe2157edd30ed  K230_brief_datasheet.md
-f0bd20a600be373b8b5ca605d65215651ccb29e7d2c09cfdf26a74bec8ebc556  K230_datasheet-v1.0-2023-07-06.md
-19e7243c50197a4835b9f85ca51c3fc9abd52ca9d353c6a92ddc8eaf9a3384f4  K230_Hardware_Design_Guide.md
-c2b297c9a615e0b67e9bd2c443d7c218a9d3ec4feab33a129e3e8f6ce4132ee5  K230_nncase_Development_Guide.md
-91a057dbc885f9761392f57c67c6e06bbf2a53cd96de558b8de3b58a5e9829d1  K230_PMU_User_Guide.md
-6dc416406711b5490b2dcc927f77997aaa861436a345801116c9f552789a186a  K230_RVV_In_Action.md
-77a7facbfab8cff717f3305635cb1f9f0965dab90431fc98aeb60119152c4cb0  K230_RVV_optimization_performance_description.md
diff --git a/components/cellwise/README.md b/components/cellwise/README.md
deleted file mode 100644
index f7141cf..0000000
--- a/components/cellwise/README.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# CellWise (CW) — battery fuel gauges
-
-Shenzhen CellWise Microelectronics designs the **CW2xxx** family of low-cost
-single-cell Li-ion fuel gauges, widely used in Chinese consumer devices as a
-cheaper alternative to TI's BQ27xxx line.
-
-| Part | Where |
-|---|---|
-| [`cw2017`](cw2017/README.md) | Xteink X4 Pro, Xteink X4 Classic |
-
-**The family trait that bites:** CellWise gauges are **profile-driven**. They
-report nothing useful until the host uploads a battery-model table, and they
-expose **no current register**, so charge/discharge direction is not observable
-from the gauge at all.
diff --git a/components/cellwise/cw2017/README.md b/components/cellwise/cw2017/README.md
deleted file mode 100644
index 0a60ef6..0000000
--- a/components/cellwise/cw2017/README.md
+++ /dev/null
@@ -1,177 +0,0 @@
-# CellWise CW2017 — I²C battery fuel gauge
-
-- **Category:** single-cell Li-ion state-of-charge gauge, I²C.
-- **Manufacturer:** Shenzhen CellWise Microelectronics (深圳市赛微微电子).
-- **Research status:** ⚠ Identified from **firmware reverse engineering plus a
-  live I²C register dump**. No datasheet retrieved.
-- **Retrieved:** 2026-09-04
-
-The battery gauge of the **Xteink X4 Pro** and **X4 Classic**.
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| I²C address | **0x63** (the part's default) | live bus scan + board profile |
-| Bus speed used | 400 kHz | board profile |
-| **State of charge** | register **`0x04`** | `BatteryMonitor`, from OEM RE |
-| **Cell voltage** | registers **`0x02`/`0x03`**, 14-bit, **`mV = (raw·5 + 8) >> 4`** | same |
-| **Battery profile (BATINFO)** | **80 bytes**, registers **`0x10`–`0x5F`** | same |
-| **Reports 0 % until the profile is loaded** | yes | same |
-| **Current register** | **NONE** | same |
-| Charge-state observability | **not observable from the gauge** | same |
-| SDK type | `GaugeType::Cw2017` | `BoardConfig.h` |
-
-## 2. How it was identified — a nice piece of evidence
-
-The address alone was ambiguous. The identification came from an **I²C register
-dump of the live bus**: registers `0x10`–`0x3F` showed *"the classic BATINFO
-battery-model curve"*, and 0x63 is the CW2017's default address.
-
-That mattered because an earlier hypothesis held that **0x63 was a display
-power-management IC** and that the X4 Pro's panel had dead rails needing an
-external supply. That narrative sent the bring-up down a long false path. Reading
-the register contents rather than guessing from the address killed it.
-
-**Reusable lesson:** an I²C address is a weak identifier. A register dump that
-shows a recognisable data *shape* is a strong one.
-
-## 3. The BATINFO profile — the active defect risk
-
-**A CW2017 with no resident profile reports 0 % forever.** It does not error; it
-just reads flat.
-
-`BatteryMonitor` therefore:
-1. verifies the resident profile at `0x10`–`0x5F`;
-2. **re-uploads the OEM 80-byte table** (recovered from the stock firmware's
-   `Cw2017PowerHal` class via Ghidra) if it is missing;
-3. then reads SoC from `0x04`.
-
-Any firmware that talks to this gauge without doing step 2 will show a
-permanently empty battery on a healthy device. **This is the highest-consequence
-software fact about the X4 Pro's power path.**
-
-## 4. Charging state must come from elsewhere
-
-The CW2017 has **no current register**, and on both Xteink boards there is **no
-charger IC on the gauge's I²C bus**. So the gauge cannot tell you whether the
-device is charging.
-
-Both boards solve it the same way: a **charger `STAT` line on GPIO21**, configured
-input / no-pull and read **active-HIGH** (raw level = charging). `BatteryMonitor`
-falls back to this pin when the gauge reports charging as unobservable.
-
-## 5. Datasheet
-
-**Not retrieved.** No public CellWise portal was reached this session. The
-register semantics above come from firmware RE and are consistent with published
-CW2015/CW2017 driver code in the wild, but **have not been checked against a
-vendor document**. Treat the voltage formula in particular as
-`reported-working`, not `datasheet-confirmed`.
-
-## 6. Caveats and unsafe assumptions
-
-- **Do not assume a fresh or replaced cell keeps the profile valid.** The BATINFO
-  table models a *specific* cell chemistry and capacity. Neither Xteink board's
-  battery capacity is documented, so the table cannot be audited.
-- Do not assume the CW2015 register map applies unchanged.
-- **Do not read charge state from this part.** Use the STAT GPIO.
-
----
-
-## Used By
-
-### [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md)
-
-At **0x63** on the shared I²C bus **SDA 39 / SCL 38 @ 400 kHz**, alongside the
-[GT911 touch controller](../../goodix/gt911/README.md) (0x5D) and the
-[BM8563 RTC](../../generic/bm8563/README.md) (0x51), all on Arduino controller 0
-(`Wire`). Charge STAT on **GPIO21**, active-HIGH — recovered from
-`Cw2017PowerHal` vtable slot 3 → IROM `0x4214f67c`, pin `0x15` set in board init
-`0x4214eeb0`. Battery capacity is **unknown**.
-
-→ [`devices/xteink/x4-pro/features/battery-and-power.md`](../../../devices/xteink/x4-pro/features/battery-and-power.md)
-→ [`devices/xteink/x4-pro/pinouts-and-buses.md`](../../../devices/xteink/x4-pro/pinouts-and-buses.md)
-
-### [Xteink X4 Classic](../../../devices/xteink/x4-classic/README.md)
-
-Identical: **0x63** on **SDA 39 / SCL 38 @ 400 kHz**, sharing the bus with the
-BM8563 RTC (0x51) and a [QMI8658 IMU](../../qst/qmi8658a/README.md) (0x6B).
-Charge STAT again **GPIO21** active-HIGH, though the SDK marks the **polarity as
-`PENDING`** on this board.
-
-→ [`devices/xteink/x4-classic/README.md`](../../../devices/xteink/x4-classic/README.md)
-
-## See also
-
-The other two Xteink battery approaches, for contrast:
-[`../../texas-instruments/bq27220/README.md`](../../texas-instruments/bq27220/README.md)
-(X3 — a real impedance-track gauge, **no profile upload needed**) and the
-[X4](../../../devices/xteink/x4/features/battery-and-power.md) (a bare ADC).
-
----
-
-## Datasheet — **not obtained**, 2026-09-11
-
-The record above states *"No datasheet retrieved."* That is still true, and this
-section records what was tried so it is not repeated.
-
-| Source tried | Result |
-|---|---|
-| `http://www.cellwise-semi.com/` (CN) | **200** — site is live and reachable |
-| `http://en.cellwise-semi.com/` | **200** |
-| `…/products/index?ptype=voltameter&voltage=电压型` (voltage-type gauges) | 200, **no `CW2017` on the page** |
-| `…/Home/Index/products` (full product index) | 200 — parts listed are **CW1011, CW2015, CW2215, CW3301, CW6004, CW6301, CW6305, CW6307, CW6308, CW6602, CW6603**. **No CW2017** |
-| `https://www.cellwise-semi.com/uploads/CW2017.pdf`, `/upload/CW2017.pdf` | connection failure / not found |
-| **LCSC** `wmsc.lcsc.com/ftps/wm/search/global?keyword=CW2017` | **403 on every UA tried** (Chrome, WhatsApp, ClaudeBot) |
-| GitHub code search `filename:CW2017 extension:pdf` | **`total_count: 0`** |
-| DuckDuckGo HTML endpoint | **HTTP 202 bot-check**, no results |
-
-### The finding, not just the failure
-
-**CW2017 is not in CellWise's own public catalogue.** Its closest listed
-siblings are **CW2015** and **CW2215**, both voltage-type single-cell gauges.
-Three readings are possible and the evidence does not choose between them:
-
-1. the part is a customer-specific or China-only variant never catalogued;
-2. it is superseded and the page was removed;
-3. it is catalogued only in a region or behind a login not reachable from here.
-
-**This is a real unavailability, not a lazy search.** The part is confirmed
-present and working on hardware — a third party read it on the live I²C bus of a
-physical X4 Pro at `0x63` on 2026-09-06
-([`kycube/x4pro-emu` `docs/hardware.md`](https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/hardware.md)) —
-but its datasheet is not public.
-
-### What the working behaviour already establishes, without a datasheet
-
-From FreeInk's driver plus the live-bus observation, and now independently
-restated by a second firmware project:
-
-| Register | Meaning |
-|---|---|
-| `0x04` | State of charge (%) |
-| `0x02` / `0x03` | VCELL, 14-bit; **mV = (raw × 5 + 8) >> 4** |
-| `0x10`–`0x5F` | **80-byte BATINFO profile.** Until it is written, SoC reads 0 % |
-
-That mV conversion and the 80-byte profile window are the two facts a datasheet
-would normally supply, and both are now corroborated by two independent code
-bases and one live-bus reading. **The remaining unknowns are the alert/threshold
-registers, the sleep behaviour, and what the correct BATINFO curve is for the
-actual cell** — and none of those can be answered from code.
-
-### What would settle it
-
-1. **Chinese-language search**: `CW2017 规格书`, `CW2017 数据手册`,
-   `赛微微电 CW2017` (CellWise = 深圳市赛微微电子). Not attempted this pass.
-2. **LCSC HTML storefront** `https://www.lcsc.com/search?q=CW2017` with UA
-   `WhatsApp/2.23.20.0` — the JSON API 403s but the HTML page returned 200 and
-   was not mined.
-3. **A CW2015 datasheet as a proxy.** CW2015 *is* catalogued. Its register map is
-   likely close, and the differences would themselves be informative — but
-   **a proxy must never be recorded as this part's datasheet.**
-4. Ask the FreeInk authors, who wrote a working driver and presumably had
-   something to write it from.
-
-**Used by:** [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md) ·
-[Xteink X4 Classic](../../../devices/xteink/x4-classic/README.md).
diff --git a/components/changjing/cj2310/README.md b/components/changjing/cj2310/README.md
deleted file mode 100644
index 91be3f1..0000000
--- a/components/changjing/cj2310/README.md
+++ /dev/null
@@ -1,266 +0,0 @@
-# Jiangsu Changjing CJ2310
-
-> **N-channel MOSFET**, 60 V, 3 A, 125 mΩ @ V<sub>GS</sub> = 4.5 V, trench technology, **SOT-23**.
-> Research snapshot **2026-09-01**. Fitted as **`Q4` on sheet 4** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), where it is the **external switching transistor for the e-paper panel's on-chip DC/DC** — the highest-voltage node on the board runs through it.
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Jiangsu Changjing `CJ2310` datasheet, local copy `artifacts/cj2310-changjing-lcsc-mirror.pdf` | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entry `C75882`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 4 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[MAN]** | DKE **EPD Module User Manual** §7.4, held under the [panel record](../../dke/depg0397bbs770f3/README.md) | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and ratings **[DS]**
-
-| Property | Value |
-|---|---|
-| Part | **`CJ2310`** |
-| Manufacturer | **Jiangsu Changjiang Electronics Technology Co., Ltd.** (江苏长电科技) |
-| LCSC part | `C75882` **[CAT]** |
-| Function | **N-channel** enhancement MOSFET, trench |
-| Package | **SOT-23** |
-| **V<sub>(BR)DSS</sub>** | **60 V** |
-| I<sub>D</sub> continuous | **3 A** |
-| R<sub>DS(on)</sub> | **105 mΩ @ 10 V**, **125 mΩ @ 4.5 V** |
-| P<sub>D</sub> | 350 mW **[CAT]** |
-| C<sub>iss</sub> / C<sub>rss</sub> | 247 pF / 19.5 pF **[CAT]** |
-| Q<sub>g</sub> | 6 nC @ 10 V **[CAT]** |
-| V<sub>DS(on)</sub> | 500 mV **[CAT]** |
-| Operating range | −40 °C to +150 °C **[CAT]** |
-| Vendor description | *"uses advanced trench technology to provide excellent R<sub>DS(ON)</sub>, low gate charge and operation with gate voltage as low as **2.5 V**. Suitable for use as a battery protection or in other switching application"* |
-| Vendor applications | *"Battery switch; DC/DC converter"* |
-
-### 1.1 Pinout **[DS]**
-
-| Pin | Function |
-|---:|---|
-| **1** | **GATE** |
-| **2** | **SOURCE** |
-| **3** | **DRAIN** |
-
-Same order as the board's SOT-523 Shikues parts, which makes the schematic
-consistent to read across sheets.
-
-### 1.2 ⚠ 60 V is the property that matters here
-
-Every other MOSFET on this board is a 20 V part. `Q4` is **60 V**, and that is not
-incidental — it is switching the node that generates the e-paper panel's
-**`PREVGH`** and **`PREVGL`** gate-drive rails (§3). Choosing a 60 V device where
-20 V parts serve everywhere else is the designer telling you where the voltage
-is.
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — `Q4`, sheet 4
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-**One instance.**
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes**. Both SKUs carry the identical
-[DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) panel, which needs
-this converter. Not read from the Lite's own schematic, which is published only
-as a 4-sheet `PRJ` PDF.
-
----
-
-## 3. What it actually switches **[SCH-V]**
-
-`Q4` is the switch of a **boost converter plus an inverting charge pump**, both
-controlled by the **SSD1677 driver IC inside the e-paper panel** and both built
-from discrete parts on the mainboard. The controller is on the far side of a
-24-way FPC connector; only the power stage is here.
-
-```
-EPD_3V3_L3 ──[ L8  33 µH ]───┬─────▶|─── D4 ────┬──── PREVGH  ──▶ J5.21
-  SPH252010H330MT            │    1N5819WS      │      (C72 10 µF/25 V)
-                             │                  │
-                        Q4 pin 3 DRAIN          │
-                        (CJ2310, N-channel)     │
-                             │                  │
-  J5.2  GDR ──┬── Q4 pin 1 GATE                 │
-              │                                 │
-         R58 10 kΩ    ┌──┤ C67 10 µF/25 V ├─────┘
-              │       │
-             GND      ├──── D5 1N5819WS ──▶ (up, to the C67 node)
-                      │
-                      ├──── PREVGL ──▶ J5.23    (C73 10 µF/25 V)
-                      │
-                      └──── D6 1N5819WS ──▶ GND
-
-        Q4 pin 2 SOURCE ──┬── R59 1.2 Ω ── GND
-                          └── J5.3  RESE   (current sense, back to the panel)
-```
-
-| `Q4` terminal | Net | Note |
-|---|---|---|
-| pin 1 **GATE** | **`GDR`** = `J5`.2 | driven **by the panel**, not by the ESP32 |
-| pin 2 **SOURCE** | `RESE` = `J5`.3, and **`R59` = 1.2 Ω** to GND | the current-sense node |
-| pin 3 **DRAIN** | the switch node: `L8` and `D4`'s anode | |
-
-**How it works.** The SSD1677 asserts `GDR`, `Q4` turns on, current ramps in
-`L8` and develops a voltage across `R59`; the panel watches that voltage on
-`RESE` and releases `GDR` at its peak-current threshold. The inductor's flyback
-then forward-biases `D4` and charges `C72` to **`PREVGH`**, the positive
-gate-drive rail. The same switching node drives `C67` as a flying capacitor, and
-`D5`/`D6` rectify it the other way into **`PREVGL`**, the negative rail.
-
-This matches DKE's own typical application circuit **[MAN]** §7.4 — which is the
-independent confirmation that this reading of the topology is right.
-
-### 3.1 Three consequences worth knowing
-
-1. **Firmware does not control this converter.** `GDR` comes from inside the
-   panel. There is no GPIO, no register on the ESP32-S3 side, and no way to
-   observe it except with a probe. A display that will not refresh because
-   `PREVGH` is not coming up looks, from software, exactly like a panel that is
-   busy.
-2. **`R59` = 1.2 Ω sets the peak current, and it sits in series with a
-   connector.** The sense loop runs mainboard → `J5`.3 → panel and back. Contact
-   resistance in the FPC joint adds to `R59`, *lowering* the peak current the
-   panel thinks it has reached. A partially seated flex therefore produces weak
-   bias rails and **display artefacts**, not a clean failure. **[INF]** This is
-   worth trying before debugging waveform LUTs.
-3. **`R58` = 10 kΩ is a gate pulldown.** With the panel unpowered or the flex
-   unplugged, `GDR` floats; `R58` holds `Q4` off so the converter cannot
-   self-start into an undefined state.
-
-### 3.2 Operating conditions
-
-| Parameter | Rating | On this board | Margin |
-|---|---|---|---|
-| V<sub>DS</sub> | **60 V** | switch node swings to `PREVGH` + V<sub>F</sub> | see below |
-| V<sub>GS</sub> | ±20 V (typical for the class; **not transcribed from [DS]**) | `GDR` from a 3.3 V-class panel driver | comfortable |
-| I<sub>D</sub> | 3 A | inductor peak set by `R59` | comfortable |
-| R<sub>DS(on)</sub> | 125 mΩ @ 4.5 V | in series with `R59` = 1.2 Ω in the sense path | **~10 % of the sense resistance** |
-
-**On V<sub>DS</sub>:** the SSD1677's `VGH` is typically around **+22 V** and
-`VGL` around **−20 V** for this panel class. The drain therefore swings to
-roughly `PREVGH` + 0.5 V ≈ 22.5 V, well inside 60 V. The 60 V part gives ~2.7×
-margin, which is appropriate for a hard-switched node with inductor ringing.
-**[INF]** — the exact `VGH`/`VGL` values were **not** read from the SSD1677
-datasheet for this record.
-
-**On R<sub>DS(on)</sub>:** 125 mΩ against `R59` = 1.2 Ω means `Q4`'s channel
-contributes about **10 %** of the total sense resistance. That is not negligible,
-and it is temperature-dependent — R<sub>DS(on)</sub> rises with junction
-temperature, which lowers the peak current slightly as the panel warms. Whether
-the SSD1677's design accounts for this is unknown; a 10 % term suggests the
-resistor value was chosen with the FET's contribution in mind. **[INF]**
-
----
-
-## 4. Substitution
-
-Required: **N-channel**, V<sub>DS</sub> ≥ 60 V (do **not** substitute a 20 V or
-30 V part — §1.2), logic-level threshold (must be fully on from the panel's gate
-drive, which the vendor states works down to **2.5 V**), R<sub>DS(on)</sub>
-≲ 150 mΩ so the sense-path contribution does not shift, SOT-23, **pin 1 = G,
-2 = S, 3 = D**.
-
-| Alternative | Note |
-|---|---|
-| Diodes **DMN6075S**, Vishay **Si2306BDS**, AOS **AO3402** | 60 V-class SOT-23 N-channel |
-| **`2N7002`** | ⚠ **60 V but only ~115 mA** — nowhere near enough, and a classic substitution error |
-| [AOS **AO3400A**](../../alpha-and-omega-semiconductor/ao3400a/README.md) | ⚠ **30 V only.** Documented in this repo, and **not** a substitute here |
-
-**Match R<sub>DS(on)</sub> as well as voltage**, because it is 10 % of the
-current-sense resistance (§3.2) — a much lower-R<sub>DS(on)</sub> part shifts the
-converter's peak current up.
-
----
-
-## 5. Integration pitfalls
-
-1. **60 V for a reason** (§1.2, §3.2). The single most important substitution
-   constraint.
-2. **The gate is driven by the display, not the host** (§3.1). No software
-   control, no software visibility.
-3. **`R59` = 1.2 Ω and `Q4`'s R<sub>DS(on)</sub> are in the same sense path**
-   (§3.2) — changing either changes the panel's bias rails.
-4. **The sense loop crosses an FPC connector** (§3.1) — a mechanical fault
-   presents as a display-quality bug.
-5. **`R58` = 10 kΩ is not optional** (§3.1).
-6. **This node reaches ~±20 V.** The decoupling around `J5` pins 17–24 is
-   **25 V**-rated for that reason. Probe accordingly, and do not hot-plug the
-   panel flex.
-7. **Same maker, adjacent part numbers.** The board also carries
-   [`CJ3439KDW`](../cj3439kdw/README.md); `CJ2310` and `CJ3439KDW` are both
-   Changjing N-channel-bearing parts in different packages with different
-   functions.
-
----
-
-## 6. Open questions
-
-- The SSD1677's actual `VGH`/`VGL` targets on this panel, which set `Q4`'s real
-  V<sub>DS</sub> stress (§3.2) — obtainable from the
-  [SSD1677 record](../../solomon-systech/ssd1677/README.md) and the
-  [panel manual](../../dke/depg0397bbs770f3/README.md), not read for this record.
-- The datasheet's V<sub>GS</sub> maximum and V<sub>GS(th)</sub> — present in the
-  file, not transcribed.
-- The switching frequency of the panel's DC/DC, hence `L8`'s ripple and `Q4`'s
-  switching loss. Not published by DKE or Solomon Systech in the documents held.
-- No measurement of anything.
-
----
-
-## Manufacturer
-
-**Jiangsu Changjiang Electronics Technology Co., Ltd.** (江苏长电科技, "CJ"),
-`www.cj-elec.com`. No vendor sourcing guide exists in this repository yet.
-
-**⚠ Retrieval finding — the LCSC PDF host trap.** LCSC's catalogue gave
-`https://www.lcsc.com/datasheet/lcsc_datasheet_1810010214_…CJ2310_C75882.pdf`,
-which returned **HTTP 200 and 47 960 bytes of HTML** to all five user-agents
-tried. The CDN rewrite worked first try:
-
-```
-wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/1810010214_Jiangsu-Changjing-Electronics-Technology-Co---Ltd--CJ2310_C75882.pdf
-```
-
-**Check the `%PDF` magic bytes; the status code and the extension both lie.**
-`executed-success`, 2026-09-01. Note also that LCSC spells the maker
-**"Changjing"** in filenames while the datasheet header says **"CHANGJIANG"** —
-search both spellings. This belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## Related pages
-
-- [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) — the panel whose DC/DC this serves; §7.4 of its manual is the reference circuit
-- [Solomon Systech SSD1677](../../solomon-systech/ssd1677/README.md) — the controller that drives `GDR`
-- [FPC0.5-SMT-24P-B](../../generic/fpc0.5-smt-24p-b/README.md) — `J5`, the connector this converter's sense loop crosses
-- [1N5819WS](../../generic/1n5819ws/README.md) — `D4`/`D5`/`D6` in the same converter
-- [Changjing CJ3439KDW](../cj3439kdw/README.md) — same maker, `Q1`, the battery-sense gate
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `CJ2310` SOT-23 Plastic-Encapsulate MOSFETs | Jiangsu Changjiang Electronics (via LCSC CDN) | primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/1810010214_Jiangsu-Changjing-Electronics-Technology-Co---Ltd--CJ2310_C75882.pdf> | 2026-09-01 | undated, 5 pp | **60 V**, 3 A, 105/125 mΩ, **pin 1 = G / 2 = S / 3 = D**, the 2.5 V gate-drive claim | `artifacts/cj2310-changjing-lcsc-mirror.pdf` |
-| C1 | LCSC entry `C75882` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `CJ2310` | 2026-09-01 | — | manufacturer; 350 mW; 247 pF/19.5 pF; 6 nC; −40…+150 °C; the (broken) `www.lcsc.com` URL | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `Q4` = `CJ2310`; the whole §3 topology; `L8`, `R58`, `R59`, `C67`, `C72`, `C73`, `D4`–`D6`; the `J5`.2/.3 connections | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| M1 | EPD Module User Manual §7.4 *Typical application circuit* | DKE | primary | see the [panel record](../../dke/depg0397bbs770f3/README.md#12-authoritative-sources) | 2026-09-01 | 30 pp | independent confirmation of the §3 topology | `../../dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/cj2310-changjing-lcsc-mirror.pdf` | 1 218 917 | `8095c146e18963bbe745b141c23716030c3caf7ab08f149070b07c666130deb8` | 5 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) with an intact text
-layer. §3 was read from a 200 dpi render of sheet 4; the text layer in that region
-interleaves the labels of `Q4`, `D4`, `D5`, `D6`, `C67`, `C71`–`C73` and the
-neighbouring translator, and cannot be untangled reliably. The topology was then
-cross-checked against DKE's own reference circuit, which agrees.
diff --git a/components/changjing/cj2310/artifacts/cj2310-changjing-lcsc-mirror.pdf b/components/changjing/cj2310/artifacts/cj2310-changjing-lcsc-mirror.pdf
deleted file mode 100644
index bed6bf1..0000000
Binary files a/components/changjing/cj2310/artifacts/cj2310-changjing-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/changjing/cj3439kdw/README.md b/components/changjing/cj3439kdw/README.md
deleted file mode 100644
index 89757f5..0000000
--- a/components/changjing/cj3439kdw/README.md
+++ /dev/null
@@ -1,318 +0,0 @@
-# Jiangsu Changjing CJ3439KDW
-
-> **Complementary MOSFET pair — one N-channel and one P-channel in a single SOT-363**, ±20 V, 0.75 A / −0.66 A, 380 mΩ @ 4.5 V.
-> Research snapshot **2026-09-01**. Fitted as **`Q1` on sheet 2** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), where the two halves together form the **gated battery-voltage sense divider** — the circuit that lets the board measure the cell without leaking current the rest of the time.
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Jiangsu Changjing `CJ3439KDW` datasheet, **D, Mar 2016**; local copy `artifacts/cj3439kdw-changjing-lcsc-mirror.pdf` | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entry `C99824`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 2 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and ratings **[DS]**
-
-| Property | Value |
-|---|---|
-| Part | **`CJ3439KDW`** |
-| Manufacturer | **Jiangsu Changjiang Electronics Technology Co., Ltd.** (江苏长电科技) |
-| LCSC part | `C99824` **[CAT]** |
-| Function | **N-channel + P-channel complementary pair**, two independent dice in one package |
-| Package | **SOT-363** (SC-88, 6-lead) |
-| Datasheet date | **D, Mar 2016** |
-| Vendor applications | *"Load/power switching; interfacing switching; battery management for ultra small portable electronics; logic level shift"* |
-| Vendor note | *"Including a N-ch **CJ3134K** and a P-ch **CJ3139K** (independently) in a package"* |
-
-| | **N-MOSFET** | **P-MOSFET** |
-|---|---|---|
-| V<sub>DS</sub> | **20 V** | **−20 V** |
-| **V<sub>GS</sub>** | **±12 V** | **±12 V** |
-| I<sub>D</sub> continuous | **0.75 A** | **−0.66 A** |
-| I<sub>DM</sub> pulsed (10 µs) | 1.8 A | −1.2 A |
-| R<sub>DS(on)</sub> @ 4.5 V | **380 mΩ** | 520 mΩ |
-| R<sub>DS(on)</sub> @ 2.5 V | 450 mΩ | 700 mΩ |
-| R<sub>DS(on)</sub> @ 1.8 V | 800 mΩ | 950 mΩ (typ) |
-
-Thermal: R<sub>θJA</sub> **833 °C/W**, T<sub>J</sub> 150 °C, T<sub>stg</sub>
-−55…+150 °C, lead temperature 260 °C. Features listed: low R<sub>DS(on)</sub>,
-operation at low logic-level gate drive, **ESD-protected gates**.
-
-> **V<sub>GS</sub> = ±12 V**, noticeably more headroom than the ±8 V of the
-> board's [SK2301AAT](../../generic/sk2301aat/README.md) and
-> [SK2302AAT](../../generic/sk2302aat/README.md).
-
-### 1.1 Pinout **[DS]** — this is what makes §3 assertable
-
-```
-   D1    G2    S2
-    6     5     4
-    ┌───────────┐
-    │           │
-    └───────────┘
-    1     2     3
-   S1    G1    D2
-```
-
-| Pin | Function | Die |
-|---:|---|---|
-| 1 | `S1` — source | **N-channel** |
-| 2 | `G1` — gate | **N-channel** |
-| 6 | `D1` — drain | **N-channel** |
-| 3 | `D2` — drain | **P-channel** |
-| 4 | `S2` — source | **P-channel** |
-| 5 | `G2` — gate | **P-channel** |
-
-Note the **diagonal layout**: the N-channel occupies pins 1, 2, 6 and the
-P-channel pins 3, 4, 5. Reading it as "left half / right half" is wrong and is an
-easy mistake at a rework bench.
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — `Q1`, sheet 2
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-**One instance.** The schematic draws it as two symbols, **`Q1A`** (the
-N-channel) and **`Q1B`** (the P-channel), which is why the census records `Q1`
-twice — one `CO` marker per drawn part, one physical package.
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes**. The Lite drops only NFC and LoRa and carries the same 1150 mAh
-cell and the same charging arrangement, so it needs the same battery
-measurement. Not read from the Lite's own schematic.
-
----
-
-## 3. What it actually switches **[SCH-V]**
-
-`Q1` is the switch in a **gated battery-voltage divider**. This is the circuit the
-firmware uses to read the cell, and both dice are needed for it.
-
-```
-                    VBAT_L0
-                       │
-              ┌────────┴────────┐
-              │                 │
-         R3 1 MΩ           Q1B pin 4  SOURCE
-              │            (P-channel, CJ3439KDW)
-              ├──────────  Q1B pin 5  GATE
-              │            Q1B pin 3  DRAIN
-     Q1A pin 6 DRAIN            │
-     (N-channel)           R5 1 kΩ
-     Q1A pin 1 SOURCE ─ GND     │
-     Q1A pin 2 GATE             ├──── BAT_ADC ──┬── C7 100 nF/25 V ── GND
-              │                 │               │
-   BAT_ADC_EN ┤            R12 1 kΩ             │
-              │                 │               │
-        R11 100 kΩ             GND              │
-              │                                 │
-             GND                                └── to the M5PM1 BAT_ADC_IN
-```
-
-| Node | Net | Evidence |
-|---|---|---|
-| `Q1A` gate (pin 2) | **`BAT_ADC_EN`**, pulled down by **`R11` = 100 kΩ** | **[SCH-V]** |
-| `Q1A` source (pin 1) | **GND** | **[SCH-V]** |
-| `Q1A` drain (pin 6) | `Q1B`'s gate node, pulled up by **`R3` = 1 MΩ** | **[SCH-V]** |
-| `Q1B` source (pin 4) | **`VBAT_L0`** | **[SCH-V]** |
-| `Q1B` gate (pin 5) | the same node as `Q1A`'s drain | **[SCH-V]** |
-| `Q1B` drain (pin 3) | **`R5` = 1 kΩ** → `BAT_ADC` → **`R12` = 1 kΩ** → GND | **[SCH-V]** |
-| `BAT_ADC` | filtered by **`C7` = 100 nF/25 V** | **[SCH-V]** |
-
-**Operation:**
-
-| `BAT_ADC_EN` | `Q1A` | `Q1B` gate | `Q1B` | `BAT_ADC` | Divider current |
-|---|---|---|---|---|---|
-| **low** (or floating — `R11` holds it) | off | pulled to `VBAT_L0` by `R3` ⇒ V<sub>GS</sub> = 0 | **off** | ~0 V | **only `V`<sub>BAT</sub>`/1 MΩ` ≈ 4 µA through `R3`** |
-| **high** | on | pulled to GND ⇒ V<sub>GS</sub> ≈ −V<sub>BAT</sub> | **on** | **≈ V<sub>BAT</sub> / 2** | ≈ 2 mA through `R5`+`R12` |
-
-`R5` = `R12` = 1 kΩ, so **`BAT_ADC` = V<sub>BAT</sub> × 0.5** — a 4.2 V cell
-presents 2.1 V, comfortably inside a 3.3 V ADC range.
-
-### 3.1 Why the gate exists, and why it is worth 1 kΩ + 1 kΩ
-
-A permanently connected 1 kΩ/1 kΩ divider across a 3.7 V cell burns
-**≈ 1.85 mA continuously**. On a 1150 mAh cell that alone is a **~26-day** flat
-battery with the rest of the board switched off. Unacceptable for a device whose
-selling point is e-paper standby.
-
-Gating it costs one dual MOSFET and two resistors and reduces the standing drain
-to the ~4 µA through `R3` — a **~450× improvement** — while keeping the divider
-low-impedance (1 kΩ) *during* a measurement, which is what an SAR ADC wants for a
-fast, accurate settle. A high-value always-on divider (say 1 MΩ/1 MΩ) would have
-avoided the drain but would need a long settling time and would be noise-prone.
-
-**This is a deliberate and rather good piece of design**, and it is the reason the
-part is a *complementary pair* rather than a single FET: the P-channel does the
-high-side switching and the N-channel provides the level shift that lets a 3.3 V
-logic signal control it against a variable battery rail. **[INF]**
-
-### 3.2 The `_EN` polarity is the right way round, and that is evidence
-
-Note the logic: **`BAT_ADC_EN` high enables the divider.** Had `Q1B` been an
-N-channel with its source at the bottom, `R3` would hold it *on* by default and
-the signal would have to be named `_DIS`. The naming and the topology agree,
-which is a useful independent check that the P-channel identification is right —
-and the datasheet's pinout (§1.1) confirms it directly.
-
-### 3.3 Who owns `BAT_ADC_EN` and `BAT_ADC`
-
-Both belong to the [M5PM1](../../m5stack/m5pm1/README.md) power-management
-coprocessor, not to the ESP32-S3: sheet 2 shows `BAT_ADC_EN_OD` on M5PM1 pin 1
-and `BAT_ADC_IN` on pin 11. **[SCH-V]** So **battery measurement is a
-power-manager function**, and an application reads the cell by asking the M5PM1
-over I²C at `0x6E` rather than by sampling an ADC itself. See
-[`power-architecture.md`](../../../devices/m5stack/papermono/power-architecture.md).
-
-The `_OD` suffix on the M5PM1 pin name indicates an **open-drain** output, which
-`R11` = 100 kΩ complements as the pulldown — meaning the M5PM1 can only pull the
-node *low*, and the enable is… **[INF]** ⚠ this reading and the §3 operating
-table disagree about which way an open-drain output would drive the gate. With an
-open-drain output and a pulldown, the pin cannot drive the gate high at all.
-**Either the `_OD` naming is inherited rather than literal, or there is a pull-up
-not visible in this reading.** Recorded as an open question (§7) rather than
-resolved; the divider topology itself is not in doubt.
-
-### 3.4 Operating conditions — heavily de-rated
-
-| Parameter | Rating | On this board |
-|---|---|---|
-| V<sub>DS</sub> (both) | ±20 V | ≤ 4.35 V |
-| **V<sub>GS</sub>** | **±12 V** | ≤ 4.35 V — **~2.8× margin** |
-| I<sub>D</sub> | 0.75 A / −0.66 A | ~2 mA |
-| R<sub>DS(on)</sub> | 520 mΩ @ −4.5 V (P) | in series with `R5` = 1 kΩ ⇒ **~0.05 % divider error** |
-
-That last row is worth stating: the P-channel's on-resistance sits in series with
-the top leg of the divider, so it perturbs the ratio. At ~520 mΩ against 1 kΩ it
-is **0.05 %** — negligible. But R<sub>DS(on)</sub> rises to 700 mΩ at 2.5 V of
-drive and ~950 mΩ at 1.8 V, so at a **deeply discharged cell** the error grows to
-about 0.1 %, still negligible, and the *real* risk is not accuracy but the FET
-failing to enhance at all. **[INF]**
-
----
-
-## 4. Substitution
-
-| Alternative | Note |
-|---|---|
-| Changjing **`CJ3134K`** + **`CJ3139K`** | The two dice, sold separately — the datasheet says so explicitly **[DS]** |
-| Diodes **DMC2400UV**, AOS **AO6604**, Vishay **Si1029X** | Complementary pairs in SOT-363 / SC-70-6 |
-| Two discrete SOT-523 FETs | ⚠ Doubles the footprint and loses the matched pair; the board already carries [SK2301AAT](../../generic/sk2301aat/README.md) + [SK2302AAT](../../generic/sk2302aat/README.md) doing exactly this on the `VBAT_DET` path |
-
-Required: **one N-channel and one P-channel**, ≥ 20 V, **V<sub>GS</sub> ≥ ±8 V**,
-logic-level thresholds, **and the same SOT-363 pin assignment** — complementary
-pairs in this package do **not** share a universal pinout, and swapping the dice
-turns the circuit into a permanent short from `VBAT_L0` to the divider.
-
----
-
-## 5. Integration pitfalls
-
-1. **The pinout is diagonal** (§1.1): N-channel on 1/2/6, P-channel on 3/4/5.
-   Verify against the replacement's own datasheet, never by assumption.
-2. **`R3` = 1 MΩ is the standing drain**, ~4 µA. If the board's sleep current is
-   being budgeted, this is one of the terms.
-3. **`R11` = 100 kΩ is a safety pulldown.** Without it the divider's state during
-   reset is undefined and the board would leak ~1.85 mA whenever the M5PM1 is not
-   driving the pin.
-4. **`R5` and `R12` must be matched to keep the ratio.** Both are 1 %; the ratio
-   error is therefore up to ~1 %, which is **larger than every other error term
-   in §3.4 combined** and is the dominant uncertainty in the reported battery
-   voltage. **[INF]**
-5. **`BAT_ADC` is an M5PM1 pin, not an ESP32-S3 pin** (§3.3). Firmware reads it
-   over I²C.
-6. **Two `CO` markers, one package** (§2) — a census counts `Q1` twice.
-
----
-
-## 6. A note on the board's two gated-sense circuits
-
-The PaperMono has **two** transistor-gated battery-related nets, and they are
-easily confused:
-
-| | `BAT_ADC` (this record) | `VBAT_DET` ([SK2301AAT](../../generic/sk2301aat/README.md)) |
-|---|---|---|
-| Switch | `Q1` CJ3439KDW, N+P in one package | `Q2` + `Q5`, two discrete SOT-523 FETs |
-| Controlled by | **`BAT_ADC_EN`** — a logic signal from the M5PM1 | **`VUSB_IN`** — a power rail; automatic, no firmware |
-| Output | V<sub>BAT</sub> **÷ 2**, filtered | V<sub>BAT</sub> **unattenuated** |
-| Consumer | M5PM1 ADC | not established |
-| Purpose | measure the cell | detect the cell, probably for the charger |
-
-Same idea, different mechanism, different purpose. **They are not redundant.**
-
----
-
-## 7. Open questions
-
-- **The `_OD` / pulldown contradiction in §3.3.** The M5PM1 pin is named
-  `BAT_ADC_EN_OD` (open-drain) but the gate has only a 100 kΩ pulldown, and an
-  open-drain output cannot then drive it high. Resolving this needs a re-render of
-  the M5PM1 pin region, or the M5PM1 datasheet's pin-type table.
-- Whether firmware calibrates out the `R5`/`R12` tolerance (§5.4).
-- The datasheet's V<sub>GS(th)</sub> and full electrical tables — present in the
-  file, not transcribed here.
-- No measurement of anything: no ADC reading, no leakage, no divider accuracy.
-
----
-
-## Manufacturer
-
-**Jiangsu Changjiang Electronics Technology Co., Ltd.** (江苏长电科技, "CJ"),
-`www.cj-elec.com`. A large Chinese discrete-semiconductor maker, distributed
-mainly through LCSC. No vendor sourcing guide exists in this repository yet.
-The board also carries their [CJ2310](../cj2310/README.md) and, probably, their
-[1N4148WS](../../generic/1n4148ws/README.md).
-
-**⚠ Retrieval finding — the LCSC PDF host trap.** LCSC's catalogue gives the
-datasheet URL as
-`https://www.lcsc.com/datasheet/lcsc_datasheet_1810010613_…CJ3439KDW_C99824.pdf`,
-which returned **HTTP 200 and 47 908 bytes of HTML** to all five user-agents
-tried. Rewriting the host and path to the CDN worked first try:
-
-```
-wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/1810010613_Jiangsu-Changjing-Electronics-Technology-Co---Ltd--CJ3439KDW_C99824.pdf
-```
-
-**Check the `%PDF` magic bytes; the status code and the `.pdf` extension both
-lie.** `executed-success`, 2026-09-01. This belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-Note that LCSC's stored filename spells the company **"Changjing"** while the
-datasheet's own header spells it **"CHANGJIANG"**. Search both.
-
-## Related pages
-
-- [Changjing CJ2310](../cj2310/README.md) — same maker, `Q4`, the e-paper bias switch
-- [Shikues SK2301AAT](../../generic/sk2301aat/README.md) · [SK2302AAT](../../generic/sk2302aat/README.md) — the board's other gated battery circuit (§6)
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — owns `BAT_ADC_EN` and `BAT_ADC`
-- [1150 mAh Li-ion cell](../../generic/papermono-1150mah-liion-cell/README.md) — what is being measured
-- [PaperMono power architecture](../../../devices/m5stack/papermono/power-architecture.md) · [bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `CJ3439KDW` SOT-363 Plastic-Encapsulate MOSFETs | Jiangsu Changjiang Electronics (via LCSC CDN) | primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/1810010613_Jiangsu-Changjing-Electronics-Technology-Co---Ltd--CJ3439KDW_C99824.pdf> | 2026-09-01 | **D, Mar 2016**, 6 pp | complementary N+P construction, **the §1.1 equivalent-circuit pinout**, all §1 maxima, the `CJ3134K`/`CJ3139K` die identification | `artifacts/cj3439kdw-changjing-lcsc-mirror.pdf` |
-| C1 | LCSC entry `C99824` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `CJ3439KDW` | 2026-09-01 | — | manufacturer; 120 pF / 13 pF / 15 pF; 660 mA / 750 mA; the (broken) `www.lcsc.com` URL | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `Q1` = `CJ3439KDW`; the whole §3 topology; `R3`, `R5`, `R11`, `R12`, `C7` values; `BAT_ADC_EN` and `BAT_ADC` nets | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/cj3439kdw-changjing-lcsc-mirror.pdf` | 1 042 949 | `41cb3b3374616678b096dfab449a544e165c1878e2b6d7b2f0fbf1c70effcb66` | 6 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) with an intact text
-layer. §3 was read from a 200 dpi render of sheet 2 **before** the datasheet was
-retrieved; the datasheet's equivalent-circuit pinout then confirmed the channel
-assignment independently — the image showed a complementary pair with the
-P-channel high-side, and `CJ3439KDW` turned out to be exactly that. Two
-independent sources agreeing is why §3 is asserted rather than inferred.
diff --git a/components/changjing/cj3439kdw/artifacts/cj3439kdw-changjing-lcsc-mirror.pdf b/components/changjing/cj3439kdw/artifacts/cj3439kdw-changjing-lcsc-mirror.pdf
deleted file mode 100644
index 42ad7f6..0000000
Binary files a/components/changjing/cj3439kdw/artifacts/cj3439kdw-changjing-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/chipone/co5300/README.md b/components/chipone/co5300/README.md
deleted file mode 100644
index 72302d9..0000000
--- a/components/chipone/co5300/README.md
+++ /dev/null
@@ -1,80 +0,0 @@
-# Chipone CO5300 (also marketed / referenced as ICNA3311)
-
-- **Category:** AMOLED display driver IC, QSPI/MIPI host interfaces.
-- **Manufacturer:** **Chipone Technology (Beijing) Co., Ltd.** — `www.chipone-ic.com`.
-  Established from the datasheet cover; see [§2](#2-reading-that-cover-was-not-trivial).
-- **Retrieved:** 2026-09-07
-
-The display driver of the **LilyGO T-Display-S3 AMOLED 1.64″** (280 × 456) and of two of the
-three round panels sold as **T-Display-S3 AMOLED 1.43″/1.75″** (466 × 466).
-
-## 1. Identity
-
-| Property | Value |
-|---|---|
-| Part | **CO5300** |
-| Datasheet version | **V0.01**, 2023 |
-| Publisher | Chipone Technology (Beijing) Co., Ltd. |
-| Local artifact | [`artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf`](artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf) — **archived**, see the placeholder beside it. 13 236 092 B, SHA-256 `2ad0461aec31aa046e2661f52f43e9c36b36218c58c53f07217c73bef7d710c6` |
-| Mirror sources (two, identical size) | `Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64` → `information/CO5300_V0.01.pdf` @ `e236a4dfb3295c473d8ac7c240cbea93313707c0` · `Xinyuan-LilyGO/T-Display-S3-AMOLED-1.43-1.75` → same filename @ `87aabe888eea6a7c0f95ce1991ca75fa98c2a172` |
-| Licence | Chipone copyright. The 1.64 repo is **GPL-3.0** and the 1.43-1.75 repo **MIT**; neither covers the PDF. **Redistribution status: unknown** |
-
-Archived rather than kept in-tree at 12.6 MiB — it is the largest single artifact this pass
-produced. The placeholder carries the hash, size and both re-acquisition URLs.
-
-## 2. Reading that cover was not trivial
-
-The PDF's text layer uses a **uniform +0x1D code-point offset**. Extracted naively it reads
-`&2||2/(' … &+,321(7HFKQRORJ\`, and through the `/ToUnicode` CMap it reads
-`FOD300 … FHHPONE TecOnology` — *human-legible and wrong*, which is the most dangerous
-extraction failure there is.
-
-Both decode consistently to **`CO5300 … CHIPONE Technology (Beijing) Co., Ltd.
-www.chipone-ic.com Datasheet V0.01 2023`**. Two independent routes converging is what makes the
-identification safe; either alone would have produced a plausible-looking error.
-
-Recorded as a vendor trap in
-[`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md), because it will recur on any
-Chinese-vendor datasheet exported by the same toolchain.
-
-## 3. The ICNA3311 question
-
-LilyGO's 1.64″ README writes the display driver as **"ICNA3311(CO5300)"**. ICNA3311 is also a
-Chipone part number. Whether they are:
-
-- the same die under two order codes,
-- a rebadge for a particular panel maker, or
-- a successor/predecessor pair,
-
-is **not established.** The datasheet LilyGO ships says only *CO5300*. Recorded as an open
-question rather than resolved by assumption.
-
-## 4. Board usage
-
-| Board | Panel | Touch partner | Bus |
-|---|---|---|---|
-| [T-Display-S3 AMOLED 1.64″](../../../devices/lilygo/t-display-s3-amoled-1-64/README.md) | 280 × 456 | [FT3168](../../focaltech/ft3168/README.md) | QSPI |
-| [T-Display-S3 AMOLED 1.43″](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md), build symbol `DO0143FMST10` | 466 × 466 round | FT3168 | QSPI |
-| [T-Display-S3 AMOLED 1.75″](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md), build symbol `H0175Y003AM` | 466 × 466 round | CST9217 | QSPI |
-
-The 1.43″ board's **other** build option, `DO0143FAT01`, uses an
-[SH8601](../../shenghe-microelectronics/sh8601z/README.md) instead — so one product page ships
-two different display controllers.
-
-**Resolution conflict:** LilyGO's README says 466 × 466 while its `pin_config.h` says
-`LCD_WIDTH 473 / LCD_HEIGHT 467`. The likely reading is addressable window versus visible
-circle, but that is inference. See the device record.
-
-Pins on the 1.43/1.75 board: `LCD_SDIO0..3` GPIO 11/13/14/15, `LCD_SCLK` 12, `LCD_CS` 10,
-`LCD_RST` 17, `LCD_EN` 16.
-
-## 5. What was not verified
-
-Beyond the cover, **the datasheet was not read** — no register, timing or electrical value is
-transcribed here. Given the text-layer offset, anyone extracting values from it **must**
-validate against a rendered page first.
-
-## 6. Used by
-
-- [`devices/lilygo/t-display-s3-amoled-1-64`](../../../devices/lilygo/t-display-s3-amoled-1-64/README.md) — 280 × 456; **no schematic and no pin map published for that board**, which is its principal gap
-- [`devices/lilygo/t-display-s3-amoled-1-43-1-75`](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md) — 466 × 466 round, two of three build variants
diff --git a/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf b/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf
deleted file mode 120000
index 5277efe..0000000
--- a/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf
\ No newline at end of file
diff --git a/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf.ARCHIVED.link b/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf.ARCHIVED.link
deleted file mode 120000
index 250d5dd..0000000
--- a/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-co5300-datasheet-v0.01-lilygo-mirror.pdf
\ No newline at end of file
diff --git a/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf.ARCHIVED.md b/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf.ARCHIVED.md
deleted file mode 100644
index 01f987a..0000000
--- a/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# ARCHIVED: `co5300-datasheet-v0.01-lilygo-mirror.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-07**.
-
-**Reason:** 13.2 MB scanned-image datasheet; largest single artifact added by the LilyGO T-Display-S3 family pass. Unique in that Chipone does not publish CO5300 on a public portal, so the LilyGO repository mirror is currently the only reliable copy; archived rather than deleted.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf` |
-| Type | file |
-| Size | 13,236,092 B (12.62 MiB) |
-| SHA-256 | `2ad0461aec31aa046e2661f52f43e9c36b36218c58c53f07217c73bef7d710c6` |
-| Last modified (mtime) | 2026-09-07 10:30:02Z |
-| Upstream repository | Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64 |
-| Commit | `e236a4dfb3295c473d8ac7c240cbea93313707c0` |
-| Author / committer | Xinyuan-LilyGO |
-| Commit date | 2026-07-22 |
-| License | GPL-3.0 declared for the repository; the PDF itself is Chipone copyright, redistribution terms unknown |
-| Path within upstream repo | `information/CO5300_V0.01.pdf` |
-
-## How to get it back
-
-Independent recovery URLs, most reliable first:
-
-- raw file, pinned to commit (exact bytes):  
-  <https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64/e236a4dfb3295c473d8ac7c240cbea93313707c0/information/CO5300_V0.01.pdf>
-- GitHub blob view, pinned to commit:  
-  <https://github.com/Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64/blob/e236a4dfb3295c473d8ac7c240cbea93313707c0/information/CO5300_V0.01.pdf>
-- jsDelivr CDN mirror, pinned to commit:  
-  <https://cdn.jsdelivr.net/gh/Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64@e236a4dfb3295c473d8ac7c240cbea93313707c0/information/CO5300_V0.01.pdf>
-- whole-repository tarball at that commit (**works for directories**):  
-  <https://codeload.github.com/Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64/tar.gz/e236a4dfb3295c473d8ac7c240cbea93313707c0>
-- current default branch (may have changed):  
-  <https://github.com/Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64/raw/HEAD/information/CO5300_V0.01.pdf>
-
-Restore from the local archive:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf" \
-   "components/chipone/co5300/artifacts/co5300-datasheet-v0.01-lilygo-mirror.pdf"
-```
-
-Or re-download and verify:
-
-```bash
-curl -fsSL "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64/e236a4dfb3295c473d8ac7c240cbea93313707c0/information/CO5300_V0.01.pdf" -o "co5300-datasheet-v0.01-lilygo-mirror.pdf"
-echo "2ad0461aec31aa046e2661f52f43e9c36b36218c58c53f07217c73bef7d710c6  co5300-datasheet-v0.01-lilygo-mirror.pdf" | sha256sum -c -
-```
-
-If every URL above is dead, try the Wayback Machine:
-
-    https://web.archive.org/web/2/https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64/e236a4dfb3295c473d8ac7c240cbea93313707c0/information/CO5300_V0.01.pdf
-
diff --git a/components/chipsemi/chsc5816/README.md b/components/chipsemi/chsc5816/README.md
deleted file mode 100644
index 3f0a4bc..0000000
--- a/components/chipsemi/chsc5816/README.md
+++ /dev/null
@@ -1,49 +0,0 @@
-# Chipsemi CHSC5816
-
-- **Category:** capacitive touch controller, I²C slave, aimed at small round and rectangular
-  panels.
-- **Manufacturer:** Chipsemi (Shenzhen) / 海栎创-adjacent Chinese touch vendor. **Not
-  independently verified** — see §1.
-- **Retrieved:** 2026-09-07
-
-> **This record was created 2026-09-07 to fill a gap.** The directory already held
-> [`artifacts/chsc5816-datasheet-v1-20221114-zh.pdf`](artifacts/chsc5816-datasheet-v1-20221114-zh.pdf)
-> with **no `README.md` beside it**. The datasheet was **not read** by this pass; nothing below
-> is transcribed from it. This is a stub that makes the artifact discoverable and records the
-> device that uses it.
-
-## 1. Identity
-
-| Property | Value |
-|---|---|
-| Part | **CHSC5816** |
-| Datasheet | `chsc5816-datasheet-v1-20221114-zh.pdf`, Chinese, dated **2022-11-14** — acquired by an earlier pass; provenance URL not recorded at the time |
-| Interface | I²C |
-| Address | **not verified here** |
-| Manufacturer | the filename and LilyGO's link both point at `lewisxhe/SensorLib`, whose copy is named *"CHSC5816触控芯片使用说明V1-20221114"*. The maker is not stated on any source read by this pass |
-
-**Acquisition route for a fresh copy:** LilyGO links it from
-`github.com/lewisxhe/SensorLib/blob/master/datasheet/` — the same third-party library
-repository it uses for the Hynitron CST parts. Pin that to a commit if you re-fetch it.
-
-## 2. Used By
-
-### LilyGO T-Display AMOLED Lite (1.47″)
-→ [`devices/lilygo/t-display-amoled-lite`](../../../devices/lilygo/t-display-amoled-lite/README.md)
-
-Touch controller of the 194 × 368 AMOLED panel. `TOUCH_IRQ` **GPIO13**, `TOUCH_RST` **GPIO14**,
-I²C SDA **GPIO1** / SCL **GPIO2** — `LilyGo-Display-IDF/main/product_pins.h`, block
-`CONFIG_LILYGO_T_AMOLED_LITE_147` @ `b1a1cc54994bf1b417e3bb30c437bbe1036bff7f`.
-
-**Its signals cross a 1.8 V level translator.** That board's panel and touch controller run at
-1.8 V behind an RS0108 translator — the schematic's net names make it explicit (`TP_INT` ↔
-`TP_INT_1V8`). That is unique in the
-[T-Display-S3 family](../../../devices/lilygo/t-display-s3-shared/README.md) and is why the
-board also carries an [AXP2101 PMU](../../x-powers/axp2101/README.md).
-
-Driver: `lewisxhe/SensorLib` (declared as **v0.2.4** by `LilyGo-AMOLED-Series` @ `6d1dc00`).
-
-## 3. Gaps
-
-Datasheet not read: address, register map, gesture support, timing and electrical limits are
-all unrecorded. Original acquisition URL unknown. Not verified on hardware.
diff --git a/components/consonance/cn809/README.md b/components/consonance/cn809/README.md
deleted file mode 100644
index ba2273b..0000000
--- a/components/consonance/cn809/README.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# CN809 — voltage supervisor / reset generator
-
-> Schematic value on the M5Stack Cardputer boards: **`CN809J`** (designator U3).
-> Record created **2026-09-04**. The `CN809` family is a MicroPower voltage-detector /
-> reset-generator commonly attributed to **Consonance Electronic** (上海如韵 / Consonance
-> Electronic Inc.); the exact manufacturer of the fitted part is **not established** — see *Gaps*.
-
-## Function
-
-A three-terminal supply supervisor. It watches `VCC` and holds its `RESET` output asserted while
-the supply is below a threshold, releasing it after a fixed delay once the supply is good. The
-suffix letter selects the threshold voltage — that is what the `J` in `CN809J` encodes.
-
-Its purpose on a battery device is to guarantee a clean reset on brown-out and on a battery that
-sags under load, rather than letting the MCU run at an undefined voltage.
-
-## Key capabilities
-
-| Property | Value | Evidence |
-|---|---|---|
-| Package | 3-pin SOT-23-class | schematic symbol: `VCC` (3), `GND` (1), `RESET` (2) |
-| Threshold | selected by the suffix; **`J` variant** | value string; **threshold voltage not established** |
-| Reset output | push-pull or open-drain depending on the family member | **not established** |
-| Reset timeout | fixed, typically ~140–240 ms in this family | **not established** |
-
-## Pinout as drawn
-
-| Pin | Name | Net on the Cardputer |
-|---|---|---|
-| 1 | `GND` | GND |
-| 2 | `RESET` | via **R7 100 kΩ** to GND; also to the Q1 gate network |
-| 3 | `VCC` | **`+5VIN`** |
-
-Read from a rendered crop of Cardputer ADV schematic sheet 1.
-
-## Used By
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-Designator **U3**, in the power-input block on sheet 1, immediately beside the **TP4057**
-charger and the `VBAT_IN`/`VBAT_OUT` power-path FETs (Q1–Q3, `LP3218DT1G`).
-
-It supervises the **`+5VIN`** rail — the USB input — and its `RESET` output participates in the
-power-path gating rather than driving the SoC's `EN` pin directly. (The SoC's `CHIP_PU` is driven
-from `ESP_EN` on the Stamp module, through its own RC and 10 kΩ pull-up.)
-
-**Practical consequence for firmware:** none directly. The part is invisible to software. It
-matters for two things a developer will meet:
-
-* The device's behaviour when USB is connected or removed while running, and
-* the interaction with M5Stack's repeated instruction that **the power switch must be ON to
-  charge** — the charge path, the supervisor and the switch are all in the same block.
-
-### M5Stack Cardputer v1.0 (K132) and v1.1 (K132-V11)
-
-[`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md)
-
-**Same part, same designator `U3`.** The value string `CN809J` appears on the v1.0/v1.1 shared
-schematic (SHA-256 `6016c1fe…`) exactly as it does on the ADV — one of several parts confirming
-that the ADV's power train is carried over unchanged from the earlier boards. The others are
-`TP4057` (U1), `SY7088` (U2), `SY8089` (U4) and `LP3218DT1G` (Q1–Q3).
-
-## Substitutes
-
-| Part | Note |
-|---|---|
-| MAX809 / MAX810 | the parts the CN809 family is pin- and function-compatible with by design |
-| APX809, SGM809, HT7XXX | common second sources; **check the threshold suffix**, which is not standardised across vendors |
-| MCU internal brown-out detector | free, but does not gate the power path |
-
-## Gaps
-
-* **No datasheet retrieved.** The threshold voltage the `J` suffix selects, the reset timeout,
-  the output structure (push-pull vs open-drain) and the supply range are all **unknown**.
-* **Manufacturer not confirmed.** `CN809` is used by more than one vendor; the directory is named
-  for the most commonly attributed one and this uncertainty is recorded rather than hidden.
-* No board photograph, so the top marking has not been checked against the schematic value.
diff --git a/components/diodes-incorporated/ap2112k/README.md b/components/diodes-incorporated/ap2112k/README.md
deleted file mode 100644
index b25ecb1..0000000
--- a/components/diodes-incorporated/ap2112k/README.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# Diodes Incorporated AP2112K-3.3
-
-- **Category:** 600 mA low-dropout linear regulator, fixed 3.3 V output, with an enable pin and
-  short-circuit/thermal protection. SOT-25 / SOT-23-5.
-- **Manufacturer:** Diodes Incorporated.
-- **Retrieved:** 2026-09-07
-- **Sibling record here:** [`pi4ioe5v6408`](../pi4ioe5v6408/README.md)
-
-The 3.3 V regulator of the **LilyGO T-Display-S3**, designator `U7`.
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Schematic part string | **`AP2112K-3.3V(RT9013)`** | designator/part text `OUT 5 U7 AP2112K-3.3V(RT9013)` recovered from `T_Display_S3.pdf` @ `ec889e7` |
-| Pins shown | `IN 1`, `GND 2`, `EN 3`, `NC 4`, `OUT 5` | same |
-| Alternate part | **RT9013** (Richtek), named in parentheses on the sheet | same |
-| Datasheet | **not retrieved by this pass.** Diodes Inc. publishes AP2112 openly at `diodes.com`; acquisition is straightforward and simply was not done | — |
-| Local artifact | **none** | — |
-
-**The parenthesised `(RT9013)` is the interesting part.** It is LilyGO explicitly declaring a
-**second source**: AP2112K-3.3 and RT9013-33 are pin-compatible SOT-23-5 3.3 V LDOs from
-different manufacturers. So the part fitted to any given board **may be either**, and that is
-by design rather than by drift — a rare case where LilyGO documented an alternate up front.
-
-Practical difference between the two: AP2112K is rated **600 mA**, RT9013 **500 mA**. Both
-comfortably exceed the ESP32-S3's needs, but if you are budgeting the header's 3V rail against
-the vendor's stated **100 mA** limit, note that the limit is a *board* figure, not the LDO's.
-
-## 2. Board integration
-
-```
-USB-C 5V or VBAT ──→ U7 (AP2112K-3.3 / RT9013) ──→ 3V3 ──┬─→ ESP32-S3, flash   (always on)
-                                                          └─→ Q2/Q3 SI2301 gate ──→ V3V rail
-                                                                    ▲
-                                                               GPIO15
-```
-
-The LDO output feeds the SoC directly and, through a P-channel gate controlled by **GPIO15**,
-the switched `V3V` rail carrying the panel, the touch controller and the header's 3V pin.
-The `EN` pin's control net was **not traced** — the schematic's connectivity was not recovered,
-only its designators.
-
-## 3. Gaps
-
-- Datasheet not retrieved for either part.
-- **Which of the two is actually fitted is unknown**, and there is no reason to expect
-  consistency across production runs.
-- `EN` net not traced; whether the LDO itself can be shut down (as opposed to the downstream
-  gate) is therefore unknown — and that matters for deep-sleep current.
-
-## 4. Used by
-
-### LilyGO T-Display-S3 / T-Display-S3 Touch — designator `U7`
-→ [`devices/lilygo/t-display-s3`](../../../devices/lilygo/t-display-s3/README.md)
-
-Sole 3.3 V regulator. Its output is unswitched to the SoC and switched via GPIO15 to
-everything else — which is why the board runs, but shows nothing, when GPIO15 is left low.
-See [`features/power-and-battery.md`](../../../devices/lilygo/t-display-s3/features/power-and-battery.md).
diff --git a/components/diodes-incorporated/pi4ioe5v6408/README.md b/components/diodes-incorporated/pi4ioe5v6408/README.md
deleted file mode 100644
index 8c0c350..0000000
--- a/components/diodes-incorporated/pi4ioe5v6408/README.md
+++ /dev/null
@@ -1,159 +0,0 @@
-# Diodes Incorporated PI4IOE5V6408
-
-- **Category:** 8-bit **I²C GPIO expander**, 5 V-tolerant, with per-pin high-impedance
-  control and an interrupt output
-- **Package as fitted:** 16-pin (`INT`, `VDD`, `P7…P0`, `ADDR`, `RESET`, `SCL`, `SDA`,
-  `VDD_Bus`, `GND`)
-- **Research status:** **no datasheet retrieved.** Everything below is established from
-  M5Stack schematics, M5Stack's own driver class, and Meshtastic's raw register writes —
-  three independent sources that agree.
-- **Retrieved:** 2026-09-04
-
-> **Why this part has a record:** it appears in **three** M5Stack LoRa products as the thing
-> that switches an SX1262's antenna path. If an M5Stack LoRa radio initialises but does not
-> reach the air, this chip is the first place to look.
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **Diodes Incorporated** (formerly Pericom — the `PI` prefix) | part-number convention, `inferred` |
-| Function | 8-bit I²C I/O expander | vendor docs |
-| I²C address as fitted | **0x43** (7-bit) | M5Stack `PI4IOE5V6408_Class ioe(0x43, …)`; Meshtastic `#define PI4IO_ADDR 0x43` |
-| Address selection | `ADDR` pin (9) strap | schematic |
-| Bus speed used | **400 kHz** in M5Stack's example | vendor code |
-| Supply | `VDD` (2), plus a separate `VDD_Bus` (15) reference | schematic |
-| Interrupt | `INT` (1) — **not routed** on the Cap LoRa-1262 | schematic |
-| Reset | `RESET` (10) — tied off on the Cap LoRa-1262 | schematic |
-
-Pin order as drawn on the M5Stack symbol: 1 `INT`, 2 `VDD`, 3 `P7`, 4 `P6`, 5 `P5`, 6 `P4`,
-7 `P3`, 8 `P2`, 9 `ADDR`, 10 `RESET`, 11 `P1`, 12 `P0`, 13 `SCL`, 14 `SDA`, 15 `VDD_Bus`,
-16 `GND`.
-
-## 2. Registers, as used in the field
-
-Meshtastic writes raw registers; this is the primary evidence for the map. **[SRC]**
-`meshtastic/firmware` `src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp`
-
-| Register | Name used upstream | Purpose |
-|---|---|---|
-| **`0x03`** | `PI4IO_REG_IO_DIR` | per-pin direction; **1 = output** |
-| **`0x05`** | `PI4IO_REG_OUT_SET` | per-pin output level |
-| **`0x07`** | `PI4IO_REG_OUT_H_IM` | per-pin **high-impedance**; **0 = drive** |
-
-⚠ **The high-impedance register is the trap.** A pin configured as an output on this part is
-*still* not driving until `0x07` clears its bit. M5Stack's own source comments the line
-*"Disable high-impedance so pin can actually drive"*. Any port that sets direction and level
-but skips `0x07` produces a pin that measures floating and a radio that appears dead.
-
-Correct order (both vendor and upstream do it this way):
-
-```text
-0x03 |= (1 << n)      # output
-0x07 &= ~(1 << n)     # not high-Z
-0x05 |= (1 << n)      # high
-```
-
-M5Unified wraps the same three writes:
-
-```cpp
-m5::PI4IOE5V6408_Class ioe(0x43, 400000, &m5::In_I2C);
-if (ioe.begin()) {                    // presence == identity, see §4
-    ioe.setDirection(0, true);
-    ioe.setHighImpedance(0, false);
-    ioe.digitalWrite(0, true);
-}
-```
-
-## 3. ⚠ Registers **not** established
-
-`0x00`–`0x02`, `0x04`, `0x06`, `0x08`+ — including the device-ID register, input register,
-pull-up/pull-down configuration, interrupt mask and interrupt status — were **not**
-established by this pass, because no datasheet was retrieved and neither code path touches
-them. Do not guess them.
-
-## 4. Presence at 0x43 is used as a *product* identity, and that is fragile
-
-Both M5Stack's example and Meshtastic decide **which expansion board is fitted** by probing
-address `0x43`:
-
-| Probe | Conclusion drawn |
-|---|---|
-| ACK | Cap LoRa-1262 (U214) — drive P0 high before RF |
-| NAK | Cap LoRa868 (U201) — no antenna switch to set |
-
-Meshtastic probes **`Wire1` first, then `Wire`**, logs `"Cap LoRa-1262 not found"` on
-failure, and continues regardless.
-
-**This is a heuristic, not an identity read.** Anything else answering at 0x43 — including a
-Grove sensor plugged into the Cap's own pass-through I²C port — is mistaken for the antenna
-switch, and the real switch never gets set. Neither code path reads a device-ID register to
-confirm.
-
-## 5. Used By
-
-### [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) — designator `U2`
-
-| Pin | Net | Goes to |
-|---:|---|---|
-| **12 (`P0`)** | **`SX_ANT_SW`** | `Stamp LoRa-1262 Mini` **pin 10 `SW`** — the LoRa antenna/RF switch |
-| 13 (`SCL`) | `SCL` | host **G9** |
-| 14 (`SDA`) | `SDA` | host **G8** |
-| 2 (`VDD`) | `VDD_3V3` | on-board buck |
-| 9 (`ADDR`) | strapped | → 0x43 |
-| 1 (`INT`), 10 (`RESET`), 3–8 (`P7…P2`), 11 (`P1`) | **unused** | — |
-
-**Seven of eight outputs are unused** and already on the host's I²C bus — free expansion for
-a derivative design. Depopulated around it: `R5/NC`, `R6/NC`, `R7/NC` (10 kΩ), `C13/NC`,
-`C14/NC` (100 nF).
-
-Bring-up consequence: **the radio cannot reach the antenna without a working I²C bus**, even
-though SPI, reset and BUSY are all direct host GPIO. Full detail:
-[`devices/m5stack/cap-lora-1262/features/io-expander-and-rf-switch.md`](../../../devices/m5stack/cap-lora-1262/features/io-expander-and-rf-switch.md).
-
-### [M5Stack Stamp C6LoRa (S012)](../../../devices/m5stack/stamp-c6lora/README.md) — inside the module
-
-The vendor description: *"A PI4IOE5V6408 IO expansion chip is integrated internally to
-control the LoRa module's transceiver circuit and **signal amplifier enable** function,
-achieving superior power consumption control while providing additional available IO
-resources."* Five expander pins are brought out of the module as **`EXT_P0 … EXT_P4`**.
-
-Note the extra job here: as well as the RF switch it gates the **SGM13005L4 LNA**, which is
-a real power win compared with an always-on LNA. Address and register usage inside the
-module: **not established**.
-
-### [M5Stack Unit C6L (U202)](../../../devices/m5stack/unit-c6l/README.md) — inside the Stamp C6LoRa
-
-Inherited from the module above.
-
-### ❌ Not the same as the PaperMono's expander
-
-The [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) uses **`M5IOE1`**, a
-different part with its own quirks (including a documented `M5IOE1_PIN_n` = `n − 1`
-off-by-one). Do not carry assumptions across —
-[`components/m5stack/m5ioe1`](../../m5stack/m5ioe1/README.md).
-
-## 6. Caveats
-
-| # | Issue |
-|---|---|
-| 1 | **No datasheet in this repository.** Register map is known only where two code bases exercise it |
-| 2 | **The high-impedance register (`0x07`) is mandatory** and easy to miss — §2 |
-| 3 | **Presence-probing as product identification is fragile** — §4 |
-| 4 | Upstream Meshtastic shipped this init **wrong twice** before it worked (fixes `3261c04a`, 2026-05-18 and `98e0604e`, 2026-05-19; first good release **v2.7.24**). If you are debugging an older build, suspect it |
-| 5 | Whether `INT` is usable, and what the interrupt semantics are, is **unknown** here |
-
-## 7. Local artifacts
-
-**None.** No PI4IOE5V6408 datasheet was retrieved. If one is obtained it belongs in
-`artifacts/` here, and §3 should shrink accordingly.
-
-## 8. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| P-1 | Cap LoRa-1262 schematic V1.1 | M5Stack | primary | schematic | [`devices/m5stack/cap-lora-1262/artifacts/schematic/`](../../../devices/m5stack/cap-lora-1262/artifacts/schematic/) | 2026-09-04 | 16-pin symbol, `P0` → `SX_ANT_SW`, unused pins |
-| P-2 | Cap LoRa-1262 documentation (pin map) | M5Stack | primary | official page | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` | 2026-09-04 | *"Enable the RF antenna switch: Set P0 of the PI4IOE IO expansion chip to high level."* |
-| P-3 | M5Stack Arduino guide | M5Stack | primary | tutorial | `https://docs.m5stack.com/en/arduino/projects/cap/cap_lora868` | 2026-09-04 | `PI4IOE5V6408_Class(0x43, 400000, &m5::In_I2C)` and the three-call sequence |
-| P-4 | Meshtastic `variant.cpp` | Meshtastic | primary | repository | `https://github.com/meshtastic/firmware/blob/master/src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp` | 2026-09-04 | **Register numbers 0x03 / 0x05 / 0x07 and their values** |
-| P-5 | Stamp C6LoRa store listing | M5Stack | primary | store listing | `https://shop.m5stack.com/products/m5stamp-c6lora-module-esp32-c6-sx1262.json` | 2026-09-04 | Second and third **Used By** entries; LNA-enable role |
diff --git a/components/dke/depg0397bbs770f3/README.md b/components/dke/depg0397bbs770f3/README.md
deleted file mode 100644
index 5a4a72d..0000000
--- a/components/dke/depg0397bbs770f3/README.md
+++ /dev/null
@@ -1,601 +0,0 @@
-# DKE DEPG0397BBS770F3
-
-- **Category:** 3.97-inch active-matrix electrophoretic (e-paper) display module — 480 × 800, bi-stable, pure-reflective, SPI, with an [SSD1677](../../solomon-systech/ssd1677/README.md) driver bonded on
-- **Manufacturer:** **DKE Holding Company Limited** (东方科脉 / Dongfang Kemai)
-- **Research status:** the **full 30-page module user manual is retained** in `artifacts/`. **The PDF has no text layer** — every glyph is a vector outline — so every value below was transcribed by rendering pages to PNG at 140 dpi and reading the images. Pages 1, 4, 5, 6, 7, 8, 9, 10, 15, 16, 17, 18, 19, 21, 22, 23, 24, 25 were read this way.
-- **Retrieved:** 2026-09-01
-
-The display of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) and its Lite sibling. The panel is bonded to a 24-pin FPC carrying a 4-wire SPI interface and the discrete boost network the on-chip DC/DC needs.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[MAN]** | Read off a **rendered page image** of `artifacts/depg0397bbs770f3-epd-module-user-manual.pdf`, cited by manual page number | `executed-success` for the transcription; `not-tested` — the vendor's values themselves are unmeasured |
-| **[SCH]** | Read out of `PaperMono_SCH_V0.6.2_20260522.pdf`, cited as sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[CTL]** | Solomon Systech SSD1677 datasheet, Rev 1.0, Nov 2018 — held at [`../../solomon-systech/ssd1677/artifacts/`](../../solomon-systech/ssd1677/README.md) | `not-tested` |
-| **[DOC]** | `docs.m5stack.com` / `shop.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference | `inferred` |
-
-> **Why the transcription method matters.** `pdftotext` returns **nothing** for this document — not garbage, nothing. Had it returned plausible-looking text, that text would have had to be validated against a rendered page before use. It does not, so page rasterisation was the only route. Every figure below can be re-checked by rendering the cited page:
->
-> ```bash
-> nix-shell -p poppler-utils --run \
->   'pdftoppm -r 140 -png -f 7 -l 7 artifacts/depg0397bbs770f3-epd-module-user-manual.pdf pg'
-> ```
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **DKE Holding Company Limited** — the footer of every page; the mechanical drawing carries the Chinese mark **东方科脉** | **[MAN]** pp. 1–30 |
-| Model on the manual cover | **`DEPG0397BBS770F3`** | **[MAN]** p. 1: "Specification for 3.97 inch EPD — Model NO. : DEPG0397BBS770F3" |
-| Model per M5Stack's OTP demo | **`DEPG0397BBS770F3HP-XM`** | **[SRC]** `M5PaperMono-OTP-Demo/README.md`. ⚠ **Conflict — see §8-C1** |
-| Document | **EPD Module User Manual**, 30 pp. The embedded mechanical drawing is `REV. A0`, `FIRST ISSUE`, dated **2024-09-29** | **[MAN]** pp. 1, 6 |
-| Driver IC | **Solomon Systech `SSD1677`**, named on the mechanical drawing | **[MAN]** p. 6, drawing note 2 |
-| Interface | **4-wire SPI** (`BS` pin tied low). 3-wire 9-bit SPI is selectable but not used here | **[MAN]** p. 7 pin 8, p. 8 note 5-5; **[SCH]** |
-| Resolution | **480 (H) × 800 (V)**, DPI **235** | **[MAN]** p. 5 |
-| Reference designator on PaperMono | FPC connector **`J5`**, sheet 4 | **[SCH]** |
-| ⚠ Marking verified? | **No.** No photograph of the fitted panel's model/batch label was inspected. The mechanical drawing shows dedicated `MODEL NO.` and `BATCH NO.` fields on the back of the module, so the fitted part's exact suffix is physically checkable but was not checked here | **[INF]** |
-
----
-
-## 2. Overview and features
-
-**[MAN]** p. 4, verbatim in substance:
-
-> DEPG0397BBS770F3 is an Active Matrix Electrophoretic Display (AM EPD), with interface and a reference system design. The display is capable to display image at **1-bit white and black** full display capabilities. The 3.97 inch active area contains 480 × 800 pixels. The module is a TFT-array driving electrophoresis display, with integrated circuits including gate driver, source driver, MCU interface, timing controller, oscillator, DC-DC, SRAM, LUT, VCOM. Module can be used in portable electronic devices, such as Electronic Shelf Label (ESL) System.
-
-Feature list **[MAN]** p. 4:
-
-- 480 × 800 pixels display
-- High contrast, high reflectance
-- Ultra-wide viewing angle, ultra-low power consumption
-- **Pure reflective mode** — no backlight of its own (PaperMono adds a separate frontlight, §7)
-- **Bi-stable display** — the image persists with power removed
-- Commercial temperature range
-- Landscape / portrait modes
-- Hard-coat antiglare display surface
-- **Ultra-low-current deep sleep mode**
-- **On-chip display RAM**
-- **Waveform can be stored in on-chip OTP or written by MCU**
-- Serial peripheral interface available
-- On-chip oscillator
-- On-chip booster and regulator for generating VCOM, gate and source driving voltage
-- **I²C signal master interface to read an external temperature sensor**
-- **Built-in temperature sensor**
-
-Note the manual describes the panel as **1-bit black and white** and, in the optical table, as `2Grey Level`. M5Stack markets it as 4-level greyscale and ships a working 4-grey demo. **Conflict — §8-C2.**
-
----
-
-## 3. Mechanical and optical specification
-
-### 3.1 Mechanical
-
-**[MAN]** p. 5.
-
-| Parameter | Specification | Unit | Remark |
-|---|---|---|---|
-| Screen size | **3.97** | inch | |
-| Display resolution | **480 (H) × 800 (V)** | pixel | **DPI 235** |
-| Active area | **51.84 × 86.40** | mm | |
-| Pixel pitch | **0.108 × 0.108** | mm | |
-| Pixel configuration | **Rectangle** | | |
-| Outline dimension | **56.24 (H) × 96.62 (V) × 0.92** | mm | |
-| Weight | **10.44 ± 0.5** | g | |
-
-Additional dimensions from the mechanical drawing **[MAN]** p. 6: module thickness **0.92 ± 0.10 mm** without protect film; protect film (TPT) **0.50 mm**; FPC thickness **0.10 ± 0.03 mm**; stiffener on the connector side **0.30 ± 0.05 mm**; FPC tail overall **43.83 ± 0.30 mm**. Drawing tolerances: unmarked angles ± 5°, `.X = ±0.4 mm`, `.XX = ±0.20 mm`, `.XXX = ±0.20 mm`. Drawn by `HH HUANG`, checked `H GONG`, approved `LY YU`. RoHS mark present.
-
-### 3.2 Optical
-
-**[MAN]** p. 5. Measured with an Eye-One Pro spectrophotometer (note 3-1).
-
-| Symbol | Parameter | Conditions | Min | Typ | Max | Unit |
-|---|---|---|---:|---:|---:|---|
-| `KS` | Black state L* value | | – | **24** | 30 | |
-| `WS` | White state L* value | | **58** | **62** | – | |
-| `WS` | **White ghosting ΔL** | Full display mode | – | **1** | – | |
-| `WS` | White ghosting ΔL | Partial display mode | – | **1** | – | |
-| `WS` | White ghosting ΔL | Full-partial display mode | – | **1** | – | |
-| `R` | **White reflectivity** | White | **26** | **30** | – | **%** |
-| `CR` | **Contrast ratio** | **Indoor** | **5** | **7** | – | |
-| `GN` | **`2Grey Level`** | – | – | – | – | |
-| `Life` | | **23 ± 3 °C, 55 ± 10 %RH** | | **5 years** | | |
-
-Notes **[MAN]** p. 5: *3-2.* `CR = surface reflectance with all white pixels / surface reflectance with all black pixels`. *3-3.* "When the product is stored, the display screen should be kept **white and face up**."
-
-Two things worth reading carefully rather than skimming:
-
-- **Contrast ratio 5–7 is an e-paper figure, not an LCD figure.** A typical 7:1 with 30 % white reflectance is roughly newsprint. It is specified *indoor*; outdoors in daylight a reflective display gets better, not worse, but that is not what this row states.
-- **The 5-year life figure is a storage/ambient-condition statement**, not a refresh-count endurance rating. The manual gives **no** maximum refresh count anywhere, which is exactly the number you would want when choosing between refresh modes.
-
----
-
-## 4. FPC pin assignment
-
-**24-pin FPC.** Transcribed in full from **[MAN]** p. 7, §5 *Input/output Pin Assignment*. `I` = input, `O` = output, `I/O` = bidirectional, `P` = power, `C` = capacitor pin.
-
-| No. | Name | I/O | Description | Remark |
-|---:|---|---|---|---|
-| 1 | `NC` | | Do not connect with other NC pins | Keep Open |
-| 2 | `GDR` | O | N-Channel MOSFET Gate Drive Control | |
-| 3 | `RESE` | I | Current Sense Input for the Control Loop | |
-| 4 | `NC` | | Do not connect with other NC pins | Keep Open |
-| 5 | `VDHR` | C | Positive Source driving voltage | |
-| 6 | `NC` | O | I2C Interface to digital temperature sensor Clock pin | Note 5-6 |
-| 7 | `NC` | I/O | I2C Interface to digital temperature sensor Data pin | Note 5-6 |
-| 8 | `BS` | I | Bus Interface selection pin | Note 5-5 |
-| 9 | `BUSY_N` | O | Busy state output pin | Note 5-4 |
-| 10 | `RST_N` | I | Reset signal input. Active Low. | Note 5-3 |
-| 11 | `DC` | I | Data /Command control pin | Note 5-2 |
-| 12 | `CSB` | I | Chip select input pin | Note 5-1 |
-| 13 | `SCL` | I | Serial Clock pin (SPI) | |
-| 14 | `SDA` | I/O | Serial Data pin (SPI) | |
-| 15 | `VDDIO` | P | Power Supply for interface logic pins. It should be connected with VCI | |
-| 16 | `VDD` | P | Power Supply for the chip | |
-| 17 | `GND` | P | Ground | |
-| 18 | `VDDD` | C | Core logic power pin. VDD can be regulated internally from VCI. A capacitor should be connected between VDD and VSS | |
-| 19 | `VPP` | P | FOR TEST | Keep Open |
-| 20 | `VSH` | C | Positive Source driving voltage | |
-| 21 | `VGH` | C | Power Supply pin for Positive Gate driving voltage and VSH1 | |
-| 22 | `VSL` | C | Negative Source driving voltage | |
-| 23 | `VGL` | C | Power Supply pin for Negative Gate driving voltage, VCOM and VSL | |
-| 24 | `VCOM` | C | VCOM driving voltage | |
-
-Notes **[MAN]** p. 8:
-
-- **5-1** `CSB` (CS#): the chip is enabled for MCU communication **only when CS# is pulled LOW**.
-- **5-2** `DC` (D/C#): **HIGH ⇒ data, LOW ⇒ command**, in 4-wire SPI mode.
-- **5-3** `RST_N` (RES#): reset is **active low**.
-- **5-4** `BUSY_N`: "When Busy is **High**, the operation of chip should not be interrupted, **command should not be sent**." The chip raises Busy when outputting a display waveform and when communicating with a digital temperature sensor.
-- **5-5** Bus interface selection:
-
-  | `BS1` state | MCU interface |
-  |---|---|
-  | **L** | **4-line serial peripheral interface (SPI) — 8-bit SPI** |
-  | H | 3-line serial peripheral interface (SPI) — 9-bit SPI |
-
-- **5-6** Pins 6/7 "connect to the VSS if there is no external temperature sensor. External pull-up resistor is required when connecting to an I2C slave."
-
-> ⚠ **`BUSY_N` is named as if active-low but documented as active-high.** Note 5-4 and the SSD1677 datasheet both say the pad outputs **high** while busy **[MAN]** p. 8, **[CTL]** §7 (`0x12`, `0x20`, `0x10`). The `_N` suffix is misleading. M5Stack's driver treats high as busy **[SRC]**.
-
-### 4.1 Pin names differ between the module manual and the controller datasheet
-
-The FPC labels are DKE's; the die pads are Solomon Systech's. They are not the same strings:
-
-| FPC (DKE) | SSD1677 (Solomon Systech) |
-|---|---|
-| `BS` | `BS1` |
-| `BUSY_N` | `BUSY` |
-| `RST_N` | `RES#` |
-| `DC` | `D/C#` |
-| `CSB` | `CS#` |
-| `SDA` | `SDI` / `SDO` (bidirectional on one pad) |
-| `VDHR` | `VSH1R` / `VSH2R` family |
-| `VDDD` | `VDD` |
-
-**[MAN]** p. 7 vs **[CTL]** §5.
-
----
-
-## 5. Electrical characteristics
-
-### 5.1 Absolute maximum ratings
-
-**[MAN]** p. 9, §6.1.
-
-| Parameter | Symbol | Rating | Unit |
-|---|---|---|---|
-| Logic supply voltage | `VCI`, `VDDIO` | **−0.5 to +4.0** | V |
-| Logic input voltage | `VIN` | −0.5 to V<sub>DDIO</sub> + 0.5 | V |
-| Logic output voltage | `VOUT` | −0.5 to V<sub>DDIO</sub> + 0.5 | V |
-| **Operating temperature** | `TOPR` | **0 to +50** | °C |
-| **Storage temperature** | `TSTG` | **−25 to +70** | °C |
-| Optimal storage temperature | `TSTGo` | **23 ± 3** | °C |
-| Optimal storage humidity | `HSTGo` | **55 ± 10** | %RH |
-
-> ⚠ **The panel's operating range is 0 to +50 °C — far narrower than the controller's.** The SSD1677 die is rated `TOPR` **−25 to +85 °C** **[CTL]** §10. The *module* is the binding constraint: below 0 °C the electrophoretic ink itself is out of specification, and the OTP waveform bank does not extend there. Anyone reasoning from the controller datasheet alone will over-estimate the environmental envelope by 25 °C at one end and 35 °C at the other. **[INF]** from two `not-tested` primary sources.
->
-> Storage note **[MAN]** p. 9 note 2 and p. 5 note 3-3: **the screen should be left white and face up** during storage. This is a real requirement for e-paper, not boilerplate — a panel stored dark for long periods can retain the pattern.
-
-### 5.2 Panel DC characteristics
-
-**[MAN]** p. 10, §6.2. Conditions: `VSS = 0 V`, `VCI = 3.0 V`, `TOPR = 23 °C`.
-
-| Parameter | Symbol | Condition | Pin | Min | Typ | Max | Unit |
-|---|---|---|---|---:|---:|---:|---|
-| Single ground | `VSS` | – | | – | 0 | – | V |
-| **Logic supply voltage** | `VCI` | – | `VCI` | **2.2** | **3.0** | **3.3** | V |
-| Power for interface logic pins | `VDDIO` | | `VDDIO` | 2.2 | – | 3.3 | V |
-| Core logic voltage | `VDD` | | `VDD` | 1.7 | 1.8 | 1.9 | V |
-| VCOM_DC output voltage | `Vcom` | – | `VCOM` | −4.0 | – | −0.1 | V |
-| High level input voltage | `VIH` | – | – | 0.8 V<sub>DDIO</sub> | – | – | V |
-| Low level input voltage | `VIL` | – | – | – | – | 0.2 V<sub>DDIO</sub> | V |
-| High level output voltage | `VOH` | I<sub>OH</sub> = −100 µA | – | – | 0.9 V<sub>DDIO</sub> | – | V |
-| Low level output voltage | `VOL` | I<sub>OL</sub> = 100 µA | – | – | – | 0.1 V<sub>DDIO</sub> | V |
-| **Typical power** | `PTYP` | VCI = 3.0 V | | – | – | **36** | mW |
-| **Deep sleep mode power** | `PSTPY` | VCI = 3.0 V | | – | – | **0.003** | mW |
-| **Typical operating current** | `Iopr_VCI` | VCI = 3.0 V | | – | – | **12** | mA |
-| **Image update time** | – | 23 °C | | – | – | **4** | **sec** |
-| **Typical peak current** | `Iopr_VCI` | 2.3 – 3.6 V | | | **120** | – | mA |
-| **Deep sleep mode current** | `Idslp_VCI` | DC/DC off, no clock, no input load, RAM data not retained | | – | – | **1** … **5** | µA |
-
-Notes **[MAN]** p. 10: typical power is measured for a transition from a horizontal 2-scale pattern to a vertical 2-scale pattern; **"the listed electrical characteristics are only guaranteed under the controller & waveform provided by DKE"** (note 3); measured with a Tektronix MDO3014 oscilloscope and TCP0030A current probe (note 4).
-
-> ⚠ **Note 3 is the most consequential sentence in the electrical section.** DKE guarantees these numbers **only for the waveform it programmed into the SSD1677's OTP**. M5GFX does *not* use that waveform — it uploads its own LUTs from flash (§7). Every figure in this table, including the 4-second image update time and the 120 mA peak, is therefore untested for the M5GFX path, and the vendor's own recommendation to prefer the OTP demo follows directly from it.
->
-> **120 mA peak at 3 V is not negligible** for a battery device that also runs Wi-Fi. It is a short burst during the update, but a supply designed to the 12 mA typical figure will sag.
-
-### 5.3 Serial interface timing
-
-**[MAN]** p. 16. Conditions: `VDDIO − VSS = 2.2 V to 3.7 V`, `TOPR = 23 °C`, `CL = 30 pF`.
-
-**Write mode**
-
-| Symbol | Parameter | Min | Typ | Max | Unit |
-|---|---|---:|---:|---:|---|
-| `fSCL` | **SCL frequency (write mode)** | | | **20** | **MHz** |
-| `tCSSU` | CS# low before the first rising edge of SCLK | 20 | | | ns |
-| `tCSHLD` | CS# remains low after the last falling edge of SCLK | 20 | | | ns |
-| `tCSHIGH` | CS# remains high between two transfers | 100 | | | ns |
-| `tSCLCYC` | SCL cycle time | 50 | | | ns |
-| `tSCLHIGH` | SCL high time | 25 | | | ns |
-| `tSCLLOW` | SCL low time | 25 | | | ns |
-| `tSISU` | SDA setup before the next SCL rising edge | 10 | | | ns |
-| `tSIHLD` | SDA hold after the SCL rising edge | 40 | | | ns |
-
-**Read mode**
-
-| Symbol | Parameter | Min | Typ | Max | Unit |
-|---|---|---:|---:|---:|---|
-| `fSCL` | **SCL frequency (read mode)** | | | **2.5** | **MHz** |
-| `tCSSU` | | 100 | | | ns |
-| `tCSHLD` | | 50 | | | ns |
-| `tCSHIGH` | | 250 | | | ns |
-| `tSCLHIGH` / `tSCLLOW` | | 180 | | | ns |
-| `tSOSU` | SDA (read) stable before the next SCL rising edge | | 50 | | ns |
-| `tSOHLD` | SDA (read) stable after the SCL falling edge | | 0 | | ns |
-
-> ⚠ **Write is 20 MHz max; read is 2.5 MHz max — an 8× asymmetry.** Any code that reads back the OTP registers or the status byte at the write clock is out of specification. This figure is identical in the SSD1677 datasheet **[CTL]** §12.1, so the two documents agree.
->
-> ⚠ **M5GFX drives this panel at 40 MHz** — `freq_write = 40000000` **[SRC]** `M5GFX/src/M5GFX.cpp:2114` — which is **twice the documented maximum**. The vendor's own recommended OTP demo uses **20 MHz**, exactly at spec **[SRC]** `EDP_SPI.cpp:33`. See §8-C4.
-
----
-
-## 6. Command set as this module documents it
-
-The command table is the SSD1677's, reproduced by DKE in abbreviated form on **[MAN]** pp. 17–20. The [SSD1677 record](../../solomon-systech/ssd1677/README.md) carries the controller-level detail; what follows is what *DKE* chose to document for *this* module, which is a strict subset and is the better guide to what the fitted OTP actually supports.
-
-| Hex | Command | Parameters DKE documents |
-|---|---|---|
-| `0x01` | Driver Output control | `A[9:0] = 2A7h [POR], 680 MUX`; `B[2:0] = 000 [POR]` |
-| `0x03` | Gate Driving voltage control | `A[4:0] = 17h [POR]`, VGH at 20 V; range 12–20 V |
-| `0x04` | Source Driving voltage control | `A = 41h` (VSH1 15 V), `B = A8h` (VSH2 5.0 V), `C = 32h` (VSL −15 V) |
-| `0x10` | **Deep Sleep mode** | `A[1:0]`: `00` normal [POR], **`11` enter deep sleep**. "BUSY pad will keep output high" |
-| `0x11` | Data Entry mode setting | `A[1:0]` = ID[1:0] increment/decrement; `A[2]` = AM (X- or Y-direction address advance) |
-| `0x12` | SWRESET | Resets commands/parameters to S/W-reset defaults **except `R10h` Deep Sleep**. **RAM is unaffected** |
-| `0x18` | Temperature Sensor Control | **`A = 48h` [POR] external sensor; `A = 80h` internal sensor** |
-| `0x1A` | Temperature Sensor Control (write) | `A[11:0] = 7FFh [POR]` |
-| `0x20` | **Master Activation** | Activates the display-update sequence selected by `R22h`. "User should not interrupt this operation to avoid corruption of panel images" |
-| `0x21` | Display Update Control 1 | `A[7:4]` Red RAM option, `A[3:0]` BW RAM option: `0000` normal, `0100` bypass as 0, `1000` inverse |
-| `0x22` | **Display Update Control 2** | See below — **DKE documents only three values** |
-| `0x24` | Write RAM (BW) | **White pixel = 1, black pixel = 0** |
-| `0x26` | Write RAM (RED) | RED = 1; white/black = 0 |
-| `0x2C` | Write VCOM register | `A[7:0] = 50h` |
-| `0x2D` | OTP Register Read | 11 bytes: `A`–`B` VCOM information, `C`–`G` display mode, `H`–`K` waveform version |
-| `0x2F` | Status Bit Read | `[5]` HV-ready flag (0 = ready), `[4]` VCI-detection flag, `[2]` busy flag, `[1:0]` chip ID [POR `01`]. **`[5]`/`[4]` are invalid after reset until commands `0x14`/`0x15` are issued** |
-| `0x32` | Write LUT | LUT register from the MCU interface |
-
-`0x22` values, as DKE documents them **[MAN]** p. 18:
-
-| Setting | Sequence | Value |
-|---|---|---|
-| **LUT from MCU** | Enable clock → enable analog → **pattern display** → disable analog → disable OSC | **`C7`** |
-| **LUT from OTP** (external temperature sensor operation) | Enable analog → **load LUT** | **`90`** |
-| | Enable analog → **pattern display** → disable analog → disable OSC | **`47`** |
-
-> ⚠ **The values M5Stack actually uses are in neither table.** The OTP demo writes `0x22` = **`0xF8`** (partial refresh), **`0x14`** (partial follow-up), **`0xFF`** (mono full refresh) and **`0xD7`** (four-grey full refresh) **[SRC]** `EDP_OTP_LUT_demo.cpp:264-266, 276-279, 319-321, 370-375`. DKE's reference program at **[MAN]** p. 24 uses **`0xF7`**. The SSD1677 datasheet enumerates twelve values (`80 01 C0 03 91 99 B1 B9 C7 CF F7 FF`) **[CTL]** §7, of which only `FF` matches M5Stack's set. §8-C5.
-
----
-
-## 7. Operation
-
-### 7.1 LUT-from-OTP operation flow
-
-**[MAN]** p. 23, §10.1, transcribed from the flowchart:
-
-```
-Power On (Apply VCI)
-        ↓
-Reset the EPD driver IC
-        ↓
-Turn on the oscillator clock and DC/DC regulator to generate the drive voltage
-        ↓
-Define the display size, RAM address, border
-        ↓
-Load LUT from OTP
-        ↓
-Load image data and update
-        ↓
-   ┌────┴────┐
-Power Off   Enter into deep sleep
-   │             │
-   └→ Power On   └→ Reset the EPD driver IC
-```
-
-Two exits are drawn, and they re-enter at different points: **power-off returns to "Power On"**, **deep sleep returns to "Reset the EPD driver IC"**. That matches the controller's rule that leaving deep sleep requires a hardware reset **[CTL]** §7 (`0x10` remark).
-
-### 7.2 OTP operation reference program code
-
-**[MAN]** p. 24, §10.2, transcribed in full. This is DKE's own known-good sequence and is the reference against which M5Stack's driver should be judged.
-
-| Action | Value / data | Comment |
-|---|---|---|
-| **POWER ON** | 3 V | |
-| delay | 10 ms | |
-| **PIN CONFIG** | | |
-| `RES#` | low | Hardware reset |
-| delay | **200 µs** | |
-| `RES#` | high | |
-| delay | **200 µs** | |
-| Read busy pin | | Wait for busy low |
-| Command `0x12` | | Software reset |
-| Read busy pin | | Wait for busy low |
-| Command `0x0C` | `AE C7 C3 C0 80` | Booster Soft-start Control |
-| Command `0x01` | `DF 01 02` | Set display size and driver output control |
-| Command `0x11` | **`01`** | RAM data entry mode |
-| Command `0x44` | `00 00 1F 03` | Set RAM X address |
-| Command `0x45` | `DF 01 00 00` | Set RAM Y address |
-| Command `0x3C` | `01` | Set border |
-| Command `0x18` | `80` | *(internal temperature sensor)* |
-| **LOAD IMAGE AND UPDATE** | | |
-| Command `0x4E` | `00 00` | Set RAM X address counter |
-| Command `0x4F` | `DF 01` | Set RAM Y address counter |
-| Command `0x24` | **48000 bytes** | Load BW image (800/8 × 480) |
-| Command `0x22` | **`F7`** | Image update |
-| Command `0x20` | | |
-| Read busy pin | | Wait for busy low |
-| Command `0x10` | **`01`** | Enter deep sleep mode |
-| **POWER OFF** | | |
-
-Decoding the geometry parameters against the controller **[CTL]** §7, §8.1, §8.3–8.5 — `inferred`, arithmetic shown so it can be checked:
-
-- `0x01` `{DF, 01, 02}` ⇒ `A[9:0] = 0x1DF = 479`; MUX gate lines = `A + 1` = **480 gate lines**. `B[2:0] = 010` ⇒ `SM = 1`, i.e. the interlaced scan order `G0, G2, G4 … G678, G1, G3 …`.
-- `0x44` `{00, 00, 1F, 03}` ⇒ `XSA = 0x000`, `XEA = 0x31F = 799` ⇒ **800 source columns**.
-- `0x45` `{DF, 01, 00, 00}` ⇒ `YSA = 0x1DF = 479`, `YEA = 0x000` ⇒ **480 rows, counted downward**.
-- `0x11 = 0x01` ⇒ Y decrement, X increment; `AM = 0` ⇒ counter advances in X.
-- 48 000 bytes = 800 × 480 / 8. ✅ consistent.
-
-So **the panel is 800 source × 480 gate.** That contradicts the mechanical drawing on the same document's page 6 — §8-C3.
-
-### 7.3 What M5Stack's OTP demo does differently
-
-`M5PaperMono-OTP-Demo` follows DKE's sequence closely, which is itself evidence the demo was derived from this manual **[SRC]** `components/EDP_OTP_LUT_demo/src/EDP_OTP_LUT_demo.cpp:206-224`:
-
-| Step | DKE reference **[MAN]** p. 24 | M5Stack OTP demo **[SRC]** | Same? |
-|---|---|---|---|
-| `0x12` software reset | ✅ | `EDP_OTP_LUT_demo.cpp:206` | ✅ |
-| `0x0C` booster soft-start | `AE C7 C3 C0 80` | `{0xAE,0xC7,0xC3,0xC0,0x80}` at `:221`, `:336` | ✅ **byte-identical** |
-| `0x01` driver output | `DF 01 02` | `{0xDF,0x01,0x02}` at `:222`, `:337` | ✅ **byte-identical** |
-| `0x18` temperature sensor | `80` (internal) | `{0x80}` at `:220`, `:356` | ✅ |
-| `0x3C` border | `01` | `{0x01}` at `:223`, `:355`; **`0x80` (float) for partial refresh** at `:251` | ✅ + extension |
-| `0x11` data entry | `01` | **`0x03`** for mono at `:162`; **`0x02`** for four-grey at `:340` | ❌ **differs** |
-| `0x21` RAM display mode | *(absent)* | `{0x00}` at `:224`, and again before mono refresh at `:319` | ➕ M5Stack adds |
-| `0x1A` temperature override | *(absent)* | **`{0x5A}` = 90** in four-grey mode at `:357` | ➕ M5Stack adds |
-| `0x22` update value | **`F7`** | `0xFF` mono / `0xD7` four-grey / `0xF8`, `0x14` partial | ❌ **differs** |
-| `0x10` deep sleep | `01` | `{0x01}` at `:236` — **after every refresh** | ✅ |
-| RAM pre-clear `0x46`/`0x47` | *(absent)* | *(absent)* | both omit what **[CTL]** §9.1 prescribes |
-
-Register `0x1A = 0x5A` (decimal 90) in the four-grey path is the interesting addition: the demo's own comment calls it "Gray-mode temperature value", i.e. it **forces a temperature reading** so that the controller's OTP LUT search selects the greyscale waveform bank rather than whichever bank the real die temperature would pick **[SRC]** `EDP_OTP_LUT_demo.cpp:357`. `inferred` — the mechanism follows from the controller's documented LUT-search rule ("last match wins" over 34 temperature ranges, **[CTL]** §6.9) but was not verified against DKE's OTP contents, which are not published.
-
-Other demo details **[SRC]**: SPI2, mode 0, half-duplex, 4092-byte chunks, 20 MHz; packing MSB-first, 100 bytes per row × 480 rows; in mono RAM **1 = white, 0 = black** (matching `0x24`'s definition); four-grey encoding `white = 00, light = 10, dark = 01, black = 11` across the (`0x24`, `0x26`) plane pair; three frame buffers of 48 000 bytes allocated in PSRAM.
-
-### 7.4 Typical application circuit
-
-**[MAN]** p. 22, §9. The module needs an external boost network — the SSD1677's on-chip regulator drives an external FET:
-
-| Part | Value | Reference part / requirement |
-|---|---|---|
-| `C4`, `C6` | 1 µF | 0603, X5R/X7R, 6 V |
-| `C1 C2 C3 C5 C7 C8` | 4.7 µF | 0805, X5R/X7R, **25 V** |
-| `C9` | 1 µF | 0805, X7R, 25 V |
-| `R1` | **2.2 Ω** | 0805, 1 % — the `RESE` current-sense resistor |
-| `D1 D2 D3` | Schottky | **MBR0530**: V<sub>R</sub> ≥ 30 V, I<sub>O</sub> ≥ 500 mA, V<sub>F</sub> ≤ 430 mV |
-| `Q1` | NMOS | **Si1304BDL / NX3008NBK**: BV<sub>DSS</sub> ≥ 30 V, V<sub>GS(th)</sub> 0.9 V typ / 1.3 V max, R<sub>DS(on)</sub> ≤ 2.1 Ω @ V<sub>GS</sub> = 2.5 V |
-| `L1` | **47 µH** | CDRH2D18 / LDNP-470NC |
-
-`GDR` drives `Q1`'s gate, `RESE` senses the current through `R1`, and `D1`–`D3` with `C1`–`C3` form the charge pump that produces `VGH`/`VGL`. **The 25 V capacitor rating is not optional** — `VGH` reaches 20 V.
-
-### 7.5 Reliability test conditions
-
-**[MAN]** p. 25, §11. Useful as an environmental envelope even though these are DKE's qualification tests, not user ratings.
-
-| # | Test | Condition |
-|---|---|---|
-| 1 | Low-temperature operation | **0 °C for 240 h** |
-| 2 | High-temperature high-humidity storage | 60 °C / 80 %RH for 240 h |
-| 3 | Thermal shock | 1 cycle: −25 °C / 30 min ↔ 60 °C / 30 min, **100 cycles** |
-| 4 | Low-humidity storage | 60 °C / 35 %RH for 240 h |
-| 5 | High-temperature high-humidity operation | 40 °C / 80 %RH for 240 h |
-| 6 | ESD gun | Air ±4 kV; contact ±2 kV (HBM 100 pF / 1.5 kΩ); contact ±200 V (MM 200 pF / 0 Ω) — **naked EPD display, including IC and FPC area** |
-| 7 | Vibration | 10–500 Hz, X/Y/Z, 1 h per direction |
-| 8 | Drop | Height by object weight: ≤ 20 kg → 1000 mm; ≤ 50 kg → 500 mm; ≤ 100 kg → 250 mm |
-
-Notes: "Stay white pattern for storage and non-operation test"; "Operation is black → white pattern, the interval is **150 s**."
-
-That 150-second interval is worth noting — DKE's own endurance testing refreshes **once every 2.5 minutes**, which says something about the duty cycle the panel is designed for.
-
----
-
-## 8. Conflicts and caveats
-
-These are recorded, not resolved. Where a least-risky implementation path exists it is stated.
-
-### C1 — Model number: `DEPG0397BBS770F3` vs `DEPG0397BBS770F3HP-XM`
-
-| Source | String |
-|---|---|
-| Manual cover **[MAN]** p. 1 | "Model NO. : **`DEPG0397BBS770F3`**" |
-| Mechanical drawing title block **[MAN]** p. 6 | `PROJECT: DEPG0397BBS770F3` |
-| `M5PaperMono-OTP-Demo/README.md` **[SRC]** | "**`DEPG0397BBS770F3HP-XM`**" |
-| `docs.m5stack.com` product pages **[DOC]** | *no panel part number at all* — only "3.97-inch Touchscreen" in the datasheet list |
-
-**Unresolved.** The M5Stack string is a strict superset of the DKE string, so the likeliest reading is that `HP-XM` is a variant/customisation suffix — `HP` possibly a waveform or OTP option, `XM` a customer code — and that DKE supplied a customer-specific OTP under a base-model manual. That is a hypothesis, **not a finding**: no DKE document in hand mentions any suffix, and no part-number decoder for the `DEPGxxxx` family was located.
-
-**Practical consequence.** The retained manual may describe a *base* model whose OTP contents differ from the fitted part's. §8-C2 is exactly the kind of divergence that would produce. **Least-risky path:** treat the manual's optical and electrical tables as indicative, read the fitted panel's actual OTP with command `0x2D` (returns VCOM information, display mode and a 4-byte **waveform version**) before relying on any waveform behaviour, and check the `MODEL NO.`/`BATCH NO.` fields silkscreened on the module's back **[MAN]** p. 6.
-
-### C2 — Greyscale: `2Grey Level` vs 4-level greyscale
-
-| Source | Claim |
-|---|---|
-| Manual optical table **[MAN]** p. 5 | Row `GN` — **`2Grey Level`** (all min/typ/max cells empty) |
-| Manual overview **[MAN]** p. 4 | "capable to display image at **1-bit white and black** full display capabilities" |
-| M5Stack product pages **[DOC]** | "3.97" **4-level grayscale** monochrome e-paper, 480×800" — on both the PaperMono and PaperMono-Lite spec tables |
-| M5Stack OTP demo **[SRC]** | Implements a **four-grey mode** using the OTP waveform: two RAM planes, `white = 00, light = 10, dark = 01, black = 11`, `0x22 = 0xD7`, `0x1A = 0x5A` (`EDP_OTP_LUT_demo.cpp:139-140, 336-375`) |
-| M5GFX **[SRC]** | Ships a `Panel_SSD1677_4Gray` class with four-grey LUTs |
-
-**Unresolved.** Three readings are each plausible and the evidence does not choose between them:
-
-1. **The manual is stale or describes a different OTP.** The `HP-XM` suffix (C1) would be the mechanism.
-2. **`GN` documents the *guaranteed optically characterised* levels**, not the achievable ones. The row has no min/typ/max values, only a label — consistent with "we characterise black and white, we do not characterise intermediate levels". Under this reading four-grey works but its L* values, ghosting and life are unspecified.
-3. **Four-grey is a controller capability being used beyond the module's specification.** The SSD1677 has two RAM planes and a `DISPLAY Mode 2` **[CTL]** §7 (`0x22`); driving them does not require the module vendor's blessing.
-
-**Least-risky path.** Reading 2 is the one that costs nothing to assume: use four-grey, but **do not expect the p. 5 optical figures to hold for the intermediate levels**, and treat DKE's electrical note 3 (§5.2 — figures guaranteed only under DKE's waveform) as applying with extra force. Note also that the vendor's four-grey path *is* the OTP path, so it is at least using DKE's own waveform data rather than a third-party LUT.
-
-### C3 — The mechanical drawing has gate and source swapped
-
-| Source | Claim |
-|---|---|
-| Mechanical drawing note 3 **[MAN]** p. 6 | `RESOLUTION: 800gate X 480source` |
-| Controller configuration, DKE's own reference code **[MAN]** p. 24 | `0x01` `{DF,01,02}` ⇒ **480 gate lines**; `0x44` ⇒ `XEA = 799` ⇒ **800 source columns** |
-| SSD1677 hardware maximum **[CTL]** §1, §5 | **960 source outputs, 680 gate outputs** |
-| M5Stack drivers **[SRC]** | `M5GFX.cpp:2126-2130` sets `panel_width = 800, panel_height = 480, offset_rotation = 3`; the OTP demo works natively in 800 × 480 |
-
-**The drawing is wrong, and provably so:** 800 gate lines exceed the SSD1677's 680 gate outputs. The panel is **800 source × 480 gate**, and DKE's own reference program on p. 24 configures it that way. Recorded because the erroneous string is on a page a hardware engineer is likely to read in isolation.
-
-### C4 — M5GFX exceeds the documented SPI write clock by 2×
-
-| Source | Clock |
-|---|---|
-| Module manual **[MAN]** p. 16 | `fSCL` write mode **max 20 MHz** |
-| SSD1677 datasheet **[CTL]** §12.1 | `fSCL` write mode **max 20 MHz** — same figure, independently stated |
-| M5Stack OTP demo **[SRC]** `EDP_SPI.cpp:33` | **20 MHz** — at spec |
-| M5GFX **[SRC]** `M5GFX.cpp:2114` | **40 MHz** — `freq_write = 40000000` |
-
-Both primary documents agree on 20 MHz; M5GFX runs at double it. M5Stack's docs specify neither. This is **not** an interpretation conflict — it is a driver operating outside a specification that two independent vendor documents state identically.
-
-Whether it misbehaves in practice is `not-tested` here; SPI over a short FPC often tolerates overclocking. But it is a concrete, checkable mechanism behind M5Stack's own warning that "the e-paper driver waveforms for PaperMono in the M5GFX library are currently unstable" **[DOC]**, and it is the first thing to change when debugging refresh artefacts.
-
-### C5 — Nobody's `0x22` values match anybody's table
-
-| Source | `0x22` values documented or used |
-|---|---|
-| SSD1677 datasheet **[CTL]** §7 | `80 01 C0 03 91 99 B1 B9 C7 CF F7 FF` |
-| DKE manual **[MAN]** p. 18 | `C7` (LUT from MCU), `90` (load LUT from OTP), `47` (pattern display) |
-| DKE reference program **[MAN]** p. 24 | `F7` |
-| M5Stack OTP demo **[SRC]** | `FF` (mono full), `D7` (four-grey full), `F8` (partial), `14` (partial follow-up) |
-
-Only `C7`, `F7` and `FF` are common to any two lists. `90`, `47`, `D7`, `F8` and `14` appear in exactly one source each.
-
-**The values are evidently a bit-field, not an enumeration** — `C7` = `1100 0111`, `CF` = `C7 | 0x08` (mode 2), `F7` = `C7 | 0x30` (load temperature twice) — and M5GFX carries a comment confirming the field is decomposable: "0x07 becomes 0xC7 when the analog section is off: Mode 1 refresh, followed by analog and oscillator power-down" **[SRC]** `M5GFX develop:src/lgfx/v1/panel/Panel_SSD1677.cpp` in `_refresh_mode1_text`. But **no source in hand publishes the bit definitions**, so `0xD7`, `0xF8` and `0x14` cannot be decoded with confidence. `inferred`, and deliberately left there.
-
-**Least-risky path:** copy the values from the vendor path you have chosen (DKE's `F7`, or M5Stack's OTP demo) rather than composing your own.
-
-### C6 — Deep-sleep parameter `0x01` is not a documented value
-
-Both DKE's reference program **[MAN]** p. 24 and M5Stack's demo **[SRC]** `EDP_OTP_LUT_demo.cpp:236` write `0x10` with data **`0x01`**. Both the module manual **[MAN]** p. 17 and the controller datasheet **[CTL]** §7 define only `A[1:0] = 00` (normal) and **`11`** (enter deep sleep) — i.e. `0x03`.
-
-Two independent vendors using `0x01` against their own documentation is more likely to mean the parameter is decoded loosely (any non-zero, or bit 0 alone) than that both made the same typo, but that is **`inferred`**. Recorded because a reader who "corrects" `0x01` to `0x03` is departing from the only two known-working sequences.
-
-### C7 — Resolution is quoted both ways round
-
-Every `docs.m5stack.com` page and the SSD1677 configuration say **480 × 800**; both store product titles *and* both URL handles say **800 × 480** **[DOC]**. The manual says `480(H) × 800(V)` **[MAN]** p. 5 while its own reference code drives 800 columns × 480 rows **[MAN]** p. 24.
-
-Not a contradiction — portrait-native panel, landscape-native RAM, marketing picks whichever reads better — but anyone writing a raw driver from the "480 × 800" figure **will get the axes transposed**. M5GFX resolves it with `offset_rotation = 3` **[SRC]**.
-
-### C8 — Other gaps
-
-- **No maximum refresh count / endurance rating** anywhere in the manual. The "5 years" life row is a storage-condition statement (§3.2).
-- **No viewing-angle number** despite "ultra wide viewing angle" in the feature list.
-- **OTP contents are not published.** How many of the 34 waveform sets and temperature ranges DKE programmed, and over what temperature span, is unknown — and per **[CTL]** §6.9, "display will not be updated if no suitable temperature range matches the sensed temperature." Given the module's 0–50 °C operating rating (§5.1), behaviour below 0 °C is undefined in a specific and unpleasant way.
-- **DC balance.** M5Stack warns that when supplying custom waveforms you must "pay attention to DC balance; otherwise, **irreversible damage may be caused to the panel**" **[DOC]**. DKE's manual does not restate this, because its recommended path is the factory OTP waveform where the question does not arise. It is the strongest argument for the OTP path over M5GFX's uploaded LUTs.
-
----
-
-## 9. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — FPC connector `J5`, sheet 4
-
-The panel connects through a **24-pin FPC** to `J5`. The board provides the boost network of §7.4 as discrete parts around the connector, and routes the four SPI signals plus BUSY straight to the ESP32-S3 — but **not** reset or power, which come from the [M5IOE1](../../m5stack/m5ioe1/README.md) expander instead.
-
-| `J5` pin | Panel signal | PaperMono net | Goes to | Evidence |
-|---:|---|---|---|---|
-| 2 | `GDR` | — | Gate of the boost NMOS | **[SCH]** `J5`.2 |
-| 3 | `RESE` | — | Current-sense node | **[SCH]** `J5`.3 |
-| 9 | `BUSY_N` | `G18_EINK_BUSY` | **ESP32-S3 GPIO18** | **[SCH]** `J5`.9; **[SRC]** `EDP_SPI.cpp:30`, `M5GFX.cpp:2125` |
-| 10 | `RST_N` | `PYB_EINK_RST` | **M5IOE1 `IO5`** — *not* an ESP32 pin | **[SCH]** `J5`.10; **[SRC]** `EDP_SPI.cpp:38`, and `M5GFX.cpp:2124` sets `cfg.pin_rst = GPIO_NUM_NC` |
-| 11 | `DC` | `G17_EINK_DC` | **ESP32-S3 GPIO17** | **[SCH]** `J5`.11; **[SRC]** `EDP_SPI.cpp:29`, `M5GFX.cpp:2109` |
-| 12 | `CSB` | `G16_EINK_CS` | **ESP32-S3 GPIO16** | **[SCH]** `J5`.12; **[SRC]** `EDP_SPI.cpp:28`, `M5GFX.cpp:2085, 2123` |
-| 13 | `SCL` | `G15_SPI2_CLK` | **ESP32-S3 GPIO15** | **[SCH]** `J5`.13; **[SRC]** `EDP_SPI.cpp:27`, `M5GFX.cpp:2108` |
-| 14 | `SDA` | `G14_SPI2_MOSI` | **ESP32-S3 GPIO14** | **[SCH]** `J5`.14; **[SRC]** `EDP_SPI.cpp:26`, `M5GFX.cpp:2106` |
-| 15 | `VDDIO` | `EPD_3V3_L3B` | Rail gated by **M5IOE1 `IO3`** | **[SCH]** `J5`.15; **[SRC]** `EDP_SPI.cpp:37` |
-| 17–24 | `GND`, `VDDD`, `VSH`, `VGH`, `VSL`, `VGL`, `VCOM` | — | Local decoupling: `C77`–`C84`, values **1 µF/25 V** and **4.7 µF/25 V** as the manual specifies | **[SCH]** `J5`.17–.24 |
-
-Sheet 4 also shows the nets `PREVGH` and `PREVGL` near `J5`.21–.23 **[SCH]**, matching DKE's own block diagram where the driver PCBA's DC/DC circuit feeds `PREVGH & PREVGL` to the panel **[MAN]** p. 21.
-
-Board-level consequences worth stating in this record because they are properties of *the panel's integration*, not of the panel:
-
-- **Reset and power both live behind the I²C expander.** You cannot reset or power-cycle the display without a working I²C bus and a working M5IOE1. `EDP_SPI.cpp`'s `hardware_reset()` does exactly this: enable `IOE_EPD_ENABLE` (raw pin `2` = `IO3`), then pulse `IOE_EPD_RESET` (raw `4` = `IO5`) low for 10 ms and high for 10 ms **[SRC]** `EDP_SPI.cpp:36-38` and the surrounding function. Note the **10 ms** pulses versus DKE's **200 µs** (§7.2) — M5Stack is generous, which is the safe direction.
-- **The panel is driven landscape and rotated in software** — `offset_rotation = 3` **[SRC]** `M5GFX.cpp:2126-2130`. See §8-C7.
-- **PSRAM is a hard requirement.** M5GFX aborts display init with `"M5PaperMono need OPI-PSRAM enabled"` if `CONFIG_SPIRAM_MODE_OCT` is absent **[SRC]** `M5GFX.cpp:2072-2081`; the board still enumerates but the screen stays dark. The OTP demo allocates 3 × 48 000 bytes in PSRAM **[SRC]** `EDP_OTP_LUT_demo.cpp:96`.
-- **A frontlight is added by the board, not the module.** The panel is pure-reflective (§2); PaperMono's frontlight is a separate 15 V LED string (`BL_15V_L3B`, `EINK_BL`) driven by PWM from the [M5PM1](../../m5stack/m5pm1/README.md) `IO3` **[SCH]** sheet 1, `U7`.13.
-- **M5Stack's own refresh timings should not be treated as characteristic of this panel.** The published figures (`epd_quality` 4.71 s, `epd_text` 0.45 s, `epd_fast` 0.34 s, `epd_fastest` 0.07 s **[DOC]**) are M5GFX LUT timings from an unnamed build; both `lut_quality` and `lut_text` were replaced on M5GFX `develop`, and the factory firmware pins an older commit than either branch head **[SRC]**. DKE's own figure for a full update is **4 s** at 23 °C (§5.2).
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md)
-
-**Same panel, same connector, same wiring.** The Lite differs from the PaperMono only in dropping NFC and LoRa; both product pages carry an identical display specification row and both link the same "3.97-inch Touchscreen" datasheet **[DOC]**. The Lite's schematic is published as a 4-sheet `PRJ` PDF rather than a 6-sheet `SCH`, so its `J5` wiring is **not** independently confirmed here.
-
----
-
-## 10. Related components
-
-- [**Solomon Systech SSD1677**](../../solomon-systech/ssd1677/README.md) — the driver IC bonded to this panel. Command-level detail, OTP mechanism, LUT search and the DC-balance hazard live there
-- [**M5Stack M5IOE1**](../../m5stack/m5ioe1/README.md) — supplies this panel's **reset** (`IO5`) and **3V3 rail** (`IO3`)
-- [**M5Stack M5PM1**](../../m5stack/m5pm1/README.md) — drives the board's frontlight, which the panel itself does not have
-- [Vendor sourcing guides index](../../../vendors/README.md) — `vendors/dke/` exists but carries no sourcing guide yet. This manual was obtained only as an M5Stack product-page attachment, not from DKE
-
----
-
-## 11. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/depg0397bbs770f3-epd-module-user-manual.pdf` | 8 666 208 | `6b65f56d5d549a132e5c807eef329fb3e997feab04ac06e8a107f01591618130` | **DKE EPD Module User Manual**, "Specification for 3.97 inch EPD", model `DEPG0397BBS770F3`, **30 pp.** PDF 1.4, A4. Producer **`iLovePDF`**, ModDate **2026-08-21** |
-
-**⚠ No text layer.** All glyphs are vector outlines; `pdftotext` returns empty output for every page. Transcription was done from 140 dpi PNG renders (§Evidence labelling). The `iLovePDF` producer string and the 2026-08-21 modification date — the same day the PaperMono store listing went live — indicate the file was **re-processed before publication**, which is the most likely explanation for the lost text layer. There is no `Author`, `Title` or `Creator` metadata at all; the original authoring tool is unrecoverable from the file.
-
-The manual is **undated on its cover** and carries **no revision table**. The only internal date is on the embedded mechanical drawing: `REV. A0`, `FIRST ISSUE`, **2024-09-29**.
-
-**Licence.** DKE Holding Company Limited copyright, no licence statement, no confidentiality footer. Mirrored by M5Stack with no stated terms. Redistribution status **`unknown`**; disposition `repository`.
-
-**Only one acquisition URL is known.** The document was located solely as an attachment on M5Stack's PaperMono product page, under the generic label "3.97-inch Touchscreen". No DKE-hosted copy was found. That single-source status is recorded here deliberately rather than left as a silent gap.
-
----
-
-## 12. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | EPD Module User Manual — `DEPG0397BBS770F3` | **DKE Holding Company Limited**, mirrored by M5Stack | primary (via authorized mirror) | module specification | `artifacts/depg0397bbs770f3-epd-module-user-manual.pdf`; upstream `static-cdn.m5stack.com/resource/docs/products/core/PaperMono/…` (linked as "3.97-inch Touchscreen") | 2026-09-01 | undated cover; drawing **REV A0, 2024-09-29**; file ModDate 2026-08-21 | §1–§8 |
-| S-2 | SSD1677 datasheet | Solomon Systech, mirrored by M5Stack | authorized mirror | controller datasheet | [`../../solomon-systech/ssd1677/artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf`](../../solomon-systech/ssd1677/README.md) | 2026-09-01 | **Rev 1.0, Nov 2018**, "Advance Information" | §4.1, §5.1, §6, §7.2, §8-C3/C4/C5/C6 |
-| S-3 | PaperMono schematic | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | **V0.6.2, 2026-05-22**, 6 sheets | §9 wiring (sheet 4, `J5`) |
-| S-4 | `M5PaperMono-OTP-Demo` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-OTP-Demo` @ `c7c02554f89fd06f80d988b805b2a59050c78a46` | 2026-09-01 | 2026-08-20, MIT | §1 model string, §7.3, §8-C1/C5/C6 |
-| S-5 | `M5GFX` | M5Stack | primary | source | `github.com/m5stack/M5GFX`, `master` @ `d91077b9a607b59404e4e4a49f775c792bfae382`; `develop` @ `8d6e8b3e0e9629e0bf0702d263e9263b588b6075` | 2026-09-01 | release 0.2.28 | §8-C4/C5/C7, §9 |
-| S-6 | PaperMono / PaperMono-Lite product pages | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono`, `.../PaperMono-Lite` | 2026-09-01 | undated | §8-C2/C7/C8, §9 |
-| S-7 | PaperMono store listing | M5Stack | primary | retail listing | `shop.m5stack.com/products/m5papermono-with-lora-nfc-800x480-3-97-eink-display` | 2026-09-01 | SKU `C153`, published 2026-08-21 | §8-C7 (the `800x480` handle) |
diff --git a/components/dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf b/components/dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf
deleted file mode 100644
index 2e6beef..0000000
Binary files a/components/dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf and /dev/null differ
diff --git a/components/ebyte/e22-900m22s/README.md b/components/ebyte/e22-900m22s/README.md
index 7796036..a7662d1 100644
--- a/components/ebyte/e22-900m22s/README.md
+++ b/components/ebyte/e22-900m22s/README.md
@@ -1,7 +1,5 @@
 # Ebyte E22-900M22S
 
-> **Common guide:** [`guides/lora`](../../../guides/lora/README.md) — the device-independent LoRa material (the module-independent LoRa material: modulation trade-offs, band plans, SX126x interface pitfalls and RadioLib). This record covers the part; that guide covers the domain.
-
 > LoRa transceiver module: a **Semtech SX1262** plus a power amplifier, LNA, RF switch and matching, in a stamp-hole SMD module. 868/915 MHz, 22 dBm.
 > Research snapshot **2026-08-30**. Fitted as `U23` on the Nicolai Electronics Tanmatsu. **No hardware was available.**
 >
diff --git a/components/ebyte/e22-900m22s/artifacts/WRONG-PART-e810-ttl-01-manual-cdebyte-id1211.pdf b/components/ebyte/e22-900m22s/artifacts/WRONG-PART-e810-ttl-01-manual-cdebyte-id1211.pdf
deleted file mode 120000
index a74de09..0000000
--- a/components/ebyte/e22-900m22s/artifacts/WRONG-PART-e810-ttl-01-manual-cdebyte-id1211.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/ebyte/e22-900m22s/artifacts/WRONG-PART-e810-ttl-01-manual-cdebyte-id1211.pdf
\ No newline at end of file
diff --git a/components/ebyte/e220-400t22s/README.md b/components/ebyte/e220-400t22s/README.md
deleted file mode 100644
index 380c0b5..0000000
--- a/components/ebyte/e220-400t22s/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Ebyte E220 series — `E220-400T22S` and `E220-900T22S`
-
-- **Category:** **UART LoRa modem module** — an LLCC68 radio behind a microcontroller that
-  speaks a serial/AT-style protocol. The host **cannot reach the radio's registers.**
-- **Scope:** this page covers both M5Stack-fitted E220 variants;
-  [`../e220-900t22s/`](../e220-900t22s/README.md) is a pointer to it.
-- **Retrieved:** 2026-09-04
-- **⚠ Not the same as the E22.** This repository also holds
-  [`components/ebyte/e22-900m22s`](../e22-900m22s/README.md), which is **SX1262-based**.
-  Read both before assuming interchangeability — §3.
-
-## 1. Identity
-
-| | `E220-400T22S` | `E220-900T22S (JP)` |
-|---|---|---|
-| Manufacturer | Chengdu Ebyte | Chengdu Ebyte |
-| **Radio chip** | **Semtech LLCC68** | **Semtech LLCC68** |
-| Band | **410.125 – 493.125 MHz** (default 433) | **920.6 – 928.0 MHz** |
-| Max TX | **22 dBm**, software-selectable | **13 dBm** (~20 mW) |
-| RX sensitivity | **−129 dBm** | not published by M5Stack |
-| Host interface | **UART, 115200 default** | UART |
-| Certification | none cited | **Telec `001-P01730`** |
-| Fitted on | [M5Stack Unit LoRaE220-433 (U170-433)](../../../devices/m5stack/unit-lora-e220/README.md) | [M5Stack Unit LoRaE220-920 (U170)](../../../devices/m5stack/unit-lora-e220/README.md) |
-
-Modes, selectable by an **onboard DIP switch** on the M5Stack units: transmission,
-**WOR (Wake-on-Radio) transmit**, WOR receive, sleep. Additional features named by the
-vendor: carrier sensing, communication keys, point-to-point and broadcast addressing.
-
-## 2. What "UART modem" means for firmware — and why it rules out Meshtastic
-
-The E220 is not a transceiver you drive; it is a **link** you configure. The module's own
-MCU owns the LLCC68 and exposes a serial pipe, a configuration register set reachable with
-`AT`-style / `0xC0`-framed commands, mode pins (`M0`/`M1`, wired to the DIP switch on the
-M5Stack units) and an `AUX` busy/ready line.
-
-| You want | Possible with E220? |
-|---|---|
-| Simple point-to-point or broadcast serial link | ✅ — easier than raw LoRa; the DIP switch alone can get a link up |
-| Wake-on-Radio low-power receive | ✅ — a genuine strength |
-| Choosing SF/BW/CR freely | ⚠ only from the module's supported table |
-| Raw packet access, custom PHY, arbitrary sync words | ❌ |
-| **Meshtastic** | ❌ **No.** Meshtastic drives an SX126x/SX127x/LR11xx **over SPI**. There is no upstream variant for any UART LoRa modem, and there cannot be one without a new radio-transport abstraction. `executed-success` on the negative: the full recursive Meshtastic variant tree (2026-09-04) contains no LLCC68 or E220 entry |
-| **LoRaWAN** | ❌ — different product (see [STM32WLE5](../../stmicroelectronics/stm32wle5/README.md)) |
-
-**This is the single most important fact in this record**, because M5Stack sells the E220
-units as "LoRa" alongside genuinely SPI-attached SX1262 products, and buyers reasonably
-assume they are equivalent. They are not.
-
-## 3. E220 vs E22 — do not confuse them
-
-| | **E220** | **E22** |
-|---|---|---|
-| Radio silicon | **LLCC68** | **SX1262** |
-| Host access to the radio | **UART modem only** | E22 variants exist with **SPI** access to the SX1262 |
-| Spreading factors | LLCC68 supports **SF5–SF11** (no SF12) | SX1262 supports SF5–SF12 |
-| Meshtastic-capable | **No** | Depends on the variant — an SPI E22 exposes a real SX1262 |
-| Record here | this page | [`components/ebyte/e22-900m22s`](../e22-900m22s/README.md) |
-
-The **absence of SF12** on LLCC68 is the practical difference that bites: the longest-range,
-lowest-rate LoRa configurations are simply unavailable, and a link configured for SF12 at
-the other end will not be heard.
-
-## 4. Used By
-
-### [M5Stack LoRa Unit (E220)](../../../devices/m5stack/unit-lora-e220/README.md) — U170 and U170-433
-
-Grove **HY2.0-4P** (UART), 5 V supply, SMA-male antenna, onboard DIP switch.
-Attachable to **any** M5Stack host with a Grove port — **including the original
-Cardputer (K132)**, whose only expansion is `PORT.CUSTOM` (G2/G1). That makes the E220 unit
-one of the genuine pre-Cap answers to "LoRa on a Cardputer", with the large caveat in §2.
-
-Libraries: `github.com/m5stack/M5-LoRa-E220` and `M5-LoRa-E220-JP` (both last pushed
-2025-01-16).
-
-## 5. Gaps
-
-- **No Ebyte datasheet retrieved** for either part. Register map, command framing, `AUX`
-  timing and the `M0`/`M1` mode table are unestablished here.
-- M5Stack's documentation slugs for these units were **not resolved**
-  (`/en/unit/lorae220-433`, `/en/unit/Unit-LoRaE220-JP` both 404), so no pin map or DIP
-  table was obtained.
-- The **LLCC68 has no component record** in this repository.
-- No firsthand community report of an E220 unit driven from a Cardputer was found in the
-  217-post Reddit sample.
-
-## 6. Sources
-
-| ID | Title | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|
-| EB-1 | U170-433 store listing JSON | primary | `https://shop.m5stack.com/products/lora-unit-433mhz-with-antenna-e220.json` | 2026-09-04 | `E220-400T22S@LLCC68`, 410–493 MHz, 22 dBm, −129 dBm, UART 115200, four DIP modes |
-| EB-2 | U170 store listing JSON | primary | `https://shop.m5stack.com/products/lora-unit-jp-version-with-antenna-e220.json` | 2026-09-04 | `E220-900T22S (JP) @ Telec (001-P01730)`, LLCC68, 920.6–928.0 MHz, 13 dBm |
-| EB-3 | Meshtastic variant tree | primary | `api.github.com/repos/meshtastic/firmware/git/trees/master?recursive=1` | 2026-09-04 | **Negative result** — no LLCC68/E220 variant exists |
-| EB-4 | `m5stack/M5-LoRa-E220`, `M5-LoRa-E220-JP` | primary | `https://github.com/m5stack/M5-LoRa-E220` | 2026-09-04 | The vendor libraries, last pushed 2025-01-16 |
diff --git a/components/ebyte/e220-900t22s/README.md b/components/ebyte/e220-900t22s/README.md
deleted file mode 100644
index 6e3997a..0000000
--- a/components/ebyte/e220-900t22s/README.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# Ebyte `E220-900T22S` — see the E220 series record
-
-The `E220-900T22S (JP)` variant (920.6–928.0 MHz, LLCC68, 13 dBm, **Telec `001-P01730`**),
-fitted on the [M5Stack LoRa Unit U170](../../../devices/m5stack/unit-lora-e220/README.md),
-is documented together with its 433 MHz sibling in:
-
-## → [`components/ebyte/e220-400t22s/README.md`](../e220-400t22s/README.md)
-
-Kept as a separate directory because the two part numbers are distinct orderable items and
-a future pass may need somewhere to put a `E220-900T22S`-specific datasheet. The shared
-record covers architecture, the E220-vs-E22 distinction, and why neither is a Meshtastic
-path.
diff --git a/components/espressif/esp32-c3/README.md b/components/espressif/esp32-c3/README.md
deleted file mode 100644
index d607dd4..0000000
--- a/components/espressif/esp32-c3/README.md
+++ /dev/null
@@ -1,166 +0,0 @@
-# Espressif ESP32-C3 — RISC-V Wi-Fi + BLE SoC
-
-- **Category:** 32-bit RISC-V microcontroller with 2.4 GHz Wi-Fi and Bluetooth LE 5.
-- **Manufacturer:** Espressif Systems.
-- **Research status:** ⚠ **Family-level identification only.** See §1 — the exact
-  package/variant on the Xteink boards has **never been read**.
-- **Retrieved:** 2026-09-04
-
-The application processor of the **Xteink X3** and **Xteink X4**.
-
-## 1. Identification status — read this before citing a part number
-
-**No exact part number is asserted anywhere in this repository for the Xteink
-boards.** What exists:
-
-| Evidence | Says |
-|---|---|
-| [Imgur X3 teardown](../../../devices/xteink/x3/media.md), image 10 | *"ESP32-C3 main CPU"* — a photograph caption |
-| [`sunwoods/Xteink-X3`](https://github.com/sunwoods/Xteink-X3) BOM | `ESP32-C3` |
-| **X4 factory flash dump**, bootloader header | **chip-id field = 5**, which is the ESP32-C3 |
-| FreeInk SDK | targets `esp32c3` |
-
-Chip-id 5 is a **hard, machine-readable confirmation of the family** and is the
-strongest of the four. But **the family is all it confirms.**
-
-**Why the variant is not inferable.** Both teardowns show a **separate Puya
-128 Mbit flash chip**, so the SoC is one of the variants *without* embedded flash
-(e.g. a bare `ESP32-C3` QFN32) rather than an `ESP32-C3FH4`/`FN4` or a
-`ESP32-C3-MINI-1` module. **That is an inference from a photograph, not a
-reading**, and this record does not promote it. A legible top-marking photograph
-would settle it in seconds.
-
-Per the research method's rule: *"Do not assign a guessed part number."*
-
-## 2. What the family gives you
-
-| Property | Value |
-|---|---|
-| Core | Single **RISC-V RV32IMC**, up to 160 MHz |
-| SRAM | 400 KB |
-| **PSRAM** | **None on these boards.** This is the defining constraint |
-| Radios | Wi-Fi 2.4 GHz b/g/n; **Bluetooth LE 5** |
-| **Bluetooth Classic** | **Not present.** The C3 has no BR/EDR radio |
-| USB | **USB Serial/JTAG** peripheral — flashing and debug over the native port, no bridge IC |
-| ADC | ADC1 channels on GPIO0–GPIO4 |
-
-**The absence of PSRAM is the single most consequential fact** for anyone writing
-firmware for the X3 or X4. It is why CrossPoint abandoned GitHub-release OTA —
-*"it causes out of memory issues on the x3"* — and why the S3-based
-[X4 Pro](../../../devices/xteink/x4-pro/README.md) and
-[X4 Classic](../../../devices/xteink/x4-classic/README.md), with 8 MB PSRAM, can
-do multi-buffer rendering and damage-window partial refresh that the C3 cannot.
-
-## 3. How the Xteink boards use ADC1
-
-Both C3 devices put **four functions on the four ADC1-capable pins**:
-
-| GPIO | ADC1 channel | Xteink role |
-|---:|---|---|
-| 0 | CH0 | Battery voltage sense (÷2 divider) — **X4**; contested on the X3 |
-| 1 | CH1 | **Button ladder group 1** — Back / Confirm / Left / Right |
-| 2 | CH2 | **Button ladder group 2** — Up / Down |
-| 3 | CH3 | Power button (digital, not ADC) |
-
-`analogSetAttenuation(ADC_11db)`. Six buttons on two pins — see
-[`devices/xteink/x4/features/buttons.md`](../../../devices/xteink/x4/features/buttons.md)
-for the three-device calibration data.
-
-## 4. Datasheet
-
-**Not retrieved in this session.** Espressif publishes openly at
-`https://www.espressif.com/sites/default/files/documentation/esp32-c3_datasheet_en.pdf`
-plus a technical reference manual. Retrieval status `not-attempted`; recorded as
-an open acquisition.
-
-**Note the repository's own precedent:** three agents once fetched three ESP32-S3
-datasheets from three portals and got **three different SHA-256 values and three
-different sizes**. If this is fetched later, hash it and name the source in the
-filename.
-
-## 5. Caveats and unsafe assumptions
-
-- **Do not assume the ESP32-S3 pin conventions.** On the C3, GPIO20 and GPIO0 are
-  ordinary pins the Xteink boards use for I²C; on the **S3** those are USB D+ and
-  a boot strap. This is exactly why `XteinkDetect` compiles its C3 I²C fingerprint
-  to a no-op unless a C3 profile is in the build — running it on an S3 would poke
-  USB D+ and a strap pin at boot.
-- **No Bluetooth Classic.** Any project expecting A2DP or SPP is on the wrong SoC.
-- The exact variant is unknown, so **flash-embedded-vs-external assumptions are
-  unsafe** for anyone recompiling bootloaders.
-
----
-
-## Used By
-
-### [Xteink X4](../../../devices/xteink/x4/README.md)
-
-Sole processor. 16 MB external
-[Puya SPI NOR flash](../../unidentified/xteink-x3-x4/spi-nor-flash-128mbit-puya/README.md),
-no PSRAM. Drives one shared SPI bus (SCLK 8 / MOSI 10) for **both** the
-[e-paper controller](../../solomon-systech/ssd1677/README.md) and the microSD
-card; a two-pin ADC button ladder; and a battery MOSFET latch on GPIO13.
-**No I²C peripherals at all** — that absence is what the SDK's runtime probe uses
-to tell an X4 from an X3.
-
-Stock firmware is an **Arduino-framework build on ESP-IDF v4.4.7**, confirmed from
-the dump's `esp_app_desc_t`.
-
-→ [`devices/xteink/x4/pinouts-and-buses.md`](../../../devices/xteink/x4/pinouts-and-buses.md)
-→ [`devices/xteink/x4/factory-firmware.md`](../../../devices/xteink/x4/factory-firmware.md)
-
-### [Xteink X3](../../../devices/xteink/x3/README.md)
-
-Same board family, same flash. Adds a secondary **I²C bus on SDA 20 / SCL 0**
-carrying a [BQ27220 gauge](../../texas-instruments/bq27220/README.md) (0x55),
-a [DS-series RTC](../../unidentified/xteink-x3-x4/rtc-ds-series/README.md) (0x68)
-and a [QMI8658 IMU](../../qst/qmi8658a/README.md) (0x6B). Same two-pin ADC ladder.
-GPIO13 becomes the **SD power rail** rather than a battery latch.
-
-**Note two unresolved dual-assignments** on this device: GPIO0 (`batteryAdc` vs
-I²C SCL) and GPIO20 (`usbDetect` vs I²C SDA). See
-[`devices/xteink/x3/gaps-and-conflicts.md`](../../../devices/xteink/x3/gaps-and-conflicts.md).
-
-→ [`devices/xteink/x3/pinouts-and-buses.md`](../../../devices/xteink/x3/pinouts-and-buses.md)
-
-## See also
-
-[`../esp32-s3r8/README.md`](../esp32-s3r8/README.md) — the SoC of the X4 Pro and
-X4 Classic, and the reason those devices can do things these cannot.
-
----
-
-## Datasheet — retrieved 2026-09-11
-
-The record above gave the URL with retrieval status `not-attempted`. **Fetched,
-validated and retained.**
-
-| Field | Value |
-|---|---|
-| Local path | [`artifacts/esp32-c3-datasheet-en-v2.4.pdf`](artifacts/esp32-c3-datasheet-en-v2.4.pdf) |
-| **SHA-256** | `833fc000b4b3c3d39c496fcbd597fed5806956503ce7390b19cc8ae82f19f968` |
-| **Bytes** | **900,158** |
-| Pages | **76**, A4 |
-| Source URL | <https://www.espressif.com/sites/default/files/documentation/esp32-c3_datasheet_en.pdf> |
-| Source class | **primary** — Espressif's own host |
-| Retrieved | **2026-09-11**, HTTP 200, magic bytes `%PDF` |
-| **Document version** | **Datasheet Version 2.4** (read from the cover) |
-| PDF `CreationDate` | **2026-05-06 04:52:40** |
-| Producer | `xdvipdfmx (20240407)` |
-| Covers | `ESP32-C3`, `ESP32-C3FN4` (**End of life**), `ESP32-C3FH4` |
-| Redistribution status | `unknown` — Espressif datasheets carry no explicit redistribution grant |
-| Disposition | `repository`, **unstaged** |
-
-**Text-layer validated** against the rendered cover: *"ESP32-C3 Series /
-Datasheet Version 2.4 / Ultra-Low-Power SoC with RISC-V Single-Core CPU /
-2.4 GHz Wi-Fi (802.11b/g/n) and Bluetooth® 5 (LE) / QFN32 (5×5 mm) package"*.
-
-**Note the variant coverage.** This document covers the bare `ESP32-C3` and the
-in-package-flash `ESP32-C3FN4`/`FH4`. The Xteink X3 and X4 use an **external**
-16 MB SPI flash, so the in-package-flash variants are **not** what is fitted.
-Neither device's exact Espressif part number or module has been read off a board
-by this repository — the FCC internal photographs of both are now retained
-(see the device records) and have **not** been read at marking level.
-
-**Used by:** [Xteink X3](../../../devices/xteink/x3/README.md) ·
-[Xteink X4](../../../devices/xteink/x4/README.md).
diff --git a/components/espressif/esp32-c3/artifacts/esp32-c3-datasheet-en-v2.4.pdf b/components/espressif/esp32-c3/artifacts/esp32-c3-datasheet-en-v2.4.pdf
deleted file mode 100644
index a4bfc75..0000000
Binary files a/components/espressif/esp32-c3/artifacts/esp32-c3-datasheet-en-v2.4.pdf and /dev/null differ
diff --git a/components/espressif/esp32-p4/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md b/components/espressif/esp32-p4/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
index 86bc0bc..3afcfc6 100644
--- a/components/espressif/esp32-p4/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
+++ b/components/espressif/esp32-p4/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
@@ -3,7 +3,7 @@
 One large Espressif **framework documentation** PDF that used to live in this directory has been moved out of the repository. It was **regenerable from a stable, verified Espressif URL** and is not scarce, unlike the datasheet, technical reference manual, errata and hardware-design guidelines in this directory, **all of which are retained**.
 
 - **Archived:** 2026-08-24
-- **Moved to:** `archive/components/espressif/esp32-p4/artifacts/` (same relative path)
+- **Moved to:** `../hardware-doc-archive/doc/hardware/components/espressif/esp32-p4/artifacts/` (same relative path)
 - **Total reclaimed here:** 13 656 675 bytes (~13.0 MiB)
 
 Nothing was deleted. The knowledge worth keeping was extracted into committed Markdown **before** the file was moved — see [What was extracted](#what-was-extracted-and-where-it-now-lives).
diff --git a/components/espressif/esp32-p4/artifacts/esp-idf-programming-guide-v5.3.2-esp32p4.pdf b/components/espressif/esp32-p4/artifacts/esp-idf-programming-guide-v5.3.2-esp32p4.pdf
deleted file mode 120000
index 75d7843..0000000
--- a/components/espressif/esp32-p4/artifacts/esp-idf-programming-guide-v5.3.2-esp32p4.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-p4/artifacts/esp-idf-programming-guide-v5.3.2-esp32p4.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-s3-wroom-1/acquisition/manifest.json b/components/espressif/esp32-s3-wroom-1/acquisition/manifest.json
deleted file mode 100644
index 7f0baac..0000000
--- a/components/espressif/esp32-s3-wroom-1/acquisition/manifest.json
+++ /dev/null
@@ -1,656 +0,0 @@
-{
- "record": "components/espressif/esp32-s3-wroom-1",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104673",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/Test-Report/Antenna-specification-9104673.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104673",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104673.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/Test-Report/Antenna-specification-9104673.pdf"
-   ],
-   "sha256": "da8da91adaa5b481ccfc927af92e39f785383c3465cb13545d091b3fefa904a8",
-   "bytes": 1996381,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104673",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna specification",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104632",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photo-9104632.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104632",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104632.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photo-9104632.pdf"
-   ],
-   "sha256": "a0104b88a862efd59851ea020519fe700b8501678b4a888bbffdbbcd13186f65",
-   "bytes": 1367037,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104632",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photo",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-5637981",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-photos-5637981.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5637981",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/5637981.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-photos-5637981.pdf"
-   ],
-   "sha256": "b04d392ae5298711cec05f57970745731dcaec0c05016a8ed9c68ad8cff0d848",
-   "bytes": 332733,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-07-21",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "5637981",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External photos",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-6102617",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photos-6102617.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102617",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102617.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photos-6102617.pdf"
-   ],
-   "sha256": "8fe953474e9707bcc8adcbf0ee2eff4a6386283d2c36414dc7786a2d23c70261",
-   "bytes": 1275356,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-08",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "6102617",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104633",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/Internal-Photos/Internal-Photo-9104633.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104633",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104633.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/Internal-Photos/Internal-Photo-9104633.pdf"
-   ],
-   "sha256": "318d8c6c95232515185c1e71389e5f90260094b4548f9e432589ba84f3b2c50a",
-   "bytes": 3636909,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photo.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104633",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photo",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-6102620",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/Internal-Photos/Internal-photos-6102620.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102620",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102620.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/Internal-Photos/Internal-photos-6102620.pdf"
-   ],
-   "sha256": "1f60246b57db617203601cb18284a081bba4a27f13defca80ee7e6a68a64b7c8",
-   "bytes": 338977,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-08",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "6102620",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal photos",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-6102619",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/Label/Label-location-6102619.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102619",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102619.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/Label/Label-location-6102619.pdf"
-   ],
-   "sha256": "68e843105466c1628186304e319636cb9c96081bf2a34bb284d124940c6d627f",
-   "bytes": 30758,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-08",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "6102619",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label location",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-6102618",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/Label/Label-6102618.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102618",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102618.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/Label/Label-6102618.pdf"
-   ],
-   "sha256": "081ac1c0f3292f1bfcce8d8f169a538d04ce0477379cd1f930f0e930c5e6a8c8",
-   "bytes": 44224,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-08",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "6102618",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104630",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/Label/Lable-and-location-9104630.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104630",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104630.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/Label/Lable-and-location-9104630.pdf"
-   ],
-   "sha256": "0a57b90982013049a822a885d9a4e6b67f6d629012ee67cbe7a44e2ce22c8cd9",
-   "bytes": 1437286,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-lable-and-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104630",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Lable and location",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-6102621",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/RF-Exposure-6102621.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102621",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102621.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/RF-Exposure-6102621.pdf"
-   ],
-   "sha256": "b1ae557e1e78bbfa0ff2a20a8077103a8cb6c7c63760db0a63b187806fcf3d40",
-   "bytes": 499298,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-08",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "6102621",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104674",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-A-9104674.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104674",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104674.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-A-9104674.pdf"
-   ],
-   "sha256": "54f4972a02877d9bdeb336f9b2596aa14bdc8506703293845b696b8f4e37a72a",
-   "bytes": 845988,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104674",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "SAR Report A",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104675",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-B-9104675.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104675",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104675.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-B-9104675.pdf"
-   ],
-   "sha256": "62b4f82db50809aa91a1f0e80e878982838cac07880d865a6578d78d0462f942",
-   "bytes": 850218,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104675",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "SAR Report B",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104676",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C1-9104676.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104676",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104676.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C1-9104676.pdf"
-   ],
-   "sha256": "8fbf6c55dc6a02487d8290108deb6471b45aa58d3bfe2b55a855af7256d063c7",
-   "bytes": 5908102,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104676",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "SAR Report C1",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104677",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C2-9104677.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104677",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104677.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C2-9104677.pdf"
-   ],
-   "sha256": "4c6ed64c435d4f04041663f8e5c3de27e9d81d67c4d0ae9e9b904f0edee026dc",
-   "bytes": 3930042,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104677",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "SAR Report C2",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104678",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-D-9104678.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104678",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104678.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-D-9104678.pdf"
-   ],
-   "sha256": "04798068d0a5ee3b4439fc2655b6d0694c8f247864c6139e5fb8215dd32cb12e",
-   "bytes": 3974985,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104678",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "SAR Report D",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104679",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-9104679.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104679",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104679.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-9104679.pdf"
-   ],
-   "sha256": "60f7208dd54ccff8d2af1d93c2e7d706c2259d0f2b9de6563b606057d49ba7a4",
-   "bytes": 1936491,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104679",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "SAR Report",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-6102626",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-manual-6102626.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102626",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102626.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-manual-6102626.pdf"
-   ],
-   "sha256": "f8d1d246c0c849a6d51681f716c959ae554a3597aa73e74767b5734bdbf2a301",
-   "bytes": 886672,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-08",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "6102626",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User manual",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1-9104631",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-Manual-9104631.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104631",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104631.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-Manual-9104631.pdf"
-   ],
-   "sha256": "3e493b8b9ea24f00bca907dbade0be47aa602547df2c80b6ec80f59ded1a0c30",
-   "bytes": 2603588,
-   "destination": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1",
-   "fcc_document_id": "9104631",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2026-02-27",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "SGS-CSTC Standards Technical Services Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 9b91dd5..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,996,381 B (1.90 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,996,381 B (1.90 MiB) |
-| SHA-256 | `da8da91adaa5b481ccfc927af92e39f785383c3465cb13545d091b3fefa904a8` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna specification |
-| FCC document id | 9104673 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/Test-Report/Antenna-specification-9104673.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104673>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104673.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/Test-Report/Antenna-specification-9104673.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/Test-Report/Antenna-specification-9104673.pdf" -o "2AC7Z-ESPS3WROOM1-antenna-specification.pdf"
-echo "da8da91adaa5b481ccfc927af92e39f785383c3465cb13545d091b3fefa904a8  2AC7Z-ESPS3WROOM1-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf.ARCHIVED.md
deleted file mode 100644
index c07b136..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-external-photo.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 1,367,037 B (1.30 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,367,037 B (1.30 MiB) |
-| SHA-256 | `a0104b88a862efd59851ea020519fe700b8501678b4a888bbffdbbcd13186f65` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photo |
-| FCC document id | 9104632 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photo-9104632.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104632>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104632.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photo-9104632.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photo.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photo-9104632.pdf" -o "2AC7Z-ESPS3WROOM1-external-photo.pdf"
-echo "a0104b88a862efd59851ea020519fe700b8501678b4a888bbffdbbcd13186f65  2AC7Z-ESPS3WROOM1-external-photo.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf.ARCHIVED.md
deleted file mode 100644
index 0ae1ab2..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 332,733 B (0.32 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 332,733 B (0.32 MiB) |
-| SHA-256 | `b04d392ae5298711cec05f57970745731dcaec0c05016a8ed9c68ad8cff0d848` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External photos |
-| FCC document id | 5637981 |
-| Upstream publication date | 2022-07-21 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-photos-5637981.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5637981>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/5637981.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-photos-5637981.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-photos-5637981.pdf" -o "2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf"
-echo "b04d392ae5298711cec05f57970745731dcaec0c05016a8ed9c68ad8cff0d848  2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf.ARCHIVED.md
deleted file mode 100644
index f6d49c1..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 1,275,356 B (1.22 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,275,356 B (1.22 MiB) |
-| SHA-256 | `8fe953474e9707bcc8adcbf0ee2eff4a6386283d2c36414dc7786a2d23c70261` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 6102617 |
-| Upstream publication date | 2022-09-08 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photos-6102617.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102617>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102617.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photos-6102617.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/External-Photos/External-Photos-6102617.pdf" -o "2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf"
-echo "8fe953474e9707bcc8adcbf0ee2eff4a6386283d2c36414dc7786a2d23c70261  2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photo.pdf b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photo.pdf
deleted file mode 100644
index ad18950..0000000
Binary files a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photo.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photos.pdf b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photos.pdf
deleted file mode 100644
index cd40f10..0000000
Binary files a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-internal-photos.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label-location.pdf b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label-location.pdf
deleted file mode 100644
index fa3fd56..0000000
Binary files a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label-location.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label.pdf b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label.pdf
deleted file mode 100644
index b5ac7a4..0000000
Binary files a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-label.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-lable-and-location.pdf b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-lable-and-location.pdf
deleted file mode 100644
index 40e3c25..0000000
Binary files a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-lable-and-location.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf.ARCHIVED.md
deleted file mode 100644
index b3eb427..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-rf-exposure.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 499,298 B (0.48 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 499,298 B (0.48 MiB) |
-| SHA-256 | `b1ae557e1e78bbfa0ff2a20a8077103a8cb6c7c63760db0a63b187806fcf3d40` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure |
-| FCC document id | 6102621 |
-| Upstream publication date | 2022-09-08 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/RF-Exposure-6102621.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102621>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102621.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/RF-Exposure-6102621.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-rf-exposure.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/RF-Exposure-6102621.pdf" -o "2AC7Z-ESPS3WROOM1-rf-exposure.pdf"
-echo "b1ae557e1e78bbfa0ff2a20a8077103a8cb6c7c63760db0a63b187806fcf3d40  2AC7Z-ESPS3WROOM1-rf-exposure.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf.ARCHIVED.md
deleted file mode 100644
index e916f6a..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-sar-report-a.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 845,988 B (0.81 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 845,988 B (0.81 MiB) |
-| SHA-256 | `54f4972a02877d9bdeb336f9b2596aa14bdc8506703293845b696b8f4e37a72a` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | SAR Report A |
-| FCC document id | 9104674 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-A-9104674.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104674>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104674.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-A-9104674.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-a.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-A-9104674.pdf" -o "2AC7Z-ESPS3WROOM1-sar-report-a.pdf"
-echo "54f4972a02877d9bdeb336f9b2596aa14bdc8506703293845b696b8f4e37a72a  2AC7Z-ESPS3WROOM1-sar-report-a.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf.ARCHIVED.md
deleted file mode 100644
index e341e37..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-sar-report-b.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 850,218 B (0.81 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 850,218 B (0.81 MiB) |
-| SHA-256 | `62b4f82db50809aa91a1f0e80e878982838cac07880d865a6578d78d0462f942` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | SAR Report B |
-| FCC document id | 9104675 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-B-9104675.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104675>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104675.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-B-9104675.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-b.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-B-9104675.pdf" -o "2AC7Z-ESPS3WROOM1-sar-report-b.pdf"
-echo "62b4f82db50809aa91a1f0e80e878982838cac07880d865a6578d78d0462f942  2AC7Z-ESPS3WROOM1-sar-report-b.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf.ARCHIVED.md
deleted file mode 100644
index c1994e9..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-sar-report-c1.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 5,908,102 B (5.63 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 5,908,102 B (5.63 MiB) |
-| SHA-256 | `8fbf6c55dc6a02487d8290108deb6471b45aa58d3bfe2b55a855af7256d063c7` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | SAR Report C1 |
-| FCC document id | 9104676 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C1-9104676.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104676>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104676.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C1-9104676.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c1.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C1-9104676.pdf" -o "2AC7Z-ESPS3WROOM1-sar-report-c1.pdf"
-echo "8fbf6c55dc6a02487d8290108deb6471b45aa58d3bfe2b55a855af7256d063c7  2AC7Z-ESPS3WROOM1-sar-report-c1.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf.ARCHIVED.md
deleted file mode 100644
index aa3b03e..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-sar-report-c2.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 3,930,042 B (3.75 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 3,930,042 B (3.75 MiB) |
-| SHA-256 | `4c6ed64c435d4f04041663f8e5c3de27e9d81d67c4d0ae9e9b904f0edee026dc` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | SAR Report C2 |
-| FCC document id | 9104677 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C2-9104677.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104677>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104677.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C2-9104677.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-c2.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-C2-9104677.pdf" -o "2AC7Z-ESPS3WROOM1-sar-report-c2.pdf"
-echo "4c6ed64c435d4f04041663f8e5c3de27e9d81d67c4d0ae9e9b904f0edee026dc  2AC7Z-ESPS3WROOM1-sar-report-c2.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf.ARCHIVED.md
deleted file mode 100644
index 4ebde8d..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-sar-report-d.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 3,974,985 B (3.79 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 3,974,985 B (3.79 MiB) |
-| SHA-256 | `04798068d0a5ee3b4439fc2655b6d0694c8f247864c6139e5fb8215dd32cb12e` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | SAR Report D |
-| FCC document id | 9104678 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-D-9104678.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104678>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104678.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-D-9104678.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report-d.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-D-9104678.pdf" -o "2AC7Z-ESPS3WROOM1-sar-report-d.pdf"
-echo "04798068d0a5ee3b4439fc2655b6d0694c8f247864c6139e5fb8215dd32cb12e  2AC7Z-ESPS3WROOM1-sar-report-d.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf.ARCHIVED.md
deleted file mode 100644
index 1024fc1..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-sar-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 1,936,491 B (1.85 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,936,491 B (1.85 MiB) |
-| SHA-256 | `60f7208dd54ccff8d2af1d93c2e7d706c2259d0f2b9de6563b606057d49ba7a4` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | SAR Report |
-| FCC document id | 9104679 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-9104679.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104679>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104679.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-9104679.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-sar-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/RF-Exposure-Info/SAR-Report-9104679.pdf" -o "2AC7Z-ESPS3WROOM1-sar-report.pdf"
-echo "60f7208dd54ccff8d2af1d93c2e7d706c2259d0f2b9de6563b606057d49ba7a4  2AC7Z-ESPS3WROOM1-sar-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf.ARCHIVED.md
deleted file mode 100644
index f7e3f88..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 886,672 B (0.85 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 886,672 B (0.85 MiB) |
-| SHA-256 | `f8d1d246c0c849a6d51681f716c959ae554a3597aa73e74767b5734bdbf2a301` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User manual |
-| FCC document id | 6102626 |
-| Upstream publication date | 2022-09-08 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-manual-6102626.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6102626>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/6102626.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-manual-6102626.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-manual-6102626.pdf" -o "2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf"
-echo "f8d1d246c0c849a6d51681f716c959ae554a3597aa73e74767b5734bdbf2a301  2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf.ARCHIVED.md
deleted file mode 100644
index a0b2d0b..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 2,603,588 B (2.48 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,603,588 B (2.48 MiB) |
-| SHA-256 | `3e493b8b9ea24f00bca907dbade0be47aa602547df2c80b6ec80f59ded1a0c30` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 9104631 |
-| Upstream publication date | 2026-02-27 |
-| Grant date | 2026-02-27 |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-Manual-9104631.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9104631>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1/9104631.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-Manual-9104631.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf" \
-   "components/espressif/esp32-s3-wroom-1/artifacts/certification/2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1/User-Manual/User-Manual-9104631.pdf" -o "2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf"
-echo "3e493b8b9ea24f00bca907dbade0be47aa602547df2c80b6ec80f59ded1a0c30  2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1/artifacts/certification/README.md b/components/espressif/esp32-s3-wroom-1/artifacts/certification/README.md
deleted file mode 100644
index 3f0c341..0000000
--- a/components/espressif/esp32-s3-wroom-1/artifacts/certification/README.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# FCC equipment-authorization exhibits — `2AC7Z-ESPS3WROOM1`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AC7Z-ESPS3WROOM1`** |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Granted | **2026-02-27** |
-| Equipment class | BrushBot, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Source page | <https://fccid.io/2AC7Z-ESPS3WROOM1> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AC7Z-ESPS3WROOM1-internal-photo.pdf` | 3,636,909 | `318d8c6c95232515185c1e71389e5f90260094b4548f9e432589ba84f3b2c50a` | Internal Photos |
-| `2AC7Z-ESPS3WROOM1-internal-photos.pdf` | 338,977 | `1f60246b57db617203601cb18284a081bba4a27f13defca80ee7e6a68a64b7c8` | Internal Photos |
-| `2AC7Z-ESPS3WROOM1-label-location.pdf` | 30,758 | `68e843105466c1628186304e319636cb9c96081bf2a34bb284d124940c6d627f` | ID Label/Location Info |
-| `2AC7Z-ESPS3WROOM1-label.pdf` | 44,224 | `081ac1c0f3292f1bfcce8d8f169a538d04ce0477379cd1f930f0e930c5e6a8c8` | ID Label/Location Info |
-| `2AC7Z-ESPS3WROOM1-lable-and-location.pdf` | 1,437,286 | `0a57b90982013049a822a885d9a4e6b67f6d629012ee67cbe7a44e2ce22c8cd9` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AC7Z-ESPS3WROOM1-antenna-specification.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-antenna-specification.pdf.ARCHIVED.md) | 1,996,381 | Test Report |
-| [`2AC7Z-ESPS3WROOM1-external-photo.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-external-photo.pdf.ARCHIVED.md) | 1,367,037 | External Photos |
-| [`2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-external-photos-5637981.pdf.ARCHIVED.md) | 332,733 | External Photos |
-| [`2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-external-photos-6102617.pdf.ARCHIVED.md) | 1,275,356 | External Photos |
-| [`2AC7Z-ESPS3WROOM1-rf-exposure.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-rf-exposure.pdf.ARCHIVED.md) | 499,298 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1-sar-report-a.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-sar-report-a.pdf.ARCHIVED.md) | 845,988 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1-sar-report-b.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-sar-report-b.pdf.ARCHIVED.md) | 850,218 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1-sar-report-c1.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-sar-report-c1.pdf.ARCHIVED.md) | 5,908,102 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1-sar-report-c2.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-sar-report-c2.pdf.ARCHIVED.md) | 3,930,042 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1-sar-report-d.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-sar-report-d.pdf.ARCHIVED.md) | 3,974,985 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1-sar-report.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-sar-report.pdf.ARCHIVED.md) | 1,936,491 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-user-manual-6102626.pdf.ARCHIVED.md) | 886,672 | Users Manual |
-| [`2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1-user-manual-9104631.pdf.ARCHIVED.md) | 2,603,588 | Users Manual |
-
-Archived total: **13 files, 25.18 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **5 files, 5.23 MiB** |
-| Archived | **13 files, 25.18 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
-## ⚠ No component record exists for this module yet — *2026-09-11*
-
-This directory holds certification evidence for a part that has **no
-`components/espressif/<module>/README.md`**. It was created by the round-2 index
-merge so that the exhibits would not sit outside the repository with no
-placeholder trail, which the research method forbids for anything useful.
-
-Why the filing was fetched at all: it is the **positive control** for the whole
-certification pass. An absence finding ("no grant exists for X") is only evidence
-if the method demonstrably finds grants that *do* exist, and this is the grant it
-was tested against — see §2 of any
-`certification-and-compliance.md` in this repository.
-
-The module is fitted on several documented boards, so a full record is worth
-writing. Until one is, treat this directory as evidence storage, not as a record.
-Flagged in [`scratch/index-merge/deferred-round2.md`](../../../../../scratch/index-merge/deferred-round2.md).
-
diff --git a/components/espressif/esp32-s3-wroom-1u/acquisition/manifest.json b/components/espressif/esp32-s3-wroom-1u/acquisition/manifest.json
deleted file mode 100644
index a7d23fc..0000000
--- a/components/espressif/esp32-s3-wroom-1u/acquisition/manifest.json
+++ /dev/null
@@ -1,260 +0,0 @@
-{
- "record": "components/espressif/esp32-s3-wroom-1u",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1U-5786813",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1U/External-Photos/External-photos-5786813.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786813",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786813.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1U",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/External-Photos/External-photos-5786813.pdf"
-   ],
-   "sha256": "349908a8d4c6c648ebce87fa9d77dd1b591237976b8ca680fed7ddd663fd7f9f",
-   "bytes": 318108,
-   "destination": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1U",
-   "fcc_document_id": "5786813",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External photos",
-   "grant_date": "2022-03-31",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Sporton International Inc. (Kunshan)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1u",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1U-5786816",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1U/Internal-Photos/Internal-photos-5786816.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786816",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786816.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1U",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/Internal-Photos/Internal-photos-5786816.pdf"
-   ],
-   "sha256": "51984d7b8bb6439b3f63b11cb009f7453670e725faab65483c0eab47f1fc0944",
-   "bytes": 330364,
-   "destination": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1U",
-   "fcc_document_id": "5786816",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal photos",
-   "grant_date": "2022-03-31",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Sporton International Inc. (Kunshan)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1u",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1U-5786815",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1U/Label/Label-location-5786815.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786815",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786815.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1U",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/Label/Label-location-5786815.pdf"
-   ],
-   "sha256": "acefbe8e97ffaad5ae7e242eed1423fde8410bf3475835ee5b21a3c886e39913",
-   "bytes": 30429,
-   "destination": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-03-31",
-   "fcc_id": "2AC7Z-ESPS3WROOM1U",
-   "fcc_document_id": "5786815",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label location",
-   "grant_date": "2022-03-31",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Sporton International Inc. (Kunshan)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1u",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1U-5799920",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1U/Label/Label-5799920.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5799920",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5799920.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1U",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/Label/Label-5799920.pdf"
-   ],
-   "sha256": "e39b2e17bfd6b0b7730f49565bce383cdd8ec2b03da1dbcef42c0f089a7dbb2c",
-   "bytes": 446509,
-   "destination": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-03-31",
-   "fcc_id": "2AC7Z-ESPS3WROOM1U",
-   "fcc_document_id": "5799920",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label",
-   "grant_date": "2022-03-31",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Sporton International Inc. (Kunshan)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1u",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1U-5786820",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1U/RF-Exposure-Info/RF-Exposure-5786820.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786820",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786820.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1U",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/RF-Exposure-Info/RF-Exposure-5786820.pdf"
-   ],
-   "sha256": "72df38fc1893eea69de148b31f42fa913389b4b893245a7256b1746ca5ae8e41",
-   "bytes": 663023,
-   "destination": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-03-31",
-   "fcc_id": "2AC7Z-ESPS3WROOM1U",
-   "fcc_document_id": "5786820",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure",
-   "grant_date": "2022-03-31",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Sporton International Inc. (Kunshan)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1u",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1U-5786846",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1U/Test-Report/Test-report-BLE-5786846.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786846",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786846.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1U",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/Test-Report/Test-report-BLE-5786846.pdf"
-   ],
-   "sha256": "3233ed28800117010d620df1d917bf8f53ff54dc16ddcdba243a7d8a30c0ff2f",
-   "bytes": 4904214,
-   "destination": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-03-31",
-   "fcc_id": "2AC7Z-ESPS3WROOM1U",
-   "fcc_document_id": "5786846",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Test report BLE",
-   "grant_date": "2022-03-31",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Sporton International Inc. (Kunshan)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1u",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AC7Z-ESPS3WROOM1U-5786851",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AC7Z-ESPS3WROOM1U/User-Manual/User-manual-5786851.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786851",
-    "https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786851.pdf",
-    "https://fccid.io/2AC7Z-ESPS3WROOM1U",
-    "https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/User-Manual/User-manual-5786851.pdf"
-   ],
-   "sha256": "5cc0887f55ee8649188fd38b926130f7d72ece3ac3d821f69a17f7d725619c13",
-   "bytes": 683156,
-   "destination": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-09-27",
-   "fcc_id": "2AC7Z-ESPS3WROOM1U",
-   "fcc_document_id": "5786851",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User manual",
-   "grant_date": "2022-03-31",
-   "applicant": "ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Sporton International Inc. (Kunshan)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf",
-   "placeholder": "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/espressif/esp32-s3-wroom-1u",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 8b85fd2..0000000
--- a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1U-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 318,108 B (0.30 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 318,108 B (0.30 MiB) |
-| SHA-256 | `349908a8d4c6c648ebce87fa9d77dd1b591237976b8ca680fed7ddd663fd7f9f` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1U`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External photos |
-| FCC document id | 5786813 |
-| Upstream publication date | 2022-09-27 |
-| Grant date | 2022-03-31 |
-| Equipment class | 2.4GHz Wi-Fi & BT IoT Module, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | Sporton International Inc. (Kunshan) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U/External-Photos/External-photos-5786813.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786813>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786813.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/External-Photos/External-photos-5786813.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf" \
-   "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1U/External-Photos/External-photos-5786813.pdf" -o "2AC7Z-ESPS3WROOM1U-external-photos.pdf"
-echo "349908a8d4c6c648ebce87fa9d77dd1b591237976b8ca680fed7ddd663fd7f9f  2AC7Z-ESPS3WROOM1U-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-internal-photos.pdf b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-internal-photos.pdf
deleted file mode 100644
index 09c2885..0000000
Binary files a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-internal-photos.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label-location.pdf b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label-location.pdf
deleted file mode 100644
index d7f847d..0000000
Binary files a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label-location.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label.pdf b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label.pdf
deleted file mode 100644
index 557be41..0000000
Binary files a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-label.pdf and /dev/null differ
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf.ARCHIVED.md
deleted file mode 100644
index 987007c..0000000
--- a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1U-rf-exposure.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 663,023 B (0.63 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 663,023 B (0.63 MiB) |
-| SHA-256 | `72df38fc1893eea69de148b31f42fa913389b4b893245a7256b1746ca5ae8e41` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1U`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure |
-| FCC document id | 5786820 |
-| Upstream publication date | 2022-03-31 |
-| Grant date | 2022-03-31 |
-| Equipment class | 2.4GHz Wi-Fi & BT IoT Module, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | Sporton International Inc. (Kunshan) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U/RF-Exposure-Info/RF-Exposure-5786820.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786820>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786820.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/RF-Exposure-Info/RF-Exposure-5786820.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf" \
-   "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-rf-exposure.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1U/RF-Exposure-Info/RF-Exposure-5786820.pdf" -o "2AC7Z-ESPS3WROOM1U-rf-exposure.pdf"
-echo "72df38fc1893eea69de148b31f42fa913389b4b893245a7256b1746ca5ae8e41  2AC7Z-ESPS3WROOM1U-rf-exposure.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf.ARCHIVED.md
deleted file mode 100644
index dbfcd66..0000000
--- a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1U-test-report-ble.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 4,904,214 B (4.68 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 4,904,214 B (4.68 MiB) |
-| SHA-256 | `3233ed28800117010d620df1d917bf8f53ff54dc16ddcdba243a7d8a30c0ff2f` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1U`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Test report BLE |
-| FCC document id | 5786846 |
-| Upstream publication date | 2022-03-31 |
-| Grant date | 2022-03-31 |
-| Equipment class | 2.4GHz Wi-Fi & BT IoT Module, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | Sporton International Inc. (Kunshan) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U/Test-Report/Test-report-BLE-5786846.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786846>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786846.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/Test-Report/Test-report-BLE-5786846.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf" \
-   "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-test-report-ble.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1U/Test-Report/Test-report-BLE-5786846.pdf" -o "2AC7Z-ESPS3WROOM1U-test-report-ble.pdf"
-echo "3233ed28800117010d620df1d917bf8f53ff54dc16ddcdba243a7d8a30c0ff2f  2AC7Z-ESPS3WROOM1U-test-report-ble.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf.ARCHIVED.md b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 8a68ebf..0000000
--- a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AC7Z-ESPS3WROOM1U-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 683,156 B (0.65 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 683,156 B (0.65 MiB) |
-| SHA-256 | `5cc0887f55ee8649188fd38b926130f7d72ece3ac3d821f69a17f7d725619c13` |
-| FCC ID | **`2AC7Z-ESPS3WROOM1U`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User manual |
-| FCC document id | 5786851 |
-| Upstream publication date | 2022-09-27 |
-| Grant date | 2022-03-31 |
-| Equipment class | 2.4GHz Wi-Fi & BT IoT Module, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Test firm | Sporton International Inc. (Kunshan) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U/User-Manual/User-manual-5786851.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5786851>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AC7Z-ESPS3WROOM1U/5786851.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AC7Z-ESPS3WROOM1U>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AC7Z-ESPS3WROOM1U/User-Manual/User-manual-5786851.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf" \
-   "components/espressif/esp32-s3-wroom-1u/artifacts/certification/2AC7Z-ESPS3WROOM1U-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AC7Z-ESPS3WROOM1U/User-Manual/User-manual-5786851.pdf" -o "2AC7Z-ESPS3WROOM1U-user-manual.pdf"
-echo "5cc0887f55ee8649188fd38b926130f7d72ece3ac3d821f69a17f7d725619c13  2AC7Z-ESPS3WROOM1U-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/README.md b/components/espressif/esp32-s3-wroom-1u/artifacts/certification/README.md
deleted file mode 100644
index 8f15907..0000000
--- a/components/espressif/esp32-s3-wroom-1u/artifacts/certification/README.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# FCC equipment-authorization exhibits — `2AC7Z-ESPS3WROOM1U`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AC7Z-ESPS3WROOM1U`** |
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD 🇨🇳 |
-| Granted | **2022-03-31** |
-| Equipment class | 2.4GHz Wi-Fi & BT IoT Module, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Sporton International Inc. (Kunshan) |
-| Source page | <https://fccid.io/2AC7Z-ESPS3WROOM1U> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AC7Z-ESPS3WROOM1U-internal-photos.pdf` | 330,364 | `51984d7b8bb6439b3f63b11cb009f7453670e725faab65483c0eab47f1fc0944` | Internal Photos |
-| `2AC7Z-ESPS3WROOM1U-label-location.pdf` | 30,429 | `acefbe8e97ffaad5ae7e242eed1423fde8410bf3475835ee5b21a3c886e39913` | ID Label/Location Info |
-| `2AC7Z-ESPS3WROOM1U-label.pdf` | 446,509 | `e39b2e17bfd6b0b7730f49565bce383cdd8ec2b03da1dbcef42c0f089a7dbb2c` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AC7Z-ESPS3WROOM1U-external-photos.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1U-external-photos.pdf.ARCHIVED.md) | 318,108 | External Photos |
-| [`2AC7Z-ESPS3WROOM1U-rf-exposure.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1U-rf-exposure.pdf.ARCHIVED.md) | 663,023 | RF Exposure Info |
-| [`2AC7Z-ESPS3WROOM1U-test-report-ble.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1U-test-report-ble.pdf.ARCHIVED.md) | 4,904,214 | Test Report |
-| [`2AC7Z-ESPS3WROOM1U-user-manual.pdf.ARCHIVED.md`](2AC7Z-ESPS3WROOM1U-user-manual.pdf.ARCHIVED.md) | 683,156 | Users Manual |
-
-Archived total: **4 files, 6.26 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **3 files, 0.77 MiB** |
-| Archived | **4 files, 6.26 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
-## ⚠ No component record exists for this module yet — *2026-09-11*
-
-This directory holds certification evidence for a part that has **no
-`components/espressif/<module>/README.md`**. It was created by the round-2 index
-merge so that the exhibits would not sit outside the repository with no
-placeholder trail, which the research method forbids for anything useful.
-
-Why the filing was fetched at all: it is the **positive control** for the whole
-certification pass. An absence finding ("no grant exists for X") is only evidence
-if the method demonstrably finds grants that *do* exist, and this is the grant it
-was tested against — see §2 of any
-`certification-and-compliance.md` in this repository.
-
-The module is fitted on several documented boards, so a full record is worth
-writing. Until one is, treat this directory as evidence storage, not as a record.
-Flagged in [`scratch/index-merge/deferred-round2.md`](../../../../../scratch/index-merge/deferred-round2.md).
-
diff --git a/components/espressif/esp32-s3fn8/README.md b/components/espressif/esp32-s3fn8/README.md
deleted file mode 100644
index 6419952..0000000
--- a/components/espressif/esp32-s3fn8/README.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# Espressif ESP32-S3FN8
-
-> The ESP32-S3 variant with **8 MB flash in package and no PSRAM**.
-> Record created **2026-09-04** from M5Stack Stamp module schematics and vendor board support.
-> See also the family record [`espressif/esp32-s3r8`](../esp32-s3r8/README.md), which is the
-> **8 MB PSRAM, no-flash** variant — the two suffixes are easy to confuse and mean opposite
-> things.
-
-## Reading the suffix
-
-Espressif's ESP32-S3 part numbers encode in-package memory:
-
-| Suffix | In-package flash | In-package PSRAM |
-|---|---|---|
-| *(none)* | — | — |
-| **`FN8`** | **8 MB** | **none** |
-| `FH4` | 4 MB | none |
-| `R2` / `R8` / `R16V` | — | 2 / 8 / 16 MB |
-| `R8V`, `FN8R2`… | combinations | |
-
-**`FN8` = Flash 8, no PSRAM.** This is the single most consequential fact about every Cardputer:
-the platform has **512 KB of SRAM and nothing else**, and no amount of external wiring changes
-that, because the package has no PSRAM die and the Stamp module brings out no PSRAM-capable
-pins for one.
-
-## Key capabilities
-
-| Property | Value |
-|---|---|
-| Cores | 2 × Xtensa LX7, up to **240 MHz** |
-| SRAM | **512 KB** |
-| ROM | 384 KB |
-| In-package flash | **8 MB**, quad SPI |
-| **PSRAM** | **none** |
-| Radio | 2.4 GHz Wi-Fi 802.11 b/g/n; **Bluetooth 5 LE** (no BR/EDR) |
-| USB | **native USB-OTG** + USB Serial/JTAG |
-| Peripherals | 2 × I²S, 4 × SPI, 2 × I²C, RMT, LEDC, 2 × ADC, TWAI, SDMMC, LCD/camera interfaces |
-| Crypto | AES, SHA, RSA, HMAC, digital signature, secure boot, flash encryption |
-| GPIO | 45 usable on the bare die; **26 on the M5Stack Stamp-S3 footprint** |
-
-## What "no PSRAM" costs, concretely
-
-Measured against the Cardputer ADV's actual workload:
-
-| Consumer | Bytes | % of 512 KB |
-|---|---|---|
-| 240 × 135 × 16 bpp framebuffer | 64 800 | 12.7 % |
-| Double buffered | 129 600 | 25.3 % |
-| Wi-Fi + LWIP | ~50 000–80 000 | 10–16 % |
-
-Three independent pieces of downstream evidence:
-
-* Meshtastic's Cardputer ADV variant compiles with **`-DOLEDDISPLAY_REDUCE_MEMORY`**.
-* Bruce ships a **`-DLITE_VERSION=1`** flag "to save space".
-* A community Meshtastic-client author (r/CardPuter, 2026-08-01) put a **2.16 MB GNU Unifont
-  table in its own flash partition** and memory-mapped it, *"so rendering Cyrillic, CJK or Greek
-  costs no heap at all"* — because *"the ESP32-S3 here has no PSRAM, so a full Unicode font
-  cannot live in RAM."*
-
-## Support pins seen on the M5Stack Stamp modules
-
-From `Sch_StampS3_v0.2` and `Sch_StampS3_v0.3.3`:
-
-| Function | Detail |
-|---|---|
-| Crystal | **X1, 40 MHz**, load caps 12 pF / 10 pF (v0.2) or 12 pF / 12 pF (v0.3.3) on `XTAL_P`/`XTAL_N` (pins 53/54) |
-| `VDD_SPI` | pin 29, decoupled 100 nF + 1 µF — the in-package flash supply |
-| `VDDA1`/`VDDA2` | pins 55/56 |
-| `VDD3P3_RTC` | pin 20 · `VDD3P3_CPU` pin 46 |
-| `CHIP_PU` | pin 4, from `ESP_EN` with an RC and a 10 kΩ pull-up |
-| `LNA_IN` | pin 1 → π matching network → `ANT1` |
-| `GND` | pin 57 and the exposed pad |
-| `U0TXD`/`U0RXD` | brought to the module header with a **510 Ω 1 %** series resistor on TX |
-
-## Used By
-
-### M5Stack Stamp-S3 and Stamp-S3A modules
-
-[`components/m5stack/stamp-s3`](../../m5stack/stamp-s3/README.md) ·
-[`components/m5stack/stamp-s3a`](../../m5stack/stamp-s3a/README.md)
-*(both created by a concurrent session; this record links rather than duplicates)*
-
-Both modules carry the same `ESP32-S3FN8` die. What differs between them is entirely support
-circuitry — the 3.3 V regulator, the load switch, and **which rail the WS2812 sits on**.
-
-### M5Stack Cardputer v1.0, v1.1 and ADV
-
-[`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md) ·
-[`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-All three use the same SoC through a Stamp module. Board-level GPIO allocation differs
-substantially and is documented per device; the relevant SoC-level notes are:
-
-* **G0** is the boot strap and the user button on every Cardputer.
-* **G3** is a JTAG-source strap **and** the CAP header's `RESET` line on the ADV — worth knowing
-  before attaching a board that drives it during reset.
-* **G45/G46** are strap pins; the ADV drives G46 from the ES8311's `ASDOUT` (high-Z until the
-  codec is enabled, so benign in practice).
-* **G21** carries the WS2812 data on all three.
-* **No SDMMC 4-bit mode** is used: the microSD is 1-bit SPI on all three, with `D1`/`D2` unwired.
-
-### M5Stack CardputerZero
-
-Does **not** use this part — it is a Raspberry Pi CM0 (BCM2837) device.
-[`devices/m5stack/cardputer-zero`](../../../devices/m5stack/cardputer-zero/README.md)
-
-## Substitutes and migration
-
-| Part | Migration note |
-|---|---|
-| **`ESP32-S3R8`** / `R8V` | 8 MB PSRAM but **no in-package flash** — you must add an external flash chip. Not a drop-in. See [`esp32-s3r8`](../esp32-s3r8/README.md). |
-| `ESP32-S3FN8R2` etc. | flash **and** PSRAM in package — the part a "Cardputer with PSRAM" would want |
-| `ESP32-S3-WROOM-1-N8R8` | module form, flash + PSRAM; different footprint entirely from the Stamp-S3 |
-| ESP32-S2 | no BLE, single core |
-| ESP32-C6 | RISC-V, Wi-Fi 6 + 802.15.4, much less RAM |
-
-## Gaps
-
-* **No Espressif datasheet retained by this record.** M5Stack mirrors one at
-  `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf` (linked from the
-  Cardputer Mesh Kit page) — **not fetched in this pass**, and the PaperMono pass established
-  that M5Stack's mirrors are frequently stale. Prefer Espressif's own copy and hash both.
-* Pin-number-to-name mapping above is read from an M5Stack symbol, not from Espressif's datasheet.
-* Errata: **not reviewed**.
diff --git a/components/espressif/esp32-s3r8/README.md b/components/espressif/esp32-s3r8/README.md
index 518656d..f62bf82 100644
--- a/components/espressif/esp32-s3r8/README.md
+++ b/components/espressif/esp32-s3r8/README.md
@@ -125,12 +125,8 @@ Do not describe the board's 16 MB W25Q128 flash as part of ESP32-S3R8. GPIO0 is
 
 ## Used By
 
-- **The entire [LilyGO T-Display-S3 family](../../../devices/lilygo/t-display-s3-shared/README.md)** — eleven boards, every one of which uses the ESP32-S3R8, as a **bare die** rather than a module: [T-Display-S3](../../../devices/lilygo/t-display-s3/README.md) and [Touch](../../../devices/lilygo/t-display-s3-touch/README.md), [AMOLED](../../../devices/lilygo/t-display-s3-amoled/README.md), [AMOLED Plus](../../../devices/lilygo/t-display-s3-amoled-plus/README.md), [AMOLED 1.64″](../../../devices/lilygo/t-display-s3-amoled-1-64/README.md), [AMOLED 1.43/1.75″](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md), [T4-S3](../../../devices/lilygo/t4-s3/README.md), [AMOLED Lite](../../../devices/lilygo/t-display-amoled-lite/README.md), [Long](../../../devices/lilygo/t-display-s3-long/README.md), [Pro](../../../devices/lilygo/t-display-s3-pro/README.md). All pair it with a 16 MB [W25Q128JV](../../winbond/w25q128jv/README.md) over QIO and use the in-package 8 MB **OPI** PSRAM — which consumes **GPIO26–37** and is the reason these boards have so few free pins. Two integration facts recur family-wide and are documented at the family hub: the **native-USB `USB CDC On Boot` boot-blocking trap** ([`features/usb.md`](../../../devices/lilygo/t-display-s3/features/usb.md)) and the requirement to set Arduino `PSRAM = OPI PSRAM`, without which `ps_malloc()` silently fails.
-
 - [Waveshare ESP32-S3-Knob-Touch-LCD-1.8](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md)
 - [Seeed Studio XIAO ESP32S3 Sense](../../../devices/seeed-studio/xiao-esp32s3-sense/README.md)
-- [M5Stack PaperMono (SKU C153)](../../../devices/m5stack/papermono/README.md) — *added 2026-09-01*
-- [Waveshare ESP32-S3-ePaper-3.97 (SKUs 33552 / 33810 / 33811)](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md) — *added 2026-09-01*. Fitted as an **`ESP32-S3-WROOM-1-N16R8` module** rather than a bare die, so 16 MB flash + 8 MB **octal** PSRAM. The octal PSRAM consumes GPIO35–37, which the board's own schematic marks `NC` — see that record's [pinouts](../../../devices/waveshare/esp32-s3-epaper-3.97/pinouts-and-buses.md#is-anything-free). Native USB on GPIO19/20 with **no USB-UART bridge fitted**. Note the vendor storefront contradicts itself on the flash/PSRAM split; the module part number settles it ([C-WS3](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws3--the-storefront-swaps-flash-and-psram))
 
 ### Seeed Studio XIAO ESP32S3 Sense
 
@@ -148,72 +144,6 @@ Also relevant to this board: the [Classic Bluetooth limitation](#radio-capabilit
 
 Full pin map: [pinouts-and-buses.md](../../../devices/seeed-studio/xiao-esp32s3-sense/pinouts-and-buses.md#11-full-esp32-s3r8-pin-usage-map)
 
-### M5Stack PaperMono (SKU C153)
-
-*Added 2026-09-01.* Fitted as **`U12`**, bare package, on schematic sheet 3 (`MCU_Core`) of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) and its Lite sibling. Paired with an external **16 MB [XMC XM25UH128DHIQT](../../xmc/xm25uh128dhiqt/README.md)** NOR flash and a **[40 MHz crystal](../../generic/cn4040m000157a530001-40mhz-crystal/README.md)** (`X1`, reached through `L7` = 24 nH). Evidence is the published schematic PDF and M5Stack's own source; no hardware was available.
-
-**On this board the ESP32-S3 does not control its own power.** Two [Puya PY32L020F15U6](../../puya/py32l020f15u6/README.md) coprocessors running M5Stack firmware — the [M5PM1](../../m5stack/m5pm1/README.md) (I²C `0x6E`) and the [M5IOE1](../../m5stack/m5ioe1/README.md) (I²C `0x4F`) — own the rails, the power button, the `BOOT` strap, the display frontlight and every `L3B` peripheral rail. The S3 is a peripheral of its own power system.
-
-Four integration details from this board are worth carrying to any ESP32-S3R8 design:
-
-- **⚠ `GPIO45` and `GPIO46` are used as the PDM microphone clock and data.** Both are strapping pins: `GPIO45` selects the **`VDD_SPI` voltage** (default weak pull-down = 3.3 V; sampled high ⇒ **1.8 V**, which under-volts the 2.3–3.6 V flash), and `GPIO46` controls **ROM message printing**. The board is safe only because the microphone's rail (`PDM_VDD`) is behind a load switch that is **off at reset** — the protection is the load switch, not the wiring. Firmware that leaves that rail enabled across a soft reset re-exposes the `GPIO46` strap. See [LMD4737T261-AC02 §3.3](../../generic/lmd4737t261-ac02-pdm-microphone/README.md#33--both-pdm-signals-land-on-esp32-s3-strapping-pins).
-- **`GPIO15`/`GPIO16` — the `XTAL_32K` pins — carry the e-paper SPI** (`G15_SPI2_CLK`, `G16_EINK_CS`), so there is **no 32.768 kHz crystal**. Timekeeping across sleep is the RX8130CE's job, not the S3's internal RTC.
-- **`VDD_SPI` (pin 29) supplies the external flash directly** as `VDD_NOR`, with a 22 Ω series resistor on `SPICLK`. All four SPI data lines (`SPID`/`SPIQ`/`SPIWP`/`SPIHD`) are routed, and the fitted flash ships with its Quad Enable bit set at the factory — so **the hardware supports QIO**, even though the shipped factory image's header reports DIO. That conflict is resolved in [XM25UH128DHIQT §5](../../xmc/xm25uh128dhiqt/README.md#5--resolving-the-qiodio-conflict).
-- **Octal PSRAM is enforced in software.** `M5GFX.cpp:2072–2081` aborts display initialisation and logs `"M5PaperMono need OPI-PSRAM enabled"` if `CONFIG_SPIRAM_MODE_OCT` is missing. The board still enumerates and runs — with a blank screen and one easily-missed log line. This is a direct consequence of choosing the **R8** variant, whose 8 MB in-package PSRAM is octal.
-
-Also relevant: the [Classic Bluetooth limitation](#radio-capabilities-and-the-classic-bluetooth-limitation). The PaperMono has a buzzer and a PDM microphone but no Classic Bluetooth audio path, and none can be added.
-
-Toolchain as shipped: **ESP-IDF 5.5.1**, `arduino-esp32` 3.3.10 as a managed component, 16 MB flash, single 15 MiB `factory` partition with **no OTA slots**.
-
-### Xteink X4 Pro and X4 Classic — *added 2026-09-04*
-
-Two sealed consumer e-readers built on the same ESP32-S3 board with **16 MB flash
-and 8 MB PSRAM**, targeted in PlatformIO as `esp32-s3-devkitc1-n16r8`
-(*"matches the X4 Pro dump"*). Identified from a factory flash dump and
-on-hardware probing, not from a schematic — **no schematic or teardown exists for
-either device**.
-
-| | [X4 Pro](../../../devices/xteink/x4-pro/README.md) | [X4 Classic](../../../devices/xteink/x4-classic/README.md) |
-|---|---|---|
-| Board tag in stock firmware | `ESP32S3_X4_TL_SSD1677` | `ESP32S3_X4_CLA` (rev `ESP32S3_X4R2_CLA`) |
-| Touch | [GT911](../../goodix/gt911/README.md) @0x5D | **none** |
-| Frontlight | dual warm/cool, LEDC ch4/ch5 on GPIO8/9 | **none** — those pins become buttons |
-| IMU | **none** | [QMI8658](../../qst/qmi8658a/README.md) @0x6B |
-| Buttons | 2 side + power | **7 discrete, interrupt-driven** |
-| Display DC / RST / BUSY | 18 / 14 / 6 | **14 / 10 / 18** |
-| SD power enable | GPIO5, active-LOW | GPIO6, active-LOW |
-
-Shared: display SPI SCLK 12 / MOSI 11 / CS 13 at 20 MHz; **native SDMMC 1-bit**
-on CLK 41 / CMD 42 / DAT0 40; I²C SDA 39 / SCL 38 @ 400 kHz; native USB
-D− 19 / D+ 20; charge STAT GPIO21 active-HIGH; **GPIO1 as a master peripheral
-rail driven HIGH first at boot** — without it *"EPD BUSY never asserts, SD
-returns 0xFF"*.
-
-**Two S3-specific traps worth carrying forward:**
-
-1. **GPIO19/20 are native USB D−/D+ and must never be probed at boot.** The
-   sibling ESP32-C3 Xteink devices run an I²C device-fingerprint on SDA 20 /
-   SCL 0; on an S3 those land on **D+ and a boot strap**. The SDK compiles that
-   path out unless a C3 profile is in the build — a hand-rolled build combining
-   both profiles would be actively dangerous.
-2. **GPIO0 is the Left navigation button *and* the boot strap** on the X4 Pro.
-   Fine as a button, but powering on with it held enters download mode.
-
-**Why the R8 variant matters here.** The 8 MB in-package PSRAM is what separates
-these from the C3-based [X4](../../../devices/xteink/x4/README.md) and
-[X3](../../../devices/xteink/x3/README.md), where CrossPoint had to abandon
-GitHub-release OTA because *"it causes out of memory issues on the x3"*. The
-[InkBack SDK fork](https://github.com/goodyttoor/inkback-freeink-sdk) uses it for
-*"PSRAM multi-buffer, damage windows, ghost budget"* — none of which is possible
-on the C3 devices.
-
-Stock toolchain differs by generation: the X4 Pro's 7.4.4 firmware is a **native
-ESP-IDF 6.0.1** build (app descriptor `xteink_app 7.4.4`, built 2026-08-27), while
-the C3 devices ship **Arduino-framework** builds on ESP-IDF 4.4.7.
-
-→ [`devices/xteink/x4-pro/pinouts-and-buses.md`](../../../devices/xteink/x4-pro/pinouts-and-buses.md)
-→ [`devices/xteink/x4-classic/README.md`](../../../devices/xteink/x4-classic/README.md)
-
 ## Related components
 
 - [ESP32-U4WDH](../../espressif/esp32-u4wdh/README.md) — original-series ESP32 with BR/EDR, used as the Classic Bluetooth companion MCU on the Waveshare knob board
@@ -238,8 +168,6 @@ Distilled from the ESP-IDF and ESP-IoT-Solution PDFs formerly held in `artifacts
 | ESP-IDF Programming Guide v5.2.5 (esp32s3 target) | https://docs.espressif.com/projects/esp-idf/en/v5.2.5/esp32s3/esp-idf-en-v5.2.5-esp32s3.pdf | 2026-08-21 | v5.2.5 | **archived 2026-08-24** — see [ARCHIVED-FRAMEWORK-GUIDES.md](artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) |
 | ESP-IoT-Solution Programming Guide | https://docs.espressif.com/projects/esp-iot-solution/en/latest/esp-iot-solution-en-master.pdf | 2026-08-21 | esp-docs `master` build | **archived 2026-08-24** — see [ARCHIVED-FRAMEWORK-GUIDES.md](artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) |
 | ESP-IDF Bluetooth API reference, rendered for target `esp32s3` (evidence that no Classic Bluetooth or LE Audio API is offered for this target) | https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-reference/bluetooth/index.html | 2026-08-22 | v6.0.2 as served | - (HTML, link-only) |
-| ESP32-S3 Series Datasheet — **M5Stack mirror** (linked from the PaperMono product page) | https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf | 2026-09-01 | **v2.0**, 84 pp, 1 083 807 B | The revision M5Stack ships to PaperMono users; see [Four ESP32-S3 datasheet files](#four-esp32-s3-datasheet-files-four-different-sha-256-values--added-2026-09-01) | artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf |
-| M5Stack PaperMono schematic — `PaperMono_SCH_V0.6.2_20260522.pdf` | https://docs.m5stack.com/en/core/PaperMono | 2026-09-01 | V0.6.2, 2026-05-22, 6 sheets | The `U12` wiring in the PaperMono **Used By** section: strapping-pin usage, `VDD_SPI`→flash, `XTAL_32K` reuse | devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf |
 
 ## Local artifacts
 
@@ -255,8 +183,6 @@ Distilled from the ESP-IDF and ESP-IoT-Solution PDFs formerly held in `artifacts
 | **added 2026-08-24 (Waveshare mirror, older revisions)** | | |
 | artifacts/esp32-s3-datasheet-v1.6-waveshare-mirror.pdf | 1186331 | `b79310e52e90599920fb067c9365263a18943c2efc4b9788edffc2b2d6cdefa1` |
 | artifacts/esp32-s3-technical-reference-manual-v1.2-waveshare-mirror.pdf | 14540185 | `47bb075de167d8165fc845f4729396080cf0fc92a9f0b793a2527dddae8a2ed9` |
-| **added 2026-09-01 (M5Stack mirror, older revision)** | | |
-| artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf | 1083807 | `b6db403d6d5db8d1b4db0c8390ff7e0a7db714b8388e986e1c64bff563f76b61` |
 
 All artifacts were validated as genuine PDFs (`%PDF` header and `%%EOF` trailer present) on retrieval.
 
@@ -294,49 +220,6 @@ the vendor's choice.
 > different revision under the same filename. The mirrored copies here are revision-pinned by
 > filename and hash precisely because the upstream URL is not.
 
-### Four ESP32-S3 datasheet files, four different SHA-256 values — *added 2026-09-01*
-
-The M5Stack PaperMono research pass added a fourth copy, and the resulting picture is worth
-stating explicitly because it is the concrete case the research method's filing rules were
-written around. **The tree now holds four ESP32-S3 datasheet files. No two are byte-identical.**
-
-| Local file | Revision | Pages | Bytes | SHA-256 | Source |
-|---|---|---:|---:|---|---|
-| `artifacts/esp32-s3-datasheet.pdf` | **v2.2** — current | **87** | 1 098 115 | `2d5a7cb7fd559d8d972bd88db32669c0196d23f22d7afaafb0f63d099b589a3f` | **Espressif direct** |
-| `artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf` | **v2.0** | **84** | 1 083 807 | `b6db403d6d5db8d1b4db0c8390ff7e0a7db714b8388e986e1c64bff563f76b61` | **M5Stack mirror**, `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf` |
-| `artifacts/esp32-s3-datasheet-v1.6-waveshare-mirror.pdf` | **v1.6** | **75** | 1 186 331 | `b79310e52e90599920fb067c9365263a18943c2efc4b9788edffc2b2d6cdefa1` | **Waveshare mirror**, `files.waveshare.com/wiki/common/Esp32-s3_datasheet_en.pdf` |
-| `devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/esp32-s3-datasheet-seeed-copy.pdf` | **v1.6** | **75** | 1 186 462 | `8f3a10205e31799d11ae6629c7383cce896d59f3a009048b53fcfa1ca90708b9` | **Seeed copy** |
-
-**Which revision each board vendor ships:**
-
-| Board vendor | Revision served | Behind current (v2.2) by |
-|---|---|---|
-| **Espressif** | **v2.2**, 87 pp | — (this is current) |
-| **M5Stack** ([PaperMono](../../../devices/m5stack/papermono/README.md)) | **v2.0**, 84 pp | one minor revision |
-| **Waveshare** ([Knob-Touch-LCD-1.8](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md)) | **v1.6**, 75 pp | six revisions, twelve pages |
-| **Seeed Studio** ([XIAO ESP32S3 Sense](../../../devices/seeed-studio/xiao-esp32s3-sense/README.md)) | **v1.6**, 75 pp | six revisions, twelve pages |
-
-Two observations that only become visible once all four are held together:
-
-1. **Waveshare and Seeed both serve revision 1.6 — and their files are not the same bytes.**
-   1 186 331 vs 1 186 462 bytes, 131 bytes apart, different hashes, same 75 pages and the same
-   cover version string. These are **two separate exports of the same revision**, not two
-   different revisions and not one file mirrored twice. Deduplicating them by "they're both
-   v1.6" would have destroyed the evidence that two vendors independently re-exported the
-   document. Deduplicating them by hash would keep both, correctly.
-2. **M5Stack is the closest to current of the three board vendors**, at one minor revision
-   behind rather than six. The 84→87 page growth between v2.0 and v2.2 is not cosmetic.
-
-**The operational rule this supports:** *hash mirrors, do not assume them.* A file's revision
-string, its page count and its byte size are three independent facts and all three can agree
-while the bytes differ. Nobody could have told these four apart without hashing them, and the
-first three were collected by three different agents on three different device tasks, each of
-whom believed they were fetching "the ESP32-S3 datasheet".
-
-**Which one to read.** For what the silicon does, use **v2.2** — it is current and
-authoritative. Use a vendor's mirrored revision when you are trying to understand *that
-vendor's* design or firmware, because it is what they had in front of them.
-
 `esp-iot-solution` is included because it is the official home of the ESP-IDF component drivers this board depends on — QSPI LCD panel drivers, touch controllers, knob/encoder input and LVGL porting — none of which are documented in the core ESP-IDF programming guide. The v5.2.5 programming guide is retained alongside v5.1.4 because it is the newest ESP-IDF release for which Espressif publishes a PDF build at all; see the vendor guide for the details of that cutoff.
 
 ## Documentation sourcing
diff --git a/components/espressif/esp32-s3r8/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md b/components/espressif/esp32-s3r8/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
index 9c22eb9..c4bc278 100644
--- a/components/espressif/esp32-s3r8/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
+++ b/components/espressif/esp32-s3r8/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
@@ -3,7 +3,7 @@
 Three large Espressif **framework documentation** PDFs that used to live in this directory have been moved out of the repository. They were **regenerable from stable, verified Espressif URLs** and are not scarce, unlike the chip datasheet, TRM, errata and hardware-design guidelines in this directory, **all of which are retained**.
 
 - **Archived:** 2026-08-24
-- **Moved to:** `archive/components/espressif/esp32-s3r8/artifacts/` (same relative path)
+- **Moved to:** `../hardware-doc-archive/doc/hardware/components/espressif/esp32-s3r8/artifacts/` (same relative path)
 - **Total reclaimed here:** 80 963 336 bytes (~77.2 MiB)
 
 Nothing was deleted. The knowledge worth keeping was extracted into committed Markdown **before** the files were moved — see [What was extracted](#what-was-extracted-and-where-it-now-lives).
diff --git a/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.1.4-esp32s3.pdf b/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.1.4-esp32s3.pdf
deleted file mode 120000
index d52132b..0000000
--- a/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.1.4-esp32s3.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.1.4-esp32s3.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.2.5-esp32s3.pdf b/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.2.5-esp32s3.pdf
deleted file mode 120000
index 0d18393..0000000
--- a/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.2.5-esp32s3.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-s3r8/artifacts/esp-idf-programming-guide-v5.2.5-esp32s3.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-s3r8/artifacts/esp-iot-solution-programming-guide.pdf b/components/espressif/esp32-s3r8/artifacts/esp-iot-solution-programming-guide.pdf
deleted file mode 120000
index 738ea55..0000000
--- a/components/espressif/esp32-s3r8/artifacts/esp-iot-solution-programming-guide.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-s3r8/artifacts/esp-iot-solution-programming-guide.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf b/components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf
deleted file mode 100644
index 752be01..0000000
Binary files a/components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/espressif/esp32-u4wdh/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md b/components/espressif/esp32-u4wdh/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
index bc9a76e..7f03067 100644
--- a/components/espressif/esp32-u4wdh/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
+++ b/components/espressif/esp32-u4wdh/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
@@ -3,7 +3,7 @@
 Three large Espressif **framework documentation** PDFs that used to live in this directory have been moved out of the repository. They were **regenerable from stable, verified Espressif URLs** and are not scarce, unlike the chip datasheet, TRM, errata, hardware-design guidelines and PCNs in this directory, **all of which are retained**.
 
 - **Archived:** 2026-08-24
-- **Moved to:** `archive/components/espressif/esp32-u4wdh/artifacts/` (same relative path)
+- **Moved to:** `../hardware-doc-archive/doc/hardware/components/espressif/esp32-u4wdh/artifacts/` (same relative path)
 - **Total reclaimed here:** 94 374 621 bytes (~90.0 MiB)
 
 Nothing was deleted. The knowledge worth keeping was extracted into committed Markdown **before** the files were moved — see [What was extracted](#what-was-extracted-and-where-it-now-lives).
diff --git a/components/espressif/esp32-u4wdh/artifacts/esp-adf-programming-guide.pdf b/components/espressif/esp32-u4wdh/artifacts/esp-adf-programming-guide.pdf
deleted file mode 120000
index fb07519..0000000
--- a/components/espressif/esp32-u4wdh/artifacts/esp-adf-programming-guide.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-u4wdh/artifacts/esp-adf-programming-guide.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.1.4-esp32.pdf b/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.1.4-esp32.pdf
deleted file mode 120000
index 848f410..0000000
--- a/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.1.4-esp32.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.1.4-esp32.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.2.5-esp32.pdf b/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.2.5-esp32.pdf
deleted file mode 120000
index 5d6f9d6..0000000
--- a/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.2.5-esp32.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-u4wdh/artifacts/esp-idf-programming-guide-v5.2.5-esp32.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32-datasheet.pdf b/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32-datasheet.pdf
deleted file mode 120000
index 49042b4..0000000
--- a/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32-datasheet.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32-datasheet.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32d-wroom-32u-datasheet.pdf b/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32d-wroom-32u-datasheet.pdf
deleted file mode 120000
index 6313bd7..0000000
--- a/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32d-wroom-32u-datasheet.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32d-wroom-32u-datasheet.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32e-wroom-32ue-datasheet.pdf b/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32e-wroom-32ue-datasheet.pdf
deleted file mode 120000
index 279389e..0000000
--- a/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32e-wroom-32ue-datasheet.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-wroom-32u/artifacts/esp32-wroom-32e-wroom-32ue-datasheet.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-wrover/artifacts/esp32-wrover-b-datasheet.pdf b/components/espressif/esp32-wrover/artifacts/esp32-wrover-b-datasheet.pdf
deleted file mode 120000
index 47a4f9b..0000000
--- a/components/espressif/esp32-wrover/artifacts/esp32-wrover-b-datasheet.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-wrover/artifacts/esp32-wrover-b-datasheet.pdf
\ No newline at end of file
diff --git a/components/espressif/esp32-wrover/artifacts/esp32-wrover-e-wrover-ie-datasheet.pdf b/components/espressif/esp32-wrover/artifacts/esp32-wrover-e-wrover-ie-datasheet.pdf
deleted file mode 120000
index dcfeb87..0000000
--- a/components/espressif/esp32-wrover/artifacts/esp32-wrover-e-wrover-ie-datasheet.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/espressif/esp32-wrover/artifacts/esp32-wrover-e-wrover-ie-datasheet.pdf
\ No newline at end of file
diff --git a/components/everest-semiconductor/es8311/README.md b/components/everest-semiconductor/es8311/README.md
deleted file mode 100644
index b245b71..0000000
--- a/components/everest-semiconductor/es8311/README.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Everest Semiconductor ES8311
-
-- **Category:** low-power mono **audio codec** — ADC + DAC, I²S/PCM serial audio, I²C control, integrated microphone bias and PGA
-- **Manufacturer:** Everest Semiconductor (深圳市中科蓝讯 / Everest-semi)
-- **Control interface:** I²C. 7-bit address **`0x18`** with `CE` low, `0x19` with `CE` high — **`inferred` from the datasheet, not read from any board's source in this pass**
-- **Document status:** datasheet retained; **version `unknown`** — the mirrored copy carries no revision marking that this pass identified
-- **Research status:** **stub.** The datasheet is held and validated; the register map has **not** been mined. Board-level integration is documented under [Used by](#used-by)
-- **Retrieved:** 2026-09-01. **Nothing verified on hardware.**
-
-## What it is
-
-A single-channel codec aimed at voice: one ADC path for a microphone, one DAC path
-for a speaker or line output, with the analogue front end (bias, PGA) integrated so a
-host needs only an amplifier for loudspeaker drive. It is the codec Espressif's own
-reference designs use most often for voice-assistant work, which is why it appears on
-so many ESP32-S3 boards.
-
-Audio data moves over **I²S**; configuration goes over **I²C**. Both are needed —
-a board that wires I²S but not I²C cannot bring the part out of reset into a useful
-state.
-
-## What has not been done
-
-- **Register map not transcribed.** No initialisation sequence, no clock-tree
-  analysis, no PGA or ALC settings.
-- **No audit of any driver against the datasheet** — the method's
-  [step 10](../../../.agents/skills/hardware-device-research/SKILL.md#10-audit-vendor-firmware-and-driver-source-against-the-primary-documents).
-  Waveshare ships a hand-rolled `es8311.cpp`/`es8311_reg.h` rather than using a
-  library, which makes it a good audit target.
-- **No I²C address confirmed on hardware or in board source.** The `0x18`/`0x19`
-  values above are the part's documented defaults, labelled `inferred`.
-- **No comparison** against the sibling [ES8156](../es8156/README.md) already in this
-  knowledge base — the ES8156 is DAC-only, so the two are not interchangeable where
-  capture is needed, but that has not been written up properly.
-
-## Artifacts
-
-| File | Bytes | SHA-256 | Source | Retrieved | Version |
-|---|---|---|---|---|---|
-| [`artifacts/es8311-datasheet-waveshare-mirror.pdf`](artifacts/es8311-datasheet-waveshare-mirror.pdf) | 729 315 | `be42a2cb09093378feaccf55c227be579edc5a17786a11cc34254ea91264538a` | `https://files.waveshare.com/wiki/common/ES8311.DS.pdf` | 2026-09-01 | `unknown` |
-
-**This is Waveshare's mirror, not Everest's own copy.** Named accordingly, per the
-repository's rule that a vendor mirror is retained only when labelled as one. The
-manufacturer's original was **not obtained** in this pass — worth doing, because
-[Waveshare's mirrors have already been shown to run stale on this very board](../../nxp/pcf85063a/README.md):
-its PCF85063A copy is three years and one revision behind NXP's.
-
-Validated by magic bytes (`%PDF-`), not by HTTP status. **Licence `unknown`** — no
-stated terms. Disposition: `repository`.
-
-## Used by
-
-### [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-
-Designator `U8`. The board's only audio codec, providing both the microphone capture
-path and the playback path that feeds the
-[NS4150B](../../nsiway/ns4150b/README.md) amplifier and the MX1.25 speaker header.
-
-| Connection | Pin | Note |
-|---|---|---|
-| I²S `MCLK` | GPIO13 | |
-| I²S `SCLK` | GPIO14 | |
-| I²S `LRCK` | GPIO47 | |
-| I²S `DSOUT` | GPIO21 | codec → host (capture) |
-| I²S `DSDIN` | GPIO48 | host → codec (playback) |
-| I²C `SDA` / `SCL` | GPIO41 / GPIO42 | **shared** with the PMIC, RTC and IMU |
-| Amplifier gate | GPIO39 (`AudioCTR_PIN`) | **also carries `AXIS_INT1` in the schematic table — [unresolved](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws9--gpio39-carries-two-functions)** |
-
-Microphone nets `MIC_P` / `MIC_N` reach the codec differentially. This is the
-hardware behind the board's marketed "AI voice interaction" — the cloud side of which
-is the third-party [xiaozhi](https://github.com/78/xiaozhi-esp32) firmware, not a
-Waveshare service. See
-[development.md](../../../devices/waveshare/esp32-s3-epaper-3.97/development.md).
-
-Vendor example: `Arduino/examples/01_Audio_Test`, plus ESP-IDF `02_Mic_test` and
-`03_Music`.
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-Designator **U6**, I²C **`0x18`** on the internal bus (SDA G8 / SCL G9), I²S slave on
-`I2S_NUM_1`: `SCLK` G41, `LRCK` G43, `DSDIN` G42, `ASDOUT` G46. **No MCLK is wired**, so the
-codec is configured MCLK-from-BCLK (`0x01 = 0xB5` or `0xBA`, `0x02 = 0x18` → `MULT_PRE=3`).
-
-It is the **only** audio path on the board: the analog MEMS microphone
-([MSM381A3729H9BP](../../memsensing/msm381a3729h9bp/README.md)) feeds `MIC1P`/`MIC1N`, and the
-DAC drives both the [NS4150B](../../nsiway/ns4150b/README.md) speaker amplifier and the 3.5 mm
-jack. Nothing on this board makes a sound without it.
-
-⚠ **Two defects in M5Unified's ADV callbacks** (`8530f537`), both inherited verbatim by Bruce:
-
-1. `_speaker_enabled_cb_cardputer_adv` writes `0x01 = 0xB5` while
-   `_microphone_enabled_cb_cardputer_adv` writes `0x01 = 0xBA` — **the same clock-manager
-   register on the same shared codec**. Last writer wins; speaker-then-mic and mic-then-speaker
-   are not equivalent.
-2. The **microphone's** disable list ends `0x00 = 0x00` (**CSM power down**), while the
-   **speaker's** disable list is **empty**. So disabling the mic silences the speaker, and
-   disabling the speaker leaves the codec fully powered.
-
-Analysis: [`devices/m5stack/cardputer-adv/features/audio.md` §6](../../../devices/m5stack/cardputer-adv/features/audio.md).
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.1.*
-
-## See also
-
-- [ES8156](../es8156/README.md) — DAC-only sibling, already recorded here
-- [NS4150B](../../nsiway/ns4150b/README.md) — the amplifier it drives on this board
-- [All components](../../README.md)
diff --git a/components/everest-semiconductor/es8311/artifacts/es8311-datasheet-waveshare-mirror.pdf b/components/everest-semiconductor/es8311/artifacts/es8311-datasheet-waveshare-mirror.pdf
deleted file mode 100644
index ff7111a..0000000
Binary files a/components/everest-semiconductor/es8311/artifacts/es8311-datasheet-waveshare-mirror.pdf and /dev/null differ
diff --git a/components/focaltech/ft3168/README.md b/components/focaltech/ft3168/README.md
deleted file mode 100644
index 0b1146a..0000000
--- a/components/focaltech/ft3168/README.md
+++ /dev/null
@@ -1,55 +0,0 @@
-# FocalTech FT3168
-
-- **Category:** capacitive touch controller, I²C slave; a self/mutual-capacitance part aimed at
-  small round and rectangular AMOLED panels.
-- **Manufacturer:** FocalTech Systems Co., Ltd.
-- **Retrieved:** 2026-09-07
-- **Sibling record here:** [`ft6336g`](../ft6336g/README.md)
-
-The touch controller of the **LilyGO T-Display-S3 AMOLED 1.64″** and of the **1.43″** round
-board in both of its display-controller variants.
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **FT3168** |
-| Local artifact | [`artifacts/ft3168-datasheet-lilygo-mirror.pdf`](artifacts/ft3168-datasheet-lilygo-mirror.pdf) — 926 072 B, SHA-256 `b8c6079df7e94a539629f6dfaf2686899a29b030d15a76f4a5983dcf84f8685b` |
-| Mirror sources — **two, identical size** | `Xinyuan-LilyGO/T-Display-S3-AMOLED-1.64` → `information/FT3168.pdf` @ `e236a4dfb3295c473d8ac7c240cbea93313707c0` · `Xinyuan-LilyGO/T-Display-S3-AMOLED-1.43-1.75` → same path @ `87aabe888eea6a7c0f95ce1991ca75fa98c2a172`. One copy retained; the second URL is recorded rather than stored twice |
-| Licence | FocalTech copyright. The two mirroring repositories are **GPL-3.0** and **MIT** respectively; neither covers the PDF. **Redistribution status: unknown** |
-
-## 2. Board usage
-
-| Board | Build symbol | Display partner | I²C |
-|---|---|---|---|
-| [1.64″ AMOLED](../../../devices/lilygo/t-display-s3-amoled-1-64/README.md) | — | [CO5300/ICNA3311](../../chipone/co5300/README.md) | pins **not published** for this board |
-| [1.43″ AMOLED](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md) | `DO0143FMST10` | [CO5300](../../chipone/co5300/README.md) | SDA **GPIO7** / SCL **GPIO6**, `TP_INT` **GPIO9** |
-| [1.43″ AMOLED](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md) | `DO0143FAT01` | [SH8601](../../shenghe-microelectronics/sh8601z/README.md) | as above |
-
-The **1.75″** board in the same family uses a **Hynitron CST9217** instead — so the touch
-controller varies with the panel, not with the product name.
-
-> ⚠ **`TP_INT` and `PCF8563_INT` are both GPIO9** in LilyGO's `pin_config.h` @ `87aabe8`.
-> Either the two interrupt lines are wire-ORed (plausible — both are open-drain) or one define
-> is wrong. **Unresolved**, and no schematic is published for these boards to settle it.
-
-## 3. Software
-
-LilyGO ships `examples/FT3168` and `examples/GFX_FT3168_Image` in both repositories. No
-first-party ESPHome component was located. The FocalTech FT6x36/FT3x68 register conventions are
-broadly similar across the family, but **that similarity is not evidence** — read the datasheet
-before assuming a driver written for an FT6336 will work.
-
-## 4. What was not verified
-
-The datasheet was **not read**; no I²C address, register or timing value is transcribed here.
-**The I²C address is therefore unknown in this record.** FocalTech touch parts commonly sit at
-`0x38`, and that is the number a scanner will most likely report — but it is stated here as an
-expectation, not a finding.
-
-## 5. Gaps
-
-- Address, register map, gesture support: unknown.
-- **No pin map at all is published for the 1.64″ board** — no `pin_config.h` and no schematic
-  exist in its repository. That is the largest gap around this part.
-- Not verified on hardware.
diff --git a/components/focaltech/ft3168/artifacts/ft3168-datasheet-lilygo-mirror.pdf b/components/focaltech/ft3168/artifacts/ft3168-datasheet-lilygo-mirror.pdf
deleted file mode 100644
index e54cda9..0000000
Binary files a/components/focaltech/ft3168/artifacts/ft3168-datasheet-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/focaltech/ft6336g/README.md b/components/focaltech/ft6336g/README.md
deleted file mode 100644
index b621856..0000000
--- a/components/focaltech/ft6336g/README.md
+++ /dev/null
@@ -1,285 +0,0 @@
-# FocalTech FT6336G
-
-> Single-chip **self-capacitance touch-panel controller** with a built-in 16-bit enhanced MCU, up to 31 sensor channels, one touch point plus gestures or two touch points, 100 Hz report rate, and an I²C slave interface — for panels up to 4.0 inches.
-> Research snapshot **2026-09-01**. Used on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) at I²C **`0x38`**. **The controller is not on the mainboard** — it lives on the touch panel's flexible circuit and reaches the board through the FPC connector `J4`. **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | FocalTech `FT6336G` datasheet **Version 1.0**, © 2015 — local copy `artifacts/ft6336g-datasheet-v1.0-focuslcds-mirror.pdf` | `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack / M5GFX source at a cited `file:line` | `executed-success` for the read |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`FT6336G`** | **[DOC]**; **[SCH]** by implication (§4) |
-| Manufacturer | **FocalTech Systems Co., Ltd.** (敦泰科技) | **[DS]** |
-| Function | Self-capacitance touch-panel controller with integrated 16-bit MCU | **[DS]** |
-| **Package** | **QFN 5 × 5 mm, 40 pin, 0.6 mm height, 0.4 mm pitch** | **[DS]** §1.1 model table |
-| Sensor channels | **31** | **[DS]** §1.1 |
-| Max panel size | **≤ 4.0 inch** | **[DS]** §1.1 |
-| **I²C address** | **`0x38`** (7-bit) | **[SRC]**, **[DOC]** — ⚠ **not** in the datasheet, see §2.1 |
-| Datasheet | **Version 1.0**, © 2015 FocalTech, 10 numbered pages (12 PDF pages) | **[DS]** page footers |
-
----
-
-## 2. Capabilities and limits **[DS]**
-
-| Parameter | Value |
-|---|---|
-| Sensing technique | **Self-capacitance** |
-| Touch points | **1 point + gestures**, or **2 points** |
-| Output | Absolute X and Y coordinates, or gesture codes |
-| Report rate | **up to 100 Hz** |
-| Scan rate, Active mode | **60 fps default**, host-configurable up or down |
-| Scan rate, Monitor mode | **25 fps default**, host-configurable |
-| Interface | **I²C slave only** — no SPI |
-| **I²C clock** | **10 kHz – 400 kHz** |
-| Analogue supply `VDDA` | **2.8 – 3.6 V** (abs. max −0.3 to +3.6 V) |
-| Digital supply `VDD3` | abs. max −0.3 to +3.6 V |
-| **I/O supply `IOVCC`** | **1.8 – 3.6 V, independent of `VDDA`** |
-| Internal regulator | Generates **1.5 V** for digital circuits from `VDDA` |
-| Input thresholds | V<sub>IH</sub> ≥ 0.7 × `IOVCC`; V<sub>IL</sub> ≤ 0.3 × `IOVCC` |
-| Operating temperature | **−40 to +85 °C** |
-| Storage temperature | −55 to +150 °C |
-| ESD | HBM ≥ 7500 V, MM ≥ 500 V |
-| On-chip memory | 48 KB flash program store, 5 KB SRAM |
-| Master clock | 18 MHz, from a 36 MHz RC oscillator |
-| Auto-calibration | Yes — insensitive to capacitance and environmental variation |
-| Panel construction | Supports single-film TP and triangle pattern **without an additional shield** |
-
-**I²C timing [DS Table 2-2]:** bus-free time between STOP and START ≥ 4.7 µs; (repeated) START hold ≥ 4.0 µs; data setup ≥ 250 ns; repeated-START setup ≥ 4.7 µs; STOP setup ≥ 4.0 µs.
-
-### 2.1 ⚠ The datasheet does not contain the I²C address or the register map
-
-This is the most important thing to know before trying to work from FocalTech's document.
-
-**Version 1.0 of the FT6336G datasheet describes the architecture, the operating modes, the electrical specification, the I²C bus timing and the package — and stops there.** Full-text search finds **no occurrence of `0x38`**, no slave-address value, and no register table. There is no "read touch data from register `0x02`" section.
-
-The address `0x38` and the register semantics come entirely from downstream sources:
-
-| Source | Value | Where |
-|---|---|---|
-| M5GFX touch driver | `ft5x06_i2c_addr = 0x38` | **[SRC]** `M5GFX/src/M5GFX.cpp:575` |
-| M5GFX PaperMono touch config | `_cfg.i2c_addr = 0x38` | **[SRC]** `M5GFX.cpp:713` |
-| M5GFX board bring-up | `touch_addr = 0x38` | **[SRC]** `M5GFX.cpp:329` |
-| M5Stack documentation | `FT6336G(0x38)` | **[DOC]** |
-
-`0x38` is the long-standing family address for FocalTech's FT5x06/FT6x36 line, and M5GFX drives this part through its **FT5x06** code path — the register interface is family-compatible even though the datasheets are separate. **[INF]**
-
-**Practical consequence:** you cannot write an FT6336G driver from the FocalTech datasheet. You need either a register-map application note (FocalTech distributes these separately, and typically under NDA) or an existing open driver. See §5.
-
-### 2.2 Operation modes **[DS §2.3]**
-
-| Mode | Behaviour |
-|---|---|
-| **Active** | Full scanning at 60 fps default. Normal operation |
-| **Monitor** | Reduced 25 fps scan, most algorithms stopped, a simple presence detector runs. **⚠ The serial port is closed and no data transfers with the host in this mode** — it wakes to Active on a touch |
-| **Hibernation** | Power-down. Responds only to `RESET` or a wake-up signal from the host |
-
-> ⚠ **Monitor mode closes the I²C port.** A host that polls the controller while it is in Monitor mode gets nothing, and the correct architecture is interrupt-driven: wait for `/INT`, then read. This is exactly what the PaperMono does (§4.3).
-
-### 2.3 Host interface signals **[DS §2.3]**
-
-| Signal | Direction | Purpose |
-|---|---|---|
-| `SDA` / `SCL` | bidirectional / in | I²C slave interface |
-| **`/INT`** | out | Asserted when touch data is ready for the host to read |
-| **`RSTN`** | in | **Active-low** external reset. After reset the chip enters **Active** mode |
-
-A watchdog timer is implemented internally *"to ensure the robustness of the chip"*. **[DS]**
-
----
-
-## 3. Where it physically is
-
-**Not on the mainboard.** The PaperMono schematic contains no FT6336G symbol on any of its six sheets; sheet 4 has a `TP` block whose entire content is the FPC connector **`J4`**, a level translator and a load switch. The controller is bonded to the touch panel's own flex circuit — the standard construction for a capacitive touch panel.
-
-That has two consequences worth stating:
-
-- **The device record for the panel assembly is the right place for mechanical and optical properties**; this record covers the controller silicon only.
-- **You cannot replace the controller.** It comes with the panel.
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), on the touch FPC reaching connector **`J4`** (sheet 4). The same part is fitted on the **PaperMono-Lite** (C153-Lite), whose specification is identical for touch. **[DOC]**
-
-#### 4.1 Signals at `J4` **[SCH sheet 4]**
-
-`J4` is an 8-way FPC connector. The six signals recovered from the schematic text layer are:
-
-| Signal | Net | Goes to |
-|---|---|---|
-| Touch supply | **`TP_VDD`** | from [`U18` AW35122FDR](../../awinic/aw35122/README.md) load switch, enabled by M5IOE1 **`PYG13`** |
-| I²C clock | **`TP_SYS_SCL`** | A1 of [`U19` AW39112DNR](../../awinic/aw39112/README.md) translator |
-| I²C data | **`TP_SYS_SDA`** | A2 of `U19` |
-| Interrupt | **`G4_TP_INT`** | ESP32-S3 **GPIO4** directly |
-| Reset | **`PYB_TP_RST`** | M5IOE1 **`PYG6`** |
-| Ground | `GND` | |
-
-Passives: `R58` = 10 kΩ (pull-up to `TP_VDD`), `R59` = 1.2 Ω, `C68` = 10 µF/10 V on `TP_VDD`. **[SCH]**
-
-> **The exact pin *numbering* on `J4` was not reliably resolved** from the PDF text layer — the connector's pin markers and net labels interleave in a way the extraction could not separate with confidence. The **signal set** above is solid; the **1-to-8 ordering is not**, and is deliberately not asserted. Read it off the rendered sheet before building a replacement flex.
-
-#### 4.2 The touch bus is isolated, not merely level-shifted
-
-`U19` is an [AW39112DNR](../../awinic/aw39112/README.md) 2-bit translator whose **`VCCA` and `OE` are both `TP_VDD`**, with `VCCB` on `3V3_L2`. **[SCH]**
-
-Since `TP_VDD` is switched by M5IOE1 `PYG13`, **powering down the touch controller automatically removes it from the shared system I²C bus** — `OE` falls with the rail. No firmware step, no forgotten sequence, no possibility of a half-powered slave holding SDA low. This is a deliberate and rather good piece of design; see [AW39112 §4.2](../../awinic/aw39112/README.md#42-u19-sheet-4--the-touch-controller-bus-branch).
-
-It also means: **if you power-cycle `TP_VDD`, you must re-initialise the touch driver.** M5Stack says so explicitly — *"The pins associated with the e-paper display, touch controller, microSD, and PDM microphone are already used by M5Unified. Before modifying them, ensure that the corresponding peripheral has stopped, or the peripheral may stop working or require reinitialization."* **[DOC]**
-
-#### 4.3 `/INT` goes straight to the ESP32-S3 and is a wake source
-
-`G4_TP_INT` reaches **ESP32-S3 GPIO4** with no expander in the path. **[SCH]** In firmware it is both the touch-ready interrupt and a deep-sleep wake source:
-
-- `TOUCH_WAKE_GPIO = 4` — `app_sleep_wake.cpp:52` **[SRC]**
-- `cfg.pin_int = 4` in M5GFX's touch configuration — `M5GFX.cpp:2144` **[SRC]**
-
-Sheet 1's power-state table lists **"TP · Touch-to-wake supported"** under `L2 DeepSleep`. **[SCH]** So the intended low-power behaviour is: system asleep, touch controller in Monitor mode, a finger wakes the controller, the controller asserts `/INT`, `/INT` wakes the ESP32-S3.
-
-Note the ordering that follows from §2.2: **while the system sleeps the controller's I²C port is closed**, so a wake handler must not assume it can read coordinates immediately — the controller transitions to Active on the touch, and the first read must happen after that. **[INF]**
-
-#### 4.4 ⚠ The effective touch area is smaller than the display
-
-M5Stack documents this and it is not obvious from any datasheet:
-
-> *"The touch IC firmware internally shrinks the touch boundary. The effective touch coordinate range is limited to: **X-axis: 5 ~ 475** (total width 480 px), **Y-axis: 5 ~ 795** (total height 800 px)."* **[DOC]**
-
-| Axis | Panel | **Usable touch** | Dead border |
-|---|---|---|---|
-| X | 0 – 479 (480 px) | **5 – 475** (471 px) | 5 px leading, 4 px trailing |
-| Y | 0 – 799 (800 px) | **5 – 795** (791 px) | 5 px leading, 4 px trailing |
-
-**This is a controller-firmware property, not a mechanical one and not something a host can change.** The practical consequences:
-
-- **Do not put a hit target within 5 px of any screen edge.** A button drawn flush to the edge has a strip that cannot be pressed. Edge-swipe gestures that start at coordinate 0 will never register.
-- A host that scales raw coordinates assuming a full 0–479 / 0–799 range introduces a small but systematic offset and a ~2 % scale error. Whether M5GFX compensates was **not** determined.
-- Full-screen "tap anywhere to wake" works fine; corner affordances do not.
-
-#### 4.5 Bus context
-
-The FT6336G shares the system I²C bus (GPIO47 SDA / GPIO48 SCL) with six other devices. Addresses are all distinct — no conflict:
-
-| Device | Address |
-|---|---|
-| **FT6336G touch** | **`0x38`** |
-| RX8130CE RTC | `0x32` |
-| [BMI270](../../bosch-sensortec/bmi270/README.md) IMU | `0x68` (alt `0x69`), **run at 100 kHz** |
-| [M5IOE1](../../m5stack/m5ioe1/README.md) | `0x4F` |
-| ST25R3916 NFC | `0x50` |
-| [M5PM1](../../m5stack/m5pm1/README.md) | `0x6E` |
-| [IP2315](../../injoinic/ip2315/README.md) charger | `0x75` — **gated off the bus** |
-
-Bus pull-ups `R36`, `R37` = 2.2 kΩ to `3V3_L2`. **[SCH]**
-
-> Note the FT6336G's I²C **minimum** clock is 10 kHz (§2) and the BMI270 on the same bus is driven at **100 kHz** while the RTC and NFC run at 400 kHz. **[SRC]** Since bus speed is per-transaction on a shared bus, the touch controller sees whatever rate the current master transaction uses — all of which are inside its 10–400 kHz window.
-
----
-
-## 5. Drivers and libraries
-
-| Option | Notes |
-|---|---|
-| **M5GFX `lgfx::Touch_FT5x06`** | What ships on the PaperMono. `M5GFX.cpp:329`, `:575`, `:713`, `:2144–2146`. Configured with `pin_int = 4`, `i2c_addr = 0x38`, SDA 47 / SCL 48 |
-| **`lvgl/lv_drivers` FT6x06** | Common LVGL touch driver, register-compatible |
-| **Adafruit_FT6206** (Arduino) | Widely used; targets FT6206/FT6236 but the register interface is the same family |
-| **Linux** `drivers/input/touchscreen/edt-ft5x06.c` | Mainline, `compatible = "focaltech,ft6236"` and relatives. The most complete open implementation of the register map |
-| Roll your own | ⚠ **You cannot do this from the FocalTech datasheet** (§2.1). Read the Linux driver instead — it is the de-facto public documentation of the register map |
-
-The register interface these all share: a small register file where `0x00`–`0x01` hold mode/gesture, `0x02` holds the touch count, and each touch point occupies six bytes from `0x03` (X high/low with an event flag in the top bits, Y high/low with a touch ID, weight, area). **[INF]** — this is the FT5x06-family layout implemented by the drivers above, **not** read from `[DS]`.
-
----
-
-## 6. Integration pitfalls, in priority order
-
-1. **The datasheet has no register map or address** (§2.1). Budget for using an existing driver.
-2. **Monitor mode closes the I²C port** (§2.2). Design for interrupt-driven reads, not polling.
-3. **The usable coordinate range is inset by ~5 px on every edge** (§4.4). This is firmware inside the controller; you cannot widen it.
-4. **`IOVCC` is independent of `VDDA`** (§2). On a 3.3 V-only board this is invisible; on a mixed-voltage board it is the pin that makes level shifting unnecessary — and forgetting to power it leaves the chip alive but mute.
-5. **`RSTN` is active-low** and on the PaperMono comes from an I²C expander (§4.1) — so resetting touch requires a working I²C bus, which is awkward if the reason you are resetting is that the bus is unhappy.
-6. **After a `TP_VDD` power cycle the driver must be re-initialised** (§4.2).
-7. **31 channels, ≤ 4.0 inch panel** (§1). The PaperMono's 3.97-inch panel is right at the ceiling.
-8. **Self-capacitance, 2 points maximum.** No pinch-zoom with reliable independent point tracking; self-capacitance sensing suffers the classic two-point "ghosting" ambiguity. **[INF]**
-
----
-
-## 7. Alternatives
-
-| Part | vs. FT6336G | When |
-|---|---|---|
-| FocalTech **FT6236 / FT6206 / FT6436** | Same family, differing channel counts and panel sizes; one shared datasheet covers several | Different panel size in the same ecosystem |
-| **[Hynitron CST816D](../../hynitron/cst816d/README.md)** | Single-point capacitive controller, low cost | Small panels; documented in this repository |
-| **[Goodix GT911](../../goodix/gt911/README.md)** | 5-point mutual-capacitance | When you need real multi-touch |
-| Sitronix, Ilitek touch controllers | Comparable | Panel-vendor-driven choice |
-
-In practice **the controller is chosen by the panel supplier, not by the board designer** (§3). This table is for understanding what you have, not for substituting it.
-
----
-
-## 8. Open questions
-
-- **`J4`'s pin numbering** (§4.1).
-- Whether M5GFX compensates for the 5–475 / 5–795 coordinate inset (§4.4), or passes raw coordinates through.
-- Whether a FocalTech register-map application note for the FT6336G is publicly obtainable; only the datasheet was found, and it does not contain one (§2.1).
-- The panel assembly's own part number — the e-paper module is `DEPG0397BBS770F3HP-XM`, but whether the touch layer is a separate supplier's part is not established.
-- No hardware measurement of report rate, current draw or the actual coordinate boundaries.
-
----
-
-## Manufacturer
-
-**FocalTech Systems Co., Ltd.** No vendor sourcing guide exists in this repository yet.
-
-**⚠ Retrieval finding — record this, it will recur.** FocalTech does not serve this datasheet itself; the copies in circulation are hosted by display module vendors, and **those hosts block ordinary browser User-Agents**:
-
-| Host | Chrome 131 UA | WhatsApp UA | Safari 17 UA | **ClaudeBot UA** |
-|---|---|---|---|---|
-| `www.orientdisplay.com/wp-content/uploads/2022/08/FT6336G_v1.0.pdf` | **403** | 403 | 403 | **403** |
-| `focuslcds.com/wp-content/uploads/Drivers/FT6336G.pdf` | **403** | 403 | 403 | **200, `application/pdf`, `%PDF` ✓** |
-
-The only User-Agent that succeeded was
-`Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ClaudeBot/1.0; +claudebot@anthropic.com`,
-and only on `focuslcds.com`. Both hosts are WordPress sites behind a WAF that appears to allow declared crawlers while blocking generic desktop agents — the opposite of the usual pattern, and worth remembering. This finding belongs in [`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-A third mirror exists — `https://www.buydisplay.com/download/ic/FT6236-FT6336-FT6436L-FT6436_Datasheet.pdf` — covering the FT6236/FT6336/FT6436L/FT6436 as a set. It was **not** retrieved and may contain the register information the single-part datasheet lacks. That is the highest-value untaken lead here.
-
-## Related pages
-
-- [Awinic AW35122](../../awinic/aw35122/README.md) — `U18`, switches `TP_VDD`
-- [Awinic AW39112DNR](../../awinic/aw39112/README.md) — `U19`, the self-isolating bus branch
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — owns `PYG6` (reset) and `PYG13` (power)
-- [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) — the e-paper panel this touch layer sits on
-- [Hynitron CST816D](../../hynitron/cst816d/README.md) — comparable touch controller documented in this repository
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | FT6336G Self-Capacitive Touch Panel Controller datasheet | FocalTech Systems Co., Ltd. | primary (via credible mirror, Focus LCDs) | datasheet | <https://focuslcds.com/wp-content/uploads/Drivers/FT6336G.pdf> | 2026-09-01 | **Version 1.0**, © 2015, 10 numbered pp / 12 PDF pp, 477 869 B | Package `QFN5*5` 40-pin 0.4 mm pitch, 31 channels, ≤4.0 in, supplies, I²C 10–400 kHz and timing, three operating modes, `/INT` and `RSTN` semantics, ESD, on-chip memory | `artifacts/ft6336g-datasheet-v1.0-focuslcds-mirror.pdf` |
-| D2 | FT6236/FT6336/FT6436L/FT6436 combined datasheet | FocalTech (via Buydisplay) | credible mirror | datasheet | <https://www.buydisplay.com/download/ic/FT6236-FT6336-FT6436L-FT6436_Datasheet.pdf> | **not retrieved** | — | Possible source of the missing register map (§2.1) | — |
-| S1 | PaperMono product page — touch active area | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | The X 5–475 / Y 5–795 coordinate inset; `FT6336G(0x38)`; the M5Unified pin-ownership warning | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono.html` |
-| S2 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `J4` signal set, `U18`/`U19` topology, `G4_TP_INT` → GPIO4, `R58`/`R59`/`C68` | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S3 | `M5GFX/src/M5GFX.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5GFX> | 2026-09-01 | `master` @ `d91077b9a607b59404e4e4a49f775c792bfae382`, MIT | `0x38` at `:329`, `:575`, `:713`; `pin_int = 4` at `:2144`; SDA/SCL 47/48 at `:2145–2146` | `scratch/m5stack-papermono/repos/M5GFX/` |
-| S4 | `M5PaperMono-UserDemo/main/apps/app_sleep_wake/app_sleep_wake.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | `main` @ `c1099107271d31a0678d661a896e2b04dbb331ea`, MIT | `TOUCH_WAKE_GPIO = 4` (`:52`), `IOE1_TOUCH_RST_PIN = M5IOE1_PIN_6` (`:76`), `IOE1_TOUCH_EN_PIN = M5IOE1_PIN_13` (`:81`) | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/ft6336g-datasheet-v1.0-focuslcds-mirror.pdf` | 477 869 | `766f130b65d3e4e30ba7c3a2592a33b61b11fcdd3a39a239333acc53a1b7d793` | 12 |
-
-**Method note.** D1 validated as `%PDF` with an intact text layer, and full-text searched for `0x38` and for register tables — both absent, which is the §2.1 finding. Four User-Agents were tried across two hosts before one succeeded; see [Manufacturer](#manufacturer).
diff --git a/components/focaltech/ft6336g/artifacts/ft6336g-datasheet-v1.0-focuslcds-mirror.pdf b/components/focaltech/ft6336g/artifacts/ft6336g-datasheet-v1.0-focuslcds-mirror.pdf
deleted file mode 100644
index 2105595..0000000
Binary files a/components/focaltech/ft6336g/artifacts/ft6336g-datasheet-v1.0-focuslcds-mirror.pdf and /dev/null differ
diff --git a/components/galaxycore/gc2093/README.md b/components/galaxycore/gc2093/README.md
deleted file mode 100644
index 2896460..0000000
--- a/components/galaxycore/gc2093/README.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# GalaxyCore GC2093 — 1/2.9″ 2 MP MIPI CSI-2 CMOS image sensor
-
-- **Category:** CMOS image sensor, MIPI CSI-2, rolling shutter
-- **Manufacturer:** **GalaxyCore Inc.** (格科微电子). The `GC` prefix is GalaxyCore's; no public GC2093 datasheet was located on 2026-09-04, so the attribution rests on the family prefix and on the sensor's ubiquity in Chinese IPC/AIoT designs.
-- **Research status:** primary evidence is a **26 213-byte vendor V4L2 sensor driver** (`vvcam/src/gc2093.c`) shipped in the LilyGO BSP, plus vendor product copy.
-- **Retrieved:** 2026-09-04
-
-## 1. Known properties
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **GC2093** | S1, S2 |
-| Resolution | **2 MP, 1080p** | S1 |
-| Interface | **MIPI CSI-2** | S2 |
-| Control bus | I²C, 7-bit address **`0x37`** | S2 |
-| Linux/ISP integration | Canaan **`vvcam`** (VeriSilicon ISP V4L2 stack); `BR2_PACKAGE_VVCAM_DEF_SENSOR="gc2093"` | S3 |
-| Driver source | `k230_bsp/overlay/buildroot-overlay/package/vvcam/src/gc2093.c`, 26 213 bytes | S3 |
-| DT integration | `0036-add-gc2093-camera.patch` | S3 |
-
-`0x37` is a notable address: it is *not* the more common `0x3C`/`0x36` used by many sensors,
-and it collides with nothing else on this board because the camera sits on its own I²C bus
-(`GPIO48/49`, I²C0) rather than the shared expansion bus.
-
-## 2. Integration notes
-
-The sensor is wired through Canaan's `vvcam` ISP driver rather than a plain V4L2 subdev, so
-the useful configuration surface is the **ISP tuning** path, not the sensor driver: Canaan
-publishes `K230_ISP_Image_Tuning_Guide` and `K230_ISP_Initial_Setting_Guide`, and
-`K230_Image_Capture_Practice_How_to_support_a_new_sensor` is the document to read before
-swapping the sensor. `K230_VICAP_SENSOR_Parameter_Partition_Reference` documents where sensor
-parameters live in flash/partition terms.
-
-The K230 supports **three** MIPI CSI inputs; only one is populated on the LilyGO board, so two
-CSI interfaces are available on the expansion header for additional sensors. Canaan's own
-reference DTS also mentions `OV5647` and the BSP tree mentions `IMX219`, which are the two
-sensors most likely to work with modest effort.
-
-## 3. Unknowns
-
-- Pixel size, optical format, frame-rate/exposure limits, HDR/WDR mode support, lane count and
-  link rate: **all unknown from primary sources.** The driver contains the register writes but
-  those were not decoded against a datasheet in this pass, because no datasheet was available
-  to decode them against. This is a deliberate gap, not an oversight — see
-  [gaps-and-conflicts.md](../../../devices/lilygo/t-display-k230/gaps-and-conflicts.md) `GC-6`.
-- Lens/module vendor: unknown.
-
-## 4. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-The single fitted camera. I²C0 on **`GPIO49` SDA / `GPIO48` SCL** at **`0x37`**, image data over
-MIPI CSI. Exercised by the launcher's camera preview, still capture, RTSP push, QR scan
-(`qr_scan.c`), face detection (`camera_face_detect.cpp`) and motion probe apps.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | T-Display K230 Kit product page | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230-kit` | 2026-09-04 | "Camera: 2MP 1080P, Module: GC2093" |
-| S2 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | I²C address `0x37`, GPIO48/49, MIPI CSI |
-| S3 | `vvcam/src/gc2093.c`, `0036-add-gc2093-camera.patch`, `k230_canmv_t_display_rm69a10_defconfig` | LILYGO | primary | source | same repo | 2026-09-04 | Driver existence and size, default sensor selection |
diff --git a/components/generic/100k-rntc-thermistor/README.md b/components/generic/100k-rntc-thermistor/README.md
deleted file mode 100644
index c2ef598..0000000
--- a/components/generic/100k-rntc-thermistor/README.md
+++ /dev/null
@@ -1,299 +0,0 @@
-# 100K-RNTC — charger temperature thermistor (part **unidentified**)
-
-> **100 kΩ NTC thermistor**, fitted as **`R15` on sheet 2** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153). It is the temperature-qualification sensor for the [IP2315](../../injoinic/ip2315/README.md) battery charger — the part that is supposed to stop charging when it is too hot or too cold.
-> Research snapshot **2026-09-01**. **Safety-relevant, and it carries a finding that contradicts other records in this repository:** [§4](#4--conflict-this-does-not-measure-the-cell).
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH-V]** | Read off sheet 2 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[IP]** | Injoinic IP2315 datasheet, held under the [IP2315 record](../../injoinic/ip2315/README.md) | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Value string on the schematic | **`100K-RNTC`** | **[SCH-V]** |
-| Reference designator | **`R15`**, sheet 2 | **[SCH-V]** |
-| Function | **Negative-temperature-coefficient thermistor**, nominal **100 kΩ at 25 °C** | **[SCH-V]**, **[IP]** |
-| Manufacturer | **unidentified** | — |
-| Part number | **unidentified** | — |
-| **B constant** | **not stated on the schematic**; the IP2315 datasheet's worked example uses **B = 4100** | **[IP]** |
-| Package / case size | **not stated anywhere in the PDF** | — |
-| Tolerance | **not stated** — every other resistor on the sheet is printed `/1%`; this one is not | **[SCH-V]** |
-
-### 1.1 ⚠ `100K-RNTC` is a description, not a part number
-
-It says: a **100 k**Ω **R**esistor that is an **NTC**. Nothing more. It names no
-manufacturer, no series, no B constant, no tolerance and no package.
-
-**No part number is guessed here.** For a component whose whole job is a safety
-interlock, that gap is worth stating loudly rather than papering over.
-
-**What would resolve it:**
-
-1. **M5Stack's manufacturing BOM** — the only source that would give a series and
-   a B constant directly.
-2. **The B constant is the missing number that actually matters** (§3). If a
-   board is available, it can be measured: read the resistance at two known
-   temperatures and solve for B.
-3. A photograph of the board would give the case size but almost certainly not a
-   part number — NTC chips are rarely marked.
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — `R15`, sheet 2
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-**One instance.**
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes**. The Lite drops only NFC and LoRa; the
-[compatibility record](../../../devices/m5stack/papermono/compatibility-and-status.md)
-states the charging arrangement and the 1150 mAh cell are identical on both SKUs.
-Not read from the Lite's own schematic.
-
-### 2.1 The sensing arrangement **[SCH-V]**
-
-Read from a 200 dpi render of sheet 2. Four resistors sit in a row beneath the
-IP2315's `LED3`, `ICHGSET` and `NTC` pins:
-
-```
-   IP2315 (U1, sheet 2)
-   pin 10  LED3 ──────────────────────────┬─────── "NC" net label
-   pin 27  ICHGSET ─────────────┬         │
-   pin 26  NTC ──┬──────────┐   │         │
-                 │          │   │         │
-              R15 │       R16 │ R17 │   R18 │
-           100K-RNTC     82 kΩ   15 kΩ   NC/1%
-              (NTC)       1 %     1 %   not fitted
-                 │          │      │       │
-                 └──────────┴──────┴───────┴──── GND
-```
-
-| Ref | Value | From | To |
-|---|---|---|---|
-| **`R15`** | **`100K-RNTC`** | **`NTC` (pin 26)** | GND |
-| **`R16`** | **82 kΩ / 1 %** | **`NTC` (pin 26)** — the same node | GND |
-| `R17` | **15 kΩ / 1 %** | `ICHGSET` (pin 27) | GND |
-| `R18` | `NC/1%` | `LED3` (pin 10) | GND — **not fitted** |
-
-So **`R15` and `R16` are in parallel from the `NTC` pin to ground.** The IP2315
-biases that pin internally and reads the resulting voltage.
-
-`R16` = 82 kΩ in parallel is a **linearising resistor**: an NTC's resistance is
-exponential in temperature, and a fixed parallel resistor flattens the curve over
-the band of interest, trading sensitivity at the extremes for a more nearly
-linear response across the charge-permitted window. **[INF]**
-
-**This reproduces the IP2315 datasheet's own worked example verbatim** —
-*"R<sub>NTC</sub> = 100 kΩ @ 25 °C (B = 4100), R2 = 82 kΩ"* **[IP]** — which is
-strong evidence that M5Stack copied the reference design, and therefore that
-**B = 4100** is the intended constant. It is `inferred`, not read from the
-schematic.
-
-### 2.2 What the charger does with it **[IP]**
-
-The [IP2315 record](../../injoinic/ip2315/README.md) establishes that normal
-charging is permitted between roughly **0 °C and 55 °C**, and the charger
-suspends or reduces charging outside that window. That is the standard JEITA-style
-temperature qualification and it is the whole reason this component exists.
-
-### 2.3 A related resolution, from the same render
-
-The same image settles a question the
-[IP2315 record left open](../../injoinic/ip2315/README.md#4-2--the-ntc-and-ichgset-network):
-it could not tell from the PDF text layer **which of `R17`/`R18` reaches
-`ICHGSET`**.
-
-**Answer: `R17` = 15 kΩ is on `ICHGSET`; `R18` = `NC` is on `LED3` and is not
-fitted.** **[SCH-V]**
-
-The conflict that record raises therefore stands and is now sharper: **15 kΩ is
-not one of the four values the IP2315 datasheet tabulates for `ICHGSET`**
-(51 k / 130 k / 180 k / NC), so the programmed charge current cannot be read off
-the datasheet table at all. Sheet 1 annotates the charge current as
-**`充电电流 0.5C`** ("charge current 0.5 C") — ≈ 575 mA for the 1150 mAh cell.
-**[SCH-V]**
-
----
-
-## 3. ⚠ The B constant is unknown, and that is the safety-relevant gap
-
-An NTC is characterised by **two** numbers: its resistance at 25 °C, and its
-**B constant** (the exponent governing how fast resistance falls with
-temperature). The schematic gives the first and not the second.
-
-**Fitting a 100 kΩ NTC with the wrong B constant produces a thermistor that reads
-the right value at 25 °C and the wrong value everywhere else** — and "everywhere
-else" is precisely the region the interlock exists to detect.
-
-Worked illustration, at the trip points that matter:
-
-| B | R at 0 °C | R at 55 °C | R at 60 °C |
-|---:|---:|---:|---:|
-| **3435** | ~330 kΩ | ~23 kΩ | ~20 kΩ |
-| **4100** *(the reference-design value)* | ~380 kΩ | ~20 kΩ | ~17 kΩ |
-| **4250** | ~395 kΩ | ~19 kΩ | ~16 kΩ |
-
-**[INF]** — computed from the standard Beta relation
-`R(T) = R25 · exp(B · (1/T − 1/298.15))`, not read from any datasheet.
-
-A B = 3435 part substituted for a B = 4100 one reads about **20 kΩ at 55 °C where
-the charger expects 20 kΩ at 60 °C** — i.e. it would **let charging continue
-several degrees hotter than intended**. That is the wrong direction for a safety
-device.
-
-**Practical rules:**
-
-- **Never substitute an NTC by its 25 °C value alone.** Match B as well.
-- If this board is ever repaired, **use a 100 kΩ NTC with B = 4100** unless the
-  real value is established, because that is what the charger's reference design
-  assumes.
-- Because both trip points are determined by the *combination* of `R15`, `R16`
-  and the IP2315's internal thresholds, changing any one of them moves both
-  limits.
-
----
-
-## 4. ⚠ Conflict: this does **not** measure the cell
-
-**This is the most consequential finding in this record, and it contradicts
-wording elsewhere in this repository.**
-
-Several places in the PaperMono record describe the battery as **"NTC-sensed"**
-and place the thermistor **at the battery connector `J2`**:
-
-| Where | Wording |
-|---|---|
-| [`README.md`](../../../devices/m5stack/papermono/README.md) | "Battery \| 1150 mAh Li-ion, **NTC-sensed**" |
-| [`features/battery-and-charging.md`](../../../devices/m5stack/papermono/features/battery-and-charging.md) | "battery (**J2**, 1150 mAh **+ 100K NTC**)"; "Cell \| 1150 mAh Li-ion **at `J2`**, `100K-RNTC` thermistor" |
-| [`pinouts-and-buses.md`](../../../devices/m5stack/papermono/pinouts-and-buses.md) | "`J2` … Battery, **with a `100K-RNTC` thermistor**" |
-
-**The schematic does not support the thermistor being in the battery pack.**
-
-| Claim | Evidence **[SCH-V]** |
-|---|---|
-| **`J2` has two pins only** | Rendered at 200 dpi, `J2` is a 2-contact symbol: pin 2 → `VBAT_L0`, pin 1 → GND, with `CON2_SMD` printed beneath as the footprint name and `C13` = 22 µF/10 V across it. **There is no third contact and no thermistor pin** |
-| **`R15` is a mainboard part** | It carries a designator in sheet 2's `R` series, is placed beside the IP2315, and connects `NTC` (pin 26) to GND in parallel with `R16` (§2.1) |
-
-So the arrangement is **a 100 kΩ NTC soldered to the mainboard on the charger's
-`NTC` pin** — not a thermistor inside the cell reaching the board through the
-connector.
-
-**Two consequences, both `inferred`, both safety-relevant:**
-
-1. **What is measured is board temperature near the charger, not cell
-   temperature.** The two track loosely, and they diverge exactly when it
-   matters — a cell entering thermal runaway heats far faster than the PCB
-   beneath it, and the interlock would respond late or not at all. Conversely a
-   warm charger IC could inhibit charging while the cell is fine.
-2. **A replacement cell needs no thermistor.** Fitting a 3-wire pack would not
-   improve the protection, because there is nowhere for the third wire to go.
-
-**This conflict is recorded, not resolved.** It is entirely possible that M5Stack
-places `R15` physically beneath or beside the cell so that it is thermally
-coupled to it — that is a common and legitimate design when a pack has no NTC,
-and nothing in a schematic can show it. **A board photograph or a thermal
-measurement would settle it, and neither was available.**
-
-**Suggested reading of the existing wording**, pending that: *"the charger has
-NTC-based temperature qualification"* — which is true — rather than *"the battery
-pack contains a thermistor"* — which this evidence does not support. Date
-2026-09-01. Per the
-[conflict protocol](../../../.agents/skills/hardware-device-research/SKILL.md),
-the other records are **not** edited by this pass; they are linked and the
-disagreement is stated.
-
-See also the [battery record](../papermono-1150mah-liion-cell/README.md#5--the-thermistor-is-not-in-the-pack)
-and the
-[BOM §11](../../../devices/m5stack/papermono/bill-of-materials.md#11--conflict-raised-by-this-pass--the-ntc-does-not-measure-the-cell).
-
----
-
-## 5. Substitution
-
-| Requirement | Value |
-|---|---|
-| R at 25 °C | **100 kΩ** |
-| **B constant** | **4100** (the IP2315 reference-design value) — §3 |
-| Tolerance | unstated on the schematic; ±1 % B-tolerance parts are standard for charger sensing |
-| Package | unstated; 0402 or 0603 chip NTC is the norm |
-
-Widely available equivalents: Murata `NCP15XH103F03RC` (B = 3380 — **wrong B**),
-`NCP15WB473` (47 kΩ), Vishay `NTCS0402E3104FXT` (100 kΩ, B = 4100 — **matches**),
-Murata `NCU15XH103F6SRC`, TDK `NTCG103` series. **Check B, not just 100 kΩ.**
-
----
-
-## 6. Integration pitfalls
-
-1. **It is not a resistor.** A rework that fits an ordinary 100 kΩ chip resistor
-   in `R15` produces a charger that believes the temperature is permanently 25 °C
-   — i.e. **a silently disabled safety interlock**. Nothing in firmware would
-   report it.
-2. **B is unknown** (§3) and matters more than the nominal value.
-3. **It probably does not measure the cell** (§4).
-4. **`R15` and `R16` set the trip points jointly** (§2.1) — do not change one.
-5. **The tolerance is not printed** while every neighbouring resistor's is
-   (§1) — so the fitted grade is unknown.
-6. **`R17` = 15 kΩ on `ICHGSET` is not a tabulated value** (§2.3), so the actual
-   charge current cannot be derived from the datasheet either. Two of the
-   charger's three programming resistors are therefore not fully understood.
-
----
-
-## 7. Open questions
-
-- **Manufacturer, part number, B constant, tolerance, package** (§1.1, §3).
-- **Whether `R15` is thermally coupled to the cell** (§4) — the blocking question,
-  answerable only with a board.
-- What charge current 15 kΩ on `ICHGSET` actually programs (§2.3).
-- The IP2315's internal `NTC` bias arrangement (current source? divider from an
-  internal reference?), which determines how `R15`∥`R16` maps to a voltage. Not
-  read from **[IP]** for this record.
-- No measurement of anything.
-
----
-
-## Manufacturer
-
-**Unidentified** (§1.1). No vendor sourcing guide applies. **No search was made
-for a part number**, because the schematic string carries no vendor-specific token
-to search on — `100K-RNTC` would match every 100 kΩ NTC ever made. This is a
-deliberate non-attempt rather than a failed one: the resolution path is a BOM or a
-measurement (§1.1), not a catalogue query.
-
-## Related pages
-
-- [Injoinic IP2315](../../injoinic/ip2315/README.md) — **the charger that reads this thermistor**, and whose `R17`/`R18` question §2.3 answers
-- [1150 mAh Li-ion cell](../papermono-1150mah-liion-cell/README.md) — what is *not* being measured (§4)
-- [PaperMono battery and charging feature guide](../../../devices/m5stack/papermono/features/battery-and-charging.md)
-- [PaperMono bill of materials §11](../../../devices/m5stack/papermono/bill-of-materials.md#11--conflict-raised-by-this-pass--the-ntc-does-not-measure-the-cell)
-- [PaperMono power architecture](../../../devices/m5stack/papermono/power-architecture.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `R15` = `100K-RNTC` on IP2315 pin 26; `R16` = 82 kΩ in parallel; **`R17` = 15 kΩ on `ICHGSET`, `R18` = `NC` on `LED3`**; **`J2` is 2-pin**; the `充电电流 0.5C` annotation | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| D1 | IP2315 datasheet | Injoinic | primary | see the [IP2315 record](../../injoinic/ip2315/README.md#manufacturer) | 2026-09-01 | V1.0 (cn), 16 pp | the `R_NTC = 100 kΩ @ 25 °C (B = 4100), R2 = 82 kΩ` worked example; the ~0–55 °C charge window; the `ICHGSET` value table | `../../injoinic/ip2315/artifacts/` |
-
-**Local artifacts** — **none.** The part is unidentified (§1.1); there is no
-document to hold. The circuit evidence lives in the schematic, which is held under
-the device record.
-
-**Method note.** Everything in §2.1 and §4 was read from a **200 dpi PNG render**
-of schematic sheet 2, cropped to the `R15`–`R18` block and to `J2` respectively.
-The text layer in the `R15`–`R18` region places all four values and all three pin
-names in one horizontal band and cannot attribute them; an earlier text-only pass
-left the `R17`/`R18` question open for exactly that reason.
diff --git a/components/generic/1n4148ws/README.md b/components/generic/1n4148ws/README.md
deleted file mode 100644
index edb52cf..0000000
--- a/components/generic/1n4148ws/README.md
+++ /dev/null
@@ -1,211 +0,0 @@
-# 1N4148WS — small-signal switching diode (maker **not specified by the schematic**)
-
-> **The industry-standard 100 V / 150 mA fast switching diode**, 4 ns reverse recovery, in **SOD-323**.
-> Research snapshot **2026-09-01**. Fitted as **`D3` on sheet 4** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — the **flyback clamp across the buzzer**. One instance.
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Jiangsu Changjing `1N4148WS` datasheet, local copy `artifacts/1n4148ws-changjing-lcsc-mirror.pdf` | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entries `C2128`, `C57759`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 4 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Value string on the schematic | **`1N4148WS`** | **[SCH-V]** |
-| Manufacturer | **not specified** — §1.1 | — |
-| Function | Fast small-signal switching diode | **[DS]** |
-| Package | **SOD-323** | **[DS]** |
-| V<sub>R</sub> | **100 V** (Changjing) / **75 V** (ST) — §1.1 | **[CAT]** |
-| I<sub>F</sub> continuous | **150 mA** | **[CAT]** |
-| I<sub>FSM</sub> | **2 A** (Changjing) / 350 mA (ST) | **[CAT]** |
-| V<sub>F</sub> | 1.25 V @ 150 mA | **[CAT]** |
-| I<sub>R</sub> | 1 µA @ 75 V | **[CAT]** |
-| P<sub>D</sub> | 200 mW | **[CAT]** |
-| **t<sub>rr</sub>** | **4 ns** | **[CAT]** |
-
-### 1.1 `1N4148WS` is a JEDEC type, not a vendor part
-
-`1N4148` is one of the oldest and most widely second-sourced part numbers in
-electronics; `WS` denotes the SOD-323 package. **Dozens of makers produce it**,
-and the schematic prints only the type number. LCSC alone lists at least two:
-
-| Maker | LCSC | V<sub>R</sub> | I<sub>FSM</sub> |
-|---|---|---|---|
-| **Jiangsu Changjing** | `C2128` | **100 V** | **2 A** |
-| ST (Semtech) | `C57759` | 75 V | 350 mA |
-
-**[CAT]**
-
-The Changjing part is held here as the representative datasheet, on the reasoning
-that **M5Stack demonstrably buys Changjing discretes for this board** — the same
-sheet carries [`CJ2310`](../../changjing/cj2310/README.md) and sheet 2 carries
-[`CJ3439KDW`](../../changjing/cj3439kdw/README.md). **That is a plausibility
-argument, not an identification, and no maker is asserted.** What would resolve
-it: the top marking on an assembled board, or M5Stack's BOM.
-
-The spread matters a little: **75 V vs 100 V** of reverse rating and **350 mA vs
-2 A** of surge. Both are far beyond what this circuit needs (§2.1), so the
-ambiguity has no practical consequence *here* — but it would if the part were
-reused somewhere more demanding.
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — `D3`, sheet 4
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-**One instance**, and it is the board's only `1N4148`-type part; the three
-Schottkys in the e-paper bias converter are
-[`1N5819WS`](../1n5819ws/README.md) and the frontlight rectifier is a
-[ROHM part](../../rohm/rb162vam-20tr/README.md).
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes** — the Lite retains the buzzer, and differs only in dropping
-NFC and LoRa. Not read from the Lite's own schematic.
-
-### 2.1 Circuit role — the buzzer flyback clamp **[SCH-V]**
-
-```
-              3V3_L1
-                 │
-          ┌──────┴──────┐
-          │   BUZZER1   │   "ER103", magnetic buzzer
-          │   +      −  │
-          └───┬──────┬──┘
-              │      │
-       cathode│      │
-             D3      │       1N4148WS, across the buzzer
-        anode │      │
-              └──────┤
-                     │
-                Q3 drain (SK2302AAT, N-channel)
-                Q3 gate ── G42_BB_PWM   (R50 10 kΩ pulldown)
-                Q3 source ── GND
-```
-
-| `D3` terminal | Net |
-|---|---|
-| **anode** | `Q3`'s **drain** — the buzzer's `−` terminal |
-| **cathode** | the buzzer's `+` terminal, i.e. **`3V3_L1`** |
-
-A magnetic buzzer is an inductive load. When
-[`Q3`](../sk2302aat/README.md) turns off, the coil's current must keep flowing;
-without a path it develops whatever voltage is needed to find one, which on a
-20 V MOSFET is an avalanche event on every cycle. `D3` gives that current a path
-back into the supply, clamping the drain to about **`3V3_L1` + 0.8 V ≈ 4.1 V**.
-
-**This is why the part is a `1N4148` and not a Schottky.** The recovery speed
-(4 ns) matters more than the forward drop, because the diode conducts once per
-PWM edge; and the drop itself is *desirable* here — a higher clamp voltage
-collapses the coil current faster, which makes the buzzer louder for a given
-drive. A Schottky would clamp lower and damp the tone. **[INF]**
-
-### 2.2 Operating conditions — de-rated to the point of irrelevance
-
-| Parameter | Rating | On this board | Margin |
-|---|---|---|---|
-| V<sub>R</sub> | 75–100 V | ≤ 3.3 V | **≥ 22×** |
-| I<sub>F</sub> | 150 mA | a small magnetic buzzer's coil current, tens of mA | comfortable |
-| I<sub>FSM</sub> | 0.35–2 A | the flyback pulse, ≈ the coil's peak current | comfortable |
-| P<sub>D</sub> | 200 mW | ≈ V<sub>F</sub> × I × duty, a few mW | ≫ |
-
-The part is chosen for ubiquity and cost, not for its ratings. That is the
-correct engineering call.
-
----
-
-## 3. Notes for firmware
-
-- **The buzzer runs from `3V3_L1`**, not from the main `3V3_L2` system rail. Its
-  availability is tied to the `L1` domain being enabled — see
-  [`power-architecture.md`](../../../devices/m5stack/papermono/power-architecture.md).
-- **`G42_BB_PWM` is ESP32-S3 GPIO42**, with `R50` = 10 kΩ holding `Q3` off during
-  reset. The buzzer should be silent until firmware drives it.
-- **The buzzer symbol carries an explicit red ✗ no-connect** on one terminal —
-  a positive assertion by the designer, not an omission. **[SCH-V]**
-- The buzzer's own part, **`ER103`, is unidentified**, so its resonant frequency
-  is unknown. Driving a magnetic buzzer off resonance is dramatically quieter;
-  finding the right frequency will be empirical.
-
----
-
-## 4. Substitution
-
-Any `1N4148W`-family part in SOD-323 works. `1N4148WS`, `1N4148W` (SOD-123),
-`LL4148` (MiniMELF), `BAV70`/`BAV99` (dual, SOT-23) are all the same junction in
-different bodies.
-
-**Do not substitute a Schottky** (`BAT54`, `1N5819`) without thinking: it will
-work as a clamp, but it lowers the clamp voltage and changes the buzzer's
-acoustic output (§2.1).
-
----
-
-## 5. Open questions
-
-- **The maker actually fitted** (§1.1).
-- The buzzer `ER103`'s identity, coil inductance and resonant frequency — the
-  determinant of both the flyback energy and the drive strategy.
-- Whether firmware drives GPIO42 as a fixed square wave or a variable-duty PWM.
-- No measurement of anything.
-
----
-
-## Manufacturer
-
-**Not specified by the schematic** (§1.1). The retained datasheet is Jiangsu
-Changjing's; see the [CJ2310](../../changjing/cj2310/README.md#manufacturer) and
-[CJ3439KDW](../../changjing/cj3439kdw/README.md#manufacturer) records for that
-vendor's document-sourcing notes.
-
-**⚠ Retrieval finding — the LCSC PDF host trap.** LCSC's catalogue gave
-`https://www.lcsc.com/datasheet/lcsc_datasheet_1810101110_…1N4148WS_C2128.pdf`,
-which returned **HTTP 200 and 67 606 bytes of HTML** to all five user-agents
-tried. The CDN rewrite worked first try:
-
-```
-wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/1810101110_Jiangsu-Changjing-Electronics-Technology-Co---Ltd--1N4148WS_C2128.pdf
-```
-
-**Check the `%PDF` magic bytes; the status code and the `.pdf` extension both
-lie.** `executed-success`, 2026-09-01, reproduced across five parts from this
-board. This belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## Related pages
-
-- [Shikues SK2302AAT](../sk2302aat/README.md) — **`Q3`, the buzzer driver `D3` protects**
-- [1N5819WS](../1n5819ws/README.md) — the board's Schottky, three instances, e-paper bias
-- [ROHM RB162VAM-20TR](../../rohm/rb162vam-20tr/README.md) — the board's other rectifier
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md) · [power architecture](../../../devices/m5stack/papermono/power-architecture.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `1N4148WS` switching diode datasheet | Jiangsu Changjing (via LCSC CDN) | representative primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/1810101110_Jiangsu-Changjing-Electronics-Technology-Co---Ltd--1N4148WS_C2128.pdf> | 2026-09-01 | undated, 2 pp | SOD-323, 100 V, 150 mA, 4 ns — **for the Changjing part, which is not confirmed to be the fitted one** (§1.1) | `artifacts/1n4148ws-changjing-lcsc-mirror.pdf` |
-| C1 | LCSC entries `C2128`, `C57759` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `1N4148WS` | 2026-09-01 | — | the §1.1 multi-vendor spread; V<sub>F</sub>, I<sub>R</sub>, P<sub>D</sub>, t<sub>rr</sub> | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `D3` = `1N4148WS`; the §2.1 orientation and topology; `3V3_L1` supply; `R50` = 10 kΩ; the no-connect marker | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/1n4148ws-changjing-lcsc-mirror.pdf` | 774 532 | `59e951bd3155eb4a94e958d10edc3b7d17325f38cf06784cac07fbcc9fcabf2e` | 2 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`). The **diode's
-orientation** in §2.1 — which is the entire content of this record, since the part
-itself is a commodity — is legible only from a rendered page image; the text layer
-places `D3`, `Q3`, `BUZZER1` and `C58` labels in one cluster and cannot resolve
-which terminal is which.
diff --git a/components/generic/1n4148ws/artifacts/1n4148ws-changjing-lcsc-mirror.pdf b/components/generic/1n4148ws/artifacts/1n4148ws-changjing-lcsc-mirror.pdf
deleted file mode 100644
index 5e711e6..0000000
Binary files a/components/generic/1n4148ws/artifacts/1n4148ws-changjing-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/generic/1n5819ws/README.md b/components/generic/1n5819ws/README.md
deleted file mode 100644
index e18c311..0000000
--- a/components/generic/1n5819ws/README.md
+++ /dev/null
@@ -1,259 +0,0 @@
-# 1N5819WS — Schottky rectifier (maker **not specified by the schematic**)
-
-> **40 V / 1 A Schottky barrier diode**, V<sub>F</sub> ≈ 0.6 V @ 1 A, 25 A surge, in **SOD-323**.
-> Research snapshot **2026-09-01**. Used **three times** on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — `D4`, `D5` and `D6` on sheet 4 — all three inside the **e-paper panel's bias generator**, the highest-voltage circuit on the board.
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | `1N5817WS – 1N5819WS` datasheet (Guangdong Hottech), local copy `artifacts/1n5819ws-guangdong-hottech-lcsc-mirror.pdf` | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entries `C191023`, `C369937`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 4 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[MAN]** | DKE **EPD Module User Manual** §7.4, held under the [panel record](../../dke/depg0397bbs770f3/README.md) | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and ratings
-
-| Property | Value | Evidence |
-|---|---|---|
-| Value string on the schematic | **`1N5819WS`** | **[SCH-V]** |
-| Manufacturer | **not specified** — §1.1 | — |
-| Function | Schottky barrier rectifier | **[DS]** |
-| Package | **SOD-323** (Hottech) or **SOD-323F** (KEXIN) — §1.1 | **[CAT]** |
-| Case material | moulded plastic, UL94V-0 | **[DS]** |
-| Weight | ≈ 0.005 g | **[DS]** |
-| **V<sub>RRM</sub>** | **40 V** | **[DS]** |
-| I<sub>O</sub> | **1 A** | **[CAT]** |
-| I<sub>FSM</sub> | **25 A** | **[CAT]** |
-| **V<sub>F</sub>** | **600 mV @ 1 A** | **[CAT]** |
-| I<sub>R</sub> | 500 µA @ 40 V (Hottech) / 1 mA @ 40 V (KEXIN) | **[CAT]** |
-| Vendor applications | *"low voltage high frequency inverters and polarity protection"* | **[DS]** |
-
-The datasheet is a **family document covering `1N5817WS` (20 V), `1N5818WS`
-(30 V) and `1N5819WS` (40 V)** — the same die at three reverse ratings. Reading
-the wrong column is the obvious hazard; **40 V is the `1N5819WS` column.**
-**[DS]**
-
-### 1.1 `1N5819WS` is a JEDEC type, not a vendor part
-
-Like the [`1N4148WS`](../1n4148ws/README.md) on the same sheet, this is a
-second-sourced industry type and the schematic prints only the type number. LCSC
-lists at least:
-
-| Maker | LCSC | Package | I<sub>R</sub> @ 40 V |
-|---|---|---|---|
-| **Guangdong Hottech** | `C191023` | **SOD-323** | 500 µA |
-| KEXIN | `C369937` | **SOD-323F** | 1 mA |
-
-**[CAT]**
-
-**Note the package difference.** SOD-323 and SOD-323**F** are *not* the same
-footprint — the `F` variant is a flat-lead version with a different land pattern.
-That matters for a rework or a respin far more than the leakage spread does. **No
-maker is asserted here**; the Hottech document is retained as representative
-because its package matches the plain `SOD-323` that the type number implies.
-What would resolve it: the top marking on a board, or M5Stack's BOM.
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — **3 instances**, all sheet 4
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-
-| Ref | Role in the e-paper bias generator |
-|---|---|
-| **`D4`** | **boost rectifier** — switch node → `PREVGH` |
-| **`D5`** | **charge-pump rectifier** — `PREVGL` → the flying-capacitor node |
-| **`D6`** | **charge-pump clamp** — flying-capacitor node → GND |
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes, all three**. Both SKUs carry the identical
-[DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) panel, which needs
-this bias circuit. Not read from the Lite's own schematic.
-
----
-
-## 3. Circuit role — one boost and one inverting charge pump **[SCH-V]**
-
-The [SSD1677](../../solomon-systech/ssd1677/README.md) inside the panel runs the
-control loop; the power stage is on the mainboard and reaches the die through the
-[24-way FPC](../fpc0.5-smt-24p-b/README.md) at `J5`.
-
-```
-EPD_3V3_L3 ──[ L8  33 µH ]───┬──────▶|─── D4 ───┬──── PREVGH ──▶ J5.21
-  SPH252010H330MT            │                  │      C72 10 µF/25 V
-                        Q4 drain                │
-                        CJ2310 (N-ch)      C67 10 µF/25 V
-  J5.2 GDR ──┬── Q4 gate                        │  (flying capacitor)
-             │                                  │
-        R58 10 kΩ                    ┌──────────┴──────────┐
-             │                       │                     │
-            GND                   D5 ▲ (anode at PREVGL)  D6 ▼ (cathode at GND)
-                                     │                     │
-   Q4 source ──┬── R59 1.2 Ω ── GND  └─── PREVGL ──▶ J5.23 └── GND
-               └── J5.3 RESE              C73 10 µF/25 V
-```
-
-**`D4` — the boost rectifier.** Anode on the switch node, cathode on `PREVGH`.
-When `Q4` ([CJ2310](../../changjing/cj2310/README.md)) releases, `L8`'s flyback
-forward-biases `D4` and charges `C72`. Standard asynchronous boost.
-
-**`D5` and `D6` — the inverting charge pump.** `C67` is a flying capacitor tied
-to the same switch node. While the node is high, `D6` conducts and pins `C67`'s
-far plate near ground, charging it. When the node falls to ~0 V, that plate is
-driven **negative**, and `D5` conducts to pull `PREVGL` down with it. `C73`
-holds the result.
-
-So **one switching node, driven by one transistor, generates both a positive and
-a negative rail.** This matches DKE's own typical application circuit **[MAN]**
-§7.4 — the independent confirmation that this reading is right.
-
-### 3.1 Why 40 V, and why the same part three times
-
-`PREVGH` and `PREVGL` are the panel's gate-drive supplies, typically around
-**+22 V** and **−20 V** for this class of e-paper driver. **[INF]** — not read
-from the SSD1677 datasheet for this record.
-
-- **`D4`** sees roughly `PREVGH` in reverse while `Q4` is on: **~22 V against
-  40 V**, about 55 % of rating.
-- **`D5`** sees roughly `PREVGH` − `PREVGL` at the worst moment, which is a
-  larger swing, and **`D6`** sees roughly |`PREVGL`| plus the switch-node
-  amplitude.
-
-Using one 40 V part for all three is the sensible choice: it covers the worst
-case, removes two BOM lines, and gives a consistent V<sub>F</sub> across the two
-rails so they track. The **surrounding decoupling is 25 V-rated**
-(`C67`, `C71`, `C72`, `C73` all 10 µF/25 V), which independently corroborates
-that the rails sit in the low twenties. **[SCH-V]** + **[INF]**
-
-Contrast with `D2` on sheet 2, the frontlight rectifier, which is a
-**[20 V ROHM part](../../rohm/rb162vam-20tr/README.md)** chosen for
-ultra-low V<sub>F</sub> — the designer took efficiency there and voltage margin
-here. Two rectifiers, two different trade-offs, both defensible.
-
-### 3.2 Consequences worth knowing
-
-1. **The V<sub>F</sub> of `D5`/`D6` directly sets how negative `PREVGL` gets.**
-   An inverting charge pump loses **two** diode drops, so `PREVGL` ≈
-   −(switch-node amplitude − 2 × V<sub>F</sub>) ≈ 1.2 V short of ideal at 0.6 V
-   each. Substituting a higher-V<sub>F</sub> part makes `PREVGL` less negative,
-   which degrades the panel's gate drive and shows up as **poor contrast or
-   ghosting**, not as a failure. **[INF]**
-2. **Nothing in software controls or observes this.** `GDR` comes from inside the
-   panel. A bias-rail problem is invisible from firmware and looks like a slow or
-   dirty refresh.
-3. **These are the only 40 V-class parts in the signal area of sheet 4.** When
-   probing, `J5` pins 20–24 and the `D4`/`D5`/`D6` nodes are the high-voltage
-   ones.
-
----
-
-## 4. Substitution
-
-Required: **Schottky**, V<sub>RRM</sub> ≥ 40 V, I<sub>O</sub> ≥ 1 A, low
-V<sub>F</sub> (§3.2), **SOD-323 — check `F` vs plain** (§1.1).
-
-| Alternative | Note |
-|---|---|
-| **`1N5819HW`**, `SS14`, `B5819W` | Same class, common second sources |
-| **`1N5818WS`** (30 V) | ⚠ Same family, **less margin**; the datasheet's middle column |
-| **`1N5817WS`** (20 V) | ⚠ **Do not** — 20 V is inadequate here (§3.1) |
-| **`BAT54`** family | ⚠ 30 V and **200 mA** — far too little current |
-| [`RB162VAM-20TR`](../../rohm/rb162vam-20tr/README.md) | ⚠ The board's other Schottky, but **20 V** — not a substitute in this circuit |
-
-**Do not substitute a standard silicon rectifier** (`1N4148WS`, `1N4007`): the
-0.7–1.0 V drop costs `PREVGL` another volt (§3.2), and the recovery time is far
-too slow for a switching node.
-
----
-
-## 5. Integration pitfalls
-
-1. **SOD-323 vs SOD-323F** (§1.1) — different land patterns under the same type
-   number.
-2. **The datasheet is a three-part family document** (§1) — read the `1N5819WS`
-   column, not the header.
-3. **V<sub>F</sub> is a functional parameter here, not just a loss term** (§3.2).
-4. **Reverse leakage 0.5–1 mA at 40 V**, and the panel's bias rails are held by
-   10 µF capacitors that must survive the panel's deep-sleep periods. Leakage
-   discharges them; how fast was not calculated. **[INF]**
-5. **All three are in a converter whose controller is on the far side of a
-   connector** — see the
-   [CJ2310 record §3.1](../../changjing/cj2310/README.md#31-three-consequences-worth-knowing)
-   for why a marginal FPC contact presents as a display-quality bug.
-
----
-
-## 6. Open questions
-
-- **The maker actually fitted, and therefore the exact package** (§1.1).
-- The SSD1677's real `VGH`/`VGL` targets, which set the true reverse stress
-  (§3.1) — obtainable from the
-  [SSD1677](../../solomon-systech/ssd1677/README.md) and
-  [panel](../../dke/depg0397bbs770f3/README.md) records, not read here.
-- The converter's switching frequency, hence switching losses and ripple.
-- Whether reverse leakage meaningfully discharges the bias rails in deep sleep
-  (§5.4).
-- No measurement of anything.
-
----
-
-## Manufacturer
-
-**Not specified by the schematic** (§1.1). The retained document is Guangdong
-Hottech's. No vendor sourcing guide exists in this repository for that maker.
-
-**⚠ Retrieval finding — the LCSC PDF host trap.** LCSC's catalogue gave
-`https://www.lcsc.com/datasheet/lcsc_datasheet_2409300937_Guangdong-Hottech-1N5819WS_C191023.pdf`,
-which returned **HTTP 200 and 48 710 bytes of HTML** to all five user-agents
-tried (Chrome 131, ClaudeBot, WhatsApp, ChatGPT-User, plain `curl`). Rewriting to
-the CDN worked first try:
-
-```
-wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2409300937_Guangdong-Hottech-1N5819WS_C191023.pdf
-```
-
-**No user-agent rotation helps, because this is not bot-blocking — it is the
-wrong host.** **Check the `%PDF` magic bytes; both the status code and the `.pdf`
-extension lie.** `executed-success`, 2026-09-01, reproduced across five parts from
-this board. This belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## Related pages
-
-- [Changjing CJ2310](../../changjing/cj2310/README.md) — **`Q4`, the switch these three rectify for**
-- [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) — the panel; §7.4 of its manual is the reference circuit
-- [Solomon Systech SSD1677](../../solomon-systech/ssd1677/README.md) — the controller driving `GDR`
-- [FPC0.5-SMT-24P-B](../fpc0.5-smt-24p-b/README.md) — `J5`, where `PREVGH`/`PREVGL` cross to the panel
-- [ROHM RB162VAM-20TR](../../rohm/rb162vam-20tr/README.md) — the board's other Schottky, a different trade-off
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `1N5817WS – 1N5819WS` Schottky Barrier Diode | Guangdong Hottech (via LCSC CDN) | representative primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2409300937_Guangdong-Hottech-1N5819WS_C191023.pdf> | 2026-09-01 | undated, 4 pp | **40 V** V<sub>RRM</sub> for the `WS` suffix, SOD-323, UL94V-0, 0.005 g, the family's three-part structure — **for the Hottech part, not confirmed as the fitted one** (§1.1) | `artifacts/1n5819ws-guangdong-hottech-lcsc-mirror.pdf` |
-| C1 | LCSC entries `C191023`, `C369937` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `1N5819WS` | 2026-09-01 | — | the §1.1 multi-vendor spread including the **SOD-323 vs SOD-323F** package difference; 1 A, 25 A, 600 mV, leakage | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | all three instances; the §3 topology and every diode orientation; `L8`, `R58`, `R59`, `C67`, `C72`, `C73`; the `J5`.2/.3/.21/.23 connections | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| M1 | EPD Module User Manual §7.4 | DKE | primary | see the [panel record](../../dke/depg0397bbs770f3/README.md#12-authoritative-sources) | 2026-09-01 | 30 pp | independent confirmation of the §3 topology | `../../dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/1n5819ws-guangdong-hottech-lcsc-mirror.pdf` | 1 157 833 | `609a5bc2fcd5bbb36f47f802b11102f1e140eae519c74b067cb615b4d52d0a4f` | 4 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) with an intact text
-layer. The **orientation of all three diodes** — which is what distinguishes a
-boost rectifier from a charge-pump clamp, and therefore the whole of §3 — was read
-from a 200 dpi render of sheet 4. The text layer in that region places `D4`, `D5`,
-`D6`, `Q4`, `C67`, `C71`–`C73`, `R58`, `R59` and `L8` in one cluster and cannot
-resolve anode from cathode.
diff --git a/components/generic/1n5819ws/artifacts/1n5819ws-guangdong-hottech-lcsc-mirror.pdf b/components/generic/1n5819ws/artifacts/1n5819ws-guangdong-hottech-lcsc-mirror.pdf
deleted file mode 100644
index 058a92d..0000000
Binary files a/components/generic/1n5819ws/artifacts/1n5819ws-guangdong-hottech-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/generic/74hc138/README.md b/components/generic/74hc138/README.md
deleted file mode 100644
index 5c28702..0000000
--- a/components/generic/74hc138/README.md
+++ /dev/null
@@ -1,108 +0,0 @@
-# 74HC138 — 3-to-8 line decoder / demultiplexer
-
-> Generic logic family part. Record created **2026-09-04** from the M5Stack Cardputer
-> v1.0/v1.1 schematic and the vendor keyboard driver. Manufacturer **not specified** on the
-> schematic — the value string is simply `74HC138`, which is a multi-source industry-standard
-> part (NXP, TI, Toshiba, Nexperia, Diodes, and many Chinese second sources all make it).
-
-## Function
-
-Decodes a 3-bit binary address (`A0`, `A1`, `A2`) to **one of eight active-low outputs**
-(`/Y0`…`/Y7`), gated by three enables: `/E1`, `/E2` (active low) and `E3` (active high). Exactly
-one output is low at a time when enabled; all eight are high when disabled.
-
-In a keyboard it is the cheapest possible way to drive a matrix: three MCU pins select which of
-eight column lines is pulled low, and the MCU reads the row lines to see which key shorted.
-
-## Key capabilities
-
-| Property | Value |
-|---|---|
-| Function | 3-to-8 decoder, **active-low** outputs |
-| Enables | `/E1`, `/E2` active low; `E3` active high |
-| Supply | 2–6 V (HC family); **3.3 V** on the boards here |
-| Package | SOIC-16 / TSSOP-16, 16 pins |
-| Propagation delay | tens of ns at 3.3 V — irrelevant beside the firmware's `digitalWrite()` overhead |
-
-## Pinout as fitted (read from the M5Stack schematic)
-
-| Pin | Name | Pin | Name |
-|---|---|---|---|
-| 1 | `A0` | 16 | `VCC` |
-| 2 | `A1` | 15 | `/Y0` |
-| 3 | `A2` | 14 | `/Y1` |
-| 4 | `/E1` | 13 | `/Y2` |
-| 5 | `/E2` | 12 | `/Y3` |
-| 6 | `E3` | 11 | `/Y4` |
-| 7 | `/Y7` | 10 | `/Y5` |
-| 8 | `GND` | 9 | `/Y6` |
-
-This is the standard industry pinout; the M5Stack symbol matches it.
-
-## Used By
-
-### M5Stack Cardputer v1.0 (K132) and v1.1 (K132-V11)
-
-[`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md)
-*(the two boards share one published schematic file, SHA-256 `6016c1fe…`)*
-
-Designator **U7**, on the keyboard sheet. It is the **entire** keyboard scanner: there is no
-dedicated keypad controller on these boards.
-
-| Signal | Connection |
-|---|---|
-| `A0` (pin 1) | **G8** |
-| `A1` (pin 2) | **G9** |
-| `A2` (pin 3) | **G11** |
-| `/E1`, `/E2` (pins 4, 5) | **GND** — permanently enabled |
-| `E3` (pin 6) | **+3.3 V** — permanently enabled |
-| `/Y0`…`/Y7` | through **22 Ω 1 %** series resistors **R34…R27** to the matrix nets `Y0`…`Y7` |
-| `VCC` / `GND` | +3.3 V / GND |
-
-The seven **sense** lines (`G13, G15, G3, G4, G5, G6, G7`) go straight to the MCU as
-`INPUT_PULLUP`; the pressed key pulls one low when its column is selected.
-
-Vendor driver,
-[`IOMatrix.cpp`](https://github.com/m5stack/M5Cardputer/blob/f1392858b9994c3547120e602a57d3553d16ab01/src/utility/Keyboard/KeyboardReader/IOMatrix.cpp):
-
-```cpp
-const std::vector<int> output_list = {8, 9, 11};                 // A0, A1, A2
-const std::vector<int> input_list  = {13, 15, 3, 4, 5, 6, 7};    // seven sense lines
-void set_output(const std::vector<int>& p, uint8_t v) {           // v masked to 3 bits
-    digitalWrite(p[0], v & 1); digitalWrite(p[1], v & 2); digitalWrite(p[2], v & 4); }
-for (int i = 0; i < 8; i++) { set_output(output_list, i); … }     // eight columns per scan
-```
-
-**Cost: ten GPIOs**, which is the entire reason the Cardputer ADV exists. The ADV replaces this
-part with a [TCA8418](../../texas-instruments/tca8418/README.md) on I²C, keeps the **identical
-matrix** — same 56 switches, same `Y0..Y7` nets, same R27–R34 22 Ω resistors — and spends three
-pins instead of ten. The full comparison, including the proof that the two drivers' coordinate
-maths are algebraically equivalent, is at
-[`devices/m5stack/cardputer-adv/features/keyboard.md`](../../../devices/m5stack/cardputer-adv/features/keyboard.md).
-
-## Practical notes
-
-* **No debounce, no FIFO, no interrupt.** Everything is firmware's problem, and the scan is
-  fully synchronous: eight `set_output()` + seven `digitalRead()` per `update()`.
-* **No diodes in the Cardputer matrix**, so ghosting is possible on three-key combinations that
-  form a rectangle. The vendor driver reports all pressed coordinates and does not attempt to
-  detect ghosts.
-* The **22 Ω series resistors** are current-limiting/edge-softening on the drive lines, not
-  pull-ups. They are shared with the ADV design, which is a strong hint the matrix sub-sheet was
-  copied wholesale.
-* Because the outputs are **active low**, an unenabled or floating decoder leaves all columns
-  high and the keyboard simply reports nothing.
-
-## Substitutes
-
-Any 74HC138/74HCT138/74LVC138 from any vendor, subject to supply voltage. A larger matrix would
-want a `74HC154` (4-to-16) or a dedicated scanner. The dedicated-scanner route is what M5Stack
-eventually took.
-
-## Gaps
-
-* **No datasheet retained**, and no manufacturer identified — the schematic value is the generic
-  family number. Any vendor's HC138 datasheet applies; none was fetched in this pass.
-* Package, temperature grade and actual manufacturer on the fitted part: **unknown**. A board
-  photograph of U7's top marking would settle it.
diff --git a/components/generic/bm8563/README.md b/components/generic/bm8563/README.md
deleted file mode 100644
index caf6bfa..0000000
--- a/components/generic/bm8563/README.md
+++ /dev/null
@@ -1,117 +0,0 @@
-# BM8563 — I²C real-time clock/calendar
-
-- **Category:** low-power CMOS RTC/calendar with programmable clock output, alarm/timer
-  interrupt and power-down detector; I²C, external 32.768 kHz crystal.
-- **Manufacturer:** **unresolved.** The datasheet M5Stack mirrors carries no manufacturer name,
-  logo or contact block on page 1. Filed under `generic/` rather than guessing a vendor.
-- **Functional equivalent:** NXP **PCF8563** — same register map, same slave address, same
-  feature set. See [`components/nxp/pcf8563/`](../../nxp/pcf8563/artifacts/pcf8563-datasheet-rev-11.pdf) in this repository
-  for the fully-documented equivalent.
-- **Retrieved:** 2026-09-04
-
-The RTC of the M5Stack DinMeter, M5Dial, M5Capsule, M5StickC family and most other M5Stack
-products. M5Unified exposes it as `RTC8563_Class`.
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **BM8563** | datasheet cover; DinMeter schematic `U5` value text `RTC8563` |
-| Datasheet | `BM8563_V1.1_cn.pdf` — **Chinese only**, v1.1 | retained artifact |
-| Orderable variants | `BM8563ESA` (SOP8), `BM8563EMA` (MSOP8), `BM8563EHA` (TSSOP8), −40…+85 °C | datasheet ordering table |
-| Supply | **1.5 – 5.5 V** | datasheet |
-| Sleep current | typ. **0.25 µA** @ VDD 3.0 V, 25 °C | datasheet |
-| I²C address | **write `0xA2`, read `0xA3`** → 7-bit **`0x51`** | datasheet |
-| Max bus speed | 400 kbit/s | datasheet |
-| Clock output | 32.768 kHz / 1024 Hz / 32 Hz / 1 Hz, programmable | datasheet |
-| Interrupt | **open-drain** `INT` | datasheet |
-| Oscillator caps | integrated | datasheet |
-| Crystal | external 32.768 kHz | datasheet |
-
-### ⚠ Document-metadata finding
-
-Page 1 of `BM8563_V1.1_cn.pdf` carries the string **`MAX1937`** in the header area, immediately
-after the title block and unrelated to anything else on the page. That is the signature of a
-datasheet produced by editing another part's document — a Maxim MAX1937 template — and it is
-worth knowing before trusting any electrical table in it that is not corroborated. The register
-and address information *is* corroborated: it matches NXP's PCF8563 datasheet and M5Unified's
-`RTC8563_Class` implementation.
-
-**Language.** This document exists **only in Chinese** in every copy located. Per the
-multi-language policy it is therefore the **primary source** and is retained in the repository
-on its own merits, not archived as a translation. The English-language equivalent for the same
-silicon behaviour is the [PCF8563 datasheet](../../nxp/pcf8563/artifacts/pcf8563-datasheet-rev-11.pdf).
-
-## 2. Software
-
-| Framework | API | Evidence |
-|---|---|---|
-| Arduino / M5Unified | `M5.Rtc` → `RTC8563_Class`; `isEnabled()`, `getDateTime()`, `setDateTime()`, `setAlarmIRQ()` | `M5Unified/src/utility/RTC8563_Class.*`; DinMeter's own `M5DinMeter.h:23` re-exports it as `DinMeter.Rtc` |
-| Arduino (standalone) | `I2C_BM8563` — vendored in `m5stack/M5DinMeter-UserDemo` at `lib/I2C_BM8563/` | UserDemo snapshot |
-| ESP-IDF | no built-in driver; `esp-board-manager` models only the I²C bus and notes *"BM8563 RTC (I2C 7-bit 0x51): no bmgr device type"* | `board_peripherals.yaml` |
-| UiFlow2 / MicroPython | exposed as the board RTC | M5Stack docs |
-
-## 3. Artifacts
-
-| File | Size | SHA-256 | Version | Language | Licence | Redistribution | Disposition |
-|---|---:|---|---|---|---|---|---|
-| [`artifacts/BM8563_V1.1_cn.pdf`](artifacts/BM8563_V1.1_cn.pdf) | 590 599 | `a847c85a8d00121c1338c62797039fa1412d70588873313bd1759c80d4da44ed` | V1.1 | zh-CN (**only version that exists**) | unknown — no notice in the document | `unknown` | `repository` |
-
-Retrieved 2026-09-04 from
-`https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/BM8563_V1.1_cn.pdf`
-(HTTP 200, `%PDF` validated, text layer parses, cover heading cross-checked). Linked from **both**
-the DinMeter and DinMeter v1.1 documentation pages.
-
----
-
-## Used By
-
-### M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-Fitted as **`U5`**, 8-pin (`OSCI`, `OSCO`, `INT`, `VSS`, `SDA`, `SCL`, `CLKOUT`, `VDD`), on the
-**internal** I²C bus — **SCL GPIO12, SDA GPIO11** — which is *separate* from the PORT.A Grove
-bus (GPIO15/13). Crystal `Y2` = 32.768 kHz ±20 ppm 12.5 pF with `C28`/`C29` 6.0 pF. Supplied
-from `+3.3V`; `VBAT_IN` reaches the RTC section through `D5` so timekeeping survives the power
-latch opening.
-
-Its open-drain `INT` is one of the two wake sources for the board's power latch (the other is
-the encoder push-button on GPIO42) — an RTC alarm can power the whole device back up from a
-latched-off state. On the schematic `INT` carries a 10 kΩ pull-up whose designator text reads
-`R20` but which has no recoverable `CO` marker; see
-[`devices/m5stack/dinmeter/pinouts-and-buses.md` §6](../../../devices/m5stack/dinmeter/pinouts-and-buses.md#6-reference-designator-census-and-three-that-do-not-resolve).
-
-→ [`devices/m5stack/dinmeter/features/rtc-and-timekeeping.md`](../../../devices/m5stack/dinmeter/features/rtc-and-timekeeping.md)
-
-### Xteink X4 Pro and X4 Classic — *added 2026-09-04*
-
-Both S3-based Xteink e-readers carry a BM8563 at the standard **I²C 0x51**, on the
-shared **SDA 39 / SCL 38 @ 400 kHz** bus, Arduino controller 0 (`Wire`).
-
-The vendor's own stock firmware names the part explicitly: the class
-`XTEink::BM8563Driver` appears in the X4 Pro flash dump, with driver init at IROM
-`0x420a2834` adding device 0x51 and the bus object configured `{39, 38, 400000}`.
-That is an unusually direct confirmation — most identifications of this part come
-from an address plus a working driver, which cannot distinguish it from a PCF8563.
-
-The FreeInk SDK models it as `RtcType::Pcf8563`, i.e. it drives the register-compatible
-equivalent, and reports it **"confirmed found and initializing on hardware"**.
-
-| | [X4 Pro](../../../devices/xteink/x4-pro/README.md) | [X4 Classic](../../../devices/xteink/x4-classic/README.md) |
-|---|---|---|
-| Address | 0x51 | 0x51 |
-| Bus | SDA 39 / SCL 38 @ 400 kHz | SDA 39 / SCL 38 @ 400 kHz |
-| Bus neighbours | [GT911](../../goodix/gt911/README.md) 0x5D, [CW2017](../../cellwise/cw2017/README.md) 0x63 | CW2017 0x63, [QMI8658](../../qst/qmi8658a/README.md) 0x6B |
-| Backup power | **unknown** — no teardown exists for either device | same |
-| `INT` used as a wake source | **not established** | **not established** |
-
-**Family contrast worth recording:** the two ESP32-C3 Xteink devices answer
-differently. The [X3](../../../devices/xteink/x3/README.md) uses an
-[unidentified DS-series RTC at 0x68](../../unidentified/xteink-x3-x4/rtc-ds-series/README.md)
-— a different part at a different address, whose exact identity is an
-[open three-way conflict](../../../devices/xteink/x3/gaps-and-conflicts.md) — and
-the [X4](../../../devices/xteink/x4/README.md) has **no RTC at all**. Four devices
-from one vendor, three different answers.
-
-→ [`devices/xteink/x4-pro/features/rtc.md`](../../../devices/xteink/x4-pro/features/rtc.md)
diff --git a/components/generic/bm8563/artifacts/BM8563_V1.1_cn.pdf b/components/generic/bm8563/artifacts/BM8563_V1.1_cn.pdf
deleted file mode 100644
index 42ed135..0000000
Binary files a/components/generic/bm8563/artifacts/BM8563_V1.1_cn.pdf and /dev/null differ
diff --git a/components/generic/btb0.408-10plbdr-g41/README.md b/components/generic/btb0.408-10plbdr-g41/README.md
deleted file mode 100644
index 79fdf66..0000000
--- a/components/generic/btb0.408-10plbdr-g41/README.md
+++ /dev/null
@@ -1,313 +0,0 @@
-# XUNPU BTB0.408-10PLBDR-G41
-
-> **0.4 mm-pitch board-to-board connector**, 10 contacts in 2 rows, 0.8 mm mated height, 300 mA / 30 V, copper alloy, vertical surface mount.
-> Research snapshot **2026-09-01**. Used **twice** on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153): **`J3` on sheet 4** (mainboard) and **`J1` on sheet 6** (NFC sub-board) — the two halves of one joint.
-> **No datasheet exists** for this part anywhere reachable ([§5](#5-datasheet-search--negative-result)). **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[CAT]** | LCSC / JLCPCB catalogue entry `C42420580`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheets 4 and 6 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[SCH-M]** | Recovered from the schematic's `CO`/`PI` marker layer | `executed-success` for the extraction |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`BTB0.408-10PLBDR-G41`** | **[SCH-V]**, **[CAT]** |
-| Manufacturer | **XUNPU** (深圳市讯普电子有限公司) | **[CAT]** |
-| LCSC part | **`C42420580`** | **[CAT]** |
-| Function | Board-to-board / backplane connector | **[CAT]** |
-| **Pitch** | **0.4 mm** | **[CAT]** |
-| **Mated height** | **0.8 mm** | **[CAT]** |
-| **Contacts** | **10**, in **2 rows** | **[CAT]** |
-| Current rating | **300 mA** | **[CAT]** |
-| Voltage rating | **30 V** | **[CAT]** |
-| Contact material | copper alloy | **[CAT]** |
-| Mount | surface mount, **vertical** | **[CAT]** |
-| Operating temperature | **−35 °C to +85 °C** | **[CAT]** |
-| RoHS | yes | **[CAT]** |
-| Datasheet | **none — see §5** | — |
-
-### 1.1 Reading the part number
-
-`BTB` **0.4** **08** — **10P** — **LBDR** — **G41**, i.e. **B**oard-**T**o-**B**oard,
-**0.4 mm pitch**, **0.8 mm** mated height, **10 positions**. The trailing fields
-are XUNPU's own variant coding and **were not decoded**; guessing what `LBDR` or
-`G41` select would be exactly the kind of promotion-of-a-candidate the research
-method forbids. The decoded fields are all independently confirmed by the LCSC
-parametric entry (§1), which is why they are asserted and the rest is not.
-
-> ⚠ **The schematic labels *both* halves of the pair `BTB0.408-10PLBDR-G41`.**
-> A board-to-board joint needs a plug and a receptacle, which are ordinarily two
-> different orderable parts. One of the two symbols almost certainly carries the
-> wrong part string. Which one could not be determined, and it feeds directly
-> into the conflict in §3.3. **[SCH-V]**
-
----
-
-## 2. The symbol has 14 pins; the connector has 10 contacts
-
-Both symbols carry 14 pin markers **[SCH-M]**. Numbers 1–10 take the signals;
-**11, 12, 13 and 14 are all tied to `GND`** — 11+12 as a pair at one end, 13+14
-as a pair at the other. **[SCH-V]**
-
-Given a part number that says **10P** and an LCSC entry that says **10 contacts,
-2 rows**, positions 11–14 are the four **mounting posts / soldering tabs**, given
-pin numbers by the library symbol so they can be netted to ground. This is the
-same convention the board's Panasonic
-[A4S connectors](../../panasonic/axe512127d/README.md#32-pins-1316-are-soldering-tabs-and-the-datasheet-explains-the-tie)
-use, where the manufacturer's drawing states it explicitly. Here **no drawing
-exists to confirm it**, so it is `inferred` — strongly, but inferred.
-
-This reconciles the [device record's](../../../devices/m5stack/papermono/pinouts-and-buses.md)
-"10" with the raw marker count of 14. Not a contradiction: **10 contacts plus 4
-tabs**.
-
----
-
-## 3. Used By
-
-### `devices/m5stack/papermono` — `J3` sheet 4 **and** `J1` sheet 6
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md). This
-is the joint between the mainboard and the **NFC sub-board**
-(`02 Paper Mono NFC.SchDoc`, title block `Paper Mono NFC`, `2/2`, `V0.2`, dated
-**2026-07-28**), which carries the
-[ST25R3916](../../stmicroelectronics/st25r3916/README.md), its
-[27.12 MHz crystal](../xl7el89cmi-111ylc-27.12mhz-crystal/README.md), the
-matching bank and a 4-turn 25 × 25 mm PCB loop antenna.
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):
-NO.** The Lite drops NFC entirely — that and LoRa are the whole difference
-between the two SKUs. There is no NFC sub-board and therefore **no reason for
-this connector to be fitted at all**. Whether the mainboard still carries the
-unpopulated `J3` footprint is not established. `inferred`.
-
-### 3.1 `J3` — mainboard half, sheet 4 **[SCH-V]**
-
-| Pin | Net | Notes |
-|---:|---|---|
-| 1 | `GND` | |
-| **2** | **`3V3_L2`** | decoupled by `C59` = 10 µF/10 V |
-| 3 | — | stub, no net label |
-| **4** | **`G48_SYS_SCL`** | system I²C clock |
-| 5 | — | stub |
-| **6** | **`G47_SYS_SDA`** | system I²C data |
-| 7 | — | stub |
-| **8** | **`G6_RFID_INT`** | ST25R3916 `IRQ` → ESP32-S3 GPIO6 |
-| 9 | — | stub |
-| **10** | **`PYB_NFC_EN`** | carries a red ✗ marker; the sheet annotates *"`PYB_NFC_EN` is a spare GPIO pin"* |
-| 11, 12 | `GND` | tab pair |
-| 13, 14 | `GND` | tab pair |
-
-### 3.2 `J1` — NFC sub-board half, sheet 6 **[SCH-V]**
-
-| Pin | Net | Notes |
-|---:|---|---|
-| **1** | **`3V3_L2` → `VCC_3V3`** | through `R1` = 0 Ω and the `U1` [AW35122FDR](../../awinic/aw35122/README.md) load switch; `C1` = 10 µF |
-| 2 | `GND` | |
-| **3** | **`G48_SYS_SCL`** | |
-| 4 | — | stub |
-| **5** | **`G47_SYS_SDA`** | |
-| 6 | — | stub |
-| **7** | **`G6_RFID_INT`** | |
-| 8 | — | stub |
-| **9** | **`PYB_RFID_RST`** | same wire as `PYB_NFC_EN`; drives the load-switch enable |
-| 10 | — | stub |
-| 11, 12 | `GND` | tab pair |
-| 13, 14 | `GND` | tab pair |
-
-### 3.3 ⚠ **Unresolved conflict — the two halves do not agree on pin numbering**
-
-Put the two tables side by side and the same signal appears on a different pin
-number on each board:
-
-| Signal | `J3` (mainboard, sheet 4) | `J1` (NFC board, sheet 6) |
-|---|---:|---:|
-| `GND` | **1** | **2** |
-| 3V3 | **2** | **1** |
-| `G48_SYS_SCL` | **4** | **3** |
-| `G47_SYS_SDA` | **6** | **5** |
-| `G6_RFID_INT` | **8** | **7** |
-| enable / "reset" | **10** | **9** |
-
-`J3` puts every signal on an **even** pin; `J1` puts every signal on an **odd**
-pin. Both symbols mark pin 1 with a polarity dot, and both were read from 200 dpi
-renders, twice, so this is not an extraction artefact.
-
-**If pin *N* mated pin *N*, this connector would short `3V3_L2` to `GND`.** It
-plainly does not do that in a shipping product, so one of two things is true:
-
-| Reading | Implication |
-|---|---|
-| **A — deliberate.** The two halves are numbered from each board's own pin 1, and flipping a two-row connector over swaps the rows, so *odd mates even* by construction | The design is correct as drawn, and anyone reproducing it must replicate the same numbering convention |
-| **B — a drawing error.** One symbol's pin numbering (or its part string, §1.1) is wrong, and the PCB layout silently does the right thing | The schematic is misleading; only the layout is authoritative |
-
-**This record does not choose between them.** Most board-to-board pairs from
-mainstream vendors are designed to mate 1↔1 — but those pairs also have *two
-different part numbers*, and this one does not. Both anomalies point the same
-way and neither can be settled from the published evidence.
-
-**What is certain, and is enough for most purposes:**
-
-- The **signal set** across the joint: `3V3_L2`, `GND`, `G48_SYS_SCL`,
-  `G47_SYS_SDA`, `G6_RFID_INT`, and the enable line. Six nets, four grounds, four
-  unused positions.
-- **Each board's own net-to-pin mapping**, which is what firmware and net-level
-  debugging need.
-
-**What must not be assumed:** that `J3` pin *N* is electrically `J1` pin *N*.
-**Anyone designing a replacement NFC sub-board must verify the physical mapping
-against a real board or the connector's true datasheet, which does not exist
-(§5).** Getting this wrong applies 3.3 V to a ground pin.
-
-### 3.4 `PYB_NFC_EN` / `PYB_RFID_RST` — a power cut, not a reset
-
-Already established in
-[`gaps-and-conflicts.md`](../../../devices/m5stack/papermono/gaps-and-conflicts.md)
-R9: the two names are the same wire across this connector, it drives an
-[AW35122FDR](../../awinic/aw35122/README.md) load-switch enable, and the
-ST25R3916 **has no reset pin in any package** — so asserting it removes power
-rather than resetting the device. The `_RST` half of the name is misleading.
-
-This record adds one wrinkle, from the sheet-6 side: **`R2`, the resistor drawn
-between `PYB_RFID_RST` and `U1`'s `EN`, carries the value `NC` — not fitted** —
-and the mainboard side marks pin 10 with a red ✗ and the note *"spare GPIO pin"*.
-**[SCH-V]** So as drawn, it is not clear that the enable line reaches the load
-switch at all. What actually enables the NFC rail was **not resolved**; the
-answer may be on **NFC sheet 1 of 2, which M5Stack does not publish**.
-
----
-
-## 4. Substitution
-
-There is no datasheet, no footprint drawing and no published PCB layout, so a
-substitution cannot be specified from this record. What is known:
-
-| Property to match | Value |
-|---|---|
-| Pitch | 0.4 mm |
-| Mated height | 0.8 mm |
-| Contacts | 10, two rows |
-| Current | ≥ 300 mA per contact |
-
-Parts in the same class include Panasonic **A4S** (which this very board uses
-elsewhere — see [AXE512127D](../../panasonic/axe512127d/README.md), documented
-with a real datasheet), Hirose **DF40C**
-([documented here](../../hirose/df40c-30dp-0.4v/README.md)), JAE **WP7B** and
-Molex **SlimStack**. **None of these is claimed to be a drop-in**; the footprint
-is unknown.
-
-> Note the mild irony worth recording: the same board uses a **fully documented
-> Panasonic 0.4 mm connector** for the KEY/RGB joint and an **undocumented XUNPU
-> 0.4 mm connector** for the NFC joint. If a redesign wanted one connector family
-> across both joints, the A4S side is the one with a datasheet.
-
----
-
-## 5. Datasheet search — negative result
-
-**No datasheet was found. This is a recorded negative result.**
-
-| Attempt | Result |
-|---|---|
-| JLCPCB SMT parts API, exact keyword `BTB0.408-10PLBDR-G41` | **found the part** (`C42420580`, XUNPU) — but the record's `dataManualUrl` field is **`None`** and `lcscGoodsUrl` is **`None`** |
-| LCSC product page | none exists for this part code; the catalogue entry carries parametric data only |
-| `wmsc.lcsc.com` CDN, the path pattern that works for this board's other XUNPU part | no candidate stamp/filename to construct a URL from |
-| DuckDuckGo-lite, Mojeek, searx.be via `curl` | **all blocked or captcha'd** on 2026-09-01 |
-
-So the **entire specification in §1 comes from LCSC's parametric fields** — a
-distributor's transcription, not the manufacturer's document. It should be
-treated accordingly: good enough to identify the part, not good enough to
-qualify a design against.
-
-Date of search: **2026-09-01**.
-
-**What would resolve it:** XUNPU's own catalogue (the company distributes almost
-exclusively through LCSC and has little independent web presence); a Chinese-
-language connector distributor listing the `BTB0.4xx` series; or M5Stack's
-manufacturing BOM.
-
----
-
-## 6. Integration pitfalls
-
-1. **The mating pin correspondence is unresolved and a wrong assumption shorts a
-   rail** (§3.3). This is the single most important item on this page.
-2. **300 mA per contact**, and `3V3_L2` crosses on **one** contact to power the
-   entire NFC sub-board. The ST25R3916's transmitter is the load that matters and
-   its peak draw was not measured. **[INF]**
-3. **No datasheet** (§5) — no retention force, no mating-cycle rating, no
-   footprint, no reflow profile.
-4. **Both halves carry the same part string** (§1.1), so ordering "the part on the
-   schematic" gets you two of one half.
-5. **The enable path is drawn through an unfitted resistor** (§3.4).
-6. **−35 °C lower limit**, narrower than the Panasonic connector's −55 °C on the
-   same product. Irrelevant indoors; relevant to any outdoor claim.
-
----
-
-## 7. Open questions
-
-- Which half is the plug and which the receptacle, and what the true part number
-  of the other half is (§1.1).
-- Whether pin *N* mates pin *N* (§3.3) — **the blocking question**.
-- Whether positions 11–14 are really mounting tabs (§2) — `inferred`, unconfirmed.
-- What drives the NFC load switch's enable (§3.4) — likely answered by the
-  unpublished NFC sheet 1 of 2.
-- Whether the PaperMono-Lite mainboard retains an unpopulated `J3` footprint.
-- Mating-cycle rating, retention force, footprint — all absent (§5).
-
----
-
-## Manufacturer
-
-**XUNPU** (深圳市讯普电子有限公司), a Shenzhen connector maker distributed almost
-entirely through LCSC. No vendor sourcing guide exists in this repository yet.
-
-XUNPU also supplies this board's
-[USB-C receptacle](../typec-302-brp16sc08/README.md), for which a (text-layer-free,
-one-page) drawing **does** exist on the `wmsc.lcsc.com` CDN. **The contrast is the
-useful finding: XUNPU part coverage on LCSC is inconsistent — some parts carry a
-`dataManualUrl`, others carry `None`, and there is no fallback host.** Check the
-API's `dataManualUrl` field before spending time constructing CDN URLs by hand.
-
-Part discovery used JLCPCB's SMT parts API, which unlike DuckDuckGo-lite, Mojeek
-and searx.be was not bot-filtered on 2026-09-01:
-
-```bash
-curl -s -X POST -H 'Content-Type: application/json' \
-  -d '{"keyword":"BTB0.408-10PLBDR-G41","currentPage":1,"pageSize":2}' \
-  https://jlcpcb.com/api/overseas-pcb-order/v1/shoppingCart/smtGood/selectSmtComponentList
-```
-
-`executed-success`, 2026-09-01. Helper:
-[`scratch/m5stack-papermono/tools/lcsc_lookup.sh`](../../../scratch/m5stack-papermono/tools/lcsc_lookup.sh).
-This belongs in [`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## Related pages
-
-- [STMicroelectronics ST25R3916](../../stmicroelectronics/st25r3916/README.md) — what sits on the far side
-- [XL7EL89CMI-111YLC 27.12 MHz crystal](../xl7el89cmi-111ylc-27.12mhz-crystal/README.md) — on the same sub-board
-- [Awinic AW35122FDR](../../awinic/aw35122/README.md) — `U1` sheet 6, the rail this connector's enable line is meant to gate
-- [Panasonic AXE512127D](../../panasonic/axe512127d/README.md) — the board's *other* 0.4 mm board-to-board, fully documented
-- [XUNPU TYPEC-302-BRP16SC08](../typec-302-brp16sc08/README.md) — same vendor, USB-C
-- [PaperMono NFC feature guide](../../../devices/m5stack/papermono/features/nfc.md) · [bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| C1 | JLCPCB/LCSC catalogue entry `C42420580` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `BTB0.408-10PLBDR-G41` | 2026-09-01 | — | manufacturer XUNPU, 0.4 mm pitch, 0.8 mm height, 10P/2 rows, 300 mA, 30 V, −35…+85 °C, copper alloy, vertical SMD. **`dataManualUrl` = `None`** | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | both instances, both pinouts, the §3.3 discrepancy, `R2` = `NC` | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts** — **none.** No manufacturer document exists (§5). This is a
-negative result, recorded so it is not re-investigated.
diff --git a/components/generic/cn4040m000157a530001-40mhz-crystal/README.md b/components/generic/cn4040m000157a530001-40mhz-crystal/README.md
deleted file mode 100644
index cae52b6..0000000
--- a/components/generic/cn4040m000157a530001-40mhz-crystal/README.md
+++ /dev/null
@@ -1,173 +0,0 @@
-# 40 MHz crystal `CN4040M000157A530001` — ESP32-S3 main oscillator
-
-> The 4-pad SMD quartz crystal that provides the ESP32-S3's main 40 MHz reference on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), fitted as **`X1`** on schematic sheet 3.
-> Research snapshot **2026-09-01**. **No datasheet was found and no manufacturer could be identified** — see [§6](#6-datasheet-search--negative-result). Everything here is either read off the schematic or derived from the ESP32-S3's own requirements.
-
-> This record exists under `components/generic/` because the part could not be attributed to a manufacturer. If the vendor is later identified, move it to `components/<manufacturer>/` and leave a pointer.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet 3, `X1` and neighbours | `executed-success` for the extraction; `not-tested` electrically |
-| **[ESP]** | Espressif ESP32-S3 datasheet / hardware design guidelines — held at [`components/espressif/esp32-s3r8/artifacts/`](../../espressif/esp32-s3r8/README.md) | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity — what is actually known
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marking / value string on the schematic | **`CN4040M000157A530001`** | **[SCH]** sheet 3, adjacent to `X1` |
-| Manufacturer | **Unknown.** No vendor claims this part number in any source searched (§6) | — |
-| Function | Quartz crystal, ESP32-S3 main crystal oscillator | **[SCH]**, **[ESP]** |
-| Frequency | **40 MHz** | **[ESP]** — the ESP32-S3 requires 40 MHz; corroborated by the substring `40M000` in the value string. **[INF]** |
-| Package | **4-pad SMD**, two signal pads and two case/ground pads | **[SCH]** — the symbol has four pin markers, pins 1/2 on one side and 3/4 on the other |
-| Load capacitance | **Not stated.** Estimated ≈ 12–15 pF from the fitted 24 pF loading capacitors (§3.1) | **[INF]** |
-
-**Nothing above beyond the value string and the pad count is a direct reading of a vendor document.** The frequency is asserted because the ESP32-S3 has exactly one supported main-crystal frequency; the rest is inference or unknown, and is labelled as such.
-
-> ⚠ **Do not decode the part number.** `CN4040M000157A530001` contains recognisable-looking fields — `4040` could be a 4.0 × 4.0 mm package code, `40M000` could be 40.000 MHz, `A5` could be a tolerance grade — but **no vendor scheme was found to confirm any of it.** Reading a package size out of it and ordering a replacement on that basis would be exactly the kind of guess this knowledge base exists to avoid.
-
----
-
-## 2. Why 40 MHz, and why it is not negotiable **[ESP]**
-
-The ESP32-S3's RF and system clocking are built around a 40 MHz reference. Unlike the original ESP32, which supported 26 MHz and 40 MHz crystals, **the ESP32-S3 supports 40 MHz only.** Fitting anything else does not produce a slow board — it produces a board whose Wi-Fi does not associate and whose UART baud rates are wrong, because the whole PLL tree is scaled from this reference.
-
-This is worth stating in a component record because the crystal is the one part on an ESP32-S3 design where "close enough" is not a category.
-
----
-
-## 3. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`X1`**, schematic sheet 3 (`MCU_Core`).
-
-#### 3.1 Exact wiring **[SCH]**
-
-| Node | Connection |
-|---|---|
-| `X1` pins **3, 4** | `XTAL_P` side → **`L7` = 24 nH** in series → ESP32-S3 (`U12`) **pin 54, `XTAL_P`** |
-| `X1` pins **1, 2** | `XTAL_N` side → ESP32-S3 (`U12`) **pin 53, `XTAL_N`** |
-| `C45` | **24 pF**, `XTAL_P` to GND |
-| `C50` | **24 pF**, `XTAL_N` to GND |
-
-**Load-capacitance arithmetic [INF]:** two 24 pF capacitors in series present C1·C2/(C1+C2) = **12 pF** to the crystal, plus a few pF of board and pin stray — so the fitted crystal's specified load capacitance is most likely **12 pF, or 12–15 pF including strays**. This is the standard arrangement for a 40 MHz ESP32-S3 crystal and is not unusual. It is arithmetic, not a datasheet reading.
-
-#### 3.2 The 24 nH series inductor is a recognised ESP32-S3 practice, not an oddity
-
-`L7` = **24 nH** sits in series in the `XTAL_P` leg. **[SCH]**
-
-A series inductor in a crystal leg looks like a mistake to anyone meeting it for the first time. It is not — and this repository already holds an independent example: the **[Seeed Studio XIAO ESP32S3 Sense](../../../devices/seeed-studio/xiao-esp32s3-sense/README.md)** fits *"a 40 MHz crystal (`X1`, reached through `L5` **24 nH** since board revision v1.2)"*, as recorded in the [ESP32-S3R8 component record](../../espressif/esp32-s3r8/README.md#seeed-studio-xiao-esp32s3-sense).
-
-**Two unrelated vendors, two unrelated boards, the same 24 nH value on the same pin.** That is strong evidence of a common reference design or application-note recommendation rather than a coincidence. The Seeed record notes it appeared at a board revision, which suggests it fixed something.
-
-What it does is not documented in either vendor's material. The plausible readings — none of them confirmed here — are frequency pulling to centre the oscillator, suppression of a spurious overtone mode, or EMI shaping on the crystal edge. **[INF]** Recorded as an observed convergence between two designs; the mechanism is an open question (§7).
-
-> **Which leg carries `L7`** was determined from text-layer adjacency in the Altium PDF (`L7`'s pin markers sit between the `XTAL_P` label and `X1` pin 3). It is the less certain of the two facts here; the presence and value of `L7` are solid, the leg assignment is `inferred`. Read it off the rendered sheet if it matters to you.
-
-#### 3.3 Not to be confused with the other inductors on sheet 3
-
-Sheet 3 carries several small inductors and it is easy to attribute the wrong one **[SCH]**:
-
-| Ref | Value | Role |
-|---|---|---|
-| `L4` | `LQP03TN2N6B02D`, 2.6 nH | RF matching network, `ANT1` path |
-| `L5` | 0 Ω | RF path link |
-| `L6` | 2 nH | RF matching network |
-| **`L7`** | **24 nH** | **crystal leg — this record** |
-
-`L4`/`L5`/`L6` belong to the antenna matching network with `C39`–`C43` (two positions marked `NC(TBD)`, `GRM0335C1H2R0BA01D` 2.0 pF and `GRM0335C1H1R8BA01D` 1.8 pF), not to the oscillator.
-
-#### 3.4 There is no 32.768 kHz crystal
-
-`GPIO15/XTAL_32K_P` and `GPIO16/XTAL_32K_N` (ESP32-S3 pins 21 and 22) are used as **`G15_SPI2_CLK`** and **`G16_EINK_CS`** — the e-paper SPI bus. **[SCH]**
-
-So the ESP32-S3 has **no external low-power crystal**, and its RTC runs from an internal oscillator when the main crystal is off. That is not a defect on this board: real timekeeping is done by the **RX8130CE** on the I²C bus, which has its own crystal and its own always-on `3V3_L0` supply, and which wakes the system through M5PM1 GPIO0. **[INF]**
-
-The consequence for firmware is worth stating: **do not rely on the ESP32-S3's internal RTC for elapsed time across deep sleep on this board.** Read the RX8130CE.
-
----
-
-## 4. Drivers and software
-
-**Not applicable.** The crystal is configured by the ESP-IDF bootloader through `CONFIG_XTAL_FREQ` (40 MHz on the S3, and not selectable). No runtime interface exists.
-
-If you are bringing up a board and the crystal is suspect, the observable symptoms are: the ROM bootloader's UART output at a wrong baud rate, `esp_timer` running fast or slow by a fixed ratio, and Wi-Fi failing to associate while everything else appears fine.
-
----
-
-## 5. Integration pitfalls
-
-1. **40 MHz only on the ESP32-S3** (§2).
-2. **Load capacitance must match the crystal.** The 24 pF pair here implies a 12 pF-load part (§3.1). Substituting a crystal specified for a different load with the same capacitors shifts the frequency — typically by tens of ppm, which is enough to break Wi-Fi association margins.
-3. **ESR and drive level matter.** A crystal with too high an ESR for the ESP32-S3's oscillator may start intermittently — the classic symptom is "boots warm, fails cold".
-4. **Do not reuse `L7`'s value blindly on a board with different layout parasitics** (§3.2). It is evidently a tuning element, and its correct value depends on the board.
-5. **There is no 32.768 kHz crystal on this design** (§3.4).
-
----
-
-## 6. Datasheet search — negative result
-
-**No datasheet, product page, distributor listing or manufacturer attribution was found for `CN4040M000157A530001`.** This is a genuine negative result, not an abandoned search.
-
-Attempts on **2026-09-01**, all with a Chrome 131 desktop User-Agent unless noted:
-
-| Service / host | Query | Result |
-|---|---|---|
-| `search.brave.com` | `CN4040M000157A530001` | HTTP 429 (rate limited) on two attempts; one earlier query in the same session returned zero relevant results |
-| `search.brave.com` | `CN4040M000157A530001+crystal` | HTTP 429 |
-| `www.google.com` | `CN4040M000157A530001` | HTTP 200, but JavaScript-gated — no result links in the HTML |
-| `duckduckgo.com/html` · `html.duckduckgo.com` | `CN4040M000157A530001` | HTTP 202 challenge page, no results |
-| `search.naver.com` | `CN4040M000157A530001` | HTTP 200; only Korean shopping-aggregator links, nothing relevant |
-| `www.mojeek.com` | (rate limited before this query) | HTTP 403 |
-| `searx.be`, `search.inetol.net`, `priv.au`, `searxng.site`, `opnxng.com` | `CN4040M000157A530001` | HTTP 429 or empty |
-| `www.alldatasheet.com` | `Searchword=CN4040M000157A530001` | HTTP 200, no matching part |
-| `www.datasheets360.com` | `q=CN4040M000157A530001` | HTTP 403 |
-| `www.findchips.com`, `www.oneyac.com` | `CN4040M000157A530001` | HTTP 200 but JavaScript-rendered; the string appears only echoed in page metadata |
-| `www.oemsecrets.com` | `compare/CN4040M000157A530001` | HTTP 403 |
-| `www.lcsc.com/search?q=...` | — | Returns an identical 97 240-byte JavaScript shell for **every** query; the LCSC search API hosts (`wmsc.lcsc.com/ftps/...`) return HTTP 403 |
-
-**What would resolve it, in order of likely success:**
-
-1. A photograph of the fitted `X1` — SMD crystals carry an abbreviated marking (often just the frequency and a maker logo) that identifies the manufacturer far more reliably than the schematic string.
-2. A PaperMono BOM. M5Stack has **not** published one: the `M5_Hardware` repository stops at SKU C152 and contains no C153 directory at all (verified exhaustively — `git ls-tree -r --name-only HEAD | grep -iE 'papermono|c153'` returns nothing).
-3. LCSC's product-detail HTML for the part, if a part code can be found by another route. LCSC's search is unusable to automated clients but `https://www.lcsc.com/product-detail/<CODE>.html` does serve a `pdfUrl` field once you have the code.
-
-**What is *not* affected by this gap:** the electrical requirements (§2), the wiring (§3.1) and the integration rules (§5) are all fully established from the schematic and Espressif's documentation. A missing crystal datasheet does not block using or repairing this board — it blocks sourcing an exact replacement.
-
----
-
-## 7. Open questions
-
-- Manufacturer and datasheet (§6).
-- The crystal's specified load capacitance, ESR and frequency tolerance — all unknown; §3.1's 12 pF is arithmetic from the fitted capacitors.
-- **What `L7` is for**, and why the same 24 nH value appears on an unrelated Seeed ESP32-S3 board (§3.2). This is the most interesting question in this record, because the answer would apply to every ESP32-S3 design.
-- Which crystal leg `L7` is in (§3.2) — established only by text-layer adjacency.
-- Whether the package is 3.2 × 2.5 mm or 2.0 × 1.6 mm; the schematic symbol does not carry a footprint name in the extracted text.
-
----
-
-## Related pages
-
-- [Espressif ESP32-S3R8](../../espressif/esp32-s3r8/README.md) — the host, and the source of the 40 MHz requirement; its Seeed XIAO section records the matching 24 nH inductor
-- Seiko Epson RX8130CE (record pending; `components/seiko-epson/rx8130ce/`) — the board's actual timekeeper, which does have its own crystal
-- [Generic ceramic antenna record](../../generic/ceramic-antenna/README.md) — the RF matching network on the same schematic sheet
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 2026-05-22, 6 sheets | The value string `CN4040M000157A530001`, the 4-pad symbol, `C45`/`C50` = 24 pF, `L7` = 24 nH, connection to `U12` pins 53/54, and the absence of a 32.768 kHz crystal | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | ESP32-S3 Series Datasheet | Espressif | primary | datasheet | <https://www.espressif.com/sites/default/files/documentation/esp32-s3_datasheet_en.pdf> | 2026-08-21 (existing repository copy) | v2.2, 87 pp | The 40 MHz main-crystal requirement | `components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet.pdf` |
-| S3 | ESP Hardware Design Guidelines (ESP32-S3) | Espressif | primary | manual | <https://docs.espressif.com/projects/esp-hardware-design-guidelines/en/latest/esp32s3/esp-hardware-design-guidelines-en-master-esp32s3.pdf> | 2026-08-21 (existing repository copy) | esp-docs `master` build | Crystal and load-capacitor guidance | `components/espressif/esp32-s3r8/artifacts/esp32-s3-hardware-design-guidelines.pdf` |
-| S4 | XIAO ESP32S3 Sense crystal note | this repository | — | derived record | — | 2026-09-01 | — | The independent 24 nH observation in §3.2 | [`components/espressif/esp32-s3r8/README.md`](../../espressif/esp32-s3r8/README.md#seeed-studio-xiao-esp32s3-sense) |
-
-**Local artifacts:** none. No document specific to this part was obtained (§6).
-
-**Method note.** The pin/net table in §3.1 was recovered by parsing the Altium PDF's invisible component-outline and pin-instance markers and reading the human-readable text sharing each marker's row band. That recovers text adjacency, not electrical connectivity, which is why §3.2's leg assignment is marked `inferred` while the component values are not.
diff --git a/components/generic/esd5311/README.md b/components/generic/esd5311/README.md
deleted file mode 100644
index f643134..0000000
--- a/components/generic/esd5311/README.md
+++ /dev/null
@@ -1,246 +0,0 @@
-# ESD5311 — bidirectional ESD suppressor (TECH PUBLIC)
-
-> **Single-line bidirectional ESD protection diode**, 5 V standoff, ~0.3 pF, 4 A peak (8/20 µs), IEC 61000-4-2 / -4-5 rated, in a **DFN1006-2** (0402) package.
-> Research snapshot **2026-09-01**. **The most-used part on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) after the passives: 12 instances across 3 sheets** — every one enumerated in [§4](#4-used-by).
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | TECH PUBLIC `ESD5311X` datasheet, local copy `artifacts/esd5311x-tech-public-lcsc-mirror.pdf` — ⚠ **image-only, no text layer**, §2 | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entries `C2844730` (`ESD5311X`), `C2936982` (`ESD5311N`), retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off the schematic rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[SCH-T]** | Read from the schematic text layer only | `executed-success` for the extraction; attribution `inferred` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Value string on the schematic | **`ESD5311`** — with **no suffix** | **[SCH-V]** |
-| Manufacturer | **TECH PUBLIC** (泰科源) | **[CAT]** |
-| Function | Bidirectional transient-voltage suppressor for ESD protection | **[CAT]** |
-| Package | **DFN1006-2** — a 2-terminal 0402 leadless part | **[CAT]** |
-| Pins | **2** | **[SCH-M]**, all 12 instances |
-| RoHS | yes | **[CAT]** |
-
-### 1.1 ⚠ `ESD5311` with no suffix is not an orderable part number
-
-LCSC's catalogue has **no bare `ESD5311`**. It has two suffixed parts from the
-same maker, plus a third-party equivalent:
-
-| Part | Maker | LCSC | V<sub>RWM</sub> | V<sub>BR</sub> | Clamp | I<sub>PP</sub> (8/20 µs) | P<sub>PP</sub> | C | I<sub>R</sub> |
-|---|---|---|---|---|---|---|---|---|---|
-| **`ESD5311X`** | TECH PUBLIC | `C2844730` | **5 V** | **7.5 V** | **12 V / 21 V** | **4 A** | **80 W** | **0.3 pF** | 80 nA |
-| **`ESD5311N`** | TECH PUBLIC | `C2936982` | 5 V | 7.5 V | **15 V** | 4 A | **70 W** | 0.3 pF | 80 nA |
-| `ESD5311N` | UMW (Youtai) | `C2987704` | 5 V | 9 V | **21 V** | 4 A @ 8/20 µs | 84 W | 0.25 pF | 1 nA |
-
-**[CAT]**
-
-**Which suffix M5Stack fits is not established.** The schematic prints the family
-stem only. The two TECH PUBLIC variants differ in clamping voltage and peak power
-— 12 V/21 V and 80 W for the `X`, 15 V and 70 W for the `N` — which is a real
-difference for the pin being protected, but not one that changes any design
-decision on this board, because in every instance the protected net is a 3.3 V
-logic line or a 5 V USB line and both variants stand off 5 V.
-
-**No suffix is asserted here.** The datasheet retained is the `ESD5311X`, chosen
-because it is the higher-volume LCSC part; §1 quotes only properties the two
-share. **What would resolve it:** the top marking on an assembled board, or
-M5Stack's BOM.
-
----
-
-## 2. ⚠ The datasheet has no text layer
-
-`artifacts/esd5311x-tech-public-lcsc-mirror.pdf` is **4 pages, 953 567 bytes**,
-and `pdftotext` extracts **4 bytes** from it. Every page is a scan or a vector
-outline.
-
-So **the parametric table in §1.1 is LCSC's transcription, not the
-manufacturer's own text**, and no I–V curve, no derating curve, no solder profile
-and no marking code were read from the document. The file is retained because it
-is the only manufacturer artifact obtainable, and because a future reader can
-render its pages to PNG and read them as images — the technique used elsewhere in
-this repository for the
-[DKE panel manual](../../dke/depg0397bbs770f3/README.md), which has the same
-problem.
-
----
-
-## 3. What it is for
-
-A bidirectional TVS in an 0402 leadless package with **~0.3 pF** of capacitance.
-The capacitance is the whole point: 0.3 pF is low enough to sit on a **USB 2.0
-high-speed differential pair** without meaningfully degrading the eye, which is
-what a general-purpose 5 V TVS at tens of pF cannot do.
-
-The parts are rated to the two standards that matter for a handheld:
-
-- **IEC 61000-4-2** — the ESD test (contact and air discharge to an accessible
-  surface).
-- **IEC 61000-4-5** — the surge test.
-
-**Bidirectional** matters for the USB data lines, which are referenced to ground
-and can swing either way during a discharge, and for switch inputs where a
-discharge into a finger-accessible button can drive the pin negative.
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono` — **12 instances**
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-Every instance, with the net it protects. Designators use two different prefixes
-because they come from two different Altium documents (`TVS…` in the main
-project, `DR…` on the KEY/RGB sub-board).
-
-| # | Ref | Sheet | Net protected | Function of that net | Evidence |
-|---:|---|---:|---|---|---|
-| 1 | **`TVS1`** | 2 | **`USB_N`** | USB-C `DN1`/`DN2` — the high-speed pair | **[SCH-V]** |
-| 2 | **`TVS2`** | 2 | **`USB_P`** | USB-C `DP1`/`DP2` | **[SCH-V]** |
-| 3 | **`TVS3`** | 4 | **`G9_TF_DATA2`** | microSD DAT2 (pull-up `R62` 4.7 kΩ) | **[SCH-T]** |
-| 4 | **`TVS4`** | 4 | **`G8_TF_DATA3`** | microSD CD/DAT3 (`R63` 4.7 kΩ) | **[SCH-T]** |
-| 5 | **`TVS5`** | 4 | **`G12_TF_CMD`** | microSD CMD (`R64` 4.7 kΩ) | **[SCH-T]** |
-| 6 | **`TVS6`** | 4 | **`G13_TF_CLK`** | microSD CLK (`R65` 4.7 kΩ) | **[SCH-T]** |
-| 7 | **`TVS7`** | 4 | **`G11_TF_DATA0`** | microSD DAT0 (`R66` 4.7 kΩ) | **[SCH-T]** |
-| 8 | **`TVS8`** | 4 | **`G10_TF_DATA1`** | microSD DAT1 (`R67` 4.7 kΩ) | **[SCH-T]** |
-| 9 | **`TVS9`** | 4 | **`PYB_TF_DET`** | microSD **card-detect** (`R68` **1 MΩ**) | **[SCH-T]** |
-| 10 | **`DR1`** | 5 | **`PWR_BTN`** | power button `S1`, pulled up to **`3V3_L0`** by `R1` 10 kΩ, debounced by `C1` 100 nF | **[SCH-V]** |
-| 11 | **`DR2`** | 5 | **`G2_KEY1`** | user button A `S2`, pull-up `R2` 10 kΩ to `3V3_L2`, `C3` 100 nF | **[SCH-V]** |
-| 12 | **`DR3`** | 5 | **`G3_KEY2`** | user button B `S3`, pull-up `R5` 10 kΩ to `3V3_L2`, `C4` 100 nF | **[SCH-V]** |
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes, and probably all 12** — the Lite drops only NFC and LoRa, and
-none of these twelve is on either. The NFC sub-board (sheet 6) carries **no**
-ESD5311. Not read from the Lite's own schematic.
-
-### 4.1 The placement pattern is coherent, and it says something about the design
-
-Three groups, and each is an *externally accessible* interface:
-
-| Group | Count | Why it needs protection |
-|---|---:|---|
-| **USB-C data** | 2 | A connector a user plugs into. Low capacitance is mandatory here |
-| **microSD** | **7** | A card slot a user's fingers reach into — and **every single line is protected, including card-detect** |
-| **Buttons** | 3 | The only parts of the PCB a user touches during normal operation |
-
-Nothing else on the board gets an ESD5311: not the board-to-board connectors, not
-the FPC connectors, not the antenna. That is the correct call — those are internal
-joints, not user-accessible surfaces. **[INF]**
-
-The microSD coverage is more thorough than is common. Many designs protect the
-data lines and skip card-detect; here **`PYB_TF_DET` gets `TVS9`** even though it
-is a slow, 1 MΩ-pulled-up sense line. Its exposure is the same as the data lines'
-— it goes to a contact in the slot — so protecting it is consistent rather than
-excessive.
-
-### 4.2 The one thing to check before reusing this pattern
-
-`TVS1` and `TVS2` sit on `USB_N`/`USB_P` **at the connector**, upstream of the
-`ICMF062P900MFR` common-mode choke `FT1` and the 22 Ω series resistors `R40`/`R41`
-on sheet 3. **[SCH-V]** That is the right order: the TVS clamps at the point of
-entry, and the choke and series resistance are downstream of it.
-
-The 0.3 pF figure is what makes this legal on a USB 2.0 pair. **Substituting a
-"5 V ESD diode" with a conventional TVS at 20–50 pF would put ~100 pF across the
-pair once both are counted, and USB 2.0 high-speed would degrade.** If this part
-is ever swapped, capacitance — not voltage — is the parameter that must be
-matched. **[INF]**
-
----
-
-## 5. Substitution
-
-| Alternative | vs. ESD5311 | Note |
-|---|---|---|
-| **`ESD5311N`** (TECH PUBLIC) | Same family; 15 V clamp, 70 W | The other variant of this very part (§1.1) |
-| **`ESD5311N`** (UMW/Youtai) | 9 V V<sub>BR</sub>, 21 V clamp, 0.25 pF, 1 nA | A second source at LCSC |
-| Nexperia **PESD5V0X1BL** / **PESD5V0S1BL** | Documented, qualified, ~0.4 pF class | When the missing datasheet (§2) is unacceptable |
-| ON Semi **ESD9B5.0ST5G** | 0.35 pF, AEC-Q101 | Automotive-grade |
-| Any generic "5 V TVS" | ⚠ **usually 20–500 pF** | **Not** a substitute on the USB pair (§4.2) |
-
-**Match capacitance first, standoff voltage second.**
-
----
-
-## 6. Integration pitfalls
-
-1. **`ESD5311` alone is not orderable** (§1.1). Pick `X` or `N` deliberately.
-2. **The datasheet is image-only** (§2). Any number quoted from this record for
-   the part traces to LCSC, not to TECH PUBLIC.
-3. **Capacitance, not voltage, is the substitution constraint** on USB (§4.2).
-4. **Two designator prefixes for one part** (`TVS…` and `DR…`) across two Altium
-   documents. A search for "TVS" finds 9 of the 12.
-5. **12 instances is a real BOM line.** At 0402 leadless, placement yield matters
-   more than unit cost.
-6. **These protect against ESD, not against a shorted or over-voltage supply.**
-   A 5 V standoff on a 3.3 V logic line means the part is invisible in normal
-   operation and stays invisible right up to 7.5 V — it is not a rail clamp.
-
----
-
-## 7. Open questions
-
-- **Which suffix is fitted** (§1.1) — resolvable only from a board or a BOM.
-- The datasheet's own electrical tables, curves and marking code (§2) — present
-  in the file as images, not yet transcribed.
-- Whether the PaperMono-Lite carries all 12 (`inferred`, §4).
-- No measurement of anything: no ESD gun, no TLP, no eye diagram.
-
----
-
-## Manufacturer
-
-**TECH PUBLIC** (泰科源) is a Shenzhen protection-device maker distributed through
-LCSC. No vendor sourcing guide exists in this repository yet.
-
-**⚠ Retrieval finding — the LCSC PDF host trap.** The working URL is on
-**`wmsc.lcsc.com`**, not on `www.lcsc.com`:
-
-| URL form | Result |
-|---|---|
-| `https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2108072230_TECH-PUBLIC-ESD5311X_C2844730.pdf` | **200, `%PDF` ✓**, 953 567 B |
-| `https://www.lcsc.com/datasheet/lcsc_datasheet_<stamp>_<name>_<code>.pdf` | **HTTP 200 with `text/html`** for every part tried |
-
-`www.lcsc.com/datasheet/*.pdf` returns **HTTP 200 and HTML** under a `.pdf` URL.
-**Check the `%PDF` magic bytes; the status code proves nothing.** The rewrite that
-works is `www.lcsc.com/datasheet/lcsc_datasheet_<stamp>_<name>_<code>.pdf` →
-`wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/<stamp>_<name>_<code>.pdf`. This
-reproduces the finding already recorded in the
-[IP2315 record](../../injoinic/ip2315/README.md#manufacturer) and belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## Related pages
-
-- [XUNPU TYPEC-302-BRP16SC08](../typec-302-brp16sc08/README.md) — the connector `TVS1`/`TVS2` guard
-- [microSD / SDMMC interface](../micro-sd-sdmmc/README.md) — the interface `TVS3`–`TVS9` guard
-- [Panasonic AXE612124D](../../panasonic/axe612124d/README.md) — the sub-board `DR1`–`DR3` live on
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `ESD5311X` datasheet | TECH PUBLIC (via LCSC CDN) | primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2108072230_TECH-PUBLIC-ESD5311X_C2844730.pdf> | 2026-09-01 | undated, 4 pp | retained as the only manufacturer artifact; **no text layer**, §2 | `artifacts/esd5311x-tech-public-lcsc-mirror.pdf` |
-| C1 | LCSC entries `C2844730`, `C2936982`, `C2987704` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `ESD5311` | 2026-09-01 | — | the §1.1 parametric table; the existence of `X` and `N` suffixes and the UMW second source | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | all 12 instances and their nets (§4) | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/esd5311x-tech-public-lcsc-mirror.pdf` | 953 567 | `00acc3ed39fa5ede6b73405949bbd89446867336962d41f4115dc260d91740ab` | 4 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) and confirmed
-text-layer-free (`pdftotext` yields 4 bytes). The 12-instance census in §4 comes
-from the schematic's `CO` marker layer, enumerated across **all six sheets** —
-proving the set is complete rather than searching for the instances expected. The
-`TVS1`/`TVS2` and `DR1`–`DR3` rows were additionally re-read from 200 dpi page
-renders; the seven microSD rows were not, and are marked **[SCH-T]** accordingly.
diff --git a/components/generic/esd5311/artifacts/esd5311x-tech-public-lcsc-mirror.pdf b/components/generic/esd5311/artifacts/esd5311x-tech-public-lcsc-mirror.pdf
deleted file mode 100644
index 167625c..0000000
Binary files a/components/generic/esd5311/artifacts/esd5311x-tech-public-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/generic/fpc0.5-smt-24p-b/README.md b/components/generic/fpc0.5-smt-24p-b/README.md
deleted file mode 100644
index ecf1c92..0000000
--- a/components/generic/fpc0.5-smt-24p-b/README.md
+++ /dev/null
@@ -1,244 +0,0 @@
-# FPC0.5-SMT-24P-B — e-paper panel FPC connector (manufacturer **unidentified**)
-
-> **24-contact, 0.5 mm-pitch flat-flex (FPC) connector**, surface-mount. Fitted as **`J5` on sheet 4** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153). It is the board's interface to the e-paper display module.
-> Research snapshot **2026-09-01**. **The manufacturer and the true ordering part number were not established** — see [§2](#2--the-part-number-is-a-library-designation-not-an-orderable-part).
-> **No hardware was available.** The pinout below is nevertheless solid: it is confirmed twice, independently.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH-V]** | Read off sheet 4 of `PaperMono_SCH_V0.6.2_20260522.pdf` rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[SCH-M]** | Recovered from the schematic's `PI` pin-marker layer | `executed-success` for the extraction |
-| **[MAN]** | DKE **EPD Module User Manual** p. 7, held at [`components/dke/depg0397bbs770f3/artifacts/`](../../dke/depg0397bbs770f3/artifacts/) | `not-tested` |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Designation on the schematic | **`FPC0.5-SMT-24P-B`** | **[SCH-V]** |
-| Manufacturer | **unidentified** — §2 | — |
-| Function | 24-way flat-flex connector, board-to-FPC | **[SCH-V]** |
-| Contacts | **24** | **[SCH-M]** — 24 `PI` markers, `J5`.1 … `J5`.24 |
-| Pitch | **0.5 mm**, from the name | **[INF]** |
-| Mount | **SMT**, from the name | **[INF]** |
-| Reference designator | **`J5`**, sheet 4 | **[SCH-V]** |
-| Mates with | the [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) panel's 24-pin FPC tail | **[MAN]** |
-| Datasheet | **none found** — §5 | — |
-
----
-
-## 2. ⚠ The part number is a library designation, not an orderable part
-
-`FPC0.5-SMT-24P-B` decomposes transparently: **FPC**, **0.5** mm pitch,
-**SMT** mount, **24P** contacts, variant **B**. That is a *description*, and it
-is how EDA library symbols are commonly named when the librarian does not want
-to bind the schematic to one vendor.
-
-**Searching for it as a part number returns nothing.** A query against LCSC /
-JLCPCB's catalogue for the exact string produced **no result**. Near-neighbour
-parts in the same class exist in quantity —
-
-| Part found | Vendor | Note |
-|---|---|---|
-| `HC-FPC-0.5-24P-FH20` | Hong Cheng | 24P, 0.5 mm, 2.0 mm height, flip-top, bottom contact |
-| `FPC-0.5-24P-H20` | SHOU HAN | 24P, 0.5 mm, right-angle SMT |
-| `FPC-05F-6PH20`, `FPC-05F-8PH20` | XUNPU | same series, different contact counts |
-
-— and **none of them is this part.** XUNPU supplies both of this board's other
-connectors ([USB-C](../typec-302-brp16sc08/README.md) and
-[board-to-board](../btb0.408-10plbdr-g41/README.md)), so a XUNPU FPC connector
-is a *plausible* candidate. **That is a hypothesis and it is deliberately not
-promoted to a finding.** No part number is asserted here.
-
-### What would resolve it
-
-1. **A photograph of the connector body on an assembled PaperMono.** FPC
-   connector housings usually carry no marking, so this may not settle it either.
-2. **M5Stack's manufacturing BOM**, which is not published.
-3. **A replacement-part or repair listing** from M5Stack or a reseller.
-4. The **`-B` suffix** is the one genuinely discriminating token; a vendor whose
-   series uses a trailing `-B` for a variant (contact side, latch style, height)
-   would be a strong lead.
-
-Two properties the schematic does **not** state, and which matter for
-substitution:
-
-- **Contact side** — top-contact or bottom-contact. This determines which way up
-  the panel's flex tail must be inserted, and getting it wrong reverses the
-  entire pinout.
-- **Latch style** — flip-lock, slide-lock or ZIF-less. Determines assembly and
-  serviceability.
-
----
-
-## 3. Used By
-
-### `devices/m5stack/papermono` — `J5`, sheet 4
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-The **[PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) uses
-the same panel and the same connector**: both product pages carry an identical
-display specification and link the same 3.97-inch datasheet. The Lite's
-schematic is published only as a 4-sheet `PRJ` PDF, so its `J5` wiring is
-`inferred`, not independently read.
-
-### 3.1 Pinout — established, and cross-checked against the panel manual
-
-This is the pinout's strongest property: **two independent documents agree
-position for position**. The left three columns are the panel's own pin
-assignment from **[MAN]** p. 7; the right two are how the PaperMono wires them
-**[SCH-V]** / **[SCH-M]**.
-
-| Pin | Panel signal **[MAN]** | I/O | PaperMono net | Goes to |
-|---:|---|---|---|---|
-| 1 | `NC` | — | — | keep open |
-| 2 | **`GDR`** | O | `GDR` | **gate of `Q4`** ([CJ2310](../../changjing/cj2310/README.md)) — the panel's external boost NMOS |
-| 3 | **`RESE`** | I | `RESE` | current-sense node: `Q4` source through **`R59` = 1.2 Ω** |
-| 4 | `VDHR` | C | — | `C74` = 4.7 µF/25 V |
-| 5 | `VDHR`/`NC` region | C | — | `C75` = 4.7 µF/25 V |
-| 6 | `NC` (temp-sensor SCL) | O | — | not used |
-| 7 | `NC` (temp-sensor SDA) | I/O | — | not used |
-| 8 | **`BS`** | I | — | bus-interface select; **`R60` = 0 Ω** sets 4-wire SPI |
-| 9 | **`BUSY_N`** | O | `G18_EINK_BUSY` | **ESP32-S3 GPIO18** |
-| 10 | **`RST_N`** | I | `PYB_EINK_RST` | **[M5IOE1](../../m5stack/m5ioe1/README.md) `IO5`** — *not* an ESP32 pin; `R61` = 0 Ω in series |
-| 11 | **`DC`** | I | `G17_EINK_DC` | **ESP32-S3 GPIO17** |
-| 12 | **`CSB`** | I | `G16_EINK_CS` | **ESP32-S3 GPIO16** |
-| 13 | **`SCL`** | I | `G15_SPI2_CLK` | **ESP32-S3 GPIO15** |
-| 14 | **`SDA`** | I/O | `G14_SPI2_MOSI` | **ESP32-S3 GPIO14** |
-| 15 | **`VDDIO`** | P | `EPD_3V3_L3` | rail gated by M5IOE1 `IO3` |
-| 16 | `VDD` | P | `EPD_3V3_L3` | `C77` = 10 µF/25 V |
-| 17 | `GND` | P | `GND` | |
-| 18 | `VDDD` | C | — | `C79` = 1 µF/25 V |
-| 19 | `VPP` | P | — | test pin, keep open |
-| 20 | `VSH` | C | — | `C81` = 4.7 µF/25 V |
-| 21 | `VGH` | C | `PREVGH` | fed by the §3.2 boost; `C82` = 4.7 µF/25 V |
-| 22 | `VSL` | C | — | `C83` = 4.7 µF/25 V |
-| 23 | `VGL` | C | `PREVGL` | fed by the §3.2 charge pump |
-| 24 | `VCOM` | C | — | `C84` = 1 µF/25 V |
-
-Signal-to-GPIO assignments are corroborated a third time by M5Stack's own driver
-**[SRC]**: `EDP_SPI.cpp:26–30, 37–38` and `M5GFX.cpp:2085, 2106–2125`.
-
-> The [device record already notes](../../../devices/m5stack/papermono/pinouts-and-buses.md)
-> that this FPC pinout "matches the DKE panel manual's Input/Output Pin
-> Assignment table (p. 7) position for position — an independent cross-check that
-> the schematic extraction is being read correctly." This record reproduces that
-> table so the connector can be understood without opening the panel record.
-
-### 3.2 The connector carries a switching converter, not just logic
-
-Pins 2, 3, 21 and 23 are not signals in the usual sense. The SSD1677 inside the
-panel runs its own DC/DC, but the **inductor, switch, rectifier and charge pump
-are on the mainboard** and reach the die through this connector:
-
-```
-EPD_3V3_L3 ──[ L8 33 µH ]──┬──▶|── D4 ──┬── PREVGH ── J5.21
-  SPH252010H330MT          │            │            (C72 10 µF/25 V)
-                     Q4 drain           └─┤C67 10 µF/25 V├─┬─ D5 ─┘
-  J5.2 GDR ──┬── Q4 gate (CJ2310)                          └─ D6 ─ GND
-             │                                             │
-         R58 10 kΩ                            PREVGL ── J5.23  (C73 10 µF/25 V)
-             │
-            GND     Q4 source ── R59 1.2 Ω ── GND
-                              └── J5.3 RESE
-```
-
-**[SCH-V]**, and it matches DKE's own typical application circuit **[MAN]** §7.4.
-
-Two practical consequences:
-
-1. **This connector carries high-voltage rails.** `PREVGH` and `PREVGL` are the
-   panel's gate-drive supplies; the decoupling around pins 17–24 is rated
-   **25 V**, and `D4`/`D5`/`D6` are 40 V parts. Treat pins 20–24 as high-voltage
-   when probing, and do not hot-plug the flex.
-2. **`GDR` and `RESE` are a current-mode switching loop closed through a
-   connector.** Contact resistance is in that loop. A dirty or partially inserted
-   FPC does not fail cleanly — it changes the sense voltage across `R59` = 1.2 Ω
-   and therefore the peak current, which shows up as display artefacts rather
-   than as an obvious dead panel. **[INF]** This is worth knowing before chasing
-   a refresh-quality bug in software.
-
----
-
-## 4. Substitution guidance
-
-**The functional pinout is fixed by the panel**, so any 24-way 0.5 mm FPC
-connector is a *functional* candidate. What is not interchangeable:
-
-| Property | Why it blocks a swap |
-|---|---|
-| **Contact side** (top vs bottom) | Reverses the flex orientation — pin 1 lands on pin 24 |
-| **Footprint** | Pad pitch is fixed at 0.5 mm but pad length, latch-anchor pads and body width are not |
-| **Height** | The PaperMono is a thin device; a 2.0 mm-tall flip-top may not fit under the panel |
-| **Latch mechanism** | Affects assembly force and whether the flex can be reseated |
-
-Since **M5Stack does not publish the PCB layout**, none of these can be matched
-from this record. A substitution needs a physical board.
-
----
-
-## 5. Datasheet search — negative result
-
-**No datasheet was found, and none is expected to exist**, because the string is
-a library designation rather than a manufacturer's ordering code (§2).
-
-| Attempt | Result |
-|---|---|
-| JLCPCB SMT parts API, exact keyword `FPC0.5-SMT-24P-B` | **no results** |
-| Same API, `FPC0.5-SMT-24P` | only JLCPCB-internal assembly SKUs, no vendor part |
-| Same API, `FPC-0.5-24P` | Hong Cheng and SHOU HAN parts — **different part numbers**, not this one |
-| Same API, `0.5mm 24P FPC connector XUNPU` | XUNPU `FPC-05F-*` series, 6P and 8P — right family, wrong contact count, and the naming pattern does not match |
-| DuckDuckGo-lite, Mojeek, searx.be via `curl` | **all blocked or captcha'd** on 2026-09-01; no result obtained by general web search |
-
-Date of search: **2026-09-01**. This is a recorded negative result: it should not
-be repeated without new evidence of the kind listed in §2.
-
----
-
-## 6. Open questions
-
-- Manufacturer and ordering part number (§2).
-- Contact side (top or bottom) and latch style — both needed for any repair.
-- Current and voltage rating per contact. Unstated, and non-trivial here because
-  pins 21/23 carry the panel's gate-drive rails.
-- Insertion-cycle rating — relevant because the flex is a serviceable joint.
-- Whether the PaperMono-Lite fits the same connector (`inferred`, §3).
-
----
-
-## Manufacturer
-
-**Unidentified.** No vendor sourcing guide applies. If the part is later
-established as XUNPU — the vendor of this board's two other connectors — the
-retrieval notes in the
-[TYPEC-302-BRP16SC08 record](../typec-302-brp16sc08/README.md#manufacturer)
-apply, in particular the `wmsc.lcsc.com` vs `www.lcsc.com/datasheet` trap.
-
-## Related pages
-
-- [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) — the panel on the other end, and the source of the §3.1 table
-- [Solomon Systech SSD1677](../../solomon-systech/ssd1677/README.md) — the controller whose DC/DC §3.2 serves
-- [Changjing CJ2310](../../changjing/cj2310/README.md) — `Q4`, the boost NMOS driven by `J5`.2
-- [1N5819WS](../1n5819ws/README.md) — `D4`/`D5`/`D6` in the same converter
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — owns the panel reset and rail enable
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | the designation `FPC0.5-SMT-24P-B`, 24 pin markers, the §3.1 net column, the §3.2 converter | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| M1 | EPD Module User Manual, p. 7 §5 *Input/output Pin Assignment* | DKE | primary | see the [panel record](../../dke/depg0397bbs770f3/README.md#12-authoritative-sources) | 2026-09-01 | 30 pp, drawing `REV. A0` 2024-09-29 | the §3.1 panel-signal column | `../../dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf` |
-| S2 | `M5PaperMono-UserDemo` `EDP_SPI.cpp`, `M5GFX.cpp` | M5Stack | primary | <https://github.com/m5stack/M5GFX> | 2026-09-01 | MIT | third corroboration of the GPIO assignments | `../../../scratch/m5stack-papermono/repos/` |
-
-**Local artifacts** — none. No datasheet exists for this designation (§5); the
-panel manual that supplies the pin assignment is held under the
-[panel's own record](../../dke/depg0397bbs770f3/README.md) and is cited from
-there rather than duplicated.
diff --git a/components/generic/gnss-ceramic-patch-antenna/README.md b/components/generic/gnss-ceramic-patch-antenna/README.md
deleted file mode 100644
index 1815460..0000000
--- a/components/generic/gnss-ceramic-patch-antenna/README.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# GNSS ceramic patch antenna (18 × 18 × 4 mm class) — `ANT1818-04`
-
-- **Category:** generic **passive ceramic patch antenna** for L1-band GNSS (~1.56–1.61 GHz)
-- **⚠ Not to be confused with** [`components/generic/ceramic-antenna`](../ceramic-antenna/README.md),
-  which documents the **2.4 GHz chip antennas** on an unrelated board. Different band,
-  different physics, different part class.
-- **Research status:** part number read from a schematic comment only. **No datasheet, no
-  manufacturer identified.**
-- **Retrieved:** 2026-09-04
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Schematic comment | **`ANT181804`** as extracted — almost certainly rendered **`ANT1818-04`** | Cap LoRa-1262 schematic V1.1, `J1` |
-| Reading of the name | `18 × 18` mm footprint, `04` = **4 mm** ceramic height — the standard naming convention for this part class | `inferred` |
-| Type | passive ceramic patch, single feed | topology on the sheet |
-| Band | GNSS **L1 neighbourhood** — GPS/QZSS/SBAS L1, GALILEO E1, GLONASS R1, BDS B1I/B1C | follows from the receiver it feeds |
-| Manufacturer | **unidentified** | — |
-
-⚠ The literal extracted string is `ANT181804` with no hyphen. The repository's PaperMono
-work already documents that M5Stack Altium PDFs mangle punctuation in some text layers, so
-a missing hyphen is the likely explanation — but **the reading `ANT1818-04` is `inferred`**,
-not read.
-
-## 2. Why the size matters
-
-An 18 mm patch on a 4 mm-thick ceramic is a compromise between gain and volume, and it
-constrains what the rest of the receive chain must do:
-
-- A patch this small has modest gain and a narrow effective bandwidth, so it is normally
-  paired with an **external LNA placed immediately at the feed** to set the system noise
-  figure. That is exactly what the Cap LoRa-1262 does with a
-  [MAX2659](../../analog-devices/max2659/README.md).
-- Ceramic patches are **strongly detuned by nearby metal and by the ground plane they sit
-  on**. A patch inside a plastic Cap, 40 mm from a +22 dBm sub-GHz transmitter and above a
-  host PCB, is not operating under datasheet conditions.
-- They are **directional (hemispherical, sky-facing)**. Orientation matters; owners
-  reporting "no satellites indoors" are usually seeing exactly this plus building
-  attenuation.
-
-## 3. Used By
-
-### [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) — designator `J1`
-
-| Item | Value |
-|---|---|
-| Feed | → `L1` **6.8 nH ±5 %** series match → `U1` **MAX2659** LNA `RFIN` (pin 3) |
-| Onward | LNA `RFOUT` (6) → `C5` 470 pF → `M2` **ATGM336H-6N** pin 11 `ANT` |
-| Bias path | LNA supply from `+3.3V`; GNSS `VCC_RF` (pin 14) through `FB2` 120 Ω/MB |
-| Vendor description | *"built-in ceramic antenna"* |
-
-Board-level claims this chain supports: tracking **−162 dBm**, acquisition −160 dBm, cold
-start −148 dBm, cold TTFF 23 s / hot 1 s, accuracy < 1.5 m CEP50.
-
-### [M5Stack Cap LoRa868 (U201)](../../../devices/m5stack/cap-lora868/README.md)
-
-Vendor description is identical (*"built-in ceramic antenna"*) and the GNSS specification
-table matches exactly, so the same antenna class is almost certainly fitted. **Not
-confirmed** — the U201 schematic was not fetched.
-
-## 4. Gaps
-
-| # | Gap |
-|---|---|
-| 1 | **Manufacturer and datasheet unknown.** Gain, efficiency, axial ratio, required ground-plane size: all unknown |
-| 2 | The hyphenless `ANT181804` reading is `inferred` |
-| 3 | Ground-plane dimensions and keepout on the Cap PCB are unknown (no layout files) |
-| 4 | No measurement of GNSS performance on either Cap by anyone |
-| 5 | Whether LoRa TX at +22 dBm desensitises this front end has never been tested |
-
-## 5. Related components
-
-- [`components/analog-devices/max2659`](../../analog-devices/max2659/README.md) — the LNA at its feed
-- [`components/zhongkewei/atgm336h-6n`](../../zhongkewei/atgm336h-6n/README.md) — the receiver it serves
-- [`components/generic/ceramic-antenna`](../ceramic-antenna/README.md) — **a different part class** (2.4 GHz chip antennas), linked to prevent confusion
-
-## 6. Sources
-
-| ID | Title | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|
-| GA-1 | Cap LoRa-1262 schematic V1.1 | primary | [`devices/m5stack/cap-lora-1262/artifacts/schematic/`](../../../devices/m5stack/cap-lora-1262/artifacts/schematic/) | 2026-09-04 | `J1` comment, `L1` 6.8 nH, the LNA chain |
-| GA-2 | Cap LoRa-1262 documentation | primary | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` | 2026-09-04 | *"built-in ceramic antenna"*; the sensitivity claims the chain supports |
diff --git a/components/generic/kh3216-a35-chip-antenna/README.md b/components/generic/kh3216-a35-chip-antenna/README.md
deleted file mode 100644
index b95b1bd..0000000
--- a/components/generic/kh3216-a35-chip-antenna/README.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# KH3216-A35 — 2.4 GHz chip antenna
-
-- **Manufacturer:** **Shenzhen Jinhangbiao Electronics Co., Ltd.** (深圳市金航标电子)
-  — the specification document's own cover and footer; their site is given in the
-  document footer as `http://www.BDS666.com`.
-- **Part:** `KH3216-A35`
-- **Document version:** **V1.2** (the specification's own version block)
-- **Function:** surface-mount ceramic/chip antenna for 2.4 GHz ISM.
-- **Research status:** identified from a **primary regulatory exhibit** —
-  the antenna report filed with FCC ID `2BTR9-X4C`. Retrieved **2026-09-11**.
-
-## Why this record exists
-
-This is the **first named RF component in the Xteink family**. Nothing in any
-firmware profile, teardown or vendor page names an antenna part; FCC antenna
-reports do, because §15.203 requires the antenna to be identified.
-
-## Specifications
-
-Read from the manufacturer's specification document as filed. **Manufacturer's
-own figures — not an independent measurement of the fitted part.**
-
-| Parameter | Value |
-|---|---|
-| Package / designation | `3216` — nominally 3.2 × 1.6 mm SMD |
-| Passband width | **100 MHz typ.** |
-| **Peak gain** | **2.30 dBi** |
-| Peak gain across band | 1.98 / **2.30** / 1.55 dBi (low / mid / high channel) |
-| Average gain across band | −0.23 / −0.36 / −0.51 dBi |
-| **Efficiency** | **70 % / 71.2 % / 69 %** |
-| V.S.W.R. | **≤ 2.0** |
-| Impedance | **50 Ω** |
-| Polarization | Linear |
-| Azimuth pattern | Omni-directional |
-| Post-reliability tolerance | ±5 MHz bandwidth, ±0.1 dBi gain, ±0.1 VSWR |
-
-The document also contains external dimensions and test-board pad dimensions, a
-matching-circuit evaluation board, radiation patterns, reliability test
-conditions, and reflow profile — **sections that were not transcribed** and are
-available in the retained exhibit.
-
-## Where the document is
-
-**Not held as a standalone file.** It is embedded as the whole of the FCC antenna
-exhibit, retained in the device record that caused the fetch:
-
-| | |
-|---|---|
-| Path | [`devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-antenna-report.pdf`](../../../devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-antenna-report.pdf) |
-| **SHA-256** | `720ce021f0d403a69e7095bb5ef29f393cb49a8ad4676f8e2652245ffbd355cb` |
-| **Bytes** | **1,548,468** |
-| Source URL | <https://fccid.io/2BTR9-X4C/Test-Report/Antenna-Report-9480914.pdf> |
-| Retrieved | **2026-09-11** (UA `WhatsApp/2.23.20.0`; desktop-Chrome UA is served 403) |
-| Validation | magic bytes `%PDF`; text layer cross-checked against the rendered heading |
-| Redistribution status | `unknown` — third-party submission published by a US federal agency |
-| Disposition | `repository`, unstaged |
-
-**This is a deliberate exception to the usual filing rule.** A component
-datasheet normally belongs in the component's own `artifacts/`. Here the document
-is not a standalone datasheet — it is an FCC exhibit whose identity, integrity
-and provenance are the *device's* certification record. Splitting it would create
-a second copy of the same bytes under a different name. **The component record
-points at the device's copy, with the hash, so the chain resolves from either
-end.**
-
-## No manufacturer portal was found
-
-`BDS666.com` was not reached this pass. No independent copy of the `KH3216-A35`
-specification was located outside the FCC filing. If the standalone document is
-ever needed, the FCC exhibit is a complete copy of it.
-
-## Used by
-
-### Xteink X4 Classic (`2BTR9-X4C`)
-
-→ [`devices/xteink/x4-classic/`](../../../devices/xteink/x4-classic/README.md)
-
-The only internal antenna in the X4 Classic, feeding the ESP32-S3's 2.4 GHz
-radio. The FCC grant covers **2412–2462 MHz** only — Wi-Fi 802.11b/g/n and BLE;
-**no 5 GHz**, consistent with the SoC.
-
-### Not the X4 Light
-
-The sibling [`X4 Light`](../../../devices/xteink/x4-light/README.md)
-(`2BTR9-X4L`, granted 2026-08-13) declares an internal antenna with a **maximum
-gain of 5.19 dBi** — more than twice this part's 2.30 dBi. **That is a different
-antenna**, and its part number is in an exhibit that was not fetched. Do not
-assume the two devices share this component.
-
-### Not established for the X3, X4 or X4 Pro
-
-Each has its own FCC antenna report; **none was fetched**. Their antennas are
-unidentified. The X4's FCC internal photographs show a **meandering PCB trace
-antenna** rather than a chip part, so at least one device in this family does not
-use a discrete antenna component at all.
diff --git a/components/generic/lmd4737t261-ac02-pdm-microphone/README.md b/components/generic/lmd4737t261-ac02-pdm-microphone/README.md
deleted file mode 100644
index 5e84e59..0000000
--- a/components/generic/lmd4737t261-ac02-pdm-microphone/README.md
+++ /dev/null
@@ -1,206 +0,0 @@
-# LMD4737T261-AC02 — PDM MEMS microphone
-
-> The single digital MEMS microphone fitted to the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), designator **`U1`** on schematic sheet 5 (the KEY / RGB / PDM sub-board). A **PDM** (pulse-density modulation) part with a `SELECT` channel-select pin, powered from a switched rail.
-> Research snapshot **2026-09-01**. **No datasheet, product page, distributor listing or manufacturer attribution could be found** — see [§5](#5-datasheet-search--negative-result). Everything below is read off the schematic, M5Stack's own specification, or M5Stack's firmware.
-
-> This record lives under `components/generic/` because the manufacturer is unidentified. Move it to `components/<manufacturer>/` if that changes.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[ESP]** | ESP32-S3 datasheet, held at [`components/espressif/esp32-s3r8/artifacts/`](../../espressif/esp32-s3r8/README.md) | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity — what is actually known
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marking / value string | **`LMD4737T261-AC02`** | **[SCH]** sheet 5, next to `U1`; **[DOC]** verbatim in the product specification |
-| Manufacturer | **Unknown** (§5) | — |
-| Function | **PDM digital MEMS microphone** | **[SCH]** pin names; **[DOC]** *"PDM microphone (LMD4737T261-AC02)"* |
-| Package | **6 pin/pad** bottom-port or top-port MEMS package (port orientation not established) | **[SCH]** — six pin markers |
-| Supply | `PDM_VDD` — a switched **3.3 V** rail (§3.2) | **[SCH]** |
-| Interface | **PDM**, single data line plus clock, with a channel-`SELECT` pin | **[SCH]** |
-
-**That is the complete list of established facts about the part itself.** Sensitivity, SNR, AOP, frequency response, current consumption, clock range, `SELECT` polarity and the port location are all **unknown** and are not guessed here.
-
-> ⚠ **Do not infer specifications from the part number.** `LMD4737T261-AC02` looks decomposable — `4737` could be a package dimension, `T261` a variant code, `-AC02` a revision — but no vendor scheme was found to confirm any reading (§5).
-
----
-
-## 2. What can be said generically about PDM MEMS microphones
-
-Since the specific part is undocumented, this section states what is true of the *class*, so that the board integration below is interpretable. **None of it is verified for this part.** **[INF]** throughout.
-
-- A PDM microphone outputs a **1-bit oversampled bitstream** on a single data line, clocked by the host. There is no register interface, no address, and no configuration.
-- Typical host clock is **1–3.25 MHz**; most parts also define a **sleep** threshold (clock below a few tens of kHz) and enter a low-power state.
-- **`SELECT` (also called `L/R`) chooses which clock phase the microphone drives.** Two microphones can share one data line: one tied low drives on the low phase, one tied high drives on the high phase. On a mono design the pin still has to be tied deliberately, because it decides *which half of each clock period* the data is valid in — and the host's PDM receiver must be configured to match.
-- Output is high-Z on the phase the part is not driving, which is what makes the two-microphone sharing work.
-- Decimation to PCM is the host's job — on the ESP32-S3 this is done by the I²S peripheral in PDM RX mode.
-
----
-
-## 3. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`U1`**, schematic **sheet 5** (`PaperMono KEY RGB.SchDoc`, dated 2026-04-14).
-
-Sheet 5 is a **separate sub-board** carrying the two user keys, the power button, the RGB indicator LED and this microphone. It connects to the mainboard through a 12-way (+4 mount) board-to-board pair: **`J1` = `AXE612124D`** on the sub-board, mating with **`J6` = `AXE512127D`** on sheet 4. **[SCH]**
-
-#### 3.1 Pinout as drawn **[SCH sheet 5]**
-
-| Pin | Name | Net |
-|---:|---|---|
-| 1 | `GND` | `GND` |
-| **2** | **`SELECT`** | ⚠ **not resolved** — see §3.4 |
-| 3 | `GND` | `GND` |
-| **4** | **`CLK`** | `G45_PDM_CLK` ← **`R4` = 22 Ω/1 %** ← ESP32-S3 **GPIO45** |
-| **5** | **`DAT`** | `G46_PDM_DAT` → **`R3` = 22 Ω/1 %** → ESP32-S3 **GPIO46** |
-| 6 | `VDD` | **`PDM_VDD`** ← **`L1` = 2 nH** (ferrite/inductor), with **`C2` = 100 nF/10 V** decoupling |
-
-Both signals cross the board-to-board connector: `J1`/`J6` pin **11** = `G46_PDM_DAT`, pin **12** = `G45_PDM_CLK`, pin **2** = `PDM_VDD`. **[SCH]**
-
-The 22 Ω series resistors on both lines are edge-rate damping — sensible on a signal pair that crosses a connector at megahertz rates.
-
-#### 3.2 The rail is switched, and that turns out to matter a great deal
-
-`PDM_VDD` is produced by **[`U21`, an AW35122FDR load switch](../../awinic/aw35122/README.md)** on sheet 4, from `3V3_L2`, enabled by **M5IOE1 `PYG12`**. **[SCH]**
-
-| Layer | Identifier | Evidence |
-|---|---|---|
-| Schematic enable net | `PYB_PDM_EN` | **[SCH]** `U17` pin 5/16 |
-| M5IOE1 pin | `PYG12` → `M5IOE1_PIN_12`, enum value **11** | **[DOC]**, **[SRC]** |
-| Firmware constant | `PDM_EN_PIN = M5IOE1_PIN_12` | **[SRC]** `hal_mic.cpp:13`, `hal_board.cpp:30` |
-| Decoupling | `C85` = 10 µF/10 V on the switch output | **[SCH]** |
-
-So the microphone is off unless firmware has explicitly turned it on over I²C, and it disappears entirely in the `L2 DeepSleep` power state. Sheet 1 lists `PDM_VDD` among the `L3B` rails.
-
-#### 3.3 ⚠ Both PDM signals land on ESP32-S3 **strapping pins**
-
-This is the most consequential integration fact on this record, and it is not documented by M5Stack.
-
-| Net | ESP32-S3 pin | Strap function **[ESP §3]** | Default |
-|---|---|---|---|
-| `G45_PDM_CLK` | **GPIO45** | **`VDD_SPI` voltage select** | Weak pull-**down**, bit value **0** → `VDD_SPI` = **3.3 V** from `VDD3P3_RTC` |
-| `G46_PDM_DAT` | **GPIO46** | **ROM messages printing control** | Weak pull-**down**, bit value **0** |
-
-The schematic labels both accordingly: `GPIO45[strap]` and `GPIO46[strap]` on sheet 3. **[SCH]**
-
-**Why GPIO45 is the dangerous one.** Per **[ESP]** Table 3-4, with `EFUSE_VDD_SPI_FORCE = 0` (the default), a **GPIO45 sampled high at reset selects `VDD_SPI` = 1.8 V**. `VDD_SPI` is the supply for the board's [XM25UH128DHIQT flash](../../xmc/xm25uh128dhiqt/README.md), which is a **2.3–3.6 V** part. A board that latched that strap high would come up with an under-volted flash and would not boot — with no diagnostic, because the failure is upstream of any code that could report it.
-
-**Why this board is safe, and what would break it.** `CLK` is an ESP32-S3 **output** and a microphone **input**, so the microphone never drives GPIO45. GPIO46 is the reverse — the microphone drives it — but **`PDM_VDD` is off at reset** (§3.2), so the microphone is unpowered and its output is high-Z, leaving GPIO46 to its internal weak pull-down. The strapping latches sample at Chip Reset and hold until power-down **[ESP §3]**.
-
-> ⚠ **The protection is the load switch, not the wiring.** Firmware that leaves `PDM_VDD` enabled across a soft reset re-exposes GPIO46 to whatever the microphone's `DAT` pin does while unclocked. That changes only the ROM-message destination, so it is a nuisance rather than a brick — but it is the kind of thing that makes "sometimes there is no boot log" reproducible only after using the microphone. **[INF]**
-
-**Reusing these two GPIOs on a derivative design is where the real risk sits.** GPIO45 is a poor choice for anything that can be driven high by an external device at power-up.
-
-#### 3.4 ⚠ `SELECT` is unresolved
-
-The schematic symbol names pin 2 `SELECT`, but the **external net was not recovered** from the PDF text layer — the words `GND` adjacent to it in the extraction are the symbol's own pin *names* for pins 1 and 3, not necessarily pin 2's net. **[SCH]**
-
-This is not a cosmetic gap. `SELECT` determines which clock phase the microphone drives (§2), and the ESP32-S3's I²S PDM receiver must be configured for the matching phase — get it wrong and you capture silence or noise, not quiet audio. M5Stack's `hal_mic.cpp` configures the I²S peripheral, so the answer is recoverable from firmware; it was not extracted in this pass.
-
-Recorded as an open question rather than assumed to be grounded (§6).
-
-#### 3.5 Firmware
-
-| Constant | Value | Source |
-|---|---|---|
-| `MIC_PDM_CLK_PIN` | **45** | `hal_mic.cpp:17` **[SRC]** |
-| `MIC_PDM_DATA_PIN` | **46** | `hal_mic.cpp:16` **[SRC]** |
-| `PDM_EN_PIN` | `M5IOE1_PIN_12` | `hal_mic.cpp:13` **[SRC]** |
-
-M5Stack's UserDemo includes a "mic wave" application among its fifteen demos, and the documentation site lists a `mic` API sub-page (not retrieved). **[SRC]**, **[DOC]**
-
-On ESP-IDF the receiver is the **I²S peripheral in PDM RX mode** (`i2s_pdm_rx`), which handles clock generation and decimation to PCM. No microphone driver exists or is needed — there is nothing to configure in the part.
-
----
-
-## 4. Integration pitfalls
-
-1. **Enable `PDM_VDD` before expecting data** (§3.2). An I²S PDM RX channel reading an unpowered microphone returns a stable, plausible-looking constant — not an error.
-2. **Match the I²S PDM slot to the `SELECT` strap** (§2, §3.4). The classic symptom of a mismatch is "the microphone works but the level is wrong / the audio is garbage".
-3. **GPIO45 is the `VDD_SPI` strap** (§3.3). Do not reuse it for anything that can drive high at reset.
-4. **Do not leave `PDM_VDD` on across a reset** if you care about ROM boot messages (§3.3).
-5. **PDM needs a continuous clock.** Stopping the clock puts most PDM microphones into a sleep state with a wake-up time of tens of milliseconds; the first samples after restarting the clock are not valid. **[INF]** — generic behaviour, unverified for this part.
-6. **There is no gain control, no register interface and no identification.** You cannot detect the microphone's presence in software; a dead microphone and a disabled rail look identical.
-
----
-
-## 5. Datasheet search — negative result
-
-**No datasheet, product page, distributor listing or manufacturer attribution was found for `LMD4737T261-AC02` or `LMD4737T261`.** This is a genuine negative result.
-
-Attempts on **2026-09-01**, Chrome 131 desktop User-Agent unless noted:
-
-| Service / host | Query | Result |
-|---|---|---|
-| `search.brave.com` | `LMD4737T261+microphone+datasheet` | HTTP 200 — **zero** results for the part. Returned generic PDM-microphone material instead: Adafruit PDM breakout, Analog Devices ADMP401/ADMP521, ST MP34DT06J / MP45DT02, TDK MEMS catalogue, Knowles selection guide |
-| `search.brave.com` | `LMD4737T261-AC02+PDM+microphone` | HTTP 200 — results are all **M5Stack's own pages** (`docs.m5stack.com`, `shop.m5stack.com`), a CNX-Software article, and The Pi Hut's listing. The string exists on the web **only** because M5Stack publishes it |
-| `search.brave.com` | `LMD4737T261` | HTTP 429 (rate limited) |
-| `search.naver.com` | `LMD4737T261` | HTTP 200 — four links, all M5Stack shop/doc pages or `manuals.plus` copies of them |
-| `www.google.com` | `LMD4737T261` | HTTP 200 but JavaScript-gated; no result links in the HTML |
-| `duckduckgo.com/html`, `html.duckduckgo.com` | `LMD4737T261` | HTTP 202 challenge page |
-| `www.mojeek.com` | `LMD4737T261` | HTTP 403 |
-| `searx.be`, `search.inetol.net`, `priv.au`, `searxng.site`, `opnxng.com` | `LMD4737T261` | HTTP 429 or empty |
-| `api.qwant.com/v3/search/web` | `LMD4737T261` | HTTP 403 |
-| `www.alldatasheet.com` | `Searchword=LMD4737T261` | HTTP 403 |
-| `www.datasheets360.com` | `q=LMD4737T261` | HTTP 403 |
-| `www.findchips.com`, `www.oneyac.com` | `LMD4737T261-AC02` | HTTP 200 but JavaScript-rendered; the string appears only echoed in page metadata |
-| `www.oemsecrets.com` | `compare/LMD4737T261-AC02` | HTTP 403 |
-| `www.lcsc.com/search` | `LMD4737T261` | Identical 97 240-byte JavaScript shell returned for every query; the LCSC search API hosts return HTTP 403 |
-
-**The finding inside the negative result:** the only occurrences of this part number anywhere on the indexed web are **M5Stack's own specification text and pages that copy it.** No manufacturer publishes it, no distributor stocks it under that name. That pattern is consistent with a house part number, a customer-specific marking, or a part sold only through Chinese domestic channels that the searched indexes do not cover.
-
-**What would resolve it, in order of likely success:**
-
-1. **A photograph of the fitted `U1`.** MEMS microphones carry a small laser marking that usually identifies the maker.
-2. A PaperMono BOM. M5Stack has not published one — the `M5_Hardware` repository stops at SKU C152 and contains no C153 directory (verified exhaustively).
-3. Chinese-language search on Baidu or 1688/Alibaba domestic listings, which were not effectively reachable from this session.
-4. Comparing the schematic's 6-pin symbol and pad geometry against known MEMS microphone footprints, if the PCB files ever appear.
-
-**What is *not* blocked by this gap:** the wiring, the power control, the strapping-pin hazard and the firmware pin map are all fully established (§3). What is blocked is any statement about audio quality, current draw, or the valid clock range — which is why none is made.
-
----
-
-## 6. Open questions
-
-- Manufacturer and datasheet (§5).
-- **The `SELECT` net and therefore the correct I²S PDM slot** (§3.4). Recoverable from `hal_mic.cpp`'s I²S configuration; not extracted this pass. This is the highest-value cheap follow-up.
-- Sensitivity, SNR, acoustic overload point, supply current, valid clock range, wake-up time — all unknown.
-- Port orientation (top or bottom) and therefore what the enclosure acoustic path looks like.
-- Whether the 2 nH `L1` in the supply is a ferrite bead (RF decoupling) or an actual inductor; the schematic value string says `2nH`.
-- No hardware measurement of anything.
-
----
-
-## Related pages
-
-- [Awinic AW35122](../../awinic/aw35122/README.md) — `U21`, the load switch producing `PDM_VDD`
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — owns `PYG12`
-- [Espressif ESP32-S3R8](../../espressif/esp32-s3r8/README.md) — the I²S PDM receiver, and the owner of the two strapping pins
-- [XMC XM25UH128DHIQT](../../xmc/xm25uh128dhiqt/README.md) — the flash whose supply the GPIO45 strap selects
-- [MEMSensing MSM261D4030H1CPM](../../memsensing/msm261d4030h1cpm/README.md) · [MSM261D3526H1CPM](../../memsensing/msm261d3526h1cpm/README.md) — comparable PDM MEMS microphones documented in this repository, useful as a reference for what a datasheet for this class contains
-- [RS-C1415MBAR RGB LED](../rs-c1415mbar-rgb-led/README.md) — the other undocumented part on the same sub-board
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, sheet 5 dated 2026-04-14 | The value string, six-pin symbol with `GND`/`SELECT`/`GND`/`CLK`/`DAT`/`VDD`, `R3`/`R4` = 22 Ω, `L1` = 2 nH, `C2` = 100 nF, the `J1`/`J6` board-to-board mapping | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | PaperMono product page | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | *"PDM microphone LMD4737T261-AC02"* in the specification table | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono.html` |
-| S3 | `M5PaperMono-UserDemo/main/hal/hal_mic.cpp`, `hal_board.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | `main` @ `c1099107271d31a0678d661a896e2b04dbb331ea`, MIT | `MIC_PDM_CLK_PIN = 45`, `MIC_PDM_DATA_PIN = 46`, `PDM_EN_PIN = M5IOE1_PIN_12` | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-| S4 | ESP32-S3 Series Datasheet §3, Tables 3-1 and 3-4 | Espressif | primary | datasheet | <https://www.espressif.com/sites/default/files/documentation/esp32-s3_datasheet_en.pdf> | 2026-08-21 (existing repository copy) | v2.2, 87 pp | GPIO45/GPIO46 strapping defaults and the `VDD_SPI` voltage-control table in §3.3 | `components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet.pdf` |
-
-**Local artifacts:** none. No document specific to this part exists to store (§5).
-
-**Method note.** The pin table in §3.1 was recovered by parsing the Altium PDF's invisible pin-instance markers and reading the human-readable text sharing each marker's row band. That recovers text adjacency, not connectivity — which is precisely why `SELECT`'s net is marked unresolved (§3.4) rather than reported as `GND`.
diff --git a/components/generic/micro-sd-sdmmc/README.md b/components/generic/micro-sd-sdmmc/README.md
index a7e51ea..8aa2c5b 100644
--- a/components/generic/micro-sd-sdmmc/README.md
+++ b/components/generic/micro-sd-sdmmc/README.md
@@ -333,18 +333,6 @@ Cheap counterfeit cards are the single most common cause of unexplained SD troub
 
 - [Waveshare ESP32-S3-Knob-Touch-LCD-1.8](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) — `CARD1`, ESP32-S3 SDMMC 4-bit on GPIO2/3/4/5/6/42
 
-### LilyGO T-Display K230 / Kit — [`devices/lilygo/t-display-k230`](../../../devices/lilygo/t-display-k230/README.md) · *added 2026-09-07*
-
-K230 **MMC1**: `CMD` `GPIO54`, `CLK` `GPIO55`, `D0`–`D3` `GPIO56`–`GPIO59`, 4-bit.
-
-**The card is the boot medium *and* the root filesystem** — there is no on-board storage the
-system boots from, so card quality is system reliability and removal while running pulls the
-rootfs. BSP v0.2.4 added an SD-expansion step for cards larger than the flashed image; before
-that the extra space was unused. Changing the boot medium away from SD is the board's **one
-confirmed bricking path**.
-
-*Source: `scratch/lilygo-k230/index-fragments.md` §F4.*
-
 ## Related pages
 
 - [Pinouts and buses](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/pinouts-and-buses.md)
diff --git a/components/generic/papermono-1150mah-liion-cell/README.md b/components/generic/papermono-1150mah-liion-cell/README.md
deleted file mode 100644
index a3db068..0000000
--- a/components/generic/papermono-1150mah-liion-cell/README.md
+++ /dev/null
@@ -1,326 +0,0 @@
-# PaperMono 1150 mAh Li-ion cell (maker and part **unidentified**)
-
-> The **1150 mAh single-cell lithium-ion battery** shipped in the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) **and** the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) (C153-Lite). It attaches at **`J2` on sheet 2** through a **2-pin** `CON2_SMD` connector.
-> Research snapshot **2026-09-01**. **The cell's maker, model, dimensions and protection arrangement are not published.** What *is* established is the connector, the charge path and — contrary to other wording in this repository — that **the temperature sensor is not in the pack** ([§5](#5--the-thermistor-is-not-in-the-pack)).
-> **No hardware was available. Nothing here was measured.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH-V]** | Read off sheet 2 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[SCH-T]** | Read from the schematic text layer | `executed-success` for the extraction |
-| **[DOC]** | `docs.m5stack.com` PaperMono / PaperMono-Lite product pages, retrieved 2026-09-01 | `not-tested` |
-| **[IP]** | Injoinic IP2315 datasheet, held under the [IP2315 record](../../injoinic/ip2315/README.md) | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| **Capacity** | **1150 mAh** | **[DOC]** |
-| Chemistry | Lithium-ion / lithium-polymer, **1S** | **[INF]** from the charger topology |
-| Nominal voltage | **3.7 V** (1S Li-ion convention) | **[INF]** |
-| Charge termination | **≈ 4.2 V** — the IP2315 is a 1S charger | **[IP]** |
-| Rail name | **`VBAT_L0`** | **[SCH-V]** |
-| **Connector** | **`J2`**, footprint **`CON2_SMD`**, **2 pins** | **[SCH-V]** |
-| Pin 1 | **GND** (−) | **[SCH-V]** |
-| Pin 2 | **`VBAT_L0`** (+) | **[SCH-V]** |
-| Local decoupling | **`C13` = 22 µF/10 V** across the connector | **[SCH-V]** |
-| Trace requirement | the schematic annotates **`20mil min`** on this net | **[SCH-V]** |
-| Charge current | sheet 1 annotates **`充电电流 0.5C`** — "charge current 0.5 C", ≈ **575 mA** | **[SCH-T]** |
-| **Same on both SKUs** | **yes — 1150 mAh on C153 and C153-Lite alike** | **[DOC]** |
-
-### 1.1 What is **not** established
-
-| Unknown | Why it matters |
-|---|---|
-| **Maker and model number** | No repair source; no way to match a replacement exactly |
-| **Physical dimensions** | A replacement must fit the enclosure. The dimension code is not published |
-| **Protection circuit (PCM/PCB) presence and thresholds** | §4 — this is the important one |
-| **Connector polarity as wired to the pack** | §3 — this is the dangerous one |
-| **Discharge C-rate and internal resistance** | Governs whether Wi-Fi TX bursts sag the rail |
-| **Cycle life, cell vendor grade** | Governs long-term capacity retention |
-
-**No part number is guessed.** M5Stack publishes a capacity and nothing else.
-
----
-
-## 2. ⚠ Not the same cell as `components/generic/lipo-102035`
-
-This repository already contains a record for an
-**[LiPo 102035 battery](../lipo-102035/README.md)**. It is a **different cell for
-a different board** and the two must not be conflated:
-
-| | **This record** | [`lipo-102035`](../lipo-102035/README.md) |
-|---|---|---|
-| Device | **M5Stack PaperMono** (C153) and PaperMono-Lite | **Waveshare ESP32-S3-Knob-Touch-LCD-1.8** |
-| Designation | none published | `102035` (a dimension code) |
-| Capacity | **1150 mAh, stated by the vendor** | **unknown** — that record works with 500 mAh as an explicitly-labelled placeholder |
-| Supplied with the device? | **yes, fitted** | **no** — an optional accessory |
-| Connector | **`J2`, `CON2_SMD`, 2-pin, designator known** | designator not legible in the published sheets; **PH1.25 vs PH2.0 unresolved** |
-| Charger | **[IP2315](../../injoinic/ip2315/README.md), identified** | **no charger IC identifiable in the published sheets** |
-
-**They are cross-linked rather than merged**, because almost everything specific
-differs. What the two records genuinely share is the *class* of problem — an
-unidentified single-cell Li-ion behind an under-documented connector — and the
-`lipo-102035` record's
-[safety section](../lipo-102035/README.md#7-safety) and
-[connector-polarity warning](../lipo-102035/README.md#3-connector--also-unresolved-and-this-one-is-dangerous)
-apply here in full.
-
----
-
-## 3. ⚠ Connector polarity — verify before connecting anything
-
-The schematic establishes the **board side** unambiguously **[SCH-V]**:
-
-```
-        J2  "CON2_SMD"          20mil min
-   ┌──────────┐
-   │    2  ●──┼───────────────┬────── VBAT_L0   (+)
-   │          │               │
-   │    1  ●──┼───────────────┼─┬──── GND       (−)
-   └──────────┘               │ │
-      "Battery"           C13 22 µF/10 V
-```
-
-**Pin 2 is positive, pin 1 is negative.**
-
-**It does not establish the pack side.** There is **no industry-wide polarity
-convention for two-pin lithium-cell connectors** — some vendors wire red to pin 1
-and some to pin 2, and the housings are mechanically identical either way.
-
-> **Before connecting any replacement cell, check polarity with a meter against
-> the board's own pin 1 / pin 2.** Reversed connection of a lithium cell into a
-> charger input is a fire risk, not a "it does not work" outcome. This is the
-> single highest-risk item on this page.
-
-The connector's own part is also unidentified — `CON2_SMD` is a footprint name,
-not an orderable part — so **the housing family (PH1.25, PH2.0, ZH1.5 or other)
-is unknown**, and a replacement lead cannot be specified from this record.
-
----
-
-## 4. ⚠ Protection: what the board does, and what it does not
-
-**The board provides charge control. It does not provide cell protection.**
-
-| Function | Provided by | Where |
-|---|---|---|
-| CC/CV charging to ~4.2 V | **[IP2315](../../injoinic/ip2315/README.md)** synchronous buck charger | `U1`, sheet 2 |
-| Charge current programming | `R17` = 15 kΩ on `ICHGSET` | sheet 2 — ⚠ **not a datasheet-tabulated value**, see the [thermistor record §2.3](../100k-rntc-thermistor/README.md#23-a-related-resolution-from-the-same-render) |
-| Temperature qualification | **[`100K-RNTC`](../100k-rntc-thermistor/README.md)** `R15` ∥ `R16` = 82 kΩ on the charger's `NTC` pin | sheet 2 — ⚠ **§5** |
-| Input over-voltage | [AW32901FCR](../../awinic/aw32901/README.md), 5.95 V threshold | `U2`, sheet 2 |
-| Battery voltage measurement | the [`Q1` CJ3439KDW gated divider](../../changjing/cj3439kdw/README.md#3-what-it-actually-switches-sch-v) → M5PM1 `BAT_ADC` | sheet 2 |
-| **Over-discharge cut-off** | **not on the schematic** | — |
-| **Over-current / short-circuit cut-off** | **not on the schematic** | — |
-| **Cell over-voltage backstop** | **not on the schematic** | — |
-
-The last three are the functions of a **pack-mounted protection circuit (PCM)**,
-which single-cell pouch cells normally ship with, bonded to the tab and hidden
-under the yellow tape. **Its presence here is `inferred`, not established** — a
-2-pin connector is exactly what a PCM-protected pouch cell presents, and shipping
-an unprotected cell in a consumer product would be unusual. But nothing in the
-published evidence confirms it.
-
-**Practical consequence:** if a replacement cell is fitted **without** a PCM, the
-board will happily charge it and the ESP32-S3 will happily discharge it, with no
-hardware backstop at either end. The M5PM1's low-voltage handling is a firmware
-behaviour, not a protection circuit.
-
-> **Only fit protected cells.** `inferred` reasoning, stated as a safety
-> recommendation rather than a finding.
-
----
-
-## 5. ⚠ The thermistor is **not** in the pack
-
-**This contradicts wording in several other records in this repository, and it is
-recorded as a conflict rather than silently corrected.**
-
-The following places describe the battery as NTC-sensed and place the thermistor
-at `J2`:
-
-| Where | Wording |
-|---|---|
-| [`README.md`](../../../devices/m5stack/papermono/README.md) | "Battery \| 1150 mAh Li-ion, **NTC-sensed**" |
-| [`features/battery-and-charging.md`](../../../devices/m5stack/papermono/features/battery-and-charging.md) | "battery (**J2**, 1150 mAh **+ 100K NTC**)"; "Cell \| 1150 mAh Li-ion **at `J2`**, `100K-RNTC` thermistor" |
-| [`pinouts-and-buses.md`](../../../devices/m5stack/papermono/pinouts-and-buses.md) | "`J2` … Battery, **with a `100K-RNTC` thermistor**" |
-
-**The schematic does not support that.** **[SCH-V]**
-
-| Claim | Evidence |
-|---|---|
-| **`J2` has exactly two contacts** | Rendered at 200 dpi: a 2-pin symbol, pin 2 → `VBAT_L0`, pin 1 → GND, `CON2_SMD` beneath, `C13` across. **No third contact exists**, so no thermistor wire can reach the board |
-| **`R15` is a mainboard component** | It carries a sheet-2 `R`-series designator, sits beside the IP2315, and connects the charger's `NTC` pin (26) to ground in parallel with `R16` |
-
-So the temperature qualification measures **board temperature near the charger**,
-not cell temperature. Two consequences, both `inferred`, both safety-relevant:
-
-1. **A cell entering thermal runaway heats much faster than the PCB beneath it.**
-   A board-mounted sensor responds late, or not at all, to the failure it exists
-   to catch. Conversely, a warm charger could inhibit charging while the cell is
-   perfectly cool.
-2. **A replacement cell does not need a thermistor**, and a 3-wire pack would gain
-   nothing — there is nowhere for the third wire to go.
-
-**Unresolved, deliberately.** M5Stack may place `R15` physically under or beside
-the cell so that it is thermally coupled — a legitimate design when the pack has
-no NTC, and one that no schematic can show. **A board photograph or a thermal
-measurement settles it; neither was available.**
-
-Pending that, the accurate phrasing is *"the charger performs NTC-based
-temperature qualification"* rather than *"the pack contains a thermistor"*.
-Date 2026-09-01. Full detail in the
-[thermistor record §4](../100k-rntc-thermistor/README.md#4--conflict-this-does-not-measure-the-cell)
-and
-[BOM §11](../../../devices/m5stack/papermono/bill-of-materials.md#11--conflict-raised-by-this-pass--the-ntc-does-not-measure-the-cell).
-
----
-
-## 6. Charge current — 0.5 C, and one loose end
-
-Sheet 1's block diagram annotates the charging block **`充电电流 0.5C`**
-("charge current 0.5 C"). **[SCH-T]** At 1150 mAh that is **≈ 575 mA**, a
-conservative and cell-friendly rate: a full charge from empty takes roughly
-**2–2.5 hours** including the CV tail. **[INF]**
-
-**But the programming resistor does not corroborate it.** `R17` = **15 kΩ** sits
-on the IP2315's `ICHGSET` pin **[SCH-V]**, and **15 kΩ is not one of the four
-values the IP2315 datasheet tabulates** (51 k / 130 k / 180 k / NC) **[IP]**. Of
-those, 51 kΩ / 500 mA is the closest to 0.5 C.
-
-**The conflict is unresolved.** Either the datasheet's table is not exhaustive,
-or the resistor selects something the held datasheet version does not describe.
-It is tracked in the
-[IP2315 record](../../injoinic/ip2315/README.md#4-2--the-ntc-and-ichgset-network)
-and this record does not resolve it. **Do not quote a charge current in
-milliamps as established.**
-
-Note also that the charger is **fed from 5 V only** — the
-[USB-C CC resistors are plain 5.1 kΩ pulldowns and the IP2315's own CC pins are
-depopulated](../typec-302-brp16sc08/README.md#32--the-cc-arrangement-a-plain-sink-and-no-usb-pd--twice-over) —
-so no adapter can shorten the charge time.
-
----
-
-## 7. Runtime — what can and cannot be said
-
-**Nothing here is measured**, and no current figure for this board exists in any
-source held. What *can* be said:
-
-- **1150 mAh at 3.7 V ≈ 4.26 Wh.**
-- Conversion losses are real: `VBAT_L0` feeds the
-  [JW5712 buck](../../joulwatt/jw5712/README.md) to make `3V3_L2`, and several
-  [SSP7615 LDOs](../ssp7615-33dfr/README.md) elsewhere. An 85–90 % end-to-end
-  figure is the usual working assumption.
-- The board's deep-sleep architecture is unusually thorough — five power levels,
-  the [M5PM1](../../m5stack/m5pm1/README.md) able to unpower the ESP32-S3
-  entirely, and a **[gated battery-sense divider](../../changjing/cj3439kdw/README.md#31-why-the-gate-exists-and-why-it-is-worth-1-kω--1-kω)**
-  that exists purely to avoid ~1.85 mA of standing drain. That last detail is
-  itself evidence that standby current was taken seriously.
-- **Known standing drains identified by this pass:** ~4 µA through `R3` = 1 MΩ in
-  the sense-divider gate, and up to 0.3–1.2 mA of reverse leakage through
-  [`D2`](../../rohm/rb162vam-20tr/README.md#12--the-reverse-leakage-is-large-and-it-is-a-standby-current-term)
-  *if* the frontlight rail is biased. Neither dominates on its own.
-
-**Refusing a runtime estimate is the honest position.** See
-[`features/battery-and-charging.md`](../../../devices/m5stack/papermono/features/battery-and-charging.md)
-for what the device record says.
-
----
-
-## 8. Used By
-
-### `devices/m5stack/papermono` — at `J2`, sheet 2
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-Fitted as shipped.
-
-### `devices/m5stack/papermono-lite`
-
-→ [M5Stack PaperMono-Lite (C153-Lite)](../../../devices/m5stack/papermono-lite/README.md).
-**The same 1150 mAh cell** — explicitly, on both product pages, and noted in the
-[compatibility record](../../../devices/m5stack/papermono/compatibility-and-status.md):
-*"including the 1150 mAh battery — the Lite does not get a smaller cell."*
-**[DOC]** The Lite's schematic is published only as a 4-sheet `PRJ` PDF, so its
-`J2` wiring was **not** read directly; the connector is `inferred` to be the same.
-
----
-
-## 9. Safety
-
-In priority order. Most of this applies to any single-cell lithium device; the
-first two are specific to what this record establishes.
-
-1. **Verify connector polarity with a meter before first connection** (§3). Pin 2
-   is positive on the board side; the pack side is unknown.
-2. **Fit only protected cells** (§4). The board provides no over-discharge,
-   over-current or backstop over-voltage protection.
-3. **Do not assume the temperature interlock is watching the cell** (§5).
-4. **Match capacity and physical size conservatively.** A larger cell in the same
-   space is a mechanical hazard; a swollen or compressed pouch cell is a fire
-   risk. The enclosure's internal dimensions are not published.
-5. **Never charge a visibly swollen, punctured or previously over-discharged
-   cell.**
-6. **Charge at 0.5 C or less** if the cell's own rating is unknown (§6).
-
----
-
-## 10. Open questions
-
-- **Maker, model, dimensions** (§1.1).
-- **Whether the pack contains a PCM, and its thresholds** (§4).
-- **The pack-side connector polarity and housing family** (§3).
-- **Whether `R15` is thermally coupled to the cell** (§5) — the blocking question
-  for the safety argument.
-- **What charge current `R17` = 15 kΩ actually programs** (§6).
-- Internal resistance and discharge C-rate — determines rail sag during Wi-Fi TX.
-- No measurement of anything: no capacity test, no current draw, no runtime.
-
----
-
-## Manufacturer
-
-**Unidentified.** M5Stack publishes the capacity and nothing further; no cell
-vendor, model or dimension code appears on any product page, in the schematic, or
-in the module-size drawing held at
-`scratch/m5stack-papermono/pdf/C153_PaperMono_model_size.pdf`. **No search for a
-part number was attempted**, because there is no vendor-specific token to search
-on — the resolution path is a photograph of the cell's own label, or M5Stack's
-BOM, not a catalogue query.
-
-## Related pages
-
-- [`100K-RNTC` thermistor](../100k-rntc-thermistor/README.md) — the temperature sensor, and the §5 conflict in full
-- [Injoinic IP2315](../../injoinic/ip2315/README.md) — the charger
-- [Awinic AW32901FCR](../../awinic/aw32901/README.md) — input OVP ahead of the charger
-- [Changjing CJ3439KDW](../../changjing/cj3439kdw/README.md) — the gated divider that measures this cell
-- [Shikues SK2301AAT](../sk2301aat/README.md) — the USB-gated `VBAT_DET` tap
-- [XUNPU TYPEC-302-BRP16SC08](../typec-302-brp16sc08/README.md) — why charging is 5 V-only
-- [LiPo 102035](../lipo-102035/README.md) — a **different** cell on a **different** board (§2)
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — the power manager that owns battery measurement
-- [PaperMono battery and charging feature guide](../../../devices/m5stack/papermono/features/battery-and-charging.md) · [power architecture](../../../devices/m5stack/papermono/power-architecture.md) · [bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | **`J2` is 2-pin**, `CON2_SMD`, pin 2 = `VBAT_L0`, pin 1 = GND, `C13` = 22 µF/10 V, `20mil min`; `R15`/`R16`/`R17` placement; the `充电电流 0.5C` annotation | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| W1 | PaperMono product page | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | **1150 mAh** | `../../../scratch/m5stack-papermono/docs/pages/` |
-| W2 | PaperMono-Lite product page | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono%20Lite> | 2026-09-01 | — | **1150 mAh on the Lite too** | `../../../scratch/m5stack-papermono/docs/pages/` |
-| D1 | IP2315 datasheet | Injoinic | primary | see the [IP2315 record](../../injoinic/ip2315/README.md#manufacturer) | 2026-09-01 | V1.0 (cn), 16 pp | 1S CC/CV charging; the `ICHGSET` value table that 15 kΩ is absent from; the NTC worked example | `../../injoinic/ip2315/artifacts/` |
-
-**Local artifacts** — **none.** The cell is unidentified; there is no datasheet to
-hold, and this is a recorded negative result rather than an unattempted one.
-
-**Method note.** The `J2` pin count in §3 and §5 — the load-bearing observation in
-this record — was read from a **200 dpi PNG render** of schematic sheet 2 cropped
-to the connector. The text layer around `J2` mixes the connector's labels with
-`U4`, `C14`, `C15`, `Q2`, `Q5` and `R9`, and an earlier text-only pass could not
-have established the pin count from it.
diff --git a/components/generic/rf-balun-b0310j50100ahf/README.md b/components/generic/rf-balun-b0310j50100ahf/README.md
deleted file mode 100644
index ca28497..0000000
--- a/components/generic/rf-balun-b0310j50100ahf/README.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# RF balun `B0310J50100AHF`
-
-- **Category:** **balun / impedance transformer** — differential (balanced) to
-  single-ended (unbalanced), sub-1 GHz
-- **Research status:** ⚠ **manufacturer and datasheet not identified.** The part number is
-  read from a schematic comment. Everything in §2 is an **inference from the part-number
-  pattern** and should be treated as a hypothesis, not a fact.
-- **Retrieved:** 2026-09-04
-
-## 1. What is actually established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Schematic comment | **`B0310J50100AHF`** | Cap CC1101 schematic V0.3, `B1`, sheet 3 |
-| Pin names as drawn | `Unbalanced` (1), `GND` (2), **`Balanced`** (3), **`Balanced`** (4), `DNC` (5), `NC` (6) | schematic |
-| Function on the board | Converts the **CC1101's differential `RF_P`/`RF_N` port** to the single-ended path feeding the band-select switches and the SMA connector | schematic topology |
-| Associated network | `C42` 100 pF (RF_N series), `C46` 100 pF (RF_P series), `C43` 0.6 pF (differential), `L4` 3.3 nH, `L5` 6.8 nH ±5 %, `R5` 0 Ω, `C44` **DNP**, `C45`, `C47` 100 pF | schematic |
-
-## 2. ⚠ Inference about the part number — **not verified**
-
-The pattern `B<four digits><letter>J50100AHF` matches the naming convention used by
-**Anaren / TTM Technologies** for their balun product line, in which:
-
-- the four digits encode the **frequency range**, and
-- `50100` encodes the **impedance transformation, 50 Ω unbalanced ↔ 100 Ω balanced**.
-
-Under that reading, `0310` would mean **0.3 – 1.0 GHz** — which would exactly suit a board
-that must cover **315, 433, 868 and 915 MHz** through one balun and then switch the *matching*
-per band. The design's shape corroborates the reading: you would not fit three narrowband
-matching paths behind a *narrowband* balun.
-
-**This is `inferred` and unconfirmed.** No datasheet was located; the manufacturer was not
-identified; the six-pin footprint was not cross-checked against any published package. If a
-future pass finds the real part, this section should be replaced rather than edited.
-
-## 3. Why a balun is needed at all
-
-A CC1101 (like most sub-GHz transceivers) presents a **differential** RF port with an
-impedance that is neither 50 Ω nor single-ended. An antenna connector is 50 Ω
-single-ended. Something has to do three jobs at once:
-
-1. **Balanced → unbalanced** conversion, so common-mode currents do not radiate from the
-   feed;
-2. **impedance transformation**, here 100 Ω differential → 50 Ω single-ended;
-3. **harmonic filtering**, to the extent the network provides it.
-
-A discrete LC balun can do this cheaply for one band. A packaged wideband balun does it
-across a decade, at the cost of a component and some insertion loss — which is the trade
-this board makes in order to be multi-band.
-
-## 4. Used By
-
-### [M5Stack Cap CC1101 & NFC (U219)](../../../devices/m5stack/cap-cc1101/README.md) — designator `B1`, sheet 3
-
-Sits directly at the CC1101's `RF_P` (pin 12) / `RF_N` (pin 13) port and feeds the pair of
-[BGS13SN8](../../infineon/bgs13sn8/README.md) SP3T switches that select among the 315 MHz,
-433 MHz and 868/915 MHz matching paths, terminating at `E1`.
-
-Not used on any other board in this repository — the [Cap LoRa-1262](../../../devices/m5stack/cap-lora-1262/README.md)
-hides its RF front end inside the shielded `Stamp LoRa-1262 Mini` module, so whatever balun
-or matching it uses is invisible from outside.
-
-## 5. Gaps
-
-| # | Gap |
-|---|---|
-| 1 | **Manufacturer unidentified.** The Anaren/TTM reading in §2 is a pattern match, nothing more |
-| 2 | **No datasheet.** Insertion loss, amplitude/phase balance, power handling and the real frequency range are all unknown |
-| 3 | The `DNC` (5) and `NC` (6) pins' treatment on this board was not traced |
-| 4 | Whether `C44` being **DNP** implies a tuning option or a depopulated alternative topology is unknown |
-
-## 6. Sources
-
-| ID | Title | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|
-| BA-1 | Cap CC1101 schematic V0.3 | primary | [`devices/m5stack/cap-cc1101/artifacts/schematic/`](../../../devices/m5stack/cap-cc1101/artifacts/schematic/) | 2026-09-04 | The part number, pin names, and the surrounding network |
-| BA-2 | Cap CC1101 documentation | primary | `https://docs.m5stack.com/en/cap/Cap_CC1101` | 2026-09-04 | "multi-band RF matching circuits multiplex the 315/433/868/915 MHz bands to one RP-SMA antenna interface" — the design intent the balun serves |
diff --git a/components/generic/rp-sma-and-sma-antenna-connectors/README.md b/components/generic/rp-sma-and-sma-antenna-connectors/README.md
deleted file mode 100644
index ea379f6..0000000
--- a/components/generic/rp-sma-and-sma-antenna-connectors/README.md
+++ /dev/null
@@ -1,103 +0,0 @@
-# RP-SMA vs SMA antenna connectors (and the `SMA-KE` designation)
-
-- **Category:** generic **RF connector interface** — not a specific part number
-- **Why this record exists:** M5Stack's LoRa and sub-GHz Caps carry a board-edge antenna
-  connector that the vendor describes **inconsistently**, and owners repeatedly buy the
-  wrong antenna or an unnecessary adapter as a result. This page states the physics, the
-  evidence, and what is actually unresolved.
-- **Retrieved:** 2026-09-04
-
-## 1. The physics, in one table
-
-The confusing part is that "male/female" and "pin/socket" are **decoupled** in reverse-polarity
-variants. The *shell* determines male/female; the *centre contact* is what RP swaps.
-
-| Connector | Shell | Centre contact | Typical role |
-|---|---|---|---|
-| **SMA male (plug)** | outer thread | **pin** | on a cable / antenna |
-| **SMA female (jack)** | inner thread | **socket (hole)** | on a board |
-| **RP-SMA male (plug)** | outer thread | **socket (hole)** | on a cable / antenna |
-| **RP-SMA female (jack)** | inner thread | **pin** | on a board |
-
-Rules of thumb that follow:
-
-- **Inner thread + hole = standard SMA female.**
-- **Inner thread + pin = RP-SMA female.**
-- Wi-Fi gear is overwhelmingly RP-SMA (a historical regulatory artefact); LoRa and GNSS gear
-  is more often standard SMA. Mixing the two ecosystems is where adapters get bought.
-
-## 2. `SMA-KE` — the Chinese designation on M5Stack schematics
-
-M5Stack's schematics label the board-side connector:
-
-| Board | Designator | Schematic comment |
-|---|---|---|
-| [Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) | `E4` | **`SMA-KE`** |
-| [Cap CC1101 (U219)](../../../devices/m5stack/cap-cc1101/README.md) | `E1` | **`SMA-TH_KH-SMA-KE-Z`** |
-
-In Chinese connector nomenclature `K` (母 / *kǒng*-style suffixes) conventionally marks the
-**jack** side and `E`/`Z` denote body style and mounting. **`SMA-KE` therefore reads as "SMA
-jack", i.e. a *standard* SMA female — not RP-SMA.** That reading is `inferred` from
-nomenclature convention, not from a connector datasheet, and it is exactly the sort of
-inference that should be checked before being trusted.
-
-## 3. The conflict, laid out
-
-| Source | Says | Class |
-|---|---|---|
-| Cap LoRa-1262 docs, prose | *"equipped by default with an external **RP-SMA** antenna"* | primary |
-| Cap LoRa-1262 docs, spec row | *"Interface Type **RP-SMA (internal thread, internal hole)**"* — **internally contradictory** (see §1: inner thread + hole = *standard* SMA) | primary |
-| Cap LoRa-1262 **store** description | *"equipped by default with an external **SMA** antenna"* | primary |
-| Cap LoRa-1262 / CC1101 schematics | `SMA-KE`, `SMA-TH_KH-SMA-KE-Z` | primary |
-| Cap CC1101 docs, spec row | *"RP-SMA connector (internal thread, **female pin**)"* — **self-consistent as RP-SMA** | primary |
-| Unit C6L store spec | *"SMA connector (**female thread, female pin**)"* — again describes RP-SMA female | primary |
-| u/skinwill, 2025-12-30 | *"Looks like RP-SMA in the image."* | community, visual |
-| u/jader242, 2025-12-30 | *"It's still rp."* | community, assertion |
-| u/Big-Bunch2804, 2026-08-23 | *"Just so you know it's a rp-sma. They are a little specific."* | community, assertion |
-| **u/malonestar, 2025-11-24, with photo** | *"I think it is regular SMA female, I don't see any indications anywhere to RP-SMA… **Worked for me with a SMA antenna**."* | community, **firsthand with evidence** — but about the **U201**, not U214 |
-
-**Verdict: unresolved.** The strongest single piece of evidence is a photographed firsthand
-mating with a standard SMA antenna, but it is on the predecessor board. The vendor
-contradicts itself on the same page. Nobody has posted a close-up of the centre contact.
-
-**Would settle it:** one photograph of the connector's centre contact, or an M5Stack part
-number. Product photo `U214-Cap-LoRa-1262-main-pictures_02.webp` is held in the repository
-and **has not been inspected** — that is the cheapest next step.
-
-## 4. Practical guidance
-
-- **Buy a four-way SMA/RP-SMA adapter pack before you need one.** That is what owners
-  actually do; u/malonestar's link is to exactly such a pack.
-- **The band matters more than the polarity.** Every LoRa Cap ships an **868 MHz** whip;
-  North-American users on 915 MHz should plan on a second antenna
-  ([r/CardPuter 2026-08-22](https://old.reddit.com/r/CardPuter/comments/1vvlcs9/): *"new
-  antenna worked"*). The Cap CC1101, to M5Stack's credit, ships **three** whips.
-- **Never power a transmitter with no antenna.** M5Stack's own warning on the Cap LoRa-1262
-  page: *"Do not connect or power on the device without installing the antenna, otherwise
-  the device hardware may be permanently damaged!"*
-
-## 5. Used By
-
-| Board | Designator | Bands | Antenna supplied |
-|---|---|---|---|
-| [Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) | `E4` `SMA-KE` | 868–923 MHz | 1 × 868 MHz, 3 dBi, 108 × 9.3 mm |
-| [Cap LoRa868 (U201)](../../../devices/m5stack/cap-lora868/README.md) | not fetched | 868–923 MHz | 1 × 3 dBi, 108 × 9.3 mm |
-| [Cap CC1101 (U219)](../../../devices/m5stack/cap-cc1101/README.md) | `E1` `SMA-TH_KH-SMA-KE-Z` | 315/433/868/915 MHz | **3** — 315, 433, 868 MHz |
-| [Unit C6L (U202)](../../../devices/m5stack/unit-c6l/README.md) | — | 2.4 GHz + 868 MHz | 2 — Wi-Fi 84 mm, LoRa 108 mm |
-| [Unit LoRa E220](../../../devices/m5stack/unit-lora-e220/README.md) | — | 433 or 920 MHz | 1 × 2.5 dBi, 110 mm, **SMA male** stated |
-| [Unit LoRaWAN STM32WLE5](../../../devices/m5stack/unit-lorawan-stm32wle5/README.md) | — | per-SKU | 1 × 2.8 dBi, 195 mm, **SMA male** stated |
-| [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) | — | 868–923 MHz | **none — built-in FPC antenna**, no connector |
-
-Note the pattern: **Units state "SMA male" unambiguously; Caps do not.** The ambiguity is
-specific to the Cap product line.
-
-## 6. Sources
-
-| ID | Title | Class | URL | Retrieved |
-|---|---|---|---|---|
-| R-1 | Cap LoRa-1262 documentation + store JSON | primary | `docs.m5stack.com/en/cap/Cap_LoRa-1262`, `shop.m5stack.com/products/cap-lora-1262-….json` | 2026-09-04 |
-| R-2 | Cap CC1101 documentation | primary | `docs.m5stack.com/en/cap/Cap_CC1101` | 2026-09-04 |
-| R-3 | Cap LoRa-1262 / Cap CC1101 schematics | primary | held under the device records | 2026-09-04 |
-| R-4 | r/CardPuter "Cardputer adv up and running with Lora cap on US915" | community | `https://old.reddit.com/r/CardPuter/comments/1nkyy4c/` | 2026-09-04 |
-| R-5 | r/M5Stack "New Arrival Alert! Cap LoRa 1262" | community | `https://old.reddit.com/r/M5Stack/comments/1pzazbe/` | 2026-09-04 |
-| R-6 | r/CardPuter "cap lora issues" | community | `https://old.reddit.com/r/CardPuter/comments/1vvlcs9/` | 2026-09-04 |
diff --git a/components/generic/rs-c1415mbar-rgb-led/README.md b/components/generic/rs-c1415mbar-rgb-led/README.md
deleted file mode 100644
index 9915df7..0000000
--- a/components/generic/rs-c1415mbar-rgb-led/README.md
+++ /dev/null
@@ -1,243 +0,0 @@
-# RS-C1415MBAR — side RGB indicator LED
-
-> The three-die RGB indicator on the side of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) body, fitted as **`LED1`** on schematic sheet 5. A four-terminal common-cathode RGB LED with three individual series resistors.
-> Research snapshot **2026-09-01**. **No datasheet or manufacturer attribution could be found** — see [§6](#6-datasheet-search--negative-result).
-
-> **Headline finding:** this is **not** a fully addressable RGB indicator. The red die is driven from the [M5PM1](../../m5stack/m5pm1/README.md)'s `LED_EN_PP`, **which has no PWM mode**, while green and blue are on [M5IOE1](../../m5stack/m5ioe1/README.md) PWM channels. Red is therefore on/off only, and the achievable colour set is limited. M5Stack documents this — see [§4.3](#43--red-is-onoff-only-and-that-limits-the-colour-set).
-
-> This record lives under `components/generic/` because the manufacturer is unidentified. Move it to `components/<manufacturer>/` if that changes.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity — what is actually known
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marking / value string | **`RS-C1415MBAR`** | **[SCH]** sheet 5, next to `LED1` |
-| Manufacturer | **Unknown** (§6) | — |
-| Function | **RGB indicator LED**, three dies in one package | **[DOC]**; **[SCH]** |
-| Terminals | **4** — three anodes plus a common cathode (§3.1) | **[SCH]** |
-| Configuration | **Common cathode**, high-side driven | **[SCH]** — pin 2 is the only pin on `GND` |
-| Package | Not established. A `1415` field in the part number *may* denote 1.4 × 1.5 mm, but no vendor scheme was found to confirm it | — |
-
-**Forward voltages, luminous intensity, viewing angle, maximum forward current, colour coordinates and thermal ratings are all unknown** and are not guessed here.
-
-> ⚠ **Do not decode the part number.** `RS-C1415MBAR` has fields that invite interpretation — `1415` as a package size, `MBAR` as a colour/bin code — but **no vendor scheme was found to confirm any of it** (§6).
-
----
-
-## 2. Why this part matters more than a typical indicator LED
-
-On most boards an RGB indicator is a footnote. Here it is not, for two reasons:
-
-1. **The three dies are driven by two different chips**, on two different power domains, with two different capabilities (§4).
-2. **It is the primary user-visible status output on a device whose display takes 0.07–4.71 s to refresh.** M5Stack's own download-mode instruction is *"press and hold the power button until the **red LED** blinks"* — i.e. the red die is the indicator that tells you the boot state before any code runs. **[DOC]**
-
----
-
-## 3. Wiring **[SCH sheet 5]**
-
-`LED1` sits on the **KEY / RGB / PDM sub-board** (`PaperMono KEY RGB.SchDoc`, dated 2026-04-14), together with the two user keys, the power button and the [PDM microphone](../lmd4737t261-ac02-pdm-microphone/README.md). It reaches the mainboard through the 12-way (+4 mount) board-to-board pair **`J1` = `AXE612124D`** ↔ **`J6` = `AXE512127D`** (sheet 4).
-
-### 3.1 Terminals and series resistors
-
-| `LED1` pin | Die | Series resistor | Driven from | Domain |
-|---:|---|---|---|---|
-| **1** | **Green** | **`R7` = 820 Ω / 1 %** | `PYB_LED_G` | M5IOE1 |
-| **2** | **Common cathode** | — | `GND` | — |
-| **3** | **Blue** | **`R6` = 560 Ω / 1 %** | `PYB_LED_B` | M5IOE1 |
-| **4** | **Red** | **`R8` = 1 kΩ / 1 %** | `PY_LED_R` | **M5PM1** |
-
-Board-to-board mapping **[SCH]**: `J1`/`J6` pin **5** = `PY_LED_R`, pin **7** = `PYB_LED_G`, pin **9** = `PYB_LED_B`. `C5` = 10 µF/10 V decouples the sub-board's `3V3_L2` feed.
-
-### 3.2 What the resistor values imply
-
-Three different values for three dies is the normal way to balance an RGB indicator, because red, green and blue dies have different forward voltages and different luminous efficiencies. **[INF]**
-
-Rough current estimates, assuming a 3.3 V drive and typical die forward voltages (V<sub>F</sub> ≈ 2.0 V red, ≈ 3.0 V green and blue) — **arithmetic only, the die V<sub>F</sub> values are not from any datasheet**:
-
-| Die | R | Approx. current |
-|---|---:|---:|
-| Red | 1 kΩ | ≈ 1.3 mA |
-| Green | 820 Ω | ≈ 0.4 mA |
-| Blue | 560 Ω | ≈ 0.5 mA |
-
-These are **sub-milliamp to low-milliamp** currents — an indicator sized for a battery device and for reading in a dark room, not a torch. The absolute values depend entirely on the unknown V<sub>F</sub>, and near the knee of a diode's curve a 0.2 V error in V<sub>F</sub> changes the current by tens of percent, so treat them as order-of-magnitude only. **[INF]**
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`LED1`**, schematic sheet 5. Described by M5Stack as *"the RGB LED indicator on the side of the PaperMono body"*. **[DOC]**
-
-#### 4.1 The three channels, in full
-
-| Die | Net | Driver | Pin | Capability | Power domain |
-|---|---|---|---|---|---|
-| **Red** | `PY_LED_R` | **[M5PM1](../../m5stack/m5pm1/README.md)** `U7` **pin 5** | `LED_EN_PP` | **On/off only — no PWM** | `3V3_L0`-domain logic; lights per M5PM1 default behaviour at power-on |
-| **Green** | `PYB_LED_G` | **[M5IOE1](../../m5stack/m5ioe1/README.md)** `U17` **pin 12** | **`PYG8_PWM2`** | PWM, channel 2 | `3V3_L2` |
-| **Blue** | `PYB_LED_B` | **M5IOE1** `U17` **pin 13** | **`PYG9_PWM1`** | PWM, channel 1 | `3V3_L2` |
-
-Corroborated three ways — the schematic **[SCH]**, M5Stack's PinMap **[DOC]**, and the firmware **[SRC]**:
-
-```
-RGB_GREEN_PIN = M5IOE1_PIN_8   →  M5IOE1_PWM_CH2     hal_board.cpp:25, :27
-RGB_BLUE_PIN  = M5IOE1_PIN_9   →  M5IOE1_PWM_CH1     hal_board.cpp:26, :28
-RGB_PWM_FREQ_HZ = 5000                               hal_board.cpp:24
-```
-
-The M5IOE1 library's own channel table matches the documentation's suffixes exactly — `M5IOE1_PWM_CH2 // IO8` and `M5IOE1_PWM_CH1 // IO9`. **[SRC]**
-
-#### 4.2 Note the PWM channel numbers are crossed
-
-Green is on **PWM channel 2** (`PYG8_PWM2`) and blue on **PWM channel 1** (`PYG9_PWM1`) — the channel numbers run opposite to the pin numbers. This is a real ordering in M5Stack's silicon mapping, not a transcription error, and it is confirmed by both the documentation and the library header. Anyone writing directly to `M5IOE1_REG_PWM1_DUTY_L` (`0x1B`) expecting green will get blue. **[SRC]**
-
-#### 4.3 ⚠ Red is on/off only, and that limits the colour set
-
-M5Stack states the constraint plainly:
-
-> *"The RGB LED indicator on the side of the PaperMono body consists of three color LED dies, with the red LED connected to `LED_EN_PP` of the M5PM1. After the device is powered on, it will light up according to the M5PM1 default behavior. **Since `LED_EN_PP` does not support PWM output mode configuration, the adjustable colors of this indicator will be limited.**"* **[DOC]**
-
-The schematic corroborates the pin: `PY_LED_R` reaches **M5PM1 `U7` pin 5**, whose symbol name is `LED_EN_PP` — a plain push-pull output, distinct from the M5PM1's PWM-capable `G3`/`G4` pins. **[SCH]**
-
-**What this actually costs you.** With red as a one-bit channel and green/blue as continuous ones, the reachable colour space collapses to **two surfaces rather than a volume**:
-
-| Red state | Reachable colours |
-|---|---|
-| **Off** | The full green↔blue plane: green, cyan, blue, and every mix — continuously dimmable |
-| **On** | Red at exactly one intensity, plus any green/blue mix on top of it: orange, pink, magenta, white-ish — but always with the same fixed red component |
-
-So the things you **cannot** do are: dim red, fade red in or out, produce a *dim* warm colour, or produce a colour whose red component sits between "none" and "full". A smooth red breathing pulse — the single most common firmware idiom for a status LED — is not achievable. **[INF]**
-
-**And there is a second-order effect.** The red die's fixed contribution is set by `R8` = 1 kΩ (§3.1). Once red is on, every colour containing it is anchored to that one red level; the perceived hue of "white" and "pink" is fixed by a resistor value, not by firmware.
-
-**Practical guidance for firmware on this board:**
-
-- Use **green/blue for continuous state** (progress, breathing, level indication) and **red purely as a binary alarm or mode flag**.
-- Do not attempt gamma-corrected colour blending that assumes three PWM channels; the result will be wrong in the red axis by construction.
-- Do not design a UI that depends on distinguishing "dim red" from "bright red".
-
-#### 4.4 Red and green/blue are on different power domains, so they die at different times
-
-`PY_LED_R` comes from the M5PM1, which runs on the always-on `3V3_L0` rail. `PYB_LED_G` / `PYB_LED_B` come from the M5IOE1, which runs on `3V3_L2` — a rail that is switched off in `L1 Standby` and `L0 Shipping`. **[SCH]**
-
-**Consequence:** in low-power states **red is the only channel that can be lit.** This is consistent with M5Stack's power-tree documentation, which lists *"RGB red"* among the L2/L3A loads and the whole *"RGB LED"* among the L3B loads — the red die is reachable from a lower power state than the other two. **[DOC]** It is also why the download-mode indicator is specifically the *red* LED (§2): at that point the M5IOE1 may not be running.
-
-#### 4.5 Board variant detection depends on this LED
-
-`M5PaperMono-UserDemo/main/hal/hal_board.cpp:160–172` distinguishes the PaperMono (C153) from the PaperMono-Lite (C153-Lite) at runtime, and **the first test is whether the RGB LED came up**:
-
-```c
-160: void Hal::detectBoardVariant()
-162:     if (!_rgb_ready) { _board_variant = BoardVariant::Lite; return; }
-```
-
-followed by an attempt to power the NFC rail. **[SRC]** So a hardware fault on the M5IOE1 PWM channels does not merely lose the indicator — it makes a Pro board report itself as a Lite.
-
-#### 4.6 Not to be confused with `LED1` on sheet 2
-
-There is a **second** designator `LED1` on schematic **sheet 2**, in the charger block, associated with the [IP2315](../../injoinic/ip2315/README.md)'s `LED1`/`LED3` battery-level indicator pins. **[SCH]** It is a different component on a different sheet with the same reference designator — a consequence of the board being drawn as several independent Altium documents. This record is about the **sheet 5** `LED1`.
-
----
-
-## 5. Drivers and software
-
-**No component-level driver** — three LED dies with series resistors. On the PaperMono:
-
-```cpp
-// green and blue, via the M5IOE1 PWM channels
-ioe1.setPwmFrequency(5000);
-ioe1.analogWrite(M5IOE1_PIN_8, duty);   // green, PWM channel 2
-ioe1.analogWrite(M5IOE1_PIN_9, duty);   // blue,  PWM channel 1
-
-// red, via the M5PM1 — on/off only
-pm1.setLedEnLevel(true);
-```
-
-> ⚠ **Pin-numbering trap.** M5IOE1 labels are 1-based, enum values 0-based — `M5IOE1_PIN_8 == 7` (`M5IOE1/src/M5IOE1.h`). Use the enum, never the raw number from documentation. **[SRC]**
-
-`pm1.setLedEnLevel(bool)` is also called during shutdown sequences to hold the red LED state across an M5PM1 power-off, alongside `ldoSetPowerHold()`. **[DOC]**
-
-Note that both the M5PM1 and the M5IOE1 also expose **NeoPixel** register blocks (`M5PM1_REG_NEO_*` at `0x50`/`0x60`–`0x9F`, `M5IOE1_REG_LED_*` at `0x24`/`0x30`–`0x6F`). **Those are not this part** — they drive addressable serial LEDs, which the PaperMono does not fit. They are generic features of M5Stack's firmware, present on this board but unused for `LED1`. **[INF]**
-
----
-
-## 6. Datasheet search — negative result
-
-**No datasheet, product page, distributor listing or manufacturer attribution was found for `RS-C1415MBAR`.** Genuine negative result.
-
-Attempts on **2026-09-01**, Chrome 131 desktop User-Agent unless noted:
-
-| Service / host | Query | Result |
-|---|---|---|
-| `search.brave.com` | `RS-C1415MBAR` | HTTP 429 (rate limited) on two attempts |
-| `search.brave.com` | `RS-C1415MBAR+RGB+LED+datasheet` | HTTP 429 |
-| `search.naver.com` | `RS-C1415MBAR` | HTTP 200 — three links, none relevant: a Korean marketplace, a Korean parts index, and a made-in-china listing for an unrelated **Nationstar RS-3535 RGB LED** |
-| `www.google.com` | `RS-C1415MBAR` | HTTP 200 but JavaScript-gated; no result links in the HTML |
-| `duckduckgo.com/html`, `html.duckduckgo.com` | `RS-C1415MBAR` | HTTP 202 challenge page |
-| `www.mojeek.com` | `RS-C1415MBAR` | HTTP 403 |
-| `searx.be`, `search.inetol.net`, `priv.au`, `searxng.site`, `opnxng.com` | `RS-C1415MBAR` | HTTP 429 or empty |
-| `api.qwant.com/v3/search/web` | `RS-C1415MBAR` | HTTP 403 |
-| `www.alldatasheet.com` | `Searchword=RS-C1415MBAR` | HTTP 403 |
-| `www.datasheets360.com` | `q=RS-C1415MBAR` | HTTP 403 |
-| `www.findchips.com`, `www.oneyac.com` | `RS-C1415MBAR` | HTTP 200 but JavaScript-rendered; string echoed only in page metadata |
-| `www.oemsecrets.com` | `compare/RS-C1415MBAR` | HTTP 403 |
-| `www.lcsc.com/search` | `RS-C1415MBAR` | Identical 97 240-byte JavaScript shell returned for every query; LCSC's search API hosts return HTTP 403 |
-
-**One weak lead, recorded but not endorsed.** The Naver search surfaced *"Nationstar RS-3535 RGB LED"* — Nationstar Optoelectronics (国星光电) uses an `RS-` prefix for RGB LED product lines. That is a **prefix coincidence, not an identification**, and `RS-C1415MBAR` does not appear in any Nationstar material found. It is noted only so the next agent can rule it in or out quickly rather than rediscovering the same hint.
-
-**What would resolve it, in order of likely success:**
-
-1. **A photograph of the fitted `LED1`.** RGB LED packages of this size are usually unmarked, so this may not help — but the package outline would at least establish the dimensions.
-2. A PaperMono BOM. M5Stack has not published one — `M5_Hardware` stops at SKU C152 and has no C153 directory (verified exhaustively).
-3. A Chinese-language search on Baidu or 1688 domestic listings; not effectively reachable from this session.
-4. Searching Nationstar's own catalogue for a `C1415` series.
-
-**What is *not* blocked:** everything that matters for firmware — the pin map, the driver assignment, the PWM channels, the red-channel limitation and the power-domain split (§4) — is fully established. What is blocked is the photometric and electrical specification, which is why §3.2's currents are labelled as estimates.
-
----
-
-## 7. Open questions
-
-- Manufacturer and datasheet (§6); whether the Nationstar `RS-` prefix lead goes anywhere.
-- Forward voltages, and therefore the actual per-die currents (§3.2).
-- Package dimensions and whether it is top- or side-emitting — the indicator is described as being *"on the side of the body"*, which usually implies a side-emitting package or a light pipe, but that was not established. **[INF]**
-- What the M5PM1's *"default behavior"* for the red LED at power-on actually is (**[DOC]** says only that it exists).
-- Whether M5GFX or M5Unified expose a colour API that hides the red-channel limitation, or whether applications must handle it.
-- No hardware measurement or photograph.
-
----
-
-## Related pages
-
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — drives the red die from `LED_EN_PP`; `setLedEnLevel()`
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — drives green and blue from `PYG8_PWM2` / `PYG9_PWM1`
-- [LMD4737T261-AC02 PDM microphone](../lmd4737t261-ac02-pdm-microphone/README.md) — the other undocumented part on the same sub-board
-- [Normand SK6805-EC20](../../normand/sk6805-ec20/README.md) — an addressable RGB LED documented in this repository, for contrast with this simple three-die part
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, sheet 5 dated 2026-04-14 | The value string, four-terminal common-cathode topology, `R6` = 560 Ω / `R7` = 820 Ω / `R8` = 1 kΩ, `PY_LED_R` → M5PM1 `U7` pin 5 `LED_EN_PP`, `PYB_LED_G`/`PYB_LED_B` → M5IOE1 `U17` pins 12/13, the `J1`/`J6` mapping | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | PaperMono product page — HMI PinMap and RGB note | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | The verbatim `LED_EN_PP` / no-PWM limitation quoted in §4.3; `PYG8_PWM2` / `PYG9_PWM1`; the red-LED download-mode indicator | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono.html` |
-| S3 | `M5PaperMono-UserDemo/main/hal/hal_board.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | `main` @ `c1099107271d31a0678d661a896e2b04dbb331ea`, MIT | `RGB_GREEN_PIN`/`RGB_BLUE_PIN` and their PWM channels (`:25–28`), `RGB_PWM_FREQ_HZ = 5000` (`:24`), the variant-detection dependency (`:160–172`) | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-| S4 | `M5IOE1/src/M5IOE1.h` | M5Stack | primary | repository | <https://github.com/m5stack/M5IOE1> | 2026-09-01 | `main` @ `846eec7d05e25c09013be2acdb8804487f48a62e`, MIT | `M5IOE1_PWM_CH2 // IO8`, `M5IOE1_PWM_CH1 // IO9`; the 1-based-label / 0-based-enum trap | `scratch/m5stack-papermono/repos/M5IOE1/` |
-| S5 | PaperMono M5PM1/M5IOE1 power-management page | M5Stack | primary | official page | <https://docs.m5stack.com/en/arduino/papermono/m5pm1_m5ioe1> | 2026-09-01 | — | The L0–L3B rail assignment placing "RGB red" at L2/L3A and the whole RGB LED at L3B (§4.4); `setLedEnLevel()` | `scratch/m5stack-papermono/docs/pages/en-arduino-papermono-m5pm1_m5ioe1.html` |
-
-**Local artifacts:** none. No document specific to this part exists to store (§6).
-
-**Method note.** The pin/net table in §3.1 was recovered by parsing the Altium PDF's invisible pin-instance markers. The red-channel limitation in §4.3 is corroborated independently by the schematic (pin name `LED_EN_PP` on a non-PWM M5PM1 pin) and by M5Stack's own prose, which is why it is stated as fact rather than inference; only the *consequences* for the reachable colour set are labelled **[INF]**.
diff --git a/components/generic/sk2301aat/README.md b/components/generic/sk2301aat/README.md
deleted file mode 100644
index 8778ad1..0000000
--- a/components/generic/sk2301aat/README.md
+++ /dev/null
@@ -1,264 +0,0 @@
-# Shikues SK2301AAT
-
-> **P-channel MOSFET**, −20 V, −2.1 A, 130 mΩ @ V<sub>GS</sub> = −4.5 V, TrenchFET, **SOT-523**, marking **`A1S`**.
-> Research snapshot **2026-09-01**. Fitted as **`Q5` on sheet 2** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), where it is the **high-side switch that connects the battery to the `VBAT_DET` net — and only while USB is plugged in**.
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Shikues `SK2301AAT` datasheet **REV.08**, local copy `artifacts/sk2301aat-shikues-lcsc-mirror.pdf` | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entry `C5334586`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 2 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and ratings
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`SK2301AAT`** | **[SCH-V]**, **[DS]** |
-| Manufacturer | **Shikues** | **[CAT]** |
-| LCSC part | `C5334586` | **[CAT]** |
-| Function | **P-channel** enhancement MOSFET, TrenchFET | **[DS]** |
-| Package | **SOT-523** | **[DS]** |
-| **Top marking** | **`A1S`** | **[DS]** |
-| V<sub>DS</sub> | **−20 V** | **[DS]** |
-| **V<sub>GS</sub>** | **±8 V** | **[DS]** |
-| I<sub>D</sub> continuous | **−2.1 A** | **[DS]** |
-| I<sub>DM</sub> pulsed | −4.8 A | **[DS]** |
-| I<sub>S</sub> (body diode) | −0.72 A | **[DS]** |
-| R<sub>DS(on)</sub> | **130 mΩ @ −4.5 V** | **[CAT]** |
-| P<sub>D</sub> | **0.35 W** | **[DS]** — LCSC lists 700 mW; §1.2 |
-| R<sub>θJA</sub> | 357 °C/W (t ≤ 5 s) | **[DS]** |
-| T<sub>J</sub> | 150 °C | **[DS]** |
-| T<sub>stg</sub> | −55 to +150 °C | **[DS]** |
-| Applications (vendor) | *"Load switch for portable devices; DC/DC converter"* | **[DS]** |
-
-### 1.1 Pinout **[DS]**
-
-| Pin | Function |
-|---:|---|
-| **1** | **GATE** |
-| **2** | **SOURCE** |
-| **3** | **DRAIN** |
-
-This ordering is what makes the §3 circuit reading unambiguous, and it was
-checked against the schematic symbol's own `S`/`G`/`D` labels, which agree.
-
-### 1.2 ⚠ A power-dissipation discrepancy between the datasheet and the distributor
-
-The datasheet's absolute-maximum table says **P<sub>D</sub> = 0.35 W**. LCSC's
-parametric field says **700 mW**. **[DS]** vs **[CAT]**
-
-Both numbers are plausible for SOT-523 depending on the pad area and pulse
-duration assumed — 0.35 W is a steady-state figure and 0.7 W typically a t ≤ 5 s
-or 1-inch-square-copper figure. **The discrepancy is recorded, not resolved.**
-Use **0.35 W** as the design figure: it is the manufacturer's, and it is the
-conservative one. On this board the dissipation is negligible either way (§3.2).
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — `Q5`, sheet 2
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-**One instance**, and it is the only P-channel device on the board outside the
-complementary pair inside
-[`Q1` CJ3439KDW](../../changjing/cj3439kdw/README.md).
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes**. The Lite drops only NFC and LoRa; the charging and battery
-sensing path is stated to be identical, including the same 1150 mAh cell. Not
-read from the Lite's own schematic.
-
----
-
-## 3. What it actually switches **[SCH-V]**
-
-Read from sheet 2 rendered at 200 dpi. `Q5` works with
-**`Q2`** ([SK2302AAT](../sk2302aat/README.md), N-channel) as a two-transistor
-level-shifting high-side switch:
-
-```
-                         VBAT_L0
-                            │
-                   R45 100 kΩ   ┌── Q5 pin 2  SOURCE
-                            ├───┤   SK2301AAT  (P-channel)
-                            │   └── Q5 pin 3  DRAIN ──── VBAT_DET
-                            │
-    VUSB_IN ── Q2 pin 1 ── Q5 pin 1 GATE
-      │        (GATE)
-   R9 100 kΩ   Q2 pin 3 DRAIN
-      │        Q2 pin 2 SOURCE ── GND
-     GND        SK2302AAT (N-channel)
-```
-
-| Terminal | Net |
-|---|---|
-| `Q5` pin 2 — **SOURCE** | **`VBAT_L0`** (the battery rail) |
-| `Q5` pin 3 — **DRAIN** | **`VBAT_DET`** |
-| `Q5` pin 1 — **GATE** | `Q2`'s drain, held at `VBAT_L0` by **`R45` = 100 kΩ** |
-| `Q2` pin 1 — **GATE** | **`VUSB_IN`**, held down by **`R9` = 100 kΩ** |
-
-**Operation:**
-
-| USB state | `Q2` | `Q5` gate | `Q5` | `VBAT_DET` |
-|---|---|---|---|---|
-| **Unplugged** — `VUSB_IN` ≈ 0 V | off (`R9` holds the gate at GND) | pulled to `VBAT_L0` by `R45` ⇒ V<sub>GS</sub> = 0 | **off** | **disconnected** |
-| **Plugged** — `VUSB_IN` ≈ 5 V | on | pulled to GND ⇒ V<sub>GS</sub> ≈ −V<sub>BAT</sub> | **on** | **= `VBAT_L0`** |
-
-So: **`VBAT_DET` carries the battery voltage only while USB power is present.**
-`Q2` is doing nothing but detecting USB presence and inverting it; `Q5` is the
-actual switch.
-
-### 3.1 Why build it this way
-
-A P-channel high-side switch cannot be driven directly from a logic level
-referenced to ground when its source sits at V<sub>BAT</sub> — pulling the gate
-to 3.3 V would leave V<sub>GS</sub> ≈ −0.9 V at a 4.2 V cell, not enough to
-enhance it, and would leave it partly on at low cell voltage. The N-channel
-pull-down is the standard fix: it swings the gate the full V<sub>BAT</sub> and
-costs one transistor and two resistors. **[INF]**
-
-Using **`VUSB_IN` itself as the control signal** rather than a GPIO is the neat
-part. It makes the function **automatic and unpowered** — the detection works
-before any firmware runs, and it consumes nothing when USB is absent. **[INF]**
-
-### 3.2 Operating conditions on this board — the part is enormously de-rated
-
-| Parameter | Rating **[DS]** | On this board | Margin |
-|---|---|---|---|
-| V<sub>DS</sub> | −20 V | ≤ 4.35 V (a full 1S Li-ion) | **~4.6×** |
-| **V<sub>GS</sub>** | **±8 V** | ≤ 4.35 V | **~1.8×** |
-| I<sub>D</sub> | −2.1 A | a sense/detect current through a high-impedance node | ≫ |
-| P<sub>D</sub> | 0.35 W | negligible | ≫ |
-
-**V<sub>GS</sub> = ±8 V is the only rating worth watching**, and it is fine here
-because a 1S Li-ion cannot exceed ~4.35 V. It would **not** be fine in a 2S
-design, which is the first thing to check if this sub-circuit is copied.
-
----
-
-## 4. Where `VBAT_DET` goes — not established
-
-`VBAT_DET` also appears near the [IP2315 charger](../../injoinic/ip2315/README.md)
-block on sheet 2. **What consumes it was not resolved**: the text layer in that
-region interleaves the charger's, the OVP switch's and this circuit's labels, and
-the region was not re-rendered to settle it.
-
-Two readings, neither adopted:
-
-- a **battery-presence input** to the charger, which would let the charger
-  distinguish "no cell fitted" from "deeply discharged cell" — but only while USB
-  is present, which is exactly when the charger needs to know;
-- an **ADC sense point**, though the board already has a dedicated and better one
-  in the [`Q1`/`R5`/`R12` gated divider](../../changjing/cj3439kdw/README.md#3-what-it-actually-switches-sch-v)
-  feeding `BAT_ADC`.
-
-The **first is more plausible** — gating it on USB presence makes sense for a
-charger-side detect and makes little sense for a general voltage measurement.
-`inferred`, and listed as an open question.
-
----
-
-## 5. Substitution
-
-`2301` is a de-facto industry number for a small P-channel MOSFET, so drop-in
-equivalents are abundant — **but the package is not.**
-
-| Alternative | Package | Note |
-|---|---|---|
-| Vishay **Si2301CDS**, AOS **AO3401A**, Diodes **DMP2160U** | **SOT-23** | Electrically comparable or better; **larger footprint** |
-| UMW / Slkor / CJ `2301` parts | SOT-23 or SOT-523 | Chinese second sources; check the package suffix |
-| **Any SOT-523 P-channel ≥ 20 V, ≥ 0.5 A** | SOT-523 | What actually matters here |
-
-Required for this position: **P-channel**, |V<sub>DS</sub>| ≥ 20 V,
-**V<sub>GS</sub> ≥ ±8 V**, low-threshold (must enhance at 3.0 V of gate drive at
-a depleted cell), and **pin 1 = G, 2 = S, 3 = D** — SOT-523 pinouts are not
-universal across vendors and a mismatched one silently connects the body diode
-the wrong way round.
-
----
-
-## 6. Integration pitfalls
-
-1. **V<sub>GS</sub> = ±8 V only.** Fine at 1S; **not** at 2S (§3.2).
-2. **The body diode conducts even when the FET is off.** Source is `VBAT_L0`,
-   drain is `VBAT_DET`; the intrinsic diode points source→drain in a P-channel,
-   so `VBAT_DET` is never fully isolated from the cell — it sits about a diode
-   drop below it if something pulls it up. Not a problem for a sense node, but it
-   means "off" does not mean "open". **[INF]**
-3. **P<sub>D</sub>: 0.35 W or 0.7 W depending on the source** (§1.2).
-4. **`Q5` and `Q2` are a pair.** Replacing one without the other breaks the
-   polarity logic — `Q2` is N-channel, `Q5` is P-channel, and `SK2301AAT` and
-   [`SK2302AAT`](../sk2302aat/README.md) differ by **one digit** in the part
-   number while differing in channel type. That is an easy and destructive
-   confusion at a rework bench.
-5. **The control signal is a power rail, not a GPIO.** Firmware cannot disable
-   this path; there is no register for it.
-
----
-
-## 7. Open questions
-
-- **What consumes `VBAT_DET`** (§4) — the main gap in understanding this circuit.
-- The P<sub>D</sub> discrepancy (§1.2).
-- V<sub>GS(th)</sub> and R<sub>DS(on)</sub> at low gate drive, which govern
-  behaviour at a depleted cell — in the datasheet's electrical table, not
-  transcribed here.
-- No measurement of anything; the whole circuit is `inferred` from the drawing.
-
----
-
-## Manufacturer
-
-**Shikues.** No vendor sourcing guide exists in this repository yet.
-
-**⚠ Retrieval finding.** The datasheet is on **`wmsc.lcsc.com`** and **not** on
-`www.lcsc.com/datasheet/…`, which returns **HTTP 200 with `text/html`** under a
-`.pdf` URL. **Check the `%PDF` magic bytes, never the status code.** For this part
-the direct `wmsc` URL worked first try with a Chrome 131 UA; for its sibling
-[`SK2302AAT`](../sk2302aat/README.md) the `www.lcsc.com` form had to be rewritten
-to the `wmsc` form by hand. The rewrite is mechanical:
-
-```
-www.lcsc.com/datasheet/lcsc_datasheet_<stamp>_<name>_<code>.pdf
-  ->  wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/<stamp>_<name>_<code>.pdf
-```
-
-`executed-success`, 2026-09-01, on five parts. This belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## Related pages
-
-- [Shikues SK2302AAT](../sk2302aat/README.md) — **`Q2`, the N-channel half of this switch**, and `Q3` the buzzer driver
-- [Changjing CJ3439KDW](../../changjing/cj3439kdw/README.md) — `Q1`, the board's other two-transistor gated sense circuit
-- [Injoinic IP2315](../../injoinic/ip2315/README.md) — the charger `VBAT_DET` probably serves
-- [Awinic AW32901FCR](../../awinic/aw32901/README.md) — what produces `VUSB_IN`'s downstream rail
-- [PaperMono power architecture](../../../devices/m5stack/papermono/power-architecture.md) · [bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `SK2301AAT` P-Channel 20-V (D-S) MOSFET | Shikues (via LCSC CDN) | primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2311241453_Shikues-SK2301AAT_C5334586.pdf> | 2026-09-01 | **REV.08**, 4 pp | channel type, SOT-523, marking `A1S`, **pin 1 = G / 2 = S / 3 = D**, all §1 maxima | `artifacts/sk2301aat-shikues-lcsc-mirror.pdf` |
-| C1 | LCSC entry `C5334586` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `SK2301AAT` | 2026-09-01 | — | manufacturer; R<sub>DS(on)</sub> 130 mΩ @ 4.5 V; 290 pF / 29 pF; 3.9 nC; the 700 mW figure of §1.2 | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `Q5` = `SK2301AAT`; the §3 topology, `R45` = 100 kΩ, `R9` = 100 kΩ, `Q2` = SK2302AAT | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/sk2301aat-shikues-lcsc-mirror.pdf` | 580 924 | `427b287b6b7a9a50633b3e4e1963082f34c53a0e30484180c19a032c2662fe7a` | 4 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) with an intact text
-layer, and its pinout table is what makes §3 assertable rather than guessed. The
-circuit itself was read from a 200 dpi render of sheet 2 — the text layer in that
-region attributes labels to the wrong designators, and an earlier text-only pass
-produced a reading that the image refuted.
diff --git a/components/generic/sk2301aat/artifacts/sk2301aat-shikues-lcsc-mirror.pdf b/components/generic/sk2301aat/artifacts/sk2301aat-shikues-lcsc-mirror.pdf
deleted file mode 100644
index 6a181c7..0000000
Binary files a/components/generic/sk2301aat/artifacts/sk2301aat-shikues-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/generic/sk2302aat/README.md b/components/generic/sk2302aat/README.md
deleted file mode 100644
index 695cdf5..0000000
--- a/components/generic/sk2302aat/README.md
+++ /dev/null
@@ -1,262 +0,0 @@
-# Shikues SK2302AAT
-
-> **N-channel MOSFET**, 20 V, 2.1 A, 70 mΩ @ V<sub>GS</sub> = 2.5 V, TrenchFET, **SOT-523**, marking **`A2S`**.
-> Research snapshot **2026-09-01**. Used **twice** on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153): **`Q2` sheet 2** (the USB-presence half of the battery-detect switch) and **`Q3` sheet 4** (the **buzzer driver**).
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Shikues `SK2302AAT` datasheet **REV.08**, local copy `artifacts/sk2302aat-shikues-lcsc-mirror.pdf` | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entry `C475757`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off the schematic rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and ratings
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`SK2302AAT`** | **[SCH-V]**, **[DS]** |
-| Manufacturer | **Shikues** | **[CAT]** |
-| LCSC part | `C475757` | **[CAT]** |
-| Function | **N-channel** enhancement MOSFET, TrenchFET | **[DS]** |
-| Package | **SOT-523** | **[DS]** |
-| **Top marking** | **`A2S`** | **[DS]** |
-| V<sub>DS</sub> | **20 V** | **[DS]** |
-| **V<sub>GS</sub>** | **±8 V** | **[DS]** |
-| I<sub>D</sub> continuous | **2.1 A** | **[DS]** |
-| I<sub>S</sub> (body diode) | 0.6 A | **[DS]** |
-| R<sub>DS(on)</sub> | **70 mΩ @ 2.5 V** | **[CAT]** |
-| V<sub>GS(th)</sub> | 650 mV | **[CAT]** |
-| P<sub>D</sub> | **0.35 W** | **[DS]** — LCSC also says 350 mW; the two agree, unlike the [SK2301AAT](../sk2301aat/README.md#12--a-power-dissipation-discrepancy-between-the-datasheet-and-the-distributor) |
-| R<sub>θJA</sub> | 357 °C/W (t ≤ 5 s) | **[DS]** |
-| T<sub>J</sub> | 150 °C | **[DS]** |
-| T<sub>stg</sub> | −55 to +150 °C | **[DS]** |
-| Applications (vendor) | *"Load switch for portable devices; DC/DC converter"* | **[DS]** |
-
-### 1.1 Pinout **[DS]**
-
-| Pin | Function |
-|---:|---|
-| **1** | **GATE** |
-| **2** | **SOURCE** |
-| **3** | **DRAIN** |
-
-Same pin order as its P-channel sibling
-[`SK2301AAT`](../sk2301aat/README.md) — which is convenient for the two-transistor
-switch of §3.1 and dangerous at a rework bench, since **the two parts differ by
-one digit and by channel type**.
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — **2 instances**
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-
-| Ref | Sheet | Role | §|
-|---|---:|---|---|
-| **`Q2`** | 2 | USB-presence inverter driving the `Q5` high-side switch | §3.1 |
-| **`Q3`** | 4 | **buzzer low-side driver** | §3.2 |
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes, both**. The Lite drops only NFC and LoRa; both the battery
-detect path and the buzzer are retained. Not read from the Lite's own schematic.
-
----
-
-## 3. What each one switches **[SCH-V]**
-
-### 3.1 `Q2`, sheet 2 — USB-presence detection
-
-`Q2` is the low-side half of a two-transistor high-side switch whose pass element
-is **`Q5`** ([SK2301AAT](../sk2301aat/README.md), P-channel).
-
-| `Q2` terminal | Net |
-|---|---|
-| pin 1 **GATE** | **`VUSB_IN`**, with **`R9` = 100 kΩ** to GND |
-| pin 2 **SOURCE** | **GND** |
-| pin 3 **DRAIN** | **`Q5`'s gate**, pulled up to `VBAT_L0` by `R45` = 100 kΩ |
-
-When USB is plugged in, `VUSB_IN` rises, `Q2` turns on, `Q5`'s gate is pulled to
-ground, and `Q5` connects `VBAT_L0` to `VBAT_DET`. Unplugged, `R9` holds `Q2`
-off and `R45` holds `Q5` off. The full analysis, including why the circuit is
-built this way and where `VBAT_DET` goes, is in the
-[SK2301AAT record §3](../sk2301aat/README.md#3-what-it-actually-switches-sch-v).
-
-The gate is driven by **a power rail, not a GPIO** — the detection is automatic
-and works before firmware runs.
-
-### 3.2 `Q3`, sheet 4 — the buzzer driver
-
-This is a textbook low-side inductive-load driver, and reading it settles what
-three other parts on sheet 4 are for.
-
-```
-                       3V3_L1
-                          │
-                    ┌─────┴─────┐
-                    │  BUZZER1  │  "ER103", magnetic
-                    │  + ─── −  │
-                    └──┬─────┬──┘
-                       │     │
-                D3 ────┘     │      1N4148WS, cathode to +, anode to −
-             (flyback)       │
-                             │
-  G42_BB_PWM ──┬── Q3 pin 1 GATE
-               │   Q3 pin 3 DRAIN ──┘
-          R50 10 kΩ
-               │   Q3 pin 2 SOURCE ── GND
-              GND
-```
-
-| `Q3` terminal | Net |
-|---|---|
-| pin 1 **GATE** | **`G42_BB_PWM`** — ESP32-S3 **GPIO42**, with **`R50` = 10 kΩ** pulldown |
-| pin 2 **SOURCE** | **GND** |
-| pin 3 **DRAIN** | the buzzer's **`−`** terminal |
-
-The buzzer's `+` terminal sits on **`3V3_L1`**, and **`D3`**
-([1N4148WS](../1n4148ws/README.md)) is connected across the buzzer with its
-**anode on `Q3`'s drain and its cathode on the `3V3_L1` side** — the classic
-**flyback/freewheel diode** for an inductive load. **[SCH-V]**
-
-Three things follow that are useful when writing firmware or debugging:
-
-1. **`R50` = 10 kΩ is a gate pulldown, and it matters.** GPIO42 is high-Z during
-   reset and while the ESP32-S3 is held in reset by the
-   [M5PM1](../../m5stack/m5pm1/README.md). Without the pulldown the buzzer could
-   chirp on every boot. With it, the buzzer is silent unless firmware drives the
-   pin. **[INF]**
-2. **The buzzer runs from `3V3_L1`, not `3V3_L2`.** `3V3_L1` is a different power
-   domain from the main system rail, so **the buzzer's availability is tied to
-   `L1` being enabled**, independent of whether the application rail is up. Check
-   [`power-architecture.md`](../../../devices/m5stack/papermono/power-architecture.md)
-   before assuming a beep will sound in a given power state.
-3. **The buzzer symbol carries an explicit no-connect marker** (a red ✗) on one
-   of its terminals. That is a *positive assertion by the designer*, not an
-   omission — unlike the USB-C `SBU` stubs, which are simply left open. **[SCH-V]**
-
-### 3.3 Operating conditions — both instances are heavily de-rated
-
-| Parameter | Rating | `Q2` (sheet 2) | `Q3` (sheet 4) |
-|---|---|---|---|
-| V<sub>DS</sub> | 20 V | ≤ 4.35 V | ≤ 3.3 V + flyback (clamped by `D3`) |
-| **V<sub>GS</sub>** | **±8 V** | ≤ 5.5 V (`VUSB_IN`) | ≤ 3.3 V |
-| I<sub>D</sub> | 2.1 A | ~µA | a magnetic buzzer, tens of mA |
-| P<sub>D</sub> | 0.35 W | ~0 | ≪ |
-
-`Q2`'s gate sees `VUSB_IN`, which is USB V<sub>BUS</sub> **before** the
-[AW32901FCR](../../awinic/aw32901/README.md) OVP switch. That switch trips at
-**5.95 V**, so a fault could present up to that before it acts — still inside the
-±8 V V<sub>GS</sub> rating, but the margin is **1.3×**, not the comfortable 2.4×
-it looks like at nominal 5 V. It is the tightest rating on either instance.
-**[INF]**
-
----
-
-## 4. Substitution
-
-`2302` is a de-facto industry number for a small N-channel MOSFET.
-
-| Alternative | Package | Note |
-|---|---|---|
-| Vishay **Si2302CDS**, AOS **AO3400A** ([documented here](../../alpha-and-omega-semiconductor/ao3400a/README.md)), Diodes **DMN2075U** | **SOT-23** | Electrically equal or better; **larger footprint** |
-| UMW / Slkor / CJ `2302` parts | SOT-23 or SOT-523 | Chinese second sources; check the package suffix |
-| **Any SOT-523 N-channel ≥ 20 V, low-V<sub>GS(th)</sub>** | SOT-523 | What matters here |
-
-Required: **N-channel**, V<sub>DS</sub> ≥ 20 V, **V<sub>GS</sub> ≥ ±8 V**,
-logic-level threshold (must be fully on at 3.3 V of drive), pin order
-**1 = G, 2 = S, 3 = D**.
-
----
-
-## 5. Integration pitfalls
-
-1. **`SK2301AAT` and `SK2302AAT` differ by one digit and by channel type**, share
-   a package and share a pinout. Both are on this board, on adjacent sheets. This
-   is the most likely rework error involving either part.
-2. **V<sub>GS</sub> = ±8 V** and `Q2`'s gate is on raw USB V<sub>BUS</sub>
-   (§3.3) — the tightest margin on the part.
-3. **`R50` is not optional** (§3.2). Removing it makes the buzzer sensitive to
-   the GPIO's reset state.
-4. **`D3` is not optional either.** A magnetic buzzer is inductive; without the
-   flyback diode the drain sees a spike well beyond 20 V at turn-off.
-5. **The buzzer sits on `3V3_L1`**, a different domain from the system rail
-   (§3.2).
-6. **The body diode conducts when off.** `Q3`'s drain cannot be pulled below
-   about −0.7 V without conducting into ground.
-
----
-
-## 6. Open questions
-
-- **What consumes `VBAT_DET`** — see the
-  [SK2301AAT record §4](../sk2301aat/README.md#4-where-vbat_det-goes--not-established).
-- The buzzer's own part (`ER103`) is **unidentified**, so its inductance,
-  resonant frequency and current draw are unknown, and with them the actual
-  switching stress on `Q3`.
-- Whether M5Stack's firmware drives GPIO42 as a square wave or with a PWM duty —
-  the net is named `G42_BB_PWM`, implying PWM, but this was not read from source.
-- No measurement of anything.
-
----
-
-## Manufacturer
-
-**Shikues.** No vendor sourcing guide exists in this repository yet.
-
-**⚠ Retrieval finding — this part is the clean demonstration of the LCSC trap.**
-LCSC's own catalogue gave the datasheet URL as
-`https://www.lcsc.com/datasheet/lcsc_datasheet_2003311817_Shikues-SK2302AAT_C475757.pdf`.
-That URL returned **HTTP 200** and **47 038 bytes beginning `<!doc`** — an HTML
-page under a `.pdf` name. Five different user-agents (Chrome 131, ClaudeBot,
-WhatsApp, ChatGPT-User, plain `curl`) all got the same HTML. **No user-agent
-rotation helps, because it is not bot-blocking — it is the wrong host.**
-
-Rewriting to the CDN worked first try:
-
-```
-https://www.lcsc.com/datasheet/lcsc_datasheet_2003311817_Shikues-SK2302AAT_C475757.pdf   -> HTML
-https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2003311817_Shikues-SK2302AAT_C475757.pdf  -> %PDF ✓
-```
-
-**Check the `%PDF` magic bytes; the status code and the file extension both lie.**
-`executed-success`, 2026-09-01, reproduced on five parts from this board. This
-belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md) and
-confirms the finding first recorded in the
-[IP2315 record](../../injoinic/ip2315/README.md#manufacturer).
-
-## Related pages
-
-- [Shikues SK2301AAT](../sk2301aat/README.md) — **`Q5`, the P-channel half of the `Q2` switch**
-- [1N4148WS](../1n4148ws/README.md) — **`D3`, the buzzer flyback diode**
-- [AOS AO3400A](../../alpha-and-omega-semiconductor/ao3400a/README.md) — comparable N-channel documented here
-- [Changjing CJ2310](../../changjing/cj2310/README.md) — the board's other N-channel, in the e-paper bias converter
-- [PaperMono power architecture](../../../devices/m5stack/papermono/power-architecture.md) · [bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `SK2302AAT` SOT-523 Plastic-Encapsulate MOSFET | Shikues (via LCSC CDN) | primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2003311817_Shikues-SK2302AAT_C475757.pdf> | 2026-09-01 | **REV.08**, 4 pp | channel type, SOT-523, marking `A2S`, **pin 1 = G / 2 = S / 3 = D**, all §1 maxima | `artifacts/sk2302aat-shikues-lcsc-mirror.pdf` |
-| C1 | LCSC entry `C475757` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `SK2302AAT` | 2026-09-01 | — | manufacturer; 70 mΩ @ 2.5 V; V<sub>GS(th)</sub> 650 mV; the (broken) `www.lcsc.com` datasheet URL of the Manufacturer note | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | both instances; §3.1 and §3.2 topologies; `R9`, `R45`, `R50` values; `D3` orientation; the buzzer's no-connect marker | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/sk2302aat-shikues-lcsc-mirror.pdf` | 499 935 | `88f31ab70e4f6630b1d15e5a6f9a5f1e6ae713b40b503a4fa389a91fffed69aa` | 4 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) with an intact text
-layer. Both circuits in §3 were read from 200 dpi renders rather than from the
-text layer, which in both regions attaches labels to neighbouring designators; the
-`D3` orientation in particular is only legible from the image.
diff --git a/components/generic/sk2302aat/artifacts/sk2302aat-shikues-lcsc-mirror.pdf b/components/generic/sk2302aat/artifacts/sk2302aat-shikues-lcsc-mirror.pdf
deleted file mode 100644
index d7ecdb6..0000000
Binary files a/components/generic/sk2302aat/artifacts/sk2302aat-shikues-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/generic/ssp7615-33dfr/README.md b/components/generic/ssp7615-33dfr/README.md
deleted file mode 100644
index f295b71..0000000
--- a/components/generic/ssp7615-33dfr/README.md
+++ /dev/null
@@ -1,216 +0,0 @@
-# SSP7615-33DFR — 3.3 V / 400 mA CMOS LDO
-
-> High-accuracy, low-noise, low-dropout CMOS linear regulator: **1.5–8 V in, 400 mA at 3.3 V out, 200 mV dropout at 100 mA, 0.5 µA quiescent current**, with an active-high enable and built-in fold-back short-circuit protection, in a DFN 1 × 1 mm four-pad package.
-> Research snapshot **2026-09-01**. Fitted **four times** on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — it produces `3V3_L0`, `3V3_L1`, `3V3_L2_LoRa` and `EPD_3V3_L3B`, i.e. four of the board's five 3.3 V-class rails. **No hardware was available.**
-
-> **Filing note.** This record lives under `components/generic/` as the tree was laid out, but the part is **not** generic: a datasheet was obtained and the manufacturer is **Shanghai Siproin Microelectronics Co., Ltd.** (上海矽普微电子). A future reorganisation should move it to `components/siproin/ssp7615-33dfr/`; it is left here so that existing links keep working. The manufacturer identification is a finding of this pass, not an assumption.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Siproin `SSP7615` datasheet **V1.3 (English)** — local copy `artifacts/ssp7615-datasheet-v1.3-en.pdf` | `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and part numbering
-
-| Property | Value | Evidence |
-|---|---|---|
-| Base part | **`SSP7615`** | **[DS]** cover |
-| Ordering part as fitted | **`SSP7615-33DFR`** | **[SCH]** sheet 2 |
-| Manufacturer | **Shanghai Siproin Microelectronics Co., Ltd.** | **[DS]** footer, every page |
-| Function | High-accuracy, low-noise, high-speed CMOS linear voltage regulator | **[DS]** |
-| Datasheet | **V1.3**, English, 13 pp | **[DS]** footer |
-
-### 1.1 Decoding the suffix **[DS Ordering Information]**
-
-```
-SSP7615 - 33 DF R [G]
-          │   │  │  └── Halogen free
-          │   │  └───── RoHS / Pb free
-          │   └──────── Package:  M = SOT23-3
-          │                       M5 = SOT23-5
-          │                       DF = DFN 1 × 1 - 4
-          └──────────── Output voltage, integer form (1.2 – 5.0 V)
-```
-
-So **`SSP7615-33DFR`** = **3.3 V output, DFN 1 × 1-4 package, RoHS/Pb-free**. The output voltage is fixed at manufacture; there is no adjust pin and no divider.
-
-> ⚠ **Only the SOT23-5 and DFN packages have an enable pin.** The SOT23-3 variant is `GND` / `VOUT` / `VIN` only. A footprint change between package options is therefore also a *functional* change — this board depends on `EN` on three of its four instances.
-
----
-
-## 2. Key limits **[DS Features, Absolute Maximum Ratings]**
-
-| Parameter | Value |
-|---|---|
-| Input voltage | **1.5 V – 8 V** |
-| Output voltage options | 1.2 V – 5.0 V (fixed per ordering code) |
-| **Maximum output current** | **400 mA @ V<sub>OUT</sub> = 3.3 V** |
-| **Dropout voltage** | **200 mV @ I<sub>OUT</sub> = 100 mA** |
-| Quiescent current | **0.5 µA typical** |
-| Shutdown current | **< 1 µA** |
-| PSRR | 60 dB @ 1 kHz |
-| Recommended output capacitor | **1 µF** |
-| Protection | Built-in short-circuit protection and **fold-back** output current limiter |
-| Enable | **Active high, must not float** |
-| Vendor-named applications | radio control, cellphones/radiophones/digital cameras, Bluetooth and wireless handsets, portable consumer equipment |
-
----
-
-## 3. Pinout — DFN 1 × 1-4 **[DS Table 3]**
-
-| Pin | Name | Function |
-|---:|---|---|
-| **1** | `VOUT` | Output |
-| **2** | `GND` | Ground |
-| **3** | `EN` | **Enable — active high, "not floating"** |
-| **4** | `VIN` | Input |
-
-For reference, the other packages **[DS Tables 1–2]**:
-
-| SOT23-3 | | SOT23-5 | |
-|---:|---|---:|---|
-| 1 | `GND` | 1 | `VIN` |
-| 2 | `VOUT` | 2 | `GND` |
-| 3 | `VIN` | 3 | `EN` |
-| | | 4 | `NC` |
-| | | 5 | `VOUT` |
-
-The PaperMono's schematic symbol shows five markers — pins 1–4 plus a `GND_EP` exposed pad — matching the DFN package. **[SCH]**
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md). **Four instances, all on schematic sheet 2, all taking `VBUS_L0` as input.**
-
-Sheet 1's power architecture is explicit that this is a **parallel**, not cascaded, structure. M5Stack's own words: *"The PaperMono multi-level power switching design is **not a series structure**. The power inputs for the L1 ~ L3B switches all originate from the L0 (SYS_VBUS) source rather than from the preceding power level, allowing each level to be controlled independently."* **[DOC]** These four LDOs are the mechanism.
-
-#### 4.1 Every instance
-
-| # | Ref | Block | Input | **Output rail** | **Enable net** | Enable source | EN pull-down | Caps |
-|---|---|---|---|---|---|---|---|---|
-| 1 | **`U4`** | `L0_SW` | `VBUS_L0` | **`3V3_L0`** — always-on: M5PM1 `VCC`, RX8130CE RTC `VIO`, power-button pull-up (`R1`, 10 kΩ, sheet 5), debug test points | *not resolved* — see §4.2 | — | — | `C14`, `C15` = 10 µF/10 V |
-| 2 | **`U6`** | `L1_SW` | `VBUS_L0` | **`3V3_L1`** — the BMI270 IMU (`U15`, sheet 4) | **`3V3_L1_EN`** | [M5PM1](../../m5stack/m5pm1/README.md) `U7` pin 18, `LDO3V3_EN_PP` → `pm1.setLdoEnable(bool)` | `R24` = 1 MΩ/1 % | `C18`, `C19` = 10 µF/10 V |
-| 3 | **`U5`** | `L3_SW` | `VBUS_L0` | **`EPD_3V3_L3B`** — the e-paper panel's logic rail (FPC `J5`) | **`PYB_EPD_EN`** | [M5IOE1](../../m5stack/m5ioe1/README.md) **`PYG3`** = `M5IOE1_PIN_3`, enum value **2** | `R23` = 1 MΩ/1 % | `C16`, `C17`, `C20` = 10 µF/10 V |
-| 4 | **`U9`** | — | `VBUS_L0` | **`3V3_L2_LoRa`** — the Stamp LoRa-1262 module (`U14`, sheet 4) | **`PYG2_LoRa_EN`** | ⚠ **M5PM1 `U7` pin 20**, `G2_WAKEin(INT0/2)_IRQout_ADC` — *not* the M5IOE1, despite the `PYG` prefix | `R26` = 1 MΩ/1 % | `C22`, `C23` = 10 µF/10 V |
-
-All three switched instances use an identical **1 MΩ enable pull-down**, so an undriven or high-Z enable leaves the rail off — the safe default, and consistent across the design. **[SCH]**
-
-> ⚠ **Instance 4's net name is misleading, and this is a systematic problem on this board.** `PYG2_LoRa_EN` uses the `PYG` prefix that M5Stack's documentation otherwise reserves for M5IOE1 pins, but the schematic wires it to the **M5PM1**. The firmware agrees with the schematic, not the prefix: `LORA_EN_PM1_PIN = M5PM1_GPIO_NUM_2` (`hal_lora.cpp:29`). **[SRC]** M5IOE1 `PYG2` is a *different* pin — the LoRa **antenna switch** (`hal_lora.cpp:31`). Two different chips, two different pins, one prefix.
-
-#### 4.2 `3V3_L0`'s enable was not resolved
-
-`U4`'s `EN` net did not come out of the PDF text layer. Sheet 1 lists `3V3_L0` under the **L0 Shipping** column, i.e. it is the rail that exists whenever the battery does — which implies `EN` is tied to `VIN` or to a permanently-asserted node rather than driven. That is consistent, but it is an inference from the power-state table, not a read of the net. **[INF]** Read it off the rendered sheet before relying on it.
-
-This matters because `3V3_L0` powers the M5PM1 itself. If it were switchable, the thing that switches it would have to be the M5PM1, which cannot switch off its own supply.
-
-#### 4.3 ⚠ Near end of discharge these are not 3.3 V rails
-
-`VBUS_L0` is tied to `VBAT_L0` through a 0 Ω link (`R20`) **[SCH]**, so all four LDOs run **directly off the cell**. A single Li-ion cell spends the last part of its discharge between 3.0 V and 3.5 V, and the dropout spec is 200 mV at 100 mA (§2).
-
-**Consequence:** below roughly **3.5 V pack voltage the four rails leave regulation and follow the battery down.** They do not fail — an LDO in dropout is a resistor — but they are no longer 3.3 V, and the margin shrinks continuously as the pack empties. **[INF]**, arithmetic from two `executed-success` reads; not measured.
-
-The same effect applies to the [JW5712](../../joulwatt/jw5712/README.md) buck producing `3V3_L2`, which enters 100 % duty-cycle mode for the same reason. So **every 3.3 V rail on this board becomes a battery-follower near end of charge**, which is a coherent architectural choice rather than an oversight — but it is worth knowing before trusting an ADC reference or a display bias at 15 % battery.
-
-#### 4.4 The output capacitors are 10× the datasheet's recommendation
-
-Every instance uses **10 µF/10 V** where the datasheet recommends **1 µF** (§2). For a CMOS LDO this is normally harmless-to-beneficial for transient response, but stability of a low-I<sub>Q</sub> CMOS regulator does depend on output-capacitor ESR and value, and the datasheet gives a recommendation rather than a range. Recorded as an observation, not a defect: it is a consistent, deliberate choice across four instances, and M5Stack presumably validated it. **[INF]**
-
----
-
-## 5. Drivers and libraries
-
-**Not applicable** — no bus interface. On the PaperMono:
-
-```cpp
-pm1.setLdoEnable(true);                    // 3V3_L1  -> U6  (IMU)
-pm1.gpioSetOutput(M5PM1_GPIO_NUM_2, true); // 3V3_L2_LoRa -> U9
-ioe1.digitalWrite(M5IOE1_PIN_3, HIGH);     // EPD_3V3_L3B -> U5
-// 3V3_L0 (U4) is not software-controllable
-```
-
-`pm1.ldoSetPowerHold(true)` retains `3V3_L1` across an M5PM1 shutdown — that is how the board keeps the BMI270 alive as a wake source while everything else is off. **[DOC]**
-
----
-
-## 6. Integration pitfalls
-
-1. **`EN` must not float** (§2, §3). Every switched instance here fits a 1 MΩ pull-down; copy that.
-2. **The output voltage is in the part number** (§1.1). `SSP7615-33DFR` and `SSP7615-30DFR` share a footprint and differ by 300 mV — a silent substitution.
-3. **SOT23-3 has no `EN`** (§1.1). Package and function are coupled.
-4. **400 mA is at 3.3 V out**; the current capability is not constant across the output-voltage options.
-5. **Dropout plus a Li-ion input equals an unregulated rail at low state of charge** (§4.3).
-6. **Fold-back current limiting**, not constant-current limiting: under a hard short the LDO reduces current as the output collapses. Good for safety, but it means a heavily capacitive load can prevent start-up ("start-up into a short" behaviour). **[INF]**
-
----
-
-## 7. Alternatives
-
-| Part | vs. SSP7615-33DFR | When |
-|---|---|---|
-| **[SGMicro SGM2036-3.3](../../sgmicro/sgm2036-3.3/README.md)** | Low-noise 3.3 V LDO, documented in this repository | Direct substitute class |
-| TI **TLV757P** / **TPS7A02** | 300 mA / 200 mA, **25 nA** I<sub>Q</sub> on the TPS7A02, excellent documentation | When quiescent current dominates and the vendor's documentation quality matters |
-| **[Joulwatt JW5712](../../joulwatt/jw5712/README.md)** buck | 600 mA switching, 360 nA I<sub>Q</sub>, needs an inductor | Higher current, where the LDO's dropout loss would be significant |
-| **[AW35122](../../awinic/aw35122/README.md)** load switch | Switches without regulating | When the downstream rail does not need its own regulation |
-
-The PaperMono uses all three of those categories, and the split is instructive: **buck for the big load, LDOs for the quiet rails, load switches where the rail is just `3V3_L2` gated.** **[INF]**
-
----
-
-## 8. Open questions
-
-- `U4`'s enable net (§4.2).
-- Whether the 10 µF output capacitors are within the part's stable range (§4.4) — the datasheet gives a recommendation, not a range.
-- Whether a Chinese-language SSP7615 datasheet exists with more detail; only the English V1.3 was retrieved.
-- The LCSC part numbers found during the search (`C3011520`, `C3011522`, `C3011523`) correspond to other output-voltage options in the family; the specific code for the `-33DFR` variant was **not** confirmed.
-- No hardware measurement of dropout, load regulation or rail behaviour at low battery.
-
----
-
-## Manufacturer
-
-**Shanghai Siproin Microelectronics Co., Ltd.** (上海矽普微电子). No vendor sourcing guide exists in this repository yet.
-
-Sourcing notes from this session:
-
-- The datasheet is served **directly and without a session** from the vendor's own site: `https://www.siproin.com/uploads/Datasheets/Pow_driver/LDO/SSP7615_DATASHEET_V1.3_E.pdf`. A mirror of the same document exists at `https://www.siproin-ic.com/wp-content/uploads/2024/07/SSP7615_DATASHEET_V1.3_E.pdf` — two independent hosts for the same file, which is worth recording because it means this artifact is unusually well-preserved for a small Chinese vendor.
-- Plain `curl` with a Chrome 131 User-Agent; no fallback needed.
-- LCSC hosts copies under `https://www.lcsc.com/datasheet/lcsc_datasheet_<date>_Shanghai-Siproin-Microelectronics-SSP7615-30DFR_C3011522.pdf` — **note that is the `-30` variant**, and LCSC's PDF URLs return HTML to automated clients regardless. Prefer the vendor.
-
-## Related pages
-
-- [Joulwatt JW5712](../../joulwatt/jw5712/README.md) — the buck producing the fifth 3.3 V-class rail
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — owns `3V3_L1_EN` and `PYG2_LoRa_EN`
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — owns `PYB_EPD_EN`
-- [Awinic AW35122](../../awinic/aw35122/README.md) — the load switches used where regulation is not needed
-- [Bosch Sensortec BMI270](../../bosch-sensortec/bmi270/README.md) — the sole load on `3V3_L1`
-- [SGMicro SGM2036-3.3](../../sgmicro/sgm2036-3.3/README.md) — comparable LDO documented in this repository
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | SSP7615 datasheet | Shanghai Siproin Microelectronics | primary | datasheet | <https://www.siproin.com/uploads/Datasheets/Pow_driver/LDO/SSP7615_DATASHEET_V1.3_E.pdf> | 2026-09-01 | **V1.3**, English, 13 pp, 1 064 586 B | Manufacturer identity, ordering-code decode, all electrical limits in §2, all three package pinouts in §3 | `artifacts/ssp7615-datasheet-v1.3-en.pdf` |
-| D2 | SSP7615 datasheet (second host, same document) | Siproin | authorized mirror | datasheet | <https://www.siproin-ic.com/wp-content/uploads/2024/07/SSP7615_DATASHEET_V1.3_E.pdf> | 2026-09-01 | V1.3 | Redundant recovery URL | not stored twice |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | All four instances, rails, enable nets and passive values in §4 | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | PaperMono M5PM1/M5IOE1 power-management page | M5Stack | primary | official page | <https://docs.m5stack.com/en/arduino/papermono/m5pm1_m5ioe1> | 2026-09-01 | — | The "not a series structure" architecture statement; `setLdoEnable` / `ldoSetPowerHold` | `scratch/m5stack-papermono/docs/pages/en-arduino-papermono-m5pm1_m5ioe1.html` |
-| S3 | `M5PaperMono-UserDemo/main/hal/hal_lora.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | `main` @ `c1099107271d31a0678d661a896e2b04dbb331ea`, MIT | `LORA_EN_PM1_PIN = M5PM1_GPIO_NUM_2`, resolving the `PYG2` prefix conflict in §4.1 | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/ssp7615-datasheet-v1.3-en.pdf` | 1 064 586 | `5ca4f994acdfaaba7532d3fdd656ffe3d040272148006a63340c5eb4e0d79830` | 13 |
-
-**Method note.** D1 validated as `%PDF`, 13 pages, text layer intact. LCSC was tried first and rejected: `datasheet.lcsc.com` / `www.lcsc.com/datasheet/...` return **HTTP 200 with `text/html`** for `.pdf` URLs. **Check the `%PDF` magic bytes, never the status code.**
diff --git a/components/generic/ssp7615-33dfr/artifacts/ssp7615-datasheet-v1.3-en.pdf b/components/generic/ssp7615-33dfr/artifacts/ssp7615-datasheet-v1.3-en.pdf
deleted file mode 100644
index 5828404..0000000
Binary files a/components/generic/ssp7615-33dfr/artifacts/ssp7615-datasheet-v1.3-en.pdf and /dev/null differ
diff --git a/components/generic/tp4057/README.md b/components/generic/tp4057/README.md
deleted file mode 100644
index 5665b68..0000000
--- a/components/generic/tp4057/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# TP4057 — 500 mA linear Li-ion battery charger
-
-- **Category:** single-cell Li-ion constant-current / constant-voltage linear charger, SOT23-6.
-- **Manufacturer:** **unresolved from the mirrored datasheet.** The document M5Stack serves has
-  no vendor name or logo on page 1. TP4057 is a widely second-sourced Chinese part; filed under
-  `generic/` rather than asserting a maker.
-- **Retrieved:** 2026-09-04
-
-The battery charger of the M5Stack DinMeter (`U2`), and of many M5Stack products.
-
----
-
-## 1. Identity and headline specification
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **TP4057** | datasheet cover; DinMeter schematic `U2` value text |
-| Package | **SOT23-6** | datasheet |
-| Function | complete linear Li-ion charger, **no external MOSFET, sense resistor or blocking diode** | datasheet |
-| Max programmable charge current | **500 mA** | datasheet |
-| **Float voltage** | **4.24 V ±1 %** | datasheet — **note: 4.24 V, not the usual 4.2 V** |
-| Charge current | set by an external resistor on `PROG` | datasheet |
-| Termination | when current falls to 1/10 of the programmed value | datasheet |
-| Sleep current (input removed) | battery drain **< 1 µA** | datasheet |
-| Shutdown quiescent | 25 µA | datasheet |
-| Other features | thermal regulation (folds back current when hot), battery-temperature monitoring, UVLO, auto-recharge, **two status pins** (`CHRG`, `STDBY`) | datasheet |
-| Pins | `VCC`, `BAT`, `CHRG`, `STDBY`, `PROG`, `GND` | datasheet; DinMeter schematic `U2` |
-
-**Language.** The mirrored datasheet is **Chinese only**; no English version was located. It is
-therefore the primary source and is retained in the repository.
-
-The **4.24 V** float is worth flagging: it is above the 4.20 V nominal many cells specify. It is
-the part's documented behaviour, not a board choice.
-
-## 2. Artifacts
-
-| File | Size | SHA-256 | Language | Licence | Redistribution | Disposition |
-|---|---:|---|---|---|---|---|
-| [`artifacts/tp4057-datasheet-cn-m5stack-mirror.pdf`](artifacts/tp4057-datasheet-cn-m5stack-mirror.pdf) | 628 588 | `c949a7c3ef589ca575b2eaecd454f901e81f6b0896e6a706fa8cb4157aa0377b` | zh-CN | unknown | `unknown` | `repository` |
-
-Retrieved 2026-09-04 from
-`https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/M5DinMeter/tp4057.pdf`
-(HTTP 200, `%PDF` validated). Renamed from upstream `tp4057.pdf` to record that it is an
-M5Stack mirror rather than a vendor-hosted copy — no vendor host was located. Linked from **both**
-DinMeter documentation pages. Note the URL path is under `products/core/M5DinMeter/`: M5Stack
-files this chip datasheet under the *board*, which is exactly the filing error this repository's
-convention avoids — it lives here, under the component.
-
----
-
-## Used By
-
-### M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-Fitted as **`U2`**. Input from `+5VIN` (the [ME3116AM6G](../../microne/me3116am6g/README.md)
-buck output or USB), output to `VBAT_IN` on the 1.25 mm 2-pin battery connector `J2`. Programme
-resistor `R13` = **3.3 kΩ**; M5Stack specifies the resulting charge current as **100 mA**
-(charging a 250 mA·h bundled cell at ~0.4 C). Status pins drive indicator LEDs
-`D1`/`D2`/`D3` through `R17`/`R19` (10 kΩ / 100 kΩ). Decoupling `C15` 10 µF, `C21` 10 µF.
-
-The charger sits *upstream* of the battery power path (`Q3`/`Q6` AP40P05 P-FETs) and the boost
-converter, so charging and running are independent.
-
-→ [`devices/m5stack/dinmeter/features/power-and-battery.md`](../../../devices/m5stack/dinmeter/features/power-and-battery.md)
-→ [`devices/m5stack/dinmeter/pinouts-and-buses.md` §4](../../../devices/m5stack/dinmeter/pinouts-and-buses.md#4-power-tree-and-the-latch)
-
-### M5Stack Cardputer v1.0, v1.1 and ADV
-
-Designator **U1** on all three (the v1.0/v1.1 share one published schematic file, SHA-256
-`6016c1fe…`). `+5VIN` → R1 **0.8 Ω** → `VCC`; `BAT` → `VBAT_IN`; `PROG` → **R5 3.3 kΩ**;
-`CHRG` and `STDBY` status outputs; C6 10 µF on `BAT`.
-
-Charge current **inferred** at roughly **300 mA** from `R_PROG = 3.3 kΩ` and the family's usual
-`I = 1000 × V_PROG / R_PROG` relation. **Not measured, and no datasheet was consulted for this
-board** — treat as an order-of-magnitude figure.
-
-⚠ **R3 (1 kΩ) and D3 (an LED) beside the charger are drawn greyed out — depopulated.** A charge
-indicator the production board does not fit. That is a positive DNP marking, not an omission.
-
-⚠ M5Stack states on **all three** product pages that **the side power switch must be ON to
-charge**. This is the most repeated warning in the family's documentation and the most likely
-cause of a "my Cardputer won't charge" report.
-
-Records: [v1.0](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[v1.1](../../../devices/m5stack/cardputer-v1.1/README.md) ·
-[ADV](../../../devices/m5stack/cardputer-adv/README.md)
-
-⚠ **Note the disagreement with the DinMeter entry above**, which cites the same part with
-`R_PROG = 3.3 kΩ` and a vendor-stated **100 mA**. Both figures are recorded as their sources
-give them; they are not reconciled here. Logged in
-[`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.7.*
diff --git a/components/generic/tp4057/artifacts/tp4057-datasheet-cn-m5stack-mirror.pdf b/components/generic/tp4057/artifacts/tp4057-datasheet-cn-m5stack-mirror.pdf
deleted file mode 100644
index 2da7af0..0000000
Binary files a/components/generic/tp4057/artifacts/tp4057-datasheet-cn-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/generic/typec-302-brp16sc08/README.md b/components/generic/typec-302-brp16sc08/README.md
deleted file mode 100644
index b74bd6d..0000000
--- a/components/generic/typec-302-brp16sc08/README.md
+++ /dev/null
@@ -1,292 +0,0 @@
-# XUNPU TYPEC-302-BRP16SC08
-
-> **USB Type-C 3.1 receptacle**, 16 contacts, female, surface-mount, rated **5 A / 5 V**, 10 000 mating cycles.
-> Research snapshot **2026-09-01**. Fitted with the reference designator **`USB`, on sheet 2** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — the board's only external electrical interface besides the battery.
-> **No hardware was available.** Every claim traces to the schematic PDF, the LCSC catalogue entry or the vendor drawing held in `artifacts/`.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DWG]** | XUNPU drawing for `TYPEC-302-BRP16SC08`, local copy `artifacts/typec-302-brp16sc08-xunpu-lcsc-mirror.pdf` | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entry `C2835312`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 2 of `PaperMono_SCH_V0.6.2_20260522.pdf` rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`TYPEC-302-BRP16SC08`** | **[SCH-V]**, **[CAT]** |
-| Manufacturer | **XUNPU** (深圳市讯普电子有限公司) | **[CAT]** |
-| LCSC part | **`C2835312`** | **[CAT]** |
-| Function | USB Type-C **receptacle** (female), USB 3.1 body, 16 contacts | **[CAT]** |
-| Mounting | **SMD**, "laminated board" (板上贴片) style | **[CAT]** |
-| Contacts | **16** — 12 signal + **4 shell/shield legs** | **[SCH-V]** |
-| Current rating | **5 A** | **[CAT]** |
-| Voltage rating | **5 V** | **[CAT]** |
-| Durability | **10 000 insertion cycles** | **[CAT]** |
-| Operating temperature | **−45 °C to +85 °C** | **[CAT]** |
-| Body length | 6.5 mm | **[CAT]** |
-| Colour | black insulator | **[CAT]** |
-| RoHS | yes | **[CAT]** |
-
-> ⚠ **The `5 V` voltage rating is the connector's own specification**, and it is
-> the number a designer should notice: this is a receptacle sold for 5 V
-> applications, not one qualified for the 20 V a full USB-PD contract can carry.
-> On this board that is consistent — there is no PD (§3) — but it is a hard
-> constraint on anyone thinking of retrofitting one. **[CAT]** + **[INF]**
-
----
-
-## 2. ⚠ The datasheet is a single-page mechanical drawing with **no text layer**
-
-`artifacts/typec-302-brp16sc08-xunpu-lcsc-mirror.pdf` is **1 page, 115 078 bytes**,
-and `pdftotext` extracts **one byte** from it. Every glyph is a vector outline or
-a raster.
-
-Consequences, stated plainly:
-
-- **There is no electrical specification in the document.** The ratings in §1
-  come from LCSC's parametric fields, **not** from the manufacturer's own text.
-  They should be treated as a distributor's transcription.
-- No contact-resistance, insulation-resistance, dielectric-withstand or
-  solder-profile figures were obtained for this part from any source.
-- The drawing does carry the footprint and outline dimensions, but they must be
-  read as an image. That was **not** done here — the PaperMono's PCB layout is
-  not published, so the footprint could not be cross-checked against anything.
-
-This is a normal state of affairs for Chinese connector vendors and is not a
-defect in the acquisition; it is a limit on what can be asserted.
-
----
-
-## 3. Used By
-
-### `devices/m5stack/papermono` — **`USB`**, sheet 2
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-**The [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) uses
-the same connector**: the Lite differs only in dropping NFC and LoRa, and its USB
-path is unchanged. Its schematic is published as a 4-sheet `PRJ` PDF rather than
-a 6-sheet `SCH`, so this is `inferred` from the product pages rather than read
-from the Lite's own drawing.
-
-> ⚠ **This connector's reference designator is the bare string `USB`** — letters
-> only, no number. Its symbol carries `TYPEC-302-BRP16SC08` above and `USB`
-> below; the [IP2315 charger](../../injoinic/ip2315/README.md) on the same sheet
-> is `U1`. **[SCH-V]**
->
-> **An earlier reading of the PaperMono census recorded this part as a second
-> `U1` on sheet 2. That was wrong and is refuted here:** the Altium marker layer
-> contains one `CO` marker with body `U1` and one with body `USB`, and the latter
-> is accompanied by **16 `PIUSB01`…`PIUSB016` pin markers** — exactly a 16-contact
-> receptacle. Sheet 2 has one `U1`.
->
-> The digit-less designator has a practical consequence: **a census that filters
-> designators with a `[A-Z]+[0-9]+` pattern drops this component silently.** That
-> is how it went missing in the first place. See the
-> [BOM §2.1](../../../devices/m5stack/papermono/bill-of-materials.md#21--two-parser-artefacts-had-to-be-repaired--and-one-of-them-refutes-a-claim).
-> ⚠ [`pinouts-and-buses.md`](../../../devices/m5stack/papermono/pinouts-and-buses.md)
-> still lists it as "`U1` (sheet 2)". Not corrected there by this pass.
-
-### 3.1 Pinout as wired **[SCH-V]**
-
-Read from sheet 2 rendered at 200 dpi. Pin names are the connector symbol's own.
-
-| Pin | Name | Net on the PaperMono | Notes |
-|---:|---|---|---|
-| 1 | `GND` | `GND` | trace annotated **`20mil min`** |
-| 2 | `VBUS` | **`VUSB_IN`** | to the [AW32901FCR](../../awinic/aw32901/README.md) OVP switch |
-| 3 | `SBU2` | *(stub, unconnected)* | see §3.3 |
-| 4 | **`CC1`** | `CC1` → **`R4` = 5.1 kΩ** → `GND` | §3.2 |
-| 5 | `DN2` | `USB_N` | tied to pin 7 |
-| 6 | `DP1` | `USB_P` | tied to pin 8 |
-| 7 | `DN1` | `USB_N` | tied to pin 5 |
-| 8 | `DP2` | `USB_P` | tied to pin 6 |
-| 9 | `SBU1` | *(stub, unconnected)* | see §3.3 |
-| 10 | **`CC2`** | `CC2` → **`R14` = 5.1 kΩ** → `GND` | §3.2 |
-| 11 | `VBUS` | **`VUSB_IN`** | paralleled with pin 2 |
-| 12 | `GND` | `GND` | paralleled with pin 1 |
-| 13–16 | `SHELL` ×4 | shell / shield | |
-
-`USB_N` and `USB_P` continue to `TVS1` and `TVS2`
-([ESD5311](../../generic/esd5311/README.md)), then through the
-`ICMF062P900MFR` common-mode choke `FT1` and the 22 Ω series resistors `R40`/`R41`
-on sheet 3, to ESP32-S3 GPIO19/GPIO20.
-
-### 3.2 ⚠ The CC arrangement: a plain sink, and no USB-PD — twice over
-
-This is the single most important thing about how this connector is wired.
-
-**Both CC lines carry a 5.1 kΩ pulldown to ground:**
-
-| Resistor | On | Value | Function |
-|---|---|---|---|
-| **`R4`** | `CC1` (pin 4) | **5.1 kΩ ±1 %** | R<sub>d</sub> |
-| **`R14`** | `CC2` (pin 10) | **5.1 kΩ ±1 %** | R<sub>d</sub> |
-
-5.1 kΩ on both CC pins is the USB Type-C specification's **R<sub>d</sub>** — the
-advertisement *"I am a sink (UFP); give me default USB current"*. Putting it on
-both lines is what makes the cable orientation-independent: whichever CC the
-plug lands on, the source sees R<sub>d</sub> and applies V<sub>BUS</sub>.
-
-> The [device record's earlier note](../../../devices/m5stack/papermono/pinouts-and-buses.md)
-> mentions only one CC resistor. **There are two**, `R4` on `CC1` and `R14` on
-> `CC2`, both 5.1 kΩ/1 %. Confirmed by rendering the block at 200 dpi.
-> Date 2026-09-01. **[SCH-V]**
-
-**Meanwhile the charger's own CC pins are depopulated.** The
-[IP2315](../../injoinic/ip2315/README.md) can negotiate USB-PD, FCP, AFC and
-PE+ by itself, and its `CC1`/`CC2` (pins 2 and 3) reach the connector through
-`R1` and `R2` — both of which carry the value **`NC/1%`**, i.e. **not fitted**.
-
-So there are two independent reasons this is a 5 V-only port:
-
-1. **Passive R<sub>d</sub> only.** With plain 5.1 kΩ pulldowns and nothing driving
-   or listening on CC, the port cannot send or receive a PD message. A PD source
-   will see a legacy sink and hold V<sub>BUS</sub> at 5 V.
-2. **The one chip that could negotiate is disconnected from CC.** Even if a
-   controller wanted to talk, `R1`/`R2` are open.
-
-And a third, upstream: the [AW32901FCR](../../awinic/aw32901/README.md) OVP
-switch is configured with a **5.95 V** over-voltage threshold, so a higher
-negotiated voltage would be cut off rather than merely unused. **[SCH-V]**
-
-**Practical consequence.** Charge current is limited by what the IP2315 draws
-from a 5 V supply. Nothing a user plugs in — PD brick, PPS supply, laptop port —
-changes that. Anyone reading the IP2315 datasheet and expecting 9 V fast charge
-on a PaperMono will be disappointed, and the reason is here, not in the charger.
-
-### 3.3 `SBU1`/`SBU2` are unconnected — but that is an *omission*, not an assertion
-
-Pins 3 and 9 terminate in short stubs with nothing attached and **no drawn
-no-connect marker**. That distinction matters: elsewhere on this schematic the
-designer *does* place explicit red ✗ markers (on the buzzer symbol on sheet 4,
-on the `PYB_NFC_EN` stub at `J3`). Here they did not.
-
-So the correct reading is **"unknown/unused"**, not "the designer asserted these
-must not be connected". In practice SBU is used only for alternate modes
-(DisplayPort, debug accessory), none of which this board supports. **[INF]**
-
----
-
-## 4. Equivalents and substitution
-
-The pin *function* order of a USB-C receptacle is fixed by the USB Type-C
-specification, so any 16-pin mid-mount/SMT receptacle is functionally a
-candidate. What is **not** interchangeable is the mechanical part: shell height,
-leg pattern, board cut-out and retention geometry differ between vendors and
-between "laminated board"/sinking depths within one vendor.
-
-| Alternative | vs. this part | When |
-|---|---|---|
-| XUNPU `TYPEC-304-BCP16` and siblings | Same vendor, different mount style | Same ecosystem, different board thickness |
-| Korean Hroparts / Jing Extension 16-pin USB-C | Widely stocked at LCSC | Cost |
-| Amphenol, Molex, JAE 16-pin USB-C | Documented, qualified, far more expensive | When the 5 V rating or the 10 000-cycle figure is not enough |
-
-> **Do not substitute by pin count alone.** 16-pin USB-C receptacles exist in at
-> least four incompatible footprints. Without the PaperMono's PCB layout — which
-> M5Stack does not publish — the footprint cannot be matched from this record.
-
----
-
-## 5. Integration pitfalls
-
-1. **This is a 5 V-rated connector on a 5 V-only port.** Correct as built, but
-   it forecloses retrofitting PD without changing the connector *and* `R1`/`R2`
-   *and* the AW32901's OVP threshold (§3.2).
-2. **The datasheet has no electrical section** (§2). Do not quote a
-   contact-resistance or dielectric figure for this part; none was obtained.
-3. **Two `U1`s on sheet 2** (§3). A designator-based search will find the wrong
-   one half the time.
-4. **`SBU1`/`SBU2` are open with no ERC marker** (§3.3) — do not read that as a
-   designed no-connect.
-5. **The shell is four separate contacts (13–16)**, not one. Whether they are
-   commoned inside the connector is not shown by the drawing's text and was not
-   verified.
-
----
-
-## 6. Open questions
-
-- The drawing's mechanical dimensions and footprint (§2) — readable only as an
-  image, and with no published PCB layout to check them against.
-- Whether the four shell legs are internally commoned.
-- Contact resistance, insulation resistance and the reflow profile — absent from
-  every source found.
-- Whether the PaperMono-Lite fits the identical part number (`inferred`, §3).
-
----
-
-## Manufacturer
-
-**XUNPU** (深圳市讯普电子有限公司) is a Shenzhen connector maker whose catalogue
-is distributed almost entirely through LCSC. It has no vendor sourcing guide in
-this repository yet. The same vendor supplies this board's
-[`BTB0.408-10PLBDR-G41`](../../generic/btb0.408-10plbdr-g41/README.md)
-board-to-board connector, for which **no datasheet exists at all**.
-
-**⚠ Retrieval finding — the LCSC PDF host trap, confirmed again.** For this part
-the working URL is on **`wmsc.lcsc.com`**:
-
-| URL | Result |
-|---|---|
-| `https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2105281102_XUNPU-TYPEC-302-BRP16SC08_C2835312.pdf` | **200, `%PDF` ✓** |
-| `https://www.lcsc.com/datasheet/…` (the form LCSC's own product page links) | **HTTP 200 with `text/html`** — an interstitial page, not the document |
-
-`www.lcsc.com/datasheet/*.pdf` returns **HTTP 200 and a `.pdf` URL while serving
-HTML**. The status code is worthless; only the `%PDF` magic at byte 0 decides.
-The mechanical rewrite that works is
-`www.lcsc.com/datasheet/lcsc_datasheet_<stamp>_<name>_<code>.pdf` →
-`wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/<stamp>_<name>_<code>.pdf`.
-This matches the finding already recorded in the
-[IP2315 record](../../injoinic/ip2315/README.md#manufacturer) and belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-Part discovery itself was done through **JLCPCB's SMT parts API**, which answers
-with compact JSON including manufacturer, package and datasheet URL, and which —
-unlike DuckDuckGo-lite, Mojeek and searx.be, all of which blocked or captcha'd
-`curl` on 2026-09-01 — is not bot-filtered:
-
-```bash
-curl -s -X POST -H 'Content-Type: application/json' \
-  -d '{"keyword":"TYPEC-302-BRP16SC08","currentPage":1,"pageSize":3}' \
-  https://jlcpcb.com/api/overseas-pcb-order/v1/shoppingCart/smtGood/selectSmtComponentList
-```
-
-`executed-success`, 2026-09-01. Helper:
-[`scratch/m5stack-papermono/tools/lcsc_lookup.sh`](../../../scratch/m5stack-papermono/tools/lcsc_lookup.sh).
-
-## Related pages
-
-- [Awinic AW32901FCR](../../awinic/aw32901/README.md) — `U2`, the OVP switch `VUSB_IN` feeds
-- [Injoinic IP2315](../../injoinic/ip2315/README.md) — `U1` sheet 2, whose CC pins are depopulated
-- [ESD5311](../../generic/esd5311/README.md) — `TVS1`/`TVS2` on `USB_N`/`USB_P`
-- [USB-C target-selection interface](../usb-c-interface/README.md) — the generic interface record
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-- [PaperMono USB and serial feature guide](../../../devices/m5stack/papermono/features/usb-and-serial.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `TYPEC-302-BRP16SC08` drawing | XUNPU (via LCSC CDN) | primary, via distributor mirror | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2105281102_XUNPU-TYPEC-302-BRP16SC08_C2835312.pdf> | 2026-09-01 | undated, 1 p | mechanical outline only — **no text layer**, §2 | `artifacts/typec-302-brp16sc08-xunpu-lcsc-mirror.pdf` |
-| C1 | LCSC catalogue entry `C2835312` | LCSC / JLCPCB | distributor | <https://www.lcsc.com/product-detail/usb-connectors_xunpu-typec-302-brp16sc08_C2835312.html> | 2026-09-01 | — | manufacturer, 16P, 5 A, 5 V, 10 000 cycles, −45…+85 °C, 6.5 mm | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | the §3.1 pinout, `R4`/`R14` = 5.1 kΩ, `R1`/`R2` = `NC`, **the designator `USB` and its 16 pin markers** | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/typec-302-brp16sc08-xunpu-lcsc-mirror.pdf` | 115 078 | `99d0419afa7fb46d18ad9b441fef7c327482305ed9dd6a26013c40f4631df7ed` | 1 |
-
-**Method note.** D1 was fetched with `curl`, validated as `%PDF` (`executed-success`),
-and found to carry no text layer (`pdftotext` yields 1 byte). The pinout in §3.1
-was read from a 200 dpi PNG render of schematic sheet 2, not from the text layer —
-which for this block interleaves the connector's pin names with the neighbouring
-charger's and cannot be separated reliably.
diff --git a/components/generic/typec-302-brp16sc08/artifacts/typec-302-brp16sc08-xunpu-lcsc-mirror.pdf b/components/generic/typec-302-brp16sc08/artifacts/typec-302-brp16sc08-xunpu-lcsc-mirror.pdf
deleted file mode 100644
index 7285707..0000000
Binary files a/components/generic/typec-302-brp16sc08/artifacts/typec-302-brp16sc08-xunpu-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md b/components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md
deleted file mode 100644
index 669f6d6..0000000
--- a/components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md
+++ /dev/null
@@ -1,307 +0,0 @@
-# XL7EL89CMI-111YLC — 27.12 MHz crystal for the ST25R3916 NFC front end
-
-> **27.12 MHz quartz crystal**, YXC `XL7EL89CMI-111YLC` series, **SMD2016-4P** (2.0 × 1.6 mm, 4 pad), **10 pF load**, ±10/±20 ppm, −40 to +85 °C.
-> Research snapshot **2026-09-01**. Fitted as **`X1` on sheet 6** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — the reference for the [ST25R3916](../../stmicroelectronics/st25r3916/README.md) NFC reader on the NFC sub-board.
-> ⚠ **The 27.12 MHz variant is not in any catalogue reached; the datasheet held is for the same series at a different frequency.** See [§2](#2--what-was-and-was-not-obtained). **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | YXC `XL7EL89CMI-111YLC-24M` datasheet, local copy `artifacts/xl7el89cmi-111ylc-24m-yxc-lcsc-mirror.pdf` — ⚠ **24 MHz variant, image-only** | `not-tested` |
-| **[CAT]** | LCSC / JLCPCB catalogue entries `C2965581` (-24M), `C2965583` (-32M), retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 6 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[SCH-T]** | Read from the schematic text layer | `executed-success` for the extraction |
-| **[ST]** | ST **DS12484** ST25R3916 datasheet, held under the [ST25R3916 record](../../stmicroelectronics/st25r3916/README.md) | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Value string on the schematic | **`27.12MHZ(XL7EL89CMI-111YLC)`** | **[SCH-T]**, **[SCH-V]** |
-| **Frequency** | **27.12 MHz** | **[SCH-V]** |
-| Manufacturer | **YXC Crystal Oscillators** (扬兴科技, Yangxing) | **[CAT]** |
-| Series | `XL7EL89CMI-111YLC` | **[CAT]** |
-| Package | **SMD2016-4P** — 2.0 × 1.6 mm, 4 pads | **[CAT]** |
-| **Load capacitance C<sub>L</sub>** | **10 pF** | **[CAT]** |
-| Frequency tolerance | **±10 ppm** | **[CAT]** |
-| Frequency stability | **±20 ppm** over temperature | **[CAT]** |
-| ESR | 100 Ω (‑24M) / 80 Ω (‑32M) — **frequency-dependent, §2** | **[CAT]** |
-| Operating temperature | **−40 °C to +85 °C** | **[CAT]** |
-| Reference designator | **`X1`**, sheet 6 | **[SCH-V]** |
-
-### 1.1 The ordering code carries the frequency as a suffix
-
-LCSC lists `XL7EL89CMI-111YLC-**24M**` and `XL7EL89CMI-111YLC-**32M**`. The base
-code names the *package, load capacitance and grade*; the frequency is appended.
-So the part on this board is, by construction, **`XL7EL89CMI-111YLC-27.12M`**.
-
-That form is **not asserted as a confirmed orderable part number** — it was not
-found in any catalogue (§2) — but the decomposition itself is established from
-two siblings that differ only in the suffix. **[INF]**
-
----
-
-## 2. ⚠ What was and was not obtained
-
-| | Status |
-|---|---|
-| **The 27.12 MHz variant's own datasheet** | **Not found.** No catalogue reached lists the part at this frequency |
-| The series datasheet, via the 24 MHz sibling | **Obtained** — `artifacts/xl7el89cmi-111ylc-24m-yxc-lcsc-mirror.pdf`, 535 394 B, 1 page |
-| That document's text layer | **⚠ None.** `pdftotext` extracts **0 bytes**; the page is a scan or vector outline |
-
-Consequently **every number in §1 comes from LCSC's parametric fields**, not from
-YXC's own text, and the retained PDF is useful only as a page image.
-
-**Two properties transfer across the series and two do not.**
-
-| Property | Transfers from the ‑24M document? | Why |
-|---|---|---|
-| Package, pad layout, dimensions | **Yes** — SMD2016-4P is the series' package | |
-| Load capacitance C<sub>L</sub> = 10 pF | **Yes** — the `YLC` field encodes it, and both siblings share it | |
-| **ESR** | **No** — 100 Ω at 24 MHz, 80 Ω at 32 MHz; **27.12 MHz is between them and its value is unknown** | ESR falls with frequency in a series like this |
-| **Drive level, C<sub>0</sub>, ageing** | **No** — unread; the document has no text layer | |
-
-**Search attempts, all 2026-09-01:**
-
-| Attempt | Result |
-|---|---|
-| JLCPCB SMT parts API, `XL7EL89CMI-111YLC` | 2 results: **‑24M** and **‑32M** only. No 27.12 MHz SKU |
-| Same API, the base code without suffix | same 2 results |
-| DuckDuckGo-lite, Mojeek, searx.be via `curl` | **all blocked or captcha'd**; no general web search succeeded |
-
-**What would resolve it:** YXC's own catalogue (`yxc-crystal.com`), a Chinese
-crystal distributor listing the 27.12 MHz SKU, or M5Stack's BOM.
-
----
-
-## 3. Why 27.12 MHz is load-bearing
-
-**NFC's carrier is 13.56 MHz**, defined by ISO/IEC 14443 and ISO/IEC 15693.
-**27.12 MHz is exactly 2 ×** that, and the ST25R3916 divides it down internally
-to synthesise the carrier and to clock its receiver.
-
-This is not a "system clock" that can be any convenient value. Consequences:
-
-1. **The frequency is fixed by the standard, not by the design.** 24 MHz or
-   26 MHz — both far commoner crystal values, and both stocked by the same
-   vendor — will not work. The ST25R3916 requires 27.12 MHz.
-2. **Carrier accuracy is inherited directly from the crystal.** ISO/IEC 14443
-   specifies the carrier as 13.56 MHz **± 7 kHz**, i.e. about **±516 ppm**. The
-   crystal's ±10 ppm initial tolerance and ±20 ppm temperature stability are
-   comfortably inside that, with roughly **17× margin** on the total ±30 ppm
-   worst case. **[INF]** — the ±7 kHz figure is the standard's, quoted from
-   general knowledge of ISO 14443 and **not** read from **[ST]** for this record.
-3. **Subcarrier timing depends on it too.** The 847.5 kHz load-modulation
-   subcarrier is f<sub>c</sub>/16, and bit timing is derived in carrier periods.
-   A crystal error scales all of it together, which is why the margin above is
-   generous — but it also means **a wrong crystal does not degrade gracefully;
-   it fails to communicate at all.**
-4. **A drop-in replacement must be 27.12 MHz.** This is the single most important
-   line in this record.
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono` — `X1`, sheet 6
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), on
-the **NFC sub-board** (`02 Paper Mono NFC.SchDoc`, `Paper Mono NFC`, `2/2`,
-`V0.2`, dated **2026-07-28**), which reaches the mainboard through the
-[`BTB0.408-10PLBDR-G41`](../btb0.408-10plbdr-g41/README.md) board-to-board pair.
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):
-NO.** The Lite drops NFC entirely — that and LoRa are the whole difference
-between the SKUs. There is no NFC sub-board, so no crystal.
-
-> ⚠ **Sheet 6 has its own `X1`**, unrelated to `X1` on sheet 3 (the
-> `CN4040M000157A530001` 40 MHz crystal for the ESP32-S3). The PDF concatenates
-> three separate Altium documents; see the
-> [BOM's designator-collision table](../../../devices/m5stack/papermono/bill-of-materials.md#3--designators-repeat-across-sheets--a-designator-alone-is-meaningless).
-
-### 4.1 Connections **[SCH-V]**
-
-| `X1` pin | Net | Notes |
-|---:|---|---|
-| **2** | **`XTO`** — ST25R3916 **pin 4** | with **`C14` = 10 pF** to GND |
-| **3** | **`XTI`** — ST25R3916 **pin 5** | with **`C15` = 10 pF** to GND |
-| 1, 4 | **GND** | the case/shield pads of the 4-pad package |
-
-Nothing else is in the loop: no series resistor, no external feedback network —
-the ST25R3916 contains its own oscillator amplifier.
-
-### 4.2 ⚠ The load capacitors and the specified C<sub>L</sub> do not obviously agree
-
-`C14` = `C15` = **10 pF**, and the crystal's specified **C<sub>L</sub> = 10 pF**.
-**[SCH-V]**, **[CAT]**
-
-For a parallel-resonant crystal the oscillator presents
-
-> C<sub>L</sub> ≈ (C1 × C2) / (C1 + C2) + C<sub>stray</sub>
-
-With C1 = C2 = 10 pF that is **5 pF + C<sub>stray</sub>**. Reaching 10 pF would
-need about **5 pF of stray**, which is high for a compact 0402-populated layout
-but not impossible once the IC's own pin capacitance and the PCB traces are
-counted — and the ST25R3916's `XTI`/`XTO` pins contribute several pF of their
-own.
-
-**Three readings, none adopted:**
-
-| Reading | Comment |
-|---|---|
-| The stray really is ~5 pF | Plausible on a small dense sub-board with an IC that has significant pin capacitance |
-| ST specifies the external capacitors directly, and 10 pF is ST's recommended value rather than a computed one | ST's application notes for the ST25R39xx family do give recommended values; **not checked against [ST] for this record** |
-| The crystal's true C<sub>L</sub> at 27.12 MHz differs from the 10 pF LCSC lists for the ‑24M/‑32M siblings | Possible, since §2 shows ESR does vary across the series |
-
-**Practical consequence if the first reading is wrong:** the oscillator would run
-**fast** — pulling a crystal with too little load capacitance raises its
-frequency. A few tens of ppm would still be inside the ±516 ppm the carrier
-tolerates (§3), so this would most likely be invisible rather than fatal.
-**[INF]** Recorded as an open question, not as a defect.
-
-### 4.3 Supporting evidence: the sheet's own annotations
-
-Sheet 6 is unusually forthcoming and worth quoting, because it settles several
-things about the NFC front end without needing measurement **[SCH-T]**:
-
-- *"Supply current in Power-down mode: I = 2.5 µA — When Operation control
-  register (en=0)"*
-- *"Communication mode: `I2C_EN`=VDD ⇒ I²C mode; `I2C_EN`=GND ⇒ SPI mode"* —
-  and `R4` = 0 Ω ties `I2C_EN` to `VCC_3V3`, **selecting I²C**
-- Antenna construction: *"Turns: 4 · Antenna Length: 25 mm · Antenna Width: 25 mm
-  · Line Width: 0.25 mm · Line Spacing: 0.3 mm · Thickness: 17 µm (0.5 oz)"*
-
----
-
-## 5. Substitution
-
-**Must be 27.12 MHz** (§3). Beyond that:
-
-| Property | Requirement |
-|---|---|
-| Frequency | **27.12 MHz — non-negotiable** |
-| C<sub>L</sub> | match whatever `C14`/`C15` were designed around (§4.2) — **changing C<sub>L</sub> without changing the capacitors pulls the frequency** |
-| Tolerance / stability | ±10 / ±20 ppm as fitted; ISO 14443 allows far more (§3), so this is not tight |
-| ESR | **unknown at 27.12 MHz** (§2) — a higher-ESR part risks unreliable start-up |
-| Package | SMD2016 (2.0 × 1.6 mm) 4-pad |
-
-27.12 MHz crystals in 2016 are a standard NFC-market item from Abracon (`ABM8`),
-NDK, Epson, TXC, Hosonic and others, and any ST25R39xx reference design names
-one. **Prefer a part whose datasheet you can actually read** — this one's cannot
-be (§2).
-
----
-
-## 6. Integration pitfalls
-
-1. **27.12 MHz, not 27 MHz and not 13.56 MHz** (§3). The single most common way
-   to get this wrong.
-2. **The exact SKU is not orderable from any catalogue reached** (§2).
-3. **The datasheet held is the wrong frequency and has no text layer** (§2). Do
-   not quote an ESR or drive level from it.
-4. **C<sub>L</sub> vs `C14`/`C15` is unresolved** (§4.2).
-5. **A dead crystal presents as "NFC not responding"**, indistinguishable in
-   firmware from a bus fault or an unpowered sub-board — and the sub-board's rail
-   is switched (see the
-   [BTB record §3.4](../btb0.408-10plbdr-g41/README.md#34-pyb_nfc_en--pyb_rfid_rst--a-power-cut-not-a-reset)),
-   so "no NFC" has at least three causes before the crystal is suspected.
-6. **Drive level is unspecified.** Over-driving a small 2016 crystal ages it and
-   can fracture it; the ST25R3916's oscillator drive was not checked. **[INF]**
-
----
-
-## 7. Open questions
-
-- The 27.12 MHz SKU's ordering code, ESR, drive level, C<sub>0</sub> and ageing
-  (§2).
-- Whether `C14`/`C15` = 10 pF is ST's recommended value or a computed one, and
-  therefore whether §4.2 is a non-issue (checkable against **[ST]** DS12484 and
-  ST's ST25R3916 application notes, both already held or reachable).
-- The actual C<sub>L</sub> of the fitted part.
-- No measurement of frequency, start-up time or drive level.
-
----
-
-## Manufacturer
-
-**YXC Crystal Oscillators** (扬兴科技). No vendor sourcing guide exists in this
-repository yet.
-
-**⚠ Retrieval findings, both worth carrying forward.**
-
-1. **LCSC's `wmsc.lcsc.com` CDN served the document; `www.lcsc.com/datasheet/`
-   does not.** The rewrite is mechanical and is documented in full in the
-   [SK2302AAT record](../sk2302aat/README.md#manufacturer). **Check the `%PDF`
-   magic bytes, never the status code.**
-2. **General web search was unavailable.** On 2026-09-01, `lite.duckduckgo.com`
-   returned a captcha challenge to `curl` ("Unfortunately, bots use DuckDuckGo
-   too… Select all squares containing a duck"), `www.mojeek.com/search` returned
-   no parseable results, and `searx.be` served a "Verifying your browser…"
-   interstitial. **The only search channel that worked for these Chinese-market
-   parts was JLCPCB's SMT parts API**, which answers with compact JSON and is not
-   bot-filtered:
-
-   ```bash
-   curl -s -X POST -H 'Content-Type: application/json' \
-     -d '{"keyword":"XL7EL89CMI-111YLC","currentPage":1,"pageSize":3}' \
-     https://jlcpcb.com/api/overseas-pcb-order/v1/shoppingCart/smtGood/selectSmtComponentList
-   ```
-
-   `executed-success`, 2026-09-01. Helper:
-   [`scratch/m5stack-papermono/tools/lcsc_lookup.sh`](../../../scratch/m5stack-papermono/tools/lcsc_lookup.sh).
-
-Both belong in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## 4.4 A second board uses 27.12 MHz for the same reason — part **not** identified · *added 2026-09-04*
-
-The [M5Stack Cap CC1101 & NFC (U219)](../../../devices/m5stack/cap-cc1101/README.md) fits an
-**ST25R3916 with a 27.12 MHz crystal** — designator `Y1`, load capacitors `C19`/`C20` = **6.0 pF**,
-on `XTI` (5) / `XTO` (4), read from the Cap CC1101 schematic V0.3 (2026-05-28).
-
-**This is *not* recorded as a Used By entry for this part**, because **no part number is
-printed on that schematic** — only the frequency and the package-adjacent values. The two
-crystals share a frequency and a job; nothing establishes that they are the same component.
-
-What it does confirm is §3's argument: **27.12 MHz appears wherever an ST25R3916 does**,
-because the 13.56 MHz NFC carrier is derived from it by division by two. Two independent
-M5Stack boards, two years apart, same frequency, same reason.
-
-If the Cap CC1101's crystal part number is ever read from a photograph or a BOM and turns
-out to be `XL7EL89CMI-111YLC`, this section should become a proper **Used By** entry with
-the pin table and load-capacitor analysis that §4.1–4.2 give for the PaperMono.
-
-## Related pages
-
-- [M5Stack Cap CC1101 & NFC](../../../devices/m5stack/cap-cc1101/features/nfc.md) — the second ST25R3916 board in this repository (**SPI**-strapped, unlike the PaperMono)
-- [STMicroelectronics ST25R3916](../../stmicroelectronics/st25r3916/README.md) — **the IC this crystal clocks**
-- [BTB0.408-10PLBDR-G41](../btb0.408-10plbdr-g41/README.md) — how the NFC sub-board attaches
-- [CN4040M000157A530001 40 MHz crystal](../cn4040m000157a530001-40mhz-crystal/README.md) — the board's *other* crystal, also `X1`, also with no datasheet
-- [PaperMono NFC feature guide](../../../devices/m5stack/papermono/features/nfc.md) · [bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `XL7EL89CMI-111YLC-24M` crystal datasheet | YXC (via LCSC CDN) | **series-representative**, wrong frequency (§2) | <https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2403291506_YXC-Crystal-Oscillators-XL7EL89CMI-111YLC-24M_C2965581.pdf> | 2026-09-01 | undated, 1 p, **no text layer** | the series' existence and package; **nothing numeric** — every figure in §1 is from **[CAT]** | `artifacts/xl7el89cmi-111ylc-24m-yxc-lcsc-mirror.pdf` |
-| C1 | LCSC entries `C2965581`, `C2965583` | LCSC / JLCPCB | distributor | JLCPCB SMT parts API, keyword `XL7EL89CMI-111YLC` | 2026-09-01 | — | manufacturer YXC; SMD2016-4P; **C<sub>L</sub> = 10 pF**; ±10/±20 ppm; −40…+85 °C; ESR 100 Ω @ 24 MHz and 80 Ω @ 32 MHz; **the absence of a 27.12 MHz SKU** | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `X1` = `27.12MHZ(XL7EL89CMI-111YLC)`; the §4.1 connections; `C14`/`C15` = 10 pF; the §4.3 sheet annotations | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/xl7el89cmi-111ylc-24m-yxc-lcsc-mirror.pdf` | 535 394 | `a04912f4671b1e22bbdc13488eb82e6321fd7a71ffdb3515c111cae3472f0a0c` | 1 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) and confirmed
-text-layer-free (`pdftotext` yields 0 bytes). It is retained despite being the
-wrong frequency because it is the only YXC artifact obtainable for this series and
-because its page can be rendered and read as an image by a future pass. **It is
-labelled series-representative rather than primary precisely so that no reader
-mistakes a 24 MHz figure for a 27.12 MHz one.**
diff --git a/components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/artifacts/xl7el89cmi-111ylc-24m-yxc-lcsc-mirror.pdf b/components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/artifacts/xl7el89cmi-111ylc-24m-yxc-lcsc-mirror.pdf
deleted file mode 100644
index fa45ae8..0000000
Binary files a/components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/artifacts/xl7el89cmi-111ylc-24m-yxc-lcsc-mirror.pdf and /dev/null differ
diff --git a/components/gigadevice/gd25q64e/README.md b/components/gigadevice/gd25q64e/README.md
index 18d04fc..278a017 100644
--- a/components/gigadevice/gd25q64e/README.md
+++ b/components/gigadevice/gd25q64e/README.md
@@ -77,7 +77,7 @@ The practical mitigations, in order of preference: read **SFDP** (JEDEC JESD216)
 Thirteen URLs were tried across three sessions; all failed. Full log in [`component-download-failures.txt`](../../../component-download-failures.txt). Two failures are worth repeating because they are traps rather than plain 404s:
 
 - **`gigadevice.com.cn` 404 pages are ~139 KB of HTML** (the `.com` ones are 86 bytes). A size-based sanity check would pass them.
-- The `wmsc.lcsc.com/.../v2/...` recipe that genuinely works for other parts returned, for a **guessed** GD25Q64E filename, **a valid 1,062,428-byte PDF that is an NPN bias-resistor transistor datasheet** (MMUN2211 series). Archived to `archive/.../WRONG-PART-mmun22xx-transistor-lcsc-C2919772.pdf`. **LCSC serves *something* for any plausible filename; the filename must be read off the real product page, and the extracted text must be grepped for the part number before the file is trusted.**
+- The `wmsc.lcsc.com/.../v2/...` recipe that genuinely works for other parts returned, for a **guessed** GD25Q64E filename, **a valid 1,062,428-byte PDF that is an NPN bias-resistor transistor datasheet** (MMUN2211 series). Archived to `../hardware-doc-archive/.../WRONG-PART-mmun22xx-transistor-lcsc-C2919772.pdf`. **LCSC serves *something* for any plausible filename; the filename must be read off the real product page, and the extracted text must be grepped for the part number before the file is trusted.**
 
 **Consequently unverified here:** the QE bit location and default, the exact JEDEC device/capacity bytes, erase and program timings, supply and current limits, endurance and retention, and the SFDP contents.
 
diff --git a/components/gigadevice/gd25q64e/artifacts b/components/gigadevice/gd25q64e/artifacts
deleted file mode 120000
index 328c581..0000000
--- a/components/gigadevice/gd25q64e/artifacts
+++ /dev/null
@@ -1 +0,0 @@
-../../../archive/components/gigadevice/gd25q64e/artifacts
\ No newline at end of file
diff --git a/components/goodix/gt911/README.md b/components/goodix/gt911/README.md
index df32400..def1151 100644
--- a/components/goodix/gt911/README.md
+++ b/components/goodix/gt911/README.md
@@ -101,54 +101,6 @@ simply chose not to route its interrupt. See the device's
 > Note the resolution differs between the two variants sharing this record. Use **720 × 720** on
 > the 4C; using the 3.4C's 800 × 800 yields mis-scaled coordinates.
 
-### [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md) — *added 2026-09-04*
-
-The **only** touchscreen in the Xteink ESP32 family. On the shared I²C bus
-**SDA 39 / SCL 38 @ 400 kHz**, at **0x5D** (alt 0x14), alongside a BM8563 RTC
-(0x51) and a [CW2017 fuel gauge](../../cellwise/cw2017/README.md) (0x63).
-
-| Signal | GPIO |
-|---|---:|
-| INT | **10** |
-| RST | **4** |
-| **Power enable** | **2 — ACTIVE-LOW** |
-
-Three separate things each leave this controller **completely silent on the bus**
-until fixed, and all three were hit during bring-up:
-
-1. **The rail is gated by GPIO2 and it is active-LOW.** The OEM drives GPIO2 **LOW**
-   (with GPIO1 HIGH) at boot. Driving it *high* — the naive "enable" — keeps the
-   GT911 unpowered; an idle scan then shows only 0x51 and 0x63.
-2. **RST = GPIO4, INT = GPIO10.** An earlier reverse-engineering pass had these
-   two reversed.
-3. **The reset must be long enough.** Too short a reset skips the internal config
-   load and the config registers read back all-zero. The SDK uses
-   **10 ms / 10 ms / 50 ms / 50 ms** with INT → INPUT.
-
-**No host config upload.** The GT911 self-loads its internal config on the
-standard reset dance, and **there is no GT911 config table anywhere in the OEM
-firmware dump** (app0, app1, spiffs or nvs) — confirming the vendor relies on
-self-load too.
-
-**Point-frame layout:** `gt911CoordsAtByte0 = true` — coordinates start at **byte
-0** of the `0x8150` read, not byte 1. The datasheet-standard layout puts a
-track-id first; this panel does not. Getting it wrong shifts every coordinate by
-one byte.
-
-**Mounting:** the digitizer is **portrait on a landscape panel**, reporting
-X: 0–480, Y: 0–800 on an 800 × 480 display → `swapXY = true`.
-
-**Capacitive Home key:** the X4 Pro's "Home" pad is a **GT911 key bit**, status
-`0x814E & 0x10`, *not* a GPIO. RE-confirmed that the OEM keys off exactly that
-bit. Surfaced as `InputManager::wasHomeKeyPressed()`.
-
-⚠ **Unresolved:** the FreeInk board header sets `flipY = true` commented *"confirmed
-by corner-tap"*, while the same repository's device document says in two places
-that `flipX`/`flipY` are **pending** a corner-tap test. See
-[`devices/xteink/x4-pro/gaps-and-conflicts.md`](../../../devices/xteink/x4-pro/gaps-and-conflicts.md).
-
-→ [`devices/xteink/x4-pro/features/touch.md`](../../../devices/xteink/x4-pro/features/touch.md)
-
 ## Artifacts
 
 | File | Bytes | SHA-256 (prefix) | Provenance |
@@ -157,7 +109,7 @@ that `flipX`/`flipY` are **pending** a corner-tap test. See
 
 **Redistribution status:** `unknown`. This is a Goodix datasheet redistributed inside an
 MIT-licensed library; the MIT licence covers SensorLib's own code, **not** the bundled
-third-party document. Kept in the repository; terms noted above.
+third-party document. Held unstaged pending review.
 
 Reacquire:
 
@@ -181,69 +133,3 @@ library bundles. That makes this copy comparatively valuable and worth preservin
 - [ESP32-P4-WIFI6-Touch-LCD-3.4C](../../../devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/README.md) · [4C](../../../devices/waveshare/esp32-p4-wifi6-touch-lcd-4c/README.md)
 - [Hynitron CST816D](../../hynitron/cst816d/README.md) — a simpler single-point alternative used on the knob board
 - [Components index](../../README.md)
-
----
-
-## Programming Guide — retrieved 2026-09-11, and how it was found by accident
-
-| Field | Value |
-|---|---|
-| Local path | [`artifacts/gt911-programming-guide-rev00-2014-08-04-crystalfontz-mirror.pdf`](artifacts/gt911-programming-guide-rev00-2014-08-04-crystalfontz-mirror.pdf) |
-| **SHA-256** | `60c6c2284b482a7acdcd2747c47a9a7d25283235ccda8c688c10e2fd3216a98b` |
-| **Bytes** | **477,454** |
-| Pages | **31**, A4 |
-| Source URL | <https://www.crystalfontz.com/controllers/UltraChip/UC8179/478/> |
-| Source class | **credible mirror** — Crystalfontz, a display distributor |
-| Retrieved | **2026-09-11**, HTTP 200, magic bytes `%PDF` |
-| **Document title** | `GOODiX GT911 Programming Guide 2014-08-04_Rev.00` |
-| Subject | *"GOODiX GT911 5-Point Capacitive Touch Controller Programming Guide"* |
-| Applicability | *"firmware of version 1040 or later"* |
-| Author | GOODiX, Shenzhen Huiding Technology Co., Ltd. |
-| Producer / dates | Acrobat Distiller 9.0.0; created 2014-08-19, modified 2019-06-24 |
-| Redistribution status | **`prohibited` as written** — the document's own first page reads *"**GOODIX CONFIDENTIAL** … Reproduction and/or distribution of this document in whole or in part is strictly prohibited without written consent of GOODIX"* |
-| Disposition | `repository`, **unstaged — flagged for the user's decision**, see below |
-
-**Text-layer validated** against the rendered page-1 heading (*"GT911 Programming
-Guide (Applicable to firmware of version 1040 or later)"*) and the disclaimer
-block.
-
-### The URL is a trap, and it is why this file exists
-
-This document was fetched while trying to obtain a **UC8179** datasheet.
-`https://www.crystalfontz.com/controllers/UltraChip/UC8179/478/` returns a valid
-PDF — of a **GOODiX touch controller**. The path segment `UltraChip/UC8179` is
-decorative; only the trailing number selects a document, and `478` is the GT911
-guide. The UC8179 document is `517`.
-
-The file is retained here rather than discarded because **it is the right
-document for this component**, filed by what it *describes* rather than by what
-was being researched — and because a near-identical mis-file is exactly the
-failure this repository's conventions exist to prevent.
-
-### What it adds
-
-Register-level detail the board profiles do not carry: the real-time command
-registers, the full configuration block, the coordinate-information layout at
-`0x814E`/`0x814F`/`0x8150`, command-status registers, HotKnot registers, the
-power-on timing diagram, and **I²C address selection during power-on or reset** —
-which is the mechanism the X4 Pro's `beginGt911()` drives with INT held at a
-level across the RST pulse to choose between `0x5D` and `0x14`.
-
-It also explains a detail a third party observed on a physical X4 Pro: the Home
-pad is a **GT911 touch key**, reported in bit 4 of `0x814E` with its key byte
-immediately after the last point record at `0x814F + 8·count` — and that the
-Linux `goodix.c` driver reads it the same way.
-
-### ⚠ Decision required from the user
-
-**This document declares itself confidential and forbids redistribution without
-GOODiX's written consent.** It is widely mirrored by distributors, which does not
-constitute permission. It is left **unstaged**, and the options are:
-
-1. keep it unstaged in the working tree (current state);
-2. move it to the local archive with a placeholder carrying this hash, size and
-   the reacquisition URL;
-3. delete the bytes and keep only this metadata block as the acquisition record.
-
-**Used by:** [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md) — the only
-Xteink device with a touchscreen.
diff --git a/components/goodix/gt911/artifacts/gt911-programming-guide-rev00-2014-08-04-crystalfontz-mirror.pdf b/components/goodix/gt911/artifacts/gt911-programming-guide-rev00-2014-08-04-crystalfontz-mirror.pdf
deleted file mode 100644
index 41f5a35..0000000
Binary files a/components/goodix/gt911/artifacts/gt911-programming-guide-rev00-2014-08-04-crystalfontz-mirror.pdf and /dev/null differ
diff --git a/components/goodix/gt9895/README.md b/components/goodix/gt9895/README.md
deleted file mode 100644
index 9b127ba..0000000
--- a/components/goodix/gt9895/README.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Goodix GT9895 — capacitive touch controller ("Berlin" series)
-
-- **Category:** projected-capacitive touchscreen controller, I²C
-- **Manufacturer:** Goodix (汇顶科技)
-- **Research status:** no public GT9895 datasheet located on 2026-09-04. Everything below is from **Linux driver evidence** and vendor BSP configuration.
-- **Retrieved:** 2026-09-04
-
-## 1. Identity and driver
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **GT9895** | S1, S2 |
-| Family | Goodix **"Berlin"** — the modern large-panel generation, not the GT911/GT9271 generation | S3 |
-| Linux driver | `CONFIG_TOUCHSCREEN_GOODIX_BRL` (`goodix_berlin`) | S3 |
-| **Not** the legacy driver | `CONFIG_TOUCHSCREEN_GOODIX` is explicitly **disabled** in the same fragment | S3 |
-| Bus | I²C | S1 |
-| 7-bit address as used | **`0x5D`** | S1 |
-| Signals | SDA, SCL, IRQ, RESET | S1 |
-
-## 2. Why the family distinction matters
-
-This repository already holds [GT911](../gt911/README.md) and [GT9271](../gt9271/README.md).
-**Do not treat GT9895 as a drop-in for either.** They are different generations with different
-Linux drivers, different register maps and different firmware-download behaviour:
-
-| | GT911 / GT9271 | **GT9895** |
-|---|---|---|
-| Linux driver | `goodix` (`drivers/input/touchscreen/goodix.c`) | **`goodix_berlin`** (`goodix_berlin_core.c` + `_i2c.c`/`_spi.c`) |
-| Kconfig | `TOUCHSCREEN_GOODIX` | `TOUCHSCREEN_GOODIX_BRL` |
-| Typical addresses | `0x5D` / `0x14` | `0x5D` |
-| Config/firmware | config table written over I²C | Berlin-style firmware + config binary |
-
-The addresses overlap at `0x5D`, which is precisely why the mistake is easy to make: an I²C
-scan cannot tell them apart. The driver choice can.
-
-## 3. Board-level behaviour on the K230
-
-The LilyGO BSP builds the Berlin driver **in-tree** (not as a module) and carries a very large
-downstream patch — `0034-gt9895-touch.patch`, **307 439 bytes** — which is far larger than a
-bring-up patch and indicates a substantially vendored driver rather than a device-tree
-addition. That patch is the authoritative description of this part's behaviour on this board.
-
-**The IRQ and reset lines are shared with the optional LT9611 HDMI bridge** (`GPIO23` IRQ,
-`GPIO24` reset). Anything that resets HDMI resets touch. See
-[resources-and-conflicts.md](../../../devices/lilygo/t-display-k230/resources-and-conflicts.md).
-
-## 4. Unknowns
-
-- No datasheet, no register map, no maximum I²C rate, no supply limits from Goodix.
-- Reported touch-point count and panel size support: unknown from primary sources; the
-  launcher has a `ui_multitouch.c` test page but the point count is not asserted anywhere
-  authoritative.
-- Alternative I²C addresses: unknown.
-
-## 5. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-Touch controller for the 4.1″ RM69A10 AMOLED. I²C3 on **`GPIO37` SDA / `GPIO36` SCL** at
-**`0x5D`**, IRQ on **`GPIO23`**, reset on **`GPIO24`**. Both interrupt and reset are physically
-shared with the LT9611 HDMI path on this board.
-
-## 6. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | Address `0x5D`, GPIO36/37/23/24, shared IRQ/reset with LT9611 |
-| S2 | T-Display K230 wiki page | LILYGO | primary | official wiki | `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/` | 2026-09-04 | "GT9895 capacitive touch" |
-| S3 | `k230_bsp/overlay/buildroot-overlay/linux/linux.fragment` and `0034-gt9895-touch.patch` | LILYGO | primary | source | same repo | 2026-09-04 | `TOUCHSCREEN_GOODIX_BRL=y`, legacy `TOUCHSCREEN_GOODIX` disabled, 307 KB vendored driver patch |
diff --git a/components/hynitron/cst226se/README.md b/components/hynitron/cst226se/README.md
deleted file mode 100644
index a4c25d1..0000000
--- a/components/hynitron/cst226se/README.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# Hynitron CST226SE
-
-- **Category:** multi-point capacitive touch controller, I²C slave.
-- **Manufacturer:** Hynitron Microelectronics.
-- **Retrieved:** 2026-09-07
-- **Siblings here:** [`cst816d`](../cst816d/README.md) · [`cst328`](../cst328/README.md) ·
-  [`cst3530`](../cst3530/README.md)
-
-The touch controller of the **LilyGO T-Display-S3 Pro** and the **LilyGO T4-S3**.
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **CST226SE** | LilyGO's T-Display-S3-Pro README I²C table |
-| I²C address | **`0x5A`** | same table, which lists it beside SY6970 `0x6A` and LTR-553ALS `0x23` |
-| Datasheet | **not retrieved.** LilyGO links a Chinese Hynitron porting manual hosted in `lewisxhe/SensorLib` (`海栎创触摸芯片移植手册-v3.5-20220701(1).pdf`) rather than mirroring it | `LilyGo-AMOLED-Series` README § *T4-S3 datasheet* |
-| Local artifact | **none** | — |
-
-**Acquisition note for the next reader:** the document LilyGO points at is a *touch-chip porting
-manual* covering several Hynitron parts, not a CST226SE datasheet, and it lives in a third-party
-repository (`lewisxhe/SensorLib`, `datasheet/` directory). Retrieving it and pinning it to a
-commit is the obvious next step and was not done here.
-
-## 2. Software
-
-`lewisxhe/SensorLib` is the driver LilyGO uses on both boards — the same author maintains
-`XPowersLib` for the SY6970/AXP2101 parts. `LilyGo-AMOLED-Series` declares **SensorLib v0.2.4**
-as a dependency; the T-Display-S3-Pro repo uses `TouchLib` instead. Two vendor boards, two
-different touch libraries for the same controller — worth knowing before assuming code ports.
-
-## 3. What was not verified
-
-No datasheet, no register map, no timing. The address `0x5A` is from LilyGO's own README table
-and is **not** independently confirmed. Note that `0x5A` is also the I²C address of the
-DRV2605L haptic driver documented elsewhere in this repository — if you are scanning a bus that
-could contain either, the address alone will not tell you which.
-
-## 4. Used by
-
-### LilyGO T-Display-S3 Pro
-→ [`devices/lilygo/t-display-s3-pro`](../../../devices/lilygo/t-display-s3-pro/README.md)
-
-I²C `0x5A` on **SDA GPIO5 / SCL GPIO6**, shared with the SY6970 PMIC (`0x6A`), the LTR-553ALS
-ambient-light sensor (`0x23`) and the camera. Reset **GPIO13**. Interrupt **GPIO7** per
-`product_pins.h` — note the board's own `utilities.h` does **not** define a touch IRQ at all.
-
-### LilyGO T4-S3
-→ [`devices/lilygo/t4-s3`](../../../devices/lilygo/t4-s3/README.md)
-
-I²C on **SDA GPIO6 / SCL GPIO7**, interrupt **GPIO8**, reset **GPIO17**.
diff --git a/components/hynitron/cst328/README.md b/components/hynitron/cst328/README.md
deleted file mode 100644
index b01d333..0000000
--- a/components/hynitron/cst328/README.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# Hynitron CST328
-
-- **Category:** **mutual-capacitance** multi-touch controller, I²C slave.
-- **Manufacturer:** Hynitron Microelectronics (上海海栎创).
-- **Retrieved:** 2026-09-07
-- **Sibling record here:** [`cst816d`](../cst816d/README.md) — the *self*-capacitance CST816
-  family this part replaced on LilyGO's boards.
-
-The touch controller on **later** production of the **LilyGO T-Display-S3 Touch**.
-
-## 1. Why this record exists separately from CST816
-
-Because they are not interchangeable, and LilyGO swapped one for the other **without renaming
-the product**.
-
-| | CST816S | **CST328** |
-|---|---|---|
-| Sensing | **self**-capacitance | **mutual**-capacitance |
-| I²C address | `0x15` | **`0x1A`** |
-| `TouchLib` build flag | `-DTOUCH_MODULES_CST_SELF` | **`-DTOUCH_MODULES_CST_MUTUAL`** |
-| Multi-touch | limited | more simultaneous points |
-
-Mutual capacitance is the better technology — it resolves multiple touches properly and is less
-affected by a hand hovering — which is presumably why the swap happened. The cost is that
-firmware built for one reports **"no Touch IC found"** on the other, and the flag that selects
-between them lives in `platformio.ini`, not in the sketch. That is
-[LilyGO issue #125](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/125) (15 comments).
-
-**LilyGO's current default is `-DTOUCH_MODULES_CST_MUTUAL`**, i.e. CST328 — see
-`platformio.ini` @ `ec889e789b3cf093412689a143f7f37b42b56af7`.
-
-## 2. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **CST328** |
-| Datasheet | `CST328数据手册V2.2.pdf` — Chinese, **V2.2** per the filename |
-| Local artifact | [`artifacts/cst328-datasheet-cn-v2.2-lilygo-mirror.pdf`](artifacts/cst328-datasheet-cn-v2.2-lilygo-mirror.pdf) — 1 297 291 B, SHA-256 `fd7770d17fb29bf6bc3f0b6116f940d8249a3ab9129c9df1491e24078b6fcbd6` |
-| Mirror source | `Xinyuan-LilyGO/T-Display-S3` → `datasheet/CST328数据手册V2.2.pdf` @ `ec889e7` |
-| Language | **Chinese only.** No English version was located, from Hynitron or any mirror. Per the multi-language policy this is therefore the **primary source**, not a translation, and it is retained on its own merits |
-| Licence | Hynitron copyright; the surrounding repository is MIT, which does not cover it. **Redistribution status: unknown** |
-
-The presence of *both* this datasheet and the CST816S register guide in one board repository is
-the evidence that both controllers ship — a board with one controller does not need two
-manuals.
-
-## 3. Software
-
-| Route | Note |
-|---|---|
-| **`mmMicky/TouchLib`** | the Arduino driver LilyGO uses. Select the mutual branch with `-DTOUCH_MODULES_CST_MUTUAL` |
-| ESP-IDF | no first-party driver; use `LilyGo-Display-IDF` or write one. [Issue #156](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/156) is someone discovering this |
-| ESPHome | the `T-DISPLAY-S3` model covers the display only; touch is configured separately |
-
-**Reset before probing.** Hold `RST` low ≥ 10 ms, release, wait ≥ 50 ms. Many "intermittent
-touch" reports are a missing reset.
-
-**Expect NAKs.** The CST parts NAK while idle; a driver that treats a NAK as a bus fault will
-log errors continuously. That is
-[issue #168](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/168) (21 comments), where the
-reporter had nothing else on the bus.
-
-## 4. What was not verified
-
-The datasheet was **not read** — it is in Chinese, its text layer was not validated against a
-rendered heading, and **no register value is transcribed into this record**. The addresses and
-flag names above come from board-level and library-level sources. Reading the register map is
-the obvious next step and would let this record document the protocol properly.
-
-## 5. Used by
-
-### LilyGO T-Display-S3 Touch (later production)
-→ [`devices/lilygo/t-display-s3-touch`](../../../devices/lilygo/t-display-s3-touch/README.md)
-
-I²C address **`0x1A`** on **GPIO17 (SCL) / GPIO18 (SDA)**, with on-board 10 kΩ pull-ups.
-Interrupt **GPIO16**, reset **GPIO21**. The controller sits on the panel flex, not on the
-mainboard, which is why it does not appear in the board schematic's part census — and it is
-powered from the **GPIO15-gated rail**, so an I²C scan with GPIO15 low finds nothing.
-Revision detail: [R1](../../../devices/lilygo/t-display-s3-shared/board-revision-drift.md#r1--t-display-s3-touch-cst816s--cst328).
diff --git a/components/hynitron/cst328/artifacts/cst328-datasheet-cn-v2.2-lilygo-mirror.pdf b/components/hynitron/cst328/artifacts/cst328-datasheet-cn-v2.2-lilygo-mirror.pdf
deleted file mode 100644
index 020a023..0000000
Binary files a/components/hynitron/cst328/artifacts/cst328-datasheet-cn-v2.2-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/hynitron/cst3530/README.md b/components/hynitron/cst3530/README.md
deleted file mode 100644
index b99b86c..0000000
--- a/components/hynitron/cst3530/README.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# Hynitron CST3530
-
-- **Category:** capacitive touch controller, I²C slave.
-- **Manufacturer:** Hynitron Microelectronics.
-- **Retrieved:** 2026-09-07
-- **Siblings here:** [`cst816d`](../cst816d/README.md) · [`cst328`](../cst328/README.md) ·
-  [`cst226se`](../cst226se/README.md)
-
-The touch controller on **later production** of the **LilyGO T-Display-S3 Long**, where it
-replaces or supplements the AXS15231B's integrated touch.
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **CST3530** |
-| Datasheet | `CST3530数据手册V1.0(1).pdf` — Chinese, **V1.0** |
-| Local artifact | [`artifacts/cst3530-datasheet-cn-v1.0-lilygo-mirror.pdf`](artifacts/cst3530-datasheet-cn-v1.0-lilygo-mirror.pdf) — 781 716 B, SHA-256 `3a103cef456f696f8861593871e2cf94d71982ff5f0791384ef190fb6b9baca7` |
-| Mirror source | `Xinyuan-LilyGO/T-Display-S3-Long` → `datasheet/CST3530数据手册V1.0(1).pdf` @ `37a7e83af79a98bb395012200f811777e52b9cfc` |
-| Language | Chinese only; no English version located. **Primary source in its own right** |
-| Related document in the same repo | `CST66xx_Application Note_en_V1.01.pdf` — an **English** application note for a *different* Hynitron family, shipped alongside. Whether it applies to the CST3530 is **unknown** |
-| Licence | Hynitron copyright. **The T-Display-S3-Long repository declares no licence at all**, so redistribution status is doubly unknown |
-
-## 2. How you know a board has it
-
-The `T-Display-S3-Long` repository's **default branch is `T-Display-S3-Long-cst3530`** and it
-ships **two factory images**:
-
-| Image | Bytes |
-|---|---|
-| `firmware/factory.bin` | 1 815 872 |
-| `firmware/factory-cst3530.bin` | 2 158 624 |
-
-plus `examples/cst3530_touch/` beside the original AXS15231B touch path. **Flash `factory.bin`;
-if touch does not respond, flash `factory-cst3530.bin`.** That is the only identification
-procedure that exists — LilyGO published no statement about the change.
-
-## 3. What was not verified
-
-The datasheet was **not read**; no I²C address, register or timing value is transcribed here.
-The I²C address is therefore **unknown** — do not assume it matches the AXS15231B's `0x3B`.
-An I²C scan on the Long's bus (SDA GPIO15 / SCL GPIO10) will find it.
-
-## 4. Gaps
-
-- Register map, address and protocol: unknown.
-- Whether the CST3530 **replaces** the AXS15231B's integrated touch or **supplements** it is
-  unknown. Both readings are consistent with a separate example and a separate firmware image.
-- Whether the English `CST66xx` application note applies.
-- Not verified on hardware.
-
-## 5. Used by
-
-### LilyGO T-Display-S3 Long (later production)
-→ [`devices/lilygo/t-display-s3-long`](../../../devices/lilygo/t-display-s3-long/README.md)
-
-I²C on **GPIO15 (SDA) / GPIO10 (SCL)**; the board also defines `TP_RST` GPIO2 and `TP_IRQ`
-GPIO11. Note the vendor's `pins_config.h` has `PIN_BAT_VOLT 2` colliding with `TP_RST 2` —
-see the device record's conflict L1.
-Revision detail: [R5](../../../devices/lilygo/t-display-s3-shared/board-revision-drift.md#r5--t-display-s3-long-cst3530-touch-appears-mid-life-in-a-branch).
diff --git a/components/hynitron/cst3530/artifacts/cst3530-datasheet-cn-v1.0-lilygo-mirror.pdf b/components/hynitron/cst3530/artifacts/cst3530-datasheet-cn-v1.0-lilygo-mirror.pdf
deleted file mode 100644
index 9319b54..0000000
Binary files a/components/hynitron/cst3530/artifacts/cst3530-datasheet-cn-v1.0-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/hynitron/cst816d/README.md b/components/hynitron/cst816d/README.md
index e3b87bf..097c545 100644
--- a/components/hynitron/cst816d/README.md
+++ b/components/hynitron/cst816d/README.md
@@ -430,9 +430,6 @@ For ESP-IDF, `esp_lcd_touch` abstracts all of these behind one handle type, whic
 
 ## Used By
 
-- [LilyGO T-Display-S3 Touch](../../../devices/lilygo/t-display-s3-touch/README.md) — **CST816S**, the touch controller of *early* production of LilyGO's 1.9″ 170×320 board. I²C `0x15` on GPIO17 (SCL) / GPIO18 (SDA), on-board 10 kΩ pull-ups, `INT` GPIO16, `RST` GPIO21. Selected in software with `-DTOUCH_MODULES_CST_SELF`. **Later production substitutes the mutual-capacitance [CST328](../cst328/README.md) at `0x1A`** without renaming the product — see [board-revision-drift R1](../../../devices/lilygo/t-display-s3-shared/board-revision-drift.md#r1--t-display-s3-touch-cst816s--cst328). The controller sits on the panel flex and is powered from the board's GPIO15-gated rail, so an I²C scan with GPIO15 low finds nothing.
-- [LilyGO T-Display-S3 AMOLED](../../../devices/lilygo/t-display-s3-amoled/README.md) — a CST816-family part is the touch controller on the Touch SKUs of the 1.91″ AMOLED board. LilyGO mirrors `CST816_Register.pdf` in `LilyGo-AMOLED-Series`; retained here as [`artifacts/cst816-register-en-lilygo-mirror.pdf`](artifacts/cst816-register-en-lilygo-mirror.pdf) (66 813 B, SHA-256 `696d3517c7c21ea575f4cd63b6debc20727b74ef1b5188ecdf23bec6b5867b43`), alongside the CST816S Chinese register guide LilyGO ships in the T-Display-S3 repo, [`artifacts/cst816s-register-guide-cn-20190508-lilygo-mirror.pdf`](artifacts/cst816s-register-guide-cn-20190508-lilygo-mirror.pdf) (76 816 B, SHA-256 `c39871756afd65fb043bb262f6cf9d0c8e1d2526ecc521ffa8f6b56345ff7643`). Both retrieved 2026-09-07.
-
 - [Waveshare ESP32-S3-Knob-Touch-LCD-1.8](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) — touch controller of the bonded 360 × 360 round panel. I²C `0x15` on S3 GPIO11 (SDA) / GPIO12 (SCL), `INT` GPIO9, `RST` GPIO10; shares the bus with the DRV2605L at `0x5A`. See [Pinouts and buses § Bus inventory](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/pinouts-and-buses.md).
 
 ## Related components
@@ -468,7 +465,7 @@ publish datasheets openly; the Waveshare mirror is effectively the primary sourc
 The Waveshare device record previously held a second copy at
 `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/CST816D_datasheet_En_V1.3.pdf`.
 It was confirmed **byte-identical** to the file above — same SHA-256 `a0b14a06…`, same 1,098,205
-bytes, `cmp` clean. The device-side copy was moved to `archive/` on 2026-08-24 and
+bytes, `cmp` clean. The device-side copy was moved to `../hardware-doc-archive/` on 2026-08-24 and
 the copy here is canonical. See the placeholder at
 `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/README.md`.
 
diff --git a/components/hynitron/cst816d/artifacts/cst816-register-en-lilygo-mirror.pdf b/components/hynitron/cst816d/artifacts/cst816-register-en-lilygo-mirror.pdf
deleted file mode 100644
index e79178b..0000000
Binary files a/components/hynitron/cst816d/artifacts/cst816-register-en-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/hynitron/cst816d/artifacts/cst816s-register-guide-cn-20190508-lilygo-mirror.pdf b/components/hynitron/cst816d/artifacts/cst816s-register-guide-cn-20190508-lilygo-mirror.pdf
deleted file mode 100644
index 998e587..0000000
Binary files a/components/hynitron/cst816d/artifacts/cst816s-register-guide-cn-20190508-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/infineon/bgs13sn8/README.md b/components/infineon/bgs13sn8/README.md
deleted file mode 100644
index 8eb517c..0000000
--- a/components/infineon/bgs13sn8/README.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Infineon BGS13SN8
-
-- **Category:** **SP3T (single-pole, triple-throw) RF switch**, sub-1 GHz
-- **Ordering part as fitted:** **`BGS13SN8E6327XTSA1`** (`E6327` = green/RoHS tape-and-reel
-  suffix; `XTSA1` = packing)
-- **Research status:** **no datasheet retrieved.** Identity from a schematic symbol;
-  behaviour inferred from how the board drives it and from the vendor's published truth
-  table.
-- **Retrieved:** 2026-09-04
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **Infineon Technologies** (`BGS` = Infineon RF-switch family) | part-number convention, `inferred` |
-| Function | **SP3T RF switch** — one common port, three switched ports | M5Stack product page: *"Built-in dual single-pole triple-throw (SP3T) RF switches"* |
-| Control | **two logic inputs `V1`, `V2`** | schematic |
-| Ports as drawn | `RF1` (5), `RF2` (7), `RF3` (4), `RFin` (6); `V1` (3), `V2` (2), `VDD` (1), `GND` (8) — pin numbering differs between the two instances as drawn | schematic |
-| Supply | `VDD_3V3`, decoupled `C56`/`C57` 100 nF | schematic |
-
-⚠ **Insertion loss, isolation, power handling, control-logic thresholds and switching time
-are not stated here** — no datasheet was retrieved. Anything performance-related about this
-part in the device records is a *board-level* vendor claim.
-
-## 2. What it is doing on the one board that uses it
-
-A CC1101 covers 315/433/868/915 MHz, but a single matching network cannot. The Cap CC1101
-places **two** BGS13SN8 devices either side of **three** narrowband LC matching paths and
-switches whole paths in and out:
-
-```
-CC1101 ─ balun ─▶ U4 (SP3T) ─┬─ 315 MHz match ─┬─▶ U5 (SP3T) ─▶ SMA
-                             ├─ 433 MHz match ─┤
-                             └─ 868/915 match ─┘
-              V1,V2 ◀── RF_SW0, RF_SW1 ──▶ V1,V2
-```
-
-Both switches are driven from the **same two nets**, so they move together. Truth table (from
-M5Stack's product page and Arduino guide, which agree):
-
-| `RF_SW0` | `RF_SW1` | Band |
-|:---:|:---:|---|
-| 0 | 0 | 315 MHz |
-| 0 | 1 | 433 MHz |
-| 1 | 1 | 868 / 915 MHz |
-
-`1,0` unlisted — undefined.
-
-⚠ **Which physical switch port carries which band path was not resolved** pin-by-pin from
-the schematic text layer. The aggregate mapping above is vendor-published; the port-level
-mapping is a gap.
-
-## 3. Used By
-
-### [M5Stack Cap CC1101 & NFC (U219)](../../../devices/m5stack/cap-cc1101/README.md) — designators `U4` and `U5`, sheet 3
-
-| Item | Value |
-|---|---|
-| Count | **two** |
-| Control nets | `CC1101_RF_SW0` (from host **G13**, or **G14** on CardputerZero) and `CC1101_RF_SW1` (from the **CC1101's own `GDO2` pin**) |
-| Supply | `VDD_3V3` with `C56` / `C57` 100 nF |
-| Common port | `E1` `SMA-TH_KH-SMA-KE-Z` antenna connector |
-| Band paths | 315 MHz (`L6` 10 nH, `L7` 0 R, `L8` 10 nH, `L17` 3.6 nH, `C50` 8 pF, `C51` DNP) · 433 MHz (`L9`, `L10`–`L13` = 0 R/0 R/15 nH/0 R, `C52`–`C55` = 10 pF/NC/6.2 pF) · 868–915 MHz (`L15` 0 R, `L16` 10 nH, `C58`–`C61`, `R7`, `D1` 0 R) |
-
-The clever part is not the switch — it is that **only one of its two control lines costs a
-host GPIO**. Full walkthrough:
-[`devices/m5stack/cap-cc1101/features/band-switching.md`](../../../devices/m5stack/cap-cc1101/features/band-switching.md).
-
-## 4. Reusability
-
-This is a transferable pattern for any multi-band sub-GHz design: **wideband balun at the
-transceiver, narrowband matched paths, SP3T switches at both ends, one antenna port.** The
-alternatives are worse — a single compromise match loses several dB in every band, and
-separate antenna connectors per band cost mechanical space and confuse users.
-
-## 5. Local artifacts
-
-**None.** An Infineon datasheet would fill in §1 and settle §2's port mapping.
-
-## 6. Sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|
-| B-1 | Cap CC1101 schematic V0.3 | M5Stack | primary | [`devices/m5stack/cap-cc1101/artifacts/schematic/`](../../../devices/m5stack/cap-cc1101/artifacts/schematic/) | 2026-09-04 | Part number `BGS13SN8E6327XTSA1`, two instances, control nets, band paths |
-| B-2 | Cap CC1101 documentation | M5Stack | primary | `https://docs.m5stack.com/en/cap/Cap_CC1101` | 2026-09-04 | "dual SP3T" description and the **truth table** |
-| B-3 | Cap CC1101 Arduino guide | M5Stack | primary | `https://docs.m5stack.com/en/arduino/projects/cap/cap_cc1101` | 2026-09-04 | Truth table restated in code form |
-| B-4 | r/CardPuter release thread | community | `https://old.reddit.com/r/CardPuter/comments/1w0nwti/` | 2026-09-04 | Independent statement of the SW0/SW1 sources |
diff --git a/components/injoinic/ip2315/README.md b/components/injoinic/ip2315/README.md
deleted file mode 100644
index 4c465c0..0000000
--- a/components/injoinic/ip2315/README.md
+++ /dev/null
@@ -1,290 +0,0 @@
-# Injoinic IP2315
-
-> Single-cell Li-ion **synchronous buck charger** with integrated power MOSFETs, integrated USB input fast-charge protocol handling (PD / FCP / AFC / PE+), 4.8 A maximum charge current, and an I²C control interface **multiplexed onto its battery-level LED driver pins**.
-> Research snapshot **2026-09-01**. Fitted as **`U1`** on sheet 2 of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153). **No hardware was available** — every claim below traces to the Injoinic datasheet, the PaperMono schematic PDF, or M5Stack's published source.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Injoinic `IP2315` datasheet **V1.0** (Chinese), local copy `artifacts/ip2315-datasheet-v1.0-cn-radxa-mirror.pdf` | `not-tested` — vendor document reproduced |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, cited by sheet + designator + pin. Extraction is text-layer parsing of the Altium PDF | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | M5Stack source at a cited `file:line` | `executed-success` for the read |
-| **[DOC]** | `docs.m5stack.com/en/core/PaperMono`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference drawn from two or more of the above | `inferred` |
-
-**Nothing here was verified electrically.** No register, address or pin was guessed.
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **IP2315** (the schematic annotates it `IP2315（无后缀）` — "no suffix") | **[SCH]** sheet 2 |
-| Manufacturer | **Injoinic Technology** (英集芯), Shenzhen | **[DS]** cover, `service@injoinic.com` |
-| Function | Integrated-MOSFET synchronous buck charger for 1S Li-ion with USB input fast-charge protocol negotiation | **[DS]** §概述 |
-| Package | **QFN32, 5 mm × 5 mm, 0.5 mm pitch** (31 signal pins + EPAD pin 33) | **[DS]** 特性 |
-| Switching frequency | **500 kHz** | **[DS]** §概述 |
-| **I²C address** | **`0xEA` write / `0xEB` read (8-bit) = `0x75` 7-bit** | **[DS]** §I2C; **[SRC]** `M5Unified/src/utility/Power_Class.cpp:72`; **[DOC]** |
-| I²C rate | up to **400 kbps**; 8-bit register address, 8-bit data, MSB first | **[DS]** §I2C |
-| Datasheet revision | **V1.0**, © 2018 Injoinic Corp., 16 pp | **[DS]** footer |
-| Copyright year on document | 2018 — the document has not been revised since | **[DS]** |
-
-> ⚠ **The 7-bit address is 0x75 and the datasheet never says so.** The datasheet gives only the 8-bit forms `0xEA`/`0xEB`. `0xEA >> 1 = 0x75`. Anyone comparing the datasheet against M5Stack's `0x75` without doing that shift will conclude the two disagree. They do not. **[INF]**
-
----
-
-## 2. Key electrical limits and capabilities **[DS]**
-
-| Parameter | Value |
-|---|---|
-| Input voltage range | **5 V – 12 V** |
-| Maximum battery charge current | **4.8 A** at 9 V / 2 A input |
-| Battery float voltage | **4.2 / 4.35 / 4.4 / 4.5 V**, selected by a resistor on the `VSET` pin (which is multiplexed with `LED3`) |
-| Charge current setting | resistor on `ICHGSET` (pin 27) sets the **input-side** current |
-| Efficiency | 94 % @ 5 V in, 93.5 % @ 9 V, 93 % @ 12 V (BAT 3.7 V, 4 A) |
-| Input fast-charge protocols | **USB Type-C PD**, Huawei **FCP**, Samsung **AFC**, MTK **PE+ 1.1 / 2.0** |
-| Adaptive behaviour | reduces charge current automatically when a weak adapter cannot hold up |
-| Status indication | 1 or 2 LEDs, count auto-detected |
-| Protections | NTC battery temperature, input over-voltage, chip over-temperature |
-| ESD | 4 kV |
-
-### 2.1 `ICHGSET` resistor table **[DS §恒流充电电流设置]**
-
-The resistor from `ICHGSET` (pin 27) to GND sets the **input** current, not the battery current:
-
-| R<sub>ICHG</sub> | Input current set |
-|---|---|
-| 51 kΩ | 500 mA |
-| 130 kΩ | 1000 mA |
-| 180 kΩ | 1500 mA |
-| > 300 kΩ (NC) | 2000 mA |
-
-### 2.2 `NTC` network **[DS §充电 NTC]**
-
-The `NTC` pin (26) sources **20 µA** into an external network and compares the resulting voltage:
-
-| Condition | Meaning |
-|---|---|
-| V(NTC) > **1.32 V** | battery too **cold** |
-| V(NTC) < **0.43 V** | battery too **hot** |
-
-Normal charging is permitted between roughly **0 °C and 55 °C**. The datasheet's worked example is *"R<sub>NTC</sub> = 100 kΩ @ 25 °C (B = 4100), R2 = 82 kΩ"*.
-
-> ⚠ **`NTC` must never float.** If the function is unused the datasheet requires a **51 kΩ** resistor to GND; a floating pin *"可能导致充电异常"* — may cause abnormal charging. **[DS]**
-
----
-
-## 3. ⚠ The I²C pins are the LED driver pins — this is the whole hazard
-
-This is the single most important thing to understand about this part, and it is the mechanism behind the warning M5Stack publishes for the PaperMono.
-
-**[DS §引脚说明]** gives the pin functions verbatim:
-
-| Pin | Name | Datasheet description (translated) |
-|---:|---|---|
-| **8** | **`LED1`** | Battery-level LED drive pin L1; **`SCK` when the I²C function is used** |
-| **9** | **`LED2`** | Battery-level LED drive pin L2; **`SDA` when the I²C function is used** |
-| **10** | **`LED3`** | Battery-level LED drive pin L3; **multiplexed with `VSET`** |
-
-So the chip has exactly one set of pins that must serve as either a **current-sinking LED indicator driver**, a **battery-voltage select strap**, or an **I²C slave port** — and it decides which at power-up, from what it sees on those pins.
-
-**[DS §I2C]** shows the vendor's reference connection, and the detail that matters is the supply the pull-ups return to:
-
-```
-                       VBAT
-                        |
-        +---------------+---------------+
-        |                               |
-      2K2                             2K2
-        |                               |
-  MCU --+-- SCL ----------------- 8  IP2315
-  MCU --+-- SDA ----------------- 9
-  MCU ------ INT ---------------- 10
-```
-
-**Both I²C pull-ups go to `VBAT`, not to the host's logic rail.** That is what M5Stack's product page is describing when it says:
-
-> *"The I2C operating mode of the charging chip IP2315 depends on the I2C pins being pulled up to VBAT voltage. Connecting the device to USB triggers mode detection; if the VBAT voltage is too low, the IP2315 may not initialize into I2C mode properly, which can interfere with other devices on the same I2C bus."* **[DOC]**
-
-### 3.1 The second half of the hazard: a missing NACK wedges the bus
-
-**[DS §I2C, 特别说明]**, translated:
-
-> *"At the end of an I²C read, when the last byte has been read, a **NACK signal must be given**. Otherwise the IP2315 believes the MCU still wants more data, will output the next byte on the following SCLK, will not receive the STOP condition properly, and **this may lock up the I²C bus** (可能会导致 I2C 总线拉死)."*
-
-The vendor also requires read–modify–write on every register and forbids touching reserved bits:
-
-> *"Reserved registers must not be written arbitrarily and their existing values must not be changed, or unpredictable results will occur. Register operations must be performed read-modify-write, changing only the bits in use."*
-
-**Put the two together and the PaperMono's design makes sense as a defensive measure, not a nicety.** A part that (a) may fail to enter I²C mode at all if the battery is flat, and (b) can hold SDA/SCL indefinitely after a mis-terminated read, is a part you do not want permanently attached to a bus shared with the touch controller, RTC, IMU, NFC reader and both M5Stack coprocessors.
-
----
-
-## 4. Pinout as fitted on the PaperMono **[SCH sheet 2, `U1`]**
-
-Recovered from the Altium PDF's pin markers. The parser attributes markers `PIU10x` to designator `U1` pin `0x`; the second charger-column designator on that sheet is the JW5712 (`U10`), which is a separate part.
-
-| Pin | Name | Net on PaperMono | Notes |
-|---:|---|---|---|
-| 2 | `CC1` | USB-C `CC1` **through `R1` = `NC/1%`** | ⚠ §4.1 |
-| 3 | `CC2` | USB-C `CC2` **through `R2` = `NC/1%`** | ⚠ §4.1 |
-| 6, 7, 18, 19 | `VSYS` | `VBAT_L0` side, with `C6`, `C7`, `R6`, `R7` | "input intermediate node, requires capacitors" **[DS]** |
-| **8** | **`LED1` / `SCL`** | **`CHG_SYS_SCL`** | → B-side of the `AW39112DNR` gate (`U3`) |
-| **9** | **`LED2` / `SDA`** | **`CHG_SYS_SDA`** | → B-side of the `AW39112DNR` gate (`U3`) |
-| 10 | `LED3` / `VSET` | local network with `R11` (`NC`) / `R12` (`100 kΩ`) and `LED1` (a real indicator LED on sheet 2) | battery float-voltage strap |
-| 11–14 | `LX` | `L1` = `FTC252012S2R2MBCA` (2.2 µH) | buck switching node |
-| 15 | `BST` | `100 nF/25 V` to `LX` | bootstrap |
-| 16 | `HLED` | `Q1` (`CJ3439KDW` dual MOSFET) | fast-charge mode status output **[DS]** |
-| 17, 31 | `GND` | `GND` | |
-| 20, 21 | `VIN` | **`5V_IN`** — the output of the [AW32901FCR](../../awinic/aw32901/README.md) OVP switch | sheet annotates "PD Only" and "Ipeak 1.5A" |
-| 22 | `BAT` | `VBAT_L0` | battery sense / charge output |
-| 23 | `DM` | local network with `D1` (`DSK34`), `R3` (1 MΩ) | BC1.2 / legacy adapter detect |
-| 24 | `DP` | same network | |
-| **26** | **`NTC`** | `R15` = **`100K-RNTC`** thermistor + `R16` = **82 kΩ** | matches the datasheet's worked example exactly |
-| **27** | **`ICHGSET`** | one of `R17` = 15 kΩ / `R18` = `NC` | ⚠ §4.2 |
-| 33 (EPAD) | `GND` | `GND` | power + thermal ground |
-
-Input bulk on this rail is `C8`–`C11` = 4 × 22 µF/10 V. **[SCH]**
-
-### 4.1 ⚠ PD is depopulated — this is a 5 V charger in practice
-
-The series resistors on both CC pins, `R1` and `R2`, carry the value **`NC/1%`** in the schematic's text layer — i.e. **not fitted**. **[SCH]**
-
-Independently, the IP2315's `VIN` comes from `5V_IN`, the output of the [AW32901FCR](../../awinic/aw32901/README.md), whose over-voltage threshold is **5.95 V typical** — it disconnects the input before 9 V could ever arrive.
-
-**Consequence:** the IP2315's headline capability — asking a PD/FCP/AFC/PE+ adapter for 9 V or 12 V to shorten charge time — **cannot function on this board**, twice over. It runs as a plain 5 V-input buck charger. **[INF]**, from two `executed-success` schematic observations. Anyone reading the IP2315 datasheet and expecting 9 V behaviour from a PaperMono will be surprised; anyone porting this charger design to a board that *does* want fast charge must populate `R1`/`R2` **and** move to a higher-threshold AW329xx.
-
-### 4.2 ⚠ Unresolved: which resistor lands on `ICHGSET`
-
-Four resistors sit in a row under the `NTC` / `ICHGSET` pins: `R15` = `100K-RNTC`, `R16` = `82 kΩ/1%`, `R17` = `15 kΩ/1%`, `R18` = `NC/1%`. **[SCH]**
-
-`R15` + `R16` are unmistakably the NTC network — they reproduce the datasheet's own worked example (100 kΩ NTC @ 25 °C, R2 = 82 kΩ) verbatim. Which of `R17`/`R18` reaches `ICHGSET` was **not resolved** from the PDF text layer, and **15 kΩ does not appear in the datasheet's `ICHGSET` table at all** (51 k / 130 k / 180 k / NC). Sheet 1's block diagram annotates the charge current as **0.5 C**, which for the 1150 mAh cell is ≈575 mA — closest to the 51 kΩ / 500 mA row.
-
-This should be read off the rendered schematic sheet graphically before being relied on. Recorded as an open question rather than guessed.
-
----
-
-## 5. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`U1`**, schematic sheet 2.
-
-Charges the 1150 mAh single-cell battery from the USB-C port, behind the [AW32901FCR](../../awinic/aw32901/README.md) input over-voltage switch. It is **not permanently attached to the system I²C bus**.
-
-**The gate.** `CHG_SYS_SCL` / `CHG_SYS_SDA` (pins 8/9) reach the shared system bus only through an [**AW39112DNR**](../../awinic/aw39112/README.md) 2-bit level translator, `U3`: **[SCH]** sheet 2
-
-| `U3` pin | Name | Net |
-|---:|---|---|
-| 1 | `VCCA` | `VBUS_L0` |
-| 2 | `A1` | `G48_SYS_SCL` (ESP32-S3 GPIO48) |
-| 3 | `A2` | `G47_SYS_SDA` (ESP32-S3 GPIO47) |
-| 4 | `GND` | `GND` |
-| **5** | **`OE`** | **`PYB_CHG_IIC`** |
-| 6 | `B2` | `CHG_SYS_SDA` |
-| 7 | `B1` | `CHG_SYS_SCL` |
-| 8 | `VCCB` | **`VBAT_L0`** |
-
-Two details make this the correct implementation of §3 rather than a generic isolator:
-
-- **`VCCB` is `VBAT_L0`.** The B-side (charger side) of the translator tracks the battery, so `CHG_SYS_SCL`/`SDA` idle at V<sub>BAT</sub> — exactly the condition the IP2315 requires to come up in I²C mode. The A-side tracks `VBUS_L0`, the system logic rail.
-- **`OE` is `PYB_CHG_IIC`**, driven from **M5IOE1 `PYG11_PWM3`** (`U17` pin 10/11, sheet 4). **[SCH]** Deasserting `OE` removes the charger from the bus entirely.
-
-**The firmware side.** `M5Unified/src/utility/Power_Class.cpp` implements exactly this: the charger is connected via IOE1 `gpio11` only for the duration of a transaction, with a **64-attempt** scan loop waiting for `0x75` to appear (`:88–96`), then disconnected again (`:2399`, `:2724`). **[SRC]**
-
-> ⚠ **Callers that talk to the IP2315 without going through `set_papermono_ip2315_enabled()` will simply not find anything at `0x75`.** That is not a bug; it is the design.
-
-**Vendor operating rule, verbatim [DOC]:**
-
-> *"M5IOE1 controls the connection between the IP2315 and the system I2C bus via PYG11_PWM3: during device operation, do not keep the IP2315 mounted on the I2C bus for extended periods; disconnect it promptly after communication to avoid reducing bus communication stability. If an I2C bus communication anomaly occurs, you can reset the device by briefly pressing the power button to restore normal bus operation."*
-
-The suggested recovery — a short press of the power button — works because that is an [M5PM1](../../m5stack/m5pm1/README.md) reset input, and cycling the rails re-runs the IP2315's power-up mode detection. **[INF]**
-
-**Documentation gap.** M5Stack's dedicated power-management page (`/en/arduino/papermono/m5pm1_m5ioe1`) lists the M5IOE1 pins but **omits `M5IOE1_PIN_11` entirely** — the one pin with a published bus-stability hazard. The warning exists only on the two product pages. A developer working from the power-management tutorial alone would not know the gate exists.
-
----
-
-## 6. Drivers and libraries
-
-| Option | Notes |
-|---|---|
-| **`M5Unified` `Power_Class`** | The only published driver for this part that we found. Handles the bus gating; PaperMono-specific. See `M5Unified/src/utility/Power_Class.cpp` |
-| Linux / Zephyr | **No mainline driver exists for the IP2315.** Injoinic parts are not represented in either tree (checked 2026-09-01) |
-| Roll your own | Feasible — the register map is in the datasheet §I2C onward — but you must implement the NACK-on-last-byte rule (§3.1) and read–modify–write discipline yourself |
-
----
-
-## 7. Integration pitfalls, in priority order
-
-1. **NACK the last byte of every read.** Failing to do so can hold the bus (§3.1). If your I²C driver's "read N bytes" helper ACKs everything, this part will eventually wedge the bus.
-2. **Do not leave it on a shared bus.** Either give it a private bus or gate it, as the PaperMono does (§5).
-3. **A flat battery can prevent I²C mode entirely** (§3), because mode selection depends on the pins being pulled to V<sub>BAT</sub>. Expect enumeration failures on a deeply discharged pack, and do not treat "charger not found" as a fatal error.
-4. **Read–modify–write only.** Reserved bits must be preserved (§3.1).
-5. **`NTC` must not float** — 51 kΩ to GND if unused (§2.2).
-6. **`ICHGSET` sets the *input* current, not the battery current** (§2.1). Getting this backwards over-dimensions the charge rate.
-7. **`VSET` shares a pin with `LED3`.** A design that wants three status LEDs cannot also strap the float voltage on that pin.
-8. **The 7-bit address is 0x75**, from the datasheet's 8-bit `0xEA` (§1).
-
----
-
-## 8. Alternatives
-
-| Part | vs. IP2315 | When to prefer it |
-|---|---|---|
-| **IP2312 / IP2308 / IP2326** (Injoinic) | Same family, differing input-protocol support and current | Cost/feature trims within the same ecosystem |
-| **[TI BQ25895](../../texas-instruments/bq25895/README.md)** | 5 A charger with integrated ADC telemetry and 3.1 A boost, **dedicated I²C pins**, fully public register map at `0x6A` | When you need telemetry, OTG boost, or an I²C port that is not shared with an LED driver. Documented in this repository |
-| **[TI BQ25306](../../texas-instruments/bq25306/README.md)** | Much simpler, no boost, no ADC | Charging and nothing else. Documented in this repository |
-| **[SG Micro SGM40567](../../sgmicro/sgm40567/README.md)** | Linear charger, resistor-programmed | Low current, no switching noise, no bus at all |
-
-The IP2315's distinguishing feature is **input fast-charge protocol negotiation in the charger itself** — no separate PD sink controller. On the PaperMono that feature is depopulated (§4.1), which makes the part choice look like commonality with other M5Stack products rather than a requirement of this board. **[INF]**
-
----
-
-## 9. Open questions
-
-- Which of `R17` (15 kΩ) / `R18` (NC) is the `ICHGSET` resistor, and therefore what the configured input current actually is (§4.2).
-- What `VSET` is strapped to, and hence the float voltage — the `LED3` network shares the pin with a fitted indicator LED, which the datasheet does not show combined with a `VSET` strap.
-- Whether the depopulated CC resistors are a cost decision or a deliberate safety choice given the 5.95 V OVP.
-- No English-language IP2315 datasheet was found; the only copy obtained is Chinese V1.0 (§10).
-- No hardware measurement of charge current, efficiency or bus behaviour.
-
----
-
-## Manufacturer
-
-**Injoinic Technology (英集芯), Shenzhen.** No vendor sourcing guide exists in this repository yet.
-
-Sourcing notes gathered this session, worth recording because they cost time:
-
-- `https://www.injoinic.com/` is **intermittently unreachable**. Three of four attempts on 2026-09-01 timed out at 25–40 s; one returned a 2 642-byte redirect shell. Do not conclude the site is dead on a single timeout.
-- `datasheet.lcsc.com` and `www.lcsc.com/datasheet/...` return **HTTP 200 with `text/html`** for this part's PDF URL — an interstitial, not the document. `https://www.lcsc.com/datasheet/lcsc_datasheet_2402211727_INJOINIC-IP2315_C2764357.pdf` returned 47 427 bytes of HTML. **Always check for the `%PDF` magic bytes, never the status code.**
-- The copy that worked is a **Radxa mirror**: `https://dl.radxa.com/rock3/docs/hw/datasheet/IP2315-datasheet-cn-V1.0.pdf`, served as `application/pdf`, `%PDF` verified.
-
-## Related pages
-
-- [Awinic AW39112DNR](../../awinic/aw39112/README.md) — the level translator that gates this chip on and off the shared bus
-- [Awinic AW32901FCR](../../awinic/aw32901/README.md) — the input OVP switch upstream of `VIN`
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — drives `PYB_CHG_IIC`, the gate's `OE`
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — owns the rails and the power button used to recover a wedged bus
-- [Generic charger / power-path record](../../generic/charger-power-path/README.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | IP2315 数据手册 (datasheet, Chinese) | Injoinic Corp. | primary (via credible mirror) | datasheet | <https://dl.radxa.com/rock3/docs/hw/datasheet/IP2315-datasheet-cn-V1.0.pdf> | 2026-09-01 | **V1.0**, © 2018, 16 pp, 1 217 455 B | Pin table, I²C address `0xEA`/`0xEB`, LED/SCL/SDA multiplexing, VBAT pull-up requirement, NACK bus-lockup warning, `ICHGSET`/`NTC` tables, QFN32 package | `artifacts/ip2315-datasheet-v1.0-cn-radxa-mirror.pdf` |
-| D2 | PaperMono product page (charger hazard note) | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | The `PYG11_PWM3` gating rule and the bus-stability warning, verbatim | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono.html` |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | linked from D2 | 2026-09-01 | V0.6.2, 2026-05-22, 6 sheets | Every net and value in §4 and §5 | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | `M5Unified/src/utility/Power_Class.cpp` | M5Stack | primary | repository | <https://github.com/m5stack/M5Unified> | 2026-09-01 | `master` @ `8530f537…`, MIT | The 64-attempt scan loop, connect/disconnect discipline, address `0x75` | `scratch/m5stack-papermono/repos/M5Unified/` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/ip2315-datasheet-v1.0-cn-radxa-mirror.pdf` | 1 217 455 | `412742b36aa816722cc2830420bf660faf214c84acec60f9763ab3ea782951e1` | 16 |
-
-**Method note.** D1 was fetched with `curl` and a Chrome 131 User-Agent, validated as `%PDF` (16 pages), and read via `pdftotext`. LCSC's PDF host was tried first and rejected for serving HTML under a `.pdf` URL with HTTP 200 — see [Manufacturer](#manufacturer).
diff --git a/components/injoinic/ip2315/artifacts/ip2315-datasheet-v1.0-cn-radxa-mirror.pdf b/components/injoinic/ip2315/artifacts/ip2315-datasheet-v1.0-cn-radxa-mirror.pdf
deleted file mode 100644
index ad9a56b..0000000
Binary files a/components/injoinic/ip2315/artifacts/ip2315-datasheet-v1.0-cn-radxa-mirror.pdf and /dev/null differ
diff --git a/components/joulwatt/jw5712/README.md b/components/joulwatt/jw5712/README.md
deleted file mode 100644
index bb8498b..0000000
--- a/components/joulwatt/jw5712/README.md
+++ /dev/null
@@ -1,294 +0,0 @@
-# Joulwatt JW5712
-
-> **Ultra-low-quiescent-current synchronous step-down (buck) converter** — 600 mA continuous, 800 mA peak, from a 2.3–5.5 V input, with a typical quiescent current of **360 nA** and eight resistor-free output voltages selected by three `VSEL` strap pins.
-> Research snapshot **2026-09-01**. Fitted as **`U10`** on sheet 2 of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), where it produces **`3V3_L2`** — the main system rail that carries the ESP32-S3. **No hardware was available.**
-
-> ⚠ **The publicly served datasheet is a 4-page, image-only scan with no text layer.** Most of the parametric data below therefore comes from Joulwatt's own **product database API**, which is a primary vendor source but not a datasheet. See [§8](#8-datasheet-status--read-this-before-relying-on-a-number-here).
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Joulwatt `JW5712_JW5712A_Datasheet.pdf` — local copy `artifacts/jw5712-jw5712a-datasheet-scanned.pdf`. **Image-only, 4 pages** | `not-tested`; content not machine-readable |
-| **[VDB]** | Joulwatt product database, `https://www.joulwatt.com/jwt/web/product/list`, record `id 9661` / `plmProductId 212` | `executed-success` for the retrieval; vendor claim otherwise `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`JW5712`** (sibling: `JW5712A`) | **[SCH]** sheet 2, `U10`; **[VDB]** |
-| Manufacturer | **Joulwatt Technology** (杭州杰华特微电子 / Joulwatt Microelectronics) | **[VDB]** |
-| Marketing description | *"Ultra-Low Quiescent Current Synchronous Step-Down Converter"* | **[VDB]** `titleEn` |
-| Vendor category | Power management → *"low iq"* (`categoryCode` `PF23101001`) | **[VDB]** |
-| Package | **WLCSP-8**, **1.6 mm × 0.9 mm** (parametric table: `WLCSP 1.575 × 0.875 - 8`) | **[VDB]** |
-| Product status | **Active** (`productStatus: "Active"`, `validFlag: "Y"`) | **[VDB]** |
-| Evaluation board | JW5712 EVM — 2.3–5.5 V in, 1.2 V out @ 0.6 A | **[VDB]** `demoSubtitleEn` |
-
----
-
-## 2. Key parameters **[VDB]**
-
-Taken from the vendor's own parametric record (`cols` field) and feature list. **These are vendor claims, `not-tested`.**
-
-| Parameter | Value |
-|---|---|
-| Channels | 1 |
-| Input voltage | **2.3 V – 5.5 V** |
-| Output current | **600 mA continuous, 800 mA peak** |
-| Output voltage range (JW5712) | **1.2 V – 3.3 V**, **8 selectable values** |
-| Number of `VSEL` pins | **3** (2³ = 8 codes) |
-| Quiescent current | **360 nA typical** |
-| Switching frequency | 1200 kHz (parametric field `Data_07`) |
-| Control architecture | **COT** (constant on-time) with **PFM** light-load mode |
-| Compensation | Internal |
-| Efficiency | **up to 90 % with load current > 15 µA** |
-| 100 % duty-cycle mode | **Automatic** when V<sub>IN</sub> approaches V<sub>OUT</sub> — the high-side FET is held on and switching stops |
-| Output discharge | Yes |
-| Protections | output short-circuit, thermal |
-| Intended sources | one rechargeable Li-ion cell, Li-primary chemistries (Li-MnO₂), or two to three alkaline cells |
-
-**The 360 nA quiescent current is why this part is on this board.** A rail that stays up through `L2 DeepSleep` costs whatever its regulator burns doing nothing; at 360 nA that is roughly 0.003 mAh per day, i.e. nothing against a 1150 mAh pack. **[INF]**
-
-The "up to 90 % efficiency with load current > 15 µA" claim is the same point from the other side — the PFM/COT architecture keeps efficiency up across four or five decades of load, which a fixed-frequency PWM buck does not.
-
----
-
-## 3. Pinout as fitted **[SCH sheet 2, `U10`]**
-
-The datasheet's own pin table could not be read (§8), so this table is recovered from the schematic symbol's pin names, which Altium renders as text.
-
-| Ball | Name | Net on PaperMono |
-|---|---|---|
-| **A1** | `SW` | → **`L2` = `FTC201610S2R2MBCA`, 2.2 µH** → `3V3_L2` |
-| **A2** | `VIN` | **`VBUS_L0`** |
-| **B1** | `EN` | **`3V3_L2_EN`** — from [M5PM1](../../m5stack/m5pm1/README.md) `U7` pin 14, `DCDC3V3_EN_PP`; `R28` = **1 MΩ/1 %** pull-down |
-| **B2** | `GND` | `GND` |
-| **C1** | `VSEL1` | GND |
-| **C2** | `VOS` | output sense, on `3V3_L2` |
-| **D1** | `VSEL2` | GND |
-| **D2** | `VSEL3` | GND |
-
-> ⚠ **The `VSEL` strapping is reported as "all three to GND", and the code-to-voltage mapping is unknown.** The three `VSEL` pins each sit adjacent to a `GND` label in the extracted text layer, and the produced rail is unambiguously **3.3 V** (net `3V3_L2`, and the downstream ESP32-S3 requires it). But the datasheet's `VSEL` truth table is in the unreadable scan (§8), so **whether `000` selects 3.3 V or 1.2 V cannot be confirmed from any source retrieved here.** This is recorded as unresolved rather than guessed; if you are copying this design, read the strapping off the rendered sheet and the truth table off a legible datasheet.
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`U10`**, schematic sheet 2, in the block labelled `L2_SW`.
-
-**`3V3_L2` is the busiest rail on the board.** Sheet 1's power-state table defines it as present in **L2 DeepSleep, L3A CORE ACTIVE and L3B All ACTIVE** — i.e. everything except `L0 Shipping` and `L1 Standby` — and it is enabled by the M5PM1's `DCDC3V3_EN_PP`, exposed to firmware as `pm1.setDcdcEnable(bool)`.
-
-M5Stack's own description of the level: *"L2 / L3A: ESP32-S3, LoRa, NFC/RFID, M5IOE1, user-button pull-up, touch INT, buzzer, RGB red"*, with the distinction that *"When the ESP32-S3 is sleeping, the power system is at level L2. When the ESP32-S3 is operating, it is at level L3A."* L2 and L3A are **states, not separate rails.**
-
-Loads traced to `3V3_L2` from the schematic **[SCH]**:
-
-| Load | Where |
-|---|---|
-| **ESP32-S3R8** `VDD3P3`, `VDD3P3_CPU`, `VDD3P3_RTC`, `VDDA` | sheet 3, `U12` |
-| **M5IOE1** `VCC` | sheet 4, `U17` pin 6 |
-| **BMI270** `VDDIO` region / I²C pull-ups `R36`, `R37` (2.2 kΩ) | sheets 3–4 |
-| **[AW9967DNR](../../awinic/aw9967/README.md)** frontlight boost `VIN` | sheet 2, `U11` |
-| **[AW35122FDR](../../awinic/aw35122/README.md) `U8`** → `TF_3V3_L3B` (microSD) | sheet 2 |
-| **[AW35122FDR](../../awinic/aw35122/README.md) `U18`** → `TP_VDD` (touch) | sheet 4 |
-| **[AW35122FDR](../../awinic/aw35122/README.md) `U21`** → `PDM_VDD` (microphone) | sheet 4 |
-| **Load switch `U1` (sheet 6)** → `VCC_3V3` (NFC sub-board) | sheet 6 |
-| **[AW39112DNR](../../awinic/aw39112/README.md) `U19`** `VCCB` (touch bus translator) | sheet 4 |
-| KEY1 / KEY2 pull-ups `R2`, `R5` (10 kΩ) | sheet 5 |
-| Buzzer drive network | sheet 4 |
-
-Rails that are **not** on `3V3_L2`, which is worth stating because it changes the budget: `3V3_L0`, `3V3_L1`, `3V3_L2_LoRa` and `EPD_3V3_L3B` are each produced by their own [SSP7615-33DFR](../../generic/ssp7615-33dfr/README.md) LDO **directly from `VBUS_L0`**, not from this DC-DC. Sheet 1's block diagram is explicit that the L1/L2/L3 switches all take their input from L0 rather than cascading.
-
-#### 4.1 ⚠ 600 mA is not a generous budget for this rail
-
-**[INF]** — an arithmetic observation, not a measurement:
-
-| Load | Rough worst case at 3.3 V |
-|---|---|
-| ESP32-S3 Wi-Fi TX peak | ~350 mA |
-| microSD write burst | ~100 mA |
-| Frontlight boost at full brightness (~11 mA × ~15 V ÷ 3.3 V ÷ 0.85) | ~55 mA |
-| NFC sub-board active | tens of mA |
-| Touch, microphone, expander, pull-ups | ~10 mA |
-
-Simultaneous worst case plausibly approaches the **600 mA continuous / 800 mA peak** rating. The design is not obviously under-specified — Wi-Fi TX peaks are short and the 800 mA peak rating exists for exactly this — but **a firmware that writes to the SD card during a Wi-Fi transmission with the frontlight at maximum is operating near the converter's limit**, and the symptom of exceeding it would be a `3V3_L2` sag that browns out the ESP32-S3 rather than any error message. Anyone chasing unexplained resets on this board should measure `3V3_L2` under that combination before looking anywhere else.
-
-No hardware measurement was possible; the figures above are typical-part estimates, not this board's measured draw.
-
-#### 4.2 The 100 % duty-cycle mode matters for a Li-ion board
-
-`VBUS_L0` is joined to `VBAT_L0` through a 0 Ω link (`R20`) **[SCH]**, so the buck's input *is* the battery. A single Li-ion cell falls to ~3.3 V well before it is empty, at which point a 3.3 V buck has no headroom. The JW5712's automatic transition to 100 % duty — high-side FET held on, switching stopped — is what keeps `3V3_L2` alive (as `V_BAT` minus the FET drop) down to the pack's cut-off instead of dropping out at 3.4 V. **[VDB]**, **[INF]** for the board-level consequence.
-
-The practical implication: **below roughly 3.4 V pack voltage, `3V3_L2` is no longer regulated 3.3 V** — it tracks the battery. Anything on that rail that cares about supply accuracy (the ADC references in the ESP32-S3, for instance) sees a moving target near end of charge.
-
----
-
-### `devices/m5stack/cap-lora-1262` · *added 2026-09-04*
-
-→ [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md), designator **`U3`**, single-sheet schematic V1.1 (2025-10-29).
-
-5 V (from the Cardputer-Adv's EXT connector) → **3.3 V**, with the annotation **`IOUT: 0~0.6A`** printed beside the symbol. Inductor `L2` = `WPN201610U2R2MT` (2.2 µH). Input `C1` 1 nF + `C2`/`C3`/`C4` 22 µF; output `C15` 22 µF, `C12` 470 µF, `C16`/`C17` 100 nF.
-
-Package pin names as drawn — **a chip-scale/BGA-style map, not the PaperMono's**: `SW` A1, `VIN` A2, `ENB` B1, `GND` B2, `VSEL1` C1, `VOS` C2, `VSEL2` D1, `VSEL3` D2. Three `VSEL` straps are brought out, which is how the output voltage is selected.
-
-**`ENB` has no host connection.** `R1` = **10 kΩ** sits between the `+5V`/`+5VOUT` labels and the enable pin, so the rail comes up with the host's 5 V and stays up. ⚠ The net was **not traced end-to-end** from the PDF text layer — "always on" is `inferred` from that adjacency plus the absence of any enable signal on the 14-pin Cap-Bus.
-
-Loads: the `Stamp LoRa-1262 Mini` module, the `ATGM336H-6N` GNSS (digital `VCC` and `VCC_RF` through separate 120 Ω/MB ferrites), the always-on `MAX2659` GNSS LNA, and the `PI4IOE5V6408` expander.
-
-### `devices/m5stack/cap-cc1101` · *added 2026-09-04*
-
-→ [M5Stack Cap CC1101 & NFC (U219)](../../../devices/m5stack/cap-cc1101/README.md), designator **`U1`**, sheet 1 of schematic V0.3 (2026-05-28).
-
-Same part, same `IOUT: 0~0.6A` annotation, inductor `L1` = `MWTC201608S2R2` (2.2 µH), input `C1` 1 nF + `C2`/`C3`/`C4` 22 µF, output `C5` 22 µF + `C6` 100 nF.
-
-**The difference that matters: here `ENB` *is* host-controlled.** Board net **`POWER_EN`** arrives on **Cap-Bus pin 8** from host **G3** and drives the enable, with `R1` = **100 kΩ** in the network. That is how the board reaches its published **140.87 µA @ 5 V** sleep figure — the host can switch the entire Cap off, rather than relying on the CC1101 and ST25R3916 low-power modes.
-
-⚠ `R1`'s polarity was **not traced**, so whether the Cap defaults on (pull-up) or off (pull-down) is unestablished. The signal is *named* `POWER_EN`, which conventionally implies active-high; bring-up code should drive G3 **high and wait** rather than assume.
-
-> **Design note worth carrying:** the *same* regulator, on two boards from the same vendor, in the same product family, on the same connector — with **Cap-Bus pin 8 meaning `LoRa_RST` on one and `POWER_EN` on the other**. Any firmware that auto-detects which Cap is fitted must not assume pin-8 semantics.
-
-### M5Stack Stamp-S3A (`S007-V033`) — and every board carrying it
-
-Designator **U4** on `Sch_StampS3_v0.3.3.pdf`, producing **`VDD_3V3`** from `VIN_5V`.
-Sheet annotation: **`IOUT: 0~0.6A`**. Output selected by the **`VSEL1`/`VSEL2`/`VSEL3`** straps
-(all three tied to `VIN_5V` through the C1/D1/D2 net) — **no feedback divider**, and `VOS` is a
-remote-sense pin, not a divider tap. External inductor **`L4` = `MWTC201608S2R2`** (2.2 µH,
-2016-metric) on `SW`; `EN` from an R16 100 kΩ network; support caps C15 1 nF, C16 10 µF,
-C18 100 nF, C21/C22/C25 10 µF.
-
-Replaces the **Murata [`MUN3CAD01-SC`](../../murata/mun3cad01-sc/README.md)** µPOL module used on
-the StampS3 v0.2, which set its output with an R16 100 k / R17 22.1 k divider that the JW5712
-design deletes.
-
-Boards: [Cardputer v1.1](../../../devices/m5stack/cardputer-v1.1/README.md),
-[Cardputer ADV](../../../devices/m5stack/cardputer-adv/README.md),
-[Cardputer Mesh Kit](../../../devices/m5stack/cardputer-mesh-kit/README.md).
-
-> **Provenance note.** `components/unidentified/m5stack-stamp-s3a/dcdc-u4/` was created on
-> 2026-09-04 recording this same `U4` as "part number not established". The label **is** present
-> on the sheet — see §0 of `scratch/m5stack-cardputer/index-fragments.md` for the verifying crop
-> and hashes. That directory should be retired in favour of this record.
->
-> ⚠ **Retiring it would edit another session's record, so it has not been done.** The conflict is
-> parked for review in
-> [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.5.*
-
-## 5. Drivers and libraries
-
-**Not applicable at the component level** — no bus interface. On the PaperMono the only control is the enable line, owned by the M5PM1:
-
-```cpp
-pm1.setDcdcEnable(true);    // 3V3_L2_EN -> JW5712 EN  (this rail)
-pm1.setLdoEnable(true);     // 3V3_L1_EN -> the SSP7615 LDO feeding the IMU
-```
-
-> ⚠ **Calling `pm1.setDcdcEnable(false)` powers off the ESP32-S3 that is making the call.** It is a one-way trip; recovery is a power-button press or an M5PM1 wake source. **[INF]**
-
----
-
-## 6. Integration pitfalls
-
-1. **`VSEL` strapping is silent.** Three pins, eight voltages, no readback, no error. Mis-strapping produces a wrong but perfectly stable rail. Verify against a legible truth table (§3, §8).
-2. **`EN` needs its pull-down.** `R28` = 1 MΩ on this board. Without it the rail state at power-up is whatever the enable driver's high-Z leakage decides.
-3. **Below ~3.4 V input the output stops regulating** (§4.2). This is a feature, but it changes the rail's specification at end of discharge.
-4. **Peak versus continuous** — 800 mA peak is not a duty-cycle-free rating (§4.1).
-5. **Output discharge is active.** Disabling the rail actively pulls it down; do not rely on a slow decay for orderly shutdown of downstream logic.
-
----
-
-## 7. Alternatives
-
-| Part | vs. JW5712 | When |
-|---|---|---|
-| **JW5712A** | Same family, same package and description; the vendor lists them as one datasheet | Second option within the family; the difference was not established (§9) |
-| TI **TPS62840** | 750 mA buck, **60 nA** I<sub>Q</sub>, very well documented | When quiescent current is the whole design and you want a legible datasheet |
-| TI **TPS62203** / **TLV62569** | Higher current, ordinary I<sub>Q</sub> | When the rail never sleeps |
-| **[SGM6029](../../sgmicro/sgm6029/README.md)** | Buck-boost, 3.3 V / 600 mA | When you need to hold 3.3 V *below* 3.3 V input rather than dropping into 100 % duty. Documented in this repository |
-| **[SSP7615-33DFR](../../generic/ssp7615-33dfr/README.md)** LDO | 400 mA, 0.5 µA I<sub>Q</sub>, no inductor | Lower-current rails — which is exactly how the PaperMono uses it for `3V3_L0`, `3V3_L1`, `3V3_L2_LoRa` and `EPD_3V3_L3B` |
-
-The interesting comparison is the last one: this board fits **one** buck and **four** LDOs. The buck goes where the current is (the ESP32-S3), and the LDOs go where the current is small and the noise matters or the cost of an inductor is not worth it. **[INF]**
-
----
-
-## 8. Datasheet status — read this before relying on a number here
-
-**A datasheet was obtained, and it is largely unusable.**
-
-| Property | Value |
-|---|---|
-| URL | `https://www.joulwatt.com/jwt/profile/ProductFile/规格书/JW5712_JW5712A_Datasheet.pdf` |
-| HTTP | 200, `application/pdf`, `%PDF` verified |
-| Size | 2 547 415 B |
-| SHA-256 | `077d56d71d5b5c921499f26b4254ec4cc5a3c4b5809ca8ef2ca2dc5b81d9dba2` |
-| **Pages** | **4** |
-| **Text layer** | **None.** `pdftotext` returns zero characters |
-| Content | 4 × full-page RGB images, 2479 × 3507 px at 300 dpi — a scan or a rasterised export |
-
-A separate `..._FirstPage.pdf` (1 page, 2 546 640 B) is also served and is the same material.
-
-**Consequences, stated plainly:**
-
-- The `VSEL` truth table, the full pin description, the absolute maximum ratings and the electrical characteristics table are **not available in machine-readable form** and were **not** transcribed here, because doing so from an unreadable scan would be guessing.
-- Everything in §2 comes from **[VDB]**, Joulwatt's product-database API. That is a primary vendor source and it is internally detailed (it carries the parametric `cols` record, the bilingual feature list and the EVM description), but **it is not a datasheet** and carries no absolute maximum ratings.
-- A four-page datasheet is in any case an abridgement. Joulwatt may publish a full version to registered customers; that was not pursued.
-
-**How the file was found**, recorded because the path is not discoverable from the site UI:
-
-1. `https://www.joulwatt.com/assets/js/request.js` reveals the API base `https://www.joulwatt.com/jwt/web/`.
-2. `POST`/`GET` `https://www.joulwatt.com/jwt/web/product/list?pageSize=3000` returns all 1 564 products as JSON, including `datesheetFileSite` per part.
-3. That relative path resolves under `https://www.joulwatt.com/jwt/profile/`.
-
-`http://www.joulwatt.com/` timed out on first contact; `https://` worked. Plain `curl` with a Chrome 131 User-Agent throughout; no fallback User-Agent required, no login.
-
----
-
-## 9. Open questions
-
-- **The `VSEL` truth table.** Which of the eight codes produces 3.3 V, and therefore whether the PaperMono's strapping is what it appears to be (§3).
-- **Absolute maximum ratings** — not available from any source retrieved (§8).
-- **What distinguishes JW5712 from JW5712A.** The vendor gives both the same description, package and feature list; the parametric records differ only in the part name field. **[VDB]**
-- Whether a full-length JW5712 datasheet exists publicly.
-- No hardware measurement of `3V3_L2` under load, and no verification of the §4.1 budget concern.
-
----
-
-## Manufacturer
-
-**Joulwatt Technology** (杰华特微电子). No vendor sourcing guide exists in this repository yet. The retrieval recipe in §8 is the reusable part; the two facts worth carrying forward to any future Joulwatt part are:
-
-- **The product database is public and complete** — `GET https://www.joulwatt.com/jwt/web/product/list?pageSize=3000` returns every product with descriptions, features, parametric data and datasheet paths, in one 4.4 MB JSON response.
-- **Datasheet files live under `/jwt/profile/` + the `datesheetFileSite` value**, and the path contains Chinese characters (`规格书`) that must be percent-encoded.
-
-## Related pages
-
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — owns `3V3_L2_EN`
-- [SSP7615-33DFR](../../generic/ssp7615-33dfr/README.md) — the LDOs producing the other four rails
-- [Espressif ESP32-S3R8](../../espressif/esp32-s3r8/README.md) — the dominant load on this rail
-- [Awinic AW9967DNR](../../awinic/aw9967/README.md) — frontlight boost, powered from this rail
-- [Awinic AW35122](../../awinic/aw35122/README.md) — the three load switches downstream of this rail
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | JW5712 / JW5712A datasheet | Joulwatt | primary | datasheet | <https://www.joulwatt.com/jwt/profile/ProductFile/%E8%A7%84%E6%A0%BC%E4%B9%A6/JW5712_JW5712A_Datasheet.pdf> | 2026-09-01 | undated; 4 pp, **image-only**, 2 547 415 B | Existence and identity only — no machine-readable content (§8) | `artifacts/jw5712-jw5712a-datasheet-scanned.pdf` |
-| D2 | Joulwatt product database, record `id 9661` | Joulwatt | primary | API | <https://www.joulwatt.com/jwt/web/product/list> | 2026-09-01 | live | Every parameter in §2: input range, 600/800 mA, 360 nA I<sub>Q</sub>, 8 output voltages via 3 `VSEL` pins, WLCSP-8 1.6 × 0.9 mm, COT/PFM, 100 % duty behaviour, Active status | not vendored (4.4 MB full listing) |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `U10` ball/net table, `L2` = 2.2 µH, `R28` = 1 MΩ, `3V3_L2_EN` ← M5PM1 pin 14, every load in §4 | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | PaperMono M5PM1/M5IOE1 power-management page | M5Stack | primary | official page | <https://docs.m5stack.com/en/arduino/papermono/m5pm1_m5ioe1> | 2026-09-01 | — | The L0–L3B level definitions and `setDcdcEnable()` | `scratch/m5stack-papermono/docs/pages/en-arduino-papermono-m5pm1_m5ioe1.html` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages | Text layer |
-|---|---:|---|---:|---|
-| `artifacts/jw5712-jw5712a-datasheet-scanned.pdf` | 2 547 415 | `077d56d71d5b5c921499f26b4254ec4cc5a3c4b5809ca8ef2ca2dc5b81d9dba2` | 4 | **none** |
-
-**Method note.** D1 was validated as `%PDF` and confirmed image-only with `pdfimages -list` (4 × 2479 × 3507 RGB, 300 dpi). It is retained despite being unreadable because it is the vendor's own file and a future reader with OCR can extract what this pass could not — and because recording *that it is a scan* is itself the finding that stops the next agent repeating the search.
diff --git a/components/joulwatt/jw5712/artifacts/jw5712-jw5712a-datasheet-scanned.pdf b/components/joulwatt/jw5712/artifacts/jw5712-jw5712a-datasheet-scanned.pdf
deleted file mode 100644
index 0495875..0000000
Binary files a/components/joulwatt/jw5712/artifacts/jw5712-jw5712a-datasheet-scanned.pdf and /dev/null differ
diff --git a/components/knowles/spm1423hm4h-b/README.md b/components/knowles/spm1423hm4h-b/README.md
deleted file mode 100644
index bc1f866..0000000
--- a/components/knowles/spm1423hm4h-b/README.md
+++ /dev/null
@@ -1,97 +0,0 @@
-# Knowles SPM1423HM4H-B — PDM MEMS microphone
-
-> The microphone on the **Cardputer v1.0 and v1.1** (and on several other M5Stack products).
-> Record created **2026-09-04**. Manufacturer: **Knowles Electronics** (the SPM/SPH prefix is
-> Knowles' MEMS microphone family). M5Stack mirrors an English datasheet — see *Artifacts*.
-
-## Function
-
-A **PDM (pulse-density modulation) digital output** MEMS microphone. It takes a clock in and
-returns a 1-bit oversampled bitstream — no codec required, and no analog signal on the board.
-The host decimates the bitstream in software or in an I²S/PDM peripheral.
-
-This is the cheap, simple way to put a microphone on a microcontroller, and it is what the first
-two Cardputers do.
-
-## Key capabilities
-
-| Property | Value | Evidence |
-|---|---|---|
-| Output | **PDM**, 1-bit | part family; board wiring |
-| Interface | `CLK` in, `DAT` out, plus `VCC`/`GND` — **four pins** | M5Stack PinMap |
-| Supply | **3.3 V** on the Cardputer | PinMap: `VCC` = 3.3 V |
-| Channel select | typically an `L/R` pin or strap; **not brought out on the Cardputer** | schematic |
-| Sensitivity, SNR, AOP | in the datasheet; **not transcribed** in this pass | — |
-
-## Pinout as used
-
-| Signal | Cardputer v1.0 / v1.1 |
-|---|---|
-| `DAT` | **G46** |
-| `CLK` | **G43** |
-| `VCC` | 3.3 V |
-| `GND` | GND |
-
-Straight from the M5Stack PinMap table ("SPM1423 MIC"), and corroborated by
-[`M5Unified`](https://github.com/m5stack/M5Unified/blob/8530f5377d782e4a25a6c482de2e71c3f75ca8eb/src/M5Unified.cpp#L2664-L2670):
-
-```cpp
-case board_t::board_M5Cardputer:
-  if (cfg.internal_mic) { mic_cfg.pin_data_in = GPIO_NUM_46;
-                          mic_cfg.pin_ws      = GPIO_NUM_43; }
-  break;
-```
-
-⚠ **Note what is absent: `pin_bck` is not set.** A PDM microphone needs a clock and a data line,
-not a full I²S frame. The ADV's row in the same table *does* set `pin_bck = GPIO_NUM_41`, because
-the ADV's microphone path goes through an I²S codec instead. That one missing line is a compact
-way to see the generational difference.
-
-## Used By
-
-### M5Stack Cardputer v1.0 (K132) and v1.1 (K132-V11)
-
-[`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md)
-
-Designator **M1** on the shared mainboard schematic (SHA-256 `6016c1fe…`), value string
-`SPM1423HM4H-B`. Wired as above.
-
-`CLK` on **G43** is shared with the speaker path's `LRCLK` (the NS4168's `LRCLK` is also G43),
-so the microphone clock and the speaker word-select are the same net. That is workable because
-M5Unified drives one I²S port and only one direction is active at a time, but it means
-**simultaneous full-duplex audio is not available on the v1.x** — a limitation the ADV's codec
-removes.
-
-**Replaced on the Cardputer ADV** by an analog MEMS microphone
-([`memsensing/msm381a3729h9bp`](../../memsensing/msm381a3729h9bp/README.md)) feeding the
-[ES8311](../../everest-semiconductor/es8311/README.md) codec's ADC. That change is what makes the
-ADV's 3.5 mm jack and its recording path possible.
-
-## Artifacts
-
-M5Stack mirrors an English datasheet:
-
-```
-https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/SPM1423HM4H-B_datasheet_en.pdf
-```
-1 272 831 B, SHA-256 `85ecd7d7a42c7853a77a4dbc903606f7da82cf03abd496b75eb526147e1acbb0`,
-retrieved 2026-09-04. **Fetched into scratch, not committed here** — pending a decision, and
-because [`vendors/m5stack`](../../../vendors/m5stack/README.md) §5.5 warns that M5Stack's
-mirrors of third-party datasheets are not necessarily current. Prefer Knowles' own copy and hash
-both; keep the M5Stack mirror labelled as a mirror if it turns out to be the only accessible one.
-
-## Substitutes
-
-| Part | Note |
-|---|---|
-| Any PDM MEMS mic with `CLK`/`DAT`/`VCC`/`GND` | check the channel-select convention and the clock frequency range |
-| **MSM261D3526H1CPM / MSM261D4030H1CPM** | the PDM parts already documented in this repository |
-| **Analog MEMS mic** | **not a drop-in** — needs a codec with an analog input, which is exactly what the ADV added |
-
-## Gaps
-
-* Datasheet **retrieved but not committed and not mined** — sensitivity, SNR, AOP, clock range
-  and channel-select behaviour are not transcribed here.
-* Knowles' own current copy was not located; only M5Stack's mirror.
-* Package marking not verified against a board photograph.
diff --git a/components/lite-on/ltr-553als-01/README.md b/components/lite-on/ltr-553als-01/README.md
deleted file mode 100644
index 9f09da1..0000000
--- a/components/lite-on/ltr-553als-01/README.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Lite-On LTR-553ALS-01
-
-- **Category:** combined **ambient-light sensor and proximity sensor** with an integrated IR
-  LED driver, I²C interface.
-- **Manufacturer:** Lite-On Technology Corporation.
-- **Retrieved:** 2026-09-07
-
-> **This record was created 2026-09-07 to fill a gap.** The directory already held
-> [`artifacts/ltr-553als-01-datasheet.pdf`](artifacts/ltr-553als-01-datasheet.pdf) with **no
-> `README.md` beside it**. The datasheet was **not read** by this pass; nothing below is
-> transcribed from it. A stub, to make the artifact discoverable and record its user.
-
-## 1. Identity
-
-| Property | Value |
-|---|---|
-| Part | **LTR-553ALS-01** |
-| Datasheet | `ltr-553als-01-datasheet.pdf` — acquired by an earlier pass; version and provenance URL not recorded at the time |
-| Interface | I²C |
-| Address | **`0x23`** — from LilyGO's own I²C table for the T-Display-S3 Pro, not from the datasheet |
-
-Related record already here:
-[`generic/ambient-light-and-proximity-sensor-selection`](../../generic/ambient-light-and-proximity-sensor-selection/) *(artifacts only; no record yet)*.
-
-## 2. Used By
-
-### LilyGO T-Display-S3 Pro
-→ [`devices/lilygo/t-display-s3-pro`](../../../devices/lilygo/t-display-s3-pro/README.md)
-
-Ambient-light and proximity sensor at I²C **`0x23`**, on **SDA GPIO5 / SCL GPIO6** — a bus it
-shares with the [CST226SE touch controller](../../hynitron/cst226se/README.md) (`0x5A`), the
-[SY6970 PMIC](../../silergy/sy6970/README.md) (`0x6A`) and the camera. LilyGO's own
-`examples/factory/utilities.h` @ `08b8b2bbcb8b263131af119476403080cd30224f` says so in a
-comment: `// LTR553 , TOUCH , SY6970 , Camera share I2C Bus`.
-
-Vendor example: `examples/LTR553ALS_Sensor`.
-
-**A caution for auto-brightness code on this board.** The Pro ships in two revisions whose
-backlight scales differ by 16× — `BRIGHTNESS_MAX_LEVEL` is **255** on V1.0 and **16** on V1.1,
-selected by an `#ifdef USING_DISPLAY_PRO_V1`. Any closed loop from this sensor to the backlight
-must know which board it is on. See
-[board-revision-drift R6](../../../devices/lilygo/t-display-s3-shared/board-revision-drift.md#r6--t-display-s3-pro-v10-vs-v11-backlight-driver).
-
-## 3. Gaps
-
-Datasheet not read: register map, lux conversion, integration times, proximity configuration
-and electrical limits are unrecorded. The `0x23` address is LilyGO's claim, not independently
-confirmed. Original acquisition URL unknown. Not verified on hardware.
diff --git a/components/lontium/lt9611/README.md b/components/lontium/lt9611/README.md
deleted file mode 100644
index fa93350..0000000
--- a/components/lontium/lt9611/README.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# Lontium LT9611 — MIPI DSI to HDMI 1.4 bridge
-
-- **Category:** display bridge — MIPI DSI input, HDMI/DVI transmitter output
-- **Manufacturer:** **Lontium Semiconductor** (龙迅半导体)
-- **Research status:** **presence on the LilyGO board is not confirmed.** This record documents the part and the evidence for and against it being fitted. Do not read it as an assertion that the board has one.
-- **Retrieved:** 2026-09-04
-
-## 1. Core facts
-
-| Property | Value |
-|---|---|
-| Input | MIPI DSI, up to 4 lanes, up to 2 Gbps/lane |
-| Output | HDMI 1.4, up to **1080p60** (LT9611**UXC** variant goes to 4K30) |
-| Audio | I²S / SPDIF audio embedding into HDMI |
-| Control | I²C |
-| Typical control pins | `RESET`, `INT` |
-
-## 2. Evidence on the LilyGO T-Display K230
-
-**For:**
-- LilyGO's pin map devotes four rows to an "LT9611 HDMI bridge", giving it I²C on `GPIO37`/`GPIO36`,
-  IRQ on `GPIO23` and reset on `GPIO24` — all four **shared with the GT9895 touch controller** (S1).
-- The BSP ships `0055-riscv-dts-add-rm69a10-hdmi-output-dtb.patch` and
-  `0062-riscv-dts-rm69a10-hdmi-use-sdk-v3-baseline.patch`, and the Buildroot config builds a
-  third device tree, `canaan/k230-canmv-rm69a10-hdmi` (S2).
-- The launcher has a dedicated `ui_hdmi_test.c` page.
-- LilyGO's wiki lists **"HDMI 1080P @ 30 FPS"** as a headline feature of both the bare board and
-  the Cased Version (S3).
-- `lt9611` appears 29 times across the LilyGO tree.
-
-**Against / qualifying:**
-- LilyGO's pin map calls it the "**optional** HDMI bridge path" in every row (S1).
-- The main `README.MD` says "**HDMI support is kept as a diagnostic feature.** AMOLED remains the
-  default display path" (S2).
-- **The part is never named in the shop listing** for either the board or the kit.
-- The K230 has exactly **one** MIPI DSI output, which is already driving the RM69A10 AMOLED.
-  An HDMI bridge on the same DSI cannot run simultaneously with the panel; the separate
-  `-hdmi` device tree exists precisely because it is a **boot-time choice**, not a second head.
-
-**Conclusion:** the software supports it, it is a build-time-selected alternative to the AMOLED,
-and whether the bridge IC is populated on a given SKU is **unverified**. Tracked as `GC-4` in
-[gaps-and-conflicts.md](../../../devices/lilygo/t-display-k230/gaps-and-conflicts.md). Settle it
-by `i2cdetect` on the touch bus, or by a photograph of the PCB.
-
-## 3. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04, presence unconfirmed*
-
-If fitted: I²C on `GPIO37` SDA / `GPIO36` SCL, IRQ `GPIO23`, reset `GPIO24` — **the same four
-lines as the GT9895 touch controller**. That sharing is the important integration fact: a reset
-of one resets the other, and both must live at distinct I²C addresses on one bus.
-
-## 4. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | Shared I²C/IRQ/reset with touch; "optional" |
-| S2 | `README.MD`, `0055-…`, `0062-…`, defconfig `BR2_LINUX_KERNEL_INTREE_DTS_NAME` | LILYGO | primary | source | same repo | 2026-09-04 | HDMI as diagnostic feature; separate DTB |
-| S3 | T-Display K230 wiki + Cased Version pages | LILYGO | primary | official wiki | `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/` | 2026-09-04 | "HDMI 1080P @ 30 FPS" |
diff --git a/components/m5stack/m5ioe1/README.md b/components/m5stack/m5ioe1/README.md
deleted file mode 100644
index 9ad05a3..0000000
--- a/components/m5stack/m5ioe1/README.md
+++ /dev/null
@@ -1,360 +0,0 @@
-# M5Stack M5IOE1
-
-- **Category:** custom I²C GPIO expander — 14 GPIOs, 4 × 12-bit ADC, 4 × PWM, NeoPixel driver, die temperature sensor, 32 B retention RAM, open-drain interrupt output
-- **Not an ASIC.** The schematic identifies the underlying silicon as a **Puya `PY32L020F15U6`** Cortex-M0+ MCU — annotated `PY32L020F15U6_IIC` — running M5Stack's own I/O-expander firmware. Everything below is *firmware* behaviour.
-- **I²C address:** **`0x4F`** as fitted on PaperMono — **which is outside the range the V1.4 manual documents.** See §7-C1; this conflict is recorded, not resolved.
-- **Research status:** the **full M5Stack manual is retained** in `artifacts/` (V1.4, 10 pages) and has been read end to end. The pin table is corroborated **pin-for-pin, all 21 pads**, by the PaperMono schematic. No hardware was in the loop.
-- **Retrieved:** 2026-09-01
-
-The I/O expander of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) and its Lite sibling. It owns the `L3B` power domain — display, touch controller, microSD, PDM microphone — plus the LoRa reset/antenna-switch lines, the NFC rail, two of the three RGB LED channels, and the I²C gate that keeps the IP2315 charger off the bus.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | Stated in `artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf`, with page reference | `not-tested` — vendor claim reproduced verbatim; nothing measured |
-| **[SCH]** | Read out of `PaperMono_SCH_V0.6.2_20260522.pdf`, cited as sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | `docs.m5stack.com` product/API page, retrieved 2026-09-01 | `not-tested` |
-| **[FW]** | String recovered from the shipped factory firmware binary | `executed-success` for the extraction |
-| **[INF]** | Inference drawn from two or more of the above | `inferred` |
-
-**Nothing in this record was verified electrically.** No pin, register or address below was guessed.
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketing name | **`M5IOE1`** | **[DS]** cover; **[SCH]** sheet 4 block label next to `U17` |
-| Publisher of the manual | **Shenzhen Mingzhan Information Technology Co., Ltd.** (M5Stack's legal entity) | **[DS]** cover |
-| Document | **M5IOE1 Chip User Manual V 1.4**, 10 pp., dated **2025-11-25** in its own revision table | **[DS]** cover, p. 10 |
-| **Underlying silicon** | **`PY32L020F15U6`** — Puya PY32 series, Cortex-M0+ | **[SCH]** sheet 1, power/IO map block diagram: the legend row `PYB` is annotated **`PY32L020F15U6_IIC`**. The `_IIC` suffix distinguishes the I²C-expander firmware build from the PMIC build on the same die (row `PMIC` → `PY32L020F15U6`) |
-| Nature of the part | A **general-purpose MCU pre-programmed with M5Stack firmware** | **[DS]** §I: "provides fixed IO management, ADC, interrupt and other functions **by burning custom IO function firmware**" |
-| I²C address, per the manual | **`0x6F`–`0x76`**, selected by the voltage on **`IO7` (PA6)** sampled at power-on | **[DS]** §I.2(4), §V.5, Table 6 (p. 9) |
-| I²C address, **as fitted on PaperMono** | **`0x4F`** | **[SRC]** `M5PaperMono-UserDemo/main/hal/hal_board.cpp:14`; **[SRC]** `M5IOE1/src/M5IOE1.h:80` (`M5IOE1_DEFAULT_ADDR_2`); **[SRC]** `M5GFX/src/M5GFX.cpp:213`; **[DOC]** product page PinMap |
-| ⚠ Address conflict | **Unresolved.** `0x4F` does not appear anywhere in the V1.4 manual. See §7-C1 | — |
-| I²C speed | **100 kHz default**, 400 kHz selectable via `I²C_CFG[4] SPD`. PaperMono runs it at **100 kHz** | **[DS]** §I.2(4); **[FW]** `Initializing M5IOE1 with 100KHz (device default)` |
-| Package | **21 pads** on the schematic symbol: 20 signal/power pins per the manual's Table 1, plus **pin 21 = `VSS`** | **[DS]** Table 1 (p. 2) gives pins 1–20; **[SCH]** sheet 4 `U17`.21 = `VSS` |
-| Reference designator on PaperMono | **`U17`**, sheet 4 | **[SCH]** |
-| Identity registers | `UID_L`/`UID_H` (`0x00`/`0x01`) — 16-bit factory-programmed unique ID; `REV` (`0x02`) — firmware major version, default **`A`** (ASCII) | **[DS]** Table 3 p. 4, §IV.1 |
-| ⚠ Marking verified? | **No.** No teardown photograph of `U17` was inspected; the `PY32L020F15U6` identification rests on the schematic's block diagram | **[INF]** |
-
-### 1.1 Same die, two firmwares
-
-The M5IOE1 and the [M5PM1](../m5pm1/README.md) are the **same Puya part with different M5Stack firmware**, which explains a great deal of the two manuals' shared structure — identical section layout, identical publisher, identical wording in §Resource/§Function, an `AW8737A PULSE` register in both, 32 bytes of retention RAM in both, the same "all GPIO outputs default to open-drain" caveat in both.
-
-It also explains the differences that matter:
-
-- The PMIC firmware exposes **5** GPIOs, the expander firmware **14** — because the two builds bond out different numbers of the same die's pins to the same 20-pin footprint.
-- The PMIC has a **fixed** address, the expander a **pin-selected** one.
-- **They number their pins differently** (§6). That is a firmware/API decision, not silicon.
-- Electrical limits are the PY32's, and **neither manual states them** — no supply range, no absolute maximum ratings, no I/O drive strength. Component record pending at `components/puya/py32l020f15u6/`.
-
----
-
-## 2. Pin table
-
-Manual Table 1 and the PaperMono schematic symbol agree on all 20 signal pins, in order. Both naming conventions are given because they differ: the manual says `IOn`, the schematic says `PYGn`.
-
-| Pin | Manual name **[DS]** p. 2 | Manual type | Schematic symbol name **[SCH]** `U17` | PaperMono net **[SCH]** | PaperMono function |
-|---:|---|---|---|---|---|
-| 1 | `NRST` | NRST | `NRST` | `RST` (via `R53`) | Expander reset, **active low** |
-| 2 | `INT_OUT` | Interrupt output | `OD_INTOUT` | `G7_PYB_IRQ` | Interrupt to ESP32-S3 GPIO7 |
-| 3 | `IO14` | GPIO | `PYG14` | `PYB_TF_EN` | microSD power enable |
-| 4 | `VSS` | VSS | `VSS` | `GND` | |
-| 5 | `IO12` | GPIO | `PYG12` | `PYB_PDM_EN` | PDM microphone power enable |
-| 6 | `VCC` | VCC | `VCC` | `3V3_L2` | |
-| 7 | `IO1` | GPIO | `PYG1` | `PYB_TF_DET` | microSD card-detect (active low) |
-| 8 | `SDA` | I²C | `I2C_SDA` | `G47_SYS_SDA` | |
-| 9 | `SCL` | I²C | `I2C_SCL` | `G48_SYS_SCL` | |
-| 10 | `IO11` | GPIO | `PYG11_PWM3` | `PYB_CHG_IIC` | **IP2315 charger I²C bus gate** |
-| 11 | `IO2` | GPIO | `PYG2_ADC1` | `PYB_LoRa_ANT_SW` | SX1262 antenna switch |
-| 12 | `IO8` | GPIO | `PYG8_PWM2` | `PYB_LED_G` | RGB LED green channel |
-| 13 | `IO9` | GPIO | `PYG9_PWM1` | `PYB_LED_B` | RGB LED blue channel |
-| 14 | `IO3` | GPIO | `PYG3` | `PYB_EPD_EN` | **E-paper 3V3 rail enable** |
-| 15 | `IO13` | GPIO | `PYG13` | `PYB_TP_EN` | Touch controller VDD enable |
-| 16 | `IO4` | GPIO | `PYG4_ADC2` | `PYB_NFC_EN` | NFC/RFID power enable |
-| 17 | `IO5` | GPIO | `PYG5_ADC3` | `PYB_EINK_RST` | **E-paper reset** |
-| 18 | `IO6` | GPIO | `PYG6` | `PYB_TP_RST` | Touch controller reset |
-| 19 | `IO7` | GPIO | `PYG7_ADC4` | **`ADD_SET`** | **I²C address select** (see §1, §7-C1) |
-| 20 | `IO10` | GPIO | `PYG10_PWM4` | `PYB_LoRa_RST` | SX1262 `NRST` |
-| 21 | *(not in Table 1)* | — | `VSS` | `GND` | |
-
-The `PYGn` ↔ `IOn` mapping is **exact and independently confirmed 7-for-7** by the suffixes: the schematic's `PYG2_ADC1`, `PYG4_ADC2`, `PYG5_ADC3`, `PYG7_ADC4`, `PYG9_PWM1`, `PYG8_PWM2`, `PYG11_PWM3`, `PYG10_PWM4` match the manual's channel assignments and the library's channel comments without exception **[DS]** Table 2, **[SCH]** `U17`, **[SRC]** `M5IOE1/src/M5IOE1.h`.
-
-Note the pin order is **not** monotonic in `IOn` — the physical sequence is 14, 12, 1, 11, 2, 8, 9, 3, 13, 4, 5, 6, 7, 10. Never infer a pin number from position.
-
-### 2.1 Pin capabilities and mutual exclusions
-
-**[DS]** Table 2, p. 3.
-
-| Pin | MUX | Interrupt exclusion / note |
-|---|---|---|
-| `IO1` | — | Interrupt mutually exclusive with `IO6` |
-| `IO2` | **ADC1** | Excl. with `IO3`; interrupt auto-disabled while ADC is enabled |
-| `IO3` | — | Excl. with `IO2` |
-| `IO4` | **ADC2** | Interrupt auto-disabled while ADC is enabled |
-| `IO5` | **ADC3** | **Interrupt disabled during I²C idle sleep**; also disabled while ADC is enabled |
-| `IO6` | — | Excl. with `IO1` |
-| `IO7` | **ADC4** | Excl. with `IO12`; also the **power-on address-select input** (§1) |
-| `IO8` | **PWM2** | Excl. with `IO9`; interrupt auto-disabled while PWM is enabled |
-| `IO9` | **PWM1** | Excl. with `IO8` |
-| `IO10` | **PWM4** | Excl. with `IO14` |
-| `IO11` | **PWM3** | Excl. with `IO13` |
-| `IO12` | **SWDIO** | Excl. with `IO7`. **SWDIO disabled by default** |
-| `IO13` | **SWCLK** | Excl. with `IO11` |
-| `IO14` | **NeoPixel output** | Excl. with `IO10` |
-| `INT_OUT` | — | **Open-drain; external pull-up required.** Pulled low on interrupt, released after `GPIO_IS` is cleared |
-| `SDA`, `SCL` | — | **Open-drain; external pull-ups required** |
-| `NRST` | — | **Active-low reset** |
-
-Consolidated exclusion groups **[DS]** Table 5, p. 9 — *interrupts* cannot be enabled simultaneously within a pair: `IO1 & IO6` · `IO2 & IO3` · `IO7 & IO12` · `IO8 & IO9` · `IO10 & IO14` · `IO11 & IO13`.
-
-> ⚠ **All GPIO outputs default to open-drain** (`GPIO_DRV_L` = `0xFF`, `GPIO_DRV_H` = `0x3F`), including NeoPixel and PWM. With no external pull-up you must switch the pin to push-pull. **[DS]** Table 2 note 1, Table 3.
->
-> ⚠ **ADC / PWM / I²C / SWD / NeoPixel occupancy overrides the GPIO registers.** When a pin is claimed by a peripheral, `GPIO_M_x` and `GPIO_O_x` become inoperative for that pin. **[DS]** §IV.2(9).
-
----
-
-## 3. I²C address selection
-
-**[DS]** §V.5, Table 6 (p. 9). At power-on the firmware samples `IO7` (die pin PA6) and picks an address from an eight-step voltage ladder:
-
-| Voltage on `IO7` at power-on | I²C address |
-|---|---|
-| **Floating** | **randomly assigned** in `0x6F`–`0x76` |
-| 0 – 412.5 mV | `0x6F` |
-| 412.5 – 825 mV | `0x70` |
-| 825 – 1237.5 mV | `0x71` |
-| 1237.5 – 1650 mV | `0x72` |
-| 1650 – 2062.5 mV | `0x73` |
-| 2062.5 – 2475 mV | `0x74` |
-| 2475 – 2887.5 mV | `0x75` |
-| 2887.5 – 3300 mV | `0x76` |
-
-Manual's own warnings: do not sit on a boundary voltage, and **do not leave `IO7` floating at power-on** or the address is random.
-
-On PaperMono `IO7` is netted `ADD_SET` **[SCH]** `U17`.19 — the mechanism is used as designed — yet the address the firmware and documentation both use is **`0x4F`**, outside this table entirely. §7-C1.
-
----
-
-## 4. Register map
-
-Transcribed from **[DS]** Table 3 (pp. 4–5) and §IV (pp. 5–9). Library symbol names from **[SRC]** `M5IOE1/src/M5IOE1.h`.
-
-Layout convention: every GPIO register is split **`_L` covering P8–P1** in bits `[7:0]` and **`_H` covering P14–P9** in bits `[5:0]`, with `[7:6]` reserved.
-
-> ⚠ **Burst access is range-limited.** I²C sequential read/write works only within the blocks `0x00–0x2F`, `0x30–0x6F`, `0x70–0x8F`, `0x90`. Crossing a boundary requires separate transactions. **[DS]** Table 3 note 2.
-
-| Addr | Register | Access | Default | Function |
-|---|---|---|---|---|
-| `0x00` / `0x01` | `UID_L` / `UID_H` | R | — | 16-bit factory-programmed unique identifier |
-| `0x02` | `REV` | R | `A` | Firmware major version, `SW7–SW0` (ASCII since `SW:A`) |
-| `0x03` / `0x04` | `GPIO_M_L` / `_H` | R/W | `0x00` | Direction. **0 = input (default), 1 = output** |
-| `0x05` / `0x06` | `GPIO_O_L` / `_H` | R/W | `0x00` | Output level; effective only when `M[n] = 1` |
-| `0x07` / `0x08` | `GPIO_I_L` / `_H` | R | — | Real-time input level |
-| `0x09` / `0x0A` | `GPIO_PU_L` / `_H` | R/W | `0x00` | Pull-up enable |
-| `0x0B` / `0x0C` | `GPIO_PD_L` / `_H` | R/W | `0x00` | Pull-down enable |
-| `0x0D` / `0x0E` | `GPIO_IE_L` / `_H` | R/W | `0x00` | Interrupt enable |
-| `0x0F` / `0x10` | `GPIO_IP_L` / `_H` | R/W | `0x00` | Interrupt polarity — **1 = rising/high, 0 = falling/low** |
-| `0x11` / `0x12` | `GPIO_IS_L` / `_H` | R/W | `0x00` | Interrupt status — **write 0 to clear** |
-| `0x13` / `0x14` | `GPIO_DRV_L` / `_H` | R/W | **`0xFF` / `0x3F`** | **1 = open-drain (default), 0 = push-pull** |
-| `0x15` | `ADC_CTRL` | R/W | `0x00` | `[7]` `BUSY` (R), `[6]` `START`, `[2:0]` channel |
-| `0x16` / `0x17` | `ADC_D_L` / `_H` | R | — | 12-bit result: `_H[3:0]` + `_L[7:0]` |
-| `0x18` | `TEMP_CTRL` | R/W | `0x00` | `[7]` `TBUSY` (R), `[6]` `TSTART` |
-| `0x19` / `0x1A` | `TEMP_D_L` / `_H` | R | — | 12-bit die temperature, **°C** |
-| `0x1B` / `0x1C` | `PWM1_L` / `_H` | R/W | `0x00` | **`IO9`** — PaperMono RGB **blue**. `_H`: `[7]` EN, `[6]` POL, `[3:0]` duty `[11:8]` |
-| `0x1D` / `0x1E` | `PWM2_L` / `_H` | R/W | `0x00` | **`IO8`** — PaperMono RGB **green** |
-| `0x1F` / `0x20` | `PWM3_L` / `_H` | R/W | `0x00` | **`IO11`** |
-| `0x21` / `0x22` | `PWM4_L` / `_H` | R/W | `0x00` | **`IO10`** |
-| `0x23` | `I²C_CFG` | R/W | `0x00` | `[6]` `INTERNAL_PU/PD` (**0 = enabled, 1 = disabled**), `[5]` `WAKE_TYPE` (0 = falling, 1 = rising), `[4]` `SPD` (0 = 100 k, 1 = 400 k), `[3:0]` `SLEEP` idle-sleep seconds (0 = none) |
-| `0x24` | `LED_CFG` | R/W | `0x00` | `[6]` `REFRESH` (self-clearing), `[5:0]` NeoPixel count 0–32 (0 = all off) |
-| `0x25` / `0x26` | `PWM_FREQ_L` / `_H` | R/W | `0xF4` / `0x01` | Frequency in **Hz**; default `0x01F4` = **500 Hz** |
-| `0x27` / `0x28` | `REF_VOLTAGE_L` / `_H` | R | — | 16-bit ADC reference, **mV** |
-| `0x29` | `RESET` | W | — | **Write `0x3A`** to restore factory configuration |
-| `0x30`–`0x6F` | `LED_RAM` | R/W | `0x00` | 64 bytes: 32 NeoPixels × RGB565 |
-| `0x70`–`0x8F` | `RTC_RAM` | R/W | `0x00` | **32 bytes** power-off retention memory |
-| `0x90` | `AW8737A PULSE` | R/W | `0x00` | `[7]` REFRESH, `[6:5]` pulse count 0–3, `[4:0]` target GPIO **0–13 ⇒ GPIO1–GPIO14** |
-
-### 4.1 ADC
-
-`ADC_CTRL[2:0]` **[DS]** §IV.3(1): `000` disabled · `001` **ADC1 = `IO2`** · `010` **ADC2 = `IO4`** · `011` **ADC3 = `IO5`** · `100` **ADC4 = `IO7`**.
-
-Flow: write channel + `START = 1` → poll until `BUSY = 0` → read `ADC_D_H/L` **[DS]** §V.1. Convert with `REF_VOLTAGE` (`0x27`/`0x28`).
-
-Note `ADC4` is on `IO7`, the **same pin that selects the I²C address at power-on** — so on any board that uses address selection, ADC4 is effectively spoken for by a fixed divider.
-
-### 4.2 Pull configuration is a two-register truth table
-
-**[DS]** Table 4, p. 6. `PU[n]`/`PD[n]` are separate registers and `1/1` is **not** an error state, it is "no pull":
-
-| `PU[n]` | `PD[n]` | Result |
-|:--:|:--:|---|
-| 1 | 0 | Pull-up |
-| 0 | 1 | Pull-down |
-| 0 | 0 | None |
-| **1** | **1** | **None** |
-
-### 4.3 PWM
-
-Duty = `DUTY[11:0] / 0xFFF`, `0x000` = 0 %, `0xFFF` ≈ 100 % **[DS]** §IV.5(3). All four channels share the single `PWM_FREQ` register. High and low duty bytes must be written together to avoid a transient wrong duty **[DS]** §IV.5(5).
-
-**I²C idle sleep is disabled outright while PWM is enabled** **[DS]** §V.4 — the same restriction as on the M5PM1.
-
----
-
-## 5. Libraries
-
-| Option | Where | Verdict |
-|---|---|---|
-| **`M5IOE1`** — M5Stack's own dual Arduino/ESP-IDF driver | `github.com/m5stack/M5IOE1`, ESP-IDF registry `m5stack/m5ioe1`, latest **1.0.9**; MIT | ✅ **Use this** — but read §6 first. `src/M5IOE1.h` is a bilingual annotated copy of the register map |
-| Raw I²C / register masks | — | What M5GFX does: `lgfx::i2c::bitOn(port, 0x4F, reg, mask, freq)` **[SRC]** `M5GFX/src/M5GFX.cpp:2088-2096`. Avoids the off-by-one entirely |
-| Raw values with the library object | — | What the vendor's own OTP demo does: `ioe.digitalWrite(2, true)` with the comment `// M5IOE1 uses zero-based pin indexes.` **[SRC]** `EDP_SPI.cpp:36-38` |
-
-Version pinned by the PaperMono factory firmware: **`m5stack/m5ioe1` 1.0.9** **[SRC]** `M5PaperMono-UserDemo/dependencies.lock`.
-
-Examples shipped: `interrupt_hardware`, `interrupt_polling`, `pin_test`. Note the repository also ships a committed `.claude/` directory — agent configuration published in a release library **[SRC]**.
-
----
-
-## 6. ⚠ The `M5IOE1_PIN_n = n − 1` off-by-one
-
-> **This is the single most damaging trap on any board carrying both M5Stack expanders.**
->
-> ```c
-> // M5IOE1/src/M5IOE1.h:31-45
-> M5IOE1_PIN_NC = -1,
-> M5IOE1_PIN_1  = 0,
-> M5IOE1_PIN_2  = 1,
-> M5IOE1_PIN_3  = 2,     // <-- M5IOE1.h:34
-> ...
-> M5IOE1_PIN_14 = 13,
-> ```
->
-> | Part | Enum | Value | Rule | Evidence |
-> |---|---|---|---|---|
-> | **M5IOE1** | `M5IOE1_PIN_3` | **`2`** | Label **1**-based, enum value **0**-based — **off by one** | **[SRC]** `M5IOE1/src/M5IOE1.h:34` |
-> | [**M5PM1**](../m5pm1/README.md) | `M5PM1_GPIO_NUM_3` | **`3`** | 0-based; **label equals value** | **[SRC]** `M5PM1/src/M5PM1.h:410` |
->
-> **Consequences.**
->
-> 1. The documentation label `PYG3` = manual pin `IO3` = enum `M5IOE1_PIN_3` = **raw value 2** = **register bit 2**. Passing the literal `3` where the enum was expected targets `IO4` — on PaperMono, that swaps *e-paper power enable* for *NFC power enable*.
-> 2. The two chips sit on the same bus in the same vendor documentation with **different conventions**. Code that is correct for one is wrong for the other.
-> 3. **There is no `M5IOE1_PIN_0`.** `M5IOE1.h` defines `M5IOE1_PIN_1 … _14` and `M5IOE1_MAX_GPIO_PINS 14` **[SRC]**. So a documentation reference to `PYG0` (e.g. `PYG0_RTC_INT`) **cannot** denote an M5IOE1 pin under any reading — it is an M5PM1 pin that the docs mislabelled with the expander's prefix.
-> 4. M5GFX sidesteps the whole thing by writing register bit masks directly, and its inline comments independently confirm the mapping — **[SRC]** `M5GFX/src/M5GFX.cpp:2088-2092`:
->
-> ```
-> // bit2==IO3: EPD EN
-> // bit4==IO5: EPD RST
-> // bit5==IO6: TP RST
-> // bit12==IO13: TP EN
-> // bit13==IO14: TF EN
-> ```
->
-> 5. The vendor's own recommended e-paper demo distrusts the enum enough to bypass it with an explicit warning comment **[SRC]** `M5PaperMono-OTP-Demo/components/EDP_OTP_LUT_demo/src/EDP_SPI.cpp:36-38`.
->
-> **Neither the manual nor any `docs.m5stack.com` page states this.** It is visible only in the header.
-
----
-
-## 7. Caveats, errata and conflicts
-
-| # | Issue | Evidence |
-|---|---|---|
-| **C1** | **⚠ Address `0x4F` is undocumented.** The V1.4 manual states the address range is **`0x6F`–`0x76`** in three places (§I.2(4), Table 2 note 2, Table 6) and gives an eight-step voltage ladder on `IO7` to select within it. PaperMono uses **`0x4F`**, and `IO7` *is* wired to `ADD_SET`. The library's constant is named `M5IOE1_DEFAULT_ADDR_2`, implying a second scheme, and its auto-detect sweeps **both** `0x6F–0x76` **and** `0x4F–0x50`. **Unresolved.** The two credible readings are (a) the fitted firmware is newer than V1.4 documents and adds a low-address bank, or (b) Table 6 is incomplete. Least-risky implementation path: **do not hardcode either address — use the library's auto-detection, or probe both ranges**, and read `REV` (`0x02`) to learn which firmware you are talking to | **[DS]** §I.2(4), §V.5, Table 6 vs **[SRC]** `M5IOE1/src/M5IOE1.h:80-81`, `hal_board.cpp:14`, `M5GFX.cpp:213`, and **[DOC]** |
-| **C2** | **Pin-numbering off-by-one vs the M5PM1.** §6. Not stated in any vendor document | **[SRC]** `M5IOE1.h:34` vs `M5PM1.h:410` |
-| **C3** | **The `LED_RAM` note contradicts itself.** §IV.7(2) says "PIX0_L = 0x30, **PIX0_H = 0x37**, …, PIX31_H = 0x6F". With 2 bytes per LED starting at `0x30`, `PIX0_H` is `0x31`; `0x37` would be `PIX3_H`. The identical defect appears in the M5PM1 manual's corresponding note | **[DS]** §IV.7(2) p. 8 |
-| **C4** | **`AW8737A PULSE` GPIO field width is inconsistent.** Table 3 draws five `GPIO` bits at `0x90`; §IV.11(3) calls the field `GPIO[4:0]` with range 0–13. Both are self-consistent, but the M5PM1's equivalent register is documented as `[6:5] NUM` / `[5:0] GPIO` — **overlapping bit 5** — so the two manuals cannot both be right about the shared field layout | **[DS]** Table 3 p. 5, §IV.11 p. 8; cf. M5PM1 manual §IV.9 |
-| **C5** | **`REV` default is `A`, an ASCII character in a hex table.** The changelog's last entry is "`SW:A` — Update firmware version to A (ASCII); remove hardware version". Reading `0x02` yields `0x41`, not `0x0A`. Straightforward to get wrong | **[DS]** Table 3 p. 4, appendix p. 10 |
-| **C6** | **No electrical specification whatsoever.** No supply range, no absolute maximum ratings, no I/O drive strength, no ADC input ceiling, no timing. The M5PM1 manual at least states a 3.3 V ADC limit; this one does not | **[DS]** whole document |
-| **C7** | **`ADC4` and address-select share `IO7`.** Any board that biases `IO7` to pick an address has committed that pin, so only three of the four ADC channels are practically available. Not called out by the manual | **[INF]** from **[DS]** §IV.3(1) + §V.5 |
-| **C8** | **`SWDIO`/`SWCLK` are on `IO12`/`IO13`.** These are the PY32's debug pins. SWDIO is "disabled by default", but `IO13` (SWCLK) is used on PaperMono as the touch-controller power enable. Whether re-enabling SWD is possible at runtime, and what that does to a live board, is not documented | **[DS]** Table 2 p. 3; **[SCH]** `U17`.15 |
-| **C9** | **Docs omit `IO4` and `IO11`.** M5Stack's dedicated power-management API page lists eleven M5IOE1 pins and mentions **neither `PIN_4`** (NFC power enable, `hal_board.cpp:29`) **nor `PIN_11`** (the IP2315 I²C gate — the one pin with a published bus-stability hazard). A reader working only from that page would not know either exists | **[DOC]** vs **[SRC]** `hal_board.cpp:29`, `Power_Class.cpp:78-80` |
-| **C10** | **A stale comment in M5GFX misdescribes an expander write.** `M5GFX.cpp:2096` reads `bitOn(..., 0x06, 0b00110000, ...)` with the comment `// Set LOW io11, HIGH io13,14`. Register `0x06` is `GPIO_O_H` (P14–P9 in `[5:0]`); mask `0b00110000` is bits 4–5 ⇒ **`IO13` and `IO14` only**, and `bitOn` cannot set anything low. The **code** is consistent with the rest of the bring-up; the comment is wrong. Inert, but misleading to anyone reverse-engineering the pin map from comments | **[SRC]** `M5GFX/src/M5GFX.cpp:2096` |
-| **C11** | **`INTERNAL_PU/PD` polarity is inverted relative to intuition:** `0 = Enabled`, `1 = Disabled` | **[DS]** §IV.6(1) p. 7 |
-
----
-
-## 8. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — designator `U17`, sheet 4
-
-The M5IOE1 sits on rail **`L2`** (so it is powered only when the ESP32-S3 is) and in turn owns rail **`L3B`**. That ordering matters: the expander is **not** available while the board is in its deepest sleep state, and the peripherals it gates come up only after M5Unified has initialised it **[DOC]**.
-
-| Role on PaperMono | Pin / enum | Evidence |
-|---|---|---|
-| System I²C slave at **`0x4F`** on the shared internal bus, **GPIO47 = SDA / GPIO48 = SCL**, 100 kHz | pins 8/9 | **[SCH]** `U17`.8/.9; **[SRC]** `hal_board.cpp:14`; **[FW]** |
-| Interrupt out to **ESP32-S3 GPIO7** | pin 2 `INT_OUT` → `G7_PYB_IRQ` | **[SCH]** `U17`.2; **[DOC]**. ⚠ **Not exercised by the factory firmware** — it initialises the expander with `M5IOE1_INT_MODE_DISABLED` (`hal_board.cpp:62`) and polls instead; `GPIO_NUM_7` appears **zero** times in the UserDemo **[SRC]** |
-| Expander reset | pin 1 `NRST` ← `RST` via `R53` | **[SCH]** `U17`.1 |
-| **Address select** | pin 19 `IO7` ← `ADD_SET` | **[SCH]** `U17`.19. See §7-C1 |
-| microSD card-detect (active low) | `IO1` / `M5IOE1_PIN_1` (value **0**) | **[SRC]** `hal_tf_card.cpp:16` |
-| **SX1262 antenna switch** | `IO2` / `M5IOE1_PIN_2` (value **1**) | **[SRC]** `hal_lora.cpp:31` |
-| **E-paper 3V3 rail enable** (`EPD_3V3_L3B`) | `IO3` / `M5IOE1_PIN_3` (value **2**) | **[SRC]** `app_sleep_wake.cpp:73`; `EDP_SPI.cpp:37` (raw `2`); `M5GFX.cpp:2088` (`bit2`) — **three independent sources** |
-| **NFC/RFID power enable** | `IO4` / `M5IOE1_PIN_4` (value **3**) | **[SRC]** `hal_board.cpp:29`, `app_sleep_wake.cpp:74`. Also the **Pro-vs-Lite discriminator**: if this write fails the firmware declares the board a Lite (`hal_board.cpp:160-172`) |
-| **E-paper reset** | `IO5` / `M5IOE1_PIN_5` (value **4**) | **[SRC]** `app_sleep_wake.cpp:75`; `EDP_SPI.cpp:38` (raw `4`); `M5GFX.cpp:2089` (`bit4`) |
-| FT6336G touch reset | `IO6` / `M5IOE1_PIN_6` (value **5**) | **[SRC]** `app_sleep_wake.cpp:76`; `M5GFX.cpp:2090` (`bit5`) |
-| RGB LED **green**, PWM channel **2** | `IO8` / `M5IOE1_PIN_8` (value **7**) | **[SRC]** `hal_board.cpp:25,27` |
-| RGB LED **blue**, PWM channel **1** | `IO9` / `M5IOE1_PIN_9` (value **8**) | **[SRC]** `hal_board.cpp:26,28` |
-| **SX1262 `NRST`** | `IO10` / `M5IOE1_PIN_10` (value **9**) | **[SRC]** `hal_lora.cpp:30` |
-| **IP2315 charger I²C bus gate** | `IO11` (`gpio11`, value **10**) | **[SRC]** `M5Unified/src/utility/Power_Class.cpp:78-80, 85` |
-| PDM microphone power enable | `IO12` / `M5IOE1_PIN_12` (value **11**) | **[SRC]** `hal_mic.cpp:13`; `hal_board.cpp:30` |
-| FT6336G touch VDD enable | `IO13` / `M5IOE1_PIN_13` (value **12**) | **[SRC]** `app_sleep_wake.cpp:81`; `M5GFX.cpp:2091` (`bit12`) |
-| microSD power enable | `IO14` / `M5IOE1_PIN_14` (value **13**) | **[SRC]** `hal_tf_card.cpp:15`; `M5GFX.cpp:2092` (`bit13`) |
-
-**The RGB LED is split across two chips.** Red is `LED_EN` on the [M5PM1](../m5pm1/README.md); green and blue are `IO8`/`IO9` here. Both use 5 kHz PWM **[SRC]** `hal_board.cpp:24`.
-
-**The IP2315 gate is a structural mitigation, not advice.** M5Stack's warning reads: "do not keep the IP2315 mounted on the I²C bus for extended periods; disconnect it promptly after communication to avoid reducing bus communication stability" **[DOC]**. In code the charger is physically gated **off** the bus by `IO11` and connected only for the duration of a transaction, with a **64-attempt** scan loop waiting for it to appear, then disconnected again **[SRC]** `Power_Class.cpp:88-96`, `:2399`, `:2724`. Any caller that talks to `0x75` without going through `set_papermono_ip2315_enabled()` simply will not find it.
-
-**M5Unified already owns several of these pins.** M5Stack's own warning **[DOC]**: "The pins associated with the e-paper display, touch controller, microSD, and PDM microphone are already used by M5Unified. Before modifying them, ensure that the corresponding peripheral has stopped, or the peripheral may stop working or require reinitialization."
-
-**Not verified on this board:** the interrupt output (polled instead); all four ADC channels (`IO2`, `IO4`, `IO5`, `IO7` are all used as digital lines or as `ADD_SET`); PWM3/PWM4 (`IO11`/`IO10` used as digital); NeoPixel on `IO14`; the temperature sensor; the retention RAM; the `AW8737A` pulse register.
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md)
-
-**Same part, same designator, same address.** The Lite drops NFC and LoRa, so `IO2`, `IO4` and `IO10` lose their consumers; the vendor pin table on the Lite product page renames `TF_EN`/`TF_DET` to `EN`/`DET` but the pins are identical **[DOC]**. M5Stack publishes a 4-sheet `PRJ` PDF for the Lite rather than the 6-sheet `SCH`, so the Lite's expander wiring is **not** independently confirmed against a schematic here.
-
----
-
-## 9. Related components
-
-- [**M5PM1**](../m5pm1/README.md) — the sibling custom PMIC: same publisher, same PY32 die, **different pin-numbering convention** (§6) and a fixed address
-- `components/puya/py32l020f15u6/` — the underlying MCU. *Record pending.* The only source of electrical limits, which this manual omits entirely (§7-C6)
-- [**Solomon Systech SSD1677**](../../solomon-systech/ssd1677/README.md) — the e-paper controller whose power and reset lines are `IO3` and `IO5`
-- [**DKE DEPG0397BBS770F3**](../../dke/depg0397bbs770f3/README.md) — the panel behind it
-- [**Semtech SX1262**](../../semtech/sx1262/README.md) · [**M5Stack Stamp-LoRa-1262**](../stamp-lora-1262/README.md) — reset and antenna switch on `IO10` / `IO2`
-- [Vendor sourcing guides index](../../../vendors/README.md) — no M5Stack chip-documentation guide exists yet
-
----
-
-## 10. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf` | 398 463 | `9204d99cb2e03395ffc905e05fbeddf7f9f25de5698a31a65fa439dee700d8d2` | **M5IOE1 Chip User Manual V1.4**, 10 pp., English. PDF metadata: Author `洋 熊`, Creator/Producer `Microsoft® Word 2021`, created **2026-01-26**. Text layer validated against rendered headings before transcription |
-
-**Text-layer validation.** `pdftotext -layout` output was cross-checked against the running headers (`M5IOE1 Chip User Manual`), footers (`n / 10`, `The Innovator of Modular IoT Development Platform | M5Stack`) and section numbering. No subsetting or code-point-offset corruption observed.
-
-**Metadata note.** The same author string (`洋 熊`) and toolchain produced the M5PM1 manual, and the two documents share their section structure — consistent with one document having been derived by editing the other. Where they disagree about a shared feature (e.g. the `AW8737A` bit layout, §7-C4), neither is automatically authoritative.
-
-**A Chinese-language edition exists and was not retrieved.** The `zh_CN` product page links `1210/IO_Expander_Datasheet_CN.pdf` where `en`/`ja` link `IO_Expander_Datasheet_EN.pdf` **[DOC]**. Note the upstream *filename* is `IO_Expander_Datasheet_EN.pdf`, not `M5IOE1_…` — worth knowing when searching. A CN↔EN diff is the most promising route to settling §7-C1.
-
-**Licence.** M5Stack copyright, no licence statement on the document. Redistribution status **`unknown`**; disposition `repository`.
-
----
-
-## 11. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | M5IOE1 Chip User Manual | **M5Stack** (imprint: Shenzhen Mingzhan Information Technology Co., Ltd.) | primary | chip manual | `artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf`; upstream `static-cdn.m5stack.com/resource/docs/products/core/PaperMono/1210/IO_Expander_Datasheet_EN.pdf` | 2026-09-01 | **V1.4, 2025-11-25** | §1–§4, §7 |
-| S-2 | PaperMono schematic | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | **V0.6.2, 2026-05-22**, 6 sheets | §1 silicon identity (sheet 1), §2 pin table (sheet 4 `U17`), §8 wiring |
-| S-3 | `M5IOE1` Arduino/ESP-IDF driver | M5Stack | primary | source | `github.com/m5stack/M5IOE1` @ `846eec7d05e25c09013be2acdb8804487f48a62e` | 2026-09-01 | tag **1.0.9**, MIT | §4 symbol names, §6 enum values, §7-C1 |
-| S-4 | `M5PaperMono-UserDemo` factory firmware source | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-UserDemo` @ `c1099107271d31a0678d661a896e2b04dbb331ea` | 2026-09-01 | 2026-08-10, MIT | §8 board roles |
-| S-5 | `M5PaperMono-OTP-Demo` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-OTP-Demo` @ `c7c02554f89fd06f80d988b805b2a59050c78a46` | 2026-09-01 | 2026-08-20, MIT | §5, §6 raw-index workaround |
-| S-6 | `M5GFX` / `M5Unified` | M5Stack | primary | source | `github.com/m5stack/M5GFX` @ `d91077b9…`; `github.com/m5stack/M5Unified` @ `8530f537…` | 2026-09-01 | 0.2.28 / 0.2.21 | §6 bit-mask confirmation, §7-C10, §8 IP2315 gate |
-| S-7 | PaperMono product page + `arduino/papermono/m5pm1_m5ioe1` API page | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono`, `.../en/arduino/papermono/m5pm1_m5ioe1` | 2026-09-01 | undated | §7-C9, §8 power tree and IP2315 warning |
-| S-8 | `C153-PaperMono-ESP32S3R8-UserDemo-V1.2` firmware image | M5Stack via M5Burner | primary | binary | firmware id `2089640807996628993`, SHA-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | 2026-09-01 | v1.2, built 2026-08-06 | §1 100 kHz default, address `0x4F` |
diff --git a/components/m5stack/m5ioe1/artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf b/components/m5stack/m5ioe1/artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf
deleted file mode 100644
index 04c259d..0000000
Binary files a/components/m5stack/m5ioe1/artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf and /dev/null differ
diff --git a/components/m5stack/m5pm1/README.md b/components/m5stack/m5pm1/README.md
deleted file mode 100644
index f9a5d86..0000000
--- a/components/m5stack/m5pm1/README.md
+++ /dev/null
@@ -1,425 +0,0 @@
-# M5Stack M5PM1
-
-- **Category:** custom I²C power-management controller — rail enables, battery charging control, ADC monitoring, power button/state machine, timed wake, 5 multiplexed GPIOs
-- **Not an ASIC.** The schematic identifies the underlying silicon as a **Puya `PY32L020F15U6`** Cortex-M0+ MCU running M5Stack's own power-management firmware. Everything below is *firmware* behaviour, not silicon behaviour, and can change with a firmware revision.
-- **I²C address:** `0x6E` (fixed; no address-select pin)
-- **Research status:** the **full M5Stack manual is retained** in `artifacts/` (V1.9, 33 pages) and has been read end to end. The pin table is independently corroborated pin-for-pin by the PaperMono schematic. No hardware was in the loop.
-- **Retrieved:** 2026-09-01
-
-The power-management controller of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) and its Lite sibling. It owns the battery, the 3.3 V LDO and DC/DC rails, the power button, the ESP32-S3 `BOOT` strap and the frontlight PWM — i.e. on this board the ESP32-S3 does not control its own power at all.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | Stated in `artifacts/m5pm1-chip-user-manual-v1.9-en.pdf`, with page reference | `not-tested` — vendor claim reproduced verbatim; nothing measured |
-| **[SCH]** | Read out of `PaperMono_SCH_V0.6.2_20260522.pdf`, cited as sheet + designator + pin | `executed-success` for the extraction (PDF parsed, pin markers enumerated); `not-tested` electrically |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | `docs.m5stack.com` product/API page, retrieved 2026-09-01 | `not-tested` |
-| **[FW]** | String recovered from the shipped factory firmware binary | `executed-success` for the extraction |
-| **[INF]** | Inference drawn from two or more of the above | `inferred` |
-
-**Nothing in this record was verified electrically.** No pin, register or address below was guessed; every one is transcribed from a cited document, schematic pin marker or source line.
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketing name | **`M5PM1`** | **[DS]** cover; **[SCH]** sheet 2 block label next to `U7` |
-| Publisher of the manual | **Shenzhen Mingzhan Information Technology Co., Ltd.** (深圳市明栈信息科技有限公司 — M5Stack's legal entity) | **[DS]** cover |
-| Document | **M5PM1 Chip User Manual V 1.9**, 33 pp., dated **2026-01-22** in its own revision table | **[DS]** cover, p. 33 |
-| **Underlying silicon** | **`PY32L020F15U6`** — Puya Semiconductor PY32 series, Cortex-M0+ | **[SCH]** sheet 1, power/IO map block diagram: the legend row `PMIC` is annotated `PY32L020F15U6` |
-| Nature of the part | A **general-purpose MCU pre-programmed with M5Stack firmware**, not a purpose-built PMIC | **[DS]** §I: "M5PM1 is a power management IC **programmed with M5Stack custom power management firmware**" |
-| I²C address | **`0x6E`**, fixed | **[DS]** §I.2(4); **[SRC]** `M5PM1/src/M5PM1.h:73` (`M5PM1_DEFAULT_ADDR`); **[SRC]** `M5PaperMono-UserDemo/main/hal/hal_board.cpp:13` |
-| I²C speed | **100 kHz default**, 400 kHz selectable via `I2C_CFG[4]` | **[DS]** §I.2(4), §IV.1(10) |
-| Package | **21 pads** on the schematic symbol: 20 signal/power pins per the manual's Table 1, plus **pin 21 = GND** (exposed pad) | **[DS]** Table 1 (p. 2) gives pins 1–20; **[SCH]** sheet 2 `U7` shows a 21st marker netted to `GND` |
-| Reference designator on PaperMono | **`U7`**, sheet 2 | **[SCH]** |
-| Device identity registers | `Device_ID` (`0x00`) = **`0x50`**, `Device_Model` (`0x01`) = **`0x20`**, `HW_REV` (`0x02`) = **`0x05`**, `SW_REV` (`0x03`) = **`0x06`** | **[DS]** Table 3 (p. 4), §IV.1(1)–(4) |
-| ⚠ Marking verified? | **No.** No teardown photograph of `U7` was inspected. The `PY32L020F15U6` identification rests on the schematic's own block diagram, which is a primary vendor document but not a photograph of the die or top marking | **[INF]** |
-
-### 1.1 Why "it is a PY32" matters
-
-Three practical consequences follow from the part being a stock MCU with vendor firmware rather than dedicated silicon:
-
-1. **The register map is a firmware API, not a hardware datasheet.** The manual's appendix carries a *Firmware Modification History* running from `HW:2 / SW:1` (2025-06-30) to `HW:5 / SW:S` (2026-01-06), and register addresses genuinely moved between those revisions (see §11-C4). Read `SW_REV` (`0x03`) before assuming a layout.
-2. **"Download mode" is an MCU bootloader.** `SYS_CMD` (`0x0C`) `CMD=11` and a long press of `PWR_BTN` both put the part into a firmware-update mode **[DS]** §IV.1(13), §V.3. That is a real re-flash path for the PY32, and `BTN_CFG_1[7] DL_LOCK` exists specifically to disable it **[DS]** §IV.7(2).
-3. **Electrical limits are the PY32's, and the manual does not restate them.** The manual gives no absolute maximum ratings, no supply range and no I/O current ratings — only "ADC channel input voltage must not exceed 3.3 V" **[DS]** §VI.3(2). For anything else you must consult Puya's `PY32L020` documentation (component record pending at `components/puya/py32l020f15u6/`).
-
----
-
-## 2. Pin table
-
-The manual's Table 1 (custom-firmware pin arrangement) and the PaperMono schematic symbol agree on all 20 signal pins, in order. Both are reproduced so the two naming conventions can be reconciled — they are **not** the same names.
-
-| Pin | Manual name **[DS]** p. 2 | Manual type **[DS]** | Schematic symbol name **[SCH]** `U7` | PaperMono net **[SCH]** |
-|---:|---|---|---|---|
-| 1 | `BAT_ADC_EN` | Push-pull output | `BAT_ADC_EN_OD` | `BAT_ADC_EN` |
-| 2 | `CHG_EN` | Push-pull output | `CHG_EN_PP` | charger enable |
-| 3 | `IO0` | GPIO | `G0_WAKEin(INT0/2)_IRQout_NEOPIXEL` | `PYG0_RTC_INT` |
-| 4 | `VSS` | Power | `GND` | `GND` |
-| 5 | `LED_EN` | Push-pull output | `LED_EN_PP` | `PY_LED_R` |
-| 6 | `VCC` | Power | `VCC` | `3V3_L0` |
-| 7 | `PWR_BTN` | Input, pull-up | `BTN_PU` | `PWR_BTN` |
-| 8 | `SDA` | I²C | `I2C_SDA_OD` | `G47_SYS_SDA` |
-| 9 | `SCL` | I²C | `I2C_SCL_OD` | `G48_SYS_SCL` |
-| 10 | `DCDC_5V_EN` | Push-pull output | **`BOOST5V_EN_PP`** | 5 V boost enable |
-| 11 | `BAT_ADC` | ADC | `BAT_ADC_IN` | `BAT_ADC` |
-| 12 | `IO4` | GPIO | `G4_WAKEin(INT3/4)_IRQout_PWM` | `PYG4_IMU_INT` |
-| 13 | `IO3` | GPIO | `G3_WAKEin(INT3/4)_IRQout_PWM` | `PYG3_BL_PWM` |
-| 14 | `DCDC_3V3_EN` | Push-pull output | `DCDC3V3_EN_PP` | `3V3_L2_EN` |
-| 15 | `BOOT_OUT` | **Open-drain** output | `BOOT_OUT_OD` | `G0_BOOT_OUT` |
-| 16 | `5VIN_ADC` | ADC | `5VIN_ADC_IN` | `5VIN_ADC` |
-| 17 | `IO1` | GPIO | `G1_IRQout_ADC` | `G1_PY_IRQ` |
-| 18 | `LDO_3V3_EN` | Push-pull output | `LDO3V3_EN_PP` | `3V3_L1_EN` |
-| 19 | `5VOUT_ADC` | ADC | `5VOUT_ADC_IN` | *(5 V output sense)* |
-| 20 | `IO2` | GPIO | `G2_WAKEin(INT0/2)_IRQout_ADC` | `PYG2_LoRa_EN` |
-| 21 | *(not in Table 1)* | — | `GND` | `GND` |
-
-Two naming deltas worth carrying forward:
-
-- **Pin 10.** The manual calls it `DCDC_5V_EN`; the schematic symbol calls it `BOOST5V_EN_PP`. Same pin, same function (5 V boost enable). **[INF]**
-- **Pins 12/13 are `IO4`/`IO3`, in that order** — the higher-numbered GPIO comes first. Reading the schematic symbol top-to-bottom and assuming ascending GPIO numbers gets this wrong.
-
-### 2.1 Pin functional description
-
-**[DS]** Table 2, p. 3, unless noted.
-
-| Pin | Description | Default state | Note |
-|---|---|---|---|
-| `IO0` | GPIO 0, **supports wake-up**; MUX = **NeoPixel output** | GPIO | Wake is **mutually exclusive with `IO2`** |
-| `IO1` | GPIO 1; MUX = **ADC1** | GPIO | **Cannot wake** — its interrupt line conflicts with `SDA` **[DS]** Table 3 note on `GPIO_WAKE_EN` |
-| `IO2` | GPIO 2, supports wake-up; MUX = **ADC2** | GPIO | Wake mutually exclusive with `IO0` |
-| `IO3` | GPIO 3, supports wake-up; MUX = **PWM** | GPIO | Wake mutually exclusive with `IO4` |
-| `IO4` | GPIO 4, supports wake-up; MUX = **PWM** | GPIO | Wake mutually exclusive with `IO3` |
-| `BAT_ADC_EN` | Battery-sampling enable, active high | **High** | |
-| `CHG_EN` | Battery-charging enable, active high | **High** (charging on) | Push-pull; polarity was inverted at `HW:3 / SW:2` **[DS]** p. 32 |
-| `DCDC_5V_EN` | 5 V DC/DC (boost) control, active high | **Low** | |
-| `DCDC_3V3_EN` | 3.3 V DC/DC control, active high | **High** | Drives `3V3_L2_EN` on PaperMono |
-| `LDO_3V3_EN` | 3.3 V LDO control, active high | **High** | Drives `3V3_L1_EN` on PaperMono |
-| `5VIN_ADC` | 5 V input sense | ADC | **Divider ratio 1:1** |
-| `5VOUT_ADC` | 5 V output sense | ADC | **Divider ratio 1:1** |
-| `BAT_ADC` | Battery voltage sense | ADC | **Divider ratio 1:1** |
-| `PWR_BTN` | Power-button input | Button detection | Internal pull-up enabled by default |
-| `LED_EN` | Status-indicator LED control | LED control | **High** by default. "Uses M5PM1 proprietary LED self-control logic and is **not recommended for other purposes**" |
-| `BOOT_OUT` | Controls the main controller's (ESP32) `BOOT` strap | **High** | **Open-drain output** |
-| `SDA` / `SCL` | I²C | I²C | **Open-drain; external pull-ups required** |
-
-> ⚠ **All GPIO outputs default to open-drain**, including NeoPixel and PWM output. With no external pull-up you must set `GPIO_DRV` to push-pull or the pin will not drive high. **[DS]** Table 2 note 1. `GPIO_DRV` has **higher priority than the mux function** — configuring a pin as PWM does not override an open-drain setting. **[DS]** §IV.2(4).
-
-### 2.2 GPIO mux summary
-
-| GPIO | Wake | IRQ out | ADC | PWM | NeoPixel | Schematic symbol suffix |
-|---|:--:|:--:|:--:|:--:|:--:|---|
-| `IO0` | ✅ (excl. `IO2`) | ✅ | — | — | ✅ | `_WAKEin(INT0/2)_IRQout_NEOPIXEL` |
-| `IO1` | ❌ | ✅ | ✅ ch1 | — | — | `_IRQout_ADC` |
-| `IO2` | ✅ (excl. `IO0`) | ✅ | ✅ ch2 | — | — | `_WAKEin(INT0/2)_IRQout_ADC` |
-| `IO3` | ✅ (excl. `IO4`) | ✅ | — | ✅ | — | `_WAKEin(INT3/4)_IRQout_PWM` |
-| `IO4` | ✅ (excl. `IO3`) | ✅ | — | ✅ | — | `_WAKEin(INT3/4)_IRQout_PWM` |
-
-The schematic symbol annotates pins 13 and 20 with 唤醒源二选一 — "wake source: pick one of two" — which is the same mutual-exclusion rule drawn on the symbol itself **[SCH]** `U7` pins 13, 20.
-
----
-
-## 3. Register map
-
-Transcribed from **[DS]** Table 3 (pp. 4–11) and §IV (pp. 12–25). Library symbol names are from **[SRC]** `M5PM1/src/M5PM1.h`; that header is an exhaustively commented bilingual copy of this same map and is the practical reference when writing code.
-
-> ⚠ **Burst access is range-limited.** I²C sequential read/write works **only within** `0x00–0x0C`, `0x10–0x19`, `0x20–0x2A`, `0x30–0x35`, `0x38–0x3D`, `0x40–0x45`, `0x48–0x4A`, `0x50`, `0x53`, `0x60–0x9F`, `0xA0–0xBF`. Crossing a range boundary requires separate transactions. **[DS]** §IV preamble, p. 12.
-
-### 3.1 System
-
-| Addr | Name | Access | Default | Function |
-|---|---|---|---|---|
-| `0x00` | `Device_ID` | R | `0x50` | Device type |
-| `0x01` | `Device_Model` | R | `0x20` | Device model |
-| `0x02` | `HW_REV` | R | `0x05` | Hardware revision |
-| `0x03` | `SW_REV` | R | `0x06` | Firmware revision |
-| `0x04` | `PWR_SRC` | R | — | `[2]` BAT valid, `[1]` 5VINOUT valid *(only while the 5 V boost is disabled)*, `[0]` 5VIN valid |
-| `0x05` | `WAKE_SRC` | R/W | — | `[6]` 5VINOUT insert, `[5]` GPIO wake, `[4]` command reset, `[3]` reset button, `[2]` power button, `[1]` 5VIN insert, `[0]` timer. **Writing only clears flags; it cannot select a source** |
-| `0x06` | `PWR_CFG` | R/W | `0x17` | `[4]` LED_EN level, `[3]` 5 V boost enable, `[2]` 3V3 LDO enable, `[1]` 3V3 DC/DC enable, `[0]` charge enable |
-| `0x07` | `HOLD_CFG` | R/W | `0x00` | Retain-across-power-off: `[6]` 5VIN/OUT, `[5]` LDO 3V3, `[4:0]` GPIO4–GPIO0. **Reset to `0x00` by any reset or Download mode** |
-| `0x08` | `BATT_LVP` | R/W | `0x40` | Low-voltage cut-off = **2000 mV + n × 7.81 mV** (default ⇒ 2.5 V) |
-| `0x09` | `I2C_CFG` | R/W | `0x00` | `[4]` SPD (0 = 100 k, 1 = 400 k), `[3:0]` `SLP_TO` idle-sleep seconds (0 = disabled) |
-| `0x0A` | `WDT_CNT` | R/W | `0x00` | Watchdog countdown in **seconds**; 0 disables |
-| `0x0B` | `WDT_KEY` | W | — | Write **`0xA5`** to feed |
-| `0x0C` | `SYS_CMD` | W | — | `[7:4]` KEY = `0xA`, `[1:0]` CMD: **`01` power off, `10` restart, `11` Download mode** |
-
-### 3.2 GPIO
-
-| Addr | Name | Access | Default | Function |
-|---|---|---|---|---|
-| `0x10` | `GPIO_MODE` | R/W | `0x00` | `[4:0]` direction, 1 = output. Effective only when the matching `GPIO_FUNC` = `00` |
-| `0x11` | `GPIO_OUT` | R/W | `0x00` | `[4:0]` output level. Effective only when `GPIO_FUNC` = `00` **and** `GPIO_MODE` = 1 |
-| `0x12` | `GPIO_IN` | R | — | `[4:0]` real-time input level |
-| `0x13` | `GPIO_DRV` | R/W | **`0x1F`** | `[5]` LED_EN, `[4:0]` GPIO4–0. **1 = open-drain, 0 = push-pull.** Overrides the mux function |
-| `0x14` | `GPIO_PU/PD_0` | R/W | `0x00` | 2 bits per pin, GPIO3–GPIO0: `00` none, `01` pull-up, `10` pull-down |
-| `0x15` | `GPIO_PU/PD_1` | R/W | `0x00` | `[1:0]` GPIO4 |
-| `0x16` | `GPIO_FUNC0` | R/W | `0x00` | 2 bits per pin, GPIO3–GPIO0: `00` GPIO, `01` IRQ, `10` reserved, **`11` mux (NeoPixel / ADC / PWM)** |
-| `0x17` | `GPIO_FUNC1` | R/W | `0x00` | `[1:0]` GPIO4 |
-| `0x18` | `GPIO_WAKE_EN` | R/W | `0x00` | `[4:0]`, 1 = wake enabled. **GPIO1 unsupported**; GPIO0/GPIO2 and GPIO3/GPIO4 are pairwise exclusive |
-| `0x19` | `GPIO_WAKE_CFG` | R/W | `0x00` | `[4:0]` edge, **1 = rising, 0 = falling**. GPIO1 unsupported |
-
-> **Wake configuration survives Reset, Download mode and power-off.** `GPIO_WAKE_EN`/`GPIO_WAKE_CFG` are explicitly exempted from the state reset that clears everything else. **[DS]** §IV.2(7) note 1, §IV.2(8) note.
-
-### 3.3 ADC
-
-| Addr | Name | Access | Function |
-|---|---|---|---|
-| `0x20` / `0x21` | `VREF_L` / `_H` | R | Internal ADC reference, **mV** |
-| `0x22` / `0x23` | `VBAT_L` / `_H` | R | Battery voltage, **mV** |
-| `0x24` / `0x25` | `VIN_L` / `_H` | R | 5 V input voltage, **mV** |
-| `0x26` / `0x27` | `5VOUT_L` / `_H` | R | 5 V output voltage, **mV** |
-| `0x28` / `0x29` | `ADC_RES_L` / `_H` | R | Raw 12-bit result `[11:0]`; `_H[3:0]` is the high nibble |
-| `0x2A` | `ADC_CTRL` | R/W | `[3:1]` `CH_SEL` — **1 = GPIO1, 2 = GPIO2, 6 = internal die temperature (°C)**; `[0]` `START`, self-clearing |
-
-Flow: write `ADC_CTRL` with channel + `START=1` → poll until busy clears → read `ADC_RES_H/L` **[DS]** §V.1. Actual voltage = `raw × VREF / 4096` **[DS]** §VI.3. Channels 1 and 2 only work when the corresponding `GPIO_FUNC` is `11`.
-
-The three dedicated rail sense inputs (`BAT_ADC`, `5VIN_ADC`, `5VOUT_ADC`) are **not** reachable through `ADC_CTRL`; they are read from their own `VBAT`/`VIN`/`5VOUT` register pairs in millivolts and are used internally for low-voltage protection and insert/remove detection **[DS]** §V.1(2).
-
-### 3.4 PWM
-
-| Addr | Name | Access | Default | Function |
-|---|---|---|---|---|
-| `0x30` | `PWM0_L` | R/W | `0x00` | PWM0 duty `[7:0]` — **this is the PaperMono frontlight** |
-| `0x31` | `PWM0_HC` | R/W | `0x00` | `[5]` POL (1 = active-low), `[4]` EN, `[3:0]` duty `[11:8]` |
-| `0x32` | `PWM1_L` | R/W | `0x00` | PWM1 duty `[7:0]` |
-| `0x33` | `PWM1_HC` | R/W | `0x00` | `[5]` POL, `[4]` EN, `[3:0]` duty `[11:8]` |
-| `0x34` / `0x35` | `PWM_FREQ_L` / `_H` | R/W | `0xF4` / `0x01` | Frequency in **Hz**; default `0x01F4` = **500 Hz** |
-
-Duty = `DUTY[11:0] / 0xFFF`. **Both channels share one timer, therefore one frequency** **[DS]** §VI.4(2). High and low bytes must be written together or a transient wrong duty/frequency occurs **[DS]** §V.2.
-
-### 3.5 Timer
-
-| Addr | Name | Access | Function |
-|---|---|---|---|
-| `0x38`–`0x3B` | `TIM_CNT_BYTE_0..3` | R/W | Countdown in **seconds**, 31-bit (`0x3B[6:0]`), max **214 748 364 s** ≈ 6.8 years |
-| `0x3C` | `TIM_CFG` | R/W | `[3]` `ARM` (self-clearing at zero), `[2:0]` `ACTION` |
-| `0x3D` | `TIM_KEY` | W | Write **`0xA5`** to reload |
-
-`ACTION` truth table **[DS]** Table 4, p. 20: `000` stop · `001` set wake flag · `010` system restart · `011` **system power on** · `100` system power off.
-
-`TIM_ACTION_POWERON` is the mechanism behind "shut down and come back in N seconds" — the M5PM1 stays alive on `L0` while everything else is off. **[DOC]**
-
-### 3.6 Interrupts and button
-
-| Addr | Name | Access | Function |
-|---|---|---|---|
-| `0x40` | `IRQ Status 1` | R/W | `[4:0]` GPIO4–0 level-change flags. **Set by hardware, cleared only by the user** |
-| `0x41` | `IRQ Status 2` | R/W | `[5]` battery remove, `[4]` battery add, `[3]` 5VINOUT remove, `[2]` 5VINOUT add, `[1]` 5VIN remove, `[0]` 5VIN add — all thresholded at **2400 mV** |
-| `0x42` | `IRQ Status 3` | R/W | `[2]` double-click, `[1]` wakeup, `[0]` single-click |
-| `0x43` / `0x44` / `0x45` | `IRQ Status 1/2/3 Mask` | R/W | 1 = masked |
-| `0x48` | `BTN_Status` | R | `[7]` `BTN_Event` (press occurred; **cleared on read**), `[0]` `BTN_Status` (1 = currently pressed) |
-| `0x49` | `BTN_CFG_1` | R/W `0x2A` | `[7]` `DL_LOCK` (1 = disable Download mode), `[6:5]` double-click window (125 ms / 250 ms / 500 ms / 1 s), `[4:3]` long-press (1/2/3/4 s), `[2:1]` single-click window, `[0]` `SINGLE_RESET_DIS` |
-| `0x4A` | `BTN_CFG_2` | R/W `0x00` | `[0]` `DOUBLE_POWEROFF_DIS` |
-
-### 3.7 NeoPixel, audio pulse and retention RAM
-
-| Addr | Name | Access | Function |
-|---|---|---|---|
-| `0x50` | `NEO_CFG` | R/W | `[6]` `REFRESH`, `[5:0]` LED count 0–32 (0 = driver off) |
-| `0x53` | `AW8737A PULSE` | R/W | `[7]` REFRESH, `[6:5]` pulse count 0–3, `[4:0]` target GPIO 0–4 |
-| `0x60`–`0x9F` | `NEO_PIXn_L/H` | R/W | 32 × RGB565, 64 bytes |
-| `0xA0`–`0xBF` | `RTC_MEM` | R/W | **32 bytes of retention RAM** |
-
-The retention RAM survives *the ESP32's* power-off, **not** the M5PM1's: "M5PM1 power-off does not retain data" **[DS]** §IV.11.
-
-`0x53` drives an **AW8737A** audio power amplifier by counting pulses on a GPIO. No amplifier appears in the PaperMono specification — only a buzzer and a PDM microphone — so this register is most likely a generic firmware feature unused on this board. **[INF]**; the same feature exists in the sibling [M5IOE1](../m5ioe1/README.md) at `0x90`.
-
----
-
-## 4. Behaviours you have to know before writing code
-
-### 4.1 The first I²C transaction after idle sleep always fails
-
-**[DS]** §IV.1(10) note 2, restated on the vendor API page **[DOC]**:
-
-> After the idle-sleep function is configured and triggered, M5PM1 enters sleep. If woken via I²C, **the first I²C transaction is used only for wake-up and will fail.** Subsequent communications operate normally. Within **300 ms** after that first wake transaction, if M5PM1 does not receive a complete address it will sleep again.
-
-Idle sleep is **not self-clearing** — once `I2C_CFG[3:0]` is set, only the user can clear it. Wake-up is driven by a **fixed 100 ms internal timer that cannot be changed** **[DS]** §V.7 note. Idle sleep is also **disabled outright while any PWM channel is enabled**, and in Download mode **[DS]** §V.6 note.
-
-### 4.2 IRQ is a wired-OR, and clearing it is all-or-nothing
-
-**[DS]** §V.8. When *any* GPIO is configured as an IRQ pin (`GPIO_FUNC` = `01`):
-
-- The IRQ pin is pulled **low** while `IRQ Status 1`, `2` **or** `3` is non-zero, and is released **only when all three are clear**.
-- Configuring an IRQ pin also switches on scanning of the *other* GPIOs (those with `GPIO_FUNC` = `00`, `GPIO_MODE` = 0) and of power events. Nothing is scanned if no IRQ pin exists.
-- Conversely, **when no GPIO is an IRQ pin, all three status registers are cleared** — including by a reset or by entering Download mode, since both reset the GPIO configuration.
-
-The last point is a trap: if you need `IRQ Status 3[1] WAKEUP` after a reset, **do not clear `WAKE_SRC` (`0x05`)** until you have re-armed a GPIO as IRQ, or the wakeup interrupt can never fire **[DS]** §IV.6 "IRQ Attention" 2 / §V.8(4).
-
-### 4.3 Driving NeoPixels resets the I²C peripheral
-
-Setting `IO0` to its mux function makes the firmware **switch the core clock to 24 MHz** for RGB timing, and "switching the clock will reset I²C, so you must wait before communicating; otherwise communication will fail" **[DS]** §VI.2(2)1. During a refresh, interrupts are disabled and **32 LEDs take ≈ 7 ms** with I²C blocked throughout **[DS]** §IV.8. Only `IO0` supports NeoPixel.
-
-### 4.4 Power button semantics
-
-**[DS]** §V.3: **single click = reset, double click = power off, long press = enter Download mode**, with the intervals set by `BTN_CFG_1`. Both destructive behaviours can be disabled (`SINGLE_RESET_DIS`, `DOUBLE_POWEROFF_DIS`), and when they are, the same gesture instead raises an interrupt in `IRQ Status 3` **[DS]** §IV.6(3).
-
-On power-off the 3.3 V DC/DC and `LED_EN` go off but **charging is unaffected** **[DS]** §V.3(1).
-
-### 4.5 Low-voltage protection latches
-
-When neither 5VIN nor 5VINOUT is present and the battery falls below `BATT_LVP`, the system powers off automatically. To leave the low-voltage standby loop, the battery must exceed **`BATT_LVP` + 100 mV** — or 5VIN/5VINOUT must be inserted **[DS]** §V.5, §IV.1(9).
-
-Related trap: **with charging enabled and no battery fitted, the battery ADC floats** and power-source detection becomes unstable. The manual recommends disabling charging when no battery is present **[DS]** §IV.1(5) note 2.
-
-### 4.6 LED blink codes
-
-`LED_EN` is driven by internal logic and its blink rate is a status indication **[DS]** §V.4(2):
-
-| Pattern | Meaning |
-|---|---|
-| Flashes once | Reset occurred |
-| Flash every **500 ms** | Download mode |
-| Flash every **200 ms** | Button reset disabled **and** a GPIO has IRQ enabled |
-| Flash every **100 ms** | Double-click power-off disabled **and** a GPIO has IRQ enabled |
-
----
-
-## 5. Libraries
-
-| Option | Where | Verdict |
-|---|---|---|
-| **`M5PM1`** — M5Stack's own dual Arduino/ESP-IDF driver | `github.com/m5stack/M5PM1`, ESP-IDF registry `m5stack/m5pm1`, latest **1.0.7**; MIT | ✅ **Use this.** `src/M5PM1.h` is a bilingual annotated copy of the whole register map — 136 KB of it — and is more usable than the PDF **[SRC]** |
-| Raw I²C | — | Viable; the map above is complete. Mind the burst-range limits (§3) |
-| M5Unified | `M5Unified` `Power_Class` | Only partially wraps the part; M5GFX reaches the PMIC directly for the frontlight **[SRC]** `M5GFX/src/M5GFX.cpp:819-856` |
-
-Version pinned by the PaperMono factory firmware: **`m5stack/m5pm1` 1.0.7** **[SRC]** `M5PaperMono-UserDemo/dependencies.lock`.
-
-Representative API surface **[DOC]**:
-
-```
-pm1.begin(&M5.In_I2C, M5PM1_DEFAULT_ADDR, M5PM1_I2C_FREQ_100K)
-pm1.setLdoEnable(bool) / setDcdcEnable(bool) / ldoSetPowerHold(bool)
-pm1.shutdown() / setSingleResetDisable(bool) / setLedEnLevel(bool)
-pm1.timerSet(uint32_t seconds, m5pm1_tim_action_t action)
-pm1.setI2cSleepTime(uint8_t seconds)
-pm1.gpioSetMode / gpioSetPull / gpioSetDrive / gpioSetFunc / gpioSetOutput
-pm1.gpioSetWakeEnable(M5PM1_GPIO_NUM_n, bool)
-pm1.gpioSetWakeEdge(M5PM1_GPIO_NUM_n, M5PM1_GPIO_WAKE_FALLING)
-pm1.analogRead(M5PM1_ADC_CH_n, &v) / readTemperature(...) / readVref(&v)
-pm1.setPwmFrequency(hz) / setPwmDuty(M5PM1_PWM_CH_n, pct, pol, en)
-pm1.setLeds(rgb*, n, count, refresh)
-pm1.irqClearGpioAll / irqClearSysAll / irqClearBtnAll / irqSetGpioMask...
-```
-
----
-
-## 6. ⚠ Pin-numbering: M5PM1 is 0-based and label-matching — its sibling is not
-
-> **This is the single most damaging trap on any board carrying both M5Stack expanders.**
->
-> | Part | Enum | Value | Rule |
-> |---|---|---|---|
-> | **M5PM1** | `M5PM1_GPIO_NUM_3` | **`3`** | 0-based; **label equals value** — **[SRC]** `M5PM1/src/M5PM1.h:404-412`, specifically `M5PM1_GPIO_NUM_3 = 3` at `M5PM1.h:410` |
-> | [**M5IOE1**](../m5ioe1/README.md) | `M5IOE1_PIN_3` | **`2`** | Label is **1**-based, enum value is **0**-based — **[SRC]** `M5IOE1/src/M5IOE1.h:34` |
->
-> Two expanders on the same I²C bus with **different label↔value conventions**. Passing a documentation "`PYGn`" number straight into the M5IOE1 API silently targets pin *n+1*'s neighbour. The M5Stack OTP demo bypasses the M5IOE1 enum entirely and hardcodes raw values with the comment `// M5IOE1 uses zero-based pin indexes.` **[SRC]** `M5PaperMono-OTP-Demo/components/EDP_OTP_LUT_demo/src/EDP_SPI.cpp:36-38`.
->
-> The hazard is not symmetric: M5PM1 code written from the label is correct, M5IOE1 code written from the label is off by one. But the two chips sit side by side in the same vendor documentation, so the reader has to know which convention applies to which part.
-
-A second, related notation hazard: **M5Stack's own documentation applies the `PYGn` prefix to M5PM1 pins, which have no such prefix.** `PYG3_BL_PWM` on the product page denotes **M5PM1 GPIO3**, while `PYG3` in the IO-expander context denotes **M5IOE1 IO3 = e-paper power enable**. Writing to the wrong one cuts power to the display instead of dimming the frontlight. The M5PM1 header contains **no `PYG` identifier at all** **[SRC]** `M5PM1/src/M5PM1.h`; the shipped firmware writes `PM1 G4`, not `PYG4` **[FW]**.
-
----
-
-## 7. Caveats, errata and internal inconsistencies in the manual
-
-| # | Issue | Evidence |
-|---|---|---|
-| **C1** | **PWM channels are numbered inconsistently within the same document.** Table 2 (p. 3) labels the `IO3` mux **`PWM1`** and the `IO4` mux **`PWM2`**; the register map and §IV.4 call the same two channels **`PWM0`** and **`PWM1`**; §VI.4's example maps `M5PM1_PWM_CH_0` → GPIO3 and `M5PM1_PWM_CH_1` → GPIO4. **Take the register/API numbering (0-based) as operative**; the Table 2 column is the outlier | **[DS]** Table 2 vs §IV.4 vs §VI.4; corroborated by **[SRC]** `M5PM1.h` comment "GPIO3 (can be PWM0)" |
-| **C2** | **`PWM0_HC` and `PWM1_HC` both describe themselves as "PWM1 duty cycle high 8 bits"** — and "high 8 bits" is wrong in both cases; the field is `[3:0]`, four bits. Copy-paste defect in the register table | **[DS]** Table 3, p. 8 |
-| **C3** | **The NeoPixel buffer note contradicts the register map.** Table 3 places `NEO_PIXn_L/H` at `0x60–0x9F`, but §IV.10's note says "PIX0_L = 0x36, PIX0_H = 0x37, …, PIX31_H = 0x75". `0x36` is a *reserved* address in the same table. The `0x60–0x9F` range is the one the library uses | **[DS]** Table 3 p. 10 vs §IV.10 p. 25; **[SRC]** `M5PM1.h` `M5PM1_REG_NEO_DATA_START` = `0x60` |
-| **C4** | **The appendix cites register addresses that no longer exist.** The firmware changelog refers to "GPIO_Power_Hold register (**0x33**)", "IRQ Status 3 (**0x23**)", "BTN_CFG_2 (**0x31**)" and repeatedly to "WAKE_SRC (**0x2F**)". In the current map these are `0x07`, `0x42`, `0x4A` and `0x05`. The addresses moved at `HW:5 / SW:6` ("Updated the register map") and the historical entries were not renumbered. **Use Table 3, not the appendix** | **[DS]** pp. 32–33 vs Table 3; the `0x2F` reference also leaks into §IV.6(3) on p. 21 |
-| **C5** | **`SW_REV` default disagrees with the changelog.** Table 3 gives `SW_REV` default `0x06` (firmware V6, doc V1.7, 2025-12-13), but the latest changelog entry is `HW:5 / SW:S` (2026-01-06) — firmware version "S" as ASCII. The register-map default was not updated. **Read `0x03` from the device rather than assuming either** | **[DS]** Table 3 p. 4 vs appendix p. 33 |
-| **C6** | **§V.1(2) lists "5VOUT" twice and never 5VIN**, so one of the three internal ADC channel descriptions is mislabelled | **[DS]** p. 26 |
-| **C7** | **`I2C_CFG` bit `[7:5]` is called `DBL` in §IV.1(10)** but `Reserved` in Table 3. `DBL` is the `BTN_CFG_1` field name — a copy-paste from the button section | **[DS]** Table 3 p. 5 vs §IV.1(10) p. 14 |
-| **C8** | **`IRQ Status 2[3]` "5VINOUT Remove" and `[2]` "5VINOUT Add" carry identical threshold text** ("voltage ≤ 2400 mV → > 2400 mV") in both the status and mask sections, so the Remove condition is printed backwards. §V.8's power-event list gives the correct Remove condition (`≥ 2400 mV → < 2400 mV`) | **[DS]** §IV.6(2)/(5) pp. 21–22 vs §V.8(3) p. 28 |
-| **C9** | **No electrical specification whatsoever.** No V<sub>CC</sub> range, no absolute maximum ratings, no I/O drive strength, no quiescent current, no timing. The only limit stated anywhere is the 3.3 V ADC input ceiling. This is a real gap for anyone designing with the part rather than merely programming a fitted one | **[DS]** whole document |
-| **C10** | **`5VOUT` is bidirectional and mis-sequencing it is a hardware hazard.** "Before enabling the 5VOUT boost, the 5VOUT voltage must be detected first to ensure there is no external power input; otherwise it should remain in input mode." Enabling a boost converter into an externally driven rail is exactly the kind of thing that damages parts | **[DS]** §V.1(2) *Attention* 1 |
-
-Additionally: the **M5PM1 library's LICENSE is dated 2025** while every other PaperMono repository is dated 2026, which is consistent with the part predating this board and being reused across M5Stack products **[SRC]**; `product_i2c_addr` on `docs.m5stack.com` lists `M5PM1 (0x6e)` for the **StickS3 (K150)**, independently confirming the address on a different product **[DOC]**.
-
----
-
-## 8. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — designator `U7`, sheet 2
-
-The M5PM1 is the **only always-on active device** on the board. It sits on rail `L0` (straight off the battery, alongside the RTC) and every other rail exists downstream of a pin it controls. Consequences for the board specifically:
-
-| Role on PaperMono | Pin / register | Evidence |
-|---|---|---|
-| System I²C slave at `0x6E`, on the shared internal bus **GPIO47 = SDA, GPIO48 = SCL**, brought up at 100 kHz | pins 8/9 → `G47_SYS_SDA` / `G48_SYS_SCL` | **[SCH]** `U7`.8, `U7`.9; **[SRC]** `hal_board.cpp:13,15` |
-| **`L1` rail enable** (powers the BMI270 IMU) | pin 18 `LDO_3V3_EN` → `3V3_L1_EN`; `pm1.setLdoEnable()` | **[SCH]** `U7`.18; **[DOC]** |
-| **`L2`/`L3A` rail enable** (powers the ESP32-S3, LoRa, NFC, the M5IOE1 itself, button pull-ups, touch INT, buzzer, RGB red) | pin 14 `DCDC_3V3_EN` → `3V3_L2_EN`; `pm1.setDcdcEnable()` | **[SCH]** `U7`.14; **[DOC]** |
-| **Battery charge enable** to the AW32901/IP2315 charging path | pin 2 `CHG_EN` | **[SCH]** `U7`.2; **[SCH]** sheet 1 power-tree block |
-| **Battery / 5 V-in / 5 V-out monitoring**, and the battery-sampling enable | pins 11, 16, 19, and pin 1 `BAT_ADC_EN` | **[SCH]** `U7`.1/.11/.16/.19 |
-| **ESP32-S3 `BOOT` strap**, open-drain | pin 15 `BOOT_OUT` → net `G0_BOOT_OUT` → ESP32-S3 `GPIO0[strap]` | **[SCH]** `U7`.15 and sheet 1 I/O map. ⚠ **Not exercised by the factory firmware** — `grep -rE 'GPIO_NUM_0\b' main/` returns only `M5PM1_GPIO_NUM_0` hits **[SRC]**, so this net's behaviour is documented but unverified |
-| **Power button**, the board's single multi-function ON/OFF/RESET/BOOT control | pin 7 `PWR_BTN` | **[SCH]** `U7`.7 |
-| **Red channel of the status LED** | pin 5 `LED_EN` → `PY_LED_R` | **[SCH]** `U7`.5. Green/blue come from the M5IOE1 instead |
-| `IO0` = **RX8130CE RTC interrupt**, used as a wake source (falling edge) | `PYG0_RTC_INT` | **[SCH]** `U7`.3; **[SRC]** `app_sleep_wake.cpp:67`; **[FW]** `PM1 shutdown, wake by RX8130 timer -> PM1 G0 falling edge` |
-| `IO1` = **IRQ output toward the host**, wired to ESP32-S3 **GPIO1** | `G1_PY_IRQ` | **[SCH]** `U7`.17; **[SRC]** `app_sleep_wake.cpp:46,69` |
-| `IO2` = **LoRa module power enable** (gates `3V3_L2_LoRa`) | `PYG2_LoRa_EN` | **[SCH]** `U7`.20; **[SRC]** `hal_lora.cpp:29` |
-| `IO3` = **frontlight PWM** (PWM0), 5 kHz, gamma-squared brightness curve | `PYG3_BL_PWM` | **[SCH]** `U7`.13; **[SRC]** `M5GFX/src/M5GFX.cpp:826-853` |
-| `IO4` = **BMI270 IMU interrupt**, wake source, **active-low / falling edge** | `PYG4_IMU_INT` | **[SCH]** `U7`.12; **[SRC]** `app_sleep_wake.cpp:68`; **[FW]** `PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge` |
-
-How M5GFX programs the frontlight, exactly **[SRC]** `M5GFX/src/M5GFX.cpp:819-856`:
-
-| Step | Register | Value | Meaning | Line |
-|---|---|---|---|---|
-| Clear `GPIO_DRV` bit 3 | `0x13` | `bitOff 1<<3` | GPIO3 → **push-pull** (mandatory, see §2 note) | 826 |
-| Set `GPIO_FUNC0` | `0x16` | `bitOn 0xC0` | GPIO3 `[7:6]` → `11` = mux (PWM) | 829 |
-| Set `PWM_FREQ_L/H` | `0x34`/`0x35` | 5000 | **5 kHz** | 833–836 |
-| Brightness off | `0x31` | `0` | disable | 845 |
-| Brightness on | `0x30`, `0x31` | `br = brightness²`, `(br>>4)&0xFF`, `(br>>12)\|0x10` | squared/gamma duty; `0x10` is the `EN` bit | 850–853 |
-
-A linear brightness write sits commented out at `M5GFX.cpp:847`, superseded by the squared curve. Note the driver never reads `VREF`, never checks `PWR_SRC`, and never surfaces `IRQ Status 2`'s battery-insert/remove events.
-
-**Not verified on this board:** `BOOT_OUT` (above); the NeoPixel mux on `IO0` (used as an RTC interrupt input instead); the `AW8737A` pulse register; the ADC channels on `IO1`/`IO2` (both used as digital lines).
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md)
-
-**Same part, same designator, same wiring** — the Lite drops NFC and LoRa but keeps the entire power tree. `IO2` still drives `PYG2_LoRa_EN` in the shared schematic naming; whether the net is populated on the Lite board is not established here, because M5Stack publishes a 4-sheet `PRJ` PDF for the Lite rather than the 6-sheet `SCH` **[DOC]**.
-
----
-
-## 9. Related components
-
-- [**M5IOE1**](../m5ioe1/README.md) — the sibling custom expander, same publisher, same PY32 lineage, **different pin-numbering convention** (§6)
-- `components/puya/py32l020f15u6/` — the underlying MCU. *Record pending; not yet written at the time of this pass.* Consult it for absolute maximum ratings, supply range and I/O characteristics, none of which the M5PM1 manual provides
-- [**Semtech SX1262**](../../semtech/sx1262/README.md) — powered through `IO2`
-- [**M5Stack Stamp-LoRa-1262**](../stamp-lora-1262/README.md) — the module carrying that SX1262
-- [Vendor sourcing guides index](../../../vendors/README.md) — no M5Stack chip-documentation guide exists yet; the M5PM1/M5IOE1 manuals are reachable only from the product pages' *Datasheets* list and from `docs/` inside the driver repositories
-
----
-
-## 10. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/m5pm1-chip-user-manual-v1.9-en.pdf` | 814 731 | `c6daffd0ab89d8de50c0a19f35f94321bc6c9511ad017dd242a3e765d88a96b6` | **M5PM1 Chip User Manual V1.9**, 33 pp., English. PDF metadata: Author `洋 熊`, Creator/Producer `Microsoft® Word 2021`, created **2026-05-22**. Text layer validated against the rendered page headings before any value here was transcribed |
-
-**Text-layer validation.** `pdftotext -layout` output was cross-checked against the document's own running headers (`M5PM1 Chip User Manual`), footers (`n / 33`, `The Innovator of Modular IoT Development Platform | M5Stack`) and section numbering before transcription. No glyph-subsetting or code-point-offset corruption was observed. Some cells retain untranslated Chinese (`低 8 bit`, `电池移除`, `唤醒源二选一`), which is a property of the source document, not of the extraction.
-
-**A Chinese-language edition exists and was not retrieved.** The `zh_CN` product page links `1207/M5PM1_Datasheet_CN.pdf` where the `en`/`ja` pages link `M5PM1_Datasheet_EN.pdf` **[DOC]**. Since these two are the only vendor documentation of this part at all, a CN↔EN diff is the highest-value untaken lead — it would likely settle the nomenclature inconsistencies in §7. Recorded as an open item rather than a gap.
-
-**Licence.** M5Stack copyright, no licence statement on the document. Redistribution status **`unknown`**; disposition `repository`. The driver library that ships the same PDF in `docs/` is MIT, but that licence covers the code, not the manual.
-
----
-
-## 11. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | M5PM1 Chip User Manual | **M5Stack** (imprint: Shenzhen Mingzhan Information Technology Co., Ltd.) | primary | chip manual | `artifacts/m5pm1-chip-user-manual-v1.9-en.pdf`; upstream `static-cdn.m5stack.com/resource/docs/products/core/PaperMono/1207/M5PM1_Datasheet_EN.pdf` | 2026-09-01 | **V1.9, 2026-01-22** | §1–§5, §7 |
-| S-2 | PaperMono schematic | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | **V0.6.2, 2026-05-22**, 6 sheets | §1 silicon identity (sheet 1), §2 pin table (sheet 2 `U7`), §8 wiring |
-| S-3 | `M5PM1` Arduino/ESP-IDF driver | M5Stack | primary | source | `github.com/m5stack/M5PM1` @ `be9a5456c007c333e7ac963f33bfde1ffa5d82ee` | 2026-09-01 | tag **1.0.7**, MIT | §3 symbol names, §6 enum values |
-| S-4 | `M5PaperMono-UserDemo` factory firmware source | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-UserDemo` @ `c1099107271d31a0678d661a896e2b04dbb331ea` | 2026-09-01 | 2026-08-10, MIT | §8 board roles |
-| S-5 | `M5GFX` | M5Stack | primary | source | `github.com/m5stack/M5GFX`, `master` @ `d91077b9a607b59404e4e4a49f775c792bfae382` | 2026-09-01 | release 0.2.28 | §8 frontlight sequence |
-| S-6 | PaperMono product page + `arduino/papermono/m5pm1_m5ioe1` API page | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono`, `docs.m5stack.com/en/arduino/papermono/m5pm1_m5ioe1` | 2026-09-01 | undated | §5 API surface, §6 notation hazard, §8 power tree |
-| S-7 | `C153-PaperMono-ESP32S3R8-UserDemo-V1.2` firmware image | M5Stack via M5Burner | primary | binary | firmware id `2089640807996628993`, SHA-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | 2026-09-01 | v1.2, built 2026-08-06, IDF v5.5.1 | §6, §8 wake-source strings |
-| S-8 | `product_i2c_addr` reference table | M5Stack | primary | vendor docs | `docs.m5stack.com/en/product_i2c_addr` | 2026-09-01 | undated | §7 — independent `0x6E` confirmation via StickS3 (K150); **negative result:** PaperMono itself is absent from this table |
diff --git a/components/m5stack/m5pm1/artifacts/m5pm1-chip-user-manual-v1.9-en.pdf b/components/m5stack/m5pm1/artifacts/m5pm1-chip-user-manual-v1.9-en.pdf
deleted file mode 100644
index ccb2a68..0000000
Binary files a/components/m5stack/m5pm1/artifacts/m5pm1-chip-user-manual-v1.9-en.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-lora-1262/README.md b/components/m5stack/stamp-lora-1262/README.md
deleted file mode 100644
index 6da3385..0000000
--- a/components/m5stack/stamp-lora-1262/README.md
+++ /dev/null
@@ -1,316 +0,0 @@
-# M5Stack Stamp-LoRa-1262
-
-> **Common guide:** [`guides/lora`](../../../guides/lora/README.md) — the device-independent LoRa material (the module-independent LoRa material: modulation trade-offs, band plans, SX126x interface pitfalls and RadioLib). This record covers the part; that guide covers the domain.
-
-- **Category:** LoRa transceiver **module** — a carrier for a [Semtech SX1262](../../semtech/sx1262/README.md) sub-GHz radio, presented to the host as a 13-pin SPI + control interface
-- **Scope of this record:** **module level only.** Radio architecture, register map, modem configuration, RF characteristics and errata belong to the SX1262 and are documented in [`components/semtech/sx1262/`](../../semtech/sx1262/README.md). This record covers the module's pinout, supply, control lines and how the PaperMono drives it.
-- **Research status:** ⚠ **No module datasheet was located.** M5Stack publishes the *chip* datasheet (`DS_SX1261_2_V2-2`) and nothing module-specific. Everything below comes from the PaperMono schematic symbol, the vendor pin map and the firmware — not from a module specification.
-- **Retrieved:** 2026-09-01
-
-The LoRa radio of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153). **The PaperMono-Lite does not fit it** — that is one of the two hardware differences between the SKUs.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[SCH]** | Read out of `PaperMono_SCH_V0.6.2_20260522.pdf`, cited as sheet + designator + pin | `executed-success` for the extraction (PDF text-position parsed, all 13 pin pads enumerated); `not-tested` electrically |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | `docs.m5stack.com` / `shop.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference | `inferred` |
-
-**No pin below was guessed.** Pins 11–13 carry no printed name and no net label on the schematic symbol; that is stated as such rather than filled in (§2.1).
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Schematic symbol name | **`Stamp-LoRa-1262-mini`** | **[SCH]** sheet 4, symbol body at the `U14` footprint |
-| Name in vendor documentation | **`Stamp LoRa-1262`** | **[DOC]** PaperMono PinMap and specification table |
-| Reference designator | **`U14`**, sheet 4 | **[SCH]** |
-| Pin count | **13** — pads `PIU1401` … `PIU14013` | **[SCH]**, full pad census |
-| Radio inside | **Semtech SX1262** | **[DOC]** specification row: `SX1262 (Stamp LoRa-1262), 868–923 MHz, FPC ant.`; corroborated by the module's own pin names `SX_NRST`, `SX_NSS`, `SX_BUSY`, `SX_ANT_SW` **[SCH]** |
-| Frequency range advertised | **868 MHz – 923 MHz**, single SKU | **[DOC]** |
-| Antenna | **FPC antenna**, per the specification row. The antenna net was **not traced** in this pass | **[DOC]**; **[INF]** for the gap |
-| Supply | **3.3 V** on `VIN_3V3` (pin 5), fed from the switched rail `3V3_L2_LoRa` | **[SCH]** `U14`.5 |
-| Host interface | **SPI** (`SPI_MOSI`, `SPI_MISO`, `SPI_CLK`, `SX_NSS`) + `SX_BUSY`, `LORA_IRQ`, `SX_NRST`, `SX_ANT_SW` | **[SCH]** |
-| ⚠ Marking verified? | **No.** No teardown photograph of `U14` was inspected. The module identity rests on the schematic symbol name and the vendor specification row, both primary M5Stack documents but neither a photograph | **[INF]** |
-| ⚠ Naming variance | The schematic says `Stamp-LoRa-1262-**mini**`; the documentation says `Stamp LoRa-1262` with no suffix. Whether `-mini` denotes a distinct variant or is merely the symbol's library name is **not established** — no M5Stack catalogue entry for either exact string was confirmed in this pass | **[SCH]** vs **[DOC]** |
-
----
-
-## 2. Pin table
-
-All 13 pin pads on the `U14` symbol were enumerated from the schematic's text-position layer and matched to their printed names and adjacent net labels by coordinate. **[SCH]** sheet 4.
-
-| Pin | Module pin name | Direction (module view) | PaperMono net | Connects to |
-|---:|---|---|---|---|
-| **1** | `GND` | — | `GND` | Ground |
-| **2** | `SX_NRST` | I | `PYB_LoRa_RST` | **[M5IOE1](../m5ioe1/README.md) `IO10`** — *not* an ESP32 pin |
-| **3** | `SX_BUSY` | O | `G21_LoRa_BUSY` | ESP32-S3 **GPIO21** |
-| **4** | `LORA_IRQ` | O | `G5_LoRa_INT` | ESP32-S3 **GPIO5** |
-| **5** | `VIN_3V3` | P | `3V3_L2_LoRa` | Switched 3.3 V rail, gated by **[M5PM1](../m5pm1/README.md) `IO2`** |
-| **6** | `SPI_CLK` | I | `G39_SPI1_CLK` | ESP32-S3 **GPIO39** |
-| **7** | `SPI_MOSI` | I | `G38_SPI1_MOSI` | ESP32-S3 **GPIO38** |
-| **8** | `SPI_MISO` | O | `G40_SPI1_MISO` | ESP32-S3 **GPIO40** |
-| **9** | `SX_NSS` | I | `G41_LoRa_NSS` | ESP32-S3 **GPIO41** |
-| **10** | `SX_ANT_SW` | I | `PYB_LoRa_ANT_SW` | **[M5IOE1](../m5ioe1/README.md) `IO2`** |
-| **11** | *(no printed name)* | — | *(no net label)* | see §2.1 |
-| **12** | *(no printed name)* | — | *(no net label)* | see §2.1 |
-| **13** | *(no printed name)* | — | *(no net label)* | see §2.1 |
-
-Local decoupling: `C65`, **10 µF / 10 V**, adjacent to pin 5 **[SCH]**.
-
-### 2.1 Pins 11–13: unlabelled, not proven no-connect
-
-The pads `PIU14011`, `PIU14012` and `PIU14013` **exist on the symbol** and carry their pin numbers (13, 12, 11 top-to-bottom on the right-hand side of the symbol). They have:
-
-- **no printed pin name** inside the symbol body, and
-- **no net label** adjacent to them.
-
-The SKILL's rule applies: *a drawn no-connect marker is a positive assertion; a blank cell is merely unknown*. **No `NC` glyph was found at those coordinates**, so these three pins are **unlabelled and apparently unrouted** — which is *not* the same as documented no-connects. They may be spare module GPIOs, factory-test pads, or genuinely absent from this module variant. **Unresolved**; a module datasheet or a photograph of the footprint would settle it.
-
----
-
-## 3. Interface summary
-
-### 3.1 SPI
-
-Four-wire SPI on a bus the module does not share with anything else on this board: MOSI/MISO/CLK/NSS on ESP32-S3 GPIO 38 / 40 / 39 / 41 **[SCH]**, **[SRC]** `M5PaperMono-UserDemo/main/hal/hal_lora.cpp:23-26`. The e-paper uses a separate SPI host (SPI2 on GPIO 14/15/16/17), so there is **no chip-select arbitration** between display and radio.
-
-SPI mode, clock rate and frame format are **not** fixed by the module — they are properties of the SX1262 and of RadioLib's configuration. See the [SX1262 record](../../semtech/sx1262/README.md).
-
-### 3.2 `BUSY`
-
-Pin 3, to GPIO21. On the SX1262 this is a mandatory handshake line, not an optional status output: the host must wait for it to fall before issuing most commands. Any driver that ignores it will intermittently lose commands. `not-tested` here; the constraint is the chip's, documented in the SX1262 record.
-
-### 3.3 `LORA_IRQ` is the SX1262's `DIO1`
-
-The module labels pin 4 `LORA_IRQ`; the docs call the net `LORA_IRQ`; **the firmware names the same line `LORA_DIO1_PIN`** **[SRC]** `hal_lora.cpp:27`. So the module brings out **DIO1** specifically — not a wired-OR of all DIO pins, and not DIO2 or DIO3. That matters, because on the SX1262 DIO2 can be repurposed as an RF switch control and DIO3 as a TCXO supply; whichever of those the module uses internally is **not visible from outside** and is not documented anywhere located in this pass.
-
-The same GPIO5 line is registered as an ESP32-S3 **wake source** **[SRC]** `app_sleep_wake.cpp:44`, so a LoRa packet can wake the board.
-
-### 3.4 `SX_NRST` and `SX_ANT_SW` are behind the I²C expander
-
-Neither reset nor the antenna switch is an ESP32 pin. Both go to the [M5IOE1](../m5ioe1/README.md):
-
-| Line | Module pin | M5IOE1 pin | Enum (⚠ value ≠ label) | Source |
-|---|---:|---|---|---|
-| `SX_NRST` | **2** | `IO10` | `M5IOE1_PIN_10` = **`9`** | **[SRC]** `hal_lora.cpp:30` |
-| `SX_ANT_SW` | **10** | `IO2` | `M5IOE1_PIN_2` = **`1`** | **[SRC]** `hal_lora.cpp:31` |
-
-> ⚠ Mind the **two** numbering traps colliding here: the *module* pin numbers and the *expander* pin numbers are unrelated (module pin 2 → expander `IO10`; module pin 10 → expander `IO2` — very nearly a transposition), and the expander's enum value is one less than its label. See [M5IOE1 §6](../m5ioe1/README.md#6--the-m5ioe1_pin_n--n--1-off-by-one).
-
-**Consequence:** you cannot reset the radio, and cannot switch the antenna path, without a working I²C bus and a working M5IOE1. On a board where the same expander also gates the display's reset and power, an I²C fault takes down radio and screen together.
-
-### 3.5 Power gating
-
-`VIN_3V3` (pin 5) sits on `3V3_L2_LoRa`, a rail enabled by **M5PM1 `IO2`** — `PYG2_LoRa_EN` on the schematic **[SCH]** sheet 1 power map, `U7`.20; **[SRC]** `hal_lora.cpp:29`, `app_sleep_wake.cpp:70`.
-
-So the module has a **hard power cut** available, independent of the SX1262's own sleep modes. Bring-up order matters: enable the M5PM1 rail, then release `SX_NRST` through the M5IOE1, then talk SPI. Nothing in the vendor documentation states this ordering explicitly — it follows from the wiring. **[INF]**
-
----
-
-## 4. Software
-
-| Item | Value | Evidence |
-|---|---|---|
-| **Driver** | **RadioLib** (jgromes) | **[SRC]**, **[DOC]** |
-| **Version pinned by the factory firmware** | **`7.2.1`**, commit `b91c6af112e423dcb14529ade5827802a14e1015` | **[SRC]** `M5PaperMono-UserDemo/repos.json` |
-| Local modification | **Patched**, and the patch **removes `idf_component.yml`** so it builds as a plain component rather than a managed one | **[SRC]** `repos.json` `patched: yes, + removes idf_component.yml` |
-| Version in the published PlatformIO config | **Unpinned** — `RadioLib = https://github.com/jgromes/RadioLib` | **[DOC]** |
-| Upstream licence | RadioLib is **LGPL-3.0** upstream, while the M5Stack demo carrying it is MIT. **Not verified in this pass** — flagged, not confirmed | **[INF]**, `not-tested` |
-
-> ⚠ **The docs' unpinned dependency and the firmware's pinned commit are not the same thing.** Building from the published PlatformIO snippet pulls RadioLib `master`, not `7.2.1`. If you are trying to reproduce factory behaviour, use the pinned commit. **[SRC]** vs **[DOC]**.
-
-There is **no M5Stack-specific LoRa library** for this module. `hal_lora.cpp` in the UserDemo is a thin wrapper that hands the six pin numbers to RadioLib and gets out of the way **[SRC]**.
-
-Framework context: ESP-IDF **5.5.1**, target `esp32s3`, arduino-esp32 **3.3.10** as a managed component **[SRC]** `dependencies.lock`.
-
----
-
-## 5. Caveats and gaps
-
-| # | Issue | Evidence |
-|---|---|---|
-| **G1** | **⚠ No module datasheet exists in this repository, and none was located.** M5Stack's *Datasheets* list for the PaperMono links the **Semtech chip** datasheet (`DS_SX1261_2_V2-2`), not a module document. Nothing states the module's supply current, its RF output power at the connector, its antenna interface, its internal matching network, whether it fits a TCXO or a crystal, which DIO pins are consumed internally, or what pins 11–13 are | **[DOC]**; the absence is `executed-success` — the full datasheet list was enumerated |
-| **G2** | **Pins 11–13 are unlabelled with no drawn no-connect.** §2.1. Unresolved | **[SCH]** |
-| **G3** | **TCXO vs XTAL is unknown, and it changes the driver setup.** The SX1262 needs `DIO3` configured as a TCXO supply *if* a TCXO is fitted, and getting this wrong produces a radio that appears to initialise and then fails to transmit or receive. The module does not expose `DIO3`, so the decision was made inside the module — but no document says which. **Do not guess:** check what RadioLib's PaperMono configuration does before changing it | **[INF]**; the SX1262 record covers the mechanism |
-| **G4** | **`SX_ANT_SW` semantics are undocumented.** Whether it selects TX/RX paths, enables an external PA/LNA, or switches between antenna connectors is not stated anywhere located. `hal_lora.cpp:31` only assigns the pin | **[SRC]** |
-| **G5** | **No regulatory identifier of any kind.** `docs.m5stack.com/en/certification` returns **0 matches** for `PaperMono` and **0** for `C153`; no FCC ID, CE, IC, RCM or TELEC/MIC identifier appears on any of the 13 documentation pages, either product page, or either store listing. A **single wideband SKU spanning 868–923 MHz** covers EU 868, US 915 and JP 920 allocations with no per-region variant. Worth flagging for anyone intending to deploy the radio | **[DOC]** — negative result, `executed-success` (full-text search of a 382 669-byte page fetched HTTP 200) |
-| **G6** | **The `-mini` suffix is unexplained.** §1 | **[SCH]** vs **[DOC]** |
-| **G7** | **PDF extraction artifact worth knowing.** In the schematic's net-annotation layer, underscores render as the digit `0` — `G41_LoRa_NSS` appears as `NLG410LoRa0NSS`, `PYB_LoRa_ANT_SW` as `oRa0ANT0SW`. The **visible** net labels are correct; only the hidden annotation strings are affected. Any future automated netlist extraction from this PDF must account for it or it will produce plausible-looking wrong net names | `executed-success` — observed directly in the text-position dump of sheet 4 |
-
----
-
-## 6. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — designator `U14`, sheet 4
-
-The only LoRa radio on the board, and one of the two features that distinguish the PaperMono from the PaperMono-Lite (the other is NFC). Priced at a **USD 10.00** delta for both together **[DOC]**.
-
-Complete host-side wiring, all confirmed by two independent sources (schematic + firmware) except where noted:
-
-| Function | Module pin | Host | Evidence |
-|---|---:|---|---|
-| SPI MOSI | 7 | ESP32-S3 **GPIO38** | **[SCH]** `U14`.7; **[SRC]** `hal_lora.cpp:25` |
-| SPI MISO | 8 | ESP32-S3 **GPIO40** | **[SCH]** `U14`.8; **[SRC]** `hal_lora.cpp:24` |
-| SPI CLK | 6 | ESP32-S3 **GPIO39** | **[SCH]** `U14`.6; **[SRC]** `hal_lora.cpp:23` |
-| SPI NSS | 9 | ESP32-S3 **GPIO41** | **[SCH]** `U14`.9; **[SRC]** `hal_lora.cpp:26` |
-| BUSY | 3 | ESP32-S3 **GPIO21** | **[SCH]** `U14`.3; **[SRC]** `hal_lora.cpp:28` |
-| IRQ (**DIO1**) | 4 | ESP32-S3 **GPIO5**, also an **ESP32 wake source** | **[SCH]** `U14`.4; **[SRC]** `hal_lora.cpp:27`, `app_sleep_wake.cpp:44` |
-| `NRST` | 2 | **M5IOE1 `IO10`** (`M5IOE1_PIN_10` = value `9`) | **[SCH]** `U14`.2; **[SRC]** `hal_lora.cpp:30` |
-| `ANT_SW` | 10 | **M5IOE1 `IO2`** (`M5IOE1_PIN_2` = value `1`) | **[SCH]** `U14`.10; **[SRC]** `hal_lora.cpp:31` |
-| Power enable | 5 (`VIN_3V3`) | Rail `3V3_L2_LoRa`, gated by **M5PM1 `IO2`** | **[SCH]** `U14`.5, `U7`.20; **[SRC]** `hal_lora.cpp:29` |
-
-Board-level notes:
-
-- **The LoRa rail is on the `L2` power level**, alongside the ESP32-S3, NFC, the M5IOE1 and the buzzer **[DOC]** power-tree table. It is not part of `L3B`, so it does not depend on the M5IOE1 for *power* — only for reset and antenna switching.
-- **Bring-up ordering is implied by the wiring, not documented:** M5PM1 `IO2` high → M5IOE1 `IO10` released → SPI. `inferred`.
-- **A LoRa interrupt is a documented ESP32 wake source** on this board (`c.LoRa_INT` in the schematic's wake-source note, sheet 1) **[SCH]**, and the sheet-1 block diagram tags the LoRa block "SX1262; Wake-up support".
-- **No SPI contention with the display.** The e-paper is on SPI2 (GPIO 14–18); the radio is on the separate SPI1 pin group (GPIO 38–41) **[SCH]**, **[SRC]**.
-- The UserDemo ships a **LoRa demo application** among its fifteen apps **[SRC]**, and the Arduino documentation advertises a dedicated `lora` API sub-page (enumerated but **not fetched** in this pass) **[DOC]**.
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) — **not fitted**
-
-The Lite has **no LoRa row in its specification table at all**, no LoRa block in its PinMap, and its PlatformIO `lib_deps` omits `RadioLib` **[DOC]**. Its bill of materials is 2.3 g lighter than the PaperMono's (72.4 g vs 74.7 g product weight), which is consistent with two omitted radios **[DOC]**.
-
-Note that the shared `M5PaperMono-UserDemo` firmware image serves **both** SKUs and detects the variant at runtime by probing the NFC rail, not the radio **[SRC]** `hal_board.cpp:160-172`.
-
-### [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) — designator `M1` · *added 2026-09-04*
-
-A Cardputer-Adv / CardputerZero expansion board, store publish date **2025-12-30**, USD 14.50. Its schematic (V1.1, 2025-10-29, held at [`devices/m5stack/cap-lora-1262/artifacts/schematic/`](../../../devices/m5stack/cap-lora-1262/artifacts/schematic/)) draws the **same 13-pin module** under the same name — and **prints the three pin names that the PaperMono symbol leaves blank**. See §2.2.
-
-| Module pin | Name on the Cap symbol | Net on that board | Host GPIO |
-|---:|---|---|---|
-| 1 | `GND` | `GND` | — |
-| 2 | `NRST` | `RST` | **G3** — an *ordinary host pin*, not an expander |
-| 3 | `BUSY` | `BUSY` | **G6** |
-| 4 | `IRQ` | `IRQ` | **G4** |
-| 5 | `3V3` | `VDD_3V3` from an on-board `JW5712` buck, **no host enable** | — |
-| 6 | `CLK` | `SCK` | **G40** |
-| 7 | `MOSI` | `MOSI` | **G14** |
-| 8 | `MISO` | `MISO` | **G39** |
-| 9 | `NSS` | `NSS` | **G5** |
-| 10 | **`SW`** | `SX_ANT_SW` | **`PI4IOE5V6408` P0 @ I²C 0x43** |
-| 11 | **`GND`** | RF ground | — |
-| 12 | **`ANT`** | → `E4` SMA/RP-SMA connector | — |
-| 13 | **`GND`** | RF ground | — |
-
-Board-level notes:
-
-- **SPI is shared with the host's microSD** (`SDCARD_CS` = G12), unlike the PaperMono where the radio has its own host.
-- **No power gate.** The Cap's buck is enabled by a 10 kΩ pull-up; the module is live whenever the host supplies 5 V.
-- **`SW` is still set once and forgotten** — M5Stack's example and Meshtastic both drive `P0` high at boot and never touch it again, exactly as the PaperMono firmware does with `M5IOE1 IO2`. §5-G4 remains open.
-- **TCXO conflict:** M5Stack's Cap example passes `tcxoVoltage = 3.0` (matching the PaperMono firmware), while **Meshtastic upstream sets `SX126X_DIO3_TCXO_VOLTAGE 1.8`** with `TCXO_OPTIONAL`. Both ship; both are reported working. §5-G3 is therefore *narrowed* (a TCXO is fitted) but **not resolved** (its voltage is disputed).
-- The Cap's predecessor, [**Cap LoRa868 (U201)**](../../../devices/m5stack/cap-lora868/README.md), fits the **"legacy version, standard size"** `Stamp LoRa-1262` and claims **+20 dBm** rather than +22 — so "Mini" is a real variant distinction, not just a library name. That partially answers §5-G6.
-
-### [M5Stack Cap LoRa868 (U201)](../../../devices/m5stack/cap-lora868/README.md) — standard-size variant · *added 2026-09-04*
-
-Same 14-pin host mapping as the U214 (G3/G4/G6/G40/G14/G39/G5), **without** the `PI4IOE5V6408` antenna-switch control and without a Grove pass-through. M5Stack's own comparison table describes the fitted module as *"Stamp LoRa-1262 legacy version, standard size"*. Published 2025-09-05, now **[EOL]**.
-
-### [M5Stack Cardputer Mesh Kit (K152)](../../../devices/m5stack/cardputer-mesh-kit/README.md) · *added 2026-09-04*
-
-Via the bundled Cap LoRa-1262. The kit page links this module's schematic directly.
-
----
-
-## 6A. ⭐ Pins 11–13 are now named — §2.1 partially resolved (2026-09-04)
-
-§2.1 records module pins **11, 12 and 13** as *"unlabelled and apparently unrouted — which is not the same as documented no-connects"*, because the PaperMono schematic symbol prints no names there.
-
-**The Cap LoRa-1262 schematic prints them:**
-
-| Pin | Name on the Cap symbol |
-|---:|---|
-| 11 | **`GND`** |
-| 12 | **`ANT`** |
-| 13 | **`GND`** |
-
-A **ground-signal-ground coplanar RF launch** at the module's antenna edge — which is exactly what a shielded RF module's edge pads should look like, and it explains why the PaperMono (whose antenna is an FPC bonded elsewhere) leaves them unlabelled and unrouted.
-
-**Confidence: `inferred (strong)`, not proven.** The evidence is that both symbols have **13 pins in the same order** with **the same first nine names** (allowing for the PaperMono's `SX_`/`SPI_`/`VIN_` prefixes), both are called `Stamp LoRa-1262 Mini` / `Stamp-LoRa-1262-mini`, and pin 10 is the antenna-switch control on both. What has **not** been done is compare a photograph of either footprint, or read a module datasheet — because none exists (§5-G1).
-
-Also note: pin 10 is `SX_ANT_SW` on the PaperMono symbol and plain **`SW`** on the Cap symbol. Same pin, two names, one undocumented function.
-
----
-
-## 7. Related components
-
-- [**Semtech SX1262**](../../semtech/sx1262/README.md) — **the radio inside this module.** Modem, register map, RF performance, sleep modes, DIO configuration, TCXO handling and errata all live there. Read it for anything below the module's pin boundary
-- [**M5Stack M5IOE1**](../m5ioe1/README.md) — supplies this module's `NRST` (`IO10`) and `ANT_SW` (`IO2`)
-- [**M5Stack M5PM1**](../m5pm1/README.md) — gates this module's 3.3 V supply via `IO2`
-- [Vendor sourcing guides index](../../../vendors/README.md) — no M5Stack module-documentation guide exists yet; **G1** above is exactly the kind of finding one should record
-
----
-
-## 8. Local artifacts
-
-> **Update 2026-09-04: a module-level schematic *was* located.** §5-G1 said no module
-> document existed; that is now **partly wrong**. M5Stack publishes a `Stamp LoRa-1262 Mini`
-> schematic from the **Cap LoRa-1262** and **Cardputer Mesh Kit** documentation pages — not
-> from the PaperMono page, which is why the earlier pass did not find it. It is a
-> *schematic*, not a datasheet: it still does not state RF output at the connector, supply
-> current, the internal matching network, or which SX1262 DIO pins are consumed internally.
-> **G1 is narrowed, not closed.**
-
-| File | Bytes | SHA-256 | Provenance |
-|---|---:|---|---|
-| [`artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf`](artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf) | 184 442 | `6ec29a9240fc8dc41fbe699e74a9f645b9753d7932efc1de28b049fe58e8f03b` | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/NEW-1262-SCH_A1-Lora_2025_08_27_10_58_52.pdf`, retrieved **2026-09-04**, HTTP 200, `%PDF-1.4`. Filename encodes rev **A1**, dated **2025-08-27**. Linked from `docs.m5stack.com/en/cap/Cap_LoRa-1262` and `/en/core/Cardputer_Mesh_Kit` as *"Stamp LoRa-1262 Mini Schematics PDF"* |
-
-⚠ **Downloaded and type-verified, but not yet decoded.** A bbox text dump exists
-(`scratch/m5stack-lora-expansions/pdf/Stamp-LoRa-1262-Mini_SCH_A1_20250827/bbox-p1.xml`,
-815 words) but was **not analysed** by the 2026-09-04 pass, whose subject was the Cap boards
-rather than the module. Decoding it should settle §5-G3 (TCXO vs XTAL, and which voltage),
-§5-G4 (`SW` semantics) and much of §5-G1. Licence/redistribution: **unknown**. Disposition:
-**repository, unstaged** pending review.
-
-The relevant primary documents for the parts around it live with their owners:
-
-| Document | Where |
-|---|---|
-| SX1261/2 datasheet V2.2 | [`../../semtech/sx1262/artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf`](../../semtech/sx1262/README.md) |
-| PaperMono schematic V0.6.2 (sheet 4 carries `U14`) | Device tree — `PaperMono_SCH_V0.6.2_20260522.pdf` |
-| Cap LoRa-1262 schematic V1.1 (carries `M1` and names pins 11–13) | [`devices/m5stack/cap-lora-1262/artifacts/schematic/`](../../../devices/m5stack/cap-lora-1262/artifacts/schematic/) |
-
-If a `Stamp-LoRa-1262` module **datasheet** is ever located, it belongs here too.
-
----
-
-## 9. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | PaperMono schematic | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | **V0.6.2, 2026-05-22**, 6 sheets | §1 symbol name, §2 full pin table, §3, §6 |
-| S-2 | PaperMono product page (specification table + PinMap) | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono` | 2026-09-01 | undated | §1 identity and frequency range, §4, §6 |
-| S-3 | PaperMono-Lite product page | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono-Lite` | 2026-09-01 | undated | §6 — **negative result**: no LoRa row, no `RadioLib` |
-| S-4 | `M5PaperMono-UserDemo` — `main/hal/hal_lora.cpp`, `repos.json` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-UserDemo` @ `c1099107271d31a0678d661a896e2b04dbb331ea` | 2026-09-01 | 2026-08-10, MIT | §2, §3, §4, §6 |
-| S-5 | RadioLib | jgromes | third-party | source | `github.com/jgromes/RadioLib` @ `b91c6af112e423dcb14529ade5827802a14e1015` | 2026-09-01 | tag **7.2.1**; upstream licence LGPL-3.0 (**unverified**) | §4 |
-| S-6 | SX1261/2 datasheet | Semtech, mirrored by M5Stack | authorized mirror | datasheet | [`../../semtech/sx1262/README.md`](../../semtech/sx1262/README.md) | 2026-09-01 | V2.2 | §1, §3, §5-G3 |
-| S-7 | Certification index | M5Stack | primary | vendor docs | `docs.m5stack.com/en/certification` | 2026-09-01 | undated | §5-G5 — **negative result**, 0 matches for `PaperMono` / `C153` |
-| S-8 | PaperMono store listing | M5Stack | primary | retail listing | `shop.m5stack.com/products/m5papermono-with-lora-nfc-800x480-3-97-eink-display` | 2026-09-01 | SKU `C153`, USD 65.00, published 2026-08-21 | §6 price delta vs the Lite (USD 55.00) |
-
-## RadioLib licence — resolved 2026-09-02
-
-This record previously flagged "RadioLib is LGPL-3.0 upstream vs MIT on the demo
-— flagged, unverified", and a later pass observed MIT on today's `master` without
-checking the pinned tree.
-
-**Checked at tag `7.2.1`, the version the vendor demo pins.** RadioLib is **MIT**,
-and has been since 2018:
-
-| Evidence @ 7.2.1 | Value |
-|---|---|
-| `license.txt` (root) | "MIT License … Copyright (c) 2018 Jan Gromeš", 1,068 bytes |
-| `library.json` `license` field | `MIT` |
-| Any GPL/LGPL text in the licence file | none |
-| GitHub API repo licence today | MIT |
-
-**The LGPL-3.0 claim was wrong and is withdrawn.** Worth recording *why* it
-survived two passes: an initial probe for a file named `LICENSE` returned 404,
-because the file is `license.txt` — lowercase, `.txt`. A 404 on a guessed
-filename is not evidence of an absent licence, and it was briefly read that way
-here. There is no licence conflict between RadioLib and the MIT-licensed demo.
diff --git a/components/m5stack/stamp-lora-1262/acquisition/manifest.json b/components/m5stack/stamp-lora-1262/acquisition/manifest.json
deleted file mode 100644
index d72e532..0000000
--- a/components/m5stack/stamp-lora-1262/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "components/m5stack/stamp-lora-1262",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AN3WSTAMPLORA1262-9132667",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WSTAMPLORA1262/Test-Report/Antenna-Specification-9132667.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132667",
-    "https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132667.pdf",
-    "https://fccid.io/2AN3WSTAMPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/Test-Report/Antenna-Specification-9132667.pdf"
-   ],
-   "sha256": "d8263843c67437b08c04ea13138872b1c652d3a45f500063dc71c924f34319d7",
-   "bytes": 581354,
-   "destination": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-03-12",
-   "fcc_id": "2AN3WSTAMPLORA1262",
-   "fcc_document_id": "9132667",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Specification",
-   "grant_date": "2026-03-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf",
-   "placeholder": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WSTAMPLORA1262-9132662",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WSTAMPLORA1262/External-Photos/External-Photos-9132662.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132662",
-    "https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132662.pdf",
-    "https://fccid.io/2AN3WSTAMPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/External-Photos/External-Photos-9132662.pdf"
-   ],
-   "sha256": "bdad5d537c9e9c509a61158b54af12d616ef82453466691f265efb442ca03f1c",
-   "bytes": 2286254,
-   "destination": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-03-12",
-   "fcc_id": "2AN3WSTAMPLORA1262",
-   "fcc_document_id": "9132662",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2026-03-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf",
-   "placeholder": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WSTAMPLORA1262-9132663",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WSTAMPLORA1262/Internal-Photos/Internal-Photos-9132663.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132663",
-    "https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132663.pdf",
-    "https://fccid.io/2AN3WSTAMPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/Internal-Photos/Internal-Photos-9132663.pdf"
-   ],
-   "sha256": "edb1d780efb0b73db80e3c00c0745c910c4a3fe542ea5f5964e20df5c08101e7",
-   "bytes": 742637,
-   "destination": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-03-12",
-   "fcc_id": "2AN3WSTAMPLORA1262",
-   "fcc_document_id": "9132663",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2026-03-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WSTAMPLORA1262-9132666",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WSTAMPLORA1262/Label/Label-and-Label-Location-9132666.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132666",
-    "https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132666.pdf",
-    "https://fccid.io/2AN3WSTAMPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/Label/Label-and-Label-Location-9132666.pdf"
-   ],
-   "sha256": "9a0a7b58a7c1e495c13423f46f4b3aba5e908fd98561dcff4d7086f8eb1e7318",
-   "bytes": 502385,
-   "destination": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-label-and-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-03-12",
-   "fcc_id": "2AN3WSTAMPLORA1262",
-   "fcc_document_id": "9132666",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label and Label Location",
-   "grant_date": "2026-03-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WSTAMPLORA1262-9132665",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WSTAMPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9132665.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132665",
-    "https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132665.pdf",
-    "https://fccid.io/2AN3WSTAMPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9132665.pdf"
-   ],
-   "sha256": "c82db2fd40330b2c5e5f54e2a408a8a7ecd6cd9c0f5a428e11841574cd6d3306",
-   "bytes": 345226,
-   "destination": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-03-12",
-   "fcc_id": "2AN3WSTAMPLORA1262",
-   "fcc_document_id": "9132665",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Information",
-   "grant_date": "2026-03-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf",
-   "placeholder": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WSTAMPLORA1262-9132673",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WSTAMPLORA1262/User-Manual/User-Manual-9132673.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132673",
-    "https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132673.pdf",
-    "https://fccid.io/2AN3WSTAMPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/User-Manual/User-Manual-9132673.pdf"
-   ],
-   "sha256": "7f4bb05318f69d0cb801bf93888e74010cc4c21ff6bb99ea0c356ca64534af0a",
-   "bytes": 730607,
-   "destination": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-03-12",
-   "fcc_id": "2AN3WSTAMPLORA1262",
-   "fcc_document_id": "9132673",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2026-03-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf",
-   "placeholder": "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/components/m5stack/stamp-lora-1262/artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf b/components/m5stack/stamp-lora-1262/artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf
deleted file mode 100644
index ccfa752..0000000
Binary files a/components/m5stack/stamp-lora-1262/artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf.ARCHIVED.md b/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 4fec4f5..0000000
--- a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WSTAMPLORA1262-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 581,354 B (0.55 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 581,354 B (0.55 MiB) |
-| SHA-256 | `d8263843c67437b08c04ea13138872b1c652d3a45f500063dc71c924f34319d7` |
-| FCC ID | **`2AN3WSTAMPLORA1262`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 9132667 |
-| Upstream publication date | 2026-03-12 |
-| Grant date | 2026-03-12 |
-| Equipment class | M5Stamp LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WSTAMPLORA1262/Test-Report/Antenna-Specification-9132667.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132667>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132667.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WSTAMPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/Test-Report/Antenna-Specification-9132667.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf" \
-   "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WSTAMPLORA1262/Test-Report/Antenna-Specification-9132667.pdf" -o "2AN3WSTAMPLORA1262-antenna-specification.pdf"
-echo "d8263843c67437b08c04ea13138872b1c652d3a45f500063dc71c924f34319d7  2AN3WSTAMPLORA1262-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf.ARCHIVED.md b/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 4f6698d..0000000
--- a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WSTAMPLORA1262-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 2,286,254 B (2.18 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,286,254 B (2.18 MiB) |
-| SHA-256 | `bdad5d537c9e9c509a61158b54af12d616ef82453466691f265efb442ca03f1c` |
-| FCC ID | **`2AN3WSTAMPLORA1262`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 9132662 |
-| Upstream publication date | 2026-03-12 |
-| Grant date | 2026-03-12 |
-| Equipment class | M5Stamp LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WSTAMPLORA1262/External-Photos/External-Photos-9132662.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132662>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132662.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WSTAMPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/External-Photos/External-Photos-9132662.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf" \
-   "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WSTAMPLORA1262/External-Photos/External-Photos-9132662.pdf" -o "2AN3WSTAMPLORA1262-external-photos.pdf"
-echo "bdad5d537c9e9c509a61158b54af12d616ef82453466691f265efb442ca03f1c  2AN3WSTAMPLORA1262-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-internal-photos.pdf b/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-internal-photos.pdf
deleted file mode 100644
index 670d89c..0000000
Binary files a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-internal-photos.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-label-and-label-location.pdf b/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-label-and-label-location.pdf
deleted file mode 100644
index de7a2fe..0000000
Binary files a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-label-and-label-location.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf.ARCHIVED.md b/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf.ARCHIVED.md
deleted file mode 100644
index 3d13d00..0000000
--- a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WSTAMPLORA1262-rf-exposure-information.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 345,226 B (0.33 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 345,226 B (0.33 MiB) |
-| SHA-256 | `c82db2fd40330b2c5e5f54e2a408a8a7ecd6cd9c0f5a428e11841574cd6d3306` |
-| FCC ID | **`2AN3WSTAMPLORA1262`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Information |
-| FCC document id | 9132665 |
-| Upstream publication date | 2026-03-12 |
-| Grant date | 2026-03-12 |
-| Equipment class | M5Stamp LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WSTAMPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9132665.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132665>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132665.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WSTAMPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9132665.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf" \
-   "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-rf-exposure-information.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WSTAMPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9132665.pdf" -o "2AN3WSTAMPLORA1262-rf-exposure-information.pdf"
-echo "c82db2fd40330b2c5e5f54e2a408a8a7ecd6cd9c0f5a428e11841574cd6d3306  2AN3WSTAMPLORA1262-rf-exposure-information.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf.ARCHIVED.md b/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 665d5b0..0000000
--- a/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WSTAMPLORA1262-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 730,607 B (0.70 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 730,607 B (0.70 MiB) |
-| SHA-256 | `7f4bb05318f69d0cb801bf93888e74010cc4c21ff6bb99ea0c356ca64534af0a` |
-| FCC ID | **`2AN3WSTAMPLORA1262`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 9132673 |
-| Upstream publication date | 2026-03-12 |
-| Grant date | 2026-03-12 |
-| Equipment class | M5Stamp LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WSTAMPLORA1262/User-Manual/User-Manual-9132673.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9132673>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WSTAMPLORA1262/9132673.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WSTAMPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WSTAMPLORA1262/User-Manual/User-Manual-9132673.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf" \
-   "components/m5stack/stamp-lora-1262/artifacts/certification/2AN3WSTAMPLORA1262-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WSTAMPLORA1262/User-Manual/User-Manual-9132673.pdf" -o "2AN3WSTAMPLORA1262-user-manual.pdf"
-echo "7f4bb05318f69d0cb801bf93888e74010cc4c21ff6bb99ea0c356ca64534af0a  2AN3WSTAMPLORA1262-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-lora-1262/artifacts/certification/README.md b/components/m5stack/stamp-lora-1262/artifacts/certification/README.md
deleted file mode 100644
index 39621bf..0000000
--- a/components/m5stack/stamp-lora-1262/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WSTAMPLORA1262`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WSTAMPLORA1262`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2026-03-12** |
-| Equipment class | M5Stamp LoRa-1262, 903-914.9 MHz |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Source page | <https://fccid.io/2AN3WSTAMPLORA1262> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WSTAMPLORA1262-internal-photos.pdf` | 742,637 | `edb1d780efb0b73db80e3c00c0745c910c4a3fe542ea5f5964e20df5c08101e7` | Internal Photos |
-| `2AN3WSTAMPLORA1262-label-and-label-location.pdf` | 502,385 | `9a0a7b58a7c1e495c13423f46f4b3aba5e908fd98561dcff4d7086f8eb1e7318` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WSTAMPLORA1262-antenna-specification.pdf.ARCHIVED.md`](2AN3WSTAMPLORA1262-antenna-specification.pdf.ARCHIVED.md) | 581,354 | Test Report |
-| [`2AN3WSTAMPLORA1262-external-photos.pdf.ARCHIVED.md`](2AN3WSTAMPLORA1262-external-photos.pdf.ARCHIVED.md) | 2,286,254 | External Photos |
-| [`2AN3WSTAMPLORA1262-rf-exposure-information.pdf.ARCHIVED.md`](2AN3WSTAMPLORA1262-rf-exposure-information.pdf.ARCHIVED.md) | 345,226 | RF Exposure Info |
-| [`2AN3WSTAMPLORA1262-user-manual.pdf.ARCHIVED.md`](2AN3WSTAMPLORA1262-user-manual.pdf.ARCHIVED.md) | 730,607 | Users Manual |
-
-Archived total: **4 files, 3.76 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 1.19 MiB** |
-| Archived | **4 files, 3.76 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/components/m5stack/stamp-s3/README.md b/components/m5stack/stamp-s3/README.md
deleted file mode 100644
index 6f2b109..0000000
--- a/components/m5stack/stamp-s3/README.md
+++ /dev/null
@@ -1,257 +0,0 @@
-# M5Stack Stamp-S3
-
-- **Category:** ESP32-S3 **core module** — a castellated/SMD minimum-system board carrying an
-  Espressif ESP32-S3FN8, its own 5 V→3.3 V converter, USB-C, an RGB LED, a user button and a
-  3D chip antenna, breaking out 23 GPIOs.
-- **SKU:** **`S007`** (base SMD module). Header variants: `S007-PIN127` (1.27 mm), `S007-PIN254`
-  (2.54 mm).
-- **Scope of this record:** **module level.** ESP32-S3 silicon architecture, register map, boot
-  ROM, radio and errata belong to the SoC and are documented at
-  [`components/espressif/esp32-s3r8/`](../../espressif/esp32-s3r8/README.md) — with the caveat
-  that this module fits the **FN8** variant (8 MB in-package flash, **no PSRAM**), not the R8.
-- **Successor:** [**Stamp-S3A**](../stamp-s3a/README.md), SKU `S007-V033`. Read that record
-  before assuming a design that works with one works with the other.
-- **Retrieved:** 2026-09-04
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH]** | Read from `Sch_M5StampS3_v0.2.pdf` by parsing the Altium `CO`/`PI`/`NL` marker layer, cited by designator | `executed-success` extraction, `not-tested` electrically |
-| **[DOC]** | <https://docs.m5stack.com/en/core/StampS3>, retrieved 2026-09-04 | `not-tested` |
-| **[SRC]** | Vendor/framework source at a cited `file:line` | `executed-success` read |
-| **[INF]** | Inference, reasoning given | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketed name | **Stamp-S3** (also written *M5StampS3*, *StampS3*) | **[DOC]** |
-| SKU | `S007` | **[DOC]** page header |
-| Documentation | <https://docs.m5stack.com/en/core/StampS3> (HTTP 200) | **[DOC]** |
-| Published schematic | `Sch_M5StampS3_v0.2.pdf` — **board revision v0.2** | **[SCH]** filename + `artifacts/` |
-| SoC | **ESP32-S3FN8** — Xtensa LX7 dual-core @ 240 MHz, **8 MB in-package flash, no PSRAM** | **[DOC]**; **[SCH]** `U1` symbol `ESP32-S3FN8` |
-| DC-DC | **MUN3CAD01-SC** µPOL module (`M2`) | **[DOC]**; **[SCH]** `M2` value text |
-| RGB LED | **WS2812B-2020** ×1 (`U3`), data on **GPIO21** | **[DOC]**; **[SCH]** `U1`.27 → `SK_DIN` |
-| User button | ×1 (`S1`) on **GPIO0** | **[DOC]**; **[SCH]** |
-| Antenna | `ANT1` = **PROANT440** ceramic/chip antenna, "2.4 G 3D antenna" | **[SCH]** value text; **[DOC]** |
-| Broken-out IO | **23**: G0, G1–G15, G39–G44, G46 | **[DOC]** |
-| IO pitch | 2.54 mm **and** 1.27 mm; SMT / DIP / fly-wire | **[DOC]** |
-| Rear LCD FPC | 0.5 mm, **12-pin (`J1`) or 8-pin (`J3`)**, connector `HDGC/0.5K-HX-8PWB/NC` | **[DOC]**; **[SCH]** |
-| Size / weight | **24.0 × 18.0 × 4.7 mm** / 3.0 g | **[DOC]** |
-| Operating temp | 0 – 40 °C | **[DOC]** |
-| Input | 5 V (`VIN_5V` or USB-C) | **[DOC]** |
-
-### Power consumption (vendor-measured, method not published)
-
-| Mode | Supply | Current | Evidence |
-|---|---|---|---|
-| Sleep | USB Type-C | **400.67 µA** | **[DOC]** |
-| Sleep | `VIN_5V` | **310.89 µA** | **[DOC]** |
-| Standby | USB Type-C | **33.04 mA** | **[DOC]** |
-| Standby | `VIN_5V` | **33.56 mA** | **[DOC]** |
-
-These are the numbers the Stamp-S3A improves on by roughly 4.5× (sleep, USB) and 45× (sleep,
-`VIN_5V`). See [Stamp-S3A § Power](../stamp-s3a/README.md#5-power-the-headline-change).
-
----
-
-## 2. Internal architecture (from the v0.2 schematic)
-
-`Sch_M5StampS3_v0.2.pdf`, one sheet, **54 designators with `CO` markers** plus `C26` recovered
-from visible text only (55 total). Full parsed layout:
-[`artifacts/Sch_M5StampS3_v0.2.plaintext-layout.txt`](artifacts/Sch_M5StampS3_v0.2.plaintext-layout.txt).
-
-| Designator | Part / value | Role | Evidence |
-|---|---|---|---|
-| `U1` | **ESP32-S3FN8** | SoC, 57 pads on the symbol | **[SCH]** |
-| `M2` | **MUN3CAD01-SC** | 5 V → 3.3 V µPOL module, 6 pins (EN, GND, VIN, GND, FB, VOUT) | **[SCH]** |
-| `R6` / `R17` | 100 kΩ / 22.1 kΩ | `M2` feedback divider | **[SCH]** |
-| `C21`, `C22` | 10 µF/10 V ×2 | `M2` in/out bulk | **[SCH]** |
-| `U2` | **SGM2578** (second value text `WS4622C-4/TR`) | **Load switch** — VIN=`VDD_3V3`, EN=`DISP_BL`, VOUT→ LCD-FPC backlight rail | **[SCH]** |
-| `U3` | **WS2812** (WS2812B-2020) | RGB LED. **`VDD` = `VDD_3V3`, always powered** | **[SCH]** |
-| `ANT1` | **PROANT440** | 2.4 GHz antenna | **[SCH]** |
-| `L1` 2.2 nH, `C1` 2.2 pF, `C2` 2.0 pF | — | antenna π-match (3 elements) | **[SCH]** |
-| `X1` + `L3` 10 nH, `C9` 10 pF | — | 40 MHz crystal network | **[SCH]** |
-| `J2` | USB Type-C receptacle | `A6/B6` = D+, `DP1/DP2`, `VCC` | **[SCH]** |
-| `R1`, `R2` | 5.1 kΩ/1 % ×2 | USB-C CC pull-downs | **[SCH]** |
-| `F1`, `D14`, `JP3` (`Type-A`) | — | USB protection / ESD | **[SCH]** |
-| `S1` | tactile `BTN-USER` | GPIO0 boot/user button | **[SCH]** |
-| `D6` | 1N4148WT | on `ESP_EN` | **[SCH]** |
-| `R7` 10 kΩ, `R16` 100 kΩ, `C23` 1 µF | — | `ESP_EN` RC / pull-up | **[SCH]** |
-| `R3` | 10 kΩ/1 % | on GPIO2 | **[SCH]** |
-| `R4` 10 kΩ, `R5` | — | strapping / GPIO42-41 network | **[SCH]** |
-| `M1` | header/edge symbol | module pin field, `GPIO1`… | **[SCH]** |
-| `J1` | 12-pin 0.5 mm FPC | rear LCD option A | **[SCH]** |
-| `J3` | 8-pin 0.5 mm FPC (`HDGC/0.5K-HX-8PWB/NC`) | rear LCD option B | **[SCH]** |
-| `JP1`, `JP2`, `JP4`, `PHD1`, `L5`, `D1`–`D4`, `C3`–`C14`, `C17` | — | jumpers, mounting, decoupling | **[SCH]** |
-
-### Internal-only GPIOs — the ones that are not on the 23-pin list
-
-| ESP32-S3 GPIO | `U1` pad | Net | Goes to | Evidence |
-|---|---|---|---|---|
-| **GPIO21** | 27 | `SK_DIN` | `U3` WS2812B-2020 data in | **[SCH]** |
-| **GPIO33** | 38 | `DISP_RST` | FPC `J1`/`J3` | **[SCH]** |
-| **GPIO34** | 39 | `DISP_RS` | FPC | **[SCH]** |
-| **GPIO35** | 40 | `DISP_MOSI` | FPC | **[SCH]** |
-| **GPIO36** | 41 | `DISP_SCK` | FPC | **[SCH]** |
-| **GPIO37** | 42 | `DISP_CS` | FPC | **[SCH]** |
-| **GPIO38** | 43 | `DISP_BL` | `U2` load-switch **EN** | **[SCH]** |
-
-GPIO33–38 are the pins an ESP32-S3**R8**/**R16V** would spend on octal PSRAM. Because the module
-fits the **FN8** (no PSRAM), M5Stack was free to route them to the rear display header. That is
-the design decision that makes the whole Stamp-S3 family work. **[SCH]** **[INF]**
-
-### Rear LCD FPC pin order (v0.2)
-
-| `J1` (12P) pin | Net | | `J3` (8P) pin | Net |
-|---:|---|---|---:|---|
-| 1 | `VIN_5V` | | 1 | GPIO2 / `VIN`/`VOUT` node |
-| 2 | GPIO18 | | 2 | GPIO3 |
-| 3 | GPIO17 | | 3 | `DISP_RST` |
-| 4 | GPIO16 | | 4 | `DISP_RS` |
-| 5 | (GPIO2 node) | | 5 | `DISP_MOSI` |
-| 6 | GPIO3 | | 6 | `DISP_SCK` |
-| 7 | `DISP_RST` | | 7 | `VDD_3V3` |
-| 8 | `DISP_RS` | | 8 | `DISP_CS` |
-| 9 | `DISP_MOSI` | | | |
-| 10 | `DISP_SCK` | | | |
-| 11 | `VDD_3V3` | | | |
-| 12 | `DISP_CS` | | | |
-
-**[SCH]** — from `PIJ10x` / `PIJ30x` markers. **The Stamp-S3A numbers these connectors in the
-opposite direction for the same net order**; see
-[Stamp-S3A § FPC numbering](../stamp-s3a/README.md#6-the-fpc-numbering-question).
-
----
-
-## 3. Boot, strapping and download mode
-
-- **Download mode:** hold the `G0` button on the module while applying power, release after.
-  **[DOC]**
-- **GPIO46 is pulled down by default** on this module. **[DOC]** ("Additional Notes"). GPIO46 is
-  an ESP32-S3 strapping pin: pulling it high before boot prevents the chip starting.
-- **GPIO0** is pulled up by default and is the boot strap.
-- Consequence for carriers: a board that uses **GPIO46 as an output power latch** — which the
-  [DinMeter](../../../devices/m5stack/dinmeter/README.md) does — is relying on the pin being low
-  at reset and only driven high by firmware afterwards. That is safe by construction here, but
-  it is the reason you must never fit an external pull-up on GPIO46.
-
----
-
-## 4. Software support
-
-| Framework | Identifier | Evidence |
-|---|---|---|
-| Arduino / M5Unified | `board_t::board_M5StampS3` | **[SRC]** `M5Unified/src/M5Unified.cpp:93, 242, 2392, 3484` |
-| M5Unified button | BtnA = `!gpio_in(GPIO_NUM_0)`, `use_rawstate_bits = 0b00001` | **[SRC]** `M5Unified.cpp:3484-3490` |
-| M5Unified RGB LED | `_pin_table_other0` → `GPIO_NUM_21` | **[SRC]** `M5Unified.cpp:242` |
-| M5Unified external I²C | EX SCL `GPIO_NUM_15`, EX SDA `GPIO_NUM_13`; **no internal I²C** (255/255) | **[SRC]** `M5Unified.cpp:93` |
-| Example | `m5stack/STAMP-S3` → `examples/Led/Led.ino` | **[DOC]** link |
-| ESP-IDF | plain `esp32s3` target, no special board package required | **[DOC]** |
-| UiFlow2 | supported | **[DOC]** |
-
----
-
-## 5. Mechanical and footprints
-
-M5Stack publishes KiCad support in `m5stack/M5_Hardware` (HEAD `a240115c94b19ecf647f229c47fa9a8ce46ccdc4`,
-2026-08-17):
-
-| File | Local artifact | SHA-256 (16) |
-|---|---|---|
-| `KiCad/Footprints/M5Stack.pretty/Stamp-S3-SMD.kicad_mod` | [`artifacts/Stamp-S3-SMD.kicad_mod`](artifacts/Stamp-S3-SMD.kicad_mod) | `2435abbd80d39803` |
-| `KiCad/Footprints/M5Stack.pretty/Stamp-S3-DIP.kicad_mod` | [`artifacts/Stamp-S3-DIP.kicad_mod`](artifacts/Stamp-S3-DIP.kicad_mod) | `1e1a32ffa34603d5` |
-| `Products/S007_Stamp-S3/Structures/Stamp-S3.stl` | [`artifacts/Stamp-S3.stl`](artifacts/Stamp-S3.stl) | `f72c1af2d42930fc` |
-| `KiCad/3D/M5Stack.3dshapes/Stamp-S3.step` | **archived** → [`artifacts/Stamp-S3.step.ARCHIVED.md`](artifacts/Stamp-S3.step.ARCHIVED.md) | `7f29337cdac90c80` |
-
-`Stamp-S3-SMD.kicad_mod` is the footprint the DinMeter's `M1` uses.
-
-> **There is no `Stamp-S3A` footprint and no `Stamp-S3A.step`** in the library at that commit,
-> and `Stamp-S3A.stl` is byte-identical to `Stamp-S3.stl`. See the
-> [placeholder](artifacts/Stamp-S3.step.ARCHIVED.md#important-there-is-no-stamp-s3astep) and the
-> [Stamp-S3A record](../stamp-s3a/README.md#7-mechanical).
-
----
-
-## 6. Artifacts
-
-| File | Size | SHA-256 (16) | What it is | Licence | Redistribution | Disposition |
-|---|---:|---|---|---|---|---|
-| [`artifacts/Sch_M5StampS3_v0.2.pdf`](artifacts/Sch_M5StampS3_v0.2.pdf) | 348 884 | `6d92e1aef6577838` | **Primary evidence.** Altium-published schematic, board rev v0.2 | unknown | unknown | repository |
-| [`artifacts/Sch_M5StampS3_v0.2.plaintext-layout.txt`](artifacts/Sch_M5StampS3_v0.2.plaintext-layout.txt) | 7 646 | `7139bba1dc9404cd` | derived: sheet text as positioned rows | derived work of ↑ | — | repository |
-| [`artifacts/Stamp-S3-SMD.kicad_mod`](artifacts/Stamp-S3-SMD.kicad_mod) | 364 492 | `2435abbd80d39803` | KiCad SMD footprint | unknown (`M5_Hardware` has no `LICENSE`) | unknown | repository |
-| [`artifacts/Stamp-S3-DIP.kicad_mod`](artifacts/Stamp-S3-DIP.kicad_mod) | 365 014 | `1e1a32ffa34603d5` | KiCad DIP footprint | unknown | unknown | repository |
-| [`artifacts/Stamp-S3.stl`](artifacts/Stamp-S3.stl) | 158 484 | `f72c1af2d42930fc` | mechanical model | unknown | unknown | repository |
-| [`artifacts/S007_PinMap_01.jpg`](artifacts/S007_PinMap_01.jpg) | 631 459 | `37249f2574a8702c` | official pin-map diagram | unknown | unknown | repository |
-| `artifacts/Stamp-S3.step` | 2 904 597 | `7f29337cdac90c80` | STEP model — **archived**, [placeholder](artifacts/Stamp-S3.step.ARCHIVED.md) | unknown | unknown | archive |
-
-Sources for each are in [`../../../devices/m5stack/dinmeter/sources.md`](../../../devices/m5stack/dinmeter/sources.md).
-
-### Datasheets that belong to other components
-
-- **ESP32-S3 datasheet** — M5Stack mirrors it at
-  `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf`. That file is
-  **byte-identical** (SHA-256 `b6db403d6d5db8d1b4db0c8390ff7e0a7db714b8388e986e1c64bff563f76b61`)
-  to `components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf`
-  already held in this repository. **Not duplicated**; the extra URL is recorded here and in the
-  device source table.
-- **MUN3CAD01-SC datasheet** → [`components/murata/mun3cad01-sc/`](../../murata/mun3cad01-sc/README.md)
-- **SGM2578 load switch** → [`components/sgmicro/sgm2578/`](../../sgmicro/sgm2578/README.md)
-
----
-
-## 7. Caveats and unsafe assumptions
-
-- **`FN8`, not `R8`.** There is **no PSRAM**. Enabling PSRAM in a build will fail or silently
-  degrade. The repo's `esp32-s3r8` record describes different silicon options; read it for the
-  core, not for memory.
-- **GPIO33–38 are not yours.** They are wired to the rear FPC header and the RGB LED inside the
-  module. A carrier board cannot use them.
-- **Do not pull GPIO46 up.** Strapping pin, pulled down by design.
-- **`ANT1 = PROANT440` is read from the schematic value text, not from a chip marking.** No
-  teardown photograph was inspected. **[SCH]** **[INF]**
-- **The 33 mA standby figure is the vendor's, with no stated method** (clock, radio state,
-  peripherals). Do not use it for a battery-life calculation without measuring.
-
----
-
-## Used By
-
-### M5Stack DinMeter (SKU K134)
-
-Fitted as **`M1`**, `STAMP-S3-SMD` footprint, 31 pads. The carrier supplies 5 V on pad 13
-(`+5VIN`) and takes 3.3 V back on pad 28. All 23 module IOs are broken out to the carrier; the
-DinMeter uses 20 of them and leaves GPIO43/GPIO44 (UART0) unlabelled and GPIO0 to the module's
-own button.
-
-The module's **internal** GPIO21 RGB LED and GPIO38 backlight switch are *not* wired to anything
-on the DinMeter carrier — the DinMeter drives its own panel backlight from GPIO9 through its own
-`U6` AW35122FDR. So on this board the Stamp's RGB LED is simply an always-lit status LED on
-GPIO21, with no enable step required.
-
-Full wiring: [`devices/m5stack/dinmeter/pinouts-and-buses.md`](../../../devices/m5stack/dinmeter/pinouts-and-buses.md) §2.
-
-### M5Stack DinMeter v1.1 (SKU K134-V11) — *not* this module
-
-v1.1 fits the [Stamp-S3A](../stamp-s3a/README.md) instead. That substitution is the entire
-content of the revision; see
-[`devices/m5stack/dinmeter-v1.1/README.md`](../../../devices/m5stack/dinmeter-v1.1/README.md).
-
-### Devices carrying this module
-
-| Device | Record |
-|---|---|
-| **Cardputer v1.0** (`K132`) | [`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) |
-| Cardputer Accessory Kit (original) | sold as a spare: StampS3 + display |
-
-The Cardputer v1.0 is **the only Cardputer whose RGB LED is independent of the LCD backlight**,
-because this module feeds the WS2812 from the always-on `VDD_3V3`. The Stamp-S3A moved it to the
-switched `BL_3V3` rail, buying sleep current (0.26 µA → 0.15 µA) at the cost of that
-independence.
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.10.*
diff --git a/components/m5stack/stamp-s3/artifacts/S007_PinMap_01.jpg b/components/m5stack/stamp-s3/artifacts/S007_PinMap_01.jpg
deleted file mode 100644
index e34abc7..0000000
Binary files a/components/m5stack/stamp-s3/artifacts/S007_PinMap_01.jpg and /dev/null differ
diff --git a/components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.pdf b/components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.pdf
deleted file mode 100644
index e85dc0f..0000000
Binary files a/components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.plaintext-layout.txt b/components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.plaintext-layout.txt
deleted file mode 100644
index 06cd243..0000000
--- a/components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.plaintext-layout.txt
+++ /dev/null
@@ -1,138 +0,0 @@
-y=  31.2 | [109]1  [315]2  [523]3  [729]4
-y=  42.0 | [798]J1
-y=  48.5 | [65]ANT1
-y=  50.4 | [464]LCD
-y=  55.7 | [75]PROANT440  [717]VIN_5V  [802]1  [813]C
-y=  56.4 | [258]U1  [748]GPIO18
-y=  61.2 | [114]L1  [802]2  [813]N
-y=  63.6 | [218]ESP_LNA  [248]1  [341]5  [364]GPIO0  [748]GPIO17  [813]/
-y=  67.2 | [271]LNA_IN  [320]GPIO0  [802]3  [813]B
-y=  70.8 | [341]6  [364]GPIO1  [463]VDD_3V3  [510]U2  [704]J3  [748]GPIO16  [813]W
-y=  73.0 | [118]2.2nH  [320]GPIO1  [802]4
-y=  77.3 | [150]C1  [341]7  [364]GPIO2  [497]A2  [567]A1  [695]1  [813]P
-y=  81.1 | [103]C2  [813]2
-y=  84.7 | [154]2.2pF  [320]GPIO2  [387]R3  [517]VIN  [543]VOUT  [802]5  [813]1
-y=  85.4 | [215]ESP_EN  [247]4  [341]8  [364]GPIO3  [694]2  [813]-
-y=  88.3 | [107]2.0pF  [272]CHIP_PU  [320]GPIO3  [428]VDD_3V3  [802]6  [813]X
-y=  92.6 | [13]A  [341]9  [364]GPIO4  [474]C3  [566]B2  [591]DISP_BL  [651]DISP_RST  [694]3  [752]DISP_RST  [813]H  [827]A
-y=  96.2 | [226]FLASH_VCC  [320]GPIO4  [394]10K/1%  [548]EN  [802]7  [813]-
-y=  99.8 | [31]GND  [343]10  [364]GPIO5  [485]100nF/25V  [649]DISP_RS  [694]4  [750]DISP_RS  [813]K
-y= 103.4 | [320]GPIO5  [802]8
-y= 107.0 | [342]11  [364]GPIO6  [498]B1  [653]DISP_MOSI  [694]5  [754]DISP_MOSI  [813]5  [813].
-y= 109.6 | [813]0
-y= 110.6 | [320]GPIO6  [519]GND  [802]9  [813]/
-y= 114.2 | [139]GND  [245]29  [343]12  [364]GPIO7  [651]DISP_SCK  [694]6  [752]DISP_SCK  [813]C
-y= 117.8 | [92]GND  [170]C26  [215]C4  [273]VDD_SPI  [320]GPIO7  [803]10  [813]G
-y= 121.4 | [343]13  [364]GPIO8  [520]SGM2578  [694]7
-y= 124.2 | [179]100nF/25V  [222]1uF/10V  [320]GPIO8  [607]VDD_3V3  [803]11  [813]D
-y= 128.6 | [343]14  [364]GPIO9  [463]GND  [528]WS4622C-4/TR  [649]DISP_CS  [694]8  [750]DISP_CS  [813]H
-y= 132.2 | [320]GPIO9  [803]12
-y= 135.7 | [245]30  [343]15  [366]GPIO10
-y= 139.3 | [269]SPIHD  [318]GPIO10
-y= 142.9 | [246]31  [343]16  [366]GPIO11  [739]HDGC/0.5K-HX-8PWB/NC
-y= 146.5 | [269]SPIWP  [318]GPIO11
-y= 150.1 | [245]32  [343]17  [366]GPIO12
-y= 154.9 | [99]L3  [157]GND  [204]GND  [270]SPICS0  [318]GPIO12
-y= 157.3 | [246]33  [343]18  [366]GPIO13
-y= 160.9 | [270]SPICLK  [318]GPIO13  [672]GND  [773]GND
-y= 164.5 | [245]34  [343]19  [366]GPIO14
-y= 166.7 | [103]10nH
-y= 168.1 | [266]SPIQ  [318]GPIO14
-y= 171.7 | [92]X1  [246]35
-y= 175.3 | [266]SPID  [543]VDD_3V3
-y= 178.9 | [82]1  [125]4  [343]21  [366]GPIO15
-y= 182.5 | [155]GND  [309]XTAL_32K_P  [465]RGB  [491]LED  [651]U3
-y= 186.1 | [216]XTAL_40M_P  [245]54  [343]22  [366]GPIO16
-y= 189.7 | [271]XTAL_P  [309]XTAL_32K_N  [615]SK_DIN  [640]3  [698]2
-y= 192.6 | [49]C9  [81]2  [125]3  [343]23  [366]GPIO17  [656]DI  [678]GND  [728]GND
-y= 196.1 | [555]C17
-y= 199.7 | [52]10pF  [318]GPIO17
-y= 200.5 | [343]24  [366]GPIO18
-y= 204.1 | [318]GPIO18  [563]10uF/10V  [640]4  [698]1  [719]SK_DOUT
-y= 207.7 | [97]40Mhz  [343]25  [372]USB_DU_N  [610]VDD_3V3  [659]VDD  [681]DO
-y= 211.2 | [318]GPIO19
-y= 214.8 | [74]GND  [129]C14  [217]XTAL_40M_N  [246]53  [343]26  [371]USB_DU_P
-y= 218.4 | [272]XTAL_N  [318]GPIO20  [658]WS2812
-y= 222.0 | [343]27  [366]GPIO21  [399]SK_DIN
-y= 225.6 | [95]GND  [318]GPIO21  [525]JP4
-y= 229.2 | [13]B  [38]GND  [343]28  [827]B
-y= 232.8 | [319]SPICS1  [543]GND
-y= 236.4 | [131]12pF  [247]2
-y= 240.0 | [271]VDD3P3
-y= 243.6 | [35]VDD_3V3  [247]3  [343]36
-y= 247.2 | [271]VDD3P3  [314]SPICLK_N
-y= 248.4 | [135]L2  [343]37  [666]M1
-y= 251.9 | [481]BTN-USER
-y= 254.6 | [314]SPICLK_P
-y= 260.4 | [137]2nH  [343]38  [366]GPIO33  [395]DISP_RST  [631]GPIO1  [655]1
-y= 261.8 | [318]GPIO33  [670]G1
-y= 264.7 | [46]C5  [81]C6  [118]C7  [168]C8  [245]20  [343]39  [366]GPIO34  [393]DISP_RS  [631]GPIO2  [654]2
-y= 269.0 | [210]VDD_3V3  [279]VDD3P3_RTC  [318]GPIO34  [678]G2
-y= 271.9 | [55]10uF/10V  [89]1uF/10V  [129]100nF/25V  [179]100nF/25V  [343]40  [366]GPIO35  [397]DISP_MOSI  [631]GPIO3  [655]3
-y= 276.2 | [318]GPIO35  [670]G3
-y= 279.8 | [343]41  [366]GPIO36  [395]DISP_SCK  [474]VDD_3V3  [631]GPIO4  [654]4
-y= 283.4 | [318]GPIO36  [678]G4
-y= 287.0 | [245]46  [343]42  [366]GPIO37  [393]DISP_CS  [631]GPIO5  [654]5
-y= 290.6 | [210]VDD_3V3  [279]VDD3P3_CPU  [318]GPIO37  [670]G5
-y= 294.2 | [343]43  [366]GPIO38  [393]DISP_BL  [631]GPIO6  [654]6  [799]VDD_3V3
-y= 297.8 | [318]GPIO38  [678]G6
-y= 301.4 | [35]GND  [71]GND  [107]GND  [157]GND  [343]44  [366]GPIO39  [481]R4  [631]GPIO7  [654]7  [742]28
-y= 305.0 | [319]MTCK  [670]G7  [723]3V3
-y= 308.6 | [343]45  [366]GPIO40  [488]10K/1%  [631]GPIO8  [654]8  [742]27  [766]GPIO46
-y= 312.2 | [319]MTDO  [535]S1  [678]G8  [716]G46  [817]B
-y= 315.7 | [60]VDD_3V3  [103]VDD_3V3  [516]GPIO0  [631]GPIO9  [654]9  [742]26  [767]TX  [817]3
-y= 319.3 | [670]G9  [718]G43/Tx  [817]V
-y= 322.9 | [246]55  [343]47  [366]GPIO41  [492]B  [633]GPIO10  [653]10  [742]25  [766]GPIO42  [817]3
-y= 326.5 | [145]VDD_3V3  [270]VDDA1  [320]MTDI  [492]3  [679]G10  [706]G42/MTMS  [817]D
-y= 330.1 | [245]56  [343]48  [366]GPIO42  [492]V  [653]11  [742]24  [767]RX
-y= 333.7 | [270]VDDA2  [319]MTMS  [530]SMT_SW_1TS026A  [674]GND  [718]G44/Rx  [817]F
-y= 336.6 | [72]C10  [116]C11  [188]C12  [224]C13  [343]49  [359]R5  [399]TX  [486]D1  [492]3  [604]VIN_5V  [633]GPIO11  [653]12  [742]23  [766]GPIO41  [810]D2  [817]2
-y= 338.5 | [492]D  [817]C
-y= 343.8 | [82]100nF/25V  [125]100nF/25V  [194]1uF/10V  [230]1nF/25V  [318]U0TXD  [492]F  [679]G11  [707]G41/MTDI  [817]N
-y= 344.5 | [343]50  [363]RX  [400]510R/1%  [492]2  [653]13  [742]22  [767]EN
-y= 348.1 | [318]U0RXD  [492]C  [670]5V  [724]EN  [817]D
-y= 351.7 | [343]51  [564]GND  [633]GPIO12  [653]14  [742]21  [766]GPIO40  [817]S
-y= 355.3 | [318]GPIO45  [492]N  [679]G12  [705]G40/MTDO  [817]E
-y= 358.9 | [246]57  [343]52  [366]GPIO46  [492]D  [633]GPIO13  [653]15  [742]20  [764]GPIO0
-y= 362.5 | [266]GND  [318]GPIO46  [672]G13  [717]G0/Boot  [817]P
-y= 366.1 | [13]C  [492]S  [633]GPIO14  [653]16  [742]19  [766]GPIO39  [827]C
-y= 367.4 | [492]E
-y= 371.2 | [492]P  [679]G14  [705]G39/MTCK
-y= 373.3 | [60]GND  [103]GND  [273]ESP32-S3FN8  [633]GPIO15  [653]17  [742]18
-y= 376.9 | [672]G15  [722]GND
-y= 380.5 | [175]GND  [211]GND  [233]GND  [474]GND
-y= 387.7 | [679]STAMP-S3M
-y= 394.8 | [799]GND
-y= 403.2 | [43]ESP32  [640]GND
-y= 428.3 | [44]DCDC  [470]Type-A  [502]USB
-y= 434.6 | [89]VDD_3V3  [731]JP1
-y= 438.2 | [475]JP3
-y= 445.4 | [787]VIN_5V
-y= 455.5 | [95]R7  [654]J2  [743]F1
-y= 456.2 | [50]PHD1  [377]VDD_3V3
-y= 459.8 | [494]USB_DU_P  [560]USB_D_P  [642]A6
-y= 462.7 | [106]10K/1%D6  [665]DP1VCC
-y= 468.0 | [642]B6  [688]A5  [701]R1  [810]B
-y= 470.6 | [62]phd_3mm  [100]ESP_EN  [151]EN  [660]DP2  [671]CC1  [757]6V/1A/PPTC  [810]V
-y= 474.2 | [494]USB_DU_N  [560]USB_D_N  [642]A7  [810]5
-y= 477.8 | [208]M2  [304]R6  [350]C21  [389]C22  [660]DN1  [671]CC2  [688]B5  [719]5.1K/1%
-y= 480.6 | [801]D14  [810]D
-y= 484.2 | [101]C23  [169]R16  [313]100K/1%  [358]10uF/10V  [397]10uF/10V  [518]L5  [642]B7  [665]DN2GND  [810]F
-y= 485.7 | [129]1N4148WT  [197]1  [262]6  [711]R2  [810]2
-y= 488.6 | [213]EN  [240]VOUT  [601]B  [633]B  [810]C
-y= 491.4 | [107]1uF/10V  [176]100K/1%  [197]2  [262]5  [601]3  [633]3  [667]SHELL
-y= 495.7 | [216]GND  [246]FB  [601]V  [633]V  [810]N
-y= 499.3 | [197]3  [262]4  [601]3  [633]3  [668]USB-TYPEC  [719]5.1K/1%  [810]D
-y= 502.9 | [13]D  [141]VIN_5V  [215]VIN  [243]GND  [594]D3  [627]D4  [810]S  [827]D
-y= 506.5 | [42]GND  [306]R17  [601]D  [633]D
-y= 508.2 | [601]F  [633]F  [810]E
-y= 513.0 | [314]22.1K/1%  [474]JP2  [601]2  [633]2  [810]P
-y= 513.7 | [228]MUN3CAD01-SC  [377]GND  [601]C  [633]C
-y= 520.9 | [89]GND  [601]N  [633]N  [687]GND  [730]GND
-y= 525.0 | [601]D  [633]D  [788]GND
-y= 528.1 | [182]GND  [601]S  [633]S
-y= 533.0 | [601]E  [633]E
-y= 536.8 | [601]P  [633]P
-y= 542.5 | [276]GND  [298]GND
-y= 546.1 | [582]GND  [615]GND
-y= 564.1 | [109]1  [315]2  [523]3  [729]4
diff --git a/components/m5stack/stamp-s3/artifacts/Stamp-S3-DIP.kicad_mod b/components/m5stack/stamp-s3/artifacts/Stamp-S3-DIP.kicad_mod
deleted file mode 100644
index bb996d9..0000000
--- a/components/m5stack/stamp-s3/artifacts/Stamp-S3-DIP.kicad_mod
+++ /dev/null
@@ -1,11877 +0,0 @@
-(footprint "STAMP-S3-DIP" (version 20221018) (generator pcbnew)
-  (layer "F.Cu")
-  (descr "https://docs.m5stack.com/en/core/StampS3")
-  (tags "stamp-s3,esp32-s3")
-  (attr smd)
-  (fp_text reference "REF**" (at -8.8088 -12.8168 unlocked) (layer "F.SilkS")
-      (effects (font (size 1 1) (thickness 0.15)) (justify left bottom))
-    (tstamp 3f0ed3e7-df70-454c-b478-264607864ace)
-  )
-  (fp_text value "STAMP-S3-DIP" (at -5.08 16.51 unlocked) (layer "F.SilkS")
-      (effects (font (size 1 1) (thickness 0.15)) (justify left bottom))
-    (tstamp cd971d24-2238-440d-beab-a9f488c7a0d5)
-  )
-  (fp_poly
-    (pts
-      (xy 0.153882 4.440275)
-      (xy 0.112718 4.455288)
-      (xy 0.091959 4.48335)
-      (xy 0.087331 4.517233)
-      (xy 0.094558 4.557648)
-      (xy 0.11893 4.583005)
-      (xy 0.164486 4.595792)
-      (xy 0.21949 4.598643)
-      (xy 0.309359 4.598643)
-      (xy 0.309359 4.435823)
-      (xy 0.21949 4.435823)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6a486226-b62f-42ac-9e8d-608561281df4))
-  (fp_poly
-    (pts
-      (xy 1.563817 3.088871)
-      (xy 1.507968 3.092828)
-      (xy 1.468449 3.107134)
-      (xy 1.445402 3.123898)
-      (xy 1.412483 3.164999)
-      (xy 1.406591 3.204654)
-      (xy 1.425223 3.239342)
-      (xy 1.465873 3.265544)
-      (xy 1.526038 3.279741)
-      (xy 1.55737 3.281277)
-      (xy 1.641527 3.281277)
-      (xy 1.641527 3.088853)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5f04069b-81e2-4988-bd93-8327b361a52d))
-  (fp_poly
-    (pts
-      (xy 6.244907 4.820671)
-      (xy 6.555746 4.820671)
-      (xy 6.555746 4.96869)
-      (xy 6.27451 4.96869)
-      (xy 6.27451 5.101907)
-      (xy 6.555746 5.101907)
-      (xy 6.555746 5.264727)
-      (xy 6.230105 5.264727)
-      (xy 6.230105 5.412746)
-      (xy 6.74817 5.412746)
-      (xy 6.74817 4.687454)
-      (xy 6.244907 4.687454)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp cf70367d-992a-47eb-ba66-e009380700af))
-  (fp_poly
-    (pts
-      (xy -0.837786 5.960415)
-      (xy -0.78786 6.010527)
-      (xy -0.746425 6.05203)
-      (xy -0.717425 6.080979)
-      (xy -0.704804 6.09343)
-      (xy -0.704569 6.093632)
-      (xy -0.694544 6.083793)
-      (xy -0.667589 6.056906)
-      (xy -0.62765 6.016916)
-      (xy -0.578671 5.967767)
-      (xy -0.571352 5.960415)
-      (xy -0.438753 5.827198)
-      (xy -0.970385 5.827198)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 8e8e073f-f28c-4a8c-98bd-39ec815b8993))
-  (fp_poly
-    (pts
-      (xy 1.525295 2.80997)
-      (xy 1.498499 2.815985)
-      (xy 1.493508 2.820693)
-      (xy 1.48119 2.834513)
-      (xy 1.463904 2.84151)
-      (xy 1.439658 2.860285)
-      (xy 1.434301 2.888699)
-      (xy 1.442247 2.930433)
-      (xy 1.468546 2.956239)
-      (xy 1.51689 2.968537)
-      (xy 1.559059 2.970438)
-      (xy 1.641527 2.970438)
-      (xy 1.641527 2.807618)
-      (xy 1.567517 2.807618)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 11e5d550-8ce0-4194-bc6e-50c6304e6f24))
-  (fp_poly
-    (pts
-      (xy 0.194805 4.720136)
-      (xy 0.136313 4.723192)
-      (xy 0.101122 4.728096)
-      (xy 0.082929 4.736626)
-      (xy 0.075431 4.750564)
-      (xy 0.074678 4.754063)
-      (xy 0.062379 4.783891)
-      (xy 0.052314 4.794768)
-      (xy 0.044324 4.810127)
-      (xy 0.050326 4.816971)
-      (xy 0.069087 4.83823)
-      (xy 0.081481 4.857676)
-      (xy 0.095305 4.873853)
-      (xy 0.119467 4.883723)
-      (xy 0.16113 4.889279)
-      (xy 0.203596 4.891629)
-      (xy 0.309359 4.895977)
-      (xy 0.309359 4.715813)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 3fd098af-9969-44b8-8398-07b02e68e34b))
-  (fp_poly
-    (pts
-      (xy -2.836037 5.960415)
-      (xy -2.785417 6.010671)
-      (xy -2.742397 6.052252)
-      (xy -2.711182 6.081177)
-      (xy -2.695973 6.093464)
-      (xy -2.695402 6.093632)
-      (xy -2.682422 6.083754)
-      (xy -2.653129 6.056894)
-      (xy -2.611933 6.01721)
-      (xy -2.565577 5.971207)
-      (xy -2.517726 5.922234)
-      (xy -2.478714 5.880645)
-      (xy -2.452693 5.850982)
-      (xy -2.443788 5.83799)
-      (xy -2.457805 5.834518)
-      (xy -2.496718 5.83151)
-      (xy -2.555822 5.829159)
-      (xy -2.630409 5.82766)
-      (xy -2.706213 5.827198)
-      (xy -2.968637 5.827198)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp a4967312-bbb6-4441-9bd5-dca5386c94cb))
-  (fp_poly
-    (pts
-      (xy -6.440919 11.281963)
-      (xy -6.484145 11.283679)
-      (xy -6.508955 11.288154)
-      (xy -6.520943 11.296709)
-      (xy -6.525703 11.310666)
-      (xy -6.526808 11.317861)
-      (xy -6.523296 11.352207)
-      (xy -6.499508 11.375231)
-      (xy -6.452698 11.388274)
-      (xy -6.380122 11.39268)
-      (xy -6.373683 11.392699)
-      (xy -6.30978 11.389791)
-      (xy -6.262123 11.381809)
-      (xy -6.24189 11.373368)
-      (xy -6.221575 11.341775)
-      (xy -6.220558 11.317861)
-      (xy -6.224015 11.301438)
-      (xy -6.232518 11.290933)
-      (xy -6.251661 11.285024)
-      (xy -6.287039 11.282389)
-      (xy -6.344244 11.281707)
-      (xy -6.373683 11.281685)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 8ef3c2d0-4a8e-4699-b119-5b215d850525))
-  (fp_poly
-    (pts
-      (xy 1.574741 4.438256)
-      (xy 1.545171 4.444533)
-      (xy 1.537914 4.450625)
-      (xy 1.525925 4.463757)
-      (xy 1.515711 4.465426)
-      (xy 1.496087 4.477275)
-      (xy 1.493508 4.487629)
-      (xy 1.485515 4.507327)
-      (xy 1.478706 4.509832)
-      (xy 1.46668 4.522229)
-      (xy 1.463904 4.539436)
-      (xy 1.470103 4.563488)
-      (xy 1.478706 4.56904)
-      (xy 1.492538 4.580738)
-      (xy 1.493623 4.587542)
-      (xy 1.507269 4.60896)
-      (xy 1.542755 4.627315)
-      (xy 1.59232 4.639604)
-      (xy 1.637077 4.643049)
-      (xy 1.700734 4.643049)
-      (xy 1.700734 4.435823)
-      (xy 1.619324 4.435823)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 336078d2-ed55-4f72-ae80-e07d40609b29))
-  (fp_poly
-    (pts
-      (xy -6.292273 -9.788769)
-      (xy -6.129452 -9.788769)
-      (xy -6.129452 -10.290277)
-      (xy -6.088747 -10.269043)
-      (xy -6.032249 -10.248186)
-      (xy -5.989007 -10.252858)
-      (xy -5.956262 -10.283692)
-      (xy -5.946314 -10.301731)
-      (xy -5.931879 -10.344744)
-      (xy -5.939979 -10.369892)
-      (xy -5.972034 -10.380063)
-      (xy -5.985134 -10.380617)
-      (xy -6.007122 -10.386708)
-      (xy -6.011037 -10.393315)
-      (xy -6.022994 -10.407176)
-      (xy -6.05294 -10.426892)
-      (xy -6.06614 -10.43402)
-      (xy -6.109197 -10.458763)
-      (xy -6.145197 -10.483827)
-      (xy -6.150342 -10.488157)
-      (xy -6.187557 -10.506876)
-      (xy -6.235856 -10.514061)
-      (xy -6.292273 -10.514061)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 27e94ff8-3b81-4d85-95f2-f6d220fd0122))
-  (fp_poly
-    (pts
-      (xy -5.566982 6.596895)
-      (xy -5.418963 6.596895)
-      (xy -5.418963 6.404471)
-      (xy -5.417789 6.316142)
-      (xy -5.414031 6.255637)
-      (xy -5.407336 6.221257)
-      (xy -5.397351 6.211305)
-      (xy -5.383721 6.224085)
-      (xy -5.381958 6.226848)
-      (xy -5.358687 6.241282)
-      (xy -5.327384 6.234761)
-      (xy -5.298081 6.20978)
-      (xy -5.294849 6.205166)
-      (xy -5.274028 6.163317)
-      (xy -5.277773 6.135978)
-      (xy -5.306852 6.120057)
-      (xy -5.316483 6.117828)
-      (xy -5.356291 6.102595)
-      (xy -5.401486 6.075328)
-      (xy -5.416068 6.064171)
-      (xy -5.47556 6.02806)
-      (xy -5.518548 6.019622)
-      (xy -5.566982 6.019622)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e14360af-43cb-485f-a4ff-263917982970))
-  (fp_poly
-    (pts
-      (xy -5.31535 4.065776)
-      (xy -5.167331 4.065776)
-      (xy -5.167331 3.873352)
-      (xy -5.166213 3.789479)
-      (xy -5.162992 3.727782)
-      (xy -5.157874 3.69087)
-      (xy -5.152328 3.680928)
-      (xy -5.128871 3.688085)
-      (xy -5.107267 3.69943)
-      (xy -5.08358 3.709135)
-      (xy -5.064156 3.699238)
-      (xy -5.04859 3.680928)
-      (xy -5.026607 3.643203)
-      (xy -5.020538 3.611722)
-      (xy -5.031108 3.593827)
-      (xy -5.039823 3.592116)
-      (xy -5.077188 3.581912)
-      (xy -5.131296 3.552674)
-      (xy -5.177225 3.521808)
-      (xy -5.22068 3.499331)
-      (xy -5.26511 3.488645)
-      (xy -5.269529 3.488503)
-      (xy -5.31535 3.488503)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0442654b-3393-4798-b56e-5abbba440c2e))
-  (fp_poly
-    (pts
-      (xy -5.31535 9.128014)
-      (xy -5.167331 9.128014)
-      (xy -5.167331 8.93559)
-      (xy -5.166157 8.847261)
-      (xy -5.1624 8.786756)
-      (xy -5.155705 8.752375)
-      (xy -5.145719 8.742424)
-      (xy -5.13209 8.755204)
-      (xy -5.130327 8.757967)
-      (xy -5.106923 8.7722)
-      (xy -5.074858 8.766696)
-      (xy -5.045253 8.743746)
-      (xy -5.042355 8.739872)
-      (xy -5.021115 8.697375)
-      (xy -5.026363 8.667773)
-      (xy -5.058256 8.650432)
-      (xy -5.064852 8.648947)
-      (xy -5.104659 8.633714)
-      (xy -5.149854 8.606447)
-      (xy -5.164436 8.59529)
-      (xy -5.223928 8.559179)
-      (xy -5.266916 8.550741)
-      (xy -5.31535 8.550741)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9521f759-ce2f-426c-b7e4-acb1db01af58))
-  (fp_poly
-    (pts
-      (xy -6.42549 1.534657)
-      (xy -6.277471 1.534657)
-      (xy -6.277471 1.342233)
-      (xy -6.276297 1.253905)
-      (xy -6.272539 1.193399)
-      (xy -6.265845 1.159019)
-      (xy -6.255859 1.149067)
-      (xy -6.242229 1.161848)
-      (xy -6.240466 1.164611)
-      (xy -6.217863 1.180063)
-      (xy -6.189611 1.171421)
-      (xy -6.162288 1.141549)
-      (xy -6.154397 1.127104)
-      (xy -6.136411 1.087892)
-      (xy -6.131285 1.06838)
-      (xy -6.13881 1.061706)
-      (xy -6.152366 1.060998)
-      (xy -6.176152 1.0534)
-      (xy -6.215396 1.033596)
-      (xy -6.256267 1.009191)
-      (xy -6.308559 0.980274)
-      (xy -6.356212 0.961748)
-      (xy -6.381371 0.957385)
-      (xy -6.42549 0.957385)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 27c2e63c-c7a2-4ed3-b7b0-a537751b114b))
-  (fp_poly
-    (pts
-      (xy -5.228974 2.265827)
-      (xy -5.25615 2.268748)
-      (xy -5.326771 2.289557)
-      (xy -5.383924 2.328563)
-      (xy -5.422134 2.38069)
-      (xy -5.435834 2.435351)
-      (xy -5.436359 2.498766)
-      (xy -5.433427 2.554878)
-      (xy -5.427696 2.596216)
-      (xy -5.419997 2.615193)
-      (xy -5.406111 2.634218)
-      (xy -5.40047 2.64687)
-      (xy -5.375957 2.675741)
-      (xy -5.330275 2.699565)
-      (xy -5.271814 2.714915)
-      (xy -5.224264 2.718806)
-      (xy -5.152529 2.718806)
-      (xy -5.152529 2.497652)
-      (xy -5.153451 2.415686)
-      (xy -5.156018 2.347359)
-      (xy -5.159935 2.297433)
-      (xy -5.164905 2.270668)
-      (xy -5.166847 2.267649)
-      (xy -5.18879 2.264383)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 932fa28f-a3a8-4264-a152-97b489abd80a))
-  (fp_poly
-    (pts
-      (xy 4.64598 9.891065)
-      (xy 4.587171 9.917319)
-      (xy 4.546863 9.956239)
-      (xy 4.538747 9.979483)
-      (xy 4.532817 10.020564)
-      (xy 4.529268 10.071322)
-      (xy 4.528295 10.123596)
-      (xy 4.530092 10.169222)
-      (xy 4.534855 10.20004)
-      (xy 4.540842 10.20855)
-      (xy 4.552621 10.2213)
-      (xy 4.56229 10.251032)
-      (xy 4.576999 10.28394)
-      (xy 4.60828 10.303205)
-      (xy 4.661201 10.311302)
-      (xy 4.68701 10.311961)
-      (xy 4.719757 10.316082)
-      (xy 4.73498 10.325847)
-      (xy 4.735116 10.326965)
-      (xy 4.747784 10.338092)
-      (xy 4.772121 10.341767)
-      (xy 4.809126 10.341767)
-      (xy 4.809126 9.882909)
-      (xy 4.723608 9.882909)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp cb739b07-43eb-4e36-a6a8-d72374db25fe))
-  (fp_poly
-    (pts
-      (xy 3.324315 -6.101552)
-      (xy 3.278781 -6.097255)
-      (xy 3.256406 -6.090752)
-      (xy 3.25493 -6.088303)
-      (xy 3.242691 -6.075812)
-      (xy 3.228616 -6.073501)
-      (xy 3.196809 -6.060941)
-      (xy 3.162055 -6.022092)
-      (xy 3.140215 -5.987477)
-      (xy 3.130397 -5.957812)
-      (xy 3.124287 -5.915024)
-      (xy 3.122057 -5.868172)
-      (xy 3.12388 -5.826316)
-      (xy 3.129927 -5.798517)
-      (xy 3.136515 -5.792266)
-      (xy 3.149675 -5.780289)
-      (xy 3.151317 -5.770232)
-      (xy 3.160387 -5.742821)
-      (xy 3.176809 -5.718426)
-      (xy 3.191328 -5.705069)
-      (xy 3.211493 -5.69639)
-      (xy 3.243375 -5.691412)
-      (xy 3.293043 -5.689159)
-      (xy 3.361833 -5.688653)
-      (xy 3.521363 -5.688653)
-      (xy 3.521363 -6.103105)
-      (xy 3.388147 -6.103105)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d1dd79ad-47a7-43bf-bfc4-080710b83397))
-  (fp_poly
-    (pts
-      (xy 6.34852 4.065776)
-      (xy 6.496538 4.065776)
-      (xy 6.496538 3.873352)
-      (xy 6.496789 3.794796)
-      (xy 6.498027 3.741124)
-      (xy 6.500976 3.70762)
-      (xy 6.506362 3.689565)
-      (xy 6.514912 3.682242)
-      (xy 6.526142 3.680928)
-      (xy 6.550195 3.687126)
-      (xy 6.555746 3.69573)
-      (xy 6.563142 3.711532)
-      (xy 6.58107 3.7068)
-      (xy 6.603136 3.685287)
-      (xy 6.619613 3.658223)
-      (xy 6.637613 3.618997)
-      (xy 6.642486 3.5995)
-      (xy 6.634055 3.592837)
-      (xy 6.617914 3.592116)
-      (xy 6.587408 3.585441)
-      (xy 6.577208 3.579143)
-      (xy 6.544607 3.555922)
-      (xy 6.498032 3.530361)
-      (xy 6.448011 3.507424)
-      (xy 6.405071 3.492075)
-      (xy 6.384999 3.488503)
-      (xy 6.34852 3.488503)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp db5af78e-b317-464d-987c-02ca43beec76))
-  (fp_poly
-    (pts
-      (xy -5.182133 7.943865)
-      (xy -5.019313 7.943865)
-      (xy -5.018144 7.681132)
-      (xy -5.017379 7.598235)
-      (xy -5.015965 7.528139)
-      (xy -5.014053 7.475117)
-      (xy -5.011796 7.44344)
-      (xy -5.00951 7.436901)
-      (xy -4.989971 7.453889)
-      (xy -4.981074 7.455403)
-      (xy -4.962181 7.463802)
-      (xy -4.960105 7.470205)
-      (xy -4.947431 7.481306)
-      (xy -4.922861 7.485007)
-      (xy -4.891775 7.476371)
-      (xy -4.867485 7.446222)
-      (xy -4.861554 7.434546)
-      (xy -4.845525 7.385618)
-      (xy -4.853267 7.352797)
-      (xy -4.885707 7.33336)
-      (xy -4.896978 7.330448)
-      (xy -4.933124 7.315193)
-      (xy -4.976861 7.287004)
-      (xy -4.99789 7.270129)
-      (xy -5.042019 7.236928)
-      (xy -5.082293 7.22181)
-      (xy -5.119225 7.218857)
-      (xy -5.182133 7.218573)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 74d25b76-c3a7-41a7-a934-52933e911c59))
-  (fp_poly
-    (pts
-      (xy -5.759406 4.065776)
-      (xy -5.626189 4.065776)
-      (xy -5.626189 3.867337)
-      (xy -5.625986 3.787528)
-      (xy -5.624915 3.732857)
-      (xy -5.622283 3.69886)
-      (xy -5.617397 3.68107)
-      (xy -5.609564 3.675023)
-      (xy -5.598089 3.676253)
-      (xy -5.596585 3.676639)
-      (xy -5.57259 3.688355)
-      (xy -5.566982 3.697456)
-      (xy -5.557532 3.710458)
-      (xy -5.535515 3.706589)
-      (xy -5.510432 3.688711)
-      (xy -5.501212 3.677634)
-      (xy -5.482463 3.64003)
-      (xy -5.48 3.609182)
-      (xy -5.4939 3.592965)
-      (xy -5.500373 3.592116)
-      (xy -5.520181 3.586089)
-      (xy -5.522716 3.581015)
-      (xy -5.535141 3.569164)
-      (xy -5.566648 3.551327)
-      (xy -5.589325 3.540693)
-      (xy -5.62779 3.52165)
-      (xy -5.651789 3.505665)
-      (xy -5.655793 3.499988)
-      (xy -5.668814 3.492395)
-      (xy -5.700831 3.488602)
-      (xy -5.707599 3.488503)
-      (xy -5.759406 3.488503)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 631ae9ed-44c6-4d29-b264-2ec6fbdf93de))
-  (fp_poly
-    (pts
-      (xy -1.614884 5.027897)
-      (xy -1.437261 5.027897)
-      (xy -1.437261 4.783667)
-      (xy -1.436387 4.687393)
-      (xy -1.433856 4.613336)
-      (xy -1.429802 4.563722)
-      (xy -1.424361 4.540783)
-      (xy -1.422459 4.539436)
-      (xy -1.408088 4.5507)
-      (xy -1.407658 4.554238)
-      (xy -1.395401 4.56668)
-      (xy -1.381014 4.56904)
-      (xy -1.348515 4.578104)
-      (xy -1.337129 4.586282)
-      (xy -1.323801 4.590111)
-      (xy -1.308541 4.572368)
-      (xy -1.289763 4.533248)
-      (xy -1.27272 4.492682)
-      (xy -1.2618 4.465139)
-      (xy -1.259639 4.458403)
-      (xy -1.27207 4.451874)
-      (xy -1.296644 4.444546)
-      (xy -1.324366 4.43266)
-      (xy -1.333648 4.420739)
-      (xy -1.34563 4.407828)
-      (xy -1.355682 4.406219)
-      (xy -1.387056 4.394977)
-      (xy -1.428215 4.364693)
-      (xy -1.464868 4.328509)
-      (xy -1.502425 4.308058)
-      (xy -1.551565 4.302606)
-      (xy -1.614884 4.302606)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6d83362d-674a-4262-8ad6-af9f6bc602bb))
-  (fp_poly
-    (pts
-      (xy -5.152529 10.400974)
-      (xy -4.989709 10.400974)
-      (xy -4.989709 10.156744)
-      (xy -4.988835 10.06047)
-      (xy -4.986304 9.986412)
-      (xy -4.98225 9.936799)
-      (xy -4.976809 9.91386)
-      (xy -4.974907 9.912513)
-      (xy -4.960535 9.923777)
-      (xy -4.960105 9.927315)
-      (xy -4.948102 9.940414)
-      (xy -4.937701 9.942116)
-      (xy -4.907533 9.949632)
-      (xy -4.886264 9.960248)
-      (xy -4.863544 9.969967)
-      (xy -4.845538 9.963283)
-      (xy -4.827881 9.93614)
-      (xy -4.807031 9.886609)
-      (xy -4.793044 9.84814)
-      (xy -4.790546 9.829648)
-      (xy -4.79971 9.823755)
-      (xy -4.808506 9.823231)
-      (xy -4.840455 9.814224)
-      (xy -4.863022 9.801028)
-      (xy -4.893008 9.783931)
-      (xy -4.910958 9.779296)
-      (xy -4.940613 9.767618)
-      (xy -4.985341 9.733683)
-      (xy -5.012506 9.708987)
-      (xy -5.039077 9.697134)
-      (xy -5.080693 9.690809)
-      (xy -5.092265 9.690485)
-      (xy -5.152529 9.690485)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 55b2f941-f545-4df8-9edb-cc3f83159180))
-  (fp_poly
-    (pts
-      (xy -3.467959 7.082116)
-      (xy -3.490802 7.113341)
-      (xy -3.522761 7.15904)
-      (xy -3.560349 7.214024)
-      (xy -3.600081 7.273104)
-      (xy -3.638473 7.33109)
-      (xy -3.672039 7.382795)
-      (xy -3.697294 7.423028)
-      (xy -3.710752 7.446601)
-      (xy -3.711627 7.448604)
-      (xy -3.710949 7.456439)
-      (xy -3.699567 7.462163)
-      (xy -3.673811 7.466088)
-      (xy -3.63001 7.468528)
-      (xy -3.564495 7.469795)
-      (xy -3.473595 7.470199)
-      (xy -3.457716 7.470205)
-      (xy -3.362735 7.469902)
-      (xy -3.293684 7.468783)
-      (xy -3.246893 7.466537)
-      (xy -3.21869 7.462851)
-      (xy -3.205407 7.457414)
-      (xy -3.203372 7.449913)
-      (xy -3.203805 7.448604)
-      (xy -3.214873 7.428435)
-      (xy -3.23834 7.390709)
-      (xy -3.270719 7.340615)
-      (xy -3.308526 7.283342)
-      (xy -3.348276 7.22408)
-      (xy -3.386484 7.168018)
-      (xy -3.419663 7.120345)
-      (xy -3.44433 7.086249)
-      (xy -3.456998 7.070921)
-      (xy -3.457716 7.070555)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b1db3629-a22a-4eed-b31d-2a0ada097e39))
-  (fp_poly
-    (pts
-      (xy -1.469707 7.082116)
-      (xy -1.492551 7.113341)
-      (xy -1.524509 7.15904)
-      (xy -1.562097 7.214024)
-      (xy -1.601829 7.273104)
-      (xy -1.640221 7.33109)
-      (xy -1.673787 7.382795)
-      (xy -1.699042 7.423028)
-      (xy -1.712501 7.446601)
-      (xy -1.713375 7.448604)
-      (xy -1.712697 7.456439)
-      (xy -1.701315 7.462163)
-      (xy -1.675559 7.466088)
-      (xy -1.631758 7.468528)
-      (xy -1.566243 7.469795)
-      (xy -1.475343 7.470199)
-      (xy -1.459464 7.470205)
-      (xy -1.364484 7.469902)
-      (xy -1.295433 7.468783)
-      (xy -1.248641 7.466537)
-      (xy -1.220438 7.462851)
-      (xy -1.207155 7.457414)
-      (xy -1.20512 7.449913)
-      (xy -1.205553 7.448604)
-      (xy -1.216621 7.428435)
-      (xy -1.240088 7.390709)
-      (xy -1.272467 7.340615)
-      (xy -1.310275 7.283342)
-      (xy -1.350024 7.22408)
-      (xy -1.388232 7.168018)
-      (xy -1.421411 7.120345)
-      (xy -1.446078 7.086249)
-      (xy -1.458747 7.070921)
-      (xy -1.459464 7.070555)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 48737cf6-b6af-49a7-a3f4-c37a29b37c0c))
-  (fp_poly
-    (pts
-      (xy -6.01928 11.176961)
-      (xy -6.046272 11.19107)
-      (xy -6.055216 11.220904)
-      (xy -6.055443 11.230161)
-      (xy -6.059179 11.261488)
-      (xy -6.076687 11.272977)
-      (xy -6.099567 11.274284)
-      (xy -6.133601 11.280043)
-      (xy -6.150343 11.302638)
-      (xy -6.153556 11.313592)
-      (xy -6.150751 11.353419)
-      (xy -6.124781 11.382082)
-      (xy -6.083201 11.392699)
-      (xy -6.060735 11.405858)
-      (xy -6.052726 11.433404)
-      (xy -6.041719 11.46553)
-      (xy -6.013617 11.478083)
-      (xy -6.010484 11.478489)
-      (xy -5.978151 11.478095)
-      (xy -5.962377 11.472322)
-      (xy -5.953753 11.450288)
-      (xy -5.95183 11.430298)
-      (xy -5.94177 11.403731)
-      (xy -5.908063 11.385984)
-      (xy -5.903724 11.384659)
-      (xy -5.870019 11.3702)
-      (xy -5.85707 11.34739)
-      (xy -5.855618 11.326091)
-      (xy -5.859367 11.294956)
-      (xy -5.876731 11.281342)
-      (xy -5.903724 11.277047)
-      (xy -5.937132 11.270283)
-      (xy -5.950075 11.253037)
-      (xy -5.95183 11.229814)
-      (xy -5.959062 11.18963)
-      (xy -5.9828 11.173421)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6eb88032-5513-4bcb-ad7c-f43593ecc0bb))
-  (fp_poly
-    (pts
-      (xy -7.010849 6.249125)
-      (xy -7.134287 6.249424)
-      (xy -7.233572 6.25006)
-      (xy -7.311428 6.251148)
-      (xy -7.370581 6.2528)
-      (xy -7.413755 6.255131)
-      (xy -7.443675 6.258254)
-      (xy -7.463066 6.262282)
-      (xy -7.474654 6.26733)
-      (xy -7.481162 6.27351)
-      (xy -7.482134 6.274954)
-      (xy -7.490565 6.306758)
-      (xy -7.482138 6.326761)
-      (xy -7.476246 6.333223)
-      (xy -7.465668 6.338557)
-      (xy -7.447674 6.342895)
-      (xy -7.419535 6.346368)
-      (xy -7.378522 6.349107)
-      (xy -7.321904 6.351243)
-      (xy -7.246954 6.352909)
-      (xy -7.15094 6.354235)
-      (xy -7.031134 6.355354)
-      (xy -6.884806 6.356395)
-      (xy -6.863835 6.356531)
-      (xy -6.711932 6.357381)
-      (xy -6.587064 6.357744)
-      (xy -6.486665 6.357548)
-      (xy -6.40817 6.35672)
-      (xy -6.349012 6.355185)
-      (xy -6.306626 6.352872)
-      (xy -6.278445 6.349706)
-      (xy -6.261905 6.345614)
-      (xy -6.254439 6.340523)
-      (xy -6.253697 6.339105)
-      (xy -6.249106 6.307786)
-      (xy -6.250397 6.283432)
-      (xy -6.255268 6.249051)
-      (xy -6.860531 6.249051)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d47e7a32-1b4a-4380-b6ef-0b380fed6f9a))
-  (fp_poly
-    (pts
-      (xy 5.391893 -5.886624)
-      (xy 5.386398 -5.873676)
-      (xy 5.378406 -5.853978)
-      (xy 5.371597 -5.851473)
-      (xy 5.36047 -5.838806)
-      (xy 5.356795 -5.814469)
-      (xy 5.351728 -5.786651)
-      (xy 5.341993 -5.777464)
-      (xy 5.330587 -5.764876)
-      (xy 5.327191 -5.742926)
-      (xy 5.323189 -5.711639)
-      (xy 5.316895 -5.698092)
-      (xy 5.310373 -5.689223)
-      (xy 5.304933 -5.673271)
-      (xy 5.299008 -5.643466)
-      (xy 5.29103 -5.593038)
-      (xy 5.288161 -5.573938)
-      (xy 5.278762 -5.51103)
-      (xy 5.41399 -5.51103)
-      (xy 5.477849 -5.511511)
-      (xy 5.517704 -5.513771)
-      (xy 5.539149 -5.519033)
-      (xy 5.54778 -5.528523)
-      (xy 5.549219 -5.540634)
-      (xy 5.54302 -5.564687)
-      (xy 5.534417 -5.570238)
-      (xy 5.52329 -5.582905)
-      (xy 5.519615 -5.607243)
-      (xy 5.515199 -5.635069)
-      (xy 5.506725 -5.644247)
-      (xy 5.498418 -5.657659)
-      (xy 5.489803 -5.692528)
-      (xy 5.483787 -5.733058)
-      (xy 5.476369 -5.779847)
-      (xy 5.467205 -5.812024)
-      (xy 5.459673 -5.82187)
-      (xy 5.449097 -5.834541)
-      (xy 5.445606 -5.858874)
-      (xy 5.438668 -5.887892)
-      (xy 5.416002 -5.895879)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 11186e3e-5f4a-4169-8f2b-7f3e5bd24918))
-  (fp_poly
-    (pts
-      (xy -4.058312 6.605482)
-      (xy -4.094196 6.643673)
-      (xy -4.09821 7.622988)
-      (xy -4.098922 7.835)
-      (xy -4.099186 8.01884)
-      (xy -4.098986 8.175933)
-      (xy -4.098302 8.30771)
-      (xy -4.097115 8.415595)
-      (xy -4.095408 8.501019)
-      (xy -4.093163 8.565407)
-      (xy -4.090359 8.610188)
-      (xy -4.08698 8.636789)
-      (xy -4.085024 8.643828)
-      (xy -4.052027 8.689636)
-      (xy -4.00353 8.717752)
-      (xy -3.948745 8.724826)
-      (xy -3.901772 8.710486)
-      (xy -3.888464 8.702792)
-      (xy -3.877086 8.694651)
-      (xy -3.867486 8.683825)
-      (xy -3.859512 8.668078)
-      (xy -3.853011 8.645175)
-      (xy -3.847831 8.612879)
-      (xy -3.843819 8.568953)
-      (xy -3.840823 8.511162)
-      (xy -3.83869 8.43727)
-      (xy -3.837267 8.345039)
-      (xy -3.836404 8.232234)
-      (xy -3.835946 8.096619)
-      (xy -3.835741 7.935957)
-      (xy -3.835638 7.748013)
-      (xy -3.835634 7.740339)
-      (xy -3.835163 6.833725)
-      (xy -3.033585 6.833725)
-      (xy -2.990318 6.790458)
-      (xy -2.954801 6.737636)
-      (xy -2.947134 6.681312)
-      (xy -2.96751 6.62656)
-      (xy -2.983349 6.606457)
-      (xy -3.019647 6.567291)
-      (xy -4.022427 6.567291)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp a6941334-7034-497c-8a20-52aecbb7900c))
-  (fp_poly
-    (pts
-      (xy 1.564704 10.743626)
-      (xy 1.540713 10.749212)
-      (xy 1.537577 10.752519)
-      (xy 1.52803 10.767868)
-      (xy 1.502975 10.798773)
-      (xy 1.467279 10.839317)
-      (xy 1.45637 10.851233)
-      (xy 1.417065 10.895946)
-      (xy 1.385842 10.93542)
-      (xy 1.368339 10.962425)
-      (xy 1.366898 10.965948)
-      (xy 1.354054 10.988498)
-      (xy 1.345577 10.993049)
-      (xy 1.33162 11.005228)
-      (xy 1.326089 11.018952)
-      (xy 1.323176 11.016237)
-      (xy 1.320551 10.988772)
-      (xy 1.318541 10.941412)
-      (xy 1.317603 10.893136)
-      (xy 1.315886 10.741417)
-      (xy 1.182669 10.741417)
-      (xy 1.182669 11.30559)
-      (xy 1.245449 11.301039)
-      (xy 1.288676 11.294246)
-      (xy 1.309401 11.279962)
-      (xy 1.313449 11.268993)
-      (xy 1.326663 11.241093)
-      (xy 1.352993 11.205989)
-      (xy 1.361233 11.19696)
-      (xy 1.391066 11.160717)
-      (xy 1.411381 11.127015)
-      (xy 1.413765 11.120841)
-      (xy 1.43324 11.084205)
-      (xy 1.448048 11.067058)
-      (xy 1.473908 11.0399)
-      (xy 1.503477 11.004306)
-      (xy 1.505138 11.002154)
-      (xy 1.537914 10.959453)
-      (xy 1.537914 11.303888)
-      (xy 1.67113 11.303888)
-      (xy 1.67113 10.741417)
-      (xy 1.604522 10.741417)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp bc3f0bf6-28f2-4440-b028-2dd6afa4e574))
-  (fp_poly
-    (pts
-      (xy -1.645974 6.56739)
-      (xy -1.749595 6.568698)
-      (xy -1.84418 6.570822)
-      (xy -1.925434 6.573761)
-      (xy -1.989067 6.577515)
-      (xy -2.030786 6.582084)
-      (xy -2.04542 6.586264)
-      (xy -2.056675 6.595409)
-      (xy -2.066368 6.605733)
-      (xy -2.074617 6.619385)
-      (xy -2.081538 6.63851)
-      (xy -2.087247 6.665256)
-      (xy -2.091862 6.701769)
-      (xy -2.095498 6.750197)
-      (xy -2.098272 6.812685)
-      (xy -2.100301 6.891381)
-      (xy -2.101701 6.988431)
-      (xy -2.102589 7.105983)
-      (xy -2.103081 7.246183)
-      (xy -2.103294 7.411178)
-      (xy -2.103344 7.603114)
-      (xy -2.103345 7.65343)
-      (xy -2.103345 8.637902)
-      (xy -2.070041 8.676231)
-      (xy -2.027611 8.708042)
-      (xy -1.984111 8.722931)
-      (xy -1.942762 8.724338)
-      (xy -1.907812 8.709592)
-      (xy -1.884199 8.691512)
-      (xy -1.836912 8.651723)
-      (xy -1.836912 6.833725)
-      (xy -1.035334 6.833725)
-      (xy -0.992067 6.790458)
-      (xy -0.958228 6.738374)
-      (xy -0.95102 6.681404)
-      (xy -0.969945 6.626504)
-      (xy -1.006724 6.586264)
-      (xy -1.028125 6.581052)
-      (xy -1.074826 6.576655)
-      (xy -1.142535 6.573073)
-      (xy -1.226959 6.570306)
-      (xy -1.323808 6.568354)
-      (xy -1.428788 6.567218)
-      (xy -1.537607 6.566896)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b75ec21e-4555-4046-8a5c-1aeb48d38187))
-  (fp_poly
-    (pts
-      (xy -6.824485 8.352117)
-      (xy -6.903552 8.354394)
-      (xy -6.964424 8.35862)
-      (xy -7.012796 8.36525)
-      (xy -7.054362 8.374739)
-      (xy -7.069371 8.379131)
-      (xy -7.226219 8.441174)
-      (xy -7.365751 8.52579)
-      (xy -7.382337 8.538179)
-      (xy -7.43474 8.58305)
-      (xy -7.462202 8.620086)
-      (xy -7.466943 8.653232)
-      (xy -7.458949 8.674455)
-      (xy -7.432829 8.695572)
-      (xy -7.39395 8.692092)
-      (xy -7.345098 8.664611)
-      (xy -7.321002 8.644928)
-      (xy -7.221737 8.572205)
-      (xy -7.107856 8.518543)
-      (xy -6.976488 8.483063)
-      (xy -6.824762 8.464891)
-      (xy -6.721527 8.46193)
-      (xy -6.586931 8.466101)
-      (xy -6.473561 8.48012)
-      (xy -6.374029 8.506242)
-      (xy -6.280945 8.546726)
-      (xy -6.186921 8.603829)
-      (xy -6.134735 8.64119)
-      (xy -6.083215 8.671999)
-      (xy -6.044279 8.679559)
-      (xy -6.02024 8.664272)
-      (xy -6.013412 8.626541)
-      (xy -6.013894 8.620164)
-      (xy -6.019427 8.595735)
-      (xy -6.033956 8.57306)
-      (xy -6.062287 8.54723)
-      (xy -6.109224 8.513335)
-      (xy -6.136272 8.495092)
-      (xy -6.212525 8.447102)
-      (xy -6.282494 8.410809)
-      (xy -6.35238 8.384687)
-      (xy -6.428385 8.367215)
-      (xy -6.516709 8.35687)
-      (xy -6.623554 8.352127)
-      (xy -6.721527 8.351333)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5302e35f-39e1-4d93-8bbd-8061922f4720))
-  (fp_poly
-    (pts
-      (xy -5.975381 3.835442)
-      (xy -5.99645 3.846163)
-      (xy -6.029204 3.868763)
-      (xy -6.079278 3.906181)
-      (xy -6.085047 3.910543)
-      (xy -6.222724 4.001488)
-      (xy -6.369089 4.074384)
-      (xy -6.469895 4.111304)
-      (xy -6.548856 4.129321)
-      (xy -6.645246 4.141623)
-      (xy -6.75098 4.148109)
-      (xy -6.857967 4.148674)
-      (xy -6.958121 4.143216)
-      (xy -7.043353 4.131632)
-      (xy -7.091574 4.119223)
-      (xy -7.208276 4.072343)
-      (xy -7.316718 4.015938)
-      (xy -7.407124 3.955204)
-      (xy -7.420555 3.944357)
-      (xy -7.476843 3.90452)
-      (xy -7.519503 3.89001)
-      (xy -7.548003 3.90084)
-      (xy -7.561812 3.93702)
-      (xy -7.562295 3.941307)
-      (xy -7.561811 3.968558)
-      (xy -7.550754 3.991686)
-      (xy -7.524001 4.017914)
-      (xy -7.488286 4.045661)
-      (xy -7.363001 4.129916)
-      (xy -7.240338 4.191512)
-      (xy -7.112516 4.233126)
-      (xy -6.971753 4.257434)
-      (xy -6.847343 4.266123)
-      (xy -6.723389 4.266828)
-      (xy -6.617476 4.259995)
-      (xy -6.563652 4.252093)
-      (xy -6.389648 4.206847)
-      (xy -6.226075 4.140604)
-      (xy -6.078737 4.056047)
-      (xy -5.985134 3.984616)
-      (xy -5.944991 3.94111)
-      (xy -5.923347 3.898785)
-      (xy -5.921684 3.863162)
-      (xy -5.941482 3.839761)
-      (xy -5.945765 3.837883)
-      (xy -5.960363 3.833662)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6677a626-c17a-47d0-9a31-191d0c08ae54))
-  (fp_poly
-    (pts
-      (xy -6.85108 -9.159572)
-      (xy -6.892287 -9.14313)
-      (xy -6.899149 -9.137487)
-      (xy -6.921105 -9.108183)
-      (xy -6.928753 -9.085681)
-      (xy -6.936746 -9.065983)
-      (xy -6.943555 -9.063478)
-      (xy -6.95627 -9.051471)
-      (xy -6.957064 -9.020696)
-      (xy -6.946935 -8.979023)
-      (xy -6.927316 -8.935104)
-      (xy -6.901453 -8.898026)
-      (xy -6.861438 -8.850498)
-      (xy -6.815181 -8.801809)
-      (xy -6.807216 -8.794036)
-      (xy -6.718156 -8.708233)
-      (xy -6.958357 -8.708233)
-      (xy -6.958357 -8.60462)
-      (xy -6.58831 -8.60462)
-      (xy -6.58831 -8.671229)
-      (xy -6.59125 -8.710952)
-      (xy -6.598689 -8.734781)
-      (xy -6.603112 -8.737837)
-      (xy -6.615999 -8.749927)
-      (xy -6.617914 -8.761561)
-      (xy -6.62794 -8.781907)
-      (xy -6.654788 -8.81647)
-      (xy -6.693614 -8.859291)
-      (xy -6.715025 -8.880973)
-      (xy -6.770643 -8.939903)
-      (xy -6.801932 -8.984059)
-      (xy -6.809166 -9.01513)
-      (xy -6.79262 -9.034803)
-      (xy -6.752569 -9.044768)
-      (xy -6.741849 -9.045738)
-      (xy -6.686691 -9.042405)
-      (xy -6.658192 -9.027632)
-      (xy -6.642256 -9.016208)
-      (xy -6.626636 -9.0214)
-      (xy -6.603943 -9.046731)
-      (xy -6.59567 -9.057446)
-      (xy -6.572796 -9.089346)
-      (xy -6.561154 -9.109439)
-      (xy -6.560912 -9.112556)
-      (xy -6.576138 -9.120555)
-      (xy -6.607212 -9.13688)
-      (xy -6.615413 -9.141188)
-      (xy -6.666045 -9.158653)
-      (xy -6.728504 -9.167457)
-      (xy -6.793334 -9.167722)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 7a9bb6d1-043c-4a25-847f-ef70548df104))
-  (fp_poly
-    (pts
-      (xy 3.626659 6.567762)
-      (xy 3.478049 6.568198)
-      (xy 3.356944 6.569255)
-      (xy 3.261249 6.571004)
-      (xy 3.188869 6.573519)
-      (xy 3.137711 6.576871)
-      (xy 3.10568 6.581133)
-      (xy 3.090827 6.586264)
-      (xy 3.05377 6.631225)
-      (xy 3.038143 6.686812)
-      (xy 3.04446 6.743725)
-      (xy 3.073233 6.792663)
-      (xy 3.079126 6.798389)
-      (xy 3.09007 6.806596)
-      (xy 3.105004 6.813098)
-      (xy 3.127363 6.818138)
-      (xy 3.160583 6.821964)
-      (xy 3.208101 6.824821)
-      (xy 3.273354 6.826955)
-      (xy 3.359777 6.828611)
-      (xy 3.470806 6.830037)
-      (xy 3.530294 6.830674)
-      (xy 3.950618 6.835025)
-      (xy 3.950618 7.738262)
-      (xy 3.950873 7.951262)
-      (xy 3.951636 8.137553)
-      (xy 3.952899 8.296712)
-      (xy 3.954655 8.428317)
-      (xy 3.956898 8.531944)
-      (xy 3.95962 8.607172)
-      (xy 3.962814 8.653577)
-      (xy 3.965858 8.669976)
-      (xy 3.99139 8.697855)
-      (xy 4.031094 8.724128)
-      (xy 4.071282 8.740579)
-      (xy 4.0868 8.742573)
-      (xy 4.1129 8.735472)
-      (xy 4.14637 8.720092)
-      (xy 4.180679 8.695056)
-      (xy 4.201877 8.669851)
-      (xy 4.205281 8.648369)
-      (xy 4.208265 8.59768)
-      (xy 4.210824 8.51818)
-      (xy 4.212952 8.410265)
-      (xy 4.214643 8.274328)
-      (xy 4.215892 8.110765)
-      (xy 4.216691 7.919972)
-      (xy 4.217037 7.702342)
-      (xy 4.217051 7.643418)
-      (xy 4.217051 6.645337)
-      (xy 4.139005 6.567291)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c48ff879-ad4f-4090-b3be-06319ac39015))
-  (fp_poly
-    (pts
-      (xy 5.948869 0.054471)
-      (xy 5.911865 0.054471)
-      (xy 5.88903 0.057232)
-      (xy 5.878211 0.070802)
-      (xy 5.875001 0.103113)
-      (xy 5.87486 0.121079)
-      (xy 5.876394 0.162182)
-      (xy 5.883933 0.181656)
-      (xy 5.901884 0.187433)
-      (xy 5.911865 0.187688)
-      (xy 5.933827 0.190087)
-      (xy 5.944783 0.202333)
-      (xy 5.948519 0.231995)
-      (xy 5.948869 0.261697)
-      (xy 5.948869 0.335706)
-      (xy 6.11169 0.335706)
-      (xy 6.11169 0.187688)
-      (xy 6.407727 0.187688)
-      (xy 6.407727 0.129365)
-      (xy 6.399374 0.079892)
-      (xy 6.385867 0.041495)
-      (xy 6.240491 0.041495)
-      (xy 6.231252 0.051253)
-      (xy 6.202192 0.05428)
-      (xy 6.179296 0.054471)
-      (xy 6.11169 0.054471)
-      (xy 6.11169 -0.138984)
-      (xy 6.159771 -0.082962)
-      (xy 6.189359 -0.049091)
-      (xy 6.21105 -0.025356)
-      (xy 6.216983 -0.019539)
-      (xy 6.228158 -0.000922)
-      (xy 6.236508 0.021167)
-      (xy 6.240491 0.041495)
-      (xy 6.385867 0.041495)
-      (xy 6.377327 0.01722)
-      (xy 6.34611 -0.048512)
-      (xy 6.310242 -0.107165)
-      (xy 6.291538 -0.131175)
-      (xy 6.26905 -0.160423)
-      (xy 6.257947 -0.180143)
-      (xy 6.24622 -0.198925)
-      (xy 6.220322 -0.233319)
-      (xy 6.185418 -0.276522)
-      (xy 6.178298 -0.285042)
-      (xy 6.140194 -0.329361)
-      (xy 6.112756 -0.355636)
-      (xy 6.087811 -0.368658)
-      (xy 6.057184 -0.373216)
-      (xy 6.026579 -0.373952)
-      (xy 5.948869 -0.374783)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f1569867-b13c-456f-a0a8-104ec866d6f1))
-  (fp_poly
-    (pts
-      (xy 6.230105 1.120205)
-      (xy 6.229764 1.191462)
-      (xy 6.228122 1.238234)
-      (xy 6.224247 1.265641)
-      (xy 6.21721 1.278799)
-      (xy 6.20608 1.282825)
-      (xy 6.200501 1.283026)
-      (xy 6.181133 1.287991)
-      (xy 6.172573 1.308059)
-      (xy 6.170897 1.342233)
-      (xy 6.17338 1.380969)
-      (xy 6.183414 1.398088)
-      (xy 6.200501 1.40144)
-      (xy 6.219001 1.405799)
-      (xy 6.227749 1.423895)
-      (xy 6.230093 1.463264)
-      (xy 6.230105 1.468049)
-      (xy 6.230105 1.534657)
-      (xy 6.363322 1.534657)
-      (xy 6.363322 1.40144)
-      (xy 6.585349 1.40144)
-      (xy 6.585349 1.34817)
-      (xy 6.580337 1.307158)
-      (xy 6.573553 1.283026)
-      (xy 6.454149 1.283026)
-      (xy 6.408735 1.283026)
-      (xy 6.381364 1.281365)
-      (xy 6.368106 1.27116)
-      (xy 6.363951 1.24458)
-      (xy 6.363772 1.212717)
-      (xy 6.364977 1.172531)
-      (xy 6.368944 1.158179)
-      (xy 6.377242 1.165911)
-      (xy 6.380831 1.172012)
-      (xy 6.401394 1.205664)
-      (xy 6.425794 1.24232)
-      (xy 6.454149 1.283026)
-      (xy 6.573553 1.283026)
-      (xy 6.567704 1.262222)
-      (xy 6.551061 1.222737)
-      (xy 6.534017 1.198072)
-      (xy 6.52606 1.194214)
-      (xy 6.514467 1.181642)
-      (xy 6.504738 1.155121)
-      (xy 6.48981 1.125176)
-      (xy 6.459867 1.08349)
-      (xy 6.421242 1.038835)
-      (xy 6.419221 1.036707)
-      (xy 6.377029 0.994615)
-      (xy 6.345727 0.970552)
-      (xy 6.317337 0.95974)
-      (xy 6.28681 0.957385)
-      (xy 6.230105 0.957385)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f7eeec86-c5f2-4572-9e33-af5a37c45b52))
-  (fp_poly
-    (pts
-      (xy 6.74817 3.658725)
-      (xy 6.747577 3.733474)
-      (xy 6.745397 3.783244)
-      (xy 6.741028 3.812645)
-      (xy 6.73387 3.826284)
-      (xy 6.725967 3.828946)
-      (xy 6.709546 3.84018)
-      (xy 6.703805 3.876035)
-      (xy 6.703764 3.880753)
-      (xy 6.708579 3.91907)
-      (xy 6.723945 3.932466)
-      (xy 6.725967 3.932559)
-      (xy 6.740601 3.941276)
-      (xy 6.747267 3.970916)
-      (xy 6.74817 3.999168)
-      (xy 6.74817 4.065776)
-      (xy 6.896189 4.065776)
-      (xy 6.896189 3.932559)
-      (xy 7.118217 3.932559)
-      (xy 7.118217 3.879289)
-      (xy 7.113204 3.838277)
-      (xy 7.108066 3.820001)
-      (xy 6.993941 3.820001)
-      (xy 6.987127 3.827288)
-      (xy 6.956207 3.828936)
-      (xy 6.950289 3.828946)
-      (xy 6.896189 3.828946)
-      (xy 6.896244 3.751237)
-      (xy 6.896299 3.673527)
-      (xy 6.92746 3.725333)
-      (xy 6.953544 3.765702)
-      (xy 6.977851 3.798731)
-      (xy 6.981506 3.803043)
-      (xy 6.993941 3.820001)
-      (xy 7.108066 3.820001)
-      (xy 7.100571 3.793341)
-      (xy 7.083929 3.753856)
-      (xy 7.066885 3.729191)
-      (xy 7.058927 3.725333)
-      (xy 7.04717 3.712809)
-      (xy 7.038129 3.688329)
-      (xy 7.026243 3.660606)
-      (xy 7.014322 3.651324)
-      (xy 7.000732 3.639685)
-      (xy 6.999802 3.633382)
-      (xy 6.990087 3.613891)
-      (xy 6.964904 3.581721)
-      (xy 6.937512 3.551972)
-      (xy 6.898505 3.515214)
-      (xy 6.867297 3.496073)
-      (xy 6.833113 3.489114)
-      (xy 6.811697 3.488503)
-      (xy 6.74817 3.488503)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f5c14ceb-6788-40cb-8f0f-a940ffa26146))
-  (fp_poly
-    (pts
-      (xy 6.230105 -1.410914)
-      (xy 6.229764 -1.339657)
-      (xy 6.228122 -1.292884)
-      (xy 6.224247 -1.265478)
-      (xy 6.21721 -1.25232)
-      (xy 6.20608 -1.248294)
-      (xy 6.200501 -1.248093)
-      (xy 6.181133 -1.243128)
-      (xy 6.172573 -1.22306)
-      (xy 6.170897 -1.188886)
-      (xy 6.17338 -1.15015)
-      (xy 6.183414 -1.133031)
-      (xy 6.200501 -1.129678)
-      (xy 6.219001 -1.12532)
-      (xy 6.227749 -1.107224)
-      (xy 6.230093 -1.067855)
-      (xy 6.230105 -1.06307)
-      (xy 6.230105 -0.996462)
-      (xy 6.363322 -0.996462)
-      (xy 6.363322 -1.129678)
-      (xy 6.589461 -1.129678)
-      (xy 6.58122 -1.220565)
-      (xy 6.575889 -1.261409)
-      (xy 6.448932 -1.261409)
-      (xy 6.430138 -1.249783)
-      (xy 6.407727 -1.248093)
-      (xy 6.382773 -1.249308)
-      (xy 6.369643 -1.257701)
-      (xy 6.364716 -1.280401)
-      (xy 6.364373 -1.324533)
-      (xy 6.36449 -1.333204)
-      (xy 6.366379 -1.374513)
-      (xy 6.370123 -1.396692)
-      (xy 6.374194 -1.396112)
-      (xy 6.388453 -1.37009)
-      (xy 6.412554 -1.334648)
-      (xy 6.417431 -1.328106)
-      (xy 6.44458 -1.286552)
-      (xy 6.448932 -1.261409)
-      (xy 6.575889 -1.261409)
-      (xy 6.574791 -1.269823)
-      (xy 6.566381 -1.306299)
-      (xy 6.559174 -1.320478)
-      (xy 6.543793 -1.337497)
-      (xy 6.519988 -1.370803)
-      (xy 6.505648 -1.392915)
-      (xy 6.470371 -1.4423)
-      (xy 6.426738 -1.494414)
-      (xy 6.407224 -1.51503)
-      (xy 6.367483 -1.550789)
-      (xy 6.334073 -1.568453)
-      (xy 6.295643 -1.573675)
-      (xy 6.289312 -1.573734)
-      (xy 6.230105 -1.573734)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 12bcf80f-3e76-4bfa-a66a-88322f240ebf))
-  (fp_poly
-    (pts
-      (xy -5.818613 8.720963)
-      (xy -5.819206 8.795712)
-      (xy -5.821387 8.845482)
-      (xy -5.825755 8.874883)
-      (xy -5.832913 8.888522)
-      (xy -5.840816 8.891184)
-      (xy -5.856254 8.900961)
-      (xy -5.862616 8.93337)
-      (xy -5.863019 8.950392)
-      (xy -5.859353 8.99156)
-      (xy -5.847199 9.008524)
-      (xy -5.840816 9.009599)
-      (xy -5.825378 9.019376)
-      (xy -5.819016 9.051785)
-      (xy -5.818613 9.068806)
-      (xy -5.818613 9.128014)
-      (xy -5.670595 9.128014)
-      (xy -5.670595 9.009599)
-      (xy -5.448567 9.009599)
-      (xy -5.448567 8.936823)
-      (xy -5.450625 8.893818)
-      (xy -5.451108 8.891184)
-      (xy -5.565308 8.891184)
-      (xy -5.670595 8.891184)
-      (xy -5.670595 8.822282)
-      (xy -5.669742 8.781467)
-      (xy -5.665282 8.765244)
-      (xy -5.654359 8.76861)
-      (xy -5.644691 8.776883)
-      (xy -5.61901 8.806208)
-      (xy -5.592775 8.844558)
-      (xy -5.592048 8.845785)
-      (xy -5.565308 8.891184)
-      (xy -5.451108 8.891184)
-      (xy -5.455873 8.865206)
-      (xy -5.459668 8.859113)
-      (xy -5.472492 8.84392)
-      (xy -5.49179 8.811421)
-      (xy -5.500337 8.794972)
-      (xy -5.52274 8.753936)
-      (xy -5.543202 8.722536)
-      (xy -5.548443 8.716205)
-      (xy -5.564622 8.688281)
-      (xy -5.566982 8.6755)
-      (xy -5.574948 8.656485)
-      (xy -5.581111 8.654354)
-      (xy -5.601302 8.644096)
-      (xy -5.629355 8.619837)
-      (xy -5.655497 8.591352)
-      (xy -5.669951 8.568418)
-      (xy -5.670595 8.56487)
-      (xy -5.683908 8.55681)
-      (xy -5.717948 8.551694)
-      (xy -5.744604 8.550741)
-      (xy -5.818613 8.550741)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 79e2044a-a2dd-40a2-bd7c-60ef93b7a33b))
-  (fp_poly
-    (pts
-      (xy -6.35148 -2.846695)
-      (xy -6.348818 -2.804477)
-      (xy -6.34201 -2.77768)
-      (xy -6.336678 -2.772685)
-      (xy -6.323284 -2.760814)
-      (xy -6.321877 -2.752066)
-      (xy -6.309937 -2.729216)
-      (xy -6.299674 -2.722927)
-      (xy -6.282777 -2.703213)
-      (xy -6.277471 -2.676938)
-      (xy -6.273705 -2.648814)
-      (xy -6.26637 -2.639299)
-      (xy -6.252938 -2.625993)
-      (xy -6.233465 -2.590371)
-      (xy -6.210533 -2.538433)
-      (xy -6.186723 -2.476183)
-      (xy -6.16462 -2.409623)
-      (xy -6.15817 -2.387837)
-      (xy -6.144251 -2.344988)
-      (xy -6.131217 -2.314061)
-      (xy -6.126879 -2.307167)
-      (xy -6.118386 -2.283618)
-      (xy -6.114658 -2.24599)
-      (xy -6.114651 -2.244259)
-      (xy -6.114651 -2.195413)
-      (xy -5.95183 -2.195413)
-      (xy -5.95183 -2.253747)
-      (xy -5.955271 -2.29316)
-      (xy -5.963817 -2.318423)
-      (xy -5.966632 -2.321229)
-      (xy -5.976642 -2.340911)
-      (xy -5.981376 -2.376781)
-      (xy -5.981434 -2.38131)
-      (xy -5.984729 -2.41521)
-      (xy -5.992816 -2.431885)
-      (xy -5.994344 -2.432243)
-      (xy -6.004681 -2.445275)
-      (xy -6.014279 -2.477644)
-      (xy -6.016216 -2.488288)
-      (xy -6.028465 -2.534794)
-      (xy -6.049575 -2.59024)
-      (xy -6.062451 -2.617805)
-      (xy -6.083343 -2.66344)
-      (xy -6.096896 -2.701592)
-      (xy -6.099787 -2.717178)
-      (xy -6.106822 -2.739146)
-      (xy -6.114651 -2.743082)
-      (xy -6.129022 -2.754346)
-      (xy -6.129452 -2.757884)
-      (xy -6.115427 -2.764865)
-      (xy -6.076381 -2.76988)
-      (xy -6.016861 -2.77245)
-      (xy -5.988835 -2.772685)
-      (xy -5.848217 -2.772685)
-      (xy -5.848217 -2.920704)
-      (xy -6.35148 -2.920704)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6c0cafe9-ddee-4b34-b3b3-477058d6f7bc))
-  (fp_poly
-    (pts
-      (xy -6.928753 -6.473152)
-      (xy -6.929094 -6.401895)
-      (xy -6.930736 -6.355122)
-      (xy -6.93461 -6.327716)
-      (xy -6.941647 -6.314558)
-      (xy -6.952777 -6.310532)
-      (xy -6.958357 -6.310331)
-      (xy -6.977725 -6.305366)
-      (xy -6.986284 -6.285298)
-      (xy -6.987961 -6.251124)
-      (xy -6.985478 -6.212388)
-      (xy -6.975444 -6.195268)
-      (xy -6.958357 -6.191916)
-      (xy -6.939857 -6.187558)
-      (xy -6.931109 -6.169461)
-      (xy -6.928764 -6.130093)
-      (xy -6.928753 -6.125308)
-      (xy -6.928753 -6.058699)
-      (xy -6.795536 -6.058699)
-      (xy -6.795536 -6.191916)
-      (xy -6.558706 -6.191916)
-      (xy -6.558475 -6.240022)
-      (xy -6.567451 -6.289426)
-      (xy -6.579577 -6.320485)
-      (xy -6.709714 -6.320485)
-      (xy -6.724391 -6.311552)
-      (xy -6.749404 -6.310331)
-      (xy -6.776197 -6.311616)
-      (xy -6.78968 -6.320441)
-      (xy -6.794115 -6.344263)
-      (xy -6.793819 -6.388041)
-      (xy -6.79182 -6.426132)
-      (xy -6.788436 -6.443866)
-      (xy -6.785467 -6.440543)
-      (xy -6.766986 -6.415385)
-      (xy -6.750179 -6.406241)
-      (xy -6.726716 -6.394542)
-      (xy -6.721325 -6.387043)
-      (xy -6.717693 -6.366103)
-      (xy -6.712198 -6.343635)
-      (xy -6.709714 -6.320485)
-      (xy -6.579577 -6.320485)
-      (xy -6.59173 -6.351615)
-      (xy -6.626758 -6.417415)
-      (xy -6.667982 -6.477651)
-      (xy -6.688223 -6.501453)
-      (xy -6.716705 -6.535708)
-      (xy -6.73396 -6.563291)
-      (xy -6.736329 -6.57145)
-      (xy -6.748614 -6.590023)
-      (xy -6.765933 -6.598967)
-      (xy -6.789854 -6.612256)
-      (xy -6.795536 -6.622168)
-      (xy -6.808768 -6.630401)
-      (xy -6.842245 -6.635339)
-      (xy -6.862145 -6.635972)
-      (xy -6.928753 -6.635972)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 01759509-2722-4a22-8621-c8215ba48fbd))
-  (fp_poly
-    (pts
-      (xy 1.934897 10.743948)
-      (xy 1.869328 10.746908)
-      (xy 1.815236 10.750805)
-      (xy 1.779154 10.755079)
-      (xy 1.767742 10.758287)
-      (xy 1.7669 10.777185)
-      (xy 1.778581 10.808824)
-      (xy 1.797153 10.842561)
-      (xy 1.816985 10.867752)
-      (xy 1.829291 10.874634)
-      (xy 1.847161 10.865678)
-      (xy 1.848753 10.859832)
-      (xy 1.862136 10.851726)
-      (xy 1.896659 10.84635)
-      (xy 1.930163 10.84503)
-      (xy 1.974746 10.847464)
-      (xy 2.004316 10.85374)
-      (xy 2.011573 10.859832)
-      (xy 2.023885 10.872114)
-      (xy 2.039327 10.874634)
-      (xy 2.06183 10.886578)
-      (xy 2.076681 10.923421)
-      (xy 2.084302 10.986679)
-      (xy 2.085583 11.039978)
-      (xy 2.075129 11.108105)
-      (xy 2.044774 11.155848)
-      (xy 1.996024 11.181454)
-      (xy 1.96044 11.185473)
-      (xy 1.90796 11.185473)
-      (xy 1.90796 10.993049)
-      (xy 1.759942 10.993049)
-      (xy 1.759942 11.285386)
-      (xy 1.806197 11.294637)
-      (xy 1.880737 11.303506)
-      (xy 1.961534 11.303433)
-      (xy 2.038345 11.295199)
-      (xy 2.100931 11.279583)
-      (xy 2.121167 11.270659)
-      (xy 2.164466 11.238996)
-      (xy 2.19263 11.202522)
-      (xy 2.194721 11.197641)
-      (xy 2.20926 11.168127)
-      (xy 2.222044 11.155869)
-      (xy 2.227134 11.142171)
-      (xy 2.23108 11.105478)
-      (xy 2.233309 11.052394)
-      (xy 2.233601 11.022653)
-      (xy 2.232049 10.958821)
-      (xy 2.227751 10.913287)
-      (xy 2.221248 10.890911)
-      (xy 2.218799 10.889436)
-      (xy 2.206512 10.877125)
-      (xy 2.203998 10.861716)
-      (xy 2.193365 10.83632)
-      (xy 2.166357 10.80316)
-      (xy 2.148491 10.786337)
-      (xy 2.092984 10.738679)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp afcd4397-6dd8-46be-8368-e1345145ff52))
-  (fp_poly
-    (pts
-      (xy 6.230105 6.189844)
-      (xy 6.229791 6.262981)
-      (xy 6.228268 6.311525)
-      (xy 6.224666 6.340484)
-      (xy 6.218113 6.354866)
-      (xy 6.207739 6.359681)
-      (xy 6.200501 6.360065)
-      (xy 6.180097 6.36586)
-      (xy 6.171865 6.388484)
-      (xy 6.170897 6.411872)
-      (xy 6.174209 6.447578)
-      (xy 6.187137 6.461985)
-      (xy 6.200501 6.463678)
-      (xy 6.219001 6.468036)
-      (xy 6.227749 6.486133)
-      (xy 6.230093 6.525502)
-      (xy 6.230105 6.530287)
-      (xy 6.230105 6.596895)
-      (xy 6.363322 6.596895)
-      (xy 6.363322 6.463678)
-      (xy 6.474335 6.463678)
-      (xy 6.530831 6.463166)
-      (xy 6.563951 6.460316)
-      (xy 6.579923 6.453157)
-      (xy 6.584972 6.439715)
-      (xy 6.585349 6.428524)
-      (xy 6.578 6.360065)
-      (xy 6.451546 6.360065)
-      (xy 6.407434 6.360065)
-      (xy 6.38163 6.358514)
-      (xy 6.368566 6.348852)
-      (xy 6.363908 6.323564)
-      (xy 6.363322 6.283589)
-      (xy 6.364244 6.241939)
-      (xy 6.366615 6.216899)
-      (xy 6.368699 6.21328)
-      (xy 6.378288 6.228685)
-      (xy 6.397198 6.261706)
-      (xy 6.412811 6.289756)
-      (xy 6.451546 6.360065)
-      (xy 6.578 6.360065)
-      (xy 6.577517 6.355565)
-      (xy 6.555868 6.29616)
-      (xy 6.539299 6.272898)
-      (xy 6.518611 6.246034)
-      (xy 6.51134 6.228735)
-      (xy 6.502027 6.210953)
-      (xy 6.477918 6.179508)
-      (xy 6.452528 6.150406)
-      (xy 6.420756 6.113475)
-      (xy 6.399194 6.084097)
-      (xy 6.393205 6.071429)
-      (xy 6.379659 6.053595)
-      (xy 6.346953 6.036161)
-      (xy 6.305269 6.023461)
-      (xy 6.271559 6.019622)
-      (xy 6.230105 6.019622)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e675c340-2e81-43d8-9217-88a9b3e94aa1))
-  (fp_poly
-    (pts
-      (xy 0.884145 10.743617)
-      (xy 0.798722 10.747297)
-      (xy 0.740644 10.752633)
-      (xy 0.707686 10.759908)
-      (xy 0.697888 10.767378)
-      (xy 0.682273 10.784552)
-      (xy 0.676194 10.785823)
-      (xy 0.650562 10.798708)
-      (xy 0.622803 10.831705)
-      (xy 0.598429 10.876322)
-      (xy 0.582953 10.924071)
-      (xy 0.581676 10.931396)
-      (xy 0.575954 11.007554)
-      (xy 0.580536 11.080565)
-      (xy 0.593928 11.144768)
-      (xy 0.614635 11.194504)
-      (xy 0.641162 11.224109)
-      (xy 0.660492 11.229879)
-      (xy 0.677992 11.238032)
-      (xy 0.679405 11.242994)
-      (xy 0.693356 11.263757)
-      (xy 0.731908 11.281461)
-      (xy 0.790111 11.294811)
-      (xy 0.863017 11.302515)
-      (xy 0.912305 11.303888)
-      (xy 0.972211 11.302849)
-      (xy 1.020371 11.300072)
-      (xy 1.049478 11.296062)
-      (xy 1.054386 11.29402)
-      (xy 1.057515 11.276749)
-      (xy 1.060234 11.234715)
-      (xy 1.062377 11.172757)
-      (xy 1.063773 11.095716)
-      (xy 1.064254 11.011226)
-      (xy 1.064254 10.84503)
-      (xy 0.931037 10.84503)
-      (xy 0.931037 11.189497)
-      (xy 0.862222 11.180065)
-      (xy 0.816635 11.171029)
-      (xy 0.782002 11.159251)
-      (xy 0.773718 11.154292)
-      (xy 0.749902 11.124927)
-      (xy 0.729719 11.083437)
-      (xy 0.715018 11.037445)
-      (xy 0.707651 10.994579)
-      (xy 0.709469 10.962462)
-      (xy 0.72232 10.948721)
-      (xy 0.723811 10.948643)
-      (xy 0.737861 10.937133)
-      (xy 0.738613 10.931863)
-      (xy 0.751594 10.903926)
-      (xy 0.784342 10.876228)
-      (xy 0.827565 10.854661)
-      (xy 0.871971 10.845116)
-      (xy 0.87553 10.845048)
-      (xy 0.931037 10.84503)
-      (xy 1.064254 10.84503)
-      (xy 1.064254 10.738299)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 67b8c206-43e5-4ddf-a457-cef8799f222f))
-  (fp_poly
-    (pts
-      (xy 6.743581 8.554729)
-      (xy 6.695672 8.565963)
-      (xy 6.669859 8.587105)
-      (xy 6.662647 8.620348)
-      (xy 6.665641 8.646193)
-      (xy 6.677935 8.684275)
-      (xy 6.697931 8.698353)
-      (xy 6.703562 8.69876)
-      (xy 6.731618 8.691808)
-      (xy 6.740769 8.683958)
-      (xy 6.759583 8.675679)
-      (xy 6.798078 8.670307)
-      (xy 6.829456 8.669156)
-      (xy 6.877388 8.670965)
-      (xy 6.903741 8.678146)
-      (xy 6.916411 8.693326)
-      (xy 6.918391 8.69876)
-      (xy 6.93168 8.722681)
-      (xy 6.941592 8.728364)
-      (xy 6.953844 8.740367)
-      (xy 6.955396 8.750566)
-      (xy 6.963389 8.770264)
-      (xy 6.970198 8.772769)
-      (xy 6.979025 8.785999)
-      (xy 6.984321 8.819472)
-      (xy 6.985 8.839378)
-      (xy 6.98206 8.879101)
-      (xy 6.974622 8.90293)
-      (xy 6.970198 8.905986)
-      (xy 6.957237 8.918046)
-      (xy 6.955396 8.929246)
-      (xy 6.941622 8.964898)
-      (xy 6.90343 8.991741)
-      (xy 6.851377 9.00561)
-      (xy 6.792576 9.013497)
-      (xy 6.792576 8.817175)
-      (xy 6.659359 8.817175)
-      (xy 6.659359 8.957792)
-      (xy 6.660153 9.024824)
-      (xy 6.66306 9.067244)
-      (xy 6.668861 9.090015)
-      (xy 6.678341 9.098101)
-      (xy 6.681562 9.09841)
-      (xy 6.701259 9.106403)
-      (xy 6.703764 9.113212)
-      (xy 6.717152 9.12208)
-      (xy 6.752317 9.126854)
-      (xy 6.801768 9.127856)
-      (xy 6.85801 9.12541)
-      (xy 6.913549 9.11984)
-      (xy 6.960893 9.111469)
-      (xy 6.992302 9.100757)
-      (xy 7.051627 9.057667)
-      (xy 7.091231 9.002929)
-      (xy 7.112697 8.932465)
-      (xy 7.117605 8.842193)
-      (xy 7.114168 8.786389)
-      (xy 7.094271 8.699515)
-      (xy 7.052354 8.632297)
-      (xy 6.988795 8.585034)
-      (xy 6.903974 8.558027)
-      (xy 6.81708 8.551212)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ed7644e4-3607-4c85-9fef-f8c4ef2c1603))
-  (fp_poly
-    (pts
-      (xy -1.437261 10.84503)
-      (xy -1.34845 10.84503)
-      (xy -1.298847 10.84611)
-      (xy -1.272044 10.850855)
-      (xy -1.261272 10.861522)
-      (xy -1.259639 10.874634)
-      (xy -1.25344 10.898686)
-      (xy -1.244837 10.904238)
-      (xy -1.230465 10.915502)
-      (xy -1.230035 10.91904)
-      (xy -1.243167 10.928309)
-      (xy -1.275971 10.933464)
-      (xy -1.289243 10.933841)
-      (xy -1.326318 10.937124)
-      (xy -1.34694 10.945325)
-      (xy -1.34845 10.948643)
-      (xy -1.360567 10.961461)
-      (xy -1.372617 10.963445)
-      (xy -1.407991 10.977037)
-      (xy -1.435055 11.013707)
-      (xy -1.450146 11.067298)
-      (xy -1.452063 11.097077)
-      (xy -1.448328 11.178257)
-      (xy -1.437021 11.231329)
-      (xy -1.41799 11.256844)
-      (xy -1.407041 11.259482)
-      (xy -1.381519 11.268088)
-      (xy -1.374565 11.27735)
-      (xy -1.357886 11.286291)
-      (xy -1.319689 11.29335)
-      (xy -1.268029 11.297992)
-      (xy -1.210961 11.299684)
-      (xy -1.15654 11.297894)
-      (xy -1.122722 11.294015)
-      (xy -1.096363 11.286178)
-      (xy -1.084738 11.26844)
-      (xy -1.082023 11.231337)
-      (xy -1.082016 11.22783)
-      (xy -1.082016 11.168541)
-      (xy -1.163158 11.178679)
-      (xy -1.239201 11.183453)
-      (xy -1.290245 11.175223)
-      (xy -1.318088 11.153575)
-      (xy -1.322959 11.141742)
-      (xy -1.318833 11.106457)
-      (xy -1.295102 11.073751)
-      (xy -1.260692 11.054112)
-      (xy -1.246801 11.052256)
-      (xy -1.221702 11.046405)
-      (xy -1.215233 11.037454)
-      (xy -1.202221 11.027671)
-      (xy -1.170226 11.02278)
-      (xy -1.163427 11.022653)
-      (xy -1.11162 11.022653)
-      (xy -1.11162 10.92644)
-      (xy -1.113712 10.876164)
-      (xy -1.119252 10.841742)
-      (xy -1.126422 10.830228)
-      (xy -1.136815 10.817366)
-      (xy -1.141223 10.786375)
-      (xy -1.141224 10.785823)
-      (xy -1.141224 10.741417)
-      (xy -1.437261 10.741417)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 30d3c4dc-9a70-4545-995c-17c307274103))
-  (fp_poly
-    (pts
-      (xy -5.960588 6.020319)
-      (xy -5.998827 6.02333)
-      (xy -6.020007 6.030037)
-      (xy -6.030394 6.041823)
-      (xy -6.03324 6.049226)
-      (xy -6.046529 6.073148)
-      (xy -6.056441 6.07883)
-      (xy -6.063501 6.0923)
-      (xy -6.068252 6.127434)
-      (xy -6.069621 6.171341)
-      (xy -6.068314 6.220791)
-      (xy -6.062112 6.254526)
-      (xy -6.046358 6.28304)
-      (xy -6.016394 6.316831)
-      (xy -5.99574 6.337862)
-      (xy -5.959293 6.376832)
-      (xy -5.933017 6.40902)
-      (xy -5.922378 6.427707)
-      (xy -5.922355 6.428112)
-      (xy -5.91038 6.446248)
-      (xy -5.888922 6.460415)
-      (xy -5.877562 6.468331)
-      (xy -5.885417 6.473374)
-      (xy -5.915858 6.476191)
-      (xy -5.97226 6.47743)
-      (xy -5.977733 6.477478)
-      (xy -6.099849 6.47848)
-      (xy -6.099849 6.596895)
-      (xy -5.726244 6.596895)
-      (xy -5.7324 6.511784)
-      (xy -5.743568 6.446978)
-      (xy -5.76488 6.396589)
-      (xy -5.793264 6.366295)
-      (xy -5.814502 6.360065)
-      (xy -5.831184 6.348124)
-      (xy -5.833415 6.337545)
-      (xy -5.845553 6.315163)
-      (xy -5.869281 6.298683)
-      (xy -5.900302 6.272194)
-      (xy -5.91486 6.243642)
-      (xy -5.927677 6.211108)
-      (xy -5.940602 6.195036)
-      (xy -5.947003 6.17966)
-      (xy -5.932511 6.16122)
-      (xy -5.904501 6.145452)
-      (xy -5.870344 6.138091)
-      (xy -5.867344 6.138037)
-      (xy -5.824897 6.149305)
-      (xy -5.803811 6.167641)
-      (xy -5.778661 6.192727)
-      (xy -5.756233 6.190807)
-      (xy -5.7333 6.160938)
-      (xy -5.724963 6.14456)
-      (xy -5.709926 6.108403)
-      (xy -5.709357 6.08686)
-      (xy -5.721165 6.070551)
-      (xy -5.745969 6.052821)
-      (xy -5.758348 6.049226)
-      (xy -5.773566 6.038584)
-      (xy -5.774208 6.034424)
-      (xy -5.788114 6.0272)
-      (xy -5.826325 6.022089)
-      (xy -5.88358 6.019715)
-      (xy -5.899026 6.019622)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp af1b774e-776a-4794-b122-33417304b335))
-  (fp_poly
-    (pts
-      (xy 2.873103 10.298813)
-      (xy 2.741926 10.349018)
-      (xy 2.62813 10.420609)
-      (xy 2.534764 10.511151)
-      (xy 2.463005 10.617107)
-      (xy 2.414028 10.734941)
-      (xy 2.389009 10.861117)
-      (xy 2.389126 10.992097)
-      (xy 2.415554 11.124347)
-      (xy 2.452259 11.219918)
-      (xy 2.519395 11.329856)
-      (xy 2.607599 11.422493)
-      (xy 2.712651 11.495926)
-      (xy 2.830334 11.548247)
-      (xy 2.956427 11.577552)
-      (xy 3.086712 11.581936)
-      (xy 3.208976 11.561699)
-      (xy 3.334459 11.514034)
-      (xy 3.44267 11.44533)
-      (xy 3.532686 11.359074)
-      (xy 3.603584 11.258751)
-      (xy 3.654442 11.147847)
-      (xy 3.684338 11.029848)
-      (xy 3.68845 10.967432)
-      (xy 3.574312 10.967432)
-      (xy 3.550623 11.084097)
-      (xy 3.499252 11.198284)
-      (xy 3.446442 11.275433)
-      (xy 3.365293 11.355039)
-      (xy 3.267326 11.414006)
-      (xy 3.158129 11.451044)
-      (xy 3.043294 11.464859)
-      (xy 2.928408 11.454159)
-      (xy 2.823083 11.419543)
-      (xy 2.720047 11.357206)
-      (xy 2.634306 11.276166)
-      (xy 2.56794 11.180815)
-      (xy 2.523026 11.075547)
-      (xy 2.501642 10.964753)
-      (xy 2.505866 10.852826)
-      (xy 2.522481 10.784102)
-      (xy 2.574445 10.667224)
-      (xy 2.645165 10.569711)
-      (xy 2.731101 10.492562)
-      (xy 2.828714 10.436774)
-      (xy 2.934464 10.403346)
-      (xy 3.044812 10.393277)
-      (xy 3.156219 10.407565)
-      (xy 3.265144 10.447209)
-      (xy 3.368049 10.513206)
-      (xy 3.396436 10.537578)
-      (xy 3.481383 10.633364)
-      (xy 3.539484 10.738988)
-      (xy 3.57053 10.85137)
-      (xy 3.574312 10.967432)
-      (xy 3.68845 10.967432)
-      (xy 3.69235 10.908241)
-      (xy 3.677554 10.78651)
-      (xy 3.63903 10.668143)
-      (xy 3.575853 10.556624)
-      (xy 3.498747 10.466543)
-      (xy 3.388006 10.377538)
-      (xy 3.267533 10.315869)
-      (xy 3.139866 10.281929)
-      (xy 3.007543 10.276112)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 81452d39-d598-40db-80a3-fdaab19cb2cd))
-  (fp_poly
-    (pts
-      (xy 5.885022 0.958365)
-      (xy 5.845209 0.962384)
-      (xy 5.819966 0.971056)
-      (xy 5.801794 0.985995)
-      (xy 5.798886 0.989253)
-      (xy 5.778468 1.019331)
-      (xy 5.771247 1.04106)
-      (xy 5.762475 1.059258)
-      (xy 5.756445 1.060998)
-      (xy 5.746052 1.07386)
-      (xy 5.741644 1.104851)
-      (xy 5.741643 1.105403)
-      (xy 5.745931 1.136582)
-      (xy 5.756261 1.149805)
-      (xy 5.756445 1.149809)
-      (xy 5.768722 1.162123)
-      (xy 5.771247 1.1776)
-      (xy 5.781997 1.210304)
-      (xy 5.79345 1.223818)
-      (xy 5.812207 1.247085)
-      (xy 5.815746 1.258935)
-      (xy 5.827503 1.276829)
-      (xy 5.856117 1.298468)
-      (xy 5.860409 1.300987)
-      (xy 5.893901 1.325817)
-      (xy 5.914359 1.351453)
-      (xy 5.914905 1.352793)
-      (xy 5.9352 1.384857)
-      (xy 5.947952 1.397269)
-      (xy 5.954598 1.406423)
-      (xy 5.943198 1.41203)
-      (xy 5.909799 1.414886)
-      (xy 5.856358 1.415772)
-      (xy 5.741643 1.416242)
-      (xy 5.741643 1.534657)
-      (xy 6.11169 1.534657)
-      (xy 6.11169 1.460648)
-      (xy 6.109027 1.41843)
-      (xy 6.10222 1.391633)
-      (xy 6.096888 1.386639)
-      (xy 6.083645 1.374698)
-      (xy 6.082086 1.365109)
-      (xy 6.071976 1.341206)
-      (xy 6.047255 1.311217)
-      (xy 6.043433 1.30755)
-      (xy 6.013662 1.279732)
-      (xy 5.992632 1.259966)
-      (xy 5.991373 1.258771)
-      (xy 5.949155 1.213519)
-      (xy 5.915768 1.16824)
-      (xy 5.896186 1.130332)
-      (xy 5.893256 1.112804)
-      (xy 5.909052 1.090567)
-      (xy 5.942479 1.078483)
-      (xy 5.982995 1.077609)
-      (xy 6.020058 1.089002)
-      (xy 6.033157 1.098765)
-      (xy 6.050136 1.1123)
-      (xy 6.065381 1.109638)
-      (xy 6.087115 1.087635)
-      (xy 6.098611 1.073764)
-      (xy 6.139295 1.023993)
-      (xy 6.103289 1.002062)
-      (xy 6.077175 0.982592)
-      (xy 6.067284 0.968758)
-      (xy 6.053643 0.963515)
-      (xy 6.017352 0.95955)
-      (xy 5.965357 0.957519)
-      (xy 5.946905 0.957385)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp eda9d8b4-0edc-4d9a-a912-4df73dc770f0))
-  (fp_poly
-    (pts
-      (xy 6.74495 6.020229)
-      (xy 6.70483 6.022904)
-      (xy 6.682141 6.02893)
-      (xy 6.670802 6.03959)
-      (xy 6.666654 6.049559)
-      (xy 6.661461 6.08893)
-      (xy 6.667878 6.125949)
-      (xy 6.682292 6.154325)
-      (xy 6.70109 6.167764)
-      (xy 6.720658 6.159976)
-      (xy 6.725967 6.152839)
-      (xy 6.744621 6.144879)
-      (xy 6.783504 6.139506)
-      (xy 6.822055 6.138037)
-      (xy 6.872326 6.139523)
-      (xy 6.900647 6.14553)
-      (xy 6.914592 6.158387)
-      (xy 6.918391 6.167641)
-      (xy 6.93168 6.191562)
-      (xy 6.941592 6.197245)
-      (xy 6.953844 6.209248)
-      (xy 6.955396 6.219447)
-      (xy 6.963389 6.239145)
-      (xy 6.970198 6.24165)
-      (xy 6.979025 6.25488)
-      (xy 6.984321 6.288353)
-      (xy 6.985 6.308259)
-      (xy 6.98206 6.347982)
-      (xy 6.974622 6.371811)
-      (xy 6.970198 6.374867)
-      (xy 6.958134 6.387252)
-      (xy 6.955396 6.404189)
-      (xy 6.942137 6.431752)
-      (xy 6.918391 6.442798)
-      (xy 6.890682 6.454226)
-      (xy 6.881387 6.465283)
-      (xy 6.868251 6.473548)
-      (xy 6.835439 6.478144)
-      (xy 6.822179 6.47848)
-      (xy 6.762972 6.47848)
-      (xy 6.762972 6.286056)
-      (xy 6.659359 6.286056)
-      (xy 6.659359 6.421341)
-      (xy 6.660715 6.495521)
-      (xy 6.667999 6.545045)
-      (xy 6.686032 6.57484)
-      (xy 6.719637 6.589833)
-      (xy 6.773634 6.594951)
-      (xy 6.82958 6.595278)
-      (xy 6.894154 6.593473)
-      (xy 6.939444 6.587448)
-      (xy 6.975703 6.574954)
-      (xy 7.010003 6.555752)
-      (xy 7.053654 6.524529)
-      (xy 7.082777 6.491284)
-      (xy 7.100157 6.449207)
-      (xy 7.108575 6.391492)
-      (xy 7.110815 6.311328)
-      (xy 7.110816 6.309127)
-      (xy 7.110049 6.2431)
-      (xy 7.106675 6.198803)
-      (xy 7.099084 6.168377)
-      (xy 7.085666 6.143964)
-      (xy 7.073811 6.12852)
-      (xy 7.027883 6.078811)
-      (xy 6.981799 6.046477)
-      (xy 6.927382 6.028161)
-      (xy 6.856455 6.020506)
-      (xy 6.808583 6.019622)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b0452eba-fd24-498d-adfb-4f313e153f15))
-  (fp_poly
-    (pts
-      (xy -4.799602 8.551229)
-      (xy -4.854629 8.557882)
-      (xy -4.889997 8.569244)
-      (xy -4.916442 8.583833)
-      (xy -4.927435 8.589614)
-      (xy -4.924489 8.602645)
-      (xy -4.911863 8.632943)
-      (xy -4.906191 8.645121)
-      (xy -4.88528 8.678007)
-      (xy -4.86344 8.697129)
-      (xy -4.846909 8.698729)
-      (xy -4.84169 8.683958)
-      (xy -4.828357 8.675614)
-      (xy -4.794174 8.670246)
-      (xy -4.765583 8.669156)
-      (xy -4.716065 8.671829)
-      (xy -4.68262 8.683259)
-      (xy -4.651939 8.708559)
-      (xy -4.645288 8.715394)
-      (xy -4.62121 8.742872)
-      (xy -4.608851 8.767722)
-      (xy -4.605466 8.800414)
-      (xy -4.608311 8.85142)
-      (xy -4.608621 8.855308)
-      (xy -4.618315 8.922623)
-      (xy -4.637236 8.966314)
-      (xy -4.669638 8.991942)
-      (xy -4.71978 9.005067)
-      (xy -4.723681 9.00561)
-      (xy -4.782483 9.013497)
-      (xy -4.782483 8.817175)
-      (xy -4.930501 8.817175)
-      (xy -4.930501 8.957792)
-      (xy -4.930054 9.023149)
-      (xy -4.927943 9.064397)
-      (xy -4.92301 9.087028)
-      (xy -4.9141 9.096535)
-      (xy -4.900898 9.09841)
-      (xy -4.876845 9.104609)
-      (xy -4.871294 9.113212)
-      (xy -4.85794 9.122099)
-      (xy -4.823168 9.127342)
-      (xy -4.774908 9.129163)
-      (xy -4.721091 9.127782)
-      (xy -4.66965 9.123419)
-      (xy -4.628515 9.116294)
-      (xy -4.605618 9.106628)
-      (xy -4.60486 9.105811)
-      (xy -4.57766 9.086856)
-      (xy -4.562343 9.083515)
-      (xy -4.540027 9.071207)
-      (xy -4.515183 9.041454)
-      (xy -4.494946 9.004793)
-      (xy -4.486447 8.971762)
-      (xy -4.486445 8.971395)
-      (xy -4.478058 8.952479)
-      (xy -4.471644 8.950392)
-      (xy -4.462765 8.93709)
-      (xy -4.457926 8.90257)
-      (xy -4.456905 8.854908)
-      (xy -4.459481 8.802183)
-      (xy -4.465432 8.75247)
-      (xy -4.474537 8.713846)
-      (xy -4.478381 8.704537)
-      (xy -4.517754 8.644784)
-      (xy -4.577937 8.585381)
-      (xy -4.588412 8.576644)
-      (xy -4.62096 8.56295)
-      (xy -4.673312 8.553995)
-      (xy -4.736011 8.55001)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 60e10e9d-1e1a-401f-90cb-ca5daef1a84d))
-  (fp_poly
-    (pts
-      (xy -5.052315 6.019665)
-      (xy -5.109258 6.025362)
-      (xy -5.149271 6.036209)
-      (xy -5.156784 6.040632)
-      (xy -5.172817 6.055529)
-      (xy -5.175008 6.072429)
-      (xy -5.163495 6.101983)
-      (xy -5.157743 6.114171)
-      (xy -5.136853 6.146986)
-      (xy -5.115022 6.166039)
-      (xy -5.098508 6.167573)
-      (xy -5.093322 6.152839)
-      (xy -5.079988 6.144495)
-      (xy -5.045806 6.139127)
-      (xy -5.017215 6.138037)
-      (xy -4.967425 6.140779)
-      (xy -4.933905 6.152265)
-      (xy -4.903573 6.177387)
-      (xy -4.8988 6.182308)
-      (xy -4.867465 6.230251)
-      (xy -4.855569 6.290965)
-      (xy -4.862264 6.369548)
-      (xy -4.865086 6.384532)
-      (xy -4.886742 6.425514)
-      (xy -4.928059 6.458635)
-      (xy -4.979108 6.476894)
-      (xy -4.998309 6.47848)
-      (xy -5.017566 6.476638)
-      (xy -5.028292 6.46666)
-      (xy -5.032974 6.441867)
-      (xy -5.034098 6.39558)
-      (xy -5.034114 6.382268)
-      (xy -5.034114 6.286056)
-      (xy -5.182133 6.286056)
-      (xy -5.182133 6.426674)
-      (xy -5.181338 6.493705)
-      (xy -5.178432 6.536125)
-      (xy -5.172631 6.558896)
-      (xy -5.16315 6.566982)
-      (xy -5.15993 6.567291)
-      (xy -5.140232 6.575284)
-      (xy -5.137727 6.582093)
-      (xy -5.124352 6.590696)
-      (xy -5.089426 6.595679)
-      (xy -5.040756 6.597267)
-      (xy -4.986143 6.595684)
-      (xy -4.933391 6.591155)
-      (xy -4.890305 6.583907)
-      (xy -4.864764 6.574221)
-      (xy -4.832967 6.556968)
-      (xy -4.812958 6.552396)
-      (xy -4.791268 6.540112)
-      (xy -4.766857 6.510446)
-      (xy -4.746779 6.473961)
-      (xy -4.738088 6.441218)
-      (xy -4.738077 6.440276)
-      (xy -4.72969 6.42136)
-      (xy -4.723275 6.419273)
-      (xy -4.714397 6.405971)
-      (xy -4.709558 6.371451)
-      (xy -4.708537 6.32379)
-      (xy -4.711112 6.271064)
-      (xy -4.717064 6.221351)
-      (xy -4.726169 6.182727)
-      (xy -4.730013 6.173418)
-      (xy -4.769385 6.113665)
-      (xy -4.829569 6.054262)
-      (xy -4.840044 6.045526)
-      (xy -4.872307 6.032049)
-      (xy -4.9246 6.023152)
-      (xy -4.987682 6.018976)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 69642b65-a4bc-4591-beed-cd8d19446055))
-  (fp_poly
-    (pts
-      (xy -6.342227 -6.634899)
-      (xy -6.396695 -6.631103)
-      (xy -6.442275 -6.624948)
-      (xy -6.471308 -6.616643)
-      (xy -6.474648 -6.614598)
-      (xy -6.491698 -6.598187)
-      (xy -6.49229 -6.57962)
-      (xy -6.478512 -6.549513)
-      (xy -6.463493 -6.523994)
-      (xy -6.446531 -6.511755)
-      (xy -6.418158 -6.509465)
-      (xy -6.375164 -6.513144)
-      (xy -6.302709 -6.516729)
-      (xy -6.252294 -6.50859)
-      (xy -6.218038 -6.486844)
-      (xy -6.197139 -6.456064)
-      (xy -6.184285 -6.418641)
-      (xy -6.176474 -6.373421)
-      (xy -6.17414 -6.329388)
-      (xy -6.177718 -6.295523)
-      (xy -6.187642 -6.280809)
-      (xy -6.18866 -6.280727)
-      (xy -6.201887 -6.26878)
-      (xy -6.203462 -6.259101)
-      (xy -6.216567 -6.226933)
-      (xy -6.249484 -6.198308)
-      (xy -6.292612 -6.180142)
-      (xy -6.317267 -6.177114)
-      (xy -6.366282 -6.177114)
-      (xy -6.366282 -6.38434)
-      (xy -6.499499 -6.38434)
-      (xy -6.499499 -6.236322)
-      (xy -6.498765 -6.167298)
-      (xy -6.496077 -6.122983)
-      (xy -6.490705 -6.098508)
-      (xy -6.481917 -6.089004)
-      (xy -6.477296 -6.088303)
-      (xy -6.457598 -6.080311)
-      (xy -6.455093 -6.073501)
-      (xy -6.441203 -6.066248)
-      (xy -6.4031 -6.061125)
-      (xy -6.346139 -6.058779)
-      (xy -6.332069 -6.058699)
-      (xy -6.267682 -6.059887)
-      (xy -6.225286 -6.064412)
-      (xy -6.19733 -6.073719)
-      (xy -6.177268 -6.088303)
-      (xy -6.148935 -6.109798)
-      (xy -6.128743 -6.117907)
-      (xy -6.105304 -6.129769)
-      (xy -6.079647 -6.157876)
-      (xy -6.060601 -6.191008)
-      (xy -6.055936 -6.210419)
-      (xy -6.048523 -6.2324)
-      (xy -6.040641 -6.236322)
-      (xy -6.033162 -6.250098)
-      (xy -6.02833 -6.287442)
-      (xy -6.026909 -6.342379)
-      (xy -6.026921 -6.343635)
-      (xy -6.030503 -6.413206)
-      (xy -6.040704 -6.462172)
-      (xy -6.056697 -6.495354)
-      (xy -6.078798 -6.532725)
-      (xy -6.093566 -6.563278)
-      (xy -6.094125 -6.564818)
-      (xy -6.113815 -6.585888)
-      (xy -6.14576 -6.599298)
-      (xy -6.176187 -6.610025)
-      (xy -6.18866 -6.622346)
-      (xy -6.202087 -6.63006)
-      (xy -6.237264 -6.634585)
-      (xy -6.28653 -6.636128)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b0d3ed8c-5f3d-45a1-a500-ae4c9916283c))
-  (fp_poly
-    (pts
-      (xy 6.773149 -1.572182)
-      (xy 6.727616 -1.567884)
-      (xy 6.70524 -1.561381)
-      (xy 6.703764 -1.558932)
-      (xy 6.691776 -1.545801)
-      (xy 6.681562 -1.544131)
-      (xy 6.662909 -1.537116)
-      (xy 6.662764 -1.513835)
-      (xy 6.681146 -1.470929)
-      (xy 6.681942 -1.469386)
-      (xy 6.70292 -1.441391)
-      (xy 6.726129 -1.426275)
-      (xy 6.743606 -1.42751)
-      (xy 6.74817 -1.440518)
-      (xy 6.761494 -1.448906)
-      (xy 6.795611 -1.454271)
-      (xy 6.823318 -1.455319)
-      (xy 6.8737 -1.452266)
-      (xy 6.908341 -1.439812)
-      (xy 6.940767 -1.413016)
-      (xy 6.941733 -1.412052)
-      (xy 6.966591 -1.383515)
-      (xy 6.979617 -1.354423)
-      (xy 6.984477 -1.313571)
-      (xy 6.985 -1.279833)
-      (xy 6.983537 -1.228766)
-      (xy 6.977699 -1.199817)
-      (xy 6.965307 -1.185582)
-      (xy 6.956153 -1.181725)
-      (xy 6.927739 -1.160816)
-      (xy 6.918151 -1.143723)
-      (xy 6.903927 -1.123776)
-      (xy 6.872903 -1.115633)
-      (xy 6.850786 -1.114877)
-      (xy 6.792576 -1.114877)
-      (xy 6.792576 -1.322103)
-      (xy 6.659359 -1.322103)
-      (xy 6.659359 -1.174084)
-      (xy 6.660093 -1.10506)
-      (xy 6.662781 -1.060745)
-      (xy 6.668153 -1.03627)
-      (xy 6.676941 -1.026766)
-      (xy 6.681562 -1.026065)
-      (xy 6.701259 -1.018073)
-      (xy 6.703764 -1.011263)
-      (xy 6.717672 -1.004023)
-      (xy 6.755924 -0.999127)
-      (xy 6.813312 -0.997176)
-      (xy 6.82588 -0.997187)
-      (xy 6.890764 -0.99885)
-      (xy 6.935243 -1.004189)
-      (xy 6.968463 -1.015129)
-      (xy 6.999569 -1.033592)
-      (xy 6.999802 -1.033753)
-      (xy 7.046741 -1.066208)
-      (xy 7.078195 -1.091111)
-      (xy 7.097248 -1.11539)
-      (xy 7.106986 -1.145976)
-      (xy 7.110495 -1.189796)
-      (xy 7.11086 -1.253781)
-      (xy 7.110816 -1.283053)
-      (xy 7.110816 -1.450135)
-      (xy 7.063848 -1.497133)
-      (xy 7.030243 -1.525857)
-      (xy 7.001312 -1.54248)
-      (xy 6.993539 -1.544131)
-      (xy 6.973122 -1.551782)
-      (xy 6.970198 -1.558932)
-      (xy 6.956225 -1.566025)
-      (xy 6.917545 -1.571084)
-      (xy 6.859018 -1.57357)
-      (xy 6.836981 -1.573734)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 31981ea9-5b82-41f2-b2d1-eaa70c62826c))
-  (fp_poly
-    (pts
-      (xy -6.342227 -9.166018)
-      (xy -6.396695 -9.162222)
-      (xy -6.442275 -9.156067)
-      (xy -6.471308 -9.147762)
-      (xy -6.474648 -9.145717)
-      (xy -6.491698 -9.129306)
-      (xy -6.49229 -9.110738)
-      (xy -6.478512 -9.080632)
-      (xy -6.463493 -9.055113)
-      (xy -6.446531 -9.042874)
-      (xy -6.418158 -9.040584)
-      (xy -6.375164 -9.044263)
-      (xy -6.302709 -9.047847)
-      (xy -6.252294 -9.039709)
-      (xy -6.218038 -9.017962)
-      (xy -6.197139 -8.987183)
-      (xy -6.184659 -8.950746)
-      (xy -6.176752 -8.905967)
-      (xy -6.173938 -8.861891)
-      (xy -6.176737 -8.82756)
-      (xy -6.18567 -8.81202)
-      (xy -6.187055 -8.811846)
-      (xy -6.200528 -8.799409)
-      (xy -6.208838 -8.778542)
-      (xy -6.230657 -8.746213)
-      (xy -6.271779 -8.720958)
-      (xy -6.321928 -8.708632)
-      (xy -6.332229 -8.708233)
-      (xy -6.350041 -8.710157)
-      (xy -6.360238 -8.720215)
-      (xy -6.364933 -8.744833)
-      (xy -6.366236 -8.790439)
-      (xy -6.366282 -8.811846)
-      (xy -6.366282 -8.915459)
-      (xy -6.499499 -8.915459)
-      (xy -6.499499 -8.769167)
-      (xy -6.499305 -8.701563)
-      (xy -6.495535 -8.655631)
-      (xy -6.483405 -8.627181)
-      (xy -6.458133 -8.612025)
-      (xy -6.414936 -8.605975)
-      (xy -6.349032 -8.604842)
-      (xy -6.311833 -8.604822)
-      (xy -6.242219 -8.606648)
-      (xy -6.197026 -8.61291)
-      (xy -6.171299 -8.62437)
-      (xy -6.168572 -8.626823)
-      (xy -6.141729 -8.645175)
-      (xy -6.126809 -8.649119)
-      (xy -6.107244 -8.661329)
-      (xy -6.084329 -8.690712)
-      (xy -6.06484 -8.726624)
-      (xy -6.055551 -8.758421)
-      (xy -6.055443 -8.761239)
-      (xy -6.047056 -8.780155)
-      (xy -6.040641 -8.782243)
-      (xy -6.030335 -8.795401)
-      (xy -6.025572 -8.829559)
-      (xy -6.025829 -8.876743)
-      (xy -6.03058 -8.928976)
-      (xy -6.039302 -8.978283)
-      (xy -6.05147 -9.01669)
-      (xy -6.056697 -9.026473)
-      (xy -6.078798 -9.063844)
-      (xy -6.093566 -9.094397)
-      (xy -6.094125 -9.095937)
-      (xy -6.113815 -9.117007)
-      (xy -6.14576 -9.130417)
-      (xy -6.176187 -9.141144)
-      (xy -6.18866 -9.153465)
-      (xy -6.202087 -9.161179)
-      (xy -6.237264 -9.165704)
-      (xy -6.28653 -9.167247)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 4f7ea564-4702-445a-9479-8306fc9d893f))
-  (fp_poly
-    (pts
-      (xy -6.321877 -5.303804)
-      (xy -6.070245 -5.303804)
-      (xy -6.07036 -5.255698)
-      (xy -6.076813 -5.2171)
-      (xy -6.100909 -5.193849)
-      (xy -6.110316 -5.18909)
-      (xy -6.151893 -5.175188)
-      (xy -6.18421 -5.170588)
-      (xy -6.210582 -5.165123)
-      (xy -6.218264 -5.155786)
-      (xy -6.230488 -5.143255)
-      (xy -6.244307 -5.140984)
-      (xy -6.266754 -5.133306)
-      (xy -6.291278 -5.107506)
-      (xy -6.321487 -5.05943)
-      (xy -6.332556 -5.039379)
-      (xy -6.343531 -5.006756)
-      (xy -6.349734 -4.964391)
-      (xy -6.350925 -4.921859)
-      (xy -6.346865 -4.888733)
-      (xy -6.337315 -4.874588)
-      (xy -6.336678 -4.87455)
-      (xy -6.323547 -4.862561)
-      (xy -6.321877 -4.852347)
-      (xy -6.313884 -4.83265)
-      (xy -6.307075 -4.830145)
-      (xy -6.29339 -4.818419)
-      (xy -6.292273 -4.811231)
-      (xy -6.282009 -4.788609)
-      (xy -6.258969 -4.763125)
-      (xy -6.239769 -4.749851)
-      (xy -6.214124 -4.741009)
-      (xy -6.175795 -4.735588)
-      (xy -6.118546 -4.732578)
-      (xy -6.062844 -4.731348)
-      (xy -5.993941 -4.730954)
-      (xy -5.934162 -4.731899)
-      (xy -5.890861 -4.733992)
-      (xy -5.873221 -4.736307)
-      (xy -5.857661 -4.747327)
-      (xy -5.853244 -4.771853)
-      (xy -5.859942 -4.814934)
-      (xy -5.872522 -4.863449)
-      (xy -5.889787 -4.88539)
-      (xy -5.914771 -4.887144)
-      (xy -5.929627 -4.87455)
-      (xy -5.948248 -4.866657)
-      (xy -5.987208 -4.861287)
-      (xy -6.027386 -4.859748)
-      (xy -6.081507 -4.861847)
-      (xy -6.11674 -4.870186)
-      (xy -6.143629 -4.887833)
-      (xy -6.152328 -4.89608)
-      (xy -6.177049 -4.926335)
-      (xy -6.188554 -4.951318)
-      (xy -6.18866 -4.952994)
-      (xy -6.176524 -4.981365)
-      (xy -6.148111 -5.007942)
-      (xy -6.115415 -5.022143)
-      (xy -6.109785 -5.022569)
-      (xy -6.088511 -5.02984)
-      (xy -6.085047 -5.037371)
-      (xy -6.071564 -5.045255)
-      (xy -6.036344 -5.0506)
-      (xy -5.996236 -5.052173)
-      (xy -5.907424 -5.052173)
-      (xy -5.907424 -5.116507)
-      (xy -5.908504 -5.161247)
-      (xy -5.911379 -5.224132)
-      (xy -5.915501 -5.293798)
-      (xy -5.917042 -5.316332)
-      (xy -5.926659 -5.451823)
-      (xy -6.321877 -5.451823)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 4fe1d722-c965-4031-a29f-a253b0039749))
-  (fp_poly
-    (pts
-      (xy 6.740148 0.958703)
-      (xy 6.695019 0.964711)
-      (xy 6.670528 0.978488)
-      (xy 6.662217 1.003111)
-      (xy 6.665623 1.041661)
-      (xy 6.668109 1.055584)
-      (xy 6.681743 1.091266)
-      (xy 6.701829 1.105753)
-      (xy 6.722526 1.095509)
-      (xy 6.725967 1.090601)
-      (xy 6.744758 1.082368)
-      (xy 6.78331 1.076994)
-      (xy 6.815652 1.075799)
-      (xy 6.881012 1.083679)
-      (xy 6.928099 1.105696)
-      (xy 6.95274 1.139421)
-      (xy 6.955396 1.15721)
-      (xy 6.963389 1.176908)
-      (xy 6.970198 1.179412)
-      (xy 6.979524 1.192531)
-      (xy 6.984655 1.225248)
-      (xy 6.985 1.237746)
-      (xy 6.981559 1.27716)
-      (xy 6.973013 1.302423)
-      (xy 6.970198 1.305228)
-      (xy 6.957722 1.326126)
-      (xy 6.955396 1.342825)
-      (xy 6.942008 1.369547)
-      (xy 6.918391 1.38056)
-      (xy 6.890682 1.391989)
-      (xy 6.881387 1.403045)
-      (xy 6.868251 1.41131)
-      (xy 6.835439 1.415906)
-      (xy 6.822179 1.416242)
-      (xy 6.762972 1.416242)
-      (xy 6.762972 1.209016)
-      (xy 6.659359 1.209016)
-      (xy 6.659359 1.351703)
-      (xy 6.660542 1.427623)
-      (xy 6.667129 1.478826)
-      (xy 6.68367 1.510184)
-      (xy 6.71472 1.526571)
-      (xy 6.76483 1.532862)
-      (xy 6.82958 1.533917)
-      (xy 6.891947 1.532886)
-      (xy 6.933548 1.528252)
-      (xy 6.963174 1.518087)
-      (xy 6.989617 1.500467)
-      (xy 6.992401 1.498239)
-      (xy 7.033299 1.465403)
-      (xy 7.07193 1.434694)
-      (xy 7.073811 1.433211)
-      (xy 7.090779 1.418029)
-      (xy 7.101576 1.400411)
-      (xy 7.107588 1.373764)
-      (xy 7.110205 1.331498)
-      (xy 7.110812 1.267021)
-      (xy 7.110816 1.257396)
-      (xy 7.109851 1.186041)
-      (xy 7.106354 1.138134)
-      (xy 7.099416 1.107566)
-      (xy 7.08813 1.088224)
-      (xy 7.085239 1.085133)
-      (xy 7.060301 1.057359)
-      (xy 7.048234 1.041022)
-      (xy 7.029116 1.020752)
-      (xy 6.996754 0.994679)
-      (xy 6.990116 0.989946)
-      (xy 6.962462 0.973753)
-      (xy 6.931048 0.963912)
-      (xy 6.887761 0.958956)
-      (xy 6.824487 0.957413)
-      (xy 6.810377 0.957385)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 4ababfc3-2d1e-4d9b-8c15-ab51bae3529f))
-  (fp_poly
-    (pts
-      (xy -4.800683 3.488547)
-      (xy -4.857626 3.494243)
-      (xy -4.89764 3.50509)
-      (xy -4.905152 3.509513)
-      (xy -4.921185 3.524411)
-      (xy -4.923376 3.54131)
-      (xy -4.911864 3.570864)
-      (xy -4.906111 3.583052)
-      (xy -4.885221 3.615867)
-      (xy -4.86339 3.63492)
-      (xy -4.846876 3.636455)
-      (xy -4.84169 3.62172)
-      (xy -4.828307 3.613614)
-      (xy -4.793784 3.608238)
-      (xy -4.76028 3.606918)
-      (xy -4.715697 3.609352)
-      (xy -4.686127 3.615629)
-      (xy -4.67887 3.62172)
-      (xy -4.666855 3.634792)
-      (xy -4.6563 3.636522)
-      (xy -4.632795 3.650024)
-      (xy -4.615807 3.686271)
-      (xy -4.606596 3.738874)
-      (xy -4.606427 3.801443)
-      (xy -4.613454 3.853414)
-      (xy -4.63511 3.894395)
-      (xy -4.676428 3.927517)
-      (xy -4.727476 3.945775)
-      (xy -4.746678 3.947361)
-      (xy -4.765391 3.945687)
-      (xy -4.776102 3.936369)
-      (xy -4.781037 3.912964)
-      (xy -4.782423 3.869028)
-      (xy -4.782483 3.843748)
-      (xy -4.782483 3.740135)
-      (xy -4.930501 3.740135)
-      (xy -4.930501 3.888154)
-      (xy -4.930095 3.955523)
-      (xy -4.928162 3.99865)
-      (xy -4.92363 4.022893)
-      (xy -4.915427 4.03361)
-      (xy -4.902483 4.03616)
-      (xy -4.900898 4.036172)
-      (xy -4.876845 4.042371)
-      (xy -4.871294 4.050974)
-      (xy -4.857966 4.059736)
-      (xy -4.823321 4.064676)
-      (xy -4.775362 4.066037)
-      (xy -4.722095 4.064065)
-      (xy -4.671525 4.059002)
-      (xy -4.631656 4.051093)
-      (xy -4.613133 4.043103)
-      (xy -4.581335 4.025849)
-      (xy -4.561326 4.021277)
-      (xy -4.539636 4.008993)
-      (xy -4.515225 3.979327)
-      (xy -4.495147 3.942842)
-      (xy -4.486457 3.910099)
-      (xy -4.486445 3.909157)
-      (xy -4.478058 3.890242)
-      (xy -4.471644 3.888154)
-      (xy -4.462765 3.874852)
-      (xy -4.457926 3.840332)
-      (xy -4.456905 3.792671)
-      (xy -4.459481 3.739945)
-      (xy -4.465432 3.690232)
-      (xy -4.474537 3.651609)
-      (xy -4.478381 3.6423)
-      (xy -4.517754 3.582546)
-      (xy -4.577937 3.523143)
-      (xy -4.588412 3.514407)
-      (xy -4.620675 3.50093)
-      (xy -4.672968 3.492033)
-      (xy -4.736051 3.487857)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 3b39cdd1-cc85-4052-bd8c-04713d7055ca))
-  (fp_poly
-    (pts
-      (xy -0.958908 4.3081)
-      (xy -1.020387 4.322994)
-      (xy -1.067198 4.344902)
-      (xy -1.093354 4.371443)
-      (xy -1.096818 4.385478)
-      (xy -1.105297 4.404219)
-      (xy -1.11162 4.406219)
-      (xy -1.119355 4.419813)
-      (xy -1.124651 4.455824)
-      (xy -1.126422 4.502431)
-      (xy -1.124485 4.551426)
-      (xy -1.119417 4.586079)
-      (xy -1.112618 4.598643)
-      (xy -1.098027 4.610966)
-      (xy -1.088298 4.631947)
-      (xy -1.076383 4.65794)
-      (xy -1.054461 4.683724)
-      (xy -1.01658 4.715507)
-      (xy -0.987006 4.737634)
-      (xy -0.960439 4.76089)
-      (xy -0.94882 4.778592)
-      (xy -0.9488 4.779046)
-      (xy -0.938893 4.797353)
-      (xy -0.914747 4.823998)
-      (xy -0.911795 4.826776)
-      (xy -0.886779 4.85245)
-      (xy -0.874937 4.869503)
-      (xy -0.87479 4.870475)
-      (xy -0.888519 4.874516)
-      (xy -0.92542 4.877687)
-      (xy -0.979065 4.879558)
-      (xy -1.015408 4.879879)
-      (xy -1.156026 4.879879)
-      (xy -1.156026 5.027897)
-      (xy -0.652762 5.027897)
-      (xy -0.652762 4.984365)
-      (xy -0.657325 4.950182)
-      (xy -0.667564 4.931685)
-      (xy -0.679956 4.910828)
-      (xy -0.682366 4.893513)
-      (xy -0.692826 4.855031)
-      (xy -0.720905 4.804766)
-      (xy -0.761653 4.750096)
-      (xy -0.81012 4.698394)
-      (xy -0.8185 4.690675)
-      (xy -0.881529 4.632065)
-      (xy -0.924234 4.587103)
-      (xy -0.949882 4.551553)
-      (xy -0.96174 4.521178)
-      (xy -0.963602 4.502544)
-      (xy -0.954314 4.471107)
-      (xy -0.9265 4.456678)
-      (xy -0.874378 4.452835)
-      (xy -0.81856 4.462389)
-      (xy -0.771959 4.482356)
-      (xy -0.755326 4.49624)
-      (xy -0.739376 4.512001)
-      (xy -0.726154 4.511583)
-      (xy -0.708342 4.49177)
-      (xy -0.691758 4.4683)
-      (xy -0.66846 4.432414)
-      (xy -0.65452 4.406567)
-      (xy -0.652762 4.400666)
-      (xy -0.665689 4.37619)
-      (xy -0.698076 4.352887)
-      (xy -0.740336 4.337639)
-      (xy -0.740715 4.337562)
-      (xy -0.772182 4.327605)
-      (xy -0.785954 4.315992)
-      (xy -0.785979 4.315558)
-      (xy -0.799523 4.309151)
-      (xy -0.835142 4.30452)
-      (xy -0.88532 4.302613)
-      (xy -0.888746 4.302606)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 70b4ee0a-1746-4797-9b3e-d7e5dabd3b8e))
-  (fp_poly
-    (pts
-      (xy -5.818613 9.838503)
-      (xy -5.570091 9.838503)
-      (xy -5.564602 9.89606)
-      (xy -5.559113 9.953616)
-      (xy -5.630259 9.962042)
-      (xy -5.708172 9.984049)
-      (xy -5.771219 10.030708)
-      (xy -5.817135 10.095234)
-      (xy -5.838169 10.145642)
-      (xy -5.847462 10.193701)
-      (xy -5.844073 10.23072)
-      (xy -5.833415 10.245555)
-      (xy -5.821837 10.266017)
-      (xy -5.818613 10.289836)
-      (xy -5.806959 10.323096)
-      (xy -5.789009 10.334366)
-      (xy -5.76511 10.34694)
-      (xy -5.759406 10.35588)
-      (xy -5.747348 10.369448)
-      (xy -5.717514 10.387704)
-      (xy -5.709063 10.391887)
-      (xy -5.66627 10.40385)
-      (xy -5.602968 10.411409)
-      (xy -5.527976 10.414205)
-      (xy -5.45011 10.411881)
-      (xy -5.384542 10.405066)
-      (xy -5.358596 10.399165)
-      (xy -5.348419 10.386033)
-      (xy -5.349836 10.356674)
-      (xy -5.352945 10.336975)
-      (xy -5.360758 10.296015)
-      (xy -5.367935 10.26832)
-      (xy -5.369737 10.264057)
-      (xy -5.389436 10.254591)
-      (xy -5.421149 10.253987)
-      (xy -5.448867 10.261559)
-      (xy -5.455968 10.267757)
-      (xy -5.47514 10.276751)
-      (xy -5.51267 10.282002)
-      (xy -5.53085 10.282559)
-      (xy -5.57027 10.279583)
-      (xy -5.593733 10.272062)
-      (xy -5.596585 10.267757)
-      (xy -5.608909 10.25551)
-      (xy -5.624584 10.252956)
-      (xy -5.65088 10.23981)
-      (xy -5.661054 10.219205)
-      (xy -5.664644 10.17328)
-      (xy -5.653258 10.13751)
-      (xy -5.629965 10.12024)
-      (xy -5.624463 10.119739)
-      (xy -5.601364 10.113198)
-      (xy -5.596585 10.104937)
-      (xy -5.583273 10.096493)
-      (xy -5.549235 10.091134)
-      (xy -5.522576 10.090135)
-      (xy -5.480358 10.087473)
-      (xy -5.453561 10.080665)
-      (xy -5.448567 10.075333)
-      (xy -5.436169 10.063307)
-      (xy -5.418963 10.060531)
-      (xy -5.404169 10.058043)
-      (xy -5.395324 10.046593)
-      (xy -5.390922 10.020206)
-      (xy -5.38946 9.972908)
-      (xy -5.389359 9.94299)
-      (xy -5.391104 9.886719)
-      (xy -5.395732 9.842572)
-      (xy -5.402335 9.818325)
-      (xy -5.404161 9.816301)
-      (xy -5.413622 9.796893)
-      (xy -5.418692 9.76008)
-      (xy -5.418963 9.748819)
-      (xy -5.418963 9.690485)
-      (xy -5.818613 9.690485)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 19c896ae-7d37-4399-89c9-01c4a1f21fc7))
-  (fp_poly
-    (pts
-      (xy -5.883349 0.958254)
-      (xy -5.937778 0.961875)
-      (xy -5.983292 0.968005)
-      (xy -6.012226 0.976477)
-      (xy -6.015292 0.978394)
-      (xy -6.031325 0.993292)
-      (xy -6.033516 1.010191)
-      (xy -6.022004 1.039746)
-      (xy -6.016251 1.051933)
-      (xy -5.995361 1.084748)
-      (xy -5.97353 1.103801)
-      (xy -5.957016 1.105336)
-      (xy -5.95183 1.090601)
-      (xy -5.938494 1.082271)
-      (xy -5.904292 1.076902)
-      (xy -5.875441 1.075799)
-      (xy -5.82664 1.078231)
-      (xy -5.794466 1.088922)
-      (xy -5.766108 1.112963)
-      (xy -5.757026 1.122871)
-      (xy -5.72893 1.161703)
-      (xy -5.716852 1.203506)
-      (xy -5.715 1.241286)
-      (xy -5.717756 1.282621)
-      (xy -5.724778 1.308373)
-      (xy -5.729802 1.312629)
-      (xy -5.742063 1.324948)
-      (xy -5.744604 1.340531)
-      (xy -5.757891 1.371298)
-      (xy -5.791752 1.397645)
-      (xy -5.837192 1.413793)
-      (xy -5.862498 1.416242)
-      (xy -5.907424 1.416242)
-      (xy -5.907424 1.209016)
-      (xy -6.040641 1.209016)
-      (xy -6.040641 1.357035)
-      (xy -6.039907 1.426059)
-      (xy -6.037219 1.470374)
-      (xy -6.031847 1.494849)
-      (xy -6.023059 1.504353)
-      (xy -6.018438 1.505054)
-      (xy -5.998741 1.513046)
-      (xy -5.996236 1.519855)
-      (xy -5.982345 1.527109)
-      (xy -5.944242 1.532231)
-      (xy -5.887281 1.534577)
-      (xy -5.873211 1.534657)
-      (xy -5.808824 1.53347)
-      (xy -5.766429 1.528945)
-      (xy -5.738472 1.519638)
-      (xy -5.71841 1.505054)
-      (xy -5.690768 1.483617)
-      (xy -5.67179 1.47545)
-      (xy -5.64806 1.463753)
-      (xy -5.621649 1.436122)
-      (xy -5.601739 1.403741)
-      (xy -5.596585 1.383848)
-      (xy -5.589814 1.361354)
-      (xy -5.581783 1.357035)
-      (xy -5.573513 1.34372)
-      (xy -5.5687 1.309289)
-      (xy -5.567218 1.262009)
-      (xy -5.568938 1.210152)
-      (xy -5.573735 1.161985)
-      (xy -5.581482 1.125778)
-      (xy -5.585484 1.116304)
-      (xy -5.61149 1.077758)
-      (xy -5.644705 1.038683)
-      (xy -5.677977 1.006474)
-      (xy -5.704153 0.988531)
-      (xy -5.710503 0.986988)
-      (xy -5.72826 0.977968)
-      (xy -5.729802 0.972186)
-      (xy -5.743232 0.964107)
-      (xy -5.77841 0.959203)
-      (xy -5.827671 0.957307)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 30fb5104-820e-4974-8f9e-cc081cfbbad1))
-  (fp_poly
-    (pts
-      (xy -6.342207 -1.572865)
-      (xy -6.396636 -1.569244)
-      (xy -6.44215 -1.563114)
-      (xy -6.471084 -1.554642)
-      (xy -6.47415 -1.552724)
-      (xy -6.490183 -1.537827)
-      (xy -6.492374 -1.520927)
-      (xy -6.480861 -1.491373)
-      (xy -6.475109 -1.479186)
-      (xy -6.454219 -1.446371)
-      (xy -6.432388 -1.427317)
-      (xy -6.415874 -1.425783)
-      (xy -6.410688 -1.440518)
-      (xy -6.397305 -1.448624)
-      (xy -6.362781 -1.454)
-      (xy -6.329278 -1.455319)
-      (xy -6.284695 -1.452886)
-      (xy -6.255124 -1.446609)
-      (xy -6.247867 -1.440518)
-      (xy -6.236169 -1.426685)
-      (xy -6.229365 -1.4256)
-      (xy -6.210504 -1.413426)
-      (xy -6.19236 -1.385645)
-      (xy -6.181433 -1.349774)
-      (xy -6.175429 -1.305762)
-      (xy -6.174554 -1.262971)
-      (xy -6.179017 -1.230764)
-      (xy -6.18866 -1.21849)
-      (xy -6.201887 -1.206542)
-      (xy -6.203462 -1.196863)
-      (xy -6.216567 -1.164695)
-      (xy -6.249484 -1.13607)
-      (xy -6.292612 -1.117904)
-      (xy -6.317267 -1.114877)
-      (xy -6.366282 -1.114877)
-      (xy -6.366282 -1.322103)
-      (xy -6.499499 -1.322103)
-      (xy -6.499499 -1.174084)
-      (xy -6.498765 -1.10506)
-      (xy -6.496077 -1.060745)
-      (xy -6.490705 -1.03627)
-      (xy -6.481917 -1.026766)
-      (xy -6.477296 -1.026065)
-      (xy -6.457598 -1.018073)
-      (xy -6.455093 -1.011263)
-      (xy -6.441203 -1.00401)
-      (xy -6.4031 -0.998888)
-      (xy -6.346139 -0.996541)
-      (xy -6.332069 -0.996462)
-      (xy -6.267682 -0.997649)
-      (xy -6.225286 -1.002174)
-      (xy -6.19733 -1.011481)
-      (xy -6.177268 -1.026065)
-      (xy -6.147318 -1.047693)
-      (xy -6.124373 -1.055669)
-      (xy -6.101082 -1.067853)
-      (xy -6.076655 -1.096896)
-      (xy -6.059204 -1.131536)
-      (xy -6.055443 -1.15136)
-      (xy -6.04761 -1.17139)
-      (xy -6.040641 -1.174084)
-      (xy -6.031593 -1.187381)
-      (xy -6.026727 -1.221919)
-      (xy -6.025798 -1.269669)
-      (xy -6.02856 -1.3226)
-      (xy -6.034769 -1.372683)
-      (xy -6.04418 -1.411888)
-      (xy -6.048196 -1.421577)
-      (xy -6.075287 -1.464709)
-      (xy -6.109453 -1.504542)
-      (xy -6.14328 -1.533524)
-      (xy -6.168475 -1.544131)
-      (xy -6.186841 -1.55281)
-      (xy -6.18866 -1.558932)
-      (xy -6.202089 -1.567012)
-      (xy -6.237268 -1.571916)
-      (xy -6.286529 -1.573812)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6e27e24e-9ebd-487a-8184-00b42f5d4870))
-  (fp_poly
-    (pts
-      (xy 5.906741 8.550686)
-      (xy 5.859432 8.55814)
-      (xy 5.833575 8.566266)
-      (xy 5.797078 8.590558)
-      (xy 5.776773 8.619914)
-      (xy 5.776463 8.62105)
-      (xy 5.764975 8.646966)
-      (xy 5.75484 8.654354)
-      (xy 5.749301 8.668109)
-      (xy 5.744906 8.705197)
-      (xy 5.742215 8.759353)
-      (xy 5.741643 8.802373)
-      (xy 5.74305 8.871135)
-      (xy 5.746988 8.920849)
-      (xy 5.753029 8.94725)
-      (xy 5.756445 8.950392)
-      (xy 5.769242 8.962517)
-      (xy 5.771247 8.974692)
-      (xy 5.784274 9.00903)
-      (xy 5.817967 9.044258)
-      (xy 5.864238 9.074208)
-      (xy 5.915002 9.092715)
-      (xy 5.929011 9.095017)
-      (xy 5.970239 9.102154)
-      (xy 5.997408 9.111483)
-      (xy 6.001889 9.115175)
-      (xy 6.021258 9.12509)
-      (xy 6.045955 9.128014)
-      (xy 6.069554 9.12448)
-      (xy 6.079831 9.108285)
-      (xy 6.082086 9.071037)
-      (xy 6.082086 9.070818)
-      (xy 6.080679 9.035943)
-      (xy 6.07123 9.017912)
-      (xy 6.045899 9.00911)
-      (xy 6.013527 9.004226)
-      (xy 5.951542 8.98701)
-      (xy 5.916011 8.961509)
-      (xy 5.887055 8.928189)
-      (xy 5.973469 8.916251)
-      (xy 6.049678 8.89765)
-      (xy 6.101278 8.864658)
-      (xy 6.130912 8.814444)
-      (xy 6.141223 8.744179)
-      (xy 6.141294 8.736567)
-      (xy 6.140542 8.722585)
-      (xy 5.993275 8.722585)
-      (xy 5.984869 8.77546)
-      (xy 5.958149 8.805956)
-      (xy 5.910863 8.816562)
-      (xy 5.908164 8.816612)
-      (xy 5.874744 8.813728)
-      (xy 5.86174 8.799643)
-      (xy 5.860058 8.781044)
-      (xy 5.865516 8.749702)
-      (xy 5.87486 8.735764)
-      (xy 5.887531 8.714775)
-      (xy 5.889662 8.69947)
-      (xy 5.902 8.671724)
-      (xy 5.932931 8.658816)
-      (xy 5.965756 8.662417)
-      (xy 5.98631 8.679571)
-      (xy 5.993221 8.717335)
-      (xy 5.993275 8.722585)
-      (xy 6.140542 8.722585)
-      (xy 6.138883 8.691735)
-      (xy 6.132658 8.661874)
-      (xy 6.126492 8.654354)
-      (xy 6.112289 8.642952)
-      (xy 6.11169 8.638495)
-      (xy 6.102182 8.615705)
-      (xy 6.090809 8.601755)
-      (xy 6.070693 8.576743)
-      (xy 6.064704 8.565203)
-      (xy 6.04732 8.554844)
-      (xy 6.009393 8.548998)
-      (xy 5.95963 8.547626)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 1d3a51e7-3f56-4ed2-9e64-5e0281ab475f))
-  (fp_poly
-    (pts
-      (xy 6.354734 8.554669)
-      (xy 6.309111 8.561749)
-      (xy 6.285622 8.569239)
-      (xy 6.25417 8.592489)
-      (xy 6.238468 8.617345)
-      (xy 6.231294 8.663784)
-      (xy 6.230971 8.715136)
-      (xy 6.236805 8.760331)
-      (xy 6.248099 8.788295)
-      (xy 6.249269 8.789504)
-      (xy 6.258708 8.806239)
-      (xy 6.248501 8.827817)
-      (xy 6.234467 8.844055)
-      (xy 6.210981 8.879572)
-      (xy 6.201343 8.925907)
-      (xy 6.200501 8.952553)
-      (xy 6.20292 8.994061)
-      (xy 6.209087 9.020012)
-      (xy 6.213577 9.024401)
-      (xy 6.227636 9.036649)
-      (xy 6.23386 9.051963)
-      (xy 6.25696 9.084399)
-      (xy 6.304566 9.108944)
-      (xy 6.372247 9.12396)
-      (xy 6.439605 9.128014)
-      (xy 6.491882 9.126018)
-      (xy 6.527906 9.120688)
-      (xy 6.540944 9.113212)
-      (xy 6.552933 9.10008)
-      (xy 6.563147 9.09841)
-      (xy 6.580849 9.09103)
-      (xy 6.583895 9.065728)
-      (xy 6.576039 9.028173)
-      (xy 6.568337 9.009157)
-      (xy 6.553226 9.000715)
-      (xy 6.52256 9.000611)
-      (xy 6.488605 9.004169)
-      (xy 6.416495 9.009084)
-      (xy 6.368907 9.002942)
-      (xy 6.342454 8.984561)
-      (xy 6.33375 8.952761)
-      (xy 6.333718 8.95011)
-      (xy 6.338436 8.917732)
-      (xy 6.355953 8.906409)
-      (xy 6.363322 8.905986)
-      (xy 6.387374 8.899787)
-      (xy 6.392925 8.891184)
-      (xy 6.405937 8.8814)
-      (xy 6.437933 8.87651)
-      (xy 6.444732 8.876382)
-      (xy 6.477902 8.87459)
-      (xy 6.492643 8.863522)
-      (xy 6.496422 8.834645)
-      (xy 6.496538 8.817175)
-      (xy 6.496538 8.757967)
-      (xy 6.435262 8.757967)
-      (xy 6.386 8.751371)
-      (xy 6.354825 8.734099)
-      (xy 6.345744 8.70993)
-      (xy 6.359044 8.686121)
-      (xy 6.388981 8.672373)
-      (xy 6.434032 8.667099)
-      (xy 6.480917 8.670392)
-      (xy 6.516359 8.682347)
-      (xy 6.519977 8.684983)
-      (xy 6.53683 8.689526)
-      (xy 6.554292 8.670433)
-      (xy 6.562225 8.656137)
-      (xy 6.58122 8.613119)
-      (xy 6.582037 8.589405)
-      (xy 6.564357 8.580687)
-      (xy 6.556619 8.580345)
-      (xy 6.528283 8.573548)
-      (xy 6.518741 8.565543)
-      (xy 6.498801 8.556655)
-      (xy 6.458723 8.551977)
-      (xy 6.407653 8.551363)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5cbb7acc-b138-4547-a5cf-0d9124a5ca43))
-  (fp_poly
-    (pts
-      (xy -6.342173 -4.103763)
-      (xy -6.396565 -4.100061)
-      (xy -6.442023 -4.094023)
-      (xy -6.470877 -4.085845)
-      (xy -6.47415 -4.083843)
-      (xy -6.490183 -4.068946)
-      (xy -6.492374 -4.052046)
-      (xy -6.480861 -4.022492)
-      (xy -6.475109 -4.010305)
-      (xy -6.454219 -3.977489)
-      (xy -6.432388 -3.958436)
-      (xy -6.415874 -3.956902)
-      (xy -6.410688 -3.971636)
-      (xy -6.397305 -3.979742)
-      (xy -6.362781 -3.985119)
-      (xy -6.329278 -3.986438)
-      (xy -6.284695 -3.984005)
-      (xy -6.255124 -3.977728)
-      (xy -6.247867 -3.971636)
-      (xy -6.236169 -3.957804)
-      (xy -6.229365 -3.956719)
-      (xy -6.210504 -3.944545)
-      (xy -6.19236 -3.916763)
-      (xy -6.181433 -3.880893)
-      (xy -6.175429 -3.836881)
-      (xy -6.174554 -3.79409)
-      (xy -6.179017 -3.761882)
-      (xy -6.18866 -3.749608)
-      (xy -6.201887 -3.737661)
-      (xy -6.203462 -3.727982)
-      (xy -6.216567 -3.695814)
-      (xy -6.249484 -3.667189)
-      (xy -6.292612 -3.649023)
-      (xy -6.317267 -3.645995)
-      (xy -6.366282 -3.645995)
-      (xy -6.366282 -3.853222)
-      (xy -6.499499 -3.853222)
-      (xy -6.499499 -3.705203)
-      (xy -6.498765 -3.636179)
-      (xy -6.496077 -3.591864)
-      (xy -6.490705 -3.567389)
-      (xy -6.481917 -3.557885)
-      (xy -6.477296 -3.557184)
-      (xy -6.457598 -3.549192)
-      (xy -6.455093 -3.542382)
-      (xy -6.441203 -3.535129)
-      (xy -6.4031 -3.530007)
-      (xy -6.346139 -3.52766)
-      (xy -6.332069 -3.527581)
-      (xy -6.267682 -3.528768)
-      (xy -6.225286 -3.533293)
-      (xy -6.19733 -3.5426)
-      (xy -6.177268 -3.557184)
-      (xy -6.148935 -3.578679)
-      (xy -6.128743 -3.586788)
-      (xy -6.105304 -3.59865)
-      (xy -6.079647 -3.626757)
-      (xy -6.060601 -3.659889)
-      (xy -6.055936 -3.6793)
-      (xy -6.048523 -3.701281)
-      (xy -6.040641 -3.705203)
-      (xy -6.033162 -3.718979)
-      (xy -6.02833 -3.756323)
-      (xy -6.026909 -3.81126)
-      (xy -6.026921 -3.812516)
-      (xy -6.030503 -3.882087)
-      (xy -6.040704 -3.931053)
-      (xy -6.056697 -3.964236)
-      (xy -6.078798 -4.001606)
-      (xy -6.093566 -4.032159)
-      (xy -6.094125 -4.033699)
-      (xy -6.113815 -4.05477)
-      (xy -6.14576 -4.068179)
-      (xy -6.176187 -4.078906)
-      (xy -6.18866 -4.091227)
-      (xy -6.202089 -4.098859)
-      (xy -6.237265 -4.10336)
-      (xy -6.286516 -4.104928)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 17a65922-fefd-4aeb-8969-b9336021b6bf))
-  (fp_poly
-    (pts
-      (xy -5.593688 -10.542654)
-      (xy -5.626723 -10.538146)
-      (xy -5.640952 -10.529424)
-      (xy -5.640991 -10.528863)
-      (xy -5.653987 -10.519012)
-      (xy -5.685876 -10.514165)
-      (xy -5.691924 -10.514061)
-      (xy -5.728793 -10.510139)
-      (xy -5.751 -10.500565)
-      (xy -5.752005 -10.499259)
-      (xy -5.772774 -10.487051)
-      (xy -5.791467 -10.484457)
-      (xy -5.813098 -10.478728)
-      (xy -5.811282 -10.458554)
-      (xy -5.798351 -10.425156)
-      (xy -5.78598 -10.391753)
-      (xy -5.771178 -10.350856)
-      (xy -5.49698 -10.37013)
-      (xy -5.447773 -10.323105)
-      (xy -5.418622 -10.291235)
-      (xy -5.402491 -10.258931)
-      (xy -5.394425 -10.214175)
-      (xy -5.392222 -10.188384)
-      (xy -5.389831 -10.117928)
-      (xy -5.396262 -10.066899)
-      (xy -5.413844 -10.025838)
-      (xy -5.441199 -9.989509)
-      (xy -5.468027 -9.963728)
-      (xy -5.498661 -9.949179)
-      (xy -5.543921 -9.941588)
-      (xy -5.567397 -9.939624)
-      (xy -5.655793 -9.93323)
-      (xy -5.655793 -10.18842)
-      (xy -5.818613 -10.18842)
-      (xy -5.818613 -10.003396)
-      (xy -5.818344 -9.926611)
-      (xy -5.817022 -9.87462)
-      (xy -5.813878 -9.842612)
-      (xy -5.808144 -9.82578)
-      (xy -5.799048 -9.819314)
-      (xy -5.789009 -9.818373)
-      (xy -5.764957 -9.812174)
-      (xy -5.759406 -9.803571)
-      (xy -5.745256 -9.796881)
-      (xy -5.705347 -9.791989)
-      (xy -5.643487 -9.789242)
-      (xy -5.597459 -9.788769)
-      (xy -5.528384 -9.790062)
-      (xy -5.472943 -9.793603)
-      (xy -5.436976 -9.798887)
-      (xy -5.426364 -9.803571)
-      (xy -5.4052 -9.816703)
-      (xy -5.392186 -9.818609)
-      (xy -5.360287 -9.830435)
-      (xy -5.320398 -9.860986)
-      (xy -5.279747 -9.903593)
-      (xy -5.245564 -9.95159)
-      (xy -5.242774 -9.956438)
-      (xy -5.227203 -9.989899)
-      (xy -5.217724 -10.027959)
-      (xy -5.213011 -10.078932)
-      (xy -5.211737 -10.150992)
-      (xy -5.213218 -10.212686)
-      (xy -5.217198 -10.262405)
-      (xy -5.222982 -10.293184)
-      (xy -5.226539 -10.299434)
-      (xy -5.239612 -10.320588)
-      (xy -5.241469 -10.333611)
-      (xy -5.253009 -10.363079)
-      (xy -5.282709 -10.401095)
-      (xy -5.323544 -10.440653)
-      (xy -5.368485 -10.474745)
-      (xy -5.400962 -10.492646)
-      (xy -5.443143 -10.511559)
-      (xy -5.47707 -10.527741)
-      (xy -5.48167 -10.530107)
-      (xy -5.511168 -10.538712)
-      (xy -5.551838 -10.542869)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 8214243f-07d9-4e32-9ce5-468d787b3cdb))
-  (fp_poly
-    (pts
-      (xy -3.085621 10.291383)
-      (xy -3.214054 10.332018)
-      (xy -3.329475 10.397234)
-      (xy -3.429009 10.484972)
-      (xy -3.509779 10.593173)
-      (xy -3.568911 10.719777)
-      (xy -3.57026 10.723661)
-      (xy -3.588729 10.803399)
-      (xy -3.597333 10.898621)
-      (xy -3.595875 10.996835)
-      (xy -3.58416 11.085543)
-      (xy -3.576412 11.116051)
-      (xy -3.523879 11.241453)
-      (xy -3.449308 11.350442)
-      (xy -3.35622 11.441054)
-      (xy -3.248134 11.511322)
-      (xy -3.128574 11.559284)
-      (xy -3.001059 11.582974)
-      (xy -2.86911 11.580428)
-      (xy -2.77683 11.562212)
-      (xy -2.65132 11.513233)
-      (xy -2.540483 11.440904)
-      (xy -2.447029 11.348756)
-      (xy -2.373665 11.240319)
-      (xy -2.323101 11.119122)
-      (xy -2.298044 10.988697)
-      (xy -2.295769 10.935209)
-      (xy -2.295906 10.933841)
-      (xy -2.421585 10.933841)
-      (xy -2.42279 11.005909)
-      (xy -2.427474 11.057925)
-      (xy -2.437245 11.09938)
-      (xy -2.453708 11.139767)
-      (xy -2.457905 11.148468)
-      (xy -2.524387 11.253598)
-      (xy -2.609235 11.339818)
-      (xy -2.708307 11.405212)
-      (xy -2.817456 11.447862)
-      (xy -2.93254 11.465853)
-      (xy -3.049413 11.457268)
-      (xy -3.099 11.444984)
-      (xy -3.177121 11.412241)
-      (xy -3.257596 11.363531)
-      (xy -3.32885 11.306608)
-      (xy -3.368042 11.264769)
-      (xy -3.427535 11.167943)
-      (xy -3.466754 11.058004)
-      (xy -3.48404 10.942936)
-      (xy -3.477736 10.830726)
-      (xy -3.467498 10.785823)
-      (xy -3.433516 10.704797)
-      (xy -3.380333 10.621173)
-      (xy -3.315347 10.545356)
-      (xy -3.265292 10.50136)
-      (xy -3.165823 10.440509)
-      (xy -3.06071 10.405936)
-      (xy -2.94276 10.395314)
-      (xy -2.937707 10.395354)
-      (xy -2.822325 10.410913)
-      (xy -2.712233 10.452778)
-      (xy -2.612442 10.517653)
-      (xy -2.527963 10.602239)
-      (xy -2.463806 10.703242)
-      (xy -2.461109 10.708905)
-      (xy -2.441641 10.754603)
-      (xy -2.429759 10.796652)
-      (xy -2.423692 10.845131)
-      (xy -2.421669 10.910118)
-      (xy -2.421585 10.933841)
-      (xy -2.295906 10.933841)
-      (xy -2.309482 10.797845)
-      (xy -2.348858 10.670912)
-      (xy -2.41125 10.557081)
-      (xy -2.494014 10.459025)
-      (xy -2.594503 10.379415)
-      (xy -2.710072 10.320924)
-      (xy -2.838077 10.286224)
-      (xy -2.947051 10.277389)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 544b1a13-1dc9-4c3b-ab3a-06afb75cc6d1))
-  (fp_poly
-    (pts
-      (xy 5.543129 -0.372479)
-      (xy 5.484876 -0.368512)
-      (xy 5.447474 -0.361885)
-      (xy 5.422169 -0.349662)
-      (xy 5.40021 -0.328908)
-      (xy 5.394815 -0.32274)
-      (xy 5.36747 -0.273088)
-      (xy 5.355121 -0.212081)
-      (xy 5.358104 -0.150484)
-      (xy 5.376755 -0.099062)
-      (xy 5.387403 -0.085078)
-      (xy 5.418011 -0.052497)
-      (xy 5.380002 -0.014488)
-      (xy 5.354213 0.020572)
-      (xy 5.34212 0.05527)
-      (xy 5.341993 0.058239)
-      (xy 5.334824 0.093228)
-      (xy 5.324231 0.110718)
-      (xy 5.31409 0.13086)
-      (xy 5.324231 0.146242)
-      (xy 5.337712 0.173722)
-      (xy 5.341993 0.203916)
-      (xy 5.354747 0.24362)
-      (xy 5.387187 0.283813)
-      (xy 5.430575 0.316698)
-      (xy 5.476178 0.33448)
-      (xy 5.489653 0.335706)
-      (xy 5.523644 0.340322)
-      (xy 5.541818 0.350508)
-      (xy 5.561256 0.36003)
-      (xy 5.597971 0.36507)
-      (xy 5.608426 0.36531)
-      (xy 5.647546 0.361819)
-      (xy 5.672461 0.353163)
-      (xy 5.675035 0.350508)
-      (xy 5.694578 0.340727)
-      (xy 5.730961 0.335662)
-      (xy 5.738816 0.33548)
-      (xy 5.790627 0.331567)
-      (xy 5.818006 0.316943)
-      (xy 5.825599 0.286465)
-      (xy 5.820182 0.245351)
-      (xy 5.804956 0.201779)
-      (xy 5.782923 0.175891)
-      (xy 5.759226 0.171573)
-      (xy 5.742356 0.186535)
-      (xy 5.721118 0.197454)
-      (xy 5.680669 0.203373)
-      (xy 5.630957 0.204406)
-      (xy 5.581931 0.200669)
-      (xy 5.543537 0.192274)
-      (xy 5.5287 0.184085)
-      (xy 5.508965 0.152741)
-      (xy 5.501216 0.116655)
-      (xy 5.505598 0.085709)
-      (xy 5.522256 0.069785)
-      (xy 5.527016 0.069273)
-      (xy 5.546714 0.06128)
-      (xy 5.549219 0.054471)
-      (xy 5.562602 0.046365)
-      (xy 5.597125 0.040988)
-      (xy 5.630629 0.039669)
-      (xy 5.712039 0.039669)
-      (xy 5.712039 -0.106872)
-      (xy 5.626929 -0.111312)
-      (xy 5.541818 -0.115751)
-      (xy 5.541818 -0.234166)
-      (xy 5.619528 -0.23864)
-      (xy 5.66736 -0.23864)
-      (xy 5.693719 -0.232587)
-      (xy 5.697238 -0.227538)
-      (xy 5.706539 -0.211432)
-      (xy 5.728746 -0.212638)
-      (xy 5.755313 -0.228065)
-      (xy 5.777692 -0.254625)
-      (xy 5.77903 -0.257108)
-      (xy 5.794628 -0.301045)
-      (xy 5.789017 -0.334018)
-      (xy 5.760651 -0.356784)
-      (xy 5.707982 -0.3701)
-      (xy 5.629462 -0.374723)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5d14ded3-ebed-4c5e-a06f-05c53bcb9d07))
-  (fp_poly
-    (pts
-      (xy -6.819732 0.960482)
-      (xy -6.857384 0.971742)
-      (xy -6.884347 0.990867)
-      (xy -6.934615 1.049794)
-      (xy -6.957192 1.109797)
-      (xy -6.958357 1.126532)
-      (xy -6.963785 1.157952)
-      (xy -6.973159 1.172012)
-      (xy -6.98262 1.191419)
-      (xy -6.98769 1.228232)
-      (xy -6.987961 1.239494)
-      (xy -6.984632 1.276245)
-      (xy -6.97633 1.29647)
-      (xy -6.973159 1.297827)
-      (xy -6.963776 1.310933)
-      (xy -6.958669 1.343561)
-      (xy -6.958357 1.355293)
-      (xy -6.954343 1.39384)
-      (xy -6.938648 1.426933)
-      (xy -6.905793 1.465218)
-      (xy -6.897408 1.473708)
-      (xy -6.85927 1.509056)
-      (xy -6.828308 1.527313)
-      (xy -6.792544 1.533961)
-      (xy -6.764191 1.534657)
-      (xy -6.722548 1.531934)
-      (xy -6.69643 1.524988)
-      (xy -6.691923 1.519855)
-      (xy -6.679538 1.507791)
-      (xy -6.662602 1.505054)
-      (xy -6.635039 1.491794)
-      (xy -6.623992 1.468049)
-      (xy -6.612564 1.44034)
-      (xy -6.601507 1.431044)
-      (xy -6.592168 1.418195)
-      (xy -6.58831 1.387512)
-      (xy -6.583747 1.353329)
-      (xy -6.573508 1.334832)
-      (xy -6.565837 1.316323)
-      (xy -6.560488 1.277109)
-      (xy -6.559281 1.246021)
-      (xy -6.707129 1.246021)
-      (xy -6.708659 1.320994)
-      (xy -6.714178 1.370973)
-      (xy -6.725082 1.400452)
-      (xy -6.742766 1.413926)
-      (xy -6.759976 1.416242)
-      (xy -6.79065 1.406171)
-      (xy -6.80426 1.379238)
-      (xy -6.815688 1.351528)
-      (xy -6.826745 1.342233)
-      (xy -6.834039 1.329048)
-      (xy -6.838324 1.295635)
-      (xy -6.839673 1.251211)
-      (xy -6.83816 1.20499)
-      (xy -6.833859 1.166189)
-      (xy -6.826844 1.144023)
-      (xy -6.82514 1.142408)
-      (xy -6.812705 1.12153)
-      (xy -6.810338 1.10453)
-      (xy -6.80259 1.083062)
-      (xy -6.774708 1.075925)
-      (xy -6.767659 1.075799)
-      (xy -6.741313 1.079542)
-      (xy -6.723778 1.093938)
-      (xy -6.713362 1.12374)
-      (xy -6.708377 1.173703)
-      (xy -6.707129 1.246021)
-      (xy -6.559281 1.246021)
-      (xy -6.558706 1.231219)
-      (xy -6.560864 1.180929)
-      (xy -6.56649 1.143311)
-      (xy -6.573508 1.127606)
-      (xy -6.585313 1.107033)
-      (xy -6.58831 1.085137)
-      (xy -6.598287 1.054303)
-      (xy -6.623287 1.017036)
-      (xy -6.634472 1.0046)
-      (xy -6.665188 0.976822)
-      (xy -6.694909 0.962706)
-      (xy -6.73586 0.957797)
-      (xy -6.763988 0.957403)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 69a30b9a-0f8f-4859-b507-ce0ee5676104))
-  (fp_poly
-    (pts
-      (xy -1.628663 10.743531)
-      (xy -1.653075 10.750915)
-      (xy -1.659289 10.76362)
-      (xy -1.666276 10.783332)
-      (xy -1.672199 10.785823)
-      (xy -1.682324 10.798906)
-      (xy -1.692076 10.831645)
-      (xy -1.69468 10.845677)
-      (xy -1.704445 10.891711)
-      (xy -1.716376 10.929199)
-      (xy -1.718775 10.934488)
-      (xy -1.738226 10.973217)
-      (xy -1.7481 10.992848)
-      (xy -1.760325 11.027417)
-      (xy -1.762902 11.04574)
-      (xy -1.771417 11.063675)
-      (xy -1.79035 11.063521)
-      (xy -1.809785 11.048707)
-      (xy -1.819439 11.026202)
-      (xy -1.828021 11.000254)
-      (xy -1.837034 10.993049)
-      (xy -1.846668 10.979875)
-      (xy -1.856274 10.946527)
-      (xy -1.859888 10.92644)
-      (xy -1.868429 10.88679)
-      (xy -1.878575 10.862945)
-      (xy -1.882998 10.859832)
-      (xy -1.893425 10.847263)
-      (xy -1.89659 10.826528)
-      (xy -1.908209 10.77903)
-      (xy -1.941868 10.750836)
-      (xy -1.998201 10.741418)
-      (xy -1.998964 10.741417)
-      (xy -2.061542 10.741417)
-      (xy -2.051093 10.804325)
-      (xy -2.041915 10.843976)
-      (xy -2.031282 10.8688)
-      (xy -2.027589 10.872167)
-      (xy -2.016578 10.8891)
-      (xy -2.014534 10.904598)
-      (xy -2.007446 10.932418)
-      (xy -1.999732 10.941242)
-      (xy -1.986679 10.962394)
-      (xy -1.984839 10.97542)
-      (xy -1.978152 11.005936)
-      (xy -1.962636 11.042847)
-      (xy -1.946978 11.079352)
-      (xy -1.940525 11.10717)
-      (xy -1.932392 11.133863)
-      (xy -1.912742 11.168104)
-      (xy -1.911905 11.169289)
-      (xy -1.888039 11.210866)
-      (xy -1.873296 11.249284)
-      (xy -1.864154 11.273717)
-      (xy -1.846909 11.28528)
-      (xy -1.812447 11.288517)
-      (xy -1.794602 11.288523)
-      (xy -1.745837 11.283553)
-      (xy -1.712484 11.271306)
-      (xy -1.707395 11.266945)
-      (xy -1.691461 11.238982)
-      (xy -1.688893 11.225932)
-      (xy -1.680507 11.19909)
-      (xy -1.667161 11.177201)
-      (xy -1.649427 11.14031)
-      (xy -1.644958 11.115164)
-      (xy -1.639009 11.089158)
-      (xy -1.629685 11.08186)
-      (xy -1.616789 11.069774)
-      (xy -1.614884 11.058194)
-      (xy -1.608469 11.028042)
-      (xy -1.591709 10.981557)
-      (xy -1.568335 10.928451)
-      (xy -1.554432 10.900738)
-      (xy -1.542746 10.867503)
-      (xy -1.540874 10.852632)
-      (xy -1.53383 10.832793)
-      (xy -1.527752 10.830228)
-      (xy -1.516654 10.817372)
-      (xy -1.508198 10.786395)
-      (xy -1.508113 10.785823)
-      (xy -1.501596 10.741417)
-      (xy -1.580443 10.741417)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ac1e9013-91ba-4d04-8d11-834f881bb8e8))
-  (fp_poly
-    (pts
-      (xy -0.987096 2.69296)
-      (xy -1.062897 2.699716)
-      (xy -1.112323 2.710592)
-      (xy -1.138573 2.728355)
-      (xy -1.144845 2.755772)
-      (xy -1.134337 2.79561)
-      (xy -1.126897 2.81391)
-      (xy -1.102499 2.861406)
-      (xy -1.081716 2.880519)
-      (xy -1.063474 2.872096)
-      (xy -1.059814 2.866825)
-      (xy -1.039359 2.855262)
-      (xy -1.015408 2.852023)
-      (xy -0.984413 2.846436)
-      (xy -0.971002 2.837221)
-      (xy -0.950993 2.826557)
-      (xy -0.918322 2.822419)
-      (xy -0.887523 2.826786)
-      (xy -0.87479 2.837221)
-      (xy -0.862889 2.850552)
-      (xy -0.853787 2.852023)
-      (xy -0.827189 2.859016)
-      (xy -0.791045 2.875999)
-      (xy -0.788372 2.877512)
-      (xy -0.758156 2.901665)
-      (xy -0.739229 2.936333)
-      (xy -0.729473 2.987791)
-      (xy -0.726772 3.060136)
-      (xy -0.734533 3.144746)
-      (xy -0.758893 3.205669)
-      (xy -0.801464 3.244751)
-      (xy -0.863859 3.263835)
-      (xy -0.907185 3.266475)
-      (xy -0.993205 3.266475)
-      (xy -0.993205 3.029646)
-      (xy -1.156026 3.029646)
-      (xy -1.156026 3.205684)
-      (xy -1.155582 3.284492)
-      (xy -1.152791 3.338416)
-      (xy -1.145462 3.372177)
-      (xy -1.131406 3.390494)
-      (xy -1.108432 3.398088)
-      (xy -1.074349 3.399679)
-      (xy -1.066004 3.399692)
-      (xy -1.035353 3.40409)
-      (xy -1.022809 3.414494)
-      (xy -1.009493 3.421615)
-      (xy -0.975316 3.426426)
-      (xy -0.92894 3.428854)
-      (xy -0.879021 3.428827)
-      (xy -0.83422 3.426272)
-      (xy -0.803196 3.421116)
-      (xy -0.794562 3.416406)
-      (xy -0.775738 3.404794)
-      (xy -0.741163 3.394436)
-      (xy -0.739512 3.394099)
-      (xy -0.705829 3.379016)
-      (xy -0.665343 3.349634)
-      (xy -0.625667 3.313108)
-      (xy -0.594415 3.276591)
-      (xy -0.579202 3.24724)
-      (xy -0.578753 3.243043)
-      (xy -0.567007 3.221765)
-      (xy -0.560814 3.218557)
-      (xy -0.551873 3.20403)
-      (xy -0.546268 3.166004)
-      (xy -0.543748 3.102119)
-      (xy -0.54358 3.056494)
-      (xy -0.544523 2.985003)
-      (xy -0.547329 2.93656)
-      (xy -0.553125 2.904617)
-      (xy -0.563036 2.882627)
-      (xy -0.576321 2.866025)
-      (xy -0.598915 2.836244)
-      (xy -0.608357 2.812805)
-      (xy -0.608357 2.812748)
-      (xy -0.620081 2.791952)
-      (xy -0.640729 2.776533)
-      (xy -0.677883 2.752113)
-      (xy -0.702102 2.732188)
-      (xy -0.748326 2.707355)
-      (xy -0.821979 2.693365)
-      (xy -0.922935 2.690234)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b1df1db6-c8a4-40b7-ab49-82943d193676))
-  (fp_poly
-    (pts
-      (xy -5.558191 -5.456803)
-      (xy -5.630766 -5.454056)
-      (xy -5.682295 -5.448771)
-      (xy -5.709167 -5.441384)
-      (xy -5.712107 -5.438301)
-      (xy -5.729492 -5.423602)
-      (xy -5.738436 -5.422219)
-      (xy -5.754444 -5.417777)
-      (xy -5.75769 -5.400871)
-      (xy -5.748003 -5.366132)
-      (xy -5.735596 -5.333708)
-      (xy -5.71523 -5.293616)
-      (xy -5.692837 -5.276332)
-      (xy -5.677262 -5.274201)
-      (xy -5.646559 -5.279902)
-      (xy -5.63359 -5.289002)
-      (xy -5.614901 -5.297031)
-      (xy -5.5761 -5.302407)
-      (xy -5.53917 -5.303804)
-      (xy -5.485639 -5.301448)
-      (xy -5.449134 -5.291756)
-      (xy -5.417272 -5.270798)
-      (xy -5.406827 -5.261779)
-      (xy -5.377618 -5.231969)
-      (xy -5.36112 -5.207892)
-      (xy -5.359755 -5.202571)
-      (xy -5.349802 -5.186342)
-      (xy -5.344954 -5.185389)
-      (xy -5.337219 -5.171795)
-      (xy -5.331923 -5.135784)
-      (xy -5.330152 -5.089177)
-      (xy -5.332243 -5.038901)
-      (xy -5.337783 -5.004479)
-      (xy -5.344954 -4.992965)
-      (xy -5.358085 -4.980976)
-      (xy -5.359755 -4.970762)
-      (xy -5.371317 -4.941414)
-      (xy -5.398372 -4.911231)
-      (xy -5.429476 -4.891657)
-      (xy -5.441166 -4.889352)
-      (xy -5.460864 -4.881359)
-      (xy -5.463368 -4.87455)
-      (xy -5.476598 -4.865723)
-      (xy -5.510071 -4.860428)
-      (xy -5.529977 -4.859748)
-      (xy -5.596585 -4.859748)
-      (xy -5.596585 -5.11138)
-      (xy -5.759406 -5.11138)
-      (xy -5.759406 -4.745034)
-      (xy -5.71315 -4.735783)
-      (xy -5.672485 -4.731003)
-      (xy -5.614294 -4.728294)
-      (xy -5.54648 -4.727537)
-      (xy -5.476943 -4.728613)
-      (xy -5.413583 -4.731404)
-      (xy -5.364301 -4.735793)
-      (xy -5.337553 -4.741406)
-      (xy -5.277764 -4.780463)
-      (xy -5.225493 -4.837705)
-      (xy -5.186911 -4.904229)
-      (xy -5.168186 -4.971136)
-      (xy -5.167331 -4.986965)
-      (xy -5.163232 -5.023024)
-      (xy -5.15329 -5.044237)
-      (xy -5.152529 -5.044772)
-      (xy -5.141865 -5.064781)
-      (xy -5.137727 -5.097452)
-      (xy -5.142094 -5.128251)
-      (xy -5.152529 -5.140984)
-      (xy -5.162313 -5.153996)
-      (xy -5.167203 -5.185991)
-      (xy -5.167331 -5.19279)
-      (xy -5.171049 -5.227033)
-      (xy -5.18019 -5.244149)
-      (xy -5.182133 -5.244597)
-      (xy -5.19441 -5.256911)
-      (xy -5.196935 -5.272388)
-      (xy -5.207685 -5.305092)
-      (xy -5.219138 -5.318606)
-      (xy -5.237863 -5.342164)
-      (xy -5.24134 -5.354298)
-      (xy -5.25352 -5.369561)
-      (xy -5.285304 -5.392352)
-      (xy -5.325489 -5.415393)
-      (xy -5.366663 -5.435655)
-      (xy -5.401751 -5.448328)
-      (xy -5.439723 -5.455007)
-      (xy -5.489549 -5.457289)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f7ebaef7-8e7f-4928-9d91-f9c08e3b8787))
-  (fp_poly
-    (pts
-      (xy 5.854375 6.022406)
-      (xy 5.821105 6.032713)
-      (xy 5.798886 6.051491)
-      (xy 5.778468 6.081569)
-      (xy 5.771247 6.103297)
-      (xy 5.762475 6.121496)
-      (xy 5.756445 6.123235)
-      (xy 5.7443 6.135594)
-      (xy 5.741643 6.151966)
-      (xy 5.734846 6.180301)
-      (xy 5.726841 6.189844)
-      (xy 5.718883 6.208878)
-      (xy 5.714049 6.247995)
-      (xy 5.712389 6.297833)
-      (xy 5.713956 6.349031)
-      (xy 5.718802 6.392226)
-      (xy 5.725597 6.415773)
-      (xy 5.740314 6.446048)
-      (xy 5.759218 6.487739)
-      (xy 5.762837 6.496016)
-      (xy 5.795245 6.544567)
-      (xy 5.832964 6.573726)
-      (xy 5.86925 6.586131)
-      (xy 5.913946 6.594004)
-      (xy 5.957993 6.596824)
-      (xy 5.99233 6.594066)
-      (xy 6.007899 6.58521)
-      (xy 6.008077 6.58382)
-      (xy 6.02043 6.570123)
-      (xy 6.038779 6.562715)
-      (xy 6.067415 6.542933)
-      (xy 6.07751 6.523984)
-      (xy 6.089198 6.499409)
-      (xy 6.098614 6.493282)
-      (xy 6.107258 6.480265)
-      (xy 6.111577 6.448258)
-      (xy 6.11169 6.441475)
-      (xy 6.115408 6.407233)
-      (xy 6.124549 6.390116)
-      (xy 6.126492 6.389669)
-      (xy 6.134635 6.376294)
-      (xy 6.140012 6.341824)
-      (xy 6.141294 6.309132)
-      (xy 6.140373 6.292178)
-      (xy 5.993946 6.292178)
-      (xy 5.991027 6.344348)
-      (xy 5.984573 6.39324)
-      (xy 5.974887 6.430727)
-      (xy 5.96937 6.441996)
-      (xy 5.944199 6.467183)
-      (xy 5.916569 6.477839)
-      (xy 5.895577 6.472334)
-      (xy 5.889662 6.456277)
-      (xy 5.881669 6.436579)
-      (xy 5.87486 6.434075)
-      (xy 5.86753 6.420226)
-      (xy 5.862379 6.382416)
-      (xy 5.860107 6.326253)
-      (xy 5.860058 6.31566)
-      (xy 5.861789 6.257018)
-      (xy 5.866515 6.215809)
-      (xy 5.873536 6.197639)
-      (xy 5.87486 6.197245)
-      (xy 5.886886 6.184847)
-      (xy 5.889662 6.167641)
-      (xy 5.898335 6.144427)
-      (xy 5.926666 6.138037)
-      (xy 5.955684 6.144975)
-      (xy 5.963671 6.167641)
-      (xy 5.96987 6.191693)
-      (xy 5.978473 6.197245)
-      (xy 5.987971 6.210501)
-      (xy 5.993028 6.244854)
-      (xy 5.993946 6.292178)
-      (xy 6.140373 6.292178)
-      (xy 6.138775 6.262776)
-      (xy 6.1323 6.229535)
-      (xy 6.126492 6.219447)
-      (xy 6.115827 6.199438)
-      (xy 6.11169 6.166767)
-      (xy 6.107794 6.135962)
-      (xy 6.098493 6.123235)
-      (xy 6.08502 6.110798)
-      (xy 6.07671 6.089931)
-      (xy 6.052757 6.054506)
-      (xy 6.003606 6.030942)
-      (xy 5.931584 6.020201)
-      (xy 5.906949 6.019622)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 1c61b283-26a9-46c1-8a00-f29e6facd995))
-  (fp_poly
-    (pts
-      (xy -5.588567 -2.927415)
-      (xy -5.638935 -2.923138)
-      (xy -5.672444 -2.915852)
-      (xy -5.681945 -2.908857)
-      (xy -5.699728 -2.894018)
-      (xy -5.716234 -2.8911)
-      (xy -5.734749 -2.890433)
-      (xy -5.742089 -2.884094)
-      (xy -5.738196 -2.865577)
-      (xy -5.723012 -2.828375)
-      (xy -5.715526 -2.810917)
-      (xy -5.691014 -2.764875)
-      (xy -5.667025 -2.7447)
-      (xy -5.657192 -2.743082)
-      (xy -5.628638 -2.749762)
-      (xy -5.618788 -2.757884)
-      (xy -5.600926 -2.765681)
-      (xy -5.565128 -2.770547)
-      (xy -5.520955 -2.7724)
-      (xy -5.477968 -2.771156)
-      (xy -5.445729 -2.766733)
-      (xy -5.433765 -2.759488)
-      (xy -5.42122 -2.746458)
-      (xy -5.39676 -2.737003)
-      (xy -5.36648 -2.719224)
-      (xy -5.359755 -2.699628)
-      (xy -5.352538 -2.673694)
-      (xy -5.34391 -2.666257)
-      (xy -5.335845 -2.649848)
-      (xy -5.330727 -2.61298)
-      (xy -5.328543 -2.564651)
-      (xy -5.329279 -2.513856)
-      (xy -5.332921 -2.469594)
-      (xy -5.339457 -2.440859)
-      (xy -5.344259 -2.434941)
-      (xy -5.358867 -2.417754)
-      (xy -5.359755 -2.411307)
-      (xy -5.371537 -2.39152)
-      (xy -5.39676 -2.373035)
-      (xy -5.423636 -2.354784)
-      (xy -5.433765 -2.34093)
-      (xy -5.446999 -2.333593)
-      (xy -5.480482 -2.329193)
-      (xy -5.500373 -2.328629)
-      (xy -5.566982 -2.328629)
-      (xy -5.566982 -2.580261)
-      (xy -5.759406 -2.580261)
-      (xy -5.759406 -2.213915)
-      (xy -5.71315 -2.204664)
-      (xy -5.678473 -2.200729)
-      (xy -5.623262 -2.197746)
-      (xy -5.55658 -2.19612)
-      (xy -5.517025 -2.195953)
-      (xy -5.438358 -2.197689)
-      (xy -5.381075 -2.202995)
-      (xy -5.337055 -2.213018)
-      (xy -5.304248 -2.225987)
-      (xy -5.267094 -2.246051)
-      (xy -5.244511 -2.263347)
-      (xy -5.24134 -2.26909)
-      (xy -5.232104 -2.288026)
-      (xy -5.209374 -2.317064)
-      (xy -5.204336 -2.322627)
-      (xy -5.177072 -2.364786)
-      (xy -5.167331 -2.4048)
-      (xy -5.162842 -2.435032)
-      (xy -5.152529 -2.447044)
-      (xy -5.145055 -2.46081)
-      (xy -5.139851 -2.498031)
-      (xy -5.137738 -2.552597)
-      (xy -5.137727 -2.557185)
-      (xy -5.139586 -2.611602)
-      (xy -5.144493 -2.653738)
-      (xy -5.151444 -2.675507)
-      (xy -5.152529 -2.676473)
-      (xy -5.164964 -2.697351)
-      (xy -5.167331 -2.714352)
-      (xy -5.173015 -2.737936)
-      (xy -5.180528 -2.743082)
-      (xy -5.1935 -2.755641)
-      (xy -5.203172 -2.78072)
-      (xy -5.219173 -2.812792)
-      (xy -5.237426 -2.827878)
-      (xy -5.281177 -2.853783)
-      (xy -5.337852 -2.902099)
-      (xy -5.341849 -2.905902)
-      (xy -5.365936 -2.915711)
-      (xy -5.410023 -2.92283)
-      (xy -5.466739 -2.927197)
-      (xy -5.52871 -2.928746)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c609b32d-d191-4d04-ae2f-0cca69908168))
-  (fp_poly
-    (pts
-      (xy 5.48236 7.222158)
-      (xy 5.439614 7.228874)
-      (xy 5.413994 7.237498)
-      (xy 5.355424 7.27192)
-      (xy 5.322367 7.298457)
-      (xy 5.312389 7.318346)
-      (xy 5.303099 7.33564)
-      (xy 5.297587 7.336988)
-      (xy 5.287115 7.34983)
-      (xy 5.282785 7.38052)
-      (xy 5.278223 7.414704)
-      (xy 5.267984 7.4332)
-      (xy 5.261525 7.451129)
-      (xy 5.256503 7.491687)
-      (xy 5.253612 7.547907)
-      (xy 5.253182 7.581642)
-      (xy 5.254551 7.654724)
-      (xy 5.259489 7.706364)
-      (xy 5.26924 7.744631)
-      (xy 5.282785 7.773643)
-      (xy 5.301533 7.810288)
-      (xy 5.311755 7.836621)
-      (xy 5.312389 7.840702)
-      (xy 5.32386 7.863257)
-      (xy 5.352897 7.892696)
-      (xy 5.391442 7.921083)
-      (xy 5.398103 7.925084)
-      (xy 5.444036 7.941613)
-      (xy 5.504759 7.950789)
-      (xy 5.565981 7.950783)
-      (xy 5.582523 7.948681)
-      (xy 5.612054 7.939428)
-      (xy 5.623228 7.92808)
-      (xy 5.635302 7.915975)
-      (xy 5.646488 7.914261)
-      (xy 5.681928 7.900463)
-      (xy 5.709769 7.862953)
-      (xy 5.718418 7.839561)
-      (xy 5.741554 7.773366)
-      (xy 5.772577 7.704316)
-      (xy 5.772974 7.703535)
-      (xy 5.780251 7.674885)
-      (xy 5.784475 7.629654)
-      (xy 5.785711 7.57687)
-      (xy 5.785349 7.565848)
-      (xy 5.601736 7.565848)
-      (xy 5.601519 7.634714)
-      (xy 5.597391 7.697163)
-      (xy 5.589355 7.745281)
-      (xy 5.578823 7.76975)
-      (xy 5.541661 7.791806)
-      (xy 5.497846 7.791133)
-      (xy 5.463051 7.771)
-      (xy 5.451976 7.754856)
-      (xy 5.444652 7.729128)
-      (xy 5.440388 7.688334)
-      (xy 5.438493 7.626991)
-      (xy 5.438205 7.573818)
-      (xy 5.438936 7.49627)
-      (xy 5.441589 7.442817)
-      (xy 5.446856 7.407975)
-      (xy 5.455427 7.386262)
-      (xy 5.463051 7.376636)
-      (xy 5.502635 7.352851)
-      (xy 5.541152 7.357155)
-      (xy 5.572885 7.388399)
-      (xy 5.57891 7.399896)
-      (xy 5.590434 7.440525)
-      (xy 5.598042 7.49848)
-      (xy 5.601736 7.565848)
-      (xy 5.785349 7.565848)
-      (xy 5.784024 7.525565)
-      (xy 5.779478 7.484769)
-      (xy 5.772138 7.463511)
-      (xy 5.771247 7.462804)
-      (xy 5.760583 7.442794)
-      (xy 5.756445 7.410124)
-      (xy 5.752078 7.379325)
-      (xy 5.741643 7.366592)
-      (xy 5.729256 7.354316)
-      (xy 5.726841 7.339568)
-      (xy 5.716021 7.310637)
-      (xy 5.690358 7.278708)
-      (xy 5.660046 7.254607)
-      (xy 5.640777 7.248177)
-      (xy 5.624275 7.238399)
-      (xy 5.623228 7.233375)
-      (xy 5.610045 7.224513)
-      (xy 5.576334 7.219805)
-      (xy 5.530853 7.219077)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp acdd851c-3665-414c-9f35-05f10e11aa9d))
-  (fp_poly
-    (pts
-      (xy -5.556729 -8.00944)
-      (xy -5.584498 -8.001631)
-      (xy -5.589184 -7.997744)
-      (xy -5.608592 -7.988282)
-      (xy -5.645405 -7.983212)
-      (xy -5.656666 -7.982942)
-      (xy -5.693418 -7.979613)
-      (xy -5.713643 -7.971311)
-      (xy -5.715 -7.96814)
-      (xy -5.726989 -7.955008)
-      (xy -5.737203 -7.953338)
-      (xy -5.754736 -7.94793)
-      (xy -5.757441 -7.928392)
-      (xy -5.745379 -7.88975)
-      (xy -5.738229 -7.872101)
-      (xy -5.717052 -7.821418)
-      (xy -5.593911 -7.829688)
-      (xy -5.50539 -7.831552)
-      (xy -5.440793 -7.823939)
-      (xy -5.40163 -7.807191)
-      (xy -5.389359 -7.783483)
-      (xy -5.38148 -7.763551)
-      (xy -5.374557 -7.760914)
-      (xy -5.361425 -7.748925)
-      (xy -5.359755 -7.738711)
-      (xy -5.351763 -7.719013)
-      (xy -5.344954 -7.716508)
-      (xy -5.337219 -7.702914)
-      (xy -5.331923 -7.666903)
-      (xy -5.330152 -7.620296)
-      (xy -5.331902 -7.571299)
-      (xy -5.33648 -7.536646)
-      (xy -5.342623 -7.524084)
-      (xy -5.356888 -7.512273)
-      (xy -5.377027 -7.482866)
-      (xy -5.382993 -7.472277)
-      (xy -5.407572 -7.438233)
-      (xy -5.432569 -7.421099)
-      (xy -5.437131 -7.420471)
-      (xy -5.459292 -7.413569)
-      (xy -5.463368 -7.405669)
-      (xy -5.476598 -7.396842)
-      (xy -5.510071 -7.391546)
-      (xy -5.529977 -7.390867)
-      (xy -5.596585 -7.390867)
-      (xy -5.596585 -7.657301)
-      (xy -5.759406 -7.657301)
-      (xy -5.75929 -7.475978)
-      (xy -5.759175 -7.294655)
-      (xy -5.719335 -7.276153)
-      (xy -5.688169 -7.268131)
-      (xy -5.638927 -7.262343)
-      (xy -5.579139 -7.258872)
-      (xy -5.516334 -7.257799)
-      (xy -5.458042 -7.259208)
-      (xy -5.41179 -7.263181)
-      (xy -5.385109 -7.269801)
-      (xy -5.381958 -7.272452)
-      (xy -5.361317 -7.284473)
-      (xy -5.34038 -7.287491)
-      (xy -5.302911 -7.299784)
-      (xy -5.259978 -7.331553)
-      (xy -5.219428 -7.375827)
-      (xy -5.192219 -7.419045)
-      (xy -5.175585 -7.468539)
-      (xy -5.167483 -7.523704)
-      (xy -5.167331 -7.530799)
-      (xy -5.163682 -7.573256)
-      (xy -5.154591 -7.603565)
-      (xy -5.15124 -7.608264)
-      (xy -5.143153 -7.626131)
-      (xy -5.15124 -7.634301)
-      (xy -5.161603 -7.654295)
-      (xy -5.167076 -7.691357)
-      (xy -5.167331 -7.701706)
-      (xy -5.170822 -7.740826)
-      (xy -5.179478 -7.765741)
-      (xy -5.182133 -7.768315)
-      (xy -5.195373 -7.789493)
-      (xy -5.197369 -7.802493)
-      (xy -5.209652 -7.834869)
-      (xy -5.240738 -7.874846)
-      (xy -5.283353 -7.916008)
-      (xy -5.330226 -7.951937)
-      (xy -5.374085 -7.976217)
-      (xy -5.401872 -7.982942)
-      (xy -5.430795 -7.989433)
-      (xy -5.441166 -7.997744)
-      (xy -5.460364 -8.006789)
-      (xy -5.497818 -8.012024)
-      (xy -5.515175 -8.012546)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0d5a352e-f7d8-40f5-bf13-391c6c92a108))
-  (fp_poly
-    (pts
-      (xy -5.552656 -0.399724)
-      (xy -5.578284 -0.390344)
-      (xy -5.608123 -0.380023)
-      (xy -5.653432 -0.370361)
-      (xy -5.674295 -0.367234)
-      (xy -5.715239 -0.359394)
-      (xy -5.740585 -0.34961)
-      (xy -5.744604 -0.344572)
-      (xy -5.73968 -0.324908)
-      (xy -5.727675 -0.289168)
-      (xy -5.71274 -0.248668)
-      (xy -5.699026 -0.214722)
-      (xy -5.691313 -0.199317)
-      (xy -5.676901 -0.201735)
-      (xy -5.646602 -0.214423)
-      (xy -5.639639 -0.217819)
-      (xy -5.604653 -0.229412)
-      (xy -5.558586 -0.237375)
-      (xy -5.510033 -0.241268)
-      (xy -5.467588 -0.240651)
-      (xy -5.439846 -0.235083)
-      (xy -5.433765 -0.228369)
-      (xy -5.42122 -0.215339)
-      (xy -5.39676 -0.205884)
-      (xy -5.366175 -0.187702)
-      (xy -5.359755 -0.167275)
-      (xy -5.353503 -0.143376)
-      (xy -5.344954 -0.137953)
-      (xy -5.337623 -0.124104)
-      (xy -5.332472 -0.086295)
-      (xy -5.330201 -0.030132)
-      (xy -5.330152 -0.019539)
-      (xy -5.331883 0.039103)
-      (xy -5.336609 0.080312)
-      (xy -5.343629 0.098482)
-      (xy -5.344954 0.098876)
-      (xy -5.358504 0.110672)
-      (xy -5.359755 0.118578)
-      (xy -5.371565 0.139296)
-      (xy -5.39676 0.158084)
-      (xy -5.423636 0.176335)
-      (xy -5.433765 0.190189)
-      (xy -5.446999 0.197526)
-      (xy -5.480482 0.201926)
-      (xy -5.500373 0.202489)
-      (xy -5.566982 0.202489)
-      (xy -5.566982 -0.049142)
-      (xy -5.759406 -0.049142)
-      (xy -5.759406 0.317204)
-      (xy -5.71315 0.326455)
-      (xy -5.661419 0.332986)
-      (xy -5.594871 0.336088)
-      (xy -5.521517 0.336017)
-      (xy -5.449367 0.333029)
-      (xy -5.386431 0.32738)
-      (xy -5.340719 0.319324)
-      (xy -5.326078 0.314097)
-      (xy -5.2885 0.290955)
-      (xy -5.262113 0.269782)
-      (xy -5.239651 0.251361)
-      (xy -5.229182 0.246801)
-      (xy -5.213536 0.234197)
-      (xy -5.194768 0.203556)
-      (xy -5.177952 0.165286)
-      (xy -5.16816 0.129798)
-      (xy -5.167331 0.11988)
-      (xy -5.16211 0.092642)
-      (xy -5.152529 0.084075)
-      (xy -5.144777 0.070493)
-      (xy -5.139476 0.034569)
-      (xy -5.137727 -0.011264)
-      (xy -5.139866 -0.061792)
-      (xy -5.145446 -0.099672)
-      (xy -5.152529 -0.115751)
-      (xy -5.163194 -0.135761)
-      (xy -5.167331 -0.168431)
-      (xy -5.171226 -0.199237)
-      (xy -5.180528 -0.211963)
-      (xy -5.1935 -0.224522)
-      (xy -5.203172 -0.249601)
-      (xy -5.219424 -0.281767)
-      (xy -5.238081 -0.29696)
-      (xy -5.268745 -0.314556)
-      (xy -5.29204 -0.333147)
-      (xy -5.326369 -0.353725)
-      (xy -5.370778 -0.367556)
-      (xy -5.37345 -0.368007)
-      (xy -5.416692 -0.377572)
-      (xy -5.450313 -0.389481)
-      (xy -5.452066 -0.390394)
-      (xy -5.499607 -0.403175)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5e882282-635a-4d69-95e2-d1f643cfb8f2))
-  (fp_poly
-    (pts
-      (xy 5.771247 -1.455319)
-      (xy 5.830454 -1.455319)
-      (xy 5.867533 -1.452264)
-      (xy 5.888154 -1.444632)
-      (xy 5.889662 -1.441547)
-      (xy 5.902242 -1.428972)
-      (xy 5.922815 -1.423045)
-      (xy 5.951012 -1.409155)
-      (xy 5.960905 -1.392412)
-      (xy 5.959445 -1.376904)
-      (xy 5.943069 -1.369099)
-      (xy 5.905309 -1.36659)
-      (xy 5.891331 -1.366508)
-      (xy 5.832351 -1.361073)
-      (xy 5.798921 -1.345121)
-      (xy 5.797734 -1.343792)
-      (xy 5.771442 -1.313219)
-      (xy 5.760146 -1.300443)
-      (xy 5.751047 -1.277546)
-      (xy 5.744901 -1.238324)
-      (xy 5.741949 -1.191871)
-      (xy 5.742431 -1.147283)
-      (xy 5.746588 -1.113654)
-      (xy 5.754661 -1.100079)
-      (xy 5.75484 -1.100075)
-      (xy 5.767871 -1.08753)
-      (xy 5.777325 -1.06307)
-      (xy 5.795508 -1.032485)
-      (xy 5.815935 -1.026065)
-      (xy 5.839834 -1.019813)
-      (xy 5.845256 -1.011263)
-      (xy 5.858639 -1.003157)
-      (xy 5.893163 -0.997781)
-      (xy 5.926666 -0.996462)
-      (xy 5.97125 -0.998895)
-      (xy 6.00082 -1.005172)
-      (xy 6.008077 -1.011263)
-      (xy 6.020066 -1.024395)
-      (xy 6.03028 -1.026065)
-      (xy 6.059286 -1.037467)
-      (xy 6.08941 -1.064124)
-      (xy 6.109203 -1.094708)
-      (xy 6.11169 -1.106602)
-      (xy 6.120711 -1.131803)
-      (xy 6.126492 -1.137079)
-      (xy 6.133907 -1.155461)
-      (xy 6.138323 -1.188295)
-      (xy 5.993043 -1.188295)
-      (xy 5.982443 -1.147949)
-      (xy 5.974773 -1.137018)
-      (xy 5.944574 -1.117872)
-      (xy 5.914216 -1.119855)
-      (xy 5.894695 -1.141949)
-      (xy 5.893951 -1.14448)
-      (xy 5.882235 -1.168476)
-      (xy 5.873134 -1.174084)
-      (xy 5.862471 -1.186484)
-      (xy 5.860058 -1.203406)
-      (xy 5.873318 -1.230968)
-      (xy 5.897063 -1.242015)
-      (xy 5.924773 -1.253487)
-      (xy 5.934067 -1.264625)
-      (xy 5.944352 -1.268277)
-      (xy 5.963671 -1.25946)
-      (xy 5.986379 -1.229956)
-      (xy 5.993043 -1.188295)
-      (xy 6.138323 -1.188295)
-      (xy 6.139218 -1.194952)
-      (xy 6.141293 -1.247074)
-      (xy 6.141294 -1.248093)
-      (xy 6.139289 -1.300368)
-      (xy 6.134027 -1.340166)
-      (xy 6.12664 -1.359011)
-      (xy 6.126492 -1.359107)
-      (xy 6.112939 -1.380495)
-      (xy 6.11169 -1.389979)
-      (xy 6.101695 -1.414892)
-      (xy 6.077065 -1.448581)
-      (xy 6.045828 -1.482225)
-      (xy 6.016015 -1.507006)
-      (xy 5.998297 -1.514527)
-      (xy 5.980177 -1.523342)
-      (xy 5.978473 -1.529329)
-      (xy 5.965806 -1.540456)
-      (xy 5.941468 -1.544131)
-      (xy 5.913651 -1.549197)
-      (xy 5.904464 -1.558932)
-      (xy 5.891234 -1.56776)
-      (xy 5.857761 -1.573055)
-      (xy 5.837855 -1.573734)
-      (xy 5.771247 -1.573734)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp aa514cd8-191a-4515-ae42-84e65eabf5d9))
-  (fp_poly
-    (pts
-      (xy -0.345924 9.690505)
-      (xy -0.703548 9.69057)
-      (xy -1.033695 9.690685)
-      (xy -1.337428 9.690858)
-      (xy -1.61581 9.691094)
-      (xy -1.869904 9.691399)
-      (xy -2.100774 9.691781)
-      (xy -2.309483 9.692244)
-      (xy -2.497093 9.692795)
-      (xy -2.664669 9.693441)
-      (xy -2.813272 9.694188)
-      (xy -2.943968 9.695041)
-      (xy -3.057818 9.696008)
-      (xy -3.155885 9.697094)
-      (xy -3.239234 9.698306)
-      (xy -3.308928 9.69965)
-      (xy -3.366028 9.701132)
-      (xy -3.4116 9.702758)
-      (xy -3.446705 9.704535)
-      (xy -3.472407 9.706468)
-      (xy -3.48977 9.708565)
-      (xy -3.499856 9.710831)
-      (xy -3.500976 9.711255)
-      (xy -3.545504 9.743626)
-      (xy -3.570423 9.790042)
-      (xy -3.575954 9.842661)
-      (xy -3.562318 9.893636)
-      (xy -3.529737 9.935124)
-      (xy -3.494104 9.954915)
-      (xy -3.473503 9.956975)
-      (xy -3.424947 9.958906)
-      (xy -3.350019 9.960708)
-      (xy -3.2503 9.962383)
-      (xy -3.127376 9.963931)
-      (xy -2.98283 9.965354)
-      (xy -2.818243 9.966652)
-      (xy -2.635201 9.967825)
-      (xy -2.435285 9.968876)
-      (xy -2.22008 9.969804)
-      (xy -1.991168 9.970611)
-      (xy -1.750133 9.971298)
-      (xy -1.498558 9.971865)
-      (xy -1.238027 9.972313)
-      (xy -0.970122 9.972643)
-      (xy -0.696427 9.972855)
-      (xy -0.418524 9.972952)
-      (xy -0.137999 9.972934)
-      (xy 0.143567 9.9728)
-      (xy 0.42459 9.972554)
-      (xy 0.703487 9.972194)
-      (xy 0.978675 9.971723)
-      (xy 1.24857 9.97114)
-      (xy 1.511589 9.970447)
-      (xy 1.766149 9.969645)
-      (xy 2.010666 9.968735)
-      (xy 2.243558 9.967717)
-      (xy 2.46324 9.966592)
-      (xy 2.668131 9.965361)
-      (xy 2.856646 9.964026)
-      (xy 3.027202 9.962586)
-      (xy 3.178216 9.961043)
-      (xy 3.308105 9.959397)
-      (xy 3.415285 9.95765)
-      (xy 3.498173 9.955802)
-      (xy 3.555187 9.953854)
-      (xy 3.584742 9.951808)
-      (xy 3.588331 9.951058)
-      (xy 3.630815 9.918952)
-      (xy 3.66056 9.871324)
-      (xy 3.669382 9.829671)
-      (xy 3.656825 9.782507)
-      (xy 3.625101 9.738095)
-      (xy 3.583136 9.708533)
-      (xy 3.578812 9.706891)
-      (xy 3.563699 9.704946)
-      (xy 3.529499 9.703138)
-      (xy 3.475579 9.701464)
-      (xy 3.401306 9.699921)
-      (xy 3.306047 9.698508)
-      (xy 3.189168 9.697219)
-      (xy 3.050037 9.696054)
-      (xy 2.888019 9.695008)
-      (xy 2.702482 9.694079)
-      (xy 2.492792 9.693264)
-      (xy 2.258316 9.69256)
-      (xy 1.998421 9.691964)
-      (xy 1.712474 9.691473)
-      (xy 1.399841 9.691084)
-      (xy 1.05989 9.690795)
-      (xy 0.691986 9.690601)
-      (xy 0.295497 9.690501)
-      (xy 0.040241 9.690485)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b876731e-87d9-4ffb-9b7a-01f50eef7157))
-  (fp_poly
-    (pts
-      (xy -6.928753 -4.045646)
-      (xy -6.927015 -4.007688)
-      (xy -6.917504 -3.990815)
-      (xy -6.89378 -3.986536)
-      (xy -6.883827 -3.986438)
-      (xy -6.828917 -3.974496)
-      (xy -6.770304 -3.942232)
-      (xy -6.738972 -3.916321)
-      (xy -6.732819 -3.905527)
-      (xy -6.74609 -3.899777)
-      (xy -6.783175 -3.897724)
-      (xy -6.799884 -3.897627)
-      (xy -6.861933 -3.890512)
-      (xy -6.91337 -3.871444)
-      (xy -6.947629 -3.843839)
-      (xy -6.958357 -3.815143)
-      (xy -6.966701 -3.796144)
-      (xy -6.973159 -3.794014)
-      (xy -6.981986 -3.780784)
-      (xy -6.987281 -3.747312)
-      (xy -6.987961 -3.727406)
-      (xy -6.985021 -3.687682)
-      (xy -6.977582 -3.663854)
-      (xy -6.973159 -3.660797)
-      (xy -6.958893 -3.649444)
-      (xy -6.958357 -3.645323)
-      (xy -6.947931 -3.623795)
-      (xy -6.92335 -3.595257)
-      (xy -6.894657 -3.569752)
-      (xy -6.871893 -3.557322)
-      (xy -6.870218 -3.557184)
-      (xy -6.855304 -3.546324)
-      (xy -6.854744 -3.542382)
-      (xy -6.842031 -3.530746)
-      (xy -6.809589 -3.526999)
-      (xy -6.765966 -3.530262)
-      (xy -6.719706 -3.539653)
-      (xy -6.679357 -3.554293)
-      (xy -6.666214 -3.561805)
-      (xy -6.635364 -3.586985)
-      (xy -6.618928 -3.608825)
-      (xy -6.618108 -3.612691)
-      (xy -6.608563 -3.629893)
-      (xy -6.603112 -3.631194)
-      (xy -6.593328 -3.644206)
-      (xy -6.588438 -3.676201)
-      (xy -6.58831 -3.683)
-      (xy -6.584592 -3.717243)
-      (xy -6.575451 -3.734359)
-      (xy -6.573508 -3.734807)
-      (xy -6.570273 -3.73881)
-      (xy -6.707525 -3.73881)
-      (xy -6.716905 -3.702116)
-      (xy -6.729767 -3.678893)
-      (xy -6.761751 -3.650437)
-      (xy -6.796248 -3.651215)
-      (xy -6.819786 -3.668131)
-      (xy -6.836126 -3.699718)
-      (xy -6.83618 -3.736392)
-      (xy -6.821782 -3.766299)
-      (xy -6.802937 -3.777097)
-      (xy -6.773234 -3.789353)
-      (xy -6.762459 -3.799427)
-      (xy -6.753025 -3.807434)
-      (xy -6.751357 -3.797715)
-      (xy -6.739208 -3.781317)
-      (xy -6.728928 -3.779212)
-      (xy -6.711507 -3.767578)
-      (xy -6.707525 -3.73881)
-      (xy -6.570273 -3.73881)
-      (xy -6.563115 -3.747669)
-      (xy -6.558708 -3.77866)
-      (xy -6.558706 -3.779212)
-      (xy -6.562994 -3.810391)
-      (xy -6.573324 -3.823614)
-      (xy -6.573508 -3.823618)
-      (xy -6.583292 -3.83663)
-      (xy -6.588182 -3.868625)
-      (xy -6.58831 -3.875424)
-      (xy -6.592028 -3.909667)
-      (xy -6.60117 -3.926783)
-      (xy -6.603112 -3.927231)
-      (xy -6.616045 -3.939302)
-      (xy -6.617914 -3.950668)
-      (xy -6.629621 -3.979343)
-      (xy -6.658907 -4.013808)
-      (xy -6.69702 -4.046322)
-      (xy -6.735208 -4.069146)
-      (xy -6.758801 -4.07525)
-      (xy -6.786489 -4.08035)
-      (xy -6.795536 -4.090051)
-      (xy -6.808766 -4.098879)
-      (xy -6.842239 -4.104174)
-      (xy -6.862145 -4.104853)
-      (xy -6.928753 -4.104853)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 02166560-fc83-4b98-ad86-4f75cfc04e71))
-  (fp_poly
-    (pts
-      (xy 5.104269 -0.619014)
-      (xy 5.072437 -0.595767)
-      (xy 5.046943 -0.573666)
-      (xy 5.027084 -0.549249)
-      (xy 5.012157 -0.519052)
-      (xy 5.001457 -0.479612)
-      (xy 4.994281 -0.427468)
-      (xy 4.989926 -0.359156)
-      (xy 4.987688 -0.271213)
-      (xy 4.986863 -0.160177)
-      (xy 4.986748 -0.0406)
-      (xy 4.986818 0.083808)
-      (xy 4.987194 0.182269)
-      (xy 4.988129 0.258444)
-      (xy 4.989874 0.315989)
-      (xy 4.992681 0.358563)
-      (xy 4.996802 0.389824)
-      (xy 5.002488 0.41343)
-      (xy 5.009992 0.433039)
-      (xy 5.019565 0.452309)
-      (xy 5.020833 0.454713)
-      (xy 5.06946 0.518588)
-      (xy 5.119373 0.553253)
-      (xy 5.183829 0.587338)
-      (xy 6.521486 0.587338)
-      (xy 6.585941 0.553253)
-      (xy 6.649817 0.504626)
-      (xy 6.684481 0.454713)
-      (xy 6.694313 0.435243)
-      (xy 6.702046 0.415863)
-      (xy 6.707932 0.392914)
-      (xy 6.709429 0.382389)
-      (xy 6.600151 0.382389)
-      (xy 6.513617 0.468923)
-      (xy 5.191697 0.468923)
-      (xy 5.105163 0.382389)
-      (xy 5.105163 -0.037812)
-      (xy 5.105242 -0.160463)
-      (xy 5.105637 -0.256981)
-      (xy 5.106585 -0.330836)
-      (xy 5.108323 -0.385499)
-      (xy 5.11109 -0.424439)
-      (xy 5.115123 -0.451127)
-      (xy 5.120658 -0.469033)
-      (xy 5.127934 -0.481628)
-      (xy 5.136188 -0.491314)
-      (xy 5.171616 -0.52083)
-      (xy 5.20376 -0.538511)
-      (xy 5.226546 -0.541629)
-      (xy 5.275854 -0.544478)
-      (xy 5.348601 -0.546992)
-      (xy 5.441707 -0.549105)
-      (xy 5.552091 -0.550751)
-      (xy 5.676669 -0.551864)
-      (xy 5.812362 -0.552378)
-      (xy 5.852657 -0.552406)
-      (xy 5.990954 -0.552075)
-      (xy 6.119016 -0.551126)
-      (xy 6.233761 -0.549625)
-      (xy 6.332107 -0.547639)
-      (xy 6.410973 -0.545232)
-      (xy 6.467278 -0.542472)
-      (xy 6.49794 -0.539423)
-      (xy 6.501554 -0.538511)
-      (xy 6.539247 -0.516955)
-      (xy 6.569126 -0.491314)
-      (xy 6.578176 -0.480533)
-      (xy 6.585271 -0.467571)
-      (xy 6.590649 -0.448958)
-      (xy 6.594547 -0.421224)
-      (xy 6.597203 -0.380898)
-      (xy 6.598854 -0.32451)
-      (xy 6.599737 -0.248589)
-      (xy 6.60009 -0.149666)
-      (xy 6.600151 -0.037812)
-      (xy 6.600151 0.382389)
-      (xy 6.709429 0.382389)
-      (xy 6.712223 0.362739)
-      (xy 6.715171 0.32168)
-      (xy 6.717028 0.266077)
-      (xy 6.718045 0.192274)
-      (xy 6.718473 0.096612)
-      (xy 6.718566 -0.024567)
-      (xy 6.718566 -0.0406)
-      (xy 6.718404 -0.174825)
-      (xy 6.717447 -0.282909)
-      (xy 6.714992 -0.368315)
-      (xy 6.710336 -0.434506)
-      (xy 6.702774 -0.484944)
-      (xy 6.691605 -0.523092)
-      (xy 6.676123 -0.552414)
-      (xy 6.655625 -0.576371)
-      (xy 6.629409 -0.598426)
-      (xy 6.601045 -0.619014)
-      (xy 6.538394 -0.66342)
-      (xy 5.166921 -0.66342)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ebca5cb1-6469-405a-8a34-b68ff0c08fbc))
-  (fp_poly
-    (pts
-      (xy -5.638803 7.191632)
-      (xy -5.6656 7.19844)
-      (xy -5.670595 7.203771)
-      (xy -5.683065 7.215569)
-      (xy -5.70194 7.218573)
-      (xy -5.729604 7.228601)
-      (xy -5.766691 7.254318)
-      (xy -5.790751 7.276039)
-      (xy -5.827761 7.318467)
-      (xy -5.845028 7.355104)
-      (xy -5.848217 7.384102)
-      (xy -5.840851 7.440759)
-      (xy -5.821485 7.488696)
-      (xy -5.79422 7.518862)
-      (xy -5.785264 7.523046)
-      (xy -5.767859 7.532559)
-      (xy -5.775951 7.547943)
-      (xy -5.780506 7.552627)
-      (xy -5.805016 7.570269)
-      (xy -5.817035 7.573818)
-      (xy -5.837449 7.587151)
-      (xy -5.852428 7.622069)
-      (xy -5.861381 7.670954)
-      (xy -5.863718 7.726188)
-      (xy -5.858848 7.78015)
-      (xy -5.84618 7.825223)
-      (xy -5.837721 7.840659)
-      (xy -5.80322 7.885736)
-      (xy -5.775941 7.908675)
-      (xy -5.753936 7.914261)
-      (xy -5.728283 7.922878)
-      (xy -5.722401 7.929063)
-      (xy -5.70444 7.935444)
-      (xy -5.663425 7.94041)
-      (xy -5.605893 7.943341)
-      (xy -5.566108 7.943865)
-      (xy -5.49763 7.94245)
-      (xy -5.448159 7.938493)
-      (xy -5.421992 7.932426)
-      (xy -5.418963 7.929063)
-      (xy -5.406847 7.916241)
-      (xy -5.394823 7.914261)
-      (xy -5.379641 7.908838)
-      (xy -5.376209 7.887655)
-      (xy -5.379859 7.858754)
-      (xy -5.38595 7.817525)
-      (xy -5.38909 7.787758)
-      (xy -5.389196 7.784745)
-      (xy -5.401971 7.770842)
-      (xy -5.426364 7.766242)
-      (xy -5.454181 7.771309)
-      (xy -5.463368 7.781044)
-      (xy -5.47693 7.788825)
-      (xy -5.512708 7.794136)
-      (xy -5.557286 7.795846)
-      (xy -5.627303 7.790216)
-      (xy -5.672492 7.772182)
-      (xy -5.695631 7.740025)
-      (xy -5.700198 7.707501)
-      (xy -5.688307 7.66887)
-      (xy -5.652001 7.644562)
-      (xy -5.590336 7.634038)
-      (xy -5.570682 7.633496)
-      (xy -5.492972 7.633026)
-      (xy -5.492972 7.566417)
-      (xy -5.494254 7.52546)
-      (xy -5.501686 7.506062)
-      (xy -5.52065 7.500187)
-      (xy -5.537579 7.499809)
-      (xy -5.589382 7.491039)
-      (xy -5.636449 7.468815)
-      (xy -5.659267 7.448002)
-      (xy -5.670482 7.411939)
-      (xy -5.661626 7.3741)
-      (xy -5.639883 7.351197)
-      (xy -5.610085 7.343691)
-      (xy -5.570095 7.343085)
-      (xy -5.530377 7.348191)
-      (xy -5.501395 7.357819)
-      (xy -5.492972 7.367893)
-      (xy -5.483889 7.382335)
-      (xy -5.461535 7.378726)
-      (xy -5.433257 7.360261)
-      (xy -5.406497 7.33028)
-      (xy -5.383759 7.286798)
-      (xy -5.385746 7.259498)
-      (xy -5.412449 7.248438)
-      (xy -5.419836 7.248177)
-      (xy -5.443411 7.24181)
-      (xy -5.448567 7.233375)
-      (xy -5.461234 7.222248)
-      (xy -5.485571 7.218573)
-      (xy -5.513389 7.213506)
-      (xy -5.522576 7.203771)
-      (xy -5.535888 7.195328)
-      (xy -5.569926 7.189969)
-      (xy -5.596585 7.18897)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 72f48921-c34c-4b67-a5bb-b1dcbc63f01a))
-  (fp_poly
-    (pts
-      (xy -6.833577 -1.571787)
-      (xy -6.870458 -1.566564)
-      (xy -6.884347 -1.558994)
-      (xy -6.884347 -1.558932)
-      (xy -6.896336 -1.545801)
-      (xy -6.90655 -1.544131)
-      (xy -6.926174 -1.532282)
-      (xy -6.928753 -1.521928)
-      (xy -6.936746 -1.50223)
-      (xy -6.943555 -1.499725)
-      (xy -6.955437 -1.487108)
-      (xy -6.959626 -1.455499)
-      (xy -6.956934 -1.414261)
-      (xy -6.948172 -1.372758)
-      (xy -6.934153 -1.340354)
-      (xy -6.929179 -1.333952)
-      (xy -6.9096 -1.310625)
-      (xy -6.910297 -1.295577)
-      (xy -6.929179 -1.277328)
-      (xy -6.951301 -1.252278)
-      (xy -6.958357 -1.235256)
-      (xy -6.968517 -1.219339)
-      (xy -6.973159 -1.21849)
-      (xy -6.984752 -1.206306)
-      (xy -6.986166 -1.175883)
-      (xy -6.978352 -1.136411)
-      (xy -6.962264 -1.097082)
-      (xy -6.9602 -1.093449)
-      (xy -6.928079 -1.053896)
-      (xy -6.890973 -1.024222)
-      (xy -6.84359 -1.007365)
-      (xy -6.782841 -0.999741)
-      (xy -6.721788 -1.001805)
-      (xy -6.673493 -1.014008)
-      (xy -6.668569 -1.016509)
-      (xy -6.629053 -1.044096)
-      (xy -6.599575 -1.07462)
-      (xy -6.58831 -1.099218)
-      (xy -6.581322 -1.123601)
-      (xy -6.569808 -1.146615)
-      (xy -6.558763 -1.171763)
-      (xy -6.566861 -1.183463)
-      (xy -6.569808 -1.184652)
-      (xy -6.573981 -1.18937)
-      (xy -6.708639 -1.18937)
-      (xy -6.712846 -1.146403)
-      (xy -6.716009 -1.137509)
-      (xy -6.733153 -1.120641)
-      (xy -6.770252 -1.117198)
-      (xy -6.778917 -1.117796)
-      (xy -6.816721 -1.124967)
-      (xy -6.833789 -1.141664)
-      (xy -6.837274 -1.155606)
-      (xy -6.831215 -1.193167)
-      (xy -6.80743 -1.222227)
-      (xy -6.774545 -1.237305)
-      (xy -6.741184 -1.232918)
-      (xy -6.729356 -1.224204)
-      (xy -6.708639 -1.18937)
-      (xy -6.573981 -1.18937)
-      (xy -6.586328 -1.20333)
-      (xy -6.58831 -1.214391)
-      (xy -6.599227 -1.241328)
-      (xy -6.614213 -1.256828)
-      (xy -6.630347 -1.271745)
-      (xy -6.631219 -1.288362)
-      (xy -6.616829 -1.317873)
-      (xy -6.614213 -1.322568)
-      (xy -6.589937 -1.39099)
-      (xy -6.590458 -1.4056)
-      (xy -6.721527 -1.4056)
-      (xy -6.723828 -1.383242)
-      (xy -6.735589 -1.369864)
-      (xy -6.764094 -1.360602)
-      (xy -6.799237 -1.353722)
-      (xy -6.809197 -1.363649)
-      (xy -6.810338 -1.372676)
-      (xy -6.821658 -1.397274)
-      (xy -6.82884 -1.402279)
-      (xy -6.839726 -1.412)
-      (xy -6.82884 -1.419548)
-      (xy -6.811896 -1.440306)
-      (xy -6.810338 -1.449617)
-      (xy -6.79931 -1.473269)
-      (xy -6.773904 -1.479864)
-      (xy -6.74564 -1.466689)
-      (xy -6.74411 -1.465215)
-      (xy -6.726283 -1.433024)
-      (xy -6.721527 -1.4056)
-      (xy -6.590458 -1.4056)
-      (xy -6.592304 -1.45732)
-      (xy -6.620814 -1.515829)
-      (xy -6.632217 -1.528818)
-      (xy -6.657963 -1.552648)
-      (xy -6.682993 -1.566138)
-      (xy -6.716881 -1.572192)
-      (xy -6.769202 -1.573717)
-      (xy -6.780236 -1.573734)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f9dc2e63-0848-4a7d-a10b-eeb320aac8c8))
-  (fp_poly
-    (pts
-      (xy -1.514909 2.692465)
-      (xy -1.576219 2.696969)
-      (xy -1.615932 2.703451)
-      (xy -1.642052 2.714353)
-      (xy -1.66258 2.732117)
-      (xy -1.669173 2.739531)
-      (xy -1.69266 2.77457)
-      (xy -1.703594 2.806123)
-      (xy -1.703695 2.808443)
-      (xy -1.710052 2.832044)
-      (xy -1.718497 2.837221)
-      (xy -1.72972 2.849861)
-      (xy -1.733299 2.873352)
-      (xy -1.738756 2.904694)
-      (xy -1.7481 2.918632)
-      (xy -1.755074 2.936793)
-      (xy -1.76028 2.976735)
-      (xy -1.7628 3.030647)
-      (xy -1.762902 3.044447)
-      (xy -1.761145 3.100502)
-      (xy -1.756486 3.144415)
-      (xy -1.749843 3.168376)
-      (xy -1.7481 3.170263)
-      (xy -1.736364 3.190803)
-      (xy -1.733299 3.213268)
-      (xy -1.723852 3.259409)
-      (xy -1.699977 3.312662)
-      (xy -1.668369 3.359398)
-      (xy -1.654418 3.373789)
-      (xy -1.618627 3.393959)
-      (xy -1.590416 3.399692)
-      (xy -1.563701 3.405058)
-      (xy -1.555676 3.414494)
-      (xy -1.542545 3.423763)
-      (xy -1.509741 3.428919)
-      (xy -1.496469 3.429296)
-      (xy -1.459393 3.426013)
-      (xy -1.438771 3.417812)
-      (xy -1.437261 3.414494)
-      (xy -1.424627 3.40325)
-      (xy -1.401314 3.399692)
-      (xy -1.365121 3.391174)
-      (xy -1.345807 3.378003)
-      (xy -1.31153 3.338493)
-      (xy -1.294087 3.31378)
-      (xy -1.289243 3.297937)
-      (xy -1.277531 3.280833)
-      (xy -1.270757 3.277582)
-      (xy -1.262674 3.265811)
-      (xy -1.257094 3.234724)
-      (xy -1.253741 3.181229)
-      (xy -1.252338 3.102238)
-      (xy -1.252255 3.071552)
-      (xy -1.252328 3.064223)
-      (xy -1.407658 3.064223)
-      (xy -1.409266 3.126342)
-      (xy -1.413699 3.170439)
-      (xy -1.42037 3.191423)
-      (xy -1.422459 3.192466)
-      (xy -1.436097 3.204217)
-      (xy -1.437261 3.211658)
-      (xy -1.444837 3.232707)
-      (xy -1.46223 3.261731)
-      (xy -1.481439 3.286734)
-      (xy -1.493441 3.295883)
-      (xy -1.505682 3.286691)
-      (xy -1.529967 3.263896)
-      (xy -1.534146 3.259747)
-      (xy -1.559153 3.226377)
-      (xy -1.570426 3.194811)
-      (xy -1.570478 3.193139)
-      (xy -1.576553 3.168723)
-      (xy -1.58528 3.162862)
-      (xy -1.592889 3.149183)
-      (xy -1.598142 3.112565)
-      (xy -1.600082 3.060123)
-      (xy -1.598093 3.007619)
-      (xy -1.592872 2.967568)
-      (xy -1.585533 2.948407)
-      (xy -1.58528 2.948235)
-      (xy -1.57316 2.927583)
-      (xy -1.570007 2.906657)
-      (xy -1.557639 2.861013)
-      (xy -1.526634 2.830608)
-      (xy -1.493985 2.822419)
-      (xy -1.458606 2.836414)
-      (xy -1.432247 2.877771)
-      (xy -1.415245 2.945553)
-      (xy -1.407933 3.038823)
-      (xy -1.407658 3.064223)
-      (xy -1.252328 3.064223)
-      (xy -1.253177 2.978908)
-      (xy -1.257098 2.909697)
-      (xy -1.265725 2.857772)
-      (xy -1.280762 2.816991)
-      (xy -1.303915 2.78121)
-      (xy -1.336891 2.744283)
-      (xy -1.345556 2.735474)
-      (xy -1.395167 2.685533)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c01dcac8-f060-491f-9e0d-be52189df53a))
-  (fp_poly
-    (pts
-      (xy 6.033148 7.219918)
-      (xy 5.981395 7.223696)
-      (xy 5.95304 7.229526)
-      (xy 5.948869 7.233375)
-      (xy 5.936511 7.245521)
-      (xy 5.920139 7.248177)
-      (xy 5.889824 7.256321)
-      (xy 5.87914 7.282471)
-      (xy 5.887261 7.329205)
-      (xy 5.890702 7.340139)
-      (xy 5.909185 7.380417)
-      (xy 5.930609 7.405644)
-      (xy 5.949832 7.411484)
-      (xy 5.960317 7.398859)
-      (xy 5.978033 7.384115)
-      (xy 5.993635 7.381394)
-      (xy 6.021455 7.374306)
-      (xy 6.03028 7.366592)
-      (xy 6.049717 7.35707)
-      (xy 6.086433 7.35203)
-      (xy 6.096888 7.35179)
-      (xy 6.136008 7.355281)
-      (xy 6.160923 7.363937)
-      (xy 6.163496 7.366592)
-      (xy 6.184648 7.379646)
-      (xy 6.197674 7.381487)
-      (xy 6.220572 7.393818)
-      (xy 6.245815 7.423654)
-      (xy 6.266196 7.460481)
-      (xy 6.27451 7.493607)
-      (xy 6.282897 7.512523)
-      (xy 6.289312 7.514611)
-      (xy 6.298189 7.52783)
-      (xy 6.303472 7.561229)
-      (xy 6.304114 7.580345)
-      (xy 6.301048 7.622179)
-      (xy 6.293328 7.650272)
-      (xy 6.289312 7.655228)
-      (xy 6.275886 7.676562)
-      (xy 6.27451 7.686844)
-      (xy 6.264676 7.7109)
-      (xy 6.240182 7.743155)
-      (xy 6.231243 7.752579)
-      (xy 6.198691 7.779829)
-      (xy 6.164286 7.792603)
-      (xy 6.114503 7.795844)
-      (xy 6.112828 7.795846)
-      (xy 6.03768 7.795846)
-      (xy 6.03768 7.544214)
-      (xy 5.87486 7.544214)
-      (xy 5.875087 7.725537)
-      (xy 5.876022 7.7968)
-      (xy 5.878403 7.857714)
-      (xy 5.881872 7.901917)
-      (xy 5.886073 7.923044)
-      (xy 5.886188 7.923227)
-      (xy 5.905417 7.931467)
-      (xy 5.947048 7.938883)
-      (xy 6.00388 7.94493)
-      (xy 6.068712 7.949064)
-      (xy 6.134346 7.95074)
-      (xy 6.193578 7.949412)
-      (xy 6.213253 7.947975)
-      (xy 6.280641 7.93011)
-      (xy 6.316715 7.905928)
-      (xy 6.346525 7.881826)
-      (xy 6.368631 7.870003)
-      (xy 6.370571 7.869762)
-      (xy 6.387442 7.857632)
-      (xy 6.408397 7.828568)
-      (xy 6.427035 7.793321)
-      (xy 6.436954 7.762641)
-      (xy 6.437331 7.757642)
-      (xy 6.445718 7.738726)
-      (xy 6.452133 7.736639)
-      (xy 6.459021 7.722571)
-      (xy 6.463998 7.683234)
-      (xy 6.46663 7.622923)
-      (xy 6.466935 7.589494)
-      (xy 6.465525 7.525182)
-      (xy 6.461707 7.473459)
-      (xy 6.456102 7.440862)
-      (xy 6.452133 7.4332)
-      (xy 6.439698 7.412323)
-      (xy 6.437331 7.395322)
-      (xy 6.431699 7.371737)
-      (xy 6.424255 7.366592)
-      (xy 6.410427 7.354276)
-      (xy 6.403458 7.337063)
-      (xy 6.384649 7.307835)
-      (xy 6.368427 7.297474)
-      (xy 6.339312 7.279353)
-      (xy 6.329282 7.267796)
-      (xy 6.305911 7.251256)
-      (xy 6.288577 7.248177)
-      (xy 6.264926 7.241837)
-      (xy 6.259708 7.233375)
-      (xy 6.245593 7.2266)
-      (xy 6.205922 7.221671)
-      (xy 6.144708 7.218971)
-      (xy 6.104289 7.218573)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 7c530122-c77d-40e9-8798-da5c145067d0))
-  (fp_poly
-    (pts
-      (xy 6.570548 2.555986)
-      (xy 6.521242 2.555986)
-      (xy 6.347521 2.555986)
-      (xy 6.296214 2.555986)
-      (xy 6.264986 2.554613)
-      (xy 6.249996 2.545195)
-      (xy 6.245283 2.519781)
-      (xy 6.244907 2.487565)
-      (xy 6.246216 2.447047)
-      (xy 6.251575 2.43101)
-      (xy 6.263124 2.434392)
-      (xy 6.26634 2.436932)
-      (xy 6.287747 2.461064)
-      (xy 6.313042 2.497748)
-      (xy 6.317647 2.505353)
-      (xy 6.347521 2.555986)
-      (xy 6.521242 2.555986)
-      (xy 6.480457 2.549118)
-      (xy 6.455153 2.524324)
-      (xy 6.452133 2.518981)
-      (xy 6.433882 2.492105)
-      (xy 6.420028 2.481977)
-      (xy 6.410079 2.469539)
-      (xy 6.407727 2.451908)
-      (xy 6.398082 2.423446)
-      (xy 6.385524 2.41332)
-      (xy 6.365844 2.394197)
-      (xy 6.363322 2.383311)
-      (xy 6.35377 2.361664)
-      (xy 6.328995 2.327436)
-      (xy 6.301706 2.296084)
-      (xy 6.262826 2.257857)
-      (xy 6.231846 2.237913)
-      (xy 6.198961 2.23081)
-      (xy 6.183291 2.230345)
-      (xy 6.126492 2.230345)
-      (xy 6.126492 2.393165)
-      (xy 6.126151 2.464422)
-      (xy 6.124509 2.511195)
-      (xy 6.120634 2.538601)
-      (xy 6.113597 2.551759)
-      (xy 6.102467 2.555786)
-      (xy 6.096888 2.555986)
-      (xy 6.07752 2.560951)
-      (xy 6.06896 2.581019)
-      (xy 6.067284 2.615193)
-      (xy 6.069767 2.653929)
-      (xy 6.079801 2.671049)
-      (xy 6.096888 2.674401)
-      (xy 6.116256 2.679366)
-      (xy 6.124816 2.699434)
-      (xy 6.126492 2.733608)
-      (xy 6.126492 2.792816)
-      (xy 6.244907 2.792816)
-      (xy 6.244907 2.674401)
-      (xy 6.570548 2.674401)
-      (xy 6.570548 2.792816)
-      (xy 6.688963 2.792816)
-      (xy 6.688963 2.674401)
-      (xy 6.814778 2.674401)
-      (xy 6.876141 2.673779)
-      (xy 6.913641 2.67107)
-      (xy 6.933008 2.665011)
-      (xy 6.939972 2.654338)
-      (xy 6.940594 2.646647)
-      (xy 6.932782 2.580457)
-      (xy 6.918224 2.540663)
-      (xy 6.777774 2.540663)
-      (xy 6.764914 2.551421)
-      (xy 6.733928 2.555985)
-      (xy 6.733368 2.555986)
-      (xy 6.708414 2.554772)
-      (xy 6.695284 2.546378)
-      (xy 6.690357 2.523678)
-      (xy 6.690014 2.479546)
-      (xy 6.690131 2.470875)
-      (xy 6.692007 2.429566)
-      (xy 6.695719 2.407387)
-      (xy 6.699751 2.407967)
-      (xy 6.712505 2.43204)
-      (xy 6.717427 2.437571)
-      (xy 6.73487 2.458433)
-      (xy 6.755614 2.491227)
-      (xy 6.772292 2.523373)
-      (xy 6.777774 2.540663)
-      (xy 6.918224 2.540663)
-      (xy 6.911889 2.523348)
-      (xy 6.894543 2.498423)
-      (xy 6.87389 2.47198)
-      (xy 6.866585 2.455377)
-      (xy 6.857703 2.437176)
-      (xy 6.835252 2.406235)
-      (xy 6.822231 2.390415)
-      (xy 6.785506 2.344859)
-      (xy 6.750498 2.297534)
-      (xy 6.74403 2.288118)
-      (xy 6.718308 2.255993)
-      (xy 6.689717 2.240067)
-      (xy 6.645493 2.233582)
-      (xy 6.640365 2.233234)
-      (xy 6.570548 2.228723)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6fdca661-9984-41bd-b3fd-a9d5e9a9ab58))
-  (fp_poly
-    (pts
-      (xy -6.106609 -0.40344)
-      (xy -6.135022 -0.398747)
-      (xy -6.144254 -0.391266)
-      (xy -6.157414 -0.38141)
-      (xy -6.190649 -0.371746)
-      (xy -6.209432 -0.368371)
-      (xy -6.252597 -0.358711)
-      (xy -6.274918 -0.343059)
-      (xy -6.283723 -0.322284)
-      (xy -6.295614 -0.294889)
-      (xy -6.307357 -0.285972)
-      (xy -6.319272 -0.273611)
-      (xy -6.321877 -0.257242)
-      (xy -6.328673 -0.228906)
-      (xy -6.336678 -0.219364)
-      (xy -6.344323 -0.200306)
-      (xy -6.349091 -0.159605)
-      (xy -6.351069 -0.105071)
-      (xy -6.350345 -0.044516)
-      (xy -6.347007 0.014249)
-      (xy -6.341143 0.063413)
-      (xy -6.333151 0.094479)
-      (xy -6.313686 0.131156)
-      (xy -6.296146 0.155441)
-      (xy -6.279882 0.183027)
-      (xy -6.277471 0.195691)
-      (xy -6.26582 0.213857)
-      (xy -6.235431 0.240774)
-      (xy -6.197377 0.267617)
-      (xy -6.140916 0.299327)
-      (xy -6.086264 0.317977)
-      (xy -6.018333 0.328587)
-      (xy -6.012354 0.329192)
-      (xy -5.907424 0.339531)
-      (xy -5.907424 0.301488)
-      (xy -5.90223 0.269396)
-      (xy -5.892623 0.254296)
-      (xy -5.879003 0.232879)
-      (xy -5.877821 0.223819)
-      (xy -5.887606 0.209553)
-      (xy -5.919906 0.203169)
-      (xy -5.944429 0.202489)
-      (xy -5.984153 0.199549)
-      (xy -6.007981 0.192111)
-      (xy -6.011037 0.187688)
-      (xy -6.02344 0.175679)
-      (xy -6.040769 0.172886)
-      (xy -6.066935 0.164207)
-      (xy -6.101325 0.143085)
-      (xy -6.134151 0.116892)
-      (xy -6.155625 0.092998)
-      (xy -6.159056 0.083812)
-      (xy -6.145527 0.078482)
-      (xy -6.110028 0.074227)
-      (xy -6.060192 0.071956)
-      (xy -6.059305 0.07194)
-      (xy -6.008351 0.068988)
-      (xy -5.970681 0.062884)
-      (xy -5.954458 0.054955)
-      (xy -5.937831 0.040148)
-      (xy -5.933816 0.039669)
-      (xy -5.908418 0.026866)
-      (xy -5.880671 -0.005783)
-      (xy -5.856279 -0.049634)
-      (xy -5.840947 -0.096044)
-      (xy -5.839756 -0.102858)
-      (xy -5.838056 -0.153894)
-      (xy -5.996236 -0.153894)
-      (xy -6.002228 -0.12923)
-      (xy -6.011037 -0.123152)
-      (xy -6.025072 -0.111632)
-      (xy -6.025839 -0.106281)
-      (xy -6.038748 -0.079604)
-      (xy -6.070594 -0.060242)
-      (xy -6.111058 -0.050997)
-      (xy -6.14982 -0.05467)
-      (xy -6.170898 -0.066905)
-      (xy -6.181864 -0.090224)
-      (xy -6.187543 -0.125802)
-      (xy -6.187685 -0.162654)
-      (xy -6.18204 -0.189792)
-      (xy -6.173858 -0.197161)
-      (xy -6.160726 -0.20915)
-      (xy -6.159056 -0.219364)
-      (xy -6.146806 -0.237607)
-      (xy -6.130686 -0.241567)
-      (xy -6.104187 -0.249914)
-      (xy -6.096172 -0.259998)
-      (xy -6.084073 -0.263732)
-      (xy -6.06195 -0.249426)
-      (xy -6.036081 -0.223746)
-      (xy -6.012748 -0.193361)
-      (xy -5.998229 -0.164937)
-      (xy -5.996236 -0.153894)
-      (xy -5.838056 -0.153894)
-      (xy -5.837084 -0.183075)
-      (xy -5.854198 -0.248228)
-      (xy -5.875604 -0.280271)
-      (xy -5.899579 -0.311632)
-      (xy -5.910872 -0.332682)
-      (xy -5.930926 -0.35301)
-      (xy -5.965462 -0.367125)
-      (xy -5.999875 -0.378149)
-      (xy -6.019135 -0.390712)
-      (xy -6.019142 -0.390724)
-      (xy -6.037162 -0.399378)
-      (xy -6.070153 -0.403633)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9b1d2a1f-16b8-4f13-af80-ca5035fc8a0b))
-  (fp_poly
-    (pts
-      (xy -6.098839 -8.008623)
-      (xy -6.121046 -7.99905)
-      (xy -6.122051 -7.997744)
-      (xy -6.142447 -7.986302)
-      (xy -6.167465 -7.982942)
-      (xy -6.201715 -7.972487)
-      (xy -6.240072 -7.946641)
-      (xy -6.273048 -7.913684)
-      (xy -6.291157 -7.881893)
-      (xy -6.292273 -7.874026)
-      (xy -6.299659 -7.853017)
-      (xy -6.307075 -7.849725)
-      (xy -6.316501 -7.837071)
-      (xy -6.321094 -7.806916)
-      (xy -6.320819 -7.770971)
-      (xy -6.315645 -7.740948)
-      (xy -6.30741 -7.728843)
-      (xy -6.290756 -7.709626)
-      (xy -6.283052 -7.674699)
-      (xy -6.28527 -7.636858)
-      (xy -6.298308 -7.608974)
-      (xy -6.317407 -7.580567)
-      (xy -6.321877 -7.56302)
-      (xy -6.330494 -7.537367)
-      (xy -6.336678 -7.531485)
-      (xy -6.34614 -7.512077)
-      (xy -6.35121 -7.475264)
-      (xy -6.35148 -7.464003)
-      (xy -6.348152 -7.427251)
-      (xy -6.33985 -7.407026)
-      (xy -6.336678 -7.405669)
-      (xy -6.323547 -7.39368)
-      (xy -6.321877 -7.383466)
-      (xy -6.315755 -7.363743)
-      (xy -6.310585 -7.361263)
-      (xy -6.296726 -7.349358)
-      (xy -6.284681 -7.327959)
-      (xy -6.260538 -7.300048)
-      (xy -6.236766 -7.289925)
-      (xy -6.210739 -7.281024)
-      (xy -6.203462 -7.271423)
-      (xy -6.189706 -7.26564)
-      (xy -6.152613 -7.261053)
-      (xy -6.09844 -7.258246)
-      (xy -6.055443 -7.25765)
-      (xy -5.986681 -7.259058)
-      (xy -5.936967 -7.262995)
-      (xy -5.910566 -7.269036)
-      (xy -5.907424 -7.272452)
-      (xy -5.895015 -7.284441)
-      (xy -5.877539 -7.287254)
-      (xy -5.861035 -7.290029)
-      (xy -5.854169 -7.30221)
-      (xy -5.856686 -7.329586)
-      (xy -5.868329 -7.377943)
-      (xy -5.872793 -7.394568)
-      (xy -5.889824 -7.416501)
-      (xy -5.914734 -7.418282)
-      (xy -5.929627 -7.405669)
-      (xy -5.948248 -7.397776)
-      (xy -5.987208 -7.392406)
-      (xy -6.027386 -7.390867)
-      (xy -6.081507 -7.392966)
-      (xy -6.11674 -7.401305)
-      (xy -6.143629 -7.418952)
-      (xy -6.152328 -7.427199)
-      (xy -6.181332 -7.462629)
-      (xy -6.185215 -7.490726)
-      (xy -6.164328 -7.519247)
-      (xy -6.156791 -7.526048)
-      (xy -6.112693 -7.547553)
-      (xy -6.053178 -7.553688)
-      (xy -5.981434 -7.553688)
-      (xy -5.981434 -7.701706)
-      (xy -6.03324 -7.701706)
-      (xy -6.067488 -7.705022)
-      (xy -6.084601 -7.713176)
-      (xy -6.085047 -7.714904)
-      (xy -6.097591 -7.727934)
-      (xy -6.122051 -7.737388)
-      (xy -6.151373 -7.75617)
-      (xy -6.160544 -7.785397)
-      (xy -6.149111 -7.813938)
-      (xy -6.125752 -7.82852)
-      (xy -6.09503 -7.843331)
-      (xy -6.081798 -7.855421)
-      (xy -6.065236 -7.864331)
-      (xy -6.044224 -7.855256)
-      (xy -6.012232 -7.841944)
-      (xy -5.967556 -7.830326)
-      (xy -5.958018 -7.828568)
-      (xy -5.919182 -7.823983)
-      (xy -5.897468 -7.831282)
-      (xy -5.881078 -7.856025)
-      (xy -5.875548 -7.867443)
-      (xy -5.861599 -7.901005)
-      (xy -5.863653 -7.92189)
-      (xy -5.884287 -7.943802)
-      (xy -5.890993 -7.94962)
-      (xy -5.929907 -7.972995)
-      (xy -5.969819 -7.982921)
-      (xy -5.970332 -7.982924)
-      (xy -5.999873 -7.987581)
-      (xy -6.011037 -7.997744)
-      (xy -6.024034 -8.007594)
-      (xy -6.055922 -8.012441)
-      (xy -6.06197 -8.012546)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 8b8e783c-5e19-4f18-a7ba-a648e46b66c7))
-  (fp_poly
-    (pts
-      (xy -5.452883 -8.262763)
-      (xy -5.577415 -8.262259)
-      (xy -5.727873 -8.261394)
-      (xy -5.783756 -8.261046)
-      (xy -6.462494 -8.256776)
-      (xy -6.510012 -8.222883)
-      (xy -6.552343 -8.186168)
-      (xy -6.589891 -8.143588)
-      (xy -6.591422 -8.141473)
-      (xy -6.600915 -8.127509)
-      (xy -6.608446 -8.112935)
-      (xy -6.614242 -8.09436)
-      (xy -6.618531 -8.06839)
-      (xy -6.621539 -8.031633)
-      (xy -6.623493 -7.980698)
-      (xy -6.624621 -7.912192)
-      (xy -6.625149 -7.822722)
-      (xy -6.625305 -7.708897)
-      (xy -6.625315 -7.635098)
-      (xy -6.625266 -7.506513)
-      (xy -6.62497 -7.404139)
-      (xy -6.624198 -7.324584)
-      (xy -6.622724 -7.264456)
-      (xy -6.62032 -7.220363)
-      (xy -6.616761 -7.188912)
-      (xy -6.611817 -7.166711)
-      (xy -6.605263 -7.150368)
-      (xy -6.596872 -7.136491)
-      (xy -6.591422 -7.128723)
-      (xy -6.554706 -7.086391)
-      (xy -6.512126 -7.048843)
-      (xy -6.510012 -7.047313)
-      (xy -6.462494 -7.01342)
-      (xy -5.789009 -7.010704)
-      (xy -5.649326 -7.0104)
-      (xy -5.517766 -7.010611)
-      (xy -5.397493 -7.011297)
-      (xy -5.291671 -7.012417)
-      (xy -5.203466 -7.01393)
-      (xy -5.136041 -7.015794)
-      (xy -5.092561 -7.017971)
-      (xy -5.077241 -7.019878)
-      (xy -5.003529 -7.05605)
-      (xy -4.947426 -7.114732)
-      (xy -4.932693 -7.1385)
-      (xy -4.92342 -7.155789)
-      (xy -4.916107 -7.173264)
-      (xy -4.910558 -7.194413)
-      (xy -4.90658 -7.222724)
-      (xy -4.903978 -7.261682)
-      (xy -4.902557 -7.314776)
-      (xy -4.902123 -7.385492)
-      (xy -4.902481 -7.477318)
-      (xy -4.903436 -7.593741)
-      (xy -4.903908 -7.644198)
-      (xy -5.004511 -7.644198)
-      (xy -5.00513 -7.529504)
-      (xy -5.006896 -7.428181)
-      (xy -5.009674 -7.343895)
-      (xy -5.013328 -7.280314)
-      (xy -5.01772 -7.241105)
-      (xy -5.01978 -7.232711)
-      (xy -5.042351 -7.193566)
-      (xy -5.075213 -7.157873)
-      (xy -5.075287 -7.157811)
-      (xy -5.115525 -7.124581)
-      (xy -5.764586 -7.124507)
-      (xy -6.413648 -7.124434)
-      (xy -6.463975 -7.17476)
-      (xy -6.514301 -7.225086)
-      (xy -6.514301 -8.04511)
-      (xy -6.463975 -8.095436)
-      (xy -6.413648 -8.145762)
-      (xy -5.603392 -8.145762)
-      (xy -5.469551 -8.145546)
-      (xy -5.360001 -8.144795)
-      (xy -5.272085 -8.143187)
-      (xy -5.203147 -8.140404)
-      (xy -5.150531 -8.136123)
-      (xy -5.11158 -8.130025)
-      (xy -5.083637 -8.121789)
-      (xy -5.064047 -8.111095)
-      (xy -5.050153 -8.097623)
-      (xy -5.039298 -8.081051)
-      (xy -5.028826 -8.06106)
-      (xy -5.026629 -8.056788)
-      (xy -5.019483 -8.037694)
-      (xy -5.013984 -8.009116)
-      (xy -5.009941 -7.967515)
-      (xy -5.007165 -7.909351)
-      (xy -5.005465 -7.831084)
-      (xy -5.004653 -7.729175)
-      (xy -5.004511 -7.644198)
-      (xy -4.903908 -7.644198)
-      (xy -4.90399 -7.652998)
-      (xy -4.908299 -8.108758)
-      (xy -4.944418 -8.156906)
-      (xy -4.981495 -8.194288)
-      (xy -5.029283 -8.228003)
-      (xy -5.042778 -8.235185)
-      (xy -5.058337 -8.242261)
-      (xy -5.074949 -8.24811)
-      (xy -5.095379 -8.252827)
-      (xy -5.12239 -8.256508)
-      (xy -5.158745 -8.259251)
-      (xy -5.207209 -8.261151)
-      (xy -5.270544 -8.262306)
-      (xy -5.351514 -8.262811)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0fc04686-f385-4136-b1ed-96815229ea7f))
-  (fp_poly
-    (pts
-      (xy -5.784051 -0.667702)
-      (xy -6.449898 -0.66342)
-      (xy -6.50991 -0.623691)
-      (xy -6.566077 -0.572383)
-      (xy -6.602147 -0.517394)
-      (xy -6.611388 -0.49726)
-      (xy -6.618623 -0.477023)
-      (xy -6.624052 -0.453036)
-      (xy -6.627876 -0.421648)
-      (xy -6.630296 -0.379209)
-      (xy -6.631514 -0.32207)
-      (xy -6.63173 -0.246581)
-      (xy -6.631146 -0.149092)
-      (xy -6.629962 -0.025954)
-      (xy -6.629844 -0.014499)
-      (xy -6.625315 0.421828)
-      (xy -6.579857 0.47868)
-      (xy -6.560218 0.50325)
-      (xy -6.542192 0.523808)
-      (xy -6.523083 0.540709)
-      (xy -6.50019 0.554309)
-      (xy -6.470814 0.564964)
-      (xy -6.432258 0.573032)
-      (xy -6.381821 0.578867)
-      (xy -6.316807 0.582826)
-      (xy -6.234514 0.585267)
-      (xy -6.132246 0.586543)
-      (xy -6.007303 0.587013)
-      (xy -5.856986 0.587032)
-      (xy -5.759406 0.586978)
-      (xy -5.598221 0.586804)
-      (xy -5.463965 0.586384)
-      (xy -5.353966 0.585629)
-      (xy -5.26555 0.584447)
-      (xy -5.196043 0.582747)
-      (xy -5.142773 0.58044)
-      (xy -5.103064 0.577433)
-      (xy -5.074244 0.573636)
-      (xy -5.05364 0.568959)
-      (xy -5.038577 0.563311)
-      (xy -5.036773 0.562445)
-      (xy -4.995496 0.534353)
-      (xy -4.955394 0.495408)
-      (xy -4.947962 0.486251)
-      (xy -4.908299 0.434277)
-      (xy -4.90399 -0.022662)
-      (xy -4.902943 -0.138993)
-      (xy -5.006419 -0.138993)
-      (xy -5.007527 -0.009741)
-      (xy -5.011912 0.382584)
-      (xy -5.060251 0.425754)
-      (xy -5.108591 0.468923)
-      (xy -5.76334 0.468594)
-      (xy -5.920702 0.468437)
-      (xy -6.051134 0.468073)
-      (xy -6.157307 0.4674)
-      (xy -6.241893 0.466318)
-      (xy -6.307565 0.464725)
-      (xy -6.356995 0.462521)
-      (xy -6.392856 0.459606)
-      (xy -6.41782 0.455877)
-      (xy -6.43456 0.451235)
-      (xy -6.445746 0.445577)
-      (xy -6.449661 0.442691)
-      (xy -6.468217 0.426275)
-      (xy -6.482843 0.408171)
-      (xy -6.494004 0.384841)
-      (xy -6.502167 0.352751)
-      (xy -6.507796 0.308364)
-      (xy -6.511358 0.248145)
-      (xy -6.513319 0.168558)
-      (xy -6.514144 0.066067)
-      (xy -6.514301 -0.047936)
-      (xy -6.514301 -0.448326)
-      (xy -6.47112 -0.496665)
-      (xy -6.427939 -0.545005)
-      (xy -5.782972 -0.549157)
-      (xy -5.625504 -0.550067)
-      (xy -5.494914 -0.550532)
-      (xy -5.388481 -0.550477)
-      (xy -5.303481 -0.549824)
-      (xy -5.237192 -0.548497)
-      (xy -5.186892 -0.546418)
-      (xy -5.149857 -0.543511)
-      (xy -5.123365 -0.539699)
-      (xy -5.104693 -0.534905)
-      (xy -5.092295 -0.529672)
-      (xy -5.067264 -0.514868)
-      (xy -5.047402 -0.496988)
-      (xy -5.032166 -0.472709)
-      (xy -5.021015 -0.438707)
-      (xy -5.013407 -0.391657)
-      (xy -5.008799 -0.328238)
-      (xy -5.006651 -0.245124)
-      (xy -5.006419 -0.138993)
-      (xy -4.902943 -0.138993)
-      (xy -4.902835 -0.151053)
-      (xy -4.90219 -0.253323)
-      (xy -4.902249 -0.332957)
-      (xy -4.903206 -0.393435)
-      (xy -4.905257 -0.438241)
-      (xy -4.908595 -0.470857)
-      (xy -4.913416 -0.494765)
-      (xy -4.919913 -0.513448)
-      (xy -4.928282 -0.530388)
-      (xy -4.932808 -0.538544)
-      (xy -4.97273 -0.589489)
-      (xy -5.032199 -0.62976)
-      (xy -5.04207 -0.634736)
-      (xy -5.118205 -0.671985)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 848082e4-3d9d-420b-870f-06f0c7729e48))
-  (fp_poly
-    (pts
-      (xy 5.686755 6.937355)
-      (xy 5.54686 6.937628)
-      (xy 5.431249 6.938484)
-      (xy 5.337261 6.940253)
-      (xy 5.262236 6.943265)
-      (xy 5.203515 6.947848)
-      (xy 5.158437 6.954333)
-      (xy 5.124343 6.963047)
-      (xy 5.098572 6.974321)
-      (xy 5.078464 6.988484)
-      (xy 5.061359 7.005864)
-      (xy 5.044597 7.026792)
-      (xy 5.035591 7.038587)
-      (xy 4.994149 7.092757)
-      (xy 4.994149 8.027579)
-      (xy 5.034019 8.079851)
-      (xy 5.051488 8.10253)
-      (xy 5.068094 8.121527)
-      (xy 5.08649 8.137165)
-      (xy 5.109329 8.149771)
-      (xy 5.139263 8.159668)
-      (xy 5.178945 8.167182)
-      (xy 5.231029 8.172637)
-      (xy 5.298166 8.176358)
-      (xy 5.383011 8.17867)
-      (xy 5.488215 8.179898)
-      (xy 5.616432 8.180367)
-      (xy 5.770314 8.180401)
-      (xy 5.854894 8.180358)
-      (xy 6.016729 8.180179)
-      (xy 6.151622 8.179759)
-      (xy 6.262236 8.179008)
-      (xy 6.351233 8.177836)
-      (xy 6.421274 8.176153)
-      (xy 6.475022 8.173869)
-      (xy 6.515138 8.170895)
-      (xy 6.544286 8.16714)
-      (xy 6.565126 8.162515)
-      (xy 6.580321 8.15693)
-      (xy 6.582691 8.155801)
-      (xy 6.623969 8.12771)
-      (xy 6.664072 8.088766)
-      (xy 6.671502 8.079612)
-      (xy 6.711165 8.027641)
-      (xy 6.715683 7.585063)
-      (xy 6.71592 7.560314)
-      (xy 6.600151 7.560314)
-      (xy 6.600068 7.681218)
-      (xy 6.599651 7.776101)
-      (xy 6.598648 7.848547)
-      (xy 6.596805 7.902136)
-      (xy 6.593872 7.940453)
-      (xy 6.589595 7.967079)
-      (xy 6.583723 7.985597)
-      (xy 6.576003 7.99959)
-      (xy 6.568503 8.00971)
-      (xy 6.537331 8.041599)
-      (xy 6.506145 8.062581)
-      (xy 6.505595 8.062811)
-      (xy 6.484538 8.065462)
-      (xy 6.437093 8.067791)
-      (xy 6.366476 8.069751)
-      (xy 6.275902 8.071295)
-      (xy 6.168585 8.072375)
-      (xy 6.047742 8.072945)
-      (xy 5.916587 8.072956)
-      (xy 5.835114 8.072679)
-      (xy 5.195893 8.069681)
-      (xy 5.150528 8.026206)
-      (xy 5.105163 7.982732)
-      (xy 5.105163 7.566941)
-      (xy 5.105352 7.442621)
-      (xy 5.10604 7.344489)
-      (xy 5.107411 7.269133)
-      (xy 5.109647 7.213137)
-      (xy 5.112931 7.173089)
-      (xy 5.117447 7.145576)
-      (xy 5.123378 7.127183)
-      (xy 5.1293 7.11669)
-      (xy 5.142896 7.098778)
-      (xy 5.15814 7.083934)
-      (xy 5.177779 7.071871)
-      (xy 5.204561 7.062301)
-      (xy 5.241233 7.054936)
-      (xy 5.290542 7.049489)
-      (xy 5.355236 7.045673)
-      (xy 5.438063 7.043198)
-      (xy 5.541769 7.041779)
-      (xy 5.669103 7.041126)
-      (xy 5.822811 7.040953)
-      (xy 5.852657 7.040951)
-      (xy 6.011268 7.04107)
-      (xy 6.143024 7.041617)
-      (xy 6.250671 7.042882)
-      (xy 6.336956 7.04515)
-      (xy 6.404628 7.048711)
-      (xy 6.456434 7.053852)
-      (xy 6.495121 7.060859)
-      (xy 6.523437 7.070022)
-      (xy 6.544129 7.081628)
-      (xy 6.559944 7.095964)
-      (xy 6.573631 7.113318)
-      (xy 6.576014 7.11669)
-      (xy 6.58327 7.130332)
-      (xy 6.588939 7.150391)
-      (xy 6.59321 7.180314)
-      (xy 6.596269 7.223544)
-      (xy 6.598304 7.283525)
-      (xy 6.599503 7.363703)
-      (xy 6.600052 7.467521)
-      (xy 6.600151 7.560314)
-      (xy 6.71592 7.560314)
-      (xy 6.716895 7.458609)
-      (xy 6.717531 7.358145)
-      (xy 6.717397 7.280057)
-      (xy 6.716299 7.220735)
-      (xy 6.714042 7.176565)
-      (xy 6.710432 7.143935)
-      (xy 6.705275 7.119234)
-      (xy 6.698378 7.098849)
-      (xy 6.689545 7.079167)
-      (xy 6.688358 7.076706)
-      (xy 6.640738 7.0097)
-      (xy 6.593729 6.974133)
-      (xy 6.530942 6.937338)
-      (xy 5.853594 6.937338)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 19abbea2-e42c-4827-a17c-a2569e8e2c04))
-  (fp_poly
-    (pts
-      (xy -5.353694 9.412368)
-      (xy -5.511164 9.413404)
-      (xy -5.641791 9.414398)
-      (xy -5.748336 9.415495)
-      (xy -5.83356 9.416845)
-      (xy -5.900224 9.418592)
-      (xy -5.951087 9.420885)
-      (xy -5.988911 9.42387)
-      (xy -6.016457 9.427695)
-      (xy -6.036485 9.432507)
-      (xy -6.051755 9.438452)
-      (xy -6.065029 9.445679)
-      (xy -6.073199 9.450701)
-      (xy -6.1179 9.486915)
-      (xy -6.157005 9.53194)
-      (xy -6.16201 9.539512)
-      (xy -6.171598 9.555647)
-      (xy -6.179193 9.572073)
-      (xy -6.185026 9.592256)
-      (xy -6.189332 9.619663)
-      (xy -6.192341 9.657761)
-      (xy -6.194285 9.710017)
-      (xy -6.195397 9.779899)
-      (xy -6.19591 9.870872)
-      (xy -6.196054 9.986404)
-      (xy -6.196061 10.048056)
-      (xy -6.196061 10.501839)
-      (xy -6.151284 10.557162)
-      (xy -6.131137 10.58212)
-      (xy -6.112787 10.602998)
-      (xy -6.093526 10.620161)
-      (xy -6.070647 10.633972)
-      (xy -6.041442 10.644795)
-      (xy -6.003203 10.652993)
-      (xy -5.953223 10.65893)
-      (xy -5.888794 10.662969)
-      (xy -5.807208 10.665474)
-      (xy -5.705759 10.666808)
-      (xy -5.581737 10.667336)
-      (xy -5.432436 10.667419)
-      (xy -5.330152 10.667408)
-      (xy -5.170506 10.667343)
-      (xy -5.037736 10.667078)
-      (xy -4.929116 10.666511)
-      (xy -4.841919 10.665538)
-      (xy -4.773416 10.664056)
-      (xy -4.720882 10.661963)
-      (xy -4.681588 10.659154)
-      (xy -4.652809 10.655527)
-      (xy -4.631817 10.65098)
-      (xy -4.615884 10.645407)
-      (xy -4.604629 10.639973)
-      (xy -4.564641 10.610816)
-      (xy -4.523575 10.569058)
-      (xy -4.508648 10.549923)
-      (xy -4.464243 10.487308)
-      (xy -4.459685 10.064894)
-      (xy -4.457849 9.894679)
-      (xy -4.57694 9.894679)
-      (xy -4.577721 10.006042)
-      (xy -4.578281 10.060158)
-      (xy -4.582658 10.458288)
-      (xy -4.626132 10.50364)
-      (xy -4.669606 10.548993)
-      (xy -5.329221 10.548522)
-      (xy -5.497694 10.54819)
-      (xy -5.638501 10.547419)
-      (xy -5.753581 10.546156)
-      (xy -5.844867 10.54435)
-      (xy -5.914297 10.541948)
-      (xy -5.963808 10.538898)
-      (xy -5.995334 10.535146)
-      (xy -6.010812 10.53064)
-      (xy -6.011717 10.53002)
-      (xy -6.033081 10.51224)
-      (xy -6.049835 10.494061)
-      (xy -6.062539 10.471823)
-      (xy -6.071751 10.441868)
-      (xy -6.078033 10.400537)
-      (xy -6.081943 10.34417)
-      (xy -6.084042 10.26911)
-      (xy -6.08489 10.171696)
-      (xy -6.085047 10.050801)
-      (xy -6.084506 9.942595)
-      (xy -6.082979 9.843522)
-      (xy -6.08061 9.757823)
-      (xy -6.077542 9.689741)
-      (xy -6.073919 9.643519)
-      (xy -6.070614 9.624847)
-      (xy -6.048307 9.591673)
-      (xy -6.012758 9.560564)
-      (xy -6.007706 9.55733)
-      (xy -5.994752 9.550118)
-      (xy -5.979891 9.544183)
-      (xy -5.960282 9.539402)
-      (xy -5.93309 9.535649)
-      (xy -5.895476 9.5328)
-      (xy -5.844602 9.530731)
-      (xy -5.777631 9.529317)
-      (xy -5.691724 9.528433)
-      (xy -5.584045 9.527955)
-      (xy -5.451754 9.527758)
-      (xy -5.333117 9.52772)
-      (xy -5.172453 9.527764)
-      (xy -5.03872 9.528143)
-      (xy -4.929246 9.529184)
-      (xy -4.841357 9.531211)
-      (xy -4.772382 9.534549)
-      (xy -4.719647 9.539524)
-      (xy -4.68048 9.546462)
-      (xy -4.652208 9.555686)
-      (xy -4.632159 9.567523)
-      (xy -4.61766 9.582297)
-      (xy -4.606038 9.600335)
-      (xy -4.597033 9.617299)
-      (xy -4.589979 9.634837)
-      (xy -4.584609 9.659097)
-      (xy -4.580771 9.693645)
-      (xy -4.578314 9.742047)
-      (xy -4.577087 9.80787)
-      (xy -4.57694 9.894679)
-      (xy -4.457849 9.894679)
-      (xy -4.455128 9.642481)
-      (xy -4.493721 9.563601)
-      (xy -4.522143 9.513223)
-      (xy -4.553736 9.479761)
-      (xy -4.599972 9.451713)
-      (xy -4.610632 9.446403)
-      (xy -4.68895 9.408085)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c8309b40-4946-4ab3-8617-d2a9bb13b74d))
-  (fp_poly
-    (pts
-      (xy -6.509888 -3.15481)
-      (xy -6.566137 -3.103431)
-      (xy -6.602147 -3.048513)
-      (xy -6.611388 -3.028379)
-      (xy -6.618623 -3.008142)
-      (xy -6.624052 -2.984155)
-      (xy -6.627876 -2.952767)
-      (xy -6.630296 -2.910328)
-      (xy -6.631514 -2.853189)
-      (xy -6.63173 -2.7777)
-      (xy -6.631146 -2.680211)
-      (xy -6.629962 -2.557073)
-      (xy -6.629844 -2.545618)
-      (xy -6.625315 -2.109291)
-      (xy -6.580538 -2.053997)
-      (xy -6.560274 -2.028926)
-      (xy -6.541803 -2.007974)
-      (xy -6.522401 -1.990772)
-      (xy -6.499341 -1.976951)
-      (xy -6.469899 -1.966141)
-      (xy -6.431348 -1.957974)
-      (xy -6.380964 -1.95208)
-      (xy -6.316019 -1.948089)
-      (xy -6.23379 -1.945634)
-      (xy -6.131549 -1.944343)
-      (xy -6.006572 -1.943849)
-      (xy -5.856133 -1.943782)
-      (xy -5.767038 -1.943793)
-      (xy -5.609054 -1.943836)
-      (xy -5.477878 -1.944038)
-      (xy -5.370712 -1.944521)
-      (xy -5.28476 -1.945402)
-      (xy -5.217225 -1.946803)
-      (xy -5.165311 -1.948842)
-      (xy -5.126222 -1.951639)
-      (xy -5.09716 -1.955315)
-      (xy -5.075329 -1.959988)
-      (xy -5.057932 -1.965779)
-      (xy -5.042174 -1.972807)
-      (xy -5.03767 -1.975015)
-      (xy -4.990899 -2.004818)
-      (xy -4.95059 -2.041394)
-      (xy -4.941458 -2.052713)
-      (xy -4.932125 -2.066671)
-      (xy -4.924691 -2.081748)
-      (xy -4.918901 -2.101347)
-      (xy -4.914501 -2.128873)
-      (xy -4.911238 -2.167731)
-      (xy -4.908858 -2.221323)
-      (xy -4.907106 -2.293055)
-      (xy -4.905728 -2.38633)
-      (xy -4.904472 -2.504552)
-      (xy -4.904204 -2.53261)
-      (xy -5.002623 -2.53261)
-      (xy -5.003927 -2.433617)
-      (xy -5.006677 -2.34167)
-      (xy -5.010868 -2.261905)
-      (xy -5.016492 -2.199461)
-      (xy -5.023542 -2.159475)
-      (xy -5.026629 -2.151171)
-      (xy -5.037314 -2.130508)
-      (xy -5.047861 -2.113319)
-      (xy -5.060922 -2.099284)
-      (xy -5.079148 -2.088086)
-      (xy -5.105192 -2.079407)
-      (xy -5.141704 -2.07293)
-      (xy -5.191336 -2.068336)
-      (xy -5.25674 -2.065309)
-      (xy -5.340567 -2.063529)
-      (xy -5.445469 -2.062681)
-      (xy -5.574097 -2.062445)
-      (xy -5.729104 -2.062504)
-      (xy -5.7664 -2.062525)
-      (xy -5.923368 -2.062682)
-      (xy -6.053412 -2.063049)
-      (xy -6.159211 -2.063726)
-      (xy -6.243443 -2.064816)
-      (xy -6.308789 -2.066419)
-      (xy -6.357927 -2.068638)
-      (xy -6.393536 -2.071574)
-      (xy -6.418296 -2.075329)
-      (xy -6.434886 -2.080004)
-      (xy -6.445985 -2.085701)
-      (xy -6.449661 -2.088428)
-      (xy -6.468217 -2.104843)
-      (xy -6.482843 -2.122948)
-      (xy -6.494004 -2.146278)
-      (xy -6.502167 -2.178368)
-      (xy -6.507796 -2.222755)
-      (xy -6.511358 -2.282974)
-      (xy -6.513319 -2.362561)
-      (xy -6.514144 -2.465051)
-      (xy -6.514301 -2.579055)
-      (xy -6.514301 -2.979444)
-      (xy -6.427939 -3.076124)
-      (xy -5.782972 -3.080276)
-      (xy -5.618994 -3.081282)
-      (xy -5.482022 -3.081791)
-      (xy -5.36946 -3.081482)
-      (xy -5.278713 -3.080034)
-      (xy -5.207183 -3.077127)
-      (xy -5.152275 -3.072442)
-      (xy -5.111391 -3.065656)
-      (xy -5.081936 -3.056451)
-      (xy -5.061313 -3.044505)
-      (xy -5.046926 -3.029498)
-      (xy -5.036178 -3.01111)
-      (xy -5.026473 -2.989021)
-      (xy -5.025547 -2.986805)
-      (xy -5.018033 -2.953432)
-      (xy -5.012004 -2.896279)
-      (xy -5.007456 -2.820482)
-      (xy -5.004381 -2.73118)
-      (xy -5.002772 -2.63351)
-      (xy -5.002623 -2.53261)
-      (xy -4.904204 -2.53261)
-      (xy -4.90399 -2.554961)
-      (xy -4.902852 -2.683441)
-      (xy -4.902255 -2.785788)
-      (xy -4.902382 -2.86547)
-      (xy -4.903412 -2.925952)
-      (xy -4.905526 -2.970705)
-      (xy -4.908904 -3.003195)
-      (xy -4.913727 -3.02689)
-      (xy -4.920175 -3.045258)
-      (xy -4.92843 -3.061767)
-      (xy -4.930581 -3.065625)
-      (xy -4.963958 -3.110307)
-      (xy -5.007155 -3.150925)
-      (xy -5.0163 -3.157534)
-      (xy -5.071119 -3.194539)
-      (xy -6.449854 -3.194539)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 322ee281-3523-4fac-b06d-2aef62c11904))
-  (fp_poly
-    (pts
-      (xy -5.554939 -10.793507)
-      (xy -5.700661 -10.792681)
-      (xy -5.783756 -10.792164)
-      (xy -6.462494 -10.787895)
-      (xy -6.510012 -10.754002)
-      (xy -6.552343 -10.717287)
-      (xy -6.589891 -10.674707)
-      (xy -6.591422 -10.672592)
-      (xy -6.600974 -10.65853)
-      (xy -6.608539 -10.64385)
-      (xy -6.614347 -10.625132)
-      (xy -6.618632 -10.598956)
-      (xy -6.621624 -10.561899)
-      (xy -6.623556 -10.510542)
-      (xy -6.624659 -10.441464)
-      (xy -6.625166 -10.351244)
-      (xy -6.625308 -10.23646)
-      (xy -6.625315 -10.17255)
-      (xy -6.625315 -9.720025)
-      (xy -6.585586 -9.659978)
-      (xy -6.535765 -9.605018)
-      (xy -6.481001 -9.568535)
-      (xy -6.464639 -9.561014)
-      (xy -6.447609 -9.55481)
-      (xy -6.427067 -9.549802)
-      (xy -6.40017 -9.545872)
-      (xy -6.364073 -9.542901)
-      (xy -6.315931 -9.54077)
-      (xy -6.252901 -9.53936)
-      (xy -6.172139 -9.538551)
-      (xy -6.070801 -9.538226)
-      (xy -5.946043 -9.538264)
-      (xy -5.79502 -9.538548)
-      (xy -5.765834 -9.538613)
-      (xy -5.628968 -9.539136)
-      (xy -5.50056 -9.540035)
-      (xy -5.383785 -9.541257)
-      (xy -5.281816 -9.542752)
-      (xy -5.197826 -9.544467)
-      (xy -5.134991 -9.546351)
-      (xy -5.096483 -9.548351)
-      (xy -5.085921 -9.549714)
-      (xy -5.012699 -9.586234)
-      (xy -4.952994 -9.64056)
-      (xy -4.931288 -9.672119)
-      (xy -4.922403 -9.688935)
-      (xy -4.915402 -9.706507)
-      (xy -4.9101 -9.72831)
-      (xy -4.906312 -9.75782)
-      (xy -4.903854 -9.798512)
-      (xy -4.902539 -9.853861)
-      (xy -4.902182 -9.927342)
-      (xy -4.902598 -10.02243)
-      (xy -4.903601 -10.1426)
-      (xy -4.903919 -10.176562)
-      (xy -5.004511 -10.176562)
-      (xy -5.004888 -10.048885)
-      (xy -5.006393 -9.947341)
-      (xy -5.009586 -9.868463)
-      (xy -5.015027 -9.808786)
-      (xy -5.023277 -9.764844)
-      (xy -5.034896 -9.733172)
-      (xy -5.050443 -9.710302)
-      (xy -5.070479 -9.69277)
-      (xy -5.084154 -9.683818)
-      (xy -5.096719 -9.677013)
-      (xy -5.111874 -9.671399)
-      (xy -5.132405 -9.666862)
-      (xy -5.161096 -9.663287)
-      (xy -5.200733 -9.660559)
-      (xy -5.254102 -9.658566)
-      (xy -5.323986 -9.657192)
-      (xy -5.413173 -9.656323)
-      (xy -5.524445 -9.655846)
-      (xy -5.66059 -9.655645)
-      (xy -5.771987 -9.655608)
-      (xy -6.413648 -9.655553)
-      (xy -6.463975 -9.705879)
-      (xy -6.514301 -9.756205)
-      (xy -6.514301 -10.158071)
-      (xy -6.514034 -10.288079)
-      (xy -6.512879 -10.391784)
-      (xy -6.510303 -10.472485)
-      (xy -6.505772 -10.533482)
-      (xy -6.498752 -10.578073)
-      (xy -6.488711 -10.609558)
-      (xy -6.475116 -10.631234)
-      (xy -6.457433 -10.646402)
-      (xy -6.43513 -10.65836)
-      (xy -6.433304 -10.659198)
-      (xy -6.413392 -10.663905)
-      (xy -6.375014 -10.667808)
-      (xy -6.316461 -10.670951)
-      (xy -6.236024 -10.673379)
-      (xy -6.131994 -10.675135)
-      (xy -6.002663 -10.676264)
-      (xy -5.846323 -10.676812)
-      (xy -5.754602 -10.676881)
-      (xy -5.595029 -10.676878)
-      (xy -5.462382 -10.676652)
-      (xy -5.353984 -10.675874)
-      (xy -5.267155 -10.674218)
-      (xy -5.19922 -10.671356)
-      (xy -5.1475 -10.666961)
-      (xy -5.109317 -10.660706)
-      (xy -5.081994 -10.652264)
-      (xy -5.062853 -10.641307)
-      (xy -5.049217 -10.627508)
-      (xy -5.038407 -10.610539)
-      (xy -5.027746 -10.590074)
-      (xy -5.026629 -10.587907)
-      (xy -5.019471 -10.568777)
-      (xy -5.013966 -10.540147)
-      (xy -5.009921 -10.49847)
-      (xy -5.007147 -10.440201)
-      (xy -5.005453 -10.361794)
-      (xy -5.004648 -10.259703)
-      (xy -5.004511 -10.176562)
-      (xy -4.903919 -10.176562)
-      (xy -4.90399 -10.184116)
-      (xy -4.905263 -10.312341)
-      (xy -4.906561 -10.414369)
-      (xy -4.908138 -10.493606)
-      (xy -4.910251 -10.553457)
-      (xy -4.913154 -10.597329)
-      (xy -4.917104 -10.628627)
-      (xy -4.922356 -10.650757)
-      (xy -4.929165 -10.667125)
-      (xy -4.937787 -10.681137)
-      (xy -4.941706 -10.686712)
-      (xy -4.976322 -10.722416)
-      (xy -5.023098 -10.755836)
-      (xy -5.040066 -10.764991)
-      (xy -5.056026 -10.77237)
-      (xy -5.07249 -10.778473)
-      (xy -5.092229 -10.783402)
-      (xy -5.118016 -10.787256)
-      (xy -5.152622 -10.790138)
-      (xy -5.198818 -10.792149)
-      (xy -5.259376 -10.79339)
-      (xy -5.337068 -10.793963)
-      (xy -5.434665 -10.793968)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c3fa97af-5933-4d5c-9a48-f3ebe76c58ee))
-  (fp_poly
-    (pts
-      (xy -6.227012 -5.73147)
-      (xy -6.295047 -5.730539)
-      (xy -6.347412 -5.728878)
-      (xy -6.386896 -5.726388)
-      (xy -6.416283 -5.722967)
-      (xy -6.438361 -5.718514)
-      (xy -6.455917 -5.712929)
-      (xy -6.471738 -5.706111)
-      (xy -6.477649 -5.703284)
-      (xy -6.527633 -5.671241)
-      (xy -6.573429 -5.629534)
-      (xy -6.583421 -5.617599)
-      (xy -6.625315 -5.562837)
-      (xy -6.625315 -5.103979)
-      (xy -6.625266 -4.975394)
-      (xy -6.62497 -4.87302)
-      (xy -6.624198 -4.793465)
-      (xy -6.622724 -4.733337)
-      (xy -6.62032 -4.689244)
-      (xy -6.616761 -4.657793)
-      (xy -6.611817 -4.635592)
-      (xy -6.605263 -4.619249)
-      (xy -6.596872 -4.605372)
-      (xy -6.591422 -4.597604)
-      (xy -6.554706 -4.555272)
-      (xy -6.512126 -4.517724)
-      (xy -6.510012 -4.516194)
-      (xy -6.462494 -4.482301)
-      (xy -5.781609 -4.478307)
-      (xy -5.621898 -4.477402)
-      (xy -5.489032 -4.476798)
-      (xy -5.380251 -4.476597)
-      (xy -5.292796 -4.4769)
-      (xy -5.223909 -4.47781)
-      (xy -5.170831 -4.479429)
-      (xy -5.130803 -4.481859)
-      (xy -5.101066 -4.485202)
-      (xy -5.078861 -4.48956)
-      (xy -5.061429 -4.495035)
-      (xy -5.046011 -4.50173)
-      (xy -5.03767 -4.505828)
-      (xy -4.990941 -4.535791)
-      (xy -4.950648 -4.57244)
-      (xy -4.941458 -4.583832)
-      (xy -4.932125 -4.59779)
-      (xy -4.924691 -4.612866)
-      (xy -4.918901 -4.632466)
-      (xy -4.914501 -4.659992)
-      (xy -4.911238 -4.69885)
-      (xy -4.908858 -4.752442)
-      (xy -4.907106 -4.824174)
-      (xy -4.905728 -4.917448)
-      (xy -4.904472 -5.035671)
-      (xy -4.904204 -5.063729)
-      (xy -5.002623 -5.063729)
-      (xy -5.003927 -4.964736)
-      (xy -5.006677 -4.872788)
-      (xy -5.010868 -4.793024)
-      (xy -5.016492 -4.73058)
-      (xy -5.023542 -4.690594)
-      (xy -5.026629 -4.682289)
-      (xy -5.037417 -4.66147)
-      (xy -5.048095 -4.644179)
-      (xy -5.061343 -4.630089)
-      (xy -5.079837 -4.618873)
-      (xy -5.106256 -4.610202)
-      (xy -5.143276 -4.603751)
-      (xy -5.193576 -4.599191)
-      (xy -5.259833 -4.596196)
-      (xy -5.344725 -4.594438)
-      (xy -5.45093 -4.59359)
-      (xy -5.581125 -4.593324)
-      (xy -5.737989 -4.593314)
-      (xy -5.754602 -4.593315)
-      (xy -5.938967 -4.593697)
-      (xy -6.093877 -4.594846)
-      (xy -6.219472 -4.596766)
-      (xy -6.31589 -4.599459)
-      (xy -6.38327 -4.602929)
-      (xy -6.421752 -4.607179)
-      (xy -6.429748 -4.609378)
-      (xy -6.453415 -4.621636)
-      (xy -6.472212 -4.636662)
-      (xy -6.486696 -4.657772)
-      (xy -6.497426 -4.68828)
-      (xy -6.50496 -4.731501)
-      (xy -6.509856 -4.790748)
-      (xy -6.512672 -4.869337)
-      (xy -6.513967 -4.970581)
-      (xy -6.514299 -5.097796)
-      (xy -6.514301 -5.111444)
-      (xy -6.514301 -5.513991)
-      (xy -6.463975 -5.564317)
-      (xy -6.413648 -5.614643)
-      (xy -5.774953 -5.614643)
-      (xy -5.611891 -5.61459)
-      (xy -5.475823 -5.614205)
-      (xy -5.364139 -5.613153)
-      (xy -5.274229 -5.611095)
-      (xy -5.203482 -5.607695)
-      (xy -5.149288 -5.602617)
-      (xy -5.109038 -5.595523)
-      (xy -5.080122 -5.586077)
-      (xy -5.059929 -5.573941)
-      (xy -5.04585 -5.55878)
-      (xy -5.035274 -5.540255)
-      (xy -5.025592 -5.51803)
-      (xy -5.025547 -5.517924)
-      (xy -5.018033 -5.484551)
-      (xy -5.012004 -5.427398)
-      (xy -5.007456 -5.351601)
-      (xy -5.004381 -5.262299)
-      (xy -5.002772 -5.164629)
-      (xy -5.002623 -5.063729)
-      (xy -4.904204 -5.063729)
-      (xy -4.90399 -5.08608)
-      (xy -4.902832 -5.214267)
-      (xy -4.902183 -5.316341)
-      (xy -4.90224 -5.395794)
-      (xy -4.903198 -5.456113)
-      (xy -4.905255 -5.500788)
-      (xy -4.908608 -5.53331)
-      (xy -4.913454 -5.557169)
-      (xy -4.919988 -5.575853)
-      (xy -4.928408 -5.592852)
-      (xy -4.93303 -5.601176)
-      (xy -4.966504 -5.646658)
-      (xy -5.008148 -5.685782)
-      (xy -5.018749 -5.693085)
-      (xy -5.031731 -5.700773)
-      (xy -5.04555 -5.707165)
-      (xy -5.062945 -5.712401)
-      (xy -5.086656 -5.71662)
-      (xy -5.119422 -5.719962)
-      (xy -5.163982 -5.722566)
-      (xy -5.223075 -5.724572)
-      (xy -5.299443 -5.726118)
-      (xy -5.395823 -5.727346)
-      (xy -5.514956 -5.728393)
-      (xy -5.65958 -5.7294)
-      (xy -5.742445 -5.729932)
-      (xy -5.901024 -5.730905)
-      (xy -6.032787 -5.731553)
-      (xy -6.140521 -5.731775)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6dac0c92-0bf1-4539-a4e7-29a649ae4dc4))
-  (fp_poly
-    (pts
-      (xy -5.805203 6.939209)
-      (xy -5.874953 6.940129)
-      (xy -5.928792 6.941745)
-      (xy -5.969457 6.944153)
-      (xy -5.999688 6.947446)
-      (xy -6.022221 6.951718)
-      (xy -6.039797 6.957064)
-      (xy -6.055152 6.963577)
-      (xy -6.060984 6.966383)
-      (xy -6.108927 6.998686)
-      (xy -6.151334 7.04134)
-      (xy -6.159056 7.051923)
-      (xy -6.196061 7.107559)
-      (xy -6.196061 8.012642)
-      (xy -6.15931 8.066276)
-      (xy -6.121901 8.108917)
-      (xy -6.076796 8.145275)
-      (xy -6.068484 8.150302)
-      (xy -6.054933 8.157408)
-      (xy -6.040031 8.163309)
-      (xy -6.021065 8.168116)
-      (xy -5.99532 8.171938)
-      (xy -5.960082 8.174886)
-      (xy -5.912636 8.177069)
-      (xy -5.850269 8.178599)
-      (xy -5.770267 8.179586)
-      (xy -5.669915 8.180138)
-      (xy -5.546499 8.180368)
-      (xy -5.397305 8.180384)
-      (xy -5.328136 8.180355)
-      (xy -5.167715 8.18024)
-      (xy -5.034184 8.179994)
-      (xy -4.924833 8.1795)
-      (xy -4.836947 8.178642)
-      (xy -4.767816 8.177304)
-      (xy -4.714725 8.175371)
-      (xy -4.674963 8.172727)
-      (xy -4.645817 8.169256)
-      (xy -4.624575 8.164842)
-      (xy -4.608524 8.15937)
-      (xy -4.594951 8.152723)
-      (xy -4.587964 8.148759)
-      (xy -4.546233 8.115445)
-      (xy -4.508002 8.070534)
-      (xy -4.499153 8.056588)
-      (xy -4.489154 8.038442)
-      (xy -4.481273 8.020494)
-      (xy -4.475259 7.99915)
-      (xy -4.470858 7.970816)
-      (xy -4.46782 7.931899)
-      (xy -4.465892 7.878805)
-      (xy -4.464821 7.807939)
-      (xy -4.464356 7.715708)
-      (xy -4.464245 7.598519)
-      (xy -4.464245 7.589609)
-      (xy -4.573188 7.589609)
-      (xy -4.574078 7.689802)
-      (xy -4.576484 7.783211)
-      (xy -4.580423 7.864644)
-      (xy -4.585915 7.928906)
-      (xy -4.592979 7.970805)
-      (xy -4.595544 7.978568)
-      (xy -4.605674 8.001342)
-      (xy -4.6171 8.020275)
-      (xy -4.632473 8.035725)
-      (xy -4.654447 8.048048)
-      (xy -4.685675 8.057599)
-      (xy -4.72881 8.064736)
-      (xy -4.786504 8.069813)
-      (xy -4.861411 8.073187)
-      (xy -4.956183 8.075214)
-      (xy -5.073474 8.076251)
-      (xy -5.215935 8.076653)
-      (xy -5.326927 8.076744)
-      (xy -5.484159 8.076657)
-      (xy -5.614426 8.076152)
-      (xy -5.720366 8.075145)
-      (xy -5.804614 8.073555)
-      (xy -5.869809 8.071298)
-      (xy -5.918587 8.068293)
-      (xy -5.953585 8.064457)
-      (xy -5.977439 8.059706)
-      (xy -5.988327 8.056045)
-      (xy -6.015575 8.043247)
-      (xy -6.037172 8.027928)
-      (xy -6.053773 8.006729)
-      (xy -6.066031 7.976292)
-      (xy -6.074599 7.933258)
-      (xy -6.080131 7.874268)
-      (xy -6.08328 7.795964)
-      (xy -6.084701 7.694988)
-      (xy -6.085046 7.567981)
-      (xy -6.085047 7.559016)
-      (xy -6.084793 7.431546)
-      (xy -6.083597 7.330254)
-      (xy -6.080806 7.251717)
-      (xy -6.075768 7.192512)
-      (xy -6.067831 7.149214)
-      (xy -6.056343 7.1184)
-      (xy -6.04065 7.096647)
-      (xy -6.020101 7.08053)
-      (xy -5.994044 7.066626)
-      (xy -5.99095 7.06515)
-      (xy -5.975238 7.059084)
-      (xy -5.95421 7.054107)
-      (xy -5.925032 7.050112)
-      (xy -5.884867 7.046998)
-      (xy -5.830878 7.044659)
-      (xy -5.760231 7.042992)
-      (xy -5.670089 7.041894)
-      (xy -5.557616 7.041259)
-      (xy -5.419975 7.040986)
-      (xy -5.330152 7.040951)
-      (xy -5.169887 7.041034)
-      (xy -5.036546 7.041517)
-      (xy -4.92745 7.042751)
-      (xy -4.839919 7.045088)
-      (xy -4.771273 7.048878)
-      (xy -4.718832 7.054473)
-      (xy -4.679917 7.062225)
-      (xy -4.651848 7.072484)
-      (xy -4.631946 7.085602)
-      (xy -4.61753 7.10193)
-      (xy -4.605922 7.121819)
-      (xy -4.598603 7.136843)
-      (xy -4.5908 7.168671)
-      (xy -4.584399 7.224877)
-      (xy -4.579418 7.300267)
-      (xy -4.575876 7.389648)
-      (xy -4.573793 7.487827)
-      (xy -4.573188 7.589609)
-      (xy -4.464245 7.589609)
-      (xy -4.464243 7.559016)
-      (xy -4.464371 7.42537)
-      (xy -4.465185 7.317868)
-      (xy -4.467325 7.233053)
-      (xy -4.471432 7.167464)
-      (xy -4.478146 7.117644)
-      (xy -4.488108 7.080133)
-      (xy -4.50196 7.051473)
-      (xy -4.520342 7.028205)
-      (xy -4.543895 7.006869)
-      (xy -4.570374 6.986209)
-      (xy -4.62473 6.944739)
-      (xy -5.312323 6.940609)
-      (xy -5.473101 6.939685)
-      (xy -5.607016 6.939081)
-      (xy -5.716803 6.938891)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 10ecde5a-92ae-47a6-8dc6-d97767da1efe))
-  (fp_poly
-    (pts
-      (xy -1.156541 2.409908)
-      (xy -1.290423 2.410195)
-      (xy -1.405501 2.410687)
-      (xy -1.503317 2.411403)
-      (xy -1.585414 2.412361)
-      (xy -1.653334 2.41358)
-      (xy -1.70862 2.415079)
-      (xy -1.752815 2.416877)
-      (xy -1.787461 2.418991)
-      (xy -1.814102 2.42144)
-      (xy -1.834279 2.424244)
-      (xy -1.849536 2.42742)
-      (xy -1.861416 2.430987)
-      (xy -1.87146 2.434965)
-      (xy -1.872899 2.435596)
-      (xy -1.922889 2.466187)
-      (xy -1.969084 2.507727)
-      (xy -1.979135 2.51974)
-      (xy -2.021935 2.575824)
-      (xy -2.026044 3.021062)
-      (xy -2.027167 3.156554)
-      (xy -2.027363 3.265888)
-      (xy -2.026019 3.352508)
-      (xy -2.022522 3.419859)
-      (xy -2.01626 3.471384)
-      (xy -2.006619 3.510529)
-      (xy -1.992986 3.540737)
-      (xy -1.974749 3.565452)
-      (xy -1.951294 3.588119)
-      (xy -1.922008 3.612182)
-      (xy -1.920651 3.613267)
-      (xy -1.863772 3.658725)
-      (xy 0.085002 3.662503)
-      (xy 2.033776 3.66628)
-      (xy 2.096828 3.634981)
-      (xy 2.141782 3.607221)
-      (xy 2.178936 3.575126)
-      (xy 2.187669 3.564595)
-      (xy 2.198504 3.547711)
-      (xy -0.356725 3.547711)
-      (xy -1.819833 3.547711)
-      (xy -1.865377 3.502167)
-      (xy -1.910921 3.456622)
-      (xy -1.91045 3.039608)
-      (xy -1.910239 2.914427)
-      (xy -1.909572 2.815353)
-      (xy -1.907924 2.738888)
-      (xy -1.904771 2.681536)
-      (xy -1.899589 2.639799)
-      (xy -1.891855 2.610181)
-      (xy -1.881044 2.589185)
-      (xy -1.866631 2.573314)
-      (xy -1.848094 2.55907)
-      (xy -1.837319 2.551606)
-      (xy -1.826836 2.545807)
-      (xy -1.811985 2.540963)
-      (xy -1.790219 2.53699)
-      (xy -1.75899 2.533802)
-      (xy -1.71575 2.531316)
-      (xy -1.657951 2.529447)
-      (xy -1.583045 2.528109)
-      (xy -1.488484 2.527219)
-      (xy -1.37172 2.526691)
-      (xy -1.230206 2.52644)
-      (xy -1.078723 2.526382)
-      (xy -0.356725 2.526382)
-      (xy -0.356725 3.547711)
-      (xy 2.198504 3.547711)
-      (xy 2.205684 3.536522)
-      (xy 2.219887 3.506257)
-      (xy 2.230661 3.470133)
-      (xy 2.238388 3.42448)
-      (xy 2.240637 3.39834)
-      (xy 1.819149 3.39834)
-      (xy 1.719236 3.40389)
-      (xy 1.645554 3.406072)
-      (xy 1.571885 3.404983)
-      (xy 1.504992 3.401081)
-      (xy 1.451638 3.394821)
-      (xy 1.418584 3.386659)
-      (xy 1.412838 3.383233)
-      (xy 1.385844 3.370806)
-      (xy 1.378476 3.370088)
-      (xy 1.351641 3.360381)
-      (xy 1.337295 3.349207)
-      (xy 1.310879 3.328553)
-      (xy 1.298283 3.322282)
-      (xy 1.287142 3.304222)
-      (xy 1.278608 3.261143)
-      (xy 1.274433 3.213647)
-      (xy 1.272681 3.155497)
-      (xy 1.276392 3.117827)
-      (xy 1.287084 3.091779)
-      (xy 1.297737 3.077752)
-      (xy 1.323756 3.053799)
-      (xy 1.343525 3.044447)
-      (xy 1.358297 3.034352)
-      (xy 1.358024 3.012981)
-      (xy 1.344056 2.99371)
-      (xy 1.338088 2.990593)
-      (xy 1.318416 2.971956)
-      (xy 1.315886 2.961454)
-      (xy 1.307364 2.942794)
-      (xy 1.301084 2.940834)
-      (xy 1.291348 2.927811)
-      (xy 1.286428 2.895738)
-      (xy 1.286282 2.888383)
-      (xy 1.297004 2.84324)
-      (xy 1.300481 2.837221)
-      (xy 1.182669 2.837221)
-      (xy 0.975443 2.837221)
-      (xy 0.975443 3.399692)
-      (xy 0.812622 3.399692)
-      (xy 0.501783 3.399692)
-      (xy 0.353764 3.399692)
-      (xy 0.353764 2.943759)
-      (xy 0.309359 2.98524)
-      (xy 0.281497 3.013886)
-      (xy 0.266053 3.03485)
-      (xy 0.264953 3.038475)
-      (xy 0.255769 3.05626)
-      (xy 0.233306 3.084224)
-      (xy 0.22981 3.088043)
-      (xy 0.195093 3.12915)
-      (xy 0.158759 3.178101)
-      (xy 0.125593 3.22765)
-      (xy 0.100379 3.270554)
-      (xy 0.0879 3.299568)
-      (xy 0.087331 3.303793)
-      (xy 0.075353 3.328628)
-      (xy 0.065128 3.335132)
-      (xy 0.046407 3.355318)
-      (xy 0.042925 3.371672)
-      (xy 0.038511 3.388562)
-      (xy 0.02052 3.396978)
-      (xy -0.01817 3.399618)
-      (xy -0.031084 3.399692)
-      (xy -0.105093 3.399692)
-      (xy -0.105093 2.689203)
-      (xy 0.042925 2.689203)
-      (xy 0.042925 3.124739)
-      (xy 0.086729 3.073492)
-      (xy 0.113365 3.038827)
-      (xy 0.129247 3.011415)
-      (xy 0.131135 3.004478)
-      (xy 0.14296 2.981848)
-      (xy 0.151785 2.974874)
-      (xy 0.171029 2.955947)
-      (xy 0.197309 2.921205)
-      (xy 0.211164 2.900153)
-      (xy 0.243152 2.855656)
-      (xy 0.286511 2.803606)
-      (xy 0.324137 2.763236)
-      (xy 0.367873 2.722094)
-      (xy 0.401183 2.69932)
-      (xy 0.432131 2.690162)
-      (xy 0.449782 2.689203)
-      (xy 0.501783 2.689203)
-      (xy 0.501783 3.399692)
-      (xy 0.812622 3.399692)
-      (xy 0.812622 2.837221)
-      (xy 0.605396 2.837221)
-      (xy 0.605396 2.689203)
-      (xy 1.182669 2.689203)
-      (xy 1.182669 2.837221)
-      (xy 1.300481 2.837221)
-      (xy 1.324536 2.795578)
-      (xy 1.361928 2.75364)
-      (xy 1.402227 2.725669)
-      (xy 1.429277 2.718806)
-      (xy 1.455936 2.713424)
-      (xy 1.463904 2.704005)
-      (xy 1.477977 2.697128)
-      (xy 1.517351 2.692157)
-      (xy 1.577763 2.689517)
-      (xy 1.611923 2.689203)
-      (xy 1.680685 2.69061)
-      (xy 1.730399 2.694547)
-      (xy 1.7568 2.700589)
-      (xy 1.759942 2.704005)
-      (xy 1.772339 2.716031)
-      (xy 1.789545 2.718806)
-      (xy 1.799014 2.719857)
-      (xy 1.806214 2.725382)
-      (xy 1.811456 2.738945)
-      (xy 1.815049 2.764108)
-      (xy 1.817305 2.804433)
-      (xy 1.818533 2.863484)
-      (xy 1.819044 2.944821)
-      (xy 1.819149 3.052009)
-      (xy 1.819149 3.39834)
-      (xy 2.240637 3.39834)
-      (xy 2.243451 3.365631)
-      (xy 2.246232 3.289918)
-      (xy 2.247113 3.19367)
-      (xy 2.246478 3.073221)
-      (xy 2.245767 3.007443)
-      (xy 2.244249 2.887934)
-      (xy 2.242669 2.794225)
-      (xy 2.240705 2.722514)
-      (xy 2.238035 2.668998)
-      (xy 2.234336 2.629875)
-      (xy 2.229288 2.601341)
-      (xy 2.222569 2.579595)
-      (xy 2.213855 2.560833)
-      (xy 2.206909 2.548331)
-      (xy 2.172462 2.501565)
-      (xy 2.129627 2.459889)
-      (xy 2.119186 2.452119)
-      (xy 2.065556 2.415368)
-      (xy 0.128046 2.411452)
-      (xy -0.151062 2.410899)
-      (xy -0.402108 2.410439)
-      (xy -0.626637 2.410092)
-      (xy -0.82619 2.409875)
-      (xy -1.002311 2.409807)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 26d9d795-659a-4c3b-9475-75c142dc4af3))
-  (fp_poly
-    (pts
-      (xy 4.139606 9.495404)
-      (xy 4.095303 9.529355)
-      (xy 4.056541 9.569259)
-      (xy 4.050795 9.576814)
-      (xy 4.041238 9.591063)
-      (xy 4.033649 9.606309)
-      (xy 4.027761 9.626014)
-      (xy 4.023305 9.653638)
-      (xy 4.020014 9.692642)
-      (xy 4.017619 9.746487)
-      (xy 4.015853 9.818634)
-      (xy 4.014448 9.912545)
-      (xy 4.013136 10.031679)
-      (xy 4.012769 10.067932)
-      (xy 4.01155 10.194201)
-      (xy 4.010852 10.294453)
-      (xy 4.010891 10.372277)
-      (xy 4.01188 10.431259)
-      (xy 4.014032 10.474985)
-      (xy 4.017561 10.507041)
-      (xy 4.022682 10.531015)
-      (xy 4.029607 10.550493)
-      (xy 4.038551 10.569061)
-      (xy 4.043154 10.577816)
-      (xy 4.090737 10.641415)
-      (xy 4.14245 10.677729)
-      (xy 4.206905 10.711813)
-      (xy 6.610297 10.711813)
-      (xy 6.674752 10.677729)
-      (xy 6.738628 10.629101)
-      (xy 6.773293 10.579188)
-      (xy 6.783124 10.559718)
-      (xy 6.790857 10.540338)
-      (xy 6.796743 10.51739)
-      (xy 6.801035 10.487215)
-      (xy 6.803983 10.446155)
-      (xy 6.805839 10.390553)
-      (xy 6.806856 10.31675)
-      (xy 6.807285 10.221088)
-      (xy 6.807368 10.111903)
-      (xy 6.481736 10.111903)
-      (xy 6.479589 10.162312)
-      (xy 6.473985 10.20006)
-      (xy 6.466935 10.215951)
-      (xy 6.45535 10.236417)
-      (xy 6.452133 10.260173)
-      (xy 6.440775 10.294625)
-      (xy 6.411725 10.336436)
-      (xy 6.372518 10.377944)
-      (xy 6.33069 10.411485)
-      (xy 6.293777 10.429397)
-      (xy 6.28456 10.430578)
-      (xy 6.252522 10.43579)
-      (xy 6.237506 10.44538)
-      (xy 6.219451 10.452139)
-      (xy 6.179303 10.457279)
-      (xy 6.124558 10.459971)
-      (xy 6.103415 10.460182)
-      (xy 5.741643 10.460182)
-      (xy 5.593625 10.460182)
-      (xy 5.593625 9.980715)
-      (xy 5.541818 10.030928)
-      (xy 5.511463 10.06362)
-      (xy 5.492818 10.090005)
-      (xy 5.490011 10.098278)
-      (xy 5.480697 10.120035)
-      (xy 5.458038 10.149875)
-      (xy 5.455683 10.152457)
-      (xy 5.424563 10.194148)
-      (xy 5.402234 10.235657)
-      (xy 5.38111 10.277547)
-      (xy 5.358853 10.310545)
-      (xy 5.328903 10.346166)
-      (xy 5.310188 10.368542)
-      (xy 5.286794 10.404289)
-      (xy 5.275887 10.428996)
-      (xy 5.262427 10.450227)
-      (xy 5.234276 10.459079)
-      (xy 5.207779 10.460182)
-      (xy 5.149569 10.460182)
-      (xy 5.149569 10.092204)
-      (xy 4.957144 10.092204)
-      (xy 4.956949 10.199889)
-      (xy 4.956172 10.281781)
-      (xy 4.95453 10.341687)
-      (xy 4.95174 10.383416)
-      (xy 4.947517 10.410777)
-      (xy 4.941577 10.427577)
-      (xy 4.933636 10.437625)
-      (xy 4.931241 10.439577)
-      (xy 4.905249 10.448816)
-      (xy 4.860605 10.455386)
-      (xy 4.805757 10.459111)
-      (xy 4.749149 10.459815)
-      (xy 4.69923 10.45732)
-      (xy 4.664444 10.45145)
-      (xy 4.653706 10.44538)
-      (xy 4.634036 10.435396)
-      (xy 4.598119 10.430642)
-      (xy 4.593299 10.430578)
-      (xy 4.549161 10.418316)
-      (xy 4.499095 10.385994)
-      (xy 4.449839 10.340309)
-      (xy 4.408134 10.287957)
-      (xy 4.380717 10.235634)
-      (xy 4.374762 10.213433)
-      (xy 4.363464 10.099952)
-      (xy 4.371229 10.005922)
-      (xy 4.398839 9.927509)
-      (xy 4.446609 9.861372)
-      (xy 4.502174 9.809589)
-      (xy 4.554375 9.779452)
-      (xy 4.613329 9.766249)
-      (xy 4.65467 9.764494)
-      (xy 4.694058 9.761514)
-      (xy 4.717483 9.753984)
-      (xy 4.720315 9.749692)
-      (xy 4.733446 9.740423)
-      (xy 4.76625 9.735268)
-      (xy 4.779522 9.73489)
-      (xy 4.816598 9.738173)
-      (xy 4.83722 9.746374)
-      (xy 4.838729 9.749692)
-      (xy 4.851861 9.758961)
-      (xy 4.884665 9.764117)
-      (xy 4.897937 9.764494)
-      (xy 4.957144 9.764494)
-      (xy 4.957144 10.092204)
-      (xy 5.149569 10.092204)
-      (xy 5.149569 9.764494)
-      (xy 5.282785 9.764494)
-      (xy 5.283227 9.96802)
-      (xy 5.283669 10.171545)
-      (xy 5.341557 10.104937)
-      (xy 5.374682 10.062939)
-      (xy 5.399364 10.02452)
-      (xy 5.408063 10.004798)
-      (xy 5.425389 9.965539)
-      (xy 5.451911 9.931834)
-      (xy 5.479318 9.913534)
-      (xy 5.4859 9.912513)
-      (xy 5.503039 9.900747)
-      (xy 5.504813 9.89217)
-      (xy 5.514203 9.869997)
-      (xy 5.538061 9.83663)
-      (xy 5.55397 9.818161)
-      (xy 5.588638 9.784612)
-      (xy 5.620365 9.768873)
-      (xy 5.663259 9.764553)
-      (xy 5.672385 9.764494)
-      (xy 5.741643 9.764494)
-      (xy 5.741643 10.460182)
-      (xy 6.103415 10.460182)
-      (xy 6.04245 10.458534)
-      (xy 5.999316 10.454006)
-      (xy 5.979267 10.447221)
-      (xy 5.978473 10.44538)
-      (xy 5.965806 10.434253)
-      (xy 5.941468 10.430578)
-      (xy 5.904464 10.430578)
-      (xy 5.904464 10.090135)
-      (xy 6.052482 10.090135)
-      (xy 6.052482 10.341767)
-      (xy 6.119091 10.341767)
-      (xy 6.158814 10.338827)
-      (xy 6.182643 10.331388)
-      (xy 6.185699 10.326965)
-      (xy 6.198048 10.314792)
-      (xy 6.214229 10.312163)
-      (xy 6.247563 10.298962)
-      (xy 6.277802 10.265398)
-      (xy 6.298576 10.220531)
-      (xy 6.304114 10.184351)
-      (xy 6.30797 10.15091)
-      (xy 6.317404 10.134801)
-      (xy 6.318916 10.134541)
-      (xy 6.329101 10.122188)
-      (xy 6.333328 10.093816)
-      (xy 6.331333 10.062459)
-      (xy 6.322855 10.041149)
-      (xy 6.320828 10.03951)
-      (xy 6.309099 10.020625)
-      (xy 6.29889 9.986302)
-      (xy 6.298823 9.985971)
-      (xy 6.287346 9.945633)
-      (xy 6.268508 9.918346)
-      (xy 6.237094 9.90167)
-      (xy 6.187885 9.893166)
-      (xy 6.115666 9.890394)
-      (xy 6.09431 9.89031)
-      (xy 5.949068 9.89031)
-      (xy 5.928289 9.838503)
-      (xy 5.917748 9.800887)
-      (xy 5.926121 9.778811)
-      (xy 5.95718 9.768268)
-      (xy 5.996975 9.765534)
-      (xy 6.026535 9.760127)
-      (xy 6.03768 9.749692)
-      (xy 6.050831 9.741398)
-      (xy 6.084079 9.736576)
-      (xy 6.128115 9.735269)
-      (xy 6.173632 9.737521)
-      (xy 6.211321 9.743377)
-      (xy 6.226605 9.748798)
-      (xy 6.261385 9.762749)
-      (xy 6.290694 9.770701)
-      (xy 6.343202 9.795635)
-      (xy 6.391685 9.844231)
-      (xy 6.432822 9.910556)
-      (xy 6.463291 9.988678)
-      (xy 6.479769 10.072663)
-      (xy 6.481736 10.111903)
-      (xy 6.807368 10.111903)
-      (xy 6.807377 10.099909)
-      (xy 6.807377 10.083876)
-      (xy 6.807215 9.949651)
-      (xy 6.806258 9.841567)
-      (xy 6.803803 9.756161)
-      (xy 6.799147 9.68997)
-      (xy 6.791586 9.639532)
-      (xy 6.780416 9.601383)
-      (xy 6.764934 9.572062)
-      (xy 6.744437 9.548105)
-      (xy 6.71822 9.526049)
-      (xy 6.689857 9.505461)
-      (xy 6.627205 9.461056)
-      (xy 4.194848 9.461056)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f387e312-68a4-4324-b185-de8bf6963734))
-  (fp_poly
-    (pts
-      (xy -4.569586 4.394866)
-      (xy -5.79641 4.398818)
-      (xy -5.844559 4.434937)
-      (xy -5.881909 4.471989)
-      (xy -5.915638 4.519788)
-      (xy -5.922897 4.533421)
-      (xy -5.931513 4.552617)
-      (xy -5.938263 4.572891)
-      (xy -5.94333 4.597833)
-      (xy -5.946898 4.631035)
-      (xy -5.94915 4.676085)
-      (xy -5.950271 4.736574)
-      (xy -5.950444 4.816092)
-      (xy -5.949853 4.918229)
-      (xy -5.948758 5.038751)
-      (xy -5.944429 5.481715)
-      (xy -5.904559 5.533959)
-      (xy -5.891521 5.55162)
-      (xy -5.879816 5.567094)
-      (xy -5.867508 5.580526)
-      (xy -5.852663 5.592057)
-      (xy -5.833346 5.601833)
-      (xy -5.807623 5.609996)
-      (xy -5.77356 5.61669)
-      (xy -5.729221 5.622059)
-      (xy -5.672672 5.626246)
-      (xy -5.601978 5.629395)
-      (xy -5.515204 5.63165)
-      (xy -5.410417 5.633154)
-      (xy -5.285681 5.634051)
-      (xy -5.139061 5.634484)
-      (xy -4.968624 5.634596)
-      (xy -4.772434 5.634533)
-      (xy -4.550817 5.634437)
-      (xy -4.331347 5.634333)
-      (xy -4.139541 5.634126)
-      (xy -3.973463 5.633778)
-      (xy -3.831172 5.633251)
-      (xy -3.710731 5.632509)
-      (xy -3.6102 5.631512)
-      (xy -3.527641 5.630223)
-      (xy -3.461116 5.628605)
-      (xy -3.408686 5.626619)
-      (xy -3.368412 5.624229)
-      (xy -3.338357 5.621395)
-      (xy -3.31658 5.618081)
-      (xy -3.301144 5.614248)
-      (xy -3.290153 5.609881)
-      (xy -3.248875 5.581789)
-      (xy -3.208771 5.542845)
-      (xy -3.201342 5.533691)
-      (xy -3.161678 5.48172)
-      (xy -3.159994 5.316716)
-      (xy -3.919987 5.316716)
-      (xy -3.925842 5.340449)
-      (xy -3.946679 5.355403)
-      (xy -3.986572 5.363586)
-      (xy -4.049593 5.367007)
-      (xy -4.098291 5.3676)
-      (xy -4.16703 5.367607)
-      (xy -4.21334 5.365745)
-      (xy -4.244391 5.360392)
-      (xy -4.267357 5.349925)
-      (xy -4.289409 5.33272)
-      (xy -4.301817 5.321556)
-      (xy -4.332691 5.287968)
-      (xy -4.351031 5.257407)
-      (xy -4.353229 5.247547)
-      (xy -4.359908 5.224817)
-      (xy -4.36803 5.220322)
-      (xy -4.37912 5.207525)
-      (xy -4.382512 5.174831)
-      (xy -4.378729 5.130781)
-      (xy -4.368292 5.083918)
-      (xy -4.357968 5.055497)
-      (xy -4.318921 5.001365)
-      (xy -4.261708 4.965733)
-      (xy -4.199272 4.953888)
-      (xy -4.170763 4.948997)
-      (xy -4.160804 4.939086)
-      (xy -4.148407 4.92706)
-      (xy -4.131201 4.924284)
-      (xy -4.112701 4.919926)
-      (xy -4.103953 4.901829)
-      (xy -4.101608 4.862461)
-      (xy -4.101597 4.857676)
-      (xy -4.101597 4.791068)
-      (xy -4.353229 4.791068)
-      (xy -4.353229 4.693982)
-      (xy -4.471644 4.693982)
-      (xy -4.479379 4.718338)
-      (xy -4.48445 4.723226)
-      (xy -4.495291 4.741959)
-      (xy -4.504676 4.77712)
-      (xy -4.505427 4.781484)
-      (xy -4.517267 4.826813)
-      (xy -4.537019 4.879384)
-      (xy -4.544426 4.895637)
-      (xy -4.56288 4.938638)
-      (xy -4.573893 4.973579)
-      (xy -4.575257 4.983443)
-      (xy -4.583799 5.013774)
-      (xy -4.596989 5.03617)
-      (xy -4.61449 5.069355)
-      (xy -4.619191 5.090805)
-      (xy -4.626585 5.112786)
-      (xy -4.634464 5.116709)
-      (xy -4.645591 5.129376)
-      (xy -4.649266 5.153713)
-      (xy -4.653933 5.181537)
-      (xy -4.662892 5.190718)
-      (xy -4.675218 5.203481)
-      (xy -4.686083 5.234284)
-      (xy -4.686303 5.235272)
-      (xy -4.70059 5.282201)
-      (xy -4.718167 5.324084)
-      (xy -4.735085 5.351426)
-      (xy -4.756788 5.364259)
-      (xy -4.794045 5.367726)
-      (xy -4.80947 5.367714)
-      (xy -4.854042 5.364916)
-      (xy -4.881558 5.353283)
-      (xy -4.904468 5.3264)
-      (xy -4.911999 5.314881)
-      (xy -4.933043 5.277099)
-      (xy -4.944563 5.247094)
-      (xy -4.945303 5.241498)
-      (xy -4.95313 5.222461)
-      (xy -4.959198 5.220322)
-      (xy -4.969447 5.207143)
-      (xy -4.979423 5.173786)
-      (xy -4.983082 5.153713)
-      (xy -4.991623 5.114063)
-      (xy -5.001768 5.090217)
-      (xy -5.006191 5.087105)
-      (xy -5.017553 5.074849)
-      (xy -5.019783 5.061202)
-      (xy -5.028795 5.029146)
-      (xy -5.041986 5.006566)
-      (xy -5.059319 4.972898)
-      (xy -5.063718 4.950858)
-      (xy -5.070497 4.914085)
-      (xy -5.0769 4.89818)
-      (xy -5.1029 4.844263)
-      (xy -5.127847 4.787203)
-      (xy -5.147507 4.737123)
-      (xy -5.157278 4.705957)
-      (xy -5.159237 4.686467)
-      (xy -5.149568 4.67659)
-      (xy -5.121589 4.673114)
-      (xy -5.088236 4.672768)
-      (xy -5.041906 4.674556)
-      (xy -5.015561 4.682421)
-      (xy -4.999654 4.700386)
-      (xy -4.993409 4.712724)
-      (xy -4.979888 4.747984)
-      (xy -4.974907 4.771816)
-      (xy -4.966698 4.789551)
-      (xy -4.961494 4.791068)
-      (xy -4.952202 4.804368)
-      (xy -4.942681 4.838544)
-      (xy -4.937503 4.868777)
-      (xy -4.926396 4.921335)
-      (xy -4.910106 4.967236)
-      (xy -4.90116 4.983492)
-      (xy -4.881069 5.023481)
-      (xy -4.866028 5.072307)
-      (xy -4.864874 5.07813)
-      (xy -4.851891 5.12343)
-      (xy -4.834483 5.154419)
-      (xy -4.816808 5.167967)
-      (xy -4.803024 5.160942)
-      (xy -4.797289 5.130211)
-      (xy -4.797285 5.129043)
-      (xy -4.790586 5.106364)
-      (xy -4.782483 5.101907)
-      (xy -4.769384 5.089904)
-      (xy -4.767681 5.079503)
-      (xy -4.761242 5.048253)
-      (xy -4.752879 5.027697)
-      (xy -4.734301 4.990463)
-      (xy -4.725105 4.971821)
-      (xy -4.714423 4.940616)
-      (xy -4.703933 4.895821)
-      (xy -4.701601 4.88301)
-      (xy -4.692323 4.844886)
-      (xy -4.681465 4.822845)
-      (xy -4.677569 4.820671)
-      (xy -4.66711 4.808091)
-      (xy -4.664068 4.786618)
-      (xy -4.657742 4.74741)
-      (xy -4.645565 4.712724)
-      (xy -4.631417 4.689134)
-      (xy -4.611242 4.67724)
-      (xy -4.575617 4.673128)
-      (xy -4.549353 4.672768)
-      (xy -4.500945 4.675028)
-      (xy -4.476823 4.682905)
-      (xy -4.471644 4.693982)
-      (xy -4.353229 4.693982)
-      (xy -4.353229 4.672653)
-      (xy -3.987615 4.672653)
-      (xy -3.977998 4.808143)
-      (xy -3.973636 4.87501)
-      (xy -3.970307 4.936371)
-      (xy -3.968535 4.982115)
-      (xy -3.96838 4.993167)
-      (xy -3.96838 5.042699)
-      (xy -4.057191 5.042699)
-      (xy -4.104497 5.044946)
-      (xy -4.136569 5.050816)
-      (xy -4.146002 5.057501)
-      (xy -4.157914 5.070808)
-      (xy -4.167148 5.072303)
-      (xy -4.200788 5.08566)
-      (xy -4.225191 5.120417)
-      (xy -4.23481 5.1686)
-      (xy -4.234814 5.169572)
-      (xy -4.229789 5.207469)
-      (xy -4.213865 5.220286)
-      (xy -4.212611 5.220322)
-      (xy -4.192913 5.228314)
-      (xy -4.190408 5.235123)
-      (xy -4.176559 5.242454)
-      (xy -4.13875 5.247605)
-      (xy -4.082586 5.249876)
-      (xy -4.071993 5.249925)
-      (xy -4.004516 5.247975)
-      (xy -3.965393 5.242026)
-      (xy -3.953578 5.232656)
-      (xy -3.950054 5.22012)
-      (xy -3.941482 5.230859)
-      (xy -3.930865 5.259665)
-      (xy -3.925042 5.282198)
-      (xy -3.919987 5.316716)
-      (xy -3.159994 5.316716)
-      (xy -3.157161 5.039142)
-      (xy -3.155949 4.912688)
-      (xy -3.155312 4.812224)
-      (xy -3.155446 4.734137)
-      (xy -3.156545 4.674814)
-      (xy -3.158802 4.630644)
-      (xy -3.162412 4.598014)
-      (xy -3.167568 4.573313)
-      (xy -3.174466 4.552928)
-      (xy -3.183299 4.533247)
-      (xy -3.184486 4.530786)
-      (xy -3.231894 4.463996)
-      (xy -3.279545 4.427961)
-      (xy -3.342762 4.390913)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9eccf5b5-6d41-40ce-929b-1b3dd0e7f418))
-  (fp_poly
-    (pts
-      (xy -4.316703 1.860255)
-      (xy -4.53897 1.860298)
-      (xy -4.553054 1.860298)
-      (xy -4.776261 1.860262)
-      (xy -4.971804 1.86025)
-      (xy -5.141619 1.860407)
-      (xy -5.287647 1.86088)
-      (xy -5.411824 1.861813)
-      (xy -5.516089 1.863351)
-      (xy -5.602381 1.865641)
-      (xy -5.672639 1.868827)
-      (xy -5.728799 1.873056)
-      (xy -5.772801 1.878471)
-      (xy -5.806584 1.885219)
-      (xy -5.832085 1.893446)
-      (xy -5.851242 1.903295)
-      (xy -5.865995 1.914914)
-      (xy -5.878281 1.928447)
-      (xy -5.89004 1.944039)
-      (xy -5.902987 1.961548)
-      (xy -5.944429 2.015718)
-      (xy -5.944429 2.93557)
-      (xy -5.905045 2.995096)
-      (xy -5.892965 3.014079)
-      (xy -5.882182 3.030717)
-      (xy -5.870775 3.045163)
-      (xy -5.85682 3.057571)
-      (xy -5.838396 3.068095)
-      (xy -5.813582 3.076889)
-      (xy -5.780454 3.084105)
-      (xy -5.737091 3.089898)
-      (xy -5.681571 3.094421)
-      (xy -5.611972 3.097828)
-      (xy -5.526372 3.100272)
-      (xy -5.422848 3.101908)
-      (xy -5.299479 3.102887)
-      (xy -5.154343 3.103365)
-      (xy -4.985518 3.103495)
-      (xy -4.791081 3.10343)
-      (xy -4.569111 3.103323)
-      (xy -4.550817 3.103318)
-      (xy -4.331481 3.103215)
-      (xy -4.139807 3.103012)
-      (xy -3.973852 3.10267)
-      (xy -3.831673 3.10215)
-      (xy -3.711329 3.101416)
-      (xy -3.610876 3.100428)
-      (xy -3.528373 3.099148)
-      (xy -3.461877 3.097539)
-      (xy -3.409446 3.095563)
-      (xy -3.369138 3.09318)
-      (xy -3.33901 3.090353)
-      (xy -3.317119 3.087044)
-      (xy -3.301524 3.083214)
-      (xy -3.290282 3.078826)
-      (xy -3.289703 3.078544)
-      (xy -3.250455 3.050549)
-      (xy -3.211767 3.009802)
-      (xy -3.200892 2.994851)
-      (xy -3.161678 2.935595)
-      (xy -3.161678 2.50788)
-      (xy -3.479897 2.50788)
-      (xy -3.481571 2.559954)
-      (xy -3.485968 2.598095)
-      (xy -3.492185 2.61495)
-      (xy -3.493073 2.615193)
-      (xy -3.504295 2.628098)
-      (xy -3.514501 2.659707)
-      (xy -3.515598 2.665142)
-      (xy -3.531162 2.705804)
-      (xy -3.559255 2.74839)
-      (xy -3.592731 2.784404)
-      (xy -3.624444 2.805354)
-      (xy -3.635467 2.807618)
-      (xy -3.655082 2.815651)
-      (xy -3.657541 2.822419)
-      (xy -3.670383 2.832892)
-      (xy -3.701073 2.837221)
-      (xy -3.735256 2.841784)
-      (xy -3.753753 2.852023)
-      (xy -3.772405 2.859978)
-      (xy -3.811293 2.865351)
-      (xy -3.849965 2.866825)
-      (xy -3.8982 2.86449)
-      (xy -3.933541 2.858443)
-      (xy -3.946177 2.852023)
-      (xy -3.96586 2.842013)
-      (xy -4.001729 2.837279)
-      (xy -4.006258 2.837221)
-      (xy -4.057191 2.837221)
-      (xy -4.220012 2.837221)
-      (xy -4.382832 2.837221)
-      (xy -4.382996 2.611493)
-      (xy -4.383161 2.385764)
-      (xy -4.418455 2.43017)
-      (xy -4.451592 2.470848)
-      (xy -4.483537 2.508585)
-      (xy -4.484899 2.510145)
-      (xy -4.506863 2.541058)
-      (xy -4.516049 2.565582)
-      (xy -4.516049 2.565652)
-      (xy -4.524821 2.58385)
-      (xy -4.530851 2.58559)
-      (xy -4.544171 2.597495)
-      (xy -4.545653 2.606657)
-      (xy -4.554615 2.631015)
-      (xy -4.576757 2.66442)
-      (xy -4.582658 2.671701)
-      (xy -4.606408 2.702216)
-      (xy -4.619035 2.722902)
-      (xy -4.619662 2.725434)
-      (xy -4.628118 2.741967)
-      (xy -4.649404 2.772103)
-      (xy -4.660367 2.786205)
-      (xy -4.692901 2.820301)
-      (xy -4.725614 2.834872)
-      (xy -4.756579 2.837221)
-      (xy -4.812086 2.837221)
-      (xy -5.004511 2.837221)
-      (xy -5.055444 2.837221)
-      (xy -5.092595 2.841526)
-      (xy -5.115341 2.852027)
-      (xy -5.116383 2.853413)
-      (xy -5.137534 2.862652)
-      (xy -5.177345 2.86159)
-      (xy -5.180165 2.861167)
-      (xy -5.230689 2.853624)
-      (xy -5.288138 2.845563)
-      (xy -5.300548 2.843898)
-      (xy -5.400318 2.818538)
-      (xy -5.481966 2.772023)
-      (xy -5.50607 2.750604)
-      (xy -5.544119 2.707101)
-      (xy -5.568789 2.662265)
-      (xy -5.582597 2.60815)
-      (xy -5.588064 2.536813)
-      (xy -5.58845 2.490793)
-      (xy -5.586782 2.42055)
-      (xy -5.581632 2.370953)
-      (xy -5.571412 2.333103)
-      (xy -5.554537 2.298103)
-      (xy -5.553882 2.296953)
-      (xy -5.513111 2.238507)
-      (xy -5.470614 2.200197)
-      (xy -5.431298 2.186268)
-      (xy -5.406805 2.177171)
-      (xy -5.400928 2.168839)
-      (xy -5.384726 2.161294)
-      (xy -5.345972 2.154391)
-      (xy -5.291716 2.148555)
-      (xy -5.229008 2.144207)
-      (xy -5.164899 2.141772)
-      (xy -5.106438 2.141673)
-      (xy -5.060677 2.144333)
-      (xy -5.042651 2.147327)
-      (xy -5.004511 2.1569)
-      (xy -5.004511 2.837221)
-      (xy -4.812086 2.837221)
-      (xy -4.812086 2.141534)
-      (xy -4.67887 2.141534)
-      (xy -4.67887 2.34876)
-      (xy -4.677628 2.443174)
-      (xy -4.673762 2.508881)
-      (xy -4.667064 2.546681)
-      (xy -4.657323 2.557372)
-      (xy -4.64433 2.541752)
-      (xy -4.634319 2.5186)
-      (xy -4.612999 2.479406)
-      (xy -4.588687 2.448291)
-      (xy -4.559538 2.413471)
-      (xy -4.528535 2.370471)
-      (xy -4.523871 2.363344)
-      (xy -4.496591 2.325032)
-      (xy -4.471016 2.29555)
-      (xy -4.466256 2.291223)
-      (xy -4.446552 2.269244)
-      (xy -4.44204 2.257742)
-      (xy -4.432832 2.239674)
-      (xy -4.409513 2.209253)
-      (xy -4.395256 2.192946)
-      (xy -4.360226 2.159717)
-      (xy -4.326731 2.144802)
-      (xy -4.284242 2.141534)
-      (xy -4.220012 2.141534)
-      (xy -4.220012 2.837221)
-      (xy -4.057191 2.837221)
-      (xy -4.057191 2.496778)
-      (xy -3.909173 2.496778)
-      (xy -3.909173 2.718806)
-      (xy -3.836363 2.718806)
-      (xy -3.759285 2.709656)
-      (xy -3.703497 2.682886)
-      (xy -3.670703 2.639521)
-      (xy -3.663954 2.615193)
-      (xy -3.653101 2.568875)
-      (xy -3.638873 2.529559)
-      (xy -3.638684 2.529169)
-      (xy -3.629595 2.493462)
-      (xy -3.639749 2.466462)
-      (xy -3.653969 2.428726)
-      (xy -3.657541 2.400632)
-      (xy -3.668264 2.364664)
-      (xy -3.695912 2.323586)
-      (xy -3.703397 2.315321)
-      (xy -3.728764 2.290674)
-      (xy -3.752139 2.276393)
-      (xy -3.782613 2.269726)
-      (xy -3.829272 2.267919)
-      (xy -3.859738 2.267967)
-      (xy -3.924717 2.270417)
-      (xy -3.964482 2.27737)
-      (xy -3.983183 2.289557)
-      (xy -3.983299 2.289742)
-      (xy -3.994485 2.303459)
-      (xy -4.004782 2.299847)
-      (xy -4.018372 2.274988)
-      (xy -4.03128 2.244791)
-      (xy -4.042785 2.208141)
-      (xy -4.03986 2.181942)
-      (xy -4.019196 2.164229)
-      (xy -3.977483 2.153037)
-      (xy -3.911411 2.146403)
-      (xy -3.86126 2.143895)
-      (xy -3.786993 2.142138)
-      (xy -3.736769 2.144258)
-      (xy -3.705227 2.150729)
-      (xy -3.690239 2.159023)
-      (xy -3.660228 2.17973)
-      (xy -3.619522 2.203219)
-      (xy -3.61303 2.206604)
-      (xy -3.560529 2.249211)
-      (xy -3.519293 2.314685)
-      (xy -3.491694 2.397656)
-      (xy -3.480107 2.492756)
-      (xy -3.479897 2.50788)
-      (xy -3.161678 2.50788)
-      (xy -3.161678 2.028358)
-      (xy -3.201063 1.968844)
-      (xy -3.213154 1.949852)
-      (xy -3.223952 1.933208)
-      (xy -3.23538 1.918758)
-      (xy -3.249363 1.906347)
-      (xy -3.267824 1.895821)
-      (xy -3.292687 1.887025)
-      (xy -3.325876 1.879805)
-      (xy -3.369315 1.874007)
-      (xy -3.424929 1.869475)
-      (xy -3.49464 1.866056)
-      (xy -3.580373 1.863595)
-      (xy -3.684052 1.861938)
-      (xy -3.8076 1.86093)
-      (xy -3.952942 1.860416)
-      (xy -4.122002 1.860242)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp fcecab74-1485-476f-b781-bc2b3450b9f6))
-  (fp_poly
-    (pts
-      (xy -1.142179 4.02314)
-      (xy -1.275754 4.02338)
-      (xy -1.390524 4.023826)
-      (xy -1.488033 4.024497)
-      (xy -1.569823 4.025414)
-      (xy -1.637436 4.026598)
-      (xy -1.692416 4.02807)
-      (xy -1.736305 4.029849)
-      (xy -1.770646 4.031957)
-      (xy -1.796982 4.034413)
-      (xy -1.816855 4.03724)
-      (xy -1.831809 4.040456)
-      (xy -1.843385 4.044083)
-      (xy -1.853127 4.048141)
-      (xy -1.860207 4.051503)
-      (xy -1.910083 4.083599)
-      (xy -1.955795 4.125496)
-      (xy -1.965239 4.13683)
-      (xy -2.007133 4.191592)
-      (xy -2.007133 4.65045)
-      (xy -2.007085 4.779035)
-      (xy -2.006788 4.881409)
-      (xy -2.006016 4.960964)
-      (xy -2.004542 5.021092)
-      (xy -2.002139 5.065185)
-      (xy -1.998579 5.096636)
-      (xy -1.993635 5.118837)
-      (xy -1.987082 5.13518)
-      (xy -1.97869 5.149057)
-      (xy -1.97324 5.156825)
-      (xy -1.936524 5.199157)
-      (xy -1.893944 5.236705)
-      (xy -1.89183 5.238235)
-      (xy -1.844313 5.272128)
-      (xy 0.102133 5.27392)
-      (xy 0.340319 5.274089)
-      (xy 0.570657 5.274155)
-      (xy 0.79138 5.274121)
-      (xy 1.000717 5.273992)
-      (xy 1.196899 5.273772)
-      (xy 1.378158 5.273467)
-      (xy 1.542723 5.273079)
-      (xy 1.688827 5.272614)
-      (xy 1.814699 5.272076)
-      (xy 1.91857 5.271469)
-      (xy 1.998672 5.270798)
-      (xy 2.053235 5.270066)
-      (xy 2.08049 5.269279)
-      (xy 2.083067 5.269035)
-      (xy 2.123215 5.249931)
-      (xy 2.167616 5.211856)
-      (xy 2.20881 5.163028)
-      (xy 2.209947 5.161114)
-      (xy -0.341923 5.161114)
-      (xy -1.059117 5.161114)
-      (xy -1.252757 5.160791)
-      (xy -1.417136 5.159815)
-      (xy -1.552589 5.158181)
-      (xy -1.659453 5.155881)
-      (xy -1.738062 5.152907)
-      (xy -1.788753 5.149253)
-      (xy -1.811566 5.145051)
-      (xy -1.835233 5.132793)
-      (xy -1.85403 5.117767)
-      (xy -1.868514 5.096657)
-      (xy -1.879244 5.066149)
-      (xy -1.886778 5.022928)
-      (xy -1.891674 4.963681)
-      (xy -1.894491 4.885092)
-      (xy -1.895786 4.783847)
-      (xy -1.896117 4.656633)
-      (xy -1.896119 4.642985)
-      (xy -1.896119 4.240438)
-      (xy -1.795466 4.139785)
-      (xy -0.341923 4.139785)
-      (xy -0.341923 5.161114)
-      (xy 2.209947 5.161114)
-      (xy 2.239336 5.111663)
-      (xy 2.248473 5.086845)
-      (xy 2.254126 5.048238)
-      (xy 2.256233 5.013095)
-      (xy 1.848753 5.013095)
-      (xy 1.700734 5.013095)
-      (xy 1.700734 4.761464)
-      (xy 1.642524 4.761464)
-      (xy 1.600224 4.765711)
-      (xy 1.579318 4.780404)
-      (xy 1.575746 4.788458)
-      (xy 1.559134 4.820624)
-      (xy 1.541445 4.843965)
-      (xy 1.519906 4.873944)
-      (xy 1.494083 4.918104)
-      (xy 1.481368 4.942787)
-      (xy 1.447026 5.013095)
-      (xy 1.366654 5.013095)
-      (xy 1.322394 5.010707)
-      (xy 1.293203 5.004554)
-      (xy 1.286282 4.998744)
-      (xy 1.293651 4.975925)
-      (xy 1.312025 4.9387)
-      (xy 1.335807 4.897171)
-      (xy 1.359399 4.861441)
-      (xy 1.369194 4.849109)
-      (xy 1.386131 4.824577)
-      (xy 1.389895 4.813059)
-      (xy 1.399125 4.794325)
-      (xy 1.421358 4.766886)
-      (xy 1.421716 4.766505)
-      (xy 1.442445 4.742574)
-      (xy 1.443182 4.730668)
-      (xy 1.425416 4.721973)
-      (xy 1.392593 4.704401)
-      (xy 1.371501 4.680927)
-      (xy 1.182669 4.680927)
-      (xy 1.181184 4.746963)
-      (xy 1.177052 4.794357)
-      (xy 1.17076 4.818528)
-      (xy 1.167867 4.820671)
-      (xy 1.155447 4.832935)
-      (xy 1.153065 4.847465)
-      (xy 1.141366 4.878672)
-      (xy 1.111869 4.915541)
-      (xy 1.072975 4.949948)
-      (xy 1.033084 4.97377)
-      (xy 1.017215 4.978838)
-      (xy 0.987256 4.988778)
-      (xy 0.975443 5.000144)
-      (xy 0.961873 5.006992)
-      (xy 0.925845 5.011298)
-      (xy 0.874381 5.013218)
-      (xy 0.850547 5.013095)
-      (xy 0.442576 5.013095)
-      (xy 0.253852 5.011902)
-      (xy 0.172499 5.010797)
-      (xy 0.11423 5.008099)
-      (xy 0.072536 5.002927)
-      (xy 0.040906 4.994404)
-      (xy 0.01283 4.981649)
-      (xy 0.007221 4.978598)
-      (xy -0.030544 4.954122)
-      (xy -0.05635 4.930939)
-      (xy -0.060787 4.924284)
-      (xy -0.075549 4.893607)
-      (xy -0.087991 4.868978)
-      (xy -0.09977 4.834064)
-      (xy -0.104538 4.795163)
-      (xy -0.102098 4.762658)
-      (xy -0.092256 4.746933)
-      (xy -0.090292 4.746662)
-      (xy -0.077934 4.734376)
-      (xy -0.07549 4.719434)
-      (xy -0.063246 4.693665)
-      (xy -0.038485 4.675346)
-      (xy -0.014159 4.656947)
-      (xy -0.001457 4.634435)
-      (xy -0.003953 4.617264)
-      (xy -0.015106 4.613445)
-      (xy -0.02726 4.600636)
-      (xy -0.038727 4.569392)
-      (xy -0.0397 4.565339)
-      (xy -0.049887 4.487998)
-      (xy -0.040316 4.426725)
-      (xy -0.009454 4.380313)
-      (xy 0.04423 4.347554)
-      (xy 0.122268 4.32724)
-      (xy 0.22619 4.318163)
-      (xy 0.274628 4.317408)
-      (xy 0.442576 4.317408)
-      (xy 0.442576 5.013095)
-      (xy 0.850547 5.013095)
-      (xy 0.814505 5.012909)
-      (xy 0.753237 5.010527)
-      (xy 0.697601 5.006228)
-      (xy 0.65462 5.000167)
-      (xy 0.631315 4.992502)
-      (xy 0.631299 4.992491)
-      (xy 0.61971 4.979517)
-      (xy 0.612111 4.957897)
-      (xy 0.607719 4.922055)
-      (xy 0.605751 4.866412)
-      (xy 0.605396 4.807938)
-      (xy 0.605396 4.643049)
-      (xy 0.753415 4.643049)
-      (xy 0.753415 4.894681)
-      (xy 0.827945 4.894681)
-      (xy 0.906883 4.883519)
-      (xy 0.974909 4.847763)
-      (xy 1.005046 4.821901)
-      (xy 1.016553 4.801912)
-      (xy 1.02357 4.765464)
-      (xy 1.026814 4.707464)
-      (xy 1.027249 4.663832)
-      (xy 1.026632 4.598429)
-      (xy 1.023787 4.555595)
-      (xy 1.017223 4.528303)
-      (xy 1.005448 4.509529)
-      (xy 0.99168 4.496274)
-      (xy 0.960694 4.474483)
-      (xy 0.936173 4.465426)
-      (xy 0.917975 4.456655)
-      (xy 0.916235 4.450625)
-      (xy 0.903062 4.441287)
-      (xy 0.869215 4.436643)
-      (xy 0.823202 4.436404)
-      (xy 0.773531 4.440284)
-      (xy 0.728709 4.447994)
-      (xy 0.6996 4.457943)
-      (xy 0.67204 4.470598)
-      (xy 0.655866 4.467526)
-      (xy 0.641787 4.444061)
-      (xy 0.63324 4.424639)
-      (xy 0.617394 4.380765)
-      (xy 0.618611 4.356787)
-      (xy 0.638028 4.347647)
-      (xy 0.650675 4.347012)
-      (xy 0.674249 4.340645)
-      (xy 0.679405 4.33221)
-      (xy 0.692598 4.323213)
-      (xy 0.725817 4.317963)
-      (xy 0.743053 4.317408)
-      (xy 0.78667 4.313501)
-      (xy 0.818666 4.303732)
-      (xy 0.824464 4.299646)
-      (xy 0.844606 4.289505)
-      (xy 0.859988 4.299646)
-      (xy 0.88636 4.312027)
-      (xy 0.925529 4.317401)
-      (xy 0.926891 4.317408)
-      (xy 0.97777 4.327613)
-      (xy 1.032723 4.35443)
-      (xy 1.084541 4.392161)
-      (xy 1.126014 4.43511)
-      (xy 1.149935 4.477579)
-      (xy 1.153065 4.496153)
-      (xy 1.160345 4.523652)
-      (xy 1.167867 4.532035)
-      (xy 1.174321 4.549966)
-      (xy 1.17934 4.590551)
-      (xy 1.182233 4.646851)
-      (xy 1.182669 4.680927)
-      (xy 1.371501 4.680927)
-      (xy 1.366485 4.675345)
-      (xy 1.340908 4.629673)
-      (xy 1.318258 4.554729)
-      (xy 1.325192 4.480763)
-      (xy 1.352621 4.421448)
-      (xy 1.386173 4.379181)
-      (xy 1.423919 4.357791)
-      (xy 1.441595 4.353456)
-      (xy 1.47847 4.34357)
-      (xy 1.500642 4.332131)
-      (xy 1.501946 4.330532)
-      (xy 1.519129 4.325327)
-      (xy 1.559675 4.321099)
-      (xy 1.617345 4.318309)
-      (xy 1.679405 4.317408)
-      (xy 1.848753 4.317408)
-      (xy 1.848753 5.013095)
-      (xy 2.256233 5.013095)
-      (xy 2.258162 4.98093)
-      (xy 2.260558 4.88578)
-      (xy 2.261294 4.763649)
-      (xy 2.260355 4.616105)
-      (xy 2.258929 4.49507)
-      (xy 2.257449 4.399938)
-      (xy 2.255609 4.327008)
-      (xy 2.2531 4.272579)
-      (xy 2.249615 4.232952)
-      (xy 2.244847 4.204425)
-      (xy 2.238488 4.183299)
-      (xy 2.23023 4.165874)
-      (xy 2.221754 4.151633)
-      (xy 2.185539 4.106933)
-      (xy 2.140514 4.067827)
-      (xy 2.132943 4.062822)
-      (xy 2.078182 4.028771)
-      (xy 0.140557 4.024855)
-      (xy -0.138242 4.024296)
-      (xy -0.38898 4.023819)
-      (xy -0.6132 4.023444)
-      (xy -0.812445 4.023192)
-      (xy -0.988257 4.023084)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 2cb66163-632c-4203-b8a3-32ebdf6ed2cd))
-  (fp_poly
-    (pts
-      (xy -2.962124 -9.572409)
-      (xy -3.060675 -9.570286)
-      (xy -3.152976 -9.566186)
-      (xy -3.23306 -9.560095)
-      (xy -3.272692 -9.555489)
-      (xy -3.405058 -9.529968)
-      (xy -3.537528 -9.491205)
-      (xy -3.663205 -9.44201)
-      (xy -3.775195 -9.385194)
-      (xy -3.866599 -9.323565)
-      (xy -3.889284 -9.304277)
-      (xy -3.928747 -9.270027)
-      (xy -3.963316 -9.242599)
-      (xy -3.978096 -9.232472)
-      (xy -4.00333 -9.209049)
-      (xy -4.036672 -9.166847)
-      (xy -4.073077 -9.113606)
-      (xy -4.107496 -9.057069)
-      (xy -4.134884 -9.004976)
-      (xy -4.148568 -8.970966)
-      (xy -4.161747 -8.935736)
-      (xy -4.173649 -8.916606)
-      (xy -4.176153 -8.915459)
-      (xy -4.189771 -8.900883)
-      (xy -4.207162 -8.857517)
-      (xy -4.228125 -8.785908)
-      (xy -4.236677 -8.752639)
-      (xy -4.246832 -8.690476)
-      (xy -4.253118 -8.602593)
-      (xy -4.255301 -8.492649)
-      (xy -4.255165 -8.460474)
-      (xy -4.253313 -8.24972)
-      (xy -4.196891 -8.134833)
-      (xy -4.170087 -8.082381)
-      (xy -4.147098 -8.041245)
-      (xy -4.131622 -8.017895)
-      (xy -4.128434 -8.015013)
-      (xy -4.117579 -7.997996)
-      (xy -4.116399 -7.98801)
-      (xy -4.105785 -7.964539)
-      (xy -4.077449 -7.927759)
-      (xy -4.03665 -7.883024)
-      (xy -3.988646 -7.83569)
-      (xy -3.938695 -7.791109)
-      (xy -3.892055 -7.754635)
-      (xy -3.877555 -7.744819)
-      (xy -3.829101 -7.710439)
-      (xy -3.808047 -7.687024)
-      (xy -3.814333 -7.674478)
-      (xy -3.833638 -7.672103)
-      (xy -3.858418 -7.663604)
-      (xy -3.900441 -7.640829)
-      (xy -3.953725 -7.607856)
-      (xy -4.012288 -7.568767)
-      (xy -4.070148 -7.52764)
-      (xy -4.121323 -7.488557)
-      (xy -4.159831 -7.455597)
-      (xy -4.175703 -7.438797)
-      (xy -4.203196 -7.401012)
-      (xy -4.240246 -7.346641)
-      (xy -4.281019 -7.284384)
-      (xy -4.311292 -7.236531)
-      (xy -4.346854 -7.162883)
-      (xy -4.377029 -7.068947)
-      (xy -4.400872 -6.96203)
-      (xy -4.417441 -6.849439)
-      (xy -4.425791 -6.738482)
-      (xy -4.42498 -6.636467)
-      (xy -4.414064 -6.550702)
-      (xy -4.404353 -6.515718)
-      (xy -4.388305 -6.461267)
-      (xy -4.373867 -6.397521)
-      (xy -4.368941 -6.369539)
-      (xy -4.352238 -6.292321)
-      (xy -4.327125 -6.213591)
-      (xy -4.297341 -6.143368)
-      (xy -4.266626 -6.09167)
-      (xy -4.263972 -6.088303)
-      (xy -4.237535 -6.054398)
-      (xy -4.203914 -6.009535)
-      (xy -4.186253 -5.985362)
-      (xy -4.150783 -5.939832)
-      (xy -4.110546 -5.893525)
-      (xy -4.071077 -5.852189)
-      (xy -4.037914 -5.821573)
-      (xy -4.016594 -5.807423)
-      (xy -4.014482 -5.807068)
-      (xy -3.996619 -5.797198)
-      (xy -3.976323 -5.778062)
-      (xy -3.954235 -5.761555)
-      (xy -3.912629 -5.73664)
-      (xy -3.858142 -5.706702)
-      (xy -3.797414 -5.675125)
-      (xy -3.737085 -5.645292)
-      (xy -3.683794 -5.620588)
-      (xy -3.644181 -5.604395)
-      (xy -3.626629 -5.599842)
-      (xy -3.602891 -5.593988)
-      (xy -3.567114 -5.579731)
-      (xy -3.563566 -5.578098)
-      (xy -3.521478 -5.562854)
-      (xy -3.466136 -5.548207)
-      (xy -3.435513 -5.541985)
-      (xy -3.37945 -5.531838)
-      (xy -3.309074 -5.518753)
-      (xy -3.239126 -5.505474)
-      (xy -3.235688 -5.504812)
-      (xy -3.190237 -5.498536)
-      (xy -3.126003 -5.493002)
-      (xy -3.048195 -5.488321)
-      (xy -2.962021 -5.484603)
-      (xy -2.872689 -5.481962)
-      (xy -2.78541 -5.480508)
-      (xy -2.70539 -5.480352)
-      (xy -2.63784 -5.481606)
-      (xy -2.587966 -5.484381)
-      (xy -2.560979 -5.488788)
-      (xy -2.558237 -5.490327)
-      (xy -2.546887 -5.495547)
-      (xy -2.520416 -5.501889)
-      (xy -2.475679 -5.509888)
-      (xy -2.409531 -5.520079)
-      (xy -2.318829 -5.532997)
-      (xy -2.258765 -5.541264)
-      (xy -2.19895 -5.550362)
-      (xy -2.14771 -5.559832)
-      (xy -2.114482 -5.567891)
-      (xy -2.110746 -5.56921)
-      (xy -2.049443 -5.59161)
-      (xy -1.987634 -5.610901)
-      (xy -1.934622 -5.624423)
-      (xy -1.899714 -5.629519)
-      (xy -1.899619 -5.629519)
-      (xy -1.860432 -5.635623)
-      (xy -1.840411 -5.643353)
-      (xy -1.805273 -5.65746)
-      (xy -1.777704 -5.664913)
-      (xy -1.738252 -5.678605)
-      (xy -1.715544 -5.69171)
-      (xy -1.708127 -5.699507)
-      (xy -1.704059 -5.711724)
-      (xy -1.703966 -5.731878)
-      (xy -1.708475 -5.763491)
-      (xy -1.718211 -5.810081)
-      (xy -1.7338 -5.875169)
-      (xy -1.755869 -5.962273)
-      (xy -1.780827 -6.058699)
-      (xy -1.806147 -6.155564)
-      (xy -1.829147 -6.242557)
-      (xy -1.84875 -6.31569)
-      (xy -1.863881 -6.370975)
-      (xy -1.873464 -6.404423)
-      (xy -1.876313 -6.412733)
-      (xy -1.891837 -6.412138)
-      (xy -1.914644 -6.403845)
-      (xy -1.952707 -6.387816)
-      (xy -2.004946 -6.368078)
-      (xy -2.076184 -6.34287)
-      (xy -2.162553 -6.313367)
-      (xy -2.21946 -6.29399)
-      (xy -2.26842 -6.277062)
-      (xy -2.300159 -6.265794)
-      (xy -2.30317 -6.264674)
-      (xy -2.341593 -6.25479)
-      (xy -2.401037 -6.245014)
-      (xy -2.475617 -6.235779)
-      (xy -2.559443 -6.227516)
-      (xy -2.64663 -6.220658)
-      (xy -2.731291 -6.215636)
-      (xy -2.807537 -6.212883)
-      (xy -2.869481 -6.212831)
-      (xy -2.911238 -6.215911)
-      (xy -2.923573 -6.219148)
-      (xy -2.956499 -6.229448)
-      (xy -3.004479 -6.238521)
-      (xy -3.028462 -6.241518)
-      (xy -3.079124 -6.249899)
-      (xy -3.144654 -6.26508)
-      (xy -3.212008 -6.283994)
-      (xy -3.220886 -6.286779)
-      (xy -3.307989 -6.31995)
-      (xy -3.376721 -6.360395)
-      (xy -3.431274 -6.41288)
-      (xy -3.475836 -6.482172)
-      (xy -3.514596 -6.573035)
-      (xy -3.539765 -6.649535)
-      (xy -3.556684 -6.710218)
-      (xy -3.563439 -6.750124)
-      (xy -3.560834 -6.775978)
-      (xy -3.556063 -6.786073)
-      (xy -3.544429 -6.819268)
-      (xy -3.539154 -6.863082)
-      (xy -3.539126 -6.866173)
-      (xy -3.536392 -6.905504)
-      (xy -3.525798 -6.940389)
-      (xy -3.503754 -6.976577)
-      (xy -3.466673 -7.019817)
-      (xy -3.410965 -7.075858)
-      (xy -3.404051 -7.082562)
-      (xy -3.344183 -7.137092)
-      (xy -3.296192 -7.172225)
-      (xy -3.25404 -7.192128)
-      (xy -3.239236 -7.196343)
-      (xy -3.041637 -7.250562)
-      (xy -3.009959 -7.260444)
-      (xy -2.97602 -7.266672)
-      (xy -2.917632 -7.272448)
-      (xy -2.839947 -7.277428)
-      (xy -2.748119 -7.281266)
-      (xy -2.669516 -7.283253)
-      (xy -2.384581 -7.288467)
-      (xy -2.384581 -7.981216)
-      (xy -2.676917 -7.987751)
-      (xy -2.772543 -7.99053)
-      (xy -2.863044 -7.994336)
-      (xy -2.942327 -7.998825)
-      (xy -3.004297 -8.003649)
-      (xy -3.04286 -8.008464)
-      (xy -3.043264 -8.008541)
-      (xy -3.111128 -8.027872)
-      (xy -3.181426 -8.058122)
-      (xy -3.244792 -8.094386)
-      (xy -3.29186 -8.131756)
-      (xy -3.303113 -8.144671)
-      (xy -3.328018 -8.177351)
-      (xy -3.346541 -8.200645)
-      (xy -3.360212 -8.228793)
-      (xy -3.361504 -8.238389)
-      (xy -3.371176 -8.266446)
-      (xy -3.377056 -8.273809)
-      (xy -3.384054 -8.294727)
-      (xy -3.389725 -8.337675)
-      (xy -3.393228 -8.395079)
-      (xy -3.393891 -8.42534)
-      (xy -3.392933 -8.500225)
-      (xy -3.387627 -8.553917)
-      (xy -3.376823 -8.594653)
-      (xy -3.367237 -8.616274)
-      (xy -3.347115 -8.651808)
-      (xy -3.330767 -8.673848)
-      (xy -3.327346 -8.676447)
-      (xy -3.310288 -8.688383)
-      (xy -3.278979 -8.713618)
-      (xy -3.252605 -8.736006)
-      (xy -3.203167 -8.771679)
-      (xy -3.148548 -8.800874)
-      (xy -3.123943 -8.810184)
-      (xy -3.07667 -8.82549)
-      (xy -3.036962 -8.840131)
-      (xy -3.027348 -8.844254)
-      (xy -2.996906 -8.850266)
-      (xy -2.944983 -8.852684)
-      (xy -2.87944 -8.851824)
-      (xy -2.808139 -8.847998)
-      (xy -2.738943 -8.84152)
-      (xy -2.679715 -8.832705)
-      (xy -2.665816 -8.829822)
-      (xy -2.61528 -8.818444)
-      (xy -2.551187 -8.804057)
-      (xy -2.497866 -8.792113)
-      (xy -2.443175 -8.777713)
-      (xy -2.397845 -8.7619)
-      (xy -2.37205 -8.748334)
-      (xy -2.3411 -8.729017)
-      (xy -2.299684 -8.711158)
-      (xy -2.297596 -8.710446)
-      (xy -2.255908 -8.692788)
-      (xy -2.204355 -8.666123)
-      (xy -2.175259 -8.649143)
-      (xy -2.133426 -8.624857)
-      (xy -2.10104 -8.608686)
-      (xy -2.088391 -8.60462)
-      (xy -2.078154 -8.617205)
-      (xy -2.057408 -8.651928)
-      (xy -2.028462 -8.704242)
-      (xy -1.993627 -8.769603)
-      (xy -1.955211 -8.843463)
-      (xy -1.915525 -8.921277)
-      (xy -1.876878 -8.998498)
-      (xy -1.841579 -9.07058)
-      (xy -1.811938 -9.132977)
-      (xy -1.790265 -9.181142)
-      (xy -1.77887 -9.210529)
-      (xy -1.777704 -9.216176)
-      (xy -1.789373 -9.242816)
-      (xy -1.817153 -9.272038)
-      (xy -1.850206 -9.294173)
-      (xy -1.872022 -9.300308)
-      (xy -1.899428 -9.30724)
-      (xy -1.94035 -9.32489)
-      (xy -1.964105 -9.337312)
-      (xy -2.005771 -9.358642)
-      (xy -2.038552 -9.372015)
-      (xy -2.049188 -9.374317)
-      (xy -2.072158 -9.382561)
-      (xy -2.106595 -9.403143)
-      (xy -2.118147 -9.411322)
-      (xy -2.157275 -9.434889)
-      (xy -2.192375 -9.447605)
-      (xy -2.199473 -9.448326)
-      (xy -2.231449 -9.454154)
-      (xy -2.244703 -9.461569)
-      (xy -2.262708 -9.471241)
-      (xy -2.300128 -9.483271)
-      (xy -2.360011 -9.498495)
-      (xy -2.445403 -9.517746)
-      (xy -2.465991 -9.522192)
-      (xy -2.521855 -9.535849)
-      (xy -2.57917 -9.552209)
-      (xy -2.584406 -9.553863)
-      (xy -2.624725 -9.561413)
-      (xy -2.688623 -9.567057)
-      (xy -2.770132 -9.57078)
-      (xy -2.863287 -9.572569)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 584adb05-92b6-498b-96a8-d89b1d726549))
-  (fp_poly
-    (pts
-      (xy -0.072538 -9.572844)
-      (xy -0.205074 -9.566837)
-      (xy -0.333169 -9.557172)
-      (xy -0.450153 -9.544125)
-      (xy -0.549353 -9.527976)
-      (xy -0.608357 -9.513912)
-      (xy -0.660651 -9.49931)
-      (xy -0.706756 -9.487401)
-      (xy -0.726772 -9.482831)
-      (xy -0.804573 -9.46279)
-      (xy -0.885591 -9.434847)
-      (xy -0.955517 -9.404105)
-      (xy -0.971002 -9.395778)
-      (xy -1.024719 -9.369407)
-      (xy -1.082255 -9.347046)
-      (xy -1.093118 -9.343652)
-      (xy -1.130965 -9.331765)
-      (xy -1.153388 -9.323175)
-      (xy -1.156026 -9.321271)
-      (xy -1.15122 -9.305826)
-      (xy -1.137902 -9.267218)
-      (xy -1.117717 -9.210002)
-      (xy -1.092313 -9.138734)
-      (xy -1.063336 -9.057967)
-      (xy -1.032433 -8.972256)
-      (xy -1.001251 -8.886158)
-      (xy -0.971436 -8.804225)
-      (xy -0.944635 -8.731015)
-      (xy -0.922495 -8.67108)
-      (xy -0.906662 -8.628976)
-      (xy -0.898784 -8.609258)
-      (xy -0.898298 -8.608392)
-      (xy -0.882246 -8.611185)
-      (xy -0.842854 -8.625063)
-      (xy -0.783625 -8.648633)
-      (xy -0.708065 -8.680504)
-      (xy -0.624492 -8.717137)
-      (xy -0.576993 -8.734727)
-      (xy -0.520993 -8.750794)
-      (xy -0.506077 -8.754252)
-      (xy -0.448675 -8.766776)
-      (xy -0.391085 -8.779577)
-      (xy -0.378928 -8.782322)
-      (xy -0.327454 -8.790527)
-      (xy -0.266237 -8.795646)
-      (xy -0.241164 -8.7964)
-      (xy -0.179273 -8.800341)
-      (xy -0.115948 -8.809502)
-      (xy -0.094788 -8.814122)
-      (xy -0.045082 -8.823413)
-      (xy -0.012503 -8.820304)
-      (xy 0.000377 -8.814122)
-      (xy 0.029659 -8.804812)
-      (xy 0.076712 -8.79861)
-      (xy 0.11606 -8.797044)
-      (xy 0.167436 -8.792786)
-      (xy 0.22775 -8.7815)
-      (xy 0.289555 -8.765421)
-      (xy 0.345402 -8.746782)
-      (xy 0.387843 -8.727816)
-      (xy 0.409431 -8.710757)
-      (xy 0.410318 -8.708795)
-      (xy 0.42747 -8.694719)
-      (xy 0.436195 -8.693431)
-      (xy 0.452811 -8.681111)
-      (xy 0.476578 -8.648781)
-      (xy 0.502406 -8.603383)
-      (xy 0.502887 -8.602434)
-      (xy 0.52941 -8.544192)
-      (xy 0.541611 -8.499363)
-      (xy 0.542234 -8.457175)
-      (xy 0.541535 -8.450715)
-      (xy 0.528689 -8.369681)
-      (xy 0.512111 -8.31457)
-      (xy 0.490475 -8.281796)
-      (xy 0.475311 -8.271711)
-      (xy 0.446597 -8.251431)
-      (xy 0.435059 -8.234208)
-      (xy 0.418167 -8.212072)
-      (xy 0.386025 -8.18723)
-      (xy 0.379687 -8.183384)
-      (xy 0.346397 -8.162953)
-      (xy 0.325819 -8.148347)
-      (xy 0.324161 -8.146727)
-      (xy 0.305936 -8.134372)
-      (xy 0.270053 -8.115023)
-      (xy 0.22584 -8.093181)
-      (xy 0.182626 -8.073343)
-      (xy 0.149739 -8.060009)
-      (xy 0.137995 -8.056951)
-      (xy 0.116999 -8.05091)
-      (xy 0.079037 -8.035315)
-      (xy 0.045768 -8.019946)
-      (xy 0.000699 -7.999641)
-      (xy -0.035042 -7.986106)
-      (xy -0.049514 -7.982719)
-      (xy -0.079331 -7.976747)
-      (xy -0.123767 -7.962156)
-      (xy -0.170813 -7.943267)
-      (xy -0.203401 -7.927333)
-      (xy -0.233502 -7.91296)
-      (xy -0.280663 -7.893)
-      (xy -0.329217 -7.87388)
-      (xy -0.416922 -7.839537)
-      (xy -0.503731 -7.803679)
-      (xy -0.584064 -7.768783)
-      (xy -0.65234 -7.737326)
-      (xy -0.702979 -7.711786)
-      (xy -0.727176 -7.697183)
-      (xy -0.760192 -7.674529)
-      (xy -0.806497 -7.644465)
-      (xy -0.840451 -7.623173)
-      (xy -0.921924 -7.569668)
-      (xy -0.995067 -7.515456)
-      (xy -1.054872 -7.464651)
-      (xy -1.096333 -7.421365)
-      (xy -1.10958 -7.40211)
-      (xy -1.137077 -7.357064)
-      (xy -1.164315 -7.318693)
-      (xy -1.191483 -7.277968)
-      (xy -1.220324 -7.225297)
-      (xy -1.246588 -7.169735)
-      (xy -1.266023 -7.120336)
-      (xy -1.274378 -7.086156)
-      (xy -1.274441 -7.084135)
-      (xy -1.280149 -7.05273)
-      (xy -1.294539 -7.008583)
-      (xy -1.302272 -6.989398)
-      (xy -1.318365 -6.934639)
-      (xy -1.330656 -6.858847)
-      (xy -1.338573 -6.770417)
-      (xy -1.341546 -6.677744)
-      (xy -1.339002 -6.589221)
-      (xy -1.333378 -6.532359)
-      (xy -1.319573 -6.438519)
-      (xy -1.306363 -6.365772)
-      (xy -1.291344 -6.305758)
-      (xy -1.272109 -6.250118)
-      (xy -1.246256 -6.190494)
-      (xy -1.218401 -6.132709)
-      (xy -1.169203 -6.0401)
-      (xy -1.120199 -5.964807)
-      (xy -1.063767 -5.895593)
-      (xy -1.040141 -5.869976)
-      (xy -0.995937 -5.824569)
-      (xy -0.958579 -5.788621)
-      (xy -0.933053 -5.766795)
-      (xy -0.925198 -5.762393)
-      (xy -0.906199 -5.754511)
-      (xy -0.872137 -5.734622)
-      (xy -0.847433 -5.718507)
-      (xy -0.778163 -5.679941)
-      (xy -0.685821 -5.640871)
-      (xy -0.57684 -5.603223)
-      (xy -0.457652 -5.568922)
-      (xy -0.33469 -5.539894)
-      (xy -0.214384 -5.518064)
-      (xy -0.149499 -5.509583)
-      (xy -0.074386 -5.502751)
-      (xy 0.012671 -5.497034)
-      (xy 0.106133 -5.492555)
-      (xy 0.200462 -5.489437)
-      (xy 0.290118 -5.487802)
-      (xy 0.369564 -5.487774)
-      (xy 0.43326 -5.489474)
-      (xy 0.475669 -5.493027)
-      (xy 0.486981 -5.495474)
-      (xy 0.522847 -5.502915)
-      (xy 0.574107 -5.508156)
-      (xy 0.60663 -5.509555)
-      (xy 0.654042 -5.512221)
-      (xy 0.688805 -5.517529)
-      (xy 0.700318 -5.522132)
-      (xy 0.719115 -5.529146)
-      (xy 0.759841 -5.538361)
-      (xy 0.815065 -5.548187)
-      (xy 0.839702 -5.551955)
-      (xy 0.928579 -5.565134)
-      (xy 0.992592 -5.575258)
-      (xy 1.036221 -5.5832)
-      (xy 1.063945 -5.589829)
-      (xy 1.080243 -5.596017)
-      (xy 1.086457 -5.599922)
-      (xy 1.109232 -5.609032)
-      (xy 1.149202 -5.618611)
-      (xy 1.167867 -5.621932)
-      (xy 1.219123 -5.635145)
-      (xy 1.279281 -5.657668)
-      (xy 1.315886 -5.67479)
-      (xy 1.366523 -5.699244)
-      (xy 1.41263 -5.718484)
-      (xy 1.436912 -5.726367)
-      (xy 1.476892 -5.743878)
-      (xy 1.501668 -5.763501)
-      (xy 1.509088 -5.773571)
-      (xy 1.512866 -5.786431)
-      (xy 1.512044 -5.805631)
-      (xy 1.505662 -5.834717)
-      (xy 1.49276 -5.877238)
-      (xy 1.47238 -5.936741)
-      (xy 1.443561 -6.016775)
-      (xy 1.405346 -6.120887)
-      (xy 1.404163 -6.124096)
-      (xy 1.369265 -6.218285)
-      (xy 1.337257 -6.303707)
-      (xy 1.309702 -6.376265)
-      (xy 1.288165 -6.431865)
-      (xy 1.274209 -6.466413)
-      (xy 1.269946 -6.475634)
-      (xy 1.256064 -6.48438)
-      (xy 1.229959 -6.477326)
-      (xy 1.202019 -6.462999)
-      (xy 1.164057 -6.445368)
-      (xy 1.106567 -6.422799)
-      (xy 1.038439 -6.398654)
-      (xy 0.990245 -6.382946)
-      (xy 0.92705 -6.362255)
-      (xy 0.875279 -6.343616)
-      (xy 0.840914 -6.329294)
-      (xy 0.829891 -6.322292)
-      (xy 0.813292 -6.314181)
-      (xy 0.779398 -6.310372)
-      (xy 0.775258 -6.310331)
-      (xy 0.739264 -6.306906)
-      (xy 0.718419 -6.298567)
-      (xy 0.717716 -6.297643)
-      (xy 0.698492 -6.289488)
-      (xy 0.654491 -6.282048)
-      (xy 0.590535 -6.275472)
-      (xy 0.511445 -6.269912)
-      (xy 0.422044 -6.26552)
-      (xy 0.327153 -6.262448)
-      (xy 0.231594 -6.260847)
-      (xy 0.140189 -6.260868)
-      (xy 0.057758 -6.262663)
-      (xy -0.010875 -6.266383)
-      (xy -0.06089 -6.27218)
-      (xy -0.065466 -6.273033)
-      (xy -0.113943 -6.287261)
-      (xy -0.168931 -6.309811)
-      (xy -0.188365 -6.319477)
-      (xy -0.229373 -6.339814)
-      (xy -0.260374 -6.352554)
-      (xy -0.269653 -6.354737)
-      (xy -0.28887 -6.365957)
-      (xy -0.31745 -6.394574)
-      (xy -0.348843 -6.433019)
-      (xy -0.3765 -6.473723)
-      (xy -0.383907 -6.486767)
-      (xy -0.396164 -6.526851)
-      (xy -0.403115 -6.584436)
-      (xy -0.404794 -6.649655)
-      (xy -0.401236 -6.71264)
-      (xy -0.392477 -6.763524)
-      (xy -0.382845 -6.787317)
-      (xy -0.317595 -6.869851)
-      (xy -0.234671 -6.944041)
-      (xy -0.129712 -7.013356)
-      (xy -0.036478 -7.062969)
-      (xy 0.043749 -7.100722)
-      (xy 0.128711 -7.13777)
-      (xy 0.207736 -7.169614)
-      (xy 0.264953 -7.190099)
-      (xy 0.331578 -7.212599)
-      (xy 0.396188 -7.236088)
-      (xy 0.447132 -7.256292)
-      (xy 0.456584 -7.260427)
-      (xy 0.501783 -7.279358)
-      (xy 0.563614 -7.303354)
-      (xy 0.630659 -7.32802)
-      (xy 0.649009 -7.334517)
-      (xy 0.709386 -7.357394)
-      (xy 0.761694 -7.380304)
-      (xy 0.79752 -7.399446)
-      (xy 0.805221 -7.405082)
-      (xy 0.832377 -7.424345)
-      (xy 0.877217 -7.451425)
-      (xy 0.930888 -7.481023)
-      (xy 0.940793 -7.486204)
-      (xy 1.03088 -7.543902)
-      (xy 1.123618 -7.622579)
-      (xy 1.212242 -7.715145)
-      (xy 1.289985 -7.814513)
-      (xy 1.350084 -7.913595)
-      (xy 1.351644 -7.916688)
-      (xy 1.383765 -7.984253)
-      (xy 1.406873 -8.043464)
-      (xy 1.423621 -8.103845)
-      (xy 1.436662 -8.174923)
-      (xy 1.448405 -8.264177)
-      (xy 1.456184 -8.321901)
-      (xy 1.464436 -8.370559)
-      (xy 1.471498 -8.400461)
-      (xy 1.472093 -8.402093)
-      (xy 1.474267 -8.436126)
-      (xy 1.46688 -8.4613)
-      (xy 1.459026 -8.479501)
-      (xy 1.45219 -8.502015)
-      (xy 1.445258 -8.534417)
-      (xy 1.437115 -8.582284)
-      (xy 1.426647 -8.65119)
-      (xy 1.420365 -8.694099)
-      (xy 1.406826 -8.769075)
-      (xy 1.390634 -8.830341)
-      (xy 1.373583 -8.871925)
-      (xy 1.36291 -8.885554)
-      (xy 1.3517 -8.90225)
-      (xy 1.333152 -8.937708)
-      (xy 1.31573 -8.974581)
-      (xy 1.282187 -9.032195)
-      (xy 1.231758 -9.099151)
-      (xy 1.1709 -9.168551)
-      (xy 1.106069 -9.233502)
-      (xy 1.043721 -9.287108)
-      (xy 0.990313 -9.322474)
-      (xy 0.98967 -9.322802)
-      (xy 0.946533 -9.347117)
-      (xy 0.913123 -9.370295)
-      (xy 0.903181 -9.379612)
-      (xy 0.875974 -9.398551)
-      (xy 0.837503 -9.412211)
-      (xy 0.790453 -9.428413)
-      (xy 0.752915 -9.448896)
-      (xy 0.712767 -9.469314)
-      (xy 0.663528 -9.484633)
-      (xy 0.656703 -9.48599)
-      (xy 0.615609 -9.495387)
-      (xy 0.586957 -9.505464)
-      (xy 0.583193 -9.50771)
-      (xy 0.559411 -9.517473)
-      (xy 0.521105 -9.526479)
-      (xy 0.516585 -9.527246)
-      (xy 0.473972 -9.534699)
-      (xy 0.416392 -9.545428)
-      (xy 0.368566 -9.554703)
-      (xy 0.28499 -9.56612)
-      (xy 0.179165 -9.572764)
-      (xy 0.057765 -9.574912)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp fa8f8799-64b8-451d-a12d-e63649d3b682))
-  (fp_poly
-    (pts
-      (xy 4.14245 -3.167855)
-      (xy 4.078575 -3.119227)
-      (xy 4.04391 -3.069314)
-      (xy 4.034078 -3.049844)
-      (xy 4.026345 -3.030464)
-      (xy 4.020459 -3.007516)
-      (xy 4.016168 -2.977341)
-      (xy 4.01322 -2.936281)
-      (xy 4.011363 -2.880679)
-      (xy 4.010347 -2.806876)
-      (xy 4.009918 -2.711214)
-      (xy 4.009825 -2.590035)
-      (xy 4.009825 -2.574002)
-      (xy 4.009988 -2.439777)
-      (xy 4.010945 -2.331694)
-      (xy 4.013399 -2.246288)
-      (xy 4.018055 -2.180098)
-      (xy 4.025616 -2.12966)
-      (xy 4.036785 -2.091512)
-      (xy 4.052266 -2.06219)
-      (xy 4.072763 -2.038232)
-      (xy 4.098978 -2.016175)
-      (xy 4.127338 -1.995588)
-      (xy 4.189982 -1.951182)
-      (xy 5.391366 -1.947624)
-      (xy 5.608391 -1.947006)
-      (xy 5.797805 -1.946546)
-      (xy 5.961605 -1.946284)
-      (xy 6.101782 -1.946258)
-      (xy 6.220332 -1.946506)
-      (xy 6.319249 -1.947067)
-      (xy 6.400525 -1.947979)
-      (xy 6.466156 -1.949281)
-      (xy 6.518135 -1.95101)
-      (xy 6.558456 -1.953205)
-      (xy 6.589113 -1.955905)
-      (xy 6.6121 -1.959147)
-      (xy 6.629411 -1.962971)
-      (xy 6.64304 -1.967415)
-      (xy 6.653676 -1.971917)
-      (xy 6.701989 -2.002294)
-      (xy 6.747224 -2.043624)
-      (xy 6.757289 -2.055704)
-      (xy 6.799977 -2.111642)
-      (xy 6.801143 -2.232407)
-      (xy 6.316129 -2.232407)
-      (xy 6.304294 -2.225721)
-      (xy 6.282785 -2.225016)
-      (xy 6.251443 -2.219559)
-      (xy 6.237506 -2.210215)
-      (xy 6.219252 -2.203056)
-      (xy 6.179494 -2.197801)
-      (xy 6.126317 -2.195452)
-      (xy 6.118217 -2.195413)
-      (xy 6.062605 -2.197263)
-      (xy 6.023881 -2.202265)
-      (xy 6.008158 -2.209598)
-      (xy 6.008077 -2.210215)
-      (xy 5.995618 -2.222048)
-      (xy 5.977011 -2.225016)
-      (xy 5.945644 -2.236589)
-      (xy 5.909775 -2.265082)
-      (xy 5.878571 -2.301158)
-      (xy 5.861201 -2.335479)
-      (xy 5.860058 -2.344123)
-      (xy 5.852888 -2.371804)
-      (xy 5.845256 -2.380436)
-      (xy 5.832822 -2.401314)
-      (xy 5.830454 -2.418314)
-      (xy 5.836821 -2.441888)
-      (xy 5.845256 -2.447044)
-      (xy 5.856639 -2.459639)
-      (xy 5.860058 -2.481784)
-      (xy 5.869134 -2.516763)
-      (xy 5.890988 -2.551752)
-      (xy 5.91756 -2.575735)
-      (xy 5.932103 -2.580261)
-      (xy 5.947329 -2.58522)
-      (xy 5.940163 -2.601872)
-      (xy 5.912888 -2.629823)
-      (xy 5.88775 -2.660556)
-      (xy 5.874758 -2.699296)
-      (xy 5.871613 -2.754765)
-      (xy 5.872558 -2.782789)
-      (xy 5.882516 -2.822822)
-      (xy 5.903707 -2.839053)
-      (xy 5.932121 -2.859963)
-      (xy 5.941709 -2.877056)
-      (xy 5.961496 -2.900708)
-      (xy 5.97947 -2.905902)
-      (xy 5.744938 -2.905902)
-      (xy 5.734653 -2.850395)
-      (xy 5.724772 -2.813347)
-      (xy 5.713279 -2.791621)
-      (xy 5.710803 -2.789954)
-      (xy 5.699363 -2.773027)
-      (xy 5.697238 -2.757524)
-      (xy 5.69015 -2.729703)
-      (xy 5.682436 -2.720879)
-      (xy 5.670978 -2.700476)
-      (xy 5.667634 -2.6756)
-      (xy 5.66304 -2.648194)
-      (xy 5.654513 -2.639469)
-      (xy 5.644726 -2.626293)
-      (xy 5.635028 -2.592944)
-      (xy 5.631403 -2.57286)
-      (xy 5.622707 -2.533205)
-      (xy 5.612173 -2.509361)
-      (xy 5.607519 -2.506252)
-      (xy 5.595188 -2.494249)
-      (xy 5.593625 -2.484049)
-      (xy 5.585632 -2.464351)
-      (xy 5.578823 -2.461846)
-      (xy 5.567374 -2.449271)
-      (xy 5.564021 -2.427671)
-      (xy 5.555065 -2.388227)
-      (xy 5.542289 -2.364763)
-      (xy 5.524788 -2.331578)
-      (xy 5.520086 -2.310127)
-      (xy 5.512692 -2.288147)
-      (xy 5.504813 -2.284224)
-      (xy 5.491783 -2.272192)
-      (xy 5.490011 -2.261396)
-      (xy 5.477102 -2.22466)
-      (xy 5.439681 -2.202459)
-      (xy 5.390099 -2.195976)
-      (xy 5.346608 -2.199166)
-      (xy 5.328309 -2.210526)
-      (xy 5.327191 -2.216217)
-      (xy 5.320687 -2.240938)
-      (xy 5.311835 -2.261776)
-      (xy 5.001349 -2.261776)
-      (xy 4.995213 -2.235039)
-      (xy 4.972319 -2.225325)
-      (xy 4.964545 -2.225016)
-      (xy 4.936728 -2.21995)
-      (xy 4.927541 -2.210215)
-      (xy 4.913692 -2.202884)
-      (xy 4.875882 -2.197733)
-      (xy 4.819719 -2.195462)
-      (xy 4.809126 -2.195413)
-      (xy 4.750484 -2.197144)
-      (xy 4.709275 -2.20187)
-      (xy 4.691105 -2.20889)
-      (xy 4.690711 -2.210215)
-      (xy 4.678493 -2.222775)
-      (xy 4.664808 -2.225034)
-      (xy 4.637316 -2.234243)
-      (xy 4.60215 -2.256991)
-      (xy 4.594499 -2.263274)
-      (xy 4.571998 -2.28451)
-      (xy 4.558747 -2.305717)
-      (xy 4.552309 -2.335277)
-      (xy 4.550246 -2.381574)
-      (xy 4.550093 -2.416039)
-      (xy 4.55187 -2.481107)
-      (xy 4.557981 -2.523312)
-      (xy 4.569597 -2.549226)
-      (xy 4.574939 -2.555422)
-      (xy 4.600578 -2.57496)
-      (xy 4.615644 -2.580261)
-      (xy 4.630405 -2.588258)
-      (xy 4.621729 -2.612669)
-      (xy 4.594517 -2.648268)
-      (xy 4.562986 -2.70513)
-      (xy 4.55753 -2.743082)
-      (xy 4.571951 -2.804015)
-      (xy 4.594517 -2.837896)
-      (xy 4.618463 -2.868732)
-      (xy 4.630976 -2.890687)
-      (xy 4.631503 -2.893403)
-      (xy 4.643882 -2.903665)
-      (xy 4.660233 -2.905902)
-      (xy 4.688569 -2.912699)
-      (xy 4.698112 -2.920704)
-      (xy 4.717103 -2.929337)
-      (xy 4.755138 -2.934671)
-      (xy 4.779522 -2.935506)
-      (xy 4.823398 -2.932709)
-      (xy 4.853836 -2.925593)
-      (xy 4.860932 -2.920704)
-      (xy 4.881585 -2.908585)
-      (xy 4.902511 -2.905431)
-      (xy 4.941106 -2.896092)
-      (xy 4.961897 -2.884528)
-      (xy 4.978894 -2.868268)
-      (xy 4.979661 -2.849946)
-      (xy 4.965438 -2.818817)
-      (xy 4.946809 -2.789004)
-      (xy 4.927871 -2.781368)
-      (xy 4.904215 -2.787914)
-      (xy 4.86162 -2.797743)
-      (xy 4.809373 -2.801578)
-      (xy 4.759854 -2.799313)
-      (xy 4.725441 -2.790844)
-      (xy 4.722991 -2.789454)
-      (xy 4.709864 -2.764933)
-      (xy 4.708189 -2.719372)
-      (xy 4.712914 -2.661671)
-      (xy 4.798024 -2.657232)
-      (xy 4.883135 -2.652793)
-      (xy 4.883135 -2.535856)
-      (xy 4.816527 -2.535856)
-      (xy 4.776803 -2.532916)
-      (xy 4.752975 -2.525477)
-      (xy 4.749918 -2.521054)
-      (xy 4.738516 -2.506851)
-      (xy 4.734059 -2.506252)
-      (xy 4.702545 -2.493954)
-      (xy 4.683545 -2.462743)
-      (xy 4.678459 -2.421145)
-      (xy 4.688687 -2.377684)
-      (xy 4.708093 -2.348086)
-      (xy 4.73324 -2.327513)
-      (xy 4.765457 -2.317112)
-      (xy 4.815045 -2.31388)
-      (xy 4.825634 -2.313828)
-      (xy 4.873384 -2.316208)
-      (xy 4.908185 -2.322361)
-      (xy 4.92014 -2.328629)
-      (xy 4.942974 -2.343382)
-      (xy 4.970746 -2.337655)
-      (xy 4.990719 -2.314718)
-      (xy 4.992221 -2.310127)
-      (xy 5.001349 -2.261776)
-      (xy 5.311835 -2.261776)
-      (xy 5.304576 -2.278865)
-      (xy 5.283964 -2.319857)
-      (xy 5.263954 -2.353778)
-      (xy 5.24965 -2.37049)
-      (xy 5.249481 -2.370568)
-      (xy 5.240198 -2.38751)
-      (xy 5.23838 -2.403771)
-      (xy 5.233014 -2.433798)
-      (xy 5.219721 -2.473323)
-      (xy 5.202707 -2.51249)
-      (xy 5.186181 -2.541442)
-      (xy 5.175681 -2.550657)
-      (xy 5.167439 -2.563447)
-      (xy 5.164279 -2.591363)
-      (xy 5.157142 -2.634691)
-      (xy 5.142076 -2.674465)
-      (xy 5.126456 -2.710445)
-      (xy 5.119965 -2.737373)
-      (xy 5.111404 -2.755959)
-      (xy 5.105163 -2.757884)
-      (xy 5.094036 -2.770551)
-      (xy 5.090361 -2.794888)
-      (xy 5.085294 -2.822705)
-      (xy 5.075559 -2.831893)
-      (xy 5.064432 -2.84456)
-      (xy 5.060757 -2.868898)
-      (xy 5.063408 -2.891476)
-      (xy 5.076578 -2.902341)
-      (xy 5.108095 -2.905709)
-      (xy 5.129434 -2.905902)
-      (xy 5.189362 -2.897286)
-      (xy 5.225435 -2.871312)
-      (xy 5.237909 -2.828192)
-      (xy 5.244411 -2.806201)
-      (xy 5.251275 -2.802289)
-      (xy 5.26038 -2.78902)
-      (xy 5.269552 -2.75508)
-      (xy 5.273987 -2.72828)
-      (xy 5.282144 -2.686116)
-      (xy 5.292256 -2.659314)
-      (xy 5.298097 -2.65427)
-      (xy 5.309826 -2.641907)
-      (xy 5.312389 -2.62554)
-      (xy 5.319186 -2.597204)
-      (xy 5.327191 -2.587662)
-      (xy 5.337855 -2.567652)
-      (xy 5.341993 -2.534982)
-      (xy 5.346014 -2.504178)
-      (xy 5.355619 -2.49145)
-      (xy 5.367957 -2.47869)
-      (xy 5.378805 -2.447908)
-      (xy 5.378998 -2.447044)
-      (xy 5.391343 -2.413301)
-      (xy 5.404875 -2.403944)
-      (xy 5.41438 -2.420017)
-      (xy 5.416002 -2.439643)
-      (xy 5.421069 -2.467461)
-      (xy 5.430804 -2.476648)
-      (xy 5.443903 -2.488651)
-      (xy 5.445606 -2.499052)
-      (xy 5.452045 -2.530302)
-      (xy 5.460408 -2.550858)
-      (xy 5.479963 -2.589754)
-      (xy 5.489733 -2.609218)
-      (xy 5.501522 -2.642627)
-      (xy 5.512145 -2.688272)
-      (xy 5.513828 -2.69803)
-      (xy 5.522605 -2.735271)
-      (xy 5.533015 -2.756212)
-      (xy 5.536309 -2.757884)
-      (xy 5.546102 -2.770535)
-      (xy 5.549219 -2.794015)
-      (xy 5.554677 -2.825356)
-      (xy 5.564021 -2.839294)
-      (xy 5.576455 -2.860171)
-      (xy 5.578823 -2.877172)
-      (xy 5.58254 -2.893681)
-      (xy 5.598294 -2.902356)
-      (xy 5.632985 -2.905584)
-      (xy 5.66188 -2.905902)
-      (xy 5.744938 -2.905902)
-      (xy 5.97947 -2.905902)
-      (xy 6.002976 -2.912294)
-      (xy 6.008077 -2.920704)
-      (xy 6.02146 -2.92881)
-      (xy 6.055983 -2.934186)
-      (xy 6.089487 -2.935506)
-      (xy 6.13407 -2.933073)
-      (xy 6.16364 -2.926796)
-      (xy 6.170897 -2.920704)
-      (xy 6.183564 -2.909577)
-      (xy 6.207902 -2.905902)
-      (xy 6.235719 -2.900835)
-      (xy 6.244907 -2.8911)
-      (xy 6.257304 -2.879074)
-      (xy 6.27451 -2.876298)
-      (xy 6.296688 -2.874145)
-      (xy 6.302101 -2.863095)
-      (xy 6.291629 -2.836262)
-      (xy 6.282046 -2.817351)
-      (xy 6.264066 -2.789016)
-      (xy 6.243395 -2.781669)
-      (xy 6.211834 -2.788482)
-      (xy 6.138212 -2.801798)
-      (xy 6.075838 -2.79786)
-      (xy 6.030958 -2.77723)
-      (xy 6.025101 -2.771661)
-      (xy 6.006721 -2.747516)
-      (xy 6.006315 -2.724943)
-      (xy 6.018207 -2.697651)
-      (xy 6.033463 -2.672401)
-      (xy 6.0529 -2.659469)
-      (xy 6.086057 -2.654799)
-      (xy 6.120175 -2.65427)
-      (xy 6.200501 -2.65427)
-      (xy 6.200501 -2.535856)
-      (xy 6.133893 -2.535856)
-      (xy 6.094169 -2.532916)
-      (xy 6.070341 -2.525477)
-      (xy 6.067284 -2.521054)
-      (xy 6.055776 -2.507002)
-      (xy 6.050518 -2.506252)
-      (xy 6.020858 -2.493193)
-      (xy 5.997256 -2.460991)
-      (xy 5.985733 -2.420106)
-      (xy 5.987062 -2.396049)
-      (xy 5.994311 -2.364739)
-      (xy 5.998615 -2.350871)
-      (xy 5.998704 -2.350832)
-      (xy 6.011404 -2.344559)
-      (xy 6.033779 -2.33233)
-      (xy 6.064041 -2.322505)
-      (xy 6.107207 -2.316396)
-      (xy 6.154256 -2.314175)
-      (xy 6.196168 -2.316011)
-      (xy 6.223922 -2.322074)
-      (xy 6.230105 -2.328629)
-      (xy 6.23795 -2.344676)
-      (xy 6.256659 -2.341229)
-      (xy 6.278986 -2.322217)
-      (xy 6.297468 -2.2921)
-      (xy 6.313336 -2.252167)
-      (xy 6.316129 -2.232407)
-      (xy 6.801143 -2.232407)
-      (xy 6.804277 -2.557117)
-      (xy 6.805449 -2.683624)
-      (xy 6.806108 -2.784108)
-      (xy 6.806041 -2.862147)
-      (xy 6.805035 -2.92132)
-      (xy 6.802877 -2.965207)
-      (xy 6.799355 -2.997384)
-      (xy 6.794255 -3.021433)
-      (xy 6.787365 -3.04093)
-      (xy 6.778473 -3.059455)
-      (xy 6.773892 -3.068181)
-      (xy 6.726187 -3.131801)
-      (xy 6.674752 -3.167855)
-      (xy 6.610297 -3.201939)
-      (xy 4.206905 -3.201939)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 37569d0e-0c8a-4768-b17f-746c6692f82d))
-  (fp_poly
-    (pts
-      (xy 7.388484 -12.068199)
-      (xy 7.273901 -12.067926)
-      (xy 7.183128 -12.06729)
-      (xy 7.113268 -12.066143)
-      (xy 7.061423 -12.064336)
-      (xy 7.024696 -12.061721)
-      (xy 7.000191 -12.058149)
-      (xy 6.985011 -12.053472)
-      (xy 6.976258 -12.047542)
-      (xy 6.971035 -12.040211)
-      (xy 6.970719 -12.039626)
-      (xy 6.966098 -12.01581)
-      (xy 6.962235 -11.964132)
-      (xy 6.959181 -11.886323)
-      (xy 6.956991 -11.784115)
-      (xy 6.955718 -11.659242)
-      (xy 6.955396 -11.543763)
-      (xy 6.955396 -11.076532)
-      (xy 5.105163 -11.076532)
-      (xy 5.105163 -11.554632)
-      (xy 5.104838 -11.697836)
-      (xy 5.103813 -11.813515)
-      (xy 5.102014 -11.903741)
-      (xy 5.099367 -11.970585)
-      (xy 5.095798 -12.016121)
-      (xy 5.091232 -12.04242)
-      (xy 5.087401 -12.050494)
-      (xy 5.079463 -12.052189)
-      (xy 5.058649 -12.053781)
-      (xy 5.024218 -12.055274)
-      (xy 4.975432 -12.05667)
-      (xy 4.91155 -12.057972)
-      (xy 4.831833 -12.059182)
-      (xy 4.735541 -12.060303)
-      (xy 4.621933 -12.061338)
-      (xy 4.490271 -12.062288)
-      (xy 4.339814 -12.063158)
-      (xy 4.169822 -12.063949)
-      (xy 3.979556 -12.064663)
-      (xy 3.768277 -12.065304)
-      (xy 3.535243 -12.065875)
-      (xy 3.279715 -12.066377)
-      (xy 3.000954 -12.066813)
-      (xy 2.69822 -12.067186)
-      (xy 2.370772 -12.067499)
-      (xy 2.017872 -12.067754)
-      (xy 1.638779 -12.067954)
-      (xy 1.232753 -12.068101)
-      (xy 0.799055 -12.068199)
-      (xy 0.336945 -12.068248)
-      (xy 0.040486 -12.068256)
-      (xy -0.417498 -12.068254)
-      (xy -0.846808 -12.068244)
-      (xy -1.248374 -12.068222)
-      (xy -1.623126 -12.06818)
-      (xy -1.971993 -12.068115)
-      (xy -2.295906 -12.068022)
-      (xy -2.595794 -12.067894)
-      (xy -2.872587 -12.067727)
-      (xy -3.127215 -12.067515)
-      (xy -3.360608 -12.067253)
-      (xy -3.573696 -12.066935)
-      (xy -3.767408 -12.066557)
-      (xy -3.942674 -12.066114)
-      (xy -4.100425 -12.065599)
-      (xy -4.241589 -12.065008)
-      (xy -4.367098 -12.064335)
-      (xy -4.47788 -12.063576)
-      (xy -4.574865 -12.062724)
-      (xy -4.658984 -12.061774)
-      (xy -4.731166 -12.060722)
-      (xy -4.792341 -12.059562)
-      (xy -4.843438 -12.058289)
-      (xy -4.885389 -12.056897)
-      (xy -4.919122 -12.055381)
-      (xy -4.945567 -12.053736)
-      (xy -4.965654 -12.051956)
-      (xy -4.980314 -12.050037)
-      (xy -4.990475 -12.047973)
-      (xy -4.997068 -12.045758)
-      (xy -5.001022 -12.043388)
-      (xy -5.003268 -12.040858)
-      (xy -5.00399 -12.039626)
-      (xy -5.00861 -12.01581)
-      (xy -5.012474 -11.964132)
-      (xy -5.015528 -11.886323)
-      (xy -5.017718 -11.784115)
-      (xy -5.01899 -11.659242)
-      (xy -5.019313 -11.543763)
-      (xy -5.019313 -11.076532)
-      (xy -6.869546 -11.076532)
-      (xy -6.869546 -11.554632)
-      (xy -6.869871 -11.697836)
-      (xy -6.870896 -11.813515)
-      (xy -6.872694 -11.903741)
-      (xy -6.875341 -11.970585)
-      (xy -6.878911 -12.016121)
-      (xy -6.883477 -12.04242)
-      (xy -6.887308 -12.050494)
-      (xy -6.90077 -12.055522)
-      (xy -6.931461 -12.059611)
-      (xy -6.981391 -12.062827)
-      (xy -7.052571 -12.065234)
-      (xy -7.147009 -12.066897)
-      (xy -7.266718 -12.067881)
-      (xy -7.413708 -12.06825)
-      (xy -7.438757 -12.068256)
-      (xy -7.972443 -12.068256)
-      (xy -8.486729 -11.553814)
-      (xy -9.001014 -11.039371)
-      (xy -9.001014 10.971414)
-      (xy -7.971304 11.999576)
-      (xy 8.057669 11.999576)
-      (xy 8.579668 11.477577)
-      (xy 9.101666 10.955578)
-      (xy 9.101666 10.896669)
-      (xy 8.953648 10.896669)
-      (xy 7.999098 11.851557)
-      (xy 1.38998 11.850903)
-      (xy 0.862895 11.850849)
-      (xy 0.364612 11.850794)
-      (xy -0.105672 11.850732)
-      (xy -0.548758 11.850661)
-      (xy -0.965448 11.850577)
-      (xy -1.356544 11.850477)
-      (xy -1.722848 11.850357)
-      (xy -2.065162 11.850213)
-      (xy -2.384288 11.850042)
-      (xy -2.681028 11.84984)
-      (xy -2.956183 11.849604)
-      (xy -3.210557 11.84933)
-      (xy -3.44495 11.849015)
-      (xy -3.660165 11.848655)
-      (xy -3.857004 11.848246)
-      (xy -4.036268 11.847785)
-      (xy -4.19876 11.847269)
-      (xy -4.345282 11.846694)
-      (xy -4.476635 11.846055)
-      (xy -4.593622 11.845351)
-      (xy -4.697044 11.844576)
-      (xy -4.787704 11.843728)
-      (xy -4.866403 11.842804)
-      (xy -4.933943 11.841798)
-      (xy -4.991127 11.840709)
-      (xy -5.038755 11.839531)
-      (xy -5.077631 11.838263)
-      (xy -5.108557 11.8369)
-      (xy -5.132333 11.835438)
-      (xy -5.149763 11.833875)
-      (xy -5.161647 11.832206)
-      (xy -5.168789 11.830428)
-      (xy -5.171989 11.828538)
-      (xy -5.172051 11.826531)
-      (xy -5.169775 11.824405)
-      (xy -5.165964 11.822155)
-      (xy -5.165304 11.821804)
-      (xy -5.097492 11.774903)
-      (xy -5.029512 11.708895)
-      (xy -4.969893 11.632971)
-      (xy -4.935214 11.573866)
-      (xy -4.91602 11.531947)
-      (xy -4.903786 11.494728)
-      (xy -4.896978 11.453372)
-      (xy -4.894061 11.399041)
-      (xy -4.893497 11.333492)
-      (xy -4.894302 11.259945)
-      (xy -4.897777 11.206768)
-      (xy -4.905505 11.164743)
-      (xy -4.919073 11.124656)
-      (xy -4.936119 11.085793)
-      (xy -4.997214 10.986779)
-      (xy -5.08117 10.90001)
-      (xy -5.181914 10.831451)
-      (xy -5.208509 10.818092)
-      (xy -5.235117 10.805943)
-      (xy -5.259491 10.796521)
-      (xy -5.285799 10.789427)
-      (xy -5.318206 10.784262)
-      (xy -5.360877 10.780628)
-      (xy -5.417979 10.778127)
-      (xy -5.493676 10.776358)
-      (xy -5.592136 10.774924)
-      (xy -5.669272 10.773995)
-      (xy -5.789974 10.772885)
-      (xy -5.884046 10.772806)
-      (xy -5.95445 10.773871)
-      (xy -6.004144 10.776195)
-      (xy -6.03609 10.779888)
-      (xy -6.053248 10.785064)
-      (xy -6.057595 10.788797)
-      (xy -6.063136 10.811625)
-      (xy -6.067419 10.855975)
-      (xy -6.069771 10.913773)
-      (xy -6.070018 10.937859)
-      (xy -6.06964 11.000416)
-      (xy -6.067156 11.039924)
-      (xy -6.060941 11.062931)
-      (xy -6.049371 11.075988)
-      (xy -6.033679 11.084354)
-      (xy -5.996657 11.093553)
-      (xy -5.971594 11.080259)
-      (xy -5.957129 11.042527)
-      (xy -5.951902 10.978416)
-      (xy -5.95183 10.967514)
-      (xy -5.95183 10.871595)
-      (xy -5.652092 10.877087)
-      (xy -5.549751 10.879136)
-      (xy -5.472082 10.881398)
-      (xy -5.414152 10.884441)
-      (xy -5.371032 10.888832)
-      (xy -5.33779 10.895139)
-      (xy -5.309497 10.903928)
-      (xy -5.281221 10.915766)
-      (xy -5.269664 10.921085)
-      (xy -5.171464 10.981169)
-      (xy -5.094832 11.057365)
-      (xy -5.040248 11.145614)
-      (xy -5.008195 11.241861)
-      (xy -4.999154 11.342045)
-      (xy -5.013608 11.44211)
-      (xy -5.052037 11.537997)
-      (xy -5.114924 11.625649)
-      (xy -5.179086 11.684042)
-      (xy -5.222926 11.714282)
-      (xy -5.267935 11.737396)
-      (xy -5.318865 11.754284)
-      (xy -5.380465 11.765844)
-      (xy -5.457488 11.772975)
-      (xy -5.554684 11.776577)
-      (xy -5.673281 11.777548)
-      (xy -5.95183 11.777548)
-      (xy -5.95183 11.697348)
-      (xy -5.953888 11.634857)
-      (xy -5.961723 11.59644)
-      (xy -5.977827 11.576752)
-      (xy -6.004691 11.570448)
-      (xy -6.011037 11.570322)
-      (xy -6.037052 11.573377)
-      (xy -6.054188 11.585854)
-      (xy -6.064238 11.612714)
-      (xy -6.068992 11.658922)
-      (xy -6.070242 11.72944)
-      (xy -6.070245 11.734353)
-      (xy -6.070245 11.851557)
-      (xy -6.320766 11.851557)
-      (xy -6.329278 11.577723)
-      (xy -6.418089 11.577723)
-      (xy -6.422484 11.67846)
-      (xy -6.42688 11.779198)
-      (xy -6.733323 11.774672)
-      (xy -6.836688 11.772995)
-      (xy -6.91527 11.771071)
-      (xy -6.973889 11.768365)
-      (xy -7.017364 11.764338)
-      (xy -7.050514 11.758455)
-      (xy -7.078161 11.750179)
-      (xy -7.105122 11.738972)
-      (xy -7.121177 11.731472)
-      (xy -7.217998 11.670844)
-      (xy -7.293683 11.593459)
-      (xy -7.347249 11.50349)
-      (xy -7.377712 11.405108)
-      (xy -7.38409 11.302484)
-      (xy -7.365398 11.19979)
-      (xy -7.320656 11.101197)
-      (xy -7.282371 11.047525)
-      (xy -7.233138 10.994838)
-      (xy -7.179614 10.953474)
-      (xy -7.117694 10.922237)
-      (xy -7.043274 10.899933)
-      (xy -6.952249 10.885364)
-      (xy -6.840515 10.877337)
-      (xy -6.703967 10.874654)
-      (xy -6.688813 10.874634)
-      (xy -6.42549 10.874634)
-      (xy -6.42549 10.976663)
-      (xy -6.422431 11.040106)
-      (xy -6.411647 11.077945)
-      (xy -6.390724 11.093703)
-      (xy -6.35725 11.0909)
-      (xy -6.34889 11.088439)
-      (xy -6.336228 11.081845)
-      (xy -6.32836 11.068053)
-      (xy -6.324446 11.041442)
-      (xy -6.323646 10.996389)
-      (xy -6.325072 10.928983)
-      (xy -6.329278 10.778422)
-      (xy -7.098975 10.778422)
-      (xy -7.183929 10.820139)
-      (xy -7.289311 10.887285)
-      (xy -7.376139 10.97398)
-      (xy -7.442154 11.075913)
-      (xy -7.485098 11.188773)
-      (xy -7.502712 11.308249)
-      (xy -7.495542 11.414997)
-      (xy -7.461081 11.539622)
-      (xy -7.404046 11.649211)
-      (xy -7.326628 11.740404)
-      (xy -7.24205 11.803555)
-      (xy -7.172984 11.844156)
-      (xy -7.54268 11.848122)
-      (xy -7.912377 11.852089)
-      (xy -8.390087 11.374548)
-      (xy -8.867797 10.897008)
-      (xy -8.867797 -10.965686)
-      (xy -8.382953 -11.450363)
-      (xy -7.89811 -11.93504)
-      (xy -7.017564 -11.93504)
-      (xy -7.017564 -11.46138)
-      (xy -7.017491 -11.330274)
-      (xy -7.017143 -11.225558)
-      (xy -7.016334 -11.144017)
-      (xy -7.014873 -11.082437)
-      (xy -7.012571 -11.037603)
-      (xy -7.009239 -11.006301)
-      (xy -7.004689 -10.985318)
-      (xy -6.998731 -10.971438)
-      (xy -6.991176 -10.961448)
-      (xy -6.987961 -10.958117)
-      (xy -6.98153 -10.952332)
-      (xy -6.973236 -10.947354)
-      (xy -6.960947 -10.943123)
-      (xy -6.942536 -10.939578)
-      (xy -6.915872 -10.936658)
-      (xy -6.878825 -10.934302)
-      (xy -6.829266 -10.932451)
-      (xy -6.765066 -10.931043)
-      (xy -6.684094 -10.930018)
-      (xy -6.58422 -10.929315)
-      (xy -6.463316 -10.928873)
-      (xy -6.319252 -10.928633)
-      (xy -6.149897 -10.928533)
-      (xy -5.953123 -10.928513)
-      (xy -5.947723 -10.928513)
-      (xy -5.747846 -10.928573)
-      (xy -5.575492 -10.928785)
-      (xy -5.428579 -10.929194)
-      (xy -5.305028 -10.929847)
-      (xy -5.202756 -10.930789)
-      (xy -5.119683 -10.932066)
-      (xy -5.053728 -10.933725)
-      (xy -5.00281 -10.93581)
-      (xy -4.964848 -10.938369)
-      (xy -4.937762 -10.941446)
-      (xy -4.91947 -10.945089)
-      (xy -4.907891 -10.949343)
-      (xy -4.904191 -10.951555)
-      (xy -4.895167 -10.958399)
-      (xy -4.887965 -10.967015)
-      (xy -4.882381 -10.980546)
-      (xy -4.878207 -11.002139)
-      (xy -4.87524 -11.034938)
-      (xy -4.873272 -11.082088)
-      (xy -4.8721 -11.146734)
-      (xy -4.871516 -11.232022)
-      (xy -4.871316 -11.341096)
-      (xy -4.871294 -11.454818)
-      (xy -4.871294 -11.93504)
-      (xy 4.957144 -11.93504)
-      (xy 4.957144 -11.46138)
-      (xy 4.957218 -11.330274)
-      (xy 4.957565 -11.225558)
-      (xy 4.958375 -11.144017)
-      (xy 4.959836 -11.082437)
-      (xy 4.962138 -11.037603)
-      (xy 4.965469 -11.006301)
-      (xy 4.970019 -10.985318)
-      (xy 4.975978 -10.971438)
-      (xy 4.983533 -10.961448)
-      (xy 4.986748 -10.958117)
-      (xy 4.993179 -10.952332)
-      (xy 5.001473 -10.947354)
-      (xy 5.013761 -10.943123)
-      (xy 5.032172 -10.939578)
-      (xy 5.058837 -10.936658)
-      (xy 5.095883 -10.934302)
-      (xy 5.145442 -10.932451)
-      (xy 5.209643 -10.931043)
-      (xy 5.290615 -10.930018)
-      (xy 5.390488 -10.929315)
-      (xy 5.511392 -10.928873)
-      (xy 5.655457 -10.928633)
-      (xy 5.824811 -10.928533)
-      (xy 6.021586 -10.928513)
-      (xy 6.026986 -10.928513)
-      (xy 6.226863 -10.928573)
-      (xy 6.399217 -10.928785)
-      (xy 6.546129 -10.929194)
-      (xy 6.669681 -10.929847)
-      (xy 6.771953 -10.930789)
-      (xy 6.855026 -10.932066)
-      (xy 6.92098 -10.933725)
-      (xy 6.971898 -10.93581)
-      (xy 7.00986 -10.938369)
-      (xy 7.036947 -10.941446)
-      (xy 7.055239 -10.945089)
-      (xy 7.066818 -10.949343)
-      (xy 7.070518 -10.951555)
-      (xy 7.079542 -10.958399)
-      (xy 7.086743 -10.967015)
-      (xy 7.092328 -10.980546)
-      (xy 7.096501 -11.002139)
-      (xy 7.099469 -11.034938)
-      (xy 7.101436 -11.082088)
-      (xy 7.102609 -11.146734)
-      (xy 7.103192 -11.232022)
-      (xy 7.103393 -11.341096)
-      (xy 7.103415 -11.454818)
-      (xy 7.103415 -11.93504)
-      (xy 7.54377 -11.934343)
-      (xy 7.984126 -11.933646)
-      (xy 8.953648 -10.97605)
-      (xy 8.953648 10.896669)
-      (xy 9.101666 10.896669)
-      (xy 9.101666 -11.038546)
-      (xy 8.587586 -11.553401)
-      (xy 8.073505 -12.068256)
-      (xy 7.529773 -12.068256)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d4aa9b0c-8121-4e28-8a48-ec6754d82ee0))
-  (fp_poly
-    (pts
-      (xy 4.32482 1.864537)
-      (xy 4.12467 1.904232)
-      (xy 3.930123 1.969348)
-      (xy 3.743787 2.05969)
-      (xy 3.568267 2.175067)
-      (xy 3.406171 2.315286)
-      (xy 3.395166 2.326257)
-      (xy 3.255578 2.486398)
-      (xy 3.141643 2.658198)
-      (xy 3.052942 2.839297)
-      (xy 2.989053 3.027336)
-      (xy 2.949557 3.219954)
-      (xy 2.934031 3.414792)
-      (xy 2.942058 3.60949)
-      (xy 2.973215 3.801687)
-      (xy 3.027082 3.989025)
-      (xy 3.103239 4.169142)
-      (xy 3.201265 4.33968)
-      (xy 3.320741 4.498278)
-      (xy 3.461245 4.642577)
-      (xy 3.622356 4.770216)
-      (xy 3.803656 4.878836)
-      (xy 3.854405 4.903839)
-      (xy 4.032734 4.973412)
-      (xy 4.22468 5.022004)
-      (xy 4.42199 5.04824)
-      (xy 4.616413 5.050748)
-      (xy 4.697376 5.044154)
-      (xy 4.817099 5.02614)
-      (xy 4.940951 4.999552)
-      (xy 5.058372 4.967041)
-      (xy 5.158803 4.931256)
-      (xy 5.175472 4.924139)
-      (xy 5.23838 4.896345)
-      (xy 5.23838 5.172075)
-      (xy 5.239328 5.286945)
-      (xy 5.242895 5.376621)
-      (xy 5.250158 5.445474)
-      (xy 5.2622 5.497873)
-      (xy 5.280099 5.538188)
-      (xy 5.304937 5.57079)
-      (xy 5.337793 5.600049)
-      (xy 5.345651 5.606056)
-      (xy 5.393799 5.642175)
-      (xy 6.089487 5.645765)
-      (xy 6.252994 5.646523)
-      (xy 6.389537 5.646911)
-      (xy 6.501757 5.646854)
-      (xy 6.592293 5.64628)
-      (xy 6.663784 5.645114)
-      (xy 6.718869 5.643282)
-      (xy 6.760189 5.640711)
-      (xy 6.790381 5.637326)
-      (xy 6.812086 5.633054)
-      (xy 6.827943 5.62782)
-      (xy 6.834322 5.62491)
-      (xy 6.875607 5.596658)
-      (xy 6.915714 5.557612)
-      (xy 6.923134 5.548462)
-      (xy 6.962797 5.496461)
-      (xy 6.962797 5.180147)
-      (xy 6.864978 5.180147)
-      (xy 6.864405 5.264316)
-      (xy 6.863144 5.331569)
-      (xy 6.861243 5.377197)
-      (xy 6.859577 5.393651)
-      (xy 6.841128 5.443145)
-      (xy 6.808873 5.48978)
-      (xy 6.770578 5.524021)
-      (xy 6.743964 5.535583)
-      (xy 6.72238 5.537011)
-      (xy 6.674523 5.538425)
-      (xy 6.603727 5.539782)
-      (xy 6.513323 5.541037)
-      (xy 6.406642 5.542147)
-      (xy 6.287018 5.543069)
-      (xy 6.157781 5.543758)
-      (xy 6.107514 5.543947)
-      (xy 5.950933 5.544289)
-      (xy 5.821326 5.544124)
-      (xy 5.716066 5.543378)
-      (xy 5.632526 5.541974)
-      (xy 5.568079 5.539839)
-      (xy 5.520098 5.536897)
-      (xy 5.485957 5.533074)
-      (xy 5.463027 5.528294)
-      (xy 5.454466 5.525323)
-      (xy 5.423633 5.511167)
-      (xy 5.400073 5.495157)
-      (xy 5.382811 5.473366)
-      (xy 5.370874 5.441868)
-      (xy 5.363288 5.396737)
-      (xy 5.359079 5.334047)
-      (xy 5.357274 5.249872)
-      (xy 5.356899 5.140286)
-      (xy 5.356901 5.131917)
-      (xy 5.357008 4.828072)
-      (xy 5.419809 4.787922)
-      (xy 5.482611 4.747771)
-      (xy 5.486589 5.080258)
-      (xy 5.490567 5.412746)
-      (xy 5.570013 5.412746)
-      (xy 5.603306 5.413109)
-      (xy 5.626754 5.411377)
-      (xy 5.644677 5.403323)
-      (xy 5.661396 5.384718)
-      (xy 5.681232 5.351332)
-      (xy 5.708505 5.298937)
-      (xy 5.730951 5.255233)
-      (xy 5.753436 5.219941)
-      (xy 5.77538 5.197813)
-      (xy 5.779057 5.195914)
-      (xy 5.798473 5.177108)
-      (xy 5.800851 5.166797)
-      (xy 5.810448 5.144103)
-      (xy 5.834592 5.111524)
-      (xy 5.846752 5.098071)
-      (xy 5.882015 5.056766)
-      (xy 5.911911 5.014482)
-      (xy 5.917061 5.005695)
-      (xy 5.926366 4.990003)
-      (xy 5.933055 4.984529)
-      (xy 5.937673 4.992748)
-      (xy 5.940767 5.018137)
-      (xy 5.942883 5.064173)
-      (xy 5.944568 5.134332)
-      (xy 5.945554 5.187017)
-      (xy 5.94964 5.412746)
-      (xy 6.11169 5.412746)
-      (xy 6.11169 4.687454)
-      (xy 6.042269 4.687454)
-      (xy 5.999923 4.689782)
-      (xy 5.969277 4.700542)
-      (xy 5.938882 4.725402)
-      (xy 5.915157 4.750362)
-      (xy 5.88071 4.791177)
-      (xy 5.853984 4.828675)
-      (xy 5.844327 4.846575)
-      (xy 5.825842 4.872348)
-      (xy 5.808618 4.879879)
-      (xy 5.790003 4.892105)
-      (xy 5.786049 4.907899)
-      (xy 5.775746 4.935478)
-      (xy 5.763846 4.944439)
-      (xy 5.74415 4.964567)
-      (xy 5.741643 4.976245)
-      (xy 5.732131 5.003519)
-      (xy 5.712039 5.031307)
-      (xy 5.682436 5.063083)
-      (xy 5.682436 4.687454)
-      (xy 5.563233 4.687454)
-      (xy 5.656139 4.598805)
-      (xy 5.746359 4.512719)
-      (xy 5.557701 4.512719)
-      (xy 5.553791 4.526336)
-      (xy 5.547331 4.534559)
-      (xy 5.525643 4.55609)
-      (xy 5.488578 4.588466)
-      (xy 5.445606 4.623519)
-      (xy 5.403008 4.656264)
-      (xy 5.377977 4.672047)
-      (xy 5.365355 4.672878)
-      (xy 5.359984 4.660769)
-      (xy 5.359354 4.657144)
-      (xy 5.363666 4.622735)
-      (xy 5.379007 4.58915)
-      (xy 5.415679 4.553561)
-      (xy 5.468363 4.525048)
-      (xy 5.523471 4.510487)
-      (xy 5.535754 4.509832)
-      (xy 5.557701 4.512719)
-      (xy 5.746359 4.512719)
-      (xy 5.749044 4.510157)
-      (xy 6.25574 4.513695)
-      (xy 6.762437 4.517233)
-      (xy 6.81081 4.565596)
-      (xy 6.859184 4.61396)
-      (xy 6.863867 4.979892)
-      (xy 6.864815 5.083769)
-      (xy 6.864978 5.180147)
-      (xy 6.962797 5.180147)
-      (xy 6.962797 4.559334)
-      (xy 6.922927 4.507062)
-      (xy 6.902118 4.480787)
-      (xy 6.881703 4.459523)
-      (xy 6.858437 4.442741)
-      (xy 6.829077 4.42991)
-      (xy 6.79038 4.4205)
-      (xy 6.739101 4.413982)
-      (xy 6.671997 4.409826)
-      (xy 6.585825 4.4075)
-      (xy 6.47734 4.406476)
-      (xy 6.343299 4.406224)
-      (xy 6.305761 4.406219)
-      (xy 5.830822 4.406219)
-      (xy 5.880443 4.328509)
-      (xy 5.980581 4.147521)
-      (xy 6.056107 3.955551)
-      (xy 6.108581 3.748359)
-      (xy 6.121473 3.673527)
-      (xy 6.135317 3.524759)
-      (xy 6.135017 3.456653)
-      (xy 6.019649 3.456653)
-      (xy 6.012116 3.586599)
-      (xy 5.995464 3.714093)
-      (xy 5.974211 3.814314)
-      (xy 5.926316 3.968511)
-      (xy 5.864719 4.109759)
-      (xy 5.783899 4.250292)
-      (xy 5.762901 4.282463)
-      (xy 5.680556 4.406219)
-      (xy 5.554217 4.406219)
-      (xy 5.463068 4.410461)
-      (xy 5.394412 4.424818)
-      (xy 5.342146 4.451736)
-      (xy 5.300168 4.493663)
-      (xy 5.285757 4.513871)
-      (xy 5.25965 4.564044)
-      (xy 5.245374 4.622559)
-      (xy 5.240835 4.668738)
-      (xy 5.234707 4.764986)
-      (xy 5.143778 4.806215)
-      (xy 4.954562 4.876342)
-      (xy 4.757182 4.91988)
-      (xy 4.556282 4.936293)
-      (xy 4.356506 4.925044)
-      (xy 4.257528 4.908682)
-      (xy 4.054857 4.854319)
-      (xy 3.869384 4.776717)
-      (xy 3.698182 4.674352)
-      (xy 3.538325 4.545698)
-      (xy 3.509616 4.518755)
-      (xy 3.368225 4.363528)
-      (xy 3.252343 4.195273)
-      (xy 3.162233 4.016416)
-      (xy 3.098156 3.829384)
-      (xy 3.060374 3.636605)
-      (xy 3.049147 3.440504)
-      (xy 3.064737 3.243509)
-      (xy 3.107405 3.048046)
-      (xy 3.177412 2.856542)
-      (xy 3.27502 2.671425)
-      (xy 3.305586 2.623684)
-      (xy 3.428621 2.465113)
-      (xy 3.573792 2.324436)
-      (xy 3.738305 2.203583)
-      (xy 3.919368 2.104486)
-      (xy 4.114185 2.029074)
-      (xy 4.202249 2.004218)
-      (xy 4.314964 1.9837)
-      (xy 4.445168 1.97269)
-      (xy 4.582312 1.971187)
-      (xy 4.715849 1.979192)
-      (xy 4.835232 1.996704)
-      (xy 4.868333 2.004218)
-      (xy 5.06906 2.068168)
-      (xy 5.254069 2.15458)
-      (xy 5.420681 2.262038)
-      (xy 5.528762 2.352596)
-      (xy 5.623228 2.440965)
-      (xy 5.623228 2.684962)
-      (xy 5.624142 2.791169)
-      (xy 5.627706 2.872574)
-      (xy 5.635154 2.933948)
-      (xy 5.647721 2.980059)
-      (xy 5.666641 3.015676)
-      (xy 5.693147 3.045568)
-      (xy 5.722963 3.070341)
-      (xy 5.760427 3.093639)
-      (xy 5.804156 3.107911)
-      (xy 5.864724 3.11634)
-      (xy 5.87986 3.117611)
-      (xy 5.985594 3.125858)
-      (xy 6.005234 3.229471)
-      (xy 6.017532 3.334271)
-      (xy 6.019649 3.456653)
-      (xy 6.135017 3.456653)
-      (xy 6.1346 3.362134)
-      (xy 6.119427 3.19751)
-      (xy 6.117114 3.181365)
-      (xy 6.107792 3.118457)
-      (xy 6.632879 3.118457)
-      (xy 6.771423 3.118415)
-      (xy 6.883591 3.118167)
-      (xy 6.97261 3.117524)
-      (xy 7.041709 3.116301)
-      (xy 7.094115 3.114311)
-      (xy 7.133056 3.111367)
-      (xy 7.16176 3.107283)
-      (xy 7.183454 3.101872)
-      (xy 7.201366 3.094947)
-      (xy 7.218724 3.086322)
-      (xy 7.222421 3.084372)
-      (xy 7.285287 3.036826)
-      (xy 7.321569 2.984683)
-      (xy 7.331483 2.965292)
-      (xy 7.339266 2.946508)
-      (xy 7.345136 2.924714)
-      (xy 7.349312 2.89629)
-      (xy 7.352012 2.85762)
-      (xy 7.353453 2.805084)
-      (xy 7.353855 2.735067)
-      (xy 7.353436 2.643948)
-      (xy 7.352413 2.528111)
-      (xy 7.352072 2.493192)
-      (xy 7.236632 2.493192)
-      (xy 7.23645 2.615251)
-      (xy 7.235772 2.711247)
-      (xy 7.234395 2.784719)
-      (xy 7.232119 2.839205)
-      (xy 7.228741 2.878245)
-      (xy 7.224061 2.905377)
-      (xy 7.217876 2.92414)
-      (xy 7.211433 2.935928)
-      (xy 7.197294 2.955822)
-      (xy 7.181536 2.972005)
-      (xy 7.161156 2.984836)
-      (xy 7.133155 2.994675)
-      (xy 7.09453 3.001881)
-      (xy 7.042281 3.006812)
-      (xy 6.973407 3.009827)
-      (xy 6.884906 3.011287)
-      (xy 6.773779 3.011549)
-      (xy 6.637023 3.010972)
-      (xy 6.586717 3.010665)
-      (xy 6.07742 3.007443)
-      (xy 6.075215 3.000905)
-      (xy 5.948869 3.000905)
-      (xy 5.937216 3.013495)
-      (xy 5.907483 3.013905)
-      (xy 5.867507 3.004258)
-      (xy 5.825126 2.986677)
-      (xy 5.788179 2.963287)
-      (xy 5.778648 2.954787)
-      (xy 5.759708 2.934951)
-      (xy 5.746954 2.915887)
-      (xy 5.738984 2.891306)
-      (xy 5.734397 2.854918)
-      (xy 5.731791 2.800435)
-      (xy 5.730132 2.737063)
-      (xy 5.726021 2.563387)
-      (xy 5.792944 2.667)
-      (xy 5.825975 2.722216)
-      (xy 5.860408 2.786508)
-      (xy 5.893076 2.853086)
-      (xy 5.920806 2.915162)
-      (xy 5.94043 2.965946)
-      (xy 5.948776 2.99865)
-      (xy 5.948869 3.000905)
-      (xy 6.075215 3.000905)
-      (xy 6.044018 2.90841)
-      (xy 5.974415 2.743026)
-      (xy 5.877059 2.576156)
-      (xy 5.81571 2.489378)
-      (xy 5.726894 2.370963)
-      (xy 5.726868 2.247384)
-      (xy 5.731368 2.155553)
-      (xy 5.746031 2.087787)
-      (xy 5.772536 2.039793)
-      (xy 5.812563 2.007273)
-      (xy 5.822734 2.00206)
-      (xy 5.851071 1.995721)
-      (xy 5.904922 1.990254)
-      (xy 5.980375 1.985665)
-      (xy 6.073516 1.981955)
-      (xy 6.180433 1.979129)
-      (xy 6.297214 1.977191)
-      (xy 6.419944 1.976143)
-      (xy 6.544713 1.97599)
-      (xy 6.667606 1.976736)
-      (xy 6.784711 1.978383)
-      (xy 6.892116 1.980936)
-      (xy 6.985907 1.984398)
-      (xy 7.062172 1.988772)
-      (xy 7.116998 1.994063)
-      (xy 7.146472 2.000274)
-      (xy 7.147657 2.000831)
-      (xy 7.172885 2.014534)
-      (xy 7.192828 2.028894)
-      (xy 7.208107 2.047349)
-      (xy 7.219343 2.073337)
-      (xy 7.227157 2.110296)
-      (xy 7.23217 2.161664)
-      (xy 7.235004 2.230877)
-      (xy 7.23628 2.321375)
-      (xy 7.236619 2.436595)
-      (xy 7.236632 2.493192)
-      (xy 7.352072 2.493192)
-      (xy 7.351954 2.481085)
-      (xy 7.347646 2.043091)
-      (xy 7.308261 1.983612)
-      (xy 7.292076 1.959365)
-      (xy 7.276626 1.939028)
-      (xy 7.259298 1.922257)
-      (xy 7.237476 1.908708)
-      (xy 7.208544 1.898039)
-      (xy 7.16989 1.889905)
-      (xy 7.118896 1.883962)
-      (xy 7.052949 1.879868)
-      (xy 6.969433 1.877278)
-      (xy 6.865733 1.875849)
-      (xy 6.739235 1.875237)
-      (xy 6.587323 1.875099)
-      (xy 6.482465 1.8751)
-      (xy 6.316353 1.875097)
-      (xy 6.177185 1.875302)
-      (xy 6.062303 1.87604)
-      (xy 5.969048 1.877634)
-      (xy 5.894761 1.880407)
-      (xy 5.836782 1.884685)
-      (xy 5.792454 1.890789)
-      (xy 5.759117 1.899044)
-      (xy 5.734112 1.909774)
-      (xy 5.714781 1.923303)
-      (xy 5.698464 1.939953)
-      (xy 5.682502 1.960049)
-      (xy 5.672099 1.973752)
-      (xy 5.649672 2.007617)
-      (xy 5.635775 2.043457)
-      (xy 5.62757 2.091158)
-      (xy 5.623228 2.144023)
-      (xy 5.615827 2.260017)
-      (xy 5.497412 2.170958)
-      (xy 5.318385 2.054092)
-      (xy 5.129319 1.963801)
-      (xy 4.932823 1.899893)
-      (xy 4.731504 1.862174)
-      (xy 4.527967 1.850453)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 32a6e9d7-a981-4f4f-a38c-9dc4a8c9ba00))
-  (fp_poly
-    (pts
-      (xy 2.210769 -10.269513)
-      (xy 2.144597 -10.202001)
-      (xy 2.097367 -10.151138)
-      (xy 2.06631 -10.113449)
-      (xy 2.048656 -10.085459)
-      (xy 2.041635 -10.063694)
-      (xy 2.041177 -10.056778)
-      (xy 2.044516 -10.029027)
-      (xy 2.060073 -10.014452)
-      (xy 2.096161 -10.005799)
-      (xy 2.100384 -10.005113)
-      (xy 2.1374 -9.995962)
-      (xy 2.158046 -9.984583)
-      (xy 2.159592 -9.981019)
-      (xy 2.171991 -9.969134)
-      (xy 2.189196 -9.966392)
-      (xy 2.213248 -9.960193)
-      (xy 2.218799 -9.95159)
-      (xy 2.230572 -9.937994)
-      (xy 2.238233 -9.936788)
-      (xy 2.260521 -9.926414)
-      (xy 2.290543 -9.901538)
-      (xy 2.318781 -9.871532)
-      (xy 2.335717 -9.845766)
-      (xy 2.337214 -9.839333)
-      (xy 2.347985 -9.820335)
-      (xy 2.365965 -9.804186)
-      (xy 2.387354 -9.776324)
-      (xy 2.402747 -9.734625)
-      (xy 2.404258 -9.726986)
-      (xy 2.413634 -9.688532)
-      (xy 2.424834 -9.664452)
-      (xy 2.427313 -9.662157)
-      (xy 2.434979 -9.643423)
-      (xy 2.439368 -9.605628)
-      (xy 2.440481 -9.559132)
-      (xy 2.438318 -9.514297)
-      (xy 2.432879 -9.481483)
-      (xy 2.427313 -9.471325)
-      (xy 2.416482 -9.452581)
-      (xy 2.406155 -9.416191)
-      (xy 2.40381 -9.403843)
-      (xy 2.394581 -9.366878)
-      (xy 2.383643 -9.346258)
-      (xy 2.380319 -9.344713)
-      (xy 2.367874 -9.332937)
-      (xy 2.366818 -9.325515)
-      (xy 2.356636 -9.304907)
-      (xy 2.331335 -9.273796)
-      (xy 2.298783 -9.240171)
-      (xy 2.266846 -9.212019)
-      (xy 2.243393 -9.19733)
-      (xy 2.239945 -9.196695)
-      (xy 2.22077 -9.185921)
-      (xy 2.204749 -9.168134)
-      (xy 2.172341 -9.145141)
-      (xy 2.117101 -9.13038)
-      (xy 2.11267 -9.12974)
-      (xy 2.041177 -9.119907)
-      (xy 2.041177 -9.025084)
-      (xy 2.041849 -8.973827)
-      (xy 2.045616 -8.945434)
-      (xy 2.055107 -8.933171)
-      (xy 2.07295 -8.930301)
-      (xy 2.078182 -8.930261)
-      (xy 2.106016 -8.926384)
-      (xy 2.115186 -8.918951)
-      (xy 2.127241 -8.907926)
-      (xy 2.156537 -8.891107)
-      (xy 2.192772 -8.873553)
-      (xy 2.225647 -8.860324)
-      (xy 2.242855 -8.856252)
-      (xy 2.258793 -8.845624)
-      (xy 2.283885 -8.819849)
-      (xy 2.310392 -8.78809)
-      (xy 2.330574 -8.759512)
-      (xy 2.336978 -8.744805)
-      (xy 2.347988 -8.725305)
-      (xy 2.367211 -8.70795)
-      (xy 2.389862 -8.678767)
-      (xy 2.40515 -8.635965)
-      (xy 2.406107 -8.630673)
-      (xy 2.414835 -8.59499)
-      (xy 2.425374 -8.575979)
-      (xy 2.427917 -8.575016)
-      (xy 2.434492 -8.561516)
-      (xy 2.439142 -8.526192)
-      (xy 2.440827 -8.478804)
-      (xy 2.438736 -8.428528)
-      (xy 2.433196 -8.394106)
-      (xy 2.426025 -8.382592)
-      (xy 2.414192 -8.370133)
-      (xy 2.411224 -8.351525)
-      (xy 2.400121 -8.302143)
-      (xy 2.370932 -8.244121)
-      (xy 2.329835 -8.185776)
-      (xy 2.283008 -8.135427)
-      (xy 2.23663 -8.101392)
-      (xy 2.220261 -8.09442)
-      (xy 2.195577 -8.081138)
-      (xy 2.189196 -8.070756)
-      (xy 2.176523 -8.060376)
-      (xy 2.152191 -8.056951)
-      (xy 2.124374 -8.051884)
-      (xy 2.115186 -8.042149)
-      (xy 2.102519 -8.031022)
-      (xy 2.078182 -8.027347)
-      (xy 2.05829 -8.02566)
-      (xy 2.04721 -8.01614)
-      (xy 2.04237 -7.992099)
-      (xy 2.041198 -7.946849)
-      (xy 2.041177 -7.931135)
-      (xy 2.041826 -7.879416)
-      (xy 2.045487 -7.850609)
-      (xy 2.054734 -7.838026)
-      (xy 2.072138 -7.834979)
-      (xy 2.078182 -7.834923)
-      (xy 2.106002 -7.830084)
-      (xy 2.115186 -7.820792)
-      (xy 2.128126 -7.809047)
-      (xy 2.159967 -7.79839)
-      (xy 2.166993 -7.796942)
-      (xy 2.201146 -7.787251)
-      (xy 2.218319 -7.775948)
-      (xy 2.218799 -7.774068)
-      (xy 2.230254 -7.761447)
-      (xy 2.23474 -7.760914)
-      (xy 2.255478 -7.750662)
-      (xy 2.28497 -7.725934)
-      (xy 2.314099 -7.695773)
-      (xy 2.333749 -7.669219)
-      (xy 2.337214 -7.659279)
-      (xy 2.348089 -7.639789)
-      (xy 2.365548 -7.624332)
-      (xy 2.387067 -7.597006)
-      (xy 2.402825 -7.55591)
-      (xy 2.40423 -7.54932)
-      (xy 2.414153 -7.511431)
-      (xy 2.425498 -7.488019)
-      (xy 2.427703 -7.486042)
-      (xy 2.435089 -7.467529)
-      (xy 2.439362 -7.429932)
-      (xy 2.440509 -7.383597)
-      (xy 2.438516 -7.338868)
-      (xy 2.433367 -7.306093)
-      (xy 2.42797 -7.295857)
-      (xy 2.417703 -7.277393)
-      (xy 2.407892 -7.241122)
-      (xy 2.405592 -7.228375)
-      (xy 2.396438 -7.191239)
-      (xy 2.385073 -7.170445)
-      (xy 2.381445 -7.168839)
-      (xy 2.367766 -7.157136)
-      (xy 2.36669 -7.150337)
-      (xy 2.356543 -7.128291)
-      (xy 2.331516 -7.096126)
-      (xy 2.299431 -7.062055)
-      (xy 2.268111 -7.034291)
-      (xy 2.245379 -7.021048)
-      (xy 2.243338 -7.020821)
-      (xy 2.221373 -7.009932)
-      (xy 2.204749 -6.99226)
-      (xy 2.172341 -6.969266)
-      (xy 2.117101 -6.954506)
-      (xy 2.11267 -6.953866)
-      (xy 2.041177 -6.944033)
-      (xy 2.041177 -6.84921)
-      (xy 2.041849 -6.797953)
-      (xy 2.045616 -6.76956)
-      (xy 2.055107 -6.757297)
-      (xy 2.07295 -6.754427)
-      (xy 2.078182 -6.754387)
-      (xy 2.105999 -6.74932)
-      (xy 2.115186 -6.739585)
-      (xy 2.127175 -6.726453)
-      (xy 2.137389 -6.724783)
-      (xy 2.157087 -6.716791)
-      (xy 2.159592 -6.709981)
-      (xy 2.171917 -6.697737)
-      (xy 2.187612 -6.69518)
-      (xy 2.215191 -6.684877)
-      (xy 2.224152 -6.672977)
-      (xy 2.244546 -6.653329)
-      (xy 2.256667 -6.650774)
-      (xy 2.282804 -6.639543)
-      (xy 2.311784 -6.613315)
-      (xy 2.332656 -6.583285)
-      (xy 2.336722 -6.568931)
-      (xy 2.347942 -6.549415)
-      (xy 2.367211 -6.532076)
-      (xy 2.389862 -6.502893)
-      (xy 2.40515 -6.460091)
-      (xy 2.406107 -6.454799)
-      (xy 2.414835 -6.419116)
-      (xy 2.425374 -6.400105)
-      (xy 2.427917 -6.399142)
-      (xy 2.434492 -6.385642)
-      (xy 2.439142 -6.350318)
-      (xy 2.440827 -6.30293)
-      (xy 2.438986 -6.253934)
-      (xy 2.434169 -6.219281)
-      (xy 2.427706 -6.206718)
-      (xy 2.41792 -6.193543)
-      (xy 2.408221 -6.160193)
-      (xy 2.404596 -6.14011)
-      (xy 2.395901 -6.100455)
-      (xy 2.385366 -6.07661)
-      (xy 2.380713 -6.073501)
-      (xy 2.367216 -6.06221)
-      (xy 2.366818 -6.058699)
-      (xy 2.357172 -6.041732)
-      (xy 2.333096 -6.012609)
-      (xy 2.301885 -5.97899)
-      (xy 2.270831 -5.948534)
-      (xy 2.247231 -5.928898)
-      (xy 2.239945 -5.925483)
-      (xy 2.223887 -5.916273)
-      (xy 2.209284 -5.90328)
-      (xy 2.177218 -5.885562)
-      (xy 2.151134 -5.881077)
-      (xy 2.123826 -5.875875)
-      (xy 2.115186 -5.866275)
-      (xy 2.102519 -5.855148)
-      (xy 2.078182 -5.851473)
-      (xy 2.05829 -5.849786)
-      (xy 2.04721 -5.840266)
-      (xy 2.04237 -5.816225)
-      (xy 2.041198 -5.770975)
-      (xy 2.041177 -5.755261)
-      (xy 2.041826 -5.703542)
-      (xy 2.045487 -5.674735)
-      (xy 2.054734 -5.662152)
-      (xy 2.072138 -5.659105)
-      (xy 2.078182 -5.659049)
-      (xy 2.106005 -5.654382)
-      (xy 2.115186 -5.645423)
-      (xy 2.128011 -5.633368)
-      (xy 2.159288 -5.622158)
-      (xy 2.163292 -5.621232)
-      (xy 2.202876 -5.605699)
-      (xy 2.230676 -5.583141)
-      (xy 2.230739 -5.583051)
-      (xy 2.251542 -5.561165)
-      (xy 2.264044 -5.555436)
-      (xy 2.28525 -5.545012)
-      (xy 2.311744 -5.521211)
-      (xy 2.332319 -5.495238)
-      (xy 2.337214 -5.482266)
-      (xy 2.348062 -5.463798)
-      (xy 2.366206 -5.447997)
-      (xy 2.388548 -5.418632)
-      (xy 2.403922 -5.372379)
-      (xy 2.405102 -5.365748)
-      (xy 2.41391 -5.327752)
-      (xy 2.424269 -5.305888)
-      (xy 2.427917 -5.303804)
-      (xy 2.434492 -5.290304)
-      (xy 2.439142 -5.25498)
-      (xy 2.440827 -5.207592)
-      (xy 2.439016 -5.158596)
-      (xy 2.434276 -5.123943)
-      (xy 2.427917 -5.11138)
-      (xy 2.417758 -5.098305)
-      (xy 2.408029 -5.065626)
-      (xy 2.40554 -5.052173)
-      (xy 2.396388 -5.015157)
-      (xy 2.385009 -4.994511)
-      (xy 2.381445 -4.992965)
-      (xy 2.368351 -4.981025)
-      (xy 2.366818 -4.971475)
-      (xy 2.356455 -4.949102)
-      (xy 2.330776 -4.917042)
-      (xy 2.297895 -4.88352)
-      (xy 2.265927 -4.856763)
-      (xy 2.242987 -4.844997)
-      (xy 2.241999 -4.844946)
-      (xy 2.221301 -4.834089)
-      (xy 2.203998 -4.815343)
-      (xy 2.174218 -4.792043)
-      (xy 2.148923 -4.785739)
-      (xy 2.12271 -4.780229)
-      (xy 2.115186 -4.770937)
-      (xy 2.102519 -4.75981)
-      (xy 2.078182 -4.756135)
-      (xy 2.050367 -4.750317)
-      (xy 2.041445 -4.727015)
-      (xy 2.041177 -4.717713)
-      (xy 2.046623 -4.696773)
-      (xy 2.06459 -4.667774)
-      (xy 2.097523 -4.627716)
-      (xy 2.147863 -4.573599)
-      (xy 2.209981 -4.510487)
-      (xy 2.378785 -4.341683)
-      (xy 7.895315 -4.343121)
-      (xy 8.061835 -4.511268)
-      (xy 8.129496 -4.580877)
-      (xy 8.177563 -4.63365)
-      (xy 8.208438 -4.672561)
-      (xy 8.224521 -4.70059)
-      (xy 8.228356 -4.717775)
-      (xy 8.223833 -4.745127)
-      (xy 8.204199 -4.755157)
-      (xy 8.183951 -4.756135)
-      (xy 8.152772 -4.760423)
-      (xy 8.139549 -4.770753)
-      (xy 8.139545 -4.770937)
-      (xy 8.127148 -4.782963)
-      (xy 8.109942 -4.785739)
-      (xy 8.085878 -4.791221)
-      (xy 8.080338 -4.798815)
-      (xy 8.068362 -4.814155)
-      (xy 8.054435 -4.821254)
-      (xy 8.009447 -4.842371)
-      (xy 7.964476 -4.871124)
-      (xy 7.927233 -4.901622)
-      (xy 7.905434 -4.927975)
-      (xy 7.902715 -4.937109)
-      (xy 7.893291 -4.95761)
-      (xy 7.880513 -4.972877)
-      (xy 7.862795 -5.004943)
-      (xy 7.85831 -5.031027)
-      (xy 7.853108 -5.058334)
-      (xy 7.843508 -5.066974)
-      (xy 7.833724 -5.079986)
-      (xy 7.828834 -5.111982)
-      (xy 7.828706 -5.118781)
-      (xy 7.824988 -5.153024)
-      (xy 7.81908 -5.164087)
-      (xy 7.281037 -5.164087)
-      (xy 7.277222 -5.127039)
-      (xy 7.261666 -5.108826)
-      (xy 7.244032 -5.102656)
-      (xy 7.216341 -5.091824)
-      (xy 7.207028 -5.081898)
-      (xy 7.193342 -5.064707)
-      (xy 7.156463 -5.050806)
-      (xy 7.10266 -5.040588)
-      (xy 7.038202 -5.034449)
-      (xy 6.969358 -5.032782)
-      (xy 6.902397 -5.035984)
-      (xy 6.843587 -5.044447)
-      (xy 6.803677 -5.056509)
-      (xy 6.774826 -5.072364)
-      (xy 6.762972 -5.08539)
-      (xy 6.750979 -5.095413)
-      (xy 6.741442 -5.096578)
-      (xy 6.714802 -5.107618)
-      (xy 6.68307 -5.134032)
-      (xy 6.656307 -5.165759)
-      (xy 6.644572 -5.192741)
-      (xy 6.644557 -5.193463)
-      (xy 6.638366 -5.212823)
-      (xy 6.633456 -5.215109)
-      (xy 6.615892 -5.228879)
-      (xy 6.601788 -5.265159)
-      (xy 6.591709 -5.316995)
-      (xy 6.586221 -5.377432)
-      (xy 6.58589 -5.439519)
-      (xy 6.591283 -5.496302)
-      (xy 6.602965 -5.540828)
-      (xy 6.606343 -5.548111)
-      (xy 6.640481 -5.597931)
-      (xy 6.688031 -5.647247)
-      (xy 6.741566 -5.690145)
-      (xy 6.793654 -5.720709)
-      (xy 6.836867 -5.733028)
-      (xy 6.838673 -5.733058)
-      (xy 6.861791 -5.739592)
-      (xy 6.866585 -5.74786)
-      (xy 6.879252 -5.758987)
-      (xy 6.90359 -5.762662)
-      (xy 6.93141 -5.767501)
-      (xy 6.940594 -5.776793)
-      (xy 6.953534 -5.788539)
-      (xy 6.985375 -5.799195)
-      (xy 6.992401 -5.800643)
-      (xy 7.026554 -5.810334)
-      (xy 7.043726 -5.821638)
-      (xy 7.044207 -5.823517)
-      (xy 7.05622 -5.835195)
-      (xy 7.06641 -5.836671)
-      (xy 7.086034 -5.84852)
-      (xy 7.088613 -5.858874)
-      (xy 7.096605 -5.878572)
-      (xy 7.103415 -5.881077)
-      (xy 7.111858 -5.894389)
-      (xy 7.117218 -5.928427)
-      (xy 7.118217 -5.955086)
-      (xy 7.115554 -5.997304)
-      (xy 7.108747 -6.024101)
-      (xy 7.103415 -6.029096)
-      (xy 7.090283 -6.041085)
-      (xy 7.088613 -6.051298)
-      (xy 7.076764 -6.070922)
-      (xy 7.06641 -6.073501)
-      (xy 7.046712 -6.081494)
-      (xy 7.044207 -6.088303)
-      (xy 7.030234 -6.095396)
-      (xy 6.991554 -6.100455)
-      (xy 6.933027 -6.102941)
-      (xy 6.910991 -6.103105)
-      (xy 6.847159 -6.101552)
-      (xy 6.801625 -6.097255)
-      (xy 6.779249 -6.090752)
-      (xy 6.777774 -6.088303)
-      (xy 6.764664 -6.07894)
-      (xy 6.732005 -6.073824)
-      (xy 6.720014 -6.073501)
-      (xy 6.680745 -6.076515)
-      (xy 6.659744 -6.089952)
-      (xy 6.647155 -6.116817)
-      (xy 6.637283 -6.155068)
-      (xy 6.635705 -6.177869)
-      (xy 6.521278 -6.177869)
-      (xy 6.493448 -6.139341)
-      (xy 6.489025 -6.135378)
-      (xy 6.465219 -6.118604)
-      (xy 6.436187 -6.10878)
-      (xy 6.393666 -6.104187)
-      (xy 6.333795 -6.103105)
-      (xy 6.215682 -6.103105)
-      (xy 6.207902 -5.060439)
-      (xy 6.173348 -5.043216)
-      (xy 6.127434 -5.031537)
-      (xy 6.091605 -5.047668)
-      (xy 6.07098 -5.078086)
-      (xy 6.065472 -5.098659)
-      (xy 6.061196 -5.134861)
-      (xy 5.83072 -5.134861)
-      (xy 5.828973 -5.094562)
-      (xy 5.826957 -5.084264)
-      (xy 5.806759 -5.048191)
-      (xy 5.774164 -5.036763)
-      (xy 5.733626 -5.050287)
-      (xy 5.702002 -5.075666)
-      (xy 5.667337 -5.130811)
-      (xy 5.656344 -5.179279)
-      (xy 5.649317 -5.218535)
-      (xy 5.64012 -5.241827)
-      (xy 5.636105 -5.244597)
-      (xy 5.626422 -5.257275)
-      (xy 5.623228 -5.281601)
-      (xy 5.623228 -5.318606)
-      (xy 5.416002 -5.318606)
-      (xy 5.332426 -5.318162)
-      (xy 5.274203 -5.316525)
-      (xy 5.237093 -5.313243)
-      (xy 5.216852 -5.30786)
-      (xy 5.209241 -5.299921)
-      (xy 5.208776 -5.296403)
-      (xy 5.200783 -5.276705)
-      (xy 5.193974 -5.274201)
-      (xy 5.182751 -5.261561)
-      (xy 5.179172 -5.238069)
-      (xy 5.174479 -5.207268)
-      (xy 5.166366 -5.194023)
-      (xy 5.155659 -5.175359)
-      (xy 5.146143 -5.13993)
-      (xy 5.145069 -5.133791)
-      (xy 5.127154 -5.078334)
-      (xy 5.093807 -5.047046)
-      (xy 5.043234 -5.037371)
-      (xy 5.008971 -5.041082)
-      (xy 4.989996 -5.057962)
-      (xy 4.977648 -5.089589)
-      (xy 4.970095 -5.125467)
-      (xy 4.972205 -5.147746)
-      (xy 4.974026 -5.14967)
-      (xy 4.982612 -5.168407)
-      (xy 4.986694 -5.203736)
-      (xy 4.986748 -5.208466)
-      (xy 4.990525 -5.24236)
-      (xy 4.999792 -5.259039)
-      (xy 5.00155 -5.259399)
-      (xy 5.012677 -5.272066)
-      (xy 5.016352 -5.296403)
-      (xy 5.020946 -5.324228)
-      (xy 5.029765 -5.333408)
-      (xy 5.039228 -5.346674)
-      (xy 5.048753 -5.380604)
-      (xy 5.053356 -5.407417)
-      (xy 5.061558 -5.449569)
-      (xy 5.071394 -5.476372)
-      (xy 5.076948 -5.481427)
-      (xy 5.087034 -5.494102)
-      (xy 5.090361 -5.518431)
-      (xy 5.095428 -5.546249)
-      (xy 5.105163 -5.555436)
-      (xy 5.116569 -5.568024)
-      (xy 5.119965 -5.589974)
-      (xy 5.1243 -5.621643)
-      (xy 5.131066 -5.635613)
-      (xy 5.14287 -5.654536)
-      (xy 5.143275 -5.656582)
-      (xy 5.145882 -5.674561)
-      (xy 4.868134 -5.674561)
-      (xy 4.867969 -5.557983)
-      (xy 4.867451 -5.445289)
-      (xy 4.866583 -5.340663)
-      (xy 4.865363 -5.24829)
-      (xy 4.863792 -5.172357)
-      (xy 4.861872 -5.117049)
-      (xy 4.859602 -5.086551)
-      (xy 4.859246 -5.084447)
-      (xy 4.845258 -5.049185)
-      (xy 4.817092 -5.034081)
-      (xy 4.81114 -5.033008)
-      (xy 4.781261 -5.027834)
-      (xy 4.769093 -5.024787)
-      (xy 4.757856 -5.03259)
-      (xy 4.734019 -5.054674)
-      (xy 4.728388 -5.060246)
-      (xy 4.690711 -5.097924)
-      (xy 4.690711 -5.718256)
-      (xy 4.654882 -5.718256)
-      (xy 4.626775 -5.710947)
-      (xy 4.611765 -5.683822)
-      (xy 4.609301 -5.673851)
-      (xy 4.59856 -5.642776)
-      (xy 4.586188 -5.629454)
-      (xy 4.585922 -5.629445)
-      (xy 4.574847 -5.617038)
-      (xy 4.572296 -5.599842)
-      (xy 4.566814 -5.575778)
-      (xy 4.55922 -5.570238)
-      (xy 4.545099 -5.557951)
-      (xy 4.535308 -5.536934)
-      (xy 4.525314 -5.508053)
-      (xy 4.520489 -5.496229)
-      (xy 4.513259 -5.477794)
-      (xy 4.50567 -5.455523)
-      (xy 4.492456 -5.429738)
-      (xy 4.481758 -5.422219)
-      (xy 4.47113 -5.409807)
-      (xy 4.468683 -5.392615)
-      (xy 4.46315 -5.368553)
-      (xy 4.455486 -5.363012)
-      (xy 4.442455 -5.350467)
-      (xy 4.433001 -5.326007)
-      (xy 4.416665 -5.296697)
-      (xy 4.385933 -5.289002)
-      (xy 4.346634 -5.29843)
-      (xy 4.316387 -5.321467)
-      (xy 4.305862 -5.347153)
-      (xy 4.296369 -5.362383)
-      (xy 4.292708 -5.363012)
-      (xy 4.281609 -5.375945)
-      (xy 4.271278 -5.407772)
-      (xy 4.269834 -5.414818)
-      (xy 4.259896 -5.448979)
-      (xy 4.24799 -5.466147)
-      (xy 4.245984 -5.466625)
-      (xy 4.234501 -5.479028)
-      (xy 4.231853 -5.496229)
-      (xy 4.225654 -5.520281)
-      (xy 4.217051 -5.525832)
-      (xy 4.203919 -5.537821)
-      (xy 4.202249 -5.548035)
-      (xy 4.19524 -5.567747)
-      (xy 4.189298 -5.570238)
-      (xy 4.177929 -5.583089)
-      (xy 4.167552 -5.614412)
-      (xy 4.166747 -5.618231)
-      (xy 4.148883 -5.682673)
-      (xy 4.126089 -5.727077)
-      (xy 4.100748 -5.747141)
-      (xy 4.095023 -5.74786)
-      (xy 4.086526 -5.74592)
-      (xy 4.080104 -5.737699)
-      (xy 4.075469 -5.719595)
-      (xy 4.072336 -5.688007)
-      (xy 4.070415 -5.639333)
-      (xy 4.069419 -5.569972)
-      (xy 4.069062 -5.476323)
-      (xy 4.069032 -5.422219)
-      (xy 4.068371 -5.306703)
-      (xy 4.066434 -5.214886)
-      (xy 4.063289 -5.148278)
-      (xy 4.059006 -5.108388)
-      (xy 4.054231 -5.096578)
-      (xy 4.042204 -5.084181)
-      (xy 4.039429 -5.066974)
-      (xy 4.034437 -5.047571)
-      (xy 4.014283 -5.03902)
-      (xy 3.980503 -5.037371)
-      (xy 3.941065 -5.040153)
-      (xy 3.921258 -5.052018)
-      (xy 3.91229 -5.074375)
-      (xy 3.900862 -5.102085)
-      (xy 3.889805 -5.11138)
-      (xy 3.886703 -5.125696)
-      (xy 3.883891 -5.166702)
-      (xy 3.881439 -5.231485)
-      (xy 3.879415 -5.317133)
-      (xy 3.877889 -5.420733)
-      (xy 3.876931 -5.539371)
-      (xy 3.876627 -5.659049)
-      (xy 3.713788 -5.659049)
-      (xy 3.713401 -5.498578)
-      (xy 3.712255 -5.363966)
-      (xy 3.710366 -5.255914)
-      (xy 3.707754 -5.175125)
-      (xy 3.704437 -5.122299)
-      (xy 3.700433 -5.098141)
-      (xy 3.698986 -5.096578)
-      (xy 3.686819 -5.084227)
-      (xy 3.684184 -5.068004)
-      (xy 3.67128 -5.041672)
-      (xy 3.65088 -5.033015)
-      (xy 3.62039 -5.02711)
-      (xy 3.607531 -5.024585)
-      (xy 3.590334 -5.032189)
-      (xy 3.574227 -5.045829)
-      (xy 3.555323 -5.073596)
-      (xy 3.550967 -5.090235)
-      (xy 3.542629 -5.109244)
-      (xy 3.536165 -5.11138)
-      (xy 3.529668 -5.125601)
-      (xy 3.524861 -5.166007)
-      (xy 3.522026 -5.229213)
-      (xy 3.521363 -5.289002)
-      (xy 3.521363 -5.466625)
-      (xy 3.41775 -5.466625)
-      (xy 3.364599 -5.468581)
-      (xy 3.327873 -5.473822)
-      (xy 3.314137 -5.481412)
-      (xy 3.314137 -5.481427)
-      (xy 3.301051 -5.491201)
-      (xy 3.268605 -5.496875)
-      (xy 3.25863 -5.49731)
-      (xy 3.207634 -5.506134)
-      (xy 3.160434 -5.526002)
-      (xy 3.158718 -5.527087)
-      (xy 3.121043 -5.549286)
-      (xy 3.089911 -5.564196)
-      (xy 3.088409 -5.564736)
-      (xy 3.066479 -5.582261)
-      (xy 3.062506 -5.594874)
-      (xy 3.052387 -5.61877)
-      (xy 3.027797 -5.648183)
-      (xy 3.025501 -5.650352)
-      (xy 2.999838 -5.683024)
-      (xy 2.988523 -5.715022)
-      (xy 2.988496 -5.716253)
-      (xy 2.982652 -5.741373)
-      (xy 2.973694 -5.74786)
-      (xy 2.966602 -5.761833)
-      (xy 2.961543 -5.800513)
-      (xy 2.959057 -5.85904)
-      (xy 2.958893 -5.881077)
-      (xy 2.960445 -5.944909)
-      (xy 2.964743 -5.990442)
-      (xy 2.971246 -6.012818)
-      (xy 2.973694 -6.014294)
-      (xy 2.984821 -6.026961)
-      (xy 2.988496 -6.051298)
-      (xy 2.993224 -6.079121)
-      (xy 3.002301 -6.088303)
-      (xy 3.017048 -6.100589)
-      (xy 3.026278 -6.120354)
-      (xy 3.042938 -6.151708)
-      (xy 3.069941 -6.185306)
-      (xy 3.098613 -6.211705)
-      (xy 3.119228 -6.22152)
-      (xy 3.139118 -6.231676)
-      (xy 3.151317 -6.243723)
-      (xy 3.178079 -6.259095)
-      (xy 3.217645 -6.265906)
-      (xy 3.219738 -6.265925)
-      (xy 3.253253 -6.269768)
-      (xy 3.269457 -6.279174)
-      (xy 3.269732 -6.280727)
-      (xy 3.283907 -6.28735)
-      (xy 3.323996 -6.292213)
-      (xy 3.386343 -6.294993)
-      (xy 3.437002 -6.295529)
-      (xy 3.540174 -6.292591)
-      (xy 3.615067 -6.283666)
-      (xy 3.662428 -6.268584)
-      (xy 3.683005 -6.247179)
-      (xy 3.684068 -6.240022)
-      (xy 3.693534 -6.222823)
-      (xy 3.698986 -6.22152)
-      (xy 3.703209 -6.206839)
-      (xy 3.706751 -6.163263)
-      (xy 3.709595 -6.091495)
-      (xy 3.711721 -5.992236)
-      (xy 3.713111 -5.866188)
-      (xy 3.713747 -5.714053)
-      (xy 3.713788 -5.659049)
-      (xy 3.876627 -5.659049)
-      (xy 3.876608 -5.66645)
-      (xy 3.876949 -5.796924)
-      (xy 3.877924 -5.915192)
-      (xy 3.879464 -6.018343)
-      (xy 3.8815 -6.103463)
-      (xy 3.883963 -6.167639)
-      (xy 3.886784 -6.207958)
-      (xy 3.889805 -6.22152)
-      (xy 3.902857 -6.234059)
-      (xy 3.912234 -6.258299)
-      (xy 3.934787 -6.292901)
-      (xy 3.958244 -6.304309)
-      (xy 3.988842 -6.322738)
-      (xy 3.99536 -6.34524)
-      (xy 3.998079 -6.36025)
-      (xy 4.007237 -6.350986)
-      (xy 4.020637 -6.325133)
-      (xy 4.039256 -6.289879)
-      (xy 4.053936 -6.267857)
-      (xy 4.056131 -6.265777)
-      (xy 4.067146 -6.247171)
-      (xy 4.0769 -6.217531)
-      (xy 4.088653 -6.185016)
-      (xy 4.100276 -6.1687)
-      (xy 4.110444 -6.149161)
-      (xy 4.113438 -6.124434)
-      (xy 4.118016 -6.097029)
-      (xy 4.126514 -6.088303)
-      (xy 4.140635 -6.076017)
-      (xy 4.150426 -6.054999)
-      (xy 4.16042 -6.026119)
-      (xy 4.165245 -6.014294)
-      (xy 4.172475 -5.99586)
-      (xy 4.180064 -5.973589)
-      (xy 4.193278 -5.947803)
-      (xy 4.203976 -5.940284)
-      (xy 4.214604 -5.927872)
-      (xy 4.217051 -5.910681)
-      (xy 4.222972 -5.886624)
-      (xy 4.231182 -5.881077)
-      (xy 4.242634 -5.868079)
-      (xy 4.253391 -5.835825)
-      (xy 4.25552 -5.82557)
-      (xy 4.264476 -5.787805)
-      (xy 4.273709 -5.764657)
-      (xy 4.275464 -5.762662)
-      (xy 4.288799 -5.743677)
-      (xy 4.30666 -5.708754)
-      (xy 4.32361 -5.669835)
-      (xy 4.334213 -5.638857)
-      (xy 4.335466 -5.630909)
-      (xy 4.347985 -5.61836)
-      (xy 4.36877 -5.615008)
-      (xy 4.396165 -5.628026)
-      (xy 4.423907 -5.659979)
-      (xy 4.445358 -5.701035)
-      (xy 4.453881 -5.741068)
-      (xy 4.462069 -5.760372)
-      (xy 4.468683 -5.762662)
-      (xy 4.47981 -5.775329)
-      (xy 4.483485 -5.799667)
-      (xy 4.488323 -5.827488)
-      (xy 4.497616 -5.836671)
-      (xy 4.509361 -5.849611)
-      (xy 4.520018 -5.881452)
-      (xy 4.521466 -5.888478)
-      (xy 4.531157 -5.922631)
-      (xy 4.54246 -5.939804)
-      (xy 4.544339 -5.940284)
-      (xy 4.556017 -5.952297)
-      (xy 4.557494 -5.962487)
-      (xy 4.565487 -5.982185)
-      (xy 4.572296 -5.98469)
-      (xy 4.584322 -5.997087)
-      (xy 4.587098 -6.014294)
-      (xy 4.593018 -6.038351)
-      (xy 4.601229 -6.043898)
-      (xy 4.612974 -6.056837)
-      (xy 4.623631 -6.088678)
-      (xy 4.625079 -6.095704)
-      (xy 4.63477 -6.129857)
-      (xy 4.646073 -6.14703)
-      (xy 4.647953 -6.147511)
-      (xy 4.657844 -6.160187)
-      (xy 4.661107 -6.184515)
-      (xy 4.666174 -6.212333)
-      (xy 4.675909 -6.22152)
-      (xy 4.689997 -6.233252)
-      (xy 4.691213 -6.240022)
-      (xy 4.697507 -6.264243)
-      (xy 4.712621 -6.302264)
-      (xy 4.718694 -6.315547)
-      (xy 4.735878 -6.349136)
-      (xy 4.74583 -6.358292)
-      (xy 4.752567 -6.345963)
-      (xy 4.753837 -6.341352)
-      (xy 4.775731 -6.312975)
-      (xy 4.806224 -6.30129)
-      (xy 4.841024 -6.28694)
-      (xy 4.857556 -6.2559)
-      (xy 4.85939 -6.247732)
-      (xy 4.861704 -6.22117)
-      (xy 4.863662 -6.169193)
-      (xy 4.865265 -6.095986)
-      (xy 4.866513 -6.005733)
-      (xy 4.867407 -5.902621)
-      (xy 4.867947 -5.790835)
-      (xy 4.868134 -5.674561)
-      (xy 5.145882 -5.674561)
-      (xy 5.151451 -5.712975)
-      (xy 5.161798 -5.761841)
-      (xy 5.17244 -5.795673)
-      (xy 5.180853 -5.807068)
-      (xy 5.190805 -5.819718)
-      (xy 5.193974 -5.843199)
-      (xy 5.198899 -5.874164)
-      (xy 5.207389 -5.887621)
-      (xy 5.21698 -5.905976)
-      (xy 5.226596 -5.943628)
-      (xy 5.230981 -5.969905)
-      (xy 5.239182 -6.012051)
-      (xy 5.249018 -6.038848)
-      (xy 5.254571 -6.043898)
-      (xy 5.264656 -6.056573)
-      (xy 5.267984 -6.080902)
-      (xy 5.272407 -6.108729)
-      (xy 5.280894 -6.117907)
-      (xy 5.291053 -6.130981)
-      (xy 5.300782 -6.16366)
-      (xy 5.303271 -6.177114)
-      (xy 5.312422 -6.21413)
-      (xy 5.323802 -6.234776)
-      (xy 5.327366 -6.236322)
-      (xy 5.339251 -6.248721)
-      (xy 5.341993 -6.265925)
-      (xy 5.350735 -6.289929)
-      (xy 5.362985 -6.295529)
-      (xy 5.395994 -6.300745)
-      (xy 5.405866 -6.303929)
-      (xy 5.430568 -6.299479)
-      (xy 5.460101 -6.276574)
-      (xy 5.486797 -6.243595)
-      (xy 5.502989 -6.208923)
-      (xy 5.504813 -6.195768)
-      (xy 5.510366 -6.169697)
-      (xy 5.519615 -6.162312)
-      (xy 5.530742 -6.149645)
-      (xy 5.534417 -6.125308)
-      (xy 5.539122 -6.097485)
-      (xy 5.548154 -6.088303)
-      (xy 5.557327 -6.074956)
-      (xy 5.56662 -6.04051)
-      (xy 5.572087 -6.006697)
-      (xy 5.579893 -5.960339)
-      (xy 5.589218 -5.927225)
-      (xy 5.595355 -5.917013)
-      (xy 5.605452 -5.897521)
-      (xy 5.608426 -5.872803)
-      (xy 5.613122 -5.845399)
-      (xy 5.621839 -5.836671)
-      (xy 5.631303 -5.823406)
-      (xy 5.640827 -5.789475)
-      (xy 5.645431 -5.762662)
-      (xy 5.653633 -5.720511)
-      (xy 5.663468 -5.693707)
-      (xy 5.669023 -5.688653)
-      (xy 5.679108 -5.675977)
-      (xy 5.682436 -5.651648)
-      (xy 5.687503 -5.623831)
-      (xy 5.697238 -5.614643)
-      (xy 5.708461 -5.602003)
-      (xy 5.712039 -5.578512)
-      (xy 5.716833 -5.54764)
-      (xy 5.725111 -5.534302)
-      (xy 5.734033 -5.516215)
-      (xy 5.743164 -5.478195)
-      (xy 5.74835 -5.444851)
-      (xy 5.756276 -5.398461)
-      (xy 5.765911 -5.365236)
-      (xy 5.772283 -5.354971)
-      (xy 5.782925 -5.335114)
-      (xy 5.786049 -5.310332)
-      (xy 5.79021 -5.28292)
-      (xy 5.797928 -5.274201)
-      (xy 5.809299 -5.260922)
-      (xy 5.819486 -5.22718)
-      (xy 5.827092 -5.182113)
-      (xy 5.83072 -5.134861)
-      (xy 6.061196 -5.134861)
-      (xy 6.061049 -5.136109)
-      (xy 6.057633 -5.192652)
-      (xy 6.055148 -5.270508)
-      (xy 6.053517 -5.371894)
-      (xy 6.052661 -5.499028)
-      (xy 6.052482 -5.610193)
-      (xy 6.052482 -6.103105)
-      (xy 5.932103 -6.103105)
-      (xy 5.870509 -6.104034)
-      (xy 5.8309 -6.107945)
-      (xy 5.805686 -6.116528)
-      (xy 5.787277 -6.131471)
-      (xy 5.782949 -6.136283)
-      (xy 5.761462 -6.178701)
-      (xy 5.762512 -6.211151)
-      (xy 5.768664 -6.237657)
-      (xy 5.777602 -6.257936)
-      (xy 5.792991 -6.272822)
-      (xy 5.818495 -6.283148)
-      (xy 5.857777 -6.289748)
-      (xy 5.9145 -6.293454)
-      (xy 5.99233 -6.295099)
-      (xy 6.09493 -6.295518)
-      (xy 6.133508 -6.295529)
-      (xy 6.453478 -6.295529)
-      (xy 6.48981 -6.259197)
-      (xy 6.52006 -6.216931)
-      (xy 6.521278 -6.177869)
-      (xy 6.635705 -6.177869)
-      (xy 6.635369 -6.182716)
-      (xy 6.648705 -6.212775)
-      (xy 6.674238 -6.243325)
-      (xy 6.701764 -6.263317)
-      (xy 6.712226 -6.265925)
-      (xy 6.733334 -6.276561)
-      (xy 6.736265 -6.282018)
-      (xy 6.753307 -6.291123)
-      (xy 6.79256 -6.29733)
-      (xy 6.846773 -6.300665)
-      (xy 6.908698 -6.301158)
-      (xy 6.971087 -6.298833)
-      (xy 7.02669 -6.293718)
-      (xy 7.068258 -6.285841)
-      (xy 7.081798 -6.280727)
-      (xy 7.124375 -6.251884)
-      (xy 7.173439 -6.209455)
-      (xy 7.219815 -6.162323)
-      (xy 7.254328 -6.119368)
-      (xy 7.262535 -6.105775)
-      (xy 7.270498 -6.077466)
-      (xy 7.276315 -6.032295)
-      (xy 7.279841 -5.977931)
-      (xy 7.280935 -5.922041)
-      (xy 7.279451 -5.872293)
-      (xy 7.275249 -5.836354)
-      (xy 7.268183 -5.821893)
-      (xy 7.26784 -5.82187)
-      (xy 7.254809 -5.809325)
-      (xy 7.245355 -5.784865)
-      (xy 7.233469 -5.757142)
-      (xy 7.221548 -5.74786)
-      (xy 7.208664 -5.735867)
-      (xy 7.207028 -5.725657)
-      (xy 7.19561 -5.706024)
-      (xy 7.185664 -5.703455)
-      (xy 7.160826 -5.692378)
-      (xy 7.144959 -5.67584)
-      (xy 7.117239 -5.653274)
-      (xy 7.077667 -5.637693)
-      (xy 7.077511 -5.637659)
-      (xy 7.044894 -5.626863)
-      (xy 7.029572 -5.614638)
-      (xy 7.029405 -5.613467)
-      (xy 7.016731 -5.603222)
-      (xy 6.992401 -5.599842)
-      (xy 6.964583 -5.594775)
-      (xy 6.955396 -5.58504)
-      (xy 6.942729 -5.573913)
-      (xy 6.918391 -5.570238)
-      (xy 6.890566 -5.565731)
-      (xy 6.881387 -5.557083)
-      (xy 6.868454 -5.545985)
-      (xy 6.836626 -5.535654)
-      (xy 6.82958 -5.53421)
-      (xy 6.792167 -5.522119)
-      (xy 6.778265 -5.502107)
-      (xy 6.777774 -5.495558)
-      (xy 6.771447 -5.471872)
-      (xy 6.762972 -5.466625)
-      (xy 6.754144 -5.453395)
-      (xy 6.748849 -5.419922)
-      (xy 6.74817 -5.400016)
-      (xy 6.75111 -5.360293)
-      (xy 6.758548 -5.336464)
-      (xy 6.762972 -5.333408)
-      (xy 6.776104 -5.321419)
-      (xy 6.777774 -5.311205)
-      (xy 6.787572 -5.28494)
-      (xy 6.807377 -5.259399)
-      (xy 6.825481 -5.245237)
-      (xy 6.849884 -5.236391)
-      (xy 6.887361 -5.231682)
-      (xy 6.944688 -5.229932)
-      (xy 6.977599 -5.229795)
-      (xy 7.039854 -5.231183)
-      (xy 7.087393 -5.234952)
-      (xy 7.114319 -5.24051)
-      (xy 7.118217 -5.243926)
-      (xy 7.13117 -5.255609)
-      (xy 7.163113 -5.266324)
-      (xy 7.17093 -5.267946)
-      (xy 7.223019 -5.265991)
-      (xy 7.259911 -5.239713)
-      (xy 7.278975 -5.191593)
-      (xy 7.281037 -5.164087)
-      (xy 7.81908 -5.164087)
-      (xy 7.815847 -5.17014)
-      (xy 7.813904 -5.170588)
-      (xy 7.803511 -5.18345)
-      (xy 7.799104 -5.214441)
-      (xy 7.799102 -5.214993)
-      (xy 7.80339 -5.246172)
-      (xy 7.81372 -5.259395)
-      (xy 7.813904 -5.259399)
-      (xy 7.824377 -5.272241)
-      (xy 7.828706 -5.302931)
-      (xy 7.832905 -5.33685)
-      (xy 7.842369 -5.354907)
-      (xy 7.855277 -5.374331)
-      (xy 7.865117 -5.404712)
-      (xy 7.882003 -5.443144)
-      (xy 7.90326 -5.467017)
-      (xy 7.925925 -5.490472)
-      (xy 7.932319 -5.506897)
-      (xy 7.942366 -5.524386)
-      (xy 7.948583 -5.525832)
-      (xy 7.968099 -5.535834)
-      (xy 7.997117 -5.560828)
-      (xy 8.007092 -5.571055)
-      (xy 8.056081 -5.608444)
-      (xy 8.101842 -5.624798)
-      (xy 8.136308 -5.633571)
-      (xy 8.153802 -5.644246)
-      (xy 8.154347 -5.646184)
-      (xy 8.167025 -5.655858)
-      (xy 8.191352 -5.659049)
-      (xy 8.211244 -5.660736)
-      (xy 8.222324 -5.670256)
-      (xy 8.227163 -5.694297)
-      (xy 8.228335 -5.739547)
-      (xy 8.228356 -5.755261)
-      (xy 8.228356 -5.851473)
-      (xy 8.184824 -5.851473)
-      (xy 8.151021 -5.855513)
-      (xy 8.133158 -5.864635)
-      (xy 8.114 -5.877669)
-      (xy 8.085055 -5.887829)
-      (xy 8.046062 -5.904881)
-      (xy 8.022007 -5.9238)
-      (xy 7.99204 -5.949105)
-      (xy 7.972689 -5.959478)
-      (xy 7.945083 -5.981067)
-      (xy 7.936708 -5.995456)
-      (xy 7.918693 -6.024155)
-      (xy 7.892638 -6.05177)
-      (xy 7.867833 -6.083425)
-      (xy 7.85831 -6.113804)
-      (xy 7.852171 -6.143471)
-      (xy 7.843508 -6.154912)
-      (xy 7.832844 -6.174921)
-      (xy 7.828706 -6.207592)
-      (xy 7.82434 -6.238391)
-      (xy 7.813904 -6.251124)
-      (xy 7.803511 -6.263986)
-      (xy 7.799104 -6.294977)
-      (xy 7.799102 -6.295529)
-      (xy 7.80339 -6.326708)
-      (xy 7.81372 -6.339931)
-      (xy 7.813904 -6.339935)
-      (xy 7.823688 -6.352947)
-      (xy 7.828578 -6.384942)
-      (xy 7.828706 -6.391741)
-      (xy 7.832129 -6.425988)
-      (xy 7.840547 -6.443102)
-      (xy 7.842332 -6.443548)
-      (xy 7.854388 -6.456372)
-      (xy 7.865597 -6.487647)
-      (xy 7.86652 -6.49164)
-      (xy 7.8823 -6.53303)
-      (xy 7.904701 -6.563685)
-      (xy 7.926085 -6.588417)
-      (xy 7.932319 -6.604404)
-      (xy 7.942907 -6.620315)
-      (xy 7.947767 -6.62117)
-      (xy 7.967989 -6.630456)
-      (xy 7.997723 -6.653293)
-      (xy 8.003123 -6.658175)
-      (xy 8.034316 -6.682719)
-      (xy 8.059044 -6.694891)
-      (xy 8.061684 -6.69518)
-      (xy 8.078987 -6.704465)
-      (xy 8.080338 -6.709981)
-      (xy 8.093005 -6.721108)
-      (xy 8.117342 -6.724783)
-      (xy 8.14516 -6.72985)
-      (xy 8.154347 -6.739585)
-      (xy 8.167014 -6.750712)
-      (xy 8.191352 -6.754387)
-      (xy 8.211397 -6.756121)
-      (xy 8.222477 -6.765824)
-      (xy 8.227242 -6.790251)
-      (xy 8.228343 -6.836153)
-      (xy 8.228356 -6.848692)
-      (xy 8.228356 -6.858)
-      (xy 7.281037 -6.858)
-      (xy 6.985 -6.858)
-      (xy 6.985 -7.88673)
-      (xy 6.98495 -8.08734)
-      (xy 6.984771 -8.260352)
-      (xy 6.984417 -8.407771)
-      (xy 6.983843 -8.531601)
-      (xy 6.983003 -8.633849)
-      (xy 6.981852 -8.716518)
-      (xy 6.980345 -8.781614)
-      (xy 6.978437 -8.831142)
-      (xy 6.976082 -8.867108)
-      (xy 6.973234 -8.891515)
-      (xy 6.969849 -8.90637)
-      (xy 6.965881 -8.913678)
-      (xy 6.96174 -8.915459)
-      (xy 6.926496 -8.90176)
-      (xy 6.898039 -8.865075)
-      (xy 6.889743 -8.84446)
-      (xy 6.876453 -8.818991)
-      (xy 6.865587 -8.811846)
-      (xy 6.852335 -8.800418)
-      (xy 6.851783 -8.795987)
-      (xy 6.842774 -8.772343)
-      (xy 6.833281 -8.759496)
-      (xy 6.799129 -8.719951)
-      (xy 6.78198 -8.695714)
-      (xy 6.777774 -8.682522)
-      (xy 6.767065 -8.665462)
-      (xy 6.74817 -8.649026)
-      (xy 6.725259 -8.625783)
-      (xy 6.718566 -8.609426)
-      (xy 6.708859 -8.587422)
-      (xy 6.685132 -8.557815)
-      (xy 6.681562 -8.554159)
-      (xy 6.656723 -8.525266)
-      (xy 6.644752 -8.503374)
-      (xy 6.644557 -8.501582)
-      (xy 6.63433 -8.481969)
-      (xy 6.609515 -8.455563)
-      (xy 6.607552 -8.453834)
-      (xy 6.581962 -8.426127)
-      (xy 6.570583 -8.403015)
-      (xy 6.570548 -8.402126)
-      (xy 6.561786 -8.384203)
-      (xy 6.556028 -8.382592)
-      (xy 6.541691 -8.370103)
-      (xy 6.532934 -8.348432)
-      (xy 6.514913 -8.314506)
-      (xy 6.488247 -8.287151)
-      (xy 6.462314 -8.260449)
-      (xy 6.451998 -8.236201)
-      (xy 6.441057 -8.212024)
-      (xy 6.414245 -8.182918)
-      (xy 6.407697 -8.177484)
-      (xy 6.381015 -8.152494)
-      (xy 6.369957 -8.134048)
-      (xy 6.370478 -8.131356)
-      (xy 6.366036 -8.114398)
-      (xy 6.348171 -8.09364)
-      (xy 6.326226 -8.06884)
-      (xy 6.318916 -8.052654)
-      (xy 6.30898 -8.033577)
-      (xy 6.284772 -8.006543)
-      (xy 6.281911 -8.003848)
-      (xy 6.25667 -7.975837)
-      (xy 6.245001 -7.953782)
-      (xy 6.244907 -7.952475)
-      (xy 6.234256 -7.932137)
-      (xy 6.208569 -7.906816)
-      (xy 6.207902 -7.906288)
-      (xy 6.181716 -7.877737)
-      (xy 6.170897 -7.850234)
-      (xy 6.161347 -7.821867)
-      (xy 6.140115 -7.814188)
-      (xy 6.118329 -7.829016)
-      (xy 6.112321 -7.840663)
-      (xy 6.091043 -7.874965)
-      (xy 6.060989 -7.905418)
-      (xy 6.034421 -7.933219)
-      (xy 6.022893 -7.958958)
-      (xy 6.022879 -7.959633)
-      (xy 6.011094 -7.985541)
-      (xy 6.000676 -7.992391)
-      (xy 5.980986 -8.012147)
-      (xy 5.978473 -8.023533)
-      (xy 5.968314 -8.048478)
-      (xy 5.943643 -8.078396)
-      (xy 5.941468 -8.08045)
-      (xy 5.916086 -8.109978)
-      (xy 5.904531 -8.135272)
-      (xy 5.904464 -8.136657)
-      (xy 5.892127 -8.158343)
-      (xy 5.87486 -8.167965)
-      (xy 5.850812 -8.186812)
-      (xy 5.845256 -8.204155)
-      (xy 5.834547 -8.235942)
-      (xy 5.823053 -8.249375)
-      (xy 5.80439 -8.271761)
-      (xy 5.800851 -8.282795)
-      (xy 5.790902 -8.302217)
-      (xy 5.766666 -8.329425)
-      (xy 5.763846 -8.332082)
-      (xy 5.73848 -8.361424)
-      (xy 5.726912 -8.386321)
-      (xy 5.726841 -8.387703)
-      (xy 5.71488 -8.411139)
-      (xy 5.704416 -8.417634)
-      (xy 5.681339 -8.437158)
-      (xy 5.667447 -8.459923)
-      (xy 5.620216 -8.542578)
-      (xy 5.582523 -8.585305)
-      (xy 5.55904 -8.613477)
-      (xy 5.549219 -8.63542)
-      (xy 5.549219 -8.635481)
-      (xy 5.539022 -8.657921)
-      (xy 5.521733 -8.676893)
-      (xy 5.495117 -8.71009)
-      (xy 5.48373 -8.734136)
-      (xy 5.470472 -8.759951)
-      (xy 5.45941 -8.767441)
-      (xy 5.446095 -8.778818)
-      (xy 5.445606 -8.782889)
-      (xy 5.434965 -8.808816)
-      (xy 5.409574 -8.837211)
-      (xy 5.379235 -8.859466)
-      (xy 5.353747 -8.866973)
-      (xy 5.350738 -8.866217)
-      (xy 5.346083 -8.862252)
-      (xy 5.342078 -8.852822)
-      (xy 5.338675 -8.835868)
-      (xy 5.335826 -8.809333)
-      (xy 5.333483 -8.771162)
-      (xy 5.331598 -8.719295)
-      (xy 5.330123 -8.651676)
-      (xy 5.32901 -8.566248)
-      (xy 5.328211 -8.460954)
-      (xy 5.327678 -8.333737)
-      (xy 5.327363 -8.182539)
-      (xy 5.327217 -8.005303)
-      (xy 5.327191 -7.857591)
-      (xy 5.327191 -6.858)
-      (xy 5.016352 -6.858)
-      (xy 5.016352 -9.018794)
-      (xy 4.695691 -9.018794)
-      (xy 4.695368 -8.886807)
-      (xy 4.694616 -8.757008)
-      (xy 4.693957 -8.68332)
-      (xy 4.689803 -8.280959)
-      (xy 4.153689 -8.276269)
-      (xy 4.009001 -8.274936)
-      (xy 3.890839 -8.273476)
-      (xy 3.796129 -8.271526)
-      (xy 3.721793 -8.268722)
-      (xy 3.664757 -8.264699)
-      (xy 3.621944 -8.259093)
-      (xy 3.590278 -8.251542)
-      (xy 3.566684 -8.24168)
-      (xy 3.548085 -8.229144)
-      (xy 3.531405 -8.21357)
-      (xy 3.519785 -8.201269)
-      (xy 3.493554 -8.180879)
-      (xy 3.476824 -8.175366)
-      (xy 3.45538 -8.165053)
-      (xy 3.425426 -8.140152)
-      (xy 3.396112 -8.109721)
-      (xy 3.376592 -8.08282)
-      (xy 3.373345 -8.072945)
-      (xy 3.364061 -8.051519)
-      (xy 3.354281 -8.039506)
-      (xy 3.335991 -8.013964)
-      (xy 3.314214 -7.974779)
-      (xy 3.308718 -7.963465)
-      (xy 3.297448 -7.9345)
-      (xy 3.290215 -7.900832)
-      (xy 3.28647 -7.856146)
-      (xy 3.285663 -7.794128)
-      (xy 3.287077 -7.714965)
-      (xy 3.289981 -7.642285)
-      (xy 3.294456 -7.580532)
-      (xy 3.299927 -7.535617)
-      (xy 3.30582 -7.513452)
-      (xy 3.30676 -7.512414)
-      (xy 3.323152 -7.492602)
-      (xy 3.342453 -7.459131)
-      (xy 3.343268 -7.457476)
-      (xy 3.368447 -7.41708)
-      (xy 3.404034 -7.373194)
-      (xy 3.443447 -7.332522)
-      (xy 3.480105 -7.301768)
-      (xy 3.507426 -7.287637)
-      (xy 3.510262 -7.287366)
-      (xy 3.532232 -7.280287)
-      (xy 3.536165 -7.272452)
-      (xy 3.548154 -7.25932)
-      (xy 3.558368 -7.25765)
-      (xy 3.578161 -7.251625)
-      (xy 3.580686 -7.246549)
-      (xy 3.584613 -7.234331)
-      (xy 3.597789 -7.224306)
-      (xy 3.622729 -7.21627)
-      (xy 3.661948 -7.21002)
-      (xy 3.717959 -7.205353)
-      (xy 3.793277 -7.202065)
-      (xy 3.890414 -7.199953)
-      (xy 4.011887 -7.198815)
-      (xy 4.160208 -7.198445)
-      (xy 4.175596 -7.198443)
-      (xy 4.690711 -7.198443)
-      (xy 4.690711 -6.858)
-      (xy 4.180046 -6.858)
-      (xy 4.028418 -6.858425)
-      (xy 3.902325 -6.859685)
-      (xy 3.802573 -6.861755)
-      (xy 3.729966 -6.864614)
-      (xy 3.685309 -6.868237)
-      (xy 3.669409 -6.872601)
-      (xy 3.669382 -6.872802)
-      (xy 3.65637 -6.882586)
-      (xy 3.624375 -6.887476)
-      (xy 3.617576 -6.887604)
-      (xy 3.583321 -6.890416)
-      (xy 3.566212 -6.897331)
-      (xy 3.565769 -6.898792)
-      (xy 3.552736 -6.912163)
-      (xy 3.518653 -6.929664)
-      (xy 3.471042 -6.947682)
-      (xy 3.451055 -6.953888)
-      (xy 3.425216 -6.965909)
-      (xy 3.41775 -6.975686)
-      (xy 3.405796 -6.990172)
-      (xy 3.391847 -6.997128)
-      (xy 3.358563 -7.012094)
-      (xy 3.332906 -7.02599)
-      (xy 3.30758 -7.045049)
-      (xy 3.271418 -7.077214)
-      (xy 3.229827 -7.11702)
-      (xy 3.188218 -7.159004)
-      (xy 3.151998 -7.1977)
-      (xy 3.126578 -7.227644)
-      (xy 3.117367 -7.243372)
-      (xy 3.117425 -7.243676)
-      (xy 3.11005 -7.260227)
-      (xy 3.091522 -7.280385)
-      (xy 3.069528 -7.307248)
-      (xy 3.062506 -7.326553)
-      (xy 3.053824 -7.344732)
-      (xy 3.047879 -7.346462)
-      (xy 3.036642 -7.359545)
-      (xy 3.026313 -7.392242)
-      (xy 3.023784 -7.405669)
-      (xy 3.015016 -7.442674)
-      (xy 3.004588 -7.463324)
-      (xy 3.001406 -7.464877)
-      (xy 2.992872 -7.477894)
-      (xy 2.988607 -7.509902)
-      (xy 2.988496 -7.516683)
-      (xy 2.984779 -7.550926)
-      (xy 2.975637 -7.568042)
-      (xy 2.973694 -7.56849)
-      (xy 2.967282 -7.58274)
-      (xy 2.962514 -7.62335)
-      (xy 2.959646 -7.687108)
-      (xy 2.958893 -7.753513)
-      (xy 2.960033 -7.833666)
-      (xy 2.963281 -7.893272)
-      (xy 2.968382 -7.92912)
-      (xy 2.973694 -7.938536)
-      (xy 2.982522 -7.951766)
-      (xy 2.987817 -7.985239)
-      (xy 2.988496 -8.005145)
-      (xy 2.991061 -8.044873)
-      (xy 2.997551 -8.0687)
-      (xy 3.001406 -8.071753)
-      (xy 3.011566 -8.084828)
-      (xy 3.021294 -8.117507)
-      (xy 3.023784 -8.13096)
-      (xy 3.032935 -8.167976)
-      (xy 3.044315 -8.188622)
-      (xy 3.047879 -8.190168)
-      (xy 3.060529 -8.202294)
-      (xy 3.062506 -8.214439)
-      (xy 3.073539 -8.242352)
-      (xy 3.088409 -8.257652)
-      (xy 3.109337 -8.278984)
-      (xy 3.114312 -8.291209)
-      (xy 3.124737 -8.311994)
-      (xy 3.151624 -8.344937)
-      (xy 3.188397 -8.38361)
-      (xy 3.228475 -8.421584)
-      (xy 3.265282 -8.452431)
-      (xy 3.292238 -8.469722)
-      (xy 3.298711 -8.471403)
-      (xy 3.313599 -8.481118)
-      (xy 3.314137 -8.484558)
-      (xy 3.327071 -8.495656)
-      (xy 3.358898 -8.505988)
-      (xy 3.365944 -8.507431)
-      (xy 3.400104 -8.517369)
-      (xy 3.417272 -8.529275)
-      (xy 3.41775 -8.531282)
-      (xy 3.429749 -8.543822)
-      (xy 3.439953 -8.545413)
-      (xy 3.459661 -8.552735)
-      (xy 3.462156 -8.558952)
-      (xy 3.475752 -8.566433)
-      (xy 3.511804 -8.574131)
-      (xy 3.56321 -8.580628)
-      (xy 3.57687 -8.581838)
-      (xy 3.635317 -8.588096)
-      (xy 3.684437 -8.596051)
-      (xy 3.714845 -8.604135)
-      (xy 3.717287 -8.605303)
-      (xy 3.739238 -8.609484)
-      (xy 3.786048 -8.613174)
-      (xy 3.852971 -8.616177)
-      (xy 3.935265 -8.618299)
-      (xy 4.028185 -8.619346)
-      (xy 4.061431 -8.619422)
-      (xy 4.379872 -8.619422)
-      (xy 4.379872 -9.270704)
-      (xy 3.0181 -9.270704)
-      (xy 3.0181 -9.611147)
-      (xy 4.690028 -9.611147)
-      (xy 4.69407 -9.348414)
-      (xy 4.695043 -9.257545)
-      (xy 4.695583 -9.145023)
-      (xy 4.695691 -9.018794)
-      (xy 5.016352 -9.018794)
-      (xy 5.016352 -9.611147)
-      (xy 5.171771 -9.611147)
-      (xy 5.247236 -9.609717)
-      (xy 5.299044 -9.605591)
-      (xy 5.324757 -9.599009)
-      (xy 5.327191 -9.595672)
-      (xy 5.336823 -9.575655)
-      (xy 5.360392 -9.547078)
-      (xy 5.364196 -9.543193)
-      (xy 5.389113 -9.513485)
-      (xy 5.401028 -9.48986)
-      (xy 5.4012 -9.487926)
-      (xy 5.412109 -9.46593)
-      (xy 5.430804 -9.448326)
-      (xy 5.453715 -9.425084)
-      (xy 5.460408 -9.408727)
-      (xy 5.470115 -9.386723)
-      (xy 5.493842 -9.357115)
-      (xy 5.497412 -9.35346)
-      (xy 5.522049 -9.326596)
-      (xy 5.53416 -9.309021)
-      (xy 5.534417 -9.307736)
-      (xy 5.54353 -9.292193)
-      (xy 5.565997 -9.265053)
-      (xy 5.571422 -9.259108)
-      (xy 5.595767 -9.229896)
-      (xy 5.608064 -9.209354)
-      (xy 5.608426 -9.207301)
-      (xy 5.617621 -9.189557)
-      (xy 5.640262 -9.161186)
-      (xy 5.645431 -9.155495)
-      (xy 5.669872 -9.12534)
-      (xy 5.682109 -9.102806)
-      (xy 5.682436 -9.100447)
-      (xy 5.693197 -9.081718)
-      (xy 5.719108 -9.057767)
-      (xy 5.71944 -9.057517)
-      (xy 5.745527 -9.03285)
-      (xy 5.756445 -9.012436)
-      (xy 5.756445 -9.012367)
-      (xy 5.766355 -8.991916)
-      (xy 5.791055 -8.962241)
-      (xy 5.800324 -8.952968)
-      (xy 5.826145 -8.924418)
-      (xy 5.837795 -8.903719)
-      (xy 5.837434 -8.899975)
-      (xy 5.843425 -8.884795)
-      (xy 5.866749 -8.860801)
-      (xy 5.87483 -8.854134)
-      (xy 5.903852 -8.824721)
-      (xy 5.918652 -8.797039)
-      (xy 5.919131 -8.792879)
-      (xy 5.930159 -8.766013)
-      (xy 5.941468 -8.757992)
-      (xy 5.961147 -8.73896)
-      (xy 5.963671 -8.728146)
-      (xy 5.973794 -8.704146)
-      (xy 5.998392 -8.674682)
-      (xy 6.000676 -8.672525)
-      (xy 6.025831 -8.64542)
-      (xy 6.037568 -8.625304)
-      (xy 6.03768 -8.624094)
-      (xy 6.048546 -8.604484)
-      (xy 6.074086 -8.578677)
-      (xy 6.103719 -8.555918)
-      (xy 6.12686 -8.545448)
-      (xy 6.127765 -8.545413)
-      (xy 6.146499 -8.555457)
-      (xy 6.176542 -8.580515)
-      (xy 6.210199 -8.612974)
-      (xy 6.239778 -8.645222)
-      (xy 6.257585 -8.669645)
-      (xy 6.259708 -8.675973)
-      (xy 6.269511 -8.69327)
-      (xy 6.294435 -8.722278)
-      (xy 6.311357 -8.739459)
-      (xy 6.341653 -8.771949)
-      (xy 6.360317 -8.797844)
-      (xy 6.363164 -8.80579)
-      (xy 6.372636 -8.824593)
-      (xy 6.39703 -8.856824)
-      (xy 6.423549 -8.887201)
-      (xy 6.474876 -8.943269)
-      (xy 6.509022 -8.981967)
-      (xy 6.529241 -9.007343)
-      (xy 6.538787 -9.023445)
-      (xy 6.540944 -9.033217)
-      (xy 6.550804 -9.051908)
-      (xy 6.575665 -9.081259)
-      (xy 6.58905 -9.094755)
-      (xy 6.617267 -9.125035)
-      (xy 6.632692 -9.147724)
-      (xy 6.633761 -9.153176)
-      (xy 6.641604 -9.169532)
-      (xy 6.665367 -9.197448)
-      (xy 6.681867 -9.213839)
-      (xy 6.712146 -9.244715)
-      (xy 6.730662 -9.26806)
-      (xy 6.733368 -9.274455)
-      (xy 6.743017 -9.291079)
-      (xy 6.767599 -9.320006)
-      (xy 6.785175 -9.338299)
-      (xy 6.815362 -9.371918)
-      (xy 6.834036 -9.399322)
-      (xy 6.836981 -9.408302)
-      (xy 6.847826 -9.429285)
-      (xy 6.873909 -9.45423)
-      (xy 6.873986 -9.454287)
-      (xy 6.900161 -9.480027)
-      (xy 6.910991 -9.502705)
-      (xy 6.92089 -9.525264)
-      (xy 6.945639 -9.556656)
-      (xy 6.955906 -9.56724)
-      (xy 6.978342 -9.58772)
-      (xy 6.999716 -9.600582)
-      (xy 7.02748 -9.607595)
-      (xy 7.069085 -9.610526)
-      (xy 7.131983 -9.611144)
-      (xy 7.14093 -9.611147)
-      (xy 7.281037 -9.611147)
-      (xy 7.281037 -6.858)
-      (xy 8.228356 -6.858)
-      (xy 8.228356 -6.942997)
-      (xy 8.154347 -6.952815)
-      (xy 8.112192 -6.96066)
-      (xy 8.085389 -6.969977)
-      (xy 8.080338 -6.975198)
-      (xy 8.06831 -6.989835)
-      (xy 8.054435 -6.996462)
-      (xy 8.013363 -7.015535)
-      (xy 7.97356 -7.042218)
-      (xy 7.943669 -7.06981)
-      (xy 7.932319 -7.091103)
-      (xy 7.922158 -7.108994)
-      (xy 7.89748 -7.134563)
-      (xy 7.895315 -7.136468)
-      (xy 7.868077 -7.171644)
-      (xy 7.85831 -7.205746)
-      (xy 7.853255 -7.23361)
-      (xy 7.843508 -7.242849)
-      (xy 7.833724 -7.255861)
-      (xy 7.828834 -7.287856)
-      (xy 7.828706 -7.294655)
-      (xy 7.824988 -7.328898)
-      (xy 7.815847 -7.346014)
-      (xy 7.813904 -7.346462)
-      (xy 7.803511 -7.359324)
-      (xy 7.799104 -7.390315)
-      (xy 7.799102 -7.390867)
-      (xy 7.80339 -7.422046)
-      (xy 7.81372 -7.435269)
-      (xy 7.813904 -7.435273)
-      (xy 7.823688 -7.448285)
-      (xy 7.828578 -7.48028)
-      (xy 7.828706 -7.487079)
-      (xy 7.832129 -7.521326)
-      (xy 7.840547 -7.53844)
-      (xy 7.842332 -7.538886)
-      (xy 7.854908 -7.55159)
-      (xy 7.865079 -7.580416)
-      (xy 7.88194 -7.618892)
-      (xy 7.90326 -7.642891)
-      (xy 7.926116 -7.669484)
-      (xy 7.932319 -7.690172)
-      (xy 7.942249 -7.712331)
-      (xy 7.953849 -7.716508)
-      (xy 7.978297 -7.726302)
-      (xy 8.008965 -7.750156)
-      (xy 8.011782 -7.752911)
-      (xy 8.048637 -7.781367)
-      (xy 8.086385 -7.798901)
-      (xy 8.086604 -7.798956)
-      (xy 8.118244 -7.810697)
-      (xy 8.133158 -7.821761)
-      (xy 8.152368 -7.831227)
-      (xy 8.184824 -7.834923)
-      (xy 8.228356 -7.834923)
-      (xy 8.228356 -7.931135)
-      (xy 8.227613 -7.98293)
-      (xy 8.223813 -8.011788)
-      (xy 8.214598 -8.024366)
-      (xy 8.197614 -8.027322)
-      (xy 8.194303 -8.027347)
-      (xy 8.159369 -8.032723)
-      (xy 8.121472 -8.045768)
-      (xy 8.091545 -8.061863)
-      (xy 8.080453 -8.075453)
-      (xy 8.06837 -8.085451)
-      (xy 8.059192 -8.086555)
-      (xy 8.03107 -8.09625)
-      (xy 8.018487 -8.105885)
-      (xy 7.987092 -8.128332)
-      (xy 7.972689 -8.135153)
-      (xy 7.944913 -8.156912)
-      (xy 7.936396 -8.171291)
-      (xy 7.918918 -8.200312)
-      (xy 7.892326 -8.231507)
-      (xy 7.868315 -8.263749)
-      (xy 7.85831 -8.293548)
-      (xy 7.85831 -8.29358)
-      (xy 7.851357 -8.321635)
-      (xy 7.843508 -8.330786)
-      (xy 7.832758 -8.350838)
-      (xy 7.828706 -8.382592)
-      (xy 7.824054 -8.416448)
-      (xy 7.813904 -8.434399)
-      (xy 7.802737 -8.45329)
-      (xy 7.799481 -8.482175)
-      (xy 7.804135 -8.50741)
-      (xy 7.813904 -8.515809)
-      (xy 7.823754 -8.528805)
-      (xy 7.828602 -8.560694)
-      (xy 7.828706 -8.566742)
-      (xy 7.832181 -8.603278)
-      (xy 7.840666 -8.624854)
-      (xy 7.841868 -8.62581)
-      (xy 7.854902 -8.644967)
-      (xy 7.865062 -8.673912)
-      (xy 7.882114 -8.712905)
-      (xy 7.901033 -8.73696)
-      (xy 7.926337 -8.766927)
-      (xy 7.936711 -8.786279)
-      (xy 7.958281 -8.813967)
-      (xy 7.972689 -8.822455)
-      (xy 8.006414 -8.841625)
-      (xy 8.018487 -8.851723)
-      (xy 8.046031 -8.868464)
-      (xy 8.059192 -8.871054)
-      (xy 8.0783 -8.877343)
-      (xy 8.080453 -8.882155)
-      (xy 8.093273 -8.896957)
-      (xy 8.124178 -8.912984)
-      (xy 8.162233 -8.925614)
-      (xy 8.194303 -8.930261)
-      (xy 8.212778 -8.932411)
-      (xy 8.222993 -8.943341)
-      (xy 8.227375 -8.969772)
-      (xy 8.228353 -9.018426)
-      (xy 8.228356 -9.024566)
-      (xy 8.228356 -9.118872)
-      (xy 8.154347 -9.128689)
-      (xy 8.112183 -9.136846)
-      (xy 8.085381 -9.146958)
-      (xy 8.080338 -9.152799)
-      (xy 8.068341 -9.165481)
-      (xy 8.058135 -9.167091)
-      (xy 8.03842 -9.173844)
-      (xy 8.035932 -9.179562)
-      (xy 8.024121 -9.193827)
-      (xy 7.994714 -9.213967)
-      (xy 7.984126 -9.219933)
-      (xy 7.951208 -9.241368)
-      (xy 7.933369 -9.260198)
-      (xy 7.932319 -9.264)
-      (xy 7.922076 -9.284045)
-      (xy 7.897227 -9.310658)
-      (xy 7.895315 -9.312342)
-      (xy 7.868077 -9.347518)
-      (xy 7.85831 -9.38162)
-      (xy 7.853255 -9.409484)
-      (xy 7.843508 -9.418723)
-      (xy 7.833724 -9.431735)
-      (xy 7.828834 -9.46373)
-      (xy 7.828706 -9.470529)
-      (xy 7.824988 -9.504772)
-      (xy 7.815847 -9.521888)
-      (xy 7.813904 -9.522336)
-      (xy 7.803511 -9.535198)
-      (xy 7.799104 -9.566189)
-      (xy 7.799102 -9.566741)
-      (xy 7.80339 -9.59792)
-      (xy 7.81372 -9.611144)
-      (xy 7.813904 -9.611147)
-      (xy 7.823688 -9.624159)
-      (xy 7.828578 -9.656155)
-      (xy 7.828706 -9.662953)
-      (xy 7.832129 -9.6972)
-      (xy 7.840547 -9.714314)
-      (xy 7.842332 -9.71476)
-      (xy 7.854387 -9.727584)
-      (xy 7.865597 -9.758861)
-      (xy 7.866523 -9.762865)
-      (xy 7.882057 -9.802449)
-      (xy 7.904614 -9.83025)
-      (xy 7.904704 -9.830313)
-      (xy 7.926696 -9.852862)
-      (xy 7.932319 -9.867653)
-      (xy 7.944232 -9.885518)
-      (xy 7.973861 -9.907665)
-      (xy 7.984126 -9.91355)
-      (xy 8.016961 -9.934076)
-      (xy 8.034837 -9.950782)
-      (xy 8.035932 -9.953921)
-      (xy 8.047954 -9.964994)
-      (xy 8.058135 -9.966392)
-      (xy 8.077837 -9.974114)
-      (xy 8.080338 -9.980684)
-      (xy 8.093612 -9.990587)
-      (xy 8.127563 -10.000266)
-      (xy 8.154347 -10.004793)
-      (xy 8.198211 -10.011956)
-      (xy 8.220128 -10.021757)
-      (xy 8.227634 -10.039493)
-      (xy 8.228356 -10.056793)
-      (xy 8.224452 -10.077179)
-      (xy 8.210894 -10.102561)
-      (xy 8.184913 -10.136412)
-      (xy 8.143739 -10.182206)
-      (xy 8.084604 -10.243416)
-      (xy 8.058764 -10.269513)
-      (xy 7.889172 -10.440051)
-      (xy 2.380361 -10.440051)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 18c59b37-ed1a-4d02-b290-99c18a5d39c7))
-  (fp_line (start -8.999998 -10.999996) (end -7.999995 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp c23bf165-0460-4698-8aa9-e981b740fa55))
-  (fp_line (start -8.999998 11) (end -8.999998 -10.999996)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 823e8fe5-35aa-4f78-b48d-d3cf7f3aa9ce))
-  (fp_line (start -8.999998 11) (end -7.999995 12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp a31c1228-3810-4119-82ac-629412659676))
-  (fp_line (start -7.999995 -12) (end -6.999997 -12.000002)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp a76d306e-2091-4594-b991-4a483794b4fa))
-  (fp_line (start -7.999995 12) (end 8.000003 12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp cf5f0b79-d9cb-4d10-b7dc-862d8f901aab))
-  (fp_line (start -7 -11) (end -6.999997 -12.000002)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp d0893799-6be2-487f-a501-c5e3f81829ff))
-  (fp_line (start -7 -11) (end -5 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 393bc6ef-c5b4-46e2-9817-5c98bb01554c))
-  (fp_line (start -5 -11.999997) (end 5 -11.999997)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp f203458d-33ef-4249-a043-9ea0d405ac12))
-  (fp_line (start -5 -11) (end -5 -11.999997)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp c46e828a-8e15-4a5e-a57b-46a09533806d))
-  (fp_line (start -4.46999 6.595008) (end 4.469997 6.595008)
-    (stroke (width 0.1) (type solid)) (layer "F.SilkS") (tstamp c2d17a51-9c78-4def-98fd-97426977e472))
-  (fp_line (start -4.46999 6.595008) (end 4.469997 6.595008)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp 746513e4-5cc1-4831-b6f4-e1c51144dbe5))
-  (fp_line (start -4.46999 13.945006) (end -4.46999 6.595008)
-    (stroke (width 0.1) (type solid)) (layer "F.SilkS") (tstamp 08a36a54-7220-4d98-897d-c97c65eb6990))
-  (fp_line (start -4.46999 13.945006) (end -4.46999 6.595008)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp dd508c05-b2c5-43da-a53b-b814bc019a34))
-  (fp_line (start -4.46999 13.945006) (end 4.469997 13.945006)
-    (stroke (width 0.1) (type solid)) (layer "F.SilkS") (tstamp f52cda2d-336e-4265-ad05-1a8bc580842e))
-  (fp_line (start -4.46999 13.945006) (end 4.469997 13.945006)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp e63e8a38-dd85-4f7e-8cff-06d5f850df61))
-  (fp_line (start 4.469997 13.945006) (end 4.469997 6.595008)
-    (stroke (width 0.1) (type solid)) (layer "F.SilkS") (tstamp b8dc2733-e522-4422-837e-d57ccc5cb82c))
-  (fp_line (start 4.469997 13.945006) (end 4.469997 6.595008)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp 2028d6d2-551f-46d0-b5c0-ba2eb63425e0))
-  (fp_line (start 5 -11) (end 5 -11.999997)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 60fc26a8-1d0a-4985-b730-ae82cb61fdf3))
-  (fp_line (start 5 -11) (end 7.000003 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 25730d44-5f19-45ed-ba03-537ec276b468))
-  (fp_line (start 7.000003 -12) (end 8 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp f2b02e13-3ab8-41fa-ad86-26316fb7b2f3))
-  (fp_line (start 7.000003 -11) (end 7.000003 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 10989a02-b101-4988-9b9b-c60660c7978a))
-  (fp_line (start 8 -12) (end 9 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 062bb881-727e-423e-974f-cf25e8926069))
-  (fp_line (start 8.000003 12) (end 9 11.000003)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 6056d5d8-e31b-4b96-9983-c4755b193cfc))
-  (fp_line (start 9 11.000003) (end 9 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 146ac7bc-b86b-4704-8510-74f07bea71ea))
-  (fp_line (start -6.985 1.350002) (end -5.530005 1.350009)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp be459956-2090-42ee-ac2c-4043a297ea82))
-  (fp_line (start -6.985 11.349987) (end -5.530003 11.349984)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 9413ae12-f7c6-44ad-9c5c-5c2db253651b))
-  (fp_line (start -6.527997 -11.494397) (end 8.712003 -11.494397)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp d601ce19-ed42-4559-9dc7-5faeed9f06c4))
-  (fp_line (start -6.527997 -4.636397) (end -6.527997 -11.494397)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp 62784952-6018-4573-bc63-9409f77c6410))
-  (fp_line (start -6.527997 -4.636397) (end 8.712003 -4.636395)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp 07663527-9c47-4f49-ab6e-13b6677a0621))
-  (fp_line (start -5.530005 1.350009) (end -5.530003 11.349984)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 09ecd01e-6427-4179-9031-1a8562ab66e6))
-  (fp_line (start -5.530005 1.350009) (end -5.530003 11.349984)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 1c779381-49f0-4cc0-8275-f5ac0576e377))
-  (fp_line (start -4.954982 11.315031) (end -3.68498 11.315031)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp b2461b15-a859-46b6-97a2-cdf5b7f427ab))
-  (fp_line (start -4.954975 7.13504) (end -3.68497 7.135042)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 7d12f0cd-de40-48b2-abdf-4b4c426205d2))
-  (fp_line (start -4.31998 11.950031) (end -4.31998 10.680031)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 2b1d2e90-bd78-47f5-98d3-150142da61ae))
-  (fp_line (start -4.319972 7.770045) (end -4.319972 6.500042)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 9e4864f2-75f7-4105-ba2d-2027c3972a7c))
-  (fp_line (start -4.115 -10.223998) (end -2.844994 -10.223996)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 7c3817fb-e9de-4581-b851-9b0aa93236ac))
-  (fp_line (start -4.115 -6.413998) (end -2.844997 -6.413998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp e12bb261-dda4-4118-99a5-b7883931269a))
-  (fp_line (start -3.524983 7.664983) (end -2.25498 7.664983)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 729fa814-9a6b-43ee-b375-2412a4aada05))
-  (fp_line (start -3.48 -10.858998) (end -3.479997 -9.588998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp b07c79f8-a691-49a3-96ce-576e09d3dcd4))
-  (fp_line (start -3.479997 -5.778998) (end -3.479997 -7.048998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp a1d482b8-f335-4a64-a0f0-a34ae26cdd14))
-  (fp_line (start -2.88998 8.299983) (end -2.88998 7.029983)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 34996d06-3f4d-4285-91c5-48c87e3b4d4b))
-  (fp_line (start -1.915 -10.223998) (end -0.644996 -10.223998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 950c4ddf-8c77-49df-b139-a2cec0c738a4))
-  (fp_line (start -1.279996 -9.588998) (end -1.279996 -10.858998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 3d234cfd-0d11-45d8-8f1b-adaeed5f37a7))
-  (fp_line (start -0.635004 0) (end 0.635 0.000002)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp dd400af6-673e-4ca9-8aa7-ba6a96048e9b))
-  (fp_line (start 0 0.635) (end 0 -0.635)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 52825964-6eca-4d9d-850e-0eae3be9efca))
-  (fp_line (start 2.255034 7.664985) (end 3.525036 7.664985)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 15f78edd-10fb-4102-b1cf-0272f27237ab))
-  (fp_line (start 2.890036 8.299985) (end 2.890036 7.029985)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp ef592fac-95e2-41a7-be99-e414ec3f7862))
-  (fp_line (start 3.465 -0.299998) (end 4.735 -0.3)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 61f0a8db-3ce7-4e8f-b2f8-39d3ef5459da))
-  (fp_line (start 3.684982 11.315029) (end 4.954985 11.315029)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 39cd3b9a-077c-4748-a482-4644e8784abf))
-  (fp_line (start 3.684995 7.135037) (end 4.954998 7.135037)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 4f983513-974c-4242-a125-4f77255e9d97))
-  (fp_line (start 3.865 4) (end 5.135002 4)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp e6e270b8-9f91-44de-bb79-97b620bbb8fd))
-  (fp_line (start 4.1 0.335) (end 4.1 -0.935003)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp aff2fd1d-9565-42dc-8f8b-aa8f9412e35b))
-  (fp_line (start 4.319985 10.680029) (end 4.319988 11.950029)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 741367f4-c727-4956-94f4-68141578ee04))
-  (fp_line (start 4.319998 7.770037) (end 4.319998 6.500037)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp bbb98350-c2fa-43e2-b0fd-f56fc259bd69))
-  (fp_line (start 4.500002 4.635) (end 4.500002 3.365)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp c794179b-d25d-4d5d-9976-2d4ac519b560))
-  (fp_line (start 6.585002 -6.414397) (end 7.855002 -6.414397)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 2f053613-8fae-43d1-b823-65433d6fb218))
-  (fp_line (start 7.220002 -5.779395) (end 7.220002 -7.049397)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 12251469-782e-49ad-b486-6ee14d2420dc))
-  (fp_line (start 8.712003 -4.636395) (end 8.712003 -11.494397)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp 990255fb-990b-4baa-9101-fbaeeffcf295))
-  (pad "1" thru_hole oval (at -7.62 -10.160003) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 791df21b-3d6c-4479-8330-1a0b2f10c864))
-  (pad "2" thru_hole oval (at -7.62 -8.89) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp c7faacf3-1f90-412c-a046-83ff3dc2eb46))
-  (pad "3" thru_hole oval (at -7.62 -7.619998) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 9e1a628e-7c80-4cc7-a5dc-baffe55f1f7d))
-  (pad "4" thru_hole oval (at -7.62 -6.349998) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 9d9267f7-1729-498b-9f6f-b294dce858a1))
-  (pad "5" thru_hole oval (at -7.62 -5.08) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 9a736208-e6e1-46c3-a9f9-c86c628de7c7))
-  (pad "6" thru_hole oval (at -7.62 -3.809998) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 0d89a723-3f5c-4197-9372-54b54f8d7383))
-  (pad "7" thru_hole oval (at -7.62 -2.54) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp c8441c97-ed3f-4d8c-979e-8c890db1a078))
-  (pad "8" thru_hole oval (at -7.62 -1.269998) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 8ac9a96e-3829-4c44-b9db-9b8ee11dd470))
-  (pad "9" thru_hole oval (at -7.62 0.000002) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp e6f9bc0a-83c0-46b8-a6f4-717f80d42d0b))
-  (pad "10" thru_hole oval (at -7.62 1.270002) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 66eb12d1-da13-4acd-902e-209e9dd3a566))
-  (pad "11" thru_hole oval (at -7.62 2.54) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 0c6d6943-73fb-4ff2-b6f3-6a3631f94dd0))
-  (pad "12" thru_hole oval (at -7.62 3.81) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 3001fd83-beec-4b48-9da8-47f41738b1b8))
-  (pad "13" thru_hole oval (at -7.62 5.08) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp cc39538c-91a0-4f4c-a039-44bb8879c7da))
-  (pad "14" thru_hole oval (at -7.62 6.350002) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp cfbacc80-7cf8-429a-84dc-9badee9359a6))
-  (pad "15" thru_hole oval (at -7.62 7.62) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp ae133282-5d41-497a-a7f7-4e032654e7d2))
-  (pad "16" thru_hole oval (at -7.62 8.890002) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 7b3c0fce-7d1a-4f9f-a250-26210260252f))
-  (pad "17" thru_hole oval (at -7.62 10.16) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 6b639323-d242-4b3b-b5e5-0aea74d5855c))
-  (pad "18" thru_hole oval (at 7.62 10.160004 180) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 19f581aa-62bf-4fb5-9ea6-d5f22f68533b))
-  (pad "19" thru_hole oval (at 7.62 8.890002) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 1ad04c4f-3fa6-415b-aa39-5ec1e350a3fc))
-  (pad "20" thru_hole oval (at 7.62 7.620004 180) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 2ebdd747-9c06-49dc-8477-8a955bcd84b9))
-  (pad "21" thru_hole oval (at 7.62 6.350002) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 8a32284e-4cb9-417b-9a52-72b3212cf533))
-  (pad "22" thru_hole oval (at 7.62 5.080007 180) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 72aeb21d-a007-4781-a362-efee8fe2d36d))
-  (pad "23" thru_hole oval (at 7.62 3.81) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 1ce97e23-4077-4281-8142-c61fa3a9be6f))
-  (pad "24" thru_hole oval (at 7.62 2.540004 180) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 04f87d29-4b75-4820-9f51-76a648b1cde7))
-  (pad "25" thru_hole oval (at 7.62 1.270002) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp f9b02f99-d454-4c5c-8892-6ac11fce5183))
-  (pad "26" thru_hole oval (at 7.62 0.000004 180) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp cecac873-4fc6-47c9-929b-5551b14231e5))
-  (pad "27" thru_hole oval (at 7.62 -1.27) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask")
-    (solder_mask_margin 0.1016) (tstamp 0dfaff5c-fa54-4e1e-aea4-5d80076bfe6e))
-  (pad "28" thru_hole oval (at 7.62 -2.539996 180) (size 1 0.8) (drill 0.55) (layers "*.Cu" "*.Mask") (tstamp 9e4ea63c-6cfb-474a-b9c6-f611d0b3eb9b))
-  (group "" (id 2e2c32c9-9596-4edb-80a5-7506e0f55dfe)
-    (members
-      01759509-2722-4a22-8621-c8215ba48fbd
-      02166560-fc83-4b98-ad86-4f75cfc04e71
-      0442654b-3393-4798-b56e-5abbba440c2e
-      0d5a352e-f7d8-40f5-bf13-391c6c92a108
-      0fc04686-f385-4136-b1ed-96815229ea7f
-      10ecde5a-92ae-47a6-8dc6-d97767da1efe
-      11186e3e-5f4a-4169-8f2b-7f3e5bd24918
-      11e5d550-8ce0-4194-bc6e-50c6304e6f24
-      12bcf80f-3e76-4bfa-a66a-88322f240ebf
-      17a65922-fefd-4aeb-8969-b9336021b6bf
-      18c59b37-ed1a-4d02-b290-99c18a5d39c7
-      19abbea2-e42c-4827-a17c-a2569e8e2c04
-      19c896ae-7d37-4399-89c9-01c4a1f21fc7
-      1c61b283-26a9-46c1-8a00-f29e6facd995
-      1d3a51e7-3f56-4ed2-9e64-5e0281ab475f
-      26d9d795-659a-4c3b-9475-75c142dc4af3
-      27c2e63c-c7a2-4ed3-b7b0-a537751b114b
-      27e94ff8-3b81-4d85-95f2-f6d220fd0122
-      2cb66163-632c-4203-b8a3-32ebdf6ed2cd
-      30d3c4dc-9a70-4545-995c-17c307274103
-      30fb5104-820e-4974-8f9e-cc081cfbbad1
-      31981ea9-5b82-41f2-b2d1-eaa70c62826c
-      322ee281-3523-4fac-b06d-2aef62c11904
-      32a6e9d7-a981-4f4f-a38c-9dc4a8c9ba00
-      336078d2-ed55-4f72-ae80-e07d40609b29
-      37569d0e-0c8a-4768-b17f-746c6692f82d
-      3b39cdd1-cc85-4052-bd8c-04713d7055ca
-      3fd098af-9969-44b8-8398-07b02e68e34b
-      48737cf6-b6af-49a7-a3f4-c37a29b37c0c
-      4ababfc3-2d1e-4d9b-8c15-ab51bae3529f
-      4f7ea564-4702-445a-9479-8306fc9d893f
-      4fe1d722-c965-4031-a29f-a253b0039749
-      5302e35f-39e1-4d93-8bbd-8061922f4720
-      544b1a13-1dc9-4c3b-ab3a-06afb75cc6d1
-      55b2f941-f545-4df8-9edb-cc3f83159180
-      584adb05-92b6-498b-96a8-d89b1d726549
-      5cbb7acc-b138-4547-a5cf-0d9124a5ca43
-      5d14ded3-ebed-4c5e-a06f-05c53bcb9d07
-      5e882282-635a-4d69-95e2-d1f643cfb8f2
-      5f04069b-81e2-4988-bd93-8327b361a52d
-      60e10e9d-1e1a-401f-90cb-ca5daef1a84d
-      631ae9ed-44c6-4d29-b264-2ec6fbdf93de
-      6677a626-c17a-47d0-9a31-191d0c08ae54
-      67b8c206-43e5-4ddf-a457-cef8799f222f
-      69642b65-a4bc-4591-beed-cd8d19446055
-      69a30b9a-0f8f-4859-b507-ce0ee5676104
-      6a486226-b62f-42ac-9e8d-608561281df4
-      6c0cafe9-ddee-4b34-b3b3-477058d6f7bc
-      6d83362d-674a-4262-8ad6-af9f6bc602bb
-      6dac0c92-0bf1-4539-a4e7-29a649ae4dc4
-      6e27e24e-9ebd-487a-8184-00b42f5d4870
-      6eb88032-5513-4bcb-ad7c-f43593ecc0bb
-      6fdca661-9984-41bd-b3fd-a9d5e9a9ab58
-      70b4ee0a-1746-4797-9b3e-d7e5dabd3b8e
-      72f48921-c34c-4b67-a5bb-b1dcbc63f01a
-      74d25b76-c3a7-41a7-a934-52933e911c59
-      79e2044a-a2dd-40a2-bd7c-60ef93b7a33b
-      7a9bb6d1-043c-4a25-847f-ef70548df104
-      7c530122-c77d-40e9-8798-da5c145067d0
-      81452d39-d598-40db-80a3-fdaab19cb2cd
-      8214243f-07d9-4e32-9ce5-468d787b3cdb
-      848082e4-3d9d-420b-870f-06f0c7729e48
-      8b8e783c-5e19-4f18-a7ba-a648e46b66c7
-      8e8e073f-f28c-4a8c-98bd-39ec815b8993
-      8ef3c2d0-4a8e-4699-b119-5b215d850525
-      932fa28f-a3a8-4264-a152-97b489abd80a
-      9521f759-ce2f-426c-b7e4-acb1db01af58
-      9b1d2a1f-16b8-4f13-af80-ca5035fc8a0b
-      9eccf5b5-6d41-40ce-929b-1b3dd0e7f418
-      a4967312-bbb6-4441-9bd5-dca5386c94cb
-      a6941334-7034-497c-8a20-52aecbb7900c
-      aa514cd8-191a-4515-ae42-84e65eabf5d9
-      ac1e9013-91ba-4d04-8d11-834f881bb8e8
-      acdd851c-3665-414c-9f35-05f10e11aa9d
-      af1b774e-776a-4794-b122-33417304b335
-      afcd4397-6dd8-46be-8368-e1345145ff52
-      b0452eba-fd24-498d-adfb-4f313e153f15
-      b0d3ed8c-5f3d-45a1-a500-ae4c9916283c
-      b1db3629-a22a-4eed-b31d-2a0ada097e39
-      b1df1db6-c8a4-40b7-ab49-82943d193676
-      b75ec21e-4555-4046-8a5c-1aeb48d38187
-      b876731e-87d9-4ffb-9b7a-01f50eef7157
-      bc3f0bf6-28f2-4440-b028-2dd6afa4e574
-      c01dcac8-f060-491f-9e0d-be52189df53a
-      c3fa97af-5933-4d5c-9a48-f3ebe76c58ee
-      c48ff879-ad4f-4090-b3be-06319ac39015
-      c609b32d-d191-4d04-ae2f-0cca69908168
-      c8309b40-4946-4ab3-8617-d2a9bb13b74d
-      cb739b07-43eb-4e36-a6a8-d72374db25fe
-      cf70367d-992a-47eb-ba66-e009380700af
-      d1dd79ad-47a7-43bf-bfc4-080710b83397
-      d47e7a32-1b4a-4380-b6ef-0b380fed6f9a
-      d4aa9b0c-8121-4e28-8a48-ec6754d82ee0
-      db5af78e-b317-464d-987c-02ca43beec76
-      e14360af-43cb-485f-a4ff-263917982970
-      e675c340-2e81-43d8-9217-88a9b3e94aa1
-      ebca5cb1-6469-405a-8a34-b68ff0c08fbc
-      ed7644e4-3607-4c85-9fef-f8c4ef2c1603
-      eda9d8b4-0edc-4d9a-a912-4df73dc770f0
-      f1569867-b13c-456f-a0a8-104ec866d6f1
-      f387e312-68a4-4324-b185-de8bf6963734
-      f5c14ceb-6788-40cb-8f0f-a940ffa26146
-      f7ebaef7-8e7f-4928-9d91-f9c08e3b8787
-      f7eeec86-c5f2-4572-9e33-af5a37c45b52
-      f9dc2e63-0848-4a7d-a10b-eeb320aac8c8
-      fa8f8799-64b8-451d-a12d-e63649d3b682
-      fcecab74-1485-476f-b781-bc2b3450b9f6
-    )
-  )
-  (model "${KICAD6_3DMODEL_DIR}/Connector_PinHeader_1.27mm.3dshapes/PinHeader_1x17_P1.27mm_Vertical.step"
-    (offset (xyz -7.62 10.16 4))
-    (scale (xyz 1 1 1))
-    (rotate (xyz 0 0 0))
-  )
-  (model "${KICAD6_3DMODEL_DIR}/Connector_PinHeader_1.27mm.3dshapes/PinHeader_1x11_P1.27mm_Vertical.step"
-    (offset (xyz 7.62 2.54 4))
-    (scale (xyz 1 1 1))
-    (rotate (xyz 0 0 0))
-  )
-  (model "${KICAD6_3DMODEL_DIR}/Connector_PinSocket_1.27mm.3dshapes/PinSocket_1x17_P1.27mm_Vertical.step"
-    (offset (xyz -7.62 10.16 -0.5))
-    (scale (xyz 1 1 1))
-    (rotate (xyz 0 0 0))
-  )
-  (model "${KICAD6_3DMODEL_DIR}/Connector_PinSocket_1.27mm.3dshapes/PinSocket_1x11_P1.27mm_Vertical.step"
-    (offset (xyz 7.62 2.54 -0.5))
-    (scale (xyz 1 1 1))
-    (rotate (xyz 0 0 0))
-  )
-  (model "${KICAD_M5STACK}/M5KiCad.3d/M5STAMP-S3.step"
-    (offset (xyz 0 0 6.1))
-    (scale (xyz 1 1 1))
-    (rotate (xyz 0 0 0))
-  )
-)
diff --git a/components/m5stack/stamp-s3/artifacts/Stamp-S3-SMD.kicad_mod b/components/m5stack/stamp-s3/artifacts/Stamp-S3-SMD.kicad_mod
deleted file mode 100644
index 56a8ea7..0000000
--- a/components/m5stack/stamp-s3/artifacts/Stamp-S3-SMD.kicad_mod
+++ /dev/null
@@ -1,11852 +0,0 @@
-(footprint "STAMP-S3-SMD" (version 20221018) (generator pcbnew)
-  (layer "F.Cu")
-  (descr "https://docs.m5stack.com/en/core/StampS3")
-  (tags "stamp-s3,esp32-s3")
-  (fp_text reference "REF**" (at -9.3566 -12.8168 unlocked) (layer "F.SilkS")
-      (effects (font (size 1 1) (thickness 0.15)) (justify left bottom))
-    (tstamp 4011d71a-cb5b-4559-9a80-9c655fd197dc)
-  )
-  (fp_text value "STAMP-S3-SMD" (at -9.271 16.51 unlocked) (layer "F.SilkS")
-      (effects (font (size 1 1) (thickness 0.15)) (justify left bottom))
-    (tstamp 02abceed-da80-4ef8-a283-458910069b9b)
-  )
-  (fp_poly
-    (pts
-      (xy 0.091924 4.423505)
-      (xy 0.05076 4.438518)
-      (xy 0.030001 4.46658)
-      (xy 0.025373 4.500463)
-      (xy 0.0326 4.540878)
-      (xy 0.056972 4.566235)
-      (xy 0.102528 4.579022)
-      (xy 0.157532 4.581873)
-      (xy 0.247401 4.581873)
-      (xy 0.247401 4.419053)
-      (xy 0.157532 4.419053)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f66540a3-a6fa-42a9-ae4b-244d24f899bd))
-  (fp_poly
-    (pts
-      (xy 1.501859 3.072101)
-      (xy 1.44601 3.076058)
-      (xy 1.406491 3.090364)
-      (xy 1.383444 3.107128)
-      (xy 1.350525 3.148229)
-      (xy 1.344633 3.187884)
-      (xy 1.363265 3.222572)
-      (xy 1.403915 3.248774)
-      (xy 1.46408 3.262971)
-      (xy 1.495412 3.264507)
-      (xy 1.579569 3.264507)
-      (xy 1.579569 3.072083)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d663090d-102e-43bf-ac9b-cab6d1b781a7))
-  (fp_poly
-    (pts
-      (xy 6.182949 4.803901)
-      (xy 6.493788 4.803901)
-      (xy 6.493788 4.95192)
-      (xy 6.212552 4.95192)
-      (xy 6.212552 5.085137)
-      (xy 6.493788 5.085137)
-      (xy 6.493788 5.247957)
-      (xy 6.168147 5.247957)
-      (xy 6.168147 5.395976)
-      (xy 6.686212 5.395976)
-      (xy 6.686212 4.670684)
-      (xy 6.182949 4.670684)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ec5ef42d-4666-48c2-8226-c11dd2243a11))
-  (fp_poly
-    (pts
-      (xy -0.899744 5.943645)
-      (xy -0.849818 5.993757)
-      (xy -0.808383 6.03526)
-      (xy -0.779383 6.064209)
-      (xy -0.766762 6.07666)
-      (xy -0.766527 6.076862)
-      (xy -0.756502 6.067023)
-      (xy -0.729547 6.040136)
-      (xy -0.689608 6.000146)
-      (xy -0.640629 5.950997)
-      (xy -0.63331 5.943645)
-      (xy -0.500711 5.810428)
-      (xy -1.032343 5.810428)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c53ba1e0-69e2-4e58-9ff0-6182d4940429))
-  (fp_poly
-    (pts
-      (xy 1.463337 2.7932)
-      (xy 1.436541 2.799215)
-      (xy 1.43155 2.803923)
-      (xy 1.419232 2.817743)
-      (xy 1.401946 2.82474)
-      (xy 1.3777 2.843515)
-      (xy 1.372343 2.871929)
-      (xy 1.380289 2.913663)
-      (xy 1.406588 2.939469)
-      (xy 1.454932 2.951767)
-      (xy 1.497101 2.953668)
-      (xy 1.579569 2.953668)
-      (xy 1.579569 2.790848)
-      (xy 1.505559 2.790848)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e90ea281-b3a7-4597-8e21-250a91db8aa0))
-  (fp_poly
-    (pts
-      (xy 0.132847 4.703366)
-      (xy 0.074355 4.706422)
-      (xy 0.039164 4.711326)
-      (xy 0.020971 4.719856)
-      (xy 0.013473 4.733794)
-      (xy 0.01272 4.737293)
-      (xy 0.000421 4.767121)
-      (xy -0.009644 4.777998)
-      (xy -0.017634 4.793357)
-      (xy -0.011632 4.800201)
-      (xy 0.007129 4.82146)
-      (xy 0.019523 4.840906)
-      (xy 0.033347 4.857083)
-      (xy 0.057509 4.866953)
-      (xy 0.099172 4.872509)
-      (xy 0.141638 4.874859)
-      (xy 0.247401 4.879207)
-      (xy 0.247401 4.699043)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp a7cec450-ce12-47c0-908c-5994bf20258d))
-  (fp_poly
-    (pts
-      (xy -2.897995 5.943645)
-      (xy -2.847375 5.993901)
-      (xy -2.804355 6.035482)
-      (xy -2.77314 6.064407)
-      (xy -2.757931 6.076694)
-      (xy -2.75736 6.076862)
-      (xy -2.74438 6.066984)
-      (xy -2.715087 6.040124)
-      (xy -2.673891 6.00044)
-      (xy -2.627535 5.954437)
-      (xy -2.579684 5.905464)
-      (xy -2.540672 5.863875)
-      (xy -2.514651 5.834212)
-      (xy -2.505746 5.82122)
-      (xy -2.519763 5.817748)
-      (xy -2.558676 5.81474)
-      (xy -2.61778 5.812389)
-      (xy -2.692367 5.81089)
-      (xy -2.768171 5.810428)
-      (xy -3.030595 5.810428)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 7ad004ce-c971-4dc7-afe4-5362059426bb))
-  (fp_poly
-    (pts
-      (xy -6.502877 11.265193)
-      (xy -6.546103 11.266909)
-      (xy -6.570913 11.271384)
-      (xy -6.582901 11.279939)
-      (xy -6.587661 11.293896)
-      (xy -6.588766 11.301091)
-      (xy -6.585254 11.335437)
-      (xy -6.561466 11.358461)
-      (xy -6.514656 11.371504)
-      (xy -6.44208 11.37591)
-      (xy -6.435641 11.375929)
-      (xy -6.371738 11.373021)
-      (xy -6.324081 11.365039)
-      (xy -6.303848 11.356598)
-      (xy -6.283533 11.325005)
-      (xy -6.282516 11.301091)
-      (xy -6.285973 11.284668)
-      (xy -6.294476 11.274163)
-      (xy -6.313619 11.268254)
-      (xy -6.348997 11.265619)
-      (xy -6.406202 11.264937)
-      (xy -6.435641 11.264915)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9c890085-ad74-428d-a6d3-881f06be1c83))
-  (fp_poly
-    (pts
-      (xy 1.512783 4.421486)
-      (xy 1.483213 4.427763)
-      (xy 1.475956 4.433855)
-      (xy 1.463967 4.446987)
-      (xy 1.453753 4.448656)
-      (xy 1.434129 4.460505)
-      (xy 1.43155 4.470859)
-      (xy 1.423557 4.490557)
-      (xy 1.416748 4.493062)
-      (xy 1.404722 4.505459)
-      (xy 1.401946 4.522666)
-      (xy 1.408145 4.546718)
-      (xy 1.416748 4.55227)
-      (xy 1.43058 4.563968)
-      (xy 1.431665 4.570772)
-      (xy 1.445311 4.59219)
-      (xy 1.480797 4.610545)
-      (xy 1.530362 4.622834)
-      (xy 1.575119 4.626279)
-      (xy 1.638776 4.626279)
-      (xy 1.638776 4.419053)
-      (xy 1.557366 4.419053)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 84b32b5e-bbd3-43eb-91f5-be668ae54000))
-  (fp_poly
-    (pts
-      (xy -6.354231 -9.805539)
-      (xy -6.19141 -9.805539)
-      (xy -6.19141 -10.307047)
-      (xy -6.150705 -10.285813)
-      (xy -6.094207 -10.264956)
-      (xy -6.050965 -10.269628)
-      (xy -6.01822 -10.300462)
-      (xy -6.008272 -10.318501)
-      (xy -5.993837 -10.361514)
-      (xy -6.001937 -10.386662)
-      (xy -6.033992 -10.396833)
-      (xy -6.047092 -10.397387)
-      (xy -6.06908 -10.403478)
-      (xy -6.072995 -10.410085)
-      (xy -6.084952 -10.423946)
-      (xy -6.114898 -10.443662)
-      (xy -6.128098 -10.45079)
-      (xy -6.171155 -10.475533)
-      (xy -6.207155 -10.500597)
-      (xy -6.2123 -10.504927)
-      (xy -6.249515 -10.523646)
-      (xy -6.297814 -10.530831)
-      (xy -6.354231 -10.530831)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 919a8d8f-94a3-4d63-bc92-149551ce8cf4))
-  (fp_poly
-    (pts
-      (xy -5.62894 6.580125)
-      (xy -5.480921 6.580125)
-      (xy -5.480921 6.387701)
-      (xy -5.479747 6.299372)
-      (xy -5.475989 6.238867)
-      (xy -5.469294 6.204487)
-      (xy -5.459309 6.194535)
-      (xy -5.445679 6.207315)
-      (xy -5.443916 6.210078)
-      (xy -5.420645 6.224512)
-      (xy -5.389342 6.217991)
-      (xy -5.360039 6.19301)
-      (xy -5.356807 6.188396)
-      (xy -5.335986 6.146547)
-      (xy -5.339731 6.119208)
-      (xy -5.36881 6.103287)
-      (xy -5.378441 6.101058)
-      (xy -5.418249 6.085825)
-      (xy -5.463444 6.058558)
-      (xy -5.478026 6.047401)
-      (xy -5.537518 6.01129)
-      (xy -5.580506 6.002852)
-      (xy -5.62894 6.002852)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9283b1ae-a5eb-4a2b-a7ea-64389e499b33))
-  (fp_poly
-    (pts
-      (xy -5.377308 4.049006)
-      (xy -5.229289 4.049006)
-      (xy -5.229289 3.856582)
-      (xy -5.228171 3.772709)
-      (xy -5.22495 3.711012)
-      (xy -5.219832 3.6741)
-      (xy -5.214286 3.664158)
-      (xy -5.190829 3.671315)
-      (xy -5.169225 3.68266)
-      (xy -5.145538 3.692365)
-      (xy -5.126114 3.682468)
-      (xy -5.110548 3.664158)
-      (xy -5.088565 3.626433)
-      (xy -5.082496 3.594952)
-      (xy -5.093066 3.577057)
-      (xy -5.101781 3.575346)
-      (xy -5.139146 3.565142)
-      (xy -5.193254 3.535904)
-      (xy -5.239183 3.505038)
-      (xy -5.282638 3.482561)
-      (xy -5.327068 3.471875)
-      (xy -5.331487 3.471733)
-      (xy -5.377308 3.471733)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 89acbfd9-ed8a-4996-be31-e3bc7d162692))
-  (fp_poly
-    (pts
-      (xy -5.377308 9.111244)
-      (xy -5.229289 9.111244)
-      (xy -5.229289 8.91882)
-      (xy -5.228115 8.830491)
-      (xy -5.224358 8.769986)
-      (xy -5.217663 8.735605)
-      (xy -5.207677 8.725654)
-      (xy -5.194048 8.738434)
-      (xy -5.192285 8.741197)
-      (xy -5.168881 8.75543)
-      (xy -5.136816 8.749926)
-      (xy -5.107211 8.726976)
-      (xy -5.104313 8.723102)
-      (xy -5.083073 8.680605)
-      (xy -5.088321 8.651003)
-      (xy -5.120214 8.633662)
-      (xy -5.12681 8.632177)
-      (xy -5.166617 8.616944)
-      (xy -5.211812 8.589677)
-      (xy -5.226394 8.57852)
-      (xy -5.285886 8.542409)
-      (xy -5.328874 8.533971)
-      (xy -5.377308 8.533971)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 1e962e71-5ad8-4518-9837-71e587a0c0dd))
-  (fp_poly
-    (pts
-      (xy -6.487448 1.517887)
-      (xy -6.339429 1.517887)
-      (xy -6.339429 1.325463)
-      (xy -6.338255 1.237135)
-      (xy -6.334497 1.176629)
-      (xy -6.327803 1.142249)
-      (xy -6.317817 1.132297)
-      (xy -6.304187 1.145078)
-      (xy -6.302424 1.147841)
-      (xy -6.279821 1.163293)
-      (xy -6.251569 1.154651)
-      (xy -6.224246 1.124779)
-      (xy -6.216355 1.110334)
-      (xy -6.198369 1.071122)
-      (xy -6.193243 1.05161)
-      (xy -6.200768 1.044936)
-      (xy -6.214324 1.044228)
-      (xy -6.23811 1.03663)
-      (xy -6.277354 1.016826)
-      (xy -6.318225 0.992421)
-      (xy -6.370517 0.963504)
-      (xy -6.41817 0.944978)
-      (xy -6.443329 0.940615)
-      (xy -6.487448 0.940615)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 933fd734-c4b0-4154-8a2f-6c42689e95e1))
-  (fp_poly
-    (pts
-      (xy -5.290932 2.249057)
-      (xy -5.318108 2.251978)
-      (xy -5.388729 2.272787)
-      (xy -5.445882 2.311793)
-      (xy -5.484092 2.36392)
-      (xy -5.497792 2.418581)
-      (xy -5.498317 2.481996)
-      (xy -5.495385 2.538108)
-      (xy -5.489654 2.579446)
-      (xy -5.481955 2.598423)
-      (xy -5.468069 2.617448)
-      (xy -5.462428 2.6301)
-      (xy -5.437915 2.658971)
-      (xy -5.392233 2.682795)
-      (xy -5.333772 2.698145)
-      (xy -5.286222 2.702036)
-      (xy -5.214487 2.702036)
-      (xy -5.214487 2.480882)
-      (xy -5.215409 2.398916)
-      (xy -5.217976 2.330589)
-      (xy -5.221893 2.280663)
-      (xy -5.226863 2.253898)
-      (xy -5.228805 2.250879)
-      (xy -5.250748 2.247613)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp cf8ff2a3-47b7-4b2a-b6f5-d49e6c16d2b1))
-  (fp_poly
-    (pts
-      (xy 4.584022 9.874295)
-      (xy 4.525213 9.900549)
-      (xy 4.484905 9.939469)
-      (xy 4.476789 9.962713)
-      (xy 4.470859 10.003794)
-      (xy 4.46731 10.054552)
-      (xy 4.466337 10.106826)
-      (xy 4.468134 10.152452)
-      (xy 4.472897 10.18327)
-      (xy 4.478884 10.19178)
-      (xy 4.490663 10.20453)
-      (xy 4.500332 10.234262)
-      (xy 4.515041 10.26717)
-      (xy 4.546322 10.286435)
-      (xy 4.599243 10.294532)
-      (xy 4.625052 10.295191)
-      (xy 4.657799 10.299312)
-      (xy 4.673022 10.309077)
-      (xy 4.673158 10.310195)
-      (xy 4.685826 10.321322)
-      (xy 4.710163 10.324997)
-      (xy 4.747168 10.324997)
-      (xy 4.747168 9.866139)
-      (xy 4.66165 9.866139)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e9d9dc75-e2ed-4b55-8ae2-3b22340cda38))
-  (fp_poly
-    (pts
-      (xy 3.262357 -6.118322)
-      (xy 3.216823 -6.114025)
-      (xy 3.194448 -6.107522)
-      (xy 3.192972 -6.105073)
-      (xy 3.180733 -6.092582)
-      (xy 3.166658 -6.090271)
-      (xy 3.134851 -6.077711)
-      (xy 3.100097 -6.038862)
-      (xy 3.078257 -6.004247)
-      (xy 3.068439 -5.974582)
-      (xy 3.062329 -5.931794)
-      (xy 3.060099 -5.884942)
-      (xy 3.061922 -5.843086)
-      (xy 3.067969 -5.815287)
-      (xy 3.074557 -5.809036)
-      (xy 3.087717 -5.797059)
-      (xy 3.089359 -5.787002)
-      (xy 3.098429 -5.759591)
-      (xy 3.114851 -5.735196)
-      (xy 3.12937 -5.721839)
-      (xy 3.149535 -5.71316)
-      (xy 3.181417 -5.708182)
-      (xy 3.231085 -5.705929)
-      (xy 3.299875 -5.705423)
-      (xy 3.459405 -5.705423)
-      (xy 3.459405 -6.119875)
-      (xy 3.326189 -6.119875)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0897f653-a20e-4c77-b80d-57b32631b473))
-  (fp_poly
-    (pts
-      (xy 6.286562 4.049006)
-      (xy 6.43458 4.049006)
-      (xy 6.43458 3.856582)
-      (xy 6.434831 3.778026)
-      (xy 6.436069 3.724354)
-      (xy 6.439018 3.69085)
-      (xy 6.444404 3.672795)
-      (xy 6.452954 3.665472)
-      (xy 6.464184 3.664158)
-      (xy 6.488237 3.670356)
-      (xy 6.493788 3.67896)
-      (xy 6.501184 3.694762)
-      (xy 6.519112 3.69003)
-      (xy 6.541178 3.668517)
-      (xy 6.557655 3.641453)
-      (xy 6.575655 3.602227)
-      (xy 6.580528 3.58273)
-      (xy 6.572097 3.576067)
-      (xy 6.555956 3.575346)
-      (xy 6.52545 3.568671)
-      (xy 6.51525 3.562373)
-      (xy 6.482649 3.539152)
-      (xy 6.436074 3.513591)
-      (xy 6.386053 3.490654)
-      (xy 6.343113 3.475305)
-      (xy 6.323041 3.471733)
-      (xy 6.286562 3.471733)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 16258d9d-c5c1-41da-a9b7-5ee97beead97))
-  (fp_poly
-    (pts
-      (xy -5.244091 7.927095)
-      (xy -5.081271 7.927095)
-      (xy -5.080102 7.664362)
-      (xy -5.079337 7.581465)
-      (xy -5.077923 7.511369)
-      (xy -5.076011 7.458347)
-      (xy -5.073754 7.42667)
-      (xy -5.071468 7.420131)
-      (xy -5.051929 7.437119)
-      (xy -5.043032 7.438633)
-      (xy -5.024139 7.447032)
-      (xy -5.022063 7.453435)
-      (xy -5.009389 7.464536)
-      (xy -4.984819 7.468237)
-      (xy -4.953733 7.459601)
-      (xy -4.929443 7.429452)
-      (xy -4.923512 7.417776)
-      (xy -4.907483 7.368848)
-      (xy -4.915225 7.336027)
-      (xy -4.947665 7.31659)
-      (xy -4.958936 7.313678)
-      (xy -4.995082 7.298423)
-      (xy -5.038819 7.270234)
-      (xy -5.059848 7.253359)
-      (xy -5.103977 7.220158)
-      (xy -5.144251 7.20504)
-      (xy -5.181183 7.202087)
-      (xy -5.244091 7.201803)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e441efbe-a76b-4b3c-bad6-007b16e83b1b))
-  (fp_poly
-    (pts
-      (xy -5.821364 4.049006)
-      (xy -5.688147 4.049006)
-      (xy -5.688147 3.850567)
-      (xy -5.687944 3.770758)
-      (xy -5.686873 3.716087)
-      (xy -5.684241 3.68209)
-      (xy -5.679355 3.6643)
-      (xy -5.671522 3.658253)
-      (xy -5.660047 3.659483)
-      (xy -5.658543 3.659869)
-      (xy -5.634548 3.671585)
-      (xy -5.62894 3.680686)
-      (xy -5.61949 3.693688)
-      (xy -5.597473 3.689819)
-      (xy -5.57239 3.671941)
-      (xy -5.56317 3.660864)
-      (xy -5.544421 3.62326)
-      (xy -5.541958 3.592412)
-      (xy -5.555858 3.576195)
-      (xy -5.562331 3.575346)
-      (xy -5.582139 3.569319)
-      (xy -5.584674 3.564245)
-      (xy -5.597099 3.552394)
-      (xy -5.628606 3.534557)
-      (xy -5.651283 3.523923)
-      (xy -5.689748 3.50488)
-      (xy -5.713747 3.488895)
-      (xy -5.717751 3.483218)
-      (xy -5.730772 3.475625)
-      (xy -5.762789 3.471832)
-      (xy -5.769557 3.471733)
-      (xy -5.821364 3.471733)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6a5fa4d4-03a9-46d9-8f65-29ed6100a944))
-  (fp_poly
-    (pts
-      (xy -1.676842 5.011127)
-      (xy -1.499219 5.011127)
-      (xy -1.499219 4.766897)
-      (xy -1.498345 4.670623)
-      (xy -1.495814 4.596566)
-      (xy -1.49176 4.546952)
-      (xy -1.486319 4.524013)
-      (xy -1.484417 4.522666)
-      (xy -1.470046 4.53393)
-      (xy -1.469616 4.537468)
-      (xy -1.457359 4.54991)
-      (xy -1.442972 4.55227)
-      (xy -1.410473 4.561334)
-      (xy -1.399087 4.569512)
-      (xy -1.385759 4.573341)
-      (xy -1.370499 4.555598)
-      (xy -1.351721 4.516478)
-      (xy -1.334678 4.475912)
-      (xy -1.323758 4.448369)
-      (xy -1.321597 4.441633)
-      (xy -1.334028 4.435104)
-      (xy -1.358602 4.427776)
-      (xy -1.386324 4.41589)
-      (xy -1.395606 4.403969)
-      (xy -1.407588 4.391058)
-      (xy -1.41764 4.389449)
-      (xy -1.449014 4.378207)
-      (xy -1.490173 4.347923)
-      (xy -1.526826 4.311739)
-      (xy -1.564383 4.291288)
-      (xy -1.613523 4.285836)
-      (xy -1.676842 4.285836)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 84e91437-9e62-4b51-a15a-b7c14f490f40))
-  (fp_poly
-    (pts
-      (xy -5.214487 10.384204)
-      (xy -5.051667 10.384204)
-      (xy -5.051667 10.139974)
-      (xy -5.050793 10.0437)
-      (xy -5.048262 9.969642)
-      (xy -5.044208 9.920029)
-      (xy -5.038767 9.89709)
-      (xy -5.036865 9.895743)
-      (xy -5.022493 9.907007)
-      (xy -5.022063 9.910545)
-      (xy -5.01006 9.923644)
-      (xy -4.999659 9.925346)
-      (xy -4.969491 9.932862)
-      (xy -4.948222 9.943478)
-      (xy -4.925502 9.953197)
-      (xy -4.907496 9.946513)
-      (xy -4.889839 9.91937)
-      (xy -4.868989 9.869839)
-      (xy -4.855002 9.83137)
-      (xy -4.852504 9.812878)
-      (xy -4.861668 9.806985)
-      (xy -4.870464 9.806461)
-      (xy -4.902413 9.797454)
-      (xy -4.92498 9.784258)
-      (xy -4.954966 9.767161)
-      (xy -4.972916 9.762526)
-      (xy -5.002571 9.750848)
-      (xy -5.047299 9.716913)
-      (xy -5.074464 9.692217)
-      (xy -5.101035 9.680364)
-      (xy -5.142651 9.674039)
-      (xy -5.154223 9.673715)
-      (xy -5.214487 9.673715)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d0b09c90-6532-4806-bf92-bb71aca41949))
-  (fp_poly
-    (pts
-      (xy -3.529917 7.065346)
-      (xy -3.55276 7.096571)
-      (xy -3.584719 7.14227)
-      (xy -3.622307 7.197254)
-      (xy -3.662039 7.256334)
-      (xy -3.700431 7.31432)
-      (xy -3.733997 7.366025)
-      (xy -3.759252 7.406258)
-      (xy -3.77271 7.429831)
-      (xy -3.773585 7.431834)
-      (xy -3.772907 7.439669)
-      (xy -3.761525 7.445393)
-      (xy -3.735769 7.449318)
-      (xy -3.691968 7.451758)
-      (xy -3.626453 7.453025)
-      (xy -3.535553 7.453429)
-      (xy -3.519674 7.453435)
-      (xy -3.424693 7.453132)
-      (xy -3.355642 7.452013)
-      (xy -3.308851 7.449767)
-      (xy -3.280648 7.446081)
-      (xy -3.267365 7.440644)
-      (xy -3.26533 7.433143)
-      (xy -3.265763 7.431834)
-      (xy -3.276831 7.411665)
-      (xy -3.300298 7.373939)
-      (xy -3.332677 7.323845)
-      (xy -3.370484 7.266572)
-      (xy -3.410234 7.20731)
-      (xy -3.448442 7.151248)
-      (xy -3.481621 7.103575)
-      (xy -3.506288 7.069479)
-      (xy -3.518956 7.054151)
-      (xy -3.519674 7.053785)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 85693583-f9b5-4be9-810c-bf8f71381fab))
-  (fp_poly
-    (pts
-      (xy -1.531665 7.065346)
-      (xy -1.554509 7.096571)
-      (xy -1.586467 7.14227)
-      (xy -1.624055 7.197254)
-      (xy -1.663787 7.256334)
-      (xy -1.702179 7.31432)
-      (xy -1.735745 7.366025)
-      (xy -1.761 7.406258)
-      (xy -1.774459 7.429831)
-      (xy -1.775333 7.431834)
-      (xy -1.774655 7.439669)
-      (xy -1.763273 7.445393)
-      (xy -1.737517 7.449318)
-      (xy -1.693716 7.451758)
-      (xy -1.628201 7.453025)
-      (xy -1.537301 7.453429)
-      (xy -1.521422 7.453435)
-      (xy -1.426442 7.453132)
-      (xy -1.357391 7.452013)
-      (xy -1.310599 7.449767)
-      (xy -1.282396 7.446081)
-      (xy -1.269113 7.440644)
-      (xy -1.267078 7.433143)
-      (xy -1.267511 7.431834)
-      (xy -1.278579 7.411665)
-      (xy -1.302046 7.373939)
-      (xy -1.334425 7.323845)
-      (xy -1.372233 7.266572)
-      (xy -1.411982 7.20731)
-      (xy -1.45019 7.151248)
-      (xy -1.483369 7.103575)
-      (xy -1.508036 7.069479)
-      (xy -1.520705 7.054151)
-      (xy -1.521422 7.053785)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5a3270e2-2b2e-440b-b175-4d488ede477b))
-  (fp_poly
-    (pts
-      (xy -6.081238 11.160191)
-      (xy -6.10823 11.1743)
-      (xy -6.117174 11.204134)
-      (xy -6.117401 11.213391)
-      (xy -6.121137 11.244718)
-      (xy -6.138645 11.256207)
-      (xy -6.161525 11.257514)
-      (xy -6.195559 11.263273)
-      (xy -6.212301 11.285868)
-      (xy -6.215514 11.296822)
-      (xy -6.212709 11.336649)
-      (xy -6.186739 11.365312)
-      (xy -6.145159 11.375929)
-      (xy -6.122693 11.389088)
-      (xy -6.114684 11.416634)
-      (xy -6.103677 11.44876)
-      (xy -6.075575 11.461313)
-      (xy -6.072442 11.461719)
-      (xy -6.040109 11.461325)
-      (xy -6.024335 11.455552)
-      (xy -6.015711 11.433518)
-      (xy -6.013788 11.413528)
-      (xy -6.003728 11.386961)
-      (xy -5.970021 11.369214)
-      (xy -5.965682 11.367889)
-      (xy -5.931977 11.35343)
-      (xy -5.919028 11.33062)
-      (xy -5.917576 11.309321)
-      (xy -5.921325 11.278186)
-      (xy -5.938689 11.264572)
-      (xy -5.965682 11.260277)
-      (xy -5.99909 11.253513)
-      (xy -6.012033 11.236267)
-      (xy -6.013788 11.213044)
-      (xy -6.02102 11.17286)
-      (xy -6.044758 11.156651)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 56413d6e-7347-4974-9c35-46329de9b7f6))
-  (fp_poly
-    (pts
-      (xy -7.072807 6.232355)
-      (xy -7.196245 6.232654)
-      (xy -7.29553 6.23329)
-      (xy -7.373386 6.234378)
-      (xy -7.432539 6.23603)
-      (xy -7.475713 6.238361)
-      (xy -7.505633 6.241484)
-      (xy -7.525024 6.245512)
-      (xy -7.536612 6.25056)
-      (xy -7.54312 6.25674)
-      (xy -7.544092 6.258184)
-      (xy -7.552523 6.289988)
-      (xy -7.544096 6.309991)
-      (xy -7.538204 6.316453)
-      (xy -7.527626 6.321787)
-      (xy -7.509632 6.326125)
-      (xy -7.481493 6.329598)
-      (xy -7.44048 6.332337)
-      (xy -7.383862 6.334473)
-      (xy -7.308912 6.336139)
-      (xy -7.212898 6.337465)
-      (xy -7.093092 6.338584)
-      (xy -6.946764 6.339625)
-      (xy -6.925793 6.339761)
-      (xy -6.77389 6.340611)
-      (xy -6.649022 6.340974)
-      (xy -6.548623 6.340778)
-      (xy -6.470128 6.33995)
-      (xy -6.41097 6.338415)
-      (xy -6.368584 6.336102)
-      (xy -6.340403 6.332936)
-      (xy -6.323863 6.328844)
-      (xy -6.316397 6.323753)
-      (xy -6.315655 6.322335)
-      (xy -6.311064 6.291016)
-      (xy -6.312355 6.266662)
-      (xy -6.317226 6.232281)
-      (xy -6.922489 6.232281)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 7b5adda8-cb21-4c06-97c4-ce6866d5839b))
-  (fp_poly
-    (pts
-      (xy 5.329935 -5.903394)
-      (xy 5.32444 -5.890446)
-      (xy 5.316448 -5.870748)
-      (xy 5.309639 -5.868243)
-      (xy 5.298512 -5.855576)
-      (xy 5.294837 -5.831239)
-      (xy 5.28977 -5.803421)
-      (xy 5.280035 -5.794234)
-      (xy 5.268629 -5.781646)
-      (xy 5.265233 -5.759696)
-      (xy 5.261231 -5.728409)
-      (xy 5.254937 -5.714862)
-      (xy 5.248415 -5.705993)
-      (xy 5.242975 -5.690041)
-      (xy 5.23705 -5.660236)
-      (xy 5.229072 -5.609808)
-      (xy 5.226203 -5.590708)
-      (xy 5.216804 -5.5278)
-      (xy 5.352032 -5.5278)
-      (xy 5.415891 -5.528281)
-      (xy 5.455746 -5.530541)
-      (xy 5.477191 -5.535803)
-      (xy 5.485822 -5.545293)
-      (xy 5.487261 -5.557404)
-      (xy 5.481062 -5.581457)
-      (xy 5.472459 -5.587008)
-      (xy 5.461332 -5.599675)
-      (xy 5.457657 -5.624013)
-      (xy 5.453241 -5.651839)
-      (xy 5.444767 -5.661017)
-      (xy 5.43646 -5.674429)
-      (xy 5.427845 -5.709298)
-      (xy 5.421829 -5.749828)
-      (xy 5.414411 -5.796617)
-      (xy 5.405247 -5.828794)
-      (xy 5.397715 -5.83864)
-      (xy 5.387139 -5.851311)
-      (xy 5.383648 -5.875644)
-      (xy 5.37671 -5.904662)
-      (xy 5.354044 -5.912649)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f11d393a-b6c6-42ac-bb81-b1f9400808de))
-  (fp_poly
-    (pts
-      (xy -4.12027 6.588712)
-      (xy -4.156154 6.626903)
-      (xy -4.160168 7.606218)
-      (xy -4.16088 7.81823)
-      (xy -4.161144 8.00207)
-      (xy -4.160944 8.159163)
-      (xy -4.16026 8.29094)
-      (xy -4.159073 8.398825)
-      (xy -4.157366 8.484249)
-      (xy -4.155121 8.548637)
-      (xy -4.152317 8.593418)
-      (xy -4.148938 8.620019)
-      (xy -4.146982 8.627058)
-      (xy -4.113985 8.672866)
-      (xy -4.065488 8.700982)
-      (xy -4.010703 8.708056)
-      (xy -3.96373 8.693716)
-      (xy -3.950422 8.686022)
-      (xy -3.939044 8.677881)
-      (xy -3.929444 8.667055)
-      (xy -3.92147 8.651308)
-      (xy -3.914969 8.628405)
-      (xy -3.909789 8.596109)
-      (xy -3.905777 8.552183)
-      (xy -3.902781 8.494392)
-      (xy -3.900648 8.4205)
-      (xy -3.899225 8.328269)
-      (xy -3.898362 8.215464)
-      (xy -3.897904 8.079849)
-      (xy -3.897699 7.919187)
-      (xy -3.897596 7.731243)
-      (xy -3.897592 7.723569)
-      (xy -3.897121 6.816955)
-      (xy -3.095543 6.816955)
-      (xy -3.052276 6.773688)
-      (xy -3.016759 6.720866)
-      (xy -3.009092 6.664542)
-      (xy -3.029468 6.60979)
-      (xy -3.045307 6.589687)
-      (xy -3.081605 6.550521)
-      (xy -4.084385 6.550521)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e7512348-6772-4561-8567-713be7b0f5a4))
-  (fp_poly
-    (pts
-      (xy 1.502746 10.726856)
-      (xy 1.478755 10.732442)
-      (xy 1.475619 10.735749)
-      (xy 1.466072 10.751098)
-      (xy 1.441017 10.782003)
-      (xy 1.405321 10.822547)
-      (xy 1.394412 10.834463)
-      (xy 1.355107 10.879176)
-      (xy 1.323884 10.91865)
-      (xy 1.306381 10.945655)
-      (xy 1.30494 10.949178)
-      (xy 1.292096 10.971728)
-      (xy 1.283619 10.976279)
-      (xy 1.269662 10.988458)
-      (xy 1.264131 11.002182)
-      (xy 1.261218 10.999467)
-      (xy 1.258593 10.972002)
-      (xy 1.256583 10.924642)
-      (xy 1.255645 10.876366)
-      (xy 1.253928 10.724647)
-      (xy 1.120711 10.724647)
-      (xy 1.120711 11.28882)
-      (xy 1.183491 11.284269)
-      (xy 1.226718 11.277476)
-      (xy 1.247443 11.263192)
-      (xy 1.251491 11.252223)
-      (xy 1.264705 11.224323)
-      (xy 1.291035 11.189219)
-      (xy 1.299275 11.18019)
-      (xy 1.329108 11.143947)
-      (xy 1.349423 11.110245)
-      (xy 1.351807 11.104071)
-      (xy 1.371282 11.067435)
-      (xy 1.38609 11.050288)
-      (xy 1.41195 11.02313)
-      (xy 1.441519 10.987536)
-      (xy 1.44318 10.985384)
-      (xy 1.475956 10.942683)
-      (xy 1.475956 11.287118)
-      (xy 1.609172 11.287118)
-      (xy 1.609172 10.724647)
-      (xy 1.542564 10.724647)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 6707ccb7-e250-4bd5-87b9-34efc0cb25ce))
-  (fp_poly
-    (pts
-      (xy -1.707932 6.55062)
-      (xy -1.811553 6.551928)
-      (xy -1.906138 6.554052)
-      (xy -1.987392 6.556991)
-      (xy -2.051025 6.560745)
-      (xy -2.092744 6.565314)
-      (xy -2.107378 6.569494)
-      (xy -2.118633 6.578639)
-      (xy -2.128326 6.588963)
-      (xy -2.136575 6.602615)
-      (xy -2.143496 6.62174)
-      (xy -2.149205 6.648486)
-      (xy -2.15382 6.684999)
-      (xy -2.157456 6.733427)
-      (xy -2.16023 6.795915)
-      (xy -2.162259 6.874611)
-      (xy -2.163659 6.971661)
-      (xy -2.164547 7.089213)
-      (xy -2.165039 7.229413)
-      (xy -2.165252 7.394408)
-      (xy -2.165302 7.586344)
-      (xy -2.165303 7.63666)
-      (xy -2.165303 8.621132)
-      (xy -2.131999 8.659461)
-      (xy -2.089569 8.691272)
-      (xy -2.046069 8.706161)
-      (xy -2.00472 8.707568)
-      (xy -1.96977 8.692822)
-      (xy -1.946157 8.674742)
-      (xy -1.89887 8.634953)
-      (xy -1.89887 6.816955)
-      (xy -1.097292 6.816955)
-      (xy -1.054025 6.773688)
-      (xy -1.020186 6.721604)
-      (xy -1.012978 6.664634)
-      (xy -1.031903 6.609734)
-      (xy -1.068682 6.569494)
-      (xy -1.090083 6.564282)
-      (xy -1.136784 6.559885)
-      (xy -1.204493 6.556303)
-      (xy -1.288917 6.553536)
-      (xy -1.385766 6.551584)
-      (xy -1.490746 6.550448)
-      (xy -1.599565 6.550126)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f4c74ac9-5647-48f5-938b-19d7b3536e6e))
-  (fp_poly
-    (pts
-      (xy -6.886443 8.335347)
-      (xy -6.96551 8.337624)
-      (xy -7.026382 8.34185)
-      (xy -7.074754 8.34848)
-      (xy -7.11632 8.357969)
-      (xy -7.131329 8.362361)
-      (xy -7.288177 8.424404)
-      (xy -7.427709 8.50902)
-      (xy -7.444295 8.521409)
-      (xy -7.496698 8.56628)
-      (xy -7.52416 8.603316)
-      (xy -7.528901 8.636462)
-      (xy -7.520907 8.657685)
-      (xy -7.494787 8.678802)
-      (xy -7.455908 8.675322)
-      (xy -7.407056 8.647841)
-      (xy -7.38296 8.628158)
-      (xy -7.283695 8.555435)
-      (xy -7.169814 8.501773)
-      (xy -7.038446 8.466293)
-      (xy -6.88672 8.448121)
-      (xy -6.783485 8.44516)
-      (xy -6.648889 8.449331)
-      (xy -6.535519 8.46335)
-      (xy -6.435987 8.489472)
-      (xy -6.342903 8.529956)
-      (xy -6.248879 8.587059)
-      (xy -6.196693 8.62442)
-      (xy -6.145173 8.655229)
-      (xy -6.106237 8.662789)
-      (xy -6.082198 8.647502)
-      (xy -6.07537 8.609771)
-      (xy -6.075852 8.603394)
-      (xy -6.081385 8.578965)
-      (xy -6.095914 8.55629)
-      (xy -6.124245 8.53046)
-      (xy -6.171182 8.496565)
-      (xy -6.19823 8.478322)
-      (xy -6.274483 8.430332)
-      (xy -6.344452 8.394039)
-      (xy -6.414338 8.367917)
-      (xy -6.490343 8.350445)
-      (xy -6.578667 8.3401)
-      (xy -6.685512 8.335357)
-      (xy -6.783485 8.334563)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f2068426-0fcc-40f1-8fda-1ac9b5798677))
-  (fp_poly
-    (pts
-      (xy -6.037339 3.818672)
-      (xy -6.058408 3.829393)
-      (xy -6.091162 3.851993)
-      (xy -6.141236 3.889411)
-      (xy -6.147005 3.893773)
-      (xy -6.284682 3.984718)
-      (xy -6.431047 4.057614)
-      (xy -6.531853 4.094534)
-      (xy -6.610814 4.112551)
-      (xy -6.707204 4.124853)
-      (xy -6.812938 4.131339)
-      (xy -6.919925 4.131904)
-      (xy -7.020079 4.126446)
-      (xy -7.105311 4.114862)
-      (xy -7.153532 4.102453)
-      (xy -7.270234 4.055573)
-      (xy -7.378676 3.999168)
-      (xy -7.469082 3.938434)
-      (xy -7.482513 3.927587)
-      (xy -7.538801 3.88775)
-      (xy -7.581461 3.87324)
-      (xy -7.609961 3.88407)
-      (xy -7.62377 3.92025)
-      (xy -7.624253 3.924537)
-      (xy -7.623769 3.951788)
-      (xy -7.612712 3.974916)
-      (xy -7.585959 4.001144)
-      (xy -7.550244 4.028891)
-      (xy -7.424959 4.113146)
-      (xy -7.302296 4.174742)
-      (xy -7.174474 4.216356)
-      (xy -7.033711 4.240664)
-      (xy -6.909301 4.249353)
-      (xy -6.785347 4.250058)
-      (xy -6.679434 4.243225)
-      (xy -6.62561 4.235323)
-      (xy -6.451606 4.190077)
-      (xy -6.288033 4.123834)
-      (xy -6.140695 4.039277)
-      (xy -6.047092 3.967846)
-      (xy -6.006949 3.92434)
-      (xy -5.985305 3.882015)
-      (xy -5.983642 3.846392)
-      (xy -6.00344 3.822991)
-      (xy -6.007723 3.821113)
-      (xy -6.022321 3.816892)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 67323bd5-f5ad-4882-9b0e-72506f9b2bff))
-  (fp_poly
-    (pts
-      (xy -6.913038 -9.176342)
-      (xy -6.954245 -9.1599)
-      (xy -6.961107 -9.154257)
-      (xy -6.983063 -9.124953)
-      (xy -6.990711 -9.102451)
-      (xy -6.998704 -9.082753)
-      (xy -7.005513 -9.080248)
-      (xy -7.018228 -9.068241)
-      (xy -7.019022 -9.037466)
-      (xy -7.008893 -8.995793)
-      (xy -6.989274 -8.951874)
-      (xy -6.963411 -8.914796)
-      (xy -6.923396 -8.867268)
-      (xy -6.877139 -8.818579)
-      (xy -6.869174 -8.810806)
-      (xy -6.780114 -8.725003)
-      (xy -7.020315 -8.725003)
-      (xy -7.020315 -8.62139)
-      (xy -6.650268 -8.62139)
-      (xy -6.650268 -8.687999)
-      (xy -6.653208 -8.727722)
-      (xy -6.660647 -8.751551)
-      (xy -6.66507 -8.754607)
-      (xy -6.677957 -8.766697)
-      (xy -6.679872 -8.778331)
-      (xy -6.689898 -8.798677)
-      (xy -6.716746 -8.83324)
-      (xy -6.755572 -8.876061)
-      (xy -6.776983 -8.897743)
-      (xy -6.832601 -8.956673)
-      (xy -6.86389 -9.000829)
-      (xy -6.871124 -9.0319)
-      (xy -6.854578 -9.051573)
-      (xy -6.814527 -9.061538)
-      (xy -6.803807 -9.062508)
-      (xy -6.748649 -9.059175)
-      (xy -6.72015 -9.044402)
-      (xy -6.704214 -9.032978)
-      (xy -6.688594 -9.03817)
-      (xy -6.665901 -9.063501)
-      (xy -6.657628 -9.074216)
-      (xy -6.634754 -9.106116)
-      (xy -6.623112 -9.126209)
-      (xy -6.62287 -9.129326)
-      (xy -6.638096 -9.137325)
-      (xy -6.66917 -9.15365)
-      (xy -6.677371 -9.157958)
-      (xy -6.728003 -9.175423)
-      (xy -6.790462 -9.184227)
-      (xy -6.855292 -9.184492)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp cd437c9a-f3e0-4725-b1a4-372d2b4317b9))
-  (fp_poly
-    (pts
-      (xy 3.564701 6.550992)
-      (xy 3.416091 6.551428)
-      (xy 3.294986 6.552485)
-      (xy 3.199291 6.554234)
-      (xy 3.126911 6.556749)
-      (xy 3.075753 6.560101)
-      (xy 3.043722 6.564363)
-      (xy 3.028869 6.569494)
-      (xy 2.991812 6.614455)
-      (xy 2.976185 6.670042)
-      (xy 2.982502 6.726955)
-      (xy 3.011275 6.775893)
-      (xy 3.017168 6.781619)
-      (xy 3.028112 6.789826)
-      (xy 3.043046 6.796328)
-      (xy 3.065405 6.801368)
-      (xy 3.098625 6.805194)
-      (xy 3.146143 6.808051)
-      (xy 3.211396 6.810185)
-      (xy 3.297819 6.811841)
-      (xy 3.408848 6.813267)
-      (xy 3.468336 6.813904)
-      (xy 3.88866 6.818255)
-      (xy 3.88866 7.721492)
-      (xy 3.888915 7.934492)
-      (xy 3.889678 8.120783)
-      (xy 3.890941 8.279942)
-      (xy 3.892697 8.411547)
-      (xy 3.89494 8.515174)
-      (xy 3.897662 8.590402)
-      (xy 3.900856 8.636807)
-      (xy 3.9039 8.653206)
-      (xy 3.929432 8.681085)
-      (xy 3.969136 8.707358)
-      (xy 4.009324 8.723809)
-      (xy 4.024842 8.725803)
-      (xy 4.050942 8.718702)
-      (xy 4.084412 8.703322)
-      (xy 4.118721 8.678286)
-      (xy 4.139919 8.653081)
-      (xy 4.143323 8.631599)
-      (xy 4.146307 8.58091)
-      (xy 4.148866 8.50141)
-      (xy 4.150994 8.393495)
-      (xy 4.152685 8.257558)
-      (xy 4.153934 8.093995)
-      (xy 4.154733 7.903202)
-      (xy 4.155079 7.685572)
-      (xy 4.155093 7.626648)
-      (xy 4.155093 6.628567)
-      (xy 4.077047 6.550521)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b7ae08bd-b797-465f-ac53-e0ee179f27ab))
-  (fp_poly
-    (pts
-      (xy 5.886911 0.037701)
-      (xy 5.849907 0.037701)
-      (xy 5.827072 0.040462)
-      (xy 5.816253 0.054032)
-      (xy 5.813043 0.086343)
-      (xy 5.812902 0.104309)
-      (xy 5.814436 0.145412)
-      (xy 5.821975 0.164886)
-      (xy 5.839926 0.170663)
-      (xy 5.849907 0.170918)
-      (xy 5.871869 0.173317)
-      (xy 5.882825 0.185563)
-      (xy 5.886561 0.215225)
-      (xy 5.886911 0.244927)
-      (xy 5.886911 0.318936)
-      (xy 6.049732 0.318936)
-      (xy 6.049732 0.170918)
-      (xy 6.345769 0.170918)
-      (xy 6.345769 0.112595)
-      (xy 6.337416 0.063122)
-      (xy 6.323909 0.024725)
-      (xy 6.178533 0.024725)
-      (xy 6.169294 0.034483)
-      (xy 6.140234 0.03751)
-      (xy 6.117338 0.037701)
-      (xy 6.049732 0.037701)
-      (xy 6.049732 -0.155754)
-      (xy 6.097813 -0.099732)
-      (xy 6.127401 -0.065861)
-      (xy 6.149092 -0.042126)
-      (xy 6.155025 -0.036309)
-      (xy 6.1662 -0.017692)
-      (xy 6.17455 0.004397)
-      (xy 6.178533 0.024725)
-      (xy 6.323909 0.024725)
-      (xy 6.315369 0.00045)
-      (xy 6.284152 -0.065282)
-      (xy 6.248284 -0.123935)
-      (xy 6.22958 -0.147945)
-      (xy 6.207092 -0.177193)
-      (xy 6.195989 -0.196913)
-      (xy 6.184262 -0.215695)
-      (xy 6.158364 -0.250089)
-      (xy 6.12346 -0.293292)
-      (xy 6.11634 -0.301812)
-      (xy 6.078236 -0.346131)
-      (xy 6.050798 -0.372406)
-      (xy 6.025853 -0.385428)
-      (xy 5.995226 -0.389986)
-      (xy 5.964621 -0.390722)
-      (xy 5.886911 -0.391553)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 70c0bbf1-7dbd-4d2b-970d-e9890c5a38fd))
-  (fp_poly
-    (pts
-      (xy 6.168147 1.103435)
-      (xy 6.167806 1.174692)
-      (xy 6.166164 1.221464)
-      (xy 6.162289 1.248871)
-      (xy 6.155252 1.262029)
-      (xy 6.144122 1.266055)
-      (xy 6.138543 1.266256)
-      (xy 6.119175 1.271221)
-      (xy 6.110615 1.291289)
-      (xy 6.108939 1.325463)
-      (xy 6.111422 1.364199)
-      (xy 6.121456 1.381318)
-      (xy 6.138543 1.38467)
-      (xy 6.157043 1.389029)
-      (xy 6.165791 1.407125)
-      (xy 6.168135 1.446494)
-      (xy 6.168147 1.451279)
-      (xy 6.168147 1.517887)
-      (xy 6.301364 1.517887)
-      (xy 6.301364 1.38467)
-      (xy 6.523391 1.38467)
-      (xy 6.523391 1.3314)
-      (xy 6.518379 1.290388)
-      (xy 6.511595 1.266256)
-      (xy 6.392191 1.266256)
-      (xy 6.346777 1.266256)
-      (xy 6.319406 1.264595)
-      (xy 6.306148 1.25439)
-      (xy 6.301993 1.22781)
-      (xy 6.301814 1.195947)
-      (xy 6.303019 1.155761)
-      (xy 6.306986 1.141409)
-      (xy 6.315284 1.149141)
-      (xy 6.318873 1.155242)
-      (xy 6.339436 1.188894)
-      (xy 6.363836 1.22555)
-      (xy 6.392191 1.266256)
-      (xy 6.511595 1.266256)
-      (xy 6.505746 1.245452)
-      (xy 6.489103 1.205967)
-      (xy 6.472059 1.181302)
-      (xy 6.464102 1.177444)
-      (xy 6.452509 1.164872)
-      (xy 6.44278 1.138351)
-      (xy 6.427852 1.108406)
-      (xy 6.397909 1.06672)
-      (xy 6.359284 1.022065)
-      (xy 6.357263 1.019937)
-      (xy 6.315071 0.977845)
-      (xy 6.283769 0.953782)
-      (xy 6.255379 0.94297)
-      (xy 6.224852 0.940615)
-      (xy 6.168147 0.940615)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp fe2cd7ae-6b9b-45c5-b819-7cd644fc8aa2))
-  (fp_poly
-    (pts
-      (xy 6.686212 3.641955)
-      (xy 6.685619 3.716704)
-      (xy 6.683439 3.766474)
-      (xy 6.67907 3.795875)
-      (xy 6.671912 3.809514)
-      (xy 6.664009 3.812176)
-      (xy 6.647588 3.82341)
-      (xy 6.641847 3.859265)
-      (xy 6.641806 3.863983)
-      (xy 6.646621 3.9023)
-      (xy 6.661987 3.915696)
-      (xy 6.664009 3.915789)
-      (xy 6.678643 3.924506)
-      (xy 6.685309 3.954146)
-      (xy 6.686212 3.982398)
-      (xy 6.686212 4.049006)
-      (xy 6.834231 4.049006)
-      (xy 6.834231 3.915789)
-      (xy 7.056259 3.915789)
-      (xy 7.056259 3.862519)
-      (xy 7.051246 3.821507)
-      (xy 7.046108 3.803231)
-      (xy 6.931983 3.803231)
-      (xy 6.925169 3.810518)
-      (xy 6.894249 3.812166)
-      (xy 6.888331 3.812176)
-      (xy 6.834231 3.812176)
-      (xy 6.834286 3.734467)
-      (xy 6.834341 3.656757)
-      (xy 6.865502 3.708563)
-      (xy 6.891586 3.748932)
-      (xy 6.915893 3.781961)
-      (xy 6.919548 3.786273)
-      (xy 6.931983 3.803231)
-      (xy 7.046108 3.803231)
-      (xy 7.038613 3.776571)
-      (xy 7.021971 3.737086)
-      (xy 7.004927 3.712421)
-      (xy 6.996969 3.708563)
-      (xy 6.985212 3.696039)
-      (xy 6.976171 3.671559)
-      (xy 6.964285 3.643836)
-      (xy 6.952364 3.634554)
-      (xy 6.938774 3.622915)
-      (xy 6.937844 3.616612)
-      (xy 6.928129 3.597121)
-      (xy 6.902946 3.564951)
-      (xy 6.875554 3.535202)
-      (xy 6.836547 3.498444)
-      (xy 6.805339 3.479303)
-      (xy 6.771155 3.472344)
-      (xy 6.749739 3.471733)
-      (xy 6.686212 3.471733)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 387be091-d8ef-42ac-97c5-0efd97e37ff9))
-  (fp_poly
-    (pts
-      (xy 6.168147 -1.427684)
-      (xy 6.167806 -1.356427)
-      (xy 6.166164 -1.309654)
-      (xy 6.162289 -1.282248)
-      (xy 6.155252 -1.26909)
-      (xy 6.144122 -1.265064)
-      (xy 6.138543 -1.264863)
-      (xy 6.119175 -1.259898)
-      (xy 6.110615 -1.23983)
-      (xy 6.108939 -1.205656)
-      (xy 6.111422 -1.16692)
-      (xy 6.121456 -1.149801)
-      (xy 6.138543 -1.146448)
-      (xy 6.157043 -1.14209)
-      (xy 6.165791 -1.123994)
-      (xy 6.168135 -1.084625)
-      (xy 6.168147 -1.07984)
-      (xy 6.168147 -1.013232)
-      (xy 6.301364 -1.013232)
-      (xy 6.301364 -1.146448)
-      (xy 6.527503 -1.146448)
-      (xy 6.519262 -1.237335)
-      (xy 6.513931 -1.278179)
-      (xy 6.386974 -1.278179)
-      (xy 6.36818 -1.266553)
-      (xy 6.345769 -1.264863)
-      (xy 6.320815 -1.266078)
-      (xy 6.307685 -1.274471)
-      (xy 6.302758 -1.297171)
-      (xy 6.302415 -1.341303)
-      (xy 6.302532 -1.349974)
-      (xy 6.304421 -1.391283)
-      (xy 6.308165 -1.413462)
-      (xy 6.312236 -1.412882)
-      (xy 6.326495 -1.38686)
-      (xy 6.350596 -1.351418)
-      (xy 6.355473 -1.344876)
-      (xy 6.382622 -1.303322)
-      (xy 6.386974 -1.278179)
-      (xy 6.513931 -1.278179)
-      (xy 6.512833 -1.286593)
-      (xy 6.504423 -1.323069)
-      (xy 6.497216 -1.337248)
-      (xy 6.481835 -1.354267)
-      (xy 6.45803 -1.387573)
-      (xy 6.44369 -1.409685)
-      (xy 6.408413 -1.45907)
-      (xy 6.36478 -1.511184)
-      (xy 6.345266 -1.5318)
-      (xy 6.305525 -1.567559)
-      (xy 6.272115 -1.585223)
-      (xy 6.233685 -1.590445)
-      (xy 6.227354 -1.590504)
-      (xy 6.168147 -1.590504)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 07c54cae-9b90-4929-b2ae-4855ec4f20cb))
-  (fp_poly
-    (pts
-      (xy -5.880571 8.704193)
-      (xy -5.881164 8.778942)
-      (xy -5.883345 8.828712)
-      (xy -5.887713 8.858113)
-      (xy -5.894871 8.871752)
-      (xy -5.902774 8.874414)
-      (xy -5.918212 8.884191)
-      (xy -5.924574 8.9166)
-      (xy -5.924977 8.933622)
-      (xy -5.921311 8.97479)
-      (xy -5.909157 8.991754)
-      (xy -5.902774 8.992829)
-      (xy -5.887336 9.002606)
-      (xy -5.880974 9.035015)
-      (xy -5.880571 9.052036)
-      (xy -5.880571 9.111244)
-      (xy -5.732553 9.111244)
-      (xy -5.732553 8.992829)
-      (xy -5.510525 8.992829)
-      (xy -5.510525 8.920053)
-      (xy -5.512583 8.877048)
-      (xy -5.513066 8.874414)
-      (xy -5.627266 8.874414)
-      (xy -5.732553 8.874414)
-      (xy -5.732553 8.805512)
-      (xy -5.7317 8.764697)
-      (xy -5.72724 8.748474)
-      (xy -5.716317 8.75184)
-      (xy -5.706649 8.760113)
-      (xy -5.680968 8.789438)
-      (xy -5.654733 8.827788)
-      (xy -5.654006 8.829015)
-      (xy -5.627266 8.874414)
-      (xy -5.513066 8.874414)
-      (xy -5.517831 8.848436)
-      (xy -5.521626 8.842343)
-      (xy -5.53445 8.82715)
-      (xy -5.553748 8.794651)
-      (xy -5.562295 8.778202)
-      (xy -5.584698 8.737166)
-      (xy -5.60516 8.705766)
-      (xy -5.610401 8.699435)
-      (xy -5.62658 8.671511)
-      (xy -5.62894 8.65873)
-      (xy -5.636906 8.639715)
-      (xy -5.643069 8.637584)
-      (xy -5.66326 8.627326)
-      (xy -5.691313 8.603067)
-      (xy -5.717455 8.574582)
-      (xy -5.731909 8.551648)
-      (xy -5.732553 8.5481)
-      (xy -5.745866 8.54004)
-      (xy -5.779906 8.534924)
-      (xy -5.806562 8.533971)
-      (xy -5.880571 8.533971)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp a24ecc51-2392-4615-8d3d-6d62619fb6b3))
-  (fp_poly
-    (pts
-      (xy -6.413438 -2.863465)
-      (xy -6.410776 -2.821247)
-      (xy -6.403968 -2.79445)
-      (xy -6.398636 -2.789455)
-      (xy -6.385242 -2.777584)
-      (xy -6.383835 -2.768836)
-      (xy -6.371895 -2.745986)
-      (xy -6.361632 -2.739697)
-      (xy -6.344735 -2.719983)
-      (xy -6.339429 -2.693708)
-      (xy -6.335663 -2.665584)
-      (xy -6.328328 -2.656069)
-      (xy -6.314896 -2.642763)
-      (xy -6.295423 -2.607141)
-      (xy -6.272491 -2.555203)
-      (xy -6.248681 -2.492953)
-      (xy -6.226578 -2.426393)
-      (xy -6.220128 -2.404607)
-      (xy -6.206209 -2.361758)
-      (xy -6.193175 -2.330831)
-      (xy -6.188837 -2.323937)
-      (xy -6.180344 -2.300388)
-      (xy -6.176616 -2.26276)
-      (xy -6.176609 -2.261029)
-      (xy -6.176609 -2.212183)
-      (xy -6.013788 -2.212183)
-      (xy -6.013788 -2.270517)
-      (xy -6.017229 -2.30993)
-      (xy -6.025775 -2.335193)
-      (xy -6.02859 -2.337999)
-      (xy -6.0386 -2.357681)
-      (xy -6.043334 -2.393551)
-      (xy -6.043392 -2.39808)
-      (xy -6.046687 -2.43198)
-      (xy -6.054774 -2.448655)
-      (xy -6.056302 -2.449013)
-      (xy -6.066639 -2.462045)
-      (xy -6.076237 -2.494414)
-      (xy -6.078174 -2.505058)
-      (xy -6.090423 -2.551564)
-      (xy -6.111533 -2.60701)
-      (xy -6.124409 -2.634575)
-      (xy -6.145301 -2.68021)
-      (xy -6.158854 -2.718362)
-      (xy -6.161745 -2.733948)
-      (xy -6.16878 -2.755916)
-      (xy -6.176609 -2.759852)
-      (xy -6.19098 -2.771116)
-      (xy -6.19141 -2.774654)
-      (xy -6.177385 -2.781635)
-      (xy -6.138339 -2.78665)
-      (xy -6.078819 -2.78922)
-      (xy -6.050793 -2.789455)
-      (xy -5.910175 -2.789455)
-      (xy -5.910175 -2.937474)
-      (xy -6.413438 -2.937474)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 744a1e83-a676-4e3a-9724-099f99bd2912))
-  (fp_poly
-    (pts
-      (xy -6.990711 -6.489922)
-      (xy -6.991052 -6.418665)
-      (xy -6.992694 -6.371892)
-      (xy -6.996568 -6.344486)
-      (xy -7.003605 -6.331328)
-      (xy -7.014735 -6.327302)
-      (xy -7.020315 -6.327101)
-      (xy -7.039683 -6.322136)
-      (xy -7.048242 -6.302068)
-      (xy -7.049919 -6.267894)
-      (xy -7.047436 -6.229158)
-      (xy -7.037402 -6.212038)
-      (xy -7.020315 -6.208686)
-      (xy -7.001815 -6.204328)
-      (xy -6.993067 -6.186231)
-      (xy -6.990722 -6.146863)
-      (xy -6.990711 -6.142078)
-      (xy -6.990711 -6.075469)
-      (xy -6.857494 -6.075469)
-      (xy -6.857494 -6.208686)
-      (xy -6.620664 -6.208686)
-      (xy -6.620433 -6.256792)
-      (xy -6.629409 -6.306196)
-      (xy -6.641535 -6.337255)
-      (xy -6.771672 -6.337255)
-      (xy -6.786349 -6.328322)
-      (xy -6.811362 -6.327101)
-      (xy -6.838155 -6.328386)
-      (xy -6.851638 -6.337211)
-      (xy -6.856073 -6.361033)
-      (xy -6.855777 -6.404811)
-      (xy -6.853778 -6.442902)
-      (xy -6.850394 -6.460636)
-      (xy -6.847425 -6.457313)
-      (xy -6.828944 -6.432155)
-      (xy -6.812137 -6.423011)
-      (xy -6.788674 -6.411312)
-      (xy -6.783283 -6.403813)
-      (xy -6.779651 -6.382873)
-      (xy -6.774156 -6.360405)
-      (xy -6.771672 -6.337255)
-      (xy -6.641535 -6.337255)
-      (xy -6.653688 -6.368385)
-      (xy -6.688716 -6.434185)
-      (xy -6.72994 -6.494421)
-      (xy -6.750181 -6.518223)
-      (xy -6.778663 -6.552478)
-      (xy -6.795918 -6.580061)
-      (xy -6.798287 -6.58822)
-      (xy -6.810572 -6.606793)
-      (xy -6.827891 -6.615737)
-      (xy -6.851812 -6.629026)
-      (xy -6.857494 -6.638938)
-      (xy -6.870726 -6.647171)
-      (xy -6.904203 -6.652109)
-      (xy -6.924103 -6.652742)
-      (xy -6.990711 -6.652742)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 232cdc1a-4220-464a-899b-e32f598f78c2))
-  (fp_poly
-    (pts
-      (xy 1.872939 10.727178)
-      (xy 1.80737 10.730138)
-      (xy 1.753278 10.734035)
-      (xy 1.717196 10.738309)
-      (xy 1.705784 10.741517)
-      (xy 1.704942 10.760415)
-      (xy 1.716623 10.792054)
-      (xy 1.735195 10.825791)
-      (xy 1.755027 10.850982)
-      (xy 1.767333 10.857864)
-      (xy 1.785203 10.848908)
-      (xy 1.786795 10.843062)
-      (xy 1.800178 10.834956)
-      (xy 1.834701 10.82958)
-      (xy 1.868205 10.82826)
-      (xy 1.912788 10.830694)
-      (xy 1.942358 10.83697)
-      (xy 1.949615 10.843062)
-      (xy 1.961927 10.855344)
-      (xy 1.977369 10.857864)
-      (xy 1.999872 10.869808)
-      (xy 2.014723 10.906651)
-      (xy 2.022344 10.969909)
-      (xy 2.023625 11.023208)
-      (xy 2.013171 11.091335)
-      (xy 1.982816 11.139078)
-      (xy 1.934066 11.164684)
-      (xy 1.898482 11.168703)
-      (xy 1.846002 11.168703)
-      (xy 1.846002 10.976279)
-      (xy 1.697984 10.976279)
-      (xy 1.697984 11.268616)
-      (xy 1.744239 11.277867)
-      (xy 1.818779 11.286736)
-      (xy 1.899576 11.286663)
-      (xy 1.976387 11.278429)
-      (xy 2.038973 11.262813)
-      (xy 2.059209 11.253889)
-      (xy 2.102508 11.222226)
-      (xy 2.130672 11.185752)
-      (xy 2.132763 11.180871)
-      (xy 2.147302 11.151357)
-      (xy 2.160086 11.139099)
-      (xy 2.165176 11.125401)
-      (xy 2.169122 11.088708)
-      (xy 2.171351 11.035624)
-      (xy 2.171643 11.005883)
-      (xy 2.170091 10.942051)
-      (xy 2.165793 10.896517)
-      (xy 2.15929 10.874141)
-      (xy 2.156841 10.872666)
-      (xy 2.144554 10.860355)
-      (xy 2.14204 10.844946)
-      (xy 2.131407 10.81955)
-      (xy 2.104399 10.78639)
-      (xy 2.086533 10.769567)
-      (xy 2.031026 10.721909)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 3a4af950-f54a-4966-836d-851f057e87f0))
-  (fp_poly
-    (pts
-      (xy 6.168147 6.173074)
-      (xy 6.167833 6.246211)
-      (xy 6.16631 6.294755)
-      (xy 6.162708 6.323714)
-      (xy 6.156155 6.338096)
-      (xy 6.145781 6.342911)
-      (xy 6.138543 6.343295)
-      (xy 6.118139 6.34909)
-      (xy 6.109907 6.371714)
-      (xy 6.108939 6.395102)
-      (xy 6.112251 6.430808)
-      (xy 6.125179 6.445215)
-      (xy 6.138543 6.446908)
-      (xy 6.157043 6.451266)
-      (xy 6.165791 6.469363)
-      (xy 6.168135 6.508732)
-      (xy 6.168147 6.513517)
-      (xy 6.168147 6.580125)
-      (xy 6.301364 6.580125)
-      (xy 6.301364 6.446908)
-      (xy 6.412377 6.446908)
-      (xy 6.468873 6.446396)
-      (xy 6.501993 6.443546)
-      (xy 6.517965 6.436387)
-      (xy 6.523014 6.422945)
-      (xy 6.523391 6.411754)
-      (xy 6.516042 6.343295)
-      (xy 6.389588 6.343295)
-      (xy 6.345476 6.343295)
-      (xy 6.319672 6.341744)
-      (xy 6.306608 6.332082)
-      (xy 6.30195 6.306794)
-      (xy 6.301364 6.266819)
-      (xy 6.302286 6.225169)
-      (xy 6.304657 6.200129)
-      (xy 6.306741 6.19651)
-      (xy 6.31633 6.211915)
-      (xy 6.33524 6.244936)
-      (xy 6.350853 6.272986)
-      (xy 6.389588 6.343295)
-      (xy 6.516042 6.343295)
-      (xy 6.515559 6.338795)
-      (xy 6.49391 6.27939)
-      (xy 6.477341 6.256128)
-      (xy 6.456653 6.229264)
-      (xy 6.449382 6.211965)
-      (xy 6.440069 6.194183)
-      (xy 6.41596 6.162738)
-      (xy 6.39057 6.133636)
-      (xy 6.358798 6.096705)
-      (xy 6.337236 6.067327)
-      (xy 6.331247 6.054659)
-      (xy 6.317701 6.036825)
-      (xy 6.284995 6.019391)
-      (xy 6.243311 6.006691)
-      (xy 6.209601 6.002852)
-      (xy 6.168147 6.002852)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 42cf9784-6b1b-4198-aa28-0b411664f52b))
-  (fp_poly
-    (pts
-      (xy 0.822187 10.726847)
-      (xy 0.736764 10.730527)
-      (xy 0.678686 10.735863)
-      (xy 0.645728 10.743138)
-      (xy 0.63593 10.750608)
-      (xy 0.620315 10.767782)
-      (xy 0.614236 10.769053)
-      (xy 0.588604 10.781938)
-      (xy 0.560845 10.814935)
-      (xy 0.536471 10.859552)
-      (xy 0.520995 10.907301)
-      (xy 0.519718 10.914626)
-      (xy 0.513996 10.990784)
-      (xy 0.518578 11.063795)
-      (xy 0.53197 11.127998)
-      (xy 0.552677 11.177734)
-      (xy 0.579204 11.207339)
-      (xy 0.598534 11.213109)
-      (xy 0.616034 11.221262)
-      (xy 0.617447 11.226224)
-      (xy 0.631398 11.246987)
-      (xy 0.66995 11.264691)
-      (xy 0.728153 11.278041)
-      (xy 0.801059 11.285745)
-      (xy 0.850347 11.287118)
-      (xy 0.910253 11.286079)
-      (xy 0.958413 11.283302)
-      (xy 0.98752 11.279292)
-      (xy 0.992428 11.27725)
-      (xy 0.995557 11.259979)
-      (xy 0.998276 11.217945)
-      (xy 1.000419 11.155987)
-      (xy 1.001815 11.078946)
-      (xy 1.002296 10.994456)
-      (xy 1.002296 10.82826)
-      (xy 0.869079 10.82826)
-      (xy 0.869079 11.172727)
-      (xy 0.800264 11.163295)
-      (xy 0.754677 11.154259)
-      (xy 0.720044 11.142481)
-      (xy 0.71176 11.137522)
-      (xy 0.687944 11.108157)
-      (xy 0.667761 11.066667)
-      (xy 0.65306 11.020675)
-      (xy 0.645693 10.977809)
-      (xy 0.647511 10.945692)
-      (xy 0.660362 10.931951)
-      (xy 0.661853 10.931873)
-      (xy 0.675903 10.920363)
-      (xy 0.676655 10.915093)
-      (xy 0.689636 10.887156)
-      (xy 0.722384 10.859458)
-      (xy 0.765607 10.837891)
-      (xy 0.810013 10.828346)
-      (xy 0.813572 10.828278)
-      (xy 0.869079 10.82826)
-      (xy 1.002296 10.82826)
-      (xy 1.002296 10.721529)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0681af30-e6e7-48bb-8dd8-f081f51e4b7d))
-  (fp_poly
-    (pts
-      (xy 6.681623 8.537959)
-      (xy 6.633714 8.549193)
-      (xy 6.607901 8.570335)
-      (xy 6.600689 8.603578)
-      (xy 6.603683 8.629423)
-      (xy 6.615977 8.667505)
-      (xy 6.635973 8.681583)
-      (xy 6.641604 8.68199)
-      (xy 6.66966 8.675038)
-      (xy 6.678811 8.667188)
-      (xy 6.697625 8.658909)
-      (xy 6.73612 8.653537)
-      (xy 6.767498 8.652386)
-      (xy 6.81543 8.654195)
-      (xy 6.841783 8.661376)
-      (xy 6.854453 8.676556)
-      (xy 6.856433 8.68199)
-      (xy 6.869722 8.705911)
-      (xy 6.879634 8.711594)
-      (xy 6.891886 8.723597)
-      (xy 6.893438 8.733796)
-      (xy 6.901431 8.753494)
-      (xy 6.90824 8.755999)
-      (xy 6.917067 8.769229)
-      (xy 6.922363 8.802702)
-      (xy 6.923042 8.822608)
-      (xy 6.920102 8.862331)
-      (xy 6.912664 8.88616)
-      (xy 6.90824 8.889216)
-      (xy 6.895279 8.901276)
-      (xy 6.893438 8.912476)
-      (xy 6.879664 8.948128)
-      (xy 6.841472 8.974971)
-      (xy 6.789419 8.98884)
-      (xy 6.730618 8.996727)
-      (xy 6.730618 8.800405)
-      (xy 6.597401 8.800405)
-      (xy 6.597401 8.941022)
-      (xy 6.598195 9.008054)
-      (xy 6.601102 9.050474)
-      (xy 6.606903 9.073245)
-      (xy 6.616383 9.081331)
-      (xy 6.619604 9.08164)
-      (xy 6.639301 9.089633)
-      (xy 6.641806 9.096442)
-      (xy 6.655194 9.10531)
-      (xy 6.690359 9.110084)
-      (xy 6.73981 9.111086)
-      (xy 6.796052 9.10864)
-      (xy 6.851591 9.10307)
-      (xy 6.898935 9.094699)
-      (xy 6.930344 9.083987)
-      (xy 6.989669 9.040897)
-      (xy 7.029273 8.986159)
-      (xy 7.050739 8.915695)
-      (xy 7.055647 8.825423)
-      (xy 7.05221 8.769619)
-      (xy 7.032313 8.682745)
-      (xy 6.990396 8.615527)
-      (xy 6.926837 8.568264)
-      (xy 6.842016 8.541257)
-      (xy 6.755122 8.534442)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 3582f6c8-df32-45fc-bc63-857199f53756))
-  (fp_poly
-    (pts
-      (xy -1.499219 10.82826)
-      (xy -1.410408 10.82826)
-      (xy -1.360805 10.82934)
-      (xy -1.334002 10.834085)
-      (xy -1.32323 10.844752)
-      (xy -1.321597 10.857864)
-      (xy -1.315398 10.881916)
-      (xy -1.306795 10.887468)
-      (xy -1.292423 10.898732)
-      (xy -1.291993 10.90227)
-      (xy -1.305125 10.911539)
-      (xy -1.337929 10.916694)
-      (xy -1.351201 10.917071)
-      (xy -1.388276 10.920354)
-      (xy -1.408898 10.928555)
-      (xy -1.410408 10.931873)
-      (xy -1.422525 10.944691)
-      (xy -1.434575 10.946675)
-      (xy -1.469949 10.960267)
-      (xy -1.497013 10.996937)
-      (xy -1.512104 11.050528)
-      (xy -1.514021 11.080307)
-      (xy -1.510286 11.161487)
-      (xy -1.498979 11.214559)
-      (xy -1.479948 11.240074)
-      (xy -1.468999 11.242712)
-      (xy -1.443477 11.251318)
-      (xy -1.436523 11.26058)
-      (xy -1.419844 11.269521)
-      (xy -1.381647 11.27658)
-      (xy -1.329987 11.281222)
-      (xy -1.272919 11.282914)
-      (xy -1.218498 11.281124)
-      (xy -1.18468 11.277245)
-      (xy -1.158321 11.269408)
-      (xy -1.146696 11.25167)
-      (xy -1.143981 11.214567)
-      (xy -1.143974 11.21106)
-      (xy -1.143974 11.151771)
-      (xy -1.225116 11.161909)
-      (xy -1.301159 11.166683)
-      (xy -1.352203 11.158453)
-      (xy -1.380046 11.136805)
-      (xy -1.384917 11.124972)
-      (xy -1.380791 11.089687)
-      (xy -1.35706 11.056981)
-      (xy -1.32265 11.037342)
-      (xy -1.308759 11.035486)
-      (xy -1.28366 11.029635)
-      (xy -1.277191 11.020684)
-      (xy -1.264179 11.010901)
-      (xy -1.232184 11.00601)
-      (xy -1.225385 11.005883)
-      (xy -1.173578 11.005883)
-      (xy -1.173578 10.90967)
-      (xy -1.17567 10.859394)
-      (xy -1.18121 10.824972)
-      (xy -1.18838 10.813458)
-      (xy -1.198773 10.800596)
-      (xy -1.203181 10.769605)
-      (xy -1.203182 10.769053)
-      (xy -1.203182 10.724647)
-      (xy -1.499219 10.724647)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ad3dcda3-e151-43f9-8e07-98602c2851d2))
-  (fp_poly
-    (pts
-      (xy -6.022546 6.003549)
-      (xy -6.060785 6.00656)
-      (xy -6.081965 6.013267)
-      (xy -6.092352 6.025053)
-      (xy -6.095198 6.032456)
-      (xy -6.108487 6.056378)
-      (xy -6.118399 6.06206)
-      (xy -6.125459 6.07553)
-      (xy -6.13021 6.110664)
-      (xy -6.131579 6.154571)
-      (xy -6.130272 6.204021)
-      (xy -6.12407 6.237756)
-      (xy -6.108316 6.26627)
-      (xy -6.078352 6.300061)
-      (xy -6.057698 6.321092)
-      (xy -6.021251 6.360062)
-      (xy -5.994975 6.39225)
-      (xy -5.984336 6.410937)
-      (xy -5.984313 6.411342)
-      (xy -5.972338 6.429478)
-      (xy -5.95088 6.443645)
-      (xy -5.93952 6.451561)
-      (xy -5.947375 6.456604)
-      (xy -5.977816 6.459421)
-      (xy -6.034218 6.46066)
-      (xy -6.039691 6.460708)
-      (xy -6.161807 6.46171)
-      (xy -6.161807 6.580125)
-      (xy -5.788202 6.580125)
-      (xy -5.794358 6.495014)
-      (xy -5.805526 6.430208)
-      (xy -5.826838 6.379819)
-      (xy -5.855222 6.349525)
-      (xy -5.87646 6.343295)
-      (xy -5.893142 6.331354)
-      (xy -5.895373 6.320775)
-      (xy -5.907511 6.298393)
-      (xy -5.931239 6.281913)
-      (xy -5.96226 6.255424)
-      (xy -5.976818 6.226872)
-      (xy -5.989635 6.194338)
-      (xy -6.00256 6.178266)
-      (xy -6.008961 6.16289)
-      (xy -5.994469 6.14445)
-      (xy -5.966459 6.128682)
-      (xy -5.932302 6.121321)
-      (xy -5.929302 6.121267)
-      (xy -5.886855 6.132535)
-      (xy -5.865769 6.150871)
-      (xy -5.840619 6.175957)
-      (xy -5.818191 6.174037)
-      (xy -5.795258 6.144168)
-      (xy -5.786921 6.12779)
-      (xy -5.771884 6.091633)
-      (xy -5.771315 6.07009)
-      (xy -5.783123 6.053781)
-      (xy -5.807927 6.036051)
-      (xy -5.820306 6.032456)
-      (xy -5.835524 6.021814)
-      (xy -5.836166 6.017654)
-      (xy -5.850072 6.01043)
-      (xy -5.888283 6.005319)
-      (xy -5.945538 6.002945)
-      (xy -5.960984 6.002852)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 60669bb2-ab23-4bd2-a3b3-29128112878a))
-  (fp_poly
-    (pts
-      (xy 2.811145 10.282043)
-      (xy 2.679968 10.332248)
-      (xy 2.566172 10.403839)
-      (xy 2.472806 10.494381)
-      (xy 2.401047 10.600337)
-      (xy 2.35207 10.718171)
-      (xy 2.327051 10.844347)
-      (xy 2.327168 10.975327)
-      (xy 2.353596 11.107577)
-      (xy 2.390301 11.203148)
-      (xy 2.457437 11.313086)
-      (xy 2.545641 11.405723)
-      (xy 2.650693 11.479156)
-      (xy 2.768376 11.531477)
-      (xy 2.894469 11.560782)
-      (xy 3.024754 11.565166)
-      (xy 3.147018 11.544929)
-      (xy 3.272501 11.497264)
-      (xy 3.380712 11.42856)
-      (xy 3.470728 11.342304)
-      (xy 3.541626 11.241981)
-      (xy 3.592484 11.131077)
-      (xy 3.62238 11.013078)
-      (xy 3.626492 10.950662)
-      (xy 3.512354 10.950662)
-      (xy 3.488665 11.067327)
-      (xy 3.437294 11.181514)
-      (xy 3.384484 11.258663)
-      (xy 3.303335 11.338269)
-      (xy 3.205368 11.397236)
-      (xy 3.096171 11.434274)
-      (xy 2.981336 11.448089)
-      (xy 2.86645 11.437389)
-      (xy 2.761125 11.402773)
-      (xy 2.658089 11.340436)
-      (xy 2.572348 11.259396)
-      (xy 2.505982 11.164045)
-      (xy 2.461068 11.058777)
-      (xy 2.439684 10.947983)
-      (xy 2.443908 10.836056)
-      (xy 2.460523 10.767332)
-      (xy 2.512487 10.650454)
-      (xy 2.583207 10.552941)
-      (xy 2.669143 10.475792)
-      (xy 2.766756 10.420004)
-      (xy 2.872506 10.386576)
-      (xy 2.982854 10.376507)
-      (xy 3.094261 10.390795)
-      (xy 3.203186 10.430439)
-      (xy 3.306091 10.496436)
-      (xy 3.334478 10.520808)
-      (xy 3.419425 10.616594)
-      (xy 3.477526 10.722218)
-      (xy 3.508572 10.8346)
-      (xy 3.512354 10.950662)
-      (xy 3.626492 10.950662)
-      (xy 3.630392 10.891471)
-      (xy 3.615596 10.76974)
-      (xy 3.577072 10.651373)
-      (xy 3.513895 10.539854)
-      (xy 3.436789 10.449773)
-      (xy 3.326048 10.360768)
-      (xy 3.205575 10.299099)
-      (xy 3.077908 10.265159)
-      (xy 2.945585 10.259342)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp bc9ef36e-3246-45b5-bdee-0b694a8192b1))
-  (fp_poly
-    (pts
-      (xy 5.823064 0.941595)
-      (xy 5.783251 0.945614)
-      (xy 5.758008 0.954286)
-      (xy 5.739836 0.969225)
-      (xy 5.736928 0.972483)
-      (xy 5.71651 1.002561)
-      (xy 5.709289 1.02429)
-      (xy 5.700517 1.042488)
-      (xy 5.694487 1.044228)
-      (xy 5.684094 1.05709)
-      (xy 5.679686 1.088081)
-      (xy 5.679685 1.088633)
-      (xy 5.683973 1.119812)
-      (xy 5.694303 1.133035)
-      (xy 5.694487 1.133039)
-      (xy 5.706764 1.145353)
-      (xy 5.709289 1.16083)
-      (xy 5.720039 1.193534)
-      (xy 5.731492 1.207048)
-      (xy 5.750249 1.230315)
-      (xy 5.753788 1.242165)
-      (xy 5.765545 1.260059)
-      (xy 5.794159 1.281698)
-      (xy 5.798451 1.284217)
-      (xy 5.831943 1.309047)
-      (xy 5.852401 1.334683)
-      (xy 5.852947 1.336023)
-      (xy 5.873242 1.368087)
-      (xy 5.885994 1.380499)
-      (xy 5.89264 1.389653)
-      (xy 5.88124 1.39526)
-      (xy 5.847841 1.398116)
-      (xy 5.7944 1.399002)
-      (xy 5.679685 1.399472)
-      (xy 5.679685 1.517887)
-      (xy 6.049732 1.517887)
-      (xy 6.049732 1.443878)
-      (xy 6.047069 1.40166)
-      (xy 6.040262 1.374863)
-      (xy 6.03493 1.369869)
-      (xy 6.021687 1.357928)
-      (xy 6.020128 1.348339)
-      (xy 6.010018 1.324436)
-      (xy 5.985297 1.294447)
-      (xy 5.981475 1.29078)
-      (xy 5.951704 1.262962)
-      (xy 5.930674 1.243196)
-      (xy 5.929415 1.242001)
-      (xy 5.887197 1.196749)
-      (xy 5.85381 1.15147)
-      (xy 5.834228 1.113562)
-      (xy 5.831298 1.096034)
-      (xy 5.847094 1.073797)
-      (xy 5.880521 1.061713)
-      (xy 5.921037 1.060839)
-      (xy 5.9581 1.072232)
-      (xy 5.971199 1.081995)
-      (xy 5.988178 1.09553)
-      (xy 6.003423 1.092868)
-      (xy 6.025157 1.070865)
-      (xy 6.036653 1.056994)
-      (xy 6.077337 1.007223)
-      (xy 6.041331 0.985292)
-      (xy 6.015217 0.965822)
-      (xy 6.005326 0.951988)
-      (xy 5.991685 0.946745)
-      (xy 5.955394 0.94278)
-      (xy 5.903399 0.940749)
-      (xy 5.884947 0.940615)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ebbc4e02-691e-45a9-aa88-74c58af6811d))
-  (fp_poly
-    (pts
-      (xy 6.682992 6.003459)
-      (xy 6.642872 6.006134)
-      (xy 6.620183 6.01216)
-      (xy 6.608844 6.02282)
-      (xy 6.604696 6.032789)
-      (xy 6.599503 6.07216)
-      (xy 6.60592 6.109179)
-      (xy 6.620334 6.137555)
-      (xy 6.639132 6.150994)
-      (xy 6.6587 6.143206)
-      (xy 6.664009 6.136069)
-      (xy 6.682663 6.128109)
-      (xy 6.721546 6.122736)
-      (xy 6.760097 6.121267)
-      (xy 6.810368 6.122753)
-      (xy 6.838689 6.12876)
-      (xy 6.852634 6.141617)
-      (xy 6.856433 6.150871)
-      (xy 6.869722 6.174792)
-      (xy 6.879634 6.180475)
-      (xy 6.891886 6.192478)
-      (xy 6.893438 6.202677)
-      (xy 6.901431 6.222375)
-      (xy 6.90824 6.22488)
-      (xy 6.917067 6.23811)
-      (xy 6.922363 6.271583)
-      (xy 6.923042 6.291489)
-      (xy 6.920102 6.331212)
-      (xy 6.912664 6.355041)
-      (xy 6.90824 6.358097)
-      (xy 6.896176 6.370482)
-      (xy 6.893438 6.387419)
-      (xy 6.880179 6.414982)
-      (xy 6.856433 6.426028)
-      (xy 6.828724 6.437456)
-      (xy 6.819429 6.448513)
-      (xy 6.806293 6.456778)
-      (xy 6.773481 6.461374)
-      (xy 6.760221 6.46171)
-      (xy 6.701014 6.46171)
-      (xy 6.701014 6.269286)
-      (xy 6.597401 6.269286)
-      (xy 6.597401 6.404571)
-      (xy 6.598757 6.478751)
-      (xy 6.606041 6.528275)
-      (xy 6.624074 6.55807)
-      (xy 6.657679 6.573063)
-      (xy 6.711676 6.578181)
-      (xy 6.767622 6.578508)
-      (xy 6.832196 6.576703)
-      (xy 6.877486 6.570678)
-      (xy 6.913745 6.558184)
-      (xy 6.948045 6.538982)
-      (xy 6.991696 6.507759)
-      (xy 7.020819 6.474514)
-      (xy 7.038199 6.432437)
-      (xy 7.046617 6.374722)
-      (xy 7.048857 6.294558)
-      (xy 7.048858 6.292357)
-      (xy 7.048091 6.22633)
-      (xy 7.044717 6.182033)
-      (xy 7.037126 6.151607)
-      (xy 7.023708 6.127194)
-      (xy 7.011853 6.11175)
-      (xy 6.965925 6.062041)
-      (xy 6.919841 6.029707)
-      (xy 6.865424 6.011391)
-      (xy 6.794497 6.003736)
-      (xy 6.746625 6.002852)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 31caeaa8-dd17-4314-97a5-ece82f3eebb5))
-  (fp_poly
-    (pts
-      (xy -4.86156 8.534459)
-      (xy -4.916587 8.541112)
-      (xy -4.951955 8.552474)
-      (xy -4.9784 8.567063)
-      (xy -4.989393 8.572844)
-      (xy -4.986447 8.585875)
-      (xy -4.973821 8.616173)
-      (xy -4.968149 8.628351)
-      (xy -4.947238 8.661237)
-      (xy -4.925398 8.680359)
-      (xy -4.908867 8.681959)
-      (xy -4.903648 8.667188)
-      (xy -4.890315 8.658844)
-      (xy -4.856132 8.653476)
-      (xy -4.827541 8.652386)
-      (xy -4.778023 8.655059)
-      (xy -4.744578 8.666489)
-      (xy -4.713897 8.691789)
-      (xy -4.707246 8.698624)
-      (xy -4.683168 8.726102)
-      (xy -4.670809 8.750952)
-      (xy -4.667424 8.783644)
-      (xy -4.670269 8.83465)
-      (xy -4.670579 8.838538)
-      (xy -4.680273 8.905853)
-      (xy -4.699194 8.949544)
-      (xy -4.731596 8.975172)
-      (xy -4.781738 8.988297)
-      (xy -4.785639 8.98884)
-      (xy -4.844441 8.996727)
-      (xy -4.844441 8.800405)
-      (xy -4.992459 8.800405)
-      (xy -4.992459 8.941022)
-      (xy -4.992012 9.006379)
-      (xy -4.989901 9.047627)
-      (xy -4.984968 9.070258)
-      (xy -4.976058 9.079765)
-      (xy -4.962856 9.08164)
-      (xy -4.938803 9.087839)
-      (xy -4.933252 9.096442)
-      (xy -4.919898 9.105329)
-      (xy -4.885126 9.110572)
-      (xy -4.836866 9.112393)
-      (xy -4.783049 9.111012)
-      (xy -4.731608 9.106649)
-      (xy -4.690473 9.099524)
-      (xy -4.667576 9.089858)
-      (xy -4.666818 9.089041)
-      (xy -4.639618 9.070086)
-      (xy -4.624301 9.066745)
-      (xy -4.601985 9.054437)
-      (xy -4.577141 9.024684)
-      (xy -4.556904 8.988023)
-      (xy -4.548405 8.954992)
-      (xy -4.548403 8.954625)
-      (xy -4.540016 8.935709)
-      (xy -4.533602 8.933622)
-      (xy -4.524723 8.92032)
-      (xy -4.519884 8.8858)
-      (xy -4.518863 8.838138)
-      (xy -4.521439 8.785413)
-      (xy -4.52739 8.7357)
-      (xy -4.536495 8.697076)
-      (xy -4.540339 8.687767)
-      (xy -4.579712 8.628014)
-      (xy -4.639895 8.568611)
-      (xy -4.65037 8.559874)
-      (xy -4.682918 8.54618)
-      (xy -4.73527 8.537225)
-      (xy -4.797969 8.53324)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9e2721f6-0120-45c8-9767-b3a099486284))
-  (fp_poly
-    (pts
-      (xy -5.114273 6.002895)
-      (xy -5.171216 6.008592)
-      (xy -5.211229 6.019439)
-      (xy -5.218742 6.023862)
-      (xy -5.234775 6.038759)
-      (xy -5.236966 6.055659)
-      (xy -5.225453 6.085213)
-      (xy -5.219701 6.097401)
-      (xy -5.198811 6.130216)
-      (xy -5.17698 6.149269)
-      (xy -5.160466 6.150803)
-      (xy -5.15528 6.136069)
-      (xy -5.141946 6.127725)
-      (xy -5.107764 6.122357)
-      (xy -5.079173 6.121267)
-      (xy -5.029383 6.124009)
-      (xy -4.995863 6.135495)
-      (xy -4.965531 6.160617)
-      (xy -4.960758 6.165538)
-      (xy -4.929423 6.213481)
-      (xy -4.917527 6.274195)
-      (xy -4.924222 6.352778)
-      (xy -4.927044 6.367762)
-      (xy -4.9487 6.408744)
-      (xy -4.990017 6.441865)
-      (xy -5.041066 6.460124)
-      (xy -5.060267 6.46171)
-      (xy -5.079524 6.459868)
-      (xy -5.09025 6.44989)
-      (xy -5.094932 6.425097)
-      (xy -5.096056 6.37881)
-      (xy -5.096072 6.365498)
-      (xy -5.096072 6.269286)
-      (xy -5.244091 6.269286)
-      (xy -5.244091 6.409904)
-      (xy -5.243296 6.476935)
-      (xy -5.24039 6.519355)
-      (xy -5.234589 6.542126)
-      (xy -5.225108 6.550212)
-      (xy -5.221888 6.550521)
-      (xy -5.20219 6.558514)
-      (xy -5.199685 6.565323)
-      (xy -5.18631 6.573926)
-      (xy -5.151384 6.578909)
-      (xy -5.102714 6.580497)
-      (xy -5.048101 6.578914)
-      (xy -4.995349 6.574385)
-      (xy -4.952263 6.567137)
-      (xy -4.926722 6.557451)
-      (xy -4.894925 6.540198)
-      (xy -4.874916 6.535626)
-      (xy -4.853226 6.523342)
-      (xy -4.828815 6.493676)
-      (xy -4.808737 6.457191)
-      (xy -4.800046 6.424448)
-      (xy -4.800035 6.423506)
-      (xy -4.791648 6.40459)
-      (xy -4.785233 6.402503)
-      (xy -4.776355 6.389201)
-      (xy -4.771516 6.354681)
-      (xy -4.770495 6.30702)
-      (xy -4.77307 6.254294)
-      (xy -4.779022 6.204581)
-      (xy -4.788127 6.165957)
-      (xy -4.791971 6.156648)
-      (xy -4.831343 6.096895)
-      (xy -4.891527 6.037492)
-      (xy -4.902002 6.028756)
-      (xy -4.934265 6.015279)
-      (xy -4.986558 6.006382)
-      (xy -5.04964 6.002206)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 1c0c790e-40c0-420a-bdee-4caeedfccb4b))
-  (fp_poly
-    (pts
-      (xy -6.404185 -6.651669)
-      (xy -6.458653 -6.647873)
-      (xy -6.504233 -6.641718)
-      (xy -6.533266 -6.633413)
-      (xy -6.536606 -6.631368)
-      (xy -6.553656 -6.614957)
-      (xy -6.554248 -6.59639)
-      (xy -6.54047 -6.566283)
-      (xy -6.525451 -6.540764)
-      (xy -6.508489 -6.528525)
-      (xy -6.480116 -6.526235)
-      (xy -6.437122 -6.529914)
-      (xy -6.364667 -6.533499)
-      (xy -6.314252 -6.52536)
-      (xy -6.279996 -6.503614)
-      (xy -6.259097 -6.472834)
-      (xy -6.246243 -6.435411)
-      (xy -6.238432 -6.390191)
-      (xy -6.236098 -6.346158)
-      (xy -6.239676 -6.312293)
-      (xy -6.2496 -6.297579)
-      (xy -6.250618 -6.297497)
-      (xy -6.263845 -6.28555)
-      (xy -6.26542 -6.275871)
-      (xy -6.278525 -6.243703)
-      (xy -6.311442 -6.215078)
-      (xy -6.35457 -6.196912)
-      (xy -6.379225 -6.193884)
-      (xy -6.42824 -6.193884)
-      (xy -6.42824 -6.40111)
-      (xy -6.561457 -6.40111)
-      (xy -6.561457 -6.253092)
-      (xy -6.560723 -6.184068)
-      (xy -6.558035 -6.139753)
-      (xy -6.552663 -6.115278)
-      (xy -6.543875 -6.105774)
-      (xy -6.539254 -6.105073)
-      (xy -6.519556 -6.097081)
-      (xy -6.517051 -6.090271)
-      (xy -6.503161 -6.083018)
-      (xy -6.465058 -6.077895)
-      (xy -6.408097 -6.075549)
-      (xy -6.394027 -6.075469)
-      (xy -6.32964 -6.076657)
-      (xy -6.287244 -6.081182)
-      (xy -6.259288 -6.090489)
-      (xy -6.239226 -6.105073)
-      (xy -6.210893 -6.126568)
-      (xy -6.190701 -6.134677)
-      (xy -6.167262 -6.146539)
-      (xy -6.141605 -6.174646)
-      (xy -6.122559 -6.207778)
-      (xy -6.117894 -6.227189)
-      (xy -6.110481 -6.24917)
-      (xy -6.102599 -6.253092)
-      (xy -6.09512 -6.266868)
-      (xy -6.090288 -6.304212)
-      (xy -6.088867 -6.359149)
-      (xy -6.088879 -6.360405)
-      (xy -6.092461 -6.429976)
-      (xy -6.102662 -6.478942)
-      (xy -6.118655 -6.512124)
-      (xy -6.140756 -6.549495)
-      (xy -6.155524 -6.580048)
-      (xy -6.156083 -6.581588)
-      (xy -6.175773 -6.602658)
-      (xy -6.207718 -6.616068)
-      (xy -6.238145 -6.626795)
-      (xy -6.250618 -6.639116)
-      (xy -6.264045 -6.64683)
-      (xy -6.299222 -6.651355)
-      (xy -6.348488 -6.652898)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp fa9bd237-d766-4231-9574-d5ef7e6c96a5))
-  (fp_poly
-    (pts
-      (xy 6.711191 -1.588952)
-      (xy 6.665658 -1.584654)
-      (xy 6.643282 -1.578151)
-      (xy 6.641806 -1.575702)
-      (xy 6.629818 -1.562571)
-      (xy 6.619604 -1.560901)
-      (xy 6.600951 -1.553886)
-      (xy 6.600806 -1.530605)
-      (xy 6.619188 -1.487699)
-      (xy 6.619984 -1.486156)
-      (xy 6.640962 -1.458161)
-      (xy 6.664171 -1.443045)
-      (xy 6.681648 -1.44428)
-      (xy 6.686212 -1.457288)
-      (xy 6.699536 -1.465676)
-      (xy 6.733653 -1.471041)
-      (xy 6.76136 -1.472089)
-      (xy 6.811742 -1.469036)
-      (xy 6.846383 -1.456582)
-      (xy 6.878809 -1.429786)
-      (xy 6.879775 -1.428822)
-      (xy 6.904633 -1.400285)
-      (xy 6.917659 -1.371193)
-      (xy 6.922519 -1.330341)
-      (xy 6.923042 -1.296603)
-      (xy 6.921579 -1.245536)
-      (xy 6.915741 -1.216587)
-      (xy 6.903349 -1.202352)
-      (xy 6.894195 -1.198495)
-      (xy 6.865781 -1.177586)
-      (xy 6.856193 -1.160493)
-      (xy 6.841969 -1.140546)
-      (xy 6.810945 -1.132403)
-      (xy 6.788828 -1.131647)
-      (xy 6.730618 -1.131647)
-      (xy 6.730618 -1.338873)
-      (xy 6.597401 -1.338873)
-      (xy 6.597401 -1.190854)
-      (xy 6.598135 -1.12183)
-      (xy 6.600823 -1.077515)
-      (xy 6.606195 -1.05304)
-      (xy 6.614983 -1.043536)
-      (xy 6.619604 -1.042835)
-      (xy 6.639301 -1.034843)
-      (xy 6.641806 -1.028033)
-      (xy 6.655714 -1.020793)
-      (xy 6.693966 -1.015897)
-      (xy 6.751354 -1.013946)
-      (xy 6.763922 -1.013957)
-      (xy 6.828806 -1.01562)
-      (xy 6.873285 -1.020959)
-      (xy 6.906505 -1.031899)
-      (xy 6.937611 -1.050362)
-      (xy 6.937844 -1.050523)
-      (xy 6.984783 -1.082978)
-      (xy 7.016237 -1.107881)
-      (xy 7.03529 -1.13216)
-      (xy 7.045028 -1.162746)
-      (xy 7.048537 -1.206566)
-      (xy 7.048902 -1.270551)
-      (xy 7.048858 -1.299823)
-      (xy 7.048858 -1.466905)
-      (xy 7.00189 -1.513903)
-      (xy 6.968285 -1.542627)
-      (xy 6.939354 -1.55925)
-      (xy 6.931581 -1.560901)
-      (xy 6.911164 -1.568552)
-      (xy 6.90824 -1.575702)
-      (xy 6.894267 -1.582795)
-      (xy 6.855587 -1.587854)
-      (xy 6.79706 -1.59034)
-      (xy 6.775023 -1.590504)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d38e7858-34a0-463d-850a-bbe5143649c3))
-  (fp_poly
-    (pts
-      (xy -6.404185 -9.182788)
-      (xy -6.458653 -9.178992)
-      (xy -6.504233 -9.172837)
-      (xy -6.533266 -9.164532)
-      (xy -6.536606 -9.162487)
-      (xy -6.553656 -9.146076)
-      (xy -6.554248 -9.127508)
-      (xy -6.54047 -9.097402)
-      (xy -6.525451 -9.071883)
-      (xy -6.508489 -9.059644)
-      (xy -6.480116 -9.057354)
-      (xy -6.437122 -9.061033)
-      (xy -6.364667 -9.064617)
-      (xy -6.314252 -9.056479)
-      (xy -6.279996 -9.034732)
-      (xy -6.259097 -9.003953)
-      (xy -6.246617 -8.967516)
-      (xy -6.23871 -8.922737)
-      (xy -6.235896 -8.878661)
-      (xy -6.238695 -8.84433)
-      (xy -6.247628 -8.82879)
-      (xy -6.249013 -8.828616)
-      (xy -6.262486 -8.816179)
-      (xy -6.270796 -8.795312)
-      (xy -6.292615 -8.762983)
-      (xy -6.333737 -8.737728)
-      (xy -6.383886 -8.725402)
-      (xy -6.394187 -8.725003)
-      (xy -6.411999 -8.726927)
-      (xy -6.422196 -8.736985)
-      (xy -6.426891 -8.761603)
-      (xy -6.428194 -8.807209)
-      (xy -6.42824 -8.828616)
-      (xy -6.42824 -8.932229)
-      (xy -6.561457 -8.932229)
-      (xy -6.561457 -8.785937)
-      (xy -6.561263 -8.718333)
-      (xy -6.557493 -8.672401)
-      (xy -6.545363 -8.643951)
-      (xy -6.520091 -8.628795)
-      (xy -6.476894 -8.622745)
-      (xy -6.41099 -8.621612)
-      (xy -6.373791 -8.621592)
-      (xy -6.304177 -8.623418)
-      (xy -6.258984 -8.62968)
-      (xy -6.233257 -8.64114)
-      (xy -6.23053 -8.643593)
-      (xy -6.203687 -8.661945)
-      (xy -6.188767 -8.665889)
-      (xy -6.169202 -8.678099)
-      (xy -6.146287 -8.707482)
-      (xy -6.126798 -8.743394)
-      (xy -6.117509 -8.775191)
-      (xy -6.117401 -8.778009)
-      (xy -6.109014 -8.796925)
-      (xy -6.102599 -8.799013)
-      (xy -6.092293 -8.812171)
-      (xy -6.08753 -8.846329)
-      (xy -6.087787 -8.893513)
-      (xy -6.092538 -8.945746)
-      (xy -6.10126 -8.995053)
-      (xy -6.113428 -9.03346)
-      (xy -6.118655 -9.043243)
-      (xy -6.140756 -9.080614)
-      (xy -6.155524 -9.111167)
-      (xy -6.156083 -9.112707)
-      (xy -6.175773 -9.133777)
-      (xy -6.207718 -9.147187)
-      (xy -6.238145 -9.157914)
-      (xy -6.250618 -9.170235)
-      (xy -6.264045 -9.177949)
-      (xy -6.299222 -9.182474)
-      (xy -6.348488 -9.184017)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 1ec987c2-2b50-4649-aa71-95d58dc6a502))
-  (fp_poly
-    (pts
-      (xy -6.383835 -5.320574)
-      (xy -6.132203 -5.320574)
-      (xy -6.132318 -5.272468)
-      (xy -6.138771 -5.23387)
-      (xy -6.162867 -5.210619)
-      (xy -6.172274 -5.20586)
-      (xy -6.213851 -5.191958)
-      (xy -6.246168 -5.187358)
-      (xy -6.27254 -5.181893)
-      (xy -6.280222 -5.172556)
-      (xy -6.292446 -5.160025)
-      (xy -6.306265 -5.157754)
-      (xy -6.328712 -5.150076)
-      (xy -6.353236 -5.124276)
-      (xy -6.383445 -5.0762)
-      (xy -6.394514 -5.056149)
-      (xy -6.405489 -5.023526)
-      (xy -6.411692 -4.981161)
-      (xy -6.412883 -4.938629)
-      (xy -6.408823 -4.905503)
-      (xy -6.399273 -4.891358)
-      (xy -6.398636 -4.89132)
-      (xy -6.385505 -4.879331)
-      (xy -6.383835 -4.869117)
-      (xy -6.375842 -4.84942)
-      (xy -6.369033 -4.846915)
-      (xy -6.355348 -4.835189)
-      (xy -6.354231 -4.828001)
-      (xy -6.343967 -4.805379)
-      (xy -6.320927 -4.779895)
-      (xy -6.301727 -4.766621)
-      (xy -6.276082 -4.757779)
-      (xy -6.237753 -4.752358)
-      (xy -6.180504 -4.749348)
-      (xy -6.124802 -4.748118)
-      (xy -6.055899 -4.747724)
-      (xy -5.99612 -4.748669)
-      (xy -5.952819 -4.750762)
-      (xy -5.935179 -4.753077)
-      (xy -5.919619 -4.764097)
-      (xy -5.915202 -4.788623)
-      (xy -5.9219 -4.831704)
-      (xy -5.93448 -4.880219)
-      (xy -5.951745 -4.90216)
-      (xy -5.976729 -4.903914)
-      (xy -5.991585 -4.89132)
-      (xy -6.010206 -4.883427)
-      (xy -6.049166 -4.878057)
-      (xy -6.089344 -4.876518)
-      (xy -6.143465 -4.878617)
-      (xy -6.178698 -4.886956)
-      (xy -6.205587 -4.904603)
-      (xy -6.214286 -4.91285)
-      (xy -6.239007 -4.943105)
-      (xy -6.250512 -4.968088)
-      (xy -6.250618 -4.969764)
-      (xy -6.238482 -4.998135)
-      (xy -6.210069 -5.024712)
-      (xy -6.177373 -5.038913)
-      (xy -6.171743 -5.039339)
-      (xy -6.150469 -5.04661)
-      (xy -6.147005 -5.054141)
-      (xy -6.133522 -5.062025)
-      (xy -6.098302 -5.06737)
-      (xy -6.058194 -5.068943)
-      (xy -5.969382 -5.068943)
-      (xy -5.969382 -5.133277)
-      (xy -5.970462 -5.178017)
-      (xy -5.973337 -5.240902)
-      (xy -5.977459 -5.310568)
-      (xy -5.979 -5.333102)
-      (xy -5.988617 -5.468593)
-      (xy -6.383835 -5.468593)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c5ba7456-fbcc-46a0-ab30-1d5b6c986dd6))
-  (fp_poly
-    (pts
-      (xy 6.67819 0.941933)
-      (xy 6.633061 0.947941)
-      (xy 6.60857 0.961718)
-      (xy 6.600259 0.986341)
-      (xy 6.603665 1.024891)
-      (xy 6.606151 1.038814)
-      (xy 6.619785 1.074496)
-      (xy 6.639871 1.088983)
-      (xy 6.660568 1.078739)
-      (xy 6.664009 1.073831)
-      (xy 6.6828 1.065598)
-      (xy 6.721352 1.060224)
-      (xy 6.753694 1.059029)
-      (xy 6.819054 1.066909)
-      (xy 6.866141 1.088926)
-      (xy 6.890782 1.122651)
-      (xy 6.893438 1.14044)
-      (xy 6.901431 1.160138)
-      (xy 6.90824 1.162642)
-      (xy 6.917566 1.175761)
-      (xy 6.922697 1.208478)
-      (xy 6.923042 1.220976)
-      (xy 6.919601 1.26039)
-      (xy 6.911055 1.285653)
-      (xy 6.90824 1.288458)
-      (xy 6.895764 1.309356)
-      (xy 6.893438 1.326055)
-      (xy 6.88005 1.352777)
-      (xy 6.856433 1.36379)
-      (xy 6.828724 1.375219)
-      (xy 6.819429 1.386275)
-      (xy 6.806293 1.39454)
-      (xy 6.773481 1.399136)
-      (xy 6.760221 1.399472)
-      (xy 6.701014 1.399472)
-      (xy 6.701014 1.192246)
-      (xy 6.597401 1.192246)
-      (xy 6.597401 1.334933)
-      (xy 6.598584 1.410853)
-      (xy 6.605171 1.462056)
-      (xy 6.621712 1.493414)
-      (xy 6.652762 1.509801)
-      (xy 6.702872 1.516092)
-      (xy 6.767622 1.517147)
-      (xy 6.829989 1.516116)
-      (xy 6.87159 1.511482)
-      (xy 6.901216 1.501317)
-      (xy 6.927659 1.483697)
-      (xy 6.930443 1.481469)
-      (xy 6.971341 1.448633)
-      (xy 7.009972 1.417924)
-      (xy 7.011853 1.416441)
-      (xy 7.028821 1.401259)
-      (xy 7.039618 1.383641)
-      (xy 7.04563 1.356994)
-      (xy 7.048247 1.314728)
-      (xy 7.048854 1.250251)
-      (xy 7.048858 1.240626)
-      (xy 7.047893 1.169271)
-      (xy 7.044396 1.121364)
-      (xy 7.037458 1.090796)
-      (xy 7.026172 1.071454)
-      (xy 7.023281 1.068363)
-      (xy 6.998343 1.040589)
-      (xy 6.986276 1.024252)
-      (xy 6.967158 1.003982)
-      (xy 6.934796 0.977909)
-      (xy 6.928158 0.973176)
-      (xy 6.900504 0.956983)
-      (xy 6.86909 0.947142)
-      (xy 6.825803 0.942186)
-      (xy 6.762529 0.940643)
-      (xy 6.748419 0.940615)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d15d9a45-c141-4c3a-a593-9ae75672406b))
-  (fp_poly
-    (pts
-      (xy -4.862641 3.471777)
-      (xy -4.919584 3.477473)
-      (xy -4.959598 3.48832)
-      (xy -4.96711 3.492743)
-      (xy -4.983143 3.507641)
-      (xy -4.985334 3.52454)
-      (xy -4.973822 3.554094)
-      (xy -4.968069 3.566282)
-      (xy -4.947179 3.599097)
-      (xy -4.925348 3.61815)
-      (xy -4.908834 3.619685)
-      (xy -4.903648 3.60495)
-      (xy -4.890265 3.596844)
-      (xy -4.855742 3.591468)
-      (xy -4.822238 3.590148)
-      (xy -4.777655 3.592582)
-      (xy -4.748085 3.598859)
-      (xy -4.740828 3.60495)
-      (xy -4.728813 3.618022)
-      (xy -4.718258 3.619752)
-      (xy -4.694753 3.633254)
-      (xy -4.677765 3.669501)
-      (xy -4.668554 3.722104)
-      (xy -4.668385 3.784673)
-      (xy -4.675412 3.836644)
-      (xy -4.697068 3.877625)
-      (xy -4.738386 3.910747)
-      (xy -4.789434 3.929005)
-      (xy -4.808636 3.930591)
-      (xy -4.827349 3.928917)
-      (xy -4.83806 3.919599)
-      (xy -4.842995 3.896194)
-      (xy -4.844381 3.852258)
-      (xy -4.844441 3.826978)
-      (xy -4.844441 3.723365)
-      (xy -4.992459 3.723365)
-      (xy -4.992459 3.871384)
-      (xy -4.992053 3.938753)
-      (xy -4.99012 3.98188)
-      (xy -4.985588 4.006123)
-      (xy -4.977385 4.01684)
-      (xy -4.964441 4.01939)
-      (xy -4.962856 4.019402)
-      (xy -4.938803 4.025601)
-      (xy -4.933252 4.034204)
-      (xy -4.919924 4.042966)
-      (xy -4.885279 4.047906)
-      (xy -4.83732 4.049267)
-      (xy -4.784053 4.047295)
-      (xy -4.733483 4.042232)
-      (xy -4.693614 4.034323)
-      (xy -4.675091 4.026333)
-      (xy -4.643293 4.009079)
-      (xy -4.623284 4.004507)
-      (xy -4.601594 3.992223)
-      (xy -4.577183 3.962557)
-      (xy -4.557105 3.926072)
-      (xy -4.548415 3.893329)
-      (xy -4.548403 3.892387)
-      (xy -4.540016 3.873472)
-      (xy -4.533602 3.871384)
-      (xy -4.524723 3.858082)
-      (xy -4.519884 3.823562)
-      (xy -4.518863 3.775901)
-      (xy -4.521439 3.723175)
-      (xy -4.52739 3.673462)
-      (xy -4.536495 3.634839)
-      (xy -4.540339 3.62553)
-      (xy -4.579712 3.565776)
-      (xy -4.639895 3.506373)
-      (xy -4.65037 3.497637)
-      (xy -4.682633 3.48416)
-      (xy -4.734926 3.475263)
-      (xy -4.798009 3.471087)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 62cf05a8-2bb1-46f0-8dc6-33cd3791401d))
-  (fp_poly
-    (pts
-      (xy -1.020866 4.29133)
-      (xy -1.082345 4.306224)
-      (xy -1.129156 4.328132)
-      (xy -1.155312 4.354673)
-      (xy -1.158776 4.368708)
-      (xy -1.167255 4.387449)
-      (xy -1.173578 4.389449)
-      (xy -1.181313 4.403043)
-      (xy -1.186609 4.439054)
-      (xy -1.18838 4.485661)
-      (xy -1.186443 4.534656)
-      (xy -1.181375 4.569309)
-      (xy -1.174576 4.581873)
-      (xy -1.159985 4.594196)
-      (xy -1.150256 4.615177)
-      (xy -1.138341 4.64117)
-      (xy -1.116419 4.666954)
-      (xy -1.078538 4.698737)
-      (xy -1.048964 4.720864)
-      (xy -1.022397 4.74412)
-      (xy -1.010778 4.761822)
-      (xy -1.010758 4.762276)
-      (xy -1.000851 4.780583)
-      (xy -0.976705 4.807228)
-      (xy -0.973753 4.810006)
-      (xy -0.948737 4.83568)
-      (xy -0.936895 4.852733)
-      (xy -0.936748 4.853705)
-      (xy -0.950477 4.857746)
-      (xy -0.987378 4.860917)
-      (xy -1.041023 4.862788)
-      (xy -1.077366 4.863109)
-      (xy -1.217984 4.863109)
-      (xy -1.217984 5.011127)
-      (xy -0.71472 5.011127)
-      (xy -0.71472 4.967595)
-      (xy -0.719283 4.933412)
-      (xy -0.729522 4.914915)
-      (xy -0.741914 4.894058)
-      (xy -0.744324 4.876743)
-      (xy -0.754784 4.838261)
-      (xy -0.782863 4.787996)
-      (xy -0.823611 4.733326)
-      (xy -0.872078 4.681624)
-      (xy -0.880458 4.673905)
-      (xy -0.943487 4.615295)
-      (xy -0.986192 4.570333)
-      (xy -1.01184 4.534783)
-      (xy -1.023698 4.504408)
-      (xy -1.02556 4.485774)
-      (xy -1.016272 4.454337)
-      (xy -0.988458 4.439908)
-      (xy -0.936336 4.436065)
-      (xy -0.880518 4.445619)
-      (xy -0.833917 4.465586)
-      (xy -0.817284 4.47947)
-      (xy -0.801334 4.495231)
-      (xy -0.788112 4.494813)
-      (xy -0.7703 4.475)
-      (xy -0.753716 4.45153)
-      (xy -0.730418 4.415644)
-      (xy -0.716478 4.389797)
-      (xy -0.71472 4.383896)
-      (xy -0.727647 4.35942)
-      (xy -0.760034 4.336117)
-      (xy -0.802294 4.320869)
-      (xy -0.802673 4.320792)
-      (xy -0.83414 4.310835)
-      (xy -0.847912 4.299222)
-      (xy -0.847937 4.298788)
-      (xy -0.861481 4.292381)
-      (xy -0.8971 4.28775)
-      (xy -0.947278 4.285843)
-      (xy -0.950704 4.285836)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9ceb141b-f522-49ff-9765-62a7c2734ad2))
-  (fp_poly
-    (pts
-      (xy -5.880571 9.821733)
-      (xy -5.632049 9.821733)
-      (xy -5.62656 9.87929)
-      (xy -5.621071 9.936846)
-      (xy -5.692217 9.945272)
-      (xy -5.77013 9.967279)
-      (xy -5.833177 10.013938)
-      (xy -5.879093 10.078464)
-      (xy -5.900127 10.128872)
-      (xy -5.90942 10.176931)
-      (xy -5.906031 10.21395)
-      (xy -5.895373 10.228785)
-      (xy -5.883795 10.249247)
-      (xy -5.880571 10.273066)
-      (xy -5.868917 10.306326)
-      (xy -5.850967 10.317596)
-      (xy -5.827068 10.33017)
-      (xy -5.821364 10.33911)
-      (xy -5.809306 10.352678)
-      (xy -5.779472 10.370934)
-      (xy -5.771021 10.375117)
-      (xy -5.728228 10.38708)
-      (xy -5.664926 10.394639)
-      (xy -5.589934 10.397435)
-      (xy -5.512068 10.395111)
-      (xy -5.4465 10.388296)
-      (xy -5.420554 10.382395)
-      (xy -5.410377 10.369263)
-      (xy -5.411794 10.339904)
-      (xy -5.414903 10.320205)
-      (xy -5.422716 10.279245)
-      (xy -5.429893 10.25155)
-      (xy -5.431695 10.247287)
-      (xy -5.451394 10.237821)
-      (xy -5.483107 10.237217)
-      (xy -5.510825 10.244789)
-      (xy -5.517926 10.250987)
-      (xy -5.537098 10.259981)
-      (xy -5.574628 10.265232)
-      (xy -5.592808 10.265789)
-      (xy -5.632228 10.262813)
-      (xy -5.655691 10.255292)
-      (xy -5.658543 10.250987)
-      (xy -5.670867 10.23874)
-      (xy -5.686542 10.236186)
-      (xy -5.712838 10.22304)
-      (xy -5.723012 10.202435)
-      (xy -5.726602 10.15651)
-      (xy -5.715216 10.12074)
-      (xy -5.691923 10.10347)
-      (xy -5.686421 10.102969)
-      (xy -5.663322 10.096428)
-      (xy -5.658543 10.088167)
-      (xy -5.645231 10.079723)
-      (xy -5.611193 10.074364)
-      (xy -5.584534 10.073365)
-      (xy -5.542316 10.070703)
-      (xy -5.515519 10.063895)
-      (xy -5.510525 10.058563)
-      (xy -5.498127 10.046537)
-      (xy -5.480921 10.043761)
-      (xy -5.466127 10.041273)
-      (xy -5.457282 10.029823)
-      (xy -5.45288 10.003436)
-      (xy -5.451418 9.956138)
-      (xy -5.451317 9.92622)
-      (xy -5.453062 9.869949)
-      (xy -5.45769 9.825802)
-      (xy -5.464293 9.801555)
-      (xy -5.466119 9.799531)
-      (xy -5.47558 9.780123)
-      (xy -5.48065 9.74331)
-      (xy -5.480921 9.732049)
-      (xy -5.480921 9.673715)
-      (xy -5.880571 9.673715)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0984c573-6098-4e6d-8be5-b91a766a19d9))
-  (fp_poly
-    (pts
-      (xy -5.945307 0.941484)
-      (xy -5.999736 0.945105)
-      (xy -6.04525 0.951235)
-      (xy -6.074184 0.959707)
-      (xy -6.07725 0.961624)
-      (xy -6.093283 0.976522)
-      (xy -6.095474 0.993421)
-      (xy -6.083962 1.022976)
-      (xy -6.078209 1.035163)
-      (xy -6.057319 1.067978)
-      (xy -6.035488 1.087031)
-      (xy -6.018974 1.088566)
-      (xy -6.013788 1.073831)
-      (xy -6.000452 1.065501)
-      (xy -5.96625 1.060132)
-      (xy -5.937399 1.059029)
-      (xy -5.888598 1.061461)
-      (xy -5.856424 1.072152)
-      (xy -5.828066 1.096193)
-      (xy -5.818984 1.106101)
-      (xy -5.790888 1.144933)
-      (xy -5.77881 1.186736)
-      (xy -5.776958 1.224516)
-      (xy -5.779714 1.265851)
-      (xy -5.786736 1.291603)
-      (xy -5.79176 1.295859)
-      (xy -5.804021 1.308178)
-      (xy -5.806562 1.323761)
-      (xy -5.819849 1.354528)
-      (xy -5.85371 1.380875)
-      (xy -5.89915 1.397023)
-      (xy -5.924456 1.399472)
-      (xy -5.969382 1.399472)
-      (xy -5.969382 1.192246)
-      (xy -6.102599 1.192246)
-      (xy -6.102599 1.340265)
-      (xy -6.101865 1.409289)
-      (xy -6.099177 1.453604)
-      (xy -6.093805 1.478079)
-      (xy -6.085017 1.487583)
-      (xy -6.080396 1.488284)
-      (xy -6.060699 1.496276)
-      (xy -6.058194 1.503085)
-      (xy -6.044303 1.510339)
-      (xy -6.0062 1.515461)
-      (xy -5.949239 1.517807)
-      (xy -5.935169 1.517887)
-      (xy -5.870782 1.5167)
-      (xy -5.828387 1.512175)
-      (xy -5.80043 1.502868)
-      (xy -5.780368 1.488284)
-      (xy -5.752726 1.466847)
-      (xy -5.733748 1.45868)
-      (xy -5.710018 1.446983)
-      (xy -5.683607 1.419352)
-      (xy -5.663697 1.386971)
-      (xy -5.658543 1.367078)
-      (xy -5.651772 1.344584)
-      (xy -5.643741 1.340265)
-      (xy -5.635471 1.32695)
-      (xy -5.630658 1.292519)
-      (xy -5.629176 1.245239)
-      (xy -5.630896 1.193382)
-      (xy -5.635693 1.145215)
-      (xy -5.64344 1.109008)
-      (xy -5.647442 1.099534)
-      (xy -5.673448 1.060988)
-      (xy -5.706663 1.021913)
-      (xy -5.739935 0.989704)
-      (xy -5.766111 0.971761)
-      (xy -5.772461 0.970218)
-      (xy -5.790218 0.961198)
-      (xy -5.79176 0.955416)
-      (xy -5.80519 0.947337)
-      (xy -5.840368 0.942433)
-      (xy -5.889629 0.940537)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 84819531-bce6-47fc-903a-968712021d31))
-  (fp_poly
-    (pts
-      (xy -6.404165 -1.589635)
-      (xy -6.458594 -1.586014)
-      (xy -6.504108 -1.579884)
-      (xy -6.533042 -1.571412)
-      (xy -6.536108 -1.569494)
-      (xy -6.552141 -1.554597)
-      (xy -6.554332 -1.537697)
-      (xy -6.542819 -1.508143)
-      (xy -6.537067 -1.495956)
-      (xy -6.516177 -1.463141)
-      (xy -6.494346 -1.444087)
-      (xy -6.477832 -1.442553)
-      (xy -6.472646 -1.457288)
-      (xy -6.459263 -1.465394)
-      (xy -6.424739 -1.47077)
-      (xy -6.391236 -1.472089)
-      (xy -6.346653 -1.469656)
-      (xy -6.317082 -1.463379)
-      (xy -6.309825 -1.457288)
-      (xy -6.298127 -1.443455)
-      (xy -6.291323 -1.44237)
-      (xy -6.272462 -1.430196)
-      (xy -6.254318 -1.402415)
-      (xy -6.243391 -1.366544)
-      (xy -6.237387 -1.322532)
-      (xy -6.236512 -1.279741)
-      (xy -6.240975 -1.247534)
-      (xy -6.250618 -1.23526)
-      (xy -6.263845 -1.223312)
-      (xy -6.26542 -1.213633)
-      (xy -6.278525 -1.181465)
-      (xy -6.311442 -1.15284)
-      (xy -6.35457 -1.134674)
-      (xy -6.379225 -1.131647)
-      (xy -6.42824 -1.131647)
-      (xy -6.42824 -1.338873)
-      (xy -6.561457 -1.338873)
-      (xy -6.561457 -1.190854)
-      (xy -6.560723 -1.12183)
-      (xy -6.558035 -1.077515)
-      (xy -6.552663 -1.05304)
-      (xy -6.543875 -1.043536)
-      (xy -6.539254 -1.042835)
-      (xy -6.519556 -1.034843)
-      (xy -6.517051 -1.028033)
-      (xy -6.503161 -1.02078)
-      (xy -6.465058 -1.015658)
-      (xy -6.408097 -1.013311)
-      (xy -6.394027 -1.013232)
-      (xy -6.32964 -1.014419)
-      (xy -6.287244 -1.018944)
-      (xy -6.259288 -1.028251)
-      (xy -6.239226 -1.042835)
-      (xy -6.209276 -1.064463)
-      (xy -6.186331 -1.072439)
-      (xy -6.16304 -1.084623)
-      (xy -6.138613 -1.113666)
-      (xy -6.121162 -1.148306)
-      (xy -6.117401 -1.16813)
-      (xy -6.109568 -1.18816)
-      (xy -6.102599 -1.190854)
-      (xy -6.093551 -1.204151)
-      (xy -6.088685 -1.238689)
-      (xy -6.087756 -1.286439)
-      (xy -6.090518 -1.33937)
-      (xy -6.096727 -1.389453)
-      (xy -6.106138 -1.428658)
-      (xy -6.110154 -1.438347)
-      (xy -6.137245 -1.481479)
-      (xy -6.171411 -1.521312)
-      (xy -6.205238 -1.550294)
-      (xy -6.230433 -1.560901)
-      (xy -6.248799 -1.56958)
-      (xy -6.250618 -1.575702)
-      (xy -6.264047 -1.583782)
-      (xy -6.299226 -1.588686)
-      (xy -6.348487 -1.590582)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ef00d866-3c74-4c5c-92e0-83db4cff5935))
-  (fp_poly
-    (pts
-      (xy 5.844783 8.533916)
-      (xy 5.797474 8.54137)
-      (xy 5.771617 8.549496)
-      (xy 5.73512 8.573788)
-      (xy 5.714815 8.603144)
-      (xy 5.714505 8.60428)
-      (xy 5.703017 8.630196)
-      (xy 5.692882 8.637584)
-      (xy 5.687343 8.651339)
-      (xy 5.682948 8.688427)
-      (xy 5.680257 8.742583)
-      (xy 5.679685 8.785603)
-      (xy 5.681092 8.854365)
-      (xy 5.68503 8.904079)
-      (xy 5.691071 8.93048)
-      (xy 5.694487 8.933622)
-      (xy 5.707284 8.945747)
-      (xy 5.709289 8.957922)
-      (xy 5.722316 8.99226)
-      (xy 5.756009 9.027488)
-      (xy 5.80228 9.057438)
-      (xy 5.853044 9.075945)
-      (xy 5.867053 9.078247)
-      (xy 5.908281 9.085384)
-      (xy 5.93545 9.094713)
-      (xy 5.939931 9.098405)
-      (xy 5.9593 9.10832)
-      (xy 5.983997 9.111244)
-      (xy 6.007596 9.10771)
-      (xy 6.017873 9.091515)
-      (xy 6.020128 9.054267)
-      (xy 6.020128 9.054048)
-      (xy 6.018721 9.019173)
-      (xy 6.009272 9.001142)
-      (xy 5.983941 8.99234)
-      (xy 5.951569 8.987456)
-      (xy 5.889584 8.97024)
-      (xy 5.854053 8.944739)
-      (xy 5.825097 8.911419)
-      (xy 5.911511 8.899481)
-      (xy 5.98772 8.88088)
-      (xy 6.03932 8.847888)
-      (xy 6.068954 8.797674)
-      (xy 6.079265 8.727409)
-      (xy 6.079336 8.719797)
-      (xy 6.078584 8.705815)
-      (xy 5.931317 8.705815)
-      (xy 5.922911 8.75869)
-      (xy 5.896191 8.789186)
-      (xy 5.848905 8.799792)
-      (xy 5.846206 8.799842)
-      (xy 5.812786 8.796958)
-      (xy 5.799782 8.782873)
-      (xy 5.7981 8.764274)
-      (xy 5.803558 8.732932)
-      (xy 5.812902 8.718994)
-      (xy 5.825573 8.698005)
-      (xy 5.827704 8.6827)
-      (xy 5.840042 8.654954)
-      (xy 5.870973 8.642046)
-      (xy 5.903798 8.645647)
-      (xy 5.924352 8.662801)
-      (xy 5.931263 8.700565)
-      (xy 5.931317 8.705815)
-      (xy 6.078584 8.705815)
-      (xy 6.076925 8.674965)
-      (xy 6.0707 8.645104)
-      (xy 6.064534 8.637584)
-      (xy 6.050331 8.626182)
-      (xy 6.049732 8.621725)
-      (xy 6.040224 8.598935)
-      (xy 6.028851 8.584985)
-      (xy 6.008735 8.559973)
-      (xy 6.002746 8.548433)
-      (xy 5.985362 8.538074)
-      (xy 5.947435 8.532228)
-      (xy 5.897672 8.530856)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b11aed1e-03fc-4bd5-bcdc-7926c7d74922))
-  (fp_poly
-    (pts
-      (xy 6.292776 8.537899)
-      (xy 6.247153 8.544979)
-      (xy 6.223664 8.552469)
-      (xy 6.192212 8.575719)
-      (xy 6.17651 8.600575)
-      (xy 6.169336 8.647014)
-      (xy 6.169013 8.698366)
-      (xy 6.174847 8.743561)
-      (xy 6.186141 8.771525)
-      (xy 6.187311 8.772734)
-      (xy 6.19675 8.789469)
-      (xy 6.186543 8.811047)
-      (xy 6.172509 8.827285)
-      (xy 6.149023 8.862802)
-      (xy 6.139385 8.909137)
-      (xy 6.138543 8.935783)
-      (xy 6.140962 8.977291)
-      (xy 6.147129 9.003242)
-      (xy 6.151619 9.007631)
-      (xy 6.165678 9.019879)
-      (xy 6.171902 9.035193)
-      (xy 6.195002 9.067629)
-      (xy 6.242608 9.092174)
-      (xy 6.310289 9.10719)
-      (xy 6.377647 9.111244)
-      (xy 6.429924 9.109248)
-      (xy 6.465948 9.103918)
-      (xy 6.478986 9.096442)
-      (xy 6.490975 9.08331)
-      (xy 6.501189 9.08164)
-      (xy 6.518891 9.07426)
-      (xy 6.521937 9.048958)
-      (xy 6.514081 9.011403)
-      (xy 6.506379 8.992387)
-      (xy 6.491268 8.983945)
-      (xy 6.460602 8.983841)
-      (xy 6.426647 8.987399)
-      (xy 6.354537 8.992314)
-      (xy 6.306949 8.986172)
-      (xy 6.280496 8.967791)
-      (xy 6.271792 8.935991)
-      (xy 6.27176 8.93334)
-      (xy 6.276478 8.900962)
-      (xy 6.293995 8.889639)
-      (xy 6.301364 8.889216)
-      (xy 6.325416 8.883017)
-      (xy 6.330967 8.874414)
-      (xy 6.343979 8.86463)
-      (xy 6.375975 8.85974)
-      (xy 6.382774 8.859612)
-      (xy 6.415944 8.85782)
-      (xy 6.430685 8.846752)
-      (xy 6.434464 8.817875)
-      (xy 6.43458 8.800405)
-      (xy 6.43458 8.741197)
-      (xy 6.373304 8.741197)
-      (xy 6.324042 8.734601)
-      (xy 6.292867 8.717329)
-      (xy 6.283786 8.69316)
-      (xy 6.297086 8.669351)
-      (xy 6.327023 8.655603)
-      (xy 6.372074 8.650329)
-      (xy 6.418959 8.653622)
-      (xy 6.454401 8.665577)
-      (xy 6.458019 8.668213)
-      (xy 6.474872 8.672756)
-      (xy 6.492334 8.653663)
-      (xy 6.500267 8.639367)
-      (xy 6.519262 8.596349)
-      (xy 6.520079 8.572635)
-      (xy 6.502399 8.563917)
-      (xy 6.494661 8.563575)
-      (xy 6.466325 8.556778)
-      (xy 6.456783 8.548773)
-      (xy 6.436843 8.539885)
-      (xy 6.396765 8.535207)
-      (xy 6.345695 8.534593)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c35fa668-320e-4ad8-913c-c7fe2c50e94d))
-  (fp_poly
-    (pts
-      (xy -6.404131 -4.120533)
-      (xy -6.458523 -4.116831)
-      (xy -6.503981 -4.110793)
-      (xy -6.532835 -4.102615)
-      (xy -6.536108 -4.100613)
-      (xy -6.552141 -4.085716)
-      (xy -6.554332 -4.068816)
-      (xy -6.542819 -4.039262)
-      (xy -6.537067 -4.027075)
-      (xy -6.516177 -3.994259)
-      (xy -6.494346 -3.975206)
-      (xy -6.477832 -3.973672)
-      (xy -6.472646 -3.988406)
-      (xy -6.459263 -3.996512)
-      (xy -6.424739 -4.001889)
-      (xy -6.391236 -4.003208)
-      (xy -6.346653 -4.000775)
-      (xy -6.317082 -3.994498)
-      (xy -6.309825 -3.988406)
-      (xy -6.298127 -3.974574)
-      (xy -6.291323 -3.973489)
-      (xy -6.272462 -3.961315)
-      (xy -6.254318 -3.933533)
-      (xy -6.243391 -3.897663)
-      (xy -6.237387 -3.853651)
-      (xy -6.236512 -3.81086)
-      (xy -6.240975 -3.778652)
-      (xy -6.250618 -3.766378)
-      (xy -6.263845 -3.754431)
-      (xy -6.26542 -3.744752)
-      (xy -6.278525 -3.712584)
-      (xy -6.311442 -3.683959)
-      (xy -6.35457 -3.665793)
-      (xy -6.379225 -3.662765)
-      (xy -6.42824 -3.662765)
-      (xy -6.42824 -3.869992)
-      (xy -6.561457 -3.869992)
-      (xy -6.561457 -3.721973)
-      (xy -6.560723 -3.652949)
-      (xy -6.558035 -3.608634)
-      (xy -6.552663 -3.584159)
-      (xy -6.543875 -3.574655)
-      (xy -6.539254 -3.573954)
-      (xy -6.519556 -3.565962)
-      (xy -6.517051 -3.559152)
-      (xy -6.503161 -3.551899)
-      (xy -6.465058 -3.546777)
-      (xy -6.408097 -3.54443)
-      (xy -6.394027 -3.544351)
-      (xy -6.32964 -3.545538)
-      (xy -6.287244 -3.550063)
-      (xy -6.259288 -3.55937)
-      (xy -6.239226 -3.573954)
-      (xy -6.210893 -3.595449)
-      (xy -6.190701 -3.603558)
-      (xy -6.167262 -3.61542)
-      (xy -6.141605 -3.643527)
-      (xy -6.122559 -3.676659)
-      (xy -6.117894 -3.69607)
-      (xy -6.110481 -3.718051)
-      (xy -6.102599 -3.721973)
-      (xy -6.09512 -3.735749)
-      (xy -6.090288 -3.773093)
-      (xy -6.088867 -3.82803)
-      (xy -6.088879 -3.829286)
-      (xy -6.092461 -3.898857)
-      (xy -6.102662 -3.947823)
-      (xy -6.118655 -3.981006)
-      (xy -6.140756 -4.018376)
-      (xy -6.155524 -4.048929)
-      (xy -6.156083 -4.050469)
-      (xy -6.175773 -4.07154)
-      (xy -6.207718 -4.084949)
-      (xy -6.238145 -4.095676)
-      (xy -6.250618 -4.107997)
-      (xy -6.264047 -4.115629)
-      (xy -6.299223 -4.12013)
-      (xy -6.348474 -4.121698)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0fc51499-15f5-4fa1-8bc1-fbda6567f4b5))
-  (fp_poly
-    (pts
-      (xy -5.655646 -10.559424)
-      (xy -5.688681 -10.554916)
-      (xy -5.70291 -10.546194)
-      (xy -5.702949 -10.545633)
-      (xy -5.715945 -10.535782)
-      (xy -5.747834 -10.530935)
-      (xy -5.753882 -10.530831)
-      (xy -5.790751 -10.526909)
-      (xy -5.812958 -10.517335)
-      (xy -5.813963 -10.516029)
-      (xy -5.834732 -10.503821)
-      (xy -5.853425 -10.501227)
-      (xy -5.875056 -10.495498)
-      (xy -5.87324 -10.475324)
-      (xy -5.860309 -10.441926)
-      (xy -5.847938 -10.408523)
-      (xy -5.833136 -10.367626)
-      (xy -5.558938 -10.3869)
-      (xy -5.509731 -10.339875)
-      (xy -5.48058 -10.308005)
-      (xy -5.464449 -10.275701)
-      (xy -5.456383 -10.230945)
-      (xy -5.45418 -10.205154)
-      (xy -5.451789 -10.134698)
-      (xy -5.45822 -10.083669)
-      (xy -5.475802 -10.042608)
-      (xy -5.503157 -10.006279)
-      (xy -5.529985 -9.980498)
-      (xy -5.560619 -9.965949)
-      (xy -5.605879 -9.958358)
-      (xy -5.629355 -9.956394)
-      (xy -5.717751 -9.95)
-      (xy -5.717751 -10.20519)
-      (xy -5.880571 -10.20519)
-      (xy -5.880571 -10.020166)
-      (xy -5.880302 -9.943381)
-      (xy -5.87898 -9.89139)
-      (xy -5.875836 -9.859382)
-      (xy -5.870102 -9.84255)
-      (xy -5.861006 -9.836084)
-      (xy -5.850967 -9.835143)
-      (xy -5.826915 -9.828944)
-      (xy -5.821364 -9.820341)
-      (xy -5.807214 -9.813651)
-      (xy -5.767305 -9.808759)
-      (xy -5.705445 -9.806012)
-      (xy -5.659417 -9.805539)
-      (xy -5.590342 -9.806832)
-      (xy -5.534901 -9.810373)
-      (xy -5.498934 -9.815657)
-      (xy -5.488322 -9.820341)
-      (xy -5.467158 -9.833473)
-      (xy -5.454144 -9.835379)
-      (xy -5.422245 -9.847205)
-      (xy -5.382356 -9.877756)
-      (xy -5.341705 -9.920363)
-      (xy -5.307522 -9.96836)
-      (xy -5.304732 -9.973208)
-      (xy -5.289161 -10.006669)
-      (xy -5.279682 -10.044729)
-      (xy -5.274969 -10.095702)
-      (xy -5.273695 -10.167762)
-      (xy -5.275176 -10.229456)
-      (xy -5.279156 -10.279175)
-      (xy -5.28494 -10.309954)
-      (xy -5.288497 -10.316204)
-      (xy -5.30157 -10.337358)
-      (xy -5.303427 -10.350381)
-      (xy -5.314967 -10.379849)
-      (xy -5.344667 -10.417865)
-      (xy -5.385502 -10.457423)
-      (xy -5.430443 -10.491515)
-      (xy -5.46292 -10.509416)
-      (xy -5.505101 -10.528329)
-      (xy -5.539028 -10.544511)
-      (xy -5.543628 -10.546877)
-      (xy -5.573126 -10.555482)
-      (xy -5.613796 -10.559639)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 7d21d4af-961f-4781-b2e7-b72a2f9fa540))
-  (fp_poly
-    (pts
-      (xy -3.147579 10.274613)
-      (xy -3.276012 10.315248)
-      (xy -3.391433 10.380464)
-      (xy -3.490967 10.468202)
-      (xy -3.571737 10.576403)
-      (xy -3.630869 10.703007)
-      (xy -3.632218 10.706891)
-      (xy -3.650687 10.786629)
-      (xy -3.659291 10.881851)
-      (xy -3.657833 10.980065)
-      (xy -3.646118 11.068773)
-      (xy -3.63837 11.099281)
-      (xy -3.585837 11.224683)
-      (xy -3.511266 11.333672)
-      (xy -3.418178 11.424284)
-      (xy -3.310092 11.494552)
-      (xy -3.190532 11.542514)
-      (xy -3.063017 11.566204)
-      (xy -2.931068 11.563658)
-      (xy -2.838788 11.545442)
-      (xy -2.713278 11.496463)
-      (xy -2.602441 11.424134)
-      (xy -2.508987 11.331986)
-      (xy -2.435623 11.223549)
-      (xy -2.385059 11.102352)
-      (xy -2.360002 10.971927)
-      (xy -2.357727 10.918439)
-      (xy -2.357864 10.917071)
-      (xy -2.483543 10.917071)
-      (xy -2.484748 10.989139)
-      (xy -2.489432 11.041155)
-      (xy -2.499203 11.08261)
-      (xy -2.515666 11.122997)
-      (xy -2.519863 11.131698)
-      (xy -2.586345 11.236828)
-      (xy -2.671193 11.323048)
-      (xy -2.770265 11.388442)
-      (xy -2.879414 11.431092)
-      (xy -2.994498 11.449083)
-      (xy -3.111371 11.440498)
-      (xy -3.160958 11.428214)
-      (xy -3.239079 11.395471)
-      (xy -3.319554 11.346761)
-      (xy -3.390808 11.289838)
-      (xy -3.43 11.247999)
-      (xy -3.489493 11.151173)
-      (xy -3.528712 11.041234)
-      (xy -3.545998 10.926166)
-      (xy -3.539694 10.813956)
-      (xy -3.529456 10.769053)
-      (xy -3.495474 10.688027)
-      (xy -3.442291 10.604403)
-      (xy -3.377305 10.528586)
-      (xy -3.32725 10.48459)
-      (xy -3.227781 10.423739)
-      (xy -3.122668 10.389166)
-      (xy -3.004718 10.378544)
-      (xy -2.999665 10.378584)
-      (xy -2.884283 10.394143)
-      (xy -2.774191 10.436008)
-      (xy -2.6744 10.500883)
-      (xy -2.589921 10.585469)
-      (xy -2.525764 10.686472)
-      (xy -2.523067 10.692135)
-      (xy -2.503599 10.737833)
-      (xy -2.491717 10.779882)
-      (xy -2.48565 10.828361)
-      (xy -2.483627 10.893348)
-      (xy -2.483543 10.917071)
-      (xy -2.357864 10.917071)
-      (xy -2.37144 10.781075)
-      (xy -2.410816 10.654142)
-      (xy -2.473208 10.540311)
-      (xy -2.555972 10.442255)
-      (xy -2.656461 10.362645)
-      (xy -2.77203 10.304154)
-      (xy -2.900035 10.269454)
-      (xy -3.009009 10.260619)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 3b7d4004-a1ce-48aa-afee-404d4e2b01a2))
-  (fp_poly
-    (pts
-      (xy 5.481171 -0.389249)
-      (xy 5.422918 -0.385282)
-      (xy 5.385516 -0.378655)
-      (xy 5.360211 -0.366432)
-      (xy 5.338252 -0.345678)
-      (xy 5.332857 -0.33951)
-      (xy 5.305512 -0.289858)
-      (xy 5.293163 -0.228851)
-      (xy 5.296146 -0.167254)
-      (xy 5.314797 -0.115832)
-      (xy 5.325445 -0.101848)
-      (xy 5.356053 -0.069267)
-      (xy 5.318044 -0.031258)
-      (xy 5.292255 0.003802)
-      (xy 5.280162 0.0385)
-      (xy 5.280035 0.041469)
-      (xy 5.272866 0.076458)
-      (xy 5.262273 0.093948)
-      (xy 5.252132 0.11409)
-      (xy 5.262273 0.129472)
-      (xy 5.275754 0.156952)
-      (xy 5.280035 0.187146)
-      (xy 5.292789 0.22685)
-      (xy 5.325229 0.267043)
-      (xy 5.368617 0.299928)
-      (xy 5.41422 0.31771)
-      (xy 5.427695 0.318936)
-      (xy 5.461686 0.323552)
-      (xy 5.47986 0.333738)
-      (xy 5.499298 0.34326)
-      (xy 5.536013 0.3483)
-      (xy 5.546468 0.34854)
-      (xy 5.585588 0.345049)
-      (xy 5.610503 0.336393)
-      (xy 5.613077 0.333738)
-      (xy 5.63262 0.323957)
-      (xy 5.669003 0.318892)
-      (xy 5.676858 0.31871)
-      (xy 5.728669 0.314797)
-      (xy 5.756048 0.300173)
-      (xy 5.763641 0.269695)
-      (xy 5.758224 0.228581)
-      (xy 5.742998 0.185009)
-      (xy 5.720965 0.159121)
-      (xy 5.697268 0.154803)
-      (xy 5.680398 0.169765)
-      (xy 5.65916 0.180684)
-      (xy 5.618711 0.186603)
-      (xy 5.568999 0.187636)
-      (xy 5.519973 0.183899)
-      (xy 5.481579 0.175504)
-      (xy 5.466742 0.167315)
-      (xy 5.447007 0.135971)
-      (xy 5.439258 0.099885)
-      (xy 5.44364 0.068939)
-      (xy 5.460298 0.053015)
-      (xy 5.465058 0.052503)
-      (xy 5.484756 0.04451)
-      (xy 5.487261 0.037701)
-      (xy 5.500644 0.029595)
-      (xy 5.535167 0.024218)
-      (xy 5.568671 0.022899)
-      (xy 5.650081 0.022899)
-      (xy 5.650081 -0.123642)
-      (xy 5.564971 -0.128082)
-      (xy 5.47986 -0.132521)
-      (xy 5.47986 -0.250936)
-      (xy 5.55757 -0.25541)
-      (xy 5.605402 -0.25541)
-      (xy 5.631761 -0.249357)
-      (xy 5.63528 -0.244308)
-      (xy 5.644581 -0.228202)
-      (xy 5.666788 -0.229408)
-      (xy 5.693355 -0.244835)
-      (xy 5.715734 -0.271395)
-      (xy 5.717072 -0.273878)
-      (xy 5.73267 -0.317815)
-      (xy 5.727059 -0.350788)
-      (xy 5.698693 -0.373554)
-      (xy 5.646024 -0.38687)
-      (xy 5.567504 -0.391493)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d7499ab9-53bc-476c-bc20-6f47bc74f1b6))
-  (fp_poly
-    (pts
-      (xy -6.88169 0.943712)
-      (xy -6.919342 0.954972)
-      (xy -6.946305 0.974097)
-      (xy -6.996573 1.033024)
-      (xy -7.01915 1.093027)
-      (xy -7.020315 1.109762)
-      (xy -7.025743 1.141182)
-      (xy -7.035117 1.155242)
-      (xy -7.044578 1.174649)
-      (xy -7.049648 1.211462)
-      (xy -7.049919 1.222724)
-      (xy -7.04659 1.259475)
-      (xy -7.038288 1.2797)
-      (xy -7.035117 1.281057)
-      (xy -7.025734 1.294163)
-      (xy -7.020627 1.326791)
-      (xy -7.020315 1.338523)
-      (xy -7.016301 1.37707)
-      (xy -7.000606 1.410163)
-      (xy -6.967751 1.448448)
-      (xy -6.959366 1.456938)
-      (xy -6.921228 1.492286)
-      (xy -6.890266 1.510543)
-      (xy -6.854502 1.517191)
-      (xy -6.826149 1.517887)
-      (xy -6.784506 1.515164)
-      (xy -6.758388 1.508218)
-      (xy -6.753881 1.503085)
-      (xy -6.741496 1.491021)
-      (xy -6.72456 1.488284)
-      (xy -6.696997 1.475024)
-      (xy -6.68595 1.451279)
-      (xy -6.674522 1.42357)
-      (xy -6.663465 1.414274)
-      (xy -6.654126 1.401425)
-      (xy -6.650268 1.370742)
-      (xy -6.645705 1.336559)
-      (xy -6.635466 1.318062)
-      (xy -6.627795 1.299553)
-      (xy -6.622446 1.260339)
-      (xy -6.621239 1.229251)
-      (xy -6.769087 1.229251)
-      (xy -6.770617 1.304224)
-      (xy -6.776136 1.354203)
-      (xy -6.78704 1.383682)
-      (xy -6.804724 1.397156)
-      (xy -6.821934 1.399472)
-      (xy -6.852608 1.389401)
-      (xy -6.866218 1.362468)
-      (xy -6.877646 1.334758)
-      (xy -6.888703 1.325463)
-      (xy -6.895997 1.312278)
-      (xy -6.900282 1.278865)
-      (xy -6.901631 1.234441)
-      (xy -6.900118 1.18822)
-      (xy -6.895817 1.149419)
-      (xy -6.888802 1.127253)
-      (xy -6.887098 1.125638)
-      (xy -6.874663 1.10476)
-      (xy -6.872296 1.08776)
-      (xy -6.864548 1.066292)
-      (xy -6.836666 1.059155)
-      (xy -6.829617 1.059029)
-      (xy -6.803271 1.062772)
-      (xy -6.785736 1.077168)
-      (xy -6.77532 1.10697)
-      (xy -6.770335 1.156933)
-      (xy -6.769087 1.229251)
-      (xy -6.621239 1.229251)
-      (xy -6.620664 1.214449)
-      (xy -6.622822 1.164159)
-      (xy -6.628448 1.126541)
-      (xy -6.635466 1.110836)
-      (xy -6.647271 1.090263)
-      (xy -6.650268 1.068367)
-      (xy -6.660245 1.037533)
-      (xy -6.685245 1.000266)
-      (xy -6.69643 0.98783)
-      (xy -6.727146 0.960052)
-      (xy -6.756867 0.945936)
-      (xy -6.797818 0.941027)
-      (xy -6.825946 0.940633)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 10b7088f-1410-401a-8bf1-1d655fa47975))
-  (fp_poly
-    (pts
-      (xy -1.690621 10.726761)
-      (xy -1.715033 10.734145)
-      (xy -1.721247 10.74685)
-      (xy -1.728234 10.766562)
-      (xy -1.734157 10.769053)
-      (xy -1.744282 10.782136)
-      (xy -1.754034 10.814875)
-      (xy -1.756638 10.828907)
-      (xy -1.766403 10.874941)
-      (xy -1.778334 10.912429)
-      (xy -1.780733 10.917718)
-      (xy -1.800184 10.956447)
-      (xy -1.810058 10.976078)
-      (xy -1.822283 11.010647)
-      (xy -1.82486 11.02897)
-      (xy -1.833375 11.046905)
-      (xy -1.852308 11.046751)
-      (xy -1.871743 11.031937)
-      (xy -1.881397 11.009432)
-      (xy -1.889979 10.983484)
-      (xy -1.898992 10.976279)
-      (xy -1.908626 10.963105)
-      (xy -1.918232 10.929757)
-      (xy -1.921846 10.90967)
-      (xy -1.930387 10.87002)
-      (xy -1.940533 10.846175)
-      (xy -1.944956 10.843062)
-      (xy -1.955383 10.830493)
-      (xy -1.958548 10.809758)
-      (xy -1.970167 10.76226)
-      (xy -2.003826 10.734066)
-      (xy -2.060159 10.724648)
-      (xy -2.060922 10.724647)
-      (xy -2.1235 10.724647)
-      (xy -2.113051 10.787555)
-      (xy -2.103873 10.827206)
-      (xy -2.09324 10.85203)
-      (xy -2.089547 10.855397)
-      (xy -2.078536 10.87233)
-      (xy -2.076492 10.887828)
-      (xy -2.069404 10.915648)
-      (xy -2.06169 10.924472)
-      (xy -2.048637 10.945624)
-      (xy -2.046797 10.95865)
-      (xy -2.04011 10.989166)
-      (xy -2.024594 11.026077)
-      (xy -2.008936 11.062582)
-      (xy -2.002483 11.0904)
-      (xy -1.99435 11.117093)
-      (xy -1.9747 11.151334)
-      (xy -1.973863 11.152519)
-      (xy -1.949997 11.194096)
-      (xy -1.935254 11.232514)
-      (xy -1.926112 11.256947)
-      (xy -1.908867 11.26851)
-      (xy -1.874405 11.271747)
-      (xy -1.85656 11.271753)
-      (xy -1.807795 11.266783)
-      (xy -1.774442 11.254536)
-      (xy -1.769353 11.250175)
-      (xy -1.753419 11.222212)
-      (xy -1.750851 11.209162)
-      (xy -1.742465 11.18232)
-      (xy -1.729119 11.160431)
-      (xy -1.711385 11.12354)
-      (xy -1.706916 11.098394)
-      (xy -1.700967 11.072388)
-      (xy -1.691643 11.06509)
-      (xy -1.678747 11.053004)
-      (xy -1.676842 11.041424)
-      (xy -1.670427 11.011272)
-      (xy -1.653667 10.964787)
-      (xy -1.630293 10.911681)
-      (xy -1.61639 10.883968)
-      (xy -1.604704 10.850733)
-      (xy -1.602832 10.835862)
-      (xy -1.595788 10.816023)
-      (xy -1.58971 10.813458)
-      (xy -1.578612 10.800602)
-      (xy -1.570156 10.769625)
-      (xy -1.570071 10.769053)
-      (xy -1.563554 10.724647)
-      (xy -1.642401 10.724647)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b06b59c3-4ff0-424d-8191-5d8ebd912275))
-  (fp_poly
-    (pts
-      (xy -1.049054 2.67619)
-      (xy -1.124855 2.682946)
-      (xy -1.174281 2.693822)
-      (xy -1.200531 2.711585)
-      (xy -1.206803 2.739002)
-      (xy -1.196295 2.77884)
-      (xy -1.188855 2.79714)
-      (xy -1.164457 2.844636)
-      (xy -1.143674 2.863749)
-      (xy -1.125432 2.855326)
-      (xy -1.121772 2.850055)
-      (xy -1.101317 2.838492)
-      (xy -1.077366 2.835253)
-      (xy -1.046371 2.829666)
-      (xy -1.03296 2.820451)
-      (xy -1.012951 2.809787)
-      (xy -0.98028 2.805649)
-      (xy -0.949481 2.810016)
-      (xy -0.936748 2.820451)
-      (xy -0.924847 2.833782)
-      (xy -0.915745 2.835253)
-      (xy -0.889147 2.842246)
-      (xy -0.853003 2.859229)
-      (xy -0.85033 2.860742)
-      (xy -0.820114 2.884895)
-      (xy -0.801187 2.919563)
-      (xy -0.791431 2.971021)
-      (xy -0.78873 3.043366)
-      (xy -0.796491 3.127976)
-      (xy -0.820851 3.188899)
-      (xy -0.863422 3.227981)
-      (xy -0.925817 3.247065)
-      (xy -0.969143 3.249705)
-      (xy -1.055163 3.249705)
-      (xy -1.055163 3.012876)
-      (xy -1.217984 3.012876)
-      (xy -1.217984 3.188914)
-      (xy -1.21754 3.267722)
-      (xy -1.214749 3.321646)
-      (xy -1.20742 3.355407)
-      (xy -1.193364 3.373724)
-      (xy -1.17039 3.381318)
-      (xy -1.136307 3.382909)
-      (xy -1.127962 3.382922)
-      (xy -1.097311 3.38732)
-      (xy -1.084767 3.397724)
-      (xy -1.071451 3.404845)
-      (xy -1.037274 3.409656)
-      (xy -0.990898 3.412084)
-      (xy -0.940979 3.412057)
-      (xy -0.896178 3.409502)
-      (xy -0.865154 3.404346)
-      (xy -0.85652 3.399636)
-      (xy -0.837696 3.388024)
-      (xy -0.803121 3.377666)
-      (xy -0.80147 3.377329)
-      (xy -0.767787 3.362246)
-      (xy -0.727301 3.332864)
-      (xy -0.687625 3.296338)
-      (xy -0.656373 3.259821)
-      (xy -0.64116 3.23047)
-      (xy -0.640711 3.226273)
-      (xy -0.628965 3.204995)
-      (xy -0.622772 3.201787)
-      (xy -0.613831 3.18726)
-      (xy -0.608226 3.149234)
-      (xy -0.605706 3.085349)
-      (xy -0.605538 3.039724)
-      (xy -0.606481 2.968233)
-      (xy -0.609287 2.91979)
-      (xy -0.615083 2.887847)
-      (xy -0.624994 2.865857)
-      (xy -0.638279 2.849255)
-      (xy -0.660873 2.819474)
-      (xy -0.670315 2.796035)
-      (xy -0.670315 2.795978)
-      (xy -0.682039 2.775182)
-      (xy -0.702687 2.759763)
-      (xy -0.739841 2.735343)
-      (xy -0.76406 2.715418)
-      (xy -0.810284 2.690585)
-      (xy -0.883937 2.676595)
-      (xy -0.984893 2.673464)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e347eaed-df51-4f54-8270-ba866af187f4))
-  (fp_poly
-    (pts
-      (xy -5.620149 -5.473573)
-      (xy -5.692724 -5.470826)
-      (xy -5.744253 -5.465541)
-      (xy -5.771125 -5.458154)
-      (xy -5.774065 -5.455071)
-      (xy -5.79145 -5.440372)
-      (xy -5.800394 -5.438989)
-      (xy -5.816402 -5.434547)
-      (xy -5.819648 -5.417641)
-      (xy -5.809961 -5.382902)
-      (xy -5.797554 -5.350478)
-      (xy -5.777188 -5.310386)
-      (xy -5.754795 -5.293102)
-      (xy -5.73922 -5.290971)
-      (xy -5.708517 -5.296672)
-      (xy -5.695548 -5.305772)
-      (xy -5.676859 -5.313801)
-      (xy -5.638058 -5.319177)
-      (xy -5.601128 -5.320574)
-      (xy -5.547597 -5.318218)
-      (xy -5.511092 -5.308526)
-      (xy -5.47923 -5.287568)
-      (xy -5.468785 -5.278549)
-      (xy -5.439576 -5.248739)
-      (xy -5.423078 -5.224662)
-      (xy -5.421713 -5.219341)
-      (xy -5.41176 -5.203112)
-      (xy -5.406912 -5.202159)
-      (xy -5.399177 -5.188565)
-      (xy -5.393881 -5.152554)
-      (xy -5.39211 -5.105947)
-      (xy -5.394201 -5.055671)
-      (xy -5.399741 -5.021249)
-      (xy -5.406912 -5.009735)
-      (xy -5.420043 -4.997746)
-      (xy -5.421713 -4.987532)
-      (xy -5.433275 -4.958184)
-      (xy -5.46033 -4.928001)
-      (xy -5.491434 -4.908427)
-      (xy -5.503124 -4.906122)
-      (xy -5.522822 -4.898129)
-      (xy -5.525326 -4.89132)
-      (xy -5.538556 -4.882493)
-      (xy -5.572029 -4.877198)
-      (xy -5.591935 -4.876518)
-      (xy -5.658543 -4.876518)
-      (xy -5.658543 -5.12815)
-      (xy -5.821364 -5.12815)
-      (xy -5.821364 -4.761804)
-      (xy -5.775108 -4.752553)
-      (xy -5.734443 -4.747773)
-      (xy -5.676252 -4.745064)
-      (xy -5.608438 -4.744307)
-      (xy -5.538901 -4.745383)
-      (xy -5.475541 -4.748174)
-      (xy -5.426259 -4.752563)
-      (xy -5.399511 -4.758176)
-      (xy -5.339722 -4.797233)
-      (xy -5.287451 -4.854475)
-      (xy -5.248869 -4.920999)
-      (xy -5.230144 -4.987906)
-      (xy -5.229289 -5.003735)
-      (xy -5.22519 -5.039794)
-      (xy -5.215248 -5.061007)
-      (xy -5.214487 -5.061542)
-      (xy -5.203823 -5.081551)
-      (xy -5.199685 -5.114222)
-      (xy -5.204052 -5.145021)
-      (xy -5.214487 -5.157754)
-      (xy -5.224271 -5.170766)
-      (xy -5.229161 -5.202761)
-      (xy -5.229289 -5.20956)
-      (xy -5.233007 -5.243803)
-      (xy -5.242148 -5.260919)
-      (xy -5.244091 -5.261367)
-      (xy -5.256368 -5.273681)
-      (xy -5.258893 -5.289158)
-      (xy -5.269643 -5.321862)
-      (xy -5.281096 -5.335376)
-      (xy -5.299821 -5.358934)
-      (xy -5.303298 -5.371068)
-      (xy -5.315478 -5.386331)
-      (xy -5.347262 -5.409122)
-      (xy -5.387447 -5.432163)
-      (xy -5.428621 -5.452425)
-      (xy -5.463709 -5.465098)
-      (xy -5.501681 -5.471777)
-      (xy -5.551507 -5.474059)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e3d4d17c-0832-405d-bad8-78ceb16917d8))
-  (fp_poly
-    (pts
-      (xy 5.792417 6.005636)
-      (xy 5.759147 6.015943)
-      (xy 5.736928 6.034721)
-      (xy 5.71651 6.064799)
-      (xy 5.709289 6.086527)
-      (xy 5.700517 6.104726)
-      (xy 5.694487 6.106465)
-      (xy 5.682342 6.118824)
-      (xy 5.679685 6.135196)
-      (xy 5.672888 6.163531)
-      (xy 5.664883 6.173074)
-      (xy 5.656925 6.192108)
-      (xy 5.652091 6.231225)
-      (xy 5.650431 6.281063)
-      (xy 5.651998 6.332261)
-      (xy 5.656844 6.375456)
-      (xy 5.663639 6.399003)
-      (xy 5.678356 6.429278)
-      (xy 5.69726 6.470969)
-      (xy 5.700879 6.479246)
-      (xy 5.733287 6.527797)
-      (xy 5.771006 6.556956)
-      (xy 5.807292 6.569361)
-      (xy 5.851988 6.577234)
-      (xy 5.896035 6.580054)
-      (xy 5.930372 6.577296)
-      (xy 5.945941 6.56844)
-      (xy 5.946119 6.56705)
-      (xy 5.958472 6.553353)
-      (xy 5.976821 6.545945)
-      (xy 6.005457 6.526163)
-      (xy 6.015552 6.507214)
-      (xy 6.02724 6.482639)
-      (xy 6.036656 6.476512)
-      (xy 6.0453 6.463495)
-      (xy 6.049619 6.431488)
-      (xy 6.049732 6.424705)
-      (xy 6.05345 6.390463)
-      (xy 6.062591 6.373346)
-      (xy 6.064534 6.372899)
-      (xy 6.072677 6.359524)
-      (xy 6.078054 6.325054)
-      (xy 6.079336 6.292362)
-      (xy 6.078415 6.275408)
-      (xy 5.931988 6.275408)
-      (xy 5.929069 6.327578)
-      (xy 5.922615 6.37647)
-      (xy 5.912929 6.413957)
-      (xy 5.907412 6.425226)
-      (xy 5.882241 6.450413)
-      (xy 5.854611 6.461069)
-      (xy 5.833619 6.455564)
-      (xy 5.827704 6.439507)
-      (xy 5.819711 6.419809)
-      (xy 5.812902 6.417305)
-      (xy 5.805572 6.403456)
-      (xy 5.800421 6.365646)
-      (xy 5.798149 6.309483)
-      (xy 5.7981 6.29889)
-      (xy 5.799831 6.240248)
-      (xy 5.804557 6.199039)
-      (xy 5.811578 6.180869)
-      (xy 5.812902 6.180475)
-      (xy 5.824928 6.168077)
-      (xy 5.827704 6.150871)
-      (xy 5.836377 6.127657)
-      (xy 5.864708 6.121267)
-      (xy 5.893726 6.128205)
-      (xy 5.901713 6.150871)
-      (xy 5.907912 6.174923)
-      (xy 5.916515 6.180475)
-      (xy 5.926013 6.193731)
-      (xy 5.93107 6.228084)
-      (xy 5.931988 6.275408)
-      (xy 6.078415 6.275408)
-      (xy 6.076817 6.246006)
-      (xy 6.070342 6.212765)
-      (xy 6.064534 6.202677)
-      (xy 6.053869 6.182668)
-      (xy 6.049732 6.149997)
-      (xy 6.045836 6.119192)
-      (xy 6.036535 6.106465)
-      (xy 6.023062 6.094028)
-      (xy 6.014752 6.073161)
-      (xy 5.990799 6.037736)
-      (xy 5.941648 6.014172)
-      (xy 5.869626 6.003431)
-      (xy 5.844991 6.002852)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 1a43bfcc-f35c-499e-882f-58f29327b311))
-  (fp_poly
-    (pts
-      (xy -5.650525 -2.944185)
-      (xy -5.700893 -2.939908)
-      (xy -5.734402 -2.932622)
-      (xy -5.743903 -2.925627)
-      (xy -5.761686 -2.910788)
-      (xy -5.778192 -2.90787)
-      (xy -5.796707 -2.907203)
-      (xy -5.804047 -2.900864)
-      (xy -5.800154 -2.882347)
-      (xy -5.78497 -2.845145)
-      (xy -5.777484 -2.827687)
-      (xy -5.752972 -2.781645)
-      (xy -5.728983 -2.76147)
-      (xy -5.71915 -2.759852)
-      (xy -5.690596 -2.766532)
-      (xy -5.680746 -2.774654)
-      (xy -5.662884 -2.782451)
-      (xy -5.627086 -2.787317)
-      (xy -5.582913 -2.78917)
-      (xy -5.539926 -2.787926)
-      (xy -5.507687 -2.783503)
-      (xy -5.495723 -2.776258)
-      (xy -5.483178 -2.763228)
-      (xy -5.458718 -2.753773)
-      (xy -5.428438 -2.735994)
-      (xy -5.421713 -2.716398)
-      (xy -5.414496 -2.690464)
-      (xy -5.405868 -2.683027)
-      (xy -5.397803 -2.666618)
-      (xy -5.392685 -2.62975)
-      (xy -5.390501 -2.581421)
-      (xy -5.391237 -2.530626)
-      (xy -5.394879 -2.486364)
-      (xy -5.401415 -2.457629)
-      (xy -5.406217 -2.451711)
-      (xy -5.420825 -2.434524)
-      (xy -5.421713 -2.428077)
-      (xy -5.433495 -2.40829)
-      (xy -5.458718 -2.389805)
-      (xy -5.485594 -2.371554)
-      (xy -5.495723 -2.3577)
-      (xy -5.508957 -2.350363)
-      (xy -5.54244 -2.345963)
-      (xy -5.562331 -2.345399)
-      (xy -5.62894 -2.345399)
-      (xy -5.62894 -2.597031)
-      (xy -5.821364 -2.597031)
-      (xy -5.821364 -2.230685)
-      (xy -5.775108 -2.221434)
-      (xy -5.740431 -2.217499)
-      (xy -5.68522 -2.214516)
-      (xy -5.618538 -2.21289)
-      (xy -5.578983 -2.212723)
-      (xy -5.500316 -2.214459)
-      (xy -5.443033 -2.219765)
-      (xy -5.399013 -2.229788)
-      (xy -5.366206 -2.242757)
-      (xy -5.329052 -2.262821)
-      (xy -5.306469 -2.280117)
-      (xy -5.303298 -2.28586)
-      (xy -5.294062 -2.304796)
-      (xy -5.271332 -2.333834)
-      (xy -5.266294 -2.339397)
-      (xy -5.23903 -2.381556)
-      (xy -5.229289 -2.42157)
-      (xy -5.2248 -2.451802)
-      (xy -5.214487 -2.463814)
-      (xy -5.207013 -2.47758)
-      (xy -5.201809 -2.514801)
-      (xy -5.199696 -2.569367)
-      (xy -5.199685 -2.573955)
-      (xy -5.201544 -2.628372)
-      (xy -5.206451 -2.670508)
-      (xy -5.213402 -2.692277)
-      (xy -5.214487 -2.693243)
-      (xy -5.226922 -2.714121)
-      (xy -5.229289 -2.731122)
-      (xy -5.234973 -2.754706)
-      (xy -5.242486 -2.759852)
-      (xy -5.255458 -2.772411)
-      (xy -5.26513 -2.79749)
-      (xy -5.281131 -2.829562)
-      (xy -5.299384 -2.844648)
-      (xy -5.343135 -2.870553)
-      (xy -5.39981 -2.918869)
-      (xy -5.403807 -2.922672)
-      (xy -5.427894 -2.932481)
-      (xy -5.471981 -2.9396)
-      (xy -5.528697 -2.943967)
-      (xy -5.590668 -2.945516)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 83ce798a-243a-448c-979f-54c182e1bd36))
-  (fp_poly
-    (pts
-      (xy 5.420402 7.205388)
-      (xy 5.377656 7.212104)
-      (xy 5.352036 7.220728)
-      (xy 5.293466 7.25515)
-      (xy 5.260409 7.281687)
-      (xy 5.250431 7.301576)
-      (xy 5.241141 7.31887)
-      (xy 5.235629 7.320218)
-      (xy 5.225157 7.33306)
-      (xy 5.220827 7.36375)
-      (xy 5.216265 7.397934)
-      (xy 5.206026 7.41643)
-      (xy 5.199567 7.434359)
-      (xy 5.194545 7.474917)
-      (xy 5.191654 7.531137)
-      (xy 5.191224 7.564872)
-      (xy 5.192593 7.637954)
-      (xy 5.197531 7.689594)
-      (xy 5.207282 7.727861)
-      (xy 5.220827 7.756873)
-      (xy 5.239575 7.793518)
-      (xy 5.249797 7.819851)
-      (xy 5.250431 7.823932)
-      (xy 5.261902 7.846487)
-      (xy 5.290939 7.875926)
-      (xy 5.329484 7.904313)
-      (xy 5.336145 7.908314)
-      (xy 5.382078 7.924843)
-      (xy 5.442801 7.934019)
-      (xy 5.504023 7.934013)
-      (xy 5.520565 7.931911)
-      (xy 5.550096 7.922658)
-      (xy 5.56127 7.91131)
-      (xy 5.573344 7.899205)
-      (xy 5.58453 7.897491)
-      (xy 5.61997 7.883693)
-      (xy 5.647811 7.846183)
-      (xy 5.65646 7.822791)
-      (xy 5.679596 7.756596)
-      (xy 5.710619 7.687546)
-      (xy 5.711016 7.686765)
-      (xy 5.718293 7.658115)
-      (xy 5.722517 7.612884)
-      (xy 5.723753 7.5601)
-      (xy 5.723391 7.549078)
-      (xy 5.539778 7.549078)
-      (xy 5.539561 7.617944)
-      (xy 5.535433 7.680393)
-      (xy 5.527397 7.728511)
-      (xy 5.516865 7.75298)
-      (xy 5.479703 7.775036)
-      (xy 5.435888 7.774363)
-      (xy 5.401093 7.75423)
-      (xy 5.390018 7.738086)
-      (xy 5.382694 7.712358)
-      (xy 5.37843 7.671564)
-      (xy 5.376535 7.610221)
-      (xy 5.376247 7.557048)
-      (xy 5.376978 7.4795)
-      (xy 5.379631 7.426047)
-      (xy 5.384898 7.391205)
-      (xy 5.393469 7.369492)
-      (xy 5.401093 7.359866)
-      (xy 5.440677 7.336081)
-      (xy 5.479194 7.340385)
-      (xy 5.510927 7.371629)
-      (xy 5.516952 7.383126)
-      (xy 5.528476 7.423755)
-      (xy 5.536084 7.48171)
-      (xy 5.539778 7.549078)
-      (xy 5.723391 7.549078)
-      (xy 5.722066 7.508795)
-      (xy 5.71752 7.467999)
-      (xy 5.71018 7.446741)
-      (xy 5.709289 7.446034)
-      (xy 5.698625 7.426024)
-      (xy 5.694487 7.393354)
-      (xy 5.69012 7.362555)
-      (xy 5.679685 7.349822)
-      (xy 5.667298 7.337546)
-      (xy 5.664883 7.322798)
-      (xy 5.654063 7.293867)
-      (xy 5.6284 7.261938)
-      (xy 5.598088 7.237837)
-      (xy 5.578819 7.231407)
-      (xy 5.562317 7.221629)
-      (xy 5.56127 7.216605)
-      (xy 5.548087 7.207743)
-      (xy 5.514376 7.203035)
-      (xy 5.468895 7.202307)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9c56ce08-da97-41d6-bb14-021ed7172db1))
-  (fp_poly
-    (pts
-      (xy -5.618687 -8.02621)
-      (xy -5.646456 -8.018401)
-      (xy -5.651142 -8.014514)
-      (xy -5.67055 -8.005052)
-      (xy -5.707363 -7.999982)
-      (xy -5.718624 -7.999712)
-      (xy -5.755376 -7.996383)
-      (xy -5.775601 -7.988081)
-      (xy -5.776958 -7.98491)
-      (xy -5.788947 -7.971778)
-      (xy -5.799161 -7.970108)
-      (xy -5.816694 -7.9647)
-      (xy -5.819399 -7.945162)
-      (xy -5.807337 -7.90652)
-      (xy -5.800187 -7.888871)
-      (xy -5.77901 -7.838188)
-      (xy -5.655869 -7.846458)
-      (xy -5.567348 -7.848322)
-      (xy -5.502751 -7.840709)
-      (xy -5.463588 -7.823961)
-      (xy -5.451317 -7.800253)
-      (xy -5.443438 -7.780321)
-      (xy -5.436515 -7.777684)
-      (xy -5.423383 -7.765695)
-      (xy -5.421713 -7.755481)
-      (xy -5.413721 -7.735783)
-      (xy -5.406912 -7.733278)
-      (xy -5.399177 -7.719684)
-      (xy -5.393881 -7.683673)
-      (xy -5.39211 -7.637066)
-      (xy -5.39386 -7.588069)
-      (xy -5.398438 -7.553416)
-      (xy -5.404581 -7.540854)
-      (xy -5.418846 -7.529043)
-      (xy -5.438985 -7.499636)
-      (xy -5.444951 -7.489047)
-      (xy -5.46953 -7.455003)
-      (xy -5.494527 -7.437869)
-      (xy -5.499089 -7.437241)
-      (xy -5.52125 -7.430339)
-      (xy -5.525326 -7.422439)
-      (xy -5.538556 -7.413612)
-      (xy -5.572029 -7.408316)
-      (xy -5.591935 -7.407637)
-      (xy -5.658543 -7.407637)
-      (xy -5.658543 -7.674071)
-      (xy -5.821364 -7.674071)
-      (xy -5.821248 -7.492748)
-      (xy -5.821133 -7.311425)
-      (xy -5.781293 -7.292923)
-      (xy -5.750127 -7.284901)
-      (xy -5.700885 -7.279113)
-      (xy -5.641097 -7.275642)
-      (xy -5.578292 -7.274569)
-      (xy -5.52 -7.275978)
-      (xy -5.473748 -7.279951)
-      (xy -5.447067 -7.286571)
-      (xy -5.443916 -7.289222)
-      (xy -5.423275 -7.301243)
-      (xy -5.402338 -7.304261)
-      (xy -5.364869 -7.316554)
-      (xy -5.321936 -7.348323)
-      (xy -5.281386 -7.392597)
-      (xy -5.254177 -7.435815)
-      (xy -5.237543 -7.485309)
-      (xy -5.229441 -7.540474)
-      (xy -5.229289 -7.547569)
-      (xy -5.22564 -7.590026)
-      (xy -5.216549 -7.620335)
-      (xy -5.213198 -7.625034)
-      (xy -5.205111 -7.642901)
-      (xy -5.213198 -7.651071)
-      (xy -5.223561 -7.671065)
-      (xy -5.229034 -7.708127)
-      (xy -5.229289 -7.718476)
-      (xy -5.23278 -7.757596)
-      (xy -5.241436 -7.782511)
-      (xy -5.244091 -7.785085)
-      (xy -5.257331 -7.806263)
-      (xy -5.259327 -7.819263)
-      (xy -5.27161 -7.851639)
-      (xy -5.302696 -7.891616)
-      (xy -5.345311 -7.932778)
-      (xy -5.392184 -7.968707)
-      (xy -5.436043 -7.992987)
-      (xy -5.46383 -7.999712)
-      (xy -5.492753 -8.006203)
-      (xy -5.503124 -8.014514)
-      (xy -5.522322 -8.023559)
-      (xy -5.559776 -8.028794)
-      (xy -5.577133 -8.029316)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 3eb2223f-9284-4abd-8a36-412141015a03))
-  (fp_poly
-    (pts
-      (xy -5.614614 -0.416494)
-      (xy -5.640242 -0.407114)
-      (xy -5.670081 -0.396793)
-      (xy -5.71539 -0.387131)
-      (xy -5.736253 -0.384004)
-      (xy -5.777197 -0.376164)
-      (xy -5.802543 -0.36638)
-      (xy -5.806562 -0.361342)
-      (xy -5.801638 -0.341678)
-      (xy -5.789633 -0.305938)
-      (xy -5.774698 -0.265438)
-      (xy -5.760984 -0.231492)
-      (xy -5.753271 -0.216087)
-      (xy -5.738859 -0.218505)
-      (xy -5.70856 -0.231193)
-      (xy -5.701597 -0.234589)
-      (xy -5.666611 -0.246182)
-      (xy -5.620544 -0.254145)
-      (xy -5.571991 -0.258038)
-      (xy -5.529546 -0.257421)
-      (xy -5.501804 -0.251853)
-      (xy -5.495723 -0.245139)
-      (xy -5.483178 -0.232109)
-      (xy -5.458718 -0.222654)
-      (xy -5.428133 -0.204472)
-      (xy -5.421713 -0.184045)
-      (xy -5.415461 -0.160146)
-      (xy -5.406912 -0.154723)
-      (xy -5.399581 -0.140874)
-      (xy -5.39443 -0.103065)
-      (xy -5.392159 -0.046902)
-      (xy -5.39211 -0.036309)
-      (xy -5.393841 0.022333)
-      (xy -5.398567 0.063542)
-      (xy -5.405587 0.081712)
-      (xy -5.406912 0.082106)
-      (xy -5.420462 0.093902)
-      (xy -5.421713 0.101808)
-      (xy -5.433523 0.122526)
-      (xy -5.458718 0.141314)
-      (xy -5.485594 0.159565)
-      (xy -5.495723 0.173419)
-      (xy -5.508957 0.180756)
-      (xy -5.54244 0.185156)
-      (xy -5.562331 0.185719)
-      (xy -5.62894 0.185719)
-      (xy -5.62894 -0.065912)
-      (xy -5.821364 -0.065912)
-      (xy -5.821364 0.300434)
-      (xy -5.775108 0.309685)
-      (xy -5.723377 0.316216)
-      (xy -5.656829 0.319318)
-      (xy -5.583475 0.319247)
-      (xy -5.511325 0.316259)
-      (xy -5.448389 0.31061)
-      (xy -5.402677 0.302554)
-      (xy -5.388036 0.297327)
-      (xy -5.350458 0.274185)
-      (xy -5.324071 0.253012)
-      (xy -5.301609 0.234591)
-      (xy -5.29114 0.230031)
-      (xy -5.275494 0.217427)
-      (xy -5.256726 0.186786)
-      (xy -5.23991 0.148516)
-      (xy -5.230118 0.113028)
-      (xy -5.229289 0.10311)
-      (xy -5.224068 0.075872)
-      (xy -5.214487 0.067305)
-      (xy -5.206735 0.053723)
-      (xy -5.201434 0.017799)
-      (xy -5.199685 -0.028034)
-      (xy -5.201824 -0.078562)
-      (xy -5.207404 -0.116442)
-      (xy -5.214487 -0.132521)
-      (xy -5.225152 -0.152531)
-      (xy -5.229289 -0.185201)
-      (xy -5.233184 -0.216007)
-      (xy -5.242486 -0.228733)
-      (xy -5.255458 -0.241292)
-      (xy -5.26513 -0.266371)
-      (xy -5.281382 -0.298537)
-      (xy -5.300039 -0.31373)
-      (xy -5.330703 -0.331326)
-      (xy -5.353998 -0.349917)
-      (xy -5.388327 -0.370495)
-      (xy -5.432736 -0.384326)
-      (xy -5.435408 -0.384777)
-      (xy -5.47865 -0.394342)
-      (xy -5.512271 -0.406251)
-      (xy -5.514024 -0.407164)
-      (xy -5.561565 -0.419945)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 137a63c3-f4b7-4105-9b64-c9ba4a0bc830))
-  (fp_poly
-    (pts
-      (xy 5.709289 -1.472089)
-      (xy 5.768496 -1.472089)
-      (xy 5.805575 -1.469034)
-      (xy 5.826196 -1.461402)
-      (xy 5.827704 -1.458317)
-      (xy 5.840284 -1.445742)
-      (xy 5.860857 -1.439815)
-      (xy 5.889054 -1.425925)
-      (xy 5.898947 -1.409182)
-      (xy 5.897487 -1.393674)
-      (xy 5.881111 -1.385869)
-      (xy 5.843351 -1.38336)
-      (xy 5.829373 -1.383278)
-      (xy 5.770393 -1.377843)
-      (xy 5.736963 -1.361891)
-      (xy 5.735776 -1.360562)
-      (xy 5.709484 -1.329989)
-      (xy 5.698188 -1.317213)
-      (xy 5.689089 -1.294316)
-      (xy 5.682943 -1.255094)
-      (xy 5.679991 -1.208641)
-      (xy 5.680473 -1.164053)
-      (xy 5.68463 -1.130424)
-      (xy 5.692703 -1.116849)
-      (xy 5.692882 -1.116845)
-      (xy 5.705913 -1.1043)
-      (xy 5.715367 -1.07984)
-      (xy 5.73355 -1.049255)
-      (xy 5.753977 -1.042835)
-      (xy 5.777876 -1.036583)
-      (xy 5.783298 -1.028033)
-      (xy 5.796681 -1.019927)
-      (xy 5.831205 -1.014551)
-      (xy 5.864708 -1.013232)
-      (xy 5.909292 -1.015665)
-      (xy 5.938862 -1.021942)
-      (xy 5.946119 -1.028033)
-      (xy 5.958108 -1.041165)
-      (xy 5.968322 -1.042835)
-      (xy 5.997328 -1.054237)
-      (xy 6.027452 -1.080894)
-      (xy 6.047245 -1.111478)
-      (xy 6.049732 -1.123372)
-      (xy 6.058753 -1.148573)
-      (xy 6.064534 -1.153849)
-      (xy 6.071949 -1.172231)
-      (xy 6.076365 -1.205065)
-      (xy 5.931085 -1.205065)
-      (xy 5.920485 -1.164719)
-      (xy 5.912815 -1.153788)
-      (xy 5.882616 -1.134642)
-      (xy 5.852258 -1.136625)
-      (xy 5.832737 -1.158719)
-      (xy 5.831993 -1.16125)
-      (xy 5.820277 -1.185246)
-      (xy 5.811176 -1.190854)
-      (xy 5.800513 -1.203254)
-      (xy 5.7981 -1.220176)
-      (xy 5.81136 -1.247738)
-      (xy 5.835105 -1.258785)
-      (xy 5.862815 -1.270257)
-      (xy 5.872109 -1.281395)
-      (xy 5.882394 -1.285047)
-      (xy 5.901713 -1.27623)
-      (xy 5.924421 -1.246726)
-      (xy 5.931085 -1.205065)
-      (xy 6.076365 -1.205065)
-      (xy 6.07726 -1.211722)
-      (xy 6.079335 -1.263844)
-      (xy 6.079336 -1.264863)
-      (xy 6.077331 -1.317138)
-      (xy 6.072069 -1.356936)
-      (xy 6.064682 -1.375781)
-      (xy 6.064534 -1.375877)
-      (xy 6.050981 -1.397265)
-      (xy 6.049732 -1.406749)
-      (xy 6.039737 -1.431662)
-      (xy 6.015107 -1.465351)
-      (xy 5.98387 -1.498995)
-      (xy 5.954057 -1.523776)
-      (xy 5.936339 -1.531297)
-      (xy 5.918219 -1.540112)
-      (xy 5.916515 -1.546099)
-      (xy 5.903848 -1.557226)
-      (xy 5.87951 -1.560901)
-      (xy 5.851693 -1.565967)
-      (xy 5.842506 -1.575702)
-      (xy 5.829276 -1.58453)
-      (xy 5.795803 -1.589825)
-      (xy 5.775897 -1.590504)
-      (xy 5.709289 -1.590504)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 0a24d966-ac30-4549-a068-887411259672))
-  (fp_poly
-    (pts
-      (xy -0.407882 9.673735)
-      (xy -0.765506 9.6738)
-      (xy -1.095653 9.673915)
-      (xy -1.399386 9.674088)
-      (xy -1.677768 9.674324)
-      (xy -1.931862 9.674629)
-      (xy -2.162732 9.675011)
-      (xy -2.371441 9.675474)
-      (xy -2.559051 9.676025)
-      (xy -2.726627 9.676671)
-      (xy -2.87523 9.677418)
-      (xy -3.005926 9.678271)
-      (xy -3.119776 9.679238)
-      (xy -3.217843 9.680324)
-      (xy -3.301192 9.681536)
-      (xy -3.370886 9.68288)
-      (xy -3.427986 9.684362)
-      (xy -3.473558 9.685988)
-      (xy -3.508663 9.687765)
-      (xy -3.534365 9.689698)
-      (xy -3.551728 9.691795)
-      (xy -3.561814 9.694061)
-      (xy -3.562934 9.694485)
-      (xy -3.607462 9.726856)
-      (xy -3.632381 9.773272)
-      (xy -3.637912 9.825891)
-      (xy -3.624276 9.876866)
-      (xy -3.591695 9.918354)
-      (xy -3.556062 9.938145)
-      (xy -3.535461 9.940205)
-      (xy -3.486905 9.942136)
-      (xy -3.411977 9.943938)
-      (xy -3.312258 9.945613)
-      (xy -3.189334 9.947161)
-      (xy -3.044788 9.948584)
-      (xy -2.880201 9.949882)
-      (xy -2.697159 9.951055)
-      (xy -2.497243 9.952106)
-      (xy -2.282038 9.953034)
-      (xy -2.053126 9.953841)
-      (xy -1.812091 9.954528)
-      (xy -1.560516 9.955095)
-      (xy -1.299985 9.955543)
-      (xy -1.03208 9.955873)
-      (xy -0.758385 9.956085)
-      (xy -0.480482 9.956182)
-      (xy -0.199957 9.956164)
-      (xy 0.081609 9.95603)
-      (xy 0.362632 9.955784)
-      (xy 0.641529 9.955424)
-      (xy 0.916717 9.954953)
-      (xy 1.186612 9.95437)
-      (xy 1.449631 9.953677)
-      (xy 1.704191 9.952875)
-      (xy 1.948708 9.951965)
-      (xy 2.1816 9.950947)
-      (xy 2.401282 9.949822)
-      (xy 2.606173 9.948591)
-      (xy 2.794688 9.947256)
-      (xy 2.965244 9.945816)
-      (xy 3.116258 9.944273)
-      (xy 3.246147 9.942627)
-      (xy 3.353327 9.94088)
-      (xy 3.436215 9.939032)
-      (xy 3.493229 9.937084)
-      (xy 3.522784 9.935038)
-      (xy 3.526373 9.934288)
-      (xy 3.568857 9.902182)
-      (xy 3.598602 9.854554)
-      (xy 3.607424 9.812901)
-      (xy 3.594867 9.765737)
-      (xy 3.563143 9.721325)
-      (xy 3.521178 9.691763)
-      (xy 3.516854 9.690121)
-      (xy 3.501741 9.688176)
-      (xy 3.467541 9.686368)
-      (xy 3.413621 9.684694)
-      (xy 3.339348 9.683151)
-      (xy 3.244089 9.681738)
-      (xy 3.12721 9.680449)
-      (xy 2.988079 9.679284)
-      (xy 2.826061 9.678238)
-      (xy 2.640524 9.677309)
-      (xy 2.430834 9.676494)
-      (xy 2.196358 9.67579)
-      (xy 1.936463 9.675194)
-      (xy 1.650516 9.674703)
-      (xy 1.337883 9.674314)
-      (xy 0.997932 9.674025)
-      (xy 0.630028 9.673831)
-      (xy 0.233539 9.673731)
-      (xy -0.021717 9.673715)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 2fbb0269-cb0e-4243-98bf-32dc8c1f5bab))
-  (fp_poly
-    (pts
-      (xy -6.990711 -4.062416)
-      (xy -6.988973 -4.024458)
-      (xy -6.979462 -4.007585)
-      (xy -6.955738 -4.003306)
-      (xy -6.945785 -4.003208)
-      (xy -6.890875 -3.991266)
-      (xy -6.832262 -3.959002)
-      (xy -6.80093 -3.933091)
-      (xy -6.794777 -3.922297)
-      (xy -6.808048 -3.916547)
-      (xy -6.845133 -3.914494)
-      (xy -6.861842 -3.914397)
-      (xy -6.923891 -3.907282)
-      (xy -6.975328 -3.888214)
-      (xy -7.009587 -3.860609)
-      (xy -7.020315 -3.831913)
-      (xy -7.028659 -3.812914)
-      (xy -7.035117 -3.810784)
-      (xy -7.043944 -3.797554)
-      (xy -7.049239 -3.764082)
-      (xy -7.049919 -3.744176)
-      (xy -7.046979 -3.704452)
-      (xy -7.03954 -3.680624)
-      (xy -7.035117 -3.677567)
-      (xy -7.020851 -3.666214)
-      (xy -7.020315 -3.662093)
-      (xy -7.009889 -3.640565)
-      (xy -6.985308 -3.612027)
-      (xy -6.956615 -3.586522)
-      (xy -6.933851 -3.574092)
-      (xy -6.932176 -3.573954)
-      (xy -6.917262 -3.563094)
-      (xy -6.916702 -3.559152)
-      (xy -6.903989 -3.547516)
-      (xy -6.871547 -3.543769)
-      (xy -6.827924 -3.547032)
-      (xy -6.781664 -3.556423)
-      (xy -6.741315 -3.571063)
-      (xy -6.728172 -3.578575)
-      (xy -6.697322 -3.603755)
-      (xy -6.680886 -3.625595)
-      (xy -6.680066 -3.629461)
-      (xy -6.670521 -3.646663)
-      (xy -6.66507 -3.647964)
-      (xy -6.655286 -3.660976)
-      (xy -6.650396 -3.692971)
-      (xy -6.650268 -3.69977)
-      (xy -6.64655 -3.734013)
-      (xy -6.637409 -3.751129)
-      (xy -6.635466 -3.751577)
-      (xy -6.632231 -3.75558)
-      (xy -6.769483 -3.75558)
-      (xy -6.778863 -3.718886)
-      (xy -6.791725 -3.695663)
-      (xy -6.823709 -3.667207)
-      (xy -6.858206 -3.667985)
-      (xy -6.881744 -3.684901)
-      (xy -6.898084 -3.716488)
-      (xy -6.898138 -3.753162)
-      (xy -6.88374 -3.783069)
-      (xy -6.864895 -3.793867)
-      (xy -6.835192 -3.806123)
-      (xy -6.824417 -3.816197)
-      (xy -6.814983 -3.824204)
-      (xy -6.813315 -3.814485)
-      (xy -6.801166 -3.798087)
-      (xy -6.790886 -3.795982)
-      (xy -6.773465 -3.784348)
-      (xy -6.769483 -3.75558)
-      (xy -6.632231 -3.75558)
-      (xy -6.625073 -3.764439)
-      (xy -6.620666 -3.79543)
-      (xy -6.620664 -3.795982)
-      (xy -6.624952 -3.827161)
-      (xy -6.635282 -3.840384)
-      (xy -6.635466 -3.840388)
-      (xy -6.64525 -3.8534)
-      (xy -6.65014 -3.885395)
-      (xy -6.650268 -3.892194)
-      (xy -6.653986 -3.926437)
-      (xy -6.663128 -3.943553)
-      (xy -6.66507 -3.944001)
-      (xy -6.678003 -3.956072)
-      (xy -6.679872 -3.967438)
-      (xy -6.691579 -3.996113)
-      (xy -6.720865 -4.030578)
-      (xy -6.758978 -4.063092)
-      (xy -6.797166 -4.085916)
-      (xy -6.820759 -4.09202)
-      (xy -6.848447 -4.09712)
-      (xy -6.857494 -4.106821)
-      (xy -6.870724 -4.115649)
-      (xy -6.904197 -4.120944)
-      (xy -6.924103 -4.121623)
-      (xy -6.990711 -4.121623)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d3a229a4-62e0-4212-9f8b-11ae8d23c402))
-  (fp_poly
-    (pts
-      (xy 5.042311 -0.635784)
-      (xy 5.010479 -0.612537)
-      (xy 4.984985 -0.590436)
-      (xy 4.965126 -0.566019)
-      (xy 4.950199 -0.535822)
-      (xy 4.939499 -0.496382)
-      (xy 4.932323 -0.444238)
-      (xy 4.927968 -0.375926)
-      (xy 4.92573 -0.287983)
-      (xy 4.924905 -0.176947)
-      (xy 4.92479 -0.05737)
-      (xy 4.92486 0.067038)
-      (xy 4.925236 0.165499)
-      (xy 4.926171 0.241674)
-      (xy 4.927916 0.299219)
-      (xy 4.930723 0.341793)
-      (xy 4.934844 0.373054)
-      (xy 4.94053 0.39666)
-      (xy 4.948034 0.416269)
-      (xy 4.957607 0.435539)
-      (xy 4.958875 0.437943)
-      (xy 5.007502 0.501818)
-      (xy 5.057415 0.536483)
-      (xy 5.121871 0.570568)
-      (xy 6.459528 0.570568)
-      (xy 6.523983 0.536483)
-      (xy 6.587859 0.487856)
-      (xy 6.622523 0.437943)
-      (xy 6.632355 0.418473)
-      (xy 6.640088 0.399093)
-      (xy 6.645974 0.376144)
-      (xy 6.647471 0.365619)
-      (xy 6.538193 0.365619)
-      (xy 6.451659 0.452153)
-      (xy 5.129739 0.452153)
-      (xy 5.043205 0.365619)
-      (xy 5.043205 -0.054582)
-      (xy 5.043284 -0.177233)
-      (xy 5.043679 -0.273751)
-      (xy 5.044627 -0.347606)
-      (xy 5.046365 -0.402269)
-      (xy 5.049132 -0.441209)
-      (xy 5.053165 -0.467897)
-      (xy 5.0587 -0.485803)
-      (xy 5.065976 -0.498398)
-      (xy 5.07423 -0.508084)
-      (xy 5.109658 -0.5376)
-      (xy 5.141802 -0.555281)
-      (xy 5.164588 -0.558399)
-      (xy 5.213896 -0.561248)
-      (xy 5.286643 -0.563762)
-      (xy 5.379749 -0.565875)
-      (xy 5.490133 -0.567521)
-      (xy 5.614711 -0.568634)
-      (xy 5.750404 -0.569148)
-      (xy 5.790699 -0.569176)
-      (xy 5.928996 -0.568845)
-      (xy 6.057058 -0.567896)
-      (xy 6.171803 -0.566395)
-      (xy 6.270149 -0.564409)
-      (xy 6.349015 -0.562002)
-      (xy 6.40532 -0.559242)
-      (xy 6.435982 -0.556193)
-      (xy 6.439596 -0.555281)
-      (xy 6.477289 -0.533725)
-      (xy 6.507168 -0.508084)
-      (xy 6.516218 -0.497303)
-      (xy 6.523313 -0.484341)
-      (xy 6.528691 -0.465728)
-      (xy 6.532589 -0.437994)
-      (xy 6.535245 -0.397668)
-      (xy 6.536896 -0.34128)
-      (xy 6.537779 -0.265359)
-      (xy 6.538132 -0.166436)
-      (xy 6.538193 -0.054582)
-      (xy 6.538193 0.365619)
-      (xy 6.647471 0.365619)
-      (xy 6.650265 0.345969)
-      (xy 6.653213 0.30491)
-      (xy 6.65507 0.249307)
-      (xy 6.656087 0.175504)
-      (xy 6.656515 0.079842)
-      (xy 6.656608 -0.041337)
-      (xy 6.656608 -0.05737)
-      (xy 6.656446 -0.191595)
-      (xy 6.655489 -0.299679)
-      (xy 6.653034 -0.385085)
-      (xy 6.648378 -0.451276)
-      (xy 6.640816 -0.501714)
-      (xy 6.629647 -0.539862)
-      (xy 6.614165 -0.569184)
-      (xy 6.593667 -0.593141)
-      (xy 6.567451 -0.615196)
-      (xy 6.539087 -0.635784)
-      (xy 6.476436 -0.68019)
-      (xy 5.104963 -0.68019)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp ccfc67c3-52f3-45a1-afba-0fba8660a117))
-  (fp_poly
-    (pts
-      (xy -5.700761 7.174862)
-      (xy -5.727558 7.18167)
-      (xy -5.732553 7.187001)
-      (xy -5.745023 7.198799)
-      (xy -5.763898 7.201803)
-      (xy -5.791562 7.211831)
-      (xy -5.828649 7.237548)
-      (xy -5.852709 7.259269)
-      (xy -5.889719 7.301697)
-      (xy -5.906986 7.338334)
-      (xy -5.910175 7.367332)
-      (xy -5.902809 7.423989)
-      (xy -5.883443 7.471926)
-      (xy -5.856178 7.502092)
-      (xy -5.847222 7.506276)
-      (xy -5.829817 7.515789)
-      (xy -5.837909 7.531173)
-      (xy -5.842464 7.535857)
-      (xy -5.866974 7.553499)
-      (xy -5.878993 7.557048)
-      (xy -5.899407 7.570381)
-      (xy -5.914386 7.605299)
-      (xy -5.923339 7.654184)
-      (xy -5.925676 7.709418)
-      (xy -5.920806 7.76338)
-      (xy -5.908138 7.808453)
-      (xy -5.899679 7.823889)
-      (xy -5.865178 7.868966)
-      (xy -5.837899 7.891905)
-      (xy -5.815894 7.897491)
-      (xy -5.790241 7.906108)
-      (xy -5.784359 7.912293)
-      (xy -5.766398 7.918674)
-      (xy -5.725383 7.92364)
-      (xy -5.667851 7.926571)
-      (xy -5.628066 7.927095)
-      (xy -5.559588 7.92568)
-      (xy -5.510117 7.921723)
-      (xy -5.48395 7.915656)
-      (xy -5.480921 7.912293)
-      (xy -5.468805 7.899471)
-      (xy -5.456781 7.897491)
-      (xy -5.441599 7.892068)
-      (xy -5.438167 7.870885)
-      (xy -5.441817 7.841984)
-      (xy -5.447908 7.800755)
-      (xy -5.451048 7.770988)
-      (xy -5.451154 7.767975)
-      (xy -5.463929 7.754072)
-      (xy -5.488322 7.749472)
-      (xy -5.516139 7.754539)
-      (xy -5.525326 7.764274)
-      (xy -5.538888 7.772055)
-      (xy -5.574666 7.777366)
-      (xy -5.619244 7.779076)
-      (xy -5.689261 7.773446)
-      (xy -5.73445 7.755412)
-      (xy -5.757589 7.723255)
-      (xy -5.762156 7.690731)
-      (xy -5.750265 7.6521)
-      (xy -5.713959 7.627792)
-      (xy -5.652294 7.617268)
-      (xy -5.63264 7.616726)
-      (xy -5.55493 7.616256)
-      (xy -5.55493 7.549647)
-      (xy -5.556212 7.50869)
-      (xy -5.563644 7.489292)
-      (xy -5.582608 7.483417)
-      (xy -5.599537 7.483039)
-      (xy -5.65134 7.474269)
-      (xy -5.698407 7.452045)
-      (xy -5.721225 7.431232)
-      (xy -5.73244 7.395169)
-      (xy -5.723584 7.35733)
-      (xy -5.701841 7.334427)
-      (xy -5.672043 7.326921)
-      (xy -5.632053 7.326315)
-      (xy -5.592335 7.331421)
-      (xy -5.563353 7.341049)
-      (xy -5.55493 7.351123)
-      (xy -5.545847 7.365565)
-      (xy -5.523493 7.361956)
-      (xy -5.495215 7.343491)
-      (xy -5.468455 7.31351)
-      (xy -5.445717 7.270028)
-      (xy -5.447704 7.242728)
-      (xy -5.474407 7.231668)
-      (xy -5.481794 7.231407)
-      (xy -5.505369 7.22504)
-      (xy -5.510525 7.216605)
-      (xy -5.523192 7.205478)
-      (xy -5.547529 7.201803)
-      (xy -5.575347 7.196736)
-      (xy -5.584534 7.187001)
-      (xy -5.597846 7.178558)
-      (xy -5.631884 7.173199)
-      (xy -5.658543 7.1722)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5534c284-2c01-4af1-b4ea-5c6798841d88))
-  (fp_poly
-    (pts
-      (xy -6.895535 -1.588557)
-      (xy -6.932416 -1.583334)
-      (xy -6.946305 -1.575764)
-      (xy -6.946305 -1.575702)
-      (xy -6.958294 -1.562571)
-      (xy -6.968508 -1.560901)
-      (xy -6.988132 -1.549052)
-      (xy -6.990711 -1.538698)
-      (xy -6.998704 -1.519)
-      (xy -7.005513 -1.516495)
-      (xy -7.017395 -1.503878)
-      (xy -7.021584 -1.472269)
-      (xy -7.018892 -1.431031)
-      (xy -7.01013 -1.389528)
-      (xy -6.996111 -1.357124)
-      (xy -6.991137 -1.350722)
-      (xy -6.971558 -1.327395)
-      (xy -6.972255 -1.312347)
-      (xy -6.991137 -1.294098)
-      (xy -7.013259 -1.269048)
-      (xy -7.020315 -1.252026)
-      (xy -7.030475 -1.236109)
-      (xy -7.035117 -1.23526)
-      (xy -7.04671 -1.223076)
-      (xy -7.048124 -1.192653)
-      (xy -7.04031 -1.153181)
-      (xy -7.024222 -1.113852)
-      (xy -7.022158 -1.110219)
-      (xy -6.990037 -1.070666)
-      (xy -6.952931 -1.040992)
-      (xy -6.905548 -1.024135)
-      (xy -6.844799 -1.016511)
-      (xy -6.783746 -1.018575)
-      (xy -6.735451 -1.030778)
-      (xy -6.730527 -1.033279)
-      (xy -6.691011 -1.060866)
-      (xy -6.661533 -1.09139)
-      (xy -6.650268 -1.115988)
-      (xy -6.64328 -1.140371)
-      (xy -6.631766 -1.163385)
-      (xy -6.620721 -1.188533)
-      (xy -6.628819 -1.200233)
-      (xy -6.631766 -1.201422)
-      (xy -6.635939 -1.20614)
-      (xy -6.770597 -1.20614)
-      (xy -6.774804 -1.163173)
-      (xy -6.777967 -1.154279)
-      (xy -6.795111 -1.137411)
-      (xy -6.83221 -1.133968)
-      (xy -6.840875 -1.134566)
-      (xy -6.878679 -1.141737)
-      (xy -6.895747 -1.158434)
-      (xy -6.899232 -1.172376)
-      (xy -6.893173 -1.209937)
-      (xy -6.869388 -1.238997)
-      (xy -6.836503 -1.254075)
-      (xy -6.803142 -1.249688)
-      (xy -6.791314 -1.240974)
-      (xy -6.770597 -1.20614)
-      (xy -6.635939 -1.20614)
-      (xy -6.648286 -1.2201)
-      (xy -6.650268 -1.231161)
-      (xy -6.661185 -1.258098)
-      (xy -6.676171 -1.273598)
-      (xy -6.692305 -1.288515)
-      (xy -6.693177 -1.305132)
-      (xy -6.678787 -1.334643)
-      (xy -6.676171 -1.339338)
-      (xy -6.651895 -1.40776)
-      (xy -6.652416 -1.42237)
-      (xy -6.783485 -1.42237)
-      (xy -6.785786 -1.400012)
-      (xy -6.797547 -1.386634)
-      (xy -6.826052 -1.377372)
-      (xy -6.861195 -1.370492)
-      (xy -6.871155 -1.380419)
-      (xy -6.872296 -1.389446)
-      (xy -6.883616 -1.414044)
-      (xy -6.890798 -1.419049)
-      (xy -6.901684 -1.42877)
-      (xy -6.890798 -1.436318)
-      (xy -6.873854 -1.457076)
-      (xy -6.872296 -1.466387)
-      (xy -6.861268 -1.490039)
-      (xy -6.835862 -1.496634)
-      (xy -6.807598 -1.483459)
-      (xy -6.806068 -1.481985)
-      (xy -6.788241 -1.449794)
-      (xy -6.783485 -1.42237)
-      (xy -6.652416 -1.42237)
-      (xy -6.654262 -1.47409)
-      (xy -6.682772 -1.532599)
-      (xy -6.694175 -1.545588)
-      (xy -6.719921 -1.569418)
-      (xy -6.744951 -1.582908)
-      (xy -6.778839 -1.588962)
-      (xy -6.83116 -1.590487)
-      (xy -6.842194 -1.590504)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f2315e8d-4fce-42bf-96b4-9825ce3e4a44))
-  (fp_poly
-    (pts
-      (xy -1.576867 2.675695)
-      (xy -1.638177 2.680199)
-      (xy -1.67789 2.686681)
-      (xy -1.70401 2.697583)
-      (xy -1.724538 2.715347)
-      (xy -1.731131 2.722761)
-      (xy -1.754618 2.7578)
-      (xy -1.765552 2.789353)
-      (xy -1.765653 2.791673)
-      (xy -1.77201 2.815274)
-      (xy -1.780455 2.820451)
-      (xy -1.791678 2.833091)
-      (xy -1.795257 2.856582)
-      (xy -1.800714 2.887924)
-      (xy -1.810058 2.901862)
-      (xy -1.817032 2.920023)
-      (xy -1.822238 2.959965)
-      (xy -1.824758 3.013877)
-      (xy -1.82486 3.027677)
-      (xy -1.823103 3.083732)
-      (xy -1.818444 3.127645)
-      (xy -1.811801 3.151606)
-      (xy -1.810058 3.153493)
-      (xy -1.798322 3.174033)
-      (xy -1.795257 3.196498)
-      (xy -1.78581 3.242639)
-      (xy -1.761935 3.295892)
-      (xy -1.730327 3.342628)
-      (xy -1.716376 3.357019)
-      (xy -1.680585 3.377189)
-      (xy -1.652374 3.382922)
-      (xy -1.625659 3.388288)
-      (xy -1.617634 3.397724)
-      (xy -1.604503 3.406993)
-      (xy -1.571699 3.412149)
-      (xy -1.558427 3.412526)
-      (xy -1.521351 3.409243)
-      (xy -1.500729 3.401042)
-      (xy -1.499219 3.397724)
-      (xy -1.486585 3.38648)
-      (xy -1.463272 3.382922)
-      (xy -1.427079 3.374404)
-      (xy -1.407765 3.361233)
-      (xy -1.373488 3.321723)
-      (xy -1.356045 3.29701)
-      (xy -1.351201 3.281167)
-      (xy -1.339489 3.264063)
-      (xy -1.332715 3.260812)
-      (xy -1.324632 3.249041)
-      (xy -1.319052 3.217954)
-      (xy -1.315699 3.164459)
-      (xy -1.314296 3.085468)
-      (xy -1.314213 3.054782)
-      (xy -1.314286 3.047453)
-      (xy -1.469616 3.047453)
-      (xy -1.471224 3.109572)
-      (xy -1.475657 3.153669)
-      (xy -1.482328 3.174653)
-      (xy -1.484417 3.175696)
-      (xy -1.498055 3.187447)
-      (xy -1.499219 3.194888)
-      (xy -1.506795 3.215937)
-      (xy -1.524188 3.244961)
-      (xy -1.543397 3.269964)
-      (xy -1.555399 3.279113)
-      (xy -1.56764 3.269921)
-      (xy -1.591925 3.247126)
-      (xy -1.596104 3.242977)
-      (xy -1.621111 3.209607)
-      (xy -1.632384 3.178041)
-      (xy -1.632436 3.176369)
-      (xy -1.638511 3.151953)
-      (xy -1.647238 3.146092)
-      (xy -1.654847 3.132413)
-      (xy -1.6601 3.095795)
-      (xy -1.66204 3.043353)
-      (xy -1.660051 2.990849)
-      (xy -1.65483 2.950798)
-      (xy -1.647491 2.931637)
-      (xy -1.647238 2.931465)
-      (xy -1.635118 2.910813)
-      (xy -1.631965 2.889887)
-      (xy -1.619597 2.844243)
-      (xy -1.588592 2.813838)
-      (xy -1.555943 2.805649)
-      (xy -1.520564 2.819644)
-      (xy -1.494205 2.861001)
-      (xy -1.477203 2.928783)
-      (xy -1.469891 3.022053)
-      (xy -1.469616 3.047453)
-      (xy -1.314286 3.047453)
-      (xy -1.315135 2.962138)
-      (xy -1.319056 2.892927)
-      (xy -1.327683 2.841002)
-      (xy -1.34272 2.800221)
-      (xy -1.365873 2.76444)
-      (xy -1.398849 2.727513)
-      (xy -1.407514 2.718704)
-      (xy -1.457125 2.668763)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp e6f02aad-7320-44b4-b47c-3369c1b51c1b))
-  (fp_poly
-    (pts
-      (xy 5.97119 7.203148)
-      (xy 5.919437 7.206926)
-      (xy 5.891082 7.212756)
-      (xy 5.886911 7.216605)
-      (xy 5.874553 7.228751)
-      (xy 5.858181 7.231407)
-      (xy 5.827866 7.239551)
-      (xy 5.817182 7.265701)
-      (xy 5.825303 7.312435)
-      (xy 5.828744 7.323369)
-      (xy 5.847227 7.363647)
-      (xy 5.868651 7.388874)
-      (xy 5.887874 7.394714)
-      (xy 5.898359 7.382089)
-      (xy 5.916075 7.367345)
-      (xy 5.931677 7.364624)
-      (xy 5.959497 7.357536)
-      (xy 5.968322 7.349822)
-      (xy 5.987759 7.3403)
-      (xy 6.024475 7.33526)
-      (xy 6.03493 7.33502)
-      (xy 6.07405 7.338511)
-      (xy 6.098965 7.347167)
-      (xy 6.101538 7.349822)
-      (xy 6.12269 7.362876)
-      (xy 6.135716 7.364717)
-      (xy 6.158614 7.377048)
-      (xy 6.183857 7.406884)
-      (xy 6.204238 7.443711)
-      (xy 6.212552 7.476837)
-      (xy 6.220939 7.495753)
-      (xy 6.227354 7.497841)
-      (xy 6.236231 7.51106)
-      (xy 6.241514 7.544459)
-      (xy 6.242156 7.563575)
-      (xy 6.23909 7.605409)
-      (xy 6.23137 7.633502)
-      (xy 6.227354 7.638458)
-      (xy 6.213928 7.659792)
-      (xy 6.212552 7.670074)
-      (xy 6.202718 7.69413)
-      (xy 6.178224 7.726385)
-      (xy 6.169285 7.735809)
-      (xy 6.136733 7.763059)
-      (xy 6.102328 7.775833)
-      (xy 6.052545 7.779074)
-      (xy 6.05087 7.779076)
-      (xy 5.975722 7.779076)
-      (xy 5.975722 7.527444)
-      (xy 5.812902 7.527444)
-      (xy 5.813129 7.708767)
-      (xy 5.814064 7.78003)
-      (xy 5.816445 7.840944)
-      (xy 5.819914 7.885147)
-      (xy 5.824115 7.906274)
-      (xy 5.82423 7.906457)
-      (xy 5.843459 7.914697)
-      (xy 5.88509 7.922113)
-      (xy 5.941922 7.92816)
-      (xy 6.006754 7.932294)
-      (xy 6.072388 7.93397)
-      (xy 6.13162 7.932642)
-      (xy 6.151295 7.931205)
-      (xy 6.218683 7.91334)
-      (xy 6.254757 7.889158)
-      (xy 6.284567 7.865056)
-      (xy 6.306673 7.853233)
-      (xy 6.308613 7.852992)
-      (xy 6.325484 7.840862)
-      (xy 6.346439 7.811798)
-      (xy 6.365077 7.776551)
-      (xy 6.374996 7.745871)
-      (xy 6.375373 7.740872)
-      (xy 6.38376 7.721956)
-      (xy 6.390175 7.719869)
-      (xy 6.397063 7.705801)
-      (xy 6.40204 7.666464)
-      (xy 6.404672 7.606153)
-      (xy 6.404977 7.572724)
-      (xy 6.403567 7.508412)
-      (xy 6.399749 7.456689)
-      (xy 6.394144 7.424092)
-      (xy 6.390175 7.41643)
-      (xy 6.37774 7.395553)
-      (xy 6.375373 7.378552)
-      (xy 6.369741 7.354967)
-      (xy 6.362297 7.349822)
-      (xy 6.348469 7.337506)
-      (xy 6.3415 7.320293)
-      (xy 6.322691 7.291065)
-      (xy 6.306469 7.280704)
-      (xy 6.277354 7.262583)
-      (xy 6.267324 7.251026)
-      (xy 6.243953 7.234486)
-      (xy 6.226619 7.231407)
-      (xy 6.202968 7.225067)
-      (xy 6.19775 7.216605)
-      (xy 6.183635 7.20983)
-      (xy 6.143964 7.204901)
-      (xy 6.08275 7.202201)
-      (xy 6.042331 7.201803)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 136b564b-136b-499f-ad0e-6786eef1329b))
-  (fp_poly
-    (pts
-      (xy 6.50859 2.539216)
-      (xy 6.459284 2.539216)
-      (xy 6.285563 2.539216)
-      (xy 6.234256 2.539216)
-      (xy 6.203028 2.537843)
-      (xy 6.188038 2.528425)
-      (xy 6.183325 2.503011)
-      (xy 6.182949 2.470795)
-      (xy 6.184258 2.430277)
-      (xy 6.189617 2.41424)
-      (xy 6.201166 2.417622)
-      (xy 6.204382 2.420162)
-      (xy 6.225789 2.444294)
-      (xy 6.251084 2.480978)
-      (xy 6.255689 2.488583)
-      (xy 6.285563 2.539216)
-      (xy 6.459284 2.539216)
-      (xy 6.418499 2.532348)
-      (xy 6.393195 2.507554)
-      (xy 6.390175 2.502211)
-      (xy 6.371924 2.475335)
-      (xy 6.35807 2.465207)
-      (xy 6.348121 2.452769)
-      (xy 6.345769 2.435138)
-      (xy 6.336124 2.406676)
-      (xy 6.323566 2.39655)
-      (xy 6.303886 2.377427)
-      (xy 6.301364 2.366541)
-      (xy 6.291812 2.344894)
-      (xy 6.267037 2.310666)
-      (xy 6.239748 2.279314)
-      (xy 6.200868 2.241087)
-      (xy 6.169888 2.221143)
-      (xy 6.137003 2.21404)
-      (xy 6.121333 2.213575)
-      (xy 6.064534 2.213575)
-      (xy 6.064534 2.376395)
-      (xy 6.064193 2.447652)
-      (xy 6.062551 2.494425)
-      (xy 6.058676 2.521831)
-      (xy 6.051639 2.534989)
-      (xy 6.040509 2.539016)
-      (xy 6.03493 2.539216)
-      (xy 6.015562 2.544181)
-      (xy 6.007002 2.564249)
-      (xy 6.005326 2.598423)
-      (xy 6.007809 2.637159)
-      (xy 6.017843 2.654279)
-      (xy 6.03493 2.657631)
-      (xy 6.054298 2.662596)
-      (xy 6.062858 2.682664)
-      (xy 6.064534 2.716838)
-      (xy 6.064534 2.776046)
-      (xy 6.182949 2.776046)
-      (xy 6.182949 2.657631)
-      (xy 6.50859 2.657631)
-      (xy 6.50859 2.776046)
-      (xy 6.627005 2.776046)
-      (xy 6.627005 2.657631)
-      (xy 6.75282 2.657631)
-      (xy 6.814183 2.657009)
-      (xy 6.851683 2.6543)
-      (xy 6.87105 2.648241)
-      (xy 6.878014 2.637568)
-      (xy 6.878636 2.629877)
-      (xy 6.870824 2.563687)
-      (xy 6.856266 2.523893)
-      (xy 6.715816 2.523893)
-      (xy 6.702956 2.534651)
-      (xy 6.67197 2.539215)
-      (xy 6.67141 2.539216)
-      (xy 6.646456 2.538002)
-      (xy 6.633326 2.529608)
-      (xy 6.628399 2.506908)
-      (xy 6.628056 2.462776)
-      (xy 6.628173 2.454105)
-      (xy 6.630049 2.412796)
-      (xy 6.633761 2.390617)
-      (xy 6.637793 2.391197)
-      (xy 6.650547 2.41527)
-      (xy 6.655469 2.420801)
-      (xy 6.672912 2.441663)
-      (xy 6.693656 2.474457)
-      (xy 6.710334 2.506603)
-      (xy 6.715816 2.523893)
-      (xy 6.856266 2.523893)
-      (xy 6.849931 2.506578)
-      (xy 6.832585 2.481653)
-      (xy 6.811932 2.45521)
-      (xy 6.804627 2.438607)
-      (xy 6.795745 2.420406)
-      (xy 6.773294 2.389465)
-      (xy 6.760273 2.373645)
-      (xy 6.723548 2.328089)
-      (xy 6.68854 2.280764)
-      (xy 6.682072 2.271348)
-      (xy 6.65635 2.239223)
-      (xy 6.627759 2.223297)
-      (xy 6.583535 2.216812)
-      (xy 6.578407 2.216464)
-      (xy 6.50859 2.211953)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 20fd2493-346d-4b7c-b23b-a53b4d72b47d))
-  (fp_poly
-    (pts
-      (xy -6.168567 -0.42021)
-      (xy -6.19698 -0.415517)
-      (xy -6.206212 -0.408036)
-      (xy -6.219372 -0.39818)
-      (xy -6.252607 -0.388516)
-      (xy -6.27139 -0.385141)
-      (xy -6.314555 -0.375481)
-      (xy -6.336876 -0.359829)
-      (xy -6.345681 -0.339054)
-      (xy -6.357572 -0.311659)
-      (xy -6.369315 -0.302742)
-      (xy -6.38123 -0.290381)
-      (xy -6.383835 -0.274012)
-      (xy -6.390631 -0.245676)
-      (xy -6.398636 -0.236134)
-      (xy -6.406281 -0.217076)
-      (xy -6.411049 -0.176375)
-      (xy -6.413027 -0.121841)
-      (xy -6.412303 -0.061286)
-      (xy -6.408965 -0.002521)
-      (xy -6.403101 0.046643)
-      (xy -6.395109 0.077709)
-      (xy -6.375644 0.114386)
-      (xy -6.358104 0.138671)
-      (xy -6.34184 0.166257)
-      (xy -6.339429 0.178921)
-      (xy -6.327778 0.197087)
-      (xy -6.297389 0.224004)
-      (xy -6.259335 0.250847)
-      (xy -6.202874 0.282557)
-      (xy -6.148222 0.301207)
-      (xy -6.080291 0.311817)
-      (xy -6.074312 0.312422)
-      (xy -5.969382 0.322761)
-      (xy -5.969382 0.284718)
-      (xy -5.964188 0.252626)
-      (xy -5.954581 0.237526)
-      (xy -5.940961 0.216109)
-      (xy -5.939779 0.207049)
-      (xy -5.949564 0.192783)
-      (xy -5.981864 0.186399)
-      (xy -6.006387 0.185719)
-      (xy -6.046111 0.182779)
-      (xy -6.069939 0.175341)
-      (xy -6.072995 0.170918)
-      (xy -6.085398 0.158909)
-      (xy -6.102727 0.156116)
-      (xy -6.128893 0.147437)
-      (xy -6.163283 0.126315)
-      (xy -6.196109 0.100122)
-      (xy -6.217583 0.076228)
-      (xy -6.221014 0.067042)
-      (xy -6.207485 0.061712)
-      (xy -6.171986 0.057457)
-      (xy -6.12215 0.055186)
-      (xy -6.121263 0.05517)
-      (xy -6.070309 0.052218)
-      (xy -6.032639 0.046114)
-      (xy -6.016416 0.038185)
-      (xy -5.999789 0.023378)
-      (xy -5.995774 0.022899)
-      (xy -5.970376 0.010096)
-      (xy -5.942629 -0.022553)
-      (xy -5.918237 -0.066404)
-      (xy -5.902905 -0.112814)
-      (xy -5.901714 -0.119628)
-      (xy -5.900014 -0.170664)
-      (xy -6.058194 -0.170664)
-      (xy -6.064186 -0.146)
-      (xy -6.072995 -0.139922)
-      (xy -6.08703 -0.128402)
-      (xy -6.087797 -0.123051)
-      (xy -6.100706 -0.096374)
-      (xy -6.132552 -0.077012)
-      (xy -6.173016 -0.067767)
-      (xy -6.211778 -0.07144)
-      (xy -6.232856 -0.083675)
-      (xy -6.243822 -0.106994)
-      (xy -6.249501 -0.142572)
-      (xy -6.249643 -0.179424)
-      (xy -6.243998 -0.206562)
-      (xy -6.235816 -0.213931)
-      (xy -6.222684 -0.22592)
-      (xy -6.221014 -0.236134)
-      (xy -6.208764 -0.254377)
-      (xy -6.192644 -0.258337)
-      (xy -6.166145 -0.266684)
-      (xy -6.15813 -0.276768)
-      (xy -6.146031 -0.280502)
-      (xy -6.123908 -0.266196)
-      (xy -6.098039 -0.240516)
-      (xy -6.074706 -0.210131)
-      (xy -6.060187 -0.181707)
-      (xy -6.058194 -0.170664)
-      (xy -5.900014 -0.170664)
-      (xy -5.899042 -0.199845)
-      (xy -5.916156 -0.264998)
-      (xy -5.937562 -0.297041)
-      (xy -5.961537 -0.328402)
-      (xy -5.97283 -0.349452)
-      (xy -5.992884 -0.36978)
-      (xy -6.02742 -0.383895)
-      (xy -6.061833 -0.394919)
-      (xy -6.081093 -0.407482)
-      (xy -6.0811 -0.407494)
-      (xy -6.09912 -0.416148)
-      (xy -6.132111 -0.420403)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp eeef72b0-ba43-4d01-90ee-36b97875f1ec))
-  (fp_poly
-    (pts
-      (xy -6.160797 -8.025393)
-      (xy -6.183004 -8.01582)
-      (xy -6.184009 -8.014514)
-      (xy -6.204405 -8.003072)
-      (xy -6.229423 -7.999712)
-      (xy -6.263673 -7.989257)
-      (xy -6.30203 -7.963411)
-      (xy -6.335006 -7.930454)
-      (xy -6.353115 -7.898663)
-      (xy -6.354231 -7.890796)
-      (xy -6.361617 -7.869787)
-      (xy -6.369033 -7.866495)
-      (xy -6.378459 -7.853841)
-      (xy -6.383052 -7.823686)
-      (xy -6.382777 -7.787741)
-      (xy -6.377603 -7.757718)
-      (xy -6.369368 -7.745613)
-      (xy -6.352714 -7.726396)
-      (xy -6.34501 -7.691469)
-      (xy -6.347228 -7.653628)
-      (xy -6.360266 -7.625744)
-      (xy -6.379365 -7.597337)
-      (xy -6.383835 -7.57979)
-      (xy -6.392452 -7.554137)
-      (xy -6.398636 -7.548255)
-      (xy -6.408098 -7.528847)
-      (xy -6.413168 -7.492034)
-      (xy -6.413438 -7.480773)
-      (xy -6.41011 -7.444021)
-      (xy -6.401808 -7.423796)
-      (xy -6.398636 -7.422439)
-      (xy -6.385505 -7.41045)
-      (xy -6.383835 -7.400236)
-      (xy -6.377713 -7.380513)
-      (xy -6.372543 -7.378033)
-      (xy -6.358684 -7.366128)
-      (xy -6.346639 -7.344729)
-      (xy -6.322496 -7.316818)
-      (xy -6.298724 -7.306695)
-      (xy -6.272697 -7.297794)
-      (xy -6.26542 -7.288193)
-      (xy -6.251664 -7.28241)
-      (xy -6.214571 -7.277823)
-      (xy -6.160398 -7.275016)
-      (xy -6.117401 -7.27442)
-      (xy -6.048639 -7.275828)
-      (xy -5.998925 -7.279765)
-      (xy -5.972524 -7.285806)
-      (xy -5.969382 -7.289222)
-      (xy -5.956973 -7.301211)
-      (xy -5.939497 -7.304024)
-      (xy -5.922993 -7.306799)
-      (xy -5.916127 -7.31898)
-      (xy -5.918644 -7.346356)
-      (xy -5.930287 -7.394713)
-      (xy -5.934751 -7.411338)
-      (xy -5.951782 -7.433271)
-      (xy -5.976692 -7.435052)
-      (xy -5.991585 -7.422439)
-      (xy -6.010206 -7.414546)
-      (xy -6.049166 -7.409176)
-      (xy -6.089344 -7.407637)
-      (xy -6.143465 -7.409736)
-      (xy -6.178698 -7.418075)
-      (xy -6.205587 -7.435722)
-      (xy -6.214286 -7.443969)
-      (xy -6.24329 -7.479399)
-      (xy -6.247173 -7.507496)
-      (xy -6.226286 -7.536017)
-      (xy -6.218749 -7.542818)
-      (xy -6.174651 -7.564323)
-      (xy -6.115136 -7.570458)
-      (xy -6.043392 -7.570458)
-      (xy -6.043392 -7.718476)
-      (xy -6.095198 -7.718476)
-      (xy -6.129446 -7.721792)
-      (xy -6.146559 -7.729946)
-      (xy -6.147005 -7.731674)
-      (xy -6.159549 -7.744704)
-      (xy -6.184009 -7.754158)
-      (xy -6.213331 -7.77294)
-      (xy -6.222502 -7.802167)
-      (xy -6.211069 -7.830708)
-      (xy -6.18771 -7.84529)
-      (xy -6.156988 -7.860101)
-      (xy -6.143756 -7.872191)
-      (xy -6.127194 -7.881101)
-      (xy -6.106182 -7.872026)
-      (xy -6.07419 -7.858714)
-      (xy -6.029514 -7.847096)
-      (xy -6.019976 -7.845338)
-      (xy -5.98114 -7.840753)
-      (xy -5.959426 -7.848052)
-      (xy -5.943036 -7.872795)
-      (xy -5.937506 -7.884213)
-      (xy -5.923557 -7.917775)
-      (xy -5.925611 -7.93866)
-      (xy -5.946245 -7.960572)
-      (xy -5.952951 -7.96639)
-      (xy -5.991865 -7.989765)
-      (xy -6.031777 -7.999691)
-      (xy -6.03229 -7.999694)
-      (xy -6.061831 -8.004351)
-      (xy -6.072995 -8.014514)
-      (xy -6.085992 -8.024364)
-      (xy -6.11788 -8.029211)
-      (xy -6.123928 -8.029316)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 632eaf6e-5d54-46de-8f55-4208c0c0b677))
-  (fp_poly
-    (pts
-      (xy -5.514841 -8.279533)
-      (xy -5.639373 -8.279029)
-      (xy -5.789831 -8.278164)
-      (xy -5.845714 -8.277816)
-      (xy -6.524452 -8.273546)
-      (xy -6.57197 -8.239653)
-      (xy -6.614301 -8.202938)
-      (xy -6.651849 -8.160358)
-      (xy -6.65338 -8.158243)
-      (xy -6.662873 -8.144279)
-      (xy -6.670404 -8.129705)
-      (xy -6.6762 -8.11113)
-      (xy -6.680489 -8.08516)
-      (xy -6.683497 -8.048403)
-      (xy -6.685451 -7.997468)
-      (xy -6.686579 -7.928962)
-      (xy -6.687107 -7.839492)
-      (xy -6.687263 -7.725667)
-      (xy -6.687273 -7.651868)
-      (xy -6.687224 -7.523283)
-      (xy -6.686928 -7.420909)
-      (xy -6.686156 -7.341354)
-      (xy -6.684682 -7.281226)
-      (xy -6.682278 -7.237133)
-      (xy -6.678719 -7.205682)
-      (xy -6.673775 -7.183481)
-      (xy -6.667221 -7.167138)
-      (xy -6.65883 -7.153261)
-      (xy -6.65338 -7.145493)
-      (xy -6.616664 -7.103161)
-      (xy -6.574084 -7.065613)
-      (xy -6.57197 -7.064083)
-      (xy -6.524452 -7.03019)
-      (xy -5.850967 -7.027474)
-      (xy -5.711284 -7.02717)
-      (xy -5.579724 -7.027381)
-      (xy -5.459451 -7.028067)
-      (xy -5.353629 -7.029187)
-      (xy -5.265424 -7.0307)
-      (xy -5.197999 -7.032564)
-      (xy -5.154519 -7.034741)
-      (xy -5.139199 -7.036648)
-      (xy -5.065487 -7.07282)
-      (xy -5.009384 -7.131502)
-      (xy -4.994651 -7.15527)
-      (xy -4.985378 -7.172559)
-      (xy -4.978065 -7.190034)
-      (xy -4.972516 -7.211183)
-      (xy -4.968538 -7.239494)
-      (xy -4.965936 -7.278452)
-      (xy -4.964515 -7.331546)
-      (xy -4.964081 -7.402262)
-      (xy -4.964439 -7.494088)
-      (xy -4.965394 -7.610511)
-      (xy -4.965866 -7.660968)
-      (xy -5.066469 -7.660968)
-      (xy -5.067088 -7.546274)
-      (xy -5.068854 -7.444951)
-      (xy -5.071632 -7.360665)
-      (xy -5.075286 -7.297084)
-      (xy -5.079678 -7.257875)
-      (xy -5.081738 -7.249481)
-      (xy -5.104309 -7.210336)
-      (xy -5.137171 -7.174643)
-      (xy -5.137245 -7.174581)
-      (xy -5.177483 -7.141351)
-      (xy -5.826544 -7.141277)
-      (xy -6.475606 -7.141204)
-      (xy -6.525933 -7.19153)
-      (xy -6.576259 -7.241856)
-      (xy -6.576259 -8.06188)
-      (xy -6.525933 -8.112206)
-      (xy -6.475606 -8.162532)
-      (xy -5.66535 -8.162532)
-      (xy -5.531509 -8.162316)
-      (xy -5.421959 -8.161565)
-      (xy -5.334043 -8.159957)
-      (xy -5.265105 -8.157174)
-      (xy -5.212489 -8.152893)
-      (xy -5.173538 -8.146795)
-      (xy -5.145595 -8.138559)
-      (xy -5.126005 -8.127865)
-      (xy -5.112111 -8.114393)
-      (xy -5.101256 -8.097821)
-      (xy -5.090784 -8.07783)
-      (xy -5.088587 -8.073558)
-      (xy -5.081441 -8.054464)
-      (xy -5.075942 -8.025886)
-      (xy -5.071899 -7.984285)
-      (xy -5.069123 -7.926121)
-      (xy -5.067423 -7.847854)
-      (xy -5.066611 -7.745945)
-      (xy -5.066469 -7.660968)
-      (xy -4.965866 -7.660968)
-      (xy -4.965948 -7.669768)
-      (xy -4.970257 -8.125528)
-      (xy -5.006376 -8.173676)
-      (xy -5.043453 -8.211058)
-      (xy -5.091241 -8.244773)
-      (xy -5.104736 -8.251955)
-      (xy -5.120295 -8.259031)
-      (xy -5.136907 -8.26488)
-      (xy -5.157337 -8.269597)
-      (xy -5.184348 -8.273278)
-      (xy -5.220703 -8.276021)
-      (xy -5.269167 -8.277921)
-      (xy -5.332502 -8.279076)
-      (xy -5.413472 -8.279581)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 23b08156-b9d5-4c9b-9cc7-bc50381875f3))
-  (fp_poly
-    (pts
-      (xy -5.846009 -0.684472)
-      (xy -6.511856 -0.68019)
-      (xy -6.571868 -0.640461)
-      (xy -6.628035 -0.589153)
-      (xy -6.664105 -0.534164)
-      (xy -6.673346 -0.51403)
-      (xy -6.680581 -0.493793)
-      (xy -6.68601 -0.469806)
-      (xy -6.689834 -0.438418)
-      (xy -6.692254 -0.395979)
-      (xy -6.693472 -0.33884)
-      (xy -6.693688 -0.263351)
-      (xy -6.693104 -0.165862)
-      (xy -6.69192 -0.042724)
-      (xy -6.691802 -0.031269)
-      (xy -6.687273 0.405058)
-      (xy -6.641815 0.46191)
-      (xy -6.622176 0.48648)
-      (xy -6.60415 0.507038)
-      (xy -6.585041 0.523939)
-      (xy -6.562148 0.537539)
-      (xy -6.532772 0.548194)
-      (xy -6.494216 0.556262)
-      (xy -6.443779 0.562097)
-      (xy -6.378765 0.566056)
-      (xy -6.296472 0.568497)
-      (xy -6.194204 0.569773)
-      (xy -6.069261 0.570243)
-      (xy -5.918944 0.570262)
-      (xy -5.821364 0.570208)
-      (xy -5.660179 0.570034)
-      (xy -5.525923 0.569614)
-      (xy -5.415924 0.568859)
-      (xy -5.327508 0.567677)
-      (xy -5.258001 0.565977)
-      (xy -5.204731 0.56367)
-      (xy -5.165022 0.560663)
-      (xy -5.136202 0.556866)
-      (xy -5.115598 0.552189)
-      (xy -5.100535 0.546541)
-      (xy -5.098731 0.545675)
-      (xy -5.057454 0.517583)
-      (xy -5.017352 0.478638)
-      (xy -5.00992 0.469481)
-      (xy -4.970257 0.417507)
-      (xy -4.965948 -0.039432)
-      (xy -4.964901 -0.155763)
-      (xy -5.068377 -0.155763)
-      (xy -5.069485 -0.026511)
-      (xy -5.07387 0.365814)
-      (xy -5.122209 0.408984)
-      (xy -5.170549 0.452153)
-      (xy -5.825298 0.451824)
-      (xy -5.98266 0.451667)
-      (xy -6.113092 0.451303)
-      (xy -6.219265 0.45063)
-      (xy -6.303851 0.449548)
-      (xy -6.369523 0.447955)
-      (xy -6.418953 0.445751)
-      (xy -6.454814 0.442836)
-      (xy -6.479778 0.439107)
-      (xy -6.496518 0.434465)
-      (xy -6.507704 0.428807)
-      (xy -6.511619 0.425921)
-      (xy -6.530175 0.409505)
-      (xy -6.544801 0.391401)
-      (xy -6.555962 0.368071)
-      (xy -6.564125 0.335981)
-      (xy -6.569754 0.291594)
-      (xy -6.573316 0.231375)
-      (xy -6.575277 0.151788)
-      (xy -6.576102 0.049297)
-      (xy -6.576259 -0.064706)
-      (xy -6.576259 -0.465096)
-      (xy -6.533078 -0.513435)
-      (xy -6.489897 -0.561775)
-      (xy -5.84493 -0.565927)
-      (xy -5.687462 -0.566837)
-      (xy -5.556872 -0.567302)
-      (xy -5.450439 -0.567247)
-      (xy -5.365439 -0.566594)
-      (xy -5.29915 -0.565267)
-      (xy -5.24885 -0.563188)
-      (xy -5.211815 -0.560281)
-      (xy -5.185323 -0.556469)
-      (xy -5.166651 -0.551675)
-      (xy -5.154253 -0.546442)
-      (xy -5.129222 -0.531638)
-      (xy -5.10936 -0.513758)
-      (xy -5.094124 -0.489479)
-      (xy -5.082973 -0.455477)
-      (xy -5.075365 -0.408427)
-      (xy -5.070757 -0.345008)
-      (xy -5.068609 -0.261894)
-      (xy -5.068377 -0.155763)
-      (xy -4.964901 -0.155763)
-      (xy -4.964793 -0.167823)
-      (xy -4.964148 -0.270093)
-      (xy -4.964207 -0.349727)
-      (xy -4.965164 -0.410205)
-      (xy -4.967215 -0.455011)
-      (xy -4.970553 -0.487627)
-      (xy -4.975374 -0.511535)
-      (xy -4.981871 -0.530218)
-      (xy -4.99024 -0.547158)
-      (xy -4.994766 -0.555314)
-      (xy -5.034688 -0.606259)
-      (xy -5.094157 -0.64653)
-      (xy -5.104028 -0.651506)
-      (xy -5.180163 -0.688755)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 8cf529b2-ca25-427c-bee0-415e546e88d5))
-  (fp_poly
-    (pts
-      (xy 5.624797 6.920585)
-      (xy 5.484902 6.920858)
-      (xy 5.369291 6.921714)
-      (xy 5.275303 6.923483)
-      (xy 5.200278 6.926495)
-      (xy 5.141557 6.931078)
-      (xy 5.096479 6.937563)
-      (xy 5.062385 6.946277)
-      (xy 5.036614 6.957551)
-      (xy 5.016506 6.971714)
-      (xy 4.999401 6.989094)
-      (xy 4.982639 7.010022)
-      (xy 4.973633 7.021817)
-      (xy 4.932191 7.075987)
-      (xy 4.932191 8.010809)
-      (xy 4.972061 8.063081)
-      (xy 4.98953 8.08576)
-      (xy 5.006136 8.104757)
-      (xy 5.024532 8.120395)
-      (xy 5.047371 8.133001)
-      (xy 5.077305 8.142898)
-      (xy 5.116987 8.150412)
-      (xy 5.169071 8.155867)
-      (xy 5.236208 8.159588)
-      (xy 5.321053 8.1619)
-      (xy 5.426257 8.163128)
-      (xy 5.554474 8.163597)
-      (xy 5.708356 8.163631)
-      (xy 5.792936 8.163588)
-      (xy 5.954771 8.163409)
-      (xy 6.089664 8.162989)
-      (xy 6.200278 8.162238)
-      (xy 6.289275 8.161066)
-      (xy 6.359316 8.159383)
-      (xy 6.413064 8.157099)
-      (xy 6.45318 8.154125)
-      (xy 6.482328 8.15037)
-      (xy 6.503168 8.145745)
-      (xy 6.518363 8.14016)
-      (xy 6.520733 8.139031)
-      (xy 6.562011 8.11094)
-      (xy 6.602114 8.071996)
-      (xy 6.609544 8.062842)
-      (xy 6.649207 8.010871)
-      (xy 6.653725 7.568293)
-      (xy 6.653962 7.543544)
-      (xy 6.538193 7.543544)
-      (xy 6.53811 7.664448)
-      (xy 6.537693 7.759331)
-      (xy 6.53669 7.831777)
-      (xy 6.534847 7.885366)
-      (xy 6.531914 7.923683)
-      (xy 6.527637 7.950309)
-      (xy 6.521765 7.968827)
-      (xy 6.514045 7.98282)
-      (xy 6.506545 7.99294)
-      (xy 6.475373 8.024829)
-      (xy 6.444187 8.045811)
-      (xy 6.443637 8.046041)
-      (xy 6.42258 8.048692)
-      (xy 6.375135 8.051021)
-      (xy 6.304518 8.052981)
-      (xy 6.213944 8.054525)
-      (xy 6.106627 8.055605)
-      (xy 5.985784 8.056175)
-      (xy 5.854629 8.056186)
-      (xy 5.773156 8.055909)
-      (xy 5.133935 8.052911)
-      (xy 5.08857 8.009436)
-      (xy 5.043205 7.965962)
-      (xy 5.043205 7.550171)
-      (xy 5.043394 7.425851)
-      (xy 5.044082 7.327719)
-      (xy 5.045453 7.252363)
-      (xy 5.047689 7.196367)
-      (xy 5.050973 7.156319)
-      (xy 5.055489 7.128806)
-      (xy 5.06142 7.110413)
-      (xy 5.067342 7.09992)
-      (xy 5.080938 7.082008)
-      (xy 5.096182 7.067164)
-      (xy 5.115821 7.055101)
-      (xy 5.142603 7.045531)
-      (xy 5.179275 7.038166)
-      (xy 5.228584 7.032719)
-      (xy 5.293278 7.028903)
-      (xy 5.376105 7.026428)
-      (xy 5.479811 7.025009)
-      (xy 5.607145 7.024356)
-      (xy 5.760853 7.024183)
-      (xy 5.790699 7.024181)
-      (xy 5.94931 7.0243)
-      (xy 6.081066 7.024847)
-      (xy 6.188713 7.026112)
-      (xy 6.274998 7.02838)
-      (xy 6.34267 7.031941)
-      (xy 6.394476 7.037082)
-      (xy 6.433163 7.044089)
-      (xy 6.461479 7.053252)
-      (xy 6.482171 7.064858)
-      (xy 6.497986 7.079194)
-      (xy 6.511673 7.096548)
-      (xy 6.514056 7.09992)
-      (xy 6.521312 7.113562)
-      (xy 6.526981 7.133621)
-      (xy 6.531252 7.163544)
-      (xy 6.534311 7.206774)
-      (xy 6.536346 7.266755)
-      (xy 6.537545 7.346933)
-      (xy 6.538094 7.450751)
-      (xy 6.538193 7.543544)
-      (xy 6.653962 7.543544)
-      (xy 6.654937 7.441839)
-      (xy 6.655573 7.341375)
-      (xy 6.655439 7.263287)
-      (xy 6.654341 7.203965)
-      (xy 6.652084 7.159795)
-      (xy 6.648474 7.127165)
-      (xy 6.643317 7.102464)
-      (xy 6.63642 7.082079)
-      (xy 6.627587 7.062397)
-      (xy 6.6264 7.059936)
-      (xy 6.57878 6.99293)
-      (xy 6.531771 6.957363)
-      (xy 6.468984 6.920568)
-      (xy 5.791636 6.920568)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b072a6f9-85a5-44cc-8dd8-dc2e08d83cc5))
-  (fp_poly
-    (pts
-      (xy -5.415652 9.395598)
-      (xy -5.573122 9.396634)
-      (xy -5.703749 9.397628)
-      (xy -5.810294 9.398725)
-      (xy -5.895518 9.400075)
-      (xy -5.962182 9.401822)
-      (xy -6.013045 9.404115)
-      (xy -6.050869 9.4071)
-      (xy -6.078415 9.410925)
-      (xy -6.098443 9.415737)
-      (xy -6.113713 9.421682)
-      (xy -6.126987 9.428909)
-      (xy -6.135157 9.433931)
-      (xy -6.179858 9.470145)
-      (xy -6.218963 9.51517)
-      (xy -6.223968 9.522742)
-      (xy -6.233556 9.538877)
-      (xy -6.241151 9.555303)
-      (xy -6.246984 9.575486)
-      (xy -6.25129 9.602893)
-      (xy -6.254299 9.640991)
-      (xy -6.256243 9.693247)
-      (xy -6.257355 9.763129)
-      (xy -6.257868 9.854102)
-      (xy -6.258012 9.969634)
-      (xy -6.258019 10.031286)
-      (xy -6.258019 10.485069)
-      (xy -6.213242 10.540392)
-      (xy -6.193095 10.56535)
-      (xy -6.174745 10.586228)
-      (xy -6.155484 10.603391)
-      (xy -6.132605 10.617202)
-      (xy -6.1034 10.628025)
-      (xy -6.065161 10.636223)
-      (xy -6.015181 10.64216)
-      (xy -5.950752 10.646199)
-      (xy -5.869166 10.648704)
-      (xy -5.767717 10.650038)
-      (xy -5.643695 10.650566)
-      (xy -5.494394 10.650649)
-      (xy -5.39211 10.650638)
-      (xy -5.232464 10.650573)
-      (xy -5.099694 10.650308)
-      (xy -4.991074 10.649741)
-      (xy -4.903877 10.648768)
-      (xy -4.835374 10.647286)
-      (xy -4.78284 10.645193)
-      (xy -4.743546 10.642384)
-      (xy -4.714767 10.638757)
-      (xy -4.693775 10.63421)
-      (xy -4.677842 10.628637)
-      (xy -4.666587 10.623203)
-      (xy -4.626599 10.594046)
-      (xy -4.585533 10.552288)
-      (xy -4.570606 10.533153)
-      (xy -4.526201 10.470538)
-      (xy -4.521643 10.048124)
-      (xy -4.519807 9.877909)
-      (xy -4.638898 9.877909)
-      (xy -4.639679 9.989272)
-      (xy -4.640239 10.043388)
-      (xy -4.644616 10.441518)
-      (xy -4.68809 10.48687)
-      (xy -4.731564 10.532223)
-      (xy -5.391179 10.531752)
-      (xy -5.559652 10.53142)
-      (xy -5.700459 10.530649)
-      (xy -5.815539 10.529386)
-      (xy -5.906825 10.52758)
-      (xy -5.976255 10.525178)
-      (xy -6.025766 10.522128)
-      (xy -6.057292 10.518376)
-      (xy -6.07277 10.51387)
-      (xy -6.073675 10.51325)
-      (xy -6.095039 10.49547)
-      (xy -6.111793 10.477291)
-      (xy -6.124497 10.455053)
-      (xy -6.133709 10.425098)
-      (xy -6.139991 10.383767)
-      (xy -6.143901 10.3274)
-      (xy -6.146 10.25234)
-      (xy -6.146848 10.154926)
-      (xy -6.147005 10.034031)
-      (xy -6.146464 9.925825)
-      (xy -6.144937 9.826752)
-      (xy -6.142568 9.741053)
-      (xy -6.1395 9.672971)
-      (xy -6.135877 9.626749)
-      (xy -6.132572 9.608077)
-      (xy -6.110265 9.574903)
-      (xy -6.074716 9.543794)
-      (xy -6.069664 9.54056)
-      (xy -6.05671 9.533348)
-      (xy -6.041849 9.527413)
-      (xy -6.02224 9.522632)
-      (xy -5.995048 9.518879)
-      (xy -5.957434 9.51603)
-      (xy -5.90656 9.513961)
-      (xy -5.839589 9.512547)
-      (xy -5.753682 9.511663)
-      (xy -5.646003 9.511185)
-      (xy -5.513712 9.510988)
-      (xy -5.395075 9.51095)
-      (xy -5.234411 9.510994)
-      (xy -5.100678 9.511373)
-      (xy -4.991204 9.512414)
-      (xy -4.903315 9.514441)
-      (xy -4.83434 9.517779)
-      (xy -4.781605 9.522754)
-      (xy -4.742438 9.529692)
-      (xy -4.714166 9.538916)
-      (xy -4.694117 9.550753)
-      (xy -4.679618 9.565527)
-      (xy -4.667996 9.583565)
-      (xy -4.658991 9.600529)
-      (xy -4.651937 9.618067)
-      (xy -4.646567 9.642327)
-      (xy -4.642729 9.676875)
-      (xy -4.640272 9.725277)
-      (xy -4.639045 9.7911)
-      (xy -4.638898 9.877909)
-      (xy -4.519807 9.877909)
-      (xy -4.517086 9.625711)
-      (xy -4.555679 9.546831)
-      (xy -4.584101 9.496453)
-      (xy -4.615694 9.462991)
-      (xy -4.66193 9.434943)
-      (xy -4.67259 9.429633)
-      (xy -4.750908 9.391315)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 5a37ddaf-cbf2-49af-9e0e-27770056929d))
-  (fp_poly
-    (pts
-      (xy -6.571846 -3.17158)
-      (xy -6.628095 -3.120201)
-      (xy -6.664105 -3.065283)
-      (xy -6.673346 -3.045149)
-      (xy -6.680581 -3.024912)
-      (xy -6.68601 -3.000925)
-      (xy -6.689834 -2.969537)
-      (xy -6.692254 -2.927098)
-      (xy -6.693472 -2.869959)
-      (xy -6.693688 -2.79447)
-      (xy -6.693104 -2.696981)
-      (xy -6.69192 -2.573843)
-      (xy -6.691802 -2.562388)
-      (xy -6.687273 -2.126061)
-      (xy -6.642496 -2.070767)
-      (xy -6.622232 -2.045696)
-      (xy -6.603761 -2.024744)
-      (xy -6.584359 -2.007542)
-      (xy -6.561299 -1.993721)
-      (xy -6.531857 -1.982911)
-      (xy -6.493306 -1.974744)
-      (xy -6.442922 -1.96885)
-      (xy -6.377977 -1.964859)
-      (xy -6.295748 -1.962404)
-      (xy -6.193507 -1.961113)
-      (xy -6.06853 -1.960619)
-      (xy -5.918091 -1.960552)
-      (xy -5.828996 -1.960563)
-      (xy -5.671012 -1.960606)
-      (xy -5.539836 -1.960808)
-      (xy -5.43267 -1.961291)
-      (xy -5.346718 -1.962172)
-      (xy -5.279183 -1.963573)
-      (xy -5.227269 -1.965612)
-      (xy -5.18818 -1.968409)
-      (xy -5.159118 -1.972085)
-      (xy -5.137287 -1.976758)
-      (xy -5.11989 -1.982549)
-      (xy -5.104132 -1.989577)
-      (xy -5.099628 -1.991785)
-      (xy -5.052857 -2.021588)
-      (xy -5.012548 -2.058164)
-      (xy -5.003416 -2.069483)
-      (xy -4.994083 -2.083441)
-      (xy -4.986649 -2.098518)
-      (xy -4.980859 -2.118117)
-      (xy -4.976459 -2.145643)
-      (xy -4.973196 -2.184501)
-      (xy -4.970816 -2.238093)
-      (xy -4.969064 -2.309825)
-      (xy -4.967686 -2.4031)
-      (xy -4.96643 -2.521322)
-      (xy -4.966162 -2.54938)
-      (xy -5.064581 -2.54938)
-      (xy -5.065885 -2.450387)
-      (xy -5.068635 -2.35844)
-      (xy -5.072826 -2.278675)
-      (xy -5.07845 -2.216231)
-      (xy -5.0855 -2.176245)
-      (xy -5.088587 -2.167941)
-      (xy -5.099272 -2.147278)
-      (xy -5.109819 -2.130089)
-      (xy -5.12288 -2.116054)
-      (xy -5.141106 -2.104856)
-      (xy -5.16715 -2.096177)
-      (xy -5.203662 -2.0897)
-      (xy -5.253294 -2.085106)
-      (xy -5.318698 -2.082079)
-      (xy -5.402525 -2.080299)
-      (xy -5.507427 -2.079451)
-      (xy -5.636055 -2.079215)
-      (xy -5.791062 -2.079274)
-      (xy -5.828358 -2.079295)
-      (xy -5.985326 -2.079452)
-      (xy -6.11537 -2.079819)
-      (xy -6.221169 -2.080496)
-      (xy -6.305401 -2.081586)
-      (xy -6.370747 -2.083189)
-      (xy -6.419885 -2.085408)
-      (xy -6.455494 -2.088344)
-      (xy -6.480254 -2.092099)
-      (xy -6.496844 -2.096774)
-      (xy -6.507943 -2.102471)
-      (xy -6.511619 -2.105198)
-      (xy -6.530175 -2.121613)
-      (xy -6.544801 -2.139718)
-      (xy -6.555962 -2.163048)
-      (xy -6.564125 -2.195138)
-      (xy -6.569754 -2.239525)
-      (xy -6.573316 -2.299744)
-      (xy -6.575277 -2.379331)
-      (xy -6.576102 -2.481821)
-      (xy -6.576259 -2.595825)
-      (xy -6.576259 -2.996214)
-      (xy -6.489897 -3.092894)
-      (xy -5.84493 -3.097046)
-      (xy -5.680952 -3.098052)
-      (xy -5.54398 -3.098561)
-      (xy -5.431418 -3.098252)
-      (xy -5.340671 -3.096804)
-      (xy -5.269141 -3.093897)
-      (xy -5.214233 -3.089212)
-      (xy -5.173349 -3.082426)
-      (xy -5.143894 -3.073221)
-      (xy -5.123271 -3.061275)
-      (xy -5.108884 -3.046268)
-      (xy -5.098136 -3.02788)
-      (xy -5.088431 -3.005791)
-      (xy -5.087505 -3.003575)
-      (xy -5.079991 -2.970202)
-      (xy -5.073962 -2.913049)
-      (xy -5.069414 -2.837252)
-      (xy -5.066339 -2.74795)
-      (xy -5.06473 -2.65028)
-      (xy -5.064581 -2.54938)
-      (xy -4.966162 -2.54938)
-      (xy -4.965948 -2.571731)
-      (xy -4.96481 -2.700211)
-      (xy -4.964213 -2.802558)
-      (xy -4.96434 -2.88224)
-      (xy -4.96537 -2.942722)
-      (xy -4.967484 -2.987475)
-      (xy -4.970862 -3.019965)
-      (xy -4.975685 -3.04366)
-      (xy -4.982133 -3.062028)
-      (xy -4.990388 -3.078537)
-      (xy -4.992539 -3.082395)
-      (xy -5.025916 -3.127077)
-      (xy -5.069113 -3.167695)
-      (xy -5.078258 -3.174304)
-      (xy -5.133077 -3.211309)
-      (xy -6.511812 -3.211309)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d71acef2-68cc-4e8c-9a7d-76cb3faaf3c5))
-  (fp_poly
-    (pts
-      (xy -5.616897 -10.810277)
-      (xy -5.762619 -10.809451)
-      (xy -5.845714 -10.808934)
-      (xy -6.524452 -10.804665)
-      (xy -6.57197 -10.770772)
-      (xy -6.614301 -10.734057)
-      (xy -6.651849 -10.691477)
-      (xy -6.65338 -10.689362)
-      (xy -6.662932 -10.6753)
-      (xy -6.670497 -10.66062)
-      (xy -6.676305 -10.641902)
-      (xy -6.68059 -10.615726)
-      (xy -6.683582 -10.578669)
-      (xy -6.685514 -10.527312)
-      (xy -6.686617 -10.458234)
-      (xy -6.687124 -10.368014)
-      (xy -6.687266 -10.25323)
-      (xy -6.687273 -10.18932)
-      (xy -6.687273 -9.736795)
-      (xy -6.647544 -9.676748)
-      (xy -6.597723 -9.621788)
-      (xy -6.542959 -9.585305)
-      (xy -6.526597 -9.577784)
-      (xy -6.509567 -9.57158)
-      (xy -6.489025 -9.566572)
-      (xy -6.462128 -9.562642)
-      (xy -6.426031 -9.559671)
-      (xy -6.377889 -9.55754)
-      (xy -6.314859 -9.55613)
-      (xy -6.234097 -9.555321)
-      (xy -6.132759 -9.554996)
-      (xy -6.008001 -9.555034)
-      (xy -5.856978 -9.555318)
-      (xy -5.827792 -9.555383)
-      (xy -5.690926 -9.555906)
-      (xy -5.562518 -9.556805)
-      (xy -5.445743 -9.558027)
-      (xy -5.343774 -9.559522)
-      (xy -5.259784 -9.561237)
-      (xy -5.196949 -9.563121)
-      (xy -5.158441 -9.565121)
-      (xy -5.147879 -9.566484)
-      (xy -5.074657 -9.603004)
-      (xy -5.014952 -9.65733)
-      (xy -4.993246 -9.688889)
-      (xy -4.984361 -9.705705)
-      (xy -4.97736 -9.723277)
-      (xy -4.972058 -9.74508)
-      (xy -4.96827 -9.77459)
-      (xy -4.965812 -9.815282)
-      (xy -4.964497 -9.870631)
-      (xy -4.96414 -9.944112)
-      (xy -4.964556 -10.0392)
-      (xy -4.965559 -10.15937)
-      (xy -4.965877 -10.193332)
-      (xy -5.066469 -10.193332)
-      (xy -5.066846 -10.065655)
-      (xy -5.068351 -9.964111)
-      (xy -5.071544 -9.885233)
-      (xy -5.076985 -9.825556)
-      (xy -5.085235 -9.781614)
-      (xy -5.096854 -9.749942)
-      (xy -5.112401 -9.727072)
-      (xy -5.132437 -9.70954)
-      (xy -5.146112 -9.700588)
-      (xy -5.158677 -9.693783)
-      (xy -5.173832 -9.688169)
-      (xy -5.194363 -9.683632)
-      (xy -5.223054 -9.680057)
-      (xy -5.262691 -9.677329)
-      (xy -5.31606 -9.675336)
-      (xy -5.385944 -9.673962)
-      (xy -5.475131 -9.673093)
-      (xy -5.586403 -9.672616)
-      (xy -5.722548 -9.672415)
-      (xy -5.833945 -9.672378)
-      (xy -6.475606 -9.672323)
-      (xy -6.525933 -9.722649)
-      (xy -6.576259 -9.772975)
-      (xy -6.576259 -10.174841)
-      (xy -6.575992 -10.304849)
-      (xy -6.574837 -10.408554)
-      (xy -6.572261 -10.489255)
-      (xy -6.56773 -10.550252)
-      (xy -6.56071 -10.594843)
-      (xy -6.550669 -10.626328)
-      (xy -6.537074 -10.648004)
-      (xy -6.519391 -10.663172)
-      (xy -6.497088 -10.67513)
-      (xy -6.495262 -10.675968)
-      (xy -6.47535 -10.680675)
-      (xy -6.436972 -10.684578)
-      (xy -6.378419 -10.687721)
-      (xy -6.297982 -10.690149)
-      (xy -6.193952 -10.691905)
-      (xy -6.064621 -10.693034)
-      (xy -5.908281 -10.693582)
-      (xy -5.81656 -10.693651)
-      (xy -5.656987 -10.693648)
-      (xy -5.52434 -10.693422)
-      (xy -5.415942 -10.692644)
-      (xy -5.329113 -10.690988)
-      (xy -5.261178 -10.688126)
-      (xy -5.209458 -10.683731)
-      (xy -5.171275 -10.677476)
-      (xy -5.143952 -10.669034)
-      (xy -5.124811 -10.658077)
-      (xy -5.111175 -10.644278)
-      (xy -5.100365 -10.627309)
-      (xy -5.089704 -10.606844)
-      (xy -5.088587 -10.604677)
-      (xy -5.081429 -10.585547)
-      (xy -5.075924 -10.556917)
-      (xy -5.071879 -10.51524)
-      (xy -5.069105 -10.456971)
-      (xy -5.067411 -10.378564)
-      (xy -5.066606 -10.276473)
-      (xy -5.066469 -10.193332)
-      (xy -4.965877 -10.193332)
-      (xy -4.965948 -10.200886)
-      (xy -4.967221 -10.329111)
-      (xy -4.968519 -10.431139)
-      (xy -4.970096 -10.510376)
-      (xy -4.972209 -10.570227)
-      (xy -4.975112 -10.614099)
-      (xy -4.979062 -10.645397)
-      (xy -4.984314 -10.667527)
-      (xy -4.991123 -10.683895)
-      (xy -4.999745 -10.697907)
-      (xy -5.003664 -10.703482)
-      (xy -5.03828 -10.739186)
-      (xy -5.085056 -10.772606)
-      (xy -5.102024 -10.781761)
-      (xy -5.117984 -10.78914)
-      (xy -5.134448 -10.795243)
-      (xy -5.154187 -10.800172)
-      (xy -5.179974 -10.804026)
-      (xy -5.21458 -10.806908)
-      (xy -5.260776 -10.808919)
-      (xy -5.321334 -10.81016)
-      (xy -5.399026 -10.810733)
-      (xy -5.496623 -10.810738)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp fa7cbd91-ab3f-4225-9a41-6278f8717e82))
-  (fp_poly
-    (pts
-      (xy -6.28897 -5.74824)
-      (xy -6.357005 -5.747309)
-      (xy -6.40937 -5.745648)
-      (xy -6.448854 -5.743158)
-      (xy -6.478241 -5.739737)
-      (xy -6.500319 -5.735284)
-      (xy -6.517875 -5.729699)
-      (xy -6.533696 -5.722881)
-      (xy -6.539607 -5.720054)
-      (xy -6.589591 -5.688011)
-      (xy -6.635387 -5.646304)
-      (xy -6.645379 -5.634369)
-      (xy -6.687273 -5.579607)
-      (xy -6.687273 -5.120749)
-      (xy -6.687224 -4.992164)
-      (xy -6.686928 -4.88979)
-      (xy -6.686156 -4.810235)
-      (xy -6.684682 -4.750107)
-      (xy -6.682278 -4.706014)
-      (xy -6.678719 -4.674563)
-      (xy -6.673775 -4.652362)
-      (xy -6.667221 -4.636019)
-      (xy -6.65883 -4.622142)
-      (xy -6.65338 -4.614374)
-      (xy -6.616664 -4.572042)
-      (xy -6.574084 -4.534494)
-      (xy -6.57197 -4.532964)
-      (xy -6.524452 -4.499071)
-      (xy -5.843567 -4.495077)
-      (xy -5.683856 -4.494172)
-      (xy -5.55099 -4.493568)
-      (xy -5.442209 -4.493367)
-      (xy -5.354754 -4.49367)
-      (xy -5.285867 -4.49458)
-      (xy -5.232789 -4.496199)
-      (xy -5.192761 -4.498629)
-      (xy -5.163024 -4.501972)
-      (xy -5.140819 -4.50633)
-      (xy -5.123387 -4.511805)
-      (xy -5.107969 -4.5185)
-      (xy -5.099628 -4.522598)
-      (xy -5.052899 -4.552561)
-      (xy -5.012606 -4.58921)
-      (xy -5.003416 -4.600602)
-      (xy -4.994083 -4.61456)
-      (xy -4.986649 -4.629636)
-      (xy -4.980859 -4.649236)
-      (xy -4.976459 -4.676762)
-      (xy -4.973196 -4.71562)
-      (xy -4.970816 -4.769212)
-      (xy -4.969064 -4.840944)
-      (xy -4.967686 -4.934218)
-      (xy -4.96643 -5.052441)
-      (xy -4.966162 -5.080499)
-      (xy -5.064581 -5.080499)
-      (xy -5.065885 -4.981506)
-      (xy -5.068635 -4.889558)
-      (xy -5.072826 -4.809794)
-      (xy -5.07845 -4.74735)
-      (xy -5.0855 -4.707364)
-      (xy -5.088587 -4.699059)
-      (xy -5.099375 -4.67824)
-      (xy -5.110053 -4.660949)
-      (xy -5.123301 -4.646859)
-      (xy -5.141795 -4.635643)
-      (xy -5.168214 -4.626972)
-      (xy -5.205234 -4.620521)
-      (xy -5.255534 -4.615961)
-      (xy -5.321791 -4.612966)
-      (xy -5.406683 -4.611208)
-      (xy -5.512888 -4.61036)
-      (xy -5.643083 -4.610094)
-      (xy -5.799947 -4.610084)
-      (xy -5.81656 -4.610085)
-      (xy -6.000925 -4.610467)
-      (xy -6.155835 -4.611616)
-      (xy -6.28143 -4.613536)
-      (xy -6.377848 -4.616229)
-      (xy -6.445228 -4.619699)
-      (xy -6.48371 -4.623949)
-      (xy -6.491706 -4.626148)
-      (xy -6.515373 -4.638406)
-      (xy -6.53417 -4.653432)
-      (xy -6.548654 -4.674542)
-      (xy -6.559384 -4.70505)
-      (xy -6.566918 -4.748271)
-      (xy -6.571814 -4.807518)
-      (xy -6.57463 -4.886107)
-      (xy -6.575925 -4.987351)
-      (xy -6.576257 -5.114566)
-      (xy -6.576259 -5.128214)
-      (xy -6.576259 -5.530761)
-      (xy -6.525933 -5.581087)
-      (xy -6.475606 -5.631413)
-      (xy -5.836911 -5.631413)
-      (xy -5.673849 -5.63136)
-      (xy -5.537781 -5.630975)
-      (xy -5.426097 -5.629923)
-      (xy -5.336187 -5.627865)
-      (xy -5.26544 -5.624465)
-      (xy -5.211246 -5.619387)
-      (xy -5.170996 -5.612293)
-      (xy -5.14208 -5.602847)
-      (xy -5.121887 -5.590711)
-      (xy -5.107808 -5.57555)
-      (xy -5.097232 -5.557025)
-      (xy -5.08755 -5.5348)
-      (xy -5.087505 -5.534694)
-      (xy -5.079991 -5.501321)
-      (xy -5.073962 -5.444168)
-      (xy -5.069414 -5.368371)
-      (xy -5.066339 -5.279069)
-      (xy -5.06473 -5.181399)
-      (xy -5.064581 -5.080499)
-      (xy -4.966162 -5.080499)
-      (xy -4.965948 -5.10285)
-      (xy -4.96479 -5.231037)
-      (xy -4.964141 -5.333111)
-      (xy -4.964198 -5.412564)
-      (xy -4.965156 -5.472883)
-      (xy -4.967213 -5.517558)
-      (xy -4.970566 -5.55008)
-      (xy -4.975412 -5.573939)
-      (xy -4.981946 -5.592623)
-      (xy -4.990366 -5.609622)
-      (xy -4.994988 -5.617946)
-      (xy -5.028462 -5.663428)
-      (xy -5.070106 -5.702552)
-      (xy -5.080707 -5.709855)
-      (xy -5.093689 -5.717543)
-      (xy -5.107508 -5.723935)
-      (xy -5.124903 -5.729171)
-      (xy -5.148614 -5.73339)
-      (xy -5.18138 -5.736732)
-      (xy -5.22594 -5.739336)
-      (xy -5.285033 -5.741342)
-      (xy -5.361401 -5.742888)
-      (xy -5.457781 -5.744116)
-      (xy -5.576914 -5.745163)
-      (xy -5.721538 -5.74617)
-      (xy -5.804403 -5.746702)
-      (xy -5.962982 -5.747675)
-      (xy -6.094745 -5.748323)
-      (xy -6.202479 -5.748545)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 2bc97976-af2d-40e6-9771-68d9234e801a))
-  (fp_poly
-    (pts
-      (xy -5.867161 6.922439)
-      (xy -5.936911 6.923359)
-      (xy -5.99075 6.924975)
-      (xy -6.031415 6.927383)
-      (xy -6.061646 6.930676)
-      (xy -6.084179 6.934948)
-      (xy -6.101755 6.940294)
-      (xy -6.11711 6.946807)
-      (xy -6.122942 6.949613)
-      (xy -6.170885 6.981916)
-      (xy -6.213292 7.02457)
-      (xy -6.221014 7.035153)
-      (xy -6.258019 7.090789)
-      (xy -6.258019 7.995872)
-      (xy -6.221268 8.049506)
-      (xy -6.183859 8.092147)
-      (xy -6.138754 8.128505)
-      (xy -6.130442 8.133532)
-      (xy -6.116891 8.140638)
-      (xy -6.101989 8.146539)
-      (xy -6.083023 8.151346)
-      (xy -6.057278 8.155168)
-      (xy -6.02204 8.158116)
-      (xy -5.974594 8.160299)
-      (xy -5.912227 8.161829)
-      (xy -5.832225 8.162816)
-      (xy -5.731873 8.163368)
-      (xy -5.608457 8.163598)
-      (xy -5.459263 8.163614)
-      (xy -5.390094 8.163585)
-      (xy -5.229673 8.16347)
-      (xy -5.096142 8.163224)
-      (xy -4.986791 8.16273)
-      (xy -4.898905 8.161872)
-      (xy -4.829774 8.160534)
-      (xy -4.776683 8.158601)
-      (xy -4.736921 8.155957)
-      (xy -4.707775 8.152486)
-      (xy -4.686533 8.148072)
-      (xy -4.670482 8.1426)
-      (xy -4.656909 8.135953)
-      (xy -4.649922 8.131989)
-      (xy -4.608191 8.098675)
-      (xy -4.56996 8.053764)
-      (xy -4.561111 8.039818)
-      (xy -4.551112 8.021672)
-      (xy -4.543231 8.003724)
-      (xy -4.537217 7.98238)
-      (xy -4.532816 7.954046)
-      (xy -4.529778 7.915129)
-      (xy -4.52785 7.862035)
-      (xy -4.526779 7.791169)
-      (xy -4.526314 7.698938)
-      (xy -4.526203 7.581749)
-      (xy -4.526203 7.572839)
-      (xy -4.635146 7.572839)
-      (xy -4.636036 7.673032)
-      (xy -4.638442 7.766441)
-      (xy -4.642381 7.847874)
-      (xy -4.647873 7.912136)
-      (xy -4.654937 7.954035)
-      (xy -4.657502 7.961798)
-      (xy -4.667632 7.984572)
-      (xy -4.679058 8.003505)
-      (xy -4.694431 8.018955)
-      (xy -4.716405 8.031278)
-      (xy -4.747633 8.040829)
-      (xy -4.790768 8.047966)
-      (xy -4.848462 8.053043)
-      (xy -4.923369 8.056417)
-      (xy -5.018141 8.058444)
-      (xy -5.135432 8.059481)
-      (xy -5.277893 8.059883)
-      (xy -5.388885 8.059974)
-      (xy -5.546117 8.059887)
-      (xy -5.676384 8.059382)
-      (xy -5.782324 8.058375)
-      (xy -5.866572 8.056785)
-      (xy -5.931767 8.054528)
-      (xy -5.980545 8.051523)
-      (xy -6.015543 8.047687)
-      (xy -6.039397 8.042936)
-      (xy -6.050285 8.039275)
-      (xy -6.077533 8.026477)
-      (xy -6.09913 8.011158)
-      (xy -6.115731 7.989959)
-      (xy -6.127989 7.959522)
-      (xy -6.136557 7.916488)
-      (xy -6.142089 7.857498)
-      (xy -6.145238 7.779194)
-      (xy -6.146659 7.678218)
-      (xy -6.147004 7.551211)
-      (xy -6.147005 7.542246)
-      (xy -6.146751 7.414776)
-      (xy -6.145555 7.313484)
-      (xy -6.142764 7.234947)
-      (xy -6.137726 7.175742)
-      (xy -6.129789 7.132444)
-      (xy -6.118301 7.10163)
-      (xy -6.102608 7.079877)
-      (xy -6.082059 7.06376)
-      (xy -6.056002 7.049856)
-      (xy -6.052908 7.04838)
-      (xy -6.037196 7.042314)
-      (xy -6.016168 7.037337)
-      (xy -5.98699 7.033342)
-      (xy -5.946825 7.030228)
-      (xy -5.892836 7.027889)
-      (xy -5.822189 7.026222)
-      (xy -5.732047 7.025124)
-      (xy -5.619574 7.024489)
-      (xy -5.481933 7.024216)
-      (xy -5.39211 7.024181)
-      (xy -5.231845 7.024264)
-      (xy -5.098504 7.024747)
-      (xy -4.989408 7.025981)
-      (xy -4.901877 7.028318)
-      (xy -4.833231 7.032108)
-      (xy -4.78079 7.037703)
-      (xy -4.741875 7.045455)
-      (xy -4.713806 7.055714)
-      (xy -4.693904 7.068832)
-      (xy -4.679488 7.08516)
-      (xy -4.66788 7.105049)
-      (xy -4.660561 7.120073)
-      (xy -4.652758 7.151901)
-      (xy -4.646357 7.208107)
-      (xy -4.641376 7.283497)
-      (xy -4.637834 7.372878)
-      (xy -4.635751 7.471057)
-      (xy -4.635146 7.572839)
-      (xy -4.526203 7.572839)
-      (xy -4.526201 7.542246)
-      (xy -4.526329 7.4086)
-      (xy -4.527143 7.301098)
-      (xy -4.529283 7.216283)
-      (xy -4.53339 7.150694)
-      (xy -4.540104 7.100874)
-      (xy -4.550066 7.063363)
-      (xy -4.563918 7.034703)
-      (xy -4.5823 7.011435)
-      (xy -4.605853 6.990099)
-      (xy -4.632332 6.969439)
-      (xy -4.686688 6.927969)
-      (xy -5.374281 6.923839)
-      (xy -5.535059 6.922915)
-      (xy -5.668974 6.922311)
-      (xy -5.778761 6.922121)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp f95b8ce0-8528-4acb-b6ff-988c2c4469a8))
-  (fp_poly
-    (pts
-      (xy -1.218499 2.393138)
-      (xy -1.352381 2.393425)
-      (xy -1.467459 2.393917)
-      (xy -1.565275 2.394633)
-      (xy -1.647372 2.395591)
-      (xy -1.715292 2.39681)
-      (xy -1.770578 2.398309)
-      (xy -1.814773 2.400107)
-      (xy -1.849419 2.402221)
-      (xy -1.87606 2.40467)
-      (xy -1.896237 2.407474)
-      (xy -1.911494 2.41065)
-      (xy -1.923374 2.414217)
-      (xy -1.933418 2.418195)
-      (xy -1.934857 2.418826)
-      (xy -1.984847 2.449417)
-      (xy -2.031042 2.490957)
-      (xy -2.041093 2.50297)
-      (xy -2.083893 2.559054)
-      (xy -2.088002 3.004292)
-      (xy -2.089125 3.139784)
-      (xy -2.089321 3.249118)
-      (xy -2.087977 3.335738)
-      (xy -2.08448 3.403089)
-      (xy -2.078218 3.454614)
-      (xy -2.068577 3.493759)
-      (xy -2.054944 3.523967)
-      (xy -2.036707 3.548682)
-      (xy -2.013252 3.571349)
-      (xy -1.983966 3.595412)
-      (xy -1.982609 3.596497)
-      (xy -1.92573 3.641955)
-      (xy 0.023044 3.645733)
-      (xy 1.971818 3.64951)
-      (xy 2.03487 3.618211)
-      (xy 2.079824 3.590451)
-      (xy 2.116978 3.558356)
-      (xy 2.125711 3.547825)
-      (xy 2.136546 3.530941)
-      (xy -0.418683 3.530941)
-      (xy -1.881791 3.530941)
-      (xy -1.927335 3.485397)
-      (xy -1.972879 3.439852)
-      (xy -1.972408 3.022838)
-      (xy -1.972197 2.897657)
-      (xy -1.97153 2.798583)
-      (xy -1.969882 2.722118)
-      (xy -1.966729 2.664766)
-      (xy -1.961547 2.623029)
-      (xy -1.953813 2.593411)
-      (xy -1.943002 2.572415)
-      (xy -1.928589 2.556544)
-      (xy -1.910052 2.5423)
-      (xy -1.899277 2.534836)
-      (xy -1.888794 2.529037)
-      (xy -1.873943 2.524193)
-      (xy -1.852177 2.52022)
-      (xy -1.820948 2.517032)
-      (xy -1.777708 2.514546)
-      (xy -1.719909 2.512677)
-      (xy -1.645003 2.511339)
-      (xy -1.550442 2.510449)
-      (xy -1.433678 2.509921)
-      (xy -1.292164 2.50967)
-      (xy -1.140681 2.509612)
-      (xy -0.418683 2.509612)
-      (xy -0.418683 3.530941)
-      (xy 2.136546 3.530941)
-      (xy 2.143726 3.519752)
-      (xy 2.157929 3.489487)
-      (xy 2.168703 3.453363)
-      (xy 2.17643 3.40771)
-      (xy 2.178679 3.38157)
-      (xy 1.757191 3.38157)
-      (xy 1.657278 3.38712)
-      (xy 1.583596 3.389302)
-      (xy 1.509927 3.388213)
-      (xy 1.443034 3.384311)
-      (xy 1.38968 3.378051)
-      (xy 1.356626 3.369889)
-      (xy 1.35088 3.366463)
-      (xy 1.323886 3.354036)
-      (xy 1.316518 3.353318)
-      (xy 1.289683 3.343611)
-      (xy 1.275337 3.332437)
-      (xy 1.248921 3.311783)
-      (xy 1.236325 3.305512)
-      (xy 1.225184 3.287452)
-      (xy 1.21665 3.244373)
-      (xy 1.212475 3.196877)
-      (xy 1.210723 3.138727)
-      (xy 1.214434 3.101057)
-      (xy 1.225126 3.075009)
-      (xy 1.235779 3.060982)
-      (xy 1.261798 3.037029)
-      (xy 1.281567 3.027677)
-      (xy 1.296339 3.017582)
-      (xy 1.296066 2.996211)
-      (xy 1.282098 2.97694)
-      (xy 1.27613 2.973823)
-      (xy 1.256458 2.955186)
-      (xy 1.253928 2.944684)
-      (xy 1.245406 2.926024)
-      (xy 1.239126 2.924064)
-      (xy 1.22939 2.911041)
-      (xy 1.22447 2.878968)
-      (xy 1.224324 2.871613)
-      (xy 1.235046 2.82647)
-      (xy 1.238523 2.820451)
-      (xy 1.120711 2.820451)
-      (xy 0.913485 2.820451)
-      (xy 0.913485 3.382922)
-      (xy 0.750664 3.382922)
-      (xy 0.439825 3.382922)
-      (xy 0.291806 3.382922)
-      (xy 0.291806 2.926989)
-      (xy 0.247401 2.96847)
-      (xy 0.219539 2.997116)
-      (xy 0.204095 3.01808)
-      (xy 0.202995 3.021705)
-      (xy 0.193811 3.03949)
-      (xy 0.171348 3.067454)
-      (xy 0.167852 3.071273)
-      (xy 0.133135 3.11238)
-      (xy 0.096801 3.161331)
-      (xy 0.063635 3.21088)
-      (xy 0.038421 3.253784)
-      (xy 0.025942 3.282798)
-      (xy 0.025373 3.287023)
-      (xy 0.013395 3.311858)
-      (xy 0.00317 3.318362)
-      (xy -0.015551 3.338548)
-      (xy -0.019033 3.354902)
-      (xy -0.023447 3.371792)
-      (xy -0.041438 3.380208)
-      (xy -0.080128 3.382848)
-      (xy -0.093042 3.382922)
-      (xy -0.167051 3.382922)
-      (xy -0.167051 2.672433)
-      (xy -0.019033 2.672433)
-      (xy -0.019033 3.107969)
-      (xy 0.024771 3.056722)
-      (xy 0.051407 3.022057)
-      (xy 0.067289 2.994645)
-      (xy 0.069177 2.987708)
-      (xy 0.081002 2.965078)
-      (xy 0.089827 2.958104)
-      (xy 0.109071 2.939177)
-      (xy 0.135351 2.904435)
-      (xy 0.149206 2.883383)
-      (xy 0.181194 2.838886)
-      (xy 0.224553 2.786836)
-      (xy 0.262179 2.746466)
-      (xy 0.305915 2.705324)
-      (xy 0.339225 2.68255)
-      (xy 0.370173 2.673392)
-      (xy 0.387824 2.672433)
-      (xy 0.439825 2.672433)
-      (xy 0.439825 3.382922)
-      (xy 0.750664 3.382922)
-      (xy 0.750664 2.820451)
-      (xy 0.543438 2.820451)
-      (xy 0.543438 2.672433)
-      (xy 1.120711 2.672433)
-      (xy 1.120711 2.820451)
-      (xy 1.238523 2.820451)
-      (xy 1.262578 2.778808)
-      (xy 1.29997 2.73687)
-      (xy 1.340269 2.708899)
-      (xy 1.367319 2.702036)
-      (xy 1.393978 2.696654)
-      (xy 1.401946 2.687235)
-      (xy 1.416019 2.680358)
-      (xy 1.455393 2.675387)
-      (xy 1.515805 2.672747)
-      (xy 1.549965 2.672433)
-      (xy 1.618727 2.67384)
-      (xy 1.668441 2.677777)
-      (xy 1.694842 2.683819)
-      (xy 1.697984 2.687235)
-      (xy 1.710381 2.699261)
-      (xy 1.727587 2.702036)
-      (xy 1.737056 2.703087)
-      (xy 1.744256 2.708612)
-      (xy 1.749498 2.722175)
-      (xy 1.753091 2.747338)
-      (xy 1.755347 2.787663)
-      (xy 1.756575 2.846714)
-      (xy 1.757086 2.928051)
-      (xy 1.757191 3.035239)
-      (xy 1.757191 3.38157)
-      (xy 2.178679 3.38157)
-      (xy 2.181493 3.348861)
-      (xy 2.184274 3.273148)
-      (xy 2.185155 3.1769)
-      (xy 2.18452 3.056451)
-      (xy 2.183809 2.990673)
-      (xy 2.182291 2.871164)
-      (xy 2.180711 2.777455)
-      (xy 2.178747 2.705744)
-      (xy 2.176077 2.652228)
-      (xy 2.172378 2.613105)
-      (xy 2.16733 2.584571)
-      (xy 2.160611 2.562825)
-      (xy 2.151897 2.544063)
-      (xy 2.144951 2.531561)
-      (xy 2.110504 2.484795)
-      (xy 2.067669 2.443119)
-      (xy 2.057228 2.435349)
-      (xy 2.003598 2.398598)
-      (xy 0.066088 2.394682)
-      (xy -0.21302 2.394129)
-      (xy -0.464066 2.393669)
-      (xy -0.688595 2.393322)
-      (xy -0.888148 2.393105)
-      (xy -1.064269 2.393037)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp b54453ac-c8cc-41cf-9b6f-b0e91e0df69b))
-  (fp_poly
-    (pts
-      (xy 4.077648 9.478634)
-      (xy 4.033345 9.512585)
-      (xy 3.994583 9.552489)
-      (xy 3.988837 9.560044)
-      (xy 3.97928 9.574293)
-      (xy 3.971691 9.589539)
-      (xy 3.965803 9.609244)
-      (xy 3.961347 9.636868)
-      (xy 3.958056 9.675872)
-      (xy 3.955661 9.729717)
-      (xy 3.953895 9.801864)
-      (xy 3.95249 9.895775)
-      (xy 3.951178 10.014909)
-      (xy 3.950811 10.051162)
-      (xy 3.949592 10.177431)
-      (xy 3.948894 10.277683)
-      (xy 3.948933 10.355507)
-      (xy 3.949922 10.414489)
-      (xy 3.952074 10.458215)
-      (xy 3.955603 10.490271)
-      (xy 3.960724 10.514245)
-      (xy 3.967649 10.533723)
-      (xy 3.976593 10.552291)
-      (xy 3.981196 10.561046)
-      (xy 4.028779 10.624645)
-      (xy 4.080492 10.660959)
-      (xy 4.144947 10.695043)
-      (xy 6.548339 10.695043)
-      (xy 6.612794 10.660959)
-      (xy 6.67667 10.612331)
-      (xy 6.711335 10.562418)
-      (xy 6.721166 10.542948)
-      (xy 6.728899 10.523568)
-      (xy 6.734785 10.50062)
-      (xy 6.739077 10.470445)
-      (xy 6.742025 10.429385)
-      (xy 6.743881 10.373783)
-      (xy 6.744898 10.29998)
-      (xy 6.745327 10.204318)
-      (xy 6.74541 10.095133)
-      (xy 6.419778 10.095133)
-      (xy 6.417631 10.145542)
-      (xy 6.412027 10.18329)
-      (xy 6.404977 10.199181)
-      (xy 6.393392 10.219647)
-      (xy 6.390175 10.243403)
-      (xy 6.378817 10.277855)
-      (xy 6.349767 10.319666)
-      (xy 6.31056 10.361174)
-      (xy 6.268732 10.394715)
-      (xy 6.231819 10.412627)
-      (xy 6.222602 10.413808)
-      (xy 6.190564 10.41902)
-      (xy 6.175548 10.42861)
-      (xy 6.157493 10.435369)
-      (xy 6.117345 10.440509)
-      (xy 6.0626 10.443201)
-      (xy 6.041457 10.443412)
-      (xy 5.679685 10.443412)
-      (xy 5.531667 10.443412)
-      (xy 5.531667 9.963945)
-      (xy 5.47986 10.014158)
-      (xy 5.449505 10.04685)
-      (xy 5.43086 10.073235)
-      (xy 5.428053 10.081508)
-      (xy 5.418739 10.103265)
-      (xy 5.39608 10.133105)
-      (xy 5.393725 10.135687)
-      (xy 5.362605 10.177378)
-      (xy 5.340276 10.218887)
-      (xy 5.319152 10.260777)
-      (xy 5.296895 10.293775)
-      (xy 5.266945 10.329396)
-      (xy 5.24823 10.351772)
-      (xy 5.224836 10.387519)
-      (xy 5.213929 10.412226)
-      (xy 5.200469 10.433457)
-      (xy 5.172318 10.442309)
-      (xy 5.145821 10.443412)
-      (xy 5.087611 10.443412)
-      (xy 5.087611 10.075434)
-      (xy 4.895186 10.075434)
-      (xy 4.894991 10.183119)
-      (xy 4.894214 10.265011)
-      (xy 4.892572 10.324917)
-      (xy 4.889782 10.366646)
-      (xy 4.885559 10.394007)
-      (xy 4.879619 10.410807)
-      (xy 4.871678 10.420855)
-      (xy 4.869283 10.422807)
-      (xy 4.843291 10.432046)
-      (xy 4.798647 10.438616)
-      (xy 4.743799 10.442341)
-      (xy 4.687191 10.443045)
-      (xy 4.637272 10.44055)
-      (xy 4.602486 10.43468)
-      (xy 4.591748 10.42861)
-      (xy 4.572078 10.418626)
-      (xy 4.536161 10.413872)
-      (xy 4.531341 10.413808)
-      (xy 4.487203 10.401546)
-      (xy 4.437137 10.369224)
-      (xy 4.387881 10.323539)
-      (xy 4.346176 10.271187)
-      (xy 4.318759 10.218864)
-      (xy 4.312804 10.196663)
-      (xy 4.301506 10.083182)
-      (xy 4.309271 9.989152)
-      (xy 4.336881 9.910739)
-      (xy 4.384651 9.844602)
-      (xy 4.440216 9.792819)
-      (xy 4.492417 9.762682)
-      (xy 4.551371 9.749479)
-      (xy 4.592712 9.747724)
-      (xy 4.6321 9.744744)
-      (xy 4.655525 9.737214)
-      (xy 4.658357 9.732922)
-      (xy 4.671488 9.723653)
-      (xy 4.704292 9.718498)
-      (xy 4.717564 9.71812)
-      (xy 4.75464 9.721403)
-      (xy 4.775262 9.729604)
-      (xy 4.776771 9.732922)
-      (xy 4.789903 9.742191)
-      (xy 4.822707 9.747347)
-      (xy 4.835979 9.747724)
-      (xy 4.895186 9.747724)
-      (xy 4.895186 10.075434)
-      (xy 5.087611 10.075434)
-      (xy 5.087611 9.747724)
-      (xy 5.220827 9.747724)
-      (xy 5.221269 9.95125)
-      (xy 5.221711 10.154775)
-      (xy 5.279599 10.088167)
-      (xy 5.312724 10.046169)
-      (xy 5.337406 10.00775)
-      (xy 5.346105 9.988028)
-      (xy 5.363431 9.948769)
-      (xy 5.389953 9.915064)
-      (xy 5.41736 9.896764)
-      (xy 5.423942 9.895743)
-      (xy 5.441081 9.883977)
-      (xy 5.442855 9.8754)
-      (xy 5.452245 9.853227)
-      (xy 5.476103 9.81986)
-      (xy 5.492012 9.801391)
-      (xy 5.52668 9.767842)
-      (xy 5.558407 9.752103)
-      (xy 5.601301 9.747783)
-      (xy 5.610427 9.747724)
-      (xy 5.679685 9.747724)
-      (xy 5.679685 10.443412)
-      (xy 6.041457 10.443412)
-      (xy 5.980492 10.441764)
-      (xy 5.937358 10.437236)
-      (xy 5.917309 10.430451)
-      (xy 5.916515 10.42861)
-      (xy 5.903848 10.417483)
-      (xy 5.87951 10.413808)
-      (xy 5.842506 10.413808)
-      (xy 5.842506 10.073365)
-      (xy 5.990524 10.073365)
-      (xy 5.990524 10.324997)
-      (xy 6.057133 10.324997)
-      (xy 6.096856 10.322057)
-      (xy 6.120685 10.314618)
-      (xy 6.123741 10.310195)
-      (xy 6.13609 10.298022)
-      (xy 6.152271 10.295393)
-      (xy 6.185605 10.282192)
-      (xy 6.215844 10.248628)
-      (xy 6.236618 10.203761)
-      (xy 6.242156 10.167581)
-      (xy 6.246012 10.13414)
-      (xy 6.255446 10.118031)
-      (xy 6.256958 10.117771)
-      (xy 6.267143 10.105418)
-      (xy 6.27137 10.077046)
-      (xy 6.269375 10.045689)
-      (xy 6.260897 10.024379)
-      (xy 6.25887 10.02274)
-      (xy 6.247141 10.003855)
-      (xy 6.236932 9.969532)
-      (xy 6.236865 9.969201)
-      (xy 6.225388 9.928863)
-      (xy 6.20655 9.901576)
-      (xy 6.175136 9.8849)
-      (xy 6.125927 9.876396)
-      (xy 6.053708 9.873624)
-      (xy 6.032352 9.87354)
-      (xy 5.88711 9.87354)
-      (xy 5.866331 9.821733)
-      (xy 5.85579 9.784117)
-      (xy 5.864163 9.762041)
-      (xy 5.895222 9.751498)
-      (xy 5.935017 9.748764)
-      (xy 5.964577 9.743357)
-      (xy 5.975722 9.732922)
-      (xy 5.988873 9.724628)
-      (xy 6.022121 9.719806)
-      (xy 6.066157 9.718499)
-      (xy 6.111674 9.720751)
-      (xy 6.149363 9.726607)
-      (xy 6.164647 9.732028)
-      (xy 6.199427 9.745979)
-      (xy 6.228736 9.753931)
-      (xy 6.281244 9.778865)
-      (xy 6.329727 9.827461)
-      (xy 6.370864 9.893786)
-      (xy 6.401333 9.971908)
-      (xy 6.417811 10.055893)
-      (xy 6.419778 10.095133)
-      (xy 6.74541 10.095133)
-      (xy 6.745419 10.083139)
-      (xy 6.745419 10.067106)
-      (xy 6.745257 9.932881)
-      (xy 6.7443 9.824797)
-      (xy 6.741845 9.739391)
-      (xy 6.737189 9.6732)
-      (xy 6.729628 9.622762)
-      (xy 6.718458 9.584613)
-      (xy 6.702976 9.555292)
-      (xy 6.682479 9.531335)
-      (xy 6.656262 9.509279)
-      (xy 6.627899 9.488691)
-      (xy 6.565247 9.444286)
-      (xy 4.13289 9.444286)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 77e14973-2176-4bdd-8707-ea2f4e6f29ee))
-  (fp_poly
-    (pts
-      (xy -4.631544 4.378096)
-      (xy -5.858368 4.382048)
-      (xy -5.906517 4.418167)
-      (xy -5.943867 4.455219)
-      (xy -5.977596 4.503018)
-      (xy -5.984855 4.516651)
-      (xy -5.993471 4.535847)
-      (xy -6.000221 4.556121)
-      (xy -6.005288 4.581063)
-      (xy -6.008856 4.614265)
-      (xy -6.011108 4.659315)
-      (xy -6.012229 4.719804)
-      (xy -6.012402 4.799322)
-      (xy -6.011811 4.901459)
-      (xy -6.010716 5.021981)
-      (xy -6.006387 5.464945)
-      (xy -5.966517 5.517189)
-      (xy -5.953479 5.53485)
-      (xy -5.941774 5.550324)
-      (xy -5.929466 5.563756)
-      (xy -5.914621 5.575287)
-      (xy -5.895304 5.585063)
-      (xy -5.869581 5.593226)
-      (xy -5.835518 5.59992)
-      (xy -5.791179 5.605289)
-      (xy -5.73463 5.609476)
-      (xy -5.663936 5.612625)
-      (xy -5.577162 5.61488)
-      (xy -5.472375 5.616384)
-      (xy -5.347639 5.617281)
-      (xy -5.201019 5.617714)
-      (xy -5.030582 5.617826)
-      (xy -4.834392 5.617763)
-      (xy -4.612775 5.617667)
-      (xy -4.393305 5.617563)
-      (xy -4.201499 5.617356)
-      (xy -4.035421 5.617008)
-      (xy -3.89313 5.616481)
-      (xy -3.772689 5.615739)
-      (xy -3.672158 5.614742)
-      (xy -3.589599 5.613453)
-      (xy -3.523074 5.611835)
-      (xy -3.470644 5.609849)
-      (xy -3.43037 5.607459)
-      (xy -3.400315 5.604625)
-      (xy -3.378538 5.601311)
-      (xy -3.363102 5.597478)
-      (xy -3.352111 5.593111)
-      (xy -3.310833 5.565019)
-      (xy -3.270729 5.526075)
-      (xy -3.2633 5.516921)
-      (xy -3.223636 5.46495)
-      (xy -3.221952 5.299946)
-      (xy -3.981945 5.299946)
-      (xy -3.9878 5.323679)
-      (xy -4.008637 5.338633)
-      (xy -4.04853 5.346816)
-      (xy -4.111551 5.350237)
-      (xy -4.160249 5.35083)
-      (xy -4.228988 5.350837)
-      (xy -4.275298 5.348975)
-      (xy -4.306349 5.343622)
-      (xy -4.329315 5.333155)
-      (xy -4.351367 5.31595)
-      (xy -4.363775 5.304786)
-      (xy -4.394649 5.271198)
-      (xy -4.412989 5.240637)
-      (xy -4.415187 5.230777)
-      (xy -4.421866 5.208047)
-      (xy -4.429988 5.203552)
-      (xy -4.441078 5.190755)
-      (xy -4.44447 5.158061)
-      (xy -4.440687 5.114011)
-      (xy -4.43025 5.067148)
-      (xy -4.419926 5.038727)
-      (xy -4.380879 4.984595)
-      (xy -4.323666 4.948963)
-      (xy -4.26123 4.937118)
-      (xy -4.232721 4.932227)
-      (xy -4.222762 4.922316)
-      (xy -4.210365 4.91029)
-      (xy -4.193159 4.907514)
-      (xy -4.174659 4.903156)
-      (xy -4.165911 4.885059)
-      (xy -4.163566 4.845691)
-      (xy -4.163555 4.840906)
-      (xy -4.163555 4.774298)
-      (xy -4.415187 4.774298)
-      (xy -4.415187 4.677212)
-      (xy -4.533602 4.677212)
-      (xy -4.541337 4.701568)
-      (xy -4.546408 4.706456)
-      (xy -4.557249 4.725189)
-      (xy -4.566634 4.76035)
-      (xy -4.567385 4.764714)
-      (xy -4.579225 4.810043)
-      (xy -4.598977 4.862614)
-      (xy -4.606384 4.878867)
-      (xy -4.624838 4.921868)
-      (xy -4.635851 4.956809)
-      (xy -4.637215 4.966673)
-      (xy -4.645757 4.997004)
-      (xy -4.658947 5.0194)
-      (xy -4.676448 5.052585)
-      (xy -4.681149 5.074035)
-      (xy -4.688543 5.096016)
-      (xy -4.696422 5.099939)
-      (xy -4.707549 5.112606)
-      (xy -4.711224 5.136943)
-      (xy -4.715891 5.164767)
-      (xy -4.72485 5.173948)
-      (xy -4.737176 5.186711)
-      (xy -4.748041 5.217514)
-      (xy -4.748261 5.218502)
-      (xy -4.762548 5.265431)
-      (xy -4.780125 5.307314)
-      (xy -4.797043 5.334656)
-      (xy -4.818746 5.347489)
-      (xy -4.856003 5.350956)
-      (xy -4.871428 5.350944)
-      (xy -4.916 5.348146)
-      (xy -4.943516 5.336513)
-      (xy -4.966426 5.30963)
-      (xy -4.973957 5.298111)
-      (xy -4.995001 5.260329)
-      (xy -5.006521 5.230324)
-      (xy -5.007261 5.224728)
-      (xy -5.015088 5.205691)
-      (xy -5.021156 5.203552)
-      (xy -5.031405 5.190373)
-      (xy -5.041381 5.157016)
-      (xy -5.04504 5.136943)
-      (xy -5.053581 5.097293)
-      (xy -5.063726 5.073447)
-      (xy -5.068149 5.070335)
-      (xy -5.079511 5.058079)
-      (xy -5.081741 5.044432)
-      (xy -5.090753 5.012376)
-      (xy -5.103944 4.989796)
-      (xy -5.121277 4.956128)
-      (xy -5.125676 4.934088)
-      (xy -5.132455 4.897315)
-      (xy -5.138858 4.88141)
-      (xy -5.164858 4.827493)
-      (xy -5.189805 4.770433)
-      (xy -5.209465 4.720353)
-      (xy -5.219236 4.689187)
-      (xy -5.221195 4.669697)
-      (xy -5.211526 4.65982)
-      (xy -5.183547 4.656344)
-      (xy -5.150194 4.655998)
-      (xy -5.103864 4.657786)
-      (xy -5.077519 4.665651)
-      (xy -5.061612 4.683616)
-      (xy -5.055367 4.695954)
-      (xy -5.041846 4.731214)
-      (xy -5.036865 4.755046)
-      (xy -5.028656 4.772781)
-      (xy -5.023452 4.774298)
-      (xy -5.01416 4.787598)
-      (xy -5.004639 4.821774)
-      (xy -4.999461 4.852007)
-      (xy -4.988354 4.904565)
-      (xy -4.972064 4.950466)
-      (xy -4.963118 4.966722)
-      (xy -4.943027 5.006711)
-      (xy -4.927986 5.055537)
-      (xy -4.926832 5.06136)
-      (xy -4.913849 5.10666)
-      (xy -4.896441 5.137649)
-      (xy -4.878766 5.151197)
-      (xy -4.864982 5.144172)
-      (xy -4.859247 5.113441)
-      (xy -4.859243 5.112273)
-      (xy -4.852544 5.089594)
-      (xy -4.844441 5.085137)
-      (xy -4.831342 5.073134)
-      (xy -4.829639 5.062733)
-      (xy -4.8232 5.031483)
-      (xy -4.814837 5.010927)
-      (xy -4.796259 4.973693)
-      (xy -4.787063 4.955051)
-      (xy -4.776381 4.923846)
-      (xy -4.765891 4.879051)
-      (xy -4.763559 4.86624)
-      (xy -4.754281 4.828116)
-      (xy -4.743423 4.806075)
-      (xy -4.739527 4.803901)
-      (xy -4.729068 4.791321)
-      (xy -4.726026 4.769848)
-      (xy -4.7197 4.73064)
-      (xy -4.707523 4.695954)
-      (xy -4.693375 4.672364)
-      (xy -4.6732 4.66047)
-      (xy -4.637575 4.656358)
-      (xy -4.611311 4.655998)
-      (xy -4.562903 4.658258)
-      (xy -4.538781 4.666135)
-      (xy -4.533602 4.677212)
-      (xy -4.415187 4.677212)
-      (xy -4.415187 4.655883)
-      (xy -4.049573 4.655883)
-      (xy -4.039956 4.791373)
-      (xy -4.035594 4.85824)
-      (xy -4.032265 4.919601)
-      (xy -4.030493 4.965345)
-      (xy -4.030338 4.976397)
-      (xy -4.030338 5.025929)
-      (xy -4.119149 5.025929)
-      (xy -4.166455 5.028176)
-      (xy -4.198527 5.034046)
-      (xy -4.20796 5.040731)
-      (xy -4.219872 5.054038)
-      (xy -4.229106 5.055533)
-      (xy -4.262746 5.06889)
-      (xy -4.287149 5.103647)
-      (xy -4.296768 5.15183)
-      (xy -4.296772 5.152802)
-      (xy -4.291747 5.190699)
-      (xy -4.275823 5.203516)
-      (xy -4.274569 5.203552)
-      (xy -4.254871 5.211544)
-      (xy -4.252366 5.218353)
-      (xy -4.238517 5.225684)
-      (xy -4.200708 5.230835)
-      (xy -4.144544 5.233106)
-      (xy -4.133951 5.233155)
-      (xy -4.066474 5.231205)
-      (xy -4.027351 5.225256)
-      (xy -4.015536 5.215886)
-      (xy -4.012012 5.20335)
-      (xy -4.00344 5.214089)
-      (xy -3.992823 5.242895)
-      (xy -3.987 5.265428)
-      (xy -3.981945 5.299946)
-      (xy -3.221952 5.299946)
-      (xy -3.219119 5.022372)
-      (xy -3.217907 4.895918)
-      (xy -3.21727 4.795454)
-      (xy -3.217404 4.717367)
-      (xy -3.218503 4.658044)
-      (xy -3.22076 4.613874)
-      (xy -3.22437 4.581244)
-      (xy -3.229526 4.556543)
-      (xy -3.236424 4.536158)
-      (xy -3.245257 4.516477)
-      (xy -3.246444 4.514016)
-      (xy -3.293852 4.447226)
-      (xy -3.341503 4.411191)
-      (xy -3.40472 4.374143)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 1d643733-af99-479b-86e2-19571cec0f74))
-  (fp_poly
-    (pts
-      (xy -4.378661 1.843485)
-      (xy -4.600928 1.843528)
-      (xy -4.615012 1.843528)
-      (xy -4.838219 1.843492)
-      (xy -5.033762 1.84348)
-      (xy -5.203577 1.843637)
-      (xy -5.349605 1.84411)
-      (xy -5.473782 1.845043)
-      (xy -5.578047 1.846581)
-      (xy -5.664339 1.848871)
-      (xy -5.734597 1.852057)
-      (xy -5.790757 1.856286)
-      (xy -5.834759 1.861701)
-      (xy -5.868542 1.868449)
-      (xy -5.894043 1.876676)
-      (xy -5.9132 1.886525)
-      (xy -5.927953 1.898144)
-      (xy -5.940239 1.911677)
-      (xy -5.951998 1.927269)
-      (xy -5.964945 1.944778)
-      (xy -6.006387 1.998948)
-      (xy -6.006387 2.9188)
-      (xy -5.967003 2.978326)
-      (xy -5.954923 2.997309)
-      (xy -5.94414 3.013947)
-      (xy -5.932733 3.028393)
-      (xy -5.918778 3.040801)
-      (xy -5.900354 3.051325)
-      (xy -5.87554 3.060119)
-      (xy -5.842412 3.067335)
-      (xy -5.799049 3.073128)
-      (xy -5.743529 3.077651)
-      (xy -5.67393 3.081058)
-      (xy -5.58833 3.083502)
-      (xy -5.484806 3.085138)
-      (xy -5.361437 3.086117)
-      (xy -5.216301 3.086595)
-      (xy -5.047476 3.086725)
-      (xy -4.853039 3.08666)
-      (xy -4.631069 3.086553)
-      (xy -4.612775 3.086548)
-      (xy -4.393439 3.086445)
-      (xy -4.201765 3.086242)
-      (xy -4.03581 3.0859)
-      (xy -3.893631 3.08538)
-      (xy -3.773287 3.084646)
-      (xy -3.672834 3.083658)
-      (xy -3.590331 3.082378)
-      (xy -3.523835 3.080769)
-      (xy -3.471404 3.078793)
-      (xy -3.431096 3.07641)
-      (xy -3.400968 3.073583)
-      (xy -3.379077 3.070274)
-      (xy -3.363482 3.066444)
-      (xy -3.35224 3.062056)
-      (xy -3.351661 3.061774)
-      (xy -3.312413 3.033779)
-      (xy -3.273725 2.993032)
-      (xy -3.26285 2.978081)
-      (xy -3.223636 2.918825)
-      (xy -3.223636 2.49111)
-      (xy -3.541855 2.49111)
-      (xy -3.543529 2.543184)
-      (xy -3.547926 2.581325)
-      (xy -3.554143 2.59818)
-      (xy -3.555031 2.598423)
-      (xy -3.566253 2.611328)
-      (xy -3.576459 2.642937)
-      (xy -3.577556 2.648372)
-      (xy -3.59312 2.689034)
-      (xy -3.621213 2.73162)
-      (xy -3.654689 2.767634)
-      (xy -3.686402 2.788584)
-      (xy -3.697425 2.790848)
-      (xy -3.71704 2.798881)
-      (xy -3.719499 2.805649)
-      (xy -3.732341 2.816122)
-      (xy -3.763031 2.820451)
-      (xy -3.797214 2.825014)
-      (xy -3.815711 2.835253)
-      (xy -3.834363 2.843208)
-      (xy -3.873251 2.848581)
-      (xy -3.911923 2.850055)
-      (xy -3.960158 2.84772)
-      (xy -3.995499 2.841673)
-      (xy -4.008135 2.835253)
-      (xy -4.027818 2.825243)
-      (xy -4.063687 2.820509)
-      (xy -4.068216 2.820451)
-      (xy -4.119149 2.820451)
-      (xy -4.28197 2.820451)
-      (xy -4.44479 2.820451)
-      (xy -4.444954 2.594723)
-      (xy -4.445119 2.368994)
-      (xy -4.480413 2.4134)
-      (xy -4.51355 2.454078)
-      (xy -4.545495 2.491815)
-      (xy -4.546857 2.493375)
-      (xy -4.568821 2.524288)
-      (xy -4.578007 2.548812)
-      (xy -4.578007 2.548882)
-      (xy -4.586779 2.56708)
-      (xy -4.592809 2.56882)
-      (xy -4.606129 2.580725)
-      (xy -4.607611 2.589887)
-      (xy -4.616573 2.614245)
-      (xy -4.638715 2.64765)
-      (xy -4.644616 2.654931)
-      (xy -4.668366 2.685446)
-      (xy -4.680993 2.706132)
-      (xy -4.68162 2.708664)
-      (xy -4.690076 2.725197)
-      (xy -4.711362 2.755333)
-      (xy -4.722325 2.769435)
-      (xy -4.754859 2.803531)
-      (xy -4.787572 2.818102)
-      (xy -4.818537 2.820451)
-      (xy -4.874044 2.820451)
-      (xy -5.066469 2.820451)
-      (xy -5.117402 2.820451)
-      (xy -5.154553 2.824756)
-      (xy -5.177299 2.835257)
-      (xy -5.178341 2.836643)
-      (xy -5.199492 2.845882)
-      (xy -5.239303 2.84482)
-      (xy -5.242123 2.844397)
-      (xy -5.292647 2.836854)
-      (xy -5.350096 2.828793)
-      (xy -5.362506 2.827128)
-      (xy -5.462276 2.801768)
-      (xy -5.543924 2.755253)
-      (xy -5.568028 2.733834)
-      (xy -5.606077 2.690331)
-      (xy -5.630747 2.645495)
-      (xy -5.644555 2.59138)
-      (xy -5.650022 2.520043)
-      (xy -5.650408 2.474023)
-      (xy -5.64874 2.40378)
-      (xy -5.64359 2.354183)
-      (xy -5.63337 2.316333)
-      (xy -5.616495 2.281333)
-      (xy -5.61584 2.280183)
-      (xy -5.575069 2.221737)
-      (xy -5.532572 2.183427)
-      (xy -5.493256 2.169498)
-      (xy -5.468763 2.160401)
-      (xy -5.462886 2.152069)
-      (xy -5.446684 2.144524)
-      (xy -5.40793 2.137621)
-      (xy -5.353674 2.131785)
-      (xy -5.290966 2.127437)
-      (xy -5.226857 2.125002)
-      (xy -5.168396 2.124903)
-      (xy -5.122635 2.127563)
-      (xy -5.104609 2.130557)
-      (xy -5.066469 2.14013)
-      (xy -5.066469 2.820451)
-      (xy -4.874044 2.820451)
-      (xy -4.874044 2.124764)
-      (xy -4.740828 2.124764)
-      (xy -4.740828 2.33199)
-      (xy -4.739586 2.426404)
-      (xy -4.73572 2.492111)
-      (xy -4.729022 2.529911)
-      (xy -4.719281 2.540602)
-      (xy -4.706288 2.524982)
-      (xy -4.696277 2.50183)
-      (xy -4.674957 2.462636)
-      (xy -4.650645 2.431521)
-      (xy -4.621496 2.396701)
-      (xy -4.590493 2.353701)
-      (xy -4.585829 2.346574)
-      (xy -4.558549 2.308262)
-      (xy -4.532974 2.27878)
-      (xy -4.528214 2.274453)
-      (xy -4.50851 2.252474)
-      (xy -4.503998 2.240972)
-      (xy -4.49479 2.222904)
-      (xy -4.471471 2.192483)
-      (xy -4.457214 2.176176)
-      (xy -4.422184 2.142947)
-      (xy -4.388689 2.128032)
-      (xy -4.3462 2.124764)
-      (xy -4.28197 2.124764)
-      (xy -4.28197 2.820451)
-      (xy -4.119149 2.820451)
-      (xy -4.119149 2.480008)
-      (xy -3.971131 2.480008)
-      (xy -3.971131 2.702036)
-      (xy -3.898321 2.702036)
-      (xy -3.821243 2.692886)
-      (xy -3.765455 2.666116)
-      (xy -3.732661 2.622751)
-      (xy -3.725912 2.598423)
-      (xy -3.715059 2.552105)
-      (xy -3.700831 2.512789)
-      (xy -3.700642 2.512399)
-      (xy -3.691553 2.476692)
-      (xy -3.701707 2.449692)
-      (xy -3.715927 2.411956)
-      (xy -3.719499 2.383862)
-      (xy -3.730222 2.347894)
-      (xy -3.75787 2.306816)
-      (xy -3.765355 2.298551)
-      (xy -3.790722 2.273904)
-      (xy -3.814097 2.259623)
-      (xy -3.844571 2.252956)
-      (xy -3.89123 2.251149)
-      (xy -3.921696 2.251197)
-      (xy -3.986675 2.253647)
-      (xy -4.02644 2.2606)
-      (xy -4.045141 2.272787)
-      (xy -4.045257 2.272972)
-      (xy -4.056443 2.286689)
-      (xy -4.06674 2.283077)
-      (xy -4.08033 2.258218)
-      (xy -4.093238 2.228021)
-      (xy -4.104743 2.191371)
-      (xy -4.101818 2.165172)
-      (xy -4.081154 2.147459)
-      (xy -4.039441 2.136267)
-      (xy -3.973369 2.129633)
-      (xy -3.923218 2.127125)
-      (xy -3.848951 2.125368)
-      (xy -3.798727 2.127488)
-      (xy -3.767185 2.133959)
-      (xy -3.752197 2.142253)
-      (xy -3.722186 2.16296)
-      (xy -3.68148 2.186449)
-      (xy -3.674988 2.189834)
-      (xy -3.622487 2.232441)
-      (xy -3.581251 2.297915)
-      (xy -3.553652 2.380886)
-      (xy -3.542065 2.475986)
-      (xy -3.541855 2.49111)
-      (xy -3.223636 2.49111)
-      (xy -3.223636 2.011588)
-      (xy -3.263021 1.952074)
-      (xy -3.275112 1.933082)
-      (xy -3.28591 1.916438)
-      (xy -3.297338 1.901988)
-      (xy -3.311321 1.889577)
-      (xy -3.329782 1.879051)
-      (xy -3.354645 1.870255)
-      (xy -3.387834 1.863035)
-      (xy -3.431273 1.857237)
-      (xy -3.486887 1.852705)
-      (xy -3.556598 1.849286)
-      (xy -3.642331 1.846825)
-      (xy -3.74601 1.845168)
-      (xy -3.869558 1.84416)
-      (xy -4.0149 1.843646)
-      (xy -4.18396 1.843472)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 9f3fb963-03c0-4ee9-9527-6d5774dd347b))
-  (fp_poly
-    (pts
-      (xy -1.204137 4.00637)
-      (xy -1.337712 4.00661)
-      (xy -1.452482 4.007056)
-      (xy -1.549991 4.007727)
-      (xy -1.631781 4.008644)
-      (xy -1.699394 4.009828)
-      (xy -1.754374 4.0113)
-      (xy -1.798263 4.013079)
-      (xy -1.832604 4.015187)
-      (xy -1.85894 4.017643)
-      (xy -1.878813 4.02047)
-      (xy -1.893767 4.023686)
-      (xy -1.905343 4.027313)
-      (xy -1.915085 4.031371)
-      (xy -1.922165 4.034733)
-      (xy -1.972041 4.066829)
-      (xy -2.017753 4.108726)
-      (xy -2.027197 4.12006)
-      (xy -2.069091 4.174822)
-      (xy -2.069091 4.63368)
-      (xy -2.069043 4.762265)
-      (xy -2.068746 4.864639)
-      (xy -2.067974 4.944194)
-      (xy -2.0665 5.004322)
-      (xy -2.064097 5.048415)
-      (xy -2.060537 5.079866)
-      (xy -2.055593 5.102067)
-      (xy -2.04904 5.11841)
-      (xy -2.040648 5.132287)
-      (xy -2.035198 5.140055)
-      (xy -1.998482 5.182387)
-      (xy -1.955902 5.219935)
-      (xy -1.953788 5.221465)
-      (xy -1.906271 5.255358)
-      (xy 0.040175 5.25715)
-      (xy 0.278361 5.257319)
-      (xy 0.508699 5.257385)
-      (xy 0.729422 5.257351)
-      (xy 0.938759 5.257222)
-      (xy 1.134941 5.257002)
-      (xy 1.3162 5.256697)
-      (xy 1.480765 5.256309)
-      (xy 1.626869 5.255844)
-      (xy 1.752741 5.255306)
-      (xy 1.856612 5.254699)
-      (xy 1.936714 5.254028)
-      (xy 1.991277 5.253296)
-      (xy 2.018532 5.252509)
-      (xy 2.021109 5.252265)
-      (xy 2.061257 5.233161)
-      (xy 2.105658 5.195086)
-      (xy 2.146852 5.146258)
-      (xy 2.147989 5.144344)
-      (xy -0.403881 5.144344)
-      (xy -1.121075 5.144344)
-      (xy -1.314715 5.144021)
-      (xy -1.479094 5.143045)
-      (xy -1.614547 5.141411)
-      (xy -1.721411 5.139111)
-      (xy -1.80002 5.136137)
-      (xy -1.850711 5.132483)
-      (xy -1.873524 5.128281)
-      (xy -1.897191 5.116023)
-      (xy -1.915988 5.100997)
-      (xy -1.930472 5.079887)
-      (xy -1.941202 5.049379)
-      (xy -1.948736 5.006158)
-      (xy -1.953632 4.946911)
-      (xy -1.956449 4.868322)
-      (xy -1.957744 4.767077)
-      (xy -1.958075 4.639863)
-      (xy -1.958077 4.626215)
-      (xy -1.958077 4.223668)
-      (xy -1.857424 4.123015)
-      (xy -0.403881 4.123015)
-      (xy -0.403881 5.144344)
-      (xy 2.147989 5.144344)
-      (xy 2.177378 5.094893)
-      (xy 2.186515 5.070075)
-      (xy 2.192168 5.031468)
-      (xy 2.194275 4.996325)
-      (xy 1.786795 4.996325)
-      (xy 1.638776 4.996325)
-      (xy 1.638776 4.744694)
-      (xy 1.580566 4.744694)
-      (xy 1.538266 4.748941)
-      (xy 1.51736 4.763634)
-      (xy 1.513788 4.771688)
-      (xy 1.497176 4.803854)
-      (xy 1.479487 4.827195)
-      (xy 1.457948 4.857174)
-      (xy 1.432125 4.901334)
-      (xy 1.41941 4.926017)
-      (xy 1.385068 4.996325)
-      (xy 1.304696 4.996325)
-      (xy 1.260436 4.993937)
-      (xy 1.231245 4.987784)
-      (xy 1.224324 4.981974)
-      (xy 1.231693 4.959155)
-      (xy 1.250067 4.92193)
-      (xy 1.273849 4.880401)
-      (xy 1.297441 4.844671)
-      (xy 1.307236 4.832339)
-      (xy 1.324173 4.807807)
-      (xy 1.327937 4.796289)
-      (xy 1.337167 4.777555)
-      (xy 1.3594 4.750116)
-      (xy 1.359758 4.749735)
-      (xy 1.380487 4.725804)
-      (xy 1.381224 4.713898)
-      (xy 1.363458 4.705203)
-      (xy 1.330635 4.687631)
-      (xy 1.309543 4.664157)
-      (xy 1.120711 4.664157)
-      (xy 1.119226 4.730193)
-      (xy 1.115094 4.777587)
-      (xy 1.108802 4.801758)
-      (xy 1.105909 4.803901)
-      (xy 1.093489 4.816165)
-      (xy 1.091107 4.830695)
-      (xy 1.079408 4.861902)
-      (xy 1.049911 4.898771)
-      (xy 1.011017 4.933178)
-      (xy 0.971126 4.957)
-      (xy 0.955257 4.962068)
-      (xy 0.925298 4.972008)
-      (xy 0.913485 4.983374)
-      (xy 0.899915 4.990222)
-      (xy 0.863887 4.994528)
-      (xy 0.812423 4.996448)
-      (xy 0.788589 4.996325)
-      (xy 0.380618 4.996325)
-      (xy 0.191894 4.995132)
-      (xy 0.110541 4.994027)
-      (xy 0.052272 4.991329)
-      (xy 0.010578 4.986157)
-      (xy -0.021052 4.977634)
-      (xy -0.049128 4.964879)
-      (xy -0.054737 4.961828)
-      (xy -0.092502 4.937352)
-      (xy -0.118308 4.914169)
-      (xy -0.122745 4.907514)
-      (xy -0.137507 4.876837)
-      (xy -0.149949 4.852208)
-      (xy -0.161728 4.817294)
-      (xy -0.166496 4.778393)
-      (xy -0.164056 4.745888)
-      (xy -0.154214 4.730163)
-      (xy -0.15225 4.729892)
-      (xy -0.139892 4.717606)
-      (xy -0.137448 4.702664)
-      (xy -0.125204 4.676895)
-      (xy -0.100443 4.658576)
-      (xy -0.076117 4.640177)
-      (xy -0.063415 4.617665)
-      (xy -0.065911 4.600494)
-      (xy -0.077064 4.596675)
-      (xy -0.089218 4.583866)
-      (xy -0.100685 4.552622)
-      (xy -0.101658 4.548569)
-      (xy -0.111845 4.471228)
-      (xy -0.102274 4.409955)
-      (xy -0.071412 4.363543)
-      (xy -0.017728 4.330784)
-      (xy 0.06031 4.31047)
-      (xy 0.164232 4.301393)
-      (xy 0.21267 4.300638)
-      (xy 0.380618 4.300638)
-      (xy 0.380618 4.996325)
-      (xy 0.788589 4.996325)
-      (xy 0.752547 4.996139)
-      (xy 0.691279 4.993757)
-      (xy 0.635643 4.989458)
-      (xy 0.592662 4.983397)
-      (xy 0.569357 4.975732)
-      (xy 0.569341 4.975721)
-      (xy 0.557752 4.962747)
-      (xy 0.550153 4.941127)
-      (xy 0.545761 4.905285)
-      (xy 0.543793 4.849642)
-      (xy 0.543438 4.791168)
-      (xy 0.543438 4.626279)
-      (xy 0.691457 4.626279)
-      (xy 0.691457 4.877911)
-      (xy 0.765987 4.877911)
-      (xy 0.844925 4.866749)
-      (xy 0.912951 4.830993)
-      (xy 0.943088 4.805131)
-      (xy 0.954595 4.785142)
-      (xy 0.961612 4.748694)
-      (xy 0.964856 4.690694)
-      (xy 0.965291 4.647062)
-      (xy 0.964674 4.581659)
-      (xy 0.961829 4.538825)
-      (xy 0.955265 4.511533)
-      (xy 0.94349 4.492759)
-      (xy 0.929722 4.479504)
-      (xy 0.898736 4.457713)
-      (xy 0.874215 4.448656)
-      (xy 0.856017 4.439885)
-      (xy 0.854277 4.433855)
-      (xy 0.841104 4.424517)
-      (xy 0.807257 4.419873)
-      (xy 0.761244 4.419634)
-      (xy 0.711573 4.423514)
-      (xy 0.666751 4.431224)
-      (xy 0.637642 4.441173)
-      (xy 0.610082 4.453828)
-      (xy 0.593908 4.450756)
-      (xy 0.579829 4.427291)
-      (xy 0.571282 4.407869)
-      (xy 0.555436 4.363995)
-      (xy 0.556653 4.340017)
-      (xy 0.57607 4.330877)
-      (xy 0.588717 4.330242)
-      (xy 0.612291 4.323875)
-      (xy 0.617447 4.31544)
-      (xy 0.63064 4.306443)
-      (xy 0.663859 4.301193)
-      (xy 0.681095 4.300638)
-      (xy 0.724712 4.296731)
-      (xy 0.756708 4.286962)
-      (xy 0.762506 4.282876)
-      (xy 0.782648 4.272735)
-      (xy 0.79803 4.282876)
-      (xy 0.824402 4.295257)
-      (xy 0.863571 4.300631)
-      (xy 0.864933 4.300638)
-      (xy 0.915812 4.310843)
-      (xy 0.970765 4.33766)
-      (xy 1.022583 4.375391)
-      (xy 1.064056 4.41834)
-      (xy 1.087977 4.460809)
-      (xy 1.091107 4.479383)
-      (xy 1.098387 4.506882)
-      (xy 1.105909 4.515265)
-      (xy 1.112363 4.533196)
-      (xy 1.117382 4.573781)
-      (xy 1.120275 4.630081)
-      (xy 1.120711 4.664157)
-      (xy 1.309543 4.664157)
-      (xy 1.304527 4.658575)
-      (xy 1.27895 4.612903)
-      (xy 1.2563 4.537959)
-      (xy 1.263234 4.463993)
-      (xy 1.290663 4.404678)
-      (xy 1.324215 4.362411)
-      (xy 1.361961 4.341021)
-      (xy 1.379637 4.336686)
-      (xy 1.416512 4.3268)
-      (xy 1.438684 4.315361)
-      (xy 1.439988 4.313762)
-      (xy 1.457171 4.308557)
-      (xy 1.497717 4.304329)
-      (xy 1.555387 4.301539)
-      (xy 1.617447 4.300638)
-      (xy 1.786795 4.300638)
-      (xy 1.786795 4.996325)
-      (xy 2.194275 4.996325)
-      (xy 2.196204 4.96416)
-      (xy 2.1986 4.86901)
-      (xy 2.199336 4.746879)
-      (xy 2.198397 4.599335)
-      (xy 2.196971 4.4783)
-      (xy 2.195491 4.383168)
-      (xy 2.193651 4.310238)
-      (xy 2.191142 4.255809)
-      (xy 2.187657 4.216182)
-      (xy 2.182889 4.187655)
-      (xy 2.17653 4.166529)
-      (xy 2.168272 4.149104)
-      (xy 2.159796 4.134863)
-      (xy 2.123581 4.090163)
-      (xy 2.078556 4.051057)
-      (xy 2.070985 4.046052)
-      (xy 2.016224 4.012001)
-      (xy 0.078599 4.008085)
-      (xy -0.2002 4.007526)
-      (xy -0.450938 4.007049)
-      (xy -0.675158 4.006674)
-      (xy -0.874403 4.006422)
-      (xy -1.050215 4.006314)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 8c3310c6-596c-4d53-be4f-1c01a3a41573))
-  (fp_poly
-    (pts
-      (xy -3.024082 -9.589179)
-      (xy -3.122633 -9.587056)
-      (xy -3.214934 -9.582956)
-      (xy -3.295018 -9.576865)
-      (xy -3.33465 -9.572259)
-      (xy -3.467016 -9.546738)
-      (xy -3.599486 -9.507975)
-      (xy -3.725163 -9.45878)
-      (xy -3.837153 -9.401964)
-      (xy -3.928557 -9.340335)
-      (xy -3.951242 -9.321047)
-      (xy -3.990705 -9.286797)
-      (xy -4.025274 -9.259369)
-      (xy -4.040054 -9.249242)
-      (xy -4.065288 -9.225819)
-      (xy -4.09863 -9.183617)
-      (xy -4.135035 -9.130376)
-      (xy -4.169454 -9.073839)
-      (xy -4.196842 -9.021746)
-      (xy -4.210526 -8.987736)
-      (xy -4.223705 -8.952506)
-      (xy -4.235607 -8.933376)
-      (xy -4.238111 -8.932229)
-      (xy -4.251729 -8.917653)
-      (xy -4.26912 -8.874287)
-      (xy -4.290083 -8.802678)
-      (xy -4.298635 -8.769409)
-      (xy -4.30879 -8.707246)
-      (xy -4.315076 -8.619363)
-      (xy -4.317259 -8.509419)
-      (xy -4.317123 -8.477244)
-      (xy -4.315271 -8.26649)
-      (xy -4.258849 -8.151603)
-      (xy -4.232045 -8.099151)
-      (xy -4.209056 -8.058015)
-      (xy -4.19358 -8.034665)
-      (xy -4.190392 -8.031783)
-      (xy -4.179537 -8.014766)
-      (xy -4.178357 -8.00478)
-      (xy -4.167743 -7.981309)
-      (xy -4.139407 -7.944529)
-      (xy -4.098608 -7.899794)
-      (xy -4.050604 -7.85246)
-      (xy -4.000653 -7.807879)
-      (xy -3.954013 -7.771405)
-      (xy -3.939513 -7.761589)
-      (xy -3.891059 -7.727209)
-      (xy -3.870005 -7.703794)
-      (xy -3.876291 -7.691248)
-      (xy -3.895596 -7.688873)
-      (xy -3.920376 -7.680374)
-      (xy -3.962399 -7.657599)
-      (xy -4.015683 -7.624626)
-      (xy -4.074246 -7.585537)
-      (xy -4.132106 -7.54441)
-      (xy -4.183281 -7.505327)
-      (xy -4.221789 -7.472367)
-      (xy -4.237661 -7.455567)
-      (xy -4.265154 -7.417782)
-      (xy -4.302204 -7.363411)
-      (xy -4.342977 -7.301154)
-      (xy -4.37325 -7.253301)
-      (xy -4.408812 -7.179653)
-      (xy -4.438987 -7.085717)
-      (xy -4.46283 -6.9788)
-      (xy -4.479399 -6.866209)
-      (xy -4.487749 -6.755252)
-      (xy -4.486938 -6.653237)
-      (xy -4.476022 -6.567472)
-      (xy -4.466311 -6.532488)
-      (xy -4.450263 -6.478037)
-      (xy -4.435825 -6.414291)
-      (xy -4.430899 -6.386309)
-      (xy -4.414196 -6.309091)
-      (xy -4.389083 -6.230361)
-      (xy -4.359299 -6.160138)
-      (xy -4.328584 -6.10844)
-      (xy -4.32593 -6.105073)
-      (xy -4.299493 -6.071168)
-      (xy -4.265872 -6.026305)
-      (xy -4.248211 -6.002132)
-      (xy -4.212741 -5.956602)
-      (xy -4.172504 -5.910295)
-      (xy -4.133035 -5.868959)
-      (xy -4.099872 -5.838343)
-      (xy -4.078552 -5.824193)
-      (xy -4.07644 -5.823838)
-      (xy -4.058577 -5.813968)
-      (xy -4.038281 -5.794832)
-      (xy -4.016193 -5.778325)
-      (xy -3.974587 -5.75341)
-      (xy -3.9201 -5.723472)
-      (xy -3.859372 -5.691895)
-      (xy -3.799043 -5.662062)
-      (xy -3.745752 -5.637358)
-      (xy -3.706139 -5.621165)
-      (xy -3.688587 -5.616612)
-      (xy -3.664849 -5.610758)
-      (xy -3.629072 -5.596501)
-      (xy -3.625524 -5.594868)
-      (xy -3.583436 -5.579624)
-      (xy -3.528094 -5.564977)
-      (xy -3.497471 -5.558755)
-      (xy -3.441408 -5.548608)
-      (xy -3.371032 -5.535523)
-      (xy -3.301084 -5.522244)
-      (xy -3.297646 -5.521582)
-      (xy -3.252195 -5.515306)
-      (xy -3.187961 -5.509772)
-      (xy -3.110153 -5.505091)
-      (xy -3.023979 -5.501373)
-      (xy -2.934647 -5.498732)
-      (xy -2.847368 -5.497278)
-      (xy -2.767348 -5.497122)
-      (xy -2.699798 -5.498376)
-      (xy -2.649924 -5.501151)
-      (xy -2.622937 -5.505558)
-      (xy -2.620195 -5.507097)
-      (xy -2.608845 -5.512317)
-      (xy -2.582374 -5.518659)
-      (xy -2.537637 -5.526658)
-      (xy -2.471489 -5.536849)
-      (xy -2.380787 -5.549767)
-      (xy -2.320723 -5.558034)
-      (xy -2.260908 -5.567132)
-      (xy -2.209668 -5.576602)
-      (xy -2.17644 -5.584661)
-      (xy -2.172704 -5.58598)
-      (xy -2.111401 -5.60838)
-      (xy -2.049592 -5.627671)
-      (xy -1.99658 -5.641193)
-      (xy -1.961672 -5.646289)
-      (xy -1.961577 -5.646289)
-      (xy -1.92239 -5.652393)
-      (xy -1.902369 -5.660123)
-      (xy -1.867231 -5.67423)
-      (xy -1.839662 -5.681683)
-      (xy -1.80021 -5.695375)
-      (xy -1.777502 -5.70848)
-      (xy -1.770085 -5.716277)
-      (xy -1.766017 -5.728494)
-      (xy -1.765924 -5.748648)
-      (xy -1.770433 -5.780261)
-      (xy -1.780169 -5.826851)
-      (xy -1.795758 -5.891939)
-      (xy -1.817827 -5.979043)
-      (xy -1.842785 -6.075469)
-      (xy -1.868105 -6.172334)
-      (xy -1.891105 -6.259327)
-      (xy -1.910708 -6.33246)
-      (xy -1.925839 -6.387745)
-      (xy -1.935422 -6.421193)
-      (xy -1.938271 -6.429503)
-      (xy -1.953795 -6.428908)
-      (xy -1.976602 -6.420615)
-      (xy -2.014665 -6.404586)
-      (xy -2.066904 -6.384848)
-      (xy -2.138142 -6.35964)
-      (xy -2.224511 -6.330137)
-      (xy -2.281418 -6.31076)
-      (xy -2.330378 -6.293832)
-      (xy -2.362117 -6.282564)
-      (xy -2.365128 -6.281444)
-      (xy -2.403551 -6.27156)
-      (xy -2.462995 -6.261784)
-      (xy -2.537575 -6.252549)
-      (xy -2.621401 -6.244286)
-      (xy -2.708588 -6.237428)
-      (xy -2.793249 -6.232406)
-      (xy -2.869495 -6.229653)
-      (xy -2.931439 -6.229601)
-      (xy -2.973196 -6.232681)
-      (xy -2.985531 -6.235918)
-      (xy -3.018457 -6.246218)
-      (xy -3.066437 -6.255291)
-      (xy -3.09042 -6.258288)
-      (xy -3.141082 -6.266669)
-      (xy -3.206612 -6.28185)
-      (xy -3.273966 -6.300764)
-      (xy -3.282844 -6.303549)
-      (xy -3.369947 -6.33672)
-      (xy -3.438679 -6.377165)
-      (xy -3.493232 -6.42965)
-      (xy -3.537794 -6.498942)
-      (xy -3.576554 -6.589805)
-      (xy -3.601723 -6.666305)
-      (xy -3.618642 -6.726988)
-      (xy -3.625397 -6.766894)
-      (xy -3.622792 -6.792748)
-      (xy -3.618021 -6.802843)
-      (xy -3.606387 -6.836038)
-      (xy -3.601112 -6.879852)
-      (xy -3.601084 -6.882943)
-      (xy -3.59835 -6.922274)
-      (xy -3.587756 -6.957159)
-      (xy -3.565712 -6.993347)
-      (xy -3.528631 -7.036587)
-      (xy -3.472923 -7.092628)
-      (xy -3.466009 -7.099332)
-      (xy -3.406141 -7.153862)
-      (xy -3.35815 -7.188995)
-      (xy -3.315998 -7.208898)
-      (xy -3.301194 -7.213113)
-      (xy -3.103595 -7.267332)
-      (xy -3.071917 -7.277214)
-      (xy -3.037978 -7.283442)
-      (xy -2.97959 -7.289218)
-      (xy -2.901905 -7.294198)
-      (xy -2.810077 -7.298036)
-      (xy -2.731474 -7.300023)
-      (xy -2.446539 -7.305237)
-      (xy -2.446539 -7.997986)
-      (xy -2.738875 -8.004521)
-      (xy -2.834501 -8.0073)
-      (xy -2.925002 -8.011106)
-      (xy -3.004285 -8.015595)
-      (xy -3.066255 -8.020419)
-      (xy -3.104818 -8.025234)
-      (xy -3.105222 -8.025311)
-      (xy -3.173086 -8.044642)
-      (xy -3.243384 -8.074892)
-      (xy -3.30675 -8.111156)
-      (xy -3.353818 -8.148526)
-      (xy -3.365071 -8.161441)
-      (xy -3.389976 -8.194121)
-      (xy -3.408499 -8.217415)
-      (xy -3.42217 -8.245563)
-      (xy -3.423462 -8.255159)
-      (xy -3.433134 -8.283216)
-      (xy -3.439014 -8.290579)
-      (xy -3.446012 -8.311497)
-      (xy -3.451683 -8.354445)
-      (xy -3.455186 -8.411849)
-      (xy -3.455849 -8.44211)
-      (xy -3.454891 -8.516995)
-      (xy -3.449585 -8.570687)
-      (xy -3.438781 -8.611423)
-      (xy -3.429195 -8.633044)
-      (xy -3.409073 -8.668578)
-      (xy -3.392725 -8.690618)
-      (xy -3.389304 -8.693217)
-      (xy -3.372246 -8.705153)
-      (xy -3.340937 -8.730388)
-      (xy -3.314563 -8.752776)
-      (xy -3.265125 -8.788449)
-      (xy -3.210506 -8.817644)
-      (xy -3.185901 -8.826954)
-      (xy -3.138628 -8.84226)
-      (xy -3.09892 -8.856901)
-      (xy -3.089306 -8.861024)
-      (xy -3.058864 -8.867036)
-      (xy -3.006941 -8.869454)
-      (xy -2.941398 -8.868594)
-      (xy -2.870097 -8.864768)
-      (xy -2.800901 -8.85829)
-      (xy -2.741673 -8.849475)
-      (xy -2.727774 -8.846592)
-      (xy -2.677238 -8.835214)
-      (xy -2.613145 -8.820827)
-      (xy -2.559824 -8.808883)
-      (xy -2.505133 -8.794483)
-      (xy -2.459803 -8.77867)
-      (xy -2.434008 -8.765104)
-      (xy -2.403058 -8.745787)
-      (xy -2.361642 -8.727928)
-      (xy -2.359554 -8.727216)
-      (xy -2.317866 -8.709558)
-      (xy -2.266313 -8.682893)
-      (xy -2.237217 -8.665913)
-      (xy -2.195384 -8.641627)
-      (xy -2.162998 -8.625456)
-      (xy -2.150349 -8.62139)
-      (xy -2.140112 -8.633975)
-      (xy -2.119366 -8.668698)
-      (xy -2.09042 -8.721012)
-      (xy -2.055585 -8.786373)
-      (xy -2.017169 -8.860233)
-      (xy -1.977483 -8.938047)
-      (xy -1.938836 -9.015268)
-      (xy -1.903537 -9.08735)
-      (xy -1.873896 -9.149747)
-      (xy -1.852223 -9.197912)
-      (xy -1.840828 -9.227299)
-      (xy -1.839662 -9.232946)
-      (xy -1.851331 -9.259586)
-      (xy -1.879111 -9.288808)
-      (xy -1.912164 -9.310943)
-      (xy -1.93398 -9.317078)
-      (xy -1.961386 -9.32401)
-      (xy -2.002308 -9.34166)
-      (xy -2.026063 -9.354082)
-      (xy -2.067729 -9.375412)
-      (xy -2.10051 -9.388785)
-      (xy -2.111146 -9.391087)
-      (xy -2.134116 -9.399331)
-      (xy -2.168553 -9.419913)
-      (xy -2.180105 -9.428092)
-      (xy -2.219233 -9.451659)
-      (xy -2.254333 -9.464375)
-      (xy -2.261431 -9.465096)
-      (xy -2.293407 -9.470924)
-      (xy -2.306661 -9.478339)
-      (xy -2.324666 -9.488011)
-      (xy -2.362086 -9.500041)
-      (xy -2.421969 -9.515265)
-      (xy -2.507361 -9.534516)
-      (xy -2.527949 -9.538962)
-      (xy -2.583813 -9.552619)
-      (xy -2.641128 -9.568979)
-      (xy -2.646364 -9.570633)
-      (xy -2.686683 -9.578183)
-      (xy -2.750581 -9.583827)
-      (xy -2.83209 -9.58755)
-      (xy -2.925245 -9.589339)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 848af073-6c5e-4918-8c43-ade8c5263fd0))
-  (fp_poly
-    (pts
-      (xy -0.134496 -9.589614)
-      (xy -0.267032 -9.583607)
-      (xy -0.395127 -9.573942)
-      (xy -0.512111 -9.560895)
-      (xy -0.611311 -9.544746)
-      (xy -0.670315 -9.530682)
-      (xy -0.722609 -9.51608)
-      (xy -0.768714 -9.504171)
-      (xy -0.78873 -9.499601)
-      (xy -0.866531 -9.47956)
-      (xy -0.947549 -9.451617)
-      (xy -1.017475 -9.420875)
-      (xy -1.03296 -9.412548)
-      (xy -1.086677 -9.386177)
-      (xy -1.144213 -9.363816)
-      (xy -1.155076 -9.360422)
-      (xy -1.192923 -9.348535)
-      (xy -1.215346 -9.339945)
-      (xy -1.217984 -9.338041)
-      (xy -1.213178 -9.322596)
-      (xy -1.19986 -9.283988)
-      (xy -1.179675 -9.226772)
-      (xy -1.154271 -9.155504)
-      (xy -1.125294 -9.074737)
-      (xy -1.094391 -8.989026)
-      (xy -1.063209 -8.902928)
-      (xy -1.033394 -8.820995)
-      (xy -1.006593 -8.747785)
-      (xy -0.984453 -8.68785)
-      (xy -0.96862 -8.645746)
-      (xy -0.960742 -8.626028)
-      (xy -0.960256 -8.625162)
-      (xy -0.944204 -8.627955)
-      (xy -0.904812 -8.641833)
-      (xy -0.845583 -8.665403)
-      (xy -0.770023 -8.697274)
-      (xy -0.68645 -8.733907)
-      (xy -0.638951 -8.751497)
-      (xy -0.582951 -8.767564)
-      (xy -0.568035 -8.771022)
-      (xy -0.510633 -8.783546)
-      (xy -0.453043 -8.796347)
-      (xy -0.440886 -8.799092)
-      (xy -0.389412 -8.807297)
-      (xy -0.328195 -8.812416)
-      (xy -0.303122 -8.81317)
-      (xy -0.241231 -8.817111)
-      (xy -0.177906 -8.826272)
-      (xy -0.156746 -8.830892)
-      (xy -0.10704 -8.840183)
-      (xy -0.074461 -8.837074)
-      (xy -0.061581 -8.830892)
-      (xy -0.032299 -8.821582)
-      (xy 0.014754 -8.81538)
-      (xy 0.054102 -8.813814)
-      (xy 0.105478 -8.809556)
-      (xy 0.165792 -8.79827)
-      (xy 0.227597 -8.782191)
-      (xy 0.283444 -8.763552)
-      (xy 0.325885 -8.744586)
-      (xy 0.347473 -8.727527)
-      (xy 0.34836 -8.725565)
-      (xy 0.365512 -8.711489)
-      (xy 0.374237 -8.710201)
-      (xy 0.390853 -8.697881)
-      (xy 0.41462 -8.665551)
-      (xy 0.440448 -8.620153)
-      (xy 0.440929 -8.619204)
-      (xy 0.467452 -8.560962)
-      (xy 0.479653 -8.516133)
-      (xy 0.480276 -8.473945)
-      (xy 0.479577 -8.467485)
-      (xy 0.466731 -8.386451)
-      (xy 0.450153 -8.33134)
-      (xy 0.428517 -8.298566)
-      (xy 0.413353 -8.288481)
-      (xy 0.384639 -8.268201)
-      (xy 0.373101 -8.250978)
-      (xy 0.356209 -8.228842)
-      (xy 0.324067 -8.204)
-      (xy 0.317729 -8.200154)
-      (xy 0.284439 -8.179723)
-      (xy 0.263861 -8.165117)
-      (xy 0.262203 -8.163497)
-      (xy 0.243978 -8.151142)
-      (xy 0.208095 -8.131793)
-      (xy 0.163882 -8.109951)
-      (xy 0.120668 -8.090113)
-      (xy 0.087781 -8.076779)
-      (xy 0.076037 -8.073721)
-      (xy 0.055041 -8.06768)
-      (xy 0.017079 -8.052085)
-      (xy -0.01619 -8.036716)
-      (xy -0.061259 -8.016411)
-      (xy -0.097 -8.002876)
-      (xy -0.111472 -7.999489)
-      (xy -0.141289 -7.993517)
-      (xy -0.185725 -7.978926)
-      (xy -0.232771 -7.960037)
-      (xy -0.265359 -7.944103)
-      (xy -0.29546 -7.92973)
-      (xy -0.342621 -7.90977)
-      (xy -0.391175 -7.89065)
-      (xy -0.47888 -7.856307)
-      (xy -0.565689 -7.820449)
-      (xy -0.646022 -7.785553)
-      (xy -0.714298 -7.754096)
-      (xy -0.764937 -7.728556)
-      (xy -0.789134 -7.713953)
-      (xy -0.82215 -7.691299)
-      (xy -0.868455 -7.661235)
-      (xy -0.902409 -7.639943)
-      (xy -0.983882 -7.586438)
-      (xy -1.057025 -7.532226)
-      (xy -1.11683 -7.481421)
-      (xy -1.158291 -7.438135)
-      (xy -1.171538 -7.41888)
-      (xy -1.199035 -7.373834)
-      (xy -1.226273 -7.335463)
-      (xy -1.253441 -7.294738)
-      (xy -1.282282 -7.242067)
-      (xy -1.308546 -7.186505)
-      (xy -1.327981 -7.137106)
-      (xy -1.336336 -7.102926)
-      (xy -1.336399 -7.100905)
-      (xy -1.342107 -7.0695)
-      (xy -1.356497 -7.025353)
-      (xy -1.36423 -7.006168)
-      (xy -1.380323 -6.951409)
-      (xy -1.392614 -6.875617)
-      (xy -1.400531 -6.787187)
-      (xy -1.403504 -6.694514)
-      (xy -1.40096 -6.605991)
-      (xy -1.395336 -6.549129)
-      (xy -1.381531 -6.455289)
-      (xy -1.368321 -6.382542)
-      (xy -1.353302 -6.322528)
-      (xy -1.334067 -6.266888)
-      (xy -1.308214 -6.207264)
-      (xy -1.280359 -6.149479)
-      (xy -1.231161 -6.05687)
-      (xy -1.182157 -5.981577)
-      (xy -1.125725 -5.912363)
-      (xy -1.102099 -5.886746)
-      (xy -1.057895 -5.841339)
-      (xy -1.020537 -5.805391)
-      (xy -0.995011 -5.783565)
-      (xy -0.987156 -5.779163)
-      (xy -0.968157 -5.771281)
-      (xy -0.934095 -5.751392)
-      (xy -0.909391 -5.735277)
-      (xy -0.840121 -5.696711)
-      (xy -0.747779 -5.657641)
-      (xy -0.638798 -5.619993)
-      (xy -0.51961 -5.585692)
-      (xy -0.396648 -5.556664)
-      (xy -0.276342 -5.534834)
-      (xy -0.211457 -5.526353)
-      (xy -0.136344 -5.519521)
-      (xy -0.049287 -5.513804)
-      (xy 0.044175 -5.509325)
-      (xy 0.138504 -5.506207)
-      (xy 0.22816 -5.504572)
-      (xy 0.307606 -5.504544)
-      (xy 0.371302 -5.506244)
-      (xy 0.413711 -5.509797)
-      (xy 0.425023 -5.512244)
-      (xy 0.460889 -5.519685)
-      (xy 0.512149 -5.524926)
-      (xy 0.544672 -5.526325)
-      (xy 0.592084 -5.528991)
-      (xy 0.626847 -5.534299)
-      (xy 0.63836 -5.538902)
-      (xy 0.657157 -5.545916)
-      (xy 0.697883 -5.555131)
-      (xy 0.753107 -5.564957)
-      (xy 0.777744 -5.568725)
-      (xy 0.866621 -5.581904)
-      (xy 0.930634 -5.592028)
-      (xy 0.974263 -5.59997)
-      (xy 1.001987 -5.606599)
-      (xy 1.018285 -5.612787)
-      (xy 1.024499 -5.616692)
-      (xy 1.047274 -5.625802)
-      (xy 1.087244 -5.635381)
-      (xy 1.105909 -5.638702)
-      (xy 1.157165 -5.651915)
-      (xy 1.217323 -5.674438)
-      (xy 1.253928 -5.69156)
-      (xy 1.304565 -5.716014)
-      (xy 1.350672 -5.735254)
-      (xy 1.374954 -5.743137)
-      (xy 1.414934 -5.760648)
-      (xy 1.43971 -5.780271)
-      (xy 1.44713 -5.790341)
-      (xy 1.450908 -5.803201)
-      (xy 1.450086 -5.822401)
-      (xy 1.443704 -5.851487)
-      (xy 1.430802 -5.894008)
-      (xy 1.410422 -5.953511)
-      (xy 1.381603 -6.033545)
-      (xy 1.343388 -6.137657)
-      (xy 1.342205 -6.140866)
-      (xy 1.307307 -6.235055)
-      (xy 1.275299 -6.320477)
-      (xy 1.247744 -6.393035)
-      (xy 1.226207 -6.448635)
-      (xy 1.212251 -6.483183)
-      (xy 1.207988 -6.492404)
-      (xy 1.194106 -6.50115)
-      (xy 1.168001 -6.494096)
-      (xy 1.140061 -6.479769)
-      (xy 1.102099 -6.462138)
-      (xy 1.044609 -6.439569)
-      (xy 0.976481 -6.415424)
-      (xy 0.928287 -6.399716)
-      (xy 0.865092 -6.379025)
-      (xy 0.813321 -6.360386)
-      (xy 0.778956 -6.346064)
-      (xy 0.767933 -6.339062)
-      (xy 0.751334 -6.330951)
-      (xy 0.71744 -6.327142)
-      (xy 0.7133 -6.327101)
-      (xy 0.677306 -6.323676)
-      (xy 0.656461 -6.315337)
-      (xy 0.655758 -6.314413)
-      (xy 0.636534 -6.306258)
-      (xy 0.592533 -6.298818)
-      (xy 0.528577 -6.292242)
-      (xy 0.449487 -6.286682)
-      (xy 0.360086 -6.28229)
-      (xy 0.265195 -6.279218)
-      (xy 0.169636 -6.277617)
-      (xy 0.078231 -6.277638)
-      (xy -0.0042 -6.279433)
-      (xy -0.072833 -6.283153)
-      (xy -0.122848 -6.28895)
-      (xy -0.127424 -6.289803)
-      (xy -0.175901 -6.304031)
-      (xy -0.230889 -6.326581)
-      (xy -0.250323 -6.336247)
-      (xy -0.291331 -6.356584)
-      (xy -0.322332 -6.369324)
-      (xy -0.331611 -6.371507)
-      (xy -0.350828 -6.382727)
-      (xy -0.379408 -6.411344)
-      (xy -0.410801 -6.449789)
-      (xy -0.438458 -6.490493)
-      (xy -0.445865 -6.503537)
-      (xy -0.458122 -6.543621)
-      (xy -0.465073 -6.601206)
-      (xy -0.466752 -6.666425)
-      (xy -0.463194 -6.72941)
-      (xy -0.454435 -6.780294)
-      (xy -0.444803 -6.804087)
-      (xy -0.379553 -6.886621)
-      (xy -0.296629 -6.960811)
-      (xy -0.19167 -7.030126)
-      (xy -0.098436 -7.079739)
-      (xy -0.018209 -7.117492)
-      (xy 0.066753 -7.15454)
-      (xy 0.145778 -7.186384)
-      (xy 0.202995 -7.206869)
-      (xy 0.26962 -7.229369)
-      (xy 0.33423 -7.252858)
-      (xy 0.385174 -7.273062)
-      (xy 0.394626 -7.277197)
-      (xy 0.439825 -7.296128)
-      (xy 0.501656 -7.320124)
-      (xy 0.568701 -7.34479)
-      (xy 0.587051 -7.351287)
-      (xy 0.647428 -7.374164)
-      (xy 0.699736 -7.397074)
-      (xy 0.735562 -7.416216)
-      (xy 0.743263 -7.421852)
-      (xy 0.770419 -7.441115)
-      (xy 0.815259 -7.468195)
-      (xy 0.86893 -7.497793)
-      (xy 0.878835 -7.502974)
-      (xy 0.968922 -7.560672)
-      (xy 1.06166 -7.639349)
-      (xy 1.150284 -7.731915)
-      (xy 1.228027 -7.831283)
-      (xy 1.288126 -7.930365)
-      (xy 1.289686 -7.933458)
-      (xy 1.321807 -8.001023)
-      (xy 1.344915 -8.060234)
-      (xy 1.361663 -8.120615)
-      (xy 1.374704 -8.191693)
-      (xy 1.386447 -8.280947)
-      (xy 1.394226 -8.338671)
-      (xy 1.402478 -8.387329)
-      (xy 1.40954 -8.417231)
-      (xy 1.410135 -8.418863)
-      (xy 1.412309 -8.452896)
-      (xy 1.404922 -8.47807)
-      (xy 1.397068 -8.496271)
-      (xy 1.390232 -8.518785)
-      (xy 1.3833 -8.551187)
-      (xy 1.375157 -8.599054)
-      (xy 1.364689 -8.66796)
-      (xy 1.358407 -8.710869)
-      (xy 1.344868 -8.785845)
-      (xy 1.328676 -8.847111)
-      (xy 1.311625 -8.888695)
-      (xy 1.300952 -8.902324)
-      (xy 1.289742 -8.91902)
-      (xy 1.271194 -8.954478)
-      (xy 1.253772 -8.991351)
-      (xy 1.220229 -9.048965)
-      (xy 1.1698 -9.115921)
-      (xy 1.108942 -9.185321)
-      (xy 1.044111 -9.250272)
-      (xy 0.981763 -9.303878)
-      (xy 0.928355 -9.339244)
-      (xy 0.927712 -9.339572)
-      (xy 0.884575 -9.363887)
-      (xy 0.851165 -9.387065)
-      (xy 0.841223 -9.396382)
-      (xy 0.814016 -9.415321)
-      (xy 0.775545 -9.428981)
-      (xy 0.728495 -9.445183)
-      (xy 0.690957 -9.465666)
-      (xy 0.650809 -9.486084)
-      (xy 0.60157 -9.501403)
-      (xy 0.594745 -9.50276)
-      (xy 0.553651 -9.512157)
-      (xy 0.524999 -9.522234)
-      (xy 0.521235 -9.52448)
-      (xy 0.497453 -9.534243)
-      (xy 0.459147 -9.543249)
-      (xy 0.454627 -9.544016)
-      (xy 0.412014 -9.551469)
-      (xy 0.354434 -9.562198)
-      (xy 0.306608 -9.571473)
-      (xy 0.223032 -9.58289)
-      (xy 0.117207 -9.589534)
-      (xy -0.004193 -9.591682)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp c30c42e2-406e-4759-929e-56a50e9f582c))
-  (fp_poly
-    (pts
-      (xy 4.080492 -3.184625)
-      (xy 4.016617 -3.135997)
-      (xy 3.981952 -3.086084)
-      (xy 3.97212 -3.066614)
-      (xy 3.964387 -3.047234)
-      (xy 3.958501 -3.024286)
-      (xy 3.95421 -2.994111)
-      (xy 3.951262 -2.953051)
-      (xy 3.949405 -2.897449)
-      (xy 3.948389 -2.823646)
-      (xy 3.94796 -2.727984)
-      (xy 3.947867 -2.606805)
-      (xy 3.947867 -2.590772)
-      (xy 3.94803 -2.456547)
-      (xy 3.948987 -2.348464)
-      (xy 3.951441 -2.263058)
-      (xy 3.956097 -2.196868)
-      (xy 3.963658 -2.14643)
-      (xy 3.974827 -2.108282)
-      (xy 3.990308 -2.07896)
-      (xy 4.010805 -2.055002)
-      (xy 4.03702 -2.032945)
-      (xy 4.06538 -2.012358)
-      (xy 4.128024 -1.967952)
-      (xy 5.329408 -1.964394)
-      (xy 5.546433 -1.963776)
-      (xy 5.735847 -1.963316)
-      (xy 5.899647 -1.963054)
-      (xy 6.039824 -1.963028)
-      (xy 6.158374 -1.963276)
-      (xy 6.257291 -1.963837)
-      (xy 6.338567 -1.964749)
-      (xy 6.404198 -1.966051)
-      (xy 6.456177 -1.96778)
-      (xy 6.496498 -1.969975)
-      (xy 6.527155 -1.972675)
-      (xy 6.550142 -1.975917)
-      (xy 6.567453 -1.979741)
-      (xy 6.581082 -1.984185)
-      (xy 6.591718 -1.988687)
-      (xy 6.640031 -2.019064)
-      (xy 6.685266 -2.060394)
-      (xy 6.695331 -2.072474)
-      (xy 6.738019 -2.128412)
-      (xy 6.739185 -2.249177)
-      (xy 6.254171 -2.249177)
-      (xy 6.242336 -2.242491)
-      (xy 6.220827 -2.241786)
-      (xy 6.189485 -2.236329)
-      (xy 6.175548 -2.226985)
-      (xy 6.157294 -2.219826)
-      (xy 6.117536 -2.214571)
-      (xy 6.064359 -2.212222)
-      (xy 6.056259 -2.212183)
-      (xy 6.000647 -2.214033)
-      (xy 5.961923 -2.219035)
-      (xy 5.9462 -2.226368)
-      (xy 5.946119 -2.226985)
-      (xy 5.93366 -2.238818)
-      (xy 5.915053 -2.241786)
-      (xy 5.883686 -2.253359)
-      (xy 5.847817 -2.281852)
-      (xy 5.816613 -2.317928)
-      (xy 5.799243 -2.352249)
-      (xy 5.7981 -2.360893)
-      (xy 5.79093 -2.388574)
-      (xy 5.783298 -2.397206)
-      (xy 5.770864 -2.418084)
-      (xy 5.768496 -2.435084)
-      (xy 5.774863 -2.458658)
-      (xy 5.783298 -2.463814)
-      (xy 5.794681 -2.476409)
-      (xy 5.7981 -2.498554)
-      (xy 5.807176 -2.533533)
-      (xy 5.82903 -2.568522)
-      (xy 5.855602 -2.592505)
-      (xy 5.870145 -2.597031)
-      (xy 5.885371 -2.60199)
-      (xy 5.878205 -2.618642)
-      (xy 5.85093 -2.646593)
-      (xy 5.825792 -2.677326)
-      (xy 5.8128 -2.716066)
-      (xy 5.809655 -2.771535)
-      (xy 5.8106 -2.799559)
-      (xy 5.820558 -2.839592)
-      (xy 5.841749 -2.855823)
-      (xy 5.870163 -2.876733)
-      (xy 5.879751 -2.893826)
-      (xy 5.899538 -2.917478)
-      (xy 5.917512 -2.922672)
-      (xy 5.68298 -2.922672)
-      (xy 5.672695 -2.867165)
-      (xy 5.662814 -2.830117)
-      (xy 5.651321 -2.808391)
-      (xy 5.648845 -2.806724)
-      (xy 5.637405 -2.789797)
-      (xy 5.63528 -2.774294)
-      (xy 5.628192 -2.746473)
-      (xy 5.620478 -2.737649)
-      (xy 5.60902 -2.717246)
-      (xy 5.605676 -2.69237)
-      (xy 5.601082 -2.664964)
-      (xy 5.592555 -2.656239)
-      (xy 5.582768 -2.643063)
-      (xy 5.57307 -2.609714)
-      (xy 5.569445 -2.58963)
-      (xy 5.560749 -2.549975)
-      (xy 5.550215 -2.526131)
-      (xy 5.545561 -2.523022)
-      (xy 5.53323 -2.511019)
-      (xy 5.531667 -2.500819)
-      (xy 5.523674 -2.481121)
-      (xy 5.516865 -2.478616)
-      (xy 5.505416 -2.466041)
-      (xy 5.502063 -2.444441)
-      (xy 5.493107 -2.404997)
-      (xy 5.480331 -2.381533)
-      (xy 5.46283 -2.348348)
-      (xy 5.458128 -2.326897)
-      (xy 5.450734 -2.304917)
-      (xy 5.442855 -2.300994)
-      (xy 5.429825 -2.288962)
-      (xy 5.428053 -2.278166)
-      (xy 5.415144 -2.24143)
-      (xy 5.377723 -2.219229)
-      (xy 5.328141 -2.212746)
-      (xy 5.28465 -2.215936)
-      (xy 5.266351 -2.227296)
-      (xy 5.265233 -2.232987)
-      (xy 5.258729 -2.257708)
-      (xy 5.249877 -2.278546)
-      (xy 4.939391 -2.278546)
-      (xy 4.933255 -2.251809)
-      (xy 4.910361 -2.242095)
-      (xy 4.902587 -2.241786)
-      (xy 4.87477 -2.23672)
-      (xy 4.865583 -2.226985)
-      (xy 4.851734 -2.219654)
-      (xy 4.813924 -2.214503)
-      (xy 4.757761 -2.212232)
-      (xy 4.747168 -2.212183)
-      (xy 4.688526 -2.213914)
-      (xy 4.647317 -2.21864)
-      (xy 4.629147 -2.22566)
-      (xy 4.628753 -2.226985)
-      (xy 4.616535 -2.239545)
-      (xy 4.60285 -2.241804)
-      (xy 4.575358 -2.251013)
-      (xy 4.540192 -2.273761)
-      (xy 4.532541 -2.280044)
-      (xy 4.51004 -2.30128)
-      (xy 4.496789 -2.322487)
-      (xy 4.490351 -2.352047)
-      (xy 4.488288 -2.398344)
-      (xy 4.488135 -2.432809)
-      (xy 4.489912 -2.497877)
-      (xy 4.496023 -2.540082)
-      (xy 4.507639 -2.565996)
-      (xy 4.512981 -2.572192)
-      (xy 4.53862 -2.59173)
-      (xy 4.553686 -2.597031)
-      (xy 4.568447 -2.605028)
-      (xy 4.559771 -2.629439)
-      (xy 4.532559 -2.665038)
-      (xy 4.501028 -2.7219)
-      (xy 4.495572 -2.759852)
-      (xy 4.509993 -2.820785)
-      (xy 4.532559 -2.854666)
-      (xy 4.556505 -2.885502)
-      (xy 4.569018 -2.907457)
-      (xy 4.569545 -2.910173)
-      (xy 4.581924 -2.920435)
-      (xy 4.598275 -2.922672)
-      (xy 4.626611 -2.929469)
-      (xy 4.636154 -2.937474)
-      (xy 4.655145 -2.946107)
-      (xy 4.69318 -2.951441)
-      (xy 4.717564 -2.952276)
-      (xy 4.76144 -2.949479)
-      (xy 4.791878 -2.942363)
-      (xy 4.798974 -2.937474)
-      (xy 4.819627 -2.925355)
-      (xy 4.840553 -2.922201)
-      (xy 4.879148 -2.912862)
-      (xy 4.899939 -2.901298)
-      (xy 4.916936 -2.885038)
-      (xy 4.917703 -2.866716)
-      (xy 4.90348 -2.835587)
-      (xy 4.884851 -2.805774)
-      (xy 4.865913 -2.798138)
-      (xy 4.842257 -2.804684)
-      (xy 4.799662 -2.814513)
-      (xy 4.747415 -2.818348)
-      (xy 4.697896 -2.816083)
-      (xy 4.663483 -2.807614)
-      (xy 4.661033 -2.806224)
-      (xy 4.647906 -2.781703)
-      (xy 4.646231 -2.736142)
-      (xy 4.650956 -2.678441)
-      (xy 4.736066 -2.674002)
-      (xy 4.821177 -2.669563)
-      (xy 4.821177 -2.552626)
-      (xy 4.754569 -2.552626)
-      (xy 4.714845 -2.549686)
-      (xy 4.691017 -2.542247)
-      (xy 4.68796 -2.537824)
-      (xy 4.676558 -2.523621)
-      (xy 4.672101 -2.523022)
-      (xy 4.640587 -2.510724)
-      (xy 4.621587 -2.479513)
-      (xy 4.616501 -2.437915)
-      (xy 4.626729 -2.394454)
-      (xy 4.646135 -2.364856)
-      (xy 4.671282 -2.344283)
-      (xy 4.703499 -2.333882)
-      (xy 4.753087 -2.33065)
-      (xy 4.763676 -2.330598)
-      (xy 4.811426 -2.332978)
-      (xy 4.846227 -2.339131)
-      (xy 4.858182 -2.345399)
-      (xy 4.881016 -2.360152)
-      (xy 4.908788 -2.354425)
-      (xy 4.928761 -2.331488)
-      (xy 4.930263 -2.326897)
-      (xy 4.939391 -2.278546)
-      (xy 5.249877 -2.278546)
-      (xy 5.242618 -2.295635)
-      (xy 5.222006 -2.336627)
-      (xy 5.201996 -2.370548)
-      (xy 5.187692 -2.38726)
-      (xy 5.187523 -2.387338)
-      (xy 5.17824 -2.40428)
-      (xy 5.176422 -2.420541)
-      (xy 5.171056 -2.450568)
-      (xy 5.157763 -2.490093)
-      (xy 5.140749 -2.52926)
-      (xy 5.124223 -2.558212)
-      (xy 5.113723 -2.567427)
-      (xy 5.105481 -2.580217)
-      (xy 5.102321 -2.608133)
-      (xy 5.095184 -2.651461)
-      (xy 5.080118 -2.691235)
-      (xy 5.064498 -2.727215)
-      (xy 5.058007 -2.754143)
-      (xy 5.049446 -2.772729)
-      (xy 5.043205 -2.774654)
-      (xy 5.032078 -2.787321)
-      (xy 5.028403 -2.811658)
-      (xy 5.023336 -2.839475)
-      (xy 5.013601 -2.848663)
-      (xy 5.002474 -2.86133)
-      (xy 4.998799 -2.885668)
-      (xy 5.00145 -2.908246)
-      (xy 5.01462 -2.919111)
-      (xy 5.046137 -2.922479)
-      (xy 5.067476 -2.922672)
-      (xy 5.127404 -2.914056)
-      (xy 5.163477 -2.888082)
-      (xy 5.175951 -2.844962)
-      (xy 5.182453 -2.822971)
-      (xy 5.189317 -2.819059)
-      (xy 5.198422 -2.80579)
-      (xy 5.207594 -2.77185)
-      (xy 5.212029 -2.74505)
-      (xy 5.220186 -2.702886)
-      (xy 5.230298 -2.676084)
-      (xy 5.236139 -2.67104)
-      (xy 5.247868 -2.658677)
-      (xy 5.250431 -2.64231)
-      (xy 5.257228 -2.613974)
-      (xy 5.265233 -2.604432)
-      (xy 5.275897 -2.584422)
-      (xy 5.280035 -2.551752)
-      (xy 5.284056 -2.520948)
-      (xy 5.293661 -2.50822)
-      (xy 5.305999 -2.49546)
-      (xy 5.316847 -2.464678)
-      (xy 5.31704 -2.463814)
-      (xy 5.329385 -2.430071)
-      (xy 5.342917 -2.420714)
-      (xy 5.352422 -2.436787)
-      (xy 5.354044 -2.456413)
-      (xy 5.359111 -2.484231)
-      (xy 5.368846 -2.493418)
-      (xy 5.381945 -2.505421)
-      (xy 5.383648 -2.515822)
-      (xy 5.390087 -2.547072)
-      (xy 5.39845 -2.567628)
-      (xy 5.418005 -2.606524)
-      (xy 5.427775 -2.625988)
-      (xy 5.439564 -2.659397)
-      (xy 5.450187 -2.705042)
-      (xy 5.45187 -2.7148)
-      (xy 5.460647 -2.752041)
-      (xy 5.471057 -2.772982)
-      (xy 5.474351 -2.774654)
-      (xy 5.484144 -2.787305)
-      (xy 5.487261 -2.810785)
-      (xy 5.492719 -2.842126)
-      (xy 5.502063 -2.856064)
-      (xy 5.514497 -2.876941)
-      (xy 5.516865 -2.893942)
-      (xy 5.520582 -2.910451)
-      (xy 5.536336 -2.919126)
-      (xy 5.571027 -2.922354)
-      (xy 5.599922 -2.922672)
-      (xy 5.68298 -2.922672)
-      (xy 5.917512 -2.922672)
-      (xy 5.941018 -2.929064)
-      (xy 5.946119 -2.937474)
-      (xy 5.959502 -2.94558)
-      (xy 5.994025 -2.950956)
-      (xy 6.027529 -2.952276)
-      (xy 6.072112 -2.949843)
-      (xy 6.101682 -2.943566)
-      (xy 6.108939 -2.937474)
-      (xy 6.121606 -2.926347)
-      (xy 6.145944 -2.922672)
-      (xy 6.173761 -2.917605)
-      (xy 6.182949 -2.90787)
-      (xy 6.195346 -2.895844)
-      (xy 6.212552 -2.893068)
-      (xy 6.23473 -2.890915)
-      (xy 6.240143 -2.879865)
-      (xy 6.229671 -2.853032)
-      (xy 6.220088 -2.834121)
-      (xy 6.202108 -2.805786)
-      (xy 6.181437 -2.798439)
-      (xy 6.149876 -2.805252)
-      (xy 6.076254 -2.818568)
-      (xy 6.01388 -2.81463)
-      (xy 5.969 -2.794)
-      (xy 5.963143 -2.788431)
-      (xy 5.944763 -2.764286)
-      (xy 5.944357 -2.741713)
-      (xy 5.956249 -2.714421)
-      (xy 5.971505 -2.689171)
-      (xy 5.990942 -2.676239)
-      (xy 6.024099 -2.671569)
-      (xy 6.058217 -2.67104)
-      (xy 6.138543 -2.67104)
-      (xy 6.138543 -2.552626)
-      (xy 6.071935 -2.552626)
-      (xy 6.032211 -2.549686)
-      (xy 6.008383 -2.542247)
-      (xy 6.005326 -2.537824)
-      (xy 5.993818 -2.523772)
-      (xy 5.98856 -2.523022)
-      (xy 5.9589 -2.509963)
-      (xy 5.935298 -2.477761)
-      (xy 5.923775 -2.436876)
-      (xy 5.925104 -2.412819)
-      (xy 5.932353 -2.381509)
-      (xy 5.936657 -2.367641)
-      (xy 5.936746 -2.367602)
-      (xy 5.949446 -2.361329)
-      (xy 5.971821 -2.3491)
-      (xy 6.002083 -2.339275)
-      (xy 6.045249 -2.333166)
-      (xy 6.092298 -2.330945)
-      (xy 6.13421 -2.332781)
-      (xy 6.161964 -2.338844)
-      (xy 6.168147 -2.345399)
-      (xy 6.175992 -2.361446)
-      (xy 6.194701 -2.357999)
-      (xy 6.217028 -2.338987)
-      (xy 6.23551 -2.30887)
-      (xy 6.251378 -2.268937)
-      (xy 6.254171 -2.249177)
-      (xy 6.739185 -2.249177)
-      (xy 6.742319 -2.573887)
-      (xy 6.743491 -2.700394)
-      (xy 6.74415 -2.800878)
-      (xy 6.744083 -2.878917)
-      (xy 6.743077 -2.93809)
-      (xy 6.740919 -2.981977)
-      (xy 6.737397 -3.014154)
-      (xy 6.732297 -3.038203)
-      (xy 6.725407 -3.0577)
-      (xy 6.716515 -3.076225)
-      (xy 6.711934 -3.084951)
-      (xy 6.664229 -3.148571)
-      (xy 6.612794 -3.184625)
-      (xy 6.548339 -3.218709)
-      (xy 4.144947 -3.218709)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp cdb2643c-1fac-431b-8554-235257416261))
-  (fp_poly
-    (pts
-      (xy 7.326526 -12.084969)
-      (xy 7.211943 -12.084696)
-      (xy 7.12117 -12.08406)
-      (xy 7.05131 -12.082913)
-      (xy 6.999465 -12.081106)
-      (xy 6.962738 -12.078491)
-      (xy 6.938233 -12.074919)
-      (xy 6.923053 -12.070242)
-      (xy 6.9143 -12.064312)
-      (xy 6.909077 -12.056981)
-      (xy 6.908761 -12.056396)
-      (xy 6.90414 -12.03258)
-      (xy 6.900277 -11.980902)
-      (xy 6.897223 -11.903093)
-      (xy 6.895033 -11.800885)
-      (xy 6.89376 -11.676012)
-      (xy 6.893438 -11.560533)
-      (xy 6.893438 -11.093302)
-      (xy 5.043205 -11.093302)
-      (xy 5.043205 -11.571402)
-      (xy 5.04288 -11.714606)
-      (xy 5.041855 -11.830285)
-      (xy 5.040056 -11.920511)
-      (xy 5.037409 -11.987355)
-      (xy 5.03384 -12.032891)
-      (xy 5.029274 -12.05919)
-      (xy 5.025443 -12.067264)
-      (xy 5.017505 -12.068959)
-      (xy 4.996691 -12.070551)
-      (xy 4.96226 -12.072044)
-      (xy 4.913474 -12.07344)
-      (xy 4.849592 -12.074742)
-      (xy 4.769875 -12.075952)
-      (xy 4.673583 -12.077073)
-      (xy 4.559975 -12.078108)
-      (xy 4.428313 -12.079058)
-      (xy 4.277856 -12.079928)
-      (xy 4.107864 -12.080719)
-      (xy 3.917598 -12.081433)
-      (xy 3.706319 -12.082074)
-      (xy 3.473285 -12.082645)
-      (xy 3.217757 -12.083147)
-      (xy 2.938996 -12.083583)
-      (xy 2.636262 -12.083956)
-      (xy 2.308814 -12.084269)
-      (xy 1.955914 -12.084524)
-      (xy 1.576821 -12.084724)
-      (xy 1.170795 -12.084871)
-      (xy 0.737097 -12.084969)
-      (xy 0.274987 -12.085018)
-      (xy -0.021472 -12.085026)
-      (xy -0.479456 -12.085024)
-      (xy -0.908766 -12.085014)
-      (xy -1.310332 -12.084992)
-      (xy -1.685084 -12.08495)
-      (xy -2.033951 -12.084885)
-      (xy -2.357864 -12.084792)
-      (xy -2.657752 -12.084664)
-      (xy -2.934545 -12.084497)
-      (xy -3.189173 -12.084285)
-      (xy -3.422566 -12.084023)
-      (xy -3.635654 -12.083705)
-      (xy -3.829366 -12.083327)
-      (xy -4.004632 -12.082884)
-      (xy -4.162383 -12.082369)
-      (xy -4.303547 -12.081778)
-      (xy -4.429056 -12.081105)
-      (xy -4.539838 -12.080346)
-      (xy -4.636823 -12.079494)
-      (xy -4.720942 -12.078544)
-      (xy -4.793124 -12.077492)
-      (xy -4.854299 -12.076332)
-      (xy -4.905396 -12.075059)
-      (xy -4.947347 -12.073667)
-      (xy -4.98108 -12.072151)
-      (xy -5.007525 -12.070506)
-      (xy -5.027612 -12.068726)
-      (xy -5.042272 -12.066807)
-      (xy -5.052433 -12.064743)
-      (xy -5.059026 -12.062528)
-      (xy -5.06298 -12.060158)
-      (xy -5.065226 -12.057628)
-      (xy -5.065948 -12.056396)
-      (xy -5.070568 -12.03258)
-      (xy -5.074432 -11.980902)
-      (xy -5.077486 -11.903093)
-      (xy -5.079676 -11.800885)
-      (xy -5.080948 -11.676012)
-      (xy -5.081271 -11.560533)
-      (xy -5.081271 -11.093302)
-      (xy -6.931504 -11.093302)
-      (xy -6.931504 -11.571402)
-      (xy -6.931829 -11.714606)
-      (xy -6.932854 -11.830285)
-      (xy -6.934652 -11.920511)
-      (xy -6.937299 -11.987355)
-      (xy -6.940869 -12.032891)
-      (xy -6.945435 -12.05919)
-      (xy -6.949266 -12.067264)
-      (xy -6.962728 -12.072292)
-      (xy -6.993419 -12.076381)
-      (xy -7.043349 -12.079597)
-      (xy -7.114529 -12.082004)
-      (xy -7.208967 -12.083667)
-      (xy -7.328676 -12.084651)
-      (xy -7.475666 -12.08502)
-      (xy -7.500715 -12.085026)
-      (xy -8.034401 -12.085026)
-      (xy -8.548687 -11.570584)
-      (xy -9.062972 -11.056141)
-      (xy -9.062972 10.954644)
-      (xy -8.033262 11.982806)
-      (xy 7.995711 11.982806)
-      (xy 8.51771 11.460807)
-      (xy 9.039708 10.938808)
-      (xy 9.039708 10.879899)
-      (xy 8.89169 10.879899)
-      (xy 7.93714 11.834787)
-      (xy 1.328022 11.834133)
-      (xy 0.800937 11.834079)
-      (xy 0.302654 11.834024)
-      (xy -0.16763 11.833962)
-      (xy -0.610716 11.833891)
-      (xy -1.027406 11.833807)
-      (xy -1.418502 11.833707)
-      (xy -1.784806 11.833587)
-      (xy -2.12712 11.833443)
-      (xy -2.446246 11.833272)
-      (xy -2.742986 11.83307)
-      (xy -3.018141 11.832834)
-      (xy -3.272515 11.83256)
-      (xy -3.506908 11.832245)
-      (xy -3.722123 11.831885)
-      (xy -3.918962 11.831476)
-      (xy -4.098226 11.831015)
-      (xy -4.260718 11.830499)
-      (xy -4.40724 11.829924)
-      (xy -4.538593 11.829285)
-      (xy -4.65558 11.828581)
-      (xy -4.759002 11.827806)
-      (xy -4.849662 11.826958)
-      (xy -4.928361 11.826034)
-      (xy -4.995901 11.825028)
-      (xy -5.053085 11.823939)
-      (xy -5.100713 11.822761)
-      (xy -5.139589 11.821493)
-      (xy -5.170515 11.82013)
-      (xy -5.194291 11.818668)
-      (xy -5.211721 11.817105)
-      (xy -5.223605 11.815436)
-      (xy -5.230747 11.813658)
-      (xy -5.233947 11.811768)
-      (xy -5.234009 11.809761)
-      (xy -5.231733 11.807635)
-      (xy -5.227922 11.805385)
-      (xy -5.227262 11.805034)
-      (xy -5.15945 11.758133)
-      (xy -5.09147 11.692125)
-      (xy -5.031851 11.616201)
-      (xy -4.997172 11.557096)
-      (xy -4.977978 11.515177)
-      (xy -4.965744 11.477958)
-      (xy -4.958936 11.436602)
-      (xy -4.956019 11.382271)
-      (xy -4.955455 11.316722)
-      (xy -4.95626 11.243175)
-      (xy -4.959735 11.189998)
-      (xy -4.967463 11.147973)
-      (xy -4.981031 11.107886)
-      (xy -4.998077 11.069023)
-      (xy -5.059172 10.970009)
-      (xy -5.143128 10.88324)
-      (xy -5.243872 10.814681)
-      (xy -5.270467 10.801322)
-      (xy -5.297075 10.789173)
-      (xy -5.321449 10.779751)
-      (xy -5.347757 10.772657)
-      (xy -5.380164 10.767492)
-      (xy -5.422835 10.763858)
-      (xy -5.479937 10.761357)
-      (xy -5.555634 10.759588)
-      (xy -5.654094 10.758154)
-      (xy -5.73123 10.757225)
-      (xy -5.851932 10.756115)
-      (xy -5.946004 10.756036)
-      (xy -6.016408 10.757101)
-      (xy -6.066102 10.759425)
-      (xy -6.098048 10.763118)
-      (xy -6.115206 10.768294)
-      (xy -6.119553 10.772027)
-      (xy -6.125094 10.794855)
-      (xy -6.129377 10.839205)
-      (xy -6.131729 10.897003)
-      (xy -6.131976 10.921089)
-      (xy -6.131598 10.983646)
-      (xy -6.129114 11.023154)
-      (xy -6.122899 11.046161)
-      (xy -6.111329 11.059218)
-      (xy -6.095637 11.067584)
-      (xy -6.058615 11.076783)
-      (xy -6.033552 11.063489)
-      (xy -6.019087 11.025757)
-      (xy -6.01386 10.961646)
-      (xy -6.013788 10.950744)
-      (xy -6.013788 10.854825)
-      (xy -5.71405 10.860317)
-      (xy -5.611709 10.862366)
-      (xy -5.53404 10.864628)
-      (xy -5.47611 10.867671)
-      (xy -5.43299 10.872062)
-      (xy -5.399748 10.878369)
-      (xy -5.371455 10.887158)
-      (xy -5.343179 10.898996)
-      (xy -5.331622 10.904315)
-      (xy -5.233422 10.964399)
-      (xy -5.15679 11.040595)
-      (xy -5.102206 11.128844)
-      (xy -5.070153 11.225091)
-      (xy -5.061112 11.325275)
-      (xy -5.075566 11.42534)
-      (xy -5.113995 11.521227)
-      (xy -5.176882 11.608879)
-      (xy -5.241044 11.667272)
-      (xy -5.284884 11.697512)
-      (xy -5.329893 11.720626)
-      (xy -5.380823 11.737514)
-      (xy -5.442423 11.749074)
-      (xy -5.519446 11.756205)
-      (xy -5.616642 11.759807)
-      (xy -5.735239 11.760778)
-      (xy -6.013788 11.760778)
-      (xy -6.013788 11.680578)
-      (xy -6.015846 11.618087)
-      (xy -6.023681 11.57967)
-      (xy -6.039785 11.559982)
-      (xy -6.066649 11.553678)
-      (xy -6.072995 11.553552)
-      (xy -6.09901 11.556607)
-      (xy -6.116146 11.569084)
-      (xy -6.126196 11.595944)
-      (xy -6.13095 11.642152)
-      (xy -6.1322 11.71267)
-      (xy -6.132203 11.717583)
-      (xy -6.132203 11.834787)
-      (xy -6.382724 11.834787)
-      (xy -6.391236 11.560953)
-      (xy -6.480047 11.560953)
-      (xy -6.484442 11.66169)
-      (xy -6.488838 11.762428)
-      (xy -6.795281 11.757902)
-      (xy -6.898646 11.756225)
-      (xy -6.977228 11.754301)
-      (xy -7.035847 11.751595)
-      (xy -7.079322 11.747568)
-      (xy -7.112472 11.741685)
-      (xy -7.140119 11.733409)
-      (xy -7.16708 11.722202)
-      (xy -7.183135 11.714702)
-      (xy -7.279956 11.654074)
-      (xy -7.355641 11.576689)
-      (xy -7.409207 11.48672)
-      (xy -7.43967 11.388338)
-      (xy -7.446048 11.285714)
-      (xy -7.427356 11.18302)
-      (xy -7.382614 11.084427)
-      (xy -7.344329 11.030755)
-      (xy -7.295096 10.978068)
-      (xy -7.241572 10.936704)
-      (xy -7.179652 10.905467)
-      (xy -7.105232 10.883163)
-      (xy -7.014207 10.868594)
-      (xy -6.902473 10.860567)
-      (xy -6.765925 10.857884)
-      (xy -6.750771 10.857864)
-      (xy -6.487448 10.857864)
-      (xy -6.487448 10.959893)
-      (xy -6.484389 11.023336)
-      (xy -6.473605 11.061175)
-      (xy -6.452682 11.076933)
-      (xy -6.419208 11.07413)
-      (xy -6.410848 11.071669)
-      (xy -6.398186 11.065075)
-      (xy -6.390318 11.051283)
-      (xy -6.386404 11.024672)
-      (xy -6.385604 10.979619)
-      (xy -6.38703 10.912213)
-      (xy -6.391236 10.761652)
-      (xy -7.160933 10.761652)
-      (xy -7.245887 10.803369)
-      (xy -7.351269 10.870515)
-      (xy -7.438097 10.95721)
-      (xy -7.504112 11.059143)
-      (xy -7.547056 11.172003)
-      (xy -7.56467 11.291479)
-      (xy -7.5575 11.398227)
-      (xy -7.523039 11.522852)
-      (xy -7.466004 11.632441)
-      (xy -7.388586 11.723634)
-      (xy -7.304008 11.786785)
-      (xy -7.234942 11.827386)
-      (xy -7.604638 11.831352)
-      (xy -7.974335 11.835319)
-      (xy -8.452045 11.357778)
-      (xy -8.929755 10.880238)
-      (xy -8.929755 -10.982456)
-      (xy -8.444911 -11.467133)
-      (xy -7.960068 -11.95181)
-      (xy -7.079522 -11.95181)
-      (xy -7.079522 -11.47815)
-      (xy -7.079449 -11.347044)
-      (xy -7.079101 -11.242328)
-      (xy -7.078292 -11.160787)
-      (xy -7.076831 -11.099207)
-      (xy -7.074529 -11.054373)
-      (xy -7.071197 -11.023071)
-      (xy -7.066647 -11.002088)
-      (xy -7.060689 -10.988208)
-      (xy -7.053134 -10.978218)
-      (xy -7.049919 -10.974887)
-      (xy -7.043488 -10.969102)
-      (xy -7.035194 -10.964124)
-      (xy -7.022905 -10.959893)
-      (xy -7.004494 -10.956348)
-      (xy -6.97783 -10.953428)
-      (xy -6.940783 -10.951072)
-      (xy -6.891224 -10.949221)
-      (xy -6.827024 -10.947813)
-      (xy -6.746052 -10.946788)
-      (xy -6.646178 -10.946085)
-      (xy -6.525274 -10.945643)
-      (xy -6.38121 -10.945403)
-      (xy -6.211855 -10.945303)
-      (xy -6.015081 -10.945283)
-      (xy -6.009681 -10.945283)
-      (xy -5.809804 -10.945343)
-      (xy -5.63745 -10.945555)
-      (xy -5.490537 -10.945964)
-      (xy -5.366986 -10.946617)
-      (xy -5.264714 -10.947559)
-      (xy -5.181641 -10.948836)
-      (xy -5.115686 -10.950495)
-      (xy -5.064768 -10.95258)
-      (xy -5.026806 -10.955139)
-      (xy -4.99972 -10.958216)
-      (xy -4.981428 -10.961859)
-      (xy -4.969849 -10.966113)
-      (xy -4.966149 -10.968325)
-      (xy -4.957125 -10.975169)
-      (xy -4.949923 -10.983785)
-      (xy -4.944339 -10.997316)
-      (xy -4.940165 -11.018909)
-      (xy -4.937198 -11.051708)
-      (xy -4.93523 -11.098858)
-      (xy -4.934058 -11.163504)
-      (xy -4.933474 -11.248792)
-      (xy -4.933274 -11.357866)
-      (xy -4.933252 -11.471588)
-      (xy -4.933252 -11.95181)
-      (xy 4.895186 -11.95181)
-      (xy 4.895186 -11.47815)
-      (xy 4.89526 -11.347044)
-      (xy 4.895607 -11.242328)
-      (xy 4.896417 -11.160787)
-      (xy 4.897878 -11.099207)
-      (xy 4.90018 -11.054373)
-      (xy 4.903511 -11.023071)
-      (xy 4.908061 -11.002088)
-      (xy 4.91402 -10.988208)
-      (xy 4.921575 -10.978218)
-      (xy 4.92479 -10.974887)
-      (xy 4.931221 -10.969102)
-      (xy 4.939515 -10.964124)
-      (xy 4.951803 -10.959893)
-      (xy 4.970214 -10.956348)
-      (xy 4.996879 -10.953428)
-      (xy 5.033925 -10.951072)
-      (xy 5.083484 -10.949221)
-      (xy 5.147685 -10.947813)
-      (xy 5.228657 -10.946788)
-      (xy 5.32853 -10.946085)
-      (xy 5.449434 -10.945643)
-      (xy 5.593499 -10.945403)
-      (xy 5.762853 -10.945303)
-      (xy 5.959628 -10.945283)
-      (xy 5.965028 -10.945283)
-      (xy 6.164905 -10.945343)
-      (xy 6.337259 -10.945555)
-      (xy 6.484171 -10.945964)
-      (xy 6.607723 -10.946617)
-      (xy 6.709995 -10.947559)
-      (xy 6.793068 -10.948836)
-      (xy 6.859022 -10.950495)
-      (xy 6.90994 -10.95258)
-      (xy 6.947902 -10.955139)
-      (xy 6.974989 -10.958216)
-      (xy 6.993281 -10.961859)
-      (xy 7.00486 -10.966113)
-      (xy 7.00856 -10.968325)
-      (xy 7.017584 -10.975169)
-      (xy 7.024785 -10.983785)
-      (xy 7.03037 -10.997316)
-      (xy 7.034543 -11.018909)
-      (xy 7.037511 -11.051708)
-      (xy 7.039478 -11.098858)
-      (xy 7.040651 -11.163504)
-      (xy 7.041234 -11.248792)
-      (xy 7.041435 -11.357866)
-      (xy 7.041457 -11.471588)
-      (xy 7.041457 -11.95181)
-      (xy 7.481812 -11.951113)
-      (xy 7.922168 -11.950416)
-      (xy 8.89169 -10.99282)
-      (xy 8.89169 10.879899)
-      (xy 9.039708 10.879899)
-      (xy 9.039708 -11.055316)
-      (xy 8.525628 -11.570171)
-      (xy 8.011547 -12.085026)
-      (xy 7.467815 -12.085026)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp 3294e5cc-adc7-4de4-aa3e-bc11bbd09cb1))
-  (fp_poly
-    (pts
-      (xy 4.262862 1.847767)
-      (xy 4.062712 1.887462)
-      (xy 3.868165 1.952578)
-      (xy 3.681829 2.04292)
-      (xy 3.506309 2.158297)
-      (xy 3.344213 2.298516)
-      (xy 3.333208 2.309487)
-      (xy 3.19362 2.469628)
-      (xy 3.079685 2.641428)
-      (xy 2.990984 2.822527)
-      (xy 2.927095 3.010566)
-      (xy 2.887599 3.203184)
-      (xy 2.872073 3.398022)
-      (xy 2.8801 3.59272)
-      (xy 2.911257 3.784917)
-      (xy 2.965124 3.972255)
-      (xy 3.041281 4.152372)
-      (xy 3.139307 4.32291)
-      (xy 3.258783 4.481508)
-      (xy 3.399287 4.625807)
-      (xy 3.560398 4.753446)
-      (xy 3.741698 4.862066)
-      (xy 3.792447 4.887069)
-      (xy 3.970776 4.956642)
-      (xy 4.162722 5.005234)
-      (xy 4.360032 5.03147)
-      (xy 4.554455 5.033978)
-      (xy 4.635418 5.027384)
-      (xy 4.755141 5.00937)
-      (xy 4.878993 4.982782)
-      (xy 4.996414 4.950271)
-      (xy 5.096845 4.914486)
-      (xy 5.113514 4.907369)
-      (xy 5.176422 4.879575)
-      (xy 5.176422 5.155305)
-      (xy 5.17737 5.270175)
-      (xy 5.180937 5.359851)
-      (xy 5.1882 5.428704)
-      (xy 5.200242 5.481103)
-      (xy 5.218141 5.521418)
-      (xy 5.242979 5.55402)
-      (xy 5.275835 5.583279)
-      (xy 5.283693 5.589286)
-      (xy 5.331841 5.625405)
-      (xy 6.027529 5.628995)
-      (xy 6.191036 5.629753)
-      (xy 6.327579 5.630141)
-      (xy 6.439799 5.630084)
-      (xy 6.530335 5.62951)
-      (xy 6.601826 5.628344)
-      (xy 6.656911 5.626512)
-      (xy 6.698231 5.623941)
-      (xy 6.728423 5.620556)
-      (xy 6.750128 5.616284)
-      (xy 6.765985 5.61105)
-      (xy 6.772364 5.60814)
-      (xy 6.813649 5.579888)
-      (xy 6.853756 5.540842)
-      (xy 6.861176 5.531692)
-      (xy 6.900839 5.479691)
-      (xy 6.900839 5.163377)
-      (xy 6.80302 5.163377)
-      (xy 6.802447 5.247546)
-      (xy 6.801186 5.314799)
-      (xy 6.799285 5.360427)
-      (xy 6.797619 5.376881)
-      (xy 6.77917 5.426375)
-      (xy 6.746915 5.47301)
-      (xy 6.70862 5.507251)
-      (xy 6.682006 5.518813)
-      (xy 6.660422 5.520241)
-      (xy 6.612565 5.521655)
-      (xy 6.541769 5.523012)
-      (xy 6.451365 5.524267)
-      (xy 6.344684 5.525377)
-      (xy 6.22506 5.526299)
-      (xy 6.095823 5.526988)
-      (xy 6.045556 5.527177)
-      (xy 5.888975 5.527519)
-      (xy 5.759368 5.527354)
-      (xy 5.654108 5.526608)
-      (xy 5.570568 5.525204)
-      (xy 5.506121 5.523069)
-      (xy 5.45814 5.520127)
-      (xy 5.423999 5.516304)
-      (xy 5.401069 5.511524)
-      (xy 5.392508 5.508553)
-      (xy 5.361675 5.494397)
-      (xy 5.338115 5.478387)
-      (xy 5.320853 5.456596)
-      (xy 5.308916 5.425098)
-      (xy 5.30133 5.379967)
-      (xy 5.297121 5.317277)
-      (xy 5.295316 5.233102)
-      (xy 5.294941 5.123516)
-      (xy 5.294943 5.115147)
-      (xy 5.29505 4.811302)
-      (xy 5.357851 4.771152)
-      (xy 5.420653 4.731001)
-      (xy 5.424631 5.063488)
-      (xy 5.428609 5.395976)
-      (xy 5.508055 5.395976)
-      (xy 5.541348 5.396339)
-      (xy 5.564796 5.394607)
-      (xy 5.582719 5.386553)
-      (xy 5.599438 5.367948)
-      (xy 5.619274 5.334562)
-      (xy 5.646547 5.282167)
-      (xy 5.668993 5.238463)
-      (xy 5.691478 5.203171)
-      (xy 5.713422 5.181043)
-      (xy 5.717099 5.179144)
-      (xy 5.736515 5.160338)
-      (xy 5.738893 5.150027)
-      (xy 5.74849 5.127333)
-      (xy 5.772634 5.094754)
-      (xy 5.784794 5.081301)
-      (xy 5.820057 5.039996)
-      (xy 5.849953 4.997712)
-      (xy 5.855103 4.988925)
-      (xy 5.864408 4.973233)
-      (xy 5.871097 4.967759)
-      (xy 5.875715 4.975978)
-      (xy 5.878809 5.001367)
-      (xy 5.880925 5.047403)
-      (xy 5.88261 5.117562)
-      (xy 5.883596 5.170247)
-      (xy 5.887682 5.395976)
-      (xy 6.049732 5.395976)
-      (xy 6.049732 4.670684)
-      (xy 5.980311 4.670684)
-      (xy 5.937965 4.673012)
-      (xy 5.907319 4.683772)
-      (xy 5.876924 4.708632)
-      (xy 5.853199 4.733592)
-      (xy 5.818752 4.774407)
-      (xy 5.792026 4.811905)
-      (xy 5.782369 4.829805)
-      (xy 5.763884 4.855578)
-      (xy 5.74666 4.863109)
-      (xy 5.728045 4.875335)
-      (xy 5.724091 4.891129)
-      (xy 5.713788 4.918708)
-      (xy 5.701888 4.927669)
-      (xy 5.682192 4.947797)
-      (xy 5.679685 4.959475)
-      (xy 5.670173 4.986749)
-      (xy 5.650081 5.014537)
-      (xy 5.620478 5.046313)
-      (xy 5.620478 4.670684)
-      (xy 5.501275 4.670684)
-      (xy 5.594181 4.582035)
-      (xy 5.684401 4.495949)
-      (xy 5.495743 4.495949)
-      (xy 5.491833 4.509566)
-      (xy 5.485373 4.517789)
-      (xy 5.463685 4.53932)
-      (xy 5.42662 4.571696)
-      (xy 5.383648 4.606749)
-      (xy 5.34105 4.639494)
-      (xy 5.316019 4.655277)
-      (xy 5.303397 4.656108)
-      (xy 5.298026 4.643999)
-      (xy 5.297396 4.640374)
-      (xy 5.301708 4.605965)
-      (xy 5.317049 4.57238)
-      (xy 5.353721 4.536791)
-      (xy 5.406405 4.508278)
-      (xy 5.461513 4.493717)
-      (xy 5.473796 4.493062)
-      (xy 5.495743 4.495949)
-      (xy 5.684401 4.495949)
-      (xy 5.687086 4.493387)
-      (xy 6.193782 4.496925)
-      (xy 6.700479 4.500463)
-      (xy 6.748852 4.548826)
-      (xy 6.797226 4.59719)
-      (xy 6.801909 4.963122)
-      (xy 6.802857 5.066999)
-      (xy 6.80302 5.163377)
-      (xy 6.900839 5.163377)
-      (xy 6.900839 4.542564)
-      (xy 6.860969 4.490292)
-      (xy 6.84016 4.464017)
-      (xy 6.819745 4.442753)
-      (xy 6.796479 4.425971)
-      (xy 6.767119 4.41314)
-      (xy 6.728422 4.40373)
-      (xy 6.677143 4.397212)
-      (xy 6.610039 4.393056)
-      (xy 6.523867 4.39073)
-      (xy 6.415382 4.389706)
-      (xy 6.281341 4.389454)
-      (xy 6.243803 4.389449)
-      (xy 5.768864 4.389449)
-      (xy 5.818485 4.311739)
-      (xy 5.918623 4.130751)
-      (xy 5.994149 3.938781)
-      (xy 6.046623 3.731589)
-      (xy 6.059515 3.656757)
-      (xy 6.073359 3.507989)
-      (xy 6.073059 3.439883)
-      (xy 5.957691 3.439883)
-      (xy 5.950158 3.569829)
-      (xy 5.933506 3.697323)
-      (xy 5.912253 3.797544)
-      (xy 5.864358 3.951741)
-      (xy 5.802761 4.092989)
-      (xy 5.721941 4.233522)
-      (xy 5.700943 4.265693)
-      (xy 5.618598 4.389449)
-      (xy 5.492259 4.389449)
-      (xy 5.40111 4.393691)
-      (xy 5.332454 4.408048)
-      (xy 5.280188 4.434966)
-      (xy 5.23821 4.476893)
-      (xy 5.223799 4.497101)
-      (xy 5.197692 4.547274)
-      (xy 5.183416 4.605789)
-      (xy 5.178877 4.651968)
-      (xy 5.172749 4.748216)
-      (xy 5.08182 4.789445)
-      (xy 4.892604 4.859572)
-      (xy 4.695224 4.90311)
-      (xy 4.494324 4.919523)
-      (xy 4.294548 4.908274)
-      (xy 4.19557 4.891912)
-      (xy 3.992899 4.837549)
-      (xy 3.807426 4.759947)
-      (xy 3.636224 4.657582)
-      (xy 3.476367 4.528928)
-      (xy 3.447658 4.501985)
-      (xy 3.306267 4.346758)
-      (xy 3.190385 4.178503)
-      (xy 3.100275 3.999646)
-      (xy 3.036198 3.812614)
-      (xy 2.998416 3.619835)
-      (xy 2.987189 3.423734)
-      (xy 3.002779 3.226739)
-      (xy 3.045447 3.031276)
-      (xy 3.115454 2.839772)
-      (xy 3.213062 2.654655)
-      (xy 3.243628 2.606914)
-      (xy 3.366663 2.448343)
-      (xy 3.511834 2.307666)
-      (xy 3.676347 2.186813)
-      (xy 3.85741 2.087716)
-      (xy 4.052227 2.012304)
-      (xy 4.140291 1.987448)
-      (xy 4.253006 1.96693)
-      (xy 4.38321 1.95592)
-      (xy 4.520354 1.954417)
-      (xy 4.653891 1.962422)
-      (xy 4.773274 1.979934)
-      (xy 4.806375 1.987448)
-      (xy 5.007102 2.051398)
-      (xy 5.192111 2.13781)
-      (xy 5.358723 2.245268)
-      (xy 5.466804 2.335826)
-      (xy 5.56127 2.424195)
-      (xy 5.56127 2.668192)
-      (xy 5.562184 2.774399)
-      (xy 5.565748 2.855804)
-      (xy 5.573196 2.917178)
-      (xy 5.585763 2.963289)
-      (xy 5.604683 2.998906)
-      (xy 5.631189 3.028798)
-      (xy 5.661005 3.053571)
-      (xy 5.698469 3.076869)
-      (xy 5.742198 3.091141)
-      (xy 5.802766 3.09957)
-      (xy 5.817902 3.100841)
-      (xy 5.923636 3.109088)
-      (xy 5.943276 3.212701)
-      (xy 5.955574 3.317501)
-      (xy 5.957691 3.439883)
-      (xy 6.073059 3.439883)
-      (xy 6.072642 3.345364)
-      (xy 6.057469 3.18074)
-      (xy 6.055156 3.164595)
-      (xy 6.045834 3.101687)
-      (xy 6.570921 3.101687)
-      (xy 6.709465 3.101645)
-      (xy 6.821633 3.101397)
-      (xy 6.910652 3.100754)
-      (xy 6.979751 3.099531)
-      (xy 7.032157 3.097541)
-      (xy 7.071098 3.094597)
-      (xy 7.099802 3.090513)
-      (xy 7.121496 3.085102)
-      (xy 7.139408 3.078177)
-      (xy 7.156766 3.069552)
-      (xy 7.160463 3.067602)
-      (xy 7.223329 3.020056)
-      (xy 7.259611 2.967913)
-      (xy 7.269525 2.948522)
-      (xy 7.277308 2.929738)
-      (xy 7.283178 2.907944)
-      (xy 7.287354 2.87952)
-      (xy 7.290054 2.84085)
-      (xy 7.291495 2.788314)
-      (xy 7.291897 2.718297)
-      (xy 7.291478 2.627178)
-      (xy 7.290455 2.511341)
-      (xy 7.290114 2.476422)
-      (xy 7.174674 2.476422)
-      (xy 7.174492 2.598481)
-      (xy 7.173814 2.694477)
-      (xy 7.172437 2.767949)
-      (xy 7.170161 2.822435)
-      (xy 7.166783 2.861475)
-      (xy 7.162103 2.888607)
-      (xy 7.155918 2.90737)
-      (xy 7.149475 2.919158)
-      (xy 7.135336 2.939052)
-      (xy 7.119578 2.955235)
-      (xy 7.099198 2.968066)
-      (xy 7.071197 2.977905)
-      (xy 7.032572 2.985111)
-      (xy 6.980323 2.990042)
-      (xy 6.911449 2.993057)
-      (xy 6.822948 2.994517)
-      (xy 6.711821 2.994779)
-      (xy 6.575065 2.994202)
-      (xy 6.524759 2.993895)
-      (xy 6.015462 2.990673)
-      (xy 6.013257 2.984135)
-      (xy 5.886911 2.984135)
-      (xy 5.875258 2.996725)
-      (xy 5.845525 2.997135)
-      (xy 5.805549 2.987488)
-      (xy 5.763168 2.969907)
-      (xy 5.726221 2.946517)
-      (xy 5.71669 2.938017)
-      (xy 5.69775 2.918181)
-      (xy 5.684996 2.899117)
-      (xy 5.677026 2.874536)
-      (xy 5.672439 2.838148)
-      (xy 5.669833 2.783665)
-      (xy 5.668174 2.720293)
-      (xy 5.664063 2.546617)
-      (xy 5.730986 2.65023)
-      (xy 5.764017 2.705446)
-      (xy 5.79845 2.769738)
-      (xy 5.831118 2.836316)
-      (xy 5.858848 2.898392)
-      (xy 5.878472 2.949176)
-      (xy 5.886818 2.98188)
-      (xy 5.886911 2.984135)
-      (xy 6.013257 2.984135)
-      (xy 5.98206 2.89164)
-      (xy 5.912457 2.726256)
-      (xy 5.815101 2.559386)
-      (xy 5.753752 2.472608)
-      (xy 5.664936 2.354193)
-      (xy 5.66491 2.230614)
-      (xy 5.66941 2.138783)
-      (xy 5.684073 2.071017)
-      (xy 5.710578 2.023023)
-      (xy 5.750605 1.990503)
-      (xy 5.760776 1.98529)
-      (xy 5.789113 1.978951)
-      (xy 5.842964 1.973484)
-      (xy 5.918417 1.968895)
-      (xy 6.011558 1.965185)
-      (xy 6.118475 1.962359)
-      (xy 6.235256 1.960421)
-      (xy 6.357986 1.959373)
-      (xy 6.482755 1.95922)
-      (xy 6.605648 1.959966)
-      (xy 6.722753 1.961613)
-      (xy 6.830158 1.964166)
-      (xy 6.923949 1.967628)
-      (xy 7.000214 1.972002)
-      (xy 7.05504 1.977293)
-      (xy 7.084514 1.983504)
-      (xy 7.085699 1.984061)
-      (xy 7.110927 1.997764)
-      (xy 7.13087 2.012124)
-      (xy 7.146149 2.030579)
-      (xy 7.157385 2.056567)
-      (xy 7.165199 2.093526)
-      (xy 7.170212 2.144894)
-      (xy 7.173046 2.214107)
-      (xy 7.174322 2.304605)
-      (xy 7.174661 2.419825)
-      (xy 7.174674 2.476422)
-      (xy 7.290114 2.476422)
-      (xy 7.289996 2.464315)
-      (xy 7.285688 2.026321)
-      (xy 7.246303 1.966842)
-      (xy 7.230118 1.942595)
-      (xy 7.214668 1.922258)
-      (xy 7.19734 1.905487)
-      (xy 7.175518 1.891938)
-      (xy 7.146586 1.881269)
-      (xy 7.107932 1.873135)
-      (xy 7.056938 1.867192)
-      (xy 6.990991 1.863098)
-      (xy 6.907475 1.860508)
-      (xy 6.803775 1.859079)
-      (xy 6.677277 1.858467)
-      (xy 6.525365 1.858329)
-      (xy 6.420507 1.85833)
-      (xy 6.254395 1.858327)
-      (xy 6.115227 1.858532)
-      (xy 6.000345 1.85927)
-      (xy 5.90709 1.860864)
-      (xy 5.832803 1.863637)
-      (xy 5.774824 1.867915)
-      (xy 5.730496 1.874019)
-      (xy 5.697159 1.882274)
-      (xy 5.672154 1.893004)
-      (xy 5.652823 1.906533)
-      (xy 5.636506 1.923183)
-      (xy 5.620544 1.943279)
-      (xy 5.610141 1.956982)
-      (xy 5.587714 1.990847)
-      (xy 5.573817 2.026687)
-      (xy 5.565612 2.074388)
-      (xy 5.56127 2.127253)
-      (xy 5.553869 2.243247)
-      (xy 5.435454 2.154188)
-      (xy 5.256427 2.037322)
-      (xy 5.067361 1.947031)
-      (xy 4.870865 1.883123)
-      (xy 4.669546 1.845404)
-      (xy 4.466009 1.833683)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp d777bba5-c6b7-480f-ac41-9dd01d40db78))
-  (fp_poly
-    (pts
-      (xy 2.148811 -10.286283)
-      (xy 2.082639 -10.218771)
-      (xy 2.035409 -10.167908)
-      (xy 2.004352 -10.130219)
-      (xy 1.986698 -10.102229)
-      (xy 1.979677 -10.080464)
-      (xy 1.979219 -10.073548)
-      (xy 1.982558 -10.045797)
-      (xy 1.998115 -10.031222)
-      (xy 2.034203 -10.022569)
-      (xy 2.038426 -10.021883)
-      (xy 2.075442 -10.012732)
-      (xy 2.096088 -10.001353)
-      (xy 2.097634 -9.997789)
-      (xy 2.110033 -9.985904)
-      (xy 2.127238 -9.983162)
-      (xy 2.15129 -9.976963)
-      (xy 2.156841 -9.96836)
-      (xy 2.168614 -9.954764)
-      (xy 2.176275 -9.953558)
-      (xy 2.198563 -9.943184)
-      (xy 2.228585 -9.918308)
-      (xy 2.256823 -9.888302)
-      (xy 2.273759 -9.862536)
-      (xy 2.275256 -9.856103)
-      (xy 2.286027 -9.837105)
-      (xy 2.304007 -9.820956)
-      (xy 2.325396 -9.793094)
-      (xy 2.340789 -9.751395)
-      (xy 2.3423 -9.743756)
-      (xy 2.351676 -9.705302)
-      (xy 2.362876 -9.681222)
-      (xy 2.365355 -9.678927)
-      (xy 2.373021 -9.660193)
-      (xy 2.37741 -9.622398)
-      (xy 2.378523 -9.575902)
-      (xy 2.37636 -9.531067)
-      (xy 2.370921 -9.498253)
-      (xy 2.365355 -9.488095)
-      (xy 2.354524 -9.469351)
-      (xy 2.344197 -9.432961)
-      (xy 2.341852 -9.420613)
-      (xy 2.332623 -9.383648)
-      (xy 2.321685 -9.363028)
-      (xy 2.318361 -9.361483)
-      (xy 2.305916 -9.349707)
-      (xy 2.30486 -9.342285)
-      (xy 2.294678 -9.321677)
-      (xy 2.269377 -9.290566)
-      (xy 2.236825 -9.256941)
-      (xy 2.204888 -9.228789)
-      (xy 2.181435 -9.2141)
-      (xy 2.177987 -9.213465)
-      (xy 2.158812 -9.202691)
-      (xy 2.142791 -9.184904)
-      (xy 2.110383 -9.161911)
-      (xy 2.055143 -9.14715)
-      (xy 2.050712 -9.14651)
-      (xy 1.979219 -9.136677)
-      (xy 1.979219 -9.041854)
-      (xy 1.979891 -8.990597)
-      (xy 1.983658 -8.962204)
-      (xy 1.993149 -8.949941)
-      (xy 2.010992 -8.947071)
-      (xy 2.016224 -8.947031)
-      (xy 2.044058 -8.943154)
-      (xy 2.053228 -8.935721)
-      (xy 2.065283 -8.924696)
-      (xy 2.094579 -8.907877)
-      (xy 2.130814 -8.890323)
-      (xy 2.163689 -8.877094)
-      (xy 2.180897 -8.873022)
-      (xy 2.196835 -8.862394)
-      (xy 2.221927 -8.836619)
-      (xy 2.248434 -8.80486)
-      (xy 2.268616 -8.776282)
-      (xy 2.27502 -8.761575)
-      (xy 2.28603 -8.742075)
-      (xy 2.305253 -8.72472)
-      (xy 2.327904 -8.695537)
-      (xy 2.343192 -8.652735)
-      (xy 2.344149 -8.647443)
-      (xy 2.352877 -8.61176)
-      (xy 2.363416 -8.592749)
-      (xy 2.365959 -8.591786)
-      (xy 2.372534 -8.578286)
-      (xy 2.377184 -8.542962)
-      (xy 2.378869 -8.495574)
-      (xy 2.376778 -8.445298)
-      (xy 2.371238 -8.410876)
-      (xy 2.364067 -8.399362)
-      (xy 2.352234 -8.386903)
-      (xy 2.349266 -8.368295)
-      (xy 2.338163 -8.318913)
-      (xy 2.308974 -8.260891)
-      (xy 2.267877 -8.202546)
-      (xy 2.22105 -8.152197)
-      (xy 2.174672 -8.118162)
-      (xy 2.158303 -8.11119)
-      (xy 2.133619 -8.097908)
-      (xy 2.127238 -8.087526)
-      (xy 2.114565 -8.077146)
-      (xy 2.090233 -8.073721)
-      (xy 2.062416 -8.068654)
-      (xy 2.053228 -8.058919)
-      (xy 2.040561 -8.047792)
-      (xy 2.016224 -8.044117)
-      (xy 1.996332 -8.04243)
-      (xy 1.985252 -8.03291)
-      (xy 1.980412 -8.008869)
-      (xy 1.97924 -7.963619)
-      (xy 1.979219 -7.947905)
-      (xy 1.979868 -7.896186)
-      (xy 1.983529 -7.867379)
-      (xy 1.992776 -7.854796)
-      (xy 2.01018 -7.851749)
-      (xy 2.016224 -7.851693)
-      (xy 2.044044 -7.846854)
-      (xy 2.053228 -7.837562)
-      (xy 2.066168 -7.825817)
-      (xy 2.098009 -7.81516)
-      (xy 2.105035 -7.813712)
-      (xy 2.139188 -7.804021)
-      (xy 2.156361 -7.792718)
-      (xy 2.156841 -7.790838)
-      (xy 2.168296 -7.778217)
-      (xy 2.172782 -7.777684)
-      (xy 2.19352 -7.767432)
-      (xy 2.223012 -7.742704)
-      (xy 2.252141 -7.712543)
-      (xy 2.271791 -7.685989)
-      (xy 2.275256 -7.676049)
-      (xy 2.286131 -7.656559)
-      (xy 2.30359 -7.641102)
-      (xy 2.325109 -7.613776)
-      (xy 2.340867 -7.57268)
-      (xy 2.342272 -7.56609)
-      (xy 2.352195 -7.528201)
-      (xy 2.36354 -7.504789)
-      (xy 2.365745 -7.502812)
-      (xy 2.373131 -7.484299)
-      (xy 2.377404 -7.446702)
-      (xy 2.378551 -7.400367)
-      (xy 2.376558 -7.355638)
-      (xy 2.371409 -7.322863)
-      (xy 2.366012 -7.312627)
-      (xy 2.355745 -7.294163)
-      (xy 2.345934 -7.257892)
-      (xy 2.343634 -7.245145)
-      (xy 2.33448 -7.208009)
-      (xy 2.323115 -7.187215)
-      (xy 2.319487 -7.185609)
-      (xy 2.305808 -7.173906)
-      (xy 2.304732 -7.167107)
-      (xy 2.294585 -7.145061)
-      (xy 2.269558 -7.112896)
-      (xy 2.237473 -7.078825)
-      (xy 2.206153 -7.051061)
-      (xy 2.183421 -7.037818)
-      (xy 2.18138 -7.037591)
-      (xy 2.159415 -7.026702)
-      (xy 2.142791 -7.00903)
-      (xy 2.110383 -6.986036)
-      (xy 2.055143 -6.971276)
-      (xy 2.050712 -6.970636)
-      (xy 1.979219 -6.960803)
-      (xy 1.979219 -6.86598)
-      (xy 1.979891 -6.814723)
-      (xy 1.983658 -6.78633)
-      (xy 1.993149 -6.774067)
-      (xy 2.010992 -6.771197)
-      (xy 2.016224 -6.771157)
-      (xy 2.044041 -6.76609)
-      (xy 2.053228 -6.756355)
-      (xy 2.065217 -6.743223)
-      (xy 2.075431 -6.741553)
-      (xy 2.095129 -6.733561)
-      (xy 2.097634 -6.726751)
-      (xy 2.109959 -6.714507)
-      (xy 2.125654 -6.71195)
-      (xy 2.153233 -6.701647)
-      (xy 2.162194 -6.689747)
-      (xy 2.182588 -6.670099)
-      (xy 2.194709 -6.667544)
-      (xy 2.220846 -6.656313)
-      (xy 2.249826 -6.630085)
-      (xy 2.270698 -6.600055)
-      (xy 2.274764 -6.585701)
-      (xy 2.285984 -6.566185)
-      (xy 2.305253 -6.548846)
-      (xy 2.327904 -6.519663)
-      (xy 2.343192 -6.476861)
-      (xy 2.344149 -6.471569)
-      (xy 2.352877 -6.435886)
-      (xy 2.363416 -6.416875)
-      (xy 2.365959 -6.415912)
-      (xy 2.372534 -6.402412)
-      (xy 2.377184 -6.367088)
-      (xy 2.378869 -6.3197)
-      (xy 2.377028 -6.270704)
-      (xy 2.372211 -6.236051)
-      (xy 2.365748 -6.223488)
-      (xy 2.355962 -6.210313)
-      (xy 2.346263 -6.176963)
-      (xy 2.342638 -6.15688)
-      (xy 2.333943 -6.117225)
-      (xy 2.323408 -6.09338)
-      (xy 2.318755 -6.090271)
-      (xy 2.305258 -6.07898)
-      (xy 2.30486 -6.075469)
-      (xy 2.295214 -6.058502)
-      (xy 2.271138 -6.029379)
-      (xy 2.239927 -5.99576)
-      (xy 2.208873 -5.965304)
-      (xy 2.185273 -5.945668)
-      (xy 2.177987 -5.942253)
-      (xy 2.161929 -5.933043)
-      (xy 2.147326 -5.92005)
-      (xy 2.11526 -5.902332)
-      (xy 2.089176 -5.897847)
-      (xy 2.061868 -5.892645)
-      (xy 2.053228 -5.883045)
-      (xy 2.040561 -5.871918)
-      (xy 2.016224 -5.868243)
-      (xy 1.996332 -5.866556)
-      (xy 1.985252 -5.857036)
-      (xy 1.980412 -5.832995)
-      (xy 1.97924 -5.787745)
-      (xy 1.979219 -5.772031)
-      (xy 1.979868 -5.720312)
-      (xy 1.983529 -5.691505)
-      (xy 1.992776 -5.678922)
-      (xy 2.01018 -5.675875)
-      (xy 2.016224 -5.675819)
-      (xy 2.044047 -5.671152)
-      (xy 2.053228 -5.662193)
-      (xy 2.066053 -5.650138)
-      (xy 2.09733 -5.638928)
-      (xy 2.101334 -5.638002)
-      (xy 2.140918 -5.622469)
-      (xy 2.168718 -5.599911)
-      (xy 2.168781 -5.599821)
-      (xy 2.189584 -5.577935)
-      (xy 2.202086 -5.572206)
-      (xy 2.223292 -5.561782)
-      (xy 2.249786 -5.537981)
-      (xy 2.270361 -5.512008)
-      (xy 2.275256 -5.499036)
-      (xy 2.286104 -5.480568)
-      (xy 2.304248 -5.464767)
-      (xy 2.32659 -5.435402)
-      (xy 2.341964 -5.389149)
-      (xy 2.343144 -5.382518)
-      (xy 2.351952 -5.344522)
-      (xy 2.362311 -5.322658)
-      (xy 2.365959 -5.320574)
-      (xy 2.372534 -5.307074)
-      (xy 2.377184 -5.27175)
-      (xy 2.378869 -5.224362)
-      (xy 2.377058 -5.175366)
-      (xy 2.372318 -5.140713)
-      (xy 2.365959 -5.12815)
-      (xy 2.3558 -5.115075)
-      (xy 2.346071 -5.082396)
-      (xy 2.343582 -5.068943)
-      (xy 2.33443 -5.031927)
-      (xy 2.323051 -5.011281)
-      (xy 2.319487 -5.009735)
-      (xy 2.306393 -4.997795)
-      (xy 2.30486 -4.988245)
-      (xy 2.294497 -4.965872)
-      (xy 2.268818 -4.933812)
-      (xy 2.235937 -4.90029)
-      (xy 2.203969 -4.873533)
-      (xy 2.181029 -4.861767)
-      (xy 2.180041 -4.861716)
-      (xy 2.159343 -4.850859)
-      (xy 2.14204 -4.832113)
-      (xy 2.11226 -4.808813)
-      (xy 2.086965 -4.802509)
-      (xy 2.060752 -4.796999)
-      (xy 2.053228 -4.787707)
-      (xy 2.040561 -4.77658)
-      (xy 2.016224 -4.772905)
-      (xy 1.988409 -4.767087)
-      (xy 1.979487 -4.743785)
-      (xy 1.979219 -4.734483)
-      (xy 1.984665 -4.713543)
-      (xy 2.002632 -4.684544)
-      (xy 2.035565 -4.644486)
-      (xy 2.085905 -4.590369)
-      (xy 2.148023 -4.527257)
-      (xy 2.316827 -4.358453)
-      (xy 7.833357 -4.359891)
-      (xy 7.999877 -4.528038)
-      (xy 8.067538 -4.597647)
-      (xy 8.115605 -4.65042)
-      (xy 8.14648 -4.689331)
-      (xy 8.162563 -4.71736)
-      (xy 8.166398 -4.734545)
-      (xy 8.161875 -4.761897)
-      (xy 8.142241 -4.771927)
-      (xy 8.121993 -4.772905)
-      (xy 8.090814 -4.777193)
-      (xy 8.077591 -4.787523)
-      (xy 8.077587 -4.787707)
-      (xy 8.06519 -4.799733)
-      (xy 8.047984 -4.802509)
-      (xy 8.02392 -4.807991)
-      (xy 8.01838 -4.815585)
-      (xy 8.006404 -4.830925)
-      (xy 7.992477 -4.838024)
-      (xy 7.947489 -4.859141)
-      (xy 7.902518 -4.887894)
-      (xy 7.865275 -4.918392)
-      (xy 7.843476 -4.944745)
-      (xy 7.840757 -4.953879)
-      (xy 7.831333 -4.97438)
-      (xy 7.818555 -4.989647)
-      (xy 7.800837 -5.021713)
-      (xy 7.796352 -5.047797)
-      (xy 7.79115 -5.075104)
-      (xy 7.78155 -5.083744)
-      (xy 7.771766 -5.096756)
-      (xy 7.766876 -5.128752)
-      (xy 7.766748 -5.135551)
-      (xy 7.76303 -5.169794)
-      (xy 7.757122 -5.180857)
-      (xy 7.219079 -5.180857)
-      (xy 7.215264 -5.143809)
-      (xy 7.199708 -5.125596)
-      (xy 7.182074 -5.119426)
-      (xy 7.154383 -5.108594)
-      (xy 7.14507 -5.098668)
-      (xy 7.131384 -5.081477)
-      (xy 7.094505 -5.067576)
-      (xy 7.040702 -5.057358)
-      (xy 6.976244 -5.051219)
-      (xy 6.9074 -5.049552)
-      (xy 6.840439 -5.052754)
-      (xy 6.781629 -5.061217)
-      (xy 6.741719 -5.073279)
-      (xy 6.712868 -5.089134)
-      (xy 6.701014 -5.10216)
-      (xy 6.689021 -5.112183)
-      (xy 6.679484 -5.113348)
-      (xy 6.652844 -5.124388)
-      (xy 6.621112 -5.150802)
-      (xy 6.594349 -5.182529)
-      (xy 6.582614 -5.209511)
-      (xy 6.582599 -5.210233)
-      (xy 6.576408 -5.229593)
-      (xy 6.571498 -5.231879)
-      (xy 6.553934 -5.245649)
-      (xy 6.53983 -5.281929)
-      (xy 6.529751 -5.333765)
-      (xy 6.524263 -5.394202)
-      (xy 6.523932 -5.456289)
-      (xy 6.529325 -5.513072)
-      (xy 6.541007 -5.557598)
-      (xy 6.544385 -5.564881)
-      (xy 6.578523 -5.614701)
-      (xy 6.626073 -5.664017)
-      (xy 6.679608 -5.706915)
-      (xy 6.731696 -5.737479)
-      (xy 6.774909 -5.749798)
-      (xy 6.776715 -5.749828)
-      (xy 6.799833 -5.756362)
-      (xy 6.804627 -5.76463)
-      (xy 6.817294 -5.775757)
-      (xy 6.841632 -5.779432)
-      (xy 6.869452 -5.784271)
-      (xy 6.878636 -5.793563)
-      (xy 6.891576 -5.805309)
-      (xy 6.923417 -5.815965)
-      (xy 6.930443 -5.817413)
-      (xy 6.964596 -5.827104)
-      (xy 6.981768 -5.838408)
-      (xy 6.982249 -5.840287)
-      (xy 6.994262 -5.851965)
-      (xy 7.004452 -5.853441)
-      (xy 7.024076 -5.86529)
-      (xy 7.026655 -5.875644)
-      (xy 7.034647 -5.895342)
-      (xy 7.041457 -5.897847)
-      (xy 7.0499 -5.911159)
-      (xy 7.05526 -5.945197)
-      (xy 7.056259 -5.971856)
-      (xy 7.053596 -6.014074)
-      (xy 7.046789 -6.040871)
-      (xy 7.041457 -6.045866)
-      (xy 7.028325 -6.057855)
-      (xy 7.026655 -6.068068)
-      (xy 7.014806 -6.087692)
-      (xy 7.004452 -6.090271)
-      (xy 6.984754 -6.098264)
-      (xy 6.982249 -6.105073)
-      (xy 6.968276 -6.112166)
-      (xy 6.929596 -6.117225)
-      (xy 6.871069 -6.119711)
-      (xy 6.849033 -6.119875)
-      (xy 6.785201 -6.118322)
-      (xy 6.739667 -6.114025)
-      (xy 6.717291 -6.107522)
-      (xy 6.715816 -6.105073)
-      (xy 6.702706 -6.09571)
-      (xy 6.670047 -6.090594)
-      (xy 6.658056 -6.090271)
-      (xy 6.618787 -6.093285)
-      (xy 6.597786 -6.106722)
-      (xy 6.585197 -6.133587)
-      (xy 6.575325 -6.171838)
-      (xy 6.573747 -6.194639)
-      (xy 6.45932 -6.194639)
-      (xy 6.43149 -6.156111)
-      (xy 6.427067 -6.152148)
-      (xy 6.403261 -6.135374)
-      (xy 6.374229 -6.12555)
-      (xy 6.331708 -6.120957)
-      (xy 6.271837 -6.119875)
-      (xy 6.153724 -6.119875)
-      (xy 6.145944 -5.077209)
-      (xy 6.11139 -5.059986)
-      (xy 6.065476 -5.048307)
-      (xy 6.029647 -5.064438)
-      (xy 6.009022 -5.094856)
-      (xy 6.003514 -5.115429)
-      (xy 5.999238 -5.151631)
-      (xy 5.768762 -5.151631)
-      (xy 5.767015 -5.111332)
-      (xy 5.764999 -5.101034)
-      (xy 5.744801 -5.064961)
-      (xy 5.712206 -5.053533)
-      (xy 5.671668 -5.067057)
-      (xy 5.640044 -5.092436)
-      (xy 5.605379 -5.147581)
-      (xy 5.594386 -5.196049)
-      (xy 5.587359 -5.235305)
-      (xy 5.578162 -5.258597)
-      (xy 5.574147 -5.261367)
-      (xy 5.564464 -5.274045)
-      (xy 5.56127 -5.298371)
-      (xy 5.56127 -5.335376)
-      (xy 5.354044 -5.335376)
-      (xy 5.270468 -5.334932)
-      (xy 5.212245 -5.333295)
-      (xy 5.175135 -5.330013)
-      (xy 5.154894 -5.32463)
-      (xy 5.147283 -5.316691)
-      (xy 5.146818 -5.313173)
-      (xy 5.138825 -5.293475)
-      (xy 5.132016 -5.290971)
-      (xy 5.120793 -5.278331)
-      (xy 5.117214 -5.254839)
-      (xy 5.112521 -5.224038)
-      (xy 5.104408 -5.210793)
-      (xy 5.093701 -5.192129)
-      (xy 5.084185 -5.1567)
-      (xy 5.083111 -5.150561)
-      (xy 5.065196 -5.095104)
-      (xy 5.031849 -5.063816)
-      (xy 4.981276 -5.054141)
-      (xy 4.947013 -5.057852)
-      (xy 4.928038 -5.074732)
-      (xy 4.91569 -5.106359)
-      (xy 4.908137 -5.142237)
-      (xy 4.910247 -5.164516)
-      (xy 4.912068 -5.16644)
-      (xy 4.920654 -5.185177)
-      (xy 4.924736 -5.220506)
-      (xy 4.92479 -5.225236)
-      (xy 4.928567 -5.25913)
-      (xy 4.937834 -5.275809)
-      (xy 4.939592 -5.276169)
-      (xy 4.950719 -5.288836)
-      (xy 4.954394 -5.313173)
-      (xy 4.958988 -5.340998)
-      (xy 4.967807 -5.350178)
-      (xy 4.97727 -5.363444)
-      (xy 4.986795 -5.397374)
-      (xy 4.991398 -5.424187)
-      (xy 4.9996 -5.466339)
-      (xy 5.009436 -5.493142)
-      (xy 5.01499 -5.498197)
-      (xy 5.025076 -5.510872)
-      (xy 5.028403 -5.535201)
-      (xy 5.03347 -5.563019)
-      (xy 5.043205 -5.572206)
-      (xy 5.054611 -5.584794)
-      (xy 5.058007 -5.606744)
-      (xy 5.062342 -5.638413)
-      (xy 5.069108 -5.652383)
-      (xy 5.080912 -5.671306)
-      (xy 5.081317 -5.673352)
-      (xy 5.083924 -5.691331)
-      (xy 4.806176 -5.691331)
-      (xy 4.806011 -5.574753)
-      (xy 4.805493 -5.462059)
-      (xy 4.804625 -5.357433)
-      (xy 4.803405 -5.26506)
-      (xy 4.801834 -5.189127)
-      (xy 4.799914 -5.133819)
-      (xy 4.797644 -5.103321)
-      (xy 4.797288 -5.101217)
-      (xy 4.7833 -5.065955)
-      (xy 4.755134 -5.050851)
-      (xy 4.749182 -5.049778)
-      (xy 4.719303 -5.044604)
-      (xy 4.707135 -5.041557)
-      (xy 4.695898 -5.04936)
-      (xy 4.672061 -5.071444)
-      (xy 4.66643 -5.077016)
-      (xy 4.628753 -5.114694)
-      (xy 4.628753 -5.735026)
-      (xy 4.592924 -5.735026)
-      (xy 4.564817 -5.727717)
-      (xy 4.549807 -5.700592)
-      (xy 4.547343 -5.690621)
-      (xy 4.536602 -5.659546)
-      (xy 4.52423 -5.646224)
-      (xy 4.523964 -5.646215)
-      (xy 4.512889 -5.633808)
-      (xy 4.510338 -5.616612)
-      (xy 4.504856 -5.592548)
-      (xy 4.497262 -5.587008)
-      (xy 4.483141 -5.574721)
-      (xy 4.47335 -5.553704)
-      (xy 4.463356 -5.524823)
-      (xy 4.458531 -5.512999)
-      (xy 4.451301 -5.494564)
-      (xy 4.443712 -5.472293)
-      (xy 4.430498 -5.446508)
-      (xy 4.4198 -5.438989)
-      (xy 4.409172 -5.426577)
-      (xy 4.406725 -5.409385)
-      (xy 4.401192 -5.385323)
-      (xy 4.393528 -5.379782)
-      (xy 4.380497 -5.367237)
-      (xy 4.371043 -5.342777)
-      (xy 4.354707 -5.313467)
-      (xy 4.323975 -5.305772)
-      (xy 4.284676 -5.3152)
-      (xy 4.254429 -5.338237)
-      (xy 4.243904 -5.363923)
-      (xy 4.234411 -5.379153)
-      (xy 4.23075 -5.379782)
-      (xy 4.219651 -5.392715)
-      (xy 4.20932 -5.424542)
-      (xy 4.207876 -5.431588)
-      (xy 4.197938 -5.465749)
-      (xy 4.186032 -5.482917)
-      (xy 4.184026 -5.483395)
-      (xy 4.172543 -5.495798)
-      (xy 4.169895 -5.512999)
-      (xy 4.163696 -5.537051)
-      (xy 4.155093 -5.542602)
-      (xy 4.141961 -5.554591)
-      (xy 4.140291 -5.564805)
-      (xy 4.133282 -5.584517)
-      (xy 4.12734 -5.587008)
-      (xy 4.115971 -5.599859)
-      (xy 4.105594 -5.631182)
-      (xy 4.104789 -5.635001)
-      (xy 4.086925 -5.699443)
-      (xy 4.064131 -5.743847)
-      (xy 4.03879 -5.763911)
-      (xy 4.033065 -5.76463)
-      (xy 4.024568 -5.76269)
-      (xy 4.018146 -5.754469)
-      (xy 4.013511 -5.736365)
-      (xy 4.010378 -5.704777)
-      (xy 4.008457 -5.656103)
-      (xy 4.007461 -5.586742)
-      (xy 4.007104 -5.493093)
-      (xy 4.007074 -5.438989)
-      (xy 4.006413 -5.323473)
-      (xy 4.004476 -5.231656)
-      (xy 4.001331 -5.165048)
-      (xy 3.997048 -5.125158)
-      (xy 3.992273 -5.113348)
-      (xy 3.980246 -5.100951)
-      (xy 3.977471 -5.083744)
-      (xy 3.972479 -5.064341)
-      (xy 3.952325 -5.05579)
-      (xy 3.918545 -5.054141)
-      (xy 3.879107 -5.056923)
-      (xy 3.8593 -5.068788)
-      (xy 3.850332 -5.091145)
-      (xy 3.838904 -5.118855)
-      (xy 3.827847 -5.12815)
-      (xy 3.824745 -5.142466)
-      (xy 3.821933 -5.183472)
-      (xy 3.819481 -5.248255)
-      (xy 3.817457 -5.333903)
-      (xy 3.815931 -5.437503)
-      (xy 3.814973 -5.556141)
-      (xy 3.814669 -5.675819)
-      (xy 3.65183 -5.675819)
-      (xy 3.651443 -5.515348)
-      (xy 3.650297 -5.380736)
-      (xy 3.648408 -5.272684)
-      (xy 3.645796 -5.191895)
-      (xy 3.642479 -5.139069)
-      (xy 3.638475 -5.114911)
-      (xy 3.637028 -5.113348)
-      (xy 3.624861 -5.100997)
-      (xy 3.622226 -5.084774)
-      (xy 3.609322 -5.058442)
-      (xy 3.588922 -5.049785)
-      (xy 3.558432 -5.04388)
-      (xy 3.545573 -5.041355)
-      (xy 3.528376 -5.048959)
-      (xy 3.512269 -5.062599)
-      (xy 3.493365 -5.090366)
-      (xy 3.489009 -5.107005)
-      (xy 3.480671 -5.126014)
-      (xy 3.474207 -5.12815)
-      (xy 3.46771 -5.142371)
-      (xy 3.462903 -5.182777)
-      (xy 3.460068 -5.245983)
-      (xy 3.459405 -5.305772)
-      (xy 3.459405 -5.483395)
-      (xy 3.355792 -5.483395)
-      (xy 3.302641 -5.485351)
-      (xy 3.265915 -5.490592)
-      (xy 3.252179 -5.498182)
-      (xy 3.252179 -5.498197)
-      (xy 3.239093 -5.507971)
-      (xy 3.206647 -5.513645)
-      (xy 3.196672 -5.51408)
-      (xy 3.145676 -5.522904)
-      (xy 3.098476 -5.542772)
-      (xy 3.09676 -5.543857)
-      (xy 3.059085 -5.566056)
-      (xy 3.027953 -5.580966)
-      (xy 3.026451 -5.581506)
-      (xy 3.004521 -5.599031)
-      (xy 3.000548 -5.611644)
-      (xy 2.990429 -5.63554)
-      (xy 2.965839 -5.664953)
-      (xy 2.963543 -5.667122)
-      (xy 2.93788 -5.699794)
-      (xy 2.926565 -5.731792)
-      (xy 2.926538 -5.733023)
-      (xy 2.920694 -5.758143)
-      (xy 2.911736 -5.76463)
-      (xy 2.904644 -5.778603)
-      (xy 2.899585 -5.817283)
-      (xy 2.897099 -5.87581)
-      (xy 2.896935 -5.897847)
-      (xy 2.898487 -5.961679)
-      (xy 2.902785 -6.007212)
-      (xy 2.909288 -6.029588)
-      (xy 2.911736 -6.031064)
-      (xy 2.922863 -6.043731)
-      (xy 2.926538 -6.068068)
-      (xy 2.931266 -6.095891)
-      (xy 2.940343 -6.105073)
-      (xy 2.95509 -6.117359)
-      (xy 2.96432 -6.137124)
-      (xy 2.98098 -6.168478)
-      (xy 3.007983 -6.202076)
-      (xy 3.036655 -6.228475)
-      (xy 3.05727 -6.23829)
-      (xy 3.07716 -6.248446)
-      (xy 3.089359 -6.260493)
-      (xy 3.116121 -6.275865)
-      (xy 3.155687 -6.282676)
-      (xy 3.15778 -6.282695)
-      (xy 3.191295 -6.286538)
-      (xy 3.207499 -6.295944)
-      (xy 3.207774 -6.297497)
-      (xy 3.221949 -6.30412)
-      (xy 3.262038 -6.308983)
-      (xy 3.324385 -6.311763)
-      (xy 3.375044 -6.312299)
-      (xy 3.478216 -6.309361)
-      (xy 3.553109 -6.300436)
-      (xy 3.60047 -6.285354)
-      (xy 3.621047 -6.263949)
-      (xy 3.62211 -6.256792)
-      (xy 3.631576 -6.239593)
-      (xy 3.637028 -6.23829)
-      (xy 3.641251 -6.223609)
-      (xy 3.644793 -6.180033)
-      (xy 3.647637 -6.108265)
-      (xy 3.649763 -6.009006)
-      (xy 3.651153 -5.882958)
-      (xy 3.651789 -5.730823)
-      (xy 3.65183 -5.675819)
-      (xy 3.814669 -5.675819)
-      (xy 3.81465 -5.68322)
-      (xy 3.814991 -5.813694)
-      (xy 3.815966 -5.931962)
-      (xy 3.817506 -6.035113)
-      (xy 3.819542 -6.120233)
-      (xy 3.822005 -6.184409)
-      (xy 3.824826 -6.224728)
-      (xy 3.827847 -6.23829)
-      (xy 3.840899 -6.250829)
-      (xy 3.850276 -6.275069)
-      (xy 3.872829 -6.309671)
-      (xy 3.896286 -6.321079)
-      (xy 3.926884 -6.339508)
-      (xy 3.933402 -6.36201)
-      (xy 3.936121 -6.37702)
-      (xy 3.945279 -6.367756)
-      (xy 3.958679 -6.341903)
-      (xy 3.977298 -6.306649)
-      (xy 3.991978 -6.284627)
-      (xy 3.994173 -6.282547)
-      (xy 4.005188 -6.263941)
-      (xy 4.014942 -6.234301)
-      (xy 4.026695 -6.201786)
-      (xy 4.038318 -6.18547)
-      (xy 4.048486 -6.165931)
-      (xy 4.05148 -6.141204)
-      (xy 4.056058 -6.113799)
-      (xy 4.064556 -6.105073)
-      (xy 4.078677 -6.092787)
-      (xy 4.088468 -6.071769)
-      (xy 4.098462 -6.042889)
-      (xy 4.103287 -6.031064)
-      (xy 4.110517 -6.01263)
-      (xy 4.118106 -5.990359)
-      (xy 4.13132 -5.964573)
-      (xy 4.142018 -5.957054)
-      (xy 4.152646 -5.944642)
-      (xy 4.155093 -5.927451)
-      (xy 4.161014 -5.903394)
-      (xy 4.169224 -5.897847)
-      (xy 4.180676 -5.884849)
-      (xy 4.191433 -5.852595)
-      (xy 4.193562 -5.84234)
-      (xy 4.202518 -5.804575)
-      (xy 4.211751 -5.781427)
-      (xy 4.213506 -5.779432)
-      (xy 4.226841 -5.760447)
-      (xy 4.244702 -5.725524)
-      (xy 4.261652 -5.686605)
-      (xy 4.272255 -5.655627)
-      (xy 4.273508 -5.647679)
-      (xy 4.286027 -5.63513)
-      (xy 4.306812 -5.631778)
-      (xy 4.334207 -5.644796)
-      (xy 4.361949 -5.676749)
-      (xy 4.3834 -5.717805)
-      (xy 4.391923 -5.757838)
-      (xy 4.400111 -5.777142)
-      (xy 4.406725 -5.779432)
-      (xy 4.417852 -5.792099)
-      (xy 4.421527 -5.816437)
-      (xy 4.426365 -5.844258)
-      (xy 4.435658 -5.853441)
-      (xy 4.447403 -5.866381)
-      (xy 4.45806 -5.898222)
-      (xy 4.459508 -5.905248)
-      (xy 4.469199 -5.939401)
-      (xy 4.480502 -5.956574)
-      (xy 4.482381 -5.957054)
-      (xy 4.494059 -5.969067)
-      (xy 4.495536 -5.979257)
-      (xy 4.503529 -5.998955)
-      (xy 4.510338 -6.00146)
-      (xy 4.522364 -6.013857)
-      (xy 4.52514 -6.031064)
-      (xy 4.53106 -6.055121)
-      (xy 4.539271 -6.060668)
-      (xy 4.551016 -6.073607)
-      (xy 4.561673 -6.105448)
-      (xy 4.563121 -6.112474)
-      (xy 4.572812 -6.146627)
-      (xy 4.584115 -6.1638)
-      (xy 4.585995 -6.164281)
-      (xy 4.595886 -6.176957)
-      (xy 4.599149 -6.201285)
-      (xy 4.604216 -6.229103)
-      (xy 4.613951 -6.23829)
-      (xy 4.628039 -6.250022)
-      (xy 4.629255 -6.256792)
-      (xy 4.635549 -6.281013)
-      (xy 4.650663 -6.319034)
-      (xy 4.656736 -6.332317)
-      (xy 4.67392 -6.365906)
-      (xy 4.683872 -6.375062)
-      (xy 4.690609 -6.362733)
-      (xy 4.691879 -6.358122)
-      (xy 4.713773 -6.329745)
-      (xy 4.744266 -6.31806)
-      (xy 4.779066 -6.30371)
-      (xy 4.795598 -6.27267)
-      (xy 4.797432 -6.264502)
-      (xy 4.799746 -6.23794)
-      (xy 4.801704 -6.185963)
-      (xy 4.803307 -6.112756)
-      (xy 4.804555 -6.022503)
-      (xy 4.805449 -5.919391)
-      (xy 4.805989 -5.807605)
-      (xy 4.806176 -5.691331)
-      (xy 5.083924 -5.691331)
-      (xy 5.089493 -5.729745)
-      (xy 5.09984 -5.778611)
-      (xy 5.110482 -5.812443)
-      (xy 5.118895 -5.823838)
-      (xy 5.128847 -5.836488)
-      (xy 5.132016 -5.859969)
-      (xy 5.136941 -5.890934)
-      (xy 5.145431 -5.904391)
-      (xy 5.155022 -5.922746)
-      (xy 5.164638 -5.960398)
-      (xy 5.169023 -5.986675)
-      (xy 5.177224 -6.028821)
-      (xy 5.18706 -6.055618)
-      (xy 5.192613 -6.060668)
-      (xy 5.202698 -6.073343)
-      (xy 5.206026 -6.097672)
-      (xy 5.210449 -6.125499)
-      (xy 5.218936 -6.134677)
-      (xy 5.229095 -6.147751)
-      (xy 5.238824 -6.18043)
-      (xy 5.241313 -6.193884)
-      (xy 5.250464 -6.2309)
-      (xy 5.261844 -6.251546)
-      (xy 5.265408 -6.253092)
-      (xy 5.277293 -6.265491)
-      (xy 5.280035 -6.282695)
-      (xy 5.288777 -6.306699)
-      (xy 5.301027 -6.312299)
-      (xy 5.334036 -6.317515)
-      (xy 5.343908 -6.320699)
-      (xy 5.36861 -6.316249)
-      (xy 5.398143 -6.293344)
-      (xy 5.424839 -6.260365)
-      (xy 5.441031 -6.225693)
-      (xy 5.442855 -6.212538)
-      (xy 5.448408 -6.186467)
-      (xy 5.457657 -6.179082)
-      (xy 5.468784 -6.166415)
-      (xy 5.472459 -6.142078)
-      (xy 5.477164 -6.114255)
-      (xy 5.486196 -6.105073)
-      (xy 5.495369 -6.091726)
-      (xy 5.504662 -6.05728)
-      (xy 5.510129 -6.023467)
-      (xy 5.517935 -5.977109)
-      (xy 5.52726 -5.943995)
-      (xy 5.533397 -5.933783)
-      (xy 5.543494 -5.914291)
-      (xy 5.546468 -5.889573)
-      (xy 5.551164 -5.862169)
-      (xy 5.559881 -5.853441)
-      (xy 5.569345 -5.840176)
-      (xy 5.578869 -5.806245)
-      (xy 5.583473 -5.779432)
-      (xy 5.591675 -5.737281)
-      (xy 5.60151 -5.710477)
-      (xy 5.607065 -5.705423)
-      (xy 5.61715 -5.692747)
-      (xy 5.620478 -5.668418)
-      (xy 5.625545 -5.640601)
-      (xy 5.63528 -5.631413)
-      (xy 5.646503 -5.618773)
-      (xy 5.650081 -5.595282)
-      (xy 5.654875 -5.56441)
-      (xy 5.663153 -5.551072)
-      (xy 5.672075 -5.532985)
-      (xy 5.681206 -5.494965)
-      (xy 5.686392 -5.461621)
-      (xy 5.694318 -5.415231)
-      (xy 5.703953 -5.382006)
-      (xy 5.710325 -5.371741)
-      (xy 5.720967 -5.351884)
-      (xy 5.724091 -5.327102)
-      (xy 5.728252 -5.29969)
-      (xy 5.73597 -5.290971)
-      (xy 5.747341 -5.277692)
-      (xy 5.757528 -5.24395)
-      (xy 5.765134 -5.198883)
-      (xy 5.768762 -5.151631)
-      (xy 5.999238 -5.151631)
-      (xy 5.999091 -5.152879)
-      (xy 5.995675 -5.209422)
-      (xy 5.99319 -5.287278)
-      (xy 5.991559 -5.388664)
-      (xy 5.990703 -5.515798)
-      (xy 5.990524 -5.626963)
-      (xy 5.990524 -6.119875)
-      (xy 5.870145 -6.119875)
-      (xy 5.808551 -6.120804)
-      (xy 5.768942 -6.124715)
-      (xy 5.743728 -6.133298)
-      (xy 5.725319 -6.148241)
-      (xy 5.720991 -6.153053)
-      (xy 5.699504 -6.195471)
-      (xy 5.700554 -6.227921)
-      (xy 5.706706 -6.254427)
-      (xy 5.715644 -6.274706)
-      (xy 5.731033 -6.289592)
-      (xy 5.756537 -6.299918)
-      (xy 5.795819 -6.306518)
-      (xy 5.852542 -6.310224)
-      (xy 5.930372 -6.311869)
-      (xy 6.032972 -6.312288)
-      (xy 6.07155 -6.312299)
-      (xy 6.39152 -6.312299)
-      (xy 6.427852 -6.275967)
-      (xy 6.458102 -6.233701)
-      (xy 6.45932 -6.194639)
-      (xy 6.573747 -6.194639)
-      (xy 6.573411 -6.199486)
-      (xy 6.586747 -6.229545)
-      (xy 6.61228 -6.260095)
-      (xy 6.639806 -6.280087)
-      (xy 6.650268 -6.282695)
-      (xy 6.671376 -6.293331)
-      (xy 6.674307 -6.298788)
-      (xy 6.691349 -6.307893)
-      (xy 6.730602 -6.3141)
-      (xy 6.784815 -6.317435)
-      (xy 6.84674 -6.317928)
-      (xy 6.909129 -6.315603)
-      (xy 6.964732 -6.310488)
-      (xy 7.0063 -6.302611)
-      (xy 7.01984 -6.297497)
-      (xy 7.062417 -6.268654)
-      (xy 7.111481 -6.226225)
-      (xy 7.157857 -6.179093)
-      (xy 7.19237 -6.136138)
-      (xy 7.200577 -6.122545)
-      (xy 7.20854 -6.094236)
-      (xy 7.214357 -6.049065)
-      (xy 7.217883 -5.994701)
-      (xy 7.218977 -5.938811)
-      (xy 7.217493 -5.889063)
-      (xy 7.213291 -5.853124)
-      (xy 7.206225 -5.838663)
-      (xy 7.205882 -5.83864)
-      (xy 7.192851 -5.826095)
-      (xy 7.183397 -5.801635)
-      (xy 7.171511 -5.773912)
-      (xy 7.15959 -5.76463)
-      (xy 7.146706 -5.752637)
-      (xy 7.14507 -5.742427)
-      (xy 7.133652 -5.722794)
-      (xy 7.123706 -5.720225)
-      (xy 7.098868 -5.709148)
-      (xy 7.083001 -5.69261)
-      (xy 7.055281 -5.670044)
-      (xy 7.015709 -5.654463)
-      (xy 7.015553 -5.654429)
-      (xy 6.982936 -5.643633)
-      (xy 6.967614 -5.631408)
-      (xy 6.967447 -5.630237)
-      (xy 6.954773 -5.619992)
-      (xy 6.930443 -5.616612)
-      (xy 6.902625 -5.611545)
-      (xy 6.893438 -5.60181)
-      (xy 6.880771 -5.590683)
-      (xy 6.856433 -5.587008)
-      (xy 6.828608 -5.582501)
-      (xy 6.819429 -5.573853)
-      (xy 6.806496 -5.562755)
-      (xy 6.774668 -5.552424)
-      (xy 6.767622 -5.55098)
-      (xy 6.730209 -5.538889)
-      (xy 6.716307 -5.518877)
-      (xy 6.715816 -5.512328)
-      (xy 6.709489 -5.488642)
-      (xy 6.701014 -5.483395)
-      (xy 6.692186 -5.470165)
-      (xy 6.686891 -5.436692)
-      (xy 6.686212 -5.416786)
-      (xy 6.689152 -5.377063)
-      (xy 6.69659 -5.353234)
-      (xy 6.701014 -5.350178)
-      (xy 6.714146 -5.338189)
-      (xy 6.715816 -5.327975)
-      (xy 6.725614 -5.30171)
-      (xy 6.745419 -5.276169)
-      (xy 6.763523 -5.262007)
-      (xy 6.787926 -5.253161)
-      (xy 6.825403 -5.248452)
-      (xy 6.88273 -5.246702)
-      (xy 6.915641 -5.246565)
-      (xy 6.977896 -5.247953)
-      (xy 7.025435 -5.251722)
-      (xy 7.052361 -5.25728)
-      (xy 7.056259 -5.260696)
-      (xy 7.069212 -5.272379)
-      (xy 7.101155 -5.283094)
-      (xy 7.108972 -5.284716)
-      (xy 7.161061 -5.282761)
-      (xy 7.197953 -5.256483)
-      (xy 7.217017 -5.208363)
-      (xy 7.219079 -5.180857)
-      (xy 7.757122 -5.180857)
-      (xy 7.753889 -5.18691)
-      (xy 7.751946 -5.187358)
-      (xy 7.741553 -5.20022)
-      (xy 7.737146 -5.231211)
-      (xy 7.737144 -5.231763)
-      (xy 7.741432 -5.262942)
-      (xy 7.751762 -5.276165)
-      (xy 7.751946 -5.276169)
-      (xy 7.762419 -5.289011)
-      (xy 7.766748 -5.319701)
-      (xy 7.770947 -5.35362)
-      (xy 7.780411 -5.371677)
-      (xy 7.793319 -5.391101)
-      (xy 7.803159 -5.421482)
-      (xy 7.820045 -5.459914)
-      (xy 7.841302 -5.483787)
-      (xy 7.863967 -5.507242)
-      (xy 7.870361 -5.523667)
-      (xy 7.880408 -5.541156)
-      (xy 7.886625 -5.542602)
-      (xy 7.906141 -5.552604)
-      (xy 7.935159 -5.577598)
-      (xy 7.945134 -5.587825)
-      (xy 7.994123 -5.625214)
-      (xy 8.039884 -5.641568)
-      (xy 8.07435 -5.650341)
-      (xy 8.091844 -5.661016)
-      (xy 8.092389 -5.662954)
-      (xy 8.105067 -5.672628)
-      (xy 8.129394 -5.675819)
-      (xy 8.149286 -5.677506)
-      (xy 8.160366 -5.687026)
-      (xy 8.165205 -5.711067)
-      (xy 8.166377 -5.756317)
-      (xy 8.166398 -5.772031)
-      (xy 8.166398 -5.868243)
-      (xy 8.122866 -5.868243)
-      (xy 8.089063 -5.872283)
-      (xy 8.0712 -5.881405)
-      (xy 8.052042 -5.894439)
-      (xy 8.023097 -5.904599)
-      (xy 7.984104 -5.921651)
-      (xy 7.960049 -5.94057)
-      (xy 7.930082 -5.965875)
-      (xy 7.910731 -5.976248)
-      (xy 7.883125 -5.997837)
-      (xy 7.87475 -6.012226)
-      (xy 7.856735 -6.040925)
-      (xy 7.83068 -6.06854)
-      (xy 7.805875 -6.100195)
-      (xy 7.796352 -6.130574)
-      (xy 7.790213 -6.160241)
-      (xy 7.78155 -6.171682)
-      (xy 7.770886 -6.191691)
-      (xy 7.766748 -6.224362)
-      (xy 7.762382 -6.255161)
-      (xy 7.751946 -6.267894)
-      (xy 7.741553 -6.280756)
-      (xy 7.737146 -6.311747)
-      (xy 7.737144 -6.312299)
-      (xy 7.741432 -6.343478)
-      (xy 7.751762 -6.356701)
-      (xy 7.751946 -6.356705)
-      (xy 7.76173 -6.369717)
-      (xy 7.76662 -6.401712)
-      (xy 7.766748 -6.408511)
-      (xy 7.770171 -6.442758)
-      (xy 7.778589 -6.459872)
-      (xy 7.780374 -6.460318)
-      (xy 7.79243 -6.473142)
-      (xy 7.803639 -6.504417)
-      (xy 7.804562 -6.50841)
-      (xy 7.820342 -6.5498)
-      (xy 7.842743 -6.580455)
-      (xy 7.864127 -6.605187)
-      (xy 7.870361 -6.621174)
-      (xy 7.880949 -6.637085)
-      (xy 7.885809 -6.63794)
-      (xy 7.906031 -6.647226)
-      (xy 7.935765 -6.670063)
-      (xy 7.941165 -6.674945)
-      (xy 7.972358 -6.699489)
-      (xy 7.997086 -6.711661)
-      (xy 7.999726 -6.71195)
-      (xy 8.017029 -6.721235)
-      (xy 8.01838 -6.726751)
-      (xy 8.031047 -6.737878)
-      (xy 8.055384 -6.741553)
-      (xy 8.083202 -6.74662)
-      (xy 8.092389 -6.756355)
-      (xy 8.105056 -6.767482)
-      (xy 8.129394 -6.771157)
-      (xy 8.149439 -6.772891)
-      (xy 8.160519 -6.782594)
-      (xy 8.165284 -6.807021)
-      (xy 8.166385 -6.852923)
-      (xy 8.166398 -6.865462)
-      (xy 8.166398 -6.87477)
-      (xy 7.219079 -6.87477)
-      (xy 6.923042 -6.87477)
-      (xy 6.923042 -7.9035)
-      (xy 6.922992 -8.10411)
-      (xy 6.922813 -8.277122)
-      (xy 6.922459 -8.424541)
-      (xy 6.921885 -8.548371)
-      (xy 6.921045 -8.650619)
-      (xy 6.919894 -8.733288)
-      (xy 6.918387 -8.798384)
-      (xy 6.916479 -8.847912)
-      (xy 6.914124 -8.883878)
-      (xy 6.911276 -8.908285)
-      (xy 6.907891 -8.92314)
-      (xy 6.903923 -8.930448)
-      (xy 6.899782 -8.932229)
-      (xy 6.864538 -8.91853)
-      (xy 6.836081 -8.881845)
-      (xy 6.827785 -8.86123)
-      (xy 6.814495 -8.835761)
-      (xy 6.803629 -8.828616)
-      (xy 6.790377 -8.817188)
-      (xy 6.789825 -8.812757)
-      (xy 6.780816 -8.789113)
-      (xy 6.771323 -8.776266)
-      (xy 6.737171 -8.736721)
-      (xy 6.720022 -8.712484)
-      (xy 6.715816 -8.699292)
-      (xy 6.705107 -8.682232)
-      (xy 6.686212 -8.665796)
-      (xy 6.663301 -8.642553)
-      (xy 6.656608 -8.626196)
-      (xy 6.646901 -8.604192)
-      (xy 6.623174 -8.574585)
-      (xy 6.619604 -8.570929)
-      (xy 6.594765 -8.542036)
-      (xy 6.582794 -8.520144)
-      (xy 6.582599 -8.518352)
-      (xy 6.572372 -8.498739)
-      (xy 6.547557 -8.472333)
-      (xy 6.545594 -8.470604)
-      (xy 6.520004 -8.442897)
-      (xy 6.508625 -8.419785)
-      (xy 6.50859 -8.418896)
-      (xy 6.499828 -8.400973)
-      (xy 6.49407 -8.399362)
-      (xy 6.479733 -8.386873)
-      (xy 6.470976 -8.365202)
-      (xy 6.452955 -8.331276)
-      (xy 6.426289 -8.303921)
-      (xy 6.400356 -8.277219)
-      (xy 6.39004 -8.252971)
-      (xy 6.379099 -8.228794)
-      (xy 6.352287 -8.199688)
-      (xy 6.345739 -8.194254)
-      (xy 6.319057 -8.169264)
-      (xy 6.307999 -8.150818)
-      (xy 6.30852 -8.148126)
-      (xy 6.304078 -8.131168)
-      (xy 6.286213 -8.11041)
-      (xy 6.264268 -8.08561)
-      (xy 6.256958 -8.069424)
-      (xy 6.247022 -8.050347)
-      (xy 6.222814 -8.023313)
-      (xy 6.219953 -8.020618)
-      (xy 6.194712 -7.992607)
-      (xy 6.183043 -7.970552)
-      (xy 6.182949 -7.969245)
-      (xy 6.172298 -7.948907)
-      (xy 6.146611 -7.923586)
-      (xy 6.145944 -7.923058)
-      (xy 6.119758 -7.894507)
-      (xy 6.108939 -7.867004)
-      (xy 6.099389 -7.838637)
-      (xy 6.078157 -7.830958)
-      (xy 6.056371 -7.845786)
-      (xy 6.050363 -7.857433)
-      (xy 6.029085 -7.891735)
-      (xy 5.999031 -7.922188)
-      (xy 5.972463 -7.949989)
-      (xy 5.960935 -7.975728)
-      (xy 5.960921 -7.976403)
-      (xy 5.949136 -8.002311)
-      (xy 5.938718 -8.009161)
-      (xy 5.919028 -8.028917)
-      (xy 5.916515 -8.040303)
-      (xy 5.906356 -8.065248)
-      (xy 5.881685 -8.095166)
-      (xy 5.87951 -8.09722)
-      (xy 5.854128 -8.126748)
-      (xy 5.842573 -8.152042)
-      (xy 5.842506 -8.153427)
-      (xy 5.830169 -8.175113)
-      (xy 5.812902 -8.184735)
-      (xy 5.788854 -8.203582)
-      (xy 5.783298 -8.220925)
-      (xy 5.772589 -8.252712)
-      (xy 5.761095 -8.266145)
-      (xy 5.742432 -8.288531)
-      (xy 5.738893 -8.299565)
-      (xy 5.728944 -8.318987)
-      (xy 5.704708 -8.346195)
-      (xy 5.701888 -8.348852)
-      (xy 5.676522 -8.378194)
-      (xy 5.664954 -8.403091)
-      (xy 5.664883 -8.404473)
-      (xy 5.652922 -8.427909)
-      (xy 5.642458 -8.434404)
-      (xy 5.619381 -8.453928)
-      (xy 5.605489 -8.476693)
-      (xy 5.558258 -8.559348)
-      (xy 5.520565 -8.602075)
-      (xy 5.497082 -8.630247)
-      (xy 5.487261 -8.65219)
-      (xy 5.487261 -8.652251)
-      (xy 5.477064 -8.674691)
-      (xy 5.459775 -8.693663)
-      (xy 5.433159 -8.72686)
-      (xy 5.421772 -8.750906)
-      (xy 5.408514 -8.776721)
-      (xy 5.397452 -8.784211)
-      (xy 5.384137 -8.795588)
-      (xy 5.383648 -8.799659)
-      (xy 5.373007 -8.825586)
-      (xy 5.347616 -8.853981)
-      (xy 5.317277 -8.876236)
-      (xy 5.291789 -8.883743)
-      (xy 5.28878 -8.882987)
-      (xy 5.284125 -8.879022)
-      (xy 5.28012 -8.869592)
-      (xy 5.276717 -8.852638)
-      (xy 5.273868 -8.826103)
-      (xy 5.271525 -8.787932)
-      (xy 5.26964 -8.736065)
-      (xy 5.268165 -8.668446)
-      (xy 5.267052 -8.583018)
-      (xy 5.266253 -8.477724)
-      (xy 5.26572 -8.350507)
-      (xy 5.265405 -8.199309)
-      (xy 5.265259 -8.022073)
-      (xy 5.265233 -7.874361)
-      (xy 5.265233 -6.87477)
-      (xy 4.954394 -6.87477)
-      (xy 4.954394 -9.035564)
-      (xy 4.633733 -9.035564)
-      (xy 4.63341 -8.903577)
-      (xy 4.632658 -8.773778)
-      (xy 4.631999 -8.70009)
-      (xy 4.627845 -8.297729)
-      (xy 4.091731 -8.293039)
-      (xy 3.947043 -8.291706)
-      (xy 3.828881 -8.290246)
-      (xy 3.734171 -8.288296)
-      (xy 3.659835 -8.285492)
-      (xy 3.602799 -8.281469)
-      (xy 3.559986 -8.275863)
-      (xy 3.52832 -8.268312)
-      (xy 3.504726 -8.25845)
-      (xy 3.486127 -8.245914)
-      (xy 3.469447 -8.23034)
-      (xy 3.457827 -8.218039)
-      (xy 3.431596 -8.197649)
-      (xy 3.414866 -8.192136)
-      (xy 3.393422 -8.181823)
-      (xy 3.363468 -8.156922)
-      (xy 3.334154 -8.126491)
-      (xy 3.314634 -8.09959)
-      (xy 3.311387 -8.089715)
-      (xy 3.302103 -8.068289)
-      (xy 3.292323 -8.056276)
-      (xy 3.274033 -8.030734)
-      (xy 3.252256 -7.991549)
-      (xy 3.24676 -7.980235)
-      (xy 3.23549 -7.95127)
-      (xy 3.228257 -7.917602)
-      (xy 3.224512 -7.872916)
-      (xy 3.223705 -7.810898)
-      (xy 3.225119 -7.731735)
-      (xy 3.228023 -7.659055)
-      (xy 3.232498 -7.597302)
-      (xy 3.237969 -7.552387)
-      (xy 3.243862 -7.530222)
-      (xy 3.244802 -7.529184)
-      (xy 3.261194 -7.509372)
-      (xy 3.280495 -7.475901)
-      (xy 3.28131 -7.474246)
-      (xy 3.306489 -7.43385)
-      (xy 3.342076 -7.389964)
-      (xy 3.381489 -7.349292)
-      (xy 3.418147 -7.318538)
-      (xy 3.445468 -7.304407)
-      (xy 3.448304 -7.304136)
-      (xy 3.470274 -7.297057)
-      (xy 3.474207 -7.289222)
-      (xy 3.486196 -7.27609)
-      (xy 3.49641 -7.27442)
-      (xy 3.516203 -7.268395)
-      (xy 3.518728 -7.263319)
-      (xy 3.522655 -7.251101)
-      (xy 3.535831 -7.241076)
-      (xy 3.560771 -7.23304)
-      (xy 3.59999 -7.22679)
-      (xy 3.656001 -7.222123)
-      (xy 3.731319 -7.218835)
-      (xy 3.828456 -7.216723)
-      (xy 3.949929 -7.215585)
-      (xy 4.09825 -7.215215)
-      (xy 4.113638 -7.215213)
-      (xy 4.628753 -7.215213)
-      (xy 4.628753 -6.87477)
-      (xy 4.118088 -6.87477)
-      (xy 3.96646 -6.875195)
-      (xy 3.840367 -6.876455)
-      (xy 3.740615 -6.878525)
-      (xy 3.668008 -6.881384)
-      (xy 3.623351 -6.885007)
-      (xy 3.607451 -6.889371)
-      (xy 3.607424 -6.889572)
-      (xy 3.594412 -6.899356)
-      (xy 3.562417 -6.904246)
-      (xy 3.555618 -6.904374)
-      (xy 3.521363 -6.907186)
-      (xy 3.504254 -6.914101)
-      (xy 3.503811 -6.915562)
-      (xy 3.490778 -6.928933)
-      (xy 3.456695 -6.946434)
-      (xy 3.409084 -6.964452)
-      (xy 3.389097 -6.970658)
-      (xy 3.363258 -6.982679)
-      (xy 3.355792 -6.992456)
-      (xy 3.343838 -7.006942)
-      (xy 3.329889 -7.013898)
-      (xy 3.296605 -7.028864)
-      (xy 3.270948 -7.04276)
-      (xy 3.245622 -7.061819)
-      (xy 3.20946 -7.093984)
-      (xy 3.167869 -7.13379)
-      (xy 3.12626 -7.175774)
-      (xy 3.09004 -7.21447)
-      (xy 3.06462 -7.244414)
-      (xy 3.055409 -7.260142)
-      (xy 3.055467 -7.260446)
-      (xy 3.048092 -7.276997)
-      (xy 3.029564 -7.297155)
-      (xy 3.00757 -7.324018)
-      (xy 3.000548 -7.343323)
-      (xy 2.991866 -7.361502)
-      (xy 2.985921 -7.363232)
-      (xy 2.974684 -7.376315)
-      (xy 2.964355 -7.409012)
-      (xy 2.961826 -7.422439)
-      (xy 2.953058 -7.459444)
-      (xy 2.94263 -7.480094)
-      (xy 2.939448 -7.481647)
-      (xy 2.930914 -7.494664)
-      (xy 2.926649 -7.526672)
-      (xy 2.926538 -7.533453)
-      (xy 2.922821 -7.567696)
-      (xy 2.913679 -7.584812)
-      (xy 2.911736 -7.58526)
-      (xy 2.905324 -7.59951)
-      (xy 2.900556 -7.64012)
-      (xy 2.897688 -7.703878)
-      (xy 2.896935 -7.770283)
-      (xy 2.898075 -7.850436)
-      (xy 2.901323 -7.910042)
-      (xy 2.906424 -7.94589)
-      (xy 2.911736 -7.955306)
-      (xy 2.920564 -7.968536)
-      (xy 2.925859 -8.002009)
-      (xy 2.926538 -8.021915)
-      (xy 2.929103 -8.061643)
-      (xy 2.935593 -8.08547)
-      (xy 2.939448 -8.088523)
-      (xy 2.949608 -8.101598)
-      (xy 2.959336 -8.134277)
-      (xy 2.961826 -8.14773)
-      (xy 2.970977 -8.184746)
-      (xy 2.982357 -8.205392)
-      (xy 2.985921 -8.206938)
-      (xy 2.998571 -8.219064)
-      (xy 3.000548 -8.231209)
-      (xy 3.011581 -8.259122)
-      (xy 3.026451 -8.274422)
-      (xy 3.047379 -8.295754)
-      (xy 3.052354 -8.307979)
-      (xy 3.062779 -8.328764)
-      (xy 3.089666 -8.361707)
-      (xy 3.126439 -8.40038)
-      (xy 3.166517 -8.438354)
-      (xy 3.203324 -8.469201)
-      (xy 3.23028 -8.486492)
-      (xy 3.236753 -8.488173)
-      (xy 3.251641 -8.497888)
-      (xy 3.252179 -8.501328)
-      (xy 3.265113 -8.512426)
-      (xy 3.29694 -8.522758)
-      (xy 3.303986 -8.524201)
-      (xy 3.338146 -8.534139)
-      (xy 3.355314 -8.546045)
-      (xy 3.355792 -8.548052)
-      (xy 3.367791 -8.560592)
-      (xy 3.377995 -8.562183)
-      (xy 3.397703 -8.569505)
-      (xy 3.400198 -8.575722)
-      (xy 3.413794 -8.583203)
-      (xy 3.449846 -8.590901)
-      (xy 3.501252 -8.597398)
-      (xy 3.514912 -8.598608)
-      (xy 3.573359 -8.604866)
-      (xy 3.622479 -8.612821)
-      (xy 3.652887 -8.620905)
-      (xy 3.655329 -8.622073)
-      (xy 3.67728 -8.626254)
-      (xy 3.72409 -8.629944)
-      (xy 3.791013 -8.632947)
-      (xy 3.873307 -8.635069)
-      (xy 3.966227 -8.636116)
-      (xy 3.999473 -8.636192)
-      (xy 4.317914 -8.636192)
-      (xy 4.317914 -9.287474)
-      (xy 2.956142 -9.287474)
-      (xy 2.956142 -9.627917)
-      (xy 4.62807 -9.627917)
-      (xy 4.632112 -9.365184)
-      (xy 4.633085 -9.274315)
-      (xy 4.633625 -9.161793)
-      (xy 4.633733 -9.035564)
-      (xy 4.954394 -9.035564)
-      (xy 4.954394 -9.627917)
-      (xy 5.109813 -9.627917)
-      (xy 5.185278 -9.626487)
-      (xy 5.237086 -9.622361)
-      (xy 5.262799 -9.615779)
-      (xy 5.265233 -9.612442)
-      (xy 5.274865 -9.592425)
-      (xy 5.298434 -9.563848)
-      (xy 5.302238 -9.559963)
-      (xy 5.327155 -9.530255)
-      (xy 5.33907 -9.50663)
-      (xy 5.339242 -9.504696)
-      (xy 5.350151 -9.4827)
-      (xy 5.368846 -9.465096)
-      (xy 5.391757 -9.441854)
-      (xy 5.39845 -9.425497)
-      (xy 5.408157 -9.403493)
-      (xy 5.431884 -9.373885)
-      (xy 5.435454 -9.37023)
-      (xy 5.460091 -9.343366)
-      (xy 5.472202 -9.325791)
-      (xy 5.472459 -9.324506)
-      (xy 5.481572 -9.308963)
-      (xy 5.504039 -9.281823)
-      (xy 5.509464 -9.275878)
-      (xy 5.533809 -9.246666)
-      (xy 5.546106 -9.226124)
-      (xy 5.546468 -9.224071)
-      (xy 5.555663 -9.206327)
-      (xy 5.578304 -9.177956)
-      (xy 5.583473 -9.172265)
-      (xy 5.607914 -9.14211)
-      (xy 5.620151 -9.119576)
-      (xy 5.620478 -9.117217)
-      (xy 5.631239 -9.098488)
-      (xy 5.65715 -9.074537)
-      (xy 5.657482 -9.074287)
-      (xy 5.683569 -9.04962)
-      (xy 5.694487 -9.029206)
-      (xy 5.694487 -9.029137)
-      (xy 5.704397 -9.008686)
-      (xy 5.729097 -8.979011)
-      (xy 5.738366 -8.969738)
-      (xy 5.764187 -8.941188)
-      (xy 5.775837 -8.920489)
-      (xy 5.775476 -8.916745)
-      (xy 5.781467 -8.901565)
-      (xy 5.804791 -8.877571)
-      (xy 5.812872 -8.870904)
-      (xy 5.841894 -8.841491)
-      (xy 5.856694 -8.813809)
-      (xy 5.857173 -8.809649)
-      (xy 5.868201 -8.782783)
-      (xy 5.87951 -8.774762)
-      (xy 5.899189 -8.75573)
-      (xy 5.901713 -8.744916)
-      (xy 5.911836 -8.720916)
-      (xy 5.936434 -8.691452)
-      (xy 5.938718 -8.689295)
-      (xy 5.963873 -8.66219)
-      (xy 5.97561 -8.642074)
-      (xy 5.975722 -8.640864)
-      (xy 5.986588 -8.621254)
-      (xy 6.012128 -8.595447)
-      (xy 6.041761 -8.572688)
-      (xy 6.064902 -8.562218)
-      (xy 6.065807 -8.562183)
-      (xy 6.084541 -8.572227)
-      (xy 6.114584 -8.597285)
-      (xy 6.148241 -8.629744)
-      (xy 6.17782 -8.661992)
-      (xy 6.195627 -8.686415)
-      (xy 6.19775 -8.692743)
-      (xy 6.207553 -8.71004)
-      (xy 6.232477 -8.739048)
-      (xy 6.249399 -8.756229)
-      (xy 6.279695 -8.788719)
-      (xy 6.298359 -8.814614)
-      (xy 6.301206 -8.82256)
-      (xy 6.310678 -8.841363)
-      (xy 6.335072 -8.873594)
-      (xy 6.361591 -8.903971)
-      (xy 6.412918 -8.960039)
-      (xy 6.447064 -8.998737)
-      (xy 6.467283 -9.024113)
-      (xy 6.476829 -9.040215)
-      (xy 6.478986 -9.049987)
-      (xy 6.488846 -9.068678)
-      (xy 6.513707 -9.098029)
-      (xy 6.527092 -9.111525)
-      (xy 6.555309 -9.141805)
-      (xy 6.570734 -9.164494)
-      (xy 6.571803 -9.169946)
-      (xy 6.579646 -9.186302)
-      (xy 6.603409 -9.214218)
-      (xy 6.619909 -9.230609)
-      (xy 6.650188 -9.261485)
-      (xy 6.668704 -9.28483)
-      (xy 6.67141 -9.291225)
-      (xy 6.681059 -9.307849)
-      (xy 6.705641 -9.336776)
-      (xy 6.723217 -9.355069)
-      (xy 6.753404 -9.388688)
-      (xy 6.772078 -9.416092)
-      (xy 6.775023 -9.425072)
-      (xy 6.785868 -9.446055)
-      (xy 6.811951 -9.471)
-      (xy 6.812028 -9.471057)
-      (xy 6.838203 -9.496797)
-      (xy 6.849033 -9.519475)
-      (xy 6.858932 -9.542034)
-      (xy 6.883681 -9.573426)
-      (xy 6.893948 -9.58401)
-      (xy 6.916384 -9.60449)
-      (xy 6.937758 -9.617352)
-      (xy 6.965522 -9.624365)
-      (xy 7.007127 -9.627296)
-      (xy 7.070025 -9.627914)
-      (xy 7.078972 -9.627917)
-      (xy 7.219079 -9.627917)
-      (xy 7.219079 -6.87477)
-      (xy 8.166398 -6.87477)
-      (xy 8.166398 -6.959767)
-      (xy 8.092389 -6.969585)
-      (xy 8.050234 -6.97743)
-      (xy 8.023431 -6.986747)
-      (xy 8.01838 -6.991968)
-      (xy 8.006352 -7.006605)
-      (xy 7.992477 -7.013232)
-      (xy 7.951405 -7.032305)
-      (xy 7.911602 -7.058988)
-      (xy 7.881711 -7.08658)
-      (xy 7.870361 -7.107873)
-      (xy 7.8602 -7.125764)
-      (xy 7.835522 -7.151333)
-      (xy 7.833357 -7.153238)
-      (xy 7.806119 -7.188414)
-      (xy 7.796352 -7.222516)
-      (xy 7.791297 -7.25038)
-      (xy 7.78155 -7.259619)
-      (xy 7.771766 -7.272631)
-      (xy 7.766876 -7.304626)
-      (xy 7.766748 -7.311425)
-      (xy 7.76303 -7.345668)
-      (xy 7.753889 -7.362784)
-      (xy 7.751946 -7.363232)
-      (xy 7.741553 -7.376094)
-      (xy 7.737146 -7.407085)
-      (xy 7.737144 -7.407637)
-      (xy 7.741432 -7.438816)
-      (xy 7.751762 -7.452039)
-      (xy 7.751946 -7.452043)
-      (xy 7.76173 -7.465055)
-      (xy 7.76662 -7.49705)
-      (xy 7.766748 -7.503849)
-      (xy 7.770171 -7.538096)
-      (xy 7.778589 -7.55521)
-      (xy 7.780374 -7.555656)
-      (xy 7.79295 -7.56836)
-      (xy 7.803121 -7.597186)
-      (xy 7.819982 -7.635662)
-      (xy 7.841302 -7.659661)
-      (xy 7.864158 -7.686254)
-      (xy 7.870361 -7.706942)
-      (xy 7.880291 -7.729101)
-      (xy 7.891891 -7.733278)
-      (xy 7.916339 -7.743072)
-      (xy 7.947007 -7.766926)
-      (xy 7.949824 -7.769681)
-      (xy 7.986679 -7.798137)
-      (xy 8.024427 -7.815671)
-      (xy 8.024646 -7.815726)
-      (xy 8.056286 -7.827467)
-      (xy 8.0712 -7.838531)
-      (xy 8.09041 -7.847997)
-      (xy 8.122866 -7.851693)
-      (xy 8.166398 -7.851693)
-      (xy 8.166398 -7.947905)
-      (xy 8.165655 -7.9997)
-      (xy 8.161855 -8.028558)
-      (xy 8.15264 -8.041136)
-      (xy 8.135656 -8.044092)
-      (xy 8.132345 -8.044117)
-      (xy 8.097411 -8.049493)
-      (xy 8.059514 -8.062538)
-      (xy 8.029587 -8.078633)
-      (xy 8.018495 -8.092223)
-      (xy 8.006412 -8.102221)
-      (xy 7.997234 -8.103325)
-      (xy 7.969112 -8.11302)
-      (xy 7.956529 -8.122655)
-      (xy 7.925134 -8.145102)
-      (xy 7.910731 -8.151923)
-      (xy 7.882955 -8.173682)
-      (xy 7.874438 -8.188061)
-      (xy 7.85696 -8.217082)
-      (xy 7.830368 -8.248277)
-      (xy 7.806357 -8.280519)
-      (xy 7.796352 -8.310318)
-      (xy 7.796352 -8.31035)
-      (xy 7.789399 -8.338405)
-      (xy 7.78155 -8.347556)
-      (xy 7.7708 -8.367608)
-      (xy 7.766748 -8.399362)
-      (xy 7.762096 -8.433218)
-      (xy 7.751946 -8.451169)
-      (xy 7.740779 -8.47006)
-      (xy 7.737523 -8.498945)
-      (xy 7.742177 -8.52418)
-      (xy 7.751946 -8.532579)
-      (xy 7.761796 -8.545575)
-      (xy 7.766644 -8.577464)
-      (xy 7.766748 -8.583512)
-      (xy 7.770223 -8.620048)
-      (xy 7.778708 -8.641624)
-      (xy 7.77991 -8.64258)
-      (xy 7.792944 -8.661737)
-      (xy 7.803104 -8.690682)
-      (xy 7.820156 -8.729675)
-      (xy 7.839075 -8.75373)
-      (xy 7.864379 -8.783697)
-      (xy 7.874753 -8.803049)
-      (xy 7.896323 -8.830737)
-      (xy 7.910731 -8.839225)
-      (xy 7.944456 -8.858395)
-      (xy 7.956529 -8.868493)
-      (xy 7.984073 -8.885234)
-      (xy 7.997234 -8.887824)
-      (xy 8.016342 -8.894113)
-      (xy 8.018495 -8.898925)
-      (xy 8.031315 -8.913727)
-      (xy 8.06222 -8.929754)
-      (xy 8.100275 -8.942384)
-      (xy 8.132345 -8.947031)
-      (xy 8.15082 -8.949181)
-      (xy 8.161035 -8.960111)
-      (xy 8.165417 -8.986542)
-      (xy 8.166395 -9.035196)
-      (xy 8.166398 -9.041336)
-      (xy 8.166398 -9.135642)
-      (xy 8.092389 -9.145459)
-      (xy 8.050225 -9.153616)
-      (xy 8.023423 -9.163728)
-      (xy 8.01838 -9.169569)
-      (xy 8.006383 -9.182251)
-      (xy 7.996177 -9.183861)
-      (xy 7.976462 -9.190614)
-      (xy 7.973974 -9.196332)
-      (xy 7.962163 -9.210597)
-      (xy 7.932756 -9.230737)
-      (xy 7.922168 -9.236703)
-      (xy 7.88925 -9.258138)
-      (xy 7.871411 -9.276968)
-      (xy 7.870361 -9.28077)
-      (xy 7.860118 -9.300815)
-      (xy 7.835269 -9.327428)
-      (xy 7.833357 -9.329112)
-      (xy 7.806119 -9.364288)
-      (xy 7.796352 -9.39839)
-      (xy 7.791297 -9.426254)
-      (xy 7.78155 -9.435493)
-      (xy 7.771766 -9.448505)
-      (xy 7.766876 -9.4805)
-      (xy 7.766748 -9.487299)
-      (xy 7.76303 -9.521542)
-      (xy 7.753889 -9.538658)
-      (xy 7.751946 -9.539106)
-      (xy 7.741553 -9.551968)
-      (xy 7.737146 -9.582959)
-      (xy 7.737144 -9.583511)
-      (xy 7.741432 -9.61469)
-      (xy 7.751762 -9.627914)
-      (xy 7.751946 -9.627917)
-      (xy 7.76173 -9.640929)
-      (xy 7.76662 -9.672925)
-      (xy 7.766748 -9.679723)
-      (xy 7.770171 -9.71397)
-      (xy 7.778589 -9.731084)
-      (xy 7.780374 -9.73153)
-      (xy 7.792429 -9.744354)
-      (xy 7.803639 -9.775631)
-      (xy 7.804565 -9.779635)
-      (xy 7.820099 -9.819219)
-      (xy 7.842656 -9.84702)
-      (xy 7.842746 -9.847083)
-      (xy 7.864738 -9.869632)
-      (xy 7.870361 -9.884423)
-      (xy 7.882274 -9.902288)
-      (xy 7.911903 -9.924435)
-      (xy 7.922168 -9.93032)
-      (xy 7.955003 -9.950846)
-      (xy 7.972879 -9.967552)
-      (xy 7.973974 -9.970691)
-      (xy 7.985996 -9.981764)
-      (xy 7.996177 -9.983162)
-      (xy 8.015879 -9.990884)
-      (xy 8.01838 -9.997454)
-      (xy 8.031654 -10.007357)
-      (xy 8.065605 -10.017036)
-      (xy 8.092389 -10.021563)
-      (xy 8.136253 -10.028726)
-      (xy 8.15817 -10.038527)
-      (xy 8.165676 -10.056263)
-      (xy 8.166398 -10.073563)
-      (xy 8.162494 -10.093949)
-      (xy 8.148936 -10.119331)
-      (xy 8.122955 -10.153182)
-      (xy 8.081781 -10.198976)
-      (xy 8.022646 -10.260186)
-      (xy 7.996806 -10.286283)
-      (xy 7.827214 -10.456821)
-      (xy 2.318403 -10.456821)
-    )
-
-    (stroke (width 0) (type solid)) (fill solid) (layer "B.SilkS") (tstamp adae2843-45ad-4f34-b55b-4b5227241167))
-  (fp_line (start -9 -11) (end -8 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp faea7ad2-d47f-4ca1-9177-743da169787f))
-  (fp_line (start -9 11) (end -9 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 76899a4d-3f55-439c-ae94-77618fbc33af))
-  (fp_line (start -9 11) (end -8 12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 6b77454f-d552-44f0-ab75-12c9aa475453))
-  (fp_line (start -8 -12) (end -7 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp ce50612b-5260-4d10-81d9-1d2609139fdf))
-  (fp_line (start -8 12) (end 8.000002 12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 3c8214ee-3f52-4665-8ada-910b065a2108))
-  (fp_line (start -7 -11) (end -7 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 008d9de0-6aab-4d6b-bb32-ff165b032a6f))
-  (fp_line (start -7 -11) (end -5 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp dc1055de-f33d-4a0e-8cd0-69ecb7344775))
-  (fp_line (start -5 -11.999997) (end 5 -11.999997)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp b0c32b6a-8cf5-4deb-97ec-c3ae4126b5b9))
-  (fp_line (start -5 -11) (end -5 -11.999997)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp edb02825-4b7c-41b7-b1e1-95031d6a05e8))
-  (fp_line (start -4.469991 6.595008) (end 4.469997 6.595008)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp 977b4a5f-1b42-428b-a505-591e53f6fa20))
-  (fp_line (start -4.469991 13.945006) (end -4.469991 6.595008)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp d913fb62-3236-4cc1-a29d-b3eaf94051aa))
-  (fp_line (start -4.469991 13.945006) (end 4.469997 13.945006)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp 7cae0126-578c-4822-9c30-00592df6882e))
-  (fp_line (start -4.319978 6.764984) (end -4.319978 7.564984)
-    (stroke (width 0.8) (type solid)) (layer "F.SilkS") (tstamp d23dc835-8951-40d7-bdd7-4e614a1a974a))
-  (fp_line (start -4.319978 11.095011) (end -4.319978 11.595011)
-    (stroke (width 0.8) (type solid)) (layer "F.SilkS") (tstamp b6c8c5a7-c97f-4369-a660-4b7421923903))
-  (fp_line (start 4.320035 6.764984) (end 4.320035 7.564984)
-    (stroke (width 0.8) (type solid)) (layer "F.SilkS") (tstamp dde4e78e-a9bb-4106-b269-64ab6429e6b8))
-  (fp_line (start 4.320035 11.095011) (end 4.320035 11.595011)
-    (stroke (width 0.8) (type solid)) (layer "F.SilkS") (tstamp 5671ab0d-9298-45ca-b626-6438349a59b0))
-  (fp_line (start 4.469997 13.945006) (end 4.469997 6.595008)
-    (stroke (width 0.2) (type solid)) (layer "F.SilkS") (tstamp f8367998-f65d-4f48-9485-878186e16d23))
-  (fp_line (start 5 -11) (end 5 -11.999997)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 2dadff75-03af-4080-b3e9-4a9916fe2ba0))
-  (fp_line (start 5 -11) (end 7.000002 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 310f5691-dbf5-43d3-b0b0-542812dce518))
-  (fp_line (start 7.000002 -12) (end 8 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 9993f3fa-3b39-4f88-be1a-f41780bbe675))
-  (fp_line (start 7.000002 -11) (end 7.000002 -12)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp d7a54ff9-1bc8-40b9-aa47-ad11ffd32922))
-  (fp_line (start 8 -12) (end 9 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 8b713bcc-8f45-4bba-a3c4-32100753cb49))
-  (fp_line (start 8.000002 12) (end 9 11.000003)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp bcf5a7b4-4f2d-40df-a5ed-504c4ae8438d))
-  (fp_line (start 9 11.000003) (end 9 -11)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp c62c1224-091e-44c5-bf88-54d84c23423d))
-  (fp_arc (start 6.7034 3.5) (mid 2.3034 3.500001) (end 6.7034 3.499997)
-    (stroke (width 0.127) (type solid)) (layer "F.SilkS") (tstamp 49810b73-266a-463b-8676-2044ad78860c))
-  (fp_circle (center 4.5034 3.5) (end 4.5034 1.95)
-    (stroke (width 0.127) (type solid)) (fill none) (layer "F.SilkS") (tstamp b1e57173-711b-438a-95b8-cede50abe252))
-  (fp_line (start -6.985 1.350004) (end -5.530006 1.350009)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 06b532e0-ebe1-42a6-823d-c0eb06ea817b))
-  (fp_line (start -6.985 11.349987) (end -5.530006 11.349984)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp bc3fd67c-e0e0-460c-a9fb-a1d3163cec7e))
-  (fp_line (start -6.527998 -11.494397) (end 8.712002 -11.494397)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp 7ed8e046-4148-4709-a18a-1e97483863e1))
-  (fp_line (start -6.527998 -4.636397) (end -6.527998 -11.494397)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp 607e3970-9057-47e7-a695-bc5e357b5ec8))
-  (fp_line (start -6.527998 -4.636397) (end 8.712002 -4.636397)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp 6d87122b-3f80-46d6-acf8-2be72bb84b82))
-  (fp_line (start -5.530006 11.349984) (end -5.530006 1.350009)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 3982d108-ed64-44b5-98a6-e9efe87c3cf3))
-  (fp_line (start -5.530006 11.349984) (end -5.530006 1.350009)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 97fcc9fb-2c57-43e0-bb10-a52b72ec9229))
-  (fp_line (start -4.954983 11.315031) (end -3.684981 11.315031)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 0db51089-f5d6-448e-836b-2c974fdf8a66))
-  (fp_line (start -4.954976 7.135042) (end -3.684973 7.135042)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 820bc5d6-1985-478f-8ab1-d6d5baf9fea9))
-  (fp_line (start -4.319981 11.950031) (end -4.319981 10.680031)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 6f6b2000-584d-4180-81fb-a8c02ad8cc36))
-  (fp_line (start -4.319973 7.770042) (end -4.319973 6.500042)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 44beb524-110c-4ea4-af31-3804ac6e2c6f))
-  (fp_line (start -4.115 -10.223998) (end -2.844998 -10.223998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 9d97574a-8065-4d99-bacd-38fada53d15b))
-  (fp_line (start -4.115 -6.413998) (end -2.844998 -6.413998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 2c5decc7-0350-4c12-9a19-83c5b7149935))
-  (fp_line (start -3.524984 7.664983) (end -2.254981 7.664983)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 36aa3008-86dd-4d10-b614-c355268bedfc))
-  (fp_line (start -3.479998 -9.588998) (end -3.479998 -10.858998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp a6fdbee0-ee2c-49e3-9b77-f80468281a0d))
-  (fp_line (start -3.479998 -5.778998) (end -3.479998 -7.048998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 10c4ccc3-aa49-4760-8e9e-c8a626a1a65b))
-  (fp_line (start -2.889981 8.299983) (end -2.889981 7.029983)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp f7d2fd15-0e8b-468e-b534-e6a27236dc78))
-  (fp_line (start -1.915 -10.223998) (end -0.644997 -10.223998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp f695da7a-59f4-493e-af06-36f1465556e0))
-  (fp_line (start -1.279997 -9.588998) (end -1.279997 -10.858998)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 861f4fa5-2d2d-4337-9305-5743e7b0eb53))
-  (fp_line (start -0.635002 0) (end 0.635 0)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp fcfe4c9c-3d82-4642-8591-626745c7ee4c))
-  (fp_line (start 0 0.635) (end 0 -0.635)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp d3b9f36b-6bb8-4114-95de-9a9d77427c03))
-  (fp_line (start 2.255033 7.664985) (end 3.525035 7.664985)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 259df9c0-138a-48da-9b2c-ccf847bac56d))
-  (fp_line (start 2.890035 8.299985) (end 2.890035 7.029985)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 945b17ce-aa9c-4cf8-a520-7e6ad48104ee))
-  (fp_line (start 3.464997 -0.3) (end 4.735 -0.3)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 9cd82616-ef3c-45e6-aec4-bf69d5d79899))
-  (fp_line (start 3.684982 11.315029) (end 4.954984 11.315029)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 90bb57ed-2634-4a13-b98f-373e9d5318aa))
-  (fp_line (start 3.684994 7.135037) (end 4.954997 7.135037)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 037f1729-9310-4c26-acfb-974ad8696a6e))
-  (fp_line (start 3.865 4) (end 5.135002 4)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 2be03dfc-f406-4001-becf-09f223f80727))
-  (fp_line (start 4.1 0.335) (end 4.1 -0.935)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 0264dec9-7de5-4b25-900e-82893f2c366d))
-  (fp_line (start 4.319984 11.950029) (end 4.319984 10.680029)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp b4420dc6-d7c7-4459-bd14-d43db6777c8d))
-  (fp_line (start 4.319997 7.770037) (end 4.319997 6.500037)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 0cfadba8-341b-41d9-9085-dc571b0bd722))
-  (fp_line (start 4.500002 4.635) (end 4.500002 3.365)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 2c257a0f-5455-43cd-a0b7-c4dbb651dd72))
-  (fp_line (start 6.585 -6.414397) (end 7.855 -6.414397)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp 751ff26f-71f2-4ec1-8fc6-a37507c0bb67))
-  (fp_line (start 7.22 -5.779397) (end 7.22 -7.049397)
-    (stroke (width 0.127) (type solid)) (layer "Eco1.User") (tstamp baa08355-0c20-4978-b9b8-a75fa53ba3cb))
-  (fp_line (start 8.712002 -4.636397) (end 8.712002 -11.494397)
-    (stroke (width 0.254) (type solid)) (layer "Eco1.User") (tstamp e3be3129-7490-4c92-9ff8-fc0585a8bd65))
-  (pad "1" smd oval (at -8.599997 -10.16) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 123d4600-40bf-4016-8ba7-1925a5ac0442))
-  (pad "2" smd oval (at -8.599997 -8.89) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp f5017df6-3526-48cd-ad91-cdc135986265))
-  (pad "3" smd oval (at -8.599997 -7.619998) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 84a291bd-29e0-4600-9d94-6f90fb2ad555))
-  (pad "4" smd oval (at -8.599997 -6.349998) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 7a955fa3-20dd-42d4-8eb2-de0552134b14))
-  (pad "5" smd oval (at -8.599997 -5.079998) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 75be6fd1-0d93-417a-abe5-e7733fe26311))
-  (pad "6" smd oval (at -8.599997 -3.809998) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp edada770-2c0e-496c-9f55-17a9b7f4098f))
-  (pad "7" smd oval (at -8.599997 -2.539998) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp c42cbd8f-80d3-45af-bb28-0c26be441de7))
-  (pad "8" smd oval (at -8.599997 -1.269998) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 4313bf05-bc5b-4fde-b6a1-1351d81d71f8))
-  (pad "9" smd oval (at -8.599997 0.000002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 155ac965-e181-4c9b-a8a0-6df82b980843))
-  (pad "10" smd oval (at -8.599997 1.270002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 2feacbe4-e9d6-4b6f-9757-01532d9ba6ce))
-  (pad "11" smd oval (at -8.599997 2.540002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp b7b9b576-2ec3-4cb2-8899-115657d59cb9))
-  (pad "12" smd oval (at -8.599997 3.810002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 60f5a17b-23c1-402e-a74e-ef93f1f3078f))
-  (pad "13" smd oval (at -8.599997 5.080002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 2eb71d59-f944-4eba-ae9c-4152d049d9c1))
-  (pad "14" smd oval (at -8.599997 6.350002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 4ddf6c5f-4c03-4f2e-ba61-6693c4b0d4b9))
-  (pad "15" smd oval (at -8.599997 7.620002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp ed7d203a-ec2e-4eeb-8e72-24ca81c508e3))
-  (pad "16" smd oval (at -8.599997 8.890002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 05dbb9e2-39f7-43c4-ae2d-21f08eb31806))
-  (pad "17" smd oval (at -8.599997 10.160002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp e50dba5e-b81e-484a-90af-a0f8d3b5ddd9))
-  (pad "18" smd oval (at 8.6 10.160002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 668ea2cf-7f95-4656-8852-b873c2eb110b))
-  (pad "19" smd oval (at 8.6 8.890002 180) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp b03b0e7f-094a-4a71-b323-78742dc6bf58))
-  (pad "20" smd oval (at 8.6 7.620002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp d0e9c6c3-2597-4f84-8e87-448b6c704b47))
-  (pad "21" smd oval (at 8.6 6.350002 180) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 4fb6a590-9a48-4ced-828e-4dc46a5102f6))
-  (pad "22" smd oval (at 8.6 5.080002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp e6322c41-2e4b-47e2-b80b-e79f01d647e5))
-  (pad "23" smd oval (at 8.6 3.810002 180) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 823ad384-a54b-409e-b476-5db2d3942c02))
-  (pad "24" smd oval (at 8.6 2.540002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 463e8685-7481-404e-bce7-d2c436752697))
-  (pad "25" smd oval (at 8.6 1.270002 180) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp fb5cc92c-09fb-4e77-9863-6add4092741f))
-  (pad "26" smd oval (at 8.6 0.000002) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 5ce1b358-db25-42c0-9fb7-6baf46122c6e))
-  (pad "27" smd oval (at 8.6 -1.269998 180) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp eb041cf5-19b6-40ee-b69e-57929bb2e5a4))
-  (pad "28" smd oval (at 8.6 -2.539998 180) (size 1.8 0.8) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp c42792a8-794d-431b-b1d5-41f8853f07f8))
-  (pad "29" smd circle (at -7 11.4) (size 0.6 0.6) (layers "F.Cu" "F.Paste" "F.Mask")
-    (solder_mask_margin 0.0254) (tstamp cdfba992-bbc9-43f8-a762-2d072924f690))
-  (pad "30" smd circle (at -5.5 11.4) (size 0.6 0.6) (layers "F.Cu" "F.Paste" "F.Mask")
-    (solder_mask_margin 0.0254) (tstamp db9a804e-60c9-49ff-a2d0-33e0016eff96))
-  (pad "31" smd rect (at -2.328047 -1.0882 180) (size 3 3) (layers "F.Cu" "F.Paste" "F.Mask") (tstamp 11c89542-2f42-4038-adf6-9b16ecc7dc67))
-  (group "" (id b2e17341-e5bd-4545-8e66-3a86f4ef0396)
-    (members
-      0681af30-e6e7-48bb-8dd8-f081f51e4b7d
-      07c54cae-9b90-4929-b2ae-4855ec4f20cb
-      0897f653-a20e-4c77-b80d-57b32631b473
-      0984c573-6098-4e6d-8be5-b91a766a19d9
-      0a24d966-ac30-4549-a068-887411259672
-      0fc51499-15f5-4fa1-8bc1-fbda6567f4b5
-      10b7088f-1410-401a-8bf1-1d655fa47975
-      136b564b-136b-499f-ad0e-6786eef1329b
-      137a63c3-f4b7-4105-9b64-c9ba4a0bc830
-      16258d9d-c5c1-41da-a9b7-5ee97beead97
-      1a43bfcc-f35c-499e-882f-58f29327b311
-      1c0c790e-40c0-420a-bdee-4caeedfccb4b
-      1d643733-af99-479b-86e2-19571cec0f74
-      1e962e71-5ad8-4518-9837-71e587a0c0dd
-      1ec987c2-2b50-4649-aa71-95d58dc6a502
-      20fd2493-346d-4b7c-b23b-a53b4d72b47d
-      232cdc1a-4220-464a-899b-e32f598f78c2
-      23b08156-b9d5-4c9b-9cc7-bc50381875f3
-      2bc97976-af2d-40e6-9771-68d9234e801a
-      2fbb0269-cb0e-4243-98bf-32dc8c1f5bab
-      31caeaa8-dd17-4314-97a5-ece82f3eebb5
-      3294e5cc-adc7-4de4-aa3e-bc11bbd09cb1
-      3582f6c8-df32-45fc-bc63-857199f53756
-      387be091-d8ef-42ac-97c5-0efd97e37ff9
-      3a4af950-f54a-4966-836d-851f057e87f0
-      3b7d4004-a1ce-48aa-afee-404d4e2b01a2
-      3eb2223f-9284-4abd-8a36-412141015a03
-      42cf9784-6b1b-4198-aa28-0b411664f52b
-      5534c284-2c01-4af1-b4ea-5c6798841d88
-      56413d6e-7347-4974-9c35-46329de9b7f6
-      5a3270e2-2b2e-440b-b175-4d488ede477b
-      5a37ddaf-cbf2-49af-9e0e-27770056929d
-      60669bb2-ab23-4bd2-a3b3-29128112878a
-      62cf05a8-2bb1-46f0-8dc6-33cd3791401d
-      632eaf6e-5d54-46de-8f55-4208c0c0b677
-      6707ccb7-e250-4bd5-87b9-34efc0cb25ce
-      67323bd5-f5ad-4882-9b0e-72506f9b2bff
-      6a5fa4d4-03a9-46d9-8f65-29ed6100a944
-      70c0bbf1-7dbd-4d2b-970d-e9890c5a38fd
-      744a1e83-a676-4e3a-9724-099f99bd2912
-      77e14973-2176-4bdd-8707-ea2f4e6f29ee
-      7ad004ce-c971-4dc7-afe4-5362059426bb
-      7b5adda8-cb21-4c06-97c4-ce6866d5839b
-      7d21d4af-961f-4781-b2e7-b72a2f9fa540
-      83ce798a-243a-448c-979f-54c182e1bd36
-      84819531-bce6-47fc-903a-968712021d31
-      848af073-6c5e-4918-8c43-ade8c5263fd0
-      84b32b5e-bbd3-43eb-91f5-be668ae54000
-      84e91437-9e62-4b51-a15a-b7c14f490f40
-      85693583-f9b5-4be9-810c-bf8f71381fab
-      89acbfd9-ed8a-4996-be31-e3bc7d162692
-      8c3310c6-596c-4d53-be4f-1c01a3a41573
-      8cf529b2-ca25-427c-bee0-415e546e88d5
-      919a8d8f-94a3-4d63-bc92-149551ce8cf4
-      9283b1ae-a5eb-4a2b-a7ea-64389e499b33
-      933fd734-c4b0-4154-8a2f-6c42689e95e1
-      9c56ce08-da97-41d6-bb14-021ed7172db1
-      9c890085-ad74-428d-a6d3-881f06be1c83
-      9ceb141b-f522-49ff-9765-62a7c2734ad2
-      9e2721f6-0120-45c8-9767-b3a099486284
-      9f3fb963-03c0-4ee9-9527-6d5774dd347b
-      a24ecc51-2392-4615-8d3d-6d62619fb6b3
-      a7cec450-ce12-47c0-908c-5994bf20258d
-      ad3dcda3-e151-43f9-8e07-98602c2851d2
-      adae2843-45ad-4f34-b55b-4b5227241167
-      b06b59c3-4ff0-424d-8191-5d8ebd912275
-      b072a6f9-85a5-44cc-8dd8-dc2e08d83cc5
-      b11aed1e-03fc-4bd5-bcdc-7926c7d74922
-      b54453ac-c8cc-41cf-9b6f-b0e91e0df69b
-      b7ae08bd-b797-465f-ac53-e0ee179f27ab
-      bc9ef36e-3246-45b5-bdee-0b694a8192b1
-      c30c42e2-406e-4759-929e-56a50e9f582c
-      c35fa668-320e-4ad8-913c-c7fe2c50e94d
-      c53ba1e0-69e2-4e58-9ff0-6182d4940429
-      c5ba7456-fbcc-46a0-ab30-1d5b6c986dd6
-      ccfc67c3-52f3-45a1-afba-0fba8660a117
-      cd437c9a-f3e0-4725-b1a4-372d2b4317b9
-      cdb2643c-1fac-431b-8554-235257416261
-      cf8ff2a3-47b7-4b2a-b6f5-d49e6c16d2b1
-      d0b09c90-6532-4806-bf92-bb71aca41949
-      d15d9a45-c141-4c3a-a593-9ae75672406b
-      d38e7858-34a0-463d-850a-bbe5143649c3
-      d3a229a4-62e0-4212-9f8b-11ae8d23c402
-      d663090d-102e-43bf-ac9b-cab6d1b781a7
-      d71acef2-68cc-4e8c-9a7d-76cb3faaf3c5
-      d7499ab9-53bc-476c-bc20-6f47bc74f1b6
-      d777bba5-c6b7-480f-ac41-9dd01d40db78
-      e347eaed-df51-4f54-8270-ba866af187f4
-      e3d4d17c-0832-405d-bad8-78ceb16917d8
-      e441efbe-a76b-4b3c-bad6-007b16e83b1b
-      e6f02aad-7320-44b4-b47c-3369c1b51c1b
-      e7512348-6772-4561-8567-713be7b0f5a4
-      e90ea281-b3a7-4597-8e21-250a91db8aa0
-      e9d9dc75-e2ed-4b55-8ae2-3b22340cda38
-      ebbc4e02-691e-45a9-aa88-74c58af6811d
-      ec5ef42d-4666-48c2-8226-c11dd2243a11
-      eeef72b0-ba43-4d01-90ee-36b97875f1ec
-      ef00d866-3c74-4c5c-92e0-83db4cff5935
-      f11d393a-b6c6-42ac-bb81-b1f9400808de
-      f2068426-0fcc-40f1-8fda-1ac9b5798677
-      f2315e8d-4fce-42bf-96b4-9825ce3e4a44
-      f4c74ac9-5647-48f5-938b-19d7b3536e6e
-      f66540a3-a6fa-42a9-ae4b-244d24f899bd
-      f95b8ce0-8528-4acb-b6ff-988c2c4469a8
-      fa7cbd91-ab3f-4225-9a41-6278f8717e82
-      fa9bd237-d766-4231-9574-d5ef7e6c96a5
-      fe2cd7ae-6b9b-45c5-b819-7cd644fc8aa2
-    )
-  )
-  (model "${KICAD_M5STACK}/M5KiCad.3d/M5STAMP-S3.step"
-    (offset (xyz 0 0 1.1))
-    (scale (xyz 1 1 1))
-    (rotate (xyz 0 0 0))
-  )
-)
diff --git a/components/m5stack/stamp-s3/artifacts/Stamp-S3.step b/components/m5stack/stamp-s3/artifacts/Stamp-S3.step
deleted file mode 120000
index 16aa094..0000000
--- a/components/m5stack/stamp-s3/artifacts/Stamp-S3.step
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/m5stack/stamp-s3/artifacts/Stamp-S3.step
\ No newline at end of file
diff --git a/components/m5stack/stamp-s3/artifacts/Stamp-S3.step.ARCHIVED.link b/components/m5stack/stamp-s3/artifacts/Stamp-S3.step.ARCHIVED.link
deleted file mode 120000
index cc83e18..0000000
--- a/components/m5stack/stamp-s3/artifacts/Stamp-S3.step.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Stamp-S3.step
\ No newline at end of file
diff --git a/components/m5stack/stamp-s3/artifacts/Stamp-S3.step.ARCHIVED.md b/components/m5stack/stamp-s3/artifacts/Stamp-S3.step.ARCHIVED.md
deleted file mode 100644
index b0e138f..0000000
--- a/components/m5stack/stamp-s3/artifacts/Stamp-S3.step.ARCHIVED.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# ARCHIVED — `Stamp-S3.step`
-
-STEP (AP214) solid model of the M5Stack **Stamp-S3** module, published by M5Stack in the
-`m5stack/M5_Hardware` KiCad library so the module can be placed in a host-board 3D view.
-
-| Field | Value |
-|---|---|
-| Original repository path | `components/m5stack/stamp-s3/artifacts/Stamp-S3.step` |
-| Archived to | `archive/components/m5stack/stamp-s3/artifacts/Stamp-S3.step` |
-| SHA-256 | `7f29337cdac90c80400897f52795ed0709548d4e74dc4436efb3e4f3873d2ebf` |
-| Byte size | 2 904 597 |
-| Media type | ISO 10303-21 STEP text file |
-| Retrieved | 2026-09-04 |
-| Upstream repository | <https://github.com/m5stack/M5_Hardware> |
-| Path in repository | `KiCad/3D/M5Stack.3dshapes/Stamp-S3.step` |
-| Repository HEAD when fetched | `a240115c94b19ecf647f229c47fa9a8ce46ccdc4` (authored 2026-08-17T07:36:01Z) |
-| Release/tag | none — the repository publishes no releases |
-| Licence | **unknown** — `m5stack/M5_Hardware` carries no `LICENSE` file (checked 2026-09-04) |
-| Redistribution status | `unknown` |
-| Disposition | `repository` → archived for size |
-| Why moved | Size, and it is **derived**: a mechanical export of a board M5Stack also ships as `Stamp-S3.stl` (158 484 bytes, retained in-repo beside this placeholder) and as a dimension drawing. The STL is sufficient for enclosure clearance work; the STEP matters only for parametric CAD. |
-| Reproducible? | Yes — re-fetchable byte-for-byte from a pinned commit (below) |
-| Reacquisition | `automatic` |
-
-## Reacquisition
-
-Two independent hosts:
-
-1. **GitHub raw, pinned to the commit above** (preferred — immutable):
-   ```bash
-   curl -fSL -o Stamp-S3.step \
-     'https://raw.githubusercontent.com/m5stack/M5_Hardware/a240115c94b19ecf647f229c47fa9a8ce46ccdc4/KiCad/3D/M5Stack.3dshapes/Stamp-S3.step'
-   ```
-2. **GitHub API tarball of the whole library** (survives a raw-CDN outage):
-   ```bash
-   curl -fSL -H "Authorization: Bearer $(gh auth token)" \
-     -o M5_Hardware.tar.gz \
-     'https://api.github.com/repos/m5stack/M5_Hardware/tarball/a240115c94b19ecf647f229c47fa9a8ce46ccdc4'
-   ```
-3. Branch link (moves — use only if the commit is gone):
-   <https://github.com/m5stack/M5_Hardware/blob/master/KiCad/3D/M5Stack.3dshapes/Stamp-S3.step>
-
-## Important: there is no `Stamp-S3A.step`
-
-`m5stack/M5_Hardware` at the commit above publishes **exactly one** Stamp-S3-family STEP
-model and **no Stamp-S3A footprint**. It does publish two STL files —
-`Products/S007_Stamp-S3/Structures/Stamp-S3.stl` and
-`Products/S007-V033_Stamp-S3A/Structures/Stamp-S3A.stl` — and those two files are
-**byte-identical** (both SHA-256 `f72c1af2d42930fc57a3db1bd3282568a3952095f77539016a12437d59d7df5d`).
-
-That is evidence, not proof, that the S3A is mechanically and footprint-compatible with
-the S3. It sits against the vendor's own specification tables, which give the S3 as
-24.0 × 18.0 × 4.7 mm and the S3A as 26.0 × 18.0 × 4.7 mm. The conflict is recorded in
-[`../../stamp-s3a/README.md`](../../stamp-s3a/README.md) §"Mechanical" and in
-[`devices/m5stack/dinmeter/gaps-and-conflicts.md`](../../../../devices/m5stack/dinmeter/gaps-and-conflicts.md).
-
-## Consumers
-
-- Component record: [`components/m5stack/stamp-s3/README.md`](../README.md)
-- Device that caused the fetch: [`devices/m5stack/dinmeter/README.md`](../../../../devices/m5stack/dinmeter/README.md) (fits `Stamp-S3-SMD` as `M1`)
-- Related: [`devices/m5stack/dinmeter-v1.1/README.md`](../../../../devices/m5stack/dinmeter-v1.1/README.md)
diff --git a/components/m5stack/stamp-s3/artifacts/Stamp-S3.stl b/components/m5stack/stamp-s3/artifacts/Stamp-S3.stl
deleted file mode 100644
index 3f82f65..0000000
Binary files a/components/m5stack/stamp-s3/artifacts/Stamp-S3.stl and /dev/null differ
diff --git a/components/m5stack/stamp-s3a/README.md b/components/m5stack/stamp-s3a/README.md
deleted file mode 100644
index 992e608..0000000
--- a/components/m5stack/stamp-s3a/README.md
+++ /dev/null
@@ -1,400 +0,0 @@
-# M5Stack Stamp-S3A
-
-- **Category:** ESP32-S3 **core module**. The successor to [Stamp-S3](../stamp-s3/README.md),
-  and the reason the [DinMeter v1.1](../../../devices/m5stack/dinmeter-v1.1/README.md) exists.
-- **SKU:** **`S007-V033`** (SMD). Header variants `S007-PIN127-V033`, `S007-PIN254-V033`.
-- **Scope:** module level. ESP32-S3 silicon → [`components/espressif/esp32-s3r8/`](../../espressif/esp32-s3r8/README.md)
-  (same family; this module fits the **FN8**: 8 MB in-package flash, **no PSRAM**).
-- **Retrieved:** 2026-09-04
-
-> **The one-line answer.** Same SoC, same flash, same *no* PSRAM, same 23 GPIOs, same 2.54/1.27
-> pitch, same USB-C, same WS2812B-2020, same button. What changed: **the switching regulator was
-> replaced**, **the antenna match was rebuilt**, and **the RGB LED lost its always-on supply** —
-> it now hangs off the switched backlight rail and needs **GPIO38 driven high** before it will
-> light. That last one is the only change that can break existing firmware.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH-A]** | `Sch_StampS3_v0.3.3-StampS3A.pdf`, Altium marker layer parsed, cited by designator | `executed-success` extraction |
-| **[SCH-3]** | `Sch_M5StampS3_v0.2.pdf` (the Stamp-S3), same method | `executed-success` |
-| **[DOC]** | <https://docs.m5stack.com/en/core/Stamp-S3A> and the DinMeter v1.1 page, 2026-09-04 | `not-tested` |
-| **[SRC]** | Source at a cited `file:line` | `executed-success` read |
-| **[INF]** | Inference | `inferred` |
-
-**No Stamp-S3A hardware was in hand.** Nothing here is measured.
-
----
-
-## 1. Identity, and the name
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketed name | **Stamp-S3A** | **[DOC]** |
-| SKU | **`S007-V033`** | **[DOC]** page header |
-| Documentation | <https://docs.m5stack.com/en/core/Stamp-S3A> (HTTP 200) | **[DOC]** |
-| Published schematic filename | **`Sch_StampS3_v0.3.3.pdf`** | **[SCH-A]** URL |
-| M5_Hardware product directory | `Products/S007-V033_Stamp-S3A/` | **[SRC]** |
-
-Three independent naming signals — SKU suffix `-V033`, schematic filename `v0.3.3`, and the
-directory name — all say the same thing: **the "A" is a marketing label for board revision
-v0.3.3 of the same S007 product**, not a new product line. The Stamp-S3's schematic is
-`Sch_M5StampS3_v0.2.pdf` (rev v0.2). **[SCH-A]** **[SCH-3]** **[INF]**
-
-That framing matters. It predicts — correctly, as §2 shows — that the changes would be
-incremental board-level fixes rather than a redesign.
-
----
-
-## 2. The complete Stamp-S3 → Stamp-S3A delta
-
-### 2.1 What the vendor says
-
-The Stamp-S3A page carries a two-row "Product Comparison" table and nothing else: **[DOC]**
-
-| Item | Stamp-S3A | Stamp-S3 |
-|---|---|---|
-| RGB LED control logic | "RGB LED power is multiplexed with the reserved screen FPC bus backlight" | "Powered as soon as power is applied" |
-| Antenna design | "Optimized antenna design with better signal reception" | "Conventional antenna design" |
-
-The DinMeter v1.1 page restates the first one in actionable form: **[DOC]**
-
-> "Stamp-S3A adds an independent electronic switch for the RGB LED power supply compared with the
-> previous Stamp-S3. Before controlling the RGB LED in software, set **GPIO38**, which controls
-> this switch, to a high level."
-
-### 2.2 What the schematics say
-
-Designator diff, from a full `CO`-marker census of both sheets plus visible designator text
-(retained at [`artifacts/stamp-s3-vs-s3a-designator-diff.txt`](artifacts/stamp-s3-vs-s3a-designator-diff.txt)):
-
-| | Designators |
-|---|---|
-| **Removed** in v0.3.3 | `D6`, `JP1`, `JP4`, **`M2`**, `R3`, `R6`, `R17` |
-| **Added** in v0.3.3 | `C15`, `C16`, `C18`, `C19`, `C20`, `C24`, `C25`, **`L4`**, `L6`, `L7`, **`U4`** |
-| Common (48) | `ANT1`, `C1`–`C14`, `C17`, `C21`–`C23`, `C26`, `D1`–`D4`, `D14`, `F1`, `J1`–`J3`, `JP2`, `JP3`, `L1`–`L3`, `L5`, `M1`, `PHD1`, `R1`, `R2`, `R4`, `R5`, `R7`, `R16`, `S1`, `U1`–`U3`, `X1` |
-
-Four changes fall out of that, in descending order of consequence.
-
----
-
-## 3. Change 1 — the RGB LED is no longer always powered *(firmware-visible)*
-
-`U2` is the load switch that gates the rear LCD-FPC backlight rail. Its enable is `DISP_BL` =
-**ESP32-S3 GPIO38** (`U1` pad 43) on **both** revisions. **[SCH-3]** **[SCH-A]**
-
-| | Stamp-S3 v0.2 | Stamp-S3A v0.3.3 |
-|---|---|---|
-| `U2` part | **`SGM2578`** (alt value text `WS4622C-4/TR`) | **`AW35122FDR`** |
-| `U2` `EN` | `DISP_BL` (GPIO38) | `DISP_BL` (GPIO38) |
-| `U2` `VOUT` net | FPC backlight only | **`BL_3V3`** |
-| `U3` (WS2812B-2020) `VDD` | **`VDD_3V3`** — always on | **`BL_3V3`** — switched |
-| `U3` `DI` | `SK_DIN` ← GPIO21 | `SK_DIN` ← GPIO21 |
-
-**[SCH-3]** `U2`@(509.5,69.7) value `SGM2578`@(520.5,121.4) + `WS4622C-4/TR`@(528.4,128.6);
-`U3` `VDD` net `VDD_3V3`@(607.1,125.0).
-**[SCH-A]** `U2`@(506.0,69.7) value `AW35122FDR`@(523.1,121.4); `U3` `VDD` net `BL_3V3`@(606.4,207.7).
-
-So the schematic reading and the vendor prose agree exactly. **This is the one change that
-breaks source compatibility**, and only for code that lights the RGB LED:
-
-```cpp
-// Works on Stamp-S3. Does nothing visible on Stamp-S3A.
-M5.Lcd /* ... */;  pixels.setPixelColor(0, red); pixels.show();
-
-// Portable across both:
-pinMode(38, OUTPUT);
-digitalWrite(38, HIGH);          // enable BL_3V3 -> WS2812 VDD (no-op on Stamp-S3)
-delay(1);                        // allow the rail to settle before the first WS2812 frame
-pixels.setPixelColor(0, red); pixels.show();
-```
-
-`inferred` — not built, not run on hardware. The GPIO number and the polarity are from the
-schematic and the vendor text; the settle delay is prudence, not a documented requirement.
-
-> **This affects the [DinMeter v1.1](../../../devices/m5stack/dinmeter-v1.1/README.md).** The
-> DinMeter carrier does not use GPIO38 for anything — it drives its own panel backlight from
-> GPIO9 through its own AW35122FDR. GPIO38 is entirely inside the module. So on DinMeter v1.1,
-> GPIO38 has exactly one job: turning the Stamp's status LED on.
->
-> **[SRC]** M5Unified's RGB-LED table gives `board_M5DinMeter → GPIO_NUM_21`
-> (`M5Unified/src/M5Unified.cpp:246`) and contains **no GPIO38 enable step for any board**
-> (checked at master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`, 2026-09-04). If M5Unified's
-> `board_M5DinMeter` path is used unchanged on a v1.1 unit, the RGB LED will not light. This is
-> a **predicted** defect from reading the source against the vendor note — it has **not** been
-> reproduced on hardware. Recorded as such in
-> [`devices/m5stack/dinmeter-v1.1/gaps-and-conflicts.md`](../../../devices/m5stack/dinmeter-v1.1/gaps-and-conflicts.md).
-
----
-
-## 4. Change 2 — the antenna front end was rebuilt
-
-| | Stamp-S3 v0.2 | Stamp-S3A v0.3.3 |
-|---|---|---|
-| `ANT1` part text | **`PROANT440`** | **none printed** |
-| Match elements between `ANT1` and `ESP_LNA` | `L1` 2.2 nH, `C1` 2.2 pF, `C2` 2.0 pF | `L6` (0 R), `C19`, `C20` (**NC**), `L1` 2.7 nH, `C2` 2.2 pF, `C1` 1.8 pF, values `4.3 nH` / `0R` present |
-| Extra network on `ESP_EN` / `U1` pad 4 | none | `L7` 0 R + `C24` (3 pF) |
-| `C9` (crystal network) | 10 pF | 12 pF |
-| `C8` | 100 nF/25 V | 3 pF/25 V |
-| `L2` adjacent values | `12 pF`, `2 nH` | `2 nH` |
-
-**[SCH-3]** / **[SCH-A]**, from the value text nearest each `CO` marker.
-
-Two honest caveats:
-
-1. **Value-to-designator association is nearest-neighbour**, and the antenna corner is dense.
-   `C19 ≈ 4.3 nH` is physically odd for a capacitor and probably belongs to `L6`; treat the
-   individual antenna values as indicative, and the *topology* change (3 elements → 6, plus a
-   filter on `ESP_EN`) as solid.
-2. **`PROANT440` does not appear anywhere on the v0.3.3 sheet** (searched in both single and
-   double-struck glyph forms; zero hits). Either the antenna part changed, or the value text was
-   dropped. **Not established which.**
-
-The vendor's claim is qualitative — "better signal reception" — with **no measured figure**
-(no dBi, no RSSI comparison, no test method). Nothing here corroborates or refutes it.
-
----
-
-## 5. Change 3 — the DC-DC was replaced *(and the datasheet page is stale)*
-
-| | Stamp-S3 v0.2 | Stamp-S3A v0.3.3 |
-|---|---|---|
-| Designator | `M2` | `U4` |
-| Part | **`MUN3CAD01-SC`** (µPOL module, 1 A, integrated inductor, 2.9 × 2.3 × 1.05 mm) | **not printed on the sheet** |
-| Pins | 6: `EN`, `GND`, `VIN`, `GND`, `FB`, `VOUT` | 8 balls: `A1 SW`, `A2 VIN`, `B1 EN`, `B2 GND`, `C1 VSEL1`, `C2 VOS`, `D1 VSEL2`, `D2 VSEL3` |
-| Annotation | — | **`IOUT: 0~0.6A`** |
-| External inductor | none | **`L4` = `MWTC201608S2R2`** (2.2 µH, 2016 metric / 0806) |
-| Output set by | `R6` 100 kΩ / `R17` 22.1 kΩ feedback divider | **pin-strapped** `VSEL1/2/3` (no divider — `R6`/`R17` deleted) |
-| Support passives | `C21`, `C22` 10 µF | `C15` 1 nF, `C16` 10 µF, `C18` 100 nF, `C21`/`C22`/`C25` 10 µF |
-
-**[SCH-3]** `M2`@(207,476.7), `MUN3CAD01-SC`@(228.7,513.7).
-**[SCH-A]** `U4`@(185,465.7), ball labels at (174.1,474.2)…(218.8,535.3), `IOUT: 0~0.6A`@(209.4,452.6),
-`L4`@(300,470.7) value `MWTC201608S2R2`@(307.2,463.4).
-
-> ### ⚠ Conflict: the Stamp-S3A page still lists MUN3CAD01-SC
->
-> The Stamp-S3A specification table gives **`DC-DC: MUN3CAD01-SC`** and links its datasheet at
-> `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/Stamp/S007%20StampS3/MUN3CAD01-SC.pdf`
-> — the *same* path the Stamp-S3 page uses (note the `S007 StampS3` directory). **[DOC]**
->
-> The string `MUN3CAD01` **does not occur anywhere** in `Sch_StampS3_v0.3.3.pdf`. The part it
-> names is a µPOL module with an *integrated* inductor and an `FB` pin; the v0.3.3 design fits a
-> part with an external 2.2 µH inductor and three `VSEL` strapping balls. These are not the same
-> device.
->
-> **Reading:** the specification row was carried over unedited from the Stamp-S3 page. The
-> schematic is the stronger evidence. `U4`'s actual part number is **unidentified** — recorded
-> at [`components/unidentified/m5stack-stamp-s3a/dcdc-u4/`](../../unidentified/m5stack-stamp-s3a/dcdc-u4/README.md)
-> rather than guessed. **No candidate part number is asserted anywhere in this repository.**
-
----
-
-## 6. Change 4 — `ESP_EN` and GPIO2 support parts
-
-| | v0.2 | v0.3.3 |
-|---|---|---|
-| `D6` 1N4148WT on `ESP_EN` | present | **removed** |
-| `R7` 10 kΩ, `R16` 100 kΩ, `C23` 1 µF on `ESP_EN` | present | present |
-| `L7` 0 R + `C24` on `ESP_EN` | — | **added** |
-| `R3` 10 kΩ/1 % on GPIO2 | present | **removed** |
-| `JP1`, `JP4` | present | **removed** |
-
-**[SCH-3]** **[SCH-A]** Effect not analysed; recorded for completeness.
-
----
-
-## 6b. The FPC numbering question
-
-`J1` (12-pin) and `J3` (8-pin) rear LCD headers carry the **same nets in the same physical
-order** on both revisions, but the **pin numbers run in opposite directions**:
-
-| | v0.2 | v0.3.3 |
-|---|---|---|
-| `J1` pin carrying `VIN_5V` | **1** | **12** |
-| `J1` pin carrying `DISP_CS` | **12** | **1** |
-| `J3` pin carrying `DISP_CS` | **8** | **1** |
-| `J3` pin carrying GPIO2 node | **1** | **8** |
-
-**[SCH-3]** / **[SCH-A]** from `PIJ10x` / `PIJ30x` markers.
-
-**This is not resolved.** It is either (a) a physical re-orientation of the FPC connector, which
-would mean an existing display flex mates backwards, or (b) a symbol renumbering that was
-mirrored in the footprint, which would mean nothing changed physically. The schematic alone
-cannot distinguish them.
-
-Weight of evidence leans to **(b)**: the connector part number is unchanged
-(`HDGC/0.5K-HX-8PWB/NC`), `m5stack/M5_Hardware` publishes **no Stamp-S3A footprint**, and
-`Stamp-S3A.stl` is byte-identical to `Stamp-S3.stl`. But that is inference. Anyone attaching a
-display flex to the back of a Stamp-S3A should verify against the official pin-map image
-([`artifacts/S007-V033_PinMap_01.jpg`](artifacts/S007-V033_PinMap_01.jpg)) before powering up.
-**[INF]**
-
-**It does not affect the DinMeter.** The DinMeter drives its panel from carrier GPIOs through
-its own `FPC1`, not through the Stamp's rear header.
-
----
-
-## 7. Mechanical
-
-| Property | Stamp-S3 | Stamp-S3A | Evidence |
-|---|---|---|---|
-| Product size | 24.0 × 18.0 × 4.7 mm | **26.0 × 18.0 × 4.7 mm** | **[DOC]** both pages |
-| Weight | 3.0 g | 2.9 g | **[DOC]** |
-| Package size | 138.0 × 93.0 × 10.5 mm | 138.0 × 93.0 × 10.5 mm | **[DOC]** |
-| Published STL | `Stamp-S3.stl` | `Stamp-S3A.stl` | **[SRC]** |
-| STL SHA-256 | `f72c1af2d42930fc57a3db1bd3282568a3952095f77539016a12437d59d7df5d` | **identical** | **[SRC]** |
-| Published KiCad footprint | `Stamp-S3-SMD` / `-DIP` / `_PIN1.27_Socket` / `_PIN2.54_DIP` | **none** | **[SRC]** |
-
-> ### ⚠ Conflict: 24 mm vs 26 mm
->
-> The two specification tables differ by 2 mm in length, but the two mechanical models are the
-> same bytes and no new footprint was published. One of the two is wrong, and the vendor has not
-> said which. A 2 mm growth would be a breaking change for any host PCB — and yet **M5Stack ships
-> the Stamp-S3A on the DinMeter v1.1 carrier whose published PCB assets are unchanged from
-> v1.0**, which argues the footprint did not grow. **[INF]**
->
-> **Practical advice:** if you are laying out a board for a Stamp-S3A, measure a real part or ask
-> M5Stack. Do not trust either number. This is recorded in
-> [`devices/m5stack/dinmeter/gaps-and-conflicts.md`](../../../devices/m5stack/dinmeter/gaps-and-conflicts.md) §5.
-
-Dimension drawing: [`artifacts/STAMP-S3A-dimensions.pdf`](artifacts/STAMP-S3A-dimensions.pdf).
-
----
-
-## 8. Power — the headline improvement
-
-| Mode | Supply | Stamp-S3 | Stamp-S3A | Change |
-|---|---|---|---|---|
-| Sleep | USB Type-C | 400.67 µA | **88.82 µA** | **−78 %** |
-| Sleep | `VIN_5V` | 310.89 µA | **6.84 µA** | **−98 %** (≈ 45×) |
-| Standby | USB Type-C | 33.04 mA | **25.54 mA** | −23 % |
-| Standby | `VIN_5V` | 33.56 mA | **25.53 mA** | −24 % |
-
-**[DOC]** both product pages. **Vendor figures, no stated method** — no clock configuration, no
-radio state, no peripheral state, no instrument, no sample count. They are quoted to two decimal
-places, which implies more precision than an unspecified method can support. Do not size a
-battery from them without measuring.
-
-Mechanistically the improvement is consistent with the two power changes: a modern buck IC with
-selectable light-load modes replacing a fixed µPOL module, plus removing the WS2812B's quiescent
-draw from the always-on 3.3 V rail (a WS2812B-2020 idles around 0.6–1 mA). **[INF]** — plausible
-but not decomposed or measured.
-
-The `VIN_5V` sleep figure (6.84 µA) is startling and is the single strongest reason to prefer
-the S3A for a battery product.
-
----
-
-## 9. What did *not* change
-
-Stated positively so the absence is a finding, not an omission:
-
-| Property | Both revisions | Evidence |
-|---|---|---|
-| SoC | ESP32-S3FN8, Xtensa LX7 dual-core @ 240 MHz | **[DOC]** both; **[SCH]** `U1` symbol on both |
-| Flash | 8 MB in-package | **[DOC]** |
-| **PSRAM** | **none, on either** | **[DOC]** — no PSRAM row on either page; `FN8` has none |
-| Broken-out GPIOs | 23 — G0, G1–G15, G39–G44, G46 — **identical list** | **[DOC]** both pages |
-| Internal GPIO21 | WS2812B-2020 data | **[SCH]** both, `U1` pad 27 |
-| Internal GPIO33–38 | rear FPC `DISP_RST/RS/MOSI/SCK/CS/BL` | **[SCH]** both, `U1` pads 38–43 |
-| USB | native USB-C, `J2`, `R1`/`R2` 5.1 kΩ CC | **[SCH]** both |
-| RGB LED part | WS2812B-2020 ×1 | **[DOC]** both |
-| User button | ×1 on GPIO0 | **[DOC]** both |
-| Crystal | `X1` + `L3` 10 nH | **[SCH]** both |
-| IO pitch | 2.54 mm and 1.27 mm | **[DOC]** both |
-| LCD FPC pitch | 0.5 mm, 12 P or 8 P | **[DOC]** both |
-| Operating temp | 0 – 40 °C | **[DOC]** both |
-| Download mode | hold `G0` while applying power | **[DOC]** both |
-| Price | USD 7.50 (S3A, 2026-09-04) | **[DOC]** shop |
-
----
-
-## 10. Is firmware source-compatible?
-
-**Yes, with exactly one exception.**
-
-| Aspect | Verdict | Basis |
-|---|---|---|
-| Toolchain / target | Identical (`esp32s3`, no PSRAM) | **[DOC]** |
-| Pin assignments for user IO | Identical | **[DOC]** |
-| M5Unified board enum | **Unchanged** — there is **no `board_M5StampS3A`** in M5Unified master `8530f537…` (2026-09-04). An S3A enumerates as `board_M5StampS3` | **[SRC]** grep of `src/` |
-| DinMeter board enum | `board_M5DinMeter` for both v1.0 and v1.1 — M5Unified has no v1.1 variant | **[SRC]** |
-| Display, encoder, RTC, buzzer, I²C, power-hold | Identical | **[SRC]** **[SCH]** |
-| **RGB LED** | **Breaks.** Needs `GPIO38 = HIGH` first on S3A | **[DOC]** **[SCH-A]** |
-| Boot / download procedure | Identical | **[DOC]** |
-| Antenna / RF behaviour | Different silicon-external network; no API impact | **[SCH]** |
-
-So: recompile nothing, change nothing — unless you use the RGB LED.
-
----
-
-## 11. Artifacts
-
-| File | Size | SHA-256 (16) | What it is | Licence | Redistribution | Disposition |
-|---|---:|---|---|---|---|---|
-| [`artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf`](artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf) | 369 766 | `2f9610aecc5a5d2e` | **Primary evidence.** Board rev v0.3.3 schematic. Renamed from upstream `Sch_StampS3_v0.3.3.pdf` to record that it is the S3A's | unknown | unknown | repository |
-| [`artifacts/Sch_StampS3_v0.3.3-StampS3A.plaintext-layout.txt`](artifacts/Sch_StampS3_v0.3.3-StampS3A.plaintext-layout.txt) | 7 830 | `0dddf2cc41d9f6e2` | derived: sheet text as rows | derived | — | repository |
-| [`artifacts/stamp-s3-vs-s3a-designator-diff.txt`](artifacts/stamp-s3-vs-s3a-designator-diff.txt) | 716 | `8278f9ab8975d7c5` | derived: the census diff behind §2.2 | derived | — | repository |
-| [`artifacts/STAMP-S3A-dimensions.pdf`](artifacts/STAMP-S3A-dimensions.pdf) | 95 380 | `27ba520610b03e41` | mechanical drawing | unknown | unknown | repository |
-| [`artifacts/Stamp-S3A.stl`](artifacts/Stamp-S3A.stl) | 158 484 | `f72c1af2d42930fc` | mechanical model — **byte-identical to `Stamp-S3.stl`** | unknown | unknown | repository |
-| [`artifacts/S007-V033_PinMap_01.jpg`](artifacts/S007-V033_PinMap_01.jpg) | 693 286 | `979f3572d60fd9ef` | official pin-map diagram | unknown | unknown | repository |
-
-Upstream URLs and retrieval dates: [`devices/m5stack/dinmeter/sources.md`](../../../devices/m5stack/dinmeter/sources.md)
-(rows S-14 … S-20). `Stamp-S3A.stl` was fetched from `m5stack/M5_Hardware` at commit
-`a240115c94b19ecf647f229c47fa9a8ce46ccdc4`.
-
-**Deliberate duplication:** `Stamp-S3.stl` and `Stamp-S3A.stl` have the same SHA-256 and are both
-retained, one under each component. That is intentional — the *fact* that M5Stack publishes the
-same bytes under two product names is the finding, and deduplicating would erase it. Roughly
-158 KB of redundancy, accepted.
-
-## Related components
-
-- [`components/awinic/aw35122`](../../awinic/aw35122/README.md) — `U2` on this module
-- [`components/sgmicro/sgm2578`](../../sgmicro/sgm2578/README.md) — `U2` on the Stamp-S3
-- [`components/murata/mun3cad01-sc`](../../murata/mun3cad01-sc/README.md) — `M2` on the Stamp-S3, *not* fitted here
-- [`components/unidentified/m5stack-stamp-s3a/dcdc-u4`](../../unidentified/m5stack-stamp-s3a/dcdc-u4/README.md) — `U4`, this module's actual regulator
-- [`components/espressif/esp32-s3r8`](../../espressif/esp32-s3r8/README.md) — the SoC family
-
----
-
-## Used By
-
-### M5Stack DinMeter v1.1 (SKU K134-V11)
-
-Fitted as **`M1`** on a carrier whose published schematic and STL are byte-identical to the
-v1.0 board's. The GPIO map is unchanged from v1.0 in every respect — display, encoder, RTC,
-buzzer, button, power hold, Grove ports. **[DOC]** The substitution of this module for the
-Stamp-S3 *is* the v1.1 revision.
-
-The one behavioural consequence on this carrier: the Stamp's RGB LED (GPIO21) now requires
-**GPIO38 high** first. GPIO38 is not otherwise used on the DinMeter, so there is no conflict —
-just a required extra line.
-
-→ [`devices/m5stack/dinmeter-v1.1/README.md`](../../../devices/m5stack/dinmeter-v1.1/README.md)
-
-### Other M5Stack products carrying Stamp-S3A
-
-Observed on `shop.m5stack.com` 2026-09-04 (search evidence, not exhaustive): **Air Quality Kit
-v1.1 with M5StampS3A (SEN55, SCD40)**, USD 89.90. Also sold standalone as `M5StampS3A ESP32S3
-Module` (USD 7.50), `M5StampS3A with 1.27 Header Pin` (7.50) and `M5StampS3A with 2.54 Header
-Pin` (7.50). **[DOC]**
-
-### Devices carrying this module
-
-| Device | Record | Notes |
-|---|---|---|
-| **Cardputer ADV** (`K132-Adv`) | [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md) | mainboard redesigned around the module's freed pins: TCA8418 keyboard on I²C, CAP expansion header |
-| **Cardputer v1.1** (`K132-V11`) | [`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md) | **module-only refresh** of the v1.0 — the two mainboard schematics are byte-identical, SHA-256 `6016c1fe…` |
-| **Cardputer Mesh Kit** (`K152`) | [`devices/m5stack/cardputer-mesh-kit`](../../../devices/m5stack/cardputer-mesh-kit/README.md) | ADV + Cap LoRa-1262 bundle |
-| Cardputer Accessory Kit v1.1 | — | sold as a spare: Stamp-S3A + display, $9.95 at 2026-09-04 |
-
-**How software tells this module's boards apart from Stamp-S3 boards:** it does not — M5GFX
-discriminates on the *mainboard*, by driving G9/G8/G6/G5 as input-pulldown and testing whether
-G8 and G9 still read high (the ADV's internal-I²C pull-ups). See
-[`devices/m5stack/cardputer-adv/README.md` § Board autodetect](../../../devices/m5stack/cardputer-adv/README.md).
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.9.*
diff --git a/components/m5stack/stamp-s3a/acquisition/manifest.json b/components/m5stack/stamp-s3a/acquisition/manifest.json
deleted file mode 100644
index 6005ee6..0000000
--- a/components/m5stack/stamp-s3a/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "components/m5stack/stamp-s3a",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AN3WM5STAMPS3A-8045263",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPS3A/Test-Report/AiTDG-241205002W1-Test-Report-BLE-8045263.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045263",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045263.pdf",
-    "https://fccid.io/2AN3WM5STAMPS3A",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/Test-Report/AiTDG-241205002W1-Test-Report-BLE-8045263.pdf"
-   ],
-   "sha256": "027dd133c4ac00b6223a7c52ef2bf5e7831e00cfcfb4188e5e0bd872263082f0",
-   "bytes": 959274,
-   "destination": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-02-13",
-   "fcc_id": "2AN3WM5STAMPS3A",
-   "fcc_document_id": "8045263",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "AiTDG-241205002W1-Test Report BLE",
-   "grant_date": "2025-02-13",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf",
-   "placeholder": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-s3a",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPS3A-8045271",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPS3A/External-Photos/External-Photos-8045271.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045271",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045271.pdf",
-    "https://fccid.io/2AN3WM5STAMPS3A",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/External-Photos/External-Photos-8045271.pdf"
-   ],
-   "sha256": "6910fdc8e5f4691389cb89c8f277a3ef50ebd4038089d632a0d0daef4456773a",
-   "bytes": 2142184,
-   "destination": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-02-13",
-   "fcc_id": "2AN3WM5STAMPS3A",
-   "fcc_document_id": "8045271",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2025-02-13",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf",
-   "placeholder": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-s3a",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPS3A-8045273",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPS3A/RF-Exposure-Info/FCC-RF-Exposure-MPE-20cm-8045273.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045273",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045273.pdf",
-    "https://fccid.io/2AN3WM5STAMPS3A",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/RF-Exposure-Info/FCC-RF-Exposure-MPE-20cm-8045273.pdf"
-   ],
-   "sha256": "db49d95ade5911cc7a0d60ebd93a084c7dd4ef2187ba2b48a33e3d5a1387833c",
-   "bytes": 176710,
-   "destination": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-02-13",
-   "fcc_id": "2AN3WM5STAMPS3A",
-   "fcc_document_id": "8045273",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "FCC RF Exposure-MPE (20cm)",
-   "grant_date": "2025-02-13",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf",
-   "placeholder": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-s3a",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPS3A-8045274",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPS3A/Internal-Photos/Internal-Photos-8045274.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045274",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045274.pdf",
-    "https://fccid.io/2AN3WM5STAMPS3A",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/Internal-Photos/Internal-Photos-8045274.pdf"
-   ],
-   "sha256": "e6512283b0e419c2b366b5d9dc3076ed3e6866f32e3baaaae6d7d731a68b8f13",
-   "bytes": 2778287,
-   "destination": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-02-13",
-   "fcc_id": "2AN3WM5STAMPS3A",
-   "fcc_document_id": "8045274",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2025-02-13",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-s3a",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPS3A-8045275",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPS3A/Label/label-and-location-8045275.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045275",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045275.pdf",
-    "https://fccid.io/2AN3WM5STAMPS3A",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/Label/label-and-location-8045275.pdf"
-   ],
-   "sha256": "60d9ccb36cc10e2aeff65a90960e8861d36fa6a45fbdc5aaa782b5c3b067aa02",
-   "bytes": 69357,
-   "destination": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-label-and-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-02-13",
-   "fcc_id": "2AN3WM5STAMPS3A",
-   "fcc_document_id": "8045275",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "label and location",
-   "grant_date": "2025-02-13",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-s3a",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPS3A-8045295",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPS3A/User-Manual/User-Manual-8045295.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045295",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045295.pdf",
-    "https://fccid.io/2AN3WM5STAMPS3A",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/User-Manual/User-Manual-8045295.pdf"
-   ],
-   "sha256": "e9056d899bdd6cda96095105baae754c440e9a8cf32bd48499d027a58c5c9cd1",
-   "bytes": 2308121,
-   "destination": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-02-13",
-   "fcc_id": "2AN3WM5STAMPS3A",
-   "fcc_document_id": "8045295",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2025-02-13",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf",
-   "placeholder": "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "components/m5stack/stamp-s3a",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg b/components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg
deleted file mode 100644
index 9ae6d36..0000000
Binary files a/components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg and /dev/null differ
diff --git a/components/m5stack/stamp-s3a/artifacts/STAMP-S3A-dimensions.pdf b/components/m5stack/stamp-s3a/artifacts/STAMP-S3A-dimensions.pdf
deleted file mode 100644
index ae6b5ee..0000000
Binary files a/components/m5stack/stamp-s3a/artifacts/STAMP-S3A-dimensions.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf b/components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf
deleted file mode 100644
index 8e2f214..0000000
Binary files a/components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.plaintext-layout.txt b/components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.plaintext-layout.txt
deleted file mode 100644
index b2416bf..0000000
--- a/components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.plaintext-layout.txt
+++ /dev/null
@@ -1,141 +0,0 @@
-y=  31.2 | [109]1  [315]2  [523]3  [729]4
-y=  42.0 | [783]J1
-y=  48.5 | [47]ANT1
-y=  50.4 | [464]LCD
-y=  52.8 | [703]VIN_5V  [789]12
-y=  56.4 | [258]U1  [733]GPIO18
-y=  61.2 | [67]L6  [128]L1  [789]11  [806]C
-y=  63.6 | [185]ESP_LNA  [248]1  [341]5  [364]GPIO0  [733]GPIO17  [806]N
-y=  67.2 | [271]LNA_IN  [320]GPIO0  [789]10  [806]/
-y=  70.8 | [74]0R  [133]2.7nH  [341]6  [364]GPIO1  [463]VDD_3V3  [507]U2  [604]BL_3V3  [690]J3  [733]GPIO16  [806]B
-y=  74.4 | [320]GPIO1  [787]9  [806]W
-y=  77.3 | [65]C19  [98]C20  [125]C2  [161]C1  [341]7  [364]GPIO2  [493]A2  [563]A1  [680]8
-y=  79.5 | [806]P
-y=  84.7 | [68]4.3nH  [97]NC  [129]2.2pF  [165]1.8pF  [204]L7  [320]GPIO2  [514]VIN  [539]VOUT  [787]8  [806]2
-y=  85.4 | [187]ESP_EN  [218]0R  [247]4  [341]8  [364]GPIO3  [680]7  [806]1
-y=  89.0 | [272]CHIP_PU  [320]GPIO3  [787]7  [806]-
-y=  92.6 | [13]A  [205]C24  [341]9  [364]GPIO4  [474]C3  [563]B2  [636]DISP_RST  [679]6  [737]DISP_RST  [806]X  [827]A
-y=  96.2 | [320]GPIO4  [544]EN  [787]6  [806]H
-y=  99.8 | [31]GND  [343]10  [364]GPIO5  [485]100nF/25V  [635]DISP_RS  [680]5  [735]DISP_RS  [806]-
-y= 103.4 | [170]GND  [320]GPIO5  [787]5
-y= 107.0 | [342]11  [364]GPIO6  [494]B1  [639]DISP_MOSI  [679]4  [739]DISP_MOSI  [806]K
-y= 108.2 | [806]5
-y= 110.6 | [320]GPIO6  [515]GND  [787]4  [806].  [806]0
-y= 114.2 | [53]GND  [205]3pF  [245]29  [343]12  [364]GPIO7  [637]DISP_SCK  [680]3  [738]DISP_SCK  [806]/
-y= 117.8 | [144]FLASH_VCC  [273]VDD_SPI  [320]GPIO7  [787]3  [806]C
-y= 121.4 | [343]13  [364]GPIO8  [523]AW35122FDR  [680]2
-y= 125.0 | [320]GPIO8  [592]VDD_3V3  [787]2  [806]G
-y= 127.8 | [184]C26  [226]C4  [343]14  [364]GPIO9  [463]GND  [635]DISP_CS  [680]1  [735]DISP_CS  [806]D
-y= 132.2 | [320]GPIO9  [516]DISP_BL  [787]1
-y= 135.0 | [193]100nF/25V  [233]1uF/10V  [245]30  [343]15  [366]GPIO10  [806]H
-y= 139.3 | [269]SPIHD  [318]GPIO10
-y= 142.9 | [246]31  [343]16  [366]GPIO11  [724]HDGC/0.5K-HX-8PWB/NC
-y= 146.5 | [269]SPIWP  [318]GPIO11
-y= 150.1 | [245]32  [343]17  [366]GPIO12
-y= 154.9 | [99]L3  [270]SPICS0  [318]GPIO12
-y= 157.3 | [246]33  [343]18  [366]GPIO13
-y= 160.9 | [270]SPICLK  [318]GPIO13  [658]GND  [759]GND
-y= 164.5 | [215]GND  [245]34  [343]19  [366]GPIO14
-y= 166.7 | [103]10nH
-y= 168.1 | [266]SPIQ  [318]GPIO14
-y= 171.7 | [92]X1  [246]35
-y= 175.3 | [266]SPID  [543]BL_3V3
-y= 178.9 | [82]1  [125]4  [343]21  [366]GPIO15
-y= 182.5 | [155]GND  [309]XTAL_32K_P  [465]RGB  [491]LED  [651]U3
-y= 186.1 | [216]XTAL_40M_P  [245]54  [343]22  [366]GPIO16
-y= 189.7 | [271]XTAL_P  [309]XTAL_32K_N  [615]SK_DIN  [640]3  [698]2
-y= 192.6 | [49]C9  [81]2  [125]3  [343]23  [366]GPIO17  [656]DI  [678]GND  [728]GND
-y= 196.1 | [555]C17
-y= 199.7 | [52]12pF  [318]GPIO17
-y= 200.5 | [343]24  [366]GPIO18
-y= 204.1 | [318]GPIO18  [563]10uF/10V  [640]4  [698]1  [719]SK_DOUT
-y= 207.7 | [97]40Mhz  [343]25  [372]USB_DU_N  [606]BL_3V3  [659]VDD  [681]DO
-y= 211.2 | [318]GPIO19
-y= 214.8 | [74]GND  [129]C14  [217]XTAL_40M_N  [246]53  [343]26  [371]USB_DU_P
-y= 218.4 | [272]XTAL_N  [318]GPIO20  [658]WS2812
-y= 222.0 | [343]27  [366]GPIO21  [399]SK_DIN
-y= 225.6 | [95]GND  [318]GPIO21
-y= 229.2 | [13]B  [38]GND  [343]28  [827]B
-y= 232.8 | [319]SPICS1  [543]GND
-y= 236.4 | [138]12pF12pF  [247]2
-y= 240.0 | [271]VDD3P3
-y= 243.6 | [35]VDD_3V3  [247]3  [343]36
-y= 247.2 | [271]VDD3P3  [314]SPICLK_N
-y= 248.4 | [175]L2  [343]37  [666]M1
-y= 251.9 | [481]BTN-USER
-y= 254.6 | [314]SPICLK_P
-y= 260.4 | [177]2nH  [343]38  [366]GPIO33  [395]DISP_RST  [631]GPIO1  [655]1
-y= 261.8 | [318]GPIO33  [670]G1
-y= 264.7 | [46]C5  [81]C6  [118]C7  [161]C8  [245]20  [343]39  [366]GPIO34  [393]DISP_RS  [631]GPIO2  [654]2
-y= 269.0 | [210]VDD_3V3  [279]VDD3P3_RTC  [318]GPIO34  [678]G2
-y= 271.9 | [55]10uF/10V  [89]1uF/10V  [129]100nF/25V  [169]3pF/25V  [343]40  [366]GPIO35  [397]DISP_MOSI  [631]GPIO3  [655]3
-y= 276.2 | [318]GPIO35  [670]G3
-y= 279.8 | [343]41  [366]GPIO36  [395]DISP_SCK  [474]VDD_3V3  [631]GPIO4  [654]4
-y= 283.4 | [318]GPIO36  [678]G4
-y= 287.0 | [245]46  [343]42  [366]GPIO37  [393]DISP_CS  [631]GPIO5  [654]5
-y= 290.6 | [210]VDD_3V3  [279]VDD3P3_CPU  [318]GPIO37  [670]G5
-y= 294.2 | [343]43  [366]GPIO38  [393]DISP_BL  [631]GPIO6  [654]6  [799]VDD_3V3
-y= 297.8 | [318]GPIO38  [678]G6
-y= 301.4 | [35]GND  [71]GND  [107]GND  [150]GND  [343]44  [366]GPIO39  [481]R4  [631]GPIO7  [654]7  [742]28
-y= 305.0 | [319]MTCK  [670]G7  [723]3V3
-y= 308.6 | [343]45  [366]GPIO40  [488]10K/1%  [631]GPIO8  [654]8  [742]27  [766]GPIO46
-y= 312.2 | [319]MTDO  [532]S1  [678]G8  [716]G46  [817]B
-y= 315.7 | [60]VDD_3V3  [103]VDD_3V3  [516]GPIO0  [631]GPIO9  [654]9  [742]26  [767]TX  [817]3
-y= 319.3 | [670]G9  [718]G43/Tx  [817]V
-y= 322.9 | [246]55  [343]47  [366]GPIO41  [492]B  [633]GPIO10  [653]10  [742]25  [766]GPIO42  [817]3
-y= 326.5 | [145]VDD_3V3  [270]VDDA1  [320]MTDI  [492]3  [679]G10  [706]G42/MTMS  [817]D
-y= 330.1 | [245]56  [343]48  [366]GPIO42  [492]V  [653]11  [742]24  [767]RX
-y= 333.7 | [270]VDDA2  [319]MTMS  [527]SMT_SW_1TS026A  [674]GND  [718]G44/Rx  [817]F
-y= 336.6 | [72]C10  [116]C11  [188]C12  [224]C13  [343]49  [363]R5  [399]TX  [486]D1  [492]3  [604]VIN_5V  [633]GPIO11  [653]12  [742]23  [766]GPIO41  [810]D2  [817]2
-y= 338.5 | [492]D  [817]C
-y= 343.8 | [82]100nF/25V  [125]100nF/25V  [194]1uF/10V  [230]1nF/25V  [318]U0TXD  [492]F  [679]G11  [707]G41/MTDI  [817]N
-y= 344.5 | [343]50  [363]RX  [396]510R/1%  [492]2  [653]13  [742]22  [767]EN
-y= 348.1 | [318]U0RXD  [492]C  [561]GND  [670]5V  [724]EN  [817]D
-y= 351.7 | [343]51  [633]GPIO12  [653]14  [742]21  [766]GPIO40  [817]S
-y= 355.3 | [318]GPIO45  [492]N  [679]G12  [705]G40/MTDO  [817]E
-y= 358.9 | [246]57  [343]52  [366]GPIO46  [492]D  [633]GPIO13  [653]15  [742]20  [764]GPIO0
-y= 362.5 | [266]GND  [318]GPIO46  [672]G13  [717]G0/Boot  [817]P
-y= 366.1 | [13]C  [492]S  [633]GPIO14  [653]16  [742]19  [766]GPIO39  [827]C
-y= 367.4 | [492]E
-y= 371.2 | [492]P  [679]G14  [705]G39/MTCK
-y= 373.3 | [60]GND  [103]GND  [273]ESP32-S3FN8  [633]GPIO15  [653]17  [742]18
-y= 376.9 | [672]G15  [722]GND
-y= 380.5 | [175]GND  [211]GND  [233]GND  [474]GND
-y= 387.7 | [679]STAMP-S3M
-y= 394.8 | [799]GND
-y= 403.2 | [43]ESP32  [640]GND
-y= 428.3 | [44]DCDC  [470]Type-A  [502]USB
-y= 438.2 | [42]VDD_3V3  [475]JP3
-y= 445.4 | [787]VIN_5V
-y= 452.6 | [209]IOUT:  [229]0~0.6A
-y= 454.8 | [654]J2  [743]F1
-y= 459.1 | [48]R7
-y= 459.8 | [494]USB_DU_P  [560]USB_D_P  [642]A6
-y= 463.4 | [307]MWTC201608S2R2  [665]DP1VCC
-y= 466.3 | [55]10K/1%  [186]U4  [406]VDD_3V3  [642]B6  [688]A5  [701]R1  [810]B
-y= 471.8 | [301]L4  [660]DP2  [671]CC1  [757]6V/1A/PPTC  [810]V
-y= 474.2 | [53]ESP_EN  [78]EN  [174]B1  [242]A1  [494]USB_DU_N  [560]USB_D_N  [642]A7  [810]5
-y= 477.8 | [192]EN  [223]SW  [660]DN1  [671]CC2  [688]B5  [719]5.1K/1%
-y= 481.4 | [255]VDD_3V3  [801]D14  [810]D
-y= 482.4 | [518]L5  [642]B7  [665]DN2GND  [810]F
-y= 487.8 | [54]C23  [162]R16  [289]C15  [339]C21  [379]C22  [418]C25  [712]R2  [810]2
-y= 488.6 | [242]C2  [601]B  [633]B  [810]C
-y= 492.2 | [221]VOS  [601]3  [633]3  [667]SHELL
-y= 495.0 | [60]1uF/10V  [169]100K/1%  [295]1nF/25V  [347]10uF/10V  [386]10uF/10V  [426]10uF/10V  [601]V  [633]V  [810]N
-y= 499.3 | [507]PHD1  [601]3  [633]3  [668]USB-TYPEC  [719]5.1K/1%  [810]D
-y= 502.9 | [13]D  [173]A2  [594]D3  [627]D4  [810]S  [827]D
-y= 506.5 | [83]VIN_5V  [193]VIN  [601]D  [633]D
-y= 510.1 | [254]VIN_5V  [601]F  [633]F  [810]E
-y= 510.8 | [474]JP2  [601]2  [633]2  [810]P
-y= 516.6 | [116]C16  [159]C18  [520]phd_3mm  [601]C  [633]C
-y= 517.3 | [242]C1
-y= 520.9 | [219]VSEL1  [601]N  [633]N  [687]GND  [730]GND
-y= 524.5 | [42]GND  [123]10uF/10V  [168]100nF/25V  [242]D1  [276]GND  [406]GND  [601]D  [633]D  [788]GND
-y= 528.1 | [218]VSEL2  [601]S  [633]S
-y= 531.7 | [173]B2  [242]D2
-y= 535.3 | [194]GND  [218]VSEL3  [601]E  [633]E
-y= 536.8 | [601]P  [633]P
-y= 546.1 | [193]JW5712  [582]GND  [615]GND
-y= 549.7 | [499]GND
-y= 553.3 | [103]GND
-y= 564.1 | [109]1  [315]2  [523]3  [729]4
diff --git a/components/m5stack/stamp-s3a/artifacts/Stamp-S3A.stl b/components/m5stack/stamp-s3a/artifacts/Stamp-S3A.stl
deleted file mode 100644
index 3f82f65..0000000
Binary files a/components/m5stack/stamp-s3a/artifacts/Stamp-S3A.stl and /dev/null differ
diff --git a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf.ARCHIVED.md b/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf.ARCHIVED.md
deleted file mode 100644
index 13840a4..0000000
--- a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 959,274 B (0.91 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 959,274 B (0.91 MiB) |
-| SHA-256 | `027dd133c4ac00b6223a7c52ef2bf5e7831e00cfcfb4188e5e0bd872263082f0` |
-| FCC ID | **`2AN3WM5STAMPS3A`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | AiTDG-241205002W1-Test Report BLE |
-| FCC document id | 8045263 |
-| Upstream publication date | 2025-02-13 |
-| Grant date | 2025-02-13 |
-| Equipment class | M5StampS3A, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPS3A/Test-Report/AiTDG-241205002W1-Test-Report-BLE-8045263.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045263>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045263.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPS3A>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/Test-Report/AiTDG-241205002W1-Test-Report-BLE-8045263.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf" \
-   "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPS3A/Test-Report/AiTDG-241205002W1-Test-Report-BLE-8045263.pdf" -o "2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf"
-echo "027dd133c4ac00b6223a7c52ef2bf5e7831e00cfcfb4188e5e0bd872263082f0  2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf.ARCHIVED.md b/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 1f4a3b8..0000000
--- a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPS3A-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 2,142,184 B (2.04 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,142,184 B (2.04 MiB) |
-| SHA-256 | `6910fdc8e5f4691389cb89c8f277a3ef50ebd4038089d632a0d0daef4456773a` |
-| FCC ID | **`2AN3WM5STAMPS3A`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 8045271 |
-| Upstream publication date | 2025-02-13 |
-| Grant date | 2025-02-13 |
-| Equipment class | M5StampS3A, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPS3A/External-Photos/External-Photos-8045271.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045271>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045271.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPS3A>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/External-Photos/External-Photos-8045271.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf" \
-   "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPS3A/External-Photos/External-Photos-8045271.pdf" -o "2AN3WM5STAMPS3A-external-photos.pdf"
-echo "6910fdc8e5f4691389cb89c8f277a3ef50ebd4038089d632a0d0daef4456773a  2AN3WM5STAMPS3A-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf.ARCHIVED.md b/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf.ARCHIVED.md
deleted file mode 100644
index 1c578ce..0000000
--- a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 176,710 B (0.17 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 176,710 B (0.17 MiB) |
-| SHA-256 | `db49d95ade5911cc7a0d60ebd93a084c7dd4ef2187ba2b48a33e3d5a1387833c` |
-| FCC ID | **`2AN3WM5STAMPS3A`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | FCC RF Exposure-MPE (20cm) |
-| FCC document id | 8045273 |
-| Upstream publication date | 2025-02-13 |
-| Grant date | 2025-02-13 |
-| Equipment class | M5StampS3A, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPS3A/RF-Exposure-Info/FCC-RF-Exposure-MPE-20cm-8045273.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045273>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045273.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPS3A>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/RF-Exposure-Info/FCC-RF-Exposure-MPE-20cm-8045273.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf" \
-   "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPS3A/RF-Exposure-Info/FCC-RF-Exposure-MPE-20cm-8045273.pdf" -o "2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf"
-echo "db49d95ade5911cc7a0d60ebd93a084c7dd4ef2187ba2b48a33e3d5a1387833c  2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-internal-photos.pdf b/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-internal-photos.pdf
deleted file mode 100644
index 54eca64..0000000
Binary files a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-internal-photos.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-label-and-location.pdf b/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-label-and-location.pdf
deleted file mode 100644
index 23eb513..0000000
Binary files a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-label-and-location.pdf and /dev/null differ
diff --git a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf.ARCHIVED.md b/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 2b45916..0000000
--- a/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPS3A-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 2,308,121 B (2.20 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,308,121 B (2.20 MiB) |
-| SHA-256 | `e9056d899bdd6cda96095105baae754c440e9a8cf32bd48499d027a58c5c9cd1` |
-| FCC ID | **`2AN3WM5STAMPS3A`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 8045295 |
-| Upstream publication date | 2025-02-13 |
-| Grant date | 2025-02-13 |
-| Equipment class | M5StampS3A, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPS3A/User-Manual/User-Manual-8045295.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8045295>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPS3A/8045295.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPS3A>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPS3A/User-Manual/User-Manual-8045295.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf" \
-   "components/m5stack/stamp-s3a/artifacts/certification/2AN3WM5STAMPS3A-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPS3A/User-Manual/User-Manual-8045295.pdf" -o "2AN3WM5STAMPS3A-user-manual.pdf"
-echo "e9056d899bdd6cda96095105baae754c440e9a8cf32bd48499d027a58c5c9cd1  2AN3WM5STAMPS3A-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/components/m5stack/stamp-s3a/artifacts/certification/README.md b/components/m5stack/stamp-s3a/artifacts/certification/README.md
deleted file mode 100644
index cb68766..0000000
--- a/components/m5stack/stamp-s3a/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5STAMPS3A`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5STAMPS3A`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2025-02-13** |
-| Equipment class | M5StampS3A, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Source page | <https://fccid.io/2AN3WM5STAMPS3A> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5STAMPS3A-internal-photos.pdf` | 2,778,287 | `e6512283b0e419c2b366b5d9dc3076ed3e6866f32e3baaaae6d7d731a68b8f13` | Internal Photos |
-| `2AN3WM5STAMPS3A-label-and-location.pdf` | 69,357 | `60d9ccb36cc10e2aeff65a90960e8861d36fa6a45fbdc5aaa782b5c3b067aa02` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf.ARCHIVED.md`](2AN3WM5STAMPS3A-aitdg-241205002w1-test-report-ble.pdf.ARCHIVED.md) | 959,274 | Test Report |
-| [`2AN3WM5STAMPS3A-external-photos.pdf.ARCHIVED.md`](2AN3WM5STAMPS3A-external-photos.pdf.ARCHIVED.md) | 2,142,184 | External Photos |
-| [`2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf.ARCHIVED.md`](2AN3WM5STAMPS3A-fcc-rf-exposure-mpe-20cm.pdf.ARCHIVED.md) | 176,710 | RF Exposure Info |
-| [`2AN3WM5STAMPS3A-user-manual.pdf.ARCHIVED.md`](2AN3WM5STAMPS3A-user-manual.pdf.ARCHIVED.md) | 2,308,121 | Users Manual |
-
-Archived total: **4 files, 5.33 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 2.72 MiB** |
-| Archived | **4 files, 5.33 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt b/components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt
deleted file mode 100644
index 7ffae63..0000000
--- a/components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-S3_v0.2: CO=54 textDesig=54 union=55
-  text-only (no CO marker recovered): ['C26']
-S3A_v0.3.3: CO=59 textDesig=59 union=59
-  text-only (no CO marker recovered): []
-
-== present on Stamp-S3 v0.2 only (REMOVED in v0.3.3) ==
-  ['D6', 'JP1', 'JP4', 'M2', 'R3', 'R6', 'R17']
-
-== present on Stamp-S3A v0.3.3 only (ADDED) ==
-  ['C15', 'C16', 'C18', 'C19', 'C20', 'C24', 'C25', 'L4', 'L6', 'L7', 'U4']
-
-== common ==
-  ['ANT1', 'C1', 'C2', 'C3', 'C4', 'C5', 'C6', 'C7', 'C8', 'C9', 'C10', 'C11', 'C12', 'C13', 'C14', 'C17', 'C21', 'C22', 'C23', 'C26', 'D1', 'D2', 'D3', 'D4', 'D14', 'F1', 'J1', 'J2', 'J3', 'JP2', 'JP3', 'L1', 'L2', 'L3', 'L5', 'M1', 'PHD1', 'R1', 'R2', 'R4', 'R5', 'R7', 'R16', 'S1', 'U1', 'U2', 'U3', 'X1']
diff --git a/components/memsensing/msm261s4030h0r/README.md b/components/memsensing/msm261s4030h0r/README.md
deleted file mode 100644
index d29d83d..0000000
--- a/components/memsensing/msm261s4030h0r/README.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# MEMSensing MSM261S4030H0R
-
-- **Category:** MEMS microphone. The `S` in this family designation denotes the **analogue**
-  output variant of the MSM261 family, as against the `D` (digital PDM/I²S) parts — **but that
-  reading is inferred from the family naming, not from the datasheet**, which was retained but
-  not read.
-- **Manufacturer:** MEMSensing Microsystems (Suzhou) Co., Ltd.
-- **Retrieved:** 2026-09-07
-- **Siblings already here:** [`msm261d3526h1cpm`](../msm261d3526h1cpm/README.md) ·
-  [`msm261d4030h1cpm`](../msm261d4030h1cpm/README.md) · [`msm381a3729h9bp`](../msm381a3729h9bp/README.md)
-
-The microphone of the **LilyGO T-Display-S3 Pro MVSRBoard** backplate — the **M** in *MVSR*
-(Microphone, Vibration, Speaker, RTC).
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **MSM261S4030H0R** |
-| Local artifact | [`artifacts/msm261s4030h0r-datasheet-lilygo-mirror.pdf`](artifacts/msm261s4030h0r-datasheet-lilygo-mirror.pdf) — 1 694 952 B, SHA-256 `bd2a5507eea390942ea60707b418bcfddb3ff41e561ed2e69c63a80ca2390cd5` |
-| Mirror source | `Xinyuan-LilyGO/T-Display-S3-Pro` → `datasheet/MEMSensing-MSM261S4030H0R.pdf` @ `08b8b2bbcb8b263131af119476403080cd30224f` |
-| Licence | MEMSensing copyright. **The `T-Display-S3-Pro` repository declares no licence**, so redistribution status is doubly unknown |
-
-## 2. Relationship to the parts already documented here
-
-This repository already holds two close relatives, both fitted to Waveshare boards:
-
-| Part | Output | Documented for |
-|---|---|---|
-| `MSM261D3526H1CPM` | digital (PDM) | Waveshare |
-| `MSM261D4030H1CPM` | digital (PDM) | [Waveshare ESP32-S3-Knob-Touch-LCD-1.8](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) |
-| **`MSM261S4030H0R`** | **`S`** — see the caveat above | LilyGO T-Display-S3 Pro MVSRBoard |
-
-`MSM261D**4030**H1CPM` and `MSM261S**4030**H0R` share the `4030` size/sensitivity field, which
-suggests the same acoustic element in different output configurations. **That is a reading of
-the part-number structure, not a documented fact**, and the `D`/`S` and `H1CPM`/`H0R` suffixes
-were not decoded from any datasheet. If you need to know whether this part outputs PDM or an
-analogue signal — and you do, because it determines whether it can connect to the ESP32-S3's
-I²S peripheral directly — **read the retained datasheet.**
-
-## 3. Board integration
-
-Fitted to the **MVSRBoard** backplate, not to the T-Display-S3 Pro mainboard. Pin assignment,
-clock and data routing were **not established** — no MVSRBoard pin header was located, and the
-board's own schematic was retrieved but not traced.
-
-Alongside it on the same backplate: a
-[MAX98357A](../../analog-devices/max98357a/README.md) I²S class-D speaker amplifier, a
-[PCF85063ATL](../../nxp/pcf85063a/README.md) RTC, and a vibration motor.
-
-## 4. Gaps
-
-- **Datasheet retained but not read.** Output type, sensitivity, SNR, supply and clock
-  requirements are all unrecorded.
-- Pin assignment on the MVSRBoard unknown.
-- Not verified on hardware.
-
-## 5. Used by
-
-### LilyGO T-Display-S3 Pro MVSRBoard
-→ [`devices/lilygo/t-display-s3-pro-mvsrboard`](../../../devices/lilygo/t-display-s3-pro-mvsrboard/README.md)
-(a stub record) · mainboard: [`devices/lilygo/t-display-s3-pro`](../../../devices/lilygo/t-display-s3-pro/README.md)
diff --git a/components/memsensing/msm261s4030h0r/artifacts/msm261s4030h0r-datasheet-lilygo-mirror.pdf b/components/memsensing/msm261s4030h0r/artifacts/msm261s4030h0r-datasheet-lilygo-mirror.pdf
deleted file mode 100644
index 2484d71..0000000
Binary files a/components/memsensing/msm261s4030h0r/artifacts/msm261s4030h0r-datasheet-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/memsensing/msm381a3729h9bp/README.md b/components/memsensing/msm381a3729h9bp/README.md
deleted file mode 100644
index ef03864..0000000
--- a/components/memsensing/msm381a3729h9bp/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# MEMSensing MSM381A3729H9BP — analog MEMS microphone
-
-> Marking read from the M5Stack Cardputer ADV schematic (sheet 3, designator **U8**):
-> `MSM381A3729H9BPC` in the value field. Recorded here as **`MSM381A3729H9BP`**, the part
-> family, with the trailing character treated as a packaging/grade suffix — see *Gaps*.
-> Record created **2026-09-04**. Sibling records already in this repository:
-> [`msm261d3526h1cpm`](../msm261d3526h1cpm/README.md), [`msm261d4030h1cpm`](../msm261d4030h1cpm/README.md).
-
-## Function
-
-A bottom- or top-port **analog output** MEMS microphone: a differential (or single-ended) analog
-audio signal, to be amplified and digitised by an external codec ADC. Unlike the MSM261 series
-already documented here, and unlike the **SPM1423** used on the earlier Cardputers, this part is
-**not PDM** — it produces analog audio and therefore requires a codec with an analog microphone
-input.
-
-That distinction is the whole reason the Cardputer ADV changed both the microphone *and* the
-audio chain at the same time.
-
-## Key capabilities
-
-| Property | Value | Evidence |
-|---|---|---|
-| Output | **analog** | schematic: `OUT` (pin 4) → `MIC_P` / `MIC_N` into the ES8311's `MIC1P`/`MIC1N` |
-| SNR | **65 dB** | M5Stack Cardputer ADV specification table |
-| Supply | analog `AVDD` domain, decoupled by C32 1 µF and C33 10 µF | schematic |
-| Package | 4-pad MEMS package | schematic symbol: `VDD` (1), `GND` (2), `GND` (3), `OUT` (4) |
-| Sensitivity, frequency response, AOP | **not established** | no datasheet retrieved |
-
-## Pinout as drawn
-
-| Pin | Name | Net on the Cardputer ADV |
-|---|---|---|
-| 1 | `VDD` | `AVDD` (analog 3.3 V, via R24 33 Ω 1 %) |
-| 2 | `GND` | `AGND` |
-| 3 | `GND` | `AGND` |
-| 4 | `OUT` | `MIC_P` → ES8311 pin 18 `MIC1P/DMIC_SDA` |
-
-`MIC_N` returns to the ES8311's pin 17 `MIC1N`, with R41 100 Ω 1 % and C31 1 µF in the network —
-so the codec sees a pseudo-differential input.
-
-## Used By
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-Designator **U8**, on schematic sheet 3, in the analog audio block beside the ES8311.
-
-The microphone has **no direct connection to the SoC**. Its output goes into the
-[ES8311](../../everest-semiconductor/es8311/README.md) codec's `MIC1P`/`MIC1N` inputs; the codec
-digitises it and returns I²S on `ASDOUT` → **G46**. So from firmware's point of view there is no
-"microphone" — there is a codec ADC, configured by
-[`M5Unified`'s `_microphone_enabled_cb_cardputer_adv`](../../../devices/m5stack/cardputer-adv/features/audio.md):
-
-```c
-2, 0x0E, 0x02,  // SYSTEM: enable analog PGA, enable ADC modulator
-2, 0x14, 0x10,  // ADC_REG14: select Mic1p-Mic1n, PGA gain MINIMUM
-2, 0x17, 0xBF,  // ADC_REG17: ADC volume 0 dB
-2, 0x1C, 0x6A,  // ADC_REG1C: EQ bypass, DC-offset cancellation
-```
-
-Note `0x14 = 0x10` selects the **differential Mic1p–Mic1n** path at **minimum PGA gain**. If the
-recorded level is too low on this board, that constant is where to look first — and the vendor
-never exposes it.
-
-⚠ **Cross-subsystem hazard.** The microphone's *disable* sequence in M5Unified writes
-`0x00 = 0x00` (**CSM power down**) to the shared codec, which also silences the speaker. Full
-analysis: [`cardputer-adv/features/audio.md` §6.2](../../../devices/m5stack/cardputer-adv/features/audio.md).
-
-**Predecessor on the same product line:** Cardputer v1.0 and v1.1 use a **Knowles SPM1423**
-PDM microphone wired straight to the SoC (`DAT` → G46, `CLK` → G43) with no codec.
-See [`knowles/spm1423hm4h-b`](../../knowles/spm1423hm4h-b/README.md).
-
-## Substitutes
-
-| Part | Note |
-|---|---|
-| Any analog MEMS mic with the same 4-pad footprint | the surrounding network (R39, R41, C31, C32) sets the bias and filtering; check sensitivity before swapping |
-| **PDM** MEMS mic (SPM1423, MSM261D…) | **not a drop-in** — a PDM part needs a clock and a digital receiver, not an analog codec input |
-| MSM261D3526H1CPM / MSM261D4030H1CPM | the PDM siblings already documented in this repository; different interface entirely |
-
-## Gaps
-
-* **No datasheet.** MEMSensing (深圳市敏芯微电子 / MEMSensing Microsystems, Suzhou) does not
-  publish this part number through a search-indexable route that this pass located, and M5Stack
-  does **not** link a datasheet for it on the Cardputer ADV page — the page links ES8311,
-  NS4150B, BMI270, ST7789V2 and ESP32-S3, but not the microphone.
-* Sensitivity (dBV/Pa), frequency response, acoustic overload point, directionality and port
-  orientation are all **unknown**.
-* The trailing `C` in the schematic string `MSM381A3729H9BPC` is **unexplained**. It could be a
-  package/grade suffix or an artefact of the schematic's value field. Recorded as read; the
-  directory is named for the unambiguous part of the string.
-* No board photograph was obtained, so the **top marking has not been checked** against the
-  schematic value.
diff --git a/components/microne/me3116am6g/README.md b/components/microne/me3116am6g/README.md
deleted file mode 100644
index a5f7d5b..0000000
--- a/components/microne/me3116am6g/README.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# Microne ME3116AM6G — wide-input step-down converter
-
-- **Category:** asynchronous buck (step-down) DC-DC converter IC with integrated high-side
-  switch and bootstrap, SOT23-6.
-- **Manufacturer:** **Nanjing Micro One Electronics** (南京微盟, "Microne") — inferred from the
-  `ME3xxx` part-number family, which is Micro One's buck/boost series. **No datasheet was
-  located** and no vendor page was retrieved in this pass, so the manufacturer attribution is
-  `inferred`, not read.
-- **Research status:** ⚠ **Schematic-only.** Every fact below comes from the M5Stack DinMeter
-  schematic. No component document was obtained.
-- **Retrieved:** 2026-09-04
-
-The **6–36 V wide-range input converter** of the M5Stack DinMeter — the part that makes the
-board a panel instrument rather than a 5 V dev board.
-
----
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part string | **`ME3116AM6G`** | DinMeter schematic, visible value text at (387, 99.8), associated with `U1` |
-| Pin count / names | **6**: `VIN`, `BST`, `EN`, `LX`, `GND`, `FB` | DinMeter schematic `U1` symbol, `PIU101`–`PIU106` |
-| Topology | asynchronous buck — external Schottky and external inductor, bootstrap capacitor on `BST` | implied by the pin set + the fitted `L1` and Schottky diodes |
-| Input on this board | **6 – 36 V** | M5Stack specification row |
-| Output on this board | `+5VIN` rail | schematic net |
-| Feedback divider | `R5` 56 kΩ (upper) / `R6` 10 kΩ (lower) | schematic |
-| Inductor | `L1` **10 µH**, 3015 package | schematic |
-| Input bulk | `C24` **10 µF / 35 V** | schematic |
-| Decoupling | `C7`, `C8` 100 nF; `C6` (near `D9`) | schematic |
-| Freewheel / clamp | `D9`, `D11`, `D12` (`SD36`), `D13` — B5819W / SD36 Schottky | schematic |
-
-Feedback arithmetic: 5 V out through a 56 k / 10 k divider implies a reference near
-5 × 10/(56+10) ≈ **0.758 V**, which is a common buck reference value. This is arithmetic on
-read values, **not** a datasheet figure — it is offered as a consistency check, not a
-specification.
-
-## 2. What is not established
-
-- **No datasheet.** Not from Micro One, not from a distributor, not from an aggregator, in this
-  pass. Searches logged in
-  [`devices/m5stack/dinmeter/research-log.md`](../../../devices/m5stack/dinmeter/research-log.md).
-- Absolute-maximum input, switching frequency, current limit, efficiency, thermal behaviour,
-  `EN` threshold, soft-start, protection behaviour — all **unknown**.
-- **The `AM6G` suffix is unparsed.** Whether it encodes package, grade, or a voltage option is
-  unknown.
-- **No chip-marking confirmation.** No teardown photograph of the DinMeter was inspected. The
-  part number rests on the schematic value text alone.
-
-**What would resolve it:** a Micro One datasheet, or a photograph of `U1`'s top marking on a
-real board.
-
-## 3. Practical consequences for firmware and integration
-
-- The **36 V ceiling is the board's DC-input rating**, and it is set by this part plus its
-  input capacitor (`C24` is rated 35 V — *below* the 36 V spec). Running sustained at 36 V puts
-  `C24` at 103 % of its rating. That is a design observation from read values, not a fault
-  report; derating a 35 V X7R at 36 V is common but not free.
-- `EN` is available; whether M5Stack ties it to anything switchable was not traced.
-- Nothing about this part is firmware-visible. There is no register interface.
-
-## 4. Artifacts
-
-**None.** No document was obtained. The schematic that establishes the part is a *device*
-artifact and lives at
-[`devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf`](../../../devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf).
-
----
-
-## Used By
-
-### M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-`U1`. Takes 6–36 V from the 2-pin screw terminal `J1` (via reverse/clamp Schottkys) and produces
-the `+5VIN` rail that feeds the Stamp module's pad 13, the [TP4057](../../generic/tp4057/README.md)
-charger and the `U7` CN809J supervisor. It is the *only* path from the DC terminal into the
-board.
-
-→ [`devices/m5stack/dinmeter/features/power-and-battery.md`](../../../devices/m5stack/dinmeter/features/power-and-battery.md)
diff --git a/components/murata/mun3cad01-sc/README.md b/components/murata/mun3cad01-sc/README.md
deleted file mode 100644
index 250caba..0000000
--- a/components/murata/mun3cad01-sc/README.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# MUN3CAD01-SC — 1 A µPOL step-down power module
-
-- **Category:** fully-integrated point-of-load DC-DC **module** (converter + inductor + input/
-  output capacitance in one package).
-- **Manufacturer:** **Murata** — `µPOL` is Murata's trademark for this monolithic power-module
-  family, and the part-number grammar matches. **The mirrored datasheet's first page carries no
-  vendor name or logo**, so the attribution is `inferred` from the trademark, not read. Filed
-  under `murata/` on that basis; if a contrary source appears, this record should move.
-- **Retrieved:** 2026-09-04
-
-The 5 V → 3.3 V converter inside the **M5Stack Stamp-S3** module (`M2`). **Not fitted on the
-Stamp-S3A** despite what M5Stack's Stamp-S3A page says — see §3.
-
----
-
-## 1. Specification (from the datasheet)
-
-| Property | Value |
-|---|---|
-| Output current | **1 A** |
-| Peak efficiency | 93 % at 3.3 V<sub>IN</sub> |
-| Input range | **2.7 – 5.5 V** |
-| Output range | **0.8 – 4.0 V** (set by external feedback divider) |
-| Modes | automatic power-saving / PWM |
-| Protection | UVLO, OCP (non-latching) |
-| Soft start | internal |
-| Package | **2.9 × 2.3 × 1.05 mm** |
-| Compliance | Pb-free / RoHS, MSL 2, 260 °C reflow |
-| Stated applications | single Li-ion powered equipment, LDO replacement, phones/PDAs/palmtops |
-
-All from page 1 of the retained datasheet; the text layer was validated against the visible
-title block before transcription.
-
-## 2. As fitted on the Stamp-S3 (board rev v0.2)
-
-| Property | Value | Evidence |
-|---|---|---|
-| Designator | `M2`, 6 pins: `EN`, `GND`, `VIN`, `GND`, `FB`, `VOUT` | `Sch_M5StampS3_v0.2.pdf` |
-| Input | `VIN_5V` | schematic |
-| Output | `VDD_3V3` | schematic |
-| Feedback divider | `R6` **100 kΩ** / `R17` **22.1 kΩ** | schematic |
-| Bulk capacitance | `C21`, `C22` 10 µF/10 V | schematic |
-
-Divider check: with a 0.6 V reference, 0.6 × (100/22.1 + 1) ≈ 3.32 V. Consistent with a 3.3 V
-rail. Arithmetic on read values; the reference voltage was **not** read from the datasheet page
-retained here.
-
-## 3. ⚠ It is *not* on the Stamp-S3A
-
-The [Stamp-S3A](../../m5stack/stamp-s3a/README.md) product page lists `DC-DC: MUN3CAD01-SC` and
-links this very datasheet — from the **`S007 StampS3`** directory, i.e. the Stamp-S3's own path.
-
-But the string `MUN3CAD01` **does not appear anywhere in `Sch_StampS3_v0.3.3.pdf`**, the
-designator `M2` is absent from that sheet, and the regulator there is `U4`: an 8-ball part with
-`VIN`/`EN`/`SW`/`VOS`/`VSEL1`/`VSEL2`/`VSEL3`/`GND`, annotated `IOUT: 0~0.6A`, driving an
-**external** 2.2 µH inductor (`L4`, `MWTC201608S2R2`). A µPOL module has an *integrated*
-inductor and an `FB` pin, not `SW` and `VSEL` straps.
-
-The specification row appears to have been carried over unedited when the Stamp-S3A page was
-created. The schematic is the stronger evidence.
-→ [`components/unidentified/m5stack-stamp-s3a/dcdc-u4/`](../../unidentified/m5stack-stamp-s3a/dcdc-u4/README.md)
-
-## 4. Artifacts
-
-| File | Size | SHA-256 | Licence | Redistribution | Disposition |
-|---|---:|---|---|---|---|
-| [`artifacts/mun3cad01-sc-datasheet-m5stack-mirror.pdf`](artifacts/mun3cad01-sc-datasheet-m5stack-mirror.pdf) | 2 045 960 | `90e2ecbd8cf35af2102ded0216a5f94d58d94a31adf0436308356376633433cb` | unknown | `unknown` | `repository` |
-
-Retrieved 2026-09-04 from
-`https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/Stamp/S007%20StampS3/MUN3CAD01-SC.pdf`
-(HTTP 200, `%PDF` validated, text extracted and cross-checked against the visible title).
-Renamed to record that this is an **M5Stack mirror**; no manufacturer-hosted copy was located.
-No document version or revision date is printed on page 1 — recorded as unknown rather than
-omitted.
-
----
-
-## Used By
-
-### M5Stack Stamp-S3 (SKU S007), board rev v0.2
-
-`M2` — the module's only 5 V → 3.3 V converter, feeding `VDD_3V3` which supplies the
-ESP32-S3FN8, the WS2812B-2020 RGB LED (always-on on this revision) and the
-[SGM2578](../../sgmicro/sgm2578/README.md) backlight load switch.
-→ [`components/m5stack/stamp-s3/README.md`](../../m5stack/stamp-s3/README.md)
-
-### Reached from these devices
-
-- [M5Stack DinMeter (K134)](../../../devices/m5stack/dinmeter/README.md) — fits a Stamp-S3, so
-  this part is inside it
-- [M5Stack DinMeter v1.1 (K134-V11)](../../../devices/m5stack/dinmeter-v1.1/README.md) —
-  **does not** contain this part; it fits a Stamp-S3A
diff --git a/components/murata/mun3cad01-sc/artifacts/mun3cad01-sc-datasheet-m5stack-mirror.pdf b/components/murata/mun3cad01-sc/artifacts/mun3cad01-sc-datasheet-m5stack-mirror.pdf
deleted file mode 100644
index eb47fa2..0000000
Binary files a/components/murata/mun3cad01-sc/artifacts/mun3cad01-sc-datasheet-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/nanjing-top-power/tp4065/README.md b/components/nanjing-top-power/tp4065/README.md
deleted file mode 100644
index 8e66e2d..0000000
--- a/components/nanjing-top-power/tp4065/README.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# TP4065 — linear Li-ion charger (as documented; **not** as fitted)
-
-- **Category:** single-cell Li-ion constant-current / constant-voltage linear charger with a
-  resistor-programmed charge current.
-- **Manufacturer:** **unresolved.** TP40xx parts are widely attributed to Nanjing Top Power ASIC
-  Corp; **no primary document was obtained** during this pass and the filing directory reflects
-  the common attribution, not established evidence. Compare the sibling
-  [`generic/tp4057`](../../generic/tp4057/README.md) record, which reached the same wall and
-  filed under `generic/` instead.
-- **Retrieved:** 2026-09-07
-
-## ⚠ Read this first: the part in the schematic is not the part on the board
-
-`U6` on the **LilyGO T-Display-S3** schematic (`T_Display_S3.pdf`, title block 2024-04-29) is
-labelled **`TP4065`**. An owner who traced a physical board reported something else entirely:
-
-> "when I try to find the TP4056 on the PCB it cannot be found? The datasheet shows that the IC
-> should be an 8 pin SOP-8 package which cannot be located. Tracing out the PCB I find that the
-> charging IC appears to be a device that is a **5-Lead TSOT-23 package with the marking of
-> `65b311`** printed on top. This does not agree with the posted schematic."
-> — [LilyGO issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230), 2024-03-02.
-> Evidence class: **firsthand physical inspection.** (Note the reporter writes "TP4056" in
-> prose while the schematic reads TP4065 — two different parts with similar programming
-> equations.)
-
-LilyGO never published a corrected sheet. **This record therefore documents a designator, not a
-confirmed fitted part.** The unidentified `65b311`/`AXPM65611` string has its own record:
-[`components/unidentified/lilygo-t-display-s3-family/axpm65611/`](../../unidentified/lilygo-t-display-s3-family/axpm65611/README.md).
-
-## 1. What the schematic says
-
-| Property | Value | Evidence |
-|---|---|---|
-| Designator | `U6` | `T_Display_S3.pdf` designator census |
-| Pins shown | `CHRG 1`, `GND 2`, `BAT 3`, `VCC 4`, `PROG 5` | same |
-| Programming resistor | `R9 = 2K` | same |
-| Sheet note | **`R13  IBAT (mA) = 580`** | same |
-| Vendor README | *"The default charging current is **500mA**"* | `README.md` @ `ec889e7` |
-
-**500 mA and 580 mA are both stated by LilyGO, in two documents, for the same board.** A 2 kΩ
-`PROG` resistor gives ≈580 mA under the TP4056/TP4065 equation *I = 1200 V / R<sub>PROG</sub>*,
-which matches the schematic note and not the README.
-
-## 2. Where it also appears
-
-The same `TP4065` designator string appears on **three** LilyGO schematics:
-
-| Board | Designator |
-|---|---|
-| T-Display-S3 | `U6` |
-| T-Display-S3 AMOLED (V1.0 sheet) | `U5` |
-| T-Display-S3 AMOLED Touch (V2.0 sheet) | `U6` |
-
-So whatever it is, it is LilyGO's standard cheap charger for the non-PMIC boards. The boards
-that moved upmarket use a real I²C PMIC instead — [SY6970](../../silergy/sy6970/README.md)
-on Long/Pro/T4-S3/1.64/1.43-1.75, [BQ25896](../../texas-instruments/bq25896/README.md) on
-AMOLED Plus, [AXP2101](../../x-powers/axp2101/README.md) on AMOLED Lite.
-
-## 3. Safety consequences on these boards
-
-- **No battery protection is fitted anywhere on the T-Display-S3.** LilyGO's maintainer,
-  2025-02-06: *"No built-in battery protection, needs to be used with a lithium-ion battery
-  with battery protection."* Use a protected cell.
-- **500–580 mA is above 1 C for a 350–400 mAh cell**, which is the size that fits third-party
-  shells. That is what prompted issue #230.
-- **Do not swap the programming resistor on the strength of the schematic.** The equation you
-  would use comes from a datasheet for a part that a careful owner has already shown may not be
-  fitted.
-
-## 4. Gaps
-
-- **No datasheet obtained**, for TP4065 or for the `65b311` part.
-- Manufacturer unconfirmed.
-- The actual charge current has never been measured by anyone in the searched set. A series
-  ammeter into a discharged cell would settle the 500-vs-580 question **and** narrow the part
-  identity by behaviour.
-
-## 5. Used by
-
-### LilyGO T-Display-S3 / Touch — designator `U6`
-→ [`devices/lilygo/t-display-s3`](../../../devices/lilygo/t-display-s3/README.md).
-Charges the JST 1.25 mm cell from USB-C 5 V only (`VBUS` is not brought out to the header).
-Charge status drives the red LED. **Identity disputed — see the warning above.**
-
-### LilyGO T-Display-S3 AMOLED — designator `U5` (V1.0 sheet) / `U6` (Touch sheet)
-→ [`devices/lilygo/t-display-s3-amoled`](../../../devices/lilygo/t-display-s3-amoled/README.md).
-Same role. Not independently verified against hardware.
diff --git a/components/nordic-semiconductor/nrf52840/README.md b/components/nordic-semiconductor/nrf52840/README.md
deleted file mode 100644
index c7d3914..0000000
--- a/components/nordic-semiconductor/nrf52840/README.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# Nordic Semiconductor nRF52840
-
-- **Category:** Arm Cortex-M4F multiprotocol SoC — Bluetooth 5.4 LE, Bluetooth mesh, 802.15.4/Thread/Zigbee, ANT, 2.4 GHz proprietary, **USB 2.0 full-speed device**
-- **Manufacturer:** Nordic Semiconductor ASA
-- **Research status:** widely documented part; this record covers what is needed to work with it **as fitted on the LilyGO T-Display K230 expansion base**, and points at Nordic's own documentation for the rest.
-- **Retrieved:** 2026-09-04
-
-## 1. Core facts
-
-| Property | Value |
-|---|---|
-| CPU | Arm **Cortex-M4** with FPU, 64 MHz |
-| Flash / RAM | 1 MB / 256 KB |
-| Radio | 2.4 GHz multiprotocol: Bluetooth LE (LE Coded PHY, LE 2M), Bluetooth mesh, IEEE 802.15.4, ANT, proprietary |
-| USB | **USB 2.0 full-speed device** — this is what makes UF2 drag-and-drop bootloaders possible |
-| Crypto | Arm CryptoCell-310 |
-| Typical package | aQFN73 / QFN48 |
-| Nordic documentation | `https://docs.nordicsemi.com/` (nRF52840 Product Specification) |
-
-The part is thoroughly documented by Nordic; this record deliberately does not restate the
-product specification. What is *not* documented anywhere else is how LilyGO uses it, below.
-
-## 2. Firmware ecosystem relevant to this repository
-
-| Route | Notes |
-|---|---|
-| **Adafruit nRF52 bootloader + UF2** | Double-tap reset enumerates a mass-storage device; drop a `.uf2` on it. Family ID **`0xADA52840`**. |
-| PlatformIO `platform = nordicnrf52` | Board id used by LilyGO: **`nrf52840_dk_adafruit`**, framework `arduino` |
-| nRF Connect SDK (Zephyr) | Nordic's own route; heavier |
-| Serial DFU | Nordic's `nrfutil` / Adafruit `adafruit-nrfutil` |
-
-## 3. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-Fitted on the **nRF52840 BLE / audio / sensor base board**, an optional expansion base for the
-K230 main board. It exists because **the K230 has no Bluetooth radio of any kind**; the
-nRF52840 is the board's BLE Central.
-
-**Wiring (from LilyGO's own pin map, S1):**
-
-| nRF52840 pin | Arduino pin | Goes to | Notes |
-|---|---|---|---|
-| `P0.11` | 11 | K230 **`GPIO3`** / UART1 **TX** | nRF52840 RX; K230 sends AT commands |
-| `P0.12` | 12 | K230 **`GPIO4`** / UART1 **RX** | nRF52840 TX; AT responses and BLE events |
-| `P1.00` | 32 | blue activity LED on the nRF52840 board | driven by firmware |
-| `P0.04` | 4 | **external 5 V boost enable** | boosts the **21700** battery compartment to a stable 5 V for the host unit |
-| USB CDC | — | host PC | 115 200 baud debug log |
-
-Link parameters: **115 200 8N1, no flow control**, `/dev/ttyS1` on the K230 side, enabled by
-`0060-riscv-dts-rm69a10-enable-uart1-nrf52840.patch`.
-
-`P0.04` is the one to notice: it is not a peripheral pin, it is a **power** control. The
-nRF52840 base owns the 5 V boost that powers the main unit from the 21700 cell.
-
-**Firmware.** LilyGO ships a custom **AT-command BLE Central** firmware
-(`Xinyuan-LilyGO/T-Display-K230-nRF52840`, commit `4646a728580739d487126f47a521e9b8032b3c2c`,
-2026-08-23). Prebuilt artifacts are in the repository:
-
-| File | Bytes | Role |
-|---|---|---|
-| `bootloader/k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex` | 525 680 | Bootloader with **UART DFU** at 115 200 and **SoftDevice S140 6.1.1** |
-| `firmware/k230_nrf52840_at_20260816_r4_k230_uart_dfu.uf2` | 296 960 | Application, build date **2026-08-16**, revision **r4** |
-
-**Two DFU paths exist and they are different.** The USB/UF2 path (double-tap reset, drag UF2 to
-the enumerated drive) is the normal developer route. The **UART DFU** path is what lets the
-*K230* reflash the nRF52840 in the field with no USB cable, and it is the reason for the custom
-bootloader hex above and for `tools/k230_nrf52840_dfu.cpp` (33 370 bytes) and the launcher's
-`ui_nrf52840_dfu.c`. The launcher explicitly arbitrates ownership of the nRF52840 between
-Meshtastic BLE and UART DFU (changelog v0.2.2).
-
-**AT surface:** `AT`, `AT+VER?`, `AT+MESHSTATUS?`, `AT+SCAN=<s>`, `AT+LIST?`, `AT+CONN=<i>`,
-`AT+GATTS?`, `AT+DISC`, plus read/write/subscribe on characteristics; async URCs
-`+SCAN:`, `+CONNECTED:`, `+DISCONNECTED:`, `+BOOT:K230_NRF52840_AT`, `+MESH:ADV,1`.
-Full guide: `docs/AT_COMMANDS.md` in that repository.
-
-⚠ **Serial-monitor gotcha, stated by LilyGO:** "for some serial monitors, you need to select
-**DTR** to see the serial port output messages."
-
-## 4. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | UART1 mapping, LED, AHT20 and MAX98357A on the same base |
-| S2 | `T-Display-K230-nRF52840` README, firmware and bootloader | LILYGO | primary | repository | `https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/tree/4646a728580739d487126f47a521e9b8032b3c2c` | 2026-09-04 | Pin map incl. `P0.04` boost enable, PlatformIO board, UF2 family ID, DFU procedure, AT set |
-| S3 | nRF52840 Product Specification | Nordic Semiconductor | primary | datasheet | `https://docs.nordicsemi.com/` | 2026-09-04 (not downloaded) | Core specification |
diff --git a/components/nordic-semiconductor/nrf9151/README.md b/components/nordic-semiconductor/nrf9151/README.md
deleted file mode 100644
index adf244f..0000000
--- a/components/nordic-semiconductor/nrf9151/README.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Nordic Semiconductor nRF9151 — LTE-M / NB-IoT / DECT NR+ SiP with GNSS
-
-- **Category:** cellular IoT System-in-Package — Arm Cortex-M33 application core + LTE-M/NB-IoT modem + **GNSS** + RF front end + PA in one 10 × 16 mm package
-- **Manufacturer:** Nordic Semiconductor ASA
-- **Research status:** part identified and integration fully documented from LilyGO's firmware repository; Nordic's own documentation referenced rather than restated.
-- **Retrieved:** 2026-09-04
-
-## 1. Core facts
-
-| Property | Value |
-|---|---|
-| Application core | Arm **Cortex-M33** with **TrustZone**; secure/non-secure split enforced by **TF-M** |
-| Cellular | **LTE-M (Cat-M1)** and **NB-IoT (Cat-NB1/NB2)**, 3GPP Rel-14 |
-| Other radio | **DECT NR+** (non-cellular standalone) |
-| Positioning | **GNSS** receiver in-package |
-| Package | 10 × 16 mm SiP; successor/smaller sibling to nRF9160 |
-| SDK | **nRF Connect SDK (NCS)** — Zephyr-based |
-| Modem firmware | separate signed package `mfw_nrf91x1_*.zip`, **not** updated by an application build |
-
-## 2. The TF-M split, and why it matters at build time
-
-Every nRF91-series application is really two images: TF-M (secure) plus the non-secure
-application. LilyGO's build produces **`tfm_merged.hex`**, and their README states the
-consequence explicitly:
-
-> "`tfm_merged.hex` contains TF-M plus the non-secure application. **It does not update the
-> cellular modem firmware package `mfw_nrf91x1_*.zip`.**" — S2
-
-That is the single most common nRF91 support question and LilyGO answered it in their own
-README, which is worth noting because most vendors do not.
-
-## 3. Used By
-
-### [LilyGO T-Display K230 Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-Fitted on the **nRF9151 cellular / GNSS / keyboard base board** — the keyboard half of the
-T-Display K230 Kit. It is a **priced option**: SKU `K256-04` is "Keyboard Only / **With
-nRF9151**" at $113.25, `K256-04-A` is "Keyboard Only / **Without nRF9151**" at $70.94
-(2026-09-04, S3). The nRF9151 therefore accounts for roughly **$42** of the keyboard's price,
-which is the cleanest available measure of what the cellular option costs.
-
-**Wiring (S1, S2):**
-
-| nRF9151 pin | Goes to | Direction | Notes |
-|---|---|---|---|
-| power enable | K230 **`GPIO2`** | K230 output | **high enables** the module, low disables it |
-| `P0.26` (UART1 RX1) | K230 **`GPIO28`** / UART3 TX | K230 → nRF9151 | AT command link, `/dev/ttyS3` |
-| `P0.27` (UART1 TX1) | K230 **`GPIO29`** / UART3 RX | nRF9151 → K230 | AT responses and URCs |
-| `P0.29` (UART2 TX2) | external USB-UART RX | out | optional debug console |
-| `P0.28` (UART2 RX2) | external USB-UART TX | in | optional |
-| `P0.23` | blue LED **inside the PCB** | out | run/GNSS status; on by default, AT-controllable |
-
-**115 200 8N1, no RTS/CTS.** Enabled by `0061-riscv-dts-rm69a10-enable-uart3-nrf9151.patch`,
-which also configures `GPIO2` as the userspace modem-enable pin.
-
-**Two firmware profiles** are published (`Xinyuan-LilyGO/T-Display-K230-nRF9151`, commit
-`ed4ecbe34162dec9b81213a400198125bbd6e36f`, 2026-08-14):
-
-| Profile | Use |
-|---|---|
-| `serial_modem_k230/` | **Recommended.** Nordic **Serial LTE Modem** adapted for the K230; provides the LTE/SIM/GNSS/NMEA/LED behaviour the launcher's Cellular app expects. |
-| `at_client_k230/` | Minimal AT passthrough for bring-up only. |
-
-The Serial LTE Modem profile is built from a **pinned submodule** —
-`third_party/ncs-serial-modem` at commit `13c80da97fe4d55ecb5a9745834d97be22821307` — with five
-LilyGO patches applied in order: GNSS NMEA URC + LED, optional XDFU, UART diagnostics, a GNSS
-NMEA URC worker, and AT LED control. **The upstream pin and the patch set are both retained
-upstream**, which makes this one of the better-documented vendor forks encountered in this
-repository.
-
-**Toolchain:** `nrfutil sdk-manager install --install-dir "$PWD/ncs" v3.4.0` — **NCS v3.4.0**,
-installed repository-relative at `./ncs/v3.4.0` or overridden with `NCS_ROOT`.
-Build target overlay: `boards/nrf9151dk_nrf9151_ns.overlay` (the `_ns` suffix is the
-non-secure target, consistent with the TF-M split above).
-
-**Runtime behaviour LilyGO documents (S2):** `AT+CFUN=1` is required *before* SIM commands like
-`AT+CPIN?`; `AT#XNMEA=0|1` toggles NMEA URCs on the AT UART; a GNSS fix changes the LED to a
-1 s cadence with ~300 ms on-time.
-
-## 4. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | GPIO2 enable, UART3 mapping |
-| S2 | `T-Display-K230-nRF9151` README and patch set | LILYGO | primary | repository | `https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151/tree/ed4ecbe34162dec9b81213a400198125bbd6e36f` | 2026-09-04 | Pin map, NCS version, submodule pin, patch list, AT behaviour, TF-M caveat |
-| S3 | T-Display K230 Kit `/products/t-display-k230-kit.js` | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230-kit.js` | 2026-09-04 | `K256-04` $113.25 with nRF9151, `K256-04-A` $70.94 without |
-| S4 | nRF91 AT Commands Reference Guide v0.7.1 | Nordic Semiconductor | primary | manual | `https://www.nordicsemi.com/-/media/Restricted/ProductKeys/L984675KPNS/nrf91atcommandsv071.pdf` | not retrieved (restricted path) | AT command reference, as cited by LilyGO |
diff --git a/components/normand/sk6805-ec20/README.md b/components/normand/sk6805-ec20/README.md
index 612de2c..c7a6a38 100644
--- a/components/normand/sk6805-ec20/README.md
+++ b/components/normand/sk6805-ec20/README.md
@@ -256,7 +256,7 @@ Three attempts failed before one succeeded. All are recorded in `component-downl
 |---|---|
 | `https://cdn-shop.adafruit.com/product-files/4960/4960_SK6805-EC20_REV02_EN.pdf` | HTTP 404 (9-byte `Not found`) |
 | `https://cdn-shop.adafruit.com/product-files/4960/4960_SK6805-EC20_REV01_EN.pdf` | HTTP 404 |
-| `https://cdn-shop.adafruit.com/product-files/4492/Datasheet.pdf` | ⚠ **HTTP 200, valid `%PDF`, 3 094 006 B — but the WRONG PART.** A 17-page image-only **iPixel LED** (Shenzhen) catalogue with no extractable text and no occurrence of "SK6805". Archived to `archive/components/normand/sk6805-ec20/artifacts/WRONG-PART-ipixel-catalog-adafruit-4492.pdf` rather than deleted |
+| `https://cdn-shop.adafruit.com/product-files/4492/Datasheet.pdf` | ⚠ **HTTP 200, valid `%PDF`, 3 094 006 B — but the WRONG PART.** A 17-page image-only **iPixel LED** (Shenzhen) catalogue with no extractable text and no occurrence of "SK6805". Archived to `../hardware-doc-archive/doc/hardware/components/normand/sk6805-ec20/artifacts/WRONG-PART-ipixel-catalog-adafruit-4492.pdf` rather than deleted |
 | `https://datasheet.lcsc.com/lcsc/2110250930_Normand-SK6805-EC20_C2890036.pdf` | HTTP 200 but **`text/html`** anti-bot interstitial, 56 572 B. Rejected by magic-byte check |
 | **`https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2110250930_Normand-SK6805-EC20_C2890036.pdf`** | ✅ **HTTP 200, `%PDF`, 804 947 B** — with a Chrome 131 UA and an `https://www.lcsc.com/` referer |
 
diff --git a/components/normand/sk6805-ec20/artifacts/WRONG-PART-ipixel-catalog-adafruit-4492.pdf b/components/normand/sk6805-ec20/artifacts/WRONG-PART-ipixel-catalog-adafruit-4492.pdf
deleted file mode 120000
index cf207f5..0000000
--- a/components/normand/sk6805-ec20/artifacts/WRONG-PART-ipixel-catalog-adafruit-4492.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/normand/sk6805-ec20/artifacts/WRONG-PART-ipixel-catalog-adafruit-4492.pdf
\ No newline at end of file
diff --git a/components/nsiway/ns4150b/README.md b/components/nsiway/ns4150b/README.md
deleted file mode 100644
index d48eb3c..0000000
--- a/components/nsiway/ns4150b/README.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# Nsiway NS4150B
-
-- **Category:** mono **class-D audio power amplifier**, ~3 W into 4 Ω class, single-supply, with a shutdown/enable input
-- **Manufacturer:** Nsiway (NSIWAY / 纳芯威)
-- **Document status:** **no datasheet obtained.** `reference-only`
-- **Research status:** **stub — identity only.** The part number is read directly from a schematic; nothing beyond that is established here
-- **Retrieved:** 2026-09-01. **Nothing verified on hardware.**
-
-## Evidence for the part number
-
-Read as the literal text `NS4150B` from the
-[ESP32-S3-ePaper-3.97 schematic](../../../devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf)
-text layer, and independently named as "NS4150B — Audio power amplifier chip" in
-Waveshare's storefront and documentation "Onboard Resources" list.
-
-Two sources, one of them design data. **The designator was confirmed to appear in the
-evidence before this record was created**, per the method's rule against creating a
-component record from a candidate or a near-miss part number.
-
-## What is *not* established
-
-Everything else. The category line above describes the NS4150/NS4150B family as
-generally understood, and is **`inferred`, not sourced** — no datasheet was obtained
-in this pass. Specifically unknown:
-
-- Supply range, output power, load impedance, efficiency, THD+N
-- Gain setting and whether it is fixed or resistor-programmable
-- Shutdown polarity and timing
-- Package and pinout
-- Whether `NS4150B` differs from `NS4150` in any way that matters
-
-**Do not design against the summary line at the top of this file.** Obtain the
-datasheet first.
-
-## Acquisition status
-
-| Field | Value |
-|---|---|
-| Disposition | **`reference-only`** |
-| Reacquisition | **`manual`** |
-| Attempts this pass | **none** — the part was identified late, and Waveshare's `files.waveshare.com/wiki/common/` pool was not probed for it |
-| Suggested next attempts | `files.waveshare.com/wiki/common/NS4150B.pdf` and variants; Nsiway's own site; the usual distributor datasheet aggregators |
-| Licence | `unknown` |
-
-Recorded honestly as an open acquisition rather than omitted — per the method,
-a failed or unattempted acquisition belongs in the record.
-
-## Used by
-
-### [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-
-The board's speaker amplifier, sitting between the
-[ES8311 codec](../../everest-semiconductor/es8311/README.md) DAC output and the
-**MX1.25 / PH1.25-2P speaker header `H2`**. The board ships with an **8 Ω 1 W
-speaker** in every SKU, per the storefront's package contents.
-
-Schematic nets around it include `PA_INL+`, `PA_INL-`, `PA_OUTL+`, `PA_OUTL-`, with
-`AudioCTR_PIN` on **GPIO39** as the enable/gate — a pin the schematic's allocation
-table **also** assigns to the IMU's `AXIS_INT1`, which is
-[unresolved](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws9--gpio39-carries-two-functions).
-
-Series inductors `L7`/`L8` on the outputs are consistent with class-D output
-filtering. `inferred` from net adjacency.
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-Designator **U5** on schematic sheet 3. Analog input from the
-[ES8311](../../everest-semiconductor/es8311/README.md) DAC (`INP` pin 3, `INN` pin 4), output
-`VOP`/`VON` (pins 8/5) through ferrites FB1/FB2/FB3 to the 8 Ω 1 W cavity speaker. Input network
-R16/R17 100 k 1 %, R23 10 k 1 %; `BYPASS` (pin 2) to C16 1 µF.
-
-**`CTRL` (pin 1) = the `AMP_EN` net, and no GPIO reaches it.** `AMP_EN` is generated in hardware
-from the 3.5 mm jack's `HP_DET` contact through D3 (`1N4148WT`) and Q4 (`2N7002T`) with
-R40/R42 1 k. Inserting a plug mutes the amplifier; **software can neither read the jack state nor
-override the mute.** This is the mechanism behind M5Stack's note *"When a 3.5 mm headphone jack
-is inserted, the speaker amplifier will be disabled."*
-
-Replaces the [NS4168](../ns4168/README.md) used on the Cardputer v1.0/v1.1, which took I²S
-directly and had no analog input, no enable control and no line-out path.
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.2.*
-
-## See also
-
-- [ES8311](../../everest-semiconductor/es8311/README.md) — the codec that feeds it
-- [All components](../../README.md)
diff --git a/components/nsiway/ns4168/README.md b/components/nsiway/ns4168/README.md
deleted file mode 100644
index b379d9e..0000000
--- a/components/nsiway/ns4168/README.md
+++ /dev/null
@@ -1,106 +0,0 @@
-# NSIWAY NS4168 — I²S input class-D audio amplifier
-
-> The speaker amplifier on the **Cardputer v1.0 and v1.1**.
-> Record created **2026-09-04**. Sibling already in this repository:
-> [`nsiway/ns4150b`](../ns4150b/README.md), which is the **analog**-input part the Cardputer ADV
-> uses instead.
-
-## Function
-
-A mono **class-D amplifier with an integrated I²S receiver and DAC**. It takes a digital I²S
-stream directly — no separate codec — and drives a speaker. That is what makes it attractive for
-a small MCU board: three pins from the host, one part, and you have audio out.
-
-The trade-off is that it is **output only**. There is no ADC, no analog input path, no headphone
-driver and no I²C control interface: everything is fixed by hardware.
-
-## Key capabilities
-
-| Property | Value | Evidence |
-|---|---|---|
-| Input | **I²S** (`BCLK`, `LRCLK`, `SDATA`) | M5Stack PinMap |
-| Output | mono, bridge-tied load | board: 8 Ω 1 W cavity speaker |
-| Rated output | **1 W into 8 Ω** on this board | Cardputer spec table |
-| Control | none — **no I²C**, no register interface | board wiring |
-| Supply | 3.3 V / 5 V class part | — |
-| Enable / shutdown | present on the part; **not routed to a GPIO** on the Cardputer | schematic |
-
-## Pinout as used
-
-| Signal | Cardputer v1.0 / v1.1 GPIO |
-|---|---|
-| `BCLK` | **G41** |
-| `LRCLK` | **G43** |
-| `SDATA` | **G42** |
-
-From the M5Stack PinMap table ("Speaker & IR") and corroborated by
-[`M5Unified`](https://github.com/m5stack/M5Unified/blob/8530f5377d782e4a25a6c482de2e71c3f75ca8eb/src/M5Unified.cpp#L3018-L3031):
-
-```cpp
-case board_t::board_M5Cardputer:
-case board_t::board_M5CardputerADV:
-  if (cfg.internal_spk) {
-    spk_cfg.pin_bck = GPIO_NUM_41; spk_cfg.pin_ws = GPIO_NUM_43;
-    spk_cfg.pin_data_out = GPIO_NUM_42;
-    spk_cfg.magnification = 16; spk_cfg.i2s_port = I2S_NUM_1;
-    if (_board == board_t::board_M5CardputerADV) spk_enable_cb = _speaker_enabled_cb_cardputer_adv;
-  }
-  break;
-```
-
-Note the shape of that code: **the same three pins serve both generations**, and the ADV differs
-only by installing an enable callback that configures its ES8311. On the v1.x there is no
-callback because there is nothing to configure — the NS4168 has no control interface at all.
-
-`spk_cfg.magnification = 16` is a **software** gain applied by M5Unified before the samples
-leave the I²S port. It is the only volume control in the v1.x signal chain that is not the
-digital sample values themselves.
-
-## Used By
-
-### M5Stack Cardputer v1.0 (K132) and v1.1 (K132-V11)
-
-[`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md)
-
-Wired as above, driving the internal cavity speaker (8 Ω, 1 W). There is **no headphone jack** on
-either board and no way to add one without an external DAC — the NS4168's output is a
-bridge-tied class-D switching waveform, not a line-level signal.
-
-**Replaced on the Cardputer ADV** by an [ES8311](../../everest-semiconductor/es8311/README.md)
-codec plus an [NS4150B](../ns4150b/README.md) analog-input amplifier. That two-part arrangement
-costs an extra IC and two I²C pins, and buys: a real ADC path, a line-level output for the 3.5 mm
-jack, an amplifier enable (`AMP_EN`) that the headphone-detect circuit can mute, and
-software-controllable codec gain.
-
-## Artifacts
-
-M5Stack mirrors a datasheet — **Chinese only**:
-
-```
-https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/NS4168_CN_datasheet.pdf
-```
-829 468 B, SHA-256 `479e75a104f48f31584683e5cd3e0d46843884af9da9137680b57700e6a6aab3`,
-retrieved 2026-09-04. **Fetched into scratch, not committed here.**
-
-Per the skill's multi-language policy: **no English version was located**, so this Chinese
-document is the **primary source** for this part and should be retained on its own merits when a
-staging decision is made. The same pattern was recorded for the RX8130CE during the PaperMono
-pass — M5Stack mirrors some datasheets only in Chinese.
-
-## Substitutes
-
-| Part | Note |
-|---|---|
-| **NS4150 / NS4150B** | **analog** input — not a drop-in for an I²S source. This is the ADV's part. |
-| MAX98357A | the common Western equivalent: I²S in, class-D out, has a gain/channel-select pin |
-| Any I²S class-D amp | check the I²S format (the NS4168 expects standard Philips I²S) and the shutdown-pin polarity |
-
-## Gaps
-
-* Datasheet **retrieved but not mined** — no register map exists to mine (the part has no
-  registers), but efficiency, THD+N, supply range, shutdown-pin behaviour and the exact I²S
-  format tolerances are not transcribed.
-* **No English datasheet located.**
-* Whether the part's shutdown pin is tied active or left floating on the Cardputer was **not
-  determined** — the v1.x schematic block was not cropped at sufficient resolution in this pass.
diff --git a/components/nxp/pcf85063a/README.md b/components/nxp/pcf85063a/README.md
index 60595d0..9bc3e46 100644
--- a/components/nxp/pcf85063a/README.md
+++ b/components/nxp/pcf85063a/README.md
@@ -743,24 +743,9 @@ The two parts are close enough to be dangerous:
 
 ## Used By
 
-- [LilyGO T-Display-S3 AMOLED Plus](../../../devices/lilygo/t-display-s3-amoled-plus/README.md) — designator `U7`, part string `PCF85063ATL/1`, backed by a **Seiko MS412FE-FL26E** rechargeable lithium coin cell at `U8` so the clock survives a main-battery swap. The only board in the T-Display-S3 family with a battery-backed RTC other than the round DS-series boards (which use a [PCF8563](../pcf8563/README.md) instead).
-- [LilyGO T-Display-S3 Pro MVSRBoard](../../../devices/lilygo/t-display-s3-pro-mvsrboard/README.md) — the **R** in *MVSR*. LilyGO mirrors `PCF85063ATL-1,118.pdf` in the `T-Display-S3-Pro` repository @ `08b8b2b`; not retrieved by that pass, since this record already holds the part.
-
 - [Soldered Inkplate 5](../../../devices/soldered-electronics/inkplate-5/README.md) — reference designator `U7`, I²C `0x51` on ESP32-WROVER `IO21`/`IO22`, `INT` → `IO39` via `JP2`, coin cell `K10`. **`C34`/`C35` are DNP**, so the internal load capacitors are the entire crystal load
 - [Soldered Inkplate 5 Gen 2](../../../devices/soldered-electronics/inkplate-5-gen2/README.md) — reference designator `U7`, same wiring, coin cell `K11`. **`C34`/`C35` = 12 pF fitted** — see §4.1, the correct `CAP_SEL` differs from the Inkplate 5
 - [ZeroWriter Ink](../../../devices/zerowriter/zerowriter-ink/README.md) — reference designator `U7` on the respun "Zerowriter Inkplate 5 Gen2" main board. **Unchanged from the Gen 2 design**, including the 12 pF load capacitors, plus test points `TP73` (`GPIO_39`) and `TP74` (`CLKOUT_RTC`)
-- [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md) — *added 2026-09-01*. Waveshare names the part **`PCF85063`**; the schematic label is **`PCF85063ATL`** (TSSOP14). On the board's **single shared I²C bus** (GPIO41 SDA / GPIO42 SCL) together with an [AXP2101](../../x-powers/axp2101/README.md) PMIC at `0x34`, an [ES8311](../../everest-semiconductor/es8311/README.md) codec, an [SHTC3](../../sensirion/shtc3/README.md) at `0x70` and a [QMI8658A](../../qst/qmi8658a/README.md) IMU. Interrupt net `RTC_INT_ESP` → **GPIO45**. Backup power comes from a dedicated **PH1.25-2P coin-cell header `H4`** (net `VBACKUP`, via `R61` 0 Ω) which the **AXP2101 actively charges at 3.0 V** — so *fitting a non-rechargeable cell to that header would charge a primary cell*. The `0x51` address is the part's documented default and was **not** confirmed against this board's source (`inferred`)
-
-### A second, staler copy of this datasheet — *added 2026-09-01*
-
-Waveshare mirrors this datasheet from `files.waveshare.com/wiki/common/` and links it from the ESP32-S3-ePaper-3.97 documentation. Hashed against the NXP copy already held here:
-
-| Copy | Bytes | SHA-256 | Revision |
-|---|---:|---|---|
-| NXP original | 726 288 | `a09223db…f430f6000b` | **Rev. 7, 30 March 2018** |
-| [`artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf`](artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf) | 535 722 | `93b384873539e770305b8982bcfa6387eac695650063b6a11279beae7a20602a` | **Rev. 6, 2015** |
-
-**Both retained**, per the method's rule that the same document at a different hash means keep both and investigate. Waveshare ships a copy **three years and one revision behind** the manufacturer's — a third independent confirmation of the "re-hosted third-party PDFs may be stale" warning in the [Waveshare sourcing guide](../../../vendors/waveshare/README.md). **Design against Rev. 7**; the mirror documents only what Waveshare hands its customers. Retrieved 2026-09-01, validated by magic bytes, licence `unknown`, disposition `repository`.
 
 ## Related pages
 
diff --git a/components/nxp/pcf85063a/artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf b/components/nxp/pcf85063a/artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf
deleted file mode 100644
index d875727..0000000
Binary files a/components/nxp/pcf85063a/artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf and /dev/null differ
diff --git a/components/nxp/pcf8563/README.md b/components/nxp/pcf8563/README.md
deleted file mode 100644
index e7f8d3b..0000000
--- a/components/nxp/pcf8563/README.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# NXP PCF8563
-
-- **Category:** real-time clock/calendar, I²C-bus, with alarm, timer and a programmable
-  clock output. Low-voltage, extremely low standby current.
-- **Manufacturer:** NXP Semiconductors (originally Philips).
-- **Retrieved:** 2026-09-07
-- **Sibling here:** [`pcf85063a`](../pcf85063a/README.md) — the newer, smaller NXP RTC used on
-  other boards in this repository.
-
-> **This record was created 2026-09-07 to fill a gap.** The directory already held
-> [`artifacts/pcf8563-datasheet-rev-11.pdf`](artifacts/pcf8563-datasheet-rev-11.pdf) (495 457 B,
-> added 2026-08-23 by an earlier pass) with **no `README.md` beside it**. The datasheet was
-> **not read** by this pass; nothing below is transcribed from it. This is a stub whose purpose
-> is to make the artifact discoverable and to record which device uses the part.
-
-## 1. Identity
-
-| Property | Value |
-|---|---|
-| Part | **PCF8563** |
-| Datasheet | Rev. 11, retained locally as `artifacts/pcf8563-datasheet-rev-11.pdf` — acquired 2026-08-23 by an earlier pass; provenance URL not recorded at the time |
-| Interface | I²C |
-| Address | **not verified here.** The PCF8563 is conventionally at `0x51`; that is stated as an expectation, not a finding |
-
-**Provenance gap:** the artifact has no acquisition record. NXP publishes PCF8563 openly
-(`nxp.com`, document `PCF8563`), so re-acquisition is `automatic`; the exact URL used
-originally is unknown.
-
-## 2. Used By
-
-### LilyGO T-Display-S3 AMOLED 1.43″ / 1.75″
-→ [`devices/lilygo/t-display-s3-amoled-1-43-1-75`](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md)
-
-The RTC on LilyGO's round AMOLED boards, and the reason those are the only boards in the
-[T-Display-S3 family](../../../devices/lilygo/t-display-s3-shared/README.md) that can wake from
-deep sleep at a **wall-clock time** rather than after an interval.
-
-`PCF8563_INT` is **GPIO9** in `components/private_library/pin_config.h` @
-`87aabe888eea6a7c0f95ce1991ca75fa98c2a172` — **the same pin that file assigns to `TP_INT`**.
-Either the two open-drain interrupts are wire-ORed or one define is wrong; **no schematic is
-published for these boards**, so it is unresolved. If you use both the touch controller and an
-RTC alarm, your ISR must distinguish them by polling both devices.
-
-I²C bus: SDA **GPIO7** / SCL **GPIO6**, shared with the
-[FT3168 touch controller](../../focaltech/ft3168/README.md) and the
-[SY6970 PMIC](../../silergy/sy6970/README.md).
-
-Vendor examples @ `87aabe8`: `PCF8563`, `PCF8563_Scheduled_INT`, `PCF8563_Timer_INT`,
-`Deep_Sleep_PCF8563_Scheduled_Wake_Up`, `Deep_Sleep_PCF8563_Timer_Wake_Up`. LilyGO also
-mirrors two PCF8563 documents in that repository (`PCF8563.pdf`, 498 308 B, and a Chinese
-`C5795601_实时时钟RTC_PCF8563_规格书_WJ490310.pdf`, 3 131 978 B) — **neither retrieved**, since
-this record already holds an NXP copy. Whether the LilyGO mirror is the same revision as the
-retained Rev. 11 is **unknown**.
-
-## 3. Gaps
-
-- Datasheet not read; no register, address or electrical value recorded.
-- Original acquisition URL unknown.
-- The GPIO9 double-assignment on the LilyGO boards is unresolved.
-- The LilyGO mirror was not compared against the retained copy.
diff --git a/components/omnivision/ov2640/README.md b/components/omnivision/ov2640/README.md
index ce65ab0..e755ca5 100644
--- a/components/omnivision/ov2640/README.md
+++ b/components/omnivision/ov2640/README.md
@@ -272,6 +272,6 @@ See [`gaps-and-conflicts.md` §5](../../../devices/seeed-studio/xiao-esp32s3-sen
 | D2 | `espressif/esp32-camera` | Espressif | primary | repository | <https://github.com/espressif/esp32-camera> | 2026-08-30 | tag **v2.0.15** | SCCB address `0x30`, PID `0x26`, **the bank-switching mechanism**, register names, clock-change sequence | not vendored |
 | S1 | XIAO ESP32S3 Sense records | this repository | — | internal | — | 2026-08-30 | — | §6 wiring, the sensor-identity conflict | `devices/seeed-studio/xiao-esp32s3-sense/` |
 
-**Acquisition note.** D1 was fetched independently and proved **byte-identical (SHA-256 `4460f2f1…`)** to the copy already in this repository — one artifact, two source URLs, per skill §18. A second URL (`OV2640_DS.pdf`, advertised as "software application notes") returned **the same bytes**; that duplicate has been archived to `components/omnivision/ov2640/artifacts/ov2640-datasheet-v2.2.pdf` rather than retained. No separate OV2640 application-notes document was located.
+**Acquisition note.** D1 was fetched independently and proved **byte-identical (SHA-256 `4460f2f1…`)** to the copy already in this repository — one artifact, two source URLs, per skill §18. A second URL (`OV2640_DS.pdf`, advertised as "software application notes") returned **the same bytes**; that duplicate has been archived to `../hardware-doc-archive/doc/hardware/components/omnivision/ov2640/artifacts/DUPLICATE-of-ov2640-datasheet.pdf` rather than retained. No separate OV2640 application-notes document was located.
 
 > **Redistribution: `unknown`.** D1 is marked *"Proprietary to OmniVision Technologies"*; no explicit redistribution clause was located in v1.6 — unlike the OV3660 and OV5640 datasheets, which carry one. The specification tables above are extracted factual data, not a reproduction of the document.
diff --git a/components/omnivision/ov2640/artifacts/DUPLICATE-of-ov2640-datasheet.pdf.BROKEN-LINK.md b/components/omnivision/ov2640/artifacts/DUPLICATE-of-ov2640-datasheet.pdf.BROKEN-LINK.md
deleted file mode 120000
index 6c116d3..0000000
--- a/components/omnivision/ov2640/artifacts/DUPLICATE-of-ov2640-datasheet.pdf.BROKEN-LINK.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/omnivision/ov2640/artifacts/DUPLICATE-of-ov2640-datasheet.pdf.BROKEN-LINK.md
\ No newline at end of file
diff --git a/components/omnivision/ov3660/README.md b/components/omnivision/ov3660/README.md
index b947347..caa6f98 100644
--- a/components/omnivision/ov3660/README.md
+++ b/components/omnivision/ov3660/README.md
@@ -227,10 +227,10 @@ The OV3660 datasheet and Seeed module specification currently live in the **devi
 > `devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/`; hashes re-verified unchanged after the
 > move, and a [pointer](../../../devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/RELOCATED-ov3660.md)
 > remains at the old location. This was a **move, not a copy** (duplication is what the shared-asset pass is
-> removing, and the document limits redistribution) and **not an archive** — with all five re-fetch URLs 404 as of
+> removing, and redistribution is `prohibited`) and **not an archive** — with all five re-fetch URLs 404 as of
 > 2026-08-30, these are scarce and stay in the repository.
 
-> **Redistribution: `restricted`.** The datasheet states: *"Individuals and/or organizations are not allowed to re-distribute said information."* Rehosting by Seeed does not relicense it. The specification tables in this record are extracted factual data, not a reproduction of the document.
+> **Redistribution: `prohibited`.** The datasheet states: *"Individuals and/or organizations are not allowed to re-distribute said information."* Rehosting by Seeed does not relicense it. The specification tables in this record are extracted factual data, not a reproduction of the document.
 
 ### 9.1 Independent re-acquisition failed
 
diff --git a/components/omnivision/ov5640/README.md b/components/omnivision/ov5640/README.md
index 4fac303..5af2ce9 100644
--- a/components/omnivision/ov5640/README.md
+++ b/components/omnivision/ov5640/README.md
@@ -299,7 +299,7 @@ The 15 fps full-resolution figure in §2 is a sensor number. On an ESP32-S3 over
 - The exact provenance and module-specificity of the AF blob in the Seeed-distributed library is unverified; whether it is OmniVision's reference image or a module-house variant is unknown.
 - No measured frame rates on ESP32-S3 for this record.
 - The `0x3600`–`0x37FF` analog register meanings remain undocumented by OmniVision; nothing in this record resolves them.
-- [AN] is marked *"Company Confidential / OmniVision Confidential for BYD Only"* on every page. It circulates widely via module vendors, but its redistribution status is **`restricted`/`unknown`** and it is retained here for research use only. Flagged for review.
+- [AN] is marked *"Company Confidential / OmniVision Confidential for BYD Only"* on every page. It circulates widely via module vendors, but its redistribution status is **`prohibited`/`unknown`** and it is retained here for research use only. Flagged for review.
 
 ---
 
diff --git a/components/panasonic/axe512127d/README.md b/components/panasonic/axe512127d/README.md
deleted file mode 100644
index 98a7fdd..0000000
--- a/components/panasonic/axe512127d/README.md
+++ /dev/null
@@ -1,279 +0,0 @@
-# Panasonic AXE512127D
-
-> **A4S-series narrow-pitch board-to-board connector — the SOCKET half.** 0.4 mm pitch, **12 contacts**, 0.8 mm mated height, 2.5 mm body width, gold-plated, RoHS.
-> Research snapshot **2026-09-01**. Fitted as **`J6` on sheet 4** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), where it carries the whole KEY/RGB/PDM sub-board interface.
-> Its mating half is [**`AXE612124D`**](../axe612124d/README.md), `J1` on sheet 5. **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Panasonic **A4S (0.4 mm pitch)** series datasheet, document `ACCTB7E 201602-T`, issued **2016-02-29**; local copy `artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf` | `not-tested` |
-| **[SCH-V]** | Read off the schematic rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[SCH-M]** | Recovered from the schematic's `CO`/`PI` marker layer | `executed-success` for the extraction |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`AXE512127D`** | **[SCH-V]**; **[DS]** p. 2 product-type table |
-| Manufacturer | **Panasonic Industry** (Panasonic Electric Works) | **[DS]** |
-| Series | **A4S**, "Narrow pitch connectors, 0.4 mm pitch" | **[DS]** cover |
-| Half | **Socket** (`AXE5…`) | **[DS]** ordering key |
-| Mating half | **`AXE612124D`** — Header | **[DS]** p. 2, 4 mm-pitch packaging table, 12-pin row |
-| Contacts | **12** | **[DS]**; **[SCH-M]** |
-| Pitch | **0.4 mm** | **[DS]** |
-| Mated height | **0.8 mm** | **[DS]** |
-| Body | **4.90 × 2.50 mm**, height **0.77 mm** | **[DS]** socket dimension table, 12-pin row |
-| Suffix `D` | **4 mm-pitch embossed packaging**, 15 000 pcs/reel | **[DS]** p. 2 |
-| Datasheet | `ACCTB7E 201602-T`, **11 pages**, issued 2016-02-29 | **[DS]** metadata |
-
-### 1.1 Reading the part number **[DS]** ordering key
-
-```
-AXE  5  12  1  27  D
-     │  │   │  │   └── packaging: nil = 8 mm emboss, D = 4 mm emboss
-     │  │   │  └────── surface treatment / variant
-     │  │   └───────── mated height  (socket: 1 = for 0.8 / 1.0 mm)
-     │  └───────────── number of pins (2 digits)  = 12
-     └──────────────── 5 = A4S socket,  6 = A4S header
-```
-
-So `AXE512127D` and `AXE612124D` are the socket/header pair for **12 pins at
-0.8 mm mated height in 4 mm embossed tape** — the exact row Panasonic's table
-prints together. This is *decoded from the manufacturer's own key*, not guessed.
-
-> ⚠ **This is the A4S series at 0.4 mm pitch, not a 0.5 mm part.** The `AXE`
-> prefix is used across several Panasonic narrow-pitch families and it is easy to
-> assume 0.5 mm from the pitch of neighbouring connectors on the same board. The
-> datasheet's title, cover and dimension tables all say **0.4 mm**. **[DS]**
-
----
-
-## 2. Specifications **[DS]** p. 3
-
-| | Item | Value |
-|---|---|---|
-| **Electrical** | Rated current | **0.3 A per contact** (max **5 A** across all contacts) |
-| | Rated voltage | **60 V AC/DC** |
-| | Dielectric strength | 150 V AC for 1 min |
-| | Insulation resistance | min. **1000 MΩ** initial, 250 V DC megger |
-| | **Contact resistance** | **max. 90 mΩ** (JIS C 5402) |
-| **Mechanical** | Composite insertion force | max. 1.200 N × contacts |
-| | Composite removal force | min. 0.165 N × contacts |
-| | Contact holding force (socket) | min. 0.20 N per contact |
-| | **Insertion/removal life** | **30 cycles** |
-| **Environmental** | Ambient temperature | **−55 °C to +85 °C**, no icing or condensation |
-| | Soldering heat | reflow peak **≤ 260 °C**; iron 300 °C/5 s, 350 °C/3 s |
-| | Storage | −55…+85 °C (product), **−40…+50 °C (emboss packing)** |
-| | Thermal shock | 5 cycles −55/+85 °C, IR ≥ 100 MΩ, CR ≤ 90 mΩ |
-| | Humidity | 120 h at 40 °C / 90–95 % RH |
-| | Saltwater spray | 24 h, 5 % ± 1 %, IEC 60068-2-11 |
-| | **H₂S resistance** | 48 h, 3 ppm ± 1 ppm at 40 °C — CR ≤ 90 mΩ |
-| **Materials** | Moulding | LCP resin, UL94V-0 |
-| | Contact/post | copper alloy, Ni base + **Au** surface; socket terminals carry **Ni barriers** against solder rise |
-| Unit weight | 20-pin socket **0.02 g** / header 0.01 g | |
-
-> ⚠ **30 insertion/removal cycles.** This is the number to notice. The sub-board
-> joint is *not* a serviceable connector in any repeated sense — it is an assembly
-> interconnect. Repeatedly separating the KEY/RGB/PDM board for debugging will
-> exhaust the rating quickly, and the failure mode is intermittent contact rather
-> than an obvious open. **[DS]** + **[INF]**
-
-Panasonic's own headline features for the series: 2.5 mm body width (30 % narrower
-footprint than the older F4S), "Tough Contact" construction — Ni-barrier against
-solder rise, bellows contacts against drop shock, V-notch and double contacts
-against particles and flux, and porosity treatment against corrosive gases.
-**[DS]** cover.
-
----
-
-## 3. Used By
-
-### `devices/m5stack/papermono` — `J6`, sheet 4
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md). This
-connector joins the mainboard to the **KEY / RGB / PDM sub-board**
-(`PaperMono KEY RGB.SchDoc`, sheet 5), which carries the three buttons, the side
-RGB indicator and the PDM microphone.
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes**. The Lite drops only NFC and LoRa; it keeps the buttons, the
-RGB LED and the microphone, all of which live on this sub-board. The Lite's
-schematic is published only as a 4-sheet `PRJ` PDF and its `J6` was not read
-directly.
-
-### 3.1 Pinout **[SCH-V]** — identical on both halves
-
-Read off **both** sheet 4 (`J6`, this socket) and sheet 5 (`J1`, the
-[AXE612124D](../axe612124d/README.md) header) rendered at 200 dpi. The two
-symbols are drawn identically, which is the check that the pair mates 1↔1.
-
-| Pin | Net | Purpose |
-|---:|---|---|
-| **1** | `3V3_L0` | **always-on rail** — reaches the sub-board even in the deepest power state |
-| **2** | `GND` | tied to end tabs 13/14 (§3.2) |
-| **3** | `3V3_L2` | main system rail; decoupled by `C76` = 10 µF/10 V (mainboard) and `C5` = 10 µF/10 V (sub-board) |
-| **4** | `PDM_VDD` | microphone rail, switched by `U21` [AW35122FDR](../../awinic/aw35122/README.md) |
-| **5** | `PY_LED_R` | RGB LED red — driven by the [M5PM1](../../m5stack/m5pm1/README.md), on/off only |
-| **6** | `PWR_BTN` | power button, pulled up on the sub-board to **`3V3_L0`** by `R1` = 10 kΩ |
-| **7** | `PYB_LED_G` | RGB LED green — [M5IOE1](../../m5stack/m5ioe1/README.md) PWM |
-| **8** | `G2_KEY1` | user button A → ESP32-S3 GPIO2 |
-| **9** | `PYB_LED_B` | RGB LED blue — M5IOE1 PWM |
-| **10** | `G3_KEY2` | user button B → ESP32-S3 GPIO3 **(a strapping pin)** |
-| **11** | `G46_PDM_DAT` | PDM data → ESP32-S3 GPIO46 **(a strapping pin)**, `R3` = 22 Ω series |
-| **12** | `G45_PDM_CLK` | PDM clock → ESP32-S3 GPIO45 **(a strapping pin)**, `R4` = 22 Ω series |
-| 13, 14 | `GND` | **soldering tabs**, not signal contacts (§3.2) |
-| 15, 16 | `GND` | soldering tabs, tied together |
-
-> ⚠ **Three of the twelve signals are ESP32-S3 strapping pins** — GPIO3, GPIO45
-> and GPIO46. Holding user button B, or a microphone that drives its lines during
-> reset, perturbs the straps. This is a board-level hazard already recorded in
-> [`pinouts-and-buses.md`](../../../devices/m5stack/papermono/pinouts-and-buses.md);
-> it is repeated here because the *connector* is where those signals cross a
-> separable joint, and a mis-seated sub-board is one plausible cause of a boot
-> that behaves differently after reassembly. **[INF]**
-
-### 3.2 "Pins 13–16" are soldering tabs, and the datasheet explains the tie
-
-The schematic symbol has **16 pins**: 12 signal contacts numbered 1–12, plus four
-marked **`MP`** and numbered 13–16. **The A4S ordering table has no 16-pin
-variant at 0.8 mm in `D` packaging; it has a 12-pin one, and that is what
-`AXE512127D` is.** **[DS]** So the four `MP` positions are the connector's
-**metal soldering terminals** (the mechanical anchors at each end), given pin
-numbers by the library symbol so they can be netted.
-
-The datasheet's dimension drawing carries the note:
-
-> *"Since the soldering terminals has a single-piece construction, sections Y and
-> Z are electrically connected."* **[DS]**
-
-That is exactly what the schematic reflects: `J6`.13 and `J6`.14 are the pair at
-one end and are drawn tied, with pin 2 joined to them and the whole net taken to
-`GND`; 15 and 16 are the pair at the other end, tied, also to `GND`. **[SCH-V]**
-
-So: **pin 2 is a ground contact**, and the end tabs are used as extra ground
-anchors — sensible, and the correct reading of an otherwise odd-looking loop in
-the drawing.
-
-> This refines the [device record's connector table](../../../devices/m5stack/papermono/pinouts-and-buses.md),
-> which lists `J6` as "16" pins. Sixteen is the *symbol's* pin count; the
-> **connector has 12 contacts plus 4 soldering tabs**. Not a contradiction — a
-> clarification. Date 2026-09-01.
-
----
-
-## 4. Substitution and migration
-
-`AXE512127D` is one row of a large table. Migrating within the series is
-mechanically clean, because Panasonic designed it that way:
-
-| Change | How |
-|---|---|
-| More or fewer signals | Any even count 10–80 exists at 0.8 mm; body length `A` = 4.50 + 0.4 × (pins − 10) mm **[DS]** |
-| Taller stack | **1.0 mm mated height uses the *same socket*** — only the header changes (`AXE6xx224`). **[DS]** feature 3: *"Mated heights of 0.8 and 1.0 mm are available for the same foot pattern"* |
-| 8 mm tape instead of 4 mm | Drop the `D`: `AXE512127`, 5000 pcs/reel |
-
-Outside the series, the near equivalents are Hirose **DF40C** (0.4 mm, and
-[already documented here](../../hirose/df40c-30dp-0.4v/README.md) for the XIAO
-Sense), JAE **WP7B**, Molex **SlimStack 55560/54722**. None is a drop-in
-footprint.
-
-> **Do not substitute across pitches.** The board also carries a
-> [`BTB0.408-10PLBDR-G41`](../../generic/btb0.408-10plbdr-g41/README.md), which is *also*
-> 0.4 mm pitch and *also* 0.8 mm mated height but is a different, unrelated part
-> from a different vendor. The two are not interchangeable and appear on adjacent
-> sheets.
-
----
-
-## 5. Integration pitfalls
-
-1. **30 mating cycles** (§2). Plan disassembly accordingly.
-2. **0.3 A per contact.** `3V3_L0`, `3V3_L2` and `PDM_VDD` each ride a *single*
-   contact. That is a hard ceiling on what the sub-board may draw per rail, and
-   the LED string plus the microphone must fit inside it. Not measured. **[INF]**
-3. **Pins 13–16 are tabs, not contacts** (§3.2) — do not count on them for
-   current beyond mechanical grounding.
-4. **The series is specified as "board-to-FPC"** in the datasheet's keywords and
-   applications, yet here it is used board-to-board. Electrically identical;
-   worth knowing when reading Panasonic's application notes, which assume a flex
-   on one side. **[DS]** + **[INF]**
-5. **Emboss-packing storage is −40…+50 °C**, narrower than the product's own
-   −55…+85 °C. Relevant only to stock handling.
-6. **Three strapping pins cross this joint** (§3.1).
-
----
-
-## 6. Open questions
-
-- The `27` field in `AXE512127D` (surface treatment / Ni-barrier option) is
-  decoded only as far as the datasheet's ordering key goes; the exact plating
-  variant it selects was not established.
-- Current derating with all 12 contacts loaded — the datasheet gives 0.3 A/pin
-  and a 5 A total but no derating curve.
-- Whether M5Stack fits `D` (4 mm tape) or plain (8 mm tape) in production; the
-  schematic says `D`, which is a *packaging* choice and does not change the part.
-- No hardware measurement of contact resistance or retention.
-
----
-
-## Manufacturer
-
-**Panasonic Industry.** No vendor sourcing guide exists in this repository yet.
-
-**⚠ Retrieval finding.** Panasonic's own CDN was **not** the working route:
-
-| Host | Result |
-|---|---|
-| `industrial.panasonic.com/content/data/CT/PDF/AXE_CT.pdf` | connection hang, then **404** |
-| **`media.digikey.com/pdf/Data Sheets/Panasonic Electric Works PDFs/A4S_Series.pdf`** | **200, `application/pdf`, `%PDF` ✓** — first try, Chrome 131 UA |
-| `www.mouser.com/catalog/specsheets/…a4s-catalog.pdf` | 200 but **13 897 B of non-PDF** under Chrome and ClaudeBot UAs; **succeeded only with the `WhatsApp/2.23.20.0` UA** |
-| `www1.futureelectronics.com/doc/PANASONIC/AXE610224_panasonic.pdf` | **200, `%PDF` ✓** (the same series document under a different part's name) |
-
-Two things worth carrying forward: **Digi-Key's `media.digikey.com` is a reliable
-mirror for Panasonic connector series documents**, and **Mouser's specsheet host
-served a short non-PDF body to browser and crawler agents but the real PDF to the
-WhatsApp link-preview agent** — the same inversion already recorded for
-`focuslcds.com` in the
-[FT6336G record](../../focaltech/ft6336g/README.md). Both belong in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-Note also that the acquired PDF is **encrypted** (`print:yes copy:yes
-change:no`), which does not impede reading but does mean tooling that rejects
-encrypted PDFs will choke on it.
-
-## Related pages
-
-- [Panasonic AXE612124D](../axe612124d/README.md) — **the mating header**, `J1` sheet 5
-- [Hirose DF40C-30DP-0.4V(51)](../../hirose/df40c-30dp-0.4v/README.md) — comparable 0.4 mm board-to-board documented here
-- [BTB0.408-10PLBDR-G41](../../generic/btb0.408-10plbdr-g41/README.md) — the board's *other* 0.4 mm connector, unrelated
-- [LMD4737T261-AC02](../../generic/lmd4737t261-ac02-pdm-microphone/README.md) · [RS-C1415MBAR](../../generic/rs-c1415mbar-rgb-led/README.md) — what lives on the far side
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | Narrow pitch connectors **A4S (0.4 mm pitch)** | Panasonic (via Digi-Key mirror) | primary, via distributor mirror | <https://media.digikey.com/pdf/Data%20Sheets/Panasonic%20Electric%20Works%20PDFs/A4S_Series.pdf> | 2026-09-01 | **`ACCTB7E 201602-T`**, issued **2016-02-29**, 11 pp, 399 357 B, AES-encrypted | the ordering key, the socket/header pairing, all of §2, the 12-pin dimensions, the soldering-terminal note | `artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf` |
-| D2 | Same document, Future Electronics mirror | Panasonic (via Future) | credible mirror | <https://www1.futureelectronics.com/doc/PANASONIC/AXE610224_panasonic.pdf> | 2026-09-01 | same series doc | second independent host for D1 | not retained (duplicate) |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `J6` = `AXE512127D`, the §3.1 pinout, the tab tie | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf` | 399 357 | `292023186ef0758f1862f8aa2a5f545dc1c14659f4ba84f14f7183f6385503b4` | 11 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) and full-text
-searched: `AXE512127` occurs three times and `AXE512127D` once, in the 4 mm
-embossed-packaging table beside `AXE612124D` on the 12-pin row — which is how the
-socket/header pairing and the pin count were established rather than inferred.
-The same file is held under the [header's record](../axe612124d/README.md)
-because both records are read standalone; it is one document, byte-identical, and
-its hash is the same in both places.
diff --git a/components/panasonic/axe512127d/artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf b/components/panasonic/axe512127d/artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf
deleted file mode 100644
index e85bbbb..0000000
Binary files a/components/panasonic/axe512127d/artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf and /dev/null differ
diff --git a/components/panasonic/axe612124d/README.md b/components/panasonic/axe612124d/README.md
deleted file mode 100644
index a605130..0000000
--- a/components/panasonic/axe612124d/README.md
+++ /dev/null
@@ -1,207 +0,0 @@
-# Panasonic AXE612124D
-
-> **A4S-series narrow-pitch board-to-board connector — the HEADER half.** 0.4 mm pitch, **12 contacts**, 0.8 mm mated height, 2.0 mm body width, gold-plated, RoHS.
-> Research snapshot **2026-09-01**. Fitted as **`J1` on sheet 5** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — i.e. on the **KEY / RGB / PDM sub-board**, mating the [`AXE512127D`](../axe512127d/README.md) socket at `J6` on the mainboard.
-> **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Panasonic **A4S (0.4 mm pitch)** series datasheet, `ACCTB7E 201602-T`, issued **2016-02-29**; local copy `artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf` | `not-tested` |
-| **[SCH-V]** | Read off sheet 5 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`AXE612124D`** | **[SCH-V]**; **[DS]** p. 2 |
-| Manufacturer | **Panasonic Industry** | **[DS]** |
-| Series | **A4S**, 0.4 mm pitch narrow-pitch connectors | **[DS]** |
-| Half | **Header** (`AXE6…`) | **[DS]** ordering key |
-| Mating half | **[`AXE512127D`](../axe512127d/README.md)** — Socket | **[DS]** p. 2, 12-pin row |
-| Contacts | **12** | **[DS]**; **[SCH-V]** |
-| Pitch | **0.4 mm** | **[DS]** |
-| Mated height | **0.8 mm** | **[DS]** — the `1` in position 4 of the code |
-| Body | **4.20 × 2.00 mm**, height **0.65 mm** | **[DS]** header dimension table, 12-pin row |
-| Suffix `D` | 4 mm-pitch embossed packaging, 15 000 pcs/reel | **[DS]** |
-| Unit weight | 0.01 g (20-pin reference) | **[DS]** |
-
-### 1.1 Header vs socket — what actually differs
-
-| | Socket `AXE512127D` | **Header `AXE612124D`** |
-|---|---|---|
-| Body length `A` (12 pin) | 4.90 mm | **4.20 mm** |
-| Body width | 2.50 mm | **2.00 mm** |
-| Height | 0.77 mm | **0.65 mm** |
-| Terminal coplanarity | 0.08 mm | 0.08 mm |
-| Plating, soldering terminals | Ni base + **Pd + Au flash** | Ni base + **Au** |
-| Contact construction | **bellows contacts**, Ni barriers, contact holding force min. 0.20 N/contact | **posts** |
-| 1.0 mm-height variant | **same socket** serves 0.8 and 1.0 mm | **different header** (`AXE612224D`) |
-
-**[DS]** pp. 3–4. The last row is the useful one: Panasonic keeps one socket
-across both stack heights and changes only the header, *"for the same foot
-pattern"*. Raising or lowering the sub-board on this design therefore means
-changing **this** part and not `J6`.
-
-The full electrical, mechanical and environmental specification is shared by both
-halves and is **tabulated once**, in the
-[socket record §2](../axe512127d/README.md#2-specifications-ds-p-3) — rated
-current **0.3 A per contact** (5 A total), rated voltage **60 V**, contact
-resistance **max 90 mΩ**, **30 insertion/removal cycles**, −55 °C to +85 °C, LCP
-UL94V-0 body.
-
-> ⚠ **30 insertion/removal cycles**, as for the socket. The sub-board joint is an
-> assembly interconnect, not a serviceable connector. **[DS]**
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — `J1`, sheet 5
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), on
-the **KEY / RGB / PDM sub-board** documented by
-`PaperMono KEY RGB.SchDoc` (sheet 5, title block dated **2026-04-14**). That
-board carries three tactile switches `S1`–`S3`, the
-[RS-C1415MBAR](../../generic/rs-c1415mbar-rgb-led/README.md) RGB indicator, the
-[LMD4737T261-AC02](../../generic/lmd4737t261-ac02-pdm-microphone/README.md) PDM
-microphone and three [ESD5311](../../generic/esd5311/README.md) clamps.
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes** — the Lite keeps the buttons, RGB LED and microphone, and
-differs only in dropping NFC and LoRa. Not read from the Lite's own schematic,
-which is published only as a 4-sheet `PRJ` PDF.
-
-> ⚠ **Sheet 5 is a different Altium document**, so its `J1` is unrelated to `J1`
-> on sheet 2 (the frontlight connector) and to `J1` on sheet 6 (the NFC
-> board-to-board). Cite it as **`J1` sheet 5**. See the
-> [BOM's designator-collision table](../../../devices/m5stack/papermono/bill-of-materials.md#3--designators-repeat-across-sheets--a-designator-alone-is-meaningless).
-
-### 2.1 Pinout **[SCH-V]**
-
-Identical to the socket's, which is the evidence that the pair mates 1↔1: both
-symbols were rendered at 200 dpi and read independently, and every net matches.
-
-| Pin | Net | On the sub-board |
-|---:|---|---|
-| **1** | `3V3_L0` | always-on rail — feeds `R1` = 10 kΩ, the **power-button pull-up** |
-| **2** | `GND` | tied to end tabs 13/14 |
-| **3** | `3V3_L2` | main system rail; **`C5` = 10 µF/10 V** bulk, and the pull-ups `R2`/`R5` = 10 kΩ for the two user keys |
-| **4** | `PDM_VDD` | microphone rail; `L1` = 2 nH and `C2` = 100 nF/10 V feed `U1` sheet 5 |
-| **5** | `PY_LED_R` | RGB red, ballast **`R8` = 1 kΩ** |
-| **6** | `PWR_BTN` | switch `S1`, clamp `DR1`, debounce `C1` = 100 nF/10 V |
-| **7** | `PYB_LED_G` | RGB green, ballast **`R7` = 820 Ω** |
-| **8** | `G2_KEY1` | switch `S2`, clamp `DR2`, debounce `C3` = 100 nF/10 V |
-| **9** | `PYB_LED_B` | RGB blue, ballast **`R6` = 560 Ω** |
-| **10** | `G3_KEY2` | switch `S3`, clamp `DR3`, debounce `C4` = 100 nF/10 V |
-| **11** | `G46_PDM_DAT` | PDM data, **`R3` = 22 Ω** series |
-| **12** | `G45_PDM_CLK` | PDM clock, **`R4` = 22 Ω** series |
-| 13, 14 | `GND` | **soldering tabs**, tied, one end |
-| 15, 16 | `GND` | soldering tabs, tied, other end |
-
-**Two rails cross this connector, and the split is deliberate.** Pin 1 carries
-`3V3_L0` (always on) and pin 3 carries `3V3_L2` (switched off in the deep power
-states). The **power button pulls up to `3V3_L0`** while the two **user keys pull
-up to `3V3_L2`** — so at the lowest power level only the power button can be
-sensed at all. That matches sheet 1's power-state table, which lists the power
-button as the `L0`/`L1` wake path and the keys only from `L2`. **[SCH-V]** +
-**[INF]**
-
-### 2.2 The `MP` positions
-
-Pins 13–16 are the connector's four **metal soldering terminals**, numbered by
-the library symbol. Panasonic's dimension drawing notes that *"since the
-soldering terminals has a single-piece construction, sections Y and Z are
-electrically connected"*, which is why the schematic ties 13↔14 (with pin 2) and
-15↔16 and takes both to ground. **[DS]** + **[SCH-V]** — full discussion in the
-[socket record §3.2](../axe512127d/README.md#32-pins-1316-are-soldering-tabs-and-the-datasheet-explains-the-tie).
-
----
-
-## 3. Substitution
-
-| Change | Part |
-|---|---|
-| **1.0 mm stack** instead of 0.8 mm | **`AXE612224D`** — socket unchanged **[DS]** |
-| 8 mm tape instead of 4 mm | `AXE612124` (drop the `D`), 5000/reel |
-| Different contact count | `AXE6xx124D` for xx ∈ {10, 12, 14, 16, 20, 24, 30, 34, 40, 44, 50, 60, 64} in `D` packaging **[DS]** p. 2 |
-
-Outside the series: Hirose **DF40C** (documented
-[here](../../hirose/df40c-30dp-0.4v/README.md)), JAE **WP7B**, Molex
-**SlimStack**. None is a footprint drop-in, and **the header and socket must be
-changed as a pair** — an A4S header will not mate a DF40 socket.
-
----
-
-## 4. Integration pitfalls
-
-1. **30 mating cycles** — the joint is not built for repeated service.
-2. **0.3 A per contact**, and `3V3_L0`, `3V3_L2` and `PDM_VDD` each cross on a
-   single contact. The RGB LED, the microphone and the pull-ups all draw through
-   those three. Not measured. **[INF]**
-3. **Header and socket are separate orderable parts** — replacing one without the
-   other, or mixing 0.8 mm and 1.0 mm halves, gives a connector that appears to
-   mate but does not seat.
-4. **`3V3_L0` and `3V3_L2` are adjacent-ish contacts (1 and 3) on a 0.4 mm
-   pitch.** A solder bridge there ties an always-on rail to a switched one, which
-   would defeat the board's whole power-domain scheme and present as "the device
-   will not power down". **[INF]**
-5. **Three ESP32-S3 strapping pins cross this joint** (GPIO3, GPIO45, GPIO46) —
-   see the [socket record §3.1](../axe512127d/README.md#31-pinout-sch-v--identical-on-both-halves).
-
----
-
-## 5. Open questions
-
-- The `24` field of `AXE612124D` (plating / variant) is decoded only as far as
-  Panasonic's published ordering key allows.
-- Whether M5Stack fits `D` or plain packaging in production — a packaging choice,
-  not a part change.
-- Per-contact derating with all 12 loaded; the datasheet gives no curve.
-- No hardware measurement of retention force, contact resistance or seating.
-
----
-
-## Manufacturer
-
-**Panasonic Industry.** No vendor sourcing guide exists in this repository yet.
-The retrieval findings for this document — Panasonic's own CDN 404s, Digi-Key's
-`media.digikey.com` works first try, and Mouser's specsheet host served the real
-PDF **only** to the `WhatsApp/2.23.20.0` user-agent — are recorded once, in the
-[socket record's Manufacturer section](../axe512127d/README.md#manufacturer),
-and belong in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-## Related pages
-
-- [Panasonic AXE512127D](../axe512127d/README.md) — **the mating socket**, `J6` sheet 4, and the shared specification table
-- [RS-C1415MBAR](../../generic/rs-c1415mbar-rgb-led/README.md) · [LMD4737T261-AC02](../../generic/lmd4737t261-ac02-pdm-microphone/README.md) — the sub-board's active parts
-- [ESD5311](../../generic/esd5311/README.md) — `DR1`–`DR3` on the same sub-board
-- [Hirose DF40C-30DP-0.4V(51)](../../hirose/df40c-30dp-0.4v/README.md) — comparable 0.4 mm board-to-board
-- [PaperMono bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | Narrow pitch connectors **A4S (0.4 mm pitch)** | Panasonic (via Digi-Key mirror) | primary, via distributor mirror | <https://media.digikey.com/pdf/Data%20Sheets/Panasonic%20Electric%20Works%20PDFs/A4S_Series.pdf> | 2026-09-01 | **`ACCTB7E 201602-T`**, issued **2016-02-29**, 11 pp, 399 357 B, AES-encrypted | the socket/header pairing on the 12-pin row, header dimensions, the shared specification, the soldering-terminal note | `artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf` |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `J1` sheet 5 = `AXE612124D`, the §2.1 pinout, the two-rail split | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf` | 399 357 | `292023186ef0758f1862f8aa2a5f545dc1c14659f4ba84f14f7183f6385503b4` | 11 |
-
-**Method note.** One document covers both halves of the pair. It is held under
-**both** records deliberately, byte-identical and with the same SHA-256, because
-each record is read standalone and a reader arriving at the header should not
-have to know the socket's part number to find the datasheet. `AXE612124D` occurs
-once in the file, in the 4 mm embossed-packaging table beside `AXE512127D` — that
-line is the whole basis for asserting the pairing.
diff --git a/components/panasonic/axe612124d/artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf b/components/panasonic/axe612124d/artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf
deleted file mode 100644
index e85bbbb..0000000
Binary files a/components/panasonic/axe612124d/artifacts/panasonic-a4s-series-connectors-digikey-mirror.pdf and /dev/null differ
diff --git a/components/puya/py32l020f15u6/README.md b/components/puya/py32l020f15u6/README.md
deleted file mode 100644
index c830655..0000000
--- a/components/puya/py32l020f15u6/README.md
+++ /dev/null
@@ -1,283 +0,0 @@
-# Puya PY32L020F15U6
-
-> **32-bit Arm Cortex-M0+ low-power microcontroller** — up to 48 MHz, 24 KB flash, 3 KB SRAM, 1.7–5.5 V, 18 GPIOs, 12-bit ADC, two comparators, SPI/I²C/USART, in a 3 × 3 mm QFN20.
-> Research snapshot **2026-09-01**. This is the silicon that M5Stack's schematic identifies as underlying **both** of its custom coprocessors on the [PaperMono](../../../devices/m5stack/papermono/README.md) — the **[M5PM1](../../m5stack/m5pm1/README.md)** power controller and the **[M5IOE1](../../m5stack/m5ioe1/README.md)** I/O expander.
-
-> **This record describes the generic Puya part only.** Everything M5Stack's chips do — register maps, I²C addresses, rail control, PWM behaviour, NeoPixel RAM — is **firmware**, and is documented in the two records linked above. Do not read the PY32L020 datasheet expecting to find `M5PM1_REG_PWM0_L`; it is not silicon.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | Puya `PY32L020 Datasheet` **V2.0**, 2025-05-20, English — local copy `artifacts/py32l020-datasheet-en-v2.0-m5stack-mirror.pdf` | `not-tested` — vendor document reproduced |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator | `executed-success` for the extraction; `not-tested` electrically |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **`PY32L020F15U6`** | **[SCH]** sheet 1; **[DS]** Table 1-1 |
-| Manufacturer | **Puya Semiconductor (Shanghai) Co., Ltd.** (普冉半导体) | **[DS]** cover |
-| Family | PY32L020 series — the **L = Low Power** branch of Puya's PY32 32-bit MCU line | **[DS]** §7 |
-| Core | **Arm Cortex-M0+**, 32-bit | **[DS]** cover |
-| Datasheet | **V2.0**, released **2025-05-20**, 51 pp | **[DS]** §8 |
-| Datasheet history | V1.0 2023-11-28 (initial) → V1.1 2024-03-08 (adds SOP16, SOP8) → **V2.0 2025-05-20 (major version)** | **[DS]** §8 |
-
-### 1.1 Decoding the ordering code **[DS §7]**
-
-```
-PY   32    L      020      F1    5     U    6    [xxx]
-│    │     │      │        │     │     │    │     └── Options: TR = tape/reel, TU = tube,
-│    │     │      │        │     │     │    │                  blank = tray, xxx = programmed-part code
-│    │     │      │        │     │     │    └──────── Temperature: 6 = −40…+85 °C
-│    │     │      │        │     │     │                          7 = −40…+105 °C
-│    │     │      │        │     │     └───────────── Package: U = QFN, P = TSSOP,
-│    │     │      │        │     │                             S = SOP,  D = DFN
-│    │     │      │        │     └─────────────────── User code memory size: 5 = 24 KB
-│    │     │      │        └───────────────────────── Pin count / pinout:
-│    │     │      │                                     F1 = 20 pins, Pinout1
-│    │     │      │                                     W1 = 16 pins, Pinout1
-│    │     │      │                                     L1 =  8 pins, Pinout1
-│    │     │      └────────────────────────────────── Sub-family: 020 = PY32L020xx
-│    │     └───────────────────────────────────────── Product type: L = Low Power
-│    └─────────────────────────────────────────────── Product family: 32-bit MCU
-└──────────────────────────────────────────────────── Company
-```
-
-**`PY32L020F15U6` = 20-pin Pinout1, 24 KB flash, QFN package, −40 to +85 °C.**
-
----
-
-## 2. Memory, and why this section exists
-
-| Resource | **PY32L020F15U6** | Evidence |
-|---|---|---|
-| **Flash** | **24 KB** | **[DS]** Table 1-1, column `PY32L020F15U6` |
-| **SRAM** | **3 KB** | **[DS]** Table 1-1 |
-
-These two numbers were the specific thing this research pass was asked not to guess, and they are **read directly out of Puya's own device table** — `Table 1-1 PY32L020x6 series product features and peripheral counts`, which lists `PY32L020F15U6` and `PY32L020L15D6` side by side, both at 24 KB flash / 3 KB SRAM. The ordering-code field `5 = 24 KB` (§1.1) corroborates it independently within the same document.
-
-The family's headline "Up to 24 KB Flash / up to 3 KB SRAM" on the datasheet cover is therefore not a range across variants — every published PY32L020 part has the same memory. **[DS]** Tables 1-1 and 1-2.
-
-**Why this matters for the M5Stack chips:** 24 KB of flash is the entire budget for M5Stack's power-management or I/O-expander firmware, including its I²C slave stack, its register file and its bootloader if it has one. That is a real constraint on what those chips can plausibly do, and it bounds any speculation about hidden capability. **[INF]**
-
----
-
-## 3. Full feature set **[DS Features]**
-
-### Core and clocking
-
-| Item | Value |
-|---|---|
-| Core | Arm 32-bit Cortex-M0+ |
-| Max frequency | **48 MHz** |
-| High-speed internal RC (HSI) | **24 / 48 MHz**, configurable, "high precision" |
-| Low-speed internal RC (LSI) | **32.768 kHz** |
-| Low-speed external crystal (LSE) | 32.768 kHz supported |
-| External clock input | Supported |
-
-### Power
-
-| Item | Value |
-|---|---|
-| **Operating voltage** | **1.7 – 5.5 V** |
-| Low-power modes | **Sleep / Stop / Deep_stop** |
-| Reset sources | Power-on / power-down reset (POR/PDR), **brown-out reset (BOR)** — BOR threshold selectable by option byte |
-| Operating temperature | −40 to +85 °C (`6`) or −40 to +105 °C (`7`) |
-
-The 1.7–5.5 V range is the notable one: it means the part can be run directly from a Li-ion cell without a regulator, which is exactly what a power-management coprocessor needs. **[INF]**
-
-### Peripherals — `PY32L020F15U6` counts **[DS Table 1-1]**
-
-| Peripheral | Count / detail |
-|---|---|
-| **GPIO** | **18**, all usable as external interrupts |
-| **ADC** | 1 × **12-bit**, **8 external + 2 internal** channels. Reference options: embedded **1.5 V / 2.048 V / 2.5 V** or `VCC` |
-| **Comparators** | **2** |
-| Advanced-control timer | 1 × 16-bit (`TIM1`) |
-| General-purpose timer | 1 × 16-bit (`TIM14`) |
-| Low-power timer | 1 × `LPTIM` — **can wake from Stop mode** |
-| Independent watchdog | 1 × `IWDG` |
-| SysTick | 1 |
-| **SPI** | 1 |
-| **I²C** | 1 — Standard (100 kHz) and Fast (400 kHz) modes, 7-bit addressing |
-| **USART** | 1, with **automatic baud-rate detection** |
-| CRC | Hardware **CRC-32** module |
-| Unique ID | Yes |
-| Debug | **SWD** (serial wire debug) |
-
-### Packages **[DS Features, §6]**
-
-QFN20, TSSOP20, SOP16, SOP8, DFN8.
-
-**QFN20 dimensions [DS §6.1]:** body **3.000 mm × 3.000 mm** (D, E; 2.900–3.100), height **0.550 mm** (A; 0.500–0.600), standoff A1 0.000–0.050 mm, ball/lead width b 0.150–0.250 mm, **exposed pad 1.650 mm × 1.650 mm** (D2, E2; 1.550–1.750). The package outline drawing is titled `Puya QFN20L 3x3X0.55-0.4PITCH POD`, i.e. **0.4 mm pitch**.
-
-### QFN20 pinout **[DS Figure 3-1, "QFN20 Pinout1 PY32L020F15U6 (Top view)"]**
-
-| Pin | Name | | Pin | Name |
-|---:|---|---|---:|---|
-| 1 | *(see note)* | | 11 | `PB4` |
-| 2 | `PA6` | | 12 | `PB3` |
-| 3 | `PA7` | | 13 | `PB2` |
-| 4 | `PC0-NRST` | | 14 | `PB1` |
-| 5 | `PC1` | | 15 | `PB0` |
-| 6 | `PB7` | | 16 | `PA0` |
-| 7 | `VSS` | | 17 | `PA1` |
-| 8 | `PB6-SWD` | | 18 | `PA2-SWC` |
-| 9 | `VCC` | | 19 | `PA3` |
-| 10 | `PB5` | | 20 | `PA4` |
-
-> **Pin 1's label was not recovered cleanly** from the datasheet's figure by text extraction; the remaining 19 assignments are contiguous and unambiguous, and `PA5` is the only port pin unaccounted for. It is very likely `PA5`, but that is **[INF]** and is not asserted. Read the figure directly if pin 1 matters to you.
-
-Note `PC0` doubles as `NRST`, and `PB6`/`PA2` carry `SWD`/`SWCLK` — so debug and reset consume three of the 18 GPIOs unless deliberately repurposed.
-
-### Family siblings **[DS Tables 1-1, 1-2]**
-
-| Part | Flash | SRAM | GPIO | ADC ch. | Comparators | Package | Temp |
-|---|---:|---:|---:|---|---:|---|---|
-| **`PY32L020F15U6`** | 24 KB | 3 KB | **18** | 8 ext + 2 int | **2** | QFN20 | 85 °C |
-| `PY32L020L15D6` | 24 KB | 3 KB | 7 | 4 ext + 2 int | — | DFN8 | 85 °C |
-| `PY32L020F15P7` | 24 KB | 3 KB | — | — | — | TSSOP20 | 105 °C |
-| `PY32L020W15S7` | 24 KB | 3 KB | — | — | — | SOP16 | 105 °C |
-| `PY32L020L15S7` | 24 KB | 3 KB | — | — | — | SOP8 | 105 °C |
-
-The `F15U6` is the **largest-GPIO, comparator-bearing** member — which is why it, and not a cheaper sibling, is the one M5Stack ships as a 14-GPIO expander.
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-
-**This part appears twice on the board, under two different M5Stack marketing names.** Schematic sheet 1's power/IO map block diagram annotates both custom chips with the silicon part number **[SCH]**:
-
-| Block label on sheet 1 | Annotation | M5Stack name | Designator | I²C address |
-|---|---|---|---|---|
-| `PMIC` | **`PY32L020F15U6`** | **[M5PM1](../../m5stack/m5pm1/README.md)** | `U7` (sheet 2) | `0x6E` |
-| `PYB` | **`PY32L020F15U6_IIC`** | **[M5IOE1](../../m5stack/m5ioe1/README.md)** | `U17` (sheet 4) | `0x4F` |
-
-#### 4.1 The package count corroborates the identification
-
-Both schematic symbols carry **21 pin markers** — 20 signal/power pins plus a 21st netted to `GND`. **[SCH]**
-
-That is exactly a **QFN20 plus exposed pad** (§3), and the PY32L020F15U6 is the only PY32L020 variant with a 20-pin QFN package. The pin counts are independent of M5Stack's own manuals, which describe pins 1–20 plus a ground pad. **[INF]** — a consistency check, not proof of the die.
-
-The M5IOE1's advertised resource set also lines up with the silicon: **14 GPIOs** (of the part's 18, minus `NRST`, the two SWD pins and the I²C pair), **4 PWM channels** (from `TIM1`/`TIM14`), a **12-bit ADC** (the part's), and a **die temperature sensor** (`[DS]` lists temperature-sensor characteristics in §5.3.15). None of that requires custom silicon. **[INF]**
-
-#### 4.2 What is silicon and what is firmware
-
-This distinction is the whole reason this record exists separately from the M5PM1/M5IOE1 records.
-
-| Behaviour | Where it comes from |
-|---|---|
-| Cortex-M0+ core, 24 KB flash, 3 KB SRAM, 48 MHz, 1.7–5.5 V, QFN20 | **Silicon** — this record |
-| 12-bit ADC, 2 comparators, TIM1/TIM14/LPTIM, SPI/I²C/USART, CRC-32, UID, SWD | **Silicon** — this record |
-| I²C addresses `0x6E` and `0x4F`; the `M5PM1_REG_*` / `M5IOE1_REG_*` maps; NeoPixel RAM; 32 B retention RAM; the wake-source state machine; the power-button long/short/double-press logic; `PWM_FREQ` registers; the `AW8737A_PULSE` register | **M5Stack firmware** — see the [M5PM1](../../m5stack/m5pm1/README.md) and [M5IOE1](../../m5stack/m5ioe1/README.md) records |
-| The `PYG`*n* pin naming, and its 1-based-label / 0-based-enum trap | **M5Stack convention**, not Puya's. Puya calls the pins `PA0`–`PB7` |
-
-> ⚠ **All of the firmware behaviour can change with a firmware revision.** M5Stack ships version registers (`M5PM1_REG_SW_REV` at `0x03`, `M5IOE1_REG_REV` at `0x02`) precisely because it can. The silicon in this record cannot change; the layer above it can.
-
-#### 4.3 The chips are not field-reprogrammable in practice
-
-The PY32L020's programming interface is **SWD** on `PB6-SWD` / `PA2-SWC` (§3). Neither pin appears on any PaperMono net that reaches a header, test point or connector in the extracted schematic text. **[SCH]**, **[INF]**
-
-So although the underlying part is an ordinary, cheap, publicly documented MCU that anyone could reflash, on this board it is effectively a fixed-function device. Recovering a bricked M5PM1 would require physically probing a 0.4 mm-pitch QFN.
-
----
-
-## 5. Development ecosystem for the bare part
-
-Relevant only if you are **using a PY32L020 in your own design**, not if you are talking to an M5PM1.
-
-| Item | Notes |
-|---|---|
-| Vendor SDK | Puya publishes an HAL/LL driver package and CMSIS device headers for the PY32 series |
-| Toolchain | Standard `arm-none-eabi-gcc` targeting Cortex-M0+ (`-mcpu=cortex-m0plus`) |
-| Debug/flash | **SWD**, with common probes (ST-LINK, DAPLink, J-Link). Puya also supports a serial bootloader on some family members |
-| Community | The PY32F0 series has an active open-source community (`IOsetting/py32f0-template` and similar) whose toolchain and linker setup carry over to the PY32L020 with a different device header. **[INF]** — not verified for the L020 specifically |
-| Arm CMSIS-Pack | Availability for PY32L020 was **not** verified this session |
-
-**No driver is needed to use an M5PM1 or M5IOE1** — those speak I²C and have their own libraries. See the linked records.
-
----
-
-## 6. Integration pitfalls (bare part)
-
-1. **24 KB flash is the whole budget.** With a printf-heavy libc you will run out.
-2. **Reset shares `PC0`, SWD shares `PB6`/`PA2`.** Repurposing them as GPIO costs you debug or reset access, and getting that wrong on a QFN20 means a dead board.
-3. **BOR is off by default** and is enabled through an **option byte**, not at runtime **[DS §2.5.2.2]**. On a battery design that is exactly backwards from what you want, and option bytes are set at programming time.
-4. **The ADC reference is selectable** between 1.5 V / 2.048 V / 2.5 V and `VCC` (§3). On a 1.7–5.5 V part, defaulting to `VCC` gives you a ratiometric measurement whose scale moves with the battery.
-5. **`LPTIM` is the only timer that wakes from Stop** (§3). Waking on `TIM1` will not work.
-6. **Two datasheet major versions exist** (§1). V1.0/V1.1 predate the V2.0 "major version" of 2025-05-20; if you have an older PDF, check what changed before trusting a table.
-
----
-
-## 7. Alternatives
-
-| Part | vs. PY32L020 | When |
-|---|---|---|
-| Puya **PY32F002 / PY32F003 / PY32F030** | The non-`L` PY32 branch — more flash, less aggressive low power | General-purpose use |
-| ST **STM32L011 / STM32G030** | Very similar class; the PY32 family is widely described as a low-cost STM32-alike | When you want ST's documentation and ecosystem |
-| **[WCH CH32V203](../../wch/ch32v203c8t6/README.md)** | RISC-V, more flash/RAM, USB | Documented in this repository — used as the Tanmatsu's coprocessor in exactly the same architectural role |
-| Nuvoton **N76E003**, Padauk **PMS150** | 8-bit, cheaper | When 24 KB of Cortex-M0+ is overkill |
-| A dedicated PMIC | Purpose-built silicon | When you do not want to write and maintain power-management firmware — see [TI BQ25895](../../texas-instruments/bq25895/README.md) for what a real PMIC's register map looks like |
-
-**The interesting comparison is the last two rows.** M5Stack's choice — a general-purpose MCU running vendor firmware, presented as a custom part — trades silicon cost and flexibility against documentation quality: every behaviour is a vendor manual away rather than a datasheet away, and every behaviour can change. The Tanmatsu makes the same trade with a CH32V203, and the Waveshare knob board makes it with a second ESP32. It is a common pattern in this repository and worth recognising as one.
-
----
-
-## 8. Open questions
-
-- **Pin 1 of the QFN20** (§3) — almost certainly `PA5`, not confirmed.
-- Whether M5Stack's firmware uses the `LPTIM`, the comparators or the CRC unit; nothing in the published register maps suggests the last two are exposed.
-- Whether the M5PM1 and M5IOE1 dies are literally the same part or differ in a way the schematic annotation glosses over. Sheet 1 annotates one `PY32L020F15U6` and the other `PY32L020F15U6_IIC`; the `_IIC` suffix is **not** a Puya ordering-code field (§1.1) and is presumably M5Stack's own note that this instance is the I²C-slave one. **[INF]**
-- Whether SWD is reachable anywhere on the PaperMono (§4.3).
-- No hardware was in the loop; nothing was measured or programmed.
-
----
-
-## Manufacturer
-
-**Puya Semiconductor (Shanghai) Co., Ltd.** No vendor sourcing guide exists in this repository yet.
-
-**Sourcing note, and a small finding in its own right.** The copy retained here did not come from Puya. It came from **M5Stack's own documentation CDN**:
-
-```
-https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/PY32L020_Datasheet_EN.pdf
-https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/PY32L020_Datasheet_ZH.pdf
-```
-
-Asset folder `1205` is the same pool the PaperMono's zh_CN documentation page uses for `ST25R3916_ZH.pdf` — i.e. **M5Stack hosts the datasheet of the silicon behind its "custom" chips, in the same place as the PaperMono's other component datasheets, but does not link it from the PaperMono product page.** The page's Datasheets list names ESP32-S3, ST25R3916, SSD1677, the touchscreen, RX8130CE, BMI270 and SX1262 — and neither PY32L020 nor the M5PM1/M5IOE1 manuals. Whether it is linked from some other M5Stack page was not checked.
-
-Both files were served as `application/pdf` to plain `curl` with a Chrome 131 User-Agent; `%PDF` verified; no fallback User-Agent and no login required. Puya's own site (`www.puyasemi.com`) is reachable but was not needed.
-
-## Related pages
-
-- [M5Stack M5PM1](../../m5stack/m5pm1/README.md) — this silicon running M5Stack's power-management firmware, I²C `0x6E`
-- [M5Stack M5IOE1](../../m5stack/m5ioe1/README.md) — this silicon running M5Stack's I/O-expander firmware, I²C `0x4F`
-- [WCH CH32V203C8T6](../../wch/ch32v203c8t6/README.md) — the same architectural pattern on a different board
-- [Espressif ESP32-S3R8](../../espressif/esp32-s3r8/README.md) — the host that both coprocessors serve
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | PY32L020 Datasheet (English) | Puya Semiconductor (Shanghai) Co., Ltd. | primary (via vendor-of-board mirror) | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/PY32L020_Datasheet_EN.pdf> | 2026-09-01 | **V2.0**, 2025-05-20, 51 pp, 2 262 732 B | **24 KB flash / 3 KB SRAM for `PY32L020F15U6`**, ordering-code decode, full peripheral table, QFN20 pinout and dimensions, family comparison, version history | `artifacts/py32l020-datasheet-en-v2.0-m5stack-mirror.pdf` |
-| D2 | PY32L020 数据手册 (Chinese) | Puya | primary (via mirror) | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/PY32L020_Datasheet_ZH.pdf> | 2026-09-01 | 49 pp, 2 652 633 B | Same content, Chinese; retained because the EN and ZH page counts differ (49 vs 51), so the two are not straight translations of one layout | `artifacts/py32l020-datasheet-zh-m5stack-mirror.pdf` |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | Sheet 1's `PMIC = PY32L020F15U6` and `PYB = PY32L020F15U6_IIC` annotations; the 21-pad symbols for `U7` and `U17` | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/py32l020-datasheet-en-v2.0-m5stack-mirror.pdf` | 2 262 732 | `b55f52c3c0a73e2d5256f715caf93ef36aca351c66974ed47838ed7a146c972d` | 51 |
-| `artifacts/py32l020-datasheet-zh-m5stack-mirror.pdf` | 2 652 633 | `ddb566b4ab1fec1cc61a5c76668003b089cb37880151a4474b18add2e6b3a5ff` | 49 |
-
-**Method note.** Both files validated as `%PDF` with intact text layers. The 24 KB / 3 KB figures in §2 were taken from `Table 1-1` by locating the `PY32L020F15U6` column explicitly, not from the cover's "up to" wording, and cross-checked against the ordering-code field `5 = 24 KB` in §7 of the same document.
diff --git a/components/puya/py32l020f15u6/artifacts/py32l020-datasheet-en-v2.0-m5stack-mirror.pdf b/components/puya/py32l020f15u6/artifacts/py32l020-datasheet-en-v2.0-m5stack-mirror.pdf
deleted file mode 100644
index 6cbd522..0000000
Binary files a/components/puya/py32l020f15u6/artifacts/py32l020-datasheet-en-v2.0-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/puya/py32l020f15u6/artifacts/py32l020-datasheet-zh-m5stack-mirror.pdf b/components/puya/py32l020f15u6/artifacts/py32l020-datasheet-zh-m5stack-mirror.pdf
deleted file mode 100644
index 6758a16..0000000
Binary files a/components/puya/py32l020f15u6/artifacts/py32l020-datasheet-zh-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/qst/qmi8658a/README.md b/components/qst/qmi8658a/README.md
deleted file mode 100644
index d89168f..0000000
--- a/components/qst/qmi8658a/README.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# QST QMI8658A
-
-- **Category:** **6-axis inertial measurement unit** — 3-axis accelerometer + 3-axis gyroscope, with an integrated motion engine (tap, step, pedometer, no-motion/any-motion)
-- **Manufacturer:** QST Corporation (矽睿科技)
-- **Interface:** I²C or SPI. I²C 7-bit address **`0x6A`** (`SA0` low) / **`0x6B`** (`SA0` high) — **`inferred` from the part's documented defaults, not confirmed against any board's source in this pass**
-- **Document status:** datasheet **Rev A** retained in [`artifacts/`](artifacts/)
-- **Research status:** **stub.** This page exists so that the boards citing the part have somewhere to link and the artifact is not orphaned. The register map has **not** been mined.
-- **Retrieved:** artifact 2026-08-23; this page written 2026-09-01. **Nothing verified on hardware.**
-
-## Why this page is thin
-
-The datasheet has been held in this repository since **2026-08-23** with no record
-page beside it. That is the condition the method warns about — an artifact nobody has
-read is a download, not research. This page converts it from an orphan into a stub
-with an honest scope, and names what remains.
-
-**Not done:** register map, ODR/range/bandwidth tables, the motion-engine command
-interface, self-test, calibration, noise and offset specifications, power modes and
-their currents, package/pinout, lifecycle and pricing, or any comparison against the
-obvious alternatives ([BMI270](../../bosch-sensortec/bmi270/README.md) is already in
-this knowledge base; LSM6DS3/QMI8658C are the other usual candidates).
-
-## What is established
-
-- QST's mainstream 6-axis part for consumer and hobby designs, widely used on ESP32
-  boards as the cheaper alternative to Bosch's BMI2xx family.
-- Supports **both** I²C and SPI, selectable by a mode pin — so a board's choice is a
-  board fact, not a part fact.
-- Ships a **motion engine** (pedometer, tap, significant-motion) that offloads the
-  host. This is the feature that makes it attractive on a battery-first device: the
-  host can stay asleep until the IMU decides something happened.
-
-Whether any given board actually uses that engine, rather than polling raw samples,
-is a per-board question and is **not** answered here for any of them.
-
-## Artifacts
-
-| File | Bytes | Source | Retrieved | Version |
-|---|---:|---|---|---|
-| [`artifacts/qmi8658a-datasheet-rev-a.pdf`](artifacts/qmi8658a-datasheet-rev-a.pdf) | 3 085 534 | *not recorded when acquired* | 2026-08-23 | **Rev A** |
-
-**The acquisition URL for this artifact was not recorded** by the pass that fetched
-it. That is a provenance gap, recorded rather than back-filled with a guess — per the
-method, a plausible-looking URL invented after the fact is worse than an honest
-`unknown`. A future pass should locate QST's own copy, hash it against this one, and
-record the source properly.
-
-**Licence `unknown`.** Disposition: `repository`.
-
-## Used by
-
-### [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-
-Named `QMI8658A` on the schematic, marketed by Waveshare as "QMI8658". On the board's
-**single shared I²C bus** (GPIO41 SDA / GPIO42 SCL) alongside the
-[AXP2101](../../x-powers/axp2101/README.md) PMIC, the
-[PCF85063A](../../nxp/pcf85063a/README.md) RTC, the
-[ES8311](../../everest-semiconductor/es8311/README.md) codec and the
-[SHTC3](../../sensirion/shtc3/README.md).
-
-| Signal | GPIO | Schematic net |
-|---|---|---|
-| `INT1` | GPIO39 | `AXIS_INT1` |
-| `INT2` | GPIO40 | `AXIS_INT2` |
-| `SDA` / `SCL` | GPIO41 / GPIO42 | `AXIS_SDA` / `AXSI_SCL` *(vendor's typo, verbatim)* |
-
-**`INT1` on GPIO39 is contested** — the schematic's allocation table puts the audio
-amplifier gate `AudioCTR_PIN` on the same pin. Unresolved; see
-[C-WS9](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws9--gpio39-carries-two-functions).
-
-Vendor examples: `Arduino/examples/06_QMI8658A` (using the bundled `SensorLib`) and
-ESP-IDF `05_QMI8658A`. Neither was read in this pass, which is why the I²C address
-above remains `inferred`.
-
-### [Xteink X3](../../../devices/xteink/x3/README.md) and [Xteink X4 Classic](../../../devices/xteink/x4-classic/README.md) — *added 2026-09-04*
-
-Two Xteink e-readers carry a QMI8658 at **I²C 0x6B**, with **`WHO_AM_I`
-(register `0x00`) == `0x05`** and **no interrupt line** on either board.
-
-| | X3 | X4 Classic |
-|---|---|---|
-| SoC | ESP32-C3 | ESP32-S3 |
-| Bus | SDA **20** / SCL **0** @ 400 kHz | SDA **39** / SCL **38** @ 400 kHz |
-| Address | 0x6B (alt 0x6A probed) | 0x6B |
-| Interrupt | **none** | **none** |
-| Bus neighbours | BQ27220 0x55, DS-series RTC 0x68 | BM8563 RTC 0x51, CW2017 gauge 0x63 |
-| Init observed | — | `CTRL1/2/3/7` written at 0x6B (RE-confirmed) |
-
-**This record's `inferred` I²C address is now corroborated.** The FreeInk SDK
-declares 0x6B for both boards, `XteinkDetect` probes it as a device fingerprint,
-and the Chinese X3 teardown BOM lists *"QMI8658 姿态传感器"* independently —
-three lines of evidence, one of them a physical teardown.
-
-**The X3 uses it as a product feature:** the vendor's launch announcement lists
-*"Built-in **gyroscope** for motion-based page turning"*
-([r/xteinkereader `1pi6ezd`](https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/), 2025-12-09).
-Whether any community firmware implements that is **not established**.
-
-**It also does a second, load-bearing job on the X3:** it is one of three parts
-`XteinkDetect::detectXteinkVerdict()` scores on the C3 boards' secondary I²C bus
-to decide at boot whether it is running on an **X3** (parts present) or an
-**[X4](../../../devices/xteink/x4/README.md)** (bus empty). A missing or
-mis-addressed IMU therefore selects the wrong board profile entirely, not merely
-a dead sensor.
-
-**No interrupt line means no wake-on-motion** on either device — the part must be
-polled, which costs power on a battery reader. Neither board's ODR, range or noise
-performance has been measured or reported.
-
-Notably, the **[X4 Pro](../../../devices/xteink/x4-pro/README.md) has no IMU at
-all**, so the "Pro" model is not a superset of its cheaper siblings.
-
-→ [`devices/xteink/x3/features/imu.md`](../../../devices/xteink/x3/features/imu.md)
-
-## See also
-
-- [Bosch BMI270](../../bosch-sensortec/bmi270/README.md) — the comparable part already recorded here
-- [QMC6310](../qmc6310/) — the other QST part in this knowledge base. **Artifacts-only directory; no record page yet**, in the same condition this one was until 2026-09-01
-- [All components](../../README.md)
diff --git a/components/raydium/rm67162/README.md b/components/raydium/rm67162/README.md
deleted file mode 100644
index b41f469..0000000
--- a/components/raydium/rm67162/README.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Raydium RM67162
-
-- **Category:** AMOLED display driver IC with on-chip GRAM; **QSPI / SPI / MIPI-DSI** host
-  interfaces; on-chip brightness (DBV) control.
-- **Manufacturer:** Raydium Semiconductor Corporation (Taiwan).
-- **Retrieved:** 2026-09-07
-
-The display driver of the **LilyGO T-Display-S3 AMOLED (1.91″)** and the
-**T-Display-S3 AMOLED Plus** — 240 × 536 panels driven over **QSPI**.
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **RM67162** |
-| Datasheet version | **V0.0** per the filename LilyGO ships (`RM67162 DataSheet_V0.0.pdf` in one repo, `RM67162 DataSheet.pdf` in the other) |
-| Local artifact | [`artifacts/rm67162-datasheet-v0.0-lilygo-mirror.pdf`](artifacts/rm67162-datasheet-v0.0-lilygo-mirror.pdf) — 3 729 479 B, SHA-256 `1717405949518703a8fe40e1dcbbb1d1abf7fa765b2bb7c2d101f430398a5b51` |
-| Mirror source | `Xinyuan-LilyGO/LilyGo-AMOLED-Series` → `datasheet/RM67162 DataSheet.pdf` @ `6d1dc008b94578cc34ba4a0f3b223dd808ca963f` |
-| Second mirror, same bytes | `Xinyuan-LilyGO/T-Display-S3-AMOLED` → `datasheet/RM67162 DataSheet_V0.0.pdf` @ `edd133335c9f7c38d1e9be2d0eb67371f1f6428e`, **3 729 479 B — identical size**, so almost certainly the same file under two names. Only one copy is retained; the second URL is recorded here rather than stored twice |
-| Licence | Raydium copyright. Repository is MIT, which does not cover the PDF. **Redistribution status: unknown** |
-
-Raydium does not publish RM67162 on an open portal; board-vendor mirrors are the acquisition
-route.
-
-## 2. Interface as used by LilyGO
-
-| Property | Value | Source |
-|---|---|---|
-| Host bus | **QSPI** — `CS`, `SCK`, `D0..D3`, plus `RST` and a `TE` input | `pins_config.h` @ `edd1333` |
-| Clock | **75 MHz**, mode 0, `SPI2_HOST` | `#define SPI_FREQUENCY 75000000` |
-| Resolution | 240 × 536 | vendor README |
-| Brightness | on-chip; ESPHome writes **`0xD0`** | `esphome/.../amoled.py` |
-| Sleep-out | ESPHome sets `no_slpout=True` and puts `SLPOUT` **early in the init sequence** for the plain AMOLED board | same |
-
-**Two boards, same controller, different initialisation.** ESPHome's `T-DISPLAY-S3-AMOLED`
-model uses `initsequence=(SLPOUT,)` — essentially nothing. Its `T-DISPLAY-S3-AMOLED-PLUS` model
-uses a **16-command sequence** (`PAGESEL 4`, `0x6A 0x00`, `PAGESEL 5`, `PAGESEL 7`, `0x07 0x4F`,
-`PAGESEL 1`, `0x2A 0x02`, `0x2B 0x73`, `PAGESEL 0x0A`, `0x29 0x10`, `PAGESEL 0`, `0x53 0x20`,
-`TEON 0x00`, `PIXFMT 0x75`, `0xC4 0x80`) and a **40 MHz** data rate against the plain board's
-75 MHz. Panel-module differences, not controller differences — but **RM67162 code does not
-port between the two LilyGO boards unchanged**, which is worth knowing before assuming it does.
-
-## 3. Software
-
-| Route | Note |
-|---|---|
-| **`LilyGo-AMOLED-Series`** | LilyGO's own library; carries the init tables. The path of least resistance |
-| `Arduino_GFX` | `Arduino_ESP32QSPI` + an RM67162 driver |
-| ESPHome | `mipi_spi`, models `T-DISPLAY-S3-AMOLED` / `T-DISPLAY-S3-AMOLED-PLUS` |
-| **`TFT_eSPI`** | **cannot drive it.** No QSPI transport. LilyGO's "TFT_eSPI examples" are Sprites pushed by the library's own QSPI routine |
-
-## 4. What was not verified
-
-The datasheet's cover and register map were **not read**; no value in this record is
-transcribed from it. Everything above is from board-level sources and from independent
-third-party (ESPHome) configuration. The `V0.0` version string is LilyGO's filename.
-
-## 5. Used by
-
-### LilyGO T-Display-S3 AMOLED (1.91″)
-→ [`devices/lilygo/t-display-s3-amoled`](../../../devices/lilygo/t-display-s3-amoled/README.md).
-QSPI on GPIO 6 (CS), 47 (SCK), 18/7/48/5 (D0–D3), 17 (RST), 9 (TE), 8 (SDO). 75 MHz. Touch,
-where fitted, is a separate Hynitron CST816 part on I²C.
-
-### LilyGO T-Display-S3 AMOLED Plus
-→ [`devices/lilygo/t-display-s3-amoled-plus`](../../../devices/lilygo/t-display-s3-amoled-plus/README.md).
-Same panel and controller, different board: BQ25896 PMIC, PCF85063ATL RTC, microSD, and a
-**different init sequence and clock** (see §2).
diff --git a/components/raydium/rm67162/artifacts/rm67162-datasheet-v0.0-lilygo-mirror.pdf b/components/raydium/rm67162/artifacts/rm67162-datasheet-v0.0-lilygo-mirror.pdf
deleted file mode 100644
index b31e220..0000000
Binary files a/components/raydium/rm67162/artifacts/rm67162-datasheet-v0.0-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/raydium/rm690b0/README.md b/components/raydium/rm690b0/README.md
deleted file mode 100644
index 645ee86..0000000
--- a/components/raydium/rm690b0/README.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# Raydium RM690B0
-
-- **Category:** AMOLED display driver IC with on-chip GRAM; QSPI/SPI/MIPI host interfaces.
-- **Manufacturer:** Raydium Semiconductor Corporation (Taiwan).
-- **Retrieved:** 2026-09-07
-
-The display driver of the **LilyGO T4-S3** — a 2.41″ 450 × 600 AMOLED, the largest and
-brightest panel in the T-Display-S3 family.
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **RM690B0** |
-| Datasheet version | **V0.2** per LilyGO's filename |
-| Native resolution | **480 × 600** per ESPHome's base `DriverChip("RM690B0", width=480, height=600)`; the T4-S3 panel is **450** wide and sits at **`offset_width=16`** |
-| Local artifact | [`artifacts/rm690b0-datasheet-v0.2-lilygo-mirror.pdf`](artifacts/rm690b0-datasheet-v0.2-lilygo-mirror.pdf) — 4 199 504 B, SHA-256 `2f21e71e83d818e6ac8285b6c883ff586951dcbce9037b3bdb2f4ee5a6350e7e` |
-| Mirror source | `Xinyuan-LilyGO/LilyGo-AMOLED-Series` → `datasheet/RM690B0 DataSheet_V0.2.pdf` @ `6d1dc008b94578cc34ba4a0f3b223dd808ca963f` |
-| Licence | Raydium copyright; repository MIT does not cover it. **Redistribution status: unknown** |
-
-## 2. Initialisation, from an independent source
-
-ESPHome's `RM690B0` driver definition (`esphome/components/mipi_spi/models/amoled.py`, `dev`,
-fetched 2026-09-07) gives a base init sequence that is useful precisely because it is **not**
-LilyGO's:
-
-```
-PAGESEL 0x20 · MIPI 0x0A · WRAM 0x80 · SWIRE1 0x51 · SWIRE2 0x2E ·
-PAGESEL 0x00 · 0xC2 0x00 · delay(10) · TEON 0x00 · NORON
-brightness 0xD0 · color_order RGB
-```
-
-`SWIRE1`/`SWIRE2` are the AMOLED brightness-control registers; `MIPI 0x0A` selects the host
-interface. Anyone writing an RM690B0 driver from scratch can start here.
-
-## 3. Software
-
-| Route | Note |
-|---|---|
-| **`LilyGo-AMOLED-Series`** | auto-detects T4-S3 |
-| ESPHome | `mipi_spi` model `T4-S3` extending `RM690B0`, `bus_mode=QUAD`, `requires psram` |
-| `TFT_eSPI` | **cannot drive it** (QSPI) |
-
-## 4. What was not verified
-
-Datasheet cover and register map not read; no value here is transcribed from it. The register
-names above are ESPHome's symbolic constants, which are themselves an interpretation.
-
-## 5. Used by
-
-### LilyGO T4-S3
-→ [`devices/lilygo/t4-s3`](../../../devices/lilygo/t4-s3/README.md).
-QSPI on GPIO 11 (CS), 15 (SCK), 14/10/16/12 (D0–D3), 13 (RST). Panel 450 × 600 at 550 nits,
-window offset 16. Touch is a separate Hynitron **CST226SE** on I²C (SDA 6 / SCL 7, IRQ 8,
-RST 17). **Vendor warns GPIO18 is assigned to the display TE pin** — though the vendor's own
-`product_pins.h` says TE is not wired; see the device record's conflict T4-C1.
diff --git a/components/raydium/rm690b0/artifacts/rm690b0-datasheet-v0.2-lilygo-mirror.pdf b/components/raydium/rm690b0/artifacts/rm690b0-datasheet-v0.2-lilygo-mirror.pdf
deleted file mode 100644
index d3dc36d..0000000
Binary files a/components/raydium/rm690b0/artifacts/rm690b0-datasheet-v0.2-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/raydium/rm69a10/README.md b/components/raydium/rm69a10/README.md
deleted file mode 100644
index 01f9177..0000000
--- a/components/raydium/rm69a10/README.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Raydium RM69A10 — AMOLED display driver IC
-
-- **Category:** MIPI-DSI AMOLED display driver / timing controller
-- **Manufacturer:** **Raydium Semiconductor Corporation** (瑞鼎科技). *Attribution note:* the `RM69xxx` prefix is Raydium's AMOLED driver family (RM67162, RM69090, RM690B0 are the widely documented siblings). **No public RM69A10 datasheet was located on 2026-09-04**; the manufacturer attribution is by family-prefix inference and is labelled as such.
-- **Research status:** driven entirely from **vendor BSP source**, not from a datasheet. Evidence class: primary source code, secondary product copy.
-- **Retrieved:** 2026-09-04
-
-## 1. What is actually known
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part marking / driver name | `RM69A10` | S1, S2 |
-| Interface | **MIPI DSI**, video mode; the BSP explicitly forces **burst mode** | S3 (`0029-drm-canaan-fix-video-mode-to-burst.patch`) |
-| DSI lanes | 2 (the BSP carries a "fix 2lan dsi phy with timeout" patch) | S3 (`0025-…`) |
-| Panel resolution as fitted | **RGB 568 × 1232**, 4.1-inch AMOLED | S1, S2 |
-| Colour formats driven | XRGB8888 added by patch; **RGB565 is the validated LVGL path** | S3, S4 |
-| Backlight | **DSI-command backlight**, not PWM — added by `0049-drm-panel-canaan-universal-add-rm69a10-dsi-backlight.patch` | S3 |
-| Linux driver | `panel-canaan-universal` (Canaan's generic DSI panel driver), *not* an upstream `panel-raydium-*` driver | S3 |
-
-## 2. Behaviour worth knowing before you write code
-
-**It is driven by a *generic* panel driver, not a Raydium-specific one.** Canaan's
-`panel-canaan-universal` is a table-driven DSI panel driver; the RM69A10 support is a set of
-init commands plus timing, added downstream. There is no upstream Linux support and no
-`compatible` string outside Canaan's tree.
-
-**Backlight is a DSI command.** There is no backlight PWM pin for the panel — brightness is a
-DSI write. A board-level PWM (`GPIO52`/PWM4 on the LilyGO board) exists but drives the
-*keyboard* backlight, not the panel. Conflating the two is the obvious mistake.
-
-**Reset must happen in `prepare`, not later.** `0027-panel-canaan-universal-enable-reset-in-prepare.patch`
-moves panel reset into the prepare stage; without it the panel does not come up reliably.
-
-**The boot logo and the kernel fight over the framebuffer.** Three separate patches exist to
-manage the handoff: `0038-reserve-rm69a10-uboot-logo-fb`, `0051-drm-canaan-preserve-rm69a10-boot-splash-handoff`
-and `0043-drm-canaan-defer-vo-config-load-to-vblank`. Expect flicker or a black frame at
-handoff if you rebuild without them.
-
-**High refresh needs an automatic PHY setting.** `0042-drm-canaan-rm69a10-use-auto-phy-high-refresh.patch`
-plus a diagnostic patch that logs the DSI clock PHY (`0041-…`) exist because getting the DSI
-PHY clock right on this panel was evidently not straightforward.
-
-## 3. Unknowns, stated as unknowns
-
-- No datasheet, no register map, no init sequence documentation from Raydium.
-- Panel module vendor and part number: unknown.
-- Whether the driver IC is Raydium at all rather than a compatible clone: **unverified**.
-- Touch is a separate IC ([GT9895](../../goodix/gt9895/README.md)); this record covers display only.
-
-## 4. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-The only display. 4.1″ AMOLED, RGB 568 × 1232, MIPI DSI from the K230's single DSI output.
-`GPIO22` = panel reset, `GPIO25` = panel enable — both used by the U-Boot logo path and by the
-Linux bring-up. The board's entire BSP defconfig is named after this panel
-(`k230_canmv_t_display_rm69a10_defconfig`) and so are its device trees
-(`canaan/k230-canmv-rm69a10`, `canaan/k230-canmv-rm69a10-hdmi`), which is a useful signal that
-the panel is the defining feature of the design.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | T-Display K230 product page | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230` | 2026-09-04 | "Drive Chip: RM69A10", RGB 568×1232, 4.1″ |
-| S2 | T-Display K230 Kit product page | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230-kit` | 2026-09-04 | Same, restated in the kit specification table |
-| S3 | `k230_bsp/overlay/buildroot-overlay/linux/*.patch` | LILYGO | primary | source | `https://github.com/Xinyuan-LilyGO/T-Display-K230/tree/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/overlay/buildroot-overlay/linux` | 2026-09-04 | Burst mode, 2-lane PHY, DSI backlight, reset-in-prepare, splash handoff |
-| S4 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | same repo | 2026-09-04 | GPIO22 reset / GPIO25 enable; "validated LVGL path uses RGB565" |
diff --git a/components/realtek/rtl8152b/README.md b/components/realtek/rtl8152b/README.md
deleted file mode 100644
index c29d66a..0000000
--- a/components/realtek/rtl8152b/README.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Realtek RTL8152B — USB 2.0 to 10/100 Ethernet controller
-
-- **Category:** USB 2.0 Fast Ethernet MAC + PHY in one package
-- **Manufacturer:** Realtek Semiconductor
-- **Research status:** identified from LilyGO's wiki specification. **Not corroborated by the BSP kernel fragment** — see §3, which is the whole reason this record exists.
-- **Retrieved:** 2026-09-04
-
-## 1. Why an *USB* Ethernet part is on a board with a "gigabit-capable" SoC
-
-It is not. **The Kendryte K230 has no Ethernet MAC at all.** A full-text search of both the K230
-full datasheet and the K230 brief datasheet for `ethernet`, `gmac` and `rmii` on 2026-09-04
-returned **zero matches**, and neither peripheral list contains Ethernet. Any RJ45 on a K230
-board is therefore behind a USB Ethernet controller, and LilyGO's wiki names that controller
-as **RTL8152B, 100 Mbps, IEEE 802.3u**.
-
-This is a good example of a specification that reads like a headline feature and is actually a
-constraint: the port is limited to 100 Mbit/s and it consumes one of the K230's two USB 2.0 OTG
-controllers' bandwidth.
-
-## 2. Known properties
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **RTL8152B** | S1 |
-| Rate | **100 Mbps**, IEEE 802.3u | S1 |
-| Host attach | USB 2.0 | inferred from part family; RTL8152B is a USB device-side controller |
-| Linux driver | `r8152` (`CONFIG_USB_RTL8152`) | see §3 |
-| Interface name on the board | `eth0` | S2 |
-
-## 3. The unresolved part — driver evidence does not match
-
-LilyGO's BSP kernel fragment (`linux.fragment`, S3) enables a long list of USB networking
-classes — `USB_USBNET`, `CDCETHER`, `CDC_NCM`, `CDC_MBIM`, `RNDIS_HOST`, `QMI_WWAN`,
-`CDC_SUBSET` — and **does not enable `CONFIG_USB_RTL8152`**. The launcher's Ethernet page
-manages `eth0` with `ifconfig`/`udhcpc` and does not care what drives it.
-
-Three readings, none yet eliminated:
-
-1. `CONFIG_USB_RTL8152` is already set in the base `k230` kernel defconfig, so the fragment has
-   nothing to add. **Most likely**, and testable by dumping the built `.config`.
-2. The fitted part is not an RTL8152B and the wiki is wrong — the CDC/RNDIS list would then be
-   the real driver path.
-3. The RJ45 is only ever used with an external USB dongle, and the wiki is describing an
-   accessory.
-
-**How to settle it:** on a running board, `readlink /sys/class/net/eth0/device/driver` and
-`lsusb`. Until then this record must not be read as confirming a fitted RTL8152B. Tracked as
-`GC-3` in [gaps-and-conflicts.md](../../../devices/lilygo/t-display-k230/gaps-and-conflicts.md).
-
-## 4. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-Claimed by LilyGO's wiki as the RJ45 Ethernet path on both the bare board and the Cased
-Version. The kit's shop listing instead names the Ethernet part **"RC01812"** with an RJ45
-connector — a third, unexplained designation that matches no Realtek part number and is most
-likely the **RJ45 jack/magnetics** part rather than the controller. Both are recorded; neither
-is confirmed.
-
-The RJ45's physical presence *is* confirmed by community observation: "the ethernet port is an
-odd choice. It just seems too big for this type of device" (S4, 2025-07-07).
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | T-Display K230 wiki page and Cased Version page | LILYGO | primary | official wiki | `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/` · `.../cased-version.html` | 2026-09-04 | "RTL8152B 100 Mbps Ethernet (IEEE 802.3u)" |
-| S2 | `k230_launcher/k230_phone_ui/src/ui_common.h` | LILYGO | primary | source | `https://github.com/Xinyuan-LilyGO/T-Display-K230` | 2026-09-04 | `NET_ETH_IFACE "eth0"` |
-| S3 | `k230_bsp/overlay/buildroot-overlay/linux/linux.fragment` | LILYGO | primary | source | same repo | 2026-09-04 | USB net classes enabled; **no** `USB_RTL8152` |
-| S4 | r/meshtastic comment by u/Nobodytoyou_ | Reddit | community | forum (firsthand observation of product photos) | `https://old.reddit.com/r/meshtastic/comments/1ltxxxo/` | 2026-09-04 | RJ45 physically present |
-| S5 | K230 full + brief datasheet, searched for `ethernet\|gmac\|rmii` | Canaan | primary | datasheet | `https://github.com/kendryte/k230_docs` @ `f8e3021` | 2026-09-04 | **Negative result:** no Ethernet MAC on the SoC |
diff --git a/components/realtek/rtl8189fs/README.md b/components/realtek/rtl8189fs/README.md
deleted file mode 100644
index 47ed056..0000000
--- a/components/realtek/rtl8189fs/README.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Realtek RTL8189FS — 802.11b/g/n 2.4 GHz SDIO Wi-Fi
-
-- **Category:** single-band 2.4 GHz Wi-Fi 4 (802.11 b/g/n) SoC, **SDIO** host interface
-- **Manufacturer:** Realtek Semiconductor
-- **Research status:** identified from the vendor BSP and the vendor product listing; no Realtek datasheet is publicly distributed for this part (Realtek does not publish 8189 datasheets openly).
-- **Retrieved:** 2026-09-04
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **RTL8189FS** (SDIO variant of the RTL8189F) | S1 |
-| Standard | 802.11 **b/g/n**, 2.4 GHz only | S2 |
-| Host interface | **SDIO** | S1 |
-| Bluetooth | **none** — the 8189 family is Wi-Fi only | S1 (see below) |
-| Buildroot package | `BR2_PACKAGE_RTL8189FS=y` | S3 |
-| Linux interface name | `wlan0` | S4 |
-
-## 2. The Bluetooth trap on this family
-
-The BSP also builds **RTL8723DS** (`BR2_PACKAGE_RTL8723DS=y`, `BR2_PACKAGE_RTL8723DS_BT=y`)
-and **RTL8733BS**, so an unwary reader concludes the board has combo Wi-Fi+BT. LilyGO's own
-pin map states the constraint plainly:
-
-> "RTL8189FS or RTL8723DS Wi-Fi. **RTL8723DS Bluetooth requires separate BT UART hardware
-> signals; SDIO covers Wi-Fi only.**" — S1
-
-And the board's Bluetooth is in fact **USB**: the kernel fragment enables `BT_HCIBTUSB` with
-`BT_HCIBTUSB_RTL`, and two downstream patches exist specifically for a **CSR8510/8891 USB
-dongle** (`0056-bluetooth-btusb-force-csr8510-8891-workaround.patch`,
-`0057-bluetooth-csr8510-8891-hci-init-experimental.patch`). Both are labelled *workaround* and
-*experimental* by their own filenames.
-
-Two Wi-Fi module options being compiled simultaneously is itself a finding: it means the
-fitted module is **not guaranteed identical across production runs**. Verify by
-`lsmod` / `dmesg` on the unit in hand rather than assuming.
-
-## 3. Practical notes
-
-- Out-of-tree driver. `RTL8189FS` is a Realtek vendor driver built by Buildroot, not a mainline
-  `rtlwifi`/`rtw88` driver. Kernel upgrades break it routinely; that is the normal experience
-  with this part.
-- 2.4 GHz only, 802.11n only. No 5 GHz, no Wi-Fi 5/6.
-- A community owner comparing to another LilyGO handheld said "If the WiFi is any better than
-  the t-deck plus I might end up with one" (S5) — an expectation, not a measurement. **No
-  throughput or sensitivity measurement for this board exists in any source found.**
-
-## 4. Used By
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-The board's only Wi-Fi. Attached over **SDIO** (the K230's second SD/MMC controller; the first
-carries the boot microSD on `GPIO54–59`). Enumerates as `wlan0`. LilyGO's kit specification
-sheet calls it "Wi-Fi Module 2.4G, Name: **RTL8189**, IEEE 802.11 b/g/n 2.4 GHz", which matches.
-
-⚠ LilyGO's **wiki** page for the same product instead claims an **ESP32-S3-R8 co-processor**
-provides "Wi-Fi + Bluetooth 5.0". Nothing in the BSP, the device trees, the Buildroot config or
-the launcher source references an ESP32 of any kind. Recorded as conflict `GC-2` in
-[gaps-and-conflicts.md](../../../devices/lilygo/t-display-k230/gaps-and-conflicts.md).
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` and `README.MD` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/tree/bb831ab358b66f5bd9a87ecd7c580fee4537492e` | 2026-09-04 | "RTL8189FS SDIO Wi-Fi"; SDIO covers Wi-Fi only |
-| S2 | T-Display K230 Kit product page | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230-kit` | 2026-09-04 | "RTL8189, IEEE 802.11 b/g/n 2.4GHz" |
-| S3 | `k230_canmv_t_display_rm69a10_defconfig` | LILYGO | primary | source | same repo | 2026-09-04 | `BR2_PACKAGE_RTL8189FS/RTL8723DS/RTL8723DS_BT` |
-| S4 | `k230_launcher/k230_phone_ui/src/ui_common.h` | LILYGO | primary | source | same repo | 2026-09-04 | `NET_WIFI_IFACE "wlan0"` |
-| S5 | r/LilyGO comment by u/meremale | Reddit | community | forum (opinion) | `https://old.reddit.com/r/LilyGO/comments/1vtcjuj/` | 2026-09-04 | Expectation about Wi-Fi quality vs T-Deck Plus |
diff --git a/components/rohm/rb162vam-20tr/README.md b/components/rohm/rb162vam-20tr/README.md
deleted file mode 100644
index cc8b068..0000000
--- a/components/rohm/rb162vam-20tr/README.md
+++ /dev/null
@@ -1,245 +0,0 @@
-# ROHM RB162VAM-20TR
-
-> **Schottky barrier diode**, 20 V / 1 A, **ultra-low V<sub>F</sub> = 0.36 V typ @ 1 A**, in ROHM's TUMD2M (SOD-323HE) package, marking **`N`**.
-> Research snapshot **2026-09-01**. Fitted as **`D2` on sheet 2** of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — the **rectifier of the e-paper frontlight boost converter**.
-> ⚠ **ROHM lists this part as *Not Recommended for New Designs*.** **No hardware was available.**
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | ROHM `RB162VAM-20` data sheet, **Rev.001, 2017-05-16**, © 2016 ROHM; local copy `artifacts/rb162vam-20tr-rohm-octopart-mirror.pdf` | `not-tested` |
-| **[WEB]** | ROHM product page for `RB162VAM-20TR`, retrieved 2026-09-01 | `not-tested` |
-| **[SCH-V]** | Read off sheet 2 rendered to PNG at 200 dpi | `executed-success` for the reading |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and ratings **[DS]**
-
-| Property | Value |
-|---|---|
-| Part | **`RB162VAM-20`**; ordering code **`RB162VAM-20TR`** (`TR` = taping) |
-| Manufacturer | **ROHM Co., Ltd.** |
-| Function | Schottky barrier diode, general rectification |
-| Structure | Silicon epitaxial planar |
-| Package | **TUMD2M**, i.e. **SOD-323HE** **[WEB]** |
-| **Marking** | **`N`** |
-| **V<sub>R</sub>** | **20 V** |
-| V<sub>RM</sub> (repetitive peak, duty ≤ 0.5) | **25 V** |
-| **I<sub>O</sub>** | **1 A** (glass-epoxy mounted, 60 Hz half-sine, resistive, T<sub>c</sub> ≤ 85 °C) |
-| I<sub>FSM</sub> | 5 A (100 µs, non-repetitive, single cycle, 25 °C) |
-| **V<sub>F</sub>** | **0.36 V typ, 0.40 V max @ I<sub>F</sub> = 1 A** |
-| **I<sub>R</sub>** | **0.3 mA typ, 1.2 mA max @ V<sub>R</sub> = 20 V** |
-| T<sub>j</sub> | 125 °C |
-| T<sub>stg</sub> | −40 to +125 °C |
-| Packaging | embossed tape, 180 mm reel, 8 mm width, **3000 pcs** |
-| Features (vendor) | *"High reliability; small mold type; **super low V<sub>F</sub>**"* |
-
-### 1.1 ⚠ Not Recommended for New Designs
-
-ROHM's product page states: *"**Not Recommended for New Designs.** This product
-cannot be used for new designs (Not recommended for design diversion)."*
-**[WEB]**
-
-This does not mean the PaperMono is at risk — M5Stack is presumably buying to an
-existing agreement, and NRND parts remain available for years. It does mean:
-
-- **Do not copy this circuit into a new design with this part.** Pick a current
-  ROHM equivalent (`RB160VAM-30`, `RB168VAM-40` and relatives) or another vendor.
-- Long-term repairability of the PaperMono depends on a part ROHM has already
-  begun retiring.
-
-### 1.2 ⚠ The reverse leakage is large, and it is a standby-current term
-
-**I<sub>R</sub> = 0.3 mA typical, 1.2 mA maximum at 20 V.** That is enormous for a
-signal diode and entirely normal for an ultra-low-V<sub>F</sub> Schottky — the two
-trade against each other directly, and ROHM sells this part on the V<sub>F</sub>.
-
-On a battery device the number deserves a second look. **0.3 mA is roughly two
-thirds of a milliamp-hour per hour**; on a 1150 mAh cell, a continuously reverse-
-biased `D2` alone would be about **160 days** of standby. That is tolerable, but
-it is the same order as several other quiescent terms on this board, and it is
-strongly temperature-dependent (Schottky leakage roughly doubles every 10 °C).
-
-**It only applies while the frontlight rail is up and the converter is idle.**
-When `BL_15V_L3B` is off there is no reverse bias to leak across. **[INF]** —
-not measured, and the actual reverse voltage in the idle state was not
-established.
-
----
-
-## 2. Used By
-
-### `devices/m5stack/papermono` — `D2`, sheet 2
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md).
-**One instance.**
-
-**On the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md):**
-`inferred` **yes** — both SKUs have the same e-paper panel and the same
-frontlight; the Lite differs only in dropping NFC and LoRa. Not read from the
-Lite's own schematic.
-
----
-
-## 3. Circuit role — the frontlight boost rectifier **[SCH-V]**
-
-```
-EPD_3V3_L3 ──[ L3  10 µH ]──┬────▶|──── D2 ────┬── R27 0 Ω ──┬── BL_15V_L3B
-   FTC201610S100MBCA        │   RB162VAM-20TR  │             │
-                            │                  │        C26 NC/50V
-                     U11 pin 4 SW           C24 33 pF/50 V   (not fitted)
-                     AW9967DNR              C25 1 µF/50 V
-                     (boost WLED driver)
-```
-
-| `D2` terminal | Net |
-|---|---|
-| **anode** | the switch node — `L3` and the [AW9967DNR](../../awinic/aw9967/README.md)'s `SW` pin |
-| **cathode** | the boost output, through `R27` = 0 Ω to **`BL_15V_L3B`** |
-
-This is a textbook asynchronous boost: `U11` pulls `SW` low, current ramps in
-`L3`, `U11` releases, and the inductor's flyback pushes charge through `D2` into
-`C25`. The frontlight LED string hangs off `BL_15V_L3B` and its current is set by
-`R29` = 18 Ω on the AW9967's `BL_FB` pin.
-
-### 3.1 ⚠ 20 V on a rail named 15 V — the margin is thin, and possibly thinner
-
-The net is called **`BL_15V_L3B`**, and `D2` is a **20 V** part. In a boost, the
-diode's reverse voltage while the switch is on is approximately the *output*
-voltage, so nominally `D2` sees about **15 V against a 20 V rating — 75 % of
-V<sub>R</sub>**, before any switching-node ringing.
-
-That is tight but not wrong. What makes it worth flagging is the surrounding
-component choice: **`C24`, `C25` and `C26` are all rated 50 V**, and the AW9967
-is a WLED boost whose output rises to whatever the LED string's forward voltage
-demands. A 50 V output capacitor is not what a designer fits for a hard 15 V
-rail; it is what they fit when the node can go higher. If the string's total
-V<sub>F</sub> ever exceeds ~20 V — more LEDs, a colder panel, a different
-frontlight supplier — **`D2` is the part that fails first.** **[INF]**
-
-Countervailing evidence: the net *name* says 15 V, the AW9967's own output range
-was not checked against this for this record, and the design presumably passed
-qualification. **This is a flag, not a defect claim.** It is recorded because a
-reader copying this circuit should size the rectifier from the LED string, not
-from the net name.
-
-### 3.2 Why an ultra-low-V<sub>F</sub> part here
-
-At a boost output of ~15 V from a 3.3 V input, duty is high and the diode
-conducts for the short remainder of each cycle at a comparatively large peak
-current. **V<sub>F</sub> × I is the dominant loss in an asynchronous boost's
-rectifier**, and 0.36 V versus a typical 0.55 V Schottky is a meaningful
-efficiency difference on a battery-powered backlight that may be on for hours.
-The design is trading the high reverse leakage of §1.2 for conduction efficiency.
-**[INF]**
-
----
-
-## 4. Substitution
-
-Required: **Schottky**, V<sub>R</sub> ≥ 20 V (**consider 30–40 V** given §3.1),
-I<sub>O</sub> ≥ 1 A, SOD-323HE / TUMD2M footprint, low V<sub>F</sub>.
-
-| Alternative | Note |
-|---|---|
-| ROHM **`RB160VAM-30`**, **`RB168VAM-40`** | Same family, 30 V / 40 V — **the sensible replacement given §1.1 and §3.1** |
-| ROHM **`RB162VA-20`** | The non-`M` variant in TUMD2 — **different package** |
-| **`1N5819WS`** ([used elsewhere on this board](../../generic/1n5819ws/README.md)) | 40 V / 1 A, SOD-323 — more voltage margin, **higher V<sub>F</sub> (0.6 V @ 1 A)**, hence lower efficiency |
-| Generic SOD-323 Schottky | ⚠ Check both V<sub>F</sub> *and* I<sub>R</sub>; the two trade off (§1.2) |
-
-Note that the board already stocks `1N5819WS` for the e-paper bias converter, so
-consolidating on it would remove a BOM line at a small efficiency cost. That
-M5Stack did **not** do so is itself evidence that the frontlight's efficiency was
-considered worth a separate part number. **[INF]**
-
----
-
-## 5. Integration pitfalls
-
-1. **NRND** (§1.1) — do not design it in fresh.
-2. **20 V on a rail whose capacitors are rated 50 V** (§3.1). Size a replacement
-   from the LED string's forward voltage.
-3. **0.3–1.2 mA reverse leakage** (§1.2), rising fast with temperature.
-4. **T<sub>j</sub> is only 125 °C**, low for a rectifier, and the datasheet warns:
-   *"To avoid occurrence of thermal runaway, actual board is to be designed to
-   fulfil dPd/dTj < 1/Rth(j-a)."* Schottky thermal runaway is a real failure mode
-   at high reverse bias and high temperature — the two conditions §1.2 and §3.1
-   between them describe.
-5. **`R27` = 0 Ω** sits between the rectifier and the rail. It is a link, and a
-   convenient place to break the frontlight rail for measurement.
-6. **`C26` is `NC`** — the output capacitance is `C25` = 1 µF/50 V alone, plus a
-   33 pF snubber. That is little bulk for a boost; a replacement diode with more
-   junction capacitance will change the ringing behaviour noticeably. **[INF]**
-
----
-
-## 6. Open questions
-
-- The frontlight LED string's forward voltage, which determines the actual
-  reverse stress on `D2` (§3.1). Not published; the frontlight is part of the
-  panel assembly.
-- The AW9967's switching frequency and output-voltage limit as configured —
-  partly covered in the [AW9967 record](../../awinic/aw9967/README.md), not
-  cross-checked against `D2` here.
-- Whether `D2` is reverse-biased when the frontlight is off (§1.2).
-- No measurement of anything.
-
----
-
-## Manufacturer
-
-**ROHM Co., Ltd.** No vendor sourcing guide exists in this repository yet.
-
-**⚠ Retrieval finding — ROHM's own CDN would not serve this document.** Every
-`fscdn.rohm.com` path tried returned a **404 with a 321-byte HTML body**,
-including the two forms ROHM uses for current and NRND parts:
-
-| URL | Result |
-|---|---|
-| `fscdn.rohm.com/en/products/databook/datasheet/discrete/diode/schottky_barrier/rb162vam-20-e.pdf` | **404** |
-| `fscdn.rohm.com/en/products/databook/datasheet-nrnd/…/rb162vam-20-e.pdf` | **404** |
-| `fscdn.rohm.com/…/rb162vam-20.pdf` (no `-e`) | **404** |
-| `www.rohm.com/datasheet/RB162VAM-20/rb162vam-20-e` | **403** |
-| `datasheets.ibselectronics.com/RB162VAM-20TR-Rohm-datasheet-142143350.pdf` | **403** to all five user-agents |
-| **`datasheet.octopart.com/RB162VAM-20TR-Rohm-datasheet-142143350.pdf`** | **200, `%PDF` ✓**, 2 202 076 B |
-
-**The document is on Octopart's mirror under the same numeric ID as the IBS
-Electronics copy that 403s** — `142143350`. That ID appears to be a shared
-distributor-datasheet identifier, so **when `datasheets.ibselectronics.com/<name>-<id>.pdf`
-is blocked, try `datasheet.octopart.com/<name>-<id>.pdf`**. That is the reusable
-finding here and it belongs in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md).
-
-Plausible reason for the ROHM 404s: NRND parts are removed from the public
-datasheet CDN while the product page survives. If so, **ROHM's own site is not a
-reliable source for any NRND part**, and a mirror is mandatory.
-
-## Related pages
-
-- [Awinic AW9967DNR](../../awinic/aw9967/README.md) — `U11`, the boost controller `D2` rectifies for
-- [1N5819WS](../../generic/1n5819ws/README.md) — the board's other Schottky, 40 V, in the e-paper bias converter
-- [PaperMono frontlight feature guide](../../../devices/m5stack/papermono/features/frontlight.md)
-- [PaperMono power architecture](../../../devices/m5stack/papermono/power-architecture.md) · [bill of materials](../../../devices/m5stack/papermono/bill-of-materials.md)
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| D1 | `RB162VAM-20` Schottky Barrier Diode data sheet | ROHM (via Octopart mirror) | primary, via mirror | <https://datasheet.octopart.com/RB162VAM-20TR-Rohm-datasheet-142143350.pdf> | 2026-09-01 | **Rev.001, 2017-05-16**, © 2016 ROHM, 8 pp | all of §1: V<sub>R</sub>, V<sub>RM</sub>, I<sub>O</sub>, I<sub>FSM</sub>, V<sub>F</sub>, **I<sub>R</sub>**, T<sub>j</sub>, marking `N`, taping, the thermal-runaway warning | `artifacts/rb162vam-20tr-rohm-octopart-mirror.pdf` |
-| W1 | `RB162VAM-20TR` product page | ROHM | primary | <https://www.rohm.com/products/diodes/schottky-barrier-diodes/ultra-low-vf/rb162vam-20-product> | 2026-09-01 | — | **"Not Recommended for New Designs"**; package **SOD-323HE**; the *ultra-low V<sub>F</sub>* category placement | — |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | `D2` = `RB162VAM-20TR`; the §3 topology; `L3` = 10 µH, `R27` = 0 Ω, `C24`/`C25`/`C26` values and the `NC` | `../../../devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/rb162vam-20tr-rohm-octopart-mirror.pdf` | 2 202 076 | `e769d2b55951abd54ba6fc9832086c73860cde41fa7b09408daa50ea40a4b33d` | 8 |
-
-**Method note.** D1 validated as `%PDF` (`executed-success`) with an intact text
-layer; its first page was read directly and is the source of every number in §1.
-Six URLs across four hosts were tried before one served the document — see
-[Manufacturer](#manufacturer). §3 was read from a 200 dpi render of sheet 2.
diff --git a/components/rohm/rb162vam-20tr/artifacts/rb162vam-20tr-rohm-octopart-mirror.pdf b/components/rohm/rb162vam-20tr/artifacts/rb162vam-20tr-rohm-octopart-mirror.pdf
deleted file mode 100644
index 214e468..0000000
Binary files a/components/rohm/rb162vam-20tr/artifacts/rb162vam-20tr-rohm-octopart-mirror.pdf and /dev/null differ
diff --git a/components/seiko-epson/rx8130ce/README.md b/components/seiko-epson/rx8130ce/README.md
deleted file mode 100644
index c079b68..0000000
--- a/components/seiko-epson/rx8130ce/README.md
+++ /dev/null
@@ -1,600 +0,0 @@
-# Seiko Epson RX8130CE
-
-- **Category:** I²C **real-time clock / calendar module** with a built-in, frequency-adjusted 32.768 kHz crystal, wakeup timer, alarm, time-update interrupt, FOUT clock output, reset output, 4 bytes of user RAM, a digital offset trim, and an **integrated backup-supply switchover and battery-charge controller**
-- **I²C address:** **`0x32`** (7-bit, fixed; write byte `0x64`, read byte `0x65`). No address-select pin
-- **Package:** 10-terminal ceramic module; Epson product number **`X1B000311000100`**
-- **Research status:** the **full Epson application manual is retained in two revisions** — the M5Stack mirror (`ETM50E-09`, 70 pp) and Epson's current `ETM50E-10`, both read end to end and diffed. The PaperMono schematic symbol was parsed pin-by-pin, and M5Unified's `RX8130_Class` driver was audited against the manual. No hardware was in the loop.
-- **Retrieved:** 2026-09-01
-
-The real-time clock of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) and, identically, of the [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) (C153-LITE). The board-specific fact that matters is that its **interrupt output does not reach the ESP32-S3 at all** — it goes to the [M5PM1](../../m5stack/m5pm1/README.md) power manager, which is what lets an alarm wake a board whose application processor is unpowered.
-
----
-
-## ⚠ The document filed here as "Chinese" is in English
-
-This needs stating before anything else, because the repository's own source table, the device record and this record's own filename all say otherwise.
-
-The artifact `artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf`, mirrored by M5Stack as `RX8130CE_cn-Register-Datasheet.pdf`, **is the English-language Epson application manual `ETM50E-09`**, cover to cover. `executed-success` — the full 70-page text layer was extracted and read.
-
-The cause was traced to Epson, not to M5Stack. **Epson's own download server serves the English manual under a `_cn` filename:**
-
-| Epson URL | Bytes | SHA-256 | Language |
-|---|---:|---|---|
-| `https://download.epsondevice.com/td/pdf/app/RX8130CE_en.pdf` | 2 008 845 | `db027a5f…` | **English**, `ETM50E-10` |
-| `https://download.epsondevice.com/td/pdf/app/RX8130CE_cn.pdf` | 2 008 853 | `0ff562f2…` | **English**, `ETM50E-10` — same document, 8 bytes of metadata apart |
-| `https://download.epsondevice.com/td/pdf/app/RX8130CE_ja.pdf` | 2 986 434 | `32913ca0…` | **Japanese**, `ETM50J-10`, 64 pp |
-
-So at Epson the `_cn` suffix means **"served on the China site"**, not "Chinese language". M5Stack mirrored that file and kept the suffix. All three verified `HTTP 200` on 2026-09-01.
-
-**Therefore, on the repository's multi-language policy:**
-
-- The copy held **is** the English edition. There is no separate English equivalent to go and get, and no translation-equivalence question to answer, because no Chinese-language edition of this manual was found to exist anywhere — not at Epson, not at M5Stack.
-- A **Japanese** edition (`ETM50J-10`) does exist and is a genuinely independent document — 64 pages against the English 70, and the English text still carries an untranslated Japanese figure caption (`初回周期誤差`, "first-cycle error", in Figure 20 **[DS-09]** p. 28), which shows the English is a translation of the Japanese original. It is recorded **reference-only** with size, hash and URL in [§12](#12-local-artifacts) rather than retained, since the English is authoritative for this repository's readers and the file is freely re-fetchable from a stable vendor URL.
-- **Epson's current revision was retrieved and is now held beside the mirror** (§12). It is **`ETM50E-10`, 2026-01-30** — the M5Stack mirror is **one revision behind**, and the difference runs the *unexpected* way; see [§11-C1](#11-caveats-errata-and-a-driver-audit).
-
-The filename of the mirror is left unchanged, because renaming it would break the hash-and-path chain recorded in [`devices/m5stack/papermono/sources.md`](../../../devices/m5stack/papermono/sources.md) S22. The mislabelling is documented instead.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[DS-09]** | Stated in `artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf` (`ETM50E-09`), with section/table reference | `not-tested` — manufacturer specification reproduced; nothing measured |
-| **[DS-10]** | Stated in `artifacts/rx8130ce-application-manual-etm50e-10-en-epson.pdf` (`ETM50E-10`, Epson's current) | `not-tested` |
-| **[SCH]** | Read out of `PaperMono_SCH_V0.6.2_20260522.pdf`, **sheet 4**, designator `U16` | `executed-success` for the extraction (all 10 pads enumerated from the text-position layer); `not-tested` electrically |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[FW]** | String recovered from the shipped factory firmware binary | `executed-success` for the extraction |
-| **[INF]** | Inference | `inferred` |
-
-Unless marked **[DS-10]**, register and electrical values are quoted from `ETM50E-09`, the revision the board's software was written against; the two revisions agree on every value in this record (§11-C1).
-
-**Text-layer validation.** Both PDFs were checked against their own running headers (`RX8130CE`, `ETM50E-09` / `ETM50E-10`) and page footers before transcription; the two were then normalised and diffed against each other, which is a stronger check than either alone. No glyph subsetting or code-point offset was observed. Residual Japanese in figure captions is a property of the source document, not the extraction.
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **Seiko Epson Corporation** | **[DS-09]** cover |
-| Part | **RX8130CE**, "Build-in backup battery charge control function / SERIAL-INTERFACE REAL TIME CLOCK MODULE" | **[DS-09]** §1 |
-| Epson product number | **`X1B000311000100`** | **[DS-09]** cover |
-| Document | **Application manual `ETM50E-09`**, 70 pp, revision dated **2025-06-30** | **[DS-09]** cover, revision history |
-| Epson's current document | **`ETM50E-10`**, 70 pp, revision dated **2026-01-30** | **[DS-10]** |
-| I²C address | **`0x32`** — slave address bits `0110010` + R/W | **[DS-09]** §19.4; **[SRC]** `hal_board.cpp:17` (`RX8130_ADDR = 0x32`) |
-| I²C speed | up to **400 kHz** | **[DS-09]** §1; **[SRC]** `hal_board.cpp:19` (`RX8130_I2C_FREQ_HZ = 400000`) |
-| Reference | **built-in, frequency-adjusted 32.768 kHz crystal** — no external crystal, no load capacitors | **[DS-09]** §1 |
-| Operating voltage | **1.6 – 5.5 V** (`VDD`); **1.1 – 5.5 V** timekeeping | **[DS-09]** §1, Table 5 |
-| Interface supply `VIO` | **1.6 – 5.5 V**, independent of `VDD` | **[DS-09]** Table 5 |
-| Reference designator on PaperMono | **`U16`, sheet 4** | **[SCH]** |
-| ⚠ Marking verified? | **No.** No teardown photograph of `U16` was inspected; identity rests on the schematic's value string | **[INF]** |
-
-### 1.1 Accuracy
-
-**[DS-09]** Table 4, at V<sub>DD</sub> = 3.0 V:
-
-| Parameter | Value |
-|---|---|
-| Output frequency | 32.768 kHz |
-| **Frequency stability at +25 °C** | **±5 × 10⁻⁶** (Epson prints "5 ± 23 × 10⁻⁶" for the ±23 ppm bin — the datasheet's own note reads "monthly error is equal to 60 s Max., excluding offset") |
-| Frequency vs. voltage, 1.1–5.5 V | −2 to +2 × 10⁻⁶ per volt |
-| **Frequency vs. temperature**, −20…+70 °C | **−120 to +10 × 10⁻⁶** |
-| Ageing, first year at +25 °C | ±5 × 10⁻⁶ / year |
-| Oscillation start time `t_str` | 0.19 s typ., **1.0 s max** |
-
-The temperature coefficient is the number that dominates: **−120 ppm at the edges of the range is roughly −5 minutes per month**, and this is an ordinary (not temperature-compensated) tuning-fork crystal, so the curve is parabolic about ~+25 °C. Anyone expecting minute-per-year accuracy from this part in a pocket device will be disappointed. The digital offset function (§6) can trim a *static* error but not a thermal one.
-
----
-
-## 2. Pin table
-
-**[DS-09]** §3.1, Table 1. The PaperMono column is **[SCH]** sheet 4 `U16` — all ten pads enumerated.
-
-| Pin | Name | I/O | Datasheet function | PaperMono net **[SCH]** |
-|---:|---|---|---|---|
-| 1 | `VIO` | P | **Interface supply.** "Connect the same power supply as the MCU" | **`3V3_L0`** — see §2.1 |
-| 2 | `SCL` | I | Serial clock input | **`G48_SYS_SCL`** → ESP32-S3 **GPIO48** |
-| 3 | `SDA` | I/O | Data input and output | **`G47_SYS_SDA`** → ESP32-S3 **GPIO47** |
-| 4 | `FOUT` | O | Frequency output, CMOS. 32.768 kHz / 1024 Hz / 1 Hz, or off | *(no net label — unused)* |
-| 5 | `/RST` | O | **N-ch open drain.** Asserted low when `VDD` falls below `VDET1`; released 60 ms after `VDD` rises. **Operates in backup mode too** | via **`R47` 22 Ω / 1 %** |
-| 6 | `/IRQ` | O | **N-ch open drain.** Alarm and timer interrupt output. **Can output in backup mode** | **`PYG0_RTC_INT`** → **M5PM1 pin 3 (`IO0`)** |
-| 7 | `GND` | P | Ground | `GND` |
-| 8 | `VDD` | P | Supply for internal logic | main RTC supply — see §2.1 |
-| 9 | `VOUT` | P | **Internal voltage output.** "Connect smoothing capacitor of 1.0 µF" | local, with `R47` |
-| 10 | `VBAT` | P | Backup supply pin — EDLC, secondary or primary battery | see §2.1 |
-
-Local passives on sheet 4: **`C60`, `C61`, `C62`, all 1 µF / 25 V**, and **`R49`** on the `PYG0_RTC_INT` net, which is the mandatory pull-up for the open-drain `/IRQ` **[SCH]**.
-
-Datasheet notes worth keeping **[DS-09]** §3.2:
-
-- Input pins accept up to **5.5 V regardless of the `VIO` voltage**.
-- The open-drain pins may be **pulled up to 5.5 V regardless of `VIO`**.
-- **Leave `FOUT`, `/RST` and `/IRQ` open when unused — do not tie them to GND or `VDD`.**
-- A bypass capacitor of at least 0.1 µF is required on every supply pin.
-
-### 2.1 ⚠ Which rail is it on? Two primary sources point different ways
-
-M5Stack's published power-tree table places the RTC on **`3V3_L1`**, the rail enabled by the M5PM1's `LDO_3V3_EN` **[DOC]**, and the device record's [`power-architecture.md`](../../../devices/m5stack/papermono/power-architecture.md) reproduces that: *"L1 Standby — `3V3_L1` — RTC and IMU powered"*.
-
-The schematic's text layer puts **`3V3_L0`** — the always-on rail — on the `VIO` (pin 1) row, and `3V3_L0` also appears beside `R49` on the `PYG0_RTC_INT` net **[SCH]**. Separately, the [M5PM1 record](../../m5stack/m5pm1/README.md) describes the M5PM1 as sitting on `L0` *"straight off the battery, alongside the RTC"*.
-
-**These are not necessarily in conflict, and the part is designed for exactly this.** The RX8130CE has *two* independent supplies — `VDD` for the internal logic and `VIO` for the bus interface — and the manual devotes §4.1 to a "separated power source" configuration in which they differ. A design that puts `VIO` and the `/IRQ` pull-up on the always-on `L0` rail while running `VDD` from switched `L1` is coherent: it keeps the open-drain interrupt able to drive the M5PM1 (which lives on `L0`) while `L1` is down.
-
-**What is not established** is the `VDD` (pin 8) and `VBAT` (pin 10) nets. Neither carried a recoverable net label adjacent to its pad, and the extraction tool recovers *text adjacency, not connectivity* — its own documentation says so. **No net is asserted for `VDD` or `VBAT` here.** Reading the rendered sheet graphically would settle it in minutes, and it is the first thing to check before relying on any statement about this board's behaviour at `L0`.
-
-The consequence, if the vendor table is right about `VDD`: **in state L0 the RTC's logic supply is off and the time is lost**, because there is no coin cell or supercapacitor in evidence — only three 1 µF ceramics, one of which is the manual's required `VOUT` smoothing cap. A 1 µF backup at ~300 nA holds up for well under a second. See [`features/rtc.md` §7](../../../devices/m5stack/papermono/features/rtc.md).
-
----
-
-## 3. Register map
-
-**[DS-09]** Table 12 (§13.2.1). **The clock and calendar registers start at `10h`, not `00h`.**
-
-| Addr | Function | b7 | b6 | b5 | b4 | b3 | b2 | b1 | b0 |
-|---|---|---|---|---|---|---|---|---|---|
-| `10` | `SEC` | 0 | 40 | 20 | 10 | 8 | 4 | 2 | 1 |
-| `11` | `MIN` | 0 | 40 | 20 | 10 | 8 | 4 | 2 | 1 |
-| `12` | `HOUR` | 0 | 0 | 20 | 10 | 8 | 4 | 2 | 1 |
-| `13` | `WEEK` | 0 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
-| `14` | `DAY` | 0 | 0 | 20 | 10 | 8 | 4 | 2 | 1 |
-| `15` | `MONTH` | 0 | 0 | 0 | 10 | 8 | 4 | 2 | 1 |
-| `16` | `YEAR` | 80 | 40 | 20 | 10 | 8 | 4 | 2 | 1 |
-| `17` | **`MIN Alarm`** | `AE` | 40 | 20 | 10 | 8 | 4 | 2 | 1 |
-| `18` | **`HOUR Alarm`** | `AE` | • | 20 | 10 | 8 | 4 | 2 | 1 |
-| `19` | **`WEEK`/`DAY Alarm`** | `AE` | 6 / • | 5 / 20 | 4 / 10 | 3 / 8 | 2 / 4 | 1 / 2 | 0 / 1 |
-| `1A` | `Timer Counter 0` | 128 | 64 | 32 | 16 | 8 | 4 | 2 | 1 |
-| `1B` | `Timer Counter 1` | 32768 | 16384 | 8192 | 4096 | 2048 | 1024 | 512 | 256 |
-| `1C` | **`Extension Register`** | `FSEL1` | `FSEL0` | `USEL` | `TE` | `WADA` | `TSEL2` | `TSEL1` | `TSEL0` |
-| `1D` | **`Flag Register`** | **`VBLF`** | 0 | `UF` | `TF` | `AF` | `RSF` | **`VLF`** | `VBFF` |
-| `1E` | **`Control Register 0`** | `TEST` | `STOP` | `UIE` | `TIE` | `AIE` | `TSTP` | `TBKON` | `TBKE` |
-| `1F` | **`Control Register 1`** | `SMPTSEL1` | `SMPTSEL0` | **`CHGEN`** | **`INIEN`** | 0 | `RSVSEL` | `BFVSEL1` | `BFVSEL0` |
-| `20`–`23` | **User RAM** | — 32 bits, 4 bytes, free for any data — | | | | | | | |
-| `30` | `Digital offset` | `DTE` | `L7` | `L6` | `L5` | `L4` | `L3` | `L2` | `L1` |
-| `31` | `Extension Register 1` | – | – | – | – | – | – | – | `VBLFE` |
-
-Reset values **[DS-09]** Table 13 — identical after a **software** reset:
-
-| Addr | Value at power-on reset |
-|---|---|
-| `10`–`16`, `17`–`19`, `1A`, `1B`, `20`–`23` | **undefined** (`X`; normally retains the pre-reset content) |
-| `1C` | `0000 0100` → `TSEL2 = 1` |
-| `1D` | **`0000 0110`** → **`RSF = 1`, `VLF = 1`** |
-| `1E`, `1F`, `30`, `31` | `0000 0000` |
-
-Rules that matter **[DS-09]** Table 12 footnotes:
-
-- Bits printed **`0`** are write-invalid and always read 0. Bits printed **`•`** are free RAM bits. Bits printed **`-`** are TEST bits: **initialise them to 0 and keep them 0.**
-- **The `TEST` bit (`1E` bit 7) is a manufacturer test bit. Always write 0.**
-- "RTC has different registers not mentioned above table which are programmed by the manufacturer. Please make sure to only access above mentioned user registers." — the software-reset procedure (§7.2) is the sanctioned exception, and it writes to `50h`, `53h`, `66h` and `6Bh`.
-- Unused-function registers double as RAM: the alarm registers `17h`–`19h` when `AIE = 0`, the timer counters `1Ah`/`1Bh` when `TE = TIE = 0`.
-
-### 3.1 ⚠ Auto-increment wraps inside 16-byte blocks
-
-**[DS-09]** §19.6:
-
-```
-10h -> 1Fh -> 10h
-20h -> 2Fh -> 20h
-30h -> 3Fh -> 30h
-```
-
-A burst that runs off the end of a block **wraps to the start of the same block**; it does not continue into the next. A 7-byte read from `10h` (`SEC`…`YEAR`) is safe; a burst starting at `1Ch` will wrap onto `10h` after four bytes and quietly overwrite the seconds register if you were writing. There is no cross-block burst.
-
-### 3.2 ⚠ The manual mis-states where the clock registers live
-
-§13.3.1 is headed *"Clock and calendar registers (0h ~ 16h)"*. There are **no user registers below `10h`** — Table 12 places `SEC` at `10h` and the address-circulation table starts at `10h`. The heading is an error, present identically in `ETM50E-09` and `ETM50E-10`. Take Table 12.
-
-This matters because most I²C RTCs *do* start their clock registers at `00h`; a driver ported from one will read zeros.
-
----
-
-## 4. Interrupt sources
-
-Three independent interrupt sources share the single open-drain `/IRQ` pin. Each has a flag bit in `1D` and an enable bit in `1E`. **All flags are write-0-to-clear; writing 1 is ignored.** **[DS-09]** §14.2–§14.4.
-
-| Source | Flag | Enable | Auto-releases `/IRQ`? |
-|---|---|---|---|
-| **Wakeup timer** | `TF` (`1D`.4) | `TIE` (`1E`.4) | **Yes**, after `tRTN2` |
-| **Alarm** | `AF` (`1D`.3) | `AIE` (`1E`.3) | **No — latched until cleared** |
-| **Time update** | `UF` (`1D`.5) | `UIE` (`1E`.5) | **Yes**, `tRTN1` ≈ 7.57 ms (max 15.63 ms) |
-
-The asymmetry in the third column is the practical point: **the alarm holds `/IRQ` low forever until you clear `AF`**, whereas the timer and update interrupts release themselves. **[DS-09]** §14.3: *"/IRQ='L' output when occurs alarm interruption event is not cancelled automatically unless giving intentional cancellation."*
-
-Note also that `AIE`/`TIE`/`UIE` only gate the *pin*, not the flag. Clearing `AIE` releases `/IRQ` but leaves `AF` set; the flag must be cleared separately.
-
-### 4.1 Wakeup timer
-
-A 16-bit down-counter (`1A`/`1B`, preset 1…65535) clocked from one of five sources selected by `TSEL2:0` (`1C`.2:0) **[DS-09]** Table 16:
-
-| `TSEL2:0` | Source clock | Period per count | `/IRQ` auto-release `tRTN2` (min) |
-|---|---|---|---|
-| `000` | 4096 Hz | **244.14 µs** | **122 µs** |
-| `001` | 64 Hz | 15.625 ms | 7.57 ms |
-| `010` | 1 Hz | 1 s | 7.57 ms |
-| `011` | 1/60 Hz | 1 min | 7.57 ms |
-| `100` | 1/3600 Hz | 1 h | 7.57 ms |
-
-Full range **244.14 µs to 65 535 hours** (≈ 7.5 years). `TE` (`1C`.4) starts and stops it; while `TE = 0` the counter registers read back the *preset*, while `TE = 1` they read the live count.
-
-Two traps, both stated by Epson:
-
-- **The first countdown is short.** With 4096/64/1 Hz sources the error is up to one source-clock period; with 1/60 and 1/3600 Hz it is up to **1 second** **[DS-09]** Figure 20.
-- **Reading the live count is not atomic** — "when access to timer counter data, counting value is not held". Epson's own advice: read twice and accept the value only when two reads agree **[DS-09]** §14.2.1.
-
-`TSTP`, `TBKON` and `TBKE` (`1E`.2:0) control the *Long-Timer* variant, which accumulates run time separately on the main and backup supplies and sums them — a usage counter rather than a periodic timer **[DS-09]** §13.1(3).
-
-### 4.2 Alarm
-
-Minute, hour, and either day-of-month or day-of-week, selected by `WADA` (`1C`.3): `0` = WEEK, `1` = DAY **[DS-09]** §14.3.
-
-**There is no seconds field.** The alarm resolution is one minute, and `AF`/`/IRQ` may lag the match by up to **1.46 ms**.
-
-**`AE` is low-active, and this is the part people get wrong.** Each of `17h`/`18h`/`19h` has an `AE` bit in bit 7; setting `AE = 1` makes that field a *don't-care*. So:
-
-| Want | `17h` `AE` (min) | `18h` `AE` (hour) | `19h` `AE` (week/day) |
-|---|---|---|---|
-| Once per hour, at a given minute | **0** | 1 | 1 |
-| Once per day, at a given time | 0 | 0 | 1 |
-| Once per week | 0 | 0 | 0 |
-| **Once per minute** (all fields ignored) | 1 | 1 | 1 |
-
-With `WADA = 0` (WEEK), **multiple days can be set at once** — the week alarm register is a bitmask, so "Monday, Wednesday, Friday" is a single alarm.
-
-Two cautions: **when `STOP` (`1E`.6) is 1, no alarm event occurs**; and if the alarm registers are being reused as RAM while `AIE = 1`, `/IRQ` can be driven low by accident **[DS-09]** §14.3.1.
-
-### 4.3 Time update
-
-`USEL` (`1C`.5) picks a **1-second** or **1-minute** tick, synchronised to the update of the second or minute register **[DS-09]** §14.4. `/IRQ` self-releases after `tRTN1` (min 7.57 ms). Clearing `UF` releases `/IRQ` immediately — a behaviour Epson added in `ETM50E-08`.
-
-### 4.4 `VLF` — the flag that means "your time is garbage"
-
-**[DS-09]** §14.5: `VLF` (`1D`.**1**) goes 0 → 1 when clock oscillation stopped or a power-on reset occurred, i.e. when data loss may have happened, and stays 1 until written 0.
-
-> *"During the initial power-on (from 0 V) and/or if the value of the VLF bit is '1', be sure to initialize all registers before using them."*
-
-`VLF` reads **1** after a power-on reset (Table 13) and **1** after a software reset (§7.2 note). It is the single most important bit on the device for a battery product — and the vendor driver on this board **does not read it**. See [§11-C4](#11-caveats-errata-and-a-driver-audit).
-
-Do not confuse it with `VBLF` (`1D`.**7**), which is *low-backup-voltage* detection, or with `VBFF` (`1D`.**0**), which is *backup full-charge*.
-
----
-
-## 5. Backup switchover and battery charging
-
-This is the feature that distinguishes the RX8130CE from an ordinary RTC, and it is the most intricate part of the manual (§15, twelve pages).
-
-Three MOS switches (`SW1`, `SW2A`, `SW2B`) sit between `VDD`, `VBAT` and the internal `VOUT` node, arbitrated by a supply-voltage detector. When `VDD` falls below `−VDET2` the RTC's internal supply is switched from `VDD` to `VBAT`; reverse current from `VBAT` into `VDD` is blocked. **While in backup mode the I²C bus and `FOUT` are switched off and their pins go Hi-Z** — but `/IRQ` and `/RST` keep working **[DS-09]** §3.2, §15.1.
-
-### 5.1 Detection thresholds
-
-**[DS-09]** Table 38, with the measured tolerances from Table 5:
-
-| Symbol | What it does | Typ. rising / falling | Selected by |
-|---|---|---|---|
-| `VDET1` | **Reset assert / release** — also gates I²C and FOUT when `INIEN = 1` | 2.80 V / **2.75 V** | `RSVSEL = 0` *(default)* |
-| `VDET1` | idem | 2.70 V / 2.65 V | `RSVSEL = 1` |
-| `VDET2` | **Backup switchover / recover** | 1.35 V / **1.30 V** | — |
-| `VDET3` | **`VBAT` full-charge / recharge** | 3.02 / 2.97 V | `BFVSEL = 00` *(default)* |
-| `VDET3` | idem | 3.08 / 3.03 V | `BFVSEL = 01` |
-| `VDET3` | idem | 2.92 / 2.87 V | `BFVSEL = 10` |
-| `VDET3` | **charging with no limit** | — | `BFVSEL = 11` |
-| `VDET4` | **`VBAT` low / end voltage** → sets `VBLF` | 2.40 V | — |
-
-> ⚠ **Table 39 and Table 38 disagree about `BFVSEL`.** Table 38 maps `01` → 2.92 V and `10` → 3.08 V; Table 39, on the facing page, maps `01` → 3.08 V and `10` → 2.92 V. **The two encodings are transposed.** Both revisions carry the defect. This is a live hazard: pick the wrong one and a rechargeable backup cell is charged to the wrong ceiling. Do not use either table alone — the safe reading is that the two non-default settings are 2.92 V and 3.08 V, and which code selects which is **unresolved** in the vendor documentation. See §11-C2.
-
-### 5.2 `INIEN` — the bit that latches on and cannot be un-latched
-
-**[DS-09]** Table 35. `INIEN` (`1F`.4) defaults to **0**, in which state *"the power switching function is not operating"* and the supply is fixed to `VDD`. Setting it to 1 starts the switching circuit and **initialises and stabilises it**. Epson recommends setting it at least once.
-
-The two sentences that matter:
-
-> *"If this bit is set to 1 even once, the power switching function will start operating. After that, the power switching function continues to operate even if this bit is cleared to zero."*
-
-> *"Setting INIEN from 0 to 1 with VDD < VDET1 disables I2C and FOUT outputs immediately. Therefore, I2C cannot clear INIEN to 0 while VDD < VDET1."*
-
-So `INIEN` is **a one-way latch for the switching hardware**, and setting it at the wrong moment locks you out of the bus with no way back except a supply cycle. On the PaperMono, M5Unified sets it on every `begin()` (§11-C3).
-
-Its second effect is the one that surprises people: with `INIEN = 1`, **I²C and `FOUT` stop working whenever `VDD` < `VDET1` (2.75 V)**. With `INIEN = 0` they keep working below `VDET1`. A 3.3 V rail sagging under load can therefore make the RTC vanish from the bus at 2.7 V rather than degrade gracefully.
-
-### 5.3 `CHGEN` — charging a backup cell
-
-`CHGEN` (`1F`.5), default **0** = *"For non-re-chargeable battery use"*, `SW2` off, no charging. Setting it to 1 puts `SW1`/`SW2` under automatic control for a rechargeable cell or EDLC, and requires `INIEN = 1` **[DS-09]** Table 34.
-
-Charging stops at `+VDET3` and resumes at `−VDET3`; `VBFF` (`1D`.0) reports full-charge, updated every second. `VBLF` (`1D`.7) reports `VBAT` below `VDET4` (2.4 V), and needs `VBLFE` (`31h`.0) plus `INIEN = 1` to have been set at least once. **`VBLF` detection does not work in backup mode** — it is evaluated after returning to normal mode **[DS-09]** Table 42.
-
-Detection cadence **[DS-09]** Table 36: reset detection and power-switching detection run continuously in normal mode; `VDET3`/`VDET4` are sampled **once per second**; in backup mode, switching detection drops to **once per 31.25 ms** and everything else is off.
-
-> ⚠ **`STOP = 1` breaks backup switching.** In backup mode, `STOP` halts the 31.25 ms `VDET2` sampling, *"power supply switching becomes insufficient, and there is the possibility that a leak current occurs"*. Epson's instruction: if you enter backup mode with `STOP = 1`, clear it immediately after `VDD` returns **[DS-09]** §15.6(9).
-
-### 5.4 Leakage
-
-`ISW1`/`ISW2` off-leak between `VDD`/`VBAT` and `VOUT` are **5 nA max** each **[DS-09]** Table 5, and backup-mode consumption `IBAT` is **300 nA typ., 500 nA max** at `VBAT` = 3.0 V. Those are the numbers that make a supercapacitor backup workable — and the numbers that make a **1 µF ceramic** backup last microseconds, which is why the PaperMono's L0 behaviour matters (§2.1).
-
----
-
-## 6. Reset output, FOUT and digital offset
-
-**Reset output** (§16). `/RST` is an N-ch open drain asserted whenever `VDD` < `VDET1` and released **60 ms** after `VDD` recovers. It works in backup mode. `RSF` (`1D`.2) latches that a reset-level excursion happened, and reads **1** after power-on reset. On the PaperMono `/RST` is not routed to any processor; it sits behind `R47`, a 22 Ω 1 % resistor **[SCH]**, whose purpose was not established.
-
-**FOUT** (§14.6). `FSEL1:0` (`1C`.7:6) selects **32.768 kHz** (`00`, the power-on default), **1024 Hz** (`01`), **1 Hz** (`10`) or **off** (`11`). Output stops and goes Hi-Z below `VDET1`. ⚠ **`STOP = 1` disables the 1 Hz output but leaves 32.768 kHz and 1024 Hz running.** On the PaperMono `FOUT` is unrouted, and because the power-on default is *enabled at 32.768 kHz*, an unused `FOUT` is toggling at 32 kHz until firmware turns it off. It is left open as the manual requires, so this is a (small) current cost rather than a fault. `inferred`.
-
-**Digital offset** (§17). `30h`: `DTE` (bit 7) enables it; `L7`…`L1` is a sign-magnitude trim with `L7` as the sign, over **+192.26 to −195.31 × 10⁻⁶ in 3.05 × 10⁻⁶ steps**. Correction is applied to the sub-second counter **every 10 seconds**. It does **not** change the crystal frequency, so a 32.768 kHz `FOUT` is unaffected, but 1 Hz and 1024 Hz outputs acquire jitter, and **the alarm and any wakeup-timer source slower than 4096 Hz are affected by it**.
-
----
-
-## 7. Bring-up
-
-### 7.1 Epson's initialization flow
-
-**[DS-09]** §18.1, in order:
-
-1. Power on.
-2. **Wait > 30 ms.** (Not the oscillation start time — a separate settling requirement.)
-3. **Dummy read** — one read of a free address, ignoring ACK/NACK. Needed when the power ramp did not satisfy the power-on-reset conditions.
-4. **Read `VLF`.** If `VLF = 1`, the part did not return from backup cleanly → perform a **software reset** (§7.2), starting from its step 4.
-5. **Clear `VLF` to 0.** It cannot be cleared until internal oscillation has started, so allow a wait.
-6. Set `INIEN`, then the rest of the configuration, then the clock.
-
-§10.1 adds the timing detail: **`VLF` becomes readable 30 ms after power-on**; register access is possible once `VLF` reads 0, but *"clock updating is invalid while `t_str`"* — up to 1.0 s.
-
-§10.2 adds two conditions that are easy to violate on a battery board: **`VDD` = `VBAT` = GND for ≥ 10 s before power-on** is required for the power-on reset to work, and if the `tR1` ramp condition is not met *"power-on reset may not work. As a result, the time accuracy and current consumption may not meet the specifications. Please reset by software."*
-
-### 7.2 Software reset writes outside the documented map
-
-**[DS-09]** §18.2, reproduced because it is not derivable and the addresses appear nowhere else:
-
-```
-1) Power ON
-2) Wait > 30 ms
-3) Dummy read                (ignore NACK/ACK)
-4) Write 00h to 1Eh
-5) Write 80h to 1Eh          -> then complete the rest immediately
-6) Write 6Ch to 50h
-7) Write 01h to 53h
-8) Write 03h to 66h
-9) Write 02h to 6Bh
-10) Write 01h to 6Bh         -> TEST bit self-clears here
-12) Wait 125 ms
-```
-
-Notes attached to it: leakage may occur between steps 6 and 10 because **all power switches are on** during that window; `/RST` goes low for **up to 95 ms** from step 10; **`VLF` is set to 1** and must be cleared; and **the clock and calendar registers are *not* reset** — the time survives.
-
-### 7.3 I²C protocol constraints
-
-**[DS-09]** §19.2, §19.6:
-
-- Standard I²C, up to 400 kHz. Address `0110010` + R/W.
-- **A single transfer must not exceed 0.95 seconds** between START and STOP. There is no byte-count limit, only that time limit.
-- Epson explicitly warns: *"Please make sure to send I2C start condition before actual transmission of the RTCs slave address as otherwise the slave address appears to be shifted by 1 bit."*
-- ⚠ **The clock stops during I²C communication.** §13.1(1): *"At the start of a I2C communication, the time and clock counting stops (which causes loss of time), and clock starts automatically again at the end of the I2C communication."* See §11-C5.
-
----
-
-## 8. Libraries
-
-| Option | Where | Verdict |
-|---|---|---|
-| **`M5Unified` → `M5.Rtc`** | `github.com/m5stack/M5Unified`, backed by `src/utility/rtc/RX8130_Class.{hpp,cpp}` | ✅ **What the PaperMono uses.** Competent, and better than it looks — but see the audit in §11 |
-| Raw I²C | — | Entirely reasonable; §3–§7 above is the whole device. Mind the block-wrapping auto-increment (§3.1) |
-| Epson tools | Epson publishes an Excel clock-accuracy calculator and a digital-offset calculator, linked from the manual | Not retrieved |
-
-API surface **[SRC]** `RX8130_Class.cpp`:
-
-```
-begin(I2C_Class*)
-getDateTime(rtc_date_t*, rtc_time_t*) / setDateTime(...)
-setTimerIRQ(uint32_t msec)   -> returns the period actually programmed, in ms
-setAlarmIRQ(const rtc_date_t*, const rtc_time_t*)
-getIRQstatus()   // 0x1D & 0x18  -> TF | AF
-clearIRQ()       // write 0xA7 to 0x1D  (write-0-clear: clears TF and AF only)
-disableIRQ()     // clear TIE|AIE, then clearIRQ()
-getVoltLow()     // 0x1D & 0x80  -> VBLF     <-- see C4
-```
-
-The factory firmware simply aliases it: `m5::RTC_Class& rtc = M5.Rtc;` **[SRC]** `hal.h:70`, and uses **4 bytes of the RTC's user RAM from `0x20`** **[SRC]** `hal_board.cpp:18` (`RX8130_RAM_BASE = 0x20`, `RX8130_RAM_SIZE = 4`) — that is the full `20h`–`23h` block.
-
----
-
-## 9. Vendor driver audit — `M5Unified::RX8130_Class` against `ETM50E`
-
-Read side by side, as the method requires. **Most of it is good**, and two of the findings are the opposite of defects.
-
-### 9.1 What the driver does well
-
-- **`clearIRQ()` writes `0xA7`.** Every flag in `1D` is write-0-to-clear with writes of 1 ignored, so `0b1010_0111` clears exactly `TF` (bit 4) and `AF` (bit 3) and touches nothing else. `RSF`, `VLF`, `UF`, `VBLF` and `VBFF` are all preserved. The in-code comment says `// W0C: clear TF and AF only`, and it is correct. **Not a defect.**
-- **`setAlarmIRQ()` gets `AE` polarity right.** The buffer is initialised `{0x80, 0x80, 0x80}` — all fields disabled — and a field is *enabled* by overwriting it with its BCD value, which clears `AE`. It sets `WADA` (`1C`.3) according to whether a date or a weekday was supplied, encodes the weekday as a bitmask, and sets `AIE` only if at least one field was given. Matches §14.3 exactly. **Not a defect.**
-- **`setTimerIRQ()` is unusually careful.** It picks a source clock from a table, and **deliberately treats 4096 Hz as a last resort** with the comment *"its /IRQ pulse is only 122us"* — which is precisely Epson's `tRTN2` figure for `TSEL = 000` (§4.1). It bounds the first-countdown error (§4.1's stated trap) by requiring at least 16 counts. It writes `1A`/`1B` while `TE = 0` and then **reads them back and retries up to three times**, with the comment: *"a corrupted preset was observed on a shared bus"*. That is a real-world observation about this board's seven-device I²C bus, recorded in vendor code.
-- **`getDateTime()` validates before committing** — BCD range checks on every field, a one-hot check on the weekday register, and a `validateDateTime()` pass — returning `false` rather than a plausible-looking wrong date. The rationale is in the comment.
-
-### 9.2 `getVoltLow()` reports the wrong flag — this is the finding
-
-```cpp
-bool RX8130_Class::getVoltLow(void)
-{
-  // 0x80: VBLF
-  return readRegister8(0x1D) & 0x80;
-}
-```
-
-`0x80` is bit 7 of the Flag Register, which is **`VBLF` — "Low-VBAT has been detected (`VDET4`)"** **[DS-09]** Table 41. The flag that means *the clock stopped and the register data are invalid* is **`VLF`, bit 1** (`0x02`) **[DS-09]** Table 31.
-
-Two things follow, and they compound:
-
-1. **After a power-on reset, `1D` reads `0000 0110`** — `VLF = 1`, `VBLF = 0` **[DS-09]** Table 13. So on the exact occasion the method exists to catch, **`getVoltLow()` returns `false`.**
-2. **`VBLF` detection is conditional.** It requires `VBLFE` (`31h`.0) and `INIEN = 1` to have been set, and it *"is not available in backup mode"* **[DS-09]** Table 42. `RX8130_Class::begin()` never writes `31h`. With `CHGEN = 1` (which `begin()` does set) and `VBLFE = 0`, Epson's table says detection is available *"during normal mode re-chargeable battery charging"* — which, on a board where `VBAT` may be a 1 µF ceramic rather than a cell (§2.1), is a condition that may never meaningfully arise.
-
-**Severity: latent, and the documentation amplifies it.** The device record's [`features/rtc.md` §5](../../../devices/m5stack/papermono/features/rtc.md) currently advises: *"`getVoltLow()` is the one worth wiring into a first-boot path: it tells you the RTC lost its supply and the time is not trustworthy."* On the evidence above it does not tell you that. Code that trusts it will accept an uninitialised clock as valid.
-
-**What to do instead:** read `1D` yourself and test **bit 1**. If set, follow §7.1 — software-reset if necessary, clear `VLF`, then set the time. Recorded here rather than patched into the other record; that is the device record's author's call.
-
-*(Whether the name `getVoltLow` was intended to mean "backup voltage low" rather than "the RTC lost power" is unknowable from the source. Either way the datasheet-facing behaviour is as described, and the `RX8130_Class` implementation is the only accessor M5Unified exposes for `1D`.)*
-
-### 9.3 `begin()` skips Epson's entire initialization procedure
-
-```cpp
-bool RX8130_Class::begin(I2C_Class* i2c)
-{
-  ...
-  bool res = bitOn(0x1F, 0x30);          // CHGEN=1 (0x20) and INIEN=1 (0x10)
-  res &= writeRegister8(0x30, 0x00);     // digital offset off
-  res &= writeRegister8(0x1E, 0x00);     // Control Register 0 = 0
-  ...
-}
-```
-
-Against §18.1, this omits: the **> 30 ms wait**, the **dummy read**, the **`VLF` check**, the **software reset when `VLF = 1`**, and **clearing `VLF`**. Writing `1E` = `0x00` does correctly clear `TEST` and `STOP` along with the interrupt enables, which is good hygiene.
-
-Two specific consequences:
-
-- **`INIEN` is set on every `begin()`, and it is a one-way latch** (§5.2). Epson also warns that setting it while `VDD` < `VDET1` immediately kills the I²C interface with no software route back. On a board where `begin()` may run during a rail ramp, that is a real if unlikely wedge. **Latent.**
-- **`CHGEN = 1` enables backup-battery charging** (§5.3). Epson's default is 0, *"for non-re-chargeable battery use"*. **If `VBAT` on this board carries a primary cell or nothing but a ceramic capacitor rather than a rechargeable cell or EDLC, this write is at best pointless and at worst wrong.** Since the `VBAT` net could not be established from the schematic text layer (§2.1), **this cannot be resolved here** — and that is exactly why the `VBAT` net is the highest-value open item in this record. Note that `M5Unified`'s `RX8130_Class` is shared across M5Stack products, so the setting is not necessarily a PaperMono decision at all.
-
-### 9.4 Registers the driver never touches
-
-`1C` `FSEL1:0` — so **`FOUT` is left at its power-on default of 32.768 kHz enabled** (§6). `1C` `USEL` and `1E` `UIE` — the time-update interrupt is unreachable through `M5.Rtc`. `1F` `RSVSEL`, `BFVSEL1:0`, `SMPTSEL1:0` — reset threshold, charge ceiling and sampling cadence all stay at defaults. `31h` `VBLFE`. `1E` `TSTP`/`TBKON`/`TBKE` — the Long-Timer / usage-counter mode. `30h` is written once, to zero, so the digital offset trim is explicitly disabled and never used.
-
----
-
-## 10. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — designator `U16`, sheet 4
-
-| Role on PaperMono | Pin | Evidence |
-|---|---|---|
-| I²C slave at **`0x32`** on the shared system bus, driven at **400 kHz** | 2 `SCL` → `G48_SYS_SCL` (GPIO48); 3 `SDA` → `G47_SYS_SDA` (GPIO47) | **[SCH]** `U16`.2/.3; **[SRC]** `hal_board.cpp:17,19` |
-| **`nIRQ` → M5PM1 pin 3 (`IO0`)**, *not* to any ESP32-S3 GPIO | 6 → `PYG0_RTC_INT`, pulled up by `R49` | **[SCH]** `U16`.6; **[SRC]** `app_sleep_wake.cpp:67` |
-| Interface supply | 1 `VIO` → **`3V3_L0`** (always-on rail) | **[SCH]** — see §2.1 |
-| Logic supply | 8 `VDD` → vendor power tree says **`3V3_L1`**; net not recoverable from the schematic text layer | **[DOC]** vs **[SCH]**, §2.1 |
-| Backup supply | 10 `VBAT` → **not established** | §2.1 |
-| Reset output | 5 `/RST` behind `R47` **22 Ω / 1 %**; not routed to a processor | **[SCH]** |
-| `FOUT` | 4 — **unrouted**, left open as the manual requires | **[SCH]** |
-| User RAM | `20h`–`23h`, **all 4 bytes used by the factory firmware** | **[SRC]** `hal_board.cpp:18` |
-| Local passives | `C60`, `C61`, `C62` — 1 µF / 25 V each; `R49` `/IRQ` pull-up | **[SCH]** |
-
-#### 10.1 The interrupt path is the whole point
-
-There is **no route from this RTC to any ESP32-S3 pin.** An ESP32 wake source configured for an RTC alarm can never fire.
-
-The shipped factory binary states the path and the polarity in as many words **[FW]**:
-
-```
-PM1 shutdown, wake by RX8130 timer  -> PM1 G0 falling edge
-```
-
-M5Unified configures the board to match **[SRC]** `Power_Class.cpp:528` onward: `_rtcIntPin = GPIO_NUM_1` — which is the **M5PM1's IRQ output toward the host**, not the RTC line — with `setGPIOIRQMaskBits(0x1E)` enabling M5PM1 `G0`'s interrupt and masking the other four, `G0` as a plain input, and `G1` as a push-pull IRQ output.
-
-So the chain is:
-
-- **Host awake:** RX8130CE `/IRQ` → M5PM1 `IO0` → M5PM1 `IO1` → ESP32-S3 **GPIO1**.
-- **Host asleep in L1:** the chain stops at the M5PM1, which **powers the application processor back up**. That is the capability this part exists to provide on this board.
-
-The falling edge is the RTC's open-drain `/IRQ` pulling low, and the M5PM1's `G0` wake is configured falling-edge to match **[SRC]** `app_sleep_wake.cpp:67`.
-
-⚠ Note the vendor firmware **disables both M5PM1 wake sources at startup** (`clearPm1WakeIrqState()`, `hal_board.cpp:42-43`), so it does not itself demonstrate the RTC-wake path end to end. The firmware string proves the path was designed and exercised by someone; nothing located here proves it *works*.
-
-#### 10.2 Practical consequences for this board
-
-- **Choose the right timer for the job.** For "wake me in N seconds", the [M5PM1's own 31-bit second timer](../../m5stack/m5pm1/README.md) needs no RTC at all and is the vendor-demonstrated path. Use the RX8130CE alarm when you need a wall-clock time — "07:30 on weekdays" — which the M5PM1 cannot express. See [`features/rtc.md` §6](../../../devices/m5stack/papermono/features/rtc.md).
-- **The alarm has minute resolution and latches `/IRQ`** (§4.2). Clear `AF` in the wake handler or the M5PM1's `G0` never returns high.
-- **Keep `L1` alive across a shutdown** (`ldoSetPowerHold(true)`) or the RTC loses its supply along with everything else.
-- **The bus is shared with a chatty NFC poller.** §11-C5 explains why that is not merely a bandwidth question for this particular device.
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) — **fitted, identically**
-
-The Lite drops **NFC and LoRa and nothing else**; the RX8130CE, its `0x32` address, its `PYG0_RTC_INT` line to M5PM1 `IO0` and the whole power tree carry over unchanged **[DOC]**. The shared `M5PaperMono-UserDemo` firmware image serves both SKUs and distinguishes them by probing the **NFC** rail, never the RTC **[SRC]** `hal_board.cpp:160-172`.
-
-One caveat on the strength of that claim: M5Stack publishes a **4-sheet `PRJ` PDF** for the Lite rather than the 6-sheet `SCH` published for the PaperMono, so the Lite's RTC wiring is asserted from the vendor specification table and the shared firmware, **not** from a Lite schematic. `inferred`.
-
----
-
-## 11. Caveats, errata and a driver audit
-
-| # | Issue | Evidence |
-|---|---|---|
-| **C1** | **The mirror is one revision behind — and carries *more* text than Epson's current file.** `ETM50E-09` (2025-06-30) vs `ETM50E-10` (2026-01-30). The two were normalised and diffed line by line: apart from table-of-contents renumbering and whitespace, **the only substantive change is that `-10` deletes items (1)–(7) of §14.4.2**, the seven-step operation description of the time-update interrupt. Epson's own changelog entry reads *"Deleted (1) to (7) in the operation description."* **Every register, threshold and timing value in this record is identical in both.** Both revisions are retained | `executed-success` — full-text diff, 2026-09-01 |
-| **C2** | ⚠ **`BFVSEL` is encoded two contradictory ways on facing pages.** Table 38 gives `01` → 2.92 V, `10` → 3.08 V; Table 39 gives `01` → 3.08 V, `10` → 2.92 V. Present in both revisions. **A backup cell charged to the wrong ceiling is a safety-adjacent error.** Unresolved — do not rely on either table alone | **[DS-09]**/**[DS-10]** §15.6 |
-| **C3** | **`INIEN` is a one-way latch, and M5Unified sets it on every `begin()`.** Once set, the power-switching circuit stays on even if the bit is cleared; and setting it while `VDD` < `VDET1` disables the I²C interface *with no software route back* | **[DS-09]** Table 35; **[SRC]** §9.3 |
-| **C4** | ⚠ **`getVoltLow()` reads `VBLF` (bit 7, low-backup-battery), not `VLF` (bit 1, oscillation stopped / data invalid).** After a power-on reset `VLF = 1` and `VBLF = 0`, so the method returns `false` on precisely the occasion it is used to detect. **The device record's `features/rtc.md` §5 currently recommends it for exactly that purpose.** Full analysis in §9.2 | **[DS-09]** Tables 13, 31, 41 vs **[SRC]** `RX8130_Class.cpp` |
-| **C5** | ⚠ **I²C communication stops the clock.** §13.1(1): *"At the start of a I2C communication, the time and clock counting stops (which causes loss of time), and clock starts automatically again at the end."* A transfer may run up to **0.95 s**. On a board whose single I²C bus also carries an NFC poller running 180 ms detect calls with 60 ms gaps for seconds at a time, this is a **timekeeping-accuracy** concern, not just a bandwidth one. **Unresolved:** the manual does not say whether counting halts for *any* bus activity or only for transactions addressed to `0x32`. Nothing was measured | **[DS-09]** §13.1, §19.2 |
-| **C6** | **Auto-increment wraps inside 16-byte blocks** (`10h`–`1Fh`, `20h`–`2Fh`, `30h`–`3Fh`), it does not carry into the next block (§3.1) | **[DS-09]** §19.6 |
-| **C7** | **§13.3.1 says the clock registers are at "0h ~ 16h". They are at `10h`–`16h`.** Present in both revisions. Most I²C RTCs start at `00h`, so a ported driver will read zeros (§3.2) | **[DS-09]**/**[DS-10]** §13.3.1 vs Table 12 |
-| **C8** | **`AE` is low-active.** Setting an alarm field's `AE` bit to **1** makes it a *don't-care*; all three set to 1 gives an alarm every minute (§4.2) | **[DS-09]** §14.3.1 |
-| **C9** | **The alarm latches `/IRQ` indefinitely; the timer and update interrupts self-release.** Failing to clear `AF` leaves the line low forever (§4) | **[DS-09]** §14.3 |
-| **C10** | **The 4096 Hz timer source releases `/IRQ` after only 122 µs**, versus 7.57 ms for every other source. An interrupt that short can be missed by a polling host. M5Unified deliberately avoids it (§9.1) | **[DS-09]** Table 16 |
-| **C11** | **Reading the live timer counter is not atomic.** Epson recommends reading twice and accepting the value only when two reads agree | **[DS-09]** §14.2.1 |
-| **C12** | **`STOP = 1` has three unrelated side effects:** no alarm events; 1 Hz `FOUT` disabled while 32.768 kHz and 1024 Hz keep running; and backup switching becomes unreliable with possible leakage | **[DS-09]** §14.3.1, §14.6.2, §15.6(9) |
-| **C13** | **`FOUT` defaults to *enabled* at 32.768 kHz.** On this board it is unrouted and unconfigured, so it toggles until firmware disables it. Left open as the manual requires, so this is a small current cost rather than a fault. `inferred` | **[DS-09]** §14.6.2; **[SCH]**; **[SRC]** — negative result, M5Unified never writes `FSEL` |
-| **C14** | **The power-on-reset preconditions are demanding:** `VDD` = `VBAT` = GND for **≥ 10 seconds** before power-on, plus a `tR1` ramp condition. If unmet, Epson says accuracy and current consumption may be out of specification and a **software reset is required**. Whether a PaperMono coming out of L0 satisfies this is **unknown** | **[DS-09]** §10.2 |
-| **C15** | **M5Unified's `begin()` performs none of Epson's §18.1 flow** — no 30 ms wait, no dummy read, no `VLF` check, no software reset, no `VLF` clear (§9.3) | **[SRC]** vs **[DS-09]** §18.1 |
-| **C16** | **The `VDD` and `VBAT` nets on this board are not established.** The schematic text layer yields adjacency, not connectivity, and no label was recoverable at either pad. Statements about L0 timekeeping, and the correctness of `CHGEN = 1`, both hang on this (§2.1, §9.3) | **[SCH]** — explicit gap |
-| **C17** | **Nothing about this part has been measured on this board by anyone.** No drift figure, no accuracy report, no backup-hold-up time, no confirmation that an RTC alarm has ever woken a PaperMono | **[DOC]**, community — negative result |
-
----
-
-## 12. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf` | 2 283 323 | `7157dc5692e5e0d84203027b600858e57880ef7a38b9c7d7f8c661a93fc8f3f5` | **Epson application manual `ETM50E-09`, 70 pp — in English despite the `cn` in the filename** (see the note at the top of this record). PDF metadata: Producer `Microsoft® Word for Microsoft 365`, created 2025-06-23, modified 2025-07-16, AES-256 encrypted with print/copy permitted. **This is the revision M5Stack ships and the one the board's software was written against.** |
-| `artifacts/rx8130ce-application-manual-etm50e-10-en-epson.pdf` | 2 008 845 | `db027a5fa2dd17b333da81e95063764eb5536d2878c63b64949348d2ec4b8a22` | **Epson application manual `ETM50E-10`, 70 pp, English — Epson's current revision, retrieved direct from the manufacturer in this pass.** PDF metadata: Author `Seiko Epson Corporation`, Creator `Pdf_as`, Producer `iTextSharp 5.4.5`, created 2026-02-01, RC4 encrypted with print/copy permitted. Retained **because the diff is a finding** (§11-C1): it is one revision *newer* but carries *less* text |
-
-Both files, in the schema the manifest uses:
-
-| Field | `…-cn-m5stack-mirror.pdf` | `…-etm50e-10-en-epson.pdf` |
-|---|---|---|
-| Version / revision | **`ETM50E-09`** | **`ETM50E-10`** |
-| Publication date | **2025-06-30** (document revision table) | **2026-01-30** (document revision table) |
-| Retrieval date | **2026-09-01** | **2026-09-01** |
-| Byte size | 2 283 323 | 2 008 845 |
-| SHA-256 | `7157dc56…befef1`⁠ → `7157dc5692e5e0d84203027b600858e57880ef7a38b9c7d7f8c661a93fc8f3f5` | `db027a5fa2dd17b333da81e95063764eb5536d2878c63b64949348d2ec4b8a22` |
-| **Canonical URL** | `https://download.epsondevice.com/td/pdf/app/RX8130CE_en.pdf` *(now serves `-10`; `-09` is no longer offered by Epson)* | `https://download.epsondevice.com/td/pdf/app/RX8130CE_en.pdf` |
-| **M5Stack mirror URL** | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1132/RX8130CE_cn-Register-Datasheet.pdf` | *(not mirrored by M5Stack)* |
-| Additional URL | — | `https://download.epsondevice.com/td/pdf/app/RX8130CE_cn.pdf` — **the same English document**, 2 008 853 B, `0ff562f25f4b5a8cf5f3df98632c5bc31030cdd4ebf7d7e53fbb03091d4c63d2` |
-| Product page | `https://www5.epsondevice.com/en/products/rtc/rx8130ce.html` → redirects to `https://www.epsondevice.com/crystal/en/products/rtc/rx8130ce.html` | idem |
-| Licence | **`unknown`** — © Seiko Epson Corporation. ⚠ the document's own notice 2 states: *"This document may not be copied, reproduced, or used for any other purposes, in whole or in part, without Epson's prior consent."* | **`unknown`**, identical notice |
-| Redistribution status | **`restricted`** — the document states a limitation in as many words | **`restricted`** |
-| Disposition | **`repository`** | **`repository`** |
-| Type validated | Yes — `%PDF-1.7`, 70 pp, A4 | Yes — `%PDF-1.4`, 70 pp, A4 |
-
-> **Note on the redistribution status.** Both files carry an explicit no-redistribution notice, so they are marked `restricted` rather than `unknown` — this is the honest reading of the text, recorded as metadata, not as a legal conclusion. They are retained under the repository's stated policy of gathering the artifact and recording the terms. Flagged here for review rather than acted on.
-
-Recorded reference-only, not retained:
-
-| Item | URL | Bytes | SHA-256 | Status |
-|---|---|---:|---|---|
-| Application manual, **Japanese** — `ETM50J-10`, 64 pp | `https://download.epsondevice.com/td/pdf/app/RX8130CE_ja.pdf` | 2 986 434 | `32913ca00eadaeaa263e448bf0049a492d808449fa41ee3f1aabb46c9409011c` | Downloaded, hashed and identified, **not retained**. Metadata: Creator `Microsoft® Word for Microsoft 365`, created 2025-06-23, AES-256. Six pages shorter than the English. **Equivalence not assessed.** Freely re-fetchable from a stable vendor URL; disposition `reference-only` |
-| Datasheet brief | `https://download.epsondevice.com/td/pdf/brief/RX8130CE_en.pdf` | — | — | **Not retrieved.** Confirmed listed on the Epson product page |
-| RoHS / REACH / TSCA / CA65 declarations, package-and-reflow guide | `https://download.epsondevice.com/td/pdf/rohs/RX8130CE.pdf` and siblings | — | — | **Not retrieved.** Enumerated from the product page; compliance paperwork, not technical |
-
-**Retrieval note.** `www.epsondevice.com` served every one of these to a plain modern-Chrome user-agent on the first attempt, HTTP 200, correct `application/pdf`. No user-agent rotation was needed. The only trap is the redirect from the `www5.` host to `www.epsondevice.com/crystal/…`, which `curl -L` follows without complaint. `executed-success`, 2026-09-01.
-
----
-
-## 13. Related components
-
-- [**M5Stack M5PM1**](../../m5stack/m5pm1/README.md) — where this RTC's interrupt actually lands (`IO0`), and the owner of the `3V3_L0`/`3V3_L1` rails. Its **own** 31-bit second timer is the simpler wake mechanism on this board
-- [**Espressif ESP32-S3R8**](../../espressif/esp32-s3r8/README.md) — the host. GPIO47/48 carry the bus; **no ESP32-S3 pin touches this part's interrupt**
-- [**M5Stack M5IOE1**](../../m5stack/m5ioe1/README.md) — the other coprocessor on the same bus, with 32 bytes of its own retention RAM at `0x70`–`0x8F` that nothing uses
-- [**STMicroelectronics ST25R3916**](../../stmicroelectronics/st25r3916/README.md) — the NFC front end whose polling shares this bus (§11-C5)
-- [**Bosch Sensortec BMI270**](../../bosch-sensortec/bmi270/README.md) — the other M5PM1 wake source, on `IO4`
-- [**NXP PCF85063A**](../../nxp/pcf85063a/README.md) — the comparable RTC used on the Inkplate boards in this repository, for contrast: 220 nA, I²C `0x51`, **no** backup-charge controller
-- [Vendor sourcing guides index](../../../vendors/README.md) — **no Seiko Epson guide exists yet**; the retrieval notes in §12 are what one would open with
-- [Components index](../../README.md)
-
----
-
-## 14. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | RX8130CE Application Manual | **Seiko Epson Corporation**, mirrored by M5Stack | credible mirror | application manual | `artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf`; mirror URL `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1132/RX8130CE_cn-Register-Datasheet.pdf` | 2026-09-01 | **`ETM50E-09`, 2025-06-30**, 70 pp | §1–§7, §11. **The revision the board's software targets** |
-| S-2 | RX8130CE Application Manual | **Seiko Epson Corporation** | primary | application manual | `artifacts/rx8130ce-application-manual-etm50e-10-en-epson.pdf`; `download.epsondevice.com/td/pdf/app/RX8130CE_en.pdf` | 2026-09-01 | **`ETM50E-10`, 2026-01-30**, 70 pp | §11-C1 — establishes mirror lag and its (small) content delta |
-| S-3 | RX8130CE Application Manual, Japanese | Seiko Epson Corporation | primary | application manual | `download.epsondevice.com/td/pdf/app/RX8130CE_ja.pdf` | 2026-09-01 | **`ETM50J-10`**, 64 pp | §12 — reference-only; establishes that the English text is a translation |
-| S-4 | RX8130CE product page | Seiko Epson Corporation | primary | vendor page | `www5.epsondevice.com/en/products/rtc/rx8130ce.html` → `www.epsondevice.com/crystal/en/products/rtc/rx8130ce.html` | 2026-09-01 | undated | §12 document enumeration; **negative result:** no Chinese-language manual is published |
-| S-5 | PaperMono schematic, sheet 4 (`U16`) | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | **V0.6.2, 2026-05-22** | §2 pin table, §10 wiring |
-| S-6 | `M5Unified` — `src/utility/rtc/RX8130_Class.{hpp,cpp}`, `src/utility/Power_Class.cpp` | M5Stack | primary | source | `github.com/m5stack/M5Unified`, pinned by the factory firmware at `2fe93c0c64f12f916e73a0605c86bf1241c06a6b` (patched) | 2026-09-01 | release 0.2.21 lineage, MIT | §8 API, §9 driver audit, §10.1 |
-| S-7 | `M5PaperMono-UserDemo` — `main/hal/hal_board.cpp`, `main/hal/hal.h`, `main/app_sleep_wake.cpp`, `repos.json` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-UserDemo` @ `c1099107271d31a0678d661a896e2b04dbb331ea` | 2026-09-01 | 2026-08-10, MIT | §1 address/speed, §8 RAM use, §10 |
-| S-8 | PaperMono product page — specification table, power-tree table | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono` | 2026-09-01 | undated | §2.1 rail assignment, §10 |
-| S-9 | PaperMono-Lite product page | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono-Lite` | 2026-09-01 | undated | §10 — the RTC carries over unchanged |
-| S-10 | `C153-PaperMono-UserDemo-v1.2` firmware image | M5Stack via M5Burner | primary | binary | SHA-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | 2026-09-01 | v1.2, built 2026-08-06, IDF v5.5.1 | §10.1 — `PM1 shutdown, wake by RX8130 timer -> PM1 G0 falling edge` |
diff --git a/components/seiko-epson/rx8130ce/artifacts/rx8130ce-application-manual-etm50e-10-en-epson.pdf b/components/seiko-epson/rx8130ce/artifacts/rx8130ce-application-manual-etm50e-10-en-epson.pdf
deleted file mode 100644
index 114dc68..0000000
Binary files a/components/seiko-epson/rx8130ce/artifacts/rx8130ce-application-manual-etm50e-10-en-epson.pdf and /dev/null differ
diff --git a/components/seiko-epson/rx8130ce/artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf b/components/seiko-epson/rx8130ce/artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf
deleted file mode 100644
index c001261..0000000
Binary files a/components/seiko-epson/rx8130ce/artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/semtech/llcc68/README.md b/components/semtech/llcc68/README.md
deleted file mode 100644
index 55de8dd..0000000
--- a/components/semtech/llcc68/README.md
+++ /dev/null
@@ -1,187 +0,0 @@
-# Semtech LLCC68 — "LoRa Smart Home", the cost-reduced SX1262 that cannot do SF12
-
-> **Lineage:** [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md).
-> **Domain:** [`guides/lora`](../../../guides/lora/README.md). **Full sibling record:**
-> [`sx1262`](../sx1262/README.md) — read that for the register model, `BUSY` handshake, DIO2/DIO3
-> behaviour and the four mandatory errata workarounds. **All of it applies here unchanged.**
-
-- **Category:** sub-GHz **LoRa / (G)FSK** transceiver, SPI command interface, **+22 dBm**
-- **Generation:** **2** — an SX1262 sibling. ⚠ Not named in `DS.LR20xx` §23.8, which lists one or two representatives per generation; assigning it to Gen 2 is **[INF]**, from *"Pin-to-pin compatible to SX1262"* **[PP]**
-- **Package:** *"QFN (same as SX1262)"* — i.e. QFN24, 4 × 4 mm **[PP]**
-- **Research depth:** ⚠ **light record.** The LLCC68 datasheet is behind Semtech's Salesforce gate and **was not obtained**. Content here is Semtech's product page, RadioLib source, and the SX1262 record.
-- **Retrieved:** 2026-09-04
-
----
-
-## 1. ⚠ The substitution trap, stated plainly
-
-**Cheap modules and cheap boards use the LLCC68 and the SX1262 interchangeably, and they are not
-interchangeable.** They share a pinout, a package, a command set, a register map and a driver base
-class. What differs is the LoRa configuration space, and it differs in the direction that matters
-most for range.
-
-| | **SX1262** | **LLCC68** |
-|---|---|---|
-| Max link budget **[PP]** | **170 dB** | **151 dB** |
-| Best sensitivity **[PP]** | **−148 dBm** | **−129 dBm** |
-| **Max SF at BW 125 kHz** | **SF12** | ⚠ **SF9** |
-| **Max SF at BW 250 kHz** | SF12 | ⚠ **SF10** |
-| **Max SF at BW 500 kHz** | SF12 | ⚠ **SF11** |
-| **Bandwidths below 100 kHz** | ✅ down to 7.81 kHz | ❌ **none** |
-| LoRa bit-rate range **[PP]** | up to 62.5 kbps | **1.76 – 62.5 kbps** |
-| Max Tx | +22 dBm | +22 dBm |
-| RX current | 4.6 mA | 4.6 mA |
-| FSK | to 300 kbps | to 300 kbps |
-| Pinout | — | **pin-to-pin compatible** |
-
-**19 dB of link budget.** That is roughly the difference between a 2 km link and a 200 m one, and it
-is invisible from the schematic, the footprint and the module photo.
-
-### 1.1 The restriction, in Semtech's own words
-
-**[PP]**, verbatim from the LLCC68 product page feature list:
-
-> Data rates for LoRaWAN include **SF7 to SF9 at 125 kHz, SF7 to SF10 at 250 kHz, and SF7 to SF11 at
-> 500 kHz**
-
-### 1.2 The restriction, as code
-
-**RadioLib encodes it structurally, which is independent confirmation** — `src/modules/LLCC68/LLCC68.cpp`,
-read live 2026-09-04 **[RL]**:
-
-```cpp
-class LLCC68: public SX1262 { ... };            // derives from SX1262
-
-int16_t LLCC68::setBandwidth(float bw) {
-  RADIOLIB_CHECK_RANGE(bw, 100.0f, 510.0f, RADIOLIB_ERR_INVALID_BANDWIDTH);   // ⚠ floor of 100 kHz
-  return(SX1262::setBandwidth(bw));
-}
-
-int16_t LLCC68::setSpreadingFactor(uint8_t sf) {
-  switch(SX126x::bandwidth) {
-    case RADIOLIB_SX126X_LORA_BW_125_0: RADIOLIB_CHECK_RANGE(sf, 5,  9, ...); break;   // ⚠
-    case RADIOLIB_SX126X_LORA_BW_250_0: RADIOLIB_CHECK_RANGE(sf, 5, 10, ...); break;
-    case RADIOLIB_SX126X_LORA_BW_500_0: RADIOLIB_CHECK_RANGE(sf, 5, 11, ...); break;
-    default: return(RADIOLIB_ERR_INVALID_SPREADING_FACTOR);
-  }
-  return(SX1262::setSpreadingFactor(sf));
-}
-```
-
-Two things to take from that beyond the numbers:
-
-1. ⚠ **`setBandwidth` has a 100 kHz floor.** The SX1262's narrow bandwidths — 7.81, 10.4, 15.6,
-   20.8, 31.25, 41.7, 62.5 kHz — are **all unavailable**. Semtech's marketing line only mentions the
-   SF ceiling; the bandwidth floor is at least as consequential, and is the reason a "just use a
-   lower bandwidth instead" workaround does not exist.
-2. ⚠ **The SF check reads the *current* bandwidth.** Set SF before BW and you can get a spurious
-   rejection, or pass a check against the wrong limit. **Always set bandwidth first.**
-
-### 1.3 What it means in practice
-
-- **Meshtastic's `LONG_SLOW` and `VERY_LONG_SLOW` presets use SF12.** An LLCC68 node **cannot join
-  such a mesh at all** — not "with reduced range", at all. `RADIOLIB_ERR_INVALID_SPREADING_FACTOR`.
-- **LoRaWAN DR0 (SF12/125 kHz) is unreachable.** In EU868 that is the mandatory join/fallback data
-  rate, so an LLCC68 end device has a materially different regional-parameter story.
-- **A board advertised as "SX1262-compatible" tells you nothing about which die is fitted.** They
-  are pin-to-pin compatible, so a manufacturer can substitute silently between production runs.
-
-### 1.4 How to tell which one you have
-
-Ranked by reliability:
-
-1. **Read the chip marking.** Definitive, needs a teardown and a microscope.
-2. **Ask the driver.** RadioLib's `SX126x` base exposes the device's status; more practically,
-   **request SF12 at BW 125 kHz.** An SX1262 accepts it; an LLCC68 returns
-   `RADIOLIB_ERR_INVALID_SPREADING_FACTOR` **[RL]**. Cheap, non-destructive, conclusive for the
-   thing you actually care about. **[INF]** — logically sound, `not-tested` on hardware here.
-3. **Read the firmware.** Which RadioLib class does the vendor instantiate? This is the method the
-   [SX1262 record](../sx1262/README.md) used to establish `62` rather than `61`, and it generalises.
-4. ⚠ **Do not trust the product name.** "LoRa Smart Home" is Semtech's marketing name for the
-   LLCC68; module vendors rarely use it.
-
----
-
-## 2. What is identical to the SX1262
-
-Everything in [`components/semtech/sx1262/README.md`](../sx1262/README.md) except §1's table.
-Specifically: the SPI command interface and 8-bit opcodes; the mandatory `BUSY` handshake;
-`SetDio2AsRfSwitchCtrl` and `SetDio3AsTcxoCtrl`; the DC-DC/LDO choice and the fact that **the DC-DC
-does not help transmit current** because the PA runs from `VBAT`; the four §15 errata workarounds
-including the **SX1262-only PA-clamp fix**, which applies to the LLCC68 too since it shares the
-+22 dBm PA topology; `XOSC_START_ERR` being expected at power-on with a TCXO; and the 150–960 MHz
-synthesiser range.
-
-**Do not duplicate that material here.** If you are debugging an LLCC68, you are debugging an
-SX1262 with a smaller configuration space.
-
----
-
-## 3. Software support
-
-| Stack | Status |
-|---|---|
-| **RadioLib** | ✅ `src/modules/LLCC68`, **deriving from `SX1262`** and overriding exactly two methods (§1.2). MIT **[RL]** |
-| **Semtech `llcc68_driver`** | ✅ standalone repository, **BSD-3-Clause-Clear**, last push **2025-10-15** — same day as `sx126x_driver`, so the two are maintained in lockstep **[GH]** |
-| **`one_channel_hub`** | Semtech's ESP-IDF one-channel hub explicitly *"with support of sx1261, sx1262, sx1268 and llcc68 Semtech radio chips"* **[GH]** |
-| **Meshtastic** | ✅ `LLCC68_RADIO` in `LoRaRadioType`, present in **v2.7.26 stable** **[MT]** |
-| **USP** | "buildable" on SX126x shields; the LLCC68 is not separately called out **[GH]** |
-| Linux kernel | ❌ none |
-
-⚠ **The LLCC68 has a standalone Semtech driver while the Gen-4 LR20xx does not**
-([LR2021 G11](../lr2021/README.md)). Worth knowing when you are weighing ecosystem maturity.
-
----
-
-## 4. Caveats and gaps
-
-| # | Issue |
-|---|---|
-| **L1** | ⚠ **The datasheet was not obtained.** Salesforce-gated ([vendor guide §4](../../../vendors/semtech/README.md)). Every figure here is from the product page or RadioLib source. **No datasheet section is cited in this record** |
-| **L2** | ⚠ **The SF/BW restriction is the whole point of the part** (§1) and is invisible from the footprint |
-| **L3** | ⚠ **Bandwidths below 100 kHz are unavailable** — a restriction Semtech's marketing line does not mention (§1.2) |
-| **L4** | ⚠ **Set bandwidth before spreading factor** — the SF check reads the current BW (§1.2) |
-| **L5** | **Pin-to-pin compatibility makes silent substitution easy.** A vendor can change die between runs without changing the PCB |
-| **L6** | **Generation assignment is `inferred`**, not stated by Semtech (§0) |
-| **L7** | **Nothing measured**; no LLCC68 hardware in this knowledge base |
-| **L8** | **Introduction date not established.** `unresolved` |
-
----
-
-## 5. Used By
-
-**No board in this knowledge base uses an LLCC68.** Every LoRa-bearing device here carries an
-[SX1262](../sx1262/README.md) — which is precisely why this record exists: the two are pin-compatible
-and a future board could carry either.
-
----
-
-## 6. Local artifacts
-
-**None.** The datasheet is `blocked` and no mirror was located this pass. Recorded as a deliberate
-gap; `artifacts/` does not exist for this component.
-
-**How to fill it:** Digi-Key `mm.digikey.com/Volume0/opasdata/…` or Mouser `pdfDocs` with the
-**WhatsApp** User-Agent — [`vendors/semtech/README.md` §6](../../../vendors/semtech/README.md).
-⚠ Wayback has no LLCC68 PDF under `semtech.com`.
-
----
-
-## 7. Related components
-
-- [**Semtech SX1262**](../sx1262/README.md) — **the record to read.** Everything except §1 applies
-- [**Semtech SX1268**](../sx1268/README.md) — the other SX1262 sibling; a *band* restriction rather than an SF/BW one
-- [**Semtech LR2021**](../lr2021/README.md) — **Gen 4** · [**LR1121**](../lr1121/README.md) — **Gen 3** · [**SX1276**](../sx1276/README.md) — **Gen 1**
-- [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md) · [`guides/lora` §4](../../../guides/lora/README.md) — the existing SX1261/62/68 comparison · [`vendors/semtech/README.md`](../../../vendors/semtech/README.md) · [Components index](../../README.md)
-
----
-
-## 8. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | LoRa Connect for Smart Home (LLCC68) product page | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-connect/llcc68` | 2026-09-04 | §1, §1.1 — including *"Pin-to-pin compatible to SX1262"* and the SF/BW sentence |
-| C-2 | RadioLib `src/modules/LLCC68/LLCC68.cpp`, `LLCC68.h` | jgromes | community | source | `github.com/jgromes/RadioLib` | 2026-09-04 | §1.2 — the restriction as executable code; §1.4 |
-| C-3 | `LoRa-Net/llcc68_driver`, `one_channel_hub` | Semtech | primary | source | `github.com/LoRa-Net` | 2026-09-04 | §3; BSD-3-Clause-Clear, last push 2025-10-15 |
-| C-4 | Meshtastic `src/detect/LoRaRadioType.h` @ `v2.7.26.54e0d8d` | Meshtastic | community | source | `github.com/meshtastic/firmware` | 2026-09-04 | §3 |
-| C-5 | SX1262 component record | this repository | derived | record | [`components/semtech/sx1262/README.md`](../sx1262/README.md) | 2026-09-04 | §2 |
diff --git a/components/semtech/lr1121/README.md b/components/semtech/lr1121/README.md
deleted file mode 100644
index e4277a0..0000000
--- a/components/semtech/lr1121/README.md
+++ /dev/null
@@ -1,240 +0,0 @@
-# Semtech LR1121 — LoRa Connect™, the third-generation multi-band transceiver
-
-> **Lineage:** [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md)
-> — the four generations side by side. **Domain:** [`guides/lora`](../../../guides/lora/README.md).
-
-- **Category:** multi-band **LoRa / LR-FHSS / (G)FSK** half-duplex transceiver with an **AES-128 cryptographic engine and secure key store**
-- **Bands:** **150–960 MHz** (sub-GHz) **+ 2.4 GHz ISM + 2 GHz S-band + 1.55 GHz L-band** **[PP]**
-- **Package:** **QFN32, 5 × 5 mm** · **Order code `LR1121IMLTRT`**, Pb-free/RoHS **[PP]**
-- **Generation:** **3**, stated twice over — Semtech's product page opens *"The LR1121 is Semtech's **third generation** ultra-low power LoRa® transceiver"*, and `DS.LR20xx` §23.8 lists *"Generation 3 (Gen 3): LR1110, LR1120, **LR1121** - LoRa Edge™ - Added geolocation"* **[PP]**, **[DS20]**
-- **Research depth:** ⚠ **light record.** The LR1121 datasheet is behind Semtech's Salesforce gate and **was not obtained** (§5). Everything here comes from Semtech's product page, the Gen-4 datasheet's cross-generation statements, and driver source. **No LR1121 datasheet figure is reproduced here.**
-- **Retrieved:** 2026-09-04
-
----
-
-## Evidence labelling
-
-| Marker | Meaning |
-|---|---|
-| **[PP]** | Semtech LR1121 product page, `www.semtech.com/products/wireless-rf/lora-connect/lr1121`, retrieved 2026-09-04 |
-| **[DS20]** | `DS.LR20xx` Rev 2.1 — the **LR2021** datasheet, cited only where it makes cross-generation statements. [Held here](../lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) |
-| **[RL]** | RadioLib source, read live 2026-09-04 |
-| **[MT]** | Meshtastic firmware source, read live 2026-09-04 |
-| **[GH]** | `github.com/LoRa-Net`, read live 2026-09-04 |
-| **[3P]** | Third-party vendor page |
-| **[INF]** | Inference |
-
----
-
-## 1. Identity and what makes it odd
-
-**The LR1121 is the LR1120 with the geolocation front end removed.** That single sentence explains
-everything unusual about it, including why Semtech files it in a different product family from its
-own siblings.
-
-| | **LR1110** | **LR1120** | **LR1121** |
-|---|---|---|---|
-| Sub-GHz 150–960 MHz | ✅ | ✅ | ✅ |
-| 2.4 GHz ISM | ❌ | ✅ | ✅ |
-| Satellite | ❌ | 1.9–2.1 GHz S-band | **2 GHz S-band + 1.55 GHz L-band** |
-| **GNSS scanning** | ✅ | ✅ | ❌ |
-| **Wi-Fi passive scanning** | ✅ | ✅ | ❌ |
-| **AES-128 crypto + key store** | ✅ | ✅ | ✅ |
-| Semtech catalogue family | `lora-edge` | `lora-edge` | ⚠ **`lora-connect`** |
-
-**[PP]** for all rows. So the LR1121 is a *communications* part shelved with the communications
-parts, while carrying a Gen-3 part number. ⚠ **Consequence for enumeration: you will not find it by
-browsing `lora-edge`, and you will not find `lr1110`/`lr1120` by browsing `lora-connect`.** Use
-`sitemap-products.xml` — [`vendors/semtech/README.md` §2.2](../../../vendors/semtech/README.md).
-
----
-
-## 2. Capability, as Semtech states it
-
-Reproduced from the product page's own feature list **[PP]**:
-
-- Low-power high-sensitivity **LoRa/(G)FSK half-duplex** RF transceiver
-- Worldwide ISM support **150–960 MHz (sub-GHz) and 2.4 GHz, as well as 2 GHz S-Band and 1.55 GHz L-Band**
-- Low-noise-figure RX front end
-- **High-power PA path +22 dBm** in the sub-GHz band; **PA path up to +11.5 dBm** in the 2.4 GHz band
-- **LR-FHSS modulator**
-- *"Integrated PA regulator supply selector to simplify dual power +15/+22 dBm with one board implementation (sub-GHz)"*
-- *"Able to support world-wide multi-region BOM, the circuit adapts to matching network to satisfy regulatory limits"*
-- **"Fully compatible with SX1261/2/8 devices and the LoRaWAN standard, defined by the LoRa Alliance"**
-
-### 2.1 ⭐ The cryptographic engine — the reason to choose Gen 3
-
-**[PP]**, verbatim:
-
-> **Cryptographic Engine**
-> • Supports **AES-128** encryption/decryption based algorithms
-> • Handles device parameters such as **DevEUI and JoinEUI**, as defined by the LoRa Alliance
-> • **Protects confidential information such as encryption keys against unauthorized access**
-> • **Stores NwkKey, AppKey**, as defined in the LoRaWAN standard
-
-**No other generation has this.** Gen 1 and Gen 2 have no crypto engine at all, and **Gen 4 dropped
-it** — the string `AES` does not appear anywhere in the 243-page `DS.LR20xx` **[DS20]**, and
-Waveshare's own `Core1121` vs `Core2021` comparison marks AES-128 and secure key storage as present
-on the LR1121 and absent on the LR2021 **[3P]**.
-
-⚠ **This is the single most important fact on this page for anyone planning a migration.** If your
-LoRaWAN root keys currently live inside an LR1121, **the LR2021 has nowhere to put them** and you
-need MCU-side storage or an external secure element. Say so explicitly in your migration plan.
-
----
-
-## 3. ⚠ What "fully compatible with SX1261/2/8" does and does not mean
-
-Semtech's phrasing is on all three Gen-3 product pages and is easy to over-read.
-
-**It means:** the LoRa air interface and the LoRaWAN physical-layer profile interoperate. `DS.LR20xx`
-§23.8 backs this — *"all the LoRaWAN configurations are fully compatible between all four
-generations of LoRa radios"* **[DS20]**.
-
-**It does not mean:**
-
-| | SX1262 (Gen 2) | LR1121 (Gen 3) |
-|---|---|---|
-| Package | QFN **24**, 4 × 4 mm | QFN **32**, 5 × 5 mm |
-| Pin compatible | — | ❌ **No** |
-| Command set | SX126x | **LR11xx — different** |
-| Driver | `sx126x_driver` | **`SWDR001`, a separate repository** **[GH]** |
-| RadioLib module | `SX126x` | **`LR11x0`, a separate module** **[RL]** |
-| Firmware image in the part | none | ✅ **updatable program memory** — see §4 |
-
-**Long interleaver is a Gen-3/Gen-4-only LoRa option** **[DS20]** §23.8: turn it on and a Gen-1 or
-Gen-2 peer cannot decode the packet. That is the one air-interface asymmetry to watch.
-
----
-
-## 4. The firmware image — a Gen-3 concept Gen 2 does not have
-
-LR11xx parts carry updatable **program memory**, and Semtech ships tooling specifically for it:
-
-- `AN1200.57 LR11xx Program Memory Update` **[PP]** document list
-- **`LoRa-Net/SWTL001`** — *"Reference implementation of the LR11xx firmware update procedure"*, last push 2026-04-07 **[GH]**
-- **`LoRa-Net/radio_firmware_images`** — *"Firmware images for all flash-based Semtech products"*, last push 2026-04-07 **[GH]**
-
-This is the ancestor of the Gen-4 **PRAM** mechanism, but it is not the same thing: LR11xx program
-memory is *updated* and persists; Gen-4 PRAM is *re-uploaded at every cold start*
-([LR2021 §7.1](../lr2021/README.md)). ⚠ **A driver written for one will not do the other.**
-
----
-
-## 5. Documents — and why this record is light
-
-Enumerated from the product page 2026-09-04 **[PP]**. **None was retrieved**: every one is behind
-`semtech.my.salesforce.com/sfc/p/…`, which is `blocked` for automated clients
-([vendor guide §4](../../../vendors/semtech/README.md)). Recorded so the next reader does not
-re-enumerate.
-
-| Document | Notes |
-|---|---|
-| **LR1121 Datasheet** | The primary gap in this record |
-| **LR1121 User Manual** | ⚠ Note the LR11xx line splits datasheet from **user manual** — the SX126x line does not. Two documents to find, not one |
-| `AN1200.57` LR11xx Program Memory Update | §4 |
-| `AN1200.58` Long-Range FHSS Demo · `AN1200.64` LR-FHSS System Performance · `AN1200.81` LR-FHSS Doppler Immunity | LR-FHSS trio |
-| `AN1200.59` Selecting the Optimal Reference Clock · `AN1200.66` PCB Design Guidelines | shared with the LR2021 page, different tokens |
-| `AN1200.62` FCC Pre-Compliance testing of LoRaWAN Modules | |
-| `AN1200.73` SX126x/LR11xx **SigFox** Modulation | how Gen 2/3 do BPSK without a BPSK modem — the LR2021 has one natively |
-| `AN1200.76` LR11xx **IPD Reference Design** · `AN1200.80` LoRa Modem Doppler Immunity | |
-| `AN1200.92` Modem-E Evaluation Guide · **LoRa Basics Modem-E V2.0 Reference Manual** | the Modem-E firmware variant |
-| `AN1200.94` / `AN1200.96` One-Channel LoRa Hub | |
-| Design files: `LR1121DVK1TGKS` @490 MHz · `LR1121DVK1TxKS` @868/915 MHz | |
-| Module design files: `LR1121MB2THDAS`, `LR1121MB2XHDAS` (+22 dBm, 0201, XTAL), `LR1121MB2XLDAS` (+14 dBm) | ⚠ two are titled *"not purchasable"* |
-| `LRDVK17INTERFACE` LoRa Shield → EFR32 interface board UG + production files | |
-
-**Evaluation kits** **[PP]**: `LR1121DVK1TBKS` (EU 868), `LR1121DVK1TCKS` (NA 915),
-`LR1121DVK1TGKS` (CN 490), `LR1121ED1THDAS`.
-
-⚠ **The Wayback Machine cannot help.** The CDX index for `semtech.com` contains **zero LR11xx PDFs**
-— these documents have only ever lived behind the Salesforce shell
-([vendor guide §5.2](../../../vendors/semtech/README.md)). **There is no archive route to an LR11xx
-datasheet.** Negative result, `executed-success` for the search.
-
----
-
-## 6. Software support
-
-| Stack | Status |
-|---|---|
-| **RadioLib** | ✅ `src/modules/LR11x0`, with `LR1110`, `LR1120` and `LR1121` classes. MIT **[RL]** |
-| **Semtech `SWDR001`** | ✅ *"Driver for LR11xx chip (LR1110 / LR1120 / LR1121)"*, last push 2026-04-07 **[GH]** |
-| **`SWSD003`** | LR11xx **and** SX126x SDK — the two generations share an SDK, which the LR20xx does not join **[GH]** |
-| **`SWSD006`** | LR11xx multi-stack SDK for nRF52840, Apache-2.0 **[GH]** |
-| **`SWDR006` / `SWDR007`** | LR11xx **Amazon Sidewalk** drivers for nRF52840 and Silicon Labs EFR32 **[GH]** |
-| **`lr11xx_ranging_demo`** | RTToF ranging demo **[GH]** |
-| **`lr1121_modemE_driver`** (`SWDR009`) | Modem-E firmware variant driver **[GH]** |
-| **USP** | "buildable" on LR11xx shields — not Semtech-validated **[GH]** |
-| **Meshtastic** | ✅ `LR1121Interface` alongside `LR1110Interface`, `LR1120Interface` and a shared `LR11x0Interface`; `LR1121_RADIO` in `LoRaRadioType`. Present in **v2.7.26 stable** — unlike the LR2021 **[MT]** |
-| **Zephyr** | via `usp_zephyr` / `LBM_Zephyr` (Apache-2.0) **[GH]** |
-| Linux kernel | ❌ none — userspace SPI only. Negative result |
-
-**The LR11xx has markedly better tooling than the LR20xx**: a standalone driver, two SDKs, two
-Sidewalk ports, a ranging demo, and stable-release Meshtastic support. That is what four extra
-years buys.
-
----
-
-## 7. Caveats and gaps
-
-| # | Issue |
-|---|---|
-| **L1** | ⚠ **The datasheet was not obtained** (§5). Every electrical claim here is from a marketing feature list, and no sensitivity, current or timing figure is reproduced. This record is deliberately thin rather than confidently wrong |
-| **L2** | ⚠ **The LR1121 has no GNSS and no Wi-Fi scanner** despite being "LoRa Edge generation". Assuming otherwise from the part number is the standard error |
-| **L3** | ⚠ **Semtech's own page prints the LR1120 order code as `LR1120IMLRT`**, missing the `T` that `LR1110IMLTRT` and `LR1121IMLTRT` both carry. Almost certainly a typo — **confirm before ordering**. `unresolved` **[PP]** |
-| **L4** | **"Fully compatible with SX1261/2/8" is an air-interface claim only** (§3) |
-| **L5** | **Long interleaver excludes Gen-1/Gen-2 peers** **[DS20]** §23.8 |
-| **L6** | **Introduction date not established.** "2020" for the LR1110 is widely repeated but no Semtech-dated source was retrieved and no LR11xx PDF exists in the Wayback index. `unresolved` |
-| **L7** | **Nothing measured.** No hardware, no teardown, no community measurement gathered for this part |
-
----
-
-## 8. Used By
-
-**No board in this knowledge base uses an LR1121.** Every LoRa-bearing device documented here
-carries a Gen-2 [SX1262](../sx1262/README.md).
-
-Boards that do, so the record is navigable: **LilyGo T3-S3 LR1121** (`lilygo.cc/products/t3-s3-lr1121`,
-cited by community discussion), **Waveshare `Core1121-XF`** **[3P]**, and Meshtastic's LR1121
-variants **[MT]**.
-
----
-
-## 9. Local artifacts
-
-**None.** The datasheet and user manual are `blocked` (§5) and no mirror was located this pass.
-⚠ Recorded as a deliberate gap, not an oversight: `artifacts/` does not exist for this component
-because nothing was obtained.
-
-**How to fill it**, in order of likelihood: Digi-Key `mm.digikey.com/Volume0/opasdata/…` (needs the
-exact opaque path from a Digi-Key product page); Mouser `www.mouser.com/pdfDocs/<id>LR1121…pdf` with
-the **WhatsApp** User-Agent; a board-vendor mirror (Waveshare and LilyGo both ship LR1121 modules).
-Method: [`vendors/semtech/README.md` §6](../../../vendors/semtech/README.md).
-
----
-
-## 10. Related components
-
-- [**Semtech LR1110 / LR1120**](../lr11x0/README.md) — the geolocation siblings this part is derived from
-- [**Semtech LR2021**](../lr2021/README.md) — **Gen 4**, and what you lose by moving to it
-- [**Semtech SX1262**](../sx1262/README.md) — **Gen 2**, the "fully compatible" claim's referent
-- [**Semtech SX1276**](../sx1276/README.md) — **Gen 1**
-- [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md)
-- [`vendors/semtech/README.md`](../../../vendors/semtech/README.md)
-- [Components index](../../README.md)
-
----
-
-## 11. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| L-1 | LoRa Connect LR1121 product page | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-connect/lr1121` | 2026-09-04 | §1, §2, §5 — including the **"third generation"** wording |
-| L-2 | `DS.LR20xx` Rev 2.1 §23.8 | Semtech via Digi-Key | authorized mirror | datasheet | [held here](../lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) | 2026-09-04 | §1 generation placement; §3 interoperability |
-| L-3 | LR1110 / LR1120 product pages | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-edge/lr111{0,2}0` | 2026-09-04 | §1 comparison table; L3 |
-| L-4 | `LoRa-Net` org listing | Semtech | primary | source | `api.github.com/orgs/LoRa-Net/repos` | 2026-09-04 | §4, §6 |
-| L-5 | RadioLib `src/modules/LR11x0` | jgromes | community | source | `github.com/jgromes/RadioLib` | 2026-09-04 | §3, §6 |
-| L-6 | Meshtastic `src/mesh/LR11*`, `LoRaRadioType.h` @ `v2.7.26.54e0d8d` | Meshtastic | community | source | `github.com/meshtastic/firmware` | 2026-09-04 | §6 |
-| L-7 | `Core2021-XF` comparison table (`Core1121-XF` column) | Waveshare | primary | store listing | `www.waveshare.com/Core2021-XF.htm` | 2026-09-04 | §2.1 — independent confirmation of the crypto asymmetry |
-| L-8 | Wayback CDX index for `semtech.com` PDFs | Internet Archive | archive | index | `web.archive.org/cdx/search/cdx?url=semtech.com/*&matchType=domain&filter=mimetype:application/pdf` | 2026-09-04 | §5 — **negative result: zero LR11xx PDFs** |
diff --git a/components/semtech/lr11x0/README.md b/components/semtech/lr11x0/README.md
deleted file mode 100644
index e605714..0000000
--- a/components/semtech/lr11x0/README.md
+++ /dev/null
@@ -1,231 +0,0 @@
-# Semtech LR1110 and LR1120 — LoRa Edge™, the third-generation geolocation transceivers
-
-> **Lineage:** [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md).
-> **Sibling record:** [`lr1121`](../lr1121/README.md) — the same generation with the geolocation
-> front end removed, and the deeper of the two records.
-
-- **Category:** **LoRa / LR-FHSS / (G)FSK** transceiver **+ multi-constellation GNSS scanner + passive Wi-Fi AP-MAC scanner + AES-128 crypto engine**
-- **Package:** **QFN32, 5 × 5 mm** both parts **[PP]**
-- **Order codes:** `LR1110IMLTRT` · `LR1120IMLRT` ⚠ (see G3)
-- **Generation:** **3.** `DS.LR20xx` §23.8: *"Generation 3 (Gen 3): **LR1110, LR1120**, LR1121 - LoRa Edge™ - Added geolocation"* **[DS20]**
-- **Research depth:** ⚠ **light record.** Neither datasheet was obtained — both are behind Semtech's Salesforce gate, and **the Wayback Machine has no LR11xx PDF at all**. Content here is Semtech's own feature lists, the Gen-4 datasheet's cross-generation statements, and driver source.
-- **Retrieved:** 2026-09-04
-
-**Why one record for two parts:** they share a package, an order-code shape, a command set, a driver
-(`SWDR001`), a RadioLib module (`LR11x0`) and a feature list. The LR1120 is the LR1110 with bands
-added. Splitting them would duplicate nine sections to change three rows.
-
----
-
-## Evidence labelling
-
-**[PP]** Semtech product pages (`…/lora-edge/lr1110`, `…/lora-edge/lr1120`), retrieved 2026-09-04 ·
-**[DS20]** `DS.LR20xx` Rev 2.1, [held here](../lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) ·
-**[GH]** `github.com/LoRa-Net`, read live · **[RL]** RadioLib · **[MT]** Meshtastic firmware ·
-**[INF]** inference.
-
----
-
-## 1. The two parts
-
-| | **LR1110** | **LR1120** |
-|---|---|---|
-| Sub-GHz | **150–960 MHz** | **150–960 MHz** |
-| 2.4 GHz ISM | ❌ | ✅ |
-| Satellite | ❌ | **1.9–2.1 GHz S-band** |
-| Sub-GHz max Tx | **+22 dBm** high-power path, **+15 dBm** high-efficiency path | **+22 dBm** |
-| 2.4 GHz max Tx | — | **+11.5 dBm** |
-| **GNSS (GPS/BeiDou) low-power scanning** | ✅ | ✅ |
-| **802.11 b/g/n Wi-Fi ultra-low-power passive scanning** | ✅ | ✅ |
-| **AES-128 crypto engine + secure key store** | ✅ | ✅ |
-| LR-FHSS modulator | ✅ | ✅ |
-| **Synthesiser range** | ⚠ **150–2700 MHz continuous** | not separately stated |
-| **RX ADC** | **up to 24 MHz DSB** | not separately stated |
-| Package / order code | QFN32 5×5 · `LR1110IMLTRT` | QFN32 5×5 · `LR1120IMLRT` ⚠ |
-
-All rows **[PP]**.
-
-⚠ **The LR1110's "150–2700 MHz continuous frequency synthesizer range" is not a communications
-band.** It is the front end's tuning range, and it exists to let the same silicon land on GPS L1
-(1575.42 MHz) and Wi-Fi (2.4 GHz) for *scanning*. Reading it as "the LR1110 can transmit at 2.4 GHz"
-is wrong — the LR1110 has no 2.4 GHz PA path; that is exactly what the LR1120 adds. **[INF]**, but
-strongly: Semtech lists the synthesiser range under *"Multi-Purpose Radio Front-End Targeting
-Geolocation Purposes"*, not under the transceiver features.
-
----
-
-## 2. What the geolocation front end actually is
-
-Semtech's own framing **[PP]**:
-
-> Ultra-low power platform that integrates a LoRa® transceiver, long range FHSS modulator,
-> **multi-constellation scanner**, and **passive Wi-Fi AP MAC address scanner** targeting asset
-> management applications. The LR1110 solution utilizes Semtech's cloud-based geolocation services
-> from Semtech's partners **to significantly reduce power consumption by determining asset location
-> in a cloud solver**.
-
-**This is the defining architectural idea of Gen 3, and it is easy to miss.** The chip does **not**
-compute a position. It captures a short burst of GNSS pseudorange data or a list of nearby Wi-Fi AP
-MAC addresses, and **ships the raw scan over LoRaWAN to a cloud solver** which returns coordinates.
-A conventional GNSS receiver has to stay powered long enough to acquire, track and solve; this does
-not.
-
-⚠ **Two consequences that belong in any evaluation:**
-
-1. **It creates a cloud dependency for a core function.** No solver, no position. Semtech's
-   `SWNW001` (*"Example code to integrate LoRa Edge with cloud solvers"*, MIT) and
-   `node-red-contrib-loracloud-utils` exist precisely to wire this up **[GH]**. If the solver
-   service changes terms or disappears, the scanner is a data source with no consumer.
-2. **Wi-Fi scanning is passive AP-MAC harvesting.** That is a privacy-relevant capability and, in
-   some jurisdictions, a regulated one. Worth a deliberate decision, not an accident of part choice.
-
-Also in Gen 3 and worth noting: **RTToF (round-trip time-of-flight) ranging** — `AN1200.78 LR1110
-Round-Trip-Time-of-flight Application Note` and the `lr11xx_ranging_demo` repository
-(*"a fully featured ranging demonstration featuring communication and distance measurement phases
-and the statistical post processing needed to yield accurate results"*) **[GH]**. Gen 4 keeps and
-extends this as `RTToF` §10 of `DS.LR20xx` **[DS20]**.
-
----
-
-## 3. The crypto engine
-
-Identical wording on both product pages **[PP]**:
-
-> **Cryptographic Engine** — Hardware support for **AES-128** encryption/decryption based
-> algorithms · Handling device parameters such as **DevEUI and JoinEUI** · **Protects confidential
-> information such as encryption keys against unauthorized access** · **Stores NwkKey, AppKey**
-
-Gen 1 and Gen 2 have nothing comparable, and **Gen 4 dropped it** — see
-[`lr1121` §2.1](../lr1121/README.md) and
-[`lora-radio-generations` §5.3](../../../guides/hardware/lora-radio-generations.md).
-
----
-
-## 4. Compatibility with the rest of the lineage
-
-Both pages carry the same claim: ***"Fully compatible with SX1261/2/8 devices and the LoRaWAN®
-standard, defined by the LoRa Alliance®"*** **[PP]**. Read it as **air-interface and LoRaWAN-profile**
-compatibility only — the parts are not pin-compatible with an SX1262 (QFN32 5 × 5 vs QFN24 4 × 4),
-the command set differs, and the driver is a different repository. The full unpacking is in
-[`lr1121` §3](../lr1121/README.md).
-
-**Long interleaver** is available on Gen 3 and Gen 4 and on nothing older **[DS20]** §23.8 — enable
-it and Gen-1/Gen-2 peers cannot decode.
-
----
-
-## 5. Documents — enumerated, none retrieved
-
-All behind `semtech.my.salesforce.com/sfc/p/…`, `blocked`
-([vendor guide §4](../../../vendors/semtech/README.md)). Recorded so the next reader does not repeat
-the enumeration.
-
-**LR1110** **[PP]**: Datasheet · `AN1200.56` LR1110 evaluation kit · `AN1200.57` LR11xx Program
-Memory Update · `AN1200.58` LR-FHSS Demo Code · `AN1200.59` Selecting the Optimal Reference Clock ·
-`AN1200.62` FCC Pre-Compliance testing · `AN1200.64` LR-FHSS System Performance · `AN1200.66` PCB
-Design Guidelines · **`AN1200.69` GNSS Antenna** · **`AN1200.70` LoRa Edge Advanced GNSS Scan
-Performance Overview** · `AN1200.73` SX126x/LR11xx SigFox Modulation · **`AN1200.74` LoRa Edge Clock
-Requirements** · `AN1200.76` LR11xx IPD Reference Design · **`AN1200.78` LR1110 RTToF** ·
-`AN1200.80` LoRa Modem Doppler Immunity.
-
-⚠ **`AN1200.69` (GNSS antenna) and `AN1200.74` (clock requirements) have no Gen-2 or Gen-4
-equivalent.** A GNSS-scanning design has antenna and reference-clock constraints a plain LoRa design
-does not, and those two documents are where they live. Do not start an LR1110/LR1120 board without
-them.
-
-**Evaluation kits and reference designs** **[PP]**: `LR1110DVK1TBKS/TCKS/TGKS/TPKS`,
-`LR1110MB1LBKS`, `LR1110MB1LCKS`, `LR1110MB1IPDT1DKS`, and the **tracker reference designs**
-`LR1110TRK1BKS` (+ `-IN`), `LR1110TRK1CKS` (+ `-AU`, `-JP`, `-KR`); `LR1120DVK1TBKS/TCKS/TGKS/TPKS`,
-`LR1120MB1IPDT1DKS`; `LRDVK17INTERFACE`. ⚠ **Note the regional tracker SKUs** — `-AU`, `-JP`, `-KR`,
-`-IN` — a level of per-region productisation Gen 4 explicitly set out to eliminate with its
-single-SKU front end.
-
-⚠ **No archive route exists.** The Wayback CDX index for `semtech.com` contains **zero LR11xx PDFs**;
-these documents have only ever lived behind the Salesforce shell. Negative result, verified.
-
----
-
-## 6. Software support
-
-| Repo / stack | What | Licence | Last push |
-|---|---|---|---|
-| **`SWDR001`** | *"Driver for LR11xx chip (LR1110 / LR1120 / LR1121)"* — the reference driver | NOASSERTION | 2026-04-07 |
-| **`SWTL001`** | LR11xx **firmware update** procedure | NOASSERTION | 2026-04-07 |
-| **`radio_firmware_images`** | *"Firmware images for all flash-based Semtech products"* | — | 2026-04-07 |
-| **`SWSD003`** | LR11xx **and** SX126x SDK | NOASSERTION | 2025-10-01 |
-| **`SWSD006`** | LR11xx multi-stack SDK for nRF52840 | Apache-2.0 | 2025-02-12 |
-| **`SWSD004`** / `lora_edge_tracker_ref_design` | Tracker reference-design applications | NOASSERTION | 2025-10-27 |
-| **`SWDR006` / `SWDR007`** | LR11xx **Amazon Sidewalk** drivers (nRF52840 / SiLabs EFR32) | NOASSERTION | 2024-07-18 / 2024-08-22 |
-| **`lr11xx_ranging_demo`** | RTToF demonstration | NOASSERTION | 2025-04-02 |
-| **`SWNW001`** | *"Example code to integrate LoRa Edge with cloud solvers"* | **MIT** | 2025-07-15 |
-| `node-red-contrib-loracloud-utils` | Node-RED LoRa Cloud integration | — | 2023-07-18 |
-| `lr1110_driver` | **Superseded** by `SWDR001` | BSD-3-Clause-Clear | 2022-04-13 |
-| `lr1110_evk_demo_app` | EVK demo | — | 2021-11-03 |
-| **`LoRa_Basics_ModemE`**, `ModemE_command_interpreter`, `ModemE_application_examples`, `lr1121_modemE_driver` | The **Modem-E** firmware variant — LoRaWAN stack running *inside* the radio | — | 2024–2026 |
-| **RadioLib** | `src/modules/LR11x0` with `LR1110`, `LR1120`, `LR1121` classes | MIT | current |
-| **Meshtastic** | `LR1110Interface`, `LR1120Interface`, shared `LR11x0Interface`; `LR1110_RADIO` / `LR1120_RADIO` in `LoRaRadioType`, present in **v2.7.26 stable** | GPL-3.0 | current |
-
-All **[GH]**, **[RL]**, **[MT]**, read 2026-09-04.
-
-**Modem-E deserves a sentence**, because it has no Gen-4 counterpart: it is a Semtech firmware image
-that runs the LoRaWAN stack *on the radio*, so the host MCU speaks a high-level command interface
-instead of a PHY driver. Four repositories support it. If you have seen "LoRa Basics Modem-E" and
-wondered where it fits, it is a Gen-3 delivery mode.
-
----
-
-## 7. Caveats and gaps
-
-| # | Issue |
-|---|---|
-| **G1** | ⚠ **Neither datasheet was obtained** (§5), and **no archive route exists**. Every claim here is from a marketing feature list. No electrical figure is reproduced |
-| **G2** | ⚠ **Geolocation is cloud-dependent by design** (§2). The chip scans; a solver locates |
-| **G3** | ⚠ **`LR1120IMLRT` on Semtech's own page is missing a `T`** relative to `LR1110IMLTRT`/`LR1121IMLTRT`. Probable typo — verify before ordering. `unresolved` |
-| **G4** | **The LR1110 cannot transmit at 2.4 GHz** despite a 150–2700 MHz synthesiser. The range is for scanning (§1) |
-| **G5** | **Passive Wi-Fi MAC scanning is a privacy-relevant capability**, and in some jurisdictions a regulated one. Decide deliberately |
-| **G6** | **Introduction date not established.** "2020" is widely repeated; no Semtech-dated source retrieved. `unresolved` |
-| **G7** | ⚠ **`lr1110_driver` is superseded by `SWDR001`** but is still present, still findable, and still the top search hit for "lr1110 driver". Last push 2022-04-13 |
-| **G8** | **Nothing measured**; no hardware, teardown or community measurement gathered |
-| **G9** | ⚠ **Regional tracker SKUs (`-AU`, `-JP`, `-KR`, `-IN`) mean the reference design is not one design.** Do not assume a `TRK1CKS` document applies to a `TRK1CKS-JP` |
-
----
-
-## 8. Used By
-
-**No board in this knowledge base uses an LR1110 or LR1120.** Boards that do, for navigability:
-Semtech's own **LoRa Edge Tracker reference design** (`LR1110TRK1*`, with regional variants), and
-Meshtastic's LR1110/LR1120 variants **[MT]**.
-
----
-
-## 9. Local artifacts
-
-**None** — see §5 and G1. `artifacts/` does not exist for this component because nothing was
-obtained. Recorded as a deliberate gap.
-
-**How to fill it:** Digi-Key or Mouser mirror, per
-[`vendors/semtech/README.md` §6](../../../vendors/semtech/README.md). ⚠ Wayback will not work.
-
----
-
-## 10. Related components
-
-- [**Semtech LR1121**](../lr1121/README.md) — same generation, no scanners, filed under `lora-connect`
-- [**Semtech LR2021**](../lr2021/README.md) — **Gen 4**; ⚠ **no GNSS, no Wi-Fi scanning, no crypto engine**
-- [**Semtech SX1262**](../sx1262/README.md) — **Gen 2**
-- [**Semtech SX1276**](../sx1276/README.md) — **Gen 1**
-- [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md) · [`vendors/semtech/README.md`](../../../vendors/semtech/README.md) · [Components index](../../README.md)
-
----
-
-## 11. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| E-1 | LoRa Edge™ LR1110 product page | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-edge/lr1110` | 2026-09-04 | §1, §2, §3, §5 |
-| E-2 | LoRa Edge™ LR1120 product page | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-edge/lr1120` | 2026-09-04 | §1, §3, §5 |
-| E-3 | `DS.LR20xx` Rev 2.1 §23.8 | Semtech via Digi-Key | authorized mirror | datasheet | [held here](../lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) | 2026-09-04 | generation placement; §4 |
-| E-4 | Semtech product sitemap | Semtech | primary | sitemap | `www.semtech.com/sitemap-products.xml` | 2026-09-04 | §5 EVK/reference-design SKU list |
-| E-5 | `LoRa-Net` org listing | Semtech | primary | source | `api.github.com/orgs/LoRa-Net/repos` | 2026-09-04 | §6 |
-| E-6 | RadioLib · Meshtastic firmware | jgromes · Meshtastic | community | source | GitHub | 2026-09-04 | §6 |
-| E-7 | Wayback CDX index for `semtech.com` PDFs | Internet Archive | archive | index | `web.archive.org/cdx/search/cdx?url=semtech.com/*&matchType=domain&filter=mimetype:application/pdf` | 2026-09-04 | §5 — **negative result: zero LR11xx PDFs** |
diff --git a/components/semtech/lr2021/README.md b/components/semtech/lr2021/README.md
deleted file mode 100644
index 64dd1ba..0000000
--- a/components/semtech/lr2021/README.md
+++ /dev/null
@@ -1,768 +0,0 @@
-# Semtech LR2021 — LoRa Plus™, the fourth-generation LoRa transceiver
-
-> **Cross-cutting guide:** [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md)
-> — the four generations side by side, and what breaks when you move between them.
-> **Domain guide:** [`guides/lora`](../../../guides/lora/README.md) — LoRa vs LoRaWAN vs Meshtastic,
-> airtime/duty-cycle arithmetic, band plans as a legal constraint. This record covers the part.
-
-- **Category:** multi-band, multi-PHY **LoRa / LR-FHSS / FLRC / (G)FSK / OOK / BPSK / O-QPSK / BLE-PHY / Z-Wave** transceiver, SPI-controlled
-- **Bands:** **150–960 MHz** *and* **1.5–2.5 GHz** (2.4 GHz ISM plus licensed L/S-band) **[DS]**
-- **Package:** **QFN 32, 5 × 5 mm**, Pb-free/halogen-free, RoHS/WEEE **[DS]**
-- **Order code:** `LR2021IMLTRT` · tape & reel · MOQ 3 000 **[DS]**
-- **Family:** first silicon in Semtech's **LoRa Plus™** line, alongside `LR2022` and `LR2012` (§1.2)
-- **Research status:** **Rev 2.1 of the datasheet is retained and was read** (`DS.LR20xx`, 243 pp). **Rev 1.1 is also retained**, archived, because the two differ in substance (§14). The chip has never been seen or measured here — every electrical figure below is a manufacturer specification.
-- **Retrieved:** 2026-09-04
-
-**This is the part the phrase "the new 4th gen LoRa chip" refers to, and the label is Semtech's
-own, not community shorthand.** Two independent primary sources say so in as many words — see §1.1.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | `artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf` — `DS.LR20xx`, Final Datasheet **Rev. 2.1**, `13/04/26`, 243 pp, with section/table reference | `not-tested` — manufacturer specification reproduced, nothing measured |
-| **[DS1.1]** | The superseded `DS.LR2021` **Rev. 1.1**, `10/14/25`, 236 pp — [archived](artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md) | `not-tested`; cited only where the two revisions disagree |
-| **[DRV]** | Semtech's own `lr20xx_driver` **v2.0.2** inside `LoRa-Net/usp` @ `512a095e303872f900021361a619b7b1e6e29469`, retained as `artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz` | `executed-success` for the read; `not-tested` on hardware |
-| **[RL]** | RadioLib source read live through the GitHub API at a named tag/commit | `executed-success` for the read; `inferred` for behaviour |
-| **[MT]** | Meshtastic firmware source/PR read live through the GitHub API | `executed-success` for the read |
-| **[DOC]** | `www.semtech.com` / vendor product page, retrieved 2026-09-04 | `not-tested` |
-| **[COM]** | Community report — always labelled firsthand-measurement / firsthand-ownership / informed-interpretation / hearsay in [`projects-and-community.md`](projects-and-community.md) | non-authoritative |
-| **[INF]** | Inference | `inferred` |
-
-**Nothing in this record was verified on hardware by this pass.** No opcode, register, pin or
-current figure below was guessed; each is transcribed from a cited document or source file.
-
-**Text-layer validation.** `pypdf` extraction of Rev 2.1 was checked against the document's own
-running footer (`LR2021/LR2022/LR2012 · Final Datasheet Rev. 2.1 · DS.LR20xx 13/04/26 · N of 243`)
-on every quoted page, and against the page count reported by the PDF page tree (243). ⚠ **The
-micro sign is dropped by the extractor** — sleep currents render as bare `A` where the document
-says `µA`, and PA ramp times as `s` where the document says `µs`. Both are corrected below from
-context and from the front-page summary (`470nA` sleep). ⚠ **Figures are vector art with no text
-layer at all**, so the pin-out diagram, the SIMO/LDO connection drawings and the package marking
-drawing extract as bare pin-name word lists or as nothing. Values taken from figures are marked.
-
----
-
-## 1. Identity and capability
-
-### 1.1 "Fourth generation" is Semtech's word — the evidence
-
-The user-facing question this record exists to answer is *what is the 4th generation LoRa chip*.
-Three primary sources, two of them inside the datasheet itself:
-
-| # | Source | Exact wording |
-|---|---|---|
-| 1 | Datasheet **front page**, feature block **[DS]** p. 1 | **"Generation 4 LoRa® IP"** |
-| 2 | Datasheet **General Description** **[DS]** p. 2 | "The LR2021 is Semtech's **first chip in the LoRa Plus family**. Incorporating a **fourth-generation LoRa IP** …" |
-| 3 | Semtech product page `<title>` **[DOC]** | "LoRa Plus™ LR2021 \| **Fourth-generation LoRa® IP** for Fast Long Range Communication (FLRC) \| Semtech" |
-
-And the numbering is not left implicit. **[DS]** **§23.8 "Compatibility of Generation 1-4 LoRa
-Radios"** enumerates the whole lineage verbatim:
-
-> Semtech has developed four generations of LoRa radios:
-> • Generation 1 (Gen 1): SX1272, SX1276 - First LoRa chips (2013)
-> • Generation 2 (Gen 2): SX1261, SX1262, SX1280 - Enhanced performance and efficiency
-> • Generation 3 (Gen 3): LR1110, LR1120, LR1121 - LoRa Edge™ - Added geolocation
-> • Generation 4 (Gen 4): LR2021 LoRa Plus™ Multi-band, and multi-protocol
-
-The same list, word for word, appears in **[DS1.1]** §23.7 — so it is **corroborated across two
-independent document revisions six months apart**, not a one-off editorial line.
-
-Four consequences worth stating plainly, because each rules something out:
-
-- **SX1280/SX1281 (2.4 GHz LoRa) is Gen 2, not a generation of its own.** Semtech puts it in the
-  same bullet as the SX1261/SX1262. The 2.4 GHz band is a band, not a generation.
-- **LR-FHSS is not a generation either.** It is a modulation, available on SX126x (Gen 2), LR11xx
-  (Gen 3) and LR20xx (Gen 4) alike — the patent notice in **[DS]** p. 3 lists
-  `SX1261, SX1262, SX1268, LR1110, LR1120, LR1121, LR2012, LR2021, LR2022` as the parts whose
-  purchase conveys LR-FHSS patent rights, which is the clearest available statement of which
-  silicon carries it.
-- **SX1268 and LLCC68 are not named** in §23.8. They are SX1262 siblings and inherit Gen 2 by
-  family, not by enumeration — see [`components/semtech/sx1268`](../sx1268/README.md) and
-  [`components/semtech/llcc68`](../llcc68/README.md). **[INF]**
-- **SX1277/78/79 and SX1273 are not named either**, for the same reason: §23.8 names one
-  representative per generation, not a full part list.
-
-⚠ **The LR2022 and LR2012 are also Gen 4 silicon** and §23.8 does not mention them, because §23.8
-was written for Rev 1.1 when the LR2021 was the only member. Read it as a generation list, not a
-part list. **[INF]**
-
-### 1.2 Three parts, one datasheet, and the differences are exclusions
-
-`DS.LR20xx` Rev 2.1 documents **LR2021, LR2022 and LR2012 together**, and warns explicitly that
-"product features unavailable in the LR2022 and LR2012 are described in this document but are not
-available in the corresponding IC" **[DS]** p. 2. That is the same trap as the SX1261/SX1262
-datasheet — *a claim copied from the wrong part is the most common error made with this document.*
-
-| | **LR2021** | **LR2022** | **LR2012** |
-|---|---|---|---|
-| Order code **[DS]** | `LR2021IMLTRT` | `LR2022IMLTRT` | `LR2012IMLTRT` |
-| Sub-GHz 150–960 MHz | ✅ | ✅ | ✅ |
-| 1.5–2.5 GHz (HF path) | ✅ | ✅ | ❌ — `RFI_HF`/`RFO_HF` are **NC** |
-| LoRa, LR-FHSS, (G)FSK, OOK, BPSK, WM-Bus, Wi-SUN | ✅ | ✅ | ✅ |
-| **FLRC** | ✅ | ❌ | ❌ |
-| **O-QPSK (802.15.4 / Thread / Zigbee)** | ✅ | ❌ | ❌ |
-| **Z-Wave / Z-Wave LR** | ✅ | ❌ | ❌ |
-| **Bluetooth LE PHY** | ✅ | ✅ | ❌ |
-| Semtech's one-line summary **[DS]** | Full feature set, dual band | "Same as LR2021, excluding support for FLRC, O-QPSK (802.15.4), and Z-Wave" | "Sub-GHz only, excluding support for FLRC, O-QPSK (802.15.4), Bluetooth LE, and Z-Wave" |
-
-**Everything below describes the LR2021** unless a row says otherwise. `LR20xx` marks a statement
-that holds for all three; the datasheet uses that convention in its own section headings and this
-record follows it.
-
-### 1.3 What it actually is
-
-A single-SKU, switch-less-front-end, dual-band software-defined radio that happens to speak LoRa.
-**[DS]** p. 1–2 and **[DOC]**:
-
-- **Modulations:** LoRa (SF5–SF12), LR-FHSS, (G)FSK, GMSK/MSK, OOK, (D)BPSK, O-QPSK DSSS, FLRC,
-  Bluetooth LE PHY (1M/2M/Coded 500k/125k)
-- **Protocol PHY compatibility** claimed with third-party stacks: LoRaWAN, **Amazon Sidewalk**,
-  **Sigfox** BPSK, **Wi-SUN** FSK, **Wireless M-Bus** (device *and* collector), **Z-Wave / Z-Wave LR**,
-  **802.15.4 Thread/Zigbee**, Bluetooth LE 5.0 PHY
-- **Terrestrial and NTN/SATCOM**, the latter in the licensed L/S-band — this is what the
-  "1.5–2.5 GHz" figure is for, and it is the headline reason the part exists
-- **RTToF (round-trip time-of-flight) ranging engine** — §10, inherited in spirit from the SX1280
-- **Dedicated packet handlers per PHY** in hardware, not a generic FIFO with host-side framing
-
-Semtech's positioning line, **[DOC]**: *"multi-region, single-SKU design, reducing external BOM
-costs, PCB footprint, and power consumption, while offering superior performance compared to
-previous LoRa transceivers."* Take "single-SKU" literally — the multi-region front end and the
-absence of an external RF switch are the actual BOM argument, not marketing filler (§5.3).
-
-⚠ **The chip's band coverage is not a board's band coverage.** 150–960 MHz continuous is a
-synthesiser capability; every real module narrows it with a matching network and antenna. The
-Waveshare `Core2021` ships as **three separate SKUs** (`-LF`, `-HF`, `-XF`) for exactly this
-reason **[DOC]**.
-
----
-
-## 2. Pin table
-
-QFN32 + exposed pad. Transcribed from **[DS]** Table 2-1 (a real table, not the figure).
-
-| Pin | LR2021 / LR2022 | LR2012 | Description |
-|---:|---|---|---|
-| 0 | `GND` | `GND` | Exposed ground pad |
-| 1 | `VR_PA` | `VR_PA` | Regulated supply for all power amplifiers |
-| 2 | `VPAX2` | `VPAX2` | Regulated supply for the PA regulator |
-| 3 | `NTC` | `NTC` | NTC thermistor connection (XTAL temperature compensation, §6.2) |
-| 4 | `XTA` | `XTA` | 32 MHz crystal — **also the external-reference / TCXO input** |
-| 5 | `XTB` | `XTB` | 32 MHz crystal; **leave unconnected when a TCXO is used** |
-| 6 | `VTCXO`/`VNTC` | `VTCXO`/`VNTC` | Regulated TCXO supply **or** NTC supply — one pin, two jobs |
-| 7–11 | `DIO11`…`DIO7` | idem | Multi-purpose digital I/O |
-| 12 | `VDCC1` | `VDCC1` | SIMO converter output — **must be wired externally to `VDCC2`** |
-| 13 | `VPAX1` | `VPAX1` | SIMO converter output for PA supply — **wire externally to `VPAX2`** |
-| 14 | `LXB` | `LXB` | SIMO coil |
-| 15 | `GND_DCC` | `GND_DCC` | SIMO ground |
-| 16 | `LXA` | `LXA` | SIMO coil |
-| 17 | `VBAT` | `VBAT` | Main battery supply |
-| 18–19 | `DIO6`, `DIO5` | idem | Multi-purpose digital I/O |
-| 20 | `NRESET` | `NRESET` | Reset, active low |
-| 21–24 | `MISO`, `MOSI`, `SCK`, `NSS` | idem | SPI |
-| 25 | `BUSY` | `BUSY` | Busy indicator |
-| 26 | `VDCC2` | `VDCC2` | Regulated supply input |
-| 27–28 | `RFO_LF2`, `RFO_LF1` | idem | LF PA outputs — **two of them** |
-| 29 | `RFI_LF` | `RFI_LF` | LF receiver input |
-| 30 | `GND` | `GND` | Ground |
-| 31 | `RFI_HF` | **NC** | HF receiver input |
-| 32 | `RFO_HF` | **NC** | HF PA output |
-
-Three things a driver author should notice immediately:
-
-1. **There are seven DIOs (`DIO5`–`DIO11`) and none of them is special.** Unlike the SX126x —
-   where `DIO2` means RF-switch and `DIO3` means TCXO-supply by hard convention — every function
-   here is assigned at run time by `SetDioFunction` / `SetDioRfSwitchConfig` / `SetDioIrqConfig`
-   (§4.3). Do not carry an SX126x pin habit across.
-2. **`VDCC1`→`VDCC2` and `VPAX1`→`VPAX2` are external connections you must make on the PCB.**
-   The SIMO converter's outputs leave the package and come back in. Miss one and the part does not
-   run. **[DS]** §1.8.4.
-3. **The TCXO goes to `XTA`, not to a DIO**, and its supply comes from the dedicated `VTCXO` pin
-   (§6.2). The SX126x trick of stealing `DIO3` for TCXO power is gone, and so is the class of bug
-   that came with it.
-
----
-
-## 3. The command interface — and why your SX126x driver will not survive
-
-This is the section that answers "what breaks". The LR2021 is **not** an evolution of the SX126x
-host interface. It is a different interface that happens to keep the same four wires plus `BUSY`.
-
-### 3.1 What carried over
-
-- **SPI mode 0** (CPOL = CPHA = 0), subordinate only, transaction framed by `NSS` falling/rising,
-  MISO high-Z while `NSS` is high. **[DS]** §3.7.2
-- **`BUSY` is still a mandatory handshake**, still asserted on the falling edge of `NSS`, still
-  released when the command has been processed and the chip has reached a stable mode. **[DS]** §5.2
-- Max **SCK 16 MHz**, `tCP` ≥ 61.50 ns, `tSLCH` ≥ 31.25 ns at 10 pF load. **[DS]** Table 3-27
-- A `Sleep` / `Standby RC` / `Standby XOSC` / `FS` / `Rx` / `Tx` mode ladder. **[DS]** §4.4
-
-### 3.2 What changed, item by item
-
-| | **SX126x (Gen 2)** | **LR2021 (Gen 4)** | Consequence for a driver |
-|---|---|---|---|
-| **Opcode width** | **8 bits** | **16 bits** — `Op(15:8)`, `Op(7:0)` **[DS]** §5.4.1.1 | Every opcode constant, every command-framing helper, every unit test. Total rewrite of the transport layer |
-| **Status returned on MISO** | 1 status byte | **16 status bits followed by the full 32-bit `IrqStatus`**, on *every* command **[DS]** §5.4.1.1 | You get IRQ state free with each transaction. Also: your read helpers must skip 6 bytes, not 1 |
-| **IRQ width** | 16-bit `IrqStatus` | **32-bit** **[DS]** §5.6.3 (`ClearIrq irqs_to_clear(31:0)`) | Bitmask type changes; masks do not port |
-| **Register address width** | 16-bit, byte-wide access | **24-bit address, 32-bit data** — `WriteRegMem32 0x0104 Addr(23:0) Data[1:64]`, `ReadRegMem32 0x0106`, plus a read-modify-write `WriteRegMemMask32 0x0105` **[DS]** Table 5-2 | The whole register map is a different address space with different granularity. No SX126x register constant is meaningful |
-| **Data buffer** | **one** 256-byte buffer, shared, positioned with `SetBufferBaseAddress` | **two independent 256-byte FIFOs**, `ReadRadioRxFifo 0x0001` / `WriteRadioTxFifo 0x0002`, with programmable high/low thresholds, level readback (`GetRxFifoLevel`/`GetTxFifoLevel`), explicit clear, and `FifoEmpty/Full/Overflow/Underflow` flags **[DS]** §5.3 | ⚠ **This is a capability change, not just an API change.** Payloads > 256 B are supported by *streaming* — refill Tx / drain Rx mid-packet against the threshold IRQs. The SX126x could not do that at all |
-| **RF switch control** | `SetDio2AsRfSwitchCtrl` — one pin, on or off | `SetDioRfSwitchConfig 0x0113` with **five independent state masks**: `tx_hf, rx_hf, tx_lf, rx_lf, standby`, on **any** DIO **[DS]** §6.8.2 | Genuinely more capable: a dual-band front end needs four states, and the chip drives them itself |
-| **TCXO** | `SetDio3AsTcxoCtrl` — repurposes a DIO | `SetTcxoMode 0x0120 tune(7:0) start_time(31:0)` driving the **dedicated `VTCXO` pin** **[DS]** §6.11.3 | Cleaner, and one fewer DIO consumed |
-| **Errata handling** | Four register pokes you apply yourself | **A firmware Patch RAM (PRAM) image you upload at every cold start** (§7.1) | ⚠ **New mandatory boot step with no Gen-2 equivalent** |
-| **Direct FIFO access** | — | `ReadRadioRxFifo`/`WriteRadioTxFifo` complete **within a single SPI frame** rather than needing a second frame **[DS]** §5.4.1.3–5.4.1.4 | Faster, but a different transaction shape your HAL must expose (`lr20xx_hal_direct_read`, `lr20xx_hal_direct_read_fifo` **[DRV]**) |
-| **DIO as Rx/Tx trigger** | — | A DIO can *start* an Rx or Tx sequence in hardware; ⚠ **`BUSY` is not raised** for the trigger **[DS]** §5.5 | New capability, and a `BUSY`-polling loop written for Gen 2 will read this state wrong |
-
-**Verdict.** SX127x → SX126x was a total register-model change: register-mapped to command-based.
-**SX126x → LR2021 is a second break of the same magnitude**, in the opposite direction from
-"gentle": the command model survives conceptually but nothing about its encoding, addressing,
-buffering or initialisation is portable. Semtech's own driver reflects this — `lr20xx_driver` is a
-new tree, not a `#define` layer over `sx126x_driver` **[DRV]**. So does RadioLib: `LR2021` is a new
-module under a **new `LRxxxx` base class** created to share what the LR11xx and LR20xx have in
-common — `d696fed842bc77c6699ac83d9611a7d6e1c838d6`, *"[LRxxxx] Create base class for common LR11xx
-and LR20xx commands"*, 2025-10-13 **[RL]**. Note what that says: the common ancestor is **LR11xx**,
-not SX126x.
-
-**What does survive is the air interface**, and that is the point — see §8.
-
----
-
-## 4. Modems and packet engine
-
-### 4.1 LoRa
-
-| Parameter | Value | Source |
-|---|---|---|
-| Spreading factor | **SF5 – SF12** | **[DS]** Table 3-9 |
-| Bandwidth | **7.825 – 1000 kHz** (434 MHz–2.5 GHz); **7.825 – 500 kHz** (150–433 MHz) | **[DS]** Table 3-9 |
-| Bit rate | 45.8 bps (SF12/31.25 kHz/CR4:8) … **125 kbps** (SF5/1000 kHz/CR4:5) | **[DS]** Table 3-9 |
-| Coding rate | 4/5…4/8 **plus new convolutional CR8/CR9** | **[DS]** §9.1.3, §23.8 |
-| Sync word, address filter, hopping | `SetLoraSyncword`, `SetLoraAddress`, `SetLoraHopping` | **[DS]** §9.9 |
-
-Four LoRa features are **new in Gen 4** and have no Gen-2/Gen-3 counterpart **[DS]** §9.3–9.7, §23.8:
-
-- **Multi-SF detection** — receive several spreading factors *simultaneously*. For a mesh this is
-  the single most consequential item on the list: it lets the two legs of an asymmetric link run
-  at different SFs.
-- **Multi-SF CAD** and **Fast CAD**. §9.4 notes that CAD on previous generations "uses a fixed
-  peak-to-noise ratio threshold across all symbols"; Gen 4 does not.
-- **Extended LoRa Rx bandwidth** (§9.7).
-- **Convolutional CR8/CR9**.
-
-And two are **compatibility shims** pointing straight back at Gen 1:
-
-- **§9.8 Intra-packet frequency hopping compatibility with SX127x.** Hopping existed in Gen 1,
-  vanished in Gens 2–3, and returns in Gen 4 — §23.8: *"Intra-packet hopping is available in
-  generations 1 and 4."*
-- **§9.9.2 SF6 compatibility with SX127x.** SF6 has been an interoperability trap across the whole
-  lineage; here it is an explicit mode.
-
-### 4.2 The other modems
-
-| Modem | Headline | Parts |
-|---|---|---|
-| **FLRC** | up to **2.6 Mbps**; the flagship new PHY, and the reason the marketing title says "Fast Long Range Communication" | LR2021 only |
-| **LR-FHSS** | 488 bps raw; **for SATCOM and sub-GHz** | LR20xx |
-| **(G)FSK / GMSK** | 3.4 kHz – 2666 kHz channel BW; modulation index 0.3–8.3 | LR20xx |
-| **OOK** | 1.2–32.768 kbps Tx, up to **2 Mbps** Rx | LR20xx |
-| **(D)BPSK** | 0.1–0.6 kbps, **Tx only** — this is the Sigfox uplink | LR20xx |
-| **O-QPSK DSSS** | 250 kbps @2.4 GHz, 100 kbps sub-GHz — 802.15.4 | LR2021 only |
-| **Bluetooth LE PHY** | 1M / 2M / Coded 500k / Coded 125k | LR2021, LR2022 |
-| **Z-Wave / Z-Wave LR** | dedicated packet handler with HomeID and beam filtering, and a `SetZwaveScan` engine | LR2021 only |
-| **WM-Bus** | S/T/C/R/N modes, **device *and* collector** | LR20xx |
-| **Wi-SUN FSK** | modes 1a…4b | LR20xx |
-
-⚠ **A PHY is not a stack.** Semtech is careful, and so should you be: BLE, Zigbee/Thread, Z-Wave,
-Wi-SUN and Sidewalk work *"when integrated with third-party stack offerings"* **[DOC]**. The chip
-gives you the radio and the packet handler. It does not give you a qualified Bluetooth product —
-**[DS]** p. 3 says so explicitly: *"Semtech's products are designed to be used in connection with
-qualified Bluetooth products and applications but are **not** certified or qualified Bluetooth
-products."*
-
-### 4.3 Interrupts and DIO assignment
-
-Three orthogonal commands, all taking an explicit `Dio(7:0)` argument **[DS]** §6.8:
-
-```
-SetDioFunction        0x0112   Dio(7:0), Func(3:0), pull_drive(3:0)
-SetDioRfSwitchConfig  0x0113   Dio(7:0), tx_hf, rx_hf, tx_lf, rx_lf, standby
-SetDioIrqConfig       0x0115   Dio(7:0), Irq(31:0)
-```
-
-Plus a **second, separate IRQ domain for the FIFOs** — `ConfigFifoIrq 0x011A` with independent
-enable masks and four thresholds (`rx_high`, `rx_low`, `tx_high`, `tx_low`), read back through
-`GetFifoIrqFlags 0x011B` and cleared through `ClearFifoIrqFlags 0x0114`. A driver that models
-"the IRQ register" as one 32-bit word will miss half the machine.
-
----
-
-## 5. RF front end, power and performance
-
-### 5.1 Two PAs, and a front end designed to avoid an external switch
-
-**[DS]** §1.5, §7.4, Table 3-22:
-
-| | **LF PA** (150–960 MHz) | **HF PA** (1.5–2.5 GHz, LR2021/22) |
-|---|---|---|
-| Max Tx power | **+22 dBm** typ (min 19) | **+12 dBm** typ |
-| Power range | 63 steps of **0.5 dB** (≈32 dB dynamic) | 63 steps of 0.5 dB |
-| Step accuracy | ±2 dB | ±2 dB |
-| OCP trip | **164 mA** | **55 mA** |
-| Ramp time | 2 µs … 340 µs, programmable | idem |
-| Outputs | **`RFO_LF1` *and* `RFO_LF2`** — two branches run in phase in the default "Full single-ended mode" | `RFO_HF` |
-
-⚠ **`SetPaConfig` is dangerous to guess at.** **[DS]** §7.4.1 states that non-optimised PA
-parameters may cause *"Incorrect output power / Excessive current consumption / **PA damage** /
-Regulatory non-compliance"*, and that `pa_hf_duty_cycle` accepts **only 16–31** "to avoid risk of
-aging the power amplifier". The datasheet's advice for any board that is not the reference design
-is to contact Semtech applications support. Take the PA tables from `lr20xx_pa_pwr_cfg.h` **[DRV]**
-rather than inventing them. ⚠ Semtech's own USP README adds that the **China 490 MHz `Wio-LR20xx`
-variant needs a different PA table** from the 868/915 boards **[DRV]**.
-
-### 5.2 Current
-
-**[DS]** Tables 3-4 to 3-7. `VBAT = 3.3 V`, 25 °C, **no shield, SIMO** — Rev 2.1 explicitly
-clarified those conditions, and §23.2 warns that a metallic RF shield over a SIMO design costs
-sensitivity.
-
-| Mode | Typ | Note |
-|---|---:|---|
-| Sleep, no retention, no RTC | **470 nA** | front-page figure; Table 3-4 `IDDSL0`/`IDDSL1` group spans 0.47–1.4 µA depending on retention and RTC. ⚠ **The `µ` is lost by text extraction and the five-row/five-column alignment in Table 3-4 did not survive it — read the PDF before quoting a specific retention variant** |
-| Sleep + PRAM loaded | **+80 nA** on top | **[DS]** §22.3 — the patch image costs retention current |
-| `STDBY_RC` | 1.21 mA | HFRC 32 MHz on |
-| `STDBY_XOSC` | 1.79 mA | |
-| Synthesiser (FS) | 3.0 mA | @915 MHz |
-| **Rx, LoRa SF7/125 kHz sub-GHz** | **5.7 mA** | `IDDRXLFL4` |
-| Rx, LoRa SF7/125 kHz @2.4 GHz | 6.4 mA | `IDDRXHFL4` |
-| Rx boosted, LF path | **+1.2 mA** | `IDDDELTA1` |
-| Rx, FLRC 260 kbps / 2.6 Mbps | 6.6 / 10.4 mA | |
-| **Tx +22 dBm, 868/915 MHz** | **105 mA** | `IDDTXLF1` |
-| Tx +20 / +17 / +14 / +10 dBm | 72 / 43 / **27** / 17 mA | |
-| Tx +10 dBm via HF PA with dedicated matching | **12 mA** | `IDDTXLF8` — a genuinely unusual option |
-| Tx +22 dBm, 434/490 MHz | 100 mA | |
-| Tx +12 dBm @2.4 GHz | 23 mA | `IDDTXHF` |
-
-**The receive figure is the headline.** 5.7 mA against the SX1262's 4.6 mA (DC-DC) / 9.7 mA (LDO)
-is not a dramatic win on its own — but the SX1262 only reaches 4.6 mA with its DC-DC enabled, and
-its DC-DC **cannot help the PA at all** because the SX1262's PA is fed from `VBAT`. The LR2021's
-**SIMO converter supplies both the core rail (`VDCC`, ~1.55 V, ≤20 mA) and the PA rail (`VPAX`)**
-**[DS]** §1.8.4. That is why +22 dBm costs **105 mA here versus 118 mA on an SX1262** — a ~11 %
-transmit-energy reduction that comes from supply topology, not from the PA.
-
-⚠ **SIMO is not free.** Semtech's own driver documentation states that *"Usage of DCDC regulator
-(a.k.a. SIMO converter) may negatively impact RF sensitivity for sub-GHz operations"* for FSK,
-FLRC, OOK, LoRa **and** Z-Wave **[DRV]**. LDO mode exists for "noise sensitive, low-cost or small
-size applications" **[DS]** §1.8.4, selected with `SetRegMode 0x0109`. **The current-versus-sensitivity
-trade is a real design decision on this part, and the datasheet's electrical numbers are the SIMO
-column.**
-
-### 5.3 Sensitivity — LoRa sub-GHz, 64 B payload, CR 4/5
-
-**[DS]** Table 3-17. Typical values, dBm.
-
-| BW ↓ / SF → | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
-|---|---:|---:|---:|---:|---:|---:|---:|---:|
-| **62 kHz** | — | −126.5 | −129 | −132 | −135 | −137.5 | −140.5 | **−143** |
-| **125 kHz** | — | −125 | −127.5 | −130.5 | −133 | −136 | −138.5 | **−141.5** |
-| **250 kHz** | −119 | −122 | −124.5 | −127.5 | −130 | −133 | −135.5 | −138.5 |
-| **400 kHz** | −117 | −120 | −122.5 | −125.5 | −128.5 | −130.5 | −134 | −136.5 |
-| **500 kHz** | −116 | −119 | −122 | −124.5 | −127.5 | −130 | −133 | −135.5 |
-| **800 kHz** | −113 | −115.5 | −118 | −121 | −124 | −126.5 | −130 | −132 |
-| **1000 kHz** | −112.5 | −115.5 | −118 | −120 | −123 | −126 | −129 | −131 |
-
-(SF5 at 62/125 kHz is present in the document; the value did not survive the text extraction on
-those two rows and is left blank rather than guessed. **[DS]** Table 3-17 sheets 3–4.)
-
-**−141.5 dBm at SF12/125 kHz is the marketed number** and is genuinely ~1 dB better than the
-SX1262's −140.6 dBm at the same setting. The larger practical gain is elsewhere: **multi-SF
-reception**, **improved CAD**, and **increased frequency-offset tolerance** — the last of which
-Semtech markets as *"obviating TCXO and large thermal relief"* **[DOC]**, i.e. the ability to run
-SF12 on a **plain crystal**. On Gen 2 that generally needed a TCXO, and a TCXO is both a BOM line
-and a standing sleep-current cost.
-
-Other PHYs, front-page typicals **[DS]**: FLRC sub-GHz −111 dBm @260 kbps, −104.5 @0.975 Mbps,
-**−100.5 @1.95 Mbps** (⚠ **[DS1.1]** said **−101.5** — see §14); BLE −100 dBm @1 Mbps, −97 @2 Mbps;
-O-QPSK −103 dBm @250 kbps 2.4 GHz, −111 dBm @100 kbps sub-GHz.
-
----
-
-## 6. Clocks, reset and start-up
-
-### 6.1 Reset and boot
-
-**[DS]** §4.2–4.3: `BUSY` stays **high** through reset and through the boot calibration sequence,
-falling only when the device reaches `STDBY_RC` and can accept commands. Same contract as Gen 2;
-the timing is different and the PRAM upload (§7.1) is bolted on after it.
-
-### 6.2 Crystal, TCXO, or neither
-
-Three reference options, and this is one of the areas where Gen 4 is materially cheaper to build:
-
-- **32 MHz XTAL** on `XTA`/`XTB`. The default, and — thanks to the wider frequency-offset
-  tolerance — the *intended* choice for most designs.
-- **32 MHz TCXO** on `XTA` with `XTB` unconnected, powered from the dedicated **`VTCXO`** pin whose
-  regulated voltage is programmed by `SetTcxoMode`. `ILTCXO` 1.5–4 mA; `ATCXO` 0.4/0.6/1.2 V p-p
-  clipped sine, AC-coupled through 10 pF in series with 220 Ω. **[DS]** §1.9.3, Table 3-25
-- **XTAL + NTC temperature compensation.** A resistor and NTC hung off `VTCXO` and `NTC` let the
-  chip measure crystal temperature and compensate the induced frequency shift on-chip
-  (`SetNtcParams`, `SetTempCompCfg`). **[DS]** §1.9.2, §6.12. Semtech calls this out as
-  *"particularly useful when high power PA is desired on a small PCB footprint"* — i.e. it exists
-  to fix the self-heating pull that a +22 dBm PA inflicts on a nearby crystal. **There is no Gen-2
-  equivalent.**
-- **External 32 kHz LF reference** can be injected on `DIO11` via `ConfigLfClock`, for synchronous
-  protocols that need accurate wake timing. **[DS]** §1.9.4
-
-Clock output: any of `DIO5`–`DIO11` can emit the HF clock, divided by any power of two from 32 MHz
-down to 976.562 kHz (`ConfigClkOutputs`); `DIO7`–`DIO11` can emit the 32 kHz LF clock, available
-even in sleep. **[DS]** §1.9.5
-
----
-
-## 7. Known limitations, workarounds and the PRAM
-
-### 7.1 ⚠ The Patch RAM is the biggest single migration surprise
-
-**[DS]** §22.3 and **[DRV]**:
-
-- The LR20xx ships with a **firmware patch image (PRAM)** that the host **uploads over SPI**.
-- *"While not strictly required, using the chip without the PRAM can create performance issues and
-  unexpected bugs. The use of the PRAM is therefore **highly recommended**."*
-- **It is lost on reset and on cold start.** It survives sleep-with-retention.
-- It costs **+80 nA** of retention sleep current while loaded.
-- Two images exist: `lr20xx_pram_load_pram_lr2021` and `lr20xx_pram_load_pram_lr20x2`. **They are
-  per-part.** **[DRV]** `inc/lr20xx_pram_lr2021.h`, `inc/lr20xx_pram_lr20x2.h`
-- Version-checkable at run time: `lr20xx_patch_get_version`, `lr20xx_patch_enable_pram`. **[DRV]**
-
-There is no SX126x analogue. On Gen 2 you applied four register pokes; on Gen 4 you ship a binary
-blob and load it every cold boot. A driver that does not do this will *appear* to work.
-
-### 7.2 What the PRAM fixes — Semtech's own list **[DRV]**
-
-Bluetooth LE Coded PHY access-address failures · BLE Coded PHY frequency drift degrading
-sensitivity · wrong default preamble length for BLE 2M · degraded BLE Coded PHY blocking
-performance · RTToF PLL frequency-step bias when the RF frequency is not a multiple of **122 Hz**
-· incorrect RTToF RSSI · RTToF extended mode hanging for seconds · **SIMO impact on sub-GHz
-sensitivity for FSK, FLRC, OOK, LoRa and Z-Wave**.
-
-### 7.3 Workarounds that are *not* in the PRAM — you call these yourself **[DRV]**, **[DS]** §22
-
-| Workaround function | What it is for |
-|---|---|
-| `lr20xx_workarounds_lora_enable_sx1276_compatibility_mode` | **Gen-1 LoRa interop.** ⚠ Not retained across sleep unless you also call `…_store_retention_mem` |
-| `lr20xx_workarounds_lora_freq_hop_enable_sx1276_compatibility_mode` | SX1276-compatible **intra-packet hopping**; must be called *after* `lr20xx_radio_lora_set_freq_hop` |
-| `lr20xx_workarounds_ook_set_detection_threshold_level` | **[DS]** §22.1 — the automatic OOK RSSI threshold is too conservative; measure the noise floor with `GetRssiInst` and override |
-| `lr20xx_workarounds_rttof_results_deviation` | **[DS]** §22.2 — RTToF standard deviation on the SX1280-compatible "fractional" bandwidths 101/203/406/812 kHz. Reverted by the next `set_modulation_params`; needs `…_store_retention_mem` to survive sleep |
-
-⚠ **The retention-memory pattern is a new class of bug.** Several workarounds touch registers that
-are *not* preserved by sleep-with-retention unless explicitly parked in a retention slot. A node
-that sleeps between packets will silently lose its SX1276 compatibility mode, or its RTToF fix,
-unless the driver stores it. This has no Gen-2 equivalent and is easy to miss.
-
----
-
-## 8. Interoperability with older generations — what actually still talks
-
-**[DS]** §23.8, and this is the reassuring half of the migration story:
-
-> LoRa radios across the different generations can communicate with each other when properly
-> configured with identical parameters (frequency, spreading factor, bandwidth, and coding rate).
-> … Note that **all the LoRaWAN configurations are fully compatible between all four generations**.
-
-The exceptions, all from §23.8:
-
-| Feature | Gen 1 | Gen 2 | Gen 3 | Gen 4 |
-|---|:--:|:--:|:--:|:--:|
-| **SF5** | ❌ | ✅ | ✅ | ✅ |
-| **SF6** | ⚠ needs a compatibility mode across the boundary | ⚠ | ⚠ | ⚠ `SetLoraSF6Compat` / §9.9.2 |
-| **Long interleaver** | ❌ | ❌ | ✅ | ✅ |
-| **Intra-packet hopping** | ✅ | ❌ | ❌ | ✅ |
-| **Multi-SF CAD, Fast CAD** | ❌ | ❌ | ❌ | ✅ |
-| **Convolutional CR8/CR9** | ❌ | ❌ | ❌ | ✅ |
-
-So: an LR2021 node drops into an existing SX1262 Meshtastic or LoRaWAN mesh and works, provided you
-do not turn on the new toys. The new toys are exactly what makes the part worth having, and every
-one of them is a mesh-splitting decision.
-
----
-
-## 9. Drivers, SDKs and software support
-
-| Option | Where | Verdict |
-|---|---|---|
-| **Semtech `lr20xx_driver`** (inside **USP**) | `github.com/LoRa-Net/usp`, driver **v2.0.2**, repo @ `512a095e303872f900021361a619b7b1e6e29469`, release `v1.1.2-feature-202604` (2026-04-16) · **BSD-3-Clause-Clear** | **The reference implementation.** ⚠ There is **no standalone `lr2021_driver` repository** — unlike `sx126x_driver`, `llcc68_driver`, `lr1110_driver` and `SWDR001`, the Gen-4 driver ships only inside USP |
-| **RadioLib** | `github.com/jgromes/RadioLib`, `src/modules/LR2021` — **first shipped in release 7.6.0, 2026-02-19** | **Use this for Arduino/PlatformIO work.** 15 files, ~250 KB of source. Details in [`projects-and-community.md`](projects-and-community.md) |
-| **Meshtastic** | `LR2021Interface` + `LR20x0Interface`, merged 2026-05-08 (PR #10401) | Supported on the **2.8.x** line; **not** in v2.7.26. Details in [`projects-and-community.md`](projects-and-community.md) |
-| **Zephyr** | `github.com/LoRa-Net/usp_zephyr` — "Zephyr RTOS integration of Semtech's USP … Compatible with LR20xx, SX126x and LR11xx" | Exists; not evaluated here |
-| **LoRaMac-node** | `github.com/LoRa-Net/LoRaMac-node` — last push **2024-07-03** | ⚠ **Predates the part.** The Gen-4 LoRaWAN path is USP/LoRa Basics Modem, not LoRaMac-node |
-| **Linux** | USP builds for "Linux (x86/x86_64 native + ARM cross-compilation for Raspberry Pi, embedded Linux)"; ⚠ **"Linux porting was only tested with LR2021"** **[DRV]**. Meshtastic's Portduino also has an LR2021 path (PR #11252, merged 2026-07-30) **[MT]** | Userspace SPI. **No in-tree Linux kernel driver was found** for any Semtech LoRa transceiver, Gen 4 included — `not-tested`, negative result |
-| Raw SPI | — | Feasible — §3 is the whole interface — but §7's PRAM upload and retention-memory workarounds are exactly what a hand-rolled driver omits |
-
-### 9.1 ⚠ USP is explicitly pre-production
-
-Its own README, at the pinned commit **[DRV]**:
-
-> **USP RELEASE v1.1.2 - Experimental Feature Release**
-> ⚠ **Warning**: This preview release is not intended for production use. A stable release will be
-> available soon
-
-It bundles **LoRa Basics Modem 4.9.0**. Validation status is unusually candid and worth reproducing:
-
-| Target | Status |
-|---|---|
-| LoRa Plus EVK (LoRa Plus Expansion Board + Wio-LR2021/LR2022/LR2012) on **STM32L476RG** | **Validated** — "passed the Semtech nominal validation process" |
-| LR11xx shield radios · SX126x shield radios | **Buildable** — compiles, no full validation |
-| Linux (x86/x86_64/ARM) | Buildable; **tested only with LR2021** |
-| Renesas FPB-RA0E2, STM32L073RZ | **Experimental** — one sample application, US915 Class A |
-
-The architectural claim in the repo description is the one that matters strategically: USP is
-*"MCU FW SW driving LR20xx multi-PHY radios with multiprotocol operations and radio resource
-arbitration … **Backward-compatible with SX126x and LR11xx radio devices**."* Semtech's answer to
-the three-driver problem is one abstraction over all three generations — but that abstraction is
-new, pre-production, and does not retrofit onto anything already shipped.
-
----
-
-## 10. Caveats, gaps and errata
-
-| # | Issue | Evidence |
-|---|---|---|
-| **G1** | ⚠ **Semtech's current datasheet revision could not be obtained.** The product page lists **"LR2021/22/12 Datasheet v2.2, 2026-08-08"**; the newest copy retained here is **Rev 2.1 (13/04/26)**. The canonical link is a Salesforce JS shell that yields no bytes to any non-browser client. **So this record may be one revision behind, and that is `unresolved`, not "no lag"** | `executed-failed` 2026-09-04; [`vendors/semtech/README.md` §4](../../../vendors/semtech/README.md) |
-| **G2** | **Two retained revisions disagree on a published number.** FLRC sub-GHz @1.95 Mbps: **−101.5 dBm** in Rev 1.1, **−100.5 dBm** in Rev 2.1. Both are kept; Rev 2.1 is authoritative | **[DS]** vs **[DS1.1]** front pages |
-| **G3** | ⚠ **No AES engine, no secure key store, no DevEUI/JoinEUI management.** The word `AES` does not appear in the 243-page datasheet; the only crypto-adjacent line is a warning that `GetRandomNumber` *"should not be used for cryptographic purposes"* (§6.6.2). **This is a regression against Gen 3** — the LR11xx has a crypto engine and secure key storage. Independently asserted by Waveshare's own `Core2021` vs `Core1121` comparison table | **[DS]** §6.6.2 (negative result, whole-document search); **[DOC]** Waveshare |
-| **G4** | **The package marking is a figure with no text layer.** **[DS]** §24.2 Figure 24-2 exists but extracts as nothing, so **this record cannot tell you what is printed on the lid**. Neither can it give the package outline or land pattern dimensions (§24.1, §24.3) | **[DS]** — explicit gap; open the PDF |
-| **G5** | **Nothing here was measured.** No range, throughput, sensitivity, current or battery figure in this record was reproduced by anyone whose method could be inspected. The only firsthand numbers located anywhere are community bench reports, catalogued and labelled in [`projects-and-community.md`](projects-and-community.md) | negative result |
-| **G6** | ⚠ **PA configuration can damage the part.** **[DS]** §7.4.1 lists "PA damage" among the consequences of non-optimised `SetPaConfig` parameters, and restricts `pa_hf_duty_cycle` to 16–31 "to avoid risk of aging". Any board that is not the reference design needs Semtech applications support or a vetted PA table | **[DS]** §7.4.1 |
-| **G7** | **SIMO costs sensitivity.** Semtech's driver docs list LoRa, FSK, FLRC, OOK and Z-Wave sub-GHz sensitivity as degraded by the SIMO converter, and §23.1/§23.2 add a further degradation for SIMO under a metallic RF shield. The datasheet's electrical tables are specified "no shield, SIMO" | **[DRV]**; **[DS]** §23.1–23.2 |
-| **G8** | ⚠ **Retention-memory workarounds silently revert.** SX1276 compatibility mode, SX1276 hopping compatibility and the RTToF deviation fix are all lost across sleep-with-retention unless explicitly stored in a retention slot | **[DRV]** driver README |
-| **G9** | **The PRAM is mandatory in practice and optional in wording.** "Not strictly required … therefore highly recommended" is the datasheet's phrasing for a patch that fixes BLE Coded PHY, RTToF and SIMO sensitivity. Treat it as mandatory | **[DS]** §22.3 |
-| **G10** | ⚠ **`LR2021` ≠ `LR20xx`.** FLRC, O-QPSK and Z-Wave are LR2021-only; BLE is LR2021/22-only; the whole HF path is absent on LR2012. The single-datasheet-many-parts trap that bites SX1261-vs-SX1262 readers bites harder here, because there are three parts | **[DS]** p. 2 |
-| **G11** | **No standalone driver repository.** `lr20xx_driver` exists only inside the 47 MB `usp` monorepo, whose own README says it is not for production. Compare `sx126x_driver`, `llcc68_driver`, `lr1110_driver`, `SWDR001` — all standalone | **[DRV]**, GitHub org listing |
-| **G12** | **`LoRaMac-node` has not been touched since 2024-07-03** and has no LR20xx support. Anyone whose LoRaWAN stack is LoRaMac-node has no Gen-4 path without switching to LoRa Basics Modem / USP | GitHub API, 2026-09-04 |
-| **G13** | **LR-FHSS remains patent-encumbered.** **[DS]** p. 3 grants no patent rights with the software; rights come *"by purchasing Semtech SX1261, SX1262, SX1268, LR1110, LR1120, LR1121, LR2012, LR2021 or LR2022 semiconductor devices, or their authorized counterparts"* | **[DS]** p. 3 |
-| **G14** | **Every page is stamped "Semtech Proprietary & Confidential"** — on a document freely mirrored by two distributors. Redistribution status is recorded `unknown` and the artifacts are unstaged pending review (§14) | **[DS]** running footer |
-| **G15** | **No LR2022 or LR2012 hardware was found in the wild.** Every module, board and firmware located — Waveshare `Core2021`, Seeed `Wio-LR2021`, NiceRF `LoRa2021F33-2G4`, SenseCAP MeshTracker X1, Meshnology W12 — uses the **LR2021**. ⚠ **The LR2012 is nonetheless a real, documented product**: Semtech's document catalogue lists `LR2012EVK1XBS1`/`XCS1`/`XGS1` production folders and LR2012 reference designs for EU868, US915 and CN490, all dated **2026-08-18**, and there is an `LR2012` product page with its own EVK SKUs. **The LR2022 has neither an EVK nor a reference design in the catalogue** — it appears only as a column in the datasheet and in the `LR2021EVK2*` kit names. Semtech's own driver ships a separate `lr20xx_pram_load_pram_lr20x2` patch image, so the `x2` parts are real silicon to the driver | negative result for hardware; **[DOC]** catalogue + **[DRV]**, 2026-09-04 |
-
----
-
-## 11. Lifecycle, sourcing, pricing and availability
-
-**Timeline** (dates are evidenced; see [`projects-and-community.md`](projects-and-community.md) for the community half):
-
-| Date | Event | Evidence |
-|---|---|---|
-| **2025-03-12** | Announced. Meshtastic's own account posts *"Semtech announced their 4th gen #LoRa chip!"* linking the LR2021 product page, and notes Semtech named Meshtastic specifically | **[COM]** r/meshtastic `1j9xjw6`, 82 pts |
-| **2025-06** | Datasheet **Rev 0.2**, "Preliminary release" | **[DS]** revision history |
-| **2025-06-09** | RadioLib `[LR2021] Initial WIP commit` `2472fbdf727e7263167bdc511f2bd0744194dd33` | **[RL]** |
-| **2025-10** | Datasheet **Rev 1.1**, "Final datasheet" (`DS.LR2021`, 10/14/25) | **[DS1.1]** |
-| **2025-10-14** | `LoRa-Net/usp` repository created | GitHub API |
-| **2025-12-16** | USP **v1.0.0** | GitHub API |
-| **2026-02-19** | **RadioLib 7.6.0** — first release shipping LR2021 support | **[RL]** |
-| **2026-04** | Datasheet **Rev 2.1** — expanded to cover LR2022 and LR2012 (`DS.LR20xx`) | **[DS]** |
-| **2026-05-08** | **Meshtastic** merges LR2021 support (PR #10401) | **[MT]** |
-| **2026-07-23** | Seeed SenseCAP **MeshTracker X1** pre-orders open — first mass-market Meshtastic product with the part | **[COM]** r/meshtastic `1v49g4p`, 170 pts |
-| **2026-08-08** | Datasheet **v2.2** per Semtech's listing — ⚠ not obtained (G1) | **[DOC]** |
-| **2026-08-25** | LR2021 **ETSI** and **FCC prescan** radio test reports published (ZIP) | **[DOC]** |
-
-**Lifecycle status: active, in volume, ~18 months after announcement.** Not sampling; there are
-shipping consumer products.
-
-### 11.1 What you can buy, and what it costs
-
-| Item | Vendor | Price / date | Note |
-|---|---|---|---|
-| **`LR2021EVK2XBS1`** (EU 868 + 2.4 GHz) · **`LR2021EVK2XCS1`** (NA 915 + 2.4 GHz) · **`LR2021EVK2XGS1`** (CN/Asia 490 + 2.4 GHz) | Semtech | list price not published on the product page — ⚠ the "Unit Price (USD)" widget renders as `$0` without JavaScript **[DOC]** | Each kit contains **2 × RF boards** (`LR2021RF2XDS1`, or `…XGS1` for the 490 MHz kit) |
-| `LR2021EVK1XGS1` | Semtech | — | Earlier EVK1 generation; still listed |
-| **LR2021 LoRa Plus Evaluation Kit, 915 MHz US, V2.0** | **Seeed Studio** | **US$99.00**, 2026-09-04 | ⚠ **Two complete nodes**, so ≈$50/node: nRF54L15 + Wio-LR2021 + OLED + 2 SMA antennas + cable **[COM]** |
-| **`Core2021-LF` / `-HF` / `-XF`** module | **Waveshare** | **US$11.99 / US$12.99**, 2026-09-04 | Bare LR2021 module, three band SKUs. Waveshare's own page calls it *"the fourth-generation LoRa multi-band transceiver LR2021"* |
-| **`LoRa2021F33-2G4`** 1 W module | **NiceRF** | not retrieved — `www.nicerf.com` returned **HTTP 403** to both the Chrome and WhatsApp agents, 2026-09-04 | LR2021 + external PA, ~+30 dBm. Community bench-tested (see `projects-and-community.md`) |
-| **SenseCAP MeshTracker X1** | Seeed | pre-order opened 2026-07-23; price not captured this pass | Meshtastic variant `seeed_mesh_tracker_X1` upstream **[MT]** |
-| LilyGo **T-Display P4 LR2021** | LilyGo | listed then unavailable on AliExpress, "Release on May 20" 2026 | **[COM]** hearsay, r/meshtastic `1tcb7ni` |
-
-⚠ **Distributor stock could not be checked.** The Semtech page's Digi-Key-powered inventory widget
-is JavaScript-only and renders empty to `curl`; `www.mouser.com/c/?q=` returns a 13 895-byte
-"Access Denied" page to every agent tried. **`unresolved`**, 2026-09-04.
-
-### 11.2 Reference designs and certification — available, unusually
-
-Semtech publishes, all gated behind the Salesforce shell (§14, G1):
-
-- **`LR202x` reference design files** for **CN490**, **EU868** and **US915**, each covering
-  sub-GHz *and* 2.4 GHz, 2026-08-18, ZIP
-- **LR2021 ETSI Radio Test Report** and **LR2021 FCC Prescan Radio Test Report**, both 2026-08-25, ZIP
-- `AN1200.112 - SubGHz FLRC Regulatory Measurement Reports v2.0`, 2026-07-27
-- `AN1200.66: PCB Design Guidelines`, 2026-05-20 · `AN1200.59 - Selecting the Optimal Reference Clock`, 2026-07-16
-
-This is a **better** certification story than the SX1262 has in this knowledge base, where no
-module-level certification could be found at all. Published ETSI and FCC prescan reports for a
-reference design are a real head start — they are not a grant, and they do not transfer to your
-board with your antenna, but they tell you the design has been through a chamber.
-
----
-
-## 12. Choosing it, and choosing against it
-
-**Reasons to choose the LR2021**
-
-- You need **two bands from one SKU and one antenna path** — sub-GHz for range, 2.4 GHz for
-  short-hop bulk — without an external RF switch.
-- You need **more than LoRa's data rate**: FLRC at up to 2.6 Mbps is the only Semtech PHY that
-  makes image or audio transfer over an ISM link plausible.
-- You want **multi-SF reception** — for a mesh this is the standout, and nothing else in the
-  lineage has it.
-- You want to **drop the TCXO**. Wider frequency-offset tolerance plus on-chip NTC compensation is
-  a BOM line and a sleep-current line removed.
-- **Transmit energy**: 105 mA at +22 dBm versus 118 mA on an SX1262, because SIMO feeds the PA.
-- You need a **PHY the SX126x cannot produce at all** — Z-Wave, BLE, 802.15.4, Sigfox BPSK.
-
-**Reasons not to**
-
-- ⚠ **Your driver is a rewrite, not a port** (§3). Budget for it honestly.
-- ⚠ **No AES engine or secure key storage** (G3). If you picked LR11xx for its crypto, Gen 4 is a
-  step backwards.
-- ⚠ **No GNSS, no Wi-Fi scanning.** Gen 4 is not a superset of Gen 3 — geolocation stayed in the
-  LoRa Edge line. If you want "where is it", you still want an [LR1121](../lr1121/README.md).
-- ⚠ **Software is young.** USP says "not intended for production use"; RadioLib support is ~7
-  months old; `LoRaMac-node` has no path at all.
-- **Price and volume.** A `Core2021` at $12 against SX1262 modules at a few dollars, and an
-  ecosystem two orders of magnitude smaller.
-- **You gain nothing if you only ever run stock LoRaWAN or stock Meshtastic** — §8 says the air
-  interface is compatible, which cuts both ways.
-
-**Competing and substitute parts**
-
-| Part | Relationship | When it wins |
-|---|---|---|
-| [**SX1262**](../sx1262/README.md) | Gen 2 baseline; **not a drop-in in either direction** | Cost, maturity, ecosystem. Still the right default for plain sub-GHz LoRa |
-| [**LR1121**](../lr1121/README.md) | Gen 3; multi-band + GNSS + Wi-Fi scanning + **crypto** | Asset tracking; anything needing a secure element |
-| [**LLCC68**](../llcc68/README.md) / [**SX1268**](../sx1268/README.md) | Gen-2 SX1262 siblings | Cost-down and 433/470 MHz respectively |
-| [**SX1276/SX127x**](../sx1276/README.md) | Gen 1 | Only for compatibility with an existing Gen-1 deployment |
-| **SX1280/SX1281** | **Gen 2**, 2.4 GHz only, has FLRC and ranging | Cheaper and far better supported if you only need 2.4 GHz FLRC — a community recommendation made repeatedly (`projects-and-community.md`) |
-| **STM32WL** | SX126x core on-die with a Cortex-M | One chip instead of two, on the Gen-2 driver |
-| **LR2022 / LR2012** | Same die family, features fused off | Cost, when you do not need FLRC/O-QPSK/Z-Wave/BLE. ⚠ No evidence of availability (G15) |
-
-**Drop-in compatibility: none, in any direction.** Different package (QFN32 5 × 5 vs QFN24 4 × 4),
-different pinout, different supply topology, different command encoding. What *is* compatible is
-the air interface (§8).
-
----
-
-## 13. Used By
-
-**No board in this knowledge base uses the LR2021.** Every LoRa-bearing device documented here is
-Gen 2 — the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md), the
-[Cap LoRa-1262](../../../devices/m5stack/cap-lora-1262/README.md), the
-[Cap LoRa868](../../../devices/m5stack/cap-lora868/README.md), the
-[Cardputer Mesh Kit](../../../devices/m5stack/cardputer-mesh-kit/README.md), the
-[Stamp C6LoRa](../../../devices/m5stack/stamp-c6lora/README.md) and
-[Unit C6L](../../../devices/m5stack/unit-c6l/README.md) all carry an
-[SX1262](../sx1262/README.md), and the [Ebyte E22-900M22S](../../ebyte/e22-900m22s/README.md)
-is an SX1262 with an external PA. This record is here for the lineage and for the next board, not
-because anything on the shelf needs it.
-
-**Boards that do use it**, so the record is not a dead end:
-
-| Board / module | Vendor | Evidence |
-|---|---|---|
-| **SenseCAP MeshTracker X1** | Seeed Studio | Meshtastic variant `variants/nrf52840/seeed_mesh_tracker_X1/` — `#define USE_LR2021`, `LR2021_DIO3_TCXO_VOLTAGE 1.6`, `LORA_DIO2` used as `BUSY` **[MT]** |
-| **Meshnology W12** | Meshnology | Meshtastic variant `variants/esp32s3/meshnology-w12/` **[MT]** |
-| **Wio-LR2021** RF board (in `LR2021EVK2*`) | Semtech / Seeed | Semtech's own EVK radio board; the only target USP calls *Validated* **[DRV]** |
-| **Waveshare `Core2021-LF/-HF/-XF`** | Waveshare | Product page **[DOC]**; used in community builds |
-| **NiceRF `LoRa2021F33-2G4`** (1 W) | NiceRF | **[COM]** — page 403s to automated clients |
-| `nrf52_promicro_diy_tcxo` | DIY | The Meshtastic variant PR #10401 landed against **[MT]** |
-| LilyGo T-Display P4 LR2021 | LilyGo | **[COM]**, hearsay; availability unconfirmed |
-
----
-
-## 14. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf` | 5 809 234 | `0d9051db78b243bf89db7ff00bc549ff1fe3ffedc6e08649c9081e8393ef00b7` | **`DS.LR20xx`, LR2021/LR2022/LR2012 Final Datasheet Rev. 2.1, `13/04/26`, 243 pp.** The current retained revision |
-| ~~`artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf`~~ **archived 2026-09-04** | 5 158 757 | `926b88cbfb6434e3954569b3f0d96e47c3ca2952245ebc1d01f65ab52d382ff7` | **`DS.LR2021`, LR2021 Final Datasheet Rev. 1.1, `10/14/25`, 236 pp.** Superseded; kept because it differs in substance — [placeholder](artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md) |
-| `artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz` | 106 656 | `f1f172ce871a183d8d6431c157e0d44b457057ccd0c9e4d0e1c98bf76a3493ee` | **Semtech `lr20xx_driver` v2.0.2** plus the USP top-level `README.md`, `CHANGELOG.md`, `LICENSE.txt`, `LICENSES.txt`. 70 files, 688 630 B uncompressed |
-
-### 14.1 Datasheet Rev 2.1 — provenance
-
-| Field | Value |
-|---|---|
-| Document number / revision | **`DS.LR20xx`**, **Final Datasheet Rev. 2.1** |
-| Publication date | **`13/04/26`** (running footer); PDF `/CreationDate` `D:20260413161603Z` |
-| Pages | **243** |
-| Retrieval date | **2026-09-04** |
-| Byte size | **5 809 234** |
-| SHA-256 | `0d9051db78b243bf89db7ff00bc549ff1fe3ffedc6e08649c9081e8393ef00b7` |
-| **Canonical URL** | `https://semtech.my.salesforce.com/sfc/p/E0000000JelG/a/RQ00000EZ5fu/L1sOvqDN_QMyCWYAAychIL5ygPsQw1AEq7xzcvpGNZg`, linked from `https://www.semtech.com/products/wireless-rf/lora-plus/lr2021`. ⚠ **`blocked`** — JS/POST content-distribution shell, see [`vendors/semtech/README.md` §4](../../../vendors/semtech/README.md) |
-| **Digi-Key mirror (working)** | `https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/8924/600_62785538.LR20xxDatasheet_V2_1.pdf` — HTTP 200, `application/pdf`, no UA games needed |
-| Second independent source | Wayback capture of the Digi-Key URL, submitted 2026-09-04 |
-| **Mirror lag** | ⚠ **`unresolved`.** Semtech lists **v2.2 dated 2026-08-08**; Digi-Key serves v2.1. A v2.2 exists but could not be retrieved (G1) |
-| PDF metadata | `/Title` `LR20xxDatasheet_V2_1.pdf`, `/Author` `oprevost`, `/Creator` `FrameMaker 17.0.3`, `/Producer` `Adobe PDF Library 17.0`, `/ModDate` `D:20260413193222+02'00'` |
-| Licence | **`unknown`** — © Semtech Corporation; every page footed **"Semtech Proprietary & Confidential"**, plus the LR-FHSS patent notice (G13) |
-| Redistribution status | **`unknown`** — ⚠ a "Proprietary & Confidential" marking on a document that two authorised distributors mirror openly is a genuine conflict, not an oversight. Recorded, not resolved |
-| Disposition | **`repository`, unstaged** pending review |
-| Type validated | Yes — magic bytes `%PDF-1.6`; 243 pages parsed by `pypdf`; running footer cross-checked on every quoted page |
-
-### 14.2 Datasheet Rev 1.1 vs Rev 2.1 — which is which
-
-Same part, two revisions, **two different SHA-256 values and two different page counts**, and the
-differences are substantive. Rev 2.1's own revision history:
-
-| Version | Date | Change |
-|---|---|---|
-| 0.2 | June 2025 | Preliminary release |
-| **1.1** | **October 2025** | Final datasheet; clarifications throughout |
-| **2.1** | **April 2026** | Expanded to cover LR2022 and LR2012; **+0.5 dB added to all sensitivity numbers in Tables 3-13 and 3-18**; FLRC bandwidth values corrected in three places; **new command `SetLoraTxSync`**; **new §11.1.3 (G)FSK Limitations**; **new §22.3 Firmware Patch RAM**; `IDDSL1` sleep current changed; 434/490 MHz transmit table changed; Z-Wave typical sensitivities changed; electrical conditions clarified to *"no shield, SIMO"*; reference-design figure updated |
-| 2.2 | 2026-08-08 | ⚠ **not obtained** (G1) |
-
-**Rev 2.1 is authoritative. Rev 1.1 is the record of what Semtech said first**, and the only way to
-tell whether a 2025-vintage board or driver was designed against numbers that no longer hold.
-
-### 14.3 `lr20xx_driver` snapshot — provenance
-
-| Field | Value |
-|---|---|
-| Upstream | `github.com/LoRa-Net/usp` (`Lora-net/usp` is the same org, case-insensitive) |
-| **Commit** | **`512a095e303872f900021361a619b7b1e6e29469`** |
-| Release tag | **`v1.1.2-feature-202604`**, published **2026-04-16T15:17:08Z** |
-| Driver version string | **`v2.0.2`** — `smtc_rac_lib/radio_drivers/lr20xx_driver/inc/lr20xx_driver_version.h` |
-| Driver changelog date | **2026-04-07** |
-| Licence | **BSD-3-Clause-Clear** (`The Clear BSD License`, © Semtech Corporation 2022/2025). ⚠ GitHub's repo-level label is `NOASSERTION` because the monorepo is mixed-licence; the driver subtree carries its own `LICENSE.txt` |
-| Redistribution status | **`allowed`**, conditional on preserving the copyright notice and the disclaimer — both are inside the tarball verbatim |
-| Disposition | **`repository`** |
-| Contents | The complete `smtc_rac_lib/radio_drivers/lr20xx_driver/` subtree (66 files) plus USP's top-level `README.md`, `CHANGELOG.md`, `LICENSE.txt`, `LICENSES.txt` |
-| Why a subtree, not the repo | The full `usp` tree is **47 768 093 B** across 1 419 files, overwhelmingly `examples/` (977 files). The driver and its licence are what this record cites |
-| Reacquisition | `gh api repos/LoRa-Net/usp/git/trees/512a095e303872f900021361a619b7b1e6e29469?recursive=1`, then `raw.githubusercontent.com/LoRa-Net/usp/512a095e.../<path>`. Also `https://github.com/LoRa-Net/usp/releases/tag/v1.1.2-feature-202604` |
-
----
-
-## 15. Related components
-
-- [**Semtech SX1262**](../sx1262/README.md) — **Gen 2**, the part every board in this repository actually has. Read it for what the migration is *from*
-- [**Semtech LR1121**](../lr1121/README.md) — **Gen 3**, multi-band with GNSS and Wi-Fi scanning and the crypto engine Gen 4 dropped
-- [**Semtech LR1110 / LR1120**](../lr11x0/README.md) — the rest of the Gen-3 LoRa Edge line
-- [**Semtech SX1276 / SX127x**](../sx1276/README.md) — **Gen 1**, and the generation the LR2021 has explicit compatibility shims for
-- [**Semtech SX1268**](../sx1268/README.md) · [**Semtech LLCC68**](../llcc68/README.md) — Gen-2 SX1262 siblings, and a real substitution trap
-- [**`guides/hardware/lora-radio-generations.md`**](../../../guides/hardware/lora-radio-generations.md) — **start here** for the four generations side by side
-- [**`vendors/semtech/README.md`**](../../../vendors/semtech/README.md) — how to get Semtech documents, what is gated, and what lies to you
-- [**`projects-and-community.md`**](projects-and-community.md) — RadioLib and Meshtastic support with exact commits, evaluation kits, and what people report in the field
-- [Components index](../../README.md)
-
----
-
-## 16. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | LR2021/LR2022/LR2012 Datasheet | **Semtech**, mirrored by **Digi-Key** | authorized mirror | datasheet | `artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf`; `mm.digikey.com/Volume0/opasdata/d220001/medias/docus/8924/600_62785538.LR20xxDatasheet_V2_1.pdf` | 2026-09-04 | **`DS.LR20xx` Rev 2.1, 13/04/26**, 243 pp | §1–§8, §10 — including **§23.8, the generation list** |
-| S-2 | LR2021 Datasheet | **Semtech**, mirrored by **Mouser** | authorized mirror | datasheet | [archived](artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md); `mouser.com/pdfDocs/61979758LR2021_V1_1_datasheet.pdf` (⚠ WhatsApp UA) | 2026-09-04 | **`DS.LR2021` Rev 1.1, 10/14/25**, 236 pp | §14.2 — corroborates §23.8 independently; G2 |
-| S-3 | LoRa Plus™ LR2021 product page | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-plus/lr2021` | 2026-09-04 | datasheet entry **v2.2, 2026-08-08** | §1.1 (page title), §11.2 document list, G1 |
-| S-4 | Semtech product sitemap | Semtech | primary | sitemap | `www.semtech.com/sitemap-products.xml` | 2026-09-04 | — | §1.2 — the **`lora-plus`** family exists and holds LR2012/LR2021/LR2022; LR2021 is **not** under `lora-connect` |
-| S-4b | Semtech document catalogue — 1 984 entries embedded as JSON in the Development Support Documents page | Semtech | primary | machine-readable index | `www.semtech.com/design-support/development-support-documents/` (`var doc_portal`) | 2026-09-04 | dates 2018-11-14 … 2026-08-25 | G1 (the product page's *Datasheet* link is catalogued as **v2.2, 2026-08-08**), §11.2, G15. Extraction method in [`vendors/semtech/README.md` §3.2](../../../vendors/semtech/README.md) |
-| S-5 | Semtech Salesforce content-distribution endpoint | Semtech | primary | download shell | `semtech.my.salesforce.com/sfc/p/E0000000JelG/a/RQ00000EZ5fu/…` | 2026-09-04 | — | G1 — **negative result**, `executed-failed`; analysed in the vendor guide |
-| S-6 | `LoRa-Net/usp` — Unified Software Platform, incl. `lr20xx_driver` | Semtech | primary | source | `artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz`; `github.com/LoRa-Net/usp` @ `512a095e303872f900021361a619b7b1e6e29469` | 2026-09-04 | driver **v2.0.2**; release `v1.1.2-feature-202604`, 2026-04-16; **BSD-3-Clause-Clear** | §7, §9, §9.1, G7, G8, G11 |
-| S-7 | RadioLib | jgromes | community | source | `github.com/jgromes/RadioLib`, `src/modules/LR2021` | 2026-09-04 | first release **7.6.0**, 2026-02-19; first commit `2472fbdf…`, 2025-06-09 | §3.2, §9, §11 |
-| S-8 | Meshtastic firmware | Meshtastic | community | source | `github.com/meshtastic/firmware`, PR #10401 → `5e2ca8aed4239f6682dede26485c63fcb2fdd521` | 2026-09-04 | merged **2026-05-08**; absent from v2.7.26, present in v2.8.0.* | §9, §13 |
-| S-9 | `Core2021-XF/-HF/-LF` product page | Waveshare | primary | store listing | `www.waveshare.com/Core2021-XF.htm` | 2026-09-04 | US$11.99 / US$12.99 | §11.1; **G3** — independent assertion of no AES / no secure key storage |
-| S-10 | LR2021 LoRa Plus Evaluation kit 915 MHz US V2.0 | Seeed Studio | primary | store listing | `www.seeedstudio.com/LR2021-LoRa-Plus-Evaluation-kit-915Mhz-US-V2-0-p-6698.html` | 2026-09-04 | **US$99.00** | §11.1 |
-| S-11 | Reddit / community corpus | various | community | forum | catalogued in [`projects-and-community.md`](projects-and-community.md) | 2026-09-04 | 2025-03-12 … 2026-09-02 | §11 timeline; firsthand bench reports |
-| S-12 | `www.nicerf.com/lora-module/lora2021f33-2g4.html` | NiceRF | primary | store listing | — | 2026-09-04 | — | **negative result**: HTTP **403** to both the Chrome and WhatsApp agents |
diff --git a/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf b/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf
deleted file mode 120000
index 9595fd8..0000000
--- a/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf
\ No newline at end of file
diff --git a/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.link b/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.link
deleted file mode 120000
index 1fa014e..0000000
--- a/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-lr2021-datasheet-v1.1-mouser-mirror.pdf
\ No newline at end of file
diff --git a/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md b/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md
deleted file mode 100644
index 3e875de..0000000
--- a/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# ARCHIVED: `lr2021-datasheet-v1.1-mouser-mirror.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-07**.
-
-**Reason:** Superseded datasheet revision (Rev 1.1, DS.LR2021, 2025-10-14, 236 pp) retained per the keep-both-revisions rule because it differs from Rev 2.1 in substance, not only formatting. 5.16 MB alongside the 5.81 MB Rev 2.1 copy is more weight than one chip warrants in-repo; Rev 2.1 is the current document and stays.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf` |
-| Archived to | `archive/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf` (the path after `archive/` is the path it had here) |
-| Type | file |
-| Size | 5,158,757 B (4.92 MiB) |
-| SHA-256 | `926b88cbfb6434e3954569b3f0d96e47c3ca2952245ebc1d01f65ab52d382ff7` |
-| Last modified (mtime) | 2026-09-07 10:31:43Z |
-| Author / committer | Semtech Corporation (PDF /Author 'julie') |
-| Commit date | 2025-10-13 (PDF CreationDate D:20251013170105Z) |
-| License | unknown - (c) Semtech Corporation, marked 'Proprietary & Confidential' on every page |
-| Document identity | **`DS.LR2021`, Final Datasheet Rev. 1.1, dated `10/14/25`, 236 pages.** PDF `/Title` `LR2021_V1_1_datasheet.pdf`, `/Creator` FrameMaker 17.0.4, `/Producer` Adobe PDF Library 17.0 |
-| Type validated | Yes — magic bytes `%PDF-1.6`, 236 pages parsed with `pypdf` |
-
-## How to get it back
-
-**Three independent routes, best first.** None of them is Semtech's own site: Semtech's
-canonical link for this document is a Salesforce content-distribution shell that no
-non-browser client has been able to get bytes out of (see
-[`vendors/semtech/README.md` §4](../../../../vendors/semtech/README.md)).
-
-| # | Source | URL | Verified |
-|---|---|---|---|
-| 1 | **Mouser Electronics mirror** — where this copy came from | `https://www.mouser.com/pdfDocs/61979758LR2021_V1_1_datasheet.pdf` | 2026-09-04, HTTP 200, `application/pdf`, 5 158 757 B. ⚠ **Requires a non-default User-Agent** — see below |
-| 2 | **Wayback Machine** capture of the Mouser URL | `https://web.archive.org/web/2026/https://www.mouser.com/pdfDocs/61979758LR2021_V1_1_datasheet.pdf` | submitted to `web.archive.org/save/` 2026-09-04 because Mouser is bot-hostile and a single-host recovery path is one outage from useless |
-| 3 | **Semtech product page** (canonical, but gated) | `https://www.semtech.com/products/wireless-rf/lora-plus/lr2021` → *Documents* → *Datasheet*. ⚠ Now serves **v2.2**, not v1.1 — Semtech does not publish superseded revisions. **This route cannot return this file.** Recorded so nobody wastes an hour on it | 2026-09-04 |
-
-⚠ **Mouser blocks the ordinary browser User-Agent for this path and serves the WhatsApp
-link-preview agent.** This is the reverse of the usual pattern and it is not a typo:
-
-```bash
-# 403 + a 13 895-byte "Access Denied / captcha" HTML page, saved with a .pdf name if you are careless
-curl -sSL -A 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36' \
-     -o out.pdf 'https://www.mouser.com/pdfDocs/61979758LR2021_V1_1_datasheet.pdf'
-
-# 200 application/pdf, 5 158 757 B  <- this one
-curl -sSL -A 'WhatsApp/2.23.20.0' \
-     -o out.pdf 'https://www.mouser.com/pdfDocs/61979758LR2021_V1_1_datasheet.pdf'
-sha256sum out.pdf   # 926b88cbfb6434e3954569b3f0d96e47c3ca2952245ebc1d01f65ab52d382ff7
-```
-
-The `61979758` prefix is Mouser's own opaque document id. It is **not derivable** from the
-part number — it was recovered from a search-engine index. Guessed filenames
-(`LR2021_datasheet.pdf`, `DS_LR2021_V1.0.pdf`) return HTTP **403** with a 1 140-byte body,
-`executed-failed` 2026-09-04.
-
-Restore from the local archive if you have it:
-
-```bash
-mv "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")/../repo-archive/hardware-doc/components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf" \
-   components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf
-```
-
-## Why this revision was kept rather than discarded
-
-Rev 1.1 and Rev 2.1 are **not the same document with a new date**, and the differences are
-the kind that silently invalidate a design:
-
-- Rev 1.1 is titled **`LR2021 Datasheet`** and covers **one part**. Rev 2.1 is
-  **`LR2021/LR2022/LR2012 Datasheet`** (`DS.LR20xx`) and covers three, with per-part
-  feature exclusions. A "the datasheet says…" claim sourced from Rev 1.1 has no
-  LR2022/LR2012 column to be wrong about; the same claim in Rev 2.1 might.
-- **A published sensitivity figure moved.** Rev 1.1 front page: FLRC sub-GHz
-  **−101.5 dBm @ 1.95 Mbps**. Rev 2.1 front page: **−100.5 dBm @ 1.95 Mbps**. 1 dB worse,
-  no erratum, no callout in the revision history beyond a general "Added 0.5dB to all
-  sensitivity numbers in Table 3-13 and Table 3-18".
-- Rev 2.1's own revision history lists further substantive edits — FLRC bandwidth values in
-  three tables, a new `SetLoraTxSync` command, a new §11.1.3 "(G)FSK Limitations", a new
-  §22.3 "Firmware Patch RAM (PRAM)", changed `IDDSL1` sleep current, changed 434/490 MHz
-  transmit numbers, and changed Z-Wave typical sensitivities.
-
-So: **Rev 2.1 is authoritative; Rev 1.1 is the record of what Semtech said first**, and is
-the only way to tell whether a 2025-vintage board or driver was designed against numbers
-that no longer hold.
-
-## Documented in
-
-The full provenance table, both revisions side by side, is in the component record:
-[`components/semtech/lr2021/README.md` §14](../README.md#14-local-artifacts).
diff --git a/components/semtech/lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf b/components/semtech/lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf
deleted file mode 100644
index 8717e22..0000000
Binary files a/components/semtech/lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf and /dev/null differ
diff --git a/components/semtech/lr2021/artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz b/components/semtech/lr2021/artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz
deleted file mode 100644
index 8aaaded..0000000
Binary files a/components/semtech/lr2021/artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz and /dev/null differ
diff --git a/components/semtech/lr2021/projects-and-community.md b/components/semtech/lr2021/projects-and-community.md
deleted file mode 100644
index 28afdd0..0000000
--- a/components/semtech/lr2021/projects-and-community.md
+++ /dev/null
@@ -1,280 +0,0 @@
-# LR2021 — ecosystem, software support and community
-
-Companion to [`README.md`](README.md). Everything here is dated and attributed. Community reports
-carry an explicit evidence class; nothing on this page is authoritative about the silicon.
-
-**Evidence classes used below**, per the repository convention:
-
-| Label | Meaning |
-|---|---|
-| **firsthand-measurement** | The poster measured something and says how |
-| **firsthand-ownership** | The poster has the hardware and reports use, without measurement |
-| **informed-interpretation** | Reading of a document or source by someone who plainly understands it |
-| **hearsay** | Repeating something heard elsewhere |
-| **vendor claim** | A vendor asserting something about its own product |
-
-Anecdotes establish that an experience occurred, not how common it is. The sample here is
-**25 Reddit threads matching `LR2021`** returned by `old.reddit.com/search.json?q=LR2021&sort=new`
-on 2026-09-04, of which **9 were read in full with their comment trees**. That is the whole sample;
-prevalence claims are not made from it.
-
----
-
-## 1. RadioLib — the exact commit and release
-
-`github.com/jgromes/RadioLib` · **MIT** (`license.txt`, "MIT License / Copyright (c) 2018 Jan
-Gromeš" — verified identical at tags `7.2.1` and `7.7.1`, 2026-09-04) · 2 565 stars.
-
-| Milestone | Detail |
-|---|---|
-| **Feature request** | Issue **#1457**, *"Feature Request: Support for Semtech LR2021"*, opened by **@serialrf433** on **2025-03-13** — the day after Semtech's announcement |
-| **First code** | `2472fbdf727e7263167bdc511f2bd0744194dd33` — *"[LR2021] Initial WIP commit"*, **2025-06-09**, @jgromes |
-| **Sustained work begins** | `f203c77c161c02fa4e02e9c8c4a402b1e0c6660c` *"[LR2021] Add first few SPI commands"*, **2025-10-12** |
-| **New base class** | `d696fed842bc77c6699ac83d9611a7d6e1c838d6` — ***"[LRxxxx] Create base class for common LR11xx and LR20xx commands"***, **2025-10-13**. ⚠ Read that carefully: the shared ancestor RadioLib chose for the LR2021 is **LR11xx**, not SX126x |
-| **The PR** | **#1676**, *"[LR2021] Add support for LR2021"*, @jgromes, opened **2026-01-17**, **merged 2026-01-30** as `013b0a114f7f29a455a7ae64b2e6db5e382f67e0`. Closes #1457 |
-| **First release containing it** | **7.6.0, 2026-02-19.** Release notes list ***"[LR2021] Add support for LR2021 (#1676) (#1457)"*** |
-| **Verified absent from** | 7.2.1, 7.3.0, 7.4.0, **7.5.0** — `src/modules/LR2021` returns HTTP 404 at each of those refs, and `LR2021` appears 0 times in `keywords.txt` and in `src/RadioLib.h`. Present with 15 files at 7.6.0, 7.7.0 and 7.7.1 |
-
-**So: if you want RadioLib LR2021 support, pin ≥ 7.6.0.** 7.5.0 (2026-01-10) is only six weeks
-earlier and has nothing.
-
-### 1.1 What the module contains
-
-15 files, ~250 KB of source, split one file per PHY — which mirrors the chip's own command grouping:
-
-```
-LR2021.cpp  LR2021.h  LR2021_commands.h  LR2021_config.cpp  LR2021_registers.h  LR2021_types.h
-LR2021_cmds_{chip_control,flrc,gfsk,lora,misc,ook,oqpsk,radio,ranging}.cpp
-```
-
-`LR2021_commands.h` alone is 48 984 B and `LR2021_config.cpp` 45 527 B — a fair measure of how much
-new surface Gen 4 presents compared with a Gen-2 driver.
-
-### 1.2 Post-release work, and who is doing it
-
-The 7.6.0 change log is dominated by LR2021 fixes from **@lyusupov** (SoftRF) — implicit/explicit
-LoRa header type (#1678), `DIO5` pull-up restriction (#1685), GFSK payload-length unit (#1687),
-GFSK sync-word byte order (#1686), GFSK deviation and bit-rate limits clamped to the datasheet
-(#1689, #1690), no-CRC GFSK/OOK with the inverted bit set (#1688). Later, **@caveman99** (a
-Meshtastic core developer) lands `lr2021-cr-constants` (#1850, merged 2026-08-11) and
-**@fabianbschmid** FLRC RSSI (#1816).
-
-**Read that as a maturity signal, in both directions.** A stream of "set max limit … in accordance
-with datasheet" fixes in the *first* release after merge means the initial implementation was
-written against the command reference rather than against silicon; it also means several people
-with hardware were exercising it hard within weeks. As of `267d4e95f30947bb86cd49c249c18c249a7cc19a`
-(**2026-08-12**, *"[LR2021] Fix temperature readout"*) commits were still landing — **135 commits
-touch `src/modules/LR2021`** between 2025-06-09 and 2026-08-12.
-
-### 1.3 A capability nobody expected: ADS-B
-
-PR **#1700**, *"[ADS-B] ADS-B support (LR2021 only)"*, @jgromes, merged **2026-02-19** into 7.6.0.
-RadioLib can receive 1090 MHz ADS-B on this part and on no other. ⚠ Note the tension: RadioLib's
-own `setFrequency()` documentation states the allowed ranges as **150.0–960.0 MHz, 1900–2200 MHz and
-2400–2500 MHz**, which does not include 1090 MHz, and the datasheet's sub-GHz path stops at 960 MHz.
-**Unresolved** — this record has not established how the ADS-B path is reached, and it was not
-tested. Related community interest: r/ADSB `1tpy1zv` *"low power ADSB RX chip"*, 2026-05-28.
-
-### 1.4 ⚠ A documented conflict between RadioLib and the datasheet
-
-| Source | Says |
-|---|---|
-| **[DS]** Table 3-4, `IDDSBRLD` | `STDBY_RC` runs the **"Internal HFRC(32MHz)"** |
-| RadioLib `LR2021.h` doc comment | *"uses **13 MHz RC oscillator**"* / `RADIOLIB_LR2021_STANDBY_RC (13 MHz RC oscillator)` |
-
-Recorded, not resolved. It is a comment, not a register write, so it is very likely inert — but it
-is the kind of thing that gets copied into someone's timing calculation. `not-tested`.
-
----
-
-## 2. Meshtastic — supported, but only on the 2.8 line
-
-`github.com/meshtastic/firmware`.
-
-| Milestone | Detail |
-|---|---|
-| **Announcement reaction** | The **official @meshtastic Reddit account** posted the announcement on **2025-03-12**: *"Semtech announced their 4th gen #LoRa chip! … and they specifically mentioned Meshtastic! This is big news! 🎉 … We can't wait to get hardware that supports this chip."* (82 pts, 23 comments) — **vendor/project claim** |
-| **The PR** | **#10401**, *"LR2021 radio on NRF_Promicro"*, by **@NomDeTom**, opened **2026-05-06**, **merged 2026-05-08** as `5e2ca8aed4239f6682dede26485c63fcb2fdd521` |
-| **What it added** | `LR2021_RADIO` in `src/detect/LoRaRadioType.h`; new `LR2021Interface` **and a generic `LR20x0Interface` base class**, described in the PR body as *"based on the LR11x0 and LR1110"*; radio-detection logic; the `nrf52_promicro_diy_tcxo` variant |
-| **Release status** | ⚠ **`LR2021Interface.cpp` is absent from `v2.7.26.54e0d8d`** (2026-06-24, the last non-prerelease of the 2.7 line) and `LR2021_RADIO` is absent from its `LoRaRadioType` enum — verified by reading both at that tag. It **is** present in `v2.8.0.47db0e3` (2026-09-01, prerelease). **LR2021 is a 2.8.x feature** |
-| **Portduino / native Linux** | PR **#11252** *"add LR 2021 to portduino …"*, merged **2026-07-30** (`047c4e9feb9b`). Still-open follow-ups: **#11382** *"Portduino: Fix LR2021 switch tables, power ceilings and IRQ handling"* (2026-08-10), **#11138** *"feat(lr2021): enable LR2021 LoRa radio support on native/portduino"* (2026-07-22) |
-| **Ongoing** | 35 issues/PRs mention LR2021; recent ones include `fix(lr2021): live LF↔HF reconfigure via full begin()` (#11279, 2026-07-29), `enable autoLDRO on LR2021` (#11139, 2026-07-22), `fix(radio): validate 2.4 GHz bandwidths` (#11317, open) |
-
-### 2.1 Boards upstream
-
-`USE_LR2021` appears in three variants plus Portduino glue:
-
-| Variant | Notes from `variant.h` |
-|---|---|
-| `variants/nrf52840/seeed_mesh_tracker_X1/` | **SenseCAP MeshTracker X1.** `LR2021_DIO3_TCXO_VOLTAGE 1.6`; `LORA_DIO2` (P0.07) wired as **`BUSY`**; `LORA_DIO1` (P1.01) as IRQ; `// #define LR2021_DIO_AS_RF_SWITCH` **commented out**. Also `rfswitch.h` |
-| `variants/esp32s3/meshnology-w12/` | Meshnology W12 |
-| `variants/nrf52840/diy/nrf52_promicro_diy_tcxo/` | The DIY board PR #10401 landed against |
-
-⚠ **`LR2021_DIO3_TCXO_VOLTAGE` is a misleading name inherited from the SX126x world.** On this part
-the TCXO is supplied from the dedicated `VTCXO` pin and configured by `SetTcxoMode`, not by "DIO3"
-(see [`README.md` §2, §6.2](README.md)). The constant is RadioLib's API shape, not a pin mapping.
-
-### 2.2 Meshtastic's practical position, in one line
-
-Supported, actively worked on, shipping on real hardware — and **not yet in a stable release**. A
-user on the 2.7 stable channel has no LR2021 support at all. When @DanRTD asked
-*"Any idea when the new LR2021 based nodes will be available to buy?"* (r/meshtastic `1tcb7ni`,
-2026-05-13), **@NomDeTom — the author of PR #10401 — replied five days after merging it**:
-*"They're supported now, in develop. Radio modules are available now."* (**firsthand-ownership**,
-and about as authoritative as a forum reply gets.)
-
----
-
-## 3. Semtech's own software
-
-| Repo | What | Licence | Last push |
-|---|---|---|---|
-| **`LoRa-Net/usp`** | *"MCU FW SW driving LR20xx multi-PHY radios with multiprotocol operations and radio resource arbitration. Includes LoRa Basics Modem. **Backward-compatible with SX126x and LR11xx radio devices**."* Contains `lr20xx_driver` v2.0.2 | repo `NOASSERTION` (mixed); **driver subtree is BSD-3-Clause-Clear** | 2026-04-16 |
-| **`LoRa-Net/usp_zephyr`** | Zephyr RTOS integration of USP; *"Compatible with LR20xx, SX126x and LR11xx"* | NOASSERTION | 2026-04-16 |
-| **`LoRa-Net/LoRaStudio`** | *"Software designed to demonstrate LoRa Plus series capabilities"* — Windows GUI. Semtech's LR2021 page links `LoRaStudio_UserGuide.pdf` and `LoRaStudio_Windows_Setup.exe` **directly from GitHub**, not from Salesforce | none declared | 2026-06-26 |
-| **`LoRa-Net/swdm031_img_xfer`** | *"Image transfer with FLRC long packet"* — the demo everyone asking about camera links is pointed at | NOASSERTION | 2026-02-10 |
-| **`LoRa-Net/SWL2001`** | LoRa Basics Modem LoRaWAN stack (bundled in USP as 4.9.0) | BSD-3-Clause-Clear | 2025-10-15 |
-| ⚠ `LoRa-Net/LoRaMac-node` | The classic reference LoRaWAN node | NOASSERTION | **2024-07-03 — predates the part** |
-
-⚠ **There is no `lr2021_driver` repository.** Every other generation has a standalone one —
-`sx126x_driver`, `llcc68_driver`, `SWDR005` (SX128x), `lr1110_driver`, `SWDR001` (LR11xx). Gen 4's
-driver ships only inside the 47 MB USP monorepo, whose README says *"not intended for production
-use"*. Releases: `v0.5.1-alpha` (2025-10-15), **`v1.0.0` (2025-12-16)**, `v1.1.1-feature-202602`
-(2026-03-02), `v1.1.2-feature-202604` (2026-04-16). `LoRa-Net` and `Lora-net` are the same GitHub
-org (case-insensitive) and return identical repository lists.
-
----
-
-## 4. Evaluation kits and modules
-
-| Part | What is in the box | Price (date) |
-|---|---|---|
-| **`LR2021EVK2XBS1`** | LR2021/LR2022 LoRa Plus EVK, **2 × `LR2021RF2XDS1`** RF boards, **EU 868 MHz + 2.4 GHz** | not published without JS |
-| **`LR2021EVK2XCS1`** | as above, **NA 915 MHz + 2.4 GHz** | " |
-| **`LR2021EVK2XGS1`** | **2 × `LR2021RF2XGS1`**, **CN/Asia 490 MHz + 2.4 GHz** | " |
-| `LR2021EVK1XGS1` | earlier EVK1 generation, still listed | " |
-| **Seeed "LR2021 LoRa Plus Evaluation kit 915 MHz US V2.0"** | **nRF54L15 + Wio-LR2021 + OLED + 2 SMA antennas + USB cable, ×2** | **US$99.00** (2026-09-04) |
-| **Waveshare `Core2021-LF` / `-HF` / `-XF`** | bare LR2021 module, per-band SKU | **US$11.99 / US$12.99** (2026-09-04) |
-| **NiceRF `LoRa2021F33-2G4`** | LR2021 + external PA, ~1 W | page **403s** to automated clients |
-
-⚠ **The `Wio-LR2021` is Semtech's own EVK radio board, not a Seeed original.** Semtech's USP README
-names the validated platform as *"LoRa Plus EVK (LoRa Plus Expansion Board + **Wio-LR2021**/Wio-LR2022/Wio-LR2012 radios)"*.
-Seeed sells it; Semtech validates against it. Also from that README: **the CN 490 MHz `Wio-LR20xx`
-needs a different PA table** from the 868/915 boards, per the datasheet's page-134 CN-490 entry.
-
-**On the $99 kit's value**, since it looks expensive next to a $12 module — @Fir3, 2026-06-27:
-*"The $100 is for two of these. So that means for $50 you get the nRF54L15, the LR2021, board
-connecting them, oled screen, sma connections for the antennas, 2 antennas and a usb cable."*
-(**firsthand-ownership**.) A dissenting first take from @The_Cat_Commando in the same thread was
-withdrawn once the two-pack was pointed out.
-
----
-
-## 5. What people actually report
-
-### 5.1 Firsthand measurement
-
-| Date | Who / where | Report | Class |
-|---|---|---|---|
-| **2026-06-05** | u/Time-Guidance-5150, r/meshcore [`1txo9ii`](https://old.reddit.com/r/meshcore/comments/1txo9ii/) (22 pts) | Bench-tested a **NiceRF `LoRa2021F33-2G4` 1 W module** (LR2021 + ESP32-S3 + 5 V/3 A supply) as a MeshCore node against a **RAK 1 W / SX1262** kit at the same power setting: *"I'm seeing 15-16 dB in indoor tests (vs 12-13 on Rak 1W / sx1262)"*, and later *"Early results are roughly **+2 dBm for tx/rx** compared to Rak 1W with same power setting."* Full config given: *"30 dBm TX, raw power 44, PA duty/slices 2/7, 128 µs ramp, RX boost 7, DIO6 LF-TX switch, DIO9 IRQ, TCXO 3.3 V, calibrate 0x6F, frontend cal at 912 MHz extended frequency-error mode on"* | **firsthand-measurement** — ⚠ SNR-vs-dBm units are used loosely, the comparison unit's true output was disputed in-thread by u/IAmSoWinning (5 V rail vs battery boost path on the RAK), and the promised detailed report was not posted within the search window. **Suggestive, not conclusive** |
-| **2026-06-26** | u/Fir3, r/meshtastic [`1ugfytv`](https://old.reddit.com/r/meshtastic/comments/1ugfytv/) (177 pts) | Seeed nRF54L15 + Wio-LR2021 kit running a **Zephyr-based Meshtastic fork** (`github.com/dasmensch-su/Meshtastic-nRF54L15-LR2021-Multi-SF` — note *Multi-SF* in the name). Power: *"5 V at .01 A (50 mW) or less consistently"* through a DC boost | **firsthand-measurement**, coarse (whole-node, at the boost converter's input) |
-| **2026-09-02** | u/accur4te, r/Lora [`1w519gm`](https://old.reddit.com/r/Lora/comments/1w519gm/) | **A negative result, and the most useful post in the corpus.** ESP32 + Waveshare `Core2021LF`, FLRC 260 kbps, aiming at 500 m+ for 150–200 KB JPEGs in woodland; **getting ~100 m**. Measured: *"-100 to -110 RSSI … 1 m RSSI was -30 and when put the nodes at 50 m apart LOS I went directly to -90 RSSI"*. Code published: `github.com/vedantjadhavkudrat/flrc_public_test_code` | **firsthand-measurement.** −30 dBm at 1 m and −90 dBm at 50 m is ~60 dB over a 34 dB free-space delta — the thread's diagnosis (antenna/Fresnel/init) is unresolved as of the search date |
-
-### 5.2 Comparative context offered by experienced posters
-
-u/StuartsProject, r/Lora [`1u6ldii`](https://old.reddit.com/r/Lora/comments/1u6ldii/), 2026-06-17 —
-**SX1280** measurements offered as the baseline an LR2021 FLRC design should beat
-(**firsthand-measurement**, on Gen-2 2.4 GHz silicon, *not* on an LR2021):
-
-| Type | Frequency | Settings | File | Transfer time |
-|---|---|---|---|---|
-| LoRa | 434 MHz | SF7 BW500k CR4:5 | 46 000 B | 26.3 s |
-| LoRa | 2.4 GHz | SF5 BW1600k CR4:5 | 46 000 B | 3.4 s |
-| FLRC | 2.4 GHz | BR260 BW1_2 CR_0_3 | 46 000 B | 3.9 s |
-| FLRC | 2.4 GHz | BR1300 BW1_2 CR_1_0 | 46 000 B | 1.9 s |
-
-and separately: *"Using an ESP32 and the FLRC in 1,300,000 bps mode the achieved transfer rate was
-673,027 bps"* — i.e. **~52 % of the nominal rate** once acknowledgement and framing are counted.
-His advice to an LR2021-curious asker was, notably, **to start on an SX1280** because *"there is
-more support and libraries for the 2.4 GHz SX1280 so it might be an easier place to start."*
-(2026-06-18, **informed-interpretation**.)
-
-u/Clamsax, same thread, 2026-06-15 (**informed-interpretation**, clearly hands-on): the 2.6 Mbps
-figure *"is the raw data-rate of the payload part. It does not take into account the overhead of
-preamble+syncword+header+CRC … It also does not take into account use of FEC"*, and — usefully —
-on clocking: *"You can rely on the crystal oscillator of the LR2021, which should be less than
-±30 ppm, which can also be improved with the API `set_xosc_trim`."* That is the "no TCXO needed"
-claim being used in anger by someone planning a TDMA schedule.
-
-### 5.3 On migration and mesh compatibility
-
-The recurring worry is fragmentation, and the recurring answer is §8 of the component record.
-
-- u/304769 → u/Time-Guidance-5150, r/meshcore, 2026-06-06: *"Would this make our current HW garbage
-  due to incompatibility?"* → *"It should be compatible on subg band. I use it in experimental MC
-  repeater now."* (**firsthand-ownership**)
-- u/mosaic_hops, r/meshtastic, 2025-03-13 (19 pts) — the best early read anyone posted:
-  *"Multi-SF receive which could make a huge difference in mesh efficiency by enabling different SF
-  for both legs of an asymmetric link along with support for Very Long Slow **without a TCXO**. Also
-  some interesting opptys to use 2.4 GHz for near neighbors to take some load off of the Sub-GHz
-  band."* (**informed-interpretation** — and it identified the two features that turned out to
-  matter, 14 months before hardware.)
-- u/ShakataGaNai, r/meshtastic, 2025-03-13 (**informed-interpretation**, and a useful corrective):
-  *"This is nowhere close … These LoRa chips are integrated into larger packages by other parties,
-  which are then packaged up into something you can buy. Libraries need to be written for it,
-  firmwares built, etc."* He was roughly right about the shape and about the timescale — **~14
-  months from announcement to a pre-orderable Meshtastic node**.
-- u/rcarteraz, r/meshtastic, 2025-03-13 (**hearsay**): *"This radio isn't expected to be available
-  in quantity until the end of this year."* Broadly borne out.
-- u/wirecrossed, r/meshtastic, 2026-06-27 (**firsthand-ownership**): *"My Waveshare Core2021 came in
-  today and I will be pairing it with a Seeed nRF54L15 … I'll be interested to compare my
-  esp32s3/lr1121 setups for sure."*
-
-### 5.4 Product reception
-
-- **SenseCAP MeshTracker X1** pre-orders: r/meshtastic [`1uyur93`](https://old.reddit.com/r/meshtastic/comments/1uyur93/)
-  (2026-07-17, **395 pts**, 77 comments) and [`1v49g4p`](https://old.reddit.com/r/meshtastic/comments/1v49g4p/)
-  (2026-07-23, **170 pts**, 73 comments). By r/meshtastic standards this is a large reaction.
-- By 2026-09-05 the tone had moved on from novelty to configuration: r/meshtastic
-  [`1w82lwo`](https://old.reddit.com/r/meshtastic/comments/1w82lwo/) *"Recommended configs for the
-  new SenseCAP MeshTracker X1 as a GPS tracker?"* — the clearest sign it has become ordinary
-  hardware.
-- **RF-engineering-level interest**, which is unusual for a hobby part: r/rfelectronics
-  [`1qmp6op`](https://old.reddit.com/r/rfelectronics/comments/1qmp6op/) *"Measuring S11 parameter of
-  LR2021 LoRa transceiver"* (2026-01-25, 22 comments), and two threads
-  ([`1r68c5n`](https://old.reddit.com/r/rfelectronics/comments/1r68c5n/), 2026-02-16;
-  [`1r5t97o`](https://old.reddit.com/r/AskElectronics/comments/1r5t97o/), 2026-02-15) asking what the
-  **reference design** is doing and **why it ships without component values** — consistent with
-  §11.2 of the record: Semtech publishes the reference design, but behind the Salesforce gate.
-
-### 5.5 An honest summary of the community picture
-
-**Three things are consistently reported and one is consistently *not*.**
-
-Reported: (a) the part works, on real firmware, on buyable boards; (b) the FLRC headline rate is
-achievable only at roughly half the nominal figure once framing and FEC are counted, and its
-**range at sub-GHz has disappointed at least one careful tester**; (c) the migration is not
-mesh-breaking on plain LoRa.
-
-**Not reported by anyone: a controlled sensitivity or range comparison against an SX1262 with
-stated method.** The nearest thing is §5.1's `+2 dB` bench note, whose comparison unit's true
-output was disputed in the same thread. **Every performance claim in the component record is
-therefore a Semtech specification**, and the community has not yet independently confirmed the
-headline −141.5 dBm or the multi-SF advantage. `not-tested`.
-
----
-
-## 6. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | RadioLib repo, releases, commits, PR #1676, issue #1457 | jgromes | community | source | `github.com/jgromes/RadioLib` | 2026-09-04 | §1 |
-| C-2 | Meshtastic firmware, PR #10401, variants, tags | Meshtastic | community | source | `github.com/meshtastic/firmware` | 2026-09-04 | §2 |
-| C-3 | `LoRa-Net` org repository listing | Semtech | primary | source | `api.github.com/orgs/LoRa-Net/repos` | 2026-09-04 | §3 |
-| C-4 | USP README @ `512a095e…` | Semtech | primary | source | `raw.githubusercontent.com/LoRa-Net/usp/512a095e…/README.md` | 2026-09-04 | §3, §4 |
-| C-5 | LR2021 / EVK product pages | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-plus/…` | 2026-09-04 | §4 |
-| C-6 | LR2021 LoRa Plus Evaluation kit 915 MHz US V2.0 | Seeed Studio | primary | store listing | `www.seeedstudio.com/LR2021-LoRa-Plus-Evaluation-kit-915Mhz-US-V2-0-p-6698.html` | 2026-09-04 | §4 |
-| C-7 | `Core2021-XF` | Waveshare | primary | store listing | `www.waveshare.com/Core2021-XF.htm` | 2026-09-04 | §4 |
-| C-8 | Reddit corpus — 25 threads from `old.reddit.com/search.json?q=LR2021&sort=new`, 9 read with full comment trees | various | community | forum | permalinks inline | 2026-09-04 | §5. ⚠ `www.reddit.com` 403s automated clients; `old.reddit.com/search.json` with UA `WhatsApp/2.23.20.0` returns 200 |
-| C-9 | `dasmensch-su/Meshtastic-nRF54L15-LR2021-Multi-SF` | community | community | source | cited by C-8 `1ugfytv`; **not inspected this pass** | — | §5.1 — recorded as a lead |
-| C-10 | `vedantjadhavkudrat/flrc_public_test_code` | community | community | source | cited by C-8 `1w519gm`; **not inspected this pass** | — | §5.1 — recorded as a lead |
diff --git a/components/semtech/sx1262/README.md b/components/semtech/sx1262/README.md
deleted file mode 100644
index ec66a31..0000000
--- a/components/semtech/sx1262/README.md
+++ /dev/null
@@ -1,779 +0,0 @@
-# Semtech SX1262
-
-> **Common guide:** [`guides/lora`](../../../guides/lora/README.md) — the device-independent LoRa material (LoRa vs LoRaWAN vs Meshtastic, the SF/airtime/duty-cycle trade, regional band plans as a legal constraint, BUSY/TCXO/DIO handling and the LDO-vs-DC-DC current cost). This record covers the part; that guide covers the domain.
-
-- **Category:** sub-GHz **LoRa® / LR-FHSS / (G)FSK radio transceiver**, SPI-controlled, 150–960 MHz, **+22 dBm** high-power PA
-- **Package:** QFN 4 × 4 mm, 24 leads plus exposed pad (`SX1262IMLTRT`)
-- **Scope of this record: the chip only.** On the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) the SX1262 is **not on the main board** — it is inside the [`Stamp LoRa-1262`](../../m5stack/stamp-lora-1262/README.md) plug-in module, and everything at or above the module's 13-pin boundary (host wiring, reset, antenna switch, power gating, bring-up order) belongs to that record. Read it for the board; read this for the silicon.
-- **Research status:** the **full Semtech datasheet is retained** (`DS.SX1261-2.W.APP`, Rev 2.2, 118 pp) and was read. **No module datasheet exists anywhere** — see [§10-G1](#10-caveats-gaps-and-errata). The chip has never been seen directly: no teardown photograph, no probe, no measurement.
-- **Retrieved:** 2026-09-01
-
-**The [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) does not have it.** LoRa and NFC together are the entire difference between the two SKUs.
-
----
-
-## ⚠ This datasheet covers two parts, and the differences are the whole story
-
-`DS.SX1261-2` documents the **SX1261 and SX1262 together**. They share a die family, a pinout, a command set and a register map; they differ almost entirely in the power amplifier — and a claim copied from the wrong column is the most common error made with this document.
-
-| | **SX1261** | **SX1262** ← *the one in the Stamp module* |
-|---|---|---|
-| Maximum RF output power | **+14 dBm** nominal, **+15 dBm** with special settings | **+22 dBm** |
-| `SetTxParams` power range | **−17 to +14 dBm** (`0xEF`…`0x0E`) | **−9 to +22 dBm** (`0xF7`…`0x16`) |
-| PA supply | `VDD_IN` (pin 1) connected to **`VREG`** (pin 7) | `VDD_IN` (pin 1) connected to **`VBAT`** (pin 10) |
-| `SetPaConfig` `deviceSel` | **`0x01`** | **`0x00`** |
-| `hpMax` | no effect | selects PA size; **`0x07`** for +22 dBm |
-| Over-current protection after `SetPaConfig` | **60 mA** (`0x18`) | **140 mA** (`0x38`) |
-| TX current at 868/915 MHz, full power | 25.5 mA @ +14 dBm | **118 mA @ +22 dBm** |
-| DC-DC scope | whole IC | **IC core only — the PA is supplied from `VBAT`** |
-| Order code | `SX1261IMLTRT` | **`SX1262IMLTRT`** |
-| Ordering | QFN, tape and reel, MOQ 3 000 | idem |
-
-**[DS]** §3.5.4 Table 3-9, §13.1.14 Tables 13-20/13-21, §13.4.4, §5.1 Table 5-2, §3.5.1 Table 3-6, Ordering Information.
-
-**Everything below describes the SX1262** unless a row explicitly contrasts the two.
-
-Two independent lines of evidence say the fitted part really is the **62**, not the 61:
-
-1. The module is named `Stamp-LoRa-**1262**-mini` on the schematic and `Stamp LoRa-**1262**` in M5Stack's specification table, and its own pin names are `SX_NRST`, `SX_NSS`, `SX_BUSY`, `SX_ANT_SW` **[SCH]**, **[DOC]**.
-2. The factory firmware asks RadioLib for **22 dBm** and instantiates the `SX1262` class **[SRC]** `hal_lora.cpp:37`, `:328`. **+22 dBm is unreachable on an SX1261** — its `SetTxParams` range stops at +14, and RadioLib would reject or clamp it.
-
-Neither is a photograph of the die. `inferred`, but strongly.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | Stated in `artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf` (Rev 2.2), with section/table reference | `not-tested` — manufacturer specification reproduced; nothing measured |
-| **[SCH]** | Read out of `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet 4, designator `U14` | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | `docs.m5stack.com` / `semtech.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference | `inferred` |
-
-**Nothing in this record was verified on hardware, by anyone whose report could be located.** No register value, opcode or pin below was guessed.
-
-**Text-layer validation.** `pdftotext -layout` output was checked against the document's own running footers (`SX1261/2 · Data Sheet · Rev 2.2 · DS.SX1261-2.W.APP · Dec 2024`) and page numbering before transcription. ⚠ **One real defect was found and is worth knowing about**: the *figure* fonts carry a **uniform +31 code-point offset**, so block-diagram labels extract as human-legible but wrong text — `-P3B¥` for `LoRa®`, `.PEFN` for `Modem`, `41*` for `SPI`. This is exactly the failure mode that looks fine and is not. **Body text, tables and headings are unaffected**, and every value in this record comes from body text or a table. Recorded so the next reader does not transcribe a figure label.
-
----
-
-## 1. Identity and capability
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **Semtech Corporation** | **[DS]** cover |
-| Part | **SX1262** — "Long Range, Low Power, sub-GHz RF Transceiver" | **[DS]** cover |
-| Document | **`DS.SX1261-2.W.APP`, Rev 2.2, December 2024**, 118 pp | **[DS]** cover, revision history |
-| Order code | **`SX1262IMLTRT`**, QFN, tape and reel, 3 000 pcs MOQ, Pb-free / halogen-free / RoHS | **[DS]** Ordering Information |
-| Package | **QFN 4 × 4 mm, 0.5 mm pitch, 24 leads + exposed ground pad** | **[DS]** §2.1, §16.1 |
-| **Synthesizer frequency range** | **150 – 960 MHz, continuous** | **[DS]** Table 3-7 |
-| Modulations | **LoRa®**, **LR-FHSS** (TX only), **(G)FSK** 0.6 – 300 kb/s (2-FSK to 500 kb/s in RX specs) | **[DS]** §6 |
-| Host interface | **SPI**, mode 0 (CPOL = 0, CPHA = 0), **up to 16 MHz**, slave only | **[DS]** §8.2 |
-| Supply `VBAT` / `VBAT_IO` | **1.8 – 3.7 V** | **[DS]** Table 3-3 |
-| Reference | 32 MHz crystal **or** an external TCXO powered from `DIO3` | **[DS]** §4.1 |
-| Data buffer | 256 bytes, shared TX/RX with programmable base addresses | **[DS]** §7 |
-| ⚠ Marking verified? | **No.** The chip is inside a module; no teardown photograph exists (§10-G1) | **[INF]** |
-
-Semtech positions it for smart meters, logistics, building automation, agriculture, asset tracking, street lighting and environmental sensing, and states compliance intent for **ETSI EN 300 220, FCC CFR 47 Part 15, Chinese regulations and Japanese ARIB T-108** **[DS]** General Description.
-
-> ⚠ **LR-FHSS is patent-encumbered.** Semtech's own disclaimer on page 2: using Semtech's LR-FHSS software "does not grant any rights to their patents for LR-FHSS technology"; rights are available "by purchasing Semtech SX1261, SX1262, SX1268, or LR11xx semiconductor devices, or their authorized counterparts". Worth knowing before designing a product around it. **[DS]** p. 2.
-
-### 1.1 150–960 MHz silicon versus an 868–923 MHz module
-
-The **chip** covers 150–960 MHz continuously. The **module** M5Stack fits is advertised at **868 – 923 MHz**, one wideband SKU with no regional variant **[DOC]**.
-
-That narrowing is not a chip limitation — it is the module's matching network and antenna, neither of which is documented anywhere ([§10-G1](#10-caveats-gaps-and-errata)). Do not read the datasheet's 150 MHz floor as something you can use on this board.
-
-Note also that the datasheet's own performance figures are quoted at **434 / 490 / 868 / 915 MHz** with "all RF impedances matched" **[DS]** §3.5, so even the 868–923 range is only as good as a matching network nobody has seen. And the PA settings interact with matching directly: `paDutyCycle` "will affect the distribution of the power in the harmonics and should thus be selected to work in conjunction of a given matching network" **[DS]** §13.1.14. Changing `paDutyCycle` on this module is therefore not a software-only decision.
-
----
-
-## 2. Pin table
-
-**[DS]** §2.1, Table 2-1. The "brought out by the module?" column is from the [Stamp-LoRa-1262 record](../../m5stack/stamp-lora-1262/README.md) §2 and is `inferred` by name matching — the module has no datasheet.
-
-| Pin | Name | Type | Function | Reaches the PaperMono? |
-|---:|---|---|---|---|
-| 0 | `GND` | — | Exposed ground pad | — |
-| 1 | `VDD_IN` | I | PA regulator input, `VR_PA`. **SX1261: tie to pin 7. SX1262: tie to pin 10** | internal |
-| 2 | `GND` | — | Ground | — |
-| 3 | `XTA` | — | Crystal connection; can take an external reference clock | internal |
-| 4 | `XTB` | — | Crystal connection | internal |
-| 5 | `GND` | — | Ground | — |
-| 6 | **`DIO3`** | I/O | Multi-purpose digital I/O — **or external TCXO supply** | **internal — not brought out** (§5.2) |
-| 7 | `VREG` | O | Regulated output of the internal LDO / DC-DC | internal |
-| 8 | `GND` | — | Ground | — |
-| 9 | `DCC_SW` | O | DC-DC switcher output | internal |
-| 10 | `VBAT` | I | Supply for the RFIC | module pin 5 `VIN_3V3` (3.3 V) |
-| 11 | `VBAT_IO` | I | Supply for the digital I/O pins **except `DIO3`** | internal |
-| 12 | **`DIO2`** | I/O | Multi-purpose digital I/O — **or RF switch control** | **internal — not brought out** (§5.3) |
-| 13 | **`DIO1`** | I/O | Multi-purpose digital I/O — the generic IRQ line | **module pin 4 `LORA_IRQ`** → ESP32-S3 GPIO5 |
-| 14 | **`BUSY`** | O | Busy indicator | **module pin 3 `SX_BUSY`** → ESP32-S3 GPIO21 |
-| 15 | `NRESET` | I | Reset, active low | module pin 2 `SX_NRST` → **M5IOE1 `IO10`** |
-| 16 | `MISO` | O | SPI slave output | module pin 8 → ESP32-S3 GPIO40 |
-| 17 | `MOSI` | I | SPI slave input | module pin 7 → ESP32-S3 GPIO38 |
-| 18 | `SCK` | I | SPI clock | module pin 6 → ESP32-S3 GPIO39 |
-| 19 | `NSS` | I | SPI slave select | module pin 9 `SX_NSS` → ESP32-S3 GPIO41 |
-| 20 | `GND` | — | Ground | — |
-| 21 | `RFI_P` | I | RF receiver input | internal |
-| 22 | `RFI_N` | I | RF receiver input | internal |
-| 23 | `RFO` | O | **RF transmitter output** — SX1261 low-power PA or **SX1262 high-power PA** | internal → FPC antenna |
-| 24 | `VR_PA` | — | Regulated power-amplifier supply | internal |
-
-Three consequences of that last column, all of which shape how you drive this board:
-
-- **Only `DIO1` leaves the module.** The module's `LORA_IRQ` is `DIO1` specifically — not a wired-OR of the DIOs — confirmed by the firmware naming the same line `LORA_DIO1_PIN` **[SRC]** `hal_lora.cpp:27`. `DIO2` and `DIO3` are consumed inside the module (§5).
-- **`NRESET` is behind an I²C expander**, so RadioLib is handed `RADIOLIB_NC` for reset and never resets the radio itself **[SRC]** `hal_lora.cpp:327`.
-- **`DIO3` is referenced to `VBAT`, not `VBAT_IO`** — the datasheet flags it explicitly in a footnote to the digital I/O table **[DS]** Table 3-10 note 1. That is because `DIO3` doubles as a *regulated supply output* (§5.2), not merely a logic pin.
-
----
-
-## 3. Modems
-
-### 3.1 LoRa
-
-Spread-spectrum with forward error correction, configured through `SetModulationParams` after `SetPacketType`. Four parameters **[DS]** §6.1.1:
-
-| Parameter | Range | Effect |
-|---|---|---|
-| **Spreading factor** `SF` | **5 – 12** | 2^SF chips/symbol. Symbol rate `Rs = BW / 2^SF` |
-| **Bandwidth** `BW_L` | 7.81 – 500 kHz | Higher = faster, less sensitive |
-| **Coding rate** `CR` | 4/5 – 4/8 | FEC overhead |
-| **Low data-rate optimize** `LDRO` | 0 / 1 | Relaxes the allowed frequency drift by **16×** |
-
-Demodulator SNR by spreading factor **[DS]** Table 6-1:
-
-| SF | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
-|---|---|---|---|---|---|---|---|---|
-| chips/symbol | 32 | 64 | 128 | 256 | 512 | 1024 | 2048 | 4096 |
-| typical SNR (dB) | −2.5 | −5 | −7.5 | −10 | −12.5 | −15 | −17.5 | **−20** |
-
-> ⚠ **SF5 and SF6 are not backward compatible.** Both were modified in the SX1261/2 and now work in implicit *and* explicit mode, but **SF6 here is not interoperable with SF6 on an SX1276**. For SF5/SF6, use **12 preamble symbols** rather than the usual 8 **[DS]** §6.1.1.1. Spreading factors are orthogonal, so both ends must agree in advance.
->
-> Semtech also recommends 12 preamble symbols generally for optimal performance — added in datasheet Rev 1.1.
-
-⚠ **Not every SF is available at every bandwidth** — Table 6-1 carries the footnote "Not all SF are available for any bandwidth with the SX1261/2" without enumerating which. An unresolved documentation gap in Semtech's own datasheet.
-
-**Frequency drift matters at low data rates.** With `LDRO = 0`, total drift across a packet must stay under `Freq_drift_max`; `LDRO = 1` relaxes that 16-fold. This is the mechanism that makes a **TCXO** worthwhile in a miniaturised design where heat cannot be kept away from the crystal — and Semtech says so in as many words **[DS]** §4.1.2. See §5.2.
-
-### 3.2 (G)FSK
-
-2-FSK, 0.6 – 300 kb/s (RX specifications go to 500 kb/s), with selectable Gaussian pulse shaping and a sigma-delta fractional-N modulator giving fine deviation control **[DS]** §6.2. The demodulator bandwidth must satisfy:
-
-```
-2 × Fdev + BR  <  BW
-```
-
-Packet handling includes preamble detection, sync word up to 8 bytes, node/broadcast address filtering, fixed- or variable-length packets, CRC with programmable initial value and polynomial, and data whitening.
-
-### 3.3 LR-FHSS
-
-Long Range Frequency Hopping Spread Spectrum — **transmit only** on this part, aimed at very high node density **[DS]** §6.3. Patent-encumbered (§1).
-
-### 3.4 Data buffer
-
-A single **256-byte** buffer shared between TX and RX, with independent base addresses set by `SetBufferBaseAddress` **[DS]** §7. That is the origin of the 255-byte maximum packet the vendor firmware enforces **[SRC]** `hal_lora.cpp:42`.
-
----
-
-## 4. The SPI command interface
-
-### 4.1 Electrical and timing
-
-**[DS]** §8.2: mode 0 (CPOL = 0, CPHA = 0), MSB first, slave only. MOSI is generated by the master on the SCK **falling** edge and sampled by the slave on the **rising** edge; MISO is generated on the falling edge. NSS low frames the transaction; MISO is high-Z while NSS is high. **Up to 16 MHz.**
-
-Key timings, all at ≤10 pF load **[DS]** Table 8-1:
-
-| Symbol | Meaning | Min |
-|---|---|---|
-| `t1` | NSS falling → SCK setup | 32 ns |
-| `t2` | SCK period | 62.5 ns (⇒ 16 MHz) |
-| `t8` | SCK → NSS rising hold | 31.25 ns |
-| `t9` | **NSS high time** | **125 ns** |
-| **`t10`** | **NSS falling → SCK when leaving SLEEP** | **100 µs** |
-| `t11` | NSS falling → MISO when leaving SLEEP | ≤ 150 µs |
-
-⚠ `t10` is the trap: **the first SPI clock after waking from sleep must wait 100 µs after NSS falls**, because the chip is bringing up its regulators. A driver that treats a sleep wake like an ordinary transaction will lose the first command. The correct approach is to watch `BUSY` (§4.3).
-
-The PaperMono runs this bus at **8 MHz**, half the maximum **[SRC]** `hal_lora.cpp:31`.
-
-### 4.2 Command structure
-
-Every transaction is an **opcode byte** followed by parameters and/or returned status **[DS]** §10, §11. There is no register-address protocol in the usual sense — registers are reached through `WriteRegister` (`0x0D`) and `ReadRegister` (`0x1D`) with a 16-bit address, and the packet buffer through `WriteBuffer` (`0x0E`) / `ReadBuffer` (`0x1E`).
-
-The commands that matter most **[DS]** Tables 11-1 to 11-5:
-
-| Opcode | Command | Note |
-|---|---|---|
-| `0x84` | `SetSleep` | Cold start (no retention) vs warm start (configuration retained) |
-| `0x80` | `SetStandby` | `STDBY_RC` (13 MHz RC) or `STDBY_XOSC` |
-| `0xC1` / `0x83` / `0x82` | `SetFs` / `SetTx` / `SetRx` | `SetTx`/`SetRx` take a 24-bit timeout |
-| `0x94` | `SetRxDutyCycle` | The low-power listen mode |
-| `0xC5` | `SetCad` | Channel activity detection |
-| `0x96` | `SetRegulatorMode` | LDO or DC-DC. **`STDBY_RC` only** |
-| `0x89` / `0x98` | `Calibrate` / `CalibrateImage` | |
-| **`0x95`** | **`SetPaConfig`** | **The command that differentiates SX1261 from SX1262** |
-| `0x93` | `SetRxTxFallbackMode` | Where the chip lands after TX/RX done |
-| `0x08` | `SetDioIrqParams` | Four 16-bit masks: global + one per DIO |
-| `0x12` / `0x02` | `GetIrqStatus` / `ClearIrqStatus` | |
-| **`0x9D`** | **`SetDIO2AsRfSwitchCtrl`** | §5.3 |
-| **`0x97`** | **`SetDIO3AsTcxoCtrl`** | §5.2 |
-| `0x86` / `0x8A` / `0x8E` | `SetRfFrequency` / `SetPacketType` / `SetTxParams` | |
-| `0x8B` / `0x8C` | `SetModulationParams` / `SetPacketParams` | |
-| `0xC0` / `0x13` / `0x14` / `0x15` | `GetStatus` / `GetRxBufferStatus` / `GetPacketStatus` / `GetRssiInst` | |
-| `0x17` / `0x18` | `GetDeviceErrors` / `ClearDeviceErrors` | |
-
-`SetPacketType` must be called **before** `SetModulationParams` and `SetPacketParams`, because the parameter encodings differ per modem. **[DS]** §13.4.5. `SetRegulatorMode` is only valid in `STDBY_RC`. Semtech devotes a whole section, §14.5, to "Issuing Commands in the Right Order" — the ordering is not incidental.
-
-### 4.3 `BUSY` — a mandatory handshake, not a status LED
-
-**[DS]** §8.3.1, and this is the single most important behavioural fact about the part:
-
-> When the BUSY line is held low, it indicates that the internal state machine is in idle mode and that the radio is ready to accept a command from the host controller.
-
-- **Every "write" command raises `BUSY`** after `T_SW`, which is **≤ 600 ns** from the NSS rising edge in all cases. The host must wait for `BUSY` to fall before the next command.
-- **"Read" commands do not raise `BUSY`** — they are handled without the state machine.
-- **`BUSY` also rises to service the chip's own internal interrupts.** Semtech: "it is essential to wait for the BUSY line to go low before sending an SPI command (either a 'read' or a 'write' command)." So the read exemption is not a licence to ignore the line.
-- **In sleep, `BUSY` is held high through a 20 kΩ resistor** and falls as soon as the chip leaves sleep — which is the correct, timing-independent way to satisfy `t10` (§4.1).
-- `BUSY` falls at meaningfully different moments per mode: in **FS** when the PLL locks; in **RX** when the receiver is up; in **TX** when the PA has ramped and preamble transmission starts.
-
-Mode-transition times, NSS rising to `BUSY` falling **[DS]** Table 8-2:
-
-| Transition | µs |
-|---|---:|
-| **SLEEP → STDBY_RC, cold start (no retention)** | **3500** |
-| **SLEEP → STDBY_RC, warm start (retention)** | **340** |
-| STDBY_RC → STDBY_XOSC | 31 |
-| STDBY_RC → FS / RX / TX | 50 / 83 / **126** |
-| STDBY_XOSC → FS / RX / TX | 40 / 62 / 105 |
-| FS → RX / TX | 41 / 76 |
-| RX → FS / TX | 15 / 92 |
-
-**A cold-start wake costs 3.5 ms — ten times a warm start.** On a duty-cycled battery node that is the difference between viable and not, and it is the reason `SetSleep`'s retention flag exists.
-
-⚠ **Add the TCXO delay to every one of these** if `DIO3` supplies a TCXO (§5.2).
-
-### 4.4 Interrupts
-
-Ten sources, each maskable and each mappable to any of `DIO1`, `DIO2` or `DIO3` **[DS]** §8.5, Table 8-4:
-
-| Bit | IRQ | Modulation |
-|---:|---|---|
-| 0 | `TxDone` | all |
-| 1 | `RxDone` | all |
-| 2 | `PreambleDetected` | all |
-| 3 | `SyncWordValid` | FSK |
-| 4 | `HeaderValid` | LoRa |
-| 5 | `HeaderErr` | LoRa |
-| 6 | `CrcErr` | all |
-| 7 | `CadDone` | LoRa |
-| 8 | `CadDetected` | LoRa |
-| 9 | `Timeout` | all |
-
-`DIO1` is described as "the generic IRQ line, any interrupt can be mapped to DIO1" — which is exactly why a module that brings out only one DIO brings out `DIO1`.
-
-Pin states per mode are worth knowing when the chip is asleep **[DS]** Table 8-3: in **Reset, Start-up and Sleep** all three DIOs are **pulled down** (50 kΩ) and `BUSY` is **pulled up**; only from `STDBY_RC` upward do they become real outputs. A DIO used for an external function is therefore *not* driven while the chip sleeps — relevant to both TCXO and RF-switch control.
-
----
-
-## 5. `DIO2` and `DIO3` — the two pins that are not really I/O
-
-### 5.1 Why this matters on a module
-
-Both pins have a second personality, both are configured by a single command, and **both are consumed inside the Stamp module where they cannot be observed**. Getting either wrong produces a radio that initialises cleanly and then does not work — the hardest class of fault to diagnose.
-
-### 5.2 `DIO3` as a TCXO supply
-
-**[DS]** §8.3.2, §13.3.6. `SetDIO3AsTcxoCtrl(tcxoVoltage, delay[23:0])` (opcode `0x97`) hands `DIO3` to the internal state machine, which then **drives it to a programmed voltage whenever the reference is needed** — in `STDBY_XOSC`, `FS`, `TX` and `RX` — and power-cycles the TCXO the rest of the time.
-
-| `tcxoVoltage` | `DIO3` output |
-|---|---|
-| `0x00` – `0x02` | 1.6 / 1.7 / 1.8 V |
-| `0x03` – `0x05` | 2.2 / 2.4 / 2.7 V |
-| **`0x06`** | **3.0 V** |
-| `0x07` | 3.3 V |
-
-Precision is roughly ±50 mV (quoted for the 1.8 V setting). ⚠ **The regulator targets 200 mV below the supply**, so the datasheet states the constraint as **`VDDop > VTCXO + 200 mV`**. With a 3.3 V module supply and a 3.0 V setting the margin is exactly 300 mV — inside the rule, but with only 100 mV to spare over a rail that also feeds the PA. Worth knowing before assuming headroom.
-
-`delay(23:0)` is in units of **15.625 µs** and gates the 32 MHz clock until the TCXO has settled. If 32 MHz is not detected by the end of the delay, **`XOSC_START_ERR`** is raised. Two behaviours around that flag catch people:
-
-- **`XOSC_START_ERR` is raised at POR and at every cold-start sleep wake when a TCXO is used**, because the chip does not yet know it is TCXO-clocked. Semtech: *"It is an expected behaviour... The user should simply clear this flag with the ClearDeviceErrors command."* An error handler that treats it as fatal will refuse to start a perfectly good radio.
-- **The delay is added to every STDBY_RC → TX/RX transition.** To avoid paying it on each packet, go to `STDBY_XOSC` first, wait once, then move to TX or RX.
-
-There is also a **side effect on the crystal trimming caps**: issuing `SetDIO3AsTcxoCtrl` automatically forces the `XTA` internal cap register to `0x2F` (33.4 pF) "to filter any spurious transitions which could occur and be propagated to the PLL" **[DS]** §4.1.3.
-
-`DIO3` can alternatively be driven as a **plain switched output** through raw register writes to `0x0580`, `0x0583`, `0x0584`, `0x0585` and `0x0920` **[DS]** §8.6 — and that configuration **is overwritten by the state machine at POR and on every wake from sleep**, so it must be re-applied each time.
-
-#### 5.2.1 The PaperMono evidence: `LORA_TCXO_VOLTAGE = 3.0f` — `inferred`
-
-**This is not a datasheet fact about this board, and it is not a measurement. It is an inference from vendor firmware, and it is labelled `inferred` deliberately.**
-
-```cpp
-static constexpr float LORA_TCXO_VOLTAGE = 3.0f;          // hal_lora.cpp:40
-...
-radio->begin(868.0f, 62.5f, 12, 8, 0x34, 22, 10,
-             LORA_TCXO_VOLTAGE, LORA_USE_REGULATOR_LDO);   // hal_lora.cpp:333-334
-```
-
-RadioLib's `SX126x::begin(..., tcxoVoltage, useRegulatorLDO)` maps a non-zero `tcxoVoltage` onto `SetDIO3AsTcxoCtrl`, and **3.0 V is `tcxoVoltage = 0x06`** in Semtech's table above.
-
-What that supports, and what it does not:
-
-- ✅ **The vendor firmware configures `DIO3` as a 3.0 V TCXO supply.** `executed-success` for the source read.
-- ✅ **Therefore M5Stack believes a TCXO is fitted inside the module**, since configuring a TCXO supply on a crystal-only design is at best pointless and at worst harmful.
-- ❌ **It does not prove a TCXO is physically present.** No module datasheet, no photograph, no measurement. The module could carry a plain 32 MHz crystal and the firmware could be wrong-but-working, or wrong-and-marginal.
-- ❌ **It does not establish which TCXO, its stability, or its start-up time.** The `delay` RadioLib passes was not traced.
-
-This is the same conclusion the [Stamp-LoRa-1262 record reaches at §5-G3](../../m5stack/stamp-lora-1262/README.md), which warns that getting TCXO configuration wrong yields a radio that "appears to initialise and then fails to transmit or receive". **Its advice stands: do not change this value blindly.** `3.0f` is the value the shipped firmware uses; treat it as the known-good starting point and change it only with a spectrum analyser to hand.
-
-### 5.3 `DIO2` as RF switch control
-
-**[DS]** §8.3.2, §13.3.3. `SetDIO2AsRfSwitchCtrl(enable)` (opcode `0x9D`) makes `DIO2` **high during TX and low in every other mode** — a one-line antenna-path selector for a design with separate TX and RX paths, or a single SPDT switch.
-
-The datasheet devotes §14.6.1 and §14.6.2 to application schematics of exactly this ("Application Design of the SX1261/SX1262 **with RF Switch**"), so it is the expected topology rather than an exotic one. When the paths are *not* split — a "direct tie connection between Rx and Tx" — sensitivity is measurably worse: **−133 dBm instead of −137 dBm** for LoRa at BW 125 kHz / SF12, and −115 vs −118 dBm for 2-FSK at 4.8 kb/s **[DS]** Table 3-8. **A 4 dB link-budget penalty** is the price of omitting the switch.
-
-Note also that the datasheet's headline receive figures assume "split RF paths for Rx and Tx, **RF switch insertion loss excluded**" — so real-world numbers sit below them by the switch's loss.
-
-#### 5.3.1 The PaperMono evidence, and the two switches that are not the same thing
-
-```cpp
-s_lora.radio->setDio2AsRfSwitch(true);     // hal_lora.cpp:343
-```
-
-**[SRC]**, `executed-success` for the read. So the vendor firmware tells the SX1262 to drive an RF switch from `DIO2`, and `DIO2` never leaves the module — meaning **the switch it drives is inside the module**. `inferred`.
-
-⚠ **That is emphatically not the same signal as the module's `SX_ANT_SW` pin.** The module brings out a separate `SX_ANT_SW` on pin 10, wired to **M5IOE1 `IO2`**, which the firmware sets HIGH once during bring-up and never touches again **[SRC]** `hal_lora.cpp:314`, `:319`. Its semantics are undocumented — whether it selects TX/RX paths, enables a PA/LNA, or picks between antenna connectors is stated nowhere, and remains [open question G4 in the module record](../../m5stack/stamp-lora-1262/README.md).
-
-So this board has **two** antenna-switch controls: one automatic and internal (`DIO2`), one manual and external (`SX_ANT_SW`). Conflating them is an easy and expensive mistake.
-
-### 5.4 Regulator choice, and what the PaperMono firmware gives up
-
-**[DS]** §5.1. Two regulation modes, selected by `SetRegulatorMode` **in `STDBY_RC` only**:
-
-| Mode | Sleep | STDBY_RC | STDBY_XOSC / FS / RX / TX |
-|---|---|---|---|
-| Regulator type **0** (LDO) | — | LDO | **LDO** |
-| Regulator type **1** (DC-DC) | — | LDO | **DC-DC + LDO** |
-
-DC-DC needs two external inductors — 47 nH before pin 1 and 15 µH between pins 7 and 9 — so LDO-only operation exists precisely to save that BOM and board area. On the **SX1262** the DC-DC covers the IC core only; **the PA is supplied from `VBAT` either way**, so DC-DC does not reduce transmit current at all.
-
-Where it does matter is **receive**, and the difference is large **[DS]** Table 3-5:
-
-| Mode | DC-DC | **LDO** |
-|---|---:|---:|
-| RX, FSK 4.8 kb/s | 4.2 mA | **8.0 mA** |
-| RX, LoRa 125 kHz | 4.6 mA | **8.8 mA** |
-| RX boosted, LoRa 125 kHz | 5.3 mA | **10.1 mA** |
-| Synthesizer (FS) | 2.1 mA | 3.55 mA |
-
-**The PaperMono firmware selects LDO** — `LORA_USE_REGULATOR_LDO = true` **[SRC]** `hal_lora.cpp:41`, passed as `begin()`'s last argument. **Receive current is therefore roughly double what the datasheet's headline "4.2 mA active receive" figure suggests**, and that headline is the first sentence of Semtech's own General Description.
-
-Whether that is a considered choice or a default is unknown. The likeliest reading is that **the module simply does not fit the DC-DC inductors** — they are the exact components §5.1 says LDO-only operation exists to omit, and a "Stamp"-format module is space-constrained. `inferred`, and it would be settled by a photograph of the module. For a battery product that spends its life in receive, this is the single most consequential unverified fact about the radio on this board.
-
----
-
-## 6. Power and RF performance
-
-### 6.1 Current
-
-**[DS]** Tables 3-5 and 3-6, at 25 °C, `VBAT = VBAT_IO = 3.3 V`, TCXO and RF-switch consumption **excluded**.
-
-| Mode | Typical |
-|---|---:|
-| **OFF (sleep, cold start)** | **160 nA** |
-| Sleep, configuration retained | 600 nA |
-| Sleep, retained + RC64k running | 1.2 µA |
-| `STDBY_RC` | 0.6 mA |
-| `STDBY_XOSC` | 0.8 mA |
-| RX — see §5.4 for the LDO/DC-DC split | 4.2 – 10.1 mA |
-
-Transmit, **SX1262 at 868/915 MHz** with the +22 dBm PA match:
-
-| Output | Typical |
-|---|---:|
-| **+22 dBm** | **118 mA** |
-| +20 dBm | 102 mA |
-| +17 dBm | 95 mA |
-| +14 dBm | 90 mA |
-
-With the PA re-optimised for a lower target (a different `paDutyCycle`/`hpMax` *and* a different matching network), the same output costs far less: +20 dBm → 84 mA, +17 dBm → 58 mA, +14 dBm → **45 mA**. Half the current at +14 dBm — but only with the matching network to match, which is not a software change (§1.1).
-
-**The PaperMono firmware asks for +22 dBm**, i.e. ~118 mA in transmit, on a rail supplied by an LDO rated 400 mA that also feeds nothing else **[SRC]**, [module record](../../m5stack/stamp-lora-1262/README.md). Nobody has measured it.
-
-### 6.2 Over-current protection
-
-`SetPaConfig` **automatically reprograms OCP** (register `0x08E7`): `0x18` = 60 mA after POR, and **`0x38` = 140 mA once `deviceSel` selects the SX1262** **[DS]** Table 5-2. Range is 6 bits in 2.5 mA steps, max 157.5 mA. Any manual OCP change must come **after** `SetPaConfig`, or it is overwritten.
-
-The PaperMono firmware calls `setCurrentLimit(140.0f)` **[SRC]** `hal_lora.cpp:344` — which is **exactly the SX1262 post-`SetPaConfig` default**. So the call re-applies the default rather than changing anything. Harmless, and possibly deliberate belt-and-braces; worth knowing it is not a tuning decision.
-
-### 6.3 Sensitivity
-
-**[DS]** Table 3-8, RX-boosted gain, split RF paths, switch insertion loss excluded:
-
-| LoRa | SF7 | SF12 |
-|---|---:|---:|
-| BW 10.4 kHz | −134 dBm | **−148 dBm** |
-| BW 125 kHz | −124 dBm | −137 dBm |
-| BW 250 kHz | −121 dBm | −134 dBm |
-| BW 500 kHz | −117 dBm | −129 dBm |
-
-2-FSK ranges from −125 dBm at 0.6 kb/s to −94 dBm at 500 kb/s. LoRa adjacent-channel rejection reaches 72 dB at SF12/125 kHz, and blocking immunity 88–99 dB at 1–10 MHz offset.
-
-With a "direct tie" front end instead of a switch, subtract ~4 dB (§5.3).
-
-### 6.4 Transmit
-
-**[DS]** Table 3-9:
-
-| Parameter | Value |
-|---|---|
-| Max output, **SX1262** | **+22 dBm** |
-| Power range | programmable in **31 steps**, `TXOP−31` to `TXOP` |
-| Step accuracy | ±2 dB |
-| Ramp time | programmable **10 µs to 3400 µs** (eight settings) |
-| TX wake-up time | 36 µs + PA ramping |
-| **Output power drop vs `VBAT`, SX1262 at +22 dBm** | **2 dB at 2.7 V · 3 dB at 2.4 V · 6 dB at 1.8 V** |
-
-That last row is a battery-product fact: **an SX1262 asked for +22 dBm delivers +16 dBm on a nearly-flat cell.** On the PaperMono the module runs from a regulated 3.3 V LDO rather than the battery directly, which should avoid it — `inferred`, unmeasured.
-
-### 6.5 Crystal and reference accuracy
-
-**[DS]** §3.4, §4.1.3. 32 MHz, C<sub>LOAD</sub> 10 pF, R<sub>S</sub> ≤ 60 Ω, drive level ≤ 100 µW. **No external load capacitors are needed** — internal trimming caps on `XTA` and `XTB` are adjustable in 0.47 pF steps from 11.3 pF (`0x00`) to 33.4 pF (`0x2F`) via registers `0x0911` / `0x0912`.
-
-⚠ **The trimming caps are overwritten by the state machine.** At POR or cold-start wake they initialise to `0x05` (13.6 pF); on entering `STDBY_XOSC` the state machine forces both to `0x12` (19.7 pF). **You must already be in `STDBY_XOSC` before changing them**, or your value is discarded.
-
-Semtech's system-level guidance: **±30 ppm** overall reference accuracy is expected of a LoRaWAN end device across initial error, temperature drift and lifetime ageing.
-
-⚠ **Thermal coupling is a real design constraint on this part.** §4.1.2: the SX1262 transmits up to +22 dBm from a 4 × 4 mm package, "the circuit may heat up", and "careful PCB design using thermal isolation techniques must be applied between the circuit and the crystal resonator to avoid transferring the heat to the external crystal resonator". In a miniaturised design where that isolation is impossible, Semtech's recommendation is **a TCXO** — which is a coherent reason for the Stamp module to fit one (§5.2).
-
----
-
-## 7. Operating modes
-
-**[DS]** §9:
-
-| Mode | What is running | Leaves via |
-|---|---|---|
-| **SLEEP** | Most blocks off; optionally RC64k + timer. **`BUSY` held high** | **NSS going low** (any case), or an RTC end-of-count (Listen mode) |
-| **STDBY_RC** | 13 MHz RC oscillator. The configuration mode | command |
-| **STDBY_XOSC** | XOSC on. Use when timing is critical, or to pre-pay the TCXO delay | command |
-| **FS** | PLL and regulators on. `BUSY` falls when the PLL locks or times out | command |
-| **RX** | Front end, RX ADC, selected modem. Continuous / single / single-with-timeout | command, packet, or timeout |
-| **TX** | PA ramped; `BUSY` falls when preamble transmission starts | command or timeout |
-
-⚠ **RX and TX frequencies differ.** The SX1261/2 uses a low-IF architecture, so the RX frequency is the TX frequency minus the IF; in FS and TX modes the RF frequency is programmed directly **[DS]** §9.5. `CalibrateImage` exists for this reason and should be run for the band in use.
-
-`SetRxDutyCycle` implements a low-power listen mode by alternating RX and sleep windows under RTC control, and `SetRxTxFallbackMode` chooses where the chip lands after a completed packet — both worth reaching for before hand-rolling a duty cycle in host firmware.
-
----
-
-## 8. Register-level workarounds you must implement
-
-Semtech publishes four **Known Limitations** in §15. All four are register writes the datasheet says to make, none is optional, and a driver that omits them is subtly wrong rather than obviously broken.
-
-| # | Symptom | Workaround | When to apply |
-|---|---|---|---|
-| **15.1** | Sensitivity degradation on **any** LoRa receiver when receiving a 500 kHz-bandwidth signal transmitted by an SX1261/2 | **Bit 2 of `0x0889`**: set **0** when LoRa BW = 500 kHz, **1** for any other LoRa BW and for all (G)FSK | **Before every packet transmission** |
-| **15.2** | The PA over-voltage clamp is over-protective, backing power off by **5–6 dB** on a "reasonable" antenna mismatch | **`TxClampConfig` bits 4–1 → `1111`** (default `0100`) | **After POR and after every cold-start wake.** SX1262 only |
-| **15.3** | In LoRa **implicit-header** RX with timeout, the RTC-based timeout timer is **not stopped on `RxDone`** and can fire spuriously in a later mode | Write `0x0902` to stop the counter and `0x0944` to clear the event | **After any RX-with-timeout sequence** |
-| **15.4** | Packet loss on longer packets when using **inverted IQ** | **Bit 2 of `0x0736`**: **0** for inverted IQ, **1** for standard IQ | Whenever IQ polarity is set |
-
-Two are worth dwelling on for this board:
-
-- **15.2 is an SX1262-specific fix with a 5–6 dB effect** — larger than most antenna decisions. Semtech is careful to say the workaround "improves chip functionality, but is not required to ensure long-term reliability", i.e. it is safe to apply. RadioLib is generally good about these; **whether the pinned 7.2.1 applies all four was not verified in this pass** and is recorded as an open item ([§10-G4](#10-caveats-gaps-and-errata)).
-- **15.3 bites exactly the pattern the PaperMono firmware uses** — `startReceive()` in a loop with interrupt-driven handling. Whether RadioLib clears the RTC after each receive was not traced.
-
----
-
-## 9. Drivers and libraries
-
-| Option | Where | Verdict |
-|---|---|---|
-| **RadioLib** (jgromes) | `github.com/jgromes/RadioLib`, **pinned by the PaperMono factory firmware at `7.2.1`**, commit `b91c6af112e423dcb14529ade5827802a14e1015` | ✅ **Use this.** It is what the shipped firmware runs, and it is the de-facto SX126x driver outside Semtech's own stack |
-| Semtech `SX126x` driver / `LoRaMac-node` | Semtech's GitHub organisation | The reference implementation and the LoRaWAN path. Not used by any M5Stack code found here |
-| Raw SPI | — | Entirely feasible — §4 is the whole interface — but §8's four workarounds are the kind of thing a hand-rolled driver silently omits |
-
-**Version and patch context** for the PaperMono, **[SRC]** `repos.json`:
-
-- RadioLib is **patched by the vendor build to remove `idf_component.yml`**, so it builds as a plain ESP-IDF component rather than a managed one.
-- ⚠ **M5Stack's published PlatformIO snippet pins nothing** — `RadioLib = https://github.com/jgromes/RadioLib` pulls `master`. Reproducing factory behaviour requires the pinned commit **and** the patch **[DOC]** vs **[SRC]**.
-- ⚠ **Licence mismatch, flagged not confirmed:** RadioLib is **LGPL-3.0** upstream while the M5Stack demo carrying it is MIT. Not verified in this pass.
-- ✅ **Correction, 2026-09-07 — the line immediately above is wrong and is left in place only for provenance.** RadioLib is **MIT**, not LGPL-3.0. Verified `executed-success` on 2026-09-04 by the LoRa-generations pass: the licence file is **`license.txt`, lower case** (which is why a `LICENSE` fetch 404s, and is the likely origin of the LGPL-3.0 belief), and it reads `MIT License / Copyright (c) 2018 Jan Gromeš` **byte-identically at tags `7.2.1` and `7.7.1`**. `gh api repos/jgromes/RadioLib --jq .license.spdx_id` → `MIT`. **There is no mismatch with the MIT-licensed M5Stack demo.** The original line was not edited because this pass was append-only; the correction is parked for a maintainer in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md). Source: `scratch/lora-generations/index-fragments.md` §6.1.
-
-Framework: ESP-IDF **5.5.1**, target `esp32s3`, arduino-esp32 **3.3.10** as a managed component **[SRC]** `dependencies.lock`.
-
-The vendor's integration is deliberately thin: `hal_lora.cpp` implements a `RadioLibHal` over ESP-IDF SPI and GPIO, hands RadioLib six pin numbers, and gets out of the way. `NRESET` is passed as `RADIOLIB_NC` because reset is an I²C expander pin (§2).
-
----
-
-## 10. Caveats, gaps and errata
-
-| # | Issue | Evidence |
-|---|---|---|
-| **G1** | ⚠ **No `Stamp-LoRa-1262` module datasheet exists.** M5Stack's *Datasheets* list for the PaperMono links **this chip datasheet** and nothing module-specific. So the module's supply current, RF output power at the connector, antenna type and gain, matching network, TCXO-vs-crystal choice, internal DIO usage, and the identity of module pins 11–13 are **all undocumented**. This chip record cannot fill those gaps and does not try | **[DOC]** — the absence is `executed-success`, the full list was enumerated; [module record §5-G1](../../m5stack/stamp-lora-1262/README.md) |
-| **G2** | **The chip has never been seen.** No teardown photograph of the module, no top marking read. `SX1262` rests on the module name, the vendor specification row, the module's `SX_*` pin names and the firmware's +22 dBm request — strong, but circumstantial | **[SCH]**, **[DOC]**, **[SRC]**; **[INF]** |
-| **G3** | **TCXO presence is inferred from a firmware constant** (§5.2.1). `LORA_TCXO_VOLTAGE = 3.0f` shows what M5Stack *configures*, not what is *fitted*. `inferred`, `not-tested` | **[SRC]** `hal_lora.cpp:40` |
-| **G4** | **Whether RadioLib 7.2.1 applies all four of Semtech's §15 workarounds was not verified.** Two of them (15.2's 5–6 dB clamp fix, 15.3's stuck RTC timeout) directly affect this board's usage pattern (§8) | not traced — explicit gap |
-| **G5** | **The firmware selects LDO regulation, roughly doubling receive current** versus the datasheet's headline figure (§5.4). Whether the module even has the DC-DC inductors is unknown | **[SRC]** `hal_lora.cpp:41`; **[DS]** Table 3-5 |
-| **G6** | **The chip's 150–960 MHz range is not the module's range.** The module is an 868–923 MHz single SKU, and the narrowing is imposed by an undocumented matching network and antenna (§1.1) | **[DS]** Table 3-7 vs **[DOC]** |
-| **G7** | **`SetDIO2AsRfSwitchCtrl(true)` and the module's `SX_ANT_SW` pin are two different switches** (§5.3.1). `SX_ANT_SW`'s semantics are documented nowhere; the firmware sets it HIGH once and forgets it | **[SRC]**; [module record G4](../../m5stack/stamp-lora-1262/README.md) |
-| **G8** | **`XOSC_START_ERR` is *expected* at POR and at every cold-start wake when a TCXO is used.** Treating it as a fatal error will refuse to start a working radio (§5.2) | **[DS]** §13.3.6 |
-| **G9** | **Semtech's datasheet does not enumerate which spreading factors are unavailable at which bandwidths** — Table 6-1 carries the caveat without the table (§3.1). An unresolved gap in the primary document | **[DS]** Table 6-1 footnote 1 |
-| **G10** | **SF6 is not interoperable with SF6 on an SX1276**, and SF5/SF6 need 12 preamble symbols (§3.1). A silent interoperability failure against older LoRa nodes | **[DS]** §6.1.1.1 |
-| **G11** | **Crystal trimming caps are overwritten by the state machine** unless you are already in `STDBY_XOSC` (§6.5). And `SetDIO3AsTcxoCtrl` unconditionally forces `XTA` to 33.4 pF | **[DS]** §4.1.3 |
-| **G12** | ⚠ **Semtech's canonical datasheet could not be downloaded, and Semtech's own listing is dated 2025-04-07 — later than the Rev 2.2 (Dec 2024) copy held here.** So this document **may be one revision behind**, and that is *unresolved*, not "no lag". See §11 | `executed-failed`, 2026-09-01 |
-| **G13** | **LR-FHSS is patent-encumbered**, and Semtech's disclaimer explicitly declines to grant patent rights with the software (§1) | **[DS]** p. 2 |
-| **G14** | **No certification of any kind is published for the PaperMono**, including for its sub-GHz emitter. A single wideband 868–923 MHz SKU with no per-region variant covers EU 868, US 915 and JP 920 allocations with no regulatory paperwork to point at | **[DOC]** — negative result; [`features/lora.md` §7](../../../devices/m5stack/papermono/features/lora.md) |
-| **G15** | **Nothing has been measured.** No range, throughput, sensitivity, TX current or battery-impact figure exists from M5Stack or from anyone in the community | **[DOC]**, community — negative result |
-
----
-
-## 11. Sourcing
-
-No vendor sourcing guide exists in this repository for Semtech — see the [vendor guides index](../../../vendors/README.md). This pass's findings, for whoever writes one:
-
-> ✅ **Correction, 2026-09-07 — the sentence immediately above is now out of date and is left in place only for provenance.** **A Semtech vendor guide now exists:** [`vendors/semtech/README.md`](../../../vendors/semtech/README.md), written 2026-09-04 from this section plus a fresh probe pass. It adds: the **embedded 1 984-entry JSON document catalogue** that enumerates everything Semtech publishes; the **`/uploads/documents/` soft-404**; the **`semtech.force.com` → `semtech.my.site.com`** portal migration; the exact scope of the registration wall (**no LoRa document is behind it**); working **Digi-Key and Mouser** templates with negative controls; and the finding that an **invalid Salesforce token also returns HTTP 200**, so that endpoint cannot be probed at all.
->
-> On **G12** (whether a revision newer than Rev 2.2 exists): that catalogue confirms Semtech's current listing is `SX1261/SX1262 Datasheet` — the same document held here at Rev 2.2 — so the "2025-04-07 listing date vs Dec 2024 revision" question is **still `unresolved`**, but it is now known to be a *listing-date* field in a catalogue rather than a document date.
->
-> The original text was not edited because this pass was append-only. Parked for a maintainer in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md). Source: `scratch/lora-generations/index-fragments.md` §6.2.
-
-**`www.semtech.com` serves its product pages to a normal browser user-agent** (HTTP 200, 237 407 bytes for the SX1262 page) but **403s a `WhatsApp/2.23.20.0` agent** — the reverse of `www.st.com`, which serves the WhatsApp agent and resets the connection for Chrome. There is no single agent that works everywhere; rotate.
-
-**Semtech's documents are behind a Salesforce content-distribution front end and could not be retrieved.** The SX1261/SX1262 datasheet is linked as:
-
-```
-https://semtech.my.salesforce.com/sfc/p/E0000000JelG/a/RQ000008nKCH/hp2iKwMDKWl34g1D3LBf_zC7TGBRIo2ff5LMnS8r19s
-```
-
-A `GET` returns a **1 359-byte HTML shell** that immediately JavaScript-submits a POST back to itself. Reproducing that POST returns a **53 747-byte JavaScript application** with no `<a href>`, no iframe and no servlet URL in the markup. Two guessed direct patterns (`/sfc/dist/version/download/`, `/sfc/servlet.shepherd/document/download/`) returned 550- and 787-byte HTML errors. **Reacquisition from Semtech: `blocked`.** `executed-failed`, 2026-09-01.
-
-⚠ **The consequence is a real unresolved question.** Semtech's page labels the entry **"SX1261/SX1262 Datasheet · 2025-04-07 · PDF"**, four months *after* the Rev 2.2 (December 2024) copy held here. That is consistent with a **Rev 2.3 existing**, or with a re-upload of the same revision. **Mirror lag on this document is `unresolved`, not "none".** Previously it was recorded as "not checked"; it has now been checked and could not be settled.
-
-The **working** source is M5Stack's mirror, which is open, fast and correctly typed:
-
-```
-https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf
-```
-
-Other Semtech documents enumerated from the product page and **not retrieved** (all behind the same Salesforce shell): `AN1200.115` Murata IPD design guide (2025-11-13), `AN1200.91` SX1261/62 IPD design guide (2024-07-11), `AN1200.40` reference-design explanation, `AN1200.36` `RxDutyCycle`, `AN1200.35` software Manchester encoding, `AN1200.53` packets longer than 255 bytes, the SX1261/SX1262 Development Kit user guide, and the SX1261 LoRa Calculator. **`AN1200.37` "Recommendations for Best Performance"** is cited by the datasheet itself (§4.1.2) for heat-dissipation guidance and was not located on the product page at all.
-
----
-
-## 12. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — inside module `U14`, sheet 4
-
-**The SX1262 is not a component of the main board.** It is inside the plug-in [`Stamp-LoRa-1262-mini`](../../m5stack/stamp-lora-1262/README.md) module (`U14`, sheet 4), which presents a 13-pin SPI-plus-control interface. **That record owns the board integration**; this section states only what the *chip* does on this board and points at it.
-
-Chip-level facts established for this board:
-
-| Chip-level property | Value on the PaperMono | Evidence |
-|---|---|---|
-| Part class | **SX1262** (high-power, +22 dBm), not SX1261 | firmware requests 22 dBm and instantiates `SX1262`; module name — **[SRC]** `hal_lora.cpp:37,328` |
-| Host SPI | mode 0, **8 MHz** (chip maximum 16 MHz) | **[SRC]** `hal_lora.cpp:31` |
-| `BUSY` handshake | wired out to **ESP32-S3 GPIO21**; RadioLib honours it | **[SCH]**, **[SRC]** `hal_lora.cpp:28` |
-| `DIO1` | wired out to **ESP32-S3 GPIO5** as the sole IRQ line, registered `GPIO_INTR_POSEDGE`, and also an **ESP32 wake source** | **[SCH]**, **[SRC]** `hal_lora.cpp:27`, `app_sleep_wake.cpp:44` |
-| `DIO2` | **configured as an internal RF switch control** — `setDio2AsRfSwitch(true)` | **[SRC]** `hal_lora.cpp:343` |
-| `DIO3` | **configured as a 3.0 V TCXO supply** (`tcxoVoltage = 0x06`) — `inferred` (§5.2.1) | **[SRC]** `hal_lora.cpp:40,334` |
-| `NRESET` | not driven by RadioLib (`RADIOLIB_NC`); reset is **M5IOE1 `IO10`** | **[SRC]** `hal_lora.cpp:327,330` |
-| Regulator mode | **LDO**, not DC-DC — ~2× receive current (§5.4) | **[SRC]** `hal_lora.cpp:41` |
-| OCP | `setCurrentLimit(140.0f)` — the SX1262 post-`SetPaConfig` default (§6.2) | **[SRC]** `hal_lora.cpp:344` |
-| Supply | **3.3 V** on the module's `VIN_3V3`, from an SSP7615-33DFR LDO gated by **M5PM1 `IO2`** | **[SCH]**; [module record §3.5](../../m5stack/stamp-lora-1262/README.md) |
-
-The full radio configuration the factory firmware programs **[SRC]** `hal_lora.cpp:32-43`, `:333-344`:
-
-| Parameter | Value | Note |
-|---|---|---|
-| Frequency | **868.0 MHz** | hard-coded; the EU band, at the bottom of the module's 868–923 range |
-| Bandwidth | 62.5 kHz | |
-| Spreading factor | **12** | −20 dB demodulator SNR (§3.1) |
-| Coding rate | 8 (4/8) | maximum FEC |
-| Sync word | `0x34` | |
-| TX power | **22 dBm** | ⇒ ~118 mA (§6.1) |
-| Preamble | 10 symbols | ⚠ Semtech recommends **12** (§3.1) |
-| TCXO voltage | 3.0 V | §5.2.1 |
-| Regulator | LDO | §5.4 |
-| Current limit | 140 mA | §6.2 |
-| Max packet | 255 bytes | the 256-byte buffer (§3.4) |
-
-This is **SF12 at 62.5 kHz with CR 4/8** — on the order of tens of bits per second. It is a maximum-range demonstration, not a sensible throughput default, and anyone building on it should change it deliberately.
-
-⚠ **Two things in that table are worth a second look.** The preamble is **10 symbols** where Semtech recommends 12 for optimal performance across the receiver's dynamic range (and *requires* 12 at SF5/SF6, though SF12 is in use here) **[DS]** §6.1.1.1, Rev 1.1 changelog. And the whole configuration assumes a matching network nobody outside M5Stack has seen (§1.1, G1).
-
-For host wiring, bring-up ordering, the `SX_ANT_SW` question, the SPI-host naming mismatch and the unlabelled module pins 11–13, go to the **[Stamp-LoRa-1262 record](../../m5stack/stamp-lora-1262/README.md)** and to [`features/lora.md`](../../../devices/m5stack/papermono/features/lora.md).
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) — **not fitted**
-
-**The Lite has no SX1262, and no LoRa module to put one in.** It has no LoRa row in its specification table, no LoRa block in its PinMap, and its PlatformIO `lib_deps` omits `RadioLib` entirely **[DOC]**. Its product weight is 2.3 g lower than the PaperMono's (72.4 g vs 74.7 g), consistent with two omitted radios.
-
-Together with the [ST25R3916 NFC front end](../../stmicroelectronics/st25r3916/README.md), LoRa is the whole of the **USD 10.00** difference between C153 (USD 65.00) and C153-LITE (USD 55.00) **[DOC]**. One widely repeated launch article inverted this and claimed the USD 55 model has NFC and LoRa; it does not.
-
-Note that the shared `M5PaperMono-UserDemo` firmware image serves **both** SKUs and detects the variant at runtime by probing the **NFC** rail, **not** the radio **[SRC]** `hal_board.cpp:160-172`. So a Lite runs the same binary and simply never brings the radio up.
-
-### [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) — inside module `M1` · *added 2026-09-04*
-
-A **Cardputer-Adv / CardputerZero** expansion board, store publish date **2025-12-30**, carrying the same `Stamp LoRa-1262 Mini` module as the PaperMono but wired **entirely differently**. Read this row before copying any PaperMono configuration.
-
-| Function | Host GPIO (Cardputer-Adv) | Contrast with PaperMono |
-|---|---|---|
-| SPI SCK / MOSI / MISO | **G40 / G14 / G39** | ⚠ **shared with the host's microSD** (`SDCARD_CS` = G12); PaperMono gives the radio its own bus |
-| `NSS` | **G5** | — |
-| `BUSY` | **G6** | direct GPIO, not behind an expander |
-| `DIO1` (`LoRa_IRQ`) | **G4** | direct GPIO |
-| `NRST` | **G3** — **an ordinary host pin** | PaperMono routes reset through the **M5IOE1 I²C expander** |
-| External antenna switch | **`PI4IOE5V6408` P0 @ I²C 0x43** | PaperMono uses **M5IOE1 `IO2`** |
-| Rail enable | **none** — the on-board `JW5712` buck is pulled on and stays on | PaperMono gates `3V3_L2_LoRa` with **M5PM1 `IO2`** |
-| Antenna | **external SMA/RP-SMA** + rubber duck | PaperMono uses a built-in FPC antenna |
-| `setDio2AsRfSwitch` | **not called** by M5Stack's Cap example | PaperMono firmware calls it `true` |
-
-**⚠ The two boards disagree about the TCXO voltage, and both are shipping.**
-
-| Source | `DIO3` TCXO voltage |
-|---|---|
-| M5Stack Cap Arduino example (`radio.begin(…, 3.0, true)`) | **3.0 V** |
-| M5Stack PaperMono firmware | **3.0 V** |
-| **Meshtastic upstream `variants/esp32s3/m5stack_cardputer_adv/variant.h`** | **`SX126X_DIO3_TCXO_VOLTAGE 1.8`** + `TCXO_OPTIONAL` |
-
-Since §5.2 of this record explains that a wrong `DIO3` setting yields a radio that initialises and then fails silently, the disagreement matters. Both are reported working in the field. Unresolved; start from **3.0 V** on M5Stack's own hardware. See [`devices/m5stack/cap-lora-1262/features/lora.md` §8](../../../devices/m5stack/cap-lora-1262/features/lora.md).
-
-Vendor claims for this board: **+22 dBm**, **−147 dBm**, 868–923 MHz single wideband SKU, **no published certification of any kind**. Default RadioLib configuration in M5Stack's example: 868.0 MHz, BW 125 kHz, SF12, CR 4/5, sync `0x34`, preamble 20, `useRegulatorLDO = true`, `setCurrentLimit(140)`.
-
-**Meshtastic supports this board upstream** — board `m5stack-cardputer-adv`, hardware model `meshtastic_HardwareModel_M5STACK_CARDPUTER_ADV = 112`, introduced by PR #9540 (merged 2026-03-06, commit `969aefa551d645e6110be11f330774e15ad9c87d`), first shipped in **v2.7.20.6658ec2** (2026-03-11); the antenna-switch init was fixed in **v2.7.24** (2026-05-23).
-
-### [M5Stack Cap LoRa868 (U201)](../../../devices/m5stack/cap-lora868/README.md) — inside a `Stamp LoRa-1262` (standard size) · *added 2026-09-04*
-
-The predecessor Cap, published **2025-09-05**, now **[EOL]**. Same SX1262, same host pin map, but **+20 dBm** rather than +22, **no shield can**, **no RF-switch control** and **no Grove port**. Firmware distinguishes the two Caps by probing I²C `0x43` — present means U214. Its documentation publishes the only state-resolved current figures in the family: GPS on / LoRa standby **29.24 mA**, GPS sleep / LoRa standby **3.16 mA**, GPS sleep / LoRa TX max **129.72 mA**, GPS on / LoRa TX max **155.03 mA** at DC 5 V.
-
-### [M5Stack Cardputer Mesh Kit (K152)](../../../devices/m5stack/cardputer-mesh-kit/README.md) — via the bundled Cap LoRa-1262 · *added 2026-09-04*
-
-Cardputer-Adv + Cap LoRa-1262, published 2026-04-30, USD 48.00, pre-flashed with Meshtastic and the **only** configuration eligible for Meshtastic authorised-device registration.
-
-### [M5Stack Stamp C6LoRa (S012)](../../../devices/m5stack/stamp-c6lora/README.md) and [Unit C6L (U202)](../../../devices/m5stack/unit-c6l/README.md) — *added 2026-09-04*
-
-An **SX1262 paired with an ESP32-C6** on one SMD module, 850–960 MHz, +22 dBm, −148 dBm, with an **SGM13005L4 LNA** and a **`PI4IOE5V6408`** expander controlling both the RF switch *and* the LNA enable. Unit C6L is the Grove-cabled product built around it and has its own Meshtastic variant, `variants/esp32c6/m5stack_unitc6l/`, hardware model `M5STACK_C6L = 111`. Light records; the module schematic is held but not decoded.
-
-### [M5Stack Cardputer Mesh Kit (K152)](../../../devices/m5stack/cardputer-mesh-kit/README.md) — host-side integration · *added 2026-09-07*
-
-The SX1262 itself sits on the [Cap LoRa-1262](../../../devices/m5stack/cap-lora-1262/README.md),
-which plugs into the **Cardputer ADV's** EXT 2.54-14P header. Host-side pin assignment, agreed by
-three independent implementations (M5Stack's factory firmware, Meshtastic's variant, and the
-docs PinMap):
-
-| Function | Host GPIO |
-|---|---|
-| `NSS` | G5 |
-| `RESET` | G3 |
-| `DIO1` / IRQ | G4 |
-| `BUSY` | G6 |
-| SPI `SCK`/`MOSI`/`MISO` | G40 / G14 / G39 — **shared with the microSD card**, CS G12 |
-
-Meshtastic additionally declares `SX126X_DIO2_AS_RF_SWITCH` and
-`SX126X_DIO3_TCXO_VOLTAGE 1.8` with `TCXO_OPTIONAL`.
-
-⚠ **Initialisation requires one non-obvious step**: M5Stack states that the RF antenna switch
-must be enabled by setting **`P0` of the Cap's PI4IOE I/O expander HIGH**, over the host's
-*internal* I²C bus (G8/G9). Omit it and the radio transmits into a disconnected antenna.
-
-Host-side interface documentation:
-[`devices/m5stack/cardputer-adv/features/cap-header.md`](../../../devices/m5stack/cardputer-adv/features/cap-header.md).
-
-### [LilyGO T-Display K230 / Kit](../../../devices/lilygo/t-display-k230/README.md) — main board, default radio · *added 2026-09-07*
-
-One of two selectable radios; the other is [LR2021](../lr2021/README.md). Fitted on the K230 main
-board and exposed to userspace through **spidev**, driven by **RadioLib** — there is no in-kernel
-LoRa driver on this board.
-
-`MOSI` ← `GPIO16` · `MISO` → `GPIO17` · `SCK` ← `GPIO15` · `CS` ← `GPIO14` · `RESET` ← `GPIO5` ·
-`BUSY` → `GPIO19` · **`DIO1` → `GPIO20`** · power-enable ← `GPIO44`.
-
-⚠ **The interrupt DIO differs by fitted radio.** On SX1262 units it is `DIO1`; on LR2021 units it
-is `DIO11`. Both land on K230 `GPIO20`, so firmware that hard-codes `DIO1` silently sees no
-interrupts on an LR2021 board.
-
-Band is fixed per SKU: `K256` 868 MHz · `K256-A` 915 MHz · `K256-B` 923 MHz · `K256-C` 433 MHz.
-LilyGO states that **Meshtastic voice and photo transfer are unavailable on SX1262 units** — those
-boards get text mesh only; the LR2021 variant is required for media.
-
----
-
-## 13. Related components
-
-- [**M5Stack Stamp-LoRa-1262**](../../m5stack/stamp-lora-1262/README.md) — **the module this chip lives inside.** Pinout, host wiring, reset, antenna switch, power gating and bring-up order are all there. Read it before this one if you are working on the board rather than the radio
-- [**M5Stack M5IOE1**](../../m5stack/m5ioe1/README.md) — supplies the module's `NRST` (`IO10`) and `ANT_SW` (`IO2`). ⚠ its enum values are one *less* than its pin labels
-- [**M5Stack M5PM1**](../../m5stack/m5pm1/README.md) — gates the module's 3.3 V rail via `IO2`
-- [**Espressif ESP32-S3R8**](../../espressif/esp32-s3r8/README.md) — the host; `SPI3_HOST` on GPIO38/39/40/41, plus GPIO21 `BUSY` and GPIO5 `DIO1`
-- [**SSP7615-33DFR**](../../generic/ssp7615-33dfr/README.md) — the 400 mA LDO producing `3V3_L2_LoRa`
-- [**STMicroelectronics ST25R3916**](../../stmicroelectronics/st25r3916/README.md) — the other radio the Lite does without
-- [Vendor sourcing guides index](../../../vendors/README.md) — **no Semtech guide exists yet**; §11 is what one would open with
-- [Components index](../../README.md)
-
----
-
-## 14. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf` | 4 459 535 | `6d783125dbef567954ce53095ad068d0950b2a8de52f95bb2cfde4146c4306c2` | **SX1261/2 datasheet, `DS.SX1261-2.W.APP` Rev 2.2, December 2024, 118 pp.** PDF metadata: Title `DS_SX1261_2 V2-2.pdf`, Author `julie`, Creator `FrameMaker 16.0.6`, Producer `Adobe PDF Library 17.0`, created 2024-12-04, modified 2024-12-05. **This describes the chip, not the module** (§10-G1) |
-
-| Field | Value |
-|---|---|
-| Version / revision | **Rev 2.2** (revision history runs Rev 1.0, October 2017 → Rev 2.2) |
-| Publication date | **December 2024** |
-| Retrieval date | **2026-09-01** |
-| Byte size | **4 459 535** |
-| SHA-256 | `6d783125dbef567954ce53095ad068d0950b2a8de52f95bb2cfde4146c4306c2` |
-| **Canonical URL** | `https://semtech.my.salesforce.com/sfc/p/E0000000JelG/a/RQ000008nKCH/hp2iKwMDKWl34g1D3LBf_zC7TGBRIo2ff5LMnS8r19s` — linked from `https://www.semtech.com/products/wireless-rf/lora-connect/sx1262`. ⚠ **`blocked`**: JavaScript/POST content-distribution shell, see §11 |
-| **M5Stack mirror URL** | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf` — open, HTTP 200, `application/pdf` |
-| Mirror lag | ⚠ **`unresolved`.** Semtech's listing is dated **2025-04-07**, four months after Rev 2.2. Canonical download blocked, so a Rev 2.3 can be neither confirmed nor ruled out (§10-G12) |
-| Licence | **`unknown`** — © Semtech Corporation. The document carries Semtech's standard disclaimer plus an explicit **LR-FHSS patent notice** (§1) that grants no patent rights |
-| Redistribution status | **`unknown`** |
-| Disposition | **`repository`** |
-| Type validated | Yes — `%PDF-1.6`, 118 pages, `pdfinfo` metadata as above |
-| ⚠ Text-layer note | **Figure-label fonts carry a uniform +31 code-point offset** and extract as legible-but-wrong text. Body text and tables are clean. See the Evidence labelling section |
-
-**Reacquisition:** use the M5Stack mirror. Semtech's own path is `blocked` for automated clients and requires a browser (§11). Recorded honestly rather than omitted.
-
-The module-level document that *should* exist does not: see [`components/m5stack/stamp-lora-1262/README.md` §8](../../m5stack/stamp-lora-1262/README.md), whose `artifacts/` directory is empty for exactly that reason.
-
----
-
-## 15. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | SX1261/2 Datasheet — Long Range, Low Power sub-GHz RF Transceiver | **Semtech Corporation**, mirrored by M5Stack | credible mirror | datasheet | `artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf`; mirror `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf` | 2026-09-01 | **Rev 2.2, December 2024**, `DS.SX1261-2.W.APP`, 118 pp | §1–§8, §10 |
-| S-2 | SX1262 product page — document list and dates | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-connect/sx1262` | 2026-09-01 | datasheet entry dated **2025-04-07** | §11, §10-G12; enumerates the application notes |
-| S-3 | Semtech Salesforce content-distribution endpoint | Semtech | primary | download shell | `semtech.my.salesforce.com/sfc/p/E0000000JelG/a/RQ000008nKCH/…` | 2026-09-01 | — | §11 — **negative result**, `executed-failed`; reacquisition `blocked` |
-| S-4 | PaperMono schematic, sheet 4 (`U14`) | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | **V0.6.2, 2026-05-22** | §2 module-boundary mapping, §12 |
-| S-5 | `M5PaperMono-UserDemo` — `main/hal/hal_lora.cpp`, `main/app_sleep_wake.cpp`, `repos.json`, `dependencies.lock` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-UserDemo` @ `c1099107271d31a0678d661a896e2b04dbb331ea` | 2026-09-01 | 2026-08-10, MIT | §5.2.1, §5.3.1, §5.4, §6.2, §9, §12 |
-| S-6 | RadioLib | jgromes | third-party | source | `github.com/jgromes/RadioLib` @ `b91c6af112e423dcb14529ade5827802a14e1015` | 2026-09-01 | tag **7.2.1**; upstream licence LGPL-3.0 (**unverified**) | §9 |
-| S-7 | PaperMono product page — specification table, PinMap, *Datasheets* list | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono` | 2026-09-01 | undated | §1.1 band, §10-G1, §12 |
-| S-8 | PaperMono-Lite product page | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono-Lite` | 2026-09-01 | undated | §12 — **negative result**: no LoRa row, no `RadioLib` |
-| S-9 | Certification index | M5Stack | primary | vendor docs | `docs.m5stack.com/en/certification` | 2026-09-01 | undated | §10-G14 — **negative result**, 0 matches for `PaperMono` / `C153` |
-| S-10 | `C153-PaperMono-UserDemo-v1.2` firmware image | M5Stack via M5Burner | primary | binary | SHA-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | 2026-09-01 | v1.2, built 2026-08-06, IDF v5.5.1 | corroborates the LoRa pin map and wake source |
-
-## G4 — RadioLib §15 errata workarounds — **RESOLVED 2026-09-02**
-
-Previously open as: "whether RadioLib applies all four SX126x datasheet §15
-workarounds — not verified", and later verified only on `master` 7.7.1, which is
-**not** the version the M5Stack PaperMono pins.
-
-**Verified at tag `7.2.1`** — the pinned version — by reading the source through
-the GitHub contents API (`executed-success` for the retrieval; `inferred` for
-behaviour, nothing was run on hardware):
-
-| Datasheet §15 item | Symbol in `src/modules/SX126x/SX126x.cpp` @ 7.2.1 | Present |
-|---|---|---|
-| 15.1 RX gain / sensitivity | `rxGain` / sensitivity path | ✅ ×4 |
-| 15.2 PA clamping (Tx resistance to antenna mismatch) | `fixPaClamping` | ✅ ×1 |
-| 15.3 Implicit-header-mode timeout | `fixImplicitTimeout` | ✅ ×3 |
-| 15.4 Inverted-IQ operation | `fixInvertedIQ` | ✅ ×2 |
-
-`fixPaClamping` additionally appears ×3 in `SX1262.cpp` and **×0 in
-`SX1261.cpp`**, exactly matching the datasheet's "SX1262 only" note — a good sign
-the workaround is applied deliberately rather than blanket.
-
-**Conclusion: 7.2.1 behaves as master does on this point.** The gap is closed for
-the shipping version, not just the current one.
diff --git a/components/semtech/sx1262/artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf b/components/semtech/sx1262/artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf
deleted file mode 100644
index 45c6fb0..0000000
Binary files a/components/semtech/sx1262/artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/semtech/sx1268/README.md b/components/semtech/sx1268/README.md
deleted file mode 100644
index be4496c..0000000
--- a/components/semtech/sx1268/README.md
+++ /dev/null
@@ -1,161 +0,0 @@
-# Semtech SX1268 — the 410–810 MHz SX1262
-
-> **Lineage:** [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md).
-> **Domain:** [`guides/lora`](../../../guides/lora/README.md). **Full sibling record:**
-> [`sx1262`](../sx1262/README.md) — the register model, `BUSY` handshake, DIO2/DIO3 behaviour, the
-> DC-DC/LDO trade and the four mandatory errata workarounds. **All of it applies here unchanged.**
-
-- **Category:** sub-GHz **LoRa / (G)FSK** transceiver, SPI command interface, **+22 dBm**
-- **Frequency:** ⚠ **410–810 MHz** — *not* the SX1262's 150–960 MHz
-- **Generation:** **2** — an SX1262 sibling. ⚠ Not named in `DS.LR20xx` §23.8; the assignment is **[INF]** from the shared datasheet family and Semtech's own grouping of "SX1261, SX1262 and SX1268" on one product page **[PP]**
-- **Package:** QFN24, 4 × 4 mm · Order code **`SX1268IMLTRT`**, tape & reel, 3 000 pieces **[PP]**
-- **Research depth:** ⚠ **light record.** The SX1261/2/8 datasheet family is Salesforce-gated; **no SX1268-specific document was obtained.** Content is Semtech's product page, RadioLib source, and the SX1262 record.
-- **Retrieved:** 2026-09-04
-
----
-
-## 1. What is different, and it is only one thing that matters
-
-Semtech's product page covers the SX1261, SX1262 and SX1268 together, and the operative sentence is
-**[PP]**:
-
-> The **SX1268 is suitable for systems targeting compliance with Chinese regulatory requirements**,
-> and runs in the **410 – 810 MHz** range.
-
-| | **SX1262** | **SX1268** |
-|---|---|---|
-| **Frequency range** | **150 – 960 MHz** | ⚠ **410 – 810 MHz** |
-| Max Tx | +22 dBm | **+22 dBm** |
-| Max link budget **[PP]** | **170 dB** (quoted as "SX1262 / 68") | **170 dB** |
-| Best sensitivity | −148 dBm | −148 dBm |
-| RX current | 4.6 mA | 4.6 mA |
-| LoRa bit rate | to 62.5 kbps | to 62.5 kbps |
-| FSK bit rate | to 300 kbps | to 300 kbps |
-| SF range | SF5–SF12, **no restriction** | SF5–SF12, **no restriction** |
-| Blocking immunity @1 MHz offset | 88 dB | 88 dB |
-| Co-channel rejection, LoRa | 19 dB | 19 dB |
-| Errata §15 PA clamp fix | **required** | **required** |
-| Package | QFN24 4 × 4 | QFN24 4 × 4 |
-
-**So: an SX1268 is an SX1262 with a different synthesiser/front-end range.** Everything else —
-command set, register map, `BUSY`, DIO conventions, PA topology, errata — is the same. That is the
-opposite of the [LLCC68](../llcc68/README.md), which keeps the band and cuts the configuration
-space.
-
-### 1.1 RadioLib encodes exactly this **[RL]**
-
-Read live 2026-09-04; the [`guides/lora` §4 table](../../../guides/lora/README.md) records the same
-lines:
-
-| | `SX1262.cpp` | `SX1268.cpp` |
-|---|---|---|
-| Enforced frequency range | **150 – 960 MHz** (`:179`) | ⚠ **410 – 810 MHz** (`:180`) |
-| Enforced power range | −9 … +22 dBm (`:212`) | −9 … +22 dBm (`:213`) |
-| `fixPaClamping()` called from | every `begin`/`beginFSK` variant (`:62,94,125,153`) | **every `begin`/`beginFSK` variant (`:62,94,125,153`)** |
-
-⚠ **`fixPaClamping()` is called on the SX1268 and on no `SX1261` path** — which is independent
-confirmation that the SX1268 shares the SX1262's `VBAT`-fed +22 dBm PA topology and therefore its
-errata §15.2 5–6 dB clamp defect, even though the datasheet's note is worded "SX1262 only". Treat
-the errata section as applying to the whole +22 dBm class. **[INF]**, strongly.
-
-### 1.2 ⚠ Where the substitution trap actually is
-
-**Not on the bench — in the band plan.**
-
-- **868 MHz (EU) and 915 MHz (US) are outside the SX1268's range.** An SX1268 fitted where an
-  SX1262 was expected simply cannot operate in the two most common ISM allocations. RadioLib rejects
-  the frequency; a hand-rolled driver may not, and will produce an unlocked PLL or an out-of-spec
-  emission.
-- **433 MHz and the Chinese 470–510 MHz allocation are the SX1268's home**, and there it is the
-  right part — the SX1262 covers those frequencies too, but the SX1268's front end is matched for
-  them.
-- ⚠ **Cheap 433 MHz modules are frequently SX1268 while their listings say "SX1262".** Because the
-  parts are pin-compatible and the command set is identical, a driver written for an SX1262 will
-  *appear* to work at 433 MHz on either. The divergence only shows up when someone tries to reuse
-  the same board design at 868 MHz.
-- **How to tell:** ask the driver for **915 MHz**. An SX1262 accepts it; an SX1268 must not.
-  **[INF]**, `not-tested` here.
-
----
-
-## 2. What is identical to the SX1262
-
-Everything in [`components/semtech/sx1262/README.md`](../sx1262/README.md) except the frequency row.
-Specifically: the SPI command interface and 8-bit opcodes; the mandatory `BUSY` handshake;
-`SetDio2AsRfSwitchCtrl` and `SetDio3AsTcxoCtrl`; the **`VBAT`-fed PA** and the consequence that the
-DC-DC cannot reduce transmit current; the 140 mA over-current setting after `SetPaConfig`; the four
-§15 errata workarounds; and `XOSC_START_ERR` being expected at power-on with a TCXO.
-
-**Do not duplicate that material here.**
-
----
-
-## 3. Software support
-
-| Stack | Status |
-|---|---|
-| **RadioLib** | ✅ `src/modules/SX126x/SX1268.{h,cpp}` — a sibling class of `SX1262` over the shared `SX126x` base. MIT **[RL]** |
-| **Semtech `sx126x_driver`** | ✅ covers SX1261/SX1262/SX1268 in one driver, **BSD-3-Clause-Clear**, last push **2025-10-15** **[GH]** |
-| **`SWSD003`** | LR11xx **and** SX126x SDK, explicitly *"SX126x chip (SX1261 / SX1262 / SX1268)"* **[GH]** |
-| **`one_channel_hub`** | *"with support of sx1261, sx1262, sx1268 and llcc68"* **[GH]** |
-| **Meshtastic** | ✅ `SX1268_RADIO` in `LoRaRadioType`, present in **v2.7.26 stable** **[MT]** |
-| **USP** | "buildable" on SX126x shields **[GH]** |
-| Linux kernel | ❌ none |
-
----
-
-## 4. Caveats and gaps
-
-| # | Issue |
-|---|---|
-| **S1** | ⚠ **No SX1268-specific document was obtained.** Salesforce-gated ([vendor guide §4](../../../vendors/semtech/README.md)). Every figure here is from the product page or RadioLib source |
-| **S2** | ⚠ **410–810 MHz, not 150–960 MHz.** 868 MHz and 915 MHz are out of range (§1.2) |
-| **S3** | ⚠ **Pin-compatible with the SX1262**, so substitution is invisible from the PCB and from the driver until you change band |
-| **S4** | **Errata §15.2's "SX1262 only" wording under-states it.** RadioLib applies `fixPaClamping()` to the SX1268 as well (§1.1). Treat it as "+22 dBm class" |
-| **S5** | **Generation assignment is `inferred`**, not stated by Semtech |
-| **S6** | ⚠ **The "170 dB link budget" figure is printed as "(SX1262 / 68)"** on a page that also covers the SX1261. Do not copy it into an SX1261 row |
-| **S7** | **Nothing measured**; no SX1268 hardware in this knowledge base |
-| **S8** | **Introduction date not established.** `unresolved` |
-
----
-
-## 5. Used By
-
-**No board in this knowledge base uses an SX1268.** Every LoRa-bearing device here carries an
-[SX1262](../sx1262/README.md). This record exists because the two are pin-compatible, because
-433 MHz modules commonly carry the 68, and because
-[`guides/lora` §4](../../../guides/lora/README.md) already compares the three parts and deserved a
-component record to point at.
-
----
-
-## 6. Local artifacts
-
-**None.** No SX1268-specific document was obtained; the SX1261/2 datasheet held under
-[`sx1262/artifacts/`](../sx1262/README.md) does **not** cover the SX1268. Recorded as a deliberate
-gap; `artifacts/` does not exist for this component.
-
-**How to fill it:** Digi-Key or Mouser mirror per
-[`vendors/semtech/README.md` §6](../../../vendors/semtech/README.md). ⚠ The Wayback CDX index for
-`semtech.com` has `DS_SX1261-2_V1.1.pdf` but **no SX1268 datasheet**.
-
----
-
-## 7. Related components
-
-- [**Semtech SX1262**](../sx1262/README.md) — **the record to read.** Everything except the frequency row applies
-- [**Semtech LLCC68**](../llcc68/README.md) — the other SX1262 sibling; restricts SF/BW instead of band, and is the nastier trap
-- [**Semtech LR2021**](../lr2021/README.md) — **Gen 4** · [**LR1121**](../lr1121/README.md) — **Gen 3** · [**SX1276**](../sx1276/README.md) — **Gen 1**
-- [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md) · [`guides/lora` §4](../../../guides/lora/README.md) · [`vendors/semtech/README.md`](../../../vendors/semtech/README.md) · [Components index](../../README.md)
-
----
-
-## 8. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S-1 | SX1268 product page (covers SX1261/SX1262/SX1268) | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-connect/sx1268` | 2026-09-04 | §1 — the 410–810 MHz range and the Chinese-regulatory framing |
-| S-2 | RadioLib `src/modules/SX126x/SX1268.cpp` | jgromes | community | source | `github.com/jgromes/RadioLib` | 2026-09-04 | §1.1, §3 |
-| S-3 | `LoRa-Net/sx126x_driver`, `SWSD003`, `one_channel_hub` | Semtech | primary | source | `github.com/LoRa-Net` | 2026-09-04 | §3 |
-| S-4 | Meshtastic `src/detect/LoRaRadioType.h` @ `v2.7.26.54e0d8d` | Meshtastic | community | source | `github.com/meshtastic/firmware` | 2026-09-04 | §3 |
-| S-5 | SX1262 component record; `guides/lora` §4 | this repository | derived | record | [`sx1262`](../sx1262/README.md), [`guides/lora`](../../../guides/lora/README.md) | 2026-09-04 | §1.1, §2 |
diff --git a/components/semtech/sx1276/README.md b/components/semtech/sx1276/README.md
deleted file mode 100644
index 787740d..0000000
--- a/components/semtech/sx1276/README.md
+++ /dev/null
@@ -1,251 +0,0 @@
-# Semtech SX1276/77/78/79 (SX127x) — the first-generation LoRa transceiver
-
-> **Lineage:** [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md)
-> — the four generations side by side. **Domain:** [`guides/lora`](../../../guides/lora/README.md).
-
-- **Category:** sub-GHz **LoRa / FSK / GFSK / MSK / GMSK / OOK** transceiver, **register-mapped SPI**
-- **Bands:** **137–1020 MHz** (SX1276/77/78/79); the SX1272/73 sibling covers **860–1020 MHz**
-- **Package:** **QFN 28** · Order code `SX1276IMLTRT`, Pb-free/halogen-free/RoHS **[PP]**
-- **Generation:** **1.** `DS.LR20xx` §23.8: *"Generation 1 (Gen 1): **SX1272, SX1276** - First LoRa chips (**2013**)"* **[DS20]**
-- **Silicon revision:** **V1b**, `RegVersion` (`0x42`) = `0x12`. ⚠ V1a exists and is engineering-sample only **[ER76]**
-- **Research depth:** **light record with real artifacts.** The **Rev 5 datasheet (August 2016, 132 pp) and both errata notes are retained.** The current revision is **Rev 7** and was **not** obtained (G1).
-- **Retrieved:** 2026-09-04
-
-**Why this record exists.** No board in this knowledge base uses an SX127x. It is here so the
-generation lineage is navigable, and because **the SX127x → SX126x break is the canonical
-"everything changed" migration** that the LR2021 record's §3 is measured against.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning |
-|---|---|
-| **[DS76]** | `artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf` — **Rev. 5, August 2016**, 132 pp |
-| **[ER76]** | `artifacts/sx1276-77-78-errata-wayback.pdf` — SX1276/77/78 Errata Note, **Revision 1, Sept 2013** |
-| **[ER72]** | `artifacts/sx1272-73-errata-wayback.pdf` — SX1272/73 Errata Note |
-| **[PP]** | Semtech product pages (`…/lora-connect/sx1276`, `…/sx1272`), retrieved 2026-09-04 |
-| **[DS20]** | `DS.LR20xx` Rev 2.1 — cited for cross-generation statements only. [Held here](../lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) |
-| **[RL]** | RadioLib source, read live |
-| **[INF]** | Inference |
-
----
-
-## 1. Two sub-families, and they are not the same silicon
-
-The most common SX127x error is treating "SX127x" as one part. **[PP]**:
-
-| | **SX1272 / SX1273** | **SX1276 / 77 / 78 / 79** |
-|---|---|---|
-| Frequency | **860–1020 MHz** | **137–1020 MHz** |
-| Max link budget | **157 dB** | **168 dB** |
-| Best sensitivity | **−137 dBm** | **−148 dBm** |
-| IIP3 | −12.5 dBm | −11 dBm |
-| Blocking immunity | 89 dB | "excellent" (not quoted numerically) |
-| RX current | **10 mA** | **9.9 mA** |
-| Register retention | **100 nA** | **200 nA** |
-| Order codes | `SX1272IMLTRT`, `SX1273IMLTRT` | `SX1276IMLTRT` (+77/78/79) |
-| Errata | **[ER72]** | **[ER76]** |
-| Package | QFN 28 | QFN 28 |
-
-Shared by both: +20 dBm PA (100 mW, constant vs supply) and a +14 dBm high-efficiency PA;
-programmable bit rate to 300 kbps; **FSK, GFSK, MSK, GMSK, LoRa and OOK**; built-in bit synchroniser;
-preamble detection; 127 dB dynamic-range RSSI; automatic RF sense and CAD with ultra-fast AFC;
-**packet engine up to 256 bytes with CRC**; 61 Hz synthesiser resolution; built-in temperature sensor
-and low-battery detector. **[PP]**
-
-⚠ **Within the SX1276/77/78/79 group the differences are bandwidth and band, not architecture** —
-`RFM95`/`RFM96`/`RFM98` modules are built on them and the module suffix does not always match the
-die. **This record does not resolve which module carries which die**; that is a per-module question.
-
----
-
-## 2. ⭐ The register model — what SX126x threw away
-
-This is the section worth reading even if you never touch a Gen-1 part, because it is the *before*
-picture for [`lora-radio-generations` §3.1](../../../guides/hardware/lora-radio-generations.md).
-
-**[DS76]** §4.3, verbatim in substance:
-
-- SPI, **CPOL = 0, CPHA = 0**, slave only, max 10 MHz.
-- **The first byte is an address byte**: **1 `wnr` bit (1 = write, 0 = read) + 7 address bits, MSB
-  first.** So the whole device is **128 registers**, and that is the entire interface.
-- Three access modes:
-  - **SINGLE** — address byte, then one data byte.
-  - **BURST** — address byte then many data bytes; **the address auto-increments internally**.
-  - **FIFO** — if the address byte is the FIFO's address, the address is **memorised and does not
-    increment**, so succeeding bytes stream into/out of the FIFO.
-- ⚠ **On a write, MISO returns the register's value *before* the write.** A free read-back that
-  almost nobody uses, and a genuine trap if you assume MISO is idle during writes.
-- **There is no `BUSY` pin.** Timing is the driver's problem.
-- **Mode is a register**, not a command: `RegOpMode` (`0x01`) holds the operating mode **and the
-  LoRa/FSK selection bit**, and *"it is possible to access any mode from any other mode by changing
-  the value in the `RegOpMode` register."*
-- ⚠ **There are two register maps, and they overlap.** **[DS76]** §6.2 is the FSK/OOK map and §6.4
-  is the LoRa map; the same address means different things depending on the `RegOpMode` modem bit.
-  Address `0x28` is `RegSyncValue1` in FSK and `RegFeiMsb` in LoRa. **This is the single nastiest
-  property of the Gen-1 interface** and it is why a half-initialised driver produces plausible
-  nonsense rather than an error.
-- **Interrupts** are mapped to **DIO0–DIO5** through `RegDioMapping1`/`RegDioMapping2` — host-side
-  configuration of which event lands on which pin.
-
-**Every one of those properties is gone in Gen 2.** No address byte, no `wnr` bit, no auto-increment
-semantics, no dual register map, no `RegOpMode`; instead an 8-bit opcode, a mandatory `BUSY`
-handshake, and `SetStandby`/`SetRx`/`SetTx` commands. That is why nothing ports, and why RadioLib
-keeps `SX127x` and `SX126x` as unrelated modules **[RL]**.
-
----
-
-## 3. Analog and power
-
-**[DS76]** §5:
-
-- Internal voltage regulation across the full industrial range. **+17 dBm is maintained from 1.8 V
-  to 3.7 V; +20 dBm requires 2.4 V to 3.7 V.** ⚠ A real constraint on a single-cell Li-ion design as
-  it discharges.
-- Supplies split three ways — `VBAT_ANA`, `VBAT_RF`, `VBAT_DIG` — with decoupling on `VR_PA`,
-  `VR_DIG`, `VR_ANA`. **No DC-DC anywhere.** Gen 2 adds one for the core; Gen 4 adds a SIMO that
-  feeds the PA too ([lineage §5.2](../../../guides/hardware/lora-radio-generations.md)).
-- Crystal on `XTA`/`XTB`, Pierce oscillator, automatic PLL trigger when stable. **A TCXO is
-  supported via the `TcxoInputOn` bit** — note this is a *bit*, not a pin function, and the TCXO is
-  powered by the host. Compare Gen 2's `SetDio3AsTcxoCtrl` (steals a DIO) and Gen 4's dedicated
-  `VTCXO` pin.
-- Over-current protection, low-battery detector (`RegLowBat`, mappable to any DIO), temperature
-  measurement.
-
----
-
-## 4. Errata — and a live interoperability trap
-
-### 4.1 SX1276/77/78 Errata Note, Revision 1, Sept 2013 **[ER76]**
-
-⚠ **Applies to silicon V1b only** — `RegVersion` at `0x42` returns `0x12`. Semtech states plainly:
-*"The devices of previous silicon revision V1a are engineering samples which do not offer full
-functionality. They should not be used in a production device."* **Read `0x42` before trusting
-anything.**
-
-| § | Issue |
-|---|---|
-| 2.1 | **Sensitivity optimisation with a 500 kHz bandwidth** |
-| 2.2 | **Frequency offset tolerance with 500 kHz bandwidth** |
-| 2.3 | **Receiver spurious reception of a LoRa signal** |
-| 2.4 | **Valid packet counter offset** |
-| 3.1 | `PayloadReady` set for 31.25 ns if the FIFO is empty (FSK) |
-| 3.2 | **Erroneous IBM data whitening/de-whitening** (FSK) |
-
-⚠ **§3.2 is the one that bites cross-vendor**: a whitening implementation that follows the IBM
-convention will not interoperate with an SX1276 that has this defect. If you are debugging an FSK
-link between an SX127x and anything else and the payload arrives as plausible garbage, start here.
-
-### 4.2 The SF6 trap, still live in 2026
-
-`DS.LR20xx` §23.8 lists *"SF6 requires additional configuration for backwards compatibility"* across
-**all four generations**, and Semtech's Gen-4 driver ships
-`lr20xx_workarounds_lora_enable_sx1276_compatibility_mode` and
-`lr20xx_workarounds_lora_freq_hop_enable_sx1276_compatibility_mode` **[DS20]**. **Thirteen years
-later, "SX1276 compatibility mode" is still a named function in current silicon's driver.** That is
-the measure of how much Gen-1 hardware is still deployed.
-
-**Intra-packet frequency hopping** is the other Gen-1 survival: present in Gen 1, absent in Gens 2
-and 3, **back in Gen 4** with an explicit SX1276-compatibility mode **[DS20]** §9.8, §23.8.
-
-### 4.3 SF5 does not exist on Gen 1
-
-**[DS20]** §23.8: *"SF5 is available starting from generation 2."* An SF5 network silently excludes
-every SX127x node.
-
----
-
-## 5. Software support
-
-| Stack | Status |
-|---|---|
-| **RadioLib** | ✅ `src/modules/SX127x` — a **separate module** from `SX126x`, with no shared base class **[RL]** |
-| **Semtech** | No standalone `sx127x_driver` repository exists on `LoRa-Net`; Gen-1 support lives inside `LoRaMac-node` (⚠ last push **2024-07-03**) |
-| **Meshtastic** | ✅ as **`RF95_RADIO`** in `LoRaRadioType` — named for the RFM95 module rather than the die |
-| **Arduino `LoRa`** (sandeepmistry) | The classic hobby library; SX127x-only. Not evaluated this pass |
-| Linux kernel | ❌ none |
-
-⚠ **Meshtastic calls it `RF95_RADIO`, not `SX1276_RADIO`.** If you are grepping a codebase for
-Gen-1 support, search both.
-
----
-
-## 6. Caveats and gaps
-
-| # | Issue |
-|---|---|
-| **G1** | ⚠ **The retained datasheet is Rev 5 (August 2016); the current revision is Rev 7.** The Rev 7 filename `DS_SX1276-7-8-9_W_APP_V7.pdf` appears in countless citations but `www.semtech.com/uploads/documents/` now **soft-404s** — HTTP 200 with 21 149 B of HTML for every path ([vendor guide §2.3](../../../vendors/semtech/README.md)). Rev 7 was **not obtained**. Differences between Rev 5 and Rev 7 are **`unresolved`** |
-| **G2** | ⚠ **The retained errata is Revision 1 (Sept 2013).** A later revision very likely exists. `unresolved` |
-| **G3** | ⚠ **Two register maps share one address space**, selected by a bit in `RegOpMode` (§2). Half-initialised drivers produce plausible nonsense |
-| **G4** | ⚠ **Errata applies to silicon V1b only.** Read `RegVersion` (`0x42`) = `0x12` before trusting it. V1a parts are engineering samples |
-| **G5** | ⚠ **+20 dBm needs ≥ 2.4 V**; only +17 dBm is guaranteed down to 1.8 V. Bites late in a single-cell discharge curve |
-| **G6** | **SX1272/73 ≠ SX1276/77/78/79** (§1). Different bands, 11 dB different sensitivity, different errata |
-| **G7** | **Module-to-die mapping unresolved.** `RFM95`/`RFM96`/`RFM98` are third-party modules; which die each carries is not established here |
-| **G8** | **Nothing measured**; no hardware in this knowledge base |
-| **G9** | **Lifecycle:** still listed, still orderable, still sold in enormous module volume. **No EOL notice was found** — but PCN/EOL enumeration was not performed |
-
----
-
-## 7. Used By
-
-**No board in this knowledge base uses an SX127x.** Every LoRa-bearing device documented here
-carries a Gen-2 [SX1262](../sx1262/README.md). This record exists for the lineage.
-
-Where you *will* meet it: `RFM95W`-class modules, the enormous installed base of first-generation
-LoRaWAN nodes and Meshtastic `RF95` boards, and any TTN deployment older than about 2019.
-
----
-
-## 8. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf` | 2 152 983 | `ec4e2fb67736b5d706e60ffb84fc0a22ca25a4eed33c58aa62e52580a59f7b2b` | **SX1276/77/78/79 Datasheet, Rev. 5, August 2016**, 132 pp |
-| `artifacts/sx1276-77-78-errata-wayback.pdf` | 173 175 | `d31cd91430b1ba04cc237e38895fd210a3a33aaa15a30077eb10d7cf79e0c010` | **SX1276/77/78 Errata Note, Revision 1, Sept 2013** |
-| `artifacts/sx1272-73-errata-wayback.pdf` | 140 550 | `a15152c7fdeb31fbebdfeb027157ed54b9badaf26a5adbc0532e67e0f2866242` | **SX1272/73 Errata Note** — kept because §1 shows the two sub-families are different silicon |
-
-**Provenance, all three.** All were recovered from the **Internet Archive**, because both of
-Semtech's own historical document stores are now unusable
-([vendor guide §5.2](../../../vendors/semtech/README.md)).
-
-| Field | Datasheet | Errata (76) | Errata (72) |
-|---|---|---|---|
-| Original URL | `www.semtech.com/uploads/documents/DS_SX1276-7-8-9_W_APP_V5.pdf` | `www.semtech.com/images/datasheet/sx1276_77_78-errata.pdf` | `www.semtech.com/images/datasheet/sx1272_73_errata.pdf` |
-| Wayback timestamp | **20180903190247** | **20150902061654** | **20150412001918** |
-| Recovery URL | `https://web.archive.org/web/20180903190247if_/https://www.semtech.com/uploads/documents/DS_SX1276-7-8-9_W_APP_V5.pdf` | `https://web.archive.org/web/20150902061654if_/http://www.semtech.com/images/datasheet/sx1276_77_78-errata.pdf` | `https://web.archive.org/web/20150412001918if_/http://www.semtech.com/images/datasheet/sx1272_73_errata.pdf` |
-| Second source | Semtech LR2021-era catalogue lists `SX1276-7-8 Errata Note` and `SX1272 Errata Note` — but behind the `blocked` Salesforce shell, so **it is a locator, not a download** | idem | idem |
-| ⚠ Note | The Wayback CDX also indexes `DS_SX1276-7-8-9_W_APP_V7.pdf`-era captures under a **different** path; **Rev 7 was not obtained** (G1) | — | — |
-| Retrieval date | 2026-09-04 | 2026-09-04 | 2026-09-04 |
-| Type validated | `%PDF`, 132 pages parsed by `pypdf` | `%PDF`; `/Title` `SX1276_77_8_ErrataNote_1.1_STD`, `/Author` `slebreton`, created 2013-09-23, `/Producer` GPL Ghostscript 9.05 | `%PDF` |
-| Licence | **`unknown`** — © Semtech Corporation | idem | idem |
-| Redistribution | **`unknown`** | idem | idem |
-| Disposition | **`repository`, unstaged** pending review | idem | idem |
-
-⚠ **The errata PDF's internal `/Title` says `1.1` while its cover page says "Revision 1 - Sept 2013".**
-Recorded as observed; not resolved.
-
----
-
-## 9. Related components
-
-- [**Semtech SX1262**](../sx1262/README.md) — **Gen 2**, and the migration that broke everything (§2)
-- [**Semtech SX1268**](../sx1268/README.md) · [**Semtech LLCC68**](../llcc68/README.md) — Gen-2 siblings
-- [**Semtech LR1121**](../lr1121/README.md) · [**LR1110 / LR1120**](../lr11x0/README.md) — **Gen 3**
-- [**Semtech LR2021**](../lr2021/README.md) — **Gen 4**, which ships an explicit *SX1276 compatibility mode* (§4.2)
-- [`guides/hardware/lora-radio-generations.md`](../../../guides/hardware/lora-radio-generations.md) · [`vendors/semtech/README.md`](../../../vendors/semtech/README.md) · [Components index](../../README.md)
-
----
-
-## 10. Sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| X-1 | SX1276/77/78/79 Datasheet | Semtech, via Internet Archive | credible mirror | datasheet | `artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf` | 2026-09-04 | **Rev. 5, August 2016**, 132 pp | §2, §3 |
-| X-2 | SX1276/77/78 Errata Note | Semtech, via Internet Archive | credible mirror | errata | `artifacts/sx1276-77-78-errata-wayback.pdf` | 2026-09-04 | **Revision 1, Sept 2013** | §4.1, G4 |
-| X-3 | SX1272/73 Errata Note | Semtech, via Internet Archive | credible mirror | errata | `artifacts/sx1272-73-errata-wayback.pdf` | 2026-09-04 | — | §1 |
-| X-4 | SX1276 product page | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-connect/sx1276` | 2026-09-04 | undated | §1 |
-| X-5 | SX1272 product page | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/lora-connect/sx1272` | 2026-09-04 | undated | §1 |
-| X-6 | `DS.LR20xx` Rev 2.1 §9.8, §23.8 | Semtech via Digi-Key | authorized mirror | datasheet | [held here](../lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) | 2026-09-04 | Rev 2.1, 13/04/26 | Gen-1 placement and the **2013** date; §4.2, §4.3 |
-| X-7 | Wayback CDX index for `semtech.com` PDFs | Internet Archive | archive | index | `web.archive.org/cdx/search/cdx?url=semtech.com/*&matchType=domain&filter=mimetype:application/pdf&limit=6000` | 2026-09-04 | captures 2011–2019 | §8 provenance; the 2013 first-capture dates supporting Gen 1 = 2013 |
-| X-8 | RadioLib `src/modules/SX127x`; Meshtastic `LoRaRadioType.h` | jgromes; Meshtastic | community | source | GitHub | 2026-09-04 | §5 |
diff --git a/components/semtech/sx1276/artifacts/sx1272-73-errata-wayback.pdf b/components/semtech/sx1276/artifacts/sx1272-73-errata-wayback.pdf
deleted file mode 100644
index b38c011..0000000
Binary files a/components/semtech/sx1276/artifacts/sx1272-73-errata-wayback.pdf and /dev/null differ
diff --git a/components/semtech/sx1276/artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf b/components/semtech/sx1276/artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf
deleted file mode 100644
index 1fa1740..0000000
Binary files a/components/semtech/sx1276/artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf and /dev/null differ
diff --git a/components/semtech/sx1276/artifacts/sx1276-77-78-errata-wayback.pdf b/components/semtech/sx1276/artifacts/sx1276-77-78-errata-wayback.pdf
deleted file mode 100644
index 4ff396f..0000000
Binary files a/components/semtech/sx1276/artifacts/sx1276-77-78-errata-wayback.pdf and /dev/null differ
diff --git a/components/sensirion/shtc3/README.md b/components/sensirion/shtc3/README.md
deleted file mode 100644
index 4151c84..0000000
--- a/components/sensirion/shtc3/README.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Sensirion SHTC3
-
-- **Category:** digital **relative-humidity and temperature sensor**, ultra-low-power, single package
-- **Manufacturer:** Sensirion AG
-- **Interface:** I²C, **fixed address `0x70`** — not configurable, which matters when planning a bus
-- **Document status:** datasheet retained; **version `unknown`** — the mirrored copy carries no revision marking this pass identified
-- **Research status:** **stub.** Datasheet held and validated; accuracy tables, timing and the command set have **not** been transcribed
-- **Retrieved:** 2026-09-01. **Nothing verified on hardware.**
-
-## What it is
-
-Sensirion's low-cost, low-power humidity/temperature part — the one that shows up on
-consumer and hobby boards where a full-accuracy SHT3x/SHT4x is not justified. It has
-a sleep mode measured in tenths of a microamp, which is why it pairs naturally with
-e-paper: both are chosen for designs that spend nearly all their time doing nothing.
-
-**Its address is fixed at `0x70`.** There is no address-select pin, so **two SHTC3s
-cannot share one I²C bus.** Worth knowing before designing one in alongside another
-`0x70` device.
-
-## What has not been done
-
-- Accuracy, repeatability and drift figures not transcribed.
-- Command set (`measure`, `sleep`, `wake-up`, `soft reset`, ID read), timing and CRC
-  scheme not documented.
-- No self-heating analysis — relevant for a sensor mounted on a board next to a
-  charging PMIC, which is exactly the situation on the board below.
-- No comparison against SHT3x / SHT4x / AHT2x alternatives.
-
-## Artifacts
-
-| File | Bytes | SHA-256 | Source | Retrieved | Version |
-|---|---|---|---|---|---|
-| [`artifacts/shtc3-datasheet-waveshare-mirror.pdf`](artifacts/shtc3-datasheet-waveshare-mirror.pdf) | 928 256 | `d315fe3d00282ece1d8901c0936f8bcbaa87b159bcd0e71f9002d1f03b57a8f1` | `https://files.waveshare.com/wiki/common/SHTC3_Datasheet.pdf` | 2026-09-01 | `unknown` |
-
-**Waveshare's mirror, not Sensirion's own copy** — labelled as such. Sensirion
-publishes this document openly and the original should be fetched and hashed against
-this one in a future pass; the same board already produced a case where
-[Waveshare's mirror was a full revision stale](../../nxp/pcf85063a/README.md).
-
-Validated by magic bytes (`%PDF-`), not by HTTP status. **Licence `unknown`.**
-Disposition: `repository`.
-
-## Used by
-
-### [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-
-Designator `U3`. Provides the board's environmental sensing — one of the features
-that distinguishes it from the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md),
-which has no environmental sensor at all.
-
-On the board's **single shared I²C bus** (GPIO41 SDA / GPIO42 SCL) alongside the
-[AXP2101](../../x-powers/axp2101/README.md) PMIC at `0x34`, the
-[PCF85063A](../../nxp/pcf85063a/README.md) RTC and the
-[QMI8658A](../../qst/qmi8658a/README.md) IMU. At `0x70` it does not collide with any
-of them.
-
-Notably, the schematic's own GPIO allocation table gives the SHTC3 **no column**,
-even though the part is fitted and the vendor documents it — a small reminder that
-the allocation table is a summary, not a census.
-
-Vendor examples: `Arduino/examples/04_I2C_SHTC3` and ESP-IDF `07_I2C_SHTC3`. Neither
-was read in this pass, so **the address above is the datasheet's fixed value rather
-than a value observed in this board's source**.
-
-An e-paper display with a temperature sensor is a useful combination beyond weather
-display: e-paper waveforms are strongly temperature-dependent, and the
-[SSD1677](../../solomon-systech/ssd1677/README.md) can select LUTs by temperature.
-Whether the board's firmware feeds SHTC3 readings to the panel driver, or relies on
-the controller's own sensing, is **not established**.
-
-## See also
-
-- [All components](../../README.md)
diff --git a/components/sensirion/shtc3/artifacts/shtc3-datasheet-waveshare-mirror.pdf b/components/sensirion/shtc3/artifacts/shtc3-datasheet-waveshare-mirror.pdf
deleted file mode 100644
index aecbdd0..0000000
Binary files a/components/sensirion/shtc3/artifacts/shtc3-datasheet-waveshare-mirror.pdf and /dev/null differ
diff --git a/components/sgmicro/sgm2578/README.md b/components/sgmicro/sgm2578/README.md
deleted file mode 100644
index da12292..0000000
--- a/components/sgmicro/sgm2578/README.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# SG Micro SGM2578 — load switch
-
-- **Category:** integrated load switch (high-side power switch with enable).
-- **Manufacturer:** **SG Micro Corp** — inferred from the `SGM` prefix, consistent with the
-  other SG Micro parts already documented in this repository
-  ([`sgm2036-3.3`](../sgm2036-3.3/README.md), [`sgm40567`](../sgm40567/README.md),
-  [`sgm6029`](../sgm6029/README.md)). **No datasheet located** in this pass.
-- **Research status:** ⚠ **Schematic-only.**
-- **Retrieved:** 2026-09-04
-
-The rear-LCD backlight power switch inside the **M5Stack Stamp-S3** module (`U2`, board rev
-v0.2). Replaced by an [Awinic AW35122FDR](../../awinic/aw35122/README.md) on the
-[Stamp-S3A](../../m5stack/stamp-s3a/README.md).
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part string | **`SGM2578`** | `Sch_M5StampS3_v0.2.pdf`, value text at (520.5, 121.4), associated with `U2` |
-| Second value string | **`WS4622C-4/TR`** | same symbol, at (528.4, 121.4)+ — an alternate/second-source part in the same Altium parameter block |
-| Balls/pins seen | `A1` (VOUT), `A2` (VIN), `B1`, `B2` (EN) | `PIU20A1`, `PIU20A2`, `PIU20B1`, `PIU20B2` |
-| Input | `VDD_3V3` | schematic |
-| Enable | `DISP_BL` = ESP32-S3 **GPIO38** (`U1` pad 43) | schematic |
-| Output | rear LCD-FPC backlight rail | schematic |
-| Decoupling | `C3` 100 nF/25 V | schematic |
-
-Current rating, on-resistance, slew control, reverse-current blocking and quiescent current are
-**unknown**. No chip-marking confirmation.
-
-**Second-source note.** Altium symbols commonly carry a `Comment` and a manufacturer-part
-parameter; here two distinct part strings render side by side. `WS4622C-4/TR` reads as a Will
-Semiconductor (WS) alternate. Which one is actually fitted on a given production unit is
-**not established** — only a teardown would settle it. This is recorded rather than resolved.
-
-## 2. Why it matters
-
-On the Stamp-S3 this switch gates **only** the rear FPC backlight rail. The WS2812B-2020 RGB
-LED (`U3`) sits on the unswitched `VDD_3V3`.
-
-On the Stamp-S3A the equivalent switch is an AW35122FDR whose output net is `BL_3V3`, and the
-RGB LED was **moved onto it**. That single net change is the whole firmware-visible difference
-between the two modules. See
-[`components/m5stack/stamp-s3a/README.md` §3](../../m5stack/stamp-s3a/README.md#3-change-1--the-rgb-led-is-no-longer-always-powered-firmware-visible).
-
-## 3. Artifacts
-
-**None.** Establishing evidence:
-[`components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.pdf`](../../m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.pdf).
-
----
-
-## Used By
-
-### M5Stack Stamp-S3 (SKU S007), board rev v0.2
-
-`U2`. → [`components/m5stack/stamp-s3/README.md`](../../m5stack/stamp-s3/README.md)
-
-### Reached from these devices
-
-- [M5Stack DinMeter (K134)](../../../devices/m5stack/dinmeter/README.md) — inside its Stamp-S3.
-  Note that the DinMeter carrier does **not** use the Stamp's rear FPC or GPIO38 at all: it
-  drives its own panel backlight from GPIO9 through its own AW35122FDR (`U6`). So on the
-  DinMeter this part is present but idle.
diff --git a/components/shenghe-microelectronics/sh8501b/README.md b/components/shenghe-microelectronics/sh8501b/README.md
deleted file mode 100644
index 505983e..0000000
--- a/components/shenghe-microelectronics/sh8501b/README.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Shenghe Microelectronics SH8501B (SH8501B0)
-
-- **Category:** AMOLED display driver IC — **240 RGB × n**, 16.7 M colours.
-- **Manufacturer:** **SHENGHE MICRO ELECTRONICS**, established from the datasheet cover.
-- **Retrieved:** 2026-09-07
-- **Sibling:** [`sh8601z`](../sh8601z/README.md)
-
-The display driver of the **LilyGO T-Display AMOLED Lite (1.47″)**, 194 × 368 — and the reason
-that board needs a level shifter.
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **SH8501B** (LilyGO's filename says `SH8501B0`) |
-| Cover page text | "CONFIDENTIAL · SHENGHE MICRO ELECTRONICS · 240 RGB x … / 16.7M color · AMOLED Display Driver IC · Datasheet · SH8501B" |
-| Local artifact | [`artifacts/sh8501b0-datasheet-lilygo-mirror.pdf`](artifacts/sh8501b0-datasheet-lilygo-mirror.pdf) — 4 412 013 B, SHA-256 `663d767850d7db71252c62f9de709cbaf278a88d25048aa168f6cb5586425b41` |
-| Mirror source | `Xinyuan-LilyGO/LilyGo-AMOLED-Series` → `datasheet/SH8501B0 DataSheet.pdf` @ `6d1dc008b94578cc34ba4a0f3b223dd808ca963f` |
-| Marked | **CONFIDENTIAL** |
-| Licence | Shenghe copyright, marked confidential; repository MIT does not cover it. **Redistribution status: `prohibited` on the face of the document** — should remain **unstaged** |
-
-## 2. The 1.8 V problem
-
-On the T-Display AMOLED Lite, every signal between the ESP32-S3 and this controller crosses an
-**RS0108YTQC20 8-bit level translator** (`U2`). The schematic's net names make it explicit:
-`AM_SPI_CSX`/`AM_SPI_CSX-1V8`, `AM_SPI_SCL`/`AM_SPI_SCL_1V8`, `AM_SPI_SD0..3`/`…_1V8`,
-`TE`/`TE_1V8`, `TP_INT`/`TP_INT_1V8`.
-
-**The panel side runs at 1.8 V.** That is not true of any other display in the family, and it
-has consequences:
-
-- Extra propagation delay and reduced maximum QSPI clock versus a direct 3.3 V link.
-- The board needs an **AXP2101 PMU** partly to generate the 1.8 V rail — which is why the Lite
-  is the only board in the family with a full PMU.
-- Panel power sequencing is more involved, and is plausibly why LilyGO's own figures give the
-  Lite a **1.1 mA** deep-sleep current against 230 µA for the 1.91″/2.41″ boards, and
-  **timer-only** wake instead of external GPIO wake.
-
-## 3. What was not verified
-
-Cover and table of contents only. **No register, timing or electrical value is transcribed.**
-Extraction method and its pitfalls: [`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md).
-
-## 4. Used by
-
-### LilyGO T-Display AMOLED Lite (1.47″)
-→ [`devices/lilygo/t-display-amoled-lite`](../../../devices/lilygo/t-display-amoled-lite/README.md)
-
-194 × 368, 450 nits. QSPI via the level shifter: `DISP_CS` GPIO4, `SCK` GPIO5,
-`DATA0..3` GPIO 7/10/11/12, `RESET` GPIO40, `TE` GPIO6. Touch is a separate
-[Chipsemi CHSC5816](../../chipsemi/chsc5816/README.md); PMU is an
-[X-Powers AXP2101](../../x-powers/axp2101/README.md).
-**Vendor states this board does not support hardware screen rotation.**
diff --git a/components/shenghe-microelectronics/sh8501b/artifacts/sh8501b0-datasheet-lilygo-mirror.pdf b/components/shenghe-microelectronics/sh8501b/artifacts/sh8501b0-datasheet-lilygo-mirror.pdf
deleted file mode 100644
index 5178870..0000000
Binary files a/components/shenghe-microelectronics/sh8501b/artifacts/sh8501b0-datasheet-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/shenghe-microelectronics/sh8601z/README.md b/components/shenghe-microelectronics/sh8601z/README.md
deleted file mode 100644
index 004222d..0000000
--- a/components/shenghe-microelectronics/sh8601z/README.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# Shenghe Microelectronics SH8601Z
-
-- **Category:** AMOLED display driver IC — **480 RGB × 480**, 16.7 M colours.
-- **Manufacturer:** **SHENGHE MICRO ELECTRONICS** — established from the datasheet's own cover
-  page and running headers.
-- **Retrieved:** 2026-09-07
-- **Sibling:** [`sh8501b`](../sh8501b/README.md), the 1.47″ part from the same maker.
-
-The display driver of the **LilyGO T-Display-S3 AMOLED 1.43″** in its `DO0143FAT01` /
-`DO0143FMST02` build variant.
-
-## 1. Why this record matters beyond one board
-
-**It settles who makes the SH86xx parts.** This repository already contains
-[`components/generic/sh8601-compatibility-driver`](../../generic/sh8601-compatibility-driver/README.md),
-written for a Waveshare board whose vendor code calls a driver `esp_lcd_sh8601` while the fitted
-controller is almost certainly a Sitronix ST77916. That record correctly concludes the *driver
-name* is not evidence of an SH8601 controller — and it could not say who would make one if it
-existed.
-
-**Now we know: SH8601Z is a real part, and it is Shenghe Microelectronics, not Sitronix.**
-The two records are complementary, not contradictory:
-
-| | This record | `generic/sh8601-compatibility-driver` |
-|---|---|---|
-| Subject | the **silicon** | the **software naming conflict** |
-| Claim | SH8601Z exists, is Shenghe's, and is fitted to a LilyGO board | `esp_lcd_sh8601` is a generic QSPI shim and its presence proves nothing about a Waveshare panel |
-| Together | a driver *named* `sh8601` may drive a real SH8601 (LilyGO 1.43″) **or** anything else with a QSPI DCS front end (Waveshare) | |
-
-## 2. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **SH8601Z** |
-| Cover page text | "SHENGHE MICRO ELECTRONICS · 480 RGB × 480 / 16.7M color · AMOLED Display Driver IC · Datasheet · SH8601Z" |
-| Local artifact | [`artifacts/sh8601z-datasheet-lilygo-mirror.pdf`](artifacts/sh8601z-datasheet-lilygo-mirror.pdf) — 4 505 031 B, SHA-256 `2831dc9730e8daeabd6eac0871080afc988ffd5725962421b7c21cf6972d7628` |
-| Mirror source | `Xinyuan-LilyGO/T-Display-S3-AMOLED-1.43-1.75` → `information/SH8601Z.pdf` @ `87aabe888eea6a7c0f95ce1991ca75fa98c2a172` |
-| Marked | **CONFIDENTIAL** on the first page |
-| Licence | Shenghe copyright, marked confidential. Repository is MIT, which does not cover it. **Redistribution status: `prohibited` on the face of the document** — should remain **unstaged** pending a decision |
-
-## 3. How the cover was read
-
-The PDF's plain text layer is offset like the family's other Chinese-vendor datasheets, but the
-`/ToUnicode` CMap route produced clean English (`SHENGHE MICRO ELECTRONICS`, `480 RGB x 480`,
-`16.7M color`, `AMOLED Display Driver IC`, `SH8601Z`) and the two routes agree. Method:
-[`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md).
-
-**Only the cover and table of contents were read.** No register, timing or electrical value is
-transcribed here.
-
-## 4. Board usage
-
-Selected at build time by `CONFIG_SCREEN_TYPE_DO0143FAT01` in
-`components/private_library/pin_config.h` @ `87aabe8`, whose comment reads:
-`DO0143FAT01 // DO0143FMST02 // 1.43 inches (SH8601 FT3168)`.
-
-The **other** 1.43″ build option (`DO0143FMST10`) uses a
-[Chipone CO5300](../../chipone/co5300/README.md) instead. One product page, two display
-controllers.
-
-Pins: QSPI `LCD_SDIO0..3` GPIO 11/13/14/15, `LCD_SCLK` 12, `LCD_CS` 10, `LCD_RST` 17,
-`LCD_EN` 16. Touch is a separate [FocalTech FT3168](../../focaltech/ft3168/README.md) on
-I²C (SDA GPIO7 / SCL GPIO6, INT GPIO9).
-
-Note the datasheet's **480 × 480** against the panel's **466 × 466** visible / **473 × 467**
-in LilyGO's header — three numbers, consistent with a 480-wide controller driving a smaller
-round panel through a window. Not confirmed.
-
-## 5. Used by
-
-### LilyGO T-Display-S3 AMOLED 1.43″ (`DO0143FAT01` variant)
-→ [`devices/lilygo/t-display-s3-amoled-1-43-1-75`](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md)
diff --git a/components/shenghe-microelectronics/sh8601z/artifacts/sh8601z-datasheet-lilygo-mirror.pdf b/components/shenghe-microelectronics/sh8601z/artifacts/sh8601z-datasheet-lilygo-mirror.pdf
deleted file mode 100644
index 6fe2577..0000000
Binary files a/components/shenghe-microelectronics/sh8601z/artifacts/sh8601z-datasheet-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/silergy/sy6970/README.md b/components/silergy/sy6970/README.md
deleted file mode 100644
index 765d8c5..0000000
--- a/components/silergy/sy6970/README.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Silergy SY6970
-
-- **Category:** I²C-controlled **switch-mode single-cell Li-ion charger** with power-path
-  management, OTG boost, integrated ADC and programmable input-current limit.
-- **Manufacturer:** Silergy Corp.
-- **Retrieved:** 2026-09-07
-- **Sibling Silergy records here:** [`sy7088`](../sy7088/README.md) ·
-  [`sy8089`](../sy8089/README.md)
-
-**LilyGO's standard PMIC for every board in the T-Display-S3 family above the entry tier** —
-the Long, the Pro, the T4-S3 and all three DS-series AMOLED boards. It is the single most
-important reason those boards handle batteries better than the base T-Display-S3, which uses a
-dumb linear charger with a soldered current-programming resistor.
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **SY6970** |
-| I²C address | **`0x6A`** on the T-Display-S3 Pro | LilyGO's own README I²C table |
-| Local artifact | [`artifacts/sy6970-datasheet-lilygo-mirror.pdf`](artifacts/sy6970-datasheet-lilygo-mirror.pdf) — 1 940 565 B, SHA-256 `95e9bf27d96376ead60e454e448fa1593621bbbe316b4cf1c21c9e585f6ac74d` |
-| Mirror sources — **three, all identical size** | `LilyGo-AMOLED-Series` → `datasheet/SY6970 Datasheet.pdf` @ `6d1dc00` · `T-Display-S3-Long` → `datasheet/SY6970 .pdf` [sic, trailing space] @ `37a7e83` · `T-Display-S3-Pro` → `datasheet/SY6970 .pdf` @ `08b8b2b` |
-| Additional documents not retrieved | `AN_SY6970.pdf` (application note, 1 940 565 B — **the same size as the datasheet**, so possibly the same file renamed) and `EVB_SY6970.pdf` (363 619 B), both in the 1.64 and 1.43-1.75 repos |
-| Licence | Silergy copyright; the mirroring repositories are variously MIT, GPL-3.0 and **no licence at all**. **Redistribution status: unknown** |
-
-**One copy retained.** All three mirror paths report 1 940 565 B, so they are almost certainly
-the same bytes; the other two URLs are recorded here rather than stored twice.
-
-**The `AN_SY6970.pdf` size coincidence is worth someone's attention** — if it is the datasheet
-under a different name, that is a LilyGO filing error worth recording; if it is a genuine
-application note that happens to be the same size, that is a remarkable coincidence. Not
-resolved here.
-
-## 2. Why it changes the board
-
-Against the base board's [TP4065-class linear charger](../../nanjing-top-power/tp4065/README.md):
-
-| | Linear charger (base T-Display-S3) | **SY6970** |
-|---|---|---|
-| Charge current | fixed by a soldered resistor | **programmable over I²C** |
-| Input current limit | none | programmable — matters on a weak USB port |
-| Battery voltage readout | a separate ADC pin and divider (GPIO4) | **read from the chip over I²C**; no GPIO consumed |
-| Charge status | one LED | full status/fault registers |
-| OTG / 5 V boost | no | **yes** — the board can *source* 5 V |
-| Efficiency | linear: dissipates (V<sub>in</sub>−V<sub>bat</sub>)×I as heat | switch-mode |
-
-That last row matters on the Long, whose vendor-stated active current reaches **90–350+ mA**.
-
-**Consequence for firmware:** on SY6970 boards there is **no `PIN_BAT_VOLT`** to read. Anyone
-porting battery code from the base T-Display-S3 will look for one and, on the Long, will find a
-`PIN_BAT_VOLT 2` define that is *wrong* — it collides with `TP_RST` and is copy-paste residue.
-Read the PMIC instead.
-
-## 3. Software
-
-| Route | Note |
-|---|---|
-| **`lewisxhe/XPowersLib`** | the driver LilyGO uses; `LilyGo-AMOLED-Series` declares **v0.2.7**. Same author as `SensorLib` |
-| Vendor examples | `examples/PMU_Example` (Pro) · `examples/PPM_Example_for_T4S3` · `examples/PPM_Example_for_191Plus` (that one is BQ25896, not SY6970) · `examples/SY6970` and `examples/SY6970_OTG` (1.64″ and 1.43/1.75″ repos) |
-| ESPHome | no first-party SY6970 component located as of 2026-09-07 |
-
-The `SY6970_OTG` example is the interesting one — it demonstrates using the board as a 5 V
-*source*, which is not possible on any TP4065 board in the family.
-
-## 4. What was not verified
-
-The datasheet was **not read**; no register address, current range or timing is transcribed
-here. The I²C address `0x6A` comes from LilyGO's README table. Note that TI's
-[BQ25896](../../texas-instruments/bq25896/README.md) — a functionally similar part used on the
-AMOLED Plus — is commonly at `0x6B`, so **do not assume the two are interchangeable at the same
-address**.
-
-## 5. Used by
-
-| Board | Designator | Role |
-|---|---|---|
-| [T-Display-S3 Long](../../../devices/lilygo/t-display-s3-long/README.md) | `U6` | sole charger/PMIC; battery voltage is read from it, not from an ADC |
-| [T-Display-S3 Pro](../../../devices/lilygo/t-display-s3-pro/README.md) | `U5` | I²C `0x6A`, sharing the bus (SDA GPIO5 / SCL GPIO6) with the CST226SE touch (`0x5A`), LTR-553ALS (`0x23`) and the camera |
-| [T4-S3](../../../devices/lilygo/t4-s3/README.md) | `U5` | with `examples/PPM_Example_for_T4S3` |
-| [T-Display-S3 AMOLED 1.64″](../../../devices/lilygo/t-display-s3-amoled-1-64/README.md) | — | vendor README names it; `examples/SY6970`, `SY6970_OTG` |
-| [T-Display-S3 AMOLED 1.43/1.75″](../../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md) | — | same examples, plus a PCF8563 RTC |
diff --git a/components/silergy/sy6970/artifacts/sy6970-datasheet-lilygo-mirror.pdf b/components/silergy/sy6970/artifacts/sy6970-datasheet-lilygo-mirror.pdf
deleted file mode 100644
index 4bf3c17..0000000
Binary files a/components/silergy/sy6970/artifacts/sy6970-datasheet-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/silergy/sy7088/README.md b/components/silergy/sy7088/README.md
deleted file mode 100644
index f9b9e6b..0000000
--- a/components/silergy/sy7088/README.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# Silergy SY7088 — synchronous step-up (boost) converter
-
-- **Category:** synchronous boost DC-DC converter with integrated switches.
-- **Manufacturer:** **Silergy Corp** — inferred from the `SY7xxx` part-number family, which is
-  Silergy's DC-DC series. **No datasheet was located** in this pass; attribution is `inferred`.
-- **Research status:** ⚠ **Schematic-only.**
-- **Retrieved:** 2026-09-04
-
-The **battery-to-5 V boost** of the M5Stack DinMeter — what powers the Grove ports and the
-Stamp module when the board is running from the Li-ion cell.
-
----
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part string | **`SY7088`** | DinMeter schematic, visible value text at (586, 214.8), associated with `U3` |
-| Pin count / names | **9**: `LX`, `LX`, `OUT`, `OUT`, `IN`, `EN`, `FB`, `GND`, `PGND` | DinMeter schematic `U3`, `PIU301`–`PIU309` |
-| Topology | synchronous boost (`LX` + `OUT` both present, no external Schottky in the loop) | pin set + fitted parts |
-| Input on this board | `VBAT_OUT` (Li-ion, ~3.0–4.24 V) | schematic net |
-| Output on this board | `+5VOUT` — Grove `J3`/`J4` pin 3 | schematic net |
-| Inductor | `L4` **1.5 µH**, 3015 package (`R12` 0 Ω in series) | schematic |
-| Feedback divider | `R16` **52.3 kΩ** / `R18` **15 kΩ** | schematic |
-| Vendor formula printed on the sheet | **`Vout = 1.2 V × (R1/R2 + 1)`** | schematic annotation at (575.4, 233.2) |
-| Output capacitance | `C18` 22 µF, `C19` 22 µF, `C16`/`C17` 10 µF | schematic |
-
-**Computed output:** 1.2 × (52.3 / 15 + 1) = **≈ 5.38 V**.
-
-M5Stack's specification calls the Grove rail "DC 5 V @ 220 mA". The schematic's own divider and
-its own printed formula give 5.38 V. Both are primary M5Stack statements and they disagree by
-~7.6 %. This is recorded as a conflict in
-[`devices/m5stack/dinmeter/gaps-and-conflicts.md`](../../../devices/m5stack/dinmeter/gaps-and-conflicts.md) §6.
-**If you are attaching a 5 V-max peripheral to a Grove port on battery power, measure the rail
-first.**
-
-## 2. What is not established
-
-No datasheet: switching frequency, current limit, efficiency, `EN` threshold, true-disconnect
-behaviour, maximum output current, thermal limits — all **unknown**. No chip-marking
-confirmation (no teardown photograph inspected).
-
-## 3. Artifacts
-
-**None.** Establishing evidence is the device schematic:
-[`devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf`](../../../devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf).
-
----
-
-## Used By
-
-### M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-`U3`. Boosts the battery path (`VBAT_OUT`, after the `Q3`/`Q6` AP40P05 power-path FETs) to
-`+5VOUT`, which supplies **both Grove ports** (`J3` PORT.A and `J4` PORT.B, pin 3 on each) and
-`C5` decoupling. On USB or DC power the same rail is present; the boost is what keeps the Grove
-5 V alive on battery.
-
-→ [`devices/m5stack/dinmeter/features/power-and-battery.md`](../../../devices/m5stack/dinmeter/features/power-and-battery.md)
-→ [`devices/m5stack/dinmeter/features/porta-portb-expansion.md`](../../../devices/m5stack/dinmeter/features/porta-portb-expansion.md)
-
-### M5Stack Cardputer v1.0, v1.1 and ADV
-
-Designator **U2** on all three. Boost from `VBAT_OUT` (through R2 0 Ω) to **`+5VOUT`**, with
-L1 **3015 1.5 µH**, input C4 22 µF / C5 1 µF, feedback divider **R4 75 kΩ / R6 22 kΩ**.
-
-The sheet prints its own formula beside the part — `Vout = 1.2 V × (R1/R2 + 1)` — giving
-**≈ 5.29 V**. **Inferred, not measured.**
-
-`+5VOUT` feeds the Grove connector's red wire, the CAP header's `5VOUT` pin (ADV only) and the
-[SY8089](../sy8089/README.md) buck that makes 3.3 V. So the entire 3.3 V domain is paid for at
-the product of two converter efficiencies — worth remembering when reading M5Stack's current
-figures.
-
-**No current limit is published for the Grove or CAP 5 V output on the ADV.** The CardputerZero's
-equivalent port is specified at **< 500 mA**; do not assume more.
-
-Records: [v1.0](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[v1.1](../../../devices/m5stack/cardputer-v1.1/README.md) ·
-[ADV](../../../devices/m5stack/cardputer-adv/README.md)
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.8.*
diff --git a/components/silergy/sy8089/README.md b/components/silergy/sy8089/README.md
deleted file mode 100644
index bab9091..0000000
--- a/components/silergy/sy8089/README.md
+++ /dev/null
@@ -1,165 +0,0 @@
-# Silergy SY8089 — 2 A synchronous step-down regulator
-
-> The **3.3 V rail** generator on every Cardputer mainboard (designator **U4**).
-> Record created **2026-09-04**. Sibling in this repository: [`silergy/sy7088`](../sy7088/README.md),
-> the boost that generates `+5VOUT` on the same boards.
-
-## Function
-
-A small synchronous buck converter in a 5-pin package: `EN`, `IN`, `LX`, `FB`, `GND`. It steps
-the board's 5 V rail down to 3.3 V for all the logic. Output voltage is set by an external
-feedback divider.
-
-## Key capabilities
-
-| Property | Value | Evidence |
-|---|---|---|
-| Topology | synchronous buck | schematic |
-| Package | 5-pin (SOT-23-5 class) | schematic symbol: `EN`, `IN`, `LX`, `FB`, `GND` |
-| Rated current | ~2 A class for this family | **not verified — no datasheet retrieved** |
-| Feedback reference | **not established** — see the arithmetic problem below | — |
-
-## Pinout as drawn
-
-| Pin | Name | Cardputer connection |
-|---|---|---|
-| 1 | `IN` | `+5VOUT` |
-| 2 | `EN` | enable network |
-| 3 | `LX` | **L2, 4.7 µH** → `+3.3V` |
-| 4 | `GND` | GND |
-| 5 | `FB` | divider (see below) |
-
-Output capacitors C10/C11 100 nF and C12 22 µF; input C8/C9.
-
-## ⚠ The feedback arithmetic does not resolve
-
-The schematic sheet prints its own formula beside the neighbouring **SY7088**:
-`Vout = 1.2 V × (R1/R2 + 1)`. Applying it to the resistors identified near the SY8089
-(**R12 68 kΩ**, **R13 15 kΩ**) gives:
-
-`1.2 × (68/15 + 1) = 6.64 V` — **not 3.3 V.**
-
-Two possible explanations, neither resolved in this pass:
-
-1. **The resistor identification is wrong.** Sheet 1 is dense and several `R` values sit close
-   together; the text-layer extraction may have associated the wrong pair with this divider.
-   R11 (100 kΩ) is also in the vicinity.
-2. **The SY8089 has a different feedback reference** than the SY7088. The printed formula is
-   annotated next to the boost, not the buck, and the two parts need not share a reference.
-
-**Recorded rather than fudged.** Do not use a computed output voltage for this rail; the rail is
-3.3 V because that is what the board runs on, and the divider values above should not be quoted
-as evidence for it until either a datasheet or a higher-resolution sheet crop settles which is
-true. See [`devices/m5stack/cardputer-adv/gaps-and-conflicts.md`](../../../devices/m5stack/cardputer-adv/gaps-and-conflicts.md) §U4.
-
-This is exactly the failure mode the skill warns about: an inferred value that *looks* like a
-finding. It is not one.
-
-## Used By
-
-- **[LilyGO T-Display-S3 family](../../../devices/lilygo/t-display-s3-shared/README.md)** — an `SY8089`-family buck appears as `U4` on the [T-Display-S3 AMOLED](../../../devices/lilygo/t-display-s3-amoled/README.md) V2.0 sheet (`SY8089A1AAC`, replacing the V1.0 board's RT9080 **LDO**), on the [T-Display-S3 Long](../../../devices/lilygo/t-display-s3-long/README.md) (`SY8089AAAC`), on the [T-Display-S3 Pro](../../../devices/lilygo/t-display-s3-pro/README.md) (`SY8089AAAC`) and on the [T4-S3](../../../devices/lilygo/t4-s3/README.md). Read from the schematic designator strings; net connectivity was not traced. The LDO→buck substitution between AMOLED V1.0 and V2.0 is one of the few concrete differences identifiable between those two concurrently sold revisions.
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-Designator **U4** on schematic sheet 1. Generates `+3.3V` from `+5VOUT` (itself the SY7088's
-boost output from the battery), with L2 4.7 µH. Powers the ES8311, TCA8418, BMI270, NS4150B,
-the display and the Stamp module's input.
-
-Note the rail topology: **battery → SY7088 boost → 5 V → SY8089 buck → 3.3 V**. Everything the
-board does is paid for at the product of two converter efficiencies. That is worth knowing when
-reading M5Stack's current figures, and it is why a Grove or CAP peripheral drawing from
-`+5VOUT` is comparatively cheap while 3.3 V logic is not.
-
-### M5Stack Cardputer v1.0 (K132) and v1.1 (K132-V11)
-
-[`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md)
-
-**Same part, same designator U4**, on the shared schematic (SHA-256 `6016c1fe…`). The Cardputer
-power train — TP4057, SY7088, SY8089, CN809J, three LP3218DT1G FETs — is **identical across all
-three generations**; only the battery topology changed (120 + 1400 mAh in a base → a single
-1750 mAh cell).
-
-## Substitutes
-
-| Part | Note |
-|---|---|
-| SY8088, SY8113, SY8009 | Silergy siblings at different current ratings and packages |
-| TPS62xxx, MP1584, RT8059 | common alternatives; **check the feedback reference**, which varies (0.6 V, 0.8 V, 1.2 V…) and changes the divider |
-| An LDO | far simpler, far worse — the whole point here is efficiency on a battery |
-
-## Gaps
-
-* **No datasheet retrieved.** Rated current, feedback reference, switching frequency, efficiency
-  curve, `EN` threshold and thermal limits are all unknown.
-* **The feedback divider identification is unresolved** (above). Settling it needs either the
-  datasheet's reference voltage or a 1:1 crop of sheet 1 around U4.
-* Manufacturer inferred from the `SY` prefix, which is Silergy's convention; not confirmed
-  against a package marking.
-
----
-
-## Update — 2026-09-07: **the feedback arithmetic resolves. The divider is `R11`/`R13`, and the reference is 0.6 V.**
-
-Appended, not substituted. The section above — *"⚠ The feedback arithmetic does not resolve"* —
-was working from a misread divider **and** from a formula belonging to a different converter.
-Both are corrected here. Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-
-Evidence: `devices/m5stack/cardputer-adv/artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf`,
-sheet 1, `Creator: Altium Designer`, traced with `pdftotext -bbox-layout`.
-
-### Error 1 — the upper resistor is `R11` (68 kΩ), not `R12`
-
-`R12` is **100 kΩ**, at `COR12` (236.50, 221.20) — roughly 460 pt away on the opposite side of
-the sheet, in an unrelated network. It is not part of this feedback divider.
-
-The `U4` feedback column is unambiguous once coordinates are read:
-
-```
-PIR1102 @ 690, 206.9   -> the +3.3V output rail (row y 203.8)
-PIR1101 @ 690, 228.9 --+
-                       |--- FB node; U4 pin 5 (FB) @ 640, 232.37
-PIR1302 @ 691, 235.6 --+
-PIR1301 @ 691, 258.2   -> GND (y 280.1)
-
-COR11 @ 697.50, 214.20   value "68KΩ"  @ 702, 222.4
-COR13 @ 698.00, 243.93   value "15KΩ"  @ 702, 251.4
-```
-
-### Error 2 — the printed formula belongs to the SY7088, not the SY8089
-
-`Vout=1.2V*(R1/R2+1)` sits at **(612.67, 157.65)**, directly beneath the **SY7088 boost `U2`**
-(symbol spans y 63–135). The SY8089 `U4` symbol is at y 192–244, about 86 pt lower. The formula
-was never annotating this part.
-
-Applied to `U2`'s own divider — `R4` 75 kΩ (@ 673, 99.2) / `R6` 22 kΩ (@ 673, 128.9) — it gives
-1.2 × (75/22 + 1) = **5.29 V**, self-consistent for the `+5VOUT` rail it feeds. That is the
-formula doing its job on the part it belongs to.
-
-### Result
-
-```
-Vout = Vfb x (R11/R13 + 1) = Vfb x (68/15 + 1) = Vfb x 5.5333
-3.3 V  =>  Vfb = 3.3 / 5.5333 = 0.596 V
-```
-
-A **0.6 V** feedback reference makes the design exact to 0.7 %. Of the two possibilities the
-section above offered, the second — *"the SY8089 has a different feedback reference than the
-SY7088"* — is correct, and the value it requires is 0.6 V.
-
-⚠ **Evidence status: `inferred`, not `primary`.** This 0.596 V is *derived from the board's own
-divider and its intended output*, not read from a datasheet. **No SY8089 datasheet is retained in
-this repository** — the "No datasheet retrieved" gap noted above is unchanged, and acquiring one
-remains the way to promote this from inferred to established. What has changed is that the
-arithmetic is no longer impossible, and the row above reading *"Feedback reference | **not
-established** — see the arithmetic problem below"* can now be read as "not established from a
-primary source; requires 0.6 V for this board to work as designed".
-
-### Practical note for anyone re-deriving an output voltage
-
-The divider is `R11` over `R13` on this board. If you change the output voltage, the relation is
-`Vout = 0.6 V × (R_upper/R_lower + 1)`. Do **not** use the 1.2 V constant printed on the same
-sheet — it is the boost converter's.
-
-Traced in full: [`devices/m5stack/cardputer-adv/schematic-netlist.md`](../../../devices/m5stack/cardputer-adv/schematic-netlist.md) §3.
diff --git a/components/sitronix/st7789p3/README.md b/components/sitronix/st7789p3/README.md
deleted file mode 100644
index 8d39770..0000000
--- a/components/sitronix/st7789p3/README.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Sitronix ST7789P3
-
-- **Category:** single-chip TFT-LCD controller/driver, ST7789 family.
-- **Manufacturer:** Sitronix Technology Corporation (Taiwan) — **inferred from the part-number
-  family**, not from a datasheet in hand.
-- **Research status:** ⚠ **No datasheet was located, from Sitronix or from any mirror.**
-  Everything below is what M5Stack states plus what is structurally implied by the board it
-  sits on. Nothing here is read from a component document.
-- **Retrieved:** 2026-09-04
-
-The display controller specified for the **M5Stack DinMeter v1.1 (K134-V11)**, replacing the
-[ST7789V2](../st7789v2/README.md) of the original DinMeter.
-
----
-
-## 1. What is actually established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part string | **`ST7789P3`** | M5Stack DinMeter v1.1 page, in **three** places: Features list ("ST7789P3 display"), Specifications row *Display Driver*, and the PinMap section heading. Retrieved 2026-09-04 |
-| Panel it drives on DinMeter v1.1 | 1.14 in, **135 × 240** | same page, *Display Resolution* row |
-| Interface | 4-wire SPI, write-only | DinMeter schematic (`FPC1`, 8-pin 0.5 mm FPC) — **unchanged** from v1.0 |
-| Pin assignment | CS G7, SCK G6, RS G4, MOSI G5, RESET G8, BL G9 | v1.1 PinMap — **identical to v1.0** |
-| Datasheet on `docs.m5stack.com` | **none.** The v1.1 page's *Datasheets* section lists BM8563, tp4057, the DC connector and the battery seat — and **no display part**. The v1.0 page did link `ST7789V2_SPEC_V1.0.pdf` | verified 2026-09-04 |
-| Mentioned in M5Stack's own v1.0↔v1.1 comparison table | **no** — that table has one row, *Main Controller* | verified 2026-09-04 |
-
-## 2. What is *not* established
-
-- **No datasheet.** Not on `sitronix.com.tw`, not mirrored by M5Stack, not found in this pass.
-- **No register map, no command set, no differences from ST7789V2/V/VW.**
-- **Not confirmed by a chip marking.** No teardown photograph of a v1.1 unit was inspected.
-  The part string rests entirely on M5Stack's product page.
-- **Whether "P3" denotes a different die, a different package, a different panel-integration
-  variant, or a second-source label is unknown.**
-
-## 3. Working assumption, and its status
-
-M5Stack changed exactly one thing in the display line — the part string — while leaving the
-resolution, the pin assignment, the FPC connector and the entire published schematic untouched,
-and did not list the display in its own comparison table. M5GFX/LovyanGFX and ESP-IDF's
-`esp_lcd_panel_st7789` continue to drive DinMeter v1.1 through the unchanged
-`board_M5DinMeter` path in M5Unified (master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`,
-2026-09-04, which has no v1.1 board enum and no ST7789P3 branch).
-
-**Therefore:** treat it as command-compatible with ST7789V2 for application purposes, including
-the +52 / +40 GRAM gap and the `INVON` inversion.
-
-**Evidence status: `inferred`.** Supported by the absence of any contrary evidence and by the
-framework's silence, which is weak positive evidence. It is *not* verified, and a driver author
-targeting register-level behaviour should not rely on it. What would settle it: an ST7789P3
-datasheet, or a teardown photograph of a v1.1 unit's FPC-side controller marking.
-
-## 4. Artifacts
-
-**None.** No document exists to retain. This absence is itself recorded in
-[`devices/m5stack/dinmeter/gaps-and-conflicts.md`](../../../devices/m5stack/dinmeter/gaps-and-conflicts.md) §4
-and in [`devices/m5stack/dinmeter-v1.1/gaps-and-conflicts.md`](../../../devices/m5stack/dinmeter-v1.1/gaps-and-conflicts.md).
-
-Searches performed and their (empty) results are logged in
-[`devices/m5stack/dinmeter/research-log.md`](../../../devices/m5stack/dinmeter/research-log.md).
-
----
-
-## Used By
-
-### M5Stack DinMeter v1.1 (SKU K134-V11)
-
-1.14 in 135 × 240 IPS panel, 8-pin 0.5 mm FPC. `SPI2_HOST`, mode 0, write-only: SCLK GPIO6,
-MOSI GPIO5, CS GPIO7, D/C GPIO4, RESET GPIO8. Backlight via GPIO9 →
-[AW35122FDR](../../awinic/aw35122/README.md) load switch. The wiring is identical to v1.0's
-ST7789V2 in every respect.
-
-→ [`devices/m5stack/dinmeter-v1.1/README.md`](../../../devices/m5stack/dinmeter-v1.1/README.md)
-→ [`devices/m5stack/dinmeter/features/display.md`](../../../devices/m5stack/dinmeter/features/display.md)
diff --git a/components/sitronix/st7789v/README.md b/components/sitronix/st7789v/README.md
deleted file mode 100644
index dd9a069..0000000
--- a/components/sitronix/st7789v/README.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# Sitronix ST7789V
-
-- **Category:** single-chip TFT-LCD controller/driver with on-chip GRAM — **240 RGB × 320 dot**,
-  262 k colours; 8/9/16/18-bit MCU parallel (Intel 8080 type I/II), 3/4-wire SPI, and RGB
-  interfaces.
-- **Manufacturer:** Sitronix Technology Corporation (Taiwan).
-- **Retrieved:** 2026-09-07
-- **Sibling records already in this repository:** [`st7789v2`](../st7789v2/README.md) ·
-  [`st7789vw`](../st7789vw/README.md) · [`st7789p3`](../st7789p3/README.md) ·
-  [`st7701s`](../st7701s/README.md) · [`st77916`](../st77916/README.md) ·
-  [`st7796s`](../st7796s/README.md)
-
-The display controller of the **LilyGO T-Display-S3** and **T-Display-S3 Touch**, driven over
-an **8-bit Intel-8080 parallel** bus — an unusual choice that is the main reason those boards
-redraw as fast as they do.
-
-> **Which ST7789 is this?** Sitronix ships ST7789V, V2, VW and P3 as distinct documents with
-> distinct part numbers. This record is for the **plain `V`**, because that is the exact string
-> on the datasheet LilyGO ships (`ST7789V_SPEC_V1.4.pdf`) inside the T-Display-S3 board
-> repository. Do **not** assume the V2 or VW register set applies unchanged; see
-> [§4](#4-do-not-substitute-the-family-members-blindly).
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **ST7789V** | filename and content of the vendor-mirrored datasheet |
-| Datasheet version | **V1.4** | filename `ST7789V_SPEC_V1.4.pdf`; **the cover page was not independently verified** — see [§5](#5-what-was-not-verified) |
-| Resolution | 240 RGB × 320 | family specification |
-| Local artifact | [`artifacts/st7789v-spec-v1.4-lilygo-mirror.pdf`](artifacts/st7789v-spec-v1.4-lilygo-mirror.pdf) — 3 198 803 B, SHA-256 `94c959b15fea4a8dc9381e4c4fa94e51037a39d990f16803a03c7c2294a9cdde` | fetched 2026-09-07 |
-| Mirror source | `Xinyuan-LilyGO/T-Display-S3` → `datasheet/ST7789V_SPEC_V1.4.pdf` @ commit `ec889e789b3cf093412689a143f7f37b42b56af7` | GitHub raw |
-| Licence | Sitronix copyright; the surrounding repository is MIT, which does not cover the PDF. **Redistribution status: unknown** | — |
-
-This is a **vendor mirror**, not Sitronix's own copy. Sitronix does not publish ST77xx
-datasheets on an open portal, so board-vendor mirrors are the normal acquisition route for the
-whole family — a pattern already recorded for the [ST77916](../st77916/README.md) and
-[ST7789V2](../st7789v2/README.md).
-
-## 2. Interface as used on the T-Display-S3
-
-| Property | Value |
-|---|---|
-| Bus | **8-bit Intel-8080** (`TFT_PARALLEL_8_BIT`) |
-| Signals | `D0..D7`, `WR`, `RD`, `DC`, `CS`, `RST` |
-| Pixel clock, vendor | **16 MHz** |
-| Pixel clock, ESPHome | 10 MHz |
-| Colour depth | RGB565 (16-bit), 2 bus cycles per pixel |
-| Inversion | **on** |
-| Colour order | vendor `TFT_eSPI` setup says **RGB**; ESPHome says **BGR** — an unresolved conflict, see the [device record](../../../devices/lilygo/t-display-s3/gaps-and-conflicts.md#g3--colour-order-rgb-or-bgr) |
-| GRAM offset | **35 columns** — the board's panel is 170 px wide in a 240-wide controller |
-
-**The 35-column offset is the single most consequential integration fact.** It appears as
-`CGRAM_OFFSET` in TFT_eSPI, `offset_width: 35` in ESPHome, and two literal `35`s in the
-`Arduino_GFX` constructor. Get it wrong and you see a shifted image with a garbage band —
-the symptom in [LilyGO issue #128](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/128).
-
-## 3. Software
-
-| Library | Support | Note |
-|---|---|---|
-| `TFT_eSPI` | `ST7789_DRIVER` + `TFT_PARALLEL_8_BIT` | needs `CGRAM_OFFSET`; configuration lives inside the library |
-| `Arduino_GFX` | `Arduino_ST7789` + `Arduino_ESP32LCD8` | offsets are constructor arguments |
-| `LovyanGFX` | `lgfx::Panel_ST7789` + `Bus_Parallel8` | |
-| ESP-IDF | `esp_lcd_new_panel_st7789()` + `esp_lcd_new_panel_io_i80()` | first-party |
-| ESPHome | `mipi_spi` model `T-DISPLAY-S3` | pins and offset built in |
-
-Guide: [`guides/hardware/parallel-8080-lcd-buses.md`](../../../guides/hardware/parallel-8080-lcd-buses.md).
-
-## 4. Do not substitute the family members blindly
-
-ST7789**V**, **V2**, **VW** and **P3** are separate Sitronix documents. The
-[`st7789v2` record](../st7789v2/README.md) in this repository documents a 2016 datasheet for a
-part M5Stack later replaced with a P3 in a mid-life revision — i.e. these parts are **not**
-drop-in equivalent in practice even for the same vendor. Treat a driver written against one as
-a starting point for another, not as a port.
-
-## 5. What was not verified
-
-- **The datasheet's cover page was not read.** The version "V1.4" is taken from LilyGO's
-  filename. The PDF's magic bytes and size were validated; its text layer was not checked
-  against a rendered heading, which the research method requires before transcribing values.
-  **No numeric value has been transcribed from it into this record** — everything above comes
-  from board-level sources — so the risk is contained, but the verification is owed.
-- Whether Sitronix's current ST7789V revision differs from V1.4.
-- The colour-order conflict.
-
-## 6. Used by
-
-### LilyGO T-Display-S3 and T-Display-S3 Touch
-
-→ [`devices/lilygo/t-display-s3`](../../../devices/lilygo/t-display-s3/README.md) ·
-[`devices/lilygo/t-display-s3-touch`](../../../devices/lilygo/t-display-s3-touch/README.md)
-
-Role: the sole display controller, bonded to a 1.9″ 170 × 320 IPS panel and driven over an
-8-bit Intel-8080 bus at 16 MHz. Backlight is separate, via an
-[AW9364DNR](../../awinic/aw9364/README.md) boost driver on GPIO38. The panel is powered from a
-rail gated by GPIO15, so **the controller is unreachable until that pin is driven high** —
-which is the board's most-reported failure mode. Pin map:
-[`pinouts-and-buses.md`](../../../devices/lilygo/t-display-s3/pinouts-and-buses.md).
diff --git a/components/sitronix/st7789v/artifacts/st7789v-spec-v1.4-lilygo-mirror.pdf b/components/sitronix/st7789v/artifacts/st7789v-spec-v1.4-lilygo-mirror.pdf
deleted file mode 100644
index 2c7053f..0000000
Binary files a/components/sitronix/st7789v/artifacts/st7789v-spec-v1.4-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/sitronix/st7789v2/README.md b/components/sitronix/st7789v2/README.md
deleted file mode 100644
index ca6ca18..0000000
--- a/components/sitronix/st7789v2/README.md
+++ /dev/null
@@ -1,120 +0,0 @@
-# Sitronix ST7789V2
-
-- **Category:** single-chip TFT-LCD controller/driver with on-chip GRAM — 240 RGB × 320 dot,
-  262 k colours, MCU parallel / SPI / RGB interfaces.
-- **Manufacturer:** Sitronix Technology Corporation (Taiwan).
-- **Retrieved:** 2026-09-04
-- **Sibling records:** [`st7789vw`](../st7789vw/README.md) (already in this repository),
-  [`st7789p3`](../st7789p3/README.md), [`st7701s`](../st7701s/README.md), [`st77916`](../st77916/README.md)
-
-The display controller of the **M5Stack DinMeter (K134)**, and of the M5Dial and several other
-M5Stack 1.14-inch products. Replaced by the ST7789P3 in DinMeter v1.1 — see
-[§ ST7789V2 vs ST7789P3](#st7789v2-vs-st7789p3).
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **ST7789V2** | vendor datasheet title page |
-| Datasheet version | **Version 1.0, 2016/11** | datasheet cover, validated against the rendered heading |
-| Copyright | © 2016 Sitronix Technology Corporation | datasheet cover |
-| GRAM | 240 RGB × 320 dots, 18-bit/pixel capable | datasheet |
-| Colour depth in use on DinMeter | 16 bpp (RGB565) | `esp-board-manager` `bits_per_pixel: 16` |
-| Panel on DinMeter | 1.14 in IPS, **135 × 240 visible** | M5Stack specification row |
-| Interface on DinMeter | 4-wire SPI, **write-only** (MISO not wired) | DinMeter schematic `FPC1`; `esp-board-manager` `miso_io_num: -1` |
-
-## 2. Board-independent facts worth knowing
-
-- **The visible window is a sub-region of the 240 × 320 GRAM.** For a 135 × 240 panel the
-  offset is **column +52, row +40**. ESP-IDF's `esp_lcd_panel_set_gap()` (or LovyanGFX's
-  `offset_x` / `offset_y`) must apply it or the image is displaced and wraps.
-  Source: `espressif/esp-board-manager` `m5stack_boards/m5stack_dinmeter/board_devices.yaml`
-  (HEAD `2beb9b22b0892b343bd555a1ebc9929a7edce8fc`, 2026-09-03) — *"The visible window is offset
-  inside the controller's 240x320 GRAM (column +52, row +40)."*
-- **Colour inversion is required** on the M5Stack panels: `invert_color: true` (i.e. `INVON`,
-  command `0x21`). Same source: *"ST7789V2 panel on M5Stack needs inversion"*. This is a panel
-  property, not a controller property — an ST7789V2 on a different glass may not need it.
-- **Driver:** ESP-IDF's built-in `esp_lcd_panel_st7789` handles it; no extra component
-  dependency. In Arduino, M5GFX/LovyanGFX's `Panel_ST7789` class.
-- SPI mode 0. The DinMeter clocks it at **40 MHz** (`pclk_hz: 40000000`, same source).
-
-## 3. ST7789V2 vs ST7789P3
-
-M5Stack changed the specified controller between DinMeter v1.0 and v1.1. What is actually
-established:
-
-| | ST7789V2 | ST7789P3 |
-|---|---|---|
-| Named on | DinMeter (K134) page: features, spec row, PinMap heading | DinMeter v1.1 page: same three places |
-| Datasheet published by M5Stack | **yes** — `ST7789V2_SPEC_V1.0.pdf`, retained here | **no** — the *Datasheets* section on the v1.1 page has no display entry at all |
-| Datasheet published by Sitronix (public) | not located in this pass | not located in this pass |
-| Pin assignment on DinMeter | CS G7, SCK G6, RS G4, MOSI G5, RESET G8, BL G9 | **identical** |
-| Resolution | 135 × 240 | **identical** |
-| Listed in the vendor's own v1.0↔v1.1 comparison table | — | **no** |
-
-**Assessment.** Both are ST7789-family SPI TFT controllers and no software difference is
-documented, expected or observed. The substitution is almost certainly a panel-supply decision
-rather than a functional one. But this is `inferred`: without an ST7789P3 datasheet the claim
-"register-compatible" cannot be verified, and it is not asserted here.
-→ [`../st7789p3/README.md`](../st7789p3/README.md)
-
-## 4. Artifacts
-
-| File | Size | SHA-256 | Version | Licence | Redistribution | Disposition |
-|---|---:|---|---|---|---|---|
-| [`artifacts/ST7789V2_SPEC_V1.0.pdf`](artifacts/ST7789V2_SPEC_V1.0.pdf) | 3 216 854 | `8937678475e20598c8deb17c3cdd41403da6317a3b6518f86144b8a609de9f46` | v1.0, 2016/11 | unknown — Sitronix copyright asserted, no redistribution grant | `unknown` | `repository` (unstaged pending review) |
-
-**Provenance.** Retrieved 2026-09-04 from M5Stack's mirror
-`https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf`
-(HTTP 200, `%PDF` magic validated, text layer parses and the cover heading matches).
-
-This is an **authorized-mirror copy**: M5Stack links it from its own product page, but Sitronix
-is the publisher. No copy on a Sitronix host was located in this pass. Filed under the
-component, not the device, per the "file by what it describes" rule — it was fetched while
-researching the DinMeter but it describes a chip.
-
----
-
-## Used By
-
-### M5Stack DinMeter (SKU K134)
-
-1.14 in 135 × 240 IPS panel on an 8-pin 0.5 mm FPC (`FPC1`, `FPC-0.5-8P`). Write-only 4-wire
-SPI on `SPI2_HOST`: SCLK GPIO6, MOSI GPIO5, CS GPIO7, D/C GPIO4, RESET GPIO8. Backlight is not
-a controller pin — GPIO9 gates an [AW35122FDR](../../awinic/aw35122/README.md) load switch
-(`U6`) that feeds the panel LED string. GRAM gap +52/+40; `INVON` required.
-
-→ [`devices/m5stack/dinmeter/features/display.md`](../../../devices/m5stack/dinmeter/features/display.md)
-→ [`devices/m5stack/dinmeter/pinouts-and-buses.md`](../../../devices/m5stack/dinmeter/pinouts-and-buses.md)
-
-### M5Stack DinMeter v1.1 — *not* this part
-
-v1.1 specifies **ST7789P3**. → [`../st7789p3/README.md`](../st7789p3/README.md)
-
-### M5Stack Cardputer v1.0, v1.1 and ADV
-
-Identical display path on all three: 1.14″, **240 × 135**, 4-wire SPI driven 3-wire by M5GFX
-(`spi_3wire = true`, `pin_miso = -1`), on `SPI3_HOST` at **40 MHz write / 16 MHz read**.
-Connected through an 8-pin 0.5 mm FPC (`FPC1`) from the front panel.
-
-`SCK` G36 · `MOSI` G35 · `DC` G34 · `CS` G37 · `RST` G33 · backlight **G38**.
-
-M5GFX panel configuration: `panel_width = 135`, `panel_height = 240`, `offset_x = 52`,
-`offset_y = 40`, `invert = true`, `readable = true`, `setRotation(1)`, backlight
-`_set_pwm_backlight(GPIO_NUM_38, 7, 256, false, 16)` — **LEDC channel 7, 256 Hz**.
-
-M5GFX identifies the panel by reading its ID on G37 and testing `(id & 0xFB) == 0x81`; that test
-is the **gate for the whole Cardputer/VAMeter/CardputerADV autodetect branch**, so a failed panel
-read means the board is not recognised at all.
-
-⚠ **G38 is not only a backlight PWM.** On Stamp-S3A boards it also enables the `BL_3V3` rail
-through an [AW35122FDR](../../awinic/aw35122/README.md), and that rail powers the
-[WS2812](../../worldsemi/ws2812/README.md). Dimming the backlight browns out the RGB LED.
-
-Records: [v1.0](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[v1.1](../../../devices/m5stack/cardputer-v1.1/README.md) ·
-[ADV](../../../devices/m5stack/cardputer-adv/README.md)
-
-*Added 2026-09-07 from `scratch/m5stack-cardputer/index-fragments.md` §3.6.*
diff --git a/components/sitronix/st7789v2/artifacts/ST7789V2_SPEC_V1.0.pdf b/components/sitronix/st7789v2/artifacts/ST7789V2_SPEC_V1.0.pdf
deleted file mode 100644
index fa2af27..0000000
Binary files a/components/sitronix/st7789v2/artifacts/ST7789V2_SPEC_V1.0.pdf and /dev/null differ
diff --git a/components/sitronix/st7796s/README.md b/components/sitronix/st7796s/README.md
deleted file mode 100644
index e8ff305..0000000
--- a/components/sitronix/st7796s/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Sitronix ST7796S
-
-- **Category:** single-chip TFT-LCD controller/driver with on-chip GRAM — **320 RGB × 480 dot**,
-  262 k colours; MCU parallel (8/9/16/18-bit), 3/4-wire SPI and RGB interfaces.
-- **Manufacturer:** Sitronix Technology Corporation (Taiwan).
-- **Retrieved:** 2026-09-07
-- **Siblings here:** [`st7789v`](../st7789v/README.md) · [`st7789v2`](../st7789v2/README.md) ·
-  [`st7789vw`](../st7789vw/README.md) · [`st7789p3`](../st7789p3/README.md) ·
-  [`st77916`](../st77916/README.md) · [`st7701s`](../st7701s/README.md)
-
-The display controller of the **LilyGO T-Display-S3 Pro** — 2.33″, 222 × 480, on plain **4-wire
-SPI**. It is the only board in the T-Display-S3 family that uses ordinary SPI for its display.
-
-## ⚠ S or U? An unresolved naming conflict
-
-Three sources, three strings:
-
-| Source | Says |
-|---|---|
-| LilyGO's `T-Display-S3-Pro` README specification table | **`ST7796U (SPI)`** |
-| The datasheet LilyGO ships in that same repository | **`ST7796S-Sitronix.pdf`** |
-| ESPHome's `mipi_spi` model | `ST7796` (unsuffixed), extended as `T-DISPLAY-S3-PRO` |
-
-**ST7796S and ST7796U are different Sitronix parts.** They share the 320 × 480 GRAM and much of
-the command set but are not documented as interchangeable. This record is filed under **`S`**
-because that is what the *primary document in the vendor's own repository* says, and a datasheet
-outranks a specification table — but the conflict is real and is **not resolved**. Anyone
-writing an init sequence from scratch should verify against the physical marking.
-
-## 1. Identity and artifact
-
-| Property | Value |
-|---|---|
-| Part | **ST7796S** (per the shipped datasheet) |
-| Local artifact | [`artifacts/st7796s-datasheet-lilygo-mirror.pdf`](artifacts/st7796s-datasheet-lilygo-mirror.pdf) — 3 557 406 B, SHA-256 `da0d7eb40cc1f3b59df0e70a602cbd729822eadad56f2e45d23460fe1ff70d47` |
-| Mirror source | `Xinyuan-LilyGO/T-Display-S3-Pro` → `datasheet/ST7796S-Sitronix.pdf` @ `08b8b2bbcb8b263131af119476403080cd30224f` |
-| Licence | Sitronix copyright. **The `T-Display-S3-Pro` repository declares no licence at all**, so redistribution status is doubly unknown |
-
-Sitronix does not publish ST77xx datasheets openly; board-vendor mirrors are the acquisition
-route, as recorded for [ST77916](../st77916/README.md) and [ST7789V2](../st7789v2/README.md).
-
-## 2. Interface on the T-Display-S3 Pro
-
-| Property | Value | Source |
-|---|---|---|
-| Bus | **4-wire SPI**, shared with the microSD card | `examples/factory/utilities.h` @ `08b8b2b` — the file's own comment reads `// SD , TFT share SPI Bus` |
-| Pins | `MISO` 8 · `MOSI` 17 · `SCK` 18 · `CS` 39 · `RST` 47 · `DC` 9 · `BL` 48 | same |
-| Panel | 222 × 480 (LilyGO also writes 480 × 222) | vendor README |
-| **GRAM offset** | **`offset_width = 49`** — a 222-px panel in a 320-wide controller | ESPHome `T-DISPLAY-S3-PRO` model |
-| Inversion | on | ESPHome `invert_colors=True` |
-
-The 49-column offset is the ST7796's analogue of the T-Display-S3's 35-column ST7789 offset, and
-it fails the same way if omitted: a shifted image with a garbage band.
-
-**Bus sharing matters.** The display and the microSD card are on one SPI bus with separate chip
-selects (`TFT_CS` 39, `SD_CS` 14). Concurrent access must be serialised, and a long SD write
-will stall display updates — a design constraint worth knowing before building a
-video-playback or logging application on this board.
-
-## 3. Backlight — and the V1.0/V1.1 trap
-
-`BOARD_TFT_BL` is GPIO48, but **the brightness scale changed between board revisions**:
-
-```c
-#ifdef USING_DISPLAY_PRO_V1
-#define BRIGHTNESS_MAX_LEVEL        255      // V1.0
-#else
-#define BRIGHTNESS_MAX_LEVEL        16       // V1.1
-#endif
-```
-— `examples/factory/utilities.h` @ `08b8b2b`, whose comment states *"The difference between
-V1.0 and V1.1 is the backlight driver."* Build for the wrong one and brightness is 16× off.
-Full detail: [board-revision-drift R6](../../../devices/lilygo/t-display-s3-shared/board-revision-drift.md#r6--t-display-s3-pro-v10-vs-v11-backlight-driver).
-
-## 4. Software
-
-`Arduino_GFX` (LilyGO's choice; the repo vendors `GFX Library for Arduino`) ·
-`TFT_eSPI` (plain SPI, so it can work, but **no vendor setup file ships**) ·
-`LovyanGFX` (`Panel_ST7796`) · ESP-IDF `esp_lcd_new_panel_st7796()` ·
-**ESPHome** `mipi_spi` model `T-DISPLAY-S3-PRO`.
-
-## 5. What was not verified
-
-Datasheet cover, register map and timing were **not read**; nothing is transcribed from it.
-The S-vs-U question is open.
-
-## 6. Used by
-
-### LilyGO T-Display-S3 Pro
-→ [`devices/lilygo/t-display-s3-pro`](../../../devices/lilygo/t-display-s3-pro/README.md)
-
-Sole display controller, 4-wire SPI shared with the microSD. Touch is a separate
-[Hynitron CST226SE](../../hynitron/cst226se/README.md) at I²C `0x5A`.
diff --git a/components/sitronix/st7796s/artifacts/st7796s-datasheet-lilygo-mirror.pdf b/components/sitronix/st7796s/artifacts/st7796s-datasheet-lilygo-mirror.pdf
deleted file mode 100644
index a6c3d46..0000000
Binary files a/components/sitronix/st7796s/artifacts/st7796s-datasheet-lilygo-mirror.pdf and /dev/null differ
diff --git a/components/solomon-systech/ssd1677/README.md b/components/solomon-systech/ssd1677/README.md
deleted file mode 100644
index 1fed1a7..0000000
--- a/components/solomon-systech/ssd1677/README.md
+++ /dev/null
@@ -1,537 +0,0 @@
-# Solomon Systech SSD1677
-
-- **Category:** active-matrix EPD (e-paper) display driver **with controller** — source/gate drivers, on-chip booster and regulators, oscillator, dual display RAM, programmable waveform engine, OTP waveform store, temperature sensing, SPI MCU interface
-- **Package:** **gold-bump die only** (COG). There is no packaged part; you buy this on waffle pack and it gets bonded to a panel.
-- **Document status:** **"Advance Information", Rev 1.0, November 2018** — the first and, as far as this pass established, only public revision.
-- **Research status:** the **full datasheet is retained** in `artifacts/` and has a valid text layer, cross-checked against rendered headings. Board-side behaviour is unusually well evidenced because M5Stack ships two independent drivers for the same panel and they disagree with each other in instructive ways.
-- **Retrieved:** 2026-09-01
-
-The controller bonded into the [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) panel on the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) and its Lite sibling.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | Stated in `artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf`, cited by the document's own section or page number | `not-tested` — vendor claim reproduced; nothing measured |
-| **[MAN]** | DKE module manual, read from rendered page images — held at [`../../dke/depg0397bbs770f3/artifacts/`](../../dke/depg0397bbs770f3/README.md) | `executed-success` for the transcription; `not-tested` for the values |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference | `inferred` |
-
-**Nothing in this record was verified on hardware.** No command, parameter or timing figure was guessed.
-
----
-
-## 1. Identity, and what the cover says plainly
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **Solomon Systech Limited** | **[DS]** cover, footer of every page |
-| Part | **`SSD1677`** | **[DS]** cover |
-| Document title, verbatim | **"960 Source x 680 Gate Red/Black/White — Active Matrix EPD Display Driver with Controller"** | **[DS]** cover |
-| Document status, verbatim | **"Advance Information"** — "This document contains information on a new product. Specifications and information herein are subject to change without notice." | **[DS]** cover |
-| Revision / date | **Rev 1.0, Nov 2018** | **[DS]** cover and every page footer |
-| Ordering parts | **`SSD1677Z`** (gold bump die, **bump face up**) and **`SSD1677Z8`** (gold bump die, **bump face down**). Both: waffle pack, die thickness **300 µm**, bump height **12 µm** | **[DS]** §3, Table 3-1 |
-| Maximum geometry | **960 source outputs · 680 gate outputs · 1 VCOM · 1 VBD** ⇒ max resolution **960 × 680** | **[DS]** §1, §5 Table 5-5 (`S[959:0]`, `G[679:0]`) |
-| Colour capability | **Red / Black / White** — two full-size RAM planes, `Mono B/W: 960×680 bits` and `Mono Red: 960×680 bits` | **[DS]** §1, §2 |
-| MCU interface | **SPI only** — 4-wire (8-bit) or 3-wire (9-bit), selected by the `BS1` pin | **[DS]** §2, §6.1 |
-| ⚠ Marking verified? | **Not applicable / no.** The die is chip-on-glass inside a bonded module. Identification rests on the DKE mechanical drawing naming `DRIVER IC: SSD1677` **[MAN]** p. 6, corroborated by M5Stack listing "SSD1677 Display Driver" in its datasheet set **[DOC]** | **[INF]** |
-
-### 1.1 Say it plainly: the part is bigger and more capable than this panel uses
-
-The title is not a description of the fitted display. Three of its claims do not apply here:
-
-| Datasheet capability | What the PaperMono panel actually uses | Evidence |
-|---|---|---|
-| **680 gate outputs** (POR default `0x01` `A[9:0] = 0x2A7` ⇒ **680 MUX**) | **480 gate lines** — the driver writes `0x01` `{0xDF, 0x01, 0x02}` ⇒ `A[9:0] = 0x1DF = 479` ⇒ `479 + 1` = **480 MUX**, and `B[2:0] = 010` ⇒ `SM = 1`, interlaced gate scan | **[DS]** §7 (`0x01`), §8.1; **[SRC]** `EDP_OTP_LUT_demo.cpp:222`, `:337`; identical in DKE's own reference program **[MAN]** p. 24 |
-| **960 source outputs** | **800 source columns** — `0x44` `{00, 00, 1F, 03}` ⇒ `XSA = 0x000`, `XEA = 0x31F = 799` | **[DS]** §8.3; **[MAN]** p. 24 |
-| **Red / Black / White** | **Monochrome.** The second RAM plane (`0x26`, nominally "RED") is repurposed as the **second bit-plane of a four-level greyscale** encoding: `white = 00, light = 10, dark = 01, black = 11` across (`0x24`, `0x26`) | **[DS]** §7 (`0x24`, `0x26`); **[SRC]** `EDP_OTP_LUT_demo.cpp:139-140` |
-
-So: **160 source channels and 200 gate channels are simply unused**, and the "Red" hardware is doing greyscale duty. None of this is unusual — a controller of this class is sold to fit a range of panels — but it means the datasheet's headline numbers must not be quoted as properties of the PaperMono display.
-
-> ⚠ **Related conflict, recorded in the panel record.** DKE's mechanical drawing states `RESOLUTION: 800gate X 480source`, which is the reverse and is provably wrong: 800 gate lines would exceed this controller's 680 gate outputs. See [DEPG0397BBS770F3 §8-C3](../../dke/depg0397bbs770f3/README.md#c3--the-mechanical-drawing-has-gate-and-source-swapped).
-
----
-
-## 2. Capabilities
-
-**[DS]** §1–§2 unless noted.
-
-| Area | Capability |
-|---|---|
-| Display RAM | **Two on-chip planes**, `960 × 680` bits each — B/W and "Red". The host does not need a framebuffer to hold the panel image |
-| Drive voltages, on-chip | Booster + regulators generate `VGH`, `VGL`, `VSH1`, `VSH2`, `VSL` and `VCOM`; all five driving rails **can alternatively be supplied externally** |
-| Gate output | **2 levels** (`VGH`, `VGL`), **max 40 Vp-p**; `VGH` 15–20 V, `VGL` = −`VGH`; **500 mV** adjustment step |
-| Source / VBD output | **4 levels** (`VSH1`, `VSS`, `VSL`, `VSH2`). `VSH1` 9–17 V (200 mV step); `VSH2` 2.4–17 V (100 mV step to 8.8 V, then 200 mV); `VSL` −9 to −17 V (500 mV step) |
-| VCOM | `DCVCOM` **−4 V to −0.1 V in 100 mV steps**; `ACVCOM` 3 levels: `VSH1+DCVCOM`, `DCVCOM`, `VSL+DCVCOM`. **Built-in VCOM sensing** (`0x28`/`0x29`), sensed value programmable into OTP (`0x2A`) |
-| Waveform engine | **40 phases** (4 phases/group × 10 groups with repeat), repeat count **1–256**, **max 255 frames per phase** |
-| OTP store | **34 waveform settings (WS)** including LUT, gate/source voltage and frame rate; **34 temperature ranges (TR)**; VCOM value; waveform version; module ID / user ID; plus embedded OTP for the initial code setting |
-| OTP programming | External **or internal** generated voltage; **read-back and built-in CRC** for WS and TR (`0x34`, `0x35`) |
-| Temperature | **Internal sensor, −25 to +50 °C, ±2 °C, 9-bit**; or **I²C single-master interface to an external sensor** |
-| Diagnostics | Low-voltage (VCI) detect; **high-voltage ready detect with looping**; **panel break diagnostic**; status read (`0x2F`) |
-| Display features | **Partial update**; black/white mono **dithering** (`0x25`); **auto write RAM for regular pattern** (`0x46`, `0x47`) |
-| MCU interface | **SPI serial peripheral, maximum 20 MHz for write** |
-| Power | Low current in operation and sleep; **deep sleep 1 µA typ** |
-| Package | **COG (gold bump die)** |
-
----
-
-## 3. MCU interface
-
-### 3.1 4-wire vs 3-wire, and how the choice is made
-
-**[DS]** §6.1.1, Table 6-1. The interface is **pin-selected by `BS1`**, not by a command:
-
-| MCU interface | `BS1` | Pins used |
-|---|---|---|
-| **4-wire SPI** | **L** (to `VSS`) | `RES#`, `CS#`, **`D/C#`**, `SCL`, `SDA` |
-| 3-wire SPI (9-bit) | H (to `VDDIO`) | `RES#`, `CS#`, `D/C#` **tied LOW**, `SCL`, `SDA` |
-
-`SDI` and `SDO` are bonded together as the single bidirectional `SDA` pad **[DS]** Table 6-1 note 2.
-
-**4-wire (8-bit)** **[DS]** §6.1.2, Table 6-2:
-
-| Function | `SCL` | `SDI` | `D/C#` | `CS#` |
-|---|---|---|---|---|
-| Write command | ↑ | command bit | **L** | L |
-| Write data | ↑ | data bit | **H** | L |
-
-`SDI` shifts into an 8-bit register on every **rising** edge, MSB first (D7 → D0). **`D/C#` must be held for the whole byte.** On read, `SDO` shifts out on every **falling** edge; the first byte after `CS#` goes low is always a command (`D/C#` low), then `D/C#` goes high for the data byte(s).
-
-**3-wire (9-bit)** **[DS]** §6.1.3, Table 6-3: identical, except a **9-bit** frame is shifted, the first bit being `D/C#` itself — `0` ⇒ the byte is a command, `1` ⇒ data. `D/C#` the pin must be tied LOW.
-
-**The PaperMono panel uses 4-wire.** The FPC's `BS` pin (pin 8) is pulled low on the module **[MAN]** p. 7–8; both M5Stack drivers configure a `dc` pin **[SRC]** `EDP_SPI.cpp:29`, `M5GFX.cpp:2109`.
-
-### 3.2 Timing — and the 2× overclock in M5GFX
-
-**[DS]** §12.1, Table 12-1. Conditions `VDDIO − VSS = 2.2–3.7 V`, `TOPR = 25 °C`, `CL = 30 pF`.
-
-| Symbol | Parameter | Min | Max | Unit |
-|---|---|---:|---:|---|
-| **`fSCL`** | **SCL frequency, write mode** | | **20** | **MHz** |
-| `tCSSU` | `CS#` low before the first rising `SCLK` | 20 | | ns |
-| `tCSHLD` | `CS#` low after the last falling `SCLK` | 20 | | ns |
-| `tCSHIGH` | `CS#` high between transfers | 100 | | ns |
-| `tSCLCYC` | SCL cycle time | 50 | | ns |
-| `tSCLHIGH` | SCL high time | 25 | | ns |
-
-The DKE module manual restates the identical table and adds the read-mode figures: **`fSCL` read mode max 2.5 MHz** **[MAN]** p. 16 — an **8× asymmetry** between write and read that is easy to miss.
-
-> ⚠ **M5GFX drives this controller at 40 MHz** (`freq_write = 40000000` **[SRC]** `M5GFX/src/M5GFX.cpp:2114`), **double the maximum stated identically by both the silicon vendor and the module vendor**. M5Stack's own recommended OTP demo uses **20 MHz** — exactly at spec **[SRC]** `EDP_SPI.cpp:33`.
->
-> This is a driver operating outside a specification, not a documentation ambiguity. Whether it misbehaves is `not-tested` here. It is a concrete, checkable mechanism behind M5Stack's warning that the M5GFX waveforms are "currently unstable" **[DOC]**, and it is the cheapest thing to change first when debugging refresh artefacts.
-
-### 3.3 Signal pins
-
-**[DS]** §5. Only the host-facing pins are listed; the panel-facing `S[959:0]`, `G[679:0]`, `VBD` and `VCOM` outputs, the analogue regulation pins and the reserved/test pads are in the datasheet's own tables.
-
-| Pin | Type | Role |
-|---|---|---|
-| `BS1` | I | Interface select (§3.1) |
-| `RES#` | I | Hardware reset, **active low**. Required to exit deep sleep |
-| `CS#` | I | Chip select, active low |
-| `D/C#` | I | Data / command |
-| `SCL` | I | Serial clock |
-| `SDA` | I/O | Serial data (`SDI` + `SDO` bonded) |
-| `BUSY` | O | **High while busy** |
-| `GDR` | O | Gate driver for the external boost NMOS |
-| `RESE` | I | Current-sense input for the boost control loop |
-| `VPP` | P | **OTP programming supply** — 7.25 / 7.5 / 7.75 V (min/typ/max) |
-| `VCI` / `VDDIO` / `VDD` | P | Logic supply / interface logic supply / core (1.8 V, regulated from `VCI`) |
-| `DP[0:33]` | I | **Reserved — connect to `VSS`** |
-| `TP1`–`TP9`, `TIN`, `TPE`, `RSV` | — | **Reserved for testing — keep open, and do not connect to each other** |
-
-The external boost network `GDR`/`RESE` requires is specified concretely by the module vendor rather than here — see [DEPG0397BBS770F3 §7.4](../../dke/depg0397bbs770f3/README.md) for the actual FET, diodes, inductor and the **2.2 Ω** sense resistor.
-
----
-
-## 4. Waveforms: OTP versus external LUT
-
-This distinction is the single most important thing in this record. It determines both image quality and whether you can destroy the panel.
-
-### 4.1 What a waveform is here
-
-A waveform lookup table is **112 bytes** **[DS]** §6.7:
-
-| Bytes | Content | Set by |
-|---|---|---|
-| 0–104 | `VS[n-XY]`, `TP[n#]`, `RP[n]`, frame rate | **`0x32`** (Write LUT register, **105 bytes**) |
-| 105 | Gate level | `0x03` |
-| 106–108 | Source level | `0x04` |
-| 109 | VCOM level | `0x2C` |
-| 110–111 | Reserved | — |
-
-"The waveform LUT of a particular temperature range **can be loaded from OTP or written by MCU**" **[DS]** §6.7. Those are the two paths.
-
-### 4.2 The OTP path
-
-**[DS]** §6.10. The embedded OTP holds **34 waveform settings (WS0–WS33)** at 112 bytes each — addresses 0–3807 — followed by **34 temperature ranges (TR0–TR33)** at 3808–3909, plus VCOM, display-mode selection, waveform version and user ID.
-
-Selection is automatic **[DS]** §6.9:
-
-1. Read the temperature as a 12-bit binary value (internal sensor via `0x18` = `0x80`, or external via I²C).
-2. Search `TR0` → `TR33` **in sequence**, applying `lower bound < sensed temperature ≤ upper bound`.
-3. **The last match wins** — the datasheet's own worked example makes this explicit: 34 °C matches both `TR6` (30–35 °C) and `TR7` (33–127.9 °C), and `WS7` is selected.
-4. The matching WS is loaded into the LUT registers.
-
-> ⚠ **Precaution, verbatim [DS] §6.9:** "Please ensure the temperature range covers whole range of application temperatures, **display will not be updated if no suitable temperature range matches the sensed temperature**."
->
-> This is a silent-failure mode: out of range, the panel simply does not refresh. Combined with the DKE module's **0 to +50 °C** operating rating and the fact that **DKE does not publish which of the 34 slots it programmed**, cold-weather behaviour of this panel is undefined in a specific way. Command **`0x2D`** reads back VCOM information, display mode and a 4-byte **waveform version** from OTP, which is the only in-system way to learn anything about what is actually programmed **[DS]** §7.
-
-Temperature range format **[DS]** §6.10.1: three bytes per TR — `temp_L[7:0]`, then `temp_H[3:0]` : `temp_L[11:8]`, then `temp_H[11:4]`.
-
-### 4.3 The external-LUT path
-
-Upload 105 bytes with `0x32`, plus `0x03` / `0x04` / `0x2C` for the gate, source and VCOM levels. This is what M5GFX does, with `lut_quality`, `lut_text`, `lut_fast` and friends held in flash **[SRC]** `M5GFX/src/lgfx/v1/panel/Panel_SSD1677.cpp`.
-
-### 4.4 ⚠ The DC-balance hazard
-
-M5Stack documents this explicitly **[DOC]**:
-
-> "pay attention to **DC balance**; otherwise, **irreversible damage may be caused to the panel**."
-
-Electrophoretic ink requires that the net charge delivered over a waveform sums to zero. A hand-tuned LUT that fails to balance will, over many refreshes, degrade the ink irreversibly — not a glitch, a destroyed display. **The OTP path cannot get this wrong**, because the balance was the panel manufacturer's responsibility when it burned the waveform. The external-LUT path moves that responsibility to whoever wrote the table.
-
-DKE reinforces the same point from the other side: its electrical characteristics "are only guaranteed under the **controller & waveform provided by DKE**" **[MAN]** p. 10 note 3.
-
-### 4.5 Which path M5Stack actually recommends, and why
-
-M5Stack's own documentation **[DOC]**:
-
-> "The e-paper driver waveforms for PaperMono in the M5GFX library are **currently unstable**. It is recommended to prioritize the e-paper manufacturer's **OTP example** below for refresh configuration to achieve better panel life and refresh stability."
-
-The mechanism is visible in the code:
-
-| | M5GFX `Panel_SSD1677` | `M5PaperMono-OTP-Demo` |
-|---|---|---|
-| Waveform source | **Custom LUTs uploaded from flash** (110 bytes each) | **Controller OTP** — `0x32` is **never issued** |
-| DC-balance owner | M5Stack's hand-tuned tables | DKE's factory waveform |
-| SPI clock | **40 MHz** (2× spec, §3.2) | **20 MHz** (at spec) |
-| Code size | Full panel driver in M5GFX | Two files, ~600 lines total |
-
-Corroboration that the warning is live rather than boilerplate, `executed-success` (branch diff): between M5GFX `master` and `develop`, `Panel_SSD1677.cpp` changed by 114 lines. **`lut_quality` was wholly replaced and the superseded version left commented out in-tree** (17 dead lines); the frame-rate row changed from `0x22 × 5` to `0xFF × 5` and all four greyscale rows differ. **`lut_text` was replaced too**, its comment rewritten from "Text: 64-frame absolute four-gray waveform for Mode 1" to "GC1 binary full-refresh waveform used by epd_text", and a new `Panel_SSD1677_4Gray::_refresh_mode1_text()` path added at `develop:src/lgfx/v1/panel/Panel_SSD1677.cpp:910-940`. A vendor actively swapping waveform tables between branches while keeping the old set commented out is consistent with an unresolved problem. `inferred` as to intent; the diff itself is `executed-success`.
-
-Compounding it: the **shipped factory firmware pins an older M5GFX commit than either branch head** (`02107b828acb3eb782fccd747863638d64c876d7` vs `develop` head `8d6e8b3e…`) **[SRC]** `M5PaperMono-UserDemo/repos.json`. So the factory device runs a **third** waveform set, and M5Stack's published refresh timings correspond to none of the three checked-out versions.
-
----
-
-## 5. Command set
-
-The full table is **[DS]** §7 (pp. 22–35) with per-command detail in §8. What follows is the subset the vendor's OTP demo actually issues, decoded against that table, with `file:line`. Every call site in the demo was enumerated — **24 in total, all accounted for** — and **none of them is `0x32`**, confirming no LUT is ever uploaded on this path.
-
-### 5.1 Initialisation
-
-| Cmd | Params written | Meaning **[DS]** | Source |
-|---|---|---|---|
-| `0x12` | — | **SWRESET.** Resets commands/parameters to their S/W-reset defaults **except `R10h` deep sleep**; **RAM is unaffected**; `BUSY` high during the operation | `EDP_OTP_LUT_demo.cpp:206` |
-| `0x18` | `{0x80}` | **Temperature Sensor Control** — `0x80` = **internal** sensor (`0x48` [POR] = external) | `:220`, `:356` |
-| `0x0C` | `{0xAE,0xC7,0xC3,0xC0,0x80}` | **Booster Soft-start Control.** The datasheet tabulates exactly two legal 5-byte values: **Level 1** `AE C7 C3 C0 40` and **Level 2** `AE C7 C3 C0 80`. This is **Level 2** — the stronger inrush setting | `:221`, `:336`; byte-identical in DKE's reference **[MAN]** p. 24 |
-| `0x01` | `{0xDF,0x01,0x02}` | **Driver Output control.** `A[9:0] = 0x1DF = 479` ⇒ **480 MUX gate lines**; `B[2] GD = 0`, `B[1] SM = 1` ⇒ interlaced scan `G0,G2,G4…G678,G1,G3…`, `B[0] TB = 0` ⇒ scan `G0→G679` | `:222`, `:337` |
-| `0x3C` | `{0x01}` | **Border Waveform Control.** `A[7:6] = 00` ⇒ VBD follows a **GS transition**; `A[1:0] = 01` ⇒ **LUT1**. (POR is `0xC0` = HiZ) | `:223`, `:355` |
-| `0x21` | `{0x00}` | **Display Update Control 1** — `A[7:4] = 0000` Red RAM normal, `A[3:0] = 0000` BW RAM normal | `:224`, and again before mono refresh at `:319` |
-| `0x1A` | `{0x5A}` | **Write to temperature register** — forces the value **90** so the OTP LUT search (§4.2) selects a specific waveform bank instead of the sensed one. **Four-grey path only** | `:357` |
-
-### 5.2 Window and cursor
-
-| Cmd | Meaning **[DS]** | Source |
-|---|---|---|
-| `0x11` | **Data Entry mode.** `A[1:0]` = increment/decrement per axis, `A[2] = AM` = which axis the counter advances. Demo uses **`0x03`** (Y inc, X inc) for mono and **`0x02`** (Y inc, X dec) for four-grey | `:162` (mono), `:340` (four-grey) |
-| `0x44` | **Set RAM X start/end.** `A[9:0] = XSA`, `B[9:0] = XEA`; POR `XEA = 0x3BF = 959` | `:164` |
-| `0x45` | **Set RAM Y start/end.** POR `YEA = 0x2A7 = 679` | `:168` |
-| `0x4E` / `0x4F` | **Set RAM X / Y address counter** | `:172`, `:175` |
-
-The POR end-addresses (`0x3BF`, `0x2A7`) are themselves the clearest statement of the controller's native geometry: **960 × 680, addressed in pixels, not bytes**.
-
-### 5.3 RAM writes
-
-| Cmd | Meaning **[DS]** |
-|---|---|
-| `0x24` | **Write RAM (Black/White).** **White pixel ⇒ 1, black pixel ⇒ 0.** Address pointers auto-advance until another command is written |
-| `0x26` | **Write RAM (RED).** RED ⇒ 1, white/black ⇒ 0. **Used here as the second greyscale bit-plane** (§1.1) |
-| `0x25` | Write RAM (Dithering) — routes data into the dithering engine. **Not used by either M5Stack driver** |
-| `0x46` / `0x47` | **Auto write RAM for regular pattern.** The datasheet's own operation flow (§9.1) opens with "Clear and fill two RAM by Command 0x46, Data 0xF7 … and Command 0x47, Data 0xF7". **Neither M5Stack nor DKE's reference program does this** — see §7-C3 |
-
-### 5.4 Refresh
-
-`0x22` (Display Update Control 2) selects the sequence; `0x20` (Master Activation) runs it. **[DS]** §7: "The Display Update Sequence Option is located at `R22h`. `BUSY` pad will output high during operation. **User should not interrupt this operation to avoid corruption of panel images.**"
-
-| Mode | `0x22` | Then | Source |
-|---|---|---|---|
-| Partial refresh | **`0xF8`** | `0x20` | `:264-266` |
-| Partial, follow-up | **`0x14`** | `0x20` | `:276-279` |
-| Monochrome full refresh | **`0xFF`** | `0x20`, preceded by `0x21 = 0x00` | `:319-321` |
-| Four-grey full refresh | **`0xD7`** | `0x20`, after `0x24` and `0x26` RAM writes | `:370-375` |
-
-Partial refresh additionally **floats the border** first — `0x3C = 0x80` with the vendor comment "Float the border during partial refresh" `:251` — versus `0x01` for full refreshes.
-
-The datasheet enumerates twelve `0x22` values **[DS]** §7: `80` (enable clock), `01` (disable clock), `C0`/`03` (enable/disable analog), `91`/`99` (load LUT with display mode 1/2), `B1`/`B9` (load temperature from I²C then LUT, mode 1/2), `C7`/`CF` (display with mode 1/2, then power down), `F7`/`FF` (load temperature ×2 then display, mode 1/2). **Of M5Stack's four values only `FF` appears.** See §7-C4.
-
-### 5.5 Deep sleep
-
-| Cmd | Params | Meaning **[DS]** §7 |
-|---|---|---|
-| `0x10` | `A[1:0]`: **`00` normal [POR]**, **`11` enter deep sleep** | "After this command initiated, the chip will enter Deep Sleep Mode, **BUSY pad will keep output high**. Remark: **To exit Deep Sleep mode, user required to send HWRESET to the driver.**" |
-
-Deep sleep is the intended resting state: **1 µA typ / 5 µA max** at `VCI`, with DC/DC off, no clock, no MCU access and — importantly — **RAM contents not retained** **[DS]** §11. `SWRESET` (`0x12`) explicitly does **not** reset `R10h`, so you cannot software-reset your way out of it **[DS]** §7.
-
-The vendor demo enters deep sleep **after every refresh** with `{0x01}` — `EDP_OTP_LUT_demo.cpp:236`. Note `0x01` is not one of the two documented values; §7-C5.
-
-### 5.6 Status and diagnostics that neither driver uses
-
-**[DS]** §7. Recorded because they are exactly the registers a robust driver should read and both vendor paths ignore:
-
-| Cmd | What it gives you |
-|---|---|
-| `0x2F` | **Status Bit Read** — `[5]` HV-ready flag, `[4]` VCI-detection flag, `[2]` busy flag, `[1:0]` chip ID [POR `01`]. `[5]`/`[4]` are invalid after reset until `0x14`/`0x15` are issued **[MAN]** p. 19 |
-| `0x14` | **HV Ready Detection** — requires `CLKEN=1` and `ANALOGEN=1`; result read via `0x2F` |
-| `0x2D` | **OTP Register Read** — VCOM information, display mode, **4-byte waveform version**. The only way to identify the programmed waveform in-system |
-| `0x2E` | **User ID Read** — 10 bytes from OTP |
-| `0x34` / `0x35` | **CRC calculation / CRC status read** over the OTP waveform data |
-| `0x28` / `0x29` | **VCOM Sense** and sense duration (`setting + 1` seconds, POR `09h` ⇒ 10 s) |
-| `0x31` | **Load WS OTP** — explicit OTP load, as opposed to loading via `0x22` |
-
-Neither M5GFX nor the OTP demo issues any of `0x2F`, `0x14`, `0x2D`, `0x2E`, `0x34` or `0x35`. Both poll the `BUSY` pin instead of the status register, which works but discards the VCI and HV-ready flags entirely. `executed-success` — the demo's full command call-list was extracted; `inferred` as to consequence.
-
----
-
-## 6. Reference operation flow
-
-**[DS]** §9.1, Figure 9-1, transcribed:
-
-```
-START
- 1. Power On            — supply VCI; wait 10 ms
- 2. Set Initial Configuration
-                        — define SPI interface; HW reset; SW reset (0x12); wait 10 ms
- 3. Send Initialization Code
-                        — clear and fill both RAMs: 0x46 data 0xF7 (RAM 0x24), 0x47 data 0xF7 (RAM 0x26)
-                        — set gate driver output: 0x01
-                        — set display RAM size: 0x11, 0x44, 0x45
-                        — set panel border: 0x3C
- 4. Load Waveform LUT   — sense temperature by int/ext TS: 0x18
-                        — load waveform LUT from OTP by 0x22, 0x20 — or by MCU
-                        — wait BUSY low
- 5. Write Image and Drive Display Panel
-                        — write image data: 0x4E, 0x4F, 0x24, 0x26
-                        — set soft-start: 0x0C
-                        — drive panel: 0x22, 0x20
-                        — wait BUSY low
- 6. Power Off           — deep sleep: 0x10; power off
-END
-```
-
-Two deviations in both real implementations:
-
-- **Step 3's RAM pre-clear (`0x46`/`0x47`) is skipped** by DKE's reference program and by M5Stack. §7-C3.
-- **Soft-start (`0x0C`) is issued in step 3, not step 5**, by both. Harmless reordering — the value is latched, not triggered. `inferred`.
-
----
-
-## 7. Caveats, errata and conflicts
-
-| # | Issue | Evidence |
-|---|---|---|
-| **C1** | **⚠ The document is "Advance Information" and eight years old.** Solomon Systech's own cover disclaims it: "information on a new product. Specifications and information herein are **subject to change without notice**." No later revision was located in this pass. Every figure here should be treated as provisional silicon documentation, not a finalised datasheet | **[DS]** cover |
-| **C2** | **⚠ M5GFX exceeds the documented SPI write clock by 2×.** 40 MHz against a 20 MHz maximum stated identically by Solomon Systech and DKE. §3.2 | **[DS]** §12.1; **[MAN]** p. 16; **[SRC]** `M5GFX.cpp:2114` vs `EDP_SPI.cpp:33` |
-| **C3** | **Neither vendor path performs the datasheet's prescribed RAM pre-clear.** §9.1 step 3 opens with `0x46`/`0x47` data `0xF7` on both RAMs. DKE's reference program **[MAN]** p. 24 does not; the M5Stack OTP demo does not; M5GFX does not. Since RAM is explicitly **not** reset by `SWRESET` and **not** retained through deep sleep, the first frame after a cold start is drawn against undefined RAM in the plane you did not write. In the mono path only `0x24` is written, so the `0x26` plane is never initialised. **Latent, not obviously active** — `0x21`'s "bypass RAM content as 0" option exists precisely to neutralise this, and the demo writes `0x21 = 0x00` (normal), so it does *not* neutralise it. Worth checking on hardware | **[DS]** §9.1, §7 (`0x12` note); **[MAN]** p. 24; **[SRC]** `EDP_OTP_LUT_demo.cpp:319` |
-| **C4** | **The `0x22` values in use are undocumented.** Datasheet lists `80 01 C0 03 91 99 B1 B9 C7 CF F7 FF`; DKE's manual lists `C7`, `90`, `47`; DKE's reference program uses `F7`; M5Stack uses `FF`, `D7`, `F8`, `14`. Only `FF` is common to the datasheet and M5Stack. The values are evidently a **bit-field** — `CF = C7 \| 0x08`, `F7 = C7 \| 0x30` — and M5GFX carries a comment confirming decomposability ("0x07 becomes 0xC7 when the analog section is off: Mode 1 refresh, followed by analog and oscillator power-down"). **But no source in hand publishes the bit definitions**, so `D7`, `F8` and `14` cannot be decoded with confidence. Copy values from a known-working sequence; do not compose your own | **[DS]** §7; **[MAN]** p. 18, p. 24; **[SRC]** `EDP_OTP_LUT_demo.cpp:264-375`, `Panel_SSD1677.cpp` |
-| **C5** | **Deep-sleep parameter `0x01` is not a documented value.** The table defines only `00` (normal) and `11` (⇒ `0x03`). **Both** DKE's reference program and M5Stack's demo write `0x01`. Two independent vendors converging on the same undocumented value more likely means loose decoding than a shared typo, but that is **`inferred`** | **[DS]** §7 (`0x10`); **[MAN]** p. 24; **[SRC]** `EDP_OTP_LUT_demo.cpp:236` |
-| **C6** | **OTP contents are unpublished and can silently prevent refresh.** How many of the 34 WS/TR slots DKE programmed, and over what span, is not disclosed by anyone. Out of range, the display simply does not update (§4.2). `0x2D` is the only in-system probe and no vendor driver calls it | **[DS]** §6.9, §6.10, §7 |
-| **C7** | **Fault and status reporting is entirely unused.** `0x2F` (HV-ready, VCI-detect, busy, chip ID), `0x14`, `0x34`/`0x35` (OTP CRC) are read by neither vendor driver. Both poll the `BUSY` pin. A VCI brown-out or a failed HV ramp therefore surfaces as a bad image rather than an error | **[SRC]**, full call-list extraction; **[DS]** §6.11, §6.12, §7 |
-| **C8** | **Page-count discrepancy in the retained file.** The PDF has **46 pages**; the document numbers itself `P n/47` in every footer. Either one page was dropped in the mirroring, or the original's numbering was off by one. Section §1 through §13 and the tables referenced above are all present and internally consistent, so no cited content is missing — but the artifact is **not byte-faithful to a 47-page original** if one existed | `executed-success` — `pdfinfo` reports `Pages: 46`; **[DS]** footers |
-| **C9** | **The mirrored file was re-processed.** Producer string is **`PDFill: Free PDF Writer and Tools`**, CreationDate **2019-01-09** — i.e. this is not Solomon Systech's own PDF export but a re-written copy, two months after the stated Nov 2018 publication. Text layer was validated against rendered headings before any value here was transcribed; no corruption found. Related to C8 | `executed-success` — `pdfinfo` metadata |
-| **C10** | **`TOPR −25 to +85 °C` is the *die* rating, not the display's.** The DKE module is rated **0 to +50 °C** operating. Quoting the controller's range for the PaperMono display over-states the envelope by 25 °C at one end and 35 °C at the other | **[DS]** §10; **[MAN]** p. 9 |
-| **C11** | **Reserved pins are not merely "don't care".** `DP[0:33]` **must be tied to `VSS`**; `TP1`–`TP9`, `TIN`, `TPE` and `RSV` must be **left open and not connected to one another**. On a COG bond this is the panel maker's problem, but it matters if you ever evaluate the bare die | **[DS]** §5, Table 5-6 |
-
----
-
-## 8. Electrical
-
-### 8.1 Absolute maximum ratings
-
-**[DS]** §10, Table 10-1.
-
-| Symbol | Parameter | Rating | Unit |
-|---|---|---|---|
-| `VCI` | Logic supply voltage | **−0.5 to +4.0** | V |
-| `VIN` | Logic input voltage | −0.5 to V<sub>DDIO</sub> + 0.5 | V |
-| `VOUT` | Logic output voltage | −0.5 to V<sub>DDIO</sub> + 0.5 | V |
-| `TOPR` | Operating temperature | **−25 to +85** | °C |
-| `TSTG` | Storage temperature | −65 to +150 | °C |
-
-Datasheet's own note: unused inputs should be tied to `VSS` or `VDDIO`; unused outputs **must be left open**; **"This device may be light sensitive. Caution should be taken to avoid exposure of this device to any light source during normal operation."** — relevant to bare-die handling.
-
-### 8.2 Supply and currents
-
-**[DS]** §2, §11, Table 11-1.
-
-| Symbol | Parameter | Condition | Min | Typ | Max | Unit |
-|---|---|---|---:|---:|---:|---|
-| `VCI` | Logic supply | | **2.2** | | **3.3** | V |
-| `VDDIO` | Interface logic supply | **connect to `VCI`** | | | | |
-| `VDD` | Core | regulated from `VCI` | | **1.8** | | V |
-| `VPP` | **OTP program voltage** | | 7.25 | **7.5** | 7.75 | V |
-| `Islp_VCI` | **Sleep mode current** | DC/DC off, no clock, no load, MCU + RAM access allowed | | **25** | 40 | µA |
-| `Idslp_VCI` | **Deep sleep current** | DC/DC off, no clock, no load, **no MCU access, RAM not retained** | | **1** | 5 | µA |
-| `Iopr_VCI` | Operating current | `VCI = 3.0 V` | | **2.0** | | mA |
-| `VGH` | Gate output | enabled via Master Activation | 19.5 | 20 | 20.5 | V |
-| `VSH1` / `VSH2` / `VSL` | Source outputs | `VGH = 20 V`, `VGL = −VGH` | 14.8 / 4.9 / −15.2 | 15 / 5 / −15 | 15.2 / 5.1 / −14.8 | V |
-| `VCOM` | | no transitions, no load | −2.2 | −2 | −1.8 | V |
-| `VGATE(p-p)` | Gate peak-to-peak | `G0~G679` | | | **40** | V |
-| `VIH` / `VIL` | Logic thresholds | | 0.8 V<sub>DDIO</sub> | | 0.2 V<sub>DDIO</sub> | V |
-
-Regulator source capability **[DS]** Table 11-2: `IVGH`/`IVGL` **1000 µA max**; `IVSH1`/`IVSH2`/`IVSL`/`IVCOM` **2000 µA max**. Note the difference between the controller's ~2 mA operating current and the **module's** 12 mA typical / 120 mA peak **[MAN]** p. 10 — the delta is the panel and the external boost network, not the die.
-
----
-
-## 9. Libraries
-
-| Option | Where | Verdict |
-|---|---|---|
-| **`M5PaperMono-OTP-Demo`** — direct SPI, OTP waveforms only | `github.com/m5stack/M5PaperMono-OTP-Demo`, MIT | ✅ **The vendor's own recommendation** for this panel, and the safe path with respect to DC balance (§4.4). Two files: `EDP_SPI.cpp` (bus + reset) and `EDP_OTP_LUT_demo.cpp` (init + three refresh modes). Small enough to read in full |
-| **M5GFX `Panel_SSD1677` / `Panel_SSD1677_4Gray`** | `github.com/m5stack/M5GFX`, MIT | ⚠ Full graphics stack, four refresh modes, LVGL-friendly — **but** uploads custom LUTs, runs the bus at 2× spec (§3.2), and its waveforms are being actively changed between branches (§4.5) |
-| Roll your own | — | The command set in §5 plus the flow in §6 is complete enough. **Use OTP waveforms.** Do not write `0x32` unless you can prove DC balance |
-
-Framework constraints imposed by the M5Stack path, not by the controller **[SRC]**: ESP-IDF **5.5.1**, target `esp32s3`, arduino-esp32 **3.3.10** as a managed component, and **octal PSRAM is mandatory** — `M5GFX.cpp:2072-2081` aborts display init with `"M5PaperMono need OPI-PSRAM enabled"` if `CONFIG_SPIRAM_MODE_OCT` is missing, leaving a working board with a dark screen and one easily-missed log line.
-
-No mainline Linux DRM driver for the SSD1677 was located in this pass. `not-tested`.
-
----
-
-## 10. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — bonded inside panel `J5`, sheet 4
-
-The SSD1677 is **not a board-level component**: it is chip-on-glass inside the [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) module and has no reference designator of its own. It is reachable only through the panel's 24-pin FPC at `J5`.
-
-| Controller signal | FPC pin | PaperMono net | Host | Evidence |
-|---|---:|---|---|---|
-| `SDA` (SDI) | 14 | `G14_SPI2_MOSI` | ESP32-S3 **GPIO14** | **[SCH]** `J5`.14; **[SRC]** `EDP_SPI.cpp:26`, `M5GFX.cpp:2106` |
-| `SCL` | 13 | `G15_SPI2_CLK` | ESP32-S3 **GPIO15** | **[SCH]** `J5`.13; **[SRC]** `EDP_SPI.cpp:27`, `M5GFX.cpp:2108` |
-| `CS#` | 12 | `G16_EINK_CS` | ESP32-S3 **GPIO16** | **[SCH]** `J5`.12; **[SRC]** `EDP_SPI.cpp:28`, `M5GFX.cpp:2085, 2123` |
-| `D/C#` | 11 | `G17_EINK_DC` | ESP32-S3 **GPIO17** | **[SCH]** `J5`.11; **[SRC]** `EDP_SPI.cpp:29`, `M5GFX.cpp:2109` |
-| `BUSY` | 9 | `G18_EINK_BUSY` | ESP32-S3 **GPIO18** | **[SCH]** `J5`.9; **[SRC]** `EDP_SPI.cpp:30`, `M5GFX.cpp:2125` |
-| `RES#` | 10 | `PYB_EINK_RST` | **[M5IOE1](../../m5stack/m5ioe1/README.md) `IO5`** — *not* an ESP32 pin | **[SCH]** `J5`.10; `M5GFX.cpp:2124` sets `cfg.pin_rst = GPIO_NUM_NC` |
-| `VDDIO`/`VCI` | 15 | `EPD_3V3_L3B` | Rail gated by **M5IOE1 `IO3`** | **[SCH]** `J5`.15; **[SRC]** `EDP_SPI.cpp:37` |
-| `GDR` / `RESE` | 2 / 3 | — | Board-side boost network | **[SCH]** `J5`.2, `J5`.3 |
-
-Integration facts specific to this board:
-
-- **The reset pin is behind the I²C expander.** Since `RES#` is the *only* way out of deep sleep (§5.5), and the OTP demo enters deep sleep after **every** refresh, **a functioning I²C bus and a functioning M5IOE1 are on the critical path for every single screen update**. That is a real coupling: an I²C fault — for instance the IP2315 charger disturbing the bus, which M5Stack documents as a live hazard — takes the display down with it.
-- **Reset timing is 50× the module vendor's.** DKE's reference specifies **200 µs** low and 200 µs high **[MAN]** p. 24; `EDP_SPI.cpp`'s `hardware_reset()` uses **10 ms** each way **[SRC]**. Generous, which is the safe direction.
-- **Geometry as configured:** 480 gate lines, 800 source columns, interlaced gate scan (`SM = 1`), driven landscape and rotated in software (`offset_rotation = 3`, `M5GFX.cpp:2126-2130`). §1.1.
-- **Frame buffers:** the OTP demo allocates `3 × 48 000` bytes in PSRAM (`MALLOC_CAP_SPIRAM`) — 100 bytes/row × 480 rows × 3 planes **[SRC]** `EDP_OTP_LUT_demo.cpp:96`.
-- **Bus:** SPI2_HOST, mode 0, half-duplex, 4092-byte chunks, DMA-capable internal staging buffer **[SRC]** `EDP_SPI.cpp:32-34, 225-257`.
-- **Neither driver reads the controller's status register**, so the VCI-detect and HV-ready flags are unused on this board (§7-C7).
-
-### [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md) — bonded inside the panel on FPC `J2` — *added 2026-09-01*
-
-**A second, independent board using this controller — from a different vendor, with a different panel supplier, at the same 3.97-inch size.** As on the PaperMono the die is chip-on-glass with no reference designator of its own, reachable only through the panel's FPC connector (`J2` here).
-
-| Controller signal | Host GPIO | Net | Evidence |
-|---|---|---|---|
-| `SCL` | GPIO11 | `EPD_SCK` | schematic **and** vendor `DEV_Config.h:49` |
-| `SDA` | GPIO12 | `EPD_DIN` | schematic **and** `DEV_Config.h:50` |
-| `CS#` | GPIO10 | `EPD_CS` | schematic **and** `DEV_Config.h:51` |
-| `D/C#` | GPIO9 | `EPD_DC` | schematic **and** `DEV_Config.h:53` |
-| `RES#` | GPIO46 | `EPD_RST` | schematic **and** `DEV_Config.h:52` |
-| `BUSY` | GPIO3 | `EPD_BUSY` | schematic **and** `DEV_Config.h:54` |
-
-- **Bus mode:** 4-wire 8-bit SPI. The panel manual documents `BSI` selecting 3-wire (9-bit) versus 4-wire, and the vendor driver defines `D_9PIN 1`.
-- **Panel:** [Waveshare 3.97inch e-Paper](../../waveshare/3.97inch-e-paper/README.md), 800 × 480, active area 86.40 × 51.84 mm, DPI 235 — **the same active area and DPI as the DKE panel above, transposed**. Whether it is the same panel is [unresolved](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws8--is-this-the-same-panel-as-the-papermonos).
-- **Power:** no board-level EPD boost. The controller's integrated DC-DC does the work; `GDR`, `RESE`, `VGH`, `VGL`, `VSH1`, `VSH2`, `VSL`, `VCOM` and `VPP` all appear on `J2`. Logic supply comes from an [AXP2101](../../x-powers/axp2101/README.md) rail, and there is **no GPIO panel-power pin** (`EPD_PWR_PIN -1`) — power gating is a PMIC operation.
-- **Driver:** Waveshare's own `EPD_3in97.cpp/.h`, which exposes `Init`, `Init_Fast`, `Init_Partial`, `Init_4GRAY` and matching `Display*` entry points including `_Base` variants (the previous-image buffer this controller needs for correct partial refresh).
-- **Not audited.** Unlike the PaperMono entry above, **no register-level read of this vendor's driver has been done** — the initialisation sequences, LUT handling and whether §4.4's DC-balance hazard is mitigated are all **unexamined**. That is the obvious next piece of work, and it is tracked as [G2](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#gaps).
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md)
-
-**Same controller, same panel, same wiring.** The Lite drops NFC and LoRa only; both product pages carry an identical display specification and both link the same "SSD1677 Display Driver" datasheet **[DOC]**. The Lite's schematic is published as a 4-sheet `PRJ` PDF rather than a 6-sheet `SCH`, so its `J5` wiring is **not** independently confirmed here.
-
-### [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md), [X4](../../../devices/xteink/x4/README.md) and [X4 Classic](../../../devices/xteink/x4-classic/README.md) — *added 2026-09-04*
-
-Three sealed consumer e-readers, all 800 × 480, all carrying this controller **as
-the boot default** — and all three of which **also ship in batches carrying an
-UltraChip [UC8179](../../ultrachip/uc8179/README.md) or
-[UC8279](../../ultrachip/uc8279/README.md) instead**, on identical wiring, with
-no external marking to distinguish them.
-
-| Signal | X4 Pro (ESP32-S3) | X4 (ESP32-C3) | X4 Classic (ESP32-S3) |
-|---|---:|---:|---:|
-| SCLK | 12 | 8 | 12 |
-| MOSI (SDA) | 11 | 10 | 11 |
-| CS | 13 | 21 | 13 |
-| DC | **18** | 4 | **14** |
-| RST | **14** | 5 | **10** |
-| BUSY | **6** | 6 | **18** |
-
-**Note the X4 Pro and X4 Classic permute DC/RST/BUSY between themselves** despite
-sharing SCLK/MOSI/CS — porting display code between the two without changing those
-three produces a panel that resets and runs waveforms but never develops an image.
-
-Clocks: X4 Pro **20 MHz** (OEM uses only 5 MHz); X4 **20 MHz** default with an
-opt-in, out-of-spec **40 MHz** mode (`-DFREEINK_X4_OVERCLOCK_SPI`) that halves
-plane-write time from ~38 ms to ~19 ms *"but can glitch plane writes on marginal
-wiring"*; X4 Classic 20 MHz.
-
-**This controller's most consequential property here is a negative one: it does
-not answer `VER (0x70)` or `FLG (0x71)`.** That silence is exactly what the
-FreeInk SDK's boot probe uses to tell an SSD1677 from its UltraChip substitutes —
-a released data line floats to a uniform `0x00`/`0xFF` on an SSD part and returns
-a driven, structured pattern on a UC81xx. See
-[`components/ultrachip/uc8179`](../../ultrachip/uc8179/README.md) §2 for the
-`CHIP_VER = 0x00` false-negative that this matcher had to be corrected for.
-
-No external EPD PMIC and no external charge pump on any of the three: the
-controller drives its high-voltage rails from its **internal booster**
-(`0x0C` soft-start). An early X4 Pro investigation wrongly concluded otherwise.
-
-Recovered OEM command streams (X4 Pro, firmware 7.4.4): FULL `0x22 = 0xF7`,
-FAST `0x22 = 0xFC`, border `0x3C = 0xC0`, master activation `0x20`, wait BUSY.
-An earlier X4 Pro image used `0xC7` for FAST — **version-scoped, do not hard-code**.
-Driver output control `0x01 = DF 01 02` → gate lines `0x01DF` = 479, MUX 480,
-`SM = 1`.
-
-→ [`devices/xteink/x4-pro/features/display.md`](../../../devices/xteink/x4-pro/features/display.md)
-→ [`devices/xteink/x4/features/display.md`](../../../devices/xteink/x4/features/display.md)
-→ [`devices/xteink/x4-pro/factory-firmware.md`](../../../devices/xteink/x4-pro/factory-firmware.md)
-
----
-
-## 11. Related components
-
-- [**DKE DEPG0397BBS770F3**](../../dke/depg0397bbs770f3/README.md) — the panel this die is bonded into. **Read that record first** for the FPC pinout, the external boost network, the optical/mechanical specification and the module's much narrower temperature rating
-- [**Waveshare 3.97inch e-Paper**](../../waveshare/3.97inch-e-paper/README.md) — *added 2026-09-01*. A second 3.97-inch panel carrying this controller, from a different vendor. Matches the DKE panel's active area to 0.01 mm and its DPI exactly; **its manual states the gate/source orientation the opposite way round** from what §1.1's register evidence establishes here, which is [unresolved](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws7--gate-versus-source-orientation)
-- [**M5Stack M5IOE1**](../../m5stack/m5ioe1/README.md) — supplies `RES#` (`IO5`) and the panel's 3V3 rail (`IO3`)
-- [**M5Stack M5PM1**](../../m5stack/m5pm1/README.md) — drives the board's frontlight; this controller has no backlight function
-- [Vendor sourcing guides index](../../../vendors/README.md) — no Solomon Systech sourcing guide exists yet. This datasheet was obtained **only** as an M5Stack product-page mirror; no Solomon Systech-hosted copy was located
-
----
-
-## 12. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf` | 3 602 487 | `daf8b726f822f6907529386b8af6fbea6ec5e8ecc7b7af361340be911d632544` | **SSD1677 datasheet, "Advance Information", Rev 1.0, Nov 2018.** PDF 1.4, A4, **46 pages** (document numbers itself `n/47` — §7-C8). Producer **`PDFill: Free PDF Writer and Tools`**, CreationDate **2019-01-09** — a re-written copy, not Solomon Systech's own export (§7-C9) |
-
-**Text-layer validation.** `pdftotext -layout` output was cross-checked against the cover block (`SOLOMON SYSTECH` / `SEMICONDUCTOR TECHNICAL DATA` / `Advance Information`), the per-page footer (`SSD1677  Rev 1.0  P n/47  Nov 2018`) and the numbered contents list before any value here was transcribed. No glyph subsetting or code-point-offset corruption was observed; extracted section headings match the table of contents exactly.
-
-**Licence.** Third-party (Solomon Systech) copyright — "Copyright © 2018 Solomon Systech Limited" — mirrored by M5Stack with no stated terms. **Redistribution status `unknown`**; disposition `repository` pending review. Unlike some vendor datasheets in this repository, this one carries **no per-page confidentiality footer**, so no strict term was observed.
-
-**Only one acquisition URL is known.** Located solely as an attachment on M5Stack's PaperMono product page, labelled "SSD1677 Display Driver". No Solomon Systech-hosted copy and no second independent mirror were found in this pass. Single-source status recorded deliberately rather than left as a silent gap; a later revision may exist behind Solomon Systech's registration wall.
-
----
-
-## 13. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | SSD1677 — 960 Source × 680 Gate Red/Black/White Active Matrix EPD Display Driver with Controller | **Solomon Systech Limited**, mirrored by M5Stack | authorized mirror | datasheet | `artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf`; upstream `static-cdn.m5stack.com/resource/docs/products/core/PaperMono/…` (linked as "SSD1677 Display Driver") | 2026-09-01 | **Rev 1.0, Nov 2018 — "Advance Information"** | §1–§8 |
-| S-2 | EPD Module User Manual — `DEPG0397BBS770F3` | DKE Holding Company Limited, mirrored by M5Stack | primary (via mirror) | module specification | [`../../dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf`](../../dke/depg0397bbs770f3/README.md) | 2026-09-01 | drawing REV A0, 2024-09-29 | §1.1, §3.2, §5, §7-C4/C5/C10 |
-| S-3 | `M5PaperMono-OTP-Demo` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-OTP-Demo` @ `c7c02554f89fd06f80d988b805b2a59050c78a46` | 2026-09-01 | 2026-08-20, MIT | §5, §9, §10 |
-| S-4 | `M5GFX` (`master` and `develop`) | M5Stack | primary | source | `github.com/m5stack/M5GFX`, `master` @ `d91077b9a607b59404e4e4a49f775c792bfae382`, `develop` @ `8d6e8b3e0e9629e0bf0702d263e9263b588b6075` | 2026-09-01 | release 0.2.28 | §3.2, §4.5, §9, §10 |
-| S-5 | `M5PaperMono-UserDemo` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-UserDemo` @ `c1099107271d31a0678d661a896e2b04dbb331ea` | 2026-09-01 | 2026-08-10, MIT | §4.5 pinned-commit divergence |
-| S-6 | PaperMono schematic | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | **V0.6.2, 2026-05-22**, 6 sheets | §10 wiring (sheet 4, `J5`) |
-| S-7 | PaperMono product page | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono` | 2026-09-01 | undated | §4.4 DC-balance warning, §4.5 OTP recommendation |
diff --git a/components/solomon-systech/ssd1677/artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf b/components/solomon-systech/ssd1677/artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf
deleted file mode 100644
index 0ebb777..0000000
Binary files a/components/solomon-systech/ssd1677/artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/stmicroelectronics/st25r3916/README.md b/components/stmicroelectronics/st25r3916/README.md
deleted file mode 100644
index 8628d37..0000000
--- a/components/stmicroelectronics/st25r3916/README.md
+++ /dev/null
@@ -1,656 +0,0 @@
-# STMicroelectronics ST25R3916
-
-> **Common guide:** [`guides/nfc`](../../../guides/nfc/README.md) — the device-independent NFC material (standards landscape, antenna matching and the Q trade-off, reader-silicon comparison, RFAL and library options, symptom-to-cause debugging). This record covers the part; that guide covers the domain.
-
-- **Category:** high-performance 13.56 MHz **NFC reader/writer + card-emulation + peer-to-peer front end**, with an integrated framing engine, a 512-byte FIFO, and both SPI and I²C host interfaces
-- **Exact part fitted on the PaperMono:** **`ST25R3916-AQWT`** — 32-pin VFQFPN 5 × 5 mm with wettable flanks, −40 °C to +105 °C grade, tape and reel
-- **Host interface on this board:** **I²C at address `0x50`** (fixed, no address-select pin). The chip also has a **full SPI mode**; the PaperMono does not use it — see [§3](#3-host-interface--i²c-here-spi-elsewhere)
-- **Protocols:** NFC-A / ISO14443A, NFC-B / ISO14443B, NFC-F / FeliCa™, NFC-V / ISO15693; EMVCo 3.0 analog and digital compliant
-- **Research status:** the **full ST datasheet is retained** (`DS12484 Rev 8`, 160 pp) and was read; the **PaperMono NFC sub-board schematic sheet was parsed pin-by-pin**. No hardware was in the loop, and no tag has been read by anyone whose report could be located.
-- **Retrieved:** 2026-09-01
-
-The NFC front end of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153), where it sits on **its own sub-board** rather than the main PCB. **The [PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) does not have it** — NFC and LoRa are the entire difference between the two SKUs.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | Stated in `artifacts/st25r3916-datasheet-m5stack-mirror.pdf` (`DS12484 Rev 8`), with section/table reference | `not-tested` — manufacturer specification reproduced; nothing measured |
-| **[SCH]** | Read out of `PaperMono_SCH_V0.6.2_20260522.pdf`, **sheet 6** (`02 Paper Mono NFC.SchDoc` rev V0.2), cited as designator + pin | `executed-success` for the extraction (PDF text-position layer parsed, all 33 `U2` pads enumerated); `not-tested` electrically |
-| **[SRC]** | Read out of M5Stack source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference drawn from two or more of the above | `inferred` |
-
-**Nothing here was verified electrically, and no register value or pin below was guessed.** Where the schematic's text layer gives only adjacency rather than connectivity, that is stated rather than upgraded to a net list — see [§5.2](#52-what-the-text-layer-can-and-cannot-establish).
-
-**Text-layer validation.** `pdftotext -layout` output from the datasheet was checked against the document's own running headers (`ST25R3916/7`), footers (`DS12484 Rev 8`, `n/160`) and section numbering before any value was transcribed. No glyph subsetting or code-point offset was observed. The schematic's hidden Altium annotation layer does render underscores as `0`, a defect documented in the [Stamp-LoRa-1262 record §5-G7](../../m5stack/stamp-lora-1262/README.md); the **visible** net labels used here are unaffected.
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **STMicroelectronics** | **[DS]** cover |
-| Marketing name | **ST25R3916** — "High performance NFC universal device and EMVCo reader" | **[DS]** cover |
-| Sibling part in the same document | **ST25R3917** — a **reduced** feature set, see §1.1 | **[DS]** Table 1 |
-| Document | **DS12484 Rev 8**, 160 pp, **08-May-2023**, "production data" | **[DS]** cover, p. 157 |
-| Order code on this board | **`ST25R3916-AQWT`** | **[SCH]** sheet 6, value string beside `U2` |
-| Decoded order code | `A` = −40 °C to +105 °C · `QW` = 32-pin **VFQFPN 5 × 5 mm, wettable flanks** · `T` = tape and reel, 4000/reel | **[DS]** §7 |
-| Other packages offered | UFQFPN32 (`QE`, non-wettable flanks), **WLCSP36** (`WL`) | **[DS]** §7, Table 2 |
-| I²C address | **`0x50`**, fixed — the datasheet states it flatly and offers no address-select mechanism | **[DS]** §4.3.4 first line; **[SRC]** `M5Unit-NFC/src/unit/unit_ST25R3916.hpp:40` (`DEFAULT_ADDRESS = 0x50`); **[SRC]** `M5PaperMono-UserDemo/main/hal/hal_board.cpp:21` |
-| Reference crystal | **27.12 MHz** (2 × f<sub>c</sub>), fast start-up | **[DS]** Features, Table 121 note 1 |
-| Crystal fitted on this board | **`XL7EL89CMI-111YLC`**, 27.12 MHz, with `C14`/`C15` **10 pF** load caps | **[SCH]** sheet 6 `X1` |
-| Reference designator on PaperMono | **`U2`, sheet 6** — the NFC sub-board, *not* the main board | **[SCH]** |
-| ⚠ Marking verified? | **No.** No teardown photograph of `U2` was inspected. The identification rests on the schematic's own value string, a primary vendor document but not a photograph of the top marking | **[INF]** |
-
-### 1.1 ST25R3916 vs ST25R3917 — the fitted part is the *full* one
-
-Both parts share one datasheet, and it is easy to attribute an ST25R3917 limitation to the wrong chip. **[DS]** Table 1:
-
-| Feature | ST25R3916 | ST25R3917 |
-|---|:--:|:--:|
-| ISO14443 A/B, ISO15693, FeliCa™, NFC tag types 1–5 read | ✅ | ✅ |
-| ISO18092 **passive initiator** | ✅ | ✅ |
-| Inductive sensor wake-up | ✅ | ✅ |
-| **ISO18092 passive target** | ✅ | ❌ |
-| **ISO18092 active initiator and target** | ✅ | ❌ |
-| **Automatic antenna tuning (AAT)** | ✅ | ❌ |
-| **Card emulation** | ✅ | ❌ |
-| **Capacitive sensor wake-up** | ✅ | ❌ |
-
-The PaperMono fits the **ST25R3916**, so card emulation, AAT, peer-to-peer and the capacitive sensor are all *silicon* capabilities of this board. Whether the *board* can use them is a separate question — see [§9-C3](#9-caveats-and-gaps) and [§10](#10-used-by).
-
-The ST25R3917 also drops four pins to `NC`, including `CSI` (pin 25) and both `AAT_A`/`AAT_B` (pins 18/19) **[DS]** Table 3. A driver written against a `3917` schematic will not exercise those.
-
----
-
-## 2. Pin table
-
-**[DS]** Table 2 (U/VFQFPN32 numbering; WLCSP36 ball in the second column). The PaperMono net column is **[SCH]** sheet 6 `U2` — all 33 pads (32 signal + thermal) were enumerated from the text-position layer.
-
-| Pin | WLCSP | Name | Type | Datasheet description | PaperMono net **[SCH]** |
-|---:|---|---|---|---|---|
-| 1 | A6 | `VDD_IO` | P | Positive supply for peripheral communication | `VCC_3V3` |
-| 2 | B6 | `CSO` | AO | Capacitive sensor output / test output 2 | *(no net label; local passive)* |
-| 3 | C5 | `VDD_D` | AO | **Digital supply regulator output** | `VDD_D` (local, decoupled) |
-| 4 | C6 | `XTO` | AO | Crystal oscillator output | `X1` |
-| 5 | D6 | `XTI` | AI/DI | Crystal oscillator input | `X1` |
-| 6 | D5 | `GND_D` | P | Digital ground | `GND` |
-| 7 | E4 | `VDD_A` | AO | **Analog supply regulator output** | `VDD_A` (local) |
-| 8 | E6 | `VDD` | P | External positive supply | `VCC_3V3` |
-| 9 | F6 | `VDD_RF` | AO | Regulated driver supply for antenna drivers | `VDD_RF` (local) |
-| 10 | E5 | `VDD_TX` | P | External positive supply for the TX part | `VCC_3V3` |
-| 11 | F5 | `VDD_AM` | AO | Regulated driver supply for AM modulation | `VDD_AM` (local) |
-| 12 | F4 | `GND_DR1` | P | Antenna driver ground | `GND` |
-| 13 | F3 | **`RFO1`** | AO | **Antenna driver output** | matching network → `ANT1` |
-| 14 | E3 | `VDD_DR` | P | Antenna driver positive supply input | local |
-| 15 | F2 | **`RFO2`** | AO | **Antenna driver output** | matching network → `ANT1` |
-| 16 | F1 | `GND_DR2` | P | Antenna driver ground | `GND` |
-| 17 | E2 | `EXT_LM` | AO | External load-modulation MOS gate driver | *(local passive)* |
-| 18 | E1 | `AAT_A` | AO | AAT tune voltage for variable capacitor A | *(see §5.3 — AAT branch appears unpopulated)* |
-| 19 | D1 | `AAT_B` | AO | AAT tune voltage for variable capacitor B | *(idem)* |
-| 20 | D2 | **`I2C_EN`** | DI | **I²C interface enable (VDD_D level)** | **`VCC_3V3` through `R4` = 0 Ω ⇒ I²C mode** |
-| 21 | C1–C3 | `VSS` | P | Ground, die substrate | `GND` |
-| 22 | B1 | `RFI1` | AI | Receiver input | `RFI_P` |
-| 23 | B2 | `RFI2` | AI | Receiver input | `RFI_N` |
-| 24 | A2 | `AGDC` | AIO | Analog reference voltage | `AGDC` (local) |
-| 25 | A1 | `CSI` | AIO | Capacitive sensor input / test output 1 | *(see §5.3)* |
-| 26 | A3, B3, B4 | `GND_A` | P | Analog ground | `GND` |
-| 27 | A4 | **`IRQ`** | DO | **Interrupt request output, active high** | **`G6_RFID_INT`** → ESP32-S3 **GPIO6** |
-| 28 | C4 | `MCU_CLK` | DO | Clock output for the MCU | *(no net label — unused)* |
-| 29 | A5 | `BSS` | DI | SPI enable (active low) | *(no net label — unused in I²C mode)* |
-| 30 | D3 | **`SCLK`** | DI | SPI clock / **I²C clock** | **`G48_SYS_SCL`** → ESP32-S3 **GPIO48** |
-| 31 | D4 | `MOSI` | DI | SPI data input | *(no net label — unused in I²C mode)* |
-| 32 | B5 | **`MISO`** | DO_T | SPI data output / **I²C data line** | **`G47_SYS_SDA`** → ESP32-S3 **GPIO47** |
-| 33 | — | thermal pad | P | Exposed pad | `GND` |
-
-> ⚠ **In I²C mode the data line is the pin called `MISO` and the clock is the pin called `SCLK`.** **[DS]** Table 12 names them `MISO (SDA)` and `SCLK (SCL)`. Reading the schematic symbol's pin *names* rather than its nets will suggest, wrongly, that the board is wired for SPI.
-
-There is **no reset pin** on this device in any package. Everything that looks like a reset on the PaperMono is really a supply gate — see [§10.2](#102-pyb_nfc_en-and-pyb_rfid_rst-are-the-same-wire-and-it-is-a-rail-enable).
-
----
-
-## 3. Host interface — I²C here, SPI elsewhere
-
-### 3.1 The interface is chosen by a strap, and this board straps it to I²C
-
-**[DS]** §4.3.2, in full:
-
-> The active communication interface is selected via the `I2C_EN` pin. If this pin is pulled to GND, the ST25R3916/7 operate in SPI mode. If this pin is pulled to `VDD_D`, the ST25R3916/7 operate in I2C mode.
-
-On the PaperMono, `I2C_EN` (pin 20) is tied to `VCC_3V3` through `R4`, a **0 Ω** resistor **[SCH]**. The schematic even carries the vendor's own note beside the symbol:
-
-> `Communication mode:` `I2C_EN=VDD; I2C mode` / `I2C_EN=GND; SPI mode`
-
-So the strap is a populated 0 Ω link, not a hard tie: **the board is convertible to SPI by depopulating `R4` and pulling pin 20 low**, but `MOSI` (31) and `BSS` (29) carry no net on this design, so SPI would also require rework at the connector — the 10-pin board-to-board link has no spare signals. `inferred`; not attempted.
-
-> Note the strap is referenced to **`VDD_D`**, the chip's *own regulator output* (pin 3), not to the board rail. Tying it to `VCC_3V3` works because `VDD_D` is a 3.0 V regulated output from a 3.3 V supply, but it is not the same node. **[DS]** Table 2, §5.4 (`VREG` typ. 3.00 V).
-
-### 3.2 I²C speeds
-
-**[DS]** §4.3.4:
-
-| Mode | Clock |
-|---|---|
-| Standard | 100 kHz |
-| **Fast** | **400 kHz** ← what the PaperMono firmware uses **[SRC]** `hal_board.cpp:22` (`NFC_I2C_FREQ_HZ = 400000`) |
-| Fast-mode Plus | 1 MHz |
-| High-speed | 3.4 MHz |
-
-`I2C configuration register 1` bits `i2c_thd<1:0>` (address `00h`, bits 5:4) select the data-hold time — `380/180/180/100 ns` in non-HS modes, `160/160/70/70 ns` in HS **[DS]** Table 19. The shared PaperMono bus runs at 400 kHz for NFC but **100 kHz for the M5PM1**, so the bus speed is re-negotiated per device on this board — see [`pinouts-and-buses.md`](../../../devices/m5stack/papermono/pinouts-and-buses.md).
-
-### 3.3 The mode byte: why the firmware "reads register `0x7F`"
-
-This is the single most confusing thing about driving this part, and it trips people who search the datasheet for a register at `0x7F` and find nothing.
-
-Every transaction — SPI or I²C — begins with a **mode/operation byte** whose top two bits select the operation and whose bottom six carry an address or command **[DS]** Table 11:
-
-| Operation | `M1 M0` | Trailer `C5..C0` | Byte |
-|---|---|---|---|
-| Register **write** | `0 0` | `A5..A0` | `0x00 \| addr` |
-| Register **read** | `0 1` | `A5..A0` | **`0x40 \| addr`** |
-| FIFO load | `1 0` | `000000` | `0x80` |
-| FIFO read | `1 0` | `011111` | `0x9F` |
-| PT_memory load (A-config / F-config / TSN) | `1 0` | `100000` / `101000` / `101100` | `0xA0` / `0xA8` / `0xAC` |
-| PT_memory read | `1 0` | `111111` | `0xBF` |
-| **Direct command** | `1 1` | `C5..C0` | `0xC0 \| cmd` |
-
-The **IC identity register is at address `3Fh`** in register space A **[DS]** §4.5.80, Table 117. Therefore:
-
-```
-read(0x3F)  ->  mode byte  0x40 | 0x3F  =  0x7F
-```
-
-which is exactly the constant in the vendor firmware:
-
-```cpp
-static constexpr std::uint8_t NFC_READ_IC_IDENTITY_CMD = 0x7F;   // hal_board.cpp:22
-static constexpr std::uint8_t NFC_VALID_IDENTITY_TYPE  = 0x05;   // hal_board.cpp:23
-```
-
-and in the driver library **[SRC]** `M5Unit-NFC/src/unit/ST25R3916_definition.hpp`:
-
-```cpp
-constexpr uint8_t REG_IC_IDENTITY{0x3F};      // :144
-constexpr uint8_t OP_READ_REGISTER{0x40};     // :215   01xxxxxxb
-constexpr uint8_t VALID_IDENTIFY_TYPE{0x05};  // :209   00000101b (ST25R3916/7)
-```
-
-`0x05` is the **`ic_type<4:0>` field**, bits 7:3 of the identity register, whose reset value the datasheet prints bit-by-bit as `0 0 1 0 1` **[DS]** Table 117. Bits 2:0 are `ic_rev<2:0>`, printed as `0 1 0`. So a full read of `3Fh` returns `0b00101_010` = `0x2A` for the documented revision, and the firmware masks off the low three bits before comparing. **Derived**, not quoted: `inferred` from two independent primary sources that agree exactly.
-
-> ⚠ **`ic_type` does not distinguish an ST25R3916 from an ST25R3917.** The datasheet gives one identity table for both, headed "ST25R3916/7", and the library's own comment says the same. An identity probe therefore proves *a member of this family is present*, not *which*.
-
-### 3.4 Register spaces, auto-increment and the space-B prefix
-
-Two register spaces, **A** and **B**, each up to 64 registers at `00h`–`3Fh` **[DS]** §4.5:
-
-- **Space A** is the default and holds everything ordinary: IO configuration (`00h`–`01h`), operation control (`02h`), mode definition (`03h`), bit rate (`04h`), protocol configuration (`05h`–`0Ah`), receiver configuration (`0Bh`–`0Eh`), timers (`0Fh`–`15h`), interrupt masks (`16h`–`19h`) and **interrupt status (`1Ah`–`1Dh`)**, FIFO status (`1Eh`–`1Fh`), antenna tuning (`26h`–`27h`), TX driver (`28h`–`29h`), external field detector thresholds (`2Ah`–`2Bh`), regulator (`2Ch`), RSSI (`2Dh`), capacitive sensor (`2Fh`–`30h`), wake-up (`32h`–`3Eh`) and **IC identity (`3Fh`)**.
-- **Space B** is sparse — EMD suppression (`05h`), subcarrier start (`06h`), P2P/correlator (`0Bh`–`0Dh`), squelch (`0Fh`), NFC field-on guard (`15h`), auxiliary modulation and TX driver timing (`28h`–`2Bh`), regulator display (`2Ch`) and **overshoot/undershoot protection (`30h`–`33h`)**.
-- Reaching space B means prefixing the transaction with **direct command `FBh`** ("Register space-B access") **[DS]** Table 13. The library encodes this as `PREFIX_SPACE_B = 0xFB << 8` **[SRC]** `ST25R3916_definition.hpp:211`.
-
-**All read and write modes auto-increment.** Send one mode byte and one address, then stream data **[DS]** §4.3.3, §4.3.4, Figures 21 and 24. Reading a non-existent register returns all-zero data rather than NACKing **[DS]** §4.3.4 — so **a zero read is not proof of a working bus**.
-
-### 3.5 Interrupts
-
-`IRQ` (pin 27) is **active high**, a push-pull digital output — not open-drain, and not shareable **[DS]** Table 2, Table 12. On this board it lands on ESP32-S3 **GPIO6**.
-
-Four interrupt status registers (`1Ah`–`1Dh`: main, timer-and-NFC, error-and-wake-up, passive-target) each have a mask register (`16h`–`19h`). Reading a status register clears it.
-
-**The PaperMono firmware never uses the line.** The scan application sets `cfg.using_irq = false` and polls **[SRC]**; GPIO6's interrupt path is therefore **unexercised by any vendor code** — see [`features/nfc.md` §7](../../../devices/m5stack/papermono/features/nfc.md).
-
----
-
-## 4. Operating modes, power states and wake-up
-
-The whole device is driven from the **Operation control register (`02h`)**, which resets to `0x00` **[DS]** Table 21:
-
-| Bit | Name | Meaning |
-|---|---|---|
-| 7 | `en` | Enables the crystal oscillator and regulators → **Ready mode**. FIFO and PT_memory become accessible |
-| 6 | `rx_en` | Enables the receiver |
-| 5 | `rx_chn` | 0 = both AM and PM channels; 1 = one channel |
-| 4 | `rx_man` | 0 = automatic channel selection; 1 = manual (via `ch_sel`) |
-| 3 | `tx_en` | Enables the transmitter. **Set automatically by the NFC field-on commands** and cleared after an active-mode transmission |
-| 2 | `wu` | Enables **Wake-up mode** — periodic low-power card-presence measurement |
-| 1:0 | `en_fd_c<1:0>` | External field detector: off / manual collision-avoidance threshold / manual peer threshold / automatic |
-
-Modes, cheapest first **[DS]** §4.2, Table 121:
-
-| Mode | How you get there | Typical I<sub>DD</sub> at 25 °C |
-|---|---|---|
-| **Power-down** | all bits 0 (the reset state). SPI/I²C still works, registers still configurable; FIFO and PT_memory do not | **0.8 µA** (max 2.5 µA) |
-| Low-power initial NFC target | `en_fd_c ≠ 0`, everything else 0 | **3.5 µA** |
-| **Wake-up** | `wu = 1`, everything else 0 | **3.0 µA** |
-| Ready | `en = 1` | **4.5 mA** |
-| All active (RX + TX) | `en`, `rx_en`, `tx_en` | **16 mA** (17 mA with AM modulation) |
-| All active, single RX channel | + `rx_chn` | **11 mA** |
-| Capacitive sensor | during a measurement | 1.1 mA |
-
-The **0.8 µA power-down figure is why this part can sit on a permanently-powered rail** in a battery device. The PaperMono does not take that option — it cuts the supply entirely instead ([§10](#10-used-by)) — and the sub-board schematic itself annotates the number:
-
-> `Supply current in Power-down mode: I = 2.5uA / When Operation control register( en=0 )` **[SCH]** sheet 6
-
-which is the datasheet's **maximum** at ≤25 °C, not its typical. At 85 °C the typical is 2 µA and the maximum **20 µA**; at 125 °C, 12 µA typical and **60 µA** maximum **[DS]** Table 121. A power budget built on "2.5 µA" will be wrong by an order of magnitude in a warm enclosure. **[INF]**
-
-### 4.1 Wake-up mode is the interesting one, and nothing on this board uses it
-
-`wu = 1` runs a low-power RC oscillator and a register-configurable wake-up timer (`32h`), taking periodic measurements and raising an interrupt only when the result departs from a stored reference **[DS]** §4.2, §4.2.5. Three independent triggers exist:
-
-- **Amplitude** measurement (`33h`–`36h`)
-- **Phase** measurement (`37h`–`3Ah`)
-- **Capacitance** — the capacitive sensor (`3Bh`–`3Eh`), ST25R3916-only
-
-This is the mechanism that lets an NFC reader detect a card without switching the field on. **No vendor code on the PaperMono touches it**, and the board's own wake path for NFC is unproven — the schematic's sheet-1 block diagram lists NFC as an L2 wake source, but no firmware exercises it ([`features/nfc.md` §9](../../../devices/m5stack/papermono/features/nfc.md)). Recorded as an open lead, not a capability.
-
-### 4.2 Power-on sequence — one undocumented-looking write that is mandatory
-
-**[DS]** §4.1, quoted because it is easy to skip and it is not optional:
-
-> To prevent the internal overheat protection to trigger below the junction temperature, the 3-byte frame `FCh / 04h / 10h` (register access / address / value) has to be sent after power-on and `Set default` command.
-
-`FCh` is the **Test access** direct command **[DS]** Table 13, §4.4.17 — so this is a write into the *test* register space, and it looks like a magic number because it is one. Then:
-
-1. Configure **IO configuration register 1 and 2** (`00h`, `01h`).
-2. Configure the internal voltage regulators — the datasheet recommends the **`Adjust regulators` (`D6h`)** direct command "to improve the system PSRR".
-3. If AAT is used, run the tuning procedure.
-
-The library carries `CMD_TEST_ACCESS{0xFC}` **[SRC]** `ST25R3916_definition.hpp:205`, so the path exists in the driver; whether `M5Unit-NFC` actually issues the overheat-protection frame was **not traced in this pass** and is recorded as an open question ([§9-C6](#9-caveats-and-gaps)).
-
-### 4.3 Direct commands worth knowing
-
-**[DS]** Table 13, encoded as `0xC0 | cmd` in the mode byte:
-
-| Code | Command | Note |
-|---|---|---|
-| `C0`/`C1` | **Set default** | Returns every register to its power-up state. The `FCh/04h/10h` frame must be re-sent afterwards (§4.2) |
-| `C2`/`C3` | Stop all activities | Transmission, reception, running direct commands and timers |
-| `C4` / `C5` | Transmit **with** / **without** CRC | |
-| `C6` / `C7` | Transmit `REQA` / `WUPA` | ISO14443A only |
-| `C8` / `C9` | **NFC initial / response field ON** | Performs RF collision avoidance, then switches the field on. Both raise an interrupt on completion |
-| `CD` / `CE` | Go to sense (Idle) / sleep (Halt) | Passive-target logic |
-| `D0` / `D1` | Mask / unmask receive data | |
-| `D3` | **Measure amplitude** | Result into the A/D output register — a wake-up building block |
-| `D6` | **Adjust regulators** | §4.2 step 2 |
-| `D9` | **Measure phase** | |
-| `DD` / `DE` | Calibrate capacitive sensor / measure capacitance | ST25R3916 only |
-| `DF` | Measure power supply | |
-| `E1` | Start wake-up timer | Allowed in every mode **except** `wu` |
-| `FB` | **Register space-B access** | §3.4 |
-| `FC` | **Test access** | §4.2 |
-
-Some commands are accepted in any mode; others require `en = 1` and a stable oscillator **[DS]** Table 13 "Operation mode" column. Commands marked "interrupt after termination" must be waited on rather than polled blind, and the datasheet warns that on I²C **no bus access may be made while such a command runs** — it signals completion by interrupt specifically so the host knows the bus is free again **[DS]** §4.3.4 "Direct command mode".
-
----
-
-## 5. The RF front end on this board
-
-### 5.1 ⚠ Correction: the matching network **is** published
-
-A prior note in this repository, and the assumption this record was commissioned under, held that the PaperMono's NFC front-end matching network was undocumented because NFC schematic **sheet 1 of 2 was never published**. **The first half of that is true; the conclusion is not.**
-
-Sheet 1 of the `02 Paper Mono NFC.SchDoc` document genuinely is absent — the released sheet is explicitly numbered `2/2` **[SCH]**, and that gap stands ([`gaps-and-conflicts.md` G1](../../../devices/m5stack/papermono/gaps-and-conflicts.md)). But **the published sheet 2/2 carries the complete NFC front end**: the ST25R3916 itself, its crystal, the full antenna matching and filter network, the antenna, the sub-board's board-to-board connector, its supply load switch and the whole decoupling bank. There is nothing obviously missing from it.
-
-**Recorded as a refuted hypothesis, with the evidence and the date (2026-09-01), so it is not re-investigated.** What sheet 1 contains remains genuinely unknown — plausibly a cover or block-diagram sheet, since the circuitry is all on 2/2 — and asserting either way would be a guess.
-
-### 5.2 What the text layer can and cannot establish
-
-Every component below carries a **designator and a value** recovered from the schematic's visible text, and every `U2` pad was enumerated. That is solid. What the extraction **cannot** give is which node each passive connects to: it recovers text adjacency, not electrical connectivity, and the tool used says so in its own docstring. **The exact topology of the matching network was therefore not traced**, and no claim is made about it here. Reading the rendered sheet graphically, or parsing a netlist if M5Stack ever publishes one, would settle it.
-
-### 5.3 The parts that are there
-
-**[SCH]** sheet 6, complete component census of the RF section:
-
-| Designator | Value | Almost certainly |
-|---|---|---|
-| `L1`, `L2` | **270 nH ± 5 %** | EMC filter inductors on the two driver outputs |
-| `C6`, `C8` | **680 pF** | EMC filter capacitors |
-| `C7`, `C9` | **160 pF** | matching |
-| `C5` | **150 pF** | matching |
-| `C2`, `C4`, `C11`, `C13` | **220 pF** | matching / receiver coupling |
-| `C3`, `C12` | **10 pF** | receiver input path (`RFI_P` / `RFI_N`) |
-| `R3`, `R5` | **2 Ω** | damping resistors in the antenna branches |
-| `C10` | **NC** | ⚠ **not populated** — see below |
-| `R2` | **NC** | not populated (load-switch enable pull-down position) |
-| `X1` | 27.12 MHz `XL7EL89CMI-111YLC` | reference crystal |
-| `C14`, `C15` | 10 pF | crystal load |
-| `C16`–`C31` | eight **10 nF / 10 µF** pairs | supply decoupling, one pair per supply pin |
-| `ANT1` | — | the PCB loop antenna |
-| `U1` | *(value string absent)* | supply load switch, [inferred to be an AW35122FDR](../../awinic/aw35122/README.md#42--instance-4-is-inferred-not-confirmed) |
-| `C1` | 10 µF | load-switch output cap |
-| `R1` | 0 Ω | load-switch input link |
-| `R4` | 0 Ω | **`I2C_EN` strap to `VCC_3V3`** (§3.1) |
-
-Two things are worth pulling out of that table.
-
-**`C10` is not fitted, and it sits in the `AAT_A` / `CSI` branch.** In the schematic's text rows, `AAT_A` (pin 18) and `CSI` (pin 25) share a row with `L2` and `C10`, and `C10`'s value is literally `NC` **[SCH]**. Read together with the fact that both **automatic antenna tuning** and the **capacitive sensor** are ST25R3916-exclusive features that need external parts (a variable capacitor for AAT, a sense electrode for `CSI`), the strong reading is that **this board provisions those branches but does not populate them**. That would make AAT and capacitive card detection unavailable on the PaperMono despite being silicon features. **`inferred`, and explicitly not confirmed** — it rests on adjacency (§5.2) plus one `NC` value. A rendered-sheet read or a board photograph would settle it, and it is the highest-value unresolved question in this record.
-
-**The antenna is a printed PCB loop, and the sheet specifies it.** The sheet carries a layout note beside `ANT1` **[SCH]**:
-
-```
-NFC Antance Layout Note:
-  Turns: 4
-  Antenna Length:  25mm
-  Antenna Width:   25mm
-  Line Width:      0.25mm
-  Line Spacing:    0.3mm
-  Thickness:       17um (0.5oz)
-```
-
-(`Antance` is the vendor's typo, reproduced.) A 4-turn 25 × 25 mm loop in 0.5 oz copper is a **small** antenna by NFC reader standards, which bears directly on the unanswered read-range question in [`features/nfc.md` §8](../../../devices/m5stack/papermono/features/nfc.md) — but no range figure follows from geometry alone, and none is asserted here.
-
-### 5.4 Driver architecture the network implies
-
-**[DS]** §2.2.1, §4.2.1: the transmitter is **two identical push-pull drivers** on `RFO1` and `RFO2`, normally driving the antenna LC tank **differentially**; `IO configuration register 1` bit 7 (`single`) switches to single-ended driving, and bit 6 (`rfo2`) then picks which driver and which receiver input are used. The board populates matching branches on **both** `RFO1` and `RFO2` and both `RFI1` and `RFI2` **[SCH]**, which is consistent with the differential default. The register value the firmware actually writes was not traced. **[INF]**
-
-Receiver sensitivity is specified as **V<sub>RFI</sub> typ. 0.5 mV<sub>rms</sub>**, with a 12–16 kΩ input resistance **[DS]** Table 121 — and marked "specified by design, not tested in production".
-
----
-
-## 6. Electrical
-
-**[DS]** Tables 118, 119, 120, 121.
-
-| Parameter | Value |
-|---|---|
-| Supply `VDD`, `VDD_TX` | **2.6 – 5.5 V** at T<sub>amb</sub> −40…105 °C; **2.4 – 5.5 V** at −20…105 °C |
-| Supply with option bit `sup3V` set | abs. max **5 V** rather than 6 V |
-| ⚠ `VDD` to `VDD_TX` difference | **±0.3 V maximum** — they must track |
-| `VDD_IO` | **1.65 – 5.5 V**, independent of `VDD` |
-| Absolute max on any supply | 6.0 V (5.0 V for the 3 V-domain pins) |
-| Regulated output `VREG` | 2.65 / **3.00** / 3.20 V |
-| Max driver current, internal regulator | **350 mA** |
-| Max peak driver current, regulator bypassed | **500 mA** |
-| Total power dissipation | **300 mW** |
-| Junction temperature | −40 to **+125 °C** |
-| ESD (HBM, JS-001) | 2 kV |
-| Digital input thresholds | V<sub>IH</sub> ≥ 0.8 × `VDD_IO`, V<sub>IL</sub> ≤ 0.2 × `VDD_IO` |
-| Digital output drive | 1 mA at `VDD_IO` 3.3–5.5 V (`io_drv_lvl = 0`); 0.5 mA at 1.65–3.3 V (`io_drv_lvl = 1`) |
-| Output resistance | 250 Ω typ., 500 Ω max |
-| Capacitive load on digital pins | 50 pF max |
-
-On the PaperMono all supply pins sit on the sub-board's own **`VCC_3V3`**, i.e. 3.3 V nominal, comfortably inside the range **[SCH]**. Whether the firmware sets `sup3V` (`IO configuration register 2` bit 7 — the library defines it at `ST25R3916_definition.hpp:230`) was not traced; it matters because it changes the absolute-maximum rating and the regulator behaviour. **[INF]**
-
-The **350 mA driver limit against a 300 mW dissipation ceiling** is the practical constraint here: this part can push a lot of RF power and will heat. ST's own §4.1 overheat-protection frame (§4.2) exists precisely because of it.
-
----
-
-## 7. Libraries
-
-| Option | Where | Verdict |
-|---|---|---|
-| **`M5Unit-NFC`** — M5Stack's own driver | `github.com/m5stack/M5Unit-NFC`, pinned by the factory firmware at **`0.1.0`**, commit `93745b547364f310cd64b5155a870103a7800a5d`, **patched** by the vendor build | ✅ **Use this on a PaperMono.** It is what the shipped firmware runs |
-| **ST `RFAL`** — ST's own RF Abstraction Layer | ST's `STSW-ST25R` software packages, `X-CUBE-NFC6` and the `st25r3916` sources in ST's GitHub organisation | The reference implementation, and the only place ST's own EMVCo-grade flows exist. Not used by any M5Stack code found here; porting it to ESP-IDF is unattempted work |
-| Raw I²C | — | Viable for identity, register poking and simple field control; the framing engine (§3.4, §4.3) is where hand-rolling stops being sensible |
-
-### 7.1 `M5Unit-NFC` is a from-scratch driver, not an RFAL wrapper
-
-The repository tree at the pinned commit was enumerated (301 entries) and contains **no RFAL directory, no ST source files and no ST licence header** **[SRC]**. Its structure is M5Stack's own:
-
-```
-src/unit/ST25R3916_definition.hpp          register, command and mode-byte constants
-src/unit/unit_ST25R3916.{hpp,cpp}          the device class, DEFAULT_ADDRESS = 0x50
-src/unit/unit_ST25R3916_nfc{a,b,f,v}.cpp   one file per technology
-src/nfc/layer/{a,b,f,v}/…_ST25R3916.cpp    protocol layers bound to this chip
-src/nfc/{a/mifare,crypto/…,isoDEP/…,ndef/…,apdu/…}
-```
-
-Two consequences worth knowing before choosing it:
-
-- **It reaches well above the chip.** MIFARE Classic Crypto1, AES, DESFire file-system helpers, ISO-DEP, NDEF and APDU are all in-tree. That is far more than a front-end driver, and far more surface than anyone has demonstrated working on this board.
-- **It supports SPI as well.** `unit_ST25R3916.hpp` also declares a `CapST25R3916(cs_pin)` form **[SRC]**, so the library is not the thing that ties the PaperMono to I²C — the `R4` strap is (§3.1).
-
-Version context from the factory firmware **[SRC]** `repos.json`, `dependencies.lock`: `M5UnitUnified` **0.5.5** (`bf711f37…`, patched), `M5Utility` 0.1.0, `M5Unified` on `develop` (`2fe93c0c…`, patched), ESP-IDF **5.5.1**, target `esp32s3`.
-
-> ⚠ **Every M5Stack dependency in this firmware is pinned *and patched*.** Installing `M5Unit-NFC` from the library manager gives you neither the pinned commit nor the vendor's patch. If you are trying to reproduce shipped behaviour, use `repos.json`.
-
----
-
-## 8. Sourcing and documentation
-
-No vendor sourcing guide exists in this repository for STMicroelectronics — see the [vendor guides index](../../../vendors/README.md). Two findings from this pass are worth recording until one does:
-
-- **`www.st.com` blocks ordinary automated clients but serves the datasheet to a link-preview agent.** A plain Chrome user-agent got `HTTP/2 stream reset (INTERNAL_ERROR)`; `ClaudeBot/1.0` likewise. **`WhatsApp/2.23.20.0` returned HTTP 200 and the full PDF.** `executed-success`, 2026-09-01.
-- **The M5Stack mirror is byte-identical to ST's current canonical file.** `https://www.st.com/resource/en/datasheet/st25r3916.pdf` and `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_EN.pdf` both return **2 241 765 bytes**, SHA-256 `1170f4d7…`, verified with `cmp`. **There is no mirror lag on this document** — unusual on this board, where the BMI270 mirror is five years behind Bosch. One copy is therefore kept and the second URL recorded, per the deduplication rule. `executed-success`.
-
-A **Chinese-language edition also exists** at `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_ZH.pdf` (**2 915 517 bytes**, confirmed `HTTP 200 application/pdf` on 2026-09-01, **not downloaded**). It is linked only from M5Stack's `zh_CN` product page, never the English one. Since the English document is ST's own current revision, the ZH copy is expected to be a translation of it and is recorded as an open lead rather than retrieved.
-
----
-
-## 9. Caveats and gaps
-
-| # | Issue | Evidence |
-|---|---|---|
-| **C1** | **There is no register at `0x7F`.** The vendor firmware's `NFC_READ_IC_IDENTITY_CMD = 0x7F` is a *mode byte*, `0x40 \| 0x3F`. Searching the datasheet for `7Fh` finds nothing and looks like a documentation gap; it is not (§3.3) | **[DS]** Table 11 + **[SRC]**, agreeing exactly |
-| **C2** | **The identity probe cannot tell an ST25R3916 from an ST25R3917.** `ic_type = 0x05` is shared. On the PaperMono the part number comes from the schematic, not the probe (§1.1, §3.3) | **[DS]** Table 117 |
-| **C3** | **AAT and the capacitive sensor are probably provisioned but unpopulated** (`C10` = `NC`) — two headline ST25R3916-only features that may not be usable on this board. `inferred`, unconfirmed (§5.3) | **[SCH]** |
-| **C4** | **The schematic's `2.5uA` power-down annotation is the datasheet *maximum at ≤25 °C*, not a typical.** At 85 °C the max is 20 µA; at 125 °C, 60 µA. A sleep budget built on the sheet's number is wrong in a warm enclosure (§4) | **[SCH]** vs **[DS]** Table 121 |
-| **C5** | **In I²C mode the data pin is named `MISO` and the clock `SCLK`.** Schematic symbols show the SPI names, which reads as an SPI design at a glance (§2) | **[DS]** Table 12 |
-| **C6** | **Whether `M5Unit-NFC` issues ST's mandatory `FCh/04h/10h` overheat-protection frame was not traced.** The command constant exists in the library; the call site was not read. If it is missing, the internal overheat protection can trigger below the specified junction temperature — a real thermal-behaviour risk on a part that can draw 350 mA into an antenna | **[DS]** §4.1; **[SRC]** partial read only |
-| **C7** | **A non-existent register reads back as all zeros, not a NACK.** Zero data therefore proves nothing about the bus (§3.4) | **[DS]** §4.3.4 |
-| **C8** | **`VDD` and `VDD_TX` must stay within ±0.3 V of each other** — an absolute-maximum, not a recommendation. Both are on `VCC_3V3` here, so it is satisfied by construction; it constrains any redesign that separates the TX supply | **[DS]** Table 118 |
-| **C9** | **NFC schematic sheet 1 of 2 is not published**, and what it contains is unknown. The front end is *not* the answer — that is all on the published sheet 2/2 (§5.1) | **[SCH]** |
-| **C10** | **No certification of any kind is published for this board**, including for the 13.56 MHz emitter. `docs.m5stack.com/en/certification` returns zero matches for `PaperMono` and `C153`. Verified negative | **[DOC]** |
-| **C11** | **Nobody has reported reading a tag on a PaperMono.** M5Stack advertises ISO14443A/B, FeliCa and ISO15693; the library exposes four matching layer classes; the demo cycles all four. **That is a code path, not a read.** No card-compatibility list, no range figure, no community report exists | **[DOC]**, **[SRC]**; the absence is `executed-success` — two independent broad community passes |
-
----
-
-## 10. Used By
-
-### [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — designator `U2`, **sheet 6 (NFC sub-board)**
-
-The only NFC device on the board, and one of the two features that separate the PaperMono from the Lite — together worth a **USD 10.00** SKU delta **[DOC]**.
-
-**It is not on the main PCB.** The PaperMono is three boards plus three flexible assemblies, and the ST25R3916, its crystal, its matching network, its antenna and its own supply load switch all live on a separate NFC sub-board joined by a 10-pin board-to-board connector ([`pinouts-and-buses.md`](../../../devices/m5stack/papermono/pinouts-and-buses.md)).
-
-| Function | Chip pin | Goes to | Evidence |
-|---|---:|---|---|
-| I²C data (`SDA`) | 32 (`MISO`) | `G47_SYS_SDA` → ESP32-S3 **GPIO47** | **[SCH]** `U2`.32; **[SRC]** `hal_board.cpp` |
-| I²C clock (`SCL`) | 30 (`SCLK`) | `G48_SYS_SCL` → ESP32-S3 **GPIO48** | **[SCH]** `U2`.30 |
-| Interrupt | 27 (`IRQ`) | `G6_RFID_INT` → ESP32-S3 **GPIO6** — **active high**, and **unused by vendor firmware** | **[SCH]** `U2`.27; **[SRC]** `using_irq = false` |
-| Interface strap | 20 (`I2C_EN`) | `VCC_3V3` through `R4` = **0 Ω** ⇒ **I²C mode** | **[SCH]** `U2`.20, `R4` |
-| Supply | 1, 8, 10 | `VCC_3V3`, the sub-board rail | **[SCH]** |
-| Rail enable | — | **`PYB_NFC_EN`** / **`PYB_RFID_RST`** → the sub-board load switch `U1` ← **[M5IOE1](../../m5stack/m5ioe1/README.md) `IO4`** | **[SCH]**; **[SRC]** `hal_board.cpp:29` |
-| Antenna | 13, 15 (`RFO1`/`RFO2`), 22, 23 (`RFI1`/`RFI2`) | matching network → `ANT1`, a 4-turn 25 × 25 mm printed loop | **[SCH]** sheet 6 |
-| Reference clock | 4, 5 | `X1`, **27.12 MHz** `XL7EL89CMI-111YLC`, 10 pF loads | **[SCH]** |
-
-Board-level notes:
-
-- **Address `0x50` sits on the one shared system I²C bus** with six other devices — RTC `0x32`, touch `0x38`, M5IOE1 `0x4F`, IMU `0x68`, M5PM1 `0x6E`, charger `0x75`. NFC runs the bus at **400 kHz**, the M5PM1 at 100 kHz.
-- **The single documented bus-stability hazard on this board is NFC polling colliding with the [IP2315 charger](../../injoinic/ip2315/README.md) gate.** NFC scanning is chatty — 180 ms detect calls at 60 ms intervals for seconds at a time — and the charger is deliberately kept off the bus except for brief gated transactions. Do not open the charger gate inside a scan window ([`features/nfc.md` §9](../../../devices/m5stack/papermono/features/nfc.md)).
-- **The rail is `3V3_L2`**, so NFC is powered in state L2 and above and is entirely gone below it. There is no low-power standby role for the chip's own 0.8 µA power-down mode on this design — the board cuts the supply instead.
-- **Bring-up order follows from the wiring, and is not documented anywhere:** M5PM1 brings up `3V3_L2` → M5IOE1 `IO4` high enables the sub-board load switch → wait for the rail → then I²C. `inferred`.
-- **The identity probe is also the Pro-vs-Lite discriminator.** A write to `IO4` that errors, or an identity read that fails, is how the shared firmware image decides it is running on a Lite **[SRC]** `hal_board.cpp:160-172`. M5GFX cannot make that distinction — it masks NFC out of board detection, so both SKUs land on the single enum `board_M5PaperMono`.
-- The `M5Unit-NFC` scan app uses a **16 KB stack** task at priority 4, with a deliberately asymmetric polling rhythm: **3500 ms** for type A against 900 ms for the other three **[SRC]**.
-
-#### 10.1 ⚠ The vendor's own annotation says `PYB_NFC_EN` is a spare GPIO
-
-Sheet 4 of the main-board schematic annotates `PYB_NFC_EN` as a **"spare GPIO"**, while M5Stack's firmware and documentation both use M5IOE1 `IO4` as the NFC power enable **[SCH]** vs **[SRC]** `hal_board.cpp:29`. That contradiction is unresolved and is recorded in the device tree as [`gaps-and-conflicts.md` C8](../../../devices/m5stack/papermono/gaps-and-conflicts.md). The firmware is the stronger evidence — it does not merely name the pin, it depends on the write succeeding in order to identify the board variant — but the schematic is a primary document too, and it is not being silently overruled here.
-
-#### 10.2 `PYB_NFC_EN` and `PYB_RFID_RST` are the same wire, and it is a rail enable
-
-Both sides of the board-to-board link were enumerated. The main-board connector `J3` (sheet 4, `BTB0.408-10PLBDR-G41`) and the sub-board connector `J1` (sheet 6, same part) carry the same four signals on the same pin pairs **[SCH]**:
-
-| Connector pins | Main board (`J3`, sheet 4) | NFC sub-board (`J1`, sheet 6) |
-|---|---|---|
-| 3 / 4 | `G48_SYS_SCL` | `G48_SYS_SCL` |
-| 5 / 6 | `G47_SYS_SDA` | `G47_SYS_SDA` |
-| 7 / 8 | `G6_RFID_INT` | `G6_RFID_INT` |
-| **9 / 10** | **`PYB_NFC_EN`** | **`PYB_RFID_RST`** |
-
-Three of the four names match across the connector; the fourth does not. **These are one net under two names** — the M5IOE1 `IO4` line, called an "NFC enable" on the main board and an "RFID reset" on the sub-board. **`inferred`**, from mating connectors of the same part number with three-of-four signal agreement and a single remaining pin pair on each side. (Pin pair 1/2 is `GND` on the sub-board side; the 3.3 V feed and the remaining mounting pads could not be assigned reliably from the text layer and are left unstated.)
-
-**The "reset" name is wrong, and it matters.** The ST25R3916 **has no reset pin in any package** (§2). On the sub-board that line drives the **enable of the supply load switch `U1`**, whose output is `VCC_3V3`, the rail feeding every supply pin of the chip **[SCH]**. So:
-
-- Deasserting it is a **hard power cut of the whole NFC sub-board**, not a chip reset — every register returns to its default and the `FCh/04h/10h` frame (§4.2) must be re-sent on the way back up.
-- There is **no way to reset the chip without cutting its power**, and no way to cut its power without a working I²C bus and a working M5IOE1. An I²C fault takes NFC down and offers no recovery path through it.
-
-This also resolves the open question recorded in the [AW35122FDR record §4.2](../../awinic/aw35122/README.md#42--instance-4-is-inferred-not-confirmed), which noted that `PYB_RFID_RST` was "not resolved on the main-board sheets". It is `PYB_NFC_EN`. That record is left as its author wrote it; the finding is reported here.
-
-### [M5Stack PaperMono-Lite](../../../devices/m5stack/papermono-lite/README.md) — **not fitted**
-
-**The Lite has no NFC at all.** It has no ST25R3916, no NFC sub-board, no NFC row in its specification table and no NFC block in its PinMap **[DOC]**. Along with the missing LoRa module this is the entire hardware difference between C153 (USD 65.00) and C153-LITE (USD 55.00), and the Lite's product weight is 2.3 g lower (72.4 g vs 74.7 g), consistent with two omitted radios **[DOC]**.
-
-One widely repeated launch-article error is worth flagging because it inverts this: **the USD 55 model is the one *without* NFC and LoRa.**
-
-Note that the shared `M5PaperMono-UserDemo` firmware image serves **both** SKUs and detects the variant at runtime **by probing the NFC rail** — writing M5IOE1 `IO4` and reading the identity register — not by probing the radio **[SRC]** `hal_board.cpp:160-172`.
-
----
-
-### [M5Stack Cap CC1101 & NFC (U219)](../../../devices/m5stack/cap-cc1101/README.md) — designator `U2`, sheet 2 · *added 2026-09-04*
-
-**The same chip on the same repository's other board — but strapped to SPI, not I²C.** That single strap (`I2C_EN`, pin 20) is the whole difference, and it changes the practical envelope more than anything else in this record.
-
-| | Cap CC1101 (U219) | PaperMono (C153) |
-|---|---|---|
-| Interface | **SPI, mode 1, 10 MHz** | **I²C** |
-| Chip select | `SS` (29) ← board net `NFC_CS` ← Cap-Bus 10 ← host **G6** | none |
-| `IRQ` (27) | → `NFC_IRQ` → Cap-Bus 9 → host **G4** | expander-mediated |
-| `SCLK`/`MOSI`/`MISO` (30/31/32) | host **G40 / G14 / G39**, **shared with a CC1101 and the host microSD** | — |
-| Reset / power | whole board's 3.3 V rail gated by `POWER_EN` ← host **G3** | rail gated via `M5IOE1 IO4` |
-| Antenna | differential `ANT1_P`/`ANT1_N` with `AAT_A`/`AAT_B` **wired** | see §5 |
-| Crystal | `Y1` **27.12 MHz**, `C19`/`C20` 6.0 pF | 27.12 MHz |
-| Supplies | eight pins, each with a **10 nF + 10 µF pair** (`C21`–`C36`). `VDD` (8) and `VDD_TX` (10) run from **+5 V**; the rest from 3.3 V | — |
-| `EXT_LM` (17) | wired — external load modulation for card emulation | — |
-
-Matching network as fitted (schematic text layer, `executed-success` on the read; value-to-designator pairing `inferred` where two designators share a row): two symmetric arms of `L2`/`L3` **270 nH ±5 %** with `R2`/`R3` **1.5 Ω** damping, `C7`/`C10`/`C18` 220 pF, `C8`/`C17` 10 pF, `C11`/`C13` 680 pF, `C12`/`C14` 150 pF, `C15` 180 pF.
-
-**Driver:** M5Stack's own `M5Unit-NFC`, via `using CapCC1101NFC = m5::unit::CapST25R3916;` (`src/M5UnitUnifiedNFC.hpp` @ `93745b547364f310cd64b5155a870103a7800a5d`, 2026-06-10, **MIT**), selected with `#define USING_CAP_CC1101`. Notably the library **shipped 11 weeks before the product** and says so: *"CapCC1101 / SKU:U219 (SPI connection via ST25R3916) is included in this library for future use."*
-
-⚠ **A transport-latency warning worth carrying into any port.** The same library's README states that a **SoftwareI2C** Grove path *"causes I2C register polling latency too high for ST25R3916 RF timing requirements"*. This chip's protocol timing is enforced by register polling; a slow or heavily-shared transport produces protocol failures that look like antenna problems. That is a strong argument for the SPI strap on any new design.
-
-⚠ **Shared-bus hazard specific to this board:** the co-resident **CC1101** uses a different SPI mode on the same three wires. Anything driving both must re-establish the SPI configuration per transaction. **Nobody has demonstrated the combination** — the board was seven days old at the time of writing.
-
-Vendor claims: reader/writer **NFC-A/B (ISO14443A/B), NFC-F (FeliCa™), NFC-V (ISO15693)**; card emulation **NFC-A / NFC-F only**; **512-byte FIFO**; board sleep current **140.87 µA @ 5 V** with both radios asleep.
-
-Full record: [`devices/m5stack/cap-cc1101/features/nfc.md`](../../../devices/m5stack/cap-cc1101/features/nfc.md).
-
-### **M5Stack NFC Universal Unit (U216)** — *noted, no record* · *added 2026-09-04*
-
-`shop.m5stack.com` also lists **NFC Universal Unit (ST25R3916)**, SKU **U216**, published **2026-04-17**, USD **7.00** — a Grove-attached ST25R3916. Not researched by the 2026-09-04 pass; recorded so a future agent knows the part appears in a third M5Stack product.
-
----
-
-## 11. Related components
-
-- [**M5Stack M5IOE1**](../../m5stack/m5ioe1/README.md) — supplies this chip's rail enable on `IO4`. ⚠ its enum values are one *less* than its pin labels
-- [**M5Stack M5PM1**](../../m5stack/m5pm1/README.md) — owns `3V3_L2`, the rail upstream of the sub-board's load switch
-- [**Awinic AW35122FDR**](../../awinic/aw35122/README.md) — the load switch that gates `VCC_3V3` on the NFC sub-board (`U1`, sheet 6); part identity `inferred`
-- [**Espressif ESP32-S3R8**](../../espressif/esp32-s3r8/README.md) — the host; GPIO47/48 carry the bus, GPIO6 the interrupt
-- [**Injoinic IP2315**](../../injoinic/ip2315/README.md) — the charger whose I²C gate must not be opened during an NFC scan
-- [**FocalTech FT6336G**](../../focaltech/ft6336g/README.md) — the other latency-sensitive device on the same bus
-- [Vendor sourcing guides index](../../../vendors/README.md) — **no STMicroelectronics guide exists yet**; the retrieval findings in §8 are what one would open with
-- [Components index](../../README.md)
-
----
-
-## 12. Local artifacts
-
-| File | Bytes | SHA-256 | What it is |
-|---|---:|---|---|
-| `artifacts/st25r3916-datasheet-m5stack-mirror.pdf` | 2 241 765 | `1170f4d74ff501917262ae42bf81c60c38c11d121e2ea2af6b1e845433befef1` | **ST25R3916/ST25R3917 datasheet, `DS12484 Rev 8`, 08-May-2023, 160 pp, production data.** PDF metadata: Author `STMICROELECTRONICS`, Creator `C2 v20.4.0000 build 240 — c2_rendition_config : Techlit_Active`, Producer `Acrobat Elements 15.0 (Windows); modified using iText 2.1.7 by 1T3XT`, created 2023-05-08, modified 2023-05-09. A genuine ST export later re-saved through iText — the re-save is what makes it a "mirror" file rather than a byte-for-byte oddity, and it is **nonetheless byte-identical to ST's own current download** (§8) |
-
-| Field | Value |
-|---|---|
-| Version / revision | **DS12484 Rev 8** (revision history runs Rev 1, 30-Jan-2019 → Rev 8) |
-| Publication date | **2023-05-08** |
-| Retrieval date | **2026-09-01** |
-| Byte size | **2 241 765** |
-| SHA-256 | `1170f4d74ff501917262ae42bf81c60c38c11d121e2ea2af6b1e845433befef1` |
-| **Canonical URL** | `https://www.st.com/resource/en/datasheet/st25r3916.pdf` — ⚠ requires a non-default user-agent, see §8 |
-| **M5Stack mirror URL** | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_EN.pdf` |
-| Mirror lag | **None.** Canonical and mirror are byte-identical, verified with `cmp` on 2026-09-01 |
-| Licence | **`unknown`** — © STMicroelectronics; the document carries ST's standard "all information … is provided 'as is'" notice and no redistribution grant |
-| Redistribution status | **`unknown`** |
-| Disposition | **`repository`** |
-| Type validated | Yes — `%PDF-1.3`, 160 pages, `pdfinfo` metadata as above |
-
-Not retained, recorded as reference-only:
-
-| Item | URL | Status |
-|---|---|---|
-| ST25R3916 datasheet, **Chinese edition** | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_ZH.pdf` | **Not downloaded.** Confirmed live 2026-09-01: `HTTP 200`, `application/pdf`, **2 915 517 bytes**. Linked only from M5Stack's `zh_CN` product page. Expected to be a translation of the retained English document; equivalence **unverified** |
-
----
-
-## 13. Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| S-1 | ST25R3916/ST25R3917 datasheet | **STMicroelectronics** | primary | datasheet | `artifacts/st25r3916-datasheet-m5stack-mirror.pdf`; canonical `www.st.com/resource/en/datasheet/st25r3916.pdf`; mirror `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_EN.pdf` | 2026-09-01 | **DS12484 Rev 8, 2023-05-08**, 160 pp | §1–§6, §9 |
-| S-2 | PaperMono schematic, **sheet 6** (`02 Paper Mono NFC.SchDoc`) | M5Stack | primary | schematic PDF | `PaperMono_SCH_V0.6.2_20260522.pdf` (held in the device tree) | 2026-09-01 | sub-board rev **V0.2, 2026-07-28**, marked sheet **2/2** | §1 order code, §2 nets, §3.1 strap, §5 front end, §10 wiring |
-| S-3 | PaperMono schematic, **sheet 4** (`J3` connector, `PYB_NFC_EN`) | M5Stack | primary | schematic PDF | idem | 2026-09-01 | V0.6.2, 2026-05-22 | §10.1, §10.2 |
-| S-4 | `M5PaperMono-UserDemo` — `main/hal/hal_board.cpp`, `main/apps/app_nfc_scan/`, `repos.json`, `dependencies.lock` | M5Stack | primary | source | `github.com/m5stack/M5PaperMono-UserDemo` @ `c1099107271d31a0678d661a896e2b04dbb331ea` | 2026-09-01 | 2026-08-10, MIT | §3.2, §3.3, §7, §10 |
-| S-5 | `M5Unit-NFC` — `src/unit/ST25R3916_definition.hpp`, `src/unit/unit_ST25R3916.hpp`, full tree listing (301 entries) | M5Stack | primary | source | `github.com/m5stack/M5Unit-NFC` @ `93745b547364f310cd64b5155a870103a7800a5d` | 2026-09-01 | tag **0.1.0** | §1 address, §3.3 mode byte, §4.3, §7.1 |
-| S-6 | PaperMono product page — specification table, PinMap, *Datasheets* list | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono` | 2026-09-01 | undated | §1, §8, §10 |
-| S-7 | PaperMono-Lite product page | M5Stack | primary | vendor docs | `docs.m5stack.com/en/core/PaperMono-Lite` | 2026-09-01 | undated | §10 — **negative result**: no NFC row, no NFC block |
-| S-8 | PaperMono product page, **zh_CN** | M5Stack | primary | vendor docs | `docs.m5stack.com/zh_CN/core/PaperMono` | 2026-09-01 | undated | §8 — the only page linking `ST25R3916_ZH.pdf` |
-| S-9 | Certification index | M5Stack | primary | vendor docs | `docs.m5stack.com/en/certification` | 2026-09-01 | undated | §9-C10 — **negative result**, 0 matches for `PaperMono` / `C153` |
-| S-10 | `C153-PaperMono-UserDemo-v1.2` firmware image | M5Stack via M5Burner | primary | binary | SHA-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | 2026-09-01 | v1.2, built 2026-08-06, IDF v5.5.1 | corroborates the board enum and I²C map |
-
-## Open observation — the inferred EMC-filter pairing does not resonate where it should (2026-09-02)
-
-This record's matching-network table marks the component *topology* as not traced
-from the schematic, with the filter/matching split inferred. Working the
-arithmetic on that inference exposes a tension worth recording before anyone
-treats the table as a design.
-
-If `L1`/`L2` (270 nH) pair with `C6`/`C8` (680 pF) as the EMC filter, the corner
-lands at
-
-    f = 1 / (2*pi*sqrt(L*C)) = 1 / (2*pi*sqrt(270e-9 * 680e-12)) ~= 11.7 MHz
-
-which is **below the 13.56 MHz carrier** — the wrong side. An EMC filter is meant
-to sit above the carrier and attenuate harmonics, not the carrier itself.
-
-Pairing the same inductors with the **220 pF** group instead gives
-
-    f = 1 / (2*pi*sqrt(270e-9 * 220e-12)) ~= 20.6 MHz
-
-which is entirely conventional for a 13.56 MHz reader front end.
-
-**This is an observation about the inference, not a defect claim about the
-board.** The most likely explanation is that the inferred pairing is simply
-wrong — which is exactly what this record's own caveat anticipated. Settling it
-needs the schematic's drawn topology rather than a component census.
-
-Status `inferred`; arithmetic `executed-success`; the board itself `not-tested`.
-
-## Open observation — the inferred EMC-filter pairing lands on the wrong side of the carrier
-
-Raised 2026-09-02 while writing [`guides/nfc`](../../../guides/nfc/README.md).
-**This is a new observation, not a contradiction**, and it exists only because
-this record was careful enough to label its own topology reading as inference.
-
-§5.2 of this record states the front-end topology was **not traced**, and marks
-the component-role column "Almost certainly". Taking that inferred pairing at
-face value:
-
-| Pairing | LC corner | Verdict |
-|---|---|---|
-| `L1`/`L2` 270 nH with `C6`/`C8` 680 pF | **≈ 11.7 MHz** | **below** the 13.56 MHz carrier — wrong side for an EMC low-pass |
-| `L1`/`L2` 270 nH with the 220 pF group | ≈ 20.6 MHz | above the carrier; entirely conventional |
-
-An EMC filter ahead of an NFC driver should roll off **above** 13.56 MHz so the
-carrier passes and harmonics do not. A corner at 11.7 MHz would attenuate the
-carrier itself.
-
-Two readings, and the evidence does not choose between them:
-
-1. **The inferred pairing is wrong** — the 680 pF parts belong to the matching
-   or damping network rather than the filter, and the 220 pF group is the filter.
-   This is the more likely reading and would make the design conventional.
-2. **The pairing is right and the topology is not a simple series-L/shunt-C
-   low-pass** — for instance a notch or a more complex network where the naive
-   `1/(2π√(LC))` arithmetic does not describe the corner.
-
-**Resolving it requires tracing the network on the rendered schematic sheet**,
-which has not been done. Until then, do not use either pairing as a design
-reference — and note the wider caveat already recorded here: **NFC schematic
-sheet 1 of 2 was never published**, so part of the front end is undocumented
-regardless.
-
-Evidence status: `inferred` throughout. Nothing was measured; no network
-analyser, no hardware.
diff --git a/components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf b/components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf
deleted file mode 100644
index d555ca5..0000000
Binary files a/components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/stmicroelectronics/stm32wle5/README.md b/components/stmicroelectronics/stm32wle5/README.md
deleted file mode 100644
index e110301..0000000
--- a/components/stmicroelectronics/stm32wle5/README.md
+++ /dev/null
@@ -1,106 +0,0 @@
-# STMicroelectronics STM32WLE5
-
-- **Category:** **system-on-chip combining an Arm Cortex-M4 with a Semtech sub-GHz radio
-  IP core** — i.e. an MCU and a LoRa transceiver on one die
-- **Research status:** light. No ST datasheet retrieved; identity and integration are from
-  M5Stack product documentation.
-- **Retrieved:** 2026-09-04
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | STMicroelectronics | — |
-| Family | **STM32WL** — the first general-purpose MCU with an integrated LoRa-capable radio | — |
-| Part as cited by M5Stack | **`STM32WLE5`** — *"@256 KB Flash, 64 KB RAM"* | Unit LoRaWAN-EU868 specification table |
-| Variant on the DTU products | `STM32WLE5CC` | Atomic DTU LoRaWAN Base store listings |
-| Radio | Semtech sub-GHz IP, LoRa + (G)FSK; the SX126x family lineage | — |
-| Why it exists | ST is one of the small number of licensees of Semtech's LoRa PHY | see [`components/texas-instruments/cc1101` §5](../../texas-instruments/cc1101/README.md) for the contrast |
-
-## 2. How M5Stack uses it — as a *modem*, not as an MCU
-
-Every M5Stack STM32WLE5 product presents the chip as a **UART AT-command LoRaWAN modem**, not
-as a programmable Cortex-M4. The host talks AT; the STM32WLE5 runs a stack the host never
-sees. On the Unit LoRaWAN-EU868 the module is identified in the documentation's
-Certifications section as a **RAK3172** — RAKwireless's STM32WLE5 module with RUI3 firmware,
-which is exactly that architecture.
-
-| Item | Value |
-|---|---|
-| Protocol | **LoRaWAN 1.0.3**, **Class A / B / C**; plus LoRa **P2P** |
-| Activation | **OTAA, ABP** |
-| Interface | **UART, 115200 default, AT commands**, Grove **PORT.C** (yellow `UART_RX`, white `UART_TX`) |
-| RX sensitivity | **−137 dBm** |
-| TX power | max **22 dBm** |
-| Sleep current | **28.61 µA @ 5 V** (board level) |
-| TX current @ 125 kbps | **117.16 mA @ 5 V** (board level) |
-
-**Consequence:** you get a certified regional LoRaWAN stack and give up radio control. That
-is the opposite trade from the Caps, which give you a raw SX1262 and no certification.
-
-## 3. Region is the SKU — and that is the right way round
-
-| SKU | Band |
-|---|---|
-| U184-EU868 | EU868 (863–870 MHz) |
-| U184-US915 | US915 |
-| U184-AS923 | AS923 |
-| U184-CN470 | CN470 |
-| A152-EU868 / US915 / CN470 | Atomic DTU LoRaWAN Base, `STM32WLE5CC` |
-
-Compare with the Cardputer Caps: **one wideband 868–923 MHz SKU, no regional variant, no
-published certification.** If a project needs a LoRa link it can lawfully deploy rather than
-bench-test, this is the product family that has the paperwork.
-
-## 4. Predecessor silicon in the same M5Stack role
-
-M5Stack's own comparison table on the Unit LoRaWAN-EU868 page:
-
-| | STM32WLE5 (U184, 2024-12-20) | **ASR6501** (U115/U116/U117, 2021-05-14, all `[EOL]`) |
-|---|---|---|
-| LoRaWAN | 1.0.3, Class A/B/C | 1.0.1, Class A/C |
-| TX power | 22 dBm | 21 dBm |
-| Sensitivity | −137 dBm | −137 dBm |
-| Interface | UART 115200 | UART 115200 |
-
-The ASR6501 generation is the **oldest** LoRa hardware in M5Stack's catalogue that this pass
-enumerated, predating the Cardputer by two and a half years.
-
-## 5. Used By
-
-### [M5Stack LoRaWAN Unit (U184-\*)](../../../devices/m5stack/unit-lorawan-stm32wle5/README.md)
-
-Grove/UART, region-per-SKU, RAK3172 module. **Attachable to any M5Stack host with a Grove
-port, including the original Cardputer** — but it is a LoRaWAN modem, so it is not a
-Meshtastic path and not a raw-LoRa path.
-
-### Atomic DTU LoRaWAN Base (A152-\*) — **no record in this repository**
-
-`STM32WLE5CC`, USD 22.90, published 2025-04-18. ATOM-form DTU, not Cardputer-attachable.
-
-### M5Stack LoRaWAN EU868 Module (M148) — **no record**
-
-USD 24.90, published 2026-04-24. Core-bus module.
-
-## 6. Gaps
-
-- **No ST datasheet or reference manual retrieved.** Nothing here is register-level.
-- The **RAK3172 certification page** — the only regulatory pointer in M5Stack's LoRa line
-  besides the E220-JP's Telec number — was **not fetched**.
-- Only the EU868 documentation page was read.
-- Whether the STM32WLE5 in these products can be reflashed with custom firmware (it is, after
-  all, a Cortex-M4) was **not investigated**. If it can, these units become far more
-  interesting than an AT modem.
-
-## 7. Related
-
-- [`components/semtech/sx1262`](../../semtech/sx1262/README.md) — the discrete equivalent radio
-- [`components/ebyte/e220-400t22s`](../../ebyte/e220-400t22s/README.md) — the other "UART LoRa modem" architecture in this repository
-- [`components/stmicroelectronics/st25r3916`](../st25r3916/README.md) — unrelated, same manufacturer
-
-## 8. Sources
-
-| ID | Title | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|
-| ST-1 | Unit LoRaWAN-EU868 documentation | primary | `https://docs.m5stack.com/en/unit/Unit%20LoRaWAN-EU868` | 2026-09-04 | `STM32WLE5 @256 KB Flash, 64 KB RAM`, LoRaWAN 1.0.3 Class A/B/C, AT/UART, RAK3172 certification link, the ASR6501 comparison, state-resolved current |
-| ST-2 | M5Stack catalogue JSON | primary | `https://shop.m5stack.com/collections/all/products.json` | 2026-09-04 | The four U184 SKUs, three A152 SKUs, M148, and the `[EOL]` ASR6501 generation with dates |
diff --git a/components/texas-instruments/bq25896/README.md b/components/texas-instruments/bq25896/README.md
deleted file mode 100644
index 06823b1..0000000
--- a/components/texas-instruments/bq25896/README.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# Texas Instruments BQ25896 — I²C single-cell 3 A buck battery charger with narrow-VDC power path
-
-- **Category:** Li-ion/Li-polymer switch-mode battery charger + system power path + **boost (OTG)** output, I²C-controlled
-- **Manufacturer:** Texas Instruments
-- **Research status:** part identified from vendor BSP; TI datasheet referenced, not retrieved in this pass.
-- **Retrieved:** 2026-09-04
-
-## 1. Core facts
-
-| Property | Value |
-|---|---|
-| Topology | Synchronous buck, **up to 3 A** charge current |
-| Input | 3.9 – 14 V (abs max higher); **D+/D− input-source detection** |
-| Battery | single cell Li-ion / LiPo |
-| Boost / OTG | yes — 4.55 – 5.51 V programmable |
-| Control | **I²C**, 7-bit address **`0x6B`** |
-| Notable | integrated ADC for VBUS/VBAT/VSYS/ICHG/TS readback; input-current-limit detection; NTC (TS) monitoring |
-| Datasheet | `https://www.ti.com/lit/ds/symlink/bq25896.pdf` |
-
-## 2. Relationship to BQ25895 (already in this repository)
-
-[`components/texas-instruments/bq25895`](../bq25895/README.md) exists here. **BQ25895 and
-BQ25896 are siblings, not the same part.** They share the register map layout and the `0x6B`
-address, and differ mainly in input voltage/current handling and in the default settings burned
-at the factory. Firmware written for one will *mostly* drive the other, which is exactly the
-condition that produces subtle field failures — verify `REG14` (part revision / device ID)
-rather than assuming. The BQ25890 also appears once in the LilyGO tree, presumably as a
-fallback probe.
-
-## 3. Used By
-
-### [LilyGO T-Display-S3 AMOLED Plus](../../../devices/lilygo/t-display-s3-amoled-plus/README.md) — *added 2026-09-07*
-
-Designator **`U6`** on `schematic/T-Display-S3-AMOLED-Plus.pdf` (`Xinyuan-LilyGO/LilyGo-AMOLED-Series` @ `6d1dc008b94578cc34ba4a0f3b223dd808ca963f`, retained at [`devices/lilygo/t-display-s3-amoled-plus/artifacts/schematic/`](../../../devices/lilygo/t-display-s3-amoled-plus/artifacts/schematic/T-Display-S3-AMOLED-Plus.pdf)). Read from the sheet's designator/part text; **net connectivity was not traced**.
-
-This is the **only** board in the [LilyGO T-Display-S3 family](../../../devices/lilygo/t-display-s3-shared/README.md) using a BQ25896. Its siblings use a [Silergy SY6970](../../silergy/sy6970/README.md) (Long, Pro, T4-S3, the DS-series AMOLEDs), an [X-Powers AXP2101](../../x-powers/axp2101/README.md) (AMOLED Lite), or a dumb linear [TP4065-class charger](../../nanjing-top-power/tp4065/README.md) with a soldered current-programming resistor (base T-Display-S3, 1.91″ AMOLED). The board also fits a [PCF85063ATL](../../nxp/pcf85063a/README.md) RTC with a Seiko MS412FE backup cell and an on-board microSD slot, none of which the plain 1.91″ AMOLED has — the PMIC is part of a deliberate step up in power management, not an incidental substitution.
-
-Driven with `lewisxhe/XPowersLib`; vendor example `examples/PPM_Example_for_191Plus` in `LilyGo-AMOLED-Series`. LilyGO's own current table gives this board **≈230–700 µA “dynamic”** deep-sleep current against a flat ≈230 µA for the plain AMOLED — the range being the PMIC and RTC remaining active.
-
-
-### [LilyGO T-Display K230 Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-Charger on the **nRF9151 keyboard base board**. I²C4, shared bus: **`GPIO46` SCL / `GPIO47`
-SDA**, 7-bit address **`0x6B`**. Used by the launcher for charger state and USB/power-source
-status, alongside a [BQ27220](../bq27220/README.md) fuel gauge at `0x55` on the same bus.
-
-The launcher treats the charger as **optional hardware**: "Optional hardware features are shown
-only when the related module is detected. This includes nRF9151, nRF52840, TCA8418, BQ27220,
-BQ25896, XL9555, and AHT20." A bare K230 main board has none of these.
-
-Low-battery shutdown policy lives in the launcher (`battery_low_shutdown_*` in
-`ui_hardware.c`), driven from BQ27220 voltage/SoC readings with the BQ25896's USB-present
-status as a gate — i.e. **the shutdown decision is a software policy in userspace, not a
-hardware cut-off.** Changelog v0.2.3 "set the default low-battery shutdown threshold" and
-v0.2.2 "improved first-run charger, battery, and low-voltage shutdown defaults" show this was
-tuned after release.
-
-## 4. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | `0x6B`, I²C4 on GPIO46/47 |
-| S2 | `k230_launcher/k230_phone_ui/src/ui_hardware.c` | LILYGO | primary | source | same repo | 2026-09-04 | Charger/gauge integration, low-battery shutdown policy |
-| S3 | BQ25896 datasheet | Texas Instruments | primary | datasheet | `https://www.ti.com/lit/ds/symlink/bq25896.pdf` | not retrieved | Electrical specification |
diff --git a/components/texas-instruments/bq27220/README.md b/components/texas-instruments/bq27220/README.md
deleted file mode 100644
index 43502dc..0000000
--- a/components/texas-instruments/bq27220/README.md
+++ /dev/null
@@ -1,164 +0,0 @@
-# Texas Instruments BQ27220 — I²C battery fuel gauge
-
-- **Category:** single-cell Li-ion gas gauge with Impedance Track™.
-- **Manufacturer:** Texas Instruments.
-- **Research status:** ⚠ Identified from **firmware source plus an independent
-  teardown BOM**. No datasheet retrieved in this session.
-- **Retrieved:** 2026-09-04
-
-The battery gauge of the **Xteink X3**, and of the LilyGo T5-S3 boards the same
-SDK supports.
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| I²C address | **0x55** | FreeInk board profile; `XteinkDetect` probe |
-| Bus speed used on the X3 | 400 kHz | board profile |
-| **State of charge** | command register **`0x2C`** | `XteinkDetect.cpp` (`BQ27220_SOC_REG`) |
-| **Voltage** | command register **`0x08`** | `XteinkDetect.cpp` (`BQ27220_VOLT_REG`) |
-| Access model | **TI command registers** | `GaugeType::Bq27220` |
-| **Battery-profile upload** | **NOT required** — *"TI command registers, no profile upload"* | `BoardConfig.h:474-476` |
-| Companion charger | optional; `chargerAddr = 0` on the X3 (**none on this bus**) | board profile |
-
-## 2. Why this part is the family's best battery instrumentation
-
-Three Xteink approaches, worst to best:
-
-| Device | Method | Failure mode |
-|---|---|---|
-| [X4](../../../devices/xteink/x4/features/battery-and-power.md) | Bare **ADC** on GPIO0 with a ÷2 divider | Voltage-curve estimate only; no coulomb counting; cannot see charging |
-| [X4 Pro](../../../devices/xteink/x4-pro/features/battery-and-power.md), X4 Classic | [CW2017](../../cellwise/cw2017/README.md) | **Reports 0 % until an 80-byte BATINFO profile is uploaded**; no current register |
-| **X3** | **BQ27220** | **No profile upload needed.** Impedance Track™ coulomb counting |
-
-The BQ27220 is the **least fragile of the three for a firmware author**: read
-`0x2C`, get a number. That is worth knowing when choosing which Xteink to build a
-project on.
-
-## 3. Its second job: device identification
-
-`XteinkDetect::detectXteinkVerdict()` scores the presence of three parts on the
-C3 boards' secondary I²C bus (**SDA 20 / SCL 0**) to decide whether it is running
-on an X3 or an X4:
-
-| Address | Part | Probe |
-|---|---|---|
-| **0x55** | **BQ27220** | SoC reg `0x2C`, voltage reg `0x08` |
-| 0x68 | [DS-series RTC](../../unidentified/xteink-x3-x4/rtc-ds-series/README.md) | seconds reg `0x00` |
-| 0x6B | [QMI8658](../../qst/qmi8658a/README.md) | `WHO_AM_I` == `0x05` |
-
-Finding them → **X3**. Finding nothing → **X4**. So a missing or mis-addressed
-BQ27220 does not merely break the battery display — it can cause the firmware to
-select the wrong board profile entirely.
-
-## 4. Datasheet
-
-**Not retrieved.** TI publishes `BQ27220` documentation openly at
-`https://www.ti.com/product/BQ27220` (technical reference manual `SLUUBD2`);
-retrieval status `not-attempted` this session. Recorded as an open acquisition —
-this is one of the few chips in the Xteink subject with a **genuinely public,
-authoritative vendor datasheet**, and it should be fetched and hashed.
-
-## 5. Caveats
-
-- The two register numbers above are the only ones the Xteink firmware uses. The
-  BQ27220 has a much larger command set (`Control()`, `RemainingCapacity()`,
-  `StateOfHealth()`, flags) that **no Xteink firmware touches** — including
-  charge/discharge flags that would give charge state without a STAT GPIO.
-- **The gauge's configured chemistry and design capacity were never audited.**
-  The X3's cell is 650 mAh by teardown; whether the gauge is configured for that
-  is unknown.
-- Do not assume BQ27220 register semantics from the BQ27441 or BQ27441-G1 — they
-  differ.
-
----
-
-## Used By
-
-### [Xteink X3](../../../devices/xteink/x3/README.md)
-
-At **0x55** on the secondary I²C bus **SDA 20 / SCL 0 @ 400 kHz**, shared with the
-[DS-series RTC](../../unidentified/xteink-x3-x4/rtc-ds-series/README.md) (0x68)
-and the [QMI8658 IMU](../../qst/qmi8658a/README.md) (0x6B).
-`chargerAddr = 0` — **no charger IC on this bus**, and unlike the S3 boards there
-is also **no charge-STAT GPIO declared**, so how the stock firmware displays
-charging state is **not established**.
-
-Cell: **650 mAh**, connectorised, glued to the back cover (teardown). Charger:
-a [TP4056-class part](../../unidentified/xteink-x3-x4/battery-charger-tp4056-class/README.md).
-
-Corroborated independently by the Chinese teardown BOM: *"TI BQ27220 库仑计"*
-(coulomb counter).
-
-→ [`devices/xteink/x3/features/battery-and-power.md`](../../../devices/xteink/x3/features/battery-and-power.md)
-→ [`devices/xteink/x3/pinouts-and-buses.md`](../../../devices/xteink/x3/pinouts-and-buses.md)
-
-### LilyGo T5-S3 (not documented in this repository)
-
-The same SDK pairs a BQ27220 with a BQ25896 charger at 0x6B on that board.
-Recorded only to show the SDK's `chargerAddr` field has a real user.
-
-### LilyGO T-Display K230 Kit — [`devices/lilygo/t-display-k230`](../../../devices/lilygo/t-display-k230/README.md) · *added 2026-09-07*
-
-On the **nRF9151 keyboard base board**. I²C4: `SDA` ← `GPIO47`, `SCL` ← `GPIO46`, 7-bit address
-**`0x55`**. Shares the bus with a [BQ25896](../bq25896/README.md) charger at `0x6B`, a
-[TCA8418](../tca8418/README.md) at `0x34`, an [XL9555](../../xlsemi/xl9555/README.md) at a probed
-address in `0x20`–`0x27`, and an [AHT20](../../asair/aht20/README.md) at `0x38`.
-
-Cell is a **21700** in the keyboard-base compartment; the 5 V boost that powers the main unit from
-it is enabled by the **nRF52840's `P0.04`**, not by the K230.
-
-Low-battery shutdown is a **userspace policy** (`ui_hardware.c`), not a hardware cut-off: a
-millivolt threshold against the gauge reading, with a confirm count and a recovery log line,
-gated on BQ25896 USB-present. Defaults were tuned post-release in BSP v0.2.2 and v0.2.3.
-
-*Source: `scratch/lilygo-k230/index-fragments.md` §F3.*
-
----
-
-## Datasheet and technical reference manual — retrieved 2026-09-11
-
-The record above stated *"No datasheet retrieved in this session"* and that the
-authoritative vendor datasheet *"should be fetched and hashed"*. **Both the
-datasheet and the technical reference manual have now been fetched, validated
-and retained.**
-
-| | Datasheet | Technical Reference Manual |
-|---|---|---|
-| Local path | [`artifacts/bq27220-datasheet-sluscb7a-rev-a.pdf`](artifacts/bq27220-datasheet-sluscb7a-rev-a.pdf) | [`artifacts/bq27220-technical-reference-manual-sluubd4-rev-a.pdf`](artifacts/bq27220-technical-reference-manual-sluubd4-rev-a.pdf) |
-| **SHA-256** | `9fffe0b632cd287c9210aa1d2e71af1816b31764c11f1b62425de3a4a7cfe5f4` | `44779f229423d649e410439d1d1a3a65026d5919cdd43112ee3a3d8d9811ead9` |
-| **Bytes** | **570,379** | **2,768,446** |
-| Pages | 24 | — |
-| TI literature number | **`SLUSCB7A`** | **`SLUUBD4`** |
-| **Revision** | **Rev. A** — *SLUSCB7A – MARCH 2016 – REVISED APRIL 2016* | **Rev. A** |
-| PDF title | `bq27220 Single-Cell CEDV Fuel Gauge datasheet (Rev. A)` | `BQ27220 Technical Reference Manual (Rev. A)` |
-| PDF `CreationDate` | 2025-11-11 (TI re-renders on request) | — |
-| Source URL | <https://www.ti.com/lit/ds/symlink/bq27220.pdf> | <https://www.ti.com/lit/ug/sluubd4/sluubd4.pdf> |
-| Source class | **primary** | **primary** |
-| Redistribution status | `unknown` — TI literature carries no explicit redistribution grant | same |
-| Disposition | `repository`, **unstaged** | `repository`, **unstaged** |
-
-**Text-layer validated** for both against their rendered page-1 headings
-(*"bq27220 Single-Cell CEDV Fuel Gauge"*, `SLUSCB7A – MARCH 2016 – REVISED APRIL
-2016`; and *"BQ27220 Technical Reference Manual"*).
-
-### A failed guess, preserved
-
-`https://www.ti.com/lit/ug/sluubd2/sluubd2.pdf` was tried first and returned a
-**valid 1,277,976-byte PDF** titled ***"Using the TPS53317AEVM-726"*** — an
-evaluation-module user's guide for an entirely unrelated part. TI's `sluubdN`
-literature numbers are **not** sequential within a product family, and a
-successful HTTP 200 plus a `%PDF` magic number proves nothing about *which*
-document you got. The file was discarded. **Read the PDF title before filing
-anything from `ti.com/lit`.** The correct number is `SLUUBD4`.
-
-### Why the TRM matters more than the datasheet here
-
-The X3's gauge is described in this repository as *"needing no profile upload"*,
-in contrast to the X4 Pro's and X4 Classic's CW2017, which reports 0 % until an
-80-byte BATINFO table is written. The **CEDV** configuration model, the
-`Data Memory` layout and the gauging-parameter defaults that make that true are
-in the **TRM**, not the datasheet. It is now available for the next session to
-audit the FreeInk `BatteryMonitor` code against.
-
-**Used by:** [Xteink X3](../../../devices/xteink/x3/README.md).
diff --git a/components/texas-instruments/bq27220/artifacts/bq27220-datasheet-sluscb7a-rev-a.pdf b/components/texas-instruments/bq27220/artifacts/bq27220-datasheet-sluscb7a-rev-a.pdf
deleted file mode 100644
index 71928df..0000000
Binary files a/components/texas-instruments/bq27220/artifacts/bq27220-datasheet-sluscb7a-rev-a.pdf and /dev/null differ
diff --git a/components/texas-instruments/bq27220/artifacts/bq27220-technical-reference-manual-sluubd4-rev-a.pdf b/components/texas-instruments/bq27220/artifacts/bq27220-technical-reference-manual-sluubd4-rev-a.pdf
deleted file mode 100644
index 7e52c21..0000000
Binary files a/components/texas-instruments/bq27220/artifacts/bq27220-technical-reference-manual-sluubd4-rev-a.pdf and /dev/null differ
diff --git a/components/texas-instruments/cc1101/README.md b/components/texas-instruments/cc1101/README.md
deleted file mode 100644
index b1285f1..0000000
--- a/components/texas-instruments/cc1101/README.md
+++ /dev/null
@@ -1,152 +0,0 @@
-# Texas Instruments CC1101
-
-- **Category:** low-power **sub-1 GHz RF transceiver** (300–348 / 387–464 / 779–928 MHz), SPI
-- **Package as fitted:** **`CC1101RGPR`** — QFN-20 4 × 4 mm, pin 21 = exposed pad
-- **Research status:** vendor-mirrored datasheet held; **register map not decoded** by this
-  pass. What is documented here is the part's role and its integration on the one board in
-  this repository that fits it.
-- **Retrieved:** 2026-09-04
-
-## 1. Identity and capability
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | Texas Instruments | datasheet |
-| Ordering part | **`CC1101RGPR`** (RGP = QFN-20, R = tape and reel) | schematic comment on the Cap CC1101 |
-| Bands | 300–348, 387–464, 779–928 MHz | datasheet / vendor claims |
-| Modulations | **2-FSK, 4-FSK, GFSK, MSK, ASK, OOK** | vendor |
-| Data rate | 0.6 – 600 kbps (silicon); the Cap's example uses **2.4 kbps** | datasheet / vendor example |
-| FIFOs | **64 B TX + 64 B RX**, independent | vendor |
-| Host interface | **4-wire SPI** + `GDO0` / `GDO2` general-purpose digital outputs (`GDO1` doubles as MISO) | datasheet |
-| **Reset** | **no reset pin** — reset is the `SRES` SPI command strobe | datasheet |
-| Reference | external crystal, **26 MHz** typical | as fitted |
-| Bias | external `RBIAS` resistor — **56 kΩ** as fitted | as fitted |
-| RF port | **differential** (`RF_P`, `RF_N`) — needs a balun for a 50 Ω single-ended antenna | as fitted |
-| Output power | quantised set; RadioLib exposes **−30, −20, −15, −10, 0, 5, 7, 10 dBm** | RadioLib / vendor example |
-| ❌ **Cannot do** | **LoRa.** Chirp spread spectrum is Semtech-proprietary and not implemented in any TI sub-GHz part | see §5 |
-
-## 2. `GDO0` and `GDO2` — the pins worth understanding
-
-The CC1101's two general-purpose digital outputs are **software-selected from a large menu**
-of internal signals via `IOCFG0` / `IOCFG2`. Two menu entries matter disproportionately:
-
-| Use | How |
-|---|---|
-| Packet interrupt / sync-word detect | the conventional `GDO0` configuration |
-| **Static logic level** | select **`GDOx_HW_TO_0`** ("hardwired to 0") and then set or clear the **polarity-inversion** bit to emit a constant **0** or **1** |
-
-The second use turns a radio pin into a **free general-purpose output that costs the host no
-GPIO**. The Cap CC1101 spends `GDO2` exactly that way, to drive half of its band-select
-logic. RadioLib exposes the constants as `RADIOLIB_CC1101_GDOX_HW_TO_0`,
-`RADIOLIB_CC1101_GDO2_NORM` and `RADIOLIB_CC1101_GDO2_INV`.
-
-**Cost of the trick:** the pin is only controllable once SPI is up, so anything it drives
-cannot be configured before the radio is initialised.
-
-## 3. What a host must provide
-
-| Resource | Count | Notes |
-|---|---|---|
-| SPI SCK/MOSI/MISO | 3 | shareable with other SPI devices |
-| `CSN` | 1 | dedicated |
-| `GDO0` | 1 | packet interrupt |
-| `GDO2` | 0–1 | optional second interrupt **or** a free static output |
-| Reset GPIO | **0** | there is no reset pin |
-| Crystal | 1 | 26 MHz, 12 pF loads as fitted |
-| `RBIAS` resistor | 1 | not optional — sets internal bias current |
-| Balun + matching | 1 set | differential-to-50 Ω |
-
-## 4. Drivers and libraries
-
-| Library | Notes |
-|---|---|
-| **RadioLib** (jgromes), **MIT** | The driver M5Stack's documentation links to for the Cap CC1101. Same API family as its SX1262 driver, so **one library serves both radios** — a meaningful fact for firmware that already carries RadioLib for LoRa. `new Module(csn, gdo0, RADIOLIB_NC /*rst*/, gdo2)` then `begin(freq, bitrate, freqDev, rxBw, power, preambleLen)` |
-| SmartRF Studio (TI) | Register-set generator; not used by any project in this repository |
-| **M5Stack** | **No M5Stack CC1101 library exists** — `org:m5stack cc1101` returns 0 repositories (2026-09-04, `executed-success`) |
-
-## 5. CC1101 versus LoRa — a recurring confusion
-
-The bands overlap almost exactly (433/868/915 MHz), so buyers repeatedly ask whether a
-CC1101 board can join a LoRa or Meshtastic network. It cannot: LoRa's chirp-spread-spectrum
-PHY is Semtech intellectual property, licensed to a handful of vendors (ST, Microchip, ASR),
-and TI is not among them. A CC1101 and an SX1262 cannot hear each other at all.
-
-## 6. Caveats
-
-- **64-byte FIFOs.** Longer packets require infinite-packet-length mode with mid-transfer
-  FIFO servicing — a classic source of CC1101 bugs.
-- **Band-specific matching.** One CC1101 covers three bands, but one *matching network* does
-  not. Multi-band designs need switched paths (see the Cap CC1101) or accept large losses.
-- **`GDO1` is `MISO`.** Do not configure `IOCFG1` casually.
-- **Legality is per-band and per-region** — 315 MHz is not an EU allocation, 915 MHz is not
-  either. See [`devices/m5stack/cap-cc1101/features/sub-ghz.md` §7](../../../devices/m5stack/cap-cc1101/features/sub-ghz.md).
-
-## 7. Used By
-
-### [M5Stack Cap CC1101 & NFC (U219)](../../../devices/m5stack/cap-cc1101/README.md) — designator `U3`, sheet 3
-
-The only board in this repository fitted with a CC1101.
-
-| Signal | Chip pin | Board net | Host GPIO (Cardputer-Adv) |
-|---|---:|---|---|
-| `SCLK` | 1 | `SPI_SCLK` | **G40** |
-| `MISO` | 2 | `SPI_MISO` | **G39** |
-| `MOSI` | 20 | `SPI_MOSI` | **G14** |
-| `CSN` | 7 | `CC1101_CS` | **G5** |
-| `GDO0` | 6 | `CC1101_G0`, via `R4` **330 Ω** | **G15** |
-| **`GDO2`** | 3 | **`CC1101_RF_SW1`** — stays on the board | — |
-| `RF_P` / `RF_N` | 12 / 13 | via `C46`/`C42` 100 pF → `B1` balun | — |
-| `XOSC_Q1` / `Q2` | 8 / 10 | `Y2` **26 MHz**, `C48`/`C49` 12 pF | — |
-| `RBIAS` | 17 | `R6` **56 kΩ** | — |
-| `DCOUPL` | 5 | local decoupling | — |
-| `AVDD` | 9, 11, 14, 15 | `VDD_3V3`, `C37`–`C41` 100 nF | — |
-| `DVDD` | 4 | `VDD_3V3` | — |
-| `DGUARD` | 18 | — | — |
-| `GND` | 16, 19, EPAD 21 | `GND` | — |
-
-Board-level notes:
-
-- **Shared SPI** with an ST25R3916 NFC front end (`CS` = G6) and the host's microSD
-  (`CS` = G12). The NFC part is driven in **SPI mode 1**; anything using both must
-  re-establish the mode per transaction.
-- **`GDO2` drives band selection**, not an interrupt — see §2 and
-  [the band-switching guide](../../../devices/m5stack/cap-cc1101/features/band-switching.md).
-- The whole board's 3.3 V rail is gated by host **G3** (`POWER_EN`).
-- Vendor claims for the fitted part: **+10 dBm** TX, **−99.5 dBm** RX, ~435–441 m at
-  58 kbps FSK.
-
-### Not fitted elsewhere
-
-M5Stack also sells a **CC1101 Module (M146)**, 855–925 MHz single-band, USD 10.95, published
-2025-11-07 — a **Core-bus** module, not a Cardputer accessory. No record in this repository.
-
-## 8. Related components
-
-- [`components/generic/rf-balun-b0310j50100ahf`](../../generic/rf-balun-b0310j50100ahf/README.md) — the balun on its RF port
-- [`components/infineon/bgs13sn8`](../../infineon/bgs13sn8/README.md) — the SP3T switches it feeds
-- [`components/semtech/sx1262`](../../semtech/sx1262/README.md) — the LoRa part it is *not*
-
-## 9. Local artifacts
-
-| File | Bytes | SHA-256 | Provenance |
-|---|---:|---|---|
-| [`artifacts/cc1101-datasheet-m5stack-mirror.pdf`](artifacts/cc1101-datasheet-m5stack-mirror.pdf) | 2 718 663 | `0c5cdadd06a9f8de6776dda8c8fb29c5029baa2838413335270e223e55a4e169` | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1188/CC1101_Datasheet.pdf`, retrieved 2026-09-04, HTTP 200, `%PDF-1.4` |
-
-⚠ **This is a vendor mirror, and its revision is unverified against TI's own copy.** Note
-the CDN path prefix `/1188/` belongs to the **CC1101 Module (M146)** product, not to the Cap
-CC1101 — M5Stack reuses one upload across products. If precision about a register detail
-matters, fetch TI's `www.ti.com/lit/ds/symlink/cc1101.pdf` and compare hashes; a differing
-hash under the same document name is itself a finding.
-
-Licence/redistribution: **unknown** (TI datasheets carry TI's standard notices). Disposition:
-**repository, unstaged** pending review.
-
-## 10. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| T-1 | CC1101 datasheet | Texas Instruments, mirrored by M5Stack | authorized mirror | datasheet | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1188/CC1101_Datasheet.pdf` | 2026-09-04 | The part |
-| T-2 | Cap CC1101 schematic V0.3 | M5Stack | primary | schematic | held at [`devices/m5stack/cap-cc1101/artifacts/schematic/`](../../../devices/m5stack/cap-cc1101/artifacts/schematic/) | 2026-09-04 | §7 pin table |
-| T-3 | Cap CC1101 Arduino guide | M5Stack | primary | tutorial | `https://docs.m5stack.com/en/arduino/projects/cap/cap_cc1101` | 2026-09-04 | §2 `GDOX_HW_TO_0` trick, §4 RadioLib usage |
-| T-4 | RadioLib | jgromes | primary | repository | `https://github.com/jgromes/RadioLib` | 2026-09-04 | Driver, MIT, rel. 7.7.1 |
-| T-5 | r/CardPuter release thread | community | forum | `https://old.reddit.com/r/CardPuter/comments/1w0nwti/` | 2026-09-04 | §5 — the CC1101-vs-LoRa explanations |
diff --git a/components/texas-instruments/cc1101/artifacts/cc1101-datasheet-m5stack-mirror.pdf b/components/texas-instruments/cc1101/artifacts/cc1101-datasheet-m5stack-mirror.pdf
deleted file mode 100644
index 575b7c5..0000000
Binary files a/components/texas-instruments/cc1101/artifacts/cc1101-datasheet-m5stack-mirror.pdf and /dev/null differ
diff --git a/components/texas-instruments/drv2605/README.md b/components/texas-instruments/drv2605/README.md
index cf49e61..093e9b6 100644
--- a/components/texas-instruments/drv2605/README.md
+++ b/components/texas-instruments/drv2605/README.md
@@ -53,7 +53,7 @@ reacquire, since TI serves only the current revision from the `symlink` path.
 The Waveshare device record previously held its own copy of this document at
 `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/Drv2605.pdf`. It was confirmed
 **byte-identical** to `drv2605-datasheet-slos825-2025-06-02.pdf` (same SHA-256 `bd754913…`, same
-2,478,601 bytes, `cmp` clean). The device-side copy was moved to `archive/` on
+2,478,601 bytes, `cmp` clean). The device-side copy was moved to `../hardware-doc-archive/` on
 2026-08-24; the copy here is canonical. See the placeholder at
 `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/README.md`.
 
diff --git a/components/texas-instruments/tca8418/README.md b/components/texas-instruments/tca8418/README.md
deleted file mode 100644
index 245d78f..0000000
--- a/components/texas-instruments/tca8418/README.md
+++ /dev/null
@@ -1,180 +0,0 @@
-# Texas Instruments TCA8418 — I²C keypad scanner / GPIO expander
-
-> **Exact part on the boards documented here: `TCA8418RTWR`** — 24-pin WQFN (RTW), tape and reel.
-> Record created **2026-09-04** from the M5Stack Cardputer ADV schematic and three independent
-> driver implementations. **No TI datasheet was retrieved in this pass** — see *Gaps*.
-
-## Function
-
-A dedicated **keypad scan and key-event FIFO** controller on I²C. It owns the matrix: it drives
-the columns, senses the rows, debounces, and presents *events* (key down / key up, encoded as a
-single byte) through a 10-deep FIFO, asserting an interrupt when the FIFO is non-empty. Unused
-matrix pins can be repurposed as general GPIO.
-
-The value proposition is pin count. A 56-key matrix costs **ten** MCU GPIOs scanned directly; it
-costs **three** through a TCA8418 (SDA, SCL, INT), two of which are a bus you probably already
-have.
-
-## Key capabilities
-
-| Property | Value | Evidence |
-|---|---|---|
-| Interface | I²C, up to 400 kHz | driver usage |
-| Matrix | up to **8 ROW × 10 COL = 80 keys** | pin complement `ROW0..7`, `COL0..9`, both fully visible on the Cardputer ADV schematic symbol |
-| Event FIFO | 10 deep | Adafruit driver + Bruce comments |
-| Event encoding | one byte: `bit7` = state (1 = press), `bits6..0` = `row × 10 + col + 1` | derived from the vendor decode, below |
-| Interrupt | active-low, open-drain, needs a pull-up | Cardputer ADV fits **3.3 kΩ** |
-| Supply | 3.3 V on both boards seen | schematic |
-| Package | WQFN-24 (RTW) with an exposed pad | schematic symbol has pins 1–24 **plus `EP` (25)** |
-| Reset | active-low `RESET` pin | see the hazard below |
-
-### Event decode
-
-From `M5Cardputer/src/utility/Keyboard/KeyboardReader/TCA8418.cpp:75-85`:
-
-```cpp
-ret.state = eventRaw & 0x80;          // 1 = pressed
-uint16_t buffer = eventRaw & 0x7F;
-buffer--;                             // FIFO encodes 1-based
-ret.row = buffer / 10;                // base 10, not base 8 -- because COL goes to 9
-ret.col = buffer % 10;
-```
-
-The **base-10** arithmetic is the thing to remember: the FIFO packs `(row, col)` as
-`row × 10 + col + 1` because the part supports ten columns. Implementations that assume base 8
-will decode correctly only for `col < 8` on `row 0`.
-
-## Pins seen in use
-
-| Pin | Name | Note |
-|---|---|---|
-| 1–8 | `ROW7`…`ROW0` (descending) | pin 8 is `ROW0` |
-| 9–18 | `COL0`…`COL9` (ascending) | |
-| 19 | `GND` | |
-| 20 | `RESET` | active low |
-| 21 | `VCC` | |
-| 22 | `SDA` | |
-| 23 | `SCL` | |
-| 24 | `INT` | active low, open drain |
-| 25 | `EP` | exposed pad → GND |
-
-Read from the rendered M5Stack Cardputer ADV schematic sheet 2. **This ordering is worth
-checking against TI's datasheet before you lay out a board** — it is a reading of one vendor's
-symbol, and vendor symbols are occasionally wrong.
-
-## Addressing
-
-`0x34` on every board seen here, and it is the Adafruit library's default.
-
-> ⚠ **A community document gets this wrong.** `bmorcelli/Launcher`'s `CardputerADV.md` lists
-> "`0x18`: Likely accelerometer/IMU" and "`0x69`: Likely additional sensor" alongside `0x34`.
-> On the Cardputer ADV, `0x18` is the **ES8311 codec** and `0x69` is the **BMI270**. The `0x34`
-> entry is right.
-
-## Software
-
-| Option | Notes |
-|---|---|
-| **`adafruit/Adafruit TCA8418`** (`^1.0.2`) | the de-facto driver. M5Stack **vendors a modified copy** at `M5Cardputer/src/utility/Adafruit_TCA8418/`; Bruce pulls it from the registry |
-| `M5Cardputer` `TCA8418KeyboardReader` | interrupt-driven wrapper, board-specific remap |
-| Bruce `boards/m5stack-cardputer/interface.cpp` | polling wrapper with key repeat |
-| ESP-IDF | `M5Cardputer-UserDemo` `main/hal/utils/adafruit_tca8418/` |
-
-Minimal initialisation, from the vendor reader:
-
-```cpp
-Adafruit_TCA8418 tca;
-tca.begin(0x34, &Wire1);
-tca.matrix(rows, cols);        // enrol the matrix -- pins NOT enrolled are never scanned
-tca.flush();                   // drain stale events
-tca.enableInterrupts();
-```
-
-Clearing the interrupt (note the read-back — a single write is not enough if events are queued):
-
-```cpp
-tca.writeRegister(TCA8418_REG_INT_STAT, 1);
-if ((tca.readRegister(TCA8418_REG_INT_STAT) & 0x01) == 0) isr_flag = false;
-```
-
-## Driver audit findings
-
-Reading the three implementations side by side, with the caveat that **no datasheet was
-available to check them against**:
-
-* **None of the three touches the GPIO, debounce-configuration, key-lock or GPI-event registers.**
-  Everything uses defaults. The part's debounce behaviour on these boards is therefore whatever
-  TI ships from reset — undocumented in every downstream project.
-* **None reads a device-ID or performs any presence check beyond `begin()` succeeding.** Bruce
-  uses exactly that as its board-detection mechanism, which works but conflates "no TCA8418" with
-  "I²C bus broken".
-* **Bruce polls at ~100 ms** with its own repeat timers (`TCA8418_REPEAT_START_MS 350`,
-  `TCA8418_REPEAT_MS 150`) rather than using `INT`. Perceptibly less responsive on held keys than
-  the vendor library's interrupt path. A deliberate adaptation, not a defect — but a real
-  behavioural difference between firmwares on identical hardware.
-* **`matrix(rows, cols)` is load-bearing and silent.** Pins not enrolled are never scanned and
-  never produce events. A wrong argument produces a partly-working keyboard with no error.
-
-## Used By
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-Designator **U9**. `matrix(7, 8)` — 7 ROW × 8 COL = 56 keys.
-`SDA` ← **G8**, `SCL` ← **G9**, `INT` ← **G11**, all with **3.3 kΩ** pull-ups (R37, R36, R35).
-`COL0..COL7` reach the matrix through **22 Ω 1 %** series resistors R27–R34, and the
-**`COL`→net mapping is reversed**: `COL0 → Y7` … `COL7 → Y0`.
-**`ROW7`, `COL8` and `COL9` are explicit no-connects** (drawn `×`, a positive assertion).
-
-⚠ **`RESET` (pin 20) is tied to +3.3 V through R38 (10 kΩ) and reaches no GPIO.** There is no
-software recovery from a wedged scanner on this board; only a power cycle.
-
-The board's I²C pull-ups on `SDA`/`SCL` are also what **M5GFX uses to identify the ADV**: it
-drives G8/G9 as input-pulldown and tests whether they still read high.
-Full treatment: [`devices/m5stack/cardputer-adv/features/keyboard.md`](../../../devices/m5stack/cardputer-adv/features/keyboard.md).
-
-### M5Stack CardputerZero (C154 / C155) — [`devices/m5stack/cardputer-zero`](../../../devices/m5stack/cardputer-zero/README.md)
-
-Same part, same address `0x34`, on a **Raspberry Pi CM0** host rather than an ESP32-S3.
-**46 keys.** `SDA`/`SCL` on `G2`/`G3` (`I2C1`), `KB_INT` on `G27`.
-Its `RESET` **is** controllable — but indirectly, and it is **shared with the USB hub**:
-`PYG3_KB_HUB_RST` on the M5IOE1 expander resets the TCA8418 **and** the GL852G-OHY60 together.
-That is a better arrangement than the ADV's (recovery is possible) with a caveat (you cannot
-reset the keyboard without also resetting USB).
-
-### LilyGO T-Display K230 Kit — [`devices/lilygo/t-display-k230`](../../../devices/lilygo/t-display-k230/README.md) · *added 2026-09-07*
-
-On the **nRF9151 keyboard base board**, not the main board. I²C4 shared bus:
-`SDA` ← `GPIO47`, `SCL` ← `GPIO46`, 7-bit address **`0x34`**, `RESET` ← `GPIO43`,
-`IRQ` → `GPIO42`. Configured **`matrix(7, 10)`** — 7 ROW × 10 COL — while the launcher draws a
-6 × 11 layout. Code → position is `row = (code-1)/10`, `col = (code-1)%10`.
-
-Registers driven by LilyGO's userspace driver: `CFG 0x01`, `INT_STAT 0x02`, `KEY_LCK_EC 0x03`,
-`KEY_EVENT_A 0x04`, `KP_GPIO_1/2/3 0x1D/0x1E/0x1F`, `DEBOUNCE_DIS_1/2/3 0x29/0x2A/0x2B`.
-Config mode `KE_IEN | OVR_FLOW_IEN | OVR_FLOW_M` with IRQ (default), or `OVR_FLOW_M` with polling.
-
-⚠ **Userspace rewrites the K230 IOMUX register for `GPIO42` directly** (offset `42*4`, value
-`0x00000344`) to force GPIO-input mode, bypassing the kernel pin controller. If another driver
-later re-muxes that pin, the keyboard IRQ stops with no error.
-
-Full key map (60 named keys, two `SPACE` codes, two `FN` keys, a `LILYGO` key and a `MIC` key):
-[`pinouts-and-buses.md` §8](../../../devices/lilygo/t-display-k230/pinouts-and-buses.md#8-keyboard-matrix--full-decode).
-
-*Source: `scratch/lilygo-k230/index-fragments.md` §F2.*
-
-## Substitutes
-
-| Part | Trade-off |
-|---|---|
-| **74HC138 + N sense GPIOs** | what the Cardputer v1.0/v1.1 do. Free and simple; costs 10 GPIOs and CPU time, and gives no debounce or FIFO |
-| Adafruit/Microchip `MCP23017` etc. | a general expander, not a scanner — you still implement scanning and debounce in firmware |
-| `TCA8418E` | the same part in a different package/temperature grade; not seen here |
-| An MCU with enough pins | the honest alternative when pin count is not the constraint |
-
-## Gaps
-
-* **No TI datasheet retrieved.** Register addresses, debounce timing, electrical limits, the
-  official pinout and the GPIO-mode configuration are all **not verified against a primary
-  document** in this pass. Everything above comes from a vendor schematic and three drivers.
-  `https://www.ti.com/product/TCA8418` is the place to start.
-* Pricing, lifecycle status and package variants: **not researched**.
-* The `EP`/pin-25 numbering is as drawn by M5Stack; TI may number it differently.
diff --git a/components/texas-instruments/tps65186/README.md b/components/texas-instruments/tps65186/README.md
index f370ac8..95c991d 100644
--- a/components/texas-instruments/tps65186/README.md
+++ b/components/texas-instruments/tps65186/README.md
@@ -754,7 +754,7 @@ curl -L -o tps65186.pdf           https://www.ti.com/lit/gpn/TPS65186
 
 ### Design files read
 
-All under the knowledge-base root, all read with `devices/soldered-electronics/inkplate-5/tools/kicad_pcb_nets.py` (resolved nets) and `.../tools/parse_kicad_sch.py` (BOM):
+All under ``, all read with `devices/soldered-electronics/inkplate-5/tools/kicad_pcb_nets.py` (resolved nets) and `.../tools/parse_kicad_sch.py` (BOM):
 
 | File | What it established |
 |---|---|
diff --git a/components/ultrachip/README.md b/components/ultrachip/README.md
deleted file mode 100644
index f01bb1f..0000000
--- a/components/ultrachip/README.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# UltraChip (UC) — e-paper display controllers
-
-UltraChip Inc. designs the **UC8xxx** family of electrophoretic display driver
-ICs, ubiquitous in small mono and colour e-paper modules. Parts are usually
-delivered **chip-on-glass or chip-on-film inside a display module**, so they have
-no board reference designator and are identified from the module datasheet, the
-driver source, or a runtime register read.
-
-| Part | Role in this knowledge base |
-|---|---|
-| [`uc8253`](uc8253/README.md) | Xteink X3 (792×528) — original production |
-| [`uc8179`](uc8179/README.md) | Xteink X4 / X4 Pro / X4 Classic (800×480) — newer batches |
-| [`uc8279`](uc8279/README.md) | Xteink X3 (as UC8279d) and X4-family (800×480) — newer batches; also EEGO A4 as UC8279C |
-
-## The family trait that matters most
-
-**UC81xx parts answer `VER (0x70)` and `FLG (0x71)` register reads; the Solomon
-Systech SSD16xx family does not.** That single asymmetry is what makes runtime
-controller detection possible on boards that ship more than one panel variant —
-see [`../solomon-systech/ssd1677/README.md`](../solomon-systech/ssd1677/README.md)
-and the Xteink display guides.
-
-## Sourcing note
-
-UltraChip does not publish a public datasheet portal that this session could
-reach. Every UC8xxx datasheet referenced here is served by a **module vendor
-mirror** (Good Display, Elecrow, Waveshare). Record the mirror, and treat the
-revision as unverified against the chip maker.
diff --git a/components/ultrachip/uc8179/README.md b/components/ultrachip/uc8179/README.md
deleted file mode 100644
index 274b43e..0000000
--- a/components/ultrachip/uc8179/README.md
+++ /dev/null
@@ -1,147 +0,0 @@
-# UltraChip UC8179 — e-paper display controller (800×480 class)
-
-- **Category:** electrophoretic display driver / timing controller.
-- **Manufacturer:** UltraChip Inc.
-- **Research status:** ⚠ **Identified from firmware source and a live register
-  read.** No datasheet retrieved.
-- **Retrieved:** 2026-09-04
-
-The controller found in **newer production batches of the Xteink X4, X4 Pro and
-X4 Classic**, in place of the Solomon Systech SSD1677 the same boards originally
-shipped.
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Function | Mono e-paper timing controller, UC81xx KW command family | FreeInk SDK |
-| Panel | 800 × 480 on these boards | board profiles |
-| Readable ID registers | **`VER (0x70)`** — reserved `0x00`, `CHIP_VER`, 24-bit `LUT_VER`; **`FLG (0x71)`** status, `BUSY_N` = D0 | `XteinkDetect.cpp` |
-| Bulk MTP read | **`RMTP (0xA2)`** — 1 dummy byte then MTP[0..n]; `0xA5` at byte 0 indicates a programmed MTP | `XteinkDetect.cpp` |
-| `LUT_VER` value | **`0x01`** per the vendor reference | `XteinkDetect.cpp:373-390` |
-| **Observed on a shipping X4 Pro** | **`VER = 00 00 01 FF FF`, `FLG = 0x13`** | FreeInk SDK, firsthand |
-| Serial write clock used | 20 MHz on Xteink boards | board profiles |
-| NVS `screenType` code | **1**, or **0x0B** | `XteinkDetect.cpp` |
-
-## 2. The `CHIP_VER = 0x00` finding — a preserved negative result
-
-An earlier version of the FreeInk matcher required `ver[1] != 0`, on the
-reasonable assumption that `CHIP_VER` would carry the datasheet default. A
-**shipping X4 Pro carrying a UC8179 returned `CHIP_VER = 0x00`** and was wrongly
-rejected, falling back to the SSD1677 driver and producing a blank panel.
-
-The matcher now deliberately **pins no specific `CHIP_VER` value**:
-
-```c
-// XteinkDetect.cpp:113-119
-bool matchUc81xx(const uint8_t ver[5], uint8_t flg) {
-  if (flg == 0x00 || flg == 0xFF) return false;   // floating bus
-  if ((flg & 0x01) != 0x01) return false;         // BUSY_N must be idle
-  return !verIsFloating(ver);                     // VER must be driven
-}
-```
-
-**Do not reintroduce a `CHIP_VER` equality check.** This is the most reusable
-lesson in the UC81xx records here.
-
-## 3. Datasheet
-
-**Not retrieved.** No UltraChip public portal was located; module-vendor mirrors
-(Good Display, Waveshare) are the usual route. Recorded as an open acquisition.
-
-## 4. Caveats
-
-- **`VER`/`FLG` readability is the whole basis of controller auto-detection.** It
-  requires a bus where the host can release its data line to input mid-transaction
-  — which the **Xteink X4 Classic cannot do** (no MISO, and its bus geometry
-  prevents the half-duplex read). On that board, NVS is the only source of truth.
-- `LUT_VER` `0x01` distinguishes it from the UC8279's `0x02`/`0x68`/`0x69`.
-  **Anything unrecognised falls back to UC8179**, on the empirical grounds that it
-  is *"the variant every unit benched so far has carried"*.
-
----
-
-## Used By
-
-### [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md) — newer batches
-
-Alternative to the SSD1677 on identical wiring
-(SCLK 12 / MOSI 11 / CS 13 / DC 18 / RST 14 / BUSY 6). Selected at boot by the
-`VER`/`FLG` probe. **Observed on real hardware returning `VER = 00 00 01 FF FF`.**
-→ [`devices/xteink/x4-pro/features/display.md`](../../../devices/xteink/x4-pro/features/display.md)
-
-### [Xteink X4](../../../devices/xteink/x4/README.md) — newer batches
-
-Same role, on the C3 board's pins
-(SCLK 8 / MOSI 10 / CS 21 / DC 4 / RST 5 / BUSY 6).
-→ [`devices/xteink/x4/features/display.md`](../../../devices/xteink/x4/features/display.md)
-
-### [Xteink X4 Classic](../../../devices/xteink/x4-classic/README.md) — batch-dependent
-
-**Cannot be probed on this board** — the X4C display bus has no MISO, so `VER`
-always floats to `0xFF`. Selected instead from NVS `hw_calib/screenType` = **1**
-or **0x0B**. This makes cross-unit full-flash restores hazardous on the X4C.
-→ [`devices/xteink/x4-classic/README.md`](../../../devices/xteink/x4-classic/README.md)
-
-## See also
-
-[`../uc8279/README.md`](../uc8279/README.md) ·
-[`../../solomon-systech/ssd1677/README.md`](../../solomon-systech/ssd1677/README.md) —
-the part it substitutes for · [`../README.md`](../README.md)
-
----
-
-## Datasheet — obtained 2026-09-11
-
-The record above stated *"No datasheet retrieved."* **One has now been obtained,
-validated and retained.**
-
-| Field | Value |
-|---|---|
-| Local path | [`artifacts/uc8179c-c-datasheet-rev0.6-2019-11-26-crystalfontz-mirror.pdf`](artifacts/uc8179c-c-datasheet-rev0.6-2019-11-26-crystalfontz-mirror.pdf) |
-| **SHA-256** | `bf1dcef76e0d02a5683814e5f2b525bb7079e57509bf9a0754235b24fa587f50` |
-| **Bytes** | **1,202,516** |
-| Pages | **81**, A4 |
-| Source URL | <https://www.crystalfontz.com/controllers/UltraChip/UC8179/517/> |
-| Source class | **credible mirror** — Crystalfontz is a display distributor, not UltraChip |
-| Retrieved | **2026-09-11**, HTTP 200, magic bytes `%PDF` |
-| **Document title (PDF metadata)** | `03-DTS-1664  UC8179c_Ｃ0.6 for__TFT_Module_Use_only` (note the full-width `Ｃ`) |
-| **IC version** | **`c_C`** |
-| **Datasheet revision** | **0.6**, dated **November 26, 2019** |
-| PDF `CreationDate` | 2019-12-05 00:13:59 |
-| PDF author / producer | `cindy.lu` / PDFCreator 2.5.3.6324 |
-| Redistribution status | **`conditional` / `unknown`** — cover marked ***"for TFT Module Use Only"*** |
-| Disposition | `repository`, **unstaged** |
-
-**Text-layer validated** against the rendered page-1 heading
-(*"HIGH-VOLTAGE MIXED-SIGNAL IC"*, *"IC Version: c_C"*,
-*"Datasheet Revision: 0.6 (for_TFT_Module_Use_Only) November 26, 2019"*).
-
-### This is the `c_C` silicon — and that matters for the Xteink boards
-
-The FreeInk driver's notes refer to *"the UC8179c table"* when interpreting the
-PLL (`0x30`) register. **This document is that part.** The X4 Pro, X4 Classic and
-X4 all ship UC8179 in some production batches; whether they ship `c_C`
-specifically is **not established** — no top marking has been read off any
-Xteink board, because the only public board photographs are the FCC internal
-photos of the X3 and X4, which have not been read at that level of detail.
-
-### How it was found — a trap worth recording
-
-`https://www.crystalfontz.com/controllers/UltraChip/UC8179/478/` returns a
-**valid 477 KB PDF**, and it is **the GOODiX GT911 Programming Guide**. The
-`UC8179` path segment is decorative; only the trailing number selects a document.
-The correct id is `517`, read from the page's own
-`datasheet-viewer.php?id=517` link. `datasheet-viewer.php?id=517` itself returns
-HTML, not the PDF — the working form is the trailing-number path.
-
-**Validating by magic bytes alone would have filed a touch-controller manual as a
-display-controller datasheet.** Always check the PDF's own title.
-
-Crystalfontz carries only **UC8151** (id 511) and **UC8179** (id 517) from
-UltraChip. It does **not** carry UC8253 or UC8279.
-
-**Used by:** [Xteink X4](../../../devices/xteink/x4/README.md) ·
-[X4 Pro](../../../devices/xteink/x4-pro/README.md) ·
-[X4 Classic](../../../devices/xteink/x4-classic/README.md) — all three as one of
-three batch-dependent controller options.
diff --git a/components/ultrachip/uc8179/artifacts/uc8179c-c-datasheet-rev0.6-2019-11-26-crystalfontz-mirror.pdf b/components/ultrachip/uc8179/artifacts/uc8179c-c-datasheet-rev0.6-2019-11-26-crystalfontz-mirror.pdf
deleted file mode 100644
index 4343900..0000000
Binary files a/components/ultrachip/uc8179/artifacts/uc8179c-c-datasheet-rev0.6-2019-11-26-crystalfontz-mirror.pdf and /dev/null differ
diff --git a/components/ultrachip/uc8253/README.md b/components/ultrachip/uc8253/README.md
deleted file mode 100644
index 80a1545..0000000
--- a/components/ultrachip/uc8253/README.md
+++ /dev/null
@@ -1,139 +0,0 @@
-# UltraChip UC8253 — e-paper display controller
-
-- **Category:** electrophoretic (e-paper) display driver / timing controller.
-- **Manufacturer:** UltraChip Inc.
-- **Research status:** ⚠ **Identified from firmware and driver source only.** No
-  datasheet was retrieved in this session; the specification below is what the
-  FreeInk SDK cites and implements.
-- **Retrieved:** 2026-09-04
-
-The panel controller of the **original-production Xteink X3**.
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Function | Mono e-paper timing controller, KW (black/white) mode | driver source |
-| Interface | 4-wire SPI, write-oriented | driver source |
-| **Max serial write clock** | **20 MHz** — *"Clock rate up to 20 MHz"*, serial write timing `TSCYCW` | UC8253 datasheet, cited by FreeInk SDK |
-| Mode used | `PSR KW/R = 1`: 1 bpp, `DTM1` = OLD plane, `DTM2` = NEW plane, **differential refresh** | `Uc8253Driver` |
-| Command set | `PSR`, `PON`, `POF`, `DTM1 0x10`, `DSP 0x11`, `DRF 0x12`, `DTM2 0x13`, `CDI 0x50`, `TRES 0x61`, `DSLP 0x07`+`0xA5` | driver source |
-| Waveforms | The X3 driver carries **six tuned custom banks**, in the UC8253's **43-byte LUT format** | `docs/xteink-x3-uc8279-support.md` |
-| Grayscale | **Supported** on this part — the X3 reader's **4-level anti-aliasing** path uses it | same |
-| **`VER (0x70)` behaviour** | **UNKNOWN.** See §3 | same, marked `Pending` |
-
-## 2. Datasheet
-
-**Not retrieved.** The FreeInk SDK cites:
-
-`https://www.elecrow.com/download/product/DIE01237S/UC8253_Datasheet.pdf`
-
-— an **Elecrow mirror**, not an UltraChip-hosted document. No UltraChip public
-portal was located. Retrieval status: `not-attempted` this session; recorded so a
-future pass can fetch and hash it. Expect the usual mirror caveat: the revision a
-module vendor serves may lag the chip maker's.
-
-## 3. The open question about `0x70`
-
-The Xteink X3 boot probe distinguishes UC8253 from UC8279d by issuing `VER (0x70)`
-and checking for a structured, non-floating reply. It works — but the FreeInk
-maintainers flag an assumption they have not tested:
-
-> "**Pending:** what the UC8253 actually answers to `0x70` (UC815x-family REV
-> places the revision in the first byte, which the matcher relies on)…"
-
-So the detection is **empirically reliable and theoretically unverified**. If a
-UC8253 ever answers `0x70` with a driven, structured byte pattern, the matcher
-would misidentify it as an UltraChip sibling. Recorded as a live risk, not a
-defect.
-
-## 4. Caveats and unsafe assumptions
-
-- **Its LUT format is incompatible with the UC8279's.** UC8253 uses 43-byte LUTs;
-  the UC8279 uses **group-based** 7-byte groups, 7 groups per LUT in KW mode.
-  Tuned waveform banks **cannot be copied between them**, despite a nearly
-  identical command set. This is the single most expensive trap in porting between
-  the two.
-- Do not assume grayscale carries over to the UC8279 — it does not, yet.
-
----
-
-## Used By
-
-### [Xteink X3](../../../devices/xteink/x3/README.md) — original production run
-
-Chip-on-glass inside the 3.7″ 792×528 module; **no board reference designator**.
-Driven by the ESP32-C3 over the SPI bus it **shares with the microSD card**:
-
-| Controller signal | X3 GPIO |
-|---|---:|
-| SCLK | 8 |
-| SDA (MOSI) | 10 |
-| CS | 21 |
-| DC | 4 |
-| RST | 5 |
-| BUSY | 6 |
-
-`displaySpiHz` = **20 MHz** (datasheet maximum). A prior fork ran 16 MHz;
-20 MHz is in-spec and ~25 % faster on plane writes.
-
-Selected at boot: if the display-bus probe does **not** find an UltraChip
-`VER`/`FLG` signature, the SDK conservatively resolves to this part.
-
-→ [`devices/xteink/x3/features/display.md`](../../../devices/xteink/x3/features/display.md)
-→ [`devices/xteink/x3/pinouts-and-buses.md`](../../../devices/xteink/x3/pinouts-and-buses.md)
-
-## See also
-
-[`../uc8279/README.md`](../uc8279/README.md) — the part that replaced it in
-~July 2026 production · [`../README.md`](../README.md)
-
----
-
-## Datasheet — retrieved 2026-09-11
-
-The record above listed `https://www.elecrow.com/download/product/DIE01237S/UC8253_Datasheet.pdf`
-with retrieval status `not-attempted`. **It has now been fetched, validated and
-retained.**
-
-| Field | Value |
-|---|---|
-| Local path | [`artifacts/uc8253c-a-datasheet-rev0.6-2020-10-13-elecrow-mirror.pdf`](artifacts/uc8253c-a-datasheet-rev0.6-2020-10-13-elecrow-mirror.pdf) |
-| **SHA-256** | `bee25538177b8cc6f67c1ffe696d8fd09bda7842b42e021fb9bd41a3da91c125` |
-| **Bytes** | **1,294,916** |
-| Pages | **75**, A4 (595 × 842 pt) |
-| Source URL | <https://www.elecrow.com/download/product/DIE01237S/UC8253_Datasheet.pdf> |
-| Source class | **credible mirror** — Elecrow is a module vendor, not UltraChip |
-| Retrieved | **2026-09-11**, HTTP 200, magic bytes `%PDF` |
-| **Document title (PDF metadata)** | `03-DTS-1891 UC8253c_A0.6 for TFT module use only` |
-| **IC version** | **`c_A`** |
-| **Datasheet revision** | **0.6**, dated **October 13, 2020** |
-| PDF `CreationDate` | 2020-10-20 21:43:51 |
-| PDF author / producer | `matthew.lin` / PDFCreator Free 3.5.1 |
-| Cover text | *"HIGH-VOLTAGE MIXED-SIGNAL IC — All-in-one driver IC w/ Timing Controller for White/Black/Red Dot-Matrix Micro-Cup ESL"* |
-| Redistribution status | **`conditional` / `unknown`** — the cover is marked ***"for TFT module use only"***, which is a use restriction of unclear scope, not a licence |
-| Disposition | `repository`, **unstaged** |
-
-**Text-layer validation performed.** `pdftotext -layout` on page 1 returns the
-same heading visible in the rendered page (*"HIGH-VOLTAGE MIXED-SIGNAL IC"*,
-*"IC Version: c_A"*, *"Datasheet Revision: 0.6 … Oct 13, 2020"*). No value has
-been transcribed from an unvalidated text layer.
-
-### Two things the metadata tells you that the content does not
-
-1. **This is the `c_A` silicon**, not an unqualified "UC8253". UltraChip's
-   internal document number is `03-DTS-1891`. If the X3's fitted part is a
-   different sub-revision, register defaults may differ.
-2. **It was exported by a named UltraChip employee with a consumer PDF tool in
-   October 2020** and has circulated through module vendors ever since. **There is
-   no UltraChip customer portal**; this is the distribution channel.
-
-### Relationship to the UC8179 datasheet now held
-
-[`../uc8179/`](../uc8179/README.md) holds `03-DTS-1664 UC8179c_C0.6`, from a
-different mirror. The two share a document template, a revision number (0.6), a
-cover, and the *"for TFT module use only"* marking — they are siblings from one
-document family. **They are different parts and different documents**; the shared
-`0.6` is a coincidence of UltraChip's numbering, not a common revision.
-
-**Used by:** [Xteink X3](../../../devices/xteink/x3/README.md).
diff --git a/components/ultrachip/uc8253/artifacts/uc8253c-a-datasheet-rev0.6-2020-10-13-elecrow-mirror.pdf b/components/ultrachip/uc8253/artifacts/uc8253c-a-datasheet-rev0.6-2020-10-13-elecrow-mirror.pdf
deleted file mode 100644
index 8f8a524..0000000
Binary files a/components/ultrachip/uc8253/artifacts/uc8253c-a-datasheet-rev0.6-2020-10-13-elecrow-mirror.pdf and /dev/null differ
diff --git a/components/ultrachip/uc8279/README.md b/components/ultrachip/uc8279/README.md
deleted file mode 100644
index 2b3e20c..0000000
--- a/components/ultrachip/uc8279/README.md
+++ /dev/null
@@ -1,181 +0,0 @@
-# UltraChip UC8279 (and UC8279d, UC8279C) — e-paper display controller
-
-- **Category:** electrophoretic display driver / timing controller.
-- **Manufacturer:** UltraChip Inc.
-- **Research status:** ⚠ Driver written **from a datasheet the FreeInk authors
-  hold**, not retrieved here. **Never validated on X3 hardware.**
-- **Retrieved:** 2026-09-04
-
-Three closely-related variants appear in this knowledge base:
-
-| Variant | Where | `LUT_VER` | NVS `screenType` |
-|---|---|---|---|
-| **UC8279** (800×480) | Xteink X4 / X4 Pro / X4 Classic, newer batches | `0x02`, `0x68` | 2 or 0x0C |
-| **UC8279** reserved | — | `0x69` | — |
-| **UC8279d** ("d_B" silicon) | **Xteink X3**, production from ~July 2026 | — | — |
-| **UC8279C** | EEGO A4 768×552 (`Uc8279cA4Driver`) | — | — |
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Mode used | `PSR KW/R = 1` — 1 bpp, `DTM1` = OLD, `DTM2` = NEW, differential refresh | `Uc8279Driver` |
-| Command set | Near-identical to the UC8253: `PSR`/`PON`/`POF`, `DTM1 0x10`, `DSP 0x11`, `DRF 0x12`, `DTM2 0x13`, `CDI 0x50`, `TRES 0x61`, `DSLP 0x07`+`0xA5` | driver source |
-| **LUT format** | **Group-based: 7-byte groups, 7 groups per LUT in KW mode** — **NOT** the UC8253's 43-byte format | `docs/xteink-x3-uc8279-support.md` |
-| Serial write clock | **20 MHz** — *"Clock rate up to 20 MHz"* | datasheet, cited |
-| Readable IDs | `VER 0x70` (reserved `0x00`, `CHIP_VER` default `0x03`, 24-bit `LUT_VER`), `FLG 0x71`, `RMTP 0xA2` | `XteinkDetect.cpp` |
-| **OTP waveforms** | **4K MTP carrying 12 temperature-range LUT sets**, each with its own frame rate and rail voltages | `docs/xteink-x3-uc8279-support.md` |
-| **`TS_AUTO`** | **Re-senses temperature before every booster enable** — PWR/PLL/VDCS stay at silicon defaults and every refresh is temperature-compensated *by the controller* | same |
-| `CDI` default | SDK drives the border white each refresh (`0x97`); the **datasheet default is `0xD7`**, which floats it | same |
-| Datasheet held by SDK authors | **UC8279d_B rev 0.1, dated December 2025** | same |
-
-## 2. Features present in silicon but not wired up
-
-Documented by the FreeInk authors as available and unused:
-
-| Command | Capability | Why it might matter |
-|---|---|---|
-| **`AUTO (0x17)`** | `PON → DRF → POF (→ DSLP)` as a **single command** | Removes host round-trips on sleepy, ESL-style periodic updates — a real power win for always-on dashboards |
-| **`PBC (0x44)`** | Panel-break check via the CHKGI/CHKGO wire loop | Only if the module bonds the loop out |
-| **`CRC (0x72)`** | MTP integrity check over `0x000–0xFFF` | Field diagnosis of a corrupted waveform store |
-| **`TSC (0x40)`** | On-chip temperature readback | Free ambient temperature for a consumer that wants it |
-
-## 3. What does **not** work yet, and why
-
-**On the Xteink X3, this driver has never run on a physical device.** Quoted:
-
-> "Everything below is written from the UC8279d_B 0.1 datasheet (Dec 2025) and is
-> **Pending hardware validation — no UC8279 X3 unit has been on the bench yet.**"
-
-Consequences, all still open:
-
-- **Full / Half / Fast all run the same OTP waveform**, so a page turn is likely a
-  full GC-style flash. Fast modes need custom register banks (`REG = 1`,
-  commands `0x20`–`0x24`).
-- **The X3's six tuned UC8253 banks cannot be ported** — different LUT format
-  (see §1). This is a rewrite, not a copy, despite the near-identical command set.
-- **No grayscale** (`supportsStripGrayscale()` false). The X3 reader's 4-level
-  anti-aliasing path needs UC8279-format gray banks tuned on hardware.
-- `TRES` is programmed 792×528 on the X3, but the UC8253 init programs
-  **VRES = 600** (the OEM scans the full gate count). If the image is offset or
-  compressed, the SDK suggests trying `0x02 0x58`.
-
-The only project observed working this problem is
-[`anki630/crossmosa-freeink-sdk`](https://github.com/anki630/crossmosa-freeink-sdk)
-— *"UC8279 waveform tuning"*.
-
-## 4. Datasheet
-
-**Not retrieved.** The SDK authors cite **UC8279d_B 0.1 (December 2025)**; no
-public URL was located. Recorded as an open acquisition — this is the single most
-valuable missing document in the Xteink subject, because it is the only thing
-standing between the X3's newer panel and working fast waveforms.
-
----
-
-## Used By
-
-### [Xteink X3](../../../devices/xteink/x3/README.md) — production from ~July 2026 (as **UC8279d**)
-
-Same board, same 792×528 glass, same pinout as the UC8253 units; **only the
-controller changes**. Profile `BoardConfig::XTEINK_X3_UC8279`. Selected at boot
-by `detectX3DisplayController()`, which bit-bangs a half-duplex read on
-SCLK 8 / SDA 10 / CS 21 / DC 4 / RST 5 / BUSY 6 and requires **two passes agreeing
-byte-for-byte**.
-
-The vendor gave the community advance notice of this switch — the only
-pre-announced silent hardware change found in the family. Owners report a
-**user-visible difference**: one X3 has *"slightly whiter background and clearer
-text… page turns and menus seem slower"*, the other *"slightly darker background
-and not as clear text… page turns and menus seem faster"*
-([r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/), 2026-08-10,
-firsthand side-by-side comparison — **which unit is which controller is not
-established**).
-
-→ [`devices/xteink/x3/features/display.md`](../../../devices/xteink/x3/features/display.md)
-
-### [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md) / [X4](../../../devices/xteink/x4/README.md) — newer batches (800×480)
-
-Alternative to SSD1677/UC8179 on identical wiring. Distinguished from the UC8179
-by `LUT_VER` ∈ {`0x02`, `0x68`, `0x69`}.
-
-### [Xteink X4 Classic](../../../devices/xteink/x4-classic/README.md) — batch-dependent
-
-Selected from NVS `hw_calib/screenType` = **2** or **0x0C**; **the bus cannot be
-probed** on that board.
-
-### EEGO A4 (as **UC8279C**, 768×552)
-
-Not documented in this repository; recorded because the same SDK carries
-`Uc8279cA4Driver` and it establishes the variant exists.
-
-## See also
-
-[`../uc8253/README.md`](../uc8253/README.md) — the part it replaces on the X3 ·
-[`../uc8179/README.md`](../uc8179/README.md) — its 800×480 sibling ·
-[`../README.md`](../README.md)
-
----
-
-## Datasheet — **not obtained**, 2026-09-11. What was tried, and what would work.
-
-The record above notes that the FreeInk authors hold **UC8279d_B rev 0.1, dated
-December 2025** and wrote their driver from it. **That document was not located
-publicly by this pass, and neither was any other UC8279 datasheet.**
-
-### Attempts, all failed
-
-| Source tried | Result |
-|---|---|
-| `crystalfontz.com/controllers/UltraChip/` | **Carries only UC8151 and UC8179.** The full controller index contains no other `UC82xx` |
-| Crystalfontz document-id probe, ids 512–523 via the working trailing-number path | Returned FocalTech, D-FT3267, SSD1780, ST7567S/A, CH13620 and Hynitron CST816D — **no UC8279** |
-| `buydisplay.com/download/ic/UC8279.pdf` | **403** |
-| `good-display.com` product path, `v4.cecdn.yun300.cn` CDN | **403** / HTML |
-| `e-paper-display.com`, `e-paper-display.cn` | **404** |
-| `waveshare.com` / `waveshare.net` / `files.waveshare.com` wiki upload paths | 403 / 404 / HTML |
-| GitHub code search `filename:UC8279 extension:pdf` | **`total_count: 0`** |
-| **LCSC** `wmsc.lcsc.com/ftps/wm/search/global` | **403 on every UA tried** (Chrome, WhatsApp, ClaudeBot). `www.lcsc.com/search` HTML returns 200 but was not mined further |
-| DuckDuckGo HTML endpoint | **HTTP 202 bot-check page**, no results, on four queries |
-| `alldatasheet.com` | **403** |
-
-### Honest status
-
-**UltraChip publishes nothing.** There is no customer portal, no product page and
-no public datasheet index. Every UltraChip document in circulation — including
-the two now held in this repository for the [UC8253](../uc8253/README.md) and
-[UC8179](../uc8179/README.md) — is a **PDF exported by a named UltraChip employee
-with a consumer tool, stamped *"for TFT module use only"*, that leaked through a
-module vendor or a distributor.** UC8279 is a 2025-era part; it has not leaked
-yet, or not to a host reachable from here.
-
-**This is a genuine unavailability, not a failed search.** Record it as such and
-do not re-run the same twelve attempts.
-
-### What would actually work, in order of likely success
-
-1. **A Chinese module vendor's download page.** DKE, Good Display / 大连佳显,
-   微雪 (Waveshare CN), 中景园, and Elecrow all publish controller PDFs beside the
-   panels that use them — **Elecrow is where this repository's UC8253 came from**.
-   Search in Chinese: `UC8279 规格书`, `UC8279 数据手册`, `UC8279d`.
-2. **LCSC via the HTML storefront** (`https://www.lcsc.com/search?q=UC8279`) with
-   UA `WhatsApp/2.23.20.0`, which returns 200 where the JSON API returns 403.
-   LCSC serves datasheets from `datasheet.lcsc.com/lcsc/<id>.pdf`.
-3. **Ask the FreeInk authors.** They hold `UC8279d_B 0.1 (Dec 2025)` and cite it
-   openly in `Uc8279X4Driver.cpp`. A GitHub issue is the cheapest route to the
-   exact document the drivers were written against.
-4. **The EEGO Reader A4**, which the FreeInk SDK now supports, uses a
-   **UC8279C** — a different sub-revision — and its vendor may publish more.
-
-### Why it matters more than usual here
-
-The UC8279 is the controller actually fitted to at least one shipping X4 Pro
-(`hw_calib/screenType = 2`, `VER = 00 0F 68 00 00`, LUT_VER `0x68`), and the
-FreeInk driver's own comments record that **the family datasheet's 6-byte LUT
-groups do not fit the tables this part uses** — a 7-byte reading is required, and
-the tail byte's role is unknown. That is precisely the kind of question only the
-correct revision of the datasheet answers.
-
-**Used by:** [Xteink X3](../../../devices/xteink/x3/README.md) (UC8279d) ·
-[X4](../../../devices/xteink/x4/README.md) ·
-[X4 Pro](../../../devices/xteink/x4-pro/README.md) ·
-[X4 Classic](../../../devices/xteink/x4-classic/README.md).
diff --git a/components/unidentified/cardputer/lp3218dt1g/README.md b/components/unidentified/cardputer/lp3218dt1g/README.md
deleted file mode 100644
index d41ffa2..0000000
--- a/components/unidentified/cardputer/lp3218dt1g/README.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# `LP3218DT1G` — power-path MOSFET (manufacturer unidentified)
-
-> **This is an unidentified part.** `LP3218DT1G` is the value string read from the M5Stack
-> Cardputer schematics; **the manufacturer has not been established** and no datasheet was
-> located. Scoped to the Cardputer family rather than filed under a guessed vendor, per the
-> research skill's rule for unidentified parts.
-> Record created **2026-09-04**.
-
-## What is actually known
-
-| Fact | Evidence | Confidence |
-|---|---|---|
-| The value string is exactly `LP3218DT1G` | appears three times on Cardputer ADV schematic sheet 1 and on the v1.0/v1.1 shared schematic | **high** — read from a rendered sheet crop, not only from the text layer |
-| Three are fitted, designators **Q1, Q2, Q3** | designator census, all four ADV sheets | **high** |
-| They sit in the **battery power path** | Q1 between `VBAT_IN` and the charger/supervisor block; Q2 and Q3 between `BAT+` and `VBAT_OUT` | **high** |
-| The symbol is a **P-channel MOSFET with a body diode**, drawn source-up in a high-side load-switch configuration | rendered crop of sheet 1 | **medium** — read from the symbol, which is a vendor drawing |
-| Gate network involves R7 100 kΩ and the CN809J's `RESET` output | rendered crop | **medium** |
-
-## What is not known
-
-* **Manufacturer.** The `DT1G` suffix is an **ON Semiconductor / onsemi packaging convention**
-  (`D` = SOT-223-class or dual, `T1G` = tape-and-reel, green), which is suggestive but is used by
-  several vendors and by second sources copying the convention. `LP3218` itself does not resolve
-  to an onsemi part in any source located in this pass.
-* Voltage and current ratings, `R_DS(on)`, gate threshold, package.
-* Whether all three are the same channel type.
-
-## Why it is recorded rather than guessed
-
-The skill is explicit that a candidate must never be promoted to a finding, and that a part
-number differing by one character from a real part on a different board is a common trap.
-`LP3218` is close enough to several real part numbers (`LP3218`, `LP3210`, `AO3401`-class
-alternatives) that guessing would be worse than saying nothing.
-
-**What would settle it:** a photograph of the Cardputer mainboard showing Q1–Q3's top marking, or
-a BOM. Neither is published.
-
-## Used By
-
-### M5Stack Cardputer ADV (K132-Adv) — [`devices/m5stack/cardputer-adv`](../../../../devices/m5stack/cardputer-adv/README.md)
-
-**Q1, Q2, Q3** on schematic sheet 1.
-
-* **Q1** sits between `VBAT_IN` and the downstream rail, gated from the network that includes the
-  **CN809J** supervisor's `RESET` output and R7 (100 kΩ). This is the classic arrangement for
-  "hold the load off until the supply is good".
-* **Q2** and **Q3** sit between the battery connector `J8` (`BAT+`/`BAT-`) and `VBAT_OUT`,
-  back-to-back — the usual way to make a bidirectional switch out of two MOSFETs whose body
-  diodes would otherwise conduct.
-
-Together with `D1`/`D2` (`SS34` Schottky) from `+5VIN`, this is the board's **power path**:
-it selects between USB and battery, and prevents the battery back-feeding USB.
-
-**Firmware relevance: none directly** — no GPIO reaches these gates. They matter because they
-determine what happens when USB is inserted or removed under load, and they are part of the
-circuit that makes M5Stack's *"switch the power to ON to charge"* instruction necessary.
-
-### M5Stack Cardputer v1.0 (K132) and v1.1 (K132-V11)
-
-[`devices/m5stack/cardputer-v1.0`](../../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../../devices/m5stack/cardputer-v1.1/README.md)
-
-Same three designators, same value string, on the shared schematic (SHA-256 `6016c1fe…`). Part
-of the power train that is **carried over unchanged** across all three Cardputer generations.
-
-## If you are replacing one
-
-Do **not** substitute from this record — it does not contain a rating. Read the part off the
-board, or choose a P-channel MOSFET rated well above 5 V with low `R_DS(on)` at 2.5 V gate drive
-and a package that fits, and verify the body-diode orientation matches the original.
-
-## Resolution path
-
-1. Board photograph of Q1–Q3 top marking (highest value, lowest effort).
-2. `github.com/m5stack/M5_Hardware` — no BOM was found for `K132-Adv` in this pass, but only the
-   `Structures` directory was ever linked; the repository was not walked.
-3. Ask M5Stack support.
diff --git a/components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md b/components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md
deleted file mode 100644
index 0c0499a..0000000
--- a/components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md
+++ /dev/null
@@ -1,205 +0,0 @@
-# Unidentified — `AXPM65611` / `65b311` (LilyGO T-Display-S3 family)
-
-- **Category:** unidentified. Two related-looking strings appear across the family; whether they
-  are one part, two parts, or unrelated is **not established**.
-- **Manufacturer:** **unknown.**
-- **Scope:** deliberately scoped to the LilyGO T-Display-S3 family, per the repository
-  convention for unidentified parts, so it cannot collide with other unknowns.
-- **Retrieved:** 2026-09-07
-
-## What is actually known
-
-### String A — `AXPM65611`, from LilyGO schematics
-
-Recovered from the designator/part text layer of **two** published schematics:
-
-| Board | Designator | Adjacent pin label | Sheet |
-|---|---|---|---|
-| T-Display-S3 AMOLED (Touch sheet) | `U5` | `VIN`, pin 12 | `T-Display-S3-AMOLED-Touch.pdf` @ `6d1dc00` |
-| T-Display-S3 AMOLED Plus | `U4` | `VIN`, pin 12 | `T-Display-S3-AMOLED-Plus.pdf` @ `6d1dc00` |
-
-Context on both sheets places it in the **display supply** area, near `KIA3400` transistors
-annotated `-2.2V` and `+4.6V` on the Plus sheet. AMOLED panels need positive and negative
-supplies (ELVDD/ELVSS, commonly ≈ +4.6 V / −2.2 V), so **the strongest hypothesis is that this
-is an AMOLED bipolar display-supply generator.** That is a hypothesis, clearly marked as one.
-
-### String B — `65b311`, from a physical board
-
-An owner tracing a **T-Display-S3** (base board) PCB reported the charger position `U6` carried
-a **5-lead TSOT-23 marked `65b311`**, not the SOP-8 `TP4065` in the schematic —
-[issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230), 2024-03-02, firsthand
-inspection.
-
-### The link between A and B is a guess
-
-Both contain `65`+`6`/`b`+`311`/`611`. **That is the entire basis for connecting them, and it is
-not enough.** Top-marking codes on small packages are usually vendor-internal and bear no
-relation to the ordering part number, so a shared fragment between a *schematic part string* and
-a *package top mark* is weak evidence. They are recorded together because a future reader
-searching either string should find both, not because they are believed to be the same part.
-
-## What was tried
-
-| Attempt | Result |
-|---|---|
-| Search for a datasheet under `AXPM65611` | nothing found |
-| Search for `65b311` as a top mark | nothing found |
-| Look for the part in any other LilyGO repository | appears only on the two AMOLED sheets |
-| Check whether X-Powers (`AXP`-prefixed parts) publishes it | no `AXPM` series found; the `AXP` prefix in "AXPM65611" may be coincidental |
-| Check LilyGO's own BOM or `information/` directories | **LilyGO publishes no BOM for any board in this family** |
-
-## What would resolve it
-
-Any one of these, in decreasing order of decisiveness:
-
-1. **A readable photograph of `U5`/`U4` on an AMOLED board** and of `U6` on a base board, at
-   enough magnification to read the top mark and count the leads.
-2. **LilyGO's BOM**, if it ever publishes one, or an answer in an issue thread — the maintainer
-   answers technical questions readily and has posted PCB photographs before
-   ([issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313)).
-3. **A measured charge current** on a base board, which would narrow the `65b311` part by
-   behaviour even without a marking.
-4. **Measuring the ELVDD/ELVSS rails** on an AMOLED board, which would confirm or refute the
-   display-supply hypothesis for `AXPM65611`.
-
-## Why this matters
-
-For `65b311`: the entire published procedure for **changing the battery charge current** on the
-T-Display-S3 derives from a TP4056/TP4065 datasheet. If the fitted part is different, that
-procedure is unsafe advice. See
-[`components/nanjing-top-power/tp4065`](../../../nanjing-top-power/tp4065/README.md).
-
-For `AXPM65611`: if it is the AMOLED bipolar supply, it is on the critical path for anyone
-trying to control panel power or measure sleep current on those boards.
-
-## Used by
-
-- [`devices/lilygo/t-display-s3-amoled`](../../../../devices/lilygo/t-display-s3-amoled/README.md) — `U5`
-- [`devices/lilygo/t-display-s3-amoled-plus`](../../../../devices/lilygo/t-display-s3-amoled-plus/README.md) — `U4`
-- [`devices/lilygo/t-display-s3`](../../../../devices/lilygo/t-display-s3/README.md) — possibly `U6`, via string B only
-
-## Related unidentified strings in the same family
-
-Recorded here rather than as separate stubs, since none has any evidence beyond a schematic
-string:
-
-| String | Board | Designator | Context |
-|---|---|---|---|
-| **`BV6802`** | T-Display-S3 AMOLED V1.0 | `U6` | near `AVDD` — display supply |
-| **`BV6804`** | T-Display AMOLED Lite; T4-S3 | `U4` / `U6` | near `AVDD` — display supply |
-| **`ULC0511C`** | T4-S3 | — | unknown |
-| **`RS0108YTQC20`** | T-Display AMOLED Lite | `U2` | an 8-bit bidirectional **level shifter** — the Lite's panel runs at 1.8 V. Identity is well-supported by the `_1V8` net names around it; a datasheet was not obtained |
-
-`BV6802` and `BV6804` sharing a prefix and both sitting on `AVDD` is the one genuinely
-suggestive pattern here: they look like two members of one AMOLED-supply family, from a vendor
-whose name begins `BV`. Still a hypothesis.
-
----
-
-## Update — 2026-09-07: schematic net tracing. **String A's function is now established; string B's conflict is resolved in the owner's favour.**
-
-Appended, not substituted. Everything above stands as written on 2026-09-07 (first pass); this
-section reports what `pdftotext -bbox-layout` recovered once poppler became available. Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-
-### String A — `AXPM65611` is an AMOLED bipolar display-bias supply. Hypothesis → established.
-
-The symbol has **12 pins**, and both sheets agree pin-for-pin:
-
-| Pin | Name | `T-Display-S3-AMOLED-Touch.pdf` p3 (`U5`) | `T-Display-S3-AMOLED-Plus.pdf` p3 (`U4`) |
-|---|---|---|---|
-| 1 | `SWP` | `PIU501` @ 282.50, 390.37 | `PIU401` @ 651.00, 95.37 |
-| 2 | `PGND` | `PIU502` @ 282.50, 454.37 | `PIU402` @ 651.00, 152.91 |
-| 3 | `VPOS` | `PIU503` @ 282.50, 397.83 | `PIU403` @ 651.00, 102.37 — annotated **`+4.6V`** @ 677, 100.1 |
-| 4 | `EN` | `PIU504` @ 218.50, 446.37 | `PIU404` @ 593.00, 145.37 |
-| 5 | `GND` | `PIU505` @ 282.50, 462.37 | `PIU405` @ 651.00, 160.37 |
-| 6 | `TEST` | `PIU506` @ 282.50, 446.37 | `PIU406` @ 651.00, 145.37 |
-| 7 | `CTRL` | `PIU507` @ 218.50, 462.37 | `PIU407` @ 593.00, 160.37 — net **`SWIRE`** @ 572, 196.6 |
-| 8 | `AVDD` | `PIU508` @ 218.50, 422.37 | `PIU408` @ 593.00, 124.37 |
-| 9 | `VNEG` | `PIU509` @ 282.50, 414.37 | `PIU409` @ 651.00, 117.37 — annotated **`-2.2V`** @ 677, 114.5; also labelled `EAVDD` |
-| 10 | `SWN` | `PIU5010` @ 282.50, 430.37 | `PIU4010` @ 651.00, 131.37 |
-| 11 | `VIN` | `PIU5011` @ 218.50, 397.83 | `PIU4011` @ 593.00, 102.37 — from **`+3.3V`** @ 569, 114.5 |
-| 12 | `VIN` | `PIU5012` @ 218.50, 390.37 | `PIU4012` @ 593.00, 95.37 |
-
-Two switch nodes, each with its own 10 µH inductor (`DFP252012TF-100M`: `L6`/`L7` on the Touch
-sheet, `L3`/`L4` on the Plus sheet), producing one positive and one negative output at **+4.6 V**
-and **−2.2 V** — the sheet states both voltages itself — plus a one-wire `SWIRE` control line on
-`CTRL`.
-
-That is unambiguously an **AMOLED panel bias generator (ELVDD / ELVSS)**. The hypothesis recorded
-above is now **confirmed by the schematic, not merely plausible**. `SWIRE` in particular is the
-one-wire ELVSS-trim protocol used by this class of part, and its presence on `CTRL` is strong
-corroboration.
-
-**Still unknown:** manufacturer and orderable part number. The function is established; the
-identity is not. Nothing above should be read as identifying the part.
-
-**Proposed real component record** — *proposed only, not created, and this unidentified record
-must not be deleted:* `components/unidentified/lilygo-t-display-s3-family/axpm65611/` stays as
-the canonical home until a manufacturer is established, at which point
-`components/<manufacturer>/<part>/` should be created and this record should link forward to it.
-Recorded in [`scratch/schematic-tracing/index-fragments.md`](../../../../scratch/schematic-tracing/index-fragments.md).
-
-### String B — the `TP4065` / `65b311` conflict is **resolved**. The schematic never said SOP-8.
-
-The claim recorded above and in the T-Display-S3 records — *"the SOP-8 `TP4065` in the
-schematic"* — is **incorrect**, and the error was in this repository's reading of the schematic,
-not in the owner's inspection of the board.
-
-`T_Display_S3.pdf` p1 draws `U6` with **exactly five pin tokens**:
-
-```
-python3 trace.py grep bbox/tds3.xhtml '^PIU6'
-  p1 x=264.50 y=483.48  PIU604      p1 x=283.50 y=496.46  PIU603
-  p1 x=241.50 y=499.46  PIU601      p1 x=283.50 y=503.46  PIU605
-  p1 x=264.50 y=518.48  PIU602
-```
-
-There is no `PIU606`, `PIU607` or `PIU608`. The pin function text at those coordinates reads
-1 `CHRG`, 2 `GND`, 3 `BAT`, 4 `VCC`, 5 `PROG` — the LTC4054 / TP4054 / TP4056 **SOT-23-5**
-arrangement. A 300 dpi render of the region confirms a five-terminal symbol visually.
-
-Two sibling sheets give the same answer independently: `T-DISPLAY-S3-AMOLED.pdf` p1 `U5`
-(`PIU501`…`PIU505`) and `T-Display-S3-AMOLED-Touch.pdf` p3 `U6` (`PIU601`…`PIU605`), both with
-the same five function names.
-
-**So the schematic and [issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230)
-agree: the part is a 5-lead SOT-23/TSOT-23.** The owner's `65b311` top mark is consistent with
-the schematic rather than contradicting it, and the two strings A and B are *still* unrelated —
-string A is a 12-pin AMOLED bias supply, string B a 5-pin charger. The speculative link between
-them, already described above as weak, should now be considered **refuted by pin count**: they
-cannot be the same part.
-
-### Charge current: the sheet states it
-
-`T_Display_S3.pdf` carries a rotated note, tokens at x ≈ 311.7, y 510.95–531.81, reading
-**`IBAT (mA) = 580`**, beside `R13` = 2 kΩ on `PROG`. (Poppler merges this with the adjacent
-rotated designator `R13` into one apparent line; the rendered crop shows they are two separate
-text objects.)
-
-This narrows the fitted part by behaviour, which resolution route 3 above anticipated:
-
-- It is **not a TP4057.** That part is **SOT-23-6** with a separate `STDBY` pin the symbol does
-  not have, and its own datasheet — held at
-  `components/generic/tp4057/artifacts/tp4057-datasheet-cn-m5stack-mirror.pdf` — specifies
-  **500 mA typical at `RPROG` = 2 kΩ**, not 580 mA.
-- 580 mA at 2 kΩ implies a programming constant near 1160, close to the TP4056 family's 1200.
-
-**Consequence for the safety note above:** the published procedure for changing the T-Display-S3
-charge current is derived from an 8-pin part's datasheet, and the fitted part is 5-pin. The
-procedure's *arithmetic* may still be approximately right — the sheet's own 580 mA figure is
-consistent with a TP4056-family constant — but it is derived from the wrong package and should
-not be relied on without measurement. The warning stands; its basis is now better.
-
-### Sheet-level evidence index
-
-| Claim | File | Page | Coordinate |
-|---|---|---|---|
-| `TP4065` part string | `T_Display_S3.pdf` | 1 | 273.09, 484.09 |
-| 5 pin tokens | `T_Display_S3.pdf` | 1 | see block above |
-| `IBAT (mA) = 580` | `T_Display_S3.pdf` | 1 | x≈311.7, y 510.95–531.81 |
-| `AXPM65611` string | `T-Display-S3-AMOLED-Touch.pdf` | 3 | 238.26, 474.41 |
-| `AXPM65611` string | `T-Display-S3-AMOLED-Plus.pdf` | 3 | 615.31, 171.80 |
-| `+4.6V` / `-2.2V` rails | `T-Display-S3-AMOLED-Plus.pdf` | 3 | 677, 100.1 / 677, 114.5 |
-
-Full trace: [`devices/lilygo/t-display-s3-shared/schematic-netlist.md`](../../../../devices/lilygo/t-display-s3-shared/schematic-netlist.md).
diff --git a/components/unidentified/m5stack-dinmeter/buzzer/README.md b/components/unidentified/m5stack-dinmeter/buzzer/README.md
deleted file mode 100644
index 4e8c72c..0000000
--- a/components/unidentified/m5stack-dinmeter/buzzer/README.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# Unidentified — M5Stack DinMeter buzzer (`LS1`)
-
-- **Category:** electro-magnetic (passive) buzzer / sounder.
-- **Manufacturer / part number:** ⚠ **NOT ESTABLISHED.** `LS1` carries a `CO` marker and the
-  label `Buzzer` on the schematic, but **no part number and no value**.
-- **Retrieved:** 2026-09-04
-
-## 1. What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Designator | `LS1`, 2 pads (`PILS101`, `PILS102`) | DinMeter schematic |
-| Label on sheet | `Buzzer` | schematic, (158, 464.1) |
-| Drive | **`Q5` SS8050 NPN** low-side, base resistor **`R25` 470 Ω** from net `beep` | schematic |
-| Flyback | **`D6` 1N4148WT** across the coil | schematic — *a flyback diode implies an inductive (magnetic) buzzer, not a piezo* |
-| Supply | `+5VIN` | schematic |
-| Local bulk | `C27` 10 µF | schematic |
-| Control GPIO | `beep` → Stamp pad 3 → **ESP32-S3 GPIO3** | schematic; M5Unified |
-| Passive, not self-driving | ESP-IDF board support models it as a **LEDC PWM tone source**, not an on/off element | `esp-board-manager` `ledc_buzzer` |
-| Default tone config | LEDC channel 1, timer 1, **4 kHz**, 10-bit resolution, low-speed mode | `esp-board-manager` |
-| M5Unified config | `spk_cfg.pin_data_out = GPIO_NUM_3`, `spk_cfg.buzzer = true`, `magnification = 48` | `M5Unified/src/M5Unified.cpp:2921-2928` |
-| Frequencies used in vendor examples | 4 000 Hz, 8 000 Hz, 10 000 Hz | `M5DinMeter/examples/Basic/{buzzer,button,encoder}.ino` |
-
-The `SS8050` transistor is annotated on the sheet with `Y1` immediately to its right — that is
-the SOT-23 **marking code** for an SS8050, not a separate designator. See
-[`devices/m5stack/dinmeter/pinouts-and-buses.md` §6](../../../../devices/m5stack/dinmeter/pinouts-and-buses.md#6-reference-designator-census-and-three-that-do-not-resolve).
-
-## 2. What is not established
-
-Resonant frequency, sound-pressure level, rated voltage, coil resistance, current draw, and
-package/footprint dimensions. Nothing about the acoustic behaviour is published.
-
-**What would resolve it:** a teardown photograph of `LS1`'s top marking, or an M5Stack BOM.
-
-## 3. Practical notes
-
-- It is **passive**: you must supply a square wave. Writing a DC level makes it click once.
-- Being magnetic with a flyback diode, it will have a pronounced resonance — the vendor's use
-  of 4 kHz and 8–10 kHz in different examples suggests a broad usable range, but the loudest
-  frequency is unknown without measurement.
-- It is driven from **`+5VIN`**, so it is louder on USB/DC than on battery-only operation where
-  the rail comes from the boost.
-- GPIO3 is an ESP32-S3 **strapping-adjacent** pin (JTAG source select on some parts); it is
-  driven as a plain LEDC output here with no reported issue.
-
-## 4. Artifacts
-
-**None.** Establishing evidence: the device schematic and
-[`devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml`](../../../../devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml).
-
----
-
-## Used By
-
-### M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-`LS1`. Identical on both revisions.
-→ [`devices/m5stack/dinmeter/features/buzzer.md`](../../../../devices/m5stack/dinmeter/features/buzzer.md)
-
----
-
-## Update — 2026-09-07: drive circuit re-traced. **`C27` is in series with the base, not a bulk capacitor.**
-
-Appended, not substituted. The table above records *"Local bulk | `C27` 10 µF"*. Net tracing
-shows `C27` is **in the base-drive path**, between `R25` and the transistor — an AC coupling
-capacitor, not decoupling. Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-
-### The evidence
-
-All five drive-path pin tokens share **y = 491.37** and run strictly left-to-right in x:
-
-```
-PIR2501 @  45.00, 491.37   R25 pin 1   <- net `beep`
-PIR2502 @  67.00, 491.37   R25 pin 2
-PIC2701 @  74.00, 491.37   C27 pin 1
-PIC2702 @  89.00, 491.37   C27 pin 2
-PIQ501  @ 121.00, 491.37   Q5 base
-```
-
-A series chain on one horizontal wire. A decoupling capacitor would have one pin on the rail and
-one on ground; both of `C27`'s pins are on the signal path. Confirmed by a 300 dpi render, which
-shows the capacitor symbol drawn *in* the wire between `R25` and the base node.
-
-`D7` `1N4148WT` hangs off the base node at x = 99.50 — cathode `PID702` @ y 502.57 (up, to the
-base), anode `PID701` @ y 523.57 (down, to `GND` @ y 553.60): a **negative-excursion clamp**,
-which is exactly what an AC-coupled base needs.
-
-```
-beep ── R25 470Ω ── C27 10µF ──┬── Q5 base (SS8050 NPN)
-                               └── D7 (cathode up) ── GND
-```
-
-### What this changes
-
-- **The row "Local bulk | `C27` 10 µF" is superseded.** `C27` is a coupling capacitor. There is
-  no local bulk capacitor identified on the `+5VIN` node in this branch.
-- **The transducer cannot be driven with a DC level.** A steady GPIO high produces one brief
-  pulse and then nothing. It *must* be driven with a waveform. The record's existing statement
-  that the part is passive and modelled as a PWM tone source is therefore **confirmed by the
-  hardware**, not merely by how the library treats it.
-- **High-pass corner ≈ 34 Hz** (1 / 2π · 470 Ω · 10 µF), so the whole audio band passes and the
-  coupling imposes no practical restriction on tone selection.
-
-### Re-confirmed unchanged
-
-| Property | Value | Token |
-|---|---|---|
-| `LS1`, 2 pads | value field `Buzzer` | `PILS101` @ 142.50, 448.37 · `PILS102` @ 142.50, 455.37 |
-| `D6` `1N4148WT` anti-parallel across `LS1` | flyback | `PID602` @ 99.50, 426.57 · `PID601` @ 99.50, 448.57 |
-| `Q5` `SS8050` low-side NPN | collector/emitter | `PIQ503` @ 135.50, 476.77 · `PIQ502` @ 135.50, 505.77 → `GND` |
-| `R25` 470 Ω | base resistor | above |
-| Supply | `+5VIN` | — |
-| Control GPIO | `beep` → module pad 3 → `G3` | `NLbeep` @ 29.50, 488.20 |
-
-**The flyback diode remains the strongest evidence for the category.** `D6` is drawn
-anti-parallel across `LS1`; a catch diode is only needed for an inductive load. This supports the
-"electro-magnetic (passive) buzzer" categorisation at the head of this record — a piezo element
-would not need one.
-
-### Still not established
-
-Resonant frequency, sound-pressure level, rated voltage, coil resistance, current draw,
-manufacturer and part number — **all unchanged.** The schematic gives topology, not identity.
-This record stays open.
diff --git a/components/unidentified/m5stack-dinmeter/rotary-encoder/README.md b/components/unidentified/m5stack-dinmeter/rotary-encoder/README.md
deleted file mode 100644
index 29a1aba..0000000
--- a/components/unidentified/m5stack-dinmeter/rotary-encoder/README.md
+++ /dev/null
@@ -1,136 +0,0 @@
-# Unidentified — M5Stack DinMeter rotary encoder ("the orange knob")
-
-- **Category:** incremental quadrature rotary encoder with integrated push switch.
-- **Manufacturer / part number:** ⚠ **NOT ESTABLISHED.** No part number, manufacturer or series
-  is printed on the schematic, stated in the documentation, or listed in the datasheets section
-  of either DinMeter product page.
-- **Scope:** device-scoped, per the convention for unidentified parts, so it cannot collide
-  with other unknown encoders.
-- **Retrieved:** 2026-09-04
-
-This is the component that defines the product's identity — the bright orange knurled knob —
-and it is the one M5Stack documents least.
-
----
-
-## 1. What *is* established
-
-All from the DinMeter schematic (`K134_DIN_Meter_v1.0-schematic.pdf`, parsed marker layer),
-which is shared byte-for-byte by v1.0 and v1.1.
-
-| Property | Value |
-|---|---|
-| Not soldered to the main board | It attaches through a **7-pad connector `J5`** (`PIJ501`…`PIJ505` recovered, pads 6–7 present on the symbol), labelled **`Rotary encode`** on the sheet |
-| Channel A | `IN_A` → Stamp pad 23 → **ESP32-S3 GPIO41**, pulled up by `R2` 10 kΩ to `+3.3V` |
-| Channel B | `IN_B` → Stamp pad 21 → **ESP32-S3 GPIO40**, pulled up by `R3` 10 kΩ to `+3.3V` |
-| Common | `GND` |
-| Push switch | separate contacts labelled `b1`/`b2` on the same connector block, net `BTN` → `WAKE` → Stamp pad 25 → **GPIO42**, pulled up by `R1` 10 kΩ, debounced by `C1` 100 nF |
-| Switch also wakes the board | `BTN` feeds the power-latch wake path through `D4` (B5819WT) |
-| Detent behaviour | **not stated anywhere.** Counts-per-revolution, detents-per-revolution and whether detents align to full quadrature cycles are all unknown |
-| Shaft, knob, torque, life | **not stated** |
-| Colour | orange knob cap (product photography) — whether the cap is part of the encoder or a separate moulding is **not established** |
-
-## 2. What the software assumes
-
-Two independent implementations agree that it is a **standard 2-channel quadrature encoder with
-4 counts per detent**:
-
-| Source | Treatment |
-|---|---|
-| `m5stack/M5DinMeter` | A vendored copy of **PJRC's `Encoder` library** (Paul Stoffregen, MIT, v1.2), constructed as `ENCODER(41, 40)` — `src/M5DinMeter.h:8-9,33`. Full x4 decoding, interrupt-driven |
-| `espressif/esp-board-manager` | **PCNT** unit, two channels, each pin edge on one channel and level on the other, `max_glitch_ns: 1000`, limits ±1000, `accum_count: true`. Its comment: *"Both channels are counted so one detent is four counts and the direction is unambiguous."* |
-
-So: x4 decoding, 1 kHz-ish glitch filtering is adequate, and no external debounce hardware
-beyond the 10 kΩ pull-ups is fitted.
-
-## 3. Why identification matters, and what would resolve it
-
-It matters for: sourcing a replacement after mechanical wear (this is the part that will fail
-first in a panel instrument), knowing the rated rotational life, knowing the switch's rated
-operations, and knowing whether the detent count matches the electrical cycle count.
-
-**Candidate families were deliberately NOT recorded here.** This repository holds an
-[Alps Alpine `SSCM110100`](../../../alps-alpine/sscm110100/README.md) encoder record from
-another device; the DinMeter's encoder is **not** asserted to be that part or any relative of
-it. Nothing in the DinMeter's evidence names Alps.
-
-**What would settle it:**
-1. A teardown photograph showing the encoder body's manufacturer marking.
-2. An M5Stack BOM or a reply from `support@m5stack.com`.
-3. The `J5` mating connector part, which would at least narrow the encoder module family.
-
-Until then this record stays `unidentified`.
-
-## 4. Artifacts
-
-**None.** Establishing evidence is the device schematic and the extracted layout:
-- [`devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf`](../../../../devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf)
-- [`devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml`](../../../../devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml)
-
----
-
-## Used By
-
-### M5Stack DinMeter (K134) and DinMeter v1.1 (K134-V11)
-
-The primary input device. Quadrature on GPIO41 (A) / GPIO40 (B); push switch on GPIO42, which
-doubles as the board's wake key. Identical on both revisions.
-
-→ [`devices/m5stack/dinmeter/features/rotary-encoder-and-buttons.md`](../../../../devices/m5stack/dinmeter/features/rotary-encoder-and-buttons.md)
-
----
-
-## Update — 2026-09-07: `J5` has **five** pins, not seven; topology now established
-
-Appended, not substituted. The table above states *"a **7-pad connector `J5`**
-(`PIJ501`…`PIJ505` recovered, pads 6–7 present on the symbol)"*. **The symbol has five pins.**
-Method: [`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-
-```
-python3 trace.py grep bbox/<dinmeter>.xhtml '^PIJ5'
-  p1 x=445.50 y=361.91  PIJ501      p1 x=503.00 y=361.91  PIJ502
-  p1 x=459.50 y=389.77  PIJ503      p1 x=474.50 y=389.77  PIJ504
-  p1 x=488.50 y=389.77  PIJ505
-```
-
-There is no `PIJ506` or `PIJ507` anywhere in the document. A 300 dpi render of the symbol shows
-five pins and no more. The earlier "pads 6–7 present" reading is withdrawn.
-
-### What the render adds that the marker layer alone could not
-
-The five pins are **named on the symbol**, and the names settle the topology:
-
-| Pin | Symbol name | Net | Termination |
-|---|---|---|---|
-| 1 | `b1` | `BTN` @ 430, 359.2 | push switch, one side |
-| 2 | `b2` | `GND` @ 533, 362.5 | push switch, other side |
-| 3 | **`A`** | `IN_A` @ 457, 419.9 | `R2` 10 kΩ to `+3.3V`, `C2` 100 nF to `GND` |
-| 4 | **`COM`** | `GND` @ 475, 416.7 | — |
-| 5 | **`B`** | `IN_B` @ 486, 419.9 | `R3` 10 kΩ to `+3.3V`, `C3` 100 nF to `GND` |
-
-So it is a **standard 3-terminal incremental quadrature encoder (A / COM / B) with COM
-grounded**, plus an integrated 2-terminal momentary push switch — a single 5-terminal part, not a
-7-pad connector carrying two separate devices. The switch contacts are drawn *inside the same
-symbol*, above the A/COM/B group.
-
-Everything the existing table says about the GPIO mapping, the pull-ups and the wake path is
-**confirmed unchanged**: `IN_A` → pad 23 → GPIO41, `IN_B` → pad 21 → GPIO40, `BTN` → `WAKE` →
-pad 25 → GPIO42.
-
-### Two things this makes newly sayable
-
-1. **The encoder sits on the JTAG data pins.** The module footprint prints the pad names itself:
-   pad 23 is `G41/MTDI` and pad 21 is `G40/MTDO`. An external JTAG probe and the encoder cannot
-   be used simultaneously. Not stated in the header, the driver, or M5Stack's documentation.
-2. **The input filter has a measurable ceiling.** With the 10 kΩ external pull-up in parallel
-   with the ESP32-S3 internal one that `Encoder::begin()` also enables (≈ 8.2 kΩ) and `C2`/`C3`
-   at 100 nF, τ ≈ 0.82 ms and the corner is ≈ **194 Hz**. That is the hardware limit on edge
-   rate, independent of firmware. See
-   [`devices/m5stack/dinmeter/driver-vs-document-audit.md`](../../../../devices/m5stack/dinmeter/driver-vs-document-audit.md).
-
-### Still not established
-
-Manufacturer, part number, series, counts-per-revolution, detents-per-revolution, detent
-alignment, shaft type, torque and rated life — **all unchanged from the list above.** The
-schematic names none of them, and pin-count alone does not identify a part. This record stays
-open.
diff --git a/components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md b/components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md
deleted file mode 100644
index 4aa76aa..0000000
--- a/components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md
+++ /dev/null
@@ -1,163 +0,0 @@
-# Unidentified — Stamp-S3A step-down converter (`U4`)
-
-- **Category:** synchronous step-down (buck) converter IC, wafer-level/CSP ball grid, with
-  pin-strapped output selection.
-- **Manufacturer / part number:** ⚠ **NOT ESTABLISHED.** The `Sch_StampS3_v0.3.3.pdf` symbol
-  carries **no part-number text**.
-- **Retrieved:** 2026-09-04
-
-The 5 V → 3.3 V converter on the **M5Stack Stamp-S3A** (board rev v0.3.3), replacing the
-[MUN3CAD01-SC](../../../murata/mun3cad01-sc/README.md) µPOL module used on the Stamp-S3 v0.2.
-
----
-
-## 1. What is established
-
-From `Sch_StampS3_v0.3.3.pdf`, marker layer parsed:
-
-| Property | Value |
-|---|---|
-| Designator | `U4` |
-| Ball/pin names, 8 total | `A1 SW`, `A2 VIN`, `B1 EN`, `B2 GND`, `C1 VSEL1`, `C2 VOS`, `D1 VSEL2`, `D2 VSEL3` |
-| Vendor annotation on the sheet | **`IOUT: 0~0.6A`** |
-| Input | `VIN_5V` |
-| Output sense | `VOS` → `VDD_3V3` (a *sense* pin, so the output node is measured remotely rather than through a resistive divider) |
-| External inductor | **`L4` = `MWTC201608S2R2`** — 2.2 µH in a 2016-metric (0806-imperial) package, on the `SW` node |
-| Support passives | `C15` 1 nF, `C16` 10 µF/10 V, `C18` 100 nF/25 V, `C21` 10 µF, `C22` 10 µF, `C25` 10 µF |
-| Enable | `B1 EN` ← `R16` 100 kΩ network |
-| Output-voltage setting | **pin-strapped** via `VSEL1` / `VSEL2` / `VSEL3` — there is **no feedback divider**; `R6` and `R17` from the v0.2 design are deleted |
-
-## 2. Why this is recorded as unidentified rather than guessed
-
-The topology is distinctive — three `VSEL` strap balls, a `VOS` sense pin, `SW` with an
-external inductor, 0.6 A, 2 × 4 ball grid — and it would be easy to name a plausible family.
-**No candidate part number is asserted anywhere in this repository**, because a comparison
-shortlist is not a reading, and a near-miss part number on a power rail is exactly the kind of
-error that propagates.
-
-M5Stack's own Stamp-S3A specification page lists `DC-DC: MUN3CAD01-SC` and links that
-datasheet. **That is demonstrably not this part**: the µPOL module has an integrated inductor
-and an `FB` pin, no `SW`, no `VSEL` straps, and is rated 1 A rather than 0.6 A. The
-specification row was evidently carried over from the Stamp-S3 page. See
-[`components/m5stack/stamp-s3a/README.md` §5](../../../m5stack/stamp-s3a/README.md#5-change-3--the-dc-dc-was-replaced-and-the-datasheet-page-is-stale).
-
-## 3. What would resolve it
-
-1. A photograph of `U4`'s top marking on a Stamp-S3A (CSP parts often carry a 3–4 character
-   code, which usually needs a vendor decode table).
-2. The `MWTC201608S2R2` inductor's maker — a 2.2 µH/0806 power inductor is often specified in
-   the converter vendor's own reference design, so identifying it may point at the IC family.
-3. An M5Stack BOM, or a reply from `support@m5stack.com`.
-4. An updated Stamp-S3A specification page. Worth re-checking periodically: the current page's
-   DC-DC row is stale, so M5Stack may correct it.
-
-## 4. Consequences while it stays unidentified
-
-- **The 0.6 A output limit is a real design constraint** and it is *lower* than the Stamp-S3's
-  1 A. Anything drawing 3.3 V through the module — an application that loads `VDD_3V3` heavily
-  via the module's `3V3` pin — has less headroom on an S3A than on an S3. The vendor does not
-  mention this anywhere. **`inferred` from the schematic annotation.**
-- Efficiency curve, light-load mode behaviour, switching frequency, soft-start and protection
-  behaviour are unknown, so the module's much-improved sleep figures cannot be attributed with
-  confidence.
-- Nothing here is firmware-visible: there is no register interface.
-
-## 5. Artifacts
-
-**None.** Establishing evidence:
-[`components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf`](../../../m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf)
-and the parsed layout beside it.
-
----
-
-## Used By
-
-### M5Stack Stamp-S3A (SKU S007-V033), board rev v0.3.3
-
-`U4` — the module's only 5 V → 3.3 V converter.
-→ [`components/m5stack/stamp-s3a/README.md`](../../../m5stack/stamp-s3a/README.md)
-
-### Reached from this device
-
-- [M5Stack DinMeter v1.1 (K134-V11)](../../../../devices/m5stack/dinmeter-v1.1/README.md) — the
-  Stamp-S3A it fits contains this part.
-
----
-
-## Update — 2026-09-07: **RESOLVED. The schematic prints `JW5712`.**
-
-Appended, not substituted. The statement above — *"The `Sch_StampS3_v0.3.3.pdf` symbol carries
-**no part-number text**"* — is **incorrect for the copy retained in this repository**, and the
-sibling session's `JW5712` argument is confirmed *directly*, not inferentially.
-
-### The evidence
-
-File: `components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf`, page 1,
-`Creator: Altium Designer`, 0 embedded rasters, 865 words, 50 `NL` tokens.
-
-```
-python3 trace.py grep bbox/<file>.xhtml 'JW5712'
-  p1 x=193.49 y=546.41  JW5712
-```
-
-That coordinate is directly **below** the `U4` symbol body (pin tokens span x 171.5–243.5,
-y 477.37–534.91), which is Altium's Comment/Value position; the designator `U4` sits
-correspondingly **above** it at (186.67, 467.31). A 300 dpi render of the region shows
-`U4` above the symbol and `JW5712` below it, in the vendor's ordinary designator/value styling.
-
-So this is not an inference from pin function, package or current rating. **The sheet names the
-part.**
-
-### Why the earlier pass missed it
-
-The earlier pass parsed the *marker* layer (`CO`/`PI` tokens) and correctly recovered all eight
-ball names. The value string is ordinary visible text in the page's text layer, ~12 pt below the
-symbol, and it was not in the coordinate window that was read. This is a good argument for
-always running `netlist.py --components`, which reports each `CO<designator>` together with the
-plain-text tokens nearest it, rather than only harvesting the marker layer.
-
-### Ball map re-confirmed, with coordinates
-
-Unchanged from the table above; restated with tokens so it can be re-checked.
-
-| Ball | Name | Token | Net |
-|---|---|---|---|
-| `A1` | `SW` | `PIU40A1` @ 243.50, 477.37 | `L4` `MWTC201608S2R2` 2.2 µH → output node |
-| `A2` | `VIN` | `PIU40A2` @ 171.50, 506.37 | `VIN_5V` |
-| `B1` | `EN` | `PIU40B1` @ 171.50, 477.37 | `R16` 100 kΩ/1 % up to the `VIN` line |
-| `B2` | `GND` | `PIU40B2` @ 171.50, 534.91 | `GND` |
-| `C1` | `VSEL1` | `PIU40C1` @ 243.50, 520.37 | strap |
-| `C2` | `VOS` | `PIU40C2` @ 243.50, 491.37 | `VDD_3V3` — remote sense |
-| `D1` | `VSEL2` | `PIU40D1` @ 243.50, 527.37 | strap |
-| `D2` | `VSEL3` | `PIU40D2` @ 243.50, 534.91 | strap |
-
-Annotations on the sheet: **`IOUT: 0~0.6A`** @ (209.45–229.20, 452.93), and the section headings
-`ESP32` @ (44, 403.8) / `DCDC` @ (44, 428.9) / `VDD_3V3` @ (42, 438.6).
-
-**New observation from the render:** `VSEL1`, `VSEL2` and `VSEL3` are **all three tied together
-to a single vertical net labelled `VIN_5V`**, with junction dots on `C1` and `D1`. The output
-voltage is therefore selected by the strap combination "all high", not by any resistor network —
-which is consistent with the existing observation that `R6` and `R17` from the v0.2 design are
-deleted.
-
-### Corroboration already in the repository
-
-`devices/m5stack/cap-lora-1262/artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf`
-carries the **same part** as `U3`, with the value string `JW5712` at (140, 186.3), the same
-`IOUT: 0~0.6A` annotation and the same eight ball names — a second, independent M5Stack sheet
-naming it. `devices/m5stack/cap-cc1101/…/U219-Cap_CC1101_SCH_V0.3_20260528.pdf` fits it a third
-time as `U1`.
-
-### Disposition
-
-**This unidentified record is retained and must not be deleted** — other records link to it.
-The real component record already exists:
-[`components/joulwatt/jw5712`](../../../joulwatt/jw5712/README.md), with a scanned datasheet at
-`components/joulwatt/jw5712/artifacts/jw5712-jw5712a-datasheet-scanned.pdf`.
-
-> ⚠ Note for whoever works that datasheet: it is a **raster scan** — 4 pages, 4 full-page
-> images, `pdftotext` yields **0 words**. It cannot be text-searched. See
-> [`scratch/schematic-tracing/traceability-census.md`](../../../../scratch/schematic-tracing/traceability-census.md) §5.
-
-Proposed index change (not applied):
-[`scratch/schematic-tracing/index-fragments.md`](../../../../scratch/schematic-tracing/index-fragments.md).
diff --git a/components/unidentified/t-display-k230/README.md b/components/unidentified/t-display-k230/README.md
deleted file mode 100644
index 1f60d37..0000000
--- a/components/unidentified/t-display-k230/README.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Unidentified parts — LilyGO T-Display K230
-
-Scope-limited to this board, per the convention that unidentified parts must not collapse into a
-single shared record. Every entry states what is known, what evidence would resolve it, and why
-it was not resolved on 2026-09-04.
-
-## U1 — Main-board PMIC
-
-**Known:** the K230's PMU block provides "**two output IOs to control PMIC and system reset**"
-(Canaan brief datasheet), so an external PMIC is architecturally required. The board is
-battery-powered and runs a 1.6 GHz core with DVFS, so it is not a two-LDO design.
-
-**Not known:** manufacturer or part number. A full part-number sweep of the LilyGO BSP,
-launcher, device trees and Buildroot config on 2026-09-04 — regex-matching every common
-PMIC/regulator prefix including `axp`, `sy`, `mp`, `tps`, `eta`, `sgm`, `rk8`, `hi65` — returned
-**no PMIC part at all**. This is consistent with a PMIC that Linux never touches, i.e. one
-sequenced entirely by the K230 PMU in hardware.
-
-**What would resolve it:** a photograph of the main-board PCB, or a LilyGO schematic. Neither
-exists publicly; the wiki's `#schematic` heading has **no link under it** (verified 2026-09-04).
-
-**Why it matters:** without it, nothing can be said about rail voltages, DVFS operating points,
-programmable current limits or true shutdown behaviour.
-
-## U2 — Speaker amplifier on the main board / cased version
-
-**Known:** the Cased Version wiki page lists "microphone, **speaker**, 3.5 mm headphone jack".
-The K230 has an on-die codec with 2 DAC channels, but a codec cannot drive a speaker directly.
-A separate amplifier must exist on the main board or in the case assembly.
-
-**Not known:** part number. The only amplifier named anywhere in LilyGO's sources is the
-**MAX98357A on the nRF52840 base board**, which is a *different* board.
-
-**What would resolve it:** PCB photograph, or an `aplay -l` / ALSA control dump from a running
-cased unit.
-
-## U3 — Microphone
-
-**Known:** a microphone is listed on the wiki and the launcher has `ui_mic_spectrum.c` and a
-Xiaozhi wake-word path that "owns the microphone". The K230 supports up to 8 PDM DMICs *and* 2
-analogue ADC channels, so either type is possible.
-
-**Not known:** PDM or analogue, part number, count.
-
-## U4 — "RC01812" Ethernet part
-
-**Known:** the T-Display K230 Kit shop listing states "Ethernet Module | Name: **RC01812** |
-Connector: RJ45". The wiki instead names **RTL8152B**.
-
-**Assessment:** `RC01812` matches no Realtek, Microchip, ASIX or Corechips Ethernet controller
-naming scheme. It is most consistent with an **RJ45 jack with integrated magnetics** part number
-from a Chinese connector vendor. **This is an interpretation, not a finding.** Both designations
-are recorded in [`components/realtek/rtl8152b`](../../realtek/rtl8152b/README.md) and in
-`GC-3`.
-
-## U5 — Claimed ESP32-S3-R8 co-processor
-
-**Known:** LilyGO's wiki page for the T-Display K230 states the board is "combined with
-**ESP32-S3-R8** (16 MB Flash, 8 MB PSRAM) for Wi-Fi/Bluetooth connectivity", offers PlatformIO
-and Arduino instructions for an "ESP32-S3 co-processor", and lists "Bluetooth 5.0 LE (ESP32-S3)".
-
-**Contradicting evidence:** an exhaustive part-number sweep of the entire T-Display-K230
-repository at commit `bb831ab…` finds **zero** occurrences of `esp32`, `esp32s3` or any
-Espressif identifier. The BSP's Wi-Fi is RTL8189FS over SDIO; its Bluetooth is a USB dongle with
-a CSR8510 workaround patch. The shop listing names RTL8189, not ESP32-S3. The Cased Version wiki
-page names no Wi-Fi chip at all.
-
-**Assessment:** most likely a copy-paste from a sibling LilyGO product page. **Not resolved.**
-Recorded as `GC-2`. A component record for
-[`espressif/esp32-s3r8`](../../espressif/esp32-s3r8/README.md) already exists in this repository
-and has deliberately **not** been given a Used-By entry for this board, because the claim is
-unverified.
-
-## U6 — 21700 cell and battery assembly
-
-**Known:** the nRF52840 base board's `P0.04` enables an "external 5 V boost … for boosting the
-**21700 battery compartment**". So the kit's power source is a 21700 cell, not a pouch LiPo.
-
-**Not known:** capacity, chemistry, protection-circuit part, cell vendor, whether a cell is
-included in any SKU. Community report 2026-08-20: an early buyer received "just the screen and
-motherboard on risers in the package" with no case or battery.
-
-## Sources
-
-All claims above are sourced from the same primary set used by the device record: LilyGO's
-`T-Display-K230` repository at commit `bb831ab358b66f5bd9a87ecd7c580fee4537492e`, LilyGO's shop
-listings and wiki retrieved 2026-09-04, and the Canaan K230 datasheets at `k230_docs` commit
-`f8e30213963e0ed5cf995c3cd4701218a45e4793`. See
-[`devices/lilygo/t-display-k230/sources.md`](../../../devices/lilygo/t-display-k230/sources.md).
diff --git a/components/unidentified/xteink-x3-x4/README.md b/components/unidentified/xteink-x3-x4/README.md
deleted file mode 100644
index 0f20093..0000000
--- a/components/unidentified/xteink-x3-x4/README.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Unidentified parts — Xteink X3 / X4 board family
-
-Parts fitted to the ESP32-C3 Xteink boards that are **evidenced but not
-identified to a part number**. Scoped to this device family so that unrelated
-unknowns never collapse into one record, per the research method.
-
-| Record | What is known | What is missing |
-|---|---|---|
-| [`spi-nor-flash-128mbit-puya`](spi-nor-flash-128mbit-puya/README.md) | Maker (Puya), density (128 Mbit / 16 MB), two independent teardowns | Part number |
-| [`rtc-ds-series`](rtc-ds-series/README.md) | Address 0x68, "DS-series" | **Which DS part — three sources disagree** |
-| [`nfc-tag-iso14443a`](nfc-tag-iso14443a/README.md) | Passive, writable, ISO 14443A, **purpose now established** | Part number, tag type |
-| [`battery-charger-tp4056-class`](battery-charger-tp4056-class/README.md) | "TP4056-like" | Actual part |
-
-**None of these has been promoted from candidate to finding.** Each record states
-exactly what evidence would resolve it. In every case that evidence is cheap — a
-legible top-marking photograph, or one I²C register read.
-
-The boards themselves: [X3](../../../devices/xteink/x3/README.md) ·
-[X4](../../../devices/xteink/x4/README.md)
-
----
-
-## Round 2 — 2026-09-11: the evidence that resolves these now exists and is in this repository
-
-**No line above was altered.** None of the four parts is resolved by this pass.
-What has changed is that the **kind of evidence that resolves them has become
-available**, and it is retained here rather than hypothetical.
-
-### FCC internal photographs, public and retained
-
-| Device | Exhibit | Public since | Local path | Images | SHA-256 |
-|---|---|---|---|---|---|
-| **X3** | Internal Photos | **2026-06-24** | [`devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf`](../../../devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf) | **16** | `b3affd56115e9c3e49428f9727ba194c0eec6705ddd0b039fd9b4ce28b430a45` |
-| **X4** | Internal Photos | **2026-07-04** | [`devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf`](../../../devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf) | **15** | `fd1623a7c9df42ba8140cea6d2618722726c1f442209c02f8229c1b50658f370` |
-
-Both were fetched from `fccid.io` on 2026-09-11 with UA `WhatsApp/2.23.20.0`
-(a desktop-Chrome UA is served 403) and validated `%PDF`. Images are extractable
-with `nix-shell -p poppler-utils --run 'pdfimages -png in.pdf out/p'`.
-
-**These are regulatory photographs of the board as shipped**, taken under an
-obligation to show the assembly, and at higher resolution than the community
-teardowns already archived for the X3.
-
-### Status of each part, unchanged
-
-| Part | Status | What these photographs could give it |
-|---|---|---|
-| `flash` | unresolved | The 8-pin SOIC package is **visible** in at least one X4 image. A readable top marking would name the manufacturer and density directly |
-| `rtc` | unresolved — **and it is a live 3-way conflict**: `DS3231` (firmware) vs `DS1307` (teardown caption) vs "DS-series" (Chinese BOM) | A readable top marking would **settle a conflict that has stood since 2026-09-04**. This is the single highest-value read in the set |
-| `nfc-tag` | unresolved (X3 only) | The tag is an inlay, likely under the rear shell — may not appear |
-| `charger` | unresolved | A readable marking on the charge-path IC |
-
-### One observation, offered as an observation and not as an identification
-
-A **single** image from the X4 set (`p-007`) was opened. It shows a green PCB
-with a meandering trace antenna, a shielded area containing an Espressif-logo
-QFN part, a **40.000 MHz crystal**, an **8-pin SOIC** package, a USB-C
-receptacle on an adjoining board section, and two FPC connectors of different
-widths.
-
-**No top marking was transcribed and no part was identified.** Doing that
-properly needs the full 31 images across both devices opened at native
-resolution, cross-referenced against the reference designators, and read
-carefully — work this pass did not do and deliberately did not guess at.
-
-**The next session's cheapest high-value task in the whole Xteink tree is to read
-these 31 images.** Four unidentified parts and one three-way conflict are waiting
-on it, and the files are already here and hashed.
diff --git a/components/unidentified/xteink-x3-x4/battery-charger-tp4056-class/README.md b/components/unidentified/xteink-x3-x4/battery-charger-tp4056-class/README.md
deleted file mode 100644
index 472875a..0000000
--- a/components/unidentified/xteink-x3-x4/battery-charger-tp4056-class/README.md
+++ /dev/null
@@ -1,84 +0,0 @@
-# "TP4056-class" Li-ion charger — Xteink X3 (part unresolved)
-
-- **Category:** single-cell Li-ion linear charge-management IC.
-- **Manufacturer / part:** **unknown.**
-- **Research status:** ⚠ **One source, and that source hedges.**
-- **Retrieved:** 2026-09-04
-
-## What is established
-
-Exactly one line of evidence:
-
-> 类似TP4056的电池管理芯片
-> *"a battery-management chip similar to the TP4056"*
-> — [`sunwoods/Xteink-X3`](https://github.com/sunwoods/Xteink-X3) BOM, firsthand teardown
-
-**The author explicitly wrote "similar to", not "is".** This record preserves that
-hedge rather than laundering it into a part number.
-
-The TP4056 is an extremely widely second-sourced Chinese linear charger
-(constant-current/constant-voltage, ~1 A programmable, SOP-8 with thermal pad,
-`CHRG`/`STDBY` open-drain status outputs). "TP4056-class" therefore describes a
-**category of interchangeable parts**, not a specific one — which is probably why
-the teardown author phrased it that way.
-
-## What is missing
-
-- **The part number**, and therefore the programmed charge current, float voltage,
-  thermal-regulation behaviour and whether it has a battery-temperature input.
-- **Whether it exposes a status line to the SoC.** The X3's board profile declares
-  **no `batteryChargeStatus` GPIO** — unlike the
-  [X4 Pro and X4 Classic](../../../cellwise/cw2017/README.md), which read a charge
-  `STAT` line on GPIO21. So either the X3's charger status is unconnected, or it
-  is connected to a pin the SDK has not identified.
-- **Whether the X4 uses the same part.** No X4 teardown exists.
-
-## Why the missing status line is interesting
-
-The X3 has the family's best battery *gauge*
-([BQ27220](../../../texas-instruments/bq27220/README.md)) and, apparently, **no
-charge-state signal at all**. The BQ27220 *can* report charge/discharge direction
-through its flags register — which no Xteink firmware reads — so the stock
-firmware may derive charging state from the gauge rather than a GPIO. **Not
-established.**
-
-Note also the physical evidence that a charge indicator exists: an owner
-describes *"the XTEINK where the **led glows red while charging**"* on the back of
-the device ([r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/),
-2026-08-10, firsthand). A TP4056-class part drives exactly such an LED from its
-`CHRG` pin **without host involvement** — which would explain both the LED and the
-absent GPIO.
-
-That is a coherent hypothesis, and it is **not** confirmed.
-
-## What would resolve it
-
-A legible top-marking photograph. The archived teardown includes chip close-ups
-explicitly captioned *"at an angle to better read the chip labels"* —
-**not examined at full resolution.**
-See [`devices/xteink/x3/media.md`](../../../../devices/xteink/x3/media.md).
-
----
-
-## Used By
-
-### [Xteink X3](../../../../devices/xteink/x3/README.md)
-
-Charges a **650 mAh** connectorised cell over the **magnetic pogo-pin
-connector**. Drives a red charge LED visible through the back cover on at least
-some units. No charge-status GPIO is declared in the board profile.
-
-→ [`devices/xteink/x3/features/battery-and-power.md`](../../../../devices/xteink/x3/features/battery-and-power.md)
-
-### [Xteink X4](../../../../devices/xteink/x4/README.md) — **assumed, not evidenced**
-
-The X4 charges over **USB-C** and no teardown of it exists. Whether it carries the
-same charger is **unknown**. Recorded here only so the assumption is visible
-rather than silent.
-
-## Contrast
-
-A fully identified charger of the same class is documented elsewhere in this
-repository at [`components/generic/tp4057`](../../../generic/tp4057/README.md)
-(M5Stack DinMeter) — useful as a reference for what this record would contain if
-the part were known.
diff --git a/components/unidentified/xteink-x3-x4/nfc-tag-iso14443a/README.md b/components/unidentified/xteink-x3-x4/nfc-tag-iso14443a/README.md
deleted file mode 100644
index 09e2885..0000000
--- a/components/unidentified/xteink-x3-x4/nfc-tag-iso14443a/README.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# ISO/IEC 14443A NFC tag — Xteink X3 (part unresolved, **purpose established**)
-
-- **Category:** passive NFC tag, **not connected to the host processor**.
-- **Manufacturer / part:** **unknown.**
-- **Research status:** ⚠ Part unidentified — but **what it is and what it does is
-  now established** from an authoritative maintainer statement plus multiple
-  firsthand owner reports.
-- **Retrieved:** 2026-09-04
-
-## What it is — resolved
-
-**A blank, user-writable passive NFC tag embedded in the device.** It is
-*not* an NFC reader, and it is **electrically independent of the ESP32-C3**.
-
-The decisive statement is from **uxjulia**, maintainer of the CrossInk firmware,
-on the CrossPoint Reader discussion board:
-
-> "The NFC chip on the device is **independent of the firmware**. The iPhone can't
-> read/write from it because of the type of NFC chip that's being used, but you
-> can use Apple's Shortcuts app to **detect** the NFC tag and run an automation.
-> **Android phones seem to have no problem reading/writing to it** though."
-> — [`crosspoint-reader/crosspoint-reader` discussion #2259](https://github.com/crosspoint-reader/crosspoint-reader/discussions/2259), 2026-06-03 · *informed maintainer statement*
-
-Corroborating firsthand owner reports, all from
-[r/xteinkereader `1vit43t`](https://old.reddit.com/r/xteinkereader/comments/1vit43t/) (2026-08-08):
-
-| Report | Type |
-|---|---|
-| *"It's not an NFC reader afaik. Just a **writeable nfc tag, like an embedded NFC sticker**"* | informed interpretation |
-| *"**By default there is no data in the nfc tag** of the xteink3"* | **firsthand ownership** |
-| *"In my case, I **wrote my contact infos**, in case it get lost… Used an NFC writer app on my Android phone, created a contact card format and used it as payload"* | **firsthand ownership, demonstrated** |
-| *"I made a post how I use NFC so when I **tap my phone to it it automatically joins the X3 WiFi and opens the crosspoint manager** in the browser! I use it every time when I want to load up a new book."* | **firsthand, demonstrable project** |
-| *"I knew it could **clone NFC cards**, not encrypted of course"* | hearsay — **unverified**, and implausible for a passive tag |
-
-A second demonstrated use, from the same GitHub discussion: a user built an iOS
-Shortcuts automation to **open `http://crosspoint.local/` when the tag is
-detected**, with a screenshot.
-
-**This resolves the open question recorded earlier in this repository.** The tag
-is a convenience feature for phone hand-off, shipped **blank**, and it is up to
-the owner to write something to it.
-
-## What is still unknown
-
-| Unknown | Note |
-|---|---|
-| **Part number** | Never read from any photograph |
-| **Tag type** | Some type that **iOS can detect but not read or write**, while Android can do both. That asymmetry is a strong clue — it suggests a tag outside iOS's supported NDEF-formatted set, or an unformatted tag — but no source names the type |
-| **Capacity** | Unknown |
-| **Antenna location** | Not identified in either teardown |
-| **Whether the X3 is the only model with it** | No X4/X4 Pro/X4C owner report of NFC was found, and no board profile mentions it |
-
-## Why firmware cannot help
-
-Because the tag is **not on any host bus**, no amount of firmware work exposes it.
-This is worth stating plainly because a user spent effort trying:
-
-> "I did try with claude code to figure out if i can add the functionality to the
-> crosspoint-reader code but no luck, **it could not find the driver for the nfc
-> chip and also scanning the original firmware bin file for the driver didn't
-> work.**"
-> — discussion #2259, 2026-06-03
-
-The search failed because there is nothing to find. That negative result is
-recorded here so nobody repeats it.
-
-## What would resolve the part identity
-
-An Android NFC app that reports tag technology (`NfcA`, `MifareUltralight`,
-`Ndef`) and the tag's UID prefix — a 30-second operation for any owner. Failing
-that, an antenna-coil trace visible in a teardown photograph.
-
-## Do not confuse this with the "Tong Card" / "Nano"
-
-Xteink also sells a **separate product**, the **Tong Card (瞳卡)**, marketed
-internationally as the **Nano**: a battery-less four-colour e-paper display that
-is **powered and written over NFC** and snaps magnetically to a phone. That is a
-distinct device with an NFC-powered display, not this embedded tag. See
-[`devices/xteink/nano/README.md`](../../../../devices/xteink/nano/README.md).
-
----
-
-## Used By
-
-### [Xteink X3](../../../../devices/xteink/x3/README.md)
-
-Fitted; **not on any bus**; blank from the factory. Advertised by the vendor at
-launch as *"NFC support"*
-([r/xteinkereader `1pi6ezd`](https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/), 2025-12-09)
-and listed in the Chinese teardown BOM as `***ISO/IEC 14443a NFC Tag`, asterisked
-by that author as notable.
-
-**The X3 is the only Xteink device evidenced to carry one.**
-
-→ [`devices/xteink/x3/features/nfc.md`](../../../../devices/xteink/x3/features/nfc.md)
diff --git a/components/unidentified/xteink-x3-x4/rtc-ds-series/README.md b/components/unidentified/xteink-x3-x4/rtc-ds-series/README.md
deleted file mode 100644
index 340743b..0000000
--- a/components/unidentified/xteink-x3-x4/rtc-ds-series/README.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# "DS-series" real-time clock @ 0x68 — Xteink X3 (part unresolved)
-
-- **Category:** I²C real-time clock.
-- **Manufacturer:** presumed Maxim/Analog Devices lineage or a second source —
-  **not established**.
-- **Research status:** 🔴 **Active conflict. Three sources, three answers.**
-- **Retrieved:** 2026-09-04
-
-## The conflict
-
-| Source | Class | Claim |
-|---|---|---|
-| FreeInk SDK `BoardConfig.h:915` | firmware driven in production | **`RtcType::Ds3231`** |
-| [Imgur X3 teardown](../../../../devices/xteink/x3/media.md), image 13 | firsthand photograph of the marking | **"DS1307 RTC"** |
-| [`sunwoods/Xteink-X3`](https://github.com/sunwoods/Xteink-X3) BOM | firsthand teardown, Chinese | **"DS系列RTC时钟芯片"** — *DS-series*, **deliberately not narrowed** |
-
-**All three are consistent with I²C address 0x68**, which the DS1307 and the
-DS3231 both use. The address does not discriminate.
-
-## Why the firmware is not decisive either
-
-`XteinkDetect` probes the RTC by reading `DS3231_SEC_REG = 0x00` — the **seconds
-register, which is byte-identical on both parts**. So the code that appears to
-confirm a DS3231 confirms only *"something with a DS-family register 0"*.
-
-The SDK's `Ds3231` label may itself be an unfalsified assumption. A working
-driver is **not** proof of part identity when the two candidates share the
-registers the driver touches.
-
-## Why it matters
-
-| | DS1307 | DS3231 |
-|---|---|---|
-| Timekeeping registers `0x00`–`0x06` | same layout | same |
-| Oscillator | external 32.768 kHz crystal, **uncompensated** | **integrated TCXO**, ±2 ppm |
-| Temperature registers | **none** | `0x11` / `0x12` |
-| Alarms | none | two |
-| Nominal supply | 5 V part | 2.3–5.5 V |
-
-Drift is user-visible on a device that displays a clock — and the X3's launch
-announcement explicitly advertises *"Time display and battery percentage"*.
-A 5 V-nominal part on a 3.3 V board would also be an unusual design choice worth
-knowing about.
-
-## What would resolve it — one register read
-
-**Read registers `0x11` and `0x12`.** The DS3231 returns a temperature there
-(8-bit integer + 2-bit fraction). The DS1307 does not implement them and will
-return whatever its RAM holds or float.
-
-```c
-// inferred, not executed — one I2C read settles a three-way conflict
-Wire.beginTransmission(0x68); Wire.write(0x11); Wire.endTransmission(false);
-Wire.requestFrom(0x68, 2);   // DS3231: plausible temperature. DS1307: RAM/garbage
-```
-
-Alternatively: examine the archived teardown photograph `13-Ay3rpJg.jpg`
-(5760 × 3240) at full resolution and judge whether the caption is supported by
-the image. **That has not been done.**
-
-## Filed under `unidentified/` deliberately
-
-Per the research method: *"Do not assign a guessed part number. Create an
-unidentified/generic record and explain what evidence would resolve it."*
-Filing this under `maxim/ds3231` or `maxim/ds1307` would launder a conflict into
-a fact.
-
----
-
-## Used By
-
-### [Xteink X3](../../../../devices/xteink/x3/README.md)
-
-At **0x68** on the secondary I²C bus **SDA 20 / SCL 0 @ 400 kHz**, shared with the
-[BQ27220 fuel gauge](../../../texas-instruments/bq27220/README.md) (0x55) and the
-[QMI8658 IMU](../../../qst/qmi8658a/README.md) (0x6B).
-
-Also serves as one of the three device-identification fingerprints that
-distinguish an X3 from an [X4](../../../../devices/xteink/x4/README.md) at boot.
-
-**Backup power source is unknown** — no supercap or coin cell is identified in
-either teardown.
-
-→ [`devices/xteink/x3/features/rtc.md`](../../../../devices/xteink/x3/features/rtc.md)
-→ [`devices/xteink/x3/gaps-and-conflicts.md`](../../../../devices/xteink/x3/gaps-and-conflicts.md)
-
-## Family contrast
-
-The S3 devices use a **BM8563 at 0x51** (PCF8563-register-compatible) — a
-different part at a different address. The **[X4](../../../../devices/xteink/x4/README.md)
-has no RTC at all.** Four devices, three answers.
diff --git a/components/unidentified/xteink-x3-x4/spi-nor-flash-128mbit-puya/README.md b/components/unidentified/xteink-x3-x4/spi-nor-flash-128mbit-puya/README.md
deleted file mode 100644
index 3f4209e..0000000
--- a/components/unidentified/xteink-x3-x4/spi-nor-flash-128mbit-puya/README.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Puya 128 Mbit SPI NOR flash — Xteink X3 / X4 (part number unresolved)
-
-- **Category:** external SPI NOR flash holding the ESP32-C3's firmware.
-- **Manufacturer:** **Puya Semiconductor (普冉半导体)** — read from the chip marking.
-- **Research status:** ⚠ **Maker and density established; part number never read.**
-- **Retrieved:** 2026-09-04
-
-## What is established
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **Puya** | **[CN-TD]** `sunwoods/Xteink-X3` BOM: *"PUYA 128Mbit Flash"* |
-| Density | **128 Mbit = 16 MB** | **[EN-TD]** Imgur image 10 caption: *"128MBit (16MB) flash for firmware"*; **[CN-TD]** BOM |
-| Role | External firmware flash for the ESP32-C3 | both |
-| Interface | SPI NOR (implied by the SoC's boot path) | inference |
-| **Confirmed capacity** | **16,777,216 bytes** | **[DUMP]** the X4 factory image is *exactly* this size |
-
-Three independent lines of evidence agree on 16 MB: two teardown photographs and
-the byte length of an actual flash dump.
-
-## What is missing
-
-**The part number.** Neither teardown transcribes a full marking. Puya's 16 MB
-SPI NOR parts are in the `P25Q128*` family, but **no specific part is asserted
-here** — that would be promoting a plausible candidate to a finding, which the
-research method forbids.
-
-Practical consequences of not knowing it:
-- **Maximum SPI clock and supported read modes (QPI/QIO/DIO) are unknown.** ESP-IDF
-  flash timing settings cannot be validated against the part.
-- **Erase/write endurance and sector geometry are unknown.**
-- **Whether the part supports the SFDP parameters the bootloader assumes** is
-  unverified — relevant because Puya parts have a documented history of
-  non-standard behaviour in some ESP-IDF versions.
-
-## What would resolve it
-
-A legible photograph of the chip's top marking. The archived teardown images
-include chip close-ups at up to 5760 × 3240
-([`devices/xteink/x3/media.md`](../../../../devices/xteink/x3/media.md), images
-10 and 11: *"at an angle to better read the chip labels"*) — **these have not been
-examined at full resolution.** This is the cheapest open identification in the
-whole subject.
-
-Failing that: `esptool.py flash_id` on a USB-unlocked unit returns the JEDEC
-manufacturer and device ID, which maps directly to a part number.
-
-```bash
-# inferred, not executed — one command settles it
-esptool.py --chip esp32c3 --port /dev/ttyUSB0 flash_id
-```
-
----
-
-## Used By
-
-### [Xteink X4](../../../../devices/xteink/x4/README.md)
-
-External firmware flash. Partition table parsed from the dump: `nvs` `0x9000` ·
-`otadata` `0xE000` · `app0` `0x10000` (6400 KiB) · `app1` `0x650000` (6400 KiB) ·
-**`spiffs` `0xC90000` (3456 KiB)** · `coredump` `0xFF0000`.
-
-The unusually large SPIFFS is consistent with the stock firmware serving the
-on-device web file manager (`http://bofi.xteink.cn/index.html`) out of flash.
-
-→ [`devices/xteink/x4/factory-firmware.md`](../../../../devices/xteink/x4/factory-firmware.md)
-
-### [Xteink X3](../../../../devices/xteink/x3/README.md)
-
-Same part, same board family — this is the device both teardowns photographed.
-The X3's own partition layout is **not established**; the X4's is assumed but
-unverified.
-
-→ [`devices/xteink/x3/factory-firmware.md`](../../../../devices/xteink/x3/factory-firmware.md)
diff --git a/components/waveshare/3.97inch-e-paper/README.md b/components/waveshare/3.97inch-e-paper/README.md
deleted file mode 100644
index a774684..0000000
--- a/components/waveshare/3.97inch-e-paper/README.md
+++ /dev/null
@@ -1,216 +0,0 @@
-# Waveshare 3.97inch e-Paper (raw panel module)
-
-- **Category:** 3.97-inch active-matrix electrophoretic (AM EPD) display module — 800 × 480, bi-stable, pure-reflective, SPI
-- **Driver IC:** **[Solomon Systech SSD1677](../../solomon-systech/ssd1677/README.md)**, bonded on (COG)
-- **Vendor part number:** **not published.** Waveshare sells and documents this panel only as "3.97inch e-Paper"; no supplier or module part number appears on the storefront, in the docs, in the manual, or in the schematic's text layer
-- **Document status:** manual **Rev 1.0, 2025-04-24** — revision history reads "New creation", so this is the first published revision
-- **Research status:** manual retained in [`artifacts/`](artifacts/). **Its text layer is offset-encoded and must be decoded before use** — see [below](#the-manual-has-a-hostile-text-layer)
-- **Retrieved:** 2026-09-01. **Nothing verified on hardware.**
-
-Filed under `components/waveshare/` rather than under a board because **it is a panel,
-not a board** — it is sold both as a standalone raw panel (`3.97inch e-Paper HAT+`
-product family, from whose file directory the manual is served) and fitted to the
-[ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md).
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[MAN]** | `artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf`, decoded text layer, cited by section number where the document gives one | `executed-success` for the decode and transcription; `not-tested` for the values themselves |
-| **[SCH]** | The host board's schematic, `devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/` | `executed-success` for the extraction |
-| **[SRC]** | Waveshare driver source at a cited `file:line` | `executed-success` for the read |
-| **[STORE]** | Waveshare storefront/docs prose | `reported-working` — vendor claim |
-
-## Specifications
-
-| Property | Value | Evidence |
-|---|---|---|
-| Screen size | 3.97 inch | **[MAN]** |
-| Resolution | **800 × 480** | **[MAN]**, **[SRC]** `EPD_3in97.h:35–36` |
-| **Active area** | **86.40 × 51.84 mm** | **[MAN]** |
-| Outline | 56.24 (H) × 96.62 (V) × 0.92 (D) mm | **[MAN]** |
-| Pixel pitch | 0.108 × 0.108 mm | **[MAN]** §4-4 |
-| **DPI** | **235** | **[MAN]** |
-| Weight | 10.44 ± 0.5 g | **[MAN]** |
-| Colours | Black / white | **[STORE]** |
-| Greyscale | **4 levels** | **[STORE]**; the driver exposes `Init_4GRAY` / `Display_4Gray` **[SRC]** |
-| Viewing angle | > 170° | **[STORE]** |
-| Interface | 3-wire (9-bit) or 4-wire (8-bit) SPI, selected by `BS1` | **[MAN]** §6.4 |
-| Core logic voltage | 1.7 / **1.8** / 1.9 V | **[MAN]** |
-| Operating temperature | **0 to +50 °C** | **[MAN]** |
-| Storage temperature | −25 to +70 °C | **[MAN]** |
-| Optimal storage humidity | 55 ± 10 % RH | **[MAN]** |
-
-### Timing and power
-
-| Parameter | Value | Conditions | Evidence |
-|---|---|---|---|
-| 4-grey update | **3 s** | 23 °C | **[MAN]** |
-| Partial update | **0.3 s** | 23 °C | **[MAN]** |
-| Typical power | **36 mW** | V = 3.0 V | **[MAN]** |
-| Deep-sleep power | **0.003 mW** | V = 3.0 V | **[MAN]** |
-| Peak current | **120 mA** | — | **[MAN]** |
-
-The manual states these were measured with a **Tektronix TCP0030A** current probe
-under a defined pattern transition — unusually specific for a panel document, and
-worth preserving because it makes the figures comparable to nothing else that does
-not state the same.
-
-> **These are panel figures, not board figures.** The host board's storefront quotes
-> different, slower numbers (full 3.5 s, fast 2.8 s, partial 0.6 s). That is expected
-> — a board number includes the host's SPI transfer — but neither set is a
-> measurement you can rely on. See
-> [C-WS6](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws6--refresh-times-disagree-between-module-and-panel-documents).
-
-## What the panel provides on its own
-
-From the manual's own description **[MAN]**:
-
-> The display is capable to display image at 1-bit white and black full display
-> capabilities. The 3.97 inch active area contains 800 × 480 pixels. The module is a
-> TFT-array driving electrophoresis display, with integrated circuits including gate
-> driver, source driver, MCU interface, timing controller, oscillator, DC-DC, SRAM,
-> LUT, and VCOM.
-
-Note **"1-bit white and black"** in the module's own overview, against the marketed
-**4 greyscale**. This is the same tension the
-[DKE DEPG0397BBS770F3 record](../../dke/depg0397bbs770f3/README.md) documents for the
-PaperMono's panel, where the manual's optical table says 2 grey levels and the vendor
-markets 4. **The pattern recurs across 3.97" panels from different vendors** — read
-it as "4-grey is achievable with the right waveform, 1-bit is what the module
-guarantees", and treat 4-grey quality as something to verify per unit.
-
-Because the SSD1677 integrates the **DC-DC, oscillator, SRAM, LUT and VCOM**
-generation, a host board needs no EPD boost converter — it supplies logic power and
-the SPI lines, and the panel's `GDR`/`RESE` pins plus an inductor close the boost
-loop. The host board's FPC connector `J2` carries `VGH`, `VGL`, `VSH1`, `VSH2`,
-`VSL`, `VCOM`, `VPP`, `GDR` and `RESE`, consistent with that topology **[SCH]**.
-
-## Pin interface
-
-The manual's pin table names, among others:
-
-| Pin | Role | Evidence |
-|---|---|---|
-| `VDDIO` (15) | Power supply for interface logic pins; should be tied to `VCI` | **[MAN]** |
-| `VDDP` (16) | Power supply for the chip | **[MAN]** |
-| `VDD` (18) | Core logic, regulated internally from `VCI`; needs a capacitor | **[MAN]** |
-| `BSI` (8) | **Bus interface selection**: H = 3-wire 9-bit SPI, L = 4-wire 8-bit SPI | **[MAN]** §5-5 |
-| `RESE` (3) | Current-sense input for the boost control loop | **[MAN]** |
-
-The SSD1677 additionally offers an **I²C master interface to read an external
-temperature sensor** **[MAN]** — relevant because e-paper waveforms are strongly
-temperature-dependent, and a panel that can read its own ambient temperature can
-select its LUT without host involvement. Whether the host board wires this is
-**not established**.
-
-## The manual has a hostile text layer
-
-**Do not `grep` this PDF and believe the result.** The document embeds two subset
-fonts whose code points are uniformly displaced from the real characters:
-
-| Font | Offset | Raw | Decoded |
-|---|---|---|---|
-| A | **+26** | `OTINK 6GVKX` | `inch e-Paper` |
-| B | **+29** | `LQFKH 3DSHU` | `inch e-Paper` |
-
-Naive extraction yields text that is **human-legible but wrong** — the most dangerous
-PDF failure mode, because it does not look like a failure. The method's rule applies
-literally here: *validate the text layer against a known heading before transcribing
-any value.*
-
-The decoder used, and the validation against the cover heading `3.97inch e-Paper`, is
-[`tools/deshift.py`](../../../devices/waveshare/esp32-s3-epaper-3.97/tools/deshift.py)
-with the procedure in
-[`commands.md` §6](../../../devices/waveshare/esp32-s3-epaper-3.97/commands.md).
-**Only after the heading validated was `Driver IC: SSD1677` — or any number above —
-transcribed.**
-
-## Is this the same panel as the M5Stack PaperMono's?
-
-| Property | This panel | [DKE `DEPG0397BBS770F3`](../../dke/depg0397bbs770f3/README.md) |
-|---|---|---|
-| **Active area** | **86.40 × 51.84 mm** | **51.84 × 86.40 mm** |
-| **DPI** | **235** | **235** |
-| **Driver IC** | **SSD1677** | **SSD1677** |
-| Resolution | 800 × 480 | 480 × 800 |
-| Greyscale marketed / manual | 4 / "1-bit" | 4 / 2 |
-| Part number | **not published** | `DEPG0397BBS770F3` |
-
-Active area matches **to 0.01 mm** transposed; DPI is identical; the controller is
-identical. **This is `inferred` and deliberately not asserted.** It is equally
-consistent with one panel sold to two board vendors, two panels built to a common
-ESL-market reference, or coincidence in a size where the controller dictates the
-geometry.
-
-What would settle it: a photograph of the FPC marking on either board, or Waveshare
-publishing a part number. Tracked as
-[C-WS8](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws8--is-this-the-same-panel-as-the-papermonos).
-
-### One place the two documents actively disagree
-
-This manual states **"Resolution: 800 gate × 480 source"** **[MAN]** §4-3. The DKE
-record derives the **opposite** — 800 *source* × 480 *gate* — from SSD1677 register
-values (`0x44` sets `XEA = 799`; the frame is 48 000 bytes = 800 × 480 / 8), which is
-stronger evidence than a specification line.
-
-Unresolved. Practical impact is low because drivers address the framebuffer, but it
-matters if you write your own controller init. See
-[C-WS7](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws7--gate-versus-source-orientation).
-
-## Software
-
-The reference driver is Waveshare's own `EPD_3in97.cpp/.h`
-([repo](https://github.com/waveshareteam/ESP32-S3-ePaper-3.97) @ `9b12d40`), which
-exposes:
-
-| Function group | Members |
-|---|---|
-| Init | `Init`, `Init_Fast`, `Init_Partial`, `Init_4GRAY` |
-| Display | `Display`, `Display_Base`, `Display_Fast`, `Display_Fast_Base`, `Display_Partial`, `Display_4Gray`, `WritePicture_4Gray` |
-| Windowed | `V2_Display_Window`, `V2_Display_Window_Base` |
-| Clear | `Clear`, `Clear_Black` |
-
-The `_Base` variants write the previous-image buffer, which is what makes correct
-partial refresh possible on an SSD1677 — the controller diffs old against new. The
-presence of `V2_` names suggests lineage from Waveshare's generic e-paper driver
-family rather than code written for this panel.
-
-Generic SSD1677 behaviour, register map and the **DC-balance hazard** are documented
-once, in the [SSD1677 record](../../solomon-systech/ssd1677/README.md) — not repeated
-here.
-
-## Artifacts
-
-| File | Bytes | SHA-256 | Source | Retrieved |
-|---|---|---|---|---|
-| [`artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf`](artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf) | 2 774 287 | `4f756734dbfa7485c57e7ab7124f59f0afb00ca2600cda24a2285f02e4ab05cf` | `https://files.waveshare.com/wiki/3.97inch_e-Paper_HAT%2B/3.97inch_e-Paper.pdf` | 2026-09-01 |
-
-Validated as a real PDF by magic bytes (`%PDF-`), not by HTTP status.
-**Licence `unknown`** — the document states no terms. Disposition: `repository`.
-
-## Used by
-
-### [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-
-Fitted as the integrated display, on FPC connector `J2`. Driven over **4-wire SPI**
-from the ESP32-S3: `EPD_SCK` GPIO11, `EPD_DIN` GPIO12, `EPD_CS` GPIO10, `EPD_DC`
-GPIO9, `EPD_RST` GPIO46, `EPD_BUSY` GPIO3 — corroborated by both the schematic and
-`DEV_Config.h`. Panel supply comes from an
-[AXP2101](../../x-powers/axp2101/README.md) rail (`EPD_VCC_AXP`); there is **no
-GPIO-controlled panel power pin** (`EPD_PWR_PIN -1`), so power gating is a PMIC
-operation. Full map in
-[pinouts-and-buses.md](../../../devices/waveshare/esp32-s3-epaper-3.97/pinouts-and-buses.md).
-
-### Sold standalone
-
-As a raw panel in the `3.97inch e-Paper HAT+` family — the manual is served from that
-product's file directory. Those products were **not researched** in this pass; only
-the panel document was taken.
-
-## See also
-
-- [SSD1677 controller](../../solomon-systech/ssd1677/README.md)
-- [DKE DEPG0397BBS770F3](../../dke/depg0397bbs770f3/README.md) — the comparable panel on the PaperMono
-- [Waveshare documentation-sourcing guide](../../../vendors/waveshare/README.md)
-- [All components](../../README.md)
diff --git a/components/waveshare/3.97inch-e-paper/artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf b/components/waveshare/3.97inch-e-paper/artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf
deleted file mode 100644
index 8902c7e..0000000
Binary files a/components/waveshare/3.97inch-e-paper/artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf and /dev/null differ
diff --git a/components/winbond/w25q128jv/README.md b/components/winbond/w25q128jv/README.md
index 3b012fa..06476df 100644
--- a/components/winbond/w25q128jv/README.md
+++ b/components/winbond/w25q128jv/README.md
@@ -315,8 +315,6 @@ The WSON-8 6×5 mm SPI NOR footprint is one of the most standardised in the indu
 
 ## Used By
 
-- **[LilyGO T-Display-S3 family](../../../devices/lilygo/t-display-s3-shared/README.md)** — designator `U3` on the [T-Display-S3](../../../devices/lilygo/t-display-s3/README.md) (part string `W25Q128JV` on `T_Display_S3.pdf` @ `ec889e7`), and likewise on the [AMOLED](../../../devices/lilygo/t-display-s3-amoled/README.md) V2.0 sheet, [AMOLED Plus](../../../devices/lilygo/t-display-s3-amoled-plus/README.md), [Long](../../../devices/lilygo/t-display-s3-long/README.md), [Pro](../../../devices/lilygo/t-display-s3-pro/README.md), [T4-S3](../../../devices/lilygo/t4-s3/README.md) and [AMOLED Lite](../../../devices/lilygo/t-display-amoled-lite/README.md). QIO at 80 MHz; PlatformIO board manifest declares `memory_type qio_opi`, `flash_size 16MB`, `partitions default_16MB.csv`. **Note the conflict:** the *older* 1.91″ AMOLED schematic shows a **`W25Q32`** (4 MB) in the same position while every LilyGO README and store listing says 16 MB — see [that board's gaps](../../../devices/lilygo/t-display-s3-amoled/gaps-and-conflicts.md). Verify with `esptool.py flash_id` before relying on 16 MB.
-
 ### `W25Q128JVPIQ` — Waveshare ESP32-S3-Knob-Touch-LCD-1.8
 
 [Device record](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) — reference designator **`U3`**, the ESP32-S3's application flash, on the dedicated SPI0/1 flash interface powered from `VDD_SPI`. Marketed as "16MB Flash". See [Pinouts and buses § Bus inventory](../../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/pinouts-and-buses.md).
diff --git a/components/worldsemi/ws2812/README.md b/components/worldsemi/ws2812/README.md
deleted file mode 100644
index 0daf955..0000000
--- a/components/worldsemi/ws2812/README.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# WS2812 — addressable RGB LED
-
-> Schematic value string on the M5Stack Stamp-S3 and Stamp-S3A: **`WS2812`** exactly.
-> Record created **2026-09-04**. Manufacturer conventionally **Worldsemi** (世微 / WorldSemi
-> Co., Ltd), which originated the family; the part is widely second-sourced and the exact
-> package variant on these modules is **not established** — see *Gaps*.
-
-## Function
-
-A single-wire addressable RGB LED: a 24-bit (GRB) shift register, a constant-current driver and
-three LED dice in one package. Data enters on `DI`, the first 24 bits are consumed, and the
-remainder is retransmitted on `DO` — so devices chain without any addressing.
-
-Timing is encoded in pulse width at roughly 800 kbit/s and is tight enough that bit-banging is
-unreliable under interrupts; on ESP32 the **RMT** peripheral is the normal driver.
-
-## Key capabilities
-
-| Property | Value |
-|---|---|
-| Interface | single-wire, ~800 kbit/s, self-clocked |
-| Colour order | **GRB**, 8 bits each |
-| Supply | 3.3 V on these modules (many WS2812 variants specify 3.5–5.3 V — see *Gaps*) |
-| Pins | `VDD`, `GND`, `DI`, `DO` — 4 |
-| Reset | a low period of ≳ 50 µs latches the frame |
-
-## Pinout as drawn on the M5Stack Stamp modules
-
-| Pin | Name | Stamp-S3 v0.2 | Stamp-S3A v0.3.3 |
-|---|---|---|---|
-| 1 | `DO` | `SK_DOUT` (no downstream device) | `SK_DOUT` |
-| 2 | `GND` | GND | GND |
-| 3 | `DI` | `SK_DIN` ← **GPIO 21** | `SK_DIN` ← **GPIO 21** |
-| 4 | `VDD` | **`VDD_3V3`** | **`BL_3V3`** |
-
-Decoupled by C17, 10 µF/10 V.
-
-## ⚠ The rail change is the whole story
-
-This part is the reason the Cardputer family has a documented behavioural quirk, and it is
-visible only by **diffing two schematics**:
-
-| | StampS3 `v0.2` (Cardputer v1.0) | Stamp-S3A `v0.3.3` (Cardputer v1.1, ADV) |
-|---|---|---|
-| WS2812 `VDD` net | **`VDD_3V3`** — always on | **`BL_3V3`** |
-| `BL_3V3` source | — | **AW35122FDR** load switch, `EN` = `DISP_BL` = **GPIO 38** |
-| Also on that rail | — | the **LCD backlight** |
-| Consequence | the LED works whenever the board is on | **PWM-dimming the backlight chops the LED's supply** |
-
-M5Stack documents the consequence on the **Cardputer v1.1** page:
-
-> "Since RGB and LCD backlight share the same power source, when the LCD backlight brightness is
-> below 100%, RGB will not be powered properly. Please use the RGB function when the backlight is
-> at full brightness."
-
-…and **omits it from the Cardputer ADV page**, which instead says only *"set GPIO38, which
-controls this switch, to a high level"* before using the LED. Both describe the same
-AW35122FDR. The omission is a vendor documentation defect, recorded at
-[`devices/m5stack/cardputer-adv/gaps-and-conflicts.md`](../../../devices/m5stack/cardputer-adv/gaps-and-conflicts.md) §C4.
-
-The trade was deliberate: gating the LED rail is part of how the Stamp-S3A gets its sleep current
-from **0.26 µA to 0.15 µA**.
-
-Also removed between the two revisions: a solder jumper **`JP4`** sat beside the WS2812 on
-v0.2 and is absent on v0.3.3.
-
-## Software
-
-| Option | Note |
-|---|---|
-| `M5Unified` | `_pin_table_rgb` gives `GPIO_NUM_21` for `board_M5Cardputer` and `board_M5CardputerADV`; `M5.Display`-adjacent LED APIs handle the timing |
-| `xylopyrographer/LiteLED` `^1.2.0` | what **Bruce** uses (`-DHAS_RGB_LED=1 -DRGB_LED=21`) |
-| `FastLED`, `Adafruit_NeoPixel`, `led_strip` (ESP-IDF) | all standard; all use RMT on ESP32-S3 |
-
-**On the Stamp-S3A you must raise GPIO 38 first**, or the LED has no supply — and raising it also
-turns the backlight fully on. There is no way to have a dark screen and a lit status LED.
-
-## Used By
-
-### M5Stack Stamp-S3 and Stamp-S3A modules
-
-[`components/m5stack/stamp-s3`](../../m5stack/stamp-s3/README.md) ·
-[`components/m5stack/stamp-s3a`](../../m5stack/stamp-s3a/README.md)
-*(both created by a concurrent session)*
-
-Designator **U3** on both. Data from GPIO 21; supply as tabulated above. `DO` goes to a net
-named `SK_DOUT` with no downstream device — a single LED, not a chain, but the output is
-available at the module edge on v0.2 via `JP4`.
-
-### M5Stack Cardputer v1.0, v1.1, ADV
-
-[`devices/m5stack/cardputer-v1.0`](../../../devices/m5stack/cardputer-v1.0/README.md) ·
-[`devices/m5stack/cardputer-v1.1`](../../../devices/m5stack/cardputer-v1.1/README.md) ·
-[`devices/m5stack/cardputer-adv`](../../../devices/m5stack/cardputer-adv/README.md)
-
-All three inherit the LED from their Stamp module; none adds one on the mainboard. GPIO 21 on all
-three. The v1.0 is **the only Cardputer whose RGB LED is independent of the backlight.**
-
-## Substitutes
-
-| Part | Note |
-|---|---|
-| WS2812B, WS2812C, WS2812C-2020 | package and supply-range variants of the same protocol |
-| SK6812 | compatible protocol, slightly different timing tolerance; RGBW variants exist |
-| **APA102 / SK9822** | two-wire (clock + data) — **not protocol-compatible**, but immune to timing jitter |
-| Any 800 kbit/s single-wire LED | check the reset-period requirement, which has shortened in newer parts |
-
-Related record already in this repository:
-[`generic/rs-c1415mbar-rgb-led`](../../generic/rs-c1415mbar-rgb-led/README.md).
-
-## Gaps
-
-* **No datasheet retrieved**, and the exact variant is unknown. The schematic says `WS2812`
-  without a suffix; the physical part could be a WS2812B or a small WS2812C-2020. **This matters**
-  — the original WS2812 specifies 3.5 V minimum supply, while these modules run it at **3.3 V**,
-  which is out of spec for some variants and in spec for others (WS2812C is specified from 3.0 V).
-  A board photograph or a BOM would settle it.
-* Manufacturer not confirmed; the family is heavily second-sourced.
-* No measurement of actual brightness, current draw or timing margin at 3.3 V.
diff --git a/components/x-powers/axp2101/README.md b/components/x-powers/axp2101/README.md
deleted file mode 100644
index dde162f..0000000
--- a/components/x-powers/axp2101/README.md
+++ /dev/null
@@ -1,161 +0,0 @@
-# X-Powers AXP2101
-
-- **Category:** highly integrated single-cell Li-ion **power-management IC** — charger, multi-rail regulator (DC-DCs + ALDO/BLDO/DLDO/CPUSLDO), power-key controller, ADC/fuel-gauge inputs, watchdog, backup-battery charger
-- **Manufacturer:** X-Powers (Shenzhen X-Powers Technology / 芯智慧)
-- **Host interface:** I²C, slave address **`0x34`**
-- **Document status:** datasheet **V1.4, English** — retained in [`artifacts/`](artifacts/)
-- **Research status:** **stub-plus.** The datasheet is held and the part's identity on one board is firmly established, but the register map has **not** been mined and no independent audit of the vendor driver against the datasheet has been done. What is written below is what the evidence supports.
-- **Retrieved:** 2026-09-01. **Nothing verified on hardware.**
-
-## Why this record exists: a marketing-versus-silicon conflict
-
-This part is documented here primarily because **Waveshare does not call it by its
-name.** Both the storefront and the official documentation for the
-[ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-describe the PMIC as a **"TG28"**:
-
-> "Onboard **TG28** power management chip … supports outputting multiple configurable
-> voltages, and integrates charging and battery management functions"
-
-Two higher-authority sources say otherwise:
-
-| Source | Evidence | Class |
-|---|---|---|
-| **Board schematic** | Part label `AXP2101`, with nets `ALDOIN`, `ALDO1`–`ALDO4`, `BLDOIN`, `BLDO1`–`BLDO2`, `DLDO1/DC1SW`, `DLDO2/DC4SW`, `CPUSLDO`, `VSYS`, `PWRON`, `PWROK`, `VBACKUP` — **these are the AXP2101's own pin names** | primary, design data |
-| **Waveshare's own firmware** | Component directory named `axpPower/`; `static XPowersPMU axp2101;`; `axp2101.begin(AXP2101_SLAVE_ADDRESS, …)`; vendored `REG/AXP2101Constants.h` and `XPowersAXP2101.tpp` | primary, source |
-
-Under this repository's Waveshare trust order
-([vendor guide §4](../../../vendors/waveshare/README.md): schematic > demo source >
-wiki > storefront), **both higher-ranked sources agree against both lower-ranked
-ones**. The fitted part is an AXP2101.
-
-**What "TG28" refers to is unexplained.** No datasheet, product page or registry
-entry for a PMIC of that name was found in this pass. It may be a marking variant, a
-second-source, or an error copied from another product. **No `tg28` component record
-has been created** — that would be a part number promoted from marketing copy, which
-the method's
-[evidence-discipline rules](../../../.agents/skills/hardware-device-research/SKILL.md#evidence-discipline-and-known-failure-modes)
-forbid. Recorded as an open question in
-[C-WS2](../../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws2--tg28-versus-axp2101).
-
-## Rails observed on a real design
-
-Named on the ESP32-S3-ePaper-3.97 schematic. This is **that board's** use of the
-part, not a general pinout:
-
-| Rail | Present | Configured to | Evidence |
-|---|---|---|---|
-| `DC1` (via `DLDO1/DC1SW`) | yes | **3300 mV** | vendor source `axp_prot.cpp:53` |
-| `ALDO1` | yes | **3300 mV** | `:55` |
-| `ALDO2` | yes | **3300 mV** | `:56` |
-| `ALDO3` | yes | **3300 mV** | `:57` |
-| `ALDO4` | yes | not set in the sampled source | schematic |
-| `BLDO1`, `BLDO2` | yes | not set in the sampled source | schematic |
-| `CPUSLDO` | yes | — | schematic |
-| `VBACKUP` | yes | RTC coin cell, charge target **3000 mV** | `:116` |
-| `VSYS`, `PWRON`, `PWROK` | yes | power sequencing and key | schematic |
-
-## Capabilities exercised by a shipping driver
-
-Read from Waveshare's `axp_prot.cpp` at commit `9b12d40`. These are **firmware
-settings, not silicon limits** — a different program may choose differently.
-
-| Capability | Setting | Line |
-|---|---|---|
-| VBUS voltage limit | 4.36 V | `:46` |
-| VBUS current limit | **1500 mA** | `:47` |
-| System power-down voltage | 2600 mV | `:50` |
-| Precharge current | 50 mA | `:101` |
-| Constant-current charge | **200 mA** | `:102` |
-| Termination current | 25 mA | `:103` |
-| Charge target voltage | **4.2 V** | `:106` |
-| Power-key press-off hold | 4 s | `:61` |
-| Power-key press-on hold | 1 s | `:76` |
-| Watchdog | 4 s, **IRQ to pin** | `:110`–`:112` |
-| Backup-battery charging | **enabled**, 3.0 V | `:116`–`:117` |
-| Low-battery warning | 10 % | `:119` |
-| Measurements enabled | die temperature, battery detect, VBUS voltage, battery voltage, system voltage | `:91`–`:95` |
-| Charge LED | off | `:98` |
-
-That list is a reasonable summary of what the part does: **it charges a cell, powers
-several rails, debounces a power button, watches the system, and measures itself.**
-
-### Two things worth flagging to anyone using this part
-
-Both `inferred` from reading the vendor driver, neither reproduced:
-
-1. **The watchdog is enabled and never fed** in the sampled code — `clrWatchdog()` is
-   present but commented out at `:113`. Configured as `WDT_IRQ_TO_PIN`, so it raises
-   an interrupt rather than resetting, and is therefore **a latent trap, not an
-   active defect**. If a derived design promotes the watchdog to reset without adding
-   a feed, it becomes a 4-second reboot loop.
-2. **Backup-battery charging is enabled unconditionally.** If a **non-rechargeable**
-   coin cell is fitted to the RTC backup header, this charges a primary cell. Worth a
-   warning in any product derived from a board that does this.
-
-## What has *not* been done
-
-Stated plainly so the next pass knows where to start:
-
-- **The datasheet has not been mined.** No register map, no electrical limits, no
-  package or thermal data has been transcribed from the held V1.4 document.
-- **No audit of XPowersLib against the datasheet.** The method's
-  [step 10](../../../.agents/skills/hardware-device-research/SKILL.md#10-audit-vendor-firmware-and-driver-source-against-the-primary-documents)
-  asks for exactly that, and it is the obvious next piece of work — the library is
-  widely used well beyond Waveshare.
-- **No lifecycle, pricing, packaging or availability information.**
-- **No comparison** against the obvious alternatives (AXP192/AXP202 in the same
-  family; BQ25896 and SY6970, whose constants XPowersLib also ships).
-
-## Artifacts
-
-| File | Bytes | SHA-256 | Source | Retrieved | Version |
-|---|---|---|---|---|---|
-| [`artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf`](artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf) | 1 554 740 | `9e51d16d84d905c32a001a123be8e6c58213ee21e42d5bdb1458b731dba10f6d` | `https://raw.githubusercontent.com/lewisxhe/XPowersLib/master/datasheet/AXP2101_Datasheet_V1.4_en.pdf` | 2026-09-01 | **V1.4, English** |
-
-**This is a community mirror, not the manufacturer's copy.** X-Powers publishes no
-accessible primary URL that this pass could find. Two direct attempts failed and
-**neither was retained under a `.pdf` name**:
-
-| Attempt | Result |
-|---|---|
-| `files.waveshare.com/wiki/common/AXP2101.pdf` | HTTP 404, body was XML |
-| `github.com/lewisxhe/XPowersLib/raw/master/datasheet/AXP2101_Datasheet_V1.0_en.pdf` | HTTP 404, body was **267 330 bytes of HTML** — a size that would pass a naive length check |
-
-The working filename was found by listing the repository directory through the GitHub
-API rather than guessing. Validated by magic bytes (`%PDF-`).
-
-**Licence `unknown`.** The document states no terms; the hosting library is MIT but a
-library's licence does not govern a manufacturer datasheet it redistributes.
-Disposition: `repository`. If X-Powers' own copy is later located, keep both and hash
-them — mirrors of this document may well differ by revision, as
-[has already happened](../../nxp/pcf85063a/README.md) with another datasheet on the
-same board.
-
-## Used by
-
-- [LilyGO T-Display AMOLED Lite (1.47″)](../../../devices/lilygo/t-display-amoled-lite/README.md) — designator `U5`, the **only full PMU anywhere in the [LilyGO T-Display-S3 family](../../../devices/lilygo/t-display-s3-shared/README.md)**. It is fitted because that board's [SH8501B](../../shenghe-microelectronics/sh8501b/README.md) AMOLED panel runs at **1.8 V** behind an RS0108 level translator and needs rails the family's other boards do not. Driven with `lewisxhe/XPowersLib`; LilyGO ships `examples/PMU_ADC` and `examples/PMU_Interrupt` marked *“only support 1.47-inch AMOLED”*. PMU interrupt GPIO3; I²C SDA GPIO1 / SCL GPIO2 per `LilyGo-Display-IDF/main/product_pins.h` @ `b1a1cc54994bf1b417e3bb30c437bbe1036bff7f`. Every other board in that family uses a plain charger instead — [SY6970](../../silergy/sy6970/README.md), [BQ25896](../../texas-instruments/bq25896/README.md) or a linear [TP4065-class part](../../nanjing-top-power/tp4065/README.md). *(Added 2026-09-07.)*
-
-### [Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-
-The board's **sole** power-management device. On the shared I²C bus at `0x34`
-(GPIO41 SDA / GPIO42 SCL), with `PWR_IRQ` on GPIO38, `ESP_CHG` on GPIO2 and
-`PWR_OUT` on GPIO1. It owns:
-
-- the 3.3 V logic rail and the e-paper panel supply (`EPD_VCC_AXP`),
-- charging of the MX1.25/PH1.25 3.7 V Li-ion on header `H3`,
-- charging of the RTC backup cell on header `H4`,
-- the **PWR button**, which is why that button is described as programmable — it is a
-  PMIC input, not a GPIO.
-
-Consequence for developers: **on this board the PMIC gates the display.** Ignoring
-the AXP2101 makes battery and panel behaviour inexplicable. Details in
-[pinouts-and-buses.md § Power domains](../../../devices/waveshare/esp32-s3-epaper-3.97/pinouts-and-buses.md#power-domains)
-and [development.md](../../../devices/waveshare/esp32-s3-epaper-3.97/development.md).
-
-Marketed by Waveshare as "TG28" — see the [conflict](#why-this-record-exists-a-marketing-versus-silicon-conflict).
-
-## See also
-
-- [XPowersLib](https://github.com/lewisxhe/XPowersLib) — the de-facto driver, vendored by Waveshare
-- [All components](../../README.md)
diff --git a/components/x-powers/axp2101/artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf b/components/x-powers/axp2101/artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf
deleted file mode 100644
index 8480539..0000000
Binary files a/components/x-powers/axp2101/artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf and /dev/null differ
diff --git a/components/xlsemi/xl9555/README.md b/components/xlsemi/xl9555/README.md
deleted file mode 100644
index d51a1c0..0000000
--- a/components/xlsemi/xl9555/README.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# XL9555 — 16-bit I²C GPIO expander
-
-- **Category:** I²C to 16-bit parallel I/O expander, interrupt-capable
-- **Manufacturer:** filed here under **XLSEMI** to match this repository's existing
-  `components/xlsemi/xl9555/artifacts/` directory, which already held
-  `xl9555-datasheet-rev-2.3.pdf` before this pass. *Attribution caution:* the XL9555 is
-  variously attributed to XLSEMI and to Shenzhen XINLUDA; it is functionally a **TCA9555 /
-  PCA9555 clone**. Verify against the retained datasheet rather than against the folder name.
-- **Research status:** this README is new (2026-09-04); the datasheet artifact beside it predates
-  this pass and was **not** modified.
-- **Retrieved:** 2026-09-04
-
-## 1. Core facts
-
-| Property | Value |
-|---|---|
-| I/O | **16** bidirectional pins, two 8-bit ports (`P0.x`, `P1.x`) |
-| Interface | I²C, **7-bit address `0x20` – `0x27`** selected by `A0`/`A1`/`A2` |
-| Interrupt | open-drain `INT`, asserted on input change |
-| Registers | `0x00/0x01` input, `0x02/0x03` output, `0x04/0x05` polarity inversion, `0x06/0x07` configuration (1 = input) |
-| Compatible with | TCA9555, PCA9555, and the Linux `pca953x` driver family |
-| Local artifact | [`artifacts/xl9555-datasheet-rev-2.3.pdf`](artifacts/xl9555-datasheet-rev-2.3.pdf) |
-
-**Address ambiguity is the operational hazard.** Eight possible addresses in a contiguous block
-means an I²C scan cannot distinguish an XL9555 from anything else in `0x20–0x27`, and the strap
-resistors are frequently changed between board revisions without a note.
-
-## 2. Used By
-
-### [LilyGO T-Display K230 Kit](../../../devices/lilygo/t-display-k230/README.md) — *added 2026-09-04*
-
-On the **nRF9151 keyboard base board**, I²C4 (`GPIO46` SCL / `GPIO47` SDA), used for LED and
-keyboard-base support alongside the [TCA8418](../../texas-instruments/tca8418/README.md)
-keyboard scanner, [BQ25896](../../texas-instruments/bq25896/README.md) charger and
-[BQ27220](../../texas-instruments/bq27220/README.md) gauge.
-
-LilyGO does not pin the address. Their pin map says: "7-bit I²C address can be **`0x20`-`0x27`**;
-**software probes and caches the detected address**", and the main README lists the address as
-depending on "hardware strap/version". That is an unusually honest vendor statement and it
-means **any firmware for this board must probe rather than hard-code.** Treat a hard-coded
-`0x20` as a bug.
-
-## 3. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | 2026-09-04 | Bus, address range, probe-and-cache behaviour |
-| S2 | `xl9555-datasheet-rev-2.3.pdf` | XLSEMI | primary | datasheet | retained locally, pre-existing artifact | before 2026-09-04 | Register map, addressing |
diff --git a/components/xmc/xm25uh128dhiqt/README.md b/components/xmc/xm25uh128dhiqt/README.md
deleted file mode 100644
index c70d7e2..0000000
--- a/components/xmc/xm25uh128dhiqt/README.md
+++ /dev/null
@@ -1,282 +0,0 @@
-# XMC XM25UH128DHIQT
-
-> **128 Mbit (16 MB) serial NOR flash** — 2.3–3.6 V, Standard / Dual / Quad SPI plus QPI and DTR read modes, 166 MHz fast read, 4 KB uniform sectors, 128-bit unique ID, SFDP, and three 1 KB OTP-lockable security registers.
-> Research snapshot **2026-09-01**. Fitted as **`U13`** on sheet 3 of the [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) (SKU C153) — the ESP32-S3's application flash. **No hardware was available.**
-
-> **Headline finding:** all four data lines are wired, and the ordering code specifies the **Quad Enable bit programmed to 1 at the factory**. The hardware therefore supports QIO in full, matching M5Stack's published `board_build.arduino.memory_type = qio_opi`, even though the shipped factory image's header reports **DIO**. See [§5 — resolving the QIO/DIO conflict](#5--resolving-the-qiodio-conflict).
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[DS]** | XMC `XM25UH128D` datasheet **Rev1.2**, issue date 2025-06-12 — local copy `artifacts/xm25uh128d-datasheet-ver1.2.pdf` | `not-tested` |
-| **[SCH]** | `PaperMono_SCH_V0.6.2_20260522.pdf`, sheet + designator + pin | `executed-success` for the extraction; `not-tested` electrically |
-| **[FW]** | Parsed from the shipped factory firmware image | `executed-success` for the parse |
-| **[DOC]** | `docs.m5stack.com`, retrieved 2026-09-01 | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
----
-
-## 1. Identity and part-number decode
-
-| Property | Value | Evidence |
-|---|---|---|
-| Ordering part | **`XM25UH128DHIQT`** | **[SCH]** sheet 3, `U13` |
-| Base device | **`XM25UH128D`** | **[DS]** |
-| Manufacturer | **Wuhan Xinxin Semiconductor Manufacturing Co., Ltd. (XMC)** | **[DS]** footer, every page |
-| Density | **128 Mbit / 16 MByte** | **[DS]** §1 |
-| Datasheet | **Rev1.2**, issue date **2025-06-12**, 98 pp | **[DS]** footer |
-
-### 1.1 The ordering code, decoded **[DS §3 Ordering Information]**
-
-```
-XM  25  UH  128  D   H   I   Q   T
-│   │   │   │    │   │   │   │   └── Packing:  U = tube, T = tape and reel, R = tray
-│   │   │   │    │   │   │   └────── QE code:  G = green, QE = 0
-│   │   │   │    │   │   │                     Q = green, QE = 1  (default)
-│   │   │   │    │   │   └────────── Temperature: I = −40 … +85 °C (industrial)
-│   │   │   │    │   │                           P = −40 … +105 °C
-│   │   │   │    │   └────────────── Package:  H  = SOP 208 mil 8L
-│   │   │   │    │                             W  = WSON 5 × 6 8L
-│   │   │   │    │                             X  = WSON 6 × 8 8L
-│   │   │   │    │                             U4 = FOSON 3 × 3 8L
-│   │   │   │    └────────────────── Version: D
-│   │   │   └─────────────────────── Density: 128 Mbit
-│   │   └─────────────────────────── Series: UH = 2.3–3.6 V, 4 KB uniform sector, Quad Mode
-│   └─────────────────────────────── Product family: 25 = SPI interface flash
-└─────────────────────────────────── Company prefix: XMC
-```
-
-**So `XM25UH128DHIQT` is: SOP-8 208 mil, industrial temperature, `QE = 1` programmed at the factory, tape-and-reel.**
-
-> The `Q` character is the one that matters here. It is not a marketing letter — it selects the factory state of the **Quad Enable bit in Status Register-2**, and `Q` (QE = 1) is the vendor's stated default. A host does not have to set QE before using quad-mode reads on this part. See §5.
-
-Note also the packing character is **not on the part marking** **[DS §3 note 1]**, so a physical inspection cannot distinguish `…HIQT` from `…HIQU`.
-
-### 1.2 Device identification **[DS §9.1]**
-
-| Instruction | Response |
-|---|---|
-| `9Fh` Read JEDEC ID | `46h 40h 18h` — manufacturer `46h` (XMC Serial Flash), device ID **`4018h`** |
-| `ABh` / `90h` / `92h` / `94h` | device ID **`17h`** |
-
-Also available: `4Bh` Read Unique ID (128-bit), `5Ah` Read SFDP.
-
----
-
-## 2. Key capabilities and limits **[DS §1, §10]**
-
-| Parameter | Value |
-|---|---|
-| Supply | **2.3 – 3.6 V**, single |
-| Interfaces | Standard SPI · **Dual SPI** · **Quad SPI** · **QPI** (2-clock instruction) · **SPI/QPI DTR** |
-| Max clock — fast read (single/dual/quad) | **166 MHz** |
-| Max clock — normal read (`03h`) | 108 MHz |
-| Max clock — DTR read | 108 MHz |
-| Equivalent throughput | 332 MHz-equivalent dual I/O, **664 MHz-equivalent quad I/O** |
-| Standby current | 10 µA typ |
-| **Deep power-down current** | **0.2 µA typ** (`B9h` / `ABh`) |
-| Active read current | 4 mA typ @ 80 MHz quad I/O |
-| Erase granularity | **4 KB sector**, 32 KB block, 64 KB block, chip |
-| Program granularity | 1–256 bytes per page; **65 536 pages**, 4 096 sectors, 256 blocks |
-| Page program time | 0.25 ms typ |
-| Sector erase (4 KB) | 25 ms typ |
-| Block erase (32 KB / 64 KB) | 100 ms / 150 ms typ |
-| Chip erase | **20 s typ** |
-| Endurance | > 100 000 erase/program cycles |
-| Retention | > 20 years |
-| Suspend/resume | Erase and program, `75h` / `7Ah` |
-| Security | 128-bit unique ID · **3 × 1024-byte security registers with OTP lock bits** · software and hardware write protect · power-supply lock-down · top/bottom and complement array protection |
-| Continuous read | 8 / 16 / 32 / 64-byte wrap; true XIP |
-| Configurable dummy cycles | Yes, for fast-read tuning |
-| Packages | SOP 208 mil 8L, WSON 5 × 6, WSON 6 × 8, FOSON 3 × 3 |
-
-**Status-register bits a driver may care about [DS §8.1]:** `BUSY`, `WEL`, `BP2..BP0`, `TB`, `SEC`, `CMP`, `SRP1`/`SRP0`, `SUS`, `LB3..LB1` (security-register OTP locks), **`QE`**, `DRV1`/`DRV0` (output driver strength), **`HOLD/RST`** (IO3 pin function), and the dummy-cycle bits. Most are **volatile *or* non-volatile writable**, which is a useful property — you can change drive strength or QE for one session without spending a non-volatile write.
-
----
-
-## 3. Pinout **[DS §5, §6]**
-
-Standard 8-pin SPI NOR arrangement, with the three multi-function pins:
-
-| Pin | SPI name | Dual | Quad / QPI |
-|---:|---|---|---|
-| 1 | `/CS` | `/CS` | `/CS` |
-| 2 | `SO` | `IO1` | `IO1` |
-| 3 | `/WP` | `/WP` | **`IO2`** |
-| 4 | `GND` | | |
-| 5 | `SI` | `IO0` | `IO0` |
-| 6 | `CLK` | `CLK` | `CLK` |
-| 7 | `/HOLD` **or** `/RESET` | | **`IO3`** |
-| 8 | `VCC` | | |
-
-> ⚠ **Pin 7 has three possible functions and the choice is a register bit.** `/HOLD` or `/RESET` is selected by the `HOLD/RST` bit in Status Register-3 **[DS §8.1]**; in quad/QPI mode the pin is `IO3` regardless. A part configured for `/RESET` cannot do quad I/O. This is the classic way a "QIO does not work" bug is actually a status-register bug.
-
----
-
-## 4. Used By
-
-### `devices/m5stack/papermono`
-
-→ [M5Stack PaperMono (C153)](../../../devices/m5stack/papermono/README.md), designator **`U13`**, schematic sheet 3 (`MCU_Core`). It is the ESP32-S3R8's external application flash. M5Stack's specification lists **16 MB Flash + 8 MB Octal PSRAM**; the PSRAM is inside the [ESP32-S3R8](../../espressif/esp32-s3r8/README.md) package, the flash is this part.
-
-#### 4.1 Exact wiring **[SCH sheet 3]**
-
-| `U13` pin | Name | Net | ESP32-S3 (`U12`) pin | S3 signal |
-|---:|---|---|---:|---|
-| 1 | `CS#` | `NOR_CS` | 32 | `SPICS0` |
-| 2 | `SO` / **`IO1`** | **`NOR_DO`** | 34 | `SPIQ` |
-| 3 | `WP#` / **`IO2`** | **`NOR_WP`** | 31 | `SPIWP` |
-| 4 | `GND` | `GND` | — | — |
-| 5 | `SI` / **`IO0`** | **`NOR_DI`** | 35 | `SPID` |
-| 6 | `SCLK` | `NOR_SCK` ← **`R39` = 22 Ω/1 %** ← | 33 | `SPICLK` |
-| 7 | `HOLD#` / **`IO3`** | **`NOR_HOLD`** | 30 | `SPIHD` |
-| 8 | `VCC` | **`VDD_NOR`** | 29 | **`VDD_SPI`** |
-
-Decoupling: `C56` = 1 µF/25 V on `VDD_NOR`. A 22 Ω series resistor (`R39`) damps the clock — standard practice at these edge rates and worth copying.
-
-#### 4.2 `VCC` comes from the ESP32-S3's internal `VDD_SPI` regulator
-
-`VDD_NOR` is driven from `U12` pin 29, `VDD_SPI` — the ESP32-S3's on-chip flash-supply output, **not** from `3V3_L2` directly. **[SCH]**
-
-That is the normal Espressif arrangement, but it carries a specific hazard: `VDD_SPI` can be configured by eFuse as either **3.3 V (pass-through)** or **1.8 V (regulated)**. This flash is a **2.3–3.6 V** part (§2). A board or a recovery procedure that burns the `VDD_SPI = 1.8 V` eFuse on this design leaves the flash below its minimum supply — and eFuses are one-way. **[INF]** Nothing observed suggests M5Stack has done this; it is recorded because it is the failure mode that a "16 MB flash, why won't it boot" investigation should rule out early.
-
----
-
-## 5. ⚠ Resolving the QIO/DIO conflict
-
-This board's documentation and its shipped binary disagree about the flash mode, and the disagreement has been recorded elsewhere in this research as an open conflict. **The schematic settles the hardware half of it.**
-
-### 5.1 The two claims
-
-| Source | Claim | Evidence |
-|---|---|---|
-| M5Stack PlatformIO config, on both product pages | `board_build.arduino.memory_type = qio_opi` — **QIO** flash + OPI PSRAM | **[DOC]** |
-| Shipped factory image `C153-PaperMono-UserDemo-v1.2.bin`, ESP image headers at `0x0` (bootloader) **and** `0x10000` (app) | `flash_mode: DIO` | **[FW]** |
-| Community image `crosspoint-paper-mono-cjk-1.5.0-RC.bin` | also `flash_mode: DIO` | **[FW]** |
-| `M5PaperMono-UserDemo/sdkconfig.defaults` | **no** `CONFIG_ESPTOOLPY_FLASHMODE_*` entry at all — IDF default applies | source read in full |
-
-### 5.2 What the hardware actually supports
-
-Three independent facts, all `executed-success`:
-
-1. **All four data lines are routed.** `NOR_DI`, `NOR_DO`, `NOR_WP` and `NOR_HOLD` each reach a dedicated ESP32-S3 SPI pin (§4.1). Nothing is tied off, pulled to a rail, or left floating. IO2 and IO3 — the two pins a DIO-only design would strap or omit — are both live signals to `SPIWP` and `SPIHD`.
-2. **The part is a Quad-Mode device by series designation.** `UH` = *"2.3–3.6 V, 4 KB uniform sector, **Quad Mode**"* **[DS §3]**.
-3. **`QE` is programmed to 1 at the factory.** The `Q` in `XM25UH128DHIQT` selects *"Green Package with QE = 1 (default)"* **[DS §3]**. Quad mode is available on first power-up without the host writing Status Register-2.
-
-Pin 7's `HOLD/RST` bit would be the remaining obstacle (§3), and its default is the `/HOLD` function, i.e. IO3 usable — this is the one link in the chain not independently confirmed from the shipped part.
-
-### 5.3 The conclusion
-
-**The hardware is not the limitation.** The PaperMono is wired for QIO, populated with a factory-QE-enabled quad-mode flash, and documented by its vendor as a QIO build target. The `DIO` in the shipped image header reflects **how that particular image was built and flashed**, not a board constraint.
-
-Two ordinary explanations, neither of which requires anyone to have made a mistake **[INF]**:
-
-- `sdkconfig.defaults` pins no flash mode, so the ESP-IDF default (`DIO`) was used for the factory build. The vendor's PlatformIO snippet targets *Arduino/PlatformIO* users and is a different build path.
-- ESP-IDF's `esptool.py` rewrites the flash-mode byte in the image header at flash time, and the ROM bootloader honours it. A `DIO` header is a legitimate, working configuration on QIO-capable hardware — it is simply slower.
-
-**Practical guidance.** If you want quad-mode performance on a PaperMono, build with `CONFIG_ESPTOOLPY_FLASHMODE_QIO=y` (ESP-IDF) or `board_build.arduino.memory_type = qio_opi` (PlatformIO). Nothing on the board prevents it. If it fails, check the flash's `HOLD/RST` bit before suspecting the wiring.
-
-**This resolves the documentation conflict rather than merely restating it**, and the resolution is: *the vendor's build config is right about the hardware; the shipped binary's header is right about that binary.* Both are true simultaneously.
-
----
-
-## 6. Flash layout as shipped **[FW]**
-
-The partition table at `0x8000` of the factory image, and the two projects' `partitions.csv`, agree:
-
-```
-# Name,   Type, SubType, Offset,  Size,     Flags
-nvs,      data, nvs,     0x9000,  0x6000,
-phy_init, data, phy,     0xf000,  0x1000,
-factory,  app,  factory, 0x10000, 0xF00000,
-```
-
-**One 15 MiB factory app, no OTA slots, no filesystem partition**, with roughly 960 KB of the 16 MB unallocated above it. The device as shipped is therefore **not field-updatable over the air**. **[INF]**
-
-For contrast, the community CrossPoint reader image repartitions the same chip into `nvs` / `app0` 6400 K / `cjkfont` 4096 K (custom subtype `0x40`) / `spiffs` 3456 K / `coredump` 64 K — a reminder that the 16 MB is a resource, not a fixed layout.
-
----
-
-## 7. Drivers and software
-
-| Layer | Notes |
-|---|---|
-| **ESP-IDF `esp_flash`** | Handles this part generically through SFDP and the standard JEDEC command set. No chip driver is needed |
-| **`esptool.py`** | Detects the part by `9Fh` JEDEC ID (`46 40 18`, §1.2). If your esptool reports "unknown flash", it is an old version, not a bad chip |
-| **Linux MTD `spi-nor`** | Generic SFDP-based probing works; XMC parts are not individually enumerated in older kernels |
-| **SFDP** | Supported (`5Ah`), so any SFDP-aware stack can configure dummy cycles and address width without a device table |
-
----
-
-## 8. Integration pitfalls
-
-1. **Check `HOLD/RST` before blaming the wiring for a QIO failure** (§3). It is a status-register bit, and it makes IO3 unusable as data when set to `/RESET`.
-2. **`QE` state depends on the ordering code** (§1.1). `…G…` parts ship with QE = 0 and need the host to set it; `…Q…` parts do not. Two part numbers that differ by one character behave differently at first boot.
-3. **The packing character is not on the marking** (§1.1) — you cannot read the full ordering code off the chip.
-4. **`VDD_SPI` voltage is an eFuse decision** and the flash needs ≥ 2.3 V (§4.2).
-5. **Chip erase takes ~20 s** (§2). Flashing tools that appear to hang during erase are usually not hung.
-6. **Security registers have OTP lock bits** (`LB3..LB1`). Writing them is irreversible.
-7. **166 MHz is the *device* limit, not the achievable system clock.** The ESP32-S3 tops out at 80 MHz for QIO in most configurations, and the board's 22 Ω clock resistor and trace lengths matter more than the die's rating. **[INF]**
-
----
-
-## 9. Alternatives
-
-| Part | vs. XM25UH128D | When |
-|---|---|---|
-| **[Winbond W25Q128JV](../../winbond/w25q128jv/README.md)** | The de-facto reference 128 Mbit SPI NOR; same command set, JEDEC ID `EF 40 18` | Widest tool and driver support. Documented in this repository |
-| **[GigaDevice GD25Q64E](../../gigadevice/gd25q64e/README.md)** | 64 Mbit, otherwise comparable | Half the density. Documented in this repository |
-| XMC **XM25QH128B** | XMC's other 128 Mbit line | Different series; check the supply range and sector granularity |
-| XMC **XM25RH128D** / **XM25RU128C** | Same generation, different voltage/feature classes | 1.8 V-class designs |
-| Macronix **MX25L12833F**, ISSI **IS25LP128** | Second sources | Supply-chain diversity |
-
-XM25UH128D's distinguishing features against the Winbond baseline are the **DTR read modes** and the **0.2 µA deep power-down** — neither of which the ESP32-S3's flash driver uses by default. **[INF]**
-
----
-
-## 10. Open questions
-
-- The shipped `HOLD/RST` bit state (§5.2). It is the last link in the QIO chain not independently confirmed.
-- Whether a PaperMono actually boots and runs stably in QIO — untested, no hardware.
-- The fitted package. The ordering code says SOP-8 208 mil; the schematic symbol shows an 8-pin device but does not carry a footprint name in the extracted text.
-- Whether XMC publishes an errata sheet for this part; only the datasheet was found.
-- No hardware measurement of read throughput in DIO versus QIO on this board.
-
----
-
-## Manufacturer
-
-**Wuhan Xinxin Semiconductor Manufacturing Co., Ltd. (XMC)**, `www.xmcwh.com`. No vendor sourcing guide exists in this repository yet. The recipe that worked on 2026-09-01, recorded because the site's product table is JavaScript-rendered and the datasheet link is not in the HTML:
-
-1. `POST https://www.xmcwh.com/product/getProductList` with `page=1&limit=500` returns the **entire 519-part catalogue** as JSON in one response. (Keyword parameters are ignored — filter client-side.)
-2. Each record's `form_data.picture` field holds either a datasheet path (`/uploads/<id>/<PART>_VerX.Y.pdf`) or a `/site/support?...` link.
-3. `https://www.xmcwh.com/uploads/1045/XM25UH128D_Ver1.2.pdf` served the document directly, `application/pdf`, `%PDF` verified.
-
-Plain `curl` with a Chrome 131 User-Agent; no fallback needed, no login. Note the site's own JavaScript contains a commented-out branch that would have suppressed downloads for `description == 'XM25UH'` — the family this part belongs to. It is not active, but it suggests the availability of these documents has changed before and may change again.
-
-## Related pages
-
-- [Espressif ESP32-S3R8](../../espressif/esp32-s3r8/README.md) — the host, and the source of `VDD_SPI`
-- [Winbond W25Q128JV](../../winbond/w25q128jv/README.md) — the equivalent part on other boards in this repository
-- [GigaDevice GD25Q64E](../../gigadevice/gd25q64e/README.md) — 64 Mbit sibling class
-
-## Authoritative sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | XM25UH128D datasheet | Wuhan Xinxin Semiconductor Manufacturing Co., Ltd. (XMC) | primary | datasheet | <https://www.xmcwh.com/uploads/1045/XM25UH128D_Ver1.2.pdf> | 2026-09-01 | **Rev1.2**, 2025-06-12, 98 pp, 3 730 929 B | Ordering-code decode incl. **QE = 1 default**, JEDEC ID, all limits in §2, pin functions, status-register bit list, timing | `artifacts/xm25uh128d-datasheet-ver1.2.pdf` |
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | V0.6.2, 6 sheets | The §4.1 pin/net table — **all four data lines routed**, `R39` = 22 Ω, `VDD_NOR` ← `VDD_SPI` | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| S2 | PaperMono product page — PlatformIO configuration | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | `board_build.arduino.memory_type = qio_opi` | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono.html` |
-| S3 | `C153-PaperMono-UserDemo-v1.2.bin` — ESP image headers and partition table | M5Stack | primary | firmware | M5Burner API, firmware id `2089640807996628993` | 2026-09-01 | v1.2, built 2026-08-06, `app_version c78f6c5-dirty`, IDF v5.5.1; 2 868 208 B, SHA-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | `flash_mode: DIO` in both headers; the 15 MiB single-`factory` partition table | `scratch/m5stack-papermono/docs/firmware/` |
-| S4 | `M5PaperMono-UserDemo/sdkconfig.defaults`, `partitions.csv` | M5Stack | primary | repository | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | `main` @ `c1099107271d31a0678d661a896e2b04dbb331ea`, MIT | **No** `CONFIG_ESPTOOLPY_FLASHMODE_*` is set — the DIO header is an IDF default, not a decision | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-
-**Local artifacts**
-
-| File | Bytes | SHA-256 | Pages |
-|---|---:|---|---:|
-| `artifacts/xm25uh128d-datasheet-ver1.2.pdf` | 3 730 929 | `a6f683599543c81d36dff7f3a20dc6f5f637e9cac6554fa87873abaf2126c014` | 98 |
-
-**Method note.** D1 validated as `%PDF`, 98 pages, text layer intact. The §5 resolution combines three independent `executed-success` observations — the schematic netlist, the datasheet's ordering table, and the firmware image header — rather than preferring one source over another.
diff --git a/components/xmc/xm25uh128dhiqt/artifacts/xm25uh128d-datasheet-ver1.2.pdf b/components/xmc/xm25uh128dhiqt/artifacts/xm25uh128d-datasheet-ver1.2.pdf
deleted file mode 100644
index 3c08be2..0000000
Binary files a/components/xmc/xm25uh128dhiqt/artifacts/xm25uh128d-datasheet-ver1.2.pdf and /dev/null differ
diff --git a/components/zhongkewei/at6668/README.md b/components/zhongkewei/at6668/README.md
deleted file mode 100644
index ed87ba6..0000000
--- a/components/zhongkewei/at6668/README.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# ZhongKeWei AT6668
-
-- **Category:** **multi-mode GNSS baseband/RF chipset** — the silicon inside the
-  [ATGM336H-6N](../atgm336h-6n/README.md) module
-- **Research status:** **no chip datasheet located.** What *is* held is the **CASIC
-  Multi-mode Satellite Navigation Receiver Protocol Specification**, which is the document
-  that actually matters for firmware, because everything beyond "read NMEA" goes through it.
-- **Retrieved:** 2026-09-04
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **ZhongKeWei / 中科微电子** (Zhongke Microelectronics) | `inferred` from the module lineage |
-| Part | **`AT6668`** | M5Stack writes the module/chip pairing as **`ATGM336H-6N@AT6668`** on three separate product pages |
-| Role | Multi-constellation GNSS receiver SoC | vendor |
-| Constellations | GPS, QZSS, BDS (B1I + B1C), GALILEO E1, GLONASS R1, SBAS | vendor |
-| Channels | 50 | vendor |
-| Host protocol | **NMEA 0183 4.1** output; **CASIC binary** for configuration and status | vendor + the protocol specification |
-
-The chip is not sold as a bare part in the channels this pass searched; it is encountered
-only inside modules. That is why the module record carries the electrical detail and this
-record carries the protocol.
-
-## 2. Why the CASIC protocol matters
-
-Reading a position is easy — the receiver emits standard NMEA sentences and any parser will
-do. **Everything else requires CASIC binary messages:**
-
-| Task | Mechanism |
-|---|---|
-| Select which constellations are used | CASIC config message |
-| Cold / warm / hot / factory start | CASIC command |
-| Change update rate | CASIC config |
-| Change UART baud rate | CASIC config |
-| Query firmware version | CASIC query |
-| Power/standby modes | CASIC command |
-
-M5Stack's `MultipleSatellite` class (in their `TinyGPSPlus` fork) exposes exactly this
-surface — `setSystemBootMode(BOOT_FACTORY_START)`, `setSatelliteMode(SATELLITE_MODE_GLONASS)`,
-`getGNSSVersion()` — and those calls are CASIC frames underneath, not NMEA.
-
-**Practical consequence for a port:** if you drop a generic NMEA library onto an
-ATGM336H/AT6668 and then find you cannot change the constellation set or the update rate,
-this is why. The protocol specification is the reference; it is archived below.
-
-## 3. Used By
-
-### [ATGM336H-6N module](../atgm336h-6n/README.md)
-
-The only route by which this chipset appears in this repository. Through that module it
-reaches:
-
-- [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) — designator `M2`, UART only
-- [M5Stack Cap LoRa868 (U201)](../../../devices/m5stack/cap-lora868/README.md) — same
-- [M5Stack Cardputer Mesh Kit (K152)](../../../devices/m5stack/cardputer-mesh-kit/README.md) — via the bundled Cap
-
-On all three the chipset speaks **UART at 115200 8N1** and nothing else is exposed.
-
-## 4. Caveats
-
-| # | Issue |
-|---|---|
-| 1 | **No AT6668 chip datasheet located.** Constellation, channel and sensitivity figures here are *module-level* claims from M5Stack |
-| 2 | The CASIC specification is a **multi-vendor** document covering a family of receivers — not every message it defines is necessarily implemented by the AT6668 |
-| 3 | The archived specification's **language and revision were not checked** (see the placeholder). CASIC documentation commonly circulates in Chinese with partial English translations |
-| 4 | Whether the AT6668 differs materially from the AT6558 / AT6558R used in older ATGM336H variants was **not investigated** |
-
-## 5. Local artifacts
-
-| File | Status |
-|---|---|
-| [`artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.ARCHIVED.md`](artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.ARCHIVED.md) | **Archived** 2026-09-04 — 2 899 191 B. The placeholder carries the hash and two reacquisition URLs |
-
-Cited from the device records that caused the fetch:
-[Cap LoRa-1262 `sources.md` S-20](../../../devices/m5stack/cap-lora-1262/sources.md) and
-[Cardputer Mesh Kit §7](../../../devices/m5stack/cardputer-mesh-kit/README.md).
-
-## 6. Sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|
-| Z-1 | CASIC Multi-mode Satellite Navigation Receiver Protocol Specification | CASIC, mirrored by M5Stack | authorized mirror | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1173/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf` | 2026-09-04 | The binary configuration protocol — **archived** |
-| Z-2 | Cap LoRa-1262 documentation | M5Stack | primary | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` | 2026-09-04 | `ATGM336H-6N@AT6668` pairing; constellation and band list |
-| Z-3 | `m5stack/TinyGPSPlus` (`MultipleSatellite`) | M5Stack | primary | `https://github.com/m5stack/TinyGPSPlus` @ `254a10041ac38d17d98dab24c0ae4d2a8d19a677` | 2026-09-04 | The CASIC-backed API surface named in §2 |
diff --git a/components/zhongkewei/at6668/artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.ARCHIVED.md b/components/zhongkewei/at6668/artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.ARCHIVED.md
deleted file mode 100644
index eccb116..0000000
--- a/components/zhongkewei/at6668/artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.ARCHIVED.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# ARCHIVED: `CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf`
-
-> This file was **moved out of the repository**, not deleted. Archived **2026-09-04**.
-
-**What it was:** the **CASIC binary protocol specification** for multi-mode satellite
-navigation receivers — the document that defines the configuration and query messages used
-by ZhongKeWei GNSS chipsets including the **AT6668** inside the
-[ATGM336H-6N](../../atgm336h-6n/README.md).
-
-**What it is for:** everything beyond reading NMEA. Constellation selection, boot mode
-(cold/warm/hot/factory), update rate, baud rate and firmware-version query are all CASIC
-messages, not NMEA sentences. M5Stack's `MultipleSatellite` API
-(`setSatelliteMode()`, `setSystemBootMode()`, `getGNSSVersion()`) is a thin wrapper over
-this protocol.
-
-**Why it was moved:** 2.9 MB, and it is a **protocol manual rather than a part datasheet** —
-the least central of the four PDFs this research pass retained. It is re-fetchable from a
-stable vendor CDN.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repository path | `components/zhongkewei/at6668/artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf` |
-| Archived to | `archive/components/zhongkewei/at6668/artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf` |
-| Type | file, PDF (`%PDF-1.7`, magic verified) |
-| Size | **2 899 191 B (2.76 MiB)** |
-| SHA-256 | `61e2567dcf04b0d8e4d5ec6c9c841f8ac0caa846f5b54645a64b7704d800fe04` |
-| Retrieved | **2026-09-04**, HTTP 200 |
-| Document version / date | **unknown** — no version string in the filename, and the file's contents were **not read** by the pass that fetched it |
-| Language | **unknown** (CASIC material commonly circulates in Chinese; an English rendering of the title is used by M5Stack) |
-| Publisher | CASIC (China Aerospace Science and Industry Corporation), mirrored by M5Stack |
-| Licence | **unknown.** No licence statement accompanies M5Stack's document mirrors |
-| Redistribution status | **unknown** |
-| Disposition | **archived** (local-cache equivalent); not tracked in this repository |
-
-## How to get it back
-
-Verified **2026-09-04**.
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-
-# Source 1 — M5Stack documentation CDN (the copy that was archived)
-curl -sSL -A "$UA" -o CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf \
-  https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1173/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf
-
-# Source 2 — the same file is linked from two M5Stack product pages, in case the
-# direct CDN path changes. Re-scrape the "Datasheets" section of either:
-#   https://docs.m5stack.com/en/cap/Cap_LoRa-1262
-#   https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit
-
-# Verify
-sha256sum CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf
-#   61e2567dcf04b0d8e4d5ec6c9c841f8ac0caa846f5b54645a64b7704d800fe04
-stat -c%s CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf
-#   2899191
-head -c 8 CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf
-#   %PDF-1.7
-```
-
-Reacquisition status: **automatic** (both routes are unauthenticated HTTP GET).
-
-**Not submitted to the Wayback Machine.** It is a vendor-CDN mirror of a widely-circulated
-Chinese-industry protocol document, not a scarce one-off — the criteria in `AGENTS.md` for
-`web.archive.org/save/` are not met. If a future pass finds the CDN path dead and no
-alternative, that judgement should be revisited.
-
-## Restore from the local archive
-
-```bash
-mv archive/components/zhongkewei/at6668/artifacts/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf \
-   components/zhongkewei/at6668/artifacts/
-```
-
-## Cited by
-
-- [`components/zhongkewei/at6668/README.md`](../README.md) §5
-- [`components/zhongkewei/atgm336h-6n/README.md`](../../atgm336h-6n/README.md) §6
-- [`devices/m5stack/cap-lora-1262/sources.md`](../../../../devices/m5stack/cap-lora-1262/sources.md) — S-20
-- [`devices/m5stack/cap-lora-1262/features/gnss.md`](../../../../devices/m5stack/cap-lora-1262/features/gnss.md) §3
-- [`devices/m5stack/cardputer-mesh-kit/README.md`](../../../../devices/m5stack/cardputer-mesh-kit/README.md) §7
diff --git a/components/zhongkewei/atgm336h-6n/README.md b/components/zhongkewei/atgm336h-6n/README.md
deleted file mode 100644
index 5ab35cc..0000000
--- a/components/zhongkewei/atgm336h-6n/README.md
+++ /dev/null
@@ -1,150 +0,0 @@
-# ZhongKeWei ATGM336H-6N
-
-- **Category:** **GNSS receiver module** — a carrier for an **AT6668** multi-mode
-  satellite-navigation chipset, presented as an 18-pad UART/I²C module
-- **Scope:** module level. The chipset's protocol, constellations and configuration commands
-  belong to [`components/zhongkewei/at6668`](../at6668/README.md)
-- **Retrieved:** 2026-09-04
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Manufacturer | **ZhongKeWei / 中科微电子** (Zhongke Microelectronics), Chengdu | datasheet title, `inferred` for the English rendering |
-| Part | **`ATGM336H-6N`** — the `-6N` suffix denotes the variant/firmware grade | M5Stack specification tables |
-| Chipset inside | **`AT6668`** — M5Stack writes the pairing as **`ATGM336H-6N@AT6668`** | M5Stack specification tables, three product pages |
-| Pads | **18** | schematic symbol |
-| Interfaces | **UART** (primary), **I²C**, `1PPS`, `ON/OFF`, `NRST`, `VBAT` backup | schematic symbol |
-| Protocol | **NMEA 0183 4.1** on the wire; **CASIC binary** for configuration | M5Stack |
-
-### Pinout as drawn on M5Stack's symbol
-
-| Pin | Name | Pin | Name |
-|---:|---|---:|---|
-| 1 | `GND` | 10 | `GND` |
-| 2 | `TXD1` | 11 | `ANT` |
-| 3 | `RXD1` | 12 | `GND` |
-| 4 | `1PPS` | 13 | `NC` |
-| 5 | `ON/OFF` | 14 | `VCC_RF` |
-| 6 | `VBAT` | 15 | `NC` |
-| 7 | `NC` | 16 | `SDA` |
-| 8 | `VCC` | 17 | `SCL` |
-| 9 | `NRST` | 18 | `NC` |
-
-Note the **separate `VCC` and `VCC_RF` supplies** (pins 8 and 14) — boards commonly feed
-them through separate ferrites, and `VCC_RF` is what biases an external active antenna or
-LNA.
-
-## 2. Capability, as M5Stack publishes it
-
-| Item | Value |
-|---|---|
-| Constellations | **GPS · QZSS · BDS (BD2 + BD3) · GALILEO · GLONASS** |
-| Bands | BDS **B1I + B1C** · GPS/QZSS/SBAS **L1** · GALILEO **E1** · GLONASS **R1** |
-| Channels | 50 |
-| Accuracy | **< 1.5 m CEP50** |
-| Update rate | up to **10 Hz** |
-| Sensitivity | tracking **−162 dBm** · acquisition −160 dBm · cold start −148 dBm |
-| TTFF | cold **23 s** · hot **1 s** |
-| Default UART on M5Stack boards | **115200 bps 8N1** |
-
-⚠ **"Multi-frequency" here means multiple *constellations'* L1-neighbourhood signals
-(1.56–1.61 GHz), not L1+L5 dual-frequency.** One 18 mm patch and one LNA cover all of them.
-Do not read RTK-grade capability into the specification table.
-
-⚠ The **−162 dBm tracking** figure quoted by M5Stack is for a board carrying an external
-**MAX2659 LNA**, not for the bare module. Attributing it to the module alone would be wrong.
-
-## 3. Software
-
-| Library | Notes |
-|---|---|
-| **`m5stack/TinyGPSPlus`** — class **`MultipleSatellite`** | M5Stack's fork, head `254a10041ac38d17d98dab24c0ae4d2a8d19a677` (2025-01-02). ⚠ The vendor documentation says explicitly: *"needs to be downloaded from the GitHub version adapted for M5Stack devices… **Do not download it from the Arduino Library Manager**"*. **No LICENSE file is present in the fork**; upstream TinyGPSPlus is LGPL-2.1 — flagged, unresolved |
-| Meshtastic | built-in GPS subsystem; `GPS_BAUDRATE 115200` |
-| Any NMEA parser | sufficient for position/time; **not** sufficient for configuration |
-
-`MultipleSatellite` adds M5Stack-specific calls — `setSystemBootMode(BOOT_FACTORY_START)`,
-`setSatelliteMode(...)`, `getGNSSVersion()` — which are **CASIC binary commands**, not NMEA.
-See the [AT6668 record](../at6668/README.md).
-
-## 4. Used By
-
-### [M5Stack Cap LoRa-1262 (U214)](../../../devices/m5stack/cap-lora-1262/README.md) — designator `M2`, symbol comment `GP-02`
-
-| Function | Module pin | Board / host |
-|---|---:|---|
-| UART TX (module → host RX) | 2 | Cap-Bus 1 → host **G15** |
-| UART RX (module ← host TX) | 3 | Cap-Bus 2 → host **G13** |
-| `VCC` | 8 | `+3.3V` via `FB3` 120 Ω/MB |
-| `VCC_RF` | 14 | `+3.3V` via `FB2` 120 Ω/MB |
-| `ANT` | 11 | ← `U1` **MAX2659** LNA `RFOUT` via `C5` 470 pF ← `J1` `ANT1818-04` patch |
-| `VBAT` | 6 | `BT1` backup cell |
-| `1PPS` (4), `ON/OFF` (5), `NRST` (9), `SDA` (16), `SCL` (17) | — | **not routed to the Cap-Bus** |
-
-**So on this board it is a UART-only device with no host reset, no hardware standby and no
-pulse-per-second.** Everything configurable must go over the serial link. Full detail:
-[`devices/m5stack/cap-lora-1262/features/gnss.md`](../../../devices/m5stack/cap-lora-1262/features/gnss.md).
-
-⚠ **The symbol comment reads `GP-02`, not `ATGM336H-6N`.** The specification table says
-`ATGM336H-6N@AT6668`. Whether `GP-02` is an M5Stack internal library name, a second-source
-designation, or something else is **unresolved**.
-
-### [M5Stack Cap LoRa868 (U201)](../../../devices/m5stack/cap-lora868/README.md) — same part
-
-Specification table gives the identical `ATGM336H-6N@AT6668` pairing and identical GNSS
-figures. Pin map shows the same two Cap-Bus lines (`GPS_TX` → G15, `GPS_RX` → G13). The
-U201 page additionally publishes **state-resolved current** — GPS on / LoRa standby
-**29.24 mA** vs **GPS sleep / LoRa standby 3.16 mA** — i.e. **the GNSS dominates idle draw**
-on that board.
-
-### [M5Stack Cardputer Mesh Kit (K152)](../../../devices/m5stack/cardputer-mesh-kit/README.md)
-
-Via the bundled Cap LoRa-1262.
-
-### Elsewhere in M5Stack's catalogue
-
-The datasheet mirror this repository holds is served from M5Stack's **`Unit-GPS v1.1`**
-documentation path, so the same module is fitted to at least one Unit-series product. **Not
-researched** by this pass.
-
-## 5. Caveats
-
-| # | Issue |
-|---|---|
-| 1 | **115200 bps is not the ATGM336H's usual factory default** (9600 is common elsewhere). Whether M5Stack's boards store the setting in the module or apply it from firmware is **unknown**. Autobaud should include 9600 |
-| 2 | Sensitivity/accuracy figures quoted by M5Stack are **board-level with an external LNA** |
-| 3 | `GP-02` unexplained (§4) |
-| 4 | On both Caps the module's I²C, `1PPS`, `NRST` and `ON/OFF` are **not available to the host** |
-| 5 | No independent measurement of TTFF, accuracy or sensitivity |
-
-## 6. Related components
-
-- [`components/zhongkewei/at6668`](../at6668/README.md) — the chipset inside, and the CASIC protocol
-- [`components/analog-devices/max2659`](../../analog-devices/max2659/README.md) — the LNA in front of it on both Caps
-- [`components/generic/gnss-ceramic-patch-antenna`](../../generic/gnss-ceramic-patch-antenna/README.md)
-
-## 7. Local artifacts
-
-| File | Bytes | SHA-256 | Provenance |
-|---|---:|---|---|
-| [`artifacts/atgm336h-6n-datasheet-m5stack-mirror.pdf`](artifacts/atgm336h-6n-datasheet-m5stack-mirror.pdf) | 752 259 | `7b1c10193709d7600e0234445a1c15603bf3443e14780ecde4818091ec2eda32` | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/unit/Unit-GPS%20v1.1/ATGM336H-6N.pdf`, retrieved 2026-09-04, HTTP 200, `%PDF-1.7` |
-
-⚠ **Vendor mirror, served from a *different product's* documentation path** (`Unit-GPS
-v1.1`), linked from the Cap LoRa-1262 and Cardputer Mesh Kit pages. Revision unverified
-against ZhongKeWei's own publication; the file carries no version in its name.
-**The PDF was downloaded and type-verified but its contents were not read** by this pass —
-every ATGM336H figure in this record comes from M5Stack's specification tables, not from the
-datasheet. That is a gap a future pass should close.
-
-Licence/redistribution: **unknown**. Disposition: **repository, unstaged** pending review.
-
-## 8. Sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|
-| A-1 | ATGM336H-6N datasheet | ZhongKeWei, mirrored by M5Stack | authorized mirror | see §7 | 2026-09-04 | The module (**held, not yet read**) |
-| A-2 | Cap LoRa-1262 documentation | M5Stack | primary | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` | 2026-09-04 | `ATGM336H-6N@AT6668`, all §2 figures, the pin map |
-| A-3 | Cap LoRa868 documentation | M5Stack | primary | `https://docs.m5stack.com/en/cap/Cap_LoRa868` | 2026-09-04 | Same module on the predecessor; **state-resolved current** |
-| A-4 | Cardputer Mesh Kit documentation | M5Stack | primary | `https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit` | 2026-09-04 | Third citation of the same pairing |
-| A-5 | Cap LoRa-1262 schematic V1.1 | M5Stack | primary | [`devices/m5stack/cap-lora-1262/artifacts/schematic/`](../../../devices/m5stack/cap-lora-1262/artifacts/schematic/) | 2026-09-04 | The 18-pad pinout and what is/is not routed |
-| A-6 | `m5stack/TinyGPSPlus` | M5Stack | primary | `https://github.com/m5stack/TinyGPSPlus` | 2026-09-04 | `MultipleSatellite`; head `254a1004…`; **no LICENSE file** |
diff --git a/components/zhongkewei/atgm336h-6n/artifacts/atgm336h-6n-datasheet-m5stack-mirror.pdf b/components/zhongkewei/atgm336h-6n/artifacts/atgm336h-6n-datasheet-m5stack-mirror.pdf
deleted file mode 100644
index 03d97c3..0000000
Binary files a/components/zhongkewei/atgm336h-6n/artifacts/atgm336h-6n-datasheet-m5stack-mirror.pdf and /dev/null differ
diff --git a/devices/README.md b/devices/README.md
index 1ac6339..511ab8a 100644
--- a/devices/README.md
+++ b/devices/README.md
@@ -13,16 +13,6 @@ Three findings from that pass are worth knowing before buying one: the **user LE
 ## Waveshare
 
 - [Waveshare ESP32-S3-Knob-Touch-LCD-1.8](waveshare/esp32-s3-knob-touch-lcd-1.8/README.md), product ID 31623, retrieved 2026-08-21 — vendor guide: [Waveshare](../vendors/waveshare/README.md)
-- [Waveshare ESP32-S3-ePaper-3.97](waveshare/esp32-s3-epaper-3.97/README.md), SKUs **33552 / 33810 / 33811**, **USD 34.99–47.99**, retrieved 2026-09-01 — the knowledge base's first Waveshare **e-paper** board (all others are LCD). Same SoC, memory, 3.97" 4-grey panel **and SSD1677 controller** as the [M5Stack PaperMono](m5stack/papermono/README.md); active area matches to 0.01 mm and DPI exactly. **It has no expansion header** — which refutes the "prefer a Waveshare board *with expansion*" advice it was written to support. Schematic, panel manual and vendor source retained; [pinouts](waveshare/esp32-s3-epaper-3.97/pinouts-and-buses.md) · [conflicts](waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md)
-
-**Waveshare's other ESP32 e-paper boards** — surveyed 2026-09-01, stub records, not researched in depth. Recorded so the population is known:
-
-| Board | Price, 2026-09-01 | Why it is here |
-|---|---|---|
-| [e-Paper ESP32 Driver Board](waveshare/e-paper-esp32-driver-board/README.md) | USD 14.99 | Original ESP32; drives **23 documented raw panels** over a 24-pin FPC. The oldest and most widely deployed of the family |
-| [ESP32-S3-ePaper-1.54](waveshare/esp32-s3-epaper-1.54/README.md) | USD 15.99–22.99 | 1.54" 200 × 200. **Has the 2 × 6 2.54 mm expansion header the 3.97" lacks** — 40 000 pixels instead of 384 000 |
-| [ESP32-C6-ePaper-1.54](waveshare/esp32-c6-epaper-1.54/README.md) | USD 16.99–17.99 | Same, on **ESP32-C6 — Wi-Fi 6, Zigbee/Thread**, plus a TCA9554 I/O expander |
-| [ESP32-S3-PhotoPainter](waveshare/esp32-s3-photopainter/README.md) | USD 82.99–83.99 | 7.3" Spectra 6 in a wood frame. **An appliance, not a development board** — and the `PhotoPainter` name covers four products, only one of which is ESP32 |
 
 A sibling of this board, the **Guition JC3636K518**, is documented — as far as the evidence allows — in [clones-and-variants.md §5](../guides/markets/clones-and-variants.md#5-worked-example--waveshare-knob-board-and-guition-jc3636k518). It is not a separate device record here because we have not handled one.
 
@@ -93,218 +83,6 @@ Its Raspberry-Pi predecessor, **ZeroWriter 1**, silently patched two files in Wa
 
 **Zerowriter Fold** is documented **from vendor marketing material only** — the Kickstarter campaign page bot-blocks every user agent tried and was never read. No design files, teardown, review or unit exists. Treat every figure as a vendor claim about an unshipped product; the record's [source manifest](zerowriter/zerowriter-fold/sources.md) states exactly what that evidence can and cannot support. The consequential claim is that the Fold uses **in-house hardware** rather than an Inkplate — if accurate, none of the Inkplate research transfers to it.
 
-## M5Stack
-
-Retrieved **2026-09-01**. Two SKUs of **one board**, launched together on 2026-08-21 and both out of stock nine minutes later.
-
-| Board | SKU | Price | Distinguishing feature | Sources |
-|---|---|---|---|---|
-| [PaperMono](m5stack/papermono/README.md) | **C153** | USD 65.00 | Grey case, **NFC (ST25R3916) + LoRa (Stamp LoRa-1262)** | [sources](m5stack/papermono/sources.md) · [research log](m5stack/papermono/research-log.md) · [commands](m5stack/papermono/commands.md) |
-| [PaperMono-Lite](m5stack/papermono-lite/README.md) | **C153-Lite** / `C153-LITE` | USD 55.00 | White case, **no NFC, no LoRa**; 72.4 g vs 74.7 g. Everything else identical, battery included | shares the PaperMono's manifests |
-
-A 3.97″ 480 × 800 frontlit touch e-paper handheld on an ESP32-S3R8. Best understood as **a battery-first low-power platform that happens to have a display**, not an e-paper board that happens to have a battery: it has five hardware power states and can wake on RTC alarm, motion, touch or keys **with the application processor unpowered**. The full record: [`papermono/`](m5stack/papermono/README.md), with [pinouts and buses](m5stack/papermono/pinouts-and-buses.md), [power architecture](m5stack/papermono/power-architecture.md) and [gaps and conflicts](m5stack/papermono/gaps-and-conflicts.md).
-
-Four things to know before buying or building for one:
-
-- **There is no expansion connector at all** — no Grove, no M-Bus. Every GPIO is committed; the only way in is the shared I²C bus. This is unusual for an M5Stack core and is the single biggest constraint.
-- **Two auxiliary microcontrollers sit between the application processor and most of the board.** Panel power and reset, touch power and reset, microSD power and detect, microphone power, NFC enable, LoRa reset, two of three LED colours and the charger's bus gate are all behind the **M5IOE1** expander; reset, boot mode, rail enables and every wake source are behind the **M5PM1** power manager. Neither is optional, and both are the *same* Puya PY32L020F15U6 die running different M5Stack firmware.
-- **`PYG3` denotes two different pins**, one on each of those chips — the frontlight PWM and the e-paper rail enable. Getting it wrong silently kills the display. [The whole hazard, and how it was resolved from the schematic](m5stack/papermono/pin-naming-and-the-pyg-ambiguity.md).
-- **Do not read PaperMono as a successor to the M5PaperS3.** Against the PaperS3 it has ~35 % fewer pixels, 4 grey levels instead of 16, a smaller battery and no expansion port, while adding a frontlight, NFC, LoRa and the power architecture. A repositioning, not an upgrade.
-
-⚠ **Nothing in either record was verified on physical hardware.** Every behavioural claim is `inferred`, `reported-working` or read from vendor source. The board sold out within minutes of launch and had not restocked eleven days later, so no unit could be obtained — and for the same reason there were, at the snapshot date, **zero written reviews and one hands-on video** anywhere. The real independent evidence is four third-party GitHub projects, two with credible hardware validation.
-
-M5Stack publishes a complete schematic and datasheets for both of its custom chips, which is better hardware disclosure than most comparable vendors — but **no C153 directory exists in `m5stack/M5_Hardware`**, so there is no machine-readable netlist and the pin map was recovered by parsing invisible Altium marker text out of the published PDF. Method and limitations: [`commands.md`](m5stack/papermono/commands.md#altium-pdf-tooling).
-
-### DinMeter — *added 2026-09-04*
-
-A 1/32-DIN panel instrument built on a Stamp module: orange rotary encoder, 1.14" display, buzzer and a **6–36 V DC input**, in a DIN 43700 cutout. M5Stack publishes a **byte-identical** schematic and STL for both revisions, so the v1.1 record is scoped to the module substitution that is the entire content of the revision.
-
-| Device | SKU | Record | Notes |
-|---|---|---|---|
-| **DinMeter** | `K134` | [`m5stack/dinmeter`](m5stack/dinmeter/README.md) | 1/32-DIN panel instrument: orange rotary encoder, 1.14" ST7789V2 135×240, BM8563 RTC, buzzer, **6–36 V DC input**, Li-ion charger + latch, PORT.A/B. Stamp-S3 core module. **`[EOL]` at the vendor, 2026-09-04** |
-| **DinMeter v1.1** | `K134-V11` | [`m5stack/dinmeter-v1.1`](m5stack/dinmeter-v1.1/README.md) | Same carrier with a **Stamp-S3A** module and an ST7789P3 display. Scoped revision record — M5Stack publishes a **byte-identical** schematic and STL for both. Includes [`stamp-s3-to-s3a-delta.md`](m5stack/dinmeter-v1.1/stamp-s3-to-s3a-delta.md), the full schematic-derived module delta |
-
-### Cardputer family — *added 2026-09-04*
-
-Card-sized computers with a 56-key QWERTY keyboard over a 1.14″ 240×135 display. Five records; the ADV is the full-depth one. Note that **the v1.0 and v1.1 share one published schematic file byte-for-byte** (SHA-256 `6016c1fe…`), so the revision is a module substitution — Stamp-S3 → Stamp-S3A — with an undocumented or unchanged mainboard, and the document alone cannot say which.
-
-| Device | Manufacturer | SKU | SoC | Notes |
-|---|---|---|---|---|
-| [Cardputer ADV](m5stack/cardputer-adv/README.md) | M5Stack | `K132-Adv` | ESP32-S3FN8 | Card-sized computer, 56-key TCA8418 keyboard, ES8311 audio, BMI270, 14-pin CAP expansion header. **Full-depth record.** |
-| [Cardputer v1.1](m5stack/cardputer-v1.1/README.md) | M5Stack | `K132-V11` | ESP32-S3FN8 | Stamp-S3A refresh of the original; 74HC138 keyboard. **`[EOL]` at 2026-09-04.** |
-| [Cardputer v1.0](m5stack/cardputer-v1.0/README.md) | M5Stack | `K132` | ESP32-S3FN8 | The original; StampS3 module. Shares a published schematic file with v1.1. |
-| [Cardputer Mesh Kit](m5stack/cardputer-mesh-kit/README.md) | M5Stack | `K152` | ESP32-S3FN8 | Cardputer ADV + Cap LoRa-1262 bundle; officially licensed Meshtastic device. |
-| [CardputerZero](m5stack/cardputer-zero/README.md) | M5Stack | `C154` / `C155` | **Raspberry Pi CM0** | Linux handheld in the Cardputer form factor. Vendor marks it *work in progress*. |
-
-⚠ **The Cardputer ADV and the CardputerZero are not comparable devices** despite sharing a name, a form factor, a keypad scanner and an expansion connector: one is a microcontroller, the other a Linux computer, and their EXT headers are **not pin-compatible** — the Zero's left column is USB/GPIO/SPI0 and its UART pair is reversed relative to the ADV's.
-
-### Cardputer expansions — LoRa, sub-GHz and NFC — *added 2026-09-04*
-
-Nine records covering M5Stack's radio expansions for the Cardputer line, from the Grove-attached E220 units of 2023 to the **Cap CC1101 & NFC** released 2026-08-28. Entry point: [`m5stack/cap-lora-1262/`](m5stack/cap-lora-1262/README.md); the two portability-focused guides are [`features/lora.md`](m5stack/cap-lora-1262/features/lora.md) and [`features/nfc.md`](m5stack/cap-cc1101/features/nfc.md), both written for someone adding these capabilities to *other* firmware.
-
-| Device | Notes | Depth |
-|---|---|---|
-| [M5Stack Cap LoRa-1262 (U214)](m5stack/cap-lora-1262/README.md) | Cardputer-Adv expansion — SX1262 LoRa + ATGM336H-6N GNSS, 868–923 MHz, Meshtastic-supported upstream | full |
-| [M5Stack Cap CC1101 & NFC (U219)](m5stack/cap-cc1101/README.md) | Cardputer-Adv expansion — CC1101 sub-GHz (315/433/868/915 MHz, dual SP3T switched) + ST25R3916 NFC over SPI | full |
-| [M5Stack Cap LoRa868 (U201)](m5stack/cap-lora868/README.md) | The **first** Cardputer-Adv LoRa expansion, 2025-09-05, now EOL — predecessor of the Cap LoRa-1262 | medium |
-| [M5Stack Cardputer Mesh Kit (K152)](m5stack/cardputer-mesh-kit/README.md) | Bundle: Cardputer-Adv + Cap LoRa-1262, pre-flashed Meshtastic, the only Meshtastic-registration-eligible configuration | medium |
-| [M5Stack LoRa Unit (E220)](m5stack/unit-lora-e220/README.md) | Grove/UART LLCC68 modem — attaches to *any* Cardputer, but **not** a Meshtastic path | light |
-| [M5Stack LoRaWAN Unit (STM32WLE5)](m5stack/unit-lorawan-stm32wle5/README.md) | Grove/UART LoRaWAN modem, **region per SKU**, RAK3172 module | light |
-| [M5Stack Unit C6L (U202)](m5stack/unit-c6l/README.md) | Self-contained ESP32-C6 + SX1262 Meshtastic node on a Grove cable — the route for an **original** Cardputer | light |
-| [M5Stack Stamp C6LoRa (S012)](m5stack/stamp-c6lora/README.md) | Solder-down ESP32-C6 + SX1262 SMD module — **not** a Cardputer expansion | light |
-
-⚠ **Initialising the Cap LoRa-1262 requires one non-obvious step**: M5Stack states that the RF antenna switch must be enabled by setting **`P0` of the Cap's PI4IOE I/O expander HIGH**, over the host's *internal* I²C bus. Omit it and the radio transmits into a disconnected antenna.
-
-## Xteink (阅星瞳 / 星瞳 "Star Pupil")
-
-Shenzhen maker of low-cost pocket e-ink readers, and the hardware target of the
-CrossPoint Reader / FreeInk firmware ecosystem. **Six products**, four of them
-ESP32-based. See the [family index](xteink/README.md).
-
-| Device | SoC | Panel | Price (2026-09-04) | Record |
-|---|---|---|---|---|
-| [X4 Pro](xteink/x4-pro/README.md) | ESP32-S3, 8 MB PSRAM | 4.26″ 800×480, GT911 touch, warm/cool frontlight | **$99** | deep |
-| [X4](xteink/x4/README.md) | ESP32-C3 | 4.26″ 800×480 | **delisted** | deep |
-| [X3](xteink/x3/README.md) | ESP32-C3 | 3.7″ 792×528, ~257 PPI, IMU + NFC | **$69** | deep |
-| [X4 Classic](xteink/x4-classic/README.md) | ESP32-S3, 8 MB PSRAM | 4.26″ 800×480, 7 buttons, IMU | not listed | medium |
-| [S4](xteink/s4/README.md) | **Android 11** | not established | ¥339 (China) | stub |
-| [Nano / Tong Card 瞳卡](xteink/nano/README.md) | **none — passive NFC-powered** | four-colour e-paper card | not captured | stub |
-
-**Note the naming trap:** the X4 Pro is *not* an enhanced X4. They share a screen
-size and a brand; different SoC architecture, flash layout, input hardware and
-charging connector. Firmware for one will not run on the other.
-
-Three axes of variation are **invisible from outside** and none is externally marked: the **panel controller** (the X3 ships a UC8253 *or* a UC8279d; the X4 family an SSD1677 *or* UC8179 *or* UC8279 — firmware probes the display bus at boot, **except on the X4 Classic, which has no MISO and must trust an NVS byte the factory wrote once**); the **power latch** (at least one X4 revision does not self-latch); and the **USB-lock state**, which owners find **does not correlate with sales channel**.
-
-### Round-two corrections — *2026-09-11*
-
-⚠ **Two rows in the table above are now wrong, and one device is missing from it.** Per this
-repository's append-only rule the stale rows are **left exactly as written**; the corrections are
-here. The family index [`xteink/README.md`](xteink/README.md) carries the full corrected table.
-
-**1. The X4 Classic launched on 2026-09-06, and it replaced the X4.**
-The row above says *"not listed"*. It is listed, and the X4 row's price is the one that is now
-historical:
-
-| Device | Marketed as | Listed | Price | Status 2026-09-11 |
-|---|---|---|---|---|
-| [X4 Classic](xteink/x4-classic/README.md) | **"XTEINK X4 Classic (X4 V2)"** | **2026-09-06** | **USD 79** bare / 95 with base | on sale, in stock |
-| [X4](xteink/x4/README.md) | — | — | last observed ~USD 69 | **withdrawn — the product record *and all four of its dedicated accessories* are gone from the catalogue** |
-
-**The vendor's own store title asserts the succession**: the Classic *is* the second version of
-the X4. The FCC record agrees — `2BTR9-XTEINKX4` granted 2026-01-05, then `2BTR9-X4C` granted
-2026-07-20. On 2026-09-04 the X4's four accessories were still listed but sold out; a week later
-the product records themselves had been removed. **That is a completed withdrawal, not a
-stockout.**
-
-**2. There is a sixth device, and the vendor has never mentioned it.**
-
-| Device | SoC | Panel | Price | Record |
-|---|---|---|---|---|
-| [X4 Light](xteink/x4-light/README.md) | **unknown** | **unknown** | **never listed** | certification-only |
-
-**FCC `2BTR9-X4L`, granted 2026-08-13.** No announcement, no store listing, no price, no review,
-no community mention. It was found by **enumerating Xteink's FCC grantee code `2BTR9`**, not by
-searching for a product name — a vendor's grantee index lists every device it has certified for
-the US, including ones it has never announced. Its internal photographs unlock **2027-02-09**;
-its external photographs are already public and held in the record. ⚠ **"Light" is a marketing
-word and the filing does not define it** — do not infer a specification or a price slot from the
-name.
-
-That makes the table above **seven entries**, not six. Four are confirmed ESP32-based; the X4
-Light's SoC is **unknown**, and the Nano is a passive NFC card rather than a reader.
-
-**3. ⚠ The certification finding for this family is reversed.** Records in this tree stated that
-no FCC or CE filing existed for any Xteink device. **Refuted.** Xteink holds **five granted
-Original Equipment authorisations** under grantee code `2BTR9` — X3, X4, X4 Pro, X4 Classic and
-X4 Light. The original finding confused *"no mark visible in a product photo"* with *"no grant"*.
-Per-device detail and the positive/negative controls that make it evidence:
-`xteink/<record>/certification-and-compliance.md`. Corrections are appended beneath every stale
-claim and listed in
-[`scratch/index-merge/corrections-requiring-review.md`](../scratch/index-merge/corrections-requiring-review.md).
-
-One consequence worth surfacing at index level: the `2BTR9-XTEINKX4` filing's **Internal Photos
-were never withheld**, which makes them the **first public teardown of the Xteink X4** —
-[`xteink/x4/artifacts/certification/`](xteink/x4/artifacts/certification/README.md). The X3's are
-public too; the X4 Pro's unlock **2026-12-12**. Schematics are withheld **permanently** on all
-five filings, so the FCC is not a route to an Xteink schematic.
-
-## LilyGO (Shenzhen Xin Yuan Electronic Technology; also trades as TTGO)
-
-Vendor guide: [LilyGO / TTGO](../vendors/lilygo/README.md). The **T-Display-S3 family** is a *name*, not a platform: eleven boards, eight display
-controllers and four different chargers ship under it. Start at the shared platform record.
-
-| Device | Identity | Depth |
-|---|---|---|
-| [T-Display-S3 family — shared platform](lilygo/t-display-s3-shared/README.md) | family hub: enumeration evidence, shared artifacts, family-wide traps, [board-revision drift](lilygo/t-display-s3-shared/board-revision-drift.md) | — |
-| [T-Display-S3](lilygo/t-display-s3/README.md) | ESP32-S3R8 + 1.9″ 170×320 ST7789V on an **8-bit Intel-8080 parallel** bus. USD 9.04 | **full** |
-| [T-Display-S3 Touch](lilygo/t-display-s3-touch/README.md) | same PCB; panel swapped for one with a bonded CST816S → later CST328 | medium |
-| [T-Display-S3 AMOLED](lilygo/t-display-s3-amoled/README.md) | 1.91″ 240×536 RM67162 on QSPI; **V1.0 and V2.0 sold concurrently** | full-ish |
-| [T-Display-S3 AMOLED Plus](lilygo/t-display-s3-amoled-plus/README.md) | same panel, BQ25896 PMIC + PCF85063ATL RTC + microSD | medium |
-| [T-Display-S3 AMOLED 1.64″](lilygo/t-display-s3-amoled-1-64/README.md) | 280×456 CO5300/ICNA3311 + FT3168 + SY6970 | medium |
-| [T-Display-S3 AMOLED 1.43″/1.75″](lilygo/t-display-s3-amoled-1-43-1-75/README.md) | round 466×466; **two display and two touch controllers behind one product page** | medium |
-| [T4-S3](lilygo/t4-s3/README.md) | the "2.41″ AMOLED": 450×600 RM690B0 + CST226SE. Sold as *T4-S3*, not T-Display-S3 | medium |
-| [T-Display AMOLED Lite](lilygo/t-display-amoled-lite/README.md) | 1.47″ 194×368 SH8501B behind a **1.8 V level shifter**; AXP2101 PMU | medium |
-| [T-Display-S3 Long](lilygo/t-display-s3-long/README.md) | 3.4″ 180×640 bar; **AXS15231B drives display *and* touch from one die** | full-ish |
-| [T-Display-S3 Pro](lilygo/t-display-s3-pro/README.md) | 2.33″ 222×480 ST7796 on plain SPI, camera, microSD, 3 buttons, SY6970 | full-ish |
-| [T-Display-S3 Pro MVSRBoard](lilygo/t-display-s3-pro-mvsrboard/README.md) | audio/RTC/haptic backplate for the Pro | stub |
-| [T-Display (TTGO, ESP32)](lilygo/t-display-ttgo/README.md) | the ancestor. 1.14″ 135×240 SPI. **The only one WLED supports** | lineage stub |
-| [T-QT](lilygo/t-qt/README.md) | thumbnail-sized 128×128 cousin | lineage stub |
-| [T-Dongle-S3](lilygo/t-dongle-s3/README.md) | USB-A dongle, 0.96″ ST7735, on-board microSD | lineage stub |
-| [T-Display K230 / Kit](lilygo/t-display-k230/README.md) | **the repository's first RISC-V device** — see below | full |
-
-### T-Display K230 — *added 2026-09-04*
-
-- [`lilygo/t-display-k230`](lilygo/t-display-k230/README.md) — **T-Display K230** (SKU `K256`/`-A`/`-B`/`-C`) and **T-Display K230 Kit** (`K256-03`, `K277`, `K256-04`, `K256-04-A`). A 4.1″ AMOLED handheld running **Linux on a 64-bit RISC-V** Kendryte K230, with LoRa, a 2 MP MIPI camera, USB Ethernet, a 40-pin header, and an optional QWERTY keyboard base carrying an nRF9151 LTE-M/GNSS modem. **The repository's first RISC-V device.**
-
-⚠ **LilyGO stock codes collide with chip names.** `K230` is a LilyGO SKU for the transparent-case variant of the **T-Embed CC1101**, an ESP32-S3 board with no Kendryte silicon in it. The Kendryte K230 board's SKUs are `K256*` and `K277`. **Never infer silicon from a LilyGO SKU** — and see the [vendor guide](../vendors/lilygo/README.md) for why the wiki must be verified against the board's GitHub repository.
-
----
-
-## Nicolai Electronics
-
-- [Nicolai Electronics Tanmatsu](nicolai-electronics/tanmatsu/README.md), retrieved 2026-08-24, hardware repo commit `640805dd` — "the terminal for hackers": an **ESP32-P4** handheld with a QWERTY keyboard, LoRa, a MIPI-DSI display and a 36-pin expansion port, derived from the Dutch hacker-camp badge lineage ([Badge.team](https://badge.team), MCH2022 / WHY2025) but sold as a product.
-
-Notable for **openness rather than volume**: the full KiCad design is published under **CERN-OHL-P** and the firmware under **MIT**, with a git-maintained Sphinx documentation site. The limiting factor on information is that the device is new and low-volume, and the detail is spread across ~10 repositories.
-
-> *Indexed 2026-09-07.* This record was written in the 2026-08-24 pass but was never linked from this index — an orphan found by the cross-link audit at the end of the 2026-09-04/07 sweep. The entry above is a discoverability fix written from the record's own opening section; **the record itself was not reviewed or modified**, and it remains the authority on its own contents.
-
----
-
-## Two new per-record file types — *added 2026-09-11*
-
-Round two of the 2026-09-04 sweep added two kinds of page to device records across the tree.
-Neither is listed per-device above; both are worth knowing exist.
-
-| File | What it is | Where |
-|---|---|---|
-| `certification-and-compliance.md` | Regulatory grants by jurisdiction — FCC ID, grant date, frequencies, test firm, withheld exhibits and embargo dates — **each carrying the positive and negative controls that make an absence finding mean anything**. Method: [`guides/research/finding-certification-records.md`](../guides/research/finding-certification-records.md) | **32 records**: M5Stack, LilyGO and all five Xteink |
-| `schematic-netlist.md` | A net list **recovered from the vendor's schematic PDF**, not from EDA sources — connector pinouts, per-net membership and the unrouted or mislabelled nets the trace exposed. Method: [`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md) | [`lilygo/t-display-s3-shared`](lilygo/t-display-s3-shared/schematic-netlist.md) · [`m5stack/cardputer-adv`](m5stack/cardputer-adv/schematic-netlist.md) · [`m5stack/dinmeter`](m5stack/dinmeter/schematic-netlist.md) · [`m5stack/cap-lora-1262`](m5stack/cap-lora-1262/schematic-netlist.md) · [`m5stack/cap-cc1101`](m5stack/cap-cc1101/schematic-netlist.md) |
-
-Two of those boards also gained a `driver-vs-document-audit.md` — the vendor driver read
-side-by-side against the schematic and the datasheet:
-[`cardputer-adv`](m5stack/cardputer-adv/driver-vs-document-audit.md) (`M5Cardputer` @ `f1392858`)
-and [`dinmeter`](m5stack/dinmeter/driver-vs-document-audit.md) (`M5DinMeter` @ `8ccbad7`).
-
-**Why the tracing worked, and when it will not.** Altium exports embed invisible `CO` / `PI` /
-`NL` marker tokens at item coordinates — component outlines, pins and net labels — so a net can
-be reconstructed by geometry from the PDF text layer alone. **291 schematic PDFs in this
-repository were assessed**; the per-file verdict is in
-[`scratch/schematic-tracing/traceability-census.md`](../scratch/schematic-tracing/traceability-census.md).
-Two traps that census found, both worth checking before concluding a design is undocumented:
-
-- ⚠ **KiCad and EAGLE exports frequently outline their text to vector paths.** `pdftotext` then
-  yields **zero words** and the file is permanently untraceable. For
-  [`zerowriter/zerowriter-ink`](zerowriter/zerowriter-ink/README.md) and
-  [`seeed-studio/xiao-esp32s3-sense`](seeed-studio/xiao-esp32s3-sense/README.md) **a second,
-  usable export of the same design sits in the same directory** — prefer the `Eeschema` copies.
-- ⚠ **Non-Altium exports carry no `CO`/`PI`/`NL` tokens**, so every binding must be geometric.
-  That applies to the Espressif ESP32-P4 board schematics, which are otherwise traceable.
-
-The richest untraced sheet in the repository is the **M5Stack PaperMono**'s
-`PaperMono_SCH_V0.6.2` — 6 pages, 144 net-label tokens, fully traceable, and **not traced**,
-because that record was owned by another session throughout both rounds.
-
 ---
 
 ## Related
diff --git a/devices/espressif/esp32-p4-eye/sources.md b/devices/espressif/esp32-p4-eye/sources.md
index f37a1da..5cbedbc 100644
--- a/devices/espressif/esp32-p4-eye/sources.md
+++ b/devices/espressif/esp32-p4-eye/sources.md
@@ -42,7 +42,7 @@ adapter boards.
 | ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
 |---|---|---|---|---|---|---|---|---|---|---|
 | P4E-5 | Component documentation mirrored by Espressif — OV2710, HDF2710-47-MIPI, ST7789VW, ZJY154KC-IF17 | third-party manufacturers, via Espressif | authorized mirror | datasheet | `https://dl.espressif.com/AE/esp-dev-kits/{ov2710pbv1.1web,HDF2710-47-MIPI-V2.0,ST7789VW芯片手册,胶铁一体ZJY154KC-IF17}.pdf` | 2026-08-21; all four HTTP 206 `application/pdf` 2026-08-28 | as served | The **camera and display part identities**: an OV2710-based `HDF2710-47-MIPI` camera module, and a `ZJY154KC-IF17` 1.54-inch module driven by an **ST7789VW** | ⚠ **Third-party copyright, mirrored by Espressif with no stated licence** — redistribution status `unknown`; retained for internal engineering reference only. The last two upstream filenames are **Chinese and must be percent-encoded** in the request (`ST7789VW%E8%8A%AF%E7%89%87%E6%89%8B%E5%86%8C.pdf`, `%E8%83%B6%E9%93%81%E4%B8%80%E4%BD%93ZJY154KC-IF17.pdf`); both were renamed to portable ASCII on retrieval. Note the **third distinct path prefix** on this host: `/AE/esp-dev-kits/`, unrelated to `/dl/schematics/` and `/schematics/` | [`../shared-artifacts/`](../shared-artifacts/) — see [its manifest](../shared-artifacts/sources.md) |
-| P4E-6 | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide — **including this board's, whose HTML URL has since moved** (§4) | ⚠ **`master` build — a moving target.** **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Provenance and verified URLs: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `archive/devices/espressif/shared-artifacts/` |
+| P4E-6 | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide — **including this board's, whose HTML URL has since moved** (§4) | ⚠ **`master` build — a moving target.** **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Provenance and verified URLs: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `../hardware-doc-archive/doc/hardware/devices/espressif/shared-artifacts/` |
 | P4E-7 | Failed-download probe log | this repository | — (internal) | — | [`../../../component-download-failures.txt`](../../../component-download-failures.txt) | 2026-08-21 | — | The probes showing the successor's *"ESP32-P4X-EYE Reference Design (ZIP)"* link does not resolve for any filename variant — the reason this EOL record exists | Negative result, retained so the probes are not repeated | [`../../../component-download-failures.txt`](../../../component-download-failures.txt) |
 
 ---
diff --git a/devices/espressif/esp32-p4-function-ev-board/sources.md b/devices/espressif/esp32-p4-function-ev-board/sources.md
index b93bc60..c8f7949 100644
--- a/devices/espressif/esp32-p4-function-ev-board/sources.md
+++ b/devices/espressif/esp32-p4-function-ev-board/sources.md
@@ -42,7 +42,7 @@ All published by Espressif from `dl.espressif.com/dl/schematics/`. All five re-p
 
 | ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
 |---|---|---|---|---|---|---|---|---|---|---|
-| P4F-5 | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide in one file — **including the two EOL guides whose HTML URLs have since moved** (§4), which makes it the most robust surviving copy of P4F-1 | ⚠ **`master` build — a moving target**, not a versioned release; the URL will serve newer content over time. **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Full provenance and verified download URLs: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `archive/devices/espressif/shared-artifacts/` |
+| P4F-5 | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide in one file — **including the two EOL guides whose HTML URLs have since moved** (§4), which makes it the most robust surviving copy of P4F-1 | ⚠ **`master` build — a moving target**, not a versioned release; the URL will serve newer content over time. **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Full provenance and verified download URLs: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `../hardware-doc-archive/doc/hardware/devices/espressif/shared-artifacts/` |
 | P4F-6 | Shared artifact set for the Function-EV family | Espressif Systems and third-party vendors | primary / authorized mirror | datasheet, schematic | see [`../shared-artifacts/sources.md`](../shared-artifacts/sources.md) | 2026-08-21; all re-probed 2026-08-28 | per-file | FPC connector spec, panel and camera datasheets, display-driver datasheets, LCD/camera sub-board schematics and layouts, and the two **adapter-board reference designs with Gerbers, BOM and editable EDA source** | Stored once in [`../shared-artifacts/`](../shared-artifacts/) rather than duplicated into four board directories. Third-party datasheets are mirrored by Espressif with **no stated licence** — redistribution status `unknown` | [`../shared-artifacts/`](../shared-artifacts/) |
 | P4F-7 | Failed-download probe log | this repository | — (internal) | — | [`../../../component-download-failures.txt`](../../../component-download-failures.txt) | 2026-08-21 | — | The recorded probes showing the **successor's** *"Reference Design (ZIP)"* link does not resolve for any filename variant — the reason this EOL record exists | Negative result. Retained so the probes are not repeated | [`../../../component-download-failures.txt`](../../../component-download-failures.txt) |
 
diff --git a/devices/espressif/esp32-p4x-eye/sources.md b/devices/espressif/esp32-p4x-eye/sources.md
index 5cc5d4c..55ba365 100644
--- a/devices/espressif/esp32-p4x-eye/sources.md
+++ b/devices/espressif/esp32-p4x-eye/sources.md
@@ -56,7 +56,7 @@ predecessor's published files are used as the closest available primary evidence
 | ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
 |---|---|---|---|---|---|---|---|---|---|---|
 | PXE-7 | `espressif/esp-dev-kits` — `examples/esp32-p4-eye/examples/factory_demo` | Espressif Systems | primary | repository | <https://github.com/espressif/esp-dev-kits> | 2026-08-21; HTTP 200 2026-08-28 | commit `f6f80ab` at retrieval | The **single official example** for this board, and the concrete demonstration of the P4's AI capability: photo/timed capture, video recording, album preview, USB SD-card mounting, image-parameter configuration, and face / pedestrian / **YOLOv11-nano** detection | ⚠ Example directory named after the **pre-P4X** board. **Not cloned, built or run**; nothing retained locally. **No performance figures published or measured** — the demo's existence is established, its speed is not | – |
-| PXE-8 | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide, **including the EOL guides whose HTML URLs have since moved** | ⚠ **`master` build — a moving target.** **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Provenance: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `archive/devices/espressif/shared-artifacts/` |
+| PXE-8 | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide, **including the EOL guides whose HTML URLs have since moved** | ⚠ **`master` build — a moving target.** **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Provenance: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `../hardware-doc-archive/doc/hardware/devices/espressif/shared-artifacts/` |
 
 ---
 
diff --git a/devices/espressif/esp32-p4x-function-ev-board/sources.md b/devices/espressif/esp32-p4x-function-ev-board/sources.md
index 19c92e8..dfc454a 100644
--- a/devices/espressif/esp32-p4x-function-ev-board/sources.md
+++ b/devices/espressif/esp32-p4x-function-ev-board/sources.md
@@ -23,7 +23,7 @@ throughout that page map onto `P4X-1`–`P4X-5` here.
 | P4X-2 (=S2) | ESP32-P4-Function-EV-Board User Guide (predecessor) | Espressif Systems | primary | manual | **current:** <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp32-p4-function-ev-board/user_guide.html> · **as cited 2026-08-21:** `…/esp32p4/eol/esp32-p4-function-ev-board/user_guide.html` | 2026-08-21; re-verified 2026-08-28 | esp-dev-kits `latest` | The **v1.4 → v1.52 revision history** reproduced in [`README.md` §9](README.md#9-product-history) — the USB-UART → native USB Serial/JTAG change and the **removal of IO24/IO25 from the pin headers**; plus every design-file URL used in §3 | ⚠ **The cited URL is now HTTP 404** — the EOL guides moved. See [the predecessor's manifest §4](../esp32-p4-function-ev-board/sources.md#4-retrieval-findings) for the full migration finding | – |
 | P4X-3 (=S3) | Espressif DevKits product catalogue | Espressif Systems | primary | store listing | <https://www.espressif.com/en/products/devkits> | 2026-08-21; HTTP 200 2026-08-28 (465,290 B) | as served, undated | The board lineup, the marketing description, and the **`ESP32-P4X-Function-EV-Board-L2` SKU string** | ⚠ **The `-L2` suffix is unresolved.** It appears **only** in this catalogue — no user guide, schematic or revision note in `esp-dev-kits` uses it, and this same page says the board has "Same functionality as ESP32-P4-Function-EV-Board". Most likely an accessory-bundle SKU (LCD and camera are optional extras). **Do not assume it is a distinct PCB.** Undated marketing page; no version to pin | – |
 | P4X-4 (=S4) | esp-dev-kits — EOL (End of Life) Boards, ESP32-P4 | Espressif Systems | primary | official page | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/eol/eol-boards.html> | 2026-08-21; HTTP 200 2026-08-28 (15,478 B) | `latest`; source commit `df877cb` on 2026-08-28 | The EOL status of the predecessor boards, which is what makes the §3 substitution necessary | Still live at its original URL — this page did not move | – |
-| P4X-5 (=S5) | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide, including the two EOL guides whose HTML URLs have since moved | ⚠ **`master` build — a moving target**, not a versioned release; the URL serves newer content over time. **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Provenance, Wayback capture and verified URLs: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `archive/devices/espressif/shared-artifacts/` |
+| P4X-5 (=S5) | esp-dev-kits documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release `master`; title page **2026-08-23** | An offline copy of every P4 board user guide, including the two EOL guides whose HTML URLs have since moved | ⚠ **`master` build — a moving target**, not a versioned release; the URL serves newer content over time. **Archived out of the repository 2026-08-24**; 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Provenance, Wayback capture and verified URLs: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `../hardware-doc-archive/doc/hardware/devices/espressif/shared-artifacts/` |
 
 ## 2. Software and tooling references
 
diff --git a/devices/espressif/shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md b/devices/espressif/shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
index fd358f1..a577c44 100644
--- a/devices/espressif/shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
+++ b/devices/espressif/shared-artifacts/ARCHIVED-FRAMEWORK-GUIDES.md
@@ -3,7 +3,7 @@
 One large Espressif **development-board documentation** PDF that used to live in this directory has been moved out of the repository. It was **regenerable from a stable, verified Espressif URL** and is not scarce, unlike the board schematics, PCB layouts, dimension drawings and component datasheets in this directory, **all of which are retained**.
 
 - **Archived:** 2026-08-24
-- **Moved to:** `archive/devices/espressif/shared-artifacts/` (same relative path)
+- **Moved to:** `../hardware-doc-archive/doc/hardware/devices/espressif/shared-artifacts/` (same relative path)
 - **Total reclaimed here:** 30 482 003 bytes (~29.1 MiB)
 
 Nothing was deleted.
diff --git a/devices/espressif/shared-artifacts/esp-dev-kits-en-master-esp32p4.pdf b/devices/espressif/shared-artifacts/esp-dev-kits-en-master-esp32p4.pdf
deleted file mode 120000
index 3606c20..0000000
--- a/devices/espressif/shared-artifacts/esp-dev-kits-en-master-esp32p4.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../archive/devices/espressif/shared-artifacts/esp-dev-kits-en-master-esp32p4.pdf
\ No newline at end of file
diff --git a/devices/espressif/shared-artifacts/sources.md b/devices/espressif/shared-artifacts/sources.md
index c977a46..f05b85c 100644
--- a/devices/espressif/shared-artifacts/sources.md
+++ b/devices/espressif/shared-artifacts/sources.md
@@ -76,7 +76,7 @@ All re-probed **2026-08-28**: HTTP 206, `application/pdf`.
 
 | ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
 |---|---|---|---|---|---|---|---|---|---|---|
-| SA-17 | esp-dev-kits Documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release **`master`**; title page **Aug 23, 2026**; PDF `CreationDate` 2026-08-23 12:25:45; **80 pages** | The offline user guide for **every** P4 board, current and EOL — which now makes it the most robust surviving copy of the two EOL guides whose HTML URLs have since **moved and 404'd** | ⚠ **Archived out of the repository 2026-08-24** to `archive/…` at the same relative path; **nothing was deleted**. Removal was safe because its content was already mined into the five board records on 2026-08-21. ⚠ **`master` build — a moving target**; the URL will serve newer documents over time, so the hash pins only what was fetched. Mitigations: a Wayback capture from 2026-03-31, a fresh Wayback save accepted 2026-08-24, and the docs source in Git. ⚠ The **un-scoped** URL form (without `esp32p4/`) returns HTTP 404. 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Full record: [`ARCHIVED-FRAMEWORK-GUIDES.md`](ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `archive/devices/espressif/shared-artifacts/` |
+| SA-17 | esp-dev-kits Documentation, ESP32-P4 target, PDF build | Espressif Systems | primary | manual | <https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32p4/esp-dev-kits-en-master-esp32p4.pdf> | 2026-08-21; HTTP 206 `application/pdf` 2026-08-28 | release **`master`**; title page **Aug 23, 2026**; PDF `CreationDate` 2026-08-23 12:25:45; **80 pages** | The offline user guide for **every** P4 board, current and EOL — which now makes it the most robust surviving copy of the two EOL guides whose HTML URLs have since **moved and 404'd** | ⚠ **Archived out of the repository 2026-08-24** to `../hardware-doc-archive/…` at the same relative path; **nothing was deleted**. Removal was safe because its content was already mined into the five board records on 2026-08-21. ⚠ **`master` build — a moving target**; the URL will serve newer documents over time, so the hash pins only what was fetched. Mitigations: a Wayback capture from 2026-03-31, a fresh Wayback save accepted 2026-08-24, and the docs source in Git. ⚠ The **un-scoped** URL form (without `esp32p4/`) returns HTTP 404. 30,482,003 B, SHA-256 `04d75d2acda82c8f5136bfed4d1732e7e4bd095437e2ecacce271374d8f8538c`. Full record: [`ARCHIVED-FRAMEWORK-GUIDES.md`](ARCHIVED-FRAMEWORK-GUIDES.md) | archived → `../hardware-doc-archive/doc/hardware/devices/espressif/shared-artifacts/` |
 
 ## 6. Verification and reacquisition sources
 
diff --git a/devices/lilygo/t-display-amoled-lite/README.md b/devices/lilygo/t-display-amoled-lite/README.md
deleted file mode 100644
index 5613155..0000000
--- a/devices/lilygo/t-display-amoled-lite/README.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# LilyGO T-Display AMOLED Lite (1.47″)
-
-> Store handle `t-display-amoled-lite`, SKU `H593`, **USD 35.66**, in stock 2026-09-07.
-> Published **2022-11-12** — **five months before** the T-Display-S3 AMOLED 1.91″, despite the
-> "Lite" name. It is the *first* AMOLED board in the line, not a cut-down later one.
->
-> Covered by `LilyGo-AMOLED-Series` @ **`6d1dc008b94578cc34ba4a0f3b223dd808ca963f`**.
-> Research retrieved 2026-09-07. **Depth: medium.** No hardware.
-> Note LilyGO does **not** put "S3" in this product's name.
-
-## Identity — the odd one out
-
-| | | Source |
-|---|---|---|
-| Panel | 1.47″ AMOLED, **194 × 368**, **450 nits** | library README @ `6d1dc00` |
-| Display driver | **SH8501B** — **Shenghe Microelectronics**, established from the datasheet cover | `datasheet/SH8501B0 DataSheet.pdf` |
-| **Level shifter `U2`** | **RS0108YTQC20** — the panel runs at **1.8 V** and the ESP32-S3 at 3.3 V. Every display and touch signal crosses a translator (`AM_SPI_*_1V8`, `TP_INT_1V8` nets on the sheet) | schematic |
-| Touch | **CHSC5816** (Chipsemi) | library README | 
-| **PMU `U5`** | **X-Powers AXP2101** — a full PMU with I²C, ADC and multiple rails. The only board in the family with one | schematic + `examples/PMU_ADC`, `PMU_Interrupt` |
-| Ambient light | **CM32181** (Capella) | library README datasheet links |
-| RGB LED `U6` | **WS2812B-2020** on GPIO18 | schematic; `BOARD_PIXELS_PIN (18)`, `BOARD_PIXELS_NUM 1` |
-| Other | `U4 = BV6804` (unidentified), `Q1 AO3400`, blue LED, USB-C 3.0 receptacle `J1` | schematic |
-| Component records | [`shenghe-microelectronics/sh8501b`](../../../components/shenghe-microelectronics/sh8501b/README.md) · [`x-powers/axp2101`](../../../components/x-powers/axp2101/README.md) · [`chipsemi/chsc5816`](../../../components/chipsemi/chsc5816/README.md) · [`capella-microsystems`](../../../components/capella-microsystems/) · [`worldsemi`](../../../components/worldsemi/) |
-
-**The 1.8 V level-shifted panel is the defining difference.** Nothing else in the family has
-one, and it explains both the AXP2101 (multiple rails) and why this board's code is not
-interchangeable with the other AMOLED boards despite sharing a library.
-
-## Pinout
-
-`product_pins.h` block `#if CONFIG_LILYGO_T_AMOLED_LITE_147` @ `b1a1cc5`:
-
-| Signal | GPIO |
-|---|---|
-| `DISP_CS` / `SCK` | 4 / 5 |
-| `DISP_DATA0..3` | 7, 10, 11, 12 |
-| `DISP_RESET` / `TE` | 40 / 6 |
-| `I2C_SDA` / `SCL` | 1 / 2 |
-| `PMU_IRQ` | 3 |
-| `SENSOR_IRQ` | 8 |
-| `TOUCH_IRQ` / `TOUCH_RST` | 13 / 14 |
-| `BOOT` / `BUTTON1` / `BUTTON2` | 0 / 0 / 21 |
-| `PIXELS` (WS2812B) | 18 |
-
-## Vendor-stated limitations
-
-From the library README @ `6d1dc00`, FAQ 3:
-> "**1.47 inches AMOLED (T-Display-AMOLED-Lite)** does not support hardware screen rotation
-> function"
-
-and the current table:
-> **90–230+ mA** active; **≈1.1 mA** deep sleep, **timer wakeup only**
-
-That 1.1 mA is **five times** the 1.91″/2.41″ boards' 230 µA, and the wake source is limited to
-a timer where the others support external GPIO0 wake. **This is the worst board in the family
-for battery life**, and the vendor says so in a table most people skip.
-
-Examples specific to it: `LumenMeter` (the CM32181 ambient-light sensor), `PMU_ADC`,
-`PMU_Interrupt` — the last two are marked *"only support 1.47-inch AMOLED"*.
-
-## Artifacts
-
-`artifacts/schematic/T-Display_AMOLED-Lite.pdf` — 417 259 B,
-SHA-256 `3660881df7844a145b7f773fdb41f27679ddb1bce49a95d0122d8b9b014a01ca`, retrieved 2026-09-07
-at `6d1dc00`. The SH8501B0 datasheet is filed under
-[`components/shenghe-microelectronics/sh8501b/artifacts/`](../../../components/shenghe-microelectronics/sh8501b/artifacts/).
-
-## Sources
-
-| ID | Source | Class | Retrieved |
-|---|---|---|---|
-| L1 | `LilyGo-AMOLED-Series` README.MD @ `6d1dc00` | primary | 2026-09-07 |
-| L2 | `schematic/T-Display_AMOLED-Lite.pdf` @ `6d1dc00` | primary | 2026-09-07 |
-| L3 | `LilyGo-Display-IDF/main/product_pins.h` @ `b1a1cc5` | primary | 2026-09-07 |
-| L4 | `datasheet/SH8501B0 DataSheet.pdf` @ `6d1dc00` | credible mirror | 2026-09-07 |
-| L5 | LilyGO store feed | primary | 2026-09-07 |
-
-## Gaps
-
-- Medium-depth stub: no `features/`, no example catalogue, no acquisition manifest.
-- `BV6804` (`U4`) unidentified — same family as the `BV6802` on the 1.91″ AMOLED V1.0.
-- **No ESPHome model** for this board (the other three AMOLEDs have one).
-- Net connectivity not traced. No hardware.
diff --git a/devices/lilygo/t-display-amoled-lite/artifacts/schematic/T-Display_AMOLED-Lite.pdf b/devices/lilygo/t-display-amoled-lite/artifacts/schematic/T-Display_AMOLED-Lite.pdf
deleted file mode 100644
index 424a826..0000000
Binary files a/devices/lilygo/t-display-amoled-lite/artifacts/schematic/T-Display_AMOLED-Lite.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-amoled-lite/certification-and-compliance.md b/devices/lilygo/t-display-amoled-lite/certification-and-compliance.md
deleted file mode 100644
index cedd069..0000000
--- a/devices/lilygo/t-display-amoled-lite/certification-and-compliance.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Certification and compliance — t-display-amoled-lite
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-⚠ **No FCC grant found** naming 'AMOLED Lite'. Controlled absence; see §4.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-amoled-lite/market-and-pricing.md b/devices/lilygo/t-display-amoled-lite/market-and-pricing.md
deleted file mode 100644
index d39eb3d..0000000
--- a/devices/lilygo/t-display-amoled-lite/market-and-pricing.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Market and pricing — t-display-amoled-lite
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display AMOLED Lite | 2022-11-12 | T-Display AMOLED  Lite [H593] | `H593` | **USD 35.66** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 35.66, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-amoled-lite`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `H593`.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-k230/README.md b/devices/lilygo/t-display-k230/README.md
deleted file mode 100644
index 71aa5b0..0000000
--- a/devices/lilygo/t-display-k230/README.md
+++ /dev/null
@@ -1,404 +0,0 @@
-# LILYGO T-Display K230 / T-Display K230 Kit
-
-> **Product IDs:** bare board `K256` / `K256-A` / `K256-B` / `K256-C` · kit `K256-03` / `K277` / `K256-04` / `K256-04-A`
-> **Status:** in production, actively developed (BSP `v0.2.4`, 2026-09-03) · **Research retrieved 2026-09-04**
-> **Evidence basis:** LilyGO's own board-support repository at commit `bb831ab358b66f5bd9a87ecd7c580fee4537492e`, the Shopify product JSON, the LilyGO wiki, the Canaan K230 datasheets, and Reddit threads. **No hardware was in hand; nothing below was executed or measured.**
-
----
-
-## 1. Identity, SKUs and variants
-
-The board's **confirmed marketed name is "T-Display K230"**, and the keyboard bundle is
-**"T-Display K230 Kit"**. It is *not* a T-Deck, not a "T-Deck K230", not a "T-K230" and not a
-"Cardputer". Those were plausible names to search for and every one of them is wrong; LilyGO
-files this product in its **T-Display** series, alongside T-Display-S3 and T-Display P4.
-
-### The SKU trap
-
-| String | What it actually is |
-|---|---|
-| **`K230`** | A **LilyGO stock code for the transparent-shell T-Embed CC1101** — an ESP32-S3 board containing no Kendryte silicon at all. It is the top hit when you search the LilyGO store for "K230". |
-| `K230-A`, `K230DE`, `K230US`, `K230-ADE`, `K230-AUS` | Same T-Embed CC1101, black shell and regional-warehouse suffixes. |
-| **`K256*` / `K277`** | The **actual Kendryte K230 boards.** |
-
-**LilyGO stock codes collide with chip part numbers and carry no information about silicon.**
-Never infer hardware from a LilyGO SKU. (Reusable version of this finding:
-[`scratch/lilygo-k230/vendor-guide-additions.md`](../../../scratch/lilygo-k230/vendor-guide-additions.md).)
-
-### Bare board — "T-Display K230", `/products/t-display-k230`
-
-Shopify product id `8182759063733`, created **2025-03-21 13:52 +08:00**, published **2025-03-21 14:22 +08:00**.
-
-| SKU | Variant | Price (2026-09-04) | Available |
-|---|---|---:|---|
-| `K256` | 868 MHz | $98.79 | yes |
-| `K256-A` | 915 MHz | $98.79 | yes |
-| `K256-B` | 923 MHz | $98.79 | yes |
-| `K256-C` | 433 MHz | $98.79 | yes |
-
-All four differ **only** in the LoRa band. Same PCB, same silicon otherwise.
-
-### Kit — "T-Display K230 Kit", `/products/t-display-k230-kit`
-
-Shopify product id `10544222011573`, created **2026-08-06 09:31 +08:00**, published **2026-08-20 15:10 +08:00**.
-
-| SKU | Variant | Price (2026-09-04) | What you get |
-|---|---|---:|---|
-| `K256-03` | Main Unit / **SX1262** / 868 MHz | **$150.31** | K230 main unit in the kit configuration |
-| `K277` | Main Unit / **LR2021** / 830–940 MHz | **$153.01** | Same, with the newer multi-protocol radio |
-| `K256-04` | **Keyboard Only** / **with nRF9151** | **$113.25** | Keyboard base including the cellular/GNSS SiP |
-| `K256-04-A` | **Keyboard Only** / **without nRF9151** | **$70.94** | Keyboard base, no cellular |
-
-**Read that table carefully — it is the single most misread thing about this product.** "Main
-Unit" and "Keyboard Only" are *separate purchases*. There is no single SKU that is "the whole
-handheld". A buyer wanting the complete keyboard handheld with cellular pays
-**$150.31 + $113.25 = $263.56** before shipping. A Reddit user on the launch thread asked
-exactly this — "I'm confused on what is what… I want the kit with the keyboard. What do I buy?"
-— and received no answer (R-KIT).
-
-The **$42.31 delta** between `K256-04` and `K256-04-A` is the cleanest available price for the
-nRF9151 cellular option.
-
-### Third variant: "Cased Version"
-
-LilyGO's wiki documents a **T-Display K230 Cased Version** at
-`/products/t-display-series/t-display-k230/cased-version.html`: a 110 × 58 × 30 mm enclosed unit
-with speaker, microphone, 3.5 mm jack, QWIIC and an nRF52840 GPIO expansion header. It has **no
-shop listing** as of 2026-09-04. A buyer confirmed on 2026-08-13 that "the encased K230 model
-that goes with keyboard is a newer one that isn't listed on the website yet" (R-CASE), and an
-earlier buyer received "just the screen and motherboard on risers in the package" — no case, no
-battery (R-BARE).
-
-### Related but distinct
-
-| Product | Relationship |
-|---|---|
-| **T-Display P4** | Espressif ESP32-P4 sibling in the same T-Display line, with **its own, incompatible keyboard** (`/products/t-display-p4-keyboard`). LilyGO confirmed on 2026-07-28: "the keyboard for the T-Display K230 does **not** fit the T-Display P4". |
-| **T-Deck / T-Deck Plus / T-Deck Pro / T-Deck MAX** | LilyGO's *other* keyboard handheld family, all ESP32-S3. Different series, different keyboard, different everything. A sibling session documents **T-Display-S3 and variants** in this repository (expected at `devices/lilygo/t-display-s3*`; not yet present at the time of writing, so no link is given). |
-| **CanMV-K230**, **BPI-CanMV-K230D-Zero** | Other K230 boards; see [the K230 component record](../../../components/canaan/k230/README.md#13-notable-k230-boards). |
-
----
-
-## 2. What it is, and visual identification
-
-A **4.1-inch AMOLED handheld running Linux on a 64-bit RISC-V SoC**, with LoRa, a 2 MP camera,
-an RJ45 Ethernet port, a 40-pin expansion header, and — via the Kit — a physical QWERTY keyboard
-base carrying an LTE-M/NB-IoT/GNSS modem, a charger, a fuel gauge and a keyboard scanner.
-
-Identify it by, in descending order of reliability:
-
-1. **The tall narrow AMOLED.** 568 × 1232 in a 104 × 51 mm board is an unusually tall aspect
-   ratio; it looks like a phone screen, because it is one.
-2. **An RJ45 socket on a handheld.** Almost nothing else in this class has one, and community
-   reaction on first sight was "the ethernet port is an odd choice. It just seems too big for
-   this type of device" (R-ETH).
-3. **A 2 × 20 pin header** along the long edge.
-4. **No ESP32 markings** and a large BGA under the shield/heat area.
-
-Images with full provenance: [`media.md`](media.md) and [`media/manifest.json`](media/manifest.json).
-
----
-
-## 3. Product history, family and culture
-
-Full timeline with sources: [`product-history-and-family.md`](product-history-and-family.md).
-Condensed:
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2023-07-06 | Canaan K230 datasheet V1.0 | C1 |
-| 2023-10-24 | CanMV-K230 reference board covered by CNX-Software | N1 |
-| **2025-03-21** | **T-Display K230 created and published on lilygo.cc**; announced on r/LilyGO the same day; **sold out within days** | D1, R-LAUNCH |
-| 2025-03-26 | oreboot maintainer publicly notes oreboot supports K230 and boots Linux from mask ROM over USB in ~3 s | R-OREBOOT |
-| 2025-07-07 | r/meshtastic post reaches **187 points / 40 comments** — the board's largest single moment of attention | R-MESH |
-| 2026-07-28 | Keyboard announced on r/LilyGO | R-KB |
-| **2026-08-06 / 2026-08-20** | **T-Display K230 Kit created / published**; announced on r/LilyGO (83 points) | D2, R-KIT |
-| 2026-08-13 | BSP repository `Xinyuan-LilyGO/T-Display-K230` created | G1 |
-| 2026-08-16 | nRF52840 AT firmware build `r4` | G3 |
-| 2026-08-23 · 2026-08-14 | nRF52840 and nRF9151 firmware repositories last pushed | G3, G4 |
-| **2026-09-03** | BSP **v0.2.4** — PicoClaw chat app, Meshtastic map-tile download, storage expansion, async I²C scan | G1 |
-
-**Culture.** This is a LilyGO product in the strong sense: shipped early, documented late,
-supported publicly on Reddit by `u/LilyGoXinyuan`, and improved rapidly afterwards. The BSP
-repository is **three weeks old at the time of writing and already at v0.2.4**. The gap between
-"board on sale" (2025-03-21) and "board-support repository exists" (2026-08-13) is **almost
-seventeen months**, which is the single best explanation for the early-owner experience
-described in [§8](#8-shortcomings-and-constraints).
-
----
-
-## 4. Key specifications
-
-Every functional part links to its component record.
-
-| Function | Part | Interface / detail | Component record |
-|---|---|---|---|
-| **SoC** | **Canaan Kendryte K230** | 2 × XuanTie C908 RISC-V 64-bit: **CPU1 @ 1.6 GHz with RVV 1.0**, CPU0 @ 800 MHz; KPU/NPU, DPU, 2.5D GPU, H.264+H.265 VPU, ISP | [canaan/k230](../../../components/canaan/k230/README.md) |
-| **DRAM** | LPDDR4, **8 Gb = 1 GB**, 32-bit | external (K230 13 × 13 mm package, not the K230D SiP) | [canaan/k230](../../../components/canaan/k230/README.md#6-audio-memory-and-peripherals) |
-| **Display** | **RM69A10** 4.1″ AMOLED | MIPI DSI, **RGB 568 × 1232**, `GPIO22` reset, `GPIO25` enable, DSI-command backlight | [raydium/rm69a10](../../../components/raydium/rm69a10/README.md) |
-| **Touch** | **Goodix GT9895** ("Berlin") | I²C3 `GPIO37`/`GPIO36`, addr **`0x5D`**, IRQ `GPIO23`, RST `GPIO24` | [goodix/gt9895](../../../components/goodix/gt9895/README.md) |
-| **Camera** | **GalaxyCore GC2093** 2 MP | MIPI CSI + I²C0 `GPIO49`/`GPIO48`, addr **`0x37`** | [galaxycore/gc2093](../../../components/galaxycore/gc2093/README.md) |
-| **Wi-Fi** | **Realtek RTL8189FS** | SDIO, 802.11 b/g/n 2.4 GHz, `wlan0` | [realtek/rtl8189fs](../../../components/realtek/rtl8189fs/README.md) |
-| **Bluetooth** | **USB dongle** (CSR8510/8891 workaround) | *no on-board BT radio* | see [features/wifi-and-bluetooth.md](features/wifi-and-bluetooth.md) |
-| **Ethernet** | **RTL8152B** claimed, 100 Mbps, `eth0` | USB-attached; **K230 has no Ethernet MAC** | [realtek/rtl8152b](../../../components/realtek/rtl8152b/README.md) |
-| **LoRa** | **Semtech SX1262** *or* **LR2021** | SPI `GPIO15/16/17`, CS `GPIO14`, RST `GPIO5`, BUSY `GPIO19`, IRQ `GPIO20`, PWR `GPIO44`; **spidev + RadioLib** | [semtech/sx1262](../../../components/semtech/sx1262/README.md) · [semtech/lr2021](../../../components/semtech/lr2021/README.md) |
-| **HDMI bridge** | **LT9611** — *presence unconfirmed* | shares touch I²C/IRQ/reset; boot-time alternative to AMOLED | [lontium/lt9611](../../../components/lontium/lt9611/README.md) |
-| **Storage** | microSD | MMC1 `GPIO54–59`; **also the boot medium** | [generic/micro-sd-sdmmc](../../../components/generic/micro-sd-sdmmc/README.md) |
-| **Keyboard scanner** | **TI TCA8418** | I²C4, addr **`0x34`**, RST `GPIO43`, IRQ `GPIO42`; **7 ROW × 10 COL** | [texas-instruments/tca8418](../../../components/texas-instruments/tca8418/README.md) |
-| **GPIO expander** | **XL9555** | I²C4, addr **probed** in `0x20–0x27` | [xlsemi/xl9555](../../../components/xlsemi/xl9555/README.md) |
-| **Charger** | **TI BQ25896** | I²C4, addr **`0x6B`** | [texas-instruments/bq25896](../../../components/texas-instruments/bq25896/README.md) |
-| **Fuel gauge** | **TI BQ27220** | I²C4, addr **`0x55`** | [texas-instruments/bq27220](../../../components/texas-instruments/bq27220/README.md) |
-| **Cellular + GNSS** | **Nordic nRF9151** | UART3 `GPIO28/29` @115200, enable `GPIO2`; NCS v3.4.0 Serial LTE Modem | [nordic-semiconductor/nrf9151](../../../components/nordic-semiconductor/nrf9151/README.md) |
-| **BLE central** | **Nordic nRF52840** | UART1 `GPIO3/4` @115200; also drives the 21700 5 V boost on `P0.04` | [nordic-semiconductor/nrf52840](../../../components/nordic-semiconductor/nrf52840/README.md) |
-| **Audio amp** | **MAX98357A** | I²S `GPIO32/33/35`, SD `GPIO34` | [analog-devices/max98357a](../../../components/analog-devices/max98357a/README.md) |
-| **Temp/humidity** | **AHT20** | I²C4, addr **`0x38`** | [asair/aht20](../../../components/asair/aht20/README.md) |
-| **PMIC, speaker amp, microphone, 21700 pack** | **unidentified** | — | [unidentified/t-display-k230](../../../components/unidentified/t-display-k230/README.md) |
-| Dimensions | 104 × 51 × 15.5 mm (board) · ~110 × 58 × 30 mm (cased) | | |
-| USB charging | 5 V, 500 mA | | |
-
-**What the table means in practice.** Only the first eleven rows are on the main board. Rows
-from TCA8418 down are on **base boards you buy separately** — and the launcher treats every one
-of them as optional, detected at runtime. A bare `K256` is a screen, a camera, a radio and a
-40-pin header; it is not a handheld until you add a base.
-
----
-
-## 5. Architecture
-
-```
-                    ┌──────────────────────── K230 main board (K256*) ────────────────────────┐
-   4.1" AMOLED ─DSI─┤ RM69A10                                                                 │
-   GT9895 touch ─I²C3(G37/G36)+IRQ G23+RST G24─┐                                              │
-   LT9611 HDMI  ─── same four lines ───────────┘   ┌─────────────────────┐                    │
-   GC2093 cam  ─CSI + I²C0(G49/G48 @0x37)──────────┤   Kendryte K230     │                    │
-   microSD     ─MMC1 (G54..G59) ── BOOT MEDIUM ────┤ CPU1 1.6GHz  RVV1.0 │── 1 GB LPDDR4      │
-   RTL8189FS   ─SDIO ────────────────────────── ───┤ CPU0 0.8GHz  Linux  │                    │
-   SX1262/LR2021─SPI(G15/16/17) CS G14 RST G5      │ KPU DPU GPU VPU ISP │                    │
-                 BUSY G19 IRQ G20 PWREN G44 ───────┤                     │                    │
-   RTL8152B ─USB─ RJ45                             │  PMU  ── INT0 = power key (G64)          │
-   USB-BT dongle ─USB─                             └──────────┬──────────┘                    │
-   BOOT0 button ── G0                                         │ 2x20 header                   │
-   └───────────────────────────────────────────────────────── │ ──────────────────────────────┘
-                                                              │
-        ┌─────────────────────────────────────────────────────┴───────────────────────────┐
-        │                                                                                 │
- ┌──────┴────── nRF52840 base ──────┐              ┌───────────── nRF9151 keyboard base ──┴────────┐
- │ nRF52840 ─UART1 G3/G4 @115200    │              │ nRF9151 ─UART3 G28/G29 @115200, EN G2        │
- │   P0.04 → 21700 5 V boost enable │              │ TCA8418  0x34  RST G43  IRQ G42   7x10 matrix│
- │ AHT20   0x38 ─┐                  │              │ XL9555   0x20-0x27 (probed) ─┐               │
- │ MAX98357A ─I²S G32/33/35, SD G34 │              │ BQ25896  0x6B ───────────────┼─ I²C4 G46/G47 │
- └───────────────┴─ I²C4 G46/G47 ───┘              │ BQ27220  0x55 ───────────────┘               │
-                                                   │ keyboard backlight ← G52 / PWM4              │
-                                                   └──────────────────────────────────────────────┘
-```
-
-Three structural points:
-
-1. **One MIPI DSI output, two possible sinks.** The AMOLED and the LT9611 HDMI bridge cannot run
-   at once; the BSP builds a *separate device tree* (`k230-canmv-rm69a10-hdmi`) for the HDMI
-   case. HDMI is a boot-time alternative and LilyGO calls it "a diagnostic feature".
-2. **Everything the K230 lacks is bolted on over a serial bus.** No radio on the die → SDIO
-   Wi-Fi + USB Bluetooth + SPI LoRa + UART cellular + UART BLE. No Ethernet MAC → USB Ethernet.
-   That is five external devices doing what an integrated SoC would do internally, and it is the
-   defining architectural fact of the board.
-3. **The two base boards share one I²C bus (I²C4, `GPIO46`/`GPIO47`) and are mutually
-   exclusive in practice** — they are different physical bases. Nothing prevents address
-   collisions in principle, but as fitted, `0x38` (AHT20), `0x34`, `0x55`, `0x6B` and `0x20–0x27`
-   do not overlap.
-
----
-
-## 6. Common uses and representative projects
-
-| Use | Status | Notes |
-|---|---|---|
-| **Phone-style LVGL launcher** with camera, gallery, music, network radio, recorder, video player, terminal, MTP, settings | **Stable** per LilyGO | The shipped default experience |
-| **Meshtastic handheld** | **Beta** | Chat, node display, map view, channel sharing. **Voice/photo transfer requires LR2021**; SX1262 units get text only |
-| **LoRaWAN tooling** | Beta | `lorawan_test.cpp`, RF test profiles |
-| **On-device AI** — face detection, QR scan, AI camera | Working | KPU-accelerated; `camera_face_detect.cpp`, `ui_ai_demo.c` |
-| **Xiaozhi voice assistant** | Beta | Needs network + a compatible Xiaozhi service; wake-word only while the app owns the mic |
-| **PicoClaw** LLM chat client | Beta (v0.2.4) | Needs an OpenAI-compatible API key |
-| **NES emulator** | Present | `ui_nes.cpp`; **ROMs not bundled** |
-| **Offline maps** | Present | Tile downloader added v0.2.4; **tiles not bundled** |
-| **Cellular data / GNSS** | Beta | Requires the `K256-04` keyboard base |
-| **nRF52840 UART DFU from the K230** | Beta | Field-update the companion MCU with no PC |
-
-Community-originated work is catalogued in
-[`projects-and-community.md`](projects-and-community.md). The most substantive third-party items
-are **oreboot** (K230 support, mask-ROM USB boot), **k230-debian**, and an in-progress
-independent Meshtastic UI announced 2026-06-02.
-
----
-
-## 7. Distinctive strengths
-
-- **It is a RISC-V Linux handheld you can buy for $98.79.** Not an MCU running a GUI library —
-  a Linux userspace with 1 GB of RAM, a package set, SSH, and a terminal app.
-- **1 GB LPDDR4 is 2× the CanMV-K230 reference board and 8× a K230D board.** Among K230 hardware
-  this is the memory-rich option, and memory is the binding constraint on that SoC.
-- **A genuine NPU plus H.265 encode *and* decode**, which nothing in the ESP32 class has.
-- **Radio choice at purchase**, including a current-generation LR2021.
-- **The BSP is unusually good for LilyGO**: a documented pin map, 30+ named kernel patches, a
-  pinned upstream SDK commit, pinned kernel commit, pinned toolchain version, an `overlay_manifest.txt`,
-  and separate repositories for each companion MCU with their own patch sets and prebuilt firmware.
-- **Companion-MCU firmware is open and buildable**, including the nRF9151 Serial LTE Modem fork
-  with its five patches and the pinned upstream commit they apply to.
-
-## 8. Shortcomings and constraints
-
-- **Bricking is real and recovery is not documented by LilyGO.** A verified owner: "I managed to
-  get an mp3 player and notepad working… but once I attempted to turn on the 'fun' features it
-  bricked it… my board is still unresponsive to boot pin and term. I think I flashed it into mmc
-  mode vs sd card and it's stuck" (R-BRICK, 2026-08-21 / 2026-08-28). There is **no recovery
-  section in any LilyGO document**. See [`factory-firmware.md`](factory-firmware.md).
-- **The 17-month documentation gap.** Sold from 2025-03-21; BSP repository created 2026-08-13.
-  Early buyers were on their own — "I've also been completely unable to figure out how to even
-  get an OS installed" (R-BARE).
-- **No Bluetooth without a USB dongle**, and the dongle support is two patches whose own
-  filenames say *workaround* and *experimental*.
-- **The kit is two purchases**, and the store does not say so clearly.
-- **Ethernet is 100 Mbit over USB**, not a MAC.
-- **Nothing in the ESP32 ecosystem applies.** No Arduino, no PlatformIO for the main SoC, no
-  ESP-IDF. LilyGO's own FAQ says so: "No. T-Display K230 is based on the Kendryte K230 RISC-V SoC
-  and requires the K230 SDK toolchain."
-- **Build host requirements are heavy**: Ubuntu 20.04/22.04/24.04 or WSL2 or Docker, plus a
-  vendor toolchain at a hard-coded `/opt/toolchain` path. On NixOS this needs deliberate work —
-  [`guides/nixos/riscv-and-vendor-sdk-toolchains.md`](../../../guides/nixos/riscv-and-vendor-sdk-toolchains.md).
-- **No schematic is published.** The wiki has a `#schematic` heading with nothing under it.
-- **No IP rating.** "Wish there were more IPX water resistant options across all your product
-  lines. I prototype field devices" (R-IPX).
-- **Battery life is unmeasured** and community scepticism is explicit: "the battery life on this
-  would be less than it would be with just a phone and a regular nRF node" (R-BATT) — an opinion,
-  not a measurement, and nobody has published a measurement.
-
-## 9. Performance summary
-
-**No independent benchmark of this board exists.** Everything available is either a Canaan
-silicon-level claim or a vendor statement. The BSP does build **CoreMark and CoreMark-PRO** into
-the image (`BR2_PACKAGE_COREMARK=y`, `BR2_PACKAGE_COREMARK_PRO=y`), so the board ships with the
-tools to produce a number that nobody has published. Full treatment, including exactly what to
-run: [`performance.md`](performance.md).
-
-## 10. Pricing and availability
-
-Dated observations, currency conversion notes and stock evidence: [`market-and-pricing.md`](market-and-pricing.md).
-Headline, **2026-09-04, lilygo.cc, USD**: bare board **$98.79**; kit main unit **$150.31**
-(SX1262) or **$153.01** (LR2021); keyboard base **$113.25** (with nRF9151) or **$70.94**
-(without). Complete keyboard handheld with cellular: **$263.56** before shipping.
-
-## 11. Competitors, equivalents and clones
-
-Full comparison: [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md).
-Nearest things: LilyGO **T-Deck Plus** (ESP32-S3, cheaper, mature, no Linux),
-**T-Display P4** (ESP32-P4, MCU-class, its own keyboard), **M5Stack Cardputer**
-(much cheaper, much less capable), **CanMV-K230** (same SoC, no display, half the RAM),
-**BPI-CanMV-K230D-Zero** ($29, K230D, 128 MB). **No clone of this board was found.**
-
-## 12. Launch-era versus current market fit
-
-**At launch (2025-03-21):** near-unique. A sub-$100 RISC-V Linux handheld with AMOLED and LoRa
-had no direct equivalent, which is why the r/meshtastic thread drew 187 points. But there was no
-board-support repository, no wiki entry with substance, and no keyboard — it was a development
-board with a beautiful screen and no software story.
-
-**Now (2026-09-04):** the software story exists and is moving weekly, and the keyboard makes it a
-handheld. But the competitive picture changed: the **T-Display P4** exists in the same line with
-a mature toolchain, and the K230's own advantage — Linux — is still gated behind a build process
-that assumes Ubuntu and a vendor toolchain. It is a much better product than it was and a
-slightly harder sell.
-
-## 13. When to use / when not to use
-
-**Use it when** you need on-device Linux with a real NPU and a MIPI camera in a handheld form
-factor; when you specifically want RISC-V; when you want LoRa mesh with **voice/photo** transfer
-(LR2021 only); or when you need a Linux userspace — Python, SSH, standard tooling — on a
-battery-powered device with a screen.
-
-**Do not use it when** you want an Arduino/ESP-IDF workflow; when you need Bluetooth without a
-dongle; when you need a documented recovery path for a fleet; when you need gigabit Ethernet or
-5 GHz Wi-Fi; when you need certified radios for a product; or when the project is a Meshtastic
-node and nothing more — a $30 dedicated node does that better and lasts far longer on a charge.
-
-**Alternatives by tier:** [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md).
-
----
-
-## 14. Common tasks / How do I…?
-
-| I want to… | Guide |
-|---|---|
-| Drive the 4.1″ AMOLED, set brightness, understand the boot-logo handoff | [features/display.md](features/display.md) |
-| Read touch input | [features/touch.md](features/touch.md) |
-| Use the QWERTY keyboard, read the key matrix, change F-key actions, set backlight | [features/keyboard.md](features/keyboard.md) |
-| Capture from the camera, run face detect / QR / RTSP | [features/camera.md](features/camera.md) |
-| Get on Wi-Fi; get Bluetooth working at all | [features/wifi-and-bluetooth.md](features/wifi-and-bluetooth.md) |
-| Use the RJ45 Ethernet port | [features/ethernet.md](features/ethernet.md) |
-| Send and receive LoRa; choose between SX1262 and LR2021; run Meshtastic | [features/lora.md](features/lora.md) |
-| Play or record audio, use the I²S amplifier, use the microphone | [features/audio.md](features/audio.md) |
-| Mount, resize or replace the microSD card | [features/microsd.md](features/microsd.md) |
-| Use USB — host, gadget, MTP, mass storage | [features/usb.md](features/usb.md) |
-| Read battery state, configure charging and low-battery shutdown | [features/battery-and-power.md](features/battery-and-power.md) |
-| Use the 40-pin header, ADCs, I²C, PWM, spare GPIO | [features/gpio-and-expansion.md](features/gpio-and-expansion.md) |
-| Run a neural network on the KPU/NPU | [features/kpu-npu.md](features/kpu-npu.md) |
-| Understand and use the two CPU cores and RVV | [features/dual-core-riscv.md](features/dual-core-riscv.md) |
-| Talk to the nRF52840 (BLE) or nRF9151 (cellular/GNSS) | [features/nrf52840-ble.md](features/nrf52840-ble.md) · [features/nrf9151-cellular-gnss.md](features/nrf9151-cellular-gnss.md) |
-| Build the whole image from source | [development.md](development.md) |
-| Flash an SD card, or recover a board that will not boot | [factory-firmware.md](factory-firmware.md) |
-
-## 15. Documentation map
-
-| File | Contents |
-|---|---|
-| [pinouts-and-buses.md](pinouts-and-buses.md) | Every pin, bus, address and its source |
-| [resources-and-conflicts.md](resources-and-conflicts.md) | Shared lines, arbitration, what cannot coexist |
-| [development.md](development.md) | Toolchain, build, deploy, all four toolchains |
-| [factory-firmware.md](factory-firmware.md) | Images, flashing, **recovery and bricking** |
-| [compatibility-and-status.md](compatibility-and-status.md) | Working / partial / failing / untested |
-| [coverage.md](coverage.md) | Feature → evidence → guide map |
-| [gaps-and-conflicts.md](gaps-and-conflicts.md) | `GC-1`…`GC-9`, unresolved |
-| [performance.md](performance.md) | What is claimed, what is measured (little) |
-| [market-and-pricing.md](market-and-pricing.md) | Dated price observations |
-| [product-history-and-family.md](product-history-and-family.md) | Timeline, family, lineage |
-| [projects-and-community.md](projects-and-community.md) | Every firmware/project, with licence and status |
-| [community.md](community.md) | Threads, posts, anecdotes, evidence labels |
-| [comparisons-and-recommendations.md](comparisons-and-recommendations.md) | Competitors and tiers |
-| [sources.md](sources.md) | Full source table |
-| [research-log.md](research-log.md) | Every query, every dead end |
-| [commands.md](commands.md) | Command ledger with execution status |
-| [media.md](media.md) · [media/manifest.json](media/manifest.json) | Images and provenance |
-| [examples/](examples/) | Catalogue, search log, selection |
-| [acquisition/](acquisition/) | Manifest and clean-clone instructions |
-
-## 16. Artifact layout
-
-```
-devices/lilygo/t-display-k230/
-├── artifacts/
-│   ├── datasheets/          (empty — chip documents live under components/, by design)
-│   ├── source-snapshots/    BSP pin map, defconfig, patch list, keyboard matrix extract
-│   ├── firmware/            nRF52840 firmware/bootloader provenance (files upstream)
-│   ├── schematic/           EMPTY — LilyGO publishes no schematic (see gaps GC-5)
-│   └── originals/
-├── media/                   product and wiki images + manifest.json
-└── examples/
-```
-
-**Chip documents are filed under the component, not here.** The K230 datasheet lives at
-[`components/canaan/k230/artifacts/`](../../../components/canaan/k230/artifacts/), reached from
-here through the [key-specification table](#4-key-specifications).
-
-## 17. Known conflicts and unresolved identities
-
-Nine open items, tracked in [`gaps-and-conflicts.md`](gaps-and-conflicts.md). The three that
-matter most:
-
-- **`GC-2`** — LilyGO's wiki claims an **ESP32-S3-R8 co-processor** for Wi-Fi/BT. The BSP
-  contains **zero** Espressif references; Wi-Fi is RTL8189FS over SDIO and BT is a USB dongle.
-- **`GC-3`** — Ethernet is variously **RTL8152B** (wiki) and **"RC01812"** (shop). The K230 has
-  no Ethernet MAC, and the BSP kernel fragment does not enable `USB_RTL8152`.
-- **`GC-1`** — LilyGO's wiki inverts the K230's core roles relative to Canaan's datasheet.
-
----
-
-*Compiled 2026-09-04. Reproducible broad-coverage snapshot, not a claim of completeness — see
-[`research-log.md`](research-log.md) for searched sources, depth and exclusions.*
diff --git a/devices/lilygo/t-display-k230/acquisition/README.md b/devices/lilygo/t-display-k230/acquisition/README.md
deleted file mode 100644
index 01518c9..0000000
--- a/devices/lilygo/t-display-k230/acquisition/README.md
+++ /dev/null
@@ -1,130 +0,0 @@
-# T-Display K230 — acquisition
-
-Clean-clone reproduction, in execution order. Every step states its expected result and its
-failure mode. Machine-readable form: [`manifest.json`](manifest.json).
-
-## 0. Prerequisites
-
-```sh
-# GitHub token: api.github.com limits per identity, so no User-Agent helps.
-gh auth status
-export GH_TOKEN="$(gh auth token)"    # or use `gh api` directly
-```
-
-`curl`, `git`, `python3`, `sha256sum`, `file`.
-
-## 1. Chip documentation — **filed under the component, not here**
-
-The K230 datasheets belong to `components/canaan/k230/artifacts/` because they describe the
-**chip**, not this board. They are already retained there; this section exists so a reader
-starting from the board record can reach them.
-
-```sh
-cd components/canaan/k230/artifacts
-SHA=f8e30213963e0ed5cf995c3cd4701218a45e4793
-for p in en/00_hardware/K230_datasheet.md en/K230_brief_datasheet.md \
-         en/00_hardware/K230_Hardware_Design_Guide.md \
-         en/01_software/board/osdrv/K230_PMU_User_Guide.md \
-         en/01_software/board/ai/K230_nncase_Development_Guide.md \
-         en/02_applications/tutorials/K230_RVV_In_Action.md \
-         en/02_applications/tutorials/K230_RVV_optimization_performance_description.md; do
-  curl -sSLo "$(basename "$p")" "https://raw.githubusercontent.com/kendryte/k230_docs/$SHA/$p"
-done
-sha256sum -c SHA256SUMS      # expect: all OK
-```
-
-Reacquisition: **automatic**. Fallback host:
-`https://www.kendryte.com/k230/en/main/00_hardware/K230_datasheet.html`.
-
-The Canaan reference-board EDA set is **enumerated but not retrieved** —
-[`CANAAN-EDA-SET.md`](../../../../components/canaan/k230/artifacts/CANAAN-EDA-SET.md) carries
-every path, exact byte size and two reacquisition URLs.
-
-## 2. Board software — pinned commits
-
-```sh
-git clone https://github.com/Xinyuan-LilyGO/T-Display-K230.git
-git -C T-Display-K230 checkout bb831ab358b66f5bd9a87ecd7c580fee4537492e
-# with the SDK submodule (adds ~100 MB):
-git -C T-Display-K230 submodule update --init --recursive
-
-git clone https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840.git
-git -C T-Display-K230-nRF52840 checkout 4646a728580739d487126f47a521e9b8032b3c2c
-
-git clone https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151.git
-git -C T-Display-K230-nRF9151 checkout ed4ecbe34162dec9b81213a400198125bbd6e36f
-```
-
-**Not vendored into this repository.** Reasons: ~192 MB combined, **no licence file on any of
-them**, and they are reproducible from pinned commits. Facts extracted from them are in
-[`pinouts-and-buses.md`](../pinouts-and-buses.md), [`development.md`](../development.md) and the
-component records, so no future work depends on re-reading the trees.
-
-Disposition `reference-only`; redistribution status `unknown`; reacquisition `automatic`.
-
-## 3. Companion-MCU prebuilt firmware
-
-```sh
-B=https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c
-curl -sSLO "$B/firmware/k230_nrf52840_at_20260816_r4_k230_uart_dfu.uf2"    # 296 960 B
-curl -sSLO "$B/bootloader/k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex"  # 525 680 B
-file *.uf2 *.hex     # validate from content, never from the extension
-```
-
-**Not retained here** — no licence, and byte sizes are recorded so identity can be confirmed on
-reacquisition. **SHA-256 is unknown**: the files were enumerated from the Git tree API, not
-downloaded. Recorded as unknown rather than omitted.
-
-## 4. Images
-
-Retained in [`../media/`](../media/) with SHA-256 and byte size for all 14 in
-[`../media/manifest.json`](../media/manifest.json). Held **unstaged** — no licence statement
-exists on either lilygo.cc or wiki.lilygo.cc.
-
-**Enumerated but not fetched:** the six Cased Version wiki images, base URL
-`https://wiki.lilygo.cc/products/t-display-series/t-display-k230/cased-version/image/<name>.jpg`,
-names `t-display-k230-cased-{angle,front-back,dimensions,features,details,pinmap}.jpg`. And the
-repository images, notably **`image/pins_annotated.png` (699 111 B)** in the nRF52840 repository —
-an annotated pin photograph of the base board, and the most useful un-fetched image known.
-
-## 5. Verification
-
-```sh
-sha256sum -c components/canaan/k230/artifacts/SHA256SUMS      # expect: 7x OK
-
-# Verify every retained image against its manifest, and check JPEG magic bytes.
-# (`file` is absent on some hosts; check the magic directly.)
-python3 tools/verify_media_manifest.py devices/lilygo/t-display-k230/media/manifest.json
-```
-
-If that helper does not exist in your checkout, the equivalent inline check is: for each record
-in `media/manifest.json`, recompute `sha256` over the file at `devices/lilygo/t-display-k230/` +
-its `file` field, compare against the recorded value, and confirm the first three bytes are
-`FF D8 FF`. All 14 records were verified this way on 2026-09-04 and all matched.
-
-## 6. Reacquisition status summary
-
-| Class | Status |
-|---|---|
-| Canaan documentation | **automatic** — pinned commit + a second host |
-| Canaan EDA set | **automatic** — enumerated, two URLs each |
-| LilyGO repositories | **automatic** — pinned commits |
-| Companion firmware binaries | **automatic** — pinned raw URLs; **SHA-256 unknown** (enumerated from the tree API, not downloaded) |
-| Product/wiki images | **automatic**, retained |
-| Cased Version images | **automatic**, enumerated but not fetched |
-| `image/pins_annotated.png` | **automatic**, not fetched |
-| **A LilyGO schematic** | **lost** — never published ([`GC-5`](../gaps-and-conflicts.md)) |
-| **`K230_PINOUT_V1.0_20230524`** | **lost** — cited by Canaan’s datasheet, absent from the repository |
-| **A factory system image** | **does not exist** — LilyGO publishes none |
-
-## 7. Licence and decisions report
-
-| Group | Items | Recommendation |
-|---|---|---|
-| **Known permissive** | `kendryte/k230_linux_sdk`, `k230_sdk`, `k230_docs` repositories — BSD-2-Clause | Safe to reference and to build from |
-| **Conflicting / strict** | The Canaan **documents**, which carry “shall not disseminate … in any form” inside a BSD-2-Clause repository | 7 files retained **unstaged**. User decision needed: stage, move to local cache, or keep metadata only. |
-| **Unknown terms** | **Every LilyGO repository** (no LICENSE file), the prebuilt nRF52840 firmware and bootloader, and all 14 product/wiki images | Repositories and firmware kept `reference-only`; images retained **unstaged**. User decision needed on the images. |
-| **Large paths** | LilyGO BSP ~110 MB (+ ~100 MB SDK submodule); `T-Display-K230_canmv_rt` **745 MB**; Canaan EDA set ~19 MB | All `reference-only`. None downloaded into the repository. |
-| **Opaque binaries** | `k230_nrf52840_at_*.uf2`, `k230_nrf52840_bootloader_*.hex` | Not downloaded. Byte sizes recorded; SHA-256 unknown and recorded as unknown. |
-
-**Nothing has been staged or committed by this session.**
diff --git a/devices/lilygo/t-display-k230/acquisition/manifest.json b/devices/lilygo/t-display-k230/acquisition/manifest.json
deleted file mode 100644
index 500d4f3..0000000
--- a/devices/lilygo/t-display-k230/acquisition/manifest.json
+++ /dev/null
@@ -1,333 +0,0 @@
-{
-  "schema": "hardware-doc/acquisition-manifest/1",
-  "device": "lilygo/t-display-k230",
-  "compiled": "2026-09-04",
-  "summary": {
-    "records": 19,
-    "downloaded_and_retained": 7,
-    "retained_note": "All 7 retained files are CHIP documents filed under components/canaan/k230/artifacts/, not under this device. 14 images are additionally retained under devices/lilygo/t-display-k230/media/ with their own manifest.",
-    "reference_only": 12,
-    "lost": 3,
-    "licence_note": "Every LilyGO repository for this product lacks a licence file; the Canaan repository is BSD-2-Clause but the documents inside it carry a conflicting restrictive notice. Nothing has been staged."
-  },
-  "artifacts": [
-    {
-      "id": "canaan-k230-datasheet",
-      "kind": "datasheet",
-      "url": "https://raw.githubusercontent.com/kendryte/k230_docs/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/00_hardware/K230_datasheet.md",
-      "sha256": "f0bd20a600be373b8b5ca605d65215651ccb29e7d2c09cfdf26a74bec8ebc556",
-      "bytes": 83002,
-      "destination": "components/canaan/k230/artifacts/K230_datasheet-v1.0-2023-07-06.md",
-      "retrieved": "2026-09-04",
-      "upstream_version": "V1.0",
-      "upstream_date": "2023-07-06",
-      "repo": "https://github.com/kendryte/k230_docs",
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "CONFLICT: repository BSD-2-Clause vs document 'shall not disseminate ... in any form'",
-      "license_evidence": "repo metadata; document Trademark Notice section",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "target_hardware": "Kendryte K230 SoC",
-      "fallback_urls": [
-        "https://www.kendryte.com/k230/en/main/00_hardware/K230_datasheet.html"
-      ],
-      "reacquisition": "automatic",
-      "notes": "Chip document: filed under the COMPONENT, not the device, per the filing rule."
-    },
-    {
-      "id": "canaan-k230-brief-datasheet",
-      "kind": "datasheet",
-      "url": "https://raw.githubusercontent.com/kendryte/k230_docs/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/K230_brief_datasheet.md",
-      "sha256": "5cb684cf593698defe9b2d0044ec54fbcd2e0045efe6afd3961fe2157edd30ed",
-      "bytes": 7781,
-      "destination": "components/canaan/k230/artifacts/K230_brief_datasheet.md",
-      "retrieved": "2026-09-04",
-      "upstream_version": null,
-      "upstream_date": "repo commit 2025-09-12",
-      "repo": "https://github.com/kendryte/k230_docs",
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "see canaan-k230-datasheet",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "reacquisition": "automatic",
-      "notes": "NOT under 00_hardware/ - it sits at the en/ tree root. Easy to miss. Source of the CPU0/CPU1 role statement and the package dimensions."
-    },
-    {
-      "id": "canaan-k230-hdg",
-      "kind": "design-guide",
-      "url": "https://raw.githubusercontent.com/kendryte/k230_docs/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/00_hardware/K230_Hardware_Design_Guide.md",
-      "sha256": "19e7243c50197a4835b9f85ca51c3fc9abd52ca9d353c6a92ddc8eaf9a3384f4",
-      "bytes": 49061,
-      "destination": "components/canaan/k230/artifacts/K230_Hardware_Design_Guide.md",
-      "retrieved": "2026-09-04",
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "see canaan-k230-datasheet",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "canaan-k230-pmu",
-      "kind": "manual",
-      "url": "https://raw.githubusercontent.com/kendryte/k230_docs/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/01_software/board/osdrv/K230_PMU_User_Guide.md",
-      "sha256": "91a057dbc885f9761392f57c67c6e06bbf2a53cd96de558b8de3b58a5e9829d1",
-      "bytes": 10039,
-      "destination": "components/canaan/k230/artifacts/K230_PMU_User_Guide.md",
-      "retrieved": "2026-09-04",
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "see canaan-k230-datasheet",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "canaan-k230-nncase",
-      "kind": "manual",
-      "url": "https://raw.githubusercontent.com/kendryte/k230_docs/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/01_software/board/ai/K230_nncase_Development_Guide.md",
-      "sha256": "c2b297c9a615e0b67e9bd2c443d7c218a9d3ec4feab33a129e3e8f6ce4132ee5",
-      "bytes": 81128,
-      "destination": "components/canaan/k230/artifacts/K230_nncase_Development_Guide.md",
-      "retrieved": "2026-09-04",
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "see canaan-k230-datasheet",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "canaan-k230-rvv-1",
-      "kind": "tutorial",
-      "url": "https://raw.githubusercontent.com/kendryte/k230_docs/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/02_applications/tutorials/K230_RVV_In_Action.md",
-      "sha256": "6dc416406711b5490b2dcc927f77997aaa861436a345801116c9f552789a186a",
-      "bytes": 12528,
-      "destination": "components/canaan/k230/artifacts/K230_RVV_In_Action.md",
-      "retrieved": "2026-09-04",
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "see canaan-k230-datasheet",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "canaan-k230-rvv-2",
-      "kind": "tutorial",
-      "url": "https://raw.githubusercontent.com/kendryte/k230_docs/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/02_applications/tutorials/K230_RVV_optimization_performance_description.md",
-      "sha256": "77a7facbfab8cff717f3305635cb1f9f0965dab90431fc98aeb60119152c4cb0",
-      "bytes": 12004,
-      "destination": "components/canaan/k230/artifacts/K230_RVV_optimization_performance_description.md",
-      "retrieved": "2026-09-04",
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "see canaan-k230-datasheet",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "lilygo-bsp",
-      "kind": "source-repository",
-      "url": "https://github.com/Xinyuan-LilyGO/T-Display-K230",
-      "sha256": null,
-      "bytes": 113552384,
-      "destination": null,
-      "retrieved": "2026-09-04",
-      "commit": "bb831ab358b66f5bd9a87ecd7c580fee4537492e",
-      "release_tag": "v0.2.4 (changelog only)",
-      "license": "NONE DECLARED",
-      "license_evidence": "no LICENSE file at the pinned commit",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "target_hardware": "T-Display K230 / Kit",
-      "reacquisition": "automatic",
-      "notes": "~110 MB before the SDK submodule. Extracted facts live in pinouts-and-buses.md, development.md and the component records; no future work requires re-reading the tree."
-    },
-    {
-      "id": "lilygo-nrf52840",
-      "kind": "source-repository",
-      "url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840",
-      "sha256": null,
-      "bytes": 5306368,
-      "retrieved": "2026-09-04",
-      "commit": "4646a728580739d487126f47a521e9b8032b3c2c",
-      "license": "NONE DECLARED",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "lilygo-nrf9151",
-      "kind": "source-repository",
-      "url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151",
-      "sha256": null,
-      "bytes": 4591616,
-      "retrieved": "2026-09-04",
-      "commit": "ed4ecbe34162dec9b81213a400198125bbd6e36f",
-      "license": "NONE DECLARED",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "notes": "Vendors Nordic Serial LTE Modem as a pinned submodule at 13c80da97fe4d55ecb5a9745834d97be22821307 with five retained patches."
-    },
-    {
-      "id": "lilygo-canmv-rt",
-      "kind": "source-repository",
-      "url": "https://github.com/Xinyuan-LilyGO/T-Display-K230_canmv_rt",
-      "sha256": null,
-      "bytes": 763256832,
-      "retrieved": null,
-      "commit": null,
-      "branch": "main",
-      "license": "NONE DECLARED",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "omission_reason": "745 MB, not examined. 25 stars vs the main BSP's 1; created 2025-03-05, last push 2026-08-03. THE LARGEST UNEXPLORED ARTIFACT for this board."
-    },
-    {
-      "id": "nrf52840-firmware-uf2",
-      "kind": "firmware",
-      "url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c/firmware/k230_nrf52840_at_20260816_r4_k230_uart_dfu.uf2",
-      "sha256": null,
-      "sha256_reason": "enumerated from the Git tree API; not downloaded",
-      "bytes": 296960,
-      "retrieved": null,
-      "upstream_version": "r4",
-      "upstream_date": "2026-08-16",
-      "commit": "4646a728580739d487126f47a521e9b8032b3c2c",
-      "target_mcu": "Nordic nRF52840",
-      "compatible_hw": "T-Display K230 nRF52840 base board",
-      "image_role": "application (UF2)",
-      "uf2_family_id": "0xADA52840",
-      "flash_offset": "handled by the UF2 bootloader",
-      "companion_images": [
-        "nrf52840-bootloader-hex"
-      ],
-      "license": "NONE DECLARED",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "flash_instructions_authoritative": "LilyGO: double-tap RST to GND (or touch the USB-C shell) to enter DFU, then drag the .uf2 onto the enumerated drive."
-    },
-    {
-      "id": "nrf52840-bootloader-hex",
-      "kind": "firmware",
-      "url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c/bootloader/k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex",
-      "sha256": null,
-      "sha256_reason": "enumerated from the Git tree API; not downloaded",
-      "bytes": 525680,
-      "retrieved": null,
-      "commit": "4646a728580739d487126f47a521e9b8032b3c2c",
-      "target_mcu": "Nordic nRF52840",
-      "image_role": "bootloader + SoftDevice",
-      "sdk_version": "SoftDevice S140 6.1.1",
-      "dfu": "UART @ 115200",
-      "license": "NONE DECLARED",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "canaan-eda-set",
-      "kind": "eda-and-pdf-set",
-      "url": "https://github.com/kendryte/k230_docs/tree/f8e30213963e0ed5cf995c3cd4701218a45e4793/zh/00_hardware",
-      "sha256": null,
-      "bytes": 19000000,
-      "bytes_note": "approximate sum of 22 enumerated files; exact per-file sizes are in CANAAN-EDA-SET.md",
-      "retrieved": null,
-      "commit": "f8e30213963e0ed5cf995c3cd4701218a45e4793",
-      "license": "see canaan-k230-datasheet",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "notes": "Canaan REFERENCE-BOARD design data (LP3, LP4, K230D SiP EVB). Only in the zh/ tree; the en/ tree has no binary hardware artifacts. Does not describe the LilyGO board."
-    },
-    {
-      "id": "wiki-cased-version-images",
-      "kind": "images",
-      "url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/cased-version/image/",
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "members": [
-        "t-display-k230-cased-angle.jpg",
-        "t-display-k230-cased-front-back.jpg",
-        "t-display-k230-cased-dimensions.jpg",
-        "t-display-k230-cased-features.jpg",
-        "t-display-k230-cased-details.jpg",
-        "t-display-k230-cased-pinmap.jpg"
-      ],
-      "notes": "Enumerated from the Cased Version wiki page HTML; not fetched."
-    },
-    {
-      "id": "nrf52840-pins-annotated",
-      "kind": "image",
-      "url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c/image/pins_annotated.png",
-      "sha256": null,
-      "bytes": 699111,
-      "retrieved": null,
-      "commit": "4646a728580739d487126f47a521e9b8032b3c2c",
-      "license": "NONE DECLARED",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "notes": "Annotated pin photograph of the nRF52840 base board. The most useful un-fetched image identified in this pass."
-    },
-    {
-      "id": "lilygo-schematic",
-      "kind": "schematic",
-      "url": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "license": null,
-      "redistribution_status": null,
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "lost",
-      "omission_reason": "DOES NOT EXIST PUBLICLY. The LilyGO wiki has a '#schematic' heading with no content beneath it (verified 2026-09-04). Tracked as GC-5."
-    },
-    {
-      "id": "canaan-k230-pinout",
-      "kind": "pinout",
-      "url": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "lost",
-      "omission_reason": "Document 'K230_PINOUT_V1.0_20230524' is cited by the K230 datasheet but is NOT present anywhere in kendryte/k230_docs, in either language tree. Verified by full recursive listing at f8e3021."
-    },
-    {
-      "id": "lilygo-factory-image",
-      "kind": "firmware",
-      "url": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "lost",
-      "omission_reason": "LilyGO publishes NO prebuilt system image. Their README states images under k230_bsp/images/ are local build artifacts. Canaan's developer portal has generic K230 images which do not drive this board's peripherals."
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/lilygo/t-display-k230/artifacts/README.md b/devices/lilygo/t-display-k230/artifacts/README.md
deleted file mode 100644
index fa47a23..0000000
--- a/devices/lilygo/t-display-k230/artifacts/README.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# T-Display K230 — artifact layout
-
-## What is here
-
-| Directory | Contents |
-|---|---|
-| `source-snapshots/` | Facts extracted from LilyGO's BSP at a pinned commit, so no future work depends on re-cloning ~192 MB of unlicensed repositories |
-| `datasheets/` | **Deliberately empty.** Chip documents describe a *component*, not this board, and are filed at [`components/canaan/k230/artifacts/`](../../../../components/canaan/k230/artifacts/) |
-| `schematic/` | **Empty, and this is a finding.** LilyGO publishes no schematic for this board — the wiki's `#schematic` heading has no content beneath it. Tracked as [`GC-5`](../gaps-and-conflicts.md) |
-| `firmware/` | **Empty.** LilyGO ships **no** factory system image; the only prebuilt binaries are the nRF52840 UF2 and bootloader, which live in a companion repository and are recorded in [`acquisition/manifest.json`](../acquisition/manifest.json) |
-| `originals/` | Empty |
-
-## Why so little is vendored
-
-Three independent reasons, all recorded rather than assumed:
-
-1. **Licence.** Not one of the four LilyGO repositories for this product carries a `LICENSE`
-   file. Redistribution status is `unknown` for their source *and* for the prebuilt firmware.
-2. **Size.** The BSP is ~110 MB before its ~100 MB SDK submodule; `T-Display-K230_canmv_rt` is
-   745 MB.
-3. **Reproducibility.** Everything is available at a pinned commit and reacquisition is
-   `automatic` for every item that exists at all.
-
-The three items whose reacquisition is **`lost`** — the schematic, `K230_PINOUT_V1.0_20230524`,
-and a factory image — are lost because **they were never published**, not because they were
-missed.
-
-## Where the chip documents actually are
-
-[`components/canaan/k230/artifacts/`](../../../../components/canaan/k230/artifacts/) — seven
-Markdown documents with a `SHA256SUMS` file, plus
-[`CANAAN-EDA-SET.md`](../../../../components/canaan/k230/artifacts/CANAAN-EDA-SET.md), which
-enumerates 22 Canaan reference-board EDA files with exact byte sizes and two reacquisition URLs
-each.
diff --git a/devices/lilygo/t-display-k230/artifacts/datasheets/CHIP-DOCS-ARE-FILED-UNDER-COMPONENTS.md b/devices/lilygo/t-display-k230/artifacts/datasheets/CHIP-DOCS-ARE-FILED-UNDER-COMPONENTS.md
deleted file mode 100644
index 3ccacf4..0000000
--- a/devices/lilygo/t-display-k230/artifacts/datasheets/CHIP-DOCS-ARE-FILED-UNDER-COMPONENTS.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Chip documents are not here — and that is deliberate
-
-A document is filed by **what it describes**, not by what was being researched when it was
-fetched. The Kendryte K230 datasheet describes a **chip**, so it is a *component* artifact even
-though a board task fetched it.
-
-All K230 documentation retrieved during this device's research lives at:
-
-**[`components/canaan/k230/artifacts/`](../../../../../components/canaan/k230/artifacts/)**
-
-| File | Bytes | Establishes |
-|---|---:|---|
-| `K230_datasheet-v1.0-2023-07-06.md` | 83 002 | Full feature list, KPU operators, packages, electrical sections, PMU, security |
-| `K230_brief_datasheet.md` | 7 781 | **CPU0/CPU1 roles and frequencies**, package dimensions, SiP memory, peripheral counts |
-| `K230_Hardware_Design_Guide.md` | 49 061 | Board-design rules |
-| `K230_PMU_User_Guide.md` | 10 039 | PMU registers, power key, shutdown |
-| `K230_nncase_Development_Guide.md` | 81 128 | KPU model compilation |
-| `K230_RVV_In_Action.md` | 12 528 | Practical RVV on CPU1 |
-| `K230_RVV_optimization_performance_description.md` | 12 004 | Vector speed-up figures |
-| `SHA256SUMS` | 677 | Verification |
-| `CANAAN-EDA-SET.md` | — | 22 Canaan reference-board EDA files, enumerated with exact sizes and two reacquisition URLs each |
-
-All seven documents were retrieved 2026-09-04 from `kendryte/k230_docs` at commit
-**`f8e30213963e0ed5cf995c3cd4701218a45e4793`**.
-
-Component datasheets for the other fitted parts follow the same rule and are under their own
-manufacturers: [`raydium/rm69a10`](../../../../../components/raydium/rm69a10/README.md),
-[`goodix/gt9895`](../../../../../components/goodix/gt9895/README.md),
-[`galaxycore/gc2093`](../../../../../components/galaxycore/gc2093/README.md),
-[`realtek/rtl8189fs`](../../../../../components/realtek/rtl8189fs/README.md),
-[`realtek/rtl8152b`](../../../../../components/realtek/rtl8152b/README.md),
-[`semtech/sx1262`](../../../../../components/semtech/sx1262/README.md),
-[`semtech/lr2021`](../../../../../components/semtech/lr2021/README.md),
-[`nordic-semiconductor/nrf52840`](../../../../../components/nordic-semiconductor/nrf52840/README.md),
-[`nordic-semiconductor/nrf9151`](../../../../../components/nordic-semiconductor/nrf9151/README.md),
-[`texas-instruments/tca8418`](../../../../../components/texas-instruments/tca8418/README.md),
-[`texas-instruments/bq25896`](../../../../../components/texas-instruments/bq25896/README.md),
-[`texas-instruments/bq27220`](../../../../../components/texas-instruments/bq27220/README.md),
-[`xlsemi/xl9555`](../../../../../components/xlsemi/xl9555/README.md),
-[`analog-devices/max98357a`](../../../../../components/analog-devices/max98357a/README.md),
-[`asair/aht20`](../../../../../components/asair/aht20/README.md),
-[`lontium/lt9611`](../../../../../components/lontium/lt9611/README.md).
diff --git a/devices/lilygo/t-display-k230/artifacts/firmware/NO-FACTORY-IMAGE.md b/devices/lilygo/t-display-k230/artifacts/firmware/NO-FACTORY-IMAGE.md
deleted file mode 100644
index f3d9068..0000000
--- a/devices/lilygo/t-display-k230/artifacts/firmware/NO-FACTORY-IMAGE.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# There is no factory firmware image for this board
-
-**Verified 2026-09-04.** Negative result.
-
-LilyGO publishes **no prebuilt system image** for the T-Display K230. Their own README says:
-
-> "Generated image files under `k230_bsp/images/` are local build artifacts."
-
-To get a running system you must **build `sysimage-sdcard.img` yourself** — see
-[`../../development.md`](../../development.md) — which needs Ubuntu 22.04/24.04 (or Docker, or
-WSL2) and the XuanTie toolchain at `/opt/toolchain`.
-
-Canaan publishes generic K230 images at `developer.canaan-creative.com` → *K230* → *Images*.
-Those boot a K230, but they drive **none** of this board's peripherals: the AMOLED, touch,
-keyboard, camera, Wi-Fi and radio support are all in LilyGO's overlay.
-
-## Why this matters more than usual
-
-A user who bricks a board cannot download a known-good image and start again. Combined with the
-absence of any documented recovery procedure ([`../../factory-firmware.md` §5](../../factory-firmware.md)),
-this is the single largest practical risk of owning the product — and it is exactly what one
-owner ran into on 2026-08-21.
-
-## The only prebuilt binaries LilyGO does publish
-
-Both are for the **nRF52840 companion**, in a different repository, and both have **no licence**:
-
-| File | Bytes | Role |
-|---|---:|---|
-| `firmware/k230_nrf52840_at_20260816_r4_k230_uart_dfu.uf2` | 296 960 | AT/BLE-Central application, build **2026-08-16**, revision **r4**, UF2 family `0xADA52840` |
-| `bootloader/k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex` | 525 680 | Bootloader with UART DFU @ 115200 and **SoftDevice S140 6.1.1** |
-
-Reacquisition (**automatic**), from the pinned commit:
-
-```
-https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c/firmware/k230_nrf52840_at_20260816_r4_k230_uart_dfu.uf2
-https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c/bootloader/k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex
-```
-
-Second, mutable URL for each: replace the commit SHA with `master`.
-
-**SHA-256 for both is unknown** — they were enumerated from the Git tree API rather than
-downloaded. Recorded as unknown rather than omitted. Byte sizes above are exact and are enough to
-confirm identity on reacquisition.
-
-Full records: [`../../acquisition/manifest.json`](../../acquisition/manifest.json),
-entries `nrf52840-firmware-uf2` and `nrf52840-bootloader-hex`.
diff --git a/devices/lilygo/t-display-k230/artifacts/schematic/NOT-PUBLISHED.md b/devices/lilygo/t-display-k230/artifacts/schematic/NOT-PUBLISHED.md
deleted file mode 100644
index 58300fd..0000000
--- a/devices/lilygo/t-display-k230/artifacts/schematic/NOT-PUBLISHED.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# No schematic exists for this board
-
-**Verified 2026-09-04.** This is a negative result, recorded so it is not re-investigated.
-
-LilyGO's wiki page for the T-Display K230 contains a heading `## Schematic` with **no link, no
-file and no content beneath it**. The same is true of `## Dimension Diagram` on the bare-board
-page. This is a *soft* gap: there is no 404, no broken link, and nothing for a link checker to
-catch — the section is simply empty.
-
-Checked and empty:
-
-- `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/` — `#schematic` heading, no content
-- `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/cased-version.html` — no schematic
-- `https://github.com/Xinyuan-LilyGO/T-Display-K230` @ `bb831ab358b66f5bd9a87ecd7c580fee4537492e` — no schematic, no EDA files
-- `https://lilygo.cc/products/t-display-k230` and `/t-display-k230-kit` — product descriptions only
-
-**For comparison**, LilyGO *does* publish a schematic for older products in the same series — the
-T-Display wiki page links "T-Display V1.0 Schematic". So this is a per-product omission, not a
-vendor-wide policy, and it may appear later.
-
-## What this costs
-
-Every pin claim in [`../../pinouts-and-buses.md`](../../pinouts-and-buses.md) rests on a **single
-vendor document** (`HARDWARE_PINMAP.md`) with nothing to cross-check it against. And six parts
-remain unidentified because there is no netlist and no PCB photograph:
-[`components/unidentified/t-display-k230`](../../../../../components/unidentified/t-display-k230/README.md).
-
-## Nearest available substitutes
-
-Canaan publishes complete EDA sources for its **own** K230 reference boards — schematic PDFs,
-OrCAD `.DSN`, Gerbers, PCB, DXF, SMT and BOM — under the **Chinese** tree of `kendryte/k230_docs`.
-The LilyGO board is an LPDDR4, non-SiP design, so `K230_LP4` (the USIP EVB) is the closest
-reference. Full inventory with exact sizes and two reacquisition URLs each:
-[`components/canaan/k230/artifacts/CANAAN-EDA-SET.md`](../../../../../components/canaan/k230/artifacts/CANAAN-EDA-SET.md).
-
-Tracked as [`GC-5`](../../gaps-and-conflicts.md). Reacquisition status: **lost** — because the
-document was never created, not because it was missed.
diff --git a/devices/lilygo/t-display-k230/artifacts/source-snapshots/README.md b/devices/lilygo/t-display-k230/artifacts/source-snapshots/README.md
deleted file mode 100644
index f5455ac..0000000
--- a/devices/lilygo/t-display-k230/artifacts/source-snapshots/README.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# Extracted facts — LilyGO T-Display K230 BSP
-
-Source: `Xinyuan-LilyGO/T-Display-K230` @ **`bb831ab358b66f5bd9a87ecd7c580fee4537492e`**
-(`main`, 2026-09-03, changelog v0.2.4). Extracted **2026-09-04**.
-
-This file exists so that nothing in this repository depends on re-cloning an unlicensed 110 MB
-tree. Where a fact is long, it is written up in full in the authored documents and only pointed
-at from here.
-
-## Pinned revisions
-
-| Thing | Pin |
-|---|---|
-| BSP commit | `bb831ab358b66f5bd9a87ecd7c580fee4537492e` |
-| Upstream SDK | `kendryte/k230_linux_sdk` @ `22d02c6b6783a57a3aca7eb3160e313e772cb710` (branch `dev`) — recorded in `k230_bsp/metadata/upstream_sdk_commit.txt` |
-| Kernel | `ruyisdk/linux-xuantie-kernel` @ `7d4e1f444f461dbe3833bd99a4640e7b6c2cd529`, defconfig `k230` |
-| Toolchain | `/opt/toolchain/Xuantie-900-gcc-linux-6.6.0-glibc-x86_64-V3.0.2/`, prefix `riscv64-unknown-linux-gnu` |
-| Target flags | `-mcpu=c908v -mtune=c908 -mrvv-v0p10-compatible -mrvv-auto-vectorize` |
-| LVGL | upstream `59dc7e436ae97a25e32656739ea6a943f9f11b6a` + 4 LilyGO patches |
-| Device trees built | `canaan/k230-canmv-rm69a10`, `canaan/k230-canmv-v3`, `canaan/k230-canmv-rm69a10-hdmi` |
-| nRF52840 repo | `4646a728580739d487126f47a521e9b8032b3c2c` |
-| nRF9151 repo | `ed4ecbe34162dec9b81213a400198125bbd6e36f`; upstream SLM submodule `13c80da97fe4d55ecb5a9745834d97be22821307`; NCS **v3.4.0** |
-
-## Extracted content, and where it now lives
-
-| Content | Written up in |
-|---|---|
-| Complete GPIO / bus / I²C-address map | [`pinouts-and-buses.md` §1–§7](../../pinouts-and-buses.md) |
-| **Full TCA8418 keyboard matrix**, key codes, labels, layout, repeat timing, hotkeys | [`pinouts-and-buses.md` §8](../../pinouts-and-buses.md#8-keyboard-matrix--full-decode) |
-| PMU power-key register flow and constants | [`pinouts-and-buses.md` §9](../../pinouts-and-buses.md#9-pmu-power-key-register-flow) |
-| IO bank voltage table and the damage warning | [`pinouts-and-buses.md` §6](../../pinouts-and-buses.md#6-io-bank-voltages--the-hardware-damage-path) |
-| Build, flash and deploy procedure | [`development.md`](../../development.md) |
-| Kernel patch inventory (`0025`–`0064`) | [`development.md` §2.5](../../development.md) |
-| Buildroot package selections | [`development.md`](../../development.md), [`features/*`](../../features/) |
-| Companion-MCU wiring, AT sets, DFU | [`features/nrf52840-ble.md`](../../features/nrf52840-ble.md), [`features/nrf9151-cellular-gnss.md`](../../features/nrf9151-cellular-gnss.md) |
-| Part-number census | [`research-log.md` #19](../../research-log.md) |
-
-## Part-number census — the raw result
-
-Regex sweep over `*.c/cpp/h/md/MD/sh/patch/dts/mk/in/_defconfig` at the pinned commit, ranked:
-
-```
-579 lr2021      532 k230       203 nrf9151    168 nrf52840   151 sx1262
-124 rm69a10      72 tca8418     59 bq25896     57 bq27220     54 aht20
- 44 gc2093       42 xl9555      29 lt9611      25 max98357a   19 gt9895
- 16 rtl8723ds    13 sx1268       9 sx1261       6 rtl8189fs    5 k230d
-  4 csr8510       3 sx1231       3 rtl8733bs    2 tca8414      2 ov5647
-  2 aht10         1 sx1278       1 sx1272       1 rtl8723bs    1 imx219
-  1 cp2104        1 bq25890
-```
-
-**Zero hits for `esp32`, `esp32s3` or any Espressif identifier.** That negative result is the
-evidence behind [`GC-2`](../../gaps-and-conflicts.md).
-
-**Zero hits for any PMIC family** (`axp`, `sy`, `mp`, `tps`, `eta`, `sgm`, `rk8`, `hi65`), which
-is why the PMIC is [U1 in the unidentified record](../../../../../components/unidentified/t-display-k230/README.md).
-
-`lr2021` outranking `sx1262` almost four to one is itself informative: LilyGO's recent
-development effort is going into the newer radio.
-
-## Files worth re-reading if you do clone it
-
-| Path | Bytes | Why |
-|---|---:|---|
-| `k230_bsp/docs/HARDWARE_PINMAP.md` | 8 593 | The authoritative pin map |
-| `k230_launcher/k230_phone_ui/src/ui_hardware.c` | large | Keyboard matrix, TCA8418 registers, PMU constants, battery policy, XL9555 probe |
-| `k230_bsp/metadata/overlay_manifest.txt` | 5 764 | Exactly what the overlay changes, without diffing trees |
-| `.../linux/0034-gt9895-touch.patch` | 307 439 | The vendored Goodix Berlin driver |
-| `.../linux/0064-input-k230-pmu-pwrkey.patch` | 21 523 | The PMU power-key driver |
-| `.../linux/rejected/0044-*.rejected` | 829 | A retained failed patch — write-combine dumb buffers |
-| `.../package/vvcam/src/gc2093.c` | 26 213 | Camera sensor register writes, **undecoded** ([`GC-6`](../../gaps-and-conflicts.md)) |
-| `.../board/canaan/k230-soc/genimage.cfg` | 1 280 | Authoritative SD image partition layout |
diff --git a/devices/lilygo/t-display-k230/certification-and-compliance.md b/devices/lilygo/t-display-k230/certification-and-compliance.md
deleted file mode 100644
index be75666..0000000
--- a/devices/lilygo/t-display-k230/certification-and-compliance.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Certification and compliance — t-display-k230
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-⚠ **No FCC grant exists for the T-Display K230, under `2ASYE` or any other grantee.** This is a *controlled* absence — see §2 and §4. The board is on sale at USD 98.79.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-k230/commands.md b/devices/lilygo/t-display-k230/commands.md
deleted file mode 100644
index c8dd767..0000000
--- a/devices/lilygo/t-display-k230/commands.md
+++ /dev/null
@@ -1,171 +0,0 @@
-# T-Display K230 — command ledger
-
-Status vocabulary: `executed-success` · `executed-failed` · `reported-working` · `inferred` ·
-`not-tested`.
-
-**No command touching the target hardware was executed.** Everything under §2–§5 is
-`reported-working` (LilyGO or Canaan documents it and the supporting source exists) or `inferred`.
-§1 was executed on the research host and is labelled accordingly.
-
-Host for §1: Linux, `bash`, `curl 8.x`, `git 2.x`, `gh` (authenticated), `python3`.
-
----
-
-## 1. Research commands — `executed-success`
-
-```sh
-# Establish the marketed name and SKUs. Returns 3 products; one is the SKU collision.
-curl -sS "https://lilygo.cc/search?q=K230&type=product" -H "User-Agent: <browser UA>"
-
-# Full structured product record: variants, SKUs, cent prices, created_at/published_at, images
-curl -sS https://lilygo.cc/products/t-display-k230.js      | python3 -m json.tool
-curl -sS https://lilygo.cc/products/t-display-k230-kit.js  | python3 -m json.tool
-
-# Enumerate the whole LilyGO org (254 repos) and filter
-gh api "orgs/Xinyuan-LilyGO/repos?per_page=100&sort=pushed" --paginate
-
-# Repository identity: default branch matters — Canaan uses 'dev' and 'canmv_k230'
-gh api repos/kendryte/k230_linux_sdk -q '.default_branch'
-
-# 837-entry recursive listing of the Canaan doc repo. gh, not curl: this can exhaust the
-# 60/hour anonymous limit and the resulting 403 looks exactly like a bot block.
-gh api repos/kendryte/k230_docs/git/trees/main?recursive=1
-
-# Pin the doc commit for citations
-gh api repos/kendryte/k230_docs/commits/main -q '.sha+" "+.commit.committer.date'
-#   -> f8e30213963e0ed5cf995c3cd4701218a45e4793 2025-09-12T07:01:37Z
-
-# Fetch a Canaan document
-curl -sSL https://raw.githubusercontent.com/kendryte/k230_docs/main/en/00_hardware/K230_datasheet.md
-
-# Reddit. www.reddit.com returns 403; old.reddit.com + this UA returns 200.
-curl -sS -H "User-Agent: WhatsApp/2.23.20.0" \
-  "https://old.reddit.com/search.json?q=lilygo%20k230&sort=new&limit=25&t=all"
-curl -sS -H "User-Agent: WhatsApp/2.23.20.0" \
-  "https://old.reddit.com/r/LilyGO/comments/1vtcjuj.json?limit=100"
-
-# Clone the BSP (shallow) and pin the commit
-git clone --depth 1 https://github.com/Xinyuan-LilyGO/T-Display-K230.git
-git -C T-Display-K230 rev-parse HEAD    # bb831ab358b66f5bd9a87ecd7c580fee4537492e
-
-# The single most productive analysis command of the session: part-number census
-grep -rhoiE "\b(rtl[0-9]{4}[a-z]{0,3}|lt[0-9]{4}|max[0-9]{4,5}[a-z]?|tps[0-9]{4,5}|bq[0-9]{5}|gc[0-9]{4}|rm69[a-z0-9]+|gt9[0-9]{3}|xl[0-9]{4}|tca[0-9]{4}|aht[0-9]{2}|sx12[0-9]{2}|lr[0-9]{4}|nrf[0-9]{4,5}|k230[a-z]?|es8[0-9]{3}|axp[0-9]{4})\b" \
-  --include=*.c --include=*.cpp --include=*.h --include=*.md --include=*.MD \
-  --include=*.sh --include=*.patch --include=*.dts --include=*_defconfig . \
-  | tr 'A-Z' 'a-z' | sort | uniq -c | sort -rn
-
-# Negative result that settles the Ethernet question
-grep -ni "ethernet\|gmac\|rmii" K230_datasheet.md K230_brief_datasheet.md   # -> no output
-
-# Validate file type from content, never from the URL suffix
-file media/*.jpg && sha256sum media/*.jpg
-```
-
-## 2. Building the K230 image — `reported-working` (LilyGO)
-
-```sh
-sudo apt update && sudo apt install -y git ca-certificates build-essential make rsync python3
-git clone --recurse-submodules https://github.com/Xinyuan-LilyGO/T-Display-K230.git t-display-k230
-cd t-display-k230
-git submodule update --init --recursive     # if you forgot --recurse-submodules
-./scripts/setup_ubuntu.sh                   # installs XuanTie toolchain to /opt/toolchain
-./scripts/apply_to_sdk.sh
-./scripts/build_sdcard_image.sh
-# -> k230_bsp/images/sysimage-sdcard.img
-
-# clean rebuild
-rm -rf k230_linux_sdk/output && ./scripts/apply_to_sdk.sh && ./scripts/build_sdcard_image.sh
-```
-
-Prereqs: Ubuntu 22.04/24.04 (LilyGO) or 20.04/Docker (Canaan); WSL2 on Windows, **not** under
-`/mnt/c/`. Requires network — Buildroot downloads into `dl/` during the build.
-
-Canaan's Docker alternative — `reported-working` (LilyGO wiki):
-
-```sh
-docker pull ghcr.io/kendryte/k230_sdk
-git clone https://github.com/kendryte/k230_sdk && cd k230_sdk && make prepare_sourcecode
-docker run -u root -it -v $(pwd):$(pwd) -v $(pwd)/toolchain:/opt/toolchain -w $(pwd) \
-  ghcr.io/kendryte/k230_sdk /bin/bash
-make CONF=k230_evb_defconfig
-```
-
-⚠ `k230_evb_defconfig` is the **Canaan EVB** target, not this board. It will not drive the
-AMOLED, touch or keyboard.
-
-## 3. Flashing — `reported-working`
-
-```sh
-# Linux
-sudo dd if=k230_bsp/images/sysimage-sdcard.img of=/dev/sdX bs=8M status=progress conv=fsync && sync
-# macOS
-diskutil unmountDisk /dev/diskN
-sudo dd if=k230_bsp/images/sysimage-sdcard.img of=/dev/rdiskN bs=8m status=progress && sync
-# Windows: Rufus, "Write in DD Image mode". Cancel the "format unknown partition" prompt.
-```
-
-Canaan's variant, same effect: `sudo dd if=sysimage-sdcard.img of=/dev/sdx bs=1M oflag=sync`.
-
-## 4. Companion firmware — `reported-working`
-
-```sh
-# nRF52840
-python3 -m pip install --user platformio
-cd t-display-k230-nrf52840 && pio run
-python3 ./scripts/uf2conv.py .pio/build/nrf52840/firmware.hex -c -f 0xADA52840 \
-  -o .pio/build/nrf52840/k230_nrf52840_at.uf2
-# DFU: jumper RST to GND twice quickly (or touch the USB-C shell), then drag the .uf2
-
-# nRF9151
-nrfutil install sdk-manager
-nrfutil sdk-manager install --install-dir "$PWD/ncs" v3.4.0
-export NCS_ROOT=/path/to/ncs/v3.4.0        # only if installed elsewhere
-git clone --recurse-submodules https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151
-cd T-Display-K230-nRF9151 && ./build_serial_modem.sh
-find build/serial_modem_k230 -path '*/zephyr/tfm_merged.hex' -o -path '*/zephyr/zephyr.hex'
-```
-
-## 5. On-board diagnostics — `inferred` (tools are built into the image; not run here)
-
-```sh
-cat /proc/cpuinfo                       # settles GC-1: which core runs Linux
-free -h                                 # settles GC-7: 512 MB vs 1 GB
-readlink /sys/class/net/eth0/device/driver ; lsusb    # settles GC-3: the Ethernet controller
-zcat /proc/config.gz | grep -i rtl8152  # ditto
-dmesg | grep -iE 'rtl|blue|goodix|gc2093|k230'
-cat /proc/mtd                           # settles GC-9: the 16 MB flash
-i2cdetect -y 4                          # I2C4: expect 0x34 0x38 0x55 0x6B and one of 0x20-0x27
-i2cdetect -y <touch-bus>                # settles GC-4: a second address means LT9611 is fitted
-evtest                                  # keyboard and PMU power key
-gpioinfo                                # line ownership
-aplay -l ; amixer                       # settles the audio route question
-coremark                                # built in; nobody has ever published the result
-
-# Fast iteration once networked
-./scripts/deploy_launcher.sh 192.168.1.100
-./scripts/deploy_launcher.sh 192.168.1.100 --full --reboot
-```
-
-## 6. Recovery — `not-tested`
-
-No vendor procedure exists ([`factory-firmware.md` §5](factory-firmware.md)). The two documented
-leads, neither exercised:
-
-```sh
-# Canaan's own tool — see K230_SDK_Burntool_User_Guide.md in kendryte/k230_docs
-# k230_burntool ...
-
-# oreboot's kendryte_boot — author reports Linux from mask ROM over USB in ~3 s
-# https://github.com/oreboot/oreboot
-```
-
-**Do not present either as authoritative.** They are the paths to try, not paths that have been
-shown to work on this board.
-
-## 7. Commands that failed — kept deliberately
-
-| Command | Failure | Diagnosis | Correct form |
-|---|---|---|---|
-| `curl .../products/t-display-series/t-display-k230-cased-version/` | **404** | Guessed the wiki URL shape; the Cased Version is a *child page*, not a sibling product | `.../t-display-series/t-display-k230/cased-version.html` |
-| Searching only `en/` in `k230_docs` for schematics | zero results | Wrong conclusion ("Canaan publishes no schematics"). The artifacts are in the **`zh/`** tree | list `zh/00_hardware/` as well |
-| First `k230_docs` listing missed `K230_brief_datasheet.md` | not in `00_hardware/` | The brief datasheet sits at the **tree root** (`en/`), not under `00_hardware/` | list the whole tree, filter afterwards |
diff --git a/devices/lilygo/t-display-k230/community.md b/devices/lilygo/t-display-k230/community.md
deleted file mode 100644
index b85cf9a..0000000
--- a/devices/lilygo/t-display-k230/community.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# T-Display K230 — community index
-
-Thread-level index. Quotations, evidence labels and analysis are in
-[`projects-and-community.md`](projects-and-community.md); this file is the navigable list.
-
-## Threads
-
-| Date | Subreddit | Title | Score | Comments | URL |
-|---|---|---|---:|---:|---|
-| 2026-08-20 | **r/LilyGO** | The T-Display K230 Kit is finally here! 🎉 | 83 | 22 | `https://old.reddit.com/r/LilyGO/comments/1vtcjuj/` |
-| 2026-07-28 | r/LilyGO | Keyboard for T-Display K230 is here 🙌 | 34 | 4 | `https://old.reddit.com/r/LilyGO/comments/1v8kedv/` |
-| **2025-07-07** | **r/meshtastic** | **New Lilygo T-Display K230** | **187** | **40** | `https://old.reddit.com/r/meshtastic/comments/1ltxxxo/` |
-| 2025-07-04 | r/LilyGO | T-Display K230 and T-Lora Pager have some stock available | 3 | 0 | `https://old.reddit.com/r/LilyGO/comments/1lr7zrf/` |
-| 2025-04-25 | r/LilyGO | T-Display K230, integrated AMOLED display and can run Linux or RTOS | 7 | 1 | `https://old.reddit.com/r/LilyGO/comments/1k79az1/` |
-| 2025-03-21 | r/LilyGO | T-Display K230 is available! | 12 | 5 | `https://old.reddit.com/r/LilyGO/comments/1jgb4kn/` |
-| 2025-10-23 | r/brucefw | need help with finding the device for bruce | 4 | 9 | `https://old.reddit.com/r/brucefw/comments/1oduhp0/` — Bruce is ESP32-only; not applicable |
-
-## K230-chip threads (not this board)
-
-| Date | Subreddit | Title | Score | Comments |
-|---|---|---|---:|---:|
-| 2025-03-03 | r/RISCV | Kendryte K230 RISC-V Development Board – CanMV-K230 Default App | 0 | 0 |
-| 2024-05-09 | r/RISCV | Kendryte K230 (RVV1.0 supported) available for remote access | 14 | 17 |
-| 2024-05-08 | r/RISCV | Where do people buy CANMV K230 from? | 6 | 18 |
-| 2024-01-30 | r/RISCV | [Ready to go] CanMV-K230 … 512MB RAM 3x 4K Camera Inputs Support RVV1.0 for AI | 13 | 9 |
-| 2023-12-15 | r/RISCV | How to run baremetal program on a Canaan Kendryte K230 development board? | 2 | 8 |
-| 2023-10-26 | r/RISCV | CanMV-K230 AI development board features Kendryte K230 dual-core 64-bit RISC-V processor – CNX Software | 14 | 10 |
-| 2023-10-18 | r/RISCV | Kendryte K230 RISC-V Development Board – CanMV-K230 – AnalogLamb | 19 | 21 |
-
-## Editorial
-
-| Publication | Coverage of **this board** |
-|---|---|
-| **CNX-Software** | **None.** Site search for `K230` on 2026-09-04 returned 5 results — CanMV-K230 (2023-10-24), BPI-CanMV-K230D-Zero (2024-11-18), K510 (2021-07-09) and two HUSKYLENS articles. |
-| **Hackaday** | **None found.** |
-| **Video** | LilyGO's wiki links one "K230 SDK Video Tutorial" at `https://www.youtube.com/watch?v=lxcQWDoruOI`. **Not watched** in this pass. The oreboot maintainer also references a demo on his own YouTube channel; URL not captured. |
-| Chinese-language sources | **Not searched directly.** Recorded gap. |
-
-## The shape of the coverage
-
-Two things stand out.
-
-**The RISC-V community has never discussed this board.** r/RISCV has seven threads about the K230
-chip and CanMV boards spanning 2023–2025, and **zero** about the LilyGO product. The board's only
-real community moment came from **r/meshtastic**, whose interest is LoRa and a screen, not the
-instruction set.
-
-**No independent editorial coverage exists at all.** The most prolific SBC publication has
-covered two other K230 boards and not this one. There is no review, no teardown, no benchmark,
-no photograph of the PCB. Everything known about this product comes from LilyGO, from Canaan, or
-from roughly two dozen Reddit comments.
diff --git a/devices/lilygo/t-display-k230/comparisons-and-recommendations.md b/devices/lilygo/t-display-k230/comparisons-and-recommendations.md
deleted file mode 100644
index 32279c4..0000000
--- a/devices/lilygo/t-display-k230/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,129 +0,0 @@
-# T-Display K230 — competitors, equivalents and recommendations
-
-Comparisons are scoped to a stated workload. Nothing here is called "equivalent" unless the
-interfaces, performance and software requirements actually align — and in this comparison set,
-almost nothing does.
-
-## 1. Direct comparison
-
-Prices are the dated observations from [`market-and-pricing.md`](market-and-pricing.md);
-everything else is vendor specification. **No cross-device benchmark exists**, so no performance
-ranking is offered.
-
-| | **T-Display K230 Kit** | **LilyGO T-Deck Plus** | **LilyGO T-Display P4** | **M5Stack Cardputer** | **CanMV-K230** | **BPI-CanMV-K230D-Zero** |
-|---|---|---|---|---|---|---|
-| SoC | K230, 2 × RV64 @ 1.6 + 0.8 GHz | ESP32-S3 | ESP32-P4 | ESP32-S3 | K230 | K230D |
-| Class | **application processor, Linux** | MCU | MCU | MCU | application processor | application processor |
-| RAM | **1 GB LPDDR4** | 8 MB PSRAM | 16/32 MB PSRAM | 8 MB PSRAM | 512 MB | 128 MB (SiP) |
-| NPU | **yes (KPU)** | no | **no** | no | yes | yes |
-| Vector | **RVV 1.0 on CPU1** | no | Espressif PIE | no | RVV 1.0 | RVV 1.0 |
-| Display | **4.1″ AMOLED 568×1232** | 2.8″ IPS 320×240 | — (kit) | 1.14″ 240×135 | none | none |
-| Keyboard | **full QWERTY, backlit** | small QWERTY + trackball | separate, incompatible | QWERTY | none | none |
-| Camera | **2 MP MIPI CSI** (3 CSI available) | no | MIPI CSI capable | optional unit | 3 × CSI | CSI |
-| Video codec | **H.264+H.265 enc *and* dec** | none | H.264 **enc only** | none | same as K230 | same |
-| Wi-Fi | 2.4 GHz 802.11n (external) | 2.4 GHz (integrated) | **none on SoC** | 2.4 GHz | — | — |
-| Bluetooth | **USB dongle only** | integrated BLE | **none on SoC** | integrated BLE | — | — |
-| LoRa | **SX1262 or LR2021** | SX1262 | no | via unit | no | no |
-| Cellular / GNSS | **nRF9151 option** | GPS option | no | no | no | no |
-| Ethernet | **100 Mbit USB** | no | **MAC on SoC** | no | no | yes |
-| OS | **Linux** | Arduino / ESP-IDF | ESP-IDF | Arduino / M5 | Linux | Linux |
-| Toolchain maturity | **poor** | **excellent** | good | excellent | poor | poor |
-| Price, 2026-09-04 | **$263.56** full | ~$60–70 (not re-verified) | not observed | ~$30 (not re-verified) | not established | **$29** (2024) |
-
-⚠ **The T-Deck Plus and Cardputer prices are from memory of the general market, not from a dated
-observation made in this pass.** They are marked as such and must not be quoted as findings.
-
-## 2. What each comparison actually tells you
-
-**vs T-Deck Plus** — the closest thing in spirit, and the wrong comparison technically. The
-T-Deck Plus is an ESP32-S3 handheld: cheaper, mature, with an enormous community and a working
-Meshtastic firmware today. The K230 kit costs roughly four times as much and gives you Linux, a
-much better screen, a camera and an NPU. **If your project is "a Meshtastic node with a keyboard",
-buy the T-Deck Plus.** If it is "a Linux computer that happens to have LoRa", the T-Deck cannot
-do it at all. One user made the trade explicitly: *"If the WiFi is any better than the t-deck plus
-I might end up with one."*
-
-**vs T-Display P4** — the interesting one, because it is the same vendor, the same product line
-and the same idea one class down. The P4 is a *microcontroller* with MIPI DSI and CSI; it runs
-ESP-IDF, which is a genuinely good SDK with reproducible NixOS packaging. The K230 runs Linux with
-1 GB of RAM and an NPU, and its build system wants Ubuntu and a hard-coded `/opt/toolchain`.
-**The K230 is more capable and much harder to work with.** The keyboards are mutually incompatible
-(LilyGO, 2026-07-28). See [`components/espressif/esp32-p4`](../../../components/espressif/esp32-p4/README.md)
-and the [K230 record §11](../../../components/canaan/k230/README.md#11-competing-and-substitute-parts).
-
-**vs M5Stack Cardputer** — not a competitor. An order of magnitude cheaper, an order of magnitude
-less capable. It came up in this research only because a user asked whether to buy one instead.
-One K230 kit buyer said: *"I'll stick with the cardputer zero I ordered but I'm going to be
-watching this."*
-
-**vs CanMV-K230 / BPI-CanMV-K230D-Zero** — same silicon, no display, no keyboard, no radio, and
-**half or an eighth of the memory**. If you want to develop for the K230 chip and do not need a
-handheld, the $29 Zero is the rational purchase. The LilyGO board is the only K230 board with
-1 GB and the only one with a screen attached.
-
-**vs a de-Googled phone** — raised by the community, and it is a fair challenge for the
-Meshtastic use case specifically. A phone has better radios, a better screen, a much better
-battery and a real OS. It does not have a 40-pin header, three MIPI CSI inputs, an LR2021, or a
-Linux userspace you control.
-
-## 3. Alternatives by tier — for a *LoRa-mesh handheld*, dated 2026-09-04
-
-| Tier | Choice | Why |
-|---|---|---|
-| **Budget** | A dedicated Meshtastic node (~$30) + your phone | Best battery life, best software maturity, lowest cost |
-| **Mainstream** | **LilyGO T-Deck Plus** | Integrated keyboard handheld, mature Meshtastic support, no build system required |
-| **Capability** | **T-Display K230 Kit, `K277` + `K256-04`** | The only option with mesh **voice and photo** transfer, plus Linux, a camera and cellular |
-| **Experimentation / RISC-V** | **T-Display K230 bare board `K256`** | Cheapest route to 1 GB of K230 with a screen |
-| **Chip development only** | **BPI-CanMV-K230D-Zero** ($29) | Cheapest K230; accept 128 MB |
-| **Professional / product** | **None of the above** | No certification data, no errata, no published schematic, no recovery procedure, no licence on the vendor firmware |
-
-## 4. Alternatives by tier — for an *on-device vision/AI* project
-
-| Tier | Choice | Why |
-|---|---|---|
-| Cheapest working NPU | Sophgo CV1800B boards (Milk-V Duo) | ~0.5 TOPS, 64 MB, tiny, cheap |
-| Balanced | **T-Display K230** | 1 GB, real ISP, 3 CSI, H.265, integrated screen |
-| Mature ecosystem | Rockchip RV1106 boards | The IP-camera default; large community; single Cortex-A7 |
-| Arm alternative | Allwinner V853 | Mature Tina Linux BSP |
-| **MCU-class** | ESP32-P4 | If 32 MB of PSRAM is enough and you want ESP-IDF |
-
-## 5. Clones and used market
-
-**No clone of the T-Display K230 was found** in any search performed. **No used listings** were
-found either — the kit is fifteen days old at the research date. Both are negative results from a
-search that did not include AliExpress or Taobao ([`research-log.md`](research-log.md)), so they
-are weaker than they look.
-
-## 6. Comparison traps specific to this device
-
-1. **"Two RISC-V cores" ≠ a dual-core SMP system.** Two independent subsystems, one with a vector
-   unit and one without, historically running two different operating systems.
-2. **"Ethernet" ≠ an Ethernet MAC.** 100 Mbit over USB.
-3. **"Wi-Fi + Bluetooth" ≠ integrated.** SDIO Wi-Fi and a Bluetooth *dongle*.
-4. **"1.6 TOPS" is not a datasheet figure.** Canaan publishes none.
-5. **"Kit" is two purchases**, and no single SKU is the complete handheld.
-6. **A 2025 review describes a different product** — the software arrived in August 2026.
-7. **`K230` as a SKU means a T-Embed CC1101.** Never infer silicon from a LilyGO stock code.
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered.
-
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — the K230 Kit placed against the Cardputer ADV ($29.90), the Cardputer v1.1 and
-  the Tanmatsu (~€120) in a keyboard-handheld group, with the **$263.56 complete
-  price** stated up front and the comparisons that are not supportable — notably
-  that **no independent benchmark of this board exists**, even though its own BSP
-  builds CoreMark into the shipped image.
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — the K230 against ESP32-C3/S3/P4 and the nRF parts on memory, radio integration,
-  toolchain maturity and price. Two figures from this record do heavy lifting there:
-  the **≤ 20 µW SoC standby** claim and the board's **2.5 W idle**, which together
-  are the whole Linux-versus-MCU trade. It also uses the **$42.31 nRF9151 delta**
-  between `K256-04` and `K256-04-A` as the only clean per-chip price signal in this
-  repository.
-- [**Adding LoRa, NFC and an RGB sidelight to e-ink firmware**](../../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-  — for the LR2021-versus-SX1262 purchase decision in a wider radio context.
diff --git a/devices/lilygo/t-display-k230/compatibility-and-status.md b/devices/lilygo/t-display-k230/compatibility-and-status.md
deleted file mode 100644
index 23c0c76..0000000
--- a/devices/lilygo/t-display-k230/compatibility-and-status.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# T-Display K230 — compatibility and status
-
-Keyed by BSP version where known. **No entry in this file was verified on hardware by this
-session**; the status column reflects what LilyGO states plus what community members report.
-
-## LilyGO's own feature status — BSP v0.2.4 (2026-09-03)
-
-### Stated **stable**
-
-Camera · gallery · music · network radio · recorder · video player · terminal · MTP · Wi-Fi ·
-Ethernet · display · audio · notification · battery · charger · sensor · keyboard · system
-settings.
-
-### Stated **beta**
-
-| Feature | Caveat stated by LilyGO |
-|---|---|
-| **Meshtastic** | Chat, node display, map view, channel sharing work. **Voice/photo transfer requires LR2021**; SX1262 gets text only |
-| LoRaWAN | — |
-| **Xiaozhi** voice assistant | Needs network **and** a compatible Xiaozhi service; wake word only while the app owns the mic |
-| **PicoClaw** | Needs network **and** an OpenAI-compatible API key. The board does not run a model locally |
-| nRF9151 cellular / GNSS | Requires the keyboard base |
-| nRF52840 UART DFU | Ownership arbitrated against Meshtastic BLE since v0.2.2 |
-
-### Stated **not included / user-supplied**
-
-NES ROMs · offline map tiles · user media. **HDMI** is "kept as a diagnostic feature"; AMOLED is
-the default path.
-
-### Runtime-optional, detected only if present
-
-nRF9151 · nRF52840 · TCA8418 · BQ27220 · BQ25896 · XL9555 · AHT20. On a bare `K256` board, none
-of these exists and the corresponding UI does not appear.
-
-## Community-reported status
-
-| Report | Date | Evidence class | Status |
-|---|---|---|---|
-| **Board bricked** by a boot-medium change; unresponsive to boot pin and terminal afterwards | 2026-08-21 / 2026-08-28 | **firsthand ownership** | **Failing.** Not contradicted by anyone. No recovery reported. |
-| Got "an mp3 player and notepad working"; then the "fun" features bricked it | 2026-08-21 | firsthand ownership | Partial |
-| "completely unable to figure out how to even get an OS installed" (bare board, pre-BSP era) | 2026-08-20 | firsthand ownership | Failing at the time; the BSP now exists |
-| Keyboard base does **not** include a case for the main board | 2026-08-13 | firsthand ownership | Confirmed limitation |
-| Early units shipped as bare board on risers — no case, no battery | 2026-08-20 | firsthand ownership | Confirmed for pre-kit purchases |
-| Ethernet port physically present and large for the form factor | 2025-07-07 | firsthand observation | Confirmed |
-| No Bluetooth markings visible; K230 page does not mention Bluetooth | 2025-07-08 | firsthand observation | Consistent with the BSP |
-| oreboot supports K230; boots Linux from mask ROM over USB in ~3 s | 2025-03-26 | **demonstrable project**, author's own statement | Reported-working **for K230 generally**, not demonstrated on this board |
-| Independent Meshtastic UI in progress, "lots of challenges adapting to the K230's preferred formats" | 2026-06-02 | announced project | In progress, no repository |
-| "sold out" days after launch | 2025-03-26 | firsthand | Availability, since resolved |
-
-**Prevalence:** four distinct firsthand-ownership reports were found across **26 comments in the
-two largest threads** reviewed. That is the whole sample. It is far too small to support any
-statement about how common bricking is — only that it happened at least once, to someone who
-described the exact sequence.
-
-## Software-version compatibility
-
-| Component | Version this board is pinned to | Notes |
-|---|---|---|
-| Kendryte Linux SDK | `22d02c6b6783a57a3aca7eb3160e313e772cb710` (`dev`) | Recorded in `k230_bsp/metadata/upstream_sdk_commit.txt` |
-| Kernel | `ruyisdk/linux-xuantie-kernel` @ `7d4e1f444f461dbe3833bd99a4640e7b6c2cd529`, defconfig `k230` | **Not mainline** |
-| Toolchain | XuanTie GCC `Xuantie-900-gcc-linux-6.6.0-glibc-x86_64-V3.0.2` | Hard-coded `/opt/toolchain` path |
-| LVGL | `59dc7e436ae97a25e32656739ea6a943f9f11b6a` + 4 LilyGO patches | Upstream pin retained |
-| NCS (nRF9151) | **v3.4.0** | Repository-relative install |
-| Nordic Serial LTE Modem | `13c80da97fe4d55ecb5a9745834d97be22821307` + 5 patches | Upstream pin retained |
-| SoftDevice (nRF52840) | **S140 6.1.1** | In the shipped bootloader |
-| PlatformIO (nRF52840) | `nordicnrf52`, board `nrf52840_dk_adafruit` | Arduino framework |
-
-**Everything is pinned.** That is unusually good hygiene and it means a rebuild in a year should
-still produce the same image — provided the XuanTie tarball and the upstream Git remotes survive.
-
-## Known incompatibilities
-
-| Claim | Status |
-|---|---|
-| Arduino IDE for the K230 | **Incompatible.** LilyGO's own FAQ says so. |
-| ESP-IDF | **Incompatible.** Different architecture and vendor. |
-| The T-Display **P4** keyboard | **Incompatible** with this board — LilyGO, 2026-07-28 |
-| The T-Display K230 keyboard on a P4 | **Incompatible** — same source |
-| Mainline Linux | **Not supported.** Vendor kernel only. |
-| Zephyr | **No K230 support upstream** as of 2026-09-04 |
-| CanMV / MaixPy | Run on K230; **no board profile for this board** — display, touch and keyboard need porting |
-| Canaan `k230_evb_defconfig` images | Boot, but drive none of this board's peripherals |
-| Mainline RVV-1.0 binaries | Not interchangeable with the shipped `-mrvv-v0p10-compatible` userspace |
diff --git a/devices/lilygo/t-display-k230/coverage.md b/devices/lilygo/t-display-k230/coverage.md
deleted file mode 100644
index 710f708..0000000
--- a/devices/lilygo/t-display-k230/coverage.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# T-Display K230 — feature coverage
-
-Legend for **Evidence**: `V` vendor-documented · `S` vendor source code read in this pass ·
-`C` community-reported · `—` none found.
-**Test status** is uniform: nothing was executed on hardware in this pass.
-
-| Feature | Hardware | Component record | Vendor doc | Source read | Community | Feature guide | Build tested | HW tested | Gap |
-|---|---|---|---|---|---|---|---|---|---|
-| AMOLED display | RM69A10 + K230 DSI | [✔](../../../components/raydium/rm69a10/README.md) | V | S | C | [✔](features/display.md) | no | **no** | refresh rate, brightness curve, measured fps |
-| Touch | GT9895 | [✔](../../../components/goodix/gt9895/README.md) | V | S | — | [✔](features/touch.md) | no | **no** | touch-point count, datasheet |
-| Keyboard | TCA8418 + XL9555 | [✔](../../../components/texas-instruments/tca8418/README.md) · [✔](../../../components/xlsemi/xl9555/README.md) | V | S | C | [✔](features/keyboard.md) | no | **no** | rollover, XL9555 actual address |
-| Keyboard backlight | K230 PWM4 | — | V | S | — | [✔](features/keyboard.md) | no | **no** | brightness curve |
-| Camera | GC2093 | [✔](../../../components/galaxycore/gc2093/README.md) | V | S | C | [✔](features/camera.md) | no | **no** | `GC-6` — sensor parameters |
-| ISP | K230 | [✔](../../../components/canaan/k230/README.md) | V | — | — | [✔](features/camera.md) | no | **no** | tuning not exercised |
-| **KPU / NPU** | K230 | [✔](../../../components/canaan/k230/README.md) | V | S | C | [✔](features/kpu-npu.md) | no | **no** | no measurement on this board; TOPS disputed |
-| Dual RISC-V cores / RVV | K230 | [✔](../../../components/canaan/k230/README.md) | V | S | C | [✔](features/dual-core-riscv.md) | no | **no** | `GC-1` — which core runs Linux here |
-| Video encode/decode | K230 VPU | [✔](../../../components/canaan/k230/README.md) | V | — | — | — *(covered in the component record)* | no | **no** | not exercised |
-| GPU (2.5D) | K230 | [✔](../../../components/canaan/k230/README.md) | V | S (`vg_lite_demos`) | — | — *(component record)* | no | **no** | not exercised |
-| DPU (structured light) | K230 | [✔](../../../components/canaan/k230/README.md) | V | — | — | — | no | **no** | **no structured-light projector on this board** — silicon feature, unusable as fitted |
-| Wi-Fi | RTL8189FS | [✔](../../../components/realtek/rtl8189fs/README.md) | V | S | C | [✔](features/wifi-and-bluetooth.md) | no | **no** | throughput; which module is actually fitted |
-| Bluetooth | USB dongle | — *(no on-board part)* | partial | S | C | [✔](features/wifi-and-bluetooth.md) | no | **no** | `GC-2` — ESP32-S3 claim |
-| Ethernet | USB, RTL8152B claimed | [✔](../../../components/realtek/rtl8152b/README.md) | V | S | C | [✔](features/ethernet.md) | no | **no** | `GC-3` — controller identity |
-| LoRa | SX1262 / LR2021 | [✔](../../../components/semtech/sx1262/README.md) · [✔](../../../components/semtech/lr2021/README.md) | V | S | C | [✔](features/lora.md) | no | **no** | range, TX current, certification |
-| Audio out | K230 codec + MAX98357A | [✔](../../../components/analog-devices/max98357a/README.md) | V | S | — | [✔](features/audio.md) | no | **no** | speaker amp unidentified (U2) |
-| Microphone | unknown | [U3](../../../components/unidentified/t-display-k230/README.md) | partial | S | — | [✔](features/audio.md) | no | **no** | PDM or analogue? |
-| 3.5 mm jack | K230 codec | — | V (cased only) | — | — | [✔](features/audio.md) | no | **no** | |
-| microSD | K230 MMC1 | [✔](../../../components/generic/micro-sd-sdmmc/README.md) | V | S | C | [✔](features/microsd.md) | no | **no** | throughput |
-| USB host | K230 OTG | — | V | S | C | [✔](features/usb.md) | no | **no** | speed not confirmed |
-| USB gadget (MTP/MSC/RNDIS/ACM) | K230 OTG | — | V | S | — | [✔](features/usb.md) | no | **no** | |
-| Battery + charging | BQ25896 + BQ27220 | [✔](../../../components/texas-instruments/bq25896/README.md) · [✔](../../../components/texas-instruments/bq27220/README.md) | V | S | C | [✔](features/battery-and-power.md) | no | **no** | **battery life never measured** |
-| Power key | K230 PMU INT0 | [✔](../../../components/canaan/k230/README.md) | V | S | — | [✔](features/battery-and-power.md) | no | **no** | |
-| Thermal sensor | K230 | [✔](../../../components/canaan/k230/README.md) | V | S | — | [✔](features/battery-and-power.md) | no | **no** | no thermal data |
-| 40-pin header / GPIO | K230 | [✔](../../../components/canaan/k230/README.md) | V | S | — | [✔](features/gpio-and-expansion.md) | no | **no** | current limits |
-| ADC ×3 | K230 | — | **—** | — | — | [✔](features/gpio-and-expansion.md) | no | **no** | `GC-8` — not in the peripheral list |
-| BLE via nRF52840 | nRF52840 | [✔](../../../components/nordic-semiconductor/nrf52840/README.md) | V | S | — | [✔](features/nrf52840-ble.md) | no | **no** | range, throughput |
-| Cellular + GNSS | nRF9151 | [✔](../../../components/nordic-semiconductor/nrf9151/README.md) | V | S | — | [✔](features/nrf9151-cellular-gnss.md) | no | **no** | bands, SIM form factor, antenna, certification |
-| Temp/humidity | AHT20 | [✔](../../../components/asair/aht20/README.md) | V | S | — | [✔](features/gpio-and-expansion.md) | no | **no** | AHT10 vs AHT20 uncertainty |
-| HDMI out | LT9611 (?) | [✔](../../../components/lontium/lt9611/README.md) | V | S | — | referenced in [display.md](features/display.md) | no | **no** | `GC-4` — presence unconfirmed |
-| QWIIC | — | — | V (cased only) | — | — | [✔](features/gpio-and-expansion.md) | no | **no** | which bus? |
-| 16 MB flash | unknown | — | V | **—** | — | — | no | **no** | `GC-9` — role unknown |
-| PMIC | unknown | [U1](../../../components/unidentified/t-display-k230/README.md) | **—** | **—** | — | — | no | **no** | not identified at all |
-
-## Summary
-
-| | Count |
-|---|---:|
-| Advertised or fitted capabilities enumerated | **32** |
-| With a component record | 24 |
-| With a feature guide | 16 (guides) covering 28 capabilities |
-| With an explicit recorded gap | 9 tracked as `GC-1`…`GC-9`, plus 6 unidentified parts |
-| **Build-tested here** | **0** |
-| **Hardware-tested here** | **0** |
-
-**The honest headline: coverage of *documentation* is broad; coverage of *verification* is zero.**
-Every capability above has a hardware path traced to a component record and a task-oriented guide,
-and not one of them has been observed working. The `commands.md` §5 list is written so that a
-single session with hardware in hand could close most of the gaps in an afternoon.
-
-## Silicon capabilities present but unusable as fitted
-
-Worth stating because they inflate spec-sheet comparisons:
-
-- **DPU (3D structured light)** — needs a projector and an IR camera. Neither is fitted.
-- **RGB-IR 4×4 ISP mode** — needs an RGB-IR sensor. GC2093 is not one.
-- **Two further MIPI CSI inputs** — unpopulated, but genuinely available on the header.
-- **eMMC / SPI NAND boot** — supported by the SoC; the board boots from SD.
-- **8 PDM DMIC inputs** — far more than the board fits.
-- **Deep sleep ≤ 20 µW** — a silicon claim with no board-level demonstration.
diff --git a/devices/lilygo/t-display-k230/development.md b/devices/lilygo/t-display-k230/development.md
deleted file mode 100644
index bb249c8..0000000
--- a/devices/lilygo/t-display-k230/development.md
+++ /dev/null
@@ -1,261 +0,0 @@
-# T-Display K230 — development
-
-**Evidence status: everything on this page is `reported-working` or `inferred`. Nothing was
-executed.** No K230 hardware and no Ubuntu build host were available on 2026-09-04. Commands are
-transcribed verbatim from LilyGO's and Canaan's own documentation; the command ledger with
-status labels is [`commands.md`](commands.md).
-
----
-
-## 1. There are four toolchains, and they are unrelated
-
-This is the first thing to understand about the board.
-
-| Target | Toolchain | Language / framework |
-|---|---|---|
-| **K230** (the main SoC) | XuanTie GCC + Buildroot + Kendryte Linux SDK | C/C++ on Linux, LVGL for UI |
-| **nRF52840** companion | **PlatformIO** `nordicnrf52`, board `nrf52840_dk_adafruit` | Arduino |
-| **nRF9151** companion | **nRF Connect SDK v3.4.0** via `nrfutil sdk-manager` | Zephyr |
-| SD card | `dd` / Rufus | — |
-
-**Nothing in the ESP32 world applies.** LilyGO's own FAQ: *"Q: Can I use Arduino IDE for
-T-Display K230? A: **No.** T-Display K230 is based on the Kendryte K230 RISC-V SoC and requires
-the K230 SDK toolchain."*
-
-⚠ The LilyGO **wiki** contradicts this by offering PlatformIO/Arduino instructions for an
-"ESP32-S3 co-processor" — see [`GC-2`](gaps-and-conflicts.md).
-
----
-
-## 2. Building the K230 system image
-
-### 2.1 Host
-
-LilyGO: **Ubuntu 22.04 or 24.04 recommended**. Canaan's own wiki instructions say Ubuntu 20.04 or
-Docker. Windows: **WSL2 with Ubuntu only** — LilyGO explicitly warns off CMD, PowerShell, Git
-Bash, MSYS2 and Cygwin, and warns not to build under `/mnt/c/...` because it "is slower and can
-break Linux-style permissions or symlinks used by the SDK".
-
-```sh
-sudo apt update
-sudo apt install -y git ca-certificates build-essential make rsync python3
-```
-
-### 2.2 Clone — **with submodules**
-
-```sh
-git clone --recurse-submodules https://github.com/Xinyuan-LilyGO/T-Display-K230.git t-display-k230
-cd t-display-k230
-# if you forgot:
-git submodule update --init --recursive
-```
-
-The submodule is `k230_linux_sdk` → `https://github.com/kendryte/k230_linux_sdk.git`, pinned by
-`k230_bsp/metadata/upstream_sdk_commit.txt` to **`22d02c6b6783a57a3aca7eb3160e313e772cb710`**
-(branch `dev`). Cloning without `--recurse-submodules` gives you an empty SDK directory and a
-build that fails immediately.
-
-### 2.3 Toolchain and host dependencies
-
-```sh
-./scripts/setup_ubuntu.sh
-```
-
-This is `apt`-based. It installs, among other things, the **XuanTie toolchain to
-`/opt/toolchain/`** — the defconfig hard-codes
-`BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/toolchain/Xuantie-900-gcc-linux-6.6.0-glibc-x86_64-V3.0.2/"`.
-On a non-FHS host this is the step that breaks; see
-[`guides/nixos/riscv-and-vendor-sdk-toolchains.md`](../../../guides/nixos/riscv-and-vendor-sdk-toolchains.md).
-
-### 2.4 Apply the board overlay, then build
-
-```sh
-./scripts/apply_to_sdk.sh
-./scripts/build_sdcard_image.sh
-# output:
-#   k230_bsp/images/sysimage-sdcard.img
-```
-
-Clean rebuild:
-
-```sh
-rm -rf k230_linux_sdk/output
-./scripts/apply_to_sdk.sh
-./scripts/build_sdcard_image.sh
-```
-
-The overlay is not a patch series applied to a checkout — it is a **file overlay plus a patch
-set**, catalogued in `k230_bsp/metadata/overlay_manifest.txt` (5 764 bytes) and applied by
-`k230_bsp/scripts/apply.sh`. That manifest is the file to read if you want to know exactly what
-LilyGO changes about the stock SDK without diffing two trees.
-
-### 2.5 What the overlay actually contains
-
-| Area | Contents |
-|---|---|
-| **U-Boot** (`u-boot-2022.10-overlay`) | `k230_canmv_v3.dts`, `k230d.dtsi`, `k230_board_common.c`, a full **boot-logo** implementation (`display_logo.c/.h`, `k230_logo.c`, `st7701.c`), and `k230_canmv_t_display_defconfig` |
-| **Linux patches** | 30+ numbered patches, `0025`–`0064`. Display/DSI: `0025`, `0026`, `0029`, `0030`, `0031`, `0032`, `0033`, `0038`, `0039`, `0041`, `0042`, `0043`, `0049`, `0051`. Touch: `0034` (**307 KB**). Camera: `0036`. Graphics: `0035` GDMA rotation. LoRa: `0054`. HDMI: `0055`, `0062`. Bluetooth: `0056`, `0057`. Audio: `0058`, `0059`. UARTs: `0060`, `0061`. Thermal: `0063`. Power key: `0064`. |
-| **Rejected patches** | `linux/rejected/0044-drm-canaan-use-wc-allocation-for-dumb-buffers.rejected` — **kept in the tree.** Good practice; it tells you write-combine dumb-buffer allocation was tried and did not apply. |
-| **Buildroot packages** | LVGL (pinned to upstream commit `59dc7e436ae97a25e32656739ea6a943f9f11b6a` with **four** LilyGO patches), `rtl8189fs`, `rtl8723ds`, `rtl8723ds-bt`, `rtl8733bs`, `vvcam` (with `gc2093.c`) |
-| **Rootfs overlay** | `S40bluetoothd`, `S41adb_mtp`, `inittab`, `k230-usb-storage-gadget`, `getty-tty1-rm69a10`, and the boot splash images `logo.xrgb` (2.8 MB) / `logo.yuv` (1.0 MB) |
-| **Launcher** | `k230_phone_ui`, an LVGL application with ~50 UI modules, a 9.5 MB CJK font, a Pinyin dictionary and emoji tables |
-
-**The LVGL fork is properly documented**, which is unusual. Upstream commit is pinned in the
-directory name, and the four patches are named for what they do: a pcpp Python preprocessor
-fallback, K230 plane rotation in the DRM backend, FreeType fixed-colour-bitmap scaling, and a
-K230 staging scanout buffer. The pinned upstream revision the patches apply to is retained.
-
-### 2.6 Faster iteration — deploy over SSH
-
-Once the board is running and on the network:
-
-```sh
-./scripts/deploy_launcher.sh 192.168.1.100
-./scripts/deploy_launcher.sh 192.168.1.100 --full --reboot   # launcher + boot files
-```
-
-This avoids reflashing the card for every launcher change and is the practical development loop.
-
----
-
-## 3. Flashing the SD card
-
-```sh
-# Linux
-sudo dd if=k230_bsp/images/sysimage-sdcard.img of=/dev/sdX bs=8M status=progress conv=fsync
-sync
-
-# macOS
-diskutil unmountDisk /dev/diskN
-sudo dd if=k230_bsp/images/sysimage-sdcard.img of=/dev/rdiskN bs=8m status=progress
-sync
-```
-
-**Windows: Rufus, in "Write in DD Image mode".** After writing, Windows offers to format an
-unknown partition — **cancel it**; those are the Linux partitions.
-
-Canaan's own wiki instructions use `bs=1M oflag=sync` instead of `bs=8M conv=fsync`; both are
-correct, LilyGO's is faster.
-
----
-
-## 4. Building the nRF52840 firmware
-
-```sh
-python3 -m pip install --user platformio
-cd t-display-k230-nrf52840
-pio run
-# .pio/build/nrf52840/firmware.{elf,bin,hex}
-
-python3 ./scripts/uf2conv.py .pio/build/nrf52840/firmware.hex \
-  -c -f 0xADA52840 -o .pio/build/nrf52840/k230_nrf52840_at.uf2
-```
-
-`platform = nordicnrf52`, `board = nrf52840_dk_adafruit`, `framework = arduino`.
-UF2 family ID **`0xADA52840`** (Adafruit nRF52840 bootloader).
-
-**Entering DFU**, in LilyGO's own words: insert a jumper wire into the `RST` port and *"quickly
-touch the GND hole twice with the other end… (simulating RST being pressed twice). If you find
-this difficult, touching the USB-C metal casing will achieve the same effect."* The board then
-enumerates as a USB drive; drag the `.uf2` onto it. Animated guides:
-`image/dfu_reset_guide_en.gif` in that repository.
-
-There is **also a UART DFU path** driven from the K230 itself
-(`tools/k230_nrf52840_dfu.cpp`, launcher page `ui_nrf52840_dfu.c`, custom bootloader
-`k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex`). That is what lets the handheld update
-its own BLE controller with no PC.
-
-Runtime log: nRF52840 USB-C at 115200. **Some serial monitors need DTR asserted** or you see
-nothing. Expected boot banner:
-
-```
-+BOOT:K230_NRF52840_AT
-+MESH:ADV,1
-DBG <ms> boot
-```
-
----
-
-## 5. Building the nRF9151 firmware
-
-```sh
-nrfutil install sdk-manager
-nrfutil sdk-manager install --install-dir "$PWD/ncs" v3.4.0     # NCS v3.4.0
-export NCS_ROOT=/path/to/ncs/v3.4.0                              # only if installed elsewhere
-
-git clone --recurse-submodules https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151 t-display-k230-nrf9151
-cd t-display-k230-nrf9151
-./build_serial_modem.sh
-# build/serial_modem_k230/zephyr/tfm_merged.hex
-```
-
-If the output layout moves:
-
-```sh
-find build/serial_modem_k230 -path '*/zephyr/tfm_merged.hex' \
-  -o -path '*/zephyr/zephyr.hex' -o -path '*/zephyr/zephyr.elf'
-```
-
-Two profiles: `serial_modem_k230/` (**recommended**, Nordic Serial LTE Modem adapted) and
-`at_client_k230/` (bring-up only). The Serial LTE Modem source is a **pinned submodule**,
-`third_party/ncs-serial-modem` at `13c80da97fe4d55ecb5a9745834d97be22821307`, with five ordered
-LilyGO patches (`0001` GNSS NMEA URC + LED, `0002` optional XDFU, `0003` UART diag, `0004` GNSS
-NMEA URC worker, `0005` LED AT control).
-
-⚠ **`tfm_merged.hex` does not update the modem firmware.** The cellular modem package
-`mfw_nrf91x1_*.zip` is a separate signed image with its own update procedure.
-
-Programming: SWD (the repository ships `images/swd.png`, 3.1 MB, and an
-`images/nRF-ConnectProgrammer.mp4` walkthrough, 2.1 MB).
-
----
-
-## 6. Debug and diagnostics on the running board
-
-| Tool | Where |
-|---|---|
-| **I²C scanner** | Launcher → I2C Scan. Async, multi-bus since v0.2.4. |
-| **Display test** | `ui_display_test.c` |
-| **HDMI test** | `ui_hdmi_test.c` |
-| **I²S test** | `ui_i2s_test.c` |
-| **Multitouch test** | `ui_multitouch.c` |
-| **Mic spectrum** | `ui_mic_spectrum.c` |
-| **DRM motion probe** | `drm_motion_probe.c` (34 KB) |
-| **LVGL scroll probe** | `lvgl_scroll_probe.c` |
-| **LoRa FLRC bench** | `lora_flrc_bench.cpp` |
-| **CoreMark / CoreMark-PRO** | Built into the image (`BR2_PACKAGE_COREMARK`, `_PRO`) |
-| **evtest** | Built in — the right tool for the TCA8418 keyboard and PMU power key |
-| **`linux-tools-gpio`** | Built in (`BR2_PACKAGE_LINUX_TOOLS_GPIO`) — `gpioinfo`, `gpioget`, `gpioset` |
-| **Terminal app** | In the launcher, so you have a shell without SSH |
-| **MTP / ADB** | `S41adb_mtp` init script |
-
----
-
-## 7. Alternative software stacks
-
-| Stack | Applicability to *this board* |
-|---|---|
-| `kendryte/k230_sdk` (dual-OS) | Builds for CanMV/EVB targets. **No T-Display K230 board profile.** Porting means recreating LilyGO's overlay against a different SDK. |
-| **CanMV / MicroPython** (`kendryte/canmv_k230`) | Runs on K230. **No T-Display K230 board support.** Display, touch and keyboard would all need porting. |
-| **MaixPy** (`sipeed/MaixPy`) | Same situation. |
-| **oreboot** | Has K230 support. Boots Linux from mask ROM over USB. **The most interesting recovery lever available** — see [`factory-firmware.md`](factory-firmware.md). |
-| **k230-debian** (`intx82/k230-debian`) | Debian rootfs experiment, kernel 6.6 branch, last touched 2024-12. Not board-specific. |
-| **RT-Thread / RT-Smart** | The CPU1 OS in the dual-OS SDK; not used by this board's Linux-only image. |
-| **Zephyr** | **No K230 support upstream.** |
-
-See [`projects-and-community.md`](projects-and-community.md) for licences, commits and status.
-
----
-
-## 8. Known build and bring-up risks
-
-1. **Cloning without submodules** → empty SDK, immediate failure.
-2. **Building on native Windows or under `/mnt/c/`** → permission and symlink corruption. LilyGO
-   warns explicitly.
-3. **`/opt/toolchain` hard-coded** → breaks on any non-FHS host.
-4. **Buildroot downloads during the build** → no offline or hermetic build without pre-seeding `dl/`.
-5. **Wrong boot medium** → the documented bricking path. See [`factory-firmware.md`](factory-firmware.md).
-6. **IO bank voltage** → Canaan's own DTS says a wrong setting *will damage the chip*.
-7. **nncase version mismatch** → runtime failure, not build failure. Canaan publishes a
-   correspondence table; use it.
-8. **DTR not asserted** on the nRF52840 USB serial → silent console.
diff --git a/devices/lilygo/t-display-k230/examples/best.md b/devices/lilygo/t-display-k230/examples/best.md
deleted file mode 100644
index 2a5f45f..0000000
--- a/devices/lilygo/t-display-k230/examples/best.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# T-Display K230 — selected examples
-
-Six selections from thirteen catalogued candidates ([`catalog.json`](catalog.json)). **None was
-built or run**: no Ubuntu host and no XuanTie toolchain were available. Every "status" below is
-`not-attempted`, and that is stated rather than hidden.
-
-## Why this set looks unusual
-
-This board has **no library, no `examples/` directory and no sketches**. Its software is one
-Buildroot system image containing one large LVGL application. So the selections are a BSP, a set
-of application modules, two companion-MCU firmware projects, an upstream SDK, and a recovery
-tool — not a portfolio of demos.
-
-## The selections
-
-### 1. `K230-BSP-FULL` — the integrated application
-
-`Xinyuan-LilyGO/T-Display-K230` @ `bb831ab358b66f5bd9a87ecd7c580fee4537492e`
-
-The complete board support package plus launcher. Covers **every** feature simultaneously. Chosen
-because there is no alternative: it is the board's software. Notable for pinning its SDK, kernel,
-toolchain and LVGL, for 30+ named kernel patches, and for retaining a `.rejected` patch instead of
-deleting it. **Has no licence file.**
-
-### 2. `K230-LAUNCHER-MODULES` — the per-feature minimal examples
-
-`k230_launcher/k230_phone_ui/src/`, same commit
-
-~50 modules that between them are the minimal-example set. The one to read first is
-**`ui_hardware.c`** — the single most information-dense file in the corpus, containing the
-complete TCA8418 key map, the register set, the PMU power-key constants, the battery shutdown
-policy and the XL9555 address-probe logic. The purpose-built diagnostics
-(`drm_motion_probe.c`, `lvgl_scroll_probe.c`, `ui_i2c_scan.c`, `ui_display_test.c`,
-`ui_i2s_test.c`, `ui_multitouch.c`, `ui_mic_spectrum.c`) are the **limit-testing** examples.
-
-### 3. `K230-NRF52840-AT` — the best small buildable example
-
-`Xinyuan-LilyGO/T-Display-K230-nRF52840` @ `4646a728580739d487126f47a521e9b8032b3c2c`
-
-A single-purpose firmware with a documented AT surface, two DFU routes, and prebuilt binaries to
-compare a local build against. It is the only example on this platform that a newcomer can build
-in minutes with a standard toolchain (`pip install platformio && pio run`). Also the clearest
-demonstration of the board's architecture: **the companion MCU exists because the SoC has no
-Bluetooth**, and it also owns the 5 V boost enable.
-
-### 4. `K230-NRF9151-SLM` — the best-engineered vendor fork
-
-`Xinyuan-LilyGO/T-Display-K230-nRF9151` @ `ed4ecbe34162dec9b81213a400198125bbd6e36f`
-
-Selected specifically as an example of *how to vendor upstream code properly*: the upstream Serial
-LTE Modem is a **pinned submodule** at `13c80da97fe4d55ecb5a9745834d97be22821307`, the five
-patches are named for what they do, and the README pre-empts the classic nRF91 confusion by
-stating that `tfm_merged.hex` does **not** update the modem firmware. This is better hygiene than
-most vendor forks in this repository.
-
-### 5. `K230-LINUX-SDK` — the upstream
-
-`kendryte/k230_linux_sdk`, branch **`dev`**, pinned by LilyGO at
-`22d02c6b6783a57a3aca7eb3160e313e772cb710`. **BSD-2-Clause** — the only clearly-licensed item in
-the set. Required to understand what LilyGO's overlay changes. Note the default branch is `dev`.
-
-### 6. `OREBOOT` — the negative / recovery example
-
-`oreboot/oreboot`, GPL-2.0, 1795★
-
-Selected as the **useful negative example**. The failure mode this board actually exhibits is
-"wrong boot medium, now unresponsive", and neither LilyGO nor this record has a tested procedure
-for it. oreboot's K230 support, and the maintainer's public statement that it boots Linux from
-mask ROM over USB in ~3 seconds, is the only credible documented route back in. Studying it is the
-highest-value thing a reader with hardware can do.
-
-## Deliberately not selected, with reasons
-
-| Candidate | Reason |
-|---|---|
-| **`T-Display-K230_canmv_rt`** | **NOT EXAMINED.** 745 MB, 25★ — more than the main BSP's 1 — created 2025-03-05, last push 2026-08-03. **The largest known gap in this survey.** Start here next. |
-| `kendryte/k230_sdk` (dual-OS) | Targets Canaan EVB/CanMV. Its images boot but drive none of this board's peripherals. |
-| `canmv_k230`, `MaixPy` | K230-capable, **no board profile**. Display, touch and keyboard need porting. |
-| `intx82/k230-debian` | Stale: last push 2024-12-03, 1★, not board-specific. |
-| Independent Meshtastic UI | Announced 2026-06-02, **no repository located**. |
-| Bruce firmware | **Wrong architecture** — ESP32-only. A refuted association, recorded so it is not chased again. |
-
-## Feature coverage of the selected set
-
-| Feature | Covered by |
-|---|---|
-| Display, touch, keyboard, camera, audio, microSD, USB, battery, GPIO, Wi-Fi, Ethernet, LoRa, KPU | `K230-BSP-FULL` + `K230-LAUNCHER-MODULES` |
-| BLE | `K230-NRF52840-AT` |
-| Cellular, GNSS | `K230-NRF9151-SLM` |
-| Build system, toolchain | `K230-LINUX-SDK` |
-| Recovery / boot ROM | `OREBOOT` |
-| **Not covered by any example** | **HDMI beyond a test page; the DPU (no projector fitted); RGB-IR (no sensor); the two spare CSI inputs; deep sleep** |
-
-## Validation status
-
-**Zero built. Zero run. Zero hardware-tested.** The blocking requirements are an Ubuntu 22.04/24.04
-host (or Docker) and the XuanTie toolchain at `/opt/toolchain`. The nRF52840 example is the
-cheapest to validate — PlatformIO alone — and would be the sensible first thing to attempt.
diff --git a/devices/lilygo/t-display-k230/examples/catalog.json b/devices/lilygo/t-display-k230/examples/catalog.json
deleted file mode 100644
index 812b7d3..0000000
--- a/devices/lilygo/t-display-k230/examples/catalog.json
+++ /dev/null
@@ -1,320 +0,0 @@
-{
-  "schema": "hardware-doc/example-catalog/1",
-  "device": "lilygo/t-display-k230",
-  "compiled": "2026-09-04",
-  "caveat": "This board has no library and no examples/ directory. The unit of study is a launcher module, a build script or a companion-MCU firmware project. ZERO examples were built or run: no Ubuntu host and no XuanTie toolchain were available.",
-  "counts": {
-    "cataloged": 13,
-    "selected": 6,
-    "built": 0,
-    "hardware_tested": 0
-  },
-  "examples": [
-    {
-      "id": "K230-BSP-FULL",
-      "title": "T-Display K230 board support package and phone-UI launcher",
-      "author": "LILYGO",
-      "source_class": "vendor/primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230/tree/bb831ab358b66f5bd9a87ecd7c580fee4537492e",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-03",
-      "release_tag": "v0.2.4 (changelog only, no git tag observed)",
-      "commit": "bb831ab358b66f5bd9a87ecd7c580fee4537492e",
-      "device": "T-Display K230 / Kit, all SKUs",
-      "hw_revision": "unknown",
-      "framework": "Buildroot + Kendryte k230_linux_sdk @ 22d02c6b6783a57a3aca7eb3160e313e772cb710; XuanTie GCC V3.0.2; kernel ruyisdk/linux-xuantie-kernel @ 7d4e1f444f461dbe3833bd99a4640e7b6c2cd529",
-      "features": [
-        "display",
-        "touch",
-        "keyboard",
-        "camera",
-        "wifi",
-        "ethernet",
-        "bluetooth-usb",
-        "lora",
-        "audio",
-        "microsd",
-        "usb",
-        "battery",
-        "kpu",
-        "nrf52840",
-        "nrf9151",
-        "hdmi"
-      ],
-      "dependencies": {
-        "lvgl": "59dc7e436ae97a25e32656739ea6a943f9f11b6a + 4 LilyGO patches",
-        "rtl8189fs": "buildroot package",
-        "vvcam": "vendored, sensor gc2093"
-      },
-      "license": "NONE DECLARED",
-      "license_evidence": "no LICENSE file at the pinned commit; GitHub reports no licence",
-      "build_status": "not-attempted",
-      "test_environment": "none \u2014 no Ubuntu host or XuanTie toolchain available",
-      "strengths": [
-        "The only complete software for this board",
-        "Documented pin map",
-        "30+ named kernel patches",
-        "Pinned SDK, kernel, toolchain and LVGL",
-        "Retains a .rejected patch"
-      ],
-      "pitfalls": [
-        "No licence",
-        "Requires --recurse-submodules",
-        "Hard-coded /opt/toolchain path",
-        "Buildroot downloads during build"
-      ],
-      "lineage": "overlay on kendryte/k230_linux_sdk",
-      "selected": true,
-      "selection_reason": "There is no alternative. It is the board."
-    },
-    {
-      "id": "K230-LAUNCHER-MODULES",
-      "title": "k230_phone_ui application modules (~50 files)",
-      "author": "LILYGO",
-      "source_class": "vendor/primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230/tree/main/k230_launcher/k230_phone_ui/src",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230/tree/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_launcher/k230_phone_ui/src",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-03",
-      "commit": "bb831ab358b66f5bd9a87ecd7c580fee4537492e",
-      "device": "T-Display K230",
-      "framework": "LVGL over DRM",
-      "features": [
-        "per-feature reference implementations"
-      ],
-      "license": "NONE DECLARED",
-      "build_status": "not-attempted",
-      "notable_modules": {
-        "ui_hardware.c": "keyboard matrix, TCA8418 registers, PMU constants, battery policy, XL9555 probe \u2014 the single most information-dense file in the tree",
-        "camera_capture.c": "28230 B camera pipeline",
-        "camera_face_detect.cpp": "KPU face detection",
-        "qr_scan.c": "QR decode",
-        "ui_lora.cpp": "LoRa/RadioLib integration",
-        "lora_flrc_bench.cpp": "FLRC benchmark",
-        "lorawan_test.cpp": "LoRaWAN",
-        "k230_meshtastic_probe.cpp": "Meshtastic",
-        "k230_nrf52840_dfu.cpp": "UART DFU host",
-        "ui_nrf9151_manager.c": "cellular/GNSS",
-        "ui_i2c_scan.c": "async multi-bus I2C scanner",
-        "drm_motion_probe.c": "34375 B DRM probe",
-        "lvgl_scroll_probe.c": "scroll benchmark",
-        "ui_display_test.c": "display diagnostics",
-        "ui_i2s_test.c": "audio route test",
-        "ui_multitouch.c": "touch test",
-        "ui_mic_spectrum.c": "microphone test",
-        "k230_storage_expand.sh": "SD expansion",
-        "k230_map_tile_downloader.c": "offline map tiles",
-        "ui_nes.cpp": "NES emulator",
-        "k230_xiaozhi_kws.cpp": "wake word"
-      },
-      "selected": true,
-      "selection_reason": "Collectively the minimal + integrated + diagnostic example set for every feature. There is no separate examples directory; these are it."
-    },
-    {
-      "id": "K230-NRF52840-AT",
-      "title": "nRF52840 BLE-Central AT firmware",
-      "author": "LILYGO",
-      "source_class": "vendor/primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/tree/4646a728580739d487126f47a521e9b8032b3c2c",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-23",
-      "commit": "4646a728580739d487126f47a521e9b8032b3c2c",
-      "device": "nRF52840 base board",
-      "framework": "PlatformIO platform=nordicnrf52, board=nrf52840_dk_adafruit, framework=arduino",
-      "features": [
-        "ble-central",
-        "uart-at",
-        "uart-dfu",
-        "5v-boost-enable"
-      ],
-      "artifacts": {
-        "firmware/k230_nrf52840_at_20260816_r4_k230_uart_dfu.uf2": {
-          "bytes": 296960,
-          "build_date": "2026-08-16",
-          "revision": "r4",
-          "uf2_family": "0xADA52840"
-        },
-        "bootloader/k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex": {
-          "bytes": 525680,
-          "softdevice": "S140 6.1.1",
-          "dfu": "UART @115200"
-        }
-      },
-      "license": "NONE DECLARED",
-      "build_status": "not-attempted",
-      "selected": true,
-      "selection_reason": "Best small self-contained buildable example on the platform; single-purpose, documented AT surface, two DFU routes, prebuilt binaries to compare against."
-    },
-    {
-      "id": "K230-NRF9151-SLM",
-      "title": "nRF9151 Serial LTE Modem, K230 profile",
-      "author": "LILYGO",
-      "source_class": "vendor/primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151/tree/ed4ecbe34162dec9b81213a400198125bbd6e36f",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-14",
-      "commit": "ed4ecbe34162dec9b81213a400198125bbd6e36f",
-      "device": "nRF9151 keyboard base",
-      "framework": "nRF Connect SDK v3.4.0 (Zephyr)",
-      "upstream_pin": "third_party/ncs-serial-modem @ 13c80da97fe4d55ecb5a9745834d97be22821307",
-      "patches": [
-        "0001-k230-gnss-nmea-urc-and-led",
-        "0002-k230-optional-xdfu",
-        "0003-k230-uart-diag",
-        "0004-k230-gnss-nmea-urc-worker",
-        "0005-k230-led-at-control"
-      ],
-      "features": [
-        "lte-m",
-        "nb-iot",
-        "gnss",
-        "nmea",
-        "at",
-        "tfm"
-      ],
-      "license": "NONE DECLARED (LilyGO); upstream Nordic 5-clause",
-      "build_status": "not-attempted",
-      "selected": true,
-      "selection_reason": "Best example of a properly-pinned vendor fork in the whole corpus: upstream commit retained, five patches named for what they do, and the modem-firmware caveat documented in the README."
-    },
-    {
-      "id": "K230-CANMV-RT",
-      "title": "T-Display-K230_canmv_rt",
-      "author": "LILYGO",
-      "source_class": "vendor/primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-K230_canmv_rt",
-      "immutable_url": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-03",
-      "created": "2025-03-05",
-      "commit": null,
-      "stars": 25,
-      "size_kb": 745368,
-      "license": "NONE DECLARED",
-      "build_status": "not-attempted",
-      "selected": false,
-      "selection_reason": "NOT EXAMINED. 745 MB. More stars (25) than the main BSP (1) and predates the product launch. The single largest unexplored artifact for this board; a follow-up session should start here."
-    },
-    {
-      "id": "K230-LINUX-SDK",
-      "title": "Kendryte K230 Linux SDK",
-      "author": "Canaan Creative",
-      "source_class": "chip-vendor/primary",
-      "canonical_url": "https://github.com/kendryte/k230_linux_sdk",
-      "immutable_url": "https://github.com/kendryte/k230_linux_sdk/tree/22d02c6b6783a57a3aca7eb3160e313e772cb710",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-03",
-      "commit": "22d02c6b6783a57a3aca7eb3160e313e772cb710",
-      "branch": "dev",
-      "license": "BSD-2-Clause",
-      "license_evidence": "repository metadata",
-      "build_status": "not-attempted",
-      "selected": true,
-      "selection_reason": "The upstream this board's image is built from. Required to understand the overlay."
-    },
-    {
-      "id": "K230-SDK-DUAL",
-      "title": "Kendryte K230 SDK (RT-Smart + Linux)",
-      "author": "Canaan Creative",
-      "source_class": "chip-vendor/primary",
-      "canonical_url": "https://github.com/kendryte/k230_sdk",
-      "retrieved": "2026-09-04",
-      "last_activity": "2025-09-12",
-      "branch": "main",
-      "license": "BSD-2-Clause",
-      "stars": 273,
-      "build_status": "not-attempted",
-      "selected": false,
-      "selection_reason": "Rejected for this board: targets Canaan EVB/CanMV. Its images boot but drive none of this board's peripherals. Retained in the catalogue because it is the reference for dual-OS work."
-    },
-    {
-      "id": "K230-CANMV-MPY",
-      "title": "CanMV MicroPython for K230",
-      "author": "Canaan Creative",
-      "source_class": "chip-vendor/primary",
-      "canonical_url": "https://github.com/kendryte/canmv_k230",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-03",
-      "branch": "canmv_k230",
-      "license": "NONE DECLARED",
-      "stars": 119,
-      "build_status": "not-attempted",
-      "selected": false,
-      "selection_reason": "Rejected: no board profile. Display, touch and keyboard would all need porting. Note the non-obvious default branch."
-    },
-    {
-      "id": "MAIXPY",
-      "title": "MaixPy",
-      "author": "Sipeed",
-      "source_class": "community/vendor",
-      "canonical_url": "https://github.com/sipeed/MaixPy",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-28",
-      "branch": "main",
-      "license": "NOASSERTION",
-      "stars": 843,
-      "build_status": "not-attempted",
-      "selected": false,
-      "selection_reason": "Rejected: K230-capable, no board profile."
-    },
-    {
-      "id": "OREBOOT",
-      "title": "oreboot \u2014 open firmware with K230 support",
-      "author": "oreboot project",
-      "source_class": "community",
-      "canonical_url": "https://github.com/oreboot/oreboot",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-07-13",
-      "branch": "main",
-      "license": "GPL-2.0",
-      "stars": 1795,
-      "build_status": "not-attempted",
-      "selected": true,
-      "selection_reason": "Selected as the best NEGATIVE/RECOVERY example: the only credible documented route back into a K230 whose SD boot is broken. Maintainer reports Linux from mask ROM over USB in ~3 s (r/LilyGO 2025-03-26)."
-    },
-    {
-      "id": "K230-DEBIAN",
-      "title": "k230-debian",
-      "author": "intx82",
-      "source_class": "community",
-      "canonical_url": "https://github.com/intx82/k230-debian",
-      "retrieved": "2026-09-04",
-      "last_activity": "2024-12-03",
-      "branch": "6.6",
-      "license": "BSD-2-Clause",
-      "stars": 1,
-      "build_status": "not-attempted",
-      "selected": false,
-      "selection_reason": "Rejected as stale: last push 2024-12-03, one star, not board-specific. Retained because it is the only Debian-on-K230 effort found."
-    },
-    {
-      "id": "MESHTASTIC-UI-K230",
-      "title": "Independent Meshtastic UI for T-Display K230",
-      "author": "u/wirecrossed",
-      "source_class": "community",
-      "canonical_url": "https://old.reddit.com/r/meshtastic/comments/1ltxxxo/",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-06-02",
-      "license": null,
-      "build_status": "no-repository",
-      "selected": false,
-      "selection_reason": "Announced only. No repository located as of 2026-09-04. Cataloged so the next session can check whether it shipped."
-    },
-    {
-      "id": "BRUCE-FW",
-      "title": "Bruce firmware (r/brucefw enquiry)",
-      "author": "Bruce project",
-      "source_class": "community",
-      "canonical_url": "https://old.reddit.com/r/brucefw/comments/1oduhp0/",
-      "retrieved": "2026-09-04",
-      "last_activity": "2025-10-23",
-      "license": null,
-      "build_status": "not-applicable",
-      "selected": false,
-      "selection_reason": "REJECTED \u2014 wrong architecture. Bruce is ESP32-only; the K230 is RISC-V. Recorded as a refuted association so it is not re-investigated."
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/lilygo/t-display-k230/examples/search-log.md b/devices/lilygo/t-display-k230/examples/search-log.md
deleted file mode 100644
index 191716f..0000000
--- a/devices/lilygo/t-display-k230/examples/search-log.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# T-Display K230 — example search log
-
-**Date: 2026-09-04.** Scope, queries and dispositions for the example survey.
-
-## Scope
-
-"Examples" for this board means something different from an ESP32 board. There is **no library,
-no `examples/` directory and no set of sketches** — the board's software is a single Buildroot
-system image with one large LVGL application. The useful unit of study is therefore an
-**application module inside the launcher**, a **build script**, or a **companion-MCU firmware
-project**, not a standalone sketch.
-
-## Queries
-
-| # | Service | Query / method | Results | Disposition |
-|---|---|---|---|---|
-| 1 | GitHub | `search/repositories?q=org:Xinyuan-LilyGO+K230` | 4 | all cataloged |
-| 2 | GitHub | Full org listing (254 repos), filtered `k230\|k256\|canmv\|kendryte` | 4 | same 4; no others |
-| 3 | GitHub tree | `T-Display-K230` @ `bb831ab…` recursive, 624 blobs | ~50 launcher modules | cataloged by function |
-| 4 | GitHub tree | `T-Display-K230-nRF52840` @ `4646a72…`, 32 blobs | 1 firmware project + tools | cataloged |
-| 5 | GitHub tree | `T-Display-K230-nRF9151` @ `ed4ecbe…`, 40 blobs | 2 firmware profiles | cataloged |
-| 6 | GitHub | `kendryte/k230_docs` tree | ~15 demo/tutorial documents | cataloged as chip-level, not board-level |
-| 7 | GitHub | `oreboot/oreboot`, `intx82/k230-debian`, `kendryte/canmv_k230`, `sipeed/MaixPy` | 4 | cataloged; **none has a board profile** |
-| 8 | Reddit | 3 searches + 4 thread fetches | 1 announced project (Meshtastic UI), 1 tool (`kendryte_boot`) | cataloged, no repository located |
-| 9 | CNX-Software | site search `K230` | 5, **none about this board** | rejected — wrong product |
-
-## Explicitly not done
-
-- **`T-Display-K230_canmv_rt` was not cloned.** 745 MB, 25★, created 2025-03-05, last push
-  2026-08-03. **This is the largest known gap in the example survey** and should be the first
-  thing a follow-up session examines.
-- No example was **built**. No Ubuntu host and no XuanTie toolchain were available. Zero
-  build-tested examples, stated plainly.
-- Chinese-language project sites were not searched.
-- GitHub issue and discussion threads on the four LilyGO repositories were not read.
-
-## Stopping criterion
-
-Passes 1 and 2 converged on the same four repositories; pass 3–5 enumerated their contents
-exhaustively at pinned commits. A third broad pass produced only duplicates.
diff --git a/devices/lilygo/t-display-k230/factory-firmware.md b/devices/lilygo/t-display-k230/factory-firmware.md
deleted file mode 100644
index 6ceb4a1..0000000
--- a/devices/lilygo/t-display-k230/factory-firmware.md
+++ /dev/null
@@ -1,111 +0,0 @@
-# T-Display K230 — images, flashing and recovery
-
-**Evidence status: `reported-working` / `inferred`. Nothing here was executed.** The recovery
-section in particular is assembled from primary documents and one community report, and is
-labelled per claim.
-
----
-
-## 1. There is no factory firmware binary
-
-LilyGO publishes **no prebuilt image** for the T-Display K230. The repository states plainly:
-
-> "Generated image files under `k230_bsp/images/` are local build artifacts."
-
-The supported path is: build `sysimage-sdcard.img` yourself ([`development.md`](development.md)),
-or take a **Canaan** prebuilt image from `developer.canaan-creative.com` → *K230* → *Images* —
-which will boot a generic K230 Linux but will not drive this board's AMOLED, touch, keyboard or
-radio, because all of that is in LilyGO's overlay.
-
-This is a real gap. A user who bricks a board cannot download a known-good image; they must be
-able to build one. Combined with the 17-month gap between the board going on sale and the BSP
-being published, it explains the early-owner experience described in
-[`community.md`](community.md).
-
-## 2. Image format and layout
-
-| Property | Value |
-|---|---|
-| Artifact | `k230_bsp/images/sysimage-sdcard.img` |
-| Type | Whole-disk image, written with `dd` |
-| Generator | Buildroot `genimage` — config at `board/canaan/k230-soc/genimage.cfg` (1 280 bytes) |
-| Post-image script | `board/canaan/k230-soc/post-image.sh` (9 836 bytes) |
-| Post-build script | `board/canaan/k230-soc/post-build.sh` (4 257 bytes) |
-| Filesystems | Linux partitions plus a small FAT-ish region — Windows offers to format one after writing; **cancel that prompt** |
-| Boot medium | **microSD**, MMC1 on `GPIO54`–`GPIO59` |
-| Expansion | BSP v0.2.4 added "storage expansion settings for SD cards larger than the flashed image" — before that, a 64 GB card gave you the image's size and no more |
-
-Exact partition offsets were not extracted, because the image is not published and could not be
-built. Read `genimage.cfg` at the pinned commit for the authoritative layout.
-
-## 3. Companion-MCU firmware — the only prebuilt binaries LilyGO ships
-
-Both live in the companion repositories, not in the board repository.
-
-| Artifact | Repo / commit | Bytes | Target | Role |
-|---|---|---:|---|---|
-| `bootloader/k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex` | `T-Display-K230-nRF52840` @ `4646a728580739d487126f47a521e9b8032b3c2c` | 525 680 | **nRF52840** | Bootloader with **UART DFU @ 115200** and **SoftDevice S140 6.1.1** |
-| `firmware/k230_nrf52840_at_20260816_r4_k230_uart_dfu.uf2` | same | 296 960 | **nRF52840** | AT/BLE-Central application, build date **2026-08-16**, revision **r4**, UF2 family `0xADA52840` |
-
-Neither has a published SHA-256 from LilyGO. Both are reacquirable from the pinned commit:
-`https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c/<path>`.
-Full provenance in [`acquisition/manifest.json`](acquisition/manifest.json).
-
-nRF9151 firmware is **source-only** — build `tfm_merged.hex` yourself. Note that it contains
-TF-M plus the non-secure application and **does not update the modem firmware package**
-(`mfw_nrf91x1_*.zip`), which is a separate signed image.
-
-## 4. Flashing
-
-See [`development.md` §3](development.md#3-flashing-the-sd-card). Summary: `dd` on Linux/macOS,
-**Rufus in DD Image mode** on Windows.
-
-## 5. Recovery — what is known and what is not
-
-### 5.1 The failure that is actually reported
-
-r/LilyGO, **2026-08-21 and 2026-08-28**, u/phirzcolru, **firsthand ownership**:
-
-> "extensive attempts to work with this device. i managed to get an mp3 player and notepad
-> working for it. but once i attempted to turn on the 'fun' features it bricked it. its not
-> quite user friendly."
-
-> "my board is **still unresponsive to boot pin and term**. I think I **flashed it into mmc mode
-> vs sd card** and it's stuck."
-
-LilyGO's reply pointed at the GitHub repository and the wiki. **Neither contains a recovery
-procedure.** The user did not report recovering.
-
-### 5.2 What the silicon offers — `inferred` from primary documents
-
-The K230 boot ROM supports **USB boot**, and this is the lever that should exist:
-
-| Route | Source | Status |
-|---|---|---|
-| **Canaan `k230_burntool`** | `K230_SDK_Burntool_User_Guide.md` in `kendryte/k230_docs` | Canaan's own flashing/recovery utility. **Not tested here.** Guide not retrieved in this pass. |
-| **oreboot + `kendryte_boot`** | oreboot maintainer u/CyReVolt, r/LilyGO 2025-03-26: oreboot supports K230 and "can **boot Linux from mask ROM over USB in 3 seconds**"; `kendryte_boot` is on GitHub | **Demonstrable project**, stated by its author, with a video demo. The most promising documented path back into a board whose SD boot is broken. |
-| **BOOT0/BOOT1 straps** | `IO0` = BOOT0, `IO1` = BOOT1 in the Canaan reference DTS; the pin map documents the BOOT0 **button** on `GPIO0`, idle high / pressed low | The strap pins exist and the button is on one of them. **How the strap combinations map to boot media is not documented by either vendor**, which is precisely why the reported failure was unrecoverable for that user. |
-
-### 5.3 Honest statement of the gap
-
-**There is no vendor-documented recovery procedure for this board.** Not in LilyGO's README, not
-in the wiki, not in the BSP, not in the Quick Start. The recommended action for anyone about to
-change boot configuration is:
-
-1. Read `K230_SDK_Burntool_User_Guide.md` **before** you need it.
-2. Have `kendryte_boot` and the oreboot K230 target built and tested **before** you need them.
-3. Keep a known-good SD image.
-
-Marked `not-tested`. Anyone who executes one of these successfully should replace this section
-with an `executed-success` procedure.
-
-## 6. Bricking risks, ranked
-
-| Risk | Severity | Notes |
-|---|---|---|
-| Changing boot medium (SD ↔ eMMC/MMC mode) | **High** | The one confirmed brick |
-| Wrong IO bank voltage in a custom device tree | **High — physical damage** | Canaan: "will damage the chip" |
-| Interrupting an nRF52840 UART DFU | Medium | UART DFU bootloader should survive; USB/UF2 DFU is the fallback |
-| Writing a mismatched U-Boot | Medium | Boot ROM USB path should still exist |
-| SD card removal during write | Low | Reflash the card |
-| nRF9151 TF-M/modem confusion | Low–Medium | Application flash does not touch modem firmware; SWD recovers |
diff --git a/devices/lilygo/t-display-k230/features/README.md b/devices/lilygo/t-display-k230/features/README.md
deleted file mode 100644
index 172d6ae..0000000
--- a/devices/lilygo/t-display-k230/features/README.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# T-Display K230 — feature guides
-
-One guide per fitted capability. Each answers a natural question, names the exact hardware path
-through linked component records, and states its own evidence status.
-
-**Repository-wide caveat for every guide here: nothing was executed on hardware.** The highest
-evidence class reached anywhere in this set is `reported-working` — i.e. LilyGO's shipped BSP
-does it, and the source that does it is cited.
-
-| Guide | Question it answers | Hardware |
-|---|---|---|
-| [display.md](display.md) | How do I drive the AMOLED? | RM69A10 + K230 MIPI DSI |
-| [touch.md](touch.md) | How do I read touch? | GT9895 |
-| [keyboard.md](keyboard.md) | How do I read the QWERTY keyboard and its backlight? | TCA8418 + XL9555 |
-| [camera.md](camera.md) | How do I capture and process images? | GC2093 + K230 ISP |
-| [kpu-npu.md](kpu-npu.md) | How do I run a neural network on the NPU? | K230 KPU + nncase |
-| [dual-core-riscv.md](dual-core-riscv.md) | How do the two RISC-V cores work, and how do I use RVV? | K230 CPU0/CPU1 |
-| [wifi-and-bluetooth.md](wifi-and-bluetooth.md) | How do I get on Wi-Fi? Why is there no Bluetooth? | RTL8189FS + USB dongle |
-| [ethernet.md](ethernet.md) | How do I use the RJ45? | USB Ethernet |
-| [lora.md](lora.md) | How do I send LoRa / run Meshtastic? | SX1262 or LR2021 |
-| [audio.md](audio.md) | How do I play and record audio? | K230 codec + MAX98357A |
-| [microsd.md](microsd.md) | How do I use the SD card? | K230 MMC1 |
-| [usb.md](usb.md) | How do I use USB host and gadget? | K230 USB 2.0 OTG ×2 |
-| [battery-and-power.md](battery-and-power.md) | How do I read battery and configure charging? | BQ25896 + BQ27220 + PMU |
-| [gpio-and-expansion.md](gpio-and-expansion.md) | What can I actually attach to the 40-pin header? | K230 GPIO/ADC/I²C/PWM |
-| [nrf52840-ble.md](nrf52840-ble.md) | How do I do BLE? | nRF52840 over UART1 |
-| [nrf9151-cellular-gnss.md](nrf9151-cellular-gnss.md) | How do I do cellular and GNSS? | nRF9151 over UART3 |
diff --git a/devices/lilygo/t-display-k230/features/audio.md b/devices/lilygo/t-display-k230/features/audio.md
deleted file mode 100644
index a0f6ad0..0000000
--- a/devices/lilygo/t-display-k230/features/audio.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# Audio — playback, capture and the two output paths
-
-**Question:** *How do I play sound and record from the microphone — and why is there no sound?*
-
-| | |
-|---|---|
-| On-chip | [K230](../../../../components/canaan/k230/README.md) audio codec: **2 DAC + 2 ADC channels, 8–192 kHz**, ALC, up to **8 PDM DMICs**, I²S with 2×2 expansion |
-| External amp | [MAX98357A](../../../../components/analog-devices/max98357a/README.md) on the **nRF52840 base board** |
-| I²S pins | data `GPIO35`, BCLK `GPIO32`, LRCK `GPIO33`, shutdown `GPIO34` (**high = on**) |
-| Analogue out | 3.5 mm jack (Cased Version) |
-| Speaker / microphone parts | **unidentified** — [`unidentified/t-display-k230`](../../../../components/unidentified/t-display-k230/README.md) U2, U3 |
-| Userspace | **ALSA** (`amixer`, `aplay`) |
-| Evidence | `reported-working` |
-
-## Two output paths, and this is the usual cause of silence
-
-The K230 has an **on-die codec** that can drive the headphone jack directly, *and* an I²S output
-that feeds the MAX98357A on the expansion base. They are different sinks and the BSP adds an
-explicit route switch to choose between them:
-
-- `0059-asoc-canaan-add-external-i2s-output-switch.patch`
-- `0058-riscv-dts-rm69a10-add-audio-fan-sensor-pins.patch` (pin muxing)
-
-**If there is no sound, check the route before anything else.** Then check `GPIO34` — the
-MAX98357A is in shutdown when that line is low.
-
-## Playing and recording
-
-```sh
-aplay -l                     # list playback devices
-aplay -D <dev> file.wav
-amixer                       # the route switch and volumes live here
-arecord -D <dev> -f S16_LE -r 16000 out.wav
-```
-
-Buildroot builds `alsa-utils` with `amixer` and `aplay`
-(`BR2_PACKAGE_ALSA_UTILS_AMIXER`, `_APLAY`), plus Canaan's `audio_demo`
-(`BR2_PACKAGE_AUDIO_DEMO`) and `audio_rec_play` (`BR2_PACKAGE_AUDIO_REC_PLAY`).
-
-Launcher apps: music player, network radio, recorder, video player,
-`ui_audio.c`, `ui_i2s_test.c`, `ui_mic_spectrum.c`, `pcm_volume.c`.
-
-## Microphone
-
-A microphone exists (wiki, and the launcher's mic spectrum and Xiaozhi wake-word features).
-**Whether it is PDM or analogue is unknown** — the K230 supports both, up to 8 PDM DMICs or 2 ADC
-channels. See U3 in the unidentified-parts record.
-
-**Ownership matters:** *"Wake-word listening is active only while the Xiaozhi app is open and
-owns the microphone."* One consumer at a time, arbitrated in the launcher only.
-
-## Alternatives
-
-| Route | When |
-|---|---|
-| On-chip codec → 3.5 mm | Headphones, line out. No extra hardware. |
-| On-chip I²S → MAX98357A | Speaker on the nRF52840 base. Louder, mono, needs the base board. |
-| PDM DMIC | Up to 8, board fits fewer. |
-| USB audio | Possible via the USB host port; untested. |
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Sample rates | 8–192 kHz | silicon |
-| DAC / ADC | 2 / 2 | silicon |
-| PDM DMICs | 8 max | silicon |
-| MAX98357A | mono, 3.2 W into 4 Ω @ 5 V | component |
-| Simultaneous I²S-out + PDM-in | supported by the SoC; **untested on this board** | silicon / unmeasured |
-| Measured SNR, output power, latency | **none published** | unmeasured |
-
-## Pitfalls
-
-1. Wrong route → silence with no error.
-2. `GPIO34` low → amplifier in shutdown.
-3. The MAX98357A is on the **nRF52840 base**, not the bare board or the keyboard base.
-4. `0058` mentions "fan" pins alongside audio — a fan header may exist on some variant. The
-   launcher has `K230_FAN_ENABLED 0`. Unverified.
diff --git a/devices/lilygo/t-display-k230/features/battery-and-power.md b/devices/lilygo/t-display-k230/features/battery-and-power.md
deleted file mode 100644
index 28de718..0000000
--- a/devices/lilygo/t-display-k230/features/battery-and-power.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Battery and power
-
-**Question:** *How do I read battery state, configure charging, and stop it shutting down at the
-wrong voltage?*
-
-| | |
-|---|---|
-| Charger | [TI BQ25896](../../../../components/texas-instruments/bq25896/README.md), I²C4, **`0x6B`** |
-| Fuel gauge | [TI BQ27220](../../../../components/texas-instruments/bq27220/README.md), I²C4, **`0x55`** |
-| Cell | **21700** in the keyboard-base compartment |
-| 5 V boost | enabled by the **nRF52840's `P0.04`** |
-| Power key | K230 **PMU INT0**, `GPIO64`, driver `k230-pmu-pwrkey` |
-| USB in | 5 V, 500 mA |
-| PMIC | **unidentified** ([U1](../../../../components/unidentified/t-display-k230/README.md)) |
-| Evidence | `reported-working` |
-
-## The chain
-
-```
-USB-C 5V/500mA ──► BQ25896 charger (0x6B) ──► 21700 cell ──► BQ27220 gauge (0x55)
-                                                 │
-                                                 └─► 5V boost  ◄── enabled by nRF52840 P0.04
-                                                          │
-                                                          └─► main unit
-```
-
-**Note what that means:** on a kit configuration the **companion MCU on an expansion board
-controls the rail that powers the main unit from the battery.** If the nRF52840 is wedged or
-mid-DFU, that is a power dependency, not just a comms one.
-
-## Reading state
-
-Both chips are on the shared I²C4 bus and are treated as **optional, runtime-detected** hardware
-— a bare `K256` board has neither. The launcher's `ui_power_manager.c` and `ui_hardware.c`
-poll the gauge for voltage (mV), current (mA) and state of charge (%), and the charger for
-USB-present and charging status.
-
-## Low-battery shutdown is a userspace policy
-
-Not a hardware cut-off. In `ui_hardware.c`:
-
-- a millivolt threshold, compared against the gauge reading
-- `BATTERY_LOW_SHUTDOWN_CONFIRM_COUNT` consecutive low readings before acting
-- gated on charger USB-present, and it logs a "low-shutdown recovered" line when the condition
-  clears
-
-BSP **v0.2.3** "set the default low-battery shutdown threshold"; **v0.2.2** "improved first-run
-charger, battery, and low-voltage shutdown defaults". Both are evidence this was tuned after
-release — if you are on an older image, the defaults may be wrong.
-
-**Anything that blocks I²C4 blinds this policy.** See
-[`resources-and-conflicts.md`](../resources-and-conflicts.md).
-
-## The power key
-
-Not a normal GPIO. `GPIO64` is PMU input channel 0, **idle low, pressed high** — the opposite
-polarity to the BOOT0 button on `GPIO0`. It reaches userspace through
-`0064-input-k230-pmu-pwrkey.patch` (21 523 bytes), whose register flow "mirrors the RT-Thread PMU
-pwrkey driver": route PMU `KEY_EDGE` to **CPU IRQ 175**, rising-edge detect, and on shutdown
-program INT0 long-press wakeup and ask the PMU to cut power.
-
-Launcher constants: long-press **96 000** ticks, debounce **256** ticks.
-
-Full register list: [`pinouts-and-buses.md` §9](../pinouts-and-buses.md#9-pmu-power-key-register-flow).
-Canaan's `K230_PMU_User_Guide.md` is retained under the
-[K230 component](../../../../components/canaan/k230/artifacts/K230_PMU_User_Guide.md).
-
-## Thermal
-
-`CONFIG_CANAAN_THERMAL=y` plus `0063-thermal-canaan-convert-k230-tsensor-raw.patch` give an
-on-die temperature sensor. The launcher exposes it. `K230_FAN_ENABLED 0` and a "fan" mention in
-`0058-riscv-dts-rm69a10-add-audio-fan-sensor-pins.patch` suggest a fan header on some variant —
-**unverified**.
-
-## Limits and unknowns
-
-| Item | Status |
-|---|---|
-| Cell capacity, chemistry, protection IC | **unknown** ([U6](../../../../components/unidentified/t-display-k230/README.md)) |
-| PMIC | **unknown** |
-| Battery life under any workload | **never measured or published** |
-| Idle / suspend current | **unknown** |
-| Deep-sleep support on this board | K230 silicon claims ≤ 20 µW standby; **nothing on this board demonstrates it** |
-| Charge current setting | BQ25896 is capable of 3 A; input is 500 mA |
-
-Community scepticism is on record and unanswered: *"the battery life on this would be less than
-it would be with just a phone and a regular nRF node on a 1000mAh battery"* (2025-07-07,
-opinion). Nobody has published a measurement either way. This is the **largest single evidence
-gap** about the product.
diff --git a/devices/lilygo/t-display-k230/features/camera.md b/devices/lilygo/t-display-k230/features/camera.md
deleted file mode 100644
index dc34339..0000000
--- a/devices/lilygo/t-display-k230/features/camera.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Camera — GC2093 2 MP over MIPI CSI
-
-**Question:** *How do I capture, stream and run vision on the camera?*
-
-| | |
-|---|---|
-| Sensor | [GalaxyCore GC2093](../../../../components/galaxycore/gc2093/README.md), 2 MP 1080p |
-| Data | K230 **MIPI CSI-2** |
-| Control | I²C0 — `GPIO49` SDA / `GPIO48` SCL, **`0x37`** |
-| ISP | K230 on-chip ISP, **8 MP @ 30 fps** total throughput, 3A / 2DNR / 3DNR / WDR / HDR / LTM / de-warp / RGB-IR |
-| Stack | Canaan **`vvcam`** (VeriSilicon ISP) → V4L2 |
-| Evidence | `reported-working` |
-
-## Software
-
-`BR2_PACKAGE_VVCAM=y` with `BR2_PACKAGE_VVCAM_DEF_SENSOR="gc2093"`. The sensor driver is
-`vvcam/src/gc2093.c` (26 213 bytes); board integration is `0036-add-gc2093-camera.patch`. A V4L2
-↔ DRM shim lives at `vvcam/v4l2-drm/src/lib.c` (21 372 bytes), and the MIPI driver is
-`vvcam/mipi/vvcam_mipi_driver.c` (16 697 bytes).
-
-Because it goes through `vvcam` rather than a plain V4L2 subdev, **the tuning surface is the ISP,
-not the sensor driver.** Canaan's relevant documents are `K230_ISP_Image_Tuning_Guide`,
-`K230_ISP_Initial_Setting_Guide`, `K230_VICAP_API_Reference` and
-`K230_VICAP_SENSOR_Parameter_Partition_Reference`.
-
-## What is already built and working
-
-| Capability | Where |
-|---|---|
-| Preview + still capture | `camera_capture.c` (28 230 bytes) |
-| **Face detection** | `camera_face_detect.cpp`, `BR2_PACKAGE_FACE_DETECT=y` — KPU-accelerated |
-| **QR scanning** | `qr_scan.c` |
-| **RTSP push** | `BR2_PACKAGE_CAMERA_RTSP_DEMO=y`, `BR2_PACKAGE_LIB_RTSPSERVER=y` |
-| Motion probe | `drm_motion_probe.c` |
-| Camera over LoRa FLRC | `k230_flrc_camera_stream.sh` |
-| Camera over HaLow | `k230_halow_camera_stream.sh`, `halow_udp_stream.c` |
-| UVC / OpenCV | Canaan `K230_Opencv_UVC_Usage_Guide`, `BR2_PACKAGE_*` OpenCV guides |
-
-The **FLRC camera stream** is worth calling out: streaming images over a LoRa-family modulation
-is unusual, and it is the concrete reason LilyGO gates Meshtastic photo transfer on LR2021
-hardware.
-
-## Adding a second or third camera
-
-The K230 has **three MIPI CSI inputs** — (1 × 4-lane + 1 × 2-lane) or 3 × 2-lane. Only one is
-populated. Canaan's reference DTS references `OV5647` and the tree mentions `IMX219`, so those
-two are the least-effort additions. Procedure:
-`K230_Image_Capture_Practice_How_to_support_a_new_sensor` and
-`K230_Camera_Sensor_Adaptation_Guide`.
-
-A community comment on the launch thread got this right: *"It might support two more cams. Might
-be able to wrap their tethers around a tree and have a 360 degree view."*
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| CSI inputs | 3 | silicon |
-| ISP throughput | 8 MP @ 30 fps | silicon |
-| Encode | H.264/H.265/JPEG, 8 MP @ 20 fps | silicon |
-| Decode | 8 MP @ 40 fps | silicon |
-| Fitted sensor | 2 MP 1080p | board |
-| Sensor lane count, link rate, HDR modes | **unknown** | [`GC-6`](../gaps-and-conflicts.md) |
-| Measured capture latency / fps on this board | **none published** | unmeasured |
-
-## Pitfalls
-
-1. `0x37` is unusual for an image sensor — do not assume `0x3C`.
-2. The camera has its **own** I²C bus, so it is not affected by keyboard-base bus problems.
-3. ISP tuning is a real project. Canaan ships a PC-side tuning tool for a reason.
-4. **nncase version must match the SDK** for KPU-accelerated vision, or you get a runtime failure.
diff --git a/devices/lilygo/t-display-k230/features/display.md b/devices/lilygo/t-display-k230/features/display.md
deleted file mode 100644
index e44c619..0000000
--- a/devices/lilygo/t-display-k230/features/display.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# Display — 4.1″ AMOLED, 568 × 1232
-
-**Question:** *How do I draw on the screen, control brightness, and stop the boot logo from
-fighting the kernel?*
-
-| | |
-|---|---|
-| Panel driver IC | [Raydium RM69A10](../../../../components/raydium/rm69a10/README.md) |
-| SoC path | [K230](../../../../components/canaan/k230/README.md) **MIPI DSI**, 2-lane, video mode, **burst** |
-| Resolution | RGB **568 × 1232**, 4.1 inch |
-| Control pins | `GPIO22` reset · `GPIO25` enable |
-| Backlight | **DSI command**, not PWM |
-| Applicable revision | all SKUs `K256*`, `K277` |
-| Evidence | `reported-working` — LilyGO BSP; **not** hardware-verified here |
-
-## Hardware path
-
-K230 MIPI DSI (the SoC's **only** DSI output) → RM69A10 → AMOLED. Because there is exactly one
-DSI, the [LT9611 HDMI bridge](../../../../components/lontium/lt9611/README.md) is a **boot-time
-alternative**, never a second head — see [`resources-and-conflicts.md`](../resources-and-conflicts.md) HC-1.
-
-## Software stack
-
-Standard Linux DRM/KMS. Panel driver is Canaan's **`panel-canaan-universal`** — there is no
-upstream `panel-raydium-*` for this part, and no upstream `compatible` string. Userspace is
-**LVGL** through the DRM backend.
-
-LVGL is pinned in Buildroot at upstream commit `59dc7e436ae97a25e32656739ea6a943f9f11b6a` with
-four LilyGO patches, two of which are display-related:
-
-- `0002-lvgl-linux-drm-add-k230-plane-rotation.patch`
-- `0004-lvgl-drm-add-k230-staging-scanout-buffer.patch`
-
-## Minimal procedure
-
-The panel is already up when Linux hands off to userspace. To draw:
-
-1. Open the DRM device and pick the connector the RM69A10 is on.
-2. **Use RGB565.** LilyGO: *"The validated LVGL path uses RGB565 for stable refresh."* XRGB8888
-   works (added by `0026-drm-canaan-vo-add-xrgb8888-format.patch`) but is not the validated path.
-3. For rotation, use the **GDMA** engine rather than CPU rotation —
-   `0035-gdma-xrgb8888-rotation.patch` and the LVGL plane-rotation patch exist for exactly this.
-
-Diagnostics already on the board: launcher → **Display Test** (`ui_display_test.c`),
-`drm_motion_probe.c`, `lvgl_scroll_probe.c`.
-
-## Resources consumed
-
-MIPI DSI (all of it), `GPIO22`, `GPIO25`, one DRM plane, and a framebuffer. A 568 × 1232 RGB565
-framebuffer is **1.40 MB**; double-buffered, 2.80 MB. Against 1 GB of LPDDR4 that is
-inconsequential — unlike on an MCU-class part.
-
-## Alternatives and decision table
-
-| Approach | When |
-|---|---|
-| **LVGL over DRM** (LilyGO's) | Default. Widgets, fonts, input integration all done. |
-| Raw DRM/KMS + your own drawing | You want full control or a different UI toolkit. |
-| Framebuffer (`/dev/fb0`) | `DRM_FBDEV_EMULATION`, `FB` and `FRAMEBUFFER_CONSOLE` are all enabled, so a legacy fbdev app works. Simplest, slowest. |
-| Console on the panel | `getty-tty1-rm69a10` in the rootfs overlay puts a login shell on the AMOLED with the `TER16x32` font. Genuinely useful for bring-up. |
-| **HDMI via LT9611** | Diagnostics only; requires the `-hdmi` device tree and gives up the AMOLED. |
-
-## Initialisation, teardown, handoff
-
-**The boot-logo handoff is the fiddly part** and three patches exist for it:
-
-- `0038-reserve-rm69a10-uboot-logo-fb` — reserve the U-Boot framebuffer so Linux does not stomp it
-- `0051-drm-canaan-preserve-rm69a10-boot-splash-handoff` — keep the splash across the handoff
-- `0043-drm-canaan-defer-vo-config-load-to-vblank` — load video-output config on vblank
-
-U-Boot draws the logo itself: `display_logo.c` (32 KB), `k230_logo.c`, plus `logo.xrgb` (2.8 MB)
-and `logo.yuv` (1.0 MB) in the rootfs overlay. If you rebuild U-Boot without the overlay you get
-a blank screen until the kernel comes up.
-
-`0027-panel-canaan-universal-enable-reset-in-prepare` moves panel reset into `prepare` — without
-it the panel does not come up reliably.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| DSI output count | **1** | silicon |
-| Max DSI resolution | 2 MP @ 60 fps | silicon |
-| Panel | 568 × 1232 fixed | board |
-| Validated colour format | RGB565 | framework/board (LilyGO's word) |
-| Refresh rate | not published | **unknown** |
-| Brightness range/steps | not published | **unknown** |
-| Measured frame rate | none published | **unmeasured** |
-
-## Pitfalls
-
-1. **Do not look for a backlight PWM for the panel.** `GPIO52`/PWM4 is the **keyboard** backlight.
-2. Rebuilding without the display patch set gives flicker, a black handoff, or a dead panel.
-3. Video mode must be **burst** (`0029-drm-canaan-fix-video-mode-to-burst`).
-4. Colour swap bugs were real and are fixed by patch — `0030` (XRGB8888 opaque + RB swap) and
-   `0033` (RGB2YUV colour swap). If you port to a different kernel, expect them back.
-
-## Unresolved
-
-Refresh rate, brightness curve, panel module vendor, actual measured LVGL frame rate. See
-[`GC-5`](../gaps-and-conflicts.md).
diff --git a/devices/lilygo/t-display-k230/features/dual-core-riscv.md b/devices/lilygo/t-display-k230/features/dual-core-riscv.md
deleted file mode 100644
index 866a949..0000000
--- a/devices/lilygo/t-display-k230/features/dual-core-riscv.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# The two RISC-V cores, RVV, and what "small core" means
-
-**Question:** *There are two cores with different capabilities — which is which, which one runs
-my code, and how do I use the vector unit?*
-
-| | CPU 1 — "big core" | CPU 0 — "little/small core" |
-|---|---|---|
-| Clock | **1.6 GHz** | **800 MHz** |
-| ISA | RV64 + **RVV 1.0**, 128-bit VPU | **RV64GCB** — no vector |
-| L2 | 256 KB | 128 KB |
-| L1 | 32 KB I + 32 KB D | 32 KB I + 32 KB D |
-| MMU / FPU / PLIC (208 sources) / JTAG | yes | yes |
-| Canaan's intended OS | **RTOS** (RT-Smart) | **Linux** |
-
-Both are **XuanTie C908** cores. Evidence: Canaan K230 datasheet and brief datasheet.
-
-## Three things people get wrong
-
-**1. Only CPU1 has the vector unit.** Vector code traps on CPU0. Every RVV-accelerated library —
-OpenBLAS RVV kernels, vectorised OpenCV, nncase vector paths — is a CPU1 story.
-
-**2. There is no third core.** The K230 has exactly two CPU subsystems. Where you see "two cores
-plus a small core", the "small core" **is CPU0** — that is Canaan's own name for it (小核), in
-contrast to CPU1, the big core (大核). The **PMU is fixed-function hardware**: a 32 kHz RTC, six
-inputs, two outputs, long/short-press detection and a 512-bit shutdown log. It is not
-programmable. Contrast the [ESP32-P4](../../../../components/espressif/esp32-p4/README.md), which
-genuinely does have a third 40 MHz RISC-V core on a retained power domain with its own
-peripherals — the K230 has no equivalent.
-
-**3. It is not an SMP pair.** Two independent L2 caches, two independent PLICs, and in Canaan's
-dual-OS SDK **two different operating systems** with an explicit IPC API
-(`K230_Inter_Processer_Communication_API_Reference`) and a `sharefs` mechanism. You do not
-schedule a Linux thread onto CPU1.
-
-## On *this board*, specifically
-
-LilyGO builds from **`kendryte/k230_linux_sdk`**, which is the **Linux-only** SDK. So the dual-OS
-arrangement above is not what this board ships. What exactly runs on CPU1 in the Linux-only
-configuration was **not established** in this pass — see [`GC-1`](../gaps-and-conflicts.md) —
-and `cat /proc/cpuinfo` on a running unit settles it in one command.
-
-⚠ LilyGO's wiki FAQ states the opposite of Canaan's datasheet ("big core runs Linux, little core
-runs RT-Thread"). **Canaan is primary; the wiki is wrong.**
-
-## Using RVV
-
-The Buildroot target flags are:
-
-```
-BR2_TARGET_OPTIMIZATION="-mcpu=c908v -mtune=c908 -mrvv-v0p10-compatible -mrvv-auto-vectorize"
-BR2_RISCV_ISA_RVV=y
-BR2_RISCV_ISA_RVC=y
-```
-
-Three consequences:
-
-1. **`-mcpu=c908v` is XuanTie-specific.** Mainline GCC does not accept it.
-2. **`-mrvv-v0p10-compatible` targets draft RVV 0.10**, not ratified 1.0, even though the core
-   implements 1.0. Binaries are **not** interchangeable with mainline RVV-1.0 output.
-3. `-mrvv-auto-vectorize` is on, so ordinary C gets auto-vectorised for CPU1.
-
-Canaan's own tutorials, retained locally:
-[`K230_RVV_In_Action.md`](../../../../components/canaan/k230/artifacts/K230_RVV_In_Action.md) and
-[`K230_RVV_optimization_performance_description.md`](../../../../components/canaan/k230/artifacts/K230_RVV_optimization_performance_description.md).
-
-## DVFS
-
-CPU1 and the KPU both support DVFS. When they share a clock source their frequencies change
-together; on separate sources they change independently. Frequency must match the current
-voltage — this is the PMIC's job, and the PMIC on this board is
-[unidentified](../../../../components/unidentified/t-display-k230/README.md).
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Vector length | 128-bit | silicon |
-| RVV version implemented | 1.0 | silicon |
-| RVV version the shipped toolchain targets | **0.10-compatible** | toolchain |
-| Cores | 2, no third | silicon |
-| CoreMark on this board | **built into the image, never published** | unmeasured |
-
-## Pitfalls
-
-1. Compiling with vector instructions and running on CPU0.
-2. Mixing mainline-RVV-1.0 and XuanTie-0p10-compatible binaries.
-3. Expecting an always-on core for sensor polling. There isn't one.
-4. Expecting `taskset` to move work to the fast core in a dual-OS configuration.
diff --git a/devices/lilygo/t-display-k230/features/ethernet.md b/devices/lilygo/t-display-k230/features/ethernet.md
deleted file mode 100644
index dd3c925..0000000
--- a/devices/lilygo/t-display-k230/features/ethernet.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# Ethernet — the RJ45
-
-**Question:** *There's an RJ45 on a handheld. How do I use it, and what is behind it?*
-
-| | |
-|---|---|
-| Interface | `eth0` |
-| Physical | RJ45, confirmed present by product photography and community observation |
-| Controller | **USB-attached.** Claimed [RTL8152B](../../../../components/realtek/rtl8152b/README.md), 100 Mbps, IEEE 802.3u |
-| Speed | **100 Mbit/s** |
-| Evidence | `reported-working` for `eth0`; the controller identity is **unresolved** — [`GC-3`](../gaps-and-conflicts.md) |
-
-## Why it is USB
-
-**The K230 has no Ethernet MAC.** A full-text search of Canaan's full and brief datasheets for
-`ethernet`, `gmac` and `rmii` on 2026-09-04 returned **zero matches**, and the peripheral list
-contains no Ethernet. Anything with an RJ45 on a K230 board is therefore behind a USB Ethernet
-controller.
-
-That is a genuine constraint dressed as a feature: 100 Mbit/s ceiling, and it occupies USB
-bandwidth shared with the Bluetooth dongle and any USB modem.
-
-## Using it
-
-The launcher's Ethernet page (`ui_ethernet.c`) does DHCP or static, persisted as preferences
-`ethernet.mode`, `ethernet.static_ip`, `ethernet.netmask`, `ethernet.gateway`, `ethernet.dns`.
-Underneath it is BusyBox:
-
-```sh
-ifconfig eth0 up
-udhcpc -i eth0 -p /var/run/udhcpc.eth0.pid          # DHCP
-# or static:
-ifconfig eth0 <ip> netmask <mask>
-route del default dev eth0
-route add default gw <gw> dev eth0
-```
-
-Buildroot's `BR2_SYSTEM_DHCP="eth0"` means DHCP on `eth0` is the boot default.
-
-Status is read from `/sys/class/net/eth0/` — `carrier`, `address` and the operational state.
-
-## The unresolved bit
-
-LilyGO's wiki says **RTL8152B**. LilyGO's shop says **"RC01812"**, which matches no Ethernet
-controller naming scheme and is most consistent with an RJ45 jack part number. And the BSP's
-kernel fragment enables the USB **CDC/RNDIS/NCM/MBIM/QMI** class drivers but **not**
-`CONFIG_USB_RTL8152`, which would be needed for an RTL8152B.
-
-Most likely `CONFIG_USB_RTL8152` is already in the base `k230` defconfig. **Settle it on hardware:**
-
-```sh
-readlink /sys/class/net/eth0/device/driver
-lsusb
-zcat /proc/config.gz | grep -i rtl8152
-```
-
-## Realistic uses
-
-The obvious one, from the launch thread: *"I can hot glue this to the back of a starlink dish and
-connect ethernet."* Reply: *"That's a bit of a waste of the screen. There are existing boards
-with Ethernet for that task."* Both fair. The port makes most sense as a **provisioning and
-recovery path** when Wi-Fi is unavailable — which, given SSH-based launcher deployment
-(`deploy_launcher.sh <ip>`), is exactly how a developer will use it.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Speed | 100 Mbit/s | board |
-| MAC | none on SoC | **silicon** |
-| PoE | none | board |
-| Measured throughput | **none published** | unmeasured |
diff --git a/devices/lilygo/t-display-k230/features/gpio-and-expansion.md b/devices/lilygo/t-display-k230/features/gpio-and-expansion.md
deleted file mode 100644
index 06739dc..0000000
--- a/devices/lilygo/t-display-k230/features/gpio-and-expansion.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# GPIO and the 40-pin expansion header
-
-**Question:** *What can I actually attach, and which pins are genuinely free?*
-
-| | |
-|---|---|
-| Header | 2 × 20, 40 pins |
-| SoC | [K230](../../../../components/canaan/k230/README.md): **64 GPIO + 8 PMU GPIO**, 5 UART, 5 I²C, 6 PWM, 3 SPI |
-| Tools on board | `linux-tools-gpio` (`gpioinfo`, `gpioget`, `gpioset`), `evtest`, launcher I²C scanner |
-| Evidence | `reported-working` for the map; electrical characteristics **unverified** |
-
-## Read this first: most of the header is already spoken for
-
-Full pinout: [`pinouts-and-buses.md` §1](../pinouts-and-buses.md#1-40-pin-expansion-header-2--20).
-Claimed by on-board or base-board functions:
-
-`GPIO2` nRF9151 enable · `GPIO3`/`GPIO4` nRF52840 UART · `GPIO5` LoRa reset ·
-`GPIO14`–`GPIO17`, `GPIO19`, `GPIO20`, `GPIO44` LoRa SPI · `GPIO28`/`GPIO29` nRF9151 UART ·
-`GPIO32`–`GPIO35` I²S · `GPIO42`/`GPIO43` keyboard IRQ/reset · `GPIO46`/`GPIO47` I²C4 ·
-`GPIO52` keyboard backlight PWM.
-
-**Genuinely uncommitted:** `GPIO6`, `GPIO18`, `GPIO26`, `GPIO27`, `GPIO30`, `GPIO31`, `GPIO45`,
-`GPIO53`, `GPIO62`, `GPIO63`, plus `ADC0`, `ADC1`, `ADC2`.
-
-That is **ten digital pins and three analogue inputs** on a fully populated kit. If you need
-more, drop a subsystem — not using LoRa frees seven pins, not using the nRF52840 base frees the
-I²S four.
-
-## Power on the header
-
-`5V`, `3V3`, two `GND`, and `USB-IN-5V`. No current limits are published.
-
-## ⚠ IO bank voltage — the way to destroy the chip
-
-The K230's IO banks have a **software-selected voltage** and Canaan's own reference device tree
-says, in a comment:
-
-> `// Please pay attention to the bank voltage! will damage the chip.`
-
-Reference-design settings: `IO0`–`IO1` fixed **1.8 V**; everything else **3.3 V**. Before
-attaching 1.8 V logic, read [`pinouts-and-buses.md` §6](../pinouts-and-buses.md#6-io-bank-voltages--the-hardware-damage-path).
-Changing a bank in the device tree changes it for the whole bank, including pins other things
-are using.
-
-## I²C4 is shared with power management
-
-Anything you hang on `GPIO46`/`GPIO47` shares a bus with the keyboard scanner, the charger and
-the fuel gauge. **Avoid `0x20`–`0x27`** — the XL9555 expander's address is strap-dependent and
-software-probed.
-
-## ADC
-
-Three analogue inputs are exposed. **The K230 brief datasheet's peripheral list does not
-enumerate an ADC**, so resolution, reference voltage, sample rate and input range are all
-unknown — [`GC-8`](../gaps-and-conflicts.md). Canaan's
-`K230_Big_Core_Low_Speed_Driver_API_Reference` is the place to look; it was retrieved but not
-mined in this pass.
-
-## PWM
-
-Six PWM channels in the SoC. **PWM4 is the keyboard backlight** on `GPIO52`. The others are
-available if their pins are.
-
-## Other expansion
-
-- **QWIIC** connector on the Cased Version (wiki) — a standard 4-pin I²C connector. Which bus it
-  is on is **not stated**; most plausibly I²C4. Unverified.
-- **nRF52840 GPIO expansion header** on the Cased Version (wiki).
-- **Two unused MIPI CSI inputs** — arguably the most valuable expansion on the board. See
-  [camera.md](camera.md).
-
-## Minimal procedure
-
-```sh
-gpioinfo                          # enumerate lines and current consumers
-gpioget gpiochip0 6
-gpioset gpiochip0 6=1
-i2cdetect -y 4                    # or use the launcher's async I2C Scan
-```
-
-Adafruit Blinka is built in (`BR2_PACKAGE_PYTHON_ADAFRUIT_BLINKA=y`), so CircuitPython-style
-Python drivers for I²C/SPI sensors are available. That is a genuinely convenient path and it is
-easy to miss.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Free digital pins on a full kit | ~10 | board |
-| ADC characteristics | **unknown** | unknown |
-| Header current limits | **unpublished** | unknown |
-| Max GPIO toggle rate | **unmeasured** | unmeasured |
-| PMU GPIO (8 of them, ≤ 25 MHz) | not exposed on the header | board |
diff --git a/devices/lilygo/t-display-k230/features/keyboard.md b/devices/lilygo/t-display-k230/features/keyboard.md
deleted file mode 100644
index 0a8aba5..0000000
--- a/devices/lilygo/t-display-k230/features/keyboard.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# Keyboard — TCA8418 QWERTY matrix, backlight and hotkeys
-
-**Question:** *How do I read the physical keyboard, remap the F-keys, and control the backlight?*
-
-| | |
-|---|---|
-| Scanner | [TI TCA8418](../../../../components/texas-instruments/tca8418/README.md) |
-| Bus / address | I²C4 (`GPIO46` SCL / `GPIO47` SDA), **`0x34`** |
-| RESET / IRQ | `GPIO43` / `GPIO42` |
-| Matrix | **7 ROW × 10 COL** configured; 6 × 11 displayed layout |
-| Backlight | **`GPIO52` / PWM4** |
-| Expander | [XL9555](../../../../components/xlsemi/xl9555/README.md), address **probed** in `0x20`–`0x27` |
-| Where | **nRF9151 keyboard base board** (kit SKUs `K256-04`, `K256-04-A`) — *not* on the bare board |
-| Evidence | `reported-working` |
-
-## The full key map
-
-Every key code, its label, and the physical layout are decoded in
-[`pinouts-and-buses.md` §8](../pinouts-and-buses.md#8-keyboard-matrix--full-decode). The things
-that will surprise you:
-
-- **Two `SPACE` codes** (`5` and `14`) — one wide bar across two intersections.
-- **Two `FN` keys** — `9` (left) and `3` (`FN-R`, right); either satisfies `FN`.
-- A dedicated **`LILYGO`** key (code `8`) and a dedicated **`MIC`** key (code `11`).
-- Arrows are scattered along the bottom two rows, not clustered: `UP` 22, `DOWN` 12, `LEFT` 2,
-  `RIGHT` 1.
-- **11 F-keys.**
-
-Code → matrix position: `row = (code-1)/10`, `col = (code-1)%10`.
-
-## Reading it
-
-The image ships `evtest`; the scanner appears as a Linux input device. In the launcher, keys are
-read through `ui_hardware.c`, which talks to the TCA8418 over I²C directly and maintains its own
-`keyboard_key_pressed[row][col]` state under a mutex.
-
-Registers used: `CFG 0x01`, `INT_STAT 0x02`, `KEY_LCK_EC 0x03`, `KEY_EVENT_A 0x04`,
-`KP_GPIO_1/2/3 0x1D/0x1E/0x1F`, `DEBOUNCE_DIS_1/2/3 0x29/0x2A/0x2B`. Config mode with IRQ
-(`K230_TCA8418_USE_IRQ 1`, default) is `KE_IEN | OVR_FLOW_IEN | OVR_FLOW_M`; without IRQ it is
-`OVR_FLOW_M` and the driver polls.
-
-**Repeat timing:** first repeat at **450 ms**, then every **85 ms**.
-
-## The IOMUX detail worth knowing
-
-The launcher **writes the K230 IOMUX register for `GPIO42` directly** —
-`TCA8418_IRQ_IOMUX_IO42_OFFSET = 42*4`, value `0x00000344` — to force GPIO-input mode. That is
-userspace reaching past the kernel pin controller. If another driver later claims and re-muxes
-`GPIO42`, the keyboard IRQ silently stops and the scanner falls back to nothing. If you see keys
-stop working after loading an unrelated driver, this is why.
-
-## Hotkeys and remapping
-
-- Preference keys `keyboard.hotkey.f1` … `keyboard.hotkey.f11`.
-- **v0.2.4 defaults:** `F3` / `F4` = keyboard backlight down / up, `F7` = screenshot.
-- `FN+B` toggles the backlight.
-- `keyboard.esc_back` (default on) makes `ESC` act as Back.
-- Hotkey activity is logged to `/tmp/k230_keyboard_hotkey.log`; an on-screen OSD shows for
-  ~950 ms with a 160 ms fade.
-
-## Backlight
-
-`GPIO52` on **PWM4**, driven from userspace. The reference pin configuration leaves `IO52` as
-**input with pull-down until userspace enables PWM4** — a deliberate safe default, and the reason
-the backlight is dark before the launcher starts.
-
-⚠ **This is the keyboard backlight, not the display backlight.** The AMOLED's brightness is a DSI
-command ([display.md](display.md)).
-
-## Auto-detection
-
-The keyboard base is optional and detected: `EXT_KEY_AUTO_DETECT_DEFAULT 1`, probe interval
-default **3 s** (range 3–30 s), `EXT_KEY_FAIL_LIMIT 5` consecutive failures before giving up.
-Queues: `EXT_KEY_QUEUE_SIZE 64`, `TCA8418_RAW_QUEUE_SIZE 96`.
-
-## Limits
-
-- **7 × 10 = 70 possible codes**; ~60 keys are named. Code `0` is not a key.
-- The TCA8418 supports up to 8 × 10; this board uses 7 rows.
-- Rollover behaviour: unstated. The launcher tracks a full pressed-state matrix, so multi-key
-  detection works at the software level.
-- `tca8414` appears twice in the tree — a probable typo, or fallback support. Unverified.
-
-## Pitfalls
-
-1. **The keyboard is a separate purchase.** No keyboard on `K256*` bare boards.
-2. Don't hard-code the XL9555 address; the software probes `0x20`–`0x27`.
-3. The keyboard shares I²C4 with the charger and gauge — a stuck bus takes out power management
-   too ([`resources-and-conflicts.md`](../resources-and-conflicts.md)).
-4. The keyboard base does **not** include a case for the main board (confirmed by an owner,
-   2026-08-13).
diff --git a/devices/lilygo/t-display-k230/features/kpu-npu.md b/devices/lilygo/t-display-k230/features/kpu-npu.md
deleted file mode 100644
index a0b51e8..0000000
--- a/devices/lilygo/t-display-k230/features/kpu-npu.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# KPU / NPU — running neural networks
-
-**Question:** *How do I run a model on the K230's AI accelerator, and what will it actually do?*
-
-| | |
-|---|---|
-| Accelerator | [K230](../../../../components/canaan/k230/README.md) **KPU**, INT8 + INT16, weight-sparse |
-| Compiler | **nncase** |
-| Dedicated SRAM | 2 MB (the second of two 2 MB blocks) |
-| On-board packages | `BR2_PACKAGE_LIBNNCASE=y`, `BR2_PACKAGE_FACE_DETECT=y`, `BR2_PACKAGE_AI2D_KPU=y` |
-| Evidence | `reported-working` for the shipped face-detect demo; everything else `not-tested` |
-
-## Published throughput — use these, not TOPS
-
-Canaan's datasheet gives three numbers and **no TOPS figure at all**:
-
-| Network | Throughput |
-|---|---|
-| ResNet-50 | **≥ 85 fps @ INT8** |
-| MobileNet v2 | **≥ 670 fps @ INT8** |
-| YOLOv5s | **≥ 38 fps @ INT8** |
-
-LilyGO's wiki says "**up to 1.6 TOPS**". A Reddit commenter said "**abt 17 tops**". Neither
-number appears in any Canaan document. **Quote the fps figures.**
-
-## Workflow
-
-1. Train wherever you like — supported import formats are **TensorFlow, PyTorch, TFLite,
-   PaddlePaddle, ONNX** (the brief datasheet lists TVM instead of TFLite/Paddle).
-2. Compile with **nncase**, quantising to INT8 or INT16. Canaan claims **< 1 %** accuracy loss.
-3. **Check the nncase ↔ SDK version table** — Canaan publishes
-   `K230_SDK_nncase_version_correspondence.md` precisely because mismatches fail *at runtime*,
-   not at build time. This is the number one KPU support issue.
-4. Deploy and run against `libnncase` on the board.
-5. Preprocess with the **AI 2D engine** (`BR2_PACKAGE_AI2D_KPU`) — affine, crop, resize, pad,
-   shift and colour-space conversion in hardware, with OpenCV-compatible rounding. Doing resize
-   and CSC on the CPU instead is the most common avoidable slowdown.
-
-Reference: [`K230_nncase_Development_Guide.md`](../../../../components/canaan/k230/artifacts/K230_nncase_Development_Guide.md)
-(81 128 bytes, retained locally).
-
-## Supported operators
-
-The full ONNX operator list Canaan commits to is reproduced verbatim in the
-[K230 component record §3](../../../../components/canaan/k230/README.md#3-kpunpu--capability-and-supported-operators).
-**Anything outside it falls back to CPU**, which on CPU0 at 800 MHz without vector instructions
-is slow. If a model is unexpectedly slow, check the operator list before blaming the hardware.
-
-## What ships working on this board
-
-- **Face detection** from the live camera (`camera_face_detect.cpp`, `BR2_PACKAGE_FACE_DETECT`)
-- An AI demo page (`ui_ai_demo.c`) and a `models/` directory in the launcher
-- QR scanning (classical CV, not the KPU)
-
-## Alternatives
-
-| Route | When |
-|---|---|
-| **nncase + KPU** | Anything real-time. The only path that uses the accelerator. |
-| **OpenCV on CPU1** | Classical CV. Canaan ships an OpenCV guide; CPU1 has RVV 1.0, so vectorised OpenCV is meaningful. |
-| **OpenBLAS with RVV kernels** | Dense linear algebra. Canaan ships `K230_OpenBLAS_Development_Guide`. |
-| **HHB (T-Head)** | Alternative deployment tool, documented in `K230_AI_in_Action_HHB_…`. |
-| CPU0 | Do not. No vector unit. |
-
-## Resources and conflicts
-
-The KPU has 2 MB of SRAM by default and can reach the **shared** 2 MB block as well, where it has
-priority over the AXI slaves. Sharing that block with the decompression engine and AI 2D work is
-a real bandwidth question at 1080p. No measurement exists.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Precision | INT8 / INT16 only — **no FP inference** | silicon |
-| Operators | fixed list; unsupported ops → CPU | silicon/toolchain |
-| Model size | bounded by 1 GB LPDDR4 in practice | board |
-| Measured performance on *this board* | **none** | unmeasured |
-| LLM-class workloads | not credible — INT8 CNN accelerator, 1 GB RAM | inferred |
-
-The launcher's **PicoClaw** chat app makes this explicit: it "requires network access and an
-OpenAI-compatible model API key". The board does not run the model.
-
-## Pitfalls
-
-1. nncase/SDK version mismatch — the single most common failure.
-2. Unsupported operators silently falling back to CPU.
-3. Doing preprocessing on the CPU instead of the AI 2D engine.
-4. Believing a TOPS number.
diff --git a/devices/lilygo/t-display-k230/features/lora.md b/devices/lilygo/t-display-k230/features/lora.md
deleted file mode 100644
index c8cf40b..0000000
--- a/devices/lilygo/t-display-k230/features/lora.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# LoRa — SX1262 or LR2021, and Meshtastic
-
-**Question:** *How do I send LoRa, and which radio should I buy?*
-
-| | |
-|---|---|
-| Radio (option A) | [Semtech SX1262](../../../../components/semtech/sx1262/README.md) |
-| Radio (option B) | [Semtech LR2021](../../../../components/semtech/lr2021/README.md), 830–940 MHz |
-| Bus | SPI — MOSI `GPIO16`, MISO `GPIO17`, SCK `GPIO15`, CS `GPIO14` |
-| Control | RESET `GPIO5`, BUSY `GPIO19`, **IRQ `GPIO20`**, power enable `GPIO44` |
-| Kernel | **spidev** (`0054-riscv-dts-rm69a10-enable-lora-spidev.patch`) |
-| Userspace | **RadioLib** |
-| Evidence | `reported-working` |
-
-## Choose the radio before you buy
-
-| SKU | Radio | Band | Price 2026-09-04 | Meshtastic capability |
-|---|---|---|---:|---|
-| `K256` / `-A` / `-B` / `-C` | SX1262 | 868 / 915 / 923 / 433 MHz | $98.79 | text mesh only |
-| `K256-03` (kit) | SX1262 | 868 MHz | $150.31 | text mesh only |
-| **`K277`** (kit) | **LR2021** | 830–940 MHz | $153.01 | **voice and photo transfer** |
-
-LilyGO states it plainly: *"Voice/photo transfer is only available between K230 boards fitted
-with LR2021 modules; SX1262 boards support basic text mesh messages only."* For **$2.70** more at
-kit level, the LR2021 unlocks a capability class. If mesh voice or images matter at all, buy
-`K277`.
-
-## The DIO trap
-
-Both radios connect their interrupt to K230 `GPIO20`, but from **different radio pins**:
-
-- **SX1262 → `DIO1`**
-- **LR2021 → `DIO11`**
-
-A driver that hard-codes `DIO1` sees no interrupts on an LR2021 board and looks like dead
-hardware. Configure per fitted part.
-
-## Software model
-
-The radio is **not** a kernel LoRa driver. The device tree exposes plain **spidev** and
-everything happens in userspace through **RadioLib**, including reset, which LilyGO notes is
-"controlled by the RadioLib HAL".
-
-Consequences:
-
-- Any process that can open the spidev node can corrupt radio state. There is **no kernel-side
-  arbitration** between the Meshtastic app, the LoRa test app and the FLRC bench — the launcher
-  arbitrates internally, and only internally.
-- Porting RadioLib code from an Arduino board is mostly a matter of writing a Linux spidev +
-  gpiod HAL, which LilyGO has already done.
-
-## What ships
-
-| App | Status | Notes |
-|---|---|---|
-| **Meshtastic** | **Beta** | chat, node list, map view, channel sharing; on-device **map tile download** added v0.2.4 |
-| **LoRaWAN** | Beta | `lorawan_test.cpp` |
-| **LoRa tools** | v0.2.4 added radio-model persistence and cleaner RF-test profile controls | `ui_lora.cpp` |
-| **FLRC bench** | present | `lora_flrc_bench.cpp` |
-| **FLRC camera stream** | present | `k230_flrc_camera_stream.sh` — images over a LoRa-family modulation |
-| Meshtastic probe | present | `k230_meshtastic_probe.cpp` |
-
-An **independent** Meshtastic UI is in progress: r/meshtastic, 2026-06-02 — *"I am working on a
-full Meshtastic UI app for this and will publish a repo once complete. Lots of challenges
-adapting everything to the K230's preferred formats but making progress."* (announced project,
-no repository at the time of writing).
-
-## Antenna
-
-Product photography shows a LoRa antenna. **No external-antenna connector option is offered**,
-and a user asked for one on 2025-03-24 without a recorded response.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Radios fitted | one, chosen at purchase | board |
-| Band | fixed per SKU | board |
-| Meshtastic voice/photo | **LR2021 only** | board |
-| Kernel arbitration | none — spidev | framework |
-| Link budget, range, TX current | **not published for this board** | unmeasured |
-| Regulatory certification | **not established** | unknown |
-
-## Pitfalls
-
-1. Buying `K256-03` and then wanting mesh voice.
-2. Hard-coding `DIO1`.
-3. Forgetting `GPIO44` — the radio is unpowered until you assert it.
-4. Two programs opening spidev at once.
diff --git a/devices/lilygo/t-display-k230/features/microsd.md b/devices/lilygo/t-display-k230/features/microsd.md
deleted file mode 100644
index dc3ec8b..0000000
--- a/devices/lilygo/t-display-k230/features/microsd.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# microSD — storage and the boot medium
-
-**Question:** *How do I use the SD card, and why does it matter more than usual?*
-
-| | |
-|---|---|
-| Controller | K230 **MMC1** |
-| Pins | CMD `GPIO54`, CLK `GPIO55`, D0–D3 `GPIO56`–`GPIO59` |
-| Role | **Boot medium *and* main storage** |
-| SoC capability | SD 3.01 / eMMC 5.0, 4- or 8-bit, HS200/HS400 | 
-| Component | [generic/micro-sd-sdmmc](../../../../components/generic/micro-sd-sdmmc/README.md) |
-| Evidence | `reported-working` |
-
-## The card is the system
-
-There is no on-board storage the system boots from — **the whole Linux image lives on the SD
-card**. That has two consequences most boards do not have:
-
-1. **Card quality is system reliability.** A flaky card is a flaky computer, not a flaky data
-   store.
-2. **Removing the card while running is not a hot-unplug, it is pulling the root filesystem.**
-
-## Writing an image
-
-See [`development.md` §3](../development.md#3-flashing-the-sd-card). `dd` on Linux/macOS,
-**Rufus in DD Image mode** on Windows. After writing on Windows, decline the "format this
-partition" prompt.
-
-## Using the spare space
-
-Before BSP **v0.2.4** the image occupied its declared size and the rest of a large card was
-simply unused. v0.2.4 "added storage expansion settings for SD cards larger than the flashed
-image" — `k230_storage_expand.sh` in the launcher, exposed in Settings.
-
-`resize2fs` and `parted` are both in the image (`BR2_PACKAGE_E2FSPROGS_RESIZE2FS`,
-`BR2_PACKAGE_PARTED`), as are `dosfstools` with `mkfs.fat` and `fsck.fat`.
-
-## Getting files on and off
-
-| Route | Notes |
-|---|---|
-| **MTP over USB** | `S41adb_mtp` init script; launcher has an MTP page with its own layout work in v0.2.3/v0.2.4 |
-| **USB mass storage gadget** | `k230-usb-storage-gadget` + `/etc/default/k230_usb_storage`; `USB_CONFIGFS_MASS_STORAGE=y` |
-| **SSH / scp** | Once networked. `deploy_launcher.sh` uses it. |
-| Card reader | Offline. |
-
-User content LilyGO deliberately does **not** ship: **NES ROMs**, **offline map tiles**, media.
-Copy them to the card yourself.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Bus | 4-bit as wired | board |
-| SoC max mode | SD 3.01 | silicon |
-| Card size | expandable since v0.2.4 | framework |
-| Measured throughput | **none published** | unmeasured |
-| Hot-swap | not supported — it is the rootfs | board |
-
-## Pitfalls
-
-1. **Changing boot medium is the documented bricking path.** See
-   [`factory-firmware.md`](../factory-firmware.md).
-2. Formatting the "unknown partition" Windows offers to format destroys the boot partition.
-3. Cheap cards. This is the rootfs.
diff --git a/devices/lilygo/t-display-k230/features/nrf52840-ble.md b/devices/lilygo/t-display-k230/features/nrf52840-ble.md
deleted file mode 100644
index bfd8c29..0000000
--- a/devices/lilygo/t-display-k230/features/nrf52840-ble.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# BLE via the nRF52840 companion
-
-**Question:** *How do I do Bluetooth Low Energy on a board whose SoC has no Bluetooth?*
-
-| | |
-|---|---|
-| Companion | [Nordic nRF52840](../../../../components/nordic-semiconductor/nrf52840/README.md) |
-| Where | **nRF52840 BLE / audio / sensor base board** (optional expansion) |
-| Link | K230 **UART1** — `GPIO3` TX → `P0.11`, `GPIO4` RX ← `P0.12` |
-| Device | `/dev/ttyS1`, **115200 8N1** |
-| Protocol | LilyGO **AT command set** |
-| Role | **BLE Central** |
-| Evidence | `reported-working` |
-
-## Why this exists
-
-The K230 has **no Bluetooth radio**. The alternatives are a USB dongle (workaround-patched,
-experimental — [wifi-and-bluetooth.md](wifi-and-bluetooth.md)) or this. This is the better one.
-
-## AT interface
-
-```
-AT                 → OK
-AT+VER?
-AT+MESHSTATUS?
-AT+SCAN=5          scan for 5 s
-AT+LIST?           cached results
-AT+CONN=0          connect to index 0
-AT+GATTS?          discover services
-AT+DISC            disconnect
-```
-
-Plus characteristic read / write / subscribe / unsubscribe. Every command returns `OK` or
-`ERR:<reason>`. Asynchronous events arrive as URCs:
-
-```
-+SCAN:<index>,<addr>,<rssi>,<ble_uart_advertised>,<name>
-+SCAN:DONE,<count>
-+CONNECTED:<handle>
-+DISCONNECTED:<handle>,<reason_hex>
-+BOOT:K230_NRF52840_AT
-+MESH:ADV,1
-```
-
-Full reference: `docs/AT_COMMANDS.md` in `Xinyuan-LilyGO/T-Display-K230-nRF52840`.
-
-## Talking to it
-
-From the K230, open `/dev/ttyS1` at 115200 8N1 and write AT lines. The launcher's BLE page
-(`ui_ble.c`) does exactly this. Enabled by
-`0060-riscv-dts-rm69a10-enable-uart1-nrf52840.patch`.
-
-From a PC, connect to the nRF52840's own USB-C for a debug log at 115200. ⚠ **Some serial
-monitors need DTR asserted** or the port stays silent — LilyGO says so explicitly.
-
-## Updating the firmware
-
-Two paths, and the second one is the interesting one.
-
-**USB / UF2** — the developer path. Jumper `RST` to `GND` twice quickly (or touch the USB-C
-shell), the Adafruit bootloader enumerates a drive, drag the `.uf2`. Family ID `0xADA52840`.
-Build with PlatformIO (`nrf52840_dk_adafruit`, Arduino framework), convert with
-`scripts/uf2conv.py`.
-
-**UART DFU from the K230** — the field path. A custom bootloader
-(`k230_nrf52840_bootloader_uartdfu_115200_s140_6.1.1.hex`, SoftDevice **S140 6.1.1**) plus
-`tools/k230_nrf52840_dfu.cpp` (33 370 bytes) and the launcher's `ui_nrf52840_dfu.c` let the
-handheld reflash its own BLE controller with no PC attached. That is a genuinely well-thought-out
-piece of product design and it is not common at this price.
-
-**Ownership arbitration:** BSP v0.2.2 "improved nRF52840 ownership coordination between
-Meshtastic BLE and UART DFU". Both want `/dev/ttyS1`; only the launcher arbitrates.
-
-## It also controls power
-
-`P0.04` (Arduino pin 4) is the **external 5 V boost enable** for the 21700 battery compartment,
-supplying the main unit. So the nRF52840 is not only a radio peripheral, it is in the power path.
-See [battery-and-power.md](battery-and-power.md).
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Role | **Central** as shipped | firmware |
-| Link rate | 115200 8N1 — caps GATT throughput | board/firmware |
-| Peripheral role, mesh, Thread, Zigbee | silicon-capable, **not in the shipped firmware** | firmware |
-| Requires | the nRF52840 base board (separate purchase) | board |
-| Measured BLE range / throughput | **none published** | unmeasured |
-
-## Pitfalls
-
-1. The base board is optional. A bare `K256` has no nRF52840.
-2. 115200 is the bottleneck for anything data-heavy over GATT.
-3. Interrupting UART DFU — the UF2 path is the fallback.
-4. Reflashing the nRF52840 while it holds the 5 V boost enable.
diff --git a/devices/lilygo/t-display-k230/features/nrf9151-cellular-gnss.md b/devices/lilygo/t-display-k230/features/nrf9151-cellular-gnss.md
deleted file mode 100644
index 5427061..0000000
--- a/devices/lilygo/t-display-k230/features/nrf9151-cellular-gnss.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# Cellular and GNSS via the nRF9151 companion
-
-**Question:** *How do I get LTE data and a GPS fix?*
-
-| | |
-|---|---|
-| Companion | [Nordic nRF9151](../../../../components/nordic-semiconductor/nrf9151/README.md) — LTE-M / NB-IoT / DECT NR+ / GNSS SiP |
-| Where | **nRF9151 keyboard base board** — kit SKU **`K256-04`** ($113.25). SKU `K256-04-A` ($70.94) is the **same keyboard without it**. |
-| Link | K230 **UART3** — `GPIO28` TX → `P0.26`, `GPIO29` RX ← `P0.27` |
-| Device | `/dev/ttyS3`, **115200 8N1, no RTS/CTS** |
-| Enable | **`GPIO2` high** enables the module |
-| Firmware | Nordic **Serial LTE Modem**, NCS **v3.4.0** |
-| Evidence | `reported-working` |
-
-## Turning it on
-
-1. Drive **`GPIO2` high**. Nothing works until you do.
-2. Open `/dev/ttyS3` at 115200 8N1, no flow control.
-3. `AT+CFUN=1` — **required before SIM commands.** LilyGO states this explicitly; `AT+CPIN?`
-   before `AT+CFUN=1` fails and looks like a missing SIM.
-4. Register, attach, and use the Serial LTE Modem's socket AT commands.
-
-The launcher's Cellular page (`ui_cellular.c`) and manager (`ui_nrf9151_manager.c`) drive all of
-this. Enabled by `0061-riscv-dts-rm69a10-enable-uart3-nrf9151.patch`, which also configures
-`GPIO2` as the userspace modem-enable pin.
-
-## GNSS
-
-- `AT#XNMEA=1` enables **NMEA URCs** on the AT UART; `AT#XNMEA=0` disables them.
-- On a fix, the `P0.23` LED changes to a **1 s cadence with about 300 ms on-time** — a free
-  visual fix indicator that needs no software.
-- The NMEA URC path is one of LilyGO's five patches on top of Nordic's Serial LTE Modem
-  (`0001-k230-gnss-nmea-urc-and-led.patch`, `0004-k230-gnss-nmea-urc-worker.patch`).
-
-## Firmware, and how to rebuild it
-
-Two profiles in `Xinyuan-LilyGO/T-Display-K230-nRF9151` @ `ed4ecbe34162dec9b81213a400198125bbd6e36f`:
-
-| Profile | Use |
-|---|---|
-| `serial_modem_k230/` | **Recommended.** What the launcher expects. |
-| `at_client_k230/` | Minimal AT passthrough, bring-up only. |
-
-Build: see [`development.md` §5](../development.md#5-building-the-nrf9151-firmware). NCS v3.4.0
-via `nrfutil sdk-manager`, upstream Serial LTE Modem pinned as a submodule at
-`13c80da97fe4d55ecb5a9745834d97be22821307`, five ordered patches, output
-`build/serial_modem_k230/zephyr/tfm_merged.hex`.
-
-⚠ **`tfm_merged.hex` is TF-M plus the non-secure application. It does NOT update the modem
-firmware** (`mfw_nrf91x1_*.zip`), which is a separate signed package with its own procedure.
-This is the classic nRF91 confusion and LilyGO pre-empted it in their README.
-
-## Debug console
-
-`P0.29` (TX2) and `P0.28` (RX2) are a second UART for the Serial LTE Modem log, brought out for
-an **external USB-UART adapter** — not to the K230. If cellular misbehaves and the AT link tells
-you nothing, this is where the answer is.
-
-## Alternative: a USB modem
-
-The BSP builds `CDC_MBIM`, `QMI_WWAN`, `USB_WDM`, `USB_SERIAL_OPTION` and PPP, so a **USB LTE
-dongle** works on the host port without the keyboard base. Canaan publishes
-`K230_4G_Module_Linux_Porting_Reference` for this. Trade-off: bulk and power versus $42.31 and an
-integrated GNSS.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Radio | **LTE-M and NB-IoT only** — no LTE Cat-1/4, no 5G, no voice | silicon |
-| Throughput | LTE-M ≈ hundreds of kbit/s | silicon |
-| UART link | 115200 — a real ceiling on data | board |
-| Bands | not stated by LilyGO | **unknown** |
-| Carrier certification | **none stated** | **unknown** |
-| SIM form factor | **not stated** | **unknown** |
-| Antenna | **not documented** | **unknown** |
-| Measured fix time, power, throughput | **none published** | unmeasured |
-
-**LTE-M/NB-IoT is not general-purpose internet.** It is a low-bandwidth IoT bearer with patchy
-availability outside major carriers. Check coverage in your country before buying `K256-04`
-rather than `K256-04-A`.
-
-## Pitfalls
-
-1. Forgetting `GPIO2`.
-2. `AT+CPIN?` before `AT+CFUN=1`.
-3. Expecting `tfm_merged.hex` to update modem firmware.
-4. Buying `K256-04-A` and expecting cellular. Read the SKU.
diff --git a/devices/lilygo/t-display-k230/features/touch.md b/devices/lilygo/t-display-k230/features/touch.md
deleted file mode 100644
index 72222a6..0000000
--- a/devices/lilygo/t-display-k230/features/touch.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# Touch — Goodix GT9895
-
-**Question:** *How do I read touch input, and why does resetting HDMI break it?*
-
-| | |
-|---|---|
-| Controller | [Goodix GT9895](../../../../components/goodix/gt9895/README.md) ("Berlin" family) |
-| Bus | I²C3 — `GPIO37` SDA, `GPIO36` SCL |
-| Address | **`0x5D`** |
-| IRQ / RESET | `GPIO23` / `GPIO24` — **both shared with LT9611** |
-| Driver | `CONFIG_TOUCHSCREEN_GOODIX_BRL` (`goodix_berlin`), **built-in** |
-| Evidence | `reported-working` |
-
-## Software
-
-Touch is a standard Linux **input** device. LVGL consumes it through the evdev backend; nothing
-board-specific is needed in application code.
-
-**Use the right driver.** The BSP sets `CONFIG_TOUCHSCREEN_GOODIX_BRL=y` and explicitly
-**disables** `CONFIG_TOUCHSCREEN_GOODIX`. The legacy driver serves GT911/GT9271 and will not
-drive a GT9895, even though both answer at `0x5D`. This repository holds
-[GT911](../../../../components/goodix/gt911/README.md) and
-[GT9271](../../../../components/goodix/gt9271/README.md) records — they are **not**
-interchangeable with this part.
-
-LilyGO carries a **307 439-byte** downstream patch, `0034-gt9895-touch.patch`. That size means a
-substantially vendored driver, not a device-tree addition. It is the authoritative description
-of this controller's behaviour on this board.
-
-## Minimal procedure
-
-```sh
-evtest                       # built into the image; pick the Goodix device
-cat /proc/bus/input/devices  # confirm it enumerated
-i2cdetect -y <bus>           # 0x5D should answer   (launcher: I2C Scan)
-```
-
-## Conflicts
-
-**`GPIO23` and `GPIO24` are shared with the LT9611 HDMI bridge.** Anything that resets HDMI
-resets touch. In practice the two are already mutually exclusive because they contend for the
-single DSI output ([HC-1](../resources-and-conflicts.md)), so this bites only in HDMI diagnostic
-mode.
-
-## Limits and unknowns
-
-- **Touch-point count: unknown.** The launcher has a multitouch test page (`ui_multitouch.c`) but
-  no source asserts a number.
-- Report rate, gesture support, palm rejection, firmware update procedure: **unknown**.
-- No Goodix datasheet is public for this part.
-
-## Debugging
-
-No touch at all → check the driver actually bound (`dmesg | grep -i goodix`), then that `0x5D`
-answers, then that `GPIO23` is not held by something else. Touch working but coordinates wrong →
-axis swap/invert in the device tree, not a driver bug.
diff --git a/devices/lilygo/t-display-k230/features/usb.md b/devices/lilygo/t-display-k230/features/usb.md
deleted file mode 100644
index 23b0730..0000000
--- a/devices/lilygo/t-display-k230/features/usb.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# USB — host, gadget, MTP, mass storage
-
-**Question:** *What can I plug in, and how do I make the board appear as a device?*
-
-| | |
-|---|---|
-| SoC | [K230](../../../../components/canaan/k230/README.md) — **2 × USB 2.0 OTG** |
-| Connectors | USB-C for power; USB-C for OTG (product page: "1 × Power + 1 × USB 2.0 OTG (Type-C)") |
-| Charging | 5 V, **500 mA** |
-| Evidence | `reported-working` |
-
-## Host side — three devices the BSP expects
-
-| Device | Kernel support built | Why |
-|---|---|---|
-| **USB Ethernet** | `USB_USBNET`, `CDCETHER`, `CDC_NCM`, `RNDIS_HOST`, `CDC_SUBSET` | the RJ45 ([ethernet.md](ethernet.md)) |
-| **USB Bluetooth** | `BT_HCIBTUSB` + `_BCM`/`_MTK`/`_RTL`, CSR8510 patches | the only Bluetooth ([wifi-and-bluetooth.md](wifi-and-bluetooth.md)) |
-| **USB cellular modem** | `CDC_MBIM`, `QMI_WWAN`, `USB_WDM`, `USB_SERIAL_WWAN`, `USB_SERIAL_OPTION`, `PPP*` | an alternative to the nRF9151 base |
-
-`USB_ACM` and `USB_SERIAL` are also on, so ordinary USB serial adapters work. Canaan publishes
-`K230_4G_Module_Linux_Porting_Reference` for the modem case.
-
-## Gadget side
-
-`CONFIG_USB_CONFIGFS=m` with `F_FS`, **`MASS_STORAGE`**, **`RNDIS`** and **`ACM`** functions. The
-rootfs overlay ships `/usr/sbin/k230-usb-storage-gadget` (5 601 bytes) and
-`/etc/default/k230_usb_storage` (303 bytes), and `S41adb_mtp` starts ADB/MTP.
-
-So the board can present itself to a PC as:
-
-- a **mass-storage device** (expose the SD card)
-- an **MTP device** (file transfer without unmounting)
-- an **RNDIS network device** (USB networking to the host)
-- a **serial device** (ACM console)
-
-## Alternatives decision table
-
-| Goal | Route |
-|---|---|
-| Copy media to the board, board still running | **MTP** |
-| Expose the card wholesale to a PC | **mass storage gadget** |
-| Network to a host with no Wi-Fi or Ethernet | **RNDIS gadget** |
-| Console when the display is dead | **ACM gadget**, or UART0 |
-| Add Bluetooth | USB dongle (host) |
-| Add cellular without the keyboard base | USB modem (host) |
-
-## Conflicts
-
-Only two USB controllers exist and one is largely the power port. **Host and gadget roles on the
-same connector are exclusive**; running the mass-storage gadget while a USB Ethernet dongle is
-attached needs the two roles on different controllers. Untested.
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Controllers | 2 × USB 2.0 OTG | silicon |
-| Speed | USB 2.0 High-Speed per the SoC; **not confirmed for this board's ports** | silicon / unverified |
-| Charge current | 5 V 500 mA | board |
-| Measured throughput | **none published** | unmeasured |
-
-## Pitfalls
-
-1. **500 mA is a modest budget.** A 1.6 GHz SoC, an AMOLED and a charging cell on 2.5 W is tight.
-   The launch thread's top comment was "Plug in that device! It's thirsty!" about the battery
-   indicator in LilyGO's own promotional photo.
-2. Enabling multiple gadget functions and a host role at once will contend.
-3. USB Bluetooth is a **workaround-patched, experimental** path.
diff --git a/devices/lilygo/t-display-k230/features/wifi-and-bluetooth.md b/devices/lilygo/t-display-k230/features/wifi-and-bluetooth.md
deleted file mode 100644
index f162ad8..0000000
--- a/devices/lilygo/t-display-k230/features/wifi-and-bluetooth.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# Wi-Fi and Bluetooth
-
-**Question:** *How do I get on Wi-Fi? And why does Bluetooth need a dongle?*
-
-| | |
-|---|---|
-| Wi-Fi | [Realtek RTL8189FS](../../../../components/realtek/rtl8189fs/README.md), **SDIO**, 802.11 b/g/n 2.4 GHz, `wlan0` |
-| Bluetooth | **USB dongle** — CSR8510/8891, BlueZ. **No on-board BT radio.** |
-| Alternate Wi-Fi modules built | RTL8723DS, RTL8733BS |
-| Evidence | `reported-working` |
-
-## Wi-Fi
-
-`BR2_PACKAGE_RTL8189FS=y` builds Realtek's **out-of-tree** vendor driver. Userspace has
-`wpa_supplicant` (with Wi-Fi Display), `wireless_tools` and `udhcpc`. The launcher's Wi-Fi page
-handles scan/connect/DHCP; nothing exotic is required.
-
-```sh
-ip link set wlan0 up
-wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
-udhcpc -i wlan0
-```
-
-**2.4 GHz only. 802.11n only.** No 5 GHz, no Wi-Fi 5/6.
-
-**Two Wi-Fi drivers are compiled simultaneously** (`RTL8189FS` *and* `RTL8723DS`). That means the
-fitted module is not guaranteed identical across production runs. Check the unit in hand:
-`dmesg | grep -i rtl` or `lsmod`.
-
-Out-of-tree vendor drivers break on kernel upgrades. That is normal for this part and is a real
-maintenance cost if you plan to move off LilyGO's pinned kernel
-(`ruyisdk/linux-xuantie-kernel` @ `7d4e1f444f461dbe3833bd99a4640e7b6c2cd529`).
-
-## Bluetooth — read this before buying
-
-**The K230 has no Bluetooth radio.** The kit specification sheet lists no Bluetooth at all. What
-the BSP provides is **USB** Bluetooth:
-
-- `CONFIG_BT=m`, `BT_BREDR`, `BT_LE`, `BT_RFCOMM`, `BT_BNEP`, `BT_HIDP`
-- `CONFIG_BT_HCIBTUSB=m` with `_BCM`, `_MTK`, `_RTL` vendor support
-- `S40bluetoothd` init script, BlueZ runtime
-- **`0056-bluetooth-btusb-force-csr8510-8891-workaround.patch`**
-- **`0057-bluetooth-csr8510-8891-hci-init-experimental.patch`**
-
-Both patch names contain the words *workaround* and *experimental*. Treat Bluetooth on this
-board as working-with-a-specific-dongle, not as a platform feature.
-
-⚠ **The wiki claims otherwise.** LilyGO's T-Display K230 wiki page states the board has an
-ESP32-S3-R8 providing "Bluetooth 5.0 LE". Nothing in the BSP corroborates that — see
-[`GC-2`](../gaps-and-conflicts.md). **Do not plan a project around on-board Bluetooth.**
-
-Community, r/meshtastic 2025-07-08: *"Bluetooth seems to be missing — might that be an
-impediment…"* / *"You're right. I don't see BT labels on the board, and the K230 page does not
-mention Bluetooth."* / *"USB C Bluetooth adaptors are $20, but that seems like a REALLY weird
-omission."*
-
-## If you need BLE properly: use the nRF52840
-
-The [nRF52840 base board](nrf52840-ble.md) is the sanctioned BLE path, over UART1 with an AT
-protocol. It is a **BLE Central** implementation and it is what the launcher's Meshtastic BLE
-support uses. That is a considerably more solid answer than the dongle.
-
-## Wi-Fi HaLow?
-
-The launcher has `ui_halow.c`, `halow_udp_stream.c` and `k230_halow_camera_stream.sh` —
-**802.11ah HaLow** support for an external module. No HaLow hardware is listed in any product
-specification, so this is presumably for a user-supplied module on the expansion header.
-**Unverified.**
-
-## Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Wi-Fi bands | 2.4 GHz only | board |
-| Wi-Fi standard | 802.11 b/g/n | board |
-| Bluetooth | USB dongle only | **silicon** (no radio on K230) |
-| BLE via nRF52840 | Central role, AT-mediated | board |
-| Antenna | internal; **no external antenna connector** requested by users but not provided | board |
-| Measured throughput / range | **none published** | unmeasured |
-
-A user asked at launch: *"I'd really like to see more options to add external antennas for wifi,
-lora and gps."* (2025-03-24). No response was recorded.
diff --git a/devices/lilygo/t-display-k230/gaps-and-conflicts.md b/devices/lilygo/t-display-k230/gaps-and-conflicts.md
deleted file mode 100644
index 31bca6e..0000000
--- a/devices/lilygo/t-display-k230/gaps-and-conflicts.md
+++ /dev/null
@@ -1,157 +0,0 @@
-# T-Display K230 — gaps and conflicts
-
-Open items as of **2026-09-04**. Each states the conflict, both sides with sources, and **what
-evidence would settle it**. None is resolved by preference.
-
----
-
-## `GC-1` — Which K230 core runs Linux
-
-| Source | Claim |
-|---|---|
-| **Canaan K230 brief datasheet** (primary) | "CPU 1 … 1.6 GHz … **runs RTOS system**"; "CPU 0 … 800 MHz … **runs LINUX system**" |
-| **LilyGO wiki**, T-Display K230 Quick Start FAQ | "the dual-core architecture — **big core runs Linux, little core runs RT-Thread** or bare-metal" |
-
-**Assessment.** Canaan's document is primary and matches the SDK's own configuration naming.
-LilyGO's FAQ is wrong. Separately, this board's shipped image is built from
-`kendryte/k230_linux_sdk`, which is **Linux-only**, so in the default configuration CPU1 is not
-running RT-Smart at all.
-
-**Settles it:** `cat /proc/cpuinfo` and `dmesg | grep -i 'cpu\|hart'` on a running unit.
-
----
-
-## `GC-2` — The claimed ESP32-S3-R8 co-processor  ⚠ most consequential
-
-| Source | Claim |
-|---|---|
-| **LilyGO wiki**, T-Display K230 page | Board is "combined with **ESP32-S3-R8** (16 MB Flash, 8 MB PSRAM) for Wi-Fi/Bluetooth connectivity"; lists "Bluetooth 5.0 LE (ESP32-S3)"; gives PlatformIO and Arduino build instructions for "the ESP32-S3 co-processor" |
-| **LilyGO shop**, T-Display K230 Kit | "Wi-Fi Module \| 2.4G, Name: **RTL8189**, IEEE 802.11 b/g/n 2.4GHz". No Bluetooth row at all. |
-| **LilyGO BSP** at `bb831ab…` | `BR2_PACKAGE_RTL8189FS=y`. Bluetooth via `BT_HCIBTUSB` + two **CSR8510/8891 USB dongle** patches. A regex sweep for every Espressif identifier across the whole repository returns **zero matches**. |
-| **LilyGO wiki**, Cased Version page | "Supports 2.4GHz Wi-Fi, BLE" — **names no chip** |
-| **Community**, r/meshtastic 2025-07-08 | "I don't see BT labels on the board, and the K230 page does not mention Bluetooth" |
-
-**Assessment.** The BSP is the strongest evidence and it is unambiguous: SDIO Realtek Wi-Fi, USB
-Bluetooth, no Espressif part. The wiki paragraph reads like copy-paste from a sibling T-Display
-product. But the wiki is a *primary vendor source*, and a later hardware revision adding an
-ESP32-S3 cannot be excluded — one owner wrote on 2026-08-28 "now that you have the keyboard and
-**the esp** I might purchase again", which may reflect a newer variant or may reflect the wiki.
-
-**Deliberate consequence:** the existing
-[`components/espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) record
-has **not** been given a Used-By entry for this board.
-
-**Settles it:** `lsusb`, `dmesg | grep -i blue`, `ls /sys/class/net`, or a photograph of the PCB.
-
----
-
-## `GC-3` — What drives the RJ45
-
-| Source | Claim |
-|---|---|
-| **LilyGO wiki** (both pages) | "**RTL8152B** 100 Mbps Ethernet (IEEE 802.3u)" |
-| **LilyGO shop**, Kit | "Ethernet Module \| Name: **RC01812** \| Connector: RJ45" |
-| **Canaan K230 datasheet** | **No Ethernet MAC.** Full-text search for `ethernet`, `gmac`, `rmii` across the full and brief datasheets: **zero matches.** |
-| **LilyGO BSP** `linux.fragment` | Enables `USB_USBNET`, `CDCETHER`, `CDC_NCM`, `CDC_MBIM`, `RNDIS_HOST`, `QMI_WWAN`, `CDC_SUBSET`. **Does not enable `CONFIG_USB_RTL8152`.** |
-| **Launcher** | Manages `eth0` with `ifconfig`/`udhcpc`; driver-agnostic |
-
-**Assessment.** The RJ45 is definitely USB-attached, because the SoC has no MAC. `RC01812`
-matches no known Ethernet controller and is most consistent with an **RJ45 jack with magnetics**
-part number — an interpretation, not a finding. `CONFIG_USB_RTL8152` is probably already set in
-the base `k230` kernel defconfig, which the fragment only extends.
-
-**Settles it:** `readlink /sys/class/net/eth0/device/driver` and `lsusb` on a running unit; or
-`zcat /proc/config.gz | grep RTL8152`.
-
----
-
-## `GC-4` — Is the LT9611 HDMI bridge actually fitted?
-
-Software support is extensive (dedicated device tree, two patches, a launcher test page, 29
-source references, and a headline "HDMI 1080P @ 30 FPS" on the wiki), but LilyGO calls the path
-"optional" in every pin-map row and "a diagnostic feature" in the README, and **never names the
-part in either shop listing**.
-
-**Settles it:** `i2cdetect` on the touch bus for a second address, or a PCB photograph.
-
----
-
-## `GC-5` — No schematic exists publicly
-
-LilyGO's wiki page has a `#schematic` heading with **no link or file beneath it** (verified
-2026-09-04). Same for `#dimension-diagram` on the bare-board page. This is a *soft* gap: no 404,
-no broken link, nothing for a link checker to catch.
-
-Consequence: the pin map is **unverifiable**, and the PMIC, speaker amplifier and microphone
-remain unidentified. Every pin claim in
-[`pinouts-and-buses.md`](pinouts-and-buses.md) rests on a single vendor document.
-
-**Settles it:** LilyGO publishing one, or a competent teardown with high-resolution PCB
-photographs. Neither existed on 2026-09-04.
-
----
-
-## `GC-6` — GC2093 sensor parameters undocumented
-
-The vendor V4L2 driver (`vvcam/src/gc2093.c`, 26 213 bytes) contains the full register
-initialisation but **no GalaxyCore datasheet is publicly available**, so the writes were not
-decoded. Pixel size, optical format, lane count, link rate, exposure and HDR/WDR limits are all
-unknown.
-
-**Settles it:** a GC2093 datasheet, or decoding the driver against a sibling GalaxyCore part.
-The skill's vendor-driver-audit step was **not performed for this sensor**, and that is recorded
-here rather than silently skipped.
-
----
-
-## `GC-7` — 512 MB versus 1 GB in the device tree
-
-The product specification says **8 Gb = 1 GB LPDDR4**. The Canaan U-Boot reference DTS the BSP
-overlays (`k230_canmv_v3.dts`) declares `memory@0 … <0x0 0 0x0 0x20000000>` = **512 MB**.
-
-**Assessment.** Almost certainly the upstream CanMV-v3 baseline that LilyGO's overlay replaces
-or that the boot loader corrects at runtime; the K230 SDK also splits DRAM between OSes in
-dual-OS configurations. **Not verified.**
-
-**Settles it:** `free -h` or `cat /proc/meminfo` on a running unit.
-
----
-
-## `GC-8` — ADC characteristics unknown
-
-`ADC0`, `ADC1`, `ADC2` are exposed on the 40-pin header. The K230 brief datasheet's peripheral
-list does **not** enumerate an ADC. Resolution, reference voltage, sample rate and input range
-are all unknown.
-
-**Settles it:** the Canaan `K230_Big_Core_Low_Speed_Driver_API_Reference` (retrieved but not yet
-mined) or the missing pinout document.
-
----
-
-## `GC-9` — 16 MB flash, purpose unclear
-
-LilyGO's wiki lists "Flash 16 MB" and "1 GB LPDDR4, **16 MB Flash**, TF card slot". The BSP boots
-from **SD**. The K230 supports SPI NOR and SPI NAND boot. Whether the 16 MB part is a boot NOR,
-storage for the (claimed) ESP32-S3, or a wiki error tied to `GC-2` is unresolved.
-
-**Settles it:** `cat /proc/mtd`, `dmesg | grep -i spi-nor`, or a PCB photograph.
-
----
-
-## Negative results confirmed in this pass
-
-Recorded so they are not re-investigated:
-
-- **The K230 has no Ethernet MAC.** Searched both datasheets for `ethernet`/`gmac`/`rmii` on
-  2026-09-04: zero matches.
-- **The K230 has no third CPU core.** The datasheet feature list contains exactly two CPU
-  subsystems. The PMU is fixed-function.
-- **Canaan publishes no K230 errata.** Full recursive listing of `kendryte/k230_docs` at
-  `f8e3021…`: no errata document in either language tree.
-- **`K230_PINOUT_V1.0_20230524` is cited by the datasheet but is not published.** Same listing.
-- **No LilyGO schematic for this board exists.** Wiki heading present, content absent.
-- **Zephyr has no K230 support upstream** as of 2026-09-04.
-- **No clone of this board was found** on any marketplace searched.
-- **No independent benchmark of this board exists** in any source searched.
-- **Canaan's `en/` documentation tree contains no binary hardware artifacts; the `zh/` tree
-  does.** This is a *correction* to the natural assumption, verified by full tree listing.
diff --git a/devices/lilygo/t-display-k230/market-and-pricing.md b/devices/lilygo/t-display-k230/market-and-pricing.md
deleted file mode 100644
index 715013d..0000000
--- a/devices/lilygo/t-display-k230/market-and-pricing.md
+++ /dev/null
@@ -1,162 +0,0 @@
-# T-Display K230 — market and pricing
-
-Every observation is dated, sourced and tied to an exact configuration. **All prices below come
-from LilyGO's own Shopify JSON endpoints on 2026-09-04**, which return integer cents per variant
-and therefore carry no currency-formatting ambiguity.
-
-## Current pricing — 2026-09-04, lilygo.cc, USD, worldwide storefront
-
-| Product | SKU | Configuration | Price | In stock |
-|---|---|---|---:|---|
-| T-Display K230 | `K256` | bare board, SX1262 **868 MHz** | **$98.79** | yes |
-| T-Display K230 | `K256-A` | bare board, SX1262 **915 MHz** | **$98.79** | yes |
-| T-Display K230 | `K256-B` | bare board, SX1262 **923 MHz** | **$98.79** | yes |
-| T-Display K230 | `K256-C` | bare board, SX1262 **433 MHz** | **$98.79** | yes |
-| T-Display K230 Kit | `K256-03` | **Main Unit**, SX1262 868 MHz | **$150.31** | yes |
-| T-Display K230 Kit | `K277` | **Main Unit**, **LR2021** 830–940 MHz | **$153.01** | yes |
-| T-Display K230 Kit | `K256-04` | **Keyboard only**, **with nRF9151** | **$113.25** | yes |
-| T-Display K230 Kit | `K256-04-A` | **Keyboard only**, **without nRF9151** | **$70.94** | yes |
-
-**Shipping, tax and duty are not included and were not observed.** Currency is USD as returned by
-the store; no conversion was performed, so no conversion date applies.
-
-### The derived numbers that matter
-
-| Question | Answer | Working |
-|---|---|---|
-| Cheapest way into a K230 | **$98.79** | bare board, any band |
-| Complete keyboard handheld, no cellular | **$221.25** | `K256-03` $150.31 + `K256-04-A` $70.94 |
-| Complete keyboard handheld **with cellular** | **$263.56** | `K256-03` + `K256-04` |
-| Complete handheld with **LR2021** + cellular | **$266.26** | `K277` $153.01 + `K256-04` |
-| Price of the **nRF9151 cellular option** | **$42.31** | `K256-04` − `K256-04-A` |
-| Price of the **LR2021 upgrade** | **$2.70** | `K277` − `K256-03` |
-| Main Unit premium over bare board | **$51.52** | `K256-03` − `K256` |
-
-**Two of these deserve emphasis.**
-
-The **$2.70 LR2021 upgrade** buys Meshtastic voice and photo transfer, which LilyGO states is
-impossible on SX1262 units. That is an unusually cheap capability jump and there is no obvious
-reason to choose `K256-03` over `K277`.
-
-The **$51.52 Main Unit premium** is not explained anywhere in the listing. The bare board and the
-"Main Unit" both carry an SX1262 at 868 MHz. The difference is presumably the case, the battery
-compartment, or the base-board interface — LilyGO's shipping-list graphic was not machine-readable
-and the difference remains **unexplained**. Do not assume the two are the same hardware.
-
-## Launch pricing
-
-| Date | Product | Price | Source |
-|---|---|---|---|
-| 2025-03-21 | T-Display K230, bare board | **not recorded** | Product created and published this date; the store returns only *current* prices, and no archived listing was retrieved |
-| 2026-08-20 | T-Display K230 Kit | **not recorded** separately | Published 2026-08-20; the 2026-09-04 prices are 15 days old at most, so they are effectively launch prices for the kit |
-
-**Launch price for the bare board is a genuine gap.** An Internet Archive capture of
-`https://lilygo.cc/products/t-display-k230` from March 2025 would settle it; not attempted here.
-
-## Comparative price points, dated
-
-| Board | SoC | RAM | Display | Price | Date | Source |
-|---|---|---|---|---:|---|---|
-| **BPI-CanMV-K230D-Zero** | K230**D** | 128 MB (SiP) | none | **$29** | 2024-11-18 | CNX-Software launch coverage |
-| **CanMV-K230** | K230 | 512 MB | none | not established | 2023-10 | Repeatedly out of stock; see below |
-| **T-Display K230** | K230 | **1 GB** | 4.1″ AMOLED | **$98.79** | 2026-09-04 | lilygo.cc |
-| **T-Display K230 Kit**, full | K230 | 1 GB | + keyboard + cellular | **$263.56** | 2026-09-04 | lilygo.cc |
-
-The K230D Zero at $29 is the reference point for "what a K230 costs as a component". The LilyGO
-board's $98.79 buys **8× the RAM**, an AMOLED, a camera, LoRa, Ethernet and a 40-pin header on top
-of that. Viewed that way the pricing is reasonable; viewed as a handheld against a $30 Meshtastic
-node, it is not.
-
-## Availability
-
-| Date | Observation | Evidence |
-|---|---|---|
-| 2025-03-26 | "**Already sold out…** any chance to get it back in stock?" — five days after launch | firsthand, r/LilyGO |
-| 2025-03-27 | LilyGO: "Don't worry, sales will resume soon" | vendor |
-| 2025-07-04 | "T-Display K230 and T-Lora Pager **have some stock available**" | vendor post, r/LilyGO |
-| 2026-09-04 | **All eight variants show available** in the Shopify JSON | primary |
-| 2024-05-08 | "Where do people buy CANMV K230 from?" — the reference board was hard to source | r/RISCV |
-
-K230 hardware has a persistent history of being hard to buy. As of the research date, the LilyGO
-board is not — every SKU is in stock.
-
-## Marketplaces, used market, clones — negative results
-
-- **AliExpress, Amazon, Tindie, Taobao: not searched in this pass.** Deliberate; see
-  [`research-log.md`](research-log.md). Third-party listings for LilyGO products are common and
-  often carry different prices, so this is a real gap, recorded rather than glossed.
-- **Used market: no observations.** The product is too new — the kit is 15 days old.
-- **Clones: none found.** No clone or compatible listing was located in any search performed.
-- **Regional variants:** LilyGO uses region-suffixed SKUs elsewhere (`…DE`, `…US`) but **none
-  exists for the K230 SKUs** — the four bare-board variants differ only by LoRa band.
-
-## Cost-of-ownership notes
-
-Things not in the sticker price:
-
-- **A microSD card** is mandatory — it is the boot medium and the system disk.
-- **A 21700 cell** is not confirmed included in any SKU. One early buyer received no battery.
-- **A USB Bluetooth dongle** if you need Bluetooth (community estimate: ~$20).
-- **A case** for the main board is not included with the keyboard, confirmed 2026-08-13.
-- **A build host** — Ubuntu or Docker. No prebuilt image is published.
-
----
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display K230 | 2025-03-21 | 915Mhz [K256-A] | `K256-A` | **USD 98.79** | ✅ yes |
-| T-Display K230 | 2025-03-21 | 868Mhz [K256] | `K256` | **USD 98.79** | ✅ yes |
-| T-Display K230 | 2025-03-21 | 433Mhz [K256-C] | `K256-C` | **USD 98.79** | ✅ yes |
-| T-Display K230 | 2025-03-21 | 923 Mhz [K256-B] | `K256-B` | **USD 98.79** | ✅ yes |
-| T-Display K230 Kit | 2026-08-20 | Main Unit / SX1262/ 868MHz | `K256-03` | **USD 150.31** | ✅ yes |
-| T-Display K230 Kit | 2026-08-20 | Main Unit / LR2021/ 830–940MHz | `K277` | **USD 153.01** | ✅ yes |
-| T-Display K230 Kit | 2026-08-20 | Keyboard Only / With nRF9151 | `K256-04` | **USD 113.25** | ✅ yes |
-| T-Display K230 Kit | 2026-08-20 | Keyboard Only / Without nRF9151 | `K256-04-A` | **USD 70.94** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 98.79, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-k230`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-⚠ **Bare board and kit must not be merged.** Board USD 98.79 flat across all four radio frequencies (433/868/915/923 MHz) — **frequency choice carries no price difference**. The **Kit** is a separate handle at USD 150.31 (SX1262) / USD 153.01 (LR2021), plus a keyboard-only option at USD 113.25 with nRF9151 or USD 70.94 without.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-k230/media.md b/devices/lilygo/t-display-k230/media.md
deleted file mode 100644
index 8af0925..0000000
--- a/devices/lilygo/t-display-k230/media.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# T-Display K230 — images and provenance
-
-Machine-readable provenance for every retained image: [`media/manifest.json`](media/manifest.json)
-(14 records, each with SHA-256, byte size, direct URL, source page, retrieval date, licence
-status and modification history).
-
-**All 14 images are vendor material.** Neither lilygo.cc nor wiki.lilygo.cc carries a licence
-statement, so every record is `redistribution_status: unknown` and every file is held
-**unstaged** pending review.
-
-## What was obtained
-
-| Image | Shows | Source |
-|---|---|---|
-| `LILYGO-T-DISPLAY-K230_11.jpg` | Bare board, angled, AMOLED lit — the primary listing photo | Shopify CDN |
-| `LILYGO-T-DISPLAY-K230_9.jpg` · `_1.jpg` | Bare board, alternate marketing views | Shopify CDN |
-| `LILYGO-T-DISPLAY-K230-KIT_12.jpg` | **Kit — main unit docked to the keyboard base.** The single most useful image for identifying the product | Shopify CDN |
-| `LILYGO-T-DISPLAY-K230-KIT_9/6/10.jpg` | Kit, alternate views | Shopify CDN |
-| `t-display-k230-specifications.jpg` | **Annotated specification card** — LilyGO's own callout graphic | wiki |
-| `t-display-k230-40pin.jpg` | **40-pin header pinout diagram** | wiki |
-| `t-display-k230-keyboard-extension.jpg` | **Keyboard extension board diagram** | wiki |
-| `t-display-k230-cn.jpg` | Chinese-market annotated feature graphic | wiki |
-| `t-display-k230-1/2/3.jpg` | Wiki product images | wiki |
-
-The three annotated graphics — specification card, 40-pin diagram, keyboard extension diagram —
-are the highest-value items. They are the only published visual documentation of the header and
-the keyboard base, and they exist **only on the wiki**, not in the shop listing or the GitHub
-repository.
-
-## What was not found — negative results
-
-Searched on 2026-09-04 and **not located**:
-
-| Missing | Consequence |
-|---|---|
-| **Any PCB photograph**, front or back | The PMIC, speaker amplifier, microphone and the claimed ESP32-S3 cannot be resolved. Directly blocks [`GC-2`](gaps-and-conflicts.md), [`GC-4`](gaps-and-conflicts.md), [`GC-9`](gaps-and-conflicts.md) and every entry in the [unidentified-parts record](../../../components/unidentified/t-display-k230/README.md). |
-| **Any teardown**, at any stage | Same. |
-| **Any third-party review photograph** | No independent visual evidence exists at all. |
-| **A schematic** | The wiki's `#schematic` heading has no content ([`GC-5`](gaps-and-conflicts.md)). |
-| **A dimension drawing** | The `#dimension-diagram` heading on the bare-board page has no content. The Cased Version page references `t-display-k230-cased-dimensions.jpg`, which was **not fetched** in this pass — see below. |
-| **Cased Version images** | Six are referenced by the Cased Version wiki page: `-cased-angle`, `-cased-front-back`, `-cased-dimensions`, `-cased-features`, `-cased-details`, `-cased-pinmap`. Base URL `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/cased-version/image/<name>.jpg`. **Enumerated, not retrieved** — reacquisition is `automatic`. |
-
-Images embedded in the GitHub repositories were also **not** copied into this record, because
-they are reachable at pinned commits and are large: `images/top.png` (227 921 B),
-`image/bottom.png` (938 091 B), `image/left.png` (481 816 B), `image/pins_annotated.png`
-(699 111 B), `image/dfu_reset_guide.gif` / `_en.gif` (~1 MB each), `images/swd.png`
-(3 113 181 B), `images/nRF-ConnectProgrammer.mp4` (2 089 939 B). All are recoverable from
-`https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/raw/4646a728580739d487126f47a521e9b8032b3c2c/<path>`
-and the nRF9151 equivalent at `ed4ecbe3…`. **`image/pins_annotated.png` is the most valuable of
-these** — an annotated pin photograph of the nRF52840 base board.
-
-## Rights
-
-No watermark was removed, no image was cropped, rotated, annotated or recompressed. Every file
-is byte-identical to what the server returned, and its SHA-256 in the manifest proves it.
-An image-search result is not provenance; every record here names the page the image was
-published on.
diff --git a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_10.jpg b/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_10.jpg
deleted file mode 100644
index a15bd98..0000000
Binary files a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_10.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_12.jpg b/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_12.jpg
deleted file mode 100644
index 5876fd5..0000000
Binary files a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_12.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_6.jpg b/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_6.jpg
deleted file mode 100644
index 3ae1c83..0000000
Binary files a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_6.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_9.jpg b/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_9.jpg
deleted file mode 100644
index a44d275..0000000
Binary files a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230-KIT_9.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_1.jpg b/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_1.jpg
deleted file mode 100644
index a9f1bd4..0000000
Binary files a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_1.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_11.jpg b/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_11.jpg
deleted file mode 100644
index fbe7a81..0000000
Binary files a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_11.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_9.jpg b/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_9.jpg
deleted file mode 100644
index 0b30877..0000000
Binary files a/devices/lilygo/t-display-k230/media/LILYGO-T-DISPLAY-K230_9.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/manifest.json b/devices/lilygo/t-display-k230/media/manifest.json
deleted file mode 100644
index b104d10..0000000
--- a/devices/lilygo/t-display-k230/media/manifest.json
+++ /dev/null
@@ -1,260 +0,0 @@
-{
-  "schema": "hardware-doc/media-manifest/1",
-  "device": "lilygo/t-display-k230",
-  "compiled": "2026-09-04",
-  "note": "All images are vendor marketing or wiki material. No licence statement exists on either source; redistribution status is unknown and every file is held unstaged pending review. No teardown, PCB or third-party photograph was located \u2014 see media.md.",
-  "images": [
-    {
-      "file": "media/LILYGO-T-DISPLAY-K230_11.jpg",
-      "caption": "Bare board, primary product photo (angled, screen on)",
-      "alt_text": "LilyGO T-Display K230 bare board, angled, AMOLED lit",
-      "creator_rightsholder": "LILYGO (Shenzhen Xin Yuan Electronic Technology Co., Ltd)",
-      "source_page": "https://lilygo.cc/products/t-display-k230",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0617/7190/7253/files/LILYGO-T-DISPLAY-K230_11.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230 / T-Display K230 Kit, revision unknown",
-      "license": "unknown \u2014 vendor product photography, no licence statement on the store",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "7d34f5e6c62d9c3aad5b523d16caa98d53ad1160f8990b08f33be95cc9712b9a",
-      "bytes": 99683,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/LILYGO-T-DISPLAY-K230_9.jpg",
-      "caption": "Bare board, second marketing view",
-      "alt_text": "LilyGO T-Display K230 bare board, alternate view",
-      "creator_rightsholder": "LILYGO (Shenzhen Xin Yuan Electronic Technology Co., Ltd)",
-      "source_page": "https://lilygo.cc/products/t-display-k230",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0617/7190/7253/files/LILYGO-T-DISPLAY-K230_9.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230 / T-Display K230 Kit, revision unknown",
-      "license": "unknown \u2014 vendor product photography, no licence statement on the store",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "7ef6797e1c290e9090844dcdbf3381d5bfaba3dcb6bae0546c0727657b9dd20c",
-      "bytes": 81624,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/LILYGO-T-DISPLAY-K230_1.jpg",
-      "caption": "Bare board, product listing thumbnail",
-      "alt_text": "LilyGO T-Display K230 product thumbnail",
-      "creator_rightsholder": "LILYGO (Shenzhen Xin Yuan Electronic Technology Co., Ltd)",
-      "source_page": "https://lilygo.cc/products/t-display-k230",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0617/7190/7253/files/LILYGO-T-DISPLAY-K230_1.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230 / T-Display K230 Kit, revision unknown",
-      "license": "unknown \u2014 vendor product photography, no licence statement on the store",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "011b95623e7f193b5bc9db0a7322d5dc76797031c39a910d79647dbfb7c6e6b9",
-      "bytes": 35632,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/LILYGO-T-DISPLAY-K230-KIT_12.jpg",
-      "caption": "Kit, primary product photo \u2014 main unit plus keyboard base",
-      "alt_text": "T-Display K230 Kit, handheld with QWERTY keyboard base",
-      "creator_rightsholder": "LILYGO (Shenzhen Xin Yuan Electronic Technology Co., Ltd)",
-      "source_page": "https://lilygo.cc/products/t-display-k230-kit",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0617/7190/7253/files/LILYGO-T-DISPLAY-K230-KIT_12.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230 / T-Display K230 Kit, revision unknown",
-      "license": "unknown \u2014 vendor product photography, no licence statement on the store",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "b41b997c6bc09520b1c4cb0ced263298cde1c6c9efce8174e3e7caf09ecf52a2",
-      "bytes": 71865,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/LILYGO-T-DISPLAY-K230-KIT_9.jpg",
-      "caption": "Kit, second view",
-      "alt_text": "T-Display K230 Kit, alternate view",
-      "creator_rightsholder": "LILYGO (Shenzhen Xin Yuan Electronic Technology Co., Ltd)",
-      "source_page": "https://lilygo.cc/products/t-display-k230-kit",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0617/7190/7253/files/LILYGO-T-DISPLAY-K230-KIT_9.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230 / T-Display K230 Kit, revision unknown",
-      "license": "unknown \u2014 vendor product photography, no licence statement on the store",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "c7271b8069116c8fa69ad47eadb0c0c36b3a6d896ea53b25d9ebdf43a378d702",
-      "bytes": 43411,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/LILYGO-T-DISPLAY-K230-KIT_6.jpg",
-      "caption": "Kit, third view",
-      "alt_text": "T-Display K230 Kit, alternate view",
-      "creator_rightsholder": "LILYGO (Shenzhen Xin Yuan Electronic Technology Co., Ltd)",
-      "source_page": "https://lilygo.cc/products/t-display-k230-kit",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0617/7190/7253/files/LILYGO-T-DISPLAY-K230-KIT_6.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230 / T-Display K230 Kit, revision unknown",
-      "license": "unknown \u2014 vendor product photography, no licence statement on the store",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "38ec5ec16d8be986520a136bb317e8fa663889d5140bdacb3f5daf0009cc1cf2",
-      "bytes": 45688,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/LILYGO-T-DISPLAY-K230-KIT_10.jpg",
-      "caption": "Kit, fourth view",
-      "alt_text": "T-Display K230 Kit, alternate view",
-      "creator_rightsholder": "LILYGO (Shenzhen Xin Yuan Electronic Technology Co., Ltd)",
-      "source_page": "https://lilygo.cc/products/t-display-k230-kit",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0617/7190/7253/files/LILYGO-T-DISPLAY-K230-KIT_10.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230 / T-Display K230 Kit, revision unknown",
-      "license": "unknown \u2014 vendor product photography, no licence statement on the store",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "3628da0cb6eb85a8c064f81990c0c46b02d1e5075163f28dfd8aba4bf0e08513",
-      "bytes": 58382,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/t-display-k230-1.jpg",
-      "caption": "Wiki product image 1",
-      "alt_text": "T-Display K230 wiki product image",
-      "creator_rightsholder": "LILYGO",
-      "source_page": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/",
-      "direct_url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/index/image/t-display-k230-1.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230, revision unknown",
-      "license": "unknown \u2014 no licence statement on the wiki",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "69452f4aacdc726d3a5831a16cc02c1b59f2db51350ebd99688abbc1db0decf6",
-      "bytes": 259521,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/t-display-k230-2.jpg",
-      "caption": "Wiki product image 2",
-      "alt_text": "T-Display K230 wiki product image",
-      "creator_rightsholder": "LILYGO",
-      "source_page": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/",
-      "direct_url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/index/image/t-display-k230-2.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230, revision unknown",
-      "license": "unknown \u2014 no licence statement on the wiki",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "0a23c1dd875244d1c9560aef5829af488463d6bb91f97ec768c21cbb83ac00dc",
-      "bytes": 247954,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/t-display-k230-3.jpg",
-      "caption": "Wiki product image 3",
-      "alt_text": "T-Display K230 wiki product image",
-      "creator_rightsholder": "LILYGO",
-      "source_page": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/",
-      "direct_url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/index/image/t-display-k230-3.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230, revision unknown",
-      "license": "unknown \u2014 no licence statement on the wiki",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "16066595af4b059807e062438da2cb15e7820a4a865f3e6d5da763ea1e5ec423",
-      "bytes": 198759,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/t-display-k230-specifications.jpg",
-      "caption": "**Specification card** \u2014 the wiki's own annotated feature graphic",
-      "alt_text": "Annotated specification graphic for the T-Display K230",
-      "creator_rightsholder": "LILYGO",
-      "source_page": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/",
-      "direct_url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/index/image/t-display-k230-specifications.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230, revision unknown",
-      "license": "unknown \u2014 no licence statement on the wiki",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "38106425bc779d2d810d5bac16c5c96b89d531303f48b7d7b5c1d7009521f3aa",
-      "bytes": 344996,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/t-display-k230-cn.jpg",
-      "caption": "Chinese-market annotated feature graphic",
-      "alt_text": "Chinese-language annotated feature graphic",
-      "creator_rightsholder": "LILYGO",
-      "source_page": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/",
-      "direct_url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/index/image/t-display-k230-cn.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230, revision unknown",
-      "license": "unknown \u2014 no licence statement on the wiki",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "491de1860770625e7866b9687c6c0930bd4e873d06f8eef6e49f0436fb22f943",
-      "bytes": 474510,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/t-display-k230-40pin.jpg",
-      "caption": "**40-pin header pinout diagram**",
-      "alt_text": "Pinout diagram of the T-Display K230 2x20 expansion header",
-      "creator_rightsholder": "LILYGO",
-      "source_page": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/",
-      "direct_url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/index/image/t-display-k230-40pin.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230, revision unknown",
-      "license": "unknown \u2014 no licence statement on the wiki",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "dafb6abe992e70ea1b10e446963ea17efd2c3c2d6e41c2991ea3dd3275527437",
-      "bytes": 569301,
-      "content_type_verified": "JPEG (magic bytes)"
-    },
-    {
-      "file": "media/t-display-k230-keyboard-extension.jpg",
-      "caption": "**Keyboard extension board diagram**",
-      "alt_text": "Diagram of the T-Display K230 keyboard extension board",
-      "creator_rightsholder": "LILYGO",
-      "source_page": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/",
-      "direct_url": "https://wiki.lilygo.cc/products/t-display-series/t-display-k230/index/image/t-display-k230-keyboard-extension.jpg",
-      "published": "unknown",
-      "retrieved": "2026-09-04",
-      "applies_to": "T-Display K230, revision unknown",
-      "license": "unknown \u2014 no licence statement on the wiki",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged)",
-      "modifications": "none \u2014 byte-identical to the fetched original",
-      "sha256": "55bce96b52ca27216211e31d1784a3f29deb202db7096c3d4de9cebc29a6e769",
-      "bytes": 481088,
-      "content_type_verified": "JPEG (magic bytes)"
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/lilygo/t-display-k230/media/t-display-k230-1.jpg b/devices/lilygo/t-display-k230/media/t-display-k230-1.jpg
deleted file mode 100644
index f96abd0..0000000
Binary files a/devices/lilygo/t-display-k230/media/t-display-k230-1.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/t-display-k230-2.jpg b/devices/lilygo/t-display-k230/media/t-display-k230-2.jpg
deleted file mode 100644
index edfcd64..0000000
Binary files a/devices/lilygo/t-display-k230/media/t-display-k230-2.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/t-display-k230-3.jpg b/devices/lilygo/t-display-k230/media/t-display-k230-3.jpg
deleted file mode 100644
index 4dcddcf..0000000
Binary files a/devices/lilygo/t-display-k230/media/t-display-k230-3.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/t-display-k230-40pin.jpg b/devices/lilygo/t-display-k230/media/t-display-k230-40pin.jpg
deleted file mode 100644
index 612436b..0000000
Binary files a/devices/lilygo/t-display-k230/media/t-display-k230-40pin.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/t-display-k230-cn.jpg b/devices/lilygo/t-display-k230/media/t-display-k230-cn.jpg
deleted file mode 100644
index 042fecb..0000000
Binary files a/devices/lilygo/t-display-k230/media/t-display-k230-cn.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/t-display-k230-keyboard-extension.jpg b/devices/lilygo/t-display-k230/media/t-display-k230-keyboard-extension.jpg
deleted file mode 100644
index 11df5fa..0000000
Binary files a/devices/lilygo/t-display-k230/media/t-display-k230-keyboard-extension.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/media/t-display-k230-specifications.jpg b/devices/lilygo/t-display-k230/media/t-display-k230-specifications.jpg
deleted file mode 100644
index d33a4d5..0000000
Binary files a/devices/lilygo/t-display-k230/media/t-display-k230-specifications.jpg and /dev/null differ
diff --git a/devices/lilygo/t-display-k230/performance.md b/devices/lilygo/t-display-k230/performance.md
deleted file mode 100644
index 9c4dcf5..0000000
--- a/devices/lilygo/t-display-k230/performance.md
+++ /dev/null
@@ -1,108 +0,0 @@
-# T-Display K230 — performance
-
-**There is no independent performance measurement of this board. None. In any source searched.**
-
-That statement is the most important content on this page, so it comes first. What follows
-separates what Canaan claims about the silicon from what is known about the board, and says
-exactly how to close the gap.
-
-## 1. Silicon claims — vendor figures, not measurements
-
-From Canaan's K230 datasheet and brief datasheet. These are **official claims** produced under
-Canaan's own build and configuration, on Canaan's own boards.
-
-| Workload | Claim |
-|---|---|
-| ResNet-50 INT8 (KPU) | **≥ 85 fps** |
-| MobileNet v2 INT8 (KPU) | **≥ 670 fps** |
-| YOLOv5s INT8 (KPU) | **≥ 38 fps** |
-| Video encode | H.264/H.265, **8 MP @ 20 fps** |
-| Video decode | H.264/H.265, **8 MP @ 40 fps** |
-| ISP throughput | **8 MP @ 30 fps** |
-| DPU depth | 1280×800 @ 30 fps · 1280×1080 @ 15 fps · 1920×1080 @ 9 fps |
-| 2D GDMA rotation | 2 × 1080×1280 YUV400 @ 15 fps **+** 1 × 1080×1920 YUV420 @ 30 fps |
-| GZIP decompression | **≥ 400 MB/s** |
-| 4096-point FFT/IFFT | **≤ 1 ms** including data movement and interrupt |
-| Boot to first 3A image | **≤ 400 ms** |
-| Deep-sleep standby | **≤ 20 µW** |
-| Operating temperature | −40 … +85 °C |
-
-**No CoreMark or DMIPS figure is published for the K230 by Canaan.** Compare
-[ESP32-P4](../../../components/espressif/esp32-p4/README.md), where Espressif quotes
-6.92 CoreMark/MHz.
-
-**No TOPS figure is published either.** LilyGO's wiki says "up to 1.6 TOPS"; a Reddit commenter
-said "abt 17 tops". Neither number appears in any Canaan document. Use the fps figures.
-
-## 2. What is known about *this board*
-
-| Metric | Value | Class |
-|---|---|---|
-| CPU1 clock | 1.6 GHz | vendor spec |
-| CPU0 clock | 800 MHz | vendor spec |
-| RAM | 1 GB LPDDR4, 32-bit | vendor spec — but see [`GC-7`](gaps-and-conflicts.md) |
-| Ethernet | 100 Mbit/s ceiling | vendor spec |
-| Wi-Fi | 802.11n, 2.4 GHz only | vendor spec |
-| USB charge input | 5 V, 500 mA | vendor spec |
-| **Everything else** | **unmeasured** | — |
-
-Unmeasured and unpublished: boot time, LVGL frame rate, display refresh rate, camera capture
-latency, Wi-Fi throughput, Ethernet throughput, SD throughput, LoRa range and TX current, KPU
-inference latency on this board, thermal behaviour under load, **and battery life under any
-workload whatsoever.**
-
-## 3. The board ships with benchmarks nobody has run
-
-This is the striking part. The Buildroot configuration contains:
-
-```
-BR2_PACKAGE_COREMARK=y
-BR2_PACKAGE_COREMARK_PRO=y
-```
-
-**CoreMark and CoreMark-PRO are built into every image LilyGO produces**, and no CoreMark result
-for this board exists anywhere. A single command on a running unit would produce the first
-published number.
-
-Also built in and unused for measurement: `evtest`, `linux-tools-gpio`, `alsa-utils`, plus
-LilyGO's own `drm_motion_probe.c`, `lvgl_scroll_probe.c` and `lora_flrc_bench.cpp` — three
-purpose-built probes whose outputs have never been published.
-
-## 4. Reasoning that is *not* measurement
-
-One community comparison is worth recording because it is the only quantitative reasoning found,
-and it is **informed interpretation, not a measurement** (r/meshtastic, 2025-07-09):
-
-> "This board has 1G ram and a 1.6GHz RVV1 'big' core. It's basically more powerful than the
-> 1GHz non RVV core in my MQ-Pro, and has 8x the memory."
-
-Comparing to the Allwinner D1 in a MangoPi MQ-Pro: the clock ratio (1.6× ) and the memory ratio
-(8×) are both correct arithmetic on published specifications, and RVV 1.0 versus the D1's draft
-RVV 0.7.1 is a real architectural difference. **But it is inference from specifications, and
-specification-derived performance claims are exactly what this repository does not accept as
-measurement.** Recorded, labelled, not promoted.
-
-## 5. What would close the gap — a concrete protocol
-
-Every command below runs on the shipped image with no additional software. Anyone with hardware
-could produce all of it in an afternoon, and it would be the first performance data that exists
-for this product.
-
-| Measurement | Command | Record alongside |
-|---|---|---|
-| CPU | `coremark` (and `coremark-pro`) | which core it ran on (`taskset`), governor, clock, ambient |
-| Memory | `sysbench`/`mbw` if added, else a simple `dd` to `/dev/null` from tmpfs | frequency, single vs dual channel |
-| Boot time | `systemd-analyze` if present, else timestamped `dmesg` | to first LVGL frame, not just to shell |
-| Display | `lvgl_scroll_probe`, `drm_motion_probe` | resolution, colour format, buffering |
-| SD | `dd` and `fio` if added | card make/model/class — **this dominates the result** |
-| Wi-Fi | `iperf3` | AP model, distance, band, channel width, RSSI |
-| Ethernet | `iperf3` | link speed, switch |
-| KPU | run the shipped face-detect at a fixed resolution and time it | nncase version, model, input size |
-| Camera | timestamp V4L2 buffer dequeues | resolution, format, ISP settings |
-| **Battery** | log BQ27220 voltage/current/SoC over a defined workload | **cell capacity, screen brightness, radios on/off** — without these the number means nothing |
-| Thermal | read the Canaan thermal sensor under sustained load | ambient, warm-up time, duration, throttling observed |
-| Power | external meter at the USB-C input | measurement point and instrument |
-
-**Do not merge results across different SD cards, different image versions or different
-governors into one ranking.** The single largest confounder on this board is the SD card, because
-the card is the root filesystem.
diff --git a/devices/lilygo/t-display-k230/pinouts-and-buses.md b/devices/lilygo/t-display-k230/pinouts-and-buses.md
deleted file mode 100644
index e2a90b3..0000000
--- a/devices/lilygo/t-display-k230/pinouts-and-buses.md
+++ /dev/null
@@ -1,247 +0,0 @@
-# T-Display K230 — pinouts, buses and addresses
-
-**All tables below are reproduced from LilyGO's own `k230_bsp/docs/HARDWARE_PINMAP.md` at commit
-`bb831ab358b66f5bd9a87ecd7c580fee4537492e` (2026-09-03) unless a different source is named.**
-That document is the board's authoritative pin map; there is **no published schematic** to
-cross-check it against ([`GC-5`](gaps-and-conflicts.md)). Where the Canaan reference device tree
-adds detail, it is cited as `C3`.
-
-Evidence status for every row here: **`reported-working`** — LilyGO states these are the
-assignments its shipped BSP uses, and the corresponding device-tree patches exist in the same
-repository. **None has been verified against hardware.**
-
----
-
-## 1. 40-pin expansion header (2 × 20)
-
-Orientation: **USB-C facing down; the left column below is the physical left side.**
-
-| Left | Right |
-|---|---|
-| `ADC0` | `ADC2` |
-| `ADC1` | `GND` |
-| `GPIO47` | `GPIO43` |
-| `GPIO14` | `GPIO46` |
-| `GPIO17` | `GPIO18` |
-| `GPIO53` | `GPIO52` |
-| `GPIO33` | `GPIO62` |
-| `GPIO34` | `GPIO32` |
-| `GPIO29` | `GPIO31` |
-| `GPIO28` | `GPIO30` |
-| `GPIO6` | `GPIO26` |
-| `GPIO3` | `GPIO5` |
-| `GPIO63` | `GPIO27` |
-| `GPIO35` | `GPIO4` |
-| `GPIO45` | `GPIO2` |
-| `GPIO44` | `GPIO42` |
-| `GPIO15` | `GPIO16` |
-| `GPIO19` | `GPIO20` |
-| `5V` | `3V3` |
-| `GND` | `USB-IN-5V` |
-
-**The header is not "spare I/O".** Read it against §2 and §3: `GPIO14/15/16/17/19/20/44` are the
-LoRa SPI, `GPIO3/4` are the nRF52840 UART, `GPIO28/29` are the nRF9151 UART, `GPIO2` is the
-nRF9151 enable, `GPIO42/43` are the keyboard IRQ and reset, `GPIO46/47` are the shared I²C4 bus,
-`GPIO32/33/34/35` are the I²S path, and `GPIO52` is the keyboard backlight PWM. **The base
-boards plug into this header and claim most of it.** Genuinely uncommitted pins are
-`GPIO6`, `GPIO18`, `GPIO26`, `GPIO27`, `GPIO30`, `GPIO31`, `GPIO45`, `GPIO53`, `GPIO62`,
-`GPIO63`, plus `ADC0/1/2`.
-
-Three analogue inputs (`ADC0`, `ADC1`, `ADC2`) are exposed. The K230 datasheet does not
-enumerate an ADC in its peripheral list, so their electrical characteristics are **unknown**
-([`GC-8`](gaps-and-conflicts.md)).
-
----
-
-## 2. K230 main board
-
-| Function | K230 signal | Dir | Peripheral signal | Notes |
-|---|---|---|---|---|
-| BOOT0 button | `GPIO0` | in | button | **Idle high, pressed low.** The launcher repurposes it as a screen/backlight toggle. |
-| PMU INT0 / power key | `GPIO64` | PMU in | PMU input channel 0 | **Not a normal GPIO.** **Idle low, pressed high** — inverted relative to BOOT0. Reaches userspace through the `k230-pmu-pwrkey` input driver. |
-| RM69A10 AMOLED | `GPIO22` | out | panel **reset** | Used by both the U-Boot logo path and Linux bring-up |
-| RM69A10 AMOLED | `GPIO25` | out | panel **enable** | Boot logo + launcher backlight/display enable |
-| RM69A10 AMOLED | MIPI DSI | out | display data | Default output. **Validated LVGL path is RGB565.** |
-| GT9895 touch | `GPIO37` | I²C SDA | touch SDA | ⚠ shared with LT9611 |
-| GT9895 touch | `GPIO36` | I²C SCL | touch SCL | address **`0x5D`** |
-| GT9895 touch | `GPIO23` | in | touch IRQ | ⚠ shared with LT9611 IRQ |
-| GT9895 touch | `GPIO24` | out | touch reset | ⚠ shared with LT9611 reset |
-| LT9611 HDMI bridge | `GPIO37`/`GPIO36`/`GPIO23`/`GPIO24` | — | SDA/SCL/IRQ/RST | **Optional path.** Same four lines as touch. |
-| GC2093 camera | `GPIO49` | I²C SDA | camera SDA | address **`0x37`** |
-| GC2093 camera | `GPIO48` | I²C SCL | camera SCL | |
-| GC2093 camera | MIPI CSI | in | camera data | preview, capture, RTSP, AI camera |
-| microSD | `GPIO54` | SDIO CMD | SD CMD | **boot + storage** |
-| microSD | `GPIO55` | SDIO CLK | SD CLK | |
-| microSD | `GPIO56`…`GPIO59` | SDIO D0–D3 | SD D0–D3 | |
-| Wi-Fi | SDIO | I/O | RTL8189FS or RTL8723DS | "RTL8723DS Bluetooth requires separate BT UART hardware signals; **SDIO covers Wi-Fi only**" |
-| USB host | USB | I/O | USB Ethernet, USB modem, USB Bluetooth | root filesystem carries the drivers |
-| LoRa | `GPIO16` | SPI MOSI | MOSI | |
-| LoRa | `GPIO17` | SPI MISO | MISO | |
-| LoRa | `GPIO15` | SPI SCLK | SCK | |
-| LoRa | `GPIO14` | out | CS | |
-| LoRa | `GPIO5` | out | RESET | driven by the RadioLib HAL |
-| LoRa | `GPIO19` | in | BUSY | |
-| LoRa | `GPIO20` | in | IRQ | **SX1262 → `DIO1`; LR2021 → `DIO11`.** Same K230 pin, different radio pin. |
-| LoRa | `GPIO44` | out | power enable | enables the module's power path |
-
----
-
-## 3. nRF52840 BLE / audio / sensor base board
-
-| Base-board function | Base signal | K230 signal | Dir from K230 | Notes |
-|---|---|---|---|---|
-| nRF52840 UART | `P0.11` / Arduino 11 (RX) | `GPIO3` / UART1 TX | out | K230 → nRF52840, `/dev/ttyS1`, **115200 8N1** |
-| nRF52840 UART | `P0.12` / Arduino 12 (TX) | `GPIO4` / UART1 RX | in | AT responses and BLE events |
-| nRF52840 LED | `P1.00` / Arduino 32 | — | (nRF out) | blue activity LED on the nRF52840 board |
-| **5 V boost enable** | `P0.04` / Arduino 4 | — | (nRF out) | **Boosts the 21700 battery compartment to a stable 5 V for the host unit.** Source: the nRF52840 firmware README, not the pin map. |
-| nRF52840 debug | USB CDC | host PC | I/O | 115200; **some monitors need DTR asserted** |
-| AHT20 | SCL | `GPIO46` / I²C4 SCL | I²C | **`0x38`** |
-| AHT20 | SDA | `GPIO47` / I²C4 SDA | I²C | shared expansion bus |
-| MAX98357A | `DIN` | `GPIO35` / I²S data | out | |
-| MAX98357A | `BCLK` | `GPIO32` / I²S BCLK | out | |
-| MAX98357A | `LRCK`/`WS` | `GPIO33` / I²S LRCK | out | |
-| MAX98357A | shutdown | `GPIO34` | out | **high = enabled** |
-
----
-
-## 4. nRF9151 cellular / GNSS / keyboard base board
-
-| Base-board function | Base signal | K230 signal | Dir from K230 | Notes |
-|---|---|---|---|---|
-| nRF9151 enable | power enable | `GPIO2` | out | **drive high to enable** |
-| nRF9151 UART1 | `P0.26` / RX1 | `GPIO28` / UART3 TX | out | `/dev/ttyS3`, **115200 8N1, no flow control** |
-| nRF9151 UART1 | `P0.27` / TX1 | `GPIO29` / UART3 RX | in | AT responses + URCs |
-| nRF9151 debug UART2 | `P0.29` / TX2 | external USB-UART RX | (nRF out) | optional Serial LTE Modem log |
-| nRF9151 debug UART2 | `P0.28` / RX2 | external USB-UART TX | (nRF in) | optional |
-| nRF9151 LED | `P0.23` | — | (nRF out) | blue LED **inside the PCB**; GNSS fix → 1 s cadence, ~300 ms on |
-| BQ25896 charger | SCL/SDA | `GPIO46`/`GPIO47` | I²C4 | **`0x6B`** |
-| BQ27220 gauge | SCL/SDA | `GPIO46`/`GPIO47` | I²C4 | **`0x55`** |
-| TCA8418 keyboard | SCL/SDA | `GPIO46`/`GPIO47` | I²C4 | **`0x34`** (7-bit, as Linux uses it) |
-| TCA8418 keyboard | RESET | `GPIO43` | out | |
-| TCA8418 keyboard | IRQ | `GPIO42` | in | |
-| XL9555 expander | SCL/SDA | `GPIO46`/`GPIO47` | I²C4 | **`0x20`–`0x27`; software probes and caches** |
-| Keyboard backlight | PWM | `GPIO52` / **PWM4** | out | userspace drives brightness |
-
----
-
-## 5. I²C address map
-
-| Bus | K230 pins | 7-bit addr | Device | Board |
-|---|---|---|---|---|
-| I²C0 | `GPIO48` SCL / `GPIO49` SDA | `0x37` | GC2093 camera | main |
-| I²C3 | `GPIO36` SCL / `GPIO37` SDA | `0x5D` | GT9895 touch | main |
-| I²C3 | same | ? | LT9611 HDMI bridge (if fitted) | main |
-| **I²C4** | `GPIO46` SCL / `GPIO47` SDA | `0x34` | TCA8418 keyboard | nRF9151 base |
-| I²C4 | same | `0x38` | AHT20 | nRF52840 base |
-| I²C4 | same | `0x55` | BQ27220 gauge | nRF9151 base |
-| I²C4 | same | `0x6B` | BQ25896 charger | nRF9151 base |
-| I²C4 | same | `0x20`–`0x27` | XL9555 expander | nRF9151 base |
-
-I²C4 is also exposed on the 40-pin header, so **anything you attach there shares a bus with the
-keyboard scanner and the power-management chips.** An address collision in `0x20–0x27` is the
-most likely accident, because the XL9555's address is not fixed.
-
-The launcher ships an **I²C scanner** (`ui_i2c_scan.c`; v0.2.4 made it asynchronous and
-multi-bus) — use it before assuming anything on a board in hand.
-
----
-
-## 6. IO bank voltages — the hardware-damage path
-
-Canaan's reference device tree (`C3`) sets a `MSC` (voltage) field per bank and carries the
-comment:
-
-> `// Please pay attention to the bank voltage! will damage the chip.`
-
-| Bank | Reference-design setting |
-|---|---|
-| `IO0`–`IO1` | **`K230_MSC_1V8` — FIXED** |
-| `IO2`–`IO13` | `K230_MSC_3V3` |
-| `IO14`–`IO25` | `K230_MSC_3V3` |
-| `IO26`–`IO37` | `K230_MSC_3V3` |
-| `IO38`–`IO49` | `K230_MSC_3V3` |
-| `IO50`–`IO61` | `K230_MSC_3V3` |
-| `IO62`–`IO63` | `K230_MSC_3V3` |
-
-`IO0`/`IO1` are the **BOOT0/BOOT1 strapping pins** and are fixed at 1.8 V. Note that the pin map
-describes the **BOOT0 button on `GPIO0`** and the reference DTS configures `IO0` as *output with
-pull-up* — the button and the strap are the same pin, which is normal but worth knowing before
-attaching anything to it.
-
----
-
-## 7. UART summary
-
-| Linux device | K230 pins | Peer | Rate |
-|---|---|---|---|
-| `/dev/ttyS0` | `IO38` TX / `IO39` RX (reference DTS) | console | typically 115200 |
-| `/dev/ttyS1` | `GPIO3` TX / `GPIO4` RX | **nRF52840** | 115200 8N1 |
-| `/dev/ttyS3` | `GPIO28` TX / `GPIO29` RX | **nRF9151** | 115200 8N1, no flow control |
-
-Enabled by `0060-riscv-dts-rm69a10-enable-uart1-nrf52840.patch` and
-`0061-riscv-dts-rm69a10-enable-uart3-nrf9151.patch` respectively.
-
----
-
-## 8. Keyboard matrix — full decode
-
-Source: `k230_launcher/k230_phone_ui/src/ui_hardware.c`, same commit. Scanner is a
-**TCA8418 configured `TCA8418_ROWS 7` × `TCA8418_COLS 10`**; the *displayed* layout is
-`KEYBOARD_LAYOUT_ROWS 6` × `KEYBOARD_LAYOUT_COLS 11`. Key code → (row, col) is
-`row = (code-1)/10`, `col = (code-1)%10`.
-
-Physical layout as the launcher draws it, by key code:
-
-| | | | | | | | | | | |
-|---|---|---|---|---|---|---|---|---|---|---|
-| `50` F1 | `60` F2 | `59` F3 | `68` F4 | `67` F5 | `66` F6 | `65` F7 | `64` F8 | `63` F9 | `62` F10 | `61` F11 |
-| `40` ESC | `49` 1 | `48` 2 | `58` 3 | `57` 4 | `56` 5 | `55` 6 | `54` 7 | `53` 8 | `52` 9 | `51` 0 |
-| `20` Q | `39` W | `38` E | `37` R | `47` T | `46` Y | `45` U | `44` I | `43` O | `42` P | `41` DEL |
-| `10` CAPS | `29` A | `28` S | `27` D | `26` F | `36` G | `35` H | `34` J | `33` K | `32` L | `21` ENTER |
-| `19` ALT | `18` Z | `17` X | `16` C | `15` V | `25` B | `24` N | `13` M | `23` CTRL | `22` UP | `11` MIC |
-| `9` FN | `8` LILYGO | `7` SHIFT | `6` TAB | `5` SPACE | `14` SPACE | `3` FN-R | `2` LEFT | `12` DOWN | `1` RIGHT | `0` — |
-
-Notes that matter when writing a driver:
-
-- **Two `SPACE` codes** (`5` and `14`) — a wide spacebar spanning two matrix intersections.
-- **Two `FN` keys**: `9` (`FN`, left) and `3` (`FN-R`, right). `extension_keyboard_fn_pressed()`
-  returns true for either.
-- A dedicated **`LILYGO`** key (code `8`) and a dedicated **`MIC`** key (code `11`).
-- Code `0` is not a key; TCA8418 key codes are 1-based.
-- Only `UP`/`DOWN`/`LEFT`/`RIGHT` arrows exist as codes `22`/`12`/`2`/`1` — arranged in the
-  bottom two rows, not as a cluster.
-- **11 F-keys**, each remappable: preference key `keyboard.hotkey.f<N>`. Defaults changed in BSP
-  v0.2.4 to **F3/F4 = keyboard backlight down/up, F7 = screenshot**.
-- `FN+B` toggles the keyboard backlight.
-- ESC-as-back is a preference (`keyboard.esc_back`, default on).
-- Key repeat: **450 ms** to first repeat, then **85 ms** period.
-
-TCA8418 registers the launcher touches: `CFG 0x01`, `INT_STAT 0x02`, `KEY_LCK_EC 0x03`,
-`KEY_EVENT_A 0x04`, `KP_GPIO_1/2/3 0x1D/0x1E/0x1F`, `DEBOUNCE_DIS_1/2/3 0x29/0x2A/0x2B`.
-Configuration mode is `KE_IEN | OVR_FLOW_IEN | OVR_FLOW_M` when IRQ mode is enabled
-(`K230_TCA8418_USE_IRQ 1`, the default), otherwise `OVR_FLOW_M` alone with polling.
-
-The launcher also **rewrites the K230 IOMUX for `GPIO42` directly** —
-`TCA8418_IRQ_IOMUX_IO42_OFFSET (42*4)`, value `0x00000344` — to force it to GPIO input mode.
-That is userspace reaching into the pin controller behind the kernel's back, and it is worth
-knowing about if you see the IRQ line behave unexpectedly after another driver claims it.
-
----
-
-## 9. PMU power-key register flow
-
-The `k230-pmu-pwrkey` driver (added by `0064-input-k230-pmu-pwrkey.patch`, 21 523 bytes) states
-that its register flow "mirrors the RT-Thread PMU pwrkey driver": route PMU `KEY_EDGE` to
-**CPU IRQ 175**, start with rising-edge detection, and on shutdown program INT0 long-press
-wakeup and ask the PMU to cut power.
-
-Registers used: `PMU_STATUS 0x3c`, `INT0_TO_CTL 0x40`, `INT1_TO_CTL 0x44`, `INT0_TO_CPU 0x48`,
-`INT_DETECT_EN 0x4c`, `INT_DETECT_TYP 0x50`, `INT_DETECT_CLR 0x54`,
-`INT0_LONG_PRESS_TRIGGER_VAL 0x58`, `INT0_LEVEL_DEBOUNCE_VAL 0x64`, `SYSCTRL_REG 0x78`,
-`OUT_EVENT_CTRL 0xa4`, `OUT_LOGIC_CTRL 0xa8`, `INT_STATE_REG 0xac`, and
-`PWR_PMU_PWR_ISO_CTRL_REG 0x158`. Node address `pmu-pwrkey@91000000`, `reg-names = "pmu", "pwr"`.
-
-Launcher-side constants: long-press `96000` ticks, debounce `256` ticks.
-
-Canaan's `K230_PMU_User_Guide.md` is retained at
-[`components/canaan/k230/artifacts/K230_PMU_User_Guide.md`](../../../components/canaan/k230/artifacts/K230_PMU_User_Guide.md).
diff --git a/devices/lilygo/t-display-k230/product-history-and-family.md b/devices/lilygo/t-display-k230/product-history-and-family.md
deleted file mode 100644
index d7fc82a..0000000
--- a/devices/lilygo/t-display-k230/product-history-and-family.md
+++ /dev/null
@@ -1,111 +0,0 @@
-# T-Display K230 — product history, family and lineage
-
-## Timeline
-
-Every row is dated from a primary source; Shopify `created_at`/`published_at` values are exact to
-the minute in `+08:00` (LilyGO's timezone) and are the strongest dating evidence available.
-
-| Date | Event | Source |
-|---|---|---|
-| 2018 | Kendryte **K210** — the line's origin: dual RV64GC @ 400 MHz, on-die SRAM, no DDR | — |
-| 2021-07-09 | Kendryte **K510** — tri-core RISC-V, up to 3 TOPS | CNX-Software |
-| **2023-07-06** | **K230 datasheet V1.0** | Canaan, document revision date |
-| 2023-09-15 / 2023-10-11 | CanMV-K230 board documents dated in `k230_docs` | Canaan repository |
-| 2023-10-18 / 2023-10-24 | CanMV-K230 covered on r/RISCV and CNX-Software | community, blog |
-| 2023-12-15 | "How to run baremetal program on a Canaan Kendryte K230 development board?" | r/RISCV |
-| 2024-05-08 | "**Where do people buy CANMV K230 from?**" — sourcing difficulty | r/RISCV |
-| 2024-05-09 | "Kendryte K230 (RVV1.0 supported) available for remote access" | r/RISCV |
-| 2024-11-18 | **BPI-CanMV-K230D-Zero at $29** | CNX-Software |
-| 2024-12-03 | `intx82/k230-debian` last push | GitHub |
-| **2025-03-21 13:52 +08** | **T-Display K230 created on lilygo.cc** | Shopify `created_at` |
-| **2025-03-21 14:22 +08** | **T-Display K230 published** — 30 minutes later | Shopify `published_at` |
-| 2025-03-21 | Announced on **r/LilyGO** | Reddit |
-| 2025-03-24 | First user questions: "can it run linux?" · "I'd really like to see more options to add external antennas for wifi, lora and gps" | Reddit |
-| 2025-03-25 | LilyGO answers "Yes" and links Canaan's developer site | Reddit |
-| **2025-03-26** | **oreboot maintainer**: oreboot supports K230, boots Linux from mask ROM over USB in ~3 s; also "**Already sold out**" | Reddit |
-| 2025-03-27 | LilyGO: "sales will resume soon" | Reddit |
-| 2025-04-25 | "T-Display K230, integrated AMOLED display and can run Linux or RTOS" | r/LilyGO |
-| 2025-07-04 | "T-Display K230 and T-Lora Pager have some stock available" | r/LilyGO |
-| **2025-07-07** | **r/meshtastic post — 187 points, 40 comments.** The product's largest moment of public attention, and it came from the *mesh* community, not the RISC-V one | Reddit |
-| 2025-07-09 | `k230-debian` and MQ-Pro comparison raised in that thread | Reddit |
-| 2026-05-10 | "any support for meshtastic yet?" | Reddit |
-| **2026-06-02** | "I am working on a **full Meshtastic UI app** for this and will publish a repo once complete" | Reddit |
-| **2026-07-28** | **Keyboard announced** on r/LilyGO; LilyGO confirms the P4 keyboard is separate and "already in production" | Reddit |
-| **2026-08-06 09:31 +08** | **T-Display K230 Kit created** | Shopify |
-| **2026-08-13 02:10 UTC** | **`Xinyuan-LilyGO/T-Display-K230` repository created** | GitHub |
-| 2026-08-13 | Owner confirms the keyboard ships **without** a case for the main board | Reddit |
-| 2026-08-13 06:52 UTC | `T-Display-K230-nRF52840` repository created | GitHub |
-| 2026-08-14 02:59 UTC | `T-Display-K230-nRF9151` repository created | GitHub |
-| 2026-08-16 | nRF52840 AT firmware build **`r4`** | firmware filename |
-| **2026-08-20 15:10 +08** | **T-Display K230 Kit published**; announced on r/LilyGO (83 points) | Shopify, Reddit |
-| 2026-08-20 | Owner: received bare board on risers, "completely unable to figure out how to even get an OS installed" | Reddit |
-| **2026-08-21** | **Owner reports bricking the board** | Reddit |
-| 2026-08-21 | LilyGO responds, links the new repository and wiki | Reddit |
-| 2026-08-23 | nRF52840 repository last push | GitHub |
-| 2026-08-25 | LilyGO points a user to the **T-Display P4 keyboard** product page | Reddit |
-| 2026-08-28 | Same owner: "my board is still unresponsive to boot pin and term" | Reddit |
-| **2026-09-03** | **BSP v0.2.4** — PicoClaw, Meshtastic map tiles, storage expansion, async I²C scan, new F-key defaults | CHANGELOG |
-| 2026-09-04 | This research snapshot | — |
-
-## The seventeen-month gap
-
-The board went on sale **2025-03-21**. Its board-support repository was created **2026-08-13** —
-**almost seventeen months later.** Everything a developer needs (the pin map, the kernel patches,
-the launcher, the build scripts, the companion firmware) arrived in that three-week burst in
-August 2026, at the same time as the keyboard.
-
-That single fact explains almost every negative community report. The people who bought in 2025
-had a beautiful screen, a RISC-V chip, and nothing else. One of them wrote in August 2026: *"The
-problem is I haven't been able to find anyone developing for this board, and RISC-V chips
-typically have very finicky bootloaders where you can't just install any common OS."* He was
-right at the time.
-
-It also means **the product you can buy today is materially different from the product reviewed
-or discussed in 2025**, even though the hardware SKU `K256` is unchanged. Treat any pre-August-2026
-commentary as describing a different situation.
-
-## Family
-
-### Within the T-Display series
-
-| Product | SoC | Relationship |
-|---|---|---|
-| **T-Display K230** | Kendryte K230 (RISC-V) | this record |
-| **T-Display P4** | Espressif ESP32-P4 | The direct sibling — same series, same idea, MCU class instead of application class. **Its keyboard is incompatible with the K230's, in both directions** (LilyGO, 2026-07-28). Its keyboard was "already in production" on 2026-07-28 and on sale by 2026-08-25. |
-| T-Display-S3 and its many AMOLED/Long/Pro variants | ESP32-S3 | The volume products of the series. Documented separately in this repository by another session, expected at `devices/lilygo/t-display-s3*`. Not present at the time of writing, so no link is given. |
-| T-Display-Keyboard | ESP32-D0WDQ6 | **A name trap.** An old ESP32 T-Display in a keyboard shell, with a 1.14″ 240 × 135 ST7789V. Nothing to do with the K230 keyboard. |
-| T-Display C5, Bar, SF32, AMOLED-Lite | various | Same series, unrelated |
-
-### The other LilyGO keyboard handhelds
-
-**T-Deck**, **T-Deck Plus**, **T-Deck Pro**, **T-Deck MAX** are a *different series* — all
-ESP32-S3, all with the small BlackBerry-style trackball keyboard. The T-Display K230 Kit is not a
-T-Deck and does not share its keyboard, its firmware or its ecosystem. Community members
-repeatedly compare the two on Wi-Fi quality and form factor, which is fair, but they are not
-variants of each other.
-
-### Other K230 hardware
-
-| Board | Vendor | Variant | RAM |
-|---|---|---|---|
-| CanMV-K230 | Canaan | K230 | 512 MB |
-| K230 DEMO BOARD (LP3) / USIP EVB (LP4) | Canaan | K230 | — |
-| K230-SIP-EVB | Canaan | K230D | 128 MB |
-| BPI-CanMV-K230D-Zero | Banana Pi | K230D | 128 MB |
-| **T-Display K230** | LilyGO | K230 | **1 GB** |
-
-**The LilyGO board has the most RAM of any published K230 board** — 2× the reference board and 8×
-the SiP boards. Given that memory is the binding constraint on a K230 running Linux, that is the
-board's strongest technical differentiator and it is not advertised as one.
-
-## Culture
-
-Three characteristics, each evidenced above:
-
-1. **Ship first, document later.** Seventeen months, then everything at once.
-2. **Support happens on Reddit.** `u/LilyGoXinyuan` answered on 2025-03-25, 2025-03-27,
-   2026-07-28, 2026-08-21 and 2026-08-25 — usually within a day, usually with a GitHub link. For
-   a product this new the subreddit is a better support channel than the wiki.
-3. **Rapid iteration once started.** v0.2.2 → v0.2.4 inside the first three weeks, with the
-   changelog entries showing real responsiveness (low-battery defaults tuned, nRF52840 ownership
-   arbitration added, MTP layout fixed, F-key defaults changed).
diff --git a/devices/lilygo/t-display-k230/projects-and-community.md b/devices/lilygo/t-display-k230/projects-and-community.md
deleted file mode 100644
index 66fcfc7..0000000
--- a/devices/lilygo/t-display-k230/projects-and-community.md
+++ /dev/null
@@ -1,207 +0,0 @@
-# T-Display K230 — software projects and community
-
-Every firmware, SDK and project targeting this board or the K230 generally, with repository,
-pinned revision, licence, build route and board-support status. Then the community record, with
-each contribution labelled by evidence type.
-
----
-
-## Part 1 — Software projects
-
-### Targeting this board specifically
-
-| Project | Repository | Revision | Licence | Build | Board support |
-|---|---|---|---|---|---|
-| **T-Display-K230 BSP + launcher** | `Xinyuan-LilyGO/T-Display-K230` | `bb831ab358b66f5bd9a87ecd7c580fee4537492e` (`main`), 2026-09-03, **v0.2.4** | ⚠ **none declared** | `./scripts/{setup_ubuntu,apply_to_sdk,build_sdcard_image}.sh` | **Complete** — this *is* the board's software |
-| **nRF52840 AT firmware** | `Xinyuan-LilyGO/T-Display-K230-nRF52840` | `4646a728580739d487126f47a521e9b8032b3c2c` (`master`), 2026-08-23 | ⚠ **none declared** | PlatformIO `nordicnrf52` / `nrf52840_dk_adafruit` | Complete; prebuilt UF2 (`r4`, 2026-08-16) and bootloader shipped |
-| **nRF9151 Serial LTE Modem** | `Xinyuan-LilyGO/T-Display-K230-nRF9151` | `ed4ecbe34162dec9b81213a400198125bbd6e36f` (`main`), 2026-08-14 | ⚠ **none declared** | NCS v3.4.0 + `./build_serial_modem.sh` | Complete; source only, no prebuilt |
-| **T-Display-K230_canmv_rt** | `Xinyuan-LilyGO/T-Display-K230_canmv_rt` | `main`, 2026-08-03, **25★** | ⚠ **none declared** | not examined | **Not examined in this pass.** 745 MB repository; the name suggests a CanMV/RT-Smart variant for this board and it has more stars than the main BSP. **A real gap** — see below. |
-
-> ⚠ **Not one LilyGO repository for this product carries a licence file.** Redistribution status
-> of their source *and* of the prebuilt nRF52840 binaries is **unknown**. Nothing from them has
-> been copied into this repository.
-
-### K230 platform software
-
-| Project | Repository | Revision / branch | Licence | Stars | Board support |
-|---|---|---|---|---|---|
-| **k230_linux_sdk** | `kendryte/k230_linux_sdk` | branch **`dev`**; LilyGO pins `22d02c6b6783a57a3aca7eb3160e313e772cb710` | **BSD-2-Clause** | 62 | **The upstream this board builds from.** Linux-only. |
-| **k230_sdk** (dual-OS) | `kendryte/k230_sdk` | `main`, last push 2025-09-12 | BSD-2-Clause | 273 | Targets Canaan EVB/CanMV. **No profile for this board.** RT-Smart on CPU1 + Linux on CPU0. Docker image `ghcr.io/kendryte/k230_sdk`. |
-| **CanMV (MicroPython)** | `kendryte/canmv_k230` | branch **`canmv_k230`**, 2026-09-03 | none declared | 119 | Runs on K230. **No board profile** — display, touch and keyboard would need porting. |
-| **MaixPy** | `sipeed/MaixPy` | `main`, 2026-08-28 | NOASSERTION | 843 | Same situation. Sipeed's Python runtime. |
-| **oreboot** | `oreboot/oreboot` | `main`, 2026-07-13 | **GPL-2.0** | **1795** | **Has K230 support.** Maintainer states it boots Linux from mask ROM over USB in ~3 s. Board-specific status unknown, but this is the most credible recovery lever. |
-| **k230-debian** | `intx82/k230-debian` | branch `6.6`, last push **2024-12-03** | BSD-2-Clause | 1 | Debian rootfs experiment. Low activity; a starting point, not a distribution. |
-| **linux-xuantie-kernel** | `ruyisdk/linux-xuantie-kernel` | `7d4e1f444f461dbe3833bd99a4640e7b6c2cd529` | GPL-2.0 | — | The kernel this board actually runs |
-| **nncase** | Canaan | version must match the SDK | — | — | KPU model compiler |
-| **RT-Thread / RT-Smart** | upstream | — | Apache-2.0 | — | CPU1 OS in the dual-OS SDK; not used by this board's image |
-| **Zephyr** | upstream | — | Apache-2.0 | — | ❌ **No K230 SoC or board support upstream** as of 2026-09-04 |
-
-### Vendored dependencies inside the BSP — identity and delta
-
-Both are properly pinned, which is worth crediting.
-
-| Tree | Upstream pin | Modifications | Reproducible? |
-|---|---|---|---|
-| **LVGL** | commit `59dc7e436ae97a25e32656739ea6a943f9f11b6a` (in the directory name) | **4 patches**, retained beside the pin: `0001` pcpp Python preprocessor fallback · `0002` K230 plane rotation in the DRM backend · `0003` FreeType fixed-colour-bitmap scaling · `0004` K230 staging scanout buffer | **Yes** — upstream commit + patch series |
-| **Nordic Serial LTE Modem** | submodule at `13c80da97fe4d55ecb5a9745834d97be22821307` | **5 patches**: `0001` GNSS NMEA URC + LED · `0002` optional XDFU · `0003` UART diag · `0004` GNSS NMEA URC worker · `0005` LED AT control | **Yes** |
-| Kernel | `linux-xuantie-kernel` @ `7d4e1f44…` | **30+ numbered patches** `0025`–`0064`, plus one **retained `.rejected`** file | **Yes** |
-
-Keeping `linux/rejected/0044-drm-canaan-use-wc-allocation-for-dumb-buffers.rejected` in the tree
-is good practice — it records that write-combine dumb-buffer allocation was attempted and did not
-apply, which saves the next person the experiment.
-
-### Community projects
-
-| Project | Status | Evidence |
-|---|---|---|
-| **Independent Meshtastic UI** | Announced 2026-06-02, "will publish a repo once complete". **No repository located** as of 2026-09-04. | announced project |
-| `kendryte_boot` | Boot tool by the oreboot maintainer, "on GitHub" per the author | demonstrable project, URL not captured |
-| `Bruce` firmware | A user asked in r/brucefw (2025-10-23) about device support. Bruce is ESP32-only; **not applicable** to a RISC-V board. Recorded as a refuted association. | hearsay, refuted |
-
-### Gap: `T-Display-K230_canmv_rt`
-
-This repository has **25 stars — more than the main BSP's 1** — was created 2025-03-05 (two weeks
-before the product launched) and was last pushed 2026-08-03. Its 745 MB size suggests vendored
-SDK content. It was **not cloned or examined** in this pass because of its size, and that is the
-largest single unexplored software artifact for this board. Anyone continuing this work should
-start there.
-
----
-
-## Part 2 — Community
-
-Evidence labels: **firsthand measurement** · **firsthand ownership** · **demonstrable project** ·
-**announced project** · **informed interpretation** · **opinion** · **hearsay** · **unsupported
-assertion**.
-
-### Where the community is
-
-| Venue | Activity | Note |
-|---|---|---|
-| **r/LilyGO** | Active; **LilyGO staff answer as `u/LilyGoXinyuan`**, usually within a day | The de-facto support channel |
-| **r/meshtastic** | The single largest thread about this board (187 pts / 40 comments) | Mesh users found it before RISC-V users did |
-| **r/RISCV** | Discusses the K230 chip and CanMV boards; **has never discussed the LilyGO board** | Notable absence |
-| **CNX-Software** | Covered CanMV-K230 (2023) and BPI-CanMV-K230D-Zero (2024); **never this board** | Site search returned 5 K230 results, none about it |
-| **Hackaday** | **Nothing found** | |
-| GitHub issues | `.github/workflows/issues.yaml` exists in every LilyGO repo; issue traffic not examined | gap |
-| Chinese sources (Bilibili, Zhihu) | **Not searched directly** | Recorded gap |
-
-### The anecdotes that matter
-
-**The brick — firsthand ownership, 2026-08-21 and 2026-08-28, u/phirzcolru**
-
-> "extensive attempts to work with this device. i managed to get an mp3 player and notepad
-> working for it. but once i attempted to turn on the 'fun' features it bricked it. its not quite
-> user friendly. i will be switching to an orange pi… that said im no programmer. the display is
-> awesome looking."
-
-> "I also saw the newer k230 stuff. Alas my board is still unresponsive to boot pin and term. I
-> think I flashed it into mmc mode vs sd card and it's stuck. Now that you have the keyboard and
-> the esp I might purchase again… Still a great board for the record."
-
-The most consequential report about this product. Note the last sentence of each: the user is not
-hostile, he is stuck. Also note "**and the esp**" — a possible independent hint at
-[`GC-2`](gaps-and-conflicts.md), or an echo of the wiki.
-
-**The bare board — firsthand ownership, 2026-08-20, u/Opposite_Future2602**
-
-> "I got one of these but it was just the screen and motherboard on risers in the package. Just
-> fair warning, I've also been completely unable to figure out how to even get an OS installed."
-
-> "The CPU is in the name, it uses a Kendryte K230. It's a RISC-V chip that's probably capable of
-> running some cut down form of Linux. The problem is I haven't been able to find anyone
-> developing for this board, and RISC-V chips typically have very finicky bootloaders where you
-> can't just install any common OS."
-
-Accurate for the situation before 2026-08-13. LilyGO replied the next day with the repository and
-wiki links.
-
-**oreboot — demonstrable project, 2025-03-26, u/CyReVolt**
-
-> "I'm a developer of the oreboot firmware project, and we have support for the K230, can boot
-> Linux from mask ROM over USB in 3 seconds. You can find a demo on my YouTube channel. Also
-> check out the kendryte_boot tool that I made, it's on GitHub."
-
-Author of the project making a claim about his own work, with a demo. **The single most useful
-recovery lead** in the whole corpus.
-
-**The keyboard ships without a case — firsthand ownership, 2026-08-13, u/Circuitnaut24**
-
-> "I can confirm it does not. It seems like the encased K230 model that goes with keyboard is a
-> newer one that isn't listed on the website yet."
-
-Independently corroborates the wiki's undocumented "Cased Version".
-
-**Ethernet — firsthand observation, 2025-07-07, u/Nobodytoyou_**
-
-> "It's very interesting, though the ethernet port is an odd choice. It just seems too big for
-> this type of device, lol."
-
-**Missing Bluetooth — firsthand observation, 2025-07-08**
-
-> u/skeptikoz: "But Bluetooth seems to be missing — might that be an impediment to porting the…"
-> u/Hot-Win2571: "You're right. I don't see BT labels on the board, and the K230 page does not
-> mention Bluetooth."
-> u/ExcitingTabletop: "USB C Bluetooth adaptors are $20, but that seems like a REALLY weird
-> omission."
-
-Three independent observers reaching the same conclusion the BSP confirms.
-
-**Value judgement — opinion, 2025-07-08, u/skeptikoz**
-
-> "It seems more of a development platform than an end-user product, but WOW that is a lot of
-> bang for <$100! Two RISC-V cores, one fast with a Vector Processor, a KPU capable of running
-> ResNet or Yolo in real-time, 2D and 3D graphics engines, HDMI out, multiple MIPI camera ports,
-> the list goes on. LoRa is icing on top!"
-
-The most accurate one-paragraph summary of the product written by anyone, including LilyGO.
-
-**Battery scepticism — opinion, 2025-07-07, u/Ryan_e3p**
-
-> "Seems like it's getting to the point where I'd rather just get a phone de-Google'd, and install
-> Meshtastic on it. It seems like the battery life on this would be less then it would be with a
-> phone and a regular nRF node on a 1000mAh battery."
-
-Unmeasured, and nobody has measured it since. See [`performance.md`](performance.md).
-
-**MQ-Pro comparison — informed interpretation, 2025-07-09, u/Nanocupid**
-
-> "This board has 1G ram and a 1.6GHz RVV1 'big' core. It's basically more powerful than the 1GHz
-> non RVV core in my MQ-Pro, and has 8x the memory."
-
-Correct arithmetic on published specifications. **Not a measurement.**
-
-**"17 TOPS" — unsupported assertion, 2025-07-08, u/Middle_Chicken_2577**
-
-> "(k230 is the new k210 which i have in my maixcam pro)… sounds fun, since the k230 has abt 17
-> tops and therefore can surely do stuff."
-
-Contradicted by every Canaan document, which publish **no** TOPS figure. Recorded only because it
-circulates.
-
-**ATAK interest — opinion, 2025-07-07, u/Electroboy101 (31 points)**
-
-> "If you could run ATAK on this, it might just become even more interesting."
-
-The top-voted comment on the largest thread. ATAK is Android; this is not an Android device. It
-tells you what the mesh community wants from a Linux handheld with a screen, GPS and LoRa.
-
-**IP rating — opinion / requirement, 2026-08-20, u/No-Craft-7979**
-
-> "Wish there were more IPX water resistant options across all your product lines. I prototype
-> field devices. The designs are not taken seriously because they are afraid of water."
-
-**Purchasing confusion — 2026-08-20, u/Silly_Abalone_288**
-
-> "I'm confused on what is what I'm in the USA and I want the kit with the keyboard. What do I
-> buy?"
-
-**Unanswered.** See [§1 of the README](README.md#1-identity-skus-and-variants) — the answer is two
-SKUs, `K256-03` + `K256-04`.
-
-### Prevalence — stated honestly
-
-**Four** distinct firsthand-ownership reports were found, across **26 comments** in the two
-largest threads and **6 threads** in total mentioning the product by name. That is the entire
-sample. It supports statements like "at least one owner bricked a board this way", and supports
-nothing at all about how often it happens.
diff --git a/devices/lilygo/t-display-k230/research-log.md b/devices/lilygo/t-display-k230/research-log.md
deleted file mode 100644
index 64cde8d..0000000
--- a/devices/lilygo/t-display-k230/research-log.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# T-Display K230 — research log
-
-**Session date: 2026-09-04.** Single pass, no hardware. Every query, its depth, and its outcome.
-
-## Declared scope and exclusions
-
-- **Searched:** LilyGO store (Shopify HTML + `.js` endpoints), LilyGO wiki, GitHub (org listing,
-  repository metadata, full recursive trees, code search), Canaan `kendryte/k230_docs`,
-  CNX-Software site search, Reddit via `old.reddit.com/search.json` and per-thread JSON.
-- **Not searched, and why:** AliExpress, Amazon, Tindie and Taobao — deliberately deferred; all
-  three are heavily bot-protected and the vendor's own store gives authoritative dated prices,
-  which is what the pricing record needs. Chinese-language sources (Bilibili, Zhihu) were
-  **queried only through GitHub and CNX-Software**, not directly; recorded as a gap. YouTube: one
-  LilyGO-linked video was identified by URL but not watched.
-- **Depth:** every search below was taken to the end of its first result page; Reddit searches
-  used `limit=25`–`50` and `t=all`, and returned fewer results than the limit in every case, so
-  the result sets are complete rather than truncated.
-
-## Product identification
-
-| # | Service | Query | Result |
-|---|---|---|---|
-| 1 | lilygo.cc | `/search?q=K230&type=product` | **3 products.** `t-display-k230`, `t-display-k230-kit`, `t-embed-cc1101`. The third is the SKU collision (`K230` = T-Embed CC1101 transparent). **Established the marketed name in one query.** |
-| 2 | lilygo.cc | `/products/t-display-k230.js` | Full variant/SKU/price/date record |
-| 3 | lilygo.cc | `/products/t-display-k230-kit.js` | Same for the kit; **the description HTML is the fullest published BOM** |
-| 4 | GitHub | `search/repositories?q=org:Xinyuan-LilyGO+K230` | 4 repositories |
-| 5 | GitHub | `orgs/Xinyuan-LilyGO/repos?per_page=100 --paginate`, filtered for `k230\|k256\|riscv\|canmv\|kendryte\|deck` | **254 repositories** enumerated; confirmed the 4 K230 repos and separately identified T-Deck/T-Deck-Pro/T-Deck-MAX as a *different* family |
-| 6 | wiki.lilygo.cc | `/products/t-display-series/t-display-k230/` | Product page; sidebar revealed **`cased-version.html`** and `quick-start.html` |
-| 7 | wiki.lilygo.cc | guessed `/t-display-k230-cased-version/` | **404** — wrong shape. Correct path is `/t-display-k230/cased-version.html`. Recorded so the next agent does not repeat it. |
-| 8 | wiki.lilygo.cc | `/t-display-series/t-display-keyboard/` | **Different product** — an ESP32 T-Display in a keyboard shell. A name trap; nothing to do with K230. |
-
-**Candidate names tested and refuted:** `T-Deck K230`, `T-K230`, `T-Deck Pro K230`,
-`K230 Cardputer`. None returns a LilyGO product. The store search for `K230` returns three
-products and none is named any of those.
-
-## Chip documentation
-
-| # | Service | Query | Result |
-|---|---|---|---|
-| 9 | GitHub | `repos/kendryte/k230_docs/git/trees/main?recursive=1` | **837 entries**, not truncated. The single highest-yield call of the session. |
-| 10 | raw.githubusercontent | 6 targeted `en/` document fetches | All 200 |
-| 11 | GitHub code search | `repo:kendryte/k230_docs "C908"` | 11 files; led to `en/K230_brief_datasheet.md`, which was **not** in the first directory listing pass because it sits at the tree root, not under `00_hardware/` |
-| 12 | local grep | `ethernet\|gmac\|rmii` across both datasheets | **Zero matches** — the negative result that resolves the RJ45 question |
-| 13 | local grep | `third core\|small core\|little core\|big core\|C908\|security\|OTP\|boot` | Confirmed exactly two CPU subsystems |
-| 14 | tree listing | `zh/00_hardware` filter | **22 binary EDA artifacts the `en/` tree does not have.** Recorded in the vendor guide as the vendor's most important trap. |
-| 15 | tree listing | search for `K230_PINOUT` | **Not present.** Cited by the datasheet, never published. |
-| 16 | tree listing | search for errata | **None published.** |
-
-## BSP source mining
-
-| # | Method | Result |
-|---|---|---|
-| 17 | `git clone --depth 1` × 3 | 172 MB + 9.9 MB + 9.8 MB; commits `bb831ab…`, `4646a72…`, `ed4ecbe…` |
-| 18 | Read `HARDWARE_PINMAP.md` | Complete pin/bus/address map — the backbone of this record |
-| 19 | Regex sweep for ~30 part-number families across `*.c/cpp/h/md/MD/sh/patch/dts/mk/in/defconfig` | Ranked hit counts: `lr2021` 579, `k230` 532, `nrf9151` 203, `nrf52840` 168, `sx1262` 151, `rm69a10` 124, `tca8418` 72, `bq25896` 59, `bq27220` 57, `aht20` 54, `gc2093` 44, `xl9555` 42, `lt9611` 29, `max98357a` 25, `gt9895` 19, `rtl8723ds` 16, `rtl8189fs` 6, `csr8510` 4. **Zero hits for any Espressif identifier** — the evidence behind `GC-2`. **Zero hits for any PMIC family** — U1. |
-| 20 | Grep `ui_hardware.c` for the key map | Full TCA8418 code→label table and 6×11 display layout extracted |
-| 21 | Read `linux.fragment` and the defconfig | Toolchain path/flags, kernel repo+commit, driver choices, built-in test tools |
-| 22 | Grep for `NET_ETH_IFACE` | `eth0`; and `USB_RTL8152` is **absent** from the fragment |
-| 23 | Read `k230_canmv_v3.dts` | IO bank voltage warning; 512 MB memory node (`GC-7`) |
-
-## Community
-
-| # | Service | Query | Results | Note |
-|---|---|---|---|---|
-| 24 | `old.reddit.com/search.json` (UA `WhatsApp/2.23.20.0`) | `"T-Display K230"` | 6 | **200 OK.** `www.reddit.com` returns 403 to the same request; the documented UA fallback worked exactly as the repository's `ai-crawler-site-access-table.md` says |
-| 25 | same | `lilygo k230` | 6 | Revealed **r/LilyGO exists** and is active |
-| 26 | same | `kendryte k230` | 8 | Mostly r/RISCV, 2023–2025 |
-| 27 | per-thread `.json?limit=100` × 4 | `1vtcjuj`, `1ltxxxo`, `1v8kedv`, `1jgb4kn` | full comment trees | Source of every anecdote in [`community.md`](community.md), including the two most consequential — the brick and the oreboot recovery lead |
-| 28 | cnx-software.com | `/?s=K230` | 5 | **None is about this board.** Negative result. |
-
-**Not found despite looking:** any Hackaday article; any independent review; any teardown; any
-PCB photograph; any benchmark; any clone listing.
-
-## Method notes worth reusing
-
-- **`gh api` rather than anonymous `curl` for GitHub.** One recursive tree call on `k230_docs`
-  returns 837 entries and can exhaust the 60/hour anonymous limit; the resulting 403 is
-  indistinguishable from a bot block except by `X-RateLimit-Remaining`.
-- **Shopify's `/products/<handle>.js`** gives `created_at`, `published_at`, per-variant SKU and
-  integer-cent prices that the rendered page never shows. This is how the launch dates in
-  [`product-history-and-family.md`](product-history-and-family.md) were established.
-- **`old.reddit.com/search.json` with `User-Agent: WhatsApp/2.23.20.0`** returned 200 on every
-  call. No other UA rotation was needed anywhere in this session; `lilygo.cc`,
-  `wiki.lilygo.cc`, `raw.githubusercontent.com` and `cnx-software.com` all served a plain request.
-- **Grep the vendor tree for part-number *families*, not for parts you expect.** The zero-hit
-  results (Espressif, PMIC) were more informative than most of the positive ones.
-
-## Stopping criterion
-
-Two consecutive broad passes produced only duplicates. Remaining unknowns
-([`gaps-and-conflicts.md`](gaps-and-conflicts.md)) require **physical hardware, a PCB photograph,
-or a schematic LilyGO has not published** — not more searching. This is a reproducible
-broad-coverage snapshot dated 2026-09-04, not a claim that nothing else exists.
diff --git a/devices/lilygo/t-display-k230/resources-and-conflicts.md b/devices/lilygo/t-display-k230/resources-and-conflicts.md
deleted file mode 100644
index 58c1360..0000000
--- a/devices/lilygo/t-display-k230/resources-and-conflicts.md
+++ /dev/null
@@ -1,121 +0,0 @@
-# T-Display K230 — resources, ownership and conflicts
-
-Evidence status throughout: **`reported-working`** or **`inferred`**, never `executed-*`. No
-hardware was available.
-
-## 1. Hard conflicts — things that physically cannot coexist
-
-| # | Conflict | Why | Consequence |
-|---|---|---|---|
-| **HC-1** | **AMOLED panel vs LT9611 HDMI output** | The K230 has **exactly one MIPI DSI output** (Canaan brief datasheet: "1 × MIPI DSI"). Both sinks are DSI. | Mutually exclusive, and resolved at **boot time by device tree**: `canaan/k230-canmv-rm69a10` vs `canaan/k230-canmv-rm69a10-hdmi`. There is no runtime switch. LilyGO: "HDMI support is kept as a diagnostic feature. AMOLED remains the default display path." |
-| **HC-2** | **GT9895 touch vs LT9611 control lines** | Both use I²C3 (`GPIO37`/`GPIO36`), IRQ `GPIO23` and reset `GPIO24`. | A reset asserted for one resets the other. They must occupy different I²C addresses. Since HC-1 already makes them exclusive in practice, this is mostly a diagnostic-mode hazard. |
-| **HC-3** | **BOOT0 button vs `IO0` boot strap** | `GPIO0` is both the BOOT0 strap and the button the launcher reads for screen toggle. | Holding the button through reset changes boot behaviour. Do not wire anything else to it. |
-| **HC-4** | **Two base boards, one 40-pin header** | The nRF52840 base and the nRF9151 keyboard base both plug into the same 2 × 20 header and both claim `GPIO46`/`GPIO47`. | You get one base at a time. The launcher detects which. |
-
-## 2. Shared buses
-
-### I²C4 (`GPIO46` SCL / `GPIO47` SDA) — the crowded one
-
-Carries, depending on base board: TCA8418 `0x34`, AHT20 `0x38`, BQ27220 `0x55`, BQ25896 `0x6B`,
-XL9555 **`0x20`–`0x27` (probed)**. It is **also exposed on the 40-pin header**, so any user
-peripheral joins the same bus as the keyboard scanner and the charger.
-
-Three practical rules:
-
-1. **Never hard-code the XL9555 address.** LilyGO's own software probes and caches it.
-2. **Anything you add in `0x20`–`0x27` may shadow the expander.** Pick outside that block.
-3. **Bus errors take down power management, not just your device.** A peripheral that holds SDA
-   low blinds the charger and gauge, and the launcher's low-battery shutdown depends on gauge
-   reads. Consider that before hanging a marginal sensor on this bus.
-
-### SPI — LoRa only
-
-`GPIO15/16/17` + CS `GPIO14`, exposed to userspace through **spidev**
-(`0054-riscv-dts-rm69a10-enable-lora-spidev.patch`). The radio is driven by **RadioLib from
-userspace**, not by a kernel LoRa driver. Two consequences: any process can open the spidev node
-and corrupt radio state, and there is no kernel-side arbitration between, say, the Meshtastic app
-and the LoRa test app. The launcher arbitrates in software; another program does not have to.
-
-### SDIO / SD-MMC
-
-Two controllers. **MMC1 (`GPIO54`–`GPIO59`) is the microSD and is the boot medium.** The Wi-Fi
-module is on the other SDIO controller. They do not contend.
-
-### I²S
-
-`GPIO32/33/35` + shutdown `GPIO34` reach the MAX98357A on the nRF52840 base. The K230 also has
-an **on-die codec** with its own DAC/ADC path, so there are two audio outputs and the BSP adds
-`0059-asoc-canaan-add-external-i2s-output-switch.patch` to choose between them. **Choosing the
-wrong route is the most likely "no sound" cause** on this board.
-
-### USB
-
-Both K230 USB 2.0 OTG controllers are in play: one is the **host** carrying Ethernet (RTL8152B),
-the Bluetooth dongle and any USB modem; one is used for the **gadget** side — the rootfs overlay
-ships `k230-usb-storage-gadget` and `/etc/default/k230_usb_storage`, and the kernel fragment
-enables `USB_CONFIGFS` with mass storage, RNDIS and ACM functions. Enabling USB mass-storage
-gadget on the same port you are using for host devices is the obvious conflict.
-
-## 3. Ownership arbitration the launcher performs
-
-These are software policies, not hardware interlocks. Anything running outside the launcher can
-break them.
-
-| Resource | Contenders | Arbitration |
-|---|---|---|
-| **nRF52840 UART (`/dev/ttyS1`)** | Meshtastic BLE app, nRF52840 UART DFU | Explicit ownership coordination, added in BSP **v0.2.2** |
-| **Microphone** | Xiaozhi wake-word listener, recorder, mic spectrum | "Wake-word listening is active only while the Xiaozhi app is open and **owns the microphone**" |
-| **LoRa spidev** | Meshtastic, LoRaWAN test, FLRC bench, RF test profiles | Launcher-internal only |
-| **`GPIO42` IOMUX** | kernel pinctrl, launcher | The launcher **writes the K230 IOMUX register for `GPIO42` directly** to force GPIO-input mode. If a kernel driver later re-muxes it, the keyboard IRQ stops. |
-| **Display framebuffer** | U-Boot boot logo, kernel DRM, LVGL | Three patches manage the handoff (`0038`, `0051`, `0043`) |
-
-## 4. Interrupts
-
-| Line | Owner | Note |
-|---|---|---|
-| `GPIO23` | GT9895 touch **and** LT9611 | see HC-2 |
-| `GPIO20` | LoRa — **`DIO1` on SX1262, `DIO11` on LR2021** | same K230 pin, different radio pin |
-| `GPIO42` | TCA8418 keyboard | launcher forces the IOMUX |
-| `GPIO64` (PMU INT0) | power key | routed to **CPU IRQ 175** |
-| `GPIO0` | BOOT0 button | also a boot strap |
-
-## 5. Power rails and domains
-
-| Rail | Notes |
-|---|---|
-| USB-C in | **5 V, 500 mA** per the product page — a modest charge budget for a 1.6 GHz SoC plus an AMOLED |
-| 21700 cell | in the keyboard base compartment |
-| **5 V boost** | enabled by the **nRF52840's `P0.04`**, supplying the host unit from the 21700 |
-| 3V3 / 5V on header | pins 19/20 of the 40-pin header, plus `USB-IN-5V` |
-| PMIC | **unidentified** — [`components/unidentified/t-display-k230`](../../../components/unidentified/t-display-k230/README.md) U1 |
-
-**The boost-enable arrangement is worth stating plainly:** on a kit configuration the *companion
-MCU on an expansion board* controls the 5 V rail that powers the main unit from the battery. If
-the nRF52840 firmware is wedged or being reflashed, that is a power dependency, not just a
-comms dependency.
-
-Low-battery shutdown is a **userspace policy** in `ui_hardware.c` driven by BQ27220 readings and
-gated on BQ25896 USB-present, with a confirm count before acting. It is not a hardware cut-off.
-
-## 6. Memory and storage
-
-| Resource | Size | Notes |
-|---|---|---|
-| LPDDR4 | **1 GB** (8 Gb, 32-bit) | Product specification. **Note:** the Canaan U-Boot reference DTS this BSP derives from declares `memory@0 … 0x20000000` = **512 MB**; that is the upstream CanMV-v3 baseline, not necessarily what the LilyGO build uses. Unverified — [`GC-7`](gaps-and-conflicts.md). |
-| K230 SRAM | 2 MB shared + 2 MB KPU | see the component record |
-| microSD | user-supplied | Holds the whole system image. BSP v0.2.4 added **storage expansion for cards larger than the flashed image** — before that, the extra space was simply unused. |
-| Flash | LilyGO's wiki says **16 MB**; the BSP boots from SD | Role unclear; possibly the boot SPI NOR. Unverified. |
-
-## 7. Realistic simultaneous-use scenarios
-
-| Scenario | Assessment |
-|---|---|
-| Display + touch + keyboard + Wi-Fi | Expected to work; this is the shipped default |
-| Display + camera + KPU inference | Supported by design (ISP → KPU); no throughput figure published |
-| Camera RTSP + Wi-Fi | `camera_rtsp_demo` package is built in; bandwidth impact unmeasured |
-| LoRa + Wi-Fi | Different buses; no conflict. 2.4 GHz Wi-Fi and sub-GHz LoRa do not share spectrum. |
-| Bluetooth + Wi-Fi | **Bluetooth is a USB dongle**, so this is a USB-bandwidth question, not an RF-coexistence one — unusually, it avoids the classic combo-chip coexistence problem entirely |
-| HDMI + AMOLED | **Impossible** (HC-1) |
-| USB mass-storage gadget + USB Ethernet | Contends for USB roles; untested |
-| Audio out (I²S amp) + microphone capture | K230 supports simultaneous I²S-out and PDM/ADC-in per its datasheet; on this board, untested |
-| nRF52840 DFU + Meshtastic BLE | **Arbitrated in software only** (v0.2.2) |
diff --git a/devices/lilygo/t-display-k230/sources.md b/devices/lilygo/t-display-k230/sources.md
deleted file mode 100644
index b3554ca..0000000
--- a/devices/lilygo/t-display-k230/sources.md
+++ /dev/null
@@ -1,94 +0,0 @@
-# T-Display K230 — sources
-
-`Class` ∈ {primary, authorized mirror, credible mirror, standard, community}.
-`Medium` describes format. All URLs retrieved **2026-09-04** unless stated.
-
-## Vendor — LILYGO
-
-| ID | Title | Publisher | Class | Medium | URL | Published/updated | Establishes | Scope / limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| D1 | T-Display K230 product page + `/products/t-display-k230.js` | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230` | created 2025-03-21 13:52+08, published 2025-03-21 14:22+08 | SKUs `K256`/`-A`/`-B`/`-C`, $98.79, SoC/display spec, images | Marketing copy; contains the RM69A10 and resolution but not the full BOM | `scratch/lilygo-k230/shop-t-display-k230.{js,html}` |
-| D2 | T-Display K230 Kit product page + `.js` | LILYGO | primary | store listing | `https://lilygo.cc/products/t-display-k230-kit` | created 2026-08-06 09:31+08, published 2026-08-20 15:10+08 | Kit SKUs and prices; **the fullest published component list**: RM69A10, SX1262, GC2093, 8 Gb LPDDR4, RTL8189, "RC01812" Ethernet | Does not mention Bluetooth or the base-board silicon | `scratch/lilygo-k230/shop-t-display-k230-kit.{js,html}` |
-| D3 | `k230_bsp/docs/HARDWARE_PINMAP.md` | LILYGO | primary | repository doc | `https://github.com/Xinyuan-LilyGO/T-Display-K230/blob/bb831ab358b66f5bd9a87ecd7c580fee4537492e/k230_bsp/docs/HARDWARE_PINMAP.md` | commit 2026-09-03 | **The authoritative pin map.** Every GPIO, bus, address, IRQ | Single source, **no schematic to corroborate it** | `scratch/lilygo-k230/repos/T-Display-K230/` |
-| D4 | `k230_canmv_t_display_rm69a10_defconfig` | LILYGO | primary | source | same repo, `k230_bsp/overlay/buildroot-overlay/configs/` | commit 2026-09-03 | XuanTie toolchain path and flags, kernel repo + commit, Wi-Fi packages, built-in test tools | | same |
-| D5 | `linux.fragment` + 30 numbered kernel patches | LILYGO | primary | source | same repo, `k230_bsp/overlay/buildroot-overlay/linux/` | commit 2026-09-03 | Touch driver choice, USB net classes, Bluetooth dongle workarounds, display fixes, PMU power key | | same |
-| D6 | `k230_canmv_v3.dts` (Canaan copyright 2023, in LilyGO's overlay) | Canaan / LILYGO | primary | source | same repo, U-Boot overlay | commit 2026-09-03 | **IO bank voltage warning**, BOOT0/BOOT1 on IO0/IO1, per-pin mux, 512 MB memory node | The memory node is the CanMV-v3 baseline — see `GC-7` | same |
-| D7 | `k230_launcher/k230_phone_ui/src/ui_hardware.c` | LILYGO | primary | source | same repo | commit 2026-09-03 | **Complete keyboard key map and layout**, TCA8418 registers, PMU constants, low-battery policy, XL9555 probe behaviour | | same |
-| D8 | `README.MD` + `CHANGELOG.MD` | LILYGO | primary | repository doc | same repo | v0.2.4, 2026-09-03 | Fitted-hardware list, feature status, known limitations, build and flash procedure, dated release history | | same |
-| D9 | T-Display K230 wiki page | LILYGO | primary | official wiki | `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/` | undated | RTL8152B Ethernet, GT9895, 1.6 TOPS claim, 16 MB flash, HDMI 1080p | ⚠ **contains at least three errors** — `GC-1`, `GC-2`, and empty schematic/dimension sections | `scratch/lilygo-k230/wiki/` |
-| D10 | T-Display K230 **Cased Version** wiki page | LILYGO | primary | official wiki | `https://wiki.lilygo.cc/products/t-display-series/t-display-k230/cased-version.html` | undated | Third variant: 110×58×30 mm, speaker, mic, 3.5 mm, QWIIC, nRF52840 header, "optional SX1262 or LR2021" | No shop listing exists for it | same |
-| D11 | T-Display K230 Quick Start wiki page | LILYGO | primary | official wiki | `.../t-display-k230/quick-start.html` | undated | "No Arduino IDE"; ⚠ **inverts the core roles** (`GC-1`) | | same |
-| D12 | `Xinyuan-LilyGO/T-Display-K230-nRF52840` | LILYGO | primary | repository | `https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF52840/tree/4646a728580739d487126f47a521e9b8032b3c2c` | pushed 2026-08-23 | nRF52840 pin map incl. `P0.04` 5 V boost, AT set, DFU procedure, prebuilt firmware + bootloader | No licence file | `scratch/lilygo-k230/repos/` |
-| D13 | `Xinyuan-LilyGO/T-Display-K230-nRF9151` | LILYGO | primary | repository | `https://github.com/Xinyuan-LilyGO/T-Display-K230-nRF9151/tree/ed4ecbe34162dec9b81213a400198125bbd6e36f` | pushed 2026-08-14 | nRF9151 pin map, NCS v3.4.0, pinned upstream submodule, five patches, AT behaviour, TF-M caveat | No licence file | same |
-| D14 | Product and wiki imagery | LILYGO | primary | images | see [`media/manifest.json`](media/manifest.json) | undated | 40-pin diagram, keyboard-extension diagram, specification card | No licence statement | `media/` |
-
-## Chip vendor — Canaan Creative
-
-| ID | Title | Publisher | Class | Medium | URL | Published/updated | Establishes | Local path |
-|---|---|---|---|---|---|---|---|---|
-| C1 | K230 Product Full Datasheet **V1.0** | Canaan | primary | datasheet | `https://github.com/kendryte/k230_docs/blob/f8e30213963e0ed5cf995c3cd4701218a45e4793/en/00_hardware/K230_datasheet.md` | doc **2023-07-06** | Full feature list, KPU operators, packages, electrical sections, PMU, security | [`components/canaan/k230/artifacts/`](../../../components/canaan/k230/artifacts/) |
-| C2 | K230 Brief Datasheet | Canaan | primary | datasheet | `.../en/K230_brief_datasheet.md` | repo 2025-09-12 | **Core roles and frequencies**, package sizes, SiP memory, peripheral counts | same |
-| C3 | K230 Hardware Design Guide | Canaan | primary | design guide | `.../en/00_hardware/K230_Hardware_Design_Guide.md` | repo 2025-09-12 | Board-design rules | same |
-| C4 | K230 PMU User Guide | Canaan | primary | manual | `.../en/01_software/board/osdrv/K230_PMU_User_Guide.md` | repo 2025-09-12 | PMU register flow, power key, shutdown | same |
-| C5 | K230 nncase Development Guide | Canaan | primary | manual | `.../en/01_software/board/ai/K230_nncase_Development_Guide.md` | repo 2025-09-12 | KPU model compilation | same |
-| C6 | K230 RVV in Action / RVV optimisation | Canaan | primary | tutorial | `.../en/02_applications/tutorials/K230_RVV_*.md` | repo 2025-09-12 | Practical RVV use on CPU1 | same |
-| C7 | `kendryte/k230_docs` full tree listing at `f8e3021…` | Canaan | primary | repository | `https://github.com/kendryte/k230_docs` | 2025-09-12 | **Negative results**: no errata, no `K230_PINOUT` document; **positive**: the `zh/` EDA set | [`CANAAN-EDA-SET.md`](../../../components/canaan/k230/artifacts/CANAAN-EDA-SET.md) |
-| C8 | `kendryte/k230_linux_sdk` | Canaan | primary | repository | `https://github.com/kendryte/k230_linux_sdk` | pushed 2026-09-03; **pinned by LilyGO at `22d02c6b6783a57a3aca7eb3160e313e772cb710`** | The SDK this board's image is built from | — |
-
-## Independent editorial
-
-| ID | Title | Publisher | Class | Medium | URL | Published | Establishes |
-|---|---|---|---|---|---|---|---|
-| N1 | "CanMV-K230 AI development board features Kendryte K230 dual-core 64-bit RISC-V processor" | CNX-Software | community | blog | `https://www.cnx-software.com/2023/10/24/canmv-k230-ai-development-board-features-kendryte-k230-dual-core-64-bit-risc-v-processor/` | 2023-10-24 | K230 launch-era coverage |
-| N2 | "$29 Banana Pi BPI-CanMV-K230D-Zero…" | CNX-Software | community | blog | `https://www.cnx-software.com/2024/11/18/29-banana-pi-bpi-canmv-k230d-zero-features-kendryte-k230d-risc-v-soc-for-aiot-applications/` | 2024-11-18 | K230D board price point |
-| N3 | "Kendryte K510 tri-core RISC-V AI processor deliver up to 3 TOPS" | CNX-Software | community | blog | `https://www.cnx-software.com/2021/07/09/kendryte-k510-tri-core-risc-v-ai-processor-3-tops/` | 2021-07-09 | K510 lineage |
-
-**Negative result:** a CNX-Software site search for `K230` on 2026-09-04 returned **five** results
-and **none of them is about the LilyGO T-Display K230**. As of the research date, the most
-prolific independent SBC publication has never covered this product. No Hackaday article was
-found either.
-
-## Community
-
-Full thread-level treatment with evidence labels: [`community.md`](community.md).
-
-| ID | Thread / comment | Where | Date | Evidence type |
-|---|---|---|---|---|
-| R-LAUNCH | "T-Display K230 is available!" | r/LilyGO | 2025-03-21 | vendor announcement |
-| R-OREBOOT | u/CyReVolt on oreboot K230 support | r/LilyGO | 2025-03-26 | **demonstrable project** (author is the maintainer) |
-| R-MESH | "New Lilygo T-Display K230" — 187 pts, 40 comments | r/meshtastic | 2025-07-07 | discussion; contains firsthand observation of the RJ45 and the missing BT |
-| R-STOCK | "T-Display K230 and T-Lora Pager have some stock available" | r/LilyGO | 2025-07-04 | availability |
-| R-KB | "Keyboard for T-Display K230 is here" | r/LilyGO | 2026-07-28 | vendor announcement |
-| R-CASE | u/Circuitnaut24: keyboard does **not** include a case | r/LilyGO | 2026-08-13 | **firsthand ownership** |
-| R-KIT | "The T-Display K230 Kit is finally here!" — 83 pts | r/LilyGO | 2026-08-20 | vendor announcement + discussion |
-| R-BARE | u/Opposite_Future2602: received bare board on risers, could not install an OS | r/LilyGO | 2026-08-20 | **firsthand ownership** |
-| R-BRICK | u/phirzcolru: bricked by boot-medium change, unresponsive to boot pin | r/LilyGO | 2026-08-21, 2026-08-28 | **firsthand ownership** |
-| R-ETH | u/Nobodytoyou_: the Ethernet port is oversized for the form factor | r/meshtastic | 2025-07-07 | firsthand observation |
-| R-BATT | u/Ryan_e3p: battery-life scepticism | r/meshtastic | 2025-07-07 | **opinion** |
-| R-IPX | u/No-Craft-7979: wants IP-rated options for field devices | r/LilyGO | 2026-08-20 | opinion / requirement |
-| R-DEBIAN | u/Nanocupid links `intx82/k230-debian` and compares to an MQ-Pro | r/meshtastic | 2025-07-09 | **informed interpretation** |
-| R-MESHUI | u/wirecrossed: building a full Meshtastic UI for this board | r/meshtastic | 2026-06-02 | **announced project**, no repo yet |
-| R-TOPS | u/Middle_Chicken_2577: "the k230 has abt 17 tops" | r/meshtastic | 2025-07-08 | **unsupported assertion** — contradicted by Canaan |
-| R-BUY | "Where do people buy CANMV K230 from?" | r/RISCV | 2024-05-08 | availability |
-| R-RVV | "Kendryte K230 (RVV1.0 supported) available for remote access" | r/RISCV | 2024-05-09 | community interest |
-
-## Software projects
-
-| ID | Project | URL | Commit / branch | Licence | Stars |
-|---|---|---|---|---|---|
-| G1 | `Xinyuan-LilyGO/T-Display-K230` | GitHub | `bb831ab358b66f5bd9a87ecd7c580fee4537492e`, `main` | **none declared** | 1 |
-| G2 | `Xinyuan-LilyGO/T-Display-K230_canmv_rt` | GitHub | `main`, pushed 2026-08-03 | none declared | 25 |
-| G3 | `Xinyuan-LilyGO/T-Display-K230-nRF52840` | GitHub | `4646a728580739d487126f47a521e9b8032b3c2c`, `master` | none declared | 0 |
-| G4 | `Xinyuan-LilyGO/T-Display-K230-nRF9151` | GitHub | `ed4ecbe34162dec9b81213a400198125bbd6e36f`, `main` | none declared | 0 |
-| G5 | `kendryte/k230_linux_sdk` | GitHub | `dev` | BSD-2-Clause | 62 |
-| G6 | `kendryte/k230_sdk` | GitHub | `main` | BSD-2-Clause | 273 |
-| G7 | `kendryte/canmv_k230` | GitHub | `canmv_k230` | none declared | 119 |
-| G8 | `sipeed/MaixPy` | GitHub | `main` | NOASSERTION | 843 |
-| G9 | `oreboot/oreboot` | GitHub | `main` | GPL-2.0 | 1795 |
-| G10 | `intx82/k230-debian` | GitHub | `6.6`, last push 2024-12-03 | BSD-2-Clause | 1 |
-| G11 | `ruyisdk/linux-xuantie-kernel` | GitHub | `7d4e1f444f461dbe3833bd99a4640e7b6c2cd529` | GPL-2.0 (kernel) | — |
-| G12 | LVGL, vendored | — | `59dc7e436ae97a25e32656739ea6a943f9f11b6a` + 4 LilyGO patches | MIT | — |
-| G13 | Nordic Serial LTE Modem, vendored | — | `13c80da97fe4d55ecb5a9745834d97be22821307` + 5 LilyGO patches | Nordic 5-clause | — |
-
-⚠ **Every LilyGO repository for this product has no licence file.** Redistribution status of
-their source and prebuilt firmware is therefore **unknown**.
diff --git a/devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md b/devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md
deleted file mode 100644
index d21eeab..0000000
--- a/devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md
+++ /dev/null
@@ -1,115 +0,0 @@
-# LilyGO T-Display-S3 AMOLED 1.43″ / 1.75″ (round)
-
-> Sold on the same store page as the [1.64″](../t-display-s3-amoled-1-64/README.md)
-> (handle `t-display-s3-amoled-1-64`, title *T-Display S3 AMOLED (DS)*).
-> SKUs `H741` 1.43″ **USD 23.99**, `H741-01` 1.75″ **USD 27.86**, `H741-02` 1.75″ half-circle
-> convex mirror **USD 30.25**. In stock 2026-09-07.
->
-> Repo `T-Display-S3-AMOLED-1.43-1.75` @ **`87aabe888eea6a7c0f95ce1991ca75fa98c2a172`**,
-> licence **MIT**. Research retrieved 2026-09-07. **Depth: medium.** No hardware.
-
-## Three panels, one Kconfig switch
-
-`components/private_library/pin_config.h` @ `87aabe8` opens with a three-way selector that
-**`#error`s if you pick none** — the clearest statement anywhere of what this product is:
-
-```c
-#if defined CONFIG_SCREEN_TYPE_DO0143FMST10
-#define DO0143FMST10 // 1.43 inches (CO5300 FT3168)
-#elif defined CONFIG_SCREEN_TYPE_DO0143FAT01
-#define DO0143FAT01  // DO0143FMST02 // 1.43 inches (SH8601 FT3168)
-#elif defined CONFIG_SCREEN_TYPE_H0175Y003AM
-#define H0175Y003AM  // 1.75 inches (CO5300 CST9217)
-#else
-#error "Unknown macro definition. Please select the correct macro definition."
-#endif
-```
-
-| Build symbol | Panel | Display driver | Touch |
-|---|---|---|---|
-| `DO0143FMST10` | 1.43″ round | **CO5300** (Chipone) | **FT3168** (FocalTech) |
-| `DO0143FAT01` / `DO0143FMST02` | 1.43″ round | **SH8601** (Shenghe Microelectronics) | **FT3168** |
-| `H0175Y003AM` | 1.75″ round | **CO5300** | **CST9217** (Hynitron) |
-
-**Two different display controllers and two different touch controllers ship under one product
-page.** This is the sharpest example of LilyGO's revision culture in the whole family.
-
-## Pinout — QSPI
-
-Verbatim from the same file @ `87aabe8`:
-
-| Signal | GPIO |
-|---|---|
-| `LCD_SDIO0..3` | 11, 13, 14, 15 |
-| `LCD_SCLK` | 12 |
-| `LCD_CS` | 10 |
-| `LCD_RST` | 17 |
-| `LCD_EN` | 16 |
-| `IIC_SDA` / `IIC_SCL` | 7 / 6 |
-| `TP_INT` | 9 |
-| `PCF8563_INT` | **9** — **the same pin as `TP_INT`** |
-| `BATTERY_VOLTAGE_ADC_DATA` | 4 |
-| `SD_CS` / `MOSI` / `MISO` / `SCLK` | 38 / 39 / 40 / 41 |
-
-**`TP_INT` and `PCF8563_INT` are both GPIO9.** Either the two interrupts are wire-ORed (likely,
-both being open-drain) or one define is wrong. **Not resolved** — no schematic is published.
-
-## Resolution conflict
-
-| Source | Value |
-|---|---|
-| repo README | **466 × 466** |
-| `pin_config.h` @ `87aabe8` | `LCD_WIDTH 473` / `LCD_HEIGHT 467` |
-
-Both for both panel sizes. The likely reading is that 473 × 467 is the CO5300/SH8601
-**addressable window** and 466 × 466 the visible circle — but that is inference. Recorded as
-family conflict [F4](../t-display-s3-shared/README.md#4-family-level-conflicts).
-
-## Chips
-
-| Function | Part | Component record |
-|---|---|---|
-| SoC | ESP32-S3R8, 16 MB flash, 8 MB OPI PSRAM | [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) |
-| Display | **CO5300** or **SH8601** | [`chipone/co5300`](../../../components/chipone/co5300/README.md) · [`shenghe-microelectronics/sh8601z`](../../../components/shenghe-microelectronics/sh8601z/README.md) |
-| Touch | **FT3168** or **CST9217** | [`focaltech/ft3168`](../../../components/focaltech/ft3168/README.md) · CST9217 *(record pending)* |
-| PMIC | **SY6970** | [`silergy/sy6970`](../../../components/silergy/sy6970/README.md) |
-| RTC | **PCF8563** | [`nxp/pcf8563`](../../../components/nxp/pcf8563/README.md) |
-| microSD | on-board, SPI | [`generic/micro-sd-sdmmc`](../../../components/generic/micro-sd-sdmmc/README.md) |
-
-Examples confirm each: `FT3168`, `SY6970`, `SY6970_OTG`, `PCF8563`, `PCF8563_Scheduled_INT`,
-`PCF8563_Timer_INT`, `Deep_Sleep_PCF8563_Scheduled_Wake_Up`, `Deep_Sleep_PCF8563_Timer_Wake_Up`,
-`Original_Test`, `GFX_FT3168_Image`, `lvgl_benchmark`, plus a `debug/` tree with `SD_MJPEG`
-video-playback examples.
-
-**The RTC-scheduled deep-sleep wake examples are notable** — this and the AMOLED Plus are the
-only boards in the family that can wake on a wall-clock time rather than a timer or a pin.
-
-## Documents shipped in `information/`
-
-`CO5300_V0.01.pdf` (13.2 MB) · `SH8601Z.pdf` (4.5 MB) · `FT3168.pdf` · `PCF8563.pdf` ·
-a Chinese PCF8563 spec · `AN_SY6970.pdf` · `EVB_SY6970.pdf` ·
-`DO0143FMST10-DWO.pdf` (panel drawing) ·
-`H0175Y003AM V0 1.75Inches 466X466 MIPI OR QSPI AMOLED.pdf`.
-The chip datasheets are filed under their component records; the panel drawings were **not**
-retrieved.
-
-Note the 1.75″ panel document's own title says **466 × 466** and "MIPI **OR** QSPI" — the panel
-supports both interfaces and LilyGO wires QSPI.
-
-## Sources
-
-| ID | Source | Class | Retrieved |
-|---|---|---|---|
-| R1 | repo README.md @ `87aabe8` | primary | 2026-09-07 |
-| R2 | `components/private_library/pin_config.h` @ `87aabe8` | primary | 2026-09-07 |
-| R3 | `information/*.pdf` tree listing @ `87aabe8` | primary | 2026-09-07 |
-| R4 | LilyGO store feed | primary | 2026-09-07 |
-
-## Gaps
-
-- **No schematic published.** Searched the full tree; there is none.
-- **GPIO9 double-assignment unresolved.**
-- **Resolution conflict unresolved.**
-- Medium-depth stub: no `features/`, no example catalogue, no acquisition manifest.
-- CST9217 has no component record yet.
-- No hardware.
diff --git a/devices/lilygo/t-display-s3-amoled-1-43-1-75/certification-and-compliance.md b/devices/lilygo/t-display-s3-amoled-1-43-1-75/certification-and-compliance.md
deleted file mode 100644
index d3ba357..0000000
--- a/devices/lilygo/t-display-s3-amoled-1-43-1-75/certification-and-compliance.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# Certification and compliance — t-display-s3-amoled-1-43-1-75
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-⚠ As above — no grant names these panel sizes. **Unresolved.**
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2ASYE-TDISS3-AMOLED`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-TDISS3-AMOLED`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2025-03-17** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2025-03-17 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2472 MHz** (Wi-Fi 2.4 GHz, ch 1–13 — ⚠ wider than the usual US 1–11) |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-TDISS3-AMOLED` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 1,797,931 | `28026191703ef5d5…` |
-| `ID-Label-Location-Info-E-Label.pdf` | 1,132,948 | `b59d8d92acbbc8f9…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,830,747 | `042a30c69f0e1175…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 152,844 | `8c40576dcdf810a5…` |
-| `Test-Report-Antenna-Specification.pdf` | 1,444,723 | `ff7b49a25f654d63…` |
-| `Users-Manual-User-Manual.pdf` | 2,753,493 | `d4106c5cc334ca45…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-TDISS3-AMOLED/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-TDISS3-AMOLED/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-amoled-1-43-1-75/market-and-pricing.md b/devices/lilygo/t-display-s3-amoled-1-43-1-75/market-and-pricing.md
deleted file mode 100644
index e727dfb..0000000
--- a/devices/lilygo/t-display-s3-amoled-1-43-1-75/market-and-pricing.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# Market and pricing — t-display-s3-amoled-1-43-1-75
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.75 inch Half Circle Convex Mirror [H741-02] | `H741-02` | **USD 30.25** | ✅ yes |
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.75 inch [H741-01] | `H741-01` | **USD 27.86** | ✅ yes |
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.43 inch [H741] | `H741` | **USD 23.99** | ✅ yes |
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.64 inch [H708] | `H708` | **USD 22.99** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 30.25, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3-amoled-1-64`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-⚠ **Same store handle as `t-display-s3-amoled-1-64`.** The 1.43″ (USD 23.99) and 1.75″ (USD 27.86 / 30.25 convex) variants live under the handle named for the 1.64″. **This repo's two records map onto one storefront product**; that is a repo-side split, not a vendor one.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3-amoled-1-64/README.md b/devices/lilygo/t-display-s3-amoled-1-64/README.md
deleted file mode 100644
index 55de196..0000000
--- a/devices/lilygo/t-display-s3-amoled-1-64/README.md
+++ /dev/null
@@ -1,80 +0,0 @@
-# LilyGO T-Display-S3 AMOLED 1.64″ (sold as "T-Display S3 AMOLED (DS)")
-
-> **Product:** store handle **`t-display-s3-amoled-1-64`**, title *T-Display S3 AMOLED (DS)*,
-> published **2024-07-18**. That one page sells **four different panels**; this record covers
-> the **1.64″**, SKU `H708`, **USD 22.99** (in stock 2026-09-07). The 1.43″ and 1.75″ are
-> [a separate record](../t-display-s3-amoled-1-43-1-75/README.md) with a separate repository.
->
-> Repo `T-Display-S3-AMOLED-1.64` @ **`e236a4dfb3295c473d8ac7c240cbea93313707c0`**,
-> **default branch `arduino-esp32-libs_V2.0.14`** — not `main`.
-> Licence **GPL-3.0**. Research retrieved 2026-09-07. **Depth: medium.** No hardware.
-
-## Identity
-
-| | | Source |
-|---|---|---|
-| Panel | 1.64″ AMOLED, **280 × 456** | repo README @ `e236a4d` |
-| Display driver | **ICNA3311 (CO5300)** — the README writes both names | repo README |
-| CO5300 maker | **Chipone Technology (Beijing) Co., Ltd.** — established from the datasheet cover, decoded through a code-point-offset text layer and confirmed two ways | `information/CO5300_V0.01.pdf` |
-| Touch | **FocalTech FT3168**, I²C | repo README + `information/FT3168.pdf` |
-| PMIC | **Silergy SY6970**, I²C | repo README; `examples/SY6970`, `examples/SY6970_OTG` |
-| SoC | ESP32-S3R8, **16 MB flash, 8 MB OPI PSRAM** | repo README |
-| Panel spec | `SPEC-DO0164FMST02-20240126.pdf` ships in `information/` | tree listing |
-| Component records | [`chipone/co5300`](../../../components/chipone/co5300/README.md) · [`focaltech/ft3168`](../../../components/focaltech/ft3168/README.md) · [`silergy/sy6970`](../../../components/silergy/sy6970/README.md) |
-
-## The naming problem
-
-The store page title is **"T-Display S3 AMOLED (DS)"**. "DS" is not explained anywhere. The
-same page sells:
-
-| SKU | Panel | USD 2026-09-07 |
-|---|---|---|
-| `H708` | **1.64 inch** | 22.99 |
-| `H741` | 1.43 inch | 23.99 |
-| `H741-01` | 1.75 inch | 27.86 |
-| `H741-02` | 1.75 inch **half-circle convex mirror** | 30.25 |
-
-…and two different GitHub repositories cover them, with different display controllers and
-different touch controllers. **Buying "T-Display S3 AMOLED (DS)" without specifying the SKU
-tells you nothing about what arrives.**
-
-## Toolchain — pinned, and visible in the branch name
-
-The default branch is literally called **`arduino-esp32-libs_V2.0.14`**, and the README's
-example table repeats per example:
-`[Platformio IDE][espressif32-v6.5.0]` / `[Arduino IDE][esp32_v2.0.14]`.
-Board settings: `QIO 80MHz`, `16MB (128Mb)`, `16M Flash (3MB APP/9.9MB FATFS)`, `OPI PSRAM` —
-the family standard.
-
-## Examples
-
-`FT3168` (touch), `GFX_FT3168_Image`, `SY6970` (PMU), `SY6970_OTG`, `Lvgl_benchmark`.
-The **`Lvgl_benchmark`** is notable: it exists here and **not** in the base-board repo, so this
-is the only board in the family with a vendor LVGL benchmark.
-
-## Firmware
-
-`firmware/` holds deep-sleep and light-sleep wake-up images plus a `deprecated/` directory with
-seven more, including a Wi-Fi iperf image and a screen colour test. Filenames use bracketed
-tags: `[T-Display-S3-AMOLED-1.64_V1.0][Deep_Sleep_Wake_Up]_firmware_V1.0.0.bin`.
-**None retrieved by this pass.**
-
-## Sources
-
-| ID | Source | Class | Retrieved |
-|---|---|---|---|
-| S64-1 | repo README.md @ `e236a4d` | primary | 2026-09-07 |
-| S64-2 | `information/CO5300_V0.01.pdf` (13 236 092 B) | credible mirror | 2026-09-07 — **archived**, see [`components/chipone/co5300/artifacts/`](../../../components/chipone/co5300/artifacts/) |
-| S64-3 | `information/FT3168.pdf` (926 072 B) | credible mirror | 2026-09-07 → [`components/focaltech/ft3168/artifacts/`](../../../components/focaltech/ft3168/artifacts/) |
-| S64-4 | LilyGO store feed | primary | 2026-09-07 |
-
-## Gaps
-
-- **Medium-depth stub.** No pinout table: `boards/esp32s3_flash_*.json` exist but **no
-  `pin_config.h` was found in this repository** — the pin map for the 1.64″ was **not
-  established** by this pass. That is the biggest single gap here.
-- No schematic is published for this board. Searched the full tree at `e236a4d`; there is no
-  `schematic/` directory. **This is the only board in the family with no published schematic.**
-- Firmware not retrieved; `SPEC-DO0164FMST02` panel spec not retrieved.
-- The relationship between `ICNA3311` and `CO5300` (same die? rebadge? successor?) is
-  **unresolved** — LilyGO writes "ICNA3311(CO5300)" and the datasheet says only CO5300.
diff --git a/devices/lilygo/t-display-s3-amoled-1-64/certification-and-compliance.md b/devices/lilygo/t-display-s3-amoled-1-64/certification-and-compliance.md
deleted file mode 100644
index b79e008..0000000
--- a/devices/lilygo/t-display-s3-amoled-1-64/certification-and-compliance.md
+++ /dev/null
@@ -1,159 +0,0 @@
-# Certification and compliance — t-display-s3-amoled-1-64
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-⚠ **No grant names the 1.43″/1.64″/1.75″ sizes.** The two AMOLED grants name 'T-Display-S3-AMOLED' and '1.91'. Whether the DS-series sizes ride on either grant is **unresolved**.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2ASYE-TDISS3-AMOLED`, `2ASYE-T-DISPLAY-19`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-TDISS3-AMOLED`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2025-03-17** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2025-03-17 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2472 MHz** (Wi-Fi 2.4 GHz, ch 1–13 — ⚠ wider than the usual US 1–11) |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-TDISS3-AMOLED` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 1,797,931 | `28026191703ef5d5…` |
-| `ID-Label-Location-Info-E-Label.pdf` | 1,132,948 | `b59d8d92acbbc8f9…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,830,747 | `042a30c69f0e1175…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 152,844 | `8c40576dcdf810a5…` |
-| `Test-Report-Antenna-Specification.pdf` | 1,444,723 | `ff7b49a25f654d63…` |
-| `Users-Manual-User-Manual.pdf` | 2,753,493 | `d4106c5cc334ca45…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-TDISS3-AMOLED/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-TDISS3-AMOLED/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2ASYE-T-DISPLAY-19`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-03-21** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-03-21 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 15 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY-19` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 805,031 | `c4d77ec49971c832…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info.pdf` | 546,549 | `e50584b3ca7fa52b…` |
-| `Internal-Photos-Internal-Photos.pdf` | 763,922 | `bb73f298bb8eec10…` |
-| `RF-Exposure-Info-RF-Exposure-Info.pdf` | 146,095 | `0d98c024a6d1a029…` |
-| `Test-Report-ATN-Test-Report.pdf` | 1,174,923 | `a1300af9d0563dac…` |
-| `Users-Manual-Users-Manual.pdf` | 1,068,816 | `97096597308fdd0e…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY-19/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY-19/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-amoled-1-64/market-and-pricing.md b/devices/lilygo/t-display-s3-amoled-1-64/market-and-pricing.md
deleted file mode 100644
index bd58fad..0000000
--- a/devices/lilygo/t-display-s3-amoled-1-64/market-and-pricing.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# Market and pricing — t-display-s3-amoled-1-64
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.75 inch Half Circle Convex Mirror [H741-02] | `H741-02` | **USD 30.25** | ✅ yes |
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.75 inch [H741-01] | `H741-01` | **USD 27.86** | ✅ yes |
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.43 inch [H741] | `H741` | **USD 23.99** | ✅ yes |
-| T-Display S3 AMOLED (DS) | 2024-07-18 | 1.64 inch [H708] | `H708` | **USD 22.99** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 30.25, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3-amoled-1-64`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-The store calls this handle **'T-Display S3 AMOLED (DS)'** and sells four panel sizes under it: 1.64″ USD 22.99, 1.43″ USD 23.99, 1.75″ USD 27.86, 1.75″ convex-mirror USD 30.25. ⚠ This repo splits the same store handle across **two** device records — see the note below.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3-amoled-plus/README.md b/devices/lilygo/t-display-s3-amoled-plus/README.md
deleted file mode 100644
index 5f4873b..0000000
--- a/devices/lilygo/t-display-s3-amoled-plus/README.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# LilyGO T-Display-S3 AMOLED Plus
-
-> **Product:** T-Display S3 AMOLED Plus · handle `t-display-s3-amoled-plus` · published
-> **2024-10-31** · SKU `H754` "1.9inch" · **USD 32.68**, in stock 2026-09-07.
-> Covered by `LilyGo-AMOLED-Series` @ **`6d1dc008b94578cc34ba4a0f3b223dd808ca963f`**.
-> Research retrieved 2026-09-07. **Depth: medium.** No hardware.
-
-## Identity — the same panel, a completely different board
-
-The panel is the **same 1.91″ 240 × 536 RM67162 AMOLED** as the
-[T-Display-S3 AMOLED](../t-display-s3-amoled/README.md). Everything behind it is different, and
-the differences are the reason to buy it.
-
-| Function | Part | Interface | Component record |
-|---|---|---|---|
-| SoC | ESP32-S3 | — | [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) |
-| Flash `U3` | **W25Q128JV**, 16 MB | QSPI | [`winbond/w25q128jv`](../../../components/winbond/w25q128jv/README.md) |
-| Display | RM67162, 240×536 | QSPI | [`raydium/rm67162`](../../../components/raydium/rm67162/README.md) |
-| **Charger / PMIC `U6`** | **TI BQ25896** — I²C, buck charger with OTG boost, ADC, path management | I²C | [`texas-instruments/bq25896`](../../../components/texas-instruments/bq25896/README.md) |
-| **RTC `U7`** | **NXP PCF85063ATL** | I²C | [`nxp/pcf85063a`](../../../components/nxp/pcf85063a/README.md) |
-| **RTC backup cell `U8`** | **Seiko MS412FE-FL26E** rechargeable lithium coin | — | *(record pending)* |
-| Regulator `U5` | RT9080-33GJ5 LDO | — | *(record pending)* |
-| Display supply `U4` | `AXPM65611` — **unidentified** | — | [unidentified](../../../components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md) |
-| **microSD `J1`** | `MISROSD/TF_SLOT` | SPI/SDMMC | [`generic/micro-sd-sdmmc`](../../../components/generic/micro-sd-sdmmc/README.md) |
-| Battery connectors | **two** — `CN4`, `CN5`, both 2P 2.5 mm | — | — |
-| Antenna | `P1` IPEX-1 | — | — |
-| Headers | `P4`, `P5` — 14-pin 2.54 mm | — | — |
-
-Derived from `schematic/T-Display-S3-AMOLED-Plus.pdf` @ `6d1dc00`
-(468 313 B, SHA-256 `ec4a97b697dd14413c88ea98d9bedaf601fa98ef24d88c9b0d7bf3fd0c2d046f`,
-retained under `artifacts/schematic/`). Part identities are read from the sheet's designator
-strings; **net connectivity was not traced.**
-
-## Why it matters
-
-Three things the plain AMOLED board does not have:
-
-1. **A real PMIC.** The BQ25896 is I²C-controlled: programmable charge current, input-current
-   limit, OTG 5 V boost, and on-chip ADC for battery/system/input voltage and charge current.
-   Compare the plain AMOLED's dumb linear **TP4065**, where charge current is a soldered
-   resistor. LilyGO ships `examples/PPM_Example_for_191Plus` for it.
-2. **A battery-backed RTC.** PCF85063ATL plus a Seiko MS412FE rechargeable coin cell means the
-   clock survives a main-battery swap. Nothing else in the AMOLED line has this.
-3. **A microSD slot on the board**, not on a shield.
-
-LilyGO's own sleep figure reflects the added complexity: **≈230–700 µA "dynamic"** deep sleep
-against a flat ≈230 µA for the plain AMOLED — the range is the RTC and PMIC doing work.
-Active current is the same 90–230+ mA class.
-
-## Software
-
-`LilyGo-AMOLED-Series` auto-detects the board. Pin map is in `product_pins.h` @ `b1a1cc5` and
-in the library's board table.
-
-**ESPHome supports it as a named model** — `T-DISPLAY-S3-AMOLED-PLUS` in
-`esphome/components/mipi_spi/models/amoled.py` (`dev`, 2026-09-07):
-`cs_pin=6, reset_pin=17, dc_pin=7, enable_pin=38, data_rate=40MHz, brightness=0xD0`, with a
-**16-command init sequence** (`PAGESEL 4 / 0x6A 0x00 / PAGESEL 5 / PAGESEL 7 / 0x07 0x4F / …`).
-That sequence differs from the plain AMOLED's, which is `(SLPOUT,)` only — so **the two boards
-need different panel initialisation despite the same controller.** That is a concrete, useful
-finding: do not assume RM67162 code ports between them.
-
-## Sources
-
-| ID | Source | Class | Retrieved |
-|---|---|---|---|
-| PL1 | `LilyGo-AMOLED-Series` README.MD § *Support Product* @ `6d1dc00` | primary | 2026-09-07 |
-| PL2 | `schematic/T-Display-S3-AMOLED-Plus.pdf` @ `6d1dc00` | primary | 2026-09-07 |
-| PL3 | `esphome/components/mipi_spi/models/amoled.py`, `dev` | primary (third-party) | 2026-09-07 |
-| PL4 | LilyGO store feed | primary | 2026-09-07 |
-
-## Gaps
-
-- **This is a medium-depth record.** No `pinouts-and-buses.md`, `features/` or `examples/`
-  directory was written. What is missing: a full GPIO table, per-feature guides, an example
-  catalogue and an acquisition manifest.
-- Net connectivity not traced.
-- `AXPM65611` (`U4`) unidentified.
-- **Two battery connectors** (`CN4`, `CN5`) — whether they are parallel, alternates, or one is
-  for the RTC cell is **not established**.
-- No hardware; no measurements.
diff --git a/devices/lilygo/t-display-s3-amoled-plus/artifacts/schematic/T-Display-S3-AMOLED-Plus.pdf b/devices/lilygo/t-display-s3-amoled-plus/artifacts/schematic/T-Display-S3-AMOLED-Plus.pdf
deleted file mode 100644
index 77a11be..0000000
Binary files a/devices/lilygo/t-display-s3-amoled-plus/artifacts/schematic/T-Display-S3-AMOLED-Plus.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled-plus/certification-and-compliance.md b/devices/lilygo/t-display-s3-amoled-plus/certification-and-compliance.md
deleted file mode 100644
index c506fb8..0000000
--- a/devices/lilygo/t-display-s3-amoled-plus/certification-and-compliance.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# Certification and compliance — t-display-s3-amoled-plus
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-⚠ No grant names 'AMOLED Plus'. The store lists it as 1.9 inch, which *may* place it under `2ASYE-T-DISPLAY-19` ('AMOLED 1.91'). **Inferred from the panel size alone; not confirmed.**
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2ASYE-T-DISPLAY-19`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-DISPLAY-19`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-03-21** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-03-21 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 15 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY-19` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 805,031 | `c4d77ec49971c832…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info.pdf` | 546,549 | `e50584b3ca7fa52b…` |
-| `Internal-Photos-Internal-Photos.pdf` | 763,922 | `bb73f298bb8eec10…` |
-| `RF-Exposure-Info-RF-Exposure-Info.pdf` | 146,095 | `0d98c024a6d1a029…` |
-| `Test-Report-ATN-Test-Report.pdf` | 1,174,923 | `a1300af9d0563dac…` |
-| `Users-Manual-Users-Manual.pdf` | 1,068,816 | `97096597308fdd0e…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY-19/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY-19/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-amoled-plus/market-and-pricing.md b/devices/lilygo/t-display-s3-amoled-plus/market-and-pricing.md
deleted file mode 100644
index 9e546af..0000000
--- a/devices/lilygo/t-display-s3-amoled-plus/market-and-pricing.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Market and pricing — t-display-s3-amoled-plus
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 AMOLED Plus | 2024-10-31 | 1.9inch [H754] | `H754` | **USD 32.68** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 32.68, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3-amoled-plus`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `H754`, 1.9 inch.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3-amoled/README.md b/devices/lilygo/t-display-s3-amoled/README.md
deleted file mode 100644
index 92bd05c..0000000
--- a/devices/lilygo/t-display-s3-amoled/README.md
+++ /dev/null
@@ -1,141 +0,0 @@
-# LilyGO T-Display-S3 AMOLED (1.91″)
-
-> **Product:** T-Display S3 AMOLED · store handle `t-display-s3-amoled` · published **2023-04-14** ·
-> **16 SKUs** including **V1.0 and V2.0 sold concurrently**, touch and non-touch, three regional
-> warehouses · from **USD 26.44** (2026-09-07).
->
-> **Two repositories cover this board.** The original
-> [`T-Display-S3-AMOLED`](https://github.com/Xinyuan-LilyGO/T-Display-S3-AMOLED) @ `edd1333`
-> **stopped receiving pushes on 2024-08-09**; the live one is
-> [`LilyGo-AMOLED-Series`](https://github.com/Xinyuan-LilyGO/LilyGo-AMOLED-Series) @ `6d1dc00`,
-> a single Arduino/PlatformIO library covering four AMOLED boards. **Use the latter.**
->
-> Research retrieved **2026-09-07**. No hardware. Part of the
-> [T-Display-S3 family](../t-display-s3-shared/README.md).
-
-## Identity
-
-| | |
-|---|---|
-| Panel | 1.91″ AMOLED, **240 × 536**, **350 nits** (vendor figure) |
-| Controller | **Raydium RM67162**, **QSPI** — not parallel, not plain SPI |
-| Touch | optional; **Hynitron CST816** family, I²C. LilyGO's library supports "both touch and non-touch versions" from one build |
-| SoC | ESP32-S3R8, 16 MB flash, 8 MB OPI PSRAM |
-| Sold as | V1.0 / V2.0 × soldered / non-soldered × touch / non-touch × 3 warehouses |
-| Component records | [`raydium/rm67162`](../../../components/raydium/rm67162/README.md) · [`hynitron/cst816d`](../../../components/hynitron/cst816d/README.md) · [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) · [`winbond/w25q128jv`](../../../components/winbond/w25q128jv/README.md) |
-
-## The V1.0 / V2.0 problem — read before buying
-
-LilyGO sells **both revisions at once** (`H619`/`H634` = V1.0, `H713`/`H712` = V2.0, all in
-stock 2026-09-07) and publishes **no statement of what differs**. Comparing the two schematics
-it ships:
-
-| | `T-DISPLAY-S3-AMOLED.pdf` (older repo) | `T-Display-S3-AMOLED-Touch.pdf` (`LilyGo-AMOLED-Series`) |
-|---|---|---|
-| Flash `U3` | **`W25Q32`** — 4 MB | **`W25Q128JV`** — 16 MB |
-| 3.3 V regulator | `U4 = IC_RT9080` (LDO) | `U4 = SY8089A1AAC` (**buck**) |
-| Display supply | `U6 = IC_BV6802` | `U5 = AXPM65611` |
-| Charger | `U5 = TP4065` | `U6 = TP4065` |
-| Transistors | — | `Q1 NCE3401AY`, `Q2 KIA3400` |
-| ESD | `D1/D2 ESD5451N-2` | `D5 SMF5.0A`, `D4 B5819W` |
-
-The `W25Q32` is the alarming one: **4 MB where every README and store listing says 16 MB.**
-Most likely a stale early sheet, but it is the vendor's own document and it is still published.
-**Run `esptool.py flash_id` before you rely on 16 MB.** Recorded as family conflict
-[F3](../t-display-s3-shared/README.md#4-family-level-conflicts) and revision
-[R2](../t-display-s3-shared/board-revision-drift.md#r2--t-display-s3-amoled-191-v10-and-v20-sold-concurrently).
-
-## Pinout
-
-From `examples/factory/pins_config.h` @ **`edd133335c9f7c38d1e9be2d0eb67371f1f6428e`**,
-cross-checked against `LilyGo-Display-IDF/main/product_pins.h`
-(`#elif CONFIG_LILYGO_T_DISPLAY_S3_AMOLED`) @ `b1a1cc5`. **The two agree exactly.**
-
-| Signal | GPIO | Note |
-|---|---|---|
-| `TFT_QSPI_CS` | 6 | |
-| `TFT_QSPI_SCK` | 47 | |
-| `TFT_QSPI_D0` | 18 | also `TFT_MOSI` |
-| `TFT_QSPI_D1` | 7 | also `TFT_DC` |
-| `TFT_QSPI_D2` | 48 | |
-| `TFT_QSPI_D3` | 5 | |
-| `TFT_QSPI_RST` | 17 | |
-| `TFT_TE` | 9 | tearing-effect input |
-| `TFT_SDO` | 8 | |
-| `PIN_LED` | 38 | **not a backlight** — AMOLED is self-emissive. This is an indicator |
-| `PIN_BAT_VOLT` | 4 | same divider arrangement as the base board |
-| `PIN_BUTTON_1` | 0 | BOOT |
-| `PIN_BUTTON_2` | **21** | **not GPIO14** — code from the base board will read a floating pin |
-| I²C `SDA` / `SCL` | **3 / 2** | per `product_pins.h`; **touch IRQ is GPIO21 on the Touch variant, which collides with `BUTTON_2`** |
-
-SPI clock in LilyGO's own example: **75 MHz** (`#define SPI_FREQUENCY 75000000`), mode 0,
-`SPI2_HOST`. That is far faster than the base board's 16 MHz parallel bus — QSPI at 75 MHz
-moves 4 bits per clock.
-
-**There is no GPIO15 power gate on this board.** The single most important base-board
-workaround does not apply, and looking for it wastes time.
-
-## Display and software
-
-`TFT_eSPI` **cannot drive this panel** — it has no QSPI transport. LilyGO's "TFT_eSPI examples"
-in `LilyGo-AMOLED-Series` are `TFT_eSPI` **Sprites** rendered off-screen and pushed by the
-library's own QSPI routine. Use:
-
-| Route | How |
-|---|---|
-| **`LilyGo-AMOLED-Series`** (recommended) | Arduino Library Manager → "LilyGO AMOLED Series" → Install All. Auto-detects which of the four AMOLED boards it is on |
-| `Arduino_GFX` | `Arduino_ESP32QSPI` + an RM67162 init |
-| **ESPHome** | `mipi_spi` model **`T-DISPLAY-S3-AMOLED`**: `cs_pin=6, reset_pin=17, enable_pin=38, bus_mode=QUAD, brightness=0xD0, no_slpout=True`. Confirmed in `esphome/components/mipi_spi/models/amoled.py`, `dev` @ 2026-09-07 |
-| LVGL | 8.x by default; the library ships an `lv_conf.h.v9` you rename to move to 9.x |
-
-Dependencies the library declares: `XPowersLib v0.2.7`, `SensorLib v0.2.4`, `lvgl 8.x/9.x`,
-`AceButton v1.10.1`, `Adafruit_NeoPixel v1.11.0`, `TinyGPSPlus v1.0.3`.
-Arduino core: **V2.0.16 or later** — note this is *different from and newer than* the 2.0.14
-the base board pins.
-
-## Power
-
-| | |
-|---|---|
-| Charger | **TP4065** on both schematics |
-| Regulator | RT9080 LDO (V1.0) → SY8089A1AAC buck (V2.0) |
-| Battery sense | GPIO4 |
-| Vendor current figures | **90–230+ mA** active at 240 MHz with Wi-Fi; **≈230 µA** deep sleep, external GPIO0 wake |
-
-Those sleep figures are LilyGO's own, from the `LilyGo-AMOLED-Series` README table @ `6d1dc00`
-— and unlike the base board, they exist. They are **not** transferable to the base board.
-
-## Add-ons
-
-A **Camera Shield** exists (`H679`, USD 6.33) with its own schematic and example; it is the
-only 1.91″-specific accessory.
-
-## Documentation map
-
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — the V1.0/V2.0 problem, the flash-size
-  conflict, the GPIO21 collision, two unidentified parts
-- Pinout, development and software: **in this file** (§ *Pinout*, § *Display and software*)
-- Family-level material: [`../t-display-s3-shared/README.md`](../t-display-s3-shared/README.md),
-  [`board-revision-drift.md`](../t-display-s3-shared/board-revision-drift.md),
-  [`sources.md`](../t-display-s3-shared/sources.md)
-- Pricing for every board in the family, dated 2026-09-07:
-  [`../t-display-s3/market-and-pricing.md`](../t-display-s3/market-and-pricing.md)
-- The `USB CDC On Boot` trap and the Arduino-core version pin apply here too:
-  [`../t-display-s3/features/usb.md`](../t-display-s3/features/usb.md),
-  [`../t-display-s3/development.md`](../t-display-s3/development.md)
-
-**Not written for this board:** a standalone `pinouts-and-buses.md`, `features/`,
-`examples/catalog.json` or `acquisition/manifest.json`. This is a **full-ish**, not a full,
-record — see [`../t-display-s3-shared/research-log.md`](../t-display-s3-shared/research-log.md)
-for the depth table.
-
-## Artifacts
-
-`artifacts/schematic/T-DISPLAY-S3-AMOLED.pdf` (507 994 B, SHA-256 `e44158506e7ca189…`) —
-the V1.0-era sheet.
-`artifacts/schematic/T-Display-S3-AMOLED-Touch.pdf` (361 409 B, SHA-256 `da46e0f36732b99c…`) —
-the current sheet, and the one LilyGO's resource table points at for **both** touch and
-non-touch.
-`artifacts/schematic/Camera-Shield.pdf` (157 812 B, SHA-256 `362bdcfb504a57c8…`).
-Both retrieved 2026-09-07 at the commits above. RM67162 and CST816 datasheets are filed under
-their components.
diff --git a/devices/lilygo/t-display-s3-amoled/acquisition/manifest.json b/devices/lilygo/t-display-s3-amoled/acquisition/manifest.json
deleted file mode 100644
index 825dcf7..0000000
--- a/devices/lilygo/t-display-s3-amoled/acquisition/manifest.json
+++ /dev/null
@@ -1,440 +0,0 @@
-{
- "record": "devices/lilygo/t-display-s3-amoled",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-19-7190709",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-19/Test-Report/ATN-Test-Report-7190709.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190709",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190709.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-19",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/Test-Report/ATN-Test-Report-7190709.pdf"
-   ],
-   "sha256": "a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62",
-   "bytes": 1174923,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-21",
-   "fcc_id": "2ASYE-T-DISPLAY-19",
-   "fcc_document_id": "7190709",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "ATN Test Report",
-   "grant_date": "2024-03-21",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-19-7190736",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-19/External-Photos/External-Photos-7190736.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190736",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190736.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-19",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/External-Photos/External-Photos-7190736.pdf"
-   ],
-   "sha256": "c4d77ec49971c8328323b5cc1c607980bea75a1d24933017431a7ce285a83ea7",
-   "bytes": 805031,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-21",
-   "fcc_id": "2ASYE-T-DISPLAY-19",
-   "fcc_document_id": "7190736",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2024-03-21",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-19-7190706",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-19/Label/ID-Label-Location-Info-7190706.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190706",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190706.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-19",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/Label/ID-Label-Location-Info-7190706.pdf"
-   ],
-   "sha256": "e50584b3ca7fa52b83b40ccdaea4f97563e3bb1596e63af58636d47d25bdfca6",
-   "bytes": 546549,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-id-label-location-info.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-21",
-   "fcc_id": "2ASYE-T-DISPLAY-19",
-   "fcc_document_id": "7190706",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "ID Label/Location Info",
-   "grant_date": "2024-03-21",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-19-7190737",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-19/Internal-Photos/Internal-Photos-7190737.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190737",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190737.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-19",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/Internal-Photos/Internal-Photos-7190737.pdf"
-   ],
-   "sha256": "bb73f298bb8eec1000761260f9c7475008c00c82f739e4e269354d0bf3313d21",
-   "bytes": 763922,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-21",
-   "fcc_id": "2ASYE-T-DISPLAY-19",
-   "fcc_document_id": "7190737",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2024-03-21",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-19-7190712",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-19/RF-Exposure-Info/RF-Exposure-Info-7190712.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190712",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190712.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-19",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/RF-Exposure-Info/RF-Exposure-Info-7190712.pdf"
-   ],
-   "sha256": "0d98c024a6d1a029fc98c09e316d53e30b686a4f688f8732f2d329ad2a165935",
-   "bytes": 146095,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-21",
-   "fcc_id": "2ASYE-T-DISPLAY-19",
-   "fcc_document_id": "7190712",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Info",
-   "grant_date": "2024-03-21",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-19-7190708",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-19/User-Manual/Users-Manual-7190708.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190708",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190708.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-19",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/User-Manual/Users-Manual-7190708.pdf"
-   ],
-   "sha256": "97096597308fdd0e2c78366f937f1d9b5506f8cb9bd765ba3a8fcf652673b40c",
-   "bytes": 1068816,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-21",
-   "fcc_id": "2ASYE-T-DISPLAY-19",
-   "fcc_document_id": "7190708",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "Users Manual",
-   "grant_date": "2024-03-21",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISS3-AMOLED-8123274",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISS3-AMOLED/Test-Report/Antenna-Specification-8123274.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123274",
-    "https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123274.pdf",
-    "https://fccid.io/2ASYE-TDISS3-AMOLED",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/Test-Report/Antenna-Specification-8123274.pdf"
-   ],
-   "sha256": "ff7b49a25f654d6329c13074335d801eda8e54e90daad4b0bc17ebb40b9a3399",
-   "bytes": 1444723,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-03-17",
-   "fcc_id": "2ASYE-TDISS3-AMOLED",
-   "fcc_document_id": "8123274",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Specification",
-   "grant_date": "2025-03-17",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Bay Area Compliance Laboratories Corp (Shenzhen)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISS3-AMOLED-8123273",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISS3-AMOLED/Label/E-Label-8123273.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123273",
-    "https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123273.pdf",
-    "https://fccid.io/2ASYE-TDISS3-AMOLED",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/Label/E-Label-8123273.pdf"
-   ],
-   "sha256": "b59d8d92acbbc8f9f6b0ff8be9e6e0c0788ebab2279f88610b277dffadc6a260",
-   "bytes": 1132948,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-e-label.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-03-17",
-   "fcc_id": "2ASYE-TDISS3-AMOLED",
-   "fcc_document_id": "8123273",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "E-Label",
-   "grant_date": "2025-03-17",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Bay Area Compliance Laboratories Corp (Shenzhen)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISS3-AMOLED-8123268",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISS3-AMOLED/External-Photos/External-Photos-8123268.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123268",
-    "https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123268.pdf",
-    "https://fccid.io/2ASYE-TDISS3-AMOLED",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/External-Photos/External-Photos-8123268.pdf"
-   ],
-   "sha256": "28026191703ef5d57ec29a752dbee1d896c3dd6dbc180a201e8d2c39c9eb7930",
-   "bytes": 1797931,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-03-17",
-   "fcc_id": "2ASYE-TDISS3-AMOLED",
-   "fcc_document_id": "8123268",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2025-03-17",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Bay Area Compliance Laboratories Corp (Shenzhen)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISS3-AMOLED-8123269",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISS3-AMOLED/Internal-Photos/Internal-Photos-8123269.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123269",
-    "https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123269.pdf",
-    "https://fccid.io/2ASYE-TDISS3-AMOLED",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/Internal-Photos/Internal-Photos-8123269.pdf"
-   ],
-   "sha256": "042a30c69f0e1175a47b14db052a1587de627a0e12600a41ea9dc5780c262497",
-   "bytes": 1830747,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-03-17",
-   "fcc_id": "2ASYE-TDISS3-AMOLED",
-   "fcc_document_id": "8123269",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2025-03-17",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Bay Area Compliance Laboratories Corp (Shenzhen)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISS3-AMOLED-8123279",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISS3-AMOLED/RF-Exposure-Info/RF-Exposure-8123279.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123279",
-    "https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123279.pdf",
-    "https://fccid.io/2ASYE-TDISS3-AMOLED",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/RF-Exposure-Info/RF-Exposure-8123279.pdf"
-   ],
-   "sha256": "8c40576dcdf810a5a88a9277110802fd85e8b6e7549d75471efec77d9ebd7623",
-   "bytes": 152844,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-03-17",
-   "fcc_id": "2ASYE-TDISS3-AMOLED",
-   "fcc_document_id": "8123279",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure",
-   "grant_date": "2025-03-17",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Bay Area Compliance Laboratories Corp (Shenzhen)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISS3-AMOLED-8123278",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISS3-AMOLED/User-Manual/User-Manual-8123278.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123278",
-    "https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123278.pdf",
-    "https://fccid.io/2ASYE-TDISS3-AMOLED",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/User-Manual/User-Manual-8123278.pdf"
-   ],
-   "sha256": "d4106c5cc334ca45ca17c4f9b321b088d288065668defcde15e209b18d681638",
-   "bytes": 2753493,
-   "destination": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-03-17",
-   "fcc_id": "2ASYE-TDISS3-AMOLED",
-   "fcc_document_id": "8123278",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2025-03-17",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Bay Area Compliance Laboratories Corp (Shenzhen)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-amoled",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf.ARCHIVED.md
deleted file mode 100644
index 777c39a..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-19-atn-test-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,174,923 B (1.12 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,174,923 B (1.12 MiB) |
-| SHA-256 | `a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62` |
-| FCC ID | **`2ASYE-T-DISPLAY-19`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | ATN Test Report |
-| FCC document id | 7190709 |
-| Upstream publication date | 2024-03-21 |
-| Grant date | 2024-03-21 |
-| Equipment class | T-Display-S3 AMOLED 1.91, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19/Test-Report/ATN-Test-Report-7190709.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190709>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190709.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/Test-Report/ATN-Test-Report-7190709.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-atn-test-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-19/Test-Report/ATN-Test-Report-7190709.pdf" -o "2ASYE-T-DISPLAY-19-atn-test-report.pdf"
-echo "a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62  2ASYE-T-DISPLAY-19-atn-test-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 5aadfdd..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-19-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 805,031 B (0.77 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 805,031 B (0.77 MiB) |
-| SHA-256 | `c4d77ec49971c8328323b5cc1c607980bea75a1d24933017431a7ce285a83ea7` |
-| FCC ID | **`2ASYE-T-DISPLAY-19`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 7190736 |
-| Upstream publication date | 2024-03-21 |
-| Grant date | 2024-03-21 |
-| Equipment class | T-Display-S3 AMOLED 1.91, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19/External-Photos/External-Photos-7190736.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190736>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190736.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/External-Photos/External-Photos-7190736.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-19/External-Photos/External-Photos-7190736.pdf" -o "2ASYE-T-DISPLAY-19-external-photos.pdf"
-echo "c4d77ec49971c8328323b5cc1c607980bea75a1d24933017431a7ce285a83ea7  2ASYE-T-DISPLAY-19-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-id-label-location-info.pdf b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-id-label-location-info.pdf
deleted file mode 100644
index 9c39139..0000000
Binary files a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-id-label-location-info.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-internal-photos.pdf b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-internal-photos.pdf
deleted file mode 100644
index b725d64..0000000
Binary files a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf.ARCHIVED.md
deleted file mode 100644
index b810e42..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-19-rf-exposure-info.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 146,095 B (0.14 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 146,095 B (0.14 MiB) |
-| SHA-256 | `0d98c024a6d1a029fc98c09e316d53e30b686a4f688f8732f2d329ad2a165935` |
-| FCC ID | **`2ASYE-T-DISPLAY-19`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Info |
-| FCC document id | 7190712 |
-| Upstream publication date | 2024-03-21 |
-| Grant date | 2024-03-21 |
-| Equipment class | T-Display-S3 AMOLED 1.91, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19/RF-Exposure-Info/RF-Exposure-Info-7190712.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190712>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190712.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/RF-Exposure-Info/RF-Exposure-Info-7190712.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-rf-exposure-info.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-19/RF-Exposure-Info/RF-Exposure-Info-7190712.pdf" -o "2ASYE-T-DISPLAY-19-rf-exposure-info.pdf"
-echo "0d98c024a6d1a029fc98c09e316d53e30b686a4f688f8732f2d329ad2a165935  2ASYE-T-DISPLAY-19-rf-exposure-info.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf.ARCHIVED.md
deleted file mode 100644
index bb57849..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-19-users-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,068,816 B (1.02 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,068,816 B (1.02 MiB) |
-| SHA-256 | `97096597308fdd0e2c78366f937f1d9b5506f8cb9bd765ba3a8fcf652673b40c` |
-| FCC ID | **`2ASYE-T-DISPLAY-19`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | Users Manual |
-| FCC document id | 7190708 |
-| Upstream publication date | 2024-03-21 |
-| Grant date | 2024-03-21 |
-| Equipment class | T-Display-S3 AMOLED 1.91, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19/User-Manual/Users-Manual-7190708.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7190708>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-19/7190708.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-19>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-19/User-Manual/Users-Manual-7190708.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-T-DISPLAY-19-users-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-19/User-Manual/Users-Manual-7190708.pdf" -o "2ASYE-T-DISPLAY-19-users-manual.pdf"
-echo "97096597308fdd0e2c78366f937f1d9b5506f8cb9bd765ba3a8fcf652673b40c  2ASYE-T-DISPLAY-19-users-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index ca11561..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISS3-AMOLED-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,444,723 B (1.38 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,444,723 B (1.38 MiB) |
-| SHA-256 | `ff7b49a25f654d6329c13074335d801eda8e54e90daad4b0bc17ebb40b9a3399` |
-| FCC ID | **`2ASYE-TDISS3-AMOLED`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 8123274 |
-| Upstream publication date | 2025-03-17 |
-| Grant date | 2025-03-17 |
-| Equipment class | T-Display-S3-AMOLED, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED/Test-Report/Antenna-Specification-8123274.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123274>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123274.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/Test-Report/Antenna-Specification-8123274.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISS3-AMOLED/Test-Report/Antenna-Specification-8123274.pdf" -o "2ASYE-TDISS3-AMOLED-antenna-specification.pdf"
-echo "ff7b49a25f654d6329c13074335d801eda8e54e90daad4b0bc17ebb40b9a3399  2ASYE-TDISS3-AMOLED-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-e-label.pdf b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-e-label.pdf
deleted file mode 100644
index cff82a0..0000000
Binary files a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-e-label.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index f71749d..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISS3-AMOLED-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 1,797,931 B (1.71 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,797,931 B (1.71 MiB) |
-| SHA-256 | `28026191703ef5d57ec29a752dbee1d896c3dd6dbc180a201e8d2c39c9eb7930` |
-| FCC ID | **`2ASYE-TDISS3-AMOLED`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 8123268 |
-| Upstream publication date | 2025-03-17 |
-| Grant date | 2025-03-17 |
-| Equipment class | T-Display-S3-AMOLED, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED/External-Photos/External-Photos-8123268.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123268>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123268.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/External-Photos/External-Photos-8123268.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISS3-AMOLED/External-Photos/External-Photos-8123268.pdf" -o "2ASYE-TDISS3-AMOLED-external-photos.pdf"
-echo "28026191703ef5d57ec29a752dbee1d896c3dd6dbc180a201e8d2c39c9eb7930  2ASYE-TDISS3-AMOLED-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-internal-photos.pdf b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-internal-photos.pdf
deleted file mode 100644
index e6ed41f..0000000
Binary files a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf.ARCHIVED.md
deleted file mode 100644
index e32570a..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISS3-AMOLED-rf-exposure.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 152,844 B (0.15 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 152,844 B (0.15 MiB) |
-| SHA-256 | `8c40576dcdf810a5a88a9277110802fd85e8b6e7549d75471efec77d9ebd7623` |
-| FCC ID | **`2ASYE-TDISS3-AMOLED`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure |
-| FCC document id | 8123279 |
-| Upstream publication date | 2025-03-17 |
-| Grant date | 2025-03-17 |
-| Equipment class | T-Display-S3-AMOLED, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED/RF-Exposure-Info/RF-Exposure-8123279.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123279>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123279.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/RF-Exposure-Info/RF-Exposure-8123279.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-rf-exposure.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISS3-AMOLED/RF-Exposure-Info/RF-Exposure-8123279.pdf" -o "2ASYE-TDISS3-AMOLED-rf-exposure.pdf"
-echo "8c40576dcdf810a5a88a9277110802fd85e8b6e7549d75471efec77d9ebd7623  2ASYE-TDISS3-AMOLED-rf-exposure.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index ebdfcdd..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISS3-AMOLED-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 2,753,493 B (2.63 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,753,493 B (2.63 MiB) |
-| SHA-256 | `d4106c5cc334ca45ca17c4f9b321b088d288065668defcde15e209b18d681638` |
-| FCC ID | **`2ASYE-TDISS3-AMOLED`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 8123278 |
-| Upstream publication date | 2025-03-17 |
-| Grant date | 2025-03-17 |
-| Equipment class | T-Display-S3-AMOLED, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED/User-Manual/User-Manual-8123278.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8123278>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISS3-AMOLED/8123278.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISS3-AMOLED>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISS3-AMOLED/User-Manual/User-Manual-8123278.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf" \
-   "devices/lilygo/t-display-s3-amoled/artifacts/certification/2ASYE-TDISS3-AMOLED-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISS3-AMOLED/User-Manual/User-Manual-8123278.pdf" -o "2ASYE-TDISS3-AMOLED-user-manual.pdf"
-echo "d4106c5cc334ca45ca17c4f9b321b088d288065668defcde15e209b18d681638  2ASYE-TDISS3-AMOLED-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/certification/README.md b/devices/lilygo/t-display-s3-amoled/artifacts/certification/README.md
deleted file mode 100644
index 5baeada..0000000
--- a/devices/lilygo/t-display-s3-amoled/artifacts/certification/README.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-T-DISPLAY-19`, `2ASYE-TDISS3-AMOLED`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-T-DISPLAY-19`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2024-03-21** |
-| Equipment class | T-Display-S3 AMOLED 1.91, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Source page | <https://fccid.io/2ASYE-T-DISPLAY-19> |
-| FCC ID | **`2ASYE-TDISS3-AMOLED`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2025-03-17** |
-| Equipment class | T-Display-S3-AMOLED, 2402-2480 MHz, 2412-2472 MHz |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Source page | <https://fccid.io/2ASYE-TDISS3-AMOLED> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-T-DISPLAY-19-id-label-location-info.pdf` | 546,549 | `e50584b3ca7fa52b83b40ccdaea4f97563e3bb1596e63af58636d47d25bdfca6` | ID Label/Location Info |
-| `2ASYE-T-DISPLAY-19-internal-photos.pdf` | 763,922 | `bb73f298bb8eec1000761260f9c7475008c00c82f739e4e269354d0bf3313d21` | Internal Photos |
-| `2ASYE-TDISS3-AMOLED-e-label.pdf` | 1,132,948 | `b59d8d92acbbc8f9f6b0ff8be9e6e0c0788ebab2279f88610b277dffadc6a260` | ID Label/Location Info |
-| `2ASYE-TDISS3-AMOLED-internal-photos.pdf` | 1,830,747 | `042a30c69f0e1175a47b14db052a1587de627a0e12600a41ea9dc5780c262497` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-T-DISPLAY-19-atn-test-report.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-19-atn-test-report.pdf.ARCHIVED.md) | 1,174,923 | Test Report |
-| [`2ASYE-T-DISPLAY-19-external-photos.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-19-external-photos.pdf.ARCHIVED.md) | 805,031 | External Photos |
-| [`2ASYE-T-DISPLAY-19-rf-exposure-info.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-19-rf-exposure-info.pdf.ARCHIVED.md) | 146,095 | RF Exposure Info |
-| [`2ASYE-T-DISPLAY-19-users-manual.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-19-users-manual.pdf.ARCHIVED.md) | 1,068,816 | Users Manual |
-| [`2ASYE-TDISS3-AMOLED-antenna-specification.pdf.ARCHIVED.md`](2ASYE-TDISS3-AMOLED-antenna-specification.pdf.ARCHIVED.md) | 1,444,723 | Test Report |
-| [`2ASYE-TDISS3-AMOLED-external-photos.pdf.ARCHIVED.md`](2ASYE-TDISS3-AMOLED-external-photos.pdf.ARCHIVED.md) | 1,797,931 | External Photos |
-| [`2ASYE-TDISS3-AMOLED-rf-exposure.pdf.ARCHIVED.md`](2ASYE-TDISS3-AMOLED-rf-exposure.pdf.ARCHIVED.md) | 152,844 | RF Exposure Info |
-| [`2ASYE-TDISS3-AMOLED-user-manual.pdf.ARCHIVED.md`](2ASYE-TDISS3-AMOLED-user-manual.pdf.ARCHIVED.md) | 2,753,493 | Users Manual |
-
-Archived total: **8 files, 8.91 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **4 files, 4.08 MiB** |
-| Archived | **8 files, 8.91 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/schematic/Camera-Shield.pdf b/devices/lilygo/t-display-s3-amoled/artifacts/schematic/Camera-Shield.pdf
deleted file mode 100644
index ee40a1e..0000000
Binary files a/devices/lilygo/t-display-s3-amoled/artifacts/schematic/Camera-Shield.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/schematic/T-DISPLAY-S3-AMOLED.pdf b/devices/lilygo/t-display-s3-amoled/artifacts/schematic/T-DISPLAY-S3-AMOLED.pdf
deleted file mode 100644
index 247ddde..0000000
Binary files a/devices/lilygo/t-display-s3-amoled/artifacts/schematic/T-DISPLAY-S3-AMOLED.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled/artifacts/schematic/T-Display-S3-AMOLED-Touch.pdf b/devices/lilygo/t-display-s3-amoled/artifacts/schematic/T-Display-S3-AMOLED-Touch.pdf
deleted file mode 100644
index 92d7de0..0000000
Binary files a/devices/lilygo/t-display-s3-amoled/artifacts/schematic/T-Display-S3-AMOLED-Touch.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-amoled/certification-and-compliance.md b/devices/lilygo/t-display-s3-amoled/certification-and-compliance.md
deleted file mode 100644
index 346ddef..0000000
--- a/devices/lilygo/t-display-s3-amoled/certification-and-compliance.md
+++ /dev/null
@@ -1,212 +0,0 @@
-# Certification and compliance — t-display-s3-amoled
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 2 filing(s) apply directly.
-
-Two grants plausibly apply: `2ASYE-TDISS3-AMOLED` (2025-03-17, 'T-Display-S3-AMOLED') and `2ASYE-T-DISPLAY-19` (2024-03-21, 'T-Display-S3 AMOLED 1.91'). **Which covers which store variant is not established** — see §4.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-TDISS3-AMOLED`, `2ASYE-T-DISPLAY-19` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AC7Z-ESPS3WROOM1`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-TDISS3-AMOLED`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2025-03-17** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2025-03-17 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2472 MHz** (Wi-Fi 2.4 GHz, ch 1–13 — ⚠ wider than the usual US 1–11) |
-| Test firm | Bay Area Compliance Laboratories Corp (Shenzhen) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-TDISS3-AMOLED` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 1,797,931 | `28026191703ef5d5…` |
-| `ID-Label-Location-Info-E-Label.pdf` | 1,132,948 | `b59d8d92acbbc8f9…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,830,747 | `042a30c69f0e1175…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 152,844 | `8c40576dcdf810a5…` |
-| `Test-Report-Antenna-Specification.pdf` | 1,444,723 | `ff7b49a25f654d63…` |
-| `Users-Manual-User-Manual.pdf` | 2,753,493 | `d4106c5cc334ca45…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-TDISS3-AMOLED/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-TDISS3-AMOLED/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2ASYE-T-DISPLAY-19`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-03-21** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-03-21 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 15 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY-19` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 805,031 | `c4d77ec49971c832…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info.pdf` | 546,549 | `e50584b3ca7fa52b…` |
-| `Internal-Photos-Internal-Photos.pdf` | 763,922 | `bb73f298bb8eec10…` |
-| `RF-Exposure-Info-RF-Exposure-Info.pdf` | 146,095 | `0d98c024a6d1a029…` |
-| `Test-Report-ATN-Test-Report.pdf` | 1,174,923 | `a1300af9d0563dac…` |
-| `Users-Manual-Users-Manual.pdf` | 1,068,816 | `97096597308fdd0e…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY-19/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY-19/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AC7Z-ESPS3WROOM1`
-
-| Field | Value |
-|---|---|
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD |
-| Grantee code | `2AC7Z` — registered 2014-09-15, 78 FCC IDs total |
-| Final action date | **2026-02-27** |
-| Application purpose | Class II permissive change or modification of presently authorized equipment |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 57 available, 11 metadata-only |
-| Filing page | `https://fccid.io/2AC7Z-ESPS3WROOM1` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Block diagram [Block Diagram]
-- Schematic [Schematics]
-- Schematics [Schematics]
-- Operation description [Operational Description]
-- Operational Description [Operational Description]
-- Parts list [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up procedure [Parts List/Tune Up Info]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photo.pdf` | 1,367,037 | `a0104b88a862efd5…` |
-| `External-Photos-External-Photos.pdf` | 1,275,356 | `8fe953474e9707bc…` |
-| `External-Photos-External-photos.pdf` | 332,733 | `b04d392ae5298711…` |
-| `ID-Label-Location-Info-Label-location.pdf` | 30,758 | `68e843105466c162…` |
-| `ID-Label-Location-Info-Label.pdf` | 44,224 | `081ac1c0f3292f1b…` |
-| `ID-Label-Location-Info-Lable-and-location.pdf` | 1,437,286 | `0a57b90982013049…` |
-| `Internal-Photos-Internal-Photo.pdf` | 3,636,909 | `318d8c6c95232515…` |
-| `Internal-Photos-Internal-photos.pdf` | 338,977 | `1f60246b57db6172…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 499,298 | `b1ae557e1e78bbfa…` |
-| `RF-Exposure-Info-SAR-Report-A.pdf` | 845,988 | `54f4972a02877d9b…` |
-| `RF-Exposure-Info-SAR-Report-B.pdf` | 850,218 | `62b4f82db50809aa…` |
-| `RF-Exposure-Info-SAR-Report-C1.pdf` | 5,908,102 | `8fbf6c55dc6a0248…` |
-| `RF-Exposure-Info-SAR-Report-C2.pdf` | 3,930,042 | `4c6ed64c435d4f04…` |
-| `RF-Exposure-Info-SAR-Report-D.pdf` | 3,974,985 | `04798068d0a5ee3b…` |
-| `RF-Exposure-Info-SAR-Report.pdf` | 1,936,491 | `60f7208dd54ccff8…` |
-| `Test-Report-Antenna-specification.pdf` | 1,996,381 | `da8da91adaa5b481…` |
-| `Users-Manual-User-Manual.pdf` | 2,603,588 | `3e493b8b9ea24f00…` |
-| `Users-Manual-User-manual.pdf` | 886,672 | `f8d1d246c0c849a6…` |
-
-Held at `scratch/market-and-certification/fcc/2AC7Z-ESPS3WROOM1/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AC7Z-ESPS3WROOM1/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-amoled/gaps-and-conflicts.md b/devices/lilygo/t-display-s3-amoled/gaps-and-conflicts.md
deleted file mode 100644
index 6c0fe41..0000000
--- a/devices/lilygo/t-display-s3-amoled/gaps-and-conflicts.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# T-Display-S3 AMOLED — gaps and conflicts
-
-| # | Conflict | Evidence | Status |
-|---|---|---|---|
-| A1 | **Flash size: 4 MB or 16 MB?** `T-DISPLAY-S3-AMOLED.pdf` shows `U3 = W25Q32` (4 MB); `T-Display-S3-AMOLED-Touch.pdf` shows `U3 = W25Q128JV` (16 MB); every README and store listing says 16 MB | both LilyGO schematics, retained here | **Unresolved.** Probably a stale early sheet. Settle with `esptool.py flash_id` |
-| A2 | **What differs between V1.0 and V2.0?** LilyGO sells both, states nothing | store feed 2026-09-07; schematic diff | **Unresolved.** The schematic diff (regulator, display supply, flash) is *this record's inference from two sheets that are not labelled by revision* |
-| A3 | **I²C pins.** `product_pins.h` gives SDA 3 / SCL 2; the older `pins_config.h` defines no I²C at all | `LilyGo-Display-IDF` @ `b1a1cc5` vs `T-Display-S3-AMOLED` @ `edd1333` | **Resolved in favour of `product_pins.h`** — it is newer and covers the touch variant |
-| A4 | **GPIO21 does double duty**: `PIN_BUTTON_2` in `pins_config.h` **and** `BOARD_TOUCH_IRQ` in `product_pins.h` for the Touch variant | both vendor files | **Confirmed collision.** On a Touch board, GPIO21 is the touch interrupt; treating it as a button will misfire |
-| A5 | **`AXPM65611` (`U5`) is unidentified.** No datasheet or manufacturer found | schematic text | **Open** — [`components/unidentified/lilygo-t-display-s3-family/axpm65611/`](../../../components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md) |
-| A6 | **`BV6802` (`U6`, V1.0) is unidentified.** Same family as the `BV6804` on the AMOLED Lite | schematic text | **Open** |
-| A7 | **Arduino core version.** The base board pins 2.0.14; this board's library says **"V2.0.16 or later or latest"** | two vendor READMEs | **Both correct for their own board.** Do not carry the base board's pin over |
-
-## Gaps
-
-- Net connectivity not traced (same poppler blocker as the base board).
-- **The V1.0/V2.0 schematics are not labelled by revision** — the mapping of sheet to revision
-  in the README is inferred from which repository each lives in, and from the flash part.
-- No hardware; nothing verified.
-- The Camera Shield was not researched beyond its schematic and example directory.
-
-## Negative results
-
-- **`TFT_eSPI` cannot drive this panel.** It has no QSPI transport. The vendor's "TFT_eSPI
-  examples" are Sprite-based. Recorded because the example names strongly imply otherwise.
-- **There is no GPIO15 power gate**, unlike the base board. Searched `pins_config.h`,
-  `product_pins.h` and the schematic text; no `PWR_EN`-equivalent net.
-- **No microSD on this board.** The AMOLED **Plus** has one; this one does not.
diff --git a/devices/lilygo/t-display-s3-amoled/market-and-pricing.md b/devices/lilygo/t-display-s3-amoled/market-and-pricing.md
deleted file mode 100644
index 7c1800c..0000000
--- a/devices/lilygo/t-display-s3-amoled/market-and-pricing.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Market and pricing — t-display-s3-amoled
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / Touch With Black Shell [H717] | `H717` | **USD 33.98** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / V2.0 Soldered Pin [H712] | `H712` | **USD 26.94** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / V2.0 Non-Soldered Pin [H713] | `H713` | **USD 26.44** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / V1.0 Soldered Pin [H634] | `H634` | **USD 26.94** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / V1.0 Non-Soldered Pin [H619] | `H619` | **USD 26.44** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / Touch Soldered pin [H705] | `H705` | **USD 30.44** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / Touch Non-Soldered Pin [H681] | `H681` | **USD 30.03** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | China [For Worldwide] / Only Camera Shield [H679] | `H679` | **USD 6.33** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | Canada [For CA only] / Touch With Black Shell [H717] | `H717CA` | **USD 32.00** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | United States [For US only] / V2.0 Soldered Pin [H712] | `H712-US` | **USD 30.94** | ❌ no |
-| T-Display S3 AMOLED | 2023-04-14 | United States [For US only] / V2.0 Non-Soldered Pin [H713] | `H713US` | **USD 30.94** | ❌ no |
-| T-Display S3 AMOLED | 2023-04-14 | Germany [ For Europe only] / Touch With Black Shell [H717] | `DEH717` | **USD 38.48** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | Germany [ For Europe only] / Touch Soldered pin [H705] | `DEH705` | **USD 34.94** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | United States [For US only] / Touch With Black Shell [H717] | `USH717` | **USD 38.48** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | United States [For US only] / Touch Non-Soldered Pin [H681] | `USH681` | **USD 34.63** | ✅ yes |
-| T-Display S3 AMOLED | 2023-04-14 | Germany [ For Europe only] / V2.0 Soldered Pin [H712] | `H712-DE` | **USD 33.98** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 33.98, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3-amoled`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-⚠ **16 variants.** V1.0 and V2.0 are the **same price** (USD 26.44/26.94), so the revision carries no premium. Touch adds ~USD 3.6. Camera shield alone is USD 6.33. US/DE regional SKUs run USD 4–8 higher than 'China [For Worldwide]'.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3-long/README.md b/devices/lilygo/t-display-s3-long/README.md
deleted file mode 100644
index 1476da4..0000000
--- a/devices/lilygo/t-display-s3-long/README.md
+++ /dev/null
@@ -1,127 +0,0 @@
-# LilyGO T-Display-S3 Long (3.4″ bar)
-
-> **Product:** T-Display S3 Long · store handle `t-display-s3-long` · published **2023-10-27** ·
-> SKUs `H685` basic **USD 29.35**, `H721` with shell **USD 32.13**, both in stock 2026-09-07.
->
-> **Repository default branch is `T-Display-S3-Long-cst3530`, not `main`.** That is not a typo —
-> it is how LilyGO shipped a touch-controller change. Commit **`37a7e83af79a98bb395012200f811777e52b9cfc`**.
->
-> Research retrieved **2026-09-07**. No hardware. Part of the
-> [T-Display-S3 family](../t-display-s3-shared/README.md).
-
-## Identity
-
-| | |
-|---|---|
-| Panel | 3.4″ bar, **180 × 640** |
-| Controller | **AXS15231B** — **display driver and touch controller in one die**, QSPI + I²C |
-| Manufacturer | **AXS Technology Corp.** (established from the datasheet cover, not guessed) |
-| Alternate touch | later boards add/substitute a discrete **Hynitron CST3530** — see below |
-| SoC | ESP32-S3R8, 16 MB flash, 8 MB OPI PSRAM |
-| PMIC | **Silergy SY6970** (`U6`) — a real I²C charger/PMIC, unlike the base board's dumb linear charger |
-| Backlight | **PT4103B23F** boost (`U5`) |
-| Unique feature | a **hardware slide switch** (`SW1` = `MSK12C02-HB`) — the only board in the family with a physical power switch |
-| Component records | [`axs-technology/axs15231b`](../../../components/axs-technology/axs15231b/README.md) · [`hynitron/cst3530`](../../../components/hynitron/cst3530/README.md) · [`silergy/sy6970`](../../../components/silergy/sy6970/README.md) · [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) |
-
-## Why this board is interesting
-
-**One die drives the panel and reads the touch.** The AXS15231B takes pixels over QSPI and
-answers touch queries over I²C at address **`0x3B`** — a command-framed protocol rather than a
-conventional register map. LilyGO ships a dedicated note for it:
-`examples/GFX_AXS15231B_Image/T-Display-S3-Long_AXS15231B_Touch_Register.pdf`
-(63 044 B, "Modified on: 2024.07.19"), which describes the sequence as:
-
-> "Initialize touch IIC: IIC device `0x3B`, touch reset, set external interrupt. … Write the
-> command to read touch information: continuously write the following formatted command data to
-> the touch IIC address `0x3B`. … Take touching the fingers to count 1 and event `0x08` together
-> as the trigger flag."
-
-That last sentence is the operative one and is easy to miss: **a valid touch requires both the
-finger count and event code `0x08`**, not either alone.
-
-## Pinout
-
-From `examples/factory/pins_config.h` @ `37a7e83`:
-
-| Signal | GPIO |
-|---|---|
-| `TFT_QSPI_CS` / `SCK` | 12 / 17 |
-| `TFT_QSPI_D0..D3` | 13, 18, 21, 14 |
-| `TFT_QSPI_RST` | 16 |
-| `TFT_BL` | 1 |
-| `TP_RST` / `TP_IRQ` | 2 / 11 |
-| `I2C_SDA` / `I2C_SCL` | 15 / 10 |
-| `SPI_SD_CS/MOSI/MISO/SCLK` | 38 / 39 / 41 / 40 |
-| `PIN_BUTTON_1` | 0 |
-
-SPI clock **32 MHz**; `SEND_BUF_SIZE 28800/2` (RGB565).
-
-### Two defects in that file — do not copy it blindly
-
-```c
-#define TFT_QSPI_D2   21     …   #define PIN_BUTTON_2   21     ← collision
-#define TP_RST         2     …   #define PIN_BAT_VOLT    2     ← collision
-```
-
-Both are copy-paste residue from the AMOLED board's header (where `PIN_BUTTON_2 21` and
-`PIN_BAT_VOLT 4` are correct). **`PIN_BUTTON_2` and `PIN_BAT_VOLT` are wrong for this board and
-must not be used.** GPIO21 is a display data line; GPIO2 is the touch reset.
-
-Battery voltage on this board is read **from the SY6970 over I²C**, not from an ADC — which is
-why no correct `PIN_BAT_VOLT` exists. That is an upgrade over the base board: a real
-fuel-gauge-adjacent path with charge status, input current limit and OTG control.
-
-## The CST3530 branch
-
-The repository's **default branch is `T-Display-S3-Long-cst3530`** and it ships **two factory
-images**:
-
-| Image | Bytes |
-|---|---|
-| `firmware/factory.bin` | 1 815 872 |
-| `firmware/factory-cst3530.bin` | 2 158 624 |
-
-plus `examples/cst3530_touch/` beside the original AXS15231B touch path, and a
-`CST3530数据手册V1.0` datasheet. **Reading:** later production substitutes or adds a discrete
-Hynitron CST3530 touch controller. LilyGO handled it by making that branch the default rather
-than merging. **How to tell:** flash `factory.bin`; if touch does not respond, flash
-`factory-cst3530.bin`. See
-[revision R5](../t-display-s3-shared/board-revision-drift.md#r5--t-display-s3-long-cst3530-touch-appears-mid-life-in-a-branch).
-
-## Software
-
-| Route | Status |
-|---|---|
-| **`Arduino_GFX`** | LilyGO's own choice; the repo vendors `Arduino_GFX-1.3.7` |
-| `TFT_eSPI` | **cannot drive it** — QSPI |
-| ESPHome | **no model for this board** in `mipi_spi` as of 2026-09-07. AMOLED, base and Pro have models; Long does not |
-| LVGL | `examples/lvgl_demo` |
-
-## Power and current
-
-LilyGO's own table @ `37a7e83`: **90–350+ mA** active at 240 MHz with Wi-Fi (notably higher than
-the AMOLED boards' 230 mA ceiling — the bar panel and its boost backlight cost real power), and
-**≈1.1 mA** deep sleep with GPIO wake. That 1.1 mA is **five times** the AMOLED boards' 230 µA;
-this is not a good board for a long-running battery device.
-
-## Two schematics
-
-`T-Display-S3-Long-3.4-V1.0.pdf` (330 477 B, `7ca6e7037f67c844…`) and
-`T-Display-S3-Long-3.4-with-SD-slot.pdf` (341 862 B, `157ef432daaefb8f…`). **The SD-slot version
-is a second board variant**, and the SPI SD pins in `pins_config.h` (GPIO38–41) belong to it.
-Whether the `H685`/`H721` SKUs ship with or without the slot is **not established** — the store
-does not say.
-
-## Artifacts
-
-Both schematics retained under `artifacts/schematic/`, retrieved 2026-09-07 at `37a7e83`.
-The **AXS15231B datasheet (8.8 MB, V0.4, 2022-11-08)** and its touch-register note are filed
-under [`components/axs-technology/axs15231b/artifacts/`](../../../components/axs-technology/axs15231b/artifacts/);
-CST3530 under [`components/hynitron/cst3530/artifacts/`](../../../components/hynitron/cst3530/artifacts/);
-SY6970 under [`components/silergy/sy6970/artifacts/`](../../../components/silergy/sy6970/artifacts/).
-
-## Gaps and conflicts
-
-See [`gaps-and-conflicts.md`](gaps-and-conflicts.md). The repo has **25 open issues**, the most
-of any board in the family — proportionally far more than the base board's 1 open of 318 — which
-is itself a signal about maturity.
diff --git a/devices/lilygo/t-display-s3-long/acquisition/manifest.json b/devices/lilygo/t-display-s3-long/acquisition/manifest.json
deleted file mode 100644
index 978d365..0000000
--- a/devices/lilygo/t-display-s3-long/acquisition/manifest.json
+++ /dev/null
@@ -1,260 +0,0 @@
-{
- "record": "devices/lilygo/t-display-s3-long",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2ASYE-TDISPLAY-LONG-7134147",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISPLAY-LONG/Test-Report/Antenna-Specification-7134147.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134147",
-    "https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134147.pdf",
-    "https://fccid.io/2ASYE-TDISPLAY-LONG",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/Test-Report/Antenna-Specification-7134147.pdf"
-   ],
-   "sha256": "a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62",
-   "bytes": 1174923,
-   "destination": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-23",
-   "fcc_id": "2ASYE-TDISPLAY-LONG",
-   "fcc_document_id": "7134147",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Specification",
-   "grant_date": "2024-02-23",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-long",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISPLAY-LONG-7134138",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISPLAY-LONG/External-Photos/External-Photos-7134138.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134138",
-    "https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134138.pdf",
-    "https://fccid.io/2ASYE-TDISPLAY-LONG",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/External-Photos/External-Photos-7134138.pdf"
-   ],
-   "sha256": "e80c1246ae6b9101d292e96c61c8d0e71a4b6bd995fb5c49f01cf226cc147ac6",
-   "bytes": 722944,
-   "destination": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-23",
-   "fcc_id": "2ASYE-TDISPLAY-LONG",
-   "fcc_document_id": "7134138",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2024-02-23",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-long",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISPLAY-LONG-7134139",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISPLAY-LONG/Internal-Photos/Internal-Photos-7134139.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134139",
-    "https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134139.pdf",
-    "https://fccid.io/2ASYE-TDISPLAY-LONG",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/Internal-Photos/Internal-Photos-7134139.pdf"
-   ],
-   "sha256": "6655935bdc86a8eebf91ddafeea7ba2b9685a5b2aedd246f36246fde1a7a0e2f",
-   "bytes": 1074668,
-   "destination": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-23",
-   "fcc_id": "2ASYE-TDISPLAY-LONG",
-   "fcc_document_id": "7134139",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2024-02-23",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-long",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISPLAY-LONG-7134145",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISPLAY-LONG/Label/Label-Label-Location-7134145.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134145",
-    "https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134145.pdf",
-    "https://fccid.io/2ASYE-TDISPLAY-LONG",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/Label/Label-Label-Location-7134145.pdf"
-   ],
-   "sha256": "973a0b07e1fc10c9179665f73d9b8e009f3b331b013fb9ed3b0bb49eaa5947ec",
-   "bytes": 452588,
-   "destination": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-label-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-23",
-   "fcc_id": "2ASYE-TDISPLAY-LONG",
-   "fcc_document_id": "7134145",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label & Label Location",
-   "grant_date": "2024-02-23",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-long",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISPLAY-LONG-7134150",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-BLE-7134150.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134150",
-    "https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134150.pdf",
-    "https://fccid.io/2ASYE-TDISPLAY-LONG",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-BLE-7134150.pdf"
-   ],
-   "sha256": "6af1e686fa63f85bd4e469d66e8116e42cce5f4044e39cacac652dc690b95054",
-   "bytes": 169460,
-   "destination": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-23",
-   "fcc_id": "2ASYE-TDISPLAY-LONG",
-   "fcc_document_id": "7134150",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure - BLE",
-   "grant_date": "2024-02-23",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-long",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISPLAY-LONG-7134151",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-Wi-Fi-7134151.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134151",
-    "https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134151.pdf",
-    "https://fccid.io/2ASYE-TDISPLAY-LONG",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-Wi-Fi-7134151.pdf"
-   ],
-   "sha256": "9239093c56bccf475349bf7bfcbfa7456369fc796e29297868d0a7d83037c7db",
-   "bytes": 146111,
-   "destination": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-23",
-   "fcc_id": "2ASYE-TDISPLAY-LONG",
-   "fcc_document_id": "7134151",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure - Wi-Fi",
-   "grant_date": "2024-02-23",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-long",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-TDISPLAY-LONG-7134146",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-TDISPLAY-LONG/User-Manual/User-Manual-7134146.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134146",
-    "https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134146.pdf",
-    "https://fccid.io/2ASYE-TDISPLAY-LONG",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/User-Manual/User-Manual-7134146.pdf"
-   ],
-   "sha256": "a3d949a545df696e9f8572d974428b90e0579ad7cfe9fa1ac4109a86de1dad7f",
-   "bytes": 1187373,
-   "destination": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-23",
-   "fcc_id": "2ASYE-TDISPLAY-LONG",
-   "fcc_document_id": "7134146",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2024-02-23",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-long",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 93a407f..0000000
--- a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISPLAY-LONG-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,174,923 B (1.12 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,174,923 B (1.12 MiB) |
-| SHA-256 | `a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62` |
-| FCC ID | **`2ASYE-TDISPLAY-LONG`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 7134147 |
-| Upstream publication date | 2024-02-23 |
-| Grant date | 2024-02-23 |
-| Equipment class | T-Display-S3-Long, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG/Test-Report/Antenna-Specification-7134147.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134147>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134147.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/Test-Report/Antenna-Specification-7134147.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf" \
-   "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISPLAY-LONG/Test-Report/Antenna-Specification-7134147.pdf" -o "2ASYE-TDISPLAY-LONG-antenna-specification.pdf"
-echo "a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62  2ASYE-TDISPLAY-LONG-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 7bdb4db..0000000
--- a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISPLAY-LONG-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 722,944 B (0.69 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 722,944 B (0.69 MiB) |
-| SHA-256 | `e80c1246ae6b9101d292e96c61c8d0e71a4b6bd995fb5c49f01cf226cc147ac6` |
-| FCC ID | **`2ASYE-TDISPLAY-LONG`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 7134138 |
-| Upstream publication date | 2024-02-23 |
-| Grant date | 2024-02-23 |
-| Equipment class | T-Display-S3-Long, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG/External-Photos/External-Photos-7134138.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134138>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134138.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/External-Photos/External-Photos-7134138.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf" \
-   "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISPLAY-LONG/External-Photos/External-Photos-7134138.pdf" -o "2ASYE-TDISPLAY-LONG-external-photos.pdf"
-echo "e80c1246ae6b9101d292e96c61c8d0e71a4b6bd995fb5c49f01cf226cc147ac6  2ASYE-TDISPLAY-LONG-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-internal-photos.pdf b/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-internal-photos.pdf
deleted file mode 100644
index dd33887..0000000
Binary files a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-label-label-location.pdf b/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-label-label-location.pdf
deleted file mode 100644
index ee736e6..0000000
Binary files a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-label-label-location.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf.ARCHIVED.md
deleted file mode 100644
index c6fe5e9..0000000
--- a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 169,460 B (0.16 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 169,460 B (0.16 MiB) |
-| SHA-256 | `6af1e686fa63f85bd4e469d66e8116e42cce5f4044e39cacac652dc690b95054` |
-| FCC ID | **`2ASYE-TDISPLAY-LONG`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure - BLE |
-| FCC document id | 7134150 |
-| Upstream publication date | 2024-02-23 |
-| Grant date | 2024-02-23 |
-| Equipment class | T-Display-S3-Long, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-BLE-7134150.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134150>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134150.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-BLE-7134150.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf" \
-   "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-BLE-7134150.pdf" -o "2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf"
-echo "6af1e686fa63f85bd4e469d66e8116e42cce5f4044e39cacac652dc690b95054  2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf.ARCHIVED.md
deleted file mode 100644
index 2ac0266..0000000
--- a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 146,111 B (0.14 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 146,111 B (0.14 MiB) |
-| SHA-256 | `9239093c56bccf475349bf7bfcbfa7456369fc796e29297868d0a7d83037c7db` |
-| FCC ID | **`2ASYE-TDISPLAY-LONG`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure - Wi-Fi |
-| FCC document id | 7134151 |
-| Upstream publication date | 2024-02-23 |
-| Grant date | 2024-02-23 |
-| Equipment class | T-Display-S3-Long, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-Wi-Fi-7134151.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134151>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134151.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-Wi-Fi-7134151.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf" \
-   "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISPLAY-LONG/RF-Exposure-Info/RF-Exposure-Wi-Fi-7134151.pdf" -o "2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf"
-echo "9239093c56bccf475349bf7bfcbfa7456369fc796e29297868d0a7d83037c7db  2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index b687282..0000000
--- a/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-TDISPLAY-LONG-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,187,373 B (1.13 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,187,373 B (1.13 MiB) |
-| SHA-256 | `a3d949a545df696e9f8572d974428b90e0579ad7cfe9fa1ac4109a86de1dad7f` |
-| FCC ID | **`2ASYE-TDISPLAY-LONG`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 7134146 |
-| Upstream publication date | 2024-02-23 |
-| Grant date | 2024-02-23 |
-| Equipment class | T-Display-S3-Long, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG/User-Manual/User-Manual-7134146.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7134146>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-TDISPLAY-LONG/7134146.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-TDISPLAY-LONG>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-TDISPLAY-LONG/User-Manual/User-Manual-7134146.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf" \
-   "devices/lilygo/t-display-s3-long/artifacts/certification/2ASYE-TDISPLAY-LONG-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-TDISPLAY-LONG/User-Manual/User-Manual-7134146.pdf" -o "2ASYE-TDISPLAY-LONG-user-manual.pdf"
-echo "a3d949a545df696e9f8572d974428b90e0579ad7cfe9fa1ac4109a86de1dad7f  2ASYE-TDISPLAY-LONG-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-long/artifacts/certification/README.md b/devices/lilygo/t-display-s3-long/artifacts/certification/README.md
deleted file mode 100644
index cbf9015..0000000
--- a/devices/lilygo/t-display-s3-long/artifacts/certification/README.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-TDISPLAY-LONG`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-TDISPLAY-LONG`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2024-02-23** |
-| Equipment class | T-Display-S3-Long, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Source page | <https://fccid.io/2ASYE-TDISPLAY-LONG> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-TDISPLAY-LONG-internal-photos.pdf` | 1,074,668 | `6655935bdc86a8eebf91ddafeea7ba2b9685a5b2aedd246f36246fde1a7a0e2f` | Internal Photos |
-| `2ASYE-TDISPLAY-LONG-label-label-location.pdf` | 452,588 | `973a0b07e1fc10c9179665f73d9b8e009f3b331b013fb9ed3b0bb49eaa5947ec` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-TDISPLAY-LONG-antenna-specification.pdf.ARCHIVED.md`](2ASYE-TDISPLAY-LONG-antenna-specification.pdf.ARCHIVED.md) | 1,174,923 | Test Report |
-| [`2ASYE-TDISPLAY-LONG-external-photos.pdf.ARCHIVED.md`](2ASYE-TDISPLAY-LONG-external-photos.pdf.ARCHIVED.md) | 722,944 | External Photos |
-| [`2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf.ARCHIVED.md`](2ASYE-TDISPLAY-LONG-rf-exposure-ble.pdf.ARCHIVED.md) | 169,460 | RF Exposure Info |
-| [`2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf.ARCHIVED.md`](2ASYE-TDISPLAY-LONG-rf-exposure-wi-fi.pdf.ARCHIVED.md) | 146,111 | RF Exposure Info |
-| [`2ASYE-TDISPLAY-LONG-user-manual.pdf.ARCHIVED.md`](2ASYE-TDISPLAY-LONG-user-manual.pdf.ARCHIVED.md) | 1,187,373 | Users Manual |
-
-Archived total: **5 files, 3.24 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 1.46 MiB** |
-| Archived | **5 files, 3.24 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t-display-s3-long/artifacts/schematic/T-Display-S3-Long-3.4-V1.0.pdf b/devices/lilygo/t-display-s3-long/artifacts/schematic/T-Display-S3-Long-3.4-V1.0.pdf
deleted file mode 100644
index 51b7eb2..0000000
Binary files a/devices/lilygo/t-display-s3-long/artifacts/schematic/T-Display-S3-Long-3.4-V1.0.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-long/artifacts/schematic/T-Display-S3-Long-3.4-with-SD-slot.pdf b/devices/lilygo/t-display-s3-long/artifacts/schematic/T-Display-S3-Long-3.4-with-SD-slot.pdf
deleted file mode 100644
index 359e7e9..0000000
Binary files a/devices/lilygo/t-display-s3-long/artifacts/schematic/T-Display-S3-Long-3.4-with-SD-slot.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-long/certification-and-compliance.md b/devices/lilygo/t-display-s3-long/certification-and-compliance.md
deleted file mode 100644
index 846660f..0000000
--- a/devices/lilygo/t-display-s3-long/certification-and-compliance.md
+++ /dev/null
@@ -1,178 +0,0 @@
-# Certification and compliance — t-display-s3-long
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-TDISPLAY-LONG` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AC7Z-ESPS3WROOM1`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-TDISPLAY-LONG`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2412-2462 MHz Original Equipment 2024-02-23** |
-| Application purpose | Final Action Date 2412-2462 MHz Original Equipment 2024-02-23 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-TDISPLAY-LONG` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Circuit Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 722,944 | `e80c1246ae6b9101…` |
-| `ID-Label-Location-Info-Label-Label-Location.pdf` | 452,588 | `973a0b07e1fc10c9…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,074,668 | `6655935bdc86a8ee…` |
-| `RF-Exposure-Info-RF-Exposure---BLE.pdf` | 169,460 | `6af1e686fa63f85b…` |
-| `RF-Exposure-Info-RF-Exposure---Wi-Fi.pdf` | 146,111 | `9239093c56bccf47…` |
-| `Test-Report-Antenna-Specification.pdf` | 1,174,923 | `a1300af9d0563dac…` |
-| `Users-Manual-User-Manual.pdf` | 1,187,373 | `a3d949a545df696e…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-TDISPLAY-LONG/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-TDISPLAY-LONG/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AC7Z-ESPS3WROOM1`
-
-| Field | Value |
-|---|---|
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD |
-| Grantee code | `2AC7Z` — registered 2014-09-15, 78 FCC IDs total |
-| Final action date | **2026-02-27** |
-| Application purpose | Class II permissive change or modification of presently authorized equipment |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 57 available, 11 metadata-only |
-| Filing page | `https://fccid.io/2AC7Z-ESPS3WROOM1` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Block diagram [Block Diagram]
-- Schematic [Schematics]
-- Schematics [Schematics]
-- Operation description [Operational Description]
-- Operational Description [Operational Description]
-- Parts list [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up procedure [Parts List/Tune Up Info]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photo.pdf` | 1,367,037 | `a0104b88a862efd5…` |
-| `External-Photos-External-Photos.pdf` | 1,275,356 | `8fe953474e9707bc…` |
-| `External-Photos-External-photos.pdf` | 332,733 | `b04d392ae5298711…` |
-| `ID-Label-Location-Info-Label-location.pdf` | 30,758 | `68e843105466c162…` |
-| `ID-Label-Location-Info-Label.pdf` | 44,224 | `081ac1c0f3292f1b…` |
-| `ID-Label-Location-Info-Lable-and-location.pdf` | 1,437,286 | `0a57b90982013049…` |
-| `Internal-Photos-Internal-Photo.pdf` | 3,636,909 | `318d8c6c95232515…` |
-| `Internal-Photos-Internal-photos.pdf` | 338,977 | `1f60246b57db6172…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 499,298 | `b1ae557e1e78bbfa…` |
-| `RF-Exposure-Info-SAR-Report-A.pdf` | 845,988 | `54f4972a02877d9b…` |
-| `RF-Exposure-Info-SAR-Report-B.pdf` | 850,218 | `62b4f82db50809aa…` |
-| `RF-Exposure-Info-SAR-Report-C1.pdf` | 5,908,102 | `8fbf6c55dc6a0248…` |
-| `RF-Exposure-Info-SAR-Report-C2.pdf` | 3,930,042 | `4c6ed64c435d4f04…` |
-| `RF-Exposure-Info-SAR-Report-D.pdf` | 3,974,985 | `04798068d0a5ee3b…` |
-| `RF-Exposure-Info-SAR-Report.pdf` | 1,936,491 | `60f7208dd54ccff8…` |
-| `Test-Report-Antenna-specification.pdf` | 1,996,381 | `da8da91adaa5b481…` |
-| `Users-Manual-User-Manual.pdf` | 2,603,588 | `3e493b8b9ea24f00…` |
-| `Users-Manual-User-manual.pdf` | 886,672 | `f8d1d246c0c849a6…` |
-
-Held at `scratch/market-and-certification/fcc/2AC7Z-ESPS3WROOM1/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AC7Z-ESPS3WROOM1/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-long/gaps-and-conflicts.md b/devices/lilygo/t-display-s3-long/gaps-and-conflicts.md
deleted file mode 100644
index 59b4c5c..0000000
--- a/devices/lilygo/t-display-s3-long/gaps-and-conflicts.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# T-Display-S3 Long — gaps and conflicts
-
-| # | Item | Evidence | Status |
-|---|---|---|---|
-| L1 | **`pins_config.h` contradicts itself twice.** `TFT_QSPI_D2 21` vs `PIN_BUTTON_2 21`; `TP_RST 2` vs `PIN_BAT_VOLT 2` | `examples/factory/pins_config.h` @ `37a7e83`, single file | **Confirmed defect.** Copy-paste residue from the AMOLED header. Neither `PIN_BUTTON_2` nor `PIN_BAT_VOLT` is valid on this board |
-| L2 | **Which touch controller does a given board have?** Default branch is `…-cst3530`; two factory images ship; the AXS15231B has integrated touch | branch name, `firmware/factory.bin` vs `factory-cst3530.bin`, `examples/cst3530_touch/` | **Unresolved by documentation.** Resolve empirically: flash each factory image |
-| L3 | **With or without SD slot?** Two schematics exist; the store lists no SD option | `T-Display-S3-Long-3.4-V1.0.pdf` vs `…-with-SD-slot.pdf` | **Unresolved.** The SPI SD pins in `pins_config.h` (38/39/40/41) presuppose the slot |
-| L4 | **Repo has no LICENSE.** `gh api repos/…` reports `license: none` | GitHub API 2026-09-07 | Redistribution status of the schematics and firmware here is **unknown**, unlike the MIT base-board repo |
-| L5 | **Battery voltage** has no ADC path; must be read from the SY6970 over I²C | absence of a valid `PIN_BAT_VOLT`; SY6970 present | **Inferred**, consistent, but no vendor example named `SY6970` exists in *this* repo (the 1.64″ repo has one) |
-| L6 | **No ESPHome support.** `mipi_spi` has models for T-DISPLAY-S3, -PRO, -AMOLED, -AMOLED-PLUS and T4-S3, but none for the Long | `esphome/components/mipi_spi/models/*.py`, `dev` @ 2026-09-07 | **Negative result** |
-| L7 | **25 open issues**, the most of any board in the family | GitHub API | Not a defect per se; a maturity signal worth stating |
-
-## Gaps
-
-- No hardware; nothing verified.
-- Schematic net connectivity not traced.
-- The AXS15231B touch protocol is described only by a 2-page vendor note; the full command set
-  is not documented anywhere located.
-- Which SKU (`H685` / `H721`) corresponds to which schematic is unknown.
diff --git a/devices/lilygo/t-display-s3-long/market-and-pricing.md b/devices/lilygo/t-display-s3-long/market-and-pricing.md
deleted file mode 100644
index 111e09e..0000000
--- a/devices/lilygo/t-display-s3-long/market-and-pricing.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Market and pricing — t-display-s3-long
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 Long | 2023-10-27 | With Shell [H721] | `H721` | **USD 32.13** | ✅ yes |
-| T-Display S3 Long | 2023-10-27 | Basic [H685] | `H685` | **USD 29.35** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 32.13, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3-long`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-Basic USD 29.35, with shell USD 32.13 — a USD 2.78 shell premium.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3-pro-mvsrboard/README.md b/devices/lilygo/t-display-s3-pro-mvsrboard/README.md
deleted file mode 100644
index 47dc7c2..0000000
--- a/devices/lilygo/t-display-s3-pro-mvsrboard/README.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# LilyGO T-Display-S3 Pro MVSRBoard
-
-> **Stub record.** An accessory backplate for the
-> [T-Display-S3 Pro](../t-display-s3-pro/README.md), not a standalone board.
-> Store SKU `H751` "Only MVSR Board" **USD 10.20**; bundled with a mainboard as `K255`/`K255-01`
-> at **USD 42.33**. In stock 2026-09-07.
-> Repo `T-Display-S3-Pro-MVSRBoard` @ **`c9c1a76b263ee1696c9aefcd283086751bb9bf73`**,
-> licence **GPL-3.0**. Research retrieved 2026-09-07. No hardware.
-
-## What it is
-
-LilyGO's own description, verbatim from the repository metadata:
-
-> "The T-Display-S3-Pro-MVSRBoard is the backplate design for the T-Display-S3-Pro motherboard,
-> featuring onboard speaker and microphone expansion with extremely low static current.
-> Additionally, it includes vibration and RTC (Real-Time Clock) functions."
-
-**MVSR** = **M**icrophone · **V**ibration · **S**peaker · **R**TC.
-
-## Fitted parts
-
-Read from the datasheets and schematics the Pro repository ships for it. **This is inference
-from co-located documents, not from a traced schematic of the MVSRBoard itself.**
-
-| Function | Part | Component record |
-|---|---|---|
-| Speaker amplifier | **MAX98357A** (I²S class-D) | [`analog-devices/max98357a`](../../../components/analog-devices/max98357a/README.md) |
-| Microphone | **MEMSensing MSM261S4030H0R** (PDM) | [`memsensing/msm261s4030h0r`](../../../components/memsensing/msm261s4030h0r/README.md) |
-| RTC | **NXP PCF85063ATL** | [`nxp/pcf85063a`](../../../components/nxp/pcf85063a/README.md) |
-| Vibration | motor, part unidentified | [`generic/lra-motor`](../../../components/generic/lra-motor/README.md) *(family record)* |
-
-## Sibling
-
-**`T-Display-S3-Pro-MVSRLora`** — the same backplate **plus LoRa**, repo
-`T-Display-S3-Pro-MVSRLora` @ `3457ffc0f9569858891d3692ce52f800947bd0c4`, GPL-3.0.
-Not researched by this pass beyond its existence and description. Note that this, and the
-separately sold **T-Display S3 Pro LR1121** (USD 65.29), are the only routes to LoRa anywhere
-in the T-Display-S3 family — relevant to anyone who arrived here looking for Meshtastic.
-
-## Artifacts
-
-`artifacts/schematic/T-Display-S3-Pro-MVSRBoard_V1.0_20241109.pdf` — 1 184 978 B,
-SHA-256 `5dda2c17f5e4c3ffe305b32b284380ca58d23670b45ced1b3b234107d9b31f09`, retrieved 2026-09-07
-from the **Pro** repository at `08b8b2b`.
-
-**An earlier sheet exists**, `T-Display-S3-Pro-MVSRBoard_V1.0_20240913.pdf` (1 173 823 B) — same
-declared version `V1.0`, different date and different size. **Two documents, one version
-number.** Not retrieved; recorded because the pair is itself evidence of the revision culture
-described in [`../t-display-s3-shared/board-revision-drift.md`](../t-display-s3-shared/board-revision-drift.md).
-
-## Gaps
-
-**This is a stub.** Missing: a traced parts census from the MVSRBoard's own schematic, the pin
-assignments (I²S clock/data, PDM, motor, RTC interrupt), the example catalogue, and any
-verification that the parts above are the ones actually fitted rather than merely documented
-alongside. The 2024-09-13 sheet was not retrieved and the two `V1.0` sheets were not diffed.
-No hardware.
diff --git a/devices/lilygo/t-display-s3-pro-mvsrboard/artifacts/schematic/T-Display-S3-Pro-MVSRBoard_V1.0_20241109.pdf b/devices/lilygo/t-display-s3-pro-mvsrboard/artifacts/schematic/T-Display-S3-Pro-MVSRBoard_V1.0_20241109.pdf
deleted file mode 100644
index fb6b5e5..0000000
Binary files a/devices/lilygo/t-display-s3-pro-mvsrboard/artifacts/schematic/T-Display-S3-Pro-MVSRBoard_V1.0_20241109.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-pro-mvsrboard/certification-and-compliance.md b/devices/lilygo/t-display-s3-pro-mvsrboard/certification-and-compliance.md
deleted file mode 100644
index c7a9819..0000000
--- a/devices/lilygo/t-display-s3-pro-mvsrboard/certification-and-compliance.md
+++ /dev/null
@@ -1,129 +0,0 @@
-# Certification and compliance — t-display-s3-pro-mvsrboard
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-An add-on board for the T-Display-S3 Pro; no independent grant, and none expected.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2ASYE-T-DISPLAY-PRO`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-DISPLAY-PRO`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-03-27** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-03-27 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 20 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY-PRO` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos-1.pdf` | 5,534,909 | `cf8db3e26ae5a115…` |
-| `External-Photos-External-Photos-2.pdf` | 5,737,973 | `ca357899424b5787…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info-1.pdf` | 309,287 | `44c20ebf6a73ad6b…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info-2.pdf` | 227,798 | `76d12dffc2889435…` |
-| `Internal-Photos-Internal-Photos.pdf` | 4,541,201 | `9624956bf203111d…` |
-| `RF-Exposure-Info-RF-Exposure-Info-1.pdf` | 100,255 | `63235ef32237eae4…` |
-| `RF-Exposure-Info-RF-Exposure-Info-2.pdf` | 100,231 | `621b801a871d4d99…` |
-| `Test-Report-ANT-Test-Report.pdf` | 1,177,730 | `635fa5a26234c5ba…` |
-| `Users-Manual-Users-Manual.pdf` | 938,620 | `1e4c731fadac5111…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY-PRO/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY-PRO/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-pro-mvsrboard/market-and-pricing.md b/devices/lilygo/t-display-s3-pro-mvsrboard/market-and-pricing.md
deleted file mode 100644
index 1c5580a..0000000
--- a/devices/lilygo/t-display-s3-pro-mvsrboard/market-and-pricing.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# Market and pricing — t-display-s3-pro-mvsrboard
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / White | `K239` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / White with Orange | `K240` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / Black | `K241` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / Orange | `K242` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / White | `K232` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / White with Orange | `K235` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / Black | `K236` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / Orange | `K238` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / White | `K231` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / White with Orange | `K233` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / Black | `K234` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / Orange | `K237` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Only Black Lens Cover / Only Black Lens Cover | `H688` | **USD 6.02** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Only MVSR Board / Only MVSR Board | `H751` | **USD 10.20** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Black Mainboard With MVSR Board / Black Mainboard With MVSR Board | `K255` | **USD 42.33** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / White Mainboard With MVSR Board / White Mainboard With MVSR Board | `K255-01` | **USD 42.33** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | Germany [ For Europe only] / With GC0308 Camera / White | `K239DE` | **USD 48.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | Germany [ For Europe only] / Without Camera / White | `K231DE` | **USD 41.72** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 46.54, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3-pro`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-Within the `t-display-s3-pro` handle: `H751` **MVSR board alone** USD 10.20; `K255`/`K255-01` mainboard **with** MVSR board USD 42.33.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3-pro/README.md b/devices/lilygo/t-display-s3-pro/README.md
deleted file mode 100644
index a440fc9..0000000
--- a/devices/lilygo/t-display-s3-pro/README.md
+++ /dev/null
@@ -1,140 +0,0 @@
-# LilyGO T-Display-S3 Pro (2.33″)
-
-> **Product:** T-Display S3 Pro · store handle `t-display-s3-pro` · published **2023-09-07** ·
-> **18 SKUs**: no camera **USD 37.99**, GC0308 camera **46.54**, OV5640 camera **56.99**, four
-> shell colours, plus MVSR-board bundles. All in stock 2026-09-07.
-> Repo `T-Display-S3-Pro` @ **`08b8b2bbcb8b263131af119476403080cd30224f`**.
->
-> Research retrieved **2026-09-07**. No hardware. Part of the
-> [T-Display-S3 family](../t-display-s3-shared/README.md).
-
-## Identity
-
-| | |
-|---|---|
-| Panel | 2.33″, **222 × 480** (README also writes it 480 × 222) |
-| Controller | **Sitronix ST7796** on **4-wire SPI** — *not* parallel, *not* QSPI. **Naming conflict**: the README says **ST7796U**, the repo ships **`ST7796S-Sitronix.pdf`** |
-| Touch | **Hynitron CST226SE**, I²C **`0x5A`** |
-| PMIC | **Silergy SY6970**, I²C **`0x6A`** — charging, OTG, ADC, input-current limit |
-| Ambient light | **Lite-On LTR-553ALS**, I²C **`0x23`** |
-| IMU | **BHI260AP** *or* an ICM-209xx-class part — **two schematics ship** |
-| Storage | microSD on the shared SPI bus, `CS` GPIO14 |
-| Buttons | **three**: GPIO0, GPIO12, GPIO16 |
-| Extras | vibration motor GPIO16, camera FPC, a hardware power switch |
-| Component records | [`sitronix/st7796s`](../../../components/sitronix/st7796s/README.md) · [`hynitron/cst226se`](../../../components/hynitron/cst226se/README.md) · [`silergy/sy6970`](../../../components/silergy/sy6970/README.md) · [`lite-on/ltr-553als-01`](../../../components/lite-on/ltr-553als-01/README.md) · [`bosch-sensortec/bhi260ap`](../../../components/bosch-sensortec/bhi260ap/README.md) |
-
-This is the most complete board in the family — the only one that is close to being a product
-rather than a module. It is also the one with the most revision ambiguity.
-
-## Pinout
-
-From `examples/factory/utilities.h` @ `08b8b2b`, verbatim in structure:
-
-```c
-// LTR553 , TOUCH , SY6970 , Camera share I2C Bus
-#define BOARD_I2C_SDA       5
-#define BOARD_I2C_SCL       6
-#define VIBRATING_MOTOR    16
-// SD , TFT share SPI Bus
-#define BOARD_SPI_MISO      8
-#define BOARD_SPI_MOSI     17
-#define BOARD_SPI_SCK      18
-#define BOARD_TFT_CS       39
-#define BOARD_TFT_RST      47
-#define BOARD_TFT_DC        9
-#define BOARD_TFT_BL       48
-#define BOARD_SD_CS        14
-#define BOARD_SENSOR_IRQ   21
-#define BOARD_TOUCH_RST    13
-#define BOARD_TFT_WIDTH   222
-#define BOARD_TFT_HEIHT   480      // sic
-#define BOARD_USER_BUTTON  {0, 12, 16}
-#define BOARD_USER_BTN_NUM 3
-```
-
-**`VIBRATING_MOTOR` and the third user button are both GPIO16.** That is in LilyGO's own file
-and is not obviously an error — a haptic driven by the same pin as a button read would be —
-but it is worth verifying before using either. `product_pins.h` @ `b1a1cc5` gives
-`BOARD_TOUCH_IRQ 7`, which `utilities.h` does not define at all.
-
-Camera pins are in the same file (`CAMERA_PIN_*`, XCLK GPIO11 at 20 MHz, PWDN GPIO46, white LED
-GPIO38) and apply to the Camera Shield.
-
-## V1.0 vs V1.1 — the backlight scale
-
-Directly from `examples/factory/utilities.h` @ `08b8b2b`:
-
-```c
-//! Using T-Display-Pro V1.0 , uncomment use V1.1 ,
-//! The difference between V1.0 and V1.1 is the backlight driver.
-// #define USING_DISPLAY_PRO_V1
-…
-#ifdef USING_DISPLAY_PRO_V1
-#define BRIGHTNESS_MAX_LEVEL        255
-#else
-#define BRIGHTNESS_MAX_LEVEL        16
-#endif
-```
-
-**255 levels on V1.0, 16 on V1.1.** Build for the wrong one and brightness is 16× off. The repo
-also ships `firmware/v1.0/` and `firmware/v1.1/` as separate directories. This is documented
-**nowhere but that comment** — see
-[revision R6](../t-display-s3-shared/board-revision-drift.md#r6--t-display-s3-pro-v10-vs-v11-backlight-driver).
-
-## Which IMU?
-
-The repo ships **both** `schematic/T-BHI260.pdf` (+ a `_V1.1` version) and
-`schematic/T-ICM29048.pdf`, KiCad footprints for both (`T-BHI260.kicad_mod`,
-`T-CIM29048.kicad_mod`), and firmware named `UnitTest_V1.1_DisChg_BHI260_241111.bin`.
-**The product name does not tell you which sensor is fitted.** Scan I²C.
-Recorded as [R7](../t-display-s3-shared/board-revision-drift.md#r7--t-display-s3-pro-two-different-imu-daughter-boards).
-
-## Power
-
-- **SY6970** at `0x6A` — full I²C charger/PMIC. Battery voltage, charge state, input current
-  limit and OTG boost are all readable/settable in software. `examples/PMU_Example` is the
-  reference. This is a genuine step up from the base board.
-- **A hardware power switch**, with a vendor caveat worth quoting: *"The power switch is only
-  effective when the battery is connected; disconnect the battery from the motherboard."*
-  It gates the battery, not USB.
-
-## Software
-
-| Route | Status |
-|---|---|
-| `Arduino_GFX` | LilyGO's choice; the repo vendors `GFX Library for Arduino` |
-| `TFT_eSPI` | plain SPI, so it *can* work, but no vendor setup file ships |
-| **ESPHome** | model **`T-DISPLAY-S3-PRO`** exists: `ST7796`, `width=222, height=480, offset_width=49, cs_pin=39, reset_pin=47, dc_pin=9, backlight_pin=48, invert_colors=True`. Note `offset_width=49` — the 222-px panel sits in a 320-wide ST7796 window |
-| Libraries | `TouchLib`, `ESP32_USB_Stream v0.0.1`, `ESP32-audioI2S v3.0.8`, `SensorLib`, `XPowersLib` |
-
-## Add-on backplates
-
-| Board | What it adds | Repo |
-|---|---|---|
-| **MVSRBoard** (`H751`, USD 10.20) | MAX98357A speaker amp, MSM261S4030H0R mic, PCF85063ATL RTC, vibration — "extremely low static current" | [`t-display-s3-pro-mvsrboard`](../t-display-s3-pro-mvsrboard/README.md) |
-| **MVSRLora** | the above **plus LoRa** | `T-Display-S3-Pro-MVSRLora` |
-| **Camera Shield** | GC0308 or OV5640 | in-repo |
-| **T-Display S3 Pro LR1121** (USD 65.29) | LoRa variant sold as its own product | store |
-
-## Artifacts
-
-`artifacts/schematic/`: `T-Display-Pro.pdf` (275 972 B, `3d21d23987d83013…`),
-`T-BHI260_V1.1.pdf` (362 516 B, `afc9bc9a426a0626…`),
-`T-ICM29048.pdf` (371 702 B, `76effd69dd22b519…`),
-`Camer-Shield.pdf` [sic] (92 889 B, `cf36beb70a7653b7…`). All retrieved 2026-09-07 at `08b8b2b`.
-Chip datasheets (ST7796S, SY6970, MAX98357A, MSM261S4030H0R, PCF85063ATL) are filed under
-their components.
-
-**Repo licence: none declared.** Redistribution status of these PDFs is **unknown**.
-
-## Gaps and conflicts
-
-| # | Item | Status |
-|---|---|---|
-| P1 | **ST7796U (README) vs ST7796S (shipped datasheet) vs `ST7796` (ESPHome)** | **Unresolved.** The S and U are different parts with different max resolutions. ESPHome's `offset_width=49` implies a 320-wide controller, consistent with either |
-| P2 | **GPIO16 is both `VIBRATING_MOTOR` and user button 3** | **Unresolved.** In the vendor's own file |
-| P3 | **Which IMU is fitted** | **Unresolved by documentation.** Scan I²C |
-| P4 | **V1.0 vs V1.1** backlight scale, documented only in a source comment | **Vendor-documented, badly** |
-| P5 | `BOARD_TOUCH_IRQ` absent from `utilities.h`, present as GPIO7 in `product_pins.h` | **Resolved in favour of `product_pins.h`** |
-| P6 | 22 open issues | maturity signal |
-| P7 | `datasheet/C492375.PDF.pdf` is named by **LCSC part number**, so what it documents is not knowable from the filename | **Open** — not retrieved by this pass |
diff --git a/devices/lilygo/t-display-s3-pro/acquisition/manifest.json b/devices/lilygo/t-display-s3-pro/acquisition/manifest.json
deleted file mode 100644
index 460fb39..0000000
--- a/devices/lilygo/t-display-s3-pro/acquisition/manifest.json
+++ /dev/null
@@ -1,332 +0,0 @@
-{
- "record": "devices/lilygo/t-display-s3-pro",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203506",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/Test-Report/ANT-Test-Report-7203506.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203506",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203506.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/Test-Report/ANT-Test-Report-7203506.pdf"
-   ],
-   "sha256": "635fa5a26234c5ba2d0a317062f9be815c91a21c1ef10af1988ff3cc135c0442",
-   "bytes": 1177730,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203506",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "ANT Test Report",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203575",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-1-7203575.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203575",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203575.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-1-7203575.pdf"
-   ],
-   "sha256": "cf8db3e26ae5a115debd2d4debe6b9fdac390ebbf1d7195e38353dcf1e93f2e6",
-   "bytes": 5534909,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203575",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos 1",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203576",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-2-7203576.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203576",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203576.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-2-7203576.pdf"
-   ],
-   "sha256": "ca357899424b5787db51b0d9b625134722200aa27c66b89e32fb336abcedd418",
-   "bytes": 5737973,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203576",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos 2",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203498",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/Label/ID-Label-Location-Info-1-7203498.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203498",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203498.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/Label/ID-Label-Location-Info-1-7203498.pdf"
-   ],
-   "sha256": "44c20ebf6a73ad6ba9a66fd9ff9b2ed11ba27886e3b4d8d44ca6f61a63757c03",
-   "bytes": 309287,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-1.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203498",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "ID Label/Location Info 1",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203516",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/Label/ID-Label-Location-Info-2-7203516.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203516",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203516.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/Label/ID-Label-Location-Info-2-7203516.pdf"
-   ],
-   "sha256": "76d12dffc288943554809d44bc4366d626b00405349d26ba0d3aea8f0d0ddb60",
-   "bytes": 227798,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-2.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203516",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "ID Label/Location Info 2",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203577",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/Internal-Photos/Internal-Photos-7203577.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203577",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203577.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/Internal-Photos/Internal-Photos-7203577.pdf"
-   ],
-   "sha256": "9624956bf203111d7f34f300d8106b7ebf84b5b267b635fdc0f803f51bed071b",
-   "bytes": 4541201,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203577",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203571",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-1-7203571.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203571",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203571.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-1-7203571.pdf"
-   ],
-   "sha256": "63235ef32237eae4d6cae39ef9bda77a377d62a920476d2d35b93b7eed989eed",
-   "bytes": 100255,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203571",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Info 1",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203574",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-2-7203574.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203574",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203574.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-2-7203574.pdf"
-   ],
-   "sha256": "621b801a871d4d99b4c3efc0a029c9b3998cb53940c88b3c6422fabfb5bcd11c",
-   "bytes": 100231,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203574",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Info 2",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-PRO-7203503",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-PRO/User-Manual/Users-Manual-7203503.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203503",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203503.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/User-Manual/Users-Manual-7203503.pdf"
-   ],
-   "sha256": "1e4c731fadac5111f5e7507b3489b5481d5a59c5833da73b7620af7c2ad39197",
-   "bytes": 938620,
-   "destination": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-03-27",
-   "fcc_id": "2ASYE-T-DISPLAY-PRO",
-   "fcc_document_id": "7203503",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "Users Manual",
-   "grant_date": "2024-03-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf",
-   "placeholder": "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-s3-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf.ARCHIVED.md
deleted file mode 100644
index 96e2380..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-PRO-ant-test-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,177,730 B (1.12 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,177,730 B (1.12 MiB) |
-| SHA-256 | `635fa5a26234c5ba2d0a317062f9be815c91a21c1ef10af1988ff3cc135c0442` |
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | ANT Test Report |
-| FCC document id | 7203506 |
-| Upstream publication date | 2024-03-27 |
-| Grant date | 2024-03-27 |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO/Test-Report/ANT-Test-Report-7203506.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203506>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203506.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/Test-Report/ANT-Test-Report-7203506.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf" \
-   "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-ant-test-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-PRO/Test-Report/ANT-Test-Report-7203506.pdf" -o "2ASYE-T-DISPLAY-PRO-ant-test-report.pdf"
-echo "635fa5a26234c5ba2d0a317062f9be815c91a21c1ef10af1988ff3cc135c0442  2ASYE-T-DISPLAY-PRO-ant-test-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf.ARCHIVED.md
deleted file mode 100644
index 525698e..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-PRO-external-photos-1.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 5,534,909 B (5.28 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 5,534,909 B (5.28 MiB) |
-| SHA-256 | `cf8db3e26ae5a115debd2d4debe6b9fdac390ebbf1d7195e38353dcf1e93f2e6` |
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos 1 |
-| FCC document id | 7203575 |
-| Upstream publication date | 2024-03-27 |
-| Grant date | 2024-03-27 |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-1-7203575.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203575>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203575.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-1-7203575.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf" \
-   "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-1.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-1-7203575.pdf" -o "2ASYE-T-DISPLAY-PRO-external-photos-1.pdf"
-echo "cf8db3e26ae5a115debd2d4debe6b9fdac390ebbf1d7195e38353dcf1e93f2e6  2ASYE-T-DISPLAY-PRO-external-photos-1.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf.ARCHIVED.md
deleted file mode 100644
index e721cdd..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-PRO-external-photos-2.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 5,737,973 B (5.47 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 5,737,973 B (5.47 MiB) |
-| SHA-256 | `ca357899424b5787db51b0d9b625134722200aa27c66b89e32fb336abcedd418` |
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos 2 |
-| FCC document id | 7203576 |
-| Upstream publication date | 2024-03-27 |
-| Grant date | 2024-03-27 |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-2-7203576.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203576>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203576.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-2-7203576.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf" \
-   "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-external-photos-2.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-PRO/External-Photos/External-Photos-2-7203576.pdf" -o "2ASYE-T-DISPLAY-PRO-external-photos-2.pdf"
-echo "ca357899424b5787db51b0d9b625134722200aa27c66b89e32fb336abcedd418  2ASYE-T-DISPLAY-PRO-external-photos-2.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-1.pdf b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-1.pdf
deleted file mode 100644
index e54bd84..0000000
Binary files a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-1.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-2.pdf b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-2.pdf
deleted file mode 100644
index 1741e0c..0000000
Binary files a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-id-label-location-info-2.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf.ARCHIVED.md
deleted file mode 100644
index f8a0e67..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-PRO-internal-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — internal photos, 4,541,201 B (4.33 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 4,541,201 B (4.33 MiB) |
-| SHA-256 | `9624956bf203111d7f34f300d8106b7ebf84b5b267b635fdc0f803f51bed071b` |
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Exhibit type | **Internal Photos** |
-| Exhibit title, as filed | Internal Photos |
-| FCC document id | 7203577 |
-| Upstream publication date | 2024-03-27 |
-| Grant date | 2024-03-27 |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO/Internal-Photos/Internal-Photos-7203577.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203577>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203577.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/Internal-Photos/Internal-Photos-7203577.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf" \
-   "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-internal-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-PRO/Internal-Photos/Internal-Photos-7203577.pdf" -o "2ASYE-T-DISPLAY-PRO-internal-photos.pdf"
-echo "9624956bf203111d7f34f300d8106b7ebf84b5b267b635fdc0f803f51bed071b  2ASYE-T-DISPLAY-PRO-internal-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf.ARCHIVED.md
deleted file mode 100644
index a395896..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 100,255 B (0.10 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 100,255 B (0.10 MiB) |
-| SHA-256 | `63235ef32237eae4d6cae39ef9bda77a377d62a920476d2d35b93b7eed989eed` |
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Info 1 |
-| FCC document id | 7203571 |
-| Upstream publication date | 2024-03-27 |
-| Grant date | 2024-03-27 |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-1-7203571.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203571>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203571.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-1-7203571.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf" \
-   "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-1-7203571.pdf" -o "2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf"
-echo "63235ef32237eae4d6cae39ef9bda77a377d62a920476d2d35b93b7eed989eed  2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf.ARCHIVED.md
deleted file mode 100644
index f9ce70a..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 100,231 B (0.10 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 100,231 B (0.10 MiB) |
-| SHA-256 | `621b801a871d4d99b4c3efc0a029c9b3998cb53940c88b3c6422fabfb5bcd11c` |
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Info 2 |
-| FCC document id | 7203574 |
-| Upstream publication date | 2024-03-27 |
-| Grant date | 2024-03-27 |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-2-7203574.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203574>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203574.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-2-7203574.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf" \
-   "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-PRO/RF-Exposure-Info/RF-Exposure-Info-2-7203574.pdf" -o "2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf"
-echo "621b801a871d4d99b4c3efc0a029c9b3998cb53940c88b3c6422fabfb5bcd11c  2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 304998a..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-PRO-users-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 938,620 B (0.90 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 938,620 B (0.90 MiB) |
-| SHA-256 | `1e4c731fadac5111f5e7507b3489b5481d5a59c5833da73b7620af7c2ad39197` |
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | Users Manual |
-| FCC document id | 7203503 |
-| Upstream publication date | 2024-03-27 |
-| Grant date | 2024-03-27 |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO/User-Manual/Users-Manual-7203503.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7203503>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-PRO/7203503.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-PRO/User-Manual/Users-Manual-7203503.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf" \
-   "devices/lilygo/t-display-s3-pro/artifacts/certification/2ASYE-T-DISPLAY-PRO-users-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-PRO/User-Manual/Users-Manual-7203503.pdf" -o "2ASYE-T-DISPLAY-PRO-users-manual.pdf"
-echo "1e4c731fadac5111f5e7507b3489b5481d5a59c5833da73b7620af7c2ad39197  2ASYE-T-DISPLAY-PRO-users-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/certification/README.md b/devices/lilygo/t-display-s3-pro/artifacts/certification/README.md
deleted file mode 100644
index d4b04ee..0000000
--- a/devices/lilygo/t-display-s3-pro/artifacts/certification/README.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-T-DISPLAY-PRO`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-T-DISPLAY-PRO`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2024-03-27** |
-| Equipment class | T-Display-S3 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Source page | <https://fccid.io/2ASYE-T-DISPLAY-PRO> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-T-DISPLAY-PRO-id-label-location-info-1.pdf` | 309,287 | `44c20ebf6a73ad6ba9a66fd9ff9b2ed11ba27886e3b4d8d44ca6f61a63757c03` | ID Label/Location Info |
-| `2ASYE-T-DISPLAY-PRO-id-label-location-info-2.pdf` | 227,798 | `76d12dffc288943554809d44bc4366d626b00405349d26ba0d3aea8f0d0ddb60` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-T-DISPLAY-PRO-ant-test-report.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-PRO-ant-test-report.pdf.ARCHIVED.md) | 1,177,730 | Test Report |
-| [`2ASYE-T-DISPLAY-PRO-external-photos-1.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-PRO-external-photos-1.pdf.ARCHIVED.md) | 5,534,909 | External Photos |
-| [`2ASYE-T-DISPLAY-PRO-external-photos-2.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-PRO-external-photos-2.pdf.ARCHIVED.md) | 5,737,973 | External Photos |
-| [`2ASYE-T-DISPLAY-PRO-internal-photos.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-PRO-internal-photos.pdf.ARCHIVED.md) | 4,541,201 | Internal Photos |
-| [`2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-PRO-rf-exposure-info-1.pdf.ARCHIVED.md) | 100,255 | RF Exposure Info |
-| [`2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-PRO-rf-exposure-info-2.pdf.ARCHIVED.md) | 100,231 | RF Exposure Info |
-| [`2ASYE-T-DISPLAY-PRO-users-manual.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-PRO-users-manual.pdf.ARCHIVED.md) | 938,620 | Users Manual |
-
-Archived total: **7 files, 17.29 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 0.51 MiB** |
-| Archived | **7 files, 17.29 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/schematic/Camer-Shield.pdf b/devices/lilygo/t-display-s3-pro/artifacts/schematic/Camer-Shield.pdf
deleted file mode 100644
index 6c1f402..0000000
Binary files a/devices/lilygo/t-display-s3-pro/artifacts/schematic/Camer-Shield.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-BHI260_V1.1.pdf b/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-BHI260_V1.1.pdf
deleted file mode 100644
index 48c4e00..0000000
Binary files a/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-BHI260_V1.1.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-Display-Pro.pdf b/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-Display-Pro.pdf
deleted file mode 100644
index 635cd22..0000000
Binary files a/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-Display-Pro.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-ICM29048.pdf b/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-ICM29048.pdf
deleted file mode 100644
index b08e812..0000000
Binary files a/devices/lilygo/t-display-s3-pro/artifacts/schematic/T-ICM29048.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-pro/certification-and-compliance.md b/devices/lilygo/t-display-s3-pro/certification-and-compliance.md
deleted file mode 100644
index 10e88c0..0000000
--- a/devices/lilygo/t-display-s3-pro/certification-and-compliance.md
+++ /dev/null
@@ -1,180 +0,0 @@
-# Certification and compliance — t-display-s3-pro
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-T-DISPLAY-PRO` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AC7Z-ESPS3WROOM1`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-DISPLAY-PRO`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-03-27** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-03-27 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 20 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY-PRO` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos-1.pdf` | 5,534,909 | `cf8db3e26ae5a115…` |
-| `External-Photos-External-Photos-2.pdf` | 5,737,973 | `ca357899424b5787…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info-1.pdf` | 309,287 | `44c20ebf6a73ad6b…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info-2.pdf` | 227,798 | `76d12dffc2889435…` |
-| `Internal-Photos-Internal-Photos.pdf` | 4,541,201 | `9624956bf203111d…` |
-| `RF-Exposure-Info-RF-Exposure-Info-1.pdf` | 100,255 | `63235ef32237eae4…` |
-| `RF-Exposure-Info-RF-Exposure-Info-2.pdf` | 100,231 | `621b801a871d4d99…` |
-| `Test-Report-ANT-Test-Report.pdf` | 1,177,730 | `635fa5a26234c5ba…` |
-| `Users-Manual-Users-Manual.pdf` | 938,620 | `1e4c731fadac5111…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY-PRO/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY-PRO/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AC7Z-ESPS3WROOM1`
-
-| Field | Value |
-|---|---|
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD |
-| Grantee code | `2AC7Z` — registered 2014-09-15, 78 FCC IDs total |
-| Final action date | **2026-02-27** |
-| Application purpose | Class II permissive change or modification of presently authorized equipment |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 57 available, 11 metadata-only |
-| Filing page | `https://fccid.io/2AC7Z-ESPS3WROOM1` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Block diagram [Block Diagram]
-- Schematic [Schematics]
-- Schematics [Schematics]
-- Operation description [Operational Description]
-- Operational Description [Operational Description]
-- Parts list [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up procedure [Parts List/Tune Up Info]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photo.pdf` | 1,367,037 | `a0104b88a862efd5…` |
-| `External-Photos-External-Photos.pdf` | 1,275,356 | `8fe953474e9707bc…` |
-| `External-Photos-External-photos.pdf` | 332,733 | `b04d392ae5298711…` |
-| `ID-Label-Location-Info-Label-location.pdf` | 30,758 | `68e843105466c162…` |
-| `ID-Label-Location-Info-Label.pdf` | 44,224 | `081ac1c0f3292f1b…` |
-| `ID-Label-Location-Info-Lable-and-location.pdf` | 1,437,286 | `0a57b90982013049…` |
-| `Internal-Photos-Internal-Photo.pdf` | 3,636,909 | `318d8c6c95232515…` |
-| `Internal-Photos-Internal-photos.pdf` | 338,977 | `1f60246b57db6172…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 499,298 | `b1ae557e1e78bbfa…` |
-| `RF-Exposure-Info-SAR-Report-A.pdf` | 845,988 | `54f4972a02877d9b…` |
-| `RF-Exposure-Info-SAR-Report-B.pdf` | 850,218 | `62b4f82db50809aa…` |
-| `RF-Exposure-Info-SAR-Report-C1.pdf` | 5,908,102 | `8fbf6c55dc6a0248…` |
-| `RF-Exposure-Info-SAR-Report-C2.pdf` | 3,930,042 | `4c6ed64c435d4f04…` |
-| `RF-Exposure-Info-SAR-Report-D.pdf` | 3,974,985 | `04798068d0a5ee3b…` |
-| `RF-Exposure-Info-SAR-Report.pdf` | 1,936,491 | `60f7208dd54ccff8…` |
-| `Test-Report-Antenna-specification.pdf` | 1,996,381 | `da8da91adaa5b481…` |
-| `Users-Manual-User-Manual.pdf` | 2,603,588 | `3e493b8b9ea24f00…` |
-| `Users-Manual-User-manual.pdf` | 886,672 | `f8d1d246c0c849a6…` |
-
-Held at `scratch/market-and-certification/fcc/2AC7Z-ESPS3WROOM1/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AC7Z-ESPS3WROOM1/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-pro/market-and-pricing.md b/devices/lilygo/t-display-s3-pro/market-and-pricing.md
deleted file mode 100644
index b66b215..0000000
--- a/devices/lilygo/t-display-s3-pro/market-and-pricing.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# Market and pricing — t-display-s3-pro
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / White | `K239` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / White with Orange | `K240` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / Black | `K241` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With GC0308 Camera / Orange | `K242` | **USD 46.54** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / White | `K232` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / White with Orange | `K235` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / Black | `K236` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / With OV5640 Camera / Orange | `K238` | **USD 56.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / White | `K231` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / White with Orange | `K233` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / Black | `K234` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Without Camera / Orange | `K237` | **USD 37.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Only Black Lens Cover / Only Black Lens Cover | `H688` | **USD 6.02** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Only MVSR Board / Only MVSR Board | `H751` | **USD 10.20** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / Black Mainboard With MVSR Board / Black Mainboard With MVSR Board | `K255` | **USD 42.33** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | China [For Worldwide] / White Mainboard With MVSR Board / White Mainboard With MVSR Board | `K255-01` | **USD 42.33** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | Germany [ For Europe only] / With GC0308 Camera / White | `K239DE` | **USD 48.99** | ✅ yes |
-| T-Display S3 Pro | 2023-09-07 | Germany [ For Europe only] / Without Camera / White | `K231DE` | **USD 41.72** | ❌ no |
-| T-Display S3 Pro LR1121 | 2025-07-16 | [K252-01] | `K252-01` | **USD 65.29** | ✅ yes |
-| T-Display S3 Pro External | 2025-11-28 | T-Display S3 Pro External [H742] | `H742` | **USD 34.05** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 46.54, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3-pro`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-⚠ **Camera tiering dominates the price**: no camera USD 37.99 → GC0308 USD 46.54 → OV5640 USD 56.99. Colour does not affect price. The LR1121 LoRa variant is a **different product** at USD 65.29.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3-shared/README.md b/devices/lilygo/t-display-s3-shared/README.md
deleted file mode 100644
index bf75d4a..0000000
--- a/devices/lilygo/t-display-s3-shared/README.md
+++ /dev/null
@@ -1,221 +0,0 @@
-# LilyGO T-Display-S3 family — shared platform record
-
-> **Not a product you can buy.** This is the hub for the T-Display-S3 *name*, which LilyGO
-> applies to at least ten electrically distinct boards. It holds the material that is genuinely
-> shared across them, the enumeration evidence, and the family-level findings.
->
-> Research snapshot **2026-09-07** (host clock, corroborated by `updated_at` timestamps in
-> LilyGO's own Shopify product feed). The task brief stated 2026-09-04; the three-day
-> discrepancy is recorded in [`research-log.md`](research-log.md) and every retrieval date in
-> this tree is the machine-verified one.
-
-## Why this directory exists
-
-Three separate things are shared and would otherwise be duplicated eleven times:
-
-1. **`LilyGo-Display-IDF/main/product_pins.h`** — one header that carries the pin map for
-   *nine* boards behind `CONFIG_LILYGO_*` switches. It is the single best cross-variant
-   primary source in the whole family, and it belongs to no one board.
-   → [`artifacts/originals/LilyGo-Display-IDF-product_pins.h`](artifacts/originals/LilyGo-Display-IDF-product_pins.h)
-2. **The base-board schematic and factory firmware**, which cover the T-Display-S3 *and*
-   T-Display-S3-Touch — LilyGO ships one schematic PDF for both.
-   → [`artifacts/schematic/T_Display_S3.pdf`](artifacts/schematic/T_Display_S3.pdf)
-3. **The family-wide traps** — the `USB CDC On Boot` trap, the Arduino-core version
-   dependency, the parallel-8080/QSPI bus split. These recur on every board and are written
-   once, here and in [`guides/hardware/parallel-8080-lcd-buses.md`](../../../guides/hardware/parallel-8080-lcd-buses.md).
-
-Precedent: [`devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/`](../../waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md).
-
----
-
-## 1. The confirmed family, enumerated from primary evidence
-
-Enumerated by listing **every repository in the `Xinyuan-LilyGO` GitHub organisation**
-(254 repos, captured 2026-09-07 →
-[`artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv`](artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv))
-and cross-checking against LilyGO's Shopify product feed
-(`https://lilygo.cc/collections/all/products.json`, 214 products, same date).
-
-**A board is listed as confirmed only when it has both a repository and a store listing, or a
-repository containing a schematic naming it.**
-
-| # | Board | One-line identity | Repo (commit) | Record | Depth |
-|---|---|---|---|---|---|
-| 1 | **T-Display-S3** | ESP32-S3R8 + 1.9″ 170×320 **ST7789V** on an **8-bit Intel-8080 parallel** bus; the reference board | `T-Display-S3` @ `ec889e7` | [`t-display-s3`](../t-display-s3/README.md) | **full** |
-| 2 | **T-Display-S3 Touch** | Same PCB and schematic as #1, panel swapped for one with a bonded **CST816S** (later **CST328**) I²C touch controller | `T-Display-S3` @ `ec889e7` | [`t-display-s3-touch`](../t-display-s3-touch/README.md) | medium |
-| 3 | **T-Display-S3 AMOLED** (1.91″) | ESP32-S3 + 240×536 **RM67162** AMOLED on **QSPI**; V1.0 and V2.0 PCBs sold side by side; touch/non-touch options | `T-Display-S3-AMOLED` @ `edd1333`, `LilyGo-AMOLED-Series` @ `6d1dc00` | [`t-display-s3-amoled`](../t-display-s3-amoled/README.md) | **full** |
-| 4 | **T-Display-S3 AMOLED Plus** | Same 1.91″ RM67162 panel, **completely different power section**: TI **BQ25896** PMIC, **PCF85063ATL** RTC + Seiko **MS412FE** backup cell, microSD slot | `LilyGo-AMOLED-Series` @ `6d1dc00` | [`t-display-s3-amoled-plus`](../t-display-s3-amoled-plus/README.md) | medium |
-| 5 | **T-Display-S3 AMOLED (DS) 1.64″** | 280×456 **CO5300 / ICNA3311** AMOLED, **FT3168** touch, **SY6970** PMIC | `T-Display-S3-AMOLED-1.64` @ `e236a4d` | [`t-display-s3-amoled-1-64`](../t-display-s3-amoled-1-64/README.md) | medium |
-| 6 | **T-Display-S3 AMOLED (DS) 1.43″ / 1.75″** | Round 466×466 panels; 1.43″ = **SH8601 / CO5300** + FT3168, 1.75″ = **CO5300** + **CST9217**; adds **PCF8563** RTC | `T-Display-S3-AMOLED-1.43-1.75` @ `87aabe8` | [`t-display-s3-amoled-1-43-1-75`](../t-display-s3-amoled-1-43-1-75/README.md) | medium |
-| 7 | **T4-S3** (the "AMOLED 2.41″") | 450×600 **RM690B0** AMOLED, **CST226SE** touch, **SY6970** PMIC, SPI microSD. Marketed as *T4-S3*, **not** as a T-Display-S3 | `LilyGo-AMOLED-Series` @ `6d1dc00` | [`t4-s3`](../t4-s3/README.md) | medium |
-| 8 | **T-Display AMOLED Lite** (1.47″) | 194×368 **SH8501B** AMOLED behind an **RS0108** 1.8 V level shifter; **AXP2101** PMU; **CHSC5816** touch. Same library, different silicon generation | `LilyGo-AMOLED-Series` @ `6d1dc00` | [`t-display-amoled-lite`](../t-display-amoled-lite/README.md) | medium |
-| 9 | **T-Display-S3 Long** | 3.4″ 180×640 bar display, **AXS15231B** (display **and** touch in one die) on QSPI; **SY6970** PMIC; hardware slide switch | `T-Display-S3-Long` @ `37a7e83` | [`t-display-s3-long`](../t-display-s3-long/README.md) | **full** |
-| 10 | **T-Display-S3 Pro** | 2.33″ 222×480 **ST7796S** on **4-wire SPI** (not parallel), **CST226SE** touch, **SY6970** PMIC, microSD, camera FPC, 3 buttons | `T-Display-S3-Pro` @ `08b8b2b` | [`t-display-s3-pro`](../t-display-s3-pro/README.md) | **full** |
-| 11 | **T-Display-S3 Pro MVSRBoard** | Backplate for #10: MAX98357A speaker amp, MSM261S4030H0R mic, PCF85063 RTC, vibration motor | `T-Display-S3-Pro-MVSRBoard` @ `c9c1a76` | [`t-display-s3-pro-mvsrboard`](../t-display-s3-pro-mvsrboard/README.md) | stub |
-
-### Refuted or out of family
-
-Recorded so nobody re-investigates them:
-
-| Candidate from the brief | Verdict | Evidence |
-|---|---|---|
-| "T-Display-S3 AMOLED Touch" as a *separate product* | **Refuted as a distinct board.** It is a purchase option of #3. LilyGO's own resource table lists `T-Display-S3-AMOLED-Touch.pdf` as *the* schematic for both the touch and non-touch 1.91″ SKUs, and the library README states "This code supports T-Display-S3 AMOLED both touch and non-touch versions" | `LilyGo-AMOLED-Series` README.MD @ `6d1dc00`, §1 and §8 |
-| "T-Display-S3 Cardputer-style" | **Refuted.** No such product or repo exists. LilyGO's keyboard handhelds are **T-Deck**, **T-Deck-Pro**, **T-Deck-MAX** and **T-Display-keyboard**, none of which carry the T-Display-S3 name or PCB | org repo listing; store feed |
-| **T-Deck** family | **Out of family.** Separate PCB, separate repo, ESP32-S3 + LoRa + BlackBerry keyboard. Related only by vendor | `T-Deck` repo, 602★ |
-| **T-Display** (ESP32), **T-QT**, **T-Dongle-S3**, **T-Display-S2**, **T-Display-RP2040**, **T-Display-GD32** | **Predecessors / cousins, not variants.** Kept as lineage stubs — see [`product-history-and-family.md`](product-history-and-family.md) | separate repos |
-| **T-Display-C5 / P4 / K230 / SF32 / CM0** | **Successor line, different SoC.** The `T-Display-` prefix is being reused for ESP32-C5, ESP32-P4, Kendryte K230 and SiFli SF32. The K230 keyboard kit is documented separately at [`t-display-k230`](../t-display-k230/) by another agent | org repo listing |
-| "AMOLED 2.41″" as a *T-Display-S3* | **Partially refuted.** The 2.41″ AMOLED board exists and is in the same library, but LilyGO sells and names it **T4-S3**. Calling it "T-Display-S3 AMOLED 2.41″" will not match any repo, SKU or board file | store handle `t4-s3`; `LilyGo-AMOLED-Series` README §1 |
-
----
-
-## 2. What is actually shared, and what is not
-
-The family name implies far more commonality than exists. This table is derived from the
-schematics and board headers, not from marketing.
-
-| Aspect | Shared across all? | Detail |
-|---|---|---|
-| SoC | **Yes, effectively** | **ESP32-S3R8** bare die (not a module) on every board in the table, 16 MB external NOR + 8 MB in-package OPI PSRAM. Only the 2023-era 1.91″ AMOLED schematic shows a **W25Q32** (4 MB) — see [§4 conflicts](#4-family-level-conflicts) |
-| Flash part | Yes | Winbond **W25Q128JV**, 16 MB, QIO → [`components/winbond/w25q128jv`](../../../components/winbond/w25q128jv/README.md) |
-| Display bus | **No — this is the big one** | 8-bit **Intel-8080 parallel** (base, Touch) · **QSPI** (all AMOLED, Long) · **4-wire SPI** (Pro) |
-| Display controller | No | ST7789V · RM67162 · RM690B0 · SH8501B · SH8601 · CO5300 · AXS15231B · ST7796S — **eight** controllers |
-| Touch controller | No | CST816S · CST328 · CST226SE · CST3530 · CST9217 · FT3168 · CHSC5816 · AXS15231B (integrated) |
-| Charger / PMIC | **No** | **TP4065** (base, 1.91″ AMOLED) · **SY6970** (Long, Pro, T4-S3, 1.64/1.43/1.75) · **BQ25896** (AMOLED Plus) · **AXP2101** (AMOLED Lite) |
-| Battery-sense pin | Mostly GPIO4 | GPIO4 on base, 1.91″ AMOLED, 1.43/1.64/1.75. **Not** on Long/Pro/T4-S3, which read the PMIC over I²C instead |
-| `BOOT` button | Yes | GPIO0 on every board |
-| Second button | GPIO14 (base) / GPIO21 (AMOLED) / GPIO0+12+16 (Pro) | Not portable |
-| Arduino board target | **Yes** | `ESP32S3 Dev Module`, 16 MB flash, OPI PSRAM, `USB CDC On Boot = Enable`, partition `16M Flash (3M APP/9.9MB FATFS)` |
-| The `USB CDC On Boot` trap | **Yes** | [§3.1](#31-the-usb-cdc-on-boot-trap) |
-| Peripheral power-enable GPIO | **No** | GPIO15 on base/Touch **only**. Nothing equivalent on the AMOLED boards |
-
-**Practical consequence.** Code written for the base T-Display-S3 will not run on any AMOLED
-board without changing the display driver, the bus type, the button pins and the power
-sequence. The only thing that ports unchanged is the Arduino board configuration. Treat
-"T-Display-S3" as a *marketing prefix*, not a platform.
-
----
-
-## 3. The three traps that catch almost everyone
-
-Full write-ups live in the base-board record; the summaries are here because they apply to
-every board in the table.
-
-### 3.1 The `USB CDC On Boot` trap
-
-**Symptom:** a board that appears completely dead — no serial output, or the sketch never
-starts — until you connect it to a PC.
-
-Every board here uses the ESP32-S3's **native USB** for both flashing and `Serial`. There is
-no CH340/CP210x. When `USB CDC On Boot = Enable` (which LilyGO's own instructions require,
-and PlatformIO sets via `-DARDUINO_USB_CDC_ON_BOOT=1`), `Serial` is the USB CDC device — and
-the Arduino core **blocks at startup waiting for a host to open the port**. Run the same
-firmware from a battery or a bench supply and it hangs before `setup()` finishes.
-
-The fix is version-dependent and counter-intuitive, and it is documented in LilyGO's own FAQ:
-
-```ini
-build_flags =
-    ; -DARDUINO_USB_CDC_ON_BOOT=1   ; prints to USB-C, BLOCKS on startup until a terminal attaches
-    -UARDUINO_USB_CDC_ON_BOOT       ; no blocking on battery; Serial moves to GPIO43/44
-```
-
-> — `T-Display-S3/README.md` FAQ 5 @ `ec889e7`; `LilyGo-AMOLED-Series/README.MD` FAQ 4 @ `6d1dc00`
-
-Disabling it moves `Serial` to **UART0 on GPIO43 (TX) / GPIO44 (RX)**, which on most of these
-boards are broken out to the header — so you lose USB console but gain a working battery
-device. Full treatment, including `USB Mode`, `Upload Mode` and the recovery ritual:
-[`t-display-s3/features/usb.md`](../t-display-s3/features/usb.md).
-
-### 3.2 The Arduino-core version dependency
-
-LilyGO pins its test matrix and does not track the current core. From
-`T-Display-S3/README.md` @ `ec889e7`:
-
-> "The test phase uses version **2.0.14**. Versions above 2.0.14 may not work correctly —
-> please downgrade if you encounter issues. As of 2024/08/02, **TFT_eSPI does not work on
-> versions higher than 2.0.14**."
-
-That is corroborated independently: the factory binaries in the repo carry
-`arduino-lib-builder` app descriptors naming their ESP-IDF base, and the newest
-(`t-display-s3-lvgl-demo-20250109`) is built on **ESP-IDF v4.4.6**, the base of
-arduino-esp32 **2.0.14** — LilyGO has not rebuilt against a 3.x core.
-Exact version table: [`t-display-s3/development.md`](../t-display-s3/development.md).
-
-### 3.3 The display-bus split
-
-`TFT_eSPI`, `Arduino_GFX` and `LovyanGFX` are **not** interchangeable here, and which one
-works depends on the bus, not the board name.
-
-| Bus | Boards | Recommended library | Why |
-|---|---|---|---|
-| 8-bit Intel-8080 parallel | T-Display-S3, Touch | **`TFT_eSPI` with `Setup206_LilyGo_T_Display_S3.h`** *or* `Arduino_GFX` `Arduino_ESP32LCD8` | TFT_eSPI needs a hand-edited `User_Setup_Select.h`; `Arduino_GFX` needs none |
-| QSPI | all AMOLED, Long | **`Arduino_GFX`** or LilyGO's own `LilyGo-AMOLED-Series` | `TFT_eSPI` has no QSPI transport; it can only be used through a **Sprite** pushed by a vendor QSPI routine |
-| 4-wire SPI | Pro | `Arduino_GFX` (LilyGO's choice) or `TFT_eSPI` | ordinary SPI, nothing special |
-
-Detail and the failure modes: [`guides/hardware/parallel-8080-lcd-buses.md`](../../../guides/hardware/parallel-8080-lcd-buses.md)
-(new, written by this pass) and the existing
-[`guides/hardware/display-interfaces.md`](../../../guides/hardware/display-interfaces.md).
-
----
-
-## 4. Family-level conflicts
-
-Recorded, not resolved by preference. Per-board detail lives in each record's
-`gaps-and-conflicts.md`.
-
-| # | Conflict | Sources | Status |
-|---|---|---|---|
-| F1 | **The two "different" factory firmwares for the base board are byte-identical.** `firmware/t-display-s3-touch-20230417_0x0.bin` and `firmware/t-display-s3-no-touch-20231013_0x0.bin` both hash to `f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa`, 1 601 328 B | measured locally 2026-09-07; user-reported in [issue #212](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212) (2024-01-02) | **Confirmed by measurement.** The filenames and their two different dates are misleading |
-| F2 | **Charger part mismatch on the base board.** Schematic sheet dated 2024-04-29 shows `U6 = TP4065` in an SOP-8-style symbol; an owner tracing a physical PCB found a **5-lead TSOT-23 marked `65b311`** | schematic `T_Display_S3.pdf`; [issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230) (2024-03-02, firsthand PCB inspection) | **Unresolved.** LilyGO never published a corrected sheet. The `65611`/`65b311` marking also appears as `AXPM65611` on three AMOLED schematics — see [§4.1](#41-the-65611-thread) |
-| F3 | **1.91″ AMOLED flash size.** The 2023 `T-DISPLAY-S3-AMOLED.pdf` shows `U3 = W25Q32` (4 MB); every README and store listing says 16 MB; the newer `T-Display-S3-AMOLED-Touch.pdf` shows `U3 = W25Q128JV` | both schematics, this repo's `artifacts/` | **Probably a stale early sheet.** Treat 16 MB as correct for shipping boards but verify with `esptool.py flash_id` before assuming |
-| F4 | **1.43/1.75″ resolution.** README says **466×466**; the board header says `LCD_WIDTH 473 / LCD_HEIGHT 467` | `T-Display-S3-AMOLED-1.43-1.75` README.md vs `components/private_library/pin_config.h`, both @ `87aabe8` | **Unresolved.** 473×467 is almost certainly the *driver window* (CO5300 addressable area) and 466×466 the visible circle |
-| F5 | **Long board pin collisions in LilyGO's own header.** `examples/factory/pins_config.h` @ `37a7e83` defines `PIN_BAT_VOLT 2` while `TP_RST 2`, and `PIN_BUTTON_2 21` while `TFT_QSPI_D2 21` | single file, self-contradictory | **Confirmed defect.** Copy-paste residue from the AMOLED header. Do not use those two defines — see [`t-display-s3-long/gaps-and-conflicts.md`](../t-display-s3-long/gaps-and-conflicts.md) |
-| F6 | **GPIO16/17 are not free on the non-touch base board.** LilyGO fits pull-ups on the back of the panel even where no touch controller exists | [issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313) (2025-07-28), answered with PCB photos by LilyGO's own maintainer `lewisxhe` | **Confirmed by vendor** |
-
-### 4.1 The `65611` thread
-
-Worth flagging because it ties F2 together with the AMOLED boards. Three independent AMOLED
-schematics — `T-Display-S3-AMOLED-Touch.pdf` (U5), `T-Display-S3-AMOLED-Plus.pdf` (U4) — carry
-a part LilyGO writes as **`AXPM65611`** on a `VIN`-pin-12 symbol, and the base-board owner in
-issue #230 read **`65b311`** off a 5-lead TSOT-23. No datasheet for either string was located
-during this pass and no manufacturer could be identified from primary evidence.
-
-**It is recorded as unidentified rather than guessed** —
-[`components/unidentified/lilygo-t-display-s3-family/axpm65611/`](../../../components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md)
-states exactly what evidence would resolve it.
-
----
-
-## 5. Shared artifacts held here
-
-| File | Bytes | SHA-256 (first 16) | What it is |
-|---|---|---|---|
-| [`artifacts/schematic/T_Display_S3.pdf`](artifacts/schematic/T_Display_S3.pdf) | 395 064 | `607b6330063652 1f` | **The** base-board schematic, one sheet, title block dated **2024-04-29**. Covers T-Display-S3 and T-Display-S3-Touch |
-| [`artifacts/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf`](artifacts/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf) | 693 393 | `c3d5651d79b933d0` | MIDI shield add-on schematic V1.1 |
-| [`artifacts/originals/LilyGo-Display-IDF-product_pins.h`](artifacts/originals/LilyGo-Display-IDF-product_pins.h) | 13 544 | `c400cc8dcc1ccf28` | Nine boards' pin maps in one header, ESP-IDF side |
-| [`artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv`](artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv) | — | — | The enumeration evidence: all 254 org repos with push dates |
-| [`artifacts/originals/platformio.ini`](artifacts/originals/platformio.ini) · [`boards-lilygo-t-display-s3.json`](artifacts/originals/boards-lilygo-t-display-s3.json) | 7 981 / 855 | `d0ce207e8bdea5f3` / `529abb0314591c5f` | PlatformIO build definition and board manifest |
-| [`artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h`](artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h) | 906 | `809949416716286a` | The `TFT_eSPI` user setup that must be selected by hand |
-| `artifacts/firmware/*.bin` (6 files) | 489 616 – 1 601 328 | see [`../t-display-s3/factory-firmware.md`](../t-display-s3/factory-firmware.md) | Merged `0x0` factory images, ESP32-S3, decoded partition tables |
-
-All retrieved 2026-09-07 from `raw.githubusercontent.com` at the pinned commits above.
-Repository licence is **MIT** for `T-Display-S3`, `T-Display-S3-AMOLED` and
-`LilyGo-AMOLED-Series`; **none declared** for `T-Display-S3-Long` and `T-Display-S3-Pro`;
-**GPL-3.0** for the 1.64 and 1.43-1.75 repos. Vendor-mirrored *chip* datasheets are filed under
-their component records, not here — see [`sources.md`](sources.md).
-
----
-
-## 6. Documentation map
-
-- [`product-history-and-family.md`](product-history-and-family.md) — the lineage from TTGO
-  T-Display (2019) to T-Display-P4/K230 (2026), with dates
-- [`sources.md`](sources.md) — full source table for the family-level claims
-- [`research-log.md`](research-log.md) — queries, depth, dead ends, date discrepancy
-- Per-board records — see [§1](#1-the-confirmed-family-enumerated-from-primary-evidence)
-- [`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md) — how to find LilyGO
-  documentation, and the traps in doing so
-- [`guides/hardware/parallel-8080-lcd-buses.md`](../../../guides/hardware/parallel-8080-lcd-buses.md)
-- [`guides/markets/clones-and-variants.md`](../../../guides/markets/clones-and-variants.md) —
-  read for method; the T-Display-S3 worked example is in
-  [`t-display-s3/comparisons-and-recommendations.md`](../t-display-s3/comparisons-and-recommendations.md)
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-lvgl-demo-20250109_0x0.bin b/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-lvgl-demo-20250109_0x0.bin
deleted file mode 100644
index b2a8a77..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-lvgl-demo-20250109_0x0.bin and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-midi-v1.0.1-20231013_0x0.bin b/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-midi-v1.0.1-20231013_0x0.bin
deleted file mode 100644
index 12b12a0..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-midi-v1.0.1-20231013_0x0.bin and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-no-touch-20231013_0x0.bin b/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-no-touch-20231013_0x0.bin
deleted file mode 100644
index 208864d..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-no-touch-20231013_0x0.bin and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-screen-detect-20230315_0x0.bin b/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-screen-detect-20230315_0x0.bin
deleted file mode 100644
index de0dd8c..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-screen-detect-20230315_0x0.bin and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-tft-espi-20231113_0x0.bin b/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-tft-espi-20231113_0x0.bin
deleted file mode 100644
index 75cf034..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-tft-espi-20231113_0x0.bin and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-touch-20230417_0x0.bin b/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-touch-20230417_0x0.bin
deleted file mode 100644
index 208864d..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-touch-20230417_0x0.bin and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/originals/LilyGo-Display-IDF-product_pins.h b/devices/lilygo/t-display-s3-shared/artifacts/originals/LilyGo-Display-IDF-product_pins.h
deleted file mode 100644
index ef64509..0000000
--- a/devices/lilygo/t-display-s3-shared/artifacts/originals/LilyGo-Display-IDF-product_pins.h
+++ /dev/null
@@ -1,531 +0,0 @@
-/**
- * @file      product_pins.h
- * @author    Lewis He (lewishe@outlook.com)
- * @license   MIT
- * @copyright Copyright (c) 2024  Shenzhen Xinyuan Electronic Technology Co., Ltd
- * @date      2024-01-07
- *
- */
-
-#pragma once
-
-#include <sdkconfig.h>
-#include "initSequence.h"
-
-#define BOARD_NONE_PIN      (-1)
-
-// LILYGO 1.47 Inch AMOLED(SH8501) S3R8
-// https://www.lilygo.cc/products/t-display-amoled
-#if CONFIG_LILYGO_T_AMOLED_LITE_147
-
-#define BOARD_DISP_CS       (4)
-#define BOARD_DISP_SCK      (5)
-#define BOARD_DISP_DATA0    (7)
-#define BOARD_DISP_DATA1    (10)
-#define BOARD_DISP_DATA2    (11)
-#define BOARD_DISP_DATA3    (12)
-#define BOARD_DISP_RESET    (40)
-#define BOARD_DISP_TE       (6)
-#define BOARD_I2C_SDA       (1)
-#define BOARD_I2C_SCL       (2)
-#define BOARD_PMU_IRQ       (3)
-#define BOARD_SENSOR_IRQ    (8)
-#define BOARD_TOUCH_IRQ     (13)
-#define BOARD_TOUCH_RST     (14)
-#define BOARD_BOOT_PIN      (0)
-#define BOARD_BUTTON1_PIN   (0)
-#define BOARD_BUTTON2_PIN   (21)
-#define BOARD_PIXELS_PIN    (18)
-#define BOARD_PIXELS_NUM    (1)
-#define DEFAULT_SCK_SPEED   (30000000)
-
-#define AMOLED_WIDTH        194
-#define AMOLED_HEIGHT       368
-#define AMOLED_EN_PIN       (-1)
-
-
-#define AMOLED_INIT_CMD     sh8501_cmd
-#define AMOLED_INIT_CMD_LEN SH8501_INIT_SEQUENCE_LENGHT
-
-#define CONFIG_PMU_AXP2101  (1)
-#define BOARD_HAS_TOUCH      1
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-#define DISPLAY_FULLRESH     true
-// LILYGO 1.91 Inch AMOLED(RM67162) S3R8
-// https://www.lilygo.cc/products/t-display-s3-amoled?variant=42837728526517
-#elif CONFIG_LILYGO_T_DISPLAY_S3_AMOLED
-
-#define BOARD_DISP_CS       (6)
-#define BOARD_DISP_SCK      (47)
-#define BOARD_DISP_DATA0    (18)
-#define BOARD_DISP_DATA1    (7)
-#define BOARD_DISP_DATA2    (48)
-#define BOARD_DISP_DATA3    (5)
-#define BOARD_DISP_RESET    (17)
-#define BOARD_DISP_TE       (9)
-
-#define BOARD_BOOT_PIN      (0)
-#define BOARD_BUTTON1_PIN   (0)
-#define BOARD_BUTTON2_PIN   (21)
-#define DEFAULT_SCK_SPEED   (75000000)
-
-// Define 3,2 use i2c
-#define BOARD_I2C_SDA       (3)
-#define BOARD_I2C_SCL       (2)
-
-#define AMOLED_WIDTH        240
-#define AMOLED_HEIGHT       536
-#define AMOLED_EN_PIN       (-1)
-
-#define AMOLED_INIT_CMD     rm67162_cmd
-#define AMOLED_INIT_CMD_LEN RM67162_INIT_SEQUENCE_LENGHT
-#define BOARD_HAS_TOUCH      0
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-#define DISPLAY_FULLRESH     true
-
-// LILYGO 1.91 Inch AMOLED Touch (RM67162) S3R8
-// https://www.lilygo.cc/products/t-display-s3-amoled?variant=43228221636789
-#elif CONFIG_LILYGO_T_DISPLAY_S3_AMOLED_TOUCH
-
-#define BOARD_DISP_CS       (6)
-#define BOARD_DISP_SCK      (47)
-#define BOARD_DISP_DATA0    (18)
-#define BOARD_DISP_DATA1    (7)
-#define BOARD_DISP_DATA2    (48)
-#define BOARD_DISP_DATA3    (5)
-#define BOARD_DISP_RESET    (17)
-#define BOARD_DISP_TE       (9)
-
-#define BOARD_I2C_SDA       (3)
-#define BOARD_I2C_SCL       (2)
-
-#define BOARD_TOUCH_IRQ     (21)
-#define BOARD_TOUCH_RST     (-1)
-
-#define BOARD_BOOT_PIN      (0)
-#define BOARD_BUTTON1_PIN   (0)
-#define BOARD_BUTTON2_PIN   (21)
-#define DEFAULT_SCK_SPEED   (75000000)
-
-#define AMOLED_WIDTH        240
-#define AMOLED_HEIGHT       536
-#define AMOLED_EN_PIN       (38)
-
-#define AMOLED_INIT_CMD     rm67162_cmd
-#define AMOLED_INIT_CMD_LEN RM67162_INIT_SEQUENCE_LENGHT
-#define BOARD_HAS_TOUCH      1
-
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-#define DISPLAY_FULLRESH     true
-// LILYGO 2.41 Inch AMOLED(RM690B0) S3R8
-// https://www.lilygo.cc/products/t4-s3
-#elif CONFIG_LILYGO_T4_S3_241
-
-#define BOARD_DISP_CS       (11)
-#define BOARD_DISP_SCK      (15)
-#define BOARD_DISP_DATA0    (14)
-#define BOARD_DISP_DATA1    (10)
-#define BOARD_DISP_DATA2    (16)
-#define BOARD_DISP_DATA3    (12)
-#define BOARD_DISP_RESET    (13)
-#define BOARD_DISP_TE       (-1)
-
-#define BOARD_I2C_SDA       (6)
-#define BOARD_I2C_SCL       (7)
-
-#define BOARD_TOUCH_IRQ     (8)
-#define BOARD_TOUCH_RST     (17)
-
-#define BOARD_SD_MISO       (4)
-#define BOARD_SD_MOSI       (2)
-#define BOARD_SD_SCLK       (3)
-#define BOARD_SD_CS         (1)
-
-#define BOARD_BOOT_PIN      (0)
-#define BOARD_BUTTON1_PIN   (0)
-#define DEFAULT_SCK_SPEED   (36000000)
-
-#define AMOLED_WIDTH        600
-#define AMOLED_HEIGHT       450
-
-#define AMOLED_EN_PIN       (9)
-
-#define AMOLED_INIT_CMD     rm690b0_cmd
-#define AMOLED_INIT_CMD_LEN RM690B0_INIT_SEQUENCE_LENGHT
-
-#define CONFIG_PMU_SY6970   (1)
-
-#define BOARD_HAS_TOUCH      1
-
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-#define DISPLAY_FULLRESH     true
-
-#elif CONFIG_LILYGO_T_Track_102
-
-#define AMOLED_WIDTH        600
-#define AMOLED_HEIGHT       450
-
-#define AMOLED_EN_PIN       (-1)
-
-#define AMOLED_INIT_CMD     jd9613_cmd
-#define AMOLED_INIT_CMD_LEN JD9613_INIT_SEQUENCE_LENGHT
-
-#define BOARD_HAS_TOUCH      0
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-
-#define DISPLAY_FULLRESH     true
-
-
-#elif CONFIG_LILYGO_T_DISPLAY
-
-#define BOARD_POWERON        (gpio_num_t)(14)
-
-#define BOARD_SPI_MISO       (21)
-#define BOARD_SPI_MOSI       (19)
-#define BOARD_SPI_SCK        (18)
-#define BOARD_TFT_CS         (5)
-#define BOARD_TFT_RST        (23)
-#define BOARD_TFT_DC         (16)
-#define BOARD_TFT_BL         (4)
-
-#define AMOLED_WIDTH         (135)
-#define AMOLED_HEIGHT        (240)
-
-#define BOARD_HAS_TOUCH      0
-
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * 100)
-
-#define DISPLAY_FULLRESH     false
-
-#elif CONFIG_LILYGO_T_DISPLAY_S3
-
-#define BOARD_POWERON        (gpio_num_t)(15)
-
-#define BOARD_TFT_BL         (38)
-#define BOARD_TFT_DATA0      (39)
-#define BOARD_TFT_DATA1      (40)
-#define BOARD_TFT_DATA2      (41)
-#define BOARD_TFT_DATA3      (42)
-#define BOARD_TFT_DATA4      (45)
-#define BOARD_TFT_DATA5      (46)
-#define BOARD_TFT_DATA6      (47)
-#define BOARD_TFT_DATA7      (48)
-#define BOARD_TFT_RST        (5)
-#define BOARD_TFT_CS         (6)
-#define BOARD_TFT_DC         (7)
-#define BOARD_TFT_WR         (8)
-#define BOARD_TFT_RD         (9)
-#define BOARD_I2C_SCL        (17)
-#define BOARD_I2C_SDA        (18)
-#define BOARD_TOUCH_IRQ      (16)
-#define BOARD_TOUCH_RST      (21)
-#define AMOLED_WIDTH         (170)
-#define AMOLED_HEIGHT        (320)
-
-#define BOARD_HAS_TOUCH      1
-
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * 100)
-
-#define DISPLAY_FULLRESH     false
-
-#elif CONFIG_LILYGO_T_DISPLAY_S3_PRO
-
-// LTR553 , TOUCH , SY6970 , Camera share I2C Bus
-#define BOARD_I2C_SDA        (5)
-#define BOARD_I2C_SCL        (6)
-// SD , TFT share SPI Bus
-#define BOARD_SPI_MISO       (8)
-#define BOARD_SPI_MOSI       (17)
-#define BOARD_SPI_SCK        (18)
-#define BOARD_TFT_CS         (39)
-#define BOARD_TFT_RST        (47)
-#define BOARD_TFT_DC         (9)
-#define BOARD_TFT_BL         (48)
-#define BOARD_SD_CS          (14)
-#define BOARD_SENSOR_IRQ     (21)
-#define BOARD_TOUCH_RST      (13)
-#define BOARD_TOUCH_IRQ      (7)
-#define AMOLED_HEIGHT        (480)
-#define AMOLED_WIDTH         (222)
-
-#define BOARD_HAS_TOUCH      1
-#define DISPLAY_FULLRESH     false
-
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * 100)
-
-#elif CONFIG_LILYGO_T_QT_S3
-
-// #define BOARD_POWERON        (gpio_num_t)(10)
-
-#define BOARD_SPI_MISO       (-1)
-#define BOARD_SPI_MOSI       (2)
-#define BOARD_SPI_SCK        (3)
-#define BOARD_TFT_CS         (5)
-#define BOARD_TFT_RST        (1)
-#define BOARD_TFT_DC         (6)
-#define BOARD_TFT_BL         (10)
-
-#define AMOLED_HEIGHT        (128)
-#define AMOLED_WIDTH         (128)
-
-#define BOARD_HAS_TOUCH      0
-#define DISPLAY_FULLRESH     false
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-
-#elif CONFIG_LILYGO_T_DONGLE_S2
-
-// #define BOARD_POWERON        (gpio_num_t)(10)
-
-#define BOARD_SPI_MISO       (-1)
-#define BOARD_SPI_MOSI       (35)
-#define BOARD_SPI_SCK        (36)
-#define BOARD_TFT_CS         (34)
-#define BOARD_TFT_RST        (38)
-#define BOARD_TFT_DC         (37)
-#define BOARD_TFT_BL         (33)
-
-#define AMOLED_HEIGHT        (135)
-#define AMOLED_WIDTH         (240)
-
-#define BOARD_HAS_TOUCH      0
-#define DISPLAY_FULLRESH     false
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-#elif CONFIG_LILYGO_T_DONGLE_S3
-
-// #define BOARD_POWERON        (gpio_num_t)(10)
-
-#define BOARD_SPI_MISO       (-1)
-#define BOARD_SPI_MOSI       (3)
-#define BOARD_SPI_SCK        (5)
-#define BOARD_TFT_CS         (4)
-#define BOARD_TFT_RST        (1)
-#define BOARD_TFT_DC         (2)
-#define BOARD_TFT_BL         (38)
-
-#define AMOLED_HEIGHT        (80)
-#define AMOLED_WIDTH         (160)
-
-#define BOARD_HAS_TOUCH      0
-#define DISPLAY_FULLRESH     false
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-#elif CONFIG_LILYGO_T_DISPLAY_LONG
-
-
-#define BOARD_DISP_CS       (12)
-#define BOARD_DISP_SCK      (17)
-#define BOARD_DISP_DATA0    (13)
-#define BOARD_DISP_DATA1    (18)
-#define BOARD_DISP_DATA2    (21)
-#define BOARD_DISP_DATA3    (14)
-#define BOARD_DISP_RESET    (16)
-#define BOARD_DISP_TE       (-1)
-#define BOARD_DISP_BL       (1)
-
-#define BOARD_I2C_SDA       (15)
-#define BOARD_I2C_SCL       (10)
-
-#define BOARD_TOUCH_IRQ     (11)
-#define BOARD_TOUCH_RST     (16)
-
-#define AMOLED_HEIGHT       (180)
-#define AMOLED_WIDTH        (640)
-
-#define BOARD_HAS_TOUCH      1
-
-#define DISPLAY_FULLRESH     true
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-#define DEFAULT_SCK_SPEED   (30000000)
-
-#elif CONFIG_LILYGO_T_HMI
-
-
-#define BOARD_POWERON         (gpio_num_t)(14)
-#define BOARD_POWERON1        (gpio_num_t)(10)
-
-#define BOARD_TFT_BL         (38)
-#define BOARD_TFT_DATA0      (48)
-#define BOARD_TFT_DATA1      (47)
-#define BOARD_TFT_DATA2      (39)
-#define BOARD_TFT_DATA3      (40)
-#define BOARD_TFT_DATA4      (41)
-#define BOARD_TFT_DATA5      (42)
-#define BOARD_TFT_DATA6      (45)
-#define BOARD_TFT_DATA7      (46)
-#define BOARD_TFT_RST        (-1)
-#define BOARD_TFT_CS         (6)
-#define BOARD_TFT_DC         (7)
-#define BOARD_TFT_WR         (8)
-
-
-#define BOARD_TOUCH_SPI_MISO (4)
-#define BOARD_TOUCH_SPI_MOSI (3)
-#define BOARD_TOUCH_SPI_SCLK (1)
-#define BOARD_TOUCH_SPI_CS   (2)
-#define BOARD_TOUCH_IRQ      (gpio_num_t)(9)
-
-#define AMOLED_WIDTH         (240)
-#define AMOLED_HEIGHT        (320)
-
-#define BOARD_HAS_TOUCH      1
-
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * 100)
-
-#define DISPLAY_FULLRESH     false
-
-#elif CONFIG_LILYGO_T_QT_C6
-
-#define BOARD_SPI_MISO       (-1)
-#define BOARD_SPI_MOSI       (15)
-#define BOARD_SPI_SCK        (18)
-#define BOARD_TFT_CS         (14)
-#define BOARD_TFT_RST        (20)
-#define BOARD_TFT_DC         (19)
-#define BOARD_TFT_BL         (2)
-
-#define BOARD_I2C_SDA       (21)
-#define BOARD_I2C_SCL       (22)
-
-#define BOARD_TOUCH_IRQ     (7)
-#define BOARD_TOUCH_RST     (23)
-
-#define AMOLED_HEIGHT        (128)
-#define AMOLED_WIDTH         (128)
-
-#define BOARD_HAS_TOUCH      1
-#define DISPLAY_FULLRESH     false
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-
-
-#elif CONFIG_LILYGO_T_RGB
-
-// #define BOARD_POWERON        (15)
-
-#define BOARD_TFT_BL         (gpio_num_t)(46)
-
-#define BOARD_TFT_HSYNC          47
-#define BOARD_TFT_VSYNC          41
-#define BOARD_TFT_DE             45
-#define BOARD_TFT_PCLK           42
-
-
-#define BOARD_TFT_DATA0      (44)
-#define BOARD_TFT_DATA1      (21)
-#define BOARD_TFT_DATA2      (18)
-#define BOARD_TFT_DATA3      (17)
-#define BOARD_TFT_DATA4      (16)
-#define BOARD_TFT_DATA5      (15)
-#define BOARD_TFT_DATA6      (14)
-#define BOARD_TFT_DATA7      (13)
-#define BOARD_TFT_DATA8      (12)
-#define BOARD_TFT_DATA9      (11)
-#define BOARD_TFT_DATA10     (10)
-#define BOARD_TFT_DATA11     (9)
-#define BOARD_TFT_DATA12     (43)
-#define BOARD_TFT_DATA13     (7)
-#define BOARD_TFT_DATA14     (6)
-#define BOARD_TFT_DATA15     (5)
-#define BOARD_TFT_DATA16     (3)
-#define BOARD_TFT_DATA17     (2)
-
-#define BOARD_TFT_RST        (6)
-#define BOARD_TFT_CS         (3)
-#define BOARD_TFT_MOSI       (4)
-#define BOARD_TFT_SCLK       (5)
-
-#define BOARD_I2C_SDA        (8)
-#define BOARD_I2C_SCL        (48)
-
-#define BOARD_TOUCH_IRQ      (1)
-#define BOARD_TOUCH_RST      (1)
-#define AMOLED_WIDTH         (480)
-#define AMOLED_HEIGHT        (480)
-
-#define SDMMC_EN            (7)
-#define BOARD_HAS_TOUCH      1
-
-#define DISPLAY_BUFFER_SIZE  (AMOLED_WIDTH * AMOLED_HEIGHT)
-
-#define DISPLAY_FULLRESH     false
-
-#elif CONFIG_LILYGO_T_WATCH_S3
-
-#define BOARD_SPI_MISO       (-1)
-#define BOARD_SPI_MOSI       (13)
-#define BOARD_SPI_SCK        (18)
-#define BOARD_TFT_CS         (12)
-#define BOARD_TFT_RST        (-1)
-#define BOARD_TFT_DC         (38)
-#define BOARD_TFT_BL         (45)
-
-#define BOARD_I2C_SDA        (10)
-#define BOARD_I2C_SCL        (11)
-
-#define BOARD_TOUCH_IRQ      (16)
-#define BOARD_TOUCH_RST      (-1)
-
-#define AMOLED_HEIGHT        (240)
-#define AMOLED_WIDTH         (240)
-
-#define BOARD_HAS_TOUCH       0         //NOT YET
-#define DISPLAY_FULLRESH      false
-#define DISPLAY_BUFFER_SIZE   (AMOLED_WIDTH * AMOLED_HEIGHT)
-#define CONFIG_PMU_AXP2101  (1)
-
-#elif CONFIG_LILYGO_T_WATCH_2019
-
-
-#define BOARD_SPI_MISO       (-1)
-#define BOARD_SPI_MOSI       (19)
-#define BOARD_SPI_SCK        (18)
-#define BOARD_TFT_CS         (5)
-#define BOARD_TFT_RST        (-1)
-#define BOARD_TFT_DC         (27)
-#define BOARD_TFT_BL         (12)
-
-#define BOARD_I2C_SDA        (21)
-#define BOARD_I2C_SCL        (22)
-
-#define BOARD_TOUCH_IRQ      (38)
-#define BOARD_TOUCH_RST      (-1)
-
-#define AMOLED_HEIGHT        (240)
-#define AMOLED_WIDTH         (240)
-
-#define BOARD_HAS_TOUCH       0         //NOT YET
-#define DISPLAY_FULLRESH      false
-#define DISPLAY_BUFFER_SIZE   (AMOLED_WIDTH * AMOLED_HEIGHT)
-#define CONFIG_PMU_AXP202     (1)
-
-
-
-
-#else
-#error "No select product"
-#endif
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/originals/boards-lilygo-t-display-s3.json b/devices/lilygo/t-display-s3-shared/artifacts/originals/boards-lilygo-t-display-s3.json
deleted file mode 100644
index 419532f..0000000
--- a/devices/lilygo/t-display-s3-shared/artifacts/originals/boards-lilygo-t-display-s3.json
+++ /dev/null
@@ -1,45 +0,0 @@
-{
-  "build": {
-    "arduino": {
-      "ldscript": "esp32s3_out.ld",
-      "memory_type": "qio_opi",
-      "partitions": "default_16MB.csv"
-    },
-    "core": "esp32",
-    "extra_flags": [
-      "-DBOARD_HAS_PSRAM"
-    ],
-    "f_cpu": "240000000L",
-    "f_flash": "80000000L",
-    "flash_mode": "qio",
-    "hwids": [
-      [
-        "0X303A",
-        "0x1001"
-      ]
-    ],
-    "mcu": "esp32s3",
-    "variant": "esp32s3"
-  },
-  "connectivity": [
-    "wifi",
-    "bluetooth"
-  ],
-  "debug": {
-    "openocd_target": "esp32s3-builtin.cfg"
-  },
-  "frameworks": [
-    "arduino",
-    "espidf"
-  ],
-  "name": "T-DisplayS3",
-  "upload": {
-    "flash_size": "16MB",
-    "maximum_ram_size": 327680,
-    "maximum_size": 16777216,
-    "require_upload_port": true,
-    "speed": 921600
-  },
-  "url": "https://www.lilygo.cc/products/t-display-s3",
-  "vendor": "LILYGO"
-}
\ No newline at end of file
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/originals/platformio.ini b/devices/lilygo/t-display-s3-shared/artifacts/originals/platformio.ini
deleted file mode 100644
index e9fae35..0000000
--- a/devices/lilygo/t-display-s3-shared/artifacts/originals/platformio.ini
+++ /dev/null
@@ -1,411 +0,0 @@
-; PlatformIO Project Configuration File
-;
-;   Build options: build flags, source filter
-;   Upload options: custom upload port, speed and extra flags
-;   Library options: dependencies, extra library storages
-;   Advanced options: extra scripting
-;
-; Please visit documentation for the other options and example
-; https://docs.platformio.org/page/projectconf.html
-
-[platformio]
-
-; default_envs = Arduino_GFX_PDQgraphicstest
-; default_envs = Arduino_GFXDemo
-default_envs = factory
-; default_envs = Sleep
-; default_envs = lv_demos
-; default_envs = nes
-; default_envs = sd
-; default_envs = tft
-; default_envs = TFT_Rainbow
-; default_envs = touch_test
-; default_envs = usb_hid_pad
-; default_envs = ota
-; default_envs = SerialExample
-; default_envs = T-Display-S3-MIDI
-; default_envs = T-Display-S3-Piano
-; default_envs = ImageScroll
-; default_envs = GetBatteryVoltage
-; default_envs = PokerS3
-; default_envs = PCBClock
-; default_envs = WIFI_Audio_I2S
-; default_envs = CapacitiveTouch
-
-src_dir = examples/${platformio.default_envs}
-
-
-[env]
-platform = espressif32@6.5.0
-board = lilygo-t-display-s3
-framework = arduino
-
-debug_tool = esp-builtin
-
-; Use this when burning with USB CDC
-upload_protocol = esptool
-
-; When using ESP32-USB-JTAG debugging
-; upload_protocol = esp-builtin
-
-build_flags = 
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    ; -UARDUINO_USB_CDC_ON_BOOT
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DARDUINO_USB_MODE=1
-    ; Choose different options according to different driver chips
-    ; Early use of CST328
-    -DTOUCH_MODULES_CST_MUTUAL
-    ; Use CST816 by default
-    ; -DTOUCH_MODULES_CST_SELF        
-
-[env:Arduino_GFX_PDQgraphicstest]
-lib_ignore =
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:Arduino_GFXDemo]
-lib_ignore =
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:factory]
-lib_ignore =
-    TFT_eSPI
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-
-[env:lv_demos]
-build_flags =   ${env.build_flags}
-lib_ignore =
-    TFT_eSPI
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-
-[env:nes]
-lib_ignore =
-    TFT_eSPI
-    Adafruit MPR121
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:sd]
-lib_ignore =
-    TFT_eSPI
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:tft]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:Sleep]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:TFT_Rainbow]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:ImageScroll]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:touch_test]
-extends = env
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:SerialExample]
-lib_ignore =
-    TFT_eSPI
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:MPR121TouchSensor]
-lib_ignore =
-    TFT_eSPI
-    GFX Library for Arduino
-    arduino-nofrendo
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:I2CScan]
-lib_ignore =
-    TFT_eSPI
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:usb_hid_pad]
-build_flags =   -DARDUINO_USB_MODE=0
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:ota]
-upload_protocol = espota
-; Change to the IP address of the board
-upload_port = 192.168.36.172
-
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:T-Display-S3-MIDI]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    DabbleESP32
-    lvgl
-
-[env:T-Display-S3-Piano]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DARDUINO_USB_MODE=0
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    lovyan03/LovyanGFX
-lib_ignore =
-    GFX Library for Arduino
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:GetBatteryVoltage]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:PokerS3]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:PCBClock]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-[env:WIFI_Audio_I2S]
-
-[env:CapacitiveTouch]
-lib_ignore =
-    GFX Library for Arduino
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-    TouchLib
-
-
-[env:T-Display-S3-Queue]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    lovyan03/LovyanGFX
-lib_ignore =
-    GFX Library for Arduino
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:T-Display-S3-Gingoduino]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    lovyan03/LovyanGFX
-lib_ignore =
-    GFX Library for Arduino
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:T-Display-S3-Piano-Debug]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    lovyan03/LovyanGFX
-lib_ignore =
-    GFX Library for Arduino
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:T-Display-S3-BLE-Receiver]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    lovyan03/LovyanGFX
-lib_ignore =
-    GFX Library for Arduino
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:T-Display-S3-BLE-Sender]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    lovyan03/LovyanGFX
-lib_ignore =
-    GFX Library for Arduino
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:T-Display-S3-USB-Device]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DARDUINO_USB_MODE=0
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    lovyan03/LovyanGFX
-lib_ignore =
-    GFX Library for Arduino
-    TFT_eSPI
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
-
-[env:T-Display-S3-Music-Explorer]
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DTOUCH_MODULES_CST_MUTUAL
-lib_deps =
-    sauloverissimo/gingoduino
-lib_ignore =
-    GFX Library for Arduino
-    LovyanGFX
-    arduino-nofrendo
-    Adafruit MPR121
-    DabbleESP32
-    PCF8575 library
-    PCA95x5
-    lvgl
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv b/devices/lilygo/t-display-s3-shared/artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv
deleted file mode 100644
index 8e2a8b3..0000000
--- a/devices/lilygo/t-display-s3-shared/artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv
+++ /dev/null
@@ -1,254 +0,0 @@
-T5S3-4.7-e-paper-PRO	2026-09-01T03:24:55Z	H752-01	114	UI written for the LilyGo-EPD47-S3 project
-T-Display-S3-MicroPython	2026-09-04T06:51:48Z	main	4	
-lilygobox-espidf	2026-09-02T10:20:17Z	main	2	
-T-Echo-Lite-MicroPython	2026-09-04T01:27:42Z	main	0	
-lilygo_device_driver_example	2026-09-04T01:11:50Z	main	0	
-lilygo_device_driver	2026-09-04T01:11:27Z	main	1	
-T-Halow-P4	2026-08-05T08:10:13Z	master	8	
-T-Display-S3	2026-08-31T07:24:25Z	main	1167	
-T-2Can	2026-08-24T08:06:47Z	main	35	
-T-CAN485	2026-08-27T06:57:53Z	arduino-esp32-libs_v3.0.1	164	
-T-Display-K230	2026-09-03T09:49:04Z	main	1	
-T-QT-C6	2026-09-03T08:34:34Z	main	16	TQT-C6 is a mini development board based on the ESP32C6 chip, which is only the size of two thumbnails. It features a 128x128px TFT full-color touch screen, a separate charging indicator light, and an independent battery. It can communicate with the power path management chip to modify the power bus status and limit values.
-T-Display-S3-Pro	2026-08-06T09:33:36Z	master	63	
-LilyGo-Modem-Series	2026-09-03T07:54:45Z	main	348	LilyGo A7670X A7608X SIM7670G SIM7000G SIM7080 SIM7600 series
-LILYGO-Spark	2026-09-03T05:21:51Z	main	28	A firmware hub and flashing tool for esp32 series boards — discover, share, and flash firmware with ease.
-T-Embed-CC1101	2026-08-24T09:43:54Z	master	495	
-T-Deck	2026-09-03T03:33:36Z	master	602	LilyGo-T-Deck & T-Deck-Plus
-LilyGo-Modem-Series-MicroPython	2025-09-18T02:59:57Z	main	2	
-T-Display-K230_canmv_rt	2026-08-03T02:27:11Z	main	25	
-LilyGo-T-Display-S2	2022-09-23T02:46:48Z	master	48	
-T-Keyboard-S3-Pro	2025-09-06T09:15:56Z	main	23	This is an upgraded version of the T-Keyboard-S3 developed based on the T-Keyboard-S3 project, named T-Keyboard-S3-Pro. 
-T-Display-P4	2026-09-01T05:37:13Z	main	58	The T-Display-P4 is a versatile development board based on the ESP32-P4 core.
-T-Radar	2026-05-27T07:32:33Z	master	5	
-LilyGO-T-HiGrow-LoRaWLAN	2022-10-14T09:45:11Z	master	15	
-T-Display-CM0	2026-09-02T09:12:42Z	main	2	board base CM0_Lite
-T-Halow	2026-01-16T02:48:47Z	master	88	
-documentation	2026-09-02T02:38:17Z	master	1	LILYGO Documentation Site: https://wiki.lilygo.cc/
-T-Display-Bar	2026-04-07T02:04:37Z	master	7	Equipped with esp32s3, a 2.25-inch screen, BHI260AP 6-axis AI sensor, and a buzzer
-LilyGo-LoRa-Series	2026-08-28T02:48:29Z	master	983	LILYGO LoRa Series examples
-T-C5-Base	2026-08-22T06:55:24Z	master	0	
-TTGO-T-Display	2025-02-20T08:56:26Z	master	1192	
-LilyGO-T-ETH-Series	2026-06-01T02:15:56Z	master	226	
-T-Echo-Card	2026-08-31T10:05:36Z	main	16	
-LilyGoLib	2026-08-11T01:12:57Z	master	136	T-Watch Ultra &  T-LoRa-Pager & T-Watch-S3 & T-Watch-S3-Plus
-T-Dongle-S3	2026-07-24T03:51:10Z	main	412	An ESP32S3 development board that can freely use WIFI, BLE, TF, LED, TFT_LCD functions.
-LilyGo-AMOLED-Series	2026-05-06T02:31:43Z	master	226	LilyGo AMOLED Series
-LilyGo-Display-IDF	2025-11-03T01:07:57Z	master	69	This project is an esp-idf sample repository for the LilyGo display family.
-LilyGo-EPD47	2026-08-19T01:19:03Z	esp32s3	560	
-Lilygo-T-Pico2	2025-03-28T02:50:30Z	master	26	2.33-inch screen development board with RP2350 and esp32c3
-LilyGo-T-SIM7080G	2026-08-27T06:27:20Z	master	136	
-LilyGo-T-SIM7080G-MicroPython	2025-09-17T10:03:47Z	main	3	
-T-Panel	2026-08-20T02:54:52Z	main	36	 This is an RGB screen with a pixel resolution of 480x480, featuring dual chips on board, ESP32S3 and ESP32H2 chips, supporting 7-24V voltage input, RS485 communication, and more.
-T-Glass-V3	2026-08-28T05:55:06Z	master	0	
-T7-C6	2026-04-23T09:46:45Z	main	6	
-T-Echo	2026-07-17T08:30:12Z	main	233	
-T-Impulse-Plus	2026-08-24T07:29:26Z	main	5	
-T-HMI	2026-05-20T04:02:15Z	master	59	
-T-Lora-Dual	2025-12-31T07:30:20Z	master	19	two LR1121, LED, ExpressLRS
-T-Display-SF32	2026-08-20T03:26:06Z	master	1	
-T-PicoC3	2024-01-18T03:35:18Z	main	185	
-T-Embed	2026-04-27T05:43:14Z	main	262	
-T-Display-S3-AMOLED	2024-08-09T06:52:33Z	main	182	An upgraded version of T-Display-S3. It has a high-resolution color screen and more configurable GPIO ports. Enrich your needs.
-T-QT	2026-04-13T01:56:10Z	main	149	
-T7-S3	2023-08-23T06:07:20Z	main	37	ESP32-S3 Development Board
-LilyGo-T5-Grayscale	2025-05-20T03:31:12Z	master	9	
-T-Dongle-C5	2026-08-17T03:04:18Z	master	31	ESP32C5 + LED + TF + LCD + USB
-T-Display-K230-nRF52840	2026-08-23T07:04:03Z	master	0	
-lilygo-assistant-skill	2026-07-20T09:45:41Z	master	3	
-lilygo-micropython	2023-07-12T22:28:57Z	master	127	Micropython for LILYGO boards
-T-keyboard	2024-01-06T06:35:52Z	main	88	mini ble Keyboard for IOS/Android/Windows
-telink-zigbee-sdk	2022-11-14T05:53:42Z	master	5	
-SlFli-SDK-Lilygo	2026-08-21T06:53:31Z	master	0	
-T-Deck-MAX	2026-06-18T04:13:00Z	master	18	
-LilyGo-T5-Epaper-Series	2026-07-22T02:57:40Z	master	227	
-T7-C5	2026-01-20T06:18:09Z	master	3	ESP32-C5 development board
-T-Display-S3-Long	2026-06-15T05:48:18Z	T-Display-S3-Long-cst3530	80	
-T3-S3-MVSRBoard	2026-01-12T04:14:31Z	main	26	The T3-S3-MVSRBoard is the backplate design for the T3-S3_V1.2 motherboard, featuring onboard speaker and microphone expansion with extremely low static current. Additionally, it includes vibration and RTC (Real-Time Clock) functions.
-LilyGo-T-PCIE	2025-03-25T03:00:31Z	master	108	
-RFID-UHF-reader	2021-10-29T02:59:07Z	main	28	MagicRF M100/QM100
-T5-E-Paper-Basic	2026-08-19T09:03:21Z	master	1	
-lilygo-linux-dtoverlays	2026-08-19T08:54:02Z	master	0	
-T-Knob	2025-02-17T07:05:45Z	master	19	
-LilyGo-Cam-ESP32S3	2026-04-01T02:59:12Z	master	80	
-LilyGO-T-Wristband-and-T-Glass	2024-12-24T07:10:12Z	master	81	
-LilyGo-EPD-4-7-OWM-Weather-Display	2024-04-02T09:55:28Z	main	99	Using the LilyGo EPD 4.7" display to show OWM Weather Data
-VGA32	2022-09-04T03:24:01Z	master	44	ESP32 Display Controller (VGA, PAL/NTSC Color Composite), PS/2 Mouse and Keyboard Controller, Graphics Library, Sound Engine, Game Engine and ANSI/VT Terminal
-T-Display-C5	2026-08-17T06:17:39Z	master	2	The LilyGO T-Display-C5 is a development board based on the ESP32-C5, featuring a 1.9-inch ST7789 LCD touchscreen, an AXP2602 power management chip, and a CST816S capacitive touch controller. It supports wake-up from deep sleep via button (IO0) and I2C (IO2, IO3).
-T-Circle-S3	2026-06-12T02:49:48Z	arduino-esp32-libs_V2.0.14	33	T-Circle-S3 is a development board with a 0.75-inch onboard small screen developed based on the ESP32S3, equipped with a speaker, microphone, and three-color LED lights. It has six programmable input/output IO ports on the back, which can be expanded to connect a variety of peripherals.
-T-Wristband	2023-03-27T02:39:37Z	master	321	DIY Programmable Bracelet
-T-Display-K230-nRF9151	2026-08-14T03:17:12Z	main	0	
-T-Halow-RJ45	2026-06-26T07:10:40Z	main	6	
-T-Deck-Pro	2026-08-11T09:01:39Z	master	116	
-T-Energy-S3	2026-04-24T05:35:45Z	main	22	
-T-Display-S3-AMOLED-1.43-1.75	2026-06-17T01:56:39Z	main	34	T-Display-AMOLED-1.43-1.75 is a development board featuring a high-definition AMOLED display with a circular shape, based on the ESP32S3, designed for standalone battery connectivity.
-LilyGo-T-Pico2-MicroPython	2026-08-13T06:38:05Z	main	0	
-T-01C3	2022-01-14T08:43:35Z	main	25	
-TTGO_TWatch_Library	2026-01-08T06:12:31Z	master	1069	
-T-Track	2026-08-12T02:57:07Z	main	12	
-LilyGo-HiGrow	2026-06-22T08:07:50Z	master	137	https://pt.aliexpress.com/item/32815782900.html
-T-Panle-P4	2026-08-11T07:23:34Z	master	0	
-LilyGo-T-Call-SIM800	2025-10-25T02:25:49Z	master	542	
-T-Motor	2026-08-10T06:25:24Z	main	24	
-T-Echo-Lite	2026-08-10T01:36:48Z	main	15	
-T-MixRF	2026-05-08T02:49:17Z	main	4	
-esp-claw	2026-09-02T10:01:05Z	master	1	ESP-Claw, a "Chat Coding" AI agent framework for IoT devices
-LilyGo-Esp-Claw	2026-08-08T08:42:35Z	main	6	
-T-Internet-COM	2023-05-24T02:18:37Z	main	65	
-LilyGoLib-PlatformIO	2025-11-04T07:28:07Z	master	14	
-T-SIM7600X	2025-08-09T06:15:27Z	master	169	
-LilyGo-Document	2024-04-18T06:21:58Z	master	56	
-esp32-camera-screen	2019-11-28T06:39:31Z	master	91	TTGO T-camera Plus
-T-FPGA	2026-06-01T09:29:34Z	main	82	The circuit board is an integrated ESP32S3 and FPGA (GW1NSR-LV4CQN48PC6/I5) control chip. With the power management AXP2101 can be used to switch the voltage of different BANK areas.
-T-Vending	2026-03-17T02:43:54Z	master	10	
-CH9102_Driver	2022-04-27T01:30:27Z	main	41	
-T-CameraPlus-S3	2026-07-31T02:47:08Z	arduino-esp32-libs_V2.0.14	32	 T-CameraPlus-S3 is an intelligent camera module developed based on the ESP32S3 chip, equipped with a 240x240 TFT display, digital microphone, speaker, one independent button, power control chip, and SD card module.
-lilygo-skills	2026-07-29T11:27:35Z	main	4	A skill runtime for AI-assisted LilyGO board development.
-LilyGo-T-Relay	2026-03-30T01:53:09Z	main	87	
-LilyGO-T-DisplayGD32	2021-09-08T08:14:38Z	master	41	LilyGo GD32
-LilyGo-display-library	2026-07-27T07:03:28Z	main	0	
-LilyGo_Txx	2024-07-17T02:54:51Z	master	76	LilyGo T4 and T10 test code
-LilyGO-T-SIM7000G	2025-08-09T06:20:02Z	master	336	LilyGO T-SIM7000G
-FastEPD	2025-08-31T16:26:14Z	main	1	Optimized library for driving parallel eink displays with the ESP32
-T-TWR	2025-08-05T03:59:33Z	master	142	Programmable walkie-talkie.
-T-Display-S3-AMOLED-1.64	2026-07-22T03:38:11Z	arduino-esp32-libs_V2.0.14	18	
-lilygo-doc-mcp	2026-07-21T02:48:57Z	master	0	
-tlorapager-claude-os	2026-07-20T01:24:34Z	main	0	
-T-Panel-Lite	2026-07-17T05:51:00Z	main	3	T-Panel_ Lite is a streamlined version of T-Panel
-LilyGo-T-OI-PLUS	2023-03-29T08:30:17Z	main	80	esp32-c3 development board with 16340 battery holder
-LilyGoLib-MicroPython	2026-03-17T02:54:17Z	main	11	
-T-Weigh	2022-01-19T09:35:03Z	main	9	
-T-Encoder-Pro	2026-06-24T03:31:42Z	arduino-esp32-libs_V3.0.7	51	 T-Encoder-Pro is a smart control knob equipped with a AMOLED screen, developed based on the ESP32S3R8 chip, which is controlled by a dial.
-T3-STM32	2026-07-08T02:50:47Z	master	5	
-T-Keyboard-S3-Pro-Library	2026-06-30T08:52:35Z	master	0	
-LilyGo-Camera-Series	2026-04-02T01:41:08Z	master	175	🔰 Compatible with all TTGO camera products
-T-Connect	2026-02-24T01:26:24Z	main	11	T-Connect is a board with four different sets of module output data. It supports the mutual switching between two different modules, CAN and RS485. It can support up to three groups of RS485 and one group of CAN bus to output different data.
-T-Watch-2021	2025-10-28T08:04:10Z	main	87	
-T-Dongle-ESP32S2	2023-04-01T09:35:28Z	main	24	
-T-Keyboard-S3-Library	2026-06-22T08:55:51Z	master	0	
-esp32-oled-sh1106	2022-04-01T08:19:32Z	master	7	Driver for the SSD1306 and SH1106 based 128x64, 128x32, 64x48 pixel OLED display running on ESP8266/ESP32
-T-Display-S3-Pro-MVSRBoard	2026-06-16T01:10:32Z	main	5	The T-Display-S3-Pro-MVSRBoard is the backplate design for the T-Display-S3-Pro motherboard, featuring onboard speaker and microphone expansion with extremely low static current. Additionally, it includes vibration and RTC (Real-Time Clock) functions.
-LilyGoLib-ThirdParty	2026-06-13T07:04:48Z	master	1	
-Lilygo-LoRa-Epaper-series	2025-12-26T03:35:07Z	master	8	
-LilyGo-T-RGB	2025-06-26T02:56:49Z	main	100	
-T-Bao	2026-06-09T06:32:05Z	main	0	
-T-Spe	2026-06-05T08:58:55Z	main	1	
-T-Display-S3-Pro-MVSRLora	2026-04-29T03:05:50Z	main	5	The T-Display-S3-Pro-MVSRLora is the backplate design for the T-Display-S3-Pro motherboard. It includes onboard speaker and microphone expansion, featuring extremely low static current. Additionally, it offers functionalities such as vibration, RTC (Real-Time Clock), and LoRa.
-TTGO-LoRa-Series	2020-07-26T12:07:30Z	master	191	TTGO Lora  Test code
-T-Connection-P4-Pro	2026-05-22T02:48:09Z	main	0	The main control is ESP32P4 MCU, while the slave is ESP32C6. It is equipped with RS485/RS232, network port, LoRa, relay, GPS, ADC current detection, and 8 optocoupler input ports.
-LilyGo-esp32s2-base	2021-01-16T07:08:47Z	master	37	
-LilyGo-W5500-Lite	2020-12-09T02:47:22Z	master	20	
-T-Connect-Pro	2026-03-16T02:47:30Z	main	15	T-Connect-Pro is a product based on the ESP32S3 microcontroller, consisting of three stacked circuit boards.
-T-HiGrow-Dashboard	2019-12-24T02:31:10Z	master	10	
-T-ZigBee	2023-03-06T00:54:37Z	main	85	Zigbee Ultra Low Power IOT Development Board
-LilyGo-T-PicoPro	2024-07-10T02:23:05Z	master	15	
-T-RSC3	2025-12-23T07:25:55Z	main	22	
-LilyGo-K210-Script	2025-09-29T09:22:03Z	master	6	
-T-Camera	2019-04-22T02:28:54Z	master	9	OV2640 V16
-ESP32_S2	2023-11-20T07:33:58Z	main	16	
-T-Keyboard-S3	2025-04-01T04:18:16Z	main	31	A Smart Screen Keyboard Based on ESP32s3
-LilyGO-T-Motion	2021-11-16T08:45:39Z	master	12	LilyGO-T-Motion
-Wrist-E-Paper	2025-11-27T02:05:31Z	main	35	
-T5-Ink-Screen-Series	2021-12-18T09:36:49Z	master	165	TTGO T5 V2.2 ESP32 2.9“EPaper Plus
-LILYGO-T-display-RP2040	2023-11-23T03:27:59Z	main	87	
-TTGO-T-Watch	2019-10-10T09:23:27Z	master	116	Obsolete, please visit https://github.com/Xinyuan-LilyGO/TTGO_TWatch_Library
-T8-S3	2025-09-29T09:13:05Z	main	6	
-LILYGO-T8	2025-05-13T05:49:58Z	main	6	
-LilyGO-Mini-Epaper-S3	2025-07-12T06:07:58Z	main	3	
-Launchpad	2026-03-03T06:27:34Z	main	0	LILYGO web flash tool
-T-Micro32-Series	2024-06-12T09:21:12Z	main	9	
-T-Encoder	2022-06-24T10:07:49Z	main	15	
-Meshtastic-Python	2024-11-24T19:44:41Z	master	2	The Python CLI and API for talking to Meshtastic devices
-CH9102_Mac_Driver	2022-03-29T05:44:39Z	main	5	
-Meshtastic_firmware	2024-11-26T04:49:13Z	master	3	Meshtastic device firmware
-T-0.99TFT	2023-04-08T03:03:01Z	main	11	
-T-HC32	2022-09-09T06:33:03Z	main	16	
-T-Impulse	2022-06-24T02:06:12Z	master	57	Wristband with LoRa and GPS
-LilyGo-HAL	2021-02-01T02:37:50Z	master	17	
-LilyGO-Mini-Epaper	2024-08-21T03:34:11Z	main	17	
-T-A7608X	2023-11-16T07:13:30Z	main	23	
-T-Touch_Bar	2023-11-23T03:22:22Z	main	22	
-LilyPi	2023-06-10T08:18:13Z	main	8	
-T-Display-keyboard	2023-06-26T09:34:17Z	main	9	
-SoftRF	2021-06-22T17:57:12Z	master	4	:airplane:  Multifunctional, compatible DIY general aviation proximity awareness system
-esp32-camera-plus-bigiot	2019-03-12T10:57:52Z	master	33	Use TTGO-Camera-Plus to upload captured images to the BIGIOT platform every 10 seconds
-esp-gitee-tools	2025-08-20T09:32:55Z	main	1	
-My-TTGO-Watch	2020-07-10T07:49:50Z	master	4	Firmware for a smartwatch based on ESP32 from LilyGo.
-T-Touchbar-AMOLED	2025-09-22T02:33:30Z	master	9	
-micropython	2025-10-27T02:25:18Z	main	0	
-LilyGo-T-Wristband-NRF52	2023-10-27T09:51:40Z	master	26	
-T-Watch-Deps	2024-11-19T03:15:40Z	master	5	
-T-Connect-Pro-MicroPython	2025-08-20T10:07:48Z	main	0	T-Connect-Pro is a product based on the ESP32S3 microcontroller, consisting of three stacked circuit boards.
-esp-idf	2025-08-20T10:06:21Z	main	0	
-LilyGO-Mini-E-paper-S3	2025-04-26T02:20:09Z	main	2	
-LilyGO-ETH-Gateway	2024-07-08T01:03:39Z	master	2	
-Ka-Radio32	2020-03-09T01:59:19Z	master	7	esp32 version of Ka-Radio (https://github.com/karawin/Ka-Radio)
-T96-OLED-SSD1306	2021-12-15T09:47:26Z	main	7	
-tbeam-helium-mapper	2024-06-26T16:15:37Z	main	16	
-T8-C3	2024-12-04T06:25:54Z	main	12	
-T-GlassV2	2025-01-07T03:55:33Z	master	1	T-GlassV2 comprehensive examples
-T-Circle	2024-08-27T09:08:30Z	master	1	
-Q445	2024-12-02T01:55:43Z	main	1	
-Meshtastic-Web	2024-11-24T22:16:25Z	master	2	Meshtastic Web Client
-Meshtastic-Apple	2024-11-26T00:10:51Z	main	4	Apple iOS, iPadOS & macOS Clients For Meshtastic
-Meshtastic-Android	2024-11-25T23:09:53Z	master	1	Android application for Meshtastic
-Meshtastic	2024-11-25T22:44:10Z	master	1	Meshtastic project website and documentation
-LilyGo-TTV	2025-02-15T08:14:20Z	master	21	
-LILYGO-T-TWR-Plus-case	2023-07-04T19:36:08Z	main	4	3D model and case for the LILYGO T-TWR Plus (https://www.lilygo.cc/products/t-twr-plus)
-MicroPython_ESP32_psRAM_LoBo	2023-01-12T08:52:59Z	master	5	MicroPython for ESP32 with psRAM support
-LilyGo-eink-v2.3-micropython	2020-06-09T01:53:41Z	master	12	
-DabbleESP32	2019-12-03T05:42:00Z	master	8	DabbleESP32 is library for using Dabble app with ESP32. It uses BLE of ESP32 for communicating with the app. The app consists virtual modules that help in accessing certain features of smartphone via hardware and helps in providing hardware control via smartphone. 
-twatch-series-modules	2019-08-09T09:04:44Z	master	15	
-T-U2T	2022-04-12T02:35:41Z	main	13	
-EPD47-HC08	2021-06-07T01:53:14Z	main	7	
-T-SimHat	2023-05-13T06:32:40Z	main	1	
-T-WATCH-Keyboard	2023-07-26T06:28:28Z	main	6	
-esp32-face-recognition	2019-02-15T03:10:38Z	master	44	TTGO T-Câmera
-SX1302_HAL_GATEWAY	2022-11-29T03:29:20Z	master	6	
-3.71-Inch-Capacitive-Touch-E-Paper	2021-11-24T09:12:58Z	main	4	
-T5-ePaper-NewPanel	2020-12-28T09:44:07Z	master	6	
-T-Encoder-shield	2023-02-03T01:33:06Z	main	8	Customize Macro Keys and APA102 RGB Full Color LED light.
-TTGO_Camera_Mini	2021-10-27T06:29:27Z	master	25	TTGO_Camera_Mini
-CubOS	2022-02-02T20:36:01Z	main	1	
-TTGO_T_Watch_Baidu_Rec	2019-08-11T06:47:24Z	master	4	用 TTGO_T_Watch 手表做的百度语音识别终端
-MaixPy	2022-05-11T03:35:27Z	master	5	MicroPython for K210 RISC-V, let's play with edge AI easier
-TTGO-Camer-Mic	2019-10-07T01:20:43Z	master	13	TTGO Camera Microphone version
-LilyGo-TWR-Library	2024-03-19T11:00:09Z	master	0	LilyGo-TWR project dependent libraries
-LilyGO-SIM7000-Cayenne	2020-02-25T07:00:50Z	master	2	The code was moved to sim7000g master 
-S76G_GPS_Firmware	2020-06-16T03:20:43Z	master	3	
-LilyGo-OLED	2021-04-14T00:54:55Z	master	2	
-T-Watch-2021-lvgl	2023-05-31T07:19:51Z	master	2	
-CH340K_Driver	2023-05-08T03:12:20Z	main	4	
-LilyGo-HeartRate-Kit	2020-08-19T06:51:45Z	master	22	
-ESP32-Paxcounter	2022-01-05T08:31:11Z	master	6	Wifi & BLE driven passenger flow metering with cheap ESP32 boards
-S7xG	2020-04-19T13:29:48Z	master	2	HAB Firmware for the S7xG board in the LilyGo Watch, to provide basic GPS and LoRa for UKHAS telemetry
-open-smartwatch-os	2021-04-28T06:16:48Z	master	7	The Open-Smartwatch Operating System.
-T-NixieTube	2021-06-05T06:32:04Z	main	5	
-arduino-nofrendo	2020-11-03T00:56:07Z	master	3	Clone from source http://www.baisoku.org/nofrendo-2.0pre1.zip
-LilyGO-TM	2023-04-24T09:08:39Z	master	0	
-Adafruit_nRF52_Bootloader	2021-05-10T08:32:01Z	master	1	USB-enabled bootloaders for the nRF52 BLE SoC chips
-T-solar	2019-12-24T06:32:36Z	master	10	
-netdisk	2022-06-23T03:28:13Z	master	0	
-T-Color	2022-06-20T06:11:44Z	main	0	
-Document_List	2021-12-15T01:52:27Z	main	1	
-ESP_AT_Lib	2021-12-22T05:00:43Z	master	1	An ESP8266/ESP32 wrapper library for Arduino providing an easy-to-use way to manipulate ESP8266/ESP32-AT shields.
-WiFiEspAT	2022-01-05T14:01:23Z	master	0	Arduino networking library. Standard Arduino WiFi networking API over ESP8266 or ESP32 AT commands.
-T-Watch-2019-reissue-peak	2021-11-06T08:31:15Z	main	0	
-Twatch-example	2019-11-20T02:17:05Z	master	4	
-T-Block	2021-10-11T08:39:19Z	main	0	T-Block/T-Block-V1
-GxEPD	2021-09-30T08:49:52Z	master	1	A simple E-Paper display library with common base class and separate IO class for Arduino.
-3d-files	2021-04-27T14:45:46Z	master	1	3D printable design files. Sources as well as stl
-bbq10kbd_i2c_sw	2020-07-16T05:43:45Z	master	1	
-LilyGo-T-Node	2021-02-26T01:24:31Z	master	4	
-open-smartwatch-light	2021-04-09T11:01:35Z	main	0	Hardware design files. Light version (no GPS, no uSD) of the open-smartwatch
-MAX7219LedMatrix	2018-08-02T20:49:35Z	master	3	Library for the ESP8266 on Arduino IDE displaying text on multiple 8x8 led matrices
-TTCar_3D_Model	2019-10-22T10:21:53Z	master	8	
-LilyGo-T-Controlle	2021-01-03T04:00:35Z	master	1	
-Maixduino	2019-11-20T13:35:19Z	master	2	Arduino port on Maix board ( k210 )
-arduino-dw1000	2020-11-20T07:54:31Z	master	0	A library that offers functionality to use Decawave's DW1000 chips/modules with Arduino.
-T_Watch_Game	2020-05-23T10:44:36Z	master	1	GAME1.Tic Tac Toe
-esp32-soil-dash	2019-02-16T02:07:46Z	master	5	Higrow ESP32 Rev1
-sx1302_hal	2020-08-05T07:26:47Z	master	0	SX1302 Hardware Abstraction Layer and Tools (packet forwarder...)
-THABWatch	2020-04-22T09:38:19Z	master	0	TTGO T-Watch HAB Firmware for receiving and chasing LoRa balloons
-TTGO_T_Watch_See_Camera	2020-05-23T06:01:52Z	master	0	TTGO_T_Watch_See_Raspberry pi Camera  
-T-Quick	2019-10-22T07:33:42Z	master	2	
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf b/devices/lilygo/t-display-s3-shared/artifacts/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf
deleted file mode 100644
index db99918..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/schematic/T_Display_S3.pdf b/devices/lilygo/t-display-s3-shared/artifacts/schematic/T_Display_S3.pdf
deleted file mode 100644
index 318cc4f..0000000
Binary files a/devices/lilygo/t-display-s3-shared/artifacts/schematic/T_Display_S3.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h b/devices/lilygo/t-display-s3-shared/artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h
deleted file mode 100644
index 734d222..0000000
--- a/devices/lilygo/t-display-s3-shared/artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h
+++ /dev/null
@@ -1,48 +0,0 @@
-// ST7789 using 8-bit Parallel
-
-#define USER_SETUP_ID 206
-
-#define USE_HSPI_PORT
-#define ST7789_DRIVER
-#define INIT_SEQUENCE_3 // Using this initialisation sequence improves the display image
-
-#define CGRAM_OFFSET
-#define TFT_RGB_ORDER TFT_RGB  // Colour order Red-Green-Blue
-//#define TFT_RGB_ORDER TFT_BGR // Colour order Blue-Green-Red
-
-#define TFT_INVERSION_ON
-// #define TFT_INVERSION_OFF
-
-#define TFT_PARALLEL_8_BIT
-
-#define TFT_WIDTH 170
-#define TFT_HEIGHT 320
-
-#define TFT_CS  6
-#define TFT_DC  7
-#define TFT_RST 5
-
-#define TFT_WR 8
-#define TFT_RD 9
-
-#define TFT_D0 39
-#define TFT_D1 40
-#define TFT_D2 41
-#define TFT_D3 42
-#define TFT_D4 45
-#define TFT_D5 46
-#define TFT_D6 47
-#define TFT_D7 48
-
-#define TFT_BL 38
-#define TFT_BACKLIGHT_ON HIGH
-
-#define LOAD_GLCD
-#define LOAD_FONT2
-#define LOAD_FONT4
-#define LOAD_FONT6
-#define LOAD_FONT7
-#define LOAD_FONT8
-#define LOAD_GFXFF
-
-#define SMOOTH_FONT
diff --git a/devices/lilygo/t-display-s3-shared/board-revision-drift.md b/devices/lilygo/t-display-s3-shared/board-revision-drift.md
deleted file mode 100644
index 88a1ea0..0000000
--- a/devices/lilygo/t-display-s3-shared/board-revision-drift.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# LilyGO board-revision drift — what changes under one name, and how to tell
-
-> Family-level. Snapshot **2026-09-07**. This is the document to read before trusting *any*
-> pin map, schematic or photograph for a LilyGO board you have not physically identified.
-
-## The problem, stated plainly
-
-LilyGO revises boards without renaming them, without incrementing a visible revision, and
-without withdrawing the old schematic. There is no changelog, no ECN, no revision field on most
-silkscreens. The result is that "T-Display-S3" and "T-Display-S3 AMOLED" each name **a set of
-boards**, and code that works on one member can fail on another.
-
-This is not a criticism that requires inference — LilyGO **sells two revisions of the same
-product side by side in the same dropdown** (see R2 below), which is the clearest possible
-admission that the name does not identify the hardware.
-
-## Evidenced revisions
-
-Ordered by how likely you are to be bitten.
-
-### R1 — T-Display-S3 Touch: **CST816S → CST328**
-
-| | |
-|---|---|
-| **Boards** | T-Display-S3 Touch (`H587`, `H589`) |
-| **What changed** | The bonded touch controller. **CST816S** is *self*-capacitance, I²C `0x15`. **CST328** is *mutual*-capacitance, I²C `0x1A`, and supports more simultaneous points |
-| **Evidence** | The board repo `Xinyuan-LilyGO/T-Display-S3` @ `ec889e7` ships **both** datasheets in `datasheet/`: `CST816S寄存器说明-20190508.pdf` (76 816 B) and `CST328数据手册V2.2.pdf` (1 297 291 B). A board with one controller does not need two register manuals |
-| **Second evidence** | `platformio.ini` @ `ec889e7` carries `-DTOUCH_MODULES_CST_MUTUAL` in the shared `[env]` — i.e. the vendor's *current default build* selects the **mutual**-capacitance (CST328) driver branch |
-| **How to tell them apart without opening anything** | Scan I²C on GPIO17/18. `0x15` → CST816S. `0x1A` → CST328 |
-| **What breaks** | A sketch built with `-DTOUCH_MODULES_CST_SELF` (or an older LilyGO example) finds no touch controller on a new board, and vice versa. This is the mechanism behind [issue #125 "no Touch IC found"](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/125) (15 comments) |
-| **Date bounds** | CST816S register guide is dated 2019; the CST328 datasheet is V2.2. LilyGO never announced the switch, so the changeover date is **unknown** |
-
-### R2 — T-Display-S3 AMOLED 1.91″: **V1.0 and V2.0 sold concurrently**
-
-| | |
-|---|---|
-| **Evidence** | LilyGO's own store feed, retrieved 2026-09-07, offers under the single handle `t-display-s3-amoled`: `H619` "V1.0 Non-Soldered Pin", `H634` "V1.0 Soldered Pin", `H713` "V2.0 Non-Soldered Pin", `H712` "V2.0 Soldered Pin" — **all four in stock at the same time**, plus separate `H681`/`H705`/`H717` "Touch" SKUs |
-| **What changed** | Not stated by LilyGO anywhere. Comparing the two schematics LilyGO publishes for this board strongly suggests a power-section redesign: `T-DISPLAY-S3-AMOLED.pdf` (in the older `T-Display-S3-AMOLED` repo) shows `U4 = RT9080` LDO, `U6 = BV6802`, `U3 = W25Q32`; `T-Display-S3-AMOLED-Touch.pdf` (in `LilyGo-AMOLED-Series`) shows `U4 = SY8089A1AAC` **buck**, `U5 = AXPM65611`, `U3 = W25Q128JV` |
-| **How to tell** | Read the silkscreen; these boards do carry `V1.0`/`V2.0`. Failing that, `esptool.py flash_id` distinguishes 4 MB from 16 MB |
-| **What breaks** | Anything assuming 16 MB flash on a V1.0 built to the older sheet; any current-consumption assumption (LDO vs buck) |
-| **Status** | **Unresolved.** LilyGO publishes no V1→V2 delta. Recorded as conflict F3 in the [family README](README.md#4-family-level-conflicts) |
-
-### R3 — T-Display-S3 base: **the charger does not match the schematic**
-
-| | |
-|---|---|
-| **Evidence — schematic** | `schematic/T_Display_S3.pdf`, title block **2024-04-29**, shows `U6 = TP4065` with a `PROG` pin and a 2 kΩ program resistor `R9`; a sheet note reads `R13  IBAT (mA) = 580` |
-| **Evidence — hardware** | [Issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230), 2024-03-02, an owner tracing a physical PCB: *"when I try to find the TP4056 on the PCB it cannot be found? … Tracing out the PCB I find that the charging IC appears to be a device that is a **5-Lead TSOT-23 package with the marking of `65b311`** printed on top. This does not agree with the posted schematic."* Evidence class: **firsthand physical inspection** |
-| **Third data point** | Three AMOLED schematics carry a part LilyGO spells **`AXPM65611`**. The shared `65611`/`65b311` fragment is suggestive but **not proof** |
-| **Practical consequence** | The published charge-current programming procedure (swap `R9` for 10 kΩ to get ~130 mA) is derived from a TP4056/TP4065 datasheet that may not describe the fitted part. **Do not modify the charge resistor on the strength of the schematic alone** |
-| **Status** | **Unresolved.** The part was never identified — [`components/unidentified/lilygo-t-display-s3-family/axpm65611/`](../../../components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md) records what would settle it |
-
-### R4 — T-Display-S3 base: **GPIO16/17 pull-ups fitted on non-touch boards**
-
-| | |
-|---|---|
-| **Evidence** | [Issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313), 2025-07-28. LilyGO maintainer `lewisxhe` posted **two photographs of the PCB back showing the resistors** and wrote: *"Pull-up resistors are already added to the 16 and 17 boards, so when you set it to floating, it's pulled high by default… If you must use these two GPIOs, you can remove these two resistors."* The reporter confirmed a **non-touch** board |
-| **How to tell** | Measure GPIO16/GPIO17 to 3V3 with the board unpowered, or look at the back of the panel |
-| **What breaks** | Any use of GPIO16/17 as a clean input or a low-side driver; and the pins go high again the moment you enter deep sleep |
-| **Status** | **Confirmed by vendor.** Whether *all* production runs fit them is not established |
-
-### R5 — T-Display-S3 Long: **CST3530 touch appears mid-life, in a branch**
-
-| | |
-|---|---|
-| **Evidence** | The `T-Display-S3-Long` repo's **default branch is `T-Display-S3-Long-cst3530`**, not `main` or `master`. It ships `firmware/factory.bin` **and** `firmware/factory-cst3530.bin` as separate images, and `examples/cst3530_touch/` alongside the original touch example |
-| **Reading** | The original Long used the AXS15231B's **integrated** touch. A later run adds/substitutes a discrete **Hynitron CST3530**. LilyGO handled it by making the CST3530 branch the default rather than merging |
-| **How to tell** | Flash `factory.bin`; if touch does not respond, flash `factory-cst3530.bin` |
-| **Status** | Evidenced by repository structure. No vendor statement located |
-
-### R6 — T-Display-S3 Pro: **V1.0 vs V1.1 backlight driver**
-
-| | |
-|---|---|
-| **Evidence** | `examples/factory/utilities.h` @ `08b8b2b`, verbatim: `//! Using T-Display-Pro V1.0 , uncomment use V1.1 , //! The difference between V1.0 and V1.1 is the backlight driver.` followed by `#ifdef USING_DISPLAY_PRO_V1 / #define BRIGHTNESS_MAX_LEVEL 255 / #else / #define BRIGHTNESS_MAX_LEVEL 16 / #endif` |
-| **What changed** | The backlight brightness scale — **255 levels on V1.0, 16 on V1.1**. Firmware built for the wrong one is 16× off |
-| **Second evidence** | The repo ships `firmware/v1.0/` and `firmware/v1.1/` as separate directories |
-| **How to tell** | Try the V1.1 firmware; and see the schematics — the Pro repo carries `T-BHI260.pdf` *and* `T-BHI260_V1.1.pdf` |
-| **Status** | **Vendor-documented, in a source comment only.** This is the clearest example of the pattern: a real, breaking revision documented nowhere but a `//!` comment |
-
-### R7 — T-Display-S3 Pro: **two different IMU daughter-boards**
-
-The Pro repo ships schematics for both `T-BHI260.pdf` (Bosch BHI260AP) and `T-ICM29048.pdf`
-(TDK ICM-20948-class), plus `kicad_sensor.pretty/T-BHI260.kicad_mod` and
-`T-CIM29048.kicad_mod`. Firmware named `UnitTest_V1.1_DisChg_BHI260_241111.bin` exists.
-**The sensor fitted to your Pro is not determined by the product name.** Scan I²C.
-
-### R8 — The 1.43/1.75″ AMOLED: **three panels, one product page**
-
-Store handle `t-display-s3-amoled-1-64` sells four things: `H708` 1.64″, `H741` 1.43″,
-`H741-01` 1.75″, `H741-02` 1.75″ half-circle convex mirror. Two repos cover them. The display
-controllers differ (**CO5300/ICNA3311** vs **SH8601**) *and* the touch controllers differ
-(**FT3168** vs **CST9217**). Selection is by `CONFIG_SCREEN_TYPE_*` Kconfig symbol —
-`DO0143FMST10` (1.43″, CO5300+FT3168), `DO0143FAT01` (1.43″, SH8601+FT3168),
-`H0175Y003AM` (1.75″, CO5300+CST9217) — and the header `#error`s if you pick none.
-Source: `components/private_library/pin_config.h` @ `87aabe8`.
-
-## How to identify a board you are holding
-
-In increasing order of effort:
-
-1. **Silkscreen.** AMOLED 1.91″ and Pro do carry `V1.0`/`V1.1`/`V2.0`. The base T-Display-S3
-   does not.
-2. **`esptool.py flash_id`** — distinguishes 4 MB from 16 MB, and reports the USB VID/PID
-   (`303A:1001` for native USB-Serial-JTAG).
-3. **I²C scan on the board's I²C pins.** This is the single most informative test: it names the
-   touch controller (`0x15` CST816S · `0x1A` CST328 · `0x5A` CST226SE/CST3530 family ·
-   `0x38` FT3168) and, on PMIC boards, the charger (`0x6B` SY6970/BQ25896 · `0x34` AXP2101).
-4. **Flash the vendor factory image and see what it does.** LilyGO ships a
-   `t-display-s3-screen-detect` image for exactly this purpose.
-5. **Read the chip markings.** The definitive answer, and the only one that would have caught
-   R3.
-
-## What this means for anything written about these boards
-
-Every pin map, current figure and library recipe — including everything in this repository —
-is **valid for the revision it was derived from and no other**. Each record here states its
-commit and retrieval date for that reason. When a source does not state which board it saw,
-treat it as describing an unknown member of a set.
-
-## Cross-references
-
-- [Family README §4](README.md#4-family-level-conflicts) — the conflict register
-- [`guides/markets/clones-and-variants.md`](../../../guides/markets/clones-and-variants.md) —
-  the general method (read; not edited by this pass)
-- Per-board `gaps-and-conflicts.md` files
diff --git a/devices/lilygo/t-display-s3-shared/media/manifest-schematic-crops.json b/devices/lilygo/t-display-s3-shared/media/manifest-schematic-crops.json
deleted file mode 100644
index 1698b9d..0000000
--- a/devices/lilygo/t-display-s3-shared/media/manifest-schematic-crops.json
+++ /dev/null
@@ -1,71 +0,0 @@
-{
-  "$schema-note": "Image provenance manifest for images DERIVED from retained schematic PDFs by local rasterisation. Kept separate from media/manifest.json so that no pre-existing file is modified; an index owner may merge them.",
-  "device": "lilygo/t-display-s3-shared",
-  "generated": "2026-09-07",
-  "generator": "2026-09-07 schematic net-tracing pass; poppler 26.06.0 + ImageMagick",
-  "global_notes": [
-    "These are NOT photographs and NOT vendor-published images. Each is a crop of a page the vendor published as a vector PDF, rasterised locally at 300 dpi.",
-    "pdfimages could not be used: pdfimages -list reports ZERO embedded rasters in every source PDF here. The drawings are vector, so pdftoppm plus a crop is the only route. This is recorded because reaching for pdfimages is the obvious wrong first move.",
-    "Copyright in the underlying drawing remains with the vendor named in creator_rightsholder. Licence is UNKNOWN: no licence statement appears in any of the source PDFs. Redistribution status unknown; disposition repository, unstaged pending user review.",
-    "Every image is reproducible byte-for-byte from the retained artifact using the recorded generation_command, so none of them is uniquely held here.",
-    "Each image exists because it settles a specific documented question; see why_retained."
-  ],
-  "images": [
-    {
-      "local_path": "media/schematic-T_Display_S3-U6-tp4065-5pin.png",
-      "filename": "schematic-T_Display_S3-U6-tp4065-5pin.png",
-      "sha256": "b65530a7a7581822544d4b7a35dd19a916010e4eda97863312395318551c7856",
-      "bytes": 9717,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "LilyGO / Xinyuan Electronic Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/T_Display_S3.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export, llPDFLib 3.x, CreationDate 2024-04-29; 1 page, 792x612 pt; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 620x300+830+1935 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "620x300+830+1935",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "T-Display-S3 (base board), sheet as published by LilyGO",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: charger U6, part string TP4065, drawn with FIVE pins",
-      "alt_text": "Schematic detail showing a five-pin IC symbol labelled U6 / TP4065. Pin 4 VCC at top, pin 1 CHRG at left driving LED1 through R9 2K, pin 3 BAT at right, pin 5 PROG with R13 2K, pin 2 GND at bottom. A dashed note box to the right carries the rotated text 'IBAT (mA) = 580'.",
-      "why_retained": "Settles the charger package conflict: the schematic symbol has five pins, not SOP-8, matching the owner-reported 5-lead TSOT-23. Also shows the vendor's own 580 mA charge-current annotation."
-    },
-    {
-      "local_path": "media/schematic-T_Display_S3-P1-P2-headers.png",
-      "filename": "schematic-T_Display_S3-P1-P2-headers.png",
-      "sha256": "c749d36d7c86f68c426a688cb45bf288513221f14c80d475f78f11cb32d38dea",
-      "bytes": 9990,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "LilyGO / Xinyuan Electronic Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/T_Display_S3.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export, llPDFLib 3.x, CreationDate 2024-04-29; 1 page, 792x612 pt; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 700x270+1680+1420 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "700x270+1680+1420",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "T-Display-S3 (base board), sheet as published by LilyGO",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: the two 12-way headers P1 and P2 with their net labels",
-      "alt_text": "Schematic detail showing two twelve-pin header symbols side by side, each captioned 'Header 12'. P2's pins 11 to 5 carry net labels GPIO1, GPIO2, GPIO3, GPIO10, GPIO11, GPIO12, GPIO13; P1's pins 11 to 6 carry U0TXD, U0RXD, IIC_SDA, IIC_SCL, ESP_TP_RESET, ESP_TP_INT. Pins 4 and 3 of P2 and pin 4 of P1 carry X no-connect markers.",
-      "why_retained": "Fixes the label-to-pin binding for the header pinout, which the text layer alone leaves ambiguous at plus or minus 1.7 points: pin 12 of P2 runs unbroken to a VDD3V3 power port, which proves labels sit above their wire."
-    }
-  ]
-}
diff --git a/devices/lilygo/t-display-s3-shared/media/schematic-T_Display_S3-P1-P2-headers.png b/devices/lilygo/t-display-s3-shared/media/schematic-T_Display_S3-P1-P2-headers.png
deleted file mode 100644
index 7b7fe2e..0000000
Binary files a/devices/lilygo/t-display-s3-shared/media/schematic-T_Display_S3-P1-P2-headers.png and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/media/schematic-T_Display_S3-U6-tp4065-5pin.png b/devices/lilygo/t-display-s3-shared/media/schematic-T_Display_S3-U6-tp4065-5pin.png
deleted file mode 100644
index b1f5fa4..0000000
Binary files a/devices/lilygo/t-display-s3-shared/media/schematic-T_Display_S3-U6-tp4065-5pin.png and /dev/null differ
diff --git a/devices/lilygo/t-display-s3-shared/product-history-and-family.md b/devices/lilygo/t-display-s3-shared/product-history-and-family.md
deleted file mode 100644
index c6095dc..0000000
--- a/devices/lilygo/t-display-s3-shared/product-history-and-family.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# LilyGO T-Display-S3 family — history and lineage
-
-The dated timeline, the lineage diagram and the culture notes live in the base board's record,
-because that is where a reader arrives:
-**→ [`../t-display-s3/product-history-and-family.md`](../t-display-s3/product-history-and-family.md)**
-
-This page adds only what is genuinely family-scoped.
-
-## Launch order of the whole line
-
-| Listed | Board | Note |
-|---|---|---|
-| ~2019 | TTGO T-Display (ESP32) | the ancestor |
-| **2022-07-15** | **T-Display-S3** | the reference board |
-| 2022-11-12 | T-Display AMOLED **Lite** 1.47″ | **first AMOLED**, despite the name |
-| 2023-04-14 | T-Display-S3 AMOLED 1.91″ | |
-| 2023-09-07 | T-Display-S3 **Pro** 2.33″ | |
-| 2023-10-27 | T-Display-S3 **Long** 3.4″ | |
-| 2023-11-03 | **T4-S3** 2.41″ | not named T-Display-S3 |
-| 2024-07-18 | T-Display S3 AMOLED **(DS)** 1.43/1.64/1.75″ | four panels, one page |
-| 2024-10-31 | T-Display-S3 AMOLED **Plus** | |
-| 2025-11-28 | T-Display S3 Pro External | |
-
-Dates are LilyGO's own `published_at` from the store feed, retrieved 2026-09-07.
-
-## Repository health, 2026-09-07
-
-A useful proxy for how much you can rely on each board's software.
-
-| Repo | ★ | Forks | Open issues | Last push | Licence |
-|---|---|---|---|---|---|
-| `T-Display-S3` | **1 169** | 273 | **1** | 2026-08-31 | MIT |
-| `LilyGo-AMOLED-Series` | 226 | 57 | **1** | 2026-05-06 | MIT |
-| `T-Display-S3-AMOLED` | 182 | 36 | 1 | **2024-08-09 (dead)** | MIT |
-| `T-Display-S3-Long` | 80 | 23 | **25** | 2026-06-15 | **none** |
-| `T-Display-S3-Pro` | 63 | 17 | **22** | 2026-08-06 | **none** |
-| `T-Display-S3-AMOLED-1.64` | 18 | — | 1 | 2026-07-22 | GPL-3.0 |
-| `T-Display-S3-AMOLED-1.43-1.75` | 34 | — | — | 2026-06-17 | MIT |
-| `LilyGo-Display-IDF` | 69 | — | — | 2025-11-03 | MIT |
-
-**Read that table before choosing a board.** The base board and the AMOLED library are
-maintained to a closed-issue state; **Long and Pro carry 25 and 22 open issues** and declare
-**no licence at all**, which makes the redistribution status of their schematics and firmware
-unknown. `T-Display-S3-AMOLED` is dead — use `LilyGo-AMOLED-Series`.
-
-## Default branches are not `main`
-
-An enumeration trap worth stating once. Three of these repositories default to a branch that
-encodes a hardware or toolchain fact:
-
-| Repo | Default branch | What it means |
-|---|---|---|
-| `T-Display-S3-Long` | **`T-Display-S3-Long-cst3530`** | a touch-controller revision |
-| `T-Display-S3-AMOLED-1.64` | **`arduino-esp32-libs_V2.0.14`** | a pinned Arduino core |
-| `T-CameraPlus-S3`, `T-Circle-S3` | `arduino-esp32-libs_V2.0.14` | as above |
-| `T-Encoder-Pro` | `arduino-esp32-libs_V3.0.7` | a *different* pinned core |
-| `T5S3-4.7-e-paper-PRO` | `H752-01` | an SKU |
-
-**Always read `.default_branch` from the API; never assume `main`.** Recorded in
-[`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md).
diff --git a/devices/lilygo/t-display-s3-shared/research-log.md b/devices/lilygo/t-display-s3-shared/research-log.md
deleted file mode 100644
index bdb2d9e..0000000
--- a/devices/lilygo/t-display-s3-shared/research-log.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# T-Display-S3 family — research log (family-scoped)
-
-Snapshot **2026-09-07**. The detailed per-query ledger is in
-[`../t-display-s3/research-log.md`](../t-display-s3/research-log.md); this page records only
-what applies to the family as a whole.
-
-## Date discrepancy
-
-The task brief said 2026-09-04. The host clock said **2026-09-07 10:23 UTC**, and LilyGO's
-product feed independently returned `updated_at: 2026-09-07`. Two independent sources against
-one assertion, so **2026-09-07 is used throughout**. Subtract three days uniformly if the
-brief was right; nothing depends on it.
-
-## How the family was enumerated
-
-The brief listed suspected members and asked for the list to be established from primary
-evidence. Method:
-
-1. **List every repository in `Xinyuan-LilyGO`** — 254, via the API, three pages.
-2. **List every product in LilyGO's store** — 214, via the public Shopify product feed.
-3. **Intersect.** A board is *confirmed* when it has both a repository and a store listing, or
-   a repository containing a schematic that names it.
-4. **Pin every confirmed repository to a commit** before reading anything from it.
-5. **Read the vendor's own cross-board sources** — `LilyGo-AMOLED-Series/README.MD` §1 and
-   `LilyGo-Display-IDF/main/product_pins.h` — which each enumerate several boards and are the
-   strongest evidence of what LilyGO considers one family.
-
-That produced **11 confirmed members**, three refutations and six out-of-family relatives.
-Recorded in [`README.md` §1](README.md#1-the-confirmed-family-enumerated-from-primary-evidence).
-
-## Refutations, with the evidence
-
-| Hypothesis from the brief | Verdict | Evidence |
-|---|---|---|
-| "T-Display-S3 AMOLED Touch" is a separate board | **refuted** | LilyGO's resource table gives `T-Display-S3-AMOLED-Touch.pdf` as *the* schematic for both touch and non-touch 1.91″ SKUs, and the library README says it supports both from one build |
-| "T-Display-S3 Cardputer-style" exists | **refuted** | No such repository or product. The keyboard handhelds are T-Deck / T-Deck-Pro / T-Deck-MAX / T-Display-keyboard |
-| "AMOLED 2.41″" is a T-Display-S3 | **partially refuted** | The board exists and is in the same library; LilyGO sells and names it **T4-S3** |
-| T-Deck is a T-Display-S3 relative | **out of family** | separate PCB, separate repo |
-
-## Deliberate exclusions
-
-- **Hardware.** None available; nothing is hardware-verified anywhere in this tree.
-- **Net-level schematic tracing.** Blocked on poppler being absent from the host. This is the
-  largest quality gap and the cheapest to close.
-- **Marketplace pricing** (AliExpress, Amazon, Banggood, used). Only LilyGO's own store.
-- **Regulatory records** (FCC, CE).
-- **Chinese-language community sources** (Bilibili, Zhihu, CSDN) — though Chinese-language
-  *datasheets* shipped in the repos were used.
-- **YouTube, Hackaday, Discord.**
-- **The 273 forks** of the base-board repository.
-
-## Boards documented at less than device depth
-
-Stated so nobody mistakes a stub for a finished record:
-
-| Board | Depth | Principal missing item |
-|---|---|---|
-| T-Display-S3 | **full** | net-traced schematic |
-| T-Display-S3 AMOLED | full-ish | `features/`, examples catalogue |
-| T-Display-S3 Long | full-ish | `features/`, examples catalogue |
-| T-Display-S3 Pro | full-ish | `features/`, examples catalogue |
-| T-Display-S3 Touch | medium (by design — the base record covers the electronics) | — |
-| AMOLED Plus, 1.64″, 1.43/1.75″, T4-S3, AMOLED Lite | **medium** | pin tables in some cases, `features/`, examples, acquisition manifests |
-| Pro MVSRBoard | **stub** | everything except identity and artifacts |
-| T-Display (TTGO), T-QT, T-Dongle-S3 | **lineage stubs** | everything except identity and relationship |
-
-## Stopping criterion
-
-Two consecutive broad passes over the org listing, the store feed, the issue trackers and
-Reddit produced only duplicates of findings already recorded. Remaining sources need hardware,
-a package manager, or marketplace sampling.
diff --git a/devices/lilygo/t-display-s3-shared/schematic-netlist.md b/devices/lilygo/t-display-s3-shared/schematic-netlist.md
deleted file mode 100644
index eafe96f..0000000
--- a/devices/lilygo/t-display-s3-shared/schematic-netlist.md
+++ /dev/null
@@ -1,224 +0,0 @@
-# T-Display-S3 family — net list traced from the schematic PDFs
-
-**Traced:** 2026-09-07 · **Method:**
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md)
-· **Tool:** poppler 26.06.0 `pdftotext -bbox-layout`, plus 300 dpi `pdftoppm` crops for the
-ambiguous cases.
-
-This file is **new** and adds to the record; it does not replace any existing pinout table. Where
-it contradicts one, the contradiction is listed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-Every row cites the **sheet, the designator/pin token and its page coordinate**, so any claim can
-be re-checked with one command. Coordinates are PDF points, top-left origin, as poppler reports
-them.
-
----
-
-## 0. Source files and their traceability
-
-| File | Pages | Producer | Rasters | Helper tokens |
-|---|---|---|---|---|
-| `artifacts/schematic/T_Display_S3.pdf` | 1 | Altium Designer / llPDFLib 3.x, CreationDate 2024‑04‑29 | **0** | `CO`, `PI` present; **no `NL`** |
-| `artifacts/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf` | 1 | — | 2 (a logo + its soft mask) | `CO`, `PI` |
-
-`pdfimages -list` on `T_Display_S3.pdf` prints its two header lines and nothing else: the sheet
-contains **no embedded raster at all**. It is pure vector, and fully traceable.
-
----
-
-## 1. `U6` — the charger. **The schematic draws a 5-pin part.**
-
-This settles a standing conflict. The schematic's part string is `TP4065`
-(`T_Display_S3.pdf` p1, x=273.09 y=484.09) and the symbol carries **exactly five pin tokens**:
-
-| Token | Coordinate | Pin | Function text | Coordinate of function text |
-|---|---|---|---|---|
-| `PIU601` | 241.50, 499.46 | 1 | `CHRG` | 254.13, 499.92 |
-| `PIU602` | 264.50, 518.48 | 2 | `GND` | 264.99, 507.91 |
-| `PIU603` | 283.50, 496.46 | 3 | `BAT` | 273.02, 496.32 |
-| `PIU604` | 264.50, 483.48 | 4 | `VCC` | 264.99, 494.81 |
-| `PIU605` | 283.50, 503.46 | 5 | `PROG` | 272.02, 503.27 |
-
-`python3 trace.py grep bbox/tds3.xhtml '^PIU6'` returns those five and **no `PIU606`,
-`PIU607` or `PIU608`**. A rendered 300 dpi crop of the region confirms a five-terminal symbol
-visually.
-
-The same check on two sibling sheets returns the same five pins and the same five function
-names:
-
-| Sheet | Designator | Pin tokens | `PROG` resistor |
-|---|---|---|---|
-| `T-DISPLAY-S3-AMOLED.pdf` p1 | `U5` | `PIU501`…`PIU505` | `R18` 2.32 kΩ |
-| `T-Display-S3-AMOLED-Touch.pdf` p3 | `U6` | `PIU601`…`PIU605` | `R20` 2.2 kΩ |
-| `T_Display_S3.pdf` p1 | `U6` | `PIU601`…`PIU605` | `R13` 2 kΩ |
-
-Pin order 1 `CHRG` · 2 `GND` · 3 `BAT` · 4 `VCC` · 5 `PROG` is the LTC4054 / TP4054 / TP4056
-SOT‑23‑5 arrangement.
-
-**Charge-current annotation.** The sheet carries a rotated note reading **`IBAT (mA) = 580`**
-beside `R13` = 2 kΩ, inside a dashed note box (tokens at x≈311.7, y 510.95–531.81). Poppler
-merges it with the adjacent rotated designator `R13` into one apparent line — see the guide's
-failure-modes section — but the rendered crop shows the two are separate text objects.
-
-Implication: with the fitted `R13` = 2 kΩ the designed charge current is **580 mA**. That is
-*not* consistent with a TP4057 (whose own datasheet, held at
-`components/generic/tp4057/artifacts/`, specifies 500 mA typical at `RPROG` = 2 kΩ, and which is
-a **SOT‑23‑6** part with a separate `STDBY` pin the symbol does not have). It is close to the
-TP4056 family constant.
-
-### Charger periphery
-
-| From | Via | To | Evidence |
-|---|---|---|---|
-| `VBUS` | — | `U6.4 VCC` | `VBUS` text at 264.55, 449.09, column x≈264.5 down to `PIU604` |
-| `U6.4 VCC` | `C21` 100 nF, `C22` 10 µF/16 V | `GND` | `PIC2101/02` at x 294/299.5 y 461.46; `PIC2201/02` y 471.91 |
-| `VBUS` | `R9` 2 kΩ → `LED1` (Red) | `U6.1 CHRG` | `PIR901/02` at y 471.91; `PILED101/02` y 499.46; `PIU601` y 499.46 |
-| `U6.3 BAT` | — | `VBAT` rail, decoupled by `C28` 100 nF and `C29` 10 µF/16 V | `VBAT` at 338, 470.4; `PIC2801/02` x 327.5 |
-| `U6.5 PROG` | `R13` 2 kΩ | `GND` | `PIR1301` 302.5, 536.28 → `GND` 303.05, 561.06 |
-
-## 2. `U2` — ESP32-S3R8 module, signal names as printed
-
-Read directly from the module symbol on `T_Display_S3.pdf` p1 (symbol body x≈600–690).
-
-| ESP32-S3 pin name | Net on this board |
-|---|---|
-| `GPIO0` | `GPIO0` (boot, to `S2` `SW-PB` and `R1` 10 kΩ pull-up to `VDD3V3`) |
-| `GPIO1` | `GPIO1` |
-| `GPIO2` | `GPIO2` |
-| `GPIO3` | `GPIO3` |
-| `GPIO4` | `BAT_ADC` |
-| `GPIO5` | `ESP_LCD_RES` |
-| `GPIO6` | `ESP_LCD_CS` |
-| `GPIO7` | `ESP_LCD_D/C` |
-| `GPIO8` | `ESP_LCD_WR` |
-| `GPIO9` | `ESP_LCD_RD` |
-| `GPIO10` | `II2C_SDA` |
-| `GPIO11` | `II2C_SCL` |
-| `GPIO12` | `ESP_TP_RESET` |
-| `GPIO13` | `ESP_TP_INT` |
-| `GPIO14` | `KEY` |
-| `GPIO15` | `PWR_EN` — the sheet prints, at (622–748, 341.4), **"Battery power must set IO15 to HIGH"** |
-| `GPIO38` | `ESP_LCD_BLK` (to `U4.EN`) |
-| `GPIO39`…`GPIO48` | `ESP_LCD_D0`…`ESP_LCD_D7`, `ESP_USB_DM`, `ESP_USB_DP` (see §4) |
-| `CHIP_PU` | `CHIP_PU` — `SW` `SW-PB`, `RW` 10 kΩ to `VDD3V3`, `CU` 1 µF/6.3 V |
-
-## 3. Power tree
-
-| Designator | Part (as printed) | Function | Key nets |
-|---|---|---|---|
-| `U7` | `AP2112K-3.3V(RT9013)` | 3.3 V LDO | `1 IN` ← `V3V`; `5 OUT` → `VDD3V3`; `3 EN`; `4 NC`; `2 GND`. In: `C23` 47 µF/10 V, `C24` 22 µF/10 V, `C25` 100 nF. Out: `C30`/`C31`/`C32`, `C26` 10 µF/16 V, `C27` 100 nF |
-| `U6` | `TP4065` (5-pin, §1) | Li-ion charger | — |
-| `U4` | `AW9364DNR` | backlight boost | `3 EN` ← `ESP_LCD_BLK`; `4 VIN`; `1 PGND`; `2 EP`; `9/8/7/5` → `LED1`…`LED4` → `LEDK1`…`LEDK4` |
-| `Q1` | `PMBT3904` | NPN, power-latch | with `R5` 10 kΩ, `R6` 1 kΩ, `D1`/`D2` 1N4148 |
-| `Q2`, `Q3` | `SI2301` | P-FET | `VBUS`/`V3V` path, `R7`/`R8` 100 kΩ |
-| `Q4` | `SI2307` | P-FET | `+5V` path, `D3` 1N5819, `R12`/`R14` 100 kΩ |
-| `U5` | `TYPE-C` receptacle | USB-C | `A4/A9 VBUS`, `A6 DP1+`, `A7 DN1-`, `A5 CC`, `A8 SUB1`, `A12/B1 GND`; `B6 DP+`, `B7 DN-`, `B8 SBU2`, `B5 VCONN`, `B4/B9 PWR` |
-| `U1` | 40 MHz crystal | — | `XIN`/`XOUT`, `C2` 12 pF, `C4` 15 pF |
-| `U3` | `W25Q128JV` | 16 MB SPI flash | `1 CS`→`SPICS0`, `2 DO`→`SPIQ`, `3 WP`→`SPIWP`, `4 GND`, `5 DI/IO0`→`SPID`, `6 CLK`→`SPICLK`, `7 HOLD`→`SPIHD`, `8 VCC`→`VDD_SDIO`; `C19` 100 nF |
-
-`VBAT` is annotated **`(3.7V~~4.2V)`** at (468, 491.0). The 5 V input path carries the note
-`5V/2A 保险丝` (“5 V / 2 A fuse”) at (359–365, 495.3) beside `R10`.
-
-## 4. `CN1` — display FPC, `KH-FG0.5-H2.0-30PIN`
-
-Pin count on the symbol is 31 (`PICN101`…`PICN1031`); the part string says 30 pin. Named pins:
-
-| CN1 pin | Net |
-|---|---|
-| 4 | `ESP_LCD_RES` |
-| 5 | `ESP_LCD_CS` |
-| 6 | `ESP_LCD_D/C` |
-| 7 | `ESP_LCD_WR` |
-| 8 | `ESP_LCD_RD` |
-| 11–18 | `ESP_LCD_D0` … `ESP_LCD_D7` |
-| 21–24 | `LEDK1` … `LEDK4` |
-| 26 | `ESP_TP_RESET` |
-| 27 | `II2C_SCL` (pull-up `RIIC` 10 kΩ to `VDD3V3`) |
-| 28 | `II2C_SDA` (pull-up `RIID` 10 kΩ) |
-| 29 | `ESP_TP_INT` (pull-up `RINT` 100 kΩ) |
-
-Decoupling on the FPC rail: `C17`, `C18` 100 nF, `C20` 1 µF/6.3 V; `V3V` feeds pin 20 area.
-
-## 5. `P1` / `P2` — the two 12-way headers
-
-Both symbols are `Header 12`. **Verified against a 300 dpi crop**, because the text-layer offsets
-alone are ambiguous at ±1.7 pt: pin 12 of `P2` runs unbroken to a `VDD3V3` power port, which
-fixes the binding as "label sits above its wire".
-
-| `P2` pin | Net | | `P1` pin | Net |
-|---|---|---|---|---|
-| 12 | `VDD3V3` | | 12 | `GND` |
-| 11 | `GPIO1` | | 11 | `U0TXD` |
-| 10 | `GPIO2` | | 10 | `U0RXD` |
-| 9 | `GPIO3` | | 9 | `II2C_SDA` |
-| 8 | `GPIO10` | | 8 | `II2C_SCL` |
-| 7 | `GPIO11` | | 7 | `ESP_TP_RESET` |
-| 6 | `GPIO12` | | 6 | `ESP_TP_INT` |
-| 5 | `GPIO13` | | 5 | **unlabelled stub** |
-| 4 | **✗ no-connect** (X marker) | | 4 | **✗ no-connect** (X marker) |
-| 3 | **✗ no-connect** (X marker) | | 3 | `GND` |
-| 2 | `GND` | | 2 | `GND` |
-| 1 | `+5V` | | 1 | `VDD3V3` |
-
-⚠ **Recorded, not resolved.** `P1` pins 9/8/7/6 carry `II2C_SDA`/`II2C_SCL`/`ESP_TP_RESET`/
-`ESP_TP_INT`, and §2 shows those are `GPIO10`/`GPIO11`/`GPIO12`/`GPIO13` — the *same four
-signals* that `P2` pins 8/7/6/5 expose under their raw GPIO names. Two readings are possible:
-the board genuinely brings the same four GPIOs to both headers, or `P1` and `P2` are two
-renderings of one physical header. **The sheet does not distinguish them, and no attempt is made
-to here.** A continuity check between `P1.9` and `P2.8` on a physical board settles it in
-seconds.
-
-## 6. `AXPM65611` — function established (AMOLED variants)
-
-Not on the base board. On `T-Display-S3-AMOLED-Touch.pdf` p3 (`U5`) and
-`T-Display-S3-AMOLED-Plus.pdf` p3 (`U4`) the symbol has **12 pins**, identical on both sheets:
-
-| Pin | Name | Plus-sheet rail annotation |
-|---|---|---|
-| 1 | `SWP` | → `L6`/`L3` `DFP252012TF-100M` |
-| 2 | `PGND` | |
-| 3 | `VPOS` | **`+4.6V`** |
-| 4 | `EN` | |
-| 5 | `GND` | |
-| 6 | `TEST` | |
-| 7 | `CTRL` | net `SWIRE` |
-| 8 | `AVDD` | |
-| 9 | `VNEG` | **`-2.2V`**, also labelled `EAVDD` on the Touch sheet |
-| 10 | `SWN` | → `L7`/`L4` `DFP252012TF-100M` |
-| 11 | `VIN` | `+3.3V` |
-| 12 | `VIN` | `+3.3V` |
-
-Two switch nodes with two separate 10 µH inductors, one positive and one negative output at
-ELVDD/ELVSS-typical voltages, plus a `SWIRE` control line: this is **an AMOLED bipolar display
-bias supply**, confirmed rather than hypothesised. The manufacturer and orderable part number
-remain unknown. See
-[`components/unidentified/lilygo-t-display-s3-family/axpm65611`](../../../components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md).
-
-## 7. `SCH_T-Display-S3-MIDI_V1.1.pdf`
-
-Traceable (711 words, `CO`/`PI` tokens present). The 2 objects reported by `pdfimages -list`
-are one RGB image and its greyscale soft mask — a logo, not schematic content. No net-level
-conflict with the base board was found; the MIDI variant's additions are not covered here.
-
-## 8. What could **not** be traced
-
-The **1.64″ AMOLED variant** (`devices/lilygo/t-display-s3-amoled-1-64/`) has **no schematic in
-this repository at all** — the directory contains only `README.md`. This is therefore not a
-tracing failure but a *missing artifact*: no poppler invocation can help. Its pin map remains
-unestablished, and the only routes to it are LilyGO publishing the sheet, or a `pin_config.h`
-appearing in a per-board repository. Recorded here so the gap is not mistaken for one this
-session could have closed.
-
----
-
-## Reproducing any row above
-
-```bash
-nix-shell -p poppler-utils --run \
-  'pdftotext -bbox-layout devices/lilygo/t-display-s3-shared/artifacts/schematic/T_Display_S3.pdf /tmp/tds3.xhtml'
-cd scratch/schematic-tracing
-python3 trace.py   grep    /tmp/tds3.xhtml '^PIU6'          # pin tokens for U6
-python3 trace.py   cluster /tmp/tds3.xhtml --x 262 --y 500 --r 75
-python3 render.py  /tmp/tds3.xhtml --hide-pi --x0 200 --x1 420 --y0 440 --y1 560
-```
diff --git a/devices/lilygo/t-display-s3-shared/sources.md b/devices/lilygo/t-display-s3-shared/sources.md
deleted file mode 100644
index 0bb692b..0000000
--- a/devices/lilygo/t-display-s3-shared/sources.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# T-Display-S3 family — sources
-
-Family-scoped sources only. Per-board sources are in each board's own record; the fullest is
-[`../t-display-s3/sources.md`](../t-display-s3/sources.md). All retrieved **2026-09-07**.
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| F-1 | `Xinyuan-LilyGO` organisation repository listing, 254 repos | GitHub API | primary | repository | `gh api orgs/Xinyuan-LilyGO/repos?per_page=100` | 2026-09-07 | live | **the family enumeration**, star/fork/issue counts, default branches, licences, push dates | a snapshot; the org changes weekly | [`artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv`](artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv) |
-| F-2 | LilyGO Shopify product feed, 214 products | LILYGO | primary | store listing | https://lilygo.cc/collections/all/products.json | 2026-09-07 | feed `updated_at` 2026-09-07 | every SKU, price, stock state and `published_at` launch date in the family; **the V1.0/V2.0 concurrency finding** | prices exclude shipping and tax; needs a browser User-Agent | `scratch/lilygo-t-display-s3/shop-products.jsonl` |
-| F-3 | `LilyGo-Display-IDF` → `main/product_pins.h` | LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/LilyGo-Display-IDF/blob/b1a1cc54994bf1b417e3bb30c437bbe1036bff7f/main/product_pins.h | 2026-09-07 | commit 2025-11-03 | **nine boards' pin maps in one file**, behind `CONFIG_LILYGO_*` switches | ESP-IDF only; does not cover the 1.43/1.64/1.75 boards | [`artifacts/originals/LilyGo-Display-IDF-product_pins.h`](artifacts/originals/LilyGo-Display-IDF-product_pins.h) |
-| F-4 | `LilyGo-AMOLED-Series` README.MD | LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/LilyGo-AMOLED-Series/blob/6d1dc008b94578cc34ba4a0f3b223dd808ca963f/README.MD | 2026-09-07 | commit 2026-05-06 | the four AMOLED boards, resolutions, luminance, **the only published current-consumption table in the family**, the T4-S3 GPIO18 warning, library dependencies with versions | vendor prose | scratch |
-| F-5 | `T-Display-S3` README.md | LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/README.md | 2026-09-07 | commit 2026-08-31 | the `USB CDC On Boot` FAQ, the Arduino-core 2.0.14 pin, the GPIO15 requirement | — | scratch |
-| F-6 | `esphome/components/mipi_spi/models/{lilygo,amoled}.py` | ESPHome | primary (third-party) | repository | https://github.com/esphome/esphome/tree/dev/esphome/components/mipi_spi/models | 2026-09-07 | branch `dev` | **independent** pin, offset, colour-order and init-sequence data for six boards in the family | **cited by branch, not commit** — the one such citation in this pass | scratch |
-| F-7 | Eight LilyGO board schematics | LILYGO | primary | schematic | per-board repositories at the commits in each record | 2026-09-07 | title-block dates 2024-04-29 … 2024-07-19 | the designator/part census that underpins every chip identity claimed here | **net connectivity was not traced for any of them** | per-board `artifacts/schematic/` |
-| F-8 | Six issue trackers, 550 issues | LILYGO + community | community | issue | per repository | 2026-09-07 | 2022-06 … 2026-08 | the gotcha corpus, and the open-issue counts in [`product-history-and-family.md`](product-history-and-family.md) | selection biased toward high-engagement threads | `scratch/lilygo-t-display-s3/issues/` |
-| F-9 | `old.reddit.com/search.json`, 4 queries | Reddit | community | forum | https://old.reddit.com/search.json | 2026-09-07 | 2023-05 … 2026-08 | 27 family-relevant posts; two read in full | needs a link-preview User-Agent; `www.reddit.com` returns 403 | `scratch/lilygo-t-display-s3/reddit.txt` |
-| F-10 | Chip datasheets mirrored inside LilyGO board repos | various makers, mirrored by LILYGO | credible mirror | datasheet | per-repo `datasheet/` and `information/` | 2026-09-07 | various | the identities of ST7789V, RM67162, RM690B0, SH8501B, SH8601Z, CO5300, AXS15231, CST328, CST3530, FT3168, SY6970, ST7796S, MSM261S4030H0R | **all filed under their component records, not here** | `components/**/artifacts/` |
-
-## Family-scoped sources sought and not found
-
-| Sought | Result |
-|---|---|
-| A LilyGO changelog, revision register or ECN process | **none exists.** The nearest thing is a `//!` comment in the Pro's `utilities.h` |
-| A LilyGO documentation portal | none. Everything is GitHub + Shopify |
-| Published PCB revision numbers | only for the AMOLED 1.91″ (V1.0/V2.0, in store variant titles) and the Pro (V1.0/V1.1, in a source comment) |
-| Schematics for the 1.43/1.64/1.75″ AMOLED boards | **none published.** The only boards in the family without one |
-| A licence for `T-Display-S3-Long` and `T-Display-S3-Pro` | **none declared** |
-| Any current-consumption figure for the base T-Display-S3 | none |
diff --git a/devices/lilygo/t-display-s3-touch/README.md b/devices/lilygo/t-display-s3-touch/README.md
deleted file mode 100644
index 0264f71..0000000
--- a/devices/lilygo/t-display-s3-touch/README.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# LilyGO T-Display-S3 Touch
-
-> **Not a separate PCB.** LilyGO publishes **one schematic** (`T_Display_S3.pdf`) for both the
-> T-Display-S3 and the Touch version, and one repository covers both. This record exists
-> because the Touch version is a distinct SKU with distinct software requirements — and because
-> **which touch controller it carries changed silently**.
->
-> SKUs `H587` (non-soldered) **USD 12.61**, `H589` (soldered) **USD 13.02**,
-> `H717`/`H705`/`H681` shell and regional variants up to **USD 38.48**. In stock 2026-09-07.
-> Research retrieved 2026-09-07. Depth: **medium — deliberately, because the base-board record
-> covers everything electrical.**
-
-## Read the base-board record first
-
-Everything about the SoC, flash, PSRAM, display bus, power, GPIO15, USB, battery and Wi-Fi is
-identical and is documented once at **[`../t-display-s3/README.md`](../t-display-s3/README.md)**.
-Shared artifacts: [`../t-display-s3-shared/`](../t-display-s3-shared/README.md).
-
-## What is different
-
-| | Base | **Touch** |
-|---|---|---|
-| Panel | 1.9″ IPS, no digitiser | 1.9″ IPS **with a bonded capacitive digitiser** |
-| Touch controller | none | **Hynitron CST816S** (early) **or CST328** (later) |
-| I²C address | — | **`0x15`** (CST816S) / **`0x1A`** (CST328) |
-| GPIO16 (`TOUCH_INT`) | fitted pull-up, otherwise unused | touch interrupt |
-| GPIO21 (`TOUCH_RES`) | free | touch reset |
-| Price | USD 9.04 | **USD 12.61** (+3.57) |
-| Build flag | irrelevant | **`-DTOUCH_MODULES_CST_MUTUAL`** (CST328) or `-DTOUCH_MODULES_CST_SELF` (CST816S) |
-
-That is the entire delta. The touch controller is **on the panel flex**, not on the mainboard —
-which is why one schematic covers both, and why no touch-controller designator appears in the
-schematic's part census.
-
-## The one thing that will cost you an evening
-
-**Two generations of touch controller ship under the same product name**, and the driver flag
-that selects between them lives in `platformio.ini`, not in your sketch. LilyGO's current
-default is `-DTOUCH_MODULES_CST_MUTUAL` (**CST328**). If your board is an early **CST816S**,
-that default finds nothing and reports "no Touch IC found" —
-[issue #125](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/125), 15 comments.
-
-**Identify before you build:** run `examples/I2CScan` on GPIO17/18.
-
-The evidence that both exist is that the board repository ships **both register documents** —
-`CST816S寄存器说明-20190508.pdf` (76 816 B) and `CST328数据手册V2.2.pdf` (1 297 291 B). A board
-with one controller does not need two manuals. Full treatment:
-[revision R1](../t-display-s3-shared/board-revision-drift.md#r1--t-display-s3-touch-cst816s--cst328)
-and [`../t-display-s3/features/touch.md`](../t-display-s3/features/touch.md).
-
-## Second thing: I²C lives on the gated rail
-
-The touch controller is powered from the GPIO15-gated `V3V` rail. **An I²C scan with GPIO15
-low finds nothing**, which is indistinguishable from a dead controller. Drive GPIO15 high
-before scanning.
-
-## Software
-
-Identical to the base board except the flag above. `TouchLib` (`mmMicky/TouchLib`) is the
-Arduino driver; ESP-IDF users need `LilyGo-Display-IDF`
-([issue #156](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/156)). ESPHome's
-`T-DISPLAY-S3` model covers the display; touch is configured separately.
-
-Examples: `touch_test`, `CapacitiveTouch`, `usb_hid_pad`, `factory` — all in the base-board
-repo at `ec889e7`, catalogued in
-[`../t-display-s3/examples/catalog.json`](../t-display-s3/examples/catalog.json).
-
-## Artifacts
-
-**None held separately.** The schematic, firmware and dimension files are the base board's and
-live once in [`../t-display-s3-shared/artifacts/`](../t-display-s3-shared/artifacts/). The
-touch-controller datasheets are filed under
-[`components/hynitron/cst816d/`](../../../components/hynitron/cst816d/artifacts/) and
-[`components/hynitron/cst328/`](../../../components/hynitron/cst328/artifacts/).
-
-The repo does hold Touch-specific mechanical files —
-`dimensions/CapacitiveTouchScreen.stp` (169 278 B) and
-`dimensions/Lilygo_T-DisplayS3_Touch_from Stuttgart.zip` (2 393 118 B, a community-contributed
-3D model) — **neither retrieved by this pass**; recorded here so they are findable.
-
-## Sources
-
-| ID | Source | Class | Retrieved | Establishes |
-|---|---|---|---|---|
-| T1 | `Xinyuan-LilyGO/T-Display-S3` README § *Supported Products* @ `ec889e7` | primary | 2026-09-07 | Touch is a variant of the same board, same schematic, same dimensions |
-| T2 | `platformio.ini` @ `ec889e7` | primary | 2026-09-07 | `-DTOUCH_MODULES_CST_MUTUAL` is the current default |
-| T3 | `datasheet/CST816S…pdf` + `datasheet/CST328…pdf` @ `ec889e7` | credible mirror | 2026-09-07 | two controller generations |
-| T4 | Store feed | primary | 2026-09-07 | SKUs and prices |
-| T5 | [Issue #125](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/125), [#168](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/168), [#156](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/156) | community | 2026-09-07 | the driver-flag failure, I²C NAK behaviour, ESP-IDF gap |
-
-## Gaps
-
-- **The changeover date from CST816S to CST328 is unknown.** No vendor announcement exists.
-- **No external way to tell the two apart** was found; identification is by I²C scan only.
-- Not verified on hardware.
diff --git a/devices/lilygo/t-display-s3-touch/certification-and-compliance.md b/devices/lilygo/t-display-s3-touch/certification-and-compliance.md
deleted file mode 100644
index 9806e00..0000000
--- a/devices/lilygo/t-display-s3-touch/certification-and-compliance.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# Certification and compliance — t-display-s3-touch
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-No touch-specific grant. The touch variant is a variant of the same product; a capacitive touch layer is not a radio change. **Inferred**, not confirmed by a permissive-change filing.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2ASYE-T-DISPLAY-S3`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-DISPLAY-S3`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2022-12-12** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2022-12-12 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2472 MHz** (Wi-Fi 2.4 GHz, ch 1–13 — ⚠ wider than the usual US 1–11) |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 9 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY-S3` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Circuit Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 164,139 | `017b0f56a7b17f1b…` |
-| `ID-Label-Location-Info-Label-Label-Location.pdf` | 93,568 | `9db9d7aa37227ff3…` |
-| `Internal-Photos-Internal-Photos.pdf` | 365,798 | `3bc9aeeaa4b61bb5…` |
-| `Test-Report-Antenna-Report.pdf` | 1,054,223 | `45b9998b58613e2b…` |
-| `Users-Manual-User-Manual.pdf` | 1,020,247 | `8aaf7b92dc11ea5f…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY-S3/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY-S3/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3-touch/market-and-pricing.md b/devices/lilygo/t-display-s3-touch/market-and-pricing.md
deleted file mode 100644
index d32dced..0000000
--- a/devices/lilygo/t-display-s3-touch/market-and-pricing.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# Market and pricing — t-display-s3-touch
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Non-Soldered Pin [H569] | `H569` | **USD 9.04** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Touch Non-Soldered Pin [H587] | `H587` | **USD 12.61** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Touch Soldered [H589] | `H589` | **USD 13.02** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Soldered Pin [H577] | `H577` | **USD 9.54** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Grey Shell [K206] | `K206` | **USD 13.22** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Black Shell [K204] | `K204` | **USD 13.22** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Black Shell and built-in 700 mAh battery [K204-01] | `K204-01` | **USD 20.60** | ❌ no |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Grey Shell and built-in 700 mAh battery [K206-01] | `K206-01` | **USD 20.60** | ❌ no |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Only MIDI Board [H656] | `H656` | **USD 15.47** | ✅ yes |
-| T-Display S3 | 2022-07-15 | Germany [ For Europe only] / With Black Shell [K204] | `K204-DE` | **USD 17.72** | ❌ no |
-| T-Display S3 | 2022-07-15 | United States [For US only] / Soldered Pin [H577] | `USH577` | **USD 14.04** | ❌ no |
-| T-Display S3 | 2022-07-15 | United States [For US only] / With Black Shell [K204] | `K204US` | **USD 17.72** | ❌ no |
-| T-Display S3 | 2022-07-15 | Germany [ For Europe only] / Soldered Pin [H577] | `DEH577` | **USD 14.04** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 9.04, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-Touch variants of the shared `t-display-s3` handle: `H587` non-soldered USD 12.61, `H589` soldered USD 13.02 — a **USD 3.57 premium** over the equivalent non-touch board.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3/README.md b/devices/lilygo/t-display-s3/README.md
deleted file mode 100644
index 17de768..0000000
--- a/devices/lilygo/t-display-s3/README.md
+++ /dev/null
@@ -1,212 +0,0 @@
-# LilyGO T-Display-S3
-
-> **Product:** T-Display-S3 · store handle `t-display-s3` · SKUs `H569` (non-soldered),
-> `H577` (soldered), `H587`/`H589` (Touch), `K204`/`K206` (with shell) · published to
-> LilyGO's store **2022-07-15** · **active, in stock** as of 2026-09-07 at **USD 9.04**
-> (bare, non-soldered header pins).
->
-> **PCB revision status:** LilyGO has never published a numbered revision for this board. The
-> only schematic is one undated-by-version sheet whose title block reads **2024-04-29**, and it
-> disagrees with at least one shipping board — see
-> [`gaps-and-conflicts.md`](gaps-and-conflicts.md). Treat "T-Display-S3" as a *rolling* design.
->
-> Research retrieved **2026-09-07**. No physical hardware was available; nothing here is
-> hardware-verified by this pass, and every claim is labelled.
-
-**Part of the [T-Display-S3 family](../t-display-s3-shared/README.md)**, which is a
-name rather than a platform — eleven boards, eight display controllers, four different
-chargers. Read the family hub before assuming code ports.
-
----
-
-## Identity and variants
-
-| | |
-|---|---|
-| Marketed name | **T-Display-S3** (LilyGO also writes it *T-Display S3*, *LILYGO T-Display-S3*, and the ESP32 core calls the board target `lilygo-t-display-s3`) |
-| Predecessor | **TTGO T-Display** (ESP32, 1.14″ 135×240) — [lineage](../t-display-ttgo/README.md) |
-| Sibling on the same PCB | **[T-Display-S3 Touch](../t-display-s3-touch/README.md)** — identical schematic, panel swapped |
-| Add-on boards sold for it | **T-Display TF Shield** (microSD, `H609`/`H610`), **T-Display-S3 MIDI** shield (`H656`), **T-Display-S3 Shell** (`L929`/`L930`), **T-Display keyboard** |
-| Not the same thing | T-Display-S3 **AMOLED**, **Long**, **Pro** — different PCBs entirely |
-
-Purchase options that are **not** revisions, and are frequently mistaken for them: header
-soldered vs not; grey vs black shell; with/without a 700 mAh battery; China/US/Germany
-warehouse. The regional SKUs (`USH577`, `DEH577`, `K204US`, `K204-DE`) are the same board at a
-higher price — see [`market-and-pricing.md`](market-and-pricing.md).
-
-## What it is and visual identification
-
-A 62 × 26 mm ESP32-S3 board dominated by a 1.9-inch landscape IPS strip bonded to the front,
-with a USB-C port on the short edge, a JST 1.25 mm battery socket beside it, and two 12-pin
-0.1″ header rows down the long edges. Two tactile buttons sit on the long edge next to USB-C
-(`BOOT`/GPIO0 and `RST`), and a third (GPIO14) on the opposite edge.
-
-Fastest positive identification without opening anything:
-
-- **Green LED lit while on USB** → the `V3V` rail indicator (`LED8`). If it is *off* while the
-  board is on battery, GPIO15 has not been driven high.
-- **Red LED** → charge status (`LED1`). *Flashes or glows dimly when no battery is connected*,
-  solid while charging, off when full — this specific behaviour is documented by LilyGO and is
-  a good "is it a genuine board" check.
-- **Touch vs non-touch**: the Touch panel has a glass overlay that extends past the active
-  area and a slightly thicker bezel; electrically, scan I²C on GPIO17/18 — a device at `0x15`
-  (CST816S) or `0x1A` (CST328) means Touch. **A non-touch board still pulls GPIO16/17 high**,
-  so pin behaviour alone will not tell you.
-
-## Product history, family and culture
-
-Announced and listed 2022-07-15, six weeks after the GitHub repo was created (2022-06-13). It
-became LilyGO's most successful board by community metrics: **1 169 GitHub stars and 273
-forks** on `Xinyuan-LilyGO/T-Display-S3` as of 2026-09-07, more than double any other board in
-the family and second in the whole organisation only to the original `TTGO-T-Display`
-(1 192★) which it replaced.
-
-Full dated lineage: [`product-history-and-family.md`](product-history-and-family.md).
-
-## Key specifications
-
-| Function | Part | Interface | Component record |
-|---|---|---|---|
-| SoC | **ESP32-S3R8** — bare die, *not* a module; 8 MB in-package OPI PSRAM | — | [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) |
-| Flash | **Winbond W25Q128JV**, 16 MB, QIO 80 MHz (`U3`) | quad SPI | [`winbond/w25q128jv`](../../../components/winbond/w25q128jv/README.md) |
-| Display controller | **Sitronix ST7789V** (`ST7789V_SPEC_V1.4.pdf` ships in the repo) | 8-bit Intel-8080 | [`sitronix/st7789v`](../../../components/sitronix/st7789v/README.md) |
-| Panel | 1.9″ IPS, 170 × 320, window offset 35 columns | — | — |
-| Backlight driver | **Awinic AW9364DNR** (`U4`), 4-channel LED boost | GPIO38 enable / one-wire | [`awinic/aw9364`](../../../components/awinic/aw9364/README.md) |
-| Touch (Touch SKU only) | **Hynitron CST816S** (early) or **CST328** (later) | I²C `0x15` / `0x1A` | [`hynitron/cst816d`](../../../components/hynitron/cst816d/README.md) · [`hynitron/cst328`](../../../components/hynitron/cst328/README.md) |
-| Li-ion charger | **TP4065** per schematic (`U6`); a shipping board was found carrying a 5-lead TSOT-23 marked `65b311` instead | — | [`nanjing-top-power/tp4065`](../../../components/nanjing-top-power/tp4065/README.md) · [unidentified `AXPM65611`/`65b311`](../../../components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md) |
-| 3.3 V LDO | **AP2112K-3.3** (`U7`), schematic lists **RT9013** as the alternate | — | [`diodes-incorporated/ap2112k`](../../../components/diodes-incorporated/ap2112k/README.md) |
-| Rail gate | `Q2`/`Q3` **SI2301**, `Q4` **SI2307** P-channel MOSFETs, driven by GPIO15 | — | — |
-| USB | **native ESP32-S3 USB** on GPIO19/20 → 16-pin Type-C receptacle (`U5`). **No UART bridge fitted** | USB 1.1 FS | [`generic/usb-c-interface`](../../../components/generic/usb-c-interface/README.md) |
-| Crystal | 40 MHz (`U1`) | — | — |
-| Antenna | on-board ceramic + a **`RX`/`RX2` 0 Ω resistor pair** to switch to u.FL | — | [`generic/ceramic-antenna`](../../../components/generic/ceramic-antenna/README.md) |
-| Battery connector | JST **1.25 mm** 2-pin, 3.7–4.2 V | — | — |
-| Expansion | 2 × 12-pin 0.1″ headers, 1 × 4-pin SH1.0 I²C ("Qwiic-like", **not** Qwiic-compatible) | — | — |
-| microSD | **not fitted** — only via the T-Display TF Shield | 1-bit SDMMC | [`generic/micro-sd-sdmmc`](../../../components/generic/micro-sd-sdmmc/README.md) |
-
-Electrical envelope, from LilyGO's own table: USB-C in **5 V**; battery **3.7–4.2 V**;
-header `VBUS` = 5 V (**output only**, cannot back-feed); header `VBAT` = 4.2 V; **the 3V header
-pin is rated for ≤ 100 mA**. That last figure is the one people miss when hanging sensors off
-the header.
-
-Full map: [`pinouts-and-buses.md`](pinouts-and-buses.md).
-
-## Architecture and components
-
-Bare-die ESP32-S3R8 with external QIO flash and no module can. The design consequence that
-matters: **GPIO26–37 are consumed by the in-package OPI PSRAM** and are simply not available,
-which is why a 45-pin-capable chip exposes so few usable pins here once the 8-bit LCD bus takes
-another thirteen.
-
-Power is a two-stage arrangement — USB-C 5 V or battery → charger/path → AP2112K LDO → a
-**gated `V3V` rail** controlled by GPIO15. Almost every "my board is dead on battery" report
-resolves to that gate. See [`features/power-and-battery.md`](features/power-and-battery.md).
-
-## Common tasks / How do I…?
-
-| I want to… | Guide |
-|---|---|
-| get anything on the screen at all | [`features/display.md`](features/display.md) |
-| choose between TFT_eSPI, Arduino_GFX and LovyanGFX | [`features/display.md`](features/display.md) → and [`guides/hardware/parallel-8080-lcd-buses.md`](../../../guides/hardware/parallel-8080-lcd-buses.md) |
-| make it work on battery (it "does nothing") | [`features/power-and-battery.md`](features/power-and-battery.md) · [`features/usb.md`](features/usb.md) |
-| read the battery voltage correctly | [`features/battery-voltage-measurement.md`](features/battery-voltage-measurement.md) |
-| change the charge current | [`features/power-and-battery.md`](features/power-and-battery.md#changing-the-charge-current) |
-| use the touch panel | [`features/touch.md`](features/touch.md) |
-| use the buttons and wake from them | [`features/buttons.md`](features/buttons.md) |
-| add a microSD card | [`features/microsd.md`](features/microsd.md) |
-| get Wi-Fi/BLE range that is not terrible | [`features/wifi-and-ble.md`](features/wifi-and-ble.md) |
-| sleep at low current | [`features/deep-sleep.md`](features/deep-sleep.md) |
-| use the headers, I²C and the SH1.0 connector | [`features/gpio-and-expansion.md`](features/gpio-and-expansion.md) |
-| flash it / un-brick it | [`development.md`](development.md) · [`factory-firmware.md`](factory-firmware.md) |
-| know which Arduino core version to use | [`development.md`](development.md#arduino-core-versions) |
-| run ESPHome / Tasmota / MicroPython on it | [`projects-and-community.md`](projects-and-community.md) |
-
-## Distinctive strengths
-
-- **Price-to-pixels.** USD 9.04 for an ESP32-S3 with 16 MB flash, 8 MB OPI PSRAM *and* a
-  bonded 170×320 IPS panel is, as of 2026-09-07, the cheapest way to get all four in one part.
-- **The parallel bus is genuinely fast.** 8-bit 8080 at 16 MHz beats the SPI-driven 240×240
-  boards it competes with for full-screen refresh, which is why it is the default LVGL demo
-  board for a lot of people.
-- **Enormous community mass.** 1 169★/273 forks, plus ESPHome, Tasmota and MicroPython support
-  that all name the board explicitly. Almost any question has already been asked.
-- **Real 16 MB flash and 8 MB PSRAM**, not the 4 MB/no-PSRAM of most cheap display boards.
-
-## Shortcomings and constraints
-
-- **VBUS is not brought out**, so the battery cannot be charged from anything but USB-C.
-  Reported [2022-11-07](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/42), never fixed;
-  LilyGO's own answer was "maybe you can solve it by soldering a wire from VBUS."
-- **No battery protection on board.** LilyGO's maintainer, 2025-02-06:
-  *"No built-in battery protection, needs to be used with a lithium-ion battery with battery
-  protection."* Use a protected cell.
-- **Charge current is fixed at roughly 500–580 mA** by a soldered resistor, which is above 1C
-  for the 350–400 mAh cells that physically fit the shell.
-- **GPIO16/17 carry fitted pull-ups even on non-touch boards**, and GPIO43/44 are unusable
-  under Arduino. Between those and the PSRAM pins, the genuinely free GPIO count is small.
-- **The vendor pins the Arduino core at 2.0.14** and TFT_eSPI is documented as broken above it.
-- **Antenna performance is a recurring complaint** — [issues #123](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/123),
-  [#340](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/340). The u.FL switch exists but
-  requires moving a 0 Ω resistor.
-
-## Performance summary
-
-See [`performance.md`](performance.md). Short version: no independent benchmark of this board
-was located, and none is reproduced here. LilyGO publishes no current figures for the base
-board (it does for the AMOLED boards). What *is* evidenced is the 16 MHz pixel clock LilyGO
-chose, their own warning that raising or lowering it causes visible tearing, and ESPHome's
-more conservative 10 MHz.
-
-## Pricing and availability
-
-Dated observations, all from LilyGO's own store feed on **2026-09-07**:
-bare board **USD 9.04**, soldered **9.54**, Touch **12.61/13.02**, with shell **13.22**,
-MIDI shield alone **15.47**. US and German warehouse stock of several SKUs was **out of
-stock**. Full table, marketplace and clone pricing: [`market-and-pricing.md`](market-and-pricing.md).
-
-## Competitors, equivalents and clones
-
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) compares against
-boards already documented here — Waveshare ESP32-S3-Knob-Touch-LCD-1.8, Seeed XIAO ESP32S3
-Sense, M5Stack Cardputer ADV — and against the obvious rivals, and contains the worked
-clone example that [`guides/markets/clones-and-variants.md`](../../../guides/markets/clones-and-variants.md)
-asks for.
-
-## Images and teardown/PCB views
-
-No image was retained by this pass; rights for LilyGO's product photography were not
-established and no third-party teardown with clear licensing was found. What exists and where
-to get it is catalogued with provenance in [`media/manifest.json`](media/manifest.json), which
-also records the two PCB photographs LilyGO's maintainer posted into
-[issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313) — the most useful
-"where are the pull-up resistors" images in existence, and GitHub-hosted.
-
-## Community, editorial and project coverage
-
-[`projects-and-community.md`](projects-and-community.md) (software, firmware, ESPHome/Tasmota
-/MicroPython status) and [`community.md`](community.md) (forums, Reddit, issue-tracker
-findings, each labelled by evidence class).
-
-## Documentation map
-
-`pinouts-and-buses.md` · `resources-and-conflicts.md` · `development.md` ·
-`factory-firmware.md` · `features/` · `examples/` · `acquisition/` · `coverage.md` ·
-`compatibility-and-status.md` · `gaps-and-conflicts.md` · `performance.md` ·
-`market-and-pricing.md` · `comparisons-and-recommendations.md` ·
-`product-history-and-family.md` · `projects-and-community.md` · `community.md` ·
-`sources.md` · `research-log.md` · `commands.md`
-
-## Artifact layout
-
-Board-level artifacts for this PCB live in the **[shared platform
-record](../t-display-s3-shared/README.md#5-shared-artifacts-held-here)**, because the
-schematic and factory firmware cover the Touch variant too and storing them twice would be
-wrong. Chip datasheets live under their component records, per repository policy — including
-the `ST7789V_SPEC_V1.4.pdf`, `CST816S` register guide and `CST328` datasheet that LilyGO ships
-inside this *board* repository.
-
-## Known conflicts and unresolved identities
-
-Six, listed with evidence and what would settle each, in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md). The two that matter most:
-the **charger part number does not match shipping hardware**, and the two factory firmware
-images that claim to be different are **byte-identical**.
diff --git a/devices/lilygo/t-display-s3/acquisition/README.md b/devices/lilygo/t-display-s3/acquisition/README.md
deleted file mode 100644
index bd6c280..0000000
--- a/devices/lilygo/t-display-s3/acquisition/README.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# T-Display-S3 — acquisition
-
-Clean-clone reproduction, in execution order. All entries verified **2026-09-07**.
-
-## 0. Prerequisites
-
-```bash
-gh auth login          # api.github.com limits per identity: 60/h anonymous, 5000/h with a token
-python3 --version      # 3.9+
-```
-`curl` is sufficient for everything; `gh` is only needed for the API enumeration steps.
-
-## 1. Tracked artifacts — already in the repository
-
-Board-level artifacts for this PCB live in
-[`../../t-display-s3-shared/artifacts/`](../../t-display-s3-shared/artifacts/) because they
-also cover the Touch variant. Nothing needs downloading for those; verify with:
-
-```bash
-cd devices/lilygo/t-display-s3-shared/artifacts
-sha256sum -c <<'EOF'
-607b63300636521fc78fbb36ed371ac10e81e3145ffa770784f45c2bf52e08c9  schematic/T_Display_S3.pdf
-c3d5651d79b933d0995f294caeb60f4ee0c5f59090a531f13915868d125c7ce6  schematic/SCH_T-Display-S3-MIDI_V1.1.pdf
-f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa  firmware/t-display-s3-touch-20230417_0x0.bin
-f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa  firmware/t-display-s3-no-touch-20231013_0x0.bin
-4af91e520a3f5037d9b0420aa620f8736e4e6469601098fea6eb4985323d847f  firmware/t-display-s3-lvgl-demo-20250109_0x0.bin
-45385b2a90070a7616b7fceca553d60ca984e33115f4b9586a5ebb6ddb8213f1  firmware/t-display-s3-tft-espi-20231113_0x0.bin
-2f0cf68a3ac19cec982735d7ccbcb93e522e65c9d8736e440efbf4001f9707fd  firmware/t-display-s3-screen-detect-20230315_0x0.bin
-f6883c8ba9be6b1c0b9840943a79fb6eee7d4e5af506ea42b01a95a1c7a9134a  firmware/t-display-s3-midi-v1.0.1-20231013_0x0.bin
-809949416716286a5b2db0821608251a1d69463ceea5721ccc5598a7fd841a5c  tft-espi/Setup206_LilyGo_T_Display_S3.h
-529abb0314591c5f3c31f517f32b9af98b19cb5e240784e22939512e0d65281a  originals/boards-lilygo-t-display-s3.json
-d0ce207e8bdea5f36e682ab143297f97869ef8302ee757a9ef802d1b8f882cb9  originals/platformio.ini
-c400cc8dcc1ccf28a6f3bba00483b64230f9d6d074490cc516a6278ef5fe90f0  originals/LilyGo-Display-IDF-product_pins.h
-EOF
-```
-
-**The two identical firmware hashes are not a copy-paste error** — see
-[`../factory-firmware.md`](../factory-firmware.md) §2.
-
-## 2. Component datasheets
-
-Filed under their components, not here, per repository policy:
-
-| Artifact | Destination |
-|---|---|
-| `ST7789V_SPEC_V1.4.pdf` | [`components/sitronix/st7789v/artifacts/`](../../../../components/sitronix/st7789v/artifacts/) |
-| CST816S register guide | [`components/hynitron/cst816d/artifacts/`](../../../../components/hynitron/cst816d/artifacts/) |
-| CST328 datasheet V2.2 | [`components/hynitron/cst328/artifacts/`](../../../../components/hynitron/cst328/artifacts/) |
-
-Reacquisition commands are in each component's own record.
-
-## 3. Not tracked — the vendor source tree
-
-**Reacquisition: automatic.** ~180 MB, one `git clone` away, and 5 MB of it is a single image
-header. Not vendored.
-
-```bash
-git clone https://github.com/Xinyuan-LilyGO/T-Display-S3.git
-cd T-Display-S3
-git checkout ec889e789b3cf093412689a143f7f37b42b56af7   # the commit every citation here uses
-```
-
-Or a single file without cloning:
-
-```bash
-curl -fsSL -H "Authorization: Bearer $(gh auth token)" \
-  https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/examples/factory/pin_config.h
-```
-
-Fallback if GitHub is unavailable: `https://codeload.github.com/Xinyuan-LilyGO/T-Display-S3/tar.gz/<sha>`,
-or the Software Heritage archive.
-
-## 4. Not tracked — market data
-
-```bash
-curl -sS -A 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36' \
-  'https://lilygo.cc/collections/all/products.json?limit=250&page=1'
-```
-**Reacquisition: automatic, but the data changes daily.** The 2026-09-07 snapshot is in
-scratch; the derived table is in [`../market-and-pricing.md`](../market-and-pricing.md).
-
-## 5. Validation
-
-Never trust a file extension — LilyGO's CDN and GitHub redirects have both been known to serve
-HTML for missing paths.
-
-```bash
-python3 scratch/lilygo-t-display-s3/magic.py <files...>   # magic bytes, size, SHA-256
-```
-
-`file(1)` was **not available** on the host used for this pass, which is why a replacement
-exists. Every artifact in this record passed; no HTML was retained under a binary extension.
-
-## 6. Expected failure modes
-
-| Symptom | Cause | Action |
-|---|---|---|
-| HTTP 403 with `X-RateLimit-Remaining: 0` | GitHub API limit, not bot-blocking | authenticate; do **not** rotate User-Agent |
-| HTTP 404 on `raw.githubusercontent.com` | the commit or path is wrong | LilyGO force-pushes; re-resolve the tip with `gh api repos/…/commits/<branch>` and record the new SHA |
-| `products.json` returns HTML | Shopify bot protection | retry with the browser User-Agent above |
-| Default branch is not `main`/`master` | **normal for LilyGO** — `T-Display-S3-Long` defaults to `T-Display-S3-Long-cst3530`, `T-Display-S3-AMOLED-1.64` to `arduino-esp32-libs_V2.0.14` | always read `.default_branch`; never assume |
diff --git a/devices/lilygo/t-display-s3/acquisition/manifest.json b/devices/lilygo/t-display-s3/acquisition/manifest.json
deleted file mode 100644
index 34beb7e..0000000
--- a/devices/lilygo/t-display-s3/acquisition/manifest.json
+++ /dev/null
@@ -1,473 +0,0 @@
-{
-  "schema": "hardware-doc/acquisition-manifest/1",
-  "device": "devices/lilygo/t-display-s3",
-  "generated": "2026-09-07",
-  "note": "Board-level artifacts are stored once in devices/lilygo/t-display-s3-shared/ because they also cover the Touch variant. Chip datasheets are filed under their component records and manifested there.",
-  "artifacts": [
-   {
-     "id": "fcc-2ASYE-T-DISPLAY-S3-6272040",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-S3/Test-Report/Antenna-Report-6272040.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272040",
-      "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272040.pdf",
-      "https://fccid.io/2ASYE-T-DISPLAY-S3",
-      "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/Test-Report/Antenna-Report-6272040.pdf"
-     ],
-     "sha256": "45b9998b58613e2b69ba1478a665fb71f5d9fa40824f104fd5f44bf5ea73fae9",
-     "bytes": 1054223,
-     "destination": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2022-12-12",
-     "fcc_id": "2ASYE-T-DISPLAY-S3",
-     "fcc_document_id": "6272040",
-     "exhibit_type": "Test Report",
-     "exhibit_title_as_filed": "Antenna Report",
-     "grant_date": "2022-12-12",
-     "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf",
-     "placeholder": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/lilygo/t-display-s3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2ASYE-T-DISPLAY-S3-6272036",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-S3/External-Photos/External-Photos-6272036.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272036",
-      "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272036.pdf",
-      "https://fccid.io/2ASYE-T-DISPLAY-S3",
-      "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/External-Photos/External-Photos-6272036.pdf"
-     ],
-     "sha256": "017b0f56a7b17f1b9601d5a27acd877fc88609c4e51cfff9cf11a4c7f5acd990",
-     "bytes": 164139,
-     "destination": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2022-12-12",
-     "fcc_id": "2ASYE-T-DISPLAY-S3",
-     "fcc_document_id": "6272036",
-     "exhibit_type": "External Photos",
-     "exhibit_title_as_filed": "External Photos",
-     "grant_date": "2022-12-12",
-     "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf",
-     "placeholder": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/lilygo/t-display-s3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2ASYE-T-DISPLAY-S3-6272037",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-S3/Internal-Photos/Internal-Photos-6272037.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272037",
-      "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272037.pdf",
-      "https://fccid.io/2ASYE-T-DISPLAY-S3",
-      "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/Internal-Photos/Internal-Photos-6272037.pdf"
-     ],
-     "sha256": "3bc9aeeaa4b61bb52e5d1ac3be9d87c18c9df3a40a4be03dcc5b51339b868fc1",
-     "bytes": 365798,
-     "destination": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-internal-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2022-12-12",
-     "fcc_id": "2ASYE-T-DISPLAY-S3",
-     "fcc_document_id": "6272037",
-     "exhibit_type": "Internal Photos",
-     "exhibit_title_as_filed": "Internal Photos",
-     "grant_date": "2022-12-12",
-     "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/lilygo/t-display-s3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2ASYE-T-DISPLAY-S3-6272047",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-S3/Label/Label-Label-Location-6272047.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272047",
-      "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272047.pdf",
-      "https://fccid.io/2ASYE-T-DISPLAY-S3",
-      "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/Label/Label-Label-Location-6272047.pdf"
-     ],
-     "sha256": "9db9d7aa37227ff33d2b00796cd128455a04ea29b78c0d1359826032ed38269f",
-     "bytes": 93568,
-     "destination": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-label-label-location.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2022-12-12",
-     "fcc_id": "2ASYE-T-DISPLAY-S3",
-     "fcc_document_id": "6272047",
-     "exhibit_type": "ID Label/Location Info",
-     "exhibit_title_as_filed": "Label & Label Location",
-     "grant_date": "2022-12-12",
-     "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/lilygo/t-display-s3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2ASYE-T-DISPLAY-S3-6272046",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY-S3/User-Manual/User-Manual-6272046.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272046",
-      "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272046.pdf",
-      "https://fccid.io/2ASYE-T-DISPLAY-S3",
-      "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/User-Manual/User-Manual-6272046.pdf"
-     ],
-     "sha256": "8aaf7b92dc11ea5fb046481b015b4e9974dbb0c723a4c74410b0366cbf3143d8",
-     "bytes": 1020247,
-     "destination": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2022-12-12",
-     "fcc_id": "2ASYE-T-DISPLAY-S3",
-     "fcc_document_id": "6272046",
-     "exhibit_type": "Users Manual",
-     "exhibit_title_as_filed": "User Manual",
-     "grant_date": "2022-12-12",
-     "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf",
-     "placeholder": "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/lilygo/t-display-s3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-      "id": "sch-tds3",
-      "kind": "schematic",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/schematic/T_Display_S3.pdf",
-      "sha256": "607b63300636521fc78fbb36ed371ac10e81e3145ffa770784f45c2bf52e08c9",
-      "bytes": 395064,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/schematic/T_Display_S3.pdf",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "Single sheet, title block 2024-04-29. Only published schematic for this board. Disagrees with a shipping board on the charger (conflict G2)."
-    },
-    {
-      "id": "sch-midi",
-      "kind": "schematic",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf",
-      "sha256": "c3d5651d79b933d0995f294caeb60f4ee0c5f59090a531f13915868d125c7ce6",
-      "bytes": 693393,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/schematic/SCH_T-Display-S3-MIDI_V1.1.pdf",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "MIDI shield add-on (store SKU H656)."
-    },
-    {
-      "id": "fw-touch",
-      "kind": "firmware",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/firmware/t-display-s3-touch-20230417_0x0.bin",
-      "sha256": "f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa",
-      "bytes": 1601328,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-touch-20230417_0x0.bin",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "Merged image, flash offset 0x0. BYTE-IDENTICAL to fw-notouch. 8MB partition layout on a 16MB board. arduino-lib-builder / ESP-IDF v4.4.4, core build Feb 8 2023."
-    },
-    {
-      "id": "fw-notouch",
-      "kind": "firmware",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/firmware/t-display-s3-no-touch-20231013_0x0.bin",
-      "sha256": "f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa",
-      "bytes": 1601328,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-no-touch-20231013_0x0.bin",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "Intentional duplicate: retained despite an identical hash to fw-touch BECAUSE the duplication is the finding (conflict G1). Both upstream paths exist."
-    },
-    {
-      "id": "fw-lvgl",
-      "kind": "firmware",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/firmware/t-display-s3-lvgl-demo-20250109_0x0.bin",
-      "sha256": "4af91e520a3f5037d9b0420aa620f8736e4e6469601098fea6eb4985323d847f",
-      "bytes": 675920,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-lvgl-demo-20250109_0x0.bin",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "Newest factory image (2025-01-09), still built on ESP-IDF v4.4.6 = arduino-esp32 2.0.14. 16MB partition layout."
-    },
-    {
-      "id": "fw-tftespi",
-      "kind": "firmware",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/firmware/t-display-s3-tft-espi-20231113_0x0.bin",
-      "sha256": "45385b2a90070a7616b7fceca553d60ca984e33115f4b9586a5ebb6ddb8213f1",
-      "bytes": 501520,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-tft-espi-20231113_0x0.bin",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "ESP-IDF v4.4.5."
-    },
-    {
-      "id": "fw-screendetect",
-      "kind": "firmware",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/firmware/t-display-s3-screen-detect-20230315_0x0.bin",
-      "sha256": "2f0cf68a3ac19cec982735d7ccbcb93e522e65c9d8736e440efbf4001f9707fd",
-      "bytes": 489616,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-screen-detect-20230315_0x0.bin",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "Smallest image; exists to prove the panel works. Best first diagnostic."
-    },
-    {
-      "id": "fw-midi101",
-      "kind": "firmware",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/firmware/t-display-s3-midi-v1.0.1-20231013_0x0.bin",
-      "sha256": "f6883c8ba9be6b1c0b9840943a79fb6eee7d4e5af506ea42b01a95a1c7a9134a",
-      "bytes": 971824,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/firmware/t-display-s3-midi-v1.0.1-20231013_0x0.bin",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "MIDI shield firmware."
-    },
-    {
-      "id": "setup206",
-      "kind": "source",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/lib/TFT_eSPI/User_Setups/Setup206_LilyGo_T_Display_S3.h",
-      "sha256": "809949416716286a5b2db0821608251a1d69463ceea5721ccc5598a7fd841a5c",
-      "bytes": 906,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "FreeBSD/BSD-2 (TFT_eSPI upstream); shipped inside an MIT repository",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "The file that must be selected by hand in TFT_eSPI/User_Setup_Select.h. Vendored copy; upstream TFT_eSPI may differ."
-    },
-    {
-      "id": "boardjson",
-      "kind": "source",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/boards/lilygo-t-display-s3.json",
-      "sha256": "529abb0314591c5f3c31f517f32b9af98b19cb5e240784e22939512e0d65281a",
-      "bytes": 855,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/originals/boards-lilygo-t-display-s3.json",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "PlatformIO board manifest: qio_opi, default_16MB.csv, USB VID/PID 303A:1001."
-    },
-    {
-      "id": "pioini",
-      "kind": "source",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/platformio.ini",
-      "sha256": "d0ce207e8bdea5f36e682ab143297f97869ef8302ee757a9ef802d1b8f882cb9",
-      "bytes": 7981,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/originals/platformio.ini",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository LICENSE); artifact-specific terms unstated",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/LICENSE",
-      "redistribution_status": "conditional",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "Pins espressif32@6.5.0 (= arduino-esp32 2.0.14) and carries the five load-bearing build flags."
-    },
-    {
-      "id": "productpins",
-      "kind": "source",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/LilyGo-Display-IDF/b1a1cc54994bf1b417e3bb30c437bbe1036bff7f/main/product_pins.h",
-      "sha256": "c400cc8dcc1ccf28a6f3bba00483b64230f9d6d074490cc516a6278ef5fe90f0",
-      "bytes": 13544,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/originals/LilyGo-Display-IDF-product_pins.h",
-      "retrieved": "2026-09-07",
-      "upstream_version": "commit b1a1cc54994bf1b417e3bb30c437bbe1036bff7f",
-      "license": "MIT",
-      "license_evidence": "https://github.com/Xinyuan-LilyGO/LilyGo-Display-IDF/blob/b1a1cc5/LICENSE",
-      "redistribution_status": "allowed",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO/LilyGo-Display-IDF",
-      "commit": "b1a1cc54994bf1b417e3bb30c437bbe1036bff7f",
-      "reacquisition": "automatic",
-      "notes": "Pin maps for nine boards behind CONFIG_LILYGO_* switches. The best cross-variant primary source in the family."
-    },
-    {
-      "id": "orgrepos",
-      "kind": "metadata",
-      "canonical_url": "gh api orgs/Xinyuan-LilyGO/repos?per_page=100&page=N",
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/lilygo/t-display-s3-shared/artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv",
-      "retrieved": "2026-09-07",
-      "upstream_version": "live API, 254 repositories",
-      "license": "factual metadata",
-      "license_evidence": null,
-      "redistribution_status": "allowed",
-      "disposition": "repository",
-      "repo_state": "unstaged",
-      "upstream_repo": "Xinyuan-LilyGO",
-      "commit": null,
-      "reacquisition": "automatic",
-      "notes": "The family-enumeration evidence. Hash is null because the content changes with every vendor push; the retrieval date identifies it."
-    },
-    {
-      "id": "fw-midi100",
-      "kind": "firmware",
-      "canonical_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/firmware/t-display-s3-midi-v1.0.0-20231013_0x0.bin",
-      "sha256": null,
-      "bytes": 902784,
-      "destination": null,
-      "retrieved": null,
-      "upstream_version": "commit ec889e789b3cf093412689a143f7f37b42b56af7",
-      "license": "MIT (repository)",
-      "license_evidence": null,
-      "redistribution_status": "conditional",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "upstream_repo": "Xinyuan-LilyGO/T-Display-S3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "reacquisition": "automatic",
-      "notes": "Superseded by v1.0.1. Size known from the git tree listing; not downloaded, so no hash. The v1.0.0 -> v1.0.1 delta is uncharacterised."
-    },
-    {
-      "id": "shopfeed",
-      "kind": "market-data",
-      "canonical_url": "https://lilygo.cc/collections/all/products.json?limit=250&page=1",
-      "sha256": null,
-      "bytes": 2503053,
-      "destination": "scratch/lilygo-t-display-s3/shop-products.jsonl",
-      "retrieved": "2026-09-07",
-      "upstream_version": "feed updated_at 2026-09-07",
-      "license": "vendor store data; not licensed for redistribution",
-      "license_evidence": null,
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "untracked",
-      "upstream_repo": null,
-      "commit": null,
-      "reacquisition": "automatic",
-      "notes": "214 products with dated prices and stock. Requires a browser User-Agent. Changes daily; the derived table in market-and-pricing.md is the durable artifact."
-    }
-  ]
-}
diff --git a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf.ARCHIVED.md
deleted file mode 100644
index d39d5ec..0000000
--- a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-S3-antenna-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,054,223 B (1.01 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,054,223 B (1.01 MiB) |
-| SHA-256 | `45b9998b58613e2b69ba1478a665fb71f5d9fa40824f104fd5f44bf5ea73fae9` |
-| FCC ID | **`2ASYE-T-DISPLAY-S3`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Report |
-| FCC document id | 6272040 |
-| Upstream publication date | 2022-12-12 |
-| Grant date | 2022-12-12 |
-| Equipment class | T-Display-S3, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-S3/Test-Report/Antenna-Report-6272040.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272040>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272040.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/Test-Report/Antenna-Report-6272040.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf" \
-   "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-antenna-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-S3/Test-Report/Antenna-Report-6272040.pdf" -o "2ASYE-T-DISPLAY-S3-antenna-report.pdf"
-echo "45b9998b58613e2b69ba1478a665fb71f5d9fa40824f104fd5f44bf5ea73fae9  2ASYE-T-DISPLAY-S3-antenna-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 68a6079..0000000
--- a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-S3-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 164,139 B (0.16 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 164,139 B (0.16 MiB) |
-| SHA-256 | `017b0f56a7b17f1b9601d5a27acd877fc88609c4e51cfff9cf11a4c7f5acd990` |
-| FCC ID | **`2ASYE-T-DISPLAY-S3`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 6272036 |
-| Upstream publication date | 2022-12-12 |
-| Grant date | 2022-12-12 |
-| Equipment class | T-Display-S3, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-S3/External-Photos/External-Photos-6272036.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272036>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272036.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/External-Photos/External-Photos-6272036.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf" \
-   "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-S3/External-Photos/External-Photos-6272036.pdf" -o "2ASYE-T-DISPLAY-S3-external-photos.pdf"
-echo "017b0f56a7b17f1b9601d5a27acd877fc88609c4e51cfff9cf11a4c7f5acd990  2ASYE-T-DISPLAY-S3-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-internal-photos.pdf b/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-internal-photos.pdf
deleted file mode 100644
index 3ec564b..0000000
Binary files a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-label-label-location.pdf b/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-label-label-location.pdf
deleted file mode 100644
index f9df93a..0000000
Binary files a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-label-label-location.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf.ARCHIVED.md b/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 89cd108..0000000
--- a/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-S3-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,020,247 B (0.97 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,020,247 B (0.97 MiB) |
-| SHA-256 | `8aaf7b92dc11ea5fb046481b015b4e9974dbb0c723a4c74410b0366cbf3143d8` |
-| FCC ID | **`2ASYE-T-DISPLAY-S3`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 6272046 |
-| Upstream publication date | 2022-12-12 |
-| Grant date | 2022-12-12 |
-| Equipment class | T-Display-S3, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY-S3/User-Manual/User-Manual-6272046.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6272046>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY-S3/6272046.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY-S3/User-Manual/User-Manual-6272046.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf" \
-   "devices/lilygo/t-display-s3/artifacts/certification/2ASYE-T-DISPLAY-S3-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY-S3/User-Manual/User-Manual-6272046.pdf" -o "2ASYE-T-DISPLAY-S3-user-manual.pdf"
-echo "8aaf7b92dc11ea5fb046481b015b4e9974dbb0c723a4c74410b0366cbf3143d8  2ASYE-T-DISPLAY-S3-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-s3/artifacts/certification/README.md b/devices/lilygo/t-display-s3/artifacts/certification/README.md
deleted file mode 100644
index 678118b..0000000
--- a/devices/lilygo/t-display-s3/artifacts/certification/README.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-T-DISPLAY-S3`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-T-DISPLAY-S3`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2022-12-12** |
-| Equipment class | T-Display-S3, 2402-2480 MHz, 2412-2472 MHz |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Source page | <https://fccid.io/2ASYE-T-DISPLAY-S3> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-T-DISPLAY-S3-internal-photos.pdf` | 365,798 | `3bc9aeeaa4b61bb52e5d1ac3be9d87c18c9df3a40a4be03dcc5b51339b868fc1` | Internal Photos |
-| `2ASYE-T-DISPLAY-S3-label-label-location.pdf` | 93,568 | `9db9d7aa37227ff33d2b00796cd128455a04ea29b78c0d1359826032ed38269f` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-T-DISPLAY-S3-antenna-report.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-S3-antenna-report.pdf.ARCHIVED.md) | 1,054,223 | Test Report |
-| [`2ASYE-T-DISPLAY-S3-external-photos.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-S3-external-photos.pdf.ARCHIVED.md) | 164,139 | External Photos |
-| [`2ASYE-T-DISPLAY-S3-user-manual.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-S3-user-manual.pdf.ARCHIVED.md) | 1,020,247 | Users Manual |
-
-Archived total: **3 files, 2.13 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 0.44 MiB** |
-| Archived | **3 files, 2.13 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t-display-s3/certification-and-compliance.md b/devices/lilygo/t-display-s3/certification-and-compliance.md
deleted file mode 100644
index 9f8e01b..0000000
--- a/devices/lilygo/t-display-s3/certification-and-compliance.md
+++ /dev/null
@@ -1,178 +0,0 @@
-# Certification and compliance — t-display-s3
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-The board carries an ESP32-S3-WROOM-1 module, itself FCC-granted under Espressif's `2AC7Z`.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-T-DISPLAY-S3` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AC7Z-ESPS3WROOM1`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-DISPLAY-S3`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2022-12-12** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2022-12-12 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2472 MHz** (Wi-Fi 2.4 GHz, ch 1–13 — ⚠ wider than the usual US 1–11) |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 9 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY-S3` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Circuit Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 164,139 | `017b0f56a7b17f1b…` |
-| `ID-Label-Location-Info-Label-Label-Location.pdf` | 93,568 | `9db9d7aa37227ff3…` |
-| `Internal-Photos-Internal-Photos.pdf` | 365,798 | `3bc9aeeaa4b61bb5…` |
-| `Test-Report-Antenna-Report.pdf` | 1,054,223 | `45b9998b58613e2b…` |
-| `Users-Manual-User-Manual.pdf` | 1,020,247 | `8aaf7b92dc11ea5f…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY-S3/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY-S3/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AC7Z-ESPS3WROOM1`
-
-| Field | Value |
-|---|---|
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD |
-| Grantee code | `2AC7Z` — registered 2014-09-15, 78 FCC IDs total |
-| Final action date | **2026-02-27** |
-| Application purpose | Class II permissive change or modification of presently authorized equipment |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 57 available, 11 metadata-only |
-| Filing page | `https://fccid.io/2AC7Z-ESPS3WROOM1` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Block diagram [Block Diagram]
-- Schematic [Schematics]
-- Schematics [Schematics]
-- Operation description [Operational Description]
-- Operational Description [Operational Description]
-- Parts list [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up procedure [Parts List/Tune Up Info]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photo.pdf` | 1,367,037 | `a0104b88a862efd5…` |
-| `External-Photos-External-Photos.pdf` | 1,275,356 | `8fe953474e9707bc…` |
-| `External-Photos-External-photos.pdf` | 332,733 | `b04d392ae5298711…` |
-| `ID-Label-Location-Info-Label-location.pdf` | 30,758 | `68e843105466c162…` |
-| `ID-Label-Location-Info-Label.pdf` | 44,224 | `081ac1c0f3292f1b…` |
-| `ID-Label-Location-Info-Lable-and-location.pdf` | 1,437,286 | `0a57b90982013049…` |
-| `Internal-Photos-Internal-Photo.pdf` | 3,636,909 | `318d8c6c95232515…` |
-| `Internal-Photos-Internal-photos.pdf` | 338,977 | `1f60246b57db6172…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 499,298 | `b1ae557e1e78bbfa…` |
-| `RF-Exposure-Info-SAR-Report-A.pdf` | 845,988 | `54f4972a02877d9b…` |
-| `RF-Exposure-Info-SAR-Report-B.pdf` | 850,218 | `62b4f82db50809aa…` |
-| `RF-Exposure-Info-SAR-Report-C1.pdf` | 5,908,102 | `8fbf6c55dc6a0248…` |
-| `RF-Exposure-Info-SAR-Report-C2.pdf` | 3,930,042 | `4c6ed64c435d4f04…` |
-| `RF-Exposure-Info-SAR-Report-D.pdf` | 3,974,985 | `04798068d0a5ee3b…` |
-| `RF-Exposure-Info-SAR-Report.pdf` | 1,936,491 | `60f7208dd54ccff8…` |
-| `Test-Report-Antenna-specification.pdf` | 1,996,381 | `da8da91adaa5b481…` |
-| `Users-Manual-User-Manual.pdf` | 2,603,588 | `3e493b8b9ea24f00…` |
-| `Users-Manual-User-manual.pdf` | 886,672 | `f8d1d246c0c849a6…` |
-
-Held at `scratch/market-and-certification/fcc/2AC7Z-ESPS3WROOM1/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AC7Z-ESPS3WROOM1/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-s3/commands.md b/devices/lilygo/t-display-s3/commands.md
deleted file mode 100644
index de1dd37..0000000
--- a/devices/lilygo/t-display-s3/commands.md
+++ /dev/null
@@ -1,147 +0,0 @@
-# T-Display-S3 — command ledger
-
-Every command that mattered, with status. **No hardware was attached**, so board-side commands
-are `reported-working` or `inferred`, never `executed-success`.
-
-Environment for everything marked `executed-success`: Linux, bash, Python 3.11+, `gh` CLI
-authenticated, `curl`. Date 2026-09-07.
-
-## Acquisition
-
-```bash
-# Enumerate the vendor's whole GitHub org (the family-enumeration evidence).
-for p in 1 2 3; do
-  gh api "orgs/Xinyuan-LilyGO/repos?per_page=100&page=$p&sort=updated" \
-    --jq '.[] | [.name,.pushed_at,.default_branch,.stargazers_count,(.description//"")] | @tsv'
-done
-```
-`executed-success` — 254 rows. Uses the token, which lifts the API limit from 60/h to 5 000/h;
-without it this call alone can exhaust the anonymous quota.
-
-```bash
-# Pin a repository to a commit before fetching anything from it.
-gh api repos/Xinyuan-LilyGO/T-Display-S3/commits/main --jq '.sha'
-#   -> ec889e789b3cf093412689a143f7f37b42b56af7
-
-# Recursive tree listing at that commit (one call instead of hundreds).
-gh api "repos/Xinyuan-LilyGO/T-Display-S3/git/trees/ec889e78…?recursive=1" \
-  --jq '.tree[] | [.type,.size//0,.path] | @tsv'
-```
-`executed-success` — 3 431 entries.
-
-```bash
-# Fetch a file at a pinned commit. raw.githubusercontent is not the API and is far
-# more permissive; still send the token.
-curl -fsSL -H "Authorization: Bearer $(gh auth token)" \
-  "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e78…/examples/factory/pin_config.h"
-```
-`executed-success`.
-
-## Validation
-
-```bash
-# Never trust a URL suffix. `file` was NOT available on this host; a magic-byte
-# check was written instead.
-python3 scratch/lilygo-t-display-s3/magic.py <paths...>
-```
-`executed-success`. Output columns: detected type, byte size, SHA-256, path. Every artifact in
-this record passed; **no HTML error page was retained under a `.pdf` or `.bin` name.**
-
-```bash
-sha256sum <file>; stat -c%s <file>
-```
-`executed-success`. This is what found [G1](gaps-and-conflicts.md#g1--the-touch-and-no-touch-factory-images-are-byte-identical).
-
-<a id="decoding-an-esp32-app-descriptor"></a>
-## Decoding an ESP32 app descriptor from a merged image
-
-The repository's own [`tools/esp_image_info.py`](../../../tools/esp_image_info.py) reads the
-image header correctly but reports *"no app descriptor"* on these files, because a **merged**
-image has the bootloader at `0x0` and the app at `0x10000` — the descriptor is at `0x10020`,
-not `0x20`. That is a real limitation worth recording rather than working around silently.
-
-```bash
-python3 tools/esp_image_info.py <merged.bin>          # bootloader header: chip, flash size/mode
-python3 scratch/lilygo-t-display-s3/appdesc.py <merged.bin>   # scans for magic 0xABCD5432
-```
-Both `executed-success`. The second also decodes the partition table at `0x8000`
-(entry magic `0xAA50`, 32-byte records), which is how the 8 MB-vs-16 MB layout split in
-[`factory-firmware.md`](factory-firmware.md) §3 was found.
-
-## Reading an Altium schematic PDF without poppler
-
-`pdftotext`, `pdftoppm`, `qpdf`, `mutool` and `pypdf` were **all unavailable**, and there is no
-package manager on the host. A minimal extractor was written instead:
-
-```bash
-python3 scratch/lilygo-t-display-s3/pdfall.py <sheet.pdf>   # WinAnsi fonts, Form XObjects
-python3 scratch/lilygo-t-display-s3/pdfcid.py <sheet.pdf>   # Type0/Identity-H via ToUnicode CMap
-```
-`executed-success`, with two lessons worth carrying forward:
-
-1. **Altium puts the whole sheet in a Form XObject**, so reading `/Contents` alone returns only
-   the `PI…`/`CO…` pin markers and none of the labels. You must walk every stream in the file.
-2. **Text must be grouped by `BT…ET` block.** Reading `Tj`/`TJ` operators individually
-   shreds every label into single characters, which is what the first attempt did.
-
-**Both extractors were cross-checked against each other** on the Chipone CO5300 datasheet,
-which uses a **uniform +0x1D code-point offset** — the exact "human-legible but wrong" trap the
-research skill warns about. The raw route yielded `&+,321(7HFKQRORJ\` and the CMap route
-yielded `FHHPONE TecOnology`; both decode to **CHIPONE Technology**, and neither is readable as
-written. Recorded in [`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md).
-
-**Not done:** net-level connectivity. `tools/altium_pdf_netlist.py` needs `pdftotext -bbox`
-XML. `inferred` blocker; see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) K1.
-
-```bash
-# The command that would close K1, once poppler exists:
-for p in $(seq 1 1); do pdftotext -bbox -f $p -l $p T_Display_S3.pdf pdf/bbox-p$p.xml; done
-python3 tools/altium_pdf_pin_table.py 1 U2
-```
-`not-tested` — poppler absent.
-
-## Market data
-
-```bash
-curl -sS -A 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) …Chrome/131…' \
-  'https://lilygo.cc/collections/all/products.json?limit=250&page=1'
-```
-`executed-success` — 214 products, full variant/price/stock detail. Shopify's public product
-feed is far better evidence than scraping the rendered page, and it carries `published_at`
-(the product's launch date) and per-variant `available`.
-
-```bash
-# Reddit: www.reddit.com returns 403 to scripts; old.reddit.com with a link-preview UA does not.
-curl -sS -A 'WhatsApp/2.23.20.0' 'https://old.reddit.com/search.json?q=t-display-s3&limit=25&t=all'
-curl -sS -A 'WhatsApp/2.23.20.0' 'https://old.reddit.com/r/esp32/comments/<id>/.json'
-```
-`executed-success`.
-
-## Board-side commands (none executed here)
-
-```bash
-# Restore a board. reported-working (LilyGO's documented procedure).
-esptool.py --chip esp32s3 --port /dev/ttyACM0 erase_flash
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-    write_flash -z 0x0 t-display-s3-lvgl-demo-20250109_0x0.bin
-
-# Identify a board. inferred (standard esptool usage, not run against this board).
-esptool.py --chip esp32s3 --port /dev/ttyACM0 flash_id
-
-# Build and flash the vendor examples. reported-working.
-pio run -e factory
-pio run -e factory -t upload
-pio device monitor -b 115200
-```
-
-The port is **`/dev/ttyACM*`** (CDC-ACM), not `/dev/ttyUSB*` — there is no UART bridge. See
-[`features/usb.md`](features/usb.md).
-
-## Failed / abandoned
-
-| Command | Result | Diagnosis |
-|---|---|---|
-| `file -b --mime-type <f>` | `file: command not found` | not installed; replaced by `magic.py` |
-| `pip install pypdf` | `pip: command not found` | no Python package manager; extractors written from scratch |
-| `gh api search/code -f q='repo:arendst/Tasmota t-display-s3'` | HTTP 404 | GitHub code search does not index every repo for every query shape. `repo:arendst/Tasmota lilygo` worked and returned 19 hits |
-| `gh api -X GET search/code -f q='org:meshtastic t-display-s3'` | HTTP 404 | hyphenated terms confuse code search; `org:meshtastic tdisplay` returned 247 hits, none a T-Display-S3 variant |
diff --git a/devices/lilygo/t-display-s3/community.md b/devices/lilygo/t-display-s3/community.md
deleted file mode 100644
index e44b791..0000000
--- a/devices/lilygo/t-display-s3/community.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# T-Display-S3 — community evidence
-
-Every item is labelled by evidence class:
-**FM** firsthand measurement · **FO** firsthand ownership/use · **DP** demonstrable project ·
-**VC** vendor confirmation · **II** informed interpretation · **HS** hearsay/unsupported.
-
-Sampling is stated where a prevalence claim would otherwise be implied. **No claim below is a
-prevalence claim** unless it names its sample.
-
-## The issue tracker is the primary community source
-
-318 issues on `Xinyuan-LilyGO/T-Display-S3`, retrieved 2026-09-07. Selection rule for deep
-reading: **≥5 comments or ≥2 reactions**, then filtered for technical content → 56 candidates,
-22 read in full.
-
-Nearly all are closed, most by a stale-bot after 30 + 14 days. **The bot closes threads, not
-questions** — several of the most valuable findings sit in threads marked "closed as inactive".
-
-### Highest-value threads
-
-| # | Title | Date | c | Finding | Class |
-|---|---|---|---|---|---|
-| [230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230) | T-Display-S3 Battery Charge Circuit? | 2024-03-02 | 9 | Owner traced the PCB: the charger is **a 5-lead TSOT-23 marked `65b311`**, not the SOP-8 part in the schematic. Also the correct `analogReadMilliVolts` recipe. LilyGO confirms **no battery protection** (2025-02-06) | **FM + VC** |
-| [313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313) | Pins 16 and 17 in floating mode | 2025-07-28 | 11 | Fitted pull-ups on GPIO16/17 **on non-touch boards**; pins go high again on deep-sleep entry. LilyGO answered **with two PCB photographs** and offered removal instructions | **FO → VC** |
-| [190](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/190) | Measure BAT_ADC incorrect voltage | 2023-09-22 | 17 | ESP-IDF `raw*3.3/4096` gave **2.14 V** against a multimeter's **3.9 V**. Wrong in a plausible-looking way | **FM** |
-| [212](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212) | Firmware_no_Touch is the same as Touch? | 2024-01-02 | 9 | Independent notice of the byte-identical firmware pair; **and** the `User_Setup_Select.h` overwrite fix, which resolved the reporter's problem | **FO** |
-| [42](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/42) | Can not charge the battery via IO PIN | 2022-11-07 | 10 | `VBUS` not on the header. LilyGO: *"We have not considered this situation. Maybe you can solve it by soldering a wire from VBUS."* Later (2023-11-01) a firsthand back-powering hazard report | **FO + VC** |
-| [79](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/79) | If you are having difficulty with your new T-Display S3 | 2023-01-03 | 11 | The GPIO15 trap, and the community guide that documents it. LilyGO's maintainer thanked the author in-thread | **DP + VC** |
-| [313→](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/326) 326 | TFT_eSPI Setup206 `#error` | 2026-02-23 | 11 | The `User_Setup_Select.h` problem now fails loudly at compile time rather than silently at runtime | **FO** |
-| [18](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/18) | Tasmota support | 2022-10-06 | 25, 4👍 | Tasmota works via `Tasmota32-S3 (QIO/OPI)` + the "Lilygo S3 Display" template. **`displaydimmer 100` is required** or the screen looks dead. A Tasmota maintainer participated | **FO** |
-| [151](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/151) | Black screen with TFT | 2023-05-19 | **32** | The single largest thread on the repo, and it is the `User_Setup_Select.h`/GPIO15 pair again | **FO** |
-| [205](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/205) | Power with external 3.3 V / 5 V | 2023-11-30 | 22 | Supported inputs are USB-C and the JST connector only. Answers are **community**, not vendor | **II** |
-| [181](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/181) | None of my Qwiic sensors is recognized | 2023-08-08 | 12 | The SH1.0 connector is **not** Qwiic pin-compatible | **FO** |
-| [168](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/168) | Constant I²C errors with touch | 2023-06-29 | 21 | CST parts NAK while idle | **FO** |
-| [12](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/12) | Where is the schematic for this board | 2022-09-19 | 9, **7👍** | The most-upvoted issue on the repo is *"please publish the schematic"* — a fair summary of the documentation culture | **—** |
-
-### Recurring themes, with counts from the read sample
-
-Of the **22 threads read in full**:
-
-| Root cause | Threads |
-|---|---|
-| `User_Setup_Select.h` not selecting Setup206 | 5 |
-| GPIO15 not driven | 4 |
-| Battery / charging / ADC | 5 |
-| `USB CDC On Boot` or port enumeration | 4 |
-| Wi-Fi range or connection | 2 |
-| Flash size / partition scheme | 2 |
-
-Those are counts **within the deliberately biased sample** (selected for engagement), not
-across all 318 issues. They indicate what generates long threads, not what happens most often.
-
-## Reddit
-
-Search method: `old.reddit.com/search.json` with a link-preview User-Agent (the standard
-`www.reddit.com` path returns 403 to scripts), four query shapes, `t=all`, 25 results each →
-**27 family-relevant posts**. Two threads read in full.
-
-### The single most useful community post
-
-[r/esp32, 2026-05-25, "LilyGo T-Display S3 Clock with DS18B20 and PIR — lessons learned"](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/)
-
-| Claim | Class | Note |
-|---|---|---|
-| "GPIO 43 and 44 are blocked by UART0 in Arduino IDE **even when using Hardware CDC**" | **FM, independently reproduced** | A second commenter (`u/MrBoomer1951`) initially disputed it, tested, and retracted: *"OKAY! I just tried it and it does not work on 43 or 44! TIL"*. This is the strongest single piece of community evidence in the whole record |
-| "`ledcSetup` and `ledcAttachPin` are deprecated in core 3.x — use `ledcAttach`/`ledcDetach`" | **FM** | Confirms the core-3.x break extends past TFT_eSPI |
-| "needs **both** GPIO 15 (LCD power) and GPIO 38 (backlight) set HIGH" | **FO** | Matches the vendor README |
-| "5 GHz WiFi doesn't work on ESP32-S3" | **II** | Correct, and silicon-level, not board-level |
-| "The UART0 pins can be used if you disabled it in sdkconfig (esp-idf). Harder to do in Arduino." | **II, untested** | A plausible workaround nobody in-thread verified |
-| MakerFocus 3.7 V 1000 mAh #952540 fits a printed backpack for the LilyGO shell | **FO** | A dated, specific, working battery combination — rare and useful |
-
-### Visibility, dated
-
-| Post | Sub | Date | Score |
-|---|---|---|---|
-| ESP32 Internet Weather Station | r/esp32 | 2024-08-16 | 1312↑ / 68c |
-| DIY auto gauge UI (LVGL) | r/esp32 | 2025-03-11 | 840↑ / 61c |
-| "Finally AMOLED display on the development board" | r/arduino | 2023-05-31 | 987↑ / 76c |
-| same, cross-posted | r/esp32 | 2023-05-31 | 400↑ / 32c |
-| "This is T-display S3… internet weather station" | r/arduino | 2023-05-20 | 583↑ / 17c |
-| "The LILYGO T-Display-S3 Amoled is quite good" | r/Esphome | 2024-10-19 | 65↑ |
-| Bitcoin ticker on the AMOLED | r/esp32 | 2024-09-11 | 184↑ |
-
-**Interpretation, offered as interpretation:** the high-scoring posts are almost all *finished
-projects with a photograph*, and the help requests score near zero. Reddit is where this board
-is shown off; GitHub is where it is debugged.
-
-### A negative result worth keeping
-
-[r/arduino, 2026-06-11, "T-Display S3 AMOLED Touch schematics accurate?"](https://old.reddit.com/r/arduino/comments/1u3et4u/tdisplay_s3_amoled_touch_schematics_accurate/) —
-an owner reported that driving GPIO13 broke touch on an AMOLED Touch board, suspected the
-schematic was wrong, and **two days later retracted**: *"today, I cannot reproduce the
-behavior. Must have been something else."* Recorded because the thread is findable, the
-retraction is not prominent, and the intermediate hypothesis (that LilyGO's schematic is wrong
-about GPIO13) would otherwise propagate. The thread also surfaced `LilyGo-Display-IDF`'s
-`product_pins.h` — which turned out to be one of the best sources in this whole pass.
-
-## Not searched
-
-Hackaday, YouTube, Bilibili/Zhihu/CSDN, the ESP32 forum, and Discord. Deliberate exclusions,
-recorded in [`research-log.md`](research-log.md).
diff --git a/devices/lilygo/t-display-s3/comparisons-and-recommendations.md b/devices/lilygo/t-display-s3/comparisons-and-recommendations.md
deleted file mode 100644
index 075a412..0000000
--- a/devices/lilygo/t-display-s3/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,164 +0,0 @@
-# T-Display-S3 — comparisons and recommendations
-
-> Dated **2026-09-07**. Prices are official-store, region "China [For Worldwide]", excluding
-> shipping and tax, on that date. Comparisons are scoped to a stated workload; nothing here
-> calls two boards "equivalent" without saying at what.
-
-## 1. Against boards already documented in this repository
-
-| | **LilyGO T-Display-S3** | [Waveshare ESP32-S3-Knob-Touch-LCD-1.8](../../waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) | [Seeed XIAO ESP32S3 Sense](../../seeed-studio/xiao-esp32s3-sense/README.md) | [M5Stack Cardputer ADV](../../m5stack/cardputer-adv/README.md) |
-|---|---|---|---|---|
-| Price, 2026-09-07 | **USD 9.04** | not re-checked this pass | not re-checked this pass | not re-checked this pass |
-| SoC | ESP32-S3R8 | ESP32-S3R8 **+ ESP32-U4WDH** | ESP32-S3R8 | ESP32-S3 |
-| Flash / PSRAM | 16 MB / 8 MB OPI | 16 MB / 8 MB | 8 MB / 8 MB | — |
-| Display | 1.9″ **170×320** IPS, ST7789V | 1.8″ **360×360** round | **none** | 1.14″ 240×135 |
-| Display bus | **8-bit 8080 parallel** | QSPI | — | SPI |
-| Touch | optional, +USD 3.57 | yes, CST816D | — | — |
-| Audio in | — | PDM mic | **PDM mic** | mic + codec |
-| Audio out | — | PCM5100A DAC → 3.5 mm | — | codec + speaker + 3.5 mm |
-| Camera | — | — | **OV2640** | — |
-| microSD | shield only, 1-bit | 4-bit SDMMC | yes | yes |
-| Keyboard | — | 2 knobs | — | **56 keys** |
-| IMU | — | — | — | yes |
-| Battery | JST 1.25, unprotected, ~500 mA charge | optional LiPo | pads | single large cell |
-| Classic Bluetooth | **no** | **yes**, via the U4WDH | no | no |
-| Size class | 62 × 26 mm | round knob | 21 × 17.8 mm | 84 × 54 mm card |
-
-### What each is actually for
-
-- **T-Display-S3 — the cheapest good screen.** If the job is "put a colour UI on a networked
-  thing", this wins on price per pixel and on the parallel bus's refresh rate. It has almost
-  no other features, which is the point.
-- **Waveshare Knob-Touch-LCD-1.8 — the only one with Classic Bluetooth**, because it carries a
-  second MCU for it, and the only one with real line-out audio and haptics. Considerably more
-  complex: two MCUs, a shared DAC with a mux, and a documented controller-naming conflict.
-  Choose it when you need a *round* UI, audio, or BR/EDR.
-- **XIAO ESP32S3 Sense — the only one with a camera**, and by far the smallest. No display at
-  all. These two boards are complements, not alternatives; a common pairing is Sense for
-  capture and T-Display-S3 for the UI.
-- **Cardputer ADV — the only one that is a computer.** Keyboard, speaker, IMU, battery, case.
-  If you want to *type* on it, nothing else here comes close. If you want to embed it in
-  something, it is the wrong shape.
-
-**No performance comparison is offered**, because none of these four has a measured benchmark
-in this repository under a shared method. Saying one is "faster" would be exactly the
-unsupported comparison the method forbids.
-
-## 2. Against the obvious market rivals
-
-| Board | ~Price | Display | Why you might prefer it | Why you might not |
-|---|---|---|---|---|
-| **LilyGO T-Display-S3** | **USD 9.04** | 1.9″ 170×320 IPS, 8080 | cheapest with 16 MB + 8 MB PSRAM + bonded display | 7 free GPIOs; no SD; no protection circuit; vendor pinned to Arduino core 2.0.14 |
-| **LilyGO T-Display (ESP32)** | USD 8.04 | 1.14″ 135×240, SPI | cheaper still; huge legacy community (1 192★) | ESP32 not S3, 4 MB flash on the base SKU, smaller/slower panel |
-| **ESP32-S3-BOX / BOX-3** | ~USD 45–60 | 2.4″ 320×240 + touch | speech front-end, mic array, speaker, enclosure, first-party Espressif support | 5× the price; a product, not a component |
-| **M5Stack CoreS3** | ~USD 55 | 2.0″ 320×240 + touch | enclosure, battery, IMU, huge Unit ecosystem | 6× the price |
-| **Waveshare ESP32-S3-Touch-LCD-1.28/1.69** | ~USD 20–30 | round or 240×280 | round option; some have IMU/RTC | 2–3× the price for similar silicon |
-| **Sunton / "Cheap Yellow Display" ESP32-2432S028** | ~USD 12–15 | 2.8″ 320×240 resistive | bigger screen, SD slot, cheap | plain ESP32, resistive touch, no PSRAM on most, documentation is community-only |
-| **Bare ESP32-S3-DevKitC + separate panel** | ~USD 8 + panel | your choice | full pin freedom | you assemble and wire it; total cost rarely beats USD 9.04 |
-
-**The honest summary:** at USD 9 the T-Display-S3 has no direct competitor that includes a
-bonded 170×320 IPS panel, 16 MB flash and 8 MB PSRAM. Everything cheaper drops one of those;
-everything comparable costs at least twice as much. What you pay for that is a **very** tight
-GPIO budget and a vendor whose documentation lags its hardware.
-
-## 3. Who should buy which — concrete, dated
-
-| You want to… | Buy | Why |
-|---|---|---|
-| put a networked colour UI in a box, cheaply | **T-Display-S3 `H569`, USD 9.04** | nothing else is close at this price |
-| …and poke it with a finger | **T-Display-S3 Touch `H587`, USD 12.61** | cheapest capacitive touch on any ESP32-S3 board here; check whether your board is CST816S or CST328 before writing code |
-| …with a case and a battery | `K204`/`K206` USD 13.22 + a **protected** ≥600 mAh cell | the bundled-battery SKU was out of stock 2026-09-07 |
-| a display you can read outdoors / at an angle | **T-Display-S3 AMOLED**, USD 26.44 | AMOLED contrast; but you inherit the V1.0/V2.0 question |
-| a long thin bar display (VU meter, ticker, dashboard) | **T-Display-S3 Long**, USD 29.35 | 180×640 is a shape nothing else offers; note the vendor's own header has [pin collisions](../t-display-s3-long/gaps-and-conflicts.md) |
-| a handheld with camera, microSD and 3 buttons | **T-Display-S3 Pro**, USD 37.99–56.99 | closest thing to a product in the family; **check V1.0 vs V1.1** for the backlight scale |
-| the biggest AMOLED | **T4-S3**, USD 56.89 | 450×600; sold under the T4 name, not T-Display-S3 |
-| a camera, not a display | **XIAO ESP32S3 Sense** | different job entirely |
-| something you type on | **Cardputer ADV** | different job entirely |
-| Classic Bluetooth (BR/EDR) | **not any of these** — the Waveshare Knob board, via its second MCU | the ESP32-S3 has no BR/EDR at all. This catches people |
-| LoRa / Meshtastic | **not any T-Display-S3** | no radio. Look at T-Beam, T-Deck, T3-S3, or T-Display-S3 Pro **LR1121** (USD 65.29) |
-
-## 4. Do not use a T-Display-S3 when…
-
-- **You need more than ~7 free GPIOs.** Count them first
-  ([`features/gpio-and-expansion.md`](features/gpio-and-expansion.md)). This is the number-one
-  reason people regret the choice.
-- **You need Classic Bluetooth.** ESP32-S3 is BLE-only.
-- **You need an unattended battery product.** No battery protection, no fuel gauge, a fixed
-  ~500 mA charge current, and the battery ADC reads nonsense while USB is attached.
-- **You need reliable serial on battery.** `USB CDC On Boot` forces a choice; see
-  [`features/usb.md`](features/usb.md).
-- **You need a supported, versioned platform.** There is no PCB revision scheme, no changelog,
-  and the vendor's tested Arduino core is two major versions behind.
-- **You need known Wi-Fi range.** It has never been measured, and it is the most-complained-of
-  characteristic.
-
-<a id="the-clone-question"></a>
-## 5. The clone question — worked example
-
-Method: [`guides/markets/clones-and-variants.md`](../../../guides/markets/clones-and-variants.md)
-(read for this pass; **not edited**). Applied to this board:
-
-**What "clone" means here is unusually murky, because LilyGO is itself a rebadger.** The
-company trades as *Shenzhen Xin Yuan Electronic Technology* (the copyright line in its own
-source headers), sells under **LilyGO** and historically **TTGO**, and its GitHub org is
-`Xinyuan-LilyGO`. The predecessor board is called *TTGO T-Display* in the repo and *T-Display*
-in the store. There is no "original" brand to be cloned *from* in the way there is with, say,
-an Arduino Uno.
-
-### What can be established
-
-| Test | Result |
-|---|---|
-| Does LilyGO publish a schematic? | **Yes, one sheet.** So a copyist has the design |
-| Are the design files licensed? | The **repository** is MIT. Whether that covers the PDF schematic is unstated — MIT is a software licence, and LilyGO applies no hardware licence |
-| Is there a serial number, QR or authentication? | **No.** None found on the board, in the schematic, or in the firmware |
-| Does the firmware identify the board? | **No.** The app descriptors say `arduino-lib-builder`; there is no LilyGO string, no version, no board id |
-| Is there a distinguishing USB VID/PID? | **No.** `303A:1001` is **Espressif's** native USB-Serial-JTAG identity, shared by every ESP32-S3 using the built-in USB. It proves the SoC, not the vendor |
-| Does the vendor sell through marketplaces? | Yes — a Banggood coupon for the AMOLED board was posted to Reddit on 2024-11-30. So a marketplace listing is **not** evidence of a clone |
-
-### What follows
-
-**There is no reliable way to tell a genuine LilyGO T-Display-S3 from a competent copy**, and
-this record does not claim one exists. The available discriminators are all weak:
-
-- **Silkscreen and logo.** Present on genuine boards; trivially copied.
-- **LED behaviour.** LilyGO documents specific charge-LED semantics (dim/flashing with no
-  battery, solid charging, off when full). A copy using a different charger will behave
-  differently. **This is behavioural evidence, and it is the strongest cheap test available** —
-  but it fails against a copy that uses the same charger.
-- **The `65b311` charger marking.** Since even LilyGO's own schematic does not match its own
-  board here, chip markings cannot distinguish genuine from copy without a known-good
-  reference.
-- **Price.** A listing far under USD 9 for a bare board is suspicious in the sense that
-  margins are already thin; it is not proof.
-
-**The practical risk is not counterfeiting, it is silent revision drift** — which affects
-genuine boards too, and is documented at
-[`../t-display-s3-shared/board-revision-drift.md`](../t-display-s3-shared/board-revision-drift.md).
-Treat any board you did not buy from LilyGO directly as an **unidentified member of the
-T-Display-S3 set**, run the identification checklist in that document, and write code that
-probes rather than assumes.
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered. ⚠ This file was last modified less than an hour before
-this append; the section was added at the end of the file only, and nothing else in
-this tree was touched.
-
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — the T-Display-S3 family in a display-dev-board group against the Waveshare
-  ESP32-S3-Knob-Touch-LCD-1.8 and the XIAO ESP32S3 Sense, with the family's three
-  traps (the `USB CDC On Boot` block, the Arduino-core 2.0.14 pin, the display-bus
-  split) carried through, and the note that **two boards in the family declare no
-  licence at all**.
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — this board is the price anchor for the guide's central argument: **$9.04 buys
-  an ESP32-S3 with 16 MB flash and 8 MB OPI PSRAM *and* a colour LCD**, the same
-  memory configuration as a $65 PaperMono and a $99 Xteink X4 Pro. PSRAM is not
-  what makes an e-ink device expensive, so choosing an `R8` over a no-PSRAM part is
-  close to free — and the C3's memory ceiling is the most expensive constraint in
-  this repository measured in developer time. The guide also carries this family's
-  **GPIO26–37 / GPIO33–37 OPI-PSRAM pin cost** as the practical price of `R8`.
diff --git a/devices/lilygo/t-display-s3/compatibility-and-status.md b/devices/lilygo/t-display-s3/compatibility-and-status.md
deleted file mode 100644
index d3d3f04..0000000
--- a/devices/lilygo/t-display-s3/compatibility-and-status.md
+++ /dev/null
@@ -1,66 +0,0 @@
-# T-Display-S3 — compatibility and status
-
-Keyed by hardware revision where one can be distinguished, and by software version.
-**Nothing below was verified on hardware by this pass**; the class column says who did verify.
-
-Classes: **VC** vendor-confirmed · **FM** firsthand measurement · **FO** firsthand ownership ·
-**II** informed interpretation · **INF** inferred here.
-
-## Working
-
-| Item | Version / revision | Class | Evidence |
-|---|---|---|---|
-| Arduino, `TFT_eSPI` + `Setup206` | arduino-esp32 **≤ 2.0.14** | VC | vendor README; the entire example set |
-| Arduino, `Arduino_GFX` | 2.0.14 **and** 3.x | FO | vendor README FAQ 2 recommends it as the hardware test |
-| PlatformIO | `espressif32@6.5.0` | VC | `platformio.ini` @ `ec889e7` |
-| ESP-IDF | v5.x via `LilyGo-Display-IDF` | VC | repo @ `b1a1cc5` |
-| **Tasmota** | `Tasmota32-S3 (QIO Flash/OPI PSRAM)` + "Lilygo S3 Display" template | FO | [issue #18](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/18); `Display Model 17`, 320×170. **Needs `displaydimmer 100`** |
-| **ESPHome** | `mipi_spi` model `T-DISPLAY-S3`, board `lilygo-t-display-s3` | VC (upstream source) | `esphome/.../lilygo.py`, `dev` |
-| **MicroPython** | `russhughes/st7789s3_mpy` | FO | vendor README §6; `tft_config.py` exists for this board |
-| LVGL | 8.x | VC | `examples/lv_demos/lv_conf.h` |
-| Touch, CST328 boards | `-DTOUCH_MODULES_CST_MUTUAL` | VC | vendor `platformio.ini` default |
-| Battery ADC | `analogReadMilliVolts(4) * 2` | FM | [issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230) |
-| Battery + shell | MakerFocus 3.7 V 1000 mAh #952540 + printed backpack | FO | [r/esp32 2026-08-30](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/) |
-| JTAG over USB-C | `USB Mode = CDC and JTAG`, `debug_tool = esp-builtin` | VC | `platformio.ini`, board manifest |
-
-## Partial
-
-| Item | Limitation | Class |
-|---|---|---|
-| Battery operation with USB serial | must choose: `USB CDC On Boot` on (blocks on battery) or off (serial moves to GPIO43/44) | VC |
-| Deep sleep | works; **no current figure published for this board**, and GPIO16/17 pull-ups add unquantified draw | VC + FO |
-| Touch under ESP-IDF | `TouchLib` is Arduino-only; use `LilyGo-Display-IDF` or write a driver | FO ([#156](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/156)) |
-| ULP | vendor examples state they need **arduino-esp32 3.0.0-rc3**, contradicting the repo's 2.0.14 pin | VC (self-contradictory) |
-| I²S audio | no codec fitted; pins scarce | FO ([#158](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/158)) |
-| Qwiic sensors on the SH1.0 connector | **not pin-compatible with Qwiic** | FO ([#181](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/181)) |
-
-## Failing
-
-| Item | Symptom | Class |
-|---|---|---|
-| `TFT_eSPI` on arduino-esp32 **> 2.0.14** | documented broken by the vendor, citing [TFT_eSPI#3329](https://github.com/Bodmer/TFT_eSPI/issues/3329) | VC |
-| `ledcSetup` / `ledcAttachPin` on core 3.x | removed; use `ledcAttach`/`ledcDetach` | FM |
-| **GPIO43 / GPIO44 as GPIO under Arduino** | claimed by UART0 even with hardware CDC. Reproduced by a second person after initially disputing it | **FM ×2** |
-| GPIO16 / GPIO17 as clean inputs or low-side drivers | fitted pull-ups hold them high; they go high again on deep-sleep entry | FO → **VC with photographs** |
-| Battery ADC while USB attached | reads ≈2.5 V, not the cell | VC |
-| Charging from the 5 V header pin | `VBUS` is not brought out; feeding 5 V in back-powers the charger | VC + FO |
-| `analogRead(4) * 3.3 / 4096` | gave 2.14 V for a 3.9 V cell | FM |
-| 5 GHz Wi-Fi | not supported by the silicon | II |
-| Meshtastic | no LoRa radio | INF (searched; no variant exists) |
-| WLED | no S3 board file or usermod | INF (searched) |
-
-## Conflicting reports
-
-| Item | Reports | Status |
-|---|---|---|
-| Charge current | README 500 mA vs schematic note 580 mA | [G2/G5](gaps-and-conflicts.md) — unresolved |
-| Charger part | schematic `TP4065` vs a board marked `65b311` | [G2](gaps-and-conflicts.md) — unresolved |
-| Colour order | `TFT_eSPI` says RGB, ESPHome says BGR | [G3](gaps-and-conflicts.md) — unresolved |
-| Pixel clock | vendor 16 MHz vs ESPHome 10 MHz | [G4](gaps-and-conflicts.md) — both work; panel-dependent |
-| GPIO43/44 usability | one commenter asserted they work, then tested and retracted | **resolved against**: they do not, under Arduino |
-
-## Untested here (everything requiring hardware)
-
-Display refresh rate · deep-sleep current · Wi-Fi RSSI · actual charge current · backlight
-linearity · whether the pull-ups are fitted on every production run · whether the `sdkconfig`
-workaround frees GPIO43/44 in ESP-IDF. See [`performance.md`](performance.md) for the method.
diff --git a/devices/lilygo/t-display-s3/coverage.md b/devices/lilygo/t-display-s3/coverage.md
deleted file mode 100644
index 75c0aa2..0000000
--- a/devices/lilygo/t-display-s3/coverage.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# T-Display-S3 — feature coverage map
-
-Snapshot 2026-09-07. **Build/hardware test status is `untested` throughout**: no board was
-available. That is stated once here rather than repeated in every row.
-
-| Feature | Hardware | Official doc | Official example | Community example | Feature guide | Status |
-|---|---|---|---|---|---|---|
-| Display (ST7789V, 8080) | ST7789V + AW9364 backlight | README pinout; `Setup206` | `tft`, `Arduino_GFXDemo`, `TFT_Rainbow`, `lv_demos`, `PCBClock`, `PokerS3`, `ImageScroll` | ESPHome model; Tasmota template; many | [`display.md`](features/display.md) | **documented** |
-| Backlight / dimming | GPIO38 → AW9364DNR | README table only | inside the display examples | core-3.x LEDC rename (firsthand) | [`display.md`](features/display.md) | **partial** — one-wire protocol undocumented by vendor |
-| Touch (Touch SKU) | CST816S **or** CST328 | two datasheets shipped; no prose | `touch_test`, `CapacitiveTouch`, `usb_hid_pad` | issue #125, #168 | [`touch.md`](features/touch.md) | **documented**, with the [R1 revision caveat](../t-display-s3-shared/board-revision-drift.md#r1--t-display-s3-touch-cst816s--cst328) |
-| Buttons | GPIO0 (strap), GPIO14, RST | README pinout | `Sleep`, `factory` | AceButton in sibling repos | [`buttons.md`](features/buttons.md) | **documented** |
-| Battery / charging | TP4065-or-`65b311`, no protection | README + FAQ 8 | — | issue #230, #42, #291 | [`power-and-battery.md`](features/power-and-battery.md) | **conflicted** — see [G2](gaps-and-conflicts.md) |
-| Battery voltage ADC | GPIO4, 100k/100k | README note | `GetBatteryVoltage` | issue #190, #65 | [`battery-voltage-measurement.md`](features/battery-voltage-measurement.md) | **documented**, ratio inferred |
-| Peripheral power gate | GPIO15 | README **IMPORTANT** block | every example | issue #79 and ~4 more | [`power-and-battery.md`](features/power-and-battery.md) | **documented** |
-| USB (native, CDC/JTAG) | ESP32-S3 USB → Type-C | README FAQ 4, 5 | `usb_hid_pad`, MIDI examples | issues #7, #16, #166, #162 | [`usb.md`](features/usb.md) | **documented** |
-| USB HID / MIDI device | USB-OTG mode | — | `usb_hid_pad`, 8 MIDI examples | `@sauloverissimo` upstreamed | [`usb.md`](features/usb.md) | **documented** |
-| Wi-Fi | ESP32-S3 radio + ceramic antenna | README antenna note + image | `factory`, `ota` | issues #123, #247, #340 | [`wifi-and-ble.md`](features/wifi-and-ble.md) | **documented; unmeasured** |
-| Bluetooth LE | ESP32-S3 radio | links to Espressif examples | `T-Display-S3-BLE-*` | — | [`wifi-and-ble.md`](features/wifi-and-ble.md) | **partial** |
-| External antenna (u.FL) | `RX`/`RX2` 0 Ω positions | README + image | — | — | [`wifi-and-ble.md`](features/wifi-and-ble.md) | **documented; unverified** |
-| microSD | **shield only**, 1-bit SDMMC | README explicit | `sd` | — | [`microsd.md`](features/microsd.md) | **documented** |
-| I²C / SH1.0 connector | GPIO17/18, fitted pull-ups | pinout only | `I2CScan`, `MPR121TouchSensor` | issue #181 (not Qwiic-compatible) | [`gpio-and-expansion.md`](features/gpio-and-expansion.md) | **documented** |
-| GPIO / headers | 2 × 12-pin + SH1.0 | pinout + electrical table | — | issues #313, #117 | [`gpio-and-expansion.md`](features/gpio-and-expansion.md) | **documented** |
-| Deep sleep | ESP32-S3 RTC | — | `Sleep` | issue #313 (pins go high) | [`deep-sleep.md`](features/deep-sleep.md) | **partial — no current figure exists** |
-| ULP | ESP32-S3 ULP-FSM | — | `ULP_ADC`, `ULP_Count` — **require core 3.0.0-rc3**, contradicting the repo's own 2.0.14 pin | — | — | **gap — no guide written** |
-| OTA update | — | — | `ota` | — | — | **gap — no guide written** |
-| I²S audio | no codec fitted | — | `WIFI_Audio_I2S` (source file only) | issue #158 "Can't manage to use I2S" | — | **gap; and pins are scarce** |
-| NES emulation | — | — | `nes` (vendored `arduino-nofrendo`) | — | — | out of scope |
-| JTAG debugging | built-in USB-JTAG | `debug_tool = esp-builtin` | — | — | [`usb.md`](features/usb.md) | **documented** |
-
-## Advertised or fitted capabilities with no guide
-
-| Capability | Why no guide | Where it is covered instead |
-|---|---|---|
-| OTA | thin evidence; the `ota` example is generic Arduino OTA with nothing board-specific | `examples/catalog.json` |
-| ULP | vendor's own examples require a core version the rest of the repo forbids; untangling that needs hardware | [`development.md`](development.md), noted as a contradiction |
-| I²S audio | **no codec, amplifier or speaker is fitted.** Not a board feature; the example drives an external I²S device | [`resources-and-conflicts.md`](resources-and-conflicts.md) |
-
-## Not fitted, and therefore absent by design
-
-IMU · RTC · audio codec · LoRa · camera · Ethernet · battery protection · fuel gauge ·
-USB-UART bridge · onboard microSD. Each is evidenced by the schematic designator census
-(`U1`–`U7`, **no `U8`**) in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) § *Negative
-results*.
diff --git a/devices/lilygo/t-display-s3/development.md b/devices/lilygo/t-display-s3/development.md
deleted file mode 100644
index 8cfedb1..0000000
--- a/devices/lilygo/t-display-s3/development.md
+++ /dev/null
@@ -1,193 +0,0 @@
-# LilyGO T-Display-S3 — development
-
-> Snapshot **2026-09-07**. Every command is labelled `executed-success`, `reported-working`,
-> `inferred` or `not-tested`. **No physical board was available to this pass**, so nothing here
-> is `executed-success` against hardware; the label distribution is honest, not modest.
-
-## 1. Board target and build configuration
-
-### PlatformIO (LilyGO's own, and the one that works out of the box)
-
-From `platformio.ini` @ **`ec889e789b3cf093412689a143f7f37b42b56af7`**, verbatim `[env]`:
-
-```ini
-[platformio]
-default_envs = factory
-src_dir = examples/${platformio.default_envs}
-
-[env]
-platform = espressif32@6.5.0
-board = lilygo-t-display-s3
-framework = arduino
-debug_tool = esp-builtin
-upload_protocol = esptool
-build_flags =
-    -DLV_LVGL_H_INCLUDE_SIMPLE
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DDISABLE_ALL_LIBRARY_WARNINGS
-    -DARDUINO_USB_MODE=1
-    -DTOUCH_MODULES_CST_MUTUAL
-```
-
-Four of those five flags are load-bearing:
-
-| Flag | What it actually does | If you drop it |
-|---|---|---|
-| `-DARDUINO_USB_CDC_ON_BOOT=1` | `Serial` becomes the native-USB CDC device | Serial output moves to GPIO43/44 and the board **stops blocking at boot** — see [`features/usb.md`](features/usb.md) |
-| `-DARDUINO_USB_MODE=1` | selects the **TinyUSB-free "CDC and JTAG"** hardware USB-serial-JTAG peripheral rather than the OTG stack | you lose the built-in JTAG debugger and `debug_tool = esp-builtin` stops working |
-| `-DTOUCH_MODULES_CST_MUTUAL` | selects the **mutual-capacitance** branch of the `TouchLib` driver, i.e. **CST328**, not CST816S | a **CST328** board will not be detected. This single flag is the difference between the two touch panel generations |
-| `-DLV_LVGL_H_INCLUDE_SIMPLE` | LVGL header-path convention | LVGL examples fail to compile |
-
-`platform = espressif32@6.5.0` pins **Arduino-ESP32 2.0.14**. That is not incidental — see §2.
-
-Board manifest, `boards/lilygo-t-display-s3.json` @ `ec889e7`:
-`mcu esp32s3`, `memory_type qio_opi`, `partitions default_16MB.csv`, `f_cpu 240 MHz`,
-`f_flash 80 MHz`, `flash_mode qio`, `-DBOARD_HAS_PSRAM`, `flash_size 16MB`,
-`maximum_ram_size 327680`, `upload speed 921600`, USB VID/PID **`0x303A:0x1001`**
-(Espressif's native USB-serial-JTAG identity — a useful positive ID that no CH340 board can
-fake).
-
-### Arduino IDE
-
-LilyGO's required settings, from `README.md` @ `ec889e7`. **Bold = mandatory**; the rest can
-follow your needs.
-
-| Setting | Value |
-|---|---|
-| Board | **ESP32S3 Dev Module** |
-| **USB CDC On Boot** | **Enable** |
-| CPU Frequency | 240 MHz (WiFi) |
-| Flash Mode | QIO 80 MHz |
-| **Flash Size** | **16MB (128Mb)** |
-| **Partition Scheme** | **16M Flash (3M APP/9.9MB FATFS)** |
-| **PSRAM** | **OPI PSRAM** |
-| **Upload Mode** | **UART0/Hardware CDC** |
-| **USB Mode** | **CDC and JTAG** |
-| Upload Speed | 921600 |
-| USB DFU On Boot / USB Firmware MSC On Boot | Disable |
-
-> "You can also choose `LilyGo T-Display-S3` as the board, but the partition table is fixed to
-> 16M Flash (3M APP/9.9MB FATFS)." — README @ `ec889e7`
-
-**Getting `PSRAM = OPI PSRAM` wrong is silent and fatal**: with the default `QSPI PSRAM` the
-ESP32-S3R8's in-package octal PSRAM is not detected, `ps_malloc()` returns `NULL`, LVGL falls
-back to internal RAM and the board runs out of heap in ways that look like random crashes.
-Related: [issue #256](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/256).
-
-Likewise `Flash Size = 16MB` — [issues #8](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/8)
-and [#41](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/41) are both "16 MB flash
-setting not working" and both resolve to the partition scheme, not the board.
-
-<a id="arduino-core-versions"></a>
-## 2. The Arduino board-package version dependency
-
-This is the single most expensive undocumented dependency in the family, so it gets exact
-versions and independent corroboration rather than a warning.
-
-### What LilyGO says
-
-> "**Note:** The test phase uses version **2.0.14**. Versions above 2.0.14 may not work
-> correctly — please downgrade if you encounter issues. As of **2024/08/02**, **TFT_eSPI does
-> not work on versions higher than 2.0.14** (see
-> [TFT_eSPI#3329](https://github.com/Bodmer/TFT_eSPI/issues/3329))."
-> — `T-Display-S3/README.md` @ `ec889e7`, § *Arduino IDE Manual Installation*
-
-### What the shipped binaries independently show
-
-Every factory image in `firmware/` carries an ESP-IDF **app descriptor** at flash offset
-`0x10000` whose `project_name` is `arduino-lib-builder` — i.e. it records the Arduino core's
-own build stamp. Decoded locally (`executed-success`, host-side, 2026-09-07):
-
-| Factory image | ESP-IDF in descriptor | Core build date | Implies arduino-esp32 |
-|---|---|---|---|
-| `t-display-s3-touch-20230417_0x0.bin` | `v4.4.4 e8bdaf9198` | 2023-02-08 | **2.0.7** |
-| `t-display-s3-no-touch-20231013_0x0.bin` | `v4.4.4 e8bdaf9198` | 2023-02-08 | **2.0.7** (byte-identical to the above — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) G1) |
-| `t-display-s3-screen-detect-20230315_0x0.bin` | `v4.4.4 e8bdaf9198` | 2023-04-20 | 2.0.8–2.0.9 |
-| `t-display-s3-midi-v1.0.1-20231013_0x0.bin` | `v4.4.4 e8bdaf9198` | 2023-04-20 | 2.0.8–2.0.9 |
-| `t-display-s3-tft-espi-20231113_0x0.bin` | `v4.4.5 ac5d805d0e` | 2023-06-12 | 2.0.9–2.0.11 |
-| `t-display-s3-lvgl-demo-20250109_0x0.bin` | **`v4.4.6 3572900934`** | **2023-10-04** | **2.0.14** |
-
-The newest image LilyGO shipped — dated January 2025 — is still built on the **2.0.14** core.
-The ESP-IDF/core mapping is the published arduino-esp32 correspondence (2.0.14 ↔ IDF v4.4.6);
-the *descriptor contents* are firsthand measurement, the *mapping* is documentation.
-Method: [`commands.md`](commands.md#decoding-an-esp32-app-descriptor).
-
-### Practical version table
-
-| Component | Known-good | Known-broken | Evidence |
-|---|---|---|---|
-| **arduino-esp32 core** | **2.0.14** | > 2.0.14 with TFT_eSPI | vendor README; TFT_eSPI#3329 |
-| PlatformIO platform | **`espressif32@6.5.0`** (= core 2.0.14) | untested above | `platformio.ini` @ `ec889e7` |
-| `TFT_eSPI` | any version **with** `Setup206` selected, on core ≤ 2.0.14 | any version on core 3.x | vendor README, issue #326 |
-| `Arduino_GFX` | the vendored `GFX Library for Arduino` copy; also works on 3.x | — | vendor README FAQ 2 recommends it as the *hardware* test precisely because it does not depend on `User_Setup_Select.h` |
-| `LovyanGFX` | community-reported working on 3.x | — | *reported-working*, not verified here |
-| `lvgl` | **8.x** for LilyGO's examples | 9.x needs the examples ported | `examples/lv_demos/lv_conf.h` @ `ec889e7` is an LVGL 8 config |
-| ESP-IDF (direct) | **v5.x**, via `LilyGo-Display-IDF` | v5.0 had teething problems | [issue #103](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/103) |
-| ESPHome | ≥ the release adding `mipi_spi` model `T-DISPLAY-S3` | older `st7789v` platform needed manual pins | `esphome/components/mipi_spi/models/lilygo.py`, `dev` @ 2026-09-07 |
-
-**The core-3.x situation, stated carefully.** LilyGO's warning is specifically about
-`TFT_eSPI`, and it is dated 2024-08-02. Core 3.x also renames the LEDC API — a
-[firsthand community report](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/)
-(2026-05-25) notes `ledcSetup`/`ledcAttachPin` are gone in favour of `ledcAttach`/`ledcDetach`,
-which breaks LilyGO's backlight-dimming snippets. Boards **do** run on core 3.x if you use
-`Arduino_GFX` and fix the LEDC calls; the vendor examples do not.
-
-## 3. Build, flash, monitor
-
-`reported-working` (LilyGO's documented procedure), `not-tested` here.
-
-```bash
-# PlatformIO, from the repo root
-pio run -e factory                 # build
-pio run -e factory -t upload       # flash
-pio device monitor -b 115200       # monitor
-```
-
-Selecting a different example means editing `default_envs` in `platformio.ini`; LilyGO drives
-`src_dir` from it, so exactly one line must be uncommented.
-
-### When the port keeps disappearing — manual download mode
-
-The most-repeated instruction in the whole family, quoted from the README:
-
-1. Connect the board via USB.
-2. Press and **hold BOOT**.
-3. While still holding BOOT, press **RST**.
-4. Release **RST**.
-5. Release **BOOT**.
-6. Upload. Then press **RST** to leave download mode.
-
-This is needed because the native USB device is re-enumerated by the *application*; if the
-application crashes, reconfigures USB, or blocks, the port vanishes. There is no auto-reset
-circuit to fall back on — a CH340 board would have one. See
-[`features/usb.md`](features/usb.md).
-
-## 4. Debugging
-
-`debug_tool = esp-builtin` in LilyGO's `platformio.ini` selects the **ESP32-S3's built-in
-USB-JTAG**, which requires `USB Mode = CDC and JTAG` (`-DARDUINO_USB_MODE=1`). You get JTAG
-over the same USB-C cable, with no external probe. Choosing the OTG USB mode to get TinyUSB
-features costs you the debugger — that trade-off is not obvious from either menu.
-
-`openocd_target` is `esp32s3-builtin.cfg` per the board manifest.
-
-## 5. Recovery
-
-Full procedure and offsets: [`factory-firmware.md`](factory-firmware.md). Summary: the shipped
-images are **merged images starting at `0x0`** (bootloader + partition table + app), so a
-single `esptool.py write_flash 0x0 <file>` restores a board, and LilyGO also hosts a web
-flasher. Note the trap that the two 8 MB-layout images will leave a 16 MB board with a
-partition table that only addresses the first 8 MB.
-
-## 6. MicroPython and other languages
-
-| Runtime | Status | Source |
-|---|---|---|
-| **MicroPython** | Supported through **`russhughes/st7789s3_mpy`** — a C-level ST7789 driver with an 8-bit parallel backend written for this board — and LilyGO's `Xinyuan-LilyGO/lilygo-micropython`. There is also `Xinyuan-LilyGO/T-Display-S3-MicroPython` (created recently, `board/lilygo-t-displays3.json`, pushed 2026-09-04) | vendor README §6; org repo listing |
-| **CircuitPython** | **No board definition located** in Adafruit's repository during this pass. Recorded as a gap, not as an absence proof | [`research-log.md`](research-log.md) |
-| **Rust** | asked in [issue #160](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/160); `esp-hal` targets the SoC, not the board. No board-support crate found | — |
-
-**MicroPython carries the GPIO15 trap too**, and it bites harder because there is no `setup()`
-convention: [issue #79](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/79) contains an
-exchange (2024-04-23) where a MicroPython user could not make GPIO15 work and asked whether a
-wire would do instead. It will not; the pin must be driven by code every boot.
diff --git a/devices/lilygo/t-display-s3/examples/best.md b/devices/lilygo/t-display-s3/examples/best.md
deleted file mode 100644
index 7154046..0000000
--- a/devices/lilygo/t-display-s3/examples/best.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# T-Display-S3 — recommended examples
-
-Selected from the 32 catalogued in [`catalog.json`](catalog.json). **None was built or run**
-(no hardware, no toolchain). These are reasoned selections, not validated ones.
-
-## Start here, in this order
-
-| Order | Example | Why this one |
-|---|---|---|
-| 1 | **`Arduino_GFXDemo`** | LilyGO's own recommended first test (README FAQ 2). It needs **no** library-internal configuration, so if it draws, the hardware is fine and any later problem is `TFT_eSPI` config. Running this first saves the most time of anything in the repo |
-| 2 | **`I2CScan`** | Thirty seconds, and it tells you whether you have a Touch board, and whether it is CST816S (`0x15`) or CST328 (`0x1A`). Also proves GPIO15 is high, because the touch controller sits on the gated rail |
-| 3 | **`tft`** | The minimal `TFT_eSPI` path. If step 1 worked and this does not, you have the `User_Setup_Select.h` problem and nothing else |
-| 4 | **`GetBatteryVoltage`** | The vendor reference for the GPIO4 divider — read it next to [issue #190](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/190), where the naive arithmetic gives a wrong-but-plausible answer |
-
-## Portfolio, by purpose
-
-| Purpose | Example | Notes |
-|---|---|---|
-| **Diagnostic** | `Arduino_GFXDemo`, `I2CScan` | isolate hardware from configuration |
-| **Minimal per feature** | `tft` (display) · `touch_test` (touch) · `GetBatteryVoltage` (ADC) · `Sleep` (deep sleep) · `T-Display-S3-BLE-Sender` (BLE) | one feature each, small enough to read |
-| **Integrated** | `factory` · `lv_demos` | `factory` exercises display + touch + Wi-Fi + NTP + LVGL + buttons + battery. `lv_demos` is the LVGL starting point and the reason `PSRAM = OPI` matters |
-| **Limit testing** | `Arduino_GFX_PDQgraphicstest` | the vehicle for the pixel-clock measurements in [`../performance.md`](../performance.md) |
-| **Alternative approach** | `usb_hid_pad` | requires `USB Mode = USB-OTG`, which **disables the built-in JTAG debugger** — the clearest demonstration of that trade-off |
-| **Negative / cautionary** | `tft` (fails without the `User_Setup_Select.h` edit) · `ULP_ADC` (demands a core version the repo forbids) · `WIFI_Audio_I2S` (a `.cpp` with no `.ino`) | each teaches something the docs do not |
-| **ESP-IDF starting point** | `LilyGo-Display-IDF` @ `b1a1cc5` | MIT; nine boards behind `CONFIG_LILYGO_*` |
-
-## Feature coverage of the selection
-
-| Feature | Covered by |
-|---|---|
-| Display | `Arduino_GFXDemo`, `tft`, `lv_demos`, `factory` |
-| Touch | `touch_test`, `factory` |
-| Buttons | `Sleep`, `factory` |
-| Battery ADC | `GetBatteryVoltage`, `factory` |
-| Deep sleep | `Sleep` |
-| Wi-Fi | `factory` |
-| BLE | `T-Display-S3-BLE-Sender` |
-| USB device (OTG) | `usb_hid_pad` |
-| I²C | `I2CScan` |
-| PSRAM | `lv_demos` |
-| Performance | `Arduino_GFX_PDQgraphicstest` |
-
-**Not covered by any selected example, and not covered well by any example at all:**
-microSD (needs the shield), OTA (generic), I²S audio (broken as shipped), ULP (version
-conflict), external antenna (no example possible). See
-[`../coverage.md`](../coverage.md).
-
-## Not vendored here
-
-The vendor examples are **not copied into this repository**. They are ~180 MB of repo including
-multi-megabyte image headers and nine vendored libraries, they are one `git clone` away, and
-every entry in [`catalog.json`](catalog.json) carries a commit-pinned permalink. Reacquisition:
-[`../acquisition/README.md`](../acquisition/README.md).
diff --git a/devices/lilygo/t-display-s3/examples/catalog.json b/devices/lilygo/t-display-s3/examples/catalog.json
deleted file mode 100644
index cb64631..0000000
--- a/devices/lilygo/t-display-s3/examples/catalog.json
+++ /dev/null
@@ -1,894 +0,0 @@
-{
-  "schema": "hardware-doc/examples-catalog/1",
-  "device": "devices/lilygo/t-display-s3",
-  "generated": "2026-09-07",
-  "search_log": "search-log.md",
-  "selected": "best.md",
-  "caveat": "No example was compiled or run. build_status is 'not-built' for every entry; this is an inventory with reasoned selection, not a validation.",
-  "examples": [
-    {
-      "id": "tds3-factory",
-      "title": "factory",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/factory",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/factory",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display",
-        "touch",
-        "wifi",
-        "ntp",
-        "lvgl",
-        "buttons",
-        "battery"
-      ],
-      "dependencies": [
-        "lvgl 8.x",
-        "TouchLib",
-        "TFT_eSPI(ignored)"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "The shipped demo. Also the source of the ESP-Touch/LCD-touch naming confusion in issue #212.",
-      "selection_decision": "selected \u2014 integrated"
-    },
-    {
-      "id": "tds3-tft",
-      "title": "tft",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/tft",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/tft",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display"
-      ],
-      "dependencies": [
-        "TFT_eSPI + Setup206"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Smallest TFT_eSPI path. Fails if User_Setup_Select.h is not edited \u2014 which is the point.",
-      "selection_decision": "selected \u2014 minimal, and a negative example"
-    },
-    {
-      "id": "tds3-gfxdemo",
-      "title": "Arduino_GFXDemo",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/Arduino_GFXDemo",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/Arduino_GFXDemo",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display"
-      ],
-      "dependencies": [
-        "GFX Library for Arduino"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "LilyGO's own recommended hardware test (FAQ 2): needs no library-internal config, so it isolates hardware faults from TFT_eSPI config faults.",
-      "selection_decision": "selected \u2014 diagnostic"
-    },
-    {
-      "id": "tds3-gfxpdq",
-      "title": "Arduino_GFX_PDQgraphicstest",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/Arduino_GFX_PDQgraphicstest",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/Arduino_GFX_PDQgraphicstest",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display",
-        "performance"
-      ],
-      "dependencies": [
-        "GFX Library for Arduino"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Timed graphics benchmark. The obvious vehicle for the pixel-clock measurements listed in performance.md.",
-      "selection_decision": "selected \u2014 limit testing"
-    },
-    {
-      "id": "tds3-battery",
-      "title": "GetBatteryVoltage",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/GetBatteryVoltage",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/GetBatteryVoltage",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "adc",
-        "battery"
-      ],
-      "dependencies": [
-        "-"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Vendor reference for the GPIO4 divider. Read alongside issue #190, where naive raw-count arithmetic gives a wrong-but-plausible answer.",
-      "selection_decision": "selected \u2014 feature minimal"
-    },
-    {
-      "id": "tds3-touchtest",
-      "title": "touch_test",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/touch_test",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/touch_test",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "touch",
-        "display",
-        "i2c"
-      ],
-      "dependencies": [
-        "TouchLib"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Touch probe. Behaviour depends on -DTOUCH_MODULES_CST_MUTUAL vs _SELF; see revision R1.",
-      "selection_decision": "selected \u2014 feature minimal"
-    },
-    {
-      "id": "tds3-captouch",
-      "title": "CapacitiveTouch",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/CapacitiveTouch",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/CapacitiveTouch",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "touch",
-        "display"
-      ],
-      "dependencies": [
-        "TouchLib"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Second touch example with a bundled image.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-i2cscan",
-      "title": "I2CScan",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/I2CScan",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/I2CScan",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "i2c"
-      ],
-      "dependencies": [
-        "-"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "The fastest way to identify which touch controller a board carries. Punches above its weight.",
-      "selection_decision": "selected \u2014 diagnostic"
-    },
-    {
-      "id": "tds3-sleep",
-      "title": "Sleep",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/Sleep",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/Sleep",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "deep-sleep",
-        "buttons",
-        "display"
-      ],
-      "dependencies": [
-        "-"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Only vendor sleep guidance. Does not address the GPIO16/17 pull-up draw found in issue #313.",
-      "selection_decision": "selected \u2014 feature minimal"
-    },
-    {
-      "id": "tds3-lvdemos",
-      "title": "lv_demos",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/lv_demos",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/lv_demos",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display",
-        "lvgl",
-        "psram"
-      ],
-      "dependencies": [
-        "lvgl 8.x"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "LVGL widgets demo. Requires PSRAM=OPI; failing that it exhausts heap.",
-      "selection_decision": "selected \u2014 integrated"
-    },
-    {
-      "id": "tds3-sd",
-      "title": "sd",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/sd",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/sd",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "microsd"
-      ],
-      "dependencies": [
-        "SD_MMC"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "1-bit SDMMC via the separately sold TF Shield. Useless without the shield.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-ota",
-      "title": "ota",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/ota",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/ota",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "ota",
-        "wifi"
-      ],
-      "dependencies": [
-        "ArduinoOTA"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Generic Arduino OTA; nothing board-specific.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-serial",
-      "title": "SerialExample",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/SerialExample",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/SerialExample",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "usb",
-        "uart"
-      ],
-      "dependencies": [
-        "-"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Trivial, but the right first test when USB CDC On Boot is in doubt.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-usbhid",
-      "title": "usb_hid_pad",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/usb_hid_pad",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/usb_hid_pad",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "usb-otg",
-        "touch",
-        "display"
-      ],
-      "dependencies": [
-        "TinyUSB"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Needs USB Mode = USB-OTG, which disables the built-in JTAG debugger. A good demonstration of that trade-off.",
-      "selection_decision": "selected \u2014 alternative approach"
-    },
-    {
-      "id": "tds3-nes",
-      "title": "nes",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/nes",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/nes",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display",
-        "audio",
-        "buttons"
-      ],
-      "dependencies": [
-        "arduino-nofrendo (vendored)"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "NES emulator. Vendored upstream library; a stress test of the display path more than a feature example.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-ulpadc",
-      "title": "ULP_ADC",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/ULP_ADC",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/ULP_ADC",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "ulp",
-        "adc"
-      ],
-      "dependencies": [
-        "arduino-esp32 3.0.0-rc3"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "States it requires a core newer than the 2.0.14 the rest of the repo pins. An internal contradiction in LilyGO's own repository.",
-      "selection_decision": "catalogued \u2014 negative/conflict"
-    },
-    {
-      "id": "tds3-ulpcount",
-      "title": "ULP_Count",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/ULP_Count",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/ULP_Count",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "ulp"
-      ],
-      "dependencies": [
-        "arduino-esp32 3.0.0-rc3"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "As above.",
-      "selection_decision": "catalogued \u2014 negative/conflict"
-    },
-    {
-      "id": "tds3-mpr121",
-      "title": "MPR121TouchSensor",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/MPR121TouchSensor",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/MPR121TouchSensor",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "i2c"
-      ],
-      "dependencies": [
-        "Adafruit_MPR121 (vendored)"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "External capacitive-touch breakout over I2C; unrelated to the panel touch.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-imgscroll",
-      "title": "ImageScroll",
-      "author": "Rudi Ackermann",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/ImageScroll",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/ImageScroll",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display"
-      ],
-      "dependencies": [
-        "TFT_eSPI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @Rudi Ackermann. 5 MB of image headers; a good example of why this repo is 180 MB.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-pcbclock",
-      "title": "PCBClock",
-      "author": "VolosR",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/PCBClock",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/PCBClock",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display",
-        "wifi",
-        "ntp"
-      ],
-      "dependencies": [
-        "TFT_eSPI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @VolosR. Issue #256 reports it not fitting \u2014 an OPI-PSRAM setting problem, not a size problem.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-poker",
-      "title": "PokerS3",
-      "author": "VolosR",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/PokerS3",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/PokerS3",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display"
-      ],
-      "dependencies": [
-        "TFT_eSPI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @VolosR.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-rainbow",
-      "title": "TFT_Rainbow",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/TFT_Rainbow",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/TFT_Rainbow",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "display"
-      ],
-      "dependencies": [
-        "TFT_eSPI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "Minimal TFT_eSPI colour test.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-midi",
-      "title": "T-Display-S3-MIDI",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-MIDI",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-MIDI",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "usb-otg",
-        "midi",
-        "display"
-      ],
-      "dependencies": [
-        "TinyUSB"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "For the separately sold MIDI shield (SKU H656, USD 15.47), which has its own schematic.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-piano",
-      "title": "T-Display-S3-Piano",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-Piano",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-Piano",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "usb-otg",
-        "midi",
-        "display"
-      ],
-      "dependencies": [
-        "ESP32_Host_MIDI",
-        "Gingoduino"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @sauloverissimo. Ships two PDFs including a T-Display-S3 microcontroller reference.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-blerx",
-      "title": "T-Display-S3-BLE-Receiver",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-BLE-Receiver",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-BLE-Receiver",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "ble",
-        "midi",
-        "display"
-      ],
-      "dependencies": [
-        "ESP32_Host_MIDI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @sauloverissimo.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-bletx",
-      "title": "T-Display-S3-BLE-Sender",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-BLE-Sender",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-BLE-Sender",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "ble",
-        "midi",
-        "display"
-      ],
-      "dependencies": [
-        "ESP32_Host_MIDI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @sauloverissimo. The clearest vendor-repo BLE example.",
-      "selection_decision": "selected \u2014 feature minimal"
-    },
-    {
-      "id": "tds3-usbdev",
-      "title": "T-Display-S3-USB-Device",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-USB-Device",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-USB-Device",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "usb-otg",
-        "ble",
-        "midi"
-      ],
-      "dependencies": [
-        "ESP32_Host_MIDI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "BLE-to-USB MIDI bridge; exercises both radios and USB device mode at once.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-gingo",
-      "title": "T-Display-S3-Gingoduino",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-Gingoduino",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-Gingoduino",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "midi",
-        "display"
-      ],
-      "dependencies": [
-        "Gingoduino"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @sauloverissimo.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-queue",
-      "title": "T-Display-S3-Queue",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-Queue",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-Queue",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "midi",
-        "display"
-      ],
-      "dependencies": [
-        "ESP32_Host_MIDI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @sauloverissimo.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-music",
-      "title": "T-Display-S3-Music-Explorer",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-Music-Explorer",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-Music-Explorer",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "midi",
-        "audio",
-        "display"
-      ],
-      "dependencies": [
-        "Gingoduino"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @sauloverissimo; ships its own README_AUDIO.md.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-pianodbg",
-      "title": "T-Display-S3-Piano-Debug",
-      "author": "sauloverissimo",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/T-Display-S3-Piano-Debug",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/T-Display-S3-Piano-Debug",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "midi"
-      ],
-      "dependencies": [
-        "ESP32_Host_MIDI"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "By @sauloverissimo.",
-      "selection_decision": "catalogued"
-    },
-    {
-      "id": "tds3-i2saudio",
-      "title": "WIFI_Audio_I2S",
-      "author": "LILYGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/main/examples/WIFI_Audio_I2S",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/examples/WIFI_Audio_I2S",
-      "commit": "ec889e789b3cf093412689a143f7f37b42b56af7",
-      "retrieved": "2026-09-07",
-      "last_activity": "2026-08-31",
-      "device": "LilyGO T-Display-S3",
-      "hw_revision": "unversioned (schematic dated 2024-04-29)",
-      "framework": "Arduino (arduino-esp32 2.0.14 / espressif32@6.5.0)",
-      "features": [
-        "i2s",
-        "wifi"
-      ],
-      "dependencies": [
-        "ESP32-audioI2S 3.0.6 (vendored)"
-      ],
-      "license": "MIT (repository)",
-      "build_status": "not-built",
-      "test_environment": "none \u2014 no hardware available 2026-09-07",
-      "notes": "A .cpp with no .ino \u2014 not a buildable Arduino sketch as shipped. Related: issue #158.",
-      "selection_decision": "catalogued \u2014 broken as shipped"
-    }
-  ],
-  "external_examples": [
-    {
-      "id": "ext-teastain",
-      "title": "LilyGO-T-display-S3-setup-and-examples",
-      "author": "teastainGit",
-      "source_class": "community",
-      "canonical_url": "https://github.com/teastainGit/LilyGO-T-display-S3-setup-and-examples",
-      "commit": null,
-      "retrieved": "2026-09-07",
-      "license": "not established",
-      "build_status": "not-built",
-      "notes": "The de-facto community setup guide; endorsed by LilyGO's maintainer in issue #79 on 2023-03-13. Documents GPIO15, backlight, battery and the User_Setup_Select.h problem. Not pinned to a commit by this pass \u2014 a gap.",
-      "selection_decision": "referenced, not vendored (licence not established)"
-    },
-    {
-      "id": "ext-st7789s3mpy",
-      "title": "st7789s3_mpy",
-      "author": "russhughes",
-      "source_class": "community",
-      "canonical_url": "https://github.com/russhughes/st7789s3_mpy",
-      "commit": null,
-      "retrieved": "2026-09-07",
-      "license": "not established",
-      "build_status": "not-built",
-      "notes": "MicroPython C driver with an 8-bit parallel backend; carries tft_config.py for this board. Linked from LilyGO's own README.",
-      "selection_decision": "referenced"
-    },
-    {
-      "id": "ext-lilygo-idf",
-      "title": "LilyGo-Display-IDF",
-      "author": "Xinyuan-LilyGO",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Xinyuan-LilyGO/LilyGo-Display-IDF",
-      "immutable_url": "https://github.com/Xinyuan-LilyGO/LilyGo-Display-IDF/tree/b1a1cc54994bf1b417e3bb30c437bbe1036bff7f",
-      "commit": "b1a1cc54994bf1b417e3bb30c437bbe1036bff7f",
-      "retrieved": "2026-09-07",
-      "license": "MIT",
-      "build_status": "not-built",
-      "notes": "The ESP-IDF example set for nine boards. Its main/product_pins.h is the single best cross-variant pin source in the family and is retained in the shared platform record.",
-      "selection_decision": "selected \u2014 the ESP-IDF starting point"
-    }
-  ]
-}
diff --git a/devices/lilygo/t-display-s3/examples/search-log.md b/devices/lilygo/t-display-s3/examples/search-log.md
deleted file mode 100644
index de62745..0000000
--- a/devices/lilygo/t-display-s3/examples/search-log.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# T-Display-S3 — example search log
-
-Date **2026-09-07**. Depth and exclusions stated; this is a broad-coverage snapshot, not a
-census.
-
-| Source | Method | Depth | Result |
-|---|---|---|---|
-| Vendor repo `examples/` | full recursive tree at commit `ec889e7` | 3 431 tree entries filtered to 29 example directories | all 29 catalogued |
-| Vendor repo `lib/` | same tree | 9 vendored libraries | not catalogued as examples; recorded as dependencies |
-| `LilyGo-Display-IDF` | full tree at `b1a1cc5` | 84 entries | ESP-IDF example set — catalogued as external |
-| GitHub code search | `repo:esphome/esphome t-display-s3` | 4 hits | ESPHome model definitions — catalogued as external |
-| GitHub code search | `repo:russhughes/st7789s3_mpy t-display` | 7 hits | MicroPython driver + this board's `tft_config.py` |
-| GitHub code search | `repo:arendst/Tasmota lilygo` · `TDisplayS3` | 19 / 0 hits | Tasmota support is a **runtime template**, not a source example |
-| GitHub code search | `repo:wled/WLED lilygo` · `org:meshtastic tdisplay` | 10 / 247 hits | **negative** — no example exists for either |
-| Issue tracker | 318 issues scanned for linked code | 22 read in full | found `teastainGit/…` (endorsed by the vendor) and several gists |
-| Reddit | 4 query shapes, `t=all`, 25 results each | 27 relevant posts | project showcases; most link code |
-
-## Not searched
-
-Hackaday.io, Instructables, Bilibili, GitLab, YouTube descriptions, and forks of the vendor
-repo (273 exist; none inspected). Recorded as deliberate exclusions.
-
-## Rejections and negative findings
-
-| Candidate | Disposition |
-|---|---|
-| `examples/WIFI_Audio_I2S` | **Broken as shipped** — a `.cpp` with no `.ino`, so the Arduino IDE will not open it as a sketch. Catalogued as such |
-| `examples/ULP_ADC`, `ULP_Count` | Catalogued as a **conflict**: they state they need arduino-esp32 3.0.0-rc3, which the repository's own README forbids |
-| `examples/nes` | Catalogued but not selected — the value is the vendored emulator, not board knowledge |
-| `examples/ImageScroll`, `PCBClock`, `PokerS3` | Catalogued; community-authored showcases with multi-MB image headers |
-| WLED / Meshtastic examples | Do not exist. Recorded as negative results in [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md) |
-
-## Not done
-
-**No example was compiled or run.** No toolchain was installed and no board was attached, so
-every `build_status` in [`catalog.json`](catalog.json) is `not-built`. Selection below is
-reasoned from source reading and vendor/community reports, and is labelled as such.
diff --git a/devices/lilygo/t-display-s3/factory-firmware.md b/devices/lilygo/t-display-s3/factory-firmware.md
deleted file mode 100644
index 166ff30..0000000
--- a/devices/lilygo/t-display-s3/factory-firmware.md
+++ /dev/null
@@ -1,130 +0,0 @@
-# T-Display-S3 — factory firmware
-
-> Six merged images retained. All decoded locally on **2026-09-07**
-> (`executed-success`, host-side analysis of the binaries; **not** flashed to hardware).
-> Stored once in the [shared platform record](../t-display-s3-shared/README.md) because they
-> cover the Touch variant too.
-
-## 1. The images
-
-Source: `Xinyuan-LilyGO/T-Display-S3` → `firmware/` @ **`ec889e789b3cf093412689a143f7f37b42b56af7`**,
-retrieved 2026-09-07 from `raw.githubusercontent.com`. Repository licence **MIT**; the binaries
-carry no separate licence statement.
-
-| File | Bytes | SHA-256 | Flash offset | Bootloader header | App-descriptor ESP-IDF | Core build stamp |
-|---|---|---|---|---|---|---|
-| `t-display-s3-touch-20230417_0x0.bin` | 1 601 328 | `f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa` | `0x0` | DIO, **8 MB**, 80 MHz | `v4.4.4 e8bdaf9198` | Feb 8 2023 18:07:54 |
-| `t-display-s3-no-touch-20231013_0x0.bin` | 1 601 328 | **`f288081645eecf7b…` — identical** | `0x0` | DIO, **8 MB**, 80 MHz | `v4.4.4 e8bdaf9198` | Feb 8 2023 18:07:54 |
-| `t-display-s3-lvgl-demo-20250109_0x0.bin` | 675 920 | `4af91e520a3f5037d9b0420aa620f8736e4e6469601098fea6eb4985323d847f` | `0x0` | DIO, **16 MB**, 80 MHz | `v4.4.6 3572900934` | Oct 4 2023 16:40:08 |
-| `t-display-s3-tft-espi-20231113_0x0.bin` | 501 520 | `45385b2a90070a7616b7fceca553d60ca984e33115f4b9586a5ebb6ddb8213f1` | `0x0` | DIO, 16 MB, 80 MHz | `v4.4.5 ac5d805d0e` | Jun 12 2023 16:32:29 |
-| `t-display-s3-screen-detect-20230315_0x0.bin` | 489 616 | `2f0cf68a3ac19cec982735d7ccbcb93e522e65c9d8736e440efbf4001f9707fd` | `0x0` | DIO, 16 MB, 80 MHz | `v4.4.4 e8bdaf9198` | Apr 20 2023 00:44:44 |
-| `t-display-s3-midi-v1.0.1-20231013_0x0.bin` | 971 824 | `f6883c8ba9be6b1c0b9840943a79fb6eee7d4e5af506ea42b01a95a1c7a9134a` | `0x0` | DIO, 16 MB, 80 MHz | `v4.4.4 e8bdaf9198` | Apr 20 2023 00:44:44 |
-
-*(`t-display-s3-midi-v1.0.0-20231013_0x0.bin`, 902 784 B, exists upstream and was not
-retained; it is superseded by v1.0.1 and recorded in
-[`acquisition/manifest.json`](acquisition/manifest.json) as `reference-only`.)*
-
-All six are **ESP32-S3** images (`magic 0xE9`, chip id 9). All are **merged** — bootloader at
-`0x0`, partition table at `0x8000`, app at `0x10000` — so one write restores a board.
-
-**The `project_name` in every app descriptor is `arduino-lib-builder`, not a LilyGO project
-name.** That is the Arduino core's own stamp, which is why the "build date" column dates the
-*core*, not the sketch. It is still useful — it is how [`development.md`](development.md#arduino-core-versions)
-establishes that LilyGO never rebuilt past core 2.0.14.
-
-## 2. Finding G1 — "touch" and "no-touch" are the same file
-
-`t-display-s3-touch-20230417_0x0.bin` and `t-display-s3-no-touch-20231013_0x0.bin` have
-**identical SHA-256, identical size, and identical app descriptors including build time**.
-They are one binary published twice under two names and two dates.
-
-- **Measured** 2026-09-07: `f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa`,
-  1 601 328 B, both.
-- **Independently noticed by a user** in
-  [issue #212 "Firmware_no_Touch is the same as Touch ?"](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212)
-  (2024-01-02). The thread never resolves it — it diverts into a separate confusion between the
-  "ESP-Touch" Wi-Fi provisioning app and LCD touch, which is itself a naming trap worth
-  knowing about.
-
-**Practical consequence:** flashing the "no-touch" image to a non-touch board gives you the
-touch factory demo, whose UI expects a touchscreen. Combined with the ESP-Touch confusion, this
-is a reliable way to conclude your board is broken when it is not.
-
-## 3. Finding G2 — the two big images carry an 8 MB partition table on a 16 MB board
-
-`touch`/`no-touch` decode as:
-
-```
-bootloader header: flash size 8MB
-nvs       type=1 subtype=0x02 off=0x009000 size=0x005000   20K
-otadata   type=1 subtype=0x00 off=0x00e000 size=0x002000    8K
-app0      type=0 subtype=0x10 off=0x010000 size=0x330000  3264K
-app1      type=0 subtype=0x11 off=0x340000 size=0x330000  3264K
-spiffs    type=1 subtype=0x82 off=0x670000 size=0x180000  1536K
-coredump  type=1 subtype=0x03 off=0x7f0000 size=0x010000    64K      ← ends at 8 MB
-```
-
-while the other four decode as the `default_16MB` layout:
-
-```
-app0      off=0x010000 size=0x640000  6400K
-app1      off=0x650000 size=0x640000  6400K
-spiffs    off=0xc90000 size=0x360000  3456K
-coredump  off=0xff0000 size=0x010000    64K      ← ends at 16 MB
-```
-
-The board has **16 MB**. Flashing the touch/no-touch image therefore leaves a partition table
-that addresses only the lower half, and a bootloader header claiming 8 MB. It boots and runs —
-the ESP32-S3 bootloader tolerates an under-declared flash size — but the upper 8 MB is
-unaddressed until you flash something with the correct table. This is a plausible mechanism
-behind several "16 MB flash setting not working" reports
-([#8](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/8),
-[#41](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/41)); **that causal link is
-inferred, not demonstrated.**
-
-Also note `flash mode = DIO` in every bootloader header, while LilyGO's Arduino instructions
-and PlatformIO board file both specify **QIO**. The bootloader header is authoritative for how
-the *bootloader* reads flash; the app can and does switch. Not a defect, but it means you
-cannot read the recommended flash mode off these images.
-
-## 4. Restoring a board
-
-`reported-working` (LilyGO's documented procedure), `not-tested` here.
-
-```bash
-# 1. Manual download mode: hold BOOT, tap RST, release RST, release BOOT.
-# 2. Erase — recommended when switching between the 8 MB and 16 MB layouts,
-#    otherwise a stale partition table can survive.
-esptool.py --chip esp32s3 --port /dev/ttyACM0 erase_flash
-
-# 3. Write the merged image at 0x0.
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-    write_flash -z 0x0 t-display-s3-lvgl-demo-20250109_0x0.bin
-```
-
-LilyGO also documents two GUI routes in `firmware/README.MD` @ `ec889e7`: Espressif's
-**Flash Download Tool** (Windows) and a **web flasher** (`LILYGO-Spark`, WebSerial-based,
-Chrome/Edge only). Both write the same merged image to `0x0`.
-
-**Which image to use for a first diagnosis:** `t-display-s3-screen-detect-20230315_0x0.bin`
-(489 KB) exists specifically to prove the panel works. It is the smallest and the fastest
-answer to "is my board dead?".
-
-## 5. What is not established
-
-- **No image was flashed to hardware by this pass.** Everything above is static analysis.
-- **No official hash list exists** to compare against; LilyGO publishes no checksums. The
-  hashes here are of the bytes as served by `raw.githubusercontent.com` at the pinned commit,
-  which is the strongest available provenance.
-- The **`t-display-s3-midi-v1.0.0`** image was not retained, so the v1.0.0→v1.0.1 delta is
-  uncharacterised.
-- **No factory image contains a LilyGO project name or version string** in its app descriptor,
-  so the file name is the only version identifier. That is why the byte-identical pair in §2
-  went unnoticed for years.
-
-## Method
-
-Decoding recipe and script: [`commands.md`](commands.md#decoding-an-esp32-app-descriptor).
-The repository's [`tools/esp_image_info.py`](../../../tools/esp_image_info.py) reads the
-bootloader header directly but reports *"no app descriptor"* on merged images because it looks
-at offset `0x20`, not `0x10020`; the extra step is documented in `commands.md`.
diff --git a/devices/lilygo/t-display-s3/features/README.md b/devices/lilygo/t-display-s3/features/README.md
deleted file mode 100644
index 5400745..0000000
--- a/devices/lilygo/t-display-s3/features/README.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# T-Display-S3 — feature guides
-
-Every advertised or fitted capability, one guide each. Evidence status is stated inside each
-guide; **none of these were verified against physical hardware by the 2026-09-07 pass**.
-
-| Guide | Covers | Evidence status |
-|---|---|---|
-| [`display.md`](display.md) | ST7789V, 8-bit 8080 bus, library choice, backlight, offsets | vendor source + independent library configs |
-| [`touch.md`](touch.md) | CST816S / CST328, the two-generation split, I²C | vendor source + shipped datasheets |
-| [`buttons.md`](buttons.md) | BOOT/GPIO0, GPIO14, RST, wake sources | vendor source |
-| [`power-and-battery.md`](power-and-battery.md) | GPIO15 gate, charger, charge current, no protection | vendor doc + firsthand reports |
-| [`battery-voltage-measurement.md`](battery-voltage-measurement.md) | GPIO4 ADC, divider, the pin conflict | schematic designators + firsthand reports |
-| [`usb.md`](usb.md) | native USB, **the `USB CDC On Boot` trap**, USB Mode, recovery | vendor doc, repeatedly corroborated |
-| [`wifi-and-ble.md`](wifi-and-ble.md) | on-board vs u.FL antenna, the resistor move, reported range | vendor doc + user reports |
-| [`microsd.md`](microsd.md) | TF Shield only, 1-bit SDMMC | vendor doc |
-| [`gpio-and-expansion.md`](gpio-and-expansion.md) | headers, SH1.0 connector, what is actually free | vendor source + issue tracker |
-| [`deep-sleep.md`](deep-sleep.md) | wake sources, what to switch off, the pins that go high | vendor example + firsthand report |
-
-Not fitted, and therefore not documented as features: IMU, audio codec, RTC, LoRa, camera,
-Ethernet, battery protection. See [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md)
-§ *Negative results*.
diff --git a/devices/lilygo/t-display-s3/features/battery-voltage-measurement.md b/devices/lilygo/t-display-s3/features/battery-voltage-measurement.md
deleted file mode 100644
index 3896a23..0000000
--- a/devices/lilygo/t-display-s3/features/battery-voltage-measurement.md
+++ /dev/null
@@ -1,103 +0,0 @@
-# T-Display-S3 — battery voltage measurement, the divider, and the pin conflict it creates
-
-> Evidence: schematic designators + LilyGO's own example + three independent user reports.
-> **Not hardware-verified by this pass.** The divider *ratio* is inferred, not traced — §5.
-
-## 1. The circuit, as far as it is established
-
-| Fact | Value | Evidence class |
-|---|---|---|
-| Sense pin | **GPIO4** (`PIN_BAT_VOLT`, ADC1 channel 3) | primary — `examples/*/pin_config.h` @ `ec889e7`, all copies agree |
-| Divider resistors | `R2` and `R4`, both printed **`100K %1`** | primary — designator/value strings recovered from `schematic/T_Display_S3.pdf` |
-| Implied ratio | **1 : 2** (V<sub>ADC</sub> = V<sub>BAT</sub> / 2) | **inferred**, corroborated by the vendor multiplying by 2 |
-| Gate | a P-channel MOSFET (`Q4` = `SI2307`) sits in the sense path | primary designator; **the gate's control net was not traced** |
-| Reading with USB attached | ≈ **2.5 V**, i.e. 5 V/2 — *not* the battery voltage | firsthand user report, corroborated by vendor doc |
-
-LilyGO states the behavioural consequence directly:
-
-> "The battery ADC pin can only read the battery voltage when the USB-C port is **not** plugged
-> in; it cannot read the battery voltage after the USB-C port is plugged in."
-> — `T-Display-S3/README.md` @ `ec889e789b3cf093412689a143f7f37b42b56af7`
-
-## 2. The correct way to read it
-
-This is the vendor-adjacent recipe from
-[issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230) (2024, by the same
-owner who traced the PCB), and it is right for a reason worth spelling out:
-
-```cpp
-void setup() {
-    analogReadResolution(12);            // 0..4095
-    analogSetAttenuation(ADC_11db);      // widest input range
-}
-
-void loop() {
-    // analogReadMilliVolts() applies the per-chip eFuse ADC calibration.
-    // analogRead() does NOT, and the ESP32-S3 ADC is markedly non-linear without it.
-    uint32_t mv = analogReadMilliVolts(4) * 2;   // ×2 for the 100k/100k divider
-}
-```
-
-**Use `analogReadMilliVolts()`, not `analogRead()` × a constant.** That is the whole difference
-between the two most-reported bug reports on this topic:
-
-- [issue #190](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/190) (2023-09-22) — an
-  ESP-IDF user computing `raw * 3.3 / 4096` read **2.14–2.15 V** with a battery measuring
-  **3.9 V** on a multimeter. Expected would be ~1.95 V; the raw-count arithmetic plus ADC
-  non-linearity produced a number that is wrong in a plausible-looking way. Evidence class:
-  **firsthand measurement with an independent instrument.**
-- [issue #65](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/65) (2022-12-12) —
-  "LCD_BAT_VOLT does not work on battery", 18 comments.
-
-In ESP-IDF, the equivalent is `adc_cali_*` with the curve-fitting scheme, not
-`raw * Vref / 4096`.
-
-## 3. The pin conflict
-
-**GPIO4 is the only battery sense, and it is a general-purpose pin on the header.** There is
-no PMIC to ask instead — unlike the Long, Pro and T4-S3, which read the SY6970 over I²C and
-leave GPIO4 free.
-
-| If you want GPIO4 for… | Then |
-|---|---|
-| another ADC input | you lose battery monitoring entirely. There is no alternative path |
-| a digital output | **do not.** You are driving into the top of a divider connected to `VBAT`; at minimum you fight the divider, and you can push current into the sense node |
-| a digital input | works, but the fitted divider holds it near V<sub>BAT</sub>/2 with no battery and near 2.5 V on USB — it is not a clean input |
-
-There is a subtler conflict too: **ADC2 is unusable while Wi-Fi is active** on ESP32-S3.
-GPIO4 is on **ADC1**, so battery sensing is safe — but it means one of your scarce ADC1
-channels is permanently spoken for, and if you also need an analogue sensor you must keep it
-on ADC1 (GPIO1–GPIO10) rather than reaching for ADC2 pins.
-
-## 4. What the reading means, and what it does not
-
-- **There is no state-of-charge gauge.** No BQ27220, no coulomb counter. You are inferring
-  charge from terminal voltage under unknown load, which on a LiPo is worth roughly ±20 % in
-  the flat part of the curve.
-- **There is no on-board battery protection.** LilyGO's maintainer, 2025-02-06:
-  *"No built-in battery protection, needs to be used with a lithium-ion battery with battery
-  protection."* Your firmware's low-voltage cutoff is not a substitute for a protected cell —
-  it stops working the moment your firmware crashes.
-- **While charging, the terminal voltage is the charger's output**, not the cell's state.
-- **With USB attached you read ~2.5 V regardless**, so any "is the battery low" logic must
-  first detect USB presence — and the only way to do that on this board is to notice the
-  reading is pinned near 2.5 V, because `VBUS` is not sensed by any GPIO.
-
-## 5. What was not established, and how to settle it
-
-| Open question | How to settle it |
-|---|---|
-| Is the divider really 100 k/100 k to ground, or 100 k/100 k with a series gate that changes the ratio? | Trace `R2`/`R4`/`Q4` on the schematic sheet with a netlist extractor, or measure a board with no battery and a known voltage on the JST connector |
-| What drives `Q4`'s gate? Is the divider disconnected in deep sleep? | Same. This matters for sleep current — a permanently connected 200 kΩ divider across a 4.2 V cell draws ~21 µA, which is comparable to the whole deep-sleep budget |
-| Exact ADC attenuation LilyGO's own example uses | Read `examples/GetBatteryVoltage/GetBatteryVoltage.ino` @ `ec889e7` (retained in scratch); it is the vendor's reference |
-
-The netlist route is available in this repository —
-[`tools/altium_pdf_netlist.py`](../../../../tools/altium_pdf_netlist.py) — but it needs
-`pdftotext -bbox` XML and poppler was not installed on the host used for this pass. Recorded
-in [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-## Cross-references
-
-- [`power-and-battery.md`](power-and-battery.md) — charging, charge current, the GPIO15 gate
-- [`deep-sleep.md`](deep-sleep.md) — why the divider matters for sleep current
-- [`../pinouts-and-buses.md`](../pinouts-and-buses.md) — the full GPIO map
diff --git a/devices/lilygo/t-display-s3/features/buttons.md b/devices/lilygo/t-display-s3/features/buttons.md
deleted file mode 100644
index cb56c89..0000000
--- a/devices/lilygo/t-display-s3/features/buttons.md
+++ /dev/null
@@ -1,55 +0,0 @@
-# T-Display-S3 — buttons
-
-| Button | GPIO | Role | Notes |
-|---|---|---|---|
-| **BOOT** | **0** | `PIN_BUTTON_1`, and the ESP32-S3 **strapping** pin | active low. Held at reset → ROM download mode |
-| **user** | **14** | `PIN_BUTTON_2` | active low, ordinary GPIO |
-| **RST** | — | hardware reset, **not** a GPIO | cannot be read by software |
-
-Three tactile switches are fitted (`S2`, `S3`, `SW` = `SW-PB` in the schematic designator
-census). Two are next to the USB-C connector; the third is on the opposite long edge.
-
-## Reading them
-
-```cpp
-pinMode(0,  INPUT_PULLUP);   // BOOT
-pinMode(14, INPUT_PULLUP);   // user
-// both read LOW when pressed
-```
-
-Internal pull-ups are sufficient; the schematic shows `RINT 100K`-class parts around the button
-network but the individual nets were not traced.
-
-## The BOOT-button trap
-
-GPIO0 is a strapping pin. **Holding it during reset puts the chip in download mode instead of
-running your firmware.** That is a feature — it is the recovery path — but it means:
-
-- Do not use GPIO0 for anything that could be low at power-on. A momentary button is fine; a
-  sensor output is not.
-- If your product has a case where the button can be pressed while power is applied, users can
-  put it into download mode and see a dead device.
-
-## Wake from sleep
-
-`examples/Sleep/Sleep.ino` @ `ec889e789b3cf093412689a143f7f37b42b56af7` is LilyGO's reference.
-GPIO0 and GPIO14 are both RTC-capable on the ESP32-S3, so either works with
-`esp_sleep_enable_ext0_wakeup()` / `ext1`. Details and the current implications:
-[`deep-sleep.md`](deep-sleep.md).
-
-## AceButton and debouncing
-
-LilyGO's AMOLED examples pull in `AceButton v1.10.1`; the base-board examples debounce by hand.
-Either is fine. There is no hardware debounce on this board.
-
-## Comparison with the rest of the family
-
-| Board | Buttons |
-|---|---|
-| T-Display-S3 / Touch | GPIO0, GPIO14, RST |
-| T-Display-S3 AMOLED (all) | GPIO0, **GPIO21**, RST |
-| T-Display-S3 Long | GPIO0 + a **hardware slide switch** (`SW1` = `MSK12C02-HB`) |
-| T-Display-S3 Pro | **three** user buttons: GPIO0, GPIO12, GPIO16 (`BOARD_USER_BUTTON {0,12,16}`) |
-
-**GPIO14 is not portable.** Code that hardcodes `PIN_BUTTON_2 14` will read a floating pin on
-every AMOLED board.
diff --git a/devices/lilygo/t-display-s3/features/deep-sleep.md b/devices/lilygo/t-display-s3/features/deep-sleep.md
deleted file mode 100644
index 0de9c08..0000000
--- a/devices/lilygo/t-display-s3/features/deep-sleep.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# T-Display-S3 — deep sleep
-
-> **No current measurement exists for this board**, from LilyGO or from this pass. What follows
-> is the mechanism and the known traps, clearly separated from the numbers we do not have.
-
-## Reference example
-
-`examples/Sleep/Sleep.ino` @ **`ec889e789b3cf093412689a143f7f37b42b56af7`** — LilyGO's own,
-and the only vendor guidance. It uses the standard `esp_sleep_*` API.
-
-## What to switch off before sleeping
-
-In this order:
-
-```cpp
-// 1. Backlight
-digitalWrite(38, LOW);
-// 2. Put the panel to sleep (controller-level), then
-// 3. Drop the whole V3V rail — panel, 3V header pin, touch controller
-digitalWrite(15, LOW);
-// 4. Hold GPIO15 low through sleep, or it floats and the rail may come back
-gpio_hold_en((gpio_num_t)15);
-gpio_deep_sleep_hold_en();
-// 5. Sleep
-esp_sleep_enable_ext0_wakeup((gpio_num_t)0, 0);   // BOOT button, active low
-esp_deep_sleep_start();
-```
-
-**Step 4 is the one people miss.** Without `gpio_hold_en()`, GPIO15 is released when the
-digital core powers down, and the rail's behaviour then depends on the gate's pull network —
-which was not traced by this pass ([`../gaps-and-conflicts.md`](../gaps-and-conflicts.md) K3).
-Holding it is cheap and removes the question.
-
-## Wake sources
-
-| Source | Pin | Works |
-|---|---|---|
-| `ext0` / `ext1` | GPIO0 (BOOT), GPIO14 | yes, both are RTC-capable |
-| Timer | — | yes |
-| Touch IRQ | GPIO16 | RTC-capable, **but** the controller is on the gated rail, so it cannot signal if you dropped `V3V` |
-| ULP | — | supported; `examples/ULP_ADC` and `examples/ULP_Count` exist in the repo and note they need *"arduino_esp32 version: 3.0.0-rc3"* — i.e. **a core newer than the 2.0.14 the rest of the repo pins**. That is an internal contradiction in LilyGO's own repo, recorded here |
-
-## The pins that go high in sleep
-
-Firsthand report, [issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313)
-(2025-07-28), MicroPython:
-
-> "After I do LOW it turns off and stays off during 10 seconds of normal sleep, but immediately
-> when I go into deep sleep mode it turns on again with a weak light."
-
-Cause, confirmed by LilyGO with PCB photographs: **fitted pull-up resistors on GPIO16 and
-GPIO17**. When the driver stops holding them low at sleep entry, they go high. If anything is
-connected to those pins it will be driven — and it will also **draw current for the whole sleep
-period**, which is the part the reporter did not raise but which matters for a battery device.
-
-Mitigation: `gpio_hold_en()` on 16 and 17 as well, or remove the resistors (LilyGO's own
-suggestion; they are on the back of the panel).
-
-## The other sleep-current unknown
-
-The battery-sense divider is two `100K` resistors. If it is permanently across `VBAT` — i.e. if
-`Q4` does not disconnect it — that is **≈ 21 µA at 4.2 V**, continuously. On a board whose
-whole deep-sleep budget is plausibly in the hundreds of microamps, that is not negligible, and
-it is exactly what was not established. See
-[`battery-voltage-measurement.md`](battery-voltage-measurement.md) §5.
-
-## Numbers we have, and their provenance
-
-| Figure | Board | Source | Applies here? |
-|---|---|---|---|
-| ~230 µA deep sleep, external GPIO0 wake | T-Display-S3 **AMOLED** | `LilyGo-AMOLED-Series/README.MD` @ `6d1dc00`, vendor table | **No.** Different display, different regulators, different charger. Quoted only for order of magnitude |
-| ~1.1 mA deep sleep, timer wake | T-Display AMOLED **Lite** | same table | No |
-| 90–230+ mA active at 240 MHz with Wi-Fi | AMOLED boards | same table | Roughly, since the SoC dominates |
-
-**LilyGO publishes no deep-sleep figure for the base T-Display-S3.** Anyone quoting one is
-quoting a different board.
-
-## Also relevant
-
-`USB CDC On Boot` interacts with sleep in a way that surprises people: on wake, if CDC is
-enabled and no host is attached, the core can block again. Battery devices should build with
-`-UARDUINO_USB_CDC_ON_BOOT`. See [`usb.md`](usb.md).
diff --git a/devices/lilygo/t-display-s3/features/display.md b/devices/lilygo/t-display-s3/features/display.md
deleted file mode 100644
index 13847d6..0000000
--- a/devices/lilygo/t-display-s3/features/display.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# T-Display-S3 — display
-
-| | |
-|---|---|
-| Panel | 1.9″ IPS, **170 × 320** portrait-native (LilyGO markets it landscape) |
-| Controller | **Sitronix ST7789V** → [component](../../../../components/sitronix/st7789v/README.md) |
-| Bus | 8-bit **Intel-8080 parallel**, `WR`-strobed |
-| Pins | `D0..D7` = 39,40,41,42,45,46,47,48 · `WR` 8 · `RD` 9 · `DC` 7 · `CS` 6 · `RST` 5 |
-| Backlight | **GPIO38** → Awinic **AW9364DNR** boost driver → [component](../../../../components/awinic/aw9364/README.md) |
-| Panel power | **gated by GPIO15** — must be HIGH |
-| GRAM offset | **35 columns** (170-px panel on a 240-wide controller) |
-| Colour | inversion **on**; RGB/BGR is [disputed](../gaps-and-conflicts.md#g3--colour-order-rgb-or-bgr) |
-
-## Minimum working sketch
-
-```cpp
-#include <TFT_eSPI.h>            // requires Setup206 selected — see below
-TFT_eSPI tft = TFT_eSPI();
-
-void setup() {
-    pinMode(15, OUTPUT); digitalWrite(15, HIGH);   // panel rail — WITHOUT THIS, NOTHING
-    pinMode(38, OUTPUT); digitalWrite(38, HIGH);   // backlight
-    tft.init();
-    tft.setRotation(1);          // 320x170 landscape
-    tft.fillScreen(TFT_BLACK);
-    tft.drawString("hello", 10, 10, 4);
-}
-void loop() {}
-```
-
-Two `pinMode`/`digitalWrite` pairs before `tft.init()`. Omit the first and you get a lit
-backlight over a dead panel — which reads as a broken screen, and is the most common false
-hardware diagnosis on this board.
-
-## Choosing a library
-
-Full decision guide, including why this matters more than usual:
-[`guides/hardware/parallel-8080-lcd-buses.md`](../../../../guides/hardware/parallel-8080-lcd-buses.md).
-
-| Library | Verdict for this board |
-|---|---|
-| **`TFT_eSPI`** | LilyGO's default. Richest API. **Requires editing `User_Setup_Select.h` inside the library** to select `Setup206_LilyGo_T_Display_S3.h`, and that edit is destroyed by any library update. Documented broken on Arduino core > 2.0.14 |
-| **`Arduino_GFX`** | Configuration lives in your sketch, so it survives updates and works on core 3.x. **LilyGO's own recommended hardware test** for exactly that reason |
-| **`LovyanGFX`** | Best if one codebase must span several boards in this family |
-| **ESPHome** | `mipi_spi` with model `T-DISPLAY-S3` — pins, offset and the GPIO15 enable are all built in |
-| **LVGL** | 8.x for LilyGO's examples (`examples/lv_demos/lv_conf.h` @ `ec889e7` is an LVGL 8 config). 9.x needs porting |
-
-The `TFT_eSPI` edit, verbatim:
-
-```c
-// TFT_eSPI/User_Setup_Select.h
-//#include <User_Setup.h>
-#include <User_Setups/Setup206_LilyGo_T_Display_S3.h>
-```
-
-Community workaround worth knowing, from
-[issue #212](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212) (2024-01-03): keep a
-copy of your edited `User_Setup_Select.h` outside the library and restore it after every
-update. *"Confusing? YES!"* — the same commenter.
-
-## Backlight and dimming
-
-GPIO38 drives the **enable input of an AW9364 boost driver**, not an LED directly.
-
-- Crude PWM (`ledcAttach(38, 5000, 8); ledcWrite(38, duty)`) works and is what everyone does.
-- **Arduino core 3.x renamed the API**: `ledcSetup`/`ledcAttachPin` → `ledcAttach`/`ledcDetach`.
-  LilyGO's snippets predate this. Firsthand report:
-  [r/esp32, 2026-05-25](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/).
-- The AW9364 also implements a **one-wire pulse-count** brightness protocol (16 steps selected
-  by counting rising edges inside a timeout). Nothing in LilyGO's examples uses it. If your PWM
-  dimming behaves oddly at low duty — flicker, or steps rather than a ramp — that is why: you
-  are feeding pulse trains into a part that counts pulses.
-- Brightness is **not** linear in duty cycle. Do not build a UI slider on the assumption.
-
-## Rotation and geometry
-
-`setRotation(1)` gives 320 × 170 landscape with the USB-C port on the left. Rotation 3 flips
-it. Rotations 0 and 2 give 170 × 320 portrait. The GRAM offset applies in all of them, which
-is why it must be a library setting rather than something you subtract yourself.
-
-## Resource cost
-
-| Resource | Taken |
-|---|---|
-| GPIO | **13** (8 data + WR + RD + DC + CS + RST), plus GPIO38 backlight and GPIO15 rail = **15** |
-| Peripheral | ESP32-S3 **LCD_CAM** i80 unit (one of one) |
-| DMA | one GDMA channel when using `esp_lcd`/`Arduino_GFX` DMA paths |
-| PSRAM | a full 170×320 RGB565 framebuffer is 108.8 KB; LVGL double-buffered at full height needs 217.6 KB — this is why **`PSRAM = OPI PSRAM` is mandatory** for the vendor LVGL demo |
-
-## Known failures and their causes
-
-| Symptom | Cause | Fix |
-|---|---|---|
-| Backlight on, screen black | GPIO15 not high | two lines in `setup()` |
-| Nothing at all, sketch uploaded fine | `User_Setup_Select.h` overwritten | re-select Setup206, or use `Arduino_GFX` to prove the hardware |
-| Image shifted, garbage band at one edge | GRAM offset missing | `CGRAM_OFFSET` / `offset_width: 35` / the two `35`s in the `Arduino_GFX` constructor |
-| Mosaic, speckle, tearing | pixel clock too high (or too low) | try 10 MHz |
-| Half the display garbage | offset **and** wrong width | [issue #128](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/128) |
-| Colours inverted or R/B swapped | inversion or colour-order setting | one `#define`, see [G3](../gaps-and-conflicts.md#g3--colour-order-rgb-or-bgr) |
-| Compile `#error` about Setup206 | newer TFT_eSPI detecting the unselected setup | [issue #326](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/326) |
-| Runs out of memory in LVGL | `PSRAM` not set to OPI | [issue #256](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/256) |
diff --git a/devices/lilygo/t-display-s3/features/gpio-and-expansion.md b/devices/lilygo/t-display-s3/features/gpio-and-expansion.md
deleted file mode 100644
index 51e9fb7..0000000
--- a/devices/lilygo/t-display-s3/features/gpio-and-expansion.md
+++ /dev/null
@@ -1,80 +0,0 @@
-# T-Display-S3 — GPIO, headers and expansion
-
-## What is actually free
-
-Start from 45 GPIOs and subtract:
-
-| Consumed by | Pins | Count |
-|---|---|---|
-| In-package OPI PSRAM (ESP32-S3**R8**) | 26–37 | 12 |
-| LCD 8080 bus | 5, 6, 7, 8, 9, 39, 40, 41, 42, 45, 46, 47, 48 | 13 |
-| Backlight | 38 | 1 |
-| `V3V` rail gate | 15 | 1 |
-| Native USB | 19, 20 | 2 |
-| UART0 — [unusable as GPIO under Arduino](../pinouts-and-buses.md#6-gpio43--gpio44-are-not-usable-as-gpio-under-arduino) | 43, 44 | 2 |
-| Battery sense (only path) | 4 | 1 |
-| Buttons | 0, 14 | 2 |
-| I²C (with fitted pull-ups) | 17, 18 | 2 |
-| Touch IRQ/RST — **16 has a fitted pull-up even on non-touch boards** | 16, 21 | 2 |
-
-**Genuinely free and unencumbered: GPIO1, 2, 3, 10, 11, 12, 13** — seven pins, three of which
-(11, 12, 13) you lose if you fit the TF Shield.
-
-GPIO3 is the ESP32-S3's JTAG-source strapping pin; leaving it floating is fine, but do not
-hold it at a fixed level at reset unless you know what you are asking for.
-
-## Headers
-
-Two 12-pin 0.1″ rows (`P1`, `P2` in the schematic, both `Header 12`) plus a 2-pin `P3`.
-Sold **soldered** (`H577`) or **unsoldered** (`H569`) — that choice is a purchase option, not
-a revision.
-
-| Pin name | Value | Notes |
-|---|---|---|
-| `VBUS` | 5 V | **output only**, from USB-C. Cannot power the board |
-| `VBAT` | 4.2 V | battery rail |
-| `3V` | 3.3 V | **≤ 100 mA**, and **gated by GPIO15** |
-| `GND` | — | |
-
-The 100 mA figure is LilyGO's own. It is a real constraint: a GPS module or an SD breakout with
-a burst current above that will brown out the rail your *display* is on.
-
-## The SH1.0 4-pin connector
-
-A 4-pin 1.0 mm connector carries the I²C bus (GPIO17/18) plus power and ground. LilyGO markets
-it loosely as Qwiic-style.
-
-**It is not Qwiic-compatible.** [Issue #181](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/181)
-(2023-08-08, 12 comments, "None of my Qwiic (I2C) sensors is recognized") is what happens when
-you assume otherwise: the connector is SH1.0, Qwiic is JST-SH 1.0 with a **defined pin order**,
-and LilyGO's order is not guaranteed to match. Check continuity before plugging in a sensor —
-a reversed power/ground pair kills the sensor, not the board.
-
-The same connector is discussed in [issue #117](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/117)
-where a user tried to hang a DS18B20 off it via GPIO43 and could not — that is the UART0
-problem, not the connector.
-
-## I²C bus sharing
-
-One bus, GPIO17/18, with **10 kΩ pull-ups fitted on board** (`RIIC`, `RIID`). On a Touch board
-the touch controller is already on it. Adding external devices works — different addresses —
-but note:
-
-- Two 10 kΩ pull-ups plus whatever your breakout adds can over-pull the bus. Most Qwiic
-  breakouts fit 2.2–10 kΩ; three in parallel is too stiff for 3.3 V at 400 kHz on long wires.
-- The CST touch parts NAK while idle, which confuses simple scanners.
-- **Everything on this bus is on the GPIO15-gated rail.** Drop the rail, lose the bus.
-
-## Add-on boards LilyGO sells for it
-
-| Board | What it adds | SKU / price 2026-09-07 |
-|---|---|---|
-| **T-Display TF Shield** | 1-bit SDMMC microSD on GPIO11/12/13 | `H609` USD 2.51 · `H610` USD 2.38 |
-| **T-Display-S3 MIDI** | MIDI in/out; own schematic `SCH_T-Display-S3-MIDI_V1.1.pdf` | `H656` USD 15.47 |
-| **T-Display keyboard** | QWERTY keypad | `t-display-keyboard`, USD 6.88–30.98 |
-| **T-Display-S3 Shell** | enclosure, grey or black | `L929`/`L930` USD 5.02 |
-
-## Level and drive
-
-3.3 V logic. No 5 V-tolerant pins. The ESP32-S3's per-pin drive is configurable up to 40 mA
-but the sane working figure is 20 mA, and the **total** across the chip is the real limit.
diff --git a/devices/lilygo/t-display-s3/features/microsd.md b/devices/lilygo/t-display-s3/features/microsd.md
deleted file mode 100644
index f74dbc7..0000000
--- a/devices/lilygo/t-display-s3/features/microsd.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# T-Display-S3 — microSD
-
-## There is no microSD slot on this board
-
-The `pin_config.h` files define:
-
-```c
-/* External expansion */
-#define PIN_SD_CMD    13
-#define PIN_SD_CLK    11
-#define PIN_SD_D0     12
-```
-
-and the comment `/* External expansion */` is doing a lot of work. LilyGO states it plainly:
-
-> "SD card pins (SD CMD/CLK/D0) are only available on boards with the SD Shield add-on. The
-> standard T-Display-S3 board does not have an onboard SD card slot."
-> — `README.md` @ `ec889e789b3cf093412689a143f7f37b42b56af7`
-
-The designator census of `schematic/T_Display_S3.pdf` confirms it: no card-socket designator
-appears anywhere on the sheet.
-
-## The T-Display TF Shield
-
-| | |
-|---|---|
-| Product | **T-Display TF Shied** [sic], store handle `t-display-tf-shied` |
-| SKUs | `H609` (pin header) **USD 2.51** · `H610` (female header) **USD 2.38**, both in stock 2026-09-07 |
-| Interface | **1-bit SDMMC**: `CMD` GPIO13, `CLK` GPIO11, `D0` GPIO12 |
-| Mechanical drawing | `dimensions/SD-Shield.DXF` in the board repo @ `ec889e7` |
-| Vendor example | `examples/sd/` |
-| Component record | [`generic/micro-sd-sdmmc`](../../../../components/generic/micro-sd-sdmmc/README.md) |
-
-1-bit, not 4-bit. Expect a few MB/s, not tens.
-
-```cpp
-#include "SD_MMC.h"
-SD_MMC.setPins(11 /*CLK*/, 13 /*CMD*/, 12 /*D0*/);
-if (!SD_MMC.begin("/sdcard", true /* 1-bit mode */)) { /* … */ }
-```
-
-The `true` is mandatory — it selects 1-bit mode. Omitting it makes the driver look for D1–D3
-that are not wired.
-
-## If you do not fit the shield
-
-GPIO11, 12 and 13 are **free** and are the most useful spare pins on the board, because they
-are RTC-capable, ADC2-capable and physically adjacent on the header. Given how few pins remain
-after the LCD bus and the PSRAM, that matters — see
-[`gpio-and-expansion.md`](gpio-and-expansion.md).
-
-## Alternative
-
-An SPI microSD breakout on any three free pins works and avoids the shield. It is slower than
-1-bit SDMMC but not dramatically so at these speeds, and it frees you from the shield's
-mechanical footprint.
diff --git a/devices/lilygo/t-display-s3/features/power-and-battery.md b/devices/lilygo/t-display-s3/features/power-and-battery.md
deleted file mode 100644
index 8dad4a7..0000000
--- a/devices/lilygo/t-display-s3/features/power-and-battery.md
+++ /dev/null
@@ -1,114 +0,0 @@
-# T-Display-S3 — power, battery and charging
-
-> The single highest-value page for this board. Most "dead board" reports resolve here.
-
-## 1. The GPIO15 gate — read this first
-
-```cpp
-pinMode(15, OUTPUT);
-digitalWrite(15, HIGH);   // enables the V3V rail: panel, 3V header pin, peripherals
-```
-
-> "**Note:** GPIO15 is the peripheral power control pin. You must set it HIGH before using the
-> board, otherwise the LCD and other peripherals will not work."
-> — `README.md` @ `ec889e789b3cf093412689a143f7f37b42b56af7`
-
-**Why it only bites on battery:** the LDO output is present whenever USB is attached, so a
-board on a desk works with or without the line. Unplug it and the gate matters. This produces
-the classic report *"works on USB, dead on battery"* — [issue #79](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/79)
-exists solely because of it, and a commenter's summary is worth quoting:
-
-> "it is so ridiculous there is nothing mentioned on their site about pulling pin 15 high to
-> get it to power on when using the little jst battery input." — 2023-10-06
-
-**Free diagnostic:** the **green LED** sits on the `V3V` rail. On battery, green off = GPIO15
-low. On USB it is always on, which is why the LED does not help you at the desk.
-
-**It applies in MicroPython too**, and there is no `setup()` to hide it in — see
-[`../development.md`](../development.md#6-micropython-and-other-languages).
-
-## 2. Power topology
-
-```
-USB-C (U5) ── 5V ──┬─→ charger U6 ──→ VBAT ─┬─→ LDO U7 (AP2112K-3.3) ──→ 3V3 (SoC, always on)
-                   │                        │
-JST 1.25mm ────────┴────────────────────────┘        └─→ Q2/Q3 (SI2301) gate ──→ V3V rail
-                                                          ▲                        │
-                                                     GPIO15                        ├→ LCD panel
-                                                                                   ├→ 3V header pin
-                                                                                   └→ green LED8
-```
-
-Designators from `schematic/T_Display_S3.pdf` @ `ec889e7`. **The gate's exact wiring was not
-traced** — see [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md) K1.
-
-| Rail | Value | Notes |
-|---|---|---|
-| USB-C input | 5 V | the **only** charger input; `VBUS` is not on the header |
-| Battery | 3.7–4.2 V, JST **1.25 mm** 2-pin | polarity is not standardised across vendors — **check before plugging in** |
-| Header `VBUS` pin | 5 V **out**, sourced from USB-C | capacity = whatever your USB supply gives |
-| Header `VBAT` pin | 4.2 V | |
-| Header `3V` pin | 3.3 V, **≤ 100 mA** | vendor figure. Gated by GPIO15 |
-
-## 3. Charging
-
-| | |
-|---|---|
-| Charger | `U6`; schematic says **TP4065**, a shipping board carried a 5-lead TSOT-23 marked `65b311` — [G2](../gaps-and-conflicts.md#g2--charger-part-number-vs-shipping-hardware) |
-| Current | README: **500 mA**. Schematic note: **`R13 IBAT (mA) = 580`** with a 2 kΩ program resistor. Unresolved |
-| Indicator | **red LED1** — *flashes or glows dimly with no battery*, solid while charging, off when full |
-| Protection | **none on board.** LilyGO maintainer, 2025-02-06: *"No built-in battery protection, needs to be used with a lithium-ion battery with battery protection"* |
-| Path management | none evidenced. There is no PPM/power-path IC; this is a plain linear charger |
-
-<a id="changing-the-charge-current"></a>
-### Changing the charge current
-
-The commonly cited procedure — replace the 2 kΩ `PROG` resistor with 10 kΩ for ≈130 mA — comes
-from the **TP4056/TP4065 datasheet equation** (I = 1200 V / R<sub>PROG</sub>) applied to the
-published schematic. **It may not describe the part actually fitted** (G2). LilyGO's README
-points at [issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230) for this.
-
-If you must: identify `U6` on your board *first*, read the marking, and find the datasheet for
-that part. Do not desolder on the strength of a PDF that a careful owner has already shown to
-disagree with hardware.
-
-### Why this matters for the shell
-
-LilyGO sells the board with a shell and a **700 mAh** battery (`K204-01`, `K206-01` — both
-out of stock 2026-09-07). Cells that physically fit third-party shells are commonly
-**350–400 mAh**, and 500–580 mA into a 350 mAh cell is **1.4–1.7 C** — above the 1 C most
-datasheets allow. That is precisely the concern that opened issue #230.
-
-Community-reported working combination (firsthand ownership, 2026-08-30, r/esp32): *MakerFocus
-3.7 V 1000 mAh LiPo #952540*, in a printed
-[battery backpack for the LilyGO shell](https://www.printables.com/model/1065538-lilygo-t-display-s3-shell-battery-backpack).
-At 1000 mAh, 580 mA is a comfortable 0.6 C.
-
-## 4. Powering from anything else
-
-- **You cannot charge from the 5 V pin.** `VBUS` is not brought out.
-  [Issue #42](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/42), 2022-11-07; LilyGO's
-  answer was to solder a wire to `VBUS`. Still true in 2026.
-- **Feeding 5 V into the 5 V pin back-powers the charger input.** Firsthand report, 2023-11-01:
-  *"The charging voltage jumps up to 5V, because of backpowering. If you're using an
-  unprotected battery it might blow up in this case!"* — one owner, not independently
-  reproduced, but consistent with the topology.
-- **3.3 V into the 3V pin** is discussed in [issue #205](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/205);
-  the answers there are community, not vendor, and involve back-feeding an LDO output. Treat
-  as unsupported.
-- **The supported inputs are USB-C and the JST connector.** Anything else is a modification.
-
-## 5. Consumption
-
-**No measurement exists in this record.** LilyGO publishes current figures for its AMOLED
-boards and **not** for this one. For scale, the same-SoC AMOLED boards are documented at
-*"(240MHz) WiFi On 90~230+ mA"* active and *"About 230uA"* in deep sleep — that is a different
-board with a different display and different regulators, and is offered as an order of
-magnitude only. See [`deep-sleep.md`](deep-sleep.md) and
-[`../performance.md`](../performance.md).
-
-## Cross-references
-
-[`battery-voltage-measurement.md`](battery-voltage-measurement.md) ·
-[`usb.md`](usb.md) · [`deep-sleep.md`](deep-sleep.md) ·
-[`../../t-display-s3-shared/board-revision-drift.md`](../../t-display-s3-shared/board-revision-drift.md)
diff --git a/devices/lilygo/t-display-s3/features/touch.md b/devices/lilygo/t-display-s3/features/touch.md
deleted file mode 100644
index 366e527..0000000
--- a/devices/lilygo/t-display-s3/features/touch.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# T-Display-S3 — touch (Touch SKU only)
-
-| | |
-|---|---|
-| Fitted on | `H587` / `H589` "Touch" SKUs and the `H717`-style shell bundles. **Not** on `H569`/`H577` |
-| Controller | **Hynitron CST816S** (early boards) or **CST328** (later) — see [revision R1](../../t-display-s3-shared/board-revision-drift.md#r1--t-display-s3-touch-cst816s--cst328) |
-| Bus | I²C on **GPIO17 (SCL) / GPIO18 (SDA)**, 10 kΩ pull-ups fitted on board |
-| Address | **`0x15`** (CST816S) · **`0x1A`** (CST328) |
-| IRQ / RST | **GPIO16** (`TOUCH_INT`) / **GPIO21** (`TOUCH_RES`) |
-| Component records | [`hynitron/cst816d`](../../../../components/hynitron/cst816d/README.md) (CST816 family) · [`hynitron/cst328`](../../../../components/hynitron/cst328/README.md) |
-
-## The generation split, and the single flag that decides it
-
-LilyGO's `platformio.ini` @ `ec889e7` carries, in the **shared** `[env]` section:
-
-```ini
-build_flags =
-    …
-    -DTOUCH_MODULES_CST_MUTUAL
-```
-
-`TouchLib` uses this to select the **mutual-capacitance** driver — the CST328 branch. The
-alternative is `-DTOUCH_MODULES_CST_SELF` for the self-capacitance **CST816S**. Get it wrong
-and the driver probes the wrong address with the wrong register semantics, and reports **no
-touch controller found** — which is exactly [issue #125](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/125)
-(15 comments, "no Touch IC found").
-
-**The evidence that both generations exist** is that the board repository ships **both**
-register documents:
-
-| File in `datasheet/` @ `ec889e7` | Bytes | Now filed at |
-|---|---|---|
-| `CST816S寄存器说明-20190508.pdf` | 76 816 | [`components/hynitron/cst816d/artifacts/`](../../../../components/hynitron/cst816d/artifacts/cst816s-register-guide-cn-20190508-lilygo-mirror.pdf) |
-| `CST328数据手册V2.2.pdf` | 1 297 291 | [`components/hynitron/cst328/artifacts/`](../../../../components/hynitron/cst328/artifacts/cst328-datasheet-cn-v2.2-lilygo-mirror.pdf) |
-
-A board with one controller does not need two register manuals.
-
-## Identify your board in 30 seconds
-
-Run `examples/I2CScan/I2CScan.ino` from the repo, or any I²C scanner on GPIO17/18:
-
-```
-0x15 → CST816S  → build with -DTOUCH_MODULES_CST_SELF
-0x1A → CST328   → build with -DTOUCH_MODULES_CST_MUTUAL   (LilyGO's current default)
-nothing → you have a non-touch board, or GPIO15 is low
-```
-
-That last line matters: **the touch controller is on the gated `V3V` rail**, so an I²C scan
-with GPIO15 low finds nothing and looks like a hardware fault.
-
-## Minimal use
-
-LilyGO's `examples/touch_test/touch_test.ino` and `examples/CapacitiveTouch/` @ `ec889e7` are
-the reference. Both include a `pin_config.h` with `PIN_TOUCH_INT 16` / `PIN_TOUCH_RES 21` and
-drive reset before probing.
-
-Reset sequence matters: hold `TOUCH_RES` low ≥ 10 ms, release, wait ≥ 50 ms, then probe. Many
-"intermittent touch" reports are a missing reset.
-
-## Known problems
-
-- **Constant I²C errors with nothing else on the bus** —
-  [issue #168](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/168) (21 comments,
-  2023-06-29). The CST parts NAK aggressively while asleep; the driver must tolerate it rather
-  than treating a NAK as a fault.
-- **Touch works under Arduino but not ESP-IDF** —
-  [issue #156](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/156). `TouchLib` is an
-  Arduino library; ESP-IDF users need `LilyGo-Display-IDF` or their own driver.
-- **GPIO16 is pulled up even on non-touch boards** — see
-  [`../pinouts-and-buses.md`](../pinouts-and-buses.md#5-gpio16--gpio17-are-not-free). Do not
-  infer "touch fitted" from a high GPIO16.
-
-## Resource cost
-
-GPIO16, GPIO17, GPIO18, GPIO21 — four pins, of which two (17/18) are the board's only I²C bus
-and are shared with the SH1.0 external connector. Adding an external I²C sensor means sharing
-with the touch controller; that works (different addresses) but the CST parts' NAK behaviour
-can confuse naive bus scanners. See [issue #181](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/181).
diff --git a/devices/lilygo/t-display-s3/features/usb.md b/devices/lilygo/t-display-s3/features/usb.md
deleted file mode 100644
index c23630b..0000000
--- a/devices/lilygo/t-display-s3/features/usb.md
+++ /dev/null
@@ -1,144 +0,0 @@
-# T-Display-S3 — USB, and the `USB CDC On Boot` trap
-
-> Applies to: **every board in the [T-Display-S3 family](../../t-display-s3-shared/README.md)**,
-> and to essentially every native-USB ESP32-S3/C3/S2 board. Written here because this is where
-> people hit it. Evidence status: **vendor-documented** + **many independent user reports**;
-> not hardware-verified by this pass.
-
-## The one-paragraph version
-
-The T-Display-S3 has **no USB-UART bridge**. There is no CH340, no CP2102, no FTDI — the
-ESP32-S3's own USB peripheral drives the Type-C connector directly (GPIO19/20 → `U5`). That
-buys you flashing, `Serial`, JTAG debugging and USB-device roles over one cable. It costs you
-three things that a bridge would have given you for free: an auto-reset circuit, a serial port
-that exists when your firmware is broken, and a `Serial` object that does not care whether a
-host is attached. **The board setting `USB CDC On Boot` decides which of those you lose**, and
-with it selected — as LilyGO requires — a board running from a battery **stops during startup
-and waits for a PC that will never arrive**.
-
-## Why a board "does nothing"
-
-```
-Symptom                                   Almost always
-────────────────────────────────────────  ─────────────────────────────────────────────
-Works on USB, dead on battery             GPIO15 not driven high  → power-and-battery.md
-Works on USB, hangs on battery            USB CDC On Boot = Enable → this page
-No serial output at all                   USB CDC On Boot = Disable, and you are
-                                          watching the USB port instead of GPIO43/44
-Port appears then vanishes, repeatedly    firmware crashed/reconfigured USB → manual
-                                          download mode (below)
-```
-
-The second and third rows are the *same setting* producing opposite symptoms, which is why the
-trap survives so well: whichever way you have it set, the failure looks like a hardware fault.
-
-## What the setting actually does
-
-With `USB CDC On Boot = Enable` (PlatformIO: `-DARDUINO_USB_CDC_ON_BOOT=1`), the Arduino core
-aliases `Serial` to the USB CDC device and, during core startup, **waits for the host to open
-the port** before proceeding. On a desk with a PC attached that wait is invisible. On battery
-it never ends.
-
-LilyGO documents it, twice, in two different repos:
-
-> "**If you use an external power supply instead of USB-C, please disable the CDC option.** The
-> board waits for USB access on startup when CDC is enabled.
-> — Arduino IDE: `Tools` > `USB CDC On Boot` > `Disable`
-> > Disabling USB CDC turns off Serial redirection to USB-C. Serial output will come from
-> > GPIO43 and GPIO44 instead."
-> — `T-Display-S3/README.md` FAQ 5 @ `ec889e789b3cf093412689a143f7f37b42b56af7`
-
-> "If you use external power supply instead of USBC, please turn off the CDC option. This is
-> because the board will wait for USB access when it starts."
-> — `LilyGo-AMOLED-Series/README.MD` FAQ 4 @ `6d1dc008b94578cc34ba4a0f3b223dd808ca963f`
-
-PlatformIO form, verbatim from the same FAQ — note that it uses `-U` (undefine) rather than
-`=0`, because the core tests for *definedness*:
-
-```ini
-build_flags =
-    ; -DARDUINO_USB_CDC_ON_BOOT=1   ; enable: prints, and blocks at startup awaiting a terminal
-    -UARDUINO_USB_CDC_ON_BOOT        ; disable: no blocking when running from the battery
-```
-
-**`-DARDUINO_USB_CDC_ON_BOOT=0` is not equivalent to `-U…` in all core versions.** Use `-U`.
-
-## The decision table
-
-| Your situation | `USB CDC On Boot` | Where `Serial` goes | Cost |
-|---|---|---|---|
-| Developing at a desk, board on USB | **Enable** | USB-C | none |
-| Shipping a battery-powered device | **Disable** | GPIO43 (TX) / GPIO44 (RX) at 115200 | you need a USB-TTL adapter to see logs |
-| Battery device, but you still want USB logs | Enable **and** never let the code depend on `Serial` being open | USB-C | boot still blocks — do not do this |
-| Using the board as a USB HID/MIDI device | Enable, `USB Mode = CDC and JTAG` for the built-in JTAG, or the OTG mode for TinyUSB roles | — | the two USB modes are mutually exclusive; see below |
-
-## The second, quieter setting: `USB Mode`
-
-`USB Mode` picks which silicon block owns the port.
-
-| `USB Mode` | PlatformIO flag | Gives you | Takes away |
-|---|---|---|---|
-| **CDC and JTAG** (LilyGO's default) | `-DARDUINO_USB_MODE=1` | hardware USB-Serial-JTAG: flashing, `Serial`, **and built-in JTAG debugging** over the one cable (`debug_tool = esp-builtin`) | TinyUSB device roles — no USB HID, MSC or MIDI |
-| **USB-OTG (TinyUSB)** | `-DARDUINO_USB_MODE=0` | full TinyUSB: HID keyboard/mouse/gamepad, MSC, MIDI — this is what `examples/usb_hid_pad` and the MIDI shield examples need | **the built-in JTAG debugger stops working** |
-
-This is the "USB-OTG" half of the trap. People switch to OTG mode to build a USB HID gadget,
-then find their debugger gone and, worse, that a crashing TinyUSB descriptor takes the whole
-port down — at which point flashing requires the manual button ritual below. The VID/PID also
-changes: native USB-Serial-JTAG enumerates as **`303A:1001`** (per LilyGO's own
-`boards/lilygo-t-display-s3.json`), TinyUSB as whatever your descriptor says.
-
-## Manual download mode — the ritual
-
-When there is no port, or it flashes in and out, put the ROM bootloader in charge. From the
-README, and repeated identically in the AMOLED README:
-
-1. Connect the board via the USB cable.
-2. **Press and hold BOOT** (GPIO0, the button next to USB-C).
-3. While still holding BOOT, **press RST**.
-4. Release **RST**.
-5. Release **BOOT**. The port should now be stable.
-6. Upload.
-7. Press **RST** to exit download mode.
-
-The ROM bootloader's USB stack is in mask ROM, so this works no matter how broken the
-application is. This is the reason a bricked-looking board is almost never bricked — see
-[issue #16 "Device is bricked"](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/16) and
-[#162](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/162), both resolved this way.
-
-## Host-side symptoms worth recognising
-
-- **Linux:** `Can't connect to ttyACM0` — [issue #7](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/7).
-  The device is `/dev/ttyACM*` (CDC-ACM), *not* `/dev/ttyUSB*` (which is what a CH340 gives).
-  If you are looking for `ttyUSB0` you will never find it. `dialout`/`uucp` group membership
-  still applies.
-- **Windows 10:** "does not appear as USB device" — [issue #166](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/166).
-  No driver is needed for CDC-ACM on Win10+; a missing device is a cable (charge-only) or a
-  blocked-boot problem, not a driver problem.
-- **macOS:** enumerates as `/dev/cu.usbmodem*`.
-- **A charge-only USB-C cable will do exactly this too**, and is the single most common cause
-  of "no port" reports across the whole family. Rule it out first.
-
-## Powering from something that is not USB-C
-
-`VBUS` is **not** brought out to the headers on this board. The 5 V header pin is an *output*
-sourced from USB-C. Consequences, from
-[issue #205](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/205) and
-[#42](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/42):
-
-- You **cannot** charge the battery from the 5 V pin, a solar panel or a wireless charger
-  without soldering to `VBUS`. LilyGO's own answer, 2022-11-12: *"We have not considered this
-  situation. Maybe you can solve it by soldering a wire from VBUS."*
-- Feeding 5 V into the 5 V pin **back-powers the charger input**. A firsthand report
-  (2023-11-01): *"The charging voltage jumps up to 5V, because of backpowering. If you're using
-  an unprotected battery it might blow up in this case!"* — evidence class: firsthand
-  measurement by one owner, not independently reproduced, but consistent with the topology.
-- The supported ways in are **USB-C** and **the JST battery connector** (3–6 V per a
-  community answer; LilyGO states 3.7–4.2 V, and the lower bound in that community answer is
-  *not* vendor-confirmed).
-
-## Cross-references
-
-- [`features/power-and-battery.md`](power-and-battery.md) — the GPIO15 gate, charging
-- [`../development.md`](../development.md) — the flags in context, and core versions
-- [`../factory-firmware.md`](../factory-firmware.md) — recovery when nothing else works
-- [`../../t-display-s3-shared/README.md#31-the-usb-cdc-on-boot-trap`](../../t-display-s3-shared/README.md#31-the-usb-cdc-on-boot-trap) — family-level summary
diff --git a/devices/lilygo/t-display-s3/features/wifi-and-ble.md b/devices/lilygo/t-display-s3/features/wifi-and-ble.md
deleted file mode 100644
index 65484ac..0000000
--- a/devices/lilygo/t-display-s3/features/wifi-and-ble.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# T-Display-S3 — Wi-Fi and Bluetooth LE
-
-| | |
-|---|---|
-| Radio | integral to the **ESP32-S3R8** — 2.4 GHz Wi-Fi 4 (b/g/n) + Bluetooth 5 LE. **No 5 GHz** |
-| Antenna | on-board ceramic chip antenna by default; a **u.FL/IPEX** footprint exists |
-| Switching | move a **0 Ω resistor** (`RX` / `RX2` in the schematic; `RX` is fitted at `10R`, `RX2` is marked `NC`) |
-| Matching | `L1 = 2.0 nH` series inductor in the antenna path |
-
-## Switching to an external antenna
-
-> "The default is onboard antenna. If you need to use an external antenna, you need to rotate
-> the resistor in the red position in the image below to the position highlighted in yellow to
-> switch to external antenna mode."
-> — `README.md` @ `ec889e789b3cf093412689a143f7f37b42b56af7`, with an image at `./image/WiFi.png`
-
-The schematic census corroborates the mechanism: `RX` (value `10R`) and `RX2` (explicitly
-`(NC)`) form the two positions, with `XX1`/`XX2` antenna-related parts either side. **This is a
-soldering job on 0402-class parts.** There is no switch and no solder-blob jumper.
-
-## Reported range and reception
-
-This is the board's most-complained-about non-power characteristic. Three separate threads,
-spanning four years:
-
-| Report | Date | Comments | Evidence class |
-|---|---|---|---|
-| ["wifi is very weak"](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/123) | 2023-03-17 | 14 | firsthand ownership, no instrumentation |
-| ["My board doesn't connect to WiFi"](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/247) | 2024-05-11 | 19 | firsthand, mixed causes |
-| ["wifi reception"](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/340) | 2026-04-12 | 17 | firsthand |
-
-**No RSSI measurement, no anechoic data, and no comparison against a reference board exists in
-any of them.** Treat "the Wi-Fi is weak" as *repeatedly reported by owners*, not as measured.
-Confounders that appear in those threads and are worth eliminating first: 5 GHz-only SSIDs
-(the ESP32-S3 cannot see them — a firsthand
-[reminder from r/esp32, 2026-05-25](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/)),
-WPA3-only networks, and a metal shell or a battery sitting over the antenna.
-
-**Physical cause that is plausible and untested:** the antenna sits at one end of a board whose
-other 90 % is a bonded LCD with a metal frame and a shielding layer. That is a poor RF
-environment, and it is the structural difference between this board and a bare-module dev kit.
-
-## Coexistence
-
-Wi-Fi and BLE share the one radio; the ESP32-S3 time-slices them. Running both roughly halves
-each one's throughput and adds latency jitter — this is silicon behaviour, not board behaviour,
-and Espressif documents it.
-
-**ADC2 is unusable while Wi-Fi is active.** The battery sense on GPIO4 is on **ADC1**, so it is
-unaffected — but any additional analogue input you add must also be on ADC1
-(GPIO1–GPIO10) or it will fail as soon as Wi-Fi starts. See
-[`battery-voltage-measurement.md`](battery-voltage-measurement.md) §3.
-
-## Power
-
-Vendor figure for same-SoC boards in this family: *"(240MHz) WiFi On 90~230+ mA"*
-(`LilyGo-AMOLED-Series/README.MD` @ `6d1dc00`). That is a **different board**; quoted for
-order of magnitude. The peak matters for battery sizing — a 350 mAh cell cannot sustain 230 mA
-for long, and transmit peaks brown out marginal supplies, which is one plausible reading of
-[issue #143 "Unable to power board with wall plug, but computer USB-C works"](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/143).
-
-## Provisioning
-
-The factory firmware uses **ESP-Touch** (SmartConfig) — a phone app that pushes credentials
-over Wi-Fi. Two things about it recur:
-
-- It is called "ESP **Touch**", which people reliably confuse with the LCD touchscreen. That
-  confusion is the entire content of [issue #212](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212).
-- SmartConfig does not work on many modern routers and phones. For anything real, use
-  WiFiManager, ESPHome, or hardcoded credentials.
diff --git a/devices/lilygo/t-display-s3/gaps-and-conflicts.md b/devices/lilygo/t-display-s3/gaps-and-conflicts.md
deleted file mode 100644
index 90776c4..0000000
--- a/devices/lilygo/t-display-s3/gaps-and-conflicts.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# T-Display-S3 — gaps, conflicts and unresolved identities
-
-> Snapshot **2026-09-07**. Conflicts are recorded, not resolved by preference. Each entry says
-> what evidence would settle it.
-
-## Conflicts
-
-### G1 — The "touch" and "no-touch" factory images are byte-identical
-
-| | |
-|---|---|
-| Claim A | LilyGO ships `firmware/t-display-s3-touch-20230417_0x0.bin` and `firmware/t-display-s3-no-touch-20231013_0x0.bin` as distinct builds for distinct boards, dated six months apart |
-| Claim B | They are one file. SHA-256 `f288081645eecf7bf6a17fd7b5bc2e724121d00cdc2099b5a5ea7db5107eb9fa`, 1 601 328 B, identical app descriptors including build timestamp |
-| Evidence for B | **Measured locally 2026-09-07** (firsthand). Independently noticed by a user in [issue #212](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212), 2024-01-02, where it was never addressed |
-| Status | **Resolved in favour of B.** The filenames are wrong |
-| Consequence | Flashing "no-touch" to a non-touch board yields a UI expecting touch |
-
-### G2 — Charger part number vs shipping hardware
-
-| | |
-|---|---|
-| Claim A | `schematic/T_Display_S3.pdf` (title block 2024-04-29) shows `U6 = TP4065`, `PROG` resistor `R9 = 2K`, sheet note `R13  IBAT (mA) = 580` |
-| Claim B | A physical board carries a **5-lead TSOT-23 marked `65b311`**, and no SOP-8 is present — [issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230), 2024-03-02, firsthand PCB inspection with the package and marking quoted |
-| Claim C | LilyGO's README says "The default charging current is **500mA**", citing that same issue |
-| Notes | The issue author writes "TP4056" in prose while the schematic reads TP4065 — the two are different parts with similar programming equations. A 2 kΩ `PROG` resistor gives ≈ 580 mA on a TP4056 (I = 1200 V / R<sub>PROG</sub>), which matches the sheet note and **not** the 500 mA in the README |
-| Status | **Unresolved, three ways.** The fitted part, the actual charge current, and whether the documented resistor swap applies are all open |
-| What would settle it | A photograph of `U6` on a 2025-or-later board at readable magnification; or a measured charge current into a discharged cell; or a LilyGO statement |
-| Do not | swap the charge-programming resistor on the strength of the schematic |
-
-### G3 — Colour order: RGB or BGR?
-
-| | |
-|---|---|
-| Claim A | `Setup206_LilyGo_T_Display_S3.h` @ `ec889e7`: `#define TFT_RGB_ORDER TFT_RGB` (with the BGR line commented out) |
-| Claim B | ESPHome `mipi_spi` model `T-DISPLAY-S3`: `color_order=MODE_BGR` |
-| Both agree on | colour **inversion** on (`TFT_INVERSION_ON` / `invert_colors=True`) |
-| Status | **Unresolved.** Both libraries are in wide use and neither has a flood of "colours are wrong" reports, which suggests the two settings compensate for a difference elsewhere in each library's pipeline rather than describing the panel differently |
-| What would settle it | Display a pure-red bitmap on one board with each library and photograph the result |
-| Practical advice | If red and blue are swapped, flip this one setting; do not go looking for a hardware fault |
-
-### G4 — Pixel clock: 16 MHz or 10 MHz?
-
-`examples/factory/pin_config.h` @ `ec889e7` uses **16 MHz** with the comment *"Too low or too
-high pixel clock may cause screen mosaic"*. ESPHome uses **10 MHz**. Neither is authoritative
-for your board; the limit is set by the panel flex. **Not a defect** — recorded because people
-copy the 16 MHz figure and then see tearing.
-
-### G5 — Battery charge current: 500 mA or 580 mA?
-
-README says 500 mA; the schematic note says 580 mA. See G2. Unresolved.
-
-### G6 — Is GPIO16/17 pull-up fitment universal?
-
-LilyGO confirmed the resistors exist on a non-touch board ([issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313),
-with photographs). **Whether every production run fits them is not established.** Measure your
-board rather than assuming either way.
-
-## Gaps — things this pass did not establish
-
-| # | Gap | Why it is open | How to close it |
-|---|---|---|---|
-| K1 | **Schematic net connectivity was not traced.** Only designators, part strings and printed values were recovered from `T_Display_S3.pdf` | The PDF is an Altium export; the repo's [`tools/altium_pdf_netlist.py`](../../../tools/altium_pdf_netlist.py) needs `pdftotext -bbox` XML and **poppler was not installed on this host** | Install poppler-utils, run `pdftotext -bbox-layout` per page, then the existing tool. Everything else is already in place |
-| K2 | **The battery divider ratio is inferred**, from two `100K %1` resistors plus the vendor multiplying by 2 | see K1 | as K1, or measure |
-| K3 | **`Q4` (SI2307) gate control not traced** — so it is unknown whether the divider is disconnected in deep sleep, which matters for the sleep-current budget | see K1 | as K1 |
-| K4 | **No independent performance measurement** of this board was located, and none was produced | No hardware available; no published benchmark found in 40+ searched sources | Measure full-screen fill rate at 10/16/20 MHz and deep-sleep current with and without a battery |
-| K5 | **No product photography retained** | LilyGO's image rights were not established and no clearly licensed teardown was found | Ask LilyGO, or photograph a board |
-| K6 | **CircuitPython support unknown** — no board definition found, but absence was not proven across all forks | search depth limited to the Adafruit repository and the CircuitPython board list | Search `adafruit/circuitpython/ports/espressif/boards` exhaustively |
-| K7 | **The `AXPM65611` / `65b311` part is unidentified** | No datasheet found under either string; no manufacturer identifiable from primary evidence | See [`components/unidentified/lilygo-t-display-s3-family/axpm65611/`](../../../components/unidentified/lilygo-t-display-s3-family/axpm65611/README.md) |
-| K8 | **No dated marketplace/clone price observations** beyond LilyGO's own store | AliExpress and Amazon listings were not sampled systematically in this pass | Sample ≥10 listings with dates, sellers and shipping, per [`guides/markets/clones-and-variants.md`](../../../guides/markets/clones-and-variants.md) |
-
-## Negative results worth keeping
-
-- **There is no USB-UART bridge on this board.** Searched the schematic designator census for
-  CH340/CP210x/FTDI/CH343 — absent. The USB path is native ESP32-S3 only. Recorded because
-  "which driver do I install" is a recurring question with the answer *none*.
-- **There is no onboard microSD slot.** The `PIN_SD_*` defines in every `pin_config.h` describe
-  the separately sold TF Shield. LilyGO's README says so explicitly. Recorded because the
-  defines make it look otherwise.
-- **There is no onboard IMU, no audio codec, no RTC and no battery-protection IC.** A full
-  designator census of the single schematic sheet found `U1` (crystal), `U2` (ESP32-S3R8),
-  `U3` (W25Q128JV), `U4` (AW9364DNR), `U5` (USB-C), `U6` (charger), `U7` (LDO) — and no `U8`.
-  The gap in the sequence is itself the evidence that nothing else is fitted.
-- **Meshtastic does not support this board**, and cannot: no LoRa radio. Searched
-  `meshtastic/firmware` variants; no T-Display-S3 target exists.
-- **WLED does not support this board.** `wled/WLED` carries a `TTGO-T-Display` usermod for the
-  *ESP32* predecessor only; no S3 variant.
diff --git a/devices/lilygo/t-display-s3/market-and-pricing.md b/devices/lilygo/t-display-s3/market-and-pricing.md
deleted file mode 100644
index b247a2b..0000000
--- a/devices/lilygo/t-display-s3/market-and-pricing.md
+++ /dev/null
@@ -1,163 +0,0 @@
-# T-Display-S3 — pricing and availability
-
-> All observations **2026-09-07**, from LilyGO's own Shopify product feed
-> (`https://lilygo.cc/collections/all/products.json`), whose `updated_at` was the same date.
-> **Prices exclude shipping, VAT and duty.** Currency USD as listed by the store.
-
-## Launch
-
-| | |
-|---|---|
-| Store `published_at` | **2022-07-15** |
-| Repo created | 2022-06-13 |
-| Launch price | **not established.** The feed carries current prices only; no archived listing was retrieved |
-
-## Current — LilyGO official store, 2026-09-07
-
-| SKU | Configuration | USD | Stock |
-|---|---|---|---|
-| `H569` | bare, **non-soldered** header pins | **9.04** | in stock |
-| `H577` | bare, soldered pins | 9.54 | in stock |
-| `H587` | **Touch**, non-soldered | 12.61 | in stock |
-| `H589` | **Touch**, soldered | 13.02 | in stock |
-| `K204` / `K206` | with black / grey shell | 13.22 | in stock |
-| `K204-01` / `K206-01` | shell **+ 700 mAh battery** | 20.60 | **out of stock** |
-| `H656` | MIDI shield **only** (no board) | 15.47 | in stock |
-| `USH577` | soldered, **US warehouse** | 14.04 | out of stock |
-| `DEH577` | soldered, **DE warehouse** | 14.04 | out of stock |
-| `K204US` / `K204-DE` | black shell, US / DE warehouse | 17.72 | out of stock |
-
-A **second listing** exists under handle `t-display-s3-copy`, published 2026-07-27, offering
-`H569` at **USD 9.03** — one cent lower, same SKU. Almost certainly a duplicated product page
-rather than a different item; recorded because a price-comparison script will report it as a
-distinct product.
-
-### The regional-warehouse premium
-
-`H577` costs **9.54** from China and **14.04** from the US or German warehouse — a **47 %**
-markup for local stock, and **every** regional SKU was out of stock on the observation date.
-Local warehouses are not a reliable purchase path for this board.
-
-### Accessories
-
-| Item | USD | Note |
-|---|---|---|
-| T-Display TF Shield `H609` / `H610` | 2.51 / 2.38 | microSD; the only way to get a card slot |
-| T-Display-S3 Shell `L929` / `L930` | 5.02 | shell alone |
-| T-Display keyboard | 6.88 – 30.98 | separate product |
-
-## Family price context, same date
-
-| Board | From (USD) |
-|---|---|
-| **T-Display-S3** | **9.04** |
-| T-Display (ESP32 predecessor) | 8.04 |
-| T-Dongle S3 | 10.99 |
-| T-QT Pro | 9.05 |
-| T-Display S3 AMOLED (DS) 1.64″ | 22.99 |
-| T-Display S3 AMOLED 1.91″ | 26.44 |
-| T-Display S3 Long | 29.35 |
-| T-Display S3 AMOLED Plus | 32.68 |
-| T-Display AMOLED Lite 1.47″ | 35.66 |
-| T-Display S3 Pro | 37.99 (no camera) – 56.99 (OV5640) |
-| T4-S3 2.41″ AMOLED | 56.89 |
-
-**Adding an AMOLED panel roughly triples the price**, and adding touch to the base board costs
-**+USD 3.57** (`H569` → `H587`) — which is the cheapest capacitive touch on any ESP32-S3 board
-documented in this repository.
-
-## Marketplace and clones
-
-**Not sampled in this pass.** AliExpress, Amazon, Banggood and the used market were not
-surveyed, so no dated marketplace observation is offered — a range quoted without dates,
-sellers and shipping is worse than none. Recorded as gap
-[K8](gaps-and-conflicts.md).
-
-One dated third-party data point survives in the searched set, and is offered only as such:
-a coupon post on r/couponsjet, **2024-11-30**, advertising the **AMOLED** board at
-**USD 32.99** on Banggood. Evidence class: *promotional post, unverified, different board.*
-
-The genuine-vs-clone question, with a worked example, is in
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md#the-clone-question).
-Method: [`guides/markets/clones-and-variants.md`](../../../guides/markets/clones-and-variants.md).
-
-## Buying advice, dated 2026-09-07
-
-- **If you do not need touch, do not buy touch.** The non-touch board is USD 3.57 cheaper and
-  avoids the CST816S/CST328 driver-flag problem entirely.
-- **Buy non-soldered** (`H569`) unless you want the headers exactly as LilyGO fits them; 50 ¢
-  is not worth losing the option.
-- **Do not buy the regional-warehouse SKUs** at a 47 % premium; they were out of stock anyway.
-- **The shell-plus-battery bundle is the only sanctioned battery**, and it was out of stock.
-  Any cell you source yourself must be **protected** (no on-board protection) and should be
-  ≥ 600 mAh to keep the ~580 mA charge current below 1 C.
-- **If you want AMOLED, price it against the alternatives**: at USD 26–33 the 1.91″ AMOLED
-  boards compete with entirely different classes of board. See
-  [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md).
-
----
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Non-Soldered Pin [H569] | `H569` | **USD 9.04** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Touch Non-Soldered Pin [H587] | `H587` | **USD 12.61** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Touch Soldered [H589] | `H589` | **USD 13.02** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Soldered Pin [H577] | `H577` | **USD 9.54** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Grey Shell [K206] | `K206` | **USD 13.22** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Black Shell [K204] | `K204` | **USD 13.22** | ✅ yes |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Black Shell and built-in 700 mAh battery [K204-01] | `K204-01` | **USD 20.60** | ❌ no |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / With Grey Shell and built-in 700 mAh battery [K206-01] | `K206-01` | **USD 20.60** | ❌ no |
-| T-Display S3 | 2022-07-15 | China [For Worldwide] / Only MIDI Board [H656] | `H656` | **USD 15.47** | ✅ yes |
-| T-Display S3 | 2022-07-15 | Germany [ For Europe only] / With Black Shell [K204] | `K204-DE` | **USD 17.72** | ❌ no |
-| T-Display S3 | 2022-07-15 | United States [For US only] / Soldered Pin [H577] | `USH577` | **USD 14.04** | ❌ no |
-| T-Display S3 | 2022-07-15 | United States [For US only] / With Black Shell [K204] | `K204US` | **USD 17.72** | ❌ no |
-| T-Display S3 | 2022-07-15 | Germany [ For Europe only] / Soldered Pin [H577] | `DEH577` | **USD 14.04** | ❌ no |
-| T-Display S3 | 2026-07-27 | China [For Worldwide] / Non-Soldered Pin [H569] | `H569` | **USD 9.03** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 9.04, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display-s3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-⚠ **13 variants under one handle.** Bare non-soldered board USD 9.04 → shell + 700 mAh battery USD 20.60. **Do not quote a single price.** Note a second handle `t-display-s3-copy` (vendor field literally `1`, published 2026-07-27) duplicates the base SKU `H569` at USD 9.03 — a store artefact, not a product. **Region matters:** US/DE variants of the same SKU cost USD 14.04–17.72 vs USD 9.54 for the 'China [For Worldwide]' variant.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-display-s3/media/manifest.json b/devices/lilygo/t-display-s3/media/manifest.json
deleted file mode 100644
index f1ed948..0000000
--- a/devices/lilygo/t-display-s3/media/manifest.json
+++ /dev/null
@@ -1,116 +0,0 @@
-{
-  "schema": "hardware-doc/media-manifest/1",
-  "device": "devices/lilygo/t-display-s3",
-  "generated": "2026-09-07",
-  "status": "NO IMAGE RETAINED. Rights for LilyGO's product photography were not established, and no third-party teardown with clear licensing was located. This manifest records what exists, where, and what would have to be resolved before retaining any of it.",
-  "images": [
-    {
-      "id": "pinmap-tds3",
-      "description": "LilyGO's own annotated pin-map illustration of the T-Display-S3, front view with every header pin labelled",
-      "creator": "LILYGO (Shenzhen Xin Yuan Electronic Technology)",
-      "source_page": "https://github.com/Xinyuan-LilyGO/T-Display-S3",
-      "direct_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/image/T-DISPLAY-S3.jpg",
-      "published": "in-repo, commit-pinned",
-      "retrieved": null,
-      "applies_to": "T-Display-S3 non-touch",
-      "license": "unstated. The repository LICENSE is MIT, a software licence; whether it covers images is not stated by LilyGO",
-      "redistribution_status": "unknown",
-      "retained": false,
-      "caption": "Vendor pin-map. The most useful single image for this board; every header pin is labelled.",
-      "alt_text": "Front view of the LilyGO T-Display-S3 with each header pin labelled with its GPIO number.",
-      "modifications": "none",
-      "notes": "Cited by an owner in issue #313 to show that GPIO16/17 are physically exposed."
-    },
-    {
-      "id": "pinmap-tds3-touch",
-      "description": "Same, for the Touch variant",
-      "creator": "LILYGO",
-      "source_page": "https://github.com/Xinyuan-LilyGO/T-Display-S3",
-      "direct_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/image/T-DISPLAY-S3-TOUCH.png",
-      "published": "in-repo",
-      "retrieved": null,
-      "applies_to": "T-Display-S3 Touch",
-      "license": "unstated",
-      "redistribution_status": "unknown",
-      "retained": false,
-      "caption": "Vendor pin-map for the Touch variant.",
-      "alt_text": "Front view of the LilyGO T-Display-S3 Touch with header pins labelled.",
-      "modifications": "none",
-      "notes": null
-    },
-    {
-      "id": "wifi-antenna-switch",
-      "description": "Vendor illustration showing the 0-ohm resistor positions (red = on-board antenna, yellow = u.FL) for switching antenna mode",
-      "creator": "LILYGO",
-      "source_page": "https://github.com/Xinyuan-LilyGO/T-Display-S3",
-      "direct_url": "https://raw.githubusercontent.com/Xinyuan-LilyGO/T-Display-S3/ec889e789b3cf093412689a143f7f37b42b56af7/image/WiFi.png",
-      "published": "in-repo",
-      "retrieved": null,
-      "applies_to": "T-Display-S3, all",
-      "license": "unstated",
-      "redistribution_status": "unknown",
-      "retained": false,
-      "caption": "The only published guidance on moving the antenna-select resistor.",
-      "alt_text": "Close-up PCB photograph with the current resistor position circled in red and the external-antenna position highlighted in yellow.",
-      "modifications": "none",
-      "notes": "Referenced from features/wifi-and-ble.md."
-    },
-    {
-      "id": "pullup-resistors-1",
-      "description": "PCB back, showing the fitted pull-up resistors on GPIO16 and GPIO17 on a NON-TOUCH board",
-      "creator": "lewisxhe (LILYGO maintainer)",
-      "source_page": "https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313",
-      "direct_url": "https://github.com/user-attachments/assets/4ce1bb1d-94c6-401f-8b3d-9e4723f20d0a",
-      "published": "2025-07-29",
-      "retrieved": null,
-      "applies_to": "T-Display-S3 non-touch, unknown production run",
-      "license": "GitHub user content; no explicit licence",
-      "redistribution_status": "unknown",
-      "retained": false,
-      "caption": "LilyGO's own photograph identifying which resistors to remove to free GPIO16/17. The most useful teardown-adjacent image in existence for this board.",
-      "alt_text": "Photograph of the back of a T-Display-S3 with two small surface-mount resistors circled behind the display.",
-      "modifications": "none",
-      "notes": "Cited in pinouts-and-buses.md section 5 and in board-revision-drift.md R4. GitHub-hosted; durable while the issue exists."
-    },
-    {
-      "id": "pullup-resistors-2",
-      "description": "Second photograph from the same reply, wider view",
-      "creator": "lewisxhe (LILYGO maintainer)",
-      "source_page": "https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313",
-      "direct_url": "https://github.com/user-attachments/assets/a40027a6-cb87-4d59-8a93-0172870809be",
-      "published": "2025-07-29",
-      "retrieved": null,
-      "applies_to": "T-Display-S3 non-touch",
-      "license": "GitHub user content; no explicit licence",
-      "redistribution_status": "unknown",
-      "retained": false,
-      "caption": "Companion view to pullup-resistors-1.",
-      "alt_text": "Wider photograph of a T-Display-S3 board showing the area behind the display panel.",
-      "modifications": "none",
-      "notes": null
-    },
-    {
-      "id": "store-photography",
-      "description": "LilyGO's product photography (front, back, angled, with shell, with battery), several per SKU",
-      "creator": "LILYGO",
-      "source_page": "https://lilygo.cc/products/t-display-s3",
-      "direct_url": "see the images[] array in https://lilygo.cc/collections/all/products.json",
-      "published": "2022-07-15 onward",
-      "retrieved": null,
-      "applies_to": "all SKUs",
-      "license": "commercial product photography; all rights reserved unless stated",
-      "redistribution_status": "prohibited (assumed absent evidence)",
-      "retained": false,
-      "caption": "Store photography, useful for SKU identification (shell colours, header options).",
-      "alt_text": "LilyGO store photographs of the T-Display-S3 in its several sold configurations.",
-      "modifications": "none",
-      "notes": "The product feed carries full-resolution URLs and is the reliable way to enumerate them."
-    }
-  ],
-  "gaps": [
-    "No image of the board's back at a magnification that would resolve the U6 charger marking. That single photograph would settle conflict G2, which is the largest open question about this board.",
-    "No independent teardown with clear licensing was located.",
-    "No photograph of the two 0-ohm antenna-select resistor positions other than LilyGO's own annotated illustration.",
-    "No photograph distinguishing a CST816S board from a CST328 board externally (there may be no external difference)."
-  ]
-}
diff --git a/devices/lilygo/t-display-s3/performance.md b/devices/lilygo/t-display-s3/performance.md
deleted file mode 100644
index b8b6450..0000000
--- a/devices/lilygo/t-display-s3/performance.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# T-Display-S3 — performance
-
-> **This record contains no measurement of this board.** None was produced (no hardware) and
-> none was found (40+ sources searched). What follows is what is actually evidenced, and what
-> would have to be measured.
-
-## What is evidenced
-
-| Quantity | Value | Class | Source |
-|---|---|---|---|
-| Display pixel clock, vendor's choice | **16 MHz**, with the vendor's own caveat *"Too low or too high pixel clock may cause screen mosaic"* | official configuration | `examples/factory/pin_config.h` @ `ec889e7` |
-| Display pixel clock, ESPHome's choice | **10 MHz** | third-party configuration | `esphome/.../mipi_spi/models/lilygo.py`, `dev` |
-| CPU | 240 MHz, dual Xtensa LX7 | official spec | board manifest `f_cpu 240000000L` |
-| Flash | 16 MB, **QIO 80 MHz** per the board manifest; the shipped factory bootloaders say **DIO** | official / measured | manifest vs decoded images |
-| PSRAM | 8 MB octal (OPI) | official | `memory_type qio_opi` |
-| Usable RAM | 327 680 B per the board manifest | official | — |
-| Upload speed | 921 600 baud | official | — |
-
-## Derived, not measured
-
-An 8-bit 8080 bus at 16 MHz carries one byte per `WR` strobe → 2 strobes per RGB565 pixel →
-~8 M pixel/s. A 170 × 320 = 54 400-pixel full-screen redraw is therefore **~6.8 ms of bus
-time**. Real figures will be worse: driver overhead, DMA setup, and any per-line command
-framing. Treat this as a ceiling, not a benchmark. At ESPHome's 10 MHz it becomes ~10.9 ms.
-
-For comparison, the same panel on a 40 MHz single-lane SPI link would need ~21.8 ms of bus
-time. **That ~3× is the entire argument for the 13-wire bus**, and it is arithmetic, not a
-measurement.
-
-## Numbers from other boards, clearly labelled as such
-
-LilyGO publishes a current table for its **AMOLED** boards and none for this one:
-
-| Board | Active (240 MHz, Wi-Fi on) | Deep sleep | Wake source |
-|---|---|---|---|
-| T-Display AMOLED Lite | 90–230+ mA | ~1.1 mA | timer |
-| **T-Display-S3 AMOLED** | 90–230+ mA | ~230 µA | GPIO0 |
-| T4-S3 | 90–230+ mA | ~230 µA | GPIO0 |
-| T-Display-S3 AMOLED Plus | 90–230+ mA | ~230–700 µA dynamic | GPIO0 |
-
-— `LilyGo-AMOLED-Series/README.MD` @ `6d1dc00`, vendor table.
-
-**These are different boards.** Different display technology, different regulators (LDO vs
-buck), different charger, different sleep topology. The active figure is dominated by the SoC
-and radio and is therefore roughly transferable; **the deep-sleep figure is not**, because it
-is exactly the part that the board design determines. Anyone quoting "230 µA deep sleep for the
-T-Display-S3" is quoting the AMOLED board.
-
-## What to measure, and why each matters
-
-| Measurement | Method | Why it matters |
-|---|---|---|
-| Full-screen fill rate at 10/16/20 MHz | `Arduino_GFX` `PDQgraphicstest` (already in the repo) at each clock, timed | settles the mosaic threshold, which varies by production run |
-| Deep-sleep current, battery only, GPIO15 held low | µA-capable meter in series with the cell | LilyGO publishes nothing; the divider question ([K3](gaps-and-conflicts.md)) is worth ~21 µA |
-| Deep-sleep current **with and without** `gpio_hold_en()` on 16/17 | as above | quantifies the fitted-pull-up cost |
-| Wi-Fi TX peak | high-bandwidth current probe | explains brown-outs on marginal supplies ([issue #143](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/143)) |
-| RSSI vs a reference ESP32-S3 devkit at fixed distance | both boards, same AP, same orientation | the "weak Wi-Fi" complaint has **never** been measured by anyone in the searched set |
-| Actual charge current into a discharged cell | series meter | settles the 500-vs-580 mA conflict **and** identifies the fitted charger by behaviour |
-| Backlight luminance vs PWM duty | photometer | tests the AW9364 non-linearity claim |
-
-Each of these is a few minutes with a board and a meter, and each closes a question that
-currently has no answer anywhere.
-
-## LVGL
-
-LilyGO ships `examples/lv_demos` with an LVGL **8.x** config. `examples/Lvgl_benchmark`
-exists in the **1.64″ AMOLED** repo but **not** in the base-board repo, so there is no vendor
-LVGL benchmark for this board. One community report notes the `PCBClock` example failing to
-fit ([issue #256](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/256)) — an out-of-memory
-symptom that resolves to the OPI PSRAM setting rather than to performance.
diff --git a/devices/lilygo/t-display-s3/pinouts-and-buses.md b/devices/lilygo/t-display-s3/pinouts-and-buses.md
deleted file mode 100644
index b9252e3..0000000
--- a/devices/lilygo/t-display-s3/pinouts-and-buses.md
+++ /dev/null
@@ -1,308 +0,0 @@
-# LilyGO T-Display-S3 — pinouts and buses
-
-> Board: **T-Display-S3** (non-touch and Touch share this map). Research snapshot **2026-09-07**.
-> Every row is traceable to a file and commit. Where LilyGO's own sources disagree, both are shown.
-
-## Evidence used
-
-| Tag | Source | Retrieved |
-|---|---|---|
-| `PIN_CFG` | `Xinyuan-LilyGO/T-Display-S3` → `examples/factory/pin_config.h` @ **`ec889e789b3cf093412689a143f7f37b42b56af7`** (2 069 B, SHA-256 of the file body as fetched) | 2026-09-07 |
-| `README` | same repo, `README.md` § *Pinout* @ `ec889e7` | 2026-09-07 |
-| `IDF` | `Xinyuan-LilyGO/LilyGo-Display-IDF` → `main/product_pins.h`, block `#elif CONFIG_LILYGO_T_DISPLAY_S3` @ **`b1a1cc54994bf1b417e3bb30c437bbe1036bff7f`** | 2026-09-07 |
-| `SCH` | `schematic/T_Display_S3.pdf` @ `ec889e7`, title block **2024-04-29**, one sheet. Text recovered with a locally written extractor; **designator/part strings only** — net connectivity was *not* traced. See [§7](#7-what-was-not-established) | 2026-09-07 |
-| `TFT206` | `lib/TFT_eSPI/User_Setups/Setup206_LilyGo_T_Display_S3.h` @ `ec889e7` | 2026-09-07 |
-| `ESPH` | `esphome/esphome` → `esphome/components/mipi_spi/models/lilygo.py`, entry `T-DISPLAY-S3`, branch `dev` fetched 2026-09-07 | 2026-09-07 |
-
-`PIN_CFG` verbatim, the authoritative block:
-
-```c
-/* examples/factory/pin_config.h @ ec889e789b3cf093412689a143f7f37b42b56af7 */
-#define PIN_LCD_BL                   38
-
-#define PIN_LCD_D0                   39
-#define PIN_LCD_D1                   40
-#define PIN_LCD_D2                   41
-#define PIN_LCD_D3                   42
-#define PIN_LCD_D4                   45
-#define PIN_LCD_D5                   46
-#define PIN_LCD_D6                   47
-#define PIN_LCD_D7                   48
-
-#define PIN_POWER_ON                 15
-
-#define PIN_LCD_RES                  5
-#define PIN_LCD_CS                   6
-#define PIN_LCD_DC                   7
-#define PIN_LCD_WR                   8
-#define PIN_LCD_RD                   9
-
-#define PIN_BUTTON_1                 0
-#define PIN_BUTTON_2                 14
-#define PIN_BAT_VOLT                 4
-
-#define PIN_IIC_SCL                  17
-#define PIN_IIC_SDA                  18
-
-#define PIN_TOUCH_INT                16
-#define PIN_TOUCH_RES                21
-
-/* External expansion */
-#define PIN_SD_CMD                   13
-#define PIN_SD_CLK                   11
-#define PIN_SD_D0                    12
-```
-
-Nine `pin_config.h` copies exist across the repo's examples (`factory`, `tft`, `touch_test`,
-`GetBatteryVoltage`, `sd`, `lv_demos`, `nes`, `ota`, `Sleep`, `PCBClock`, `PokerS3`,
-`ImageScroll`, `TFT_Rainbow`). **All agree** on the pin numbers; they differ only in which
-subset they define and in unrelated Wi-Fi/LCD-clock constants. That agreement is itself
-evidence — a divergent copy would be the interesting case, and there is none.
-
----
-
-## 1. Master GPIO map
-
-| GPIO | Signal | Direction | Bus / role | Shared / strap | Source |
-|---|---|---|---|---|---|
-| 0 | `BUTTON_1` / **BOOT** | in, active-low | strap | **Strapping pin.** Held low at reset = download mode | `PIN_CFG`, `SCH` (`S2/S3/SW` = `SW-PB`) |
-| 1 | free | — | header | — | `README` (absent from pin map ⇒ unused) |
-| 2 | free | — | header | — | `README` |
-| 3 | free | — | header | JTAG-select strap on ESP32-S3 | `README` |
-| 4 | `BAT_VOLT` | in (ADC1_CH3) | ADC | **Conflict:** also the only battery sense. Cannot be reused | `PIN_CFG`, `SCH` (`R2`,`R4` = `100K %1`) |
-| 5 | `LCD_RES` | out | 8080 | — | `PIN_CFG`, `IDF`, `TFT206`, `ESPH` |
-| 6 | `LCD_CS` | out | 8080 | — | all |
-| 7 | `LCD_DC` | out | 8080 | — | all |
-| 8 | `LCD_WR` | out | 8080 | — | all |
-| 9 | `LCD_RD` | out | 8080 | ESPHome treats it as an *enable* pin, tied high | `PIN_CFG`; `ESPH` `enable_pin=[9, 15]` |
-| 10 | free | — | header | — | `README` |
-| 11 | `SD_CLK` | out | SDMMC (**shield only**) | free unless the TF Shield is fitted | `PIN_CFG`, `README` |
-| 12 | `SD_D0` | i/o | SDMMC (**shield only**) | as above | `PIN_CFG` |
-| 13 | `SD_CMD` | i/o | SDMMC (**shield only**) | as above | `PIN_CFG` |
-| 14 | `BUTTON_2` | in, active-low | — | the *other* user button; **not** RST | `PIN_CFG` |
-| 15 | **`POWER_ON`** | out | power gate | **Must be driven HIGH** or nothing works on battery — [§3](#3-the-gpio15-power-gate) | `PIN_CFG`, `README`, `IDF` |
-| 16 | `TOUCH_INT` | in | I²C IRQ | **Pulled up by a fitted resistor even on non-touch boards** — [§5](#5-gpio16--gpio17-are-not-free) | `PIN_CFG`, issue #313 |
-| 17 | `IIC_SCL` | out | I²C | 10 kΩ pull-up `RIIC` fitted | `PIN_CFG`, `SCH` (`RIIC 10K`) |
-| 18 | `IIC_SDA` | i/o | I²C | 10 kΩ pull-up `RIID` fitted | `PIN_CFG`, `SCH` (`RIID 10K`) |
-| 19 | USB D− | — | native USB | not a GPIO in practice | `SCH` (`ESP_USB_DM`) |
-| 20 | USB D+ | — | native USB | not a GPIO in practice | `SCH` (`ESP_USB_DP`) |
-| 21 | `TOUCH_RES` | out | touch reset | free on non-touch boards, but see §5 | `PIN_CFG` |
-| 26–32 | **unusable** | — | in-package OPI PSRAM | ESP32-S3R8 reserves them | ESP32-S3 datasheet |
-| 33–37 | **unusable** | — | in-package OPI PSRAM (`SPIIO4..7`, `SPIDQS`) | ESP32-S3R8 reserves them | `SCH` (`SHICLK 33`, `SHICS0 32`, `SHIPD 30`, `SHIWP 31`) |
-| 38 | `LCD_BL` | out | backlight enable → `U4 AW9364DNR` | **not a raw LED PWM** — [§4](#4-the-backlight-is-a-one-wire-boost-driver-not-a-pwm-pin) | `PIN_CFG`, `SCH` |
-| 39 | `LCD_D0` | out | 8080 data | — | `PIN_CFG` |
-| 40 | `LCD_D1` | out | 8080 data | — | `PIN_CFG` |
-| 41 | `LCD_D2` | out | 8080 data | — | `PIN_CFG` |
-| 42 | `LCD_D3` | out | 8080 data | — | `PIN_CFG` |
-| 43 | `U0TXD` | out | UART0 | **Claimed by UART0 in Arduino even with CDC on** — [§6](#6-gpio43--gpio44-are-not-usable-as-gpio-under-arduino) | `SCH`, community |
-| 44 | `U0RXD` | in | UART0 | as above | `SCH`, community |
-| 45 | `LCD_D4` | out | 8080 data | **Strapping pin** (`VDD_SPI` voltage select) | `PIN_CFG` |
-| 46 | `LCD_D5` | out | 8080 data | **Strapping pin** | `PIN_CFG` |
-| 47 | `LCD_D6` | out | 8080 data | — | `PIN_CFG` |
-| 48 | `LCD_D7` | out | 8080 data | — | `PIN_CFG` |
-
-**Note on GPIO45/46.** Both are ESP32-S3 strapping pins *and* LCD data lines. They are sampled
-only at reset, and the LCD driver only drives them afterwards, so there is no conflict in
-normal operation — but if you hang anything on the LCD data bus (you should not) you can
-change the boot behaviour. This is a board-level constraint, not a silicon defect.
-
----
-
-## 2. Buses
-
-### 2.1 The display: 8-bit Intel-8080 parallel
-
-| Property | Value | Source |
-|---|---|---|
-| Controller | **Sitronix ST7789V** → [component record](../../../components/sitronix/st7789v/README.md) | `datasheet/ST7789V_SPEC_V1.4.pdf` shipped in the repo |
-| Panel | 1.9″ IPS, **170 × 320** visible | `README` |
-| Controller window offset | **`offset_width = 35`** — the ST7789V is a 240-wide part; the 170-px panel sits at column 35 | `ESPH`; corroborated by `TFT206` `#define TFT_WIDTH 170` + LilyGO's `Arduino_GFX` args |
-| Bus | 8-bit parallel, `WR` strobed, `RD` unused in practice | `PIN_CFG`, `TFT206` `#define TFT_PARALLEL_8_BIT` |
-| Pixel clock used by LilyGO | **16 MHz** — `#define EXAMPLE_LCD_PIXEL_CLOCK_HZ (16 * 1000 * 1000)` with the in-file comment *"Too low or too high pixel clock may cause screen mosaic"* | `PIN_CFG` |
-| Pixel clock used by ESPHome | **10 MHz** (`data_rate="10MHz"`) | `ESPH` |
-| Colour order | **Conflict.** `TFT_eSPI` setup says **RGB**; ESPHome says **BGR**. Both apply colour inversion | `TFT206` `#define TFT_RGB_ORDER TFT_RGB` vs `ESPH` `color_order=MODE_BGR` — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) G3 |
-| Colour inversion | **on** in both | `TFT206` `#define TFT_INVERSION_ON`; `ESPH` `invert_colors=True` |
-| Init sequence | `INIT_SEQUENCE_3` — TFT_eSPI's alternate ST7789 init, with LilyGO's comment *"Using this initialisation sequence improves the display image"* | `TFT206` |
-
-`TFT206` **verbatim and complete** — the file you must select by hand in
-`TFT_eSPI/User_Setup_Select.h`:
-
-```c
-// ST7789 using 8-bit Parallel
-// lib/TFT_eSPI/User_Setups/Setup206_LilyGo_T_Display_S3.h @ ec889e7
-
-#define USER_SETUP_ID 206
-
-#define USE_HSPI_PORT
-#define ST7789_DRIVER
-#define INIT_SEQUENCE_3 // Using this initialisation sequence improves the display image
-
-#define CGRAM_OFFSET
-#define TFT_RGB_ORDER TFT_RGB  // Colour order Red-Green-Blue
-//#define TFT_RGB_ORDER TFT_BGR // Colour order Blue-Green-Red
-
-#define TFT_INVERSION_ON
-// #define TFT_INVERSION_OFF
-
-#define TFT_PARALLEL_8_BIT
-
-#define TFT_WIDTH 170
-#define TFT_HEIGHT 320
-
-#define TFT_CS  6
-#define TFT_DC  7
-#define TFT_RST 5
-
-#define TFT_WR 8
-#define TFT_RD 9
-
-#define TFT_D0 39
-#define TFT_D1 40
-#define TFT_D2 41
-#define TFT_D3 42
-#define TFT_D4 45
-#define TFT_D5 46
-#define TFT_D6 47
-#define TFT_D7 48
-
-#define TFT_BL 38
-#define TFT_BACKLIGHT_ON HIGH
-
-#define LOAD_GLCD
-#define LOAD_FONT2
-#define LOAD_FONT4
-#define LOAD_FONT6
-#define LOAD_FONT7
-#define LOAD_FONT8
-#define LOAD_GFXFF
-
-#define SMOOTH_FONT
-```
-
-Two things in that file are worth reading twice. **`CGRAM_OFFSET`** is what makes TFT_eSPI
-apply the 35-column offset into the ST7789V's 240-wide GRAM — remove it and the image shifts.
-**`USE_HSPI_PORT`** is vestigial for a parallel setup and does nothing here; it is left over
-from TFT_eSPI's SPI setups and is not a mistake worth "fixing".
-
-*(Reproduced from the retained copy at
-[`../t-display-s3-shared/artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h`](../t-display-s3-shared/artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h),
-SHA-256 `809949416716286a5b2db0821608251a1d69463ceea5721ccc5598a7fd841a5c`, 906 B.)*
-
-### 2.2 I²C
-
-| Property | Value |
-|---|---|
-| `SCL` / `SDA` | GPIO17 / GPIO18 |
-| Pull-ups | **fitted on-board**, `RIIC` and `RIID` = 10 kΩ each (`SCH`) |
-| Devices on a **Touch** board | touch controller only — **CST816S** at `0x15` (early boards) or **CST328** at `0x1A` (later). Both datasheets ship in the repo, which is itself the revision evidence |
-| Devices on a non-touch board | **none** — the bus is free, but GPIO16 still carries a pull-up |
-| Also on this bus | the 4-pin `SH1.0` "Qwiic-ish" connector, which is **not** Qwiic-pinout-compatible — see [issue #181](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/181) |
-
-### 2.3 SDMMC — shield only
-
-`PIN_SD_CMD 13 / PIN_SD_CLK 11 / PIN_SD_D0 12` describe the **T-Display TF Shield**
-(store SKU `H609`/`H610`, USD 2.38–2.51 as of 2026-09-07), a separate PCB. The README states
-plainly:
-
-> "SD card pins (SD CMD/CLK/D0) are only available on boards with the SD Shield add-on. The
-> standard T-Display-S3 board does not have an onboard SD card slot."
-
-1-bit SDMMC. Do not expect 4-bit.
-
-### 2.4 USB
-
-Native ESP32-S3 USB on GPIO19/20 straight to the Type-C receptacle (`U5`, a 16-pin
-`TYPEY-C` part in `SCH`). **There is no USB-UART bridge on this board** — no CH340, no CP210x.
-Consequences in [`features/usb.md`](features/usb.md).
-
-### 2.5 UART0
-
-GPIO43 (TX) / GPIO44 (RX), brought out to the header. This is where `Serial` goes when
-`USB CDC On Boot` is disabled.
-
----
-
-## 3. The GPIO15 power gate
-
-> "**Note:** GPIO15 is the peripheral power control pin. You must set it HIGH before using the
-> board, otherwise the LCD and other peripherals will not work."
-> — `README` @ `ec889e7`
-
-```cpp
-void setup() {
-    pinMode(15, OUTPUT);
-    digitalWrite(15, HIGH);   // V3V rail on — LCD, headers' 3V pin
-    pinMode(38, OUTPUT);
-    digitalWrite(38, HIGH);   // backlight on
-}
-```
-
-`SCH` shows GPIO15 as net `PWR_EN`, gating a P-channel MOSFET (`Q2`/`Q3` = `SI2301`) that
-feeds the `V3V` rail. The board's **green LED8** is on that rail, which gives you a free
-indicator: *green LED off while on battery = you forgot GPIO15*.
-
-When USB is connected the LDO output is present regardless, which is exactly why this bug
-only appears on battery — the single most-reported problem with this board. The vendor FAQ
-entry, [issue #79](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/79) and dozens of
-duplicates all trace to it.
-
-## 4. The backlight is a one-wire boost driver, not a PWM pin
-
-`SCH` shows `U4 = AW9364DNR` with `LEDK1..LEDK4` — an **Awinic AW9364** LED backlight boost
-driver → [component record](../../../components/awinic/aw9364/README.md). GPIO38 is its
-enable/one-wire control input, not a current sink.
-
-Practical effect: ordinary `ledcWrite()` PWM on GPIO38 *works* for coarse dimming, because the
-driver's output follows the enable duty cycle, but the AW9364 also implements a **one-wire
-pulse-count brightness protocol** (count rising edges within the timeout window to select one
-of 16 levels). LilyGO's own `Dimming` notes and community code use the crude PWM route. Do not
-assume linear brightness. See [`features/display.md`](features/display.md).
-
-## 5. GPIO16 / GPIO17 are not free
-
-From [issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313) (2025-07-28),
-answered by LilyGO maintainer `lewisxhe` with two PCB photographs:
-
-> "Pull-up resistors are already added to the 16 and 17 boards, so when you set it to floating,
-> it's pulled high by default. … If you must use these two GPIOs, you can remove these two
-> resistors. The resistors are located on the back of the screen, please remove them carefully."
-
-Reporter's firsthand symptom: an LED on GPIO16 or GPIO17 glows faintly with no code running,
-and glows again the moment the chip enters deep sleep (when the driver stops holding the pin
-low). **This applies to the non-touch board too** — the reporter confirmed they had the
-non-touch version.
-
-Evidence class: *vendor confirmation of a firsthand user report, with photographs.*
-
-## 6. GPIO43 / GPIO44 are not usable as GPIO under Arduino
-
-Firsthand, and reproduced by a second person in the same thread:
-
-> "**GPIO 43 and 44 on ESP32-S3** are blocked by UART0 in Arduino IDE even when using Hardware
-> CDC — can't be used for OneWire or digital input"
-> — u/Alarming_Breadfruit5, [r/esp32, 2026-05-25](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/)
->
-> "OKAY! I just tried it and it does not work on 43 or 44! TIL"
-> — u/MrBoomer1951, same thread, 2026-05-26, after initially disputing it
-
-> "The UART0 pins can be used if you disabled it in sdkconfig (esp-idf). Harder to do in
-> Arduino." — u/Extreme_Turnover_838, same thread
-
-Evidence class: **firsthand measurement, independently reproduced, with a stated workaround
-that was not itself tested here.** Corroborates the earlier
-[issue #117](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/117) (DS18B20 on GPIO43).
-
-## 7. What was *not* established
-
-Stated plainly so the next reader does not assume more rigour than exists.
-
-- **Net connectivity was not traced from the schematic.** The PDF is an Altium export whose
-  text layer yields designators, part strings and pin markers but not wires. What is asserted
-  above from `SCH` is *the existence and part number of a designator*, plus the value printed
-  beside it. The repo's [`tools/altium_pdf_netlist.py`](../../../tools/altium_pdf_netlist.py)
-  can close this gap but needs `pdftotext -bbox` XML, and poppler was not available on this
-  host. Recorded in [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-- **The ADC divider ratio is inferred**, not traced: `R2` and `R4` are both `100K %1` and the
-  vendor's own example multiplies the reading by 2. That is consistent, not proven.
-- **No hardware was available.** Nothing in this record is `executed-success` against a
-  physical board. Every command in [`commands.md`](commands.md) is labelled accordingly.
diff --git a/devices/lilygo/t-display-s3/product-history-and-family.md b/devices/lilygo/t-display-s3/product-history-and-family.md
deleted file mode 100644
index 84afcaa..0000000
--- a/devices/lilygo/t-display-s3/product-history-and-family.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# T-Display-S3 — product history, family and culture
-
-## Dated timeline
-
-| Date | Event | Evidence |
-|---|---|---|
-| ~2019 | **TTGO T-Display** (ESP32, 1.14″ 135×240 ST7789 on SPI) establishes the format: a cheap ESP32 with a bonded colour strip. It becomes LilyGO's most-starred repo ever — **1 192★** | `Xinyuan-LilyGO/TTGO-T-Display` |
-| 2021-09-08 | `LilyGO-T-DisplayGD32` — the same format on a GD32. A dead end (41★) | org listing |
-| 2022-06-13 | `Xinyuan-LilyGO/T-Display-S3` repository created | GitHub API |
-| **2022-07-15** | **T-Display-S3 listed for sale** | store `published_at` |
-| 2022-07-18 | T-Dongle (ESP32-S2) listed | store |
-| 2022-09-21 | T-QT Pro listed | store |
-| 2022-09-23 | `LilyGo-T-Display-S2` last pushed — the S2 line ends | org listing |
-| 2022-10-06 | Tasmota support requested ([issue #18](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/18)); working by 2023-01 | issue |
-| 2022-10-20 | T-Dongle S3 listed | store |
-| 2022-11-07 | [Issue #42](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/42): `VBUS` not on the header. Never fixed | issue |
-| 2022-11-12 | T-Display AMOLED Lite listed — first AMOLED in the line | store |
-| 2023-01-03 | [Issue #79](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/79): the community setup guide that documents the GPIO15 trap LilyGO's own docs did not | issue |
-| 2023-02-09 | T-Display TF Shield listed | store |
-| 2023-02-17 | `T-Display-S3-AMOLED` repo created | GitHub API |
-| 2023-03-24 | T-Display-S3 Shell listed | store |
-| **2023-04-14** | **T-Display-S3 AMOLED (1.91″) listed** | store |
-| 2023-05-20/31 | The board goes visibly mainstream on Reddit: r/arduino "This is T-display S3…" (583↑) and "Finally AMOLED display on the development board" (987↑ on r/arduino, 400↑ on r/esp32) | Reddit |
-| 2023-08-09 | `LilyGo-AMOLED-Series` created — one library for the whole AMOLED line | GitHub API |
-| 2023-08-17 | `T-Display-S3-Pro` repo created | GitHub API |
-| 2023-08-22 | `T-Display-S3-Long` repo created | GitHub API |
-| 2023-09-07 | **T-Display-S3 Pro listed** | store |
-| 2023-10-27 | **T-Display-S3 Long listed** | store |
-| 2023-11-03 | **T4-S3 (2.41″ AMOLED) listed** | store |
-| 2024-03-02 | [Issue #230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230): an owner traces the PCB and finds the charger is not the part in the schematic | issue |
-| **2024-04-29** | Title-block date on the only published base-board schematic | `T_Display_S3.pdf` |
-| 2024-07-18 | **T-Display S3 AMOLED (DS)** listed — one page, four round/small panels | store |
-| 2024-08-02 | LilyGO adds the README note that **TFT_eSPI does not work above Arduino core 2.0.14** | README |
-| 2024-08-09 | `T-Display-S3-AMOLED` repo's **last push** — superseded by `LilyGo-AMOLED-Series` | GitHub API |
-| 2024-10-31 | **T-Display-S3 AMOLED Plus** listed — BQ25896, RTC, microSD | store |
-| 2025-01-09 | Newest base-board factory image (`lvgl-demo`), still built on Arduino core 2.0.14 | app descriptor |
-| 2025-07-28 | [Issue #313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313): LilyGO confirms the GPIO16/17 pull-ups with PCB photos | issue |
-| 2025-11-28 | "T-Display S3 Pro External" listed | store |
-| 2026-01-28 | T-Dongle C5 listed — the ESP32-C5 era begins | store |
-| 2026-07-03 | **T-Display C5** listed (ESP32-C5, ST7789 1.9″ touch, **AXP2602** PMU, CST816S) — the direct successor concept | store + repo description |
-| 2026-07-27 | Duplicate `t-display-s3-copy` store listing appears | store |
-| 2026-08-11 | **T-Display SF32** listed (SiFli SF32) | store |
-| 2026-08-20 | T-Display K230 Kit listed | store |
-| 2026-08-31 | Last push to `Xinyuan-LilyGO/T-Display-S3` — **still actively maintained after four years** | GitHub API |
-| 2026-09-07 | This snapshot. Board in stock at USD 9.04 | store |
-
-## Lineage
-
-```
-TTGO T-Display (ESP32, 1.14" SPI, ~2019, 1192*)
-   │
-   ├─ T-Display-GD32 (2021)            — dead end
-   ├─ T-Display-S2   (→2022)           — dead end
-   ├─ T-Display-RP2040 (→2023)         — dead end
-   │
-   └─ T-DISPLAY-S3 (ESP32-S3, 1.9" 8080 parallel, 2022-07, 1169*)   ← this board
-        ├─ T-Display-S3 Touch                    (same PCB)
-        ├─ T-Display-S3 AMOLED 1.91"  (2023-04)  ├ QSPI AMOLED branch
-        │    └─ AMOLED Plus           (2024-10)  │  + BQ25896, RTC, microSD
-        ├─ T-Display-S3 AMOLED DS 1.43/1.64/1.75 (2024-07)
-        ├─ T4-S3 2.41" AMOLED         (2023-11)
-        ├─ T-Display AMOLED Lite 1.47"(2022-11)  — actually predates the AMOLED 1.91"
-        ├─ T-Display-S3 Long 3.4"     (2023-10)  — AXS15231B bar display
-        └─ T-Display-S3 Pro 2.33"     (2023-09)  — SPI ST7796S, camera, 3 buttons
-                                                   └─ Pro MVSRBoard / MVSRLora backplates
-
-        successors reusing the "T-Display-" prefix on other silicon:
-        T-Display-C5 (ESP32-C5, 2026-07) · T-Display-P4 (ESP32-P4, 2025-12)
-        T-Display-K230 (Kendryte, 2025-03) · T-Display-SF32 (SiFli, 2026-08)
-        T-Display-CM0 (2026-09)
-```
-
-**The AMOLED Lite predates the AMOLED 1.91″ by five months** (2022-11 vs 2023-04), despite the
-"Lite" name implying it is a cut-down later model. It is not — it is the first AMOLED board,
-built around a different controller (SH8501B behind a level shifter) and a different PMU
-(AXP2101), and it is the *odd one out* rather than a simplification.
-
-## Cousins that share the name but not the design
-
-`T-Deck`, `T-Deck-Pro`, `T-Deck-MAX`, `T-Panel`, `T-Encoder-Pro`, `T-Circle-S3`,
-`T-Keyboard-S3`, `T-Display-Bar`, `T-Touchbar-AMOLED`, `T-FPGA`. All ESP32-S3, all separate
-PCBs. `T-Display-Bar` and `T-Touchbar-AMOLED` are particularly easy to confuse with the
-T-Display-S3 Long; they are different boards with different repos.
-
-## Culture
-
-The most striking thing about this board's community is that **the best documentation is not
-LilyGO's**. `teastainGit/LilyGO-T-display-S3-setup-and-examples` was written by an owner in
-January 2023 because the vendor documentation omitted the GPIO15 requirement, and it is linked
-from dozens of issue threads. LilyGO's own maintainer endorsed it in-thread on 2023-03-13:
-*"Thank you for bringing more clear and concise examples."* Three years later the vendor README
-has absorbed the GPIO15 note — but the third-party guide is still the one people are pointed
-at.
-
-The second pattern is **vendor responsiveness without vendor process**. `lewisxhe` answers
-issues quickly, accurately, and often with photographs of the PCB — the GPIO16/17 pull-up
-answer is a good example. What does not happen is any of that reaching the documentation, a
-revision number, or a changelog. The knowledge lives in closed GitHub issues.
diff --git a/devices/lilygo/t-display-s3/projects-and-community.md b/devices/lilygo/t-display-s3/projects-and-community.md
deleted file mode 100644
index c8bf4fa..0000000
--- a/devices/lilygo/t-display-s3/projects-and-community.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# T-Display-S3 — software, firmware and projects
-
-> Family-level software survey lives here because the base board has the widest support.
-> Per-variant status is in the "Which variants" column. Snapshot **2026-09-07**.
-
-## 1. Framework and firmware support matrix
-
-| Project | Supports | Which variants | Build | Status / evidence |
-|---|---|---|---|---|
-| **ESPHome** | **Yes, first-class** | `T-DISPLAY-S3`, `T-DISPLAY-S3-PRO`, `T-DISPLAY-S3-AMOLED`, `T-DISPLAY-S3-AMOLED-PLUS`, `T4-S3`, plus the ESP32 `T-DISPLAY` | YAML: `esp32: board: lilygo-t-display-s3` + `display: platform: mipi_spi, model: T-DISPLAY-S3` | **Confirmed in source.** `esphome/components/mipi_spi/models/lilygo.py` and `amoled.py`, `dev` branch fetched 2026-09-07. Board id `lilygo-t-display-s3` is in `esp32/boards.py`. Licence **MIT + GPLv3** (ESPHome dual) |
-| **Tasmota** | **Yes, via runtime template** | base board only | Flash `Tasmota32-S3 (QIO Flash/OPI PSRAM)` with the web installer, then auto-configure with the **"Lilygo S3 Display"** template | **Firsthand user reports**, [issue #18](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/18). A Tasmota maintainer (`Jason2866`) participated. Reported working state: `Display Model 17, 320×170`. **You must run `displaydimmer 100`** or the screen is nearly black — the single most useful line in that thread. Licence **GPLv3** |
-| **Meshtastic** | **No, and cannot** | — | — | **Negative result.** No LoRa radio on any T-Display-S3 variant. Searched `org:meshtastic tdisplay` (247 hits) — no variant exists. The LoRa members of the wider LilyGO catalogue (T-Beam, T-Deck, T3-S3, **T-Display-S3 Pro LR1121**) are separate products |
-| **WLED** | **No** | — | — | **Negative result.** `wled/WLED` carries `usermods/TTGO-T-Display/` for the **ESP32** predecessor only. No S3 board file, no usermod |
-| **MicroPython** | **Yes** | base board; others vary | `russhughes/st7789s3_mpy` — a C ST7789 driver with an 8-bit-parallel backend, with `tft_config.py` for this board. Also `Xinyuan-LilyGO/lilygo-micropython` and the newer `Xinyuan-LilyGO/T-Display-S3-MicroPython` (`boards/lilygo-t-displays3.json`, pushed 2026-09-04) | Linked from LilyGO's own README §6. **GPIO15 must still be driven in Python** — a MicroPython user's confusion about exactly this is in [issue #79](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/79), 2024-04-23 |
-| **CircuitPython** | **Unknown** | — | — | No board definition located. **Absence not proven** — [K6](gaps-and-conflicts.md) |
-| **LVGL** | **Yes, 8.x** | all | `examples/lv_demos` @ `ec889e7`; `lv_conf.h` is an LVGL 8 config | 9.x needs porting. The AMOLED library ships an `lv_conf.h.v9` you rename — see [`../t-display-s3-amoled/README.md`](../t-display-s3-amoled/README.md) |
-| **ESP-IDF** | **Yes** | nine boards | `Xinyuan-LilyGO/LilyGo-Display-IDF` @ `b1a1cc5`, MIT. `menuconfig` selects the board via `CONFIG_LILYGO_*` | The `product_pins.h` in it is the best cross-variant pin source in the family |
-| **Arduino** | **Yes, pinned to core 2.0.14** | all | see [`development.md`](development.md) | Vendor-pinned; TFT_eSPI documented broken above 2.0.14 |
-| **Rust (`esp-hal`)** | SoC yes, board no | — | — | Asked in [issue #160](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/160). No board-support crate found |
-
-### ESPHome, in detail
-
-The `mipi_spi` model is worth reading because it encodes board knowledge you would otherwise
-have to discover:
-
-```python
-ST7789V.extend("T-DISPLAY-S3",
-    height=320, width=170, offset_width=35,
-    color_order=MODE_BGR, invert_colors=True, draw_rounding=1,
-    dc_pin=7, cs_pin=6, reset_pin=5,
-    enable_pin=[9, 15],          # LCD_RD *and* the GPIO15 power gate
-    data_rate="10MHz", bus_mode=TYPE_OCTAL,
-    requires={"psram"})
-```
-
-`enable_pin=[9, 15]` is ESPHome doing the GPIO15 dance for you. `requires={"psram"}` makes the
-OPI-PSRAM requirement a build error rather than a runtime mystery. This is why ESPHome is the
-lowest-friction route onto this board for anyone who does not need custom C++.
-
-One caution: an ESPHome regression report exists in this repo's tracker
-([issue #314](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/314), 2025-08-08,
-`Setup Failed: ESP_ERR_NOT_SUPPORTED` after upgrading to 2025.7.5) — but it turned out to be a
-**T-Camera S3**, not a T-Display-S3, and the cause was an `esp32_camera` API change requiring an
-I²C bus id instead of pins. Recorded so the next reader does not mis-attribute it.
-
-## 2. Notable community projects
-
-Evidence class in the last column: **DP** = demonstrable project (code or photos published),
-**FO** = firsthand ownership report, **H** = hearsay.
-
-| Project | What | Date | Where | Class |
-|---|---|---|---|---|
-| `teastainGit/LilyGO-T-display-S3-setup-and-examples` | The de-facto setup guide. Written because the vendor docs omitted GPIO15; **endorsed by LilyGO's maintainer in-thread** (2023-03-13) | 2023-01 → | [repo](https://github.com/teastainGit/LilyGO-T-display-S3-setup-and-examples) | DP |
-| **NerdMiner V2** | Lottery Bitcoin miner; the T-Display-S3 is one of its headline targets | — | referenced in [issue #212](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212) by an owner who had it running when nothing else worked | FO |
-| **ESP32 Internet Weather Station** | Full LVGL weather UI, code published | 2024-08-16 | [r/esp32, 1312↑, 68 comments](https://old.reddit.com/r/esp32/comments/1ethutq/i_made_another_esp32_internet_weather_station_i/) | DP |
-| **DIY auto gauge UI (LVGL)** | Automotive gauge cluster | 2025-03-11 | [r/esp32, 840↑](https://old.reddit.com/r/esp32/comments/1j8zvbc/diy_auto_gauge_ui_using_lvgl_on_lilygo_tdisplay_s3/) | DP |
-| **Weather Micro Station** | Compact weather display | 2025-11-07 | [r/esp32, 105↑](https://old.reddit.com/r/esp32/comments/1oqx825/weather_micro_station_for_tdisplay_s3/) | DP |
-| **Claude usage meter** | API-quota display; a 2026 genre | 2026-07-05 | [r/esp32](https://old.reddit.com/r/esp32/comments/1uo0m7i/claude_usage_meter_on_a_lilygo_tdisplay_s3/) | DP |
-| **DS18B20 + PIR clock** | Notable for its **negative results**, not its output — see [`community.md`](community.md) | 2026-05-25 | [r/esp32](https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/) | FO + measurement |
-| **MIDI ecosystem** (`@sauloverissimo`) | Eight examples upstreamed **into the vendor repo**: BLE MIDI sender/receiver, USB MIDI piano visualiser, chord detection, event-queue debugger, BLE→USB MIDI bridge, music-theory explorer | 2025 | `examples/T-Display-S3-*` @ `ec889e7` | DP |
-| **`@VolosR` PCBClock / PokerS3** | TFT_eSPI showcase sketches, also upstreamed | — | `examples/PCBClock`, `examples/PokerS3` | DP |
-| **`@Rudi Ackermann` ImageScroll** | Smooth image scrolling with world time zones | — | `examples/ImageScroll` | DP |
-| **NES emulator** | `arduino-nofrendo` vendored in the repo, playable | — | `examples/nes` | DP |
-| **Bruce firmware** | Pentest/RF multi-tool; r/brucefw discusses the **AMOLED** variant | 2026-04-12 | [r/brucefw](https://old.reddit.com/r/brucefw/comments/1sjplql/lilygo_tdisplay_s3_amoled/) | H (for the base board) |
-| **Battery backpack for the LilyGO shell** | Printable, referenced with a working cell part number | 2026-08 | [printables.com/model/1065538](https://www.printables.com/model/1065538-lilygo-t-display-s3-shell-battery-backpack) | DP |
-
-**On prevalence:** the Reddit sample above is **27 family-relevant posts out of four
-`search.json` queries at `t=all`**, not a census. It establishes that these projects exist and
-were built; it does not establish how common any use is.
-
-## 3. Vendor-shipped examples
-
-Twenty-nine directories under `examples/` @ `ec889e7`. Catalogued with selection decisions in
-[`examples/catalog.json`](examples/catalog.json); the recommended subset is in
-[`examples/best.md`](examples/best.md).
-
-## 4. Where to ask
-
-| Venue | Useful for | Note |
-|---|---|---|
-| [`Xinyuan-LilyGO/T-Display-S3` issues](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues) | **the best resource.** 318 issues, nearly all closed, maintainer-answered | A bot closes issues after 30 days stale + 14 days. Answers survive; threads die |
-| r/esp32 | project help, library problems | highest signal of the subreddits |
-| r/LilyGO | vendor-specific | small, low traffic |
-| r/Esphome | ESPHome YAML | active; the AMOLED board is well liked there |
-| Tasmota Discord | Tasmota | issue #18 was explicitly redirected there |
diff --git a/devices/lilygo/t-display-s3/research-log.md b/devices/lilygo/t-display-s3/research-log.md
deleted file mode 100644
index ee39c12..0000000
--- a/devices/lilygo/t-display-s3/research-log.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# T-Display-S3 — research log
-
-Snapshot pass, **2026-09-07**. Broad-coverage, reproducible; **not** a claim that no other
-source exists.
-
-## Date discrepancy — recorded, not silently resolved
-
-The task brief stated "today is 2026-09-04". The host clock reported **2026-09-07 10:23 UTC**,
-and LilyGO's Shopify feed independently returned `updated_at: 2026-09-07` on every product.
-Two independent sources beat one assertion, so **every retrieval date in this tree is
-2026-09-07**. If the brief's date is the correct one, subtract three days uniformly; nothing
-here depends on the difference.
-
-## Search ledger
-
-| Service | Query / method | Depth | Date | Outcome |
-|---|---|---|---|---|
-| GitHub API | `orgs/Xinyuan-LilyGO/repos`, 3 pages ×100, sorted by update | all 254 repos | 09-07 | **the family enumeration.** 60+ display-related repos identified; 17 pinned to commits |
-| GitHub API | `repos/…/git/trees/<sha>?recursive=1` on 12 repos | full trees, 84–5 008 entries each | 09-07 | located every schematic, datasheet, firmware and pin header without guessing paths |
-| GitHub raw | 60+ individual files at pinned commits | — | 09-07 | all 200 OK; no HTML served under a binary name |
-| GitHub API | issues, `state=all`, 6 pages, on 6 repos | 550 issues | 09-07 | T-Display-S3 **318**, AMOLED-Series 123, Long 45, AMOLED 38, Pro 25, AMOLED-1.64 1 |
-| GitHub API | 22 individual issue threads with all comments | — | 09-07 | the gotcha corpus. Selection rule: ≥5 comments **or** ≥2 reactions, then filtered for technical content |
-| GitHub code search | `repo:esphome/esphome t-display-s3` | 4 hits | 09-07 | **found**: `mipi_spi/models/lilygo.py`, `amoled.py`, `esp32/boards.py` |
-| GitHub code search | `repo:arendst/Tasmota lilygo` | 19 hits | 09-07 | Tasmota has LilyGO material but no T-Display-S3 board file; support is via a runtime template |
-| GitHub code search | `org:meshtastic tdisplay` | 247 hits | 09-07 | **negative result**: no T-Display-S3 variant. Expected — no LoRa |
-| GitHub code search | `repo:wled/WLED lilygo` | 10 hits | 09-07 | **negative result**: only a `TTGO-T-Display` usermod for the ESP32 predecessor |
-| GitHub code search | `repo:russhughes/st7789s3_mpy t-display` | 7 hits | 09-07 | MicroPython driver confirmed, with this board's `tft_config.py` |
-| LilyGO store | `collections/all/products.json`, 6 pages | 214 products | 09-07 | dated prices, SKUs, stock, `published_at`, **the V1.0/V2.0 concurrency finding** |
-| old.reddit.com | `search.json` × 4 query shapes, `t=all` | 25 results each | 09-07 | 27 family-relevant posts; 2 threads read in full |
-| Reddit | `r/esp32`, `r/arduino`, `r/LilyGO`, `r/Esphome`, `r/esp32projects`, `r/cyberDeck` | via search | 09-07 | see [`community.md`](community.md) |
-| Local | SHA-256 + size of every retained artifact | 30 files | 09-07 | **found G1** (byte-identical firmware pair) |
-| Local | ESP app-descriptor + partition-table decode, 6 images | — | 09-07 | Arduino-core dating; the 8 MB/16 MB layout split |
-| Local | PDF text extraction, 8 schematics | — | 09-07 | designator/part census for 7 boards; **T4-S3 needed a second extractor** (Type0/Identity-H) |
-
-## What was deliberately not done
-
-- **Net-level schematic tracing.** Blocked on poppler; see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) K1.
-  This is the largest single quality gap in the record and the cheapest to close.
-- **Marketplace price sampling** (AliExpress, Amazon, Banggood). Only LilyGO's own store was
-  sampled. K8.
-- **Regulatory databases** (FCC ID, CE DoC). Not searched.
-- **Chinese-language sources** beyond the Chinese datasheets and READMEs already in the repos.
-  Bilibili, Zhihu and CSDN were not searched; recorded as a deliberate exclusion.
-- **YouTube.** LilyGO links two of their own videos from the README; no independent video was
-  catalogued.
-- **Hardware.** None available.
-
-## Dead ends and corrections
-
-| Attempt | What happened |
-|---|---|
-| `gh api repos/Xinyuan-LilyGO/T-Display-S2` | 404. The repo is `LilyGo-T-Display-S2` — LilyGO's naming is inconsistent between repo and product |
-| First PDF extractor read `/Contents` only | Returned 403 pin markers and zero labels. Altium puts the sheet in a Form XObject |
-| Second attempt read `Tj`/`TJ` per line | Shredded every label into single characters. Fixed by grouping on `BT…ET` |
-| T4-S3 schematic returned nothing | Uses Type0/Identity-H subset fonts; needed a `/ToUnicode` CMap decoder |
-| CO5300 datasheet text looked readable but wrong | **Uniform +0x1D code-point offset.** Two independent extraction routes both produced garbage that decodes to the same answer. Exactly the trap the skill warns about; recorded in the vendor guide |
-| Assumed the charger was SY6970 (it is, on four other boards) | **Wrong for this board.** The schematic says TP4065. Corrected before it reached any record |
-| Assumed `U6` = flash from a partial text join | **Wrong.** `U3` is the W25Q128JV; `U6` is the charger. Corrected by re-reading the joined strings |
-
-That last pair is worth keeping: both were candidate readings promoted too early, caught by
-re-reading the primary evidence. Neither reached a component record.
-
-## Stopping criterion
-
-Two consecutive broad passes over the issue trackers and Reddit produced only duplicates of
-findings already recorded (GPIO15, `USB CDC On Boot`, `User_Setup_Select.h`, battery ADC).
-Remaining unexplored sources require **hardware** (K4, K5), **a package manager** (K1–K3), or
-**marketplace sampling** (K8). The record stops there and says so.
diff --git a/devices/lilygo/t-display-s3/resources-and-conflicts.md b/devices/lilygo/t-display-s3/resources-and-conflicts.md
deleted file mode 100644
index 9d89c21..0000000
--- a/devices/lilygo/t-display-s3/resources-and-conflicts.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# T-Display-S3 — resources, ownership and conflicts
-
-## GPIO budget
-
-45 GPIOs on the ESP32-S3; **7 genuinely free** on this board. Derivation:
-[`features/gpio-and-expansion.md`](features/gpio-and-expansion.md).
-
-| Owner | Pins | Releasable? |
-|---|---|---|
-| OPI PSRAM (in package) | 26–37 | **No.** Physically bonded |
-| LCD 8080 bus | 5,6,7,8,9,39,40,41,42,45,46,47,48 | only by not using the display |
-| Backlight | 38 | no |
-| `V3V` gate | 15 | no |
-| Native USB | 19,20 | only by not using USB |
-| UART0 | 43,44 | in ESP-IDF via `sdkconfig`; **not in Arduino** |
-| Battery sense | 4 | yes, at the cost of all battery monitoring |
-| Buttons | 0,14 | 14 yes; 0 is the strap/BOOT pin |
-| I²C + fitted pull-ups | 17,18 | pull-ups are soldered |
-| Touch IRQ/RST | 16,21 | **16 has a fitted pull-up even without touch** |
-| **Free** | **1,2,3,10,11,12,13** | 11/12/13 lost to the TF Shield |
-
-## Peripheral ownership
-
-| Peripheral | Owner | Contention |
-|---|---|---|
-| **LCD_CAM (i80)** | the display, exclusively | one unit; nothing else can use it |
-| **ADC1** | battery sense on ch3 (GPIO4) | other analogue inputs must also be ADC1 (GPIO1–10) |
-| **ADC2** | — | **unusable while Wi-Fi is on.** Silicon limitation |
-| **I²C0** | touch controller + the SH1.0 connector | one bus, shared |
-| **UART0** | `Serial` when `USB CDC On Boot` is off | GPIO43/44 |
-| **USB-Serial-JTAG** | `Serial` + flashing + JTAG when `ARDUINO_USB_MODE=1` | **mutually exclusive with TinyUSB device roles** |
-| **SDMMC (1-bit)** | TF Shield only | GPIO11/12/13 |
-| **Radio** | Wi-Fi and BLE time-share one radio | throughput roughly halves when both are active |
-| **GDMA** | one channel per active LCD/SD transfer | ample |
-
-## Memory
-
-| Resource | Size | Notes |
-|---|---|---|
-| Internal SRAM | 512 KB (`maximum_ram_size 327680` usable per the board manifest) | |
-| PSRAM | **8 MB, OPI, in package** | **requires `PSRAM = OPI PSRAM`.** Wrong setting = silently absent |
-| Flash | 16 MB, W25Q128JV, QIO 80 MHz | |
-| Default partitions | `default_16MB.csv` → app0/app1 6 400 KB each, SPIFFS 3 456 KB, coredump 64 KB | |
-| Vendor Arduino partition | `16M Flash (3M APP/9.9MB FATFS)` | different from the PlatformIO default — a source of "it fits in PlatformIO but not Arduino" |
-| Full framebuffer | 170×320×2 = **108.8 KB** | LVGL double-buffered full-height = 217.6 KB → PSRAM territory |
-
-## Power budget
-
-| Rail | Limit | Enforced by |
-|---|---|---|
-| Header `3V` | **100 mA** | vendor statement |
-| Header `VBUS` 5 V | your USB supply | output only |
-| Battery charge | 500 mA (README) / 580 mA (schematic) | soldered resistor |
-| Battery discharge | unprotected | **use a protected cell** |
-
-## Realistic feature combinations
-
-| Combination | Works? | Cost |
-|---|---|---|
-| Display + Wi-Fi | yes | ~90–230 mA class current; framebuffer in PSRAM |
-| Display + Wi-Fi + BLE | yes | radio time-shared; expect jitter in UI updates driven by network events |
-| Display + touch + I²C sensor | yes | one bus; watch pull-up stacking and CST NAK behaviour |
-| Display + TF Shield + Wi-Fi | yes | GPIO11/12/13 gone; only GPIO1/2/3/10 remain |
-| Display + battery monitoring | yes | GPIO4 permanently spoken for; **reads 2.5 V whenever USB is attached** |
-| Display + USB HID | yes, in **USB-OTG** mode | **loses built-in JTAG debugging** |
-| Deep sleep + touch wake | **partial** | the touch controller is on the GPIO15-gated rail; keeping it alive costs sleep current |
-| Battery operation + USB serial logging | **no** | `USB CDC On Boot` must be off for reliable battery boot, which moves `Serial` to GPIO43/44 |
-| I²S audio + display | reported difficult — [issue #158](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/158) | pins are scarce; no codec fitted |
-
-## Boot straps
-
-| Pin | Strap | Board use | Risk |
-|---|---|---|---|
-| 0 | boot mode | BOOT button | pressing it during reset enters download mode |
-| 3 | JTAG source | free | leave floating |
-| 45 | `VDD_SPI` voltage | **LCD_D4** | driven only after boot; do not load the pin |
-| 46 | boot config | **LCD_D5** | as above |
diff --git a/devices/lilygo/t-display-s3/sources.md b/devices/lilygo/t-display-s3/sources.md
deleted file mode 100644
index b60610b..0000000
--- a/devices/lilygo/t-display-s3/sources.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# T-Display-S3 — sources
-
-All retrieved **2026-09-07** unless stated. `Class` ∈ {primary, authorized mirror, credible
-mirror, standard, community}. GitHub sources are cited by **commit**, never by branch.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| S1 | `T-Display-S3` repository, README.md | Xinyuan-LilyGO (LILYGO) | primary | repository | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/README.md | 2026-09-07 | commit 2026-08-31 | pinout, Arduino settings, FAQ, electrical envelope, LED behaviour, antenna switch | vendor prose; contradicts its own schematic on charge current | `scratch/lilygo-t-display-s3/repos/T-Display-S3@ec889e7/README.md` |
-| S2 | `schematic/T_Display_S3.pdf` | LILYGO | primary | schematic | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/schematic/T_Display_S3.pdf | 2026-09-07 | title block **2024-04-29** | designator/part census: ESP32-S3R8, W25Q128JV, AW9364DNR, TP4065, AP2112K-3.3, USB-C, 3 buttons, 2 LEDs | **only one sheet; net connectivity not traced**; disagrees with a shipping board (G2) | [`../t-display-s3-shared/artifacts/schematic/T_Display_S3.pdf`](../t-display-s3-shared/artifacts/schematic/T_Display_S3.pdf) |
-| S3 | `examples/factory/pin_config.h` | LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/examples/factory/pin_config.h | 2026-09-07 | commit 2026-08-31 | the authoritative GPIO map | consistent across 13 sibling copies | scratch |
-| S4 | `platformio.ini` | LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/platformio.ini | 2026-09-07 | commit 2026-08-31 | `espressif32@6.5.0`, the five build flags, `-DTOUCH_MODULES_CST_MUTUAL` | — | [`../t-display-s3-shared/artifacts/originals/platformio.ini`](../t-display-s3-shared/artifacts/originals/platformio.ini) |
-| S5 | `boards/lilygo-t-display-s3.json` | LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/boards/lilygo-t-display-s3.json | 2026-09-07 | commit 2026-08-31 | `qio_opi`, `default_16MB.csv`, 240 MHz, USB VID/PID `303A:1001` | — | [`../t-display-s3-shared/artifacts/originals/boards-lilygo-t-display-s3.json`](../t-display-s3-shared/artifacts/originals/boards-lilygo-t-display-s3.json) |
-| S6 | `lib/TFT_eSPI/User_Setups/Setup206_LilyGo_T_Display_S3.h` | Bodmer / LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/lib/TFT_eSPI/User_Setups/Setup206_LilyGo_T_Display_S3.h | 2026-09-07 | commit 2026-08-31 | the exact TFT_eSPI configuration, `CGRAM_OFFSET`, `TFT_RGB_ORDER TFT_RGB` | vendored copy; upstream TFT_eSPI may differ | [`../t-display-s3-shared/artifacts/tft-espi/`](../t-display-s3-shared/artifacts/tft-espi/Setup206_LilyGo_T_Display_S3.h) |
-| S7 | `firmware/` — six merged images + `README.MD` | LILYGO | primary | firmware | https://github.com/Xinyuan-LilyGO/T-Display-S3/tree/ec889e789b3cf093412689a143f7f37b42b56af7/firmware | 2026-09-07 | file dates 2023-03 … 2025-01 | partition layouts, Arduino-core build stamps, **G1 byte-identical pair** | no vendor checksums published | [`../t-display-s3-shared/artifacts/firmware/`](../t-display-s3-shared/artifacts/firmware/) |
-| S8 | `LilyGo-Display-IDF` → `main/product_pins.h` | LILYGO | primary | repository | https://github.com/Xinyuan-LilyGO/LilyGo-Display-IDF/blob/b1a1cc54994bf1b417e3bb30c437bbe1036bff7f/main/product_pins.h | 2026-09-07 | commit 2025-11-03 | independent confirmation of the pin map, plus nine sibling boards | ESP-IDF side only | [`../t-display-s3-shared/artifacts/originals/LilyGo-Display-IDF-product_pins.h`](../t-display-s3-shared/artifacts/originals/LilyGo-Display-IDF-product_pins.h) |
-| S9 | `esphome/components/mipi_spi/models/lilygo.py` | ESPHome project | primary (third-party) | repository | https://github.com/esphome/esphome/blob/dev/esphome/components/mipi_spi/models/lilygo.py | 2026-09-07 | branch `dev` | **independent** pin/offset/colour confirmation: `offset_width=35`, `enable_pin=[9,15]`, 10 MHz, `MODE_BGR` | **cited by branch, not commit** — the only such citation here, flagged in [`research-log.md`](research-log.md) | scratch |
-| S10 | Store product feed, `t-display-s3` | LILYGO (Shopify) | primary | store listing | https://lilygo.cc/collections/all/products.json | 2026-09-07 | feed `updated_at` 2026-09-07 | 13 SKUs, dated prices, stock, regional variants, publication date 2022-07-15 | prices exclude shipping/tax | `scratch/lilygo-t-display-s3/shop-products.jsonl` |
-| S11 | Issue #79 "If you are having difficulty with your new T-Display S3" | teastainGit + LILYGO maintainer | community | forum/issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/79 | 2026-09-07 | 2023-01-03 → 2024 | the GPIO15 trap; a widely used third-party setup guide | firsthand ownership; multiple corroborations | — |
-| S12 | Issue #230 "T-Display-S3 Battery Charge Circuit?" | rpsavage + lewisxhe | community | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230 | 2026-09-07 | 2024-03-02 → 2025-02-06 | **firsthand PCB inspection**: charger is a 5-lead TSOT-23 marked `65b311`; correct ADC recipe; vendor confirms **no battery protection** | one board, one owner | — |
-| S13 | Issue #313 "Pins 16 and 17 in floating mode" | sgbmzm + lewisxhe | community → vendor-confirmed | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313 | 2026-09-07 | 2025-07-28 | fitted pull-ups on GPIO16/17 **on non-touch boards**, with vendor PCB photographs | photos are GitHub-hosted user content | — |
-| S14 | Issue #190 "Measure BAT_ADC incorrect voltage" | krupis | community | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/190 | 2026-09-07 | 2023-09-22 | firsthand measurement: raw-count arithmetic gives 2.14 V for a 3.9 V cell | ESP-IDF, one board | — |
-| S15 | Issue #212 "Firmware_no_Touch is the same as Touch ?" | Maddin4000, teastainGit | community | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/212 | 2026-09-07 | 2024-01-02 | independent notice of **G1**; the ESP-Touch/LCD-touch naming confusion; the `User_Setup_Select.h` overwrite problem | never resolved by vendor | — |
-| S16 | Issue #42 "Can not charge the battery via IO PIN" | fjulian79 + mmMicky (LILYGO) | community + vendor reply | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/42 | 2026-09-07 | 2022-11-07 → 2023-11-01 | `VBUS` not on header; vendor "solder a wire"; firsthand back-powering report | back-powering report not reproduced | — |
-| S17 | Issue #205 "Power T-Display-S3 with external 3.3V/5V" | danielcharrua + teastainGit | community | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/205 | 2026-09-07 | 2023-11-30 | supported power inputs; 5 V pin is output-only | answers are community, not vendor | — |
-| S18 | Issue #18 "Tasmota support" | multiple + Jason2866 (Tasmota) | community | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/18 | 2026-09-07 | 2022-10-06 → 2024-03 | **Tasmota works**: `Tasmota32-S3 (QIO Flash/OPI PSRAM)` + autoconf template "Lilygo S3 Display"; `Display Model 17`, 320×170; `displaydimmer 100` needed | firsthand user reports incl. a Tasmota maintainer | — |
-| S19 | Issue #313-adjacent: #326 TFT_eSPI `#error` | multiple | community | issue | https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/326 | 2026-09-07 | 2026-02-23 | the `User_Setup_Select.h` failure now surfaces as a compile error | — | — |
-| S20 | r/esp32 "LilyGo T-Display S3 Clock with DS18B20 and PIR — lessons learned" | u/Alarming_Breadfruit5 et al. | community | forum | https://old.reddit.com/r/esp32/comments/1tnop7r/lilygo_tdisplay_s3_clock_with_ds18b20_and_pir/ | 2026-09-07 | 2026-05-25 | **firsthand, independently reproduced**: GPIO43/44 unusable under Arduino; core 3.x LEDC rename; GPIO15+GPIO38 both needed; a working battery/shell combination | one project; the sdkconfig workaround is untested | `scratch/lilygo-t-display-s3/reddit.txt` |
-| S21 | `ST7789V_SPEC_V1.4.pdf` | Sitronix, mirrored by LILYGO | credible mirror | datasheet | https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/ec889e789b3cf093412689a143f7f37b42b56af7/datasheet/ST7789V_SPEC_V1.4.pdf | 2026-09-07 | spec v1.4 | the fitted display controller | vendor mirror; **filed under the component, not here** | [`components/sitronix/st7789v/artifacts/`](../../../components/sitronix/st7789v/artifacts/st7789v-spec-v1.4-lilygo-mirror.pdf) |
-| S22 | `CST816S寄存器说明-20190508.pdf`, `CST328数据手册V2.2.pdf` | Hynitron, mirrored by LILYGO | credible mirror | datasheet | same repo, `datasheet/` | 2026-09-07 | 2019-05-08 / V2.2 | **two** touch controllers ⇒ revision R1 | Chinese only | [`components/hynitron/cst816d/artifacts/`](../../../components/hynitron/cst816d/artifacts/) · [`components/hynitron/cst328/artifacts/`](../../../components/hynitron/cst328/artifacts/) |
-| S23 | Espressif ESP32-S3 datasheet & TRM | Espressif | primary | datasheet | (already held) | — | — | GPIO26–37 reserved by OPI PSRAM; ADC2/Wi-Fi conflict; strapping pins | — | [`components/espressif/esp32-s3r8/artifacts/`](../../../components/espressif/esp32-s3r8/artifacts/) |
-| S24 | `Xinyuan-LilyGO` org repository listing (254 repos) | GitHub API | primary | repository | `gh api orgs/Xinyuan-LilyGO/repos` | 2026-09-07 | live | the family enumeration | — | [`../t-display-s3-shared/artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv`](../t-display-s3-shared/artifacts/originals/xinyuan-lilygo-org-repos-2026-09-07.tsv) |
-| S25 | `teastainGit/LilyGO-T-display-S3-setup-and-examples` | Terry Stainton | community | repository | https://github.com/teastainGit/LilyGO-T-display-S3-setup-and-examples | 2026-09-07 | ongoing since 2023-01 | the de-facto community setup guide; endorsed in-thread by LILYGO's `lewisxhe` (2023-03-13: *"Thank you for bringing more clear and concise examples"*) | third-party; not pinned to a commit here | — |
-
-## Sources sought and not found
-
-| Sought | Result |
-|---|---|
-| A numbered PCB revision for the base board | **none published.** The schematic has a date, not a revision |
-| Vendor checksums for the factory images | none |
-| An independent benchmark or current measurement | none located across the searched set |
-| A CircuitPython board definition | not found (absence **not** proven — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) K6) |
-| A Meshtastic variant | none, and none possible: no LoRa radio |
-| A WLED build | none for S3; `wled/WLED` has a `TTGO-T-Display` usermod for the ESP32 predecessor only |
-| FCC/CE certification records | not searched in this pass — recorded as a gap |
diff --git a/devices/lilygo/t-display-ttgo/README.md b/devices/lilygo/t-display-ttgo/README.md
deleted file mode 100644
index bd1902a..0000000
--- a/devices/lilygo/t-display-ttgo/README.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# LilyGO / TTGO T-Display (ESP32) — lineage stub
-
-> **Stub record**, written to anchor the T-Display-S3's ancestry. Not researched to device
-> depth. Store handle `t-display`, published **2023-08-04** (the *store page*; the product is
-> older — the repo predates it). SKUs `Q224` 4 MB **USD 8.04**, `Q125` 16 MB **USD 8.94**,
-> `K163`/`K164`/`K198` with shell **USD 11.99–12.99**. In stock 2026-09-07.
-> Repo `Xinyuan-LilyGO/TTGO-T-Display` @ **`6f89cddcde7152b84f7afc1831b6a1dee1fc3206`**,
-> licence MIT, **1 192★** — the most-starred repository in the whole organisation.
-
-## Identity
-
-| | | Source |
-|---|---|---|
-| SoC | **ESP32** (not S3), dual LX6 | store, repo |
-| Display | **1.14″, 135 × 240**, ST7789 on **4-wire SPI** | ESPHome model `T-DISPLAY` |
-| Pins (ESPHome model) | `cs_pin=5, dc_pin=16`, `offset_width=52, offset_height=40`, `invert_colors=True` | `esphome/components/mipi_spi/models/lilygo.py`, `dev` @ 2026-09-07 |
-| Pins (ESP-IDF) | `POWERON 14`, `SPI MISO 21 / MOSI 19 / SCK 18`, `TFT_CS 5 / RST 23 / DC 16 / BL 4` | `LilyGo-Display-IDF/main/product_pins.h`, `#elif CONFIG_LILYGO_T_DISPLAY` @ `b1a1cc5` |
-| Flash | 4 MB or 16 MB **as a purchase option** | store SKUs `Q224` / `Q125` |
-
-## Why it matters to the T-Display-S3
-
-- **It defined the format** — a cheap ESP32 with a bonded colour strip, two buttons and a
-  battery connector — and the S3 board is a straight re-do of it with a faster SoC, a bigger
-  panel and a parallel bus.
-- **It carries a power-enable pin too** (`BOARD_POWERON 14`), which is the direct ancestor of
-  the T-Display-S3's GPIO15 gate. The trap is inherited, not new.
-- **It has software support the S3 board does not**: `wled/WLED` ships
-  `usermods/TTGO-T-Display/`, and there is no WLED equivalent for any S3 board in the family.
-- Its 1 192★ against the S3's 1 169★ is the clearest single measure of how much community mass
-  the line carries.
-
-## Differences that matter if you are choosing between them
-
-| | T-Display (ESP32) | T-Display-S3 |
-|---|---|---|
-| Price 2026-09-07 | **USD 8.04** | USD 9.04 |
-| SoC | ESP32 (LX6, BLE **and Classic Bluetooth**) | ESP32-S3 (LX7, **BLE only**) |
-| Display | 1.14″ 135×240 SPI | 1.9″ 170×320 **8-bit parallel** |
-| PSRAM | none | 8 MB OPI |
-| Flash | 4 or 16 MB | 16 MB |
-| USB | CH340-class bridge | **native USB**, no bridge |
-| WLED | **supported** | not supported |
-
-**The ESP32 board is the one to pick if you need Classic Bluetooth or WLED.** For everything
-else the S3 board is better for a dollar more.
-
-## Gaps
-
-This is a **stub**. No pinout table beyond the two vendor sources quoted, no schematic
-retrieved, no artifacts held, no market analysis beyond the store snapshot. Documented to the
-depth needed to establish lineage and nothing further.
diff --git a/devices/lilygo/t-display-ttgo/acquisition/manifest.json b/devices/lilygo/t-display-ttgo/acquisition/manifest.json
deleted file mode 100644
index fdeaed8..0000000
--- a/devices/lilygo/t-display-ttgo/acquisition/manifest.json
+++ /dev/null
@@ -1,296 +0,0 @@
-{
- "record": "devices/lilygo/t-display-ttgo",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793896",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/External-Photos/External-Photos-5793896.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793896",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793896.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/External-Photos/External-Photos-5793896.pdf"
-   ],
-   "sha256": "1f1fce9575b54ebbbd9db1f421de4c34b903fed963fbc074048ae1e9bfde985e",
-   "bytes": 269648,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793896",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf",
-   "placeholder": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793897",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/Label/ID-Label-and-Label-Location-5793897.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793897",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793897.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/Label/ID-Label-and-Label-Location-5793897.pdf"
-   ],
-   "sha256": "f7f17e85c56b9ac65b2ccb7fd6c75c9b497b9154acc88426d185ca1b60024515",
-   "bytes": 684932,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-id-label-and-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793897",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "ID Label and Label Location",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793898",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/Internal-Photos/Internal-Photos-5793898.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793898",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793898.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/Internal-Photos/Internal-Photos-5793898.pdf"
-   ],
-   "sha256": "d2ba004a92339bfe06be50a6e00cbec4b77bfda241689846f6cd0d0dd5fc2bbd",
-   "bytes": 412217,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793898",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793876",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/Label/Label-Location-5793876.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793876",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793876.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/Label/Label-Location-5793876.pdf"
-   ],
-   "sha256": "f7f17e85c56b9ac65b2ccb7fd6c75c9b497b9154acc88426d185ca1b60024515",
-   "bytes": 684932,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793876",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label & Location",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793880",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/RF-Exposure-Info/RF-Exposure-5793880.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793880",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793880.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/RF-Exposure-Info/RF-Exposure-5793880.pdf"
-   ],
-   "sha256": "9eb5745466139f519ee424ebd7fb13dccb36752fee22d3d85a6e85110bc6c5d6",
-   "bytes": 172367,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793880",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf",
-   "placeholder": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793902",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/Test-Report/Test-Report-5793902.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793902",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793902.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/Test-Report/Test-Report-5793902.pdf"
-   ],
-   "sha256": "ff8e1a9ab5d3796df1607140a27f01402fdda74d8c6f9041092ac2cd934f4258",
-   "bytes": 5339001,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793902",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Test Report",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf",
-   "placeholder": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793883",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-manual-5793883.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793883",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793883.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-manual-5793883.pdf"
-   ],
-   "sha256": "d8d3912dd323438e2501a69a22bf8c7e74000fd03c186f243b378293dd134417",
-   "bytes": 909089,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793883",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User manual",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf",
-   "placeholder": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DISPLAY-5793904",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-Manual-5793904.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793904",
-    "https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793904.pdf",
-    "https://fccid.io/2ASYE-T-DISPLAY",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-Manual-5793904.pdf"
-   ],
-   "sha256": "d8d3912dd323438e2501a69a22bf8c7e74000fd03c186f243b378293dd134417",
-   "bytes": 909089,
-   "destination": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-04-01",
-   "fcc_id": "2ASYE-T-DISPLAY",
-   "fcc_document_id": "5793904",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2022-04-01",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf",
-   "placeholder": "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-display-ttgo",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 69d0ec3..0000000
--- a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 269,648 B (0.26 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 269,648 B (0.26 MiB) |
-| SHA-256 | `1f1fce9575b54ebbbd9db1f421de4c34b903fed963fbc074048ae1e9bfde985e` |
-| FCC ID | **`2ASYE-T-DISPLAY`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 5793896 |
-| Upstream publication date | 2022-04-01 |
-| Grant date | 2022-04-01 |
-| Equipment class | T-Display, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY/External-Photos/External-Photos-5793896.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793896>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793896.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/External-Photos/External-Photos-5793896.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf" \
-   "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY/External-Photos/External-Photos-5793896.pdf" -o "2ASYE-T-DISPLAY-external-photos.pdf"
-echo "1f1fce9575b54ebbbd9db1f421de4c34b903fed963fbc074048ae1e9bfde985e  2ASYE-T-DISPLAY-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-id-label-and-label-location.pdf b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-id-label-and-label-location.pdf
deleted file mode 100644
index 3783c97..0000000
Binary files a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-id-label-and-label-location.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-internal-photos.pdf b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-internal-photos.pdf
deleted file mode 100644
index c3efec8..0000000
Binary files a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-label-location.pdf b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-label-location.pdf
deleted file mode 100644
index 3783c97..0000000
Binary files a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-label-location.pdf and /dev/null differ
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf.ARCHIVED.md b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf.ARCHIVED.md
deleted file mode 100644
index 0c6e92d..0000000
--- a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-rf-exposure.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 172,367 B (0.16 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 172,367 B (0.16 MiB) |
-| SHA-256 | `9eb5745466139f519ee424ebd7fb13dccb36752fee22d3d85a6e85110bc6c5d6` |
-| FCC ID | **`2ASYE-T-DISPLAY`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure |
-| FCC document id | 5793880 |
-| Upstream publication date | 2022-04-01 |
-| Grant date | 2022-04-01 |
-| Equipment class | T-Display, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY/RF-Exposure-Info/RF-Exposure-5793880.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793880>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793880.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/RF-Exposure-Info/RF-Exposure-5793880.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf" \
-   "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-rf-exposure.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY/RF-Exposure-Info/RF-Exposure-5793880.pdf" -o "2ASYE-T-DISPLAY-rf-exposure.pdf"
-echo "9eb5745466139f519ee424ebd7fb13dccb36752fee22d3d85a6e85110bc6c5d6  2ASYE-T-DISPLAY-rf-exposure.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf.ARCHIVED.md b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf.ARCHIVED.md
deleted file mode 100644
index 3502a24..0000000
--- a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-test-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 5,339,001 B (5.09 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 5,339,001 B (5.09 MiB) |
-| SHA-256 | `ff8e1a9ab5d3796df1607140a27f01402fdda74d8c6f9041092ac2cd934f4258` |
-| FCC ID | **`2ASYE-T-DISPLAY`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Test Report |
-| FCC document id | 5793902 |
-| Upstream publication date | 2022-04-01 |
-| Grant date | 2022-04-01 |
-| Equipment class | T-Display, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY/Test-Report/Test-Report-5793902.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793902>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793902.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/Test-Report/Test-Report-5793902.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf" \
-   "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-test-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY/Test-Report/Test-Report-5793902.pdf" -o "2ASYE-T-DISPLAY-test-report.pdf"
-echo "ff8e1a9ab5d3796df1607140a27f01402fdda74d8c6f9041092ac2cd934f4258  2ASYE-T-DISPLAY-test-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf.ARCHIVED.md b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf.ARCHIVED.md
deleted file mode 100644
index 9a252ae..0000000
--- a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-user-manual-5793883.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 909,089 B (0.87 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 909,089 B (0.87 MiB) |
-| SHA-256 | `d8d3912dd323438e2501a69a22bf8c7e74000fd03c186f243b378293dd134417` |
-| FCC ID | **`2ASYE-T-DISPLAY`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User manual |
-| FCC document id | 5793883 |
-| Upstream publication date | 2022-04-01 |
-| Grant date | 2022-04-01 |
-| Equipment class | T-Display, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-manual-5793883.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793883>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793883.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-manual-5793883.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf" \
-   "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793883.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-manual-5793883.pdf" -o "2ASYE-T-DISPLAY-user-manual-5793883.pdf"
-echo "d8d3912dd323438e2501a69a22bf8c7e74000fd03c186f243b378293dd134417  2ASYE-T-DISPLAY-user-manual-5793883.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf.ARCHIVED.md b/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf.ARCHIVED.md
deleted file mode 100644
index cb17087..0000000
--- a/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DISPLAY-user-manual-5793904.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 909,089 B (0.87 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 909,089 B (0.87 MiB) |
-| SHA-256 | `d8d3912dd323438e2501a69a22bf8c7e74000fd03c186f243b378293dd134417` |
-| FCC ID | **`2ASYE-T-DISPLAY`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 5793904 |
-| Upstream publication date | 2022-04-01 |
-| Grant date | 2022-04-01 |
-| Equipment class | T-Display, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-Manual-5793904.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=5793904>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DISPLAY/5793904.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DISPLAY>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-Manual-5793904.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf" \
-   "devices/lilygo/t-display-ttgo/artifacts/certification/2ASYE-T-DISPLAY-user-manual-5793904.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DISPLAY/User-Manual/User-Manual-5793904.pdf" -o "2ASYE-T-DISPLAY-user-manual-5793904.pdf"
-echo "d8d3912dd323438e2501a69a22bf8c7e74000fd03c186f243b378293dd134417  2ASYE-T-DISPLAY-user-manual-5793904.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-display-ttgo/artifacts/certification/README.md b/devices/lilygo/t-display-ttgo/artifacts/certification/README.md
deleted file mode 100644
index 53051a4..0000000
--- a/devices/lilygo/t-display-ttgo/artifacts/certification/README.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-T-DISPLAY`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-T-DISPLAY`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2022-04-01** |
-| Equipment class | T-Display, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Source page | <https://fccid.io/2ASYE-T-DISPLAY> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-T-DISPLAY-id-label-and-label-location.pdf` | 684,932 | `f7f17e85c56b9ac65b2ccb7fd6c75c9b497b9154acc88426d185ca1b60024515` | ID Label/Location Info |
-| `2ASYE-T-DISPLAY-internal-photos.pdf` | 412,217 | `d2ba004a92339bfe06be50a6e00cbec4b77bfda241689846f6cd0d0dd5fc2bbd` | Internal Photos |
-| `2ASYE-T-DISPLAY-label-location.pdf` | 684,932 | `f7f17e85c56b9ac65b2ccb7fd6c75c9b497b9154acc88426d185ca1b60024515` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-T-DISPLAY-external-photos.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-external-photos.pdf.ARCHIVED.md) | 269,648 | External Photos |
-| [`2ASYE-T-DISPLAY-rf-exposure.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-rf-exposure.pdf.ARCHIVED.md) | 172,367 | RF Exposure Info |
-| [`2ASYE-T-DISPLAY-test-report.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-test-report.pdf.ARCHIVED.md) | 5,339,001 | Test Report |
-| [`2ASYE-T-DISPLAY-user-manual-5793883.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-user-manual-5793883.pdf.ARCHIVED.md) | 909,089 | Users Manual |
-| [`2ASYE-T-DISPLAY-user-manual-5793904.pdf.ARCHIVED.md`](2ASYE-T-DISPLAY-user-manual-5793904.pdf.ARCHIVED.md) | 909,089 | Users Manual |
-
-Archived total: **5 files, 7.25 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **3 files, 1.70 MiB** |
-| Archived | **5 files, 7.25 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t-display-ttgo/certification-and-compliance.md b/devices/lilygo/t-display-ttgo/certification-and-compliance.md
deleted file mode 100644
index 4227b70..0000000
--- a/devices/lilygo/t-display-ttgo/certification-and-compliance.md
+++ /dev/null
@@ -1,127 +0,0 @@
-# Certification and compliance — t-display-ttgo
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-`2ASYE-T-DISPLAY` (2022-04-01, product 'T-Display') is the original ESP32 T-Display / TTGO board.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-T-DISPLAY` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-DISPLAY`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2022-04-01 2402-2480 MHz Original Equipment 2022-04-01** |
-| Application purpose | Original Equipment |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 14 available, 4 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DISPLAY` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Circuit Description [Operational Description]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 269,648 | `1f1fce9575b54ebb…` |
-| `ID-Label-Location-Info-ID-Label-and-Label-Location.pdf` | 684,932 | `f7f17e85c56b9ac6…` |
-| `ID-Label-Location-Info-Label-Location.pdf` | 684,932 | `f7f17e85c56b9ac6…` |
-| `Internal-Photos-Internal-Photos.pdf` | 412,217 | `d2ba004a92339bfe…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 172,367 | `9eb5745466139f51…` |
-| `Test-Report-Test-Report.pdf` | 5,339,001 | `ff8e1a9ab5d3796d…` |
-| `Users-Manual-User-Manual.pdf` | 909,089 | `d8d3912dd323438e…` |
-| `Users-Manual-User-manual.pdf` | 909,089 | `d8d3912dd323438e…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DISPLAY/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DISPLAY/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-display-ttgo/market-and-pricing.md b/devices/lilygo/t-display-ttgo/market-and-pricing.md
deleted file mode 100644
index f7a4c8f..0000000
--- a/devices/lilygo/t-display-ttgo/market-and-pricing.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# Market and pricing — t-display-ttgo
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Display | 2023-08-04 | 4MB [Q224] | `Q224` | **USD 8.04** | ✅ yes |
-| T-Display | 2023-08-04 | 16MB [Q125] | `Q125` | **USD 8.94** | ✅ yes |
-| T-Display | 2023-08-04 | 4MB With Shell [K163] | `K163` | **USD 11.99** | ✅ yes |
-| T-Display | 2023-08-04 | 16MB With Shell Soldered [K198] | `K198` | **USD 12.99** | ❌ no |
-| T-Display | 2023-08-04 | 16MB With Shell Non-Soldered [K164] | `K164` | **USD 12.99** | ✅ yes |
-| T-Display Case | 2022-08-19 | T-Display Case [L925] | `L925` | **USD 2.17** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 8.04, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-display`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-The original ESP32 T-Display: 4 MB USD 8.04, 16 MB USD 8.94, with shell USD 11.99–12.99. Case alone USD 2.17. **Still in stock in 2026** — an unusually long life for this class of board.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-dongle-s3/README.md b/devices/lilygo/t-dongle-s3/README.md
deleted file mode 100644
index 3c62c8d..0000000
--- a/devices/lilygo/t-dongle-s3/README.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# LilyGO T-Dongle-S3 — lineage stub
-
-> **Stub record.** A relative, not a T-Display-S3 variant. Store handle `t-dongle-s3`,
-> published **2022-10-20**, SKUs from **USD 10.99** (up to 16.49). In stock 2026-09-07.
-> Repo `Xinyuan-LilyGO/T-Dongle-S3` @ **`f279831ee660346f29afd5c9a589394c1758a843`**, MIT,
-> **412★** — the third-most-starred display board in the organisation.
-> Research retrieved 2026-09-07. No hardware.
-
-## Identity
-
-| | | Source |
-|---|---|---|
-| Format | a **USB-A dongle**: the board *is* the plug | store, repo |
-| Description | *"An ESP32S3 development board that can freely use WIFI, BLE, TF, LED, TFT_LCD functions."* | repo description |
-| Display | **0.96″ 80 × 160 ST7735** on SPI | `TFT_eSPI` `Setup209_LilyGo_T_Dongle_S3.h` ships in the T-Display-S3 repo's vendored TFT_eSPI |
-| Storage | **microSD on board** — unlike the T-Display-S3 | repo description |
-| RGB LED | APA102/WS2812-class, driven by the vendored `FastLED` | tree listing |
-| IR | `IRremoteESP8266` vendored | tree listing |
-| Board variants | `boards/dongles3.json`, `dongles3-plus.json`, `dongles3-dual.json` — **three** PlatformIO board definitions in one repo | tree listing @ `f279831` |
-
-## Relationship to the T-Display-S3
-
-Shares the ESP32-S3, the native-USB flashing path, the `USB CDC On Boot` trap, and the
-Arduino-core pinning culture. **Shares no PCB, panel, bus or pin map.** Its display is a
-different controller (ST7735) on a different bus (SPI).
-
-Two things it has that the T-Display-S3 does not, and which are the reasons to choose it:
-**an on-board microSD slot** (the T-Display-S3 needs a shield) and **a USB-A plug** instead of
-a socket, which makes it a dongle rather than a module.
-
-**Three board JSONs** (`dongles3`, `dongles3-plus`, `dongles3-dual`) in one repository is the
-same revision-drift pattern documented family-wide in
-[`../t-display-s3-shared/board-revision-drift.md`](../t-display-s3-shared/board-revision-drift.md)
-— multiple hardware variants behind one product name, distinguished only by a build target.
-
-## Gaps
-
-**Stub.** No schematic retrieved, no artifacts, no component records, no pinout table, and the
-three board variants were not differentiated. Documented only to the depth needed to place it
-in the family.
diff --git a/devices/lilygo/t-dongle-s3/acquisition/manifest.json b/devices/lilygo/t-dongle-s3/acquisition/manifest.json
deleted file mode 100644
index 5eaa53f..0000000
--- a/devices/lilygo/t-dongle-s3/acquisition/manifest.json
+++ /dev/null
@@ -1,260 +0,0 @@
-{
- "record": "devices/lilygo/t-dongle-s3",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2ASYE-T-DONGLE-S3-6952910",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DONGLE-S3/Test-Report/ATN-Test-Report-6952910.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6952910",
-    "https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6952910.pdf",
-    "https://fccid.io/2ASYE-T-DONGLE-S3",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/Test-Report/ATN-Test-Report-6952910.pdf"
-   ],
-   "sha256": "36babccf0bc6ff3b44f038a6b7ac85abcaca84b23ae0a9d6fe9a7c87abea9a2f",
-   "bytes": 1762022,
-   "destination": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2023-11-30",
-   "fcc_id": "2ASYE-T-DONGLE-S3",
-   "fcc_document_id": "6952910",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "ATN Test Report",
-   "grant_date": "2023-11-30",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf",
-   "placeholder": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-dongle-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DONGLE-S3-6953261",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DONGLE-S3/External-Photos/External-Photos-6953261.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6953261",
-    "https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6953261.pdf",
-    "https://fccid.io/2ASYE-T-DONGLE-S3",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/External-Photos/External-Photos-6953261.pdf"
-   ],
-   "sha256": "33ff03496c1b655b4f6e7f0966beb0a836e3736d0502b692b434e4734a4de960",
-   "bytes": 2636746,
-   "destination": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2023-11-30",
-   "fcc_id": "2ASYE-T-DONGLE-S3",
-   "fcc_document_id": "6953261",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2023-11-30",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf",
-   "placeholder": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-dongle-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DONGLE-S3-6952915",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DONGLE-S3/Label/ID-Label-Location-Info-6952915.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6952915",
-    "https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6952915.pdf",
-    "https://fccid.io/2ASYE-T-DONGLE-S3",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/Label/ID-Label-Location-Info-6952915.pdf"
-   ],
-   "sha256": "89d39b990c0b5050f0dc96c5dfe74743052cbc1574620d0c598f659792b92c11",
-   "bytes": 777839,
-   "destination": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-id-label-location-info.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2023-11-30",
-   "fcc_id": "2ASYE-T-DONGLE-S3",
-   "fcc_document_id": "6952915",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "ID Label/Location Info",
-   "grant_date": "2023-11-30",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-dongle-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DONGLE-S3-6953266",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DONGLE-S3/Internal-Photos/Internal-Photos-6953266.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6953266",
-    "https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6953266.pdf",
-    "https://fccid.io/2ASYE-T-DONGLE-S3",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/Internal-Photos/Internal-Photos-6953266.pdf"
-   ],
-   "sha256": "2cfbd440fb850ab9b56900c932c21e6778066097ef2ab499fd9b05d20d2bae6c",
-   "bytes": 3459994,
-   "destination": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2023-11-30",
-   "fcc_id": "2ASYE-T-DONGLE-S3",
-   "fcc_document_id": "6953266",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2023-11-30",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-dongle-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DONGLE-S3-6953255",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-1-6953255.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6953255",
-    "https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6953255.pdf",
-    "https://fccid.io/2ASYE-T-DONGLE-S3",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-1-6953255.pdf"
-   ],
-   "sha256": "f1cd62088f4aea0355976aa2c0de13c5fbfc6c845adaa2a7fcb3190a5cccb37e",
-   "bytes": 100065,
-   "destination": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2023-11-30",
-   "fcc_id": "2ASYE-T-DONGLE-S3",
-   "fcc_document_id": "6953255",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Info 1",
-   "grant_date": "2023-11-30",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf",
-   "placeholder": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-dongle-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DONGLE-S3-6953256",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-2-6953256.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6953256",
-    "https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6953256.pdf",
-    "https://fccid.io/2ASYE-T-DONGLE-S3",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-2-6953256.pdf"
-   ],
-   "sha256": "63c30902c6cb6a87bda967b28de623d7cecafa0641b6c879862000ef1a700611",
-   "bytes": 100039,
-   "destination": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2023-11-30",
-   "fcc_id": "2ASYE-T-DONGLE-S3",
-   "fcc_document_id": "6953256",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Info 2",
-   "grant_date": "2023-11-30",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf",
-   "placeholder": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-dongle-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-DONGLE-S3-6952913",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-DONGLE-S3/User-Manual/Users-Manual-6952913.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6952913",
-    "https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6952913.pdf",
-    "https://fccid.io/2ASYE-T-DONGLE-S3",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/User-Manual/Users-Manual-6952913.pdf"
-   ],
-   "sha256": "fb45d5c270467b10d096a54904e0dfddd94dc532ae6f09939aaaefb7965b4e46",
-   "bytes": 4153868,
-   "destination": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2023-11-30",
-   "fcc_id": "2ASYE-T-DONGLE-S3",
-   "fcc_document_id": "6952913",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "Users Manual",
-   "grant_date": "2023-11-30",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf",
-   "placeholder": "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-dongle-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf.ARCHIVED.md b/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf.ARCHIVED.md
deleted file mode 100644
index 29079f6..0000000
--- a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DONGLE-S3-atn-test-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,762,022 B (1.68 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,762,022 B (1.68 MiB) |
-| SHA-256 | `36babccf0bc6ff3b44f038a6b7ac85abcaca84b23ae0a9d6fe9a7c87abea9a2f` |
-| FCC ID | **`2ASYE-T-DONGLE-S3`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | ATN Test Report |
-| FCC document id | 6952910 |
-| Upstream publication date | 2023-11-30 |
-| Grant date | 2023-11-30 |
-| Equipment class | T-Dongle-S3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3/Test-Report/ATN-Test-Report-6952910.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6952910>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6952910.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/Test-Report/ATN-Test-Report-6952910.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf" \
-   "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-atn-test-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DONGLE-S3/Test-Report/ATN-Test-Report-6952910.pdf" -o "2ASYE-T-DONGLE-S3-atn-test-report.pdf"
-echo "36babccf0bc6ff3b44f038a6b7ac85abcaca84b23ae0a9d6fe9a7c87abea9a2f  2ASYE-T-DONGLE-S3-atn-test-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index c76ef2a..0000000
--- a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DONGLE-S3-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 2,636,746 B (2.51 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,636,746 B (2.51 MiB) |
-| SHA-256 | `33ff03496c1b655b4f6e7f0966beb0a836e3736d0502b692b434e4734a4de960` |
-| FCC ID | **`2ASYE-T-DONGLE-S3`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 6953261 |
-| Upstream publication date | 2023-11-30 |
-| Grant date | 2023-11-30 |
-| Equipment class | T-Dongle-S3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3/External-Photos/External-Photos-6953261.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6953261>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6953261.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/External-Photos/External-Photos-6953261.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf" \
-   "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DONGLE-S3/External-Photos/External-Photos-6953261.pdf" -o "2ASYE-T-DONGLE-S3-external-photos.pdf"
-echo "33ff03496c1b655b4f6e7f0966beb0a836e3736d0502b692b434e4734a4de960  2ASYE-T-DONGLE-S3-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-id-label-location-info.pdf b/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-id-label-location-info.pdf
deleted file mode 100644
index 087acbc..0000000
Binary files a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-id-label-location-info.pdf and /dev/null differ
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-internal-photos.pdf b/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-internal-photos.pdf
deleted file mode 100644
index 2bf31a0..0000000
Binary files a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf.ARCHIVED.md b/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf.ARCHIVED.md
deleted file mode 100644
index af232fb..0000000
--- a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 100,065 B (0.10 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 100,065 B (0.10 MiB) |
-| SHA-256 | `f1cd62088f4aea0355976aa2c0de13c5fbfc6c845adaa2a7fcb3190a5cccb37e` |
-| FCC ID | **`2ASYE-T-DONGLE-S3`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Info 1 |
-| FCC document id | 6953255 |
-| Upstream publication date | 2023-11-30 |
-| Grant date | 2023-11-30 |
-| Equipment class | T-Dongle-S3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-1-6953255.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6953255>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6953255.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-1-6953255.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf" \
-   "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-1-6953255.pdf" -o "2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf"
-echo "f1cd62088f4aea0355976aa2c0de13c5fbfc6c845adaa2a7fcb3190a5cccb37e  2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf.ARCHIVED.md b/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf.ARCHIVED.md
deleted file mode 100644
index ddc870b..0000000
--- a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 100,039 B (0.10 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 100,039 B (0.10 MiB) |
-| SHA-256 | `63c30902c6cb6a87bda967b28de623d7cecafa0641b6c879862000ef1a700611` |
-| FCC ID | **`2ASYE-T-DONGLE-S3`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Info 2 |
-| FCC document id | 6953256 |
-| Upstream publication date | 2023-11-30 |
-| Grant date | 2023-11-30 |
-| Equipment class | T-Dongle-S3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-2-6953256.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6953256>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6953256.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-2-6953256.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf" \
-   "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DONGLE-S3/RF-Exposure-Info/RF-Exposure-Info-2-6953256.pdf" -o "2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf"
-echo "63c30902c6cb6a87bda967b28de623d7cecafa0641b6c879862000ef1a700611  2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf.ARCHIVED.md b/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf.ARCHIVED.md
deleted file mode 100644
index b2577bd..0000000
--- a/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-DONGLE-S3-users-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 4,153,868 B (3.96 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 4,153,868 B (3.96 MiB) |
-| SHA-256 | `fb45d5c270467b10d096a54904e0dfddd94dc532ae6f09939aaaefb7965b4e46` |
-| FCC ID | **`2ASYE-T-DONGLE-S3`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | Users Manual |
-| FCC document id | 6952913 |
-| Upstream publication date | 2023-11-30 |
-| Grant date | 2023-11-30 |
-| Equipment class | T-Dongle-S3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3/User-Manual/Users-Manual-6952913.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6952913>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-DONGLE-S3/6952913.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-DONGLE-S3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-DONGLE-S3/User-Manual/Users-Manual-6952913.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf" \
-   "devices/lilygo/t-dongle-s3/artifacts/certification/2ASYE-T-DONGLE-S3-users-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-DONGLE-S3/User-Manual/Users-Manual-6952913.pdf" -o "2ASYE-T-DONGLE-S3-users-manual.pdf"
-echo "fb45d5c270467b10d096a54904e0dfddd94dc532ae6f09939aaaefb7965b4e46  2ASYE-T-DONGLE-S3-users-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-dongle-s3/artifacts/certification/README.md b/devices/lilygo/t-dongle-s3/artifacts/certification/README.md
deleted file mode 100644
index 3524346..0000000
--- a/devices/lilygo/t-dongle-s3/artifacts/certification/README.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-T-DONGLE-S3`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-T-DONGLE-S3`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2023-11-30** |
-| Equipment class | T-Dongle-S3, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Source page | <https://fccid.io/2ASYE-T-DONGLE-S3> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-T-DONGLE-S3-id-label-location-info.pdf` | 777,839 | `89d39b990c0b5050f0dc96c5dfe74743052cbc1574620d0c598f659792b92c11` | ID Label/Location Info |
-| `2ASYE-T-DONGLE-S3-internal-photos.pdf` | 3,459,994 | `2cfbd440fb850ab9b56900c932c21e6778066097ef2ab499fd9b05d20d2bae6c` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-T-DONGLE-S3-atn-test-report.pdf.ARCHIVED.md`](2ASYE-T-DONGLE-S3-atn-test-report.pdf.ARCHIVED.md) | 1,762,022 | Test Report |
-| [`2ASYE-T-DONGLE-S3-external-photos.pdf.ARCHIVED.md`](2ASYE-T-DONGLE-S3-external-photos.pdf.ARCHIVED.md) | 2,636,746 | External Photos |
-| [`2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf.ARCHIVED.md`](2ASYE-T-DONGLE-S3-rf-exposure-info-1.pdf.ARCHIVED.md) | 100,065 | RF Exposure Info |
-| [`2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf.ARCHIVED.md`](2ASYE-T-DONGLE-S3-rf-exposure-info-2.pdf.ARCHIVED.md) | 100,039 | RF Exposure Info |
-| [`2ASYE-T-DONGLE-S3-users-manual.pdf.ARCHIVED.md`](2ASYE-T-DONGLE-S3-users-manual.pdf.ARCHIVED.md) | 4,153,868 | Users Manual |
-
-Archived total: **5 files, 8.35 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 4.04 MiB** |
-| Archived | **5 files, 8.35 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t-dongle-s3/certification-and-compliance.md b/devices/lilygo/t-dongle-s3/certification-and-compliance.md
deleted file mode 100644
index 8f51245..0000000
--- a/devices/lilygo/t-dongle-s3/certification-and-compliance.md
+++ /dev/null
@@ -1,123 +0,0 @@
-# Certification and compliance — t-dongle-s3
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-T-DONGLE-S3` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-DONGLE-S3`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2023-11-30** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2023-11-30 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 18 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-DONGLE-S3` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 2,636,746 | `33ff03496c1b655b…` |
-| `ID-Label-Location-Info-ID-Label-Location-Info.pdf` | 777,839 | `89d39b990c0b5050…` |
-| `Internal-Photos-Internal-Photos.pdf` | 3,459,994 | `2cfbd440fb850ab9…` |
-| `RF-Exposure-Info-RF-Exposure-Info-1.pdf` | 100,065 | `f1cd62088f4aea03…` |
-| `RF-Exposure-Info-RF-Exposure-Info-2.pdf` | 100,039 | `63c30902c6cb6a87…` |
-| `Test-Report-ATN-Test-Report.pdf` | 1,762,022 | `36babccf0bc6ff3b…` |
-| `Users-Manual-Users-Manual.pdf` | 4,153,868 | `fb45d5c270467b10…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-DONGLE-S3/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-DONGLE-S3/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-dongle-s3/market-and-pricing.md b/devices/lilygo/t-dongle-s3/market-and-pricing.md
deleted file mode 100644
index fe3c451..0000000
--- a/devices/lilygo/t-dongle-s3/market-and-pricing.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Market and pricing — t-dongle-s3
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-Dongle S3 | 2022-10-20 | T-Dongle S3 / China [For Worldwide] / With LCD [K193] | `K193` | **USD 11.99** | ✅ yes |
-| T-Dongle S3 | 2022-10-20 | T-Dongle S3 / China [For Worldwide] / Without LCD [K194/ K194-B] | `K194` | **USD 10.99** | ✅ yes |
-| T-Dongle S3 | 2022-10-20 | T-Dongle S3 / China [For Worldwide] / Without LCD External Antenna [K194-01] | `K194-01` | **USD 10.99** | ✅ yes |
-| T-Dongle S3 | 2022-10-20 | T-Dongle S3 / Germany [ For Europe only] / With LCD [K193] | `K193DE` | **USD 16.49** | ✅ yes |
-| T-Dongle S3 | 2022-10-20 | T-Dongle S3 / United States [For US only] / With LCD [K193] | `USK193` | **USD 16.49** | ❌ no |
-| T-Dongle S3 | 2022-10-20 | T-Dongle S3 Dual / China [For Worldwide] / Without LCD [K194/ K194-B] | `K194-B` | **USD 14.96** | ✅ yes |
-| T-Dongle C5 | 2026-01-28 | China [For Worldwide] / With Screen [K193-A] | `K193-A` | **USD 13.98** | ✅ yes |
-| T-Dongle C5 | 2026-01-28 | China [For Worldwide] / Without Screen [K194-A] | `K194-A` | **USD 13.02** | ✅ yes |
-| T-Dongle C5 | 2026-01-28 | Germany [ For Europe only] / With Screen [K193-A] | `DEK193-A` | **USD 18.48** | ✅ yes |
-| T-Dongle C5 | 2026-01-28 | United States [For US only] / With Screen [K193-A] | `USK193-A` | **USD 18.48** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 11.99, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-dongle-s3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-`K193` with LCD USD 11.99, `K194` without USD 10.99. **T-Dongle C5 is a different product** (ESP32-C5), listed for contrast only.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t-qt/README.md b/devices/lilygo/t-qt/README.md
deleted file mode 100644
index cab49a9..0000000
--- a/devices/lilygo/t-qt/README.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# LilyGO T-QT — lineage stub
-
-> **Stub record.** Included because the brief names it as a family relative; it is a
-> *cousin*, not a T-Display-S3 variant. Store: **T-QT Pro** handle `t-qt-pro`, published
-> 2022-09-21, from **USD 9.05**; **T-QT C6** handle `t-qt-c6`, published 2024-06-13, from
-> **USD 13.25**. Both in stock 2026-09-07.
-> Repo `Xinyuan-LilyGO/T-QT` @ **`230f0c0ea7677fdde29ca7a49a419dbf597e6b3e`**, MIT, 149★.
-> Research retrieved 2026-09-07. No hardware.
-
-## Identity
-
-| | | Source |
-|---|---|---|
-| Format | a thumbnail-sized board — LilyGO describes T-QT C6 as *"only the size of two thumbnails"* | repo description |
-| T-QT Pro | ESP32-S3, 0.85″ **128 × 128** TFT on SPI | store, repo |
-| T-QT C6 | **ESP32-C6**, 128 × 128 **touch** TFT, separate charging LED, power-path-management chip with programmable bus limits | repo description @ 2026-09-03 |
-| Pins (T-QT S3, ESP-IDF) | `SPI MOSI 2 / SCK 3`, `TFT_CS 5 / RST 1 / DC 6 / BL 10`; `POWERON 10` is present but **commented out** | `LilyGo-Display-IDF/main/product_pins.h`, `#elif CONFIG_LILYGO_T_QT_S3` @ `b1a1cc5` |
-
-## Relationship to the T-Display-S3
-
-Same vendor, same era, same `LilyGo-Display-IDF` support tree, same Arduino-core pinning
-culture — and **no shared PCB, panel, bus or pin map**. It is in this repository's LilyGO tree
-because a reader enumerating "the T-Display family" will encounter it and should be able to
-rule it out quickly.
-
-The one genuinely transferable observation: `product_pins.h` shows a `BOARD_POWERON` define
-**commented out** for the T-QT, where the T-Display and T-Display-S3 both have one active. The
-power-gate pattern is a LilyGO habit that appears and disappears across the catalogue, which is
-why "does this board have a power-enable pin?" must be answered per board rather than assumed.
-
-## Gaps
-
-**Stub.** No schematic retrieved, no artifacts, no component records created, no market
-analysis. The T-QT C6's power-path chip is not identified. Documented only to the depth needed
-to place it in the family and rule it out.
diff --git a/devices/lilygo/t-qt/acquisition/manifest.json b/devices/lilygo/t-qt/acquisition/manifest.json
deleted file mode 100644
index 2c78f7e..0000000
--- a/devices/lilygo/t-qt/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "devices/lilygo/t-qt",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2ASYE-T-QT-PRO-6304972",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-QT-PRO/Test-Report/Antenna-Report-6304972.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304972",
-    "https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304972.pdf",
-    "https://fccid.io/2ASYE-T-QT-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/Test-Report/Antenna-Report-6304972.pdf"
-   ],
-   "sha256": "9feb27607d52592982ea3645db1285c9be73c79884442a7140e9346317f5a181",
-   "bytes": 667906,
-   "destination": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-12-31",
-   "fcc_id": "2ASYE-T-QT-PRO",
-   "fcc_document_id": "6304972",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Report",
-   "grant_date": "2022-12-31",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf",
-   "placeholder": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-qt",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-QT-PRO-6304979",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-QT-PRO/Label/E-Label-Information-6304979.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304979",
-    "https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304979.pdf",
-    "https://fccid.io/2ASYE-T-QT-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/Label/E-Label-Information-6304979.pdf"
-   ],
-   "sha256": "0f023a387208fa1be60d25a2d46a05e9a22c790685008966ee9d0ebda9a8fe0e",
-   "bytes": 791402,
-   "destination": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-e-label-information.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-12-31",
-   "fcc_id": "2ASYE-T-QT-PRO",
-   "fcc_document_id": "6304979",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "E-Label Information",
-   "grant_date": "2022-12-31",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-qt",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-QT-PRO-6304969",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-QT-PRO/External-Photos/External-Photos-6304969.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304969",
-    "https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304969.pdf",
-    "https://fccid.io/2ASYE-T-QT-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/External-Photos/External-Photos-6304969.pdf"
-   ],
-   "sha256": "a6424be9d8f42f8afbe2a0e576af45417a8fad3d9dcac100e8387760bd711853",
-   "bytes": 199661,
-   "destination": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-12-31",
-   "fcc_id": "2ASYE-T-QT-PRO",
-   "fcc_document_id": "6304969",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2022-12-31",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf",
-   "placeholder": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-qt",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-QT-PRO-6304970",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-QT-PRO/Internal-Photos/Internal-Photos-6304970.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304970",
-    "https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304970.pdf",
-    "https://fccid.io/2ASYE-T-QT-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/Internal-Photos/Internal-Photos-6304970.pdf"
-   ],
-   "sha256": "eaa10d9bc4199d8afc32c60775b22a332b3ec2b58a586705daba896410c2cc73",
-   "bytes": 1899930,
-   "destination": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-12-31",
-   "fcc_id": "2ASYE-T-QT-PRO",
-   "fcc_document_id": "6304970",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2022-12-31",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-qt",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-QT-PRO-6304974",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-QT-PRO/RF-Exposure-Info/RF-Exposure-6304974.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304974",
-    "https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304974.pdf",
-    "https://fccid.io/2ASYE-T-QT-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/RF-Exposure-Info/RF-Exposure-6304974.pdf"
-   ],
-   "sha256": "d22c52193b7daeb66039f1980f72e38f486522d39dec3b179cd135ad24d2777f",
-   "bytes": 186288,
-   "destination": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-12-31",
-   "fcc_id": "2ASYE-T-QT-PRO",
-   "fcc_document_id": "6304974",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure",
-   "grant_date": "2022-12-31",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf",
-   "placeholder": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-qt",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T-QT-PRO-6304978",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T-QT-PRO/User-Manual/User-Manual-6304978.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304978",
-    "https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304978.pdf",
-    "https://fccid.io/2ASYE-T-QT-PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/User-Manual/User-Manual-6304978.pdf"
-   ],
-   "sha256": "47d4e969e92a0a6c1f7f5442442d8bc2ae36efb86ad05fc16713db518e790e1c",
-   "bytes": 1157930,
-   "destination": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2022-12-31",
-   "fcc_id": "2ASYE-T-QT-PRO",
-   "fcc_document_id": "6304978",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2022-12-31",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf",
-   "placeholder": "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t-qt",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf.ARCHIVED.md b/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf.ARCHIVED.md
deleted file mode 100644
index 54ede3a..0000000
--- a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-QT-PRO-antenna-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 667,906 B (0.64 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 667,906 B (0.64 MiB) |
-| SHA-256 | `9feb27607d52592982ea3645db1285c9be73c79884442a7140e9346317f5a181` |
-| FCC ID | **`2ASYE-T-QT-PRO`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Report |
-| FCC document id | 6304972 |
-| Upstream publication date | 2022-12-31 |
-| Grant date | 2022-12-31 |
-| Equipment class | T-QT Pro, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-QT-PRO/Test-Report/Antenna-Report-6304972.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304972>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304972.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-QT-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/Test-Report/Antenna-Report-6304972.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf" \
-   "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-antenna-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-QT-PRO/Test-Report/Antenna-Report-6304972.pdf" -o "2ASYE-T-QT-PRO-antenna-report.pdf"
-echo "9feb27607d52592982ea3645db1285c9be73c79884442a7140e9346317f5a181  2ASYE-T-QT-PRO-antenna-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-e-label-information.pdf b/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-e-label-information.pdf
deleted file mode 100644
index aa1e5dd..0000000
Binary files a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-e-label-information.pdf and /dev/null differ
diff --git a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index d238cbb..0000000
--- a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-QT-PRO-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 199,661 B (0.19 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 199,661 B (0.19 MiB) |
-| SHA-256 | `a6424be9d8f42f8afbe2a0e576af45417a8fad3d9dcac100e8387760bd711853` |
-| FCC ID | **`2ASYE-T-QT-PRO`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 6304969 |
-| Upstream publication date | 2022-12-31 |
-| Grant date | 2022-12-31 |
-| Equipment class | T-QT Pro, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-QT-PRO/External-Photos/External-Photos-6304969.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304969>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304969.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-QT-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/External-Photos/External-Photos-6304969.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf" \
-   "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-QT-PRO/External-Photos/External-Photos-6304969.pdf" -o "2ASYE-T-QT-PRO-external-photos.pdf"
-echo "a6424be9d8f42f8afbe2a0e576af45417a8fad3d9dcac100e8387760bd711853  2ASYE-T-QT-PRO-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-internal-photos.pdf b/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-internal-photos.pdf
deleted file mode 100644
index 4ca2640..0000000
Binary files a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf.ARCHIVED.md b/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf.ARCHIVED.md
deleted file mode 100644
index f5f6977..0000000
--- a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-QT-PRO-rf-exposure.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 186,288 B (0.18 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 186,288 B (0.18 MiB) |
-| SHA-256 | `d22c52193b7daeb66039f1980f72e38f486522d39dec3b179cd135ad24d2777f` |
-| FCC ID | **`2ASYE-T-QT-PRO`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure |
-| FCC document id | 6304974 |
-| Upstream publication date | 2022-12-31 |
-| Grant date | 2022-12-31 |
-| Equipment class | T-QT Pro, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-QT-PRO/RF-Exposure-Info/RF-Exposure-6304974.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304974>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304974.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-QT-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/RF-Exposure-Info/RF-Exposure-6304974.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf" \
-   "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-rf-exposure.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-QT-PRO/RF-Exposure-Info/RF-Exposure-6304974.pdf" -o "2ASYE-T-QT-PRO-rf-exposure.pdf"
-echo "d22c52193b7daeb66039f1980f72e38f486522d39dec3b179cd135ad24d2777f  2ASYE-T-QT-PRO-rf-exposure.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf.ARCHIVED.md b/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 85615bd..0000000
--- a/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T-QT-PRO-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,157,930 B (1.10 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,157,930 B (1.10 MiB) |
-| SHA-256 | `47d4e969e92a0a6c1f7f5442442d8bc2ae36efb86ad05fc16713db518e790e1c` |
-| FCC ID | **`2ASYE-T-QT-PRO`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 6304978 |
-| Upstream publication date | 2022-12-31 |
-| Grant date | 2022-12-31 |
-| Equipment class | T-QT Pro, 2402-2480 MHz, 2412-2472 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T-QT-PRO/User-Manual/User-Manual-6304978.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6304978>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T-QT-PRO/6304978.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T-QT-PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T-QT-PRO/User-Manual/User-Manual-6304978.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf" \
-   "devices/lilygo/t-qt/artifacts/certification/2ASYE-T-QT-PRO-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T-QT-PRO/User-Manual/User-Manual-6304978.pdf" -o "2ASYE-T-QT-PRO-user-manual.pdf"
-echo "47d4e969e92a0a6c1f7f5442442d8bc2ae36efb86ad05fc16713db518e790e1c  2ASYE-T-QT-PRO-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t-qt/artifacts/certification/README.md b/devices/lilygo/t-qt/artifacts/certification/README.md
deleted file mode 100644
index 0884ba9..0000000
--- a/devices/lilygo/t-qt/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-T-QT-PRO`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-T-QT-PRO`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2022-12-31** |
-| Equipment class | T-QT Pro, 2402-2480 MHz, 2412-2472 MHz |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Source page | <https://fccid.io/2ASYE-T-QT-PRO> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-T-QT-PRO-e-label-information.pdf` | 791,402 | `0f023a387208fa1be60d25a2d46a05e9a22c790685008966ee9d0ebda9a8fe0e` | ID Label/Location Info |
-| `2ASYE-T-QT-PRO-internal-photos.pdf` | 1,899,930 | `eaa10d9bc4199d8afc32c60775b22a332b3ec2b58a586705daba896410c2cc73` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-T-QT-PRO-antenna-report.pdf.ARCHIVED.md`](2ASYE-T-QT-PRO-antenna-report.pdf.ARCHIVED.md) | 667,906 | Test Report |
-| [`2ASYE-T-QT-PRO-external-photos.pdf.ARCHIVED.md`](2ASYE-T-QT-PRO-external-photos.pdf.ARCHIVED.md) | 199,661 | External Photos |
-| [`2ASYE-T-QT-PRO-rf-exposure.pdf.ARCHIVED.md`](2ASYE-T-QT-PRO-rf-exposure.pdf.ARCHIVED.md) | 186,288 | RF Exposure Info |
-| [`2ASYE-T-QT-PRO-user-manual.pdf.ARCHIVED.md`](2ASYE-T-QT-PRO-user-manual.pdf.ARCHIVED.md) | 1,157,930 | Users Manual |
-
-Archived total: **4 files, 2.11 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 2.57 MiB** |
-| Archived | **4 files, 2.11 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t-qt/certification-and-compliance.md b/devices/lilygo/t-qt/certification-and-compliance.md
deleted file mode 100644
index 93672c5..0000000
--- a/devices/lilygo/t-qt/certification-and-compliance.md
+++ /dev/null
@@ -1,124 +0,0 @@
-# Certification and compliance — t-qt
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-The grant is named 'T-QT Pro'. The store sells T-QT Pro and T-QT C6; **only the Pro is granted**.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-T-QT-PRO` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T-QT-PRO`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2412-2472 MHz Original Equipment 2022-12-31** |
-| Application purpose | Final Action Date 2412-2472 MHz Original Equipment 2022-12-31 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2472 MHz** (Wi-Fi 2.4 GHz, ch 1–13 — ⚠ wider than the usual US 1–11) |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 10 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T-QT-PRO` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 199,661 | `a6424be9d8f42f8a…` |
-| `ID-Label-Location-Info-E-Label-Information.pdf` | 791,402 | `0f023a387208fa1b…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,899,930 | `eaa10d9bc4199d8a…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 186,288 | `d22c52193b7daeb6…` |
-| `Test-Report-Antenna-Report.pdf` | 667,906 | `9feb27607d525929…` |
-| `Users-Manual-User-Manual.pdf` | 1,157,930 | `47d4e969e92a0a6c…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T-QT-PRO/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T-QT-PRO/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t-qt/market-and-pricing.md b/devices/lilygo/t-qt/market-and-pricing.md
deleted file mode 100644
index 5d7ee5f..0000000
--- a/devices/lilygo/t-qt/market-and-pricing.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# Market and pricing — t-qt
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T-QT Pro | 2022-09-21 | ESP32-S3FN4R2 [H579] | `H579` | **USD 9.05** | ✅ yes |
-| T-QT Pro | 2022-09-21 | S3FN4R2 Solder PIN [H590] | `H590` | **USD 9.48** | ✅ yes |
-| T-QT Pro | 2022-09-21 | S3FN4R2 With Shell [K192] | `K192` | **USD 11.50** | ✅ yes |
-| T-QT Pro | 2022-09-21 | ESP32-S3FN8 Solder Pin [H628] | `H628` | **USD 10.35** | ✅ yes |
-| T-QT Pro | 2022-09-21 | ESP32-S3FN8 Not Solder Pin [H588] | `H588` | **USD 10.05** | ✅ yes |
-| T-QT Pro | 2022-09-21 | S3N8 With Shell [K191] | `K191` | **USD 11.88** | ✅ yes |
-| T-QT Pro | 2022-09-21 | Only Shell [L926] | `L926` | **USD 2.00** | ✅ yes |
-| T-QT C6 | 2024-06-13 | China [For Worldwide] / T-QT C6 With Ring [H714-01] | `H714-01` | **USD 21.47** | ✅ yes |
-| T-QT C6 | 2024-06-13 | China [For Worldwide] / T-QT C6 [H714] | `H714` | **USD 13.25** | ✅ yes |
-| T-QT C6 | 2024-06-13 | China [For Worldwide] / T-QT C6 With Ring (Non-Soldered ) [H714-02] | `H714-02` | **USD 21.47** | ✅ yes |
-| T-QT C6 | 2024-06-13 | Germany [ For Europe only] / T-QT C6 [H714] | `H714DE` | **USD 18.23** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 9.05, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t-qt-pro`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-⚠ **Two distinct products.** T-QT **Pro** (ESP32-S3) USD 9.05–11.88 across 4R2/N8/shell variants; T-QT **C6** (ESP32-C6) USD 13.25–21.47. Only the Pro is FCC-granted. `L926` USD 2.00 is a shell.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/lilygo/t4-s3/README.md b/devices/lilygo/t4-s3/README.md
deleted file mode 100644
index 86847b5..0000000
--- a/devices/lilygo/t4-s3/README.md
+++ /dev/null
@@ -1,100 +0,0 @@
-# LilyGO T4-S3 (2.41″ AMOLED)
-
-> **This is the board people mean by "T-Display-S3 AMOLED 2.41″".** LilyGO does **not** call it
-> that. Store handle **`t4-s3`**, title *T4 S3*, published **2023-11-03**.
-> SKUs `H678` basic **USD 56.89**, `H724` shell+soldered **60.23**, `H711` shell+female header
-> **58.99** (US **63.49**). In stock 2026-09-07.
->
-> Covered by `LilyGo-AMOLED-Series` @ **`6d1dc008b94578cc34ba4a0f3b223dd808ca963f`**.
-> Research retrieved 2026-09-07. **Depth: medium.** No hardware.
-> Part of the [T-Display-S3 family](../t-display-s3-shared/README.md) by library and lineage,
-> not by name.
-
-## Identity
-
-| | | Source |
-|---|---|---|
-| Panel | 2.41″ AMOLED, **450 × 600**, **550 nits** — the brightest and largest in the family | `LilyGo-AMOLED-Series` README @ `6d1dc00` |
-| Display driver | **Raydium RM690B0** | vendor datasheet `RM690B0 DataSheet_V0.2.pdf` ships in the repo |
-| Touch | **Hynitron CST226SE** | vendor README links the CST226 manual |
-| PMIC `U5` | **Silergy SY6970** | schematic designator census |
-| SoC `U2` | **ESP32-S3R8**, 16 MB flash (`U3` W25Q128), 8 MB OPI PSRAM | schematic + README |
-| Other silicon | `SY8089` buck, `BV6804` (unidentified family), `ULC0511C`, `AO3400` FET, `LTR`-marked ambient-light part | schematic designator census |
-| Storage | **microSD**, SPI: `GPIO1 SD_CS`, `GPIO2 SD_MOSI`, `GPIO3 SD_SCK`, `GPIO4 SD_MISO` (net labels drawn on the sheet) | schematic |
-| Component records | [`raydium/rm690b0`](../../../components/raydium/rm690b0/README.md) · [`hynitron/cst226se`](../../../components/hynitron/cst226se/README.md) · [`silergy/sy6970`](../../../components/silergy/sy6970/README.md) |
-
-## Pinout
-
-From `LilyGo-Display-IDF/main/product_pins.h`, block `#elif CONFIG_LILYGO_T4_S3_241`
-@ **`b1a1cc54994bf1b417e3bb30c437bbe1036bff7f`**:
-
-| Signal | GPIO |
-|---|---|
-| `DISP_CS` / `SCK` | 11 / 15 |
-| `DISP_DATA0..3` | 14, 10, 16, 12 |
-| `DISP_RESET` | 13 |
-| `DISP_TE` | −1 (not wired) |
-| `I2C_SDA` / `SCL` | 6 / 7 |
-| `TOUCH_IRQ` / `TOUCH_RST` | 8 / 17 |
-| `SD_MISO/MOSI/SCLK/CS` | 4 / 2 / 3 / 1 |
-| `BOOT` / `BUTTON1` | 0 / 0 |
-
-**ESPHome disagrees on the QSPI pins.** Its `T4-S3` model gives
-`cs_pin=11, reset_pin=13, enable_pin=9, offset_width=16, width=450` — `cs` and `reset` match,
-but it adds an `enable_pin=9` that `product_pins.h` does not mention, and `offset_width=16`
-(the RM690B0 is 480 wide; 450 sits at column 16). Recorded as a conflict below.
-
-**⚠ Vendor warning, verbatim from the library README:**
-> "`T4-S3` **GPIO18** has been assigned to the display TE Pin, please do not use this Pin"
-
-— which contradicts `product_pins.h`'s `BOARD_DISP_TE (-1)`. Two vendor sources, one file and
-one README, disagree about whether TE is wired.
-
-## Software
-
-- **`LilyGo-AMOLED-Series`** auto-detects it. `examples/PPM_Example_for_T4S3` is the
-  SY6970 example; `TFT_eSPI_Sprite_Rotation` and `LVGL_Rotation` note that hardware rotation is
-  available "only for 1.91, 2.41 inches" — i.e. this board and the 1.91″ AMOLED, not the Lite.
-- **ESPHome**: model `T4-S3`, extending `RM690B0`, `bus_mode=QUAD`, `requires psram`.
-- `TFT_eSPI` cannot drive it (QSPI).
-
-## Power
-
-Vendor figures @ `6d1dc00`: **90–230+ mA** active, **≈230 µA** deep sleep with GPIO0 wake.
-
-## Artifacts
-
-`artifacts/schematic/T4-S3-240719.pdf` — 530 032 B,
-SHA-256 `3d3831d215eb5e89c354c8a3677c929c98f6675e5be51d10a15997b3d90f79b3`, retrieved 2026-09-07
-at `6d1dc00`. The filename's `240719` is a **2024-07-19** date stamp.
-
-**A note on reading it.** This PDF uses Type0/Identity-H subset fonts with `/ToUnicode` CMaps —
-unlike every other LilyGO schematic, which use WinAnsi TrueType. A text extractor that works on
-the others returns **nothing** here. Recorded in
-[`vendors/lilygo/README.md`](../../../vendors/lilygo/README.md).
-
-RM690B0 and CST226 datasheets are filed under their components.
-
-## Sources
-
-| ID | Source | Class | Retrieved |
-|---|---|---|---|
-| T4-1 | `LilyGo-AMOLED-Series` README.MD @ `6d1dc00` | primary | 2026-09-07 |
-| T4-2 | `schematic/T4-S3-240719.pdf` @ `6d1dc00` | primary | 2026-09-07 |
-| T4-3 | `LilyGo-Display-IDF/main/product_pins.h` @ `b1a1cc5` | primary | 2026-09-07 |
-| T4-4 | `esphome/components/mipi_spi/models/amoled.py`, `dev` | primary (third-party) | 2026-09-07 |
-| T4-5 | LilyGO store feed | primary | 2026-09-07 |
-
-## Conflicts
-
-| # | Item | Status |
-|---|---|---|
-| T4-C1 | **Is TE wired?** README says GPIO18 is the display TE and must not be used; `product_pins.h` says `BOARD_DISP_TE (-1)` | **Unresolved.** Safest reading: treat GPIO18 as reserved |
-| T4-C2 | **`enable_pin=9`** appears in ESPHome and in no vendor source | **Unresolved** |
-| T4-C3 | `BV6804`, `ULC0511C` unidentified | **Open** |
-| T4-C4 | The name. Marketed as *T4-S3*; grouped with T-Display-S3 boards by library, README table and lineage | recorded, not a defect |
-
-## Gaps
-
-Medium-depth stub: no `features/`, no example catalogue, no acquisition manifest, no GPIO
-census beyond the display/touch/SD block above. Net connectivity not traced. No hardware.
diff --git a/devices/lilygo/t4-s3/acquisition/manifest.json b/devices/lilygo/t4-s3/acquisition/manifest.json
deleted file mode 100644
index 01fe130..0000000
--- a/devices/lilygo/t4-s3/acquisition/manifest.json
+++ /dev/null
@@ -1,260 +0,0 @@
-{
- "record": "devices/lilygo/t4-s3",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2ASYE-T4-S3-241-7140045",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T4-S3-241/Test-Report/Antenna-Specification-7140045.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140045",
-    "https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140045.pdf",
-    "https://fccid.io/2ASYE-T4-S3-241",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/Test-Report/Antenna-Specification-7140045.pdf"
-   ],
-   "sha256": "a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62",
-   "bytes": 1174923,
-   "destination": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-27",
-   "fcc_id": "2ASYE-T4-S3-241",
-   "fcc_document_id": "7140045",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Specification",
-   "grant_date": "2024-02-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf",
-   "placeholder": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t4-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T4-S3-241-7140032",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T4-S3-241/External-Photos/External-Photos-7140032.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140032",
-    "https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140032.pdf",
-    "https://fccid.io/2ASYE-T4-S3-241",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/External-Photos/External-Photos-7140032.pdf"
-   ],
-   "sha256": "18969bc229faadde0fe6ef61ab2484026b63179d53e12aebe581ff2c57057ede",
-   "bytes": 765158,
-   "destination": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-27",
-   "fcc_id": "2ASYE-T4-S3-241",
-   "fcc_document_id": "7140032",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2024-02-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf",
-   "placeholder": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t4-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T4-S3-241-7140033",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T4-S3-241/Internal-Photos/Internal-Photos-7140033.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140033",
-    "https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140033.pdf",
-    "https://fccid.io/2ASYE-T4-S3-241",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/Internal-Photos/Internal-Photos-7140033.pdf"
-   ],
-   "sha256": "3dbcb6171dd1904eead48e8b727991ab5d6d1ecda5fc3011ce31687fbade4073",
-   "bytes": 983085,
-   "destination": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-27",
-   "fcc_id": "2ASYE-T4-S3-241",
-   "fcc_document_id": "7140033",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2024-02-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t4-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T4-S3-241-7140049",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T4-S3-241/Label/Label-Label-Location-7140049.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140049",
-    "https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140049.pdf",
-    "https://fccid.io/2ASYE-T4-S3-241",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/Label/Label-Label-Location-7140049.pdf"
-   ],
-   "sha256": "7fcd4d856c5a08597a208e3e17721884abedaeb9db0201545a6fe4f8bc302797",
-   "bytes": 370771,
-   "destination": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-label-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-27",
-   "fcc_id": "2ASYE-T4-S3-241",
-   "fcc_document_id": "7140049",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label & Label Location",
-   "grant_date": "2024-02-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t4-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T4-S3-241-7140044",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-BLE-7140044.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140044",
-    "https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140044.pdf",
-    "https://fccid.io/2ASYE-T4-S3-241",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-BLE-7140044.pdf"
-   ],
-   "sha256": "dc70b64ee5e417341ba2fcec10909facdefd3b235afdde596f0f0dd29f70d6ea",
-   "bytes": 146101,
-   "destination": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-27",
-   "fcc_id": "2ASYE-T4-S3-241",
-   "fcc_document_id": "7140044",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure - BLE",
-   "grant_date": "2024-02-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf",
-   "placeholder": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t4-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T4-S3-241-7140043",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-WiFi-7140043.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140043",
-    "https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140043.pdf",
-    "https://fccid.io/2ASYE-T4-S3-241",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-WiFi-7140043.pdf"
-   ],
-   "sha256": "96c6adb398c1ccce799634650d36f1e086c5d69fe7f911116d8a70b9c82bcbaf",
-   "bytes": 146127,
-   "destination": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-27",
-   "fcc_id": "2ASYE-T4-S3-241",
-   "fcc_document_id": "7140043",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure - WiFi",
-   "grant_date": "2024-02-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf",
-   "placeholder": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t4-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2ASYE-T4-S3-241-7140048",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2ASYE-T4-S3-241/User-Manual/User-Manual-7140048.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140048",
-    "https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140048.pdf",
-    "https://fccid.io/2ASYE-T4-S3-241",
-    "https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/User-Manual/User-Manual-7140048.pdf"
-   ],
-   "sha256": "392e0deb78d4e31dbfe2159ccad86d02706b9faf9e0435224c6001e517a6cca0",
-   "bytes": 1308927,
-   "destination": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-02-27",
-   "fcc_id": "2ASYE-T4-S3-241",
-   "fcc_document_id": "7140048",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2024-02-27",
-   "applicant": "Shenzhen Xin Yuan Electronic Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "CHINA CERTIFICATION ICT CO., LTD (DONGGUAN)",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf",
-   "placeholder": "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/lilygo/t4-s3",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf.ARCHIVED.md b/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 6a6eb80..0000000
--- a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T4-S3-241-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,174,923 B (1.12 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,174,923 B (1.12 MiB) |
-| SHA-256 | `a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62` |
-| FCC ID | **`2ASYE-T4-S3-241`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 7140045 |
-| Upstream publication date | 2024-02-27 |
-| Grant date | 2024-02-27 |
-| Equipment class | T4-S3-2.41, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T4-S3-241/Test-Report/Antenna-Specification-7140045.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140045>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140045.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T4-S3-241>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/Test-Report/Antenna-Specification-7140045.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf" \
-   "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T4-S3-241/Test-Report/Antenna-Specification-7140045.pdf" -o "2ASYE-T4-S3-241-antenna-specification.pdf"
-echo "a1300af9d0563dac28683bee8dde89072a7d3b71117ef48c95cff16e70dabc62  2ASYE-T4-S3-241-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf.ARCHIVED.md b/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 87a3cf7..0000000
--- a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T4-S3-241-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 765,158 B (0.73 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 765,158 B (0.73 MiB) |
-| SHA-256 | `18969bc229faadde0fe6ef61ab2484026b63179d53e12aebe581ff2c57057ede` |
-| FCC ID | **`2ASYE-T4-S3-241`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 7140032 |
-| Upstream publication date | 2024-02-27 |
-| Grant date | 2024-02-27 |
-| Equipment class | T4-S3-2.41, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T4-S3-241/External-Photos/External-Photos-7140032.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140032>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140032.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T4-S3-241>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/External-Photos/External-Photos-7140032.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf" \
-   "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T4-S3-241/External-Photos/External-Photos-7140032.pdf" -o "2ASYE-T4-S3-241-external-photos.pdf"
-echo "18969bc229faadde0fe6ef61ab2484026b63179d53e12aebe581ff2c57057ede  2ASYE-T4-S3-241-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-internal-photos.pdf b/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-internal-photos.pdf
deleted file mode 100644
index 3ffb0f7..0000000
Binary files a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-internal-photos.pdf and /dev/null differ
diff --git a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-label-label-location.pdf b/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-label-label-location.pdf
deleted file mode 100644
index 1b16805..0000000
Binary files a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-label-label-location.pdf and /dev/null differ
diff --git a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf.ARCHIVED.md b/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf.ARCHIVED.md
deleted file mode 100644
index 4fd0e03..0000000
--- a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T4-S3-241-rf-exposure-ble.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 146,101 B (0.14 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 146,101 B (0.14 MiB) |
-| SHA-256 | `dc70b64ee5e417341ba2fcec10909facdefd3b235afdde596f0f0dd29f70d6ea` |
-| FCC ID | **`2ASYE-T4-S3-241`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure - BLE |
-| FCC document id | 7140044 |
-| Upstream publication date | 2024-02-27 |
-| Grant date | 2024-02-27 |
-| Equipment class | T4-S3-2.41, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-BLE-7140044.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140044>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140044.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T4-S3-241>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-BLE-7140044.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf" \
-   "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-ble.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-BLE-7140044.pdf" -o "2ASYE-T4-S3-241-rf-exposure-ble.pdf"
-echo "dc70b64ee5e417341ba2fcec10909facdefd3b235afdde596f0f0dd29f70d6ea  2ASYE-T4-S3-241-rf-exposure-ble.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf.ARCHIVED.md b/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf.ARCHIVED.md
deleted file mode 100644
index a8e106e..0000000
--- a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T4-S3-241-rf-exposure-wifi.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 146,127 B (0.14 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 146,127 B (0.14 MiB) |
-| SHA-256 | `96c6adb398c1ccce799634650d36f1e086c5d69fe7f911116d8a70b9c82bcbaf` |
-| FCC ID | **`2ASYE-T4-S3-241`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure - WiFi |
-| FCC document id | 7140043 |
-| Upstream publication date | 2024-02-27 |
-| Grant date | 2024-02-27 |
-| Equipment class | T4-S3-2.41, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-WiFi-7140043.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140043>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140043.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T4-S3-241>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-WiFi-7140043.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf" \
-   "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-rf-exposure-wifi.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T4-S3-241/RF-Exposure-Info/RF-Exposure-WiFi-7140043.pdf" -o "2ASYE-T4-S3-241-rf-exposure-wifi.pdf"
-echo "96c6adb398c1ccce799634650d36f1e086c5d69fe7f911116d8a70b9c82bcbaf  2ASYE-T4-S3-241-rf-exposure-wifi.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf.ARCHIVED.md b/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 13492d9..0000000
--- a/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2ASYE-T4-S3-241-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,308,927 B (1.25 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,308,927 B (1.25 MiB) |
-| SHA-256 | `392e0deb78d4e31dbfe2159ccad86d02706b9faf9e0435224c6001e517a6cca0` |
-| FCC ID | **`2ASYE-T4-S3-241`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 7140048 |
-| Upstream publication date | 2024-02-27 |
-| Grant date | 2024-02-27 |
-| Equipment class | T4-S3-2.41, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2ASYE-T4-S3-241/User-Manual/User-Manual-7140048.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7140048>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2ASYE-T4-S3-241/7140048.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2ASYE-T4-S3-241>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2ASYE-T4-S3-241/User-Manual/User-Manual-7140048.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf" \
-   "devices/lilygo/t4-s3/artifacts/certification/2ASYE-T4-S3-241-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2ASYE-T4-S3-241/User-Manual/User-Manual-7140048.pdf" -o "2ASYE-T4-S3-241-user-manual.pdf"
-echo "392e0deb78d4e31dbfe2159ccad86d02706b9faf9e0435224c6001e517a6cca0  2ASYE-T4-S3-241-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/lilygo/t4-s3/artifacts/certification/README.md b/devices/lilygo/t4-s3/artifacts/certification/README.md
deleted file mode 100644
index 9af0b67..0000000
--- a/devices/lilygo/t4-s3/artifacts/certification/README.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# FCC equipment-authorization exhibits — `2ASYE-T4-S3-241`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2ASYE-T4-S3-241`** |
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. 🇨🇳 |
-| Granted | **2024-02-27** |
-| Equipment class | T4-S3-2.41, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Source page | <https://fccid.io/2ASYE-T4-S3-241> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2ASYE-T4-S3-241-internal-photos.pdf` | 983,085 | `3dbcb6171dd1904eead48e8b727991ab5d6d1ecda5fc3011ce31687fbade4073` | Internal Photos |
-| `2ASYE-T4-S3-241-label-label-location.pdf` | 370,771 | `7fcd4d856c5a08597a208e3e17721884abedaeb9db0201545a6fe4f8bc302797` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2ASYE-T4-S3-241-antenna-specification.pdf.ARCHIVED.md`](2ASYE-T4-S3-241-antenna-specification.pdf.ARCHIVED.md) | 1,174,923 | Test Report |
-| [`2ASYE-T4-S3-241-external-photos.pdf.ARCHIVED.md`](2ASYE-T4-S3-241-external-photos.pdf.ARCHIVED.md) | 765,158 | External Photos |
-| [`2ASYE-T4-S3-241-rf-exposure-ble.pdf.ARCHIVED.md`](2ASYE-T4-S3-241-rf-exposure-ble.pdf.ARCHIVED.md) | 146,101 | RF Exposure Info |
-| [`2ASYE-T4-S3-241-rf-exposure-wifi.pdf.ARCHIVED.md`](2ASYE-T4-S3-241-rf-exposure-wifi.pdf.ARCHIVED.md) | 146,127 | RF Exposure Info |
-| [`2ASYE-T4-S3-241-user-manual.pdf.ARCHIVED.md`](2ASYE-T4-S3-241-user-manual.pdf.ARCHIVED.md) | 1,308,927 | Users Manual |
-
-Archived total: **5 files, 3.38 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 1.29 MiB** |
-| Archived | **5 files, 3.38 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/lilygo/t4-s3/artifacts/schematic/T4-S3-240719.pdf b/devices/lilygo/t4-s3/artifacts/schematic/T4-S3-240719.pdf
deleted file mode 100644
index 0d852e5..0000000
Binary files a/devices/lilygo/t4-s3/artifacts/schematic/T4-S3-240719.pdf and /dev/null differ
diff --git a/devices/lilygo/t4-s3/certification-and-compliance.md b/devices/lilygo/t4-s3/certification-and-compliance.md
deleted file mode 100644
index a332c2e..0000000
--- a/devices/lilygo/t4-s3/certification-and-compliance.md
+++ /dev/null
@@ -1,178 +0,0 @@
-# Certification and compliance — t4-s3
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2ASYE-T4-S3-241` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AC7Z-ESPS3WROOM1`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2ASYE-T4-S3-241`
-
-| Field | Value |
-|---|---|
-| Applicant | Shenzhen Xin Yuan Electronic Technology Co., Ltd. (LilyGO) |
-| Grantee code | `2ASYE` — registered 2019-04-05, 33 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-02-27** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-02-27 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | CHINA CERTIFICATION ICT CO., LTD (DONGGUAN) |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2ASYE-T4-S3-241` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Circuit Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 765,158 | `18969bc229faadde…` |
-| `ID-Label-Location-Info-Label-Label-Location.pdf` | 370,771 | `7fcd4d856c5a0859…` |
-| `Internal-Photos-Internal-Photos.pdf` | 983,085 | `3dbcb6171dd1904e…` |
-| `RF-Exposure-Info-RF-Exposure---BLE.pdf` | 146,101 | `dc70b64ee5e41734…` |
-| `RF-Exposure-Info-RF-Exposure---WiFi.pdf` | 146,127 | `96c6adb398c1ccce…` |
-| `Test-Report-Antenna-Specification.pdf` | 1,174,923 | `a1300af9d0563dac…` |
-| `Users-Manual-User-Manual.pdf` | 1,308,927 | `392e0deb78d4e31d…` |
-
-Held at `scratch/market-and-certification/fcc/2ASYE-T4-S3-241/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2ASYE-T4-S3-241/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AC7Z-ESPS3WROOM1`
-
-| Field | Value |
-|---|---|
-| Applicant | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD |
-| Grantee code | `2AC7Z` — registered 2014-09-15, 78 FCC IDs total |
-| Final action date | **2026-02-27** |
-| Application purpose | Class II permissive change or modification of presently authorized equipment |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | SGS-CSTC Standards Technical Services Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 57 available, 11 metadata-only |
-| Filing page | `https://fccid.io/2AC7Z-ESPS3WROOM1` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Block diagram [Block Diagram]
-- Schematic [Schematics]
-- Schematics [Schematics]
-- Operation description [Operational Description]
-- Operational Description [Operational Description]
-- Parts list [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up [Parts List/Tune Up Info]
-- Tune up procedure [Parts List/Tune Up Info]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photo.pdf` | 1,367,037 | `a0104b88a862efd5…` |
-| `External-Photos-External-Photos.pdf` | 1,275,356 | `8fe953474e9707bc…` |
-| `External-Photos-External-photos.pdf` | 332,733 | `b04d392ae5298711…` |
-| `ID-Label-Location-Info-Label-location.pdf` | 30,758 | `68e843105466c162…` |
-| `ID-Label-Location-Info-Label.pdf` | 44,224 | `081ac1c0f3292f1b…` |
-| `ID-Label-Location-Info-Lable-and-location.pdf` | 1,437,286 | `0a57b90982013049…` |
-| `Internal-Photos-Internal-Photo.pdf` | 3,636,909 | `318d8c6c95232515…` |
-| `Internal-Photos-Internal-photos.pdf` | 338,977 | `1f60246b57db6172…` |
-| `RF-Exposure-Info-RF-Exposure.pdf` | 499,298 | `b1ae557e1e78bbfa…` |
-| `RF-Exposure-Info-SAR-Report-A.pdf` | 845,988 | `54f4972a02877d9b…` |
-| `RF-Exposure-Info-SAR-Report-B.pdf` | 850,218 | `62b4f82db50809aa…` |
-| `RF-Exposure-Info-SAR-Report-C1.pdf` | 5,908,102 | `8fbf6c55dc6a0248…` |
-| `RF-Exposure-Info-SAR-Report-C2.pdf` | 3,930,042 | `4c6ed64c435d4f04…` |
-| `RF-Exposure-Info-SAR-Report-D.pdf` | 3,974,985 | `04798068d0a5ee3b…` |
-| `RF-Exposure-Info-SAR-Report.pdf` | 1,936,491 | `60f7208dd54ccff8…` |
-| `Test-Report-Antenna-specification.pdf` | 1,996,381 | `da8da91adaa5b481…` |
-| `Users-Manual-User-Manual.pdf` | 2,603,588 | `3e493b8b9ea24f00…` |
-| `Users-Manual-User-manual.pdf` | 886,672 | `f8d1d246c0c849a6…` |
-
-Held at `scratch/market-and-certification/fcc/2AC7Z-ESPS3WROOM1/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AC7Z-ESPS3WROOM1/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/lilygo/t4-s3/market-and-pricing.md b/devices/lilygo/t4-s3/market-and-pricing.md
deleted file mode 100644
index 6956a9a..0000000
--- a/devices/lilygo/t4-s3/market-and-pricing.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# Market and pricing — t4-s3
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://www.lilygo.cc/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| T4 S3 | 2023-11-03 | China [For Worldwide] / With Shell Soldered Female Pin [H711] | `H711` | **USD 58.99** | ✅ yes |
-| T4 S3 | 2023-11-03 | China [For Worldwide] / With Shell Soldered Pin [H724] | `H724` | **USD 60.23** | ✅ yes |
-| T4 S3 | 2023-11-03 | China [For Worldwide] / Basic [H678] | `H678` | **USD 56.89** | ✅ yes |
-| T4 S3 | 2023-11-03 | China [For Worldwide] / Only Sheild [H731] | `H731` | **USD 1.10** | ✅ yes |
-| T4 S3 | 2023-11-03 | Germany [ For Europe only] / With Shell Soldered Female Pin [H711] | `H711DE` | **USD 63.49** | ❌ no |
-| T4 S3 | 2023-11-03 | United States [For US only] / With Shell Soldered Female Pin [H711] | `H711US` | **USD 63.49** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 58.99, 1 unit, retrieved 2026-09-11, `https://www.lilygo.cc/products/t4-s3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-Basic USD 56.89 → shell + soldered pin USD 60.23. `H731` at USD 1.10 is **a shield only**, not a board — excluding it is why the floor here is 56.89 and not 1.10. ⚠ A naive 'from' price would read USD 1.10.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cap-cc1101/README.md b/devices/m5stack/cap-cc1101/README.md
deleted file mode 100644
index 4ddd496..0000000
--- a/devices/m5stack/cap-cc1101/README.md
+++ /dev/null
@@ -1,230 +0,0 @@
-# M5Stack Cap CC1101 & NFC (SKU U219)
-
-> **What it is:** a 14-pin expansion board ("Cap") for the **Cardputer-Adv** and
-> **CardputerZero** combining a **TI CC1101** multi-band sub-GHz transceiver
-> (315 / 433 / 868 / 915 MHz, switched by **two Infineon BGS13SN8 SP3T switches**) with an
-> **ST ST25R3916** NFC front end (reader/writer *and* card emulation), on a **shared SPI
-> bus**, behind a **host-gated** power rail, plus a Grove pass-through.
->
-> **This is the newest board in the family: store publish date 2026-08-28**, seven days
-> before this snapshot. **Schematic revision documented: V0.3, dated 2026-05-28.**
-> Nothing tested on hardware.
-
-> **Why this record matters beyond the Cardputer:** it is the cleanest published example of
-> "NFC + sub-GHz on one SPI bus with a shared antenna", which is exactly the shape of the
-> wider project's goal of adding NFC and LoRa capability to e-ink reader firmware. The
-> portability material is in [`features/nfc.md` §10](features/nfc.md) and
-> [`features/sub-ghz.md` §9](features/sub-ghz.md).
-
----
-
-## Evidence labelling
-
-| Marker | Meaning |
-|---|---|
-| **[SCH]** | `U219-Cap_CC1101_SCH_V0.3_20260528.pdf`, 3 sheets, in [`artifacts/schematic/`](artifacts/schematic/) — text-layer extraction, `executed-success`; not rendered |
-| **[DOC]** | `docs.m5stack.com/en/cap/Cap_CC1101` and the Arduino guide, retrieved 2026-09-04 |
-| **[SHOP]** | `shop.m5stack.com/products/cap-cc1101-nfc-for-cardputer.json`, 2026-09-04 |
-| **[SRC]** | Source read at a cited path/commit |
-| **[COM]** | Community report, cited by permalink and date |
-| **[INF]** | Inference |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketed name | **Cap CC1101** (store title: *Cap CC1101 & NFC for Cardputer Adv*) | **[DOC]**, **[SHOP]** |
-| SKU | **U219** | **[DOC]**, **[SHOP]** |
-| Shopify product / variant id | `9328460431617` / `50248139571457` | **[SHOP]** |
-| **Store publish date** | **2026-08-28T12:00:54+08:00** (created 2026-08-28T10:48:38+08:00 — 72 minutes earlier) | **[SHOP]** |
-| List price | **USD 18.95** | **[SHOP]** |
-| Schematic revision | **V0.3, 2026-05-28** | **[SCH]** filename + title block |
-| Hosts | **Cardputer-Adv**, **CardputerZero**; announced for **Cardputer P4 (Next)** | **[DOC]**; P4 is **[COM]** |
-| ❌ Not | the original Cardputer (no expansion bus) | **[DOC]** |
-| Bus | Cap-Bus 14-pin (`HDR_14P-P2.54`, `P1`) | **[SCH]** |
-| Extra connector | HY2.0-4P Grove (`J1`) — `5V / GND / SDA / SCL` pass-through | **[SCH]**, **[DOC]** |
-| Antenna connector | **`E1` = `SMA-TH_KH-SMA-KE-Z`**, one port for all bands | **[SCH]** |
-| In the box | the Cap + **three** RP-SMA rubber antennas: **315 MHz, 433 MHz, 868 MHz** (the 868 one covers 915) | **[DOC]** |
-| Size / weight | 84.0 × 24.0 × **19.7** mm · 14.9 g | **[DOC]** |
-
-> **Note the height.** 19.7 mm vs the LoRa Cap's 15.2 mm. If you are printing a case, the
-> two Caps are **not** dimensionally interchangeable. Existing Cardputer+LoRa-Cap cases on
-> Printables ([r/CardPuter 2026-07-18](https://old.reddit.com/r/CardPuter/comments/1v05l8h/))
-> will not fit this one.
-
-### 1.1 Eleven months from tease to shelf
-
-An owner emailed M5Stack in September 2025 and posted the reply:
-*"Cardputer ADV Hacker cap (CC1101 SubGHz & ST25R3916 RFID) expected release … So release
-will be in around 3-4 months, either in December or January."*
-([r/CardPuter 2025-09-08](https://old.reddit.com/r/CardPuter/comments/1nbe134/)). **[COM]**
-It shipped **2026-08-28**. In between, u/Relevant-Lynx-6688 asked for an update on
-2026-01-31 and got none. Both chips were named correctly in that 2025 email, so the design
-was fixed nearly a year before release.
-
----
-
-## 2. Chip inventory
-
-Designator census across all three sheets. **[SCH]**
-
-| Ref | Sheet | Part | Function | Record |
-|---|---|---|---|---|
-| **U3** | 3 | **`CC1101RGPR`** (QFN-20 + EPAD21) | Sub-1 GHz FSK/OOK transceiver | [`components/texas-instruments/cc1101`](../../../components/texas-instruments/cc1101/README.md) |
-| **U2** | 2 | **`ST25R3916-AQWT`** (QFN-32 + EPAD33) | NFC front end, reader/writer + card emulation | [`components/stmicroelectronics/st25r3916`](../../../components/stmicroelectronics/st25r3916/README.md) |
-| **U4, U5** | 3 | **`BGS13SN8E6327XTSA1`** ×2 | **SP3T RF switches** — the multi-band trick | [`components/infineon/bgs13sn8`](../../../components/infineon/bgs13sn8/README.md) |
-| **B1** | 3 | **`B0310J50100AHF`** | Wideband **balun**, CC1101 differential RF ↔ 50 Ω single-ended | [`components/generic/rf-balun-b0310j50100ahf`](../../../components/generic/rf-balun-b0310j50100ahf/README.md) |
-| **U1** | 1 | **`JW5712`** | 5 V → 3.3 V buck, `IOUT: 0~0.6 A`, **enabled by host G3** | [`components/joulwatt/jw5712`](../../../components/joulwatt/jw5712/README.md) |
-| **Y2** | 3 | **26 MHz** crystal, `Y2016` package, C48/C49 = 12 pF | CC1101 reference | — |
-| **Y1** | 2 | **27.12 MHz** crystal, C19/C20 = 6.0 pF | ST25R3916 reference — **the NFC carrier is 13.56 MHz = 27.12/2** | [`components/generic/xl7el89cmi-111ylc-27.12mhz-crystal`](../../../components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md) |
-| **ANT1** | 2 | NFC antenna, differential `ANT1_P` / `ANT1_N` | 13.56 MHz loop | — |
-| **E1** | 3 | `SMA-TH_KH-SMA-KE-Z` | Sub-GHz antenna connector | [`components/generic/rp-sma-and-sma-antenna-connectors`](../../../components/generic/rp-sma-and-sma-antenna-connectors/README.md) |
-| **P1** | 1 | `HDR_14P-P2.54` | Cap-Bus | [`pinouts-and-buses.md`](pinouts-and-buses.md) |
-| **J1** | 1 | `GROVE 4P` | HY2.0-4P pass-through | — |
-| **L1** | 1 | `MWTC201608S2R2` (2.2 µH) | Buck inductor | — |
-| **R1** | 1 | **100 kΩ** | Buck enable network with `POWER_EN` | — |
-| L4 3.3 nH · L5 6.8 nH · C42 100 pF · C43 0.6 pF · C46 100 pF · C47 100 pF · R5 0 Ω · R6 56 kΩ (`RBIAS`) | 3 | CC1101 balun / bias network | — |
-| L6 10 nH · L7 0 R · L8 10 nH · L17 3.6 nH · C50 8 pF · C51 DNP | 3 | **315 MHz** band path (`315MHz 频段`) | — |
-| L9 · L10–L13 · C52–C55 (0 R, 0 R, 15 nH, 0 R, 10 pF, NC, 6.2 pF) | 3 | **433 MHz** band path | — |
-| L15 0 R · L16 10 nH · C58/C59 · C60/C61 · R7 · D1 0 R | 3 | **868/915 MHz** band path | — |
-| C7 220 pF · C8 10 pF · C9 DNP · R2/R3 1.5 Ω · L2/L3 270 nH ±5 % · C10 220 pF · C11/C13 680 pF · C12/C14 150 pF · C15 180 pF · C16 · C17 10 pF · C18 220 pF | 2 | **ST25R3916 differential antenna matching + EMC filter** | — |
-| C21–C36 (8 × 10 nF + 8 × 10 µF) | 2 | ST25R3916 supply decoupling — one pair per supply pin | — |
-| C37–C41 (100 nF ×5) | 3 | CC1101 AVDD/DVDD decoupling | — |
-| R4 330 Ω | 3 | Series on `GDO0` → `CC1101_G0` | — |
-
-**No I/O expander on this board.** Unlike the Cap LoRa-1262, everything is directly
-host-driven — plus one trick using the CC1101's own GDO2 pin (§3).
-
----
-
-## 3. The band-switching architecture — the interesting part
-
-One antenna port serves four bands. Two `BGS13SN8` SP3T switches (one on each side of the
-band-specific matching networks) select which of three LC paths the CC1101's balun output
-travels through. They are driven by **two control lines**, and only one of them is a host
-GPIO:
-
-| Control | Comes from |
-|---|---|
-| **`CC1101_RF_SW0`** | **host GPIO** — `G13` on Cardputer-Adv, **`G14` on CardputerZero** |
-| **`CC1101_RF_SW1`** | **the CC1101's own `GDO2` pin (pin 3)** — set over SPI, not by a host pin |
-
-Truth table (M5Stack publishes it identically on the product page and in the Arduino guide;
-the schematic carries an on-sheet table which this pass could **not** transcribe reliably
-from the text layer — noted honestly rather than guessed):
-
-| `RF_SW0` | `RF_SW1` | Band |
-|:---:|:---:|---|
-| 0 | 0 | **315 MHz** |
-| 0 | 1 | **433 MHz** |
-| 1 | 1 | **868 / 915 MHz** |
-
-`1,0` is unlisted — treat as undefined.
-
-**This is the single most portable idea on the board.** It costs one host GPIO instead of
-two, because the transceiver's own general-purpose output does half the work. The cost is
-that you cannot set the band before the CC1101 is talking. Full walkthrough with code in
-[`features/band-switching.md`](features/band-switching.md).
-
-Independent corroboration from M5Stack's community manager, the day of release:
-*"multiple frequency bands: 315 / 433 / 868 / 915 MHz, which can be switched via firmware
-using a combination of G13 (Cardputer ADV) or G14 (CardputerZero) as SW0 and GDO2 from the
-CC1101 as SW1."* ([r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/)). **[COM]**
-
----
-
-## 4. Common tasks / How do I…?
-
-| Question | Guide |
-|---|---|
-| …transmit/receive sub-GHz? | [`features/sub-ghz.md`](features/sub-ghz.md) |
-| …switch bands? | [`features/band-switching.md`](features/band-switching.md) |
-| …read an NFC tag / emulate a card? | [`features/nfc.md`](features/nfc.md) |
-| …**port NFC to other firmware?** | [`features/nfc.md` §10](features/nfc.md) |
-| …**port sub-GHz to other firmware?** | [`features/sub-ghz.md` §9](features/sub-ghz.md) |
-| …power the Cap on and off? | [`features/power-and-grove.md`](features/power-and-grove.md) |
-| …find the pin numbers? | [`pinouts-and-buses.md`](pinouts-and-buses.md) |
-| …know why it can't do LoRa? | §6 below |
-
----
-
-## 5. Vendor specification
-
-| Specification | Value |
-|---|---|
-| RF chip | **CC1101** |
-| Bands | **315 / 433 / 868 / 915 MHz** |
-| Range (FSK, 58 kbps air rate) | 315 MHz: **435 m** · 433/868/915 MHz: **441 m** |
-| TX power | **+10 dBm** |
-| RX sensitivity | **up to −99.5 dBm** |
-| Modulation | 2-FSK, 4-FSK, GFSK, MSK, ASK, OOK |
-| FIFOs | 64 B TX + 64 B RX, independent |
-| NFC chip | **ST25R3916** |
-| NFC reader/writer | NFC-A/B (ISO14443A/B), NFC-F (FeliCa™), NFC-V (ISO15693) |
-| NFC card emulation | **NFC-A / NFC-F** |
-| NFC FIFO | **512 B** |
-| Host interface | **SPI** (both chips) |
-| Sleep current | **DC 5 V @ 140.87 µA** — CC1101 and NFC both asleep |
-| Operating current | **DC 5 V @ 96 mA** — CC1101 continuous TX at max power *and* NFC continuously reading |
-| Size / weight | 84.0 × 24.0 × 19.7 mm · 14.9 g |
-
-Prose on those numbers: the two current figures are unusually *well* specified for M5Stack —
-both name the exact operating state, and the 140.87 µA sleep figure is the more useful of
-the two because it tells you the Cap can be left fitted without meaningfully loading the
-host's battery. The "435 m / 441 m" range figures name a modulation and an air rate but not
-antennas, height, terrain or a link-margin criterion, so they are marketing numbers with a
-method-shaped hole in them; treat as order-of-magnitude only.
-
----
-
-## 6. ⚠ CC1101 cannot do LoRa. It is not a LoRa board.
-
-The frequencies overlap, so people ask. u/crypticsmellofit, release day:
-*"Will the cc1101 also work for LoRA? Those are the right frequencies…"*
-Two independent, correct answers followed within the hour:
-
-- u/dargerlick: *"LoRa uses chirp spread spectrum modulation which is not supported on
-  CC1101 chips."*
-- u/No_Confusion7932: *"No LoRa. … LoRa uses a proprietary spread spectrum modulation that
-  is similar to and a derivative of chirp spread spectrum (CSS) modulation. Texas
-  Instruments does not manufacture its own LoRa chips. LoRa technology and its associated
-  patents belong to Semtech."*
-
-([r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/)) **[COM]**
-
-**If you want LoRa on a Cardputer-Adv, that is the [Cap LoRa-1262](../cap-lora-1262/README.md).**
-The two Caps are complementary, and there is only one Cap slot — a limitation owners
-complain about explicitly.
-
-What the CC1101 *is* good for: the same territory as a Flipper Zero's sub-GHz radio —
-capture, replay and analysis of OOK/FSK remotes, Wireless M-Bus at 868 MHz, and
-point-to-point FSK links. u/No_Confusion7932 again: *"It's like the Sub-GHz CC1101 on the
-Flipper Zero, except this Cap for the Cardputer has a longer range"* — attributed to the
-external antenna and the per-band matching, which is a plausible interpretation but **not a
-measurement**.
-
----
-
-## 7. Photographs
-
-Four product photographs in [`media/`](media/); provenance, rights and captions in
-[`media.md`](media.md).
-
-## 8. Related records
-
-- [**Cap LoRa-1262 (U214)**](../cap-lora-1262/README.md) — the LoRa Cap, same bus
-- [**Cap LoRa868 (U201)**](../cap-lora868/README.md) — the first Cap
-- **Cardputer-Adv** — `devices/m5stack/cardputer-adv/README.md` *(parallel research pass)*
-- [**M5Stack PaperMono**](../papermono/README.md) — uses the *same* ST25R3916 over **I²C**
-  instead of SPI; the interface strap is the whole difference
-- [`guides/nfc`](../../../guides/nfc/README.md) · [`guides/lora`](../../../guides/lora/README.md)
-
-## 9. Files in this record
-
-`README.md` · [`pinouts-and-buses.md`](pinouts-and-buses.md) · [`development.md`](development.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md) · [`gaps-and-conflicts.md`](gaps-and-conflicts.md) ·
-[`market-and-pricing.md`](market-and-pricing.md) · [`projects-and-community.md`](projects-and-community.md) ·
-[`sources.md`](sources.md) · [`research-log.md`](research-log.md) · [`commands.md`](commands.md) ·
-[`media.md`](media.md) · [`features/`](features/README.md) · [`artifacts/`](artifacts/)
diff --git a/devices/m5stack/cap-cc1101/acquisition/manifest.json b/devices/m5stack/cap-cc1101/acquisition/manifest.json
deleted file mode 100644
index e776603..0000000
--- a/devices/m5stack/cap-cc1101/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "devices/m5stack/cap-cc1101",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AN3WM5CAPCC1101-9617157",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPCC1101/Test-Report/AiTDG-260609002W1-Test-Report-315-9617157.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617157",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617157.pdf",
-    "https://fccid.io/2AN3WM5CAPCC1101",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/Test-Report/AiTDG-260609002W1-Test-Report-315-9617157.pdf"
-   ],
-   "sha256": "da6829ba562a367a83cbcd74c3eaf139a6825b527838c8f199202e40a19acae8",
-   "bytes": 886164,
-   "destination": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-09-02",
-   "fcc_id": "2AN3WM5CAPCC1101",
-   "fcc_document_id": "9617157",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "AiTDG-260609002W1_Test Report-315",
-   "grant_date": "2026-09-02",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf",
-   "placeholder": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-cc1101",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPCC1101-9617200",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPCC1101/RF-Exposure-Info/AiTDG-260609002W5-FCC-RF-EXPOSURE-20cm-9617200.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617200",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617200.pdf",
-    "https://fccid.io/2AN3WM5CAPCC1101",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/RF-Exposure-Info/AiTDG-260609002W5-FCC-RF-EXPOSURE-20cm-9617200.pdf"
-   ],
-   "sha256": "253c5be1e0ff6fa0c12c534433414093134fbcb4fc5f739a58536d8ce96d8c42",
-   "bytes": 196253,
-   "destination": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-09-02",
-   "fcc_id": "2AN3WM5CAPCC1101",
-   "fcc_document_id": "9617200",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "AiTDG-260609002W5_FCC RF EXPOSURE 20cm",
-   "grant_date": "2026-09-02",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf",
-   "placeholder": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-cc1101",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPCC1101-9617204",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPCC1101/External-Photos/External-Photos-9617204.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617204",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617204.pdf",
-    "https://fccid.io/2AN3WM5CAPCC1101",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/External-Photos/External-Photos-9617204.pdf"
-   ],
-   "sha256": "475348bb11a54fd3b8570d716cea4994fb0a80d46340d454eeba5bb5d74666ba",
-   "bytes": 4676988,
-   "destination": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-09-02",
-   "fcc_id": "2AN3WM5CAPCC1101",
-   "fcc_document_id": "9617204",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2026-09-02",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf",
-   "placeholder": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-cc1101",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPCC1101-9617205",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPCC1101/Label/FCC-ID-Label-9617205.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617205",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617205.pdf",
-    "https://fccid.io/2AN3WM5CAPCC1101",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/Label/FCC-ID-Label-9617205.pdf"
-   ],
-   "sha256": "481c0f71a93501f29b070216f8deec0860066fb3e3e6e15d726fbb88def3bdde",
-   "bytes": 393120,
-   "destination": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-fcc-id-label.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-09-02",
-   "fcc_id": "2AN3WM5CAPCC1101",
-   "fcc_document_id": "9617205",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "FCC ID Label",
-   "grant_date": "2026-09-02",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-cc1101",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPCC1101-9617206",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPCC1101/Internal-Photos/Internal-Photos-9617206.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617206",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617206.pdf",
-    "https://fccid.io/2AN3WM5CAPCC1101",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/Internal-Photos/Internal-Photos-9617206.pdf"
-   ],
-   "sha256": "5ecb27e04b6abed28dcd43b166b6302273760d168cfaaafd77f412274853fa87",
-   "bytes": 1871803,
-   "destination": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-09-02",
-   "fcc_id": "2AN3WM5CAPCC1101",
-   "fcc_document_id": "9617206",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2026-09-02",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-cc1101",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPCC1101-9617244",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPCC1101/User-Manual/User-Manual-9617244.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617244",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617244.pdf",
-    "https://fccid.io/2AN3WM5CAPCC1101",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/User-Manual/User-Manual-9617244.pdf"
-   ],
-   "sha256": "86892fcec9338f1c30f1a5fe3935f17a9ce04d9299db7c4793851fef47bd4014",
-   "bytes": 547721,
-   "destination": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-09-02",
-   "fcc_id": "2AN3WM5CAPCC1101",
-   "fcc_document_id": "9617244",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2026-09-02",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf",
-   "placeholder": "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-cc1101",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf.ARCHIVED.md b/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf.ARCHIVED.md
deleted file mode 100644
index 5459511..0000000
--- a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 886,164 B (0.85 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 886,164 B (0.85 MiB) |
-| SHA-256 | `da6829ba562a367a83cbcd74c3eaf139a6825b527838c8f199202e40a19acae8` |
-| FCC ID | **`2AN3WM5CAPCC1101`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | AiTDG-260609002W1_Test Report-315 |
-| FCC document id | 9617157 |
-| Upstream publication date | 2026-09-02 |
-| Grant date | 2026-09-02 |
-| Equipment class | M5Cap CC1101, 902.3-923.4 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPCC1101/Test-Report/AiTDG-260609002W1-Test-Report-315-9617157.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617157>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617157.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPCC1101>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/Test-Report/AiTDG-260609002W1-Test-Report-315-9617157.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf" \
-   "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPCC1101/Test-Report/AiTDG-260609002W1-Test-Report-315-9617157.pdf" -o "2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf"
-echo "da6829ba562a367a83cbcd74c3eaf139a6825b527838c8f199202e40a19acae8  2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf.ARCHIVED.md b/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf.ARCHIVED.md
deleted file mode 100644
index 1a4d4b5..0000000
--- a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 196,253 B (0.19 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 196,253 B (0.19 MiB) |
-| SHA-256 | `253c5be1e0ff6fa0c12c534433414093134fbcb4fc5f739a58536d8ce96d8c42` |
-| FCC ID | **`2AN3WM5CAPCC1101`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | AiTDG-260609002W5_FCC RF EXPOSURE 20cm |
-| FCC document id | 9617200 |
-| Upstream publication date | 2026-09-02 |
-| Grant date | 2026-09-02 |
-| Equipment class | M5Cap CC1101, 902.3-923.4 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPCC1101/RF-Exposure-Info/AiTDG-260609002W5-FCC-RF-EXPOSURE-20cm-9617200.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617200>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617200.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPCC1101>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/RF-Exposure-Info/AiTDG-260609002W5-FCC-RF-EXPOSURE-20cm-9617200.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf" \
-   "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPCC1101/RF-Exposure-Info/AiTDG-260609002W5-FCC-RF-EXPOSURE-20cm-9617200.pdf" -o "2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf"
-echo "253c5be1e0ff6fa0c12c534433414093134fbcb4fc5f739a58536d8ce96d8c42  2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf.ARCHIVED.md b/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 09a4414..0000000
--- a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPCC1101-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 4,676,988 B (4.46 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 4,676,988 B (4.46 MiB) |
-| SHA-256 | `475348bb11a54fd3b8570d716cea4994fb0a80d46340d454eeba5bb5d74666ba` |
-| FCC ID | **`2AN3WM5CAPCC1101`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 9617204 |
-| Upstream publication date | 2026-09-02 |
-| Grant date | 2026-09-02 |
-| Equipment class | M5Cap CC1101, 902.3-923.4 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPCC1101/External-Photos/External-Photos-9617204.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617204>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617204.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPCC1101>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/External-Photos/External-Photos-9617204.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf" \
-   "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPCC1101/External-Photos/External-Photos-9617204.pdf" -o "2AN3WM5CAPCC1101-external-photos.pdf"
-echo "475348bb11a54fd3b8570d716cea4994fb0a80d46340d454eeba5bb5d74666ba  2AN3WM5CAPCC1101-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-fcc-id-label.pdf b/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-fcc-id-label.pdf
deleted file mode 100644
index 64b042e..0000000
Binary files a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-fcc-id-label.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-internal-photos.pdf b/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-internal-photos.pdf
deleted file mode 100644
index 40481df..0000000
Binary files a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-internal-photos.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf.ARCHIVED.md b/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index b9a31ac..0000000
--- a/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPCC1101-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 547,721 B (0.52 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 547,721 B (0.52 MiB) |
-| SHA-256 | `86892fcec9338f1c30f1a5fe3935f17a9ce04d9299db7c4793851fef47bd4014` |
-| FCC ID | **`2AN3WM5CAPCC1101`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 9617244 |
-| Upstream publication date | 2026-09-02 |
-| Grant date | 2026-09-02 |
-| Equipment class | M5Cap CC1101, 902.3-923.4 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPCC1101/User-Manual/User-Manual-9617244.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9617244>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPCC1101/9617244.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPCC1101>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPCC1101/User-Manual/User-Manual-9617244.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf" \
-   "devices/m5stack/cap-cc1101/artifacts/certification/2AN3WM5CAPCC1101-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPCC1101/User-Manual/User-Manual-9617244.pdf" -o "2AN3WM5CAPCC1101-user-manual.pdf"
-echo "86892fcec9338f1c30f1a5fe3935f17a9ce04d9299db7c4793851fef47bd4014  2AN3WM5CAPCC1101-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-cc1101/artifacts/certification/README.md b/devices/m5stack/cap-cc1101/artifacts/certification/README.md
deleted file mode 100644
index e4c8c15..0000000
--- a/devices/m5stack/cap-cc1101/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5CAPCC1101`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5CAPCC1101`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2026-09-02** |
-| Equipment class | M5Cap CC1101, 902.3-923.4 MHz |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Source page | <https://fccid.io/2AN3WM5CAPCC1101> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5CAPCC1101-fcc-id-label.pdf` | 393,120 | `481c0f71a93501f29b070216f8deec0860066fb3e3e6e15d726fbb88def3bdde` | ID Label/Location Info |
-| `2AN3WM5CAPCC1101-internal-photos.pdf` | 1,871,803 | `5ecb27e04b6abed28dcd43b166b6302273760d168cfaaafd77f412274853fa87` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf.ARCHIVED.md`](2AN3WM5CAPCC1101-aitdg-260609002w1-test-report-315.pdf.ARCHIVED.md) | 886,164 | Test Report |
-| [`2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf.ARCHIVED.md`](2AN3WM5CAPCC1101-aitdg-260609002w5-fcc-rf-exposure-20cm.pdf.ARCHIVED.md) | 196,253 | RF Exposure Info |
-| [`2AN3WM5CAPCC1101-external-photos.pdf.ARCHIVED.md`](2AN3WM5CAPCC1101-external-photos.pdf.ARCHIVED.md) | 4,676,988 | External Photos |
-| [`2AN3WM5CAPCC1101-user-manual.pdf.ARCHIVED.md`](2AN3WM5CAPCC1101-user-manual.pdf.ARCHIVED.md) | 547,721 | Users Manual |
-
-Archived total: **4 files, 6.01 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 2.16 MiB** |
-| Archived | **4 files, 6.01 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/m5stack/cap-cc1101/artifacts/mechanical/U219-Cap_CC1101_model_size.pdf b/devices/m5stack/cap-cc1101/artifacts/mechanical/U219-Cap_CC1101_model_size.pdf
deleted file mode 100644
index 329822f..0000000
Binary files a/devices/m5stack/cap-cc1101/artifacts/mechanical/U219-Cap_CC1101_model_size.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf b/devices/m5stack/cap-cc1101/artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf
deleted file mode 100644
index 8ae416f..0000000
Binary files a/devices/m5stack/cap-cc1101/artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/certification-and-compliance.md b/devices/m5stack/cap-cc1101/certification-and-compliance.md
deleted file mode 100644
index aa6ee1a..0000000
--- a/devices/m5stack/cap-cc1101/certification-and-compliance.md
+++ /dev/null
@@ -1,123 +0,0 @@
-# Certification and compliance — cap-cc1101
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5CAPCC1101` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5CAPCC1101`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **902.3-923.4 MHz Original Equipment 2026-09-02 433.92 MHz Original Equipment 2026-09-02** |
-| Application purpose | Original Equipment |
-| Frequency ranges | **902.3-923.4 MHz** |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 4 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5CAPCC1101` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-- USA-DueDigilenceLetter_V0.1 [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 4,676,988 | `475348bb11a54fd3…` |
-| `ID-Label-Location-Info-FCC-ID-Label.pdf` | 393,120 | `481c0f71a93501f2…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,871,803 | `5ecb27e04b6abed2…` |
-| `RF-Exposure-Info-AiTDG-260609002W5_FCC-RF-EXPOSURE-20cm.pdf` | 196,253 | `253c5be1e0ff6fa0…` |
-| `Test-Report-AiTDG-260609002W1_Test-Report-315.pdf` | 886,164 | `da6829ba562a367a…` |
-| `Users-Manual-User-Manual.pdf` | 547,721 | `86892fcec9338f1c…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5CAPCC1101/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5CAPCC1101/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cap-cc1101/commands.md b/devices/m5stack/cap-cc1101/commands.md
deleted file mode 100644
index 51eb4b0..0000000
--- a/devices/m5stack/cap-cc1101/commands.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Command ledger — Cap CC1101 & NFC (U219)
-
-bash on NixOS, 2026-09-04. Shares tooling with
-[`../cap-lora-1262/commands.md`](../cap-lora-1262/commands.md) — only the deltas are here.
-
-## Acquisition
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-curl -sS -A "$UA" -o Cap_CC1101.html https://docs.m5stack.com/en/cap/Cap_CC1101
-curl -sS -A "$UA" -o cap-cc1101.json https://shop.m5stack.com/products/cap-cc1101-nfc-for-cardputer.json
-curl -sS -A "$UA" -o cap_cc1101_arduino.html https://docs.m5stack.com/en/arduino/projects/cap/cap_cc1101
-curl -sSL -A "$UA" -o U219-Cap_CC1101_SCH_V0.3_20260528.pdf \
-  https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1250/SCH_Cap_CC1101_SCH_V0.3_20260528.pdf
-```
-`executed-success` — 200 / 138 934 B, 200 / 17 082 B, 200 / 456 766 B, 200 / 485 518 B
-(`%PDF-1.4`).
-
-## Schematic extraction (3 sheets)
-
-```bash
-cd scratch/m5stack-lora-expansions
-uv run --quiet --with pypdf python tools/pdf_bbox.py \
-    artifacts/U219-Cap_CC1101_SCH_V0.3_20260528.pdf \
-    pdf/U219-Cap_CC1101_SCH_V0.3_20260528
-#  page 1: 178 words   page 2: 326 words   page 3: 448 words
-for p in 1 2 3; do
-  uv run --quiet python tools/sch_dump.py \
-      pdf/U219-Cap_CC1101_SCH_V0.3_20260528/bbox-p$p.xml rows
-done
-```
-`executed-success`.
-
-Targeted region dumps that produced the pin tables:
-
-```bash
-# CC1101 (U3) body, sheet 3
-uv run --quiet python /tmp/box.py pdf/U219-…/bbox-p3.xml  60 340  70 230
-# balun + switches, sheet 3
-uv run --quiet python /tmp/box.py pdf/U219-…/bbox-p3.xml 330 560 120 230
-# buck + POWER_EN, sheet 1
-uv run --quiet python /tmp/box.py pdf/U219-…/bbox-p1.xml  60 400 240 340
-```
-`executed-success` for the first three.
-
-```bash
-# RF-switch truth table, sheet 3
-uv run --quiet python /tmp/box.py pdf/U219-…/bbox-p3.xml 380 620 470 540
-```
-**`executed-failed`** — returned only `SMA-TH_KH-SMA-KE-Z`, `PIE10*` and `GND`. The
-truth-table grid (`√` / `x` glyphs) does not survive this extractor. **Diagnosis:** the
-glyphs are likely a symbol font with no usable ToUnicode mapping, and the row/column
-association is geometric rather than textual. **Consequence recorded as gap G1** — the
-truth table in this record comes from the product page + Arduino guide + a vendor Reddit
-comment, three agreeing sources, **none of them the schematic**.
-
-## GitHub
-
-```bash
-GH="Authorization: Bearer $(gh auth token)"
-curl -sS -H "$GH" "https://api.github.com/search/repositories?q=org%3Am5stack%20cc1101"
-#   -> {"total_count": 0, ...}     NEGATIVE RESULT, executed-success
-curl -sS -H "$GH" "https://api.github.com/search/code?q=CapCC1101NFC+repo:m5stack/M5Unit-NFC"
-#   -> 38 hits, incl. src/M5UnitUnifiedNFC.hpp
-curl -sSL -H "$GH" -o M5UnitUnifiedNFC.hpp \
-  https://raw.githubusercontent.com/m5stack/M5Unit-NFC/93745b547364f310cd64b5155a870103a7800a5d/src/M5UnitUnifiedNFC.hpp
-grep -n 'CapCC1101NFC' M5UnitUnifiedNFC.hpp
-#   48:  using CapCC1101NFC = m5::unit::CapST25R3916;
-```
-`executed-success`. Pinning by **commit** rather than `main` matters here: the file is
-1 250 B and the alias could move.
-
-## Duplicate check before storing a datasheet
-
-```bash
-sha256sum components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf \
-          scratch/m5stack-lora-expansions/artifacts/st25r3916_datasheet-m5stack-mirror.pdf
-# 1170f4d74ff501917262ae42bf81c60c38c11d121e2ea2af6b1e845433befef1  (both)
-```
-`executed-success` → **not stored twice.** The `/1229/` URL was added to the component's
-source table instead. Run this before filing *any* vendor-mirrored datasheet; M5Stack
-serves the same document from multiple OSS paths.
-
-## Not executed
-
-No build, no flash, no on-device command. The `platformio.ini` in
-[`development.md`](development.md) is **`inferred`** and was **not built**.
diff --git a/devices/m5stack/cap-cc1101/compatibility-and-status.md b/devices/m5stack/cap-cc1101/compatibility-and-status.md
deleted file mode 100644
index 4542bf9..0000000
--- a/devices/m5stack/cap-cc1101/compatibility-and-status.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Compatibility and status — Cap CC1101 & NFC (U219)
-
-**Released 2026-08-28; this snapshot is 2026-09-04.** There is almost no field evidence yet,
-and the honest state of this page is *"documented, unproven"*. Nothing was tested here.
-
-## 1. Hosts
-
-| Host | Fits? | Evidence |
-|---|---|---|
-| **Cardputer-Adv** | ✅ | vendor **[DOC]**; schematic annotates every Cap-Bus pin with its ADV GPIO |
-| **CardputerZero** | ✅, **with a pin change** — `RF_SW0` moves from **G13** to **G14** | vendor **[DOC]**; **[COM]** M5Stack community post, [2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/) |
-| **Cardputer P4 ("Next")** | claimed; **product unreleased** | **[COM]** same post |
-| **Original Cardputer (K132)** | ❌ | no expansion bus |
-
-**The CardputerZero pin difference is important and under-documented.** A firmware that
-hard-codes `RF_SW0 = 13` will silently select the wrong band on a Zero. No vendor code
-handles this; the only statement of it is a Reddit comment by M5Stack's community manager.
-
-## 2. Firmware
-
-| Firmware | CC1101 | NFC | Status |
-|---|---|---|---|
-| **M5Stack Arduino examples** | ✅ | ✅ | Published with the product. `not-tested` here |
-| **M5Stack UiFlow2 / MicroPython** | ✅ | ✅ | Vendor page exists (zh-cn path) |
-| **`m5stack/M5Unit-NFC` 0.1.0** | — | ✅ | `CapCC1101NFC` present since 2026-06-10, **before** release |
-| **RadioLib** | ✅ | — | CC1101 fully supported upstream; band switching is application code |
-| **Bruce** | ❌ **not yet** | ❌ | Community expectation is that Bruce will add it; band switching needs implementing |
-| **Meshtastic** | ❌ n/a | ❌ n/a | Wrong radio class entirely |
-
-## 3. Field evidence
-
-| Date | Report | Class |
-|---|---|---|
-| 2026-08-28 | Release announcement thread, 41 upvotes / 16 comments. Several *"Ordered!"*; **no owner has posted a working result yet** | community, ordering intent only |
-| 2026-08-28 | *"I have mine ordered with the Zero"* — u/Zatoichi80 | firsthand purchase, no result |
-| 2026-08-28 | Correct technical answers on why CC1101 ≠ LoRa | informed interpretation |
-| 2025-09-08 | Pre-announcement: M5Stack told an owner "December or January". Slipped ~8 months | firsthand quote of vendor email |
-
-**Nothing in the sample is a firsthand use report of this board.** Anyone reading this
-record after ~2026-10 should re-search; the evidence base will have changed.
-
-## 4. Untested / unknown
-
-Everything measurable: output power, sensitivity, per-band insertion loss, inter-band
-isolation, NFC read range, tag compatibility, card-emulation behaviour, the two chips
-sharing one SPI bus in different modes, the `POWER_EN` polarity, and the 140.87 µA sleep
-figure.
diff --git a/devices/m5stack/cap-cc1101/development.md b/devices/m5stack/cap-cc1101/development.md
deleted file mode 100644
index cda46c7..0000000
--- a/devices/m5stack/cap-cc1101/development.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Development — Cap CC1101 & NFC (U219)
-
-No processor, no firmware of its own. Everything is host-side. Snapshot 2026-09-04, seven
-days after release — **expect this page to age quickly**.
-
-## 1. Toolchains
-
-| Path | Status |
-|---|---|
-| **Arduino / PlatformIO** | Vendor guides published for **both** subsystems (`docs.m5stack.com/en/arduino/projects/cap/cap_cc1101`). `not-tested` |
-| **ESP-IDF** | `M5Unit-NFC` ships ESP-IDF example forms (`examples/**/main/*.cpp`) and Kconfig variants. CC1101 side is RadioLib, Arduino-flavoured |
-| **UiFlow2 / MicroPython** | `uiflow-micropython.readthedocs.io/zh-cn/latest/cap/cc1101.html` — note the vendor links the **zh-cn** path from the English page |
-| **Meshtastic** | **Not applicable.** CC1101 cannot do LoRa |
-| **Bruce / M5Launcher** | Not yet. Band switching *"will still need to be implemented by the dev"* — u/No_Confusion7932, [r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/) |
-
-## 2. Libraries
-
-| Library | Role | Pin |
-|---|---|---|
-| **RadioLib** (jgromes) | CC1101 driver — the vendor's "CC1101 Driver Library" link | release **7.7.1** (2026-05-31), head `187ef247…` (2026-08-22). **MIT** |
-| **m5stack/M5Unit-NFC** | ST25R3916 driver — class `m5::unit::CapCC1101NFC` (alias of `CapST25R3916`) | head `93745b547364f310cd64b5155a870103a7800a5d` (2026-06-10), release **0.1.0** (2026-06-10). **MIT** |
-| **M5Unified / M5GFX / M5UnitUnified** | board abstraction, `wiring::addSPI` | not pinned by the docs |
-| **M5Cardputer** | keyboard | `github.com/m5stack/M5Cardputer` |
-
-> **No M5Stack CC1101 library exists** (`org:m5stack cc1101` → 0 repositories, 2026-09-04).
-> The NFC library, by contrast, is M5Stack's own and predates the product by 11 weeks.
-
-Required constants from RadioLib for band switching:
-`RADIOLIB_CC1101_GDOX_HW_TO_0`, `RADIOLIB_CC1101_GDO2_INV`, `RADIOLIB_CC1101_GDO2_NORM`.
-
-## 3. Build sketch
-
-```cpp
-// platformio.ini (illustrative, not-tested)
-[env:cardputer-adv-cap-cc1101]
-platform  = https://github.com/pioarduino/platform-espressif32.git
-board     = m5stack-stamps3
-framework = arduino
-lib_deps  =
-  m5stack/M5Unified
-  m5stack/M5Cardputer
-  https://github.com/m5stack/M5Unit-NFC.git#93745b547364f310cd64b5155a870103a7800a5d
-  jgromes/RadioLib@^7.7.1
-build_flags = -DUSING_CAP_CC1101
-```
-`inferred` — assembled from the vendor guides' `#include` sets and the libraries' own
-metadata. **Not built.** The `pioarduino/platform-espressif32` reference is taken from
-M5Stack's own Stamp-C6LoRa documentation, which pins `#55.03.37`.
-
-## 4. Bring-up order (matters here)
-
-1. **Host G3 (`POWER_EN`) → HIGH.** Nothing on the Cap answers until the rail is up.
-2. SPI up.
-3. **CC1101:** `radio.begin(freq, bitrate, freqDev, rxBw, power, preambleLen)`.
-4. **Band:** host GPIO for `RF_SW0`, `IOCFG2` write for `RF_SW1`
-   ([`features/band-switching.md`](features/band-switching.md)).
-5. **NFC:** `m5::unit::wiring::addSPI(Units, unit, 10'000'000, 1)` then `Units.begin()`.
-   ⚠ **SPI mode 1** — different from the CC1101's.
-
-## 5. Flashing / recovery
-
-Host-side only; the Cap has no flash, no MCU, no bootloader. Cardputer-Adv download mode:
-power switch OFF, hold **G0**, power on, release.
-
-If the Cap seems dead: check `POWER_EN` (G3) first — that is the failure mode unique to
-this board and it looks exactly like a dead Cap.
-
-## 6. Risks
-
-| Risk | Note |
-|---|---|
-| Transmitting with the **wrong band antenna** | Three whips ship; they are not interchangeable. Not damaging at +10 dBm, but range collapses |
-| Transmitting with **no antenna** | The vendor's no-antenna damage warning is on the *LoRa* Cap (+22 dBm). At +10 dBm the risk is much lower, but there is no vendor statement either way for this board — treat as unknown |
-| **Transmitting out of band for your region** | The examples default to **915.0 MHz**. See [`features/sub-ghz.md` §7](features/sub-ghz.md) |
-| Driving both chips without re-establishing SPI mode | Silent corruption — [`features/nfc.md` §8](features/nfc.md) |
-
-## 7. Related
-
-[`features/sub-ghz.md`](features/sub-ghz.md) · [`features/nfc.md`](features/nfc.md) ·
-[`features/band-switching.md`](features/band-switching.md) ·
-[`pinouts-and-buses.md`](pinouts-and-buses.md) · [`commands.md`](commands.md)
diff --git a/devices/m5stack/cap-cc1101/features/README.md b/devices/m5stack/cap-cc1101/features/README.md
deleted file mode 100644
index 7a46a75..0000000
--- a/devices/m5stack/cap-cc1101/features/README.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Feature guides — Cap CC1101 & NFC (U219)
-
-| Feature | Guide | Status |
-|---|---|---|
-| Sub-GHz radio (CC1101) | [`sub-ghz.md`](sub-ghz.md) | documented from schematic + vendor guide; **not hardware-tested** |
-| Multi-band antenna switching | [`band-switching.md`](band-switching.md) | documented; the board's most transferable idea |
-| NFC (ST25R3916, **SPI**) | [`nfc.md`](nfc.md) | documented; contrast with the PaperMono's I²C strap |
-| Power gate + Grove pass-through | [`power-and-grove.md`](power-and-grove.md) | documented |
-
-Cross-cutting: [`guides/nfc`](../../../../guides/nfc/README.md) ·
-[`guides/lora`](../../../../guides/lora/README.md) (for why this board is **not** a LoRa board).
diff --git a/devices/m5stack/cap-cc1101/features/band-switching.md b/devices/m5stack/cap-cc1101/features/band-switching.md
deleted file mode 100644
index 7d6b480..0000000
--- a/devices/m5stack/cap-cc1101/features/band-switching.md
+++ /dev/null
@@ -1,113 +0,0 @@
-# Band switching — Cap CC1101 (U219)
-
-The one genuinely novel thing about this board, and the part most worth stealing.
-
-## 1. The problem
-
-A CC1101 will operate anywhere in 300–348 / 387–464 / 779–928 MHz, but a *matching network*
-will not. A single fixed match across 315 → 915 MHz costs many dB. Most CC1101 modules
-therefore pick one band and stay there — which is exactly the limitation an owner named on
-release day: *"I've been using the CC1101 modules for some time, but it was always limited
-to a single frequency band, most often 433 MHz."*
-(u/No_Confusion7932, [r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/)) **[COM]**
-
-## 2. The solution on this board
-
-Three narrowband LC paths, selected by **two SP3T switches** (`U4`, `U5` —
-`BGS13SN8E6327XTSA1`) placed either side of them, fed from a **wideband balun** at the
-CC1101's differential port and terminating in **one** SMA connector.
-
-Two control lines, **only one of which is a host pin**:
-
-| Control | Source | Cardputer-Adv | CardputerZero |
-|---|---|---|---|
-| `CC1101_RF_SW0` | host GPIO, via Cap-Bus pin 2 | **G13** | **G14** |
-| `CC1101_RF_SW1` | **CC1101 `GDO2` (pin 3)** — never leaves the board | — | — |
-
-Truth table (product page and Arduino guide agree verbatim):
-
-| `RF_SW0` | `RF_SW1` | Band | Antenna to fit |
-|:---:|:---:|---|---|
-| 0 | 0 | **315 MHz** | 315 MHz whip |
-| 0 | 1 | **433 MHz** | 433 MHz whip |
-| 1 | 1 | **868 / 915 MHz** | 868 MHz whip (covers 915) |
-
-`1,0` is not defined by the vendor. Do not use it.
-
-## 3. Driving `RF_SW1` through the CC1101
-
-You cannot `digitalWrite()` a pin you do not have. `GDO2` is configured over SPI as a
-**static output**, using the CC1101's `IOCFG2` register. RadioLib exposes this through its
-GDO configuration constants; M5Stack's own guide does it like this:
-
-```cpp
-void setRfBand() {
-    bool rf_sw0{}, rf_sw1{};
-    if (CC1101_FREQ == 315.0f)                              { rf_sw0 = 0; rf_sw1 = 0; }
-    else if (CC1101_FREQ == 433.0f)                          { rf_sw0 = 0; rf_sw1 = 1; }
-    else if (CC1101_FREQ == 868.0f || CC1101_FREQ == 915.0f) { rf_sw0 = 1; rf_sw1 = 1; }
-
-    // RF_SW0 is controlled directly by the host GPIO.
-    pinMode(RF_SW0, OUTPUT);
-    digitalWrite(RF_SW0, rf_sw0 ? HIGH : LOW);
-
-    // Drive RF_SW1 from CC1101 GDO2 through SPI.
-    const uint8_t gdo2_config = RADIOLIB_CC1101_GDOX_HW_TO_0 |
-                                (rf_sw1 ? RADIOLIB_CC1101_GDO2_INV
-                                        : RADIOLIB_CC1101_GDO2_NORM);
-    // ... written to IOCFG2
-}
-```
-
-**Read that carefully.** The chosen GDO source is `HW_TO_0` — "hardwired to 0" — and the
-*polarity-inversion* bit is then used to produce a 1. That is the idiomatic way to make a
-CC1101 GDO pin a constant-level output, and it is the trick worth remembering. **[DOC]**,
-`executed-success` on the read, `not-tested`.
-
-## 4. Ordering constraint
-
-Because `RF_SW1` lives inside the transceiver, **you cannot select the band before the
-CC1101 is initialised.** Sequence:
-
-1. Power the Cap: host **G3 (`POWER_EN`) HIGH**.
-2. `radio.begin(...)` — SPI up, chip configured.
-3. `setRfBand()` — host GPIO for SW0, `IOCFG2` write for SW1.
-4. Set the exact carrier frequency (`radio.setFrequency()` if not already set in `begin`).
-5. Transmit or receive.
-
-Changing band later means repeating steps 3–4. Doing step 5 before step 3 transmits into
-the wrong matching network — not usually damaging at +10 dBm, but the range will be
-terrible and it will look like a broken board.
-
-## 5. Why this is worth copying
-
-| Property | Value |
-|---|---|
-| Host GPIO cost | **1**, not 2 |
-| Extra silicon | 2 × SP3T switch (small, cheap, sub-$1 class) |
-| Bands covered | 3 matched paths, 4 nominal bands |
-| Antenna ports | **1** |
-| Constraint | band cannot be set before the transceiver is alive |
-
-Any design with a transceiver that has a spare GDO/DIO pin and a shortage of host GPIO can
-use the same pattern. It is not CC1101-specific — an SX126x's `DIO2`/`DIO3` are used the
-same way for RF-switch control and TCXO supply respectively.
-
-## 6. Unresolved
-
-- The **schematic's own truth table** could not be transcribed from the PDF text layer
-  (the `√`/`x` grid extracted as fragments). The table above rests on **two vendor
-  documents that agree** plus the community announcement — three sources, none of them the
-  schematic. If a future pass renders sheet 3, check it.
-- Which switch (`U4` or `U5`) carries which control on which port was **not** resolved
-  pin-by-pin; both are driven from the same two nets (`V1`, `V2`).
-- Isolation between paths, insertion loss per band: unmeasured, unpublished.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | Cap **U219** schematic V0.3 |
-| Software | RadioLib ≥ 7.x for `RADIOLIB_CC1101_GDOX_HW_TO_0` / `GDO2_INV` |
-| Evidence | Truth table: **two vendor docs + one vendor community post**, mutually consistent. Code: **read from the vendor guide**. Behaviour: `not-tested` |
-| Last verified | 2026-09-04 |
diff --git a/devices/m5stack/cap-cc1101/features/nfc.md b/devices/m5stack/cap-cc1101/features/nfc.md
deleted file mode 100644
index 4648846..0000000
--- a/devices/m5stack/cap-cc1101/features/nfc.md
+++ /dev/null
@@ -1,251 +0,0 @@
-# NFC — Cap CC1101 (U219), ST25R3916 over SPI
-
-> **Common guide:** [`guides/nfc`](../../../../guides/nfc/README.md).
->
-> **Applicability:** the standard approach **applies with one large delta** — this board
-> straps the ST25R3916 to **SPI**, where the other ST25R3916 board in this repository
-> (M5Stack PaperMono) straps it to **I²C**. Everything above the transport is identical;
-> everything about bus arbitration, speed and mode is not.
-
-> **How do I read an NFC tag?** §5. **How do I put this on my own hardware?** §10.
-> Snapshot 2026-09-04 · schematic **V0.3 / 2026-05-28** · nothing tested on hardware.
-
----
-
-## 1. Hardware path
-
-```
-        13.56 MHz loop antenna (ANT1, ANT1_P / ANT1_N)
-              ▲                              ▲
-     ┌────────┴────────┐            ┌────────┴────────┐
-     │ L2 270nH ±5%    │            │ L3 270nH ±5%    │   EMC + matching
-     │ R2 1.5 Ω        │            │ R3 1.5 Ω        │
-     │ C7 220p C8 10p  │            │ C15 180p C17 10p│
-     │ C10 220p        │            │ C18 220p        │
-     │ C11 680p C12150p│            │ C13 680p C14150p│
-     └────────┬────────┘            └────────┬────────┘
-       RFO1(13)                        RFO2(15)
-       RFI1(22)/RFI_P                  RFI2(23)/RFI_N
-       AAT_A(18)                       AAT_B(19)      ← automatic antenna tuning
-                     U2  ST25R3916-AQWT
-   XTI(5)/XTO(4) ── Y1 27.12 MHz (C19/C20 6.0 pF)     ← 13.56 = 27.12 / 2
-   I2C_EN(20) ── strapped for SPI
-   SS(29)  ◀── NFC_CS   ◀── Cap-Bus 10 ◀── host G6
-   IRQ(27) ──▶ NFC_IRQ  ──▶ Cap-Bus  9 ──▶ host G4
-   SCLK(30)/MOSI(31)/MISO(32) ◀──▶ shared SPI ◀──▶ G40 / G14 / G39
-   VDD_IO(1) VDD_D(3) VDD_A(7) VDD(8) VDD_RF(9) VDD_TX(10) VDD_AM(11) VDD_DR(14)
-        each with a 10 nF + 10 µF pair (C21…C36)
-```
-
-## 2. The interface strap is the whole story
-
-The ST25R3916 chooses its host interface from a **pin strap**, not a command: `I2C_EN`
-(pin 20). This board ties it for **SPI**; the PaperMono ties it for **I²C**. Consequences:
-
-| | Cap CC1101 (SPI) | PaperMono (I²C) |
-|---|---|---|
-| Transport | 4-wire SPI, **mode 1** (CPOL=0, CPHA=1), **10 MHz** in M5Stack's example | I²C, address per `ST25R3916` record |
-| Chip select | `SS` pin 29 ← host **G6** | none |
-| Bus sharing | **with the CC1101** on the same board (different CS) and with the host's microSD | with keyboard, IMU, codec, expander |
-| Latency | high-rate; adequate for ISO-DEP framing | ⚠ the M5Unit-NFC README warns that a **SoftwareI2C** Grove path has *"I2C register polling latency too high for ST25R3916 RF timing requirements"* |
-| Library selection macro | `#define USING_CAP_CC1101` | `#define USING_UNIT_NFC` |
-
-> **The latency note is the important transferable lesson.** ST25R3916 RF timing is
-> enforced by register polling; if your transport is slow, protocols fail in ways that look
-> like antenna problems. M5Stack say so explicitly for one bus type in their own library
-> README. If you are porting to a host where I²C is bit-banged or heavily shared, **use
-> SPI**.
-
-Register-space, mode-byte and direct-command detail is **not repeated here** — it lives in
-[`components/stmicroelectronics/st25r3916`](../../../../components/stmicroelectronics/st25r3916/README.md),
-which already documents the mode byte, the space-B prefix, auto-increment behaviour and the
-mandatory power-on write sequence.
-
-## 3. Antenna and matching
-
-The board carries a **fully differential** matching network — two symmetric arms of
-270 nH ±5 % series inductance with 1.5 Ω damping, plus a 4-element EMC/matching capacitor
-group per arm — feeding `ANT1_P`/`ANT1_N`. `AAT_A` (18) and `AAT_B` (19) are connected,
-which means the chip's **Automatic Antenna Tuning** is available: the ST25R3916 can trim a
-pair of on-chip varactor banks to compensate for detuning by a nearby metal object or a
-card. Anything that wants reliable reads through a case should use it.
-
-`EXT_LM` (17) is connected via `C19`-adjacent components — external load modulation is
-therefore wired for card-emulation use.
-
-Component values are transcribed from the schematic text layer, `executed-success` on the
-read. They were **not** verified against a rendered sheet, so treat the *pairing* of value
-to designator as `inferred` where two designators sit on the same row.
-
-## 4. Software
-
-| Stack | Class | Where |
-|---|---|---|
-| **M5Unit-NFC / `M5UnitUnifiedNFC`** — the vendor's own | **`m5::unit::CapCC1101NFC`**, an alias: `using CapCC1101NFC = m5::unit::CapST25R3916;` | `github.com/m5stack/M5Unit-NFC`, head `93745b547364f310cd64b5155a870103a7800a5d` (2026-06-10), release **0.1.0** (2026-06-10), **MIT** |
-| ST's RFAL | — | **Not used.** The existing `ST25R3916` record establishes that M5Unit-NFC is *"a from-scratch driver, not an RFAL wrapper"* |
-| Anything else | — | No community ST25R3916 driver for this Cap was located |
-
-> **The library shipped before the product.** `CapCC1101NFC` and `USING_CAP_CC1101` are
-> present at the 2026-06-10 head — **11 weeks before** the Cap went on sale (2026-08-28) —
-> and the README says so in as many words: *"CapCC1101 / SKU:U219 (SPI connection via
-> ST25R3916) is included in this library for future use."* That is useful provenance: the
-> driver was written against the real hardware well ahead of release, so it is not
-> speculative support.
-
-Selection is by preprocessor macro in the examples:
-
-```cpp
-// #define USING_UNIT_NFC
-#define USING_CAP_CC1101       // SKU U219
-```
-
-Example families in the repo (`examples/UnitUnified/`): **NFCA** — Detect, Dump, NDEF,
-ReadWrite, ValueBlock, PolicyOverride, **Emulation**; **NFCB** — Detect, JapanIDCard;
-**NFCF** — Detect, Dump, NDEF, Emulation, Subtract, ReadWriteMAC,
-JapanTransportationICCard; **NFCV** — Detect, Dump, NDEF. Both Arduino (`.ino`) and
-ESP-IDF (`main/*.cpp`) forms are provided. `Kconfig.variant.basic` notes that NFC-A
-Emulation and *all* NFC-F and NFC-V examples are **only supported on ST25R3916-based
-units** — i.e. this Cap and the Unit NFC, not the RFID2/WS1850S alternatives.
-
-Support caveats from the library README, worth knowing before you promise a customer
-anything: *"MIFARE DESFire Light — NDEF is not supported yet"*; and for the I²C variant
-*"MIFARE Plus SL3 operation has issues, SL2 can not R/W"* (an I²C-variant limitation, so
-**this SPI board should be the better one** for MIFARE Plus — `inferred`, untested).
-
-## 5. Minimal read
-
-From M5Stack's Arduino guide. `executed-success` on the read; `not-tested`. **[DOC]**
-
-```cpp
-#include <M5Cardputer.h>
-#include <M5Unified.h>
-#include <M5UnitUnified.h>
-#include <M5UnitUnifiedNFC.h>
-#include <wiring/m5_unit_unified_wiring.hpp>
-using namespace m5::nfc::a;
-using namespace m5::nfc::a::mifare::classic;
-
-m5::unit::UnitUnified Units;
-m5::unit::CapCC1101NFC unit{};          // Cap CC1101 NFC (ST25R3916, SPI)
-m5::nfc::NFCLayerA    nfc_a{unit};
-constexpr Key keyA = DEFAULT_KEY;        // 0xFFFFFFFFFFFF
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg, true);
-    // SPI mode 1, 10 MHz. The library maps the Cardputer-Adv pins itself:
-    //   SCK=G40, MOSI=G14, MISO=G39, NFC CS=G6, NFC IRQ=G4
-    bool ready = m5::unit::wiring::addSPI(Units, unit, 10000000, 1) && Units.begin();
-}
-```
-
-The guide's `Dump` example triggers on the Cardputer's **Tab** key, detects/identifies/
-activates an NFC-A tag, authenticates MIFARE Classic with the default key, and dumps via
-`picc.uidAsString()` / `picc.typeAsString()`.
-
-Two things the guide states that are easy to miss:
-
-1. **You do not specify the SPI pins.** `addSPI()` maps them from the host identity. That
-   is convenient on a Cardputer-Adv and a trap on anything else — see §10.
-2. **SPI mode 1**, not mode 0. The CC1101 on the same bus uses a different mode; see
-   [`sub-ghz.md` §4](sub-ghz.md).
-
-## 6. Resources consumed
-
-| Resource | Value | Contention |
-|---|---|---|
-| Host GPIO | **2 dedicated** (G6 `NFC_CS`, G4 `NFC_IRQ`) + 3 shared SPI (G40/G14/G39) | SPI shared with **CC1101** (CS = G5) and the host **microSD** (CS = G12) |
-| SPI mode/clock | mode **1**, 10 MHz | ⚠ differs from the CC1101's mode on the same wires |
-| Power | via `VDD_3V3` from `U1`, gated by `POWER_EN` ← host **G3** | the whole Cap powers down together |
-| Interrupt | G4 | ST25R3916 `IRQ` is level-ish and must be serviced or the chip stalls |
-
-## 7. Card emulation
-
-Supported for **NFC-A and NFC-F only** (vendor spec and library README agree). NFC-B and
-NFC-V are reader/writer only. `EXT_LM` is wired, so external load modulation is available
-for the emulation path.
-
-This is the capability that makes the board interesting beyond tag reading: an NFC-A/NFC-F
-card emulator with a keyboard and a screen attached is, functionally, a programmable
-transit/access card sandbox. **No community project doing this on the Cap was found** — the
-board is seven days old.
-
-## 8. Simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| NFC + CC1101 sub-GHz | ⚠ **shared SPI, different modes** | Both on G40/G14/G39. You must switch SPI mode between transactions, or run two `SPIClass` configurations against one bus and re-`beginTransaction` each time |
-| NFC + microSD | ⚠ shared SPI | Host `SDCARD_CS` = G12 |
-| NFC + Wi-Fi/BLE | ✅ | 13.56 MHz vs 2.4 GHz |
-| NFC + sub-GHz RF-wise | ✅ | 13.56 MHz vs 315–915 MHz, separate antennas |
-| NFC + Grove I²C sensor | ✅ | different bus entirely |
-| NFC while the Cap is powered down | ❌ | `POWER_EN` (G3) low kills the rail |
-
-## 9. Debugging
-
-| Symptom | Cause |
-|---|---|
-| Nothing on the bus at all | Cap not powered — drive host **G3 high** first ([`power-and-grove.md`](power-and-grove.md)) |
-| Chip responds, no tags detected | Antenna detuning; try Automatic Antenna Tuning (`AAT_A`/`AAT_B` are wired) |
-| Works standalone, fails when the sub-GHz radio is active | **SPI mode collision** — §8 |
-| Protocol-level timeouts, ISO-DEP failures | Transport latency. Do not put this chip behind a slow/bit-banged bus — §2 |
-| MIFARE Plus SL3 misbehaves | Known library limitation, documented for the I²C variant; status on SPI untested |
-| DESFire Light NDEF unsupported | Known library gap, stated in the README |
-
-## 10. Porting checklist — adding ST25R3916 NFC to other firmware
-
-Written for the wider project's goal of adding NFC to e-ink reader firmware. The
-PaperMono's I²C treatment is the sibling case:
-[`devices/m5stack/papermono/features/nfc.md`](../../papermono/features/nfc.md).
-
-**Hardware you must provide:**
-
-| Resource | Count | Notes |
-|---|---|---|
-| SPI SCK/MOSI/MISO | 3 | shareable; **budget for mode switching** if other devices differ |
-| Chip select | 1 | dedicated |
-| `IRQ` | 1 | **strongly recommended.** Polling works but ISO-DEP timing suffers |
-| 27.12 MHz crystal | 1 | **not optional** — the 13.56 MHz carrier is derived from it. C ≈ 6.0 pF load caps |
-| 8 supply pins, each decoupled | — | this board uses a **10 nF + 10 µF pair per pin**. Under-decoupling an ST25R3916 shows up as read-range loss, not as a digital fault |
-| Differential antenna + matching | 1 | the hard part. Two 270 nH ±5 % arms, 1.5 Ω damping, ~4 caps per arm on this board |
-| `AAT_A`/`AAT_B` | 2 | wire them; automatic tuning is worth the two pins |
-| `EXT_LM` | 1 | only if you want card emulation |
-| `I2C_EN` strap | 1 | **decide early.** SPI for latency, I²C for pin count |
-
-**Software:**
-
-1. `m5stack/M5Unit-NFC` (**MIT**) is a complete, from-scratch ST25R3916 driver with
-   Arduino *and* ESP-IDF builds, NFC-A/B/F/V, and card emulation. It is the shortest path
-   and its licence permits reuse.
-2. It is written against **M5UnitUnified**, so a port means either bringing that
-   abstraction along or reimplementing `addSPI()`/`Units.begin()` against your own bus API.
-   The `wiring::addSPI(Units, unit, 10'000'000, 1)` signature is the whole surface.
-3. **`addSPI()` infers pins from the host board identity.** On non-M5Stack hardware that
-   inference does not exist and you must supply pins explicitly — expect this to be the
-   first thing you have to patch.
-4. ST's **RFAL** is the alternative if you need ST's certification-grade protocol stack;
-   it is much larger and this board does not use it.
-5. Budget flash: the NFC-A/B/F/V protocol layers plus MIFARE are not small.
-
-**What is board-specific and must not be copied:** the pin numbers, the `POWER_EN` gate,
-the SPI mode collision with a co-resident CC1101, and the antenna matching values (they are
-tuned to *this* PCB's loop).
-
-## 11. Unresolved
-
-- `I2C_EN` strap value read as "strapped for SPI" from the net name plus the vendor's
-  interface claim; the **strap resistor was not identified** on the sheet. `inferred`.
-- `ANT1` is a designator with no published geometry — PCB loop turns, area and inductance
-  are unknown, so the matching network cannot be re-derived for another board.
-- Whether the AAT is actually exercised by `M5Unit-NFC` on this Cap: not checked.
-- No read-range, tag-compatibility or emulation test by anyone. The board is seven days old.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | Cap **U219**, schematic **V0.3 / 2026-05-28** |
-| Software | `m5stack/M5Unit-NFC` @ `93745b54…` (rel. 0.1.0, MIT) · M5Unified · M5UnitUnified |
-| Evidence | Chip identity and pin map: **schematic + vendor pin-map + vendor Arduino guide**, three-way. Matching values: **schematic text layer**, `executed-success` on the read, pairing `inferred`. Behaviour: **none tested** |
-| Confidence | High on architecture; **zero on RF performance and tag compatibility** |
-| Last verified | 2026-09-04 |
diff --git a/devices/m5stack/cap-cc1101/features/power-and-grove.md b/devices/m5stack/cap-cc1101/features/power-and-grove.md
deleted file mode 100644
index f864edb..0000000
--- a/devices/m5stack/cap-cc1101/features/power-and-grove.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# Power gate and Grove pass-through — Cap CC1101 (U219)
-
-Snapshot 2026-09-04, schematic **V0.3 / 2026-05-28**.
-
-## 1. The Cap is host-switchable — unlike the LoRa Cap
-
-| Item | Value | Evidence |
-|---|---|---|
-| Regulator | **`U1` JW5712** buck, `IOUT: 0~0.6 A` | **[SCH]** sheet 1 |
-| Inductor | `L1` `MWTC201608S2R2` (2.2 µH) | **[SCH]** |
-| Input caps | `C1` 1 nF, `C2`/`C3`/`C4` 22 µF | **[SCH]** |
-| Output caps | `C5` 22 µF, `C6` 100 nF | **[SCH]** |
-| **Enable** | **`POWER_EN`** ← Cap-Bus **pin 8** ← host **G3** → `U1` `ENB` | **[SCH]** sheet 1; **[DOC]** pin map |
-| Enable network | `R1` **100 kΩ** | **[SCH]**; **polarity `inferred`, not traced** |
-
-**Cap-Bus pin 8 means something completely different on the two Caps.** On the
-[Cap LoRa-1262](../../cap-lora-1262/features/power-and-grove.md) it is `LoRa_RST`; here it
-is `POWER_EN` for the whole board. Any auto-detect logic that assumes pin-8 semantics
-across Caps is wrong.
-
-Practical consequence, and it is a good one: the host can **fully power down** the CC1101,
-the ST25R3916 and everything else on this Cap with one GPIO. That is how the vendor's
-**140.87 µA @ 5 V** sleep figure is achievable — it is a board that can be switched off, not
-merely a pair of chips in their own low-power modes.
-
-> ⚠ The `R1` polarity was not traced end-to-end from the PDF text layer, so whether the Cap
-> defaults **on** (pull-up, host pulls low to disable) or **off** (pull-down, host must
-> drive high) is **not established**. Both vendor documentation and the pin-map name the
-> signal `POWER_EN`, which conventionally implies **active-high enable**. Bring-up code
-> should therefore drive **G3 HIGH and wait** before touching SPI. `inferred`.
-
-## 2. Bring-up order
-
-1. Host **G3 → OUTPUT, HIGH** (`POWER_EN`).
-2. Allow the buck to settle (no time given by the vendor; `not-tested`).
-3. Configure SPI.
-4. `radio.begin()` for the CC1101, and/or `addSPI(...)` for the NFC front end.
-5. `setRfBand()` — [`band-switching.md`](band-switching.md).
-
-Powering down is the reverse; note the CC1101 will lose all configuration.
-
-## 3. Grove pass-through (`J1`, HY2.0-4P)
-
-| Wire | Colour | Net | Host |
-|---|---|---|---|
-| 1 | Black | `GND` | — |
-| 2 | Red | `5V` (`+5VOUT`) | host 5 V |
-| 3 | Yellow | `SDA` | **G8** |
-| 4 | White | `SCL` | **G9** |
-
-Same arrangement as the LoRa Cap: a tap onto the host's **shared** I²C bus, not a private
-one. **Unlike the LoRa Cap, there is no I²C device on this board at all**, so there is no
-address to collide with — a Grove sensor here is simply an extra device on the host bus.
-
-The vendor markets this as *"HY2.0-4P Grove expansion interface — supports sensor module
-expansion"*, which is fair: with only one Cap slot on the host, the pass-through is the
-only way to add anything else.
-
-## 4. Consumers of `VDD_3V3`
-
-| Load | Notes |
-|---|---|
-| `U3` CC1101 — `DVDD`(4), `AVDD`(9,11,14,15) | `C37`–`C41` 100 nF |
-| `U2` ST25R3916 — eight supply pins | `C21`–`C36`, a **10 nF + 10 µF pair per pin** |
-| `U4`, `U5` BGS13SN8 switches | `VDD1`/`VDD` with `C56`/`C57` 100 nF |
-
-The ST25R3916's decoupling is the dominant passive cost on the board and it is not
-optional; under-decoupling an NFC front end costs read range rather than producing a clean
-failure. See [`nfc.md` §10](nfc.md).
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | U219 schematic V0.3 |
-| Evidence | Parts/values **[SCH]** `executed-success`; **enable polarity `inferred`** |
-| Last verified | 2026-09-04 |
diff --git a/devices/m5stack/cap-cc1101/features/sub-ghz.md b/devices/m5stack/cap-cc1101/features/sub-ghz.md
deleted file mode 100644
index e058d3a..0000000
--- a/devices/m5stack/cap-cc1101/features/sub-ghz.md
+++ /dev/null
@@ -1,218 +0,0 @@
-# Sub-GHz radio — Cap CC1101 (U219)
-
-> **How do I transmit and receive?** §5. **How do I change band?** [`band-switching.md`](band-switching.md).
-> **How do I put a CC1101 on my own hardware?** §9.
-> Snapshot 2026-09-04 · schematic **V0.3 / 2026-05-28** · nothing tested on hardware.
-
-## 1. Hardware path
-
-```
-                                     ┌── L6/L7/L8 + L17 3.6nH + C50 8pF ──┐   315 MHz
-CC1101 (U3)                          │                                     │
-  RF_P(12) ── C46 100pF ──┐          ├── L9 + L10..L13 + C52..C55 ─────────┤   433 MHz
-  RF_N(13) ── C42 100pF ──┤ B1 balun │                                     │
-      C43 0.6pF across ───┘ B0310J50100AHF                                 │
-      L4 3.3nH / L5 6.8nH / R5 0R    ├── L15 0R / L16 10nH + C58..C61 ─────┤   868/915 MHz
-      C44 DNP / C45 / C47 100pF      │                                     │
-                                U4 BGS13SN8 (SP3T)                   U5 BGS13SN8 (SP3T)
-                                  V1/V2 ◀── RF_SW0, RF_SW1 ──▶ V1/V2
-                                                                            └──▶ E1 SMA
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Transceiver | **`CC1101RGPR`**, QFN-20 + EPAD | [`components/texas-instruments/cc1101`](../../../../components/texas-instruments/cc1101/README.md) |
-| Balun | **`B0310J50100AHF`** — 6-pin, `Unbalanced`(1) / `GND`(2) / `Balanced`(3,4) / `DNC`(5) / `NC`(6) | [`components/generic/rf-balun-b0310j50100ahf`](../../../../components/generic/rf-balun-b0310j50100ahf/README.md) |
-| Band switches | **2 × `BGS13SN8E6327XTSA1`** SP3T | [`components/infineon/bgs13sn8`](../../../../components/infineon/bgs13sn8/README.md) |
-| Reference | **26 MHz** crystal `Y2` (`Y2016` package), `C48`/`C49` 12 pF | — |
-| Bias | `R6` **56 kΩ** on `RBIAS` (pin 17) | — |
-| Antenna | `E1` `SMA-TH_KH-SMA-KE-Z`; three whips supplied | [`components/generic/rp-sma-and-sma-antenna-connectors`](../../../../components/generic/rp-sma-and-sma-antenna-connectors/README.md) |
-
-**Why the design looks like this.** A CC1101 has a differential RF port and needs a
-band-specific match; one match cannot serve 315 and 915 MHz well. M5Stack solved it by
-putting a **wideband balun** at the chip and then switching between **three narrowband LC
-paths** with a pair of SP3T switches. That is why there are three inductor/capacitor
-clusters on sheet 3 with the Chinese annotations `315MHz 频段`, `433MHz 频段` and
-`868MHz 频段` ("frequency band"), and why the vendor can claim usable range on all of them
-rather than only on one.
-
-## 2. Chip pin map as fitted
-
-**[SCH]** sheet 3, `U3`.
-
-| Pin | Name | Net |
-|---:|---|---|
-| 1 | `SCLK` | `SPI_SCLK` → Cap-Bus 11 → host **G40** |
-| 2 | `MISO` | `SPI_MISO` → Cap-Bus 13 → host **G39** |
-| 20 | `MOSI` | `SPI_MOSI` → Cap-Bus 12 → host **G14** |
-| 7 | `CSN` | `CC1101_CS` → Cap-Bus 14 → host **G5** |
-| **6** | **`GDO0`** | via `R4` **330 Ω** → `CC1101_G0` → Cap-Bus 1 → host **G15** — the interrupt/data line |
-| **3** | **`GDO2`** | **`CC1101_RF_SW1`** — stays on the board, drives the band switches |
-| 5 | `DCOUPL` | decoupled locally |
-| 17 | `RBIAS` | `R6` 56 kΩ |
-| 12 | `RF_P` | → `C46` → balun |
-| 13 | `RF_N` | → `C42` → balun |
-| 8 | `XOSC_Q1` | `Y2` 26 MHz |
-| 10 | `XOSC_Q2` | `Y2` 26 MHz |
-| 4 | `DVDD` | `VDD_3V3` |
-| 9, 11, 14, 15 | `AVDD` | `VDD_3V3`, `C37`–`C41` 100 nF |
-| 18 | `DGUARD` | — |
-| 16, 19 | `GND` | — |
-| 21 | `EPAD` | `GND` |
-
-> **`GDO0` carries a 330 Ω series resistor** on its way to the host. That is a
-> current-limit/edge-softening measure, not a level shift. Worth knowing if you plan to run
-> it fast or drive it as an output.
-
-> **`GDO1` is not used.** On a CC1101, `GDO1` doubles as `MISO`; leaving it as MISO only is
-> the normal choice.
-
-## 3. Vendor RF claims
-
-| Item | Value | Caveat |
-|---|---|---|
-| TX power | **+10 dBm** | RadioLib's allowed set for CC1101 is `-30, -20, -15, -10, 0, 5, 7, 10` dBm; +10 is the maximum |
-| RX sensitivity | **up to −99.5 dBm** | data-rate dependent; the rate is not stated |
-| Range | 315 MHz **435 m**; 433/868/915 MHz **441 m** | at "FSK modulation, 58 kbps air rate"; **no antenna, height, terrain or link-margin criterion given** |
-| FIFOs | 64 B TX + 64 B RX | independent; the classic CC1101 packet-length constraint |
-| Modulations | 2-FSK, 4-FSK, GFSK, MSK, ASK, OOK | |
-
-Prose: the two range numbers differing by 6 m across a 3× frequency span is not physically
-meaningful as a measurement — it reads like two runs of the same test. Treat "a few hundred
-metres, line of sight, with the supplied whip" as the honest summary.
-
-## 4. Software — RadioLib, and the exact vendor configuration
-
-M5Stack's "Cap CC1101 Arduino CC1101 Driver Library" link points at **`jgromes/RadioLib`**.
-There is **no M5Stack CC1101 library**. **[DOC]**, corroborated by a `org:m5stack cc1101`
-GitHub search returning **0 repositories**.
-
-```cpp
-#include <M5Unified.h>
-#include <RadioLib.h>
-
-#define CC1101_FREQ         915.0f   // MHz, must match the receiver
-#define CC1101_BIT_RATE     2.4f     // kbps
-#define CC1101_FREQ_OFFSET  25.4f    // kHz, FSK deviation
-#define CC1101_BW           58.0     // kHz RX filter, >= occupied BW
-#define CC1101_TX_POWER     10       // dBm; allowed: -30,-20,-15,-10,0,5,7,10
-#define CC1101_PREAMBLE_LEN 16       // bits; 16/24/32/48/64/96/128/192
-
-constexpr int CC1101_CS   = 5;
-constexpr int CC1101_GDO0 = 15;
-constexpr int RF_SW0      = 13;      // G14 on CardputerZero
-
-// CC1101 PIN order: CSN, GDO0, RST(unused), GDO2
-CC1101 radio = new Module(CC1101_CS, CC1101_GDO0, RADIOLIB_NC, RADIOLIB_NC);
-
-int state = radio.begin(CC1101_FREQ, CC1101_BIT_RATE, CC1101_FREQ_OFFSET,
-                        CC1101_BW, CC1101_TX_POWER, CC1101_PREAMBLE_LEN);
-```
-
-Note both `RST` and `GDO2` are passed as `RADIOLIB_NC`: **the CC1101 has no reset pin**
-(it is reset by an SPI strobe), and `GDO2` is not available to RadioLib as an interrupt
-because the board uses it for band selection. The guide states the remaining SPI pins are
-mapped automatically: *"The CC1101 SPI pins are G5 (CS), G14 (MOSI), G39 (MISO), G40 (SCK),
-with G15 (GD0) as the interrupt pin."*
-
-Receive side reports `RSSI`, `SNR` and **`LQI`** — the guide's sample output is
-`[CC1101] RSSI: -23.00 dBm / SNR: -25.00 dB / LQI: 2`.
-
-> ⚠ **SPI mode collision.** M5Stack's NFC example configures the shared bus for **mode 1**
-> at 10 MHz. RadioLib drives the CC1101 in its own default mode. Anything using both chips
-> must re-establish the SPI configuration per transaction. Neither vendor example does
-> both at once, so **nobody has demonstrated the combination** — see
-> [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-## 5. Minimal transmit / receive
-
-TX: set the band (see [`band-switching.md`](band-switching.md)), then
-`radio.setPacketSentAction(cb); radio.startTransmit("...")`, and `radio.finishTransmit()`
-in the callback. RX: `radio.setPacketReceivedAction(cb); radio.startReceive();` then
-`radio.readData(...)`. Standard RadioLib. `not-tested`.
-
-## 6. Resources consumed
-
-| Resource | Value |
-|---|---|
-| Host GPIO | **3 dedicated** — G5 (`CS`), G15 (`GDO0`), G13/G14 (`RF_SW0`) — plus 3 shared SPI |
-| Second switch control | **none** — `RF_SW1` is the CC1101's own `GDO2` |
-| Power | `VDD_3V3` from `U1`, gated by `POWER_EN` ← host **G3** |
-
-## 7. Legality by band — this one genuinely matters
-
-| Band | Typical status |
-|---|---|
-| **315 MHz** | US/JP remote-control allocation. **Not an EU ISM band** |
-| **433 MHz** | ISM in ITU Region 1 (EU) and widely tolerated elsewhere; **amateur allocation in some regions** |
-| **868 MHz** | EU SRD, duty-cycle limited |
-| **915 MHz** | US/AU ISM. **Not permitted in the EU** |
-
-The board hands you a switch that spans all four and three antennas to match, with **no
-region lock, no certification identifier published** by M5Stack, and firmware examples that
-default to **915.0 MHz**. A European user running the shipped example transmits out of
-band. This is a genuine, foreseeable compliance hazard and it is worth saying plainly:
-**pick the band deliberately, in code, per deployment region.** Nothing in the vendor
-material does this for you.
-
-The board's headline use — *"Copy/read/transmit signals on the specified frequencies, and
-jam"* (u/No_Confusion7932, [r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/))
-— is, in the "jam" case, illegal essentially everywhere. Recorded because it is what the
-community says the board is for. **[COM]**
-
-## 8. Conflicts and simultaneous use
-
-| Combination | Verdict |
-|---|---|
-| CC1101 + NFC | ⚠ shared SPI, **different modes** — [`nfc.md` §8](nfc.md) |
-| CC1101 + microSD | ⚠ shared SPI with the host's card slot (CS = G12) |
-| CC1101 + Wi-Fi/BLE | ✅ different bands |
-| CC1101 + LoRa | ❌ **not on the same host** — only one Cap slot, and the CC1101 cannot do LoRa anyway |
-| CC1101 + Grove sensor | ✅ different bus |
-
-## 9. Porting checklist — adding a CC1101 to other firmware
-
-**Hardware:**
-
-| Resource | Count | Notes |
-|---|---|---|
-| SPI SCK/MOSI/MISO | 3 | shareable |
-| `CSN` | 1 | dedicated |
-| `GDO0` | 1 | packet interrupt / data line. A series resistor (330 Ω here) is cheap insurance |
-| `GDO2` | 0–1 | **free general-purpose output if you do not need a second interrupt** — this board spends it on band select. That trick is the most reusable idea here |
-| Reset | **0** | The CC1101 has no reset pin; `SRES` is an SPI strobe |
-| 26 MHz crystal | 1 | 12 pF load caps here |
-| `RBIAS` resistor | 1 | 56 kΩ here; it sets the internal bias current and is not optional |
-| Balun + match | 1 set | Single band: one narrowband match. Multi-band: wideband balun + switched paths, as here |
-| Antenna | 1 | |
-
-**Software:** **RadioLib** (MIT) covers the CC1101 with the same API shape as the SX1262 —
-so a firmware that already carries RadioLib for LoRa gets CC1101 support for the cost of
-one more class. That is a genuinely useful fact for the wider project: **one library,
-both radios.**
-
-`new Module(csn, gdo0, RADIOLIB_NC /*rst*/, gdo2_or_NC)` then
-`begin(freq, bitrate, freqDev, rxBw, power, preambleLen)`.
-
-**What is board-specific:** pin numbers, the `POWER_EN` gate, the band-switch truth table,
-and the LC values of the three band paths (tuned to this PCB).
-
-## 10. Unresolved
-
-- The on-sheet RF-switch truth table could not be transcribed from the PDF text layer; the
-  table in §3 of the [README](../README.md) comes from the **product page and Arduino
-  guide**, which agree with each other and with the community announcement.
-- `B0310J50100AHF` is decoded as a **300–1000 MHz, 50 Ω↔100 Ω balun** from the part-number
-  pattern. **`inferred` — no datasheet was located.** See the component record.
-- No measurement of output power, sensitivity, harmonic content or inter-band isolation.
-- No demonstrated firmware for this Cap yet — Bruce and others will need band-switch
-  support added, as the community noted on release day.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | Cap **U219**, schematic **V0.3 / 2026-05-28** |
-| Software | RadioLib ≥ 7.x. **`RF_SW0` = G13 on Cardputer-Adv, G14 on CardputerZero** |
-| Evidence | Pin map: schematic + vendor guide + vendor pin-map, three-way. RF values: schematic text layer. Performance: **vendor claim only** |
-| Last verified | 2026-09-04 |
diff --git a/devices/m5stack/cap-cc1101/gaps-and-conflicts.md b/devices/m5stack/cap-cc1101/gaps-and-conflicts.md
deleted file mode 100644
index 7a96f06..0000000
--- a/devices/m5stack/cap-cc1101/gaps-and-conflicts.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Gaps and conflicts — Cap CC1101 & NFC (U219)
-
-Snapshot 2026-09-04, seven days after release.
-
-## Conflicts
-
-### C1 — Antenna connector: "RP-SMA" in prose, `SMA-KE` on the schematic
-
-Same family of contradiction as on the LoRa Cap. The product page says the three supplied
-antennas have *"RP-SMA connector (internal thread, female pin)"* — that phrasing **does**
-describe an RP-SMA jack correctly (internal thread + pin), unlike the LoRa Cap's
-self-contradictory *"internal thread, internal hole"*. But the schematic's board-side
-connector is `E1 = SMA-TH_KH-SMA-KE-Z`, and `SMA-KE` is the same Chinese designation used
-for the LoRa Cap's `E4`. Both boards therefore carry the same connector family while their
-documentation describes it differently. **Unresolved.** See
-[`components/generic/rp-sma-and-sma-antenna-connectors`](../../../components/generic/rp-sma-and-sma-antenna-connectors/README.md).
-
-### C2 — Timeline slip, stated and unexplained
-
-M5Stack told an owner in September 2025 that the "Hacker cap" would ship in
-"December or January". It shipped 2026-08-28. Not a technical conflict, but it is the
-documented reason a lot of people believed this board was vapourware, and it is why
-searching for it in early 2026 finds only speculation.
-
-## Gaps
-
-| # | Gap | Consequence | Would settle it |
-|---|---|---|---|
-| **G1** | **The schematic's own RF-switch truth table could not be transcribed** — the `√`/`x` grid extracts as fragments under this pass's PDF reader | The truth table in this record rests on the product page + Arduino guide + a vendor Reddit post, all consistent, **but not on the schematic** | Rendering sheet 3 |
-| **G2** | **`B0310J50100AHF` balun: no datasheet located.** The part number decodes plausibly as a **300–1000 MHz, 50 Ω ↔ 100 Ω** balun (Anaren/TTM-style `B<band><pkg>J50100AHF` naming) but that is **`inferred`** | Cannot verify insertion loss, balance or power handling; cannot substitute confidently | The manufacturer datasheet |
-| **G3** | **`ANT1` (NFC loop) has no published geometry** | The differential matching network cannot be re-derived for another PCB | A PCB layer view or a Gerber |
-| **G4** | **`I2C_EN` strap resistor not identified** | "Strapped for SPI" is `inferred` from the vendor's interface claim plus the wired `SS`/`SCLK`/`MOSI`/`MISO` | Rendering sheet 2 |
-| **G5** | **`R1` (100 kΩ) polarity on `POWER_EN` not traced** | Whether the Cap defaults on or off is unestablished; bring-up code must drive G3 high defensively | Rendering sheet 1 |
-| **G6** | **`U4`/`U5` port-by-port mapping not resolved** | Which SP3T port carries which band path is unknown; only the aggregate truth table is | Rendering sheet 3 |
-| **G7** | **No certification identifier** | A four-band, region-agnostic transmitter with no published FCC/CE/IC/TELEC reference, defaulting to 915 MHz in the examples. Real compliance exposure — [`features/sub-ghz.md` §7](features/sub-ghz.md) | A regulatory database hit |
-| **G8** | **Nobody has demonstrated CC1101 and NFC in use together** | The shared-SPI/different-mode question is unanswered in practice | A working example |
-| **G9** | **No measurement of anything** | Every performance number is a vendor claim | Field reports (the board is 7 days old) |
-| **G10** | **Case incompatibility** — 19.7 mm tall vs the LoRa Cap's 15.2 mm | Existing community cases will not fit | Nothing; recorded as a fact |
-| **G11** | UiFlow2 page (zh-cn path) **not fetched**; the vendor's Arduino page was fetched but its NFC examples only skimmed | MicroPython and deeper NFC-example coverage missing | Fetching them |
-| **G12** | Structure/3D files for U219 not located in `M5_Hardware` | Mechanical work blocked | Checking `m5stack/M5_Hardware` |
-
-## Method limitations
-
-- No hardware. Nothing measured, flashed or executed.
-- Schematic parsed from the text layer with a pypdf-derived bbox reader (no poppler on this
-  host); **not rendered**. Six of the twelve gaps above would close with a render.
-- Value-to-designator pairing on densely populated rows is `inferred` where two designators
-  share a text row.
diff --git a/devices/m5stack/cap-cc1101/market-and-pricing.md b/devices/m5stack/cap-cc1101/market-and-pricing.md
deleted file mode 100644
index 99db0b1..0000000
--- a/devices/m5stack/cap-cc1101/market-and-pricing.md
+++ /dev/null
@@ -1,111 +0,0 @@
-# Market and pricing — Cap CC1101 & NFC (U219)
-
-Observed **2026-09-04**, M5Stack official store, USD, item price only.
-
-| SKU | Product | Price | Published |
-|---|---|---|---|
-| **U219** | **Cap CC1101 & NFC for Cardputer Adv** | **USD 18.95** | **2026-08-28** |
-| U214 | [Cap LoRa-1262](../cap-lora-1262/market-and-pricing.md) | USD 14.50 | 2025-12-30 |
-| U216 | NFC Universal Unit (**same ST25R3916**, Grove) | USD 7.00 | 2026-04-17 |
-| M146 | M5Stack CC1101 Module (855–925 MHz, **single band**, Core bus) | USD 10.95 | 2025-11-07 |
-| U113 / U114 | RF Unit 433 MHz RX (SYN513R) / TX (SYN115) | USD 4.50 each | 2021-05-14 |
-
-## What the USD 18.95 actually buys
-
-Two radios plus **three antennas**. That last part is not trivial: the LoRa Cap ships one
-antenna and North-American owners routinely buy a second
-([`../cap-lora-1262/market-and-pricing.md` §3](../cap-lora-1262/market-and-pricing.md)).
-Here M5Stack pre-empts the problem by including 315, 433 and 868 MHz whips.
-
-Against the alternatives:
-
-| Want | Cheaper option | What you give up |
-|---|---|---|
-| NFC only, on any M5Stack host | **NFC Universal Unit (U216), USD 7.00** — same ST25R3916 over Grove | No sub-GHz. And note the M5Unit-NFC README's warning about **SoftwareI2C latency** on some Grove ports being *"too high for ST25R3916 RF timing requirements"* — the SPI Cap is the more robust connection |
-| Sub-GHz only, on a Core-series host | **CC1101 Module (M146), USD 10.95** | **Single band, 855–925 MHz.** No NFC, wrong host bus |
-| Cheap 433 MHz OOK | **RF Unit U113/U114, USD 4.50** | Fixed-function ASK RX or TX; no FSK, no CC1101 register access |
-| **LoRa** | **Cap LoRa-1262, USD 14.50** | Different radio class entirely — [README §6](README.md) |
-
-The band-switching Cap has no direct equivalent in M5Stack's catalogue, and the community
-recognised that immediately: *"I've been using the CC1101 modules for some time, but it was
-always limited to a single frequency band … This Cap supports multiple frequency bands and
-has three antennas covering all of them."* — u/No_Confusion7932,
-[r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/). **[COM]**
-
-## Outside M5Stack
-
-The obvious comparison is the **Flipper Zero**, whose sub-GHz radio is also a CC1101. The
-community's own framing: *"It's like the Sub-GHz CC1101 on the Flipper Zero, except this
-Cap for the Cardputer has a longer range"* — attributed to the external antenna and per-band
-matching versus the Flipper's small internal antenna. That is a **plausible interpretation,
-not a measurement**, and the two devices differ enormously in software maturity. A
-Cardputer-Adv + Cap CC1101 is roughly USD 49 against a Flipper Zero's much higher street
-price, but the Flipper ships a finished application; this Cap ships two vendor examples and
-a `TODO` for Bruce.
-
-## Availability and demand
-
-Release-day thread: several *"Ordered!"* / *"I have mine ordered with the Zero"*. Product
-JSON shows a single default variant with no backorder tag as of 2026-09-04 (contrast the
-Cardputer Mesh Kit, tagged `Backorder`). Too early for a supply picture.
-
-## Caveats
-
-Single seller, single region, single date, seven days after launch. No marketplace, used or
-clone observation — declared exclusions in [`research-log.md`](research-log.md). No price
-history exists yet.
-
----
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| Cap CC1101 & NFC for Cardputer Adv | 2026-08-28 | Default Title | `U219` | **USD 18.95** | ❌ no |
-| M5Stack CC1101 Module (855-925MHz) | 2025-11-07 | Default Title | `M146` | **USD 10.95** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 18.95, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/cap-cc1101-nfc-for-cardputer`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-⚠ **Two different products.** `U219` is the **Cap** for Cardputer ADV (CC1101 **+ NFC**); `M146` is a standalone CC1101 **module**, not a Cap. **Not interchangeable, not one price range.** The Cap is `available: false` — newly listed (2026-08-28) and not yet in stock.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cap-cc1101/media.md b/devices/m5stack/cap-cc1101/media.md
deleted file mode 100644
index 26dcd7b..0000000
--- a/devices/m5stack/cap-cc1101/media.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Media — Cap CC1101 & NFC (U219)
-
-Four product photographs in [`media/`](media/), from M5Stack's documentation CDN.
-
-| File | Bytes | SHA-256 | Source URL | Retrieved |
-|---|---:|---|---|---|
-| `U219_Cap_CC1101_main_pictures_01.webp` | 265 534 | `29ea3e3cd06a0035325e9da705e456a790efc1ba7fe7eb22b651e8e428f5e9e8` | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1250/U219_Cap_CC1101_main_pictures_01.webp` | 2026-09-04 |
-| `U219_Cap_CC1101_main_pictures_02.webp` | 137 082 | `29af42034441b9e9e825b114dab6eac33a0925c54a31ad1ead3b96c0c0f941bc` | `…_02.webp` | 2026-09-04 |
-| `U219_Cap_CC1101_main_pictures_03.webp` | 62 126 | `8e0667611271259d0433870c7af4d73a8e0433be20156aa7ae1f84a2e264f342` | `…_03.webp` | 2026-09-04 |
-| `U219_Cap_CC1101_main_pictures_05.webp` | 75 184 | `b6d642c3bae156971f893397e45a68e50d8140c521197eb29f897aeb68ddc143` | `…_05.webp` | 2026-09-04 |
-
-## Provenance and rights
-
-| Field | Value |
-|---|---|
-| Creator / rightsholder | **M5Stack Technology Co., Ltd.** |
-| Source page | `https://docs.m5stack.com/en/cap/Cap_CC1101` |
-| Publication date | unknown; CDN prefix `1250` = the U219 product record (store publish 2026-08-28) |
-| Applicable revision | Cap CC1101, U219 |
-| Licence / permission | **unknown.** No licence statement accompanies M5Stack product imagery |
-| Redistribution status | **unknown** |
-| Disposition | **repository, unstaged** pending a user decision |
-| Modifications | **none** |
-
-## Captions and alt text
-
-| File | Caption | Alt text |
-|---|---|---|
-| `…_01.webp` | Hero shot: Cap CC1101 & NFC fitted to a Cardputer-Adv with one of the three supplied rubber-duck antennas. | Black expansion board attached beneath a small keyboard computer, with a short whip antenna on one end. |
-| `…_02.webp` | Board detail — expected to show the CC1101/ST25R3916 side and the NFC loop antenna area. | Close view of a small PCB with surface-mount chips and a printed antenna region. |
-| `…_03.webp` | Board detail / connector face. | Close view of the expansion board edge with the antenna connector. |
-| `…_05.webp` | Kit contents or in-use view. | Expansion board shown with accessories. |
-
-> ⚠ **The images were downloaded and hashed but not visually inspected.** Captions for
-> `_02`, `_03` and `_05` are positional expectations from M5Stack's standard 11-image
-> product set, not descriptions of what was seen. They should be viewed and corrected.
-> `_02` is the frame most likely to show the **NFC loop antenna geometry** — which would
-> partially close gap **G3** — and `_03` the frame most likely to settle the
-> **RP-SMA vs SMA** question (conflict **C1**).
-
-## Not retrieved
-
-Seven further product frames (`_04`, `_06`…`_11`), `U219_Cap_CC1101_weight.jpg`, and the
-**schematic page renders** `SCH_Cap_CC1101_SCH_V0.3_20260528_page_0{1,2,3}.png` — the last
-of which would close six of the twelve gaps in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-**No teardown or bare-PCB photograph was located.**
diff --git a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_01.webp b/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_01.webp
deleted file mode 100644
index 5aac53a..0000000
Binary files a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_01.webp and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_02.webp b/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_02.webp
deleted file mode 100644
index 7e73938..0000000
Binary files a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_02.webp and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_03.webp b/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_03.webp
deleted file mode 100644
index e8385b5..0000000
Binary files a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_03.webp and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_05.webp b/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_05.webp
deleted file mode 100644
index 12b05e3..0000000
Binary files a/devices/m5stack/cap-cc1101/media/U219_Cap_CC1101_main_pictures_05.webp and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/media/manifest-schematic-crops.json b/devices/m5stack/cap-cc1101/media/manifest-schematic-crops.json
deleted file mode 100644
index a8f1f91..0000000
--- a/devices/m5stack/cap-cc1101/media/manifest-schematic-crops.json
+++ /dev/null
@@ -1,43 +0,0 @@
-{
-  "$schema-note": "Image provenance manifest for images DERIVED from retained schematic PDFs by local rasterisation. Kept separate from media/manifest.json so that no pre-existing file is modified; an index owner may merge them.",
-  "device": "m5stack/cap-cc1101",
-  "generated": "2026-09-07",
-  "generator": "2026-09-07 schematic net-tracing pass; poppler 26.06.0 + ImageMagick",
-  "global_notes": [
-    "These are NOT photographs and NOT vendor-published images. Each is a crop of a page the vendor published as a vector PDF, rasterised locally at 300 dpi.",
-    "pdfimages could not be used: pdfimages -list reports ZERO embedded rasters in every source PDF here. The drawings are vector, so pdftoppm plus a crop is the only route. This is recorded because reaching for pdfimages is the obvious wrong first move.",
-    "Copyright in the underlying drawing remains with the vendor named in creator_rightsholder. Licence is UNKNOWN: no licence statement appears in any of the source PDFs. Redistribution status unknown; disposition repository, unstaged pending user review.",
-    "Every image is reproducible byte-for-byte from the retained artifact using the recorded generation_command, so none of them is uniquely held here.",
-    "Each image exists because it settles a specific documented question; see why_retained."
-  ],
-  "images": [
-    {
-      "local_path": "media/schematic-P1-cap-bus-14pin.png",
-      "filename": "schematic-P1-cap-bus-14pin.png",
-      "sha256": "339cb8c0c7340481dbf405ca3ecf9ee7e87526f3042825d623d2894c8eda6ddc",
-      "bytes": 78531,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export; 3 pages; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 950x300+2140+1020 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "950x300+2140+1020",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "U219 Cap CC1101 v0.3",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: the Cap-Bus connector P1, HDR_14P-P2.54, with POWER_EN on pin 8",
-      "alt_text": "Schematic detail of a fourteen-pin connector symbol P1 captioned HDR_14P-P2.54, with the same printed pin names as the Cap LoRa-1262's connector. The functional net labels differ: pin 8 reads POWER_EN beside host alias G3, pin 9 NFC_IRQ beside G4, pin 10 NFC_CS beside G6, pins 11 to 14 SPI_SCLK, SPI_MOSI, SPI_MISO and CC1101_CS beside G40, G14, G39 and G5.",
-      "why_retained": "Shows that the bus pinout and host-GPIO assignment are identical to the Cap LoRa-1262's, and that the reported pin-8 discrepancy is a difference in board function, not in the bus."
-    }
-  ]
-}
diff --git a/devices/m5stack/cap-cc1101/media/schematic-P1-cap-bus-14pin.png b/devices/m5stack/cap-cc1101/media/schematic-P1-cap-bus-14pin.png
deleted file mode 100644
index 0ffa3fa..0000000
Binary files a/devices/m5stack/cap-cc1101/media/schematic-P1-cap-bus-14pin.png and /dev/null differ
diff --git a/devices/m5stack/cap-cc1101/pinouts-and-buses.md b/devices/m5stack/cap-cc1101/pinouts-and-buses.md
deleted file mode 100644
index f005313..0000000
--- a/devices/m5stack/cap-cc1101/pinouts-and-buses.md
+++ /dev/null
@@ -1,196 +0,0 @@
-# Pinouts and buses — Cap CC1101 & NFC (U219)
-
-Snapshot 2026-09-04. Schematic **V0.3 / 2026-05-28**, 3 sheets. Nothing measured.
-
-## 1. Cap-Bus (`P1`, `HDR_14P-P2.54`)
-
-Numbering follows the **Cap page convention** (LEFT 1–7, RIGHT 14–8). See
-[`../cap-lora-1262/pinouts-and-buses.md` §1](../cap-lora-1262/pinouts-and-buses.md) for why
-two conventions exist for this connector.
-
-| Cap pin | Cap net | Host GPIO (Cardputer-Adv) | Direction | Function |
-|---:|---|---|---|---|
-| 1 | `CC1101_G0` | **G15** | O → host | CC1101 `GDO0`, via `R4` 330 Ω — packet interrupt |
-| 2 | `CC1101_RF_SW0` | **G13** (**G14** on CardputerZero) | I | Band select, bit 0 |
-| 3 | `SCL` | **G9** | I/O | I²C — Grove pass-through only |
-| 4 | `SDA` | **G8** | I/O | I²C — Grove pass-through only |
-| 5 | `5V_OUT` | — | P | 5 V from host |
-| 6 | `GND` | — | P | Ground |
-| 7 | *(unassigned on the vendor pin map)* | — | — | The LoRa Cap uses this as `5V_IN` |
-| **8** | **`POWER_EN`** | **G3** | I | **Enables the whole Cap's 3.3 V rail** |
-| 9 | `NFC_IRQ` | **G4** | O → host | ST25R3916 `IRQ` (pin 27) |
-| 10 | `NFC_CS` | **G6** | I | ST25R3916 `SS` (pin 29) |
-| 11 | `SPI_SCLK` | **G40** | I | shared SPI clock |
-| 12 | `SPI_MOSI` | **G14** | I | shared SPI MOSI |
-| 13 | `SPI_MISO` | **G39** | O | shared SPI MISO |
-| 14 | `CC1101_CS` | **G5** | I | CC1101 `CSN` (pin 7) |
-
-Confirmed by the schematic `P1` symbol (which annotates host GPIO alongside each net), the
-vendor pin-map graphic, and the Arduino guide's prose — three agreeing sources. **[SCH]**,
-**[DOC]**
-
-### 1.1 Compare with the Cap LoRa-1262 — the same connector, different meanings
-
-| Pin | Cap LoRa-1262 | Cap CC1101 |
-|---:|---|---|
-| 1 | `GPS_TX` (G15) | `CC1101_G0` (G15) |
-| 2 | `GPS_RX` (G13) | `CC1101_RF_SW0` (G13) |
-| 7 | `5V_IN` | unassigned |
-| **8** | **`LoRa_RST`** (G3) | **`POWER_EN`** (G3) |
-| 9 | `LoRa_IRQ` (G4) | `NFC_IRQ` (G4) |
-| 10 | `LoRa_BUSY` (G6) | `NFC_CS` (G6) |
-| 11–14 | SPI + `LoRa_NSS` | SPI + `CC1101_CS` |
-
-Only the SPI trio and the power/ground pins mean the same thing on both boards. **Firmware
-must know which Cap is fitted before it drives anything**, and there is no identity
-register on either board to ask (the LoRa Cap is inferred by probing I²C `0x43`; this Cap
-has no I²C device at all, so it cannot be probed the same way).
-
-### 1.2 The `GO`/`GI` extraction artifact appears here too
-
-As on the LoRa Cap schematic, the two I²C GPIO labels extract as `GO` and `GI`; there is no
-`G8`/`G9` token in the file. Correct values are `G8` = SDA, `G9` = SCL, established from the
-vendor pin map. Recorded so nobody chases a nonexistent net.
-
-## 2. Sheet map
-
-| Sheet | Title block | Contains |
-|---:|---|---|
-| 1 | *Cardputer-Adv MAP* / `2x7PDCDC` | `P1` Cap-Bus, `U1` JW5712 buck, `J1` Grove, `POWER_EN` |
-| 2 | *NFC* | `U2` ST25R3916, `Y1` 27.12 MHz, differential antenna matching, `ANT1`, 16 decoupling caps |
-| 3 | *SUB_1GHz* | `U3` CC1101, `B1` balun, `U4`/`U5` SP3T switches, three band paths, `Y2` 26 MHz, `E1` SMA |
-
-## 3. `U3` CC1101 — see the feature guide
-
-Full pin table in [`features/sub-ghz.md` §2](features/sub-ghz.md).
-
-## 4. `U2` ST25R3916 — pins in use
-
-**[SCH]** sheet 2. The complete generic pin table is in the
-[component record](../../../components/stmicroelectronics/st25r3916/README.md); this lists
-only what this board wires.
-
-| Pin | Name | Net |
-|---:|---|---|
-| 1 | `VDD_IO` | `VDD_3V3` |
-| 2 | `CSO` | — |
-| 3 | `VDD_D` | `VDD_3V3` |
-| 4 | `XTO` | `Y1` 27.12 MHz |
-| 5 | `XTI` | `Y1` 27.12 MHz |
-| 6, 12, 16, 26 | `GND` | `GND` |
-| 7 | `VDD_A` | `VDD_3V3` |
-| 8 | `VDD` | `+5V` |
-| 9 | `VDD_RF` | `VDD_3V3` |
-| 10 | `VDD_TX` | `+5V` |
-| 11 | `VDD_AM` | `VDD_3V3` |
-| **13** | `RFO1` | → `L3`/`R3` arm → `ANT1_N` |
-| 14 | `VDD_DR` | `VDD_3V3` |
-| **15** | `RFO2` | → matching → `ANT1_P` |
-| 17 | `EXT_LM` | wired — external load modulation for card emulation |
-| **18** | `AAT_A` | automatic antenna tuning |
-| **19** | `AAT_B` | automatic antenna tuning |
-| **20** | `I2C_EN` | **strapped for SPI** (`inferred` — the strap resistor was not identified) |
-| 21 | `VSS` | `GND` |
-| **22** | `RFI1` | `RFI_P` ← `C8` 10 pF |
-| **23** | `RFI2` | `RFI_N` ← `C17` 10 pF |
-| 24 | `AGDC` | — |
-| 25 | `CSI` | — |
-| **27** | `IRQ` | `NFC_IRQ` → Cap-Bus 9 → host **G4** |
-| 28 | `MCU_CLK` | — |
-| **29** | `SS` | `NFC_CS` → Cap-Bus 10 → host **G6** |
-| **30** | `SCLK` | `SPI_SCLK` → host **G40** |
-| **31** | `MOSI` | `SPI_MOSI` → host **G14** |
-| **32** | `MISO` | `SPI_MISO` → host **G39** |
-| 33 | `EPAD` | `GND` |
-
-> **`VDD` (8) and `VDD_TX` (10) come from `+5V`, not 3.3 V.** The ST25R3916 runs its
-> transmit driver from the higher rail for field strength while the digital and analogue
-> sections sit on 3.3 V. That is a design choice worth carrying over to any port — see
-> [`features/nfc.md` §10](features/nfc.md).
-
-## 5. Bus ownership
-
-| Bus | Devices | Selects |
-|---|---|---|
-| **SPI** (G40/G14/G39) | CC1101 (`CS` = G5), ST25R3916 (`CS` = G6), **host microSD** (`CS` = G12) | three chip selects, **two different SPI modes** — the NFC part wants mode 1 |
-| **I²C** (G8/G9) | **nothing on this Cap**; Grove pass-through only | — |
-| UART | **unused by this Cap** | the host's G13/G15 are repurposed as `RF_SW0` / `GDO0` |
-
-**Note what pin 2 costs you:** on the Cardputer-Adv, G13 is the EXT connector's UART pin.
-This Cap spends it as a static band-select line, so **you cannot have this Cap and a
-UART peripheral on the bus at the same time.**
-
-## 6. Host resource cost
-
-Nine host GPIO (G3, G4, G5, G6, G13, G14, G15, G39, G40) plus a share of SPI and the I²C
-pass-through — the same order of cost as the LoRa Cap, which is why the original Cardputer
-cannot take either.
-
----
-
-# 2026-09-07 — Cap-Bus pinout confirmed from the schematic
-
-Appended beneath the existing tables; **nothing above is altered.** Full trace with coordinates:
-[`schematic-netlist.md`](schematic-netlist.md). Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-
-## Connector `P1` = `HDR_14P-P2.54` — the same bus as the Cap LoRa-1262
-
-| Pin | Symbol pin name | Host GPIO | Functional net on U219 | Token |
-|---|---|---|---|---|
-| 1 | `GPS-TX` | `G15` | `CC1101_G0` | `PIP101` @ 648.00, 506.37 |
-| 2 | `GPS-RX` | `G13` | `CC1101_RF_SW0` | `PIP102` @ 648.00, 498.91 |
-| 3 | `SCL` | `GI` = **GPIO1** | `SCL` | `PIP103` @ 647.00, 491.37 |
-| 4 | `SDA` | `GO` = **GPIO2** | `SDA` | `PIP104` @ 648.00, 484.37 |
-| 5 | `5VOUT` | — | `+5VOUT` | `PIP105` @ 648.00, 477.37 |
-| 6 | `GND` | — | `GND` | `PIP106` @ 648.00, 470.37 |
-| 7 | `5VIN` | — | `+5VIN` | `PIP107` @ 648.00, 462.91 |
-| **8** | `RESET` | **`G3`** | **`POWER_EN`** | `PIP108` @ 575.00, 462.91 |
-| 9 | `INT` | `G4` | `NFC_IRQ` | `PIP109` @ 575.00, 470.37 |
-| 10 | `BUSY` | `G6` | `NFC_CS` | `PIP1010` @ 575.00, 477.37 |
-| 11 | `SCK` | `G40` | `SPI_SCLK` | `PIP1011` @ 575.00, 484.37 |
-| 12 | `MOSI` | `G14` | `SPI_MOSI` | `PIP1012` @ 575.00, 491.37 |
-| 13 | `MISO` | `G39` | `SPI_MISO` | `PIP1013` @ 575.00, 498.91 |
-| 14 | `CS` | `G5` | `CC1101_CS` | `PIP1014` @ 575.00, 504.84 |
-
-## Pin 8 — the reported conflict, resolved
-
-The connector, the pin number, the symbol pin name (`RESET`) and the host GPIO (`G3`) are
-**identical** to the Cap LoRa-1262's. Only the board function differs:
-
-- **U214 Cap LoRa-1262:** `G3` → net `RST` → `M1` pin 2 `NRST` — the SX1262's reset.
-- **U219 Cap CC1101:** `G3` → net `POWER_EN` (@ 535.08, 258.46 and 146.12, 258.46) → `R1`
-  100 kΩ and `U1`'s `EN` ball. `U1` is this board's own step-down converter — the same
-  `JW5712` ball map (`EN`/`SW`/`VIN`/`VOS`/`VSEL1..3`/`GND`), `IOUT: 0~0.6A` annotation,
-  `L1` `MWTC201608S2R2` 2.2 µH.
-
-**So `G3` gates the CC1101 board's own 3.3 V rail.** Driving it low removes power from the radio,
-rather than resetting it. That is a materially different behaviour from the LoRa board and must
-not be assumed portable between them.
-
-⚠ The reported "conflict" was therefore never a disagreement about the bus pinout. It is a
-per-board function assignment on a stable, shared bus line.
-
-## ⚠ `NFC_IRQ` and `NFC_CS` are vestigial net names
-
-Bus pins 9 and 10 carry the names `NFC_IRQ` (@ 531.24, 265.65 p1; 192.64, 265.65 p2) and
-`NFC_CS` (@ 529.74, 272.84 p1; 191.14, 280.03 p2). **No NFC controller appears anywhere in this
-document's designator census.** They read as names inherited from a sibling design. Recorded so
-nobody goes looking for a part that is not fitted; the routing above is what matters.
-
-## Off-sheet nets (sheet 1 ↔ sheet 3)
-
-Connectivity between sheets is by net name only, and these occurrences are the only evidence of
-it:
-
-| Net | Sheet 1 | Sheet 3 |
-|---|---|---|
-| `CC1101_CS` | 534.06, 301.59 | 101.69, 107.27 |
-| `CC1101_G0` | 706.90, 301.59 | 101.63, 121.64 |
-| `CC1101_RF_SW0` | 715.06, 294.40 | 95.41, 380.66 · 563.75, 373.48 |
-| `CC1101_RF_SW1` | — | 109.79, 128.83 · 95.41, 373.47 · 563.75, 380.66 |
-| `CC1101_RF` | — | 750.13, 359.10 · 750.13, 481.54 |
-| `I2C_EN` | — | p2: 259.66, 254.87 |
-
-`CC1101_RF_SW0`/`SW1` appear at two x positions on sheet 3 in the same two rows, crossed — the
-signature of an antenna-path RF switch driven by two complementary control lines.
diff --git a/devices/m5stack/cap-cc1101/projects-and-community.md b/devices/m5stack/cap-cc1101/projects-and-community.md
deleted file mode 100644
index db775c5..0000000
--- a/devices/m5stack/cap-cc1101/projects-and-community.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Projects and community — Cap CC1101 & NFC (U219)
-
-**Released 2026-08-28. This snapshot is 2026-09-04.** There are, as of this date, **no
-projects** — only anticipation, ordering intent, and a year-long wait. That is itself the
-finding, and it is recorded rather than padded.
-
-## 1. The wait — a documented eleven-month slip
-
-| Date | Event | Source |
-|---|---|---|
-| **2025-09-08** | An owner emails M5Stack about the *"Cardputer ADV Hacker cap (CC1101 SubGHz & ST25R3916 RFID)"* and posts the reply: **"release will be in around 3-4 months, either in December or January"**. Both chips named correctly, a year early | [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1nbe134/), 20 pts |
-| 2025-09-08 | In the same thread, u/RJ01988 says he *started making a CC1101 module* for the ADV and is *"waiting to find out the correct pinout required for Bruce"*; u/heytheremonkeyboy points at [`pr3y/Bruce` commit `34aabec`](https://github.com/pr3y/Bruce/commit/34aabecb3e7b1b6ad9a64176e6fa0aa0c9da90ec) for v1.1 pinouts | same |
-| 2025-09-08 | The community wish, stated plainly by u/heytheremonkeyboy: *"Will be interesting to see how many modules we can run in one Cap with the extra GPIO pins. Would love to have a CC1101/GPS/NRF24/RFID/LoRa all in one."* | same |
-| **2026-01-31** | u/Relevant-Lynx-6688: *"Hi guys, do you have any updates about the release of this cap?"* — **no reply** | same |
-| **2026-08-28** | Ships | [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1w0nwti/) |
-
-## 2. Release-day thread — what was actually established
-
-[r/CardPuter, 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/), 41 upvotes,
-16 comments. The most technically substantive post about this board anywhere.
-
-**From M5Stack's community manager (the OP):**
-
-> *"The Cap CC1101 module supports multiple frequency bands: 315 / 433 / 868 / 915 MHz,
-> which can be switched via firmware using a combination of **G13 (Cardputer ADV) or G14
-> (CardputerZero) as SW0 and GDO2 from the CC1101 as SW1**."*
-
-This is the **only** published statement of the CardputerZero pin difference, and it
-independently confirms the architecture read from the schematic. **[COM]**, but corroborated.
-
-> *"M5Stack also expanding the Cardputer lineup with the **Cardputer P4 (Next)**. It is
-> still in the development phase … Compared to the Cardputer ADV, it adds Ethernet, HDMI…"*
-
-Followed by an exchange establishing the P4 uses an **ESP32-C5 co-processor** for Wi-Fi/BLE
-(u/A31Nesta: *"there are older photos of the board … they mentioned it in a twitter reply"*),
-with hopes for the P4X rather than the EOL original P4. **Speculation about an unreleased
-product**, recorded as such.
-
-**The recurring question, correctly answered twice:** can the CC1101 do LoRa? No — see
-[README §6](README.md).
-
-**What it is for**, per u/No_Confusion7932: *"Copy/read/transmit signals on the specified
-frequencies, and jam. The CC1101 also has a longer range."* The "jam" part is illegal
-essentially everywhere; recorded because it is what the community says, not as a
-recommendation. Same commenter links a YouTube demonstration of CC1101 use under Bruce
-firmware on a different device (`youtube.com/watch?v=BUwrWKDqtak`, 7:28–8:51) — **not
-watched** by this pass.
-
-**On firmware readiness:** *"The dev will still need to implement band switching, which
-shouldn't be too difficult, since M5Stack has already published examples for this on their
-website."* So **Bruce does not support this Cap yet** as of 2026-08-28.
-
-## 3. Ordering intent (all the field evidence there is)
-
-u/Zatoichi80: *"I have mine ordered with the Zero, good to see more info on it."*
-u/Awkward_Can_1516: *"Ordered!"* — 4 upvotes each. u/zellotron on the P4: *"Very keen …
-but it better damn well have PSRAM!"*
-
-**No owner has posted a photograph, a measurement, or a working result.**
-
-## 4. Adjacent projects that will probably adopt it
-
-| Project | Why |
-|---|---|
-| **Bruce** (`pr3y/Bruce`) | The de-facto sub-GHz/RF firmware for the Cardputer family; already supports CC1101 on other hardware. Needs band-switch support |
-| **M5Launcher** (`bmorcelli`) | The launcher most owners use; its author is active in Cardputer threads |
-| **M5Stack `M5Unit-NFC`** | **Already supports it** — the only software that does, and it shipped 11 weeks early |
-
-## 5. Evidence discipline
-
-Every item above is announcement, ordering intent, informed interpretation, or a direct
-quote of a vendor email. **None of it is measurement, and none of it is a firsthand use
-report.** Anyone reading this after ~2026-10 should re-search: this section will be
-obsolete, and that is a good thing.
diff --git a/devices/m5stack/cap-cc1101/research-log.md b/devices/m5stack/cap-cc1101/research-log.md
deleted file mode 100644
index e021128..0000000
--- a/devices/m5stack/cap-cc1101/research-log.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# Research log — Cap CC1101 & NFC (U219)
-
-Single pass, **2026-09-04** — **seven days after the product went on sale.** No hardware.
-
-## Why this record exists in the shape it does
-
-The task brief identified the Cap LoRa-1262 as "the newest one, released ~August/September
-2026". Checking that claim against `shop.m5stack.com`'s Shopify JSON showed the LoRa Cap
-was published **2025-12-30**, and that the product actually published in that window was
-**this** board — `published_at 2026-08-28T12:00:54+08:00`, created 72 minutes earlier the
-same morning. So the "brand-new" half of the brief resolves to U219, and this record was
-given full depth accordingly.
-
-## Sources searched
-
-| Class | Searched? | Notes |
-|---|---|---|
-| Manufacturer docs | ✅ | Product page + Arduino guide (62 821 B of extracted text) |
-| Manufacturer store | ✅ | Product JSON + full 662-product catalogue |
-| Manufacturer repositories | ✅ | `org:m5stack cc1101` → **0**; `M5Unit-NFC` walked (230 blobs) |
-| Component datasheets | ✅ | CC1101 (TI, via M5Stack mirror), ST25R3916 (ST, via M5Stack — **duplicate detected**) |
-| Framework/library | ✅ | RadioLib, M5Unit-NFC |
-| Community | ✅ | Reddit; **very thin** — the board is 7 days old |
-| Regulatory | ❌ | Declared exclusion |
-| Distributors / marketplaces | ❌ | Declared exclusion |
-| `community.m5stack.com` | ❌ | Declared exclusion |
-| Video | ❌ | The product page's Video section was empty at retrieval |
-
-## Query ledger
-
-| Service | Query | Result |
-|---|---|---|
-| `docs.m5stack.com/en/cap/Cap_CC1101` | direct | 200, 138 934 B |
-| `docs.m5stack.com/en/arduino/projects/cap/cap_cc1101` | direct | 200, 456 766 B |
-| `shop.m5stack.com/products/cap-cc1101-nfc-for-cardputer.json` | direct | 200 — **the release date** |
-| GitHub search | `org:m5stack cc1101` | **0 repositories** (negative result) |
-| GitHub API | `repos/m5stack/M5Unit-NFC/git/trees/main?recursive=1` | 230 blobs; `CapCC1101NFC` located in `src/M5UnitUnifiedNFC.hpp` |
-| GitHub API | `repos/m5stack/M5Unit-NFC/commits?per_page=10` | head 2026-06-10 — **library predates the product by 11 weeks** |
-| `old.reddit.com/search.json` | `"Cap CC1101"` | 1 substantive thread (the announcement) |
-| `old.reddit.com` | `/r/CardPuter/comments/1w0nwti/`, `/1nbe134/` | full comment trees |
-
-## What changed the conclusions
-
-1. **The release-date correction** (above) — this is the new board, not the LoRa Cap.
-2. **The band-switch architecture.** Reading sheet 3 showed `CC1101_RF_SW1` never leaves the
-   PCB; it comes from the CC1101's own `GDO2`. The vendor's Arduino guide and a vendor
-   Reddit comment independently confirm it. That is the board's genuinely novel idea and it
-   got its own feature guide.
-3. **The NFC interface strap.** Same ST25R3916 as the PaperMono, but **SPI** here vs **I²C**
-   there. The existing component record covers everything above the transport, so this
-   record documents the delta rather than duplicating 555 lines.
-4. **The duplicate datasheet.** The ST25R3916 PDF at `/1229/` is byte-identical to the copy
-   already in the repository. Recorded as an extra URL; not stored twice.
-5. **The library-before-product finding.** `CapCC1101NFC` existed on 2026-06-10 with the
-   README stating *"included in this library for future use"*. Useful because it means the
-   driver is not speculative.
-6. **The 11-month slip.** A 2025-09-08 owner post quotes M5Stack predicting December 2025.
-
-## Negative results kept
-
-- No M5Stack CC1101 library.
-- No certification identifier.
-- **No firsthand use report of this board anywhere** — every community mention is
-  announcement, ordering intent, or correct-but-theoretical explanation.
-- No Bruce/M5Launcher support yet; band switching explicitly noted as still to be
-  implemented.
-
-## Stopping criterion
-
-Stopped when the schematic's text layer was exhausted (six remaining gaps all require a
-**render**, which this host cannot do without poppler), the vendor's two pages were fully
-extracted, and Reddit returned no further threads. **Declared exclusions:** regulatory
-databases, marketplaces, `community.m5stack.com`, UiFlow2 zh-cn page, schematic page
-renders, remaining product photography.
-
-**Re-search advice:** this record is dated within a week of release. Anyone reading it after
-~2026-10 should expect real field evidence to exist and should treat
-[`compatibility-and-status.md`](compatibility-and-status.md) as stale.
diff --git a/devices/m5stack/cap-cc1101/schematic-netlist.md b/devices/m5stack/cap-cc1101/schematic-netlist.md
deleted file mode 100644
index bebde00..0000000
--- a/devices/m5stack/cap-cc1101/schematic-netlist.md
+++ /dev/null
@@ -1,108 +0,0 @@
-# Cap CC1101 (U219) — net list traced from `U219-Cap_CC1101_SCH_V0.3_20260528.pdf`
-
-**Traced:** 2026-09-07 · **Method:**
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md)
-· **Tool:** poppler 26.06.0.
-
-**New file.** Corrections to existing claims are appended to `pinouts-and-buses.md` and listed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-## 0. Traceability
-
-3 pages, `Creator: Altium Designer`, **0 embedded rasters**, 974 words, full `CO`/`PI` coverage,
-**no `NL` tokens** (same export setting as the Cap LoRa-1262). **Fully traceable.**
-
----
-
-## 1. `P1` — Cap-Bus connector, `HDR_14P-P2.54`
-
-Same connector part, same symbol pin names and same host-GPIO aliases as the Cap LoRa-1262. The
-functional aliases differ, because they describe what *this* board does with each line.
-
-| Pin | Symbol pin name | Host GPIO | Functional net on U219 | Pin token |
-|---|---|---|---|---|
-| 1 | `GPS-TX` | `G15` | `CC1101_G0` | `PIP101` @ 648.00, 506.37 |
-| 2 | `GPS-RX` | `G13` | `CC1101_RF_SW0` | `PIP102` @ 648.00, 498.91 |
-| 3 | `SCL` | `GI` (GPIO1) | `SCL` | `PIP103` @ 647.00, 491.37 |
-| 4 | `SDA` | `GO` (GPIO2) | `SDA` | `PIP104` @ 648.00, 484.37 |
-| 5 | `5VOUT` | — | `+5VOUT` | `PIP105` @ 648.00, 477.37 |
-| 6 | `GND` | — | `GND` | `PIP106` @ 648.00, 470.37 |
-| 7 | `5VIN` | — | `+5VIN` | `PIP107` @ 648.00, 462.91 |
-| **8** | `RESET` | **`G3`** | **`POWER_EN`** | `PIP108` @ 575.00, 462.91 |
-| 9 | `INT` | `G4` | `NFC_IRQ` | `PIP109` @ 575.00, 470.37 |
-| 10 | `BUSY` | `G6` | `NFC_CS` | `PIP1010` @ 575.00, 477.37 |
-| 11 | `SCK` | `G40` | `SPI_SCLK` | `PIP1011` @ 575.00, 484.37 |
-| 12 | `MOSI` | `G14` | `SPI_MOSI` | `PIP1012` @ 575.00, 491.37 |
-| 13 | `MISO` | `G39` | `SPI_MISO` | `PIP1013` @ 575.00, 498.91 |
-| 14 | `CS` | `G5` | `CC1101_CS` | `PIP1014` @ 575.00, 504.84 |
-
-## 2. Pin 8 — what `POWER_EN` actually controls
-
-`POWER_EN` appears twice on sheet 1: at (535.08, 258.46) beside `P1` pin 8, and at
-(146.12, 258.46) in the power block, where `netlist.py --components` reports
-
-```
-p1 R1  x=163.00 y=271.66  R1(2) | 100KΩ(11) | B1(20) | A2(21) | POWER_EN(21) | EN(34)
-p1 U1  x=189.00 y=250.20  U1(2) | EN(14) | B1(14) | IOUT:(28) | R1(34) | SW(40)
-```
-
-`U1` is the board's own step-down converter (`EN`/`SW`/`VIN`/`VOS`/`VSEL1..3`/`GND` ball map,
-`IOUT: 0~0.6A` annotation, `L1` `MWTC201608S2R2` 2.2 µH). `R1` is **100 kΩ** here, and the `EN`
-ball is driven by `POWER_EN` = host `G3`.
-
-**So on the Cap CC1101 the host GPIO on bus pin 8 gates the daughterboard's own 3.3 V rail.**
-On the Cap LoRa-1262 the equivalent ball is instead tied high through `R1` 10 kΩ to the input
-rail, and bus pin 8 goes to the SX1262's `NRST`.
-
-This is the whole of the reported "pin 8 conflict":
-
-- the **bus** pinout is identical on both boards — same connector, same pin number, same symbol
-  name `RESET`, same host GPIO `G3`;
-- the **board function** of that line is defined by the daughterboard, and the two boards define
-  it differently.
-
-Practical consequence for firmware: driving `G3` low on a Cap CC1101 **removes power from the
-radio**, whereas on a Cap LoRa-1262 it merely asserts the radio's reset. Code written for one
-must not be reused on the other without changing the meaning of that pin.
-
-## 3. ⚠ `NFC_IRQ` and `NFC_CS` — vestigial net names
-
-Bus pins 9 and 10 carry the net names `NFC_IRQ` (@ 531.24, 265.65 p1; also @ 192.64, 265.65 p2)
-and `NFC_CS` (@ 529.74, 272.84 p1; @ 191.14, 280.03 p2). **No NFC controller appears anywhere in
-this document's designator census.** These read as names carried over from a sibling design that
-did have one.
-
-Recorded, not resolved: the names are misleading but the electrical routing is what matters, and
-it is given above. Do not search for an NFC part on this board on the strength of them.
-
-## 4. Off-sheet nets
-
-Sheet 1 ↔ sheet 3 connectivity is by net name only, and it is the only evidence of it:
-
-| Net | Sheet 1 | Sheet 3 |
-|---|---|---|
-| `CC1101_CS` | 534.06, 301.59 | 101.69, 107.27 |
-| `CC1101_G0` | 706.90, 301.59 | 101.63, 121.64 |
-| `CC1101_RF_SW0` | 715.06, 294.40 | 95.41, 380.66 · 563.75, 373.48 |
-| `CC1101_RF_SW1` | — | 109.79, 128.83 · 95.41, 373.47 · 563.75, 380.66 |
-| `CC1101_RF` | — | 750.13, 359.10 · 750.13, 481.54 |
-| `NFC_IRQ`, `NFC_CS` | 531.24 / 529.74, 265.65 / 272.84 | p2: 192.64 / 191.14 |
-| `I2C_EN` | — | p2: 259.66, 254.87 |
-
-`CC1101_RF_SW0` / `CC1101_RF_SW1` appear at two x positions on sheet 3 in the same two rows
-(95.41 and 563.75, y 373.47/380.66) — an RF switch with the two control lines crossed between
-its two ports, which is what an antenna-path selector looks like. `CC1101_RF` appears twice on
-sheet 3 at the same x, 122 pt apart in y: the two ends of the RF path.
-
----
-
-## Reproducing
-
-```bash
-nix-shell -p poppler-utils --run 'pdftotext -bbox-layout \
-  "devices/m5stack/cap-cc1101/artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf" /tmp/u219.xhtml'
-cd scratch/schematic-tracing
-python3 render.py  /tmp/u219.xhtml --page 1 --x0 490 --x1 750 --y0 245 --y1 320
-python3 netlist.py /tmp/u219.xhtml --components | grep -E ' (U1|P1|R1) '
-python3 trace.py   grep /tmp/u219.xhtml 'CC1101_|NFC_'      # the off-sheet census
-```
diff --git a/devices/m5stack/cap-cc1101/sources.md b/devices/m5stack/cap-cc1101/sources.md
deleted file mode 100644
index d74d308..0000000
--- a/devices/m5stack/cap-cc1101/sources.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Sources — Cap CC1101 & NFC (U219)
-
-All retrieved **2026-09-04**.
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Published/updated | Establishes | Limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| S-1 | Cap CC1101 product documentation | M5Stack | primary | official page | `https://docs.m5stack.com/en/cap/Cap_CC1101` | 2026-09-04 | undated | SKU U219, chips (CC1101 + ST25R3916), dual SP3T switch architecture, **RF-switch truth table**, Cap-Bus pin map, host GPIO map, three antennas, currents, dimensions | Undated | `scratch/m5stack-lora-expansions/docs-html/Cap_CC1101.html` |
-| S-2 | Cap CC1101 store listing (Shopify JSON) | M5Stack | primary | store listing | `https://shop.m5stack.com/products/cap-cc1101-nfc-for-cardputer.json` | 2026-09-04 | **published_at 2026-08-28T12:00:54+08:00**, created 2026-08-28T10:48:38+08:00 | **The release date** — the newest board in the family. Product 9328460431617, variant 50248139571457, SKU U219, USD 18.95 | machine-readable | `scratch/…/shop/cap-cc1101-nfc-for-cardputer.json` |
-| S-3 | Cap CC1101 schematic | M5Stack | primary | schematic PDF | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1250/SCH_Cap_CC1101_SCH_V0.3_20260528.pdf` | 2026-09-04 | **V0.3, 2026-05-28**, 3 sheets | Full designator census; `U2` ST25R3916-AQWT pinout and matching network; `U3` CC1101RGPR pinout; `U4`/`U5` BGS13SN8; `B1` balun; `Y1` 27.12 MHz / `Y2` 26 MHz; `POWER_EN`→`U1` ENB | Text-layer extraction only; **not rendered** — the on-sheet truth table and several strap resistors were not recoverable | [`artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf`](artifacts/schematic/U219-Cap_CC1101_SCH_V0.3_20260528.pdf) — 485 518 B, `sha256 2c24e78ff5fff44ca2ddb274ad4a514fb736caefb5c8969dacf57f481a965e0b` |
-| S-4 | Cap CC1101 model-size drawing | M5Stack | primary | mechanical PDF | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1250/U219_Cap_CC1101_model_size.pdf` | 2026-09-04 | undated | Outline dimensions | Not transcribed | [`artifacts/mechanical/U219-Cap_CC1101_model_size.pdf`](artifacts/mechanical/U219-Cap_CC1101_model_size.pdf) — 41 925 B, `sha256 f0e6e622847ef5546501b7ca937a16daa0b57b89cec21c85251f6752c6c766e4` |
-| S-5 | Cap CC1101 Arduino guide | M5Stack | primary | tutorial | `https://docs.m5stack.com/en/arduino/projects/cap/cap_cc1101` | 2026-09-04 | undated | **The band-switch code** (`RADIOLIB_CC1101_GDOX_HW_TO_0` / `GDO2_INV`), the RadioLib CC1101 parameters, the `M5UnitUnifiedNFC` SPI mode-1 / 10 MHz init, the pin prose | 62 821 B of extracted text; NFC examples skimmed, not exhaustively read | `scratch/…/docs-html/en_arduino_projects_cap_cap_cc1101.txt` |
-| S-6 | CC1101 datasheet | Texas Instruments, mirrored by M5Stack | authorized mirror | datasheet | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1188/CC1101_Datasheet.pdf` | 2026-09-04 | undated in filename | The transceiver | Served from M5Stack's `/1188/` path (the **M146 CC1101 Module** product), not a U219 path — a **vendor mirror**, revision unverified against TI's own | [`components/texas-instruments/cc1101/artifacts/cc1101-datasheet-m5stack-mirror.pdf`](../../../components/texas-instruments/cc1101/README.md) — 2 718 663 B, `sha256 0c5cdadd06a9f8de6776dda8c8fb29c5029baa2838413335270e223e55a4e169` |
-| S-7 | ST25R3916 datasheet | STMicroelectronics, mirrored by M5Stack | authorized mirror | datasheet | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1229/st25r3916_datasheet.pdf` | 2026-09-04 | — | The NFC front end | **Byte-identical** to the copy already in the repository (`sha256 1170f4d7…`, 2 241 765 B) — **not stored twice**; this URL recorded as an additional source | [`components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf`](../../../components/stmicroelectronics/st25r3916/README.md) |
-| S-8 | `m5stack/M5Unit-NFC` | M5Stack | primary | repository | `https://github.com/m5stack/M5Unit-NFC` | 2026-09-04 | head `93745b547364f310cd64b5155a870103a7800a5d` 2026-06-10; release **0.1.0** 2026-06-10; **MIT** | `using CapCC1101NFC = m5::unit::CapST25R3916;`, `USING_CAP_CC1101`, the example matrix, PICC support table, the SoftwareI2C latency warning | — | `scratch/…/github/M5UnitUnifiedNFC.hpp`, `M5Unit-NFC-README.md` |
-| S-9 | RadioLib | jgromes | primary | repository | `https://github.com/jgromes/RadioLib` | 2026-09-04 | rel **7.7.1** 2026-05-31; head `187ef247…` 2026-08-22; **MIT** | The CC1101 driver the vendor links to | — | — |
-| S-10 | "Cap CC1101 & NFC … is already in the store" | M5Stack community manager, r/CardPuter | community | social post | `https://old.reddit.com/r/CardPuter/comments/1w0nwti/` | 2026-09-04 | **2026-08-28**, 41 pts / 16 comments | **Independent statement of the band-switch mechanism** (`G13` on ADV, **`G14` on Zero**, `GDO2` as SW1); Cardputer P4 compatibility claim; the CC1101-cannot-do-LoRa explanations | Vendor-adjacent poster; the technical content matches the schematic | `scratch/…/reddit/t-cc1101-announce.json` |
-| S-11 | "Cardputer ADV Hacker cap … expected release" | r/CardPuter | community | forum thread | `https://old.reddit.com/r/CardPuter/comments/1nbe134/` | 2026-09-04 | **2025-09-08** | An owner's quote of an M5Stack email predicting Dec-2025/Jan-2026; both chips named correctly a year before release; the community wish for a combined CC1101/GPS/NRF24/RFID/LoRa cap | Hearsay of a vendor email, but a direct quote | `scratch/…/reddit/t-cc1101-teaser-2025.json` |
-| S-12 | Bruce Cardputer v1.1 pinouts commit | pr3y/Bruce | community | repository | `https://github.com/pr3y/Bruce/commit/34aabecb3e7b1b6ad9a64176e6fa0aa0c9da90ec` | not fetched | 2025-09 | Cited in S-11 as the reference for Cardputer pinouts in Bruce | **Not fetched** in this pass | — |
-| S-13 | Cardputer Mesh Kit page (EXT connector table) | M5Stack | primary | official page | `https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit` | 2026-09-04 | undated | The host-side EXT 2.54-14P numbering used in §1.1 comparisons | Its UART labels are backwards — see the LoRa Cap record | `scratch/…/docs-html/Cardputer_Mesh_Kit.html` |
-| S-14 | M5Stack GitHub org search for `cc1101` | GitHub | primary | repository | `https://api.github.com/search/repositories?q=org:m5stack+cc1101` | 2026-09-04 | — | **Negative result: 0 repositories.** No M5Stack CC1101 driver | `executed-success` | — |
-
-## Not fetched, known to exist
-
-| What | URL |
-|---|---|
-| UiFlow2 MicroPython API (zh-cn path linked from the English page) | `https://uiflow-micropython.readthedocs.io/zh-cn/latest/cap/cc1101.html` |
-| Schematic page renders | `…/1250/SCH_Cap_CC1101_SCH_V0.3_20260528_page_0{1,2,3}.png` — **these would close six of the twelve gaps** |
-| Remaining seven product photos, weight photo | `…/1250/U219_Cap_CC1101_main_pictures_{04,06..11}.webp`, `U219_Cap_CC1101_weight.jpg` |
-| Bruce pinout commit | `github.com/pr3y/Bruce/commit/34aabecb…` |
diff --git a/devices/m5stack/cap-lora-1262/README.md b/devices/m5stack/cap-lora-1262/README.md
deleted file mode 100644
index 29430dc..0000000
--- a/devices/m5stack/cap-lora-1262/README.md
+++ /dev/null
@@ -1,224 +0,0 @@
-# M5Stack Cap LoRa-1262 (SKU U214)
-
-> **What it is:** a 14-pin expansion board ("Cap") for the **Cardputer-Adv** and
-> **CardputerZero**, carrying a **Semtech SX1262** LoRa radio in an M5Stack
-> `Stamp LoRa-1262 Mini` module *and* an **ATGM336H-6N** GNSS receiver, plus a
-> `PI4IOE5V6408` I/O expander, a `MAX2659` GNSS LNA, a `JW5712` buck and a
-> pass-through Grove port.
->
-> **Snapshot:** 2026-09-04 · **Schematic revision documented: V1.1, dated 2025-10-29**
-> · nothing tested on hardware.
-
----
-
-## ⚠ Read this first: the release date in circulation is wrong
-
-**Cap LoRa-1262 is not a new product.** It was published to M5Stack's store on
-**2025-12-30**, more than eight months before this snapshot. The board that shipped
-in **August 2026** is its sibling, the [**Cap CC1101 & NFC**](../cap-cc1101/README.md)
-(2026-08-28). §2 lays out the primary evidence and the full family timeline.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[SCH]** | Read out of `U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf`, held in [`artifacts/schematic/`](artifacts/schematic/) | `executed-success` for the extraction; `not-tested` electrically |
-| **[DOC]** | `docs.m5stack.com/en/cap/Cap_LoRa-1262`, retrieved 2026-09-04 | `not-tested` |
-| **[SHOP]** | `shop.m5stack.com` product JSON, retrieved 2026-09-04 | machine-readable, `executed-success` |
-| **[SRC]** | Source code read at a cited path/commit | `executed-success` for the read |
-| **[COM]** | Community report — Reddit thread, cited by permalink and date | `reported-working` at best |
-| **[INF]** | Inference | `inferred` |
-
----
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketed name | **Cap LoRa-1262** (store title: *Cap LoRa 1262 for Cardputer Adv (SX1262, ATGM336H)*) | **[DOC]**, **[SHOP]** |
-| SKU | **U214** | **[DOC]** header, **[SHOP]** variant SKU |
-| Shopify product id / variant id | `8988582248705` / `47023567274241` | **[SHOP]** |
-| Store publish date | **2025-12-30T09:27:06+08:00** (created 2025-12-25T18:14:13+08:00) | **[SHOP]** |
-| List price | **USD 14.50** | **[SHOP]** |
-| Documented schematic revision | **V1.1, 2025-10-29** (file uploaded 2025-11-07) | **[SCH]** filename + title block |
-| Host compatibility | **Cardputer-Adv**, **CardputerZero**; announced as compatible with the unreleased **Cardputer P4 (Next)** | **[DOC]**; P4 claim is **[COM]** — M5Stack community manager, [r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/) |
-| ❌ Not compatible with | **the original Cardputer (K132 / K132-V11)** — it has no expansion bus, only a Grove port | **[DOC]** Cardputer spec table; **[COM]** |
-| Bus | **Cap-Bus**, a 14-pin 2.54 mm header (`HDR-SMD_14P-P2.54`, designator `P1`) that mates with the Cardputer-Adv **EXT 2.54-14P** | **[SCH]**, **[DOC]** |
-| Extra connector | **HY2.0-4P Grove** (`J2`, `GROVE 4P`) carrying `5V / GND / SDA / SCL` — pass-through of the host I²C bus | **[SCH]**, **[DOC]** |
-| Size / weight | 84.0 × 24.0 × 15.2 mm · 22.1 g excl. antenna | **[DOC]** |
-| Predecessor | [**Cap LoRa868 / U201**](../cap-lora868/README.md), published 2025-09-05, now **[EOL]** | **[SHOP]**, **[DOC]** |
-| Sold inside | [**Cardputer Mesh Kit / K152**](../cardputer-mesh-kit/README.md) (Cardputer-Adv + this Cap), published 2026-04-30 | **[DOC]**, **[SHOP]** |
-
-### 1.1 One SKU, no regional variants — and that matters
-
-There is **one** Cap LoRa-1262. The band is **868–923 MHz** as a single wideband range,
-covering EU 868, US 915 and JP 920/923 allocations with no per-region part number, no
-per-region antenna in the box, and **no published certification identifier of any kind**
-(`docs.m5stack.com/en/certification` lists nothing for `U214`, `Cap LoRa`, or `Cardputer`).
-See [`features/lora.md` §7](features/lora.md) for what that means legally and practically.
-
----
-
-## 2. Where this board sits in the family — dated, from primary evidence
-
-Every date below is a Shopify `published_at` from `shop.m5stack.com/products/<handle>.json`,
-retrieved 2026-09-04. **[SHOP]**
-
-| Date | SKU | Product | Price (USD) | Relevance |
-|---|---|---|---|---|
-| 2023-10-13 | K132 | M5Stack Cardputer Kit w/ M5StampS3 **[EOL]** | 23.90 | The original. **Grove port only** — no Cap can attach |
-| 2023-10-20 | U170 | LoRa Unit with Antenna (E220) | 33.00 | Grove/UART LoRa modem — attaches to *any* Cardputer |
-| 2024-07-12 | U170-433 | LoRa Unit 433 MHz (E220) | 12.95 | ditto, 433 MHz |
-| 2024-12-20 | U184-\* | LoRaWAN Unit EU868/US915/AS923/CN470 (STM32WLE5) | 18.95–21.50 | Grove/UART LoRaWAN modem |
-| 2025-03-07 | K132-V11 | Cardputer with M5StampS3 v1.1 **[EOL]** | 29.90 | still Grove-only |
-| **2025-09-05** | **K132-ADV** | **M5Stack Cardputer Adv** | 29.90 | **introduces the EXT 2.54-14P bus** |
-| **2025-09-05** | **U201** | **LoRa+GPS Cap for Cardputer Adv** ("Cap LoRa868") **[EOL]** | 14.50 | **the first Cardputer LoRa expansion** |
-| 2025-10-10 | U202 | M5Stack C6L Unit for Meshtastic (SX1262 + ESP32-C6) | 22.90 | Grove-attached *self-contained* Meshtastic node |
-| 2025-11-07 | M146 | M5Stack CC1101 Module (855–925 MHz) | 10.95 | Core-bus module, **not** Cardputer |
-| **2025-12-30** | **U214** | **Cap LoRa-1262** ← *this record* | 14.50 | supersedes U201 |
-| 2026-03-13 | S012 | [M5Stamp C6LoRa](../stamp-c6lora/README.md) | 12.95 | solder-down module, not an expansion |
-| 2026-04-30 | K152 | [Cardputer Mesh Kit](../cardputer-mesh-kit/README.md) | 48.00 | ADV + U214 + antenna, Meshtastic-licensed |
-| **2026-08-28** | **U219** | [**Cap CC1101 & NFC**](../cap-cc1101/README.md) | 18.95 | **the genuinely new board** |
-
-**Corroboration for the U214 date, independent of Shopify:** M5Stack's own announcement
-post *"New Arrival Alert! Cap LoRa 1262 Available Now!"* was posted to
-[r/M5Stack](https://old.reddit.com/r/M5Stack/comments/1pzazbe/) and
-[r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1pzazuu/) on **2025-12-30**. **[COM]**
-
-**Third line of evidence:** the documentation CDN allocates a per-product numeric prefix in
-release order — `1208` = U214, `1223` = S012, `1240` = K152, `1250` = U219. U214's assets sit
-*below* all three of the 2026 products. **[DOC]**, `inferred` for the ordering rule.
-
-### 2.1 What changed from Cap LoRa868 (U201) to Cap LoRa-1262 (U214)
-
-M5Stack publishes a comparison table on the U214 page. **[DOC]**
-
-| Feature | Cap LoRa868 (U201) | Cap LoRa-1262 (U214) |
-|---|---|---|
-| HY2.0-4P Grove expansion | **No** | **Yes** |
-| LoRa module | `Stamp LoRa-1262` — "legacy version, standard size" | `Stamp LoRa-1262` **Mini**, smaller |
-| RF shielding can | **No** | **Yes** |
-| RF switch control | **None** | **via I/O expander** (`PI4IOE5V6408` P0) |
-| TX power (vendor claim) | **+20 dBm** | **+22 dBm** |
-| Performance | — | "Better" |
-
-Owner reaction on release day was that this is an incremental refresh, not a fix:
-u/griffog asked *"was there an issue with the original cap … or does this just have the
-addition of the I2C port?"*, and M5Stack-adjacent poster u/truthfly replied
-*"Just a little upgrade, yours is fine 👌"*
-([r/CardPuter, 2025-12-30](https://old.reddit.com/r/CardPuter/comments/1pzazuu/)). **[COM]**
-
----
-
-## 3. Chip inventory
-
-Complete `CO`-marker designator census from the schematic: `BT1 C1–C17 D1 E4 FB2 FB3 J1 J2
-L1 L2 M1 M2 P1 R1–R4 R5/NC R6/NC R7/NC U1 U2 U3`. **[SCH]**, `executed-success`.
-
-| Ref | Part | Function | Record |
-|---|---|---|---|
-| **M1** | **`Stamp LoRa-1262 Mini`** (13-pin module) | LoRa radio module — contains the **Semtech SX1262** | [`components/m5stack/stamp-lora-1262`](../../../components/m5stack/stamp-lora-1262/README.md) → [`components/semtech/sx1262`](../../../components/semtech/sx1262/README.md) |
-| **M2** | **`ATGM336H-6N`**, comment `GP-02` (18-pin module) | GNSS receiver — contains the **AT6668** chipset | [`components/zhongkewei/atgm336h-6n`](../../../components/zhongkewei/atgm336h-6n/README.md) → [`components/zhongkewei/at6668`](../../../components/zhongkewei/at6668/README.md) |
-| **U1** | **`MAX2659`** | GNSS **low-noise amplifier** ahead of the ceramic antenna | [`components/analog-devices/max2659`](../../../components/analog-devices/max2659/README.md) |
-| **U2** | **`PI4IOE5V6408`** (16-pin) | 8-bit I²C I/O expander at **0x43**; **P0 drives the LoRa RF switch** | [`components/diodes-incorporated/pi4ioe5v6408`](../../../components/diodes-incorporated/pi4ioe5v6408/README.md) |
-| **U3** | **`JW5712`** | 5 V → 3.3 V synchronous buck, `IOUT: 0~0.6 A` printed on the sheet | [`components/joulwatt/jw5712`](../../../components/joulwatt/jw5712/README.md) |
-| **J1** | `ANT1818-04` *(printed `ANT181804`)* | **GNSS ceramic patch antenna**, 18 × 18 × 4 mm ⚠ part number read from the schematic comment only | [`components/generic/gnss-ceramic-patch-antenna`](../../../components/generic/gnss-ceramic-patch-antenna/README.md) |
-| **E4** | `SMA-KE` | **LoRa antenna connector** — see the RP-SMA/SMA conflict in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) | [`components/generic/rp-sma-and-sma-antenna-connectors`](../../../components/generic/rp-sma-and-sma-antenna-connectors/README.md) |
-| **P1** | `HDR-SMD_14P-P2.54` | Cap-Bus header (2 × 7, 2.54 mm) | [`pinouts-and-buses.md`](pinouts-and-buses.md) |
-| **J2** | `GROVE 4P` | HY2.0-4P pass-through: `5V / GND / SDA / SCL` | — |
-| **BT1** | `Battery` | GNSS backup cell on `M2` pin 6 `VBAT` — keeps ephemeris for hot start | — |
-| **L1** | 6.8 nH ±5 % | GNSS LNA input match | — |
-| **L2** | `WPN201610U2R2MT` (2.2 µH) | JW5712 output inductor | — |
-| **FB2, FB3** | 120 Ω/MB ferrite beads | GNSS supply isolation (`VCC_RF`, `VCC`) | — |
-| **C5, C6, C7** | 470 pF, 100 nF, 33 nF | MAX2659 bias/decoupling | — |
-| **R1** | 10 kΩ | **JW5712 enable pull-up** → the buck has **no host enable**; the Cap powers up with 5 V. `inferred` from adjacency, not traced | — |
-| **R2, R4** | 0 Ω | Series links | — |
-| **R3** | 10 kΩ | Grove I²C pull-up | — |
-| R5/NC, R6/NC, R7/NC, C13/NC, C14/NC, D1 (`NC`) | not fitted | Depopulated options around `U2` and the antenna path | — |
-
-> **Two chips named on the vendor page do not appear on the schematic as described.**
-> The pin-map graphic labels an element `FM8625H` next to `PI4IOE5V6408 P0 → SX_ANT_SW`,
-> but the V1.1 schematic's only regulator is `U3 = JW5712`. Recorded as a conflict, not
-> resolved. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md) **G3**.
-
----
-
-## 4. Common tasks / How do I…?
-
-| Question | Guide |
-|---|---|
-| …send and receive a LoRa packet? | [`features/lora.md`](features/lora.md) |
-| …**port LoRa to another board's firmware?** | [`features/lora.md` §11](features/lora.md) — the portability checklist |
-| …get a GNSS fix / read NMEA? | [`features/gnss.md`](features/gnss.md) |
-| …fix "GPS never locks"? | [`features/gnss.md` §6](features/gnss.md) — it is usually the RX/TX pin swap |
-| …drive the antenna RF switch? | [`features/io-expander-and-rf-switch.md`](features/io-expander-and-rf-switch.md) |
-| …tell a Cap LoRa-1262 from a Cap LoRa868 at runtime? | [`features/io-expander-and-rf-switch.md` §4](features/io-expander-and-rf-switch.md) — probe `0x43` |
-| …use the Grove port while the Cap is fitted? | [`features/power-and-grove.md`](features/power-and-grove.md) |
-| …run Meshtastic on it? | [`development.md` §4](development.md) |
-| …know which pin is which? | [`pinouts-and-buses.md`](pinouts-and-buses.md) |
-| …know what is *not* established? | [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-
----
-
-## 5. Vendor specification (as published)
-
-| Specification | Value | Note |
-|---|---|---|
-| LoRa module | SX1262 | inside `Stamp LoRa-1262 Mini` |
-| LoRa frequency range | **868 – 923 MHz** | single wideband SKU |
-| LoRa programmable bit rate | up to 300 kbps | (G)FSK figure, not LoRa |
-| LoRa interface | SPI | |
-| LoRa TX power | **+22 dBm** | vs +20 dBm on U201 |
-| LoRa RX sensitivity | **−147 dBm** | "LoRa low data rate mode" |
-| LoRa operating current | **DC 5 V @ 163.4 mA** | condition unstated |
-| Modulation | FSK / GFSK / MSK / LoRa / OOK | the page's *Features* list also claims GMSK |
-| Antenna (supplied) | 108 × 9.3 mm, 3 dBi, "RP-SMA (internal thread, internal hole)" | ⚠ see conflict **G1** |
-| GPS module | **ATGM336H-6N @ AT6668** | |
-| GPS interface | **UART, 115200 bps 8N1** | note: *not* the 9600 default of most ATGM336H boards |
-| GNSS systems | GPS / QZSS / BD2 / BD3 / GAL / GLO | |
-| GNSS bands | BDS B1I+B1C · GPS/QZSS/SBAS L1 · GALILEO E1 · GLONASS R1 | |
-| Channels | 50 | |
-| Accuracy | < 1.5 m CEP50 | |
-| Update rate | up to 10 Hz | |
-| Protocol | NMEA 0183 4.1 (+ CASIC binary) | |
-| Sensitivity | tracking −162 dBm · acquisition −160 dBm · cold start −148 dBm | |
-| TTFF | cold 23 s · hot 1 s | |
-| Power-on consumption | **33.1 mA** | condition unstated |
-
-Prose caveat: the two current figures (33.1 mA "power on" and 163.4 mA "LoRa operating")
-are given without stating the radio state, duty cycle or supply path, and the board draws
-them through a 5 V→3.3 V buck whose own efficiency is unstated. The **predecessor** U201's
-page is considerably more useful here — it breaks current down into four named states
-(GPS on/LoRa standby 29.24 mA; GPS sleep/LoRa standby 3.16 mA; GPS sleep/LoRa TX max
-129.72 mA; GPS on/LoRa TX max 155.03 mA). Those numbers are for a *different board* and
-must not be transplanted, but they are the only state-resolved figures M5Stack publishes
-for this hardware class. **[DOC]** on both.
-
----
-
-## 6. Photographs
-
-Product photography from M5Stack's documentation CDN, retained in [`media/`](media/) — see
-[`media.md`](media.md) for provenance, rights status, captions and alt text.
-
----
-
-## 7. Related records
-
-- [**Cap CC1101 & NFC (U219)**](../cap-cc1101/README.md) — the other Cap, same bus, sub-GHz + NFC
-- [**Cap LoRa868 (U201)**](../cap-lora868/README.md) — direct predecessor
-- [**Cardputer Mesh Kit (K152)**](../cardputer-mesh-kit/README.md) — this Cap bundled with a Cardputer-Adv
-- **Cardputer-Adv** — `devices/m5stack/cardputer-adv/README.md` *(owned by a parallel research pass; this record does not write it)*
-- [**M5Stack PaperMono**](../papermono/README.md) — the other M5Stack product using a `Stamp LoRa-1262`, wired completely differently
-- [`guides/lora`](../../../guides/lora/README.md) · [`guides/nfc`](../../../guides/nfc/README.md)
-- [`software/`](../../../software/README.md)
-
-## 8. Files in this record
-
-`README.md` · [`pinouts-and-buses.md`](pinouts-and-buses.md) · [`development.md`](development.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md) · [`gaps-and-conflicts.md`](gaps-and-conflicts.md) ·
-[`market-and-pricing.md`](market-and-pricing.md) · [`projects-and-community.md`](projects-and-community.md) ·
-[`sources.md`](sources.md) · [`research-log.md`](research-log.md) · [`commands.md`](commands.md) ·
-[`media.md`](media.md) · [`features/`](features/README.md) · [`artifacts/`](artifacts/)
diff --git a/devices/m5stack/cap-lora-1262/acquisition/manifest.json b/devices/m5stack/cap-lora-1262/acquisition/manifest.json
deleted file mode 100644
index 78a3d71..0000000
--- a/devices/m5stack/cap-lora-1262/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "devices/m5stack/cap-lora-1262",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AN3WM5CAPLORA1262-9086477",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPLORA1262/Test-Report/Antenna-Specification-9086477.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086477",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086477.pdf",
-    "https://fccid.io/2AN3WM5CAPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/Test-Report/Antenna-Specification-9086477.pdf"
-   ],
-   "sha256": "da669cafd28d9fd14efd8126445191f06d5a03667c06ec713e12940be224a508",
-   "bytes": 592270,
-   "destination": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-12",
-   "fcc_id": "2AN3WM5CAPLORA1262",
-   "fcc_document_id": "9086477",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Specification",
-   "grant_date": "2026-02-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf",
-   "placeholder": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPLORA1262-9086474",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPLORA1262/External-Photos/External-Photos-9086474.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086474",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086474.pdf",
-    "https://fccid.io/2AN3WM5CAPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/External-Photos/External-Photos-9086474.pdf"
-   ],
-   "sha256": "dca8f216a5c65942a1a09c62ff9fae66f8ce9163b86238c5fd40c1813e09fb45",
-   "bytes": 767323,
-   "destination": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-12",
-   "fcc_id": "2AN3WM5CAPLORA1262",
-   "fcc_document_id": "9086474",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2026-02-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf",
-   "placeholder": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPLORA1262-9086475",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPLORA1262/Internal-Photos/Internal-Photos-9086475.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086475",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086475.pdf",
-    "https://fccid.io/2AN3WM5CAPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/Internal-Photos/Internal-Photos-9086475.pdf"
-   ],
-   "sha256": "61f89fc08fde8a09e6c9268c8f3d13d7722bf6fdc73c381621f08155381765b4",
-   "bytes": 809213,
-   "destination": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-12",
-   "fcc_id": "2AN3WM5CAPLORA1262",
-   "fcc_document_id": "9086475",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2026-02-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPLORA1262-9086480",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPLORA1262/Label/Label-and-Label-Location-9086480.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086480",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086480.pdf",
-    "https://fccid.io/2AN3WM5CAPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/Label/Label-and-Label-Location-9086480.pdf"
-   ],
-   "sha256": "e3963b8a5baed487bd9bedae8f00b23c6649d5c5a90ee7854a7522a134316209",
-   "bytes": 134335,
-   "destination": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-label-and-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-12",
-   "fcc_id": "2AN3WM5CAPLORA1262",
-   "fcc_document_id": "9086480",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label and Label Location",
-   "grant_date": "2026-02-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPLORA1262-9086479",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9086479.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086479",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086479.pdf",
-    "https://fccid.io/2AN3WM5CAPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9086479.pdf"
-   ],
-   "sha256": "ac8a66ce38b094803e6e01f7f34d895b4e5870cc3537c4bb0a35704afd1ccad8",
-   "bytes": 324207,
-   "destination": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-12",
-   "fcc_id": "2AN3WM5CAPLORA1262",
-   "fcc_document_id": "9086479",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Information",
-   "grant_date": "2026-02-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf",
-   "placeholder": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CAPLORA1262-9086484",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CAPLORA1262/User-Manual/User-Manual-9086484.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086484",
-    "https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086484.pdf",
-    "https://fccid.io/2AN3WM5CAPLORA1262",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/User-Manual/User-Manual-9086484.pdf"
-   ],
-   "sha256": "fb81cff4fb9a5d09f23128457c153b0b1723e0d2749978e3218b9e415b534de9",
-   "bytes": 765439,
-   "destination": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-02-12",
-   "fcc_id": "2AN3WM5CAPLORA1262",
-   "fcc_document_id": "9086484",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2026-02-12",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf",
-   "placeholder": "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cap-lora-1262",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf.ARCHIVED.md b/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 55d53b1..0000000
--- a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPLORA1262-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 592,270 B (0.56 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 592,270 B (0.56 MiB) |
-| SHA-256 | `da669cafd28d9fd14efd8126445191f06d5a03667c06ec713e12940be224a508` |
-| FCC ID | **`2AN3WM5CAPLORA1262`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 9086477 |
-| Upstream publication date | 2026-02-12 |
-| Grant date | 2026-02-12 |
-| Equipment class | M5Cap LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPLORA1262/Test-Report/Antenna-Specification-9086477.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086477>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086477.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/Test-Report/Antenna-Specification-9086477.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf" \
-   "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPLORA1262/Test-Report/Antenna-Specification-9086477.pdf" -o "2AN3WM5CAPLORA1262-antenna-specification.pdf"
-echo "da669cafd28d9fd14efd8126445191f06d5a03667c06ec713e12940be224a508  2AN3WM5CAPLORA1262-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf.ARCHIVED.md b/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 3d47c6a..0000000
--- a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPLORA1262-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 767,323 B (0.73 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 767,323 B (0.73 MiB) |
-| SHA-256 | `dca8f216a5c65942a1a09c62ff9fae66f8ce9163b86238c5fd40c1813e09fb45` |
-| FCC ID | **`2AN3WM5CAPLORA1262`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 9086474 |
-| Upstream publication date | 2026-02-12 |
-| Grant date | 2026-02-12 |
-| Equipment class | M5Cap LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPLORA1262/External-Photos/External-Photos-9086474.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086474>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086474.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/External-Photos/External-Photos-9086474.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf" \
-   "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPLORA1262/External-Photos/External-Photos-9086474.pdf" -o "2AN3WM5CAPLORA1262-external-photos.pdf"
-echo "dca8f216a5c65942a1a09c62ff9fae66f8ce9163b86238c5fd40c1813e09fb45  2AN3WM5CAPLORA1262-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-internal-photos.pdf b/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-internal-photos.pdf
deleted file mode 100644
index bcf620f..0000000
Binary files a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-internal-photos.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-label-and-label-location.pdf b/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-label-and-label-location.pdf
deleted file mode 100644
index 0309db4..0000000
Binary files a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-label-and-label-location.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf.ARCHIVED.md b/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf.ARCHIVED.md
deleted file mode 100644
index 9ddcbb0..0000000
--- a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPLORA1262-rf-exposure-information.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 324,207 B (0.31 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 324,207 B (0.31 MiB) |
-| SHA-256 | `ac8a66ce38b094803e6e01f7f34d895b4e5870cc3537c4bb0a35704afd1ccad8` |
-| FCC ID | **`2AN3WM5CAPLORA1262`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Information |
-| FCC document id | 9086479 |
-| Upstream publication date | 2026-02-12 |
-| Grant date | 2026-02-12 |
-| Equipment class | M5Cap LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9086479.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086479>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086479.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9086479.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf" \
-   "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-rf-exposure-information.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPLORA1262/RF-Exposure-Info/RF-Exposure-Information-9086479.pdf" -o "2AN3WM5CAPLORA1262-rf-exposure-information.pdf"
-echo "ac8a66ce38b094803e6e01f7f34d895b4e5870cc3537c4bb0a35704afd1ccad8  2AN3WM5CAPLORA1262-rf-exposure-information.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf.ARCHIVED.md b/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 6e8ec79..0000000
--- a/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CAPLORA1262-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 765,439 B (0.73 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 765,439 B (0.73 MiB) |
-| SHA-256 | `fb81cff4fb9a5d09f23128457c153b0b1723e0d2749978e3218b9e415b534de9` |
-| FCC ID | **`2AN3WM5CAPLORA1262`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 9086484 |
-| Upstream publication date | 2026-02-12 |
-| Grant date | 2026-02-12 |
-| Equipment class | M5Cap LoRa-1262, 903-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CAPLORA1262/User-Manual/User-Manual-9086484.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9086484>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CAPLORA1262/9086484.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CAPLORA1262>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CAPLORA1262/User-Manual/User-Manual-9086484.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf" \
-   "devices/m5stack/cap-lora-1262/artifacts/certification/2AN3WM5CAPLORA1262-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CAPLORA1262/User-Manual/User-Manual-9086484.pdf" -o "2AN3WM5CAPLORA1262-user-manual.pdf"
-echo "fb81cff4fb9a5d09f23128457c153b0b1723e0d2749978e3218b9e415b534de9  2AN3WM5CAPLORA1262-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cap-lora-1262/artifacts/certification/README.md b/devices/m5stack/cap-lora-1262/artifacts/certification/README.md
deleted file mode 100644
index b46cdb9..0000000
--- a/devices/m5stack/cap-lora-1262/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5CAPLORA1262`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5CAPLORA1262`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2026-02-12** |
-| Equipment class | M5Cap LoRa-1262, 903-914.9 MHz |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Source page | <https://fccid.io/2AN3WM5CAPLORA1262> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5CAPLORA1262-internal-photos.pdf` | 809,213 | `61f89fc08fde8a09e6c9268c8f3d13d7722bf6fdc73c381621f08155381765b4` | Internal Photos |
-| `2AN3WM5CAPLORA1262-label-and-label-location.pdf` | 134,335 | `e3963b8a5baed487bd9bedae8f00b23c6649d5c5a90ee7854a7522a134316209` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5CAPLORA1262-antenna-specification.pdf.ARCHIVED.md`](2AN3WM5CAPLORA1262-antenna-specification.pdf.ARCHIVED.md) | 592,270 | Test Report |
-| [`2AN3WM5CAPLORA1262-external-photos.pdf.ARCHIVED.md`](2AN3WM5CAPLORA1262-external-photos.pdf.ARCHIVED.md) | 767,323 | External Photos |
-| [`2AN3WM5CAPLORA1262-rf-exposure-information.pdf.ARCHIVED.md`](2AN3WM5CAPLORA1262-rf-exposure-information.pdf.ARCHIVED.md) | 324,207 | RF Exposure Info |
-| [`2AN3WM5CAPLORA1262-user-manual.pdf.ARCHIVED.md`](2AN3WM5CAPLORA1262-user-manual.pdf.ARCHIVED.md) | 765,439 | Users Manual |
-
-Archived total: **4 files, 2.34 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 0.90 MiB** |
-| Archived | **4 files, 2.34 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/m5stack/cap-lora-1262/artifacts/mechanical/U214-cap1262-model-size.pdf b/devices/m5stack/cap-lora-1262/artifacts/mechanical/U214-cap1262-model-size.pdf
deleted file mode 100644
index 86379dd..0000000
Binary files a/devices/m5stack/cap-lora-1262/artifacts/mechanical/U214-cap1262-model-size.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf b/devices/m5stack/cap-lora-1262/artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf
deleted file mode 100644
index 208fcb9..0000000
Binary files a/devices/m5stack/cap-lora-1262/artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/certification-and-compliance.md b/devices/m5stack/cap-lora-1262/certification-and-compliance.md
deleted file mode 100644
index 8cca118..0000000
--- a/devices/m5stack/cap-lora-1262/certification-and-compliance.md
+++ /dev/null
@@ -1,122 +0,0 @@
-# Certification and compliance — cap-lora-1262
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5CAPLORA1262` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5CAPLORA1262`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **903-914.9 MHz Original Equipment 2026-02-12** |
-| Application purpose | Final Action Date 903-914.9 MHz Original Equipment 2026-02-12 |
-| Frequency ranges | **903-914.9 MHz** |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 14 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5CAPLORA1262` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 767,323 | `dca8f216a5c65942…` |
-| `ID-Label-Location-Info-Label-and-Label-Location.pdf` | 134,335 | `e3963b8a5baed487…` |
-| `Internal-Photos-Internal-Photos.pdf` | 809,213 | `61f89fc08fde8a09…` |
-| `RF-Exposure-Info-RF-Exposure-Information.pdf` | 324,207 | `ac8a66ce38b09480…` |
-| `Test-Report-Antenna-Specification.pdf` | 592,270 | `da669cafd28d9fd1…` |
-| `Users-Manual-User-Manual.pdf` | 765,439 | `fb81cff4fb9a5d09…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5CAPLORA1262/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5CAPLORA1262/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cap-lora-1262/commands.md b/devices/m5stack/cap-lora-1262/commands.md
deleted file mode 100644
index 6a8419a..0000000
--- a/devices/m5stack/cap-lora-1262/commands.md
+++ /dev/null
@@ -1,146 +0,0 @@
-# Command ledger — Cap LoRa-1262 (U214)
-
-Shell: bash on NixOS. Date: 2026-09-04. Redacted: none (no secrets used beyond
-`gh auth token`, never printed).
-
-## 1. Acquisition
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-curl -sS -A "$UA" -o Cap_LoRa-1262.html https://docs.m5stack.com/en/cap/Cap_LoRa-1262
-```
-`executed-success` · HTTP 200 · 141 506 B. No UA rotation needed.
-
-```bash
-curl -sS -A "$UA" -o cap-lora-1262.json \
-  https://shop.m5stack.com/products/cap-lora-1262-for-cardputer-adv-sx1262-atgm336h.json
-```
-`executed-success` · HTTP 200 · 19 450 B. **This is the single most valuable command in the
-pass** — Shopify's `.json` endpoint returns `published_at`, `created_at`, SKU and price as
-machine-readable fields, which is how the release-date correction was established.
-
-Full catalogue enumeration (662 products, 3 pages; page 4 returns `{"products":[]}`):
-
-```bash
-for p in 1 2 3; do
-  curl -sS -A "$UA" -o all$p.json \
-    "https://shop.m5stack.com/collections/all/products.json?limit=250&page=$p"
-done
-```
-`executed-success`.
-
-Artifacts:
-
-```bash
-curl -sSL -A "$UA" -o U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf \
-  https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-sche-Cap-LoRa1262_SCH_V1.1_20251029_2025_11_07_22_53_19.pdf
-curl -sSL -A "$UA" -o Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf \
-  https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/NEW-1262-SCH_A1-Lora_2025_08_27_10_58_52.pdf
-```
-`executed-success` · 155 866 B / 184 442 B · both `%PDF-1.4`, magic verified with
-`head -c 8`.
-
-## 2. Schematic text extraction — no poppler on this host
-
-`pdftotext`, `pdfinfo` and `qpdf` are **absent**, so `tools/altium_pdf_pin_table.py`
-had nothing to read. Workaround, from the repository root:
-
-```bash
-cd scratch/m5stack-lora-expansions
-uv run --quiet --with pypdf python tools/pdf_bbox.py \
-    artifacts/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf \
-    pdf/U214-Cap-LoRa1262_SCH_V1.1_20251029
-# -> page 1: 766 words -> pdf/.../bbox-p1.xml
-```
-`executed-success`.
-
-```bash
-uv run --quiet python tools/sch_dump.py \
-    pdf/U214-Cap-LoRa1262_SCH_V1.1_20251029/bbox-p1.xml markers   # designator census
-uv run --quiet python tools/sch_dump.py \
-    pdf/U214-Cap-LoRa1262_SCH_V1.1_20251029/bbox-p1.xml rows      # row-banded text
-uv run --quiet python tools/sch_dump.py \
-    pdf/U214-Cap-LoRa1262_SCH_V1.1_20251029/bbox-p1.xml pins:M1   # per-designator
-```
-`executed-success` for `markers` and `rows`.
-**`executed-failed` (partially) for `pins:`** — the synthesised word boxes are not aligned
-the way pdftotext's are, so the "inside symbol / outside symbol" split misattributes text.
-Diagnosis: pypdf's visitor reports the text-matrix origin, not a glyph box. **Every pin
-assertion in this record therefore comes from the `rows` view cross-checked against
-M5Stack's published pin-map graphic, never from `pins:` alone.**
-
-Targeted region dump used instead:
-
-```bash
-uv run --quiet python /tmp/box.py \
-    pdf/U214-Cap-LoRa1262_SCH_V1.1_20251029/bbox-p1.xml 540 720 480 535   # x0 x1 y0 y1
-```
-`executed-success` — this is what produced the `P1` header table in
-[`pinouts-and-buses.md`](pinouts-and-buses.md).
-
-## 3. GitHub (authenticated — 5 000/h instead of 60/h)
-
-```bash
-GH="Authorization: Bearer $(gh auth token)"
-curl -sS -H "$GH" "https://api.github.com/repos/meshtastic/firmware/contents/variants/esp32s3/m5stack_cardputer_adv?ref=master"
-curl -sS -H "$GH" "https://api.github.com/repos/meshtastic/firmware/commits?path=variants/esp32s3/m5stack_cardputer_adv&per_page=20"
-curl -sS -H "$GH" "https://api.github.com/repos/meshtastic/firmware/pulls/9540"
-```
-`executed-success`. Never print the token.
-
-Establishing *which release first contains a commit* — the load-bearing trick:
-
-```bash
-curl -sS -H "$GH" \
- "https://api.github.com/repos/meshtastic/firmware/compare/969aefa551d645e6110be11f330774e15ad9c87d...v2.7.20.6658ec2"
-#   -> status "ahead",  ahead_by 17,  behind_by 0     => 2.7.20 CONTAINS it
-curl -sS -H "$GH" \
- "https://api.github.com/repos/meshtastic/firmware/compare/969aefa551d645e6110be11f330774e15ad9c87d...v2.7.19.bb3d6d5"
-#   -> status "behind", ahead_by 0,   behind_by 177   => 2.7.19 does NOT
-```
-`executed-success`. Far more reliable than reading release notes.
-
-Checking whether a board is in a release without downloading a 143 MB zip:
-
-```bash
-curl -sSL -H "$GH" -o firmware-2.7.20.6658ec2.json \
-  https://github.com/meshtastic/firmware/releases/download/v2.7.20.6658ec2/firmware-2.7.20.6658ec2.json
-python3 -c "import json;print([x for x in sum(json.load(open('firmware-2.7.20.6658ec2.json')).values(),[]) if 'cardputer' in json.dumps(x).lower()])"
-```
-`executed-success` → `{"board": "m5stack-cardputer-adv", "platform": "esp32s3"}` (8 917 B
-instead of 143 239 618 B).
-
-## 4. Reddit
-
-```bash
-curl -sS -A 'WhatsApp/2.23.20.0' -o out.json \
-  'https://old.reddit.com/search.json?q=cardputer+lora&sort=new&limit=100&t=all'
-curl -sS -A 'WhatsApp/2.23.20.0' -o thread.json \
-  'https://old.reddit.com/r/CardPuter/comments/1w0gv7y/.json?limit=100'
-```
-`executed-success` · HTTP 200 on all 18 calls. `www.reddit.com` was **not** attempted; the
-repo's access table already records it as 403 for automated clients.
-
-## 5. Verification
-
-```bash
-sha256sum artifacts/*.pdf
-for f in artifacts/*.pdf; do printf '%-60s %s\n' "$f" "$(head -c 8 "$f")"; done   # %PDF-1.x
-```
-`executed-success` — all ten downloads are genuine PDFs; no HTML error page was saved under
-a `.pdf` extension.
-
-Duplicate detection against material already in the repository:
-
-```bash
-sha256sum components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf \
-          scratch/m5stack-lora-expansions/artifacts/st25r3916_datasheet-m5stack-mirror.pdf
-# identical: 1170f4d74ff501917262ae42bf81c60c38c11d121e2ea2af6b1e845433befef1
-```
-`executed-success` → the second copy was **not** stored; the extra URL was recorded instead.
-
-## 6. Not executed
-
-- No build, flash or on-device command was run. No hardware present.
-- `pio run -e m5stack-cardputer-adv` in [`development.md`](development.md) is
-  **`not-tested`**, transcribed from upstream `platformio.ini`.
diff --git a/devices/m5stack/cap-lora-1262/compatibility-and-status.md b/devices/m5stack/cap-lora-1262/compatibility-and-status.md
deleted file mode 100644
index d472b80..0000000
--- a/devices/m5stack/cap-lora-1262/compatibility-and-status.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# Compatibility and status — Cap LoRa-1262 (U214)
-
-Keyed by host, firmware and version. Snapshot 2026-09-04. **Nothing in this table was
-tested by this research pass**; every row states its own evidence class.
-
-## 1. Hosts
-
-| Host | Fits? | Evidence |
-|---|---|---|
-| **Cardputer-Adv (K132-ADV)** | ✅ designed for it | vendor **[DOC]**, schematic annotates every Cap-Bus pin with its Cardputer-Adv GPIO |
-| **CardputerZero** | ✅ claimed | vendor **[DOC]** on both the U214 and U219 pages. Note the CC1101 announcement says band-select SW0 moves from **G13 (ADV) to G14 (Zero)** — so *pin mapping differs between hosts* and firmware must know which host it is on |
-| **Cardputer P4 ("Next")** | ⛔ unreleased; claimed compatible | **[COM]** M5Stack community post, [r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0nwti/) |
-| **Cardputer K132 / K132-V11 (original)** | ❌ **no** | The original has only a Grove HY2.0-4P (`PORT.CUSTOM`, G2/G1) and no expansion bus **[DOC]**. Community answer the day the ADV launched: *"No, not enough gpio pins"* — u/IceSubstantial5572, [r/CardPuter 2025-09-04](https://old.reddit.com/r/CardPuter/comments/1n8d8j2/) |
-| PaperMono / other M5Stack cores | ❌ | different bus entirely |
-
-## 2. Firmware
-
-| Firmware | LoRa | GNSS | Status | Evidence |
-|---|---|---|---|---|
-| **Meshtastic** ≥ 2.7.20 | ✅ | ✅ | **Upstream official.** Antenna switch broken until 2.7.24 | **[SRC]** variant files + commit history |
-| Meshtastic 2.7.19 and earlier | ❌ | ❌ | No variant existed. Users ran third-party M5Burner builds and hit "very common issues" — u/thetestbug, [r/CardPuter 2026-02-15](https://old.reddit.com/r/CardPuter/comments/1r4waav/), linking PR #9540 as the fix in progress | **[COM]** |
-| **M5Stack Arduino examples** | ✅ | ✅ | Published; auto-detects U214 vs U201 | **[DOC]** |
-| **UiFlow2** | ✅ | ✅ | Vendor page exists; unexplored here | **[DOC]** |
-| **MeshCore** (community) | ✅ | ✅ | `MeshCore-Cardputer-ADV` v1.1.0 released 2026-01-27, 104 upvotes / 42 comments | **[COM]** |
-| **Plai** (d4rkmen) | ✅ | ✅ | Standalone Meshtastic node firmware, 175 stars | **[COM]** |
-| **Bruce** | ✅ (sub-GHz focus) | ✅ | Used as a GNSS-diagnosis tool by owners | **[COM]** |
-| **LoRaWAN (any stack)** | ❓ | — | **Nothing demonstrated.** No example, no project, no regional-parameters config located | negative result, `executed-success` |
-
-## 3. Version-specific reports worth keeping
-
-| Date | Report | Class |
-|---|---|---|
-| 2026-02-15 | Meshtastic on Cardputer-Adv "a disaster: on esp32 wifi is unusable: web server crashes, on esp32-s3 — same story with bluetooth" — u/d4rkmen (author of Plai), [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1r4waav/) | firsthand developer opinion, pre-upstream-support |
-| 2026-06-12 | Battery percentage unreliable with a Cap fitted; several owners agree the reading is voltage-only with no BMS. u/pyreht adds that the host's 5 V IN/OUT switch perturbs the G10 battery-sense reading when the Grove port is loaded, [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1u3qeez/) | firsthand, host-side |
-| 2026-08-22 | Owner could never get Meshtastic working; thread resolves to a wrong-band antenna for NA, [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1vvlcs9/) | firsthand, resolved |
-| 2026-08-28 → 09-02 | "GNSS dead on arrival" → resolved by manually setting Meshtastic's GPS RX/TX pins; separately, M5Launcher **2.8.0** broke GPS across firmwares and the launcher author confirmed a fix in Beta 2.9, [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1w0gv7y/) | firsthand + maintainer response |
-| 2026-01-17/18 | Meshtastic position 2 miles off vs vendor demo "spot on" — cause was Meshtastic's default degraded channel precision, not the receiver, [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1qf0z9v/) | firsthand, resolved |
-
-## 4. Untested / unknown
-
-- Every RF number: range, sensitivity, output power at the connector, spurious emissions.
-- Current draw in any resolved state (the vendor gives two unconditioned aggregates).
-- LoRa TX desensitising the co-located GNSS front end.
-- Behaviour of the Cap across host deep-sleep cycles.
-- Whether `0x43` collides with any commonly-used Grove unit in practice.
-- LoRaWAN of any kind.
diff --git a/devices/m5stack/cap-lora-1262/development.md b/devices/m5stack/cap-lora-1262/development.md
deleted file mode 100644
index c0d5b70..0000000
--- a/devices/m5stack/cap-lora-1262/development.md
+++ /dev/null
@@ -1,109 +0,0 @@
-# Development — Cap LoRa-1262 (U214)
-
-The Cap has **no processor and no firmware of its own.** Everything here is host-side
-(Cardputer-Adv / CardputerZero). Snapshot 2026-09-04.
-
-## 1. Toolchains that know about this board
-
-| Path | Board target | Status |
-|---|---|---|
-| **Arduino / PlatformIO + RadioLib** | Cardputer-Adv board defs | Vendor examples published; `not-tested` here |
-| **Meshtastic** | `m5stack-cardputer-adv` (`board = m5stack-stamps3`) | **Upstream, official**, since 2.7.20 |
-| **UiFlow2 / MicroPython** | `cap/lora1262` | Vendor docs at `uiflow-micropython.readthedocs.io/en/latest/cap/lora1262.html` |
-| **ESP-IDF** | listed by M5Stack as a supported platform for the Mesh Kit | no Cap-specific component located |
-| **Bruce**, **M5Launcher**, **Plai**, **MeshCore**, **WhisperOS** | community | [`projects-and-community.md`](projects-and-community.md) |
-
-## 2. Libraries and exact versions
-
-| Library | Role | Pin |
-|---|---|---|
-| **RadioLib** (jgromes) | SX1262 driver — this *is* the "Cap LoRa-1262 Arduino LoRa Driver Library" the docs link to | latest release **7.7.1** (2026-05-31); head `187ef24791c3d844939b2be13a68bd890bd04e4c` (2026-08-22). **MIT** |
-| **m5stack/TinyGPSPlus** | GNSS — `MultipleSatellite` class. ⚠ **must** be the M5Stack fork, not the Library Manager copy | head `254a10041ac38d17d98dab24c0ae4d2a8d19a677` (2025-01-02). **No LICENSE file in the repo**; upstream TinyGPSPlus is LGPL-2.1 |
-| **M5Unified** | `m5::In_I2C`, `m5::PI4IOE5V6408_Class` | version not pinned by the docs |
-| **M5GFX** | display | — |
-
-> **There is no M5Stack driver library for this Cap.** A GitHub search of `org:m5stack`
-> for `lora`, `1262`, `cap` and `cc1101` returns no matching repository. The vendor's
-> "driver library" links are pointers to third-party projects. Recorded as a finding, not
-> a gap in the search: `executed-success`, 2026-09-04.
-
-## 3. Build and flash — Arduino path
-
-Nothing about flashing is Cap-specific; it is the host's procedure.
-
-```text
-Cardputer-Adv download mode  (vendor instructions, [DOC])
-  1. Side power switch -> OFF
-  2. Hold the G0 key
-  3. Power on, then release
-```
-
-`inferred` for anything beyond that: no Cap-specific fuse, strap or recovery step exists,
-because the Cap contains no programmable part.
-
-## 4. Meshtastic
-
-```bash
-# Reproduce the officially supported build
-git clone https://github.com/meshtastic/firmware.git
-cd firmware
-git submodule update --init --recursive
-pio run -e m5stack-cardputer-adv
-pio run -e m5stack-cardputer-adv -t upload
-```
-`not-tested` — transcribed from `variants/esp32s3/m5stack_cardputer_adv/platformio.ini`
-and Meshtastic's standard build flow, not executed in this pass.
-
-Prebuilt binaries ship inside the aggregated release asset
-`firmware-esp32s3-<version>.zip` (e.g. `firmware-esp32s3-2.7.26.54e0d8d.zip`,
-170 272 165 B). There is **no** per-board asset at the release level; the device index
-`firmware-<version>.json` is what lists `{"board":"m5stack-cardputer-adv","platform":"esp32s3"}`.
-
-Minimum useful versions:
-
-| Want | Need |
-|---|---|
-| The board at all | **2.7.20** (2026-03-11) |
-| Working antenna switch | **2.7.24** (2026-05-23) — two fixes landed 2026-05-18/19 |
-| Current | 2.7.26 (2026-06-24, stable) or 2.8.0 prereleases (2026-08-30 / 2026-09-01) |
-
-Build flags of note from `platformio.ini`: `-D M5STACK_CARDPUTER_ADV`,
-`-D ARDUINO_USB_CDC_ON_BOOT=1`, `board_build.partitions = default_8MB.csv`,
-`upload_protocol = esptool`.
-
-Dependencies it pulls (pinned as GitHub zips, not registry versions):
-`meshtastic/st7789@92bae2e4a307afb430c3b0bc3d661c55ee1565f0`,
-`pschatzmann/arduino-audio-driver@v0.3.0`,
-`meshtastic/ESP8266Audio@343024632ee78d6216907b2353fc943a62422d80`,
-`earlephilhower/ESP8266SAM@1.1.0`.
-
-## 5. UiFlow2 / MicroPython
-
-`https://uiflow-micropython.readthedocs.io/en/latest/cap/lora1262.html` — enumerated from
-the product page's link set, **not fetched** in this pass. Recorded as a known-unexplored
-source.
-
-## 6. Recovery
-
-**Not applicable to the Cap.** It has no flash, no MCU and no bootloader. If a Cap appears
-dead:
-
-1. Confirm the host is providing 5 V on the EXT connector.
-2. Probe I²C for `0x43` — if absent, either the Cap is not seated or it is a U201.
-3. If `0x43` answers but RF is dead, suspect the antenna-switch init or the connector.
-4. There is nothing to reflash.
-
-## 7. Known bricking / damage risks
-
-| Risk | Source |
-|---|---|
-| **Powering the LoRa radio with no antenna fitted** | M5Stack's own warning box on the product page: *"Do not connect or power on the device without installing the antenna, otherwise the device hardware may be permanently damaged!"* **[DOC]**. Standard for a +22 dBm PA into an open port |
-| Wrong-band antenna | Not damaging, but a real range problem — [`features/lora.md` §7](features/lora.md) |
-| Grove device at I²C 0x43 | Silently breaks the antenna switch and confuses Cap detection |
-| Reversing the 14-pin header | Not investigated. The connector is keyed only by the enclosure fit |
-
-## 8. Related
-
-[`features/lora.md`](features/lora.md) · [`features/gnss.md`](features/gnss.md) ·
-[`pinouts-and-buses.md`](pinouts-and-buses.md) · [`commands.md`](commands.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md)
diff --git a/devices/m5stack/cap-lora-1262/features/README.md b/devices/m5stack/cap-lora-1262/features/README.md
deleted file mode 100644
index 9039ff6..0000000
--- a/devices/m5stack/cap-lora-1262/features/README.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Feature guides — Cap LoRa-1262 (U214)
-
-| Feature | Guide | Status |
-|---|---|---|
-| LoRa (SX1262) | [`lora.md`](lora.md) | documented from schematic + vendor code + Meshtastic upstream; **not hardware-tested here** |
-| GNSS (ATGM336H-6N / AT6668) | [`gnss.md`](gnss.md) | documented; known documentation trap on the UART pins |
-| I/O expander + antenna RF switch | [`io-expander-and-rf-switch.md`](io-expander-and-rf-switch.md) | documented; also the runtime Cap-detection mechanism |
-| Power rail + Grove pass-through | [`power-and-grove.md`](power-and-grove.md) | documented; enable-net polarity unresolved |
-
-Not applicable to this board: display, touch, audio, storage, USB, battery — all belong to
-the host. See `devices/m5stack/cardputer-adv/` (parallel research pass).
-
-Cross-cutting: [`guides/lora`](../../../../guides/lora/README.md) ·
-[`guides/nfc`](../../../../guides/nfc/README.md) (relevant only for the sibling
-[Cap CC1101](../../cap-cc1101/features/nfc.md)).
diff --git a/devices/m5stack/cap-lora-1262/features/gnss.md b/devices/m5stack/cap-lora-1262/features/gnss.md
deleted file mode 100644
index c7dcd7d..0000000
--- a/devices/m5stack/cap-lora-1262/features/gnss.md
+++ /dev/null
@@ -1,181 +0,0 @@
-# GNSS — Cap LoRa-1262 (U214)
-
-> **How do I get a position fix?** Open `Serial1` at **115200 8N1** with **RX = G15,
-> TX = G13**, and parse NMEA. That is the whole interface. Everything difficult about this
-> subsystem comes from the two pins being documented backwards in one place — §6.
-
-Snapshot 2026-09-04 · schematic **V1.1** · nothing tested on hardware.
-
-## 1. Hardware path
-
-```
-J1 ceramic patch (ANT1818-04, 18x18x4 mm)
-   │ L1 6.8 nH
-   ▼
-U1 MAX2659 LNA  (VCC +3.3V, SHDN tied, C6 100nF / C7 33nF)
-   │ C5 470 pF
-   ▼  pin 11 ANT
-M2 ATGM336H-6N  ── AT6668 chipset inside ── VBAT ◀── BT1 backup cell
-   │ pin 2 TXD ──▶ Cap-Bus 1 ──▶ host G15   (host RX)
-   │ pin 3 RXD ◀── Cap-Bus 2 ◀── host G13   (host TX)
-   │ VCC  ◀── FB2/FB3 120 Ω/MB ◀── VDD_3V3
-   └ SDA/SCL (16/17), 1PPS (4), NRST (9), ON/OFF (5): NOT ROUTED to the host
-```
-
-| Element | Part | Record |
-|---|---|---|
-| GNSS module | **ATGM336H-6N**, schematic comment `GP-02` | [`components/zhongkewei/atgm336h-6n`](../../../../components/zhongkewei/atgm336h-6n/README.md) |
-| GNSS chipset | **AT6668** | [`components/zhongkewei/at6668`](../../../../components/zhongkewei/at6668/README.md) |
-| LNA | **MAX2659** | [`components/analog-devices/max2659`](../../../../components/analog-devices/max2659/README.md) |
-| Patch antenna | `ANT1818-04` (18 × 18 × 4 mm) | [`components/generic/gnss-ceramic-patch-antenna`](../../../../components/generic/gnss-ceramic-patch-antenna/README.md) |
-
-**The LNA is the notable design choice.** Most ATGM336H breakouts hang a passive patch
-straight off `ANT`. This board puts a **MAX2659 (≈ +20 dB gain, sub-1 dB NF)** in front of
-it, powered from `VCC_RF` through a ferrite. That is what buys the −162 dBm tracking figure
-in the specification table, and it means the GNSS front end draws current even when the
-receiver is idle — `SHDN` is tied, so the host cannot switch the LNA off.
-
-## 2. Capability, as published
-
-| Item | Value |
-|---|---|
-| Constellations | GPS · QZSS · BDS (BD2 + BD3) · GALILEO · GLONASS |
-| Bands | BDS **B1I + B1C** · GPS/QZSS/SBAS **L1** · GALILEO **E1** · GLONASS **R1** |
-| Channels | 50 |
-| Accuracy | **< 1.5 m CEP50** |
-| Update rate | up to **10 Hz** |
-| Sensitivity | tracking **−162 dBm** · acquisition −160 dBm · cold start −148 dBm |
-| TTFF | cold **23 s** · hot **1 s** |
-| Protocol | **NMEA 0183 4.1** on the wire; **CASIC binary** for configuration |
-| UART | **115200 bps, 8N1** |
-
-> ⚠ **115200, not 9600.** The ATGM336H's own factory default in most other products is
-> 9600 bps. M5Stack ships this Cap configured at 115200 and both the vendor example and
-> Meshtastic's `GPS_BAUDRATE` assume it. If you autobaud, include 9600 in the sweep anyway —
-> nothing in the documentation says the setting is stored in the module's flash rather than
-> applied by firmware.
-
-Multi-band (B1I+B1C, E1, L1, R1) does **not** mean dual-frequency: these are all the same
-~1.56–1.61 GHz L1 neighbourhood, which is why one 18 mm patch and one LNA suffice. Do not
-read "multi-frequency" here as L1+L5 RTK-grade capability.
-
-## 3. Software
-
-| Stack | Class / API | Notes |
-|---|---|---|
-| **M5Stack Arduino** | `MultipleSatellite` from **`github.com/m5stack/TinyGPSPlus`** | ⚠ *"needs to be downloaded from the GitHub version adapted for M5Stack devices … Do not download it from the Arduino Library Manager"* **[DOC]**. Repo head `254a10041ac38d17d98dab24c0ae4d2a8d19a677`, 2025-01-02, **no LICENSE file present** (upstream TinyGPSPlus is LGPL-2.1) |
-| **Meshtastic** | built-in GPS subsystem, `HAS_GPS 1` | `GPS_RX_PIN 15`, `GPS_TX_PIN 13`, `GPS_BAUDRATE 115200` |
-| **UiFlow2** | `uiflow-micropython.readthedocs.io/en/latest/cap/lora1262.html` | vendor |
-| Any NMEA parser | — | The device emits standard NMEA 0183 4.1; nothing M5Stack-specific is needed just to read a fix |
-
-Vendor example skeleton (**[DOC]**, `executed-success` on the read, `not-tested`):
-
-```cpp
-#include "MultipleSatellite.h"
-static const int RXPin = 15, TXPin = 13;      // host RX = G15, host TX = G13
-static const uint32_t GPSBaud = 115200;
-MultipleSatellite gps(Serial1, GPSBaud, SERIAL_8N1, RXPin, TXPin);
-
-satellite_mode_t currentMode = SATELLITE_MODE_GLONASS;   // vendor default
-
-void setup() {
-    gps.begin();
-    gps.setSystemBootMode(BOOT_FACTORY_START);
-    String version = gps.getGNSSVersion();
-    gps.setSatelliteMode(currentMode);
-}
-void loop() {
-    gps.updateGPS();
-    if (gps.location.isUpdated()) { gps.location.lat(); gps.location.lng(); }
-    gps.satellites.value();  gps.date.month(); gps.time.hour();
-}
-```
-
-`setSystemBootMode()`, `setSatelliteMode()` and `getGNSSVersion()` are **CASIC binary
-commands**, not NMEA — that is what the *CASIC Multi-mode Satellite Navigation Receiver
-Protocol Specification* documents. It is archived; see
-[`components/zhongkewei/at6668/artifacts/`](../../../../components/zhongkewei/at6668/artifacts/).
-
-## 4. What the host cannot do
-
-Because pins 4, 5, 9, 16 and 17 of `M2` are not routed to the Cap-Bus
-([`../pinouts-and-buses.md` §4](../pinouts-and-buses.md)):
-
-| Missing | Consequence |
-|---|---|
-| `1PPS` | **No pulse-per-second.** Rules out disciplined-clock / precise-timing uses |
-| `NRST` | No hardware reset. A wedged receiver can only be recovered over UART (or by cutting the Cap's 5 V at the host) |
-| `ON/OFF` | No hardware power/standby toggle. Power saving must be a CASIC software command |
-| `SDA`/`SCL` | The module's I²C port is unavailable; UART is the only channel |
-| LNA `SHDN` | The MAX2659 cannot be shut down; its quiescent current is always paid |
-
-## 5. Power
-
-Vendor figures, conditions unstated **[DOC]**:
-
-- U214 page: **"Power Consumption (Power On): 33.1 mA"**
-- U201 (predecessor) page, state-resolved and far more useful: GPS on / LoRa standby
-  **29.24 mA**; **GPS sleep / LoRa standby 3.16 mA**; GPS on / LoRa TX max **155.03 mA**.
-
-The 3.16 mA figure is the interesting one: putting the GNSS to sleep is worth roughly
-26 mA at 5 V on the predecessor board, i.e. it dominates idle draw. Those numbers are for
-U201 and must not be copied into a U214 table — but the *shape* of the tradeoff carries.
-
-## 6. ⚠ "No satellites, ever" — the RX/TX documentation trap
-
-This is the most-reported problem with the Cap, and it is a documentation defect, not a
-hardware defect.
-
-The Cardputer Mesh Kit page labels EXT pin 12 (`G13`) `UART_RX` and pin 14 (`G15`)
-`UART_TX`. Anyone wiring from that page puts the host's receiver on **G13** and gets
-silence. The correct assignment — confirmed by the schematic, the Cap's own pin-map
-graphic, M5Stack's Arduino example and Meshtastic's `variant.h` — is **host RX = G15,
-host TX = G13**. Full evidence table in
-[`../pinouts-and-buses.md` §1.1](../pinouts-and-buses.md).
-
-Firsthand report, [r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0gv7y/)
-("Adv & LoRa cap doesn't find gps", 15 comments): the owner tried several firmwares
-outdoors with no satellites *seen at all*, concluded the GNSS was dead on arrival, then
-edited the post — *"it seems I got this working eventually at least in meshtastic by
-setting manually the gpio rx and tx pins. See 30 satellites now."* **[COM]**
-
-Second, distinct cause in the same thread: several owners traced GNSS breakage to
-**M5Launcher 2.8.0** leaving stale state, fixed by reflashing an earlier launcher;
-u/bmorcelli (the launcher's author) replied *"I have it fixed on Launcher Beta 2.9"*
-(2026-09-02). **[COM]** So "GPS doesn't work" has at least two unrelated common causes and
-neither is the receiver.
-
-Third, a *non*-bug that looks like one: Meshtastic **degrades position precision by
-default**. u/Cricrimor, [r/CardPuter 2026-01-18](https://old.reddit.com/r/CardPuter/comments/1qf0z9v/):
-*"By default, precision of location is degraded in meshtastic. You can set this in
-parameters > Channels."* The reporting owner had a fix *2 miles off* under Meshtastic while
-M5Stack's own demo was *"spot on"*, and resolved it by changing the channel precision
-setting. **[COM]**
-
-| Symptom | Likely cause |
-|---|---|
-| Zero satellites *seen*, indoors and out, any firmware | RX/TX pins swapped — §6 |
-| Worked, then stopped after a launcher update | Stale launcher state — reflash |
-| Fix obtained but position is ~1–3 km off | Meshtastic channel position-precision setting |
-| Long TTFF every time | Backup cell `BT1` not holding, or the receiver is cold-starting because the almanac was cleared |
-| Works outdoors only | Normal. A 18 mm patch behind a plastic Cap is not an indoor antenna |
-
-## 7. Unresolved
-
-- **`ANT1818-04`** is read from a schematic comment only; no antenna datasheet was located
-  and the manufacturer is not identified.
-- **`GP-02`**, the `M2` symbol comment, is unexplained. The specification table says
-  `ATGM336H-6N@AT6668`; `GP-02` may be an M5Stack internal library name or a second-source
-  designation. Not resolved.
-- Whether 115200 bps is stored in the module or applied by firmware each boot.
-- No independent measurement of TTFF, accuracy or sensitivity for this board.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | Cap **U214**, schematic V1.1, on Cardputer-Adv |
-| Software | `m5stack/TinyGPSPlus` @ `254a1004…` · Meshtastic ≥ 2.7.20 |
-| Evidence | Pinout: schematic + three corroborating sources. Capability: **vendor claim only**. Failure modes: **firsthand community reports**, dated and cited |
-| Confidence | High on wiring; vendor-claim-only on performance |
-| Last verified | 2026-09-04 |
diff --git a/devices/m5stack/cap-lora-1262/features/io-expander-and-rf-switch.md b/devices/m5stack/cap-lora-1262/features/io-expander-and-rf-switch.md
deleted file mode 100644
index 1c8bc30..0000000
--- a/devices/m5stack/cap-lora-1262/features/io-expander-and-rf-switch.md
+++ /dev/null
@@ -1,111 +0,0 @@
-# I/O expander and antenna RF switch — Cap LoRa-1262 (U214)
-
-Snapshot 2026-09-04. `PI4IOE5V6408`, designator `U2`, I²C **0x43** (7-bit).
-
-## 1. Why this page exists
-
-The Cap has exactly **one** thing that must be configured over I²C before RF works, and
-skipping it produces a radio that passes every self-test and transmits into a dead antenna
-port. It is also the mechanism by which firmware distinguishes this Cap from its
-predecessor.
-
-## 2. The chip
-
-| Property | Value | Evidence |
-|---|---|---|
-| Part | **PI4IOE5V6408** — 8-bit I²C GPIO expander, 16-pin | **[SCH]** `U2`; **[DOC]** pin-map graphic |
-| Address | **0x43** | **[SRC]** M5Stack example `PI4IOE5V6408_Class ioe(0x43, …)`; **[SRC]** Meshtastic `#define PI4IO_ADDR 0x43`; **[SCH]** `ADDR` pin 9 strapped |
-| Bus | host I²C, `SDA` = G8, `SCL` = G9 | **[SRC]** `m5::In_I2C.begin(I2C_NUM_0, 8, 9)` |
-| Bus speed used by the vendor | **400 kHz** | **[SRC]** |
-| Pins used | **P0 only** | **[SCH]** |
-| P0 net | `SX_ANT_SW` → `Stamp LoRa-1262 Mini` pin 10 (`SW`) | **[SCH]**, **[DOC]** |
-| P1–P7 | **unconnected** | **[SCH]** |
-| `INT` (pin 1) | **not routed to the host** | **[SCH]** |
-| `RESET` (pin 10) | tied off | **[SCH]** |
-
-Component record: [`components/diodes-incorporated/pi4ioe5v6408`](../../../../components/diodes-incorporated/pi4ioe5v6408/README.md).
-
-## 3. Registers actually used, and by whom
-
-Meshtastic writes raw registers; the numbers are the primary evidence for the register map
-as used here. **[SRC]** `src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp`
-
-| Register | Name in the Meshtastic source | Written value | Meaning |
-|---|---|---|---|
-| `0x03` | `PI4IO_REG_IO_DIR` | `0b00000001` | P0 = **output** |
-| `0x07` | `PI4IO_REG_OUT_H_IM` | `0b00000000` | P0 **not** high-impedance |
-| `0x05` | `PI4IO_REG_OUT_SET` | `0b00000001` | P0 = **HIGH** |
-
-M5Stack's Arduino path does the same three things through `m5::PI4IOE5V6408_Class`:
-
-```cpp
-ioe.setDirection(0, true);        // output
-ioe.setHighImpedance(0, false);   // actually drive
-ioe.digitalWrite(0, true);        // high
-```
-
-**The order matters and the middle step is the one people forget.** The PI4IOE5V6408 has a
-separate high-impedance control per pin; a pin can be configured as an output and still not
-drive. M5Stack's own comment on that line is *"Disable high-impedance so pin can actually
-drive"*.
-
-### 3.1 Upstream got this wrong twice before getting it right
-
-Meshtastic shipped Cardputer-Adv support in **2.7.20** (2026-03-11) and then fixed the
-antenna-switch initialisation **twice**:
-
-| Commit | Date | Message |
-|---|---|---|
-| `3261c04afbdc` | 2026-05-18 | *Fix Antenna Switch on Cardputer* (PR #10491) |
-| `98e0604edf87` | 2026-05-19 | *Fix antenna switch initialization logic once more* |
-
-First release with both: **`v2.7.24.472b14c`, 2026-05-23**. If you are debugging an older
-build, that is a real candidate cause, not a red herring.
-
-## 4. Runtime Cap detection — probe 0x43
-
-Both vendor and upstream code use the presence of the expander as the *identity* of the
-Cap:
-
-| Probe result | Conclusion |
-|---|---|
-| **0x43 ACKs** | **Cap LoRa-1262 (U214)** — set P0 high before RF |
-| **0x43 silent** | **Cap LoRa868 (U201)** — no switch to set; the radio still works |
-| No Cap at all | also silent; the SX1262 will simply fail to `begin()` |
-
-M5Stack's example prints `"Using Cap LoRa-1262"` or `"Using Cap LoRa868"` from exactly this
-test. Meshtastic probes **`Wire1` first, then `Wire`**, and logs `"Cap LoRa-1262 not found"`
-if neither answers — note it does *not* abort; the radio is brought up regardless.
-
-⚠ **This detection is a heuristic, not an identity register.** Anything else at 0x43 on the
-bus — including a Grove sensor plugged into the Cap's own pass-through port — will be
-mistaken for the antenna switch, and the real switch will never be set. There is no vendor
-ID readback in either code path.
-
-## 5. What `SW` actually does is undocumented
-
-Module pin 10 (`SW` here, `SX_ANT_SW` on the PaperMono) is set HIGH once at boot and never
-touched again by any code located — vendor, upstream or community. Whether it selects
-TX/RX paths, enables an external PA/LNA, or selects between antenna connectors is stated
-**nowhere**: there is no `Stamp LoRa-1262` module datasheet
-([`components/m5stack/stamp-lora-1262` §5 G1](../../../../components/m5stack/stamp-lora-1262/README.md)).
-
-Note also that the SX1262 has its own internal `DIO2`-driven RF switch control, which is a
-*different* signal. The PaperMono firmware calls `setDio2AsRfSwitch(true)`; **neither
-M5Stack Cap example does**, and Meshtastic sets `SX126X_DIO2_AS_RF_SWITCH` in `variant.h`.
-So on this board there are plausibly **two** switch mechanisms, one inside the module driven
-by DIO2 and one outside driven by P0, and no document describes either.
-
-## 6. Free resources for a derivative design
-
-`P1`–`P7` are unused and already on the bus. `INT` is unrouted. If you are respinning this
-Cap, that is seven I²C-reachable GPIO available for nothing.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | U214 schematic V1.1. **Not** present on U201 |
-| Software | M5Unified `PI4IOE5V6408_Class`; Meshtastic ≥ 2.7.24 for the corrected init |
-| Evidence | Address and register writes: **two independent source trees agree**, `executed-success` on the reads. `SW` semantics: **unknown** |
-| Last verified | 2026-09-04 |
diff --git a/devices/m5stack/cap-lora-1262/features/lora.md b/devices/m5stack/cap-lora-1262/features/lora.md
deleted file mode 100644
index eb73a2e..0000000
--- a/devices/m5stack/cap-lora-1262/features/lora.md
+++ /dev/null
@@ -1,338 +0,0 @@
-# LoRa — Cap LoRa-1262 (U214) on Cardputer-Adv
-
-> **Common guide:** [`guides/lora`](../../../../guides/lora/README.md) holds the
-> device-independent material — SF/BW/CR against airtime, LoRa vs LoRaWAN vs Meshtastic,
-> regional band plans and duty cycle, `BUSY`/TCXO/RF-switch mechanics, generic failure
-> signatures.
->
-> **Applicability:** the standard approach **applies with deltas**. On this board the
-> radio's `NRST`, `DIO1` and `BUSY` are ordinary host GPIO (unlike the PaperMono, where
-> reset hides behind an I²C expander), but the **antenna switch is behind an I²C expander**
-> at `0x43`, the SPI bus is **shared with the microSD card**, and the **TCXO voltage is
-> disputed between the vendor (3.0 V) and Meshtastic upstream (1.8 V)**.
-
-> **How do I send and receive a LoRa packet?** — §5 (M5Stack/RadioLib), §6 (Meshtastic).
-> **How do I port this to my own firmware?** — §11.
-> Snapshot **2026-09-04** · schematic **V1.1** · nothing tested on hardware here.
-
----
-
-## 1. Hardware path
-
-```
-ESP32-S3 (Stamp-S3A) ── SPI ──▶ M1  Stamp LoRa-1262 Mini ──▶ pin 12 ANT ──▶ E4 SMA/RP-SMA
-  G40 SCK · G14 MOSI · G39 MISO · G5 NSS            (Semtech SX1262 inside)
-  G6  ◀── BUSY   (module pin 3)
-  G4  ◀── DIO1   (module pin 4, net LoRa_IRQ)
-  G3  ───▶ NRST  (module pin 2)
-                                    module pin 10 SW ◀── PI4IOE5V6408 P0 ◀── I²C 0x43 (G8/G9)
-                                    module pin 5 3V3 ◀── JW5712 buck (no host enable)
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Module | `Stamp LoRa-1262 Mini`, `M1` | [`components/m5stack/stamp-lora-1262`](../../../../components/m5stack/stamp-lora-1262/README.md) |
-| Radio | **Semtech SX1262** | [`components/semtech/sx1262`](../../../../components/semtech/sx1262/README.md) |
-| Antenna switch control | `PI4IOE5V6408` P0 @ 0x43 | [`components/diodes-incorporated/pi4ioe5v6408`](../../../../components/diodes-incorporated/pi4ioe5v6408/README.md) |
-| 3.3 V rail | `JW5712` | [`components/joulwatt/jw5712`](../../../../components/joulwatt/jw5712/README.md) |
-| Antenna connector | `E4` `SMA-KE` | [`components/generic/rp-sma-and-sma-antenna-connectors`](../../../../components/generic/rp-sma-and-sma-antenna-connectors/README.md) |
-
-## 2. Resources consumed
-
-| Resource | Value | Contention |
-|---|---|---|
-| Host GPIO | **7** — G40, G14, G39 (SPI), G5 (NSS), G6 (BUSY), G4 (DIO1), G3 (NRST) | SPI trio shared with **microSD** (CS = G12) |
-| I²C | `0x43` on G8/G9 | shared with TCA8418 keyboard, BMI270 IMU, ES8311 codec, Grove port |
-| SPI clock | M5Stack examples leave it to RadioLib's default; Meshtastic runs the shared bus with `spiLock` arbitration | |
-| Interrupt | G4, rising edge (RadioLib's `setPacketReceivedAction`) | |
-| 3.3 V budget | `JW5712` sheet annotation `IOUT: 0~0.6 A`; SX1262 TX at +22 dBm is the dominant load | |
-
-> **The SPI bus is shared with the SD card and this is deliberate upstream.** Meshtastic's
-> `variant.h` comment is explicit: *"SD card slot — shares the SPI bus with the LoRa radio
-> (separate chip select). The default SPI instance is used; spiLock arbitrates access
-> between radio and SD."* Any firmware that opens the radio on a dedicated bus and the SD
-> on another will fight itself. **[SRC]**
-
-## 3. Bring-up order
-
-Unlike the PaperMono, **there is no host power-enable to sequence** — the JW5712 comes up
-with the host's 5 V (`R1` 10 kΩ pull-up on `ENB`). What *does* have to happen before RF
-works is the antenna switch:
-
-1. Bring up I²C on **G8/G9**.
-2. Probe **0x43**. Present ⇒ Cap LoRa-1262. Absent ⇒ Cap LoRa868 (or no Cap).
-3. On the expander: **P0 → output**, **P0 → not high-impedance**, **P0 → HIGH**.
-4. Release `NRST` (G3) — RadioLib will do this if you pass `GPIO_NUM_3` as the reset pin.
-5. `radio.begin(...)`.
-
-Skipping step 3 gives a radio that initialises perfectly and transmits into a dead port.
-Both M5Stack and Meshtastic do the three expander writes in exactly that order. **[SRC]**
-
-## 4. Software options
-
-| Stack | What it gives you | Where |
-|---|---|---|
-| **RadioLib** (jgromes) | Raw LoRa / (G)FSK point-to-point. What both M5Stack examples use. **MIT** licensed (verified from the repository's licence metadata, 2026-09-04) | `github.com/jgromes/RadioLib`, latest release **7.7.1** (2026-05-31), head `187ef247…` (2026-08-22) |
-| **Meshtastic** | Full mesh firmware with UI, BLE, GNSS, keyboard. **Officially supported upstream** — see §6 | `meshtastic/firmware`, board `m5stack-cardputer-adv` |
-| **MeshCore** | Alternative mesh protocol. Community ports only | §7 of [`../projects-and-community.md`](../projects-and-community.md) |
-| **UiFlow2 / MicroPython** | Block + MicroPython API, `uiflow-micropython.readthedocs.io/en/latest/cap/lora1262.html` | vendor |
-| **LoRaWAN** | **Nothing demonstrated.** RadioLib has a LoRaWAN class that supports SX1262, but no M5Stack example, no community project and no regional-parameters configuration for this board was located | gap **G8** |
-| M5Stack-specific LoRa driver | **Does not exist.** There is no `M5Unit-LoRa`-style library for either Cap; the docs' "Arduino LoRa Driver Library" link points straight at RadioLib | verified by GitHub org search, 0 results |
-
-## 5. The vendor's exact radio configuration
-
-From M5Stack's Arduino guide (served at `/en/arduino/projects/cap/cap_lora868`, which
-covers **both** Caps and auto-detects which one is fitted). `executed-success` on the read;
-`not-tested` on hardware. **[DOC]**
-
-```cpp
-#include <M5Unified.h>
-#include <RadioLib.h>
-#include "utility/PI4IOE5V6408_Class.hpp"
-
-#define LORA_BW           125.0f   // kHz
-#define LORA_SF           12
-#define LORA_CR           5        // 4/5
-#define LORA_FREQ         868.0    // MHz
-#define LORA_SYNC_WORD    0x34
-#define LORA_TX_POWER     22       // dBm
-#define LORA_PREAMBLE_LEN 20       // symbols
-
-// SX1262 PIN order: NSS, IRQ(DIO1), RST, BUSY
-SX1262 radio = new Module(GPIO_NUM_5, GPIO_NUM_4, GPIO_NUM_3, GPIO_NUM_6);
-
-m5::PI4IOE5V6408_Class ioe(0x43, 400000, &m5::In_I2C);
-
-void setup() {
-    M5.begin();
-    if (!m5::In_I2C.begin(I2C_NUM_0, 8, 9)) { /* fail */ }
-
-    if (ioe.begin()) {                    // 0x43 present -> Cap LoRa-1262
-        ioe.setDirection(0, true);        // P0 = output
-        ioe.setHighImpedance(0, false);   // actually drive it
-        ioe.digitalWrite(0, true);        // P0 = HIGH -> antenna switch on
-    } else {                              // 0x43 absent  -> Cap LoRa868
-        /* no switch to set */
-    }
-
-    int state = radio.begin(LORA_FREQ, LORA_BW, LORA_SF, LORA_CR,
-                            LORA_SYNC_WORD, LORA_TX_POWER, LORA_PREAMBLE_LEN,
-                            3.0,     // tcxoVoltage  <-- see §8
-                            true);   // useRegulatorLDO
-    radio.setCurrentLimit(140);      // 0-140 mA, 2.5 mA step
-    radio.setPacketReceivedAction(setFlag);
-    radio.startReceive();
-}
-```
-
-Receive-side helpers in the same guide: `radio.readData()`, `radio.getPacketLength()`,
-`radio.getRSSI()`, `radio.getSNR()`, `radio.getFrequencyError()`.
-
-**Prose on those numbers.** SF12 / BW 125 kHz / CR 4/5 at 868.0 MHz is a *long-range demo*
-setting: on the order of ~250 bit/s of raw chip rate with airtimes measured in seconds for
-a short payload. It is not a sane default for anything interactive, and in EU 868 the 1 %
-duty-cycle limit will bite quickly at that airtime. `useRegulatorLDO = true` disables the
-SX1262's internal DC-DC and roughly doubles receive current — the same choice the PaperMono
-firmware makes, and the SX1262 record explains what it costs
-([`components/semtech/sx1262` §5.4](../../../../components/semtech/sx1262/README.md)).
-
-## 6. Meshtastic — officially supported, with the exact provenance
-
-| Fact | Value |
-|---|---|
-| Board target | **`m5stack-cardputer-adv`** (PlatformIO env `[env:m5stack-cardputer-adv]`, `board = m5stack-stamps3`) |
-| Variant directory | [`variants/esp32s3/m5stack_cardputer_adv/`](https://github.com/meshtastic/firmware/tree/master/variants/esp32s3/m5stack_cardputer_adv) — `variant.h` (2 349 B, blob `778d95f200fe116a7a413d47c7276d4193d6c7dc`), `platformio.ini` (1 164 B, blob `a38317e5be3fd62607ad6b06a1f7c7ea176a1657`), `pins_arduino.h` (494 B, blob `12581cde0200a5787d77889d4abe418229cc6952`) |
-| Extra variant code | [`src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp`](https://github.com/meshtastic/firmware/blob/master/src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp) (2 782 B) |
-| Introduced by | PR **[#9540 "Cardputer Kit"](https://github.com/meshtastic/firmware/pull/9540)** by **caveman99**, opened 2026-02-05, **merged 2026-03-06T11:34:41Z**, merge commit **`969aefa551d645e6110be11f330774e15ad9c87d`** |
-| **First release containing it** | **`v2.7.20.6658ec2`, published 2026-03-11T11:43:26Z** (prerelease). Verified with the compare API: `969aefa5…` is **17 commits behind** that tag and **177 commits ahead** of the previous release `v2.7.19.bb3d6d5` (2026-02-11) |
-| Device index | `firmware-2.7.20.6658ec2.json` lists `{"board": "m5stack-cardputer-adv", "platform": "esp32s3"}`; still present in `firmware-2.7.26.54e0d8d.json` |
-| Protobuf hardware model | **`meshtastic_HardwareModel_M5STACK_CARDPUTER_ADV = 112`** (`src/mesh/generated/meshtastic/mesh.pb.h`). Sibling entry `M5STACK_C6L = 111` |
-| Antenna-switch bug + fix | The expander init was **wrong at first**: [PR #10491 "Fix Antenna Switch on Cardputer"](https://github.com/meshtastic/firmware/pull/10491) merged **2026-05-18** (`3261c04afbdc`), followed by **`98e0604edf87`** *"Fix antenna switch initialization logic once more"* on **2026-05-19**. First release with both: **`v2.7.24.472b14c`, 2026-05-23** |
-| Other notable commits | `a4b55bc6f24a` 2026-04-22 moved `variant.cpp` to `extra_variants/`; `163c54877c5b` 2026-03-24 fixed I2S sound; `8d3ad2a1462d` 2026-08-02 removed `board_check` |
-
-Radio-relevant `variant.h` lines, verbatim:
-
-```c
-#define LORA_SCK 40
-#define LORA_MISO 39
-#define LORA_MOSI 14
-#define LORA_CS 5              // NSS
-#define USE_SX1262
-#define LORA_DIO0 -1
-#define LORA_RESET 3
-#define LORA_DIO1 4
-#define LORA_DIO2 6
-#define SX126X_CS     LORA_CS
-#define SX126X_DIO1   LORA_DIO1
-#define SX126X_BUSY   LORA_DIO2      // note: BUSY is aliased onto the DIO2 macro
-#define SX126X_RESET  LORA_RESET
-#define SX126X_DIO2_AS_RF_SWITCH
-#define SX126X_DIO3_TCXO_VOLTAGE 1.8
-#define TCXO_OPTIONAL
-```
-
-And the expander init, verbatim from `variant.cpp`:
-
-```c
-#define PI4IO_ADDR        0x43
-#define PI4IO_REG_IO_DIR  0x03
-#define PI4IO_REG_OUT_SET 0x05
-#define PI4IO_REG_OUT_H_IM 0x07
-// probes Wire1 then Wire; logs "Cap LoRa-1262 not found" if neither answers
-pi4ioWrite(bus, PI4IO_REG_IO_DIR,   0b00000001);   // P0 output
-pi4ioWrite(bus, PI4IO_REG_OUT_H_IM, 0b00000000);   // P0 not high-Z
-pi4ioWrite(bus, PI4IO_REG_OUT_SET,  0b00000001);   // P0 high
-```
-
-Its comment says *"PI4IOE5V6408 on the optional Cap LoRa-1262 **(and Cap LoRa868)**"* —
-which contradicts M5Stack's comparison table, where the U201 has **no** RF-switch control.
-The code probes and degrades gracefully either way, so the discrepancy is inert; it is
-recorded as conflict **G4** in [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-### 6.1 Meshtastic licensing of the Mesh Kit
-
-M5Stack states the **Cardputer Mesh Kit has been officially licensed by Meshtastic**, with
-a registration flow at an "M5 Meshtastic Device registration page", and adds: *"Only
-devices in the Cardputer Mesh Kit set can be registered. Other Cardputer/-Adv devices are
-not eligible."* **[DOC]** So a Cardputer-Adv + separately-bought U214 runs the same
-firmware but cannot claim the authorised-device mark. See
-[`../../cardputer-mesh-kit/README.md`](../../cardputer-mesh-kit/README.md).
-
-## 7. Regional bands, antennas and legality — the honest position
-
-| Question | Answer |
-|---|---|
-| Band the SKU claims | **868 – 923 MHz**, one wideband range |
-| Regional variants | **None.** One SKU worldwide |
-| Antenna supplied | **One** 3 dBi 108 mm whip, **868 MHz** |
-| What M5Stack's example uses | **868.0 MHz** hard-coded (EU) |
-| Certification identifier | **None published.** `docs.m5stack.com/en/certification` has no entry for `U214`, `Cap LoRa` or `Cardputer` |
-| Duty-cycle handling | none in any vendor code |
-
-Practical consequence, reported repeatedly by owners: **North-American buyers get an
-868 MHz antenna and have to source a 915 MHz one.** u/Hyena_Triangles, 2026-08-22:
-*"your antennae is 868MHz and for North America you need 915MHz … Edit: new antenna
-worked."* ([r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1vvlcs9/)). Another
-owner in the same thread reports the stock antenna working fine in NA, which is what you
-would expect from a mismatched-but-not-catastrophic whip. u/goattrybe: *"the 868mhz antenna
-will work for 915 btw … just a tiny difference in size"*
-([r/M5Stack, 2026-02-03](https://old.reddit.com/r/M5Stack/comments/1pzazbe/)). **[COM]**
-Three reports across the ~217 threads reviewed; that is enough to say the problem occurs,
-not enough to quantify how often.
-
-**The connector polarity is genuinely disputed** and it will cost you an adapter if you get
-it wrong — see conflict **G1** in [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-## 8. ⚠ The TCXO voltage conflict — the highest-stakes open question here
-
-| Source | `DIO3` TCXO voltage |
-|---|---|
-| M5Stack Arduino example (both Caps) | **3.0 V** |
-| M5Stack PaperMono firmware, same `Stamp LoRa-1262` module family | **3.0 V** |
-| **Meshtastic upstream `variant.h`** | **1.8 V**, plus `TCXO_OPTIONAL` |
-
-On the SX1262, `DIO3` is a *regulated supply output* for a TCXO, not a logic pin, and
-setting it wrong is the classic failure that produces a radio which initialises cleanly and
-then never transmits or receives ([`components/semtech/sx1262` §5.2](../../../../components/semtech/sx1262/README.md)).
-Both values are in shipping software and both are reported to work, which means either the
-TCXO tolerates a wide supply or `TCXO_OPTIONAL` is masking the difference by retrying
-without TCXO. **No module datasheet exists** to settle it (gap **G2**).
-
-**Guidance:** start from **3.0 V**, because that is the vendor's own number for this exact
-board. If you are cloning Meshtastic's behaviour, use 1.8 V *with* the optional-retry path.
-Do not silently change either to `0`.
-
-## 9. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| LoRa + Wi-Fi/BLE | ✅ different bands, different antennas | sub-GHz SX1262 vs 2.4 GHz ESP32-S3. They share CPU and battery, not spectrum |
-| **LoRa + microSD** | ⚠ **shared SPI bus** | G40/G14/G39 are the SD bus too (`SDCARD_CS` 12). Needs chip-select discipline; Meshtastic uses `spiLock` |
-| LoRa + GNSS (same Cap) | ✅ | GNSS is UART1; different peripheral entirely |
-| LoRa + Grove I²C device | ⚠ | The expander at `0x43` sits on the same bus a Grove sensor joins. Address collisions with `0x43` will break the antenna switch |
-| LoRa + keyboard / IMU / audio | ⚠ I²C bus contention only | TCA8418, BMI270 and ES8311 all live on G8/G9 |
-| LoRa TX + battery | ⚠ unquantified | +22 dBm through a 5 V→3.3 V buck off a 1750 mAh cell. Vendor gives one aggregate number (163.4 mA at 5 V) with no stated conditions |
-| LoRa + deep sleep | ❓ untested | No host power-gate exists; the Cap draws from the host's 5 V rail whenever it is up |
-
-## 10. Debugging
-
-| Symptom | First thing to check |
-|---|---|
-| `radio.begin()` returns an error | Wrong pin order in `new Module(...)` — it is **NSS, DIO1, RST, BUSY** = 5, 4, 3, 6 |
-| Initialises but nothing is heard, nothing gets through | **Antenna switch not set** (expander `0x43`, P0 high) — §3. Then the TCXO voltage — §8 |
-| Works at 1 m, dead at 50 m | Wrong-band antenna (868 whip on 915 MHz), or the RP-SMA/SMA adapter is not making contact |
-| Radio fine, "GPS not found" | Different subsystem — [`gnss.md` §6](gnss.md) |
-| Works in one firmware, not another | A recurring **launcher/state** problem, not the radio: several owners traced 2026-08 breakage to M5Launcher 2.8.0 and fixed it by reflashing an earlier launcher ([r/CardPuter 2026-08-28](https://old.reddit.com/r/CardPuter/comments/1w0gv7y/)) |
-| SD card corrupts while the radio is busy | SPI arbitration — §2 |
-
-## 11. Porting checklist — what it takes to add SX1262 LoRa to *other* firmware
-
-Written for the wider project's goal of adding LoRa to e-ink reader firmware
-(CrossPoint Reader / FreeInk). Compare with the PaperMono's arrangement in
-[`devices/m5stack/papermono/features/lora.md`](../../papermono/features/lora.md), which is
-the *same radio module family* wired very differently — reading the two side by side is the
-fastest way to see which parts are the chip's and which are the board's.
-
-**Minimum hardware resources an SX1262 needs from a host:**
-
-| Resource | Count | Negotiable? |
-|---|---|---|
-| SPI (SCK/MOSI/MISO) | 3 | Shareable with other SPI devices if you arbitrate chip-selects |
-| Chip select (`NSS`) | 1 | No |
-| `BUSY` | 1 | **No.** It is a mandatory handshake, not a status LED. Polling SPI without it loses commands |
-| `DIO1` interrupt | 1 | Strongly recommended; polling works but wastes power |
-| `NRST` | 1 | Can be omitted (`RADIOLIB_NC`) *only* if something else resets the module — PaperMono routes it through an I²C expander |
-| Antenna/RF switch control | 0–1 | **Board-specific.** Cap LoRa-1262 needs one I²C write; PaperMono needs a different expander pin; Cap LoRa868 needs nothing |
-| 3.3 V at TX current | — | Budget for +22 dBm; SX1262 `setCurrentLimit()` caps at 140 mA |
-
-**Minimum software:**
-
-1. **RadioLib** — MIT, header-only-ish Arduino/ESP-IDF library, ~1 dependency-free. It is
-   what M5Stack, Meshtastic and the PaperMono firmware all use. If your firmware is not
-   Arduino, implement a `RadioLibHal` subclass over your SPI/GPIO/delay primitives — that is
-   exactly what M5Stack's PaperMono `hal_lora.cpp` does in ~300 lines.
-2. Construct `new Module(nss, dio1, rst, busy)` — **in that order**; getting it wrong is the
-   most common porting bug.
-3. `begin(freq, bw, sf, cr, syncWord, power, preamble, tcxoVoltage, useRegulatorLDO)`.
-   `tcxoVoltage` **must** match the module's fitted TCXO (§8) or the radio silently fails.
-4. `setDio2AsRfSwitch(true)` if the module uses DIO2 internally. **PaperMono does; the Cap
-   examples do not call it** — one more reason not to copy a config across boards.
-5. Board-specific: whatever pin turns the external antenna switch on.
-
-**What is *not* portable between these boards, despite the same radio:**
-
-| Aspect | Cap LoRa-1262 | PaperMono |
-|---|---|---|
-| Reset | host GPIO G3 | I²C expander `M5IOE1` IO10 |
-| Antenna switch | I²C expander `PI4IOE5V6408` P0 @ 0x43 | I²C expander `M5IOE1` IO2 |
-| Rail enable | none (always on) | `M5PM1` G2 gates `3V3_L2_LoRa` |
-| SPI host | shared with microSD | dedicated (display is on a separate host) |
-| `setDio2AsRfSwitch` | not called in the vendor example | `true` |
-| TCXO | 3.0 V (vendor) / 1.8 V (Meshtastic) | 3.0 V |
-| Antenna | external SMA + rubber duck | built-in FPC |
-
-**If you want mesh networking rather than raw packets**, do not write it yourself: the
-Meshtastic variant above is 3 small files plus one `variant.cpp`, and the whole
-board-support delta for a new board is roughly *that* much work. The expensive part of
-Meshtastic is the UI/display/input integration, not the radio.
-
-## 12. Unresolved
-
-- **TCXO voltage** (§8) — vendor 3.0 V vs upstream 1.8 V, unsettled.
-- **`SW` (module pin 10) semantics** — TX/RX path select, PA/LNA enable, or connector
-  select? Nothing says. Both vendor and upstream code set it HIGH once and never touch it.
-- **RF output power at the connector**, insertion loss, and the internal matching network:
-  no module datasheet exists.
-- **No range, throughput, sensitivity or current measurement** from anyone, vendor or
-  community, for this board.
-- **LoRaWAN**: never demonstrated on this hardware.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | Cap **U214**, schematic **V1.1 / 2025-10-29**, on **Cardputer-Adv** (also claimed for CardputerZero) |
-| Firmware range | RadioLib ≥ 7.x · Meshtastic ≥ **2.7.20** (antenna-switch fix from **2.7.24**) · M5Unified with `PI4IOE5V6408_Class` |
-| Evidence | Pin map: **schematic + vendor pin-map + upstream variant.h, three-way cross-confirmed**. Radio parameters: **read from vendor source**, `executed-success`. TCXO: **conflicting primary sources**. RF performance: **none** |
-| Confidence | High on wiring and software configuration; **none on RF performance or on legality in any region** |
-| Last verified | **2026-09-04** |
diff --git a/devices/m5stack/cap-lora-1262/features/power-and-grove.md b/devices/m5stack/cap-lora-1262/features/power-and-grove.md
deleted file mode 100644
index 2b913b1..0000000
--- a/devices/m5stack/cap-lora-1262/features/power-and-grove.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# Power rail and Grove pass-through — Cap LoRa-1262 (U214)
-
-Snapshot 2026-09-04, schematic V1.1. Nothing measured.
-
-## 1. Rail
-
-| Item | Value | Evidence |
-|---|---|---|
-| Input | **5 V** from the Cap-Bus (pin 5 `5V_OUT` from host, pin 7 `5V_IN` to host) | **[SCH]**, **[DOC]** |
-| Regulator | **`U3` JW5712** synchronous buck | **[SCH]** |
-| Output | `VDD_3V3`, sheet annotation **`IOUT: 0~0.6 A`** | **[SCH]** |
-| Inductor | `L2` = `WPN201610U2R2MT`, 2.2 µH | **[SCH]** |
-| Input caps | `C1` 1 nF, `C2`/`C3`/`C4` 22 µF | **[SCH]** |
-| Output caps | `C15` 22 µF, `C12` 470 µF, `C16`/`C17` 100 nF | **[SCH]** |
-| Feedback/mode straps | `VSEL1` (C1), `VSEL2` (D1), `VSEL3` (D2) on the JW5712's chip-scale package | **[SCH]** |
-| **Enable** | `R1` **10 kΩ** adjacent to `ENB` and to the `+5V`/`+5VOUT` labels | **[SCH]**; polarity **`inferred`, not traced** |
-
-**There is no host power-enable pin on this Cap.** Cap-Bus pin 8 — which the sibling
-[Cap CC1101](../../cap-cc1101/features/power-and-grove.md) uses as `POWER_EN` — is
-`LoRa_RST` here. So the practical model is: *if the host is powering the EXT connector, the
-Cap is on.* Anything wanting to cut GNSS/LoRa power entirely has to do it on the host side.
-
-> ⚠ Honest limit on that claim: the `ENB` net was **not** traced end-to-end through the PDF
-> text layer. What is established is that a 10 kΩ resistor sits between the `+5V`/`+5VOUT`
-> labels and the regulator's `ENB` pin, and that no Cap-Bus pin carries an enable signal.
-> The conclusion "always on" follows from those two facts; it is `inferred`.
-
-## 2. Consumers of `VDD_3V3`
-
-| Load | Notes |
-|---|---|
-| `M1` Stamp LoRa-1262 Mini (pin 5) | dominant during TX at +22 dBm |
-| `M2` ATGM336H-6N `VCC` (pin 8) via `FB3` 120 Ω/MB | |
-| `M2` `VCC_RF` (pin 14) via `FB2` 120 Ω/MB | separate ferrite for the RF section |
-| `U1` MAX2659 LNA | always on — `SHDN` is tied |
-| `U2` PI4IOE5V6408 | µA-class |
-
-The two ferrite beads are worth noticing: M5Stack isolates the GNSS digital supply and the
-GNSS RF supply from each other and from the LoRa module's rail. That is the conventional
-mitigation for LoRa TX transients desensitising a co-located GNSS front end. Whether it is
-*sufficient* on this board — a +22 dBm transmitter roughly 40 mm from a GNSS patch — is
-**not** measured by anyone.
-
-## 3. Grove pass-through (`J2`, HY2.0-4P)
-
-| Grove wire | Colour | Net | Host |
-|---|---|---|---|
-| 1 | Black | `GND` | — |
-| 2 | Red | `5V` (`+5VOUT`) | host 5 V |
-| 3 | Yellow | `SDA` | **G8** |
-| 4 | White | `SCL` | **G9** |
-
-`R3` = 10 kΩ pull-up. **This is the *same* I²C bus the Cap's own expander sits on**, and the
-same bus as the host's keyboard controller (TCA8418), IMU (BMI270) and audio codec (ES8311).
-
-Consequences worth stating plainly:
-
-- **This port is not a free extra bus.** It is a tap onto a busy shared one.
-- **A Grove device at 0x43 will break the antenna switch** and, worse, will be
-  *mis-detected as the Cap itself* by both M5Stack's and Meshtastic's probe
-  ([`io-expander-and-rf-switch.md` §4](io-expander-and-rf-switch.md)).
-- The predecessor **Cap LoRa868 (U201) has no Grove port at all** — adding it is one of the
-  four differences M5Stack lists between the two.
-- Community context: the Grove-port + Cap combination is a recurring source of confusion.
-  See *"Multiple grove addons at once?"*
-  ([r/CardPuter 2026-08-07](https://old.reddit.com/r/CardPuter/comments/1vifzzz/), 17
-  comments) and u/newbie20250's report that an RFID2 unit worked on the Cardputer-Adv's own
-  Grove port but not through the Cap
-  ([r/M5Stack 2026-04-01](https://old.reddit.com/r/M5Stack/comments/1pzazbe/)). Both are
-  `reported-working`-grade anecdotes, unverified here.
-
-## 4. Host-side 5 V direction switch
-
-The Cardputer-Adv has a **5 V IN/OUT switch** next to its Grove port. u/pyreht reported
-(firsthand experimentation, [r/CardPuter 2026-06-12](https://old.reddit.com/r/CardPuter/comments/1u3qeez/))
-that with the switch in the *out* position and a load on the Grove port, the battery-sense
-pin G10 reads above 5 V, and that injecting 5 V into the Grove port with the switch in the
-*in* position also perturbs it. That is a **host** behaviour, not a Cap behaviour, but it
-affects anyone reading battery voltage while a Cap is fitted. Recorded as a firsthand
-report; not verified here. Belongs to `devices/m5stack/cardputer-adv/`.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware | U214 schematic V1.1 |
-| Evidence | Parts and values: **schematic**, `executed-success`. Enable polarity: **`inferred`**. Grove I²C sharing: schematic + vendor pin-map |
-| Last verified | 2026-09-04 |
diff --git a/devices/m5stack/cap-lora-1262/gaps-and-conflicts.md b/devices/m5stack/cap-lora-1262/gaps-and-conflicts.md
deleted file mode 100644
index 58cf456..0000000
--- a/devices/m5stack/cap-lora-1262/gaps-and-conflicts.md
+++ /dev/null
@@ -1,96 +0,0 @@
-# Gaps and conflicts — Cap LoRa-1262 (U214)
-
-Snapshot 2026-09-04. Each row states what would settle it.
-
-## Conflicts between sources
-
-### G1 — ⚠ RP-SMA or SMA? The vendor contradicts itself and owners disagree
-
-| Source | Says |
-|---|---|
-| `docs.m5stack.com/en/cap/Cap_LoRa-1262` prose | *"equipped by default with an external **RP-SMA** antenna"* |
-| Same page, specification row | *"Interface Type **RP-SMA (internal thread, internal hole)**"* |
-| `shop.m5stack.com` product description | *"equipped by default with an external **SMA** antenna"* |
-| Schematic, `E4` | footprint comment **`SMA-KE`** |
-| Cap CC1101 schematic, `E1` (same connector family) | **`SMA-TH_KH-SMA-KE-Z`** |
-
-**The specification row is self-contradictory.** *Internal thread + internal hole* describes
-a **standard SMA female (jack)** — RP-SMA female has an internal thread and an inner **pin**.
-So the row's parenthetical and its label disagree.
-
-Owners disagree too, which is the practical tell:
-
-- u/skinwill, 2025-12-30: *"Looks like RP-SMA in the image."* u/jader242: *"It's still rp."*
-  ([r/M5Stack](https://old.reddit.com/r/M5Stack/comments/1pzazbe/))
-- u/malonestar, 2025-11-24, with a photo: *"I think it is regular SMA female, I don't see
-  any indications anywhere to RP-SMA … Worked for me with a SMA antenna."*
-  ([r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1nkyy4c/)) — that thread is
-  about the **U201** predecessor, which uses the same connector family
-- u/Big-Bunch2804, 2026-08-23: *"Just so you know it's a rp-sma. They are a little specific."*
-  ([r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1vvlcs9/))
-
-**Would settle it:** a close photograph of `E4` showing whether the centre contact is a
-socket or a pin, or an M5Stack part number for the connector. Until then, buy an adapter
-kit — which is what owners repeatedly end up doing. See
-[`components/generic/rp-sma-and-sma-antenna-connectors`](../../../components/generic/rp-sma-and-sma-antenna-connectors/README.md).
-
-### G2 — TCXO voltage: 3.0 V (M5Stack) vs 1.8 V (Meshtastic)
-
-Both in shipping software, both reported working. Detailed in
-[`features/lora.md` §8](features/lora.md). **Would settle it:** a `Stamp LoRa-1262` module
-datasheet or a photograph of the TCXO's marking under the shield can.
-
-### G3 — `FM8625H` appears on the vendor pin-map but not on the schematic
-
-The Cap LoRa-1262 pin-map graphic names an element **`FM8625H`** in the block that also
-shows `PI4IOE5V6408 P0 → SX_ANT_SW`. The V1.1 schematic's only regulator is **`U3` =
-`JW5712`** and there is no `FM8625H` designator anywhere in its `CO`-marker census.
-Possibilities: a second-source regulator on a different build, a stale graphic, or a part
-that exists inside the shielded `Stamp LoRa-1262 Mini` module. Unresolved. **Would settle
-it:** a photograph of the board under the shield, or a later schematic revision.
-
-### G4 — Does the Cap LoRa868 have a PI4IOE5V6408 or not?
-
-M5Stack's own comparison table says U201 has **"RF Switch Control: None"**, and the U201
-pin-map shows no expander. Meshtastic's `variant.cpp` comment says
-*"PI4IOE5V6408 on the optional Cap LoRa-1262 **(and Cap LoRa868)**"*. The code probes and
-tolerates absence, so nothing breaks either way. Unresolved; the comment is probably just
-loose. **Would settle it:** the U201 schematic (published, **not fetched** in this pass).
-
-### G5 — The Cardputer-Adv EXT pin labels `UART_RX`/`UART_TX` are backwards
-
-Four sources against one. Fully documented in
-[`pinouts-and-buses.md` §1.1](pinouts-and-buses.md). This one **is** resolved; it is listed
-here because the wrong label is still live on M5Stack's Mesh Kit page and has cost at least
-one owner a working GNSS.
-
-### G6 — Two numbering conventions for the same 14-pin connector
-
-Cap pages number LEFT 1–7 / RIGHT 14–8; the Mesh Kit page numbers odd/even. Not an error,
-but a guaranteed source of miscommunication. [`pinouts-and-buses.md` §1](pinouts-and-buses.md).
-
-## Missing documentation
-
-| # | Missing | Consequence | Would settle it |
-|---|---|---|---|
-| **G7** | **No `Stamp LoRa-1262` module datasheet, in any form.** M5Stack publishes the *Semtech chip* datasheet instead | Unknown: module RF output at the connector, internal matching, TCXO vs XTAL, which SX1262 DIO pins are consumed internally, supply current, `SW` semantics | M5Stack publishing one; or a teardown photograph under the can |
-| **G8** | **No certification identifier of any kind** — no FCC ID, CE, IC, RCM, TELEC/MIC. `docs.m5stack.com/en/certification` has no entry for `U214`, `Cap LoRa` or `Cardputer` | One wideband 868–923 MHz SKU sold worldwide with nothing to point at. Matters for anyone deploying rather than benching | A regulatory database hit; not found by this pass |
-| **G9** | **No LoRaWAN anything** | No regional band plan, no duty-cycle handling, no join example, no community project | Someone demonstrating it |
-| **G10** | **No RF or power measurement by anyone** | Every performance claim on this page is a vendor claim | A firsthand measurement |
-| **G11** | `1PPS`, `NRST`, `ON/OFF`, I²C of the GNSS module are **not routed** | No precise timing, no hardware reset, no hardware standby | Nothing — it is a design decision, recorded so nobody hunts for the pins |
-| **G12** | `ANT1818-04` (GNSS patch antenna) and `GP-02` (GNSS module comment) are unexplained strings from the schematic | Cannot source an exact replacement antenna | A BOM or an M5Stack parts list |
-| **G13** | The `ENB` net of `U3` was **not traced end-to-end**; "always on" is `inferred` from `R1`'s adjacency plus the absence of an enable pin on the bus | A future agent should verify before relying on it for a power model | Rendering the sheet, or a netlist-grade extraction |
-| **G14** | The UiFlow2/MicroPython API page was **enumerated but not fetched** | MicroPython users have no coverage here | Fetching `uiflow-micropython.readthedocs.io/en/latest/cap/lora1262.html` |
-| **G15** | The **U201 schematic** and the **U214 structure/3D files** (`M5_Hardware/Products/U214_Cap_LoRa-1262/Structures`) were located but **not fetched** | Mechanical work and U201 verification blocked | Fetching them |
-
-## Method limitations of this pass
-
-- No hardware was present. Nothing was measured, flashed or executed on-device.
-- The schematic PDF was parsed with a **pypdf-based re-implementation** of pdftotext's
-  bbox output because poppler is absent on this host. Row-band grouping is reliable;
-  the repo's `PI<desig><pin>`→net matcher is **not** under this extractor, so every pin
-  assertion was cross-checked against M5Stack's published pin-map rather than taken from
-  the matcher. See [`commands.md`](commands.md) and the
-  [scratch README](../../../scratch/m5stack-lora-expansions/README.md).
-- The schematic was **not rendered**; claims that depend on drawn geometry (net routing
-  through resistors, no-connect glyphs) are labelled `inferred` where they occur.
diff --git a/devices/m5stack/cap-lora-1262/market-and-pricing.md b/devices/m5stack/cap-lora-1262/market-and-pricing.md
deleted file mode 100644
index 726a9c5..0000000
--- a/devices/m5stack/cap-lora-1262/market-and-pricing.md
+++ /dev/null
@@ -1,148 +0,0 @@
-# Market and pricing — Cap LoRa-1262 (U214)
-
-All observations **2026-09-04**, region: M5Stack official store (ships from Shenzhen),
-currency **USD**, prices as returned by the Shopify product JSON (item price only —
-shipping, duty and tax excluded).
-
-## 1. Official store, dated
-
-| SKU | Product | Price | Published | Status |
-|---|---|---|---|---|
-| **U214** | **Cap LoRa-1262** | **USD 14.50** | 2025-12-30 | current |
-| U201 | LoRa+GPS Cap ("Cap LoRa868") | USD 14.50 | 2025-09-05 | **[EOL]** |
-| U219 | [Cap CC1101 & NFC](../cap-cc1101/market-and-pricing.md) | USD 18.95 | 2026-08-28 | current |
-| K132-ADV | Cardputer Adv (host) | USD 29.90 | 2025-09-05 | current |
-| K152 | [Cardputer Mesh Kit](../cardputer-mesh-kit/README.md) = ADV + U214 + antenna | USD 48.00 | 2026-04-30 | Backorder (tag) |
-
-**The successor did not raise the price.** U201 and U214 are both USD 14.50; the +2 dB, the
-shield can, the Grove port and the RF switch came at no list-price change.
-
-### 1.1 Is the Mesh Kit worth it?
-
-Bare arithmetic: 29.90 + 14.50 = **44.40** vs **48.00** for K152 — a **USD 3.60 premium**.
-What the premium buys: a green-back Cardputer-Adv, the rubber-duck antenna (also included
-with a standalone U214), two M2 screws, a hex key, a safety sticker, **Meshtastic
-pre-flashed**, and — the only part that cannot be bought separately — **eligibility for
-Meshtastic authorised-device registration**. M5Stack states: *"Only devices in the
-Cardputer Mesh Kit set can be registered. Other Cardputer/-Adv devices are not eligible."*
-**[DOC]**
-
-The community asked this question directly and did not reach consensus:
-*"Cardputer Mesh Kit vs buying Cardputer-Adv + Cap LoRa-1262 separately — worth it…?"*
-([r/CardPuter 2026-07-13](https://old.reddit.com/r/CardPuter/comments/1uv6gt3/), 9 comments)
-and *"meshtastic kit vs cardputer adv"*
-([r/CardPuter 2026-07-30](https://old.reddit.com/r/CardPuter/comments/1vb2fmc/), 10 comments).
-**[COM]**
-
-## 2. Availability
-
-Sold out repeatedly after launch. Firsthand reports:
-
-- u/resentedpoet, 2025-12-31: *"Ordered one earlier and glad I did. See they are sold out again."*
-- u/MadmaxEndGame, 2026-01-02: *"I checked the website and it's out of stock."*
-- u/secret-bong, 2026-01-17: *"I think they came back this week."*
-- 2026-01-15 post title: *"Cap Lora 1262 module(with grove port) in stock at M5stack"*
-
-([r/M5Stack 1pzazbe](https://old.reddit.com/r/M5Stack/comments/1pzazbe/),
-[r/CardPuter 1pzazuu](https://old.reddit.com/r/CardPuter/comments/1pzazuu/),
-[r/CardPuter 1qdb75x](https://old.reddit.com/r/CardPuter/comments/1qdb75x/)). **[COM]**
-Sample: four independent reports over three weeks. Enough to say launch supply was tight;
-not enough to characterise current supply.
-
-## 3. The hidden cost: antennas and adapters
-
-This is the recurring real-world expense, and it is not in the list price.
-
-| Item | Why | Evidence |
-|---|---|---|
-| 915 MHz antenna | Box contains **one 868 MHz** whip; NA users need 915 | [r/CardPuter 2026-08-22](https://old.reddit.com/r/CardPuter/comments/1vvlcs9/) |
-| SMA ↔ RP-SMA gender/polarity adapter | Connector polarity is disputed (conflict **G1**) | u/malonestar bought a four-way adapter pack; u/goattrybe links a converter — [r/CardPuter 2025-09-19](https://old.reddit.com/r/CardPuter/comments/1nkyy4c/), [r/M5Stack 2026-02-03](https://old.reddit.com/r/M5Stack/comments/1pzazbe/) |
-
-u/malonestar, 2025-09-19: *"Had to wait a few extra days for some sma gender converters /
-adapters. I cannot for the life of me find an SMA female antenna for the US."* **[COM]**
-
-## 4. Regional price friction
-
-u/[OP], [r/M5Stack 2026-01-17](https://old.reddit.com/r/M5Stack/comments/1qfc24p/),
-*"Why would the same cart cost €67 on AliExpress and €44 on the official site"* (18
-comments). Recorded as an owner observation about M5Stack pricing generally, **not**
-normalised for shipping, duty or bundle contents, and **not** verified here. Marketplace
-pricing was a declared exclusion of this pass.
-
-## 5. Alternatives, by intent
-
-| If you want | Consider | Why not the Cap |
-|---|---|---|
-| Meshtastic on a Cardputer-Adv you already own | **U214** | — |
-| Meshtastic on the **original** Cardputer | **[Unit C6L (U202)](../unit-c6l/README.md)**, USD 22.90 | The Cap will not fit. The C6L is a self-contained ESP32-C6 + SX1262 node on a Grove cable |
-| Sub-GHz capture/replay + NFC, not LoRa | **[Cap CC1101 (U219)](../cap-cc1101/README.md)**, USD 18.95 | CC1101 cannot do LoRa (chirp spread spectrum is Semtech-proprietary) |
-| LoRaWAN with a certified stack | **LoRaWAN Unit (U184-\*, STM32WLE5)**, USD 18.95–21.50 | No LoRaWAN stack has been demonstrated on the Cap |
-| Simple point-to-point serial LoRa | **LoRa Unit E220 (U170/U170-433)**, USD 12.95–33.00 | AT-command modem; far less capable but far less work |
-| A dedicated mesh node, not a handheld | Heltec V3/V4, LilyGO T-Deck — repeatedly compared by owners | Different product class; the Cardputer's value is the keyboard |
-
-Owner comparisons worth reading: *"Heltec V4 vs Cardputer Adv (Meshcore)"*
-([r/CardPuter 2026-06-07](https://old.reddit.com/r/CardPuter/comments/1tzlmx9/), 32 upvotes),
-*"Question about heltec v3-4 and cardputer adv"*
-([2026-07-09](https://old.reddit.com/r/CardPuter/comments/1urr84f/)). **[COM]**
-
-## 6. Caveats on everything above
-
-Single-seller, single-region, single-date snapshot. No marketplace, used, refurbished or
-clone observation was gathered — a declared exclusion in
-[`research-log.md`](research-log.md). No clone of this Cap was found, which is unsurprising
-for a nine-month-old accessory to a niche host, but absence of evidence here is weak.
-
----
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| Cap LoRa 1262 for Cardputer Adv (SX1262, ATGM336H) | 2025-12-30 | Default Title | `U214` | **USD 14.50** | ✅ yes |
-| [EOL] LoRa+GPS Cap for Cardputer Adv (SX1262, ATGM336H) | 2025-09-05 | Default Title | `U201` | **USD 14.50** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 14.50, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/cap-lora-1262-for-cardputer-adv-sx1262-atgm336h`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-`U214` is the current part; `U201` is an `[EOL]` predecessor at the **same USD 14.50**.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cap-lora-1262/media.md b/devices/m5stack/cap-lora-1262/media.md
deleted file mode 100644
index 1aabb04..0000000
--- a/devices/m5stack/cap-lora-1262/media.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Media — Cap LoRa-1262 (U214)
-
-Four product photographs retained in [`media/`](media/). All are **M5Stack marketing
-photography** taken from the documentation CDN.
-
-| File | Bytes | SHA-256 | Source URL | Retrieved |
-|---|---:|---|---|---|
-| `U214-Cap-LoRa-1262-main-pictures_01.webp` | 152 404 | `2a7e969baee6af2afd6043b8c1eea45edb3434fe9bd435af8809e432c8e32608` | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-Cap-LoRa-1262-main-pictures_01.webp` | 2026-09-04 |
-| `U214-Cap-LoRa-1262-main-pictures_02.webp` | 58 502 | `6a256af96f7d7682d86a93f093ef5a93325a40e7f035a43d5156a9f4aee7038c` | `…/U214-Cap-LoRa-1262-main-pictures_02.webp` | 2026-09-04 |
-| `U214-Cap-LoRa-1262-main-pictures_03.webp` | 40 210 | `6ce70ea4de0b110d3b806754f10884e2be0190777ce5a8ec0e727a3af6b3ab33` | `…/U214-Cap-LoRa-1262-main-pictures_03.webp` | 2026-09-04 |
-| `U214-Cap-LoRa-1262-main-pictures_05.webp` | 66 312 | `d9d2622fd6cc61ace0b12e312fd9d87e1ea4b1d327af6be9b6ce89b70e2802f1` | `…/U214-Cap-LoRa-1262-main-pictures_05.webp` | 2026-09-04 |
-
-## Provenance and rights
-
-| Field | Value |
-|---|---|
-| Creator / rightsholder | **M5Stack Technology Co., Ltd.** |
-| Source page | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` |
-| Publication date | unknown; the CDN path prefix `1208` corresponds to the U214 product record (store publish 2025-12-30) |
-| Applicable revision | Cap LoRa-1262, U214 |
-| Licence / permission | **unknown.** No licence statement accompanies M5Stack product imagery. Site footer asserts *"Copyright © M5Stack Technology Co., Ltd. All rights reserved."* |
-| Redistribution status | **unknown** |
-| Disposition | **repository, unstaged** pending a user decision |
-| Modifications | **none.** Downloaded verbatim; no crop, rotation, annotation or watermark removal |
-
-## Captions and alt text
-
-| File | Caption | Alt text |
-|---|---|---|
-| `…_01.webp` | Hero shot: Cap LoRa-1262 fitted to a Cardputer-Adv with the rubber-duck antenna screwed into the board-edge connector. | Black expansion board attached to the underside of a small keyboard computer, with a stubby black whip antenna projecting from one end. |
-| `…_02.webp` | Board detail showing the shielded LoRa module can and the GNSS ceramic patch. | Close view of a small PCB with a metal shielding can and a square ceramic block. |
-| `…_03.webp` | Board detail / connector face. | Close view of the expansion board's edge showing the antenna connector. |
-| `…_05.webp` | Assembly or in-use view. | Expansion board shown alongside or attached to the host device. |
-
-> ⚠ **Captions for `_02`, `_03` and `_05` are descriptions of what the frames are expected
-> to show given their position in M5Stack's standard 11-image product set.** The images were
-> downloaded and hashed but **not visually inspected** by this pass. They should be viewed
-> and the captions corrected before being relied on — in particular, `_02` is the most
-> likely candidate for a close-up that would **settle conflict G1 (RP-SMA vs SMA)** by
-> showing whether the connector's centre contact is a socket or a pin.
-
-## Not retrieved
-
-- Seven further frames (`_04`, `_06` … `_11`) exist at the same CDN prefix.
-- `U214-weight.jpg`, `U214-Cap-LoRa-1262-EN.mp4` (product video), and the schematic page
-  renders `…_page_01.png` / `…_page_02.png`.
-- **No teardown, PCB-bare or under-shield photograph was located anywhere** — which is why
-  gaps **G3** (`FM8625H`) and **G7** (module internals) remain open.
diff --git a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_01.webp b/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_01.webp
deleted file mode 100644
index 5b33a11..0000000
Binary files a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_01.webp and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_02.webp b/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_02.webp
deleted file mode 100644
index 7c8587f..0000000
Binary files a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_02.webp and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_03.webp b/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_03.webp
deleted file mode 100644
index b850d21..0000000
Binary files a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_03.webp and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_05.webp b/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_05.webp
deleted file mode 100644
index 9e589cb..0000000
Binary files a/devices/m5stack/cap-lora-1262/media/U214-Cap-LoRa-1262-main-pictures_05.webp and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/media/manifest-schematic-crops.json b/devices/m5stack/cap-lora-1262/media/manifest-schematic-crops.json
deleted file mode 100644
index a7ce472..0000000
--- a/devices/m5stack/cap-lora-1262/media/manifest-schematic-crops.json
+++ /dev/null
@@ -1,43 +0,0 @@
-{
-  "$schema-note": "Image provenance manifest for images DERIVED from retained schematic PDFs by local rasterisation. Kept separate from media/manifest.json so that no pre-existing file is modified; an index owner may merge them.",
-  "device": "m5stack/cap-lora-1262",
-  "generated": "2026-09-07",
-  "generator": "2026-09-07 schematic net-tracing pass; poppler 26.06.0 + ImageMagick",
-  "global_notes": [
-    "These are NOT photographs and NOT vendor-published images. Each is a crop of a page the vendor published as a vector PDF, rasterised locally at 300 dpi.",
-    "pdfimages could not be used: pdfimages -list reports ZERO embedded rasters in every source PDF here. The drawings are vector, so pdftoppm plus a crop is the only route. This is recorded because reaching for pdfimages is the obvious wrong first move.",
-    "Copyright in the underlying drawing remains with the vendor named in creator_rightsholder. Licence is UNKNOWN: no licence statement appears in any of the source PDFs. Redistribution status unknown; disposition repository, unstaged pending user review.",
-    "Every image is reproducible byte-for-byte from the retained artifact using the recorded generation_command, so none of them is uniquely held here.",
-    "Each image exists because it settles a specific documented question; see why_retained."
-  ],
-  "images": [
-    {
-      "local_path": "media/schematic-P1-cap-bus-14pin.png",
-      "filename": "schematic-P1-cap-bus-14pin.png",
-      "sha256": "99e88766600bdf228f8b7fbdf843393f81c7f65cad03023a07d67e6270b1ee40",
-      "bytes": 66206,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export; 1 page; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 900x300+2350+1865 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "900x300+2350+1865",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "U214 Cap LoRa-1262 v1.1",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: the Cap-Bus connector P1, HDR-SMD_14P-P2.54",
-      "alt_text": "Schematic detail of a fourteen-pin connector symbol P1 captioned HDR-SMD_14P-P2.54. Its printed pin names are RESET, INT, BUSY, SCK, MOSI, MISO, CS on the left column (pins 8 to 14) and 5VIN, GND, 5VOUT, SDA, SCL, GPS-RX, GPS-TX on the right (pins 7 down to 1). Each wire carries two dark-red net labels: a functional alias such as RST, IRQ, BUSY, SCK, MOSI, MISO, NSS, and a host-GPIO alias such as G3, G4, G6, G40, G14, G39, G5; on the right, GO with SDA and GI with SCL.",
-      "why_retained": "Establishes the Cap-Bus connector part and pinout, and shows that each net carries two labels, which the text layer alone cannot distinguish from an annotation. Also pairs GI with SCL and GO with SDA, corroborating the Cardputer finding independently."
-    }
-  ]
-}
diff --git a/devices/m5stack/cap-lora-1262/media/schematic-P1-cap-bus-14pin.png b/devices/m5stack/cap-lora-1262/media/schematic-P1-cap-bus-14pin.png
deleted file mode 100644
index 0e440d5..0000000
Binary files a/devices/m5stack/cap-lora-1262/media/schematic-P1-cap-bus-14pin.png and /dev/null differ
diff --git a/devices/m5stack/cap-lora-1262/pinouts-and-buses.md b/devices/m5stack/cap-lora-1262/pinouts-and-buses.md
deleted file mode 100644
index 2472c9c..0000000
--- a/devices/m5stack/cap-lora-1262/pinouts-and-buses.md
+++ /dev/null
@@ -1,321 +0,0 @@
-# Pinouts and buses — Cap LoRa-1262 (U214)
-
-Snapshot 2026-09-04. Schematic **V1.1 / 2025-10-29**. Nothing measured on hardware.
-
----
-
-## 1. The Cap-Bus, and its two incompatible numbering conventions
-
-The connector is a **2 × 7, 2.54 mm header** — `P1`, footprint `HDR-SMD_14P-P2.54` on
-the Cap; **EXT 2.54-14P** on the Cardputer-Adv. **[SCH]**, **[DOC]**
-
-**M5Stack numbers the same connector two different ways in two different documents.**
-This is the single most confusing thing about the Cap-Bus and it has to be stated plainly:
-
-| Document | Convention |
-|---|---|
-| Cap product pages (`Cap_LoRa-1262`, `Cap_CC1101`, `Cap_LoRa868`) | **LEFT column = 1…7 top-to-bottom, RIGHT column = 14…8 top-to-bottom** |
-| Cardputer Mesh Kit page ("Cardputer-Adv EXT 2.54-14P") | **odd 1,3,5,…13 down the left, even 2,4,…14 down the right** — normal 2×N dual-row numbering |
-
-They describe the same 14 contacts. The table below is keyed by the **Cap page numbering**,
-because that is what is silkscreened in the Cap documentation, and gives the host GPIO
-alongside — the host GPIO is the unambiguous identity.
-
-| Cap pin | Cap net | Host GPIO (Cardputer-Adv) | Direction (Cap view) | Function |
-|---:|---|---|---|---|
-| 1 | `GPS_TX` | **G15** | O → host | GNSS module TX → **host RX** |
-| 2 | `GPS_RX` | **G13** | I ← host | GNSS module RX ← **host TX** |
-| 3 | `SCL` | **G9** | I/O | I²C clock (shared with host bus) |
-| 4 | `SDA` | **G8** | I/O | I²C data (shared with host bus) |
-| 5 | `5V_OUT` | — | P | 5 V from host |
-| 6 | `GND` | — | P | Ground |
-| 7 | `5V_IN` | — | P | 5 V into host |
-| 8 | `LoRa_RST` | **G3** | I | SX1262 `NRST` |
-| 9 | `LoRa_IRQ` | **G4** | O | SX1262 `DIO1` |
-| 10 | `LoRa_BUSY` | **G6** | O | SX1262 `BUSY` |
-| 11 | `LoRa_SCK` | **G40** | I | SPI clock |
-| 12 | `LoRa_MOSI` | **G14** | I | SPI MOSI |
-| 13 | `LoRa_MISO` | **G39** | O | SPI MISO |
-| 14 | `LoRa_NSS` | **G5** | I | SPI chip select |
-
-Every row is confirmed by **two independent primary sources**: the schematic's `P1` symbol
-(which annotates each pin with both the Cap net name *and* the host GPIO) and M5Stack's
-published pin-map graphic. **[SCH]** + **[DOC]**
-
-### 1.1 ⚠ The GNSS UART direction is documented inconsistently — here is the resolution
-
-The Cardputer Mesh Kit page labels EXT pin 12 (`G13`) **`UART_RX`** and pin 14 (`G15`)
-**`UART_TX`**. Taken at face value that means the host receives on G13. **That reading is
-wrong**, and three independent sources agree against it:
-
-| Source | Says |
-|---|---|
-| Cap LoRa-1262 pin-map graphic **[DOC]** | `G13 → GPS-RX`, `G15 → GPS-TX` |
-| Schematic `P1` **[SCH]** | pin 1 `GPS-TX` ← `G15`; pin 2 `GPS-RX` ← `G13` |
-| M5Stack's own Arduino example **[SRC]** | `static const int RXPin = 15, TXPin = 13;` then `MultipleSatellite gps(Serial1, 115200, SERIAL_8N1, RXPin, TXPin)` |
-| Meshtastic upstream `variant.h` **[SRC]** | `#define GPS_RX_PIN 15` / `#define GPS_TX_PIN 13` |
-
-**Resolution: `G15` is the host's *receive* pin (it is fed by the GNSS module's TX);
-`G13` is the host's *transmit* pin.** The `UART_RX` / `UART_TX` labels on the Mesh Kit
-page are named from the *peripheral's* perspective, or are simply mislabelled.
-
-This is not academic. A user on 2026-08-28 reported the GNSS finding zero satellites
-across several firmwares and fixed it by *"setting manually the gpio rx and tx pins"* in
-Meshtastic — [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1w0gv7y/). **[COM]**
-
-### 1.2 An extraction artifact you will hit if you re-parse the schematic
-
-In the text layer of `U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf`, the GPIO labels for the
-two I²C pins extract as **`GO`** and **`GI`**, never as `G8`/`G9` — there is no `G8` or `G9`
-token anywhere in the file. The same substitution appears in the Cap CC1101 schematic.
-
-The correct values are `G8` = SDA and `G9` = SCL, established independently by the vendor
-pin-map graphic, the Mesh Kit EXT table, and M5Stack's Arduino example which opens
-`m5::In_I2C.begin(I2C_NUM_0, 8, 9)`. **The `GO`/`GI` strings are an extraction artifact of
-this PDF, not a hardware fact.** Recorded so the next agent does not "discover" a
-nonexistent net. (Compare the PaperMono schematic's separate artifact where `_` renders
-as `0` — different bug, same class of trap.)
-
----
-
-## 2. On-board nets
-
-```
-                     ┌──────────── Cap LoRa-1262 (U214) ──────────────┐
- 5V_IN/5V_OUT ──▶ U3 JW5712 buck ──▶ VDD_3V3 (0–0.6 A) ──┬──────────┐ │
- (P1.5 / P1.7)      ENB ◀── R1 10k pull-up (always on)   │          │ │
-                                                          │          │ │
- G40 SCK  ─────────────────────────────────┐              │          │ │
- G14 MOSI ─────────────────────────────────┤              ▼          ▼ │
- G39 MISO ◀────────────────────────────────┤   M1 Stamp LoRa-1262 Mini │
- G5  NSS  ─────────────────────────────────┤   (SX1262 inside)         │
- G6  BUSY ◀────────────────────────────────┤    pin 10 SW ◀── U2.P0    │
- G4  IRQ (DIO1) ◀──────────────────────────┤    pin 12 ANT ──▶ E4 SMA  │
- G3  NRST ─────────────────────────────────┘                           │
-                                                                        │
- G8 SDA ──┬──▶ U2 PI4IOE5V6408 @ 0x43 ── P0 ──▶ LoRa antenna switch     │
- G9 SCL ──┤                                                             │
-          └──▶ J2 HY2.0-4P Grove (pass-through, R3 10k pull-up)         │
-                                                                        │
- G15 ◀── GPS_TX ── M2 ATGM336H-6N ── ANT ◀── U1 MAX2659 LNA ◀── J1 patch │
- G13 ──▶ GPS_RX ──┘        VBAT ◀── BT1 backup cell                     │
-                     └──────────────────────────────────────────────────┘
-```
-
-## 3. `M1` — `Stamp LoRa-1262 Mini`, all 13 pins
-
-Read directly from the `M1` symbol. **[SCH]**
-
-| Pin | Name | Direction | Net on this board |
-|---:|---|---|---|
-| 1 | `GND` | P | `GND` |
-| 2 | `NRST` | I | `RST` → P1.8 → host **G3** |
-| 3 | `BUSY` | O | `BUSY` → P1.10 → host **G6** |
-| 4 | `IRQ` | O | `IRQ` → P1.9 → host **G4** (SX1262 `DIO1`) |
-| 5 | `3V3` | P | `VDD_3V3` from `U3` |
-| 6 | `CLK` | I | `SCK` → P1.11 → host **G40** |
-| 7 | `MOSI` | I | `MOSI` → P1.12 → host **G14** |
-| 8 | `MISO` | O | `MISO` → P1.13 → host **G39** |
-| 9 | `NSS` | I | `NSS` → P1.14 → host **G5** |
-| 10 | **`SW`** | I | **RF/antenna switch control** ← `PI4IOE5V6408` **P0** |
-| 11 | **`GND`** | P | RF ground |
-| 12 | **`ANT`** | RF | → `E4` antenna connector |
-| 13 | **`GND`** | P | RF ground |
-
-> ### This resolves an open question in the PaperMono documentation
-> [`components/m5stack/stamp-lora-1262` §2.1](../../../components/m5stack/stamp-lora-1262/README.md)
-> records module pins **11, 12 and 13 as "unlabelled, not proven no-connect"**, because the
-> PaperMono schematic symbol prints no names there. The Cap LoRa-1262 symbol for the same
-> 13-pin module **does** print them: **11 = GND, 12 = ANT, 13 = GND** — a
-> ground-signal-ground coplanar RF launch, exactly what one would expect at a module's
-> antenna edge. Pin 10, which PaperMono calls `SX_ANT_SW`, is simply `SW` here.
->
-> Confidence: **high but not certain**. Both symbols have 13 pins in the same order with
-> the same first-nine names, and both are called `Stamp LoRa-1262 Mini`/`Stamp-LoRa-1262-mini`.
-> What has *not* been done is a photograph of either footprint. Treated as
-> `inferred (strong)`, and recorded in the component record rather than asserted as fact.
-
-## 4. `M2` — `ATGM336H-6N` GNSS module, all 18 pins
-
-**[SCH]**
-
-| Pin | Name | Net |
-|---:|---|---|
-| 1 | `GND` | `GND` |
-| 2 | `TXD1` | `GPS-TX` → P1.1 → host **G15** |
-| 3 | `RXD1` | `GPS-RX` → P1.2 → host **G13** |
-| 4 | `1PPS` | **not routed to the Cap-Bus** — see gap **G5** |
-| 5 | `ON/OFF` | tied off on-board; not host-controllable |
-| 6 | `VBAT` | `BT1` backup cell |
-| 7 | `NC` | — |
-| 8 | `VCC` | `+3.3V` via `FB3` (120 Ω/MB) |
-| 9 | `NRST` | tied off on-board; **not host-controllable** |
-| 10 | `GND` | `GND` |
-| 11 | `ANT` | ← `U1` MAX2659 `RFOUT` |
-| 12 | `GND` | `GND` |
-| 13 | `NC` | — |
-| 14 | `VCC_RF` | `+3.3V` via `FB2` (120 Ω/MB) — feeds the LNA bias |
-| 15 | `NC` | — |
-| 16 | `SDA` | **not routed to the Cap-Bus** |
-| 17 | `SCL` | **not routed to the Cap-Bus** |
-| 18 | `NC` | — |
-
-**Consequence:** the GNSS is a **UART-only device on this board.** Its I²C port, its
-`1PPS` output and its hardware reset are all unavailable to the host. Anything you want
-to do to it — cold/warm/hot start selection, constellation selection, update rate — must
-go over the serial link as CASIC binary or NMEA proprietary sentences. See
-[`features/gnss.md`](features/gnss.md).
-
-## 5. `U1` — MAX2659 GNSS LNA
-
-**[SCH]**
-
-| Pin | Name | Net |
-|---:|---|---|
-| 1, 2 | `GND` | `GND` |
-| 3 | `RFIN` | ← `J1` ceramic patch antenna, via `L1` 6.8 nH |
-| 4 | `VCC` | `+3.3V` |
-| 5 | `SHDN` | tied — **no host shutdown control** |
-| 6 | `RFOUT` | → `M2` pin 11 `ANT`, via `C5` 470 pF |
-
-`C6` 100 nF and `C7` 33 nF decouple the LNA supply.
-
-## 6. `U2` — PI4IOE5V6408 I/O expander
-
-I²C address **0x43** (7-bit), on the host's main I²C bus (`G8`/`G9`). **[SCH]** for the
-part and pinout, **[DOC]** + **[SRC]** for the address.
-
-| Pin | Name | Net |
-|---:|---|---|
-| 1 | `INT` | not routed to the host |
-| 2 | `VDD` | `VDD_3V3` |
-| 3–8 | `P7 … P2` | **unused** on this board |
-| 9 | `ADDR` | strapped → **0x43** |
-| 10 | `RESET` | tied off |
-| 11 | `P1` | **unused** |
-| **12** | **`P0`** | **`SX_ANT_SW`** → `M1` pin 10 |
-| 13 | `SCL` | `SCL` → host **G9** |
-| 14 | `SDA` | `SDA` → host **G8** |
-| 15 | `VDD_Bus` | bus-voltage reference |
-| 16 | `GND` | `GND` |
-
-Depopulated: `R5/NC`, `R6/NC`, `R7/NC` (10 kΩ each), `C13/NC`, `C14/NC` (100 nF each).
-
-**Seven of the eight expander outputs are unused.** If you are designing a derivative
-board, `P1`–`P7` are free I²C-reachable GPIO already on the bus.
-
-## 7. Power
-
-| Rail | Source | Notes |
-|---|---|---|
-| `+5V` | Cap-Bus pins 5/7 from the host | `C1` 1 nF, `C2`–`C4` 22 µF bulk |
-| `VDD_3V3` | `U3` JW5712 buck, `L2` = 2.2 µH `WPN201610U2R2MT` | sheet prints `IOUT: 0~0.6A`; `C15` 22 µF, `C16`/`C17` 100 nF, `C12` 470 µF |
-| Enable | `R1` 10 kΩ pull-up on `ENB` | **no host enable line** — the Cap is live whenever the host provides 5 V. `inferred` from adjacency; the ENB net was not traced end-to-end |
-
-Contrast with the [Cap CC1101](../cap-cc1101/pinouts-and-buses.md), where the *same*
-Cap-Bus pin 8 is `POWER_EN` and gates the whole board's regulator. **The two Caps use pin 8
-for entirely different purposes.** Anything that auto-detects a Cap must not assume pin 8
-semantics.
-
-## 8. Host-side resource cost
-
-Fitting this Cap consumes, on the Cardputer-Adv:
-
-| Resource | Pins | Shared? |
-|---|---|---|
-| SPI (SCK/MOSI/MISO) | G40, G14, G39 | **Yes — shared with the microSD slot** (`SDCARD_CS` = G12). Chip-select arbitration required |
-| SPI chip select | G5 | LoRa only |
-| LoRa control | G3 (RST), G4 (DIO1), G6 (BUSY) | LoRa only |
-| UART1 | G15 (RX), G13 (TX) | GNSS only |
-| I²C | G8, G9 | **Yes — shared with keyboard TCA8418, IMU BMI270, audio ES8311 and the Grove port** |
-
-That is **nine host GPIO plus a share of two buses**. It is exactly why no Cap fits the
-original Cardputer: u/IceSubstantial5572, 2025-09-04 — *"No, not enough gpio pins"*
-([r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1n8d8j2/)). The Cardputer-Adv
-freed them by moving the keyboard from a GPIO matrix onto an **I²C TCA8418** controller
-(u/MrBoomer1951, 2025-09-09, [r/CardPuter](https://old.reddit.com/r/CardPuter/comments/1nch377/)). **[COM]**
-
----
-
-Evidence key as in [`README.md`](README.md). Sources listed in [`sources.md`](sources.md).
-
----
-
-# 2026-09-07 — Cap-Bus pinout confirmed from the schematic
-
-Appended beneath the existing tables; **nothing above is altered.** Full trace with coordinates:
-[`schematic-netlist.md`](schematic-netlist.md). Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-
-## The connector is `HDR-SMD_14P-P2.54` — 14 pins, 2.54 mm, SMD
-
-Each bus net carries **two** labels on the same wire: a host-GPIO alias and a functional alias.
-A 300 dpi render was needed to establish that both are net labels rather than one label plus an
-annotation.
-
-| Pin | Symbol pin name | Host GPIO | Functional alias (U214) | Token |
-|---|---|---|---|---|
-| 1 | `GPS-TX` | `G15` | — | `PIP101` @ 705.00, 506.37 |
-| 2 | `GPS-RX` | `G13` | — | `PIP102` @ 705.00, 498.91 |
-| 3 | `SCL` | `GI` = **GPIO1** | `SCL` | `PIP103` @ 705.00, 491.37 |
-| 4 | `SDA` | `GO` = **GPIO2** | `SDA` | `PIP104` @ 705.00, 484.37 |
-| 5 | `5VOUT` | — | `+5VOUT` | `PIP105` @ 705.00, 477.37 |
-| 6 | `GND` | — | `GND` | `PIP106` @ 705.00, 470.37 |
-| 7 | `5VIN` | — | `+5VIN` | `PIP107` @ 705.00, 462.91 |
-| 8 | `RESET` | `G3` | **`RST`** → SX1262 `NRST` | `PIP108` @ 633.00, 462.91 |
-| 9 | `INT` | `G4` | `IRQ` | `PIP109` @ 633.00, 470.37 |
-| 10 | `BUSY` | `G6` | `BUSY` | `PIP1010` @ 633.00, 477.37 |
-| 11 | `SCK` | `G40` | `SCK` | `PIP1011` @ 633.00, 484.37 |
-| 12 | `MOSI` | `G14` | `MOSI` | `PIP1012` @ 633.00, 491.37 |
-| 13 | `MISO` | `G39` | `MISO` | `PIP1013` @ 633.00, 498.91 |
-| 14 | `CS` | `G5` | `NSS` | `PIP1014` @ 633.00, 506.37 |
-
-`GI` = GPIO1 and `GO` = GPIO2 is fixed by the Cardputer ADV sheet, where the same two net names
-land on module pins printed `G1` and `G2`. **Here the sheet corroborates it directly**: pin 3's
-symbol name is `SCL` and it carries `GI`; pin 4's is `SDA` and it carries `GO`. That matches
-M5Unified's `EX SCL = GPIO_NUM_1`, `EX SDA = GPIO_NUM_2`.
-
-## The reported "pin 8 conflict" with the Cap CC1101 — **explained, not a bus conflict**
-
-The bus itself is **identical** on `U214` and `U219`: same connector part, same pin numbering,
-same symbol pin names, same host-GPIO aliases. What differs is the *functional* alias, because
-each daughterboard defines what it does with the host line:
-
-| Pin | Host GPIO | U214 Cap LoRa-1262 | U219 Cap CC1101 |
-|---|---|---|---|
-| **8** | **`G3`** | **`RST`** — SX1262 `NRST` (`M1` pin 2) | **`POWER_EN`** — enables the board's own `JW5712` buck |
-| 9 | `G4` | `IRQ` | `NFC_IRQ` |
-| 10 | `G6` | `BUSY` | `NFC_CS` |
-| 11 | `G40` | `SCK` | `SPI_SCLK` |
-| 12 | `G14` | `MOSI` | `SPI_MOSI` |
-| 13 | `G39` | `MISO` | `SPI_MISO` |
-| 14 | `G5` | `NSS` | `CC1101_CS` |
-| 1 | `G15` | (GNSS TX, `M2` `GP-02`) | `CC1101_G0` |
-| 2 | `G13` | (GNSS RX, `M2` `GP-02`) | `CC1101_RF_SW0` |
-
-**Firmware consequence:** driving `G3` low on a Cap CC1101 **removes power from the radio**;
-on a Cap LoRa-1262 it merely asserts the radio's reset. Code must not be ported between the two
-boards without changing the meaning of that pin.
-
-## On-board power — `U3` is a `JW5712`, permanently enabled
-
-Value string `JW5712` @ (140, 186.3); annotation `IOUT: 0~0.6A` @ (155–175, 92.9).
-
-| Ball | Name | Net |
-|---|---|---|
-| `A1` | `SW` | `L2` `WPN201610U2R2MT` 2.2 µH → `VDD_3V3` |
-| `A2` | `VIN` | `+5V` / `+5VOUT` |
-| `B1` | `EN` | **`R1` 10 kΩ pull-up to `+5V` — no host control** |
-| `B2` | `GND` | `GND` |
-| `C1`/`D1`/`D2` | `VSEL1`/`VSEL2`/`VSEL3` | output-voltage straps |
-| `C2` | `VOS` | `VDD_3V3` remote sense |
-
-See [`components/joulwatt/jw5712`](../../../components/joulwatt/jw5712/README.md).
-
-## Other parts on the sheet
-
-`U1` `MAX2659` GNSS LNA (`L1` 6.8 nH ±5 %, `C5` 470 pF, `J1` `ANT181804`) ·
-`U2` `PI4IOE5V6408ZTAEX` I²C GPIO expander (`P0`…`P7`, `ADDR` via `R7/NC` 10 kΩ) ·
-`M1` `Stamp LoRa-1262 Mini` (13 pins; `NRST`, `BUSY`, `IRQ`, `3V3`, `CLK`, `MOSI`, `MISO`, `NSS`,
-`ANT`) · `M2` `GP-02` GNSS module · `E4` `SMA-KE` LoRa antenna · `J2` `GROVE 4P` ·
-`BT1` battery with `FB3` 120 Ω/MB.
diff --git a/devices/m5stack/cap-lora-1262/projects-and-community.md b/devices/m5stack/cap-lora-1262/projects-and-community.md
deleted file mode 100644
index 1f16df7..0000000
--- a/devices/m5stack/cap-lora-1262/projects-and-community.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# Projects and community — Cap LoRa-1262 (U214)
-
-Sample: **217 unique Reddit posts** across r/CardPuter, r/M5Stack, r/meshtastic, r/Lora,
-r/meshcore and adjacent subs, dated **2025-09-04 → 2026-09-04**, plus 13 GitHub repositories.
-Prevalence statements below are scoped to that sample and no wider.
-
-## 1. Firmware projects that use this Cap
-
-| Project | Author | Stars | Last push | What it is |
-|---|---|---|---|---|
-| [`meshtastic/firmware`](https://github.com/meshtastic/firmware) | Meshtastic | — | current | **Upstream official support**, board `m5stack-cardputer-adv` |
-| [`d4rkmen/plai`](https://github.com/d4rkmen/plai) | d4rkmen | **175** | 2026-07-27 | *"Standalone Meshtastic node for CardPuter ADV"* — written because *"the MT firmware is a disaster: on esp32 wifi is unusable … on esp32-s3 same story with bluetooth"* ([2026-02-15](https://old.reddit.com/r/CardPuter/comments/1r4waav/)) |
-| [`anton-vinogradov/meshtastic-adv`](https://github.com/anton-vinogradov/meshtastic-adv) | anton-vinogradov | 24 | 2026-08-30 | *"Keyboard-first Meshtastic client for the M5Stack Cardputer ADV — own Cap LoRa-1262 or any…"*. Full Unicode on 240×135 with no PSRAM; companion mode drives any stock Meshtastic node over BLE |
-| [`RaymiiOrg/MeshCompromise`](https://github.com/RaymiiOrg/MeshCompromise) | RaymiiOrg | 3 | 2026-08-19 | **Meshtastic + MeshCore in one firmware** on Cardputer-Adv |
-| [`TenoTrash/PoisonMesh`](https://github.com/TenoTrash/PoisonMesh) | TenoTrash | 7 | 2026-06-23 | Meshtastic-network pentesting tool for Cardputer-Adv |
-| [`baltamir1978/fantashtic`](https://github.com/baltamir1978/fantashtic) | baltamir1978 | 0 | 2026-08-15 | *"Firmware de mensajeria LoRa privada para M5Stack Cardputer Adv + Cap LoRa-1262"* — private (non-Meshtastic) LoRa messaging |
-| [`yuiseki/m5-cardputer-meshtastic-map`](https://github.com/yuiseki/m5-cardputer-meshtastic-map) | yuiseki | 0 | 2026-08-23 | Meshtastic **plus an offline planet-scale vector map** on one Cardputer-Adv |
-| [`SweetSourFox/meshtastic-meteo`](https://github.com/SweetSourFox/meshtastic-meteo) | SweetSourFox | 1 | 2026-08-17 | Meshtastic 2.7.22 + weather sensors (BME688/SCD41) |
-| [`hansgao0422/Meshtastic-CardputerADV-CN`](https://github.com/hansgao0422/Meshtastic-CardputerADV-CN), [`ce021711/cardputer-adv-meshtastic-cn`](https://github.com/ce021711/cardputer-adv-meshtastic-cn) | — | 8 / 0 | 2026-07/08 | Chinese localisation + IME |
-| [`MrOlim7/Meshtastic-CZ`](https://github.com/MrOlim7/Meshtastic-CZ) | MrOlim7 | 1 | 2026-05-25 | *"Meshtastic for Cardputer **Zero**"* — evidence the Zero path is real |
-| **MeshCore-Cardputer-ADV** | truthfly et al. | — | v1.1.0, 2026-01-27 | Announced across three subs; **104 upvotes / 42 comments** in r/CardPuter, 44/22 in r/meshcore |
-| **Bruce**, **M5Launcher**, **WhisperOS**, **Porkchop** | community | — | — | General-purpose Cardputer firmwares that expose the Cap |
-
-### For the *original* Cardputer, not this Cap
-
-| Project | Note |
-|---|---|
-| [`sigil-03/cardputer-meshtastic-client`](https://github.com/sigil-03/cardputer-meshtastic-client) | *"cursed meshtastic client for the M5 Cardputer"*, 5 stars, last push **2025-02-05** — a BLE **client** for an external node, not an on-board radio |
-| [`reydeargentina/cardtastic`](https://github.com/reydeargentina/cardtastic) | *"simple, fast UI for Meshtastic nodes running on the M5Stack Cardputer v1.1"*, 2026-02-09 |
-| [`jeroavf/Cardkb_emulator`](https://github.com/jeroavf/Cardkb_emulator) | Turns a Cardputer into an I²C CardKB keyboard **for** a Heltec/other Meshtastic node — the honest workaround for a host with no LoRa |
-| **MeshClient** | *"MeshClient Firmware for CardPuter & CardPuter ADV"*, [2025-11-11](https://old.reddit.com/r/CardPuter/comments/1ouceka/); later *"MeshClient supports on MeshCore & Meshtastic"* [2025-12-16](https://old.reddit.com/r/CardPuter/comments/1pogcwg/) |
-
-## 2. Community timeline
-
-| Date | Event |
-|---|---|
-| **2025-09-04** | *"Cardputer adv and lora module info sheet"* (66 pts) — first sighting, sourced from `x.com/M5Stack/status/1963562345785098345`. In the comments: *"Can other versions of Cardputers make use of the Caplora?"* → **"No, not enough gpio pins"** |
-| 2025-09-06 | M5Stack's own Cardputer-Adv announcement (45 pts); *"CardPuter free text to New CardPuter ADV by Meshtastic?"* (91 pts, 16 comments) |
-| **2025-09-08** | *"Cardputer ADV Hacker cap (CC1101 SubGHz & ST25R3916 RFID) expected release"* — an owner emailed M5Stack and was told **"3–4 months, either December or January"**. It actually shipped **2026-08-28**, ~11 months later |
-| 2025-09-09 | *"is it possible to port meshtastic firmware for cardputer adv to cardputer 1.0?"* — answered no: the ADV moved the keyboard to I²C, freeing the GPIO |
-| **2025-09-15** | *"Got my Cardputer ADV and Lora Cap"* — **156 pts**, the U201 arrival wave |
-| 2025-09-19 | *"Cardputer adv up and running with Lora cap on US915"* — first documented US915 use, via SMA adapters |
-| 2025-11-11 → 12-16 | MeshClient firmware releases |
-| **2025-12-30** | **U214 launch**, announced in r/M5Stack (56 pts) and r/CardPuter (40 pts) |
-| 2026-01-13 | **MeshCore-Cardputer-ADV** lands (82/33/44 pts across three subs) |
-| 2026-01-27 | MeshCore v1.1.0 (104 pts, 42 comments) — the single biggest Cardputer-mesh thread in the sample |
-| 2026-02-11/12 | *"I turned my M5Cardputer into a standalone LoRa & GPS Field Tester"* + open-source release |
-| 2026-02-15 | u/thetestbug points at **PR #9540** as the coming official support |
-| **2026-03-11** | Meshtastic **2.7.20** ships the variant |
-| 2026-04-30 | **Cardputer Mesh Kit** launches |
-| **2026-05-23** | Meshtastic **2.7.24** — antenna-switch fix |
-| 2026-07-05 → 08-01 | anton-vinogradov's keyboard-first client (15/54/44 pts across three posts) |
-| 2026-07-18 | *"Case for Cardputer+LoRa Cap (WiP)"* — **139 pts**; released on Printables 2026-07-18 (69 pts). 3D-printed cases are the most-upvoted Cap content in the sample |
-| **2026-08-28** | **Cap CC1101 & NFC** launches (41 pts, 16 comments) |
-
-## 3. What owners actually build
-
-Demonstrated (code or photos exist): Meshtastic/MeshCore nodes; a **standalone LoRa & GPS
-field tester**; **offline vector maps** driven by the Cap's GNSS; a private LoRa messaging
-firmware; mesh pentesting; weather telemetry over mesh; several 3D-printed cases.
-
-Proposed but not demonstrated in the sample: LoRaWAN of any kind; a **LoRa + GPS game**
-([r/CardPuter 2026-07-20](https://old.reddit.com/r/CardPuter/comments/1v1u7ce/), 10 pts —
-ideas only).
-
-## 4. The recurring complaints, in order of frequency in the sample
-
-1. **Antenna band/connector.** 868 whip shipped worldwide; adapters needed. §Market.
-2. **Battery reporting.** Voltage-only, no BMS, unreliable with a Cap fitted
-   ([2026-06-12](https://old.reddit.com/r/CardPuter/comments/1u3qeez/), 9 comments;
-   [2026-08-21 "Problems charging the Cardputer ADV"](https://old.reddit.com/r/CardPuter/comments/1vu5kya/), 17 comments).
-3. **GNSS "not working"** — RX/TX pins, launcher state, or Meshtastic precision settings.
-   Never yet actually a dead receiver in any thread that reached a resolution.
-4. **Meshtastic BLE/Wi-Fi instability on ESP32-S3** — the stated motivation for at least
-   two independent alternative firmwares.
-5. **Only one Cap slot.** *"Cardputer ADV + LoRa cap, only one module…any project ideas?"*
-   ([2026-08-12](https://old.reddit.com/r/CardPuter/comments/1vmd55m/)). The wish is
-   explicit: *"Would love to have a CC1101/GPS/NRF24/RFID/LoRa all in one"* —
-   u/heytheremonkeyboy, [2025-09-08](https://old.reddit.com/r/CardPuter/comments/1nbe134/).
-
-## 5. Evidence discipline
-
-Everything in §2–§4 is **firsthand owner report, demonstrable project, or informed
-interpretation** — none of it is measurement. The counts in §4 are orderings within the
-217-post sample, not population statistics. Where a thread reached a resolution, the
-resolution is quoted rather than the complaint.
diff --git a/devices/m5stack/cap-lora-1262/research-log.md b/devices/m5stack/cap-lora-1262/research-log.md
deleted file mode 100644
index 7236351..0000000
--- a/devices/m5stack/cap-lora-1262/research-log.md
+++ /dev/null
@@ -1,80 +0,0 @@
-# Research log — Cap LoRa-1262 (U214)
-
-Single pass, **2026-09-04**. Agent had no hardware. Search cutoff = the retrieval date.
-
-## Source classes searched
-
-| Class | Searched? | Depth |
-|---|---|---|
-| Manufacturer product pages / docs | ✅ | 10 pages fetched; link sets fully enumerated |
-| Manufacturer store | ✅ | per-product JSON + full catalogue (662 products, 3 pages to exhaustion) |
-| Manufacturer repositories | ✅ | `org:m5stack` searched for `lora`, `cc1101`, `cap`, `1262`; org repo listing walked |
-| Component-manufacturer datasheets | ✅ (via M5Stack mirrors) | Semtech, TI, ST, ZhongKeWei/CASIC |
-| Standards / regulatory databases | ⚠ partial | M5Stack's own certification index only (negative). **No FCC/CE database query was run** — declared exclusion |
-| Framework / SDK docs | ✅ | Meshtastic repo, RadioLib, M5Unit-NFC, TinyGPSPlus |
-| Distributors / mirrors | ❌ | Not searched. AliExpress/Amazon pricing not gathered — declared exclusion |
-| Community forums | ✅ | Reddit (6 query families, 217 unique posts, 12 full comment trees) |
-| M5Stack community forum (`community.m5stack.com`) | ❌ | **Not searched** — declared exclusion |
-| Video | ⚠ | Product video URL captured, **not watched** |
-| Archives (Wayback) | ❌ | Not needed; every live URL returned 200 |
-
-## Query ledger
-
-| Service | Query | Filters | Results | Outcome |
-|---|---|---|---|---|
-| `docs.m5stack.com` | direct slugs `en/cap/Cap_LoRa-1262`, `Cap_CC1101`, `Cap_LoRa868`, `en/core/Cardputer_Mesh_Kit`, `Stamp_C6LoRa`, `Cardputer`, `en/module/lora868` | — | 7 × HTTP 200 | all useful |
-| `docs.m5stack.com` | `en/core/CardputerAdv`, `en/core/CardputerZero`, `en/unit/lora868`, `en/unit/Unit-LoRaWAN868`, `en/arduino/projects/cap/cap_lora1262` | — | **5 × HTTP 404** (4 162 B soft pages) | slugs wrong; recorded so they are not retried |
-| `shop.m5stack.com` | `/products/<handle>.json` × 11 | — | 200 | **release dates** |
-| `shop.m5stack.com` | `/collections/all/products.json?limit=250&page=1..4` | — | 662 products; page 4 empty | full catalogue timeline |
-| GitHub search | `org:m5stack lora`, `org:m5stack cc1101`, `org:m5stack cap`, `org:m5stack 1262` | repositories | 5 / **0** / 1 / **0** | **negative:** no Cap driver repos |
-| GitHub search | `cardputer meshtastic` | repositories | 13 | community firmware catalogue |
-| GitHub search | `cardputer repo:meshtastic/firmware` | code | 9 files | located the variant |
-| GitHub API | `repos/meshtastic/firmware/git/trees/master?recursive=1` | — | not truncated | **negative:** no variant for the original Cardputer; M5Stack variants are `m5stack_core`, `m5stack_coreink`, `m5stack-stamp-c3`, `m5stack_unitc6l`, `m5stack_cardputer_adv`, `m5stack_cores3` |
-| GitHub API | `commits?path=variants/esp32s3/m5stack_cardputer_adv&per_page=20` (+ page 2 empty) | — | 20 commits, exhausted | full change history |
-| GitHub API | `compare/<sha>...<tag>` × 2 | — | ahead 17 / behind 177 | **first containing release** |
-| `old.reddit.com/search.json` | `"Cap LoRa-1262"`, `cardputer lora`, `cardputer meshtastic`, `"Cap CC1101"`, `"Cardputer Mesh Kit"`, `"LoRa868" cardputer` | `sort=new&limit=100&t=all` | 217 unique posts, 2025-09-04 → 2026-09-04 | community dossier |
-| `old.reddit.com` | 12 permalinks `.json?limit=100` | — | 200 each | quoted threads |
-
-## Chronology of what changed the conclusions
-
-1. **First surprise (docs).** The Cap LoRa-1262 page names **`AT6668`** as the GPS chip and
-   `ATGM336H-6N` as the module — the brief said "ATGM336H". Both are right; they are
-   module and chipset. Two component records created accordingly.
-2. **Second surprise (CDN filenames).** The schematic is `…SCH_V1.1_20251029…` — a
-   **2025** design. Prompted the release-date check.
-3. **The correction.** Shopify `published_at` = **2025-12-30**, not 2026-08/09. Confirmed
-   three ways (Shopify, M5Stack's own Reddit announcement of the same date, CDN
-   product-number ordering).
-4. **The real 2026 board.** `Cap CC1101 & NFC` (U219), `published_at` **2026-08-28**, seven
-   days before this snapshot.
-5. **The "older extension" answer.** The full-catalogue dump surfaced
-   **`U201 [EOL] LoRa+GPS Cap for Cardputer Adv`, published 2025-09-05** — the same day as
-   the Cardputer-Adv itself. That is the older Cardputer LoRa extension, and it is for the
-   **Adv**, not the original Cardputer.
-6. **The original Cardputer's real story.** Its docs show only a Grove port; upstream
-   Meshtastic has **no** variant for it; the community answer in 2025-09 was *"not enough
-   GPIO"*. So for the original Cardputer the honest answer is Grove-attached **Units**, not
-   a LoRa "cap".
-7. **A resolved cross-device gap.** The U214 schematic prints names for `Stamp LoRa-1262
-   Mini` pins **11/12/13** (GND/ANT/GND) that the PaperMono schematic leaves blank —
-   answering an open question in the existing component record.
-8. **A resolved cross-device conflict.** Meshtastic's `variant.h` uses **1.8 V** TCXO where
-   M5Stack uses **3.0 V** on the same module family. Recorded rather than picked.
-
-## Dead ends and negative results (kept deliberately)
-
-- No `Cap LoRa-1262` driver library exists from M5Stack.
-- No certification identifier for U214 anywhere in M5Stack's own certification index.
-- No LoRaWAN example, project or configuration for any Cardputer Cap.
-- No RF/current measurement of this board by anyone, vendor or community.
-- `pins:` mode of the local schematic reader misattributes text under a pypdf-derived bbox;
-  documented in [`commands.md`](commands.md) so it is not silently trusted.
-
-## Stopping criterion
-
-Stopped when: every published M5Stack artifact for U214 was either retrieved or explicitly
-listed as *not fetched* in [`sources.md`](sources.md); the upstream Meshtastic history for
-the board was walked to exhaustion; and Reddit queries had stopped returning new
-threads for the product. **Declared exclusions:** `community.m5stack.com`, distributor and
-marketplace pricing, FCC/CE regulatory databases, product video, and the UiFlow2
-MicroPython API page.
diff --git a/devices/m5stack/cap-lora-1262/schematic-netlist.md b/devices/m5stack/cap-lora-1262/schematic-netlist.md
deleted file mode 100644
index 9eb5d53..0000000
--- a/devices/m5stack/cap-lora-1262/schematic-netlist.md
+++ /dev/null
@@ -1,161 +0,0 @@
-# Cap LoRa-1262 (U214) — net list traced from `U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf`
-
-**Traced:** 2026-09-07 · **Method:**
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md)
-· **Tool:** poppler 26.06.0 plus a 300 dpi `pdftoppm` crop.
-
-**New file.** Corrections to existing claims are appended to `pinouts-and-buses.md` and listed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-## 0. Traceability
-
-1 page, `Creator: Altium Designer`, **0 embedded rasters**, 516 words, full `CO`/`PI` coverage.
-**No `NL` tokens on this export** — every label is ordinary visible text, so bindings were made
-geometrically and then verified against a rendered crop.
-
----
-
-## 1. `P1` — the Cap-Bus connector. **`HDR-SMD_14P-P2.54`.**
-
-Fourteen pins, 2.54 mm pitch, SMD. **Each net carries two labels**: a functional alias and a
-host-GPIO alias, both drawn on the same wire. The render was needed to establish that — from the
-text layer alone one of them looks like an annotation.
-
-| Pin | Symbol pin name | Host-GPIO alias | Functional alias | Pin token |
-|---|---|---|---|---|
-| 1 | `GPS-TX` | `G15` | — | `PIP101` @ 705.00, 506.37 |
-| 2 | `GPS-RX` | `G13` | — | `PIP102` @ 705.00, 498.91 |
-| 3 | `SCL` | **`GI`** (= GPIO1) | `SCL` | `PIP103` @ 705.00, 491.37 |
-| 4 | `SDA` | **`GO`** (= GPIO2) | `SDA` | `PIP104` @ 705.00, 484.37 |
-| 5 | `5VOUT` | — | `+5VOUT` | `PIP105` @ 705.00, 477.37 |
-| 6 | `GND` | — | `GND` | `PIP106` @ 705.00, 470.37 |
-| 7 | `5VIN` | — | `+5VIN` | `PIP107` @ 705.00, 462.91 |
-| 8 | `RESET` | `G3` | **`RST`** | `PIP108` @ 633.00, 462.91 |
-| 9 | `INT` | `G4` | `IRQ` | `PIP109` @ 633.00, 470.37 |
-| 10 | `BUSY` | `G6` | `BUSY` | `PIP1010` @ 633.00, 477.37 |
-| 11 | `SCK` | `G40` | `SCK` | `PIP1011` @ 633.00, 484.37 |
-| 12 | `MOSI` | `G14` | `MOSI` | `PIP1012` @ 633.00, 491.37 |
-| 13 | `MISO` | `G39` | `MISO` | `PIP1013` @ 633.00, 498.91 |
-| 14 | `CS` | `G5` | `NSS` | `PIP1014` @ 633.00, 506.37 |
-
-`GI` = GPIO1 and `GO` = GPIO2 is established independently on the Cardputer ADV, where the same
-two net names land on module pins whose printed names are `G1` and `G2` — see
-[`devices/m5stack/cardputer-adv/schematic-netlist.md`](../cardputer-adv/schematic-netlist.md) §2.
-**Here the sheet corroborates it directly**: pin 3's symbol name is `SCL` and carries `GI`;
-pin 4's is `SDA` and carries `GO`. That matches M5Unified's `EX SCL = GPIO_NUM_1`,
-`EX SDA = GPIO_NUM_2` exactly.
-
-## 2. Where pin 8 goes on **this** board
-
-`RST` → `M1` pin 2, whose symbol pin name is `NRST` — the **`SX1262` reset** on the
-`Stamp LoRa-1262 Mini` module (`M1`, 13 pins, value string at 649–696, 164.6).
-
-`M1` pin map as printed:
-
-| `M1` pin | Name | Net |
-|---|---|---|
-| 1 | `GND` | `GND` |
-| 2 | `NRST` | `RST` |
-| 3 | `BUSY` | `BUSY` |
-| 4 | `IRQ` | `IRQ` |
-| 5 | `3V3` | `VDD_3V3` |
-| 6 | `CLK` | `SCK` |
-| 7 | `MOSI` | `MOSI` |
-| 8 | `MISO` | `MISO` |
-| 9 | `NSS` | `NSS` |
-| 10 | `BUSY` | — |
-| 11 | `GND` | `GND` |
-| 12 | `GND` | `GND` |
-| 13 | `ANT` | to `E4` `SMA-KE` |
-
-## 3. `U3` — on-board buck is a **JW5712**, and it is **permanently enabled**
-
-The value string `JW5712` is printed at (140, 186.3), directly below the `U3` symbol, with the
-vendor annotation **`IOUT: 0~0.6A`** at (155–175, 92.9).
-
-| Ball | Name | Net |
-|---|---|---|
-| `A1` | `SW` | `L2` `WPN201610U2R2MT` 2.2 µH → `VDD_3V3` |
-| `A2` | `VIN` | `+5V` / `+5VOUT` |
-| `B1` | `EN` | **`R1` 10 kΩ pull-up to `+5V`** — `PIR102` @ 100, 121.1 · `PIR101` @ 100, 142.4 |
-| `B2` | `GND` | `GND` |
-| `C1` | `VSEL1` | strap |
-| `C2` | `VOS` | `VDD_3V3` (remote sense) |
-| `D1` | `VSEL2` | strap |
-| `D2` | `VSEL3` | strap |
-
-**`EN` is tied high through a resistor to the input rail. There is no host control of this
-converter on U214.** Contrast with the Cap CC1101, where the same ball is driven by the host —
-see §4.
-
-## 4. Cap-Bus is identical on the Cap CC1101; only the *function* of each line differs
-
-`U219-Cap_CC1101_SCH_V0.3_20260528.pdf` p1 uses the same connector (`HDR_14P-P2.54`), the same
-symbol pin names and the **same host-GPIO aliases**. What changes is the functional alias:
-
-| Pin | Symbol name | Host GPIO | U214 alias | U219 alias |
-|---|---|---|---|---|
-| 1 | `GPS-TX` | `G15` | — | `CC1101_G0` |
-| 2 | `GPS-RX` | `G13` | — | `CC1101_RF_SW0` |
-| 3 | `SCL` | `GI` (GPIO1) | `SCL` | `SCL` |
-| 4 | `SDA` | `GO` (GPIO2) | `SDA` | `SDA` |
-| 5–7 | `5VOUT`/`GND`/`5VIN` | — | same | same |
-| **8** | `RESET` | **`G3`** | **`RST`** | **`POWER_EN`** |
-| 9 | `INT` | `G4` | `IRQ` | `NFC_IRQ` |
-| 10 | `BUSY` | `G6` | `BUSY` | `NFC_CS` |
-| 11 | `SCK` | `G40` | `SCK` | `SPI_SCLK` |
-| 12 | `MOSI` | `G14` | `MOSI` | `SPI_MOSI` |
-| 13 | `MISO` | `G39` | `MISO` | `SPI_MISO` |
-| 14 | `CS` | `G5` | `NSS` | `CC1101_CS` |
-
-**The reported pin-8 conflict is not a conflict in the bus.** The connector part, the pin
-number, the symbol pin name (`RESET`) and the host GPIO (`G3`) are identical on both boards. The
-two documents disagree only about what each daughterboard *does* with that host line:
-
-- **U214** routes `G3` to the SX1262's `NRST`.
-- **U219** routes `G3` to `R1` 100 kΩ and to its own `U1` `JW5712` `EN` ball — the net is named
-  `POWER_EN` (@ 146.12, 258.46 and 535.08, 258.46), and it **switches the CC1101 board's own
-  3.3 V converter on and off.**
-
-So `G3` is a per-board control line whose meaning the daughterboard defines, and the bus pinout
-itself is stable. That is a materially different — and more useful — statement than "the
-documents contradict each other".
-
-> ⚠ **Worth flagging for the Cap CC1101 record, not resolved here:** U219's pins 9 and 10 are
-> named `NFC_IRQ` and `NFC_CS`, but no NFC part appears on that board's designator census. These
-> look like net names inherited from a sibling NFC design. They do not affect the bus pinout, but
-> anyone reading the U219 sheet should not go looking for an NFC controller.
-
-## 5. Other parts on U214
-
-| Des | Part | Function |
-|---|---|---|
-| `U1` | `MAX2659` | GNSS LNA — `VCC`, `RFIN`, `SHDN`, `RFOUT`, `GND`; `L1` 6.8 nH ±5 %, `C5` 470 pF, `J1` `ANT181804` |
-| `U2` | `PI4IOE5V6408ZTAEX` | I²C GPIO expander — `SCL`, `SDA`, `INT`, `ADDR`, `RESET`, `P0`…`P7`; `R7/NC` 10 kΩ on `ADDR` |
-| `U3` | `JW5712` | §3 |
-| `M1` | `Stamp LoRa-1262 Mini` | §2 |
-| `M2` | `GP-02` | GNSS module — `TXD1`, `RXD1`, `1PPS`, `ON/OFF`, `VBAT`, `VCC`, `NRST`, `ANT`, `VCC_RF`, `SCL`, `SDA`; `R4` 0 Ω into `G15`/`G13` |
-| `J1` | `ANT181804` | antenna |
-| `J2` | `GROVE 4P` | `SCL`/`SDA`/`5V`/`GND`, `R3` 10 kΩ |
-| `BT1` | `Battery` | with `FB3` 120 Ω/MB, `C8` 22 µF, `C9` 100 nF |
-| `E4` | `SMA-KE` | LoRa antenna |
-
-The `M2` `GP-02` GNSS module explains why bus pins 1 and 2 are named `GPS-TX`/`GPS-RX`: on
-**this** board they genuinely are the GNSS UART. On the CC1101 board the same two lines are
-re-used for `CC1101_G0` and `CC1101_RF_SW0`.
-
----
-
-## Reproducing
-
-```bash
-nix-shell -p poppler-utils --run 'pdftotext -bbox-layout \
-  "devices/m5stack/cap-lora-1262/artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf" /tmp/u214.xhtml'
-cd scratch/schematic-tracing
-python3 netlist.py /tmp/u214.xhtml --des P1
-python3 render.py  /tmp/u214.xhtml --x0 560 --x1 842 --y0 400 --y1 560
-# the crop that settled the two-labels-per-net question:
-nix-shell -p poppler-utils imagemagick --run '
-  pdftoppm -r 300 -png <pdf> /tmp/u214 &&
-  magick /tmp/u214-1.png -crop 900x300+2350+1865 +repage -resize 180% /tmp/u214-p1.png'
-```
diff --git a/devices/m5stack/cap-lora-1262/sources.md b/devices/m5stack/cap-lora-1262/sources.md
deleted file mode 100644
index 1332eef..0000000
--- a/devices/m5stack/cap-lora-1262/sources.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Sources — Cap LoRa-1262 (U214)
-
-All retrieved **2026-09-04** unless stated. Class ∈ {primary, authorized mirror, credible
-mirror, standard, community}.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope / limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| S-1 | Cap LoRa-1262 product documentation | M5Stack | primary | official page | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` | 2026-09-04 | undated page | SKU U214, full specification table, Cap-Bus pin map, host GPIO map, comparison vs Cap LoRa868, antenna warning | Undated; contradicts its own store copy on connector type | `scratch/m5stack-lora-expansions/docs-html/Cap_LoRa-1262.html` |
-| S-2 | Cap LoRa-1262 store listing (Shopify JSON) | M5Stack | primary | store listing | `https://shop.m5stack.com/products/cap-lora-1262-for-cardputer-adv-sx1262-atgm336h.json` | 2026-09-04 | **published_at 2025-12-30T09:27:06+08:00**, created 2025-12-25 | **The release date.** Product id 8988582248705, variant 47023567274241, SKU U214, USD 14.50 | Machine-readable; `updated_at` reflects any later edit | `scratch/…/shop/cap-lora-1262-….json` |
-| S-3 | Cap LoRa-1262 schematic | M5Stack | primary | schematic PDF | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-sche-Cap-LoRa1262_SCH_V1.1_20251029_2025_11_07_22_53_19.pdf` | 2026-09-04 | **V1.1, 2025-10-29** (uploaded 2025-11-07) | Complete designator census, `M1`/`M2`/`U1`/`U2`/`U3`/`P1`/`J1`/`J2`/`E4` identity and pinouts, all component values | 1 sheet; text-layer extraction only, not rendered | [`artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf`](artifacts/schematic/U214-Cap-LoRa1262_SCH_V1.1_20251029.pdf) — 155 866 B, `sha256 dbc5266d7015cf2e71f2a7ebe13fd88732bf260febced1659f42712fcd94ac8c` |
-| S-4 | Stamp LoRa-1262 Mini schematic | M5Stack | primary | schematic PDF | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/NEW-1262-SCH_A1-Lora_2025_08_27_10_58_52.pdf` | 2026-09-04 | rev **A1**, 2025-08-27 | The module itself — **filed under the component** | Not yet decoded in depth | [`components/m5stack/stamp-lora-1262/artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf`](../../../components/m5stack/stamp-lora-1262/artifacts/Stamp-LoRa-1262-Mini_SCH_A1_20250827.pdf) — 184 442 B, `sha256 6ec29a9240fc8dc41fbe699e74a9f645b9753d7932efc1de28b049fe58e8f03b` |
-| S-5 | Cap LoRa-1262 model-size drawing | M5Stack | primary | mechanical PDF | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-00-cap1262-model-size.pdf` | 2026-09-04 | undated | Outline dimensions | Not transcribed | [`artifacts/mechanical/U214-cap1262-model-size.pdf`](artifacts/mechanical/U214-cap1262-model-size.pdf) — 90 950 B, `sha256 54f765a2f74bf922d65c9c6b38e7354e008a7ff4c7a96426c4d02259b6c3cb8e` |
-| S-6 | Arduino guide for Cap LoRa868 / Cap LoRa-1262 | M5Stack | primary | tutorial | `https://docs.m5stack.com/en/arduino/projects/cap/cap_lora868` | 2026-09-04 | undated | **The vendor's exact RadioLib configuration**, the PI4IOE5V6408 init sequence, `0x43`, `In_I2C.begin(I2C_NUM_0, 8, 9)`, `MultipleSatellite` GNSS example with `RXPin=15, TXPin=13` | Serves both Caps; `/cap/cap_lora1262` is a **404** | `scratch/…/docs-html/en_arduino_projects_cap_cap_lora868.txt` |
-| S-7 | Cardputer Mesh Kit product documentation | M5Stack | primary | official page | `https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit` | 2026-09-04 | undated | Cardputer-Adv EXT 2.54-14P pin table, Meshtastic licensing statement, kit BOM | **Its `UART_RX`/`UART_TX` labels are backwards** — see G5 | `scratch/…/docs-html/Cardputer_Mesh_Kit.html` |
-| S-8 | Cap LoRa868 product documentation | M5Stack | primary | official page | `https://docs.m5stack.com/en/cap/Cap_LoRa868` | 2026-09-04 | undated | U201 identity, +20 dBm, state-resolved current figures, no Grove, no RF switch | Predecessor | `scratch/…/docs-html/en_cap_Cap_LoRa868.txt` |
-| S-9 | Cardputer product documentation | M5Stack | primary | official page | `https://docs.m5stack.com/en/core/Cardputer` | 2026-09-04 | undated | **Negative result:** original Cardputer has only HY2.0-4P `PORT.CUSTOM` (G2/G1), no expansion bus | Establishes non-compatibility | `scratch/…/docs-html/en_core_Cardputer.txt` |
-| S-10 | M5Stack full catalogue (Shopify JSON, 662 products) | M5Stack | primary | store listing | `https://shop.m5stack.com/collections/all/products.json?limit=250&page=1..3` | 2026-09-04 | — | The dated family timeline in README §2, including **U201 published 2025-09-05 and now [EOL]** | Page 4 empty | `scratch/…/shop/all{1,2,3}.json` |
-| S-11 | Meshtastic firmware — `variants/esp32s3/m5stack_cardputer_adv/` | Meshtastic project | primary | repository | `https://github.com/meshtastic/firmware/tree/master/variants/esp32s3/m5stack_cardputer_adv` | 2026-09-04 | blobs `778d95f2…` (variant.h), `a38317e5…` (platformio.ini), `12581cde…` (pins_arduino.h) | Authoritative host pin map, `SX126X_DIO3_TCXO_VOLTAGE 1.8`, shared-SPI note, GPS pins | Third-party w.r.t. M5Stack, but *machine-verified* against the hardware by its users | `scratch/…/github/meshtastic/` |
-| S-12 | Meshtastic firmware — `src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp` | Meshtastic project | primary | repository | `https://github.com/meshtastic/firmware/blob/master/src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp` | 2026-09-04 | 2 782 B | The PI4IOE5V6408 register writes and the Cap-detection probe | | `scratch/…/github/meshtastic/variant.cpp` |
-| S-13 | Meshtastic PR #9540 "Cardputer Kit" | caveman99 / Meshtastic | primary | repository | `https://github.com/meshtastic/firmware/pull/9540` | 2026-09-04 | opened 2026-02-05, **merged 2026-03-06T11:34:41Z**, merge commit `969aefa551d645e6110be11f330774e15ad9c87d` | When upstream support landed | PR body is one line ("BMI270 WIP") | — |
-| S-14 | Meshtastic release `v2.7.20.6658ec2` + device index | Meshtastic project | primary | release | `https://github.com/meshtastic/firmware/releases/tag/v2.7.20.6658ec2` | 2026-09-04 | published 2026-03-11T11:43:26Z | **First release containing the variant**; index lists `m5stack-cardputer-adv` | Prerelease flag set | `scratch/…/github/meshtastic/firmware-2.7.20.6658ec2.json` |
-| S-15 | Meshtastic `mesh.pb.h` hardware-model enum | Meshtastic project | primary | repository | `https://github.com/meshtastic/firmware/blob/master/src/mesh/generated/meshtastic/mesh.pb.h` | 2026-09-04 | — | `M5STACK_CARDPUTER_ADV = 112`, `M5STACK_C6L = 111` | Generated file | — |
-| S-16 | RadioLib | jgromes | primary | repository | `https://github.com/jgromes/RadioLib` | 2026-09-04 | release **7.7.1** 2026-05-31; head `187ef24791c3d844939b2be13a68bd890bd04e4c` 2026-08-22 | The SX1262 and CC1101 driver the vendor links to; **licence MIT** | Licence read from repository metadata, not from the LICENSE file text | — |
-| S-17 | `m5stack/TinyGPSPlus` | M5Stack fork of Mikal Hart | primary | repository | `https://github.com/m5stack/TinyGPSPlus` | 2026-09-04 | head `254a10041ac38d17d98dab24c0ae4d2a8d19a677`, 2025-01-02 | The `MultipleSatellite` GNSS class M5Stack requires | **No LICENSE file detected**; upstream is LGPL-2.1. Flagged, unresolved | — |
-| S-18 | SX1261/2 datasheet V2.2 | Semtech, mirrored by M5Stack | authorized mirror | datasheet | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf` | already held | V2.2 | Radio silicon | **Already in the repository** — not fetched again | [`components/semtech/sx1262/artifacts/`](../../../components/semtech/sx1262/README.md) |
-| S-19 | ATGM336H-6N datasheet | ZhongKeWei, mirrored by M5Stack | authorized mirror | datasheet | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/unit/Unit-GPS%20v1.1/ATGM336H-6N.pdf` | 2026-09-04 | undated | GNSS module | Served from M5Stack's *Unit GPS v1.1* path, not a U214 path | [`components/zhongkewei/atgm336h-6n/artifacts/`](../../../components/zhongkewei/atgm336h-6n/README.md) — 752 259 B, `sha256 7b1c10193709d7600e0234445a1c15603bf3443e14780ecde4818091ec2eda32` |
-| S-20 | CASIC Multi-mode Satellite Navigation Receiver Protocol Specification | CASIC, mirrored by M5Stack | authorized mirror | manual | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1173/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf` | 2026-09-04 | undated | The binary protocol behind `setSatelliteMode()` etc. | **Archived** (2 899 191 B) — placeholder in the component | [`components/zhongkewei/at6668/artifacts/…ARCHIVED.md`](../../../components/zhongkewei/at6668/README.md) |
-| S-21 | "New Arrival Alert! Cap LoRa 1262 Available Now!" | M5Stack (r/M5Stack, r/CardPuter) | community | social post | `https://old.reddit.com/r/M5Stack/comments/1pzazbe/` · `https://old.reddit.com/r/CardPuter/comments/1pzazuu/` | 2026-09-04 | **2025-12-30** | Independent corroboration of the release date; owner reactions on RP-SMA and on U201 vs U214 | Vendor-posted announcement; comments are owner opinion | `scratch/…/reddit/t-lora1262-arrival*.json` |
-| S-22 | "Cardputer adv and lora module info sheet" | u/[various], r/CardPuter | community | social post | `https://old.reddit.com/r/CardPuter/comments/1n8d8j2/` | 2026-09-04 | **2025-09-04** | Earliest Cardputer-Adv/Cap discussion found; *"No, not enough gpio pins"* on original-Cardputer compatibility. Links an M5Stack X/Twitter post `x.com/M5Stack/status/1963562345785098345` | Interpretation, not measurement | `scratch/…/reddit/t-infosheet.json` |
-| S-23 | "Adv & LoRa cap doesn't find gps" | r/CardPuter | community | forum thread | `https://old.reddit.com/r/CardPuter/comments/1w0gv7y/` | 2026-09-04 | 2026-08-28 → 2026-09-02 | Firsthand: GNSS fixed by manually setting Meshtastic RX/TX pins; separately M5Launcher 2.8.0 regression, confirmed by the launcher author | 15 comments, one owner + maintainer | `scratch/…/reddit/t-gps-not-found.json` |
-| S-24 | "cap lora issues" | r/CardPuter | community | forum thread | `https://old.reddit.com/r/CardPuter/comments/1vvlcs9/` | 2026-09-04 | 2026-08-22 | Firsthand: 868 antenna in NA; *"new antenna worked"*. One contrary report | 9 comments | `scratch/…/reddit/t-cap-lora-issues.json` |
-| S-25 | "Cardputer adv up and running with Lora cap on US915" | r/CardPuter | community | forum thread | `https://old.reddit.com/r/CardPuter/comments/1nkyy4c/` | 2026-09-04 | 2025-09-19 | Firsthand U201 use with SMA gender adapters; photo evidence of a standard SMA antenna mating | About U201 | `scratch/…/reddit/t-us915.json` |
-| S-26 | "Help needed: M5Stack Cardputer + LoRa868 Module setup issues" | r/CardPuter, r/meshtastic | community | forum thread | `https://old.reddit.com/r/CardPuter/comments/1r4waav/` | 2026-09-04 | 2026-02-14 | Pre-upstream Meshtastic pain; u/thetestbug points at PR #9540; u/d4rkmen's assessment | Firsthand user + firsthand developer | `scratch/…/reddit/t-cardputer-lora868-module.json` |
-| S-27 | M5Stack GitHub organisation search | GitHub | primary | repository | `https://api.github.com/search/repositories?q=org:m5stack+lora` etc. | 2026-09-04 | — | **Negative result:** no M5Stack driver repo for either Cap | `executed-success` | — |
-| S-28 | `docs.m5stack.com/en/certification` | M5Stack | primary | official page | `https://docs.m5stack.com/en/certification` | inherited from the PaperMono pass, 2026-09-01 | undated | **Negative result:** no entry for `Cap LoRa`, `U214` or `Cardputer` | Not re-fetched in this pass; treat as 2026-09-01 evidence | — |
-
-## Not fetched, known to exist
-
-| What | URL | Why it matters |
-|---|---|---|
-| U201 (Cap LoRa868) schematic | linked from `docs.m5stack.com/en/cap/Cap_LoRa868` | would settle conflict **G4** |
-| U214 structure / 3D files | `github.com/m5stack/M5_Hardware/tree/master/Products/U214_Cap_LoRa-1262/Structures` | enclosure work |
-| UiFlow2 MicroPython API | `https://uiflow-micropython.readthedocs.io/en/latest/cap/lora1262.html` | MicroPython coverage |
-| Product video | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-Cap-LoRa-1262-EN.mp4` | demonstration |
-| M5Stack X/Twitter post of 2025-09-04 | `x.com/M5Stack/status/1963562345785098345` | the Cardputer-Adv + Cap "info sheet" image |
diff --git a/devices/m5stack/cap-lora868/README.md b/devices/m5stack/cap-lora868/README.md
deleted file mode 100644
index 50b7676..0000000
--- a/devices/m5stack/cap-lora868/README.md
+++ /dev/null
@@ -1,154 +0,0 @@
-# M5Stack Cap LoRa868 / "LoRa+GPS Cap for Cardputer Adv" (SKU U201) — **[EOL]**
-
-> **This is the answer to "what was the older LoRa extension for the Cardputer?"**
-> — with the important correction that it is for the **Cardputer-Adv**, not the original
-> Cardputer. It was published **2025-09-05, the same day as the Cardputer-Adv itself**, and
-> is now discontinued, superseded by the [Cap LoRa-1262 (U214)](../cap-lora-1262/README.md)
-> on 2025-12-30.
->
-> Snapshot 2026-09-04. Medium-depth record: the vendor documentation was fully read, the
-> **schematic was located but not fetched**.
-
-## 1. Identity
-
-| Property | Value | Evidence |
-|---|---|---|
-| Documentation name | **Cap LoRa868** | `docs.m5stack.com/en/cap/Cap_LoRa868` |
-| Store name | **[EOL] LoRa+GPS Cap for Cardputer Adv (SX1262, ATGM336H)** | Shopify JSON |
-| SKU | **U201** | both |
-| **Publish date** | **2025-09-05** — same day as **K132-ADV** (Cardputer Adv) | Shopify catalogue JSON |
-| Price | **USD 14.50** (identical to its successor) | Shopify |
-| Status | **[EOL]** | store title prefix |
-| Hosts | Cardputer-Adv / CardputerZero | docs |
-| CDN prefix | `1177` (vs `1208` for U214) | docs link set |
-
-## 2. What it is
-
-Architecturally the same idea as the U214: a 14-pin Cap carrying a `Stamp LoRa-1262`
-(SX1262) plus an `ATGM336H-6N @ AT6668` GNSS with a ceramic antenna, on the Cap-Bus.
-
-Vendor specification, where it differs from or adds to the successor:
-
-| Item | Cap LoRa868 (U201) | Cap LoRa-1262 (U214) |
-|---|---|---|
-| LoRa module | **`Stamp LoRa-1262`** — "legacy version, **standard size**" | `Stamp LoRa-1262` **Mini** |
-| **TX power** | **+20 dBm** | **+22 dBm** |
-| RX sensitivity | −147 dBm | −147 dBm |
-| Frequency | 868 – 923 MHz | 868 – 923 MHz |
-| Shielding can | **No** | **Yes** |
-| RF switch control | **None** | I/O expander `PI4IOE5V6408` P0 @ 0x43 |
-| HY2.0-4P Grove | **No** | **Yes** |
-| Weight | 30.0 g | 22.1 g |
-| Size | 84.0 × 24.0 × 15.2 mm | identical |
-| GNSS | `ATGM336H-6N @ AT6668`, UART 115200 8N1, 50 ch, <1.5 m CEP50, 10 Hz, NMEA 0183 4.1 | identical |
-| Antenna | rubber duck 3 dBi, 108 × 9.3 mm | identical |
-
-The comparison table is M5Stack's own, published on the U214 page.
-
-## 3. ⭐ The state-resolved current figures — U201's documentation is *better* than U214's
-
-This is the only place in the whole Cap family where M5Stack publishes current by named
-operating state, and it is the most useful power data available for this hardware class:
-
-| State | Current @ DC 5 V |
-|---|---|
-| GPS on, LoRa standby | **29.24 mA** |
-| **GPS sleep, LoRa standby** | **3.16 mA** |
-| GPS sleep, LoRa TX max power | **129.72 mA** |
-| GPS on, LoRa TX max power | **155.03 mA** |
-
-Read across: **the GNSS costs ~26 mA and dominates idle draw**; putting it to sleep is worth
-almost an order of magnitude. Transmitting costs ~126 mA on top of whatever the GNSS is
-doing. The successor page replaces all four numbers with a single unconditioned
-*"Power Consumption (Power On): 33.1 mA"* and *"LoRa Operating Current: DC 5 V @ 163.4 mA"*.
-
-⚠ These are **U201** figures at **+20 dBm**. Do not transplant them into a U214 table — the
-successor transmits 2 dB harder and carries a shield can. The *shape* of the tradeoff
-carries; the numbers do not.
-
-## 4. Pin map — identical to the successor, minus the expander
-
-| Cap pin | Net | Cardputer-Adv |
-|---:|---|---|
-| 1 | `GPS_TX` | **G15** |
-| 2 | `GPS_RX` | **G13** |
-| 3 | `SCL` | G9 |
-| 4 | `SDA` | G8 |
-| 5 | `5V_OUT` | — |
-| 6 | `GND` | — |
-| 7 | `5V_IN` | — |
-| 8 | `LoRa_RST` | **G3** |
-| 9 | `LoRa_IRQ` | **G4** |
-| 10 | `LoRa_BUSY` | **G6** |
-| 11 | `LoRa_SCK` | **G40** |
-| 12 | `LoRa_MOSI` | **G14** |
-| 13 | `LoRa_MISO` | **G39** |
-| 14 | `LoRa_NSS` | **G5** |
-
-**Pin-compatible with the U214.** The vendor pin map for U201 shows *only* the LoRa and GPS
-blocks — no `PI4IOE5V6408` row and no `HY2.0-4P` row. That is the documented basis for
-runtime Cap detection by probing I²C `0x43`
-([`../cap-lora-1262/features/io-expander-and-rf-switch.md` §4](../cap-lora-1262/features/io-expander-and-rf-switch.md)).
-
-## 5. ⚠ Conflict: does U201 have an expander after all?
-
-Meshtastic's `variant.cpp` comment reads *"PI4IOE5V6408 on the optional Cap LoRa-1262
-**(and Cap LoRa868)**"*, contradicting M5Stack's comparison table ("RF Switch Control:
-None") and the U201 pin map. The code probes and tolerates absence, so nothing breaks
-either way, but the claim is unresolved. **The U201 schematic is published and would settle
-it; it was not fetched by this pass.**
-
-## 6. Software
-
-Same as the successor: **RadioLib** for the SX1262, **`m5stack/TinyGPSPlus`
-(`MultipleSatellite`)** for the GNSS. M5Stack's Arduino guide is served at
-`docs.m5stack.com/en/arduino/projects/cap/cap_lora868` and **covers both Caps**, detecting
-which is present by probing `0x43`. That is why `/cap/cap_lora1262` is a 404: the older
-board's slug is the canonical one.
-
-Meshtastic runs on it — the variant's `initLoraCap()` degrades gracefully when the expander
-is absent — but this configuration is not separately named or tested upstream.
-
-## 7. Community: the first Cardputer LoRa wave
-
-| Date | Event |
-|---|---|
-| **2025-09-04** | *"Cardputer adv and lora module info sheet"* (66 pts) — the day before launch, from `x.com/M5Stack/status/1963562345785098345`. In the comments: **"Can other versions of Cardputers make use of the Caplora?" → "No, not enough gpio pins."** |
-| 2025-09-06 | *"CardPuter free text to New CardPuter ADV by Meshtastic?"* (91 pts, 16 comments) |
-| **2025-09-15** | *"Got my Cardputer ADV and Lora Cap"* — **156 upvotes**, the arrival wave |
-| **2025-09-19** | *"Cardputer adv up and running with Lora cap on US915"* — first documented US915 use. *"Had to wait a few extra days for some sma gender converters / adapters. I cannot for the life of me find an SMA female antenna for the US."* Includes a photo of a standard SMA antenna mating, and the owner's view that *"I think it is regular SMA female, I don't see any indications anywhere to RP-SMA"* |
-| 2025-11-11 → 12-16 | MeshClient firmware for CardPuter & CardPuter ADV |
-| **2025-12-30** | U214 launches. u/griffog: *"was there an issue with the original cap (the one I have) or does this just have the addition of the I2C port?"* → u/truthfly: *"Just a little upgrade, your is fine 👌"* |
-
-Sources: [r/CardPuter 1n8d8j2](https://old.reddit.com/r/CardPuter/comments/1n8d8j2/),
-[1nhr7na](https://old.reddit.com/r/CardPuter/comments/1nhr7na/),
-[1nkyy4c](https://old.reddit.com/r/CardPuter/comments/1nkyy4c/),
-[1pzazuu](https://old.reddit.com/r/CardPuter/comments/1pzazuu/). **[COM]**
-
-## 8. Gaps
-
-| # | Gap |
-|---|---|
-| L1 | **Schematic located but not fetched** (linked from the docs page as "Cap LoRa868 Schematics PDF"). Would settle §5, and would give the designator census |
-| L2 | Model-size PDF not fetched |
-| L3 | Whether "standard size" `Stamp LoRa-1262` is the *same* 13-pin module as the "Mini" or a physically different part is **not established**. The PaperMono uses a `Stamp-LoRa-1262-mini` — so "Mini" is not unique to the U214 |
-| L4 | No certification identifier, same as the successor |
-| L5 | No RF or power measurement by anyone (the vendor's four-state table is a claim, not a measurement) |
-
-## 9. Sources
-
-| ID | Title | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|
-| U-1 | Cap LoRa868 documentation | primary | `https://docs.m5stack.com/en/cap/Cap_LoRa868` | 2026-09-04 | Identity, +20 dBm, **four-state current table**, pin map, no Grove/no expander |
-| U-2 | M5Stack catalogue JSON | primary | `https://shop.m5stack.com/collections/all/products.json` | 2026-09-04 | **U201 published 2025-09-05, USD 14.50, `[EOL]`** — and K132-ADV on the same date |
-| U-3 | Cap LoRa-1262 documentation (comparison table) | primary | `https://docs.m5stack.com/en/cap/Cap_LoRa-1262` | 2026-09-04 | The five documented differences between U201 and U214 |
-| U-4 | Arduino guide (serves both Caps) | primary | `https://docs.m5stack.com/en/arduino/projects/cap/cap_lora868` | 2026-09-04 | The `0x43` detection that distinguishes them |
-| U-5 | Meshtastic `variant.cpp` | primary | `github.com/meshtastic/firmware` `src/platform/extra_variants/m5stack_cardputer_adv/variant.cpp` | 2026-09-04 | The contested "(and Cap LoRa868)" comment |
-| U-6 | r/CardPuter threads (4) | community | see §7 | 2026-09-04 | Launch chronology, SMA/RP-SMA firsthand reports, the U201→U214 upgrade framing |
-
-## 10. Related
-
-[`../cap-lora-1262/README.md`](../cap-lora-1262/README.md) ·
-[`../cardputer-mesh-kit/README.md`](../cardputer-mesh-kit/README.md) ·
-[`components/m5stack/stamp-lora-1262`](../../../components/m5stack/stamp-lora-1262/README.md) ·
-[`components/semtech/sx1262`](../../../components/semtech/sx1262/README.md)
diff --git a/devices/m5stack/cap-lora868/certification-and-compliance.md b/devices/m5stack/cap-lora868/certification-and-compliance.md
deleted file mode 100644
index c7f163b..0000000
--- a/devices/m5stack/cap-lora868/certification-and-compliance.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Certification and compliance — cap-lora868
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-⚠ **No FCC grant found, and no such product in M5Stack's own store.** See §4. An 868 MHz part would not be sold into the US in any case — 868 MHz is the EU SRD band, not a US ISM band — so FCC absence is expected and uninformative here. The *store* absence is the notable half.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cap-lora868/market-and-pricing.md b/devices/m5stack/cap-lora868/market-and-pricing.md
deleted file mode 100644
index bef363b..0000000
--- a/devices/m5stack/cap-lora868/market-and-pricing.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Market and pricing — cap-lora868
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-**None — the product was not found in the vendor's catalogue.** See the normalisation note below.
-
-### Normalisation and caveats
-
-⚠ **No product matching 'Cap LoRa868' exists in M5Stack's store.** All 13 `868`-matching products were inspected; every one is a LoRaWAN module or unit, **none is a Cardputer Cap**. See the certification record for the matching FCC absence.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cardputer-adv/README.md b/devices/m5stack/cardputer-adv/README.md
deleted file mode 100644
index 89d06b4..0000000
--- a/devices/m5stack/cardputer-adv/README.md
+++ /dev/null
@@ -1,438 +0,0 @@
-# M5Stack Cardputer ADV (K132-Adv)
-
-> **SKU `K132-Adv`** · M5Stack CMS product id **`1178`** · Shopify product `8904041857281`
-> Board revision on the published schematic: **`Sch_M5CardputerAdv_v1.0`, dated 2025-06-20**
-> Status **in production** (the v1.1 it replaces is marked `[EOL]` on M5Stack's own store)
-> Research snapshot **2026-09-04** · vendor library `M5Cardputer` at `f1392858` · `M5Unified` at `8530f537` · `M5GFX` at `d91077b9`
-
-The Cardputer ADV is the third mainboard in M5Stack's card-sized ESP32-S3 computer line and
-the first that is a genuinely different *board*, not just a different plug-in module. It keeps
-the 84 × 54 mm card format, the 56-key keyboard and the 1.14″ 240 × 135 LCD, and changes
-almost everything behind them: an I²C keypad scanner instead of a GPIO matrix, a real audio
-codec instead of a bare I²S amplifier, an IMU, a 3.5 mm jack, a single large battery, and a
-14-pin expansion header — the **CAP bus** — that turns the underside of the device into a
-module socket.
-
-**The single most consequential fact for software:** the ADV frees **seven GPIOs**
-(G3, G4, G5, G6, G7, G13, G15) that on every earlier Cardputer were consumed by the keyboard
-matrix, and spends **two** (G8, G9) to gain an internal I²C bus. Those seven pins are what
-the CAP header is made of.
-
----
-
-## Common tasks / How do I…?
-
-| Question | Answer |
-|---|---|
-| **What changed versus the v1.1?** | [§ Generation-to-generation delta](#generation-to-generation-delta) · [`product-history-and-family.md`](product-history-and-family.md) |
-| **How does the keyboard work?** | [`features/keyboard.md`](features/keyboard.md) — full matrix, TCA8418 config, the remap maths |
-| How do I drive the display? | [`features/display.md`](features/display.md) |
-| How do I play sound / record audio? | [`features/audio.md`](features/audio.md) — **read the shared-codec warning** |
-| How do I use the microSD card? | [`features/microsd.md`](features/microsd.md) |
-| How do I read the IMU? | [`features/imu.md`](features/imu.md) |
-| How do I read battery voltage / charge safely? | [`features/battery-and-power.md`](features/battery-and-power.md) |
-| How do I use Wi-Fi and BLE? | [`features/wifi-and-ble.md`](features/wifi-and-ble.md) |
-| How do I send IR? | [`features/ir.md`](features/ir.md) |
-| How do I use the Grove / PORT.A connector? | [`features/grove-port.md`](features/grove-port.md) |
-| **How do I build my own CAP board?** | [`features/cap-header.md`](features/cap-header.md) — pinout, three conflicting numbering schemes, electrical limits |
-| How do I use USB / act as a HID keyboard? | [`features/usb.md`](features/usb.md) |
-| Is there an RTC? | [`features/rtc.md`](features/rtc.md) — **no**, and what to do instead |
-| What pin is what? | [`pinouts-and-buses.md`](pinouts-and-buses.md) |
-| What fights with what? | [`resources-and-conflicts.md`](resources-and-conflicts.md) |
-| How do I flash it / recover it? | [`development.md`](development.md) · [`factory-firmware.md`](factory-firmware.md) |
-| **Which community firmware works on ADV?** | [`projects-and-community.md`](projects-and-community.md) · [`compatibility-and-status.md`](compatibility-and-status.md) |
-| What does it cost? | [`market-and-pricing.md`](market-and-pricing.md) |
-| Should I buy this or a T-Deck / Tanmatsu? | [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) |
-| What is unresolved or contradictory? | [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-| Where did all this come from? | [`sources.md`](sources.md) · [`research-log.md`](research-log.md) · [`commands.md`](commands.md) |
-
----
-
-## Identity and variants
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | **Cardputer-Adv** (docs) / **M5Stack Cardputer Adv Version (ESP32-S3)** (store) | S1, S9 |
-| SKU | `K132-Adv` | S1 |
-| CMS product id | `1178` | asset URLs on S1 |
-| Shopify id / handle | `8904041857281` / `m5stack-cardputer-adv-version-esp32-s3` | S9 |
-| Schematic revision | `Sch_M5CardputerAdv_v1.0`, file-stamped `2025_06_20_17_19_58` | A1 |
-| Core module | **Stamp-S3A**, schematic `Sch_StampS3_v0.3.3` | S1, A2 |
-| Colour variants | Standard (orange/black); **green back shell** version is exclusive to the Cardputer Mesh Kit (K152) | S4 |
-| Regional variants | None found. No FCC/CE/TELEC identifier published — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) | — |
-
-There is **one** ADV mainboard SKU. `K132-Adv` and `K152` (Mesh Kit) contain the same board;
-the kit adds a Cap LoRa-1262, an antenna, screws and a Meshtastic registration entitlement.
-
----
-
-## Generation-to-generation delta
-
-This is the table the rest of the record exists to justify. Everything in it is from a
-schematic, a rendered schematic sheet, or vendor board-support source — not from marketing
-copy. "v1.x" means v1.0 and v1.1 together, because **their published schematics are the same
-file** (see below).
-
-| Subsystem | Cardputer v1.0 (K132) | Cardputer v1.1 (K132-V11) | **Cardputer ADV (K132-Adv)** | Evidence |
-|---|---|---|---|---|
-| Core module | **StampS3** (`Sch_M5StampS3_v0.2`) | **Stamp-S3A** (`Sch_StampS3_v0.3.3`) | **Stamp-S3A** (same file as v1.1) | S1, S2, S3, A2, A5 |
-| SoC | ESP32-S3FN8 | ESP32-S3FN8 | ESP32-S3FN8 | A2, A5 |
-| Flash / PSRAM | 8 MB in-package / **none** | 8 MB / **none** | 8 MB / **none** — unchanged | A2, A5, S1 |
-| **Keyboard scanner** | **74HC138** 3-to-8 decoder, 8 drive + 7 sense GPIOs | 74HC138, identical | **TCA8418RTWR** I²C keypad scanner @ `0x34`, 3 GPIOs | A1 sheet 2, A3 sheet 2, S1 |
-| Keyboard matrix wiring | 8 × 7, nets `Y0..Y7` via R27–R34 22 Ω | identical | **identical 8 × 7 matrix, identical `Y0..Y7` nets, identical R27–R34 22 Ω** | A1, A3 |
-| GPIOs freed / spent | — | — | **frees G3,G4,G5,G6,G7,G13,G15; spends G8,G9,G11** | M5GFX comment block, A1 |
-| Internal I²C bus | **none** | none | **SDA G8 / SCL G9**, 3.3 kΩ pull-ups R36/R37 | A1 sheet 2, M5Unified `_pin_table_i2c_ex_in` |
-| Display | ST7789V2 1.14″ 240×135 | same | same | S1–S3 |
-| Backlight / RGB LED rail | WS2812 on **always-on `VDD_3V3`** | WS2812 on **`BL_3V3`**, gated by AW35122FDR from `DISP_BL` (G38) | same as v1.1 | A5 vs A2, S2 |
-| Audio out | NS4168 I²S class-D → cavity speaker | same | **ES8311 codec** @ `0x18` + **NS4150B** amp → speaker **and 3.5 mm jack** | A1 sheet 3, S1 |
-| Audio in | **SPM1423** PDM MEMS mic | same | **MSM381A3729H9BP analog MEMS mic** → ES8311 ADC | A1 sheet 3, A3 |
-| 3.5 mm jack | none | none | **yes** (PJ-342), with `HP_DET`; inserting a plug mutes the speaker amp | A1 sheet 3, S1 |
-| IMU | none | none | **BMI270** @ `0x69` | A1 sheet 3, S1 |
-| RTC | none | none | **none** | A1 designator census |
-| Battery | 120 mAh internal + 1400 mAh base | same | **single 1750 mAh** | S1–S3 |
-| Charger / rails | TP4057 + SY7088 boost + SY8089 buck | same | **same parts, same designators** (TP4057 U1, SY7088 U2, SY8089 U4, CN809J U3) | A1, A3 |
-| Grove / PORT.A | HY2.0-4P, G1/G2 | same | same | S1–S3 |
-| **CAP / EXT header** | none | none | **EXT 2.54-14P** (`HDR-SMD_14P-P2.54`, designator P3) | A1 sheet 4, S1 |
-| Lanyard hole | no | no | **yes** | S1 |
-| Product weight | 92.3 g | 90.0 g | 81.0 g | S1–S3 |
-| Thickness | 19.7 mm | 19.7 mm | 19.6 mm | S1–S3 |
-| Sleep current (4.2 V) | 0.26 µA | 0.15 µA | **0.23 µA** (switch OFF) | S1–S3 |
-| Launch (store `published_at`) | — | **2025-03-07** | **2025-09-05** | S9 |
-| Price (2026-09-04) | — | $29.90, **`[EOL]`** | $29.90 | S9 |
-
-### The v1.0-vs-v1.1 finding: the mainboard did not change
-
-`m5stack-doc…/481/Sch_M5Cardputer.pdf` (linked from the v1.0 page) and
-`m5stack-doc…/1127/Sch_M5Cardputer.pdf` (linked from the v1.1 page) are
-**byte-identical**, SHA-256 `6016c1fe6099b9e3f0d0c88f07a3fba1aa44a3da8a7a91dd7040ad0fffa2041e`,
-717 743 B. So are the two base schematics (`29542fe1…`, 24 076 B).
-
-Read together with M5Stack's own comparison table — which lists *only* module-level
-differences (core module, RGB LED logic, antenna, boot-key size, power) — the honest
-statement is: **every published difference between Cardputer v1.0 and v1.1 lives in the
-Stamp module, not on the mainboard.** I cannot rule out an unpublished mainboard change;
-I can say M5Stack published no evidence of one. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-### The Stamp delta, from the two Stamp schematics
-
-| | StampS3 `v0.2` (id 522) | Stamp-S3A `v0.3.3` (id 1150) |
-|---|---|---|
-| 3.3 V rail | module `M2` = **Murata `MUN3CAD01-SC` µPOL** 1 A power module, FB divider R16 100 k / R17 22.1 k | **JoulWatt `JW5712`** buck, 0–0.6 A, `VSEL1/2/3` strapped, `MWTC201608S2R2` 2.2 µH |
-| Load switch | **SGM2578** (U2) | **AW35122FDR** (U2), enabled by `DISP_BL` |
-| **WS2812 supply** | **`VDD_3V3`** — always on | **`BL_3V3`** — the switched backlight rail |
-| Boot button | `SMT_SW_1TS026A` | `SMT_SW_1TS026A` (vendor says the *body* is larger: 4.0×3.0×2.0 mm vs 2.6×1.6×0.55 mm) |
-| Crystal load caps | 12 pF / 10 pF | 12 pF / 12 pF |
-| Solder jumper `JP4` at WS2812 | present | removed |
-
-That single rail change is the whole "RGB LED power supply" story M5Stack tells in prose,
-and it has a consequence the prose only half-states: because the WS2812 now shares the
-PWM-dimmed backlight rail, **dimming the backlight browns out the RGB LED**. M5Stack's v1.1
-page says so plainly; the ADV page does not repeat the warning even though the ADV inherits
-the same Stamp-S3A. See [`features/display.md`](features/display.md).
-
-> **Both regulators are identified, and one of them was contested.** The v0.2's `MUN3CAD01-SC`
-> string looked wrong here — it resembles an ON Semi digital transistor and there is no page
-> render for product id `522` to check it against — but a concurrent session retrieved a
-> datasheet and confirmed it is a **Murata `µPOL` 1 A power module**, which is exactly the
-> 5-terminal EN/VIN/VOUT/FB/GND symbol drawn.
-> Conversely, that session recorded the **Stamp-S3A's `U4` as "part number not established"**;
-> it **is** labelled **`JW5712`** in the Altium comment field directly under the symbol, which a
-> marker-layer-only parse never sees. Both corrections, with evidence, are in
-> [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §C7 and §U1.
-
----
-
-## Key specifications
-
-| Item | Value | Component record |
-|---|---|---|
-| SoC | Xtensa LX7 dual-core @ 240 MHz, 512 KB SRAM, 8 MB in-package flash, **no PSRAM** | [`espressif/esp32-s3fn8`](../../../components/espressif/esp32-s3fn8/README.md) |
-| Core module | Stamp-S3A, 24-pin 1.27 mm castellated DIP | [`m5stack/stamp-s3a`](../../../components/m5stack/stamp-s3a/README.md) |
-| Display | ST7789V2, 1.14″, 240 × 135, 4-wire SPI (3-wire in M5GFX), 40 MHz write | [`sitronix/st7789v2`](../../../components/sitronix/st7789v2/README.md) |
-| Keyboard | 56 keys (4 × 14), 160 gf, scanned by TCA8418RTWR over I²C `0x34` | [`texas-instruments/tca8418`](../../../components/texas-instruments/tca8418/README.md) |
-| Audio codec | ES8311, I²C `0x18`, I²S slave | [`everest-semiconductor/es8311`](../../../components/everest-semiconductor/es8311/README.md) |
-| Speaker amp | NS4150B mono class-D, 8 Ω 1 W, `CTRL` = `AMP_EN` | [`nsiway/ns4150b`](../../../components/nsiway/ns4150b/README.md) |
-| Microphone | MSM381A3729H9BP analog MEMS, SNR 65 dB | [`memsensing/msm381a3729h9bp`](../../../components/memsensing/msm381a3729h9bp/README.md) |
-| Headphone jack | PJ-342 3.5 mm, `HP_DET` via Q4 2N7002T | [`generic/3.5mm-audio-output`](../../../components/generic/3.5mm-audio-output/README.md) |
-| IMU | BMI270 6-axis, I²C `0x69` (SDO pulled high by R43 3.3 kΩ) | [`bosch-sensortec/bmi270`](../../../components/bosch-sensortec/bmi270/README.md) |
-| RGB LED | WS2812 on the Stamp, data G21, supply `BL_3V3` | [`worldsemi/ws2812`](../../../components/worldsemi/ws2812/README.md) |
-| Storage | microSD, 1-bit SPI on the shared SPI bus | [`generic/micro-sd-sdmmc`](../../../components/generic/micro-sd-sdmmc/README.md) |
-| Charger | TP4057 linear, `R_PROG` = 3.3 kΩ | [`generic/tp4057`](../../../components/generic/tp4057/README.md) |
-| 5 V boost | SY7088, FB 75 k / 22 k → ≈ 5.29 V | [`silergy/sy7088`](../../../components/silergy/sy7088/README.md) |
-| 3.3 V buck | SY8089, FB 68 k / 15 k | [`silergy/sy8089`](../../../components/silergy/sy8089/README.md) |
-| Supervisor | CN809J reset generator on `+5VIN` | [`consonance/cn809`](../../../components/consonance/cn809/README.md) |
-| Power path FETs | LP3218DT1G × 3 (Q1, Q2, Q3) | [`unidentified/cardputer/lp3218dt1g`](../../../components/unidentified/cardputer/lp3218dt1g/README.md) |
-| Battery | 1 × 1750 mAh Li-ion, ADC divider on G10 | [`generic/charger-power-path`](../../../components/generic/charger-power-path/README.md) |
-| IR | single emitter on G44, no receiver | — |
-| Expansion | HY2.0-4P Grove (G1/G2) + **EXT 2.54-14P CAP header** | [`features/cap-header.md`](features/cap-header.md) |
-| Size / weight | 84.0 × 54.0 × 19.6 mm, 81.0 g | A4 |
-
-Numbers marked *inferred* — the SY7088 and SY8089 output voltages and the TP4057 charge
-current — come from reading the feedback/programming resistors off the rendered schematic and
-applying the datasheet formula printed **on the sheet itself** (`Vout = 1.2 V × (R1/R2 + 1)`).
-They have not been measured. The charge current works out at roughly 300 mA for
-`R_PROG = 3.3 kΩ`; treat that as an order-of-magnitude statement, not a spec.
-
----
-
-## Architecture and components
-
-One processor, one bus tree. There is no coprocessor, no PMIC, and no I/O expander on the
-mainboard — the TCA8418 is a *keypad* scanner and exposes nothing else.
-
-```
-                                    ESP32-S3FN8 (inside Stamp-S3A)
-                                             │
-   ┌──────────────┬──────────────┬───────────┼───────────┬──────────────┬─────────────┐
-   │              │              │           │           │              │             │
- SPI2/3         I²S1        internal I²C   ADC1      RMT/LEDC        USB-OTG      GPIO0
- G36 SCK       G41 BCK      G8 SDA         G10        G44 IR TX      native       BOOT
- G35 MOSI      G43 LRCK     G9 SCL         batt       G21 WS2812
- G37 LCD CS    G42 DOUT       │            ÷2
- G33 RST       G46 DIN        ├── TCA8418  0x34  keypad   (INT → G11)
- G34 DC        G45 (unused)   ├── ES8311   0x18  codec
-   │                          └── BMI270   0x69  IMU
-   ├── ST7789V2 (FPC1, 8-pin 0.5 mm)                     external I²C (PORT.A)
-   ├── microSD  (CS G12, on SPI G40/G14/G39)             G1 SCL / G2 SDA  ← Grove
-   └── CAP header P3 (SPI G40/G14/G39 + CS G5,
-        RESET G3, INT G4, BUSY G6, UART G13/G15,
-        and the same internal I²C G8/G9)
-```
-
-Two facts fall straight out of that picture and drive most of
-[`resources-and-conflicts.md`](resources-and-conflicts.md):
-
-1. **The microSD and the CAP header share one SPI bus** (G40 SCK, G14 MOSI, G39 MISO) with
-   separate chip selects (G12 and G5). A LoRa transceiver and a filesystem on one bus is
-   workable but needs care around clock speed and long transactions.
-2. **The CAP header carries the *internal* I²C bus**, not the Grove one. Anything you hang on
-   CAP pins 10/11 shares a bus with the keyboard scanner, the audio codec and the IMU, and
-   must not collide with `0x34`, `0x18` or `0x69`.
-
----
-
-## What it is, and visual identification
-
-An 84 × 54 mm slab — the footprint of a credit card, 19.6 mm thick — with a 56-key rubber-dome
-keyboard filling the lower two-thirds and a small landscape LCD above it. The Stamp-S3A module
-is user-removable from the front panel; a ribbon FPC runs from the panel to the display, and
-M5Stack warns explicitly that lifting the module carelessly damages the display connector.
-
-Distinguishing an ADV from a v1.x **without powering it on**:
-
-| Tell | v1.0 / v1.1 | ADV |
-|---|---|---|
-| 3.5 mm jack on the edge | absent | **present** |
-| Lanyard hole | absent | **present** |
-| 14-pin 2.54 mm header on the underside | absent | **present** |
-| Base | separate battery base, held by four M2 screws | single-piece body |
-
-And *with* power: M5GFX prints `[Autodetect] board_M5CardputerADV` versus
-`[Autodetect] board_M5Cardputer`. The mechanism is in [§ Board autodetect](#board-autodetect).
-
-> **No product photograph is retained in this record.** M5Stack's product imagery carries no
-> redistribution licence (see [`vendors/m5stack`](../../../vendors/m5stack/README.md) §8).
-> [`media.md`](media.md) and [`media/manifest.json`](media/manifest.json) record the URLs,
-> provenance and what each image shows.
-
----
-
-## Board autodetect
-
-M5GFX identifies the board *before* any user code runs, and the mechanism is worth
-understanding because it is also a compatibility hazard. From
-[`M5GFX/src/M5GFX.cpp`](https://github.com/m5stack/M5GFX/blob/d91077b9a607b59404e4e4a49f775c792bfae382/src/M5GFX.cpp#L2583-L2624) — the comment block is M5Stack's own:
-
-```c
-/*
-Here, VAMeter/Cardputer/CardputerADV will be automatically recognized.
-The usage of each pin is as follows.
-|    |  VAMeter  | Cardputer  |CardputerADV|
-|:--:+:---------:+:----------:+:----------:|
-| G5 | SYS_SDA   | KEY_MATRIX |  External  |
-| G6 | SYS_SCL   | KEY_MATRIX |  External  |
-| G7 |  NC       | KEY_MATRIX |Internal FPC|
-| G8 | External  |  74HC138   |  SYS_SDA   |
-| G9 | External  |  74HC138   |  SYS_SCL   |
-*/
-```
-
-The probe drives G9, G8, G6, G5 as *input-pulldown* and reads them in that order;
-`gpio::command()` accumulates `result = (result << 1) + res`, so **G9 → bit 3, G8 → bit 2,
-G6 → bit 1, G5 → bit 0**. Then:
-
-* `(result & 0x0C) == 0x0C` — G8 **and** G9 read high against an internal pulldown → **ADV**.
-  On the ADV those are the internal I²C bus, held up by R36/R37 (3.3 kΩ each). On a v1.x they
-  are 74HC138 address lines with no pull-up.
-* `(result & 3) == 3` first triggers a VAMeter probe on G5/G6 for I²C `0x40`/`0x41`.
-
-**Hazard.** The test is "are there pull-ups on G8/G9", nothing more. Fit a v1.x Cardputer
-with anything that pulls G8 and G9 high — an ill-advised Grove hack, a probe clip, a
-mis-wired matrix — and M5GFX will declare it an ADV, install the TCA8418 keyboard reader, and
-the keyboard will simply stop working. Recorded in [`compatibility-and-status.md`](compatibility-and-status.md).
-
----
-
-## Common uses and representative projects
-
-The Cardputer's community is unusually large for a $30 board and skews four ways: **security
-tooling**, **mesh radio**, **music**, and **"tiny OS"** projects. The 2026 pattern is that the
-ADV, not the v1.x, is where new work happens — of the 100 `cardputer` repositories GitHub
-returned on 2026-09-04, the ones created in 2026 overwhelmingly say "ADV" in the title.
-
-Highlights, with full detail and build status in [`projects-and-community.md`](projects-and-community.md):
-
-* **Bruce** (`BruceDevices/firmware`, AGPL-3.0, ★6 642) — the dominant offensive-security
-  firmware. One `m5stack-cardputer` build serves **both** generations, switching at runtime on
-  whether a TCA8418 answers at `0x34`.
-* **Launcher** (`bmorcelli/Launcher`, MIT, ★2 054) — multi-firmware boot menu; ships a
-  dedicated `CardputerADV.md` documenting its TCA8418 port.
-* **Meshtastic** (GPL-3.0, ★8 250) — first-class `m5stack-cardputer-adv` variant. The Mesh Kit
-  is an officially licensed Meshtastic device.
-* **Evil-M5Project / "EvilCardputer"** (★2 570) — Wi-Fi auditing suite; the long-running
-  community favourite on v1.x.
-* **MicroHydra** (GPL-3.0, ★314) — MicroPython app switcher, the main MicroPython route.
-* **Picoware** (GPL-3.0, ★320) — cross-device firmware that explicitly lists Cardputer ADV.
-* Emulators (`geo-tp/Cardputer-Game-Station-Emulators`, `romalik/m5cardputer_doom`,
-  `matteofo/gb_cardputer`), a groovebox/DAW scene (`urtubia/miniacid`, `CHARL3X/GLIDE`,
-  BKLVA Pocket DAW), and a local-LLM experiment (`therezor/cardputer-ai`, "8 M params, Q4").
-
----
-
-## Distinctive strengths
-
-* **A real keyboard on a $30 ESP32.** Nothing else at the price has 56 keys and a screen in a
-  pocketable case.
-* **The keyboard costs almost nothing in GPIO now.** Three pins instead of fifteen, and two of
-  those three are a bus you wanted anyway.
-* **The CAP header is a genuine socket, not a breakout.** SPI + CS + RESET + IRQ + BUSY + UART
-  + I²C + switched 5 V, in the exact shape an SX1262 or a CC1101 wants. M5Stack ships two
-  boards for it and the community has already built at least four more (TFT-2.8, TFT V2,
-  CC1101/NRF24/LoRa combos).
-* **Board autodetect actually works**, so one binary can serve both generations. Bruce proves it.
-* **Audio is a step change.** A codec with a real ADC path, a headphone jack with detection, and
-  an amplifier that mutes itself — versus a PDM mic and a bare class-D on the v1.x.
-
-## Shortcomings and constraints
-
-* **No PSRAM. None. On any Cardputer.** `ESP32-S3FN8` is flash-in-package with no PSRAM die.
-  This is the constraint that shapes every ambitious project on the platform — see the
-  Meshtastic-client author's account of memory-mapping a 2.16 MB Unicode font out of a flash
-  partition because it cannot live in RAM (S15).
-* **No RTC.** Wall-clock time is lost on every power cycle. The CardputerZero has an RX8130CE;
-  the ADV does not.
-* **One SPI bus for microSD *and* the CAP header.**
-* **One codec for speaker *and* microphone**, and the vendor's two enable callbacks disagree
-  about how to configure it — see the driver audit in [`features/audio.md`](features/audio.md).
-  This is a live bug, not a theoretical one.
-* **TCA8418 `RESET` is tied high through R38 and reaches no GPIO.** If the scanner wedges,
-  software cannot reset it; only a power cycle will.
-* **The backlight rail powers the RGB LED**, so you may have PWM dimming or a stable RGB LED,
-  not both.
-* **Charging requires the power switch to be ON** — M5Stack says so on every Cardputer page.
-* **0 – 40 °C operating range**, and a sealed Li-ion cell you cannot swap without opening the case.
-* **No published certification.** See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
----
-
-## Performance summary
-
-See [`performance.md`](performance.md). Briefly: 240 MHz dual LX7, 512 KB SRAM, no PSRAM,
-40 MHz SPI display writes (M5GFX `freq_write = 40000000`), 1 500 000 baud upload in M5Stack's
-own PlatformIO profile. Vendor current figures at 4.2 V: 120.2 mA idle-operating,
-132.3 mA Wi-Fi, 154.6 mA BLE, 0.23 µA with the switch off. Against a 1750 mAh cell that is
-roughly 13–14 h of continuous Wi-Fi operation at the vendor's own numbers — a figure I have
-**not** measured and which ignores display backlight, which is likely to dominate.
-
----
-
-## Pricing and availability
-
-$29.90 at M5Stack's own store on **2026-09-04**, in stock. The Mesh Kit is $48.00, the Cap
-LoRa-1262 $14.50, the Cap CC1101 & NFC $18.95. The v1.1 it replaces is listed at the same
-$29.90 but titled `[EOL] M5Stack Cardputer with M5StampS3 v1.1`.
-Full dated observations, other channels and caveats: [`market-and-pricing.md`](market-and-pricing.md).
-
----
-
-## Competitors, equivalents and clones
-
-Detailed treatment in [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md),
-which compares the ADV against the Cardputer v1.1, the **LilyGO T-Deck**, and the
-[**Nicolai Electronics Tanmatsu**](../../nicolai-electronics/tanmatsu/README.md) already in
-this repository. Short version: the T-Deck trades the ADV's keyboard quality and expansion
-socket for a BlackBerry keyboard, PSRAM and on-board LoRa; the Tanmatsu is a different class
-of machine entirely (ESP32-P4, MIPI DSI, fully open KiCad, ~4× the price) and is the right
-answer when you need the openness or the compute, not when you need $30.
-
-No clones of the Cardputer ADV were found on 2026-09-04. See
-[`market-and-pricing.md`](market-and-pricing.md) for the searches that establish that.
-
----
-
-## Images and teardown/PCB views
-
-[`media.md`](media.md) — 13 vendor product renders, a weight photo, an IMU axis diagram, four
-schematic sheet renders and the crops derived from them, each with source URL, retrieval date,
-rights status and what it demonstrates.
-
----
-
-## Documentation map
-
-| File | Contents |
-|---|---|
-| [`pinouts-and-buses.md`](pinouts-and-buses.md) | Every GPIO, both connectors, three CAP numbering schemes |
-| [`resources-and-conflicts.md`](resources-and-conflicts.md) | SPI/I²C/I²S/timer/DMA contention, realistic combinations |
-| [`features/`](features/README.md) | Twelve task-oriented guides |
-| [`development.md`](development.md) | Arduino, ESP-IDF, PlatformIO, UiFlow2, MicroPython |
-| [`factory-firmware.md`](factory-firmware.md) | UserDemo, partitions, EasyLoader, recovery |
-| [`compatibility-and-status.md`](compatibility-and-status.md) | What works on which revision |
-| [`projects-and-community.md`](projects-and-community.md) | 40+ catalogued projects, forum evidence |
-| [`product-history-and-family.md`](product-history-and-family.md) | Dated timeline, the whole family |
-| [`market-and-pricing.md`](market-and-pricing.md) | Dated prices, channels, availability |
-| [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) | Versus v1.1, T-Deck, Tanmatsu |
-| [`performance.md`](performance.md) | Vendor figures, silicon limits, what is unmeasured |
-| [`coverage.md`](coverage.md) | Feature → evidence → guide → gap matrix |
-| [`gaps-and-conflicts.md`](gaps-and-conflicts.md) | Ten recorded contradictions and unknowns |
-| [`sources.md`](sources.md) | Full source table |
-| [`research-log.md`](research-log.md) | Every query and its disposition |
-| [`commands.md`](commands.md) | Every command, with status labels |
-| [`examples/`](examples/best.md) | Example catalogue and selection |
-| [`acquisition/`](acquisition/README.md) | Machine-readable artifact manifest |
-
-## Artifact layout
-
-```
-artifacts/
-├── schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf   878 155 B  9553f5ee…
-├── mechanical/K132-Adv-cardputer-ADV.pdf                       127 977 B  6c937ca0…
-├── docs/docs-en-core-Cardputer-Adv.html                        147 339 B  f05bbb70…
-├── docs/docs-zh_CN-core-Cardputer-Adv.html                     146 690 B  4a285b02…
-└── source-snapshots/
-    ├── M5Cardputer-f1392858/                     MIT, 33 files, 284 KB
-    └── M5Cardputer-UserDemo-CardputerADV-b549eac0/   MIT, build config only
-```
-
-The Stamp-S3A schematic is **not** duplicated here — it belongs to the module and lives at
-[`components/m5stack/stamp-s3a/artifacts/`](../../../components/m5stack/stamp-s3a/README.md),
-which another session was creating at the time of writing. Chip datasheets likewise file under
-their components, per the skill's placement rule.
-
-## Known conflicts and unresolved identities
-
-Ten are recorded in [`gaps-and-conflicts.md`](gaps-and-conflicts.md). The three that matter most:
-
-1. **The Mesh Kit page's EXT table swaps UART TX and RX.** Three independent sources — the ADV
-   product page, the schematic's own net labels, M5Stack's factory firmware `uart_set_pin()`
-   call, *and* Meshtastic's variant header — agree that **G13 is TX and G15 is RX**. Only the
-   Cardputer Mesh Kit page says otherwise, and it contradicts itself two tables later.
-2. **The CAP header has three different pin numberings in circulation** (product page,
-   schematic, Cap-board side). They describe the same physical connector.
-   [`features/cap-header.md`](features/cap-header.md) reconciles them.
-3. **The StampS3 v0.2 3.3 V regulator is unidentified.**
-
----
-
-*Snapshot 2026-09-04. This is a broad-coverage snapshot of what was publicly retrievable on
-that date, not a claim that nothing else exists.*
diff --git a/devices/m5stack/cardputer-adv/acquisition/README.md b/devices/m5stack/cardputer-adv/acquisition/README.md
deleted file mode 100644
index f9046c0..0000000
--- a/devices/m5stack/cardputer-adv/acquisition/README.md
+++ /dev/null
@@ -1,164 +0,0 @@
-# Cardputer ADV — acquisition
-
-> Snapshot **2026-09-04**. Machine-readable: [`manifest.json`](manifest.json).
-> Every artifact here is an **unauthenticated GET** or a **git clone at a pinned commit**.
-> No login, no API key, no rate limit encountered — so no bespoke downloader was written; the
-> commands below *are* the downloader, in execution order.
-
-## Prerequisites
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-cd "$(git rev-parse --show-toplevel)"/devices/m5stack/cardputer-adv
-mkdir -p artifacts/{schematic,mechanical,docs,source-snapshots}
-```
-
-A browser User-Agent is used throughout for consistency with the rest of this repository, but
-**it was not required** — `docs.m5stack.com` and the two Aliyun OSS buckets served 200 to plain
-`curl` as well.
-
-## 1. Schematic and mechanical drawing
-
-```bash
-curl -fsSL -A "$UA" -o artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf \
-  "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf"
-curl -fsSL -A "$UA" -o artifacts/mechanical/K132-Adv-cardputer-ADV.pdf \
-  "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV.pdf"
-```
-
-Verify:
-
-```bash
-sha256sum -c <<'SUMS'
-9553f5ee22b6e5f29a385388192e42c5ff76f16281b6f7ea9418f7b62a2d48b0  artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf
-6c937ca05e0894e54a3e47abb57e91de1b755dea032fd3f7438ea7a3e34550da  artifacts/mechanical/K132-Adv-cardputer-ADV.pdf
-SUMS
-```
-
-Sizes: 878 155 B and 127 977 B. Both begin `%PDF-1.4`. **Validate by magic bytes, not by
-extension** — this host has no `file`, so:
-
-```bash
-python3 -c "print(open('artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf','rb').read(8))"
-# b'%PDF-1.4'
-```
-
-## 2. Documentation snapshots
-
-```bash
-curl -fsSL -A "$UA" -o artifacts/docs/docs-en-core-Cardputer-Adv.html \
-  "https://docs.m5stack.com/en/core/Cardputer-Adv"
-curl -fsSL -A "$UA" -o artifacts/docs/docs-zh_CN-core-Cardputer-Adv.html \
-  "https://docs.m5stack.com/zh_CN/core/Cardputer-Adv"
-```
-
-`f05bbb70ca0964ebcd465e866bf25302f24cd29ecada5099803c7786c3b54fec` (147 339 B) and
-`4a285b0281f21864e394554161976786ac4846abfd7021f2422a3f4cced2ac61` (146 690 B).
-
-⚠ **These hashes will drift** — the pages are live and M5Stack edits them. If yours differ,
-that is a *finding* (compare the two and record what changed), not a failure. The retrieval date
-is the identity that matters.
-
-## 3. Source snapshots
-
-```bash
-git clone https://github.com/m5stack/M5Cardputer.git /tmp/M5Cardputer
-git -C /tmp/M5Cardputer checkout f1392858b9994c3547120e602a57d3553d16ab01
-rsync -a --exclude='.git' /tmp/M5Cardputer/ artifacts/source-snapshots/M5Cardputer-f1392858/
-
-git clone -b CardputerADV https://github.com/m5stack/M5Cardputer-UserDemo.git /tmp/UserDemo
-git -C /tmp/UserDemo checkout b549eac0a3c65bc108186c276b8fac0a214aaa4e
-mkdir -p artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0
-cp /tmp/UserDemo/{partitions.csv,repos.json,sdkconfig.defaults,dependencies.lock} \
-   artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/
-cp /tmp/UserDemo/main/hal/hal_config.h \
-   artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/
-```
-
-Tree digest for the M5Cardputer snapshot. **Record the recipe with the digest** — and note the
-trap this pass walked into:
-
-```bash
-cd artifacts/source-snapshots/M5Cardputer-f1392858
-LC_ALL=C find . -type f | LC_ALL=C sort | xargs sha256sum | sha256sum
-# b0f20d35d31d24514320a0263b51aeb33a01a50a4f68c7f341f172d3c2f232d7
-```
-
-33 files, **117 087 bytes**. **MIT**, with SPDX headers in every file.
-
-> ⚠ **`sha256sum` embeds the path it was given.** The *same bytes* produce three different tree
-> digests depending on where you stand:
->
-> | Run from | Path argument | Digest |
-> |---|---|---|
-> | repository root | `devices/m5stack/cardputer-adv/artifacts/…` | `cd081a07…` |
-> | the device directory | `artifacts/…` | `918c61c4…` |
-> | **inside the snapshot** | `.` | **`b0f20d35…`** ← the recorded one |
->
-> Only the third is portable. The skill's rule is "pin the locale when hashing trees"; the
-> working directory needs pinning for exactly the same reason, and it bit harder here than the
-> locale did.
-
-Only the UserDemo's *build configuration* is retained, not the full tree — it is 5 files and
-they are the load-bearing ones. Reconstruct the rest from the pinned commit above; then
-`python fetch_repos.py` clones the five dependencies at
-`M5GFX@0.2.15`, `M5Unified@0.2.10`, `mooncake@v2.2.0`, `mooncake_log@v1.3.0`,
-`smooth_ui_toolkit@v2.4.0`.
-
-## 4. Not acquired — and how to get each one
-
-| Artifact | Status | Command |
-|---|---|---|
-| **EasyLoader** | not-downloaded | `curl -fsSLO "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Easy_Loader_for_Cardputer-Adv.exe"` — a Windows self-extractor; expect the image plus esptool inside |
-| **Factory firmware binary** | **blocked** — no M5Burner id resolved | Find the id first: browse `burner.m5stack.com`, then `curl -fsSL "https://burner.m5stack.com/api/v1/firmwares/$ID"`. ⚠ `/api/…` returns 401; **`/api/v1/…` is public** |
-| Schematic sheet renders (4 × ~5848×4132 PNG) | in scratch, not committed | `curl -fsSLO "…/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_0{1,2,3,4}.png"` |
-| Stamp-S3A schematic | belongs to the **component** | [`components/m5stack/stamp-s3a`](../../../../components/m5stack/stamp-s3a/README.md) |
-| StampS3 v0.2 schematic | belongs to the component | `…/522/Sch_M5StampS3_v0.2.pdf` — 348 884 B, `6d92e1ae…` |
-| Cardputer v1.0/v1.1 schematic | in the v1.1 record | `…/1127/Sch_M5Cardputer.pdf` — **byte-identical to `…/481/…`** |
-| `M5_Hardware` structure files | not-downloaded | `git clone --filter=blob:none --no-checkout https://github.com/m5stack/M5_Hardware.git` then sparse-checkout `Products/K132-Adv_Cardputer-Adv/Structures` |
-| Product imagery | reference-only | **do not commit** — unlicensed. See [`../media.md`](../media.md) |
-| CardputerZero schematic + label ZIP | not-downloaded | `…/1243/C154-CardputerZERO_SCH_V0.6.1_20260702.pdf`, `…/1243/CardputerZero_Labels.zip` |
-
-## 5. Dead URL — do not retry
-
-```
-https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2_page_01.png
-```
-
-Returns **402 bytes that are not a PNG**. The `_page_NN.png` render convention is per-product,
-not universal. Checked 2026-09-04. **Not saved under a `.png` name.**
-
-## 6. Verify-only
-
-```bash
-cd "$(git rev-parse --show-toplevel)"/devices/m5stack/cardputer-adv
-python3 - <<'PY'
-import json,hashlib,os,sys
-m=json.load(open('acquisition/manifest.json')); root=os.getcwd(); bad=0
-for a in m['artifacts']:
-    d=a.get('destination')
-    if not d or a.get('repository_state')=='not-downloaded': continue
-    p=os.path.join(root, d.split('devices/m5stack/cardputer-adv/',1)[-1])
-    if d.endswith('/'):
-        print('DIR ', 'ok' if os.path.isdir(p) else 'MISSING', d); bad+= not os.path.isdir(p); continue
-    if not os.path.exists(p): print('MISSING', d); bad+=1; continue
-    h=hashlib.sha256(open(p,'rb').read()).hexdigest()
-    ok = h==a['sha256'] and os.path.getsize(p)==a['bytes']
-    print('OK  ' if ok else 'FAIL', d); bad += not ok
-sys.exit(1 if bad else 0)
-PY
-```
-
-## 7. Licensing summary
-
-| Group | Artifacts | Status | Action |
-|---|---|---|---|
-| **Permissive, clear** | `M5Cardputer` snapshot, UserDemo build config | **MIT**, SPDX headers present | safe to stage |
-| **Conditional** | UserDemo *full tree* (not retained) | MIT repo that **pins LGPL-3.0 RadioLib** | resolve before vendoring the whole tree |
-| **Unknown terms** | schematic PDF, mechanical PDF, documentation HTML | no notice anywhere; openly published on the product page | **retained but left untracked** pending a user decision — the same position this repository already takes on M5Stack schematics |
-| **Not licensed for redistribution** | all product imagery | `vendors/m5stack` §8 | **reference-only**, zero bytes committed |
-| **Large** | sheet renders (~2.5 MB total) | unlicensed technical images | kept in scratch (archive repo), regenerable from the URLs above |
-
-**User decision needed:** whether to stage the three unknown-terms documents
-(1.15 MB combined). Recommendation: **stage** — they are small, they are the primary evidence
-for the entire record, and this repository already tracks M5Stack schematics for other products.
diff --git a/devices/m5stack/cardputer-adv/acquisition/manifest.json b/devices/m5stack/cardputer-adv/acquisition/manifest.json
deleted file mode 100644
index a2d5ff1..0000000
--- a/devices/m5stack/cardputer-adv/acquisition/manifest.json
+++ /dev/null
@@ -1,434 +0,0 @@
-{
-  "schema": "hardware-doc/acquisition-manifest/1",
-  "device": "devices/m5stack/cardputer-adv",
-  "snapshot": "2026-09-04",
-  "downloader": "acquisition/README.md documents the exact curl/git commands; no bespoke downloader script was written for this device because every artifact is a single unauthenticated GET or a git clone at a pinned commit.",
-  "artifacts": [
-   {
-     "id": "fcc-2AN3WM5CARDPUTERADV-8755018",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2AN3WM5CARDPUTERADV/Test-Report/AiTDG-251013004W1-FCC-BLE-test-report-8755018.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755018",
-      "https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755018.pdf",
-      "https://fccid.io/2AN3WM5CARDPUTERADV",
-      "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/Test-Report/AiTDG-251013004W1-FCC-BLE-test-report-8755018.pdf"
-     ],
-     "sha256": "5023c54591ee8a5f7029b8291668e442e33a6ab0da65cbe0681fc3b6cd5bfa13",
-     "bytes": 987894,
-     "destination": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-11-19",
-     "fcc_id": "2AN3WM5CARDPUTERADV",
-     "fcc_document_id": "8755018",
-     "exhibit_type": "Test Report",
-     "exhibit_title_as_filed": "AiTDG-251013004W1-FCC BLE test report",
-     "grant_date": "2025-11-19",
-     "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf",
-     "placeholder": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/m5stack/cardputer-adv",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2AN3WM5CARDPUTERADV-8755020",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2AN3WM5CARDPUTERADV/RF-Exposure-Info/AiTDG-251013004W3-FCC-RF-EXPOSURE-0cm-8755020.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755020",
-      "https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755020.pdf",
-      "https://fccid.io/2AN3WM5CARDPUTERADV",
-      "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/RF-Exposure-Info/AiTDG-251013004W3-FCC-RF-EXPOSURE-0cm-8755020.pdf"
-     ],
-     "sha256": "f63d066218178f0e6cd7fde050ffabeb27ba6789c78bcd349aa87306a864e1fd",
-     "bytes": 258022,
-     "destination": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-11-19",
-     "fcc_id": "2AN3WM5CARDPUTERADV",
-     "fcc_document_id": "8755020",
-     "exhibit_type": "RF Exposure Info",
-     "exhibit_title_as_filed": "AiTDG-251013004W3_FCC RF EXPOSURE 0cm",
-     "grant_date": "2025-11-19",
-     "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf",
-     "placeholder": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/m5stack/cardputer-adv",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2AN3WM5CARDPUTERADV-8755026",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2AN3WM5CARDPUTERADV/External-Photos/External-Photos-8755026.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755026",
-      "https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755026.pdf",
-      "https://fccid.io/2AN3WM5CARDPUTERADV",
-      "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/External-Photos/External-Photos-8755026.pdf"
-     ],
-     "sha256": "b6e8389cbab5335b77c5b6aed65e341583c927cae3eedcb1132254787638e7e2",
-     "bytes": 1041781,
-     "destination": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-11-19",
-     "fcc_id": "2AN3WM5CARDPUTERADV",
-     "fcc_document_id": "8755026",
-     "exhibit_type": "External Photos",
-     "exhibit_title_as_filed": "External Photos",
-     "grant_date": "2025-11-19",
-     "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf",
-     "placeholder": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/m5stack/cardputer-adv",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2AN3WM5CARDPUTERADV-8755028",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2AN3WM5CARDPUTERADV/Label/FCC-ID-Label-8755028.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755028",
-      "https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755028.pdf",
-      "https://fccid.io/2AN3WM5CARDPUTERADV",
-      "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/Label/FCC-ID-Label-8755028.pdf"
-     ],
-     "sha256": "38b3c9554c31c2df348d4a3f2663bd370c7ce01b3c0621d6413ee5e41070c681",
-     "bytes": 184122,
-     "destination": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-fcc-id-label.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-11-19",
-     "fcc_id": "2AN3WM5CARDPUTERADV",
-     "fcc_document_id": "8755028",
-     "exhibit_type": "ID Label/Location Info",
-     "exhibit_title_as_filed": "FCC ID Label",
-     "grant_date": "2025-11-19",
-     "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/m5stack/cardputer-adv",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2AN3WM5CARDPUTERADV-8755029",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2AN3WM5CARDPUTERADV/Internal-Photos/Internal-Photos-8755029.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755029",
-      "https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755029.pdf",
-      "https://fccid.io/2AN3WM5CARDPUTERADV",
-      "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/Internal-Photos/Internal-Photos-8755029.pdf"
-     ],
-     "sha256": "b7b25570be4a4fb5f2e8b9601a0337801b1f8eac30386b9ff6bb9a30735069e1",
-     "bytes": 1848880,
-     "destination": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-internal-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-11-19",
-     "fcc_id": "2AN3WM5CARDPUTERADV",
-     "fcc_document_id": "8755029",
-     "exhibit_type": "Internal Photos",
-     "exhibit_title_as_filed": "Internal Photos",
-     "grant_date": "2025-11-19",
-     "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/m5stack/cardputer-adv",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2AN3WM5CARDPUTERADV-8755104",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2AN3WM5CARDPUTERADV/User-Manual/User-Manual-8755104.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755104",
-      "https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755104.pdf",
-      "https://fccid.io/2AN3WM5CARDPUTERADV",
-      "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/User-Manual/User-Manual-8755104.pdf"
-     ],
-     "sha256": "2e7ea0b53e4523863f0b3887e353ff1566b6011c1403004030986a8a541eb3b8",
-     "bytes": 390005,
-     "destination": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-11-19",
-     "fcc_id": "2AN3WM5CARDPUTERADV",
-     "fcc_document_id": "8755104",
-     "exhibit_type": "Users Manual",
-     "exhibit_title_as_filed": "User Manual",
-     "grant_date": "2025-11-19",
-     "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf",
-     "placeholder": "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/m5stack/cardputer-adv",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-      "id": "adv-schematic",
-      "kind": "schematic",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf",
-      "fallback_urls": [
-        "https://docs.m5stack.com/en/core/Cardputer-Adv (asset list)",
-        "https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit (same file, linked)"
-      ],
-      "destination": "devices/m5stack/cardputer-adv/artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf",
-      "sha256": "9553f5ee22b6e5f29a385388192e42c5ff76f16281b6f7ea9418f7b62a2d48b0",
-      "bytes": 878155,
-      "retrieved": "2026-09-04",
-      "upstream_version": "v1.0, file-stamped 2025-06-20",
-      "license": "none stated",
-      "license_evidence": "no notice in the PDF or on the product page",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repository_state": "untracked",
-      "target_hardware": "K132-Adv",
-      "reacquisition": "automatic",
-      "notes": "4 sheets. The primary evidence for the entire component inventory. Text layer validated against the product page PinMap; every transcribed value additionally read from a rendered sheet crop."
-    },
-    {
-      "id": "adv-mechanical",
-      "kind": "mechanical drawing",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV.pdf",
-      "fallback_urls": [
-        "https://docs.m5stack.com/en/core/Cardputer-Adv (asset list)",
-        "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV_page_01.png"
-      ],
-      "destination": "devices/m5stack/cardputer-adv/artifacts/mechanical/K132-Adv-cardputer-ADV.pdf",
-      "sha256": "6c937ca05e0894e54a3e47abb57e91de1b755dea032fd3f7438ea7a3e34550da",
-      "bytes": 127977,
-      "retrieved": "2026-09-04",
-      "upstream_version": null,
-      "license": "none stated",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repository_state": "untracked",
-      "target_hardware": "K132-Adv",
-      "reacquisition": "automatic",
-      "notes": "84.0 x 54.0 x 19.6 mm."
-    },
-    {
-      "id": "adv-docs-en",
-      "kind": "documentation snapshot",
-      "url": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "fallback_urls": [
-        "https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/Cardputer-Adv.pdf",
-        "https://web.archive.org/web/2026/https://docs.m5stack.com/en/core/Cardputer-Adv"
-      ],
-      "destination": "devices/m5stack/cardputer-adv/artifacts/docs/docs-en-core-Cardputer-Adv.html",
-      "sha256": "f05bbb70ca0964ebcd465e866bf25302f24cd29ecada5099803c7786c3b54fec",
-      "bytes": 147339,
-      "retrieved": "2026-09-04",
-      "upstream_version": "live page, undated",
-      "license": "none stated",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repository_state": "untracked",
-      "target_hardware": "K132-Adv",
-      "reacquisition": "automatic",
-      "notes": "Server-rendered HTML; the full spec table, PinMap and asset URLs are present in the source. The zh_CN copy was fetched as a translation control: unlike the PaperMono case, no CN-only datasheet links were found for this product."
-    },
-    {
-      "id": "adv-docs-zh_CN",
-      "kind": "documentation snapshot",
-      "url": "https://docs.m5stack.com/zh_CN/core/Cardputer-Adv",
-      "fallback_urls": [
-        "https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/Cardputer-Adv.pdf",
-        "https://web.archive.org/web/2026/https://docs.m5stack.com/en/core/Cardputer-Adv"
-      ],
-      "destination": "devices/m5stack/cardputer-adv/artifacts/docs/docs-zh_CN-core-Cardputer-Adv.html",
-      "sha256": "4a285b0281f21864e394554161976786ac4846abfd7021f2422a3f4cced2ac61",
-      "bytes": 146690,
-      "retrieved": "2026-09-04",
-      "upstream_version": "live page, undated",
-      "license": "none stated",
-      "redistribution_status": "unknown",
-      "disposition": "repository",
-      "repository_state": "untracked",
-      "target_hardware": "K132-Adv",
-      "reacquisition": "automatic",
-      "notes": "Server-rendered HTML; the full spec table, PinMap and asset URLs are present in the source. The zh_CN copy was fetched as a translation control: unlike the PaperMono case, no CN-only datasheet links were found for this product."
-    },
-    {
-      "id": "m5cardputer-lib",
-      "kind": "source snapshot",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01",
-      "fallback_urls": [
-        "https://github.com/m5stack/M5Cardputer/archive/f1392858b9994c3547120e602a57d3553d16ab01.zip",
-        "https://registry.platformio.org/libraries/m5stack/M5Cardputer"
-      ],
-      "destination": "devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "commit_date": "2026-07-21",
-      "retrieved": "2026-09-04",
-      "license": "MIT",
-      "license_evidence": "SPDX-FileCopyrightText / SPDX-License-Identifier headers in every source file",
-      "redistribution_status": "allowed",
-      "disposition": "repository",
-      "repository_state": "untracked",
-      "files": 33,
-      "bytes": 117087,
-      "target_hardware": "K132, K132-V11, K132-Adv",
-      "reacquisition": "automatic",
-      "notes": "Contains both keyboard readers and the vendored Adafruit_TCA8418. NOTE: library.json declares M5Unified/M5GFX/IRremote while library.properties additionally declares LibSSH-ESP32 - the two dependency lists disagree.",
-      "tree_digest": "b0f20d35d31d24514320a0263b51aeb33a01a50a4f68c7f341f172d3c2f232d7",
-      "tree_digest_recipe": "cd <snapshot root> && LC_ALL=C find . -type f | LC_ALL=C sort | xargs sha256sum | sha256sum   -- MUST be run from inside the snapshot directory: sha256sum embeds the path it was given, so running it from the repository root yields a different digest for identical bytes."
-    },
-    {
-      "id": "userdemo-adv-config",
-      "kind": "source snapshot (build configuration only)",
-      "url": "https://github.com/m5stack/M5Cardputer-UserDemo/tree/CardputerADV",
-      "permalink": "https://github.com/m5stack/M5Cardputer-UserDemo/tree/b549eac0a3c65bc108186c276b8fac0a214aaa4e",
-      "fallback_urls": [
-        "https://github.com/m5stack/M5Cardputer-UserDemo/archive/b549eac0a3c65bc108186c276b8fac0a214aaa4e.zip"
-      ],
-      "destination": "devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/",
-      "commit": "b549eac0a3c65bc108186c276b8fac0a214aaa4e",
-      "commit_date": "2026-06-08",
-      "retrieved": "2026-09-04",
-      "license": "MIT",
-      "license_evidence": "repository LICENSE; SPDX headers",
-      "redistribution_status": "conditional",
-      "obligations": "The repository is MIT, but repos.json pins RadioLib, which is LGPL-3.0 upstream. Only hal_config.h, partitions.csv, repos.json, sdkconfig.defaults and dependencies.lock were retained here; none of them is RadioLib. Flagged for a full-tree decision.",
-      "disposition": "repository",
-      "repository_state": "untracked",
-      "files": 5,
-      "target_hardware": "K132-Adv",
-      "reacquisition": "automatic",
-      "notes": "The ADV firmware lives on a branch, not on main. Dependency pins (M5GFX 0.2.15, M5Unified 0.2.10) are older than current heads."
-    },
-    {
-      "id": "adv-easyloader",
-      "kind": "firmware installer (Windows)",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Easy_Loader_for_Cardputer-Adv.exe",
-      "destination": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "omission_reason": "Windows self-extracting binary; deferred. Would yield the factory image and its build metadata.",
-      "target_hardware": "K132-Adv"
-    },
-    {
-      "id": "adv-firmware-binary",
-      "kind": "firmware image",
-      "url": "https://burner.m5stack.com/api/v1/firmwares/{id}/versions/{vid}/download",
-      "destination": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "reacquisition": "blocked",
-      "omission_reason": "No M5Burner firmware id was resolved for the Cardputer ADV in this pass. The /api/v1 route is public (vendors/m5stack section 4); the missing piece is the id.",
-      "target_hardware": "K132-Adv"
-    },
-    {
-      "id": "adv-imu-axis-image",
-      "kind": "image",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/IMU-Cardputer-Adv.jpg",
-      "destination": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "omission_reason": "M5Stack imagery carries no redistribution licence (vendors/m5stack section 8). Recorded because it is the only vendor image with information not available in text.",
-      "target_hardware": "K132-Adv"
-    },
-    {
-      "id": "m5-hardware-structures",
-      "kind": "mechanical/CAD",
-      "url": "https://github.com/m5stack/M5_Hardware/tree/master/Products/K132-Adv_Cardputer-Adv/Structures",
-      "destination": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": null,
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "omission_reason": "Not fetched in this pass. Note that vendors/m5stack section 3.2 warns absence from M5_Hardware proves nothing - but here the docs page links a path that does exist.",
-      "target_hardware": "K132-Adv"
-    },
-    {
-      "id": "stamps3-v02-page-render",
-      "kind": "image",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2_page_01.png",
-      "destination": null,
-      "sha256": null,
-      "bytes": null,
-      "retrieved": "2026-09-04",
-      "redistribution_status": "n/a",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "reacquisition": "lost",
-      "omission_reason": "DEAD: returns 402 bytes that are not a PNG. The _page_NN.png convention does not apply to product id 522. Recorded so it is not retried; deliberately not saved under a .png extension.",
-      "target_hardware": "K132"
-    }
-  ]
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf.ARCHIVED.md b/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf.ARCHIVED.md
deleted file mode 100644
index f8362f4..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 987,894 B (0.94 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 987,894 B (0.94 MiB) |
-| SHA-256 | `5023c54591ee8a5f7029b8291668e442e33a6ab0da65cbe0681fc3b6cd5bfa13` |
-| FCC ID | **`2AN3WM5CARDPUTERADV`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | AiTDG-251013004W1-FCC BLE test report |
-| FCC document id | 8755018 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Cardputer Adv, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV/Test-Report/AiTDG-251013004W1-FCC-BLE-test-report-8755018.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755018>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755018.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/Test-Report/AiTDG-251013004W1-FCC-BLE-test-report-8755018.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf" \
-   "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTERADV/Test-Report/AiTDG-251013004W1-FCC-BLE-test-report-8755018.pdf" -o "2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf"
-echo "5023c54591ee8a5f7029b8291668e442e33a6ab0da65cbe0681fc3b6cd5bfa13  2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf.ARCHIVED.md b/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf.ARCHIVED.md
deleted file mode 100644
index 08f78b5..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 258,022 B (0.25 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 258,022 B (0.25 MiB) |
-| SHA-256 | `f63d066218178f0e6cd7fde050ffabeb27ba6789c78bcd349aa87306a864e1fd` |
-| FCC ID | **`2AN3WM5CARDPUTERADV`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | AiTDG-251013004W3_FCC RF EXPOSURE 0cm |
-| FCC document id | 8755020 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Cardputer Adv, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV/RF-Exposure-Info/AiTDG-251013004W3-FCC-RF-EXPOSURE-0cm-8755020.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755020>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755020.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/RF-Exposure-Info/AiTDG-251013004W3-FCC-RF-EXPOSURE-0cm-8755020.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf" \
-   "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTERADV/RF-Exposure-Info/AiTDG-251013004W3-FCC-RF-EXPOSURE-0cm-8755020.pdf" -o "2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf"
-echo "f63d066218178f0e6cd7fde050ffabeb27ba6789c78bcd349aa87306a864e1fd  2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf.ARCHIVED.md b/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 7805f49..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTERADV-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 1,041,781 B (0.99 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,041,781 B (0.99 MiB) |
-| SHA-256 | `b6e8389cbab5335b77c5b6aed65e341583c927cae3eedcb1132254787638e7e2` |
-| FCC ID | **`2AN3WM5CARDPUTERADV`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 8755026 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Cardputer Adv, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV/External-Photos/External-Photos-8755026.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755026>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755026.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/External-Photos/External-Photos-8755026.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf" \
-   "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTERADV/External-Photos/External-Photos-8755026.pdf" -o "2AN3WM5CARDPUTERADV-external-photos.pdf"
-echo "b6e8389cbab5335b77c5b6aed65e341583c927cae3eedcb1132254787638e7e2  2AN3WM5CARDPUTERADV-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-fcc-id-label.pdf b/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-fcc-id-label.pdf
deleted file mode 100644
index a63d61e..0000000
Binary files a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-fcc-id-label.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-internal-photos.pdf b/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-internal-photos.pdf
deleted file mode 100644
index 715c036..0000000
Binary files a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-internal-photos.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf.ARCHIVED.md b/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 51124a0..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTERADV-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 390,005 B (0.37 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 390,005 B (0.37 MiB) |
-| SHA-256 | `2e7ea0b53e4523863f0b3887e353ff1566b6011c1403004030986a8a541eb3b8` |
-| FCC ID | **`2AN3WM5CARDPUTERADV`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 8755104 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Cardputer Adv, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV/User-Manual/User-Manual-8755104.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8755104>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTERADV/8755104.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTERADV>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTERADV/User-Manual/User-Manual-8755104.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf" \
-   "devices/m5stack/cardputer-adv/artifacts/certification/2AN3WM5CARDPUTERADV-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTERADV/User-Manual/User-Manual-8755104.pdf" -o "2AN3WM5CARDPUTERADV-user-manual.pdf"
-echo "2e7ea0b53e4523863f0b3887e353ff1566b6011c1403004030986a8a541eb3b8  2AN3WM5CARDPUTERADV-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-adv/artifacts/certification/README.md b/devices/m5stack/cardputer-adv/artifacts/certification/README.md
deleted file mode 100644
index 9a96bad..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5CARDPUTERADV`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5CARDPUTERADV`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2025-11-19** |
-| Equipment class | M5Cardputer Adv, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Source page | <https://fccid.io/2AN3WM5CARDPUTERADV> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5CARDPUTERADV-fcc-id-label.pdf` | 184,122 | `38b3c9554c31c2df348d4a3f2663bd370c7ce01b3c0621d6413ee5e41070c681` | ID Label/Location Info |
-| `2AN3WM5CARDPUTERADV-internal-photos.pdf` | 1,848,880 | `b7b25570be4a4fb5f2e8b9601a0337801b1f8eac30386b9ff6bb9a30735069e1` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf.ARCHIVED.md`](2AN3WM5CARDPUTERADV-aitdg-251013004w1-fcc-ble-test-report.pdf.ARCHIVED.md) | 987,894 | Test Report |
-| [`2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf.ARCHIVED.md`](2AN3WM5CARDPUTERADV-aitdg-251013004w3-fcc-rf-exposure-0cm.pdf.ARCHIVED.md) | 258,022 | RF Exposure Info |
-| [`2AN3WM5CARDPUTERADV-external-photos.pdf.ARCHIVED.md`](2AN3WM5CARDPUTERADV-external-photos.pdf.ARCHIVED.md) | 1,041,781 | External Photos |
-| [`2AN3WM5CARDPUTERADV-user-manual.pdf.ARCHIVED.md`](2AN3WM5CARDPUTERADV-user-manual.pdf.ARCHIVED.md) | 390,005 | Users Manual |
-
-Archived total: **4 files, 2.55 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 1.94 MiB** |
-| Archived | **4 files, 2.55 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/m5stack/cardputer-adv/artifacts/docs/docs-en-core-Cardputer-Adv.html b/devices/m5stack/cardputer-adv/artifacts/docs/docs-en-core-Cardputer-Adv.html
deleted file mode 100644
index 7907fd9..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/docs/docs-en-core-Cardputer-Adv.html
+++ /dev/null
@@ -1,112 +0,0 @@
-<!doctype html>
-<html data-n-head-ssr lang="en" data-n-head="%7B%22lang%22:%7B%22ssr%22:%22en%22%7D%7D">
-  <head>
-    <title>m5-docs</title><meta data-n-head="ssr" charset="utf-8"><meta data-n-head="ssr" name="viewport" content="width=device-width,initial-scale=1,minimum-scale=1,user-scalable=no"><meta data-n-head="ssr" data-hid="description" name="description" content="The reference docs for M5Stack products. Quick start, get the detailed information or instructions such as IDE,UIFLOW,Arduino. The tutorials for M5Burner, Firmware, Burning, programming. ESP32,M5StickC,StickV, StickT,M5ATOM."><link data-n-head="ssr" rel="icon" type="image/x-icon" href="/favicon.ico"><script data-n-head="ssr" data-hid="device-preload-detector">!function(){try{var e=document.documentElement;if(!e)return;var d=e.clientWidth||Number.POSITIVE_INFINITY,i=Number(window.innerWidth||0)||Number.POSITIVE_INFINITY,a=Math.min(d,i)<1024;e.classList.add(a?"device-preload-mobile":"device-preload-desktop"),a&&(e.classList.add("device-preload-pending"),window.__m5DevicePreloadReady=function(){e.classList.remove("device-preload-pending"),e.classList.add("device-preload-ready")})}catch(e){}}()</script><script data-n-head="ssr" src="https://cloud.umami.is/script.js" data-website-id="38e73ff2-ec10-4a8f-bfe2-c22a381ce306" defer></script><script data-n-head="ssr" src="/script/ga.js"></script><script data-n-head="ssr" src="/script/global.js"></script><script data-n-head="ssr" src="/public/esp-web-tools/install-button.js?module" type="module"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/marked.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/highlight.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-chat/index.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-qa/index.js"></script><link rel="preload" href="/_nuxt/41d5c62.js" as="script"><link rel="preload" href="/_nuxt/5a34d22.js" as="script"><link rel="preload" href="/_nuxt/a352c6d.js" as="script"><link rel="preload" href="/_nuxt/b9c4bc6.js" as="script"><link rel="preload" href="/_nuxt/c970150.js" as="script"><style data-vue-ssr-id="0b40e9c2:0 afa51714:0 73039f54:0 2576b79a:0 69f1b16c:0 17a511fe:0 3d88442c:0 3afe6180:0 786f8504:0 1af4924a:0 e762b0ec:0 e646c77c:0 4a658548:0 5f76b520:0 3e555512:0 4e0caf6f:0 060bbeb3:0 3ddd7ff2:0 bb0e6f22:0 27d15a7c:0 2c0daf93:0 d1c8934a:0 09fcdd3b:0 3231c87d:0 8716e91a:0 09d04477:0">body,html{width:100%;margin:0;padding:0}html.device-preload-mobile.device-preload-pending{background:linear-gradient(180deg,#f7f9fc,#eef3f8)}html.device-preload-mobile.device-preload-pending body{background:0 0}html.device-preload-mobile.device-preload-pending body:before{content:"";position:fixed;top:0;right:0;bottom:0;left:0;z-index:9999;pointer-events:none;background:linear-gradient(180deg,hsla(0,0%,100%,.92),rgba(243,247,251,.98)),radial-gradient(circle at top right,rgba(0,100,194,.08),transparent 38%)}html.device-preload-mobile.device-preload-pending body:after{content:"";position:fixed;left:50%;top:50%;width:.63529rem;height:.63529rem;margin-left:-.31765rem;margin-top:-.31765rem;z-index:10000;pointer-events:none;border:.04706rem solid rgba(35,141,251,.18);border-top-color:#238dfb;border-radius:50%;box-shadow:0 0 0 .09412rem rgba(35,141,251,.08);-webkit-animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite;animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite}html.device-preload-mobile.device-preload-pending .device-hydration-sensitive{opacity:0;visibility:hidden}html.device-preload-mobile.device-preload-ready body:after,html.device-preload-mobile.device-preload-ready body:before{opacity:0;transition:opacity .22s ease}html.device-preload-mobile.device-preload-ready .device-hydration-sensitive{visibility:visible;opacity:1;transition:opacity .18s ease}@-webkit-keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@-webkit-keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}@keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}html{overflow:hidden;overflow-y:auto}html::-webkit-scrollbar{width:.14118rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}@font-face{font-family:SourceCodePro;src:url(https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/font/SourceCodePro-Regular.ttf)}body,button{font-family:SourceCodePro,Microsoft YaHei;line-height:inherit;box-sizing:border-box}body,button,input{font-family:SourceCodePro,Microsoft YaHei,sans-serif}a{outline:0}.product_pic img{width:33%}.page-enter-active,.page-leave-active{transition:opacity .5s}.page-enter,.page-leave-active{opacity:0}.bounce-enter-active{-webkit-animation:bounce-in .8s;animation:bounce-in .8s}.bounce-leave-active{-webkit-animation:bounce-out .5s;animation:bounce-out .5s}@-webkit-keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@-webkit-keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}body,button,html[lang=zh-cn] footer,html[lang=zh-cn] header,input{font-family:Microsoft YaHei,sans-serif}html[lang=en] footer,html[lang=en] header{font-family:Montserrat,Microsoft YaHei,sans-serif}@font-face{font-family:Montserrat;font-weight:400;font-style:normal;src:url(/assets/fonts/Montserrat-Regular.woff2) format("woff2"),url(/assets/fonts/Montserrat-Regular.woff) format("woff"),url(/assets/fonts/Montserrat-Regular.otf) format("opentype"),url(/assets/fonts/Montserrat-Regular.ttf) format("truetype")}@font-face{font-family:Montserrat;font-weight:500;font-style:normal;src:url(/assets/fonts/Montserrat-Medium.woff2) format("woff2"),url(/assets/fonts/Montserrat-Medium.woff) format("woff"),url(/assets/fonts/Montserrat-Medium.otf) format("opentype"),url(/assets/fonts/Montserrat-Medium.ttf) format("truetype")}*{margin:0;padding:0;box-sizing:border-box}html{height:auto!important;font-size:10vw;line-height:1}@media screen and (max-width:320px){html{font-size:32PX}}@media screen and (min-width:540px){html{font-size:44PX}}@media screen and (min-width:860px){html{font-size:48PX}}@media screen and (min-width:960px){html{font-size:49PX}}@media screen and (min-width:1024px){html{font-size:52PX}}@media screen and (min-width:1175px){html{font-size:53PX}}@media screen and (min-width:1280px){html{font-size:56PX}}@media screen and (min-width:1366px){html{font-size:63PX}}@media screen and (min-width:1400px){html{font-size:68PX}}@media screen and (min-width:1440px){html{font-size:69PX}}@media screen and (min-width:1540px){html{font-size:73PX}}@media screen and (min-width:1680px){html{font-size:75PX}}@media screen and (min-width:1920px){html{font-size:75PX}}@media screen and (min-width:2560px){html{font-size:85PX}}body{-webkit-font-smoothing:subpixel-antialiased}li{list-style-type:none}img,li{-webkit-user-drag:none}img{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}a{text-decoration:none;-webkit-user-drag:none}a,button{outline:0}button{border:none;background-color:transparent;cursor:pointer}.fade-enter-active,.fade-leave-active{transition:opacity .5s}.fade-enter,.fade-leave-to{opacity:0}.markdown.guide img{box-shadow:0 -.07059rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);margin-top:.17647rem;margin-bottom:.58824rem;margin-left:.11765rem}.markdown.guide .blockly_svg{box-shadow:unset;margin:.17647rem 0 .05882rem;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content}.docs-layouts{padding-top:.58824rem;display:flex;justify-content:center;position:relative;margin-bottom:.35294rem}.docs-layouts .docs-layouts-sidebar{position:sticky;top:1.17647rem;left:0;height:-webkit-max-content;height:-moz-max-content;height:max-content;z-index:2;background-color:#fff}.docs-layouts .docs-layouts-title{display:flex;flex-direction:row;margin-bottom:.11765rem;align-items:center;width:100%;height:.47059rem;border-bottom:.03529rem solid #f5f5f5}.docs-layouts .docs-layouts-title .docs-layouts-icon{background-color:#238dfb;border-radius:.11765rem;display:flex;justify-content:center;align-items:center;height:.35294rem;width:.35294rem;margin-right:.11765rem}.docs-layouts .docs-layouts-title .docs-layouts-icon img{width:.23529rem;height:.23529rem}.docs-layouts .docs-layouts-title p{font-size:.23529rem;font-weight:700;color:#2f495e;line-height:.35294rem}.docs-layouts .docs-layouts-body{width:14.11765rem;min-width:0;max-width:100%;margin:0 .29412rem}.docs-layouts .docs-layouts-anchor{position:sticky;top:1.2rem;right:0;z-index:1;background-color:#fff;height:80vh;overflow-y:scroll}@media screen and (max-width:1200px){.docs-layouts .docs-layouts-anchor{display:none}}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar{width:.14118rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.mobile .docs-layouts{padding:.35294rem;display:flex}.mobile .docs-layouts .docs-layouts-body{width:100%;min-width:0;max-width:100%;margin:0}.mobile .docs-layouts .docs-layouts-sidebar{position:fixed;height:100vh;width:5.17647rem;top:0;padding:.47059rem .35294rem;left:auto;left:-100%;box-shadow:.11765rem .23529rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);transition:all .25s ease;z-index:5}.mobile .docs-layouts .docs-layouts-sidebar.active{left:0}.default{color:#3f3f46}.primary{color:#006fee}.secondary{color:#9353d3}.success{color:#17c964}.warning{color:#f5a524}.danger{color:#f31260}.markdown{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-column-gap:.18824rem;-moz-column-gap:.18824rem;column-gap:.18824rem;min-width:0;max-width:100%;overflow:hidden;word-break:break-word;padding-bottom:.35294rem;color:#4f5f6f;font-size:.18824rem;font-weight:400}.markdown>*{grid-column:1/-1}.markdown .product-sku{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .product-date,.markdown .product-sku{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.09412rem 0 .09412rem .09412rem;display:inline-block}.markdown .product-date{background-color:#efefef;color:#345b83}.markdown .tag-green{background-color:#f0fff4;color:#00c58e}.markdown .tag-blue,.markdown .tag-green{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.11765rem;display:inline-block}.markdown .tag-blue{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .tag-orange{font-size:.23529rem;margin:.23529rem .23529rem .23529rem 0;border-radius:.03529rem;padding:.02353rem .11765rem;background-color:#f8b013;color:#fff;cursor:pointer}.markdown .product-title{display:flex;align-items:center}.markdown .product-title span{color:#2f495e}.markdown .shop-title{display:flex;justify-content:space-between;position:relative;margin:.02353rem 0 0 .09412rem;background:#007bff;border-radius:.05882rem;color:#2f495e}.markdown .shop-title .shop-text{width:0;height:.47059rem;line-height:.47059rem;font-size:.2rem;text-align:center;color:#fff;overflow:hidden;transition:all .2s ease}.markdown .shop-title .shop-icon{position:relative;width:.47059rem;height:.47059rem;font-size:.35294rem;text-align:center;display:inline-block}.markdown .shop-title .shop-icon img{width:.35294rem;height:100%;display:inline-block}.markdown .shop-title .shop-icon:before{content:"";position:absolute;top:50%;right:-.32941rem;width:0;height:0;border-left:.23529rem solid transparent;border-right:.23529rem solid transparent;border-bottom:.23529rem solid #007bff;transform:translateY(-50%) rotate(90deg);display:none}.markdown .shop-title .shop-icon.eol:before{display:none}.markdown .shop-title:hover{color:#238dfb}.markdown .shop-title:hover .shop-text{width:2.35294rem}.markdown .shop-title:hover .shop-icon:before{display:block}.markdown .shop-title:hover .shop-icon.eol:before{display:none}.markdown .eol-title{display:flex;align-items:center;position:relative;margin:.02353rem 0 0 .08235rem;padding:0 .17647rem;height:.47059rem;line-height:.47059rem;background-color:#2f495e;border-radius:.05882rem}.markdown .eol-title .eol-text{font-size:.2rem;color:#fff}.markdown video{display:block;width:50%;margin-bottom:.35294rem}.markdown .video-iframe{margin:.23529rem 0;height:5.88235rem}.markdown .video-iframe iframe{width:50%;height:100%}.markdown .video-iframe>a{font-size:.23529rem;display:block;margin-bottom:.23529rem}.markdown a{color:#238dfb}.markdown h1{margin-top:.28235rem;margin-bottom:.21176rem;font-size:.54118rem;line-height:1.25}.markdown h1,.markdown h2{font-weight:600;color:#2f495e}.markdown h2{margin-top:.42353rem;margin-bottom:.18824rem;font-size:.35294rem;line-height:1.35;padding:0 .42353rem .11765rem .16471rem;position:relative;border-bottom:.01176rem solid #dfe5ec;cursor:pointer;transition:all .3s}.markdown h2:after{content:"";width:.03529rem;top:.04706rem;bottom:.16471rem;background:#238dfb;position:absolute;left:0}.markdown h2:before{content:"";position:absolute;background-image:url(/assets/link.svg);width:.29412rem;height:.29412rem;background-size:.29412rem;top:.08235rem;right:.05882rem;opacity:0;transition:opacity .3s}.markdown h2:hover{color:#0064c2}.markdown h2:hover:before{opacity:1}.markdown h3{margin-top:.32941rem;margin-bottom:.16471rem;font-size:.28235rem;color:#34495e;line-height:1.4}.markdown h3,.markdown h4{font-weight:600;position:relative}.markdown h4{margin-top:.28235rem;margin-bottom:.14118rem;font-size:.23529rem;color:#43566a;line-height:1.45}.markdown h5{margin-top:.23529rem;margin-bottom:.11765rem;font-size:.21176rem;font-weight:600;color:#526579;position:relative;line-height:1.5}.markdown ul{margin-bottom:.23529rem}.markdown ul ul{margin-bottom:.11765rem}.markdown ul li{list-style-type:circle;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f}.markdown ol{margin-bottom:.23529rem}.markdown ol li{list-style-type:decimal;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f;padding-left:.05882rem}.markdown ol li::marker{color:#6f6f6f;font-weight:700}.markdown code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;position:relative;color:#263445;font-size:.18824rem}.markdown :not(pre)>code{padding:.02353rem .05882rem;color:#165f8f;background:#eef3f7;border:.01176rem solid #dfe5ec;border-radius:.04706rem;font-size:.92em;font-weight:500}.markdown p{color:#4f5f6f;font-size:.18824rem;font-weight:400;line-height:.31765rem;margin-bottom:.16471rem}.markdown mark{background-color:#ffe051;color:#000}.markdown img{margin-bottom:.35294rem}.markdown>img:not([width]):not([class]){max-width:100%}.markdown .hljs{margin:.05882rem 0 .35294rem;font-size:.18824rem;line-height:.32941rem;white-space:pre;padding:.23529rem .29412rem;overflow-x:auto;overflow-y:hidden;border-radius:.07059rem;background-color:transparent;font-family:SourceCodePro,Microsoft YaHei;width:100%}.markdown .language-bash,.markdown .language-cpp,.markdown .language-diff,.markdown .language-dts,.markdown .language-json,.markdown .language-python,.markdown .language-shell{margin:0;font-size:.18824rem;line-height:.32941rem;white-space:pre;overflow-x:auto;overflow-y:hidden;background-color:transparent;display:block;width:100%}.markdown table thead,.markdown table tr{border-top:.01176rem solid #aabfdc}.markdown .normal-blockquote{box-shadow:-.05882rem 0 0 0 #238dfb;background-color:#fbfcfe;padding:.23529rem;margin:.17647rem 0 .17647rem .05882rem}.markdown .normal-blockquote p{font-weight:500;margin:0}.markdown .table-container{display:block;width:100%;min-width:0;max-width:100%;overflow-x:auto;overflow-y:hidden;overscroll-behavior-inline:contain;-webkit-overflow-scrolling:touch}.markdown table{border:none;display:table;min-width:100%;overflow:auto;margin:.11765rem 0 .35294rem}.markdown table thead{height:.58824rem;background:linear-gradient(-90deg,#1186de,#0064c2)}.markdown table thead tr{line-height:.58824rem;font-size:.18824rem;font-weight:700;color:#fff}.markdown table thead tr th{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr{line-height:.58824rem;font-size:.18824rem;color:#7d7d7d}.markdown table tbody tr td{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr:nth-child(odd){background-color:#fbfcfe}.markdown table tbody tr:nth-child(2n){background-color:#edf4fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table{border:.01176rem solid #e6ebf2;border-collapse:separate;border-spacing:0;border-radius:.07059rem;overflow:hidden;box-shadow:none}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead{height:auto;background:#1f6fe5}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr{border:0;line-height:1.4;font-size:.17647rem;font-weight:600;color:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr th{padding:.10588rem .17647rem;border:0;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr{border:0;line-height:1.5;color:#2c2f36}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td{padding:.10588rem .17647rem;border:0;border-right:.01176rem solid #e6ebf2;border-bottom:.01176rem solid #e6ebf2;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td:last-child{border-right:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(odd){background:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(2n){background:#f7f9fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:last-child td{border-bottom:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:hover{background:#eef3ff}.markdown .compare-table-container .table-container table thead{background:#fff!important}.markdown .compare-table-container .table-container table thead th{color:#2f495e;text-align:center!important;vertical-align:bottom}.markdown .compare-table-container .table-container table thead th a{align-items:center}.markdown .compare-table-container .table-container table thead th img{display:block;width:1.76471rem;height:1.76471rem;-o-object-fit:contain;object-fit:contain;margin:0 auto .35294rem}.markdown .compare-table-container .table-container table thead th:first-child{text-align:center!important;vertical-align:middle}.markdown .compare-table-container .table-container table tbody td:first-child,.markdown .compare-table-container .table-container table tbody td:not(:first-child){text-align:center!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(odd):hover{background:#fff!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(2n):hover{background:#f7f9fc!important}.markdown .table-text-align-left table td,.markdown .table-text-align-left table th{text-align:left}.markdown .table-text-align-right table td,.markdown .table-text-align-right table th{text-align:right}.markdown .markdown-ol li{list-style-type:decimal}.markdown .error,.markdown .tip,.markdown .warn{font-size:.21176rem;border-bottom-right-radius:.02353rem;margin:.11765rem .11765rem .11765rem 0;position:relative;background-color:#fff;box-shadow:.02353rem 0 .08235rem .01176rem #efefef;display:flex;flex-direction:column;color:#838383;font-size:.18824rem;font-weight:400;line-height:.37647rem;border-radius:.07059rem;overflow:hidden}.markdown .error .error-content,.markdown .error .tip-content,.markdown .error .warn-content,.markdown .tip .error-content,.markdown .tip .tip-content,.markdown .tip .warn-content,.markdown .warn .error-content,.markdown .warn .tip-content,.markdown .warn .warn-content{padding:.23529rem}.markdown .error .tip-title,.markdown .tip .tip-title,.markdown .warn .tip-title{height:.41176rem;background-color:rgba(35,141,251,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#238dfb}.markdown .error .warn-title,.markdown .tip .warn-title,.markdown .warn .warn-title{height:.41176rem;background-color:rgba(253,184,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#c69000}.markdown .error .error-title,.markdown .tip .error-title,.markdown .warn .error-title{height:.41176rem;background-color:rgba(253,45,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#ff1616}.markdown .tip:before{background-image:url(/assets/tip.svg)}.markdown .tip:before,.markdown .warn:before{content:"";position:absolute;width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .warn:before{background-image:url(/assets/warning.svg)}.markdown .error:before{content:"";position:absolute;background-image:url(/assets/error.svg);width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .tip{border-left:.07059rem solid #238dfb}.markdown .warn{border-left:.07059rem solid #fdb802}.markdown .error{border-left:.07059rem solid rgba(253,2,2,.83922)}.markdown .learn{display:flex;grid-column:auto;width:100%;height:2.07059rem;margin:.09412rem 0;overflow:hidden;background:#fff;border:.01176rem solid #d3dde9;border-radius:.07059rem;transition:border-color .2s ease,box-shadow .2s ease,transform .2s ease}.markdown .learn:hover{border-color:#8ab4eb;box-shadow:0 .04706rem .14118rem rgba(31,111,229,.1);transform:translateY(-.01176rem)}.markdown .learn:hover .learn-contents{background:#f6f9fe}.markdown .learn .learn-img{flex:0 0 42%;min-height:0;position:relative;overflow:hidden;text-align:center;background:#f7f9fc;border-right:.01176rem solid #e6ebf2}.markdown .learn .learn-img img{display:block;width:100%;max-width:none;box-shadow:none;margin:0;height:100%;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;font-size:.09412rem}.markdown .learn .learn-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.markdown .learn .learn-contents{flex:1;min-width:0;padding:.23529rem;position:relative;display:flex;flex-direction:column;justify-content:center;background:#fbfcfe;transition:background-color .2s ease}.markdown .learn .learn-contents .learn-title{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:2;font-size:.21176rem;font-weight:600;line-height:.29412rem}.markdown .learn .learn-contents .learn-title a{color:#1f6fe5}.markdown .learn .learn-contents .learn-desc{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:3;margin-top:.09412rem;font-size:.18824rem;font-weight:400;color:#5d6673;line-height:.28235rem}.markdown .learn [\:not-has\(\%2B.learn\)]{grid-column:1/-1}.markdown .learn :not(:has(+.learn)){grid-column:1/-1}.markdown .learn [\:not-has\(\%2B.learn\)] .learn-img{flex-basis:2.82353rem}.markdown .learn :not(:has(+.learn)) .learn-img{flex-basis:2.82353rem}.mobile .markdown{grid-template-columns:minmax(0,1fr)}.mobile .markdown p{font-size:.21176rem}.mobile .markdown .learn{flex-direction:row;height:1.88235rem;max-width:none}.mobile .markdown .learn .learn-img{flex:0 0 40%;width:auto;min-height:0;aspect-ratio:auto;border-right:.01176rem solid #e6ebf2;border-bottom:0}.mobile .markdown .learn .learn-contents{padding:.14118rem .16471rem}.mobile .markdown .learn .learn-contents .learn-title{font-size:.18824rem;line-height:.25882rem;-webkit-line-clamp:2}.mobile .markdown .learn .learn-contents .learn-desc{margin-top:.07059rem;font-size:.16471rem;line-height:.24706rem;-webkit-line-clamp:3}@media screen and (max-width:900px){.markdown{grid-template-columns:minmax(0,1fr)}.markdown .learn .learn-img{flex-basis:2.82353rem}}.mobile video{width:100%;margin-bottom:.35294rem}.mobile .video-iframe{margin:.23529rem 0;height:5.88235rem}.mobile .video-iframe iframe{width:100%;height:100%}.easyloader-box{display:flex;flex-direction:row;width:100%}.easyloader-box>div{position:relative;width:50%;overflow:hidden}.easyloader-box p{margin:.11765rem .29412rem;color:#fff}.easyloader-box p:last-child{overflow-y:scroll;height:20%;font-size:.11765rem}.easyloader-mask{position:absolute;right:0;bottom:.07059rem;height:100%;width:100%;background-color:#000;opacity:.7;transition:all .3s;display:flex;flex-direction:column;justify-content:center;display:none}.easyloader-mask a{margin-top:.58824rem;text-align:center}.video_play{bottom:-100%}.easyloader-btn{position:absolute;display:flex;flex-direction:row;justify-content:space-around;bottom:7%;width:100%;padding:0 .23529rem;font-size:.23529rem}.easyloader-btn a{width:1.05882rem;text-align:center;padding:.02353rem .11765rem;background-color:#007bff;color:#fff!important;border-radius:.11765rem;font-size:.17647rem}.easyloader-btn a:hover{background-color:#45a9ff}@media screen and (max-width:768px){.easyloader-box{flex-direction:column;width:100%}.easyloader-box>div{width:100%}}.code-block-wrapper{display:flex;flex-direction:column;position:relative;margin:.16471rem 0 .23529rem;border:.01176rem solid #dfe5ec;border-radius:.07059rem;overflow:hidden;background:#f7f9fb}.code-block-header{display:flex;justify-content:space-between;align-items:center;min-height:.44706rem;padding:.04706rem .14118rem;background:#f0f3f6;border-bottom:.01176rem solid #dfe5ec}.code-block-header .language-label{font-size:.15294rem;color:#526579;font-weight:500}.copy-all-btn{display:flex;align-items:center;grid-gap:.11765rem;gap:.11765rem;justify-content:center;background:0 0;border:none;border-radius:.05882rem;padding:.07059rem;font-size:.16471rem;cursor:pointer;transition:all .2s;width:.37647rem;height:.37647rem;color:#526579}.copy-all-btn svg{width:100%;height:100%}.copy-all-btn code{display:none}.copy-all-btn:hover{color:#1769aa;background:#e4ebf2}.copy-all-btn.focus-visible,.copy-all-btn:focus-visible{color:#1769aa;background:#e4ebf2;outline:.02353rem solid #1769aa;outline-offset:.02353rem}.code-block-container{display:flex;overflow:auto;background:#f7f9fb;align-items:flex-start}.code-block-wrapper.code-block-limited .code-block-container,.code-block-wrapper.code-block-limited .code-line-container{max-height:560px;max-height:var(--code-max-height,560px);overflow:auto;transition:max-height .35s ease}.code-block-wrapper:not(.is-collapsed).code-block-limited .code-block-container,.code-block-wrapper:not(.is-collapsed).code-block-limited .code-line-container{max-height:16.47059rem}.code-toggle-btn{display:flex;align-items:center;justify-content:center;width:100%;min-height:.49412rem;padding:.09412rem .14118rem .11765rem;border:0;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(240,244,249,.96));color:#6b7f93;cursor:pointer;transition:background .2s ease,color .2s ease;position:relative;z-index:2}.code-toggle-btn.focus-visible,.code-toggle-btn:focus-visible,.code-toggle-btn:hover{outline:0;color:#2d7be9;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(228,238,248,.98))}.code-toggle-icon{font-size:.17647rem;line-height:1;transition:transform .25s ease,color .2s ease}.code-block-wrapper:not(.is-collapsed) .code-toggle-icon,.code-toggle-icon{transform:translateY(-.01176rem)}.code-block-fade{position:absolute;left:0;right:0;bottom:.49412rem;height:1.29412rem;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(247,249,251,.96));pointer-events:none;transition:opacity .2s ease;z-index:1}.code-block-wrapper.is-collapsed .code-block-fade{opacity:1}.code-block-wrapper:not(.is-collapsed) .code-block-fade{opacity:0}.markdown .code-block-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-block-container code.hljs{margin:0!important;padding:0!important;border-radius:0;background:0 0;line-height:.32941rem;font-size:.18824rem;white-space:pre}.markdown .code-line-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-line-container code.hljs{margin:0!important;padding:0!important;line-height:.32941rem;font-size:.18824rem;white-space:pre;width:100%;border-radius:0;background-color:transparent}.code-line-container{display:flex;background:#f7f9fb;align-items:center;position:relative;padding:.18824rem .21176rem}.code-line-container .copy-all-btn{opacity:.45;position:absolute;top:.11765rem;right:.11765rem;transition:all .2s}.code-line-container pre{overflow-x:auto}.code-line-container:hover .copy-all-btn,.code-line-container[focus-within] .copy-all-btn{opacity:1}.code-line-container:focus-within .copy-all-btn,.code-line-container:hover .copy-all-btn{opacity:1}@media (hover:none){.code-line-container .copy-all-btn{opacity:1}.markdown .learn:hover{border-color:#d3dde9;box-shadow:none;transform:none}.markdown .learn:hover .learn-contents{background:#fbfcfe}}.line-numbers{padding:.11765rem .09412rem;text-align:right;background:#f3f6f9;color:#8491a0;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;border-right:.01176rem solid #dfe5ec;font-family:SourceCodePro,Microsoft YaHei,sans-serif;line-height:.32941rem;min-width:.51765rem}.line-number{display:block;height:.32941rem}.code-content{flex:1;overflow:auto;padding:.11765rem .17647rem;line-height:.32941rem}.code-block-container,.code-content,.code-line-container pre{scrollbar-color:#c5cfda transparent;scrollbar-width:thin}.code-block-container::-webkit-scrollbar,.code-content::-webkit-scrollbar,.code-line-container pre::-webkit-scrollbar{width:.09412rem;height:.09412rem}.code-block-container::-webkit-scrollbar-thumb,.code-content::-webkit-scrollbar-thumb,.code-line-container pre::-webkit-scrollbar-thumb{background:#c5cfda;border-radius:.04706rem}.code-block-container::-webkit-scrollbar-track,.code-content::-webkit-scrollbar-track,.code-line-container pre::-webkit-scrollbar-track{background:0 0}.code-line{display:block;min-height:.32941rem;line-height:.32941rem;white-space:pre;font-weight:700;font-family:SourceCodePro,Microsoft YaHei,sans-serif}.code-line:hover{background-color:#eaf1f7;cursor:pointer}pre code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;font-size:.18824rem;overflow-y:auto;font-family:SourceCodePro;display:block;width:100%;color:#263445;line-height:.32941rem}code.hljs{background:0 0}pre{position:relative}pre .copy-btn{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;opacity:0;position:absolute;right:.05882rem;top:.05882rem;cursor:pointer;padding:.05882rem;border-radius:.03529rem;transition:.3s;background:hsla(0,0%,100%,.2);width:1.52941rem;height:.58824rem;color:#0064c2}pre .copy-btn:active{background:hsla(0,0%,99.2%,.575)}pre .copy-btn .icon{width:.35294rem;position:absolute;left:70%;top:70%;transform:translate(-50%,-50%)}pre .copy-success-text{color:#fff;position:absolute;font-size:.14118rem;top:.70588rem;font-weight:200;font-family:SourceCodePro,Microsoft YaHei;-webkit-animation:successCopy .5s ease 1 both;animation:successCopy .5s ease 1 both;color:#0064c2}@-webkit-keyframes successCopy{0%{right:0}to{right:.29412rem}}@keyframes successCopy{0%{right:0}to{right:.29412rem}}pre:hover .copy-btn{opacity:1}.files_download{display:flex;flex-direction:row;justify-content:space-evenly;flex-wrap:wrap;margin:.52941rem}.files_download .item{display:flex;justify-content:center;width:2.35294rem;box-shadow:.04706rem .04706rem .08235rem 0 #cecece;transition:all .25s ease}.files_download .item:hover{transform:scale(1.2)}.card-container{display:flex;justify-content:flex-start;margin-bottom:.35294rem;align-items:flex-start}.card-container .card-item{margin:.23529rem;width:3.52941rem;display:flex;flex-direction:column;justify-content:center;align-items:center;color:#fff;transition:all .25s ease}.card-container .card-item .card-cover{height:1.76471rem;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1)}.card-container .card-item .card-cover,.card-container .card-item .card-cover-img{width:100%;display:flex;align-items:center;justify-content:center;font-size:.28235rem;font-weight:700;margin-bottom:.11765rem;border-radius:.11765rem}.card-container .card-item .card-cover-img{position:relative}.card-container .card-item .card-cover-img .card-cover-content{display:none;padding:.11765rem}.card-container .card-item .card-cover-img .card-cover-content .card-cover-btn{display:block;text-align:center;background-color:#0064c2;color:#fff;font-size:.2rem;padding:.11765rem .17647rem;border-radius:.04706rem}.card-container .card-item .card-cover-img img{width:100%;box-shadow:none;margin:0}.card-container .card-item .card-cover-img:hover .card-cover-content{display:flex;flex-direction:column;justify-content:space-around;align-items:center;position:absolute;top:0;left:0;bottom:0;right:0;background-color:rgba(0,0,0,.5098)}.card-container .card-item .card-desc{padding:.17647rem;text-align:center;font-size:.17647rem;color:#2f495e}.card-container .card-item .card-desc a{display:block;text-align:left;color:#333;line-height:.23529rem}.card-container .card-item .card-desc a:hover{text-decoration:underline;color:#238dfb}.card-container .card-item:hover{transform:translateY(-.05882rem)}.card-container .linear-blue{background:linear-gradient(45deg,#09f,#6cf)}.card-container .linear-gray{background:linear-gradient(45deg,#f2f2f2,#ccc);color:#333}.card-container .linear-orange{background:linear-gradient(45deg,#fc0,#f90)}.card-container-video{display:flex;flex-wrap:wrap;grid-gap:.23529rem;gap:.23529rem;margin:.47059rem 0}.card-container-video li{list-style-type:none}.card-container-video .card-item-video{width:22%;position:relative;border-radius:.07059rem;overflow:hidden;transition:transform .3s ease;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1);background-color:#fff}.card-container-video .card-item-video:hover{transform:translateY(-.05882rem);box-shadow:0 .09412rem .18824rem rgba(0,0,0,.15)}.card-container-video .card-item-video:hover .card-cover-content{opacity:1}.card-container-video .card-item-video .card-cover-img{position:relative;width:100%;padding-top:56.25%;background-color:#e7e7e7;overflow:hidden}.card-container-video .card-item-video .card-cover-img img{position:absolute;top:50%;left:50%;width:100%;height:100%;-o-object-fit:cover;object-fit:cover;transform:translate(-50%,-50%);min-width:100%;min-height:100%;transition:transform .3s ease;margin:0}.card-container-video .card-item-video .card-desc-video{padding:.11765rem;text-align:center;font-weight:700}.card-container-video .card-item-video .card-cover-content{position:absolute;top:0;left:0;width:100%;height:100%;display:flex;justify-content:center;align-items:center;background-color:rgba(0,0,0,.5);opacity:0;transition:opacity .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn{display:inline-block;padding:.09412rem .18824rem;margin:0 .11765rem;background-color:#fb7299;color:#fff;border-radius:.04706rem;text-decoration:none;font-size:.16471rem;transition:background-color .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn.youtube{background-color:#f03}.card-container-video .card-item-video .card-cover-content .card-cover-btn.bilibili{background-color:#ff85ad}.mobile .card-item-video{width:40%}.mobile .card-desc-video{font-size:.29412rem}.directory-links-container{display:flex;flex-direction:column}.directory-links-item{page-break-inside:avoid;-moz-column-break-inside:avoid;break-inside:avoid;margin:.11765rem;padding:.17647rem;border-radius:.05882rem;box-shadow:0 0 .05882rem rgba(0,0,0,.1)}.directory-links-body{display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(3.52941rem,1fr));position:relative}.directory-links-item h3{margin-top:0;margin-bottom:.11765rem}.directory-links-item ul{list-style-type:none;padding:0;margin:.18824rem .11765rem}.directory-links-item ul li{margin-bottom:.05882rem}.directory-links-item ul li a{text-decoration:none;color:#333}.directory-links-item ul li a:hover{text-decoration:underline;color:#238dfb}.header-nav .dropdown-icon-wrapper,.pc .nav-dropdown .dropdown-content-right,.pc .nav-dropdown .dropdown-image .image-button{display:flex;justify-content:center;align-items:center}.pc .header-nav-ul .header-nav-item a:hover{color:#0064c2}.mobile .mobile-nav-icon,.mobile .mobile-return-icon{background-repeat:no-repeat;background-size:100% 100%}header{width:100%;position:relative;background-color:#fff;border-bottom:.01176rem solid #e5e5e5;overflow:visible}.header-container{position:relative;margin:0 auto;padding:0 1.17647rem 0 0;width:15.64706rem;height:.70588rem;display:flex;align-items:center;justify-content:flex-end;font-size:.25882rem}.header-container .logo{position:absolute;left:.08235rem;display:block;width:2.08235rem;height:.41176rem;font-size:0;line-height:1;cursor:pointer}.header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.header-nav .dropdown-icon-wrapper{margin-right:.18824rem;width:.25882rem;height:.25882rem}.header-nav .dropdown-icon-wrapper .dropdown-icon{width:auto;height:auto;max-width:100%;max-height:100%;font-size:0}.language-option-box{position:absolute;height:.70588rem;right:-.65882rem;font-size:0;background-color:#fff}.language-option-box .icon{margin-right:.07059rem;width:.2rem;height:auto;color:#434343}.language-option-box .current-language{height:calc(100% - .02353rem);color:#434343;font-size:.22353rem;font-weight:700;display:flex;align-items:center;cursor:pointer;box-sizing:content-box}.language-option-box .language-dropdown-wrapper{display:none;position:fixed;top:.70588rem;padding-top:.11765rem;box-sizing:border-box;width:19.76471rem;left:50%;transform:translateX(-50%);z-index:99999}.language-option-box .language-dropdown-wrapper .language-dropdown{position:absolute;top:.11765rem;right:1.29412rem;width:1.52941rem;color:#434343;background-color:#fff;border-radius:.11765rem;overflow:hidden;box-shadow:0 .09412rem .28235rem rgba(0,0,0,.08);opacity:0;transition:opacity .2s ease}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item{font-size:.21176rem;font-weight:700;line-height:.54118rem;text-align:center;cursor:pointer}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item:hover{color:#0064c2}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item.active{background-color:#dedede}.language-option-box:hover .current-language{border-bottom:.03529rem solid #0064c2}.language-option-box:hover .current-language .header-arrow-btn{transform:rotate(-180deg)}.language-option-box:hover .language-dropdown-wrapper{display:block}.language-option-box:hover .language-dropdown{opacity:1}.disabledHover{cursor:auto!important}.disabledHover a:hover,.disabledHover li:hover,.disabledHover:hover{color:#434343!important}.pc .show-mb{display:none}.pc .header-nav{height:100%;display:flex;align-items:center}.pc .header-nav-ul{height:100%;display:flex;flex-direction:row}.pc .header-nav-ul .header-nav-item{margin-right:.30588rem;padding-left:.23529rem;height:calc(100% - .02353rem);display:flex;align-items:center;font-size:.22353rem;font-weight:700;color:#434343;cursor:pointer;box-sizing:content-box}.pc .header-nav-ul .header-nav-item.active,.pc .header-nav-ul .header-nav-item:hover{border-bottom:.03529rem solid #0064c2}.pc .header-nav-ul .header-nav-item.active .header-arrow-btn,.pc .header-nav-ul .header-nav-item:hover .header-arrow-btn{transform:rotate(-180deg)}.pc .header-nav-ul .header-nav-item:last-of-type{margin-right:0}.pc .header-nav-ul .header-nav-item a{position:relative;color:#434343}.pc .header-arrow-btn{margin-left:.07059rem;width:.11765rem;height:auto;color:#3a3a3a;font-size:0;transition:all .3s ease}.pc .nav-dropdown{position:fixed;left:50%;width:16.70588rem;max-width:calc(100vw - .47059rem);height:3.52941rem;display:flex;transform:translateX(-50%);background-color:#fff;border-radius:.23529rem;z-index:9999}.pc .nav-dropdown .dropdown-content-left{position:relative;padding:.47059rem .32941rem 0;width:calc(100% - 7.45882rem);height:100%;display:flex;justify-content:space-around}.pc .nav-dropdown .dropdown-content-right{width:7.45882rem;height:100%;background-color:#eee;border-radius:0 .23529rem .23529rem 0}.pc .nav-dropdown .dropdown-image{position:relative;width:7.05882rem;border-radius:.23529rem;font-size:0;overflow:hidden}.pc .nav-dropdown .dropdown-image img{width:100%;height:auto}.pc .nav-dropdown .dropdown-image .image-button{position:absolute;left:50%;bottom:.35294rem;transform:translateX(-50%);width:2.35294rem;height:.42353rem;font-size:.18824rem;color:#fff;background-color:#0064c2;border-radius:.04706rem}.pc .nav-dropdown .dropdown-image .image-button:hover{background-color:#058ce6}.pc .nav-dropdown .dropdown-image .image-button .image-icon{margin-right:.11765rem;width:.24706rem;height:auto}.pc .nav-dropdown .dropdown-item{width:3.29412rem;display:flex;flex-direction:column;flex-wrap:wrap}.pc .nav-dropdown .dropdown-item-li{padding-left:.16471rem;display:flex;align-items:center;font-size:.23529rem;font-weight:700;line-height:.70588rem;color:#434343}.pc .nav-dropdown .dropdown-item-li.border{border-bottom:.02353rem solid #dbdbdb}.pc .nav-dropdown .dropdown-item-li:hover{color:#0064c2}.pc .nav-dropdown .dropdown-item-child{margin-top:.18824rem;padding-left:.18824rem;display:flex;flex-direction:column}.pc .nav-dropdown .dropdown-child-li{margin-bottom:.14118rem;display:flex;align-items:center;font-size:.21176rem;font-weight:500;white-space:nowrap;color:#434343}.pc .nav-dropdown .dropdown-child-li:hover{color:#0064c2}.pc header #store{height:4.70588rem}.pc header #store .dropdown-item:first-child{width:2.21176rem}.pc header #store .dropdown-item:first-child .dropdown-child-li:nth-child(2) .dropdown-icon-wrapper{height:.32941rem}.pc header #store .dropdown-item:nth-child(2){width:4.65882rem;height:3.05882rem;border-bottom:.02353rem solid #dbdbdb}.pc header #store .dropdown-item:nth-child(2) .dropdown-item-child{width:90%;height:2rem;flex-wrap:wrap}.pc header #store .dropdown-item:nth-child(3),.pc header #store .dropdown-item:nth-child(4){position:absolute;bottom:.47059rem}.pc header #store .dropdown-item:nth-child(3){right:3.38824rem;width:2.04706rem}.pc header #store .dropdown-item:nth-child(3) .dropdown-icon-wrapper{margin-right:.14118rem;width:.32941rem}.pc header #store .dropdown-item:nth-child(4){right:.75294rem;width:2.58824rem}.pc header #software{height:4rem}.pc header #software .dropdown-content-left{width:calc(100% - 6.03529rem)}.pc header #software .dropdown-content-right{width:6.03529rem}.pc header #software .dropdown-image{width:5.58824rem}.pc header #software .dropdown-item:first-child{width:3.17647rem}.pc header #software .dropdown-item:nth-child(2){width:2.82353rem}.pc header #software .dropdown-item:nth-child(3){width:2.91765rem}.pc header #document{height:4.47059rem}.pc header #document .dropdown-content-left{width:100%}.pc header #document .dropdown-item:first-child .dropdown-item-child,.pc header #document .dropdown-item:nth-child(2) .dropdown-item-child{height:2rem;flex-wrap:wrap}.pc header #document .dropdown-item:first-child{width:4.65882rem}.pc header #document .dropdown-item:nth-child(2){width:5.01176rem}.pc header #document .dropdown-item:nth-child(3){width:3.76471rem}.pc header #aboutus{height:4.21176rem}.pc header #contact{height:1.05882rem;background-color:transparent}.pc header #contact .dropdown-content-left{position:absolute;padding:.09412rem 0;right:1.29412rem;width:2rem;height:1.05882rem;flex-direction:column;background-color:#fff;border-radius:.11765rem}.pc header #contact .dropdown-item{width:100%}.pc header #contact .dropdown-item .dropdown-item-li{padding-left:0;width:100%;justify-content:center;font-size:.21176rem;line-height:.42353rem}.mobile .show-pc,.mobile .snize-sticky-searchbox{display:none}.mobile header{height:1.10588rem;border-bottom:unset}.mobile .header-container{padding:0 .35294rem;width:100%;max-width:100%;height:1.10588rem;justify-content:unset;z-index:9999;box-shadow:0 0 .18824rem 0 hsla(0,0%,51.4%,.15)}.mobile .header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.mobile .mobile-nav-icon{width:.54118rem;height:.54118rem;background-image:url(/assets/menu.png);transition:all .28s ease}.mobile .mobile-nav-icon.active{transform:rotate(90deg)}.mobile .mobile-return-icon{position:absolute;left:1.2rem;width:.32941rem;height:.32941rem;background-image:url(/assets/return.png)}.mobile .logo{left:50%;width:2.47059rem;height:.48235rem;transform:translateX(-50%)}.mobile .header-nav{display:none;position:absolute;top:1.10588rem;left:0;padding:.18824rem 0 1.01176rem;width:5.17647rem;max-width:100%;background-color:#fff;z-index:9998}.mobile .header-nav.show{display:block}.mobile .header-nav-ul{margin-bottom:.23529rem}.mobile .header-nav-ul .header-nav-item{position:relative;padding-left:.47059rem;height:1.10588rem;font-size:.36471rem;font-weight:400;line-height:1.10588rem}.mobile .header-nav-ul .header-nav-item,.mobile .header-nav-ul .header-nav-item a{color:#434343}.mobile .header-nav-ul .header-nav-item.selected{background-color:#f7f7f7}.mobile .header-nav-ul .header-nav-item.active .header-mbnav-btn{transform:rotate(90deg)}.mobile .header-nav-ul .header-nav-item.active+.nav-dropdown{display:block}.mobile .header-mbnav-btn{position:absolute;width:.58824rem;height:.58824rem;top:.23529rem;right:.23529rem;background-image:url(/assets/arrow3.png);background-repeat:no-repeat;background-size:50% 50%;background-position:50%}.mobile .nav-dropdown{display:none;position:relative}.mobile .nav-dropdown .dropdown-content-left{width:100%}.mobile .nav-dropdown .dropdown-icon-wrapper{width:.47059rem;height:.47059rem}.mobile .nav-dropdown .dropdown-item-li{padding-left:.71765rem;width:100%;height:.88235rem;display:flex;align-items:center;font-size:.32941rem;font-weight:400;color:#434343}.mobile .nav-dropdown .dropdown-child-li{padding-left:.89412rem;width:100%;height:.82353rem;display:flex;align-items:center;font-size:.30588rem;line-height:.82353rem;white-space:nowrap;color:#434343}.mobile .language-option-box{height:1.10588rem;right:.25882rem}.mobile .language-option-box .icon{width:.35294rem}.mobile .language-option-box .current-language{font-size:.30588rem;font-weight:500}.mobile .language-option-box .language-dropdown-wrapper{width:100%;top:1.10588rem;padding-top:.11765rem;box-sizing:border-box}.mobile .language-option-box .language-dropdown{right:.11765rem;width:2.23529rem}.mobile .language-option-box .language-dropdown .language-item{font-size:.35294rem;font-weight:500;line-height:.70588rem}.header-nav-dd-pc-enter-active,.header-nav-dd-pc-leave-active{transition:opacity .2s ease-out,transform .22s cubic-bezier(.4,0,.2,1)}.header-nav-dd-pc-enter,.header-nav-dd-pc-leave-to{opacity:0;transform:translateX(-50%) translateY(-.09412rem)!important}.header-nav-dd-pc-enter-to,.header-nav-dd-pc-leave{opacity:1;transform:translateX(-50%) translateY(0)!important}.header-nav-dd-mb-enter-active,.header-nav-dd-mb-leave-active{transition:opacity .18s ease-out}.header-nav-dd-mb-enter,.header-nav-dd-mb-leave-to{opacity:0}.viewer-open .mobile .header-container,.viewer-open .mobile .language-dropdown-wrapper,.viewer-open .mobile .language-option-box{z-index:1!important}.viewer-open .mobile .language-option-box{pointer-events:none}.title-level2{height:.32941rem;font-size:.35294rem;font-weight:400;color:#434343;line-height:.32941rem;padding-left:.22353rem;position:relative;display:flex;justify-content:space-between;margin:.58824rem 0}.title-level2 .title-level2-desc{font-size:.18824rem;font-weight:400}.title-level2:after{content:"";width:.04706rem;height:.35294rem;background:#0064c2;position:absolute;left:0}.title-level3{height:.27059rem;font-size:.29412rem;font-weight:400;color:#434343;line-height:.27059rem;padding-left:.14118rem;position:relative;display:flex;justify-content:space-between;margin:.47059rem 0 .35294rem}.title-level3 .title-level3-desc{font-size:.14118rem;font-weight:400}.pc .product-list-container .Products{display:flex;flex-wrap:wrap;margin-bottom:.70588rem}.pc .product-list-container .ProductItem{border-top:.01176rem solid #e5e5e5;border-bottom:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(2n),.pc .product-list-container .ProductItem:nth-child(2n-1){border-right:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(3n){border-right:0 solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(n+4){border-top:0 solid #e5e5e5}.pc .product-list-container .ProductItem{height:4.51765rem;width:4.65882rem;text-align:center;position:relative}.pc .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.pc .product-list-container .ProductItem .ProductPic{text-align:center;width:2.35294rem;height:2.35294rem}.pc .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.pc .product-list-container .ProductItem .ProductName{margin-top:.11765rem;line-height:.29412rem;height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343}.pc .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto .17647rem;width:2.47059rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.23529rem;text-overflow:clip;overflow:hidden}.pc .product-list-container .ProductItem .product-btn-group{width:1.76471rem;height:.35294rem;border-radius:.17647rem;margin:auto;display:flex}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.29412rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.35294rem;font-size:.18824rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.47059rem;height:.35294rem;background-size:.23529rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.pc .product-list-container .ProductLinks{padding:0 .17647rem;font-size:.18824rem;display:grid;justify-content:start;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(2.82353rem,1fr));position:relative;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink:hover{color:#409eff;-webkit-text-decoration-line:underline;text-decoration-line:underline}.mobile .product-list-container{text-align:left}.mobile .product-list-container .ProductItem{text-align:center;height:5.17647rem;width:50%;border:.02353rem solid #e5e5e5;background-color:#fff;position:relative}.mobile .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.mobile .product-list-container .ProductItem .ProductPic{margin:.11765rem auto;text-align:center;width:2.82353rem;height:2.82353rem}.mobile .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.mobile .product-list-container .ProductItem .ProductName{height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343;line-height:.28235rem}.mobile .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto;display:block;width:2.36471rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.25882rem;overflow:hidden}.mobile .product-list-container .ProductItem .product-btn-group{width:2.35294rem;height:.47059rem;border-radius:.17647rem;margin:auto;display:flex}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.64706rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.47059rem;font-size:.23529rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.70588rem;height:.47059rem;background-size:.29412rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.mobile .product-list-container .ProductLinks{padding:.11765rem .17647rem;font-size:.25882rem;display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fit,minmax(3.52941rem,1fr));position:relative;margin-bottom:.14118rem;background-color:#fff}.mobile .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.14118rem}.product-list-container.hideEol .ProductItem.EOL{display:none}.footer-email-input input::-webkit-input-placeholder{font-family:Microsoft YaHei,sans-serif}.subscribe-btn{display:flex;justify-content:center;align-items:center}.pc .footer-bottom-content a:hover,.pc .footer-nav-li a:hover{color:#0064c2}.subscribe-btn:hover{background-color:#0074e1}.mobile .footer-nav-btn{background-repeat:no-repeat;background-size:100% 100%}.footer-container{width:100%;color:#fff;background-color:#000}.footer-content-wrap{height:100%;display:flex;align-items:center}.footer-email-title,.footer-qrcode-title{font-size:.32941rem;margin-bottom:.21176rem;font-weight:500;color:#fff}.footer-email-desc{font-weight:400;color:#f1f1f1}.footer-email-input{display:flex}.footer-email-input input{background:hsla(0,0%,60%,.55);border:.01176rem solid #0077c8;border-radius:.04706rem;padding:0 .23529rem;color:#fff;outline:0}.footer-email-input input::-webkit-input-placeholder{font-weight:400;color:#a0a0a0}.subscribe-btn{background:#0077c8;width:1.55294rem;height:.56471rem;font-size:.21176rem;font-weight:500;color:#fff;border-radius:.07059rem}.footer-follow{margin-top:.42353rem;width:90%}.footer-follow-ul{display:flex;flex-wrap:wrap}.footer-info-wrapper{margin-top:.47059rem;font-size:.16471rem;color:#a0a0a0}.footer-email-warning{margin-top:.11765rem;display:none;font-size:.18824rem;color:#ff2529}.footer-email-success{margin-top:.35294rem;margin-bottom:1.15294rem;display:none;font-size:.35294rem;color:#fff}.pc .footer-container{height:8.23529rem}.pc .footer-content-wrap{width:15.64706rem;margin:0 auto}.pc .footer-nav{padding:.70588rem 0 .11765rem;width:65%;height:100%;display:flex;flex-direction:column;flex-wrap:wrap}.pc .footer-nav-item{margin:0 0 .47059rem}.pc .footer-nav-title{margin-bottom:.18824rem;font-size:.29412rem;font-weight:500;color:#fff}.pc .footer-nav-title a{color:#fff}.pc .footer-nav-li{font-size:.21176rem;font-weight:400;color:#a0a0a0;line-height:.38824rem}.pc .footer-nav-li a{color:#a0a0a0;cursor:pointer}.pc .footer-right{width:35%;height:5.95294rem;padding:0 0 0 .47059rem}.pc .footer-email-title,.pc .footer-qrcode-title{margin-top:.14118rem}.pc .footer-email-desc{font-size:.21176rem;line-height:.32941rem;margin-bottom:.14118rem}.pc .footer-email-input input{width:3.71765rem;height:.56471rem;font-size:.21176rem;margin-right:.12941rem}.pc .footer-email-input input::-webkit-input-placeholder{font-size:.21176rem}.pc .footer-qrcode-list{display:flex}.pc .footer-qrcode-list .footer-qrcode-item{margin-right:.11765rem}.pc .footer-qrcode-list .footer-qrcode-img{width:1.88235rem;height:auto}.pc .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.pc .footer-qrcode-list .footer-qrcode-name{font-size:.21176rem;color:#a0a0a0}.pc .footer-follow-ul{width:100%}.pc .footer-follow-ul a{display:block;margin-right:.11765rem;margin-bottom:.11765rem;font-size:0}.pc .footer-follow-ul img{width:.58824rem;height:.58824rem}.pc .footer-address-info{line-height:.23529rem;margin:.05882rem 0}.pc .footer-info{line-height:.32941rem}.pc .footer-bottom{width:100%;height:.77647rem;background-color:#000}.pc .footer-bottom-content{margin:0 auto;padding:.23529rem .23529rem 0;width:16.07059rem;height:100%;display:flex;justify-content:space-between;font-size:.15294rem;font-weight:400;color:#a0a0a0;border-top:.01176rem solid #6d6d6d}.pc .footer-bottom-content a{display:inline-block;color:#a0a0a0;font-weight:400;font-size:.15294rem}.pc .terms-box{margin-left:.54118rem;display:flex}.pc .terms-box a{margin:0 .09412rem}.mobile .footer-container{height:11.76471rem}.mobile .footer-right{padding:0;width:100%}.mobile .footer-email-group,.mobile .footer-right{display:flex;flex-direction:column;align-items:center}.mobile .footer-email-title,.mobile .footer-qrcode-title{font-size:.58824rem;margin-bottom:.25882rem}.mobile .footer-email-success{font-size:.51765rem;margin-top:1.17647rem;margin-bottom:1.27059rem}.mobile .footer-email-desc{width:5.52941rem;font-size:.35294rem;line-height:.47059rem;text-align:center;margin-bottom:.75294rem}.mobile .footer-email-input{flex-direction:column;align-items:center}.mobile .footer-email-input input{width:7.35294rem;height:.70588rem;margin-bottom:.47059rem;font-size:.32941rem}.mobile .footer-email-input input::-webkit-input-placeholder{font-size:.32941rem}.mobile .subscribe-btn{width:2.75294rem;height:.70588rem;border-radius:.07059rem;font-size:.32941rem}.mobile .footer-email-warning{font-size:.29412rem;margin-top:.18824rem}.mobile .footer-qrcode-title{text-align:center}.mobile .footer-qrcode-list{display:flex}.mobile .footer-qrcode-list .footer-qrcode-item{margin-right:.35294rem}.mobile .footer-qrcode-list .footer-qrcode-img{width:3.05882rem;height:auto}.mobile .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.mobile .footer-qrcode-list .footer-qrcode-name{margin-top:.11765rem;font-size:.35294rem;color:#a0a0a0;text-align:center}.mobile .footer-follow{margin-top:.82353rem;width:100%}.mobile .footer-follow-ul{width:80%;margin:0 auto;justify-content:center}.mobile .footer-follow-ul a{margin-right:.23529rem}.mobile .footer-follow-ul a:nth-child(5){margin-right:0}.mobile .footer-follow-ul img{width:1.05882rem;height:1.05882rem}.mobile .footer-qrcode-img{width:2.82353rem;height:2.82353rem;margin:0 auto}.mobile .footer-qrcode-img img{width:100%;height:auto;max-height:100%}.mobile .footer-info-wrapper{width:95%;margin-top:.47059rem;font-size:.23529rem;text-align:center}.mobile .footer-address-info{line-height:.35294rem;margin:.05882rem 0}.mobile .footer-info{line-height:.44706rem}.mobile .footer-bottom{display:none}.mobile .footer-nav{background-color:#fff;border-top:.03529rem solid #eee}.mobile .footer-nav-item:nth-child(3) .footer-nav-title a{display:block}.mobile .footer-nav-title{position:relative;padding:0 0 0 .71765rem;font-size:.36471rem;line-height:1.10588rem;font-weight:500;color:#a6a6a6;height:1.10588rem;border-bottom:.03529rem solid #eee}.mobile .footer-nav-title a{color:#a6a6a6}.mobile .footer-nav-title.active .footer-nav-btn{transform:rotate(90deg)}.mobile .footer-nav-title.active+.footer-nav-ul{display:block}.mobile .footer-nav-btn{position:absolute;width:.2rem;height:.36471rem;top:.35294rem;right:.41176rem;background-image:url(/assets/arrow2.png)}.mobile .footer-nav-ul{display:none;border-bottom:.03529rem solid #eee}.mobile .footer-nav-li{font-size:.25882rem;font-weight:400;color:#a0a0a0;line-height:.65882rem;padding:0 0 0 .91765rem}.mobile .footer-nav-li a{color:#a0a0a0}.product-demo-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(2rem,1fr));grid-gap:.16471rem;gap:.16471rem;margin:.21176rem 0 .32941rem}.product-demo-item{display:flex;flex-direction:column;align-items:center;justify-content:flex-start;text-decoration:none;color:#1f2937;background:#fff;border:.01176rem solid #e5e7eb;border-radius:.14118rem;overflow:hidden;transition:transform .2s ease,border-color .2s ease;height:100%}.product-demo-item:hover{transform:translateY(-.03529rem);border-color:#93c5fd}.product-demo-item img{width:100%;height:1.41176rem;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;display:block;background:#f8fafc;box-shadow:none!important;flex-shrink:0}.product-demo-item span{display:block;width:100%;padding:.11765rem;font-size:.15294rem;line-height:1.4;font-weight:600;margin-top:auto;text-align:center}.scene-application-card{position:relative;display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.12fr);align-items:stretch;min-height:4rem;color:#0f172a;text-decoration:none;border-radius:.23529rem;overflow:hidden;background-color:#f8fafc;border:none;box-shadow:0 .21176rem .47059rem rgba(15,23,42,.1);border:.01176rem solid rgba(148,163,184,.22)}.scene-application-card--scene1{background-image:linear-gradient(180deg,rgba(15,23,42,.08),rgba(15,23,42,.56)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:50%}.scene-application-card--scene2{background-image:linear-gradient(180deg,rgba(15,23,42,.1),rgba(15,23,42,.58)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:64%}.scene-application-card:hover{color:#0f172a}.scene-application-card,.scene-application-card .scene-application-card__title,.scene-application-card p,.scene-application-card span:not(.scene-application-card__button){color:#0f172a!important}.scene-application-card__media{position:relative;display:flex;align-items:center;justify-content:center;min-height:100%;overflow:hidden;padding:.18824rem .21176rem .18824rem .14118rem;line-height:0}.scene-application-card__media img{flex:none;width:88%;max-width:4.94118rem;max-width:100%;height:auto;max-height:100%;display:block;margin:0!important;padding:0!important;border:.01176rem solid rgba(148,163,184,.34);border-radius:.16471rem;box-shadow:0 .11765rem .28235rem rgba(15,23,42,.16);vertical-align:top;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center}.scene-application-card__content{position:relative;z-index:1;display:flex;flex-direction:column;justify-content:center;grid-row-gap:.14118rem;row-gap:.14118rem;width:100%;max-width:5.17647rem;min-height:100%;padding:.32941rem .30588rem .28235rem;background:linear-gradient(180deg,hsla(0,0%,100%,.96),rgba(248,250,252,.9))}.scene-application-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-gap:.21176rem;gap:.21176rem;margin:.21176rem 0 .32941rem}.scene-application-card__title{margin:.09412rem 0 0;font-size:.32941rem;line-height:1.15;font-weight:700;text-align:center;color:#0f172a!important;text-shadow:none}.scene-application-card__desc{margin:0;font-size:.17647rem;line-height:1.6;text-align:center;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden;text-overflow:ellipsis;color:rgba(30,41,59,.9)!important;text-shadow:none}.scene-application-card__button{display:inline-flex;align-items:center;justify-content:center;align-self:center;margin-top:0;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content;min-width:1.22353rem;padding:.11765rem .18824rem;font-size:.16471rem;line-height:1;font-weight:600;white-space:nowrap;color:#fff!important;background:#2563eb;border-radius:11.75294rem;box-shadow:0 .09412rem .21176rem rgba(37,99,235,.28)}.scene-application-card .scene-application-card__button{color:#fff!important}.mobile .product-demo-grid{grid-template-columns:repeat(3,minmax(0,1fr));grid-gap:.09412rem;gap:.09412rem}.mobile .product-demo-item{border-radius:.09412rem}.mobile .product-demo-item img{height:auto;aspect-ratio:1/1;-o-object-fit:contain;object-fit:contain;-o-object-position:center;object-position:center;padding:.09412rem;box-shadow:none!important}.mobile .product-demo-item span{padding:.07059rem .07059rem .09412rem;font-size:.21176rem;line-height:1.4;text-align:center;word-break:break-word}.mobile .scene-application-card{grid-template-columns:1fr;grid-template-rows:2.35294rem minmax(0,1fr);min-height:4.58824rem;margin:0;border-radius:.16471rem}.mobile .scene-application-card__media{order:1;min-height:2.35294rem;padding:.11765rem .14118rem}.mobile .scene-application-card__media img{width:100%;max-width:none;max-height:none}.mobile .scene-application-grid{grid-template-columns:1fr;grid-gap:.16471rem;gap:.16471rem}.mobile .scene-application-card__content{order:2;max-width:none;justify-content:center;padding:.23529rem .21176rem;background:linear-gradient(180deg,hsla(0,0%,100%,.97),rgba(248,250,252,.93));grid-row-gap:.11765rem;row-gap:.11765rem}.mobile .scene-application-card__title{font-size:.25882rem;line-height:1.2;margin-top:.07059rem}.mobile .scene-application-card__desc{font-size:.15294rem;line-height:1.5;-webkit-line-clamp:4}.mobile .scene-application-card__button{min-width:1.17647rem;margin-top:.09412rem;padding:.10588rem .16471rem;font-size:.15294rem}.project-item{display:flex;height:1.96471rem;margin:.11765rem 0}.project-item .project-img{width:1.96471rem;height:1.96471rem;position:relative;overflow:hidden;text-align:center}.project-item .project-img img{height:100%;font-size:.09412rem}.project-item .project-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.project-item .project-contents{flex:1;background-color:#efefef;padding:0 .38824rem;position:relative;display:flex;flex-direction:column;justify-content:center}.project-item .project-contents .project-title{font-size:.25882rem;font-weight:700;line-height:.27059rem}.project-item .project-contents .project-title a{color:#238dfb}.project-item .project-contents .project-desc{margin-top:.15294rem;font-size:.22353rem;font-weight:400;color:#717171;line-height:.29412rem}.saerch-fliter-container{height:1.17647rem;border-bottom:.04706rem dashed #e5e5e5;display:flex}.saerch-fliter-container .search-fliter-title{font-size:.21176rem;font-weight:400;color:#434343;width:1.50588rem;margin-right:.58824rem}.saerch-fliter-container .search-fliter-options{flex:1;display:flex;flex-wrap:wrap}.saerch-fliter-container .search-fliter-options .fliter-option{font-size:.18824rem;font-weight:400;color:#959595;padding:0 .35294rem 0 0;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.saerch-fliter-container .search-fliter-options .fliter-option.active{color:#0064c2}.mobile .saerch-fliter-container{height:2.82353rem;margin-top:.35294rem}.dev-layout{flex-wrap:wrap;justify-content:space-between;margin-bottom:.70588rem;flex-direction:column}.dev-container,.dev-layout{display:flex;width:100%}.mobile .dev-container{flex-direction:column;min-height:60vh}.dev-info-container{margin:.70588rem .23529rem;display:flex;color:#5f5d5d;width:3.52941rem;overflow:hidden;flex-direction:column}.dev-info-container .dev-contents{display:flex;flex-direction:column;align-items:center;text-align:center}.dev-info-container .dev-title{font-size:.47059rem;padding:.35294rem}.dev-info-container .dev-desc{font-size:.18824rem;padding:.35294rem;line-height:.28235rem;font-weight:300;height:1.17647rem}.dev-info-container .dev-button{width:1.64706rem;height:.47059rem;background:#0064c2;border-radius:.05882rem;color:#fff;text-align:center}.dev-info-container .dev-banner{padding:.05882rem;overflow:hidden;border-radius:.11765rem}.dev-info-container .dev-banner img{box-shadow:0 0 .23529rem 0 #efefef;background-size:cover;width:5.29412rem;transition:all .25s ease;border-radius:.11765rem}.dev-info-container .dev-banner img:hover{transform:scale(1.1)}.mobile .dev-info-container{width:100%;flex-direction:row}@-webkit-keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@-webkit-keyframes fade-in{0%{opacity:0}to{opacity:1}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}@-webkit-keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}@keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}.float-icon-container{position:fixed;right:23PX;bottom:80PX;z-index:6;height:120PX;width:50PX}.float-icon-container .totop-icon{position:absolute;top:0;left:0}.float-icon-container .menu-icon{position:absolute;top:70PX;left:0}.float-icon-container .menu-icon.active,.float-icon-container .menu-icon.active:hover{background-color:#2f495e}.float-icon-container .menu-icon,.float-icon-container .totop-icon{width:50PX;height:50PX;display:flex;align-items:center;justify-content:center;border-radius:50%;background-color:#0870d1;box-shadow:0 0 .35294rem -.02353rem rgba(19,41,75,.14),0 .14118rem .15294rem -.02353rem rgba(19,41,75,.13),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.13),0 .02353rem .02353rem -.02353rem rgba(19,41,75,.12);cursor:pointer;z-index:200}.float-icon-container .menu-icon svg,.float-icon-container .totop-icon svg{width:50PX;height:50PX}.float-icon-container .menu-icon svg path,.float-icon-container .totop-icon svg path{fill:#fefefe}.float-icon-container .menu-icon:hover,.float-icon-container .totop-icon:hover{background-color:#058ce6}.markdown .hljs{color:#263445;background:0 0}.markdown .hljs-comment,.markdown .hljs-quote{color:#687789;font-style:normal}.markdown .hljs-addition,.markdown .hljs-keyword,.markdown .hljs-selector-tag{color:#b4233f;font-weight:500}.markdown .hljs-link,.markdown .hljs-literal,.markdown .hljs-number,.markdown .hljs-regexp{color:#1769aa}.markdown .hljs-doctag,.markdown .hljs-meta .hljs-meta-string,.markdown .hljs-string{color:#16705a}.markdown .hljs-name,.markdown .hljs-section,.markdown .hljs-selector-class,.markdown .hljs-selector-id,.markdown .hljs-title{color:#6f52a2}.markdown .hljs-attr,.markdown .hljs-attribute,.markdown .hljs-template-variable,.markdown .hljs-variable{color:#8a5a00}.markdown .hljs-built_in,.markdown .hljs-builtin-name,.markdown .hljs-class .hljs-title,.markdown .hljs-type{color:#9a4d16}.markdown .hljs-bullet,.markdown .hljs-meta,.markdown .hljs-meta .hljs-keyword,.markdown .hljs-selector-attr,.markdown .hljs-selector-pseudo,.markdown .hljs-subst,.markdown .hljs-symbol{color:#526579}.markdown .hljs-deletion{color:#b4233f}.markdown .hljs-formula{background:#eaf1f7}.markdown .hljs-emphasis{font-style:italic}.markdown .hljs-strong{font-weight:600}/*!
- * Viewer.js v1.11.6
- * https://fengyuanchen.github.io/viewerjs
- *
- * Copyright 2015-present Chen Fengyuan
- * Released under the MIT license
- *
- * Date: 2023-09-17T03:16:35.830Z
- */.viewer-close:before,.viewer-flip-horizontal:before,.viewer-flip-vertical:before,.viewer-fullscreen-exit:before,.viewer-fullscreen:before,.viewer-next:before,.viewer-one-to-one:before,.viewer-play:before,.viewer-prev:before,.viewer-reset:before,.viewer-rotate-left:before,.viewer-rotate-right:before,.viewer-zoom-in:before,.viewer-zoom-out:before{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAARgAAAAUCAYAAABWOyJDAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAALEgAACxIB0t1+/AAAABx0RVh0U29mdHdhcmUAQWRvYmUgRmlyZXdvcmtzIENTNui8sowAAAQPSURBVHic7Zs/iFxVFMa/0U2UaJGksUgnIVhYxVhpjDbZCBmLdAYECxsRFBTUamcXUiSNncgKQbSxsxH8gzAP3FU2jY0kKKJNiiiIghFlccnP4p3nPCdv3p9778vsLOcHB2bfveeb7955c3jvvNkBIMdxnD64a94GHMfZu3iBcRynN7zAOI7TG15gHCeeNUkr8zaxG2lbYDYsdgMbktBsP03jdQwljSXdtBhLOmtjowC9Mg9L+knSlcD8TNKpSA9lBpK2JF2VdDSR5n5J64m0qli399hNFMUlpshQii5jbXTbHGviB0nLNeNDSd9VO4A2UdB2fp+x0eCnaXxWXGA2X0au/3HgN9P4LFCjIANOJdrLr0zzZ+BEpNYDwKbpnQMeAw4m8HjQtM6Z9qa917zPQwFr3M5KgA6J5rTJCdFZJj9/lyvGhsDvwFNVuV2MhhjrK6b9bFiE+j1r87eBl4HDwCF7/U/k+ofAX5b/EXBv5JoLMuILzf3Ap6Z3EzgdqHMCuF7hcQf4HDgeoHnccncqdK/TvSDWffFXI/exICY/xZyqc6XLWF1UFZna4gJ7q8BsRvgd2/xXpo6P+D9dfT7PpECtA3cnWPM0GXGFZh/wgWltA+cDNC7X+AP4GzjZQe+k5dRxuYPeiuXU7e1qwLpDz7dFjXKRaSwuMLvAlG8zZlG+YmiK1HoFqT7wP2z+4Q45TfEGcMt01xLoNZEBTwRqD4BLpnMLeC1A41UmVxsXgXeBayV/Wx20rpTyrpnWRft7p6O/FdqzGrDukPNtkaMoMo3FBdBSQMOnYBCReyf05s126fU9ytfX98+mY54Kxnp7S9K3kj6U9KYdG0h6UdLbkh7poFXMfUnSOyVvL0h6VtIXHbS6nOP+s/Zm9mvyXW1uuC9ohZ72E9uDmXWLJOB1GxsH+DxPftsB8B6wlGDN02TAkxG6+4D3TWsbeC5CS8CDFce+AW500LhhOW2020TRjK3b21HEmgti9m0RonxbdMZeVzV+/4tF3cBpP7E9mKHNL5q8h5g0eYsCMQz0epq8gQrwMXAgcs0FGXGFRcB9wCemF9PkbYqM/Bas7fxLwNeJPdTdpo4itQti8lPMqTpXuozVRVXPpbHI3KkNTB1NfkL81j2mvhDp91HgV9MKuRIqrykj3WPq4rHyL+axj8/qGPmTqi6F9YDlHOvJU6oYcTsh/TYSzWmTE6JT19CtLTJt32D6CmHe0eQn1O8z5AXgT4sx4Vcu0/EQecMydB8z0hUWkTd2t4CrwNEePqMBcAR4mrBbwyXLPWJa8zrXmmLEhNBmfpkuY2102xxrih+pb+ieAb6vGhuA97UcJ5KR8gZ77K+99xxeYBzH6Q3/Z0fHcXrDC4zjOL3hBcZxnN74F+zlvXFWXF9PAAAAAElFTkSuQmCC);background-repeat:no-repeat;background-size:280px;color:transparent;display:block;font-size:0;height:20px;line-height:0;width:20px}.viewer-zoom-in:before{background-position:0 0;content:"Zoom In"}.viewer-zoom-out:before{background-position:-20px 0;content:"Zoom Out"}.viewer-one-to-one:before{background-position:-40px 0;content:"One to One"}.viewer-reset:before{background-position:-60px 0;content:"Reset"}.viewer-prev:before{background-position:-80px 0;content:"Previous"}.viewer-play:before{background-position:-100px 0;content:"Play"}.viewer-next:before{background-position:-120px 0;content:"Next"}.viewer-rotate-left:before{background-position:-140px 0;content:"Rotate Left"}.viewer-rotate-right:before{background-position:-160px 0;content:"Rotate Right"}.viewer-flip-horizontal:before{background-position:-180px 0;content:"Flip Horizontal"}.viewer-flip-vertical:before{background-position:-200px 0;content:"Flip Vertical"}.viewer-fullscreen:before{background-position:-220px 0;content:"Enter Full Screen"}.viewer-fullscreen-exit:before{background-position:-240px 0;content:"Exit Full Screen"}.viewer-close:before{background-position:-260px 0;content:"Close"}.viewer-container{bottom:0;direction:ltr;font-size:0;left:0;line-height:0;overflow:hidden;position:absolute;right:0;-webkit-tap-highlight-color:transparent;top:0;touch-action:none;-webkit-touch-callout:none;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.viewer-container ::-moz-selection,.viewer-container::-moz-selection{background-color:transparent}.viewer-container ::selection,.viewer-container::selection{background-color:transparent}.viewer-container:focus{outline:0}.viewer-container img{display:block;height:auto;max-height:none!important;max-width:none!important;min-height:0!important;min-width:0!important;width:100%}.viewer-canvas{bottom:0;left:0;overflow:hidden;position:absolute;right:0;top:0}.viewer-canvas>img{height:auto;margin:15px auto;max-width:90%!important;width:auto}.viewer-footer{bottom:0;left:0;overflow:hidden;position:absolute;right:0;text-align:center}.viewer-navbar{background-color:rgba(0,0,0,.5);overflow:hidden}.viewer-list{box-sizing:content-box;height:50px;margin:0;overflow:hidden;padding:1px 0}.viewer-list>li{color:transparent;cursor:pointer;float:left;font-size:0;height:50px;line-height:0;opacity:.5;overflow:hidden;transition:opacity .15s;width:30px}.viewer-list>li:focus,.viewer-list>li:hover{opacity:.75}.viewer-list>li:focus{outline:0}.viewer-list>li+li{margin-left:1px}.viewer-list>.viewer-loading{position:relative}.viewer-list>.viewer-loading:after{border-width:2px;height:20px;margin-left:-10px;margin-top:-10px;width:20px}.viewer-list>.viewer-active,.viewer-list>.viewer-active:focus,.viewer-list>.viewer-active:hover{opacity:1}.viewer-player{background-color:#000;bottom:0;cursor:none;display:none;right:0;z-index:1}.viewer-player,.viewer-player>img{left:0;position:absolute;top:0}.viewer-toolbar>ul{display:inline-block;margin:0 auto 5px;overflow:hidden;padding:6px 3px}.viewer-toolbar>ul>li{background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;float:left;height:24px;overflow:hidden;transition:background-color .15s;width:24px}.viewer-toolbar>ul>li:focus,.viewer-toolbar>ul>li:hover{background-color:rgba(0,0,0,.8)}.viewer-toolbar>ul>li:focus{box-shadow:0 0 3px #fff;outline:0;position:relative;z-index:1}.viewer-toolbar>ul>li:before{margin:2px}.viewer-toolbar>ul>li+li{margin-left:1px}.viewer-toolbar>ul>.viewer-small{height:18px;margin-bottom:3px;margin-top:3px;width:18px}.viewer-toolbar>ul>.viewer-small:before{margin:-1px}.viewer-toolbar>ul>.viewer-large{height:30px;margin-bottom:-3px;margin-top:-3px;width:30px}.viewer-toolbar>ul>.viewer-large:before{margin:5px}.viewer-tooltip{background-color:rgba(0,0,0,.8);border-radius:10px;color:#fff;display:none;font-size:12px;height:20px;left:50%;line-height:20px;margin-left:-25px;margin-top:-10px;position:absolute;text-align:center;top:50%;width:50px}.viewer-title{color:#ccc;display:inline-block;font-size:12px;line-height:1.2;margin:5px 5%;max-width:90%;min-height:14px;opacity:.8;overflow:hidden;text-overflow:ellipsis;transition:opacity .15s;white-space:nowrap}.viewer-title:hover{opacity:1}.viewer-button{-webkit-app-region:no-drag;background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;height:80px;overflow:hidden;position:absolute;right:-40px;top:-40px;transition:background-color .15s;width:80px}.viewer-button:focus,.viewer-button:hover{background-color:rgba(0,0,0,.8)}.viewer-button:focus{box-shadow:0 0 3px #fff;outline:0}.viewer-button:before{bottom:15px;left:15px;position:absolute}.viewer-fixed{position:fixed}.viewer-open{overflow:hidden}.viewer-show{display:block}.viewer-hide{display:none}.viewer-backdrop{background-color:rgba(0,0,0,.5)}.viewer-invisible{visibility:hidden}.viewer-move{cursor:move;cursor:-webkit-grab;cursor:grab}.viewer-fade{opacity:0}.viewer-in{opacity:1}.viewer-transition{transition:all .3s}@-webkit-keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}.viewer-loading:after{-webkit-animation:viewer-spinner 1s linear infinite;animation:viewer-spinner 1s linear infinite;border:4px solid hsla(0,0%,100%,.1);border-left-color:hsla(0,0%,100%,.5);border-radius:50%;content:"";display:inline-block;height:40px;left:50%;margin-left:-20px;margin-top:-20px;position:absolute;top:50%;width:40px;z-index:1}@media (max-width:767px){.viewer-hide-xs-down{display:none}}@media (max-width:991px){.viewer-hide-sm-down{display:none}}@media (max-width:1199px){.viewer-hide-md-down{display:none}}.nuxt-progress{position:fixed;top:0;left:0;right:0;height:.02353rem;width:0;opacity:1;transition:width .1s,opacity .4s;background-color:#000;z-index:999999}.nuxt-progress.nuxt-progress-notransition{transition:none}.nuxt-progress-failed{background-color:red}.side-bar{width:2.47059rem;position:sticky;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.side-bar .side-bar-title{height:.82353rem;width:2.47059rem;background-image:url(/assets/sidebar-title.jpg);background-size:cover}.side-bar .side-bar-title p{height:.21176rem;font-size:.28235rem;font-weight:700;color:#fff;line-height:.82353rem;text-align:center}.side-bar .side-bar-contents{cursor:pointer;border-bottom:.02353rem solid #e5e5e5;border-left:.02353rem solid #e5e5e5;border-right:.02353rem solid #e5e5e5}.side-bar .side-bar-contents .side-bar-collapse{position:relative;height:.50588rem;overflow:hidden;transition:all .2s ease;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.side-bar .side-bar-contents .side-bar-collapse .collapse-title{font-size:.18824rem;font-weight:400;color:#434343;line-height:.50588rem;padding-left:.24706rem;border-top:.01176rem solid #edf1f4;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.side-bar .side-bar-contents .side-bar-collapse .collapse-title.active{color:#409eff}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn{position:absolute;height:.11765rem;width:.11765rem;box-shadow:.02353rem -.02353rem 0 #82a5d7;background-color:#fff;top:.2rem;right:.18824rem;transform:rotate(45deg);transition:all .25s ease}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn.collapse-btn-active{transform:translate(.04706rem,-.04706rem) rotate(135deg)}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents{border-bottom:.01176rem solid #edf1f4}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item{padding-left:.38824rem;line-height:.44706rem;color:#838383;font-size:.16471rem}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active{color:#409eff;background-color:#f6f7f8;position:relative}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active:after{content:" ";width:.04706rem;height:.04706rem;background:#82a5d7;border-radius:50%;position:absolute;top:50%;left:.17647rem;transform:translateY(-50%)}.page-header-container{margin-bottom:.35294rem;width:100%}.page-header-container .page-header-content{display:flex;align-content:center;position:relative}.page-header-container .page-header-content .page-header-arrow-icon{width:.28235rem;height:.32941rem;padding-top:.02353rem;color:#2f495e;font-size:.23529rem;transition:all .2s ease}.page-header-container .page-header-content .header-arrow-container{width:.17647rem;height:.17647rem;background-image:url(/assets/arrow3.png);background-size:cover}.page-header-container .page-header-content .page-header-arrow-icon:hover{color:#007bff}.page-header-container .page-header-content .page-header-item{color:#858585;font-size:.18824rem;font-weight:500;display:flex;height:.35294rem;line-height:.35294rem;cursor:pointer;align-items:center}.page-header-container .page-header-content .page-header-item .page-header-tag{margin:0 .09412rem;transition:all .2s ease}.page-header-container .page-header-content .page-header-item .page-header-tag.active{color:#2f495e}.page-header-container .page-header-content .page-header-item .page-header-tag:hover{color:#007bff}.mobile .page-header-container{margin-top:.35294rem}.search-box{display:flex;grid-gap:.11765rem;gap:.11765rem;margin-bottom:.28235rem;position:relative;align-items:center}.search-box input{flex:1;min-width:7.05882rem;height:.51765rem;background:#edf1f4;border-radius:.09412rem;border:.01176rem solid #d5dee8;padding:0 .18824rem;font-size:.17647rem;color:#253443;outline:0;z-index:3;transition:border-color .2s ease,box-shadow .2s ease}.search-box input:focus{border-color:#0064c2;box-shadow:0 0 0 .03529rem rgba(0,100,194,.12157)}.search-box .search-btn{width:1.55294rem;height:.51765rem;background:#0064c2;border-radius:.09412rem;border:none;cursor:pointer;transition:background-color .2s ease}.search-box .search-btn:hover{background:#0a5aaa}.search-box .search-btn p{margin:0;line-height:.51765rem;font-size:.18824rem;font-weight:700;color:#fff}.search-box .search-cover{position:fixed;top:0;left:0;right:0;bottom:0;z-index:2;background-color:rgba(25,25,25,.1098);-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem)}.search-result-container{overflow:hidden}.search-result-container::-webkit-scrollbar{width:.14118rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.search-result-container .el-tabs__item{display:table-cell;font-size:.21176rem;font-weight:600}.search-result-container .el-tabs__active-bar{height:.04706rem}.search-result-container{width:100%;min-height:4.47059rem;max-height:7.05882rem;overflow-y:auto;background-color:#fff;position:absolute;top:.63529rem;border:.01176rem solid #e2e8f0;border-radius:.11765rem;box-shadow:0 .11765rem .17647rem -.03529rem rgba(0,0,0,.10196),0 .04706rem .07059rem -.02353rem rgba(0,0,0,.05098);transition:all .25s ease;color:#2f495e;z-index:3;padding:.14118rem;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.search-result-container .search-title{height:.70588rem;font-size:.29412rem;padding:.17647rem;border-bottom:.01176rem solid #d9d9d9}.search-result-container .search-result-contents{display:flex;align-items:flex-start;grid-gap:.11765rem;gap:.11765rem;padding:.14118rem;border-bottom:.01176rem solid #edf2f7;position:relative}.search-result-container .search-result-contents svg{display:inline;font-size:.23529rem;color:#409eff;padding-right:.11765rem}.search-result-container .search-result-contents:hover{background-color:#f3f8fd}.search-result-container .search-result-content{flex:1;display:flex;flex-direction:column;justify-content:center;position:relative;transition:all .25s ease}.search-result-container .search-result-name{font-size:.18824rem;text-align:left;font-weight:700;color:#409eff;line-height:1.4}.search-result-container .search-result-sku{font-size:.16471rem;line-height:1.6;color:#5b5b5b;margin-top:.04706rem}.search-result-container .search-result-key{font-size:.18824rem;font-weight:700;color:#2f495e;margin-top:.04706rem}.search-result-container .search-result-key .search-result-highlight{color:#409eff}.search-result-container .search-result-key .search-result-key-tag{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#5b5b5b;padding:.02353rem .11765rem;border:.01176rem solid #5b5b5b;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container .search-result-key .search-result-key-tag.active{color:#409eff;border:.01176rem solid #409eff}.search-result-container .search-result-image{width:1.31765rem;height:1.31765rem;margin:0 .21176rem 0 .04706rem}.search-result-container .search-result-eol-tag{position:absolute;width:.41176rem;height:.41176rem;border-radius:50%;top:5%;left:.35294rem;background-color:#2f495e;color:#fff;font-size:.15294rem;font-weight:700;line-height:.41176rem;text-align:center}.search-result-container .search-result-recommand-box{margin-top:.14118rem}.search-result-container .search-result-recommand-box .search-result-recommand-item{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#409eff;padding:.04706rem .11765rem;border:.01176rem solid #409eff;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container:before{display:block;position:absolute;content:"";width:.16471rem;height:.16471rem;background:#fff;z-index:1000;top:-.08235rem;left:calc(50% - .08235rem);border-top:.01176rem solid #d9d9d9;border-right:.01176rem solid #d9d9d9;transform:rotate(-45deg);border-radius:.02353rem}.mobile .search-box{margin-bottom:.09412rem;width:100%;grid-gap:.09412rem;gap:.09412rem}.mobile .search-box input{height:.65882rem;font-size:.2rem}.mobile .search-box .search-btn{width:2.11765rem;height:.65882rem;background:#0064c2;border-radius:.09412rem}.mobile .search-box .search-btn p{margin:0;line-height:.65882rem;font-size:.21176rem;font-weight:700;color:#fff}.mobile .search-result-container{top:.75294rem}.search-result-container .tabs{display:flex;grid-gap:.07059rem;gap:.07059rem;width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .14118rem;padding:.09412rem .14118rem;border-radius:0;background:hsla(0,0%,100%,.9);border:0;border-bottom:.01176rem solid #e6edf5;-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem);position:sticky;top:-.14118rem;z-index:6}.search-result-container .tabs:after{content:"";position:absolute;left:0;right:0;top:0;bottom:0;background:0 0;z-index:-1}.search-result-container .tabs button{min-width:1.27059rem;padding:.10588rem .18824rem;border-radius:.11765rem;font-size:.16471rem;font-weight:600;color:#516578;background:hsla(0,0%,100%,.6);border:.01176rem solid #d7e3ef;line-height:1.2;overflow:hidden;transition:color .2s ease,background-color .2s ease,box-shadow .2s ease}.search-result-container .tabs button:first-child,.search-result-container .tabs button:last-child{border-radius:.11765rem}.search-result-container .tabs button:hover{color:#2f4f6f;background:#f8fbff;border-color:#cddded}.search-result-container .tabs button.active{color:#0f4f8e;background:#fff;border:.01176rem solid #c8d9eb;border-radius:.11765rem;box-shadow:0 .02353rem .09412rem rgba(0,100,194,.16078)}.search-result-container .tab-content{padding:.11765rem .09412rem .09412rem;background:0 0}.search-result-container .search-result-contents{border-radius:.09412rem;transition:background-color .2s ease,box-shadow .2s ease}.search-result-container .search-result-contents:hover{box-shadow:inset 0 0 0 .01176rem #dbe9f8}.search-result-contents-list{padding-bottom:.82353rem}.search-result-view-all-wrap{position:sticky;bottom:0;z-index:4;display:flex;justify-content:center;padding:.11765rem .09412rem .07059rem;background:linear-gradient(0deg,#fff 70%,hsla(0,0%,100%,0))}.search-result-view-all-btn{display:inline-block;min-width:2.82353rem;text-align:center;padding:.12941rem .21176rem;border-radius:.28235rem;background:#0064c2;color:#fff;font-size:.17647rem;font-weight:700;text-decoration:none;box-shadow:0 .04706rem .14118rem rgba(0,100,194,.25);transition:background-color .2s ease}.search-result-view-all-btn:hover{background:#0a5aaa}.mobile .search-result-container .tabs{width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .11765rem;padding:.09412rem .11765rem}.mobile .search-result-container .tabs button{flex:1;min-width:0;padding:.14118rem .11765rem;font-size:.17647rem}.mobile .search-result-container .tab-content{padding:.09412rem .04706rem .07059rem}.search-result-container.search-result-embedded{position:relative;top:auto;max-height:none;min-height:0;padding:0;box-shadow:none;-webkit-animation:none;animation:none}.search-result-container.search-result-embedded:before{display:none}.search-result-loading{padding:.09412rem .04706rem;display:flex;flex-direction:column}.search-result-loading-header{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;color:#516578;font-size:.16471rem;margin:0 0 .11765rem}.search-result-loading-text{min-width:0;font-size:.16471rem;font-weight:400;line-height:.23529rem}.search-result-loading-dot{width:.09412rem;height:.09412rem;border-radius:50%;background:#409eff;-webkit-animation:search-loading-pulse 1s ease-in-out infinite;animation:search-loading-pulse 1s ease-in-out infinite}.search-result-loading-list{display:flex;flex-direction:column;grid-gap:.11765rem;gap:.11765rem}.search-result-loading-item{padding:.14118rem;border-radius:.09412rem;border:.01176rem solid #edf2f7;background:#fbfdff}.search-result-loading-line{height:.11765rem;border-radius:11.75294rem;margin-bottom:.09412rem;background:linear-gradient(90deg,#e9f0f7 20%,#f5f9fd 45%,#e9f0f7 70%);background-size:2.82353rem 100%;-webkit-animation:search-loading-shimmer 1.1s linear infinite;animation:search-loading-shimmer 1.1s linear infinite}.search-result-loading-line.is-title{width:52%;height:.14118rem}.search-result-loading-line.is-short{width:36%;margin-bottom:0}@-webkit-keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@-webkit-keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}@keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}.search-result-loading-text[data-v-2b770079]{min-width:0;font-size:.16471rem!important;font-weight:400;line-height:.23529rem}.tab-panel{border:.01176rem solid #e5e5e5;padding:.09412rem;border-radius:.09412rem}.tabs{display:flex;grid-gap:.09412rem;gap:.09412rem;margin-bottom:.18824rem}.tabs button{padding:.11765rem .21176rem;border:none;border-bottom:.04706rem solid transparent;background:#f9f9f9;cursor:pointer;transition:.2s}.tabs button.active{border-color:#007bff;color:#007bff}.tab-content{padding:.18824rem;background:#fefefe;border-radius:.09412rem}.search-result-container .tab-panel{border:0}.carousel-container[data-v-6e07f87d]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-6e07f87d]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-6e07f87d]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-6e07f87d]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-6e07f87d]{flex-shrink:0;width:33.333%;text-align:center;cursor:pointer}.preview-image img[data-v-6e07f87d]{max-width:100%;height:auto;margin:0}.arrow[data-v-6e07f87d]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-6e07f87d]{left:0;transform:rotateY(180deg)}.arrow.right[data-v-6e07f87d]{right:0}.carousel-thumbnails[data-v-6e07f87d]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-6e07f87d]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-6e07f87d]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-6e07f87d]{width:100%;margin:0;height:auto}.clickable-area[data-v-6e07f87d]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-6e07f87d]{left:0}.clickable-area.right[data-v-6e07f87d]{right:0}.carousel-container[data-v-7d51a79c]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-7d51a79c]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-7d51a79c]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-7d51a79c]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-7d51a79c]{flex-shrink:0;width:100%;text-align:center;cursor:pointer}.preview-image img[data-v-7d51a79c]{width:100%;height:auto;margin:0}.arrow[data-v-7d51a79c]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-7d51a79c]{left:0;transform:translateY(-50%) rotateY(180deg)}.arrow.right[data-v-7d51a79c]{right:0;transform:translateY(-50%)}.carousel-thumbnails[data-v-7d51a79c]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-7d51a79c]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-7d51a79c]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-7d51a79c]{width:100%;margin:0;height:auto}.clickable-area[data-v-7d51a79c]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-7d51a79c]{left:0}.clickable-area.right[data-v-7d51a79c]{right:0}.corner-marker[data-v-7d51a79c]{position:absolute;bottom:.11765rem;left:.11765rem;background-color:rgba(0,0,0,.5);color:#fff;padding:.05882rem .11765rem;border-radius:.05882rem;z-index:2}.video-gallery-island[data-v-5e05839f]{min-width:0;width:100%}.page-tools[data-v-39baf185]{width:2.35294rem;margin-bottom:.16471rem;border:.01176rem solid #dfeaf5;border-radius:.11765rem;background:#f8fbfe;box-shadow:0 .07059rem .21176rem rgba(19,41,75,.08);overflow:visible}.page-tools-title[data-v-39baf185]{height:.4rem;line-height:.4rem;padding:0 .14118rem;border-bottom:.01176rem solid #e5eef7;color:#2f495e;font-size:.15294rem;font-weight:700}.page-tools-actions[data-v-39baf185]{display:flex;flex-direction:column;grid-gap:.09412rem;gap:.09412rem;padding:.11765rem;align-items:stretch}.page-tools-action[data-v-39baf185]{display:inline-flex;align-items:center;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;height:.43529rem;width:100%;padding:0 .11765rem;border:.01176rem solid #d6e5f3;border-radius:.08235rem;background:#fff;color:#238dfb;font-size:.15294rem;font-weight:700;transition:background-color .2s ease,border-color .2s ease,transform .2s ease}.page-tools-action .page-tools-icon[data-v-39baf185]{width:.21176rem;height:.21176rem;flex:0 0 auto;fill:currentColor;display:block}.page-tools-action[data-v-39baf185]:after{content:"";width:.08235rem;height:.08235rem;margin-left:auto;border-top:.02353rem solid;border-right:.02353rem solid;transform:rotate(45deg);opacity:.45}.page-tools-action[data-v-39baf185]:hover{background:#eaf4ff;border-color:#b9d8f4;transform:translateY(-.01176rem)}.page-tools.mobile[data-v-39baf185]{width:auto;margin:.09412rem 0 .18824rem;border:0;background:0 0;box-shadow:none}.page-tools.mobile .page-tools-actions[data-v-39baf185]{flex-direction:row;padding:0}.page-tools.mobile .page-tools-action[data-v-39baf185]{width:.63529rem;min-width:.63529rem;height:.42353rem;padding:0;background:#edf6ff;border-color:#b7d8f5;justify-content:center}.page-tools.mobile .page-tools-action[data-v-39baf185]:after{display:none}.markdown-action-menu[data-v-5d6a4f8a]{position:relative;display:flex;justify-content:flex-end;margin:-.14118rem 0 .21176rem;z-index:20}.markdown-action-trigger[data-v-5d6a4f8a]{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;height:.47059rem;padding:0 .16471rem;border:.01176rem solid #b9cfe5;border-radius:.07059rem;background:linear-gradient(135deg,#0064c2,#238dfb);color:#fff;font-size:.16471rem;font-weight:700;cursor:pointer;transition:background-color .2s ease,border-color .2s ease}.markdown-action-trigger svg[data-v-5d6a4f8a]{width:.18824rem;height:.18824rem}.markdown-action-trigger[data-v-5d6a4f8a]:hover{background:linear-gradient(135deg,#0059ad,#167ce8);border-color:#82b6ec}.markdown-action-dropdown[data-v-5d6a4f8a]{position:fixed;z-index:2147483000;width:3.52941rem;overflow:hidden;border:.01176rem solid #c8dced;border-radius:.11765rem;background:#fff;box-shadow:0 .18824rem .44706rem rgba(18,62,111,.16),0 .02353rem .09412rem rgba(24,84,140,.08)}.markdown-action-item[data-v-5d6a4f8a]{display:flex;width:100%;grid-gap:.16471rem;gap:.16471rem;align-items:flex-start;padding:.17647rem .18824rem;border:0;border-bottom:.01176rem solid #e6edf5;background:0 0;color:#2f495e;text-align:left;cursor:pointer;transition:background-color .15s ease}.markdown-action-item svg[data-v-5d6a4f8a]{flex:0 0 auto;width:.2rem;height:.2rem;margin-top:.02353rem;color:#238dfb}.markdown-action-item strong[data-v-5d6a4f8a]{display:block;font-size:.17647rem;line-height:.23529rem}.markdown-action-item small[data-v-5d6a4f8a]{display:block;margin-top:.02353rem;color:#6f8193;font-size:.15294rem;line-height:.21176rem}.markdown-action-item[data-v-5d6a4f8a]:last-child{border-bottom:0}.markdown-action-item[data-v-5d6a4f8a]:hover{background:#f3f8fe}.markdown-action-menu.placement-sidebar[data-v-5d6a4f8a]{justify-content:center;margin:.14118rem 0 0}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;justify-content:center;background:#edf6ff;border-color:#c7dff7;color:#0064c2}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#dfefff;border-color:#9fc7ef}.markdown-action-menu.placement-sidebar .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.05882rem}.markdown-action-menu.placement-anchor[data-v-5d6a4f8a]{justify-content:flex-start;margin:0 0 .11765rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:center;padding:0 .11765rem;background:#f5f9fd;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-anchor .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.placement-toolbox[data-v-5d6a4f8a]{width:100%;flex:1;justify-content:flex-start;margin:0}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;padding:0 .11765rem;background:#fff;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]{flex:0 0 auto}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{width:.16471rem;height:.16471rem;margin-left:auto;opacity:.55}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-toolbox .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.compact[data-v-5d6a4f8a]{justify-content:flex-start;margin:.09412rem 0 .18824rem}.markdown-action-menu.compact .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center;padding:0;background:#edf6ff;border-color:#b7d8f5;color:#0064c2}.markdown-action-menu.compact .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.52941rem;max-width:calc(100vw - .37647rem)}.markdown-action-menu.compact.placement-toolbox[data-v-5d6a4f8a]{flex:0 0 auto;margin:0}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{margin-left:0}</style><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer-Adv/state.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer-Adv/payload.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/manifest.js" as="script">
-  </head>
-  <body>
-    <div data-server-rendered="true" id="__nuxt"><!----><div id="__layout"><div class="device-hydration-sensitive"><div class="pc"><header langdata="[object Object]" lang="en"><!----> <!----> <div class="header-container"><a href="https://m5stack.com/" class="logo"><img src="/assets/m5logo.svg" alt="M5Stack"></a> <div class="header-nav"><div class="header-nav-ul"><!----> <li data-id="solution" class="header-nav-item"><a class="header-nav-item-a disabledHover">Solution</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="store" class="header-nav-item"><a href="https://shop.m5stack.com" class="header-nav-item-a">Store</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="software" class="header-nav-item"><a class="header-nav-item-a disabledHover">Software</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="document" class="header-nav-item"><a class="header-nav-item-a disabledHover">Documentation</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="aboutus" class="header-nav-item"><a class="header-nav-item-a disabledHover">About Us</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="contact" class="header-nav-item"><a class="header-nav-item-a disabledHover">Contact</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----></div></div> <div class="language-option-box"><div class="current-language"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 1.32 1.32" fill="currentColor" aria-hidden="true" class="icon"><g><path d="M0.66 0c0.18,0 0.35,0.07 0.47,0.19 0.12,0.12 0.19,0.28 0.19,0.47 0,0.18 -0.07,0.35 -0.19,0.47 -0.12,0.12 -0.28,0.19 -0.47,0.19 -0.18,0 -0.35,-0.07 -0.47,-0.19 -0.12,-0.12 -0.19,-0.28 -0.19,-0.47 0,-0.18 0.07,-0.35 0.19,-0.47 0.12,-0.12 0.28,-0.19 0.47,-0.19zm0.39 0.27c-0.1,-0.1 -0.24,-0.16 -0.39,-0.16 -0.15,0 -0.29,0.06 -0.39,0.16 -0.1,0.1 -0.16,0.24 -0.16,0.39 0,0.15 0.06,0.29 0.16,0.39 0.1,0.1 0.24,0.16 0.39,0.16 0.15,0 0.29,-0.06 0.39,-0.16 0.1,-0.1 0.16,-0.24 0.16,-0.39 0,-0.15 -0.06,-0.29 -0.16,-0.39z"></path> <path d="M0.09 0.51c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.09 0.92c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.62 1.21c0.02,0.02 0.02,0.06 0,0.08 -0.02,0.02 -0.06,0.02 -0.08,0 -0.07,-0.06 -0.13,-0.16 -0.16,-0.27 -0.04,-0.11 -0.06,-0.23 -0.06,-0.36 0,-0.13 0.02,-0.26 0.06,-0.36 0.04,-0.11 0.1,-0.21 0.16,-0.27 0.02,-0.02 0.06,-0.02 0.08,0 0.02,0.02 0.02,0.06 -0,0.08 -0.06,0.05 -0.1,0.13 -0.14,0.23 -0.03,0.09 -0.05,0.21 -0.05,0.33 0,0.12 0.02,0.23 0.05,0.33 0.03,0.1 0.08,0.18 0.14,0.23z"></path> <path d="M0.78 1.29c-0.02,0.02 -0.06,0.02 -0.08,-0 -0.02,-0.02 -0.02,-0.06 0,-0.08 0.06,-0.05 0.1,-0.13 0.14,-0.23 0.03,-0.09 0.05,-0.21 0.05,-0.33 0,-0.12 -0.02,-0.23 -0.05,-0.33 -0.03,-0.1 -0.08,-0.18 -0.14,-0.23 -0.02,-0.02 -0.02,-0.06 -0,-0.08 0.02,-0.02 0.06,-0.02 0.08,-0 0.07,0.06 0.13,0.16 0.16,0.27 0.04,0.11 0.06,0.23 0.06,0.36 0,0.13 -0.02,0.26 -0.06,0.36 -0.04,0.11 -0.1,0.21 -0.16,0.27z"></path></g></svg> <div>English</div> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg></div> <div class="language-dropdown-wrapper"><div class="language-dropdown"><div class="language-item active">English</div> <div class="language-item">简体中文</div> <div class="language-item">日本語</div></div></div></div></div></header> <div class="docs-layouts"><div class="docs-layouts-sidebar"><div class="side-bar"><div class="side-bar-title"><p>CONTENTS</p></div> <div class="side-bar-contents"></div></div></div> <div class="docs-layouts-body"><div class="page-header-container"><!----></div> <!----> <div class="search-box"><div id="search"></div> <input placeholder="Product Name / SKU"> <div class="search-result-container" style="display:none" data-v-2b770079><a class="search-result-contents" data-v-2b770079><div class="search-result-content" data-v-2b770079><div class="search-result-name" data-v-2b770079>No Results Found</div> <div class="search-result-sku" data-v-2b770079>Hot Searches</div> <div class="search-result-key" data-v-2b770079><div class="search-result-recommand-box" data-v-2b770079><div data-key="Camera" class="search-result-recommand-item" data-v-2b770079>
-            Camera
-          </div><div data-key="WiFi" class="search-result-recommand-item" data-v-2b770079>
-            WiFi
-          </div><div data-key="RS485" class="search-result-recommand-item" data-v-2b770079>
-            RS485
-          </div><div data-key="RS232" class="search-result-recommand-item" data-v-2b770079>
-            RS232
-          </div><div data-key="Relay" class="search-result-recommand-item" data-v-2b770079>
-            Relay
-          </div><div data-key="LoRaWAN" class="search-result-recommand-item" data-v-2b770079>
-            LoRaWAN
-          </div><div data-key="GPS" class="search-result-recommand-item" data-v-2b770079>
-            GPS
-          </div><div data-key="NB-IoT" class="search-result-recommand-item" data-v-2b770079>
-            NB-IoT
-          </div><div data-key="LTE" class="search-result-recommand-item" data-v-2b770079>
-            LTE
-          </div><div data-key="GSM" class="search-result-recommand-item" data-v-2b770079>
-            GSM
-          </div><div data-key="Zigbee" class="search-result-recommand-item" data-v-2b770079>
-            Zigbee
-          </div><div data-key="Servo" class="search-result-recommand-item" data-v-2b770079>
-            Servo
-          </div><div data-key="StepMotor" class="search-result-recommand-item" data-v-2b770079>
-            StepMotor
-          </div><div data-key="Ethernet" class="search-result-recommand-item" data-v-2b770079>
-            Ethernet
-          </div><div data-key="E-Paper" class="search-result-recommand-item" data-v-2b770079>
-            E-Paper
-          </div></div></div></div></a> <div class="tab-panel" style="display:none" data-v-2b770079><div class="tabs"><button>
-      Product
-    </button><button>
-      Contents
-    </button></div> <div class="tab-content"><div style="display:none"></div><div style="display:none"></div></div></div></div> <button class="search-btn"><p>Search</p></button> <div class="search-cover" style="display:none"></div></div> <div class="viewer"><div class="markdown"><h1 id="cardputer-adv" data-id="Cardputer-Adv">Cardputer-Adv</h1> <p><span class="product-sku">SKU:K132-Adv</span></p><div class="carousel-container" data-v-6e07f87d><div class="carousel-preview" data-v-6e07f87d><div class="clickable-area left" data-v-6e07f87d></div> <button class="arrow left" data-v-6e07f87d></button> <div class="carousel-images" data-v-6e07f87d><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-6e07f87d><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_01.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_02.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_03.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_04.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_05.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_06.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_07.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_08.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_09.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_10.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_11.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_12.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_13.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-weight.jpg" alt="Preview" data-v-6e07f87d></div></div></div> <button class="arrow right" data-v-6e07f87d></button> <div class="clickable-area right" data-v-6e07f87d></div></div> <div class="carousel-thumbnails" data-v-6e07f87d><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_01.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_02.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_03.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_04.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_05.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_06.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_07.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_08.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_09.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_10.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_11.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_12.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_13.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-weight.jpg" alt="Thumbnail" data-v-6e07f87d></div></div></div> <h2 id="description" data-id="Description">Description</h2> <p><strong>Cardputer-Adv</strong> is a programmable card-sized computer powered by the Stamp-S3A core module (based on ESP32-S3FN8). It integrates a 1.14" LCD display and a 56-key minimalist keyboard for convenient interaction and input operations.<br>In terms of audio, it features an ES8311 audio codec, a high SNR MEMS microphone, an NS4150B amplifier, and a 1W speaker, providing high-quality audio input and output capabilities. Additionally, it has a 3.5mm audio output jack for connecting external headphones or speakers.
-Internally, it is equipped with a 1750mAh high-capacity lithium battery, combined with a low-power design and an independent power switch to ensure good battery life. It integrates a 6-axis motion sensor BMI270, an infrared emitter, a microSD card slot, and also provides an HY2.0-4P Grove port and an EXT 2.54-14P expansion bus for connecting sensors and other peripherals.
-The base contains magnets for metal attachment and is compatible with LEGO hole extensions. This product is suitable for quick function prototyping, industrial control, home automation, and other scenarios.</p><h2 id="tutorial" data-id="Tutorial">Tutorial</h2> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/uiflow2/uiflow2.0_banner_01.png" alt="UiFlow2"> <a target="_blank" href="/en/uiflow2/cardputer-adv/program">UiFlow2</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/uiflow2/cardputer-adv/program">UiFlow2</a></div> <div class="learn-desc"> This tutorial demonstrates how to control the Cardputer-Adv device with the UiFlow2 graphical programming platform. </div></div></div> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/arduino/arduino_banner_01.png" alt="Arduino IDE"> <a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-desc"> This tutorial will introduce how to program and control the Cardputer-Adv device through Arduino IDE </div></div></div><h2 id="features" data-id="Features">Features</h2> <ul><li>Stamp-S3A core controller</li> <li>56-key keyboard</li> <li>1.14" LCD display</li> <li>160gf comfortable keypress feel</li> <li>ES8311 audio codec</li> <li>High SNR MEMS microphone</li> <li>NS4150B amplifier + 1W speaker</li> <li>3.5mm audio output interface</li> <li>Infrared emitter</li> <li>6-axis motion sensor BMI270</li> <li>HY2.0-4P Grove port</li> <li>EXT 2.54-14P expansion bus</li> <li>microSD card slot</li> <li>Built-in 1750mAh battery</li> <li>Magnetic back design</li> <li>LEGO hole compatible</li> <li>Development Platform<ul><li>Arduino</li> <li>UiFlow2</li> <li>ESP-IDF</li> <li>PlatformIO</li></ul></li></ul> <h2 id="includes" data-id="Includes">Includes</h2> <ul><li>1 x Cardputer-Adv</li></ul> <h2 id="applications" data-id="Applications">Applications</h2> <ul><li>Rapid prototyping and functional verification</li> <li>Industrial control and automation</li> <li>Embedded systems development and learning</li> <li>Wireless communication and IoT projects</li></ul> <h2 id="specifications" data-id="Specifications">Specifications</h2> <div class="table-container"><table><thead><tr><th>Specification</th> <th>Parameter</th></tr></thead><tbody><tr><td>SoC</td> <td>ESP32-S3FN8 @ Xtensa® 32-bit LX7 dual-core processor, clock frequency 240MHz</td></tr> <tr><td>Flash</td> <td>8MB</td></tr> <tr><td>External Storage</td> <td>microSD</td></tr> <tr><td>Display</td> <td>ST7789V2@1.14", 240 x 135px</td></tr> <tr><td>Keyboard</td> <td>56 keys (4 x 14)</td></tr> <tr><td>Key Actuation</td> <td>160gf</td></tr> <tr><td>Expansion Ports</td> <td>HY2.0-4P + EXT 2.54-14P</td></tr> <tr><td>IR</td> <td>1x IR emitter</td></tr> <tr><td>Audio Codec</td> <td>ES8311</td></tr> <tr><td>Speaker</td> <td>NS4150B amplifier + 8Ω@1W speaker</td></tr> <tr><td>Microphone</td> <td>MEMS microphone, SNR: 65 dB</td></tr> <tr><td>IMU</td> <td>BMI270</td></tr> <tr><td>Battery Capacity</td> <td>1750mAh</td></tr> <tr><td>Operating Temp.</td> <td>0 ~ 40°C</td></tr> <tr><td>Standby Current (Power Switch Set to OFF)</td> <td>DC4.2V@0.23uA</td></tr> <tr><td>Operating Current</td> <td>DC4.2V@120.2mA</td></tr> <tr><td>Wi-Fi Operating Current</td> <td>DC4.2V@132.3mA</td></tr> <tr><td>BLE Operating Current</td> <td>DC4.2V@154.6mA</td></tr> <tr><td>Product Size</td> <td>84.0 x 54.0 x 19.6mm</td></tr> <tr><td>Product Weight</td> <td>81.0g</td></tr> <tr><td>Package Size</td> <td>145.7 x 95.0 x 20.7mm</td></tr> <tr><td>Gross Weight</td> <td>98.5g</td></tr></tbody></table></div><h2 id="learn" data-id="Learn">Learn</h2> <h3 id="download-mode" data-id="Download Mode">Download Mode</h3> <p>To enter download mode, set the side power switch of the Cardputer-Adv to the <code>OFF</code> position. Then, before powering on, hold the <code>G0</code> button, apply power to the device, and release it afterward. The device will then enter download mode.</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_operation_01.jpg" width="60%"> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_operation.gif" width="60%"> <h3 id="rgb-led-power-supply" data-id="RGB LED Power Supply">RGB LED Power Supply</h3> <div class="warn"><div class="warn-title">RGB LED Power Supply Instructions</div> <div class="warn-content">The device uses <strong>Stamp-S3A</strong> as its main controller. To optimize overall power consumption, Stamp-S3A adds an independent electronic switch for the RGB LED power supply compared with the previous Stamp-S3. Before controlling the RGB LED in software, set GPIO38, which controls this switch, to a high level.</div></div><h3 id="charging-notes" data-id="Charging Notes">Charging Notes</h3> <p>When charging the Cardputer-Adv, please switch the power to <code>ON</code>.</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_14.jpg" width="60%"> <h3 id="speaker-feature" data-id="Speaker Feature">Speaker Feature</h3> <div class="tip"><div class="tip-title">Note </div> <div class="tip-content"> When a 3.5mm headphone jack is inserted, the speaker amplifier will be disabled.</div></div><h3 id="imu-triaxial-direction-schematic-diagram" data-id="IMU Triaxial Direction Schematic Diagram">IMU Triaxial Direction Schematic Diagram</h3> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/IMU-Cardputer-Adv.jpg" width="70%"> <h2 id="schematics" data-id="Schematics">Schematics</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf">Cardputer-Adv Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf">Stamp-S3A Schematics PDF</a></li></ul> <div class="carousel-container" data-v-7d51a79c><div class="carousel-preview" data-v-7d51a79c><div class="clickable-area left" data-v-7d51a79c></div> <button class="arrow left" data-v-7d51a79c></button> <div class="carousel-images" data-v-7d51a79c><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-7d51a79c><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_02.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_03.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_04.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Preview" data-v-7d51a79c></div></div></div> <button class="arrow right" data-v-7d51a79c></button> <div class="clickable-area right" data-v-7d51a79c></div> <div class="corner-marker" data-v-7d51a79c>1/5</div></div> <div class="carousel-thumbnails" data-v-7d51a79c><div class="thumbnail active" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_02.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_03.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_04.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Thumbnail" data-v-7d51a79c></div></div></div> <h2 id="pinmap" data-id="PinMap">PinMap</h2> <h3 id="lcd" data-id="LCD">LCD</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G38</th> <th>G33</th> <th>G34</th> <th>G35</th> <th>G36</th> <th>G37</th></tr></thead><tbody><tr><td>ST7789V2</td> <td>DISP_BL</td> <td>RST</td> <td>RS</td> <td>DAT</td> <td>SCK</td> <td>CS</td></tr> <tr><td>RGB LED</td> <td>PWR_EN</td> <td></td> <td></td> <td></td> <td></td> <td></td></tr></tbody></table></div><h3 id="audio" data-id="Audio">Audio</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th> <th>G41</th> <th>G46</th> <th>G43</th> <th>G42</th></tr></thead><tbody><tr><td>ES8311</td> <td>SDA</td> <td>SCL</td> <td>SCLK</td> <td>ASDOUT</td> <td>LRCK</td> <td>DSDIN</td></tr></tbody></table></div><h3 id="imu" data-id="IMU">IMU</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th></tr></thead><tbody><tr><td>BMI270</td> <td>SDA</td> <td>SCL</td></tr></tbody></table></div><h3 id="ir" data-id="IR">IR</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G44</th></tr></thead><tbody><tr><td>IR TX</td> <td>TX</td></tr></tbody></table></div><h3 id="battery" data-id="Battery">Battery</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G10</th></tr></thead><tbody><tr><td>Battery</td> <td>ADC</td></tr></tbody></table></div><h3 id="keyboard" data-id="Keyboard">Keyboard</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th> <th>G11</th></tr></thead><tbody><tr><td>TCA8418RTWR</td> <td>SDA</td> <td>SCL</td> <td>INT</td></tr></tbody></table></div><h3 id="microsd" data-id="microSD">microSD</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G12</th> <th>G14</th> <th>G40</th> <th>G39</th></tr></thead><tbody><tr><td>microSD</td> <td>CS</td> <td>MOSI</td> <td>CLK</td> <td>MISO</td></tr></tbody></table></div><h3 id="hy20-4p" data-id="HY2.0-4P">HY2.0-4P</h3> <div class="grove-table-container"><div class="table-container"><table><thead><tr><th>HY2.0-4P</th> <th>Black</th> <th>Red</th> <th>Yellow</th> <th>White</th></tr></thead><tbody><tr><td>PORT.CUSTOM</td> <td>GND</td> <td>5V</td> <td>G2</td> <td>G1</td></tr></tbody></table></div></div><h3 id="ext-254-14p" data-id="EXT 2.54-14P">EXT 2.54-14P</h3> <div class="m5-bus-table-container core"><div class="table-container"><table><thead><tr><th>FUNC</th> <th>PIN</th> <th>LEFT</th> <th>RIGHT</th> <th>PIN</th> <th>FUNC</th></tr></thead><tbody><tr><td>RESET</td> <td>G3</td> <td>1</td> <td>2</td> <td class="VCC">5VIN</td> <td class="empty"></td></tr> <tr><td>INT</td> <td>G4</td> <td>3</td> <td>4</td> <td class="GND">GND</td> <td class="empty"></td></tr> <tr><td>BUSY</td> <td>G6</td> <td>5</td> <td>6</td> <td class="VCC">5VOUT</td> <td class="empty"></td></tr> <tr><td class="SPI">SCK</td> <td>G40</td> <td>7</td> <td>8</td> <td>G8</td> <td class="I2C">I2C_SDA</td></tr> <tr><td class="SPI">MOSI</td> <td>G14</td> <td>9</td> <td>10</td> <td>G9</td> <td class="I2C">I2C_SCL</td></tr> <tr><td class="SPI">MISO</td> <td>G39</td> <td>11</td> <td>12</td> <td>G13</td> <td>UART_TX</td></tr> <tr><td class="SPI">CS</td> <td>G5</td> <td>13</td> <td>14</td> <td>G15</td> <td>UART_RX</td></tr></tbody></table></div></div><h2 id="model-size" data-id="Model Size">Model Size</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV.pdf">Cardputer-Adv Model Size PDF</a></li></ul> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV_page_01.png" width="100%"> <h2 id="structure" data-id="Structure">Structure</h2> <ul><li><a target="_blank" href="https://github.com/m5stack/M5_Hardware/tree/master/Products/K132-Adv_Cardputer-Adv/Structures">Cardputer-Adv Structure Files</a></li></ul> <h2 id="softwares" data-id="Softwares">Softwares</h2> <h3 id="arduino" data-id="Arduino">Arduino</h3> <ul><li><a target="_blank" href="/en/arduino/m5cardputer/program">Cardputer-Adv Arduino Quick Start</a></li> <li><a target="_blank" href="https://github.com/m5stack/M5Cardputer">Cardputer-Adv Arduino Driver Library</a></li></ul> <h3 id="uiflow2" data-id="UiFlow2">UiFlow2</h3> <ul><li><a target="_blank" href="/en/uiflow2/cardputer-adv/program">Cardputer-Adv UiFlow2 Quick Start</a></li></ul> <h3 id="platformio" data-id="PlatformIO">PlatformIO</h3> <div class="code-block-wrapper"><div class="code-line-container"><pre><code class="hljs language-bash">[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code></pre> <button class="copy-all-btn"><code>[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code> <div class="fa-solid fa-copy"></div></button></div></div> <h3 id="esp-idf" data-id="ESP-IDF">ESP-IDF</h3> <ul><li><a target="_blank" href="https://github.com/m5stack/M5Cardputer-UserDemo/tree/CardputerADV">Cardputer-Adv Factory Firmware</a></li></ul> <h3 id="easyloader" data-id="Easyloader">Easyloader</h3> <div class="table-container"><table><thead><tr><th>Easyloader</th> <th>Download</th> <th>Note</th></tr></thead><tbody><tr><td>Cardputer-Adv Factory Easyloader</td> <td><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Easy_Loader_for_Cardputer-Adv.exe">download</a></td> <td>/</td></tr></tbody></table></div><h2 id="video" data-id="Video">Video</h2> <div class="video-gallery-island" data-v-5e05839f></div> <h2 id="product-comparison" data-id="Product Comparison">Product Comparison</h2> <div class="compare-table-container"><div class="table-container"><table><thead><tr><th>Product Comparison Item</th> <th><a target="_blank" href="/en/core/Cardputer-Adv">Cardputer-Adv</a> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_02.webp" alt="Cardputer-Adv"></th> <th><a target="_blank" href="/en/core/Cardputer%20V1.1">Cardputer v1.1</a> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_04.webp" alt="Cardputer v1.1"></th> <th><a target="_blank" href="/en/core/Cardputer">Cardputer</a> <img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-a02d6727-4fa1-4b38-90e6-75e401d507de.webp" alt="Cardputer"></th></tr></thead><tbody><tr><td>Core Module</td> <td>Stamp-S3A</td> <td>Stamp-S3A</td> <td>Stamp-S3</td></tr> <tr><td>RGB LED Logic</td> <td>Shares power with display backlight, optimized control logic</td> <td>Shares power with display backlight, optimized control logic</td> <td>Powered directly</td></tr> <tr><td>Antenna Design</td> <td>Optimized antenna design for better reception</td> <td>Optimized antenna design for better reception</td> <td>Standard antenna</td></tr> <tr><td>Battery Capacity</td> <td>1750mAh</td> <td>120mAh + 1400mAh</td> <td>120mAh + 1400mAh</td></tr> <tr><td>Audio Solution</td> <td>ES8311 + NS4150B</td> <td>NS4168 + SPM1423</td> <td>NS4168 + SPM1423</td></tr> <tr><td>Audio Port</td> <td>3.5mm audio jack</td> <td>/</td> <td>/</td></tr> <tr><td>IMU</td> <td>BMI270</td> <td>/</td> <td>/</td></tr> <tr><td>Keyboard IO Exp.</td> <td>TCA8418RTWR</td> <td>74HC138</td> <td>74HC138</td></tr> <tr><td>Expansion Ports</td> <td>HY2.0-4P + EXT 2.54-14P</td> <td>HY2.0-4P</td> <td>HY2.0-4P</td></tr> <tr><td>Lanyard Hole</td> <td>Yes</td> <td>No</td> <td>No</td></tr></tbody></table></div></div><p>To compare information on the Cardputer series products, you can visit the <a target="_blank" href="/en/products_selector/m5cardputer_compare?select=K132-Adv">Product Selection Table</a>, check the target products, and get the comparison results. The selection table covers key information such as core parameters and functional features, and supports comparison of multiple products simultaneously.</p></div> <!----> <!----> <!----></div></div> <div class="docs-layouts-anchor"><div class="page-tools" data-v-39baf185><div class="page-tools-title" data-v-39baf185>Page Tools</div> <div class="page-tools-actions" data-v-39baf185><a href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/Cardputer-Adv.pdf" target="_blank" rel="nofollow noopener noreferrer" title="Download PDF" class="page-tools-action page-tools-pdf" data-v-39baf185><svg viewBox="0 0 24 24" aria-hidden="true" class="page-tools-icon" data-v-39baf185><path d="M6 2h8l4 4v16H6V2zm7 1.8V7h3.2L13 3.8zM8.4 12.2h1.5c1 0 1.7-.6 1.7-1.6S10.9 9 9.9 9H7v6h1.4v-2.8zm0-1.1v-1h1.3c.3 0 .5.2.5.5s-.2.5-.5.5H8.4zm4.1 3.9h1.8c1.7 0 2.8-1.1 2.8-3s-1.1-3-2.8-3h-1.8v6zm1.4-1.2v-3.6h.4c.9 0 1.4.6 1.4 1.8s-.5 1.8-1.4 1.8h-.4zm4.1 1.2h1.4v-2.4h2.1v-1.2h-2.1v-1.2h2.4V9H18v6z" data-v-39baf185></path></svg> <span data-v-39baf185>PDF</span></a> <div class="markdown-action-menu placement-toolbox" data-v-5d6a4f8a data-v-39baf185><button type="button" title="Copy page" class="markdown-action-trigger" data-v-5d6a4f8a><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><rect x="9" y="9" width="13" height="13" rx="2"></rect><path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1"></path></svg> <span data-v-5d6a4f8a>Copy page</span> <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><polyline points="6 9 12 15 18 9"></polyline></svg></button> <!----></div></div></div></div></div> <footer><div class="footer-container"><div class="footer-content-wrap"><div class="footer-nav"><div class="footer-nav-item"><div data-id="0" class="footer-nav-title"><a class="footer-nav-title-a">
-        About Us
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/about-us">About M5Stack</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?page=1">News</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?type=blog&page=1">Blog</a></li><li class="footer-nav-li"><a href="https://m5stack.com/events">Events</a></li><li class="footer-nav-li"><a href="https://m5stack.com/contact">Contact Us</a></li></ul></div><div class="footer-nav-item"><div data-id="1" class="footer-nav-title"><a class="footer-nav-title-a">
-        Where to buy
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/distributor">Distributors</a></li><li class="footer-nav-li"><a href="https://shop.m5stack.com/">Official Store</a></li><li class="footer-nav-li"><a href="https://m5stack.aliexpress.com/store/911661199">AliExpress</a></li><li class="footer-nav-li"><a href="https://www.amazon.com/shops/m5stack">Amazon</a></li><li class="footer-nav-li"><a href="https://m5stack.taobao.com/">Taobao</a></li></ul></div><div class="footer-nav-item"><div data-id="2" class="footer-nav-title"><a class="footer-nav-title-a">
-        Solution
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/business">For Business</a></li><li class="footer-nav-li"><a href="https://m5stack.com/developers">For Developers</a></li></ul></div><div class="footer-nav-item"><div data-id="3" class="footer-nav-title"><a class="footer-nav-title-a">
-        Software
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://flow.m5stack.com/">UiFlow1</a></li><li class="footer-nav-li"><a href="https://uiflow2.m5stack.com/">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/uiflow/m5burner/intro">M5Burner</a></li><li class="footer-nav-li"><a href="https://block-designer.m5stack.com/">Block Designer</a></li><li class="footer-nav-li"><a href="/en/guide/ezdata/ezdata_v2">EzData 2.0</a></li><li class="footer-nav-li"><a href="/en/guide/easyloader/easyloader_packer">EasyLoader Packer</a></li><li class="footer-nav-li"><a href="/en/guide/develop_tools/vlw_font_creator">VLW Font Creator</a></li><li class="footer-nav-li"><a href="/en/download">Device USB Driver</a></li></ul></div><div class="footer-nav-item"><div data-id="4" class="footer-nav-title"><a class="footer-nav-title-a">
-        Documentation
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="/en/products">Product Documents</a></li><li class="footer-nav-li"><a href="/en/uiflow/uiflow_web">UiFlow1</a></li><li class="footer-nav-li"><a href="/en/uiflow2/uiflow_web">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/arduino/arduino_ide">Arduino</a></li><li class="footer-nav-li"><a href="/en/esp_idf/esp_idf">ESP-IDF</a></li><li class="footer-nav-li"><a href="/en/stackflow/overview">StackFlow AI</a></li><li class="footer-nav-li"><a href="/en/homeassistant/overview">Home Assistant</a></li><li class="footer-nav-li"><a href="https://github.com/nanoframework/nanoFramework.M5Stack">nanoFramework</a></li><li class="footer-nav-li"><a href="/en/guide/product_guide">Product Guide</a></li><li class="footer-nav-li"><a href="/en/certification">Product Certifications</a></li><li class="footer-nav-li"><a href="/en/product_i2c_addr">I2C Table</a></li><li class="footer-nav-li"><a href="/en/products_selector/m5core_compare">Product Selector</a></li><li class="footer-nav-li"><a href="https://github.com/m5stack/M5_Hardware">Hardware Design Files</a></li><li class="footer-nav-li"><a href="/en/history">Release History</a></li><li class="footer-nav-li"><a href="/en/compatible_stack">Stack Compatibility</a></li><li class="footer-nav-li"><a href="/en/learn/extension/module">Stack Screw Length</a></li></ul></div></div> <div class="footer-right"><div class="footer-email-group"><p class="footer-email-title">
-              Stay in the Loop
-            </p> <p class="footer-email-desc">
-              Weekly updates on new products, innovations, and announcements.
-            </p> <div class="footer-email-input"><input placeholder="Enter Email address" autocomplete="off" class="email-input"> <button type="button" class="subscribe-btn">
-                Subscribe
-              </button></div> <p class="footer-email-warning" style="display:none">
-              Email is invalid!
-            </p></div> <div class="footer-email-success" style="display:none">
-            Thanks for subscribing
-          </div> <div class="footer-follow"><div class="footer-follow-ul"><a href="https://x.com/M5Stack"><img src="/assets/footer/sociallist10.svg" alt></a><a href="https://www.linkedin.com/company/m5stack"><img src="/assets/footer/sociallist2.svg" alt></a><a href="https://www.instagram.com/m5stack"><img src="/assets/footer/sociallist8.svg" alt></a><a href="https://www.facebook.com/M5Stack"><img src="/assets/footer/sociallist7.svg" alt></a><a href="https://www.youtube.com/m5stack"><img src="/assets/footer/sociallist5.svg" alt></a><a href="https://www.tiktok.com/@m5stack"><img src="/assets/footer/tiktok.svg" alt></a><a href="https://www.hackster.io/m5stack"><img src="/assets/footer/sociallist3.svg" alt></a><a href="https://discord.gg/ysQAWBUE9Q"><img src="/assets/footer/sociallist4.svg" alt></a><a href="https://github.com/m5stack"><img src="/assets/footer/sociallist6.svg" alt></a></div></div> <div class="footer-info-wrapper"><div class="footer-info">
-            M5Stack Technology Co., Ltd
-          </div> <div class="footer-address-info">
-            Address: 
-             Block A10, Expo Bay South Coast, Fuhai Street, Bao'an District, Shenzhen, China
-          </div> <div class="footer-info">
-            TEL: 
-            +86 755 8657 5379
-          </div> <div class="footer-info">
-            Email: 
-            support@m5stack.com
-          </div></div></div></div></div> <div class="footer-bottom"><div class="footer-bottom-content"><div class="footer-copy">
-        Copyright ©
-        <a href="https://m5stack.com/">M5Stack Technology Co., Ltd.</a>
-        All rights reserved.
-      </div> <div class="terms-box"><!----> <a href="https://shop.m5stack.com/policies/privacy-policy">Privacy Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/terms-of-service">Terms of Service</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/shipping-policy">Shipping Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/refund-policy">Refund Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/pages/payment-method">Payment Method</a></div> <div class="beian"><a href="https://beian.miit.gov.cn/">粤ICP备16010631号</a></div></div></div> <!----></footer> <div class="float-icon-container"><div class="totop-icon"><svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 280 280" xmlns:xlink="http://www.w3.org/1999/xlink" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M143 70l58 69c1,1 1,3 1,4 -1,1 -2,2 -4,2l-20 0c-2,0 -4,2 -4,4l1 57c0,2 -2,4 -4,4l-62 0c-2,0 -4,-2 -4,-4l1 -57c0,-2 -2,-4 -4,-4l-20 0c-2,0 -3,-1 -4,-2 -1,-1 0,-3 1,-4l58 -69c1,-1 2,-1 3,-1 1,0 2,1 3,1z" class="fil1"></path></g></svg></div> <div class="menu-icon" style="display:none"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 800 800" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M253 229l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 370l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 511l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path></g></svg></div></div></div></div></div></div><script defer src="/_nuxt/static/1788504562/en/core/Cardputer-Adv/state.js"></script><script src="/_nuxt/41d5c62.js" defer></script><script src="/_nuxt/c970150.js" defer></script><script src="/_nuxt/5a34d22.js" defer></script><script src="/_nuxt/a352c6d.js" defer></script><script src="/_nuxt/b9c4bc6.js" defer></script>
-  </body>
-</html>
diff --git a/devices/m5stack/cardputer-adv/artifacts/docs/docs-zh_CN-core-Cardputer-Adv.html b/devices/m5stack/cardputer-adv/artifacts/docs/docs-zh_CN-core-Cardputer-Adv.html
deleted file mode 100644
index cd574ab..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/docs/docs-zh_CN-core-Cardputer-Adv.html
+++ /dev/null
@@ -1,106 +0,0 @@
-<!doctype html>
-<html data-n-head-ssr lang="en" data-n-head="%7B%22lang%22:%7B%22ssr%22:%22en%22%7D%7D">
-  <head>
-    <title>m5-docs</title><meta data-n-head="ssr" charset="utf-8"><meta data-n-head="ssr" name="viewport" content="width=device-width,initial-scale=1,minimum-scale=1,user-scalable=no"><meta data-n-head="ssr" data-hid="description" name="description" content="The reference docs for M5Stack products. Quick start, get the detailed information or instructions such as IDE,UIFLOW,Arduino. The tutorials for M5Burner, Firmware, Burning, programming. ESP32,M5StickC,StickV, StickT,M5ATOM."><link data-n-head="ssr" rel="icon" type="image/x-icon" href="/favicon.ico"><script data-n-head="ssr" data-hid="device-preload-detector">!function(){try{var e=document.documentElement;if(!e)return;var d=e.clientWidth||Number.POSITIVE_INFINITY,i=Number(window.innerWidth||0)||Number.POSITIVE_INFINITY,a=Math.min(d,i)<1024;e.classList.add(a?"device-preload-mobile":"device-preload-desktop"),a&&(e.classList.add("device-preload-pending"),window.__m5DevicePreloadReady=function(){e.classList.remove("device-preload-pending"),e.classList.add("device-preload-ready")})}catch(e){}}()</script><script data-n-head="ssr" src="https://cloud.umami.is/script.js" data-website-id="38e73ff2-ec10-4a8f-bfe2-c22a381ce306" defer></script><script data-n-head="ssr" src="/script/ga.js"></script><script data-n-head="ssr" src="/script/global.js"></script><script data-n-head="ssr" src="/public/esp-web-tools/install-button.js?module" type="module"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/marked.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/highlight.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-chat/index.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-qa/index.js"></script><link rel="preload" href="/_nuxt/41d5c62.js" as="script"><link rel="preload" href="/_nuxt/5a34d22.js" as="script"><link rel="preload" href="/_nuxt/a352c6d.js" as="script"><link rel="preload" href="/_nuxt/b9c4bc6.js" as="script"><link rel="preload" href="/_nuxt/c970150.js" as="script"><style data-vue-ssr-id="0b40e9c2:0 afa51714:0 73039f54:0 2576b79a:0 69f1b16c:0 17a511fe:0 3d88442c:0 3afe6180:0 786f8504:0 1af4924a:0 e762b0ec:0 e646c77c:0 4a658548:0 5f76b520:0 3e555512:0 4e0caf6f:0 060bbeb3:0 3ddd7ff2:0 bb0e6f22:0 27d15a7c:0 2c0daf93:0 d1c8934a:0 09fcdd3b:0 3231c87d:0 8716e91a:0 09d04477:0">body,html{width:100%;margin:0;padding:0}html.device-preload-mobile.device-preload-pending{background:linear-gradient(180deg,#f7f9fc,#eef3f8)}html.device-preload-mobile.device-preload-pending body{background:0 0}html.device-preload-mobile.device-preload-pending body:before{content:"";position:fixed;top:0;right:0;bottom:0;left:0;z-index:9999;pointer-events:none;background:linear-gradient(180deg,hsla(0,0%,100%,.92),rgba(243,247,251,.98)),radial-gradient(circle at top right,rgba(0,100,194,.08),transparent 38%)}html.device-preload-mobile.device-preload-pending body:after{content:"";position:fixed;left:50%;top:50%;width:.63529rem;height:.63529rem;margin-left:-.31765rem;margin-top:-.31765rem;z-index:10000;pointer-events:none;border:.04706rem solid rgba(35,141,251,.18);border-top-color:#238dfb;border-radius:50%;box-shadow:0 0 0 .09412rem rgba(35,141,251,.08);-webkit-animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite;animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite}html.device-preload-mobile.device-preload-pending .device-hydration-sensitive{opacity:0;visibility:hidden}html.device-preload-mobile.device-preload-ready body:after,html.device-preload-mobile.device-preload-ready body:before{opacity:0;transition:opacity .22s ease}html.device-preload-mobile.device-preload-ready .device-hydration-sensitive{visibility:visible;opacity:1;transition:opacity .18s ease}@-webkit-keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@-webkit-keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}@keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}html{overflow:hidden;overflow-y:auto}html::-webkit-scrollbar{width:.14118rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}@font-face{font-family:SourceCodePro;src:url(https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/font/SourceCodePro-Regular.ttf)}body,button{font-family:SourceCodePro,Microsoft YaHei;line-height:inherit;box-sizing:border-box}body,button,input{font-family:SourceCodePro,Microsoft YaHei,sans-serif}a{outline:0}.product_pic img{width:33%}.page-enter-active,.page-leave-active{transition:opacity .5s}.page-enter,.page-leave-active{opacity:0}.bounce-enter-active{-webkit-animation:bounce-in .8s;animation:bounce-in .8s}.bounce-leave-active{-webkit-animation:bounce-out .5s;animation:bounce-out .5s}@-webkit-keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@-webkit-keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}body,button,html[lang=zh-cn] footer,html[lang=zh-cn] header,input{font-family:Microsoft YaHei,sans-serif}html[lang=en] footer,html[lang=en] header{font-family:Montserrat,Microsoft YaHei,sans-serif}@font-face{font-family:Montserrat;font-weight:400;font-style:normal;src:url(/assets/fonts/Montserrat-Regular.woff2) format("woff2"),url(/assets/fonts/Montserrat-Regular.woff) format("woff"),url(/assets/fonts/Montserrat-Regular.otf) format("opentype"),url(/assets/fonts/Montserrat-Regular.ttf) format("truetype")}@font-face{font-family:Montserrat;font-weight:500;font-style:normal;src:url(/assets/fonts/Montserrat-Medium.woff2) format("woff2"),url(/assets/fonts/Montserrat-Medium.woff) format("woff"),url(/assets/fonts/Montserrat-Medium.otf) format("opentype"),url(/assets/fonts/Montserrat-Medium.ttf) format("truetype")}*{margin:0;padding:0;box-sizing:border-box}html{height:auto!important;font-size:10vw;line-height:1}@media screen and (max-width:320px){html{font-size:32PX}}@media screen and (min-width:540px){html{font-size:44PX}}@media screen and (min-width:860px){html{font-size:48PX}}@media screen and (min-width:960px){html{font-size:49PX}}@media screen and (min-width:1024px){html{font-size:52PX}}@media screen and (min-width:1175px){html{font-size:53PX}}@media screen and (min-width:1280px){html{font-size:56PX}}@media screen and (min-width:1366px){html{font-size:63PX}}@media screen and (min-width:1400px){html{font-size:68PX}}@media screen and (min-width:1440px){html{font-size:69PX}}@media screen and (min-width:1540px){html{font-size:73PX}}@media screen and (min-width:1680px){html{font-size:75PX}}@media screen and (min-width:1920px){html{font-size:75PX}}@media screen and (min-width:2560px){html{font-size:85PX}}body{-webkit-font-smoothing:subpixel-antialiased}li{list-style-type:none}img,li{-webkit-user-drag:none}img{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}a{text-decoration:none;-webkit-user-drag:none}a,button{outline:0}button{border:none;background-color:transparent;cursor:pointer}.fade-enter-active,.fade-leave-active{transition:opacity .5s}.fade-enter,.fade-leave-to{opacity:0}.markdown.guide img{box-shadow:0 -.07059rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);margin-top:.17647rem;margin-bottom:.58824rem;margin-left:.11765rem}.markdown.guide .blockly_svg{box-shadow:unset;margin:.17647rem 0 .05882rem;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content}.docs-layouts{padding-top:.58824rem;display:flex;justify-content:center;position:relative;margin-bottom:.35294rem}.docs-layouts .docs-layouts-sidebar{position:sticky;top:1.17647rem;left:0;height:-webkit-max-content;height:-moz-max-content;height:max-content;z-index:2;background-color:#fff}.docs-layouts .docs-layouts-title{display:flex;flex-direction:row;margin-bottom:.11765rem;align-items:center;width:100%;height:.47059rem;border-bottom:.03529rem solid #f5f5f5}.docs-layouts .docs-layouts-title .docs-layouts-icon{background-color:#238dfb;border-radius:.11765rem;display:flex;justify-content:center;align-items:center;height:.35294rem;width:.35294rem;margin-right:.11765rem}.docs-layouts .docs-layouts-title .docs-layouts-icon img{width:.23529rem;height:.23529rem}.docs-layouts .docs-layouts-title p{font-size:.23529rem;font-weight:700;color:#2f495e;line-height:.35294rem}.docs-layouts .docs-layouts-body{width:14.11765rem;min-width:0;max-width:100%;margin:0 .29412rem}.docs-layouts .docs-layouts-anchor{position:sticky;top:1.2rem;right:0;z-index:1;background-color:#fff;height:80vh;overflow-y:scroll}@media screen and (max-width:1200px){.docs-layouts .docs-layouts-anchor{display:none}}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar{width:.14118rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.mobile .docs-layouts{padding:.35294rem;display:flex}.mobile .docs-layouts .docs-layouts-body{width:100%;min-width:0;max-width:100%;margin:0}.mobile .docs-layouts .docs-layouts-sidebar{position:fixed;height:100vh;width:5.17647rem;top:0;padding:.47059rem .35294rem;left:auto;left:-100%;box-shadow:.11765rem .23529rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);transition:all .25s ease;z-index:5}.mobile .docs-layouts .docs-layouts-sidebar.active{left:0}.default{color:#3f3f46}.primary{color:#006fee}.secondary{color:#9353d3}.success{color:#17c964}.warning{color:#f5a524}.danger{color:#f31260}.markdown{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-column-gap:.18824rem;-moz-column-gap:.18824rem;column-gap:.18824rem;min-width:0;max-width:100%;overflow:hidden;word-break:break-word;padding-bottom:.35294rem;color:#4f5f6f;font-size:.18824rem;font-weight:400}.markdown>*{grid-column:1/-1}.markdown .product-sku{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .product-date,.markdown .product-sku{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.09412rem 0 .09412rem .09412rem;display:inline-block}.markdown .product-date{background-color:#efefef;color:#345b83}.markdown .tag-green{background-color:#f0fff4;color:#00c58e}.markdown .tag-blue,.markdown .tag-green{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.11765rem;display:inline-block}.markdown .tag-blue{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .tag-orange{font-size:.23529rem;margin:.23529rem .23529rem .23529rem 0;border-radius:.03529rem;padding:.02353rem .11765rem;background-color:#f8b013;color:#fff;cursor:pointer}.markdown .product-title{display:flex;align-items:center}.markdown .product-title span{color:#2f495e}.markdown .shop-title{display:flex;justify-content:space-between;position:relative;margin:.02353rem 0 0 .09412rem;background:#007bff;border-radius:.05882rem;color:#2f495e}.markdown .shop-title .shop-text{width:0;height:.47059rem;line-height:.47059rem;font-size:.2rem;text-align:center;color:#fff;overflow:hidden;transition:all .2s ease}.markdown .shop-title .shop-icon{position:relative;width:.47059rem;height:.47059rem;font-size:.35294rem;text-align:center;display:inline-block}.markdown .shop-title .shop-icon img{width:.35294rem;height:100%;display:inline-block}.markdown .shop-title .shop-icon:before{content:"";position:absolute;top:50%;right:-.32941rem;width:0;height:0;border-left:.23529rem solid transparent;border-right:.23529rem solid transparent;border-bottom:.23529rem solid #007bff;transform:translateY(-50%) rotate(90deg);display:none}.markdown .shop-title .shop-icon.eol:before{display:none}.markdown .shop-title:hover{color:#238dfb}.markdown .shop-title:hover .shop-text{width:2.35294rem}.markdown .shop-title:hover .shop-icon:before{display:block}.markdown .shop-title:hover .shop-icon.eol:before{display:none}.markdown .eol-title{display:flex;align-items:center;position:relative;margin:.02353rem 0 0 .08235rem;padding:0 .17647rem;height:.47059rem;line-height:.47059rem;background-color:#2f495e;border-radius:.05882rem}.markdown .eol-title .eol-text{font-size:.2rem;color:#fff}.markdown video{display:block;width:50%;margin-bottom:.35294rem}.markdown .video-iframe{margin:.23529rem 0;height:5.88235rem}.markdown .video-iframe iframe{width:50%;height:100%}.markdown .video-iframe>a{font-size:.23529rem;display:block;margin-bottom:.23529rem}.markdown a{color:#238dfb}.markdown h1{margin-top:.28235rem;margin-bottom:.21176rem;font-size:.54118rem;line-height:1.25}.markdown h1,.markdown h2{font-weight:600;color:#2f495e}.markdown h2{margin-top:.42353rem;margin-bottom:.18824rem;font-size:.35294rem;line-height:1.35;padding:0 .42353rem .11765rem .16471rem;position:relative;border-bottom:.01176rem solid #dfe5ec;cursor:pointer;transition:all .3s}.markdown h2:after{content:"";width:.03529rem;top:.04706rem;bottom:.16471rem;background:#238dfb;position:absolute;left:0}.markdown h2:before{content:"";position:absolute;background-image:url(/assets/link.svg);width:.29412rem;height:.29412rem;background-size:.29412rem;top:.08235rem;right:.05882rem;opacity:0;transition:opacity .3s}.markdown h2:hover{color:#0064c2}.markdown h2:hover:before{opacity:1}.markdown h3{margin-top:.32941rem;margin-bottom:.16471rem;font-size:.28235rem;color:#34495e;line-height:1.4}.markdown h3,.markdown h4{font-weight:600;position:relative}.markdown h4{margin-top:.28235rem;margin-bottom:.14118rem;font-size:.23529rem;color:#43566a;line-height:1.45}.markdown h5{margin-top:.23529rem;margin-bottom:.11765rem;font-size:.21176rem;font-weight:600;color:#526579;position:relative;line-height:1.5}.markdown ul{margin-bottom:.23529rem}.markdown ul ul{margin-bottom:.11765rem}.markdown ul li{list-style-type:circle;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f}.markdown ol{margin-bottom:.23529rem}.markdown ol li{list-style-type:decimal;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f;padding-left:.05882rem}.markdown ol li::marker{color:#6f6f6f;font-weight:700}.markdown code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;position:relative;color:#263445;font-size:.18824rem}.markdown :not(pre)>code{padding:.02353rem .05882rem;color:#165f8f;background:#eef3f7;border:.01176rem solid #dfe5ec;border-radius:.04706rem;font-size:.92em;font-weight:500}.markdown p{color:#4f5f6f;font-size:.18824rem;font-weight:400;line-height:.31765rem;margin-bottom:.16471rem}.markdown mark{background-color:#ffe051;color:#000}.markdown img{margin-bottom:.35294rem}.markdown>img:not([width]):not([class]){max-width:100%}.markdown .hljs{margin:.05882rem 0 .35294rem;font-size:.18824rem;line-height:.32941rem;white-space:pre;padding:.23529rem .29412rem;overflow-x:auto;overflow-y:hidden;border-radius:.07059rem;background-color:transparent;font-family:SourceCodePro,Microsoft YaHei;width:100%}.markdown .language-bash,.markdown .language-cpp,.markdown .language-diff,.markdown .language-dts,.markdown .language-json,.markdown .language-python,.markdown .language-shell{margin:0;font-size:.18824rem;line-height:.32941rem;white-space:pre;overflow-x:auto;overflow-y:hidden;background-color:transparent;display:block;width:100%}.markdown table thead,.markdown table tr{border-top:.01176rem solid #aabfdc}.markdown .normal-blockquote{box-shadow:-.05882rem 0 0 0 #238dfb;background-color:#fbfcfe;padding:.23529rem;margin:.17647rem 0 .17647rem .05882rem}.markdown .normal-blockquote p{font-weight:500;margin:0}.markdown .table-container{display:block;width:100%;min-width:0;max-width:100%;overflow-x:auto;overflow-y:hidden;overscroll-behavior-inline:contain;-webkit-overflow-scrolling:touch}.markdown table{border:none;display:table;min-width:100%;overflow:auto;margin:.11765rem 0 .35294rem}.markdown table thead{height:.58824rem;background:linear-gradient(-90deg,#1186de,#0064c2)}.markdown table thead tr{line-height:.58824rem;font-size:.18824rem;font-weight:700;color:#fff}.markdown table thead tr th{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr{line-height:.58824rem;font-size:.18824rem;color:#7d7d7d}.markdown table tbody tr td{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr:nth-child(odd){background-color:#fbfcfe}.markdown table tbody tr:nth-child(2n){background-color:#edf4fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table{border:.01176rem solid #e6ebf2;border-collapse:separate;border-spacing:0;border-radius:.07059rem;overflow:hidden;box-shadow:none}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead{height:auto;background:#1f6fe5}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr{border:0;line-height:1.4;font-size:.17647rem;font-weight:600;color:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr th{padding:.10588rem .17647rem;border:0;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr{border:0;line-height:1.5;color:#2c2f36}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td{padding:.10588rem .17647rem;border:0;border-right:.01176rem solid #e6ebf2;border-bottom:.01176rem solid #e6ebf2;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td:last-child{border-right:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(odd){background:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(2n){background:#f7f9fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:last-child td{border-bottom:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:hover{background:#eef3ff}.markdown .compare-table-container .table-container table thead{background:#fff!important}.markdown .compare-table-container .table-container table thead th{color:#2f495e;text-align:center!important;vertical-align:bottom}.markdown .compare-table-container .table-container table thead th a{align-items:center}.markdown .compare-table-container .table-container table thead th img{display:block;width:1.76471rem;height:1.76471rem;-o-object-fit:contain;object-fit:contain;margin:0 auto .35294rem}.markdown .compare-table-container .table-container table thead th:first-child{text-align:center!important;vertical-align:middle}.markdown .compare-table-container .table-container table tbody td:first-child,.markdown .compare-table-container .table-container table tbody td:not(:first-child){text-align:center!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(odd):hover{background:#fff!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(2n):hover{background:#f7f9fc!important}.markdown .table-text-align-left table td,.markdown .table-text-align-left table th{text-align:left}.markdown .table-text-align-right table td,.markdown .table-text-align-right table th{text-align:right}.markdown .markdown-ol li{list-style-type:decimal}.markdown .error,.markdown .tip,.markdown .warn{font-size:.21176rem;border-bottom-right-radius:.02353rem;margin:.11765rem .11765rem .11765rem 0;position:relative;background-color:#fff;box-shadow:.02353rem 0 .08235rem .01176rem #efefef;display:flex;flex-direction:column;color:#838383;font-size:.18824rem;font-weight:400;line-height:.37647rem;border-radius:.07059rem;overflow:hidden}.markdown .error .error-content,.markdown .error .tip-content,.markdown .error .warn-content,.markdown .tip .error-content,.markdown .tip .tip-content,.markdown .tip .warn-content,.markdown .warn .error-content,.markdown .warn .tip-content,.markdown .warn .warn-content{padding:.23529rem}.markdown .error .tip-title,.markdown .tip .tip-title,.markdown .warn .tip-title{height:.41176rem;background-color:rgba(35,141,251,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#238dfb}.markdown .error .warn-title,.markdown .tip .warn-title,.markdown .warn .warn-title{height:.41176rem;background-color:rgba(253,184,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#c69000}.markdown .error .error-title,.markdown .tip .error-title,.markdown .warn .error-title{height:.41176rem;background-color:rgba(253,45,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#ff1616}.markdown .tip:before{background-image:url(/assets/tip.svg)}.markdown .tip:before,.markdown .warn:before{content:"";position:absolute;width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .warn:before{background-image:url(/assets/warning.svg)}.markdown .error:before{content:"";position:absolute;background-image:url(/assets/error.svg);width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .tip{border-left:.07059rem solid #238dfb}.markdown .warn{border-left:.07059rem solid #fdb802}.markdown .error{border-left:.07059rem solid rgba(253,2,2,.83922)}.markdown .learn{display:flex;grid-column:auto;width:100%;height:2.07059rem;margin:.09412rem 0;overflow:hidden;background:#fff;border:.01176rem solid #d3dde9;border-radius:.07059rem;transition:border-color .2s ease,box-shadow .2s ease,transform .2s ease}.markdown .learn:hover{border-color:#8ab4eb;box-shadow:0 .04706rem .14118rem rgba(31,111,229,.1);transform:translateY(-.01176rem)}.markdown .learn:hover .learn-contents{background:#f6f9fe}.markdown .learn .learn-img{flex:0 0 42%;min-height:0;position:relative;overflow:hidden;text-align:center;background:#f7f9fc;border-right:.01176rem solid #e6ebf2}.markdown .learn .learn-img img{display:block;width:100%;max-width:none;box-shadow:none;margin:0;height:100%;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;font-size:.09412rem}.markdown .learn .learn-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.markdown .learn .learn-contents{flex:1;min-width:0;padding:.23529rem;position:relative;display:flex;flex-direction:column;justify-content:center;background:#fbfcfe;transition:background-color .2s ease}.markdown .learn .learn-contents .learn-title{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:2;font-size:.21176rem;font-weight:600;line-height:.29412rem}.markdown .learn .learn-contents .learn-title a{color:#1f6fe5}.markdown .learn .learn-contents .learn-desc{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:3;margin-top:.09412rem;font-size:.18824rem;font-weight:400;color:#5d6673;line-height:.28235rem}.markdown .learn [\:not-has\(\%2B.learn\)]{grid-column:1/-1}.markdown .learn :not(:has(+.learn)){grid-column:1/-1}.markdown .learn [\:not-has\(\%2B.learn\)] .learn-img{flex-basis:2.82353rem}.markdown .learn :not(:has(+.learn)) .learn-img{flex-basis:2.82353rem}.mobile .markdown{grid-template-columns:minmax(0,1fr)}.mobile .markdown p{font-size:.21176rem}.mobile .markdown .learn{flex-direction:row;height:1.88235rem;max-width:none}.mobile .markdown .learn .learn-img{flex:0 0 40%;width:auto;min-height:0;aspect-ratio:auto;border-right:.01176rem solid #e6ebf2;border-bottom:0}.mobile .markdown .learn .learn-contents{padding:.14118rem .16471rem}.mobile .markdown .learn .learn-contents .learn-title{font-size:.18824rem;line-height:.25882rem;-webkit-line-clamp:2}.mobile .markdown .learn .learn-contents .learn-desc{margin-top:.07059rem;font-size:.16471rem;line-height:.24706rem;-webkit-line-clamp:3}@media screen and (max-width:900px){.markdown{grid-template-columns:minmax(0,1fr)}.markdown .learn .learn-img{flex-basis:2.82353rem}}.mobile video{width:100%;margin-bottom:.35294rem}.mobile .video-iframe{margin:.23529rem 0;height:5.88235rem}.mobile .video-iframe iframe{width:100%;height:100%}.easyloader-box{display:flex;flex-direction:row;width:100%}.easyloader-box>div{position:relative;width:50%;overflow:hidden}.easyloader-box p{margin:.11765rem .29412rem;color:#fff}.easyloader-box p:last-child{overflow-y:scroll;height:20%;font-size:.11765rem}.easyloader-mask{position:absolute;right:0;bottom:.07059rem;height:100%;width:100%;background-color:#000;opacity:.7;transition:all .3s;display:flex;flex-direction:column;justify-content:center;display:none}.easyloader-mask a{margin-top:.58824rem;text-align:center}.video_play{bottom:-100%}.easyloader-btn{position:absolute;display:flex;flex-direction:row;justify-content:space-around;bottom:7%;width:100%;padding:0 .23529rem;font-size:.23529rem}.easyloader-btn a{width:1.05882rem;text-align:center;padding:.02353rem .11765rem;background-color:#007bff;color:#fff!important;border-radius:.11765rem;font-size:.17647rem}.easyloader-btn a:hover{background-color:#45a9ff}@media screen and (max-width:768px){.easyloader-box{flex-direction:column;width:100%}.easyloader-box>div{width:100%}}.code-block-wrapper{display:flex;flex-direction:column;position:relative;margin:.16471rem 0 .23529rem;border:.01176rem solid #dfe5ec;border-radius:.07059rem;overflow:hidden;background:#f7f9fb}.code-block-header{display:flex;justify-content:space-between;align-items:center;min-height:.44706rem;padding:.04706rem .14118rem;background:#f0f3f6;border-bottom:.01176rem solid #dfe5ec}.code-block-header .language-label{font-size:.15294rem;color:#526579;font-weight:500}.copy-all-btn{display:flex;align-items:center;grid-gap:.11765rem;gap:.11765rem;justify-content:center;background:0 0;border:none;border-radius:.05882rem;padding:.07059rem;font-size:.16471rem;cursor:pointer;transition:all .2s;width:.37647rem;height:.37647rem;color:#526579}.copy-all-btn svg{width:100%;height:100%}.copy-all-btn code{display:none}.copy-all-btn:hover{color:#1769aa;background:#e4ebf2}.copy-all-btn.focus-visible,.copy-all-btn:focus-visible{color:#1769aa;background:#e4ebf2;outline:.02353rem solid #1769aa;outline-offset:.02353rem}.code-block-container{display:flex;overflow:auto;background:#f7f9fb;align-items:flex-start}.code-block-wrapper.code-block-limited .code-block-container,.code-block-wrapper.code-block-limited .code-line-container{max-height:560px;max-height:var(--code-max-height,560px);overflow:auto;transition:max-height .35s ease}.code-block-wrapper:not(.is-collapsed).code-block-limited .code-block-container,.code-block-wrapper:not(.is-collapsed).code-block-limited .code-line-container{max-height:16.47059rem}.code-toggle-btn{display:flex;align-items:center;justify-content:center;width:100%;min-height:.49412rem;padding:.09412rem .14118rem .11765rem;border:0;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(240,244,249,.96));color:#6b7f93;cursor:pointer;transition:background .2s ease,color .2s ease;position:relative;z-index:2}.code-toggle-btn.focus-visible,.code-toggle-btn:focus-visible,.code-toggle-btn:hover{outline:0;color:#2d7be9;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(228,238,248,.98))}.code-toggle-icon{font-size:.17647rem;line-height:1;transition:transform .25s ease,color .2s ease}.code-block-wrapper:not(.is-collapsed) .code-toggle-icon,.code-toggle-icon{transform:translateY(-.01176rem)}.code-block-fade{position:absolute;left:0;right:0;bottom:.49412rem;height:1.29412rem;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(247,249,251,.96));pointer-events:none;transition:opacity .2s ease;z-index:1}.code-block-wrapper.is-collapsed .code-block-fade{opacity:1}.code-block-wrapper:not(.is-collapsed) .code-block-fade{opacity:0}.markdown .code-block-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-block-container code.hljs{margin:0!important;padding:0!important;border-radius:0;background:0 0;line-height:.32941rem;font-size:.18824rem;white-space:pre}.markdown .code-line-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-line-container code.hljs{margin:0!important;padding:0!important;line-height:.32941rem;font-size:.18824rem;white-space:pre;width:100%;border-radius:0;background-color:transparent}.code-line-container{display:flex;background:#f7f9fb;align-items:center;position:relative;padding:.18824rem .21176rem}.code-line-container .copy-all-btn{opacity:.45;position:absolute;top:.11765rem;right:.11765rem;transition:all .2s}.code-line-container pre{overflow-x:auto}.code-line-container:hover .copy-all-btn,.code-line-container[focus-within] .copy-all-btn{opacity:1}.code-line-container:focus-within .copy-all-btn,.code-line-container:hover .copy-all-btn{opacity:1}@media (hover:none){.code-line-container .copy-all-btn{opacity:1}.markdown .learn:hover{border-color:#d3dde9;box-shadow:none;transform:none}.markdown .learn:hover .learn-contents{background:#fbfcfe}}.line-numbers{padding:.11765rem .09412rem;text-align:right;background:#f3f6f9;color:#8491a0;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;border-right:.01176rem solid #dfe5ec;font-family:SourceCodePro,Microsoft YaHei,sans-serif;line-height:.32941rem;min-width:.51765rem}.line-number{display:block;height:.32941rem}.code-content{flex:1;overflow:auto;padding:.11765rem .17647rem;line-height:.32941rem}.code-block-container,.code-content,.code-line-container pre{scrollbar-color:#c5cfda transparent;scrollbar-width:thin}.code-block-container::-webkit-scrollbar,.code-content::-webkit-scrollbar,.code-line-container pre::-webkit-scrollbar{width:.09412rem;height:.09412rem}.code-block-container::-webkit-scrollbar-thumb,.code-content::-webkit-scrollbar-thumb,.code-line-container pre::-webkit-scrollbar-thumb{background:#c5cfda;border-radius:.04706rem}.code-block-container::-webkit-scrollbar-track,.code-content::-webkit-scrollbar-track,.code-line-container pre::-webkit-scrollbar-track{background:0 0}.code-line{display:block;min-height:.32941rem;line-height:.32941rem;white-space:pre;font-weight:700;font-family:SourceCodePro,Microsoft YaHei,sans-serif}.code-line:hover{background-color:#eaf1f7;cursor:pointer}pre code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;font-size:.18824rem;overflow-y:auto;font-family:SourceCodePro;display:block;width:100%;color:#263445;line-height:.32941rem}code.hljs{background:0 0}pre{position:relative}pre .copy-btn{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;opacity:0;position:absolute;right:.05882rem;top:.05882rem;cursor:pointer;padding:.05882rem;border-radius:.03529rem;transition:.3s;background:hsla(0,0%,100%,.2);width:1.52941rem;height:.58824rem;color:#0064c2}pre .copy-btn:active{background:hsla(0,0%,99.2%,.575)}pre .copy-btn .icon{width:.35294rem;position:absolute;left:70%;top:70%;transform:translate(-50%,-50%)}pre .copy-success-text{color:#fff;position:absolute;font-size:.14118rem;top:.70588rem;font-weight:200;font-family:SourceCodePro,Microsoft YaHei;-webkit-animation:successCopy .5s ease 1 both;animation:successCopy .5s ease 1 both;color:#0064c2}@-webkit-keyframes successCopy{0%{right:0}to{right:.29412rem}}@keyframes successCopy{0%{right:0}to{right:.29412rem}}pre:hover .copy-btn{opacity:1}.files_download{display:flex;flex-direction:row;justify-content:space-evenly;flex-wrap:wrap;margin:.52941rem}.files_download .item{display:flex;justify-content:center;width:2.35294rem;box-shadow:.04706rem .04706rem .08235rem 0 #cecece;transition:all .25s ease}.files_download .item:hover{transform:scale(1.2)}.card-container{display:flex;justify-content:flex-start;margin-bottom:.35294rem;align-items:flex-start}.card-container .card-item{margin:.23529rem;width:3.52941rem;display:flex;flex-direction:column;justify-content:center;align-items:center;color:#fff;transition:all .25s ease}.card-container .card-item .card-cover{height:1.76471rem;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1)}.card-container .card-item .card-cover,.card-container .card-item .card-cover-img{width:100%;display:flex;align-items:center;justify-content:center;font-size:.28235rem;font-weight:700;margin-bottom:.11765rem;border-radius:.11765rem}.card-container .card-item .card-cover-img{position:relative}.card-container .card-item .card-cover-img .card-cover-content{display:none;padding:.11765rem}.card-container .card-item .card-cover-img .card-cover-content .card-cover-btn{display:block;text-align:center;background-color:#0064c2;color:#fff;font-size:.2rem;padding:.11765rem .17647rem;border-radius:.04706rem}.card-container .card-item .card-cover-img img{width:100%;box-shadow:none;margin:0}.card-container .card-item .card-cover-img:hover .card-cover-content{display:flex;flex-direction:column;justify-content:space-around;align-items:center;position:absolute;top:0;left:0;bottom:0;right:0;background-color:rgba(0,0,0,.5098)}.card-container .card-item .card-desc{padding:.17647rem;text-align:center;font-size:.17647rem;color:#2f495e}.card-container .card-item .card-desc a{display:block;text-align:left;color:#333;line-height:.23529rem}.card-container .card-item .card-desc a:hover{text-decoration:underline;color:#238dfb}.card-container .card-item:hover{transform:translateY(-.05882rem)}.card-container .linear-blue{background:linear-gradient(45deg,#09f,#6cf)}.card-container .linear-gray{background:linear-gradient(45deg,#f2f2f2,#ccc);color:#333}.card-container .linear-orange{background:linear-gradient(45deg,#fc0,#f90)}.card-container-video{display:flex;flex-wrap:wrap;grid-gap:.23529rem;gap:.23529rem;margin:.47059rem 0}.card-container-video li{list-style-type:none}.card-container-video .card-item-video{width:22%;position:relative;border-radius:.07059rem;overflow:hidden;transition:transform .3s ease;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1);background-color:#fff}.card-container-video .card-item-video:hover{transform:translateY(-.05882rem);box-shadow:0 .09412rem .18824rem rgba(0,0,0,.15)}.card-container-video .card-item-video:hover .card-cover-content{opacity:1}.card-container-video .card-item-video .card-cover-img{position:relative;width:100%;padding-top:56.25%;background-color:#e7e7e7;overflow:hidden}.card-container-video .card-item-video .card-cover-img img{position:absolute;top:50%;left:50%;width:100%;height:100%;-o-object-fit:cover;object-fit:cover;transform:translate(-50%,-50%);min-width:100%;min-height:100%;transition:transform .3s ease;margin:0}.card-container-video .card-item-video .card-desc-video{padding:.11765rem;text-align:center;font-weight:700}.card-container-video .card-item-video .card-cover-content{position:absolute;top:0;left:0;width:100%;height:100%;display:flex;justify-content:center;align-items:center;background-color:rgba(0,0,0,.5);opacity:0;transition:opacity .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn{display:inline-block;padding:.09412rem .18824rem;margin:0 .11765rem;background-color:#fb7299;color:#fff;border-radius:.04706rem;text-decoration:none;font-size:.16471rem;transition:background-color .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn.youtube{background-color:#f03}.card-container-video .card-item-video .card-cover-content .card-cover-btn.bilibili{background-color:#ff85ad}.mobile .card-item-video{width:40%}.mobile .card-desc-video{font-size:.29412rem}.directory-links-container{display:flex;flex-direction:column}.directory-links-item{page-break-inside:avoid;-moz-column-break-inside:avoid;break-inside:avoid;margin:.11765rem;padding:.17647rem;border-radius:.05882rem;box-shadow:0 0 .05882rem rgba(0,0,0,.1)}.directory-links-body{display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(3.52941rem,1fr));position:relative}.directory-links-item h3{margin-top:0;margin-bottom:.11765rem}.directory-links-item ul{list-style-type:none;padding:0;margin:.18824rem .11765rem}.directory-links-item ul li{margin-bottom:.05882rem}.directory-links-item ul li a{text-decoration:none;color:#333}.directory-links-item ul li a:hover{text-decoration:underline;color:#238dfb}.header-nav .dropdown-icon-wrapper,.pc .nav-dropdown .dropdown-content-right,.pc .nav-dropdown .dropdown-image .image-button{display:flex;justify-content:center;align-items:center}.pc .header-nav-ul .header-nav-item a:hover{color:#0064c2}.mobile .mobile-nav-icon,.mobile .mobile-return-icon{background-repeat:no-repeat;background-size:100% 100%}header{width:100%;position:relative;background-color:#fff;border-bottom:.01176rem solid #e5e5e5;overflow:visible}.header-container{position:relative;margin:0 auto;padding:0 1.17647rem 0 0;width:15.64706rem;height:.70588rem;display:flex;align-items:center;justify-content:flex-end;font-size:.25882rem}.header-container .logo{position:absolute;left:.08235rem;display:block;width:2.08235rem;height:.41176rem;font-size:0;line-height:1;cursor:pointer}.header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.header-nav .dropdown-icon-wrapper{margin-right:.18824rem;width:.25882rem;height:.25882rem}.header-nav .dropdown-icon-wrapper .dropdown-icon{width:auto;height:auto;max-width:100%;max-height:100%;font-size:0}.language-option-box{position:absolute;height:.70588rem;right:-.65882rem;font-size:0;background-color:#fff}.language-option-box .icon{margin-right:.07059rem;width:.2rem;height:auto;color:#434343}.language-option-box .current-language{height:calc(100% - .02353rem);color:#434343;font-size:.22353rem;font-weight:700;display:flex;align-items:center;cursor:pointer;box-sizing:content-box}.language-option-box .language-dropdown-wrapper{display:none;position:fixed;top:.70588rem;padding-top:.11765rem;box-sizing:border-box;width:19.76471rem;left:50%;transform:translateX(-50%);z-index:99999}.language-option-box .language-dropdown-wrapper .language-dropdown{position:absolute;top:.11765rem;right:1.29412rem;width:1.52941rem;color:#434343;background-color:#fff;border-radius:.11765rem;overflow:hidden;box-shadow:0 .09412rem .28235rem rgba(0,0,0,.08);opacity:0;transition:opacity .2s ease}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item{font-size:.21176rem;font-weight:700;line-height:.54118rem;text-align:center;cursor:pointer}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item:hover{color:#0064c2}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item.active{background-color:#dedede}.language-option-box:hover .current-language{border-bottom:.03529rem solid #0064c2}.language-option-box:hover .current-language .header-arrow-btn{transform:rotate(-180deg)}.language-option-box:hover .language-dropdown-wrapper{display:block}.language-option-box:hover .language-dropdown{opacity:1}.disabledHover{cursor:auto!important}.disabledHover a:hover,.disabledHover li:hover,.disabledHover:hover{color:#434343!important}.pc .show-mb{display:none}.pc .header-nav{height:100%;display:flex;align-items:center}.pc .header-nav-ul{height:100%;display:flex;flex-direction:row}.pc .header-nav-ul .header-nav-item{margin-right:.30588rem;padding-left:.23529rem;height:calc(100% - .02353rem);display:flex;align-items:center;font-size:.22353rem;font-weight:700;color:#434343;cursor:pointer;box-sizing:content-box}.pc .header-nav-ul .header-nav-item.active,.pc .header-nav-ul .header-nav-item:hover{border-bottom:.03529rem solid #0064c2}.pc .header-nav-ul .header-nav-item.active .header-arrow-btn,.pc .header-nav-ul .header-nav-item:hover .header-arrow-btn{transform:rotate(-180deg)}.pc .header-nav-ul .header-nav-item:last-of-type{margin-right:0}.pc .header-nav-ul .header-nav-item a{position:relative;color:#434343}.pc .header-arrow-btn{margin-left:.07059rem;width:.11765rem;height:auto;color:#3a3a3a;font-size:0;transition:all .3s ease}.pc .nav-dropdown{position:fixed;left:50%;width:16.70588rem;max-width:calc(100vw - .47059rem);height:3.52941rem;display:flex;transform:translateX(-50%);background-color:#fff;border-radius:.23529rem;z-index:9999}.pc .nav-dropdown .dropdown-content-left{position:relative;padding:.47059rem .32941rem 0;width:calc(100% - 7.45882rem);height:100%;display:flex;justify-content:space-around}.pc .nav-dropdown .dropdown-content-right{width:7.45882rem;height:100%;background-color:#eee;border-radius:0 .23529rem .23529rem 0}.pc .nav-dropdown .dropdown-image{position:relative;width:7.05882rem;border-radius:.23529rem;font-size:0;overflow:hidden}.pc .nav-dropdown .dropdown-image img{width:100%;height:auto}.pc .nav-dropdown .dropdown-image .image-button{position:absolute;left:50%;bottom:.35294rem;transform:translateX(-50%);width:2.35294rem;height:.42353rem;font-size:.18824rem;color:#fff;background-color:#0064c2;border-radius:.04706rem}.pc .nav-dropdown .dropdown-image .image-button:hover{background-color:#058ce6}.pc .nav-dropdown .dropdown-image .image-button .image-icon{margin-right:.11765rem;width:.24706rem;height:auto}.pc .nav-dropdown .dropdown-item{width:3.29412rem;display:flex;flex-direction:column;flex-wrap:wrap}.pc .nav-dropdown .dropdown-item-li{padding-left:.16471rem;display:flex;align-items:center;font-size:.23529rem;font-weight:700;line-height:.70588rem;color:#434343}.pc .nav-dropdown .dropdown-item-li.border{border-bottom:.02353rem solid #dbdbdb}.pc .nav-dropdown .dropdown-item-li:hover{color:#0064c2}.pc .nav-dropdown .dropdown-item-child{margin-top:.18824rem;padding-left:.18824rem;display:flex;flex-direction:column}.pc .nav-dropdown .dropdown-child-li{margin-bottom:.14118rem;display:flex;align-items:center;font-size:.21176rem;font-weight:500;white-space:nowrap;color:#434343}.pc .nav-dropdown .dropdown-child-li:hover{color:#0064c2}.pc header #store{height:4.70588rem}.pc header #store .dropdown-item:first-child{width:2.21176rem}.pc header #store .dropdown-item:first-child .dropdown-child-li:nth-child(2) .dropdown-icon-wrapper{height:.32941rem}.pc header #store .dropdown-item:nth-child(2){width:4.65882rem;height:3.05882rem;border-bottom:.02353rem solid #dbdbdb}.pc header #store .dropdown-item:nth-child(2) .dropdown-item-child{width:90%;height:2rem;flex-wrap:wrap}.pc header #store .dropdown-item:nth-child(3),.pc header #store .dropdown-item:nth-child(4){position:absolute;bottom:.47059rem}.pc header #store .dropdown-item:nth-child(3){right:3.38824rem;width:2.04706rem}.pc header #store .dropdown-item:nth-child(3) .dropdown-icon-wrapper{margin-right:.14118rem;width:.32941rem}.pc header #store .dropdown-item:nth-child(4){right:.75294rem;width:2.58824rem}.pc header #software{height:4rem}.pc header #software .dropdown-content-left{width:calc(100% - 6.03529rem)}.pc header #software .dropdown-content-right{width:6.03529rem}.pc header #software .dropdown-image{width:5.58824rem}.pc header #software .dropdown-item:first-child{width:3.17647rem}.pc header #software .dropdown-item:nth-child(2){width:2.82353rem}.pc header #software .dropdown-item:nth-child(3){width:2.91765rem}.pc header #document{height:4.47059rem}.pc header #document .dropdown-content-left{width:100%}.pc header #document .dropdown-item:first-child .dropdown-item-child,.pc header #document .dropdown-item:nth-child(2) .dropdown-item-child{height:2rem;flex-wrap:wrap}.pc header #document .dropdown-item:first-child{width:4.65882rem}.pc header #document .dropdown-item:nth-child(2){width:5.01176rem}.pc header #document .dropdown-item:nth-child(3){width:3.76471rem}.pc header #aboutus{height:4.21176rem}.pc header #contact{height:1.05882rem;background-color:transparent}.pc header #contact .dropdown-content-left{position:absolute;padding:.09412rem 0;right:1.29412rem;width:2rem;height:1.05882rem;flex-direction:column;background-color:#fff;border-radius:.11765rem}.pc header #contact .dropdown-item{width:100%}.pc header #contact .dropdown-item .dropdown-item-li{padding-left:0;width:100%;justify-content:center;font-size:.21176rem;line-height:.42353rem}.mobile .show-pc,.mobile .snize-sticky-searchbox{display:none}.mobile header{height:1.10588rem;border-bottom:unset}.mobile .header-container{padding:0 .35294rem;width:100%;max-width:100%;height:1.10588rem;justify-content:unset;z-index:9999;box-shadow:0 0 .18824rem 0 hsla(0,0%,51.4%,.15)}.mobile .header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.mobile .mobile-nav-icon{width:.54118rem;height:.54118rem;background-image:url(/assets/menu.png);transition:all .28s ease}.mobile .mobile-nav-icon.active{transform:rotate(90deg)}.mobile .mobile-return-icon{position:absolute;left:1.2rem;width:.32941rem;height:.32941rem;background-image:url(/assets/return.png)}.mobile .logo{left:50%;width:2.47059rem;height:.48235rem;transform:translateX(-50%)}.mobile .header-nav{display:none;position:absolute;top:1.10588rem;left:0;padding:.18824rem 0 1.01176rem;width:5.17647rem;max-width:100%;background-color:#fff;z-index:9998}.mobile .header-nav.show{display:block}.mobile .header-nav-ul{margin-bottom:.23529rem}.mobile .header-nav-ul .header-nav-item{position:relative;padding-left:.47059rem;height:1.10588rem;font-size:.36471rem;font-weight:400;line-height:1.10588rem}.mobile .header-nav-ul .header-nav-item,.mobile .header-nav-ul .header-nav-item a{color:#434343}.mobile .header-nav-ul .header-nav-item.selected{background-color:#f7f7f7}.mobile .header-nav-ul .header-nav-item.active .header-mbnav-btn{transform:rotate(90deg)}.mobile .header-nav-ul .header-nav-item.active+.nav-dropdown{display:block}.mobile .header-mbnav-btn{position:absolute;width:.58824rem;height:.58824rem;top:.23529rem;right:.23529rem;background-image:url(/assets/arrow3.png);background-repeat:no-repeat;background-size:50% 50%;background-position:50%}.mobile .nav-dropdown{display:none;position:relative}.mobile .nav-dropdown .dropdown-content-left{width:100%}.mobile .nav-dropdown .dropdown-icon-wrapper{width:.47059rem;height:.47059rem}.mobile .nav-dropdown .dropdown-item-li{padding-left:.71765rem;width:100%;height:.88235rem;display:flex;align-items:center;font-size:.32941rem;font-weight:400;color:#434343}.mobile .nav-dropdown .dropdown-child-li{padding-left:.89412rem;width:100%;height:.82353rem;display:flex;align-items:center;font-size:.30588rem;line-height:.82353rem;white-space:nowrap;color:#434343}.mobile .language-option-box{height:1.10588rem;right:.25882rem}.mobile .language-option-box .icon{width:.35294rem}.mobile .language-option-box .current-language{font-size:.30588rem;font-weight:500}.mobile .language-option-box .language-dropdown-wrapper{width:100%;top:1.10588rem;padding-top:.11765rem;box-sizing:border-box}.mobile .language-option-box .language-dropdown{right:.11765rem;width:2.23529rem}.mobile .language-option-box .language-dropdown .language-item{font-size:.35294rem;font-weight:500;line-height:.70588rem}.header-nav-dd-pc-enter-active,.header-nav-dd-pc-leave-active{transition:opacity .2s ease-out,transform .22s cubic-bezier(.4,0,.2,1)}.header-nav-dd-pc-enter,.header-nav-dd-pc-leave-to{opacity:0;transform:translateX(-50%) translateY(-.09412rem)!important}.header-nav-dd-pc-enter-to,.header-nav-dd-pc-leave{opacity:1;transform:translateX(-50%) translateY(0)!important}.header-nav-dd-mb-enter-active,.header-nav-dd-mb-leave-active{transition:opacity .18s ease-out}.header-nav-dd-mb-enter,.header-nav-dd-mb-leave-to{opacity:0}.viewer-open .mobile .header-container,.viewer-open .mobile .language-dropdown-wrapper,.viewer-open .mobile .language-option-box{z-index:1!important}.viewer-open .mobile .language-option-box{pointer-events:none}.title-level2{height:.32941rem;font-size:.35294rem;font-weight:400;color:#434343;line-height:.32941rem;padding-left:.22353rem;position:relative;display:flex;justify-content:space-between;margin:.58824rem 0}.title-level2 .title-level2-desc{font-size:.18824rem;font-weight:400}.title-level2:after{content:"";width:.04706rem;height:.35294rem;background:#0064c2;position:absolute;left:0}.title-level3{height:.27059rem;font-size:.29412rem;font-weight:400;color:#434343;line-height:.27059rem;padding-left:.14118rem;position:relative;display:flex;justify-content:space-between;margin:.47059rem 0 .35294rem}.title-level3 .title-level3-desc{font-size:.14118rem;font-weight:400}.pc .product-list-container .Products{display:flex;flex-wrap:wrap;margin-bottom:.70588rem}.pc .product-list-container .ProductItem{border-top:.01176rem solid #e5e5e5;border-bottom:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(2n),.pc .product-list-container .ProductItem:nth-child(2n-1){border-right:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(3n){border-right:0 solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(n+4){border-top:0 solid #e5e5e5}.pc .product-list-container .ProductItem{height:4.51765rem;width:4.65882rem;text-align:center;position:relative}.pc .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.pc .product-list-container .ProductItem .ProductPic{text-align:center;width:2.35294rem;height:2.35294rem}.pc .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.pc .product-list-container .ProductItem .ProductName{margin-top:.11765rem;line-height:.29412rem;height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343}.pc .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto .17647rem;width:2.47059rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.23529rem;text-overflow:clip;overflow:hidden}.pc .product-list-container .ProductItem .product-btn-group{width:1.76471rem;height:.35294rem;border-radius:.17647rem;margin:auto;display:flex}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.29412rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.35294rem;font-size:.18824rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.47059rem;height:.35294rem;background-size:.23529rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.pc .product-list-container .ProductLinks{padding:0 .17647rem;font-size:.18824rem;display:grid;justify-content:start;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(2.82353rem,1fr));position:relative;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink:hover{color:#409eff;-webkit-text-decoration-line:underline;text-decoration-line:underline}.mobile .product-list-container{text-align:left}.mobile .product-list-container .ProductItem{text-align:center;height:5.17647rem;width:50%;border:.02353rem solid #e5e5e5;background-color:#fff;position:relative}.mobile .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.mobile .product-list-container .ProductItem .ProductPic{margin:.11765rem auto;text-align:center;width:2.82353rem;height:2.82353rem}.mobile .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.mobile .product-list-container .ProductItem .ProductName{height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343;line-height:.28235rem}.mobile .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto;display:block;width:2.36471rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.25882rem;overflow:hidden}.mobile .product-list-container .ProductItem .product-btn-group{width:2.35294rem;height:.47059rem;border-radius:.17647rem;margin:auto;display:flex}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.64706rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.47059rem;font-size:.23529rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.70588rem;height:.47059rem;background-size:.29412rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.mobile .product-list-container .ProductLinks{padding:.11765rem .17647rem;font-size:.25882rem;display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fit,minmax(3.52941rem,1fr));position:relative;margin-bottom:.14118rem;background-color:#fff}.mobile .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.14118rem}.product-list-container.hideEol .ProductItem.EOL{display:none}.footer-email-input input::-webkit-input-placeholder{font-family:Microsoft YaHei,sans-serif}.subscribe-btn{display:flex;justify-content:center;align-items:center}.pc .footer-bottom-content a:hover,.pc .footer-nav-li a:hover{color:#0064c2}.subscribe-btn:hover{background-color:#0074e1}.mobile .footer-nav-btn{background-repeat:no-repeat;background-size:100% 100%}.footer-container{width:100%;color:#fff;background-color:#000}.footer-content-wrap{height:100%;display:flex;align-items:center}.footer-email-title,.footer-qrcode-title{font-size:.32941rem;margin-bottom:.21176rem;font-weight:500;color:#fff}.footer-email-desc{font-weight:400;color:#f1f1f1}.footer-email-input{display:flex}.footer-email-input input{background:hsla(0,0%,60%,.55);border:.01176rem solid #0077c8;border-radius:.04706rem;padding:0 .23529rem;color:#fff;outline:0}.footer-email-input input::-webkit-input-placeholder{font-weight:400;color:#a0a0a0}.subscribe-btn{background:#0077c8;width:1.55294rem;height:.56471rem;font-size:.21176rem;font-weight:500;color:#fff;border-radius:.07059rem}.footer-follow{margin-top:.42353rem;width:90%}.footer-follow-ul{display:flex;flex-wrap:wrap}.footer-info-wrapper{margin-top:.47059rem;font-size:.16471rem;color:#a0a0a0}.footer-email-warning{margin-top:.11765rem;display:none;font-size:.18824rem;color:#ff2529}.footer-email-success{margin-top:.35294rem;margin-bottom:1.15294rem;display:none;font-size:.35294rem;color:#fff}.pc .footer-container{height:8.23529rem}.pc .footer-content-wrap{width:15.64706rem;margin:0 auto}.pc .footer-nav{padding:.70588rem 0 .11765rem;width:65%;height:100%;display:flex;flex-direction:column;flex-wrap:wrap}.pc .footer-nav-item{margin:0 0 .47059rem}.pc .footer-nav-title{margin-bottom:.18824rem;font-size:.29412rem;font-weight:500;color:#fff}.pc .footer-nav-title a{color:#fff}.pc .footer-nav-li{font-size:.21176rem;font-weight:400;color:#a0a0a0;line-height:.38824rem}.pc .footer-nav-li a{color:#a0a0a0;cursor:pointer}.pc .footer-right{width:35%;height:5.95294rem;padding:0 0 0 .47059rem}.pc .footer-email-title,.pc .footer-qrcode-title{margin-top:.14118rem}.pc .footer-email-desc{font-size:.21176rem;line-height:.32941rem;margin-bottom:.14118rem}.pc .footer-email-input input{width:3.71765rem;height:.56471rem;font-size:.21176rem;margin-right:.12941rem}.pc .footer-email-input input::-webkit-input-placeholder{font-size:.21176rem}.pc .footer-qrcode-list{display:flex}.pc .footer-qrcode-list .footer-qrcode-item{margin-right:.11765rem}.pc .footer-qrcode-list .footer-qrcode-img{width:1.88235rem;height:auto}.pc .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.pc .footer-qrcode-list .footer-qrcode-name{font-size:.21176rem;color:#a0a0a0}.pc .footer-follow-ul{width:100%}.pc .footer-follow-ul a{display:block;margin-right:.11765rem;margin-bottom:.11765rem;font-size:0}.pc .footer-follow-ul img{width:.58824rem;height:.58824rem}.pc .footer-address-info{line-height:.23529rem;margin:.05882rem 0}.pc .footer-info{line-height:.32941rem}.pc .footer-bottom{width:100%;height:.77647rem;background-color:#000}.pc .footer-bottom-content{margin:0 auto;padding:.23529rem .23529rem 0;width:16.07059rem;height:100%;display:flex;justify-content:space-between;font-size:.15294rem;font-weight:400;color:#a0a0a0;border-top:.01176rem solid #6d6d6d}.pc .footer-bottom-content a{display:inline-block;color:#a0a0a0;font-weight:400;font-size:.15294rem}.pc .terms-box{margin-left:.54118rem;display:flex}.pc .terms-box a{margin:0 .09412rem}.mobile .footer-container{height:11.76471rem}.mobile .footer-right{padding:0;width:100%}.mobile .footer-email-group,.mobile .footer-right{display:flex;flex-direction:column;align-items:center}.mobile .footer-email-title,.mobile .footer-qrcode-title{font-size:.58824rem;margin-bottom:.25882rem}.mobile .footer-email-success{font-size:.51765rem;margin-top:1.17647rem;margin-bottom:1.27059rem}.mobile .footer-email-desc{width:5.52941rem;font-size:.35294rem;line-height:.47059rem;text-align:center;margin-bottom:.75294rem}.mobile .footer-email-input{flex-direction:column;align-items:center}.mobile .footer-email-input input{width:7.35294rem;height:.70588rem;margin-bottom:.47059rem;font-size:.32941rem}.mobile .footer-email-input input::-webkit-input-placeholder{font-size:.32941rem}.mobile .subscribe-btn{width:2.75294rem;height:.70588rem;border-radius:.07059rem;font-size:.32941rem}.mobile .footer-email-warning{font-size:.29412rem;margin-top:.18824rem}.mobile .footer-qrcode-title{text-align:center}.mobile .footer-qrcode-list{display:flex}.mobile .footer-qrcode-list .footer-qrcode-item{margin-right:.35294rem}.mobile .footer-qrcode-list .footer-qrcode-img{width:3.05882rem;height:auto}.mobile .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.mobile .footer-qrcode-list .footer-qrcode-name{margin-top:.11765rem;font-size:.35294rem;color:#a0a0a0;text-align:center}.mobile .footer-follow{margin-top:.82353rem;width:100%}.mobile .footer-follow-ul{width:80%;margin:0 auto;justify-content:center}.mobile .footer-follow-ul a{margin-right:.23529rem}.mobile .footer-follow-ul a:nth-child(5){margin-right:0}.mobile .footer-follow-ul img{width:1.05882rem;height:1.05882rem}.mobile .footer-qrcode-img{width:2.82353rem;height:2.82353rem;margin:0 auto}.mobile .footer-qrcode-img img{width:100%;height:auto;max-height:100%}.mobile .footer-info-wrapper{width:95%;margin-top:.47059rem;font-size:.23529rem;text-align:center}.mobile .footer-address-info{line-height:.35294rem;margin:.05882rem 0}.mobile .footer-info{line-height:.44706rem}.mobile .footer-bottom{display:none}.mobile .footer-nav{background-color:#fff;border-top:.03529rem solid #eee}.mobile .footer-nav-item:nth-child(3) .footer-nav-title a{display:block}.mobile .footer-nav-title{position:relative;padding:0 0 0 .71765rem;font-size:.36471rem;line-height:1.10588rem;font-weight:500;color:#a6a6a6;height:1.10588rem;border-bottom:.03529rem solid #eee}.mobile .footer-nav-title a{color:#a6a6a6}.mobile .footer-nav-title.active .footer-nav-btn{transform:rotate(90deg)}.mobile .footer-nav-title.active+.footer-nav-ul{display:block}.mobile .footer-nav-btn{position:absolute;width:.2rem;height:.36471rem;top:.35294rem;right:.41176rem;background-image:url(/assets/arrow2.png)}.mobile .footer-nav-ul{display:none;border-bottom:.03529rem solid #eee}.mobile .footer-nav-li{font-size:.25882rem;font-weight:400;color:#a0a0a0;line-height:.65882rem;padding:0 0 0 .91765rem}.mobile .footer-nav-li a{color:#a0a0a0}.product-demo-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(2rem,1fr));grid-gap:.16471rem;gap:.16471rem;margin:.21176rem 0 .32941rem}.product-demo-item{display:flex;flex-direction:column;align-items:center;justify-content:flex-start;text-decoration:none;color:#1f2937;background:#fff;border:.01176rem solid #e5e7eb;border-radius:.14118rem;overflow:hidden;transition:transform .2s ease,border-color .2s ease;height:100%}.product-demo-item:hover{transform:translateY(-.03529rem);border-color:#93c5fd}.product-demo-item img{width:100%;height:1.41176rem;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;display:block;background:#f8fafc;box-shadow:none!important;flex-shrink:0}.product-demo-item span{display:block;width:100%;padding:.11765rem;font-size:.15294rem;line-height:1.4;font-weight:600;margin-top:auto;text-align:center}.scene-application-card{position:relative;display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.12fr);align-items:stretch;min-height:4rem;color:#0f172a;text-decoration:none;border-radius:.23529rem;overflow:hidden;background-color:#f8fafc;border:none;box-shadow:0 .21176rem .47059rem rgba(15,23,42,.1);border:.01176rem solid rgba(148,163,184,.22)}.scene-application-card--scene1{background-image:linear-gradient(180deg,rgba(15,23,42,.08),rgba(15,23,42,.56)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:50%}.scene-application-card--scene2{background-image:linear-gradient(180deg,rgba(15,23,42,.1),rgba(15,23,42,.58)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:64%}.scene-application-card:hover{color:#0f172a}.scene-application-card,.scene-application-card .scene-application-card__title,.scene-application-card p,.scene-application-card span:not(.scene-application-card__button){color:#0f172a!important}.scene-application-card__media{position:relative;display:flex;align-items:center;justify-content:center;min-height:100%;overflow:hidden;padding:.18824rem .21176rem .18824rem .14118rem;line-height:0}.scene-application-card__media img{flex:none;width:88%;max-width:4.94118rem;max-width:100%;height:auto;max-height:100%;display:block;margin:0!important;padding:0!important;border:.01176rem solid rgba(148,163,184,.34);border-radius:.16471rem;box-shadow:0 .11765rem .28235rem rgba(15,23,42,.16);vertical-align:top;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center}.scene-application-card__content{position:relative;z-index:1;display:flex;flex-direction:column;justify-content:center;grid-row-gap:.14118rem;row-gap:.14118rem;width:100%;max-width:5.17647rem;min-height:100%;padding:.32941rem .30588rem .28235rem;background:linear-gradient(180deg,hsla(0,0%,100%,.96),rgba(248,250,252,.9))}.scene-application-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-gap:.21176rem;gap:.21176rem;margin:.21176rem 0 .32941rem}.scene-application-card__title{margin:.09412rem 0 0;font-size:.32941rem;line-height:1.15;font-weight:700;text-align:center;color:#0f172a!important;text-shadow:none}.scene-application-card__desc{margin:0;font-size:.17647rem;line-height:1.6;text-align:center;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden;text-overflow:ellipsis;color:rgba(30,41,59,.9)!important;text-shadow:none}.scene-application-card__button{display:inline-flex;align-items:center;justify-content:center;align-self:center;margin-top:0;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content;min-width:1.22353rem;padding:.11765rem .18824rem;font-size:.16471rem;line-height:1;font-weight:600;white-space:nowrap;color:#fff!important;background:#2563eb;border-radius:11.75294rem;box-shadow:0 .09412rem .21176rem rgba(37,99,235,.28)}.scene-application-card .scene-application-card__button{color:#fff!important}.mobile .product-demo-grid{grid-template-columns:repeat(3,minmax(0,1fr));grid-gap:.09412rem;gap:.09412rem}.mobile .product-demo-item{border-radius:.09412rem}.mobile .product-demo-item img{height:auto;aspect-ratio:1/1;-o-object-fit:contain;object-fit:contain;-o-object-position:center;object-position:center;padding:.09412rem;box-shadow:none!important}.mobile .product-demo-item span{padding:.07059rem .07059rem .09412rem;font-size:.21176rem;line-height:1.4;text-align:center;word-break:break-word}.mobile .scene-application-card{grid-template-columns:1fr;grid-template-rows:2.35294rem minmax(0,1fr);min-height:4.58824rem;margin:0;border-radius:.16471rem}.mobile .scene-application-card__media{order:1;min-height:2.35294rem;padding:.11765rem .14118rem}.mobile .scene-application-card__media img{width:100%;max-width:none;max-height:none}.mobile .scene-application-grid{grid-template-columns:1fr;grid-gap:.16471rem;gap:.16471rem}.mobile .scene-application-card__content{order:2;max-width:none;justify-content:center;padding:.23529rem .21176rem;background:linear-gradient(180deg,hsla(0,0%,100%,.97),rgba(248,250,252,.93));grid-row-gap:.11765rem;row-gap:.11765rem}.mobile .scene-application-card__title{font-size:.25882rem;line-height:1.2;margin-top:.07059rem}.mobile .scene-application-card__desc{font-size:.15294rem;line-height:1.5;-webkit-line-clamp:4}.mobile .scene-application-card__button{min-width:1.17647rem;margin-top:.09412rem;padding:.10588rem .16471rem;font-size:.15294rem}.project-item{display:flex;height:1.96471rem;margin:.11765rem 0}.project-item .project-img{width:1.96471rem;height:1.96471rem;position:relative;overflow:hidden;text-align:center}.project-item .project-img img{height:100%;font-size:.09412rem}.project-item .project-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.project-item .project-contents{flex:1;background-color:#efefef;padding:0 .38824rem;position:relative;display:flex;flex-direction:column;justify-content:center}.project-item .project-contents .project-title{font-size:.25882rem;font-weight:700;line-height:.27059rem}.project-item .project-contents .project-title a{color:#238dfb}.project-item .project-contents .project-desc{margin-top:.15294rem;font-size:.22353rem;font-weight:400;color:#717171;line-height:.29412rem}.saerch-fliter-container{height:1.17647rem;border-bottom:.04706rem dashed #e5e5e5;display:flex}.saerch-fliter-container .search-fliter-title{font-size:.21176rem;font-weight:400;color:#434343;width:1.50588rem;margin-right:.58824rem}.saerch-fliter-container .search-fliter-options{flex:1;display:flex;flex-wrap:wrap}.saerch-fliter-container .search-fliter-options .fliter-option{font-size:.18824rem;font-weight:400;color:#959595;padding:0 .35294rem 0 0;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.saerch-fliter-container .search-fliter-options .fliter-option.active{color:#0064c2}.mobile .saerch-fliter-container{height:2.82353rem;margin-top:.35294rem}.dev-layout{flex-wrap:wrap;justify-content:space-between;margin-bottom:.70588rem;flex-direction:column}.dev-container,.dev-layout{display:flex;width:100%}.mobile .dev-container{flex-direction:column;min-height:60vh}.dev-info-container{margin:.70588rem .23529rem;display:flex;color:#5f5d5d;width:3.52941rem;overflow:hidden;flex-direction:column}.dev-info-container .dev-contents{display:flex;flex-direction:column;align-items:center;text-align:center}.dev-info-container .dev-title{font-size:.47059rem;padding:.35294rem}.dev-info-container .dev-desc{font-size:.18824rem;padding:.35294rem;line-height:.28235rem;font-weight:300;height:1.17647rem}.dev-info-container .dev-button{width:1.64706rem;height:.47059rem;background:#0064c2;border-radius:.05882rem;color:#fff;text-align:center}.dev-info-container .dev-banner{padding:.05882rem;overflow:hidden;border-radius:.11765rem}.dev-info-container .dev-banner img{box-shadow:0 0 .23529rem 0 #efefef;background-size:cover;width:5.29412rem;transition:all .25s ease;border-radius:.11765rem}.dev-info-container .dev-banner img:hover{transform:scale(1.1)}.mobile .dev-info-container{width:100%;flex-direction:row}@-webkit-keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@-webkit-keyframes fade-in{0%{opacity:0}to{opacity:1}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}@-webkit-keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}@keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}.float-icon-container{position:fixed;right:23PX;bottom:80PX;z-index:6;height:120PX;width:50PX}.float-icon-container .totop-icon{position:absolute;top:0;left:0}.float-icon-container .menu-icon{position:absolute;top:70PX;left:0}.float-icon-container .menu-icon.active,.float-icon-container .menu-icon.active:hover{background-color:#2f495e}.float-icon-container .menu-icon,.float-icon-container .totop-icon{width:50PX;height:50PX;display:flex;align-items:center;justify-content:center;border-radius:50%;background-color:#0870d1;box-shadow:0 0 .35294rem -.02353rem rgba(19,41,75,.14),0 .14118rem .15294rem -.02353rem rgba(19,41,75,.13),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.13),0 .02353rem .02353rem -.02353rem rgba(19,41,75,.12);cursor:pointer;z-index:200}.float-icon-container .menu-icon svg,.float-icon-container .totop-icon svg{width:50PX;height:50PX}.float-icon-container .menu-icon svg path,.float-icon-container .totop-icon svg path{fill:#fefefe}.float-icon-container .menu-icon:hover,.float-icon-container .totop-icon:hover{background-color:#058ce6}.markdown .hljs{color:#263445;background:0 0}.markdown .hljs-comment,.markdown .hljs-quote{color:#687789;font-style:normal}.markdown .hljs-addition,.markdown .hljs-keyword,.markdown .hljs-selector-tag{color:#b4233f;font-weight:500}.markdown .hljs-link,.markdown .hljs-literal,.markdown .hljs-number,.markdown .hljs-regexp{color:#1769aa}.markdown .hljs-doctag,.markdown .hljs-meta .hljs-meta-string,.markdown .hljs-string{color:#16705a}.markdown .hljs-name,.markdown .hljs-section,.markdown .hljs-selector-class,.markdown .hljs-selector-id,.markdown .hljs-title{color:#6f52a2}.markdown .hljs-attr,.markdown .hljs-attribute,.markdown .hljs-template-variable,.markdown .hljs-variable{color:#8a5a00}.markdown .hljs-built_in,.markdown .hljs-builtin-name,.markdown .hljs-class .hljs-title,.markdown .hljs-type{color:#9a4d16}.markdown .hljs-bullet,.markdown .hljs-meta,.markdown .hljs-meta .hljs-keyword,.markdown .hljs-selector-attr,.markdown .hljs-selector-pseudo,.markdown .hljs-subst,.markdown .hljs-symbol{color:#526579}.markdown .hljs-deletion{color:#b4233f}.markdown .hljs-formula{background:#eaf1f7}.markdown .hljs-emphasis{font-style:italic}.markdown .hljs-strong{font-weight:600}/*!
- * Viewer.js v1.11.6
- * https://fengyuanchen.github.io/viewerjs
- *
- * Copyright 2015-present Chen Fengyuan
- * Released under the MIT license
- *
- * Date: 2023-09-17T03:16:35.830Z
- */.viewer-close:before,.viewer-flip-horizontal:before,.viewer-flip-vertical:before,.viewer-fullscreen-exit:before,.viewer-fullscreen:before,.viewer-next:before,.viewer-one-to-one:before,.viewer-play:before,.viewer-prev:before,.viewer-reset:before,.viewer-rotate-left:before,.viewer-rotate-right:before,.viewer-zoom-in:before,.viewer-zoom-out:before{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAARgAAAAUCAYAAABWOyJDAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAALEgAACxIB0t1+/AAAABx0RVh0U29mdHdhcmUAQWRvYmUgRmlyZXdvcmtzIENTNui8sowAAAQPSURBVHic7Zs/iFxVFMa/0U2UaJGksUgnIVhYxVhpjDbZCBmLdAYECxsRFBTUamcXUiSNncgKQbSxsxH8gzAP3FU2jY0kKKJNiiiIghFlccnP4p3nPCdv3p9778vsLOcHB2bfveeb7955c3jvvNkBIMdxnD64a94GHMfZu3iBcRynN7zAOI7TG15gHCeeNUkr8zaxG2lbYDYsdgMbktBsP03jdQwljSXdtBhLOmtjowC9Mg9L+knSlcD8TNKpSA9lBpK2JF2VdDSR5n5J64m0qli399hNFMUlpshQii5jbXTbHGviB0nLNeNDSd9VO4A2UdB2fp+x0eCnaXxWXGA2X0au/3HgN9P4LFCjIANOJdrLr0zzZ+BEpNYDwKbpnQMeAw4m8HjQtM6Z9qa917zPQwFr3M5KgA6J5rTJCdFZJj9/lyvGhsDvwFNVuV2MhhjrK6b9bFiE+j1r87eBl4HDwCF7/U/k+ofAX5b/EXBv5JoLMuILzf3Ap6Z3EzgdqHMCuF7hcQf4HDgeoHnccncqdK/TvSDWffFXI/exICY/xZyqc6XLWF1UFZna4gJ7q8BsRvgd2/xXpo6P+D9dfT7PpECtA3cnWPM0GXGFZh/wgWltA+cDNC7X+AP4GzjZQe+k5dRxuYPeiuXU7e1qwLpDz7dFjXKRaSwuMLvAlG8zZlG+YmiK1HoFqT7wP2z+4Q45TfEGcMt01xLoNZEBTwRqD4BLpnMLeC1A41UmVxsXgXeBayV/Wx20rpTyrpnWRft7p6O/FdqzGrDukPNtkaMoMo3FBdBSQMOnYBCReyf05s126fU9ytfX98+mY54Kxnp7S9K3kj6U9KYdG0h6UdLbkh7poFXMfUnSOyVvL0h6VtIXHbS6nOP+s/Zm9mvyXW1uuC9ohZ72E9uDmXWLJOB1GxsH+DxPftsB8B6wlGDN02TAkxG6+4D3TWsbeC5CS8CDFce+AW500LhhOW2020TRjK3b21HEmgti9m0RonxbdMZeVzV+/4tF3cBpP7E9mKHNL5q8h5g0eYsCMQz0epq8gQrwMXAgcs0FGXGFRcB9wCemF9PkbYqM/Bas7fxLwNeJPdTdpo4itQti8lPMqTpXuozVRVXPpbHI3KkNTB1NfkL81j2mvhDp91HgV9MKuRIqrykj3WPq4rHyL+axj8/qGPmTqi6F9YDlHOvJU6oYcTsh/TYSzWmTE6JT19CtLTJt32D6CmHe0eQn1O8z5AXgT4sx4Vcu0/EQecMydB8z0hUWkTd2t4CrwNEePqMBcAR4mrBbwyXLPWJa8zrXmmLEhNBmfpkuY2102xxrih+pb+ieAb6vGhuA97UcJ5KR8gZ77K+99xxeYBzH6Q3/Z0fHcXrDC4zjOL3hBcZxnN74F+zlvXFWXF9PAAAAAElFTkSuQmCC);background-repeat:no-repeat;background-size:280px;color:transparent;display:block;font-size:0;height:20px;line-height:0;width:20px}.viewer-zoom-in:before{background-position:0 0;content:"Zoom In"}.viewer-zoom-out:before{background-position:-20px 0;content:"Zoom Out"}.viewer-one-to-one:before{background-position:-40px 0;content:"One to One"}.viewer-reset:before{background-position:-60px 0;content:"Reset"}.viewer-prev:before{background-position:-80px 0;content:"Previous"}.viewer-play:before{background-position:-100px 0;content:"Play"}.viewer-next:before{background-position:-120px 0;content:"Next"}.viewer-rotate-left:before{background-position:-140px 0;content:"Rotate Left"}.viewer-rotate-right:before{background-position:-160px 0;content:"Rotate Right"}.viewer-flip-horizontal:before{background-position:-180px 0;content:"Flip Horizontal"}.viewer-flip-vertical:before{background-position:-200px 0;content:"Flip Vertical"}.viewer-fullscreen:before{background-position:-220px 0;content:"Enter Full Screen"}.viewer-fullscreen-exit:before{background-position:-240px 0;content:"Exit Full Screen"}.viewer-close:before{background-position:-260px 0;content:"Close"}.viewer-container{bottom:0;direction:ltr;font-size:0;left:0;line-height:0;overflow:hidden;position:absolute;right:0;-webkit-tap-highlight-color:transparent;top:0;touch-action:none;-webkit-touch-callout:none;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.viewer-container ::-moz-selection,.viewer-container::-moz-selection{background-color:transparent}.viewer-container ::selection,.viewer-container::selection{background-color:transparent}.viewer-container:focus{outline:0}.viewer-container img{display:block;height:auto;max-height:none!important;max-width:none!important;min-height:0!important;min-width:0!important;width:100%}.viewer-canvas{bottom:0;left:0;overflow:hidden;position:absolute;right:0;top:0}.viewer-canvas>img{height:auto;margin:15px auto;max-width:90%!important;width:auto}.viewer-footer{bottom:0;left:0;overflow:hidden;position:absolute;right:0;text-align:center}.viewer-navbar{background-color:rgba(0,0,0,.5);overflow:hidden}.viewer-list{box-sizing:content-box;height:50px;margin:0;overflow:hidden;padding:1px 0}.viewer-list>li{color:transparent;cursor:pointer;float:left;font-size:0;height:50px;line-height:0;opacity:.5;overflow:hidden;transition:opacity .15s;width:30px}.viewer-list>li:focus,.viewer-list>li:hover{opacity:.75}.viewer-list>li:focus{outline:0}.viewer-list>li+li{margin-left:1px}.viewer-list>.viewer-loading{position:relative}.viewer-list>.viewer-loading:after{border-width:2px;height:20px;margin-left:-10px;margin-top:-10px;width:20px}.viewer-list>.viewer-active,.viewer-list>.viewer-active:focus,.viewer-list>.viewer-active:hover{opacity:1}.viewer-player{background-color:#000;bottom:0;cursor:none;display:none;right:0;z-index:1}.viewer-player,.viewer-player>img{left:0;position:absolute;top:0}.viewer-toolbar>ul{display:inline-block;margin:0 auto 5px;overflow:hidden;padding:6px 3px}.viewer-toolbar>ul>li{background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;float:left;height:24px;overflow:hidden;transition:background-color .15s;width:24px}.viewer-toolbar>ul>li:focus,.viewer-toolbar>ul>li:hover{background-color:rgba(0,0,0,.8)}.viewer-toolbar>ul>li:focus{box-shadow:0 0 3px #fff;outline:0;position:relative;z-index:1}.viewer-toolbar>ul>li:before{margin:2px}.viewer-toolbar>ul>li+li{margin-left:1px}.viewer-toolbar>ul>.viewer-small{height:18px;margin-bottom:3px;margin-top:3px;width:18px}.viewer-toolbar>ul>.viewer-small:before{margin:-1px}.viewer-toolbar>ul>.viewer-large{height:30px;margin-bottom:-3px;margin-top:-3px;width:30px}.viewer-toolbar>ul>.viewer-large:before{margin:5px}.viewer-tooltip{background-color:rgba(0,0,0,.8);border-radius:10px;color:#fff;display:none;font-size:12px;height:20px;left:50%;line-height:20px;margin-left:-25px;margin-top:-10px;position:absolute;text-align:center;top:50%;width:50px}.viewer-title{color:#ccc;display:inline-block;font-size:12px;line-height:1.2;margin:5px 5%;max-width:90%;min-height:14px;opacity:.8;overflow:hidden;text-overflow:ellipsis;transition:opacity .15s;white-space:nowrap}.viewer-title:hover{opacity:1}.viewer-button{-webkit-app-region:no-drag;background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;height:80px;overflow:hidden;position:absolute;right:-40px;top:-40px;transition:background-color .15s;width:80px}.viewer-button:focus,.viewer-button:hover{background-color:rgba(0,0,0,.8)}.viewer-button:focus{box-shadow:0 0 3px #fff;outline:0}.viewer-button:before{bottom:15px;left:15px;position:absolute}.viewer-fixed{position:fixed}.viewer-open{overflow:hidden}.viewer-show{display:block}.viewer-hide{display:none}.viewer-backdrop{background-color:rgba(0,0,0,.5)}.viewer-invisible{visibility:hidden}.viewer-move{cursor:move;cursor:-webkit-grab;cursor:grab}.viewer-fade{opacity:0}.viewer-in{opacity:1}.viewer-transition{transition:all .3s}@-webkit-keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}.viewer-loading:after{-webkit-animation:viewer-spinner 1s linear infinite;animation:viewer-spinner 1s linear infinite;border:4px solid hsla(0,0%,100%,.1);border-left-color:hsla(0,0%,100%,.5);border-radius:50%;content:"";display:inline-block;height:40px;left:50%;margin-left:-20px;margin-top:-20px;position:absolute;top:50%;width:40px;z-index:1}@media (max-width:767px){.viewer-hide-xs-down{display:none}}@media (max-width:991px){.viewer-hide-sm-down{display:none}}@media (max-width:1199px){.viewer-hide-md-down{display:none}}.nuxt-progress{position:fixed;top:0;left:0;right:0;height:.02353rem;width:0;opacity:1;transition:width .1s,opacity .4s;background-color:#000;z-index:999999}.nuxt-progress.nuxt-progress-notransition{transition:none}.nuxt-progress-failed{background-color:red}.side-bar{width:2.47059rem;position:sticky;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.side-bar .side-bar-title{height:.82353rem;width:2.47059rem;background-image:url(/assets/sidebar-title.jpg);background-size:cover}.side-bar .side-bar-title p{height:.21176rem;font-size:.28235rem;font-weight:700;color:#fff;line-height:.82353rem;text-align:center}.side-bar .side-bar-contents{cursor:pointer;border-bottom:.02353rem solid #e5e5e5;border-left:.02353rem solid #e5e5e5;border-right:.02353rem solid #e5e5e5}.side-bar .side-bar-contents .side-bar-collapse{position:relative;height:.50588rem;overflow:hidden;transition:all .2s ease;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.side-bar .side-bar-contents .side-bar-collapse .collapse-title{font-size:.18824rem;font-weight:400;color:#434343;line-height:.50588rem;padding-left:.24706rem;border-top:.01176rem solid #edf1f4;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.side-bar .side-bar-contents .side-bar-collapse .collapse-title.active{color:#409eff}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn{position:absolute;height:.11765rem;width:.11765rem;box-shadow:.02353rem -.02353rem 0 #82a5d7;background-color:#fff;top:.2rem;right:.18824rem;transform:rotate(45deg);transition:all .25s ease}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn.collapse-btn-active{transform:translate(.04706rem,-.04706rem) rotate(135deg)}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents{border-bottom:.01176rem solid #edf1f4}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item{padding-left:.38824rem;line-height:.44706rem;color:#838383;font-size:.16471rem}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active{color:#409eff;background-color:#f6f7f8;position:relative}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active:after{content:" ";width:.04706rem;height:.04706rem;background:#82a5d7;border-radius:50%;position:absolute;top:50%;left:.17647rem;transform:translateY(-50%)}.page-header-container{margin-bottom:.35294rem;width:100%}.page-header-container .page-header-content{display:flex;align-content:center;position:relative}.page-header-container .page-header-content .page-header-arrow-icon{width:.28235rem;height:.32941rem;padding-top:.02353rem;color:#2f495e;font-size:.23529rem;transition:all .2s ease}.page-header-container .page-header-content .header-arrow-container{width:.17647rem;height:.17647rem;background-image:url(/assets/arrow3.png);background-size:cover}.page-header-container .page-header-content .page-header-arrow-icon:hover{color:#007bff}.page-header-container .page-header-content .page-header-item{color:#858585;font-size:.18824rem;font-weight:500;display:flex;height:.35294rem;line-height:.35294rem;cursor:pointer;align-items:center}.page-header-container .page-header-content .page-header-item .page-header-tag{margin:0 .09412rem;transition:all .2s ease}.page-header-container .page-header-content .page-header-item .page-header-tag.active{color:#2f495e}.page-header-container .page-header-content .page-header-item .page-header-tag:hover{color:#007bff}.mobile .page-header-container{margin-top:.35294rem}.search-box{display:flex;grid-gap:.11765rem;gap:.11765rem;margin-bottom:.28235rem;position:relative;align-items:center}.search-box input{flex:1;min-width:7.05882rem;height:.51765rem;background:#edf1f4;border-radius:.09412rem;border:.01176rem solid #d5dee8;padding:0 .18824rem;font-size:.17647rem;color:#253443;outline:0;z-index:3;transition:border-color .2s ease,box-shadow .2s ease}.search-box input:focus{border-color:#0064c2;box-shadow:0 0 0 .03529rem rgba(0,100,194,.12157)}.search-box .search-btn{width:1.55294rem;height:.51765rem;background:#0064c2;border-radius:.09412rem;border:none;cursor:pointer;transition:background-color .2s ease}.search-box .search-btn:hover{background:#0a5aaa}.search-box .search-btn p{margin:0;line-height:.51765rem;font-size:.18824rem;font-weight:700;color:#fff}.search-box .search-cover{position:fixed;top:0;left:0;right:0;bottom:0;z-index:2;background-color:rgba(25,25,25,.1098);-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem)}.search-result-container{overflow:hidden}.search-result-container::-webkit-scrollbar{width:.14118rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.search-result-container .el-tabs__item{display:table-cell;font-size:.21176rem;font-weight:600}.search-result-container .el-tabs__active-bar{height:.04706rem}.search-result-container{width:100%;min-height:4.47059rem;max-height:7.05882rem;overflow-y:auto;background-color:#fff;position:absolute;top:.63529rem;border:.01176rem solid #e2e8f0;border-radius:.11765rem;box-shadow:0 .11765rem .17647rem -.03529rem rgba(0,0,0,.10196),0 .04706rem .07059rem -.02353rem rgba(0,0,0,.05098);transition:all .25s ease;color:#2f495e;z-index:3;padding:.14118rem;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.search-result-container .search-title{height:.70588rem;font-size:.29412rem;padding:.17647rem;border-bottom:.01176rem solid #d9d9d9}.search-result-container .search-result-contents{display:flex;align-items:flex-start;grid-gap:.11765rem;gap:.11765rem;padding:.14118rem;border-bottom:.01176rem solid #edf2f7;position:relative}.search-result-container .search-result-contents svg{display:inline;font-size:.23529rem;color:#409eff;padding-right:.11765rem}.search-result-container .search-result-contents:hover{background-color:#f3f8fd}.search-result-container .search-result-content{flex:1;display:flex;flex-direction:column;justify-content:center;position:relative;transition:all .25s ease}.search-result-container .search-result-name{font-size:.18824rem;text-align:left;font-weight:700;color:#409eff;line-height:1.4}.search-result-container .search-result-sku{font-size:.16471rem;line-height:1.6;color:#5b5b5b;margin-top:.04706rem}.search-result-container .search-result-key{font-size:.18824rem;font-weight:700;color:#2f495e;margin-top:.04706rem}.search-result-container .search-result-key .search-result-highlight{color:#409eff}.search-result-container .search-result-key .search-result-key-tag{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#5b5b5b;padding:.02353rem .11765rem;border:.01176rem solid #5b5b5b;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container .search-result-key .search-result-key-tag.active{color:#409eff;border:.01176rem solid #409eff}.search-result-container .search-result-image{width:1.31765rem;height:1.31765rem;margin:0 .21176rem 0 .04706rem}.search-result-container .search-result-eol-tag{position:absolute;width:.41176rem;height:.41176rem;border-radius:50%;top:5%;left:.35294rem;background-color:#2f495e;color:#fff;font-size:.15294rem;font-weight:700;line-height:.41176rem;text-align:center}.search-result-container .search-result-recommand-box{margin-top:.14118rem}.search-result-container .search-result-recommand-box .search-result-recommand-item{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#409eff;padding:.04706rem .11765rem;border:.01176rem solid #409eff;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container:before{display:block;position:absolute;content:"";width:.16471rem;height:.16471rem;background:#fff;z-index:1000;top:-.08235rem;left:calc(50% - .08235rem);border-top:.01176rem solid #d9d9d9;border-right:.01176rem solid #d9d9d9;transform:rotate(-45deg);border-radius:.02353rem}.mobile .search-box{margin-bottom:.09412rem;width:100%;grid-gap:.09412rem;gap:.09412rem}.mobile .search-box input{height:.65882rem;font-size:.2rem}.mobile .search-box .search-btn{width:2.11765rem;height:.65882rem;background:#0064c2;border-radius:.09412rem}.mobile .search-box .search-btn p{margin:0;line-height:.65882rem;font-size:.21176rem;font-weight:700;color:#fff}.mobile .search-result-container{top:.75294rem}.search-result-container .tabs{display:flex;grid-gap:.07059rem;gap:.07059rem;width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .14118rem;padding:.09412rem .14118rem;border-radius:0;background:hsla(0,0%,100%,.9);border:0;border-bottom:.01176rem solid #e6edf5;-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem);position:sticky;top:-.14118rem;z-index:6}.search-result-container .tabs:after{content:"";position:absolute;left:0;right:0;top:0;bottom:0;background:0 0;z-index:-1}.search-result-container .tabs button{min-width:1.27059rem;padding:.10588rem .18824rem;border-radius:.11765rem;font-size:.16471rem;font-weight:600;color:#516578;background:hsla(0,0%,100%,.6);border:.01176rem solid #d7e3ef;line-height:1.2;overflow:hidden;transition:color .2s ease,background-color .2s ease,box-shadow .2s ease}.search-result-container .tabs button:first-child,.search-result-container .tabs button:last-child{border-radius:.11765rem}.search-result-container .tabs button:hover{color:#2f4f6f;background:#f8fbff;border-color:#cddded}.search-result-container .tabs button.active{color:#0f4f8e;background:#fff;border:.01176rem solid #c8d9eb;border-radius:.11765rem;box-shadow:0 .02353rem .09412rem rgba(0,100,194,.16078)}.search-result-container .tab-content{padding:.11765rem .09412rem .09412rem;background:0 0}.search-result-container .search-result-contents{border-radius:.09412rem;transition:background-color .2s ease,box-shadow .2s ease}.search-result-container .search-result-contents:hover{box-shadow:inset 0 0 0 .01176rem #dbe9f8}.search-result-contents-list{padding-bottom:.82353rem}.search-result-view-all-wrap{position:sticky;bottom:0;z-index:4;display:flex;justify-content:center;padding:.11765rem .09412rem .07059rem;background:linear-gradient(0deg,#fff 70%,hsla(0,0%,100%,0))}.search-result-view-all-btn{display:inline-block;min-width:2.82353rem;text-align:center;padding:.12941rem .21176rem;border-radius:.28235rem;background:#0064c2;color:#fff;font-size:.17647rem;font-weight:700;text-decoration:none;box-shadow:0 .04706rem .14118rem rgba(0,100,194,.25);transition:background-color .2s ease}.search-result-view-all-btn:hover{background:#0a5aaa}.mobile .search-result-container .tabs{width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .11765rem;padding:.09412rem .11765rem}.mobile .search-result-container .tabs button{flex:1;min-width:0;padding:.14118rem .11765rem;font-size:.17647rem}.mobile .search-result-container .tab-content{padding:.09412rem .04706rem .07059rem}.search-result-container.search-result-embedded{position:relative;top:auto;max-height:none;min-height:0;padding:0;box-shadow:none;-webkit-animation:none;animation:none}.search-result-container.search-result-embedded:before{display:none}.search-result-loading{padding:.09412rem .04706rem;display:flex;flex-direction:column}.search-result-loading-header{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;color:#516578;font-size:.16471rem;margin:0 0 .11765rem}.search-result-loading-text{min-width:0;font-size:.16471rem;font-weight:400;line-height:.23529rem}.search-result-loading-dot{width:.09412rem;height:.09412rem;border-radius:50%;background:#409eff;-webkit-animation:search-loading-pulse 1s ease-in-out infinite;animation:search-loading-pulse 1s ease-in-out infinite}.search-result-loading-list{display:flex;flex-direction:column;grid-gap:.11765rem;gap:.11765rem}.search-result-loading-item{padding:.14118rem;border-radius:.09412rem;border:.01176rem solid #edf2f7;background:#fbfdff}.search-result-loading-line{height:.11765rem;border-radius:11.75294rem;margin-bottom:.09412rem;background:linear-gradient(90deg,#e9f0f7 20%,#f5f9fd 45%,#e9f0f7 70%);background-size:2.82353rem 100%;-webkit-animation:search-loading-shimmer 1.1s linear infinite;animation:search-loading-shimmer 1.1s linear infinite}.search-result-loading-line.is-title{width:52%;height:.14118rem}.search-result-loading-line.is-short{width:36%;margin-bottom:0}@-webkit-keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@-webkit-keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}@keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}.search-result-loading-text[data-v-2b770079]{min-width:0;font-size:.16471rem!important;font-weight:400;line-height:.23529rem}.tab-panel{border:.01176rem solid #e5e5e5;padding:.09412rem;border-radius:.09412rem}.tabs{display:flex;grid-gap:.09412rem;gap:.09412rem;margin-bottom:.18824rem}.tabs button{padding:.11765rem .21176rem;border:none;border-bottom:.04706rem solid transparent;background:#f9f9f9;cursor:pointer;transition:.2s}.tabs button.active{border-color:#007bff;color:#007bff}.tab-content{padding:.18824rem;background:#fefefe;border-radius:.09412rem}.search-result-container .tab-panel{border:0}.carousel-container[data-v-6e07f87d]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-6e07f87d]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-6e07f87d]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-6e07f87d]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-6e07f87d]{flex-shrink:0;width:33.333%;text-align:center;cursor:pointer}.preview-image img[data-v-6e07f87d]{max-width:100%;height:auto;margin:0}.arrow[data-v-6e07f87d]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-6e07f87d]{left:0;transform:rotateY(180deg)}.arrow.right[data-v-6e07f87d]{right:0}.carousel-thumbnails[data-v-6e07f87d]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-6e07f87d]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-6e07f87d]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-6e07f87d]{width:100%;margin:0;height:auto}.clickable-area[data-v-6e07f87d]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-6e07f87d]{left:0}.clickable-area.right[data-v-6e07f87d]{right:0}.carousel-container[data-v-7d51a79c]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-7d51a79c]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-7d51a79c]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-7d51a79c]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-7d51a79c]{flex-shrink:0;width:100%;text-align:center;cursor:pointer}.preview-image img[data-v-7d51a79c]{width:100%;height:auto;margin:0}.arrow[data-v-7d51a79c]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-7d51a79c]{left:0;transform:translateY(-50%) rotateY(180deg)}.arrow.right[data-v-7d51a79c]{right:0;transform:translateY(-50%)}.carousel-thumbnails[data-v-7d51a79c]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-7d51a79c]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-7d51a79c]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-7d51a79c]{width:100%;margin:0;height:auto}.clickable-area[data-v-7d51a79c]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-7d51a79c]{left:0}.clickable-area.right[data-v-7d51a79c]{right:0}.corner-marker[data-v-7d51a79c]{position:absolute;bottom:.11765rem;left:.11765rem;background-color:rgba(0,0,0,.5);color:#fff;padding:.05882rem .11765rem;border-radius:.05882rem;z-index:2}.video-gallery-island[data-v-5e05839f]{min-width:0;width:100%}.page-tools[data-v-39baf185]{width:2.35294rem;margin-bottom:.16471rem;border:.01176rem solid #dfeaf5;border-radius:.11765rem;background:#f8fbfe;box-shadow:0 .07059rem .21176rem rgba(19,41,75,.08);overflow:visible}.page-tools-title[data-v-39baf185]{height:.4rem;line-height:.4rem;padding:0 .14118rem;border-bottom:.01176rem solid #e5eef7;color:#2f495e;font-size:.15294rem;font-weight:700}.page-tools-actions[data-v-39baf185]{display:flex;flex-direction:column;grid-gap:.09412rem;gap:.09412rem;padding:.11765rem;align-items:stretch}.page-tools-action[data-v-39baf185]{display:inline-flex;align-items:center;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;height:.43529rem;width:100%;padding:0 .11765rem;border:.01176rem solid #d6e5f3;border-radius:.08235rem;background:#fff;color:#238dfb;font-size:.15294rem;font-weight:700;transition:background-color .2s ease,border-color .2s ease,transform .2s ease}.page-tools-action .page-tools-icon[data-v-39baf185]{width:.21176rem;height:.21176rem;flex:0 0 auto;fill:currentColor;display:block}.page-tools-action[data-v-39baf185]:after{content:"";width:.08235rem;height:.08235rem;margin-left:auto;border-top:.02353rem solid;border-right:.02353rem solid;transform:rotate(45deg);opacity:.45}.page-tools-action[data-v-39baf185]:hover{background:#eaf4ff;border-color:#b9d8f4;transform:translateY(-.01176rem)}.page-tools.mobile[data-v-39baf185]{width:auto;margin:.09412rem 0 .18824rem;border:0;background:0 0;box-shadow:none}.page-tools.mobile .page-tools-actions[data-v-39baf185]{flex-direction:row;padding:0}.page-tools.mobile .page-tools-action[data-v-39baf185]{width:.63529rem;min-width:.63529rem;height:.42353rem;padding:0;background:#edf6ff;border-color:#b7d8f5;justify-content:center}.page-tools.mobile .page-tools-action[data-v-39baf185]:after{display:none}.markdown-action-menu[data-v-5d6a4f8a]{position:relative;display:flex;justify-content:flex-end;margin:-.14118rem 0 .21176rem;z-index:20}.markdown-action-trigger[data-v-5d6a4f8a]{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;height:.47059rem;padding:0 .16471rem;border:.01176rem solid #b9cfe5;border-radius:.07059rem;background:linear-gradient(135deg,#0064c2,#238dfb);color:#fff;font-size:.16471rem;font-weight:700;cursor:pointer;transition:background-color .2s ease,border-color .2s ease}.markdown-action-trigger svg[data-v-5d6a4f8a]{width:.18824rem;height:.18824rem}.markdown-action-trigger[data-v-5d6a4f8a]:hover{background:linear-gradient(135deg,#0059ad,#167ce8);border-color:#82b6ec}.markdown-action-dropdown[data-v-5d6a4f8a]{position:fixed;z-index:2147483000;width:3.52941rem;overflow:hidden;border:.01176rem solid #c8dced;border-radius:.11765rem;background:#fff;box-shadow:0 .18824rem .44706rem rgba(18,62,111,.16),0 .02353rem .09412rem rgba(24,84,140,.08)}.markdown-action-item[data-v-5d6a4f8a]{display:flex;width:100%;grid-gap:.16471rem;gap:.16471rem;align-items:flex-start;padding:.17647rem .18824rem;border:0;border-bottom:.01176rem solid #e6edf5;background:0 0;color:#2f495e;text-align:left;cursor:pointer;transition:background-color .15s ease}.markdown-action-item svg[data-v-5d6a4f8a]{flex:0 0 auto;width:.2rem;height:.2rem;margin-top:.02353rem;color:#238dfb}.markdown-action-item strong[data-v-5d6a4f8a]{display:block;font-size:.17647rem;line-height:.23529rem}.markdown-action-item small[data-v-5d6a4f8a]{display:block;margin-top:.02353rem;color:#6f8193;font-size:.15294rem;line-height:.21176rem}.markdown-action-item[data-v-5d6a4f8a]:last-child{border-bottom:0}.markdown-action-item[data-v-5d6a4f8a]:hover{background:#f3f8fe}.markdown-action-menu.placement-sidebar[data-v-5d6a4f8a]{justify-content:center;margin:.14118rem 0 0}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;justify-content:center;background:#edf6ff;border-color:#c7dff7;color:#0064c2}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#dfefff;border-color:#9fc7ef}.markdown-action-menu.placement-sidebar .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.05882rem}.markdown-action-menu.placement-anchor[data-v-5d6a4f8a]{justify-content:flex-start;margin:0 0 .11765rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:center;padding:0 .11765rem;background:#f5f9fd;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-anchor .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.placement-toolbox[data-v-5d6a4f8a]{width:100%;flex:1;justify-content:flex-start;margin:0}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;padding:0 .11765rem;background:#fff;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]{flex:0 0 auto}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{width:.16471rem;height:.16471rem;margin-left:auto;opacity:.55}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-toolbox .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.compact[data-v-5d6a4f8a]{justify-content:flex-start;margin:.09412rem 0 .18824rem}.markdown-action-menu.compact .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center;padding:0;background:#edf6ff;border-color:#b7d8f5;color:#0064c2}.markdown-action-menu.compact .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.52941rem;max-width:calc(100vw - .37647rem)}.markdown-action-menu.compact.placement-toolbox[data-v-5d6a4f8a]{flex:0 0 auto;margin:0}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{margin-left:0}</style><link rel="preload" href="/_nuxt/static/1788504562/zh_CN/core/Cardputer-Adv/state.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/zh_CN/core/Cardputer-Adv/payload.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/manifest.js" as="script">
-  </head>
-  <body>
-    <div data-server-rendered="true" id="__nuxt"><!----><div id="__layout"><div class="device-hydration-sensitive"><div class="pc"><header langdata="[object Object]" lang="zh-cn"><!----> <!----> <div class="header-container"><a href="https://m5stack.com/zh-cn/" class="logo"><img src="/assets/m5logo.svg" alt="M5Stack"></a> <div class="header-nav"><div class="header-nav-ul"><!----> <li data-id="solution" class="header-nav-item"><a class="header-nav-item-a disabledHover">解决方案</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="store" class="header-nav-item"><a href="https://shop.m5stack.com" class="header-nav-item-a">硬件产品</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="software" class="header-nav-item"><a class="header-nav-item-a disabledHover">软件工具</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="document" class="header-nav-item"><a class="header-nav-item-a disabledHover">文档中心</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="aboutus" class="header-nav-item"><a class="header-nav-item-a disabledHover">关于我们</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="contact" class="header-nav-item"><a class="header-nav-item-a disabledHover">联系我们</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----></div></div> <div class="language-option-box"><div class="current-language"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 1.32 1.32" fill="currentColor" aria-hidden="true" class="icon"><g><path d="M0.66 0c0.18,0 0.35,0.07 0.47,0.19 0.12,0.12 0.19,0.28 0.19,0.47 0,0.18 -0.07,0.35 -0.19,0.47 -0.12,0.12 -0.28,0.19 -0.47,0.19 -0.18,0 -0.35,-0.07 -0.47,-0.19 -0.12,-0.12 -0.19,-0.28 -0.19,-0.47 0,-0.18 0.07,-0.35 0.19,-0.47 0.12,-0.12 0.28,-0.19 0.47,-0.19zm0.39 0.27c-0.1,-0.1 -0.24,-0.16 -0.39,-0.16 -0.15,0 -0.29,0.06 -0.39,0.16 -0.1,0.1 -0.16,0.24 -0.16,0.39 0,0.15 0.06,0.29 0.16,0.39 0.1,0.1 0.24,0.16 0.39,0.16 0.15,0 0.29,-0.06 0.39,-0.16 0.1,-0.1 0.16,-0.24 0.16,-0.39 0,-0.15 -0.06,-0.29 -0.16,-0.39z"></path> <path d="M0.09 0.51c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.09 0.92c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.62 1.21c0.02,0.02 0.02,0.06 0,0.08 -0.02,0.02 -0.06,0.02 -0.08,0 -0.07,-0.06 -0.13,-0.16 -0.16,-0.27 -0.04,-0.11 -0.06,-0.23 -0.06,-0.36 0,-0.13 0.02,-0.26 0.06,-0.36 0.04,-0.11 0.1,-0.21 0.16,-0.27 0.02,-0.02 0.06,-0.02 0.08,0 0.02,0.02 0.02,0.06 -0,0.08 -0.06,0.05 -0.1,0.13 -0.14,0.23 -0.03,0.09 -0.05,0.21 -0.05,0.33 0,0.12 0.02,0.23 0.05,0.33 0.03,0.1 0.08,0.18 0.14,0.23z"></path> <path d="M0.78 1.29c-0.02,0.02 -0.06,0.02 -0.08,-0 -0.02,-0.02 -0.02,-0.06 0,-0.08 0.06,-0.05 0.1,-0.13 0.14,-0.23 0.03,-0.09 0.05,-0.21 0.05,-0.33 0,-0.12 -0.02,-0.23 -0.05,-0.33 -0.03,-0.1 -0.08,-0.18 -0.14,-0.23 -0.02,-0.02 -0.02,-0.06 -0,-0.08 0.02,-0.02 0.06,-0.02 0.08,-0 0.07,0.06 0.13,0.16 0.16,0.27 0.04,0.11 0.06,0.23 0.06,0.36 0,0.13 -0.02,0.26 -0.06,0.36 -0.04,0.11 -0.1,0.21 -0.16,0.27z"></path></g></svg> <div>简体中文</div> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg></div> <div class="language-dropdown-wrapper"><div class="language-dropdown"><div class="language-item">English</div> <div class="language-item active">简体中文</div> <div class="language-item">日本語</div></div></div></div></div></header> <div class="docs-layouts"><div class="docs-layouts-sidebar"><div class="side-bar"><div class="side-bar-title"><p>CONTENTS</p></div> <div class="side-bar-contents"></div></div></div> <div class="docs-layouts-body"><div class="page-header-container"><!----></div> <!----> <div class="search-box"><div id="search"></div> <input placeholder="Product Name / SKU"> <div class="search-result-container" style="display:none" data-v-2b770079><a class="search-result-contents" data-v-2b770079><div class="search-result-content" data-v-2b770079><div class="search-result-name" data-v-2b770079>未找到结果</div> <div class="search-result-sku" data-v-2b770079>热门搜索</div> <div class="search-result-key" data-v-2b770079><div class="search-result-recommand-box" data-v-2b770079><div data-key="Camera" class="search-result-recommand-item" data-v-2b770079>
-            Camera
-          </div><div data-key="WiFi" class="search-result-recommand-item" data-v-2b770079>
-            WiFi
-          </div><div data-key="RS485" class="search-result-recommand-item" data-v-2b770079>
-            RS485
-          </div><div data-key="RS232" class="search-result-recommand-item" data-v-2b770079>
-            RS232
-          </div><div data-key="Relay" class="search-result-recommand-item" data-v-2b770079>
-            Relay
-          </div><div data-key="LoRaWAN" class="search-result-recommand-item" data-v-2b770079>
-            LoRaWAN
-          </div><div data-key="GPS" class="search-result-recommand-item" data-v-2b770079>
-            GPS
-          </div><div data-key="NB-IoT" class="search-result-recommand-item" data-v-2b770079>
-            NB-IoT
-          </div><div data-key="LTE" class="search-result-recommand-item" data-v-2b770079>
-            LTE
-          </div><div data-key="GSM" class="search-result-recommand-item" data-v-2b770079>
-            GSM
-          </div><div data-key="Zigbee" class="search-result-recommand-item" data-v-2b770079>
-            Zigbee
-          </div><div data-key="Servo" class="search-result-recommand-item" data-v-2b770079>
-            Servo
-          </div><div data-key="StepMotor" class="search-result-recommand-item" data-v-2b770079>
-            StepMotor
-          </div><div data-key="Ethernet" class="search-result-recommand-item" data-v-2b770079>
-            Ethernet
-          </div><div data-key="E-Paper" class="search-result-recommand-item" data-v-2b770079>
-            E-Paper
-          </div></div></div></div></a> <div class="tab-panel" style="display:none" data-v-2b770079><div class="tabs"><button>
-      产品
-    </button><button>
-      内容
-    </button></div> <div class="tab-content"><div style="display:none"></div><div style="display:none"></div></div></div></div> <button class="search-btn"><p>Search</p></button> <div class="search-cover" style="display:none"></div></div> <div class="viewer"><div class="markdown"><h1 id="cardputer-adv" data-id="Cardputer-Adv">Cardputer-Adv</h1> <p><span class="product-sku">SKU:K132-Adv</span></p><div class="carousel-container" data-v-6e07f87d><div class="carousel-preview" data-v-6e07f87d><div class="clickable-area left" data-v-6e07f87d></div> <button class="arrow left" data-v-6e07f87d></button> <div class="carousel-images" data-v-6e07f87d><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-6e07f87d><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_01.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_02.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_03.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_04.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_05.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_06.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_07.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_08.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_09.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_10.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_11.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_12.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_13.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-weight.jpg" alt="Preview" data-v-6e07f87d></div></div></div> <button class="arrow right" data-v-6e07f87d></button> <div class="clickable-area right" data-v-6e07f87d></div></div> <div class="carousel-thumbnails" data-v-6e07f87d><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_01.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_02.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_03.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_04.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_05.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_06.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_07.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_08.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_09.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_10.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_11.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_12.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_13.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-weight.jpg" alt="Thumbnail" data-v-6e07f87d></div></div></div> <h2 id="描述" data-id="描述">描述</h2> <p><strong>Cardputer-Adv</strong> 是一款可编程卡片电脑，其核心采用 Stamp-S3A 主控模组（基于 ESP32-S3FN8），集成 1.14" LCD 屏幕与 56 键极简键盘以支持便捷的交互与输入操作。音频处理方面，设备集成 ES8311 音频编解码芯片，搭配高信噪比 MEMS 麦克风，NS4150B 功放芯片和 1W 扬声器，能够提供优质的音频输入输出能力。同时配备 3.5mm 音频输出接口可以用于外接耳机或音响。内部配备 1750mAh 大容量锂电池，结合低功耗设计与独立电源开关，能够提供良好的续航能力。集成 6 轴姿态传感器 BMI270，红外发射管，microSD 卡槽，同时预留 HY2.0-4P Grove 接口， EXT 2.54-14P 拓展总线可用于传感器与其他外设拓展。结构方面，底座含磁铁可以进行金属吸附，结构设置兼容乐高孔扩展。该产品适用于工程师快速功能验证设计、工业控制、家居控制等场景。</p><h2 id="教程--快速上手" data-id="教程  快速上手">教程 & 快速上手</h2> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/uiflow2/uiflow2.0_banner_01.png" alt="UiFlow2"> <a target="_blank" href="/zh_CN/uiflow2/cardputer-adv/program">UiFlow2</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/zh_CN/uiflow2/cardputer-adv/program">UiFlow2</a></div> <div class="learn-desc"> 本教程将向你介绍，如何通过 UiFlow2 图形化编程平台控制 Cardputer-Adv 设备。 </div></div></div> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/arduino/arduino_banner_01.png" alt="Arduino IDE"> <a target="_blank" href="/zh_CN/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/zh_CN/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-desc"> 本教程将向你介绍，如何通过 Arduino IDE 编程控制 Cardputer-Adv 设备。 </div></div></div><h2 id="产品特性" data-id="产品特性">产品特性</h2> <ul><li>Stamp-S3A 核心主控</li> <li>56 键键盘</li> <li>1.14" LCD 屏幕</li> <li>160gf 舒适按键手感</li> <li>ES8311 音频编解码芯片</li> <li>高信噪比 MEMS 麦克风</li> <li>NS4150B 功放芯片和 1W 扬声器</li> <li>3.5mm 音频输出接口</li> <li>红外发射管</li> <li>6 轴姿态传感器 BMI270</li> <li>HY2.0-4P Grove 接口</li> <li>EXT 2.54-14P 拓展总线</li> <li>microSD 卡槽</li> <li>内置 1750mAh 锂电池</li> <li>背面磁吸设计</li> <li>兼容乐高孔</li> <li>开发平台<ul><li>Arduino</li> <li>UiFlow2</li> <li>ESP-IDF</li> <li>PlatformIO</li></ul></li></ul> <h2 id="包装内容" data-id="包装内容">包装内容</h2> <ul><li>1 x Cardputer-Adv</li></ul> <h2 id="应用场景" data-id="应用场景">应用场景</h2> <ul><li>快速功能验证和原型设计</li> <li>工业控制和自动化</li> <li>嵌入式系统开发和学习</li> <li>无线通信和物联网 (IoT) 项目</li></ul> <h2 id="规格参数" data-id="规格参数">规格参数</h2> <div class="table-container"><table><thead><tr><th>规格</th> <th>参数</th></tr></thead><tbody><tr><td>SoC</td> <td>ESP32-S3FN8 @ Xtensa® 32 位 LX7 双核处理器，主频 240MHz</td></tr> <tr><td>Flash</td> <td>8MB</td></tr> <tr><td>外部存储扩展</td> <td>microSD</td></tr> <tr><td>屏幕</td> <td>ST7789V2@1.14", 240 x 135px</td></tr> <tr><td>键盘</td> <td>56 按键 (4 x 14)</td></tr> <tr><td>按键操作力</td> <td>160gf</td></tr> <tr><td>拓展接口</td> <td>HY2.0-4P + EXT 2.54-14P</td></tr> <tr><td>IR</td> <td>1x IR 发射管</td></tr> <tr><td>音频编解码芯片</td> <td>ES8311</td></tr> <tr><td>扬声器</td> <td>NS4150B 功放芯片 + 8Ω@1W 扬声器</td></tr> <tr><td>麦克风</td> <td>MEMS 麦克风，信噪比 (SNR)：65 dB</td></tr> <tr><td>姿态传感器</td> <td>BMI270</td></tr> <tr><td>电池容量</td> <td>1750mAh</td></tr> <tr><td>工作温度</td> <td>0 ~ 40°C</td></tr> <tr><td>待机电流（电源开关切换到 OFF）</td> <td>DC4.2V@0.23uA</td></tr> <tr><td>工作电流</td> <td>DC4.2V@120.2mA</td></tr> <tr><td>Wi-Fi 工作电流</td> <td>DC4.2V@132.3mA</td></tr> <tr><td>BLE 工作电流</td> <td>DC4.2V@154.6mA</td></tr> <tr><td>产品尺寸</td> <td>84.0 x 54.0 x 19.6mm</td></tr> <tr><td>产品重量</td> <td>81.0g</td></tr> <tr><td>包装尺寸</td> <td>145.7 x 95.0 x 20.7mm</td></tr> <tr><td>毛重</td> <td>98.5g</td></tr></tbody></table></div><h2 id="操作说明" data-id="操作说明">操作说明</h2> <h3 id="进入下载模式" data-id="进入下载模式">进入下载模式</h3> <p>如果要进入下载模式，请将 Cardputer-Adv 侧面的开关键置于<code>OFF</code>状态，然后在开机前按住<code>G0</code>按键，在设备后通电后释放，之后设备将进入下载模式。</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_operation_01.jpg" width="60%"> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_operation.gif" width="60%"> <h3 id="rgb-led-供电" data-id="RGB LED 供电">RGB LED 供电</h3> <div class="warn"><div class="warn-title">RGB LED 供电说明</div> <div class="warn-content">设备核心主控采用 <strong>Stamp-S3A</strong>。为优化整机功耗，相较于旧款 Stamp-S3，Stamp-S3A 增设独立电子开关管控 RGB LED 供电。程序操作 RGB LED 前，需先将控制该开关的 GPIO38 引脚置为高电平。</div></div><h3 id="充电注意事项" data-id="充电注意事项">充电注意事项</h3> <p>Cardputer-Adv 充电时，请将电源开关切换至<code>ON</code>。</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_14.jpg" width="60%"> <h3 id="扬声器功能" data-id="扬声器功能">扬声器功能</h3> <div class="tip"><div class="tip-title">说明 </div> <div class="tip-content"> 当 3.5mm 耳机孔插入耳机的时候，扬声器功放将关闭。</div></div><h3 id="imu-三轴方向示意图" data-id="IMU 三轴方向示意图">IMU 三轴方向示意图</h3> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/IMU-Cardputer-Adv.jpg" width="70%"> <h2 id="原理图" data-id="原理图">原理图</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf">Cardputer-Adv 原理图 PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf">Stamp-S3A 原理图 PDF</a></li></ul> <div class="carousel-container" data-v-7d51a79c><div class="carousel-preview" data-v-7d51a79c><div class="clickable-area left" data-v-7d51a79c></div> <button class="arrow left" data-v-7d51a79c></button> <div class="carousel-images" data-v-7d51a79c><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-7d51a79c><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_02.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_03.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_04.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Preview" data-v-7d51a79c></div></div></div> <button class="arrow right" data-v-7d51a79c></button> <div class="clickable-area right" data-v-7d51a79c></div> <div class="corner-marker" data-v-7d51a79c>1/5</div></div> <div class="carousel-thumbnails" data-v-7d51a79c><div class="thumbnail active" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_02.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_03.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_04.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Thumbnail" data-v-7d51a79c></div></div></div> <h2 id="管脚映射" data-id="管脚映射">管脚映射</h2> <h3 id="lcd" data-id="LCD">LCD</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G38</th> <th>G33</th> <th>G34</th> <th>G35</th> <th>G36</th> <th>G37</th></tr></thead><tbody><tr><td>ST7789V2</td> <td>DISP_BL</td> <td>RST</td> <td>RS</td> <td>DAT</td> <td>SCK</td> <td>CS</td></tr> <tr><td>RGB LED</td> <td>PWR_EN</td> <td></td> <td></td> <td></td> <td></td> <td></td></tr></tbody></table></div><h3 id="audio" data-id="Audio">Audio</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th> <th>G41</th> <th>G46</th> <th>G43</th> <th>G42</th></tr></thead><tbody><tr><td>ES8311</td> <td>SDA</td> <td>SCL</td> <td>SCLK</td> <td>ASDOUT</td> <td>LRCK</td> <td>DSDIN</td></tr></tbody></table></div><h3 id="imu" data-id="IMU">IMU</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th></tr></thead><tbody><tr><td>BMI270</td> <td>SDA</td> <td>SCL</td></tr></tbody></table></div><h3 id="ir" data-id="IR">IR</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G44</th></tr></thead><tbody><tr><td>IR TX</td> <td>TX</td></tr></tbody></table></div><h3 id="battery" data-id="Battery">Battery</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G10</th></tr></thead><tbody><tr><td>Battery</td> <td>ADC</td></tr></tbody></table></div><h3 id="keyboard" data-id="Keyboard">Keyboard</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th> <th>G11</th></tr></thead><tbody><tr><td>TCA8418RTWR</td> <td>SDA</td> <td>SCL</td> <td>INT</td></tr></tbody></table></div><h3 id="microsd" data-id="microSD">microSD</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G12</th> <th>G14</th> <th>G40</th> <th>G39</th></tr></thead><tbody><tr><td>microSD</td> <td>CS</td> <td>MOSI</td> <td>CLK</td> <td>MISO</td></tr></tbody></table></div><h3 id="hy20-4p" data-id="HY2.0-4P">HY2.0-4P</h3> <div class="grove-table-container"><div class="table-container"><table><thead><tr><th>HY2.0-4P</th> <th>Black</th> <th>Red</th> <th>Yellow</th> <th>White</th></tr></thead><tbody><tr><td>PORT.CUSTOM</td> <td>GND</td> <td>5V</td> <td>G2</td> <td>G1</td></tr></tbody></table></div></div><h3 id="ext-254-14p" data-id="EXT 2.54-14P">EXT 2.54-14P</h3> <div class="m5-bus-table-container core"><div class="table-container"><table><thead><tr><th>FUNC</th> <th>PIN</th> <th>LEFT</th> <th>RIGHT</th> <th>PIN</th> <th>FUNC</th></tr></thead><tbody><tr><td>RESET</td> <td>G3</td> <td>1</td> <td>2</td> <td class="VCC">5VIN</td> <td class="empty"></td></tr> <tr><td>INT</td> <td>G4</td> <td>3</td> <td>4</td> <td class="GND">GND</td> <td class="empty"></td></tr> <tr><td>BUSY</td> <td>G6</td> <td>5</td> <td>6</td> <td class="VCC">5VOUT</td> <td class="empty"></td></tr> <tr><td class="SPI">SCK</td> <td>G40</td> <td>7</td> <td>8</td> <td>G8</td> <td class="I2C">I2C_SDA</td></tr> <tr><td class="SPI">MOSI</td> <td>G14</td> <td>9</td> <td>10</td> <td>G9</td> <td class="I2C">I2C_SCL</td></tr> <tr><td class="SPI">MISO</td> <td>G39</td> <td>11</td> <td>12</td> <td>G13</td> <td>UART_TX</td></tr> <tr><td class="SPI">CS</td> <td>G5</td> <td>13</td> <td>14</td> <td>G15</td> <td>UART_RX</td></tr></tbody></table></div></div><h2 id="尺寸图" data-id="尺寸图">尺寸图</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV.pdf">Cardputer-Adv模型尺寸PDF</a></li></ul> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV_page_01.png" width="100%"> <h2 id="结构文件" data-id="结构文件">结构文件</h2> <ul><li><a target="_blank" href="https://github.com/m5stack/M5_Hardware/tree/master/Products/K132-Adv_Cardputer-Adv/Structures">Cardputer-Adv 结构文件</a></li></ul> <h2 id="软件开发" data-id="软件开发">软件开发</h2> <h3 id="arduino" data-id="Arduino">Arduino</h3> <ul><li><a target="_blank" href="/zh_CN/arduino/m5cardputer/program">Cardputer-Adv Arduino 快速上手</a></li> <li><a target="_blank" href="https://github.com/m5stack/M5Cardputer">Cardputer-Adv Arduino 驱动库</a></li></ul> <h3 id="uiflow2" data-id="UiFlow2">UiFlow2</h3> <ul><li><a target="_blank" href="/zh_CN/uiflow2/cardputer-adv/program">Cardputer-Adv UiFlow2 快速上手</a></li></ul> <h3 id="platformio" data-id="PlatformIO">PlatformIO</h3> <div class="code-block-wrapper"><div class="code-line-container"><pre><code class="hljs language-bash">[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code></pre> <button class="copy-all-btn"><code>[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code> <div class="fa-solid fa-copy"></div></button></div></div> <h3 id="esp-idf" data-id="ESP-IDF">ESP-IDF</h3> <ul><li><a target="_blank" href="https://github.com/m5stack/M5Cardputer-UserDemo/tree/CardputerADV">Cardputer-Adv 出厂固件</a></li></ul> <h3 id="easyloader" data-id="Easyloader">Easyloader</h3> <div class="table-container"><table><thead><tr><th>Easyloader</th> <th>下载链接</th> <th>备注</th></tr></thead><tbody><tr><td>Cardputer-Adv 出厂固件 Easyloader</td> <td><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Easy_Loader_for_Cardputer-Adv.exe">download</a></td> <td>/</td></tr></tbody></table></div><h2 id="相关视频" data-id="相关视频">相关视频</h2> <div class="video-gallery-island" data-v-5e05839f></div> <h2 id="产品对比" data-id="产品对比">产品对比</h2> <div class="compare-table-container"><div class="table-container"><table><thead><tr><th>产品对比项</th> <th><a target="_blank" href="/zh_CN/core/Cardputer-Adv">Cardputer-Adv</a> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_02.webp" alt="Cardputer-Adv"></th> <th><a target="_blank" href="/zh_CN/core/Cardputer%20V1.1">Cardputer v1.1</a> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_04.webp" alt="Cardputer v1.1"></th> <th><a target="_blank" href="/zh_CN/core/Cardputer">Cardputer</a> <img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-a02d6727-4fa1-4b38-90e6-75e401d507de.webp" alt="Cardputer"></th></tr></thead><tbody><tr><td>核心模组</td> <td>Stamp-S3A</td> <td>Stamp-S3A</td> <td>Stamp-S3</td></tr> <tr><td>RGB LED 控制逻辑</td> <td>RGB LED 与屏幕背光共用电源，控制逻辑经过优化</td> <td>RGB LED 与屏幕背光共用电源，控制逻辑经过优化</td> <td>通电即供电</td></tr> <tr><td>天线设计</td> <td>优化天线设计，信号接收更佳</td> <td>优化天线设计，信号接收更佳</td> <td>常规天线设计</td></tr> <tr><td>电池容量</td> <td>1750mAh</td> <td>120mAh + 1400mAh</td> <td>120mAh + 1400mAh</td></tr> <tr><td>音频方案</td> <td>ES8311 + NS4150B</td> <td>NS4168 + SPM1423</td> <td>NS4168 + SPM1423</td></tr> <tr><td>音频接口</td> <td>3.5mm 音频接口</td> <td>/</td> <td>/</td></tr> <tr><td>IMU</td> <td>BMI270</td> <td>/</td> <td>/</td></tr> <tr><td>键盘 IO 拓展</td> <td>TCA8418RTWR</td> <td>74HC138</td> <td>74HC138</td></tr> <tr><td>拓展接口</td> <td>HY2.0-4P + EXT 2.54-14P</td> <td>HY2.0-4P</td> <td>HY2.0-4P</td></tr> <tr><td>挂绳孔</td> <td>有</td> <td>无</td> <td>无</td></tr></tbody></table></div></div><p>如需对比 Cardputer 系列产品信息，可访问<a target="_blank" href="/zh_CN/products_selector/m5cardputer_compare?select=K132-Adv">产品选型表</a>，勾选目标产品即可获取对比结果。选型表涵盖核心参数、功能特性等关键信息，支持多产品同步比对。</p></div> <!----> <!----> <!----></div></div> <div class="docs-layouts-anchor"><div class="page-tools" data-v-39baf185><div class="page-tools-title" data-v-39baf185>Page Tools</div> <div class="page-tools-actions" data-v-39baf185><a href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/zh_CN/core/Cardputer-Adv.pdf" target="_blank" rel="nofollow noopener noreferrer" title="Download PDF" class="page-tools-action page-tools-pdf" data-v-39baf185><svg viewBox="0 0 24 24" aria-hidden="true" class="page-tools-icon" data-v-39baf185><path d="M6 2h8l4 4v16H6V2zm7 1.8V7h3.2L13 3.8zM8.4 12.2h1.5c1 0 1.7-.6 1.7-1.6S10.9 9 9.9 9H7v6h1.4v-2.8zm0-1.1v-1h1.3c.3 0 .5.2.5.5s-.2.5-.5.5H8.4zm4.1 3.9h1.8c1.7 0 2.8-1.1 2.8-3s-1.1-3-2.8-3h-1.8v6zm1.4-1.2v-3.6h.4c.9 0 1.4.6 1.4 1.8s-.5 1.8-1.4 1.8h-.4zm4.1 1.2h1.4v-2.4h2.1v-1.2h-2.1v-1.2h2.4V9H18v6z" data-v-39baf185></path></svg> <span data-v-39baf185>PDF</span></a> <div class="markdown-action-menu placement-toolbox" data-v-5d6a4f8a data-v-39baf185><button type="button" title="复制页面" class="markdown-action-trigger" data-v-5d6a4f8a><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><rect x="9" y="9" width="13" height="13" rx="2"></rect><path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1"></path></svg> <span data-v-5d6a4f8a>复制页面</span> <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><polyline points="6 9 12 15 18 9"></polyline></svg></button> <!----></div></div></div></div></div> <footer><div class="footer-container"><div class="footer-content-wrap"><div class="footer-nav"><div class="footer-nav-item"><div data-id="0" class="footer-nav-title"><a class="footer-nav-title-a">
-        关于我们
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/about-us">关于M5Stack</a></li><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/explore?page=1">新闻资讯</a></li><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/explore?type=blog&page=1">技术博客</a></li><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/events">线下活动</a></li><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/contact">联系我们</a></li></ul></div><div class="footer-nav-item"><div data-id="1" class="footer-nav-title"><a class="footer-nav-title-a">
-        订购渠道
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.taobao.com/">淘宝企业店铺</a></li><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/distributor">全球经销商</a></li><li class="footer-nav-li"><a href="https://m5stack.aliexpress.com/store/911661199">速卖通</a></li><li class="footer-nav-li"><a href="https://www.amazon.com/shops/m5stack">亚马逊</a></li></ul></div><div class="footer-nav-item"><div data-id="2" class="footer-nav-title"><a class="footer-nav-title-a">
-        解决方案
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/business">面向行业客户</a></li><li class="footer-nav-li"><a href="https://m5stack.com/zh-cn/developers">面向工程师</a></li></ul></div><div class="footer-nav-item"><div data-id="3" class="footer-nav-title"><a class="footer-nav-title-a">
-        软件工具
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://flow.m5stack.com/">UiFlow1</a></li><li class="footer-nav-li"><a href="https://uiflow2.m5stack.com/">UiFlow2</a></li><li class="footer-nav-li"><a href="/zh_CN/uiflow/m5burner/intro">M5Burner</a></li><li class="footer-nav-li"><a href="https://block-designer.m5stack.com/">Block Designer</a></li><li class="footer-nav-li"><a href="/zh_CN/guide/ezdata/ezdata_v2">EzData 2.0</a></li><li class="footer-nav-li"><a href="/zh_CN/guide/easyloader/easyloader_packer">EasyLoader Packer</a></li><li class="footer-nav-li"><a href="/zh_CN/guide/develop_tools/vlw_font_creator">VLW Font Creator</a></li><li class="footer-nav-li"><a href="/zh_CN/download">设备USB驱动</a></li></ul></div><div class="footer-nav-item"><div data-id="4" class="footer-nav-title"><a class="footer-nav-title-a">
-        文档中心
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="/zh_CN/products">产品文档</a></li><li class="footer-nav-li"><a href="/zh_CN/uiflow/uiflow_web">UiFlow1</a></li><li class="footer-nav-li"><a href="/zh_CN/uiflow2/uiflow_web">UiFlow2</a></li><li class="footer-nav-li"><a href="/zh_CN/arduino/arduino_ide">Arduino</a></li><li class="footer-nav-li"><a href="/zh_CN/esp_idf/esp_idf">ESP-IDF</a></li><li class="footer-nav-li"><a href="/zh_CN/stackflow/overview">StackFlow AI</a></li><li class="footer-nav-li"><a href="/zh_CN/homeassistant/overview">Home Assistant</a></li><li class="footer-nav-li"><a href="https://github.com/nanoframework/nanoFramework.M5Stack">nanoFramework</a></li><li class="footer-nav-li"><a href="/zh_CN/guide/product_guide">产品使用指引</a></li><li class="footer-nav-li"><a href="/zh_CN/certification">产品认证</a></li><li class="footer-nav-li"><a href="/zh_CN/product_i2c_addr">I2C地址表</a></li><li class="footer-nav-li"><a href="/zh_CN/products_selector/m5core_compare">产品选型工具</a></li><li class="footer-nav-li"><a href="https://github.com/m5stack/M5_Hardware">硬件设计文件</a></li><li class="footer-nav-li"><a href="/zh_CN/history">产品发布历史</a></li><li class="footer-nav-li"><a href="/zh_CN/compatible_stack">模块堆叠兼容性</a></li><li class="footer-nav-li"><a href="/zh_CN/learn/extension/module">模块堆叠螺丝长度</a></li></ul></div></div> <div class="footer-right"><div class="footer-qrcode-wrapper"><div class="footer-qrcode-title">
-              关注我们，掌握最新动态
-            </div> <div class="footer-qrcode-list"><div class="footer-qrcode-item"><div class="footer-qrcode-img"><img src="/assets/footer/official-qrcode.jpg" alt="公众号"></div> <div class="footer-qrcode-name">
-                  公众号
-                </div></div><div class="footer-qrcode-item"><div class="footer-qrcode-img"><img src="/assets/footer/service-qrcode.jpg" alt="服务号"></div> <div class="footer-qrcode-name">
-                  服务号
-                </div></div></div></div> <div class="footer-follow"><div class="footer-follow-ul"><a href="https://www.xiaohongshu.com/user/profile/65fc4a98000000000b00e424"><img src="/assets/footer/xiaohongshu.svg" alt></a><a href="https://v.douyin.com/jxK20fi5EQ8/"><img src="/assets/footer/tiktok.svg" alt></a><a href="https://space.bilibili.com/443675010"><img src="/assets/footer/bilibili.svg" alt></a><a href="https://www.hackster.io/m5stack"><img src="/assets/footer/sociallist3.svg" alt></a><a href="https://github.com/m5stack"><img src="/assets/footer/sociallist6.svg" alt></a></div></div> <div class="footer-info-wrapper"><div class="footer-info">
-            深圳市明栈信息科技有限公司
-          </div> <div class="footer-address-info">
-            地址: 
-            中国广东省深圳市宝安区福海街道会展湾南广场A10栋
-          </div> <div class="footer-info">
-            TEL: 
-            +86 755 8657 5379
-          </div> <div class="footer-info">
-            Email: 
-            support@M5Stack.com
-          </div></div></div></div></div> <div class="footer-bottom"><div class="footer-bottom-content"><div class="footer-copy">
-        Copyright ©
-        <a href="https://m5stack.com/">M5Stack Technology Co., Ltd.</a>
-        All rights reserved.
-      </div> <div class="terms-box"><!----> <a href="https://shop.m5stack.com/policies/privacy-policy">Privacy Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/terms-of-service">Terms of Service</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/shipping-policy">Shipping Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/refund-policy">Refund Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/pages/payment-method">Payment Method</a></div> <div class="beian"><a href="https://beian.miit.gov.cn/">粤ICP备16010631号</a></div></div></div> <!----></footer> <div class="float-icon-container"><div class="totop-icon"><svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 280 280" xmlns:xlink="http://www.w3.org/1999/xlink" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M143 70l58 69c1,1 1,3 1,4 -1,1 -2,2 -4,2l-20 0c-2,0 -4,2 -4,4l1 57c0,2 -2,4 -4,4l-62 0c-2,0 -4,-2 -4,-4l1 -57c0,-2 -2,-4 -4,-4l-20 0c-2,0 -3,-1 -4,-2 -1,-1 0,-3 1,-4l58 -69c1,-1 2,-1 3,-1 1,0 2,1 3,1z" class="fil1"></path></g></svg></div> <div class="menu-icon" style="display:none"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 800 800" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M253 229l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 370l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 511l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path></g></svg></div></div></div></div></div></div><script defer src="/_nuxt/static/1788504562/zh_CN/core/Cardputer-Adv/state.js"></script><script src="/_nuxt/41d5c62.js" defer></script><script src="/_nuxt/c970150.js" defer></script><script src="/_nuxt/5a34d22.js" defer></script><script src="/_nuxt/a352c6d.js" defer></script><script src="/_nuxt/b9c4bc6.js" defer></script>
-  </body>
-</html>
diff --git a/devices/m5stack/cardputer-adv/artifacts/mechanical/K132-Adv-cardputer-ADV.pdf b/devices/m5stack/cardputer-adv/artifacts/mechanical/K132-Adv-cardputer-ADV.pdf
deleted file mode 100644
index f15fcf8..0000000
Binary files a/devices/m5stack/cardputer-adv/artifacts/mechanical/K132-Adv-cardputer-ADV.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-adv/artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf b/devices/m5stack/cardputer-adv/artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf
deleted file mode 100644
index a84ba04..0000000
Binary files a/devices/m5stack/cardputer-adv/artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/dependencies.lock b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/dependencies.lock
deleted file mode 100644
index b978818..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/dependencies.lock
+++ /dev/null
@@ -1,75 +0,0 @@
-dependencies:
-  espressif/cmake_utilities:
-    component_hash: 351350613ceafba240b761b4ea991e0f231ac7a9f59a9ee901f751bddc0bb18f
-    dependencies:
-    - name: idf
-      require: private
-      version: '>=4.1'
-    source:
-      registry_url: https://components.espressif.com
-      type: service
-    version: 0.5.3
-  espressif/esp-now:
-    component_hash: 56f902e978ec0b70528ad30a45265b56bf2b91653d13e0badc78159f39f41ece
-    dependencies:
-    - name: espressif/cmake_utilities
-      registry_url: https://components.espressif.com
-      require: private
-      version: 0.*
-    - name: idf
-      require: private
-      version: '>=4.4'
-    source:
-      registry_url: https://components.espressif.com/
-      type: service
-    version: 2.5.2
-  espressif/esp_tinyusb:
-    component_hash: 96d232ced7afe1976119b62f7fbf1944a2a78b36228ff6f7b9318394ac1153cc
-    dependencies:
-    - name: idf
-      require: private
-      version: '>=5.0'
-    - name: espressif/tinyusb
-      registry_url: https://components.espressif.com
-      require: public
-      version: '>=0.14.2'
-    source:
-      registry_url: https://components.espressif.com/
-      type: service
-    version: 1.7.6~1
-  espressif/tinyusb:
-    component_hash: aa65639878f27a44d349044afd9c3fc134a92bd560874fdac1d836019b5c07ca
-    dependencies:
-    - name: idf
-      require: private
-      version: '>=5.0'
-    source:
-      registry_url: https://components.espressif.com
-      type: service
-    targets:
-    - esp32s2
-    - esp32s3
-    - esp32p4
-    version: 0.18.0~4
-  idf:
-    source:
-      type: idf
-    version: 5.4.2
-  jgromes/radiolib:
-    component_hash: 7e367fd420aa66da05687e00dc3775c5891cd8236eee56d9d797d6eb04bb1918
-    dependencies:
-    - name: idf
-      require: private
-      version: '>=4.1'
-    source:
-      registry_url: https://components.espressif.com/
-      type: service
-    version: 7.2.1
-direct_dependencies:
-- espressif/esp-now
-- espressif/esp_tinyusb
-- idf
-- jgromes/radiolib
-manifest_hash: 11dfa23746cd56272c7e2231f3316fed15687713e403eee1876bad6e4bb0f037
-target: esp32s3
-version: 2.0.0
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/hal_config.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/hal_config.h
deleted file mode 100644
index a160913..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/hal_config.h
+++ /dev/null
@@ -1,19 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#pragma once
-
-#define HAL_PIN_KEYBOARD_INT   11
-#define HAL_PIN_IR_TX          44
-#define HAL_PIN_SPI_MISO       GPIO_NUM_39
-#define HAL_PIN_SPI_MOSI       GPIO_NUM_14
-#define HAL_PIN_SPI_SCLK       GPIO_NUM_40
-#define HAL_PIN_SD_CARD_CS     GPIO_NUM_12
-#define HAL_PIN_GPS_TX         GPIO_NUM_13
-#define HAL_PIN_GPS_RX         GPIO_NUM_15
-#define HAL_PIN_LORA_NSS_GPIO  5
-#define HAL_PIN_LORA_RST_GPIO  3
-#define HAL_PIN_LORA_BUSY_GPIO 6
-#define HAL_PIN_LORA_DIO1_GPIO 4
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/partitions.csv b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/partitions.csv
deleted file mode 100644
index 8abc0c9..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/partitions.csv
+++ /dev/null
@@ -1,6 +0,0 @@
-# ESP-IDF Partition Table
-# Name,   Type, SubType, Offset,  Size, Flags
-nvs,      data, nvs,     0x9000,  0x4000,
-otadata,  data, ota,     0xd000,  0x2000,
-phy_init, data, phy,     0xf000,  0x1000,
-factory,  app,  factory, 0x10000, 4M,
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/repos.json b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/repos.json
deleted file mode 100644
index 99ff131..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/repos.json
+++ /dev/null
@@ -1,27 +0,0 @@
-[
-    {
-        "url": "https://github.com/m5stack/M5GFX.git",
-        "path": "components/M5GFX",
-        "branch": "0.2.15"
-    },
-    {
-        "url": "https://github.com/m5stack/M5Unified.git",
-        "path": "components/M5Unified",
-        "branch": "0.2.10"
-    },
-    {
-        "url": "https://github.com/Forairaaaaa/mooncake.git",
-        "path": "components/mooncake",
-        "branch": "v2.2.0"
-    },
-    {
-        "url": "https://github.com/Forairaaaaa/mooncake_log.git",
-        "path": "components/mooncake_log",
-        "branch": "v1.3.0"
-    },
-    {
-        "url": "https://github.com/Forairaaaaa/smooth_ui_toolkit.git",
-        "path": "components/smooth_ui_toolkit",
-        "branch": "v2.4.0"
-    }
-]
\ No newline at end of file
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/sdkconfig.defaults b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/sdkconfig.defaults
deleted file mode 100644
index 8d8b8d6..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/sdkconfig.defaults
+++ /dev/null
@@ -1,26 +0,0 @@
-# This file was generated using idf.py save-defconfig. It can be edited manually.
-# Espressif IoT Development Framework (ESP-IDF) 5.4.2 Project Minimal Configuration
-#
-CONFIG_IDF_TARGET="esp32s3"
-CONFIG_ESPTOOLPY_FLASHSIZE_8MB=y
-CONFIG_PARTITION_TABLE_CUSTOM=y
-CONFIG_EXAMPLE_KBD_ENABLE=y
-CONFIG_BT_ENABLED=y
-CONFIG_BT_NIMBLE_ENABLED=y
-CONFIG_BT_NIMBLE_SM_LVL=2
-CONFIG_BT_NIMBLE_NVS_PERSIST=y
-CONFIG_BT_NIMBLE_SVC_GAP_DEVICE_NAME="CardputerADV Keyboard"
-CONFIG_BT_NIMBLE_SVC_BAS_BATTERY_LEVEL_NOTIFY=y
-# Request connection parameters optimised for a HID keyboard.
-# See ble_gap_upd_params in source code for dynamic set.
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_MIN_CONN_INTERVAL=12
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_MAX_CONN_INTERVAL=48
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_SLAVE_LATENCY=8
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_SUPERVISION_TMO=600
-CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_240=y
-CONFIG_ESP_MAIN_TASK_STACK_SIZE=4096
-CONFIG_ESP_CONSOLE_USB_SERIAL_JTAG=y
-CONFIG_FREERTOS_HZ=1000
-CONFIG_ESPNOW_CONTROL_AUTO_CHANNEL_SENDING=y
-CONFIG_ESPNOW_CONTROL_AUTO_CHANNEL_FORWARD=y
-CONFIG_TINYUSB_HID_COUNT=1
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/.clang-format b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/.clang-format
deleted file mode 100644
index d3c4cc9..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/.clang-format
+++ /dev/null
@@ -1,164 +0,0 @@
-BasedOnStyle:  Google
-AccessModifierOffset: -4
-AlignAfterOpenBracket: Align
-AlignConsecutiveMacros: true
-AlignConsecutiveAssignments: true
-AlignConsecutiveDeclarations: false
-AlignEscapedNewlines: Left
-AlignOperands:   true
-AlignTrailingComments: true
-AllowAllArgumentsOnNextLine: true
-AllowAllConstructorInitializersOnNextLine: true
-AllowAllParametersOfDeclarationOnNextLine: true
-AllowShortBlocksOnASingleLine: Never
-AllowShortCaseLabelsOnASingleLine: false
-AllowShortFunctionsOnASingleLine: false
-AllowShortLambdasOnASingleLine: All
-AllowShortIfStatementsOnASingleLine: WithoutElse
-AllowShortLoopsOnASingleLine: true
-AlwaysBreakAfterDefinitionReturnType: None
-AlwaysBreakAfterReturnType: None
-AlwaysBreakBeforeMultilineStrings: true
-AlwaysBreakTemplateDeclarations: Yes
-BinPackArguments: true
-BinPackParameters: true
-BraceWrapping:
-  AfterCaseLabel:  false
-  AfterClass:      false
-  AfterControlStatement: false
-  AfterEnum:       false
-  AfterFunction:   true
-  AfterNamespace:  false
-  AfterObjCDeclaration: false
-  AfterStruct:     false
-  AfterUnion:      false
-  AfterExternBlock: false
-  BeforeCatch:     false
-  BeforeElse:      false
-  IndentBraces:    false
-  SplitEmptyFunction: true
-  SplitEmptyRecord: true
-  SplitEmptyNamespace: true
-BreakBeforeBinaryOperators: None
-BreakBeforeBraces: Custom
-BreakBeforeInheritanceComma: false
-BreakInheritanceList: BeforeColon
-BreakBeforeTernaryOperators: true
-BreakConstructorInitializersBeforeComma: false
-BreakConstructorInitializers: BeforeColon
-BreakAfterJavaFieldAnnotations: false
-BreakStringLiterals: true
-ColumnLimit:     120
-CommentPragmas:  '^ IWYU pragma:'
-CompactNamespaces: false
-ConstructorInitializerAllOnOneLineOrOnePerLine: true
-ConstructorInitializerIndentWidth: 4
-ContinuationIndentWidth: 4
-Cpp11BracedListStyle: true
-DeriveLineEnding: true
-DerivePointerAlignment: true
-DisableFormat:   false
-ExperimentalAutoDetectBinPacking: false
-FixNamespaceComments: true
-ForEachMacros:
-  - foreach
-  - Q_FOREACH
-  - BOOST_FOREACH
-IncludeBlocks:   Regroup
-IncludeCategories:
-  - Regex:           '^<ext/.*\.h>'
-    Priority:        2
-    SortPriority:    0
-  - Regex:           '^<.*\.h>'
-    Priority:        1
-    SortPriority:    0
-  - Regex:           '^<.*'
-    Priority:        2
-    SortPriority:    0
-  - Regex:           '.*'
-    Priority:        3
-    SortPriority:    0
-IncludeIsMainRegex: '([-_](test|unittest))?$'
-IncludeIsMainSourceRegex: ''
-IndentCaseLabels: true
-IndentGotoLabels: true
-IndentPPDirectives: None
-IndentWidth:     4
-IndentWrappedFunctionNames: false
-JavaScriptQuotes: Leave
-JavaScriptWrapImports: true
-KeepEmptyLinesAtTheStartOfBlocks: false
-MacroBlockBegin: ''
-MacroBlockEnd:   ''
-MaxEmptyLinesToKeep: 1
-NamespaceIndentation: None
-ObjCBinPackProtocolList: Never
-ObjCBlockIndentWidth: 2
-ObjCSpaceAfterProperty: false
-ObjCSpaceBeforeProtocolList: true
-PenaltyBreakAssignment: 2
-PenaltyBreakBeforeFirstCallParameter: 1
-PenaltyBreakComment: 300
-PenaltyBreakFirstLessLess: 120
-PenaltyBreakString: 1000
-PenaltyBreakTemplateDeclaration: 10
-PenaltyExcessCharacter: 1000000
-PenaltyReturnTypeOnItsOwnLine: 200
-PointerAlignment: Left
-RawStringFormats:
-  - Language:        Cpp
-    Delimiters:
-      - cc
-      - CC
-      - cpp
-      - Cpp
-      - CPP
-      - 'c++'
-      - 'C++'
-    CanonicalDelimiter: ''
-    BasedOnStyle:    google
-  - Language:        TextProto
-    Delimiters:
-      - pb
-      - PB
-      - proto
-      - PROTO
-    EnclosingFunctions:
-      - EqualsProto
-      - EquivToProto
-      - PARSE_PARTIAL_TEXT_PROTO
-      - PARSE_TEST_PROTO
-      - PARSE_TEXT_PROTO
-      - ParseTextOrDie
-      - ParseTextProtoOrDie
-    CanonicalDelimiter: ''
-    BasedOnStyle:    google
-ReflowComments:  true
-SortIncludes:    false
-SortUsingDeclarations: true
-SpaceAfterCStyleCast: false
-SpaceAfterLogicalNot: false
-SpaceAfterTemplateKeyword: true
-SpaceBeforeAssignmentOperators: true
-SpaceBeforeCpp11BracedList: false
-SpaceBeforeCtorInitializerColon: true
-SpaceBeforeInheritanceColon: true
-SpaceBeforeParens: ControlStatements
-SpaceBeforeRangeBasedForLoopColon: true
-SpaceInEmptyBlock: false
-SpaceInEmptyParentheses: false
-SpacesBeforeTrailingComments: 2
-SpacesInAngles:  false
-SpacesInConditionalStatement: false
-SpacesInContainerLiterals: true
-SpacesInCStyleCastParentheses: false
-SpacesInParentheses: false
-SpacesInSquareBrackets: false
-SpaceBeforeSquareBrackets: false
-Standard:        Auto
-StatementMacros:
-  - Q_UNUSED
-  - QT_REQUIRE_VERSION
-TabWidth:        4
-UseCRLF:         false
-UseTab:          Never
\ No newline at end of file
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/README.md b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/README.md
deleted file mode 100644
index c9c7f9c..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/README.md
+++ /dev/null
@@ -1,11 +0,0 @@
-
-# M5Cardputer
-
-## Basic library for M5Stack M5Cardputer and M5Cardputer-ADV Board 
-
-
-License
-----------------
-M5GFX : [MIT](https://github.com/m5stack/M5GFX/blob/master/LICENSE)  
-M5Unified : [MIT](https://github.com/m5stack/M5Unified/blob/master/LICENSE)  
- 
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Advanced/SSHClient/SSHClient.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Advanced/SSHClient/SSHClient.ino
deleted file mode 100644
index 5d25f8b..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Advanced/SSHClient/SSHClient.ino
+++ /dev/null
@@ -1,272 +0,0 @@
-/**
- * @file SSHClient.ino
- * @author aat440hz (https://github.com/aat440hz/SSHClient-M5Cardputer)
- * @brief M5Cardputer SSHClient
- * @version 0.1
- * @date 2023-12-27
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.9
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- * LibSSH-ESP32: https://github.com/ewpa/LibSSH-ESP32
- */
-
-#include <WiFi.h>
-#include <M5Cardputer.h>
-#include "libssh_esp32.h"
-#include <libssh/libssh.h>
-
-const char* ssid     = "Your_SSID";      // Replace with your WiFi SSID
-const char* password = "Your_Password";  // Replace with your WiFi password
-
-// SSH server configuration (initialize as empty strings)
-String ssh_host     = "";
-String ssh_user     = "";
-String ssh_password = "";
-
-// M5Cardputer setup
-M5Canvas canvas(&M5Cardputer.Display);
-String commandBuffer              = "> ";
-int cursorY                       = 0;
-const int lineHeight              = 32;
-unsigned long lastKeyPressMillis  = 0;
-const unsigned long debounceDelay = 200;  // Adjust debounce delay as needed
-
-ssh_session my_ssh_session;
-ssh_channel channel;
-
-void waitForInput(String& input);
-
-bool filterAnsiSequences =
-    true;  // Set to false to disable ANSI sequence filtering
-
-void setup() {
-    Serial.begin(115200);  // Initialize serial communication for debugging
-    Serial.println("Starting Setup");
-
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg, true);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextSize(1);  // Set text size
-
-    // Connect to WiFi
-    WiFi.begin(ssid, password);
-    while (WiFi.status() != WL_CONNECTED) {
-        delay(500);
-        Serial.print(".");
-    }
-    Serial.println("\nWiFi Connected");
-
-    // Initialize the cursor Y position
-    cursorY = M5Cardputer.Display.getCursorY();
-
-    // Prompt for SSH host, username, and password
-    M5Cardputer.Display.print("SSH Host: ");
-    waitForInput(ssh_host);
-    M5Cardputer.Display.print("\nSSH Username: ");
-    waitForInput(ssh_user);
-    M5Cardputer.Display.print("\nSSH Password: ");
-    waitForInput(ssh_password);
-
-    // Connect and authenticate with SSH server
-    my_ssh_session = ssh_new();
-    if (my_ssh_session == NULL) {
-        Serial.println("SSH Session creation failed.");
-        return;
-    }
-    ssh_options_set(my_ssh_session, SSH_OPTIONS_HOST, ssh_host.c_str());
-    ssh_options_set(my_ssh_session, SSH_OPTIONS_USER, ssh_user.c_str());
-
-    if (ssh_connect(my_ssh_session) != SSH_OK) {
-        Serial.println("SSH Connect error.");
-        ssh_free(my_ssh_session);
-        return;
-    }
-
-    if (ssh_userauth_password(my_ssh_session, NULL, ssh_password.c_str()) !=
-        SSH_AUTH_SUCCESS) {
-        Serial.println("SSH Authentication error.");
-        ssh_disconnect(my_ssh_session);
-        ssh_free(my_ssh_session);
-        return;
-    }
-
-    channel = ssh_channel_new(my_ssh_session);
-    if (channel == NULL || ssh_channel_open_session(channel) != SSH_OK) {
-        Serial.println("SSH Channel open error.");
-        ssh_disconnect(my_ssh_session);
-        ssh_free(my_ssh_session);
-        return;
-    }
-
-    if (ssh_channel_request_pty(channel) != SSH_OK) {
-        Serial.println("SSH PTY request error.");
-        ssh_channel_close(channel);
-        ssh_channel_free(channel);
-        ssh_disconnect(my_ssh_session);
-        ssh_free(my_ssh_session);
-        return;
-    }
-
-    if (ssh_channel_request_shell(channel) != SSH_OK) {
-        Serial.println("SSH Shell request error.");
-        ssh_channel_close(channel);
-        ssh_channel_free(channel);
-        ssh_disconnect(my_ssh_session);
-        ssh_free(my_ssh_session);
-        return;
-    }
-
-    Serial.println("SSH setup completed.");
-}
-
-void loop() {
-    M5Cardputer.update();
-
-    // Handle keyboard input with debounce
-    if (M5Cardputer.Keyboard.isChange() && M5Cardputer.Keyboard.isPressed()) {
-        unsigned long currentMillis = millis();
-        if (currentMillis - lastKeyPressMillis >= debounceDelay) {
-            lastKeyPressMillis               = currentMillis;
-            Keyboard_Class::KeysState status = M5Cardputer.Keyboard.keysState();
-
-            for (auto i : status.word) {
-                commandBuffer += i;
-                M5Cardputer.Display.print(i);
-                cursorY = M5Cardputer.Display.getCursorY();
-            }
-
-            if (status.del && commandBuffer.length() > 2) {
-                commandBuffer.remove(commandBuffer.length() - 1);
-                M5Cardputer.Display.setCursor(
-                    M5Cardputer.Display.getCursorX() - 6,
-                    M5Cardputer.Display.getCursorY());
-                M5Cardputer.Display.print(" ");
-                M5Cardputer.Display.setCursor(
-                    M5Cardputer.Display.getCursorX() - 6,
-                    M5Cardputer.Display.getCursorY());
-                cursorY = M5Cardputer.Display.getCursorY();
-            }
-
-            if (status.enter) {
-                commandBuffer.trim();  // Trim the command buffer to remove
-                                       // accidental whitespaces/newlines
-                String message = commandBuffer.substring(
-                    2);  // Get the command part, exclude the "> "
-                ssh_channel_write(channel, message.c_str(),
-                                  message.length());  // Send the command
-                ssh_channel_write(channel, "\r",
-                                  1);  // Send exactly one carriage return (try
-                                       // "\n" or "\r\n" if needed)
-
-                commandBuffer = "> ";  // Reset command buffer
-                M5Cardputer.Display.print(
-                    '\n');  // Move to the next line on display
-                cursorY =
-                    M5Cardputer.Display.getCursorY();  // Update cursor position
-            }
-        }
-    }
-
-    // Check if the cursor has reached the bottom of the display
-    if (cursorY > M5Cardputer.Display.height() - lineHeight) {
-        M5Cardputer.Display.scroll(0, -lineHeight);
-        cursorY -= lineHeight;
-        M5Cardputer.Display.setCursor(M5Cardputer.Display.getCursorX(),
-                                      cursorY);
-    }
-
-    // Read data from SSH server and display it, handling ANSI sequences
-    char buffer[128];  // Reduced buffer size for less memory usage
-    int nbytes =
-        ssh_channel_read_nonblocking(channel, buffer, sizeof(buffer), 0);
-    bool isAnsiSequence =
-        false;  // To track when we are inside an ANSI sequence
-
-    if (nbytes > 0) {
-        for (int i = 0; i < nbytes; ++i) {
-            char c = buffer[i];
-            if (filterAnsiSequences) {
-                if (c == '\033') {
-                    isAnsiSequence = true;  // Enter ANSI sequence mode
-                } else if (isAnsiSequence) {
-                    if (isalpha(c)) {
-                        isAnsiSequence = false;  // Exit ANSI sequence mode at
-                                                 // the end character
-                    }
-                } else {
-                    if (c == '\r') continue;  // Ignore carriage return
-                    M5Cardputer.Display.write(c);
-                    cursorY = M5Cardputer.Display.getCursorY();
-                }
-            } else {
-                if (c == '\r') continue;  // Ignore carriage return
-                M5Cardputer.Display.write(c);
-                cursorY = M5Cardputer.Display.getCursorY();
-            }
-        }
-    }
-
-    // Handle channel closure and other conditions
-    if (nbytes < 0 || ssh_channel_is_closed(channel)) {
-        ssh_channel_close(channel);
-        ssh_channel_free(channel);
-        ssh_disconnect(my_ssh_session);
-        ssh_free(my_ssh_session);
-        M5Cardputer.Display.println("\nSSH session closed.");
-        return;  // Exit the loop upon session closure
-    }
-}
-
-void waitForInput(String& input) {
-    unsigned long startTime           = millis();
-    unsigned long lastKeyPressMillis  = 0;
-    const unsigned long debounceDelay = 200;  // Adjust debounce delay as needed
-    String currentInput               = input;
-
-    while (true) {
-        M5Cardputer.update();
-        if (M5Cardputer.Keyboard.isChange()) {
-            Keyboard_Class::KeysState status = M5Cardputer.Keyboard.keysState();
-
-            if (status.del && currentInput.length() > 0) {
-                // Handle backspace key
-                currentInput.remove(currentInput.length() - 1);
-                M5Cardputer.Display.setCursor(
-                    M5Cardputer.Display.getCursorX() - 6,
-                    M5Cardputer.Display.getCursorY());
-                M5Cardputer.Display.print(" ");
-                M5Cardputer.Display.setCursor(
-                    M5Cardputer.Display.getCursorX() - 6,
-                    M5Cardputer.Display.getCursorY());
-                cursorY            = M5Cardputer.Display.getCursorY();
-                lastKeyPressMillis = millis();
-            }
-
-            for (auto i : status.word) {
-                if (millis() - lastKeyPressMillis >= debounceDelay) {
-                    currentInput += i;
-                    M5Cardputer.Display.print(i);
-                    cursorY            = M5Cardputer.Display.getCursorY();
-                    lastKeyPressMillis = millis();
-                }
-            }
-
-            if (status.enter) {
-                M5Cardputer.Display.println();  // Move to the next line
-                input = currentInput;
-                break;
-            }
-        }
-
-        if (millis() - startTime > 180000) {  // Timeout after 3 minutes
-            M5Cardputer.Display.println("\nInput timeout. Rebooting...");
-            delay(1000);    // Delay for 1 second to allow the message to be
-                            // displayed
-            ESP.restart();  // Reboot the ESP32
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/button/button.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/button/button.ino
deleted file mode 100644
index 0fe811d..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/button/button.ino
+++ /dev/null
@@ -1,47 +0,0 @@
-/**
- * @file button.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer Button Test
- * @version 0.1
- * @date 2023-10-09
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-
-#include "M5Cardputer.h"
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextColor(GREEN);
-    M5Cardputer.Display.setTextDatum(middle_center);
-    M5Cardputer.Display.setTextFont(&fonts::Orbitron_Light_32);
-    M5Cardputer.Display.setTextSize(1);
-    M5Cardputer.Display.drawString("Button Test",
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2);
-}
-
-void loop() {
-    M5Cardputer.update();
-    if (M5Cardputer.BtnA.wasPressed()) {
-        M5Cardputer.Speaker.tone(8000, 20);
-        M5Cardputer.Display.clear();
-        M5Cardputer.Display.drawString("Pressed",
-                                       M5Cardputer.Display.width() / 2,
-                                       M5Cardputer.Display.height() / 2);
-    }
-    if (M5Cardputer.BtnA.wasReleased()) {
-        M5Cardputer.Speaker.tone(8000, 20);
-        M5Cardputer.Display.clear();
-        M5Cardputer.Display.drawString("Released",
-                                       M5Cardputer.Display.width() / 2,
-                                       M5Cardputer.Display.height() / 2);
-    }
-}
\ No newline at end of file
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/buzzer/buzzer.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/buzzer/buzzer.ino
deleted file mode 100644
index d28c8e9..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/buzzer/buzzer.ino
+++ /dev/null
@@ -1,35 +0,0 @@
-/**
- * @file buzzer.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer Buzzer Test
- * @version 0.1
- * @date 2023-10-09
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-#include "M5Cardputer.h"
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextColor(GREEN);
-    M5Cardputer.Display.setTextDatum(middle_center);
-    M5Cardputer.Display.setTextFont(&fonts::Orbitron_Light_32);
-    M5Cardputer.Display.setTextSize(1);
-    M5Cardputer.Display.drawString("Buzzer Test",
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2);
-}
-
-void loop() {
-    M5Cardputer.Speaker.tone(10000, 100);
-    delay(1000);
-    M5Cardputer.Speaker.tone(4000, 20);
-    delay(1000);
-}
\ No newline at end of file
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/display/display.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/display/display.ino
deleted file mode 100644
index 952e888..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/display/display.ino
+++ /dev/null
@@ -1,42 +0,0 @@
-/**
- * @file display.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer Display Test
- * @version 0.1
- * @date 2023-10-09
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-#include "M5Cardputer.h"
-
-void draw_function(LovyanGFX* gfx) {
-    int x      = rand() % gfx->width();
-    int y      = rand() % gfx->height();
-    int r      = (gfx->width() >> 4) + 2;
-    uint16_t c = rand();
-    gfx->fillRect(x - r, y - r, r * 2, r * 2, c);
-}
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg);
-    int textsize = M5Cardputer.Display.height() / 60;
-    if (textsize == 0) {
-        textsize = 1;
-    }
-    M5Cardputer.Display.setTextSize(textsize);
-}
-
-void loop() {
-    int x      = rand() % M5Cardputer.Display.width();
-    int y      = rand() % M5Cardputer.Display.height();
-    int r      = (M5Cardputer.Display.width() >> 4) + 2;
-    uint16_t c = rand();
-    M5Cardputer.Display.fillCircle(x, y, r, c);
-    draw_function(&M5Cardputer.Display);
-}
\ No newline at end of file
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/ir_nec/ir_nec.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/ir_nec/ir_nec.ino
deleted file mode 100644
index cb56616..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/ir_nec/ir_nec.ino
+++ /dev/null
@@ -1,76 +0,0 @@
-/**
- * @file ir_nec.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer IR NEC test
- * @version 0.1
- * @date 2023-10-13
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- * IRremote: https://github.com/Arduino-IRremote/Arduino-IRremote
- */
-
-#define DISABLE_CODE_FOR_RECEIVER  // Disables restarting receiver after each
-                                   // send. Saves 450 bytes program memory and
-                                   // 269 bytes RAM if receiving functions are
-                                   // not used.
-#define SEND_PWM_BY_TIMER
-#define IR_TX_PIN 44
-
-#include "M5Cardputer.h"
-#include <IRremote.hpp>  // include the library
-
-uint8_t sCommand = 0x34;
-uint8_t sRepeats = 0;
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg, true);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextColor(GREEN);
-    M5Cardputer.Display.setTextDatum(middle_center);
-    M5Cardputer.Display.setTextFont(&fonts::Orbitron_Light_24);
-    M5Cardputer.Display.setTextSize(1);
-
-    IrSender.begin(DISABLE_LED_FEEDBACK);  // Start with IR_SEND_PIN as send pin
-    IrSender.setSendPin(IR_TX_PIN);
-}
-
-void loop() {
-    Serial.println();
-    Serial.print(F("Send now: address=0x1111, command=0x"));
-    Serial.print(sCommand, HEX);
-    Serial.print(F(", repeats="));
-    Serial.print(sRepeats);
-    Serial.println();
-
-    M5Cardputer.Display.clear();
-    M5Cardputer.Display.drawString("IR NEC SEND",
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2 - 40);
-
-    M5Cardputer.Display.drawString("ADDR:0x1111",
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2);
-
-    M5Cardputer.Display.drawString("CMD:0x" + String(sCommand, HEX),
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2 + 40);
-
-    Serial.println(F("Send standard NEC with 16 bit address"));
-
-    M5Cardputer.Display.fillCircle(32, 105, 8, GREEN);
-    IrSender.sendNEC(0x1111, sCommand, sRepeats);
-    // IrSender.sendOnkyo(0x1111, 0x2223, sRepeats);
-    /*
-     * Increment send values
-     */
-    sCommand += 1;
-    delay(500);
-    M5Cardputer.Display.fillCircle(32, 105, 8, YELLOW);
-    delay(500);
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/inputText/inputText.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/inputText/inputText.ino
deleted file mode 100644
index 6fb81b8..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/inputText/inputText.ino
+++ /dev/null
@@ -1,73 +0,0 @@
-/**
- * @file inputText.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer input text test
- * @version 0.1
- * @date 2023-10-13
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-
-#include "M5Cardputer.h"
-#include "M5GFX.h"
-
-M5Canvas canvas(&M5Cardputer.Display);
-String data = "> ";
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg, true);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextSize(0.5);
-    M5Cardputer.Display.drawRect(0, 0, M5Cardputer.Display.width(),
-                                 M5Cardputer.Display.height() - 28, GREEN);
-    M5Cardputer.Display.setTextFont(&fonts::FreeSerifBoldItalic18pt7b);
-
-    M5Cardputer.Display.fillRect(0, M5Cardputer.Display.height() - 4,
-                                 M5Cardputer.Display.width(), 4, GREEN);
-
-    canvas.setTextFont(&fonts::FreeSerifBoldItalic18pt7b);
-    canvas.setTextSize(0.5);
-    canvas.createSprite(M5Cardputer.Display.width() - 8,
-                        M5Cardputer.Display.height() - 36);
-    canvas.setTextScroll(true);
-    canvas.println("Press Key and Enter to Input Text");
-    canvas.pushSprite(4, 4);
-    M5Cardputer.Display.drawString(data, 4, M5Cardputer.Display.height() - 24);
-}
-
-void loop() {
-    M5Cardputer.update();
-    if (M5Cardputer.Keyboard.isChange()) {
-        if (M5Cardputer.Keyboard.isPressed()) {
-            Keyboard_Class::KeysState status = M5Cardputer.Keyboard.keysState();
-
-            for (auto i : status.word) {
-                data += i;
-            }
-
-            if (status.del) {
-                data.remove(data.length() - 1);
-            }
-
-            if (status.enter) {
-                data.remove(0, 2);
-                canvas.println(data);
-                canvas.pushSprite(4, 4);
-                data = "> ";
-            }
-
-            M5Cardputer.Display.fillRect(0, M5Cardputer.Display.height() - 28,
-                                         M5Cardputer.Display.width(), 25,
-                                         BLACK);
-
-            M5Cardputer.Display.drawString(data, 4,
-                                           M5Cardputer.Display.height() - 24);
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/multiPress/multiPress.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/multiPress/multiPress.ino
deleted file mode 100644
index b412edc..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/multiPress/multiPress.ino
+++ /dev/null
@@ -1,56 +0,0 @@
-/**
- * @file multiPress.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer multi key test
- * @version 0.1
- * @date 2023-10-13
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-
-#include "M5Cardputer.h"
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg, true);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextColor(GREEN);
-    M5Cardputer.Display.setTextDatum(middle_center);
-    M5Cardputer.Display.setTextFont(&fonts::FreeSerifBoldItalic18pt7b);
-    M5Cardputer.Display.setTextSize(1);
-    M5Cardputer.Display.drawString("Press Any Key",
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2);
-}
-
-void loop() {
-    M5Cardputer.update();
-    // max press 3 button at the same time
-    if (M5Cardputer.Keyboard.isChange()) {
-        if (M5Cardputer.Keyboard.isPressed()) {
-            Keyboard_Class::KeysState status = M5Cardputer.Keyboard.keysState();
-            String keyStr                    = "";
-            for (auto i : status.word) {
-                if (keyStr != "") {
-                    keyStr = keyStr + "+" + i;
-                } else {
-                    keyStr += i;
-                }
-            }
-            M5Cardputer.Display.clear();
-            M5Cardputer.Display.drawString(keyStr,
-                                           M5Cardputer.Display.width() / 2,
-                                           M5Cardputer.Display.height() / 2);
-        } else {
-            M5Cardputer.Display.clear();
-            M5Cardputer.Display.drawString("Press Any Key",
-                                           M5Cardputer.Display.width() / 2,
-                                           M5Cardputer.Display.height() / 2);
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/singlePress/singlePress.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/singlePress/singlePress.ino
deleted file mode 100644
index 1181a2a..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/singlePress/singlePress.ino
+++ /dev/null
@@ -1,46 +0,0 @@
-/**
- * @file singlePress.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer single key test
- * @version 0.1
- * @date 2023-10-13
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-
-#include "M5Cardputer.h"
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg, true);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextColor(GREEN);
-    M5Cardputer.Display.setTextDatum(middle_center);
-    M5Cardputer.Display.setTextFont(&fonts::FreeSerifBoldItalic18pt7b);
-    M5Cardputer.Display.setTextSize(1);
-    M5Cardputer.Display.drawString("Press a Key",
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2);
-}
-
-void loop() {
-    M5Cardputer.update();
-    if (M5Cardputer.Keyboard.isChange()) {
-        if (M5Cardputer.Keyboard.isKeyPressed('a')) {
-            M5Cardputer.Display.clear();
-            M5Cardputer.Display.drawString("a Pressed",
-                                           M5Cardputer.Display.width() / 2,
-                                           M5Cardputer.Display.height() / 2);
-        } else {
-            M5Cardputer.Display.clear();
-            M5Cardputer.Display.drawString("Press a Key",
-                                           M5Cardputer.Display.width() / 2,
-                                           M5Cardputer.Display.height() / 2);
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/usbKeyboard/usbKeyboard.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/usbKeyboard/usbKeyboard.ino
deleted file mode 100644
index 5fe8fcd..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/usbKeyboard/usbKeyboard.ino
+++ /dev/null
@@ -1,82 +0,0 @@
-/**
- * @file usbKeyboard.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer USB Keyboard test
- * @version 0.1
- * @date 2023-10-13
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-
-#include "M5Cardputer.h"
-#include "USB.h"
-#include "USBHIDKeyboard.h"
-USBHIDKeyboard Keyboard;
-
-void setup() {
-    auto cfg = M5.config();
-    M5Cardputer.begin(cfg, true);
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextColor(GREEN);
-    M5Cardputer.Display.setTextDatum(middle_center);
-    M5Cardputer.Display.setTextFont(&fonts::Orbitron_Light_24);
-    M5Cardputer.Display.setTextSize(1);
-    M5Cardputer.Display.drawString("USB Keyboard",
-                                   M5Cardputer.Display.width() / 2,
-                                   M5Cardputer.Display.height() / 2);
-    Keyboard.begin();
-    USB.begin();
-}
-
-void loop() {
-    M5Cardputer.update();
-    // max press 3 button at the same time
-    if (M5Cardputer.Keyboard.isChange()) {
-        if (M5Cardputer.Keyboard.isPressed()) {
-            Keyboard_Class::KeysState status = M5Cardputer.Keyboard.keysState();
-            // for (auto i : status.word) {
-            //     Keyboard.press(i);
-            // }
-            KeyReport report = {0};
-            report.modifiers = status.modifiers;
-            uint8_t index    = 0;
-            for (auto i : status.hid_keys) {
-                report.keys[index] = i;
-                index++;
-                if (index > 5) {
-                    index = 5;
-                }
-            }
-            Keyboard.sendReport(&report);
-            Keyboard.releaseAll();
-
-            // only text for display
-            String keyStr = "";
-            for (auto i : status.word) {
-                if (keyStr != "") {
-                    keyStr = keyStr + "+" + i;
-                } else {
-                    keyStr += i;
-                }
-            }
-
-            if (keyStr.length() > 0) {
-                M5Cardputer.Display.clear();
-                M5Cardputer.Display.drawString(
-                    keyStr, M5Cardputer.Display.width() / 2,
-                    M5Cardputer.Display.height() / 2);
-            }
-
-        } else {
-            M5Cardputer.Display.clear();
-            M5Cardputer.Display.drawString("USB Keyboard",
-                                           M5Cardputer.Display.width() / 2,
-                                           M5Cardputer.Display.height() / 2);
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic/mic.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic/mic.ino
deleted file mode 100644
index 27d4c24..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic/mic.ino
+++ /dev/null
@@ -1,146 +0,0 @@
-/**
- * @file mic.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer Microphone Record Test
- * @version 0.1
- * @date 2023-10-09
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- */
-
-#include <M5Cardputer.h>
-
-static constexpr const size_t record_number     = 256;
-static constexpr const size_t record_length     = 240;
-static constexpr const size_t record_size       = record_number * record_length;
-static constexpr const size_t record_samplerate = 17000;
-static int16_t prev_y[record_length];
-static int16_t prev_h[record_length];
-static size_t rec_record_idx  = 2;
-static size_t draw_record_idx = 0;
-static int16_t *rec_data;
-
-void setup(void) {
-    auto cfg = M5.config();
-
-    M5Cardputer.begin(cfg);
-
-    M5Cardputer.Display.startWrite();
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextDatum(top_center);
-    M5Cardputer.Display.setTextColor(WHITE);
-    M5Cardputer.Display.setFont(&fonts::FreeSansBoldOblique12pt7b);
-
-    rec_data = (typeof(rec_data))heap_caps_malloc(record_size *
-
-                                                      sizeof(int16_t),
-                                                  MALLOC_CAP_8BIT);
-    memset(rec_data, 0, record_size * sizeof(int16_t));
-    M5Cardputer.Speaker.setVolume(255);
-
-    /// Since the microphone and speaker cannot be used at the same time,
-    // turn
-    /// off the speaker here.
-    M5Cardputer.Speaker.end();
-    M5Cardputer.Mic.begin();
-    M5Cardputer.Display.fillCircle(70, 15, 8, RED);
-    M5Cardputer.Display.drawString("REC", 120, 3);
-}
-
-void loop(void) {
-    M5Cardputer.update();
-
-    if (M5Cardputer.Mic.isEnabled()) {
-        static constexpr int shift = 6;
-        auto data                  = &rec_data[rec_record_idx * record_length];
-        if (M5Cardputer.Mic.record(data, record_length, record_samplerate)) {
-            data = &rec_data[draw_record_idx * record_length];
-
-            int32_t w = M5Cardputer.Display.width();
-            if (w > record_length - 1) {
-                w = record_length - 1;
-            }
-            for (int32_t x = 0; x < w; ++x) {
-                M5Cardputer.Display.writeFastVLine(x, prev_y[x], prev_h[x],
-                                                   TFT_BLACK);
-                int32_t y1 = (data[x] >> shift);
-                int32_t y2 = (data[x + 1] >> shift);
-                if (y1 > y2) {
-                    int32_t tmp = y1;
-                    y1          = y2;
-                    y2          = tmp;
-                }
-                int32_t y = ((M5Cardputer.Display.height()) >> 1) + y1;
-                int32_t h = ((M5Cardputer.Display.height()) >> 1) + y2 + 1 - y;
-                prev_y[x] = y;
-                prev_h[x] = h;
-                M5Cardputer.Display.writeFastVLine(x, prev_y[x], prev_h[x],
-                                                   WHITE);
-            }
-
-            M5Cardputer.Display.display();
-            M5Cardputer.Display.fillCircle(70, 15, 8, RED);
-            M5Cardputer.Display.drawString("REC", 120, 3);
-            if (++draw_record_idx >= record_number) {
-                draw_record_idx = 0;
-            }
-            if (++rec_record_idx >= record_number) {
-                rec_record_idx = 0;
-            }
-        }
-    }
-
-    if (M5Cardputer.BtnA.wasHold()) {
-        auto cfg               = M5Cardputer.Mic.config();
-        cfg.noise_filter_level = (cfg.noise_filter_level + 8) & 255;
-        M5Cardputer.Mic.config(cfg);
-        M5Cardputer.Display.clear();
-        M5Cardputer.Display.fillCircle(70, 15, 8, GREEN);
-        M5Cardputer.Display.drawString("NF:" + String(cfg.noise_filter_level),
-                                       120, 3);
-
-    } else if (M5Cardputer.BtnA.wasClicked()) {
-        if (M5Cardputer.Speaker.isEnabled()) {
-            M5Cardputer.Display.clear();
-            while (M5Cardputer.Mic.isRecording()) {
-                delay(1);
-            }
-            /// Since the microphone and speaker cannot be used at the same
-            /// time, turn off the microphone here.
-            M5Cardputer.Mic.end();
-            M5Cardputer.Speaker.begin();
-
-            M5Cardputer.Display.fillTriangle(70 - 8, 15 - 8, 70 - 8, 15 + 8,
-                                             70 + 8, 15, 0x1c9f);
-            M5Cardputer.Display.drawString("PLAY", 120, 3);
-            int start_pos = rec_record_idx * record_length;
-            if (start_pos < record_size) {
-                M5Cardputer.Speaker.playRaw(&rec_data[start_pos],
-                                            record_size - start_pos,
-                                            record_samplerate, false, 1, 0);
-            }
-            if (start_pos > 0) {
-                M5Cardputer.Speaker.playRaw(rec_data, start_pos,
-                                            record_samplerate, false, 1, 0);
-            }
-            do {
-                delay(1);
-                M5Cardputer.update();
-            } while (M5Cardputer.Speaker.isPlaying());
-
-            /// Since the microphone and speaker cannot be used at the same
-            /// time, turn off the speaker here.
-            M5Cardputer.Speaker.end();
-            M5Cardputer.Mic.begin();
-
-            M5Cardputer.Display.clear();
-            M5Cardputer.Display.fillCircle(70, 15, 8, RED);
-            M5Cardputer.Display.drawString("REC", 120, 3);
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic_wav_record/mic_wav_record.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic_wav_record/mic_wav_record.ino
deleted file mode 100644
index 452dafc..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic_wav_record/mic_wav_record.ino
+++ /dev/null
@@ -1,398 +0,0 @@
-
-/*
- * SPDX-FileCopyrightText: 2024 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.0.7
- * @Dependent Library:
- * M5GFX@^0.2.3: https://github.com/m5stack/M5GFX
- * M5Cardputer@^1.0.3: https://github.com/m5stack/M5Cardputer
- */
-
-#include <M5Cardputer.h>
-#include <SPI.h>
-#include <SD.h>
-
-#define SD_SPI_SCK_PIN  (40)
-#define SD_SPI_MISO_PIN (39)
-#define SD_SPI_MOSI_PIN (14)
-#define SD_SPI_CS_PIN   (12)
-
-static constexpr const size_t record_number     = 512;
-static constexpr const size_t record_length     = 240;
-static constexpr const size_t record_size       = record_number * record_length;
-static constexpr const size_t record_samplerate = 16000;
-
-static int16_t prev_y[record_length];
-static int16_t prev_h[record_length];
-static size_t rec_record_idx  = 2;
-static size_t draw_record_idx = 0;
-static int16_t* rec_data;
-
-static uint32_t file_counter     = 0;
-static uint8_t selectedFileIndex = 0;
-static std::vector<String> wavFiles;
-
-// WAV文件头部定义
-struct WAVHeader {
-    char riff[4]           = {'R', 'I', 'F', 'F'};
-    uint32_t fileSize      = 0;
-    char wave[4]           = {'W', 'A', 'V', 'E'};
-    char fmt[4]            = {'f', 'm', 't', ' '};
-    uint32_t fmtSize       = 16;
-    uint16_t audioFormat   = 1;
-    uint16_t numChannels   = 1;
-    uint32_t sampleRate    = record_samplerate;
-    uint32_t byteRate      = record_samplerate * sizeof(int16_t);
-    uint16_t blockAlign    = sizeof(int16_t);
-    uint16_t bitsPerSample = 16;
-    char data[4]           = {'d', 'a', 't', 'a'};
-    uint32_t dataSize      = 0;
-};
-
-bool saveWAVToSD(int16_t* data, size_t dataSize);  // Save the WAV file to the SD card.
-void scanAndDisplayWAVFiles(void);                 // Scan and display the WAV files on the SD card on the screen.
-bool playWAVFileFromSD(void);                      // Play the WAV files on the SD card.
-bool playSelectedWAVFile(const String& fileName);  // Play the selected WAV file.
-void playWAV(void);                                // Play the WAV file.
-void updateDisplay(std::vector<String> wavFiles, uint8_t selectedFileIndex);  // Update the displayed information.
-void setup(void)
-{
-    auto cfg = M5.config();
-
-    M5Cardputer.begin(cfg);
-    Serial.begin(115200);
-    M5Cardputer.Display.startWrite();
-    M5Cardputer.Display.setRotation(1);
-    M5Cardputer.Display.setTextDatum(top_center);
-    M5Cardputer.Display.setTextColor(WHITE);
-    M5Cardputer.Display.setFont(&fonts::FreeSansBoldOblique12pt7b);
-
-    // SD Card Initialization
-    SPI.begin(SD_SPI_SCK_PIN, SD_SPI_MISO_PIN, SD_SPI_MOSI_PIN, SD_SPI_CS_PIN);
-
-    if (!SD.begin(SD_SPI_CS_PIN, SPI, 25000000)) {
-        printf("Card failed, or not present\r\n");
-        while (1);
-    }
-    uint8_t cardType = SD.cardType();
-    if (cardType == CARD_NONE) {
-        printf("No SD card attached\r\n");
-        return;
-    }
-    printf("SD Card Type: ");
-    if (cardType == CARD_MMC) {
-        printf("MMC\r\n");
-    } else if (cardType == CARD_SD) {
-        printf("SDSC\r\n");
-    } else if (cardType == CARD_SDHC) {
-        printf("SDHC\r\n");
-    } else {
-        printf("UNKNOWN\r\n");
-    }
-    uint64_t cardSize = SD.cardSize() / (1024 * 1024);
-    printf("SD Card Size: %lluMB\r\n", cardSize);
-
-    rec_data = (typeof(rec_data))heap_caps_malloc(record_size * sizeof(int16_t), MALLOC_CAP_8BIT);
-    memset(rec_data, 0, record_size * sizeof(int16_t));
-    M5Cardputer.Speaker.setVolume(255);
-    M5Cardputer.Speaker.end();
-    M5Cardputer.Mic.begin();
-
-    scanAndDisplayWAVFiles();
-    updateDisplay(wavFiles, selectedFileIndex);
-}
-
-void loop(void)
-{
-    M5Cardputer.update();
-
-    // Press BtnA to start recording. After recording ends, the file will be saved to the SD card. If a file with the
-    // same name already exists on the SD card, the new file will overwrite the existing one.
-    if (M5Cardputer.BtnA.wasClicked()) {
-        M5Cardputer.Display.clear();
-        // Record
-        if (M5Cardputer.Mic.isEnabled()) {
-            M5Cardputer.Display.fillCircle(70, 15, 8, RED);
-            M5Cardputer.Display.drawString("REC", 120, 3);
-            static constexpr int shift = 6;
-            for (uint16_t i = 0; i < record_number; i++) {
-                auto data = &rec_data[i * record_length];
-                if (M5Cardputer.Mic.record(data, record_length, record_samplerate)) {
-                    if (i >= 2) {
-                        data      = &rec_data[(i - 2) * record_length];
-                        int32_t w = M5Cardputer.Display.width();
-                        if (w > record_length - 1) {
-                            w = record_length - 1;
-                        }
-                        for (int32_t x = 0; x < w; ++x) {
-                            M5Cardputer.Display.writeFastVLine(x, prev_y[x], prev_h[x], TFT_BLACK);
-                            int32_t y1 = (data[x] >> shift);
-                            int32_t y2 = (data[x + 1] >> shift);
-                            if (y1 > y2) {
-                                int32_t tmp = y1;
-                                y1          = y2;
-                                y2          = tmp;
-                            }
-                            int32_t y = ((M5Cardputer.Display.height()) >> 1) + y1;
-                            int32_t h = ((M5Cardputer.Display.height()) >> 1) + y2 + 1 - y;
-                            prev_y[x] = y;
-                            prev_h[x] = h;
-                            M5Cardputer.Display.writeFastVLine(x, prev_y[x], prev_h[x], WHITE);
-                        }
-                    }
-                }
-                M5Cardputer.Display.display();
-                M5Cardputer.Display.fillCircle(70, 15, 8, RED);
-                M5Cardputer.Display.drawString("REC", 120, 3);
-            }
-
-            // Save the audio recorded by the microphone in WAV format to the SD card.
-            if (saveWAVToSD(rec_data, record_size)) {
-                printf("WAV file saved successfully.\n");
-            } else {
-                printf("Failed to save WAV file.\n");
-            }
-            M5Cardputer.Display.clear();
-        }
-        updateDisplay(wavFiles, selectedFileIndex);
-    }
-    scanAndDisplayWAVFiles();
-}
-void updateDisplay(std::vector<String> wavFiles, uint8_t selectedFileIndex)
-{
-    if (wavFiles.empty()) {
-        printf("No WAV files found on SD card.\n");
-        M5Cardputer.Display.fillScreen(BLACK);
-        M5Cardputer.Display.setTextColor(RED);
-        int xPos = (M5Cardputer.Display.width()) / 2;
-        int yPos = M5Cardputer.Display.height() / 2 - 20;
-        M5Cardputer.Display.drawString("No WAV files found", xPos, yPos);
-        return;
-    }
-    const uint8_t maxVisibleFiles = 5;
-    uint8_t startIndex            = 0;
-
-    // Ensure the selected file is within the visible area.
-    if (selectedFileIndex >= maxVisibleFiles) {
-        startIndex = selectedFileIndex - (maxVisibleFiles - 1);
-    }
-
-    M5Cardputer.Display.fillScreen(BLACK);  // 清屏
-
-    // Display the list of WAV files, centered. The selected file's font will be yellow, and the unselected files' font
-    // will be white.
-    for (size_t i = startIndex; i < startIndex + maxVisibleFiles && i < wavFiles.size(); i++) {
-        uint16_t color = (i == selectedFileIndex) ? YELLOW : WHITE;
-        M5Cardputer.Display.setTextColor(color);
-        M5Cardputer.Display.drawString(wavFiles[i], M5Cardputer.Display.width() / 2, 3 + (i - startIndex) * 25);
-    }
-}
-void scanAndDisplayWAVFiles()
-{
-    static std::vector<String> previousWavFiles;
-
-    // Scan the WAV files on the SD card and store them in wavFiles.
-    File dir = SD.open("/");
-    if (!dir) {
-        printf("Failed to open directory.\n");
-        return;
-    }
-    wavFiles.clear();
-    while (File entry = dir.openNextFile()) {
-        if (!entry.isDirectory() && String(entry.name()).endsWith(".wav")) {
-            wavFiles.push_back(String(entry.name()));  // Only add .wav files to the list.
-        }
-        entry.close();
-    }
-    dir.close();
-
-    // If wavFiles changes, clear the interface and update the display.
-    if (wavFiles != previousWavFiles) {
-        previousWavFiles = wavFiles;  // Update the previous file list.
-        updateDisplay(wavFiles, selectedFileIndex);
-    }
-
-    // Check if the Cardputer keyboard is pressed.
-    if (M5Cardputer.Keyboard.isChange()) {
-        if (M5Cardputer.Keyboard.isPressed()) {
-            Keyboard_Class::KeysState status = M5Cardputer.Keyboard.keysState();
-            char data;
-            for (auto i : status.word) {
-                data += i;
-            }
-            // Use the up and down keys to select a file.
-            if (data == ';') {
-                selectedFileIndex = (selectedFileIndex == 0) ? wavFiles.size() - 1 : selectedFileIndex - 1;
-                updateDisplay(wavFiles, selectedFileIndex);
-            }
-            if (data == '.') {
-                selectedFileIndex = (selectedFileIndex + 1) % wavFiles.size();
-                updateDisplay(wavFiles, selectedFileIndex);
-            }
-
-            // Delete the selected file.
-            if (status.del) {
-                String filePath = "/" + wavFiles[selectedFileIndex];
-                if (SD.remove(filePath.c_str())) {
-                    printf("Deleted file: %s\n", filePath.c_str());
-                    wavFiles.erase(wavFiles.begin() + selectedFileIndex);
-                    if (selectedFileIndex >= wavFiles.size() && !wavFiles.empty()) {
-                        selectedFileIndex--;
-                    }
-                } else {
-                    printf("Failed to delete file: %s\n", filePath.c_str());
-                }
-            }
-
-            // Press the confirm key to play the selected file.
-            if (status.enter) {
-                playSelectedWAVFile(wavFiles[selectedFileIndex]);
-            }
-        }
-    }
-}
-
-bool playSelectedWAVFile(const String& fileName)
-{
-    String filePath = "/" + fileName;
-    printf("Playing WAV file: %s\n", filePath.c_str());
-
-    File file = SD.open(filePath.c_str());
-    if (!file) {
-        printf("Failed to open WAV file: %s\n", filePath.c_str());
-        return false;
-    }
-
-    // Skip the header of the WAV file (usually 44 bytes).
-    file.seek(44);
-
-    size_t bytesRead = file.read((uint8_t*)rec_data, record_size * sizeof(int16_t));
-    file.close();
-
-    if (bytesRead == 0) {
-        printf("Failed to read WAV file data.\n");
-        return false;
-    }
-    playWAV();
-    printf("Playback finished.\n");
-    return true;
-}
-
-bool playWAVFileFromSD(void)
-{
-    File dir       = SD.open("/");
-    String wavFile = "";
-
-    // Search for the first WAV file
-    while (File entry = dir.openNextFile()) {
-        if (!entry.isDirectory() && String(entry.name()).endsWith(".wav")) {
-            wavFile = "/" + String(entry.name());
-            entry.close();
-            break;
-        }
-        entry.close();
-    }
-    dir.close();
-
-    if (wavFile == "") {
-        printf("No WAV files found on SD card.\n");
-        return false;
-    }
-
-    printf("Playing WAV file: %s\n", wavFile.c_str());
-    File file = SD.open(wavFile.c_str());
-    if (!file) {
-        printf("Failed to open WAV file: %s\n", wavFile.c_str());
-        return false;
-    }
-
-    // Skip WAV header (typically 44 bytes)
-    file.seek(44);
-
-    size_t bytesRead = file.read((uint8_t*)rec_data, record_size);
-    file.close();
-
-    if (bytesRead == 0) {
-        printf("Failed to read WAV file data.\n");
-        return false;
-    }
-
-    playWAV();
-    printf("Playback finished.\n");
-    return true;
-}
-
-void playWAV(void)
-{
-    M5Cardputer.Display.clear();
-    M5Cardputer.Mic.end();
-    M5Cardputer.Speaker.begin();
-    M5Cardputer.Display.fillTriangle(70 - 8, 15 - 8, 70 - 8, 15 + 8, 70 + 8, 15, 0x1c9f);
-    M5Cardputer.Display.drawString("PLAY", 120, 3);
-    static constexpr int shift = 6;
-    for (uint16_t i = 0; i < record_number; i++) {
-        auto data = &rec_data[i * record_length];
-        M5Cardputer.Speaker.playRaw(&rec_data[i * record_length], record_length, record_samplerate);
-        do {
-            delay(1);
-            M5Cardputer.update();
-        } while (M5Cardputer.Speaker.isPlaying());
-        if (i >= 2) {
-            data      = &rec_data[(i - 2) * record_length];
-            int32_t w = M5Cardputer.Display.width();
-            if (w > record_length - 1) {
-                w = record_length - 1;
-            }
-            for (int32_t x = 0; x < w; ++x) {
-                M5Cardputer.Display.writeFastVLine(x, prev_y[x], prev_h[x], TFT_BLACK);
-                int32_t y1 = (data[x] >> shift);
-                int32_t y2 = (data[x + 1] >> shift);
-                if (y1 > y2) {
-                    int32_t tmp = y1;
-                    y1          = y2;
-                    y2          = tmp;
-                }
-                int32_t y = ((M5Cardputer.Display.height()) >> 1) + y1;
-                int32_t h = ((M5Cardputer.Display.height()) >> 1) + y2 + 1 - y;
-                prev_y[x] = y;
-                prev_h[x] = h;
-                M5Cardputer.Display.writeFastVLine(x, prev_y[x], prev_h[x], WHITE);
-            }
-        }
-        M5Cardputer.Display.fillTriangle(70 - 8, 15 - 8, 70 - 8, 15 + 8, 70 + 8, 15, 0x1c9f);
-        M5Cardputer.Display.drawString("PLAY", 120, 3);
-    }
-
-    M5Cardputer.Speaker.end();
-    M5Cardputer.Mic.begin();
-    M5Cardputer.Display.clear();
-    updateDisplay(wavFiles, selectedFileIndex);
-}
-
-bool saveWAVToSD(int16_t* data, size_t dataSize)
-{
-    // Generate a unique file name based on a counter. The counter defaults to 1 upon device reboot.
-    char filename[32];
-    snprintf(filename, sizeof(filename), "/recorded%lu.wav", file_counter++);  // Include the counter in the file name.
-    File file = SD.open(filename, FILE_WRITE);
-    if (!file) {
-        printf("Failed to open file for writing.\n");
-        return false;
-    }
-
-    WAVHeader header;
-    header.fileSize = 36 + dataSize * sizeof(int16_t);
-    header.dataSize = dataSize * sizeof(int16_t);
-
-    // Write the WAV header.
-    file.write((uint8_t*)&header, sizeof(WAVHeader));
-
-    // Write the audio data.
-    file.write((uint8_t*)data, dataSize * sizeof(int16_t));
-    file.close();
-
-    return true;
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/sdcard/sdcard.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/sdcard/sdcard.ino
deleted file mode 100644
index eed3b45..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/sdcard/sdcard.ino
+++ /dev/null
@@ -1,273 +0,0 @@
-/**
- * @file sdcard.ino
- * @author SeanKwok (shaoxiang@m5stack.com)
- * @brief M5Cardputer MicroSD Card Test
- * @version 0.1
- * @date 2024-01-19
- *
- *
- * @Hardwares: M5Cardputer
- * @Platform Version: Arduino M5Stack Board Manager v2.1.0
- * @Dependent Library:
- * M5GFX: https://github.com/m5stack/M5GFX
- * M5Unified: https://github.com/m5stack/M5Unified
- * M5Cardputer: https://github.com/m5stack/M5Cardputer
- */
-
-#include <M5Cardputer.h>
-#include <SPI.h>
-#include <SD.h>
-
-#define SD_SPI_SCK_PIN  40
-#define SD_SPI_MISO_PIN 39
-#define SD_SPI_MOSI_PIN 14
-#define SD_SPI_CS_PIN   12
-
-void listDir(fs::FS &fs, const char *dirname, uint8_t levels);
-void createDir(fs::FS &fs, const char *path);
-void removeDir(fs::FS &fs, const char *path);
-void readFile(fs::FS &fs, const char *path);
-void writeFile(fs::FS &fs, const char *path, const char *message);
-void appendFile(fs::FS &fs, const char *path, const char *message);
-void renameFile(fs::FS &fs, const char *path1, const char *path2);
-void deleteFile(fs::FS &fs, const char *path);
-void testFileIO(fs::FS &fs, const char *path);
-
-M5Canvas canvas(&M5Cardputer.Display);
-
-void printf_log(const char *format, ...);
-void println_log(const char *str);
-
-void setup() {
-    M5Cardputer.begin();
-    M5Cardputer.Display.setRotation(1);
-    canvas.setColorDepth(1);  // mono color
-    canvas.createSprite(M5Cardputer.Display.width(),
-                        M5Cardputer.Display.height());
-    canvas.setPaletteColor(1, GREEN);
-    canvas.setTextSize((float)canvas.width() / 160);
-    canvas.setTextScroll(true);
-
-    // SD Card Initialization
-    SPI.begin(SD_SPI_SCK_PIN, SD_SPI_MISO_PIN, SD_SPI_MOSI_PIN, SD_SPI_CS_PIN);
-
-    if (!SD.begin(SD_SPI_CS_PIN, SPI, 25000000)) {
-        // Print a message if the SD card initialization
-        // fails orif the SD card does not exist.
-        // 如果SD卡初始化失败或者SD卡不存在，则打印消息.
-        println_log("Card failed, or not present");
-        while (1)
-            ;
-    }
-
-    uint8_t cardType = SD.cardType();
-
-    if (cardType == CARD_NONE) {
-        println_log("No SD card attached");
-        return;
-    }
-
-    Serial.print("SD Card Type: ");
-    if (cardType == CARD_MMC) {
-        println_log("MMC");
-    } else if (cardType == CARD_SD) {
-        println_log("SDSC");
-    } else if (cardType == CARD_SDHC) {
-        println_log("SDHC");
-    } else {
-        println_log("UNKNOWN");
-    }
-
-    uint64_t cardSize = SD.cardSize() / (1024 * 1024);
-    printf_log("SD Card Size: %lluMB\n", cardSize);
-
-    listDir(SD, "/", 0);
-    createDir(SD, "/mydir");
-    listDir(SD, "/", 0);
-    removeDir(SD, "/mydir");
-    listDir(SD, "/", 2);
-    writeFile(SD, "/hello.txt", "Hello ");
-    appendFile(SD, "/hello.txt", "World!\n");
-    readFile(SD, "/hello.txt");
-    deleteFile(SD, "/foo.txt");
-    renameFile(SD, "/hello.txt", "/foo.txt");
-    readFile(SD, "/foo.txt");
-    testFileIO(SD, "/test.txt");
-    printf_log("Total space: %lluMB\n", SD.totalBytes() / (1024 * 1024));
-    printf_log("Used space: %lluMB\n", SD.usedBytes() / (1024 * 1024));
-}
-void loop() {
-}
-
-void listDir(fs::FS &fs, const char *dirname, uint8_t levels) {
-    printf_log("Listing directory: %s\n", dirname);
-
-    File root = fs.open(dirname);
-    if (!root) {
-        println_log("Failed to open directory");
-        return;
-    }
-    if (!root.isDirectory()) {
-        println_log("Not a directory");
-        return;
-    }
-
-    File file = root.openNextFile();
-    while (file) {
-        if (file.isDirectory()) {
-            Serial.print("  DIR : ");
-            println_log(file.name());
-            if (levels) {
-                listDir(fs, file.path(), levels - 1);
-            }
-        } else {
-            Serial.print("  FILE: ");
-            Serial.print(file.name());
-            Serial.print("  SIZE: ");
-            println_log(String(file.size()).c_str());
-        }
-        file = root.openNextFile();
-    }
-}
-
-void createDir(fs::FS &fs, const char *path) {
-    printf_log("Creating Dir: %s\n", path);
-    if (fs.mkdir(path)) {
-        println_log("Dir created");
-    } else {
-        println_log("mkdir failed");
-    }
-}
-
-void removeDir(fs::FS &fs, const char *path) {
-    printf_log("Removing Dir: %s\n", path);
-    if (fs.rmdir(path)) {
-        println_log("Dir removed");
-    } else {
-        println_log("rmdir failed");
-    }
-}
-
-void readFile(fs::FS &fs, const char *path) {
-    printf_log("Reading file: %s\n", path);
-
-    File file = fs.open(path);
-    if (!file) {
-        println_log("Failed to open file for reading");
-        return;
-    }
-
-    Serial.print("Read from file: ");
-    while (file.available()) {
-        Serial.write(file.read());
-    }
-    file.close();
-}
-
-void writeFile(fs::FS &fs, const char *path, const char *message) {
-    printf_log("Writing file: %s\n", path);
-
-    File file = fs.open(path, FILE_WRITE);
-    if (!file) {
-        println_log("Failed to open file for writing");
-        return;
-    }
-    if (file.print(message)) {
-        println_log("File written");
-    } else {
-        println_log("Write failed");
-    }
-    file.close();
-}
-
-void appendFile(fs::FS &fs, const char *path, const char *message) {
-    printf_log("Appending to file: %s\n", path);
-
-    File file = fs.open(path, FILE_APPEND);
-    if (!file) {
-        println_log("Failed to open file for appending");
-        return;
-    }
-    if (file.print(message)) {
-        println_log("Message appended");
-    } else {
-        println_log("Append failed");
-    }
-    file.close();
-}
-
-void renameFile(fs::FS &fs, const char *path1, const char *path2) {
-    printf_log("Renaming file %s to %s\n", path1, path2);
-    if (fs.rename(path1, path2)) {
-        println_log("File renamed");
-    } else {
-        println_log("Rename failed");
-    }
-}
-
-void deleteFile(fs::FS &fs, const char *path) {
-    printf_log("Deleting file: %s\n", path);
-    if (fs.remove(path)) {
-        println_log("File deleted");
-    } else {
-        println_log("Delete failed");
-    }
-}
-
-void testFileIO(fs::FS &fs, const char *path) {
-    File file = fs.open(path);
-    static uint8_t buf[512];
-    size_t len     = 0;
-    uint32_t start = millis();
-    uint32_t end   = start;
-    if (file) {
-        len         = file.size();
-        size_t flen = len;
-        start       = millis();
-        while (len) {
-            size_t toRead = len;
-            if (toRead > 512) {
-                toRead = 512;
-            }
-            file.read(buf, toRead);
-            len -= toRead;
-        }
-        end = millis() - start;
-        printf_log("%u bytes read for %lu ms\n", flen, end);
-        file.close();
-    } else {
-        println_log("Failed to open file for reading");
-    }
-
-    file = fs.open(path, FILE_WRITE);
-    if (!file) {
-        println_log("Failed to open file for writing");
-        return;
-    }
-
-    size_t i;
-    start = millis();
-    for (i = 0; i < 2048; i++) {
-        file.write(buf, 512);
-    }
-    end = millis() - start;
-    printf_log("%u bytes written for %lu ms\n", 2048 * 512, end);
-    file.close();
-}
-
-void printf_log(const char *format, ...) {
-    char buf[256];
-    va_list args;
-    va_start(args, format);
-    vsnprintf(buf, 256, format, args);
-    va_end(args);
-    Serial.print(buf);
-    canvas.printf(buf);
-    canvas.pushSprite(0, 0);
-}
-
-void println_log(const char *str) {
-    Serial.println(str);
-    canvas.println(str);
-    canvas.pushSprite(0, 0);
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/REPL.ino b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/REPL.ino
deleted file mode 100644
index 54f77ea..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/REPL.ino
+++ /dev/null
@@ -1,87 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#include "ReplView.h"
-#include <M5Cardputer.h>
-
-LGFX_Sprite *canvas;
-ReplView repl_view;
-long the_number    = 2333;
-bool is_player_win = false;
-
-bool string_to_number(const char *str, long *out)
-{
-    if (str == NULL || *str == '\0') {
-        return false;
-    }
-
-    char *end;
-    long value = strtol(str, &end, 10);
-
-    if (*end != '\0') {
-        return false;
-    }
-
-    if (value < -999 || value > 999) {
-        return false;
-    }
-
-    *out = value;
-    return true;
-}
-
-void handle_command(const std::string &command)
-{
-    /* If player win, show the message */
-    if (is_player_win) {
-        repl_view.showMessage(command, TFT_CYAN);
-        return;
-    }
-
-    /* Convert input to number */
-    long number = 0;
-    if (!string_to_number(command.c_str(), &number)) {
-        repl_view.showMessage("Invaild input :(", TFT_RED);
-        return;
-    }
-
-    /* Compare */
-    if (number == the_number) {
-        repl_view.showMessage("Correct! :)", TFT_GREENYELLOW);
-        is_player_win = true;
-    } else if (number > the_number) {
-        repl_view.showMessage("Too high!", TFT_CYAN);
-    } else {
-        repl_view.showMessage("Too low!", TFT_CYAN);
-    }
-}
-
-void setup()
-{
-    M5Cardputer.begin();
-
-    /* Create a full screen canvas for view */
-    canvas = new LGFX_Sprite(&M5Cardputer.Display);
-    canvas->createSprite(M5Cardputer.Display.width(), M5Cardputer.Display.height());
-
-    /* Init REPL view, setup callbacks */
-    repl_view.onCommand    = handle_command;
-    repl_view.onRenderTips = []() {
-        canvas->setTextColor(TFT_CYAN);
-        canvas->println("Guess the number");
-        canvas->println("The number is between\n-999 and 999 :D");
-    };
-    repl_view.init(canvas);
-
-    /* Get a random number */
-    the_number = random(-999, 999);
-}
-
-void loop()
-{
-    /* Keep updating */
-    M5Cardputer.update();
-    repl_view.update();
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/ReplView.cpp b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/ReplView.cpp
deleted file mode 100644
index 5ad7a6e..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/ReplView.cpp
+++ /dev/null
@@ -1,167 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#include "ReplView.h"
-
-void ReplView::init(LGFX_Sprite* canvas)
-{
-    _canvas = canvas;
-    render_interface();
-}
-
-void ReplView::update()
-{
-    update_keyboard_input();
-    update_cursor();
-}
-
-void ReplView::clearScreen()
-{
-    _canvas->fillScreen(TFT_BLACK);
-    _canvas->setCursor(0, 0);
-    _canvas->pushSprite(0, 0);
-}
-
-void ReplView::showMessage(const std::string& message, uint16_t color)
-{
-    _canvas->setTextColor(color, TFT_BLACK);
-    _canvas->println(message.c_str());
-    _canvas->setTextColor(TFT_WHITE, TFT_BLACK);
-    _canvas->pushSprite(0, 0);
-}
-
-void ReplView::showPrompt(const std::string& prompt_text)
-{
-    _prompt_text = prompt_text;
-    render_prompt();
-}
-
-void ReplView::setPromptText(const std::string& prompt)
-{
-    _prompt_text = prompt;
-}
-
-void ReplView::setInputBuffer(const std::string& text)
-{
-    _input_buffer = text;
-    render_prompt();
-}
-
-void ReplView::clearInputBuffer()
-{
-    _input_buffer.clear();
-    render_prompt();
-}
-
-void ReplView::render_interface()
-{
-    _canvas->fillScreen(TFT_BLACK);
-    _canvas->setFont(&fonts::efontCN_16);
-    _canvas->setTextScroll(true);
-    _canvas->setCursor(0, 0);
-    _canvas->setTextSize(1);
-    _canvas->setBaseColor(TFT_BLACK);
-    _canvas->setTextColor(TFT_WHITE, TFT_BLACK);
-
-    if (onRenderTips) {
-        onRenderTips();
-    }
-
-    render_prompt();
-}
-
-void ReplView::render_prompt()
-{
-    // 显示输入和光标
-    std::string display_text = _prompt_text + _input_buffer;
-    if (_cursor_state) {
-        display_text += "_";
-    } else {
-        display_text += " ";
-    }
-
-    // 获取当前光标位置
-    int cursor_y = _canvas->getCursorY();
-
-    // 清除当前行，确保光标被完全移除
-    _canvas->fillRect(0, cursor_y, _canvas->width(), 15, TFT_BLACK);
-
-    // 打印提示符和输入
-    _canvas->setCursor(0, cursor_y);
-    _canvas->setTextColor(TFT_WHITE, TFT_BLACK);
-    _canvas->print(display_text.c_str());
-
-    _canvas->pushSprite(0, 0);
-}
-
-void ReplView::handle_enter_key()
-{
-    // 清除当前输入行并重新绘制不带光标的版本
-    int cursor_y = _canvas->getCursorY();
-    _canvas->fillRect(0, cursor_y, _canvas->width(), 15, TFT_BLACK);
-    _canvas->setCursor(0, cursor_y);
-    _canvas->setTextColor(TFT_WHITE, TFT_BLACK);
-    _canvas->print(_prompt_text.c_str());
-    _canvas->print(_input_buffer.c_str());
-    _canvas->println();  // 移动到下一行
-
-    // 通过回调执行命令
-    if (onCommand && !_input_buffer.empty()) {
-        onCommand(_input_buffer);
-    }
-
-    // 重置输入缓冲区并显示新提示符
-    if (autoClearPrompt) {
-        _input_buffer.clear();
-    }
-    render_prompt();
-}
-
-void ReplView::handle_backspace()
-{
-    if (!_input_buffer.empty()) {
-        _input_buffer.pop_back();
-
-        // 清除更大区域确保旧光标被完全移除
-        int cursor_y = _canvas->getCursorY();
-        _canvas->fillRect(0, cursor_y, _canvas->width(), 15, TFT_BLACK);
-
-        // 重新绘制提示行
-        render_prompt();
-    }
-}
-
-void ReplView::update_cursor()
-{
-    if (millis() - _cursor_update_time > CURSOR_BLINK_PERIOD) {
-        _cursor_state       = !_cursor_state;
-        _cursor_update_time = millis();
-        render_prompt();
-    }
-}
-
-void ReplView::update_keyboard_input()
-{
-    if (M5Cardputer.Keyboard.isChange()) {
-        if (M5Cardputer.Keyboard.isPressed()) {
-            auto& status = M5Cardputer.Keyboard.keysState();
-
-            if (status.enter) {
-                handle_enter_key();
-                return;
-            }
-
-            if (status.del) {
-                handle_backspace();
-                return;
-            }
-
-            for (auto& c : status.word) {
-                _input_buffer += c;
-            }
-            render_prompt();
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/ReplView.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/ReplView.h
deleted file mode 100644
index e54f950..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL/ReplView.h
+++ /dev/null
@@ -1,51 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#pragma once
-#include <M5Cardputer.h>
-#include <functional>
-#include <string>
-
-/**
- * @brief
- *
- */
-class ReplView {
-public:
-    std::function<void()> onRenderTips;
-    std::function<void(const std::string& command)> onCommand;
-    bool autoClearPrompt = true;
-
-    void init(LGFX_Sprite* canvas);
-    void update();
-    void clearScreen();
-    void showMessage(const std::string& message, uint16_t color = TFT_WHITE);
-    void showPrompt(const std::string& prompt_text = ">>> ");
-    void setPromptText(const std::string& prompt);
-
-    void setInputBuffer(const std::string& text);
-    const std::string& getInputBuffer() const
-    {
-        return _input_buffer;
-    }
-    void clearInputBuffer();
-
-protected:
-    static constexpr uint32_t CURSOR_BLINK_PERIOD = 500;
-
-    LGFX_Sprite* _canvas         = nullptr;
-    uint32_t _cursor_update_time = 0;
-    bool _cursor_state           = false;
-    std::string _input_buffer;
-    std::string _prompt_text = ">>> ";
-    int _key_event_slot_id   = -1;
-
-    void render_interface();
-    void render_prompt();
-    void handle_enter_key();
-    void handle_backspace();
-    void update_cursor();
-    void update_keyboard_input();
-};
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/library.json b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/library.json
deleted file mode 100644
index 90b65bd..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/library.json
+++ /dev/null
@@ -1,27 +0,0 @@
-{
-  "name": "M5Cardputer",
-  "description": "Library for M5Stack M5Cardputer and M5Cardputer-ADV Board",
-  "keywords": "M5GFX,M5Stack,M5Cardputer,M5Cardputer-ADV",
-  "authors": {
-    "name": "M5Stack, Sean",
-    "url": "http://www.m5stack.com"
-  },
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/m5stack/M5Cardputer.git"
-  },
-  "version": "1.1.1",
-  "frameworks": [
-    "arduino"
-  ],
-  "platforms": [
-    "espressif32",
-    "native"
-  ],
-  "headers": "M5Cardputer.h",
-  "dependencies": {
-    "M5Unified": "*",
-    "M5GFX": "*",
-    "arduino-irremote/IRremote": "*"
-  }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/library.properties b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/library.properties
deleted file mode 100644
index 4b971d5..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/library.properties
+++ /dev/null
@@ -1,11 +0,0 @@
-name=M5Cardputer
-version=1.1.1
-author=M5Stack
-maintainer=M5Stack
-sentence=Library for M5Stack M5Cardputer and M5Cardputer-ADV Board
-paragraph=M5Stack, M5Cardputer, M5Cardputer-ADV, See more on http://M5Stack.com
-category=Display
-url=https://github.com/m5stack/M5Cardputer.git
-architectures=esp32
-includes=M5Cardputer.h
-depends=M5Unified,M5GFX,IRremote,LibSSH-ESP32
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/M5Cardputer.cpp b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/M5Cardputer.cpp
deleted file mode 100644
index 63d3f0f..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/M5Cardputer.cpp
+++ /dev/null
@@ -1,37 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#include "M5Cardputer.h"
-
-using namespace m5;
-
-M5_CARDPUTER M5Cardputer;
-
-void M5_CARDPUTER::begin(bool enableKeyboard)
-{
-    M5.begin();
-    _enableKeyboard = enableKeyboard;
-    if (enableKeyboard) {
-        Keyboard.begin();
-    }
-}
-
-void M5_CARDPUTER::begin(m5::M5Unified::config_t cfg, bool enableKeyboard)
-{
-    M5.begin(cfg);
-    _enableKeyboard = enableKeyboard;
-    if (enableKeyboard) {
-        Keyboard.begin();
-    }
-}
-
-void M5_CARDPUTER::update(void)
-{
-    M5.update();
-    if (_enableKeyboard) {
-        Keyboard.updateKeyList();
-        Keyboard.updateKeysState();
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/M5Cardputer.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/M5Cardputer.h
deleted file mode 100644
index ddd9fe2..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/M5Cardputer.h
+++ /dev/null
@@ -1,45 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#ifndef M5CARDPUTER_H
-#define M5CARDPUTER_H
-
-#include "utility/Keyboard/Keyboard.h"
-#include <M5Unified.h>
-
-namespace m5 {
-
-class M5_CARDPUTER {
-public:
-    void begin(bool enableKeyboard = true);
-    void begin(m5::M5Unified::config_t cfg, bool enableKeyboard = true);
-
-    M5GFX &Display         = M5.Display;
-    M5GFX &Lcd             = Display;
-    Power_Class &Power     = M5.Power;
-    Speaker_Class &Speaker = M5.Speaker;
-    Mic_Class &Mic         = M5.Mic;
-    Button_Class &BtnA     = M5.getButton(0);
-
-    Keyboard_Class Keyboard = Keyboard_Class();
-
-    /// for internal I2C device
-    I2C_Class &In_I2C = m5::In_I2C;
-
-    /// for external I2C device (Port.A)
-    I2C_Class &Ex_I2C = m5::Ex_I2C;
-
-    void update(void);
-
-private:
-    /* data */
-    bool _enableKeyboard;
-};
-
-}  // namespace m5
-
-extern m5::M5_CARDPUTER M5Cardputer;
-
-#endif
\ No newline at end of file
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418.cpp b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418.cpp
deleted file mode 100644
index cc22ff9..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418.cpp
+++ /dev/null
@@ -1,399 +0,0 @@
-/**
- *  @file Adafruit_TCA8418.cpp
- *
- *  @mainpage I2C Driver for the Adafruit TCA8418 Keypad Matrix / GPIO Expander
- * Breakout
- *
- *  @section intro_sec Introduction
- *
- * 	I2C Driver for the Adafruit TCA8418 Keypad Matrix / GPIO Expander
- * Breakout
- *
- * 	This is a library for the Adafruit TCA8418 breakout:
- * 	https://www.adafruit.com/product/XXXX
- *
- * 	Adafruit invests time and resources providing this open source code,
- *  please support Adafruit and open-source hardware by purchasing products from
- * 	Adafruit!
- *
- *  @section dependencies Dependencies
- *  This library depends on the Adafruit BusIO library
- *
- *  @section author Author
- *
- *  Limor Fried (Adafruit Industries)
- *
- * 	@section license License
- *
- * 	BSD (see license.txt)
- *
- * 	@section  HISTORY
- *
- *     v1.0 - First release
- */
-
-// #include "Arduino.h"
-
-#include "Adafruit_TCA8418.h"
-
-/**
- *    @brief  Instantiates a new TCA8418 class
- */
-Adafruit_TCA8418::Adafruit_TCA8418(std::uint8_t i2c_addr, std::uint32_t freq, m5::I2C_Class* i2c)
-    : I2C_Device(i2c_addr, freq, i2c)
-{
-}
-
-/**
- *    @brief  destructor
- */
-Adafruit_TCA8418::~Adafruit_TCA8418(void)
-{
-}
-
-/**
- *    @brief  Sets up the hardware and initializes I2C
- *    @param  address  The I2C address for the expander
- *    @param  wire     The TwoWire object to be used for I2C connections.
- *    @return True if initialization was successful, otherwise false.
- */
-bool Adafruit_TCA8418::begin()
-{
-    // Check
-    bool ret = false;
-
-    //  GPIO
-    //  set default all GIO pins to INPUT
-    ret = writeRegister8(TCA8418_REG_GPIO_DIR_1, 0x00);
-    ret = writeRegister8(TCA8418_REG_GPIO_DIR_2, 0x00);
-    ret = writeRegister8(TCA8418_REG_GPIO_DIR_3, 0x00);
-
-    //  add all pins to key events
-    ret = writeRegister8(TCA8418_REG_GPI_EM_1, 0xFF);
-    ret = writeRegister8(TCA8418_REG_GPI_EM_2, 0xFF);
-    ret = writeRegister8(TCA8418_REG_GPI_EM_3, 0xFF);
-
-    //  set all pins to FALLING interrupts
-    ret = writeRegister8(TCA8418_REG_GPIO_INT_LVL_1, 0x00);
-    ret = writeRegister8(TCA8418_REG_GPIO_INT_LVL_2, 0x00);
-    ret = writeRegister8(TCA8418_REG_GPIO_INT_LVL_3, 0x00);
-
-    //  add all pins to interrupts
-    ret = writeRegister8(TCA8418_REG_GPIO_INT_EN_1, 0xFF);
-    ret = writeRegister8(TCA8418_REG_GPIO_INT_EN_2, 0xFF);
-    ret = writeRegister8(TCA8418_REG_GPIO_INT_EN_3, 0xFF);
-
-    return ret;
-}
-
-/**
- * @brief configures the size of the keypad matrix.
- *
- * @param [in] rows    number of rows, should be <= 8
- * @param [in] columns number of columns, should be <= 10
- * @return true is rows and columns have valid values.
- *
- * @details will always use the lowest pins for rows and columns.
- *          0..rows-1  and  0..columns-1
- */
-bool Adafruit_TCA8418::matrix(uint8_t rows, uint8_t columns)
-{
-    if ((rows > 8) || (columns > 10)) return false;
-
-    //  MATRIX
-    //  skip zero size matrix
-    if ((rows != 0) && (columns != 0)) {
-        // setup the keypad matrix.
-        uint8_t mask = 0x00;
-        for (int r = 0; r < rows; r++) {
-            mask <<= 1;
-            mask |= 1;
-        }
-        writeRegister8(TCA8418_REG_KP_GPIO_1, mask);
-
-        mask = 0x00;
-        for (int c = 0; c < columns && c < 8; c++) {
-            mask <<= 1;
-            mask |= 1;
-        }
-        writeRegister8(TCA8418_REG_KP_GPIO_2, mask);
-
-        if (columns > 8) {
-            if (columns == 9)
-                mask = 0x01;
-            else
-                mask = 0x03;
-            writeRegister8(TCA8418_REG_KP_GPIO_3, mask);
-        }
-    }
-
-    return true;
-}
-
-/////////////////////////////////////////////////////////////////////////////
-//
-//  KEY EVENTS
-//
-
-/**
- * @brief checks if key events are available in the internal buffer
- *
- * @return number of key events in the buffer
- */
-uint8_t Adafruit_TCA8418::available()
-{
-    uint8_t eventCount = readRegister8(TCA8418_REG_KEY_LCK_EC);
-    eventCount &= 0x0F;  //  lower 4 bits only
-    return eventCount;
-}
-
-/**
- * @brief gets first event from the internal buffer
- *
- * @return key event or 0 if none available
- *
- * @details
- *     key event 0x00        no event
- *               0x01..0x50  key  press
- *               0x81..0xD0  key  release
- *               0x5B..0x72  GPIO press
- *               0xDB..0xF2  GPIO release
- */
-uint8_t Adafruit_TCA8418::getEvent()
-{
-    uint8_t event = readRegister8(TCA8418_REG_KEY_EVENT_A);
-    return event;
-}
-
-/**
- * @brief flushes the internal buffer of key events
- *        and cleans the GPIO status registers.
- *
- * @return number of keys flushed.
- */
-uint8_t Adafruit_TCA8418::flush()
-{
-    //  flush key events
-    uint8_t count = 0;
-    while (getEvent() != 0) count++;
-    //  flush gpio events
-    readRegister8(TCA8418_REG_GPIO_INT_STAT_1);
-    readRegister8(TCA8418_REG_GPIO_INT_STAT_2);
-    readRegister8(TCA8418_REG_GPIO_INT_STAT_3);
-    //  clear INT_STAT register
-    writeRegister8(TCA8418_REG_INT_STAT, 3);
-    return count;
-}
-
-/////////////////////////////////////////////////////////////////////////////
-//
-//  GPIO
-//
-
-/**
- * @brief read GPIO
- *
- * @param [in] pinnum Pin name between TCA8418_ROW0 and TCA8418_COL9  0..17
- * @return 0 = LOW, 1 = HIGH, 0xFF = pinnum out of range
- */
-uint8_t Adafruit_TCA8418::digitalRead(uint8_t pinnum)
-{
-    if (pinnum > TCA8418_COL9) return 0xFF;
-
-    uint8_t reg  = TCA8418_REG_GPIO_DAT_STAT_1 + pinnum / 8;
-    uint8_t mask = (1 << (pinnum % 8));
-
-    // LEVEL  0 = LOW  other = HIGH
-    uint8_t value = readRegister8(reg);
-    if (value & mask) return TCA8418_HIGH;
-    return TCA8418_LOW;
-}
-
-/**
- * @brief set GPIO pin to LOW or HIGH
- *
- * @param [in] pinnum  Pin name between TCA8418_ROW0 and TCA8418_COL9  0..17
- * @param [in] level   0 = LOW, all other are HIGH
- * @return true if successful
- */
-bool Adafruit_TCA8418::digitalWrite(uint8_t pinnum, uint8_t level)
-{
-    if (pinnum > TCA8418_COL9) return false;
-
-    uint8_t reg  = TCA8418_REG_GPIO_DAT_OUT_1 + pinnum / 8;
-    uint8_t mask = (1 << (pinnum % 8));
-
-    // LEVEL  0 = LOW  other = HIGH
-    uint8_t value = readRegister8(reg);
-    if (level == TCA8418_LOW)
-        value &= ~mask;
-    else
-        value |= mask;
-    writeRegister8(reg, value);
-    return true;
-}
-
-/**
- * @brief set mode of GPIO pin to INPUT, INPUT_PULLUP or OUTPUT
- *
- * @param [in] pinnum Pin name between TCA8418_ROW0 and TCA8418_COL9  0..17
- * @param [in] mode   INPUT, INPUT_PULLUP or OUTPUT
- * @return  false if failed.
- */
-bool Adafruit_TCA8418::pinMode(uint8_t pinnum, uint8_t mode)
-{
-    if (pinnum > TCA8418_COL9) return false;
-    // if (mode > INPUT_PULLUP) return false; ?s
-
-    uint8_t idx  = pinnum / 8;
-    uint8_t reg  = TCA8418_REG_GPIO_DIR_1 + idx;
-    uint8_t mask = (1 << (pinnum % 8));
-
-    // MODE  0 = INPUT   1 = OUTPUT
-    uint8_t value = readRegister8(reg);
-    if (mode == TCA8418_OUTPUT)
-        value |= mask;
-    else
-        value &= ~mask;
-    writeRegister8(reg, value);
-
-    // PULLUP  0 = enabled   1 = disabled
-    reg   = TCA8418_REG_GPIO_PULL_1 + idx;
-    value = readRegister8(reg);
-    if (mode == TCA8418_INPUT_PULLUP)
-        value &= ~mask;
-    else
-        value |= mask;
-    writeRegister8(reg, value);
-
-    return true;
-}
-
-/**
- * @brief set IRQ mode of GPIO pin to FALLING RISING
- *
- * @param [in] pinnum  Pin name between TCA8418_ROW0 and TCA8418_COL9  0..17
- * @param [in] mode    IRQ mode   FALLING RISING
- * @return  false if failed.
- */
-bool Adafruit_TCA8418::pinIRQMode(uint8_t pinnum, uint8_t mode)
-{
-    if (pinnum > TCA8418_COL9) return false;
-    if ((mode != TCA8418_RISING) && (mode != TCA8418_FALLING)) return false;
-
-    //  MODE  0 = FALLING   1 = RISING
-    uint8_t idx  = pinnum / 8;
-    uint8_t reg  = TCA8418_REG_GPIO_INT_LVL_1 + idx;
-    uint8_t mask = (1 << (pinnum % 8));
-
-    uint8_t value = readRegister8(reg);
-    if (mode == TCA8418_RISING)
-        value |= mask;
-    else
-        value &= ~mask;
-    writeRegister8(reg, value);
-
-    // ENABLE INTERRUPT
-    reg   = TCA8418_REG_GPIO_INT_EN_1 + idx;
-    value = readRegister8(reg);
-    value |= mask;
-    writeRegister8(reg, value);
-
-    return true;
-}
-
-/////////////////////////////////////////////////////////////////////////////
-//
-//  CONFIGURATION
-//
-
-/**
- * @brief enables key event + GPIO interrupts.
- */
-void Adafruit_TCA8418::enableInterrupts()
-{
-    uint8_t value = readRegister8(TCA8418_REG_CFG);
-    value |= (TCA8418_REG_CFG_GPI_IEN | TCA8418_REG_CFG_KE_IEN);
-    writeRegister8(TCA8418_REG_CFG, value);
-};
-
-/**
- * @brief disables key events + GPIO interrupts.
- */
-void Adafruit_TCA8418::disableInterrupts()
-{
-    uint8_t value = readRegister8(TCA8418_REG_CFG);
-    value &= ~(TCA8418_REG_CFG_GPI_IEN | TCA8418_REG_CFG_KE_IEN);
-    writeRegister8(TCA8418_REG_CFG, value);
-};
-
-/**
- * @brief enables matrix overflow interrupt.
- */
-void Adafruit_TCA8418::enableMatrixOverflow()
-{
-    uint8_t value = readRegister8(TCA8418_REG_CFG);
-    value |= TCA8418_REG_CFG_OVR_FLOW_M;
-    writeRegister8(TCA8418_REG_CFG, value);
-};
-
-/**
- * @brief disables matrix overflow interrupt.
- */
-void Adafruit_TCA8418::disableMatrixOverflow()
-{
-    uint8_t value = readRegister8(TCA8418_REG_CFG);
-    value &= ~TCA8418_REG_CFG_OVR_FLOW_M;
-    writeRegister8(TCA8418_REG_CFG, value);
-};
-
-/**
- * @brief enables key debounce.
- */
-void Adafruit_TCA8418::enableDebounce()
-{
-    writeRegister8(TCA8418_REG_DEBOUNCE_DIS_1, 0x00);
-    writeRegister8(TCA8418_REG_DEBOUNCE_DIS_2, 0x00);
-    writeRegister8(TCA8418_REG_DEBOUNCE_DIS_3, 0x00);
-}
-
-/**
- * @brief disables key debounce.
- */
-void Adafruit_TCA8418::disableDebounce()
-{
-    writeRegister8(TCA8418_REG_DEBOUNCE_DIS_1, 0xFF);
-    writeRegister8(TCA8418_REG_DEBOUNCE_DIS_2, 0xFF);
-    writeRegister8(TCA8418_REG_DEBOUNCE_DIS_3, 0xFF);
-}
-
-/////////////////////////////////////////////////////////////////////////////
-//
-//  LOW LEVEL
-//
-
-// /**
-//  * @brief reads byte value from register
-//  *
-//  * @param [in] reg register address
-//  * @return value from register
-//  */
-// uint8_t Adafruit_TCA8418::readRegister(uint8_t reg)
-// {
-//     Adafruit_I2CRegister i2cReg = Adafruit_I2CRegister(i2c_dev, reg);
-//     uint8_t buffer[1] = {0};
-//     i2cReg.read(buffer, 1);
-//     return buffer[0];
-// }
-
-// /**
-//  * @brief write byte value to register
-//  *
-//  * @param [in] reg register address
-//  * @param [in] value
-//  */
-// void Adafruit_TCA8418::writeRegister(uint8_t reg, uint8_t value)
-// {
-//     Adafruit_I2CRegister i2cReg = Adafruit_I2CRegister(i2c_dev, reg);
-//     i2cReg.write(value);
-// }
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418.h
deleted file mode 100644
index 725ecb4..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418.h
+++ /dev/null
@@ -1,125 +0,0 @@
-/*!
- *  @file Adafruit_TCA8418.h
- *
- * 	I2C Driver for the Adafruit TCA8418 Keypad Matrix / GPIO Expander
- *Breakout
- *
- * 	This is a library for the Adafruit TCA8418 breakout:
- * 	https://www.adafruit.com/products/4918
- *
- * 	Adafruit invests time and resources providing this open source code,
- *  please support Adafruit and open-source hardware by purchasing products from
- * 	Adafruit!
- *
- *
- *	BSD license (see license.txt)
- */
-
-#ifndef _ADAFRUIT_TCA8418_H
-#define _ADAFRUIT_TCA8418_H
-
-// #include <Arduino.h>
-// #include <Adafruit_I2CDevice.h>
-// #include <Adafruit_I2CRegister.h>
-#include "Adafruit_TCA8418_registers.h"
-#include <M5Unified.hpp>
-#include <functional>
-
-#define TCA8418_DEFAULT_ADDR 0x34  ///< The default I2C address for our breakout
-
-/** Pin IDs for matrix rows/columns */
-enum {
-    TCA8418_ROW0,  // Pin ID for row 0
-    TCA8418_ROW1,  // Pin ID for row 1
-    TCA8418_ROW2,  // Pin ID for row 2
-    TCA8418_ROW3,  // Pin ID for row 3
-    TCA8418_ROW4,  // Pin ID for row 4
-    TCA8418_ROW5,  // Pin ID for row 5
-    TCA8418_ROW6,  // Pin ID for row 6
-    TCA8418_ROW7,  // Pin ID for row 7
-    TCA8418_COL0,  // Pin ID for column 0
-    TCA8418_COL1,  // Pin ID for column 1
-    TCA8418_COL2,  // Pin ID for column 2
-    TCA8418_COL3,  // Pin ID for column 3
-    TCA8418_COL4,  // Pin ID for column 4
-    TCA8418_COL5,  // Pin ID for column 5
-    TCA8418_COL6,  // Pin ID for column 6
-    TCA8418_COL7,  // Pin ID for column 7
-    TCA8418_COL8,  // Pin ID for column 8
-    TCA8418_COL9   // Pin ID for column 9
-};
-
-enum {
-    TCA8418_LOW  = 0,
-    TCA8418_HIGH = 1,
-};
-
-enum {
-    TCA8418_INPUT = 0,
-    TCA8418_OUTPUT,
-    TCA8418_INPUT_PULLUP,
-};
-
-enum {
-    TCA8418_RISING = 0,
-    TCA8418_FALLING,
-};
-
-/*!
- *    @brief  Class that stores state and functions for interacting with
- *            the TCA8418 I2C GPIO expander
- */
-class Adafruit_TCA8418 : public m5::I2C_Device {
-public:
-    Adafruit_TCA8418(std::uint8_t i2c_addr = TCA8418_DEFAULT_ADDR, std::uint32_t freq = 400000,
-                     m5::I2C_Class* i2c = &m5::In_I2C);
-
-    // Adafruit_TCA8418();
-    ~Adafruit_TCA8418();
-
-    //  initialize the TCA8418
-    bool begin();
-
-    //  KEY EVENTS
-    //  configure the size of the keypad.
-    //  all other rows and columns are set as inputs.
-    bool matrix(uint8_t rows, uint8_t columns);
-
-    //  key events available in the internal FIFO buffer
-    uint8_t available();
-
-    //  get one event from the FIFO buffer
-    //  bit 7 indicates  press = 0  or  release == 1 (mask 0x80)
-    uint8_t getEvent();
-
-    //  flush all events in the FIFO buffer + GPIO events
-    uint8_t flush();
-
-    //  GPIO
-    uint8_t digitalRead(uint8_t pinnum);
-    bool digitalWrite(uint8_t pinnum, uint8_t level);
-    bool pinMode(uint8_t pinnum, uint8_t mode);
-    bool pinIRQMode(uint8_t pinnum, uint8_t mode);  // MODE  FALLING or RISING
-
-    //  CONFIGURATION
-    //  enable / disable interrupts for matrix and GPI pins
-    void enableInterrupts();
-    void disableInterrupts();
-
-    //  ignore key events when FIFO buffer is full or not.
-    void enableMatrixOverflow();
-    void disableMatrixOverflow();
-
-    //  debounce keys.
-    void enableDebounce();
-    void disableDebounce();
-
-    // // for expert mode
-    // uint8_t readRegister(uint8_t reg);
-    // void writeRegister(uint8_t reg, uint8_t value);
-
-    // protected:
-    //     Adafruit_I2CDevice* i2c_dev = NULL; ///< Pointer to I2C bus interface
-};
-
-#endif
\ No newline at end of file
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418_registers.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418_registers.h
deleted file mode 100644
index b2e4f34..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Adafruit_TCA8418/Adafruit_TCA8418_registers.h
+++ /dev/null
@@ -1,94 +0,0 @@
-#pragma once
-/**
- *  @file Adafruit_TCA8418_registers.h
- *
- * 	I2C Driver for the Adafruit TCA8418 Keypad Matrix / GPIO Expander
- *Breakout
- *
- * 	This is a library for the Adafruit TCA8418 breakout:
- * 	https://www.adafruit.com/products/4918
- *
- * 	Adafruit invests time and resources providing this open source code,
- *  please support Adafruit and open-source hardware by purchasing products from
- * 	Adafruit!
- *
- *
- *	BSD license (see license.txt)
- */
-
-//  REGISTERS
-
-// #define TCA8418_REG_RESERVED          0x00
-#define TCA8418_REG_CFG             0x01  ///< Configuration register
-#define TCA8418_REG_INT_STAT        0x02  ///< Interrupt status
-#define TCA8418_REG_KEY_LCK_EC      0x03  ///< Key lock and event counter
-#define TCA8418_REG_KEY_EVENT_A     0x04  ///< Key event register A
-#define TCA8418_REG_KEY_EVENT_B     0x05  ///< Key event register B
-#define TCA8418_REG_KEY_EVENT_C     0x06  ///< Key event register C
-#define TCA8418_REG_KEY_EVENT_D     0x07  ///< Key event register D
-#define TCA8418_REG_KEY_EVENT_E     0x08  ///< Key event register E
-#define TCA8418_REG_KEY_EVENT_F     0x09  ///< Key event register F
-#define TCA8418_REG_KEY_EVENT_G     0x0A  ///< Key event register G
-#define TCA8418_REG_KEY_EVENT_H     0x0B  ///< Key event register H
-#define TCA8418_REG_KEY_EVENT_I     0x0C  ///< Key event register I
-#define TCA8418_REG_KEY_EVENT_J     0x0D  ///< Key event register J
-#define TCA8418_REG_KP_LCK_TIMER    0x0E  ///< Keypad lock1 to lock2 timer
-#define TCA8418_REG_UNLOCK_1        0x0F  ///< Unlock register 1
-#define TCA8418_REG_UNLOCK_2        0x10  ///< Unlock register 2
-#define TCA8418_REG_GPIO_INT_STAT_1 0x11  ///< GPIO interrupt status 1
-#define TCA8418_REG_GPIO_INT_STAT_2 0x12  ///< GPIO interrupt status 2
-#define TCA8418_REG_GPIO_INT_STAT_3 0x13  ///< GPIO interrupt status 3
-#define TCA8418_REG_GPIO_DAT_STAT_1 0x14  ///< GPIO data status 1
-#define TCA8418_REG_GPIO_DAT_STAT_2 0x15  ///< GPIO data status 2
-#define TCA8418_REG_GPIO_DAT_STAT_3 0x16  ///< GPIO data status 3
-#define TCA8418_REG_GPIO_DAT_OUT_1  0x17  ///< GPIO data out 1
-#define TCA8418_REG_GPIO_DAT_OUT_2  0x18  ///< GPIO data out 2
-#define TCA8418_REG_GPIO_DAT_OUT_3  0x19  ///< GPIO data out 3
-#define TCA8418_REG_GPIO_INT_EN_1   0x1A  ///< GPIO interrupt enable 1
-#define TCA8418_REG_GPIO_INT_EN_2   0x1B  ///< GPIO interrupt enable 2
-#define TCA8418_REG_GPIO_INT_EN_3   0x1C  ///< GPIO interrupt enable 3
-#define TCA8418_REG_KP_GPIO_1       0x1D  ///< Keypad/GPIO select 1
-#define TCA8418_REG_KP_GPIO_2       0x1E  ///< Keypad/GPIO select 2
-#define TCA8418_REG_KP_GPIO_3       0x1F  ///< Keypad/GPIO select 3
-#define TCA8418_REG_GPI_EM_1        0x20  ///< GPI event mode 1
-#define TCA8418_REG_GPI_EM_2        0x21  ///< GPI event mode 2
-#define TCA8418_REG_GPI_EM_3        0x22  ///< GPI event mode 3
-#define TCA8418_REG_GPIO_DIR_1      0x23  ///< GPIO data direction 1
-#define TCA8418_REG_GPIO_DIR_2      0x24  ///< GPIO data direction 2
-#define TCA8418_REG_GPIO_DIR_3      0x25  ///< GPIO data direction 3
-#define TCA8418_REG_GPIO_INT_LVL_1  0x26  ///< GPIO edge/level detect 1
-#define TCA8418_REG_GPIO_INT_LVL_2  0x27  ///< GPIO edge/level detect 2
-#define TCA8418_REG_GPIO_INT_LVL_3  0x28  ///< GPIO edge/level detect 3
-#define TCA8418_REG_DEBOUNCE_DIS_1  0x29  ///< Debounce disable 1
-#define TCA8418_REG_DEBOUNCE_DIS_2  0x2A  ///< Debounce disable 2
-#define TCA8418_REG_DEBOUNCE_DIS_3  0x2B  ///< Debounce disable 3
-#define TCA8418_REG_GPIO_PULL_1     0x2C  ///< GPIO pull-up disable 1
-#define TCA8418_REG_GPIO_PULL_2     0x2D  ///< GPIO pull-up disable 2
-#define TCA8418_REG_GPIO_PULL_3     0x2E  ///< GPIO pull-up disable 3
-// #define TCA8418_REG_RESERVED          0x2F
-
-//  FIELDS CONFIG REGISTER  1
-#define TCA8418_REG_CFG_AI           0x80  ///< Auto-increment for read/write
-#define TCA8418_REG_CFG_GPI_E_CGF    0x40  ///< Event mode config
-#define TCA8418_REG_CFG_OVR_FLOW_M   0x20  ///< Overflow mode enable
-#define TCA8418_REG_CFG_INT_CFG      0x10  ///< Interrupt config
-#define TCA8418_REG_CFG_OVR_FLOW_IEN 0x08  ///< Overflow interrupt enable
-#define TCA8418_REG_CFG_K_LCK_IEN    0x04  ///< Keypad lock interrupt enable
-#define TCA8418_REG_CFG_GPI_IEN      0x02  ///< GPI interrupt enable
-#define TCA8418_REG_CFG_KE_IEN       0x01  ///< Key events interrupt enable
-
-//  FIELDS INT_STAT REGISTER  2
-#define TCA8418_REG_STAT_CAD_INT      0x10  ///< Ctrl-alt-del seq status
-#define TCA8418_REG_STAT_OVR_FLOW_INT 0x08  ///< Overflow interrupt status
-#define TCA8418_REG_STAT_K_LCK_INT    0x04  ///< Key lock interrupt status
-#define TCA8418_REG_STAT_GPI_INT      0x02  ///< GPI interrupt status
-#define TCA8418_REG_STAT_K_INT        0x01  ///< Key events interrupt status
-
-//  FIELDS  KEY_LCK_EC REGISTER 3
-#define TCA8418_REG_LCK_EC_K_LCK_EN 0x40  ///< Key lock enable
-#define TCA8418_REG_LCK_EC_LCK_2    0x20  ///< Keypad lock status 2
-#define TCA8418_REG_LCK_EC_LCK_1    0x10  ///< Keypad lock status 1
-#define TCA8418_REG_LCK_EC_KLEC_3   0x08  ///< Key event count bit 3
-#define TCA8418_REG_LCK_EC_KLEC_2   0x04  ///< Key event count bit 2
-#define TCA8418_REG_LCK_EC_KLEC_1   0x02  ///< Key event count bit 1
-#define TCA8418_REG_LCK_EC_KLEC_0   0x01  ///< Key event count bit 0
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard.cpp b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard.cpp
deleted file mode 100644
index da602a5..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard.cpp
+++ /dev/null
@@ -1,289 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#include "Keyboard.h"
-#include "../common.h"
-#include "KeyboardReader/KeyboardReader.h"
-#include "KeyboardReader/IOMatrix.h"
-#include "KeyboardReader/TCA8418.h"
-#include <Arduino.h>
-#include <M5Unified.h>
-#include <memory>
-
-void Keyboard_Class::begin()
-{
-    auto board_type = M5.getBoard();
-    _keyboard_reader.reset();
-
-    // Reader injection based on board type
-    if (board_type == m5::board_t::board_M5Cardputer) {
-        _keyboard_reader = std::make_unique<IOMatrixKeyboardReader>();
-    } else if (board_type == m5::board_t::board_M5CardputerADV) {
-        _keyboard_reader = std::make_unique<TCA8418KeyboardReader>();
-    } else {
-        printf("[error] Keyboard: Unsupported board type: %d\n", (int)board_type);
-        _keyboard_reader = std::make_unique<KeyboardReader>();
-    }
-
-    _keyboard_reader->begin();
-}
-
-void Keyboard_Class::begin(std::unique_ptr<KeyboardReader> reader)
-{
-    _keyboard_reader = std::move(reader);
-    _keyboard_reader->begin();
-}
-
-uint8_t Keyboard_Class::getKey(Point2D_t keyCoor)
-{
-    uint8_t ret = 0;
-
-    if ((keyCoor.x < 0) || (keyCoor.y < 0)) {
-        return 0;
-    }
-    if (_keys_state_buffer.ctrl || _keys_state_buffer.shift || _is_caps_locked) {
-        ret = _key_value_map[keyCoor.y][keyCoor.x].value_second;
-    } else {
-        ret = _key_value_map[keyCoor.y][keyCoor.x].value_first;
-    }
-    return ret;
-}
-
-void Keyboard_Class::updateKeyList()
-{
-    if (_keyboard_reader) {
-        _keyboard_reader->update();
-    }
-}
-
-uint8_t Keyboard_Class::isPressed()
-{
-    return keyList().size();
-}
-
-bool Keyboard_Class::isChange()
-{
-    uint8_t current_size = keyList().size();
-    if (_last_key_size != current_size) {
-        _last_key_size = current_size;
-        return true;
-    } else {
-        return false;
-    }
-}
-
-bool Keyboard_Class::isKeyPressed(char c)
-{
-    const auto& keys = keyList();
-    if (keys.size()) {
-        for (const auto& i : keys) {
-            if (getKey(i) == c) return true;
-        }
-    }
-    return false;
-}
-
-#include <cstring>
-
-void Keyboard_Class::updateKeysState()
-{
-    // printf("-------------------\n");
-
-    _keys_state_buffer.reset();
-    _key_pos_print_keys.clear();
-    _key_pos_hid_keys.clear();
-    _key_pos_modifier_keys.clear();
-
-    const auto& keys       = keyList();
-    const size_t key_count = keys.size();
-
-    // Pre-allocate containers to avoid re-allocation
-    if (key_count > 0) {
-        _key_pos_print_keys.reserve(key_count);
-        _key_pos_hid_keys.reserve(key_count);
-        _key_pos_modifier_keys.reserve(8);
-        _keys_state_buffer.modifier_keys.reserve(8);
-        _keys_state_buffer.hid_keys.reserve(key_count);
-        _keys_state_buffer.word.reserve(key_count);
-    }
-
-    // =================================================================
-    // PASS 1: Identify all active modifier keys first.
-    // This ensures their state is known before processing other keys.
-    // =================================================================
-    for (const auto& key_pos : keys) {
-        const uint8_t key_code = getKeyValue(key_pos).value_first;
-        switch (key_code) {
-            case KEY_FN:
-                _keys_state_buffer.fn = true;
-                _key_pos_modifier_keys.push_back(key_pos);
-                _keys_state_buffer.modifier_keys.push_back(key_code);
-                break;
-            case KEY_OPT:
-                _keys_state_buffer.opt = true;
-                break;
-            case KEY_LEFT_CTRL:
-                _keys_state_buffer.ctrl = true;
-                _keys_state_buffer.modifiers |= (1 << (key_code - 0x80));
-                _key_pos_modifier_keys.push_back(key_pos);
-                _keys_state_buffer.modifier_keys.push_back(key_code);
-                break;
-            case KEY_LEFT_SHIFT:
-                _keys_state_buffer.shift = true;
-                _keys_state_buffer.modifiers |= (1 << (key_code - 0x80));
-                _key_pos_modifier_keys.push_back(key_pos);
-                _keys_state_buffer.modifier_keys.push_back(key_code);
-                break;
-            case KEY_LEFT_ALT:
-                _keys_state_buffer.alt = true;
-                _keys_state_buffer.modifiers |= (1 << (key_code - 0x80));
-                _key_pos_modifier_keys.push_back(key_pos);
-                _keys_state_buffer.modifier_keys.push_back(key_code);
-                break;
-                // Note: We only handle modifiers in this pass.
-        }
-    }
-
-    // =================================================================
-    // PASS 2: Process fn-layer keys.
-    // Now the modifier state is correct, regardless of key order.
-    // The fn-layer has precedence over special keys too
-    // =================================================================
-    if (_keys_state_buffer.fn) {
-        for (const auto& key_pos : keys) {
-            const KeyValue_t key_value = getKeyValue(key_pos);
-            const uint8_t key_code     = key_value.value_third;
-
-            // printf("%d\n", key_code);
-            if (key_code == KEY_NONE) {
-                continue;
-            }
-
-            // Skip modifier keys as they were handled in the first pass
-            switch (key_code) {
-                case KEY_ESCAPE:
-                    _keys_state_buffer.esc = true;
-                    break;
-                case KEY_DELETE:
-                    _keys_state_buffer.del = true;
-                    break;
-                case KEY_F1:
-                    _keys_state_buffer.f1 = true;
-                    break;
-                case KEY_F2:
-                    _keys_state_buffer.f2 = true;
-                    break;
-                case KEY_F3:
-                    _keys_state_buffer.f3 = true;
-                    break;
-                case KEY_F4:
-                    _keys_state_buffer.f4 = true;
-                    break;
-                case KEY_F5:
-                    _keys_state_buffer.f5 = true;
-                    break;
-                case KEY_F6:
-                    _keys_state_buffer.f6 = true;
-                    break;
-                case KEY_F7:
-                    _keys_state_buffer.f7 = true;
-                    break;
-                case KEY_F8:
-                    _keys_state_buffer.f8 = true;
-                    break;
-                case KEY_F9:
-                    _keys_state_buffer.f9 = true;
-                    break;
-                case KEY_F10:
-                    _keys_state_buffer.f10 = true;
-                    break;
-                case KEY_F11:
-                    _keys_state_buffer.f11 = true;
-                    break;
-                case KEY_F12:
-                    _keys_state_buffer.f12 = true;
-                    break;
-                case KEY_UP:
-                    _keys_state_buffer.up = true;
-                    break;
-                case KEY_LEFT:
-                    _keys_state_buffer.left = true;
-                    break;
-                case KEY_DOWN:
-                    _keys_state_buffer.down = true;
-                    break;
-                case KEY_RIGHT:
-                    _keys_state_buffer.right = true;
-                    break;
-            }
-            _key_pos_hid_keys.push_back(key_pos);
-            _keys_state_buffer.hid_keys.push_back(key_code);
-        }
-        return;
-    }
-
-    // =================================================================
-    // PASS 3: Process all non-modifier keys.
-    // Now the modifier state is correct, regardless of key order.
-    // =================================================================
-    for (const auto& key_pos : keys) {
-        const KeyValue_t key_value = getKeyValue(key_pos);
-        const uint8_t key_code     = key_value.value_first;
-
-        // printf("%d\n", key_code);
-
-        // Skip modifier keys as they were handled in the first pass
-        switch (key_code) {
-            case KEY_OPT:
-            case KEY_LEFT_CTRL:
-            case KEY_LEFT_SHIFT:
-            case KEY_LEFT_ALT:
-                continue;  // Already processed
-        }
-
-        // Handle other special keys
-        switch (key_code) {
-            case KEY_TAB:
-                _keys_state_buffer.tab = true;
-                _key_pos_hid_keys.push_back(key_pos);
-                _keys_state_buffer.hid_keys.push_back(key_code);
-                continue;  // Skip further processing for this key
-            case KEY_BACKSPACE:
-                _keys_state_buffer.backspace = true;
-                _key_pos_hid_keys.push_back(key_pos);
-                _keys_state_buffer.hid_keys.push_back(key_code);
-                continue;  // Skip further processing for this key
-            case KEY_ENTER:
-                _keys_state_buffer.enter = true;
-                _key_pos_hid_keys.push_back(key_pos);
-                _keys_state_buffer.hid_keys.push_back(key_code);
-                continue;  // Skip further processing for this key
-        }
-
-        // Handle printable keys (including space)
-        if (key_code == ' ') {
-            _keys_state_buffer.space = true;
-        }
-
-        _key_pos_hid_keys.push_back(key_pos);
-        _key_pos_print_keys.push_back(key_pos);
-
-        // Add HID key to the list
-        const uint8_t hid_key = _kb_asciimap[key_code];
-        if (hid_key) {
-            _keys_state_buffer.hid_keys.push_back(hid_key);
-        }
-
-        // Add character to the word buffer, now with the correct modifier state
-        // printf("%d %d %d\n", _keys_state_buffer.ctrl, _keys_state_buffer.shift, _is_caps_locked);
-        if (_keys_state_buffer.ctrl || _keys_state_buffer.shift || _is_caps_locked) {
-            // printf("push_back %c\n", key_value.value_second);
-            _keys_state_buffer.word.push_back(key_value.value_second);
-        } else {
-            // printf("push_back %c\n", key_value.value_first);
-            _keys_state_buffer.word.push_back(key_value.value_first);
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard.h
deleted file mode 100644
index 93b2761..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard.h
+++ /dev/null
@@ -1,198 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#pragma once
-#include "KeyboardReader/KeyboardReader.h"
-#include "Keyboard_def.h"
-#include <Arduino.h>
-#include <vector>
-#include <memory>
-
-struct KeyValue_t {
-    const char value_first;
-    const char value_second; // Aa layer
-    const char value_third;  // fn layer
-};
-
-const KeyValue_t _key_value_map[4][14] = {{{'`', '~', KEY_ESCAPE},
-                                           {'1', '!', KEY_F1},
-                                           {'2', '@', KEY_F2},
-                                           {'3', '#', KEY_F3},
-                                           {'4', '$', KEY_F4},
-                                           {'5', '%', KEY_F5},
-                                           {'6', '^', KEY_F6},
-                                           {'7', '&', KEY_F7},
-                                           {'8', '*', KEY_F8},
-                                           {'9', '(', KEY_F9},
-                                           {'0', ')', KEY_F10},
-                                           {'-', '_', KEY_F11},
-                                           {'=', '+', KEY_F12},
-                                           {KEY_BACKSPACE, KEY_BACKSPACE, KEY_DELETE}},
-                                          {{KEY_TAB, KEY_TAB, KEY_NONE},
-                                           {'q', 'Q', KEY_NONE},
-                                           {'w', 'W', KEY_NONE},
-                                           {'e', 'E', KEY_NONE},
-                                           {'r', 'R', KEY_NONE},
-                                           {'t', 'T', KEY_NONE},
-                                           {'y', 'Y', KEY_NONE},
-                                           {'u', 'U', KEY_NONE},
-                                           {'i', 'I', KEY_NONE},
-                                           {'o', 'O', KEY_NONE},
-                                           {'p', 'P', KEY_NONE},
-                                           {'[', '{', KEY_NONE},
-                                           {']', '}', KEY_NONE},
-                                           {'\\', '|', KEY_NONE}},
-                                          {{KEY_FN, KEY_FN, KEY_FN},
-                                           {KEY_LEFT_SHIFT, KEY_LEFT_SHIFT, KEY_NONE},
-                                           {'a', 'A', KEY_NONE},
-                                           {'s', 'S', KEY_NONE},
-                                           {'d', 'D', KEY_NONE},
-                                           {'f', 'F', KEY_NONE},
-                                           {'g', 'G', KEY_NONE},
-                                           {'h', 'H', KEY_NONE},
-                                           {'j', 'J', KEY_NONE},
-                                           {'k', 'K', KEY_NONE},
-                                           {'l', 'L', KEY_NONE},
-                                           {';', ':', KEY_UP},
-                                           {'\'', '\"', KEY_NONE},
-                                           {KEY_ENTER, KEY_ENTER, KEY_NONE}},
-                                          {{KEY_LEFT_CTRL, KEY_LEFT_CTRL, KEY_NONE},
-                                           {KEY_OPT, KEY_OPT, KEY_NONE},
-                                           {KEY_LEFT_ALT, KEY_LEFT_ALT, KEY_NONE},
-                                           {'z', 'Z', KEY_NONE},
-                                           {'x', 'X', KEY_NONE},
-                                           {'c', 'C', KEY_NONE},
-                                           {'v', 'V', KEY_NONE},
-                                           {'b', 'B', KEY_NONE},
-                                           {'n', 'N', KEY_NONE},
-                                           {'m', 'M', KEY_NONE},
-                                           {',', '<', KEY_LEFT},
-                                           {'.', '>', KEY_DOWN},
-                                           {'/', '?', KEY_RIGHT},
-                                           {' ', ' ', KEY_NONE}}};
-
-class Keyboard_Class {
-public:
-    struct KeysState {
-        bool tab          = false;
-        bool fn           = false;
-        bool shift        = false;
-        bool ctrl         = false;
-        bool opt          = false;
-        bool alt          = false;
-        bool backspace    = false;
-        bool del          = false;
-        bool enter        = false;
-        bool space        = false;
-        bool esc          = false;
-        bool f1           = false;
-        bool f2           = false;
-        bool f3           = false;
-        bool f4           = false;
-        bool f5           = false;
-        bool f6           = false;
-        bool f7           = false;
-        bool f8           = false;
-        bool f9           = false;
-        bool f10          = false;
-        bool f11          = false;
-        bool f12          = false;
-        bool up           = false;
-        bool left         = false;
-        bool down         = false;
-        bool right        = false;
-        uint8_t modifiers = 0;
-
-        std::vector<char> word;
-        std::vector<uint8_t> hid_keys;
-        std::vector<uint8_t> modifier_keys;
-
-        void reset()
-        {
-            tab       = false;
-            fn        = false;
-            shift     = false;
-            ctrl      = false;
-            opt       = false;
-            alt       = false;
-            backspace = false;
-            del       = false;
-            enter     = false;
-            space     = false;
-            esc       = false;
-            f1        = false;
-            f2        = false;
-            f3        = false;
-            f4        = false;
-            f5        = false;
-            f6        = false;
-            f7        = false;
-            f8        = false;
-            f9        = false;
-            f10       = false;
-            f11       = false;
-            f12       = false;
-            up        = false;
-            left      = false;
-            down      = false;
-            right     = false;
-            modifiers = 0;
-            word.clear();
-            hid_keys.clear();
-            modifier_keys.clear();
-        }
-    };
-
-    Keyboard_Class() : _is_caps_locked(false)
-    {
-    }
-
-    void begin();
-    void begin(std::unique_ptr<KeyboardReader> reader);
-    uint8_t getKey(Point2D_t keyCoor);
-
-    void updateKeyList();
-    inline const std::vector<Point2D_t>& keyList()
-    {
-        if (_keyboard_reader) {
-            return _keyboard_reader->keyList();
-        }
-        static const std::vector<Point2D_t> empty_list;
-        return empty_list;
-    }
-
-    inline KeyValue_t getKeyValue(const Point2D_t& keyCoor)
-    {
-        return _key_value_map[keyCoor.y][keyCoor.x];
-    }
-
-    uint8_t isPressed();
-    bool isChange();
-    bool isKeyPressed(char c);
-
-    void updateKeysState();
-    inline KeysState& keysState()
-    {
-        return _keys_state_buffer;
-    }
-
-    inline bool capslocked(void)
-    {
-        return _is_caps_locked;
-    }
-    inline void setCapsLocked(bool isLocked)
-    {
-        _is_caps_locked = isLocked;
-    }
-
-private:
-    std::unique_ptr<KeyboardReader> _keyboard_reader;
-    std::vector<Point2D_t> _key_pos_print_keys;     // only text: eg A,B,C
-    std::vector<Point2D_t> _key_pos_hid_keys;       // print key + space, enter, del
-    std::vector<Point2D_t> _key_pos_modifier_keys;  // modifier key: eg shift, ctrl, alt
-    KeysState _keys_state_buffer;
-    bool _is_caps_locked;
-    uint8_t _last_key_size;
-};
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/IOMatrix.cpp b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/IOMatrix.cpp
deleted file mode 100644
index 5531f00..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/IOMatrix.cpp
+++ /dev/null
@@ -1,79 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#include "IOMatrix.h"
-#include <Arduino.h>
-
-void IOMatrixKeyboardReader::set_output(const std::vector<int>& pinList, uint8_t output)
-{
-    output = output & 0B00000111;
-
-    digitalWrite(pinList[0], (output & 0B00000001));
-    digitalWrite(pinList[1], (output & 0B00000010));
-    digitalWrite(pinList[2], (output & 0B00000100));
-}
-
-uint8_t IOMatrixKeyboardReader::get_input(const std::vector<int>& pinList)
-{
-    uint8_t buffer    = 0x00;
-    uint8_t pin_value = 0x00;
-
-    for (int i = 0; i < 7; i++) {
-        pin_value = (digitalRead(pinList[i]) == 1) ? 0x00 : 0x01;
-        pin_value = pin_value << i;
-        buffer    = buffer | pin_value;
-    }
-
-    return buffer;
-}
-
-void IOMatrixKeyboardReader::begin()
-{
-    for (auto i : output_list) {
-        gpio_reset_pin((gpio_num_t)i);
-        pinMode(i, OUTPUT);
-        digitalWrite(i, 0);
-    }
-
-    for (auto i : input_list) {
-        gpio_reset_pin((gpio_num_t)i);
-        pinMode(i, INPUT_PULLUP);
-    }
-
-    set_output(output_list, 0);
-}
-
-void IOMatrixKeyboardReader::update()
-{
-    _key_list.clear();
-
-    Point2D_t coor;
-    uint8_t input_value = 0;
-
-    for (int i = 0; i < 8; i++) {
-        set_output(output_list, i);
-        input_value = get_input(input_list);
-        /* If key pressed */
-
-        if (input_value) {
-            /* Get X */
-            for (int j = 0; j < 7; j++) {
-                if (input_value & (0x01 << j)) {
-                    coor.x = (i > 3) ? X_map_chart[j].x_1 : X_map_chart[j].x_2;
-
-                    /* Get Y */
-                    coor.y = (i > 3) ? (i - 4) : i;
-                    // printf("%d,%d\t", coor.x, coor.y);
-
-                    /* Keep the same as picture */
-                    coor.y = -coor.y;
-                    coor.y = coor.y + 3;
-
-                    _key_list.push_back(coor);
-                }
-            }
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/IOMatrix.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/IOMatrix.h
deleted file mode 100644
index 9c9a071..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/IOMatrix.h
+++ /dev/null
@@ -1,36 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#pragma once
-#include "KeyboardReader.h"
-#include <Arduino.h>
-#include <vector>
-
-struct Chart_t {
-    uint8_t value;
-    uint8_t x_1;
-    uint8_t x_2;
-};
-
-/**
- * @brief IO Matrix keyboard reader implementation
- */
-class IOMatrixKeyboardReader : public KeyboardReader {
-public:
-    IOMatrixKeyboardReader()          = default;
-    virtual ~IOMatrixKeyboardReader() = default;
-
-    void begin() override;
-    void update() override;
-
-private:
-    const std::vector<int> output_list = {8, 9, 11};
-    const std::vector<int> input_list  = {13, 15, 3, 4, 5, 6, 7};
-
-    const Chart_t X_map_chart[7] = {{1, 0, 1}, {2, 2, 3}, {4, 4, 5}, {8, 6, 7}, {16, 8, 9}, {32, 10, 11}, {64, 12, 13}};
-
-    void set_output(const std::vector<int>& pinList, uint8_t output);
-    uint8_t get_input(const std::vector<int>& pinList);
-};
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/KeyboardReader.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/KeyboardReader.h
deleted file mode 100644
index 1ea9044..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/KeyboardReader.h
+++ /dev/null
@@ -1,51 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#pragma once
-#include <vector>
-
-struct Point2D_t {
-    int x = 0;
-    int y = 0;
-
-    bool operator==(const Point2D_t& other) const
-    {
-        return x == other.x && y == other.y;
-    }
-};
-
-/**
- * @brief Abstract interface for keyboard reading implementations
- */
-class KeyboardReader {
-public:
-    virtual ~KeyboardReader() = default;
-
-    /**
-     * @brief Initialize the keyboard reader
-     */
-    virtual void begin()
-    {
-    }
-
-    /**
-     * @brief Update the keyboard state and key list
-     */
-    virtual void update()
-    {
-    }
-
-    /**
-     * @brief Get the current key list
-     * @return Reference to the key list
-     */
-    inline const std::vector<Point2D_t>& keyList() const
-    {
-        return _key_list;
-    }
-
-protected:
-    std::vector<Point2D_t> _key_list;
-};
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/TCA8418.cpp b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/TCA8418.cpp
deleted file mode 100644
index 774ceaf..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/TCA8418.cpp
+++ /dev/null
@@ -1,121 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#include "TCA8418.h"
-#include "../../common.h"
-#include "../../Adafruit_TCA8418/Adafruit_TCA8418_registers.h"
-#include <Arduino.h>
-#include <M5Unified.h>
-
-// Default interrupt pin for M5Cardputer ADV
-#define DEFAULT_TCA8418_INT_PIN 11
-
-TCA8418KeyboardReader::TCA8418KeyboardReader(int interrupt_pin) : _isr_flag(false), _interrupt_pin(interrupt_pin)
-{
-    if (_interrupt_pin < 0) {
-        _interrupt_pin = DEFAULT_TCA8418_INT_PIN;
-    }
-}
-
-void IRAM_ATTR TCA8418KeyboardReader::gpio_isr_handler(void* arg)
-{
-    TCA8418KeyboardReader* reader = static_cast<TCA8418KeyboardReader*>(arg);
-    reader->_isr_flag             = true;
-}
-
-void TCA8418KeyboardReader::begin()
-{
-    // Initialize TCA8418
-    _tca8418 = std::make_unique<Adafruit_TCA8418>();
-
-    if (!_tca8418->begin()) {
-        printf("[error] TCA8418KeyboardReader: Failed to initialize TCA8418\n");
-        return;
-    }
-
-    // Setup
-    _tca8418->matrix(7, 8);
-    _tca8418->flush();
-
-    // Setup interrupt pin
-    if (_interrupt_pin >= 0) {
-        pinMode(_interrupt_pin, INPUT);
-        attachInterruptArg(digitalPinToInterrupt(_interrupt_pin), gpio_isr_handler, this, CHANGE);
-    }
-
-    // Enable interrupts
-    _tca8418->enableInterrupts();
-}
-
-void TCA8418KeyboardReader::update()
-{
-    if (!_isr_flag) {
-        return;
-    }
-
-    _key_event_raw_buffer = get_key_event_raw(_tca8418->getEvent());
-
-    //  try to clear the IRQ flag
-    //  if there are pending events it is not cleared
-    _tca8418->writeRegister8(TCA8418_REG_INT_STAT, 1);
-    int intstat = _tca8418->readRegister8(TCA8418_REG_INT_STAT);
-    if ((intstat & 0x01) == 0) {
-        _isr_flag = false;
-    }
-
-    remap(_key_event_raw_buffer);
-    // printf("key event raw: (%d, %d): %d\n", _key_event_raw_buffer.row, _key_event_raw_buffer.col,
-    //        _key_event_raw_buffer.state);
-
-    update_key_list(_key_event_raw_buffer);
-}
-
-TCA8418KeyboardReader::KeyEventRaw_t TCA8418KeyboardReader::get_key_event_raw(const uint8_t& eventRaw)
-{
-    KeyEventRaw_t ret;
-    ret.state       = eventRaw & 0x80;
-    uint16_t buffer = eventRaw;
-    buffer &= 0x7F;
-    buffer--;
-    ret.row = buffer / 10;
-    ret.col = buffer % 10;
-    return ret;
-}
-
-// Remap to the same as cardputer
-void TCA8418KeyboardReader::remap(KeyEventRaw_t& key)
-{
-    // Col
-    uint8_t col = 0;
-    col         = key.row * 2;
-    if (key.col > 3) col++;
-
-    // Row
-    uint8_t row = 0;
-    row         = (key.col + 4) % 4;
-
-    key.row = row;
-    key.col = col;
-}
-
-void TCA8418KeyboardReader::update_key_list(const KeyEventRaw_t& eventRaw)
-{
-    Point2D_t point;
-    point.x = eventRaw.col;
-    point.y = eventRaw.row;
-
-    // Add or remove the key from the list
-    if (eventRaw.state) {
-        auto it = std::find(_key_list.begin(), _key_list.end(), point);
-        if (it == _key_list.end()) {
-            _key_list.push_back(point);
-        }
-    } else {
-        auto it = std::find(_key_list.begin(), _key_list.end(), point);
-        if (it != _key_list.end()) {
-            _key_list.erase(it);
-        }
-    }
-}
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/TCA8418.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/TCA8418.h
deleted file mode 100644
index dce1fc0..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/KeyboardReader/TCA8418.h
+++ /dev/null
@@ -1,40 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#pragma once
-#include "KeyboardReader.h"
-#include "../../Adafruit_TCA8418/Adafruit_TCA8418.h"
-#include <Arduino.h>
-#include <vector>
-#include <memory>
-
-/**
- * @brief TCA8418 I2C keyboard reader implementation
- */
-class TCA8418KeyboardReader : public KeyboardReader {
-public:
-    TCA8418KeyboardReader(int interrupt_pin = -1);
-    virtual ~TCA8418KeyboardReader() = default;
-
-    void begin() override;
-    void update() override;
-
-private:
-    struct KeyEventRaw_t {
-        bool state  = false;
-        uint8_t row = 0;
-        uint8_t col = 0;
-    };
-
-    std::unique_ptr<Adafruit_TCA8418> _tca8418;
-    volatile bool _isr_flag;
-    int _interrupt_pin;
-    KeyEventRaw_t _key_event_raw_buffer;
-
-    static void IRAM_ATTR gpio_isr_handler(void* arg);
-    KeyEventRaw_t get_key_event_raw(const uint8_t& eventRaw);
-    void remap(KeyEventRaw_t& eventRaw);
-    void update_key_list(const KeyEventRaw_t& eventRaw);
-};
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard_def.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard_def.h
deleted file mode 100644
index dd40f4b..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/Keyboard/Keyboard_def.h
+++ /dev/null
@@ -1,177 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#ifndef M5CARDPUTER_KB_KEYS_DEF_H
-#define M5CARDPUTER_KB_KEYS_DEF_H
-
-#include <cstdint>
-
-#define SHIFT 0x80
-
-#define KEY_LEFT_CTRL  0x80
-#define KEY_LEFT_SHIFT 0x81
-#define KEY_LEFT_ALT   0x82
-
-#define KEY_FN  0xff
-#define KEY_OPT 0x00
-
-#define KEY_F1  0x3A
-#define KEY_F2  0x3B
-#define KEY_F3  0x3C
-#define KEY_F4  0x3D
-#define KEY_F5  0x3E
-#define KEY_F6  0x3F
-#define KEY_F7  0x40
-#define KEY_F8  0x41
-#define KEY_F9  0x42
-#define KEY_F10 0x43
-#define KEY_F11 0x44
-#define KEY_F12 0x45
-
-#define KEY_RIGHT 0x4F
-#define KEY_LEFT  0x50
-#define KEY_DOWN  0x51
-#define KEY_UP    0x52
-
-#define KEY_BACKSPACE 0x2a
-#define KEY_TAB       0x2b
-#define KEY_ENTER     0x28
-#define KEY_ESCAPE    0x29
-#define KEY_DELETE    0x4c
-#define KEY_NONE      0x00
-
-const uint8_t _kb_asciimap[128] = {
-    0x00,           // NUL
-    0x00,           // SOH
-    0x00,           // STX
-    0x00,           // ETX
-    0x00,           // EOT
-    0x00,           // ENQ
-    0x00,           // ACK
-    0x00,           // BEL
-    KEY_BACKSPACE,  // BS	Backspace
-    KEY_TAB,        // TAB	Tab
-    KEY_ENTER,      // LF	Enter
-    0x00,           // VT
-    0x00,           // FF
-    0x00,           // CR
-    0x00,           // SO
-    0x00,           // SI
-    KEY_DELETE,     // DEL
-    0x00,           // DC1
-    0x00,           // DC2
-    0x00,           // DC3
-    0x00,           // DC4
-    0x00,           // NAK
-    0x00,           // SYN
-    0x00,           // ETB
-    0x00,           // CAN
-    0x00,           // EM
-    0x00,           // SUB
-    KEY_ESCAPE,     // ESC
-    0x00,           // FS
-    0x00,           // GS
-    0x00,           // RS
-    0x00,           // US
-
-    0x2c,          //  ' '
-    0x1e | SHIFT,  // !
-    0x34 | SHIFT,  // "
-    0x20 | SHIFT,  // #
-    0x21 | SHIFT,  // $
-    0x22 | SHIFT,  // %
-    0x24 | SHIFT,  // &
-    0x34,          // '
-    0x26 | SHIFT,  // (
-    0x27 | SHIFT,  // )
-    0x25 | SHIFT,  // *
-    0x2e | SHIFT,  // +
-    0x36,          // ,
-    0x2d,          // -
-    0x37,          // .
-    0x38,          // /
-    0x27,          // 0
-    0x1e,          // 1
-    0x1f,          // 2
-    0x20,          // 3
-    0x21,          // 4
-    0x22,          // 5
-    0x23,          // 6
-    0x24,          // 7
-    0x25,          // 8
-    0x26,          // 9
-    0x33 | SHIFT,  // :
-    0x33,          // ;
-    0x36 | SHIFT,  // <
-    0x2e,          // =
-    0x37 | SHIFT,  // >
-    0x38 | SHIFT,  // ?
-    0x1f | SHIFT,  // @
-    0x04 | SHIFT,  // A
-    0x05 | SHIFT,  // B
-    0x06 | SHIFT,  // C
-    0x07 | SHIFT,  // D
-    0x08 | SHIFT,  // E
-    0x09 | SHIFT,  // F
-    0x0a | SHIFT,  // G
-    0x0b | SHIFT,  // H
-    0x0c | SHIFT,  // I
-    0x0d | SHIFT,  // J
-    0x0e | SHIFT,  // K
-    0x0f | SHIFT,  // L
-    0x10 | SHIFT,  // M
-    0x11 | SHIFT,  // N
-    0x12 | SHIFT,  // O
-    0x13 | SHIFT,  // P
-    0x14 | SHIFT,  // Q
-    0x15 | SHIFT,  // R
-    0x16 | SHIFT,  // S
-    0x17 | SHIFT,  // T
-    0x18 | SHIFT,  // U
-    0x19 | SHIFT,  // V
-    0x1a | SHIFT,  // W
-    0x1b | SHIFT,  // X
-    0x1c | SHIFT,  // Y
-    0x1d | SHIFT,  // Z
-    0x2f,          // [
-    0x31,          // bslash
-    0x30,          // ]
-    0x23 | SHIFT,  // ^
-    0x2d | SHIFT,  // _
-    0x35,          // `
-    0x04,          // a
-    0x05,          // b
-    0x06,          // c
-    0x07,          // d
-    0x08,          // e
-    0x09,          // f
-    0x0a,          // g
-    0x0b,          // h
-    0x0c,          // i
-    0x0d,          // j
-    0x0e,          // k
-    0x0f,          // l
-    0x10,          // m
-    0x11,          // n
-    0x12,          // o
-    0x13,          // p
-    0x14,          // q
-    0x15,          // r
-    0x16,          // s
-    0x17,          // t
-    0x18,          // u
-    0x19,          // v
-    0x1a,          // w
-    0x1b,          // x
-    0x1c,          // y
-    0x1d,          // z
-    0x2f | SHIFT,  // {
-    0x31 | SHIFT,  // |
-    0x30 | SHIFT,  // }
-    0x35 | SHIFT,  // ~
-    0              // DEL
-};
-
-#endif
diff --git a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/common.h b/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/common.h
deleted file mode 100644
index aefe4fe..0000000
--- a/devices/m5stack/cardputer-adv/artifacts/source-snapshots/M5Cardputer-f1392858/src/utility/common.h
+++ /dev/null
@@ -1,33 +0,0 @@
-/*
- * SPDX-FileCopyrightText: 2025 M5Stack Technology CO LTD
- *
- * SPDX-License-Identifier: MIT
- */
-#pragma once
-#include <memory>
-#include <utility>
-#include <type_traits>
-#include <cstddef>
-
-#if __cplusplus < 201402L
-namespace std {
-
-template <class T, class... Args>
-typename std::enable_if<!std::is_array<T>::value, std::unique_ptr<T>>::type make_unique(Args&&... args)
-{
-    return std::unique_ptr<T>(new T(std::forward<Args>(args)...));
-}
-
-template <class T>
-typename std::enable_if<std::is_array<T>::value && std::extent<T>::value == 0, std::unique_ptr<T>>::type make_unique(
-    std::size_t n)
-{
-    using U = typename std::remove_extent<T>::type;
-    return std::unique_ptr<T>(new U[n]());
-}
-
-template <class T, class... Args>
-typename std::enable_if<(std::extent<T>::value != 0), void>::type make_unique(Args&&...) = delete;
-
-}  // namespace std
-#endif
diff --git a/devices/m5stack/cardputer-adv/certification-and-compliance.md b/devices/m5stack/cardputer-adv/certification-and-compliance.md
deleted file mode 100644
index 852aefd..0000000
--- a/devices/m5stack/cardputer-adv/certification-and-compliance.md
+++ /dev/null
@@ -1,158 +0,0 @@
-# Certification and compliance — cardputer-adv
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5CARDPUTERADV` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AN3WM5STAMPS3A`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5CARDPUTERADV`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2412-2462 MHz Original Equipment 2025-11-19** |
-| Application purpose | Final Action Date 2412-2462 MHz Original Equipment 2025-11-19 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 4 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5CARDPUTERADV` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-- USA-DueDigilenceLetter_V0.1 [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 1,041,781 | `b6e8389cbab5335b…` |
-| `ID-Label-Location-Info-FCC-ID-Label.pdf` | 184,122 | `38b3c9554c31c2df…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,848,880 | `b7b25570be4a4fb5…` |
-| `RF-Exposure-Info-AiTDG-251013004W3_FCC-RF-EXPOSURE-0cm.pdf` | 258,022 | `f63d066218178f0e…` |
-| `Test-Report-AiTDG-251013004W1-FCC-BLE-test-report.pdf` | 987,894 | `5023c54591ee8a5f…` |
-| `Users-Manual-User-Manual.pdf` | 390,005 | `2e7ea0b53e452386…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5CARDPUTERADV/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5CARDPUTERADV/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AN3WM5STAMPS3A`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2025-02-13** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2025-02-13 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5STAMPS3A` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 2,142,184 | `6910fdc8e5f46913…` |
-| `ID-Label-Location-Info-label-and-location.pdf` | 69,357 | `60d9ccb36cc10e2a…` |
-| `Internal-Photos-Internal-Photos.pdf` | 2,778,287 | `e6512283b0e419c2…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE-20cm-.pdf` | 176,710 | `db49d95ade5911cc…` |
-| `Test-Report-AiTDG-241205002W1-Test-Report-BLE.pdf` | 959,274 | `027dd133c4ac00b6…` |
-| `Users-Manual-User-Manual.pdf` | 2,308,121 | `e9056d899bdd6cda…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5STAMPS3A/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5STAMPS3A/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cardputer-adv/commands.md b/devices/m5stack/cardputer-adv/commands.md
deleted file mode 100644
index 50dc0cc..0000000
--- a/devices/m5stack/cardputer-adv/commands.md
+++ /dev/null
@@ -1,250 +0,0 @@
-# Cardputer ADV — command ledger
-
-> Every command that mattered, with status. Environment: **Linux (NixOS-style store paths)**,
-> **bash 5**, `curl 8.x`, `git 2.x`, `python3` (stdlib only), `gh` CLI authenticated.
-> Date **2026-09-04**. Working directory for scratch commands:
-> `hardware-doc/scratch/m5stack-cardputer/`.
->
-> Status ∈ `executed-success`, `executed-failed`, `reported-working`, `inferred`, `not-tested`.
-
-## 0. Host limitations that shaped everything below
-
-```bash
-which pdftotext qpdf mutool gs        # -> not found (all three)
-python3 -c "import pypdf"             # ModuleNotFoundError
-python3 -c "import fitz"              # ModuleNotFoundError
-python3 -c "import pdfminer"          # ModuleNotFoundError
-python3 -c "import PIL"               # not available
-which file                            # -> not found
-```
-`executed-success` (as negative probes). **No PDF or image tooling exists on this host**, which
-is why `pdfbbox.py` and `pngcrop.py` were written. `file` is also absent, so MIME validation was
-done by reading magic bytes in Python.
-
-## 1. Fetching M5Stack documentation
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-curl -sS -o cardputer-adv.html -w '%{http_code} %{size_download}\n' -A "$UA" -L \
-  "https://docs.m5stack.com/en/core/Cardputer-Adv"                      # 200 147339
-curl -sS -o cardputer-v1.1.html  -A "$UA" -L "https://docs.m5stack.com/en/core/Cardputer%20V1.1"   # 200
-curl -sS -o cardputer-mesh.html  -A "$UA" -L "https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit" # 200
-curl -sS -o cardputer-zero.html  -A "$UA" -L "https://docs.m5stack.com/en/CardputerZero"           # 200
-curl -sS -o adv.zh.html          -A "$UA" -L "https://docs.m5stack.com/zh_CN/core/Cardputer-Adv"   # 200
-```
-`executed-success`. **No User-Agent fallback was needed** — every M5Stack host answered 200 to
-the first request, confirming `vendors/m5stack` §1.
-
-```bash
-curl -sS -A "$UA" -L "https://docs.m5stack.com/en/accessory/Cardputer%20Accessory%20Kit_v1.1"
-# -> 404, 4162 bytes
-```
-`executed-failed` — **useful negative.** The `_v1.1` suffix form does not exist for accessory
-pages; the v1.1 accessory kit is a shop SKU only.
-
-## 2. Fetching artifacts, with validation
-
-```bash
-dl(){ u="$1"; o="$(basename "$u")"
-      c=$(curl -sS -o "$o" -w '%{http_code}' -A "$UA" -L "$u")
-      echo "$c $(stat -c%s "$o") $o"; }
-dl "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf"
-dl "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf"
-dl "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer.pdf"
-dl "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5Cardputer.pdf"
-dl "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2.pdf"
-sha256sum *.pdf
-```
-`executed-success`. Because `file` is unavailable, type validation was:
-
-```bash
-python3 -c "
-for f in ['Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf']:
-    print(f, open(f,'rb').read(8))"     # -> b'%PDF-1.4'
-```
-`executed-success`.
-
-**The finding that came out of hashing:**
-
-```bash
-cmp Sch_M5Cardputer.pdf v10-Sch_M5Cardputer.pdf && echo IDENTICAL
-# -> IDENTICAL v1.0 vs v1.1 schematic PDFs
-```
-`executed-success`. Both are `6016c1fe6099b9e3f0d0c88f07a3fba1aa44a3da8a7a91dd7040ad0fffa2041e`.
-
-## 3. Sheet renders
-
-```bash
-for n in 01 02 03 04; do
-  curl -sS -A "$UA" -L -o "adv-sch-page_$n.png" \
-    "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_$n.png"
-done
-python3 -c "
-import struct,glob
-for f in sorted(glob.glob('*.png')):
-    d=open(f,'rb').read(33); print(f, *struct.unpack('>II', d[16:24]))"
-# -> each 5848 4132
-```
-`executed-success`.
-
-```bash
-curl -sS -A "$UA" -L -o stamps3-sch_01.png \
-  "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2_page_01.png"
-# -> 402 bytes, not a PNG
-```
-`executed-failed` — **useful negative.** The `_page_NN.png` render convention does **not** apply
-to product id `522`. Do not assume renders exist for every schematic. The file was **not**
-retained under a `.png` name (per the skill's rule about misleading extensions); it was deleted
-after the magic-byte check.
-
-## 4. PDF text extraction (custom tool)
-
-```bash
-python3 pdfbbox.py artifacts/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf - pdf-adv
-# page 1: 712 words -> pdf-adv/bbox-p1.xml   (etc.)
-```
-`executed-success`, after three corrections that are worth recording because each failed
-*silently*:
-
-| Attempt | Symptom | Cause | Fix |
-|---|---|---|---|
-| 1 | 865 "words", all `CO`/`PI`/`NL` markers, characters doubled (`PPIICC110022`) | Altium draws each glyph twice (fill + stroke) | de-duplicate on `(char, round(x,2), round(y,2))` |
-| 2 | every character its own word | glyph advance computed as `w/1000×fsize`, ignoring the scale Altium hides in `Tm` | transform the pen position before and after each glyph; take the device-space distance |
-| 3 | 296 words, **no readable text at all** — only the marker layer | the `Do` operator was ignored, and the entire drawing lives in a **Form XObject** | recurse into Form XObjects |
-
-**Text-layer validation** (mandatory before transcribing anything):
-
-```bash
-grep -oiE '(TCA8418[A-Z]*|ES8311|NS4150B|NS4168|BMI270|SPM1423[A-Z0-9-]*|74HC138)' pdf-adv/all.txt pdf-v11/all.txt | sort | uniq -c
-#  ADV: TCA8418RTWR, ES8311, NS4150B, BMI270
-#  v11: 74HC138, NS4168, SPM1423HM4H-B
-```
-`executed-success`. These match the corresponding product pages' PinMap tables exactly — a clean
-positive control. **Every value actually transcribed was additionally read off a rendered crop.**
-
-## 5. Reference-designator census
-
-```bash
-python3 netlist.py pdf-adv     # wraps hardware-doc/tools/altium_pdf_netlist.py
-# pdf-adv: pages=[1,2,3,4] distinct designators=155
-#   U n=9 1..9 gaps=[]      <- nine ICs, no gaps: the inventory is complete
-python3 pintable.py pdf-adv 2 U9 2.5     # TCA8418 pin table
-python3 pintable.py pdf-adv 4 P3         # EXT header
-```
-`executed-success`. The `U` sequence having **no gaps** is what makes the "no RTC / no fuel gauge
-/ no bridge" statements *verified negatives* rather than failed searches.
-
-## 6. Sheet crops (custom tool)
-
-Scale factor: 5848 px / 842 pt = 4132 / 595 = **6.945 px per PDF point**.
-
-```bash
-python3 pngcrop.py media/adv-sch-page_02.png media/crop-adv-kbd-u9.png     200  800 1900 2150 2
-python3 pngcrop.py media/adv-sch-page_02.png media/crop-adv-kbd-matrix.png 1650 1300 3300 2900 2
-python3 pngcrop.py media/adv-sch-page_02.png media/crop-adv-kbd-s1s2.png   1650 1380 2560 1800 1
-python3 pngcrop.py media/adv-sch-page_02.png media/crop-adv-kbd-rowbus.png 1600  850 3300 1420 2
-python3 pngcrop.py media/v11-sch_02.png      media/crop-v11-kbd-u7.png      200 1350 1900 2150 2
-python3 pngcrop.py media/adv-sch-page_01.png media/crop-adv-pwr1.png        200  200 2450 1300 3
-python3 pngcrop.py media/adv-sch-page_01.png media/crop-adv-pwr2.png       2400  200 4700 1300 3
-python3 pngcrop.py media/stamps3a-sch_01.png media/crop-stamp-a.png         200  200 3000 2200 4
-python3 pngcrop.py media/stamps3a-sch_01.png media/crop-stamp-b.png        2800  200 5800 2200 4
-```
-`executed-success`, ~1.4 s each. The `den` argument min-pools rather than point-samples, which
-matters: point-sampling erases the thin strokes that *are* the schematic.
-
-These nine crops produced, between them: the complete TCA8418 pinout, the three explicit
-no-connects, the S1/S2 → `Y7`/`Y3` verification, the ROW-bus pairing, the 74HC138 pinout, the
-TP4057/CN809J/SY7088 power train with its FB divider values, the DNP marking on R3/D3, and the
-AW35122FDR/WS2812 rail relationship.
-
-## 7. Source repositories
-
-```bash
-git clone -q --depth 50 https://github.com/m5stack/M5Cardputer.git
-git clone -q --depth 50 https://github.com/m5stack/M5Unified.git
-git clone -q --depth 50 https://github.com/m5stack/M5GFX.git
-git clone -q          https://github.com/m5stack/M5Cardputer-UserDemo.git
-git -C M5Cardputer-UserDemo checkout -q origin/CardputerADV
-for d in M5Cardputer M5Unified M5GFX M5Cardputer-UserDemo; do
-  git -C $d log -1 --format='%H %ad %s' --date=iso; done
-```
-`executed-success`. Commits recorded in [`sources.md`](sources.md).
-
-Dating the ADV support:
-```bash
-git -C M5Cardputer log --format='%h %ad %s' --date=short --all | head -30
-# c331c7d 2025-08-29 basic extract          <- reader interface refactor
-# 6928513 2025-09-01 add basic tca8418 reader
-# 8ab9f43 2025-09-02 Merge PR #9 add-cardputer-adv-support
-# eccba25 2026-05-11 add fn layer support   <- arrow keys arrive
-```
-`executed-success`.
-
-## 8. GitHub ecosystem survey
-
-```bash
-gh search repos cardputer --limit 100 --json fullName,description,stargazersCount,updatedAt,license,url
-```
-`executed-success` — returned **100, the API cap**, so the true count is higher.
-
-```bash
-gh api repos/BruceDevices/firmware --jq '"\(.full_name) ★\(.stargazers_count) \(.license.spdx_id) \(.pushed_at)"'
-gh api repos/pr3y/Bruce            # -> redirects to BruceDevices/firmware
-gh api repos/bmorcelli/M5Stick-Launcher  # -> redirects to bmorcelli/Launcher
-gh api "search/code?q=repo:justcallmekoko/ESP32Marauder+cardputer" --jq '.total_count, (.items[].path)'
-gh api repos/meshtastic/firmware/contents/variants --jq '.[].name' | grep -i card   # -> (none at top level)
-gh api "search/code?q=repo:meshtastic/firmware+cardputer" --jq '.items[].path'
-#   -> variants/esp32s3/m5stack_cardputer_adv/platformio.ini
-```
-`executed-success`. **Two upstreams have been renamed** — `pr3y/Bruce` and
-`bmorcelli/M5Stick-Launcher`. Old links redirect but old *names* are what the community uses.
-
-```bash
-curl -s "https://raw.githubusercontent.com/BruceDevices/firmware/HEAD/boards/m5stack-cardputer/m5stack-cardputer.ini"
-curl -s "https://raw.githubusercontent.com/meshtastic/firmware/HEAD/variants/esp32s3/m5stack_cardputer_adv/variant.h"
-```
-`executed-success`. `raw.githubusercontent.com` needs no auth and does not count against the API
-limit — the right tool for file contents, per `hardware-doc/AGENTS.md`.
-
-## 9. Reddit
-
-```bash
-UA='WhatsApp/2.23.20.0'
-curl -sS -A "$UA" -G --data-urlencode "q=cardputer adv" --data-urlencode "sort=relevance" \
-     --data-urlencode "limit=25" --data-urlencode "t=all" "https://old.reddit.com/search.json"
-curl -sS -A "$UA" "https://old.reddit.com/comments/1vcxsv8.json?limit=20"
-```
-`executed-success`. `old.reddit.com` + that UA returns **200** where `www.reddit.com` returns
-403 to plain clients — the technique from `AGENTS.md`, re-confirmed 2026-09-04.
-
-## 10. Shopify
-
-```bash
-curl -sSg -A "$UA_BROWSER" \
-  'https://shop.m5stack.com/search/suggest.json?q=cardputer&resources%5Btype%5D=product&resources%5Blimit%5D=10'
-curl -sSg -A "$UA_BROWSER" 'https://shop.m5stack.com/products/m5stack-cardputer-adv-version-esp32-s3.json'
-```
-`executed-success`.
-
-⚠ **Without `-g`, curl rejects the URL**: `curl: (3) bad range in position 68` — it parses
-`[type]` as a glob range. Use `-g` or percent-encode the brackets. `executed-failed` on the
-first attempt; recorded because the error message does not obviously point at the brackets.
-
-## 11. Commands NOT executed
-
-| Command | Why | Status |
-|---|---|---|
-| `pio run -e m5stack-cardputer` | no toolchain, no hardware | `not-tested` |
-| `idf.py build` for the `CardputerADV` branch | no ESP-IDF 5.4.2 | `not-tested` |
-| `python fetch_repos.py` (UserDemo) | would clone five more repos; pins recorded from `repos.json` instead | `not-tested` |
-| `esptool.py write_flash …` | no hardware. Offsets in [`development.md`](development.md) are **inferred** from `partitions.csv` | `inferred` |
-| M5Burner `/api/v1/firmwares/{id}` | **no firmware id resolved for the ADV** | not attempted |
-| `curl …/1178/Easy_Loader_for_Cardputer-Adv.exe` | Windows binary; deferred | not attempted |
-| `python3 tools/audit_archive.py` | nothing was archived by this pass | n/a |
-
-## 12. Reusable scripts left in scratch
-
-`scratch/m5stack-cardputer/`: `pdfbbox.py`, `pngcrop.py`, `h2t.py`, `dump.py`, `netlist.py`,
-`pintable.py`. The first two are general-purpose and are candidates for promotion to
-`hardware-doc/tools/` — `pdfbbox.py` in particular removes this repository's dependency on
-`pdftotext` being installed, which the three existing `altium_pdf_*.py` tools assume.
diff --git a/devices/m5stack/cardputer-adv/comparisons-and-recommendations.md b/devices/m5stack/cardputer-adv/comparisons-and-recommendations.md
deleted file mode 100644
index d8327d5..0000000
--- a/devices/m5stack/cardputer-adv/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,186 +0,0 @@
-# Cardputer ADV — comparisons and recommendations
-
-> Snapshot **2026-09-04**. Prices are M5Stack's own store for the ADV; competitor prices are
-> **not** dated observations from this pass unless marked. Where I have no dated price, I say so
-> rather than quoting a remembered number.
->
-> Genre context: [`guides/markets/`](../../../guides/markets/README.md) —
-> [`device-comparison-matrix.md`](../../../guides/markets/device-comparison-matrix.md),
-> [`clones-and-variants.md`](../../../guides/markets/clones-and-variants.md).
-
-## 1. Cardputer ADV versus Cardputer v1.1
-
-The comparison most people actually face, because both are on sale at **the same $29.90**.
-
-| | Cardputer v1.1 (`[EOL]`) | **Cardputer ADV** |
-|---|---|---|
-| Price 2026-09-04 | $29.90 | $29.90 |
-| SoC / flash / PSRAM | ESP32-S3FN8 / 8 MB / **none** | **identical** |
-| Display | ST7789V2 240×135 | **identical** |
-| Keyboard feel | 56 keys | 56 keys, **160 gf specified** |
-| Free GPIO for your project | **0** (Grove only) | **7** on the CAP header |
-| Audio out | class-D to a speaker | **codec + amp + 3.5 mm jack** |
-| Audio in | PDM mic | **analog MEMS via codec ADC** |
-| IMU | — | **BMI270** |
-| Battery | 120 + 1400 mAh, separate base | **1750 mAh, one piece** |
-| Expansion modules available | none | **two official, several community** |
-| Upstream Meshtastic | ❌ | ✅ |
-| Weight | 90.0 g | **81.0 g** |
-| Lifecycle | **end of life** | current |
-
-**Recommendation: there is no scenario at parity pricing in which the v1.1 is the better buy.**
-The only reasons to choose it are (a) you already own one, or (b) you specifically need a
-firmware that has not been ported — and the honest list there is short and shrinking
-(Evil-M5Project's ADV support is unconfirmed; NEMO has no ADV config).
-
-**If you already own a v1.1:** upgrade only if you want the jack, the IMU or the CAP header. The
-compute, screen and radio are unchanged, and every ESP32-S3 project you have runs on both.
-
-## 2. Cardputer ADV versus LilyGO T-Deck
-
-| | Cardputer ADV | LilyGO T-Deck / T-Deck Plus |
-|---|---|---|
-| SoC | ESP32-S3 | ESP32-S3 |
-| **PSRAM** | **none** | **8 MB** ⭐ |
-| Display | 1.14″ 240×135 | 2.8″ 320×240, **touch** ⭐ |
-| Keyboard | **56 keys, full QWERTY row, 160 gf** ⭐ | BlackBerry-style membrane keypad, trackball |
-| LoRa | via **CAP module** (+$14.50) | **on board** (SX1262) ⭐ |
-| GNSS | via CAP LoRa module | Plus variant only |
-| Audio | **codec + amp + 3.5 mm jack** ⭐ | I²S speaker, no jack |
-| IMU | BMI270 ⭐ | — |
-| Expansion | **14-pin CAP socket** ⭐ | headers, no module ecosystem |
-| Price | **$29.90 (dated)** | *not observed in this pass* |
-| Meshtastic | ADV variant | multiple long-standing variants |
-
-**The two differences that decide it: PSRAM and screen size.** If you are writing a GUI, running
-LVGL, buffering audio or holding a large font in RAM, the T-Deck's 8 MB of PSRAM removes the
-single hardest constraint on the Cardputer platform. If you are typing — text, chat, terminal,
-tracker patterns — the Cardputer's key layout is materially better than a BlackBerry keypad.
-
-Not equivalents. **Partial substitutes**, and which is "better" depends entirely on whether your
-bottleneck is memory or input.
-
-⚠ **I did not retrieve a dated T-Deck price**, so this is a capability comparison, not a
-value comparison.
-
-## 3. Cardputer ADV versus Nicolai Electronics Tanmatsu
-
-[`devices/nicolai-electronics/tanmatsu`](../../nicolai-electronics/tanmatsu/README.md)
-
-| | Cardputer ADV | Tanmatsu |
-|---|---|---|
-| Processor | ESP32-S3, 2×LX7 @240 MHz | **ESP32-P4** + companion radio ⭐ |
-| Memory | 512 KB, **no PSRAM** | far larger; MIPI DSI display pipeline |
-| Display | 1.14″ SPI | **MIPI DSI** ⭐ |
-| Keyboard | 56 keys, rubber dome | full QWERTY, Solder Party keyboard family |
-| LoRa | CAP module | **on board** ⭐ |
-| Expansion | 14-pin CAP | **36-pin expansion port** ⭐ |
-| **Openness** | schematic PDF only; **no EDA source**, no published licence | **full KiCad under CERN-OHL-P**, firmware MIT, Sphinx docs in git ⭐⭐ |
-| App ecosystem | ~100 GitHub repos, no app store | **AppFS + BadgeLink**, 57 catalogued apps |
-| Origin | Shenzhen consumer product | Dutch hacker-camp badge lineage, low volume |
-| Price | **$29.90 (dated)** | several times that — *not observed in this pass* |
-
-These are **not competitors**; they are different answers to "I want a hackable handheld".
-
-* Choose the **Tanmatsu** when openness is the requirement — you need the schematic *source*,
-  you need to modify the hardware, you need a documented app framework, or you need P4-class
-  compute and a real display pipeline.
-* Choose the **Cardputer ADV** when price is the requirement, when you want the largest possible
-  body of existing firmware to draw on, or when you want to buy ten of them.
-
-One honest asymmetry worth naming: the **Tanmatsu record in this repository is better than this
-one can be**, because Nicolai publishes KiCad. Several findings there exist only because the PCB
-was parsed. For the Cardputer, the best available primary evidence is a PDF render and the
-vendor's own firmware — which is why this record leans so hard on M5Unified, M5GFX and the
-factory HAL.
-
-## 4. Other things people actually cross-shop
-
-| Device | Why it comes up | The real difference |
-|---|---|---|
-| **Flipper Zero** | the cultural reference point — *"budget Flipper zero alternative"*, r/CardPuter 2026-06-27 | Flipper has integrated sub-GHz, NFC, iButton, IR RX and a polished UX. The ADV needs a Cap CC1101 (+$18.95) and community firmware to approach it, and even then the IR receiver is missing. **Cheaper, not equivalent.** |
-| **LilyGO T-Embed CC1101 Plus** | r/M5Stack, **2026-09-04**: *"which one should i get? m5stack cardputer adv or t embed c1101 plus?"* | T-Embed integrates CC1101 and has a rotary encoder; no keyboard. Choose by input method. |
-| **CardputerZero (C154)** | same brand, same shape, running Linux | **A different class of machine.** Quad A53, 512 MB, camera, Ethernet, RTC, USB host. Not a faster ADV — a small Linux computer. u/G33K_FISH, r/CardPuter 2026-05-31: *"You can do things on the Zero you can not do on the ADV and vise versa."* |
-| **PicoCalc** | pocket-computer scene overlap | `jblanked/Picoware` targets both |
-| **Waveshare ESP32-S3 boards** | r/M5Stack 2026-08-13: *"Need help deciding between a waveshare and cardputer adv"* | Waveshare sells screens-and-MCU; the Cardputer sells a *keyboard* and a firmware ecosystem |
-
-## 5. When to use / when not to use
-
-**Use the Cardputer ADV when:**
-
-* You want a **pocket device you type on** — chat, mesh messaging, notes, terminal, SSH, tracker
-  sequencing. This is what it is best at and what nothing else at the price does.
-* You want **Meshtastic in your pocket with a keyboard**. Buy the Mesh Kit ($48).
-* You want the **largest ready-made firmware library** on a handheld ESP32.
-* You want to **build an expansion board** and would rather use a documented socket than a
-  soldering iron.
-* You want to make music on a $30 device — the 2026 groovebox/synth/DAW scene is real and is
-  ADV-only.
-
-**Do not use it when:**
-
-* You need **PSRAM**. Large framebuffers, LVGL, big fonts, sizeable audio buffers, ML models —
-  512 KB is the wall, and the community's cleverest work is all about getting round it. Buy a
-  T-Deck or a P4-class board.
-* You need **wall-clock time** without a network or GNSS. There is no RTC.
-* You need **IR receive**, **NFC**, or **sub-GHz** out of the box.
-* You need **motion-wake from deep sleep** — no IMU interrupt line was established.
-* You need **certification paperwork**. None is published (see
-  [`gaps-and-conflicts.md`](gaps-and-conflicts.md)).
-* You need **open hardware source**. You get a PDF, and no licence statement.
-* You need a **serviceable battery** or guaranteed spares.
-
-## 6. Alternatives by tier
-
-| Tier | Pick | Why |
-|---|---|---|
-| **Cheapest keyboard handheld** | **Cardputer ADV, $29.90** | nothing else has 56 keys at this price |
-| Cheapest *with* LoRa | **Cardputer Mesh Kit, $48.00** | licensed Meshtastic, antenna included |
-| Cheapest with sub-GHz + NFC | ADV + Cap CC1101, $48.85 | still needs community firmware |
-| **Memory-constrained work** | **LilyGO T-Deck (8 MB PSRAM)** | the ADV's hard wall is exactly what this removes |
-| **Larger screen / touch** | T-Deck, or an ADV + community Cap TFT-2.8 | the Cap route keeps the good keyboard |
-| **Open hardware, hackable** | **Tanmatsu** | CERN-OHL-P KiCad, MIT firmware, real docs |
-| **Polished security tool** | Flipper Zero | integration and UX, at a much higher price |
-| **Linux in the same shape** | CardputerZero (C154) — *when it ships* | still marked "work in progress" |
-| **Buy used** | — | no used-market data was gathered; no recommendation offered |
-
-## 7. What would change these recommendations
-
-* A **PSRAM-equipped Cardputer** would remove the main reason to look elsewhere.
-* An **RTC** — even a $0.30 PCF8563 — would remove the main functional gap.
-* **Published certification** would open commercial and educational deployments.
-* **EDA source** in `M5_Hardware` would make third-party CAP boards much easier and would let
-  the next pass on this device parse a netlist instead of cropping a PDF.
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered.
-
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — the ADV against the v1.1, the LilyGO T-Display K230 Kit ($263.56 complete), the
-  Tanmatsu (~€120) and the CardputerZero, plus a separate group covering the Caps
-  and the Grove LoRa units. It makes explicit the thing casual comparisons get
-  wrong: **the ADV is not a faster Cardputer** — same ESP32-S3FN8, same 8 MB flash,
-  same *no PSRAM*; the change is the keyboard scanner, and the seven GPIOs it frees
-  *are* the Cap header.
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — the `FN8` (flash, no PSRAM) versus `R8` (PSRAM, no flash) distinction, why it
-  is the most consequential fact about every Cardputer, and this record's
-  **310.89 µA → 6.84 µA Stamp-S3 → Stamp-S3A sleep** figures used as the worked
-  example that **board sleep current is a power-tree property, not a SoC
-  property**. It also carries the Cardputer's memory-mapped 2.16 MB Unicode font as
-  the canonical no-PSRAM workaround.
-- [**Adding LoRa, NFC and an RGB sidelight to e-ink firmware**](../../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-  — the two Caps are used there as **the reference implementation** for adding
-  radios to an existing device, with the Cap-Bus pin map and the Cap CC1101's
-  one-GPIO band-switching trick (`RF_SW1` driven from the CC1101's own `GDO2`). It
-  also imports this platform's **`BL_3V3` lesson** — that PWM-dimming the backlight
-  browns out the WS2812 — as the mistake to avoid when adding an LED to a device
-  whose frontlight you also intend to dim.
-- [**Xteink firmware ecosystem**](../../xteink/firmware-ecosystem.md) — the ADV's
-  G8/G9 pull-up board autodetect is catalogued there alongside four other runtime
-  fingerprints, with the shared lesson that **a fingerprint testing a proxy rather
-  than the thing itself will eventually misfire**.
diff --git a/devices/m5stack/cardputer-adv/compatibility-and-status.md b/devices/m5stack/cardputer-adv/compatibility-and-status.md
deleted file mode 100644
index 81d1822..0000000
--- a/devices/m5stack/cardputer-adv/compatibility-and-status.md
+++ /dev/null
@@ -1,97 +0,0 @@
-# Cardputer ADV — compatibility and status
-
-> Snapshot **2026-09-04**. Keyed by hardware revision and software version.
-> **Nothing in this table was tested on hardware by this session.** Status values are:
-> `official` (vendor states it), `source` (read from code at a pinned commit),
-> `reported` (firsthand community report, cited), `inferred`, `not-established`.
-
-## 1. Vendor libraries
-
-| Library | Version / commit | v1.0 | v1.1 | ADV | Status |
-|---|---|---|---|---|---|
-| `M5Cardputer` | **1.1.1**, `f1392858` (2026-07-21) | ✅ | ✅ | ✅ | `source` |
-| `M5Cardputer` | < 1.1.1 | ✅ | ✅ | ❌ **keyboard silent** | `source` — ADV support landed `c331c7d`…`8ab9f43`, 2025-08-29…09-02 |
-| `M5Cardputer` | < `eccba25` (2026-05-11) | ✅ | ✅ | ⚠ no fn layer → **no arrow keys** | `source` |
-| `M5Unified` | `8530f537` (2026-08-27) | ✅ | ✅ | ✅ | `source` |
-| `M5GFX` | `d91077b9` (2026-08-25) | ✅ | ✅ | ✅ | `source` |
-| `M5Cardputer-UserDemo` | `main` `a34d7ebc` | ✅ | ✅ | ❌ | `source` |
-| `M5Cardputer-UserDemo` | **`CardputerADV`** `b549eac0` (2026-06-08) | ❌ | ❌ | ✅ | `source` |
-
-The single most common ADV problem is an old `M5Cardputer` library: `Keyboard_Class::begin()`
-falls through to the base `KeyboardReader`, which does nothing, prints one `[error]` line, and
-reports no keys. **Check your library version before anything else.**
-
-## 2. ⚠ The autodetect hazard, both directions
-
-M5GFX decides `board_M5CardputerADV` by driving G9/G8/G6/G5 as input-pulldown and testing
-`(result & 0x0C) == 0x0C` — i.e. *"are G8 and G9 pulled up?"*. On the ADV they are, by R36/R37
-(3.3 kΩ). On a v1.x they are 74HC138 address lines with no pull-up.
-
-| Scenario | Outcome |
-|---|---|
-| Stock ADV | detected correctly |
-| Stock v1.0/v1.1 | detected correctly |
-| **v1.x with anything pulling G8 *and* G9 high** | **misdetected as ADV** → TCA8418 reader installed → keyboard dead. On a v1.x, G8/G9 are keyboard address lines, so this requires deliberate external wiring, but a probe clip or a mis-built harness will do it. |
-| ADV with the internal I²C bus shorted low | misdetected as v1.x → GPIO-matrix reader → keyboard dead **and** the reader drives G8/G9/G11 as outputs into a live I²C bus |
-| ADV in a case that stresses the FPC | display autodetect fails first (the panel-ID read on G37 gates everything) |
-
-The second row is the dangerous one, because the fallback reader *drives* pins that are a bus.
-`inferred` — not observed.
-
-## 3. Community firmware
-
-| Firmware | Version at snapshot | v1.0 | v1.1 | ADV | Basis | Notes |
-|---|---|---|---|---|---|---|
-| **Bruce** | `1d555e0d` 2026-08-28 | ✅ | ✅ | ✅ | `source` | one build target, runtime TCA8418 probe. Polled keyboard (100 ms) — less responsive. Inherits the ES8311 reg-`0x01` divergence. |
-| **Launcher** (a.k.a. M5Launcher) | `3b91484e` 2026-09-04 | ✅ | ✅ | ✅ | `source` + vendor doc | `CardputerADV.md`; I²C polling only |
-| **Meshtastic** upstream | `be2f68b5` 2026-09-03 | ❌ | ❌ | ✅ | `source` | `m5stack-cardputer-adv` variant only |
-| **Plai** | ★175, 2026-08-24 | ❌ | ❌ | ✅ | `reported` | *"works great … automatically detected the lora cap"* (u/Big-Bunch2804, 2026-08-05). **Regression 2026-08-29: arrow keys stopped working on ADV; configuration not persisted across firmware switches.** |
-| **MeshCore ports** ×3 | 2026-09 | ❌ | ❌ | ✅ | descriptions | `MultiMote/…` self-describes as "still in development" |
-| **ESP32Marauder** | `91724fd8` 2026-08-24 | ✅ | ✅ | ✅ | `source` | separate `User_Setup_marauder_m5cardputer_adv.h` |
-| **Evil-M5Project** | 2026-08-20 | ✅ | ✅ | ❓ | `not-established` | description lists Cardputer/AtomS3/Fire/Core2, **not** ADV |
-| **NEMO** | `0b8c5c73` 2026-07-15 | ✅ | ✅ | ❓ | `inferred` | no ADV config; builds against `M5Cardputer`, so ≥1.1.1 *should* autodetect. Unverified. |
-| **MicroHydra** | 2026-08-21 | ✅ | ✅ | ❓ | `not-established` | |
-| **Picoware** | 2026-09-03 | ❓ | ❓ | ✅ | description | names "Cardputer ADV" |
-| **d4rkmen/M5Apps** | 2026-08-28 | ✅ | ✅ | ✅ | description | *"v1.0, v1.1 and ADV"* |
-| **UiFlow2** | live service | ✅ | ✅ | ✅ | `official` | separate doc paths per model |
-
-## 4. Peripherals
-
-| Peripheral | ADV | Basis |
-|---|---|---|
-| **Cap LoRa-1262** (U214) | ✅ | official; factory firmware `CardputerADV` branch has `main/hal/cap_lora868/`; Meshtastic variant |
-| **Cap CC1101 & NFC** (U219) | ✅ | official — released 2026-08-28 "For Cardputer-Adv" |
-| Community CAP TFT boards | ✅ reported | `Prokuon/CardputerADV_Cap_TFT-2.8`, ↑989 on r/CardPuter |
-| Any Grove I²C unit | ✅ inferred | standard M5 Grove; bus is otherwise empty |
-| **Cap boards on v1.0/v1.1** | ❌ | no connector, and no free pins to build one |
-| **Cardputer Accessory Kit v1.1** (M5StampS3A + display, $9.95) | ⚠ | sold as a v1.1 spare. It is a *Stamp-S3A + display*, i.e. the parts the ADV also uses, but it is **not** an ADV upgrade path — the mainboard is what differs. |
-
-## 5. Known failures and open reports
-
-| Symptom | Revision | Cause / status |
-|---|---|---|
-| Keyboard reports nothing | ADV | `M5Cardputer` < 1.1.1, or autodetect failed. Check the boot log. |
-| No arrow keys | ADV | library older than `eccba25` (2026-05-11), or third-party firmware that never implemented the fn layer |
-| Arrow keys stopped working after an update | ADV | **firsthand regression report**, Plai, 2026-08-29 |
-| RGB LED dim/dead when the backlight is dimmed | v1.1 and ADV | **by design** — shared `BL_3V3` rail. Vendor documents it for v1.1 only. |
-| Speaker silent after using the microphone | ADV | **driver defect** — the mic disable sequence powers the shared codec down. [`features/audio.md`](features/audio.md) §6.2 |
-| Device will not charge | all | power switch must be **ON** to charge (vendor states this on all three pages) |
-| Black screen on power-on | ADV | **unresolved** — r/M5Stack 2026-08-22, two low-information replies. Single report. |
-| Configuration lost when switching firmware | ADV | reported for Plai; NVS layouts differ between firmwares. Expect to re-provision. |
-| Cannot source replacement screws/buttons | ADV | reported 2026-08-05; M5Stack sells a mixed M3 pack, buttons are commonly 3D-printed |
-
-## 6. Combination testing
-
-Covered in [`resources-and-conflicts.md`](resources-and-conflicts.md) §6. The combinations that
-**fail** rather than merely being tight:
-
-* microphone→speaker without an explicit re-enable (driver defect),
-* backlight PWM + RGB LED (shared rail),
-* IMU motion-wake from deep sleep (no interrupt line established),
-* wall-clock time across a power cycle (no RTC).
-
-## 7. What "untested" means here
-
-This session had **no Cardputer hardware**. Every ✅ above means "the code, the schematic or the
-vendor says so", and every `reported` means "a named person on a dated public post says so".
-None of it means "I saw it work".
diff --git a/devices/m5stack/cardputer-adv/coverage.md b/devices/m5stack/cardputer-adv/coverage.md
deleted file mode 100644
index 3ff70e0..0000000
--- a/devices/m5stack/cardputer-adv/coverage.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# Cardputer ADV — coverage matrix
-
-> Snapshot **2026-09-04**. Every advertised or fitted capability, mapped to hardware, evidence,
-> guide and gap. **No hardware test was performed**, so the "hardware-tested" column is empty
-> throughout and that is stated rather than left implicit.
-
-| Feature | Hardware | Component record | Vendor doc | Vendor code | Community | Guide | Build-tested | HW-tested | Gap |
-|---|---|---|---|---|---|---|---|---|---|
-| Keyboard | TCA8418RTWR @ `0x34`, INT G11 | ✅ new | ✅ PinMap | ✅ `M5Cardputer` | ✅ Bruce, Launcher | [`keyboard.md`](features/keyboard.md) | ❌ | ❌ | per-switch nets for 54 of 56 keys not individually traced |
-| Display | ST7789V2, SPI3 | ✅ existing | ✅ | ✅ M5GFX | ✅ TFT_eSPI, meshtastic/st7789 | [`display.md`](features/display.md) | ❌ | ❌ | no frame-rate measurement |
-| Backlight | G38 → AW35122FDR → `BL_3V3` | ✅ existing | ⚠ warning omitted on the ADV page | ✅ M5GFX | — | [`display.md`](features/display.md) | ❌ | ❌ | — |
-| RGB LED | WS2812, G21, on `BL_3V3` | ✅ new | ✅ | ✅ M5Unified | ✅ | [`display.md`](features/display.md) | ❌ | ❌ | — |
-| Audio out | ES8311 + NS4150B + speaker | ✅ existing ×2 | ✅ | ✅ M5Unified | ✅ Bruce, pschatzmann | [`audio.md`](features/audio.md) | ❌ | ❌ | **live driver defect** §6.2 |
-| 3.5 mm jack | PJ-342 + HP_DET + 2N7002T | ✅ generic | ✅ prose | ❌ hardware-only | ✅ | [`audio.md`](features/audio.md) | ❌ | ❌ | not software-visible |
-| Microphone | MSM381A3729H9BP → ES8311 ADC | ✅ new | ✅ (SNR only) | ✅ M5Unified | ✅ | [`audio.md`](features/audio.md) | ❌ | ❌ | no level/SNR measurement |
-| microSD | SPI G40/14/39, CS G12 | ✅ generic | ✅ | ✅ `_pin_table_sd` | ✅ every firmware | [`microsd.md`](features/microsd.md) | ❌ | ❌ | no card-compatibility data |
-| IMU | BMI270 @ `0x69` | ✅ existing | ✅ + axis diagram | ✅ M5Unified | ✅ | [`imu.md`](features/imu.md) | ❌ | ❌ | **INT1/INT2 routing not established** |
-| **RTC** | **none** | — | — | — | — | [`rtc.md`](features/rtc.md) | — | — | **verified absent** |
-| Battery sense | divider → G10 (ADC1) | ✅ generic | ✅ | ✅ `Power_Class` | ✅ Bruce | [`battery-and-power.md`](features/battery-and-power.md) | ❌ | ❌ | curve shared with the v1.x despite a different cell |
-| Charging | TP4057, R_PROG 3.3 k | ✅ existing | ✅ + switch warning | — | — | [`battery-and-power.md`](features/battery-and-power.md) | ❌ | ❌ | charge current **inferred** |
-| 5 V boost | SY7088 | ✅ existing | ❌ | — | — | [`battery-and-power.md`](features/battery-and-power.md) | — | ❌ | output **inferred**; **no current limit published** |
-| 3.3 V buck | SY8089 | ✅ new | ❌ | — | — | [`battery-and-power.md`](features/battery-and-power.md) | — | ❌ | **FB arithmetic does not resolve** |
-| Supervisor | CN809J | ✅ new | ❌ | — | — | [`battery-and-power.md`](features/battery-and-power.md) | — | ❌ | threshold unknown |
-| Wi-Fi | ESP32-S3 radio | ✅ new (SoC) | ✅ current only | ✅ stock | ✅ Marauder, Bruce, CSI | [`wifi-and-ble.md`](features/wifi-and-ble.md) | ❌ | ❌ | no RF measurement anywhere |
-| BLE | ESP32-S3 radio | ✅ | ✅ | ✅ NimBLE in factory fw | ✅ ChimeraBLE | [`wifi-and-ble.md`](features/wifi-and-ble.md) | ❌ | ❌ | vendor current figure anomalous |
-| IR TX | emitter, G44 | — | ✅ | ✅ factory fw + IRremote | ✅ Ultimate-Remote | [`ir.md`](features/ir.md) | ❌ | ❌ | **no range figure published for the ADV** |
-| **IR RX** | **none** | — | — | — | Grove/CAP workarounds | [`ir.md`](features/ir.md) | — | — | **verified absent** |
-| Grove / PORT.A | HY2.0-4P, G1/G2 | ✅ | ✅ | ✅ `Ex_I2C` | ✅ Bruce pin menus | [`grove-port.md`](features/grove-port.md) | ❌ | ❌ | ⚠ **SCL/SDA colour conflict C2** |
-| **CAP header** | P3, 14-pin | — (interface) | ✅ ×2, ⚠ conflicting | ✅ factory fw + Meshtastic | ✅ 4+ community boards | [`cap-header.md`](features/cap-header.md) | ❌ | ❌ | **no current limit**; no ESD confirmed |
-| USB | native OTG, no bridge | ✅ generic | ✅ download mode | ✅ build flags | ✅ BadCard | [`usb.md`](features/usb.md) | ❌ | ❌ | — |
-| USB HID | native | — | — | ✅ example + `_kb_asciimap` | ✅ | [`usb.md`](features/usb.md) | ❌ | ❌ | — |
-| BLE HID | NimBLE | — | ❌ | ✅ factory sdkconfig | — | [`usb.md`](features/usb.md), [`wifi-and-ble.md`](features/wifi-and-ble.md) | ❌ | ❌ | not documented by M5Stack |
-| Boot / G0 button | Stamp, 10 k pull-up | ✅ generic | ✅ | ✅ | ✅ | [`usb.md`](features/usb.md) | ❌ | ❌ | — |
-| Power switch | SW1 SPDT | — | ✅ charge warning | — | — | [`battery-and-power.md`](features/battery-and-power.md) | — | ❌ | SW2's function not established |
-| Magnets / LEGO base | mechanical | — | ✅ | — | ✅ r/M5Stack thread | — | — | ❌ | — |
-| Lanyard hole | mechanical | — | ✅ comparison table | — | — | — | — | ❌ | — |
-
-## Component records
-
-| Created by this pass | Reused (existing) | Created by a **concurrent session** — linked, not written |
-|---|---|---|
-| `texas-instruments/tca8418` · `generic/74hc138` · `espressif/esp32-s3fn8` · `memsensing/msm381a3729h9bp` · `knowles/spm1423hm4h-b` · `nsiway/ns4168` · `worldsemi/ws2812` · `consonance/cn809` · `silergy/sy8089` · `unidentified/cardputer/lp3218dt1g` | `everest-semiconductor/es8311` · `nsiway/ns4150b` · `bosch-sensortec/bmi270` · `awinic/aw35122` · `joulwatt/jw5712` · `generic/micro-sd-sdmmc` · `generic/3.5mm-audio-output` · `generic/charger-power-path` | `m5stack/stamp-s3` · `m5stack/stamp-s3a` · `sitronix/st7789v2` · `silergy/sy7088` · `sgmicro/sgm2578` · `generic/tp4057` · `unidentified/m5stack-stamp-s3a/dcdc-u4` |
-
-*Used By* additions for the middle and right columns are staged in
-[`scratch/m5stack-cardputer/index-fragments.md`](../../../scratch/m5stack-cardputer/index-fragments.md).
-
-## Uncovered
-
-| Item | Why |
-|---|---|
-| Certification | `/en/certification` not fetched with a positive control — **"not established"**, not "absent" |
-| I²C address table (`/en/product_i2c_addr`) | same |
-| UiFlow2 / Arduino tutorial sub-pages | not fetched |
-| `M5_Hardware` structure/CAD directories | not fetched |
-| Factory firmware **binary** | not retrieved; no M5Burner id resolved |
-| Any measurement of anything | no hardware |
-| SW2's function | not traced |
-| Chinese and Japanese community sources | not searched |
diff --git a/devices/m5stack/cardputer-adv/development.md b/devices/m5stack/cardputer-adv/development.md
deleted file mode 100644
index 6795d24..0000000
--- a/devices/m5stack/cardputer-adv/development.md
+++ /dev/null
@@ -1,185 +0,0 @@
-# Cardputer ADV — development and recovery
-
-> Snapshot **2026-09-04**. **Nothing here was executed on hardware.** Commands are labelled
-> `official` (published verbatim by M5Stack), `source` (read from a build config at a pinned
-> commit) or `inferred`. See [`commands.md`](commands.md) for the full ledger.
-
-## Frameworks at a glance
-
-| Framework | Minimum for ADV | Board target | Notes |
-|---|---|---|---|
-| **Arduino** | `M5Cardputer` **1.1.1** + `M5Unified` + `M5GFX` + `IRremote` | `esp32-s3-devkitc-1` (vendor) or `m5stack-cardputer` | autodetect does the rest |
-| **PlatformIO** | `platform = espressif32@6.7.0` | as above | vendor profile below |
-| **ESP-IDF** | **5.4.2** (from the factory firmware's `sdkconfig.defaults` header) | `esp32s3` | factory firmware is IDF, not Arduino |
-| **UiFlow2** | live service | `cardputer-adv` | `/en/uiflow2/cardputer-adv/program` — a **different** path from the v1.x's `/uiflow2/cardputer/` |
-| **MicroPython** | via UiFlow2 firmware, or MicroHydra | — | see below |
-| **Rust** | `Kezii/Rust-M5Stack-Cardputer` (GPL-3.0) | — | community HAL |
-
-## 1. Arduino / PlatformIO
-
-M5Stack publishes this profile on the ADV, v1.0 **and** v1.1 pages — identical text on all three
-(`official`):
-
-```ini
-[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-  -DESP32S3
-  -DCORE_DEBUG_LEVEL=5
-  -DARDUINO_USB_CDC_ON_BOOT=1
-  -DARDUINO_USB_MODE=1
-lib_deps =
-  M5Cardputer=https://github.com/m5stack/M5Cardputer
-```
-
-Notes, from reading the library at `f1392858`:
-
-* `library.json` declares `"version": "1.1.1"` and dependencies `M5Unified`, `M5GFX`,
-  `arduino-irremote/IRremote`. `library.properties` additionally lists `LibSSH-ESP32` —
-  **the two dependency lists disagree**; the Arduino IDE will try to pull LibSSH, PlatformIO
-  will not. Harmless but confusing.
-* `5604284` (2026-07-20) exists solely to "specify IRremote owner to resolve PlatformIO
-  ambiguous package warning" — if you pin an older library you will see that warning.
-* `board = esp32-s3-devkitc-1` is a **generic** target. It works because M5GFX detects the board
-  at runtime. Bruce and Launcher instead use `board = m5stack-cardputer` with their own
-  `pins_arduino.h`; Meshtastic uses `board = m5stack-stamps3`.
-
-Minimal sketch:
-
-```cpp
-#include <M5Cardputer.h>
-void setup() {
-  auto cfg = M5.config();
-  M5Cardputer.begin(cfg, true);           // second arg enables the keyboard
-}
-void loop() { M5Cardputer.update(); }
-```
-
-`M5Cardputer.begin()` → `M5.begin(cfg)` → M5GFX autodetect → `Keyboard.begin()` picks
-`TCA8418KeyboardReader` or `IOMatrixKeyboardReader` from `M5.getBoard()`.
-
-Build and upload (`inferred`, standard PlatformIO):
-
-```bash
-pio run -e m5stack-cardputer
-pio run -e m5stack-cardputer -t upload
-pio device monitor -b 115200
-```
-
-## 2. ESP-IDF — the factory firmware path
-
-`github.com/m5stack/M5Cardputer-UserDemo`, branch **`CardputerADV`**, commit `b549eac0`
-(2026-06-08). ESP-IDF **5.4.2**.
-
-M5Stack **does not vendor its dependencies.** `repos.json` + `fetch_repos.py` clone five
-repositories at pinned refs:
-
-| Repo | Pinned ref |
-|---|---|
-| `m5stack/M5GFX` | branch **`0.2.15`** |
-| `m5stack/M5Unified` | branch **`0.2.10`** |
-| `Forairaaaaa/mooncake` | `v2.2.0` |
-| `Forairaaaaa/mooncake_log` | `v1.3.0` |
-| `Forairaaaaa/smooth_ui_toolkit` | `v2.4.0` |
-
-⚠ **Those pins are older than the current library heads** (`M5GFX` is at `d91077b9`,
-`M5Unified` at `8530f537` as of 2026-08-27). The shipped factory firmware is therefore **not
-built from anything you can check out at `HEAD`** — the same pattern the PaperMono pass
-recorded for M5Stack's demos. If you are chasing a behavioural difference between the factory
-image and your own build, this is the first thing to check.
-
-`dependencies.lock` additionally pins IDF components including `espressif/esp-now@2.5.2`,
-`espressif/esp_tinyusb`, `espressif/cmake_utilities@0.5.3`.
-
-```bash
-git clone -b CardputerADV https://github.com/m5stack/M5Cardputer-UserDemo.git
-cd M5Cardputer-UserDemo
-python fetch_repos.py          # clones the five pinned repos into components/
-idf.py set-target esp32s3
-idf.py build
-idf.py -p /dev/ttyACM0 flash monitor
-```
-
-`inferred` from the repository layout — not executed here.
-
-`sdkconfig.defaults` highlights: `CONFIG_ESPTOOLPY_FLASHSIZE_8MB=y`,
-`CONFIG_PARTITION_TABLE_CUSTOM=y`, `CONFIG_EXAMPLE_KBD_ENABLE=y`,
-`CONFIG_BT_NIMBLE_ENABLED=y`, `CONFIG_BT_NIMBLE_SVC_GAP_DEVICE_NAME="CardputerADV Keyboard"`,
-`CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_240=y`.
-
-The application tree is worth reading even if you never build it — `main/hal/hal_config.h` is
-the single most compact authoritative pin list for the ADV, and `main/hal/cap_lora868/` is
-M5Stack's own SX1262 + GNSS integration (with a vendored `RadioLib` `EspHal.h` and
-`TinyGPSPlus`).
-
-> ⚠ **Licence caveat.** The demo is MIT, but it pins/vendors **RadioLib**, which is
-> **LGPL-3.0 upstream**. The same flag was raised in the PaperMono pass. Flagged, not resolved.
-
-## 3. UiFlow2
-
-`https://docs.m5stack.com/en/uiflow2/cardputer-adv/program` — a distinct path from the v1.x's
-`/en/uiflow2/cardputer/program`, which means M5Stack ships a **different UiFlow2 firmware** for
-the ADV. Neither page was mined for substance in this pass (the PaperMono pass found M5Stack's
-UiFlow2 pages "empty of substance"; expect the same). Recorded as a gap.
-
-## 4. MicroPython
-
-No official standalone MicroPython port page for the Cardputer was found. Two routes:
-
-* **UiFlow2 firmware** is MicroPython underneath; `uiflow2.m5stack.com` and M5Burner deliver it.
-* **MicroHydra** (`echo-lalia/MicroHydra`, GPL-3.0, ★314) is a MicroPython "OS-like" app
-  switcher, with `echo-lalia/Cardputer-Micropython-Examples` (MIT, ★49) as a starting point.
-  ADV support **not confirmed**.
-
-## 5. Flashing, download mode and recovery
-
-**Download mode** (`official`, identical wording on all three product pages):
-
-> Set the side power switch to **OFF**. Then, **before powering on, hold the G0 button**, apply
-> power, and release it afterwards. The device will then enter download mode.
-
-There is **no reset button on the ADV**, so the usual "hold BOOT, tap RESET" does not apply.
-
-**EasyLoader** (Windows one-click): `…/1178/Easy_Loader_for_Cardputer-Adv.exe`.
-URL recorded; **not downloaded** in this pass.
-
-**esptool** (`inferred` — flash offsets not verified against a real image):
-
-```bash
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 1500000 \
-  write_flash 0x0 bootloader.bin 0x8000 partition-table.bin 0x10000 app.bin
-```
-
-The factory `partitions.csv` puts the application at **`0x10000`** with a 4 MB `factory`
-partition. **Do not treat the command above as authoritative**; it is the standard IDF layout
-applied to the published partition table, not a procedure anyone has run here.
-
-**Erase and start over** (`inferred`): `esptool.py --chip esp32s3 erase_flash`.
-
-## 6. Bricking and hazard notes
-
-* **No UART bridge.** If your firmware never brings up USB CDC, you lose the serial port. USB
-  Serial/JTAG remains, and download mode always works — so the device is very hard to brick, but
-  easy to make *look* bricked.
-* **Charging needs the switch ON.** A flat battery plus a switch left OFF looks like a dead
-  device.
-* **G3 is both the CAP `RESET` line and an ESP32-S3 JTAG-source strap.** Holding it at a defined
-  level through reset changes strapping.
-* **Keep a recovery path.** The factory partition table has a **single `factory` app and no OTA
-  slots**, so a bad flash means re-flashing over USB. `CCP101/cardputer-recoverable-multiboot`
-  is the community answer: M5Launcher in `factory`, applications in OTA slots.
-* **NVS layouts differ between firmwares.** Switching firmware commonly loses settings; reported
-  for Plai on 2026-08-29.
-
-## 7. Debugging
-
-| Tool | Availability |
-|---|---|
-| USB Serial/JTAG console | native, always available |
-| **JTAG** | the ESP32-S3's built-in USB-JTAG works over the same port; the MTDI/MTDO/MTCK/MTMS pins (G41/G40/G39/G42) are all consumed by audio and SD, so external JTAG is impractical |
-| `CORE_DEBUG_LEVEL=5` | in the vendor profile; very verbose — reduce it for real work |
-| M5GFX autodetect log | `[Autodetect] board_M5CardputerADV` — **your first diagnostic** |
-| I²C scan | expect exactly `0x18`, `0x34`, `0x69` on G8/G9 |
diff --git a/devices/m5stack/cardputer-adv/driver-vs-document-audit.md b/devices/m5stack/cardputer-adv/driver-vs-document-audit.md
deleted file mode 100644
index 16f9e08..0000000
--- a/devices/m5stack/cardputer-adv/driver-vs-document-audit.md
+++ /dev/null
@@ -1,146 +0,0 @@
-# Cardputer ADV — vendor driver read against the schematic and the register map
-
-**Audited:** 2026-09-07 · workflow step 10 (*audit vendor firmware and driver source against the
-primary documents*).
-
-**Sources read side by side**
-
-| Role | Path / identity |
-|---|---|
-| Schematic | `artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf`, traced in [`schematic-netlist.md`](schematic-netlist.md) |
-| Vendor driver | `artifacts/source-snapshots/M5Cardputer-f1392858/` — M5Stack `M5Cardputer`, commit `f1392858` |
-| Register map | `…/src/utility/Adafruit_TCA8418/Adafruit_TCA8418_registers.h` (vendored with the driver) |
-| Component record | [`components/texas-instruments/tca8418`](../../../components/texas-instruments/tca8418/README.md) |
-
-**Evidence status.** Register *addresses and bit names* below are quoted from the vendored
-header, which is primary for what the driver believes. Claims about what the silicon does with
-those bits are marked where **no TI datasheet is held in this repository** to check them
-against — that is a gap, not an assertion.
-
-Every finding is labelled **active** (misbehaves in normal use) or **inert** (wrong or fragile,
-but harmless as the code currently runs). An incorrect write that is later overwritten is a
-latent trap, not a live bug.
-
----
-
-## A. Agreements worth recording — the driver matches the sheet
-
-These were checked because they are the things that usually go wrong, and they are correct here.
-Recording a verified agreement is as useful as recording a defect: it stops the next agent
-re-deriving it.
-
-| Claim in the driver | Source | Schematic | Verdict |
-|---|---|---|---|
-| `#define DEFAULT_TCA8418_INT_PIN 11` | `src/utility/Keyboard/KeyboardReader/TCA8418.cpp:13` | `U9` pin 24 `INT` → net `G11` (`NLG11` @ 78.50, 224.66, sheet 2) | ✅ correct |
-| `_tca8418->matrix(7, 8)` — 7 rows | `TCA8418.cpp:38` | `U9` pin 1 `ROW7` has **no net label and no aligned peer pin**; only `ROW0`…`ROW6` are netted | ✅ correct; the sheet wires 7 rows |
-| 8 columns | `TCA8418.cpp:38` | `U9` pins 9–16 → `Y7`…`Y0` through 22 R/1 % series resistors `R27`…`R34` | ✅ correct |
-| I²C address (implicit, fixed part) | `Adafruit_TCA8418` | sheet 2 prints **`7-bit Address 34H`** @ (106–142, 312.5) | ✅ consistent |
-| `pinMode(_interrupt_pin, INPUT)` — **no** internal pull-up on an open-drain `INT` | `TCA8418.cpp:44` | `R37` 3.3 kΩ pulls `G11` to `+3.3V` (one of three at x = 48.5 / 59.5 / 70.5, all spanning y 184.57→206.57, pulling `SDA`, `SCL`, `INT`) | ✅ correct **because of `R37`** — see finding 5 |
-| BMI270 at `0x69` | M5Unified | `U7` pin 1 `SDO` pulled to `+3.3V` by `R43` 3.3 kΩ; sheet prints `7-bit Address 69H` | ✅ correct |
-| BMI270 polled, never interrupt-driven | M5Unified | `U7` `INT1` (pin 4) and `INT2` (pin 9) are **not routed** | ✅ correct, and now known to be *forced* rather than chosen |
-
-## B. Findings
-
-### 1. `Adafruit_TCA8418::begin()` discards every status it collects — **active, low severity**
-
-`src/utility/Adafruit_TCA8418/Adafruit_TCA8418.cpp:60-74`
-
-```cpp
-bool Adafruit_TCA8418::begin() {
-    bool ret = false;
-    ret = writeRegister8(TCA8418_REG_GPIO_DIR_1, 0x00);
-    ret = writeRegister8(TCA8418_REG_GPIO_DIR_2, 0x00);
-    ret = writeRegister8(TCA8418_REG_GPIO_DIR_3, 0x00);
-    ret = writeRegister8(TCA8418_REG_GPI_EM_1, 0xFF);
-    ret = writeRegister8(TCA8418_REG_GPI_EM_2, 0xFF);
-    ret = writeRegister8(TCA8418_REG_GPI_EM_3, 0xFF);
-    ...
-```
-
-`ret` is **assigned, never tested**. Only the last assignment survives to the return. A bus
-fault on any earlier write is silently discarded.
-
-`TCA8418.cpp:33` branches on that return value and prints an error, so the caller *believes* it
-is checking. **Practical consequence:** a partially-failed initialisation — the realistic case
-being marginal pull-ups or a contended bus — reports success and yields a keyboard that
-enumerates but behaves oddly. A wholly absent device still fails, because the final write also
-fails, which is why the severity is low rather than high.
-
-### 2. There is no device probe at all — **inert, but state it**
-
-The TCA8418 has no identification register, so `begin()` returning `true` means only "the last
-write was ACKed". The driver never reads back a register it has just written, which would be the
-cheap substitute. Not a defect; a limit on what "keyboard initialised OK" means.
-
-### 3. Two different values are written to `INT_STAT` — **inert**
-
-| Site | Write |
-|---|---|
-| `Adafruit_TCA8418.cpp:184` (`flush()`) | `writeRegister8(TCA8418_REG_INT_STAT, 3)` |
-| `TCA8418.cpp:61` (`update()`) | `writeRegister8(TCA8418_REG_INT_STAT, 1)` |
-
-`INT_STAT` is write-1-to-clear. `flush()` clears bits 0 and 1 (`K_INT`, `GPI_INT`); the steady-state
-`update()` path clears only bit 0. Per the vendored header, bit 3 is
-`TCA8418_REG_STAT_OVR_FLOW_INT (0x08)` and is **never cleared anywhere in the driver.**
-
-This is **inert as configured**: `enableInterrupts()` (`Adafruit_TCA8418.cpp:313-318`) sets only
-`GPI_IEN | KE_IEN` and leaves `OVR_FLOW_IEN (0x08)` alone, so an overflow can set the status bit
-but will not assert `INT`. The `_isr_flag` clear test at `TCA8418.cpp:63` reads
-`(intstat & 0x01) == 0`, which is consistent with clearing only bit 0. Nothing hangs.
-
-It becomes **active** the moment anyone enables the overflow interrupt: `OVR_FLOW_INT` would
-latch, `INT` would stay asserted, and `_isr_flag` would never clear — a hung keyboard. Flagged
-as a latent trap rather than a live bug.
-
-### 4. FIFO overflow is unobservable — **active, benign under normal typing**
-
-`update()` reads exactly **one** event per call (`_tca8418->getEvent()`,
-`Adafruit_TCA8418.cpp:162-166` → a single read of `KEY_EVENT_A`), then re-reads `INT_STAT` and
-leaves `_isr_flag` set if more events are pending. Draining therefore proceeds one event per
-`M5Cardputer.update()` iteration.
-
-The driver never reads `TCA8418_REG_KEY_LCK_EC (0x03)`, the event counter, and never sets
-`TCA8418_REG_CFG_OVR_FLOW_M (0x20)`, which selects the overflow policy. **Consequence:** on a
-burst longer than the controller's event FIFO, keystrokes are discarded and *nothing in the stack
-can tell that it happened.* For a 56-key device driven by human fingers this will essentially
-never fire; for macro playback, a key-rollover test, or a slow main loop, it is a real and
-silent loss path.
-
-### 5. `GPI_EM_1..3 = 0xFF` enables key events on pins that are not in the matrix — **inert, fragile**
-
-`begin()` marks **all** GPI pins as key-event sources before `matrix(7, 8)` narrows the keypad
-selection via `KP_GPIO_1..3`. `ROW7` (`U9` pin 1) is left as a GPIO with event reporting enabled
-and, per the schematic, **nothing connected to it**.
-
-It is inert because the part's unused row/column inputs sit at a defined level on their own.
-**This could not be verified against a datasheet — none is held here** — so the statement is
-that the board has shipped in this configuration without reports of phantom keys, which is
-evidence but not proof. The fragility is real: the configuration depends on silicon default
-behaviour rather than on anything the driver states.
-
-### 6. `attachInterruptArg(..., CHANGE)` on a level-latched, active-low output — **inert**
-
-`TCA8418.cpp:45`. `INT` is open-drain and asserted low until `INT_STAT` is cleared, so the
-meaningful edge is the falling one. `CHANGE` also fires on the release, setting `_isr_flag` a
-second time; `update()` then finds `INT_STAT` bit 0 already clear and simply drops the flag.
-Harmless, slightly wasteful, and worth knowing if you ever count interrupts.
-
----
-
-## C. Not a defect: three things that look wrong and are not
-
-- **`M5Unified` polls the BMI270 rather than using an interrupt.** Established above: the
-  interrupt lines do not exist on this board. The library is correct.
-- **`pinMode(INT, INPUT)` with no pull on an open-drain output.** Correct here, because `R37`
-  3.3 kΩ is fitted. On a board without it this exact line would be a live bug — so do **not**
-  copy this driver to another TCA8418 design without checking for the resistor.
-- **`matrix(7, 8)` when the symbol shows eight `ROW` pins.** The symbol has eight pin *names*;
-  only seven are netted. The driver matches the wiring, not the symbol.
-
-## D. Gap this audit exposes
-
-**No TCA8418 datasheet is retained in this repository.** Every register-semantics claim above
-rests on the vendored `Adafruit_TCA8418_registers.h` comments, which are secondary. Findings 3,
-4 and 5 would move from "argued" to "established" with TI `SCPS215` in
-`components/texas-instruments/tca8418/artifacts/`. Recorded as an acquisition target, not
-silently worked around.
diff --git a/devices/m5stack/cardputer-adv/examples/best.md b/devices/m5stack/cardputer-adv/examples/best.md
deleted file mode 100644
index a21486e..0000000
--- a/devices/m5stack/cardputer-adv/examples/best.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# Cardputer ADV — selected examples
-
-> Snapshot **2026-09-04**. Full candidate list: [`catalog.json`](catalog.json).
-> Discovery method and depth: [`search-log.md`](search-log.md).
-> **None of these was built or run by this session** — no toolchain, no hardware. Selection is
-> on inspection of source at a pinned commit, not on execution.
-
-## The portfolio
-
-Chosen so that between them they cover every major feature, at least two distinct
-implementation approaches, one integrated application, one diagnostic, and one useful negative.
-
-| # | Example | Covers | Why this one |
-|---|---|---|---|
-| **1** | `M5Cardputer/examples/Basic/keyboard/singlePress` + `multiPress` + `inputText` | keyboard | The minimal per-feature diagnostic. Three sizes of the same idea; `inputText` is the one to copy. Vendored. |
-| **2** | `M5Cardputer/examples/Basic/display` | display | Minimal M5GFX. Vendored. |
-| **3** | `M5Cardputer/examples/Basic/mic_wav_record` | mic + microSD + audio | The only vendor example that exercises **two** subsystems together, and the one that will expose the ES8311 enable defect if it exists on your unit. Vendored. |
-| **4** | `M5Cardputer/examples/Basic/ir_nec` | IR TX | Minimal RMT/IRremote. Vendored. |
-| **5** | `M5Cardputer/examples/Basic/sdcard` | microSD | Minimal SPI SD. Vendored. |
-| **6** | `M5Cardputer/examples/Basic/keyboard/usbKeyboard` | USB HID | Turns the device into a HID keyboard — the platform's signature trick. Vendored. |
-| **7** | `M5Cardputer/examples/UI/REPL` (`REPL.ino` + `ReplView.{h,cpp}`) | **integrated**: keyboard + display + text UI | The best-maintained integrated starting point. Added `9e9ad46`, 2025-09-01 — **the same day as the TCA8418 reader**, i.e. written *for* the ADV. Vendored. |
-| **8** | `M5Cardputer/examples/Advanced/SSHClient` | keyboard + display + Wi-Fi + a large dependency | Shows the RAM ceiling in practice. ⚠ needs `LibSSH-ESP32`, which `library.json` does **not** declare (only `library.properties` does). Vendored. |
-| **9** | `m5stack/M5Cardputer-UserDemo` @ `CardputerADV` `b549eac0` | **everything**, including IMU, LoRa CAP, GNSS, BLE HID | M5Stack's own full application, ESP-IDF. Not an "example" but the reference integration. `main/hal/hal_config.h` is the most compact authoritative pin list. **Build config vendored; full tree not.** |
-| **10** | `meshtastic/firmware` `variants/esp32s3/m5stack_cardputer_adv/` @ `be2f68b5` | CAP LoRa + GNSS + display + keyboard | **A second, independent implementation** of the same hardware by people who do not work at M5Stack. Its `variant.h` is why the G13/G15 question is settled. Not vendored — GPL-3.0, large. |
-| **11** | `BruceDevices/firmware` `boards/m5stack-cardputer/` @ `1d555e0d` | **runtime dual-generation support** | The only implementation that serves v1.x and ADV from one binary. Also a **negative example**: it copies M5Unified's ES8311 register-`0x01` divergence verbatim. Not vendored — AGPL-3.0. |
-| **12** | `geo-tp/M5-Card-Computer-I2C-Scanner` | diagnostic | Confirms `0x18`/`0x34`/`0x69` on the internal bus in ten seconds. MIT. Not vendored. |
-
-## Why these and not others
-
-* **Vendor examples first**, because they are MIT, small, versioned with the library that
-  autodetects your board, and they compile against exactly the API this record documents.
-* **The REPL example over a hello-world**, because its commit date proves it was written for the
-  ADV and it is the only vendor example that is a *program* rather than a demo.
-* **Meshtastic and Bruce included despite not being vendorable**, because independent
-  reimplementations are the strongest evidence a pin map is right. Three implementations agreeing
-  on `GPS_TX_PIN 13` is worth more than one vendor page.
-* **Bruce doubles as a negative example.** Copying a driver defect from upstream is exactly the
-  failure mode the skill's §10 audit exists to catch, and here it is, in the wild, in the most
-  popular firmware on the platform.
-
-## Not selected, and why
-
-| Candidate | Reason |
-|---|---|
-| `M5Cardputer/examples/Basic/button`, `buzzer`, `mic` | subsumed by #3 and #7 |
-| `bmorcelli/Launcher` | excellent documentation (`CardputerADV.md`), but the code is a boot menu; less instructive than Bruce as an integration |
-| Emulators, games, DAWs | large, single-purpose, and none exercises a feature the list above misses |
-| `Kezii/Rust-M5Stack-Cardputer` | a distinct and interesting approach, but GPL-3.0 and unmaintained-looking; noted in the catalog |
-| `echo-lalia/Cardputer-Micropython-Examples` | MicroPython route, but ADV support unconfirmed — cannot recommend it for this board |
-
-## Coverage check
-
-| Feature | Covered by |
-|---|---|
-| Keyboard | 1, 7, 9, 10, 11 |
-| Display | 2, 7, 9, 10, 11 |
-| Audio out | 9, 11 |
-| Audio in | 3, 9 |
-| microSD | 3, 5, 9, 11 |
-| **IMU** | **9 only** (`app_imu`) — thin |
-| Battery | 9, 11 |
-| Wi-Fi | 8, 11 |
-| BLE | 9 (BLE HID) |
-| IR | 4, 9, 11 |
-| Grove | 12 |
-| **CAP header** | 9, 10 |
-| USB HID | 6, 9 |
-| **RTC** | n/a — none fitted |
-
-**Uncovered:** no example anywhere exercises the **3.5 mm jack detect** (it is hardware-only and
-not software-visible), and IMU coverage rests on a single app inside a large ESP-IDF project.
-
-## Build status
-
-**All entries: `not-tested`.** No PlatformIO, no ESP-IDF and no hardware were available. The
-correct next step for anyone with a device is `pio run -e m5stack-cardputer` on #7 and
-`idf.py build` on #9, and to record the exact output — including failures — in
-[`../commands.md`](../commands.md).
diff --git a/devices/m5stack/cardputer-adv/examples/catalog.json b/devices/m5stack/cardputer-adv/examples/catalog.json
deleted file mode 100644
index 9d355df..0000000
--- a/devices/m5stack/cardputer-adv/examples/catalog.json
+++ /dev/null
@@ -1,575 +0,0 @@
-{
-  "schema": "hardware-doc/example-catalog/1",
-  "device": "devices/m5stack/cardputer-adv",
-  "snapshot": "2026-09-04",
-  "discovery": "gh search repos cardputer (100 = API cap); gh api search/code inside 5 named upstreams; vendor library examples/ directory at a pinned commit",
-  "build_environment": "none available - no PlatformIO, no ESP-IDF, no hardware. Every build_status is not-tested and that is a limitation of this pass, not of the examples.",
-  "counts": {
-    "catalogued": 25,
-    "selected": 14,
-    "vendored": 13,
-    "rejected_with_reason": 11
-  },
-  "examples": [
-    {
-      "id": "ex-kb-single",
-      "title": "M5Cardputer Basic/keyboard/singlePress",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/keyboard/singlePress",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "keyboard",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/singlePress",
-      "selected": true,
-      "notes": "minimal single-key read",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-kb-multi",
-      "title": "M5Cardputer Basic/keyboard/multiPress",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/keyboard/multiPress",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "keyboard",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/multiPress",
-      "selected": true,
-      "notes": "multi-key / rollover",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-kb-input",
-      "title": "M5Cardputer Basic/keyboard/inputText",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/keyboard/inputText",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "keyboard + display",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/inputText",
-      "selected": true,
-      "notes": "line editing; the one to copy",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-kb-usb",
-      "title": "M5Cardputer Basic/keyboard/usbKeyboard",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/keyboard/usbKeyboard",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "USB HID",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/keyboard/usbKeyboard",
-      "selected": true,
-      "notes": "native USB HID keyboard",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-display",
-      "title": "M5Cardputer Basic/display",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/display",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "display",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/display",
-      "selected": true,
-      "notes": "minimal M5GFX",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-button",
-      "title": "M5Cardputer Basic/button",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/button",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "G0 button",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/button",
-      "selected": false,
-      "notes": "minimal",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-buzzer",
-      "title": "M5Cardputer Basic/buzzer",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/buzzer",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "audio out",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/buzzer",
-      "selected": false,
-      "notes": "tone via Speaker_Class; on ADV this runs the ES8311 enable callback",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-mic",
-      "title": "M5Cardputer Basic/mic",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/mic",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "audio in",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic",
-      "selected": false,
-      "notes": "ES8311 ADC path on ADV",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-mic-wav",
-      "title": "M5Cardputer Basic/mic_wav_record",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/mic_wav_record",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "audio in + microSD",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/mic_wav_record",
-      "selected": true,
-      "notes": "two subsystems together",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-sdcard",
-      "title": "M5Cardputer Basic/sdcard",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/sdcard",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "microSD",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/sdcard",
-      "selected": true,
-      "notes": "minimal SPI SD",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-ir",
-      "title": "M5Cardputer Basic/ir_nec",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Basic/ir_nec",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "IR TX",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Basic/ir_nec",
-      "selected": true,
-      "notes": "RMT/IRremote NEC",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-repl",
-      "title": "M5Cardputer UI/REPL",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/UI/REPL",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "keyboard + display + text UI",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/UI/REPL",
-      "selected": true,
-      "notes": "integrated; added the same day as the TCA8418 reader",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-ssh",
-      "title": "M5Cardputer Advanced/SSHClient",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer",
-      "permalink": "https://github.com/m5stack/M5Cardputer/tree/f1392858b9994c3547120e602a57d3553d16ab01/examples/Advanced/SSHClient",
-      "commit": "f1392858b9994c3547120e602a57d3553d16ab01",
-      "release": "1.1.1",
-      "last_activity": "2026-07-21",
-      "features": "keyboard + display + Wi-Fi + LibSSH",
-      "dependencies": "M5Cardputer 1.1.1, M5Unified, M5GFX, IRremote, LibSSH-ESP32",
-      "license": "MIT",
-      "license_evidence": "SPDX headers",
-      "vendored": true,
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-f1392858/examples/Advanced/SSHClient",
-      "selected": true,
-      "notes": "exposes the RAM ceiling; dependency declared only in library.properties",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-userdemo-adv",
-      "title": "M5Cardputer-UserDemo (CardputerADV branch)",
-      "author": "M5Stack",
-      "source_class": "primary",
-      "url": "https://github.com/m5stack/M5Cardputer-UserDemo/tree/CardputerADV",
-      "permalink": "https://github.com/m5stack/M5Cardputer-UserDemo/tree/b549eac0a3c65bc108186c276b8fac0a214aaa4e",
-      "commit": "b549eac0a3c65bc108186c276b8fac0a214aaa4e",
-      "last_activity": "2026-06-08",
-      "release": null,
-      "framework": "ESP-IDF 5.4.2",
-      "features": "keyboard, display, audio, microSD, IMU, IR, BLE HID, USB HID, CAP LoRa + GNSS, Wi-Fi scan",
-      "dependencies": "M5GFX@0.2.15, M5Unified@0.2.10, mooncake@v2.2.0, mooncake_log@v1.3.0, smooth_ui_toolkit@v2.4.0 (pinned, all older than current heads); esp-now@2.5.2; RadioLib (vendored)",
-      "license": "MIT",
-      "license_evidence": "LICENSE + SPDX headers",
-      "license_caveat": "pins/vendors RadioLib, LGPL-3.0 upstream",
-      "vendored": "partial",
-      "vendored_path": "artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/",
-      "selected": true,
-      "notes": "Reference integration. hal_config.h is the most compact authoritative ADV pin list; uart_helper.c settles the G13/G15 direction question.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-meshtastic-adv",
-      "title": "Meshtastic m5stack-cardputer-adv variant",
-      "author": "Meshtastic",
-      "source_class": "community",
-      "url": "https://github.com/meshtastic/firmware",
-      "permalink": "https://github.com/meshtastic/firmware/tree/be2f68b5af806332c9d877d1643007771bd10c36/variants/esp32s3/m5stack_cardputer_adv",
-      "commit": "be2f68b5af806332c9d877d1643007771bd10c36",
-      "last_activity": "2026-09-03",
-      "features": "CAP LoRa SX1262, GNSS, display, keyboard, ES8311",
-      "dependencies": "meshtastic/st7789@92bae2e4, pschatzmann/arduino-audio-driver@v0.3.0, meshtastic/ESP8266Audio@34302463, earlephilhower/ESP8266SAM@1.1.0",
-      "license": "GPL-3.0",
-      "vendored": false,
-      "selected": true,
-      "notes": "Independent reimplementation. variant.h is the third source confirming GPS_TX_PIN 13 / GPS_RX_PIN 15. Not vendored: GPL-3.0 and large.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-bruce-cardputer",
-      "title": "Bruce boards/m5stack-cardputer",
-      "author": "BruceDevices",
-      "source_class": "community",
-      "url": "https://github.com/BruceDevices/firmware",
-      "permalink": "https://github.com/BruceDevices/firmware/tree/1d555e0d5b201cc91ad201ac40c2482ec00d1ac1/boards/m5stack-cardputer",
-      "commit": "1d555e0d5b201cc91ad201ac40c2482ec00d1ac1",
-      "last_activity": "2026-08-28",
-      "features": "runtime v1.x/ADV detection, TCA8418, ES8311, IR, RF, CC1101, NRF24, W5500, LoRa, USB HID",
-      "dependencies": "adafruit/Adafruit TCA8418@^1.0.2, TFT_eSPI, LiteLED@^1.2.0",
-      "license": "AGPL-3.0",
-      "vendored": false,
-      "selected": true,
-      "notes": "Also a NEGATIVE example: copies M5Unified's ES8311 register 0x01 divergence verbatim, and polls the keyboard at ~100 ms instead of using the interrupt.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "tool-i2c-scanner",
-      "title": "M5-Card-Computer-I2C-Scanner",
-      "author": "geo-tp",
-      "source_class": "community",
-      "url": "https://github.com/geo-tp/M5-Card-Computer-I2C-Scanner",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-08-07",
-      "features": "diagnostic: internal I2C bus",
-      "license": "MIT",
-      "vendored": false,
-      "selected": true,
-      "notes": "Confirms 0x18 / 0x34 / 0x69. Commit not pinned in this pass.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-launcher",
-      "title": "Launcher (formerly M5Stick-Launcher)",
-      "author": "bmorcelli",
-      "source_class": "community",
-      "url": "https://github.com/bmorcelli/Launcher",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "MIT",
-      "vendored": false,
-      "selected": false,
-      "notes": "Excellent CardputerADV.md, but the code is a boot menu; Bruce is more instructive as an integration. Note: its docs invert the 0x18/0x69 identities.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-marauder",
-      "title": "ESP32Marauder",
-      "author": "justcallmekoko",
-      "source_class": "community",
-      "url": "https://github.com/justcallmekoko/ESP32Marauder",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "none declared",
-      "vendored": false,
-      "selected": false,
-      "notes": "Has User_Setup_marauder_m5cardputer_adv.h, so ADV is supported; Arduino-IDE project, no PlatformIO env to cite.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-nemo",
-      "title": "m5stick-nemo",
-      "author": "n0xa",
-      "source_class": "community",
-      "url": "https://github.com/n0xa/m5stick-nemo",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "NOASSERTION",
-      "vendored": false,
-      "selected": false,
-      "notes": "REJECTED as an example: no ADV config exists. Retained in the catalog as a useful negative.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-evil",
-      "title": "Evil-M5Project",
-      "author": "7h30th3r0n3",
-      "source_class": "community",
-      "url": "https://github.com/7h30th3r0n3/Evil-M5Project",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "none",
-      "vendored": false,
-      "selected": false,
-      "notes": "REJECTED: ADV support not established; no licence file.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-microhydra",
-      "title": "MicroHydra",
-      "author": "echo-lalia",
-      "source_class": "community",
-      "url": "https://github.com/echo-lalia/MicroHydra",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "GPL-3.0",
-      "vendored": false,
-      "selected": false,
-      "notes": "MicroPython route; ADV support unconfirmed, so not recommendable for this board.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-rust",
-      "title": "Rust-M5Stack-Cardputer",
-      "author": "Kezii",
-      "source_class": "community",
-      "url": "https://github.com/Kezii/Rust-M5Stack-Cardputer",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "GPL-3.0",
-      "vendored": false,
-      "selected": false,
-      "notes": "Distinct approach (Rust HAL); not selected on maintenance grounds.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "ex-mpy",
-      "title": "Cardputer-Micropython-Examples",
-      "author": "echo-lalia",
-      "source_class": "community",
-      "url": "https://github.com/echo-lalia/Cardputer-Micropython-Examples",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "MIT",
-      "vendored": false,
-      "selected": false,
-      "notes": "ADV support unconfirmed.",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    },
-    {
-      "id": "fw-plai",
-      "title": "plai",
-      "author": "d4rkmen",
-      "source_class": "community",
-      "url": "https://github.com/d4rkmen/plai",
-      "permalink": null,
-      "commit": null,
-      "last_activity": "2026-09-04 (metadata)",
-      "features": "varies",
-      "license": "GPL-3.0",
-      "vendored": false,
-      "selected": false,
-      "notes": "ADV-only Meshtastic client. Not selected as an example, but it carries the best firsthand user reports (working 2026-08-05; arrow-key regression 2026-08-29).",
-      "build_status": "not-tested",
-      "run_status": "not-tested",
-      "test_environment": null,
-      "device": "M5Stack Cardputer ADV (K132-Adv)",
-      "retrieved": "2026-09-04"
-    }
-  ]
-}
diff --git a/devices/m5stack/cardputer-adv/examples/search-log.md b/devices/m5stack/cardputer-adv/examples/search-log.md
deleted file mode 100644
index fb21781..0000000
--- a/devices/m5stack/cardputer-adv/examples/search-log.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# Cardputer ADV — example search log
-
-> **2026-09-04.** Declared depth and exclusions at the end.
-
-## Sources searched
-
-| Source | Query / path | Depth | Useful | Notes |
-|---|---|---|---|---|
-| Vendor library | `M5Cardputer/examples/**` at `f1392858` | full tree, 13 sketches | **13** | all MIT, all vendored |
-| Vendor firmware | `M5Cardputer-UserDemo` branches | `main` + **`CardputerADV`** | 2 | ADV code is on a **branch**, easy to miss |
-| GitHub repo search | `gh search repos cardputer --limit 100` | 100 = **API cap** | ~40 catalogued in [`../projects-and-community.md`](../projects-and-community.md) | true count is higher |
-| GitHub repo search | `M5Stick-Launcher`, `marauder cardputer`, `nemo esp32`, `M5Launcher` | 12 each | mixed | **two of the four returned false negatives** — see below |
-| GitHub code search | `repo:{justcallmekoko/ESP32Marauder, n0xa/m5stick-nemo, meshtastic/firmware} cardputer` | full | 17 / 15 / 9 files | **this is what repo search missed** |
-| GitHub contents API | `boards/`, `variants/`, `configs/` in five upstreams | one level, then drill | — | see the two directory-depth traps below |
-| raw.githubusercontent | 6 build configs at `HEAD` | — | 6 | no auth, no rate limit |
-| Reddit | 3 searches + 4 comment threads | ~75 threads reviewed | ~12 quoted | project announcements are a *primary* discovery channel here |
-| Awesome-lists | `terremoth/awesome-m5stack-cardputer`, `ru84r8/Cardputer-firmware-list` | noted, **not mined** | — | **gap** — a further pass should walk both |
-
-## Traps hit, in order
-
-1. **`gh search repos "marauder cardputer"` → 0 results.** Marauder *does* support the ADV;
-   `gh api search/code -f q='repo:justcallmekoko/ESP32Marauder cardputer'` returns 17 files
-   including `User_Setup_marauder_m5cardputer_adv.h`. **Repo search matches metadata, not
-   content.** Same false negative for NEMO.
-2. **`gh api repos/meshtastic/firmware/contents/variants | grep card` → nothing.** The variant is
-   at `variants/**esp32s3**/m5stack_cardputer_adv/`. Listing one directory level is not a search.
-3. **`boards/m5stack-cardputer.ini` → 404.** In Bruce it is a *directory*:
-   `boards/m5stack-cardputer/m5stack-cardputer.ini`, alongside `interface.cpp` and
-   `pins_arduino.h`. List before guessing.
-4. **Two renames.** `pr3y/Bruce` → `BruceDevices/firmware`; `bmorcelli/M5Stick-Launcher` →
-   `bmorcelli/Launcher`. The GitHub API follows the redirect silently, so `gh api repos/{old}`
-   still works — but a repository *search* for the old name finds only derivatives. Resolve
-   canonical names before concluding a project is dead.
-5. **The ADV firmware is a branch, not a repo.** `M5Cardputer-UserDemo` `main` is the v1.x
-   firmware. Checking only the default branch would have missed the entire ADV application.
-
-## Result disposition
-
-| Status | Count |
-|---|---|
-| Catalogued | **25** |
-| Selected | 14 |
-| Vendored | 13 (all MIT, all from the vendor library) |
-| Rejected with a stated reason | 11 |
-| **Built or run** | **0** — no toolchain, no hardware |
-
-## Not searched
-
-* PlatformIO registry, Arduino Library Manager
-* Hackster.io, Hackaday.io, Instructables
-* YouTube (several projects are announced there first)
-* M5Stack's own forum — **auth-walled**, no determination possible
-* Chinese- and Japanese-language ecosystems. Several prolific Cardputer authors are Japanese
-  (`shikarunochi`, `GOROman`, `Gitshaoxiang`) and at least two projects are Chinese-language
-  (`fwz233-RE/M5Claw`, `nongxl/SkyCompass_CardputerADV`, `CCP101/cardputer-recoverable-multiboot`).
-  **This is the largest single gap in the example survey.**
-* The two curated awesome-lists, which almost certainly contain projects GitHub's 100-result cap
-  hid.
-
-## Stopping criterion
-
-Stopped when the vendor's own example tree was exhausted, the five named upstreams had each been
-resolved to a concrete build target or a stated negative, and GitHub repo search had hit its cap
-with the last two query families returning only forks and duplicates. **Not** a completeness
-claim — the exclusions above are real and enumerated.
diff --git a/devices/m5stack/cardputer-adv/factory-firmware.md b/devices/m5stack/cardputer-adv/factory-firmware.md
deleted file mode 100644
index dc4bd09..0000000
--- a/devices/m5stack/cardputer-adv/factory-firmware.md
+++ /dev/null
@@ -1,149 +0,0 @@
-# Cardputer ADV — factory firmware
-
-> Snapshot **2026-09-04**. **No firmware binary was downloaded or parsed in this pass** — this
-> record is built from the published source, build configuration and partition table. Where a
-> binary would settle something, that is called out as a gap.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Repository | `github.com/m5stack/M5Cardputer-UserDemo` |
-| **Branch for the ADV** | **`CardputerADV`** — the ADV firmware is a *branch*, not the default |
-| Commit at snapshot | **`b549eac0a3c65bc108186c276b8fac0a214aaa4e`**, 2026-06-08, *"Merge pull request #40 from wdoekes/feat/CardputerADV-improve-boot-ux"* |
-| `main` branch (v1.0/v1.1) | `a34d7ebcd508fb903a2b1123be8c8b54abd55d07`, 2026-07-17 |
-| Licence | **MIT** (repository), ⚠ vendors/pins **RadioLib** which is **LGPL-3.0** upstream |
-| Framework | **ESP-IDF 5.4.2** (from the generated `sdkconfig.defaults` header) |
-| Target | `esp32s3`, 8 MB flash |
-| Stars | ★343 |
-
-The ADV image is *not* built from `main`. Anyone diffing the two branches is looking at the real
-generational delta in M5Stack's own application code.
-
-## Partition table
-
-`partitions.csv`, verbatim:
-
-```
-# Name,   Type, SubType, Offset,  Size, Flags
-nvs,      data, nvs,     0x9000,  0x4000,
-otadata,  data, ota,     0xd000,  0x2000,
-phy_init, data, phy,     0xf000,  0x1000,
-factory,  app,  factory, 0x10000, 4M,
-```
-
-Observations:
-
-* **A single `factory` app slot and no OTA slots**, despite an `otadata` partition existing.
-  Over-the-air update is not possible with this layout.
-* **4 MB of 8 MB is allocated.** Roughly 3.9 MB is unclaimed — which is exactly the room the
-  community's memory-mapped-font trick uses (see [`projects-and-community.md`](projects-and-community.md)).
-* Application base offset **`0x10000`**.
-
-## Build configuration
-
-`sdkconfig.defaults` (generated by `idf.py save-defconfig`), the load-bearing lines:
-
-```
-CONFIG_IDF_TARGET="esp32s3"
-CONFIG_ESPTOOLPY_FLASHSIZE_8MB=y
-CONFIG_PARTITION_TABLE_CUSTOM=y
-CONFIG_EXAMPLE_KBD_ENABLE=y
-CONFIG_BT_ENABLED=y
-CONFIG_BT_NIMBLE_ENABLED=y
-CONFIG_BT_NIMBLE_SM_LVL=2
-CONFIG_BT_NIMBLE_NVS_PERSIST=y
-CONFIG_BT_NIMBLE_SVC_GAP_DEVICE_NAME="CardputerADV Keyboard"
-CONFIG_BT_NIMBLE_SVC_BAS_BATTERY_LEVEL_NOTIFY=y
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_MIN_CONN_INTERVAL=12
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_MAX_CONN_INTERVAL=48
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_SLAVE_LATENCY=8
-CONFIG_BT_NIMBLE_SVC_GAP_PPCP_SUPERVISION_TMO=600
-CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_240=y
-```
-
-So the shipped image is a **BLE HID keyboard** advertising as `"CardputerADV Keyboard"`, with
-battery-level notification, security level 2, and connection parameters tuned for HID latency.
-NimBLE rather than Bluedroid — the right choice on a part with 512 KB and no PSRAM.
-
-## Application structure
-
-```
-main/
-├── hal/
-│   ├── hal_config.h                 ← the compact authoritative ADV pin list
-│   ├── keyboard/
-│   ├── cap_lora868/                 ← M5Stack's own SX1262 + GNSS integration
-│   │   ├── radio_lib/EspHal.h       ← vendored RadioLib HAL  ⚠ LGPL-3.0 upstream
-│   │   ├── TinyGPSPlus/
-│   │   └── uart/uart_helper.c       ← settles the G13/G15 TX/RX question
-│   └── utils/{ir_nec, ble_hid_device, tusb_hid_device, adafruit_tca8418, settings}
-├── apps/
-│   ├── app_launcher/  app_wifi_scan/  app_imu/  app_chat/
-│   ├── app_lora_chat/ app_record/     app_stringir_toolkit/  …
-└── assets/
-```
-
-The app list is itself informative: `app_imu` and `app_lora_chat` exist only because the ADV has
-an IMU and a CAP header; `app_record` exercises the ES8311 ADC path.
-
-`hal_config.h` in full:
-
-```c
-#define HAL_PIN_KEYBOARD_INT   11
-#define HAL_PIN_IR_TX          44
-#define HAL_PIN_SPI_MISO       GPIO_NUM_39
-#define HAL_PIN_SPI_MOSI       GPIO_NUM_14
-#define HAL_PIN_SPI_SCLK       GPIO_NUM_40
-#define HAL_PIN_SD_CARD_CS     GPIO_NUM_12
-#define HAL_PIN_GPS_TX         GPIO_NUM_13
-#define HAL_PIN_GPS_RX         GPIO_NUM_15
-#define HAL_PIN_LORA_NSS_GPIO  5
-#define HAL_PIN_LORA_RST_GPIO  3
-#define HAL_PIN_LORA_BUSY_GPIO 6
-#define HAL_PIN_LORA_DIO1_GPIO 4
-```
-
-Retained at
-[`artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/`](artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/).
-
-## ⚠ The dependency pins are stale
-
-`repos.json` clones `M5GFX` at branch **`0.2.15`** and `M5Unified` at branch **`0.2.10`**, both
-older than the current heads (`d91077b9`, `8530f537`). The shipped firmware therefore does not
-correspond to any current checkout of those libraries. Diffing the pins against `HEAD` is the
-correct move when the factory image behaves differently from your build — it is how the
-PaperMono pass found an M5GFX waveform change, and the same discipline applies here.
-
-## Getting the binary
-
-Two published routes, **neither exercised in this pass**:
-
-1. **EasyLoader** — `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Easy_Loader_for_Cardputer-Adv.exe`
-   (a Windows self-extracting flasher; the PaperMono pass established that these are named
-   `<SKU>-…_0x00.exe` and contain the image plus esptool).
-2. **M5Burner API** — `burner.m5stack.com/api/v1/firmwares/{id}` and
-   `/versions/{vid}/download`. Per [`vendors/m5stack`](../../../vendors/m5stack/README.md) §4
-   the `/api/v1` prefix is public while `/api` returns 401. **No firmware id was resolved for
-   the Cardputer ADV in this pass** — that is the main gap in this file.
-
-With a binary in hand, the useful things to extract are `esp_app_desc_t` at **`0x10020`**
-(`project_name`, `app_version`, `build_date`/`time`, `idf_version`) and the partition table at
-`0x8000`. `hardware-doc/tools/esp_image_info.py` does this.
-
-## Recovery
-
-Re-flash over USB in download mode (switch OFF → hold G0 → power → release). There is no OTA
-slot and no factory-reset button. The `nvs` partition at `0x9000` holds settings; erasing it
-resets configuration without touching the application.
-
-## Evidence status
-
-| Claim | Status |
-|---|---|
-| Branch, commit, licence, IDF version | **official** — repository at a pinned commit |
-| Partition table, sdkconfig, pin list | **official** — files quoted verbatim |
-| Stale dependency pins | **derived** — `repos.json` compared to current heads on 2026-09-04 |
-| Flash offsets for a manual esptool invocation | **inferred** from the partition table; **not verified against a binary** |
-| Image hash, build date, app version | **unknown — no binary retrieved** |
-| RadioLib licence conflict | **flagged, unresolved** |
diff --git a/devices/m5stack/cardputer-adv/features/README.md b/devices/m5stack/cardputer-adv/features/README.md
deleted file mode 100644
index b31d35c..0000000
--- a/devices/m5stack/cardputer-adv/features/README.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# Cardputer ADV — feature guides
-
-Task-oriented guides. Each answers a natural question, names the exact hardware path,
-the software options, the resources consumed and the ways it fails.
-
-| Guide | Question it answers | Hardware |
-|---|---|---|
-| [`keyboard.md`](keyboard.md) | How do I read the keyboard? | TCA8418RTWR @ I²C `0x34`, INT G11 |
-| [`display.md`](display.md) | How do I draw on the screen and dim it? | ST7789V2, SPI3, backlight G38 |
-| [`audio.md`](audio.md) | How do I play sound and record? | ES8311 `0x18` + NS4150B + MEMS mic + 3.5 mm jack |
-| [`microsd.md`](microsd.md) | How do I use the SD card? | SPI G40/G14/G39, CS G12 |
-| [`imu.md`](imu.md) | How do I read motion? | BMI270 @ I²C `0x69` |
-| [`rtc.md`](rtc.md) | How do I keep the time? | **there is no RTC** — read this before designing around one |
-| [`battery-and-power.md`](battery-and-power.md) | How do I read the battery and charge safely? | ADC G10, TP4057, SY7088/SY8089 |
-| [`wifi-and-ble.md`](wifi-and-ble.md) | How do I use Wi-Fi and BLE? | ESP32-S3 radio, Stamp-S3A antenna |
-| [`ir.md`](ir.md) | How do I send IR? | emitter on G44, **TX only** |
-| [`grove-port.md`](grove-port.md) | How do I attach a Grove sensor? | HY2.0-4P, G1/G2, external I²C |
-| [`cap-header.md`](cap-header.md) | How do I use or build a CAP board? | EXT 2.54-14P, P3 |
-| [`usb.md`](usb.md) | How do I flash it, or make it a HID keyboard? | native USB-OTG on the Stamp |
-
-Cross-cutting contention between these lives in
-[`../resources-and-conflicts.md`](../resources-and-conflicts.md); which of them work on which
-Cardputer revision lives in [`../compatibility-and-status.md`](../compatibility-and-status.md).
diff --git a/devices/m5stack/cardputer-adv/features/audio.md b/devices/m5stack/cardputer-adv/features/audio.md
deleted file mode 100644
index bed11b6..0000000
--- a/devices/m5stack/cardputer-adv/features/audio.md
+++ /dev/null
@@ -1,239 +0,0 @@
-# Cardputer ADV — audio in and out
-
-> **Question answered:** *"How do I play sound and record audio on a Cardputer ADV?"*
-> Applies to **Cardputer ADV only**. The v1.0/v1.1 path (NS4168 + SPM1423 PDM) is different and
-> simpler. Last verified **2026-09-04**. **Contains a live driver defect — read §6.**
-
-## 1. The hardware path
-
-```
-                        ┌──────────── ES8311 (U6, I²C 0x18) ────────────┐
-  MSM381A3729H9BP  ──►  │ MIC1P/MIC1N → PGA → ADC → ASDOUT ──► G46      │
-  (U8, analog MEMS)     │                                              │
-                        │  G42 ──► DSDIN → DAC → OUTP/OUTN ──┬─► NS4150B (U5) ─► 8 Ω 1 W speaker
-  G41 ──► SCLK (BCLK)   │                                    └─► DAC_P ─► PJ-342 3.5 mm jack (J7)
-  G43 ──► LRCK          │                                              │
-  G8/G9 ──► CDATA/CCLK  └──────────────────────────────────────────────┘
-                                        HP_DET ─► Q4 2N7002T ─► AMP_EN ─► NS4150B CTRL
-```
-
-| Part | Designator | Role | Record |
-|---|---|---|---|
-| ES8311 | U6 | codec, I²C `0x18`, I²S slave | [`everest-semiconductor/es8311`](../../../../components/everest-semiconductor/es8311/README.md) |
-| NS4150B | U5 | mono class-D, `CTRL` = `AMP_EN` | [`nsiway/ns4150b`](../../../../components/nsiway/ns4150b/README.md) |
-| MSM381A3729H9BP | U8 | analog MEMS mic, SNR 65 dB | [`memsensing/msm381a3729h9bp`](../../../../components/memsensing/msm381a3729h9bp/README.md) |
-| PJ-342 | J7 | 3.5 mm jack with detect | [`generic/3.5mm-audio-output`](../../../../components/generic/3.5mm-audio-output/README.md) |
-| 2N7002T | Q4 | `HP_DET` → `AMP_EN` inversion | — |
-
-Supporting parts read off sheet 3: FB1/FB2/FB3 ferrites on the speaker outputs, R16/R17
-100 k 1 % and R23 10 k 1 % around the amplifier inputs, R24 33 R on `AVDD`, R39 10 R, R40 1 k,
-R42 1 k and D3 `1N4148WT` in the headphone-detect network, C13–C33 decoupling.
-
-**There is no MCLK line.** G45 is unwired; Meshtastic declares `DAC_I2S_MCLK 45 // dummy`.
-The codec must be told to derive its master clock from BCLK.
-
-## 2. Pin table
-
-| Signal | GPIO | ES8311 pin |
-|---|---|---|
-| I²C `CCLK` (SCL) | G9 | 1 |
-| I²C `CDATA` (SDA) | G8 | 19 |
-| I²S `BCLK` | G41 | 6 `SCLK/DMIC_SCL` |
-| I²S `LRCK` | G43 | 8 |
-| I²S `DSDIN` (host → codec) | G42 | 9 |
-| I²S `ASDOUT` (codec → host) | G46 | 7 |
-| Port | `I2S_NUM_1` | — |
-
-The v1.x used the **same four I²S pins** (G41/G43/G42 for the NS4168, G46/G43 for the PDM mic)
-— which is why so much v1.x audio code half-works on an ADV: the pins are right and the codec
-is simply never initialised, so nothing comes out.
-
-## 3. Minimal procedure — Arduino / M5Unified
-
-M5Unified does everything, including the codec:
-
-```cpp
-#include <M5Cardputer.h>
-
-void setup() {
-  auto cfg = M5.config();
-  cfg.internal_spk = true;
-  cfg.internal_mic = true;
-  M5Cardputer.begin(cfg, true);
-  M5Cardputer.Speaker.setVolume(128);
-}
-
-void loop() {
-  M5Cardputer.Speaker.tone(880, 200);   // enabling the speaker runs the ES8311 init
-  delay(1000);
-}
-```
-
-`M5Unified` sets, for `board_M5CardputerADV`:
-
-```cpp
-spk_cfg.pin_bck = GPIO_NUM_41; spk_cfg.pin_ws = GPIO_NUM_43;
-spk_cfg.pin_data_out = GPIO_NUM_42; spk_cfg.magnification = 16;
-spk_cfg.i2s_port = I2S_NUM_1;
-spk_enable_cb = _speaker_enabled_cb_cardputer_adv;      // M5Unified.cpp:3018-3031
-
-mic_cfg.pin_data_in = GPIO_NUM_46; mic_cfg.pin_ws = GPIO_NUM_43;
-mic_cfg.pin_bck = GPIO_NUM_41;
-mic_enable_cb = _microphone_enabled_cb_cardputer_adv;   // M5Unified.cpp:2672-2680
-```
-
-Note `mic_cfg.pin_bck` is set on the ADV and **not** on the v1.x — the PDM mic needed only a
-clock and a data line; the codec needs a full I²S frame.
-
-## 4. Working examples
-
-* `M5Cardputer/examples/Basic/buzzer` and `Basic/mic`, `Basic/mic_wav_record` — vendored at
-  [`../artifacts/source-snapshots/M5Cardputer-f1392858/examples/`](../artifacts/source-snapshots/M5Cardputer-f1392858/examples/).
-  Written for the v1.x; they exercise the same M5Unified API and therefore work on the ADV
-  through the callbacks.
-* `AndyAiCardputer/mp3-player-winamp-cardputer-adv` — explicitly "with ES8311 audio codec support".
-* `halbeshuhn/Cardputer-WebRadio`, `wusiu/WebRadio_WuSiU_Cardputer_Adv` — streaming decode.
-* `urtubia/miniacid`, `CHARL3X/GLIDE-Synth-Cardputer-ADV` — synthesis, i.e. sustained
-  low-latency output.
-* Meshtastic pulls `pschatzmann/arduino-audio-driver@v0.3.0` for the ADV variant, which is a
-  third independent ES8311 implementation if you want to compare.
-
-## 5. Alternatives
-
-| Approach | When | Notes |
-|---|---|---|
-| `M5Unified` `Speaker_Class`/`Mic_Class` | default | handles codec enable/disable, mixing, WAV |
-| `pschatzmann/arduino-audio-driver` | you want a maintained standalone ES8311 driver | what Meshtastic uses |
-| Raw `driver/i2s_std.h` + your own I²C writes | full control over sample format and codec registers | you must implement the enable sequence yourself; see §6 for what *not* to copy |
-| ESP-ADF | full audio pipeline | heavy for 512 KB with no PSRAM |
-
-## 6. ⚠ Vendor driver audit — ES8311 enable callbacks
-
-Read side by side with the ES8311 register map. Two findings; the second is a live bug.
-
-### 6.1 The two callbacks disagree about register `0x01`
-
-[`M5Unified.cpp:1000-1023`](https://github.com/m5stack/M5Unified/blob/8530f5377d782e4a25a6c482de2e71c3f75ca8eb/src/M5Unified.cpp#L1000-L1023) — speaker enable:
-
-```c
-2, 0x00, 0x80,  // RESET / CSM POWER ON
-2, 0x01, 0xB5,  // CLOCK_MANAGER / MCLK=BCLK
-2, 0x02, 0x18,  // CLOCK_MANAGER / MULT_PRE=3
-2, 0x0D, 0x01,  // SYSTEM / power up analog
-2, 0x12, 0x00,  // SYSTEM / power-up DAC      - NOT default
-2, 0x13, 0x10,  // SYSTEM / enable HP drive   - NOT default
-2, 0x32, 0xBF,  // DAC volume (0 dB)
-2, 0x37, 0x08,  // bypass DAC equaliser       - NOT default
-```
-
-[`M5Unified.cpp:1481-1507`](https://github.com/m5stack/M5Unified/blob/8530f5377d782e4a25a6c482de2e71c3f75ca8eb/src/M5Unified.cpp#L1481-L1507) — microphone enable:
-
-```c
-2, 0x00, 0x80,
-2, 0x01, 0xBA,  // CLOCK_MANAGER / MCLK=BCLK     ← 0xBA, not 0xB5
-2, 0x02, 0x18,
-2, 0x0D, 0x01,
-2, 0x0E, 0x02,  // enable analog PGA + ADC modulator
-2, 0x14, 0x10,  // Mic1p-Mic1n, PGA gain minimum
-2, 0x17, 0xBF,  // ADC volume 0 dB
-2, 0x1C, 0x6A,  // ADC EQ bypass, DC-offset cancel
-```
-
-`0x01` is one clock-manager register on one shared codec. `0xB5` and `0xBA` differ in the low
-nibble — the ADC/DAC clock-divider select field. **Whichever subsystem is enabled last wins**,
-and the other runs on a divider it did not ask for. Severity: *latent*, because both values
-enable both clock trees and the audible effect at 16 kHz mono is small — but it means
-speaker-then-mic and mic-then-speaker are not equivalent, which is exactly the kind of thing
-that produces "it only works if I start the mic first" bug reports.
-
-### 6.2 ⚠ Disabling the microphone powers down the codec, silencing the speaker
-
-The microphone's `disabled_bulk_data`:
-
-```c
-2, 0x0D, 0xFC,  // SYSTEM / power down analog circuitry
-2, 0x0E, 0x6A,
-2, 0x00, 0x00,  // RESET / CSM POWER DOWN        ← powers down the whole chip
-```
-
-The speaker's `disabled_bulk_data` is **empty** (`{ 0 }` — a zero-length command list).
-
-So:
-
-* `Mic.end()` (or any M5Unified path that disables the mic) executes **`0x00 = 0x00`, CSM power
-  down**, on the codec that is also driving the speaker. Any speaker output in flight stops and
-  will not resume until something re-runs the speaker enable sequence.
-* Conversely `Speaker.end()` does nothing at all — the codec stays fully powered, analog
-  circuitry live. That is a **standby-current cost that the vendor's own 0.23 µA figure does
-  not include**, because that figure is measured with the power switch OFF.
-
-**Status: active defect**, present at `M5Unified` `8530f537` (2026-08-27). It is a genuine
-cross-subsystem interaction, not a theoretical one: M5Unified auto-toggles enable state when
-you alternate `Speaker` and `Mic` use, which is exactly what a voice-recorder or a
-push-to-talk app does.
-
-**Workaround:** after any microphone teardown, force a speaker re-enable
-(`M5.Speaker.end(); M5.Speaker.begin();`) before playing again, or drive the codec yourself and
-never call the vendor disable path.
-
-**Not filed upstream by this session.**
-
-### 6.3 What the driver never touches
-
-Neither callback reads any ES8311 status or fault register, and neither reads the chip ID
-(`0xFD`/`0xFE`) to confirm a codec is actually present. On a board where the codec is the only
-audio path, a silent I²C failure produces silence with no diagnostic. Bruce's port
-(`boards/m5stack-cardputer/interface.cpp:491-527`) copies the same sequences verbatim,
-including the register-`0x01` divergence — so the defect has already propagated to the largest
-third-party firmware.
-
-## 7. The headphone jack and the speaker mute
-
-M5Stack states: *"When a 3.5 mm headphone jack is inserted, the speaker amplifier will be
-disabled."* The mechanism on sheet 3 is `HP_DET` from the PJ-342's switch contact, through
-D3 (`1N4148WT`) and Q4 (`2N7002T`) with R40/R42 1 k, producing `AMP_EN` into the NS4150B's
-`CTRL` pin. It is **hardware, not firmware** — no GPIO participates, and there is no way for
-software to read jack-insertion state or to override the mute.
-
-Contrast the CardputerZero, which routes `HP_DET` to a CPU GPIO (`G17`) and enables its
-amplifier from `G24`. The ADV gives up that flexibility for pin count.
-
-## 8. Resources and conflicts
-
-| Resource | Used | Conflicts |
-|---|---|---|
-| `I2S_NUM_1` | speaker **and** mic | `I2S_NUM_0` is free; you cannot easily run them as two independent ports because there is one codec |
-| G41, G42, G43, G46 | dedicated | none |
-| I²C `0x18` | ES8311 | shares the bus with TCA8418 `0x34` and BMI270 `0x69` |
-| CPU | software mixing in `Speaker_Class` | at 240 MHz with no PSRAM, sustained decode + display + Wi-Fi is the realistic ceiling; see [`../performance.md`](../performance.md) |
-
-Simultaneous-use notes:
-
-* **Audio + keyboard**: both on the internal I²C bus. Codec register writes are short; key
-  events are FIFO-buffered. No failures reported.
-* **Audio + microSD**: independent buses, but both want CPU. WAV playback from SD is
-  demonstrated by several projects.
-* **Audio + Wi-Fi streaming**: demonstrated (`Cardputer-WebRadio`), and the community reports it
-  as the memory ceiling on a no-PSRAM part.
-
-## 9. Limits
-
-| Limit | Value | Class |
-|---|---|---|
-| Speaker | 8 Ω, 1 W | board |
-| Mic SNR | 65 dB | vendor spec |
-| No MCLK | must use BCLK-derived clocking | board |
-| No PSRAM | decode buffers live in 512 KB SRAM | **silicon** |
-| Jack detect | hardware-only, not readable | board |
-| Sample rates | not characterised by this session | not tested |
-
-## 10. Evidence status
-
-| Claim | Status |
-|---|---|
-| Part identities, designators, pin-to-pin wiring | **official** — schematic sheet 3 text layer, validated against the product page's PinMap |
-| I²S/I²C pin assignment | **official** — M5Unified source, three independent implementations agree |
-| Register sequences quoted | **official** — verbatim from M5Unified at a pinned commit |
-| §6.1 divergence, §6.2 power-down interaction | **derived by reading the source**; consequences reasoned, **not hardware-tested** |
-| Hardware jack mute | **official** — vendor prose + schematic network |
-| Any audio quality, latency or level measurement | **not tested** |
diff --git a/devices/m5stack/cardputer-adv/features/battery-and-power.md b/devices/m5stack/cardputer-adv/features/battery-and-power.md
deleted file mode 100644
index 3247fb8..0000000
--- a/devices/m5stack/cardputer-adv/features/battery-and-power.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# Cardputer ADV — battery and power
-
-> **Question:** *"How do I read the battery, charge it safely, and make it last?"*
-> ADV specifics; the v1.x power train uses the **same parts** but a different battery topology.
-> Verified **2026-09-04**. Nothing in this file was measured.
-
-## The power train
-
-```
-USB-C (Stamp-S3A) ─ F1 6V/1A PPTC ─► +5VIN ─┬─► D1 SS34 ─► VBAT_OUT
-                                            └─► U1 TP4057 charger ─► BAT ─► J8 (1750 mAh cell)
-                                                   R1 0.8 Ω sense, R5 3.3 kΩ PROG
- VBAT_IN ─► U3 CN809J supervisor ─► RESET (R7 100 kΩ)
- VBAT_OUT ─► R2 0 Ω ─► U2 SY7088 boost (L1 3015 1.5 µH, FB R4 75 k / R6 22 k) ─► +5VOUT
- VBAT_OUT ─► Q1/Q2/Q3 LP3218DT1G power path
- +5VOUT   ─► U4 SY8089 buck  (L2 4.7 µH, FB R11 100 k? / R12 68 k / R13 15 k) ─► +3.3V
- SW1 SW-SPDT = the side power switch;  SW2 SW-SPDT;  BTN1/BTN2 SW-PB
-```
-
-| Part | Designator | Role | Record |
-|---|---|---|---|
-| TP4057 | U1 | Li-ion linear charger, `PROG` = R5 3.3 kΩ | [`generic/tp4057`](../../../../components/generic/tp4057/README.md) |
-| CN809J | U3 | voltage supervisor / reset generator | [`consonance/cn809`](../../../../components/consonance/cn809/README.md) |
-| SY7088 | U2 | boost → `+5VOUT` | [`silergy/sy7088`](../../../../components/silergy/sy7088/README.md) |
-| SY8089 | U4 | buck → `+3.3V` | [`silergy/sy8089`](../../../../components/silergy/sy8089/README.md) |
-| LP3218DT1G | Q1–Q3 | power-path MOSFETs | [`unidentified/cardputer/lp3218dt1g`](../../../../components/unidentified/cardputer/lp3218dt1g/README.md) |
-| SS34 | D1, D2 | Schottky | — |
-| JW5712 | Stamp U4 | 3.3 V buck on the module, 0–0.6 A | [`joulwatt/jw5712`](../../../../components/joulwatt/jw5712/README.md) |
-| AW35122FDR | Stamp U2 | `BL_3V3` load switch | [`awinic/aw35122`](../../../../components/awinic/aw35122/README.md) |
-
-**R3 (1 kΩ) and D3 (an LED) on sheet 1 are drawn greyed out — depopulated.** A charge-status
-indicator that the production board does not fit. That is a positive DNP marking, not an
-omission.
-
-## Inferred rail voltages
-
-The sheet prints its own formula next to the SY7088: `Vout = 1.2 V × (R1/R2 + 1)`.
-
-| Rail | Divider | Computed | Status |
-|---|---|---|---|
-| `+5VOUT` | R4 75 kΩ / R6 22 kΩ | 1.2 × (75/22 + 1) = **5.29 V** | **inferred**, not measured |
-| `+3.3V` | R12 68 kΩ / R13 15 kΩ (SY8089) | 1.2 × (68/15 + 1)… ≈ 6.6 V — **does not compute to 3.3 V**, so the SY8089's reference or divider topology differs from the SY7088's. **Do not trust this line.** | **unresolved** |
-| Charge current | TP4057 with `R_PROG` = 3.3 kΩ | order of **300 mA** | **inferred** from the usual TP4057 `I = 1000 × V_PROG / R_PROG` relation; the datasheet was not retrieved |
-
-The `+3.3V` arithmetic not working out is recorded honestly rather than fudged: either the
-resistor identification from the extracted text is wrong, or the SY8089 uses a different
-feedback reference. See [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-## Reading the battery
-
-Single ADC channel, **GPIO 10**, through a divider.
-
-```cpp
-#include <M5Cardputer.h>
-void setup() { auto cfg = M5.config(); M5Cardputer.begin(cfg, true); }
-void loop() {
-  int32_t mv  = M5Cardputer.Power.getBatteryVoltage();   // millivolts
-  int32_t pct = M5Cardputer.Power.getBatteryLevel();     // 0..100, curve-fitted
-  M5Cardputer.Display.setCursor(0,0);
-  M5Cardputer.Display.printf("%ld mV  %ld%%", mv, pct);
-  delay(1000);
-}
-```
-
-`Power_Class.cpp:573-574` groups `board_M5Cardputer` and `board_M5CardputerADV` together, so
-the same conversion is used for both — despite the ADV having a *single* 1750 mAh cell where
-the v1.x has 120 mAh + 1400 mAh. The divider ratio is the same; the capacity is not, so any
-percentage curve tuned on a v1.x is only approximately right here. Bruce hard-codes
-`-DANALOG_BAT_PIN=10` and does its own conversion.
-
-There is **no fuel gauge**. The CardputerZero has a BQ27220YZFR; the ADV has a resistor divider.
-Coulomb counting, cycle count, health and time-to-empty are not available.
-
-## ⚠ Charging requires the power switch ON
-
-M5Stack states this on the ADV, v1.0 and v1.1 pages alike: *"When charging the Cardputer-Adv,
-please switch the power to ON."* The side switch (SW1) gates the path the charger needs; with
-it OFF the device draws the quoted **0.23 µA** but does not charge.
-
-This surprises people. It is the most consistently repeated warning across all three product
-pages and the one most likely to produce a "my Cardputer won't charge" report.
-
-## Vendor power figures
-
-At DC 4.2 V, from the ADV product page:
-
-| Condition | Current |
-|---|---|
-| Standby, power switch **OFF** | **0.23 µA** |
-| Operating | 120.2 mA |
-| Wi-Fi active | 132.3 mA |
-| BLE active | 154.6 mA |
-
-Against 1750 mAh that is roughly 13 h Wi-Fi / 11 h BLE **if** those figures include the display
-backlight, which M5Stack does not say. Compare the v1.1's published numbers — *"IR transmission
-mode 148.07 mA, key mode 138.93 mA"* — which are measured under different conditions again, so
-the two generations' figures are **not directly comparable**. Do not build a runtime comparison
-out of them.
-
-Note also that BLE reads *higher* than Wi-Fi here, which is the opposite of the usual ordering
-and suggests the three measurements were taken with different display/CPU states. Recorded as a
-vendor-data oddity.
-
-## Making it last
-
-* **Backlight dominates.** But see [`display.md`](display.md): dimming below 100 % browns out
-  the RGB LED, because they share the AW35122-switched rail.
-* **Deep sleep** works; the ESP32-S3's RTC domain survives it. But there is **no RTC and no
-  IMU interrupt**, so your only wake sources are timer, GPIO (G0, or a CAP `INT`) and touch.
-* **`Speaker.end()` does nothing** — the ES8311 stays powered. Explicitly run the microphone's
-  power-down sequence, or drive the codec yourself, before sleeping. See
-  [`audio.md`](audio.md) §6.2.
-* The `+5VOUT` boost runs whenever the device is on; a Grove or CAP peripheral drawing from it
-  is paid for at boost efficiency.
-
-## Safety and repair
-
-* 0 – 40 °C operating range (vendor).
-* The cell is internal and not user-serviceable without opening the case; there is **no
-  published cell part number**.
-* r/M5Stack, 2026-08-05: *"I'm looking for screws and buttons of the right height for the
-  Cardputer ADV, but I can't find them on AE."* — M5Stack sells a mixed M3 screw pack; button
-  caps are commonly 3D-printed. Spares for the ADV specifically are not stocked.
-* r/M5Stack, 2026-08-22: *"Cardputer adv black screen only when turning it on"* — a boot-time
-  display failure with two low-information replies. Unresolved; recorded because it is the only
-  hardware-fault report found for the ADV in this pass.
-
-## Evidence status
-
-| Claim | Status |
-|---|---|
-| Part identities and topology | **official** — rendered schematic sheet 1 |
-| DNP marking on R3/D3 | **official** — drawn greyed |
-| `+5VOUT` ≈ 5.29 V, ~300 mA charge | **inferred**, formula shown, not measured |
-| `+3.3V` divider arithmetic | **unresolved** — stated, not hidden |
-| Current figures | **vendor claim**, conditions unstated, **not independently measured** |
-| Runtime estimates | **derived** from vendor claims; treat as upper bounds |
diff --git a/devices/m5stack/cardputer-adv/features/cap-header.md b/devices/m5stack/cardputer-adv/features/cap-header.md
deleted file mode 100644
index 47ff9f6..0000000
--- a/devices/m5stack/cardputer-adv/features/cap-header.md
+++ /dev/null
@@ -1,211 +0,0 @@
-# Cardputer ADV — the CAP expansion header (host side)
-
-> **Question answered:** *"What is the 14-pin header on the underside, what can I plug into it,
-> and how do I design my own board for it?"*
-> **This is the host-side document.** The two M5Stack CAP boards have their own records, owned
-> by a different session: [`../../cap-lora-1262/`](../../cap-lora-1262/README.md) and
-> [`../../cap-cc1101/`](../../cap-cc1101/README.md). Nothing here duplicates them.
-> Applies to **Cardputer ADV only** — v1.0, v1.1 and the accessory kits have no such connector.
-> Last verified **2026-09-04**.
-
-## What it is
-
-M5Stack calls it two things and the community a third:
-
-| Name | Used by |
-|---|---|
-| **EXT 2.54-14P expansion bus** | the ADV and Mesh Kit product pages, spec tables |
-| **Cap-Bus** | the Mesh Kit page's pin table for the *module* side |
-| **CAP** | the product family name — `Cap LoRa-1262` (U214), `Cap CC1101` (U219), and the docs URL space `docs.m5stack.com/en/cap/…` |
-
-It is a **2 × 7 through-hole/SMD header on 2.54 mm pitch**, schematic designator **P3**,
-footprint **`HDR-SMD_14P-P2.54`**, on the underside of the device. A CAP board presents the
-mating male header and is retained by two M2 × 4 mm screws.
-
-It exists because the TCA8418 freed seven GPIOs. Every signal pin on this connector except the
-two I²C lines is a pin that a v1.x Cardputer spends on its keyboard matrix.
-
-## Pinout — by physical position
-
-Use this table. It does not depend on whose numbering you adopt.
-
-| Row L (top→bottom) | Signal | GPIO | Direction (host) | | Row R (top→bottom) | Signal | GPIO | Direction (host) |
-|---|---|---|---|---|---|---|---|---|
-| L1 | `RESET` | **G3** | out | | R1 | `5VIN` | — | power **in** |
-| L2 | `INT` / `IRQ` | **G4** | in | | R2 | `GND` | — | — |
-| L3 | `BUSY` | **G6** | in | | R3 | `5VOUT` | — | power **out** |
-| L4 | `SCK` | **G40** | out | | R4 | `I2C_SDA` | **G8** | I/O |
-| L5 | `MOSI` | **G14** | out | | R5 | `I2C_SCL` | **G9** | I/O |
-| L6 | `MISO` | **G39** | in | | R6 | `UART_TX` | **G13** | **out** |
-| L7 | `CS` | **G5** | out | | R7 | `UART_RX` | **G15** | **in** |
-
-Source: sheet 4 of `Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf`, read from the rendered
-sheet. The schematic symbol's own pin names are
-`RESET, INT, BUSY, SCK, MOSI, MISO, CS` on the left and
-`5VIN, GND, 5VOUT, SDA, SCL, GPS-RX, GPS-TX` on the right, against nets
-`G3, G4, G6, G40, G14, G39, G5` and `+5VIN, GND, +5VOUT, G8, G9, G13, G15`.
-
-## ⚠ Three numbering schemes describe this one connector
-
-This is the single most likely way to get a CAP board wrong, so it gets its own table. All
-three orderings agree on the *physical* signal order; only the numbers differ.
-
-| Physical position | Product-page number (interleaved) | Host schematic number (P3) | Cap-board number (Cap-Bus) |
-|---|---|---|---|
-| L1 `RESET` G3 | **1** | **1** | **8** (`LoRa_RST`) |
-| L2 `INT` G4 | 3 | 2 | 9 (`LoRa_IRQ`) |
-| L3 `BUSY` G6 | 5 | 3 | 10 (`LoRa_BUSY`) |
-| L4 `SCK` G40 | 7 | 4 | 11 (`LoRa_SCK`) |
-| L5 `MOSI` G14 | 9 | 5 | 12 (`LoRa_MOSI`) |
-| L6 `MISO` G39 | 11 | 6 | 13 (`LoRa_MISO`) |
-| L7 `CS` G5 | 13 | 7 | 14 (`LoRa_NSS`) |
-| R1 `5VIN` | 2 | 14 | 7 (`5V_IN`) |
-| R2 `GND` | 4 | 13 | 6 |
-| R3 `5VOUT` | 6 | 12 | 5 (`5V_OUT`) |
-| R4 `SDA` G8 | 8 | 11 | 4 |
-| R5 `SCL` G9 | 10 | 10 | 3 |
-| R6 `UART_TX` G13 | 12 | 9 | 2 (`GPS_RX`) |
-| R7 `UART_RX` G15 | 14 | 8 | 1 (`GPS_TX`) |
-
-* The **product page** numbers 1,3,5,…,13 down the left and 2,4,6,…,14 down the right — the
-  usual IDC convention.
-* The **host schematic** numbers 1–7 down the left and 8–14 **up** the right.
-* The **Cap board** uses the mirror image, because that is what a mating header does:
-  Cap pin *n* ↔ host schematic pin ((n + 6) mod 14) + 1.
-
-**Design rule:** work from the physical-position table and the signal names. Never transfer a
-bare pin number between a host document and a module document.
-
-## The UART direction, settled
-
-`G13` is the **host's TX**, `G15` is the **host's RX**. M5Stack's Mesh Kit page says the
-opposite in its EXT table and then contradicts itself in its Cap-Bus table. Four sources agree
-against it, including M5Stack's own factory firmware:
-
-```c
-/* M5Cardputer-UserDemo @ b549eac0, main/hal/hal_config.h */
-#define HAL_PIN_GPS_TX  GPIO_NUM_13
-#define HAL_PIN_GPS_RX  GPIO_NUM_15
-/* main/hal/cap_lora868/uart/uart_helper.c:71 */
-uart_set_pin(ECHO_UART_PORT_NUM, HAL_PIN_GPS_TX /*tx*/, HAL_PIN_GPS_RX /*rx*/, …);
-```
-
-and Meshtastic's `variants/esp32s3/m5stack_cardputer_adv/variant.h`:
-`#define GPS_RX_PIN 15` / `#define GPS_TX_PIN 13`.
-Full evidence table in [`../pinouts-and-buses.md` §4](../pinouts-and-buses.md).
-
-## Electrical specification
-
-| Property | Value | Evidence |
-|---|---|---|
-| Logic level | **3.3 V** — all signal pins are ESP32-S3 GPIOs, no level shifting anywhere on the host | schematic; no translator in the ADV designator census |
-| `5VIN` | accepts the host's `+5VIN` domain (USB VBUS, behind the Stamp's 6 V/1 A PPTC) | Stamp-S3A sheet, F1 |
-| `5VOUT` | the **SY7088** boost output, nominal **≈ 5.29 V [inferred]** from FB 75 k/22 k and the sheet's own `Vout = 1.2 V × (R1/R2 + 1)` | schematic sheet 1 |
-| `5VOUT` current budget | **not published.** The SY7088 is a 2 A-class boost, but the shared Grove `+5V` and the whole 3.3 V rail come from it too. The CardputerZero's equivalent port is documented at **< 500 mA**; the ADV publishes no figure. Do not assume more than a few hundred mA. | gap |
-| I²C pull-ups | **already fitted on the host** — R36/R37, 3.3 kΩ each. **Do not add more on a CAP board** unless you intend the parallel value. | schematic sheet 2 |
-| I²C addresses in use | `0x18` ES8311, `0x34` TCA8418, `0x69` BMI270 — **avoid these** | see [`../pinouts-and-buses.md`](../pinouts-and-buses.md) |
-| SPI | shared with the microSD card (CS G12). Your CS is **G5**. | see below |
-| `RESET` (G3) | **also an ESP32-S3 JTAG-source strap pin.** Leave it high-Z or high at reset. | ESP32-S3 strapping |
-| ESD | the host fits `PESDNC2FD3V3B` / `PESDNC2FD5VB` arrays elsewhere; **no ESD protection was identified on P3 itself** | designator census, sheet 4 |
-
-## ⚠ The SPI bus is shared with the microSD card
-
-`SCK` G40, `MOSI` G14, `MISO` G39 are the same three pins the microSD uses. Only the chip
-selects differ (SD = G12, CAP = G5).
-
-Consequences you must design for:
-
-1. **Deassert one CS before asserting the other.** Neither is done for you.
-2. **Clock rate is set by the slowest participant.** SD cards tolerate 20–40 MHz; an SX1262 is
-   specified to 16 MHz. If you share a bus handle, run at the transceiver's limit.
-3. **Long SD transactions add jitter to radio timing.** A LoRa receive window that opens while
-   a 512-byte SD block is in flight will be late. Meshtastic and the M5 factory firmware both
-   live with this; it is the main reason "SD logging + LoRa" projects report intermittent
-   missed packets.
-4. If you use two separate `SPIClass` instances on the same pins, you must serialise them
-   yourself — the ESP32-S3 SPI peripheral will not.
-
-Realistic combinations are tabulated in
-[`../resources-and-conflicts.md`](../resources-and-conflicts.md).
-
-## What plugs in today
-
-| Board | SKU | Released | What it adds | Record |
-|---|---|---|---|---|
-| **Cap LoRa-1262** | U214 | **2026-01-04** | SX1262 868–923 MHz, RP-SMA, ATGM336H/AT6668 GNSS, PI4IOE5V6408 expander, FM8625H RF switch, HY2.0-4P | [`../../cap-lora-1262/`](../../cap-lora-1262/README.md) |
-| **Cap CC1101 & NFC** | U219 | **2026-08-28** | CC1101 sub-GHz + NFC | [`../../cap-cc1101/`](../../cap-cc1101/README.md) |
-
-Community CAP boards found on 2026-09-04 (not verified by this session):
-`Prokuon/CardputerADV_Cap_TFT-2.8` and `CardputerADV_Cap_TFT_V2` (secondary displays — the
-Reddit announcement reached ↑989), `JosephCGS/Cardputer-ADV-CC1101-NRF24L01-LoRa`,
-`guicmg/cardputer_adv_external_screen`, and the `AndyAiCardputer` ZX Spectrum ports that drive
-ILI9341/ILI9488 panels off the header.
-
-### How the host talks to the Cap LoRa-1262
-
-Host-side pin assignment as used by all three implementations:
-
-| Function | GPIO | M5 UserDemo | Meshtastic |
-|---|---|---|---|
-| `NSS`/CS | G5 | `HAL_PIN_LORA_NSS_GPIO 5` | `LORA_CS 5` |
-| `RESET` | G3 | `HAL_PIN_LORA_RST_GPIO 3` | `LORA_RESET 3` |
-| `DIO1`/IRQ | G4 | `HAL_PIN_LORA_DIO1_GPIO 4` | `LORA_DIO1 4` |
-| `BUSY` | G6 | `HAL_PIN_LORA_BUSY_GPIO 6` | `SX126X_BUSY` ← `LORA_DIO2 6` |
-| SPI | G40/G14/G39 | `HAL_PIN_SPI_*` | `LORA_SCK/MISO/MOSI` |
-| GNSS UART | G13 TX / G15 RX @115200 8N1 | `HAL_PIN_GPS_*` | `GPS_RX_PIN 15`, `GPS_TX_PIN 13` |
-
-Meshtastic additionally declares `SX126X_DIO2_AS_RF_SWITCH` and
-`SX126X_DIO3_TCXO_VOLTAGE 1.8` with `TCXO_OPTIONAL`.
-
-**One extra step the header does not tell you:** the Cap LoRa-1262's RF antenna switch is not
-free-running. M5Stack's Mesh Kit page states plainly:
-
-> "The following steps are required to initialize the LoRa module: Enable the RF antenna
-> switch: set **P0 of the PI4IOE I/O expander to HIGH**."
-
-That expander lives on the **CAP I²C pins (G8/G9)** — i.e. on the host's *internal* bus,
-alongside the keyboard scanner. Omit it and the radio transmits into a disconnected antenna.
-Detail belongs to the Cap board's record.
-
-## Designing your own CAP board — checklist
-
-1. **Mechanical:** 84.0 × 24.0 × 15.2 mm is the Cap LoRa-1262's envelope; two M2 × 4 mm screws.
-2. **Numbering:** use the physical-position table above; label your silkscreen with *signal
-   names*, not numbers.
-3. **Power:** take `5VIN` if you want to be fed from USB, `5VOUT` if from the boost. Budget
-   conservatively; no host figure is published.
-4. **I²C:** no pull-ups. Avoid `0x18`, `0x34`, `0x69`. Expect the keyboard scanner to be
-   sharing your bus and to want low latency.
-5. **SPI:** your CS is G5 only. Arbitrate against the microSD yourself.
-6. **`RESET` on G3 is a strap pin** — do not drive it low during host reset.
-7. **ESD:** add your own on any user-touchable pin; the host does not appear to protect P3.
-8. **UART:** host TX is G13, host RX is G15. Cross them on your board.
-9. **Detection:** there is **no ID pin, no EEPROM, no presence detect.** Firmware discovers a
-   CAP board by probing — Meshtastic probes the SX1262 over SPI, the Plai client is reported by
-   a user to "automatically detect the lora cap and switch configurations" (u/Big-Bunch2804,
-   r/CardPuter, 2026-08-05). If you want your board discoverable, put something on I²C.
-
-## Is it ADV-only?
-
-**Yes, on the Cardputer line.** The v1.0/v1.1 mainboard has no such connector and, more
-fundamentally, no free pins to build one from — G3–G7, G13 and G15 are the keyboard.
-
-But the *connector* is not ADV-exclusive within M5Stack: the **CardputerZero (C154)** carries
-an `EXT 2.54-14P` with the same physical shape and the same 5VIN/GND/5VOUT/I2C/UART positions,
-while the left column becomes `HAT_P0/HAT_P1` (switchable USB or GPIO), `G22`, and SPI0. A CAP
-board that only uses power + I²C + UART has a chance of working on both; one that uses
-`RESET`/`INT`/`BUSY` does not, and the Zero's UART sits on the *opposite* member of the R6/R7
-pair. See [`../../cardputer-zero/README.md`](../../cardputer-zero/README.md).
-
-## Evidence status
-
-| Claim | Status |
-|---|---|
-| Physical pinout, net names, GPIO assignment | **official** — rendered vendor schematic sheet 4 |
-| UART direction | **official** ×4, one vendor page dissenting; resolved |
-| SPI sharing with microSD | **official** — same nets in `_pin_table_sd` and on sheet 4 |
-| I²C pull-up values | **official** — schematic sheet 2 |
-| `5VOUT` ≈ 5.29 V | **inferred** from FB resistors + the formula printed on the sheet. Not measured. |
-| `5VOUT` current limit | **unknown** — no vendor figure |
-| No ESD on P3 | **inferred** from a designator census of sheet 4; absence of evidence, stated as such |
-| Community CAP boards | **community**, catalogued not verified |
diff --git a/devices/m5stack/cardputer-adv/features/display.md b/devices/m5stack/cardputer-adv/features/display.md
deleted file mode 100644
index f4d9ad0..0000000
--- a/devices/m5stack/cardputer-adv/features/display.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Cardputer ADV — display
-
-> **Question:** *"How do I draw on the screen, and why does my RGB LED die when I dim it?"*
-> Applies to **all Cardputer revisions** — the display path is unchanged from v1.0 to ADV.
-> Verified **2026-09-04**.
-
-## Hardware
-
-| Item | Value | Record |
-|---|---|---|
-| Panel | ST7789V2, 1.14″, **240 × 135** visible | [`sitronix/st7789v2`](../../../../components/sitronix/st7789v2/README.md) |
-| Interface | SPI, `SPI3_HOST`, **3-wire** (`spi_3wire = true`, `pin_miso = -1`) | M5GFX |
-| Clock | 40 MHz write, 16 MHz read | M5GFX `bus_cfg` |
-| Connection | 8-pin 0.5 mm FPC (`FPC1`) from the front panel | schematic sheet 1 |
-
-| Signal | GPIO |
-|---|---|
-| `SCK` | G36 |
-| `MOSI` | G35 |
-| `DC`/`RS` | G34 |
-| `CS` | G37 |
-| `RST` | G33 |
-| Backlight PWM / `BL_3V3` enable | **G38** |
-
-M5GFX panel configuration for the Cardputer family:
-`panel_width = 135`, `panel_height = 240`, `offset_x = 52`, `offset_y = 40`,
-`invert = true`, `readable = true`, `setRotation(1)` — i.e. the panel is a 240-tall portrait
-part used in landscape with a window offset. Backlight:
-`_set_pwm_backlight(GPIO_NUM_38, 7, 256, false, 16)` — **LEDC channel 7, 256 Hz, offset 16**.
-
-## Minimal procedure
-
-```cpp
-#include <M5Cardputer.h>
-void setup() {
-  auto cfg = M5.config();
-  M5Cardputer.begin(cfg, true);
-  M5Cardputer.Display.setRotation(1);
-  M5Cardputer.Display.setBrightness(255);
-  M5Cardputer.Display.fillScreen(TFT_BLACK);
-  M5Cardputer.Display.drawString("hello", 10, 10);
-}
-void loop() {}
-```
-
-## ⚠ The backlight rail also powers the RGB LED
-
-On **Stamp-S3A** (so: v1.1 and ADV, not v1.0) `DISP_BL` = **G38** drives the enable pin of an
-**AW35122FDR** load switch that produces `BL_3V3`, and `BL_3V3` supplies **both** the LCD
-backlight **and** the WS2812 RGB LED. On the older StampS3 v0.2 the WS2812 was fed from the
-always-on `VDD_3V3` instead. Verified by comparing U3's `VDD` net across the two Stamp
-schematics: `VDD_3V3` on v0.2, `BL_3V3` on v0.3.3.
-
-Consequences:
-
-* **PWM-dimming the backlight chops the WS2812's supply.** M5Stack's v1.1 page says it
-  outright: *"Since RGB and LCD backlight share the same power source, when the LCD backlight
-  brightness is below 100%, RGB will not be powered properly. Please use the RGB function when
-  the backlight is at full brightness."* The ADV page **omits this warning** even though the
-  ADV uses the same Stamp-S3A — a vendor documentation gap, recorded in
-  [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-* The ADV page instead says *"set GPIO38, which controls this switch, to a high level"* before
-  using the RGB LED. Both statements describe the same AW35122FDR.
-* **Backlight off means RGB LED off.** You cannot have a dark screen and a status LED.
-* Component: [`awinic/aw35122`](../../../../components/awinic/aw35122/README.md),
-  [`worldsemi/ws2812`](../../../../components/worldsemi/ws2812/README.md).
-
-## Alternatives
-
-| Approach | Notes |
-|---|---|
-| `M5GFX` / `M5Unified` | default; gets autodetect, rotation, offsets, backlight for free |
-| `TFT_eSPI` | what Bruce uses: `ST7789_2_DRIVER`, `TFT_WIDTH=135`, `TFT_HEIGHT=240`, `TFT_RGB_ORDER=1`, `USE_HSPI_PORT`, `SPI_FREQUENCY=20000000`, `MINBRIGHT=160` |
-| `meshtastic/st7789` | Meshtastic's fork, pinned at `92bae2e4` |
-| LovyanGFX directly | M5GFX *is* a LovyanGFX derivative |
-
-Bruce runs the panel at **20 MHz**, M5GFX at **40 MHz**. Both are reported working; the
-difference is margin, not correctness.
-
-## Secondary displays
-
-The CAP header has enough SPI to drive a second panel, and the community does:
-`Prokuon/CardputerADV_Cap_TFT-2.8` and `_V2`, `guicmg/cardputer_adv_external_screen`
-("Guide to how use Dual Screen with Cardputer ADV"), and ZX Spectrum ports to ILI9341/ILI9488.
-The Cap TFT-2.8 announcement on r/CardPuter (2026-06-22) reached ↑989 with 75 comments — the
-highest-scoring Cardputer hardware post found in this pass.
-
-## Resources and limits
-
-| Resource | Used |
-|---|---|
-| SPI host | `SPI3_HOST`, exclusive to the panel |
-| GPIO | G33–G38 |
-| LEDC | channel 7 |
-| DMA | M5GFX uses SPI DMA; no explicit channel pinning found |
-
-| Limit | Class |
-|---|---|
-| 240 × 135 × 16 bpp = 64 800 B full framebuffer | **board/silicon** — that is 12.7 % of the 512 KB SRAM, and there is **no PSRAM**, so double-buffering plus a network stack is tight |
-| No touch | board |
-| No MISO wired (`spi_3wire`) | board — panel reads go over the data line |
-
-## Evidence status
-
-Pin map and M5GFX configuration: **official** (source at pinned commit).
-Rail sharing: **official** — two vendor schematics compared.
-No display timing or refresh-rate measurement was taken: **not tested**.
diff --git a/devices/m5stack/cardputer-adv/features/grove-port.md b/devices/m5stack/cardputer-adv/features/grove-port.md
deleted file mode 100644
index c14d705..0000000
--- a/devices/m5stack/cardputer-adv/features/grove-port.md
+++ /dev/null
@@ -1,84 +0,0 @@
-# Cardputer ADV — Grove / PORT.A
-
-> **Question:** *"How do I attach a Grove sensor?"*
-> Identical connector on v1.0, v1.1 and ADV. Verified **2026-09-04**.
-
-## Hardware
-
-One **HY2.0-4P** connector, schematic designator **P1**, part value `HY-2.0_IIC`, protected by
-`PESDNC2FD3V3B`/`PESDNC2FD5VB` ESD arrays (D6–D8) and fed from `+5VOUT`.
-
-| Wire | Signal | GPIO |
-|---|---|---|
-| Black | GND | — |
-| Red | +5 V (from the SY7088 boost) | — |
-| Yellow | `G2` | GPIO 2 |
-| White | `G1` | GPIO 1 |
-
-M5Stack labels the port **`PORT.CUSTOM`** in the PinMap rather than `PORT.A`, but M5Unified
-treats it as the external I²C bus for the whole Cardputer family.
-
-## ⚠ Which line is the clock?
-
-| Source | SCL | SDA |
-|---|---|---|
-| `M5Unified.cpp:99`, header `// In SCL,SDA, EX SCL,SDA` → `{…, GPIO_NUM_1, GPIO_NUM_2}` | **G1** (white) | **G2** (yellow) |
-| M5Stack's usual Grove colour convention | yellow | white |
-| Bruce `m5stack-cardputer.ini` | `-DGROVE_SCL=1` | `-DGROVE_SDA=2` |
-
-Two independent software sources say **SCL = G1, SDA = G2**; only the colour convention
-disagrees, and M5Stack calls this port `PORT.CUSTOM` rather than `PORT.A` precisely because it
-is not the standard assignment. **Use G1 = SCL, G2 = SDA.** Recorded in
-[`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-## Minimal procedure
-
-```cpp
-#include <M5Cardputer.h>
-void setup() {
-  auto cfg = M5.config(); M5Cardputer.begin(cfg, true);
-  M5Cardputer.Ex_I2C.begin();                 // G1 SCL / G2 SDA
-  for (uint8_t a = 8; a < 120; a++)
-    if (M5Cardputer.Ex_I2C.start(a, false, 100000)) {
-      M5Cardputer.Display.printf("0x%02X\n", a);
-      M5Cardputer.Ex_I2C.stop();
-    }
-}
-void loop() {}
-```
-
-`geo-tp/M5-Card-Computer-I2C-Scanner` (★23, MIT) does this as a finished app.
-
-## It is not only I²C
-
-G1 and G2 are ordinary GPIOs. Bruce exposes them as candidate pins for IR TX/RX, 433 MHz
-OOK TX/RX, a CC1101 `GDO0`, an NRF24 `CE`, a W5500 `INT` and an SPI `SS`
-(`-DSPI_SS_PIN=GROVE_SCL`). On a **v1.x**, where the CAP header does not exist, the Grove port
-is the *only* general-purpose I/O available — which is why Bruce's pin menus are written the way
-they are.
-
-## Advantages over the CAP header for I²C
-
-| | Grove (G1/G2) | CAP (G8/G9) |
-|---|---|---|
-| Other devices on the bus | **none** | TCA8418 `0x34`, ES8311 `0x18`, BMI270 `0x69` |
-| Address freedom | full | avoid three |
-| Latency impact on the keyboard | none | real |
-| Pull-ups | on your peripheral | already fitted, 3.3 kΩ |
-| Connector | keyed 2 mm, cable | 2.54 mm header, board-to-board |
-
-**Put slow or chatty I²C peripherals on Grove.** Keep the internal bus for things that must be
-on it.
-
-## Limits
-
-* Power comes from `+5VOUT` (SY7088 boost, **≈ 5.29 V inferred**). No published current limit
-  for this port on the ADV; the CardputerZero's equivalent is specified at **< 500 mA**.
-* 3.3 V logic on G1/G2 with a 5 V supply pin — the usual Grove arrangement. A 5 V-logic
-  peripheral needs level shifting.
-* One connector. Chain on the bus if you need more.
-
-## Evidence status
-
-Pin assignment: **official** ×3. SCL/SDA orientation: **conflict recorded, software sources
-preferred**. Current limit: **unknown**.
diff --git a/devices/m5stack/cardputer-adv/features/imu.md b/devices/m5stack/cardputer-adv/features/imu.md
deleted file mode 100644
index e5944c5..0000000
--- a/devices/m5stack/cardputer-adv/features/imu.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# Cardputer ADV — IMU
-
-> **Question:** *"How do I read motion on a Cardputer ADV?"*
-> **ADV only.** v1.0 and v1.1 have no IMU at all. Verified **2026-09-04**.
-
-## Hardware
-
-**Bosch BMI270**, 6-axis (3-axis accelerometer + 3-axis gyroscope), designator **U7** on
-schematic sheet 3, on the **internal** I²C bus.
-
-| Property | Value | Evidence |
-|---|---|---|
-| Bus | internal I²C — SDA **G8**, SCL **G9** | docs PinMap; schematic U7 pins 14 (`SDX`) and 13 (`SCX`) |
-| Address | **`0x69`** | the schematic prints **"7-bit Address 69H"** beside U7; R43 3.3 kΩ pulls `SDO` high |
-| Interrupts | `INT1` (pin 4) and `INT2` (pin 9) present on the symbol; **neither traced to a GPIO** | schematic |
-| Aux interface | `ASDX`/`ASCX`/`OSDO`/`OCSB` present (BMI270 auxiliary I²C for a magnetometer) — **no magnetometer fitted** | designator census of sheet 3 |
-| Decoupling | C25 10 µF/10 V, C27 100 nF, FB7 120 Ω/MB ferrite on `VDD` | schematic |
-
-Component record: [`bosch-sensortec/bmi270`](../../../../components/bosch-sensortec/bmi270/README.md).
-
-M5Stack publishes an **IMU axis diagram** for the ADV at
-`m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/IMU-Cardputer-Adv.jpg` — see
-[`../media.md`](../media.md). Orientation conventions differ between boards; use it rather than
-assuming.
-
-## Minimal procedure
-
-```cpp
-#include <M5Cardputer.h>
-void setup() {
-  auto cfg = M5.config();
-  cfg.internal_imu = true;
-  M5Cardputer.begin(cfg, true);
-}
-void loop() {
-  M5Cardputer.update();
-  if (M5.Imu.update()) {
-    auto d = M5.Imu.getImuData();
-    M5Cardputer.Display.setCursor(0,0);
-    M5Cardputer.Display.printf("%.2f %.2f %.2f\n", d.accel.x, d.accel.y, d.accel.z);
-  }
-  delay(20);
-}
-```
-
-M5Unified's `IMU_Class` probes the internal bus and identifies the BMI270 itself; the ADV row
-in `_pin_table_i2c_ex_in` (`In SCL = G9, In SDA = G8`) is what makes that possible. On a
-v1.0/v1.1 the same row is `255, 255` — there is no internal bus to probe.
-
-## Alternatives
-
-| Approach | Notes |
-|---|---|
-| `M5Unified` `M5.Imu` | default; abstracts BMI270 vs other parts |
-| `BoschSensortec/BMI270_SensorAPI` | full feature set — step counter, wrist gestures, any-motion, FIFO |
-| `M5Cardputer-UserDemo` `app_imu` | M5Stack's own ESP-IDF demo app, on the `CardputerADV` branch |
-
-The BMI270 needs a ~8 KB configuration blob uploaded at init; every driver does this, and it is
-why first `begin()` is slow. Do not be surprised by a ~100 ms init.
-
-## ⚠ No interrupt line
-
-`INT1`/`INT2` are on the symbol but were not traced to any GPIO, and no vendor document or
-driver references a BMI270 interrupt pin on this board. That means:
-
-* **No motion-wake.** You cannot use the IMU to bring the ESP32-S3 out of deep sleep.
-* Everything is polled, so sample rate is bounded by your loop and by bus contention with the
-  keyboard scanner and the codec.
-
-Stated as *not established* rather than *absent*: the sheet-3 pin table shows the names but the
-band-based text extraction did not resolve their nets, and there is no page render at
-sufficient resolution in this pass to be certain. Recorded in
-[`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-## Resources and conflicts
-
-| Resource | Used |
-|---|---|
-| I²C `0x69` on the internal bus | shared with TCA8418 `0x34`, ES8311 `0x18` |
-| GPIO | none exclusively |
-
-High-rate IMU polling competes with keyboard event latency on the same bus. Nothing has been
-measured; treat "1 kHz IMU + responsive keyboard" as unproven.
-
-## Evidence status
-
-Address `0x69`: **official** — printed on the schematic and consistent with `SDO` pulled high.
-Bus assignment: **official** ×2 (docs PinMap + M5Unified table).
-No-interrupt claim: **not established** (see above).
-No IMU data was read from hardware by this session: **not tested**.
diff --git a/devices/m5stack/cardputer-adv/features/ir.md b/devices/m5stack/cardputer-adv/features/ir.md
deleted file mode 100644
index 284dc02..0000000
--- a/devices/m5stack/cardputer-adv/features/ir.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# Cardputer ADV — infrared
-
-> **Question:** *"How do I send IR commands? Can I receive?"*
-> Verified **2026-09-04**.
-
-## Hardware
-
-A **single IR emitter, transmit only**, on **GPIO 44**. Designator `IR1` on schematic sheet 1.
-There is **no IR receiver** on any Cardputer — the CardputerZero adds one (`IR_RX` on `G13`),
-the ADV does not.
-
-| Item | Value |
-|---|---|
-| TX GPIO | **G44** |
-| RX | **none** |
-| Emitter designator | `IR1` |
-| Range (v1.1 figures; the ADV page gives none) | 410 cm at 0°, 170 cm at 45°, 66 cm at 90° |
-
-`M5Cardputer-UserDemo` `hal_config.h`: `#define HAL_PIN_IR_TX 44`.
-Bruce: `-DTXLED=44`, `-DLED_ON=HIGH`, `-DLED_OFF=LOW`.
-
-## Minimal procedure
-
-The `M5Cardputer` library depends on `arduino-irremote/IRremote` and ships
-`examples/Basic/ir_nec/ir_nec.ino` (added `0fd54b7`, 2023-10-13):
-
-```cpp
-#include <M5Cardputer.h>
-#define IR_TX_PIN 44
-#define DISABLE_CODE_FOR_RECEIVER
-#include <IRremote.hpp>
-
-void setup() {
-  auto cfg = M5.config(); M5Cardputer.begin(cfg, true);
-  IrSender.begin(IR_TX_PIN);
-}
-void loop() {
-  IrSender.sendNEC(0x0102, 0x34, 0);
-  delay(1000);
-}
-```
-
-ESP-IDF users: the factory firmware's `main/hal/utils/ir_nec/` wraps the RMT peripheral
-(`void ir_helper_init(gpio_num_t pin_tx)`).
-
-## Receiving anyway
-
-You cannot without adding hardware. Two routes:
-
-| Route | Pins | Note |
-|---|---|---|
-| Grove / PORT.A | G1, G2 | M5Stack sells an IR unit; Bruce's `IR_RX_PINS` list offers `{"M5 IR Mod", GROVE_SCL}, {"Grove W", GROVE_SCL}, {"Grove Y", GROVE_SDA}` |
-| CAP header | G3, G4, G5, G6, G13, G15 | Bruce also offers `{"ADV 3",3},{"ADV 4",4},{"ADV 5",5},{"ADV 6",6},{"ADV 13",13},{"ADV 15",15}` — a direct acknowledgement that the ADV's freed pins are the general-purpose ones |
-
-Bruce's pin lists are the clearest third-party statement of what the ADV's extra GPIOs are
-actually good for. From `boards/m5stack-cardputer/m5stack-cardputer.ini`:
-
-```
--DIR_TX_PINS='{ {"Default", TXLED}, {"M5 IR Mod", GROVE_SDA}, {"Grove W", GROVE_SCL},
-                {"Grove Y", GROVE_SDA}, {"ADV 3",3},{"ADV 4",4},{"ADV 5",5},
-                {"ADV 6",6},{"ADV 13",13},{"ADV 15",15} }'
-```
-
-The same list appears for `RF_TX_PINS`/`RF_RX_PINS`, i.e. for 433 MHz OOK modules.
-
-## Projects
-
-* `geo-tp/Ultimate-Remote` (★200) — "Universal remote control for the M5Cardputer, contains
-  3498 remote profiles".
-* r/M5Stack 2026-08-19: *"I made an ir sniper for cardputer ADV"*.
-* Bruce and Launcher both include IR replay/transmit tooling.
-
-## Resources and limits
-
-| Resource | Note |
-|---|---|
-| RMT | one channel; shares the RMT peripheral with the WS2812 on G21 |
-| Current | the v1.1 page quotes 148.07 mA in IR transmission mode — the highest single-function figure M5Stack publishes for a Cardputer |
-| Carrier | standard 38 kHz via RMT/IRremote; not board-limited |
-
-## Evidence status
-
-TX pin: **official** ×3 (docs PinMap, factory firmware, Bruce). Absence of a receiver:
-**verified negative** by designator census plus the CardputerZero positive control (which does
-list an IR receiver). Range figures: **vendor claim for v1.1**, and **not published for the ADV**
-— do not transfer them without saying so.
diff --git a/devices/m5stack/cardputer-adv/features/keyboard.md b/devices/m5stack/cardputer-adv/features/keyboard.md
deleted file mode 100644
index 35f6395..0000000
--- a/devices/m5stack/cardputer-adv/features/keyboard.md
+++ /dev/null
@@ -1,276 +0,0 @@
-# Cardputer ADV — how the keyboard works
-
-> **Question answered:** *"How do I read the keyboard on a Cardputer ADV, and how is it wired?"*
-> Applies to: **Cardputer ADV (K132-Adv)** only. The v1.0/v1.1 answer is
-> [`../../cardputer-v1.1/README.md`](../../cardputer-v1.1/README.md) and is completely different.
-> Evidence: schematic sheet 2 (rendered), `M5Cardputer` @ `f1392858`, `M5GFX` @ `d91077b9`.
-> Last verified **2026-09-04**. Not hardware-tested by this session.
-
-## Summary
-
-56 keys in a **4 rows × 14 columns** legend layout, wired as an **8 × 7 electrical matrix**,
-scanned by a **TI TCA8418RTWR** keypad scanner over the internal I²C bus at **`0x34`**, which
-raises **GPIO 11** when there is an event to read. Three GPIOs total, two of which are the I²C
-bus you wanted anyway.
-
-Component record: [`components/texas-instruments/tca8418`](../../../../components/texas-instruments/tca8418/README.md).
-
-## The hardware path
-
-```
-56 × SW-PB (S1..S56)
-   │  column side (pairs)          row side (rows + parity)
-   ├── ROW0..ROW6  ──────────────► TCA8418 pins 8..2
-   └── Y0..Y7 ── R27..R34 22 Ω ──► TCA8418 COL7..COL0 (pins 16..9)
-                                        │
-                        SDA G8 ─────────┤  (3.3 kΩ pull-up R37)
-                        SCL G9 ─────────┤  (3.3 kΩ pull-up R36)
-                        INT G11 ────────┘  (3.3 kΩ pull-up R35)
-                        RESET ── R38 10 kΩ ── +3V3   ← no GPIO
-```
-
-Read off the rendered sheet, U9 block:
-
-| TCA8418 pin | Name | Net | Series R |
-|---|---|---|---|
-| 1 | `ROW7` | **explicit no-connect (×)** | — |
-| 2 | `ROW6` | `ROW6` | — |
-| 3 | `ROW5` | `ROW5` | — |
-| 4 | `ROW4` | `ROW4` | — |
-| 5 | `ROW3` | `ROW3` | — |
-| 6 | `ROW2` | `ROW2` | — |
-| 7 | `ROW1` | `ROW1` | — |
-| 8 | `ROW0` | `ROW0` | — |
-| 9 | `COL0` | `Y7` | R27 22 Ω 1 % |
-| 10 | `COL1` | `Y6` | R28 |
-| 11 | `COL2` | `Y5` | R29 |
-| 12 | `COL3` | `Y4` | R30 |
-| 13 | `COL4` | `Y3` | R31 |
-| 14 | `COL5` | `Y2` | R32 |
-| 15 | `COL6` | `Y1` | R33 |
-| 16 | `COL7` | `Y0` | R34 |
-| 17 | `COL8` | **explicit no-connect (×)** | — |
-| 18 | `COL9` | **explicit no-connect (×)** | — |
-| 19, 25 | `GND`, `EP` | GND | — |
-| 20 | `RESET` | +3V3 via R38 10 kΩ — **no GPIO** | — |
-| 21 | `VCC` | +3V3 | — |
-| 22 | `SDA` | `G8` | pull-up R37 3.3 kΩ |
-| 23 | `SCL` | `G9` | pull-up R36 3.3 kΩ |
-| 24 | `INT` (active low) | `G11` | pull-up R35 3.3 kΩ |
-
-Note the **`COL`↔`Y` reversal**: `COL0` is `Y7`, `COL7` is `Y0`. It is not a transcription
-slip; it is what the sheet shows, and it is what makes the remap arithmetic below come out.
-
-The three no-connects are drawn as explicit **×** markers, not blanks — the designer asserting
-"unused", which is stronger evidence than an empty pin.
-
-## The finding that makes the whole delta legible
-
-**The ADV's keyboard matrix is electrically identical to the v1.0/v1.1 matrix.** Same 56
-switches, same net names `Y0..Y7`, same series resistors down to the same reference designators
-`R27`–`R34` at the same 22 Ω 1 %. On a v1.x, `Y0..Y7` are the eight **outputs of a 74HC138**
-(U7, pins 15,14,13,12,11,10,9,7 → `Y0..Y7`, also through R34..R27) and the seven column-pair
-lines go to seven GPIOs. On the ADV, `Y0..Y7` go to the TCA8418's COL pins and the seven
-column-pair lines go to its ROW pins.
-
-M5Stack redrew the driver and left the matrix alone. That is why the logical key coordinates
-come out the same on both boards, and why one binary can serve both.
-
-Note the nomenclature trap: **the TCA8418's "ROW" lines are the keyboard's *column pairs*, and
-its "COL" lines are the keyboard's *rows*.** Do not read the datasheet's ROW/COL as the
-keyboard's rows and columns.
-
-## Matrix topology
-
-| Concept | Value |
-|---|---|
-| Legend layout | 4 rows × 14 columns = 56 |
-| Electrical matrix | **7 (TCA8418 ROW) × 8 (TCA8418 COL)** = 56 |
-| `ROW`*n* serves | keyboard **columns 2n and 2n+1** |
-| `COL`*m* serves | keyboard **row m mod 4**; `m ≥ 4` selects the **odd** column of the pair |
-| Ghosting | no diodes fitted; the TCA8418 does key-event FIFO reporting rather than raw scan, so N-key rollover is bounded by the part, not the matrix |
-
-Verified against the sheet at the corner of the array: **S1** (keyboard column 0, row 0) has its
-top terminal on `ROW0` and its bottom terminal on **`Y7`** = `COL0`; **S2** (column 1, row 0)
-shares `ROW0` and goes to **`Y3`** = `COL4`. That is exactly what the rule predicts. The `ROW0`
-line visibly feeds the first switch pair, `ROW1` the second, `ROW2` the third, in a rendered
-crop of the row bus.
-
-Switch designators run **S1..S56**: S1–S14 = legend row 0, S15–S28 = row 1, S29–S42 = row 2,
-S43–S56 = row 3. (The automated designator census recovered 41 of 56 because `PIS`*nn*`0m`
-markers are ambiguous to split — a limitation of the marker parser, not a gap in the schematic.)
-
-## The vendor driver, and the arithmetic
-
-[`TCA8418.cpp`](https://github.com/m5stack/M5Cardputer/blob/f1392858b9994c3547120e602a57d3553d16ab01/src/utility/Keyboard/KeyboardReader/TCA8418.cpp):
-
-```cpp
-// line 13
-#define DEFAULT_TCA8418_INT_PIN 11
-…
-// lines 39-49
-_tca8418->matrix(7, 8);      // 7 rows, 8 columns
-_tca8418->flush();
-pinMode(_interrupt_pin, INPUT);
-attachInterruptArg(digitalPinToInterrupt(_interrupt_pin), gpio_isr_handler, this, CHANGE);
-_tca8418->enableInterrupts();
-```
-
-Event decode, lines 75–85 — the TCA8418 FIFO byte is `state<<7 | (row*10 + col + 1)`:
-
-```cpp
-ret.state = eventRaw & 0x80;
-uint16_t buffer = eventRaw; buffer &= 0x7F; buffer--;
-ret.row = buffer / 10;
-ret.col = buffer % 10;
-```
-
-Remap to Cardputer logical coordinates, lines 88–101 — **this is the whole compatibility layer**:
-
-```cpp
-uint8_t col = key.row * 2;          // TCA8418 ROW → keyboard column pair
-if (key.col > 3) col++;             //   upper 4 COLs = odd column
-uint8_t row = (key.col + 4) % 4;    // == key.col % 4  → keyboard row
-key.row = row;  key.col = col;
-```
-
-So `x = raw_row × 2 + (raw_col ≥ 4)`, `y = raw_col mod 4`, giving `x ∈ 0..13`, `y ∈ 0..3`.
-
-### Why that is bit-for-bit equivalent to the v1.x reader
-
-The v1.x reader, [`IOMatrix.cpp:91-108`](https://github.com/m5stack/M5Cardputer/blob/f1392858b9994c3547120e602a57d3553d16ab01/src/utility/Keyboard/KeyboardReader/IOMatrix.cpp#L91-L108),
-walks `i = 0..7` on the 74HC138 address lines and does:
-
-```cpp
-coor.x = (i > 3) ? X_map_chart[j].x_1 : X_map_chart[j].x_2;
-coor.y = (i > 3) ? (i - 4) : i;
-coor.y = -coor.y; coor.y = coor.y + 3;      //  y = 3 - (i mod 4)
-```
-
-Substituting `n = 7 - m` (the `Y` index for TCA8418 `COL`*m*) into the ADV rule gives
-`y = (7 - n) mod 4 = 3 - (n mod 4)` and "odd column when `n ≤ 3`" — **identical** to the v1.x
-rule expressed in the same `Y` index. The two drivers produce the same `(x, y)` for the same
-physical key. That is the reason a single `_key_value_map[4][14]` serves both, and it is a
-deliberate design choice, not a coincidence.
-
-## Key legend map
-
-`_key_value_map[4][14]` in
-[`Keyboard.h:19-74`](https://github.com/m5stack/M5Cardputer/blob/f1392858b9994c3547120e602a57d3553d16ab01/src/utility/Keyboard/Keyboard.h#L19-L74),
-`{value_first, value_second /* Aa layer */, value_third /* fn layer */}`:
-
-| y\x | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 |
-|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
-| **0** | `` ` `` | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | - | = | BkSp |
-| **1** | Tab | q | w | e | r | t | y | u | i | o | p | [ | ] | \ |
-| **2** | **FN** | **SHIFT** | a | s | d | f | g | h | j | k | l | ; | ' | Enter |
-| **3** | **CTRL** | **OPT** | **ALT** | z | x | c | v | b | n | m | , | . | / | Space |
-
-The **fn layer** (third value) gives `ESC` on `` ` ``, `F1`–`F12` on the number row, `DELETE`
-on Backspace, and arrows on `;` `,` `.` `/` — **↑ ; ← , ↓ . → /**. It was added in
-`eccba25` (2026-05-11, PR #15 by GiorgioAresu) and corrected in `84e5201` (2026-05-12); a
-library older than that has no fn layer and no arrow keys.
-
-## Minimal procedure — Arduino
-
-```cpp
-#include <M5Cardputer.h>
-
-void setup() {
-  auto cfg = M5.config();
-  M5Cardputer.begin(cfg, true);        // true = enable the keyboard
-  M5Cardputer.Display.setTextSize(2);
-}
-
-void loop() {
-  M5Cardputer.update();                // pumps updateKeyList() + updateKeysState()
-  if (M5Cardputer.Keyboard.isChange() && M5Cardputer.Keyboard.isPressed()) {
-    auto st = M5Cardputer.Keyboard.keysState();
-    for (auto c : st.word)  M5Cardputer.Display.print(c);
-    if (st.enter) M5Cardputer.Display.println();
-    if (st.del)   M5Cardputer.Display.print("\b \b");
-  }
-  delay(5);
-}
-```
-
-`M5Cardputer.begin()` calls `M5.begin()` → M5GFX autodetect → `M5.getBoard()` returns
-`board_M5CardputerADV`, and `Keyboard_Class::begin()` then injects the right reader:
-
-```cpp
-// Keyboard.cpp:21-28
-if (board_type == m5::board_t::board_M5Cardputer)          _keyboard_reader = std::make_unique<IOMatrixKeyboardReader>();
-else if (board_type == m5::board_t::board_M5CardputerADV)  _keyboard_reader = std::make_unique<TCA8418KeyboardReader>();
-else { printf("[error] Keyboard: Unsupported board type: %d\n", (int)board_type);
-       _keyboard_reader = std::make_unique<KeyboardReader>(); }   // ← does nothing
-```
-
-If autodetect fails you get the third branch: no error at compile time, a single `printf`, and
-a keyboard that never reports a key. **If your keyboard is silent, check the autodetect log
-line first.**
-
-### Bring your own reader
-
-`Keyboard_Class::begin(std::unique_ptr<KeyboardReader>)` is public, so you can inject a custom
-reader without forking the library — useful if you want polling instead of interrupts, or a
-different interrupt pin (`TCA8418KeyboardReader(int interrupt_pin)`).
-
-## Alternatives
-
-| Approach | When | Cost |
-|---|---|---|
-| `M5Cardputer` library (above) | almost always; you get board autodetect and both generations free | pulls in M5Unified + M5GFX + IRremote |
-| `Adafruit_TCA8418` directly | you only want keys and no graphics stack | you write the remap and the legend map yourself; the vendor's vendored copy is at `src/utility/Adafruit_TCA8418/` |
-| Poll instead of interrupt | you cannot spare G11, or you are inside a tight render loop | Bruce does exactly this at a 100 ms interval and it is perceptibly less responsive for held keys |
-| Raw register access | you want the TCA8418's GPIO/debounce/keylock features the vendor never touches | see the component record |
-
-## Resources consumed
-
-| Resource | Amount |
-|---|---|
-| GPIO | G8, G9 (shared bus), G11 (dedicated) |
-| I²C address | `0x34` on the internal bus |
-| GPIO interrupt | one, on G11, `CHANGE` edge |
-| Timers | none |
-| RAM | `std::vector<Point2D_t>` key list, a few hundred bytes |
-
-## Limits, pitfalls and known failures
-
-* **Silicon:** TCA8418 supports up to 80 keys (10 COL × 8 ROW); 56 are wired, `ROW7`, `COL8`,
-  `COL9` are explicit NCs.
-* **Board:** `RESET` is strapped high through R38 and reaches **no GPIO**. A wedged scanner
-  needs a power cycle. There is no software recovery path.
-* **Board:** the scanner shares its bus with the ES8311 and BMI270; a driver that holds the
-  bus during a long I²S/codec configuration will delay key events. Not observed to lose them —
-  the TCA8418 has a 10-deep FIFO — but latency is real.
-* **Framework:** `M5Cardputer` **1.1.1** is the first release with ADV support (added
-  2025-08-29…09-02, `c331c7d`…`8ab9f43`). Anything older silently uses the GPIO-matrix reader
-  on an ADV and reports no keys.
-* **Framework:** without `eccba25` (2026-05-11) there is no fn layer, hence **no arrow keys**.
-* **Community-reported:** *"The update today won't allow me to use directional arrows on adv
-  anymore."* — u/Big-Bunch2804, r/CardPuter, **2026-08-29**, on the Plai Meshtastic client.
-  Firsthand user report; arrow handling in third-party firmware is fragile.
-* **Compatibility hazard:** M5GFX's ADV test is "are G8 and G9 pulled up". Anything that pulls
-  those high on a **v1.x** makes it misdetect as an ADV and lose its keyboard. See
-  [`../compatibility-and-status.md`](../compatibility-and-status.md).
-
-## Debugging
-
-1. Watch the boot log for `[Autodetect] board_M5CardputerADV`. Wrong board → wrong reader.
-2. I²C-scan the internal bus (G8/G9). You should see exactly `0x18`, `0x34`, `0x69`.
-   `geo-tp/M5-Card-Computer-I2C-Scanner` does this if you want it prebuilt.
-3. Read `TCA8418_REG_INT_STAT`. The vendor's `update()` writes `1` to clear it and re-reads;
-   if bit 0 stays set there are still queued events.
-4. If `INT` never asserts, confirm `matrix(7, 8)` ran — the TCA8418 does not scan pins that are
-   not enrolled in the matrix.
-
-## Evidence status
-
-| Claim | Status |
-|---|---|
-| Pin-by-pin TCA8418 wiring, series resistors, no-connects | **official** — rendered vendor schematic sheet 2 |
-| `0x34` address | **official** (Adafruit default, Bruce build flag); not probed by this session |
-| Remap arithmetic and its equivalence to the v1.x reader | **official** source + **derived**, arithmetic shown |
-| S1 → `ROW0`/`Y7`, S2 → `ROW0`/`Y3` | **official** — read from a 1:1 sheet crop |
-| Full per-switch net table for all 56 keys | **not established** — the rule is verified at the array corner and by the driver, but each of the other 54 switches was not individually traced |
-| Any timing, latency or rollover number | **not tested** |
diff --git a/devices/m5stack/cardputer-adv/features/microsd.md b/devices/m5stack/cardputer-adv/features/microsd.md
deleted file mode 100644
index 5225316..0000000
--- a/devices/m5stack/cardputer-adv/features/microsd.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Cardputer ADV — microSD
-
-> **Question:** *"How do I read and write the SD card, and why does it interfere with my radio?"*
-> Applies to all Cardputer revisions (identical pins); the **conflict** section is ADV-specific.
-> Verified **2026-09-04**.
-
-## Hardware
-
-Push-push microSD socket on the SPI peripheral bus, 1-bit SPI mode.
-
-| Signal | GPIO | Source |
-|---|---|---|
-| `SCK` | **G40** | `M5Unified.cpp:211` `_pin_table_sd` |
-| `MOSI` (CMD) | **G14** | same |
-| `MISO` (D0) | **G39** | same |
-| `CS` (D3) | **G12** | same |
-| D1, D2 | not wired (`255`) | same |
-
-Identical on v1.0, v1.1 and ADV — `_pin_table_sd` has one row each and they are the same
-numbers. Component: [`generic/micro-sd-sdmmc`](../../../../components/generic/micro-sd-sdmmc/README.md).
-
-## Minimal procedure
-
-```cpp
-#include <M5Cardputer.h>
-#include <SD.h>
-#include <SPI.h>
-
-#define SD_CS 12
-void setup() {
-  auto cfg = M5.config(); M5Cardputer.begin(cfg, true);
-  SPI.begin(40, 39, 14, SD_CS);           // SCK, MISO, MOSI, SS
-  while (!SD.begin(SD_CS, SPI, 25000000)) { delay(500); }
-  auto f = SD.open("/hello.txt", FILE_WRITE); f.println("hi"); f.close();
-}
-void loop() {}
-```
-
-The vendored example `M5Cardputer/examples/Basic/sdcard/sdcard.ino` (added `889cbd7`,
-2024-01-19) does the same and is the vendor's reference.
-
-## ⚠ The bus is shared with the CAP header
-
-G40/G14/G39 also go to **CAP pins L4/L5/L6**. The CAP chip select is **G5**, the SD's is G12.
-Nothing arbitrates them for you.
-
-| Combination | Status | Notes |
-|---|---|---|
-| SD alone | **works** — vendor example | |
-| SD + Cap LoRa-1262 | **reported working** — M5Stack's own factory firmware does both, Meshtastic does both | assert one CS at a time; run the bus at the SX1262's 16 MHz limit if you share a handle |
-| SD + CAP + tight LoRa RX windows | **caution** | a 512 B SD block at 16 MHz is ~256 µs of bus occupancy plus card latency; receive windows opened late are missed packets |
-| SD + display | **works** — different SPI host | |
-
-Detail: [`cap-header.md`](cap-header.md) §"The SPI bus is shared", and
-[`../resources-and-conflicts.md`](../resources-and-conflicts.md).
-
-## Community notes
-
-* *"What sd card does everybody use with their cardputer Adv?"* — r/CardPuter, 2026-08-09,
-  ↑4/12 comments. There is no vendor-specified card class or maximum capacity, and no
-  compatibility list. Treat card choice as untested.
-* Several firmwares expect a specific SD layout: Evil-M5Project reads an `evil/` directory,
-  Launcher boots `.bin` files from the card, Bruce keeps configuration there. If you swap
-  firmware, expect to re-provision the card.
-* `uagainshadow/Tons-of-LIVE-Public-CCTV-Cameras-for-the-Cardputer` is an SD content pack —
-  a reminder that the card is a first-class part of the ecosystem, not just storage.
-
-## Limits
-
-| Limit | Class |
-|---|---|
-| 1-bit SPI only (D1/D2 unwired) — no 4-bit SDMMC | **board** |
-| Shared bus with CAP | **board** |
-| No card-detect line identified on the schematic | **board** |
-| Maximum capacity / speed class | **unknown** — no vendor statement, not tested |
-
-## Evidence status
-
-Pin map: **official** (M5Unified pinned commit, three boards agree, and the docs PinMap
-matches). Bus sharing: **official** (same nets on schematic sheet 4). Timing consequences:
-**inferred**. No SD card was exercised by this session.
diff --git a/devices/m5stack/cardputer-adv/features/rtc.md b/devices/m5stack/cardputer-adv/features/rtc.md
deleted file mode 100644
index 40aaf11..0000000
--- a/devices/m5stack/cardputer-adv/features/rtc.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Cardputer ADV — real-time clock
-
-> **Question:** *"How do I keep wall-clock time across a power cycle?"*
-> **Short answer: you cannot, in hardware. There is no RTC on any Cardputer.**
-> Verified **2026-09-04**.
-
-## The negative result, and how it was established
-
-This is a *verified negative*, not a failed search:
-
-1. **Designator census of every sheet** of `Sch_M5CardputerAdv_v1.0` (4 sheets, 155 distinct
-   reference designators). The nine `U` designators are U1 TP4057, U2 SY7088, U3 CN809J,
-   U4 SY8089, U5 NS4150B, U6 ES8311, U7 BMI270, U8 MSM381A3729H9BP, U9 TCA8418RTWR. **No RTC.**
-2. **No crystal in the 32.768 kHz class** anywhere on the mainboard; the only crystal in the
-   system is X1, 40 MHz, on the Stamp-S3A.
-3. **No coin cell, no supercap, no `VBAT`/`VRTC` net.** J8 is the main battery connector.
-4. **The ADV product page's specification table has no RTC row**, while
-   `docs.m5stack.com/en/CardputerZero` **does** (`RX8130CE`) — so M5Stack lists an RTC when one
-   is present.
-5. **M5Unified has no RTC entry** for `board_M5CardputerADV`.
-
-Positive control: the same census method on the **CardputerZero** page finds `RX8130CE @ 0x32`
-listed in both the spec table and the HMI pin map. The method detects RTCs when they exist.
-
-## What the ESP32-S3 gives you instead
-
-| Mechanism | Survives | Accuracy | Notes |
-|---|---|---|---|
-| `esp_timer` / `gettimeofday` from RTC slow memory | **deep sleep only** | internal 150 kHz RC, ±5 % uncalibrated | dies on power-off and on the ADV's hard power switch |
-| RTC slow memory + `RTC_DATA_ATTR` | deep sleep only | — | a few KB |
-| SNTP over Wi-Fi | nothing, but re-acquires | network-grade | the normal answer; needs credentials and a network |
-| GNSS time from a **Cap LoRa-1262** | nothing, but re-acquires | very good | ATGM336H over UART G13/G15; cold start 23 s, hot 1 s per the Mesh Kit spec |
-| External RTC on Grove or CAP I²C | **yes** | part-dependent | see below |
-
-## Adding an RTC
-
-Both expansion routes work. Watch the address collisions.
-
-| Route | Pins | Free addresses |
-|---|---|---|
-| **Grove / PORT.A** (external bus) | SCL G1, SDA G2 | entire space — nothing else is on it |
-| **CAP header** (internal bus) | SCL G9, SDA G8, positions R4/R5 | avoid `0x18`, `0x34`, `0x69` |
-
-Common parts and their fixed addresses: `BM8563`/`PCF8563` at `0x51`
-([`generic/bm8563`](../../../../components/generic/bm8563/README.md)), `DS3231` at `0x68` —
-**note `0x68` is one below the BMI270's `0x69`**, so a DS3231 on the *internal* bus is fine but
-a DS3231 with its address strap altered is not. `RX8130CE` (what the Zero uses) is at `0x32`.
-
-Prefer the **Grove** port: it is otherwise unused, it is 5 V-tolerant at the connector, and it
-keeps your RTC off the bus the keyboard scanner needs for latency.
-
-## Why this matters more than it sounds
-
-Several of the platform's most popular applications assume a clock:
-
-* **Meshtastic** timestamps messages. Without an RTC or GNSS, timestamps come from the mesh or
-  from a phone, and a solo node boots with no idea of the time.
-* Logging applications (`geo-tp/M5Cardputer-GPS-Logger`, CSI/radar projects) need monotonic
-  *and* absolute time.
-* Anything doing TOTP, certificate validation, or scheduled tasks needs wall-clock time.
-
-The **Cardputer Mesh Kit's** GNSS is, in practice, the ADV's clock source — one more reason the
-kit is more than the sum of its parts.
-
-## Evidence status
-
-Absence of an RTC: **verified negative** by full designator census plus a positive control.
-Alternatives: **official** for ESP32-S3 mechanisms, **inferred** for the Grove/CAP recommendations.
-Nothing here was hardware-tested.
diff --git a/devices/m5stack/cardputer-adv/features/usb.md b/devices/m5stack/cardputer-adv/features/usb.md
deleted file mode 100644
index 8654e06..0000000
--- a/devices/m5stack/cardputer-adv/features/usb.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# Cardputer ADV — USB
-
-> **Question:** *"How do I flash it, get a serial console, or make it act as a USB keyboard?"*
-> Verified **2026-09-04**.
-
-## Hardware
-
-USB-C on the **Stamp-S3A**, wired to the ESP32-S3's **native USB-OTG** peripheral. There is
-**no USB-UART bridge chip** — no CP210x, no CH340. Confirmed by designator census of the
-Stamp-S3A schematic: `J2 USB-TYPEC`, `R1`/`R2` 5.1 kΩ CC resistors, `F1` 6 V/1 A PPTC,
-`L5` common-mode choke, `D14` `PESDNC2FD5VB`, `D3`/`D4` `PESDNC2FD3V3B`, `JP2`/`JP3` solder
-jumpers on `USB_DU_P`/`USB_DU_N`. No bridge.
-
-Consequences:
-
-* The serial port **appears and disappears with the firmware**, because the CDC device is
-  implemented by the running application. A crashed or non-CDC firmware means no port.
-* `-DARDUINO_USB_CDC_ON_BOOT=1` and `-DARDUINO_USB_MODE=1` are in M5Stack's own PlatformIO
-  profile for a reason.
-* USB Serial/JTAG is available as a fallback console independent of the application.
-
-## Download mode
-
-M5Stack's procedure, identical on all three revisions:
-
-> Set the side power switch to **OFF**. Then, **before powering on, hold the G0 button**, apply
-> power, and release it afterwards. The device will then enter download mode.
-
-`G0` is the button on the Stamp module, pulled up by 10 kΩ. Note this is *not* the usual
-"hold BOOT, tap RESET" — **there is no reset button on the ADV**.
-
-## Build profile
-
-M5Stack publishes this on all three product pages:
-
-```ini
-[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-  -DESP32S3
-  -DCORE_DEBUG_LEVEL=5
-  -DARDUINO_USB_CDC_ON_BOOT=1
-  -DARDUINO_USB_MODE=1
-lib_deps =
-  M5Cardputer=https://github.com/m5stack/M5Cardputer
-```
-
-Note it targets the generic `esp32-s3-devkitc-1` board definition, not a Cardputer-specific one
-— which is fine because M5GFX autodetects at runtime. Meshtastic instead uses
-`board = m5stack-stamps3`, and Bruce/Launcher use `board = m5stack-cardputer` with their own
-`pins_arduino.h`.
-
-## USB HID
-
-The ESP32-S3's native USB can enumerate as a HID keyboard, and the Cardputer's whole point is
-that it has a keyboard to forward.
-
-* `M5Cardputer/examples/Basic/keyboard/usbKeyboard/usbKeyboard.ino` (added `2c0de0e`,
-  2023-10-16) — the vendor's reference.
-* `Keyboard_def.h` carries a full `_kb_asciimap[128]` of **USB HID usage codes** with a `SHIFT`
-  (`0x80`) flag, plus `KEY_LEFT_CTRL 0x80`, `KEY_LEFT_SHIFT 0x81`, `KEY_LEFT_ALT 0x82`,
-  `KEY_FN 0xff`, `KEY_OPT 0x00`. Everything you need to be a HID keyboard is already in the
-  library.
-* `VoidNoi/BadCard` (★148, GPL-3.0) — BadUSB with Ducky-script support.
-* Bruce: `-DUSB_as_HID=1`.
-* The factory firmware also does **BLE** HID (`"CardputerADV Keyboard"`).
-
-## Host mode
-
-The ADV is **not** a USB host in any meaningful sense — one Type-C port, no hub, no VBUS
-switching. Contrast the **CardputerZero**, which has a physical Host/Slave toggle, a
-GL852G-OHY60 hub, a USB-A port and USB-Ethernet.
-
-## Limits and pitfalls
-
-| Limit | Class |
-|---|---|
-| No UART bridge — port vanishes when firmware misbehaves | board |
-| No reset button; recovery is switch-OFF → hold G0 → power | board |
-| PPTC F1 at 6 V/1 A limits inrush and total draw | board |
-| CDC + Wi-Fi + display simultaneously is RAM-tight | silicon (no PSRAM) |
-| `-DCORE_DEBUG_LEVEL=5` in the vendor profile is *verbose*; drop it for production | framework |
-
-## Evidence status
-
-Absence of a bridge: **verified negative** by designator census of the Stamp-S3A schematic.
-Download procedure: **official** (three product pages agree verbatim).
-Build profile: **official**, quoted verbatim. **Not executed by this session** — no hardware.
diff --git a/devices/m5stack/cardputer-adv/features/wifi-and-ble.md b/devices/m5stack/cardputer-adv/features/wifi-and-ble.md
deleted file mode 100644
index d548b29..0000000
--- a/devices/m5stack/cardputer-adv/features/wifi-and-ble.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# Cardputer ADV — Wi-Fi and BLE
-
-> **Question:** *"How do I use the radio, and how good is the antenna?"*
-> Radio is on the Stamp module, so this applies to the whole family with one real difference.
-> Verified **2026-09-04**.
-
-## Hardware
-
-The ESP32-S3FN8's radio, matched by `L6 0 Ω / C19 4.3 nH / C20 (NC) / L1 2.7 nH / C2 2.2 pF /
-C1 1.8 pF` into **ANT1** on the Stamp-S3A. Single 2.4 GHz chain: **Wi-Fi 802.11 b/g/n** and
-**Bluetooth 5 LE**. No 5 GHz, no classic Bluetooth (the ESP32-S3 has no BR/EDR).
-
-**The one generation difference:** M5Stack's own comparison table says the **antenna design was
-optimised** on the Stamp-S3A — "Optimized antenna design for better reception" for v1.1 and
-ADV versus "Standard antenna" for v1.0. The two Stamp schematics do show different matching
-components, but a matching-network delta is not a quantified sensitivity improvement and
-**no RF measurement is published**. Treat "better reception" as a vendor claim.
-
-## Minimal procedure
-
-Nothing Cardputer-specific — this is stock Arduino-ESP32 / ESP-IDF:
-
-```cpp
-#include <M5Cardputer.h>
-#include <WiFi.h>
-void setup() {
-  auto cfg = M5.config(); M5Cardputer.begin(cfg, true);
-  WiFi.mode(WIFI_STA);
-  WiFi.begin("ssid", "pass");
-  while (WiFi.status() != WL_CONNECTED) { delay(250); }
-  M5Cardputer.Display.println(WiFi.localIP().toString());
-}
-void loop() {}
-```
-
-BLE: `NimBLE` is the practical choice on a no-PSRAM part, and it is what M5Stack's own factory
-firmware uses — `sdkconfig.defaults` on the `CardputerADV` branch sets
-`CONFIG_BT_NIMBLE_ENABLED=y`, `CONFIG_BT_NIMBLE_SM_LVL=2`,
-`CONFIG_BT_NIMBLE_SVC_GAP_DEVICE_NAME="CardputerADV Keyboard"` and HID-tuned connection
-parameters (12/48 interval, latency 8, 600 supervision timeout). The ADV factory firmware ships
-as a **BLE HID keyboard**.
-
-## The generic guide
-
-Standard ESP32-S3 Wi-Fi and BLE procedures apply **unchanged**. There is no board-specific
-provisioning, no external PA/LNA, no RF switch on the mainboard, and no coexistence hardware.
-
-## What the community does with it
-
-The radio is the reason most people buy this device. Catalogued in
-[`../projects-and-community.md`](../projects-and-community.md):
-
-* **Wi-Fi auditing** — Evil-M5Project (★2 570), Bruce (★6 642), ESP32Marauder (★12 212, has a
-  `User_Setup_marauder_m5cardputer_adv.h`).
-* **Wi-Fi CSI sensing** — `skizzophrenic/Cardputer-CSI-Human-Detector` (★207),
-  `Zeloksa/Cardputer-ADV-CSI-Radar` (★100). Both 2026, both ADV. This is a genuinely unusual
-  use of the part.
-* **BLE tooling** — `MatthewKuKanich/ChimeraBLE` (★220), `Gitshaoxiang/M5Cardputer-BLE-HID-Keyboard`.
-* **Streaming** — WebRadio ports, `geo-tp/M5Cardputer-Audio-Stream-Server`.
-* **ESP-NOW** — the factory firmware pulls `espressif/esp-now@2.5.2` (see `dependencies.lock`).
-
-## Resources and conflicts
-
-| Resource | Note |
-|---|---|
-| RF | single chain; Wi-Fi and BLE coexist by time-sharing, as on any ESP32-S3 |
-| **RAM** | **the binding constraint.** No PSRAM. A Wi-Fi stack plus TLS plus a framebuffer plus an audio decode buffer does not fit comfortably in 512 KB. |
-| Power | 132.3 mA Wi-Fi / 154.6 mA BLE at 4.2 V (vendor) |
-| **CAP LoRa** | a Cap LoRa-1262 adds a *second* radio at 868–923 MHz. No coexistence issue at those frequencies, but the SPI and current draw are shared. |
-
-The RAM ceiling is not theoretical. The author of a Meshtastic client wrote (r/CardPuter,
-2026-08-01): *"the ESP32-S3 here has no PSRAM, so a full Unicode font cannot live in RAM. It
-ships as its own 2.16 MB flash partition … memory-mapped, so rendering Cyrillic, CJK or Greek
-costs no heap at all."* That is a firsthand engineering account of working around the exact
-constraint, and it is the single most instructive community post about this platform.
-
-## Antenna modifications
-
-`henriquesebastiao/external-cardputer-antenna` (★55) documents fitting an external antenna;
-r/CardPuter has recurring "external antenna" mod posts. None of these are vendor-supported and
-none carry measurements. Note that modifying the antenna invalidates whatever (unpublished)
-certification the module carries.
-
-## Evidence status
-
-Antenna network: **official** — Stamp-S3A schematic. "Better reception": **vendor claim,
-unquantified**. Radio capability: **silicon spec**. Everything about throughput, range or
-sensitivity: **not tested, and no independent measurement found**.
diff --git a/devices/m5stack/cardputer-adv/gaps-and-conflicts.md b/devices/m5stack/cardputer-adv/gaps-and-conflicts.md
deleted file mode 100644
index 24d27df..0000000
--- a/devices/m5stack/cardputer-adv/gaps-and-conflicts.md
+++ /dev/null
@@ -1,321 +0,0 @@
-# Cardputer ADV — gaps, conflicts and unresolved identities
-
-> Snapshot **2026-09-04**. Each entry states what the conflict is, who says what, what would
-> settle it, and — where I take a position — why.
-
-## Conflicts
-
-### C1 — The Mesh Kit page swaps UART TX and RX ✅ **resolved**
-
-`docs.m5stack.com/en/core/Cardputer_Mesh_Kit`'s "Cardputer-Adv EXT 2.54-14P" table gives
-pin 12 = `G13` = `UART_RX` and pin 14 = `G15` = `UART_TX`. Four sources say the opposite:
-the ADV product page's identical table, the schematic's own symbol pin names (`GPS-RX` on the
-G13 pin), `M5Cardputer-UserDemo`'s `uart_set_pin(port, GPIO_NUM_13 /*tx*/, GPIO_NUM_15 /*rx*/)`,
-and Meshtastic's `GPS_TX_PIN 13` / `GPS_RX_PIN 15`. **The Mesh Kit page even contradicts itself**
-two tables later, where its Cap-Bus table maps `G13 → GPS-RX`.
-
-**Position: G13 = host TX, G15 = host RX.** The Mesh Kit EXT table is a documentation defect.
-
-### C2 — Which Grove pin is SCL ⚠ **open, with a working answer**
-
-M5Unified's `_pin_table_i2c_ex_in` row for `board_M5CardputerADV`, under the header comment
-`// In SCL,SDA, EX SCL,SDA`, reads `{ …, GPIO_NUM_1, GPIO_NUM_2 }` → **EX SCL = G1** (white),
-**EX SDA = G2** (yellow). Bruce agrees (`-DGROVE_SCL=1`, `-DGROVE_SDA=2`). M5Stack's usual
-Grove colour convention puts SCL on **yellow**, which would invert it. The docs PinMap avoids
-the question entirely by naming the port `PORT.CUSTOM` and the pins `G2`/`G1`.
-
-The schematic sheet 1 shows `IIC_SCL` and `IIC_SDA` net labels near P1/J2, but the band-based
-text extraction could not bind them to individual pins, and no page render was cropped at that
-location in this pass.
-
-**What would settle it:** a 1:1 crop of ADV schematic sheet 1 around P1, or an I²C device
-plugged in and probed. **Practical answer: use the library values.** Whatever the silkscreen
-implies, `M5.Ex_I2C` will drive G1 as clock.
-
-### C3 — The v1.0 and v1.1 schematics are the same file ⚠ **open**
-
-`…/481/Sch_M5Cardputer.pdf` and `…/1127/Sch_M5Cardputer.pdf` are byte-identical
-(SHA-256 `6016c1fe6099b9e3f0d0c88f07a3fba1aa44a3da8a7a91dd7040ad0fffa2041e`, 717 743 B), as are
-the two base schematics (`29542fe1…`, 24 076 B).
-
-Two readings: (a) the v1.1 mainboard is genuinely unchanged and every difference is in the
-Stamp module — which M5Stack's own comparison table supports, since it lists only module-level
-differences; or (b) the v1.1 schematic was never published and the v1.0 file was reused.
-
-**Position: no mainboard change is documented, and I do not assert one either way.** Anyone
-with both boards in hand could settle it by comparing silkscreen revision markings.
-
-### C4 — The RGB/backlight warning appears on the v1.1 page but not the ADV page ⚠ **vendor gap**
-
-The v1.1 page: *"Since RGB and LCD backlight share the same power source, when the LCD backlight
-brightness is below 100%, RGB will not be powered properly."* The ADV page carries only the
-positive instruction ("set GPIO38 … to a high level") and **not** the warning — despite the ADV
-using the same Stamp-S3A and therefore the same AW35122FDR-switched `BL_3V3` rail feeding the
-same WS2812. Verified by comparing U3's `VDD` net across the two Stamp schematics.
-
-**Position: the warning applies to the ADV.** The omission is a documentation defect.
-
-### C5 — The Stamp-S3A schematic link is named for the wrong part ⚠ **cosmetic**
-
-Both the ADV and v1.1 pages label `…/1150/Sch_StampS3_v0.3.3.pdf` as *"Stamp-S3A Schematics
-PDF"*, while the filename says `StampS3`. The file's contents are unambiguously the S3A
-(AW35122FDR, JW5712, `BL_3V3`-fed WS2812), so this is a filename artefact, not a wrong link.
-Recorded because it is exactly the sort of thing that makes a future reader think they have the
-wrong document.
-
-### C6 — Vendor current figures are not internally consistent ⚠ **open**
-
-The ADV page gives 120.2 mA operating / 132.3 mA Wi-Fi / **154.6 mA BLE**. BLE drawing *more*
-than Wi-Fi is unusual and suggests the three measurements were taken with different display or
-CPU states, which M5Stack does not state. The v1.1 page publishes an entirely different set of
-conditions (*"IR transmission mode 148.07 mA, key mode 138.93 mA"*), so **the two generations'
-figures cannot be compared**.
-
-**What would settle it:** an instrumented measurement at a stated backlight level.
-
-### C7 — ⚠ Cross-session conflict: the Stamp-S3A's `U4` **is** labelled `JW5712` ✅ **resolved here**
-
-A concurrent session created
-[`components/unidentified/m5stack-stamp-s3a/dcdc-u4`](../../../components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md)
-on 2026-09-04, stating:
-
-> "**Manufacturer / part number:** ⚠ **NOT ESTABLISHED.** The `Sch_StampS3_v0.3.3.pdf` symbol
-> carries **no part-number text**."
-
-**That is incorrect, and the correction is easy to verify.** The part number is printed in the
-Altium Comment field directly beneath the symbol body.
-
-Evidence, all from the vendor's own published render:
-
-| Check | Result |
-|---|---|
-| Render used | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png`, SHA-256 `1156e645de35fe68e6458e9131657c8f02045bbcd14f97ab190bb1486ee7a1c5` — **re-fetched and hash-matched against the live URL** while writing this entry |
-| 1:1 crop, region `1000,3300–2200,3900` px | shows the yellow symbol with pins `EN`, `SW`, `VOS`, `VIN`, `VSEL1`, `VSEL2`, `VSEL3`, `GND`, and **`JW5712`** in blue immediately below the body |
-| Text-layer occurrences of `JW5712` | **1** in `Sch_StampS3_v0.3.3`, **0** in `Sch_M5StampS3_v0.2` |
-| Independent corroboration | the sibling record's own observed facts — *"IOUT: 0~0.6A"*, three `VSEL` strap pins, **no feedback divider**, `VOS` remote sense — match [`components/joulwatt/jw5712`](../../../components/joulwatt/jw5712/README.md) exactly: **600 mA continuous / 800 mA peak, 2.3–5.5 V in, eight resistor-free output voltages selected by three `VSEL` straps.** That record already existed, from the PaperMono pass on 2026-09-01, where the same part is fitted as `U10`. |
-
-**Probable cause of the disagreement:** the sibling record says the marker layer was parsed.
-Altium's `CO`/`PI`/`NL` markers are an *invisible* layer, and on these files the readable text —
-part numbers, values, net names — lives inside a **Form XObject** that a marker-only parse never
-enters. This session hit exactly the same trap and it failed *silently*, producing plausible-
-looking output containing none of the readable text
-([`commands.md`](commands.md) §4, attempt 3).
-
-**Position: Stamp-S3A `U4` is a JoulWatt `JW5712`.** A ready-to-paste correction, and the
-*Used By* rows this implies, are in
-[`scratch/m5stack-cardputer/index-fragments.md`](../../../scratch/m5stack-cardputer/index-fragments.md).
-That session's tree was **not edited** — its files were modified within the last 30 minutes.
-
-## Unresolved identities
-
-### U1 — The StampS3 v0.2 3.3 V regulator ✅ **resolved by a concurrent session**
-
-Designator `M2`, a 5-terminal EN/VIN/VOUT/FB/GND symbol with an R16 100 k / R17 22.1 k feedback
-divider. The value string extracted here was **`MUN3CAD01-SC`**, which this session flagged as
-suspect because it resembles an ON Semi dual digital transistor and does not match the symbol —
-and because **no page render exists** for product id `522` (the `_page_NN.png` convention 404s
-there) to check the reading against.
-
-**The reading was correct and the suspicion was wrong.** A concurrent session retrieved a
-datasheet and identified it as a **Murata `µPOL` 1 A point-of-load power module** — a
-fully-integrated converter, inductor and capacitors in a 2.9 × 2.3 × 1.05 mm package, 2.7–5.5 V
-in, 0.8–4.0 V out set by an external divider. That is exactly the 5-terminal EN/VIN/VOUT/FB/GND
-symbol observed. Record:
-[`components/murata/mun3cad01-sc`](../../../components/murata/mun3cad01-sc/README.md).
-
-Recorded here with the date because the skill asks for refuted hypotheses to be written down:
-**hypothesis "the `MUN3CAD01-SC` string is a mis-extraction" — refuted 2026-09-04.** Affects the
-Cardputer v1.0 only.
-
-### U2 — LP3218DT1G manufacturer
-
-Q1, Q2, Q3 on the ADV (and the same designators on the v1.x) carry the marking `LP3218DT1G` in
-the schematic value field. The manufacturer is not established. Recorded at
-[`components/unidentified/cardputer/lp3218dt1g`](../../../components/unidentified/cardputer/lp3218dt1g/README.md)
-rather than guessed.
-
-### U3 — BMI270 interrupt lines
-
-`INT1` (U7 pin 4) and `INT2` (U7 pin 9) appear on the schematic symbol. Neither was resolved to
-a GPIO by the text extraction, no vendor document mentions a BMI270 interrupt on this board, and
-M5Unified polls. **Stated as "not established", not as "absent"** — the difference matters,
-because if an interrupt *is* wired, IMU motion-wake from deep sleep becomes possible.
-
-**What would settle it:** a 1:1 crop of ADV sheet 3 around U7 pins 4 and 9.
-
-### U4 — The `+3.3V` feedback divider arithmetic does not work out
-
-Applying the sheet's own `Vout = 1.2 V × (R1/R2 + 1)` to the resistors read near the SY8089
-(R12 68 kΩ, R13 15 kΩ) gives ≈ 6.6 V, not 3.3 V. Either the resistor identification from the
-text layer is wrong (several `R` values sit close together on sheet 1), or the SY8089 uses a
-different feedback reference than the SY7088. **Recorded rather than fudged.** Do not use the
-computed number.
-
-## Gaps — things that appear not to exist
-
-Each of these is a **verified negative** (method stated), not a failed search.
-
-| Gap | Method | Result |
-|---|---|---|
-| **No RTC** | full designator census of all 4 ADV sheets; no 32.768 kHz crystal; no coin cell; no RTC row in the spec table; **positive control**: the CardputerZero page *does* list `RX8130CE @ 0x32` | verified absent |
-| **No IR receiver** | designator census; **positive control**: CardputerZero lists "IR transmitter + receiver" and an `IR_RX` pin | verified absent |
-| **No USB-UART bridge** | designator census of the Stamp-S3A sheet — `J2 USB-TYPEC`, CC resistors, PPTC, choke, ESD, no bridge IC | verified absent |
-| **No PSRAM** | `ESP32-S3FN8` is flash-in-package only; no external PSRAM on either Stamp schematic; every spec table omits PSRAM; community firmware compensates for its absence explicitly | verified absent |
-| **No fuel gauge** | designator census; battery sense is a divider on G10; **positive control**: CardputerZero lists `BQ27220YZFR` | verified absent |
-| **No reset button** | ADV spec table lists no buttons; sheet 1 has exactly `BTN1`, `BTN2`, `SW1`, `SW2`; **contrast**: the v1.1 table lists "1 × Reset button + 1 × User button" | verified absent on ADV |
-| **No ESD protection on the CAP header (P3)** | designator census of sheet 4 finds only `P3` | **inferred** — absence in a census, weaker than the above |
-| **No CAP board ID/presence-detect pin** | full P3 pinout accounted for | verified absent |
-
-## Gaps — things that exist but were not retrieved
-
-| Item | Status |
-|---|---|
-| **Certification (FCC/CE/TELEC)** | `docs.m5stack.com/en/certification` is a known **soft gap** (see [`vendors/m5stack`](../../../vendors/m5stack/README.md) §5.1). This pass did **not** run the required positive control on that page for the Cardputer, so the correct statement is *"not established"*, **not** *"no certification exists"*. |
-| `/en/product_i2c_addr` entry for the Cardputer family | not checked with a positive control |
-| Hardware design files (KiCad/Altium source) | `github.com/m5stack/M5_Hardware` has `Products/K132-Adv_Cardputer-Adv/Structures` and `Products/K152_Cardputer_Mesh_Kit/Structures` per the docs links — **the structure/CAD directories were not fetched in this pass** |
-| CardputerZero schematic, `CardputerZero_Labels.zip` | URLs recorded, not fetched |
-| M5Burner firmware records for the Cardputer family | the `/api/v1/firmwares/{id}` route is documented in the vendor guide; **no id was resolved for the ADV** in this pass |
-| EasyLoader binary `…/1178/Easy_Loader_for_Cardputer-Adv.exe` | URL recorded, **not downloaded** |
-| Per-switch net assignment for all 56 keys | the rule is verified at the array corner and by the driver; 54 switches were not individually traced |
-| "BKLVA Pocket DAW" repository | announced on Reddit three times; repository not located |
-| Hackaday coverage of the ADV | none found |
-| Any independent RF, audio, thermal or battery measurement | none found anywhere |
-| M5Stack community forum reports | **auth-walled**; no determination possible |
-
-## Refuted hypotheses, recorded with evidence
-
-| Hypothesis | Refuted by | Date |
-|---|---|---|
-| "The ADV keyboard matrix must be different, since the scanner changed" | Same 56 switches, same `Y0..Y7` nets, same R27–R34 22 Ω, and the two drivers' coordinate maths proved algebraically equivalent | 2026-09-04 |
-| "Cardputer v1.1 uses StampS3, ADV introduced Stamp-S3A" | M5Stack's own comparison table and the v1.1 page both say **v1.1 already uses Stamp-S3A**; only v1.0 uses StampS3 | 2026-09-04 |
-| "The Stamp-S3A added a load switch that the StampS3 lacked" | StampS3 v0.2 **already has** a load switch (SGM2578). What changed is the *WS2812's supply net*: `VDD_3V3` → `BL_3V3` | 2026-09-04 |
-| "`0x18` on the internal bus is an IMU" (per `Launcher/CardputerADV.md`) | `0x18` is `es8311_i2c_addr0` in M5Unified; the schematic prints `7-bit Address 69H` beside the BMI270 | 2026-09-04 |
-
-## Confirmed-correct existing documentation
-
-* [`vendors/m5stack/README.md`](../../../vendors/m5stack/README.md), written 2026-09-01 during
-  the PaperMono pass, was **accurate in every particular exercised here**: server-rendered HTML,
-  lowercase-slug 302s, the OSS numeric-product-id scheme, `search/suggest.json` →
-  `<handle>.json`, and the warning that `_page_NN.png` renders are not universal. New product
-  ids and one new trap are offered for appending in
-  [`../../../scratch/m5stack-cardputer/index-fragments.md`](../../../scratch/m5stack-cardputer/index-fragments.md).
-
----
-
-# 2026-09-07 — three open items closed by net tracing
-
-Appended beneath the existing text; nothing above is altered. Poppler became available on
-2026-09-07 and `pdftotext -bbox-layout` made net-level tracing of the schematic possible for the
-first time. Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-Full trace: [`schematic-netlist.md`](schematic-netlist.md).
-
-Each item below names the section above that it answers. All three are listed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-## ✅ C2 — "Which Grove pin is SCL" → **RESOLVED. SCL = G1, SDA = G2.**
-
-Answers **§ C2** above, which recorded *"the band-based text extraction could not bind them to
-individual pins, and no page render was cropped at that location in this pass."*
-
-Sheet 1, connector `J2` (`HY-2.0_IIC`):
-
-| `J2` pin | Symbol pin name | Net label on the wire | Module pin | Module's printed pin name |
-|---|---|---|---|---|
-| 1 | `IIC_SCL` | **`GI`** @ 737.32, 366.41 | `P1.1` @ 333.50, 394.37 | **`G1`** |
-| 2 | `IIC_SDA` | **`GO`** @ 738.58, 373.60 | `P1.2` @ 333.50, 401.37 | **`G2`** |
-| 3 | `VCC` | — | — | 5 V, ESD `D8` `PESDNC2FD5VB` |
-| 4 | `GND` | — | — | — |
-
-The reason this resisted every earlier attempt: **the net names are the literal strings `GI` and
-`GO`** — letter I, letter O — not `G1` and `G2`. Searching the text layer for "G1"/"G2" near `J2`
-finds nothing. This is not a font-mapping artefact: `G0` and `G1` both occur elsewhere on the
-same sheet and extract correctly. A 300 dpi crop shows the module symbol's own pin names printed
-immediately beside those labels in an unmistakable digit glyph — `G1` and `G2`. It is a vendor
-typo in the net names.
-
-**M5Unified and Bruce were right; the colour-convention worry was not.** `EX SCL = GPIO_NUM_1`
-and `EX SDA = GPIO_NUM_2` match the schematic exactly. The advice already given in § C2 — *"use
-the library values"* — was correct, and now has a primary-evidence basis rather than a pragmatic
-one.
-
-Independent corroboration on a different M5Stack product: the Cap-Bus connector uses the same
-`GI`/`GO` net names and pairs them with symbol pin names `SCL` and `SDA` respectively —
-[`devices/m5stack/cap-lora-1262/schematic-netlist.md`](../cap-lora-1262/schematic-netlist.md) §1.
-
-## ✅ U3 — "BMI270 interrupt lines" → **RESOLVED. Neither is routed.**
-
-Answers **§ U3** above, which asked for *"a 1:1 crop of ADV sheet 3 around U7 pins 4 and 9"* and
-correctly insisted on "not established" rather than "absent". It is now **absent**.
-
-A row query across the *entire* sheet at each pin's y returns only `U7`'s own tokens:
-
-```
-python3 trace.py row <bbox> --y 167.37 --tol 4 --page 3     # INT1, U7 pin 4
-  p3 x=157.00 y=167.37  PIU704     p3 x=157.53 y=164.84  4
-  p3 x=176.83 y=168.44  INT1       p3 x=208.60 y=168.44  ASDX
-  p3 x=229.00 y=167.37  PIU702     p3 x=229.72 y=164.84  2
-```
-
-No net label, no other component pin, no power port lies at that height anywhere on the page. The
-same holds at y = 174.37 (`INT2`, pin 9) and at the four unused OIS pins (2 `ASDX`, 3 `ASCX`,
-10 `OCSB`, 11 `OSDO`). By contrast pin 8's row *does* return `PIC2502`, `PIC2702`, `PIFB701/02`
-and `+3.3V`, which shows the query finds connections when they exist.
-
-**Consequence:** IMU motion-wake from deep sleep is **not possible on the ADV**. M5Unified's
-polling is forced by the hardware, not a library shortcoming.
-
-While tracing, the rest of `U7` was recovered and is worth recording:
-`SDX` (14) = **G8**, `SCX` (13) = **G9**, `SDO` (1) pulled to `+3.3V` by `R43` 3.3 kΩ giving
-address **0x69** — which matches the `7-bit Address 69H` the sheet prints at (196.71, 114.51) and
-confirms § "Corrections" above, where `0x18` was already rejected.
-
-## ✅ U4 — "The `+3.3V` feedback divider arithmetic does not work out" → **RESOLVED. It does.**
-
-Answers **§ U4** above. Two separate mistakes produced the impossible 6.6 V.
-
-**Mistake 1 — the upper resistor is `R11`, not `R12`.** `R11` is 68 kΩ at `COR11` (697.50,
-214.20). `R12` is **100 kΩ** at `COR12` (236.50, 221.20) — 460 pt away on the other side of the
-sheet, in an unrelated network. The § U4 note above anticipated exactly this: *"several `R`
-values sit close together."*
-
-The `U4` feedback column is unambiguous once the coordinates are read:
-
-```
-PIR1102 @ 690, 206.9  -> the +3.3V rail row (y 203.8)
-PIR1101 @ 690, 228.9 -+
-                      |-- FB node; U4.5 (FB) @ 640, 232.37
-PIR1302 @ 691, 235.6 -+
-PIR1301 @ 691, 258.2  -> GND (y 280.1)
-R11 = 68KΩ (702, 222.4)      R13 = 15KΩ (702, 251.4)
-```
-
-**Mistake 2 — the printed formula belongs to a different converter.**
-`Vout=1.2V*(R1/R2+1)` sits at (612.67, 157.65), directly beneath the **SY7088 boost `U2`**
-(symbol y 63–135), ~86 pt above the SY8089. Applied to `U2`'s own divider — `R4` 75 kΩ / `R6`
-22 kΩ — it gives 1.2 × (75/22 + 1) = **5.29 V**, which is self-consistent for the `+5VOUT` rail.
-It was never the SY8089's formula.
-
-With the correct pair, 3.3 V requires a feedback reference of
-3.3 / (68/15 + 1) = **0.596 V**; a 0.6 V reference makes the design exact to 0.7 %.
-
-⚠ **Evidence status:** the 0.596 V figure is *derived from the sheet*. **No SY8089 datasheet is
-held in this repository**, so it is not read from a primary document. The second option offered
-in § U4 — *"the SY8089 uses a different feedback reference than the SY7088"* — is the correct
-one, and the value it needs is 0.6 V.
-
-Also noted, and not a defect: **`U2`'s `+5VOUT` rail is designed to 5.29 V, not 5.00 V.** The
-same vendor does the same thing on the DinMeter, whose SY7088 Grove rail computes to 5.38 V.
-That is a deliberate idiom, not an arithmetic error — see
-[`devices/m5stack/dinmeter/schematic-netlist.md`](../dinmeter/schematic-netlist.md) §3.
-
-## New material, not a correction
-
-- **`U9` `TCA8418RTWR` fully traced** — `INT` = G11, `SCL` = G9, `SDA` = G8, address `0x34`
-  printed on the sheet, `ROW7` unconnected (7 rows × 8 columns), `R35`/`R36`/`R37` 3.3 kΩ
-  pulling up `SDA`, `SCL` **and** `INT`. See [`schematic-netlist.md`](schematic-netlist.md) §4.
-- **Vendor driver audited against the sheet and the register map** —
-  [`driver-vs-document-audit.md`](driver-vs-document-audit.md). Six findings, all labelled active
-  or inert; the driver's pin assignments and matrix size all agree with the schematic.
-- **Acquisition gap exposed:** no TCA8418 datasheet is retained, so three register-semantics
-  findings rest on the vendored header rather than on TI `SCPS215`.
diff --git a/devices/m5stack/cardputer-adv/market-and-pricing.md b/devices/m5stack/cardputer-adv/market-and-pricing.md
deleted file mode 100644
index 4c1c8e9..0000000
--- a/devices/m5stack/cardputer-adv/market-and-pricing.md
+++ /dev/null
@@ -1,155 +0,0 @@
-# Cardputer ADV — market and pricing
-
-> All observations **2026-09-04** unless stated. Prices are M5Stack's own store in **USD**,
-> before shipping and before any tax or duty. Retrieved from Shopify's
-> `search/suggest.json` and `<handle>.json` endpoints — machine-readable, so the figures are
-> the store's own, not read off a rendered page.
-
-## Official store, dated
-
-| Product | Handle | Price (USD) | In stock | Shopify id | `created_at` | `published_at` |
-|---|---|---|---|---|---|---|
-| **M5Stack Cardputer Adv Version (ESP32-S3)** | `m5stack-cardputer-adv-version-esp32-s3` | **29.90** | yes | 8904041857281 | 2025-09-04 | 2025-09-05 |
-| **`[EOL]` M5Stack Cardputer with M5StampS3 v1.1** | `m5stack-cardputer-with-m5stamps3-v1-1` | **29.90** | yes | 8741357388033 | 2025-03-07 | 2025-03-07 |
-| **Cardputer Mesh Kit for Meshtastic (ESP32-S3)** | `cardputer-mesh-kit-for-meshtastic-esp32-s3` | **48.00** | yes | 9135211610369 | 2026-04-30 | 2026-04-30 |
-| Cap LoRa 1262 for Cardputer Adv (SX1262, ATGM336H) | `cap-lora-1262-for-cardputer-adv-sx1262-atgm336h` | **14.50** | yes | — | — | — |
-| Cap CC1101 & NFC for Cardputer Adv | `cap-cc1101-nfc-for-cardputer` | **18.95** | yes | — | — | — |
-| Cardputer Accessory Kit v1.1 (M5StampS3A + Display) | `cardputer-accessory-kit-v1-1-m5stamps3a-display` | **9.95** | yes | 8829253157121 | 2025-07-03 | 2025-07-04 |
-
-**The v1.1 is marked `[EOL]` in its own title but is still listed, still priced at $29.90 and
-still marked available.** Read that as "old stock at the same price as the current model", which
-makes it a poor buy at parity — see [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md).
-
-### Bundle arithmetic
-
-ADV $29.90 + Cap LoRa-1262 $14.50 = **$44.40**, versus the Mesh Kit at **$48.00**. The $3.60
-premium buys the rubber-duck RP-SMA antenna, two M2 screws, a hex key, a green back shell, a
-safety sticker — and, materially, **eligibility for Meshtastic device registration**, which
-M5Stack states is restricted: *"Only devices in the Cardputer Mesh Kit set can be registered.
-Other Cardputer/-Adv devices are not eligible for Meshtastic authorization registration."*
-
-If you want a licensed Meshtastic node, buy the kit. If you want a LoRa radio, buy the parts.
-An r/meshtastic thread of **2026-03-11** frames the same question — *"Any reason not to just get
-a Cardputer with lora cap for 55 bucks total even after ship?"*, 19 comments — from before the
-kit existed.
-
-## Channels
-
-| Channel | Evidence |
-|---|---|
-| **M5Stack official store** (`shop.m5stack.com`) | prices above, retrieved 2026-09-04 |
-| **AliExpress** (`m5stack.aliexpress.com/store/911661199`) | M5Stack's own storefront, linked from every docs page footer. **Prices not retrieved in this pass.** |
-| **Amazon** (`amazon.com/shops/m5stack`) | official storefront, linked from the docs footer. **Not retrieved.** |
-| **Taobao** (`m5stack.taobao.com`) | official, CN market. **Not retrieved.** |
-| **Distributors** (`m5stack.com/distributor`) | regional resellers — Mouser, Digi-Key and others typically carry M5Stack. **Not enumerated.** |
-| Used / refurbished | **no observations gathered** |
-
-Only the official-store figures above are dated and verified. **No AliExpress, Amazon,
-distributor or used-market price was collected**, so this record cannot support a price *range*,
-a street-price claim, or a regional comparison. Stated plainly rather than estimated.
-
-## Clones
-
-**None found.** Searching GitHub for `cardputer` returned 100 repositories, all software or
-accessories for the genuine article; no clone hardware appeared in the Reddit sample either.
-That is unsurprising: the value is in the keyboard tooling and the case, and the board is
-already $29.90.
-
-The nearest thing to a "compatible" is the **Cardputer Accessory Kit v1.1** ($9.95), which is a
-genuine M5Stack spare — a Stamp-S3A plus a display. It is **not** an ADV upgrade path; the ADV's
-differences are on the mainboard.
-
-⚠ **A negative from one day's searching in English and on GitHub/Reddit is weak evidence.**
-Taobao and AliExpress were not searched. Treat "no clones" as *not found*, not *do not exist*.
-
-## Total cost of a working setup
-
-| Configuration | Cost | Notes |
-|---|---|---|
-| ADV alone | $29.90 | includes the 1750 mAh battery |
-| ADV + microSD | ~$35 | no card included; no vendor card guidance exists |
-| ADV + Cap LoRa-1262 + antenna | ~$46–50 | antenna sold with the kit, separately otherwise |
-| **Mesh Kit** | **$48.00** | complete, licensed, ready to use |
-| ADV + Cap CC1101 & NFC | $48.85 | the sub-GHz/NFC configuration |
-| Everything | ~$68 | ADV + both Caps |
-
-Shipping, duty and tax are **not** included and vary by destination. The r/CardPuter thread of
-2026-05-31 is a reminder that for many buyers these dominate: the poster describes shipping and
-customs as the reason a Flipper Zero was out of reach in the first place.
-
-## Second-hand and repair economics
-
-* **Spares are hard to get.** r/M5Stack, 2026-08-05: *"I'm looking for screws and buttons of the
-  right height for the Cardputer ADV, but I can't find them on AE."* Replies point at a generic
-  M5Stack M3 screw pack and 3D printing. M5Stack does not stock ADV-specific mechanical spares.
-* **The battery is internal**, with no published cell part number, so a worn cell is a repair
-  job rather than a swap.
-* One Reddit reply (2026-05-31) claims people *"resell it x3 price"* — an unsupported assertion
-  from a joking comment, recorded only to note that no actual used-market data was found.
-
-## Market fit
-
-**At launch (September 2025):** a same-price replacement for a popular board, offering
-peripherals rather than compute. A reasonable first purchase; a marginal upgrade.
-
-**At this snapshot (September 2026):** the ADV is the only Cardputer worth buying new. The v1.1
-is `[EOL]` at the same money, the accessory line is ADV-only, and upstream Meshtastic supports
-only the ADV. At $29.90 with a 1750 mAh cell, a codec, an IMU and an expansion socket, it is
-priced below what the parts alone would suggest.
-
-See the applicable genre guidance and the tier-by-tier alternatives in
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md).
-
----
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| M5Stack Cardputer Adv Version (ESP32-S3) | 2025-09-05 | Default Title | `K132-ADV` | **USD 29.90** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 29.90, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/m5stack-cardputer-adv-version-esp32-s3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `K132-ADV`. In stock.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cardputer-adv/media.md b/devices/m5stack/cardputer-adv/media.md
deleted file mode 100644
index 338b69d..0000000
--- a/devices/m5stack/cardputer-adv/media.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# Cardputer ADV — images and provenance
-
-> Snapshot **2026-09-04**. Machine-readable form: [`media/manifest.json`](media/manifest.json).
-
-## Rights position
-
-**No M5Stack product photograph or render is retained in this repository.**
-[`vendors/m5stack`](../../../vendors/m5stack/README.md) §8 records that M5Stack product imagery
-carries **no redistribution licence**; the PaperMono pass reached the same conclusion and
-retained none either. Redistribution status for every vendor image below is therefore
-**`unknown`** and disposition **`reference-only`** — URL, description and provenance recorded,
-bytes not committed.
-
-**Schematic sheet renders** are a different case only in degree: they are also unlicensed, but
-they are *technical* documents rather than marketing assets, and reading them was necessary to
-produce this record. They were fetched into **scratch** (which lives in the separate archive
-repository), used to make the crops that every transcribed value came from, and **not** committed
-here. The schematic **PDF** itself *is* retained under `artifacts/schematic/`, matching how this
-repository already treats M5Stack schematics elsewhere.
-
-## Vendor product imagery — recorded, not retained
-
-| # | URL | Shows | Retrieved | Rights |
-|---|---|---|---|---|
-| 1–13 | `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_{01..13}.webp` | product renders: front, back showing the **CAP header**, edge with the **3.5 mm jack**, keyboard detail, base magnets, lanyard hole | 2026-09-04 | unknown / reference-only |
-| 14 | `…/1178/K132-Adv-weight.jpg` | scale photo establishing **81.0 g** | 2026-09-04 | unknown |
-| 15 | `…/1178/Cardputer-Adv_14.jpg` | charging illustration accompanying the "switch must be ON" note | 2026-09-04 | unknown |
-| 16 | `…/1178/Cardputer-Adv_operation_01.jpg` + `…_operation.gif` | download-mode procedure | 2026-09-04 | unknown |
-| 17 | **`…/1178/IMU-Cardputer-Adv.jpg`** | **BMI270 axis orientation** — the only vendor image with information not available in text | 2026-09-04 | unknown |
-| 18 | `…/1127/K132_v11_04.webp`, `…/1127/K132-V11_21.jpg` | v1.1 comparison and charging images | 2026-09-04 | unknown |
-| 19 | `static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-a02d6727-….webp` | v1.0 render used in the comparison table — note the **different CDN host** for older assets | 2026-09-04 | unknown |
-
-⚠ Image 17 is the one worth fetching if you need it: IMU axis conventions differ between M5Stack
-boards, and the orientation is **not** stated in text anywhere.
-
-## Schematic sheet renders — in scratch, not committed
-
-| File | Source URL | Size | Used for |
-|---|---|---|---|
-| `adv-sch-page_01.png` | `…/1178/Sch_M5CardputerAdv_v1.0_…_page_01.png` | 5848×4132, 1 053 746 B | power train: TP4057, CN809J, SY7088 + FB divider, LP3218DT1G ×3, **the DNP marking on R3/D3** |
-| `adv-sch-page_02.png` | `…_page_02.png` | 679 172 B | **TCA8418 pinout, three explicit no-connects, R27–R34 22 Ω, the switch matrix, ROW-bus pairing, S1→Y7 / S2→Y3** |
-| `adv-sch-page_03.png` | `…_page_03.png` | 540 294 B | ES8311, NS4150B, MSM381A3729H9BP, BMI270 with its printed `7-bit Address 69H`, PJ-342 |
-| `adv-sch-page_04.png` | `…_page_04.png` | 205 150 B | the EXT/CAP header P3 |
-| `v11-sch_01.png`, `v11-sch_02.png` | `…/1127/Sch_M5Cardputer_sch_0{1,2}.png` | 1 157 389 / 570 484 B | **74HC138 pinout and the identical Y-net structure** |
-| `stamps3a-sch_01.png` | `…/1150/Sch_StampS3_v0.3.3_page_01.png` | 1 483 535 B | **AW35122FDR gating `BL_3V3`, WS2812 on `BL_3V3`, JW5712, USB front end with no bridge** |
-| `522/Sch_M5StampS3_v0.2_page_01.png` | — | **402 B, not a PNG** | **does not exist** — recorded as a dead URL |
-
-### Crops derived from them
-
-Nine crops made with `scratch/m5stack-cardputer/pngcrop.py`. Each is a **mechanical crop and
-min-pool downscale** of a vendor render — **no annotation, no rotation, no watermark removal**.
-Listed with their exact arguments in [`commands.md`](commands.md) §6, so any of them can be
-regenerated byte-for-byte from the source PNG.
-
-| Crop | Region (px) | den | What it established |
-|---|---|---|---|
-| `crop-adv-kbd-u9.png` | 200,800–1900,2150 | 2 | complete TCA8418 pin table |
-| `crop-adv-kbd-matrix.png` | 1650,1300–3300,2900 | 2 | switch-array structure, `Y0..Y7` bus |
-| `crop-adv-kbd-s1s2.png` | 1650,1380–2560,1800 | **1** | **S1→Y7, S2→Y3** |
-| `crop-adv-kbd-rowbus.png` | 1600,850–3300,1420 | 2 | `ROW`*n* → column pair (2n, 2n+1) |
-| `crop-v11-kbd-u7.png` | 200,1350–1900,2150 | 2 | 74HC138 pin table, same R27–R34 |
-| `crop-adv-pwr1.png` | 200,200–2450,1300 | 3 | TP4057 + R1/R5, CN809J + R7, Q1–Q3 |
-| `crop-adv-pwr2.png` | 2400,200–4700,1300 | 3 | SY7088 + FB 75 k/22 k, **greyed-out R3/D3** |
-| `crop-stamp-a.png` | 200,200–3000,2200 | 4 | ESP32-S3FN8, antenna network, X1 40 MHz |
-| `crop-stamp-b.png` | 2800,200–5800,2200 | 4 | **AW35122FDR → `BL_3V3` → WS2812** |
-
-## Images that would improve this record
-
-| Wanted | Why |
-|---|---|
-| Underside photo showing the **CAP header** with a scale reference | the only way to confirm the physical pin-1 marking against the three numbering schemes |
-| **PCB photograph, board removed** | would let a reader confirm the designator census independently and settle U1–U4 |
-| **Silkscreen revision marking**, v1.0 vs v1.1 | would settle conflict C3 |
-| A 1:1 crop of ADV sheet 3 around **U7 pins 4 and 9** | would settle whether the BMI270 interrupts are routed |
-| A 1:1 crop of ADV sheet 1 around **P1** | would settle the Grove SCL/SDA conflict |
-
-The last two need no new hardware or rights — only another pass over PNGs already identified.
diff --git a/devices/m5stack/cardputer-adv/media/manifest-schematic-crops.json b/devices/m5stack/cardputer-adv/media/manifest-schematic-crops.json
deleted file mode 100644
index 817c8ec..0000000
--- a/devices/m5stack/cardputer-adv/media/manifest-schematic-crops.json
+++ /dev/null
@@ -1,99 +0,0 @@
-{
-  "$schema-note": "Image provenance manifest for images DERIVED from retained schematic PDFs by local rasterisation. Kept separate from media/manifest.json so that no pre-existing file is modified; an index owner may merge them.",
-  "device": "m5stack/cardputer-adv",
-  "generated": "2026-09-07",
-  "generator": "2026-09-07 schematic net-tracing pass; poppler 26.06.0 + ImageMagick",
-  "global_notes": [
-    "These are NOT photographs and NOT vendor-published images. Each is a crop of a page the vendor published as a vector PDF, rasterised locally at 300 dpi.",
-    "pdfimages could not be used: pdfimages -list reports ZERO embedded rasters in every source PDF here. The drawings are vector, so pdftoppm plus a crop is the only route. This is recorded because reaching for pdfimages is the obvious wrong first move.",
-    "Copyright in the underlying drawing remains with the vendor named in creator_rightsholder. Licence is UNKNOWN: no licence statement appears in any of the source PDFs. Redistribution status unknown; disposition repository, unstaged pending user review.",
-    "Every image is reproducible byte-for-byte from the retained artifact using the recorded generation_command, so none of them is uniquely held here.",
-    "Each image exists because it settles a specific documented question; see why_retained."
-  ],
-  "images": [
-    {
-      "local_path": "media/schematic-sheet1-J2-grove-GI-GO.png",
-      "filename": "schematic-sheet1-J2-grove-GI-GO.png",
-      "sha256": "472ab263a9263e0709aa50beda95fc6561ad45207ac9234205a262597da23470",
-      "bytes": 28143,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export; 4 pages, 842x595 pt A4 landscape; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 1500x300+2750+1470 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "1500x300+2750+1470",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "Cardputer ADV v1.0",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: Grove port J2 (HY-2.0_IIC) with net labels GI and GO",
-      "alt_text": "Schematic detail of a four-pin connector symbol J2, captioned HY-2.0_IIC, whose pin names read IIC_SCL, IIC_SDA, VCC, GND. Two dark-red net labels on the incoming wires read GI and GO, in a serif font where the second character of each is unmistakably a letter I and a letter O rather than a digit. Three ESD diodes D6, D7, D8 sit below.",
-      "why_retained": "Shows that the Grove net names really are the letters GI and GO, which is why every text search for G1 or G2 near this connector failed."
-    },
-    {
-      "local_path": "media/schematic-sheet1-M1-pin-names-G1-G2.png",
-      "filename": "schematic-sheet1-M1-pin-names-G1-G2.png",
-      "sha256": "3f5867c241f7e4d01182559d34314d983869903a73d95e38422dff75e01eee04",
-      "bytes": 25157,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export; 4 pages, 842x595 pt A4 landscape; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 700x260+1350+1590 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "700x260+1350+1590",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "Cardputer ADV v1.0",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: module footprint pin names G1/G2 beside the GI/GO net labels",
-      "alt_text": "Schematic detail showing a yellow module symbol whose printed pin names are G1, G2, G3, G4, G5, G6, G7 in an unmistakable digit glyph, with the dark-red net labels GI, GO, G3, G4, G5, G6, G7 on the wires entering pins 1 to 7.",
-      "why_retained": "The decisive comparison: the same crop contains both the digit glyph (module pin names) and the letter glyph (net labels), proving the GI/GO strings are a vendor typo and that Grove SCL is GPIO1 and SDA is GPIO2."
-    },
-    {
-      "local_path": "media/schematic-sheet3-U7-bmi270-int-unrouted.png",
-      "filename": "schematic-sheet3-U7-bmi270-int-unrouted.png",
-      "sha256": "0d4b83885aa9daab9b7bc21fc9474ded6f6dffe92fc150c562b17654b25c6f4d",
-      "bytes": 66432,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf",
-      "derived_from_page": 3,
-      "source_pdf_metadata": "Altium Designer export; 4 pages, 842x595 pt A4 landscape; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 3 -l 3 -r 300 -png <pdf> /tmp/page && magick /tmp/page-3.png -crop 1150x600+380+480 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "1150x600+380+480",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "Cardputer ADV v1.0",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: BMI270 (U7) showing INT1 and INT2 with nothing attached",
-      "alt_text": "Schematic detail of a fourteen-pin IC symbol U7 labelled BMI270. Pins 14 SDX and 13 SCX carry net labels G8 and G9 on wires leaving to the left; pin 1 SDO goes to a pull-up. Pins 4 INT1 and 9 INT2 have bare stubs with no wire, no net label and no connection. Pin 8 VDD goes right through ferrite bead FB7 to +3.3V with C25 and C27.",
-      "why_retained": "Visual confirmation of the negative result that neither BMI270 interrupt line is routed on this board, which removes IMU motion-wake from deep sleep as an option."
-    }
-  ]
-}
diff --git a/devices/m5stack/cardputer-adv/media/manifest.json b/devices/m5stack/cardputer-adv/media/manifest.json
deleted file mode 100644
index cb6655d..0000000
--- a/devices/m5stack/cardputer-adv/media/manifest.json
+++ /dev/null
@@ -1,616 +0,0 @@
-{
-  "schema": "hardware-doc/media-manifest/1",
-  "device": "devices/m5stack/cardputer-adv",
-  "snapshot": "2026-09-04",
-  "rights_policy": "M5Stack imagery carries no redistribution licence (vendors/m5stack README section 8). All vendor images are reference-only: URL and provenance recorded, bytes not committed to this repository.",
-  "items": [
-    {
-      "id": "adv-render-01",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_01.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 1 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-02",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_02.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 2 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-03",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_03.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 3 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-04",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_04.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 4 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-05",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_05.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 5 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-06",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_06.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 6 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-07",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_07.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 7 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-08",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_08.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 8 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-09",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_09.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 9 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-10",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_10.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 10 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-11",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_11.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 11 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-12",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_12.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 12 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-render-13",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_13.webp",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "M5Stack product render 13 of 13 of the Cardputer ADV.",
-      "alt": "Product render of the M5Stack Cardputer ADV, a card-sized computer with a 56-key keyboard and small landscape LCD.",
-      "shows": "exterior product render",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-weight",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-weight.jpg",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Scale photograph establishing the 81.0 g product weight.",
-      "alt": "Cardputer ADV on a digital kitchen scale.",
-      "shows": "weight verification",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-charging",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_14.jpg",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Illustration accompanying the note that the power switch must be ON to charge.",
-      "alt": "Cardputer ADV with the side power switch highlighted.",
-      "shows": "charging procedure",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-Cardputer-Adv_operation_01",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_operation_01.jpg",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Download-mode procedure: switch OFF, hold G0, apply power, release.",
-      "alt": "Animated demonstration of entering download mode on the Cardputer ADV.",
-      "shows": "download mode procedure",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-Cardputer-Adv_operation",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Cardputer-Adv_operation.gif",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Download-mode procedure: switch OFF, hold G0, apply power, release.",
-      "alt": "Animated demonstration of entering download mode on the Cardputer ADV.",
-      "shows": "download mode procedure",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-imu-axes",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/IMU-Cardputer-Adv.jpg",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "BMI270 triaxial orientation diagram. The only vendor image carrying information not available in text.",
-      "alt": "Diagram showing the X, Y and Z axis directions of the BMI270 relative to the Cardputer ADV body.",
-      "shows": "IMU axis convention",
-      "value": "high \u2014 axis conventions differ between M5Stack boards and are not stated in prose",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "reference-only",
-      "repository_state": "not-downloaded",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-sch-p1",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_01.png",
-      "bytes": 1053746,
-      "dimensions": "5848x4132",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Vendor per-sheet render of the published schematic.",
-      "alt": "Rendered schematic sheet from the M5Stack published PDF.",
-      "shows": "power train: TP4057 charger, CN809J supervisor, SY7088 boost with its feedback divider, three LP3218DT1G power-path FETs, and the depopulated R3/D3 charge indicator",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "note": "Fetched into scratch/m5stack-cardputer/media/ and used to produce the crops from which every transcribed value was read. The schematic PDF itself is retained under artifacts/schematic/.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-sch-p2",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_02.png",
-      "bytes": 679172,
-      "dimensions": "5848x4132",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Vendor per-sheet render of the published schematic.",
-      "alt": "Rendered schematic sheet from the M5Stack published PDF.",
-      "shows": "TCA8418RTWR keypad scanner, its three explicit no-connects, the R27-R34 22 ohm series resistors, and the 56-switch matrix",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "note": "Fetched into scratch/m5stack-cardputer/media/ and used to produce the crops from which every transcribed value was read. The schematic PDF itself is retained under artifacts/schematic/.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-sch-p3",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_03.png",
-      "bytes": 540294,
-      "dimensions": "5848x4132",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Vendor per-sheet render of the published schematic.",
-      "alt": "Rendered schematic sheet from the M5Stack published PDF.",
-      "shows": "ES8311 codec, NS4150B amplifier, MSM381A3729H9BP microphone, BMI270 with its printed 7-bit address 69H, and the PJ-342 jack detect network",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "note": "Fetched into scratch/m5stack-cardputer/media/ and used to produce the crops from which every transcribed value was read. The schematic PDF itself is retained under artifacts/schematic/.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "adv-sch-p4",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_04.png",
-      "bytes": 205150,
-      "dimensions": "5848x4132",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Vendor per-sheet render of the published schematic.",
-      "alt": "Rendered schematic sheet from the M5Stack published PDF.",
-      "shows": "the EXT 2.54-14P CAP header P3, with net names and symbol pin names",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "note": "Fetched into scratch/m5stack-cardputer/media/ and used to produce the crops from which every transcribed value was read. The schematic PDF itself is retained under artifacts/schematic/.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "v11-sch-p1",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer_sch_01.png",
-      "bytes": 1157389,
-      "dimensions": "5848x4132",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Vendor per-sheet render of the published schematic.",
-      "alt": "Rendered schematic sheet from the M5Stack published PDF.",
-      "shows": "Cardputer v1.0/v1.1 mainboard sheet 1",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "note": "Fetched into scratch/m5stack-cardputer/media/ and used to produce the crops from which every transcribed value was read. The schematic PDF itself is retained under artifacts/schematic/.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "v11-sch-p2",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer_sch_02.png",
-      "bytes": 570484,
-      "dimensions": "5848x4132",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Vendor per-sheet render of the published schematic.",
-      "alt": "Rendered schematic sheet from the M5Stack published PDF.",
-      "shows": "the 74HC138 keyboard decoder and the identical Y0..Y7 net structure",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "note": "Fetched into scratch/m5stack-cardputer/media/ and used to produce the crops from which every transcribed value was read. The schematic PDF itself is retained under artifacts/schematic/.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "stamps3a-sch-p1",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png",
-      "bytes": 1483535,
-      "dimensions": "5848x4132",
-      "source_page": "https://docs.m5stack.com/en/core/Cardputer-Adv",
-      "caption": "Vendor per-sheet render of the published schematic.",
-      "alt": "Rendered schematic sheet from the M5Stack published PDF.",
-      "shows": "Stamp-S3A: AW35122FDR load switch gating BL_3V3, WS2812 fed from BL_3V3, JW5712 buck, and a USB front end with no UART bridge",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "note": "Fetched into scratch/m5stack-cardputer/media/ and used to produce the crops from which every transcribed value was read. The schematic PDF itself is retained under artifacts/schematic/.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "stamps3-v02-render-DEAD",
-      "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2_page_01.png",
-      "caption": "DEAD URL. Returns 402 bytes that are not a PNG. The _page_NN.png render convention does not apply to product id 522.",
-      "alt": "n/a",
-      "shows": "nothing",
-      "repository_state": "not-downloaded",
-      "disposition": "reference-only",
-      "result": "failed - not a PNG",
-      "note": "Recorded so a future pass does not retry. Not retained under a .png extension.",
-      "creator": "M5Stack Technology Co., Ltd",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "modifications": "none",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-adv-kbd-u9",
-      "derived_from": "adv-sch-p2",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 200,800,1900,2150 px, min-pool downscale factor 2.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "complete TCA8418 pin table including three explicit no-connect markers",
-      "modifications": "crop to 200,800,1900,2150; min-pool downscale by 2; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-adv-kbd-u9.png 200 800 1900 2150 2",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-adv-kbd-matrix",
-      "derived_from": "adv-sch-p2",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 1650,1300,3300,2900 px, min-pool downscale factor 2.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "switch array structure and the Y0..Y7 column bus",
-      "modifications": "crop to 1650,1300,3300,2900; min-pool downscale by 2; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-adv-kbd-matrix.png 1650 1300 3300 2900 2",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-adv-kbd-s1s2",
-      "derived_from": "adv-sch-p2",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 1650,1380,2560,1800 px, min-pool downscale factor 1.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "S1 connects to Y7 and S2 to Y3, verifying the driver remap arithmetic",
-      "modifications": "crop to 1650,1380,2560,1800; min-pool downscale by 1; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-adv-kbd-s1s2.png 1650 1380 2560 1800 1",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-adv-kbd-rowbus",
-      "derived_from": "adv-sch-p2",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 1600,850,3300,1420 px, min-pool downscale factor 2.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "ROW n feeds keyboard column pair 2n / 2n+1",
-      "modifications": "crop to 1600,850,3300,1420; min-pool downscale by 2; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-adv-kbd-rowbus.png 1600 850 3300 1420 2",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-v11-kbd-u7",
-      "derived_from": "v11-sch-p2",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 200,1350,1900,2150 px, min-pool downscale factor 2.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "74HC138 pin table with the same R27-R34 series resistors as the ADV",
-      "modifications": "crop to 200,1350,1900,2150; min-pool downscale by 2; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-v11-kbd-u7.png 200 1350 1900 2150 2",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-adv-pwr1",
-      "derived_from": "adv-sch-p1",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 200,200,2450,1300 px, min-pool downscale factor 3.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "TP4057 with R1 0.8 ohm and R5 3.3k, CN809J with R7, Q1-Q3",
-      "modifications": "crop to 200,200,2450,1300; min-pool downscale by 3; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-adv-pwr1.png 200 200 2450 1300 3",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-adv-pwr2",
-      "derived_from": "adv-sch-p1",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 2400,200,4700,1300 px, min-pool downscale factor 3.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "SY7088 with FB 75k/22k and the greyed-out R3/D3 charge LED",
-      "modifications": "crop to 2400,200,4700,1300; min-pool downscale by 3; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-adv-pwr2.png 2400 200 4700 1300 3",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-stamp-a",
-      "derived_from": "stamps3a-sch-p1",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 200,200,3000,2200 px, min-pool downscale factor 4.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "ESP32-S3FN8, antenna matching network, X1 40 MHz crystal",
-      "modifications": "crop to 200,200,3000,2200; min-pool downscale by 4; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-stamp-a.png 200 200 3000 2200 4",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    },
-    {
-      "id": "crop-stamp-b",
-      "derived_from": "stamps3a-sch-p1",
-      "url": null,
-      "caption": "Mechanical crop of the vendor sheet render, region 2800,200,5800,2200 px, min-pool downscale factor 4.",
-      "alt": "Cropped region of a rendered schematic sheet.",
-      "shows": "AW35122FDR driven by DISP_BL producing BL_3V3, which supplies the WS2812",
-      "modifications": "crop to 2800,200,5800,2200; min-pool downscale by 4; no annotation, rotation or watermark removal",
-      "tool": "scratch/m5stack-cardputer/pngcrop.py",
-      "reproduce": "python3 pngcrop.py <parent>.png crop-stamp-b.png 2800 200 5800 2200 4",
-      "disposition": "local-cache",
-      "repository_state": "scratch (archive repo), not committed here",
-      "creator": "M5Stack Technology Co., Ltd (source render); crop is mechanical",
-      "retrieved": "2026-09-04",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "applies_to": "K132-Adv"
-    }
-  ],
-  "counts": {
-    "vendor_product_images_recorded": 18,
-    "schematic_renders": 7,
-    "crops": 9,
-    "dead_urls": 1,
-    "bytes_committed_to_this_repository": 0
-  }
-}
diff --git a/devices/m5stack/cardputer-adv/media/schematic-sheet1-J2-grove-GI-GO.png b/devices/m5stack/cardputer-adv/media/schematic-sheet1-J2-grove-GI-GO.png
deleted file mode 100644
index fbf75e0..0000000
Binary files a/devices/m5stack/cardputer-adv/media/schematic-sheet1-J2-grove-GI-GO.png and /dev/null differ
diff --git a/devices/m5stack/cardputer-adv/media/schematic-sheet1-M1-pin-names-G1-G2.png b/devices/m5stack/cardputer-adv/media/schematic-sheet1-M1-pin-names-G1-G2.png
deleted file mode 100644
index f9dc3ec..0000000
Binary files a/devices/m5stack/cardputer-adv/media/schematic-sheet1-M1-pin-names-G1-G2.png and /dev/null differ
diff --git a/devices/m5stack/cardputer-adv/media/schematic-sheet3-U7-bmi270-int-unrouted.png b/devices/m5stack/cardputer-adv/media/schematic-sheet3-U7-bmi270-int-unrouted.png
deleted file mode 100644
index b08dc04..0000000
Binary files a/devices/m5stack/cardputer-adv/media/schematic-sheet3-U7-bmi270-int-unrouted.png and /dev/null differ
diff --git a/devices/m5stack/cardputer-adv/performance.md b/devices/m5stack/cardputer-adv/performance.md
deleted file mode 100644
index 634bacd..0000000
--- a/devices/m5stack/cardputer-adv/performance.md
+++ /dev/null
@@ -1,120 +0,0 @@
-# Cardputer ADV — performance
-
-> Snapshot **2026-09-04**. **No benchmark was run by this session, and no independent
-> measurement of any Cardputer was found anywhere during this pass.** Everything below is a
-> vendor claim, a silicon specification, a configured value read from source, or a labelled
-> estimate. Nothing is a measurement.
-
-## Silicon ceiling
-
-| Item | Value | Class |
-|---|---|---|
-| CPU | Xtensa LX7 **dual-core @ 240 MHz** | silicon |
-| SRAM | **512 KB** | silicon |
-| **PSRAM** | **none** — `ESP32-S3FN8` is flash-in-package, no PSRAM die | **silicon — the binding constraint** |
-| Flash | 8 MB, in package, quad SPI | silicon |
-| ROM | 384 KB | silicon |
-| Vector/AI extensions | LX7 SIMD present on S3 | silicon |
-| Radio | 2.4 GHz Wi-Fi b/g/n, BLE 5 | silicon |
-| CPU frequency as shipped | 240 MHz (`CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_240=y`) | source |
-
-## Configured throughputs
-
-| Path | Value | Source |
-|---|---|---|
-| Display SPI write | **40 MHz** | M5GFX `bus_cfg.freq_write = 40000000` |
-| Display SPI read | 16 MHz | M5GFX `freq_read = 16000000` |
-| Display SPI (Bruce/TFT_eSPI) | **20 MHz** | Bruce `-DSPI_FREQUENCY=20000000` |
-| Serial upload | **1 500 000 baud** | vendor PlatformIO profile |
-| GNSS UART (Cap LoRa) | 115 200 8N1 | Mesh Kit spec, factory firmware |
-| I²C internal | not specified; M5GFX probes at 100 kHz | source |
-| Backlight PWM | 256 Hz, LEDC ch 7 | M5GFX `_set_pwm_backlight(38, 7, 256, false, 16)` |
-
-40 MHz over a 3-wire SPI to a 240 × 135 × 16 bpp panel is ~518 kbit per full frame, so the bus
-alone permits roughly **77 full-screen updates per second** in theory. **Actual frame rate was
-not measured** and will be dominated by rendering, not by the bus.
-
-## Memory budget — the number that matters
-
-| Consumer | Bytes | % of 512 KB |
-|---|---|---|
-| Single 240×135×16 bpp framebuffer | 64 800 | 12.7 % |
-| Double buffered | 129 600 | 25.3 % |
-| Wi-Fi + LWIP (typical) | ~50 000–80 000 | 10–16 % |
-| NimBLE | smaller than Bluedroid; why the factory firmware uses it | — |
-| TLS session | tens of KB | — |
-
-Three independent pieces of evidence that this is the real limit:
-
-1. Meshtastic's ADV variant compiles with **`-DOLEDDISPLAY_REDUCE_MEMORY`**.
-2. Bruce ships a **`-DLITE_VERSION=1`** flag explicitly "to save space".
-3. The Meshtastic-client author (r/CardPuter, **2026-08-01**, firsthand engineering account):
-   *"the ESP32-S3 here has no PSRAM, so a full Unicode font cannot live in RAM. It ships as its
-   own 2.16 MB flash partition — 68,608 fixed-size records, one per codepoint, so a glyph lookup
-   is arithmetic rather than an index search — and the partition is memory-mapped, so rendering
-   Cyrillic, CJK or Greek costs no heap at all."*
-
-That third item is the most useful performance datum in this entire record, because it names the
-constraint, the workaround and the cost.
-
-Also relevant: `engneer-hamachan/area512` — *"A self-contained Ruby & Python development
-environment for the **512KB** M5Stack Cardputer"* — is named after the limit.
-
-## Power — vendor claims
-
-At **DC 4.2 V**, from the ADV product page. **Conditions (backlight level, CPU state, radio
-duty cycle) are not stated.**
-
-| Condition | Current |
-|---|---|
-| Standby, power switch OFF | **0.23 µA** |
-| Operating | 120.2 mA |
-| Wi-Fi | 132.3 mA |
-| BLE | 154.6 mA |
-
-⚠ **BLE reading higher than Wi-Fi is anomalous** and suggests the three figures were taken under
-different display or CPU conditions. Recorded in [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-**Derived runtime, clearly labelled an estimate:** 1750 mAh ÷ 132.3 mA ≈ **13.2 h** Wi-Fi,
-÷ 154.6 mA ≈ **11.3 h** BLE, at the vendor's numbers and ignoring converter efficiency, cell
-derating and whatever backlight state the measurement used. Do not quote these as battery life.
-
-**Cross-generation comparison is not possible.** The v1.1 page publishes entirely different
-conditions (*IR transmission mode 148.07 mA, key mode 138.93 mA*, sleep 0.15 µA) and the v1.0 a
-third set (255.6 mA IR, 165.7 mA key, 0.26 µA sleep). Three products, three measurement
-protocols. Any "the ADV is more efficient" claim built from these is unsupported.
-
-## Audio
-
-| Item | Value | Class |
-|---|---|---|
-| Speaker | 8 Ω, **1 W** | vendor |
-| Amplifier | NS4150B mono class-D | schematic |
-| Mic SNR | **65 dB** | vendor |
-| Codec | ES8311, I²S slave, **no MCLK** (BCLK-derived) | schematic + source |
-| Sample rates achieved | **not measured** | — |
-| THD, output level, latency | **not measured, none published** | — |
-
-## Radio
-
-Nothing measured, nothing published. M5Stack claims *"optimized antenna design for better
-reception"* for the Stamp-S3A versus the StampS3, and the two Stamp schematics do show different
-matching networks — but **no sensitivity, throughput or range figure exists** for any Cardputer
-in any source found. Community antenna mods (`henriquesebastiao/external-cardputer-antenna`)
-likewise carry no measurements.
-
-The Cap LoRa-1262's radio figures (+22 dBm, −147 dBm sensitivity, up to 300 kbps) belong to the
-[Cap board's record](../cap-lora-1262/README.md), not to the host.
-
-## Thermal
-
-Operating range **0 – 40 °C** (vendor). No thermal measurement, no throttling report, no
-sustained-load characterisation found. The device is a sealed plastic case with a 1 W amplifier
-and a 240 MHz dual-core part; sustained full-load thermal behaviour is **unknown**.
-
-## What would make this section useful
-
-An owner with a bench supply and a scope could produce, in an afternoon, the four numbers that
-are missing everywhere: current at a stated backlight level, sustained frame rate with M5GFX,
-free heap after `M5Cardputer.begin()` + Wi-Fi, and audio output level into 8 Ω. None of those
-exists publicly for the ADV as of 2026-09-04.
diff --git a/devices/m5stack/cardputer-adv/pinouts-and-buses.md b/devices/m5stack/cardputer-adv/pinouts-and-buses.md
deleted file mode 100644
index bee1bb9..0000000
--- a/devices/m5stack/cardputer-adv/pinouts-and-buses.md
+++ /dev/null
@@ -1,334 +0,0 @@
-# Cardputer ADV — pinouts and buses
-
-> Snapshot **2026-09-04**. Evidence classes used below:
-> **[SCH]** read off a rendered sheet of `Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf`;
-> **[SRC]** vendor board-support source at a pinned commit;
-> **[DOC]** the `docs.m5stack.com/en/core/Cardputer-Adv` PinMap tables;
-> **[INF]** inferred, with the reasoning stated.
-> Where **[DOC]** and **[SCH]**/**[SRC]** disagree, the disagreement is stated, not resolved silently.
-
-## 1. Complete GPIO map
-
-The ESP32-S3FN8 sits inside the Stamp-S3A; every pin below is a module castellation as well as
-an SoC GPIO. "Free on ADV" means the pin is not consumed by an on-board function and is
-brought out to the CAP header.
-
-| GPIO | Function on ADV | Direction | Bus / role | Shared with | Evidence |
-|---|---|---|---|---|---|
-| **G0** | BOOT / user button on the Stamp | in, pull-up 10 k | strap | — | [SRC] `M5Unified.cpp:3485` reads `!gpio_in(GPIO_NUM_0)` |
-| **G1** | Grove / PORT.A **SCL** | I/O | external I²C | Grove white wire | [SRC] `_pin_table_i2c_ex_in` → EX SCL = G1 · ⚠ see §5 |
-| **G2** | Grove / PORT.A **SDA** | I/O | external I²C | Grove yellow wire | [SRC] same → EX SDA = G2 |
-| **G3** | CAP `RESET` | out | CAP pin | *was 74HC138 sense line on v1.x* | [SCH] sheet 4, net `G3` at P3-1 |
-| **G4** | CAP `INT` / `IRQ` | in | CAP pin | *was keyboard sense* | [SCH] P3-2 |
-| **G5** | CAP `CS` | out | SPI CS | *was keyboard sense* | [SCH] P3-7 |
-| **G6** | CAP `BUSY` | in | CAP pin | *was keyboard sense* | [SCH] P3-3 |
-| **G7** | **Internal display FPC** | — | — | — | [SRC] M5GFX comment: G7 = "Internal FPC" on ADV |
-| **G8** | **Internal I²C SDA** | I/O | I²C, 3.3 k pull-up R37 | TCA8418, ES8311, BMI270, **CAP pin 11** | [SCH] sheet 2/3, [SRC] `_pin_table_i2c_ex_in` |
-| **G9** | **Internal I²C SCL** | I/O | I²C, 3.3 k pull-up R36 | same | same |
-| **G10** | Battery ADC | in, analog | ADC1 | — | [DOC], [SRC] Bruce `ANALOG_BAT_PIN=10` |
-| **G11** | TCA8418 `INT` | in, 3.3 k pull-up R35 | keypad IRQ | — | [SCH] U9-24, [SRC] `TCA8418.cpp:13` |
-| **G12** | microSD `CS` | out | SPI CS | — | [SRC] `_pin_table_sd` |
-| **G13** | CAP **UART TX** | out | UART | *was keyboard sense* | [SCH] net at P3, labelled `GPS-RX` · see §4 |
-| **G14** | SPI `MOSI` | out | SPI | microSD **and** CAP | [SRC] `_pin_table_sd`, [SCH] P3 |
-| **G15** | CAP **UART RX** | in | UART | *was keyboard sense* | [SCH] labelled `GPS-TX` · see §4 |
-| **G21** | WS2812 RGB LED data | out | RMT | on the Stamp | [SRC] `M5Unified.cpp:249` |
-| **G33** | LCD `RST` | out | — | — | [SRC] M5GFX `cfg.pin_rst` |
-| **G34** | LCD `DC`/`RS` | out | SPI | — | [SRC] `bus_cfg.pin_dc` |
-| **G35** | LCD `MOSI` | out | **separate SPI** | — | [SRC] `bus_cfg.pin_mosi` |
-| **G36** | LCD `SCK` | out | **separate SPI** | — | [SRC] `bus_cfg.pin_sclk` |
-| **G37** | LCD `CS` | out | SPI CS | — | [SRC] `cfg.pin_cs` |
-| **G38** | LCD backlight PWM **and** `BL_3V3` rail enable | out | LEDC ch7 | **WS2812 supply** | [SRC] `_set_pwm_backlight(GPIO_NUM_38, 7, 256, false, 16)`; [SCH] Stamp-S3A U2 `EN` |
-| **G39** | SPI `MISO` | in | SPI | microSD **and** CAP | [SRC], [SCH] |
-| **G40** | SPI `SCK` | out | SPI | microSD **and** CAP | [SRC], [SCH] |
-| **G41** | I²S `BCLK` / ES8311 `SCLK` | out | I2S_NUM_1 | — | [SRC] `spk_cfg.pin_bck`, `mic_cfg.pin_bck` |
-| **G42** | I²S `DOUT` / ES8311 `DSDIN` | out | I2S_NUM_1 | — | [SRC] `spk_cfg.pin_data_out` |
-| **G43** | I²S `LRCK` / ES8311 `LRCK` | out | I2S_NUM_1 | — | [SRC] `spk_cfg.pin_ws`, `mic_cfg.pin_ws` |
-| **G44** | IR emitter TX | out | RMT | — | [DOC], [SRC] UserDemo `HAL_PIN_IR_TX 44` |
-| **G45** | *unused on ADV* | — | — | — | Meshtastic sets `DAC_I2S_MCLK 45 // dummy` |
-| **G46** | I²S `DIN` / ES8311 `ASDOUT` | in | I2S_NUM_1 | — | [SRC] `mic_cfg.pin_data_in` |
-
-Pins **G16–G20, G22–G32, G47, G48** are not brought out on the Stamp-S3 24-pin footprint and
-are unavailable.
-
-### 1.1 What the ADV freed and spent, versus v1.x
-
-| Pin | v1.0 / v1.1 | ADV |
-|---|---|---|
-| G3, G4, G5, G6, G7, G13, G15 | keyboard **sense** lines (`input_list = {13,15,3,4,5,6,7}`) | G7 → display FPC; the other six → CAP header |
-| G8, G9, G11 | 74HC138 address lines `A0/A1/A2` (`output_list = {8,9,11}`) | G8/G9 → internal I²C; G11 → TCA8418 `INT` |
-
-Both lists are literal, from
-[`IOMatrix.h:29-30`](https://github.com/m5stack/M5Cardputer/blob/f1392858b9994c3547120e602a57d3553d16ab01/src/utility/Keyboard/KeyboardReader/IOMatrix.h#L29-L30):
-
-```cpp
-const std::vector<int> output_list = {8, 9, 11};
-const std::vector<int> input_list  = {13, 15, 3, 4, 5, 6, 7};
-```
-
-Net gain: **fifteen pins used by the keyboard become three.**
-
----
-
-## 2. Buses
-
-### 2.1 SPI — two independent buses
-
-| Bus | Host | SCK | MOSI | MISO | Devices | Notes |
-|---|---|---|---|---|---|---|
-| Display | `SPI3_HOST` | G36 | G35 | — | ST7789V2 (CS G37) | M5GFX sets `spi_3wire = true` and `pin_miso = -1`; 40 MHz write, 16 MHz read |
-| Peripheral | (user's choice) | **G40** | **G14** | **G39** | microSD (CS G12), **CAP board (CS G5)** | shared — see [`resources-and-conflicts.md`](resources-and-conflicts.md) |
-
-The display bus is genuinely separate silicon-side; the *peripheral* bus is the contended one.
-
-### 2.2 I²C
-
-| Bus | SDA | SCL | Pull-ups | Devices |
-|---|---|---|---|---|
-| **Internal** (`M5.In_I2C`) | **G8** | **G9** | R37 / R36, 3.3 kΩ to +3V3 | `0x34` TCA8418 · `0x18` ES8311 · `0x69` BMI270 · **plus whatever a CAP board adds** |
-| **External** (`M5.Ex_I2C`, PORT.A) | G2 | G1 | on the Grove peripheral | user devices |
-
-Address `0x69` for the BMI270 is printed on the schematic itself — sheet 3 carries the text
-**"7-bit Address 69H"** beside U7, and R43 (3.3 kΩ) pulls `SDO` high to select it. `0x18` for
-the ES8311 is `es8311_i2c_addr0` in
-[`M5Unified.cpp:513`](https://github.com/m5stack/M5Unified/blob/8530f5377d782e4a25a6c482de2e71c3f75ca8eb/src/M5Unified.cpp#L513).
-`0x34` for the TCA8418 is Bruce's `-DTCA8418_I2C_ADDR=0x34` and Adafruit's library default.
-
-> **Community documentation error, recorded.** `bmorcelli/Launcher`'s `CardputerADV.md` lists
-> "**0x18**: Likely accelerometer/IMU" and "**0x69**: Likely additional sensor". Both are
-> inverted: `0x18` is the ES8311 codec and `0x69` is the BMI270. Harmless in that file, but it
-> is the kind of thing that propagates.
-
-### 2.3 I²S — one port, two directions, one codec
-
-`I2S_NUM_1`, ESP32-S3 as **master**, ES8311 as slave:
-
-| Signal | GPIO | ES8311 pin |
-|---|---|---|
-| `BCLK` | G41 | 6 `SCLK/DMIC_SCL` |
-| `LRCK` / WS | G43 | 8 `LRCK` |
-| `DOUT` (to codec DAC) | G42 | 9 `DSDIN` |
-| `DIN` (from codec ADC) | G46 | 7 `ASDOUT` |
-| `MCLK` | **not wired** | — |
-
-There is no MCLK line. M5Unified's ADV callbacks therefore program the ES8311 with
-`0x01 = 0xB5` or `0xBA` — "MCLK = BCLK" — and `0x02 = 0x18` (`MULT_PRE = 3`). Meshtastic
-declares `DAC_I2S_MCLK 45 // dummy` for the same reason. Any driver you write must select
-BCLK-as-MCLK or the codec will not clock.
-
-The **speaker path and the microphone path share this one port and this one codec**, and
-M5Unified's two enable callbacks write *different* values to register `0x01`. See the driver
-audit in [`features/audio.md`](features/audio.md); this is a real defect, not a nit.
-
-### 2.4 Timers, RMT, LEDC, ADC
-
-| Resource | Consumer | Detail |
-|---|---|---|
-| LEDC channel **7** | LCD backlight | `_set_pwm_backlight(GPIO_NUM_38, 7, 256, false, 16)` — channel 7, 256 Hz, offset 16 |
-| RMT | WS2812 (G21) and IR TX (G44) | two channels if both used simultaneously |
-| ADC1 | battery sense on G10 | ADC1 also blocks nothing else here |
-| I2S_NUM_1 | audio | I2S_NUM_0 is free |
-| GPIO ISR | TCA8418 `INT` on G11 | `attachInterruptArg(..., CHANGE)` in the vendor reader |
-
----
-
-## 3. Connectors
-
-### 3.1 HY2.0-4P Grove / PORT.A (designator P1)
-
-| Wire | Signal | GPIO |
-|---|---|---|
-| Black | GND | — |
-| Red | +5V (from the `+5VOUT` boost rail) | — |
-| Yellow | `G2` | GPIO2 |
-| White | `G1` | GPIO1 |
-
-> ⚠ **Conflict, unresolved.** M5Stack's PinMap simply names the pins `G2`/`G1` and calls the
-> connector `PORT.CUSTOM`. M5Unified's `_pin_table_i2c_ex_in` row for `board_M5CardputerADV`
-> reads `{ …, GPIO_NUM_1, GPIO_NUM_2 }` under the header comment `// In SCL,SDA, EX SCL,SDA`,
-> i.e. **external SCL = G1, external SDA = G2**. The M5Stack Grove colour convention normally
-> puts **SCL on yellow** — which would make G2 the clock and contradict the library. The
-> schematic labels the connector `HY-2.0_IIC` with nets `IIC_SCL` and `IIC_SDA` present on the
-> sheet, but the two labels could not be resolved to individual pins from the text layer at the
-> band width used.
-> **Use the library values** (`M5.Ex_I2C`, SCL = G1, SDA = G2): they are what every M5 library
-> will do at runtime regardless of the colour convention. Recorded in
-> [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-### 3.2 EXT 2.54-14P "CAP" header (designator P3, footprint `HDR-SMD_14P-P2.54`)
-
-Full treatment, including the three numbering schemes, is in
-[`features/cap-header.md`](features/cap-header.md). The physical table, by row and position —
-which is unambiguous and does not depend on whose numbering you use:
-
-| Row L, position (top→bottom) | Signal | GPIO | | Row R, position (top→bottom) | Signal | GPIO |
-|---|---|---|---|---|---|---|
-| L1 | `RESET` | G3 | | R1 | `5VIN` | — |
-| L2 | `INT` | G4 | | R2 | `GND` | — |
-| L3 | `BUSY` | G6 | | R3 | `5VOUT` | — |
-| L4 | `SCK` | G40 | | R4 | `I2C_SDA` | G8 |
-| L5 | `MOSI` | G14 | | R5 | `I2C_SCL` | G9 |
-| L6 | `MISO` | G39 | | R6 | `UART_TX` (`GPS-RX`) | **G13** |
-| L7 | `CS` | G5 | | R7 | `UART_RX` (`GPS-TX`) | **G15** |
-
-Read directly off sheet 4 of the ADV schematic; the net labels `G3, G4, G6, G40, G14, G39, G5`
-and `+5VIN, GND, +5VOUT, G8, G9, G13, G15` sit against the corresponding pins, and the symbol's
-own pin names are `RESET, INT, BUSY, SCK, MOSI, MISO, CS` / `5VIN, GND, 5VOUT, SDA, SCL,
-GPS-RX, GPS-TX`.
-
-### 3.3 Display FPC (designator FPC1, `FPC-8P-0.5`)
-
-An 8-pin 0.5 mm flat-flex from the front panel to the display. G7 is described by M5GFX as
-"Internal FPC" on the ADV. The individual FPC conductors were not traced; the SPI signals
-(G33–G37) reach the panel through it. M5Stack warns that lifting the Stamp module without
-supporting this cable damages the socket.
-
----
-
-## 4. The UART direction question, settled
-
-M5Stack's own documentation contradicts itself. The resolution matters because getting it
-wrong means a GPS or a serial CAP board that simply never answers.
-
-| Source | Pin 12 / R6 (`G13`) | Pin 14 / R7 (`G15`) |
-|---|---|---|
-| `docs.m5stack.com/en/core/Cardputer-Adv`, EXT table | `UART_TX` | `UART_RX` |
-| `…/core/Cardputer_Mesh_Kit`, **EXT table** | `UART_RX` | `UART_TX` |
-| `…/core/Cardputer_Mesh_Kit`, **Cap-Bus table** | → `GPS-RX` | → `GPS-TX` |
-| **ADV schematic sheet 4**, symbol pin names | `GPS-RX` | `GPS-TX` |
-| **`M5Cardputer-UserDemo` @ `b549eac0`** | `HAL_PIN_GPS_TX GPIO_NUM_13` | `HAL_PIN_GPS_RX GPIO_NUM_15` |
-| **Meshtastic `variant.h`** | `GPS_TX_PIN 13` | `GPS_RX_PIN 15` |
-
-The decisive evidence is the factory firmware's actual call, in
-`main/hal/cap_lora868/uart/uart_helper.c:71`:
-
-```c
-#define ECHO_TEST_TXD (HAL_PIN_GPS_TX)   /* = GPIO_NUM_13 */
-#define ECHO_TEST_RXD (HAL_PIN_GPS_RX)   /* = GPIO_NUM_15 */
-ESP_ERROR_CHECK(uart_set_pin(ECHO_UART_PORT_NUM, ECHO_TEST_TXD, ECHO_TEST_RXD, …));
-```
-
-`uart_set_pin(port, tx_io_num, rx_io_num, …)` — so **GPIO 13 is the ESP32-S3's TX and GPIO 15
-is its RX**, host-centric. The schematic's peripheral-centric labels agree: pin `GPS-RX`
-carries G13, i.e. G13 feeds the GPS receiver.
-
-**Conclusion: G13 = TX (out), G15 = RX (in). The Cardputer Mesh Kit page's EXT table is
-wrong**, and is contradicted by its own Cap-Bus table two rows further down.
-
----
-
-## 5. Boot straps and reset behaviour
-
-| Pin | Strap role | ADV wiring | Risk |
-|---|---|---|---|
-| G0 | boot mode | Stamp user button, 10 kΩ pull-up | download mode = **switch OFF → hold G0 → apply power → release** |
-| G3 | JTAG source select (ESP32-S3) | **CAP `RESET`, no pull resistor on the host side** | ⚠ a CAP board or breadboard wire that holds G3 at a defined level during reset changes the JTAG source strap. Not observed to break anything, but worth knowing before you debug a mysterious boot difference with a CAP fitted. |
-| G45 | VDD_SPI voltage | not brought out | — |
-| G46 | boot log / strap | **ES8311 `ASDOUT`** | the codec is high-Z until enabled, so this is benign in practice; noted because G46 is a strap pin and the schematic shows it driven by an IC |
-
-The **CN809J** (U3) watches `VBAT_IN` and generates a reset. R7 (100 kΩ) pulls its `RESET`
-output line down. There is **no reset button** on the ADV — M5Stack's v1.1 spec table lists
-"1 × Reset button + 1 × User button", the ADV table lists neither, and the ADV designator
-census on sheet 1 finds exactly two switches (`BTN1`, `BTN2`) and two slide switches
-(`SW1`, `SW2`).
-
----
-
-## 6. Power rails
-
-| Rail | Source | Notes |
-|---|---|---|
-| `VBAT_IN` / `VBAT_OUT` | 1750 mAh cell via Q1/Q2/Q3 LP3218DT1G power path | `BAT+` / `BAT-` at J8 |
-| `+5VIN` | USB-C VBUS on the Stamp, through a 6 V/1 A PPTC (F1) | also CAP `5VIN` |
-| `+5VOUT` | **SY7088** boost from `VBAT_OUT`, FB 75 k/22 k → **≈ 5.29 V [INF]** | Grove red wire, CAP `5VOUT` |
-| `+3.3V` | **SY8089** buck, FB 68 k/15 k | everything logic |
-| `VDD_3V3` (Stamp) | **JW5712** buck on Stamp-S3A, 0–0.6 A | SoC |
-| `BL_3V3` (Stamp) | **AW35122FDR** load switch, `EN` = `DISP_BL` = **G38** | LCD backlight **+ WS2812** |
-
-The sheet prints its own formula, `Vout = 1.2 V × (R1/R2 + 1)`, which is what the inferred
-boost figure is computed from. Nothing here has been measured.
-
----
-
-# 2026-09-07 — additions and corrections from schematic net tracing
-
-Appended beneath the existing tables; **nothing above is altered, reworded or reordered.** Where
-a row below contradicts one above, the row below is the correction and the reason is given. Full
-trace with coordinates: [`schematic-netlist.md`](schematic-netlist.md). Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-All corrections are indexed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-## Grove / `PORT.CUSTOM` (`J2`, `HY-2.0_IIC`) — now established from the sheet
-
-| `J2` pin | Signal | GPIO | Evidence |
-|---|---|---|---|
-| 1 | `IIC_SCL` | **GPIO1** | net label `GI` @ 737.32, 366.41 → module pin `P1.1`, printed pin name `G1` |
-| 2 | `IIC_SDA` | **GPIO2** | net label `GO` @ 738.58, 373.60 → module pin `P1.2`, printed pin name `G2` |
-| 3 | `VCC` | — | 5 V; ESD `D8` `PESDNC2FD5VB` |
-| 4 | `GND` | — | ESD `D6`/`D7` `PESDNC2FD3V3B` on the two signals |
-
-Pull-ups `R3`, `R10`, both 10 kΩ. The net *names* on the sheet are the literal strings `GI`/`GO`
-(letter I, letter O) — a vendor typo — which is why searching for "G1"/"G2" near `J2` finds
-nothing. Verified with a 300 dpi crop.
-
-## Internal I²C bus
-
-| Device | Address | SDA | SCL | Evidence |
-|---|---|---|---|---|
-| `U7` BMI270 | `0x69` | **G8** (pin 14 `SDX`) | **G9** (pin 13 `SCX`) | `NLG8` @ 109.50, 142.20 · `NLG9` @ 109.50, 149.20; sheet prints `7-bit Address 69H` @ 196.71, 114.51; `SDO` (pin 1) strapped high by `R43` 3.3 kΩ |
-| `U9` TCA8418RTWR | `0x34` | **G8** (pin 22) | **G9** (pin 23) | `NLG8` @ 77.00, 239.20 · `NLG9` @ 77.00, 232.20; sheet prints `7-bit Address 34H` @ 106–142, 312.5 |
-
-Bus pull-ups: `R35`, `R36`, `R37`, all 3.3 kΩ, at x = 48.5 / 59.5 / 70.5 spanning y 184.57→206.57
-on sheet 2 — one each for `SDA`, `SCL` and `INT`.
-
-## Interrupts
-
-| Line | GPIO | Evidence |
-|---|---|---|
-| TCA8418 `INT` (`U9` pin 24) | **G11** | `NLG11` @ 78.50, 224.66; open-drain, pulled up by `R37` 3.3 kΩ. Matches `DEFAULT_TCA8418_INT_PIN 11` in `M5Cardputer/src/utility/Keyboard/KeyboardReader/TCA8418.cpp:13` |
-| BMI270 `INT1` (`U7` pin 4) | **none — not routed** | a full-sheet row query at y 167.37 returns only `U7`'s own tokens |
-| BMI270 `INT2` (`U7` pin 9) | **none — not routed** | same, at y 174.37 |
-
-**IMU motion-wake from deep sleep is unavailable on this board.**
-
-## Keyboard matrix (`U9` TCA8418RTWR, sheet 2)
-
-7 rows × 8 columns = 56 keys.
-
-| `U9` pin | Name | Net |
-|---|---|---|
-| 1 | `ROW7` | **unconnected** — `PIU901` @ 164.00, 206.91, no label, no aligned peer |
-| 2–8 | `ROW6`…`ROW0` | `ROW6`…`ROW0` (`NLROW0`…`NLROW6`, x 184.50, y 152.66–196.20) |
-| 9–16 | `COL0`…`COL7` | `Y7`…`Y0`, each through a 22 R/1 % series resistor `R27`…`R34` |
-| 20 | `RESET` | `R38` 10 kΩ pull-up (`PIR382` @ 81.00, 264.37) |
-| 25 | `EP` | `GND` |
-
-## Power rails — corrected figures
-
-| Rail | Converter | Divider | Computed | Note |
-|---|---|---|---|---|
-| `+3.3V` | `U4` SY8089 buck, `L2` 4.7 µH `3015` | **`R11` 68 kΩ / `R13` 15 kΩ** | 3.3 V with a **0.6 V** feedback reference | ⚠ **correction:** the earlier reading of `R12` 68 kΩ was wrong — `R12` is 100 kΩ and sits 460 pt away at (236.50, 221.20), unrelated to this network |
-| `+5VOUT` | `U2` SY7088 boost, `L1` 1.5 µH `3015`, `D2` `SS34` | `R4` 75 kΩ / `R6` 22 kΩ | **5.29 V** using the sheet's own printed `Vout=1.2V*(R1/R2+1)` @ (612.67, 157.65) | ⚠ **correction:** that printed formula belongs to `U2`, **not** to `U4` — it sits directly beneath the SY7088 |
-
-The rail is designed high on purpose; the DinMeter's equivalent SY7088 rail computes to 5.38 V.
-
-## Module footprint `P1`, sheet 1
-
-| Pin | Printed pin name | Net |
-|---|---|---|
-| 1 | `G1` | `GI` → `J2.1 IIC_SCL` |
-| 2 | `G2` | `GO` → `J2.2 IIC_SDA` |
-| 3–9 | `G3`…`G9` | `G3`…`G9` |
-| 10 | `G10` | `GND` |
-| 11 | `G11` | `G11` → `U9.24 INT` |
-| 12–13 | — | `+5VIN` (`NL05VIN`; Altium's `NL` tokens substitute `0` for `+`) |
-| 14–15 | `G13` | `G13` |
-| 16–17 | `G15` | `G15` |
-
-## Named parts recovered from the sheets
-
-`U1` `TP4057` · `U2` `SY7088` · `U3` supervisor · `U4` `SY8089` · `U5` audio amplifier
-(`INP`/`INN`, sheet 3) · `U6` codec (`CCLK`/`MCLK`, sheet 3) · `U7` `BMI270` ·
-`U8` `MSM381A3729H9BPC` PDM microphone (sheet 3) · `U9` `TCA8418RTWR` ·
-`Q1`/`Q2`/`Q3` `LP3218DT1G` · `D6`/`D7` `PESDNC2FD3V3B` · `D8` `PESDNC2FD5VB` ·
-`FB7` 120 Ω/MB ferrite on the BMI270 supply.
diff --git a/devices/m5stack/cardputer-adv/product-history-and-family.md b/devices/m5stack/cardputer-adv/product-history-and-family.md
deleted file mode 100644
index 6f0e49f..0000000
--- a/devices/m5stack/cardputer-adv/product-history-and-family.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Cardputer family — history, timeline and culture
-
-> Snapshot **2026-09-04**. Dates are sourced individually; the three kinds of "launch date"
-> M5Stack produces (Shopify `created_at`, Shopify `published_at`, and `docs.m5stack.com/en/history`)
-> are **not** the same thing and are labelled as such.
-
-## Timeline
-
-| Date | Event | SKU | Source |
-|---|---|---|---|
-| 2023-10-10 … 10-16 | First `M5Cardputer` library commits — examples, USB keyboard demo, `v1.0.1` release | K132 | library git log |
-| 2024-01-19 | `sdcard` example added | | library git log |
-| 2024-12-25 | `mic_wav_record` demo added | | library git log |
-| **2025-03-07** | **Cardputer v1.1** created **and** published on the store, same day | K132-V11 | Shopify `created_at`/`published_at` |
-| 2025-03-07 | `add8b6f` "fix button reference issues, use M5.getButton method" | | library git log |
-| **2025-06-20** | **ADV schematic file stamp** — `Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58` | K132-Adv | artifact filename |
-| **2025-07-03 / 07-04** | Cardputer Accessory Kit v1.1 (M5StampS3A + display) created / published, $9.95 | — | Shopify |
-| **2025-08-29** | `c331c7d` *"basic extract"* — the M5Cardputer library's keyboard reader is refactored behind an interface **in preparation for the ADV** | | library git log |
-| **2025-09-01** | `630bcfc` vendored `Adafruit_TCA8418`; `6928513` *"add basic tca8418 reader"*; `db011a8`, `c2fbc89` fixes; `9e9ad46` REPL UI example; `7e97cc8` version bump | | library git log |
-| **2025-09-02** | `8ab9f43` **PR #9 "add-cardputer-adv-support"** merged | | library git log |
-| **2025-09-04** | Cardputer ADV **created** on the store | K132-Adv | Shopify `created_at` |
-| **2025-09-05** | Cardputer ADV **published** — public availability | K132-Adv | Shopify `published_at` |
-| 2025-09-28 | `0b23b2c` *"fix modifier handle before normal key"* | | library git log |
-| **2026-01-04** | **Cap LoRa-1262** released, category *"For Cardputer-Adv"* | U214 | `docs.m5stack.com/en/history` |
-| 2026-02-27 | **Plai** Meshtastic client first beta — r/CardPuter ↑153, 139 comments | | Reddit |
-| **2026-04-30** | **Cardputer Mesh Kit** released | K152 | `/en/history` |
-| 2026-05-11 / 05-12 | `eccba25` fn-layer support (PR #15), `84e5201` mapping fix — **arrow keys arrive** | | library git log |
-| 2026-06-08 | `b549eac0` factory-firmware `CardputerADV` branch head — *"improve boot UX"* | | UserDemo git log |
-| 2026-06-22 | Community **Cap TFT-2.8** announced — r/CardPuter ↑989, the pass's highest-scoring hardware post | | Reddit |
-| 2026-07-20 / 07-21 | `5604284`, `f1392858` — `M5Cardputer` **1.1.1** head | | library git log |
-| **2026-08-28** | **Cap CC1101 & NFC** released, *"For Cardputer-Adv"* | U219 | `/en/history` |
-| **2026-09-04** | Cardputer **v1.1 listed as `[EOL]`** on M5Stack's own store; ADV in stock at $29.90 | | Shopify `suggest.json` |
-| *pending* | **CardputerZero** — Kickstarter ran spring 2026; docs page carries a *"Work in progress"* banner | C154 / C155 | docs, Reddit |
-
-Two things fall out of that ordering.
-
-**The library led the product by three days.** ADV support was merged into `M5Cardputer` on
-2025-09-02; the store record was created on 2025-09-04. M5Stack ships software before hardware,
-which is why "update your library" is the first answer to almost every ADV problem.
-
-**The CAP ecosystem is the ADV's second act.** The board shipped in September 2025 with an
-expansion header and nothing to plug into it. The first CAP board arrived **four months later**
-(2026-01-04) and the second **eleven months later** (2026-08-28). The community filled the gap
-in between — the Cap TFT-2.8 predates the Cap CC1101 by two months.
-
-## The family
-
-| Product | SKU | Class | Core | Keyboard | Status 2026-09-04 |
-|---|---|---|---|---|---|
-| **Cardputer** | K132 | MCU | StampS3 (ESP32-S3FN8) | 74HC138 matrix | superseded |
-| **Cardputer v1.1** | K132-V11 | MCU | **Stamp-S3A** | 74HC138 matrix | **`[EOL]`** |
-| **Cardputer ADV** | K132-Adv | MCU | Stamp-S3A | **TCA8418 I²C** | current, $29.90 |
-| **Cardputer Mesh Kit** | K152 | bundle | = ADV + Cap LoRa-1262 | = ADV | current, $48.00 |
-| **CardputerZero** | C154 | **Linux** | Raspberry Pi CM0 (BCM2837, 4×A53, 512 MB) | **46-key**, TCA8418 | *work in progress* |
-| **CardputerZero-Lite** | C155 | Linux | as C154, no bundled SD card | as C154 | *work in progress* |
-| Cardputer Accessory Kit | — | spare | StampS3 + display | — | superseded |
-| Cardputer Accessory Kit v1.1 | — | spare | **M5StampS3A** + display | — | current, $9.95 |
-| Cap LoRa-1262 | U214 | CAP module | — | — | $14.50 |
-| Cap CC1101 & NFC | U219 | CAP module | — | — | $18.95 |
-
-Records: [`cardputer-v1.0`](../cardputer-v1.0/README.md) ·
-[`cardputer-v1.1`](../cardputer-v1.1/README.md) ·
-[`cardputer-zero`](../cardputer-zero/README.md) ·
-[`cardputer-mesh-kit`](../cardputer-mesh-kit/README.md) ·
-[`cap-lora-1262`](../cap-lora-1262/README.md) · [`cap-cc1101`](../cap-cc1101/README.md).
-
-## Shared DNA, and where it stops
-
-Three things travel across the whole line:
-
-1. **The 84 × 54 mm card format** and the LEGO-compatible magnetic base.
-2. **The keyboard matrix**, identical between v1.0, v1.1 and ADV — same switches, same `Y0..Y7`
-   nets, same 22 Ω series resistors. Only the scanner changed.
-3. **The `TCA8418` and the `EXT 2.54-14P` connector**, which the ADV introduced and the
-   CardputerZero inherited — even though the Zero is a completely different computer.
-
-Where it stops: the **CardputerZero shares almost no silicon with the ADV.** It is a
-Raspberry-Pi-CM0 Linux machine with a bigger 320 × 170 display, a 46-key keyboard, a camera, a
-magnetometer, an **RTC**, a **fuel gauge**, an **M5IOE1** I/O expander, USB host/slave switching
-and Ethernet. The family resemblance is industrial design plus two component choices.
-
-The r/CardPuter thread of 2026-05-31 captures the confusion this causes better than any spec
-sheet. u/G33K_FISH: *"FYI, the ADV and the Zero are different. The Zero will be linux based. You
-can do things on the Zero you can not do on the ADV and vise versa."*
-
-## Culture
-
-The Cardputer's community is disproportionately large and unusually *productive* — it makes
-things rather than just discussing them. Three dedicated subreddits (**r/CardPuter**,
-**r/CardPuterZero**, and heavy traffic in **r/M5Stack**), an official Discord, two curated
-awesome-lists (`terremoth/awesome-m5stack-cardputer` ★734, `ru84r8/Cardputer-firmware-list`),
-and 100+ GitHub repositories.
-
-Two cultural currents dominate:
-
-* **"Cheap Flipper Zero."** Explicit in the threads — *"I want to turn Cardputer Adv in budget
-  Flipper zero alternative"* (r/CardPuter 2026-06-27, ↑88), and in the firmware names. Bruce,
-  Marauder and Evil-M5Project all live here. It is also why the platform attracts more
-  attention than a $30 dev board otherwise would.
-* **Cyberdeck and pocket-computer romance.** r/cyberDeck 2026-06-22, ↑710. The mod scene
-  (external antennas, XL cases, dual screens, 3D-printed key caps) is large.
-
-A third current appeared in **mid-2026 and is specific to the ADV**: a **music scene**, made
-possible entirely by the ES8311 codec and the 3.5 mm jack. Grooveboxes, synths and a pocket DAW
-all appeared between June and August 2026. No such projects exist for the v1.x, because the v1.x
-has no line out.
-
-## Positioning, then and now
-
-**At launch (September 2025)** the ADV was a $29.90 refresh of a popular $29.90 board, and the
-case for upgrading was not obvious to an existing v1.x owner: same SoC, same flash, same screen,
-same price. The pitch was the peripherals.
-
-**By late 2026** the picture has inverted. The v1.1 is `[EOL]`, Meshtastic upstream supports
-only the ADV, the entire CAP accessory line is ADV-only, and new community projects target the
-ADV by default. The v1.x is now the compatibility case, not the default.
-
-See [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) for buying
-guidance dated to this snapshot.
diff --git a/devices/m5stack/cardputer-adv/projects-and-community.md b/devices/m5stack/cardputer-adv/projects-and-community.md
deleted file mode 100644
index 5ad8f6c..0000000
--- a/devices/m5stack/cardputer-adv/projects-and-community.md
+++ /dev/null
@@ -1,322 +0,0 @@
-# Cardputer ADV — projects, firmware and community
-
-> Snapshot **2026-09-04**. Discovery: `gh search repos cardputer --limit 100` (returned 100,
-> the API cap — the true count is higher), targeted `gh search code` inside five named
-> upstreams, and `old.reddit.com/search.json` with `User-Agent: WhatsApp/2.23.20.0`
-> (`www.reddit.com` returns 403 to plain clients; `old.reddit.com` with that UA returns 200).
->
-> **Evidence classes** are stated per project. "Supports ADV" means the repository contains a
-> build target, a documented ADV path, or an explicit statement — not that this session flashed
-> it. **No firmware was built or run by this session.** Everything below is
-> `reported-working`, `documented` or `inferred`.
-
-## 1. Why the ecosystem matters here
-
-The Cardputer has an unusually large third-party firmware scene for a $30 board — larger than
-its own vendor's software effort. `terremoth/awesome-m5stack-cardputer` (★734, GPL-3.0) and
-`ru84r8/Cardputer-firmware-list` (★105) exist purely to index it, and there are at least three
-dedicated subreddits (**r/CardPuter**, **r/CardPuterZero**, plus heavy traffic in r/M5Stack).
-
-The 2026 pattern is stark: **new work targets the ADV.** Of the 100 repositories GitHub
-returned, the ones created or renamed in 2026 overwhelmingly carry "ADV" in the name or
-description. The v1.x is where the ecosystem grew up; the ADV is where it lives now.
-
-## 2. The major firmwares
-
-### 2.1 Bruce — `BruceDevices/firmware`
-
-| | |
-|---|---|
-| URL | `https://github.com/BruceDevices/firmware` (**formerly `pr3y/Bruce`** — the old URL redirects) |
-| HEAD at snapshot | **`1d555e0d5b201cc91ad201ac40c2482ec00d1ac1`**, 2026-08-28 |
-| Stars / licence | ★6 642 · **AGPL-3.0** |
-| Cardputer support | **v1.0, v1.1 and ADV from one build target** |
-| Evidence | build config read at HEAD; `reported-working` by the wider community |
-
-Bruce is the most important firmware on this platform and the cleanest demonstration that
-one binary can serve both generations. `boards/m5stack-cardputer/m5stack-cardputer.ini`:
-
-```ini
-board = m5stack-cardputer
-board_build.partitions = custom_8Mb.csv
--DTCA8418_INT_PIN=11  -DTCA8418_I2C_ADDR=0x34  -DTCA8418_SDA_PIN=8  -DTCA8418_SCL_PIN=9
--D ES8311_CODEC=1     -D ES8311_ADDR=0x18
--DMIC_SPM1423=1  -DPIN_CLK=43  -DPIN_DATA=46          ; the v1.x mic
--D SYS_I2C_SDA=-1 #8 on ADV Only
--D SYS_I2C_SCL=-1 #9 on ADV Only
-lib_deps = adafruit/Adafruit TCA8418 @ ^1.0.2
-```
-
-Runtime detection, `boards/m5stack-cardputer/interface.cpp`:
-
-```cpp
-bool UseTCA8418 = false;              // line 12
-Wire1.begin(TCA8418_SDA_PIN, TCA8418_SCL_PIN);
-UseTCA8418 = tca.begin(TCA8418_I2C_ADDR, &Wire1);
-if (!UseTCA8418) {
-    Serial.println("ADV  : Failed to initialize TCA8418!");
-    Serial.println("Probable standard Cardputer detected, switching to Keyboard library");
-}
-```
-
-**Known issues, from reading the source:**
-
-* Keyboard is **polled, not interrupt-driven** (`TCA8418_REPEAT_START_MS 350`,
-  `TCA8418_REPEAT_MS 150`, ~100 ms poll). Perceptibly less responsive than the vendor library's
-  interrupt path on held keys.
-* Its ES8311 sequences at `interface.cpp:491-527` are copied verbatim from M5Unified,
-  **including the register-`0x01` divergence** between the speaker (`0xB5`) and microphone
-  (`0xBA`) paths. See [`features/audio.md`](features/audio.md) §6.1 — the defect has propagated.
-* `-DLITE_VERSION=1` exists specifically "to limit some features to save space for M5Launcher
-  Compatibility" — the 8 MB flash is a real constraint when chain-loading.
-* Its build config declares CC1101, NRF24, W5500 and LoRa on the shared SPI bus with
-  `SPI_SS_PIN = GROVE_SCL` (G1) for the v1.x path and dedicated ADV pins otherwise.
-
-Build: `pio run -e m5stack-cardputer` — `not-tested` here.
-
-### 2.2 Launcher — `bmorcelli/Launcher`
-
-| | |
-|---|---|
-| URL | `https://github.com/bmorcelli/Launcher` (**formerly `bmorcelli/M5Stick-Launcher`**) |
-| HEAD | **`3b91484efc5f1a392fac2c4d6066d8306409c688`**, 2026-09-04 |
-| Stars / licence | ★2 054 · **MIT** |
-| Cardputer support | v1.x and **ADV**, with a dedicated `boards/m5stack-cardputer/CardputerADV.md` |
-
-Widely called **"M5Launcher"** by users; the repository name changed. It is a multi-firmware
-boot menu — you keep several `.bin` images on the SD card and pick one at boot. That makes it
-the de-facto entry point for people who want Bruce *and* Marauder *and* a game.
-
-Its `CardputerADV.md` is a good short account of the port and states plainly:
-
-> | Component | Original Cardputer | Cardputer ADV |
-> | Keyboard Controller | Direct GPIO matrix | TCA8418 I2C controller |
-> | I2C Address | N/A | 0x34 |
-> | SDA/SCL/Interrupt | GPIO13 / GPIO15 / N/A | GPIO8 / GPIO9 / GPIO11 |
-> **Matrix Size**: 7 rows × 8 columns · **Communication**: I2C polling only · 100 ms interval
-
-That confirms the 7 × 8 matrix independently of M5Stack.
-
-> ⚠ **Documentation error in that file, recorded:** it lists "**0x18**: Likely
-> accelerometer/IMU" and "**0x69**: Likely additional sensor". They are inverted —
-> `0x18` is the ES8311 codec, `0x69` is the BMI270 (the ADV schematic prints
-> *"7-bit Address 69H"* beside the BMI270).
-
-Companion: `CCP101/cardputer-recoverable-multiboot` (MIT) — "M5Launcher as factory entry,
-combined with OTA application partitions", i.e. a partition scheme that keeps a recovery path.
-
-### 2.3 Meshtastic — `meshtastic/firmware`
-
-| | |
-|---|---|
-| HEAD | **`be2f68b5af806332c9d877d1643007771bd10c36`**, 2026-09-03 |
-| Stars / licence | ★8 250 · **GPL-3.0** |
-| Cardputer support | **ADV only** — env `m5stack-cardputer-adv`, `board_level = release` |
-
-`variants/esp32s3/m5stack_cardputer_adv/` is a first-class upstream variant, not a fork. It
-targets `board = m5stack-stamps3` with `default_8MB.csv`, `-DOLEDDISPLAY_REDUCE_MEMORY`, and
-pins `meshtastic/st7789@92bae2e4`, `pschatzmann/arduino-audio-driver@v0.3.0`,
-`meshtastic/ESP8266Audio@34302463`, `earlephilhower/ESP8266SAM@1.1.0`.
-
-Its `variant.h` is an excellent independent pin reference and is quoted throughout this record —
-notably `GPS_RX_PIN 15` / `GPS_TX_PIN 13`, `LORA_CS 5`, `LORA_RESET 3`, `LORA_DIO1 4`,
-`SX126X_BUSY ← 6`, `KB_INT 11`, `I2C_SDA 8`/`I2C_SCL 9`, `I2C_SDA1 2`/`I2C_SCL1 1`, and
-`#define I2C_NO_RESCAN`.
-
-**There is no `m5stack_cardputer` (non-ADV) variant.** Meshtastic on a v1.x means a third-party
-client, not upstream.
-
-The **Cardputer Mesh Kit (K152)** is an *officially licensed* Meshtastic device with a
-registration flow at `meshtastic-reg.m5stack.com`, and M5Stack states: *"Only devices in the
-Cardputer Mesh Kit set can be registered. Other Cardputer/-Adv devices are not eligible."*
-So an ADV + separately-bought Cap LoRa-1262 runs the firmware but cannot claim the badge.
-
-### 2.4 Meshtastic clients and alternatives
-
-| Project | Stars | Licence | Notes |
-|---|---|---|---|
-| `d4rkmen/plai` | ★175 | GPL-3.0 | *"Standalone Meshtastic node for CardPuter ADV"*. Announced r/CardPuter 2026-02-27 (↑153, 139 comments). u/Big-Bunch2804 (2026-08-05, firsthand): *"tested this on my cardputer adv … it works great! I also ran it yesterday with the lora cap and it automatically detected the lora cap and switched configurations. Did a couple test on LongFast and got acknowledged. Allows use of arrow keys unlike many other meshtastic firmware."* Same user, **2026-08-29**: *"The update today won't allow me to use directional arrows on adv anymore. Still won't save configurations when switching firmware."* |
-| `Stachugit/MeshCore-Cardputer-ADV` | ★134 | MIT | MeshCore, not Meshtastic |
-| `sosprz/meshcore-cardputer-adv` | ★69 | — | MeshCore client |
-| `MultiMote/meshcore-cardputer-adv` | ★18 | MIT | *"Still in development 🚧"* |
-| `ratspeak/rsCardputer` | ★53 | AGPL-3.0 | Reticulum/LXMF for ADV |
-| `nonik0/CardputerLoRaChat` | ★121 | — | |
-
-The unnamed r/CardPuter post of **2026-08-01** — *"Meshtastic client firmware for the Cardputer
-ADV — full Unicode on 240x135 with no PSRAM, and no phone in the loop"* (↑47, 38 comments) —
-contains the best single engineering account of the platform's memory constraint. Quoted in
-[`resources-and-conflicts.md`](resources-and-conflicts.md) §4.
-
-### 2.5 Evil-M5Project ("EvilCardputer") — `7h30th3r0n3/Evil-M5Project`
-
-★2 570, **no licence file** (redistribution status `unknown`), last push 2026-08-20.
-Wi-Fi auditing suite; the long-running community favourite on v1.x. Its description lists
-"Cardputer, Atoms3, Fire, core2" and does **not** mention the ADV. Version 1.4.3 was announced
-on r/CardPuter 2025-08-17 (↑330, 91 comments). **ADV support: not established.** A companion
-content repo, `uagainshadow/Tons-of-LIVE-Public-CCTV-Cameras-for-the-Cardputer`, describes
-adding an `evil/cctv` folder on the SD card.
-
-### 2.6 ESP32Marauder — `justcallmekoko/ESP32Marauder`
-
-★12 212, **no licence field returned by the API** (`none`), HEAD `91724fd8`, 2026-08-24.
-`gh search code` finds **both** `User_Setup_marauder_m5cardputer.h` **and**
-`User_Setup_marauder_m5cardputer_adv.h`, plus `installer/targets.json` and
-`esp32_marauder/Keyboard.cpp` / `Keyboard_def.h`. So **ADV is a distinct supported target**.
-It is an Arduino-IDE project, not PlatformIO — `platformio.ini` contains only `[env:native]`.
-
-### 2.7 NEMO — `n0xa/m5stick-nemo`
-
-★1 300, licence `NOASSERTION`, HEAD `0b8c5c73`, 2026-07-15. `configs/` contains exactly four
-`.env` files: `M5Cardputer`, `M5StickC`, `M5StickCPlus`, `M5StickCPlus2`. The Cardputer one is:
-
-```sh
-export FQBN="m5stack:esp32:m5stack_cardputer"
-export EXTRA_FLAGS="-DCARDPUTER"
-export LIBRARIES="M5Cardputer IRRemoteESP8266 M5Stack-SD-Updater M5Unified"
-```
-
-**There is no ADV config.** However, because it builds against the `M5Cardputer` library, a
-build using **library ≥ 1.1.1** would pick up board autodetect and the TCA8418 reader for free.
-**Status: plausible but unverified.** Recorded as `inferred`, not `working`.
-
-### 2.8 MicroHydra — `echo-lalia/MicroHydra`
-
-★314, **GPL-3.0**, last push 2026-08-21. *"a simple, 'OS-like', MicroPython based app
-switcher"*. The principal MicroPython route onto the platform; companion
-`echo-lalia/Cardputer-Micropython-Examples` (★49, MIT). ADV support **not confirmed** from the
-metadata available in this pass.
-
-### 2.9 Picoware — `jblanked/Picoware`
-
-★320, **GPL-3.0**, 2026-09-03. Description names **"PicoCalc, Cardputer ADV, Flipper Zero"** —
-explicit ADV support, cross-device.
-
-## 3. Emulators, games and "tiny OS"
-
-| Project | Stars | Licence | Target |
-|---|---|---|---|
-| `geo-tp/Cardputer-Game-Station-Emulators` | ★240 | MIT | NES, SNES, GameBoy, GameGear, Master System, Megadrive, NeoGeo |
-| `romalik/m5cardputer_doom` | ★82 | MIT | Doom |
-| `matteofo/gb_cardputer` | ★71 | — | Peanut-GB port |
-| `AndyAiCardputer/zx-spectrum-cardputer-external` / `-ili9341` | ★48 / ★26 | other | ZX Spectrum 48K on **external** ILI9488/ILI9341 via the CAP header |
-| `question-and-answer/cave-mine-cardputer-alpha1` | ★22 | MIT | "true 3D voxel sandbox" for the ADV |
-| `mindovermiles262/tamaputer` | ★25 | — | Tamagotchi, v1.x **and** ADV |
-| `acpayers-alt/raising-hell-cardputer` | ★98 | MIT | virtual pet |
-| `bomberman30/AdvanceOS-for-cardputer` | ★90 | MIT | ADV media playback OS |
-| `engneer-hamachan/area512` | ★50 | MIT | **"Ruby & Python development environment for the 512KB M5Stack Cardputer"** — announced r/CardPuter 2026-07-03 (↑120) |
-| `bryant24hao/ClawPuter` | ★149 | MIT | pixel desktop companion |
-| `technoblogy/ulisp-cardputer` | ★27 | — | uLisp — a self-contained Lisp machine |
-| `Kezii/Rust-M5Stack-Cardputer` | ★69 | GPL-3.0 | **Rust** HAL and examples |
-| `shikarunochi/CardputerSimpleLaucher` | ★61 | MIT | simple launcher |
-| `d4rkmen/M5Apps` | ★90 | MIT | *"Multi-app installer for M5 CardPuter v1.0, v1.1 and ADV"* — explicitly all three |
-
-"Cardputer-Mario"-class platformers were **not** found under that name; the emulator collections
-above are what the community actually uses to run 8/16-bit titles.
-
-## 4. Audio and music — the 2026 surprise
-
-A whole music scene appeared on the ADV in mid-2026, entirely because of the ES8311 and the jack.
-
-| Project | Stars | Notes |
-|---|---|---|
-| `urtubia/miniacid` | ★105, MIT | *"An Acid style mini groovebox for the M5Stack Cardputer ADV"*. r/CardPuter 2026-07-13 (↑515, 44 comments) and r/synthdiy the same day (↑226): *"A $30 4-track acid groovebox … 303 voices, 808/909"* |
-| `CHARL3X/GLIDE-Synth-Cardputer-ADV` | ★83 | *"a playable instrument with fretless-style glide"*. r/CardPuter 2026-06-28, ↑301 |
-| "BKLVA Pocket DAW" | — | 0.2.20 announced 2026-07-30 (↑135), 0.3.4 on 2026-08-20 (↑100): *"Scenes, song chaining, Drum16, sampling and USB MIDI"*. Repository not located in this pass — **gap** |
-| `AndyAiCardputer/mp3-player-winamp-cardputer-adv` | ★47 | *"with ES8311 audio codec support"* |
-| `halbeshuhn/Cardputer-WebRadio`, `wusiu/WebRadio_WuSiU_Cardputer_Adv`, `cyberwisk/M5Cardputer_WebRadio` | ★16 / ★21 / ★129 | streaming |
-| `sanchitminda/MP3PlayerForM5Cardputer` | ★47, GPL-3.0 | |
-| "EMBER" MP3/FLAC/WAV player | — | r/CardPuter 2026-08-05, ↑47 |
-| `wcheng95/Mini-FT8` | ★76, MIT | **FT8** digital-mode ham radio |
-
-## 5. AI and LLM
-
-| Project | Notes |
-|---|---|
-| `therezor/cardputer-ai` (★79) | *"Fully offline tiny LLM chatbot on the ESP32-S3 Cardputer ADV — 8M params, Q4"*. r/CardPuter 2026-06-12, ↑165. A genuine curiosity: an 8-million-parameter model on a no-PSRAM part. |
-| `d4rkmen/M5Gemini` (★71), `shaahin/CardputerGPT` (★8), `FelipeLima2/M5CardputerAI` (★29), `vanshksingh/M5Cardputer-Chat-with-Gemini-API` (★58) | cloud-API clients |
-| `dakshaymehta/cardputer-claude-os` (★202, Apache-2.0), `moremas/build-with-claude` (★196) | agent front-ends |
-| `GOROman/LLMCardputer` (★63), `fwz233-RE/M5Claw` (★51) | |
-
-## 6. Sensing, radio and instruments
-
-`skizzophrenic/Cardputer-CSI-Human-Detector` (★207, MIT) and
-`Zeloksa/Cardputer-ADV-CSI-Radar` (★100) do **Wi-Fi CSI** human/motion sensing — a research
-technique running on a $30 handheld. `Jay-Jayismyname1/Cardputer-ABS-B-Radar` tracks aircraft;
-`adammelancon/cardputer-satellite-tracker` (★58) and `wisnc/stellar-map` (★68, Stellarium-like)
-and `nongxl/SkyCompass_CardputerADV` (celestial navigation off the Cap LoRa GNSS) point at the
-sky. `lunarc3/CardputerGPSMap` (★27) and `geo-tp/M5Cardputer-GPS-Logger` (★37) use the GNSS.
-`MatthewKuKanich/ChimeraBLE` (★220) does BLE reverse engineering. `geo-tp/MicroCOM` (★44) is a
-serial terminal; `geo-tp/M5-Card-Computer-I2C-Scanner` (★23) an I²C scanner; several SSH clients
-exist (`aat440hz/SSHClient-M5Cardputer` ★62, `MangoX0567/M5Stack-Cardputer-SSH` ★58 "for
-Cardputer ADV", plus the vendor's own `examples/Advanced/SSHClient`).
-`baget/esphome-m5cardputer` (★31, Apache-2.0) brings it into Home Assistant.
-`nishad2m8/WLED-Cardputer` (★12, EUPL-1.2) drives WLED.
-
-## 7. Hardware mods and CAP boards
-
-* `Prokuon/CardputerADV_Cap_TFT-2.8` (★63) and `CardputerADV_Cap_TFT_V2` (★35) — community CAP
-  display boards. The announcement (r/CardPuter, **2026-06-22**) hit **↑989 with 75 comments**,
-  the highest-scoring Cardputer hardware post found.
-* `guicmg/cardputer_adv_external_screen` (★71, MIT) — dual-screen guide.
-* `JosephCGS/Cardputer-ADV-CC1101-NRF24L01-LoRa` (★39) — a DIY multi-radio CAP.
-* `henriquesebastiao/external-cardputer-antenna` (★55, MIT).
-* r/cyberDeck **2026-06-22**: *"Turning my Cardputer ADV into a mini Cyberdeck"* — ↑710.
-* r/CardPuter **2026-07-09**: *"My first cardputer adv mod!"* — ↑213.
-* "Cardputer XL mod with Schematik" — r/M5Stack 2026-08-07.
-
-## 8. Forum and community evidence
-
-**Subreddits.** r/CardPuter is the centre of gravity; r/CardPuterZero exists for the Linux
-sibling; r/M5Stack carries vendor announcements and support traffic. Cross-posting to
-r/cyberDeck, r/synthdiy, r/meshtastic and r/flipperzero is common.
-
-Selected dated posts, with evidence type:
-
-| Date | Sub | Post | Type |
-|---|---|---|---|
-| 2025-08-17 | r/CardPuter | Evil-Cardputer v1.4.3 release, ↑330/91 | project announcement |
-| 2026-02-27 | r/CardPuter | Plai first beta, ↑153/**139 comments** | project announcement |
-| 2026-03-11 | r/meshtastic | *"Any reason not to just get a Cardputer with lora cap for 55 bucks total even after ship?"*, 19 comments | purchase-decision thread |
-| 2026-04-13 | r/CardPuter | *"What are some cool things you do with your Cardputer, specifically the ADV one?"* | owner discussion |
-| 2026-05-31 | r/CardPuter | *"Guys I messed up big time"*, ↑39/**74 comments** — buyer torn between ADV and Zero. u/G33K_FISH: *"the ADV and the Zero are different. The Zero will be linux based. You can do things on the Zero you can not do on the ADV and vise versa."* u/Fluid-Fortune-432 (owns two ADVs): *"unless you're good with firmwares or coding your own stuff I'd cancel and wait for the zero."* | firsthand ownership opinion |
-| 2026-06-22 | r/CardPuter | Cap TFT-2.8, **↑989/75** | hardware project |
-| 2026-07-13 | r/CardPuter + r/synthdiy | miniacid groovebox, ↑515 + ↑226 | demonstrated project |
-| 2026-08-01 | r/CardPuter | Meshtastic client, no-PSRAM Unicode font | **engineering account** |
-| 2026-08-05 | r/M5Stack | *"Search for screws and buttons for the Cardputer ADV for repair"* — spares are hard to get; M5Stack sells a mixed M3 pack, buttons are 3D-printed | firsthand ownership problem |
-| 2026-08-09 | r/CardPuter | *"What sd card does everybody use with their cardputer Adv?"* | open question, no vendor guidance |
-| 2026-08-22 | r/M5Stack | *"Cardputer adv black screen only when turning it on"* — two replies, unresolved | **unresolved fault report** |
-| 2026-08-29 | r/CardPuter | Plai regression: arrow keys stopped working on ADV | firsthand regression report |
-| 2026-09-04 | r/M5Stack | *"which one should i get? m5stack cardputer adv or t embed c1101 plus?"* | active comparison shopping |
-
-**Prevalence caveat.** These are individual reports from a reviewed sample of ~75 threads
-returned by three Reddit searches on one day. They establish that an experience occurred. They
-do **not** establish how common it is, and no claim in this record depends on frequency.
-
-**M5Stack's own forum (`community.m5stack.com`) could not be searched.** Per
-[`vendors/m5stack`](../../../vendors/m5stack/README.md) §5.3 its search API returns
-`401 not-authorised` and `/search` redirects to login; only `/api/recent` is open. **A negative
-result from the vendor forum is "no determination possible", not "nothing exists."**
-
-Other channels: an official **Discord** (`discord.gg/ysQAWBUE9Q`), M5Stack's Hackster profile,
-and `cardputer-dev/cardputer-site` (★16). No Hackaday article specific to the ADV was located in
-this pass — recorded as a gap.
-
-## 9. Compatibility summary for the ADV
-
-| Firmware | ADV | v1.1 | v1.0 | Basis |
-|---|---|---|---|---|
-| M5Stack `M5Cardputer` ≥ 1.1.1 | ✅ | ✅ | ✅ | autodetect + reader injection |
-| M5Stack factory UserDemo | ✅ (`CardputerADV` branch) | ✅ (`main`) | ✅ | separate branches |
-| Bruce | ✅ runtime-detected | ✅ | ✅ | one build target |
-| Launcher / "M5Launcher" | ✅ documented | ✅ | ✅ | `CardputerADV.md` |
-| Meshtastic upstream | ✅ `m5stack-cardputer-adv` | ❌ no variant | ❌ | variants dir |
-| Plai | ✅ ADV-only | ❌ | ❌ | description |
-| MeshCore ports | ✅ ADV-only | ❌ | ❌ | descriptions |
-| ESP32Marauder | ✅ `_adv` user setup | ✅ | ✅ | code search |
-| Evil-M5Project | ❓ **not established** | ✅ | ✅ | description omits ADV |
-| NEMO | ❓ **inferred only** | ✅ | ✅ | no ADV config; may work via library autodetect |
-| MicroHydra | ❓ not confirmed | ✅ | ✅ | metadata only |
-| Picoware | ✅ named | ❓ | ❓ | description |
-| UiFlow2 | ✅ `/en/uiflow2/cardputer-adv/program` | ✅ `/en/uiflow2/cardputer/program` | ✅ | separate doc paths |
-
-Full status matrix with caveats: [`compatibility-and-status.md`](compatibility-and-status.md).
diff --git a/devices/m5stack/cardputer-adv/research-log.md b/devices/m5stack/cardputer-adv/research-log.md
deleted file mode 100644
index 0f48f33..0000000
--- a/devices/m5stack/cardputer-adv/research-log.md
+++ /dev/null
@@ -1,150 +0,0 @@
-# Cardputer ADV — research log
-
-> One session, **2026-09-04**. Declared depth, exclusions and stopping criterion at the end.
-> Companion: [`commands.md`](commands.md) for the commands, [`sources.md`](sources.md) for the
-> curated source table. This file is the **raw ledger**, including dead ends.
-
-## Method
-
-Followed [`vendors/m5stack/README.md`](../../../vendors/m5stack/README.md) §7 "per-product
-procedure" as written, and it worked without modification. Order of work:
-
-1. Vendor pages, EN + `zh_CN`, for all five family members → asset-URL extraction → product ids.
-2. Schematics and mechanical drawings, hashed.
-3. **Custom PDF text extractor** (no `pdftotext` on this host) → designator census → pin tables.
-4. **Custom PNG cropper** → read the values off rendered sheets rather than trusting the text layer.
-5. Vendor source repositories at pinned commits; read HALs and board tables, not READMEs.
-6. GitHub ecosystem survey; then per-project build configs via `raw.githubusercontent.com`.
-7. Reddit; Shopify; release history.
-
-## Query ledger
-
-### `docs.m5stack.com`
-
-| Query / URL | Result | Disposition |
-|---|---|---|
-| `/en/core/Cardputer-Adv` | 200, 147 339 B | **primary source S1** |
-| `/zh_CN/core/Cardputer-Adv` | 200, 146 690 B | control; **no CN-only asset delta** found (unlike PaperMono) |
-| `/en/core/Cardputer` | 200 | S3 |
-| `/en/core/Cardputer%20V1.1` | 200 | S2 |
-| `/en/core/Cardputer_Mesh_Kit` | 200 | S4 — and the source of conflict C1 |
-| `/en/CardputerZero` | 200, *"Work in progress"* | S5 |
-| `/en/accessory/Cardputer%20Accessory%20Kit` | 200 | S6 |
-| `/en/accessory/Cardputer%20Accessory%20Kit_v1.1` | **404, 4 162 B** | **dead — recorded**; the `_v1.1` form does not exist |
-| `/en/history` | 200 | S7 — dated the three CAP/kit releases |
-| `/en/certification` | **not fetched** | ⚠ **gap.** The vendor guide flags it as a *soft gap* needing a positive control; that control was not run. "Not established", not "absent". |
-| `/en/product_i2c_addr` | **not fetched** | same |
-| `/en/uiflow2/cardputer-adv/program` | **not fetched** | gap; noted that the path differs from the v1.x |
-| `/en/arduino/m5cardputer/program` | **not fetched** | gap |
-| `/en/guide/lora/meshtastic/cardputer_mesh_kit` | **not fetched** | gap; belongs mostly to the Mesh Kit record |
-
-### Aliyun OSS asset enumeration
-
-Product ids recovered from asset URLs: **ADV `1178`**, **v1.1 `1127`**, **v1.0 `481`**,
-**Stamp-S3A `1150`**, **StampS3 `522`**, **Mesh Kit `1240`**, **CardputerZero `1243`**,
-Cap LoRa-1262 `1208`, Cap CC1101 `1250`, SX1262 `1177`, CASIC protocol `1173`.
-
-| Asset | Result |
-|---|---|
-| `1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf` | 200, 878 155 B — **retained** |
-| `1178/…_page_0{1..4}.png` | 200 ×4, 5848×4132 — **retained in scratch, crops made** |
-| `1178/K132-Adv-cardputer-ADV.pdf` | 200, 127 977 B — **retained** |
-| `1150/Sch_StampS3_v0.3.3.pdf` | 200, 369 766 B — belongs to the component |
-| `1127/Sch_M5Cardputer.pdf` + `481/Sch_M5Cardputer.pdf` | 200 — **byte-identical**, finding C3 |
-| `522/Sch_M5StampS3_v0.2.pdf` | 200, 348 884 B — the v1.0 Stamp |
-| `522/Sch_M5StampS3_v0.2_page_01.png` | **402 B, not a PNG** — **dead, recorded**; the render convention is not universal |
-| `1178/IMU-Cardputer-Adv.jpg`, `1178/Cardputer-Adv_{01..13}.webp`, `K132-Adv-weight.jpg` | URLs recorded; **not retained** — imagery unlicensed |
-| `1178/Easy_Loader_for_Cardputer-Adv.exe` | **not downloaded** — gap |
-| `1243/C154-CardputerZERO_SCH_V0.6.1_20260702.pdf`, `1243/CardputerZero_Labels.zip` | **not downloaded** — CardputerZero record is deliberately lighter |
-
-### GitHub
-
-| Query | Depth | Result |
-|---|---|---|
-| `gh search repos cardputer --limit 100` | 100 (**API cap**) | ~40 catalogued in [`projects-and-community.md`](projects-and-community.md); the rest are duplicates/forks/thin |
-| `gh search repos "M5Stick-Launcher"` | 12 | only derivatives — led to discovering the **rename** to `bmorcelli/Launcher` |
-| `gh search repos "marauder cardputer"` | 12 | **0 results** — a false negative; `gh api search/code` inside the repo found 17 files including `User_Setup_marauder_m5cardputer_adv.h`. **Repo search is not a substitute for code search.** |
-| `gh search repos "nemo esp32"` | 12 | 0 useful — same lesson |
-| `gh search repos "M5Launcher"` | 12 | community ports and `CCP101/cardputer-recoverable-multiboot` |
-| `gh api repos/{pr3y/Bruce, bmorcelli/M5Stick-Launcher, justcallmekoko/ESP32Marauder, n0xa/m5stick-nemo, meshtastic/firmware, BruceDevices/firmware, 7h30th3r0n3/Evil-M5Project}` | direct | **two renames discovered** |
-| `gh api search/code repo:… cardputer` ×3 | full | Marauder 17 hits, NEMO 15, Meshtastic 9 |
-| `gh api repos/meshtastic/firmware/contents/variants` | full | **no top-level `cardputer`** — the variant is at `variants/esp32s3/m5stack_cardputer_adv/`. A directory listing at the wrong level produced a false negative first. |
-| `raw.githubusercontent.com` fetches of 6 build configs | — | all 200 |
-| `gh api repos/BruceDevices/firmware/contents/boards` | full | `m5stack-cardputer` — a **directory**, and the `.ini` is *inside* it. First guess (`boards/m5stack-cardputer.ini`) 404'd. |
-
-### Reddit
-
-`old.reddit.com/search.json` with `User-Agent: WhatsApp/2.23.20.0`, three queries, `limit=25`,
-`t=all`:
-
-| Query | Sort | Results | Useful |
-|---|---|---|---|
-| `cardputer adv` | relevance | 25 | 20 |
-| `cardputer` in `r/M5Stack` | new | 25 | 14 |
-| `cardputer` | relevance | 25 | 15 |
-
-Plus four comment threads fetched in full (`/comments/{id}.json?limit=20`): `1tsr5ke`,
-`1vcxsv8`, `1vgmcvn`, `1vv4jk3`. **~75 threads reviewed, ~12 quoted.** Subreddits observed:
-r/CardPuter (dominant), r/CardPuterZero, r/M5Stack, r/cyberDeck, r/synthdiy, r/meshtastic,
-r/flipperzero, r/hacking (no Cardputer-specific hits in the sample).
-
-### Shopify
-
-`search/suggest.json?q=cardputer` → 10 products; `<handle>.json` for four of them.
-**Discovered `[EOL]` on the v1.1** — which no documentation page states.
-
-### Not searched
-
-* **Chinese-language sources** beyond the `zh_CN` docs mirror. No Bilibili, Zhihu, Taobao,
-  CSDN or WeChat search was run. Given M5Stack is a Shenzhen company this is a real gap.
-* **Japanese sources** — the `/ja/` docs tree exists and was not fetched; M5Stack has a large
-  Japanese community (`shikarunochi`, `GOROman`, `Gitshaoxiang` all appear in the repo list).
-* Hackaday, Hackster, YouTube, Discord.
-* AliExpress, Amazon, Taobao, distributor pricing.
-* FCC ID / CE / TELEC databases.
-* `community.m5stack.com` — **auth-walled**, no determination possible.
-* `github.com/m5stack/M5_Hardware` — the docs link `Products/K132-Adv_Cardputer-Adv/Structures`
-  and `Products/K152_Cardputer_Mesh_Kit/Structures`; **neither was fetched.**
-
-## Dead ends and corrections, in order
-
-1. **`pdftotext` absent** → wrote `pdfbbox.py`. Three silent failure modes, each fixed and
-   documented in [`commands.md`](commands.md) §4. The Form-XObject one is the dangerous one: the
-   output *looks* plausible while containing none of the readable text.
-2. **`file` absent** → magic-byte checks in Python instead.
-3. **No image library** → wrote `pngcrop.py`.
-4. **`curl` glob error** on the Shopify bracket syntax → `-g`.
-5. **`522/…_page_01.png` is not a PNG** → the render convention is per-product, not universal.
-6. **`gh search repos` false negatives** for Marauder and NEMO → always follow with
-   `gh api search/code` scoped to the repo.
-7. **Meshtastic variant not at `variants/<name>`** but `variants/esp32s3/<name>` → listing one
-   directory level is not a search.
-8. **Two repository renames** (`pr3y/Bruce`, `bmorcelli/M5Stick-Launcher`) → resolve canonical
-   names via `gh api repos/{old}` before concluding a project is gone.
-9. **Assumed v1.1 used StampS3** (a widely repeated community belief) → **refuted** by M5Stack's
-   own comparison table and the v1.1 page: v1.1 already uses Stamp-S3A. Recorded in
-   [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-10. **Assumed the ADV redesigned the keyboard matrix** → **refuted**: identical matrix, identical
-    nets, identical designators; only the scanner changed.
-
-## Concurrent sessions
-
-At the time of writing, another session was actively creating
-`components/m5stack/stamp-s3`, `stamp-s3a`, `unidentified/m5stack-stamp-s3a/dcdc-u4`,
-`silergy/sy7088`, `sgmicro/sgm2578`, `generic/tp4057`, `sitronix/st7789v2` and
-`devices/m5stack/cap-lora-1262/` (mtimes within 30 minutes). **Those trees were not written to.**
-This record links to them and leaves proposed *Used By* additions in
-[`scratch/m5stack-cardputer/index-fragments.md`](../../../scratch/m5stack-cardputer/index-fragments.md).
-
-## Stopping criterion
-
-Stopped when the **primary evidence was exhausted for the ADV specifically**: every published
-vendor asset for product id `1178` was enumerated and either retrieved or recorded; the
-schematic's designator census was complete with no gaps in the `U` sequence; all four vendor
-source repositories were read at pinned commits; and the GitHub repo search hit its 100-result
-cap with the last two passes returning only duplicates and thin forks.
-
-**Not** stopped because the internet was exhausted. The declared exclusions above — Chinese and
-Japanese sources, certification databases, `M5_Hardware`, M5Burner, marketplace pricing — are
-each a real avenue that a further pass should take. This is a **reproducible broad-coverage
-snapshot dated 2026-09-04**, not a completeness claim.
diff --git a/devices/m5stack/cardputer-adv/resources-and-conflicts.md b/devices/m5stack/cardputer-adv/resources-and-conflicts.md
deleted file mode 100644
index fbc17ff..0000000
--- a/devices/m5stack/cardputer-adv/resources-and-conflicts.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# Cardputer ADV — resources, contention and realistic combinations
-
-> Snapshot **2026-09-04**. The interesting part of this board is not any single peripheral —
-> it is that the keyboard, display, SD card, audio and CAP header all want pieces of the same
-> small pin budget, and the ADV's whole design is a re-allocation of that budget.
-
-## 1. GPIO budget
-
-The Stamp-S3 footprint exposes **26 usable GPIOs** (G0–G15, G21, G33–G46 minus the ones not
-brought out). Here is where they go.
-
-| Consumer | v1.0 / v1.1 | ADV | Δ |
-|---|---|---|---|
-| Keyboard | **15** (G3,G4,G5,G6,G7,G8,G9,G11,G13,G15 + …) — precisely: 8 drive (`Y0..Y7` via 74HC138 from G8/G9/G11) + 7 sense (G13,G15,G3,G4,G5,G6,G7) = **10 GPIOs** | **3** (G8, G9, G11) | **−7** |
-| Display | 6 (G33–G38) | 6 | 0 |
-| microSD | 4 (G12,G14,G39,G40) | 4 | 0 |
-| Audio | 4 (G41,G42,G43,G46) | 4 | 0 |
-| IR | 1 (G44) | 1 | 0 |
-| RGB LED | 1 (G21) | 1 | 0 |
-| Battery ADC | 1 (G10) | 1 | 0 |
-| Grove | 2 (G1,G2) | 2 | 0 |
-| Boot | 1 (G0) | 1 | 0 |
-| **Free / expansion** | **0** (Grove only) | **7** on the CAP header (G3,G4,G5,G6,G13,G15 + the shared G8/G9) | **+7** |
-
-That single row — *free GPIOs: 0 → 7* — is the ADV.
-
-## 2. Buses
-
-| Bus | Members | Arbitration |
-|---|---|---|
-| `SPI3_HOST` (display) | ST7789V2 only | none needed |
-| **SPI peripheral** G40/G14/G39 | microSD (CS **G12**) · CAP board (CS **G5**) | **yours to write** |
-| **I²C internal** G8/G9 | TCA8418 `0x34` · ES8311 `0x18` · BMI270 `0x69` · CAP board's devices | address-based; latency is the real cost |
-| I²C external G1/G2 | nothing on board | free |
-| `I2S_NUM_1` | ES8311, both directions | one codec, one port |
-| `I2S_NUM_0` | **free** | |
-| RMT | WS2812 (G21) · IR TX (G44) | one channel each |
-| LEDC | channel **7** = backlight | 7 channels free |
-| ADC1 | battery (G10) | |
-| GPIO ISR | TCA8418 `INT` (G11) · CAP `INT` (G4) · CAP `BUSY` (G6) · G0 | ESP32-S3 has plenty |
-
-## 3. The two contended resources, in detail
-
-### 3.1 SPI peripheral bus — microSD versus CAP
-
-Same `SCK`/`MOSI`/`MISO`, different `CS`. Neither the vendor library nor any third-party
-firmware installs a mutex for you.
-
-| Failure mode | Cause | Mitigation |
-|---|---|---|
-| Radio stops responding after an SD write | both CS asserted, or bus reconfigured mid-transaction | one `SPIClass`, one owner, explicit CS handling |
-| Corrupt SD reads once a radio is added | clock raised above the transceiver's tolerance, or vice versa | run at the slower device's limit — 16 MHz for an SX1262 |
-| Missed LoRa receive windows | a 512 B block transfer holds the bus while a window opens | short SD transactions; buffer in RAM; do not log inside a receive window |
-| Meshtastic + SD logging flakiness | as above | reported pattern; not reproduced by this session |
-
-M5Stack's own factory firmware runs both (`HAL_PIN_SD_CARD_CS 12` and `HAL_PIN_LORA_NSS_GPIO 5`
-in the same `hal_config.h`), and Meshtastic's ADV variant does too — so the combination is
-**reported-working**, with the timing caveat.
-
-### 3.2 Internal I²C — keyboard versus everything
-
-The keyboard scanner is a *latency-sensitive* device on a bus shared with a codec that gets
-long configuration bursts and an IMU that people poll fast.
-
-| Combination | Effect |
-|---|---|
-| Keyboard + codec enable burst | the codec sequences are 8 register writes; sub-millisecond; TCA8418 has a 10-deep FIFO so events queue, not drop |
-| Keyboard + high-rate IMU polling | competes directly; **not characterised**. If keys feel laggy under IMU load, this is why. |
-| Keyboard + CAP I²C device | depends entirely on the device; a chatty expander on the CAP header will hurt |
-| Bruce's 100 ms polling keyboard | already visibly less responsive than the interrupt path, before any contention |
-
-**Design guidance:** put anything slow, chatty or non-critical on the **Grove** port. The
-internal bus should carry things that *must* be there.
-
-## 4. Memory — the real ceiling
-
-512 KB SRAM, **no PSRAM**, 8 MB flash. This is not a contention problem, it is a hard wall, and
-it shapes what the community builds.
-
-| Consumer | Typical cost |
-|---|---|
-| 240 × 135 × 16 bpp framebuffer | 64 800 B (12.7 % of SRAM) |
-| Double buffering | 129 600 B (25 %) |
-| Wi-Fi + LWIP | ~50–80 KB |
-| TLS session | tens of KB |
-| Audio decode buffers | tens to hundreds of KB |
-| BLE (NimBLE) | smaller than Bluedroid, which is why the factory firmware uses it |
-
-Observed community workarounds:
-
-* **Memory-mapped flash partitions instead of RAM.** The Plai/Meshtastic-client author put a
-  2.16 MB GNU Unifont table in its own partition with fixed-size records so lookup is
-  arithmetic, and mapped it — *"rendering Cyrillic, CJK or Greek costs no heap at all"*
-  (r/CardPuter, 2026-08-01).
-* Meshtastic's ADV variant compiles with **`-DOLEDDISPLAY_REDUCE_MEMORY`**.
-* Bruce ships an `[env_light]` profile and a `-DLITE_VERSION=1` flag "to save space for
-  M5Launcher Compatibility".
-* `engneer-hamachan/area512` is literally named for the constraint: *"A self-contained Ruby &
-  Python development environment for the 512 KB M5Stack Cardputer"*.
-
-## 5. Flash partitioning
-
-| Firmware | Layout |
-|---|---|
-| **M5Stack factory (`CardputerADV` branch)** | `nvs 0x9000/0x4000`, `otadata 0xd000/0x2000`, `phy_init 0xf000/0x1000`, **`factory app 0x10000 / 4 MB`** — single app, **no OTA slots**, ~3.9 MB unallocated |
-| Bruce | `board_build.partitions = custom_8Mb.csv` |
-| Meshtastic ADV | `board_build.partitions = default_8MB.csv` |
-| `CCP101/cardputer-recoverable-multiboot` | a community scheme putting M5Launcher in `factory` and applications in OTA slots — the practical answer to "how do I keep a recovery path" |
-
-The factory layout leaving half the flash unallocated is worth noting: there is room for a
-large data partition (which is exactly what the Unicode-font trick uses).
-
-## 6. Realistic combinations, assessed
-
-| Combination | Status | Evidence |
-|---|---|---|
-| Display + keyboard + SD | **works** | every firmware |
-| Display + keyboard + audio out | **works** | WebRadio, MP3 players, DAW projects |
-| Audio in **then** audio out without re-enable | **fails** | driver defect, [`features/audio.md`](features/audio.md) §6.2 |
-| Display + keyboard + Wi-Fi + audio streaming | **works, RAM-tight** | WebRadio ports |
-| Display + keyboard + CAP LoRa + GNSS | **works** | factory firmware, Meshtastic, Plai |
-| CAP LoRa + SD logging | **works with timing caveats** | §3.1 |
-| Backlight PWM + RGB LED | **fails** | shared `BL_3V3` rail; vendor documents it for v1.1 |
-| IMU motion-wake from deep sleep | **not possible** | no IMU interrupt line traced |
-| Wall-clock time across power cycle | **not possible** | no RTC |
-| Wi-Fi + BLE simultaneously | **works** (time-shared) | ESP32-S3 standard; RAM is the limit |
-| Second display on CAP + built-in display | **works** | `Prokuon/CardputerADV_Cap_TFT-2.8`, `guicmg/cardputer_adv_external_screen` |
-
-## 7. Ownership and arbitration summary
-
-There is **one CPU and no coprocessor**. Nothing on this board arbitrates anything for you:
-no bus mux, no I/O expander on the mainboard, no PMIC with a state machine. Every conflict in
-this document is resolved in your firmware or not at all.
-
-The only piece of hardware that makes a decision on its own is the **headphone-detect network**
-(`HP_DET` → Q4 → `AMP_EN`), which mutes the speaker amplifier when a plug is inserted — and
-software cannot see or override it.
diff --git a/devices/m5stack/cardputer-adv/schematic-netlist.md b/devices/m5stack/cardputer-adv/schematic-netlist.md
deleted file mode 100644
index 13f5f0a..0000000
--- a/devices/m5stack/cardputer-adv/schematic-netlist.md
+++ /dev/null
@@ -1,195 +0,0 @@
-# Cardputer ADV — net list traced from `Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf`
-
-**Traced:** 2026-09-07 · **Method:**
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md)
-· **Tool:** poppler 26.06.0.
-
-**New file.** It does not replace `pinouts-and-buses.md`; where it contradicts an existing claim,
-the contradiction is appended to that file and listed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-## 0. Traceability
-
-4 pages, A4 landscape 842 × 595 pt, `Creator: Altium Designer`. `pdfimages -list` returns
-**zero rows — no embedded raster anywhere in the document.** 1 710 words, 66 `NL` net-label
-tokens, full `CO`/`PI` coverage. **Fully traceable.**
-
-### Calibration of the label-binding rule
-
-Altium floats a net label ~3.2–4.2 pt *above* its wire, and symbol pins here are 7 pt apart, so a
-label is nearly equidistant from the pin above and the pin below. The sign was fixed against a
-known answer before anything else was trusted:
-
-> `U7` (BMI270) pin 1 is `SDO`. The sheet prints **`7-bit Address 69H`** at (196.7–214.3,
-> 114.51), and `R43` 3.3 kΩ runs from `+3.3V` (78.3) down to (136.00, 120.62) and across to
-> `PIU701` at (157.00, 138.37). A BMI270's `SDO` selects the I²C address, so it must be strapped
-> — it cannot also be a GPIO. Therefore `NLG8` (y 142.20) belongs to pin 14 (y 145.37), not to
-> pin 1 (y 138.37): **labels bind downwards.**
-
-Independently confirmed two sheets later: `U9` (TCA8418) has `SDA` and `SCL` on the same
-`G8`/`G9` pair, which is only self-consistent under the same reading.
-
----
-
-## 1. `U7` — BMI270 IMU, sheet 3. **`INT1` and `INT2` are not routed.**
-
-| Pin | Name | Token @ coordinate | Net |
-|---|---|---|---|
-| 1 | `SDO` | `PIU701` @ 157.00, 138.37 | **`R43` 3.3 kΩ pull-up to `+3.3V`** → address `0x69` |
-| 2 | `ASDX` | `PIU702` @ 229.00, 167.37 | *nothing* |
-| 3 | `ASCX` | `PIU703` @ 229.00, 174.37 | *nothing* |
-| 4 | **`INT1`** | `PIU704` @ 157.00, 167.37 | **⚠ nothing — not connected** |
-| 5 | `VDDIO` | `PIU705` @ 229.00, 145.37 | `+3.3V` via `FB7` |
-| 6 | `GNDIO` | `PIU706` @ 157.00, 188.91 | `GND` |
-| 7 | `GND` | `PIU707` @ 157.00, 196.37 | `GND` |
-| 8 | `VDD` | `PIU708` @ 229.00, 138.37 | `+3.3V` through `FB7` 120 Ω/MB ferrite; `C25` 10 µF/10 V, `C27` 100 nF |
-| 9 | **`INT2`** | `PIU709` @ 157.00, 174.37 | **⚠ nothing — not connected** |
-| 10 | `OCSB` | `PIU7010` @ 229.00, 196.37 | *nothing* |
-| 11 | `OSDO` | `PIU7011` @ 229.00, 188.91 | *nothing* |
-| 12 | `CSB` | `PIU7012` @ 229.00, 152.91 | tied to `VDDIO` (I²C mode) |
-| 13 | `SCX` | `PIU7013` @ 157.00, 152.91 | **`G9`** (`NLG9` @ 109.50, 149.20) |
-| 14 | `SDX` | `PIU7014` @ 157.00, 145.37 | **`G8`** (`NLG8` @ 109.50, 142.20) |
-
-### The evidence for "not connected"
-
-A row query at each pin's y across the **entire** page returns only `U7`'s own tokens:
-
-```
-python3 trace.py row <bbox> --y 167.37 --tol 4 --page 3
-  p3 x=157.00 y=167.37  PIU704      p3 x=157.53 y=164.84  4
-  p3 x=176.83 y=168.44  INT1        p3 x=208.60 y=168.44  ASDX
-  p3 x=229.00 y=167.37  PIU702      p3 x=229.72 y=164.84  2
-```
-
-Nothing else on the sheet lies at that height — no net label, no other component pin, no power
-port. The same is true at y=174.37, and at the four OIS pins (2, 3, 10, 11) which are likewise
-bare. Compare pin 8's row, which *does* return `PIC2502`, `PIC2702`, `PIFB701/02` and `+3.3V`.
-
-**Consequence:** IMU motion-wake from deep sleep is **not available on the ADV**. M5Unified's
-polling is not a library shortcoming; there is no interrupt line to use. This closes the
-"not established, not absent" state the record previously carried, in the direction of *absent*.
-
-## 2. `J2` — the Grove / `HY-2.0_IIC` port, sheet 1. **SCL = GPIO1, SDA = GPIO2.**
-
-| `J2` pin | Symbol name | Net label on the wire | Module pin | Module pin name |
-|---|---|---|---|---|
-| 1 | `IIC_SCL` | **`GI`** @ 737.32, 366.41 | `P1.1` | **`G1`** |
-| 2 | `IIC_SDA` | **`GO`** @ 738.58, 373.60 | `P1.2` | **`G2`** |
-| 3 | `VCC` | — | — | 5 V rail via `D8` `PESDNC2FD5VB` |
-| 4 | `GND` | — | — | — |
-
-Pull-ups `R3` and `R10`, both 10 kΩ, sit above the pair (`PIR301`/`PIR1001` @ y 354.6). ESD
-protection is `D6`/`D7` `PESDNC2FD3V3B` on the two signals and `D8` `PESDNC2FD5VB` on `VCC`.
-
-### Why this took a render to settle
-
-The net labels extract as the literal strings **`GI`** and **`GO`** — letter *I*, letter *O*.
-This is not a font-mapping fault: `G0` and `G1` both appear elsewhere on the same sheet and
-extract correctly. A 300 dpi crop shows the module symbol's own pin names printed immediately
-beside them in an unmistakable digit glyph: **`G1`** and **`G2`**.
-
-So the nets are *named* `GI`/`GO` — a vendor typo in the net names — while the pins they land on
-are `G1` and `G2`. Searching the text layer for "G1" or "G2" near `J2` finds nothing, which is
-exactly why earlier passes could not bind them.
-
-**This agrees with M5Unified** (`_pin_table_i2c_ex_in`, `EX SCL = GPIO_NUM_1`,
-`EX SDA = GPIO_NUM_2`) and with Bruce (`-DGROVE_SCL=1 -DGROVE_SDA=2`). The worry that M5Stack's
-yellow-wire convention would invert it is **not borne out by the schematic**.
-
-Independently corroborated on a different product: the M5Stack Cap-Bus connector uses the same
-`GI`/`GO` net names and pairs them explicitly with symbol pin names `SCL` and `SDA` —
-see [`devices/m5stack/cap-lora-1262/schematic-netlist.md`](../cap-lora-1262/schematic-netlist.md).
-
-## 3. `U4` — SY8089 buck. **The feedback arithmetic does resolve.**
-
-| Pin | Name | Token | Connects to |
-|---|---|---|---|
-| 4 | `IN` | `PIU404` @ 582.50, 203.37 | 5 V rail, `C12` 22 µF |
-| 1 | `EN` | `PIU401` @ 582.50, 210.37 | — |
-| 3 | `LX` | `PIU403` @ 640.00, 203.37 | `L2` 4.7 µH `3015` → `+3.3V` |
-| 5 | `FB` | `PIU405` @ 640.00, 232.37 | divider midpoint |
-| 2 | `GND` | `PIU402` @ 582.50, 232.37 | — |
-
-The divider is **`R11` 68 kΩ upper / `R13` 15 kΩ lower**, both in the column at x ≈ 690:
-
-```
-PIR1102 @ 690, 206.9   (to the +3.3V rail at y 203.8)
-PIR1101 @ 690, 228.9 ─┐
-                      ├─ FB node, U4.5 @ 640, 232.37
-PIR1302 @ 691, 235.6 ─┘
-PIR1301 @ 691, 258.2   (to GND at y 280.1)
-COR11 @ 697.50, 214.20 · "68KΩ" @ 702, 222.4
-COR13 @ 698.00, 243.93 · "15KΩ" @ 702, 251.4
-```
-
-Two errors produced the earlier impossible result:
-
-1. **The upper resistor is `R11`, not `R12`.** `R12` is 100 kΩ and sits at `COR12` @ 236.50,
-   221.20 — 450 pt away, on the opposite side of the sheet, in an unrelated network.
-2. **The printed formula `Vout=1.2V*(R1/R2+1)` belongs to `U2`, not `U4`.** It is at
-   (612.67, 157.65), directly beneath the **SY7088** boost converter (`U2`, symbol at y 63–135),
-   about 86 pt above the SY8089. Applied to `U2`'s own divider — `R4` 75 kΩ / `R6` 22 kΩ — it
-   gives 1.2 × (75/22 + 1) = **5.29 V** for the `+5VOUT` rail, which is self-consistent.
-
-With the correct pair, 3.3 V requires a feedback reference of 3.3 / (68/15 + 1) = **0.596 V**.
-A 0.6 V reference makes the design exact. That is *derived from the sheet*, not read from a
-datasheet — no SY8089 datasheet is held in this repository — but 0.6 V is the value commonly
-published for the part, and the agreement to 0.7 % is not a coincidence.
-
-## 4. `U9` — TCA8418RTWR keyboard controller, sheet 2
-
-Address printed on the sheet: **`7-bit Address 34H`** @ (106–142, 312.5).
-
-| Pin | Name | Net | Evidence |
-|---|---|---|---|
-| 1 | `ROW7` | **unconnected** | `PIU901` @ 164.00, 206.91 — no label, no peer |
-| 2–8 | `ROW6`…`ROW0` | `ROW6`…`ROW0` | `NLROW0`…`NLROW6` @ x 184.50, y 152.66–196.20 |
-| 9–18 | `COL0`…`COL9` | `Y7`…`Y0` via 22 R/1 % series resistors `R27`…`R34` | x 164.00, y 221.37–286.37 |
-| 19 | `GND` | `GND` | |
-| 20 | `RESET` | `R38` 10 kΩ pull-up | `PIR382` @ 81.00, 264.37 |
-| 21 | `VCC` | `+3.3V` | |
-| 22 | `SDA` | **`G8`** | `NLG8` @ 77.00, 239.20 |
-| 23 | `SCL` | **`G9`** | `NLG9` @ 77.00, 232.20 |
-| 24 | `INT` | **`G11`** | `NLG11` @ 78.50, 224.66 |
-| 25 | `EP` | `GND` | |
-
-`R35`, `R36`, `R37` — three 3.3 kΩ resistors at x = 48.5 / 59.5 / 70.5, all spanning y 184.57 →
-206.57 — pull up `SDA`, `SCL` **and `INT`** to `+3.3V`. The `INT` pull-up matters: the TCA8418's
-`INT` is open-drain, and the driver deliberately configures its GPIO as plain `INPUT` with no
-internal pull (see the driver audit), which is correct *only because* `R37` exists.
-
-Seven rows are wired, eight columns are used → a 7 × 8 = 56-key matrix.
-
-## 5. `P1` — the Stamp-S3A module footprint, sheet 1
-
-| Pin | Module pin name | Net |
-|---|---|---|
-| 1 | `G1` | `GI` → `J2.1 IIC_SCL` |
-| 2 | `G2` | `GO` → `J2.2 IIC_SDA` |
-| 3–9 | `G3`…`G9` | `G3`…`G9` |
-| 10 | `G10` | `GND` label at +30.0 dx |
-| 11 | `G11` | `G11` → `U9.24 INT` |
-| 12–13 | | `05VIN` (i.e. `+5VIN`; `NL` tokens substitute `0` for `+`) |
-| 14–15 | `G13` | `G13` |
-| 16–17 | `G15` | `G15` |
-
-Note the `NL`-token mangling rule: `NL05VIN` is the net `+5VIN`, not a net called `05VIN`.
-
-## 6. Other named parts on the sheets
-
-`U1` `TP4057` charger (sheet 1) · `U2` `SY7088` boost · `U3` reset/supervisor · `U4` `SY8089`
-buck · `U5` audio amplifier (`INP`/`INN`, sheet 3) · `U6` I²S codec (`CCLK`/`MCLK`, sheet 3) ·
-`U7` `BMI270` · `U8` `MSM381A3729H9BPC` PDM microphone (sheet 3) · `U9` `TCA8418RTWR`.
-
----
-
-## Reproducing
-
-```bash
-nix-shell -p poppler-utils --run 'pdftotext -bbox-layout \
-  "devices/m5stack/cardputer-adv/artifacts/schematic/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf" /tmp/adv.xhtml'
-cd scratch/schematic-tracing
-python3 netlist.py /tmp/adv.xhtml --page 3 --des U7
-python3 netlist.py /tmp/adv.xhtml --page 2 --des U9
-python3 trace.py   row /tmp/adv.xhtml --y 167.37 --tol 4 --page 3    # the INT1 negative result
-```
diff --git a/devices/m5stack/cardputer-adv/sources.md b/devices/m5stack/cardputer-adv/sources.md
deleted file mode 100644
index da60955..0000000
--- a/devices/m5stack/cardputer-adv/sources.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# Cardputer ADV — sources
-
-> Retrieval date for every row below is **2026-09-04** unless a different date is given.
-> `Class` ∈ {primary, authorized mirror, credible mirror, standard, community}.
-> All HTTP fetches used `curl` with the browser User-Agent recorded in
-> [`commands.md`](commands.md); `docs.m5stack.com` and `shop.m5stack.com` served 200 to the
-> first request in every case, consistent with
-> [`vendors/m5stack`](../../../vendors/m5stack/README.md) §1.
-
-## Primary — M5Stack documentation
-
-| ID | Title | Publisher | Class | Medium | URL | Published/updated | Establishes | Limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|
-| **S1** | Cardputer-Adv product page (EN) | M5Stack | primary | official page | `https://docs.m5stack.com/en/core/Cardputer-Adv` | undated | SKU `K132-Adv`, spec table, PinMap, EXT table, schematics/mechanical links, PlatformIO profile, product-comparison table | prose contradicts the v1.1 page on the RGB warning | `artifacts/docs/docs-en-core-Cardputer-Adv.html` (147 339 B, `f05bbb70…`) |
-| S1z | Cardputer-Adv product page (zh_CN) | M5Stack | primary | official page | `https://docs.m5stack.com/zh_CN/core/Cardputer-Adv` | undated | translation control | 146 690 B; **no CN-only datasheet delta found** for this product, unlike the PaperMono case | `artifacts/docs/docs-zh_CN-core-Cardputer-Adv.html` (`4a285b02…`) |
-| **S2** | Cardputer v1.1 product page | M5Stack | primary | official page | `https://docs.m5stack.com/en/core/Cardputer%20V1.1` | undated | SKU `K132-V11`, 74HC138 PinMap, **the RGB/backlight warning**, Stamp-S3A identification, comparison to v1.0 | — | `../cardputer-v1.1/artifacts/docs-en-core-Cardputer-V1.1.html` |
-| **S3** | Cardputer (v1.0) product page | M5Stack | primary | official page | `https://docs.m5stack.com/en/core/Cardputer` | undated | SKU `K132`, StampS3, identical PinMap to v1.1 | — | `../cardputer-v1.0/artifacts/docs-en-core-Cardputer.html` |
-| **S4** | Cardputer Mesh Kit page | M5Stack | primary | official page | `https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit` | undated | SKU `K152`, Cap-Bus table, Meshtastic licensing, LoRa/GNSS specs | ⚠ its **EXT table swaps UART TX/RX** and contradicts its own Cap-Bus table | `../cardputer-mesh-kit/artifacts/docs-en-core-Cardputer_Mesh_Kit.html` |
-| **S5** | CardputerZero page | M5Stack | primary | official page | `https://docs.m5stack.com/en/CardputerZero` | *"Work in progress"* banner | SKU `C154`/`C155`, CM0 platform, TCA8418 + M5IOE1 + RX8130CE + BQ27220, EXT 2.54-14P on a Linux device | explicitly provisional | `../cardputer-zero/artifacts/docs-en-CardputerZero.html` |
-| **S6** | Cardputer Accessory Kit page | M5Stack | primary | official page | `https://docs.m5stack.com/en/accessory/Cardputer%20Accessory%20Kit` | undated | the spare Stamp+display kit; disassembly video reference | the `…_v1.1` URL **404s** (4 162 B) | scratch |
-| **S7** | Release history | M5Stack | primary | official page | `https://docs.m5stack.com/en/history` | live | Mesh Kit 2026-04-30; Cap LoRa-1262 2026-01-04; Cap CC1101 2026-08-28, both categorised *"For Cardputer-Adv"* | paginated — older Cardputer entries not on the first page | scratch |
-| **A1** | **Cardputer-Adv schematic** | M5Stack | primary | schematic PDF, 4 sheets | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf` | file-stamped 2025-06-20 | **the whole component inventory, keyboard matrix, EXT header, power train** | no EDA source published; text layer validated against the PinMap | `artifacts/schematic/…` 878 155 B `9553f5ee…` |
-| A1p | Per-sheet renders of A1 | M5Stack | primary | PNG ×4, 5848×4132 | `…/1178/Sch_M5CardputerAdv_v1.0_…_page_0{1..4}.png` | as A1 | every value transcribed in this record was read from these | large | scratch `media/` |
-| **A2** | **Stamp-S3A schematic** | M5Stack | primary | schematic PDF | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf` | v0.3.3 | AW35122FDR, JW5712, **WS2812 on `BL_3V3`**, USB front end, no UART bridge | ⚠ linked as *"Stamp-S3A"* but **named `StampS3`** | 369 766 B `2f9610ae…`; belongs to [`components/m5stack/stamp-s3a`](../../../components/m5stack/stamp-s3a/README.md) |
-| **A3** | **Cardputer v1.0/v1.1 schematic** | M5Stack | primary | schematic PDF, 2 sheets | `…/1127/Sch_M5Cardputer.pdf` **and** `…/481/Sch_M5Cardputer.pdf` | undated | 74HC138 keyboard, NS4168, SPM1423, same power train | ⚠ **the two URLs are byte-identical** | 717 743 B `6016c1fe…` |
-| A3b | Cardputer base schematic | M5Stack | primary | schematic PDF | `…/1127/M5Cardputer_Base.pdf` = `…/481/Sch_M5cardputer_Base.pdf` | undated | base battery board | byte-identical pair | 24 076 B `29542fe1…` |
-| **A5** | **StampS3 v0.2 schematic** | M5Stack | primary | schematic PDF | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2.pdf` | v0.2 | SGM2578, **WS2812 on `VDD_3V3`**, `M2` regulator | ⚠ **no page render exists** at the `_page_NN.png` convention; the `M2` value string is suspect | 348 884 B `6d92e1ae…` |
-| **A4** | Cardputer-Adv mechanical drawing | M5Stack | primary | dimension PDF | `…/1178/K132-Adv-cardputer-ADV.pdf` | undated | 84.0 × 54.0 × 19.6 mm | — | `artifacts/mechanical/…` 127 977 B `6c937ca0…` |
-| A6 | IMU axis diagram | M5Stack | primary | image | `…/1178/IMU-Cardputer-Adv.jpg` | undated | IMU orientation | **not retained** — imagery is not licensed for redistribution | see [`media.md`](media.md) |
-| A7 | EasyLoader (ADV) | M5Stack | primary | Windows binary | `…/1178/Easy_Loader_for_Cardputer-Adv.exe` | undated | factory image delivery | **not downloaded** | — |
-| S8 | UiFlow2 quick start (ADV) | M5Stack | primary | official page | `https://docs.m5stack.com/en/uiflow2/cardputer-adv/program` | — | a **distinct** UiFlow2 path from the v1.x | **not fetched** | — |
-
-## Primary — M5Stack source code
-
-| ID | Repo | Class | Commit / ref | Establishes | Licence | Local |
-|---|---|---|---|---|---|---|
-| **S10** | `m5stack/M5Cardputer` | primary | **`f1392858b9994c3547120e602a57d3553d16ab01`**, 2026-07-21, v**1.1.1** | keyboard readers, TCA8418 remap, key legend map, board dispatch, examples | **MIT** | `artifacts/source-snapshots/M5Cardputer-f1392858/` (33 files, 284 KB) |
-| **S11** | `m5stack/M5Unified` | primary | **`8530f5377d782e4a25a6c482de2e71c3f75ca8eb`**, 2026-08-27 | I²C/SD/RGB pin tables, ES8311 enable callbacks, power class, button map | MIT | not vendored — quoted with permalinks |
-| **S12** | `m5stack/M5GFX` | primary | **`d91077b9a607b59404e4e4a49f775c792bfae382`**, 2026-08-25 | **the board-autodetect algorithm and M5Stack's own ADV-vs-Cardputer pin comment block**; panel config | MIT | not vendored — quoted with permalinks |
-| **S13** | `m5stack/M5Cardputer-UserDemo`, branch **`CardputerADV`** | primary | **`b549eac0a3c65bc108186c276b8fac0a214aaa4e`**, 2026-06-08 | `hal_config.h`, partition table, sdkconfig, `uart_set_pin` (settles TX/RX), app list | MIT ⚠ pins LGPL-3.0 RadioLib | `artifacts/source-snapshots/M5Cardputer-UserDemo-CardputerADV-b549eac0/` (build config only) |
-| S13b | same repo, `main` | primary | `a34d7ebcd508fb903a2b1123be8c8b54abd55d07`, 2026-07-17 | the v1.x factory firmware | MIT | — |
-
-## Primary — M5Stack commerce
-
-| ID | What | Class | URL | Establishes |
-|---|---|---|---|---|
-| **S9** | Shopify product JSON | primary | `shop.m5stack.com/search/suggest.json?q=cardputer&…` and `/products/<handle>.json` | prices, stock, ids, `created_at`/`published_at`, **the `[EOL]` marking on v1.1** |
-
-## Community — firmware
-
-| ID | Project | Class | Commit / ref at snapshot | Licence | Establishes |
-|---|---|---|---|---|---|
-| **S14** | `BruceDevices/firmware` (formerly `pr3y/Bruce`) | community | `1d555e0d5b201cc91ad201ac40c2482ec00d1ac1`, 2026-08-28 | **AGPL-3.0** | independent pin map; runtime ADV detection at `0x34`; ES8311 addr `0x18`; ADV pin menus |
-| S16 | `bmorcelli/Launcher` (formerly `M5Stick-Launcher`) | community | `3b91484efc5f1a392fac2c4d6066d8306409c688`, 2026-09-04 | MIT | `CardputerADV.md` — independent confirmation of 7×8 matrix, `0x34`, G8/G9/G11; ⚠ contains an I²C-address error |
-| **S17** | `meshtastic/firmware` | community | `be2f68b5af806332c9d877d1643007771bd10c36`, 2026-09-03 | GPL-3.0 | `variant.h` — independent confirmation of **`GPS_TX_PIN 13` / `GPS_RX_PIN 15`**, LoRa pins, `KB_INT 11` |
-| S18 | `justcallmekoko/ESP32Marauder` | community | `91724fd8e964cb6f55cd7da60a3320570919de5b`, 2026-08-24 | none declared | separate `_adv` user setup ⇒ ADV is a distinct target |
-| S19 | `n0xa/m5stick-nemo` | community | `0b8c5c73d5ccf69355be865b07831d47098dbff4`, 2026-07-15 | NOASSERTION | **no ADV config** — a useful negative |
-| S20 | `7h30th3r0n3/Evil-M5Project` | community | pushed 2026-08-20 | **none** | ADV not listed — negative |
-| S21 | `echo-lalia/MicroHydra` | community | pushed 2026-08-21 | GPL-3.0 | MicroPython route |
-| S22 | `d4rkmen/plai` | community | pushed 2026-08-24 | GPL-3.0 | ADV-only Meshtastic client |
-| S23 | `terremoth/awesome-m5stack-cardputer` | community | pushed 2026-09-04 | GPL-3.0 | ecosystem index |
-| S24 | GitHub repo search `cardputer` | community | 2026-09-04, **100 results — the API cap** | — | ecosystem scale and the 2026 ADV skew |
-
-## Community — forums
-
-| ID | Where | Class | Date | Establishes | Evidence type |
-|---|---|---|---|---|---|
-| **S15** | r/CardPuter, *"Meshtastic client firmware for the Cardputer ADV — full Unicode on 240x135 with no PSRAM"* — `old.reddit.com/r/CardPuter/comments/1vcxsv8/` | community | **2026-08-01** | the no-PSRAM constraint and a concrete workaround | firsthand engineering account |
-| S25 | r/CardPuter `…/1rgdwl0/` Plai first beta + comments | community | 2026-02-27, comments to 2026-08-29 | ADV Meshtastic works; **arrow-key regression 2026-08-29** | firsthand user reports |
-| S26 | r/M5Stack `…/1vv4jk3/` *"Cardputer adv black screen only when turning it on"* | community | 2026-08-22 | an unresolved hardware fault report | single anecdote |
-| S27 | r/M5Stack `…/1vgmcvn/` *"Search for screws and buttons … for repair"* | community | 2026-08-05 | spares availability | firsthand ownership problem |
-| S28 | r/CardPuter `…/1tsr5ke/` *"Guys I messed up big time"* + 74 comments | community | 2026-05-31 | ADV-vs-Zero positioning as owners understand it | opinion / firsthand ownership |
-| S29 | r/CardPuter `…/1uclhoi/` Cap TFT-2.8, ↑989 | community | 2026-06-22 | community CAP hardware exists and is popular | demonstrated project |
-| S30 | r/meshtastic `…/1rr1r8b/` *"…lora cap for 55 bucks total"* | community | 2026-03-11 | pre-Mesh-Kit purchase reasoning | discussion |
-| S31 | r/M5Stack `…/1w6qzfu/` *"cardputer adv or t embed c1101 plus?"* | community | **2026-09-04** | live cross-shopping | discussion |
-| — | **`community.m5stack.com`** | primary | — | **could not be searched** — `/api/search` returns `401 not-authorised`, `/search` 302s to login (per `vendors/m5stack` §5.3) | **no determination possible** |
-
-## Repository cross-references
-
-| Record | Why |
-|---|---|
-| [`vendors/m5stack`](../../../vendors/m5stack/README.md) | documentation-sourcing patterns; every technique it describes was re-verified here |
-| [`devices/nicolai-electronics/tanmatsu`](../../nicolai-electronics/tanmatsu/README.md) | comparison target |
-| [`devices/m5stack/cap-lora-1262`](../cap-lora-1262/README.md), [`cap-cc1101`](../cap-cc1101/README.md) | the CAP modules — **owned by a sibling session** |
-| [`guides/markets/`](../../../guides/markets/README.md) | genre guidance |
-
-## Sources deliberately not used
-
-* Vendor marketing prose for any electrical claim. Where prose and code disagreed, code won —
-  four times (§C1 in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) is the clearest case).
-* Any AI-generated summary, aggregator page or SEO listicle.
-* Reddit vote counts as evidence of correctness. They appear only as evidence of *attention*.
diff --git a/devices/m5stack/cardputer-mesh-kit/README.md b/devices/m5stack/cardputer-mesh-kit/README.md
deleted file mode 100644
index 73407ff..0000000
--- a/devices/m5stack/cardputer-mesh-kit/README.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# M5Stack Cardputer Mesh Kit (K152)
-
-> **SKU `K152`** · product id **`1240`** · Shopify `9135211610369`
-> Released **2026-04-30** · **$48.00**, in stock 2026-09-04
-> An **officially licensed Meshtastic device**. Research snapshot **2026-09-04**.
-
-A bundle, not a new board: a **Cardputer ADV in a green back shell** plus a **Cap LoRa-1262**,
-an antenna and hardware, pre-flashed with Meshtastic and — uniquely — **eligible for Meshtastic
-device registration**.
-
-| Component | Record |
-|---|---|
-| Cardputer ADV (host) | [`../cardputer-adv/`](../cardputer-adv/README.md) — **full depth** |
-| Cap LoRa-1262 (module) | [`../cap-lora-1262/`](../cap-lora-1262/README.md) — *owned by a different session* |
-| The host-side CAP interface | [`../cardputer-adv/features/cap-header.md`](../cardputer-adv/features/cap-header.md) |
-
-## Contents
-
-* 1 × Cardputer-Adv (**Green Back Shell Version** — the only place this colourway is sold)
-* 1 × Cap LoRa-1262
-* 1 × LoRa rubber-duck antenna, **RP-SMA**, 108 × 9.3 mm, 3 dBi
-* 2 × M2 × 4 mm cap-head machine screws
-* 1 × 1.5 mm hex key
-* 1 × safety-warning sticker
-
-**Bundle arithmetic:** ADV $29.90 + Cap LoRa-1262 $14.50 = $44.40 versus **$48.00**. The $3.60
-premium buys the antenna, the fasteners, the green shell — and the registration entitlement.
-
-## ⚠ Meshtastic registration is restricted to the kit
-
-M5Stack states it plainly:
-
-> "Only devices in the Cardputer Mesh Kit set can be registered. Other Cardputer/-Adv devices
-> are **not eligible** for Meshtastic authorization registration."
-
-Registration flow: flash Meshtastic (pre-flashed at the factory) → attach the Cap →
-USB-C to a computer → `https://meshtastic-reg.m5stack.com/` → *Connect Device* → select port →
-*Connect*. After success the Meshtastic app shows the device model and an authorisation mark.
-
-**Practical consequence:** an ADV plus a separately bought Cap LoRa-1262 runs identical firmware
-and joins the same mesh, but cannot claim the licensed-device badge. If that matters, buy the
-kit; if it does not, buy the parts and save $3.60.
-
-## Specifications beyond the ADV
-
-Host specs are the ADV's. The kit adds:
-
-| Item | Value |
-|---|---|
-| LoRa transceiver | **SX1262** |
-| Frequency | 868 – 923 MHz |
-| Programmable bit rate | up to 300 kbps |
-| TX power | **+22 dBm** |
-| RX sensitivity | **−147 dBm** (low data rate) |
-| Modulations | FSK / GFSK / MSK / LoRa / OOK |
-| LoRa operating current | DC 5 V @ 163.4 mA |
-| Antenna | RP-SMA (female), 108 × 9.3 mm, 3 dBi |
-| GNSS module | **ATGM336H-6N @ AT6668** |
-| GNSS interface | UART, **115200 8N1** |
-| Constellations | GPS / QZSS / BD2 / BD3 / GAL / GLO, 50 channels |
-| GNSS accuracy | < 1.5 m CEP50, up to 10 Hz |
-| TTFF | cold 23 s, hot 1 s |
-| Cap size / kit weight | 84.0 × 24.0 × 15.2 mm; 77.2 g product, 127.2 g gross |
-
-Component records: [`semtech/sx1262`](../../../components/semtech/sx1262/README.md) (existing);
-the ATGM336H, PI4IOE5V6408 and FM8625H belong to the
-[Cap LoRa-1262 record](../cap-lora-1262/README.md).
-
-## Assembly
-
-1. Turn the Cardputer-Adv over and locate the **EXT 2.54-14P** female header.
-2. Align the Cap's male header and press until seated.
-3. Screw the antenna into the RP-SMA connector.
-
-⚠ **Never transmit without the antenna fitted.** The kit ships a safety sticker for this reason.
-
-## Host-side pin usage
-
-The Cap consumes **every** CAP signal pin:
-
-| Cap function | Host GPIO | Host role |
-|---|---|---|
-| LoRa `NSS` | **G5** | SPI CS |
-| LoRa `RST` | **G3** | out |
-| LoRa `IRQ`/`DIO1` | **G4** | in |
-| LoRa `BUSY` | **G6** | in |
-| LoRa SPI | G40 / G14 / G39 | **shared with the microSD card** |
-| GNSS → host | **G15** | host **RX** |
-| host → GNSS | **G13** | host **TX** |
-| I²C (PI4IOE5V6408, HY2.0-4P) | G8 / G9 | **the host's internal bus** — shares with TCA8418 `0x34`, ES8311 `0x18`, BMI270 `0x69` |
-
-With a Cap fitted the ADV has **no free GPIO left** apart from the Grove port.
-
-**The step people miss:** M5Stack states that initialising the radio requires *"Enable the RF
-antenna switch: set **P0 of the PI4IOE I/O expander to HIGH**"*. That expander is on the host's
-internal I²C bus. Omit it and the SX1262 transmits into a disconnected antenna.
-
-## ⚠ A documentation defect on this product's page
-
-The Mesh Kit page's **"Cardputer-Adv EXT 2.54-14P"** table gives pin 12 = `G13` = `UART_RX` and
-pin 14 = `G15` = `UART_TX`. That is **wrong**, and the same page contradicts it two tables later
-where the Cap-Bus table maps `G13 → GPS-RX`. Four sources agree that **G13 is the host's TX and
-G15 its RX**: the ADV product page, the ADV schematic's symbol pin names, M5Stack's own factory
-firmware `uart_set_pin(port, GPIO_NUM_13 /*tx*/, GPIO_NUM_15 /*rx*/)`, and Meshtastic's
-`variant.h`. Full evidence:
-[`../cardputer-adv/pinouts-and-buses.md` §4](../cardputer-adv/pinouts-and-buses.md).
-
-## Firmware
-
-| Route | Notes |
-|---|---|
-| **Meshtastic upstream** | env `m5stack-cardputer-adv`, `board = m5stack-stamps3`, `default_8MB.csv`. HEAD `be2f68b5` (2026-09-03). **This is what ships.** |
-| M5Stack factory `CardputerADV` branch | includes `main/hal/cap_lora868/` — SX1262 via a vendored RadioLib HAL, `TinyGPSPlus`, and `app_lora_chat` |
-| `d4rkmen/plai` | ADV-only Meshtastic client. A user reports it *"automatically detected the lora cap and switched configurations"* (r/CardPuter, 2026-08-05) |
-| MeshCore ports ×3 | `Stachugit`, `sosprz`, `MultiMote` — a different mesh protocol on the same hardware |
-| `ratspeak/rsCardputer` | Reticulum / LXMF |
-
-Tutorial: `https://docs.m5stack.com/en/guide/lora/meshtastic/cardputer_mesh_kit`
-(recorded, **not fetched** in this pass).
-
-## Where it fits
-
-Before the kit existed, an r/meshtastic thread of **2026-03-11** asked *"Any reason not to just
-get a Cardputer with lora cap for 55 bucks total even after ship?"* (19 comments). The kit is
-M5Stack's answer: the same idea, cheaper, in one box, with a licence.
-
-Against a dedicated Meshtastic node it wins on **input** — a keyboard means composing messages
-without a phone, which is the whole pitch of the ADV-native clients. It loses on battery life
-and ruggedness. Against a LilyGO T-Deck it has a better keyboard and no PSRAM; see
-[`../cardputer-adv/comparisons-and-recommendations.md`](../cardputer-adv/comparisons-and-recommendations.md).
-
-## Sources
-
-Product page `https://docs.m5stack.com/en/core/Cardputer_Mesh_Kit` (retrieved 2026-09-04,
-snapshot at `artifacts/docs-en-core-Cardputer_Mesh_Kit.html`); `/en/history` for the
-2026-04-30 release date; Shopify `<handle>.json`; Meshtastic `variant.h` @ `be2f68b5`.
-Full table: [`../cardputer-adv/sources.md`](../cardputer-adv/sources.md).
diff --git a/devices/m5stack/cardputer-mesh-kit/artifacts/docs-en-core-Cardputer_Mesh_Kit.html b/devices/m5stack/cardputer-mesh-kit/artifacts/docs-en-core-Cardputer_Mesh_Kit.html
deleted file mode 100644
index 0714e9b..0000000
--- a/devices/m5stack/cardputer-mesh-kit/artifacts/docs-en-core-Cardputer_Mesh_Kit.html
+++ /dev/null
@@ -1,114 +0,0 @@
-<!doctype html>
-<html data-n-head-ssr lang="en" data-n-head="%7B%22lang%22:%7B%22ssr%22:%22en%22%7D%7D">
-  <head>
-    <title>m5-docs</title><meta data-n-head="ssr" charset="utf-8"><meta data-n-head="ssr" name="viewport" content="width=device-width,initial-scale=1,minimum-scale=1,user-scalable=no"><meta data-n-head="ssr" data-hid="description" name="description" content="The reference docs for M5Stack products. Quick start, get the detailed information or instructions such as IDE,UIFLOW,Arduino. The tutorials for M5Burner, Firmware, Burning, programming. ESP32,M5StickC,StickV, StickT,M5ATOM."><link data-n-head="ssr" rel="icon" type="image/x-icon" href="/favicon.ico"><script data-n-head="ssr" data-hid="device-preload-detector">!function(){try{var e=document.documentElement;if(!e)return;var d=e.clientWidth||Number.POSITIVE_INFINITY,i=Number(window.innerWidth||0)||Number.POSITIVE_INFINITY,a=Math.min(d,i)<1024;e.classList.add(a?"device-preload-mobile":"device-preload-desktop"),a&&(e.classList.add("device-preload-pending"),window.__m5DevicePreloadReady=function(){e.classList.remove("device-preload-pending"),e.classList.add("device-preload-ready")})}catch(e){}}()</script><script data-n-head="ssr" src="https://cloud.umami.is/script.js" data-website-id="38e73ff2-ec10-4a8f-bfe2-c22a381ce306" defer></script><script data-n-head="ssr" src="/script/ga.js"></script><script data-n-head="ssr" src="/script/global.js"></script><script data-n-head="ssr" src="/public/esp-web-tools/install-button.js?module" type="module"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/marked.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/highlight.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-chat/index.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-qa/index.js"></script><link rel="preload" href="/_nuxt/41d5c62.js" as="script"><link rel="preload" href="/_nuxt/5a34d22.js" as="script"><link rel="preload" href="/_nuxt/a352c6d.js" as="script"><link rel="preload" href="/_nuxt/b9c4bc6.js" as="script"><link rel="preload" href="/_nuxt/c970150.js" as="script"><style data-vue-ssr-id="0b40e9c2:0 afa51714:0 73039f54:0 2576b79a:0 69f1b16c:0 17a511fe:0 3d88442c:0 3afe6180:0 786f8504:0 1af4924a:0 e762b0ec:0 e646c77c:0 4a658548:0 5f76b520:0 3e555512:0 4e0caf6f:0 060bbeb3:0 3ddd7ff2:0 bb0e6f22:0 27d15a7c:0 2c0daf93:0 d1c8934a:0 09fcdd3b:0 3231c87d:0 8716e91a:0 09d04477:0">body,html{width:100%;margin:0;padding:0}html.device-preload-mobile.device-preload-pending{background:linear-gradient(180deg,#f7f9fc,#eef3f8)}html.device-preload-mobile.device-preload-pending body{background:0 0}html.device-preload-mobile.device-preload-pending body:before{content:"";position:fixed;top:0;right:0;bottom:0;left:0;z-index:9999;pointer-events:none;background:linear-gradient(180deg,hsla(0,0%,100%,.92),rgba(243,247,251,.98)),radial-gradient(circle at top right,rgba(0,100,194,.08),transparent 38%)}html.device-preload-mobile.device-preload-pending body:after{content:"";position:fixed;left:50%;top:50%;width:.63529rem;height:.63529rem;margin-left:-.31765rem;margin-top:-.31765rem;z-index:10000;pointer-events:none;border:.04706rem solid rgba(35,141,251,.18);border-top-color:#238dfb;border-radius:50%;box-shadow:0 0 0 .09412rem rgba(35,141,251,.08);-webkit-animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite;animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite}html.device-preload-mobile.device-preload-pending .device-hydration-sensitive{opacity:0;visibility:hidden}html.device-preload-mobile.device-preload-ready body:after,html.device-preload-mobile.device-preload-ready body:before{opacity:0;transition:opacity .22s ease}html.device-preload-mobile.device-preload-ready .device-hydration-sensitive{visibility:visible;opacity:1;transition:opacity .18s ease}@-webkit-keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@-webkit-keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}@keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}html{overflow:hidden;overflow-y:auto}html::-webkit-scrollbar{width:.14118rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}@font-face{font-family:SourceCodePro;src:url(https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/font/SourceCodePro-Regular.ttf)}body,button{font-family:SourceCodePro,Microsoft YaHei;line-height:inherit;box-sizing:border-box}body,button,input{font-family:SourceCodePro,Microsoft YaHei,sans-serif}a{outline:0}.product_pic img{width:33%}.page-enter-active,.page-leave-active{transition:opacity .5s}.page-enter,.page-leave-active{opacity:0}.bounce-enter-active{-webkit-animation:bounce-in .8s;animation:bounce-in .8s}.bounce-leave-active{-webkit-animation:bounce-out .5s;animation:bounce-out .5s}@-webkit-keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@-webkit-keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}body,button,html[lang=zh-cn] footer,html[lang=zh-cn] header,input{font-family:Microsoft YaHei,sans-serif}html[lang=en] footer,html[lang=en] header{font-family:Montserrat,Microsoft YaHei,sans-serif}@font-face{font-family:Montserrat;font-weight:400;font-style:normal;src:url(/assets/fonts/Montserrat-Regular.woff2) format("woff2"),url(/assets/fonts/Montserrat-Regular.woff) format("woff"),url(/assets/fonts/Montserrat-Regular.otf) format("opentype"),url(/assets/fonts/Montserrat-Regular.ttf) format("truetype")}@font-face{font-family:Montserrat;font-weight:500;font-style:normal;src:url(/assets/fonts/Montserrat-Medium.woff2) format("woff2"),url(/assets/fonts/Montserrat-Medium.woff) format("woff"),url(/assets/fonts/Montserrat-Medium.otf) format("opentype"),url(/assets/fonts/Montserrat-Medium.ttf) format("truetype")}*{margin:0;padding:0;box-sizing:border-box}html{height:auto!important;font-size:10vw;line-height:1}@media screen and (max-width:320px){html{font-size:32PX}}@media screen and (min-width:540px){html{font-size:44PX}}@media screen and (min-width:860px){html{font-size:48PX}}@media screen and (min-width:960px){html{font-size:49PX}}@media screen and (min-width:1024px){html{font-size:52PX}}@media screen and (min-width:1175px){html{font-size:53PX}}@media screen and (min-width:1280px){html{font-size:56PX}}@media screen and (min-width:1366px){html{font-size:63PX}}@media screen and (min-width:1400px){html{font-size:68PX}}@media screen and (min-width:1440px){html{font-size:69PX}}@media screen and (min-width:1540px){html{font-size:73PX}}@media screen and (min-width:1680px){html{font-size:75PX}}@media screen and (min-width:1920px){html{font-size:75PX}}@media screen and (min-width:2560px){html{font-size:85PX}}body{-webkit-font-smoothing:subpixel-antialiased}li{list-style-type:none}img,li{-webkit-user-drag:none}img{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}a{text-decoration:none;-webkit-user-drag:none}a,button{outline:0}button{border:none;background-color:transparent;cursor:pointer}.fade-enter-active,.fade-leave-active{transition:opacity .5s}.fade-enter,.fade-leave-to{opacity:0}.markdown.guide img{box-shadow:0 -.07059rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);margin-top:.17647rem;margin-bottom:.58824rem;margin-left:.11765rem}.markdown.guide .blockly_svg{box-shadow:unset;margin:.17647rem 0 .05882rem;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content}.docs-layouts{padding-top:.58824rem;display:flex;justify-content:center;position:relative;margin-bottom:.35294rem}.docs-layouts .docs-layouts-sidebar{position:sticky;top:1.17647rem;left:0;height:-webkit-max-content;height:-moz-max-content;height:max-content;z-index:2;background-color:#fff}.docs-layouts .docs-layouts-title{display:flex;flex-direction:row;margin-bottom:.11765rem;align-items:center;width:100%;height:.47059rem;border-bottom:.03529rem solid #f5f5f5}.docs-layouts .docs-layouts-title .docs-layouts-icon{background-color:#238dfb;border-radius:.11765rem;display:flex;justify-content:center;align-items:center;height:.35294rem;width:.35294rem;margin-right:.11765rem}.docs-layouts .docs-layouts-title .docs-layouts-icon img{width:.23529rem;height:.23529rem}.docs-layouts .docs-layouts-title p{font-size:.23529rem;font-weight:700;color:#2f495e;line-height:.35294rem}.docs-layouts .docs-layouts-body{width:14.11765rem;min-width:0;max-width:100%;margin:0 .29412rem}.docs-layouts .docs-layouts-anchor{position:sticky;top:1.2rem;right:0;z-index:1;background-color:#fff;height:80vh;overflow-y:scroll}@media screen and (max-width:1200px){.docs-layouts .docs-layouts-anchor{display:none}}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar{width:.14118rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.mobile .docs-layouts{padding:.35294rem;display:flex}.mobile .docs-layouts .docs-layouts-body{width:100%;min-width:0;max-width:100%;margin:0}.mobile .docs-layouts .docs-layouts-sidebar{position:fixed;height:100vh;width:5.17647rem;top:0;padding:.47059rem .35294rem;left:auto;left:-100%;box-shadow:.11765rem .23529rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);transition:all .25s ease;z-index:5}.mobile .docs-layouts .docs-layouts-sidebar.active{left:0}.default{color:#3f3f46}.primary{color:#006fee}.secondary{color:#9353d3}.success{color:#17c964}.warning{color:#f5a524}.danger{color:#f31260}.markdown{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-column-gap:.18824rem;-moz-column-gap:.18824rem;column-gap:.18824rem;min-width:0;max-width:100%;overflow:hidden;word-break:break-word;padding-bottom:.35294rem;color:#4f5f6f;font-size:.18824rem;font-weight:400}.markdown>*{grid-column:1/-1}.markdown .product-sku{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .product-date,.markdown .product-sku{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.09412rem 0 .09412rem .09412rem;display:inline-block}.markdown .product-date{background-color:#efefef;color:#345b83}.markdown .tag-green{background-color:#f0fff4;color:#00c58e}.markdown .tag-blue,.markdown .tag-green{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.11765rem;display:inline-block}.markdown .tag-blue{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .tag-orange{font-size:.23529rem;margin:.23529rem .23529rem .23529rem 0;border-radius:.03529rem;padding:.02353rem .11765rem;background-color:#f8b013;color:#fff;cursor:pointer}.markdown .product-title{display:flex;align-items:center}.markdown .product-title span{color:#2f495e}.markdown .shop-title{display:flex;justify-content:space-between;position:relative;margin:.02353rem 0 0 .09412rem;background:#007bff;border-radius:.05882rem;color:#2f495e}.markdown .shop-title .shop-text{width:0;height:.47059rem;line-height:.47059rem;font-size:.2rem;text-align:center;color:#fff;overflow:hidden;transition:all .2s ease}.markdown .shop-title .shop-icon{position:relative;width:.47059rem;height:.47059rem;font-size:.35294rem;text-align:center;display:inline-block}.markdown .shop-title .shop-icon img{width:.35294rem;height:100%;display:inline-block}.markdown .shop-title .shop-icon:before{content:"";position:absolute;top:50%;right:-.32941rem;width:0;height:0;border-left:.23529rem solid transparent;border-right:.23529rem solid transparent;border-bottom:.23529rem solid #007bff;transform:translateY(-50%) rotate(90deg);display:none}.markdown .shop-title .shop-icon.eol:before{display:none}.markdown .shop-title:hover{color:#238dfb}.markdown .shop-title:hover .shop-text{width:2.35294rem}.markdown .shop-title:hover .shop-icon:before{display:block}.markdown .shop-title:hover .shop-icon.eol:before{display:none}.markdown .eol-title{display:flex;align-items:center;position:relative;margin:.02353rem 0 0 .08235rem;padding:0 .17647rem;height:.47059rem;line-height:.47059rem;background-color:#2f495e;border-radius:.05882rem}.markdown .eol-title .eol-text{font-size:.2rem;color:#fff}.markdown video{display:block;width:50%;margin-bottom:.35294rem}.markdown .video-iframe{margin:.23529rem 0;height:5.88235rem}.markdown .video-iframe iframe{width:50%;height:100%}.markdown .video-iframe>a{font-size:.23529rem;display:block;margin-bottom:.23529rem}.markdown a{color:#238dfb}.markdown h1{margin-top:.28235rem;margin-bottom:.21176rem;font-size:.54118rem;line-height:1.25}.markdown h1,.markdown h2{font-weight:600;color:#2f495e}.markdown h2{margin-top:.42353rem;margin-bottom:.18824rem;font-size:.35294rem;line-height:1.35;padding:0 .42353rem .11765rem .16471rem;position:relative;border-bottom:.01176rem solid #dfe5ec;cursor:pointer;transition:all .3s}.markdown h2:after{content:"";width:.03529rem;top:.04706rem;bottom:.16471rem;background:#238dfb;position:absolute;left:0}.markdown h2:before{content:"";position:absolute;background-image:url(/assets/link.svg);width:.29412rem;height:.29412rem;background-size:.29412rem;top:.08235rem;right:.05882rem;opacity:0;transition:opacity .3s}.markdown h2:hover{color:#0064c2}.markdown h2:hover:before{opacity:1}.markdown h3{margin-top:.32941rem;margin-bottom:.16471rem;font-size:.28235rem;color:#34495e;line-height:1.4}.markdown h3,.markdown h4{font-weight:600;position:relative}.markdown h4{margin-top:.28235rem;margin-bottom:.14118rem;font-size:.23529rem;color:#43566a;line-height:1.45}.markdown h5{margin-top:.23529rem;margin-bottom:.11765rem;font-size:.21176rem;font-weight:600;color:#526579;position:relative;line-height:1.5}.markdown ul{margin-bottom:.23529rem}.markdown ul ul{margin-bottom:.11765rem}.markdown ul li{list-style-type:circle;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f}.markdown ol{margin-bottom:.23529rem}.markdown ol li{list-style-type:decimal;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f;padding-left:.05882rem}.markdown ol li::marker{color:#6f6f6f;font-weight:700}.markdown code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;position:relative;color:#263445;font-size:.18824rem}.markdown :not(pre)>code{padding:.02353rem .05882rem;color:#165f8f;background:#eef3f7;border:.01176rem solid #dfe5ec;border-radius:.04706rem;font-size:.92em;font-weight:500}.markdown p{color:#4f5f6f;font-size:.18824rem;font-weight:400;line-height:.31765rem;margin-bottom:.16471rem}.markdown mark{background-color:#ffe051;color:#000}.markdown img{margin-bottom:.35294rem}.markdown>img:not([width]):not([class]){max-width:100%}.markdown .hljs{margin:.05882rem 0 .35294rem;font-size:.18824rem;line-height:.32941rem;white-space:pre;padding:.23529rem .29412rem;overflow-x:auto;overflow-y:hidden;border-radius:.07059rem;background-color:transparent;font-family:SourceCodePro,Microsoft YaHei;width:100%}.markdown .language-bash,.markdown .language-cpp,.markdown .language-diff,.markdown .language-dts,.markdown .language-json,.markdown .language-python,.markdown .language-shell{margin:0;font-size:.18824rem;line-height:.32941rem;white-space:pre;overflow-x:auto;overflow-y:hidden;background-color:transparent;display:block;width:100%}.markdown table thead,.markdown table tr{border-top:.01176rem solid #aabfdc}.markdown .normal-blockquote{box-shadow:-.05882rem 0 0 0 #238dfb;background-color:#fbfcfe;padding:.23529rem;margin:.17647rem 0 .17647rem .05882rem}.markdown .normal-blockquote p{font-weight:500;margin:0}.markdown .table-container{display:block;width:100%;min-width:0;max-width:100%;overflow-x:auto;overflow-y:hidden;overscroll-behavior-inline:contain;-webkit-overflow-scrolling:touch}.markdown table{border:none;display:table;min-width:100%;overflow:auto;margin:.11765rem 0 .35294rem}.markdown table thead{height:.58824rem;background:linear-gradient(-90deg,#1186de,#0064c2)}.markdown table thead tr{line-height:.58824rem;font-size:.18824rem;font-weight:700;color:#fff}.markdown table thead tr th{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr{line-height:.58824rem;font-size:.18824rem;color:#7d7d7d}.markdown table tbody tr td{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr:nth-child(odd){background-color:#fbfcfe}.markdown table tbody tr:nth-child(2n){background-color:#edf4fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table{border:.01176rem solid #e6ebf2;border-collapse:separate;border-spacing:0;border-radius:.07059rem;overflow:hidden;box-shadow:none}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead{height:auto;background:#1f6fe5}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr{border:0;line-height:1.4;font-size:.17647rem;font-weight:600;color:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr th{padding:.10588rem .17647rem;border:0;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr{border:0;line-height:1.5;color:#2c2f36}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td{padding:.10588rem .17647rem;border:0;border-right:.01176rem solid #e6ebf2;border-bottom:.01176rem solid #e6ebf2;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td:last-child{border-right:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(odd){background:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(2n){background:#f7f9fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:last-child td{border-bottom:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:hover{background:#eef3ff}.markdown .compare-table-container .table-container table thead{background:#fff!important}.markdown .compare-table-container .table-container table thead th{color:#2f495e;text-align:center!important;vertical-align:bottom}.markdown .compare-table-container .table-container table thead th a{align-items:center}.markdown .compare-table-container .table-container table thead th img{display:block;width:1.76471rem;height:1.76471rem;-o-object-fit:contain;object-fit:contain;margin:0 auto .35294rem}.markdown .compare-table-container .table-container table thead th:first-child{text-align:center!important;vertical-align:middle}.markdown .compare-table-container .table-container table tbody td:first-child,.markdown .compare-table-container .table-container table tbody td:not(:first-child){text-align:center!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(odd):hover{background:#fff!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(2n):hover{background:#f7f9fc!important}.markdown .table-text-align-left table td,.markdown .table-text-align-left table th{text-align:left}.markdown .table-text-align-right table td,.markdown .table-text-align-right table th{text-align:right}.markdown .markdown-ol li{list-style-type:decimal}.markdown .error,.markdown .tip,.markdown .warn{font-size:.21176rem;border-bottom-right-radius:.02353rem;margin:.11765rem .11765rem .11765rem 0;position:relative;background-color:#fff;box-shadow:.02353rem 0 .08235rem .01176rem #efefef;display:flex;flex-direction:column;color:#838383;font-size:.18824rem;font-weight:400;line-height:.37647rem;border-radius:.07059rem;overflow:hidden}.markdown .error .error-content,.markdown .error .tip-content,.markdown .error .warn-content,.markdown .tip .error-content,.markdown .tip .tip-content,.markdown .tip .warn-content,.markdown .warn .error-content,.markdown .warn .tip-content,.markdown .warn .warn-content{padding:.23529rem}.markdown .error .tip-title,.markdown .tip .tip-title,.markdown .warn .tip-title{height:.41176rem;background-color:rgba(35,141,251,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#238dfb}.markdown .error .warn-title,.markdown .tip .warn-title,.markdown .warn .warn-title{height:.41176rem;background-color:rgba(253,184,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#c69000}.markdown .error .error-title,.markdown .tip .error-title,.markdown .warn .error-title{height:.41176rem;background-color:rgba(253,45,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#ff1616}.markdown .tip:before{background-image:url(/assets/tip.svg)}.markdown .tip:before,.markdown .warn:before{content:"";position:absolute;width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .warn:before{background-image:url(/assets/warning.svg)}.markdown .error:before{content:"";position:absolute;background-image:url(/assets/error.svg);width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .tip{border-left:.07059rem solid #238dfb}.markdown .warn{border-left:.07059rem solid #fdb802}.markdown .error{border-left:.07059rem solid rgba(253,2,2,.83922)}.markdown .learn{display:flex;grid-column:auto;width:100%;height:2.07059rem;margin:.09412rem 0;overflow:hidden;background:#fff;border:.01176rem solid #d3dde9;border-radius:.07059rem;transition:border-color .2s ease,box-shadow .2s ease,transform .2s ease}.markdown .learn:hover{border-color:#8ab4eb;box-shadow:0 .04706rem .14118rem rgba(31,111,229,.1);transform:translateY(-.01176rem)}.markdown .learn:hover .learn-contents{background:#f6f9fe}.markdown .learn .learn-img{flex:0 0 42%;min-height:0;position:relative;overflow:hidden;text-align:center;background:#f7f9fc;border-right:.01176rem solid #e6ebf2}.markdown .learn .learn-img img{display:block;width:100%;max-width:none;box-shadow:none;margin:0;height:100%;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;font-size:.09412rem}.markdown .learn .learn-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.markdown .learn .learn-contents{flex:1;min-width:0;padding:.23529rem;position:relative;display:flex;flex-direction:column;justify-content:center;background:#fbfcfe;transition:background-color .2s ease}.markdown .learn .learn-contents .learn-title{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:2;font-size:.21176rem;font-weight:600;line-height:.29412rem}.markdown .learn .learn-contents .learn-title a{color:#1f6fe5}.markdown .learn .learn-contents .learn-desc{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:3;margin-top:.09412rem;font-size:.18824rem;font-weight:400;color:#5d6673;line-height:.28235rem}.markdown .learn [\:not-has\(\%2B.learn\)]{grid-column:1/-1}.markdown .learn :not(:has(+.learn)){grid-column:1/-1}.markdown .learn [\:not-has\(\%2B.learn\)] .learn-img{flex-basis:2.82353rem}.markdown .learn :not(:has(+.learn)) .learn-img{flex-basis:2.82353rem}.mobile .markdown{grid-template-columns:minmax(0,1fr)}.mobile .markdown p{font-size:.21176rem}.mobile .markdown .learn{flex-direction:row;height:1.88235rem;max-width:none}.mobile .markdown .learn .learn-img{flex:0 0 40%;width:auto;min-height:0;aspect-ratio:auto;border-right:.01176rem solid #e6ebf2;border-bottom:0}.mobile .markdown .learn .learn-contents{padding:.14118rem .16471rem}.mobile .markdown .learn .learn-contents .learn-title{font-size:.18824rem;line-height:.25882rem;-webkit-line-clamp:2}.mobile .markdown .learn .learn-contents .learn-desc{margin-top:.07059rem;font-size:.16471rem;line-height:.24706rem;-webkit-line-clamp:3}@media screen and (max-width:900px){.markdown{grid-template-columns:minmax(0,1fr)}.markdown .learn .learn-img{flex-basis:2.82353rem}}.mobile video{width:100%;margin-bottom:.35294rem}.mobile .video-iframe{margin:.23529rem 0;height:5.88235rem}.mobile .video-iframe iframe{width:100%;height:100%}.easyloader-box{display:flex;flex-direction:row;width:100%}.easyloader-box>div{position:relative;width:50%;overflow:hidden}.easyloader-box p{margin:.11765rem .29412rem;color:#fff}.easyloader-box p:last-child{overflow-y:scroll;height:20%;font-size:.11765rem}.easyloader-mask{position:absolute;right:0;bottom:.07059rem;height:100%;width:100%;background-color:#000;opacity:.7;transition:all .3s;display:flex;flex-direction:column;justify-content:center;display:none}.easyloader-mask a{margin-top:.58824rem;text-align:center}.video_play{bottom:-100%}.easyloader-btn{position:absolute;display:flex;flex-direction:row;justify-content:space-around;bottom:7%;width:100%;padding:0 .23529rem;font-size:.23529rem}.easyloader-btn a{width:1.05882rem;text-align:center;padding:.02353rem .11765rem;background-color:#007bff;color:#fff!important;border-radius:.11765rem;font-size:.17647rem}.easyloader-btn a:hover{background-color:#45a9ff}@media screen and (max-width:768px){.easyloader-box{flex-direction:column;width:100%}.easyloader-box>div{width:100%}}.code-block-wrapper{display:flex;flex-direction:column;position:relative;margin:.16471rem 0 .23529rem;border:.01176rem solid #dfe5ec;border-radius:.07059rem;overflow:hidden;background:#f7f9fb}.code-block-header{display:flex;justify-content:space-between;align-items:center;min-height:.44706rem;padding:.04706rem .14118rem;background:#f0f3f6;border-bottom:.01176rem solid #dfe5ec}.code-block-header .language-label{font-size:.15294rem;color:#526579;font-weight:500}.copy-all-btn{display:flex;align-items:center;grid-gap:.11765rem;gap:.11765rem;justify-content:center;background:0 0;border:none;border-radius:.05882rem;padding:.07059rem;font-size:.16471rem;cursor:pointer;transition:all .2s;width:.37647rem;height:.37647rem;color:#526579}.copy-all-btn svg{width:100%;height:100%}.copy-all-btn code{display:none}.copy-all-btn:hover{color:#1769aa;background:#e4ebf2}.copy-all-btn.focus-visible,.copy-all-btn:focus-visible{color:#1769aa;background:#e4ebf2;outline:.02353rem solid #1769aa;outline-offset:.02353rem}.code-block-container{display:flex;overflow:auto;background:#f7f9fb;align-items:flex-start}.code-block-wrapper.code-block-limited .code-block-container,.code-block-wrapper.code-block-limited .code-line-container{max-height:560px;max-height:var(--code-max-height,560px);overflow:auto;transition:max-height .35s ease}.code-block-wrapper:not(.is-collapsed).code-block-limited .code-block-container,.code-block-wrapper:not(.is-collapsed).code-block-limited .code-line-container{max-height:16.47059rem}.code-toggle-btn{display:flex;align-items:center;justify-content:center;width:100%;min-height:.49412rem;padding:.09412rem .14118rem .11765rem;border:0;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(240,244,249,.96));color:#6b7f93;cursor:pointer;transition:background .2s ease,color .2s ease;position:relative;z-index:2}.code-toggle-btn.focus-visible,.code-toggle-btn:focus-visible,.code-toggle-btn:hover{outline:0;color:#2d7be9;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(228,238,248,.98))}.code-toggle-icon{font-size:.17647rem;line-height:1;transition:transform .25s ease,color .2s ease}.code-block-wrapper:not(.is-collapsed) .code-toggle-icon,.code-toggle-icon{transform:translateY(-.01176rem)}.code-block-fade{position:absolute;left:0;right:0;bottom:.49412rem;height:1.29412rem;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(247,249,251,.96));pointer-events:none;transition:opacity .2s ease;z-index:1}.code-block-wrapper.is-collapsed .code-block-fade{opacity:1}.code-block-wrapper:not(.is-collapsed) .code-block-fade{opacity:0}.markdown .code-block-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-block-container code.hljs{margin:0!important;padding:0!important;border-radius:0;background:0 0;line-height:.32941rem;font-size:.18824rem;white-space:pre}.markdown .code-line-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-line-container code.hljs{margin:0!important;padding:0!important;line-height:.32941rem;font-size:.18824rem;white-space:pre;width:100%;border-radius:0;background-color:transparent}.code-line-container{display:flex;background:#f7f9fb;align-items:center;position:relative;padding:.18824rem .21176rem}.code-line-container .copy-all-btn{opacity:.45;position:absolute;top:.11765rem;right:.11765rem;transition:all .2s}.code-line-container pre{overflow-x:auto}.code-line-container:hover .copy-all-btn,.code-line-container[focus-within] .copy-all-btn{opacity:1}.code-line-container:focus-within .copy-all-btn,.code-line-container:hover .copy-all-btn{opacity:1}@media (hover:none){.code-line-container .copy-all-btn{opacity:1}.markdown .learn:hover{border-color:#d3dde9;box-shadow:none;transform:none}.markdown .learn:hover .learn-contents{background:#fbfcfe}}.line-numbers{padding:.11765rem .09412rem;text-align:right;background:#f3f6f9;color:#8491a0;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;border-right:.01176rem solid #dfe5ec;font-family:SourceCodePro,Microsoft YaHei,sans-serif;line-height:.32941rem;min-width:.51765rem}.line-number{display:block;height:.32941rem}.code-content{flex:1;overflow:auto;padding:.11765rem .17647rem;line-height:.32941rem}.code-block-container,.code-content,.code-line-container pre{scrollbar-color:#c5cfda transparent;scrollbar-width:thin}.code-block-container::-webkit-scrollbar,.code-content::-webkit-scrollbar,.code-line-container pre::-webkit-scrollbar{width:.09412rem;height:.09412rem}.code-block-container::-webkit-scrollbar-thumb,.code-content::-webkit-scrollbar-thumb,.code-line-container pre::-webkit-scrollbar-thumb{background:#c5cfda;border-radius:.04706rem}.code-block-container::-webkit-scrollbar-track,.code-content::-webkit-scrollbar-track,.code-line-container pre::-webkit-scrollbar-track{background:0 0}.code-line{display:block;min-height:.32941rem;line-height:.32941rem;white-space:pre;font-weight:700;font-family:SourceCodePro,Microsoft YaHei,sans-serif}.code-line:hover{background-color:#eaf1f7;cursor:pointer}pre code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;font-size:.18824rem;overflow-y:auto;font-family:SourceCodePro;display:block;width:100%;color:#263445;line-height:.32941rem}code.hljs{background:0 0}pre{position:relative}pre .copy-btn{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;opacity:0;position:absolute;right:.05882rem;top:.05882rem;cursor:pointer;padding:.05882rem;border-radius:.03529rem;transition:.3s;background:hsla(0,0%,100%,.2);width:1.52941rem;height:.58824rem;color:#0064c2}pre .copy-btn:active{background:hsla(0,0%,99.2%,.575)}pre .copy-btn .icon{width:.35294rem;position:absolute;left:70%;top:70%;transform:translate(-50%,-50%)}pre .copy-success-text{color:#fff;position:absolute;font-size:.14118rem;top:.70588rem;font-weight:200;font-family:SourceCodePro,Microsoft YaHei;-webkit-animation:successCopy .5s ease 1 both;animation:successCopy .5s ease 1 both;color:#0064c2}@-webkit-keyframes successCopy{0%{right:0}to{right:.29412rem}}@keyframes successCopy{0%{right:0}to{right:.29412rem}}pre:hover .copy-btn{opacity:1}.files_download{display:flex;flex-direction:row;justify-content:space-evenly;flex-wrap:wrap;margin:.52941rem}.files_download .item{display:flex;justify-content:center;width:2.35294rem;box-shadow:.04706rem .04706rem .08235rem 0 #cecece;transition:all .25s ease}.files_download .item:hover{transform:scale(1.2)}.card-container{display:flex;justify-content:flex-start;margin-bottom:.35294rem;align-items:flex-start}.card-container .card-item{margin:.23529rem;width:3.52941rem;display:flex;flex-direction:column;justify-content:center;align-items:center;color:#fff;transition:all .25s ease}.card-container .card-item .card-cover{height:1.76471rem;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1)}.card-container .card-item .card-cover,.card-container .card-item .card-cover-img{width:100%;display:flex;align-items:center;justify-content:center;font-size:.28235rem;font-weight:700;margin-bottom:.11765rem;border-radius:.11765rem}.card-container .card-item .card-cover-img{position:relative}.card-container .card-item .card-cover-img .card-cover-content{display:none;padding:.11765rem}.card-container .card-item .card-cover-img .card-cover-content .card-cover-btn{display:block;text-align:center;background-color:#0064c2;color:#fff;font-size:.2rem;padding:.11765rem .17647rem;border-radius:.04706rem}.card-container .card-item .card-cover-img img{width:100%;box-shadow:none;margin:0}.card-container .card-item .card-cover-img:hover .card-cover-content{display:flex;flex-direction:column;justify-content:space-around;align-items:center;position:absolute;top:0;left:0;bottom:0;right:0;background-color:rgba(0,0,0,.5098)}.card-container .card-item .card-desc{padding:.17647rem;text-align:center;font-size:.17647rem;color:#2f495e}.card-container .card-item .card-desc a{display:block;text-align:left;color:#333;line-height:.23529rem}.card-container .card-item .card-desc a:hover{text-decoration:underline;color:#238dfb}.card-container .card-item:hover{transform:translateY(-.05882rem)}.card-container .linear-blue{background:linear-gradient(45deg,#09f,#6cf)}.card-container .linear-gray{background:linear-gradient(45deg,#f2f2f2,#ccc);color:#333}.card-container .linear-orange{background:linear-gradient(45deg,#fc0,#f90)}.card-container-video{display:flex;flex-wrap:wrap;grid-gap:.23529rem;gap:.23529rem;margin:.47059rem 0}.card-container-video li{list-style-type:none}.card-container-video .card-item-video{width:22%;position:relative;border-radius:.07059rem;overflow:hidden;transition:transform .3s ease;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1);background-color:#fff}.card-container-video .card-item-video:hover{transform:translateY(-.05882rem);box-shadow:0 .09412rem .18824rem rgba(0,0,0,.15)}.card-container-video .card-item-video:hover .card-cover-content{opacity:1}.card-container-video .card-item-video .card-cover-img{position:relative;width:100%;padding-top:56.25%;background-color:#e7e7e7;overflow:hidden}.card-container-video .card-item-video .card-cover-img img{position:absolute;top:50%;left:50%;width:100%;height:100%;-o-object-fit:cover;object-fit:cover;transform:translate(-50%,-50%);min-width:100%;min-height:100%;transition:transform .3s ease;margin:0}.card-container-video .card-item-video .card-desc-video{padding:.11765rem;text-align:center;font-weight:700}.card-container-video .card-item-video .card-cover-content{position:absolute;top:0;left:0;width:100%;height:100%;display:flex;justify-content:center;align-items:center;background-color:rgba(0,0,0,.5);opacity:0;transition:opacity .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn{display:inline-block;padding:.09412rem .18824rem;margin:0 .11765rem;background-color:#fb7299;color:#fff;border-radius:.04706rem;text-decoration:none;font-size:.16471rem;transition:background-color .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn.youtube{background-color:#f03}.card-container-video .card-item-video .card-cover-content .card-cover-btn.bilibili{background-color:#ff85ad}.mobile .card-item-video{width:40%}.mobile .card-desc-video{font-size:.29412rem}.directory-links-container{display:flex;flex-direction:column}.directory-links-item{page-break-inside:avoid;-moz-column-break-inside:avoid;break-inside:avoid;margin:.11765rem;padding:.17647rem;border-radius:.05882rem;box-shadow:0 0 .05882rem rgba(0,0,0,.1)}.directory-links-body{display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(3.52941rem,1fr));position:relative}.directory-links-item h3{margin-top:0;margin-bottom:.11765rem}.directory-links-item ul{list-style-type:none;padding:0;margin:.18824rem .11765rem}.directory-links-item ul li{margin-bottom:.05882rem}.directory-links-item ul li a{text-decoration:none;color:#333}.directory-links-item ul li a:hover{text-decoration:underline;color:#238dfb}.header-nav .dropdown-icon-wrapper,.pc .nav-dropdown .dropdown-content-right,.pc .nav-dropdown .dropdown-image .image-button{display:flex;justify-content:center;align-items:center}.pc .header-nav-ul .header-nav-item a:hover{color:#0064c2}.mobile .mobile-nav-icon,.mobile .mobile-return-icon{background-repeat:no-repeat;background-size:100% 100%}header{width:100%;position:relative;background-color:#fff;border-bottom:.01176rem solid #e5e5e5;overflow:visible}.header-container{position:relative;margin:0 auto;padding:0 1.17647rem 0 0;width:15.64706rem;height:.70588rem;display:flex;align-items:center;justify-content:flex-end;font-size:.25882rem}.header-container .logo{position:absolute;left:.08235rem;display:block;width:2.08235rem;height:.41176rem;font-size:0;line-height:1;cursor:pointer}.header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.header-nav .dropdown-icon-wrapper{margin-right:.18824rem;width:.25882rem;height:.25882rem}.header-nav .dropdown-icon-wrapper .dropdown-icon{width:auto;height:auto;max-width:100%;max-height:100%;font-size:0}.language-option-box{position:absolute;height:.70588rem;right:-.65882rem;font-size:0;background-color:#fff}.language-option-box .icon{margin-right:.07059rem;width:.2rem;height:auto;color:#434343}.language-option-box .current-language{height:calc(100% - .02353rem);color:#434343;font-size:.22353rem;font-weight:700;display:flex;align-items:center;cursor:pointer;box-sizing:content-box}.language-option-box .language-dropdown-wrapper{display:none;position:fixed;top:.70588rem;padding-top:.11765rem;box-sizing:border-box;width:19.76471rem;left:50%;transform:translateX(-50%);z-index:99999}.language-option-box .language-dropdown-wrapper .language-dropdown{position:absolute;top:.11765rem;right:1.29412rem;width:1.52941rem;color:#434343;background-color:#fff;border-radius:.11765rem;overflow:hidden;box-shadow:0 .09412rem .28235rem rgba(0,0,0,.08);opacity:0;transition:opacity .2s ease}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item{font-size:.21176rem;font-weight:700;line-height:.54118rem;text-align:center;cursor:pointer}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item:hover{color:#0064c2}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item.active{background-color:#dedede}.language-option-box:hover .current-language{border-bottom:.03529rem solid #0064c2}.language-option-box:hover .current-language .header-arrow-btn{transform:rotate(-180deg)}.language-option-box:hover .language-dropdown-wrapper{display:block}.language-option-box:hover .language-dropdown{opacity:1}.disabledHover{cursor:auto!important}.disabledHover a:hover,.disabledHover li:hover,.disabledHover:hover{color:#434343!important}.pc .show-mb{display:none}.pc .header-nav{height:100%;display:flex;align-items:center}.pc .header-nav-ul{height:100%;display:flex;flex-direction:row}.pc .header-nav-ul .header-nav-item{margin-right:.30588rem;padding-left:.23529rem;height:calc(100% - .02353rem);display:flex;align-items:center;font-size:.22353rem;font-weight:700;color:#434343;cursor:pointer;box-sizing:content-box}.pc .header-nav-ul .header-nav-item.active,.pc .header-nav-ul .header-nav-item:hover{border-bottom:.03529rem solid #0064c2}.pc .header-nav-ul .header-nav-item.active .header-arrow-btn,.pc .header-nav-ul .header-nav-item:hover .header-arrow-btn{transform:rotate(-180deg)}.pc .header-nav-ul .header-nav-item:last-of-type{margin-right:0}.pc .header-nav-ul .header-nav-item a{position:relative;color:#434343}.pc .header-arrow-btn{margin-left:.07059rem;width:.11765rem;height:auto;color:#3a3a3a;font-size:0;transition:all .3s ease}.pc .nav-dropdown{position:fixed;left:50%;width:16.70588rem;max-width:calc(100vw - .47059rem);height:3.52941rem;display:flex;transform:translateX(-50%);background-color:#fff;border-radius:.23529rem;z-index:9999}.pc .nav-dropdown .dropdown-content-left{position:relative;padding:.47059rem .32941rem 0;width:calc(100% - 7.45882rem);height:100%;display:flex;justify-content:space-around}.pc .nav-dropdown .dropdown-content-right{width:7.45882rem;height:100%;background-color:#eee;border-radius:0 .23529rem .23529rem 0}.pc .nav-dropdown .dropdown-image{position:relative;width:7.05882rem;border-radius:.23529rem;font-size:0;overflow:hidden}.pc .nav-dropdown .dropdown-image img{width:100%;height:auto}.pc .nav-dropdown .dropdown-image .image-button{position:absolute;left:50%;bottom:.35294rem;transform:translateX(-50%);width:2.35294rem;height:.42353rem;font-size:.18824rem;color:#fff;background-color:#0064c2;border-radius:.04706rem}.pc .nav-dropdown .dropdown-image .image-button:hover{background-color:#058ce6}.pc .nav-dropdown .dropdown-image .image-button .image-icon{margin-right:.11765rem;width:.24706rem;height:auto}.pc .nav-dropdown .dropdown-item{width:3.29412rem;display:flex;flex-direction:column;flex-wrap:wrap}.pc .nav-dropdown .dropdown-item-li{padding-left:.16471rem;display:flex;align-items:center;font-size:.23529rem;font-weight:700;line-height:.70588rem;color:#434343}.pc .nav-dropdown .dropdown-item-li.border{border-bottom:.02353rem solid #dbdbdb}.pc .nav-dropdown .dropdown-item-li:hover{color:#0064c2}.pc .nav-dropdown .dropdown-item-child{margin-top:.18824rem;padding-left:.18824rem;display:flex;flex-direction:column}.pc .nav-dropdown .dropdown-child-li{margin-bottom:.14118rem;display:flex;align-items:center;font-size:.21176rem;font-weight:500;white-space:nowrap;color:#434343}.pc .nav-dropdown .dropdown-child-li:hover{color:#0064c2}.pc header #store{height:4.70588rem}.pc header #store .dropdown-item:first-child{width:2.21176rem}.pc header #store .dropdown-item:first-child .dropdown-child-li:nth-child(2) .dropdown-icon-wrapper{height:.32941rem}.pc header #store .dropdown-item:nth-child(2){width:4.65882rem;height:3.05882rem;border-bottom:.02353rem solid #dbdbdb}.pc header #store .dropdown-item:nth-child(2) .dropdown-item-child{width:90%;height:2rem;flex-wrap:wrap}.pc header #store .dropdown-item:nth-child(3),.pc header #store .dropdown-item:nth-child(4){position:absolute;bottom:.47059rem}.pc header #store .dropdown-item:nth-child(3){right:3.38824rem;width:2.04706rem}.pc header #store .dropdown-item:nth-child(3) .dropdown-icon-wrapper{margin-right:.14118rem;width:.32941rem}.pc header #store .dropdown-item:nth-child(4){right:.75294rem;width:2.58824rem}.pc header #software{height:4rem}.pc header #software .dropdown-content-left{width:calc(100% - 6.03529rem)}.pc header #software .dropdown-content-right{width:6.03529rem}.pc header #software .dropdown-image{width:5.58824rem}.pc header #software .dropdown-item:first-child{width:3.17647rem}.pc header #software .dropdown-item:nth-child(2){width:2.82353rem}.pc header #software .dropdown-item:nth-child(3){width:2.91765rem}.pc header #document{height:4.47059rem}.pc header #document .dropdown-content-left{width:100%}.pc header #document .dropdown-item:first-child .dropdown-item-child,.pc header #document .dropdown-item:nth-child(2) .dropdown-item-child{height:2rem;flex-wrap:wrap}.pc header #document .dropdown-item:first-child{width:4.65882rem}.pc header #document .dropdown-item:nth-child(2){width:5.01176rem}.pc header #document .dropdown-item:nth-child(3){width:3.76471rem}.pc header #aboutus{height:4.21176rem}.pc header #contact{height:1.05882rem;background-color:transparent}.pc header #contact .dropdown-content-left{position:absolute;padding:.09412rem 0;right:1.29412rem;width:2rem;height:1.05882rem;flex-direction:column;background-color:#fff;border-radius:.11765rem}.pc header #contact .dropdown-item{width:100%}.pc header #contact .dropdown-item .dropdown-item-li{padding-left:0;width:100%;justify-content:center;font-size:.21176rem;line-height:.42353rem}.mobile .show-pc,.mobile .snize-sticky-searchbox{display:none}.mobile header{height:1.10588rem;border-bottom:unset}.mobile .header-container{padding:0 .35294rem;width:100%;max-width:100%;height:1.10588rem;justify-content:unset;z-index:9999;box-shadow:0 0 .18824rem 0 hsla(0,0%,51.4%,.15)}.mobile .header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.mobile .mobile-nav-icon{width:.54118rem;height:.54118rem;background-image:url(/assets/menu.png);transition:all .28s ease}.mobile .mobile-nav-icon.active{transform:rotate(90deg)}.mobile .mobile-return-icon{position:absolute;left:1.2rem;width:.32941rem;height:.32941rem;background-image:url(/assets/return.png)}.mobile .logo{left:50%;width:2.47059rem;height:.48235rem;transform:translateX(-50%)}.mobile .header-nav{display:none;position:absolute;top:1.10588rem;left:0;padding:.18824rem 0 1.01176rem;width:5.17647rem;max-width:100%;background-color:#fff;z-index:9998}.mobile .header-nav.show{display:block}.mobile .header-nav-ul{margin-bottom:.23529rem}.mobile .header-nav-ul .header-nav-item{position:relative;padding-left:.47059rem;height:1.10588rem;font-size:.36471rem;font-weight:400;line-height:1.10588rem}.mobile .header-nav-ul .header-nav-item,.mobile .header-nav-ul .header-nav-item a{color:#434343}.mobile .header-nav-ul .header-nav-item.selected{background-color:#f7f7f7}.mobile .header-nav-ul .header-nav-item.active .header-mbnav-btn{transform:rotate(90deg)}.mobile .header-nav-ul .header-nav-item.active+.nav-dropdown{display:block}.mobile .header-mbnav-btn{position:absolute;width:.58824rem;height:.58824rem;top:.23529rem;right:.23529rem;background-image:url(/assets/arrow3.png);background-repeat:no-repeat;background-size:50% 50%;background-position:50%}.mobile .nav-dropdown{display:none;position:relative}.mobile .nav-dropdown .dropdown-content-left{width:100%}.mobile .nav-dropdown .dropdown-icon-wrapper{width:.47059rem;height:.47059rem}.mobile .nav-dropdown .dropdown-item-li{padding-left:.71765rem;width:100%;height:.88235rem;display:flex;align-items:center;font-size:.32941rem;font-weight:400;color:#434343}.mobile .nav-dropdown .dropdown-child-li{padding-left:.89412rem;width:100%;height:.82353rem;display:flex;align-items:center;font-size:.30588rem;line-height:.82353rem;white-space:nowrap;color:#434343}.mobile .language-option-box{height:1.10588rem;right:.25882rem}.mobile .language-option-box .icon{width:.35294rem}.mobile .language-option-box .current-language{font-size:.30588rem;font-weight:500}.mobile .language-option-box .language-dropdown-wrapper{width:100%;top:1.10588rem;padding-top:.11765rem;box-sizing:border-box}.mobile .language-option-box .language-dropdown{right:.11765rem;width:2.23529rem}.mobile .language-option-box .language-dropdown .language-item{font-size:.35294rem;font-weight:500;line-height:.70588rem}.header-nav-dd-pc-enter-active,.header-nav-dd-pc-leave-active{transition:opacity .2s ease-out,transform .22s cubic-bezier(.4,0,.2,1)}.header-nav-dd-pc-enter,.header-nav-dd-pc-leave-to{opacity:0;transform:translateX(-50%) translateY(-.09412rem)!important}.header-nav-dd-pc-enter-to,.header-nav-dd-pc-leave{opacity:1;transform:translateX(-50%) translateY(0)!important}.header-nav-dd-mb-enter-active,.header-nav-dd-mb-leave-active{transition:opacity .18s ease-out}.header-nav-dd-mb-enter,.header-nav-dd-mb-leave-to{opacity:0}.viewer-open .mobile .header-container,.viewer-open .mobile .language-dropdown-wrapper,.viewer-open .mobile .language-option-box{z-index:1!important}.viewer-open .mobile .language-option-box{pointer-events:none}.title-level2{height:.32941rem;font-size:.35294rem;font-weight:400;color:#434343;line-height:.32941rem;padding-left:.22353rem;position:relative;display:flex;justify-content:space-between;margin:.58824rem 0}.title-level2 .title-level2-desc{font-size:.18824rem;font-weight:400}.title-level2:after{content:"";width:.04706rem;height:.35294rem;background:#0064c2;position:absolute;left:0}.title-level3{height:.27059rem;font-size:.29412rem;font-weight:400;color:#434343;line-height:.27059rem;padding-left:.14118rem;position:relative;display:flex;justify-content:space-between;margin:.47059rem 0 .35294rem}.title-level3 .title-level3-desc{font-size:.14118rem;font-weight:400}.pc .product-list-container .Products{display:flex;flex-wrap:wrap;margin-bottom:.70588rem}.pc .product-list-container .ProductItem{border-top:.01176rem solid #e5e5e5;border-bottom:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(2n),.pc .product-list-container .ProductItem:nth-child(2n-1){border-right:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(3n){border-right:0 solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(n+4){border-top:0 solid #e5e5e5}.pc .product-list-container .ProductItem{height:4.51765rem;width:4.65882rem;text-align:center;position:relative}.pc .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.pc .product-list-container .ProductItem .ProductPic{text-align:center;width:2.35294rem;height:2.35294rem}.pc .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.pc .product-list-container .ProductItem .ProductName{margin-top:.11765rem;line-height:.29412rem;height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343}.pc .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto .17647rem;width:2.47059rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.23529rem;text-overflow:clip;overflow:hidden}.pc .product-list-container .ProductItem .product-btn-group{width:1.76471rem;height:.35294rem;border-radius:.17647rem;margin:auto;display:flex}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.29412rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.35294rem;font-size:.18824rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.47059rem;height:.35294rem;background-size:.23529rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.pc .product-list-container .ProductLinks{padding:0 .17647rem;font-size:.18824rem;display:grid;justify-content:start;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(2.82353rem,1fr));position:relative;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink:hover{color:#409eff;-webkit-text-decoration-line:underline;text-decoration-line:underline}.mobile .product-list-container{text-align:left}.mobile .product-list-container .ProductItem{text-align:center;height:5.17647rem;width:50%;border:.02353rem solid #e5e5e5;background-color:#fff;position:relative}.mobile .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.mobile .product-list-container .ProductItem .ProductPic{margin:.11765rem auto;text-align:center;width:2.82353rem;height:2.82353rem}.mobile .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.mobile .product-list-container .ProductItem .ProductName{height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343;line-height:.28235rem}.mobile .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto;display:block;width:2.36471rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.25882rem;overflow:hidden}.mobile .product-list-container .ProductItem .product-btn-group{width:2.35294rem;height:.47059rem;border-radius:.17647rem;margin:auto;display:flex}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.64706rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.47059rem;font-size:.23529rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.70588rem;height:.47059rem;background-size:.29412rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.mobile .product-list-container .ProductLinks{padding:.11765rem .17647rem;font-size:.25882rem;display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fit,minmax(3.52941rem,1fr));position:relative;margin-bottom:.14118rem;background-color:#fff}.mobile .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.14118rem}.product-list-container.hideEol .ProductItem.EOL{display:none}.footer-email-input input::-webkit-input-placeholder{font-family:Microsoft YaHei,sans-serif}.subscribe-btn{display:flex;justify-content:center;align-items:center}.pc .footer-bottom-content a:hover,.pc .footer-nav-li a:hover{color:#0064c2}.subscribe-btn:hover{background-color:#0074e1}.mobile .footer-nav-btn{background-repeat:no-repeat;background-size:100% 100%}.footer-container{width:100%;color:#fff;background-color:#000}.footer-content-wrap{height:100%;display:flex;align-items:center}.footer-email-title,.footer-qrcode-title{font-size:.32941rem;margin-bottom:.21176rem;font-weight:500;color:#fff}.footer-email-desc{font-weight:400;color:#f1f1f1}.footer-email-input{display:flex}.footer-email-input input{background:hsla(0,0%,60%,.55);border:.01176rem solid #0077c8;border-radius:.04706rem;padding:0 .23529rem;color:#fff;outline:0}.footer-email-input input::-webkit-input-placeholder{font-weight:400;color:#a0a0a0}.subscribe-btn{background:#0077c8;width:1.55294rem;height:.56471rem;font-size:.21176rem;font-weight:500;color:#fff;border-radius:.07059rem}.footer-follow{margin-top:.42353rem;width:90%}.footer-follow-ul{display:flex;flex-wrap:wrap}.footer-info-wrapper{margin-top:.47059rem;font-size:.16471rem;color:#a0a0a0}.footer-email-warning{margin-top:.11765rem;display:none;font-size:.18824rem;color:#ff2529}.footer-email-success{margin-top:.35294rem;margin-bottom:1.15294rem;display:none;font-size:.35294rem;color:#fff}.pc .footer-container{height:8.23529rem}.pc .footer-content-wrap{width:15.64706rem;margin:0 auto}.pc .footer-nav{padding:.70588rem 0 .11765rem;width:65%;height:100%;display:flex;flex-direction:column;flex-wrap:wrap}.pc .footer-nav-item{margin:0 0 .47059rem}.pc .footer-nav-title{margin-bottom:.18824rem;font-size:.29412rem;font-weight:500;color:#fff}.pc .footer-nav-title a{color:#fff}.pc .footer-nav-li{font-size:.21176rem;font-weight:400;color:#a0a0a0;line-height:.38824rem}.pc .footer-nav-li a{color:#a0a0a0;cursor:pointer}.pc .footer-right{width:35%;height:5.95294rem;padding:0 0 0 .47059rem}.pc .footer-email-title,.pc .footer-qrcode-title{margin-top:.14118rem}.pc .footer-email-desc{font-size:.21176rem;line-height:.32941rem;margin-bottom:.14118rem}.pc .footer-email-input input{width:3.71765rem;height:.56471rem;font-size:.21176rem;margin-right:.12941rem}.pc .footer-email-input input::-webkit-input-placeholder{font-size:.21176rem}.pc .footer-qrcode-list{display:flex}.pc .footer-qrcode-list .footer-qrcode-item{margin-right:.11765rem}.pc .footer-qrcode-list .footer-qrcode-img{width:1.88235rem;height:auto}.pc .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.pc .footer-qrcode-list .footer-qrcode-name{font-size:.21176rem;color:#a0a0a0}.pc .footer-follow-ul{width:100%}.pc .footer-follow-ul a{display:block;margin-right:.11765rem;margin-bottom:.11765rem;font-size:0}.pc .footer-follow-ul img{width:.58824rem;height:.58824rem}.pc .footer-address-info{line-height:.23529rem;margin:.05882rem 0}.pc .footer-info{line-height:.32941rem}.pc .footer-bottom{width:100%;height:.77647rem;background-color:#000}.pc .footer-bottom-content{margin:0 auto;padding:.23529rem .23529rem 0;width:16.07059rem;height:100%;display:flex;justify-content:space-between;font-size:.15294rem;font-weight:400;color:#a0a0a0;border-top:.01176rem solid #6d6d6d}.pc .footer-bottom-content a{display:inline-block;color:#a0a0a0;font-weight:400;font-size:.15294rem}.pc .terms-box{margin-left:.54118rem;display:flex}.pc .terms-box a{margin:0 .09412rem}.mobile .footer-container{height:11.76471rem}.mobile .footer-right{padding:0;width:100%}.mobile .footer-email-group,.mobile .footer-right{display:flex;flex-direction:column;align-items:center}.mobile .footer-email-title,.mobile .footer-qrcode-title{font-size:.58824rem;margin-bottom:.25882rem}.mobile .footer-email-success{font-size:.51765rem;margin-top:1.17647rem;margin-bottom:1.27059rem}.mobile .footer-email-desc{width:5.52941rem;font-size:.35294rem;line-height:.47059rem;text-align:center;margin-bottom:.75294rem}.mobile .footer-email-input{flex-direction:column;align-items:center}.mobile .footer-email-input input{width:7.35294rem;height:.70588rem;margin-bottom:.47059rem;font-size:.32941rem}.mobile .footer-email-input input::-webkit-input-placeholder{font-size:.32941rem}.mobile .subscribe-btn{width:2.75294rem;height:.70588rem;border-radius:.07059rem;font-size:.32941rem}.mobile .footer-email-warning{font-size:.29412rem;margin-top:.18824rem}.mobile .footer-qrcode-title{text-align:center}.mobile .footer-qrcode-list{display:flex}.mobile .footer-qrcode-list .footer-qrcode-item{margin-right:.35294rem}.mobile .footer-qrcode-list .footer-qrcode-img{width:3.05882rem;height:auto}.mobile .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.mobile .footer-qrcode-list .footer-qrcode-name{margin-top:.11765rem;font-size:.35294rem;color:#a0a0a0;text-align:center}.mobile .footer-follow{margin-top:.82353rem;width:100%}.mobile .footer-follow-ul{width:80%;margin:0 auto;justify-content:center}.mobile .footer-follow-ul a{margin-right:.23529rem}.mobile .footer-follow-ul a:nth-child(5){margin-right:0}.mobile .footer-follow-ul img{width:1.05882rem;height:1.05882rem}.mobile .footer-qrcode-img{width:2.82353rem;height:2.82353rem;margin:0 auto}.mobile .footer-qrcode-img img{width:100%;height:auto;max-height:100%}.mobile .footer-info-wrapper{width:95%;margin-top:.47059rem;font-size:.23529rem;text-align:center}.mobile .footer-address-info{line-height:.35294rem;margin:.05882rem 0}.mobile .footer-info{line-height:.44706rem}.mobile .footer-bottom{display:none}.mobile .footer-nav{background-color:#fff;border-top:.03529rem solid #eee}.mobile .footer-nav-item:nth-child(3) .footer-nav-title a{display:block}.mobile .footer-nav-title{position:relative;padding:0 0 0 .71765rem;font-size:.36471rem;line-height:1.10588rem;font-weight:500;color:#a6a6a6;height:1.10588rem;border-bottom:.03529rem solid #eee}.mobile .footer-nav-title a{color:#a6a6a6}.mobile .footer-nav-title.active .footer-nav-btn{transform:rotate(90deg)}.mobile .footer-nav-title.active+.footer-nav-ul{display:block}.mobile .footer-nav-btn{position:absolute;width:.2rem;height:.36471rem;top:.35294rem;right:.41176rem;background-image:url(/assets/arrow2.png)}.mobile .footer-nav-ul{display:none;border-bottom:.03529rem solid #eee}.mobile .footer-nav-li{font-size:.25882rem;font-weight:400;color:#a0a0a0;line-height:.65882rem;padding:0 0 0 .91765rem}.mobile .footer-nav-li a{color:#a0a0a0}.product-demo-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(2rem,1fr));grid-gap:.16471rem;gap:.16471rem;margin:.21176rem 0 .32941rem}.product-demo-item{display:flex;flex-direction:column;align-items:center;justify-content:flex-start;text-decoration:none;color:#1f2937;background:#fff;border:.01176rem solid #e5e7eb;border-radius:.14118rem;overflow:hidden;transition:transform .2s ease,border-color .2s ease;height:100%}.product-demo-item:hover{transform:translateY(-.03529rem);border-color:#93c5fd}.product-demo-item img{width:100%;height:1.41176rem;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;display:block;background:#f8fafc;box-shadow:none!important;flex-shrink:0}.product-demo-item span{display:block;width:100%;padding:.11765rem;font-size:.15294rem;line-height:1.4;font-weight:600;margin-top:auto;text-align:center}.scene-application-card{position:relative;display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.12fr);align-items:stretch;min-height:4rem;color:#0f172a;text-decoration:none;border-radius:.23529rem;overflow:hidden;background-color:#f8fafc;border:none;box-shadow:0 .21176rem .47059rem rgba(15,23,42,.1);border:.01176rem solid rgba(148,163,184,.22)}.scene-application-card--scene1{background-image:linear-gradient(180deg,rgba(15,23,42,.08),rgba(15,23,42,.56)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:50%}.scene-application-card--scene2{background-image:linear-gradient(180deg,rgba(15,23,42,.1),rgba(15,23,42,.58)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:64%}.scene-application-card:hover{color:#0f172a}.scene-application-card,.scene-application-card .scene-application-card__title,.scene-application-card p,.scene-application-card span:not(.scene-application-card__button){color:#0f172a!important}.scene-application-card__media{position:relative;display:flex;align-items:center;justify-content:center;min-height:100%;overflow:hidden;padding:.18824rem .21176rem .18824rem .14118rem;line-height:0}.scene-application-card__media img{flex:none;width:88%;max-width:4.94118rem;max-width:100%;height:auto;max-height:100%;display:block;margin:0!important;padding:0!important;border:.01176rem solid rgba(148,163,184,.34);border-radius:.16471rem;box-shadow:0 .11765rem .28235rem rgba(15,23,42,.16);vertical-align:top;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center}.scene-application-card__content{position:relative;z-index:1;display:flex;flex-direction:column;justify-content:center;grid-row-gap:.14118rem;row-gap:.14118rem;width:100%;max-width:5.17647rem;min-height:100%;padding:.32941rem .30588rem .28235rem;background:linear-gradient(180deg,hsla(0,0%,100%,.96),rgba(248,250,252,.9))}.scene-application-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-gap:.21176rem;gap:.21176rem;margin:.21176rem 0 .32941rem}.scene-application-card__title{margin:.09412rem 0 0;font-size:.32941rem;line-height:1.15;font-weight:700;text-align:center;color:#0f172a!important;text-shadow:none}.scene-application-card__desc{margin:0;font-size:.17647rem;line-height:1.6;text-align:center;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden;text-overflow:ellipsis;color:rgba(30,41,59,.9)!important;text-shadow:none}.scene-application-card__button{display:inline-flex;align-items:center;justify-content:center;align-self:center;margin-top:0;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content;min-width:1.22353rem;padding:.11765rem .18824rem;font-size:.16471rem;line-height:1;font-weight:600;white-space:nowrap;color:#fff!important;background:#2563eb;border-radius:11.75294rem;box-shadow:0 .09412rem .21176rem rgba(37,99,235,.28)}.scene-application-card .scene-application-card__button{color:#fff!important}.mobile .product-demo-grid{grid-template-columns:repeat(3,minmax(0,1fr));grid-gap:.09412rem;gap:.09412rem}.mobile .product-demo-item{border-radius:.09412rem}.mobile .product-demo-item img{height:auto;aspect-ratio:1/1;-o-object-fit:contain;object-fit:contain;-o-object-position:center;object-position:center;padding:.09412rem;box-shadow:none!important}.mobile .product-demo-item span{padding:.07059rem .07059rem .09412rem;font-size:.21176rem;line-height:1.4;text-align:center;word-break:break-word}.mobile .scene-application-card{grid-template-columns:1fr;grid-template-rows:2.35294rem minmax(0,1fr);min-height:4.58824rem;margin:0;border-radius:.16471rem}.mobile .scene-application-card__media{order:1;min-height:2.35294rem;padding:.11765rem .14118rem}.mobile .scene-application-card__media img{width:100%;max-width:none;max-height:none}.mobile .scene-application-grid{grid-template-columns:1fr;grid-gap:.16471rem;gap:.16471rem}.mobile .scene-application-card__content{order:2;max-width:none;justify-content:center;padding:.23529rem .21176rem;background:linear-gradient(180deg,hsla(0,0%,100%,.97),rgba(248,250,252,.93));grid-row-gap:.11765rem;row-gap:.11765rem}.mobile .scene-application-card__title{font-size:.25882rem;line-height:1.2;margin-top:.07059rem}.mobile .scene-application-card__desc{font-size:.15294rem;line-height:1.5;-webkit-line-clamp:4}.mobile .scene-application-card__button{min-width:1.17647rem;margin-top:.09412rem;padding:.10588rem .16471rem;font-size:.15294rem}.project-item{display:flex;height:1.96471rem;margin:.11765rem 0}.project-item .project-img{width:1.96471rem;height:1.96471rem;position:relative;overflow:hidden;text-align:center}.project-item .project-img img{height:100%;font-size:.09412rem}.project-item .project-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.project-item .project-contents{flex:1;background-color:#efefef;padding:0 .38824rem;position:relative;display:flex;flex-direction:column;justify-content:center}.project-item .project-contents .project-title{font-size:.25882rem;font-weight:700;line-height:.27059rem}.project-item .project-contents .project-title a{color:#238dfb}.project-item .project-contents .project-desc{margin-top:.15294rem;font-size:.22353rem;font-weight:400;color:#717171;line-height:.29412rem}.saerch-fliter-container{height:1.17647rem;border-bottom:.04706rem dashed #e5e5e5;display:flex}.saerch-fliter-container .search-fliter-title{font-size:.21176rem;font-weight:400;color:#434343;width:1.50588rem;margin-right:.58824rem}.saerch-fliter-container .search-fliter-options{flex:1;display:flex;flex-wrap:wrap}.saerch-fliter-container .search-fliter-options .fliter-option{font-size:.18824rem;font-weight:400;color:#959595;padding:0 .35294rem 0 0;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.saerch-fliter-container .search-fliter-options .fliter-option.active{color:#0064c2}.mobile .saerch-fliter-container{height:2.82353rem;margin-top:.35294rem}.dev-layout{flex-wrap:wrap;justify-content:space-between;margin-bottom:.70588rem;flex-direction:column}.dev-container,.dev-layout{display:flex;width:100%}.mobile .dev-container{flex-direction:column;min-height:60vh}.dev-info-container{margin:.70588rem .23529rem;display:flex;color:#5f5d5d;width:3.52941rem;overflow:hidden;flex-direction:column}.dev-info-container .dev-contents{display:flex;flex-direction:column;align-items:center;text-align:center}.dev-info-container .dev-title{font-size:.47059rem;padding:.35294rem}.dev-info-container .dev-desc{font-size:.18824rem;padding:.35294rem;line-height:.28235rem;font-weight:300;height:1.17647rem}.dev-info-container .dev-button{width:1.64706rem;height:.47059rem;background:#0064c2;border-radius:.05882rem;color:#fff;text-align:center}.dev-info-container .dev-banner{padding:.05882rem;overflow:hidden;border-radius:.11765rem}.dev-info-container .dev-banner img{box-shadow:0 0 .23529rem 0 #efefef;background-size:cover;width:5.29412rem;transition:all .25s ease;border-radius:.11765rem}.dev-info-container .dev-banner img:hover{transform:scale(1.1)}.mobile .dev-info-container{width:100%;flex-direction:row}@-webkit-keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@-webkit-keyframes fade-in{0%{opacity:0}to{opacity:1}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}@-webkit-keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}@keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}.float-icon-container{position:fixed;right:23PX;bottom:80PX;z-index:6;height:120PX;width:50PX}.float-icon-container .totop-icon{position:absolute;top:0;left:0}.float-icon-container .menu-icon{position:absolute;top:70PX;left:0}.float-icon-container .menu-icon.active,.float-icon-container .menu-icon.active:hover{background-color:#2f495e}.float-icon-container .menu-icon,.float-icon-container .totop-icon{width:50PX;height:50PX;display:flex;align-items:center;justify-content:center;border-radius:50%;background-color:#0870d1;box-shadow:0 0 .35294rem -.02353rem rgba(19,41,75,.14),0 .14118rem .15294rem -.02353rem rgba(19,41,75,.13),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.13),0 .02353rem .02353rem -.02353rem rgba(19,41,75,.12);cursor:pointer;z-index:200}.float-icon-container .menu-icon svg,.float-icon-container .totop-icon svg{width:50PX;height:50PX}.float-icon-container .menu-icon svg path,.float-icon-container .totop-icon svg path{fill:#fefefe}.float-icon-container .menu-icon:hover,.float-icon-container .totop-icon:hover{background-color:#058ce6}.markdown .hljs{color:#263445;background:0 0}.markdown .hljs-comment,.markdown .hljs-quote{color:#687789;font-style:normal}.markdown .hljs-addition,.markdown .hljs-keyword,.markdown .hljs-selector-tag{color:#b4233f;font-weight:500}.markdown .hljs-link,.markdown .hljs-literal,.markdown .hljs-number,.markdown .hljs-regexp{color:#1769aa}.markdown .hljs-doctag,.markdown .hljs-meta .hljs-meta-string,.markdown .hljs-string{color:#16705a}.markdown .hljs-name,.markdown .hljs-section,.markdown .hljs-selector-class,.markdown .hljs-selector-id,.markdown .hljs-title{color:#6f52a2}.markdown .hljs-attr,.markdown .hljs-attribute,.markdown .hljs-template-variable,.markdown .hljs-variable{color:#8a5a00}.markdown .hljs-built_in,.markdown .hljs-builtin-name,.markdown .hljs-class .hljs-title,.markdown .hljs-type{color:#9a4d16}.markdown .hljs-bullet,.markdown .hljs-meta,.markdown .hljs-meta .hljs-keyword,.markdown .hljs-selector-attr,.markdown .hljs-selector-pseudo,.markdown .hljs-subst,.markdown .hljs-symbol{color:#526579}.markdown .hljs-deletion{color:#b4233f}.markdown .hljs-formula{background:#eaf1f7}.markdown .hljs-emphasis{font-style:italic}.markdown .hljs-strong{font-weight:600}/*!
- * Viewer.js v1.11.6
- * https://fengyuanchen.github.io/viewerjs
- *
- * Copyright 2015-present Chen Fengyuan
- * Released under the MIT license
- *
- * Date: 2023-09-17T03:16:35.830Z
- */.viewer-close:before,.viewer-flip-horizontal:before,.viewer-flip-vertical:before,.viewer-fullscreen-exit:before,.viewer-fullscreen:before,.viewer-next:before,.viewer-one-to-one:before,.viewer-play:before,.viewer-prev:before,.viewer-reset:before,.viewer-rotate-left:before,.viewer-rotate-right:before,.viewer-zoom-in:before,.viewer-zoom-out:before{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAARgAAAAUCAYAAABWOyJDAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAALEgAACxIB0t1+/AAAABx0RVh0U29mdHdhcmUAQWRvYmUgRmlyZXdvcmtzIENTNui8sowAAAQPSURBVHic7Zs/iFxVFMa/0U2UaJGksUgnIVhYxVhpjDbZCBmLdAYECxsRFBTUamcXUiSNncgKQbSxsxH8gzAP3FU2jY0kKKJNiiiIghFlccnP4p3nPCdv3p9778vsLOcHB2bfveeb7955c3jvvNkBIMdxnD64a94GHMfZu3iBcRynN7zAOI7TG15gHCeeNUkr8zaxG2lbYDYsdgMbktBsP03jdQwljSXdtBhLOmtjowC9Mg9L+knSlcD8TNKpSA9lBpK2JF2VdDSR5n5J64m0qli399hNFMUlpshQii5jbXTbHGviB0nLNeNDSd9VO4A2UdB2fp+x0eCnaXxWXGA2X0au/3HgN9P4LFCjIANOJdrLr0zzZ+BEpNYDwKbpnQMeAw4m8HjQtM6Z9qa917zPQwFr3M5KgA6J5rTJCdFZJj9/lyvGhsDvwFNVuV2MhhjrK6b9bFiE+j1r87eBl4HDwCF7/U/k+ofAX5b/EXBv5JoLMuILzf3Ap6Z3EzgdqHMCuF7hcQf4HDgeoHnccncqdK/TvSDWffFXI/exICY/xZyqc6XLWF1UFZna4gJ7q8BsRvgd2/xXpo6P+D9dfT7PpECtA3cnWPM0GXGFZh/wgWltA+cDNC7X+AP4GzjZQe+k5dRxuYPeiuXU7e1qwLpDz7dFjXKRaSwuMLvAlG8zZlG+YmiK1HoFqT7wP2z+4Q45TfEGcMt01xLoNZEBTwRqD4BLpnMLeC1A41UmVxsXgXeBayV/Wx20rpTyrpnWRft7p6O/FdqzGrDukPNtkaMoMo3FBdBSQMOnYBCReyf05s126fU9ytfX98+mY54Kxnp7S9K3kj6U9KYdG0h6UdLbkh7poFXMfUnSOyVvL0h6VtIXHbS6nOP+s/Zm9mvyXW1uuC9ohZ72E9uDmXWLJOB1GxsH+DxPftsB8B6wlGDN02TAkxG6+4D3TWsbeC5CS8CDFce+AW500LhhOW2020TRjK3b21HEmgti9m0RonxbdMZeVzV+/4tF3cBpP7E9mKHNL5q8h5g0eYsCMQz0epq8gQrwMXAgcs0FGXGFRcB9wCemF9PkbYqM/Bas7fxLwNeJPdTdpo4itQti8lPMqTpXuozVRVXPpbHI3KkNTB1NfkL81j2mvhDp91HgV9MKuRIqrykj3WPq4rHyL+axj8/qGPmTqi6F9YDlHOvJU6oYcTsh/TYSzWmTE6JT19CtLTJt32D6CmHe0eQn1O8z5AXgT4sx4Vcu0/EQecMydB8z0hUWkTd2t4CrwNEePqMBcAR4mrBbwyXLPWJa8zrXmmLEhNBmfpkuY2102xxrih+pb+ieAb6vGhuA97UcJ5KR8gZ77K+99xxeYBzH6Q3/Z0fHcXrDC4zjOL3hBcZxnN74F+zlvXFWXF9PAAAAAElFTkSuQmCC);background-repeat:no-repeat;background-size:280px;color:transparent;display:block;font-size:0;height:20px;line-height:0;width:20px}.viewer-zoom-in:before{background-position:0 0;content:"Zoom In"}.viewer-zoom-out:before{background-position:-20px 0;content:"Zoom Out"}.viewer-one-to-one:before{background-position:-40px 0;content:"One to One"}.viewer-reset:before{background-position:-60px 0;content:"Reset"}.viewer-prev:before{background-position:-80px 0;content:"Previous"}.viewer-play:before{background-position:-100px 0;content:"Play"}.viewer-next:before{background-position:-120px 0;content:"Next"}.viewer-rotate-left:before{background-position:-140px 0;content:"Rotate Left"}.viewer-rotate-right:before{background-position:-160px 0;content:"Rotate Right"}.viewer-flip-horizontal:before{background-position:-180px 0;content:"Flip Horizontal"}.viewer-flip-vertical:before{background-position:-200px 0;content:"Flip Vertical"}.viewer-fullscreen:before{background-position:-220px 0;content:"Enter Full Screen"}.viewer-fullscreen-exit:before{background-position:-240px 0;content:"Exit Full Screen"}.viewer-close:before{background-position:-260px 0;content:"Close"}.viewer-container{bottom:0;direction:ltr;font-size:0;left:0;line-height:0;overflow:hidden;position:absolute;right:0;-webkit-tap-highlight-color:transparent;top:0;touch-action:none;-webkit-touch-callout:none;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.viewer-container ::-moz-selection,.viewer-container::-moz-selection{background-color:transparent}.viewer-container ::selection,.viewer-container::selection{background-color:transparent}.viewer-container:focus{outline:0}.viewer-container img{display:block;height:auto;max-height:none!important;max-width:none!important;min-height:0!important;min-width:0!important;width:100%}.viewer-canvas{bottom:0;left:0;overflow:hidden;position:absolute;right:0;top:0}.viewer-canvas>img{height:auto;margin:15px auto;max-width:90%!important;width:auto}.viewer-footer{bottom:0;left:0;overflow:hidden;position:absolute;right:0;text-align:center}.viewer-navbar{background-color:rgba(0,0,0,.5);overflow:hidden}.viewer-list{box-sizing:content-box;height:50px;margin:0;overflow:hidden;padding:1px 0}.viewer-list>li{color:transparent;cursor:pointer;float:left;font-size:0;height:50px;line-height:0;opacity:.5;overflow:hidden;transition:opacity .15s;width:30px}.viewer-list>li:focus,.viewer-list>li:hover{opacity:.75}.viewer-list>li:focus{outline:0}.viewer-list>li+li{margin-left:1px}.viewer-list>.viewer-loading{position:relative}.viewer-list>.viewer-loading:after{border-width:2px;height:20px;margin-left:-10px;margin-top:-10px;width:20px}.viewer-list>.viewer-active,.viewer-list>.viewer-active:focus,.viewer-list>.viewer-active:hover{opacity:1}.viewer-player{background-color:#000;bottom:0;cursor:none;display:none;right:0;z-index:1}.viewer-player,.viewer-player>img{left:0;position:absolute;top:0}.viewer-toolbar>ul{display:inline-block;margin:0 auto 5px;overflow:hidden;padding:6px 3px}.viewer-toolbar>ul>li{background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;float:left;height:24px;overflow:hidden;transition:background-color .15s;width:24px}.viewer-toolbar>ul>li:focus,.viewer-toolbar>ul>li:hover{background-color:rgba(0,0,0,.8)}.viewer-toolbar>ul>li:focus{box-shadow:0 0 3px #fff;outline:0;position:relative;z-index:1}.viewer-toolbar>ul>li:before{margin:2px}.viewer-toolbar>ul>li+li{margin-left:1px}.viewer-toolbar>ul>.viewer-small{height:18px;margin-bottom:3px;margin-top:3px;width:18px}.viewer-toolbar>ul>.viewer-small:before{margin:-1px}.viewer-toolbar>ul>.viewer-large{height:30px;margin-bottom:-3px;margin-top:-3px;width:30px}.viewer-toolbar>ul>.viewer-large:before{margin:5px}.viewer-tooltip{background-color:rgba(0,0,0,.8);border-radius:10px;color:#fff;display:none;font-size:12px;height:20px;left:50%;line-height:20px;margin-left:-25px;margin-top:-10px;position:absolute;text-align:center;top:50%;width:50px}.viewer-title{color:#ccc;display:inline-block;font-size:12px;line-height:1.2;margin:5px 5%;max-width:90%;min-height:14px;opacity:.8;overflow:hidden;text-overflow:ellipsis;transition:opacity .15s;white-space:nowrap}.viewer-title:hover{opacity:1}.viewer-button{-webkit-app-region:no-drag;background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;height:80px;overflow:hidden;position:absolute;right:-40px;top:-40px;transition:background-color .15s;width:80px}.viewer-button:focus,.viewer-button:hover{background-color:rgba(0,0,0,.8)}.viewer-button:focus{box-shadow:0 0 3px #fff;outline:0}.viewer-button:before{bottom:15px;left:15px;position:absolute}.viewer-fixed{position:fixed}.viewer-open{overflow:hidden}.viewer-show{display:block}.viewer-hide{display:none}.viewer-backdrop{background-color:rgba(0,0,0,.5)}.viewer-invisible{visibility:hidden}.viewer-move{cursor:move;cursor:-webkit-grab;cursor:grab}.viewer-fade{opacity:0}.viewer-in{opacity:1}.viewer-transition{transition:all .3s}@-webkit-keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}.viewer-loading:after{-webkit-animation:viewer-spinner 1s linear infinite;animation:viewer-spinner 1s linear infinite;border:4px solid hsla(0,0%,100%,.1);border-left-color:hsla(0,0%,100%,.5);border-radius:50%;content:"";display:inline-block;height:40px;left:50%;margin-left:-20px;margin-top:-20px;position:absolute;top:50%;width:40px;z-index:1}@media (max-width:767px){.viewer-hide-xs-down{display:none}}@media (max-width:991px){.viewer-hide-sm-down{display:none}}@media (max-width:1199px){.viewer-hide-md-down{display:none}}.nuxt-progress{position:fixed;top:0;left:0;right:0;height:.02353rem;width:0;opacity:1;transition:width .1s,opacity .4s;background-color:#000;z-index:999999}.nuxt-progress.nuxt-progress-notransition{transition:none}.nuxt-progress-failed{background-color:red}.side-bar{width:2.47059rem;position:sticky;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.side-bar .side-bar-title{height:.82353rem;width:2.47059rem;background-image:url(/assets/sidebar-title.jpg);background-size:cover}.side-bar .side-bar-title p{height:.21176rem;font-size:.28235rem;font-weight:700;color:#fff;line-height:.82353rem;text-align:center}.side-bar .side-bar-contents{cursor:pointer;border-bottom:.02353rem solid #e5e5e5;border-left:.02353rem solid #e5e5e5;border-right:.02353rem solid #e5e5e5}.side-bar .side-bar-contents .side-bar-collapse{position:relative;height:.50588rem;overflow:hidden;transition:all .2s ease;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.side-bar .side-bar-contents .side-bar-collapse .collapse-title{font-size:.18824rem;font-weight:400;color:#434343;line-height:.50588rem;padding-left:.24706rem;border-top:.01176rem solid #edf1f4;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.side-bar .side-bar-contents .side-bar-collapse .collapse-title.active{color:#409eff}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn{position:absolute;height:.11765rem;width:.11765rem;box-shadow:.02353rem -.02353rem 0 #82a5d7;background-color:#fff;top:.2rem;right:.18824rem;transform:rotate(45deg);transition:all .25s ease}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn.collapse-btn-active{transform:translate(.04706rem,-.04706rem) rotate(135deg)}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents{border-bottom:.01176rem solid #edf1f4}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item{padding-left:.38824rem;line-height:.44706rem;color:#838383;font-size:.16471rem}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active{color:#409eff;background-color:#f6f7f8;position:relative}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active:after{content:" ";width:.04706rem;height:.04706rem;background:#82a5d7;border-radius:50%;position:absolute;top:50%;left:.17647rem;transform:translateY(-50%)}.page-header-container{margin-bottom:.35294rem;width:100%}.page-header-container .page-header-content{display:flex;align-content:center;position:relative}.page-header-container .page-header-content .page-header-arrow-icon{width:.28235rem;height:.32941rem;padding-top:.02353rem;color:#2f495e;font-size:.23529rem;transition:all .2s ease}.page-header-container .page-header-content .header-arrow-container{width:.17647rem;height:.17647rem;background-image:url(/assets/arrow3.png);background-size:cover}.page-header-container .page-header-content .page-header-arrow-icon:hover{color:#007bff}.page-header-container .page-header-content .page-header-item{color:#858585;font-size:.18824rem;font-weight:500;display:flex;height:.35294rem;line-height:.35294rem;cursor:pointer;align-items:center}.page-header-container .page-header-content .page-header-item .page-header-tag{margin:0 .09412rem;transition:all .2s ease}.page-header-container .page-header-content .page-header-item .page-header-tag.active{color:#2f495e}.page-header-container .page-header-content .page-header-item .page-header-tag:hover{color:#007bff}.mobile .page-header-container{margin-top:.35294rem}.search-box{display:flex;grid-gap:.11765rem;gap:.11765rem;margin-bottom:.28235rem;position:relative;align-items:center}.search-box input{flex:1;min-width:7.05882rem;height:.51765rem;background:#edf1f4;border-radius:.09412rem;border:.01176rem solid #d5dee8;padding:0 .18824rem;font-size:.17647rem;color:#253443;outline:0;z-index:3;transition:border-color .2s ease,box-shadow .2s ease}.search-box input:focus{border-color:#0064c2;box-shadow:0 0 0 .03529rem rgba(0,100,194,.12157)}.search-box .search-btn{width:1.55294rem;height:.51765rem;background:#0064c2;border-radius:.09412rem;border:none;cursor:pointer;transition:background-color .2s ease}.search-box .search-btn:hover{background:#0a5aaa}.search-box .search-btn p{margin:0;line-height:.51765rem;font-size:.18824rem;font-weight:700;color:#fff}.search-box .search-cover{position:fixed;top:0;left:0;right:0;bottom:0;z-index:2;background-color:rgba(25,25,25,.1098);-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem)}.search-result-container{overflow:hidden}.search-result-container::-webkit-scrollbar{width:.14118rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.search-result-container .el-tabs__item{display:table-cell;font-size:.21176rem;font-weight:600}.search-result-container .el-tabs__active-bar{height:.04706rem}.search-result-container{width:100%;min-height:4.47059rem;max-height:7.05882rem;overflow-y:auto;background-color:#fff;position:absolute;top:.63529rem;border:.01176rem solid #e2e8f0;border-radius:.11765rem;box-shadow:0 .11765rem .17647rem -.03529rem rgba(0,0,0,.10196),0 .04706rem .07059rem -.02353rem rgba(0,0,0,.05098);transition:all .25s ease;color:#2f495e;z-index:3;padding:.14118rem;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.search-result-container .search-title{height:.70588rem;font-size:.29412rem;padding:.17647rem;border-bottom:.01176rem solid #d9d9d9}.search-result-container .search-result-contents{display:flex;align-items:flex-start;grid-gap:.11765rem;gap:.11765rem;padding:.14118rem;border-bottom:.01176rem solid #edf2f7;position:relative}.search-result-container .search-result-contents svg{display:inline;font-size:.23529rem;color:#409eff;padding-right:.11765rem}.search-result-container .search-result-contents:hover{background-color:#f3f8fd}.search-result-container .search-result-content{flex:1;display:flex;flex-direction:column;justify-content:center;position:relative;transition:all .25s ease}.search-result-container .search-result-name{font-size:.18824rem;text-align:left;font-weight:700;color:#409eff;line-height:1.4}.search-result-container .search-result-sku{font-size:.16471rem;line-height:1.6;color:#5b5b5b;margin-top:.04706rem}.search-result-container .search-result-key{font-size:.18824rem;font-weight:700;color:#2f495e;margin-top:.04706rem}.search-result-container .search-result-key .search-result-highlight{color:#409eff}.search-result-container .search-result-key .search-result-key-tag{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#5b5b5b;padding:.02353rem .11765rem;border:.01176rem solid #5b5b5b;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container .search-result-key .search-result-key-tag.active{color:#409eff;border:.01176rem solid #409eff}.search-result-container .search-result-image{width:1.31765rem;height:1.31765rem;margin:0 .21176rem 0 .04706rem}.search-result-container .search-result-eol-tag{position:absolute;width:.41176rem;height:.41176rem;border-radius:50%;top:5%;left:.35294rem;background-color:#2f495e;color:#fff;font-size:.15294rem;font-weight:700;line-height:.41176rem;text-align:center}.search-result-container .search-result-recommand-box{margin-top:.14118rem}.search-result-container .search-result-recommand-box .search-result-recommand-item{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#409eff;padding:.04706rem .11765rem;border:.01176rem solid #409eff;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container:before{display:block;position:absolute;content:"";width:.16471rem;height:.16471rem;background:#fff;z-index:1000;top:-.08235rem;left:calc(50% - .08235rem);border-top:.01176rem solid #d9d9d9;border-right:.01176rem solid #d9d9d9;transform:rotate(-45deg);border-radius:.02353rem}.mobile .search-box{margin-bottom:.09412rem;width:100%;grid-gap:.09412rem;gap:.09412rem}.mobile .search-box input{height:.65882rem;font-size:.2rem}.mobile .search-box .search-btn{width:2.11765rem;height:.65882rem;background:#0064c2;border-radius:.09412rem}.mobile .search-box .search-btn p{margin:0;line-height:.65882rem;font-size:.21176rem;font-weight:700;color:#fff}.mobile .search-result-container{top:.75294rem}.search-result-container .tabs{display:flex;grid-gap:.07059rem;gap:.07059rem;width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .14118rem;padding:.09412rem .14118rem;border-radius:0;background:hsla(0,0%,100%,.9);border:0;border-bottom:.01176rem solid #e6edf5;-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem);position:sticky;top:-.14118rem;z-index:6}.search-result-container .tabs:after{content:"";position:absolute;left:0;right:0;top:0;bottom:0;background:0 0;z-index:-1}.search-result-container .tabs button{min-width:1.27059rem;padding:.10588rem .18824rem;border-radius:.11765rem;font-size:.16471rem;font-weight:600;color:#516578;background:hsla(0,0%,100%,.6);border:.01176rem solid #d7e3ef;line-height:1.2;overflow:hidden;transition:color .2s ease,background-color .2s ease,box-shadow .2s ease}.search-result-container .tabs button:first-child,.search-result-container .tabs button:last-child{border-radius:.11765rem}.search-result-container .tabs button:hover{color:#2f4f6f;background:#f8fbff;border-color:#cddded}.search-result-container .tabs button.active{color:#0f4f8e;background:#fff;border:.01176rem solid #c8d9eb;border-radius:.11765rem;box-shadow:0 .02353rem .09412rem rgba(0,100,194,.16078)}.search-result-container .tab-content{padding:.11765rem .09412rem .09412rem;background:0 0}.search-result-container .search-result-contents{border-radius:.09412rem;transition:background-color .2s ease,box-shadow .2s ease}.search-result-container .search-result-contents:hover{box-shadow:inset 0 0 0 .01176rem #dbe9f8}.search-result-contents-list{padding-bottom:.82353rem}.search-result-view-all-wrap{position:sticky;bottom:0;z-index:4;display:flex;justify-content:center;padding:.11765rem .09412rem .07059rem;background:linear-gradient(0deg,#fff 70%,hsla(0,0%,100%,0))}.search-result-view-all-btn{display:inline-block;min-width:2.82353rem;text-align:center;padding:.12941rem .21176rem;border-radius:.28235rem;background:#0064c2;color:#fff;font-size:.17647rem;font-weight:700;text-decoration:none;box-shadow:0 .04706rem .14118rem rgba(0,100,194,.25);transition:background-color .2s ease}.search-result-view-all-btn:hover{background:#0a5aaa}.mobile .search-result-container .tabs{width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .11765rem;padding:.09412rem .11765rem}.mobile .search-result-container .tabs button{flex:1;min-width:0;padding:.14118rem .11765rem;font-size:.17647rem}.mobile .search-result-container .tab-content{padding:.09412rem .04706rem .07059rem}.search-result-container.search-result-embedded{position:relative;top:auto;max-height:none;min-height:0;padding:0;box-shadow:none;-webkit-animation:none;animation:none}.search-result-container.search-result-embedded:before{display:none}.search-result-loading{padding:.09412rem .04706rem;display:flex;flex-direction:column}.search-result-loading-header{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;color:#516578;font-size:.16471rem;margin:0 0 .11765rem}.search-result-loading-text{min-width:0;font-size:.16471rem;font-weight:400;line-height:.23529rem}.search-result-loading-dot{width:.09412rem;height:.09412rem;border-radius:50%;background:#409eff;-webkit-animation:search-loading-pulse 1s ease-in-out infinite;animation:search-loading-pulse 1s ease-in-out infinite}.search-result-loading-list{display:flex;flex-direction:column;grid-gap:.11765rem;gap:.11765rem}.search-result-loading-item{padding:.14118rem;border-radius:.09412rem;border:.01176rem solid #edf2f7;background:#fbfdff}.search-result-loading-line{height:.11765rem;border-radius:11.75294rem;margin-bottom:.09412rem;background:linear-gradient(90deg,#e9f0f7 20%,#f5f9fd 45%,#e9f0f7 70%);background-size:2.82353rem 100%;-webkit-animation:search-loading-shimmer 1.1s linear infinite;animation:search-loading-shimmer 1.1s linear infinite}.search-result-loading-line.is-title{width:52%;height:.14118rem}.search-result-loading-line.is-short{width:36%;margin-bottom:0}@-webkit-keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@-webkit-keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}@keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}.search-result-loading-text[data-v-2b770079]{min-width:0;font-size:.16471rem!important;font-weight:400;line-height:.23529rem}.tab-panel{border:.01176rem solid #e5e5e5;padding:.09412rem;border-radius:.09412rem}.tabs{display:flex;grid-gap:.09412rem;gap:.09412rem;margin-bottom:.18824rem}.tabs button{padding:.11765rem .21176rem;border:none;border-bottom:.04706rem solid transparent;background:#f9f9f9;cursor:pointer;transition:.2s}.tabs button.active{border-color:#007bff;color:#007bff}.tab-content{padding:.18824rem;background:#fefefe;border-radius:.09412rem}.search-result-container .tab-panel{border:0}.carousel-container[data-v-6e07f87d]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-6e07f87d]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-6e07f87d]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-6e07f87d]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-6e07f87d]{flex-shrink:0;width:33.333%;text-align:center;cursor:pointer}.preview-image img[data-v-6e07f87d]{max-width:100%;height:auto;margin:0}.arrow[data-v-6e07f87d]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-6e07f87d]{left:0;transform:rotateY(180deg)}.arrow.right[data-v-6e07f87d]{right:0}.carousel-thumbnails[data-v-6e07f87d]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-6e07f87d]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-6e07f87d]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-6e07f87d]{width:100%;margin:0;height:auto}.clickable-area[data-v-6e07f87d]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-6e07f87d]{left:0}.clickable-area.right[data-v-6e07f87d]{right:0}.carousel-container[data-v-7d51a79c]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-7d51a79c]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-7d51a79c]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-7d51a79c]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-7d51a79c]{flex-shrink:0;width:100%;text-align:center;cursor:pointer}.preview-image img[data-v-7d51a79c]{width:100%;height:auto;margin:0}.arrow[data-v-7d51a79c]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-7d51a79c]{left:0;transform:translateY(-50%) rotateY(180deg)}.arrow.right[data-v-7d51a79c]{right:0;transform:translateY(-50%)}.carousel-thumbnails[data-v-7d51a79c]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-7d51a79c]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-7d51a79c]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-7d51a79c]{width:100%;margin:0;height:auto}.clickable-area[data-v-7d51a79c]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-7d51a79c]{left:0}.clickable-area.right[data-v-7d51a79c]{right:0}.corner-marker[data-v-7d51a79c]{position:absolute;bottom:.11765rem;left:.11765rem;background-color:rgba(0,0,0,.5);color:#fff;padding:.05882rem .11765rem;border-radius:.05882rem;z-index:2}.video-gallery-island[data-v-5e05839f]{min-width:0;width:100%}.page-tools[data-v-39baf185]{width:2.35294rem;margin-bottom:.16471rem;border:.01176rem solid #dfeaf5;border-radius:.11765rem;background:#f8fbfe;box-shadow:0 .07059rem .21176rem rgba(19,41,75,.08);overflow:visible}.page-tools-title[data-v-39baf185]{height:.4rem;line-height:.4rem;padding:0 .14118rem;border-bottom:.01176rem solid #e5eef7;color:#2f495e;font-size:.15294rem;font-weight:700}.page-tools-actions[data-v-39baf185]{display:flex;flex-direction:column;grid-gap:.09412rem;gap:.09412rem;padding:.11765rem;align-items:stretch}.page-tools-action[data-v-39baf185]{display:inline-flex;align-items:center;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;height:.43529rem;width:100%;padding:0 .11765rem;border:.01176rem solid #d6e5f3;border-radius:.08235rem;background:#fff;color:#238dfb;font-size:.15294rem;font-weight:700;transition:background-color .2s ease,border-color .2s ease,transform .2s ease}.page-tools-action .page-tools-icon[data-v-39baf185]{width:.21176rem;height:.21176rem;flex:0 0 auto;fill:currentColor;display:block}.page-tools-action[data-v-39baf185]:after{content:"";width:.08235rem;height:.08235rem;margin-left:auto;border-top:.02353rem solid;border-right:.02353rem solid;transform:rotate(45deg);opacity:.45}.page-tools-action[data-v-39baf185]:hover{background:#eaf4ff;border-color:#b9d8f4;transform:translateY(-.01176rem)}.page-tools.mobile[data-v-39baf185]{width:auto;margin:.09412rem 0 .18824rem;border:0;background:0 0;box-shadow:none}.page-tools.mobile .page-tools-actions[data-v-39baf185]{flex-direction:row;padding:0}.page-tools.mobile .page-tools-action[data-v-39baf185]{width:.63529rem;min-width:.63529rem;height:.42353rem;padding:0;background:#edf6ff;border-color:#b7d8f5;justify-content:center}.page-tools.mobile .page-tools-action[data-v-39baf185]:after{display:none}.markdown-action-menu[data-v-5d6a4f8a]{position:relative;display:flex;justify-content:flex-end;margin:-.14118rem 0 .21176rem;z-index:20}.markdown-action-trigger[data-v-5d6a4f8a]{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;height:.47059rem;padding:0 .16471rem;border:.01176rem solid #b9cfe5;border-radius:.07059rem;background:linear-gradient(135deg,#0064c2,#238dfb);color:#fff;font-size:.16471rem;font-weight:700;cursor:pointer;transition:background-color .2s ease,border-color .2s ease}.markdown-action-trigger svg[data-v-5d6a4f8a]{width:.18824rem;height:.18824rem}.markdown-action-trigger[data-v-5d6a4f8a]:hover{background:linear-gradient(135deg,#0059ad,#167ce8);border-color:#82b6ec}.markdown-action-dropdown[data-v-5d6a4f8a]{position:fixed;z-index:2147483000;width:3.52941rem;overflow:hidden;border:.01176rem solid #c8dced;border-radius:.11765rem;background:#fff;box-shadow:0 .18824rem .44706rem rgba(18,62,111,.16),0 .02353rem .09412rem rgba(24,84,140,.08)}.markdown-action-item[data-v-5d6a4f8a]{display:flex;width:100%;grid-gap:.16471rem;gap:.16471rem;align-items:flex-start;padding:.17647rem .18824rem;border:0;border-bottom:.01176rem solid #e6edf5;background:0 0;color:#2f495e;text-align:left;cursor:pointer;transition:background-color .15s ease}.markdown-action-item svg[data-v-5d6a4f8a]{flex:0 0 auto;width:.2rem;height:.2rem;margin-top:.02353rem;color:#238dfb}.markdown-action-item strong[data-v-5d6a4f8a]{display:block;font-size:.17647rem;line-height:.23529rem}.markdown-action-item small[data-v-5d6a4f8a]{display:block;margin-top:.02353rem;color:#6f8193;font-size:.15294rem;line-height:.21176rem}.markdown-action-item[data-v-5d6a4f8a]:last-child{border-bottom:0}.markdown-action-item[data-v-5d6a4f8a]:hover{background:#f3f8fe}.markdown-action-menu.placement-sidebar[data-v-5d6a4f8a]{justify-content:center;margin:.14118rem 0 0}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;justify-content:center;background:#edf6ff;border-color:#c7dff7;color:#0064c2}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#dfefff;border-color:#9fc7ef}.markdown-action-menu.placement-sidebar .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.05882rem}.markdown-action-menu.placement-anchor[data-v-5d6a4f8a]{justify-content:flex-start;margin:0 0 .11765rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:center;padding:0 .11765rem;background:#f5f9fd;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-anchor .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.placement-toolbox[data-v-5d6a4f8a]{width:100%;flex:1;justify-content:flex-start;margin:0}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;padding:0 .11765rem;background:#fff;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]{flex:0 0 auto}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{width:.16471rem;height:.16471rem;margin-left:auto;opacity:.55}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-toolbox .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.compact[data-v-5d6a4f8a]{justify-content:flex-start;margin:.09412rem 0 .18824rem}.markdown-action-menu.compact .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center;padding:0;background:#edf6ff;border-color:#b7d8f5;color:#0064c2}.markdown-action-menu.compact .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.52941rem;max-width:calc(100vw - .37647rem)}.markdown-action-menu.compact.placement-toolbox[data-v-5d6a4f8a]{flex:0 0 auto;margin:0}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{margin-left:0}</style><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer_Mesh_Kit/state.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer_Mesh_Kit/payload.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/manifest.js" as="script">
-  </head>
-  <body>
-    <div data-server-rendered="true" id="__nuxt"><!----><div id="__layout"><div class="device-hydration-sensitive"><div class="pc"><header langdata="[object Object]" lang="en"><!----> <!----> <div class="header-container"><a href="https://m5stack.com/" class="logo"><img src="/assets/m5logo.svg" alt="M5Stack"></a> <div class="header-nav"><div class="header-nav-ul"><!----> <li data-id="solution" class="header-nav-item"><a class="header-nav-item-a disabledHover">Solution</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="store" class="header-nav-item"><a href="https://shop.m5stack.com" class="header-nav-item-a">Store</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="software" class="header-nav-item"><a class="header-nav-item-a disabledHover">Software</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="document" class="header-nav-item"><a class="header-nav-item-a disabledHover">Documentation</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="aboutus" class="header-nav-item"><a class="header-nav-item-a disabledHover">About Us</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="contact" class="header-nav-item"><a class="header-nav-item-a disabledHover">Contact</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----></div></div> <div class="language-option-box"><div class="current-language"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 1.32 1.32" fill="currentColor" aria-hidden="true" class="icon"><g><path d="M0.66 0c0.18,0 0.35,0.07 0.47,0.19 0.12,0.12 0.19,0.28 0.19,0.47 0,0.18 -0.07,0.35 -0.19,0.47 -0.12,0.12 -0.28,0.19 -0.47,0.19 -0.18,0 -0.35,-0.07 -0.47,-0.19 -0.12,-0.12 -0.19,-0.28 -0.19,-0.47 0,-0.18 0.07,-0.35 0.19,-0.47 0.12,-0.12 0.28,-0.19 0.47,-0.19zm0.39 0.27c-0.1,-0.1 -0.24,-0.16 -0.39,-0.16 -0.15,0 -0.29,0.06 -0.39,0.16 -0.1,0.1 -0.16,0.24 -0.16,0.39 0,0.15 0.06,0.29 0.16,0.39 0.1,0.1 0.24,0.16 0.39,0.16 0.15,0 0.29,-0.06 0.39,-0.16 0.1,-0.1 0.16,-0.24 0.16,-0.39 0,-0.15 -0.06,-0.29 -0.16,-0.39z"></path> <path d="M0.09 0.51c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.09 0.92c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.62 1.21c0.02,0.02 0.02,0.06 0,0.08 -0.02,0.02 -0.06,0.02 -0.08,0 -0.07,-0.06 -0.13,-0.16 -0.16,-0.27 -0.04,-0.11 -0.06,-0.23 -0.06,-0.36 0,-0.13 0.02,-0.26 0.06,-0.36 0.04,-0.11 0.1,-0.21 0.16,-0.27 0.02,-0.02 0.06,-0.02 0.08,0 0.02,0.02 0.02,0.06 -0,0.08 -0.06,0.05 -0.1,0.13 -0.14,0.23 -0.03,0.09 -0.05,0.21 -0.05,0.33 0,0.12 0.02,0.23 0.05,0.33 0.03,0.1 0.08,0.18 0.14,0.23z"></path> <path d="M0.78 1.29c-0.02,0.02 -0.06,0.02 -0.08,-0 -0.02,-0.02 -0.02,-0.06 0,-0.08 0.06,-0.05 0.1,-0.13 0.14,-0.23 0.03,-0.09 0.05,-0.21 0.05,-0.33 0,-0.12 -0.02,-0.23 -0.05,-0.33 -0.03,-0.1 -0.08,-0.18 -0.14,-0.23 -0.02,-0.02 -0.02,-0.06 -0,-0.08 0.02,-0.02 0.06,-0.02 0.08,-0 0.07,0.06 0.13,0.16 0.16,0.27 0.04,0.11 0.06,0.23 0.06,0.36 0,0.13 -0.02,0.26 -0.06,0.36 -0.04,0.11 -0.1,0.21 -0.16,0.27z"></path></g></svg> <div>English</div> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg></div> <div class="language-dropdown-wrapper"><div class="language-dropdown"><div class="language-item active">English</div> <div class="language-item">简体中文</div> <div class="language-item">日本語</div></div></div></div></div></header> <div class="docs-layouts"><div class="docs-layouts-sidebar"><div class="side-bar"><div class="side-bar-title"><p>CONTENTS</p></div> <div class="side-bar-contents"></div></div></div> <div class="docs-layouts-body"><div class="page-header-container"><!----></div> <!----> <div class="search-box"><div id="search"></div> <input placeholder="Product Name / SKU"> <div class="search-result-container" style="display:none" data-v-2b770079><a class="search-result-contents" data-v-2b770079><div class="search-result-content" data-v-2b770079><div class="search-result-name" data-v-2b770079>No Results Found</div> <div class="search-result-sku" data-v-2b770079>Hot Searches</div> <div class="search-result-key" data-v-2b770079><div class="search-result-recommand-box" data-v-2b770079><div data-key="Camera" class="search-result-recommand-item" data-v-2b770079>
-            Camera
-          </div><div data-key="WiFi" class="search-result-recommand-item" data-v-2b770079>
-            WiFi
-          </div><div data-key="RS485" class="search-result-recommand-item" data-v-2b770079>
-            RS485
-          </div><div data-key="RS232" class="search-result-recommand-item" data-v-2b770079>
-            RS232
-          </div><div data-key="Relay" class="search-result-recommand-item" data-v-2b770079>
-            Relay
-          </div><div data-key="LoRaWAN" class="search-result-recommand-item" data-v-2b770079>
-            LoRaWAN
-          </div><div data-key="GPS" class="search-result-recommand-item" data-v-2b770079>
-            GPS
-          </div><div data-key="NB-IoT" class="search-result-recommand-item" data-v-2b770079>
-            NB-IoT
-          </div><div data-key="LTE" class="search-result-recommand-item" data-v-2b770079>
-            LTE
-          </div><div data-key="GSM" class="search-result-recommand-item" data-v-2b770079>
-            GSM
-          </div><div data-key="Zigbee" class="search-result-recommand-item" data-v-2b770079>
-            Zigbee
-          </div><div data-key="Servo" class="search-result-recommand-item" data-v-2b770079>
-            Servo
-          </div><div data-key="StepMotor" class="search-result-recommand-item" data-v-2b770079>
-            StepMotor
-          </div><div data-key="Ethernet" class="search-result-recommand-item" data-v-2b770079>
-            Ethernet
-          </div><div data-key="E-Paper" class="search-result-recommand-item" data-v-2b770079>
-            E-Paper
-          </div></div></div></div></a> <div class="tab-panel" style="display:none" data-v-2b770079><div class="tabs"><button>
-      Product
-    </button><button>
-      Contents
-    </button></div> <div class="tab-content"><div style="display:none"></div><div style="display:none"></div></div></div></div> <button class="search-btn"><p>Search</p></button> <div class="search-cover" style="display:none"></div></div> <div class="viewer"><div class="markdown"><h1 id="cardputer-mesh-kit" data-id="Cardputer Mesh Kit">Cardputer Mesh Kit</h1> <p><span class="product-sku">SKU:K152</span></p><div class="carousel-container" data-v-6e07f87d><div class="carousel-preview" data-v-6e07f87d><div class="clickable-area left" data-v-6e07f87d></div> <button class="arrow left" data-v-6e07f87d></button> <div class="carousel-images" data-v-6e07f87d><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-6e07f87d><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_01.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_02.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_03.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_04.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_05.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_06.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_07.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_08.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_09.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_10.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_11.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_12.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_13.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-weight.jpg" alt="Preview" data-v-6e07f87d></div></div></div> <button class="arrow right" data-v-6e07f87d></button> <div class="clickable-area right" data-v-6e07f87d></div></div> <div class="carousel-thumbnails" data-v-6e07f87d><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_01.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_02.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_03.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_04.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_05.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_06.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_07.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_08.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_09.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_10.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_11.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_12.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_13.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-weight.jpg" alt="Thumbnail" data-v-6e07f87d></div></div></div> <h2 id="description" data-id="Description">Description</h2> <p><strong>Cardputer Mesh Kit</strong> is a portable communication terminal kit that integrates LoRa Mesh networking with global positioning capabilities. The kit centers around the <strong>Cardputer-Adv</strong> core controller and the <strong>Cap LoRa-1262</strong> communication expansion module.</p><p><strong>Cardputer-Adv</strong> is a card-sized portable programmable controller built on the Stamp-S3A module (based on ESP32-S3FN8). It features a 1.14" LCD screen and a 56-key compact keyboard for convenient on-site information display and command input. A built-in 1750mAh lithium battery ensures extended standalone operation. The device integrates an ES8311 audio codec, MEMS microphone, 1W speaker, and 3.5mm audio jack for voice interaction and audio output. Additional features include a 6-axis IMU BMI270, an infrared emitter, a microSD card slot, an HY2.0-4P Grove interface, and an EXT 2.54-14P expansion bus. The chassis supports magnetic attachment and is compatible with LEGO mounting holes.</p><p><strong>Cap LoRa-1262</strong> serves as the communication expansion module of the kit. It connects to the Cardputer-Adv via the EXT 2.54-14P interface, drawing power and control signals directly from the host — plug-and-play with no additional configuration required. The module is built around the SX1262 LoRa solution, supporting the 868 ~ 923 MHz band with a receive sensitivity of -147 dBm and a transmit power of +22 dBm. An RP-SMA external antenna and RF shielding ensure reliable long-range communication with strong interference immunity. An integrated AT6668 GNSS module with a built-in ceramic antenna supports multi-constellation positioning including GPS, BeiDou, GLONASS, and Galileo. The module also includes an HY2.0-4P interface for connecting external sensors.</p><p><strong>Cardputer Mesh Kit</strong> comes pre-installed with Meshtastic firmware, making it ready to use out of the box — no complex development required to join a LoRa Mesh network. The Cardputer-Adv and Cap LoRa-1262 work seamlessly together for easy configuration and intuitive positioning, making the kit well-suited for outdoor communications, node deployment, location tracking, and industrial inspection.</p><h2 id="tutorial" data-id="Tutorial">Tutorial</h2> <div class="learn"><div class="learn-img"><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-Cardputer-Mesh-Kit-main-pictures_13.jpg" alt="Cardputer Mesh Kit"> <a target="_blank" href="/en/guide/lora/meshtastic/cardputer_mesh_kit">Meshtastic Tutorial</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/guide/lora/meshtastic/cardputer_mesh_kit">Meshtastic Tutorial</a></div> <div class="learn-desc"> This tutorial explains how to use Meshtastic with the Cardputer Mesh Kit. </div></div></div> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/uiflow2/uiflow2.0_banner_01.png" alt="UiFlow2"> <a target="_blank" href="/en/uiflow2/cardputer-adv/program">UiFlow2</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/uiflow2/cardputer-adv/program">UiFlow2</a></div> <div class="learn-desc"> This tutorial introduces how to program and control the Cardputer-Adv using the UiFlow2 graphical programming platform. </div></div></div> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/arduino/arduino_banner_01.png" alt="Arduino IDE"> <a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-desc"> This tutorial introduces how to program and control the Cardputer-Adv using Arduino IDE. </div></div></div><h2 id="features" data-id="Features">Features</h2> <p><strong>Core Controller (Cardputer-Adv)</strong>:</p><ul><li>Stamp-S3A core module (ESP32-S3FN8)</li> <li>56-key keyboard with 160gf comfortable key actuation</li> <li>1.14" LCD screen (240 x 135px)</li> <li>ES8311 audio codec + NS4150B amplifier + 1W speaker + MEMS microphone</li> <li>3.5mm audio output jack</li> <li>6-axis IMU BMI270</li> <li>Infrared emitter</li> <li>microSD card slot</li> <li>Built-in 1750mAh lithium battery</li> <li>HY2.0-4P Grove interface + EXT 2.54-14P expansion bus</li> <li>Magnetic attachment on the back, compatible with LEGO mounting holes</li></ul> <p><strong>Communication Expansion Module (Cap LoRa-1262)</strong>:</p><ul><li><p>LoRa modulation technology + GNSS global positioning system</p></li> <li><p>Operating frequency: 868 ~ 923 MHz</p></li> <li><p>Receive sensitivity as low as -147 dBm, transmit power +22 dBm</p></li> <li><p>External RP-SMA antenna interface with built-in ceramic GPS antenna</p></li> <li><p>Supports GPS / QZSS / BD2 / BD3 / GAL / GLO multi-constellation positioning</p></li> <li><p>HY2.0-4P expansion interface (for external sensor connection)</p></li> <li><p>Development Platform</p><ul><li>Arduino</li> <li>UiFlow2</li> <li>ESP-IDF</li> <li>PlatformIO</li></ul></li></ul> <h2 id="includes" data-id="Includes">Includes</h2> <ul><li>1 x Cardputer-Adv (Green Back Shell Version)</li> <li>1 x Cap LoRa-1262</li> <li>1 x LoRa Rubber Duck Antenna (RP-SMA Connector)</li> <li>2 x M2 * 4mm cap head machine screw</li> <li>1 x Hex Key L-Shape 1.5mm (For M2 Screw)</li> <li>1 x Safety Warning Sticker</li></ul> <h2 id="applications" data-id="Applications">Applications</h2> <ul><li>Remote GPS Tracker</li> <li>Outdoor Mesh Networking</li> <li>Rapid Prototyping and Functional Verification</li> <li>Industrial Control and Automation</li> <li>Smart City / Smart Home</li> <li>In-Vehicle Positioning and Navigation</li> <li>Embedded System Development and Learning</li></ul> <h2 id="specifications" data-id="Specifications">Specifications</h2> <div class="table-container"><table><thead><tr><th>Specification</th> <th>Parameter</th></tr></thead><tbody><tr><td>SoC</td> <td>ESP32-S3FN8 @ Xtensa® 32-bit LX7 dual-core processor, clock frequency 240MHz</td></tr> <tr><td>Flash</td> <td>8MB</td></tr> <tr><td>External Storage</td> <td>microSD</td></tr> <tr><td>Display</td> <td>ST7789V2 @ 1.14", 240 x 135px</td></tr> <tr><td>Keyboard</td> <td>56 keys (4 x 14), 160gf actuation force</td></tr> <tr><td>Expansion Interface</td> <td>HY2.0-4P + EXT 2.54-14P</td></tr> <tr><td>IR</td> <td>1 x Infrared Emitter</td></tr> <tr><td>Audio Codec</td> <td>ES8311</td></tr> <tr><td>Speaker</td> <td>NS4150B amplifier + 8Ω @ 1W speaker</td></tr> <tr><td>Microphone</td> <td>MEMS microphone, SNR: 65 dB</td></tr> <tr><td>IMU</td> <td>BMI270</td></tr> <tr><td>Battery Capacity</td> <td>1750mAh</td></tr> <tr><td>Operating Temperature</td> <td>0 ~ 40°C</td></tr> <tr><td>Operating Current</td> <td>DC 4.2V @ 120.2mA</td></tr> <tr><td>LoRa Module</td> <td>SX1262</td></tr> <tr><td>LoRa Frequency Range</td> <td>868 ~ 923 MHz</td></tr> <tr><td>LoRa Programmable Bit Rate</td> <td>Up to 300kbps</td></tr> <tr><td>LoRa Antenna</td> <td>Size: 108 x 9.3mm, Connector: RP-SMA (female), Gain: 3dBi</td></tr> <tr><td>LoRa Transmit Power</td> <td>+22dBm</td></tr> <tr><td>LoRa Receive Sensitivity</td> <td>-147dBm (low data rate mode)</td></tr> <tr><td>LoRa Operating Current</td> <td>DC 5V @ 163.4mA</td></tr> <tr><td>Supported Modulation</td> <td>FSK / GFSK / MSK / LoRa / OOK</td></tr> <tr><td>GPS Module</td> <td>ATGM336H-6N @ AT6668</td></tr> <tr><td>GPS Communication Interface</td> <td>UART, default 115200bps @ 8N1</td></tr> <tr><td>Supported GNSS Systems</td> <td>GPS / QZSS / BD2 / BD3 / GAL / GLO</td></tr> <tr><td>GPS Channels</td> <td>50 channels</td></tr> <tr><td>GPS Positioning Accuracy</td> <td>&lt;1.5m (CEP50)</td></tr> <tr><td>GPS Update Rate</td> <td>Up to 10Hz</td></tr> <tr><td>GPS Time to First Fix</td> <td>Cold start: 23s, Hot start: 1s</td></tr> <tr><td>Product Size</td> <td>Cardputer-Adv: 84.0 x 54.0 x 19.6mm<br>Cap LoRa-1262: 84.0 x 24.0 x 15.2mm</td></tr> <tr><td>Product Weight</td> <td>77.2g</td></tr> <tr><td>Package Size</td> <td>103.0 x 90.0 x 25.0mm</td></tr> <tr><td>Gross Weight</td> <td>127.2g</td></tr></tbody></table></div><h2 id="learn" data-id="Learn">Learn</h2> <h3 id="cardputer-adv-download-mode" data-id="Cardputer-Adv Download Mode">Cardputer-Adv Download Mode</h3> <p>Set the side power switch on the Cardputer-Adv to <code>OFF</code>. Hold down the <code>G0</code> key, then power on the device. Release the key and the device will enter download mode.</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-operate_02.jpg" width="60%"> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-download-mode-demo.gif" width="60%"> <h3 id="rgb-led-power-supply" data-id="RGB LED Power Supply">RGB LED Power Supply</h3> <div class="warn"><div class="warn-title">RGB LED Power Supply Instructions</div> <div class="warn-content">The device uses <strong>Stamp-S3A</strong> as its main controller. To optimize overall power consumption, Stamp-S3A adds an independent electronic switch for the RGB LED power supply compared with the previous Stamp-S3. Before controlling the RGB LED in software, set GPIO38, which controls this switch, to a high level.</div></div><h3 id="charging-notes" data-id="Charging Notes">Charging Notes</h3> <p>Switch the power switch to <code>ON</code> before charging.</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-operate_04.jpg" width="60%"> <h3 id="assembly-instructions" data-id="Assembly Instructions">Assembly Instructions</h3> <p>The Cap LoRa-1262 connects to the Cardputer-Adv via the EXT 2.54-14P interface:</p><ol><li>Turn the Cardputer-Adv upside down and locate the <strong>EXT 2.54-14P</strong> interface (14-pin female header).</li> <li>Align the corresponding male header pins of the Cap LoRa-1262 with the interface and gently press until fully seated.</li> <li>Screw the LoRa rubber duck antenna into the RP-SMA antenna connector on the Cap LoRa-1262.</li></ol> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/operate.png" width="60%"> <h3 id="device-registration" data-id="Device Registration">Device Registration</h3> <p>The Cardputer Mesh Kit has been officially licensed by Meshtastic. You can register it as an authorized device by following the steps below:</p><ol><li>Ensure that the device has been flashed with the Meshtastic firmware by referring to the <a target="_blank" href="/en/guide/lora/meshtastic/cardputer_mesh_kit">Flashing Tutorial</a> (the factory firmware is already pre-flashed).  </li> <li>Ensure that the Cardputer-Adv is properly connected to the Cap LoRa-1262 expansion.</li> <li>Connect the Cardputer Mesh Kit to your computer via a USB Type-C cable, and visit the <a target="_blank" href="https://meshtastic-reg.m5stack.com/">M5 Meshtastic Device</a> registration page.</li> <li>On the registration webpage, click the <code>Connect Device</code> option, select the device port, then click <code>Connect</code>, and wait for the prompt indicating that the registration is complete.</li></ol> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152_Cardputer_Mesh_Kit_operate_05.jpg" width="70%"> <p>After successful device registration, the Meshtastic app page will display the device model and authorization mark:</p> <div class="warn"><div class="warn-title">Note</div> <div class="warn-content">Only devices in the Cardputer Mesh Kit set can be registered. Other Cardputer/-Adv devices are not eligible for Meshtastic authorization registration. If registration fails, please contact M5Stack official after-sales support.</div></div><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152_Cardputer_Mesh_Kit_operate_06.jpg" width="40%"> <h2 id="pinmap" data-id="PinMap">PinMap</h2> <h3 id="cardputer-adv-ext-254-14p" data-id="Cardputer-Adv EXT 2.54-14P">Cardputer-Adv EXT 2.54-14P</h3> <div class="m5-bus-table-container core"><div class="table-container"><table><thead><tr><th>FUNC</th> <th>PIN</th> <th>LEFT</th> <th>RIGHT</th> <th>PIN</th> <th>FUNC</th></tr></thead><tbody><tr><td>RESET</td> <td>G3</td> <td>1</td> <td>2</td> <td class="VCC">5VIN</td> <td class="empty"></td></tr> <tr><td>INT</td> <td>G4</td> <td>3</td> <td>4</td> <td class="GND">GND</td> <td class="empty"></td></tr> <tr><td>BUSY</td> <td>G6</td> <td>5</td> <td>6</td> <td class="VCC">5VOUT</td> <td class="empty"></td></tr> <tr><td class="SPI">SCK</td> <td>G40</td> <td>7</td> <td>8</td> <td>G8</td> <td class="I2C">I2C_SDA</td></tr> <tr><td class="SPI">MOSI</td> <td>G14</td> <td>9</td> <td>10</td> <td>G9</td> <td class="I2C">I2C_SCL</td></tr> <tr><td class="SPI">MISO</td> <td>G39</td> <td>11</td> <td>12</td> <td>G13</td> <td>UART_RX</td></tr> <tr><td class="SPI">CS</td> <td>G5</td> <td>13</td> <td>14</td> <td>G15</td> <td>UART_TX</td></tr></tbody></table></div></div><h3 id="cardputer-adv-lcd" data-id="Cardputer-Adv LCD">Cardputer-Adv LCD</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G38</th> <th>G33</th> <th>G34</th> <th>G35</th> <th>G36</th> <th>G37</th></tr></thead><tbody><tr><td>ST7789V2</td> <td>DISP_BL</td> <td>RST</td> <td>RS</td> <td>DAT</td> <td>SCK</td> <td>CS</td></tr> <tr><td>RGB LED</td> <td>PWR_EN</td> <td></td> <td></td> <td></td> <td></td> <td></td></tr></tbody></table></div><h3 id="cardputer-adv-audio" data-id="Cardputer-Adv Audio">Cardputer-Adv Audio</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th> <th>G41</th> <th>G46</th> <th>G43</th> <th>G42</th></tr></thead><tbody><tr><td>ES8311</td> <td>SDA</td> <td>SCL</td> <td>SCLK</td> <td>ASDOUT</td> <td>LRCK</td> <td>DSDIN</td></tr></tbody></table></div><h3 id="cardputer-adv-imu" data-id="Cardputer-Adv IMU">Cardputer-Adv IMU</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th></tr></thead><tbody><tr><td>BMI270</td> <td>SDA</td> <td>SCL</td></tr></tbody></table></div><h3 id="cardputer-adv-ir" data-id="Cardputer-Adv IR">Cardputer-Adv IR</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G44</th></tr></thead><tbody><tr><td>IR TX</td> <td>TX</td></tr></tbody></table></div><h3 id="cardputer-adv-battery" data-id="Cardputer-Adv Battery">Cardputer-Adv Battery</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G10</th></tr></thead><tbody><tr><td>Battery</td> <td>ADC</td></tr></tbody></table></div><h3 id="cardputer-adv-keyboard" data-id="Cardputer-Adv Keyboard">Cardputer-Adv Keyboard</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G8</th> <th>G9</th> <th>G11</th></tr></thead><tbody><tr><td>TCA8418RTWR</td> <td>SDA</td> <td>SCL</td> <td>INT</td></tr></tbody></table></div><h3 id="cardputer-adv-microsd" data-id="Cardputer-Adv microSD">Cardputer-Adv microSD</h3> <div class="table-container"><table><thead><tr><th>Stamp-S3A</th> <th>G12</th> <th>G14</th> <th>G40</th> <th>G39</th></tr></thead><tbody><tr><td>microSD</td> <td>CS</td> <td>MOSI</td> <td>CLK</td> <td>MISO</td></tr></tbody></table></div><h3 id="cardputer-adv-hy20-4p" data-id="Cardputer-Adv HY2.0-4P">Cardputer-Adv HY2.0-4P</h3> <div class="grove-table-container"><div class="table-container"><table><thead><tr><th>HY2.0-4P</th> <th>Black</th> <th>Red</th> <th>Yellow</th> <th>White</th></tr></thead><tbody><tr><td>PORT.CUSTOM</td> <td>GND</td> <td>5V</td> <td>G2</td> <td>G1</td></tr></tbody></table></div></div><h3 id="cap-lora-1262-cap-bus" data-id="Cap LoRa-1262 Cap-Bus">Cap LoRa-1262 Cap-Bus</h3> <div class="m5-bus-table-container module"><div class="table-container"><table><thead><tr><th>PIN</th> <th>LEFT</th> <th>RIGHT</th> <th>PIN</th></tr></thead><tbody><tr><td>GPS_TX</td> <td>1</td> <td>14</td> <td>LoRa_NSS</td></tr> <tr><td>GPS_RX</td> <td>2</td> <td>13</td> <td class="SPI">LoRa_MISO</td></tr> <tr><td class="I2C">SCL</td> <td>3</td> <td>12</td> <td class="SPI">LoRa_MOSI</td></tr> <tr><td class="I2C">SDA</td> <td>4</td> <td>11</td> <td class="SPI">LoRa_SCK</td></tr> <tr><td class="VCC">5V_OUT</td> <td>5</td> <td>10</td> <td>LoRa_BUSY</td></tr> <tr><td class="GND">GND</td> <td>6</td> <td>9</td> <td class="IRQ">LoRa_IRQ</td></tr> <tr><td class="VCC">5V_IN</td> <td>7</td> <td>8</td> <td class="RST">LoRa_RST</td></tr></tbody></table></div></div><div class="table-container"><table><thead><tr><th>Cardputer-Adv</th> <th>G3</th> <th>G4</th> <th>G6</th> <th>G40</th> <th>G14</th> <th>G39</th> <th>G5</th></tr></thead><tbody><tr><td>Cap LoRa-1262 (LoRa)</td> <td>RST</td> <td>IRQ</td> <td>BUSY</td> <td>SCK</td> <td>MOSI</td> <td>MISO</td> <td>NSS</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>Cardputer-Adv</th> <th>G13</th> <th>G15</th></tr></thead><tbody><tr><td>Cap LoRa-1262 (GPS)</td> <td>GPS-RX</td> <td>GPS-TX</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>Cardputer-Adv</th> <th>G8</th> <th>G9</th></tr></thead><tbody><tr><td>Cap LoRa-1262 (PI4IOE5V6408)</td> <td>SDA</td> <td>SCL</td></tr> <tr><td>Cap LoRa-1262 (HY2.0-4P)</td> <td>SDA</td> <td>SCL</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>PI4IOE5V6408</th> <th>P0</th></tr></thead><tbody><tr><td>FM8625H</td> <td>SX_ANT_SW</td></tr></tbody></table></div><p>The following steps are required to initialize the LoRa module:</p><ul><li>Enable the RF antenna switch: set P0 of the PI4IOE I/O expander to HIGH</li></ul> <h3 id="cap-lora-1262-hy20-4p" data-id="Cap LoRa-1262 HY2.0-4P">Cap LoRa-1262 HY2.0-4P</h3> <div class="grove-table-container"><div class="table-container"><table><thead><tr><th>HY2.0-4P</th> <th>Black</th> <th>Red</th> <th>Yellow</th> <th>White</th></tr></thead><tbody><tr><td class="PORTA">PORT.A</td> <td>GND</td> <td>5V</td> <td>SDA</td> <td>SCL</td></tr></tbody></table></div></div><h2 id="schematics" data-id="Schematics">Schematics</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58.pdf">Cardputer-Adv Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf">Stamp-S3A Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-sche-Cap-LoRa1262_SCH_V1.1_20251029_2025_11_07_22_53_19.pdf">Cap LoRa-1262 Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/NEW-1262-SCH_A1-Lora_2025_08_27_10_58_52.pdf">Stamp LoRa-1262 Mini Schematics PDF</a></li></ul> <div class="carousel-container" data-v-7d51a79c><div class="carousel-preview" data-v-7d51a79c><div class="clickable-area left" data-v-7d51a79c></div> <button class="arrow left" data-v-7d51a79c></button> <div class="carousel-images" data-v-7d51a79c><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-7d51a79c><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_02.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_03.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_04.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-sche-Cap-LoRa1262_SCH_1.1_20251029_2025_11_07_22_53_19_page_02.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/NEW-1262-SCH_A1-Lora_2025_08_27_10_58_52_page_01.png" alt="Preview" data-v-7d51a79c></div></div></div> <button class="arrow right" data-v-7d51a79c></button> <div class="clickable-area right" data-v-7d51a79c></div> <div class="corner-marker" data-v-7d51a79c>1/7</div></div> <div class="carousel-thumbnails" data-v-7d51a79c><div class="thumbnail active" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_02.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_03.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/Sch_M5CardputerAdv_v1.0_2025_06_20_17_19_58_page_04.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-sche-Cap-LoRa1262_SCH_1.1_20251029_2025_11_07_22_53_19_page_02.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/NEW-1262-SCH_A1-Lora_2025_08_27_10_58_52_page_01.png" alt="Thumbnail" data-v-7d51a79c></div></div></div> <h2 id="model-size" data-id="Model Size">Model Size</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV.pdf">Cardputer-Adv Model Size PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-00-cap1262-model-size.pdf">Cap LoRa-1262 Model Size PDF</a></li></ul> <div class="carousel-container" data-v-7d51a79c><div class="carousel-preview" data-v-7d51a79c><div class="clickable-area left" data-v-7d51a79c></div> <button class="arrow left" data-v-7d51a79c></button> <div class="carousel-images" data-v-7d51a79c><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-7d51a79c><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV_page_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-00-cap1262-model-size_page_01.png" alt="Preview" data-v-7d51a79c></div></div></div> <button class="arrow right" data-v-7d51a79c></button> <div class="clickable-area right" data-v-7d51a79c></div> <div class="corner-marker" data-v-7d51a79c>1/2</div></div> <div class="carousel-thumbnails" data-v-7d51a79c><div class="thumbnail active" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1178/K132-Adv-cardputer-ADV_page_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1208/U214-00-cap1262-model-size_page_01.png" alt="Thumbnail" data-v-7d51a79c></div></div></div> <h2 id="structure" data-id="Structure">Structure</h2> <ul><li><a target="_blank" href="https://github.com/m5stack/M5_Hardware/tree/master/Products/K152_Cardputer_Mesh_Kit/Structures">Cardputer Mesh Kit Structure Files</a></li></ul> <h2 id="datasheets" data-id="Datasheets">Datasheets</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf">ESP32-S3</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf">ST7789V2</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/atom/Atomic%20Echo%20Base/ES8311.pdf">ES8311</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/atom/Atomic%20Echo%20Base/NS4150B.pdf">NS4150B</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/K128%20CoreS3/BMI270.PDF">BMI270</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf">SX1262</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/unit/Unit-GPS%20v1.1/ATGM336H-6N.pdf">ATGM336H-6N</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1173/CASIC_Multi-mode_Satellite_Navigation_Receiver_Protocol_Specification.pdf">CASIC Multi-Constellation GNSS Receiver Protocol Specification</a></li></ul> <h2 id="softwares" data-id="Softwares">Softwares</h2> <h3 id="arduino" data-id="Arduino">Arduino</h3> <ul><li><a target="_blank" href="/en/arduino/m5cardputer/program">Cardputer-Adv Arduino Quick Start</a></li> <li><a target="_blank" href="/en/arduino/projects/cap/cap_lora868">Cap LoRa-1262 Arduino Quick Start</a></li> <li><a target="_blank" href="https://github.com/m5stack/M5Cardputer">Cardputer-Adv Arduino Library</a></li> <li><a target="_blank" href="https://github.com/jgromes/RadioLib">Cap LoRa-1262 LoRa Library (RadioLib)</a></li> <li><a target="_blank" href="https://github.com/m5stack/TinyGPSPlus">Cap LoRa-1262 GPS Library (TinyGPSPlus)</a></li></ul> <h3 id="uiflow2" data-id="UiFlow2">UiFlow2</h3> <ul><li><a target="_blank" href="/en/uiflow2/cardputer-adv/program">Cardputer-Adv UiFlow2 Quick Start</a></li> <li><a target="_blank" href="https://uiflow-micropython.readthedocs.io/en/latest/cap/lora1262.html">Cap LoRa-1262 UiFlow2 Docs</a></li></ul> <h3 id="platformio" data-id="PlatformIO">PlatformIO</h3> <div class="code-block-wrapper"><div class="code-line-container"><pre><code class="hljs language-bash">[env:m5stack-cardputer-mesh-kit]
-platform = espressif32@6.12.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-          -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer
-    RadioLib=https://github.com/jgromes/RadioLib
-    TinyGPSPlus=https://github.com/m5stack/TinyGPSPlus</code></pre> <button class="copy-all-btn"><code>[env:m5stack-cardputer-mesh-kit]
-platform = espressif32@6.12.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-          -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer
-    RadioLib=https://github.com/jgromes/RadioLib
-    TinyGPSPlus=https://github.com/m5stack/TinyGPSPlus</code> <div class="fa-solid fa-copy"></div></button></div></div> <h3 id="easyloader" data-id="Easyloader">Easyloader</h3> <div class="table-container"><table><thead><tr><th>Easyloader</th> <th>Download</th></tr></thead><tbody><tr><td>Cardputer-Adv Factory Firmware Easyloader</td> <td><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1240/K152-factory-firmware.exe">download</a></td></tr></tbody></table></div><h2 id="video" data-id="Video">Video</h2> <div class="video-gallery-island" data-v-5e05839f></div></div> <!----> <!----> <!----></div></div> <div class="docs-layouts-anchor"><div class="page-tools" data-v-39baf185><div class="page-tools-title" data-v-39baf185>Page Tools</div> <div class="page-tools-actions" data-v-39baf185><a href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/Cardputer_Mesh_Kit.pdf" target="_blank" rel="nofollow noopener noreferrer" title="Download PDF" class="page-tools-action page-tools-pdf" data-v-39baf185><svg viewBox="0 0 24 24" aria-hidden="true" class="page-tools-icon" data-v-39baf185><path d="M6 2h8l4 4v16H6V2zm7 1.8V7h3.2L13 3.8zM8.4 12.2h1.5c1 0 1.7-.6 1.7-1.6S10.9 9 9.9 9H7v6h1.4v-2.8zm0-1.1v-1h1.3c.3 0 .5.2.5.5s-.2.5-.5.5H8.4zm4.1 3.9h1.8c1.7 0 2.8-1.1 2.8-3s-1.1-3-2.8-3h-1.8v6zm1.4-1.2v-3.6h.4c.9 0 1.4.6 1.4 1.8s-.5 1.8-1.4 1.8h-.4zm4.1 1.2h1.4v-2.4h2.1v-1.2h-2.1v-1.2h2.4V9H18v6z" data-v-39baf185></path></svg> <span data-v-39baf185>PDF</span></a> <div class="markdown-action-menu placement-toolbox" data-v-5d6a4f8a data-v-39baf185><button type="button" title="Copy page" class="markdown-action-trigger" data-v-5d6a4f8a><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><rect x="9" y="9" width="13" height="13" rx="2"></rect><path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1"></path></svg> <span data-v-5d6a4f8a>Copy page</span> <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><polyline points="6 9 12 15 18 9"></polyline></svg></button> <!----></div></div></div></div></div> <footer><div class="footer-container"><div class="footer-content-wrap"><div class="footer-nav"><div class="footer-nav-item"><div data-id="0" class="footer-nav-title"><a class="footer-nav-title-a">
-        About Us
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/about-us">About M5Stack</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?page=1">News</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?type=blog&page=1">Blog</a></li><li class="footer-nav-li"><a href="https://m5stack.com/events">Events</a></li><li class="footer-nav-li"><a href="https://m5stack.com/contact">Contact Us</a></li></ul></div><div class="footer-nav-item"><div data-id="1" class="footer-nav-title"><a class="footer-nav-title-a">
-        Where to buy
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/distributor">Distributors</a></li><li class="footer-nav-li"><a href="https://shop.m5stack.com/">Official Store</a></li><li class="footer-nav-li"><a href="https://m5stack.aliexpress.com/store/911661199">AliExpress</a></li><li class="footer-nav-li"><a href="https://www.amazon.com/shops/m5stack">Amazon</a></li><li class="footer-nav-li"><a href="https://m5stack.taobao.com/">Taobao</a></li></ul></div><div class="footer-nav-item"><div data-id="2" class="footer-nav-title"><a class="footer-nav-title-a">
-        Solution
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/business">For Business</a></li><li class="footer-nav-li"><a href="https://m5stack.com/developers">For Developers</a></li></ul></div><div class="footer-nav-item"><div data-id="3" class="footer-nav-title"><a class="footer-nav-title-a">
-        Software
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://flow.m5stack.com/">UiFlow1</a></li><li class="footer-nav-li"><a href="https://uiflow2.m5stack.com/">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/uiflow/m5burner/intro">M5Burner</a></li><li class="footer-nav-li"><a href="https://block-designer.m5stack.com/">Block Designer</a></li><li class="footer-nav-li"><a href="/en/guide/ezdata/ezdata_v2">EzData 2.0</a></li><li class="footer-nav-li"><a href="/en/guide/easyloader/easyloader_packer">EasyLoader Packer</a></li><li class="footer-nav-li"><a href="/en/guide/develop_tools/vlw_font_creator">VLW Font Creator</a></li><li class="footer-nav-li"><a href="/en/download">Device USB Driver</a></li></ul></div><div class="footer-nav-item"><div data-id="4" class="footer-nav-title"><a class="footer-nav-title-a">
-        Documentation
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="/en/products">Product Documents</a></li><li class="footer-nav-li"><a href="/en/uiflow/uiflow_web">UiFlow1</a></li><li class="footer-nav-li"><a href="/en/uiflow2/uiflow_web">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/arduino/arduino_ide">Arduino</a></li><li class="footer-nav-li"><a href="/en/esp_idf/esp_idf">ESP-IDF</a></li><li class="footer-nav-li"><a href="/en/stackflow/overview">StackFlow AI</a></li><li class="footer-nav-li"><a href="/en/homeassistant/overview">Home Assistant</a></li><li class="footer-nav-li"><a href="https://github.com/nanoframework/nanoFramework.M5Stack">nanoFramework</a></li><li class="footer-nav-li"><a href="/en/guide/product_guide">Product Guide</a></li><li class="footer-nav-li"><a href="/en/certification">Product Certifications</a></li><li class="footer-nav-li"><a href="/en/product_i2c_addr">I2C Table</a></li><li class="footer-nav-li"><a href="/en/products_selector/m5core_compare">Product Selector</a></li><li class="footer-nav-li"><a href="https://github.com/m5stack/M5_Hardware">Hardware Design Files</a></li><li class="footer-nav-li"><a href="/en/history">Release History</a></li><li class="footer-nav-li"><a href="/en/compatible_stack">Stack Compatibility</a></li><li class="footer-nav-li"><a href="/en/learn/extension/module">Stack Screw Length</a></li></ul></div></div> <div class="footer-right"><div class="footer-email-group"><p class="footer-email-title">
-              Stay in the Loop
-            </p> <p class="footer-email-desc">
-              Weekly updates on new products, innovations, and announcements.
-            </p> <div class="footer-email-input"><input placeholder="Enter Email address" autocomplete="off" class="email-input"> <button type="button" class="subscribe-btn">
-                Subscribe
-              </button></div> <p class="footer-email-warning" style="display:none">
-              Email is invalid!
-            </p></div> <div class="footer-email-success" style="display:none">
-            Thanks for subscribing
-          </div> <div class="footer-follow"><div class="footer-follow-ul"><a href="https://x.com/M5Stack"><img src="/assets/footer/sociallist10.svg" alt></a><a href="https://www.linkedin.com/company/m5stack"><img src="/assets/footer/sociallist2.svg" alt></a><a href="https://www.instagram.com/m5stack"><img src="/assets/footer/sociallist8.svg" alt></a><a href="https://www.facebook.com/M5Stack"><img src="/assets/footer/sociallist7.svg" alt></a><a href="https://www.youtube.com/m5stack"><img src="/assets/footer/sociallist5.svg" alt></a><a href="https://www.tiktok.com/@m5stack"><img src="/assets/footer/tiktok.svg" alt></a><a href="https://www.hackster.io/m5stack"><img src="/assets/footer/sociallist3.svg" alt></a><a href="https://discord.gg/ysQAWBUE9Q"><img src="/assets/footer/sociallist4.svg" alt></a><a href="https://github.com/m5stack"><img src="/assets/footer/sociallist6.svg" alt></a></div></div> <div class="footer-info-wrapper"><div class="footer-info">
-            M5Stack Technology Co., Ltd
-          </div> <div class="footer-address-info">
-            Address: 
-             Block A10, Expo Bay South Coast, Fuhai Street, Bao'an District, Shenzhen, China
-          </div> <div class="footer-info">
-            TEL: 
-            +86 755 8657 5379
-          </div> <div class="footer-info">
-            Email: 
-            support@m5stack.com
-          </div></div></div></div></div> <div class="footer-bottom"><div class="footer-bottom-content"><div class="footer-copy">
-        Copyright ©
-        <a href="https://m5stack.com/">M5Stack Technology Co., Ltd.</a>
-        All rights reserved.
-      </div> <div class="terms-box"><!----> <a href="https://shop.m5stack.com/policies/privacy-policy">Privacy Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/terms-of-service">Terms of Service</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/shipping-policy">Shipping Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/refund-policy">Refund Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/pages/payment-method">Payment Method</a></div> <div class="beian"><a href="https://beian.miit.gov.cn/">粤ICP备16010631号</a></div></div></div> <!----></footer> <div class="float-icon-container"><div class="totop-icon"><svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 280 280" xmlns:xlink="http://www.w3.org/1999/xlink" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M143 70l58 69c1,1 1,3 1,4 -1,1 -2,2 -4,2l-20 0c-2,0 -4,2 -4,4l1 57c0,2 -2,4 -4,4l-62 0c-2,0 -4,-2 -4,-4l1 -57c0,-2 -2,-4 -4,-4l-20 0c-2,0 -3,-1 -4,-2 -1,-1 0,-3 1,-4l58 -69c1,-1 2,-1 3,-1 1,0 2,1 3,1z" class="fil1"></path></g></svg></div> <div class="menu-icon" style="display:none"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 800 800" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M253 229l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 370l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 511l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path></g></svg></div></div></div></div></div></div><script defer src="/_nuxt/static/1788504562/en/core/Cardputer_Mesh_Kit/state.js"></script><script src="/_nuxt/41d5c62.js" defer></script><script src="/_nuxt/c970150.js" defer></script><script src="/_nuxt/5a34d22.js" defer></script><script src="/_nuxt/a352c6d.js" defer></script><script src="/_nuxt/b9c4bc6.js" defer></script>
-  </body>
-</html>
diff --git a/devices/m5stack/cardputer-mesh-kit/certification-and-compliance.md b/devices/m5stack/cardputer-mesh-kit/certification-and-compliance.md
deleted file mode 100644
index 3058e2e..0000000
--- a/devices/m5stack/cardputer-mesh-kit/certification-and-compliance.md
+++ /dev/null
@@ -1,160 +0,0 @@
-# Certification and compliance — cardputer-mesh-kit
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-A retail bundle, not a distinct radio product. The two radio-bearing parts are separately granted; a bundle does not require its own authorisation.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AN3WM5CARDPUTERADV`, `2AN3WM5CAPLORA1262`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5CARDPUTERADV`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2412-2462 MHz Original Equipment 2025-11-19** |
-| Application purpose | Final Action Date 2412-2462 MHz Original Equipment 2025-11-19 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 4 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5CARDPUTERADV` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-- USA-DueDigilenceLetter_V0.1 [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 1,041,781 | `b6e8389cbab5335b…` |
-| `ID-Label-Location-Info-FCC-ID-Label.pdf` | 184,122 | `38b3c9554c31c2df…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,848,880 | `b7b25570be4a4fb5…` |
-| `RF-Exposure-Info-AiTDG-251013004W3_FCC-RF-EXPOSURE-0cm.pdf` | 258,022 | `f63d066218178f0e…` |
-| `Test-Report-AiTDG-251013004W1-FCC-BLE-test-report.pdf` | 987,894 | `5023c54591ee8a5f…` |
-| `Users-Manual-User-Manual.pdf` | 390,005 | `2e7ea0b53e452386…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5CARDPUTERADV/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5CARDPUTERADV/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AN3WM5CAPLORA1262`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **903-914.9 MHz Original Equipment 2026-02-12** |
-| Application purpose | Final Action Date 903-914.9 MHz Original Equipment 2026-02-12 |
-| Frequency ranges | **903-914.9 MHz** |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 14 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5CAPLORA1262` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 767,323 | `dca8f216a5c65942…` |
-| `ID-Label-Location-Info-Label-and-Label-Location.pdf` | 134,335 | `e3963b8a5baed487…` |
-| `Internal-Photos-Internal-Photos.pdf` | 809,213 | `61f89fc08fde8a09…` |
-| `RF-Exposure-Info-RF-Exposure-Information.pdf` | 324,207 | `ac8a66ce38b09480…` |
-| `Test-Report-Antenna-Specification.pdf` | 592,270 | `da669cafd28d9fd1…` |
-| `Users-Manual-User-Manual.pdf` | 765,439 | `fb81cff4fb9a5d09…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5CAPLORA1262/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5CAPLORA1262/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cardputer-mesh-kit/market-and-pricing.md b/devices/m5stack/cardputer-mesh-kit/market-and-pricing.md
deleted file mode 100644
index 22fdf74..0000000
--- a/devices/m5stack/cardputer-mesh-kit/market-and-pricing.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Market and pricing — cardputer-mesh-kit
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| Cardputer Mesh Kit for Meshtastic (ESP32-S3) | 2026-04-30 | Default Title | `K152` | **USD 48.00** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 48.00, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/cardputer-mesh-kit-for-meshtastic-esp32-s3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `K152`. ⚠ **A bundle.** At USD 48.00 it sits above Cardputer ADV (29.90) + Cap LoRa 1262 (14.50) = **USD 44.40**, a USD 3.60 bundle premium. Do not merge this into a bare-board range.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cardputer-v1.0/README.md b/devices/m5stack/cardputer-v1.0/README.md
deleted file mode 100644
index 8172fc1..0000000
--- a/devices/m5stack/cardputer-v1.0/README.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# M5Stack Cardputer (v1.0, K132)
-
-> **SKU `K132`** · product id **`481`** · core module **StampS3** (`Sch_M5StampS3_v0.2`)
-> Superseded by [v1.1](../cardputer-v1.1/README.md) on **2025-03-07** and by the
-> [ADV](../cardputer-adv/README.md) on **2025-09-05**. No longer listed on M5Stack's store as of
-> **2026-09-04** (the store lists only the `[EOL]`-titled v1.1 and the ADV).
-> Research snapshot **2026-09-04**.
-
-The original. It defined the format — 84 × 54 mm, 56 keys, 1.14″ screen, magnetic LEGO-compatible
-base — and everything since has been a refinement of it.
-
-This record is light by design. The v1.0 and v1.1 **share a mainboard schematic file**, so
-everything except the Stamp module is documented at
-[`../cardputer-v1.1/README.md`](../cardputer-v1.1/README.md), and the deep treatment of the
-shared subsystems is at [`../cardputer-adv/`](../cardputer-adv/README.md).
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Name | Cardputer |
-| SKU | `K132` |
-| Product id | `481`; Stamp module `522` |
-| Core module | **StampS3** (`Sch_M5StampS3_v0.2.pdf`, 348 884 B, `6d92e1ae…`) |
-| SoC | ESP32-S3FN8, 8 MB flash, **no PSRAM** |
-| Display | ST7789V2 1.14″ 240 × 135 |
-| Keyboard | 56 keys via **74HC138** |
-| Audio | NS4168 amp + **SPM1423** PDM mic, no jack |
-| Battery | 120 mAh internal + 1400 mAh base |
-| Size / weight | 84.0 × 54.0 × 19.7 mm, **92.3 g** — the heaviest of the three |
-| Sleep / operating current | 0.26 µA; IR mode 255.6 mA, key mode 165.7 mA |
-| Includes | 1 × Cardputer, 1 × **2.0 mm** hex key |
-
-## The only real difference: the Stamp module
-
-| | **StampS3 v0.2** (this board) | Stamp-S3A v0.3.3 (v1.1, ADV) |
-|---|---|---|
-| 3.3 V rail | `M2` = **Murata `MUN3CAD01-SC`**, a `µPOL` 1 A point-of-load **power module** (converter + inductor + caps in one 2.9 × 2.3 × 1.05 mm package), 2.7–5.5 V in, output set by R16 100 k / R17 22.1 k. Identified by a concurrent session from a retrieved datasheet — this pass had flagged the string as suspect because there is **no page render for product id 522** to check it against. | **JoulWatt `JW5712`** buck |
-| Load switch | **SGM2578** (U2) | AW35122FDR (U2) |
-| **WS2812 supply** | **`VDD_3V3` — always on** | `BL_3V3` — switched with the backlight |
-| Boot button | `SMT_SW_1TS026A`, body 2.6 × 1.6 × 0.55 mm | same part, body 4.0 × 3.0 × 2.0 mm |
-| Crystal load caps | 12 pF / 10 pF | 12 pF / 12 pF |
-| Solder jumper `JP4` at the WS2812 | **present** | removed |
-| Antenna | "standard" | "optimized" |
-
-**The v1.0 is the only Cardputer whose RGB LED works at any backlight level**, because its
-WS2812 is not on the switched rail. That is a genuine advantage over both later boards, and it
-was traded away for a lower sleep current (0.26 µA → 0.15 µA). Verified by comparing U3's `VDD`
-net across the two Stamp schematics.
-
-## ⚠ The published schematics are the same file as the v1.1's
-
-`…/481/Sch_M5Cardputer.pdf` and `…/1127/Sch_M5Cardputer.pdf` are **byte-identical**
-(SHA-256 `6016c1fe6099b9e3f0d0c88f07a3fba1aa44a3da8a7a91dd7040ad0fffa2041e`, 717 743 B), as are
-the two base schematics (`29542fe1…`, 24 076 B). Read with M5Stack's own comparison table —
-which lists only module-level differences — the honest statement is that **no mainboard change
-between v1.0 and v1.1 is documented**. Whether one exists is unresolved; see
-[`../cardputer-adv/gaps-and-conflicts.md`](../cardputer-adv/gaps-and-conflicts.md) §C3.
-
-For that reason the schematic PDF is retained once, in the
-[v1.1 record](../cardputer-v1.1/README.md), rather than duplicated here.
-
-## Pin map
-
-Identical to the v1.1 in every row. See [`../cardputer-v1.1/README.md`](../cardputer-v1.1/README.md#pin-map).
-Keyboard: drive `G8/G9/G11` → 74HC138 `A0/A1/A2`; sense `G13, G15, G3, G4, G5, G6, G7`;
-battery ADC `G10`; microSD `G12/G14/G40/G39`; display `G33–G38`; RGB `G21`;
-audio `G41/G42/G43/G46`; IR `G44`; Grove `G1/G2`. **No internal I²C bus.**
-
-## Components
-
-Same as the v1.1 except the module: [`m5stack/stamp-s3`](../../../components/m5stack/stamp-s3/README.md)
-(v0.2) instead of `stamp-s3a`, and [`sgmicro/sgm2578`](../../../components/sgmicro/sgm2578/README.md)
-in place of the AW35122FDR, and [`murata/mun3cad01-sc`](../../../components/murata/mun3cad01-sc/README.md) — a `µPOL` power module — in place of the JW5712 buck.
-
-## Development
-
-Identical toolchain and procedure to the v1.1 and ADV — same PlatformIO profile, same
-download-mode sequence, same `M5Cardputer` library (which installs `IOMatrixKeyboardReader`).
-Factory firmware: `M5Cardputer-UserDemo` **`main`**. EasyLoader:
-`m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/Cardputer.exe`
-— **the same binary the v1.1 page links.**
-
-Library milestones for this board: first commits 2023-10-10, `v1.0.1` with IR/NEC and key
-numbering 2023-10-13, USB-keyboard demo 2023-10-16, SD demo 2024-01-19, WAV recording 2024-12-25.
-
-## Community
-
-Every major Cardputer firmware supports it — it is the compatibility baseline. It has no
-Meshtastic upstream variant and none of the 2026 ADV-only projects. Buying one new in 2026 is
-not possible through M5Stack; second-hand data was not gathered.
-
-## Sources
-
-Product page `https://docs.m5stack.com/en/core/Cardputer` (retrieved 2026-09-04, snapshot at
-`artifacts/docs-en-core-Cardputer.html`); StampS3 v0.2 schematic
-`https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2.pdf`;
-`M5Cardputer` @ `f1392858`. Full table: [`../cardputer-adv/sources.md`](../cardputer-adv/sources.md).
diff --git a/devices/m5stack/cardputer-v1.0/acquisition/manifest.json b/devices/m5stack/cardputer-v1.0/acquisition/manifest.json
deleted file mode 100644
index 38f8a8c..0000000
--- a/devices/m5stack/cardputer-v1.0/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "devices/m5stack/cardputer-v1.0",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AN3WM5CARDPUTER-7493098",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CARDPUTER/Test-Report/Antenna-Specification-7493098.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493098",
-    "https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493098.pdf",
-    "https://fccid.io/2AN3WM5CARDPUTER",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/Test-Report/Antenna-Specification-7493098.pdf"
-   ],
-   "sha256": "0728acb7f328e39ceb9c466d8ca99689211002d4f3dda9a1f4c452dd7ebb498c",
-   "bytes": 822846,
-   "destination": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-07-22",
-   "fcc_id": "2AN3WM5CARDPUTER",
-   "fcc_document_id": "7493098",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Specification",
-   "grant_date": "2024-07-22",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf",
-   "placeholder": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cardputer-v1.0",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CARDPUTER-7493107",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CARDPUTER/External-Photos/External-Photos-7493107.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493107",
-    "https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493107.pdf",
-    "https://fccid.io/2AN3WM5CARDPUTER",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/External-Photos/External-Photos-7493107.pdf"
-   ],
-   "sha256": "daafa38179323ddb9e33e1b22322230a698a5b803fe16c4409871d5ad0d6a9fc",
-   "bytes": 1811474,
-   "destination": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-07-22",
-   "fcc_id": "2AN3WM5CARDPUTER",
-   "fcc_document_id": "7493107",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2024-07-22",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf",
-   "placeholder": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cardputer-v1.0",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CARDPUTER-7493112",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CARDPUTER/Label/FCC-ID-Label-7493112.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493112",
-    "https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493112.pdf",
-    "https://fccid.io/2AN3WM5CARDPUTER",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/Label/FCC-ID-Label-7493112.pdf"
-   ],
-   "sha256": "fcdfbce02de768d7f1e758ee5ab179217c717e7328b79b3cb99eeda340f48495",
-   "bytes": 467757,
-   "destination": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-id-label.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-07-22",
-   "fcc_id": "2AN3WM5CARDPUTER",
-   "fcc_document_id": "7493112",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "FCC ID Label",
-   "grant_date": "2024-07-22",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cardputer-v1.0",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CARDPUTER-7493141",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CARDPUTER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7493141.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493141",
-    "https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493141.pdf",
-    "https://fccid.io/2AN3WM5CARDPUTER",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7493141.pdf"
-   ],
-   "sha256": "6c89ae08c922ccdefbf5b763f9ea4e82603d9b712e80eded1eb1cba2a54d6d02",
-   "bytes": 126467,
-   "destination": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-07-22",
-   "fcc_id": "2AN3WM5CARDPUTER",
-   "fcc_document_id": "7493141",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "FCC RF Exposure-MPE",
-   "grant_date": "2024-07-22",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf",
-   "placeholder": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cardputer-v1.0",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CARDPUTER-7493111",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CARDPUTER/Internal-Photos/Internal-Photos-7493111.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493111",
-    "https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493111.pdf",
-    "https://fccid.io/2AN3WM5CARDPUTER",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/Internal-Photos/Internal-Photos-7493111.pdf"
-   ],
-   "sha256": "04d0f83f4d202d9f12a0e09acdfab754e469117b2c086b442bfba510d4cb3d7f",
-   "bytes": 1588902,
-   "destination": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-07-22",
-   "fcc_id": "2AN3WM5CARDPUTER",
-   "fcc_document_id": "7493111",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2024-07-22",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cardputer-v1.0",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5CARDPUTER-7493146",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5CARDPUTER/User-Manual/User-Manual-7493146.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493146",
-    "https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493146.pdf",
-    "https://fccid.io/2AN3WM5CARDPUTER",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/User-Manual/User-Manual-7493146.pdf"
-   ],
-   "sha256": "629df489491ef940b43dd7d5d645b0179e26982b4fc9278235fa23091e380690",
-   "bytes": 3165025,
-   "destination": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2024-07-22",
-   "fcc_id": "2AN3WM5CARDPUTER",
-   "fcc_document_id": "7493146",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2024-07-22",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf",
-   "placeholder": "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/cardputer-v1.0",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf.ARCHIVED.md b/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 1df4685..0000000
--- a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTER-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 822,846 B (0.78 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 822,846 B (0.78 MiB) |
-| SHA-256 | `0728acb7f328e39ceb9c466d8ca99689211002d4f3dda9a1f4c452dd7ebb498c` |
-| FCC ID | **`2AN3WM5CARDPUTER`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 7493098 |
-| Upstream publication date | 2024-07-22 |
-| Grant date | 2024-07-22 |
-| Equipment class | M5Cardputer, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTER/Test-Report/Antenna-Specification-7493098.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493098>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493098.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/Test-Report/Antenna-Specification-7493098.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf" \
-   "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTER/Test-Report/Antenna-Specification-7493098.pdf" -o "2AN3WM5CARDPUTER-antenna-specification.pdf"
-echo "0728acb7f328e39ceb9c466d8ca99689211002d4f3dda9a1f4c452dd7ebb498c  2AN3WM5CARDPUTER-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf.ARCHIVED.md b/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 9723369..0000000
--- a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTER-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 1,811,474 B (1.73 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,811,474 B (1.73 MiB) |
-| SHA-256 | `daafa38179323ddb9e33e1b22322230a698a5b803fe16c4409871d5ad0d6a9fc` |
-| FCC ID | **`2AN3WM5CARDPUTER`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 7493107 |
-| Upstream publication date | 2024-07-22 |
-| Grant date | 2024-07-22 |
-| Equipment class | M5Cardputer, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTER/External-Photos/External-Photos-7493107.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493107>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493107.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/External-Photos/External-Photos-7493107.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf" \
-   "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTER/External-Photos/External-Photos-7493107.pdf" -o "2AN3WM5CARDPUTER-external-photos.pdf"
-echo "daafa38179323ddb9e33e1b22322230a698a5b803fe16c4409871d5ad0d6a9fc  2AN3WM5CARDPUTER-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-id-label.pdf b/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-id-label.pdf
deleted file mode 100644
index bb13684..0000000
Binary files a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-id-label.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md b/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md
deleted file mode 100644
index 488346d..0000000
--- a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 126,467 B (0.12 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 126,467 B (0.12 MiB) |
-| SHA-256 | `6c89ae08c922ccdefbf5b763f9ea4e82603d9b712e80eded1eb1cba2a54d6d02` |
-| FCC ID | **`2AN3WM5CARDPUTER`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | FCC RF Exposure-MPE |
-| FCC document id | 7493141 |
-| Upstream publication date | 2024-07-22 |
-| Grant date | 2024-07-22 |
-| Equipment class | M5Cardputer, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7493141.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493141>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493141.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7493141.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf" \
-   "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7493141.pdf" -o "2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf"
-echo "6c89ae08c922ccdefbf5b763f9ea4e82603d9b712e80eded1eb1cba2a54d6d02  2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-internal-photos.pdf b/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-internal-photos.pdf
deleted file mode 100644
index 22f7b57..0000000
Binary files a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-internal-photos.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf.ARCHIVED.md b/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 17d0475..0000000
--- a/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5CARDPUTER-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 3,165,025 B (3.02 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 3,165,025 B (3.02 MiB) |
-| SHA-256 | `629df489491ef940b43dd7d5d645b0179e26982b4fc9278235fa23091e380690` |
-| FCC ID | **`2AN3WM5CARDPUTER`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 7493146 |
-| Upstream publication date | 2024-07-22 |
-| Grant date | 2024-07-22 |
-| Equipment class | M5Cardputer, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5CARDPUTER/User-Manual/User-Manual-7493146.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7493146>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5CARDPUTER/7493146.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5CARDPUTER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5CARDPUTER/User-Manual/User-Manual-7493146.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf" \
-   "devices/m5stack/cardputer-v1.0/artifacts/certification/2AN3WM5CARDPUTER-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5CARDPUTER/User-Manual/User-Manual-7493146.pdf" -o "2AN3WM5CARDPUTER-user-manual.pdf"
-echo "629df489491ef940b43dd7d5d645b0179e26982b4fc9278235fa23091e380690  2AN3WM5CARDPUTER-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/certification/README.md b/devices/m5stack/cardputer-v1.0/artifacts/certification/README.md
deleted file mode 100644
index fd829d0..0000000
--- a/devices/m5stack/cardputer-v1.0/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5CARDPUTER`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5CARDPUTER`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2024-07-22** |
-| Equipment class | M5Cardputer, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Source page | <https://fccid.io/2AN3WM5CARDPUTER> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5CARDPUTER-fcc-id-label.pdf` | 467,757 | `fcdfbce02de768d7f1e758ee5ab179217c717e7328b79b3cb99eeda340f48495` | ID Label/Location Info |
-| `2AN3WM5CARDPUTER-internal-photos.pdf` | 1,588,902 | `04d0f83f4d202d9f12a0e09acdfab754e469117b2c086b442bfba510d4cb3d7f` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5CARDPUTER-antenna-specification.pdf.ARCHIVED.md`](2AN3WM5CARDPUTER-antenna-specification.pdf.ARCHIVED.md) | 822,846 | Test Report |
-| [`2AN3WM5CARDPUTER-external-photos.pdf.ARCHIVED.md`](2AN3WM5CARDPUTER-external-photos.pdf.ARCHIVED.md) | 1,811,474 | External Photos |
-| [`2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md`](2AN3WM5CARDPUTER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md) | 126,467 | RF Exposure Info |
-| [`2AN3WM5CARDPUTER-user-manual.pdf.ARCHIVED.md`](2AN3WM5CARDPUTER-user-manual.pdf.ARCHIVED.md) | 3,165,025 | Users Manual |
-
-Archived total: **4 files, 5.65 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 1.96 MiB** |
-| Archived | **4 files, 5.65 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/m5stack/cardputer-v1.0/artifacts/docs-en-core-Cardputer.html b/devices/m5stack/cardputer-v1.0/artifacts/docs-en-core-Cardputer.html
deleted file mode 100644
index 6c26084..0000000
--- a/devices/m5stack/cardputer-v1.0/artifacts/docs-en-core-Cardputer.html
+++ /dev/null
@@ -1,110 +0,0 @@
-<!doctype html>
-<html data-n-head-ssr lang="en" data-n-head="%7B%22lang%22:%7B%22ssr%22:%22en%22%7D%7D">
-  <head>
-    <title>m5-docs</title><meta data-n-head="ssr" charset="utf-8"><meta data-n-head="ssr" name="viewport" content="width=device-width,initial-scale=1,minimum-scale=1,user-scalable=no"><meta data-n-head="ssr" data-hid="description" name="description" content="The reference docs for M5Stack products. Quick start, get the detailed information or instructions such as IDE,UIFLOW,Arduino. The tutorials for M5Burner, Firmware, Burning, programming. ESP32,M5StickC,StickV, StickT,M5ATOM."><link data-n-head="ssr" rel="icon" type="image/x-icon" href="/favicon.ico"><script data-n-head="ssr" data-hid="device-preload-detector">!function(){try{var e=document.documentElement;if(!e)return;var d=e.clientWidth||Number.POSITIVE_INFINITY,i=Number(window.innerWidth||0)||Number.POSITIVE_INFINITY,a=Math.min(d,i)<1024;e.classList.add(a?"device-preload-mobile":"device-preload-desktop"),a&&(e.classList.add("device-preload-pending"),window.__m5DevicePreloadReady=function(){e.classList.remove("device-preload-pending"),e.classList.add("device-preload-ready")})}catch(e){}}()</script><script data-n-head="ssr" src="https://cloud.umami.is/script.js" data-website-id="38e73ff2-ec10-4a8f-bfe2-c22a381ce306" defer></script><script data-n-head="ssr" src="/script/ga.js"></script><script data-n-head="ssr" src="/script/global.js"></script><script data-n-head="ssr" src="/public/esp-web-tools/install-button.js?module" type="module"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/marked.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/highlight.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-chat/index.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-qa/index.js"></script><link rel="preload" href="/_nuxt/41d5c62.js" as="script"><link rel="preload" href="/_nuxt/5a34d22.js" as="script"><link rel="preload" href="/_nuxt/a352c6d.js" as="script"><link rel="preload" href="/_nuxt/b9c4bc6.js" as="script"><link rel="preload" href="/_nuxt/c970150.js" as="script"><style data-vue-ssr-id="0b40e9c2:0 afa51714:0 73039f54:0 2576b79a:0 69f1b16c:0 17a511fe:0 3d88442c:0 3afe6180:0 786f8504:0 1af4924a:0 e762b0ec:0 e646c77c:0 4a658548:0 5f76b520:0 3e555512:0 4e0caf6f:0 060bbeb3:0 3ddd7ff2:0 bb0e6f22:0 27d15a7c:0 2c0daf93:0 d1c8934a:0 09fcdd3b:0 3231c87d:0 8716e91a:0 09d04477:0">body,html{width:100%;margin:0;padding:0}html.device-preload-mobile.device-preload-pending{background:linear-gradient(180deg,#f7f9fc,#eef3f8)}html.device-preload-mobile.device-preload-pending body{background:0 0}html.device-preload-mobile.device-preload-pending body:before{content:"";position:fixed;top:0;right:0;bottom:0;left:0;z-index:9999;pointer-events:none;background:linear-gradient(180deg,hsla(0,0%,100%,.92),rgba(243,247,251,.98)),radial-gradient(circle at top right,rgba(0,100,194,.08),transparent 38%)}html.device-preload-mobile.device-preload-pending body:after{content:"";position:fixed;left:50%;top:50%;width:.63529rem;height:.63529rem;margin-left:-.31765rem;margin-top:-.31765rem;z-index:10000;pointer-events:none;border:.04706rem solid rgba(35,141,251,.18);border-top-color:#238dfb;border-radius:50%;box-shadow:0 0 0 .09412rem rgba(35,141,251,.08);-webkit-animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite;animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite}html.device-preload-mobile.device-preload-pending .device-hydration-sensitive{opacity:0;visibility:hidden}html.device-preload-mobile.device-preload-ready body:after,html.device-preload-mobile.device-preload-ready body:before{opacity:0;transition:opacity .22s ease}html.device-preload-mobile.device-preload-ready .device-hydration-sensitive{visibility:visible;opacity:1;transition:opacity .18s ease}@-webkit-keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@-webkit-keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}@keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}html{overflow:hidden;overflow-y:auto}html::-webkit-scrollbar{width:.14118rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}@font-face{font-family:SourceCodePro;src:url(https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/font/SourceCodePro-Regular.ttf)}body,button{font-family:SourceCodePro,Microsoft YaHei;line-height:inherit;box-sizing:border-box}body,button,input{font-family:SourceCodePro,Microsoft YaHei,sans-serif}a{outline:0}.product_pic img{width:33%}.page-enter-active,.page-leave-active{transition:opacity .5s}.page-enter,.page-leave-active{opacity:0}.bounce-enter-active{-webkit-animation:bounce-in .8s;animation:bounce-in .8s}.bounce-leave-active{-webkit-animation:bounce-out .5s;animation:bounce-out .5s}@-webkit-keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@-webkit-keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}body,button,html[lang=zh-cn] footer,html[lang=zh-cn] header,input{font-family:Microsoft YaHei,sans-serif}html[lang=en] footer,html[lang=en] header{font-family:Montserrat,Microsoft YaHei,sans-serif}@font-face{font-family:Montserrat;font-weight:400;font-style:normal;src:url(/assets/fonts/Montserrat-Regular.woff2) format("woff2"),url(/assets/fonts/Montserrat-Regular.woff) format("woff"),url(/assets/fonts/Montserrat-Regular.otf) format("opentype"),url(/assets/fonts/Montserrat-Regular.ttf) format("truetype")}@font-face{font-family:Montserrat;font-weight:500;font-style:normal;src:url(/assets/fonts/Montserrat-Medium.woff2) format("woff2"),url(/assets/fonts/Montserrat-Medium.woff) format("woff"),url(/assets/fonts/Montserrat-Medium.otf) format("opentype"),url(/assets/fonts/Montserrat-Medium.ttf) format("truetype")}*{margin:0;padding:0;box-sizing:border-box}html{height:auto!important;font-size:10vw;line-height:1}@media screen and (max-width:320px){html{font-size:32PX}}@media screen and (min-width:540px){html{font-size:44PX}}@media screen and (min-width:860px){html{font-size:48PX}}@media screen and (min-width:960px){html{font-size:49PX}}@media screen and (min-width:1024px){html{font-size:52PX}}@media screen and (min-width:1175px){html{font-size:53PX}}@media screen and (min-width:1280px){html{font-size:56PX}}@media screen and (min-width:1366px){html{font-size:63PX}}@media screen and (min-width:1400px){html{font-size:68PX}}@media screen and (min-width:1440px){html{font-size:69PX}}@media screen and (min-width:1540px){html{font-size:73PX}}@media screen and (min-width:1680px){html{font-size:75PX}}@media screen and (min-width:1920px){html{font-size:75PX}}@media screen and (min-width:2560px){html{font-size:85PX}}body{-webkit-font-smoothing:subpixel-antialiased}li{list-style-type:none}img,li{-webkit-user-drag:none}img{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}a{text-decoration:none;-webkit-user-drag:none}a,button{outline:0}button{border:none;background-color:transparent;cursor:pointer}.fade-enter-active,.fade-leave-active{transition:opacity .5s}.fade-enter,.fade-leave-to{opacity:0}.markdown.guide img{box-shadow:0 -.07059rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);margin-top:.17647rem;margin-bottom:.58824rem;margin-left:.11765rem}.markdown.guide .blockly_svg{box-shadow:unset;margin:.17647rem 0 .05882rem;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content}.docs-layouts{padding-top:.58824rem;display:flex;justify-content:center;position:relative;margin-bottom:.35294rem}.docs-layouts .docs-layouts-sidebar{position:sticky;top:1.17647rem;left:0;height:-webkit-max-content;height:-moz-max-content;height:max-content;z-index:2;background-color:#fff}.docs-layouts .docs-layouts-title{display:flex;flex-direction:row;margin-bottom:.11765rem;align-items:center;width:100%;height:.47059rem;border-bottom:.03529rem solid #f5f5f5}.docs-layouts .docs-layouts-title .docs-layouts-icon{background-color:#238dfb;border-radius:.11765rem;display:flex;justify-content:center;align-items:center;height:.35294rem;width:.35294rem;margin-right:.11765rem}.docs-layouts .docs-layouts-title .docs-layouts-icon img{width:.23529rem;height:.23529rem}.docs-layouts .docs-layouts-title p{font-size:.23529rem;font-weight:700;color:#2f495e;line-height:.35294rem}.docs-layouts .docs-layouts-body{width:14.11765rem;min-width:0;max-width:100%;margin:0 .29412rem}.docs-layouts .docs-layouts-anchor{position:sticky;top:1.2rem;right:0;z-index:1;background-color:#fff;height:80vh;overflow-y:scroll}@media screen and (max-width:1200px){.docs-layouts .docs-layouts-anchor{display:none}}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar{width:.14118rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.mobile .docs-layouts{padding:.35294rem;display:flex}.mobile .docs-layouts .docs-layouts-body{width:100%;min-width:0;max-width:100%;margin:0}.mobile .docs-layouts .docs-layouts-sidebar{position:fixed;height:100vh;width:5.17647rem;top:0;padding:.47059rem .35294rem;left:auto;left:-100%;box-shadow:.11765rem .23529rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);transition:all .25s ease;z-index:5}.mobile .docs-layouts .docs-layouts-sidebar.active{left:0}.default{color:#3f3f46}.primary{color:#006fee}.secondary{color:#9353d3}.success{color:#17c964}.warning{color:#f5a524}.danger{color:#f31260}.markdown{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-column-gap:.18824rem;-moz-column-gap:.18824rem;column-gap:.18824rem;min-width:0;max-width:100%;overflow:hidden;word-break:break-word;padding-bottom:.35294rem;color:#4f5f6f;font-size:.18824rem;font-weight:400}.markdown>*{grid-column:1/-1}.markdown .product-sku{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .product-date,.markdown .product-sku{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.09412rem 0 .09412rem .09412rem;display:inline-block}.markdown .product-date{background-color:#efefef;color:#345b83}.markdown .tag-green{background-color:#f0fff4;color:#00c58e}.markdown .tag-blue,.markdown .tag-green{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.11765rem;display:inline-block}.markdown .tag-blue{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .tag-orange{font-size:.23529rem;margin:.23529rem .23529rem .23529rem 0;border-radius:.03529rem;padding:.02353rem .11765rem;background-color:#f8b013;color:#fff;cursor:pointer}.markdown .product-title{display:flex;align-items:center}.markdown .product-title span{color:#2f495e}.markdown .shop-title{display:flex;justify-content:space-between;position:relative;margin:.02353rem 0 0 .09412rem;background:#007bff;border-radius:.05882rem;color:#2f495e}.markdown .shop-title .shop-text{width:0;height:.47059rem;line-height:.47059rem;font-size:.2rem;text-align:center;color:#fff;overflow:hidden;transition:all .2s ease}.markdown .shop-title .shop-icon{position:relative;width:.47059rem;height:.47059rem;font-size:.35294rem;text-align:center;display:inline-block}.markdown .shop-title .shop-icon img{width:.35294rem;height:100%;display:inline-block}.markdown .shop-title .shop-icon:before{content:"";position:absolute;top:50%;right:-.32941rem;width:0;height:0;border-left:.23529rem solid transparent;border-right:.23529rem solid transparent;border-bottom:.23529rem solid #007bff;transform:translateY(-50%) rotate(90deg);display:none}.markdown .shop-title .shop-icon.eol:before{display:none}.markdown .shop-title:hover{color:#238dfb}.markdown .shop-title:hover .shop-text{width:2.35294rem}.markdown .shop-title:hover .shop-icon:before{display:block}.markdown .shop-title:hover .shop-icon.eol:before{display:none}.markdown .eol-title{display:flex;align-items:center;position:relative;margin:.02353rem 0 0 .08235rem;padding:0 .17647rem;height:.47059rem;line-height:.47059rem;background-color:#2f495e;border-radius:.05882rem}.markdown .eol-title .eol-text{font-size:.2rem;color:#fff}.markdown video{display:block;width:50%;margin-bottom:.35294rem}.markdown .video-iframe{margin:.23529rem 0;height:5.88235rem}.markdown .video-iframe iframe{width:50%;height:100%}.markdown .video-iframe>a{font-size:.23529rem;display:block;margin-bottom:.23529rem}.markdown a{color:#238dfb}.markdown h1{margin-top:.28235rem;margin-bottom:.21176rem;font-size:.54118rem;line-height:1.25}.markdown h1,.markdown h2{font-weight:600;color:#2f495e}.markdown h2{margin-top:.42353rem;margin-bottom:.18824rem;font-size:.35294rem;line-height:1.35;padding:0 .42353rem .11765rem .16471rem;position:relative;border-bottom:.01176rem solid #dfe5ec;cursor:pointer;transition:all .3s}.markdown h2:after{content:"";width:.03529rem;top:.04706rem;bottom:.16471rem;background:#238dfb;position:absolute;left:0}.markdown h2:before{content:"";position:absolute;background-image:url(/assets/link.svg);width:.29412rem;height:.29412rem;background-size:.29412rem;top:.08235rem;right:.05882rem;opacity:0;transition:opacity .3s}.markdown h2:hover{color:#0064c2}.markdown h2:hover:before{opacity:1}.markdown h3{margin-top:.32941rem;margin-bottom:.16471rem;font-size:.28235rem;color:#34495e;line-height:1.4}.markdown h3,.markdown h4{font-weight:600;position:relative}.markdown h4{margin-top:.28235rem;margin-bottom:.14118rem;font-size:.23529rem;color:#43566a;line-height:1.45}.markdown h5{margin-top:.23529rem;margin-bottom:.11765rem;font-size:.21176rem;font-weight:600;color:#526579;position:relative;line-height:1.5}.markdown ul{margin-bottom:.23529rem}.markdown ul ul{margin-bottom:.11765rem}.markdown ul li{list-style-type:circle;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f}.markdown ol{margin-bottom:.23529rem}.markdown ol li{list-style-type:decimal;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f;padding-left:.05882rem}.markdown ol li::marker{color:#6f6f6f;font-weight:700}.markdown code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;position:relative;color:#263445;font-size:.18824rem}.markdown :not(pre)>code{padding:.02353rem .05882rem;color:#165f8f;background:#eef3f7;border:.01176rem solid #dfe5ec;border-radius:.04706rem;font-size:.92em;font-weight:500}.markdown p{color:#4f5f6f;font-size:.18824rem;font-weight:400;line-height:.31765rem;margin-bottom:.16471rem}.markdown mark{background-color:#ffe051;color:#000}.markdown img{margin-bottom:.35294rem}.markdown>img:not([width]):not([class]){max-width:100%}.markdown .hljs{margin:.05882rem 0 .35294rem;font-size:.18824rem;line-height:.32941rem;white-space:pre;padding:.23529rem .29412rem;overflow-x:auto;overflow-y:hidden;border-radius:.07059rem;background-color:transparent;font-family:SourceCodePro,Microsoft YaHei;width:100%}.markdown .language-bash,.markdown .language-cpp,.markdown .language-diff,.markdown .language-dts,.markdown .language-json,.markdown .language-python,.markdown .language-shell{margin:0;font-size:.18824rem;line-height:.32941rem;white-space:pre;overflow-x:auto;overflow-y:hidden;background-color:transparent;display:block;width:100%}.markdown table thead,.markdown table tr{border-top:.01176rem solid #aabfdc}.markdown .normal-blockquote{box-shadow:-.05882rem 0 0 0 #238dfb;background-color:#fbfcfe;padding:.23529rem;margin:.17647rem 0 .17647rem .05882rem}.markdown .normal-blockquote p{font-weight:500;margin:0}.markdown .table-container{display:block;width:100%;min-width:0;max-width:100%;overflow-x:auto;overflow-y:hidden;overscroll-behavior-inline:contain;-webkit-overflow-scrolling:touch}.markdown table{border:none;display:table;min-width:100%;overflow:auto;margin:.11765rem 0 .35294rem}.markdown table thead{height:.58824rem;background:linear-gradient(-90deg,#1186de,#0064c2)}.markdown table thead tr{line-height:.58824rem;font-size:.18824rem;font-weight:700;color:#fff}.markdown table thead tr th{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr{line-height:.58824rem;font-size:.18824rem;color:#7d7d7d}.markdown table tbody tr td{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr:nth-child(odd){background-color:#fbfcfe}.markdown table tbody tr:nth-child(2n){background-color:#edf4fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table{border:.01176rem solid #e6ebf2;border-collapse:separate;border-spacing:0;border-radius:.07059rem;overflow:hidden;box-shadow:none}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead{height:auto;background:#1f6fe5}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr{border:0;line-height:1.4;font-size:.17647rem;font-weight:600;color:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr th{padding:.10588rem .17647rem;border:0;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr{border:0;line-height:1.5;color:#2c2f36}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td{padding:.10588rem .17647rem;border:0;border-right:.01176rem solid #e6ebf2;border-bottom:.01176rem solid #e6ebf2;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td:last-child{border-right:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(odd){background:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(2n){background:#f7f9fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:last-child td{border-bottom:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:hover{background:#eef3ff}.markdown .compare-table-container .table-container table thead{background:#fff!important}.markdown .compare-table-container .table-container table thead th{color:#2f495e;text-align:center!important;vertical-align:bottom}.markdown .compare-table-container .table-container table thead th a{align-items:center}.markdown .compare-table-container .table-container table thead th img{display:block;width:1.76471rem;height:1.76471rem;-o-object-fit:contain;object-fit:contain;margin:0 auto .35294rem}.markdown .compare-table-container .table-container table thead th:first-child{text-align:center!important;vertical-align:middle}.markdown .compare-table-container .table-container table tbody td:first-child,.markdown .compare-table-container .table-container table tbody td:not(:first-child){text-align:center!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(odd):hover{background:#fff!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(2n):hover{background:#f7f9fc!important}.markdown .table-text-align-left table td,.markdown .table-text-align-left table th{text-align:left}.markdown .table-text-align-right table td,.markdown .table-text-align-right table th{text-align:right}.markdown .markdown-ol li{list-style-type:decimal}.markdown .error,.markdown .tip,.markdown .warn{font-size:.21176rem;border-bottom-right-radius:.02353rem;margin:.11765rem .11765rem .11765rem 0;position:relative;background-color:#fff;box-shadow:.02353rem 0 .08235rem .01176rem #efefef;display:flex;flex-direction:column;color:#838383;font-size:.18824rem;font-weight:400;line-height:.37647rem;border-radius:.07059rem;overflow:hidden}.markdown .error .error-content,.markdown .error .tip-content,.markdown .error .warn-content,.markdown .tip .error-content,.markdown .tip .tip-content,.markdown .tip .warn-content,.markdown .warn .error-content,.markdown .warn .tip-content,.markdown .warn .warn-content{padding:.23529rem}.markdown .error .tip-title,.markdown .tip .tip-title,.markdown .warn .tip-title{height:.41176rem;background-color:rgba(35,141,251,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#238dfb}.markdown .error .warn-title,.markdown .tip .warn-title,.markdown .warn .warn-title{height:.41176rem;background-color:rgba(253,184,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#c69000}.markdown .error .error-title,.markdown .tip .error-title,.markdown .warn .error-title{height:.41176rem;background-color:rgba(253,45,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#ff1616}.markdown .tip:before{background-image:url(/assets/tip.svg)}.markdown .tip:before,.markdown .warn:before{content:"";position:absolute;width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .warn:before{background-image:url(/assets/warning.svg)}.markdown .error:before{content:"";position:absolute;background-image:url(/assets/error.svg);width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .tip{border-left:.07059rem solid #238dfb}.markdown .warn{border-left:.07059rem solid #fdb802}.markdown .error{border-left:.07059rem solid rgba(253,2,2,.83922)}.markdown .learn{display:flex;grid-column:auto;width:100%;height:2.07059rem;margin:.09412rem 0;overflow:hidden;background:#fff;border:.01176rem solid #d3dde9;border-radius:.07059rem;transition:border-color .2s ease,box-shadow .2s ease,transform .2s ease}.markdown .learn:hover{border-color:#8ab4eb;box-shadow:0 .04706rem .14118rem rgba(31,111,229,.1);transform:translateY(-.01176rem)}.markdown .learn:hover .learn-contents{background:#f6f9fe}.markdown .learn .learn-img{flex:0 0 42%;min-height:0;position:relative;overflow:hidden;text-align:center;background:#f7f9fc;border-right:.01176rem solid #e6ebf2}.markdown .learn .learn-img img{display:block;width:100%;max-width:none;box-shadow:none;margin:0;height:100%;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;font-size:.09412rem}.markdown .learn .learn-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.markdown .learn .learn-contents{flex:1;min-width:0;padding:.23529rem;position:relative;display:flex;flex-direction:column;justify-content:center;background:#fbfcfe;transition:background-color .2s ease}.markdown .learn .learn-contents .learn-title{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:2;font-size:.21176rem;font-weight:600;line-height:.29412rem}.markdown .learn .learn-contents .learn-title a{color:#1f6fe5}.markdown .learn .learn-contents .learn-desc{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:3;margin-top:.09412rem;font-size:.18824rem;font-weight:400;color:#5d6673;line-height:.28235rem}.markdown .learn [\:not-has\(\%2B.learn\)]{grid-column:1/-1}.markdown .learn :not(:has(+.learn)){grid-column:1/-1}.markdown .learn [\:not-has\(\%2B.learn\)] .learn-img{flex-basis:2.82353rem}.markdown .learn :not(:has(+.learn)) .learn-img{flex-basis:2.82353rem}.mobile .markdown{grid-template-columns:minmax(0,1fr)}.mobile .markdown p{font-size:.21176rem}.mobile .markdown .learn{flex-direction:row;height:1.88235rem;max-width:none}.mobile .markdown .learn .learn-img{flex:0 0 40%;width:auto;min-height:0;aspect-ratio:auto;border-right:.01176rem solid #e6ebf2;border-bottom:0}.mobile .markdown .learn .learn-contents{padding:.14118rem .16471rem}.mobile .markdown .learn .learn-contents .learn-title{font-size:.18824rem;line-height:.25882rem;-webkit-line-clamp:2}.mobile .markdown .learn .learn-contents .learn-desc{margin-top:.07059rem;font-size:.16471rem;line-height:.24706rem;-webkit-line-clamp:3}@media screen and (max-width:900px){.markdown{grid-template-columns:minmax(0,1fr)}.markdown .learn .learn-img{flex-basis:2.82353rem}}.mobile video{width:100%;margin-bottom:.35294rem}.mobile .video-iframe{margin:.23529rem 0;height:5.88235rem}.mobile .video-iframe iframe{width:100%;height:100%}.easyloader-box{display:flex;flex-direction:row;width:100%}.easyloader-box>div{position:relative;width:50%;overflow:hidden}.easyloader-box p{margin:.11765rem .29412rem;color:#fff}.easyloader-box p:last-child{overflow-y:scroll;height:20%;font-size:.11765rem}.easyloader-mask{position:absolute;right:0;bottom:.07059rem;height:100%;width:100%;background-color:#000;opacity:.7;transition:all .3s;display:flex;flex-direction:column;justify-content:center;display:none}.easyloader-mask a{margin-top:.58824rem;text-align:center}.video_play{bottom:-100%}.easyloader-btn{position:absolute;display:flex;flex-direction:row;justify-content:space-around;bottom:7%;width:100%;padding:0 .23529rem;font-size:.23529rem}.easyloader-btn a{width:1.05882rem;text-align:center;padding:.02353rem .11765rem;background-color:#007bff;color:#fff!important;border-radius:.11765rem;font-size:.17647rem}.easyloader-btn a:hover{background-color:#45a9ff}@media screen and (max-width:768px){.easyloader-box{flex-direction:column;width:100%}.easyloader-box>div{width:100%}}.code-block-wrapper{display:flex;flex-direction:column;position:relative;margin:.16471rem 0 .23529rem;border:.01176rem solid #dfe5ec;border-radius:.07059rem;overflow:hidden;background:#f7f9fb}.code-block-header{display:flex;justify-content:space-between;align-items:center;min-height:.44706rem;padding:.04706rem .14118rem;background:#f0f3f6;border-bottom:.01176rem solid #dfe5ec}.code-block-header .language-label{font-size:.15294rem;color:#526579;font-weight:500}.copy-all-btn{display:flex;align-items:center;grid-gap:.11765rem;gap:.11765rem;justify-content:center;background:0 0;border:none;border-radius:.05882rem;padding:.07059rem;font-size:.16471rem;cursor:pointer;transition:all .2s;width:.37647rem;height:.37647rem;color:#526579}.copy-all-btn svg{width:100%;height:100%}.copy-all-btn code{display:none}.copy-all-btn:hover{color:#1769aa;background:#e4ebf2}.copy-all-btn.focus-visible,.copy-all-btn:focus-visible{color:#1769aa;background:#e4ebf2;outline:.02353rem solid #1769aa;outline-offset:.02353rem}.code-block-container{display:flex;overflow:auto;background:#f7f9fb;align-items:flex-start}.code-block-wrapper.code-block-limited .code-block-container,.code-block-wrapper.code-block-limited .code-line-container{max-height:560px;max-height:var(--code-max-height,560px);overflow:auto;transition:max-height .35s ease}.code-block-wrapper:not(.is-collapsed).code-block-limited .code-block-container,.code-block-wrapper:not(.is-collapsed).code-block-limited .code-line-container{max-height:16.47059rem}.code-toggle-btn{display:flex;align-items:center;justify-content:center;width:100%;min-height:.49412rem;padding:.09412rem .14118rem .11765rem;border:0;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(240,244,249,.96));color:#6b7f93;cursor:pointer;transition:background .2s ease,color .2s ease;position:relative;z-index:2}.code-toggle-btn.focus-visible,.code-toggle-btn:focus-visible,.code-toggle-btn:hover{outline:0;color:#2d7be9;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(228,238,248,.98))}.code-toggle-icon{font-size:.17647rem;line-height:1;transition:transform .25s ease,color .2s ease}.code-block-wrapper:not(.is-collapsed) .code-toggle-icon,.code-toggle-icon{transform:translateY(-.01176rem)}.code-block-fade{position:absolute;left:0;right:0;bottom:.49412rem;height:1.29412rem;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(247,249,251,.96));pointer-events:none;transition:opacity .2s ease;z-index:1}.code-block-wrapper.is-collapsed .code-block-fade{opacity:1}.code-block-wrapper:not(.is-collapsed) .code-block-fade{opacity:0}.markdown .code-block-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-block-container code.hljs{margin:0!important;padding:0!important;border-radius:0;background:0 0;line-height:.32941rem;font-size:.18824rem;white-space:pre}.markdown .code-line-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-line-container code.hljs{margin:0!important;padding:0!important;line-height:.32941rem;font-size:.18824rem;white-space:pre;width:100%;border-radius:0;background-color:transparent}.code-line-container{display:flex;background:#f7f9fb;align-items:center;position:relative;padding:.18824rem .21176rem}.code-line-container .copy-all-btn{opacity:.45;position:absolute;top:.11765rem;right:.11765rem;transition:all .2s}.code-line-container pre{overflow-x:auto}.code-line-container:hover .copy-all-btn,.code-line-container[focus-within] .copy-all-btn{opacity:1}.code-line-container:focus-within .copy-all-btn,.code-line-container:hover .copy-all-btn{opacity:1}@media (hover:none){.code-line-container .copy-all-btn{opacity:1}.markdown .learn:hover{border-color:#d3dde9;box-shadow:none;transform:none}.markdown .learn:hover .learn-contents{background:#fbfcfe}}.line-numbers{padding:.11765rem .09412rem;text-align:right;background:#f3f6f9;color:#8491a0;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;border-right:.01176rem solid #dfe5ec;font-family:SourceCodePro,Microsoft YaHei,sans-serif;line-height:.32941rem;min-width:.51765rem}.line-number{display:block;height:.32941rem}.code-content{flex:1;overflow:auto;padding:.11765rem .17647rem;line-height:.32941rem}.code-block-container,.code-content,.code-line-container pre{scrollbar-color:#c5cfda transparent;scrollbar-width:thin}.code-block-container::-webkit-scrollbar,.code-content::-webkit-scrollbar,.code-line-container pre::-webkit-scrollbar{width:.09412rem;height:.09412rem}.code-block-container::-webkit-scrollbar-thumb,.code-content::-webkit-scrollbar-thumb,.code-line-container pre::-webkit-scrollbar-thumb{background:#c5cfda;border-radius:.04706rem}.code-block-container::-webkit-scrollbar-track,.code-content::-webkit-scrollbar-track,.code-line-container pre::-webkit-scrollbar-track{background:0 0}.code-line{display:block;min-height:.32941rem;line-height:.32941rem;white-space:pre;font-weight:700;font-family:SourceCodePro,Microsoft YaHei,sans-serif}.code-line:hover{background-color:#eaf1f7;cursor:pointer}pre code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;font-size:.18824rem;overflow-y:auto;font-family:SourceCodePro;display:block;width:100%;color:#263445;line-height:.32941rem}code.hljs{background:0 0}pre{position:relative}pre .copy-btn{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;opacity:0;position:absolute;right:.05882rem;top:.05882rem;cursor:pointer;padding:.05882rem;border-radius:.03529rem;transition:.3s;background:hsla(0,0%,100%,.2);width:1.52941rem;height:.58824rem;color:#0064c2}pre .copy-btn:active{background:hsla(0,0%,99.2%,.575)}pre .copy-btn .icon{width:.35294rem;position:absolute;left:70%;top:70%;transform:translate(-50%,-50%)}pre .copy-success-text{color:#fff;position:absolute;font-size:.14118rem;top:.70588rem;font-weight:200;font-family:SourceCodePro,Microsoft YaHei;-webkit-animation:successCopy .5s ease 1 both;animation:successCopy .5s ease 1 both;color:#0064c2}@-webkit-keyframes successCopy{0%{right:0}to{right:.29412rem}}@keyframes successCopy{0%{right:0}to{right:.29412rem}}pre:hover .copy-btn{opacity:1}.files_download{display:flex;flex-direction:row;justify-content:space-evenly;flex-wrap:wrap;margin:.52941rem}.files_download .item{display:flex;justify-content:center;width:2.35294rem;box-shadow:.04706rem .04706rem .08235rem 0 #cecece;transition:all .25s ease}.files_download .item:hover{transform:scale(1.2)}.card-container{display:flex;justify-content:flex-start;margin-bottom:.35294rem;align-items:flex-start}.card-container .card-item{margin:.23529rem;width:3.52941rem;display:flex;flex-direction:column;justify-content:center;align-items:center;color:#fff;transition:all .25s ease}.card-container .card-item .card-cover{height:1.76471rem;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1)}.card-container .card-item .card-cover,.card-container .card-item .card-cover-img{width:100%;display:flex;align-items:center;justify-content:center;font-size:.28235rem;font-weight:700;margin-bottom:.11765rem;border-radius:.11765rem}.card-container .card-item .card-cover-img{position:relative}.card-container .card-item .card-cover-img .card-cover-content{display:none;padding:.11765rem}.card-container .card-item .card-cover-img .card-cover-content .card-cover-btn{display:block;text-align:center;background-color:#0064c2;color:#fff;font-size:.2rem;padding:.11765rem .17647rem;border-radius:.04706rem}.card-container .card-item .card-cover-img img{width:100%;box-shadow:none;margin:0}.card-container .card-item .card-cover-img:hover .card-cover-content{display:flex;flex-direction:column;justify-content:space-around;align-items:center;position:absolute;top:0;left:0;bottom:0;right:0;background-color:rgba(0,0,0,.5098)}.card-container .card-item .card-desc{padding:.17647rem;text-align:center;font-size:.17647rem;color:#2f495e}.card-container .card-item .card-desc a{display:block;text-align:left;color:#333;line-height:.23529rem}.card-container .card-item .card-desc a:hover{text-decoration:underline;color:#238dfb}.card-container .card-item:hover{transform:translateY(-.05882rem)}.card-container .linear-blue{background:linear-gradient(45deg,#09f,#6cf)}.card-container .linear-gray{background:linear-gradient(45deg,#f2f2f2,#ccc);color:#333}.card-container .linear-orange{background:linear-gradient(45deg,#fc0,#f90)}.card-container-video{display:flex;flex-wrap:wrap;grid-gap:.23529rem;gap:.23529rem;margin:.47059rem 0}.card-container-video li{list-style-type:none}.card-container-video .card-item-video{width:22%;position:relative;border-radius:.07059rem;overflow:hidden;transition:transform .3s ease;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1);background-color:#fff}.card-container-video .card-item-video:hover{transform:translateY(-.05882rem);box-shadow:0 .09412rem .18824rem rgba(0,0,0,.15)}.card-container-video .card-item-video:hover .card-cover-content{opacity:1}.card-container-video .card-item-video .card-cover-img{position:relative;width:100%;padding-top:56.25%;background-color:#e7e7e7;overflow:hidden}.card-container-video .card-item-video .card-cover-img img{position:absolute;top:50%;left:50%;width:100%;height:100%;-o-object-fit:cover;object-fit:cover;transform:translate(-50%,-50%);min-width:100%;min-height:100%;transition:transform .3s ease;margin:0}.card-container-video .card-item-video .card-desc-video{padding:.11765rem;text-align:center;font-weight:700}.card-container-video .card-item-video .card-cover-content{position:absolute;top:0;left:0;width:100%;height:100%;display:flex;justify-content:center;align-items:center;background-color:rgba(0,0,0,.5);opacity:0;transition:opacity .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn{display:inline-block;padding:.09412rem .18824rem;margin:0 .11765rem;background-color:#fb7299;color:#fff;border-radius:.04706rem;text-decoration:none;font-size:.16471rem;transition:background-color .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn.youtube{background-color:#f03}.card-container-video .card-item-video .card-cover-content .card-cover-btn.bilibili{background-color:#ff85ad}.mobile .card-item-video{width:40%}.mobile .card-desc-video{font-size:.29412rem}.directory-links-container{display:flex;flex-direction:column}.directory-links-item{page-break-inside:avoid;-moz-column-break-inside:avoid;break-inside:avoid;margin:.11765rem;padding:.17647rem;border-radius:.05882rem;box-shadow:0 0 .05882rem rgba(0,0,0,.1)}.directory-links-body{display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(3.52941rem,1fr));position:relative}.directory-links-item h3{margin-top:0;margin-bottom:.11765rem}.directory-links-item ul{list-style-type:none;padding:0;margin:.18824rem .11765rem}.directory-links-item ul li{margin-bottom:.05882rem}.directory-links-item ul li a{text-decoration:none;color:#333}.directory-links-item ul li a:hover{text-decoration:underline;color:#238dfb}.header-nav .dropdown-icon-wrapper,.pc .nav-dropdown .dropdown-content-right,.pc .nav-dropdown .dropdown-image .image-button{display:flex;justify-content:center;align-items:center}.pc .header-nav-ul .header-nav-item a:hover{color:#0064c2}.mobile .mobile-nav-icon,.mobile .mobile-return-icon{background-repeat:no-repeat;background-size:100% 100%}header{width:100%;position:relative;background-color:#fff;border-bottom:.01176rem solid #e5e5e5;overflow:visible}.header-container{position:relative;margin:0 auto;padding:0 1.17647rem 0 0;width:15.64706rem;height:.70588rem;display:flex;align-items:center;justify-content:flex-end;font-size:.25882rem}.header-container .logo{position:absolute;left:.08235rem;display:block;width:2.08235rem;height:.41176rem;font-size:0;line-height:1;cursor:pointer}.header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.header-nav .dropdown-icon-wrapper{margin-right:.18824rem;width:.25882rem;height:.25882rem}.header-nav .dropdown-icon-wrapper .dropdown-icon{width:auto;height:auto;max-width:100%;max-height:100%;font-size:0}.language-option-box{position:absolute;height:.70588rem;right:-.65882rem;font-size:0;background-color:#fff}.language-option-box .icon{margin-right:.07059rem;width:.2rem;height:auto;color:#434343}.language-option-box .current-language{height:calc(100% - .02353rem);color:#434343;font-size:.22353rem;font-weight:700;display:flex;align-items:center;cursor:pointer;box-sizing:content-box}.language-option-box .language-dropdown-wrapper{display:none;position:fixed;top:.70588rem;padding-top:.11765rem;box-sizing:border-box;width:19.76471rem;left:50%;transform:translateX(-50%);z-index:99999}.language-option-box .language-dropdown-wrapper .language-dropdown{position:absolute;top:.11765rem;right:1.29412rem;width:1.52941rem;color:#434343;background-color:#fff;border-radius:.11765rem;overflow:hidden;box-shadow:0 .09412rem .28235rem rgba(0,0,0,.08);opacity:0;transition:opacity .2s ease}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item{font-size:.21176rem;font-weight:700;line-height:.54118rem;text-align:center;cursor:pointer}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item:hover{color:#0064c2}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item.active{background-color:#dedede}.language-option-box:hover .current-language{border-bottom:.03529rem solid #0064c2}.language-option-box:hover .current-language .header-arrow-btn{transform:rotate(-180deg)}.language-option-box:hover .language-dropdown-wrapper{display:block}.language-option-box:hover .language-dropdown{opacity:1}.disabledHover{cursor:auto!important}.disabledHover a:hover,.disabledHover li:hover,.disabledHover:hover{color:#434343!important}.pc .show-mb{display:none}.pc .header-nav{height:100%;display:flex;align-items:center}.pc .header-nav-ul{height:100%;display:flex;flex-direction:row}.pc .header-nav-ul .header-nav-item{margin-right:.30588rem;padding-left:.23529rem;height:calc(100% - .02353rem);display:flex;align-items:center;font-size:.22353rem;font-weight:700;color:#434343;cursor:pointer;box-sizing:content-box}.pc .header-nav-ul .header-nav-item.active,.pc .header-nav-ul .header-nav-item:hover{border-bottom:.03529rem solid #0064c2}.pc .header-nav-ul .header-nav-item.active .header-arrow-btn,.pc .header-nav-ul .header-nav-item:hover .header-arrow-btn{transform:rotate(-180deg)}.pc .header-nav-ul .header-nav-item:last-of-type{margin-right:0}.pc .header-nav-ul .header-nav-item a{position:relative;color:#434343}.pc .header-arrow-btn{margin-left:.07059rem;width:.11765rem;height:auto;color:#3a3a3a;font-size:0;transition:all .3s ease}.pc .nav-dropdown{position:fixed;left:50%;width:16.70588rem;max-width:calc(100vw - .47059rem);height:3.52941rem;display:flex;transform:translateX(-50%);background-color:#fff;border-radius:.23529rem;z-index:9999}.pc .nav-dropdown .dropdown-content-left{position:relative;padding:.47059rem .32941rem 0;width:calc(100% - 7.45882rem);height:100%;display:flex;justify-content:space-around}.pc .nav-dropdown .dropdown-content-right{width:7.45882rem;height:100%;background-color:#eee;border-radius:0 .23529rem .23529rem 0}.pc .nav-dropdown .dropdown-image{position:relative;width:7.05882rem;border-radius:.23529rem;font-size:0;overflow:hidden}.pc .nav-dropdown .dropdown-image img{width:100%;height:auto}.pc .nav-dropdown .dropdown-image .image-button{position:absolute;left:50%;bottom:.35294rem;transform:translateX(-50%);width:2.35294rem;height:.42353rem;font-size:.18824rem;color:#fff;background-color:#0064c2;border-radius:.04706rem}.pc .nav-dropdown .dropdown-image .image-button:hover{background-color:#058ce6}.pc .nav-dropdown .dropdown-image .image-button .image-icon{margin-right:.11765rem;width:.24706rem;height:auto}.pc .nav-dropdown .dropdown-item{width:3.29412rem;display:flex;flex-direction:column;flex-wrap:wrap}.pc .nav-dropdown .dropdown-item-li{padding-left:.16471rem;display:flex;align-items:center;font-size:.23529rem;font-weight:700;line-height:.70588rem;color:#434343}.pc .nav-dropdown .dropdown-item-li.border{border-bottom:.02353rem solid #dbdbdb}.pc .nav-dropdown .dropdown-item-li:hover{color:#0064c2}.pc .nav-dropdown .dropdown-item-child{margin-top:.18824rem;padding-left:.18824rem;display:flex;flex-direction:column}.pc .nav-dropdown .dropdown-child-li{margin-bottom:.14118rem;display:flex;align-items:center;font-size:.21176rem;font-weight:500;white-space:nowrap;color:#434343}.pc .nav-dropdown .dropdown-child-li:hover{color:#0064c2}.pc header #store{height:4.70588rem}.pc header #store .dropdown-item:first-child{width:2.21176rem}.pc header #store .dropdown-item:first-child .dropdown-child-li:nth-child(2) .dropdown-icon-wrapper{height:.32941rem}.pc header #store .dropdown-item:nth-child(2){width:4.65882rem;height:3.05882rem;border-bottom:.02353rem solid #dbdbdb}.pc header #store .dropdown-item:nth-child(2) .dropdown-item-child{width:90%;height:2rem;flex-wrap:wrap}.pc header #store .dropdown-item:nth-child(3),.pc header #store .dropdown-item:nth-child(4){position:absolute;bottom:.47059rem}.pc header #store .dropdown-item:nth-child(3){right:3.38824rem;width:2.04706rem}.pc header #store .dropdown-item:nth-child(3) .dropdown-icon-wrapper{margin-right:.14118rem;width:.32941rem}.pc header #store .dropdown-item:nth-child(4){right:.75294rem;width:2.58824rem}.pc header #software{height:4rem}.pc header #software .dropdown-content-left{width:calc(100% - 6.03529rem)}.pc header #software .dropdown-content-right{width:6.03529rem}.pc header #software .dropdown-image{width:5.58824rem}.pc header #software .dropdown-item:first-child{width:3.17647rem}.pc header #software .dropdown-item:nth-child(2){width:2.82353rem}.pc header #software .dropdown-item:nth-child(3){width:2.91765rem}.pc header #document{height:4.47059rem}.pc header #document .dropdown-content-left{width:100%}.pc header #document .dropdown-item:first-child .dropdown-item-child,.pc header #document .dropdown-item:nth-child(2) .dropdown-item-child{height:2rem;flex-wrap:wrap}.pc header #document .dropdown-item:first-child{width:4.65882rem}.pc header #document .dropdown-item:nth-child(2){width:5.01176rem}.pc header #document .dropdown-item:nth-child(3){width:3.76471rem}.pc header #aboutus{height:4.21176rem}.pc header #contact{height:1.05882rem;background-color:transparent}.pc header #contact .dropdown-content-left{position:absolute;padding:.09412rem 0;right:1.29412rem;width:2rem;height:1.05882rem;flex-direction:column;background-color:#fff;border-radius:.11765rem}.pc header #contact .dropdown-item{width:100%}.pc header #contact .dropdown-item .dropdown-item-li{padding-left:0;width:100%;justify-content:center;font-size:.21176rem;line-height:.42353rem}.mobile .show-pc,.mobile .snize-sticky-searchbox{display:none}.mobile header{height:1.10588rem;border-bottom:unset}.mobile .header-container{padding:0 .35294rem;width:100%;max-width:100%;height:1.10588rem;justify-content:unset;z-index:9999;box-shadow:0 0 .18824rem 0 hsla(0,0%,51.4%,.15)}.mobile .header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.mobile .mobile-nav-icon{width:.54118rem;height:.54118rem;background-image:url(/assets/menu.png);transition:all .28s ease}.mobile .mobile-nav-icon.active{transform:rotate(90deg)}.mobile .mobile-return-icon{position:absolute;left:1.2rem;width:.32941rem;height:.32941rem;background-image:url(/assets/return.png)}.mobile .logo{left:50%;width:2.47059rem;height:.48235rem;transform:translateX(-50%)}.mobile .header-nav{display:none;position:absolute;top:1.10588rem;left:0;padding:.18824rem 0 1.01176rem;width:5.17647rem;max-width:100%;background-color:#fff;z-index:9998}.mobile .header-nav.show{display:block}.mobile .header-nav-ul{margin-bottom:.23529rem}.mobile .header-nav-ul .header-nav-item{position:relative;padding-left:.47059rem;height:1.10588rem;font-size:.36471rem;font-weight:400;line-height:1.10588rem}.mobile .header-nav-ul .header-nav-item,.mobile .header-nav-ul .header-nav-item a{color:#434343}.mobile .header-nav-ul .header-nav-item.selected{background-color:#f7f7f7}.mobile .header-nav-ul .header-nav-item.active .header-mbnav-btn{transform:rotate(90deg)}.mobile .header-nav-ul .header-nav-item.active+.nav-dropdown{display:block}.mobile .header-mbnav-btn{position:absolute;width:.58824rem;height:.58824rem;top:.23529rem;right:.23529rem;background-image:url(/assets/arrow3.png);background-repeat:no-repeat;background-size:50% 50%;background-position:50%}.mobile .nav-dropdown{display:none;position:relative}.mobile .nav-dropdown .dropdown-content-left{width:100%}.mobile .nav-dropdown .dropdown-icon-wrapper{width:.47059rem;height:.47059rem}.mobile .nav-dropdown .dropdown-item-li{padding-left:.71765rem;width:100%;height:.88235rem;display:flex;align-items:center;font-size:.32941rem;font-weight:400;color:#434343}.mobile .nav-dropdown .dropdown-child-li{padding-left:.89412rem;width:100%;height:.82353rem;display:flex;align-items:center;font-size:.30588rem;line-height:.82353rem;white-space:nowrap;color:#434343}.mobile .language-option-box{height:1.10588rem;right:.25882rem}.mobile .language-option-box .icon{width:.35294rem}.mobile .language-option-box .current-language{font-size:.30588rem;font-weight:500}.mobile .language-option-box .language-dropdown-wrapper{width:100%;top:1.10588rem;padding-top:.11765rem;box-sizing:border-box}.mobile .language-option-box .language-dropdown{right:.11765rem;width:2.23529rem}.mobile .language-option-box .language-dropdown .language-item{font-size:.35294rem;font-weight:500;line-height:.70588rem}.header-nav-dd-pc-enter-active,.header-nav-dd-pc-leave-active{transition:opacity .2s ease-out,transform .22s cubic-bezier(.4,0,.2,1)}.header-nav-dd-pc-enter,.header-nav-dd-pc-leave-to{opacity:0;transform:translateX(-50%) translateY(-.09412rem)!important}.header-nav-dd-pc-enter-to,.header-nav-dd-pc-leave{opacity:1;transform:translateX(-50%) translateY(0)!important}.header-nav-dd-mb-enter-active,.header-nav-dd-mb-leave-active{transition:opacity .18s ease-out}.header-nav-dd-mb-enter,.header-nav-dd-mb-leave-to{opacity:0}.viewer-open .mobile .header-container,.viewer-open .mobile .language-dropdown-wrapper,.viewer-open .mobile .language-option-box{z-index:1!important}.viewer-open .mobile .language-option-box{pointer-events:none}.title-level2{height:.32941rem;font-size:.35294rem;font-weight:400;color:#434343;line-height:.32941rem;padding-left:.22353rem;position:relative;display:flex;justify-content:space-between;margin:.58824rem 0}.title-level2 .title-level2-desc{font-size:.18824rem;font-weight:400}.title-level2:after{content:"";width:.04706rem;height:.35294rem;background:#0064c2;position:absolute;left:0}.title-level3{height:.27059rem;font-size:.29412rem;font-weight:400;color:#434343;line-height:.27059rem;padding-left:.14118rem;position:relative;display:flex;justify-content:space-between;margin:.47059rem 0 .35294rem}.title-level3 .title-level3-desc{font-size:.14118rem;font-weight:400}.pc .product-list-container .Products{display:flex;flex-wrap:wrap;margin-bottom:.70588rem}.pc .product-list-container .ProductItem{border-top:.01176rem solid #e5e5e5;border-bottom:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(2n),.pc .product-list-container .ProductItem:nth-child(2n-1){border-right:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(3n){border-right:0 solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(n+4){border-top:0 solid #e5e5e5}.pc .product-list-container .ProductItem{height:4.51765rem;width:4.65882rem;text-align:center;position:relative}.pc .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.pc .product-list-container .ProductItem .ProductPic{text-align:center;width:2.35294rem;height:2.35294rem}.pc .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.pc .product-list-container .ProductItem .ProductName{margin-top:.11765rem;line-height:.29412rem;height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343}.pc .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto .17647rem;width:2.47059rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.23529rem;text-overflow:clip;overflow:hidden}.pc .product-list-container .ProductItem .product-btn-group{width:1.76471rem;height:.35294rem;border-radius:.17647rem;margin:auto;display:flex}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.29412rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.35294rem;font-size:.18824rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.47059rem;height:.35294rem;background-size:.23529rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.pc .product-list-container .ProductLinks{padding:0 .17647rem;font-size:.18824rem;display:grid;justify-content:start;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(2.82353rem,1fr));position:relative;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink:hover{color:#409eff;-webkit-text-decoration-line:underline;text-decoration-line:underline}.mobile .product-list-container{text-align:left}.mobile .product-list-container .ProductItem{text-align:center;height:5.17647rem;width:50%;border:.02353rem solid #e5e5e5;background-color:#fff;position:relative}.mobile .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.mobile .product-list-container .ProductItem .ProductPic{margin:.11765rem auto;text-align:center;width:2.82353rem;height:2.82353rem}.mobile .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.mobile .product-list-container .ProductItem .ProductName{height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343;line-height:.28235rem}.mobile .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto;display:block;width:2.36471rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.25882rem;overflow:hidden}.mobile .product-list-container .ProductItem .product-btn-group{width:2.35294rem;height:.47059rem;border-radius:.17647rem;margin:auto;display:flex}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.64706rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.47059rem;font-size:.23529rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.70588rem;height:.47059rem;background-size:.29412rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.mobile .product-list-container .ProductLinks{padding:.11765rem .17647rem;font-size:.25882rem;display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fit,minmax(3.52941rem,1fr));position:relative;margin-bottom:.14118rem;background-color:#fff}.mobile .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.14118rem}.product-list-container.hideEol .ProductItem.EOL{display:none}.footer-email-input input::-webkit-input-placeholder{font-family:Microsoft YaHei,sans-serif}.subscribe-btn{display:flex;justify-content:center;align-items:center}.pc .footer-bottom-content a:hover,.pc .footer-nav-li a:hover{color:#0064c2}.subscribe-btn:hover{background-color:#0074e1}.mobile .footer-nav-btn{background-repeat:no-repeat;background-size:100% 100%}.footer-container{width:100%;color:#fff;background-color:#000}.footer-content-wrap{height:100%;display:flex;align-items:center}.footer-email-title,.footer-qrcode-title{font-size:.32941rem;margin-bottom:.21176rem;font-weight:500;color:#fff}.footer-email-desc{font-weight:400;color:#f1f1f1}.footer-email-input{display:flex}.footer-email-input input{background:hsla(0,0%,60%,.55);border:.01176rem solid #0077c8;border-radius:.04706rem;padding:0 .23529rem;color:#fff;outline:0}.footer-email-input input::-webkit-input-placeholder{font-weight:400;color:#a0a0a0}.subscribe-btn{background:#0077c8;width:1.55294rem;height:.56471rem;font-size:.21176rem;font-weight:500;color:#fff;border-radius:.07059rem}.footer-follow{margin-top:.42353rem;width:90%}.footer-follow-ul{display:flex;flex-wrap:wrap}.footer-info-wrapper{margin-top:.47059rem;font-size:.16471rem;color:#a0a0a0}.footer-email-warning{margin-top:.11765rem;display:none;font-size:.18824rem;color:#ff2529}.footer-email-success{margin-top:.35294rem;margin-bottom:1.15294rem;display:none;font-size:.35294rem;color:#fff}.pc .footer-container{height:8.23529rem}.pc .footer-content-wrap{width:15.64706rem;margin:0 auto}.pc .footer-nav{padding:.70588rem 0 .11765rem;width:65%;height:100%;display:flex;flex-direction:column;flex-wrap:wrap}.pc .footer-nav-item{margin:0 0 .47059rem}.pc .footer-nav-title{margin-bottom:.18824rem;font-size:.29412rem;font-weight:500;color:#fff}.pc .footer-nav-title a{color:#fff}.pc .footer-nav-li{font-size:.21176rem;font-weight:400;color:#a0a0a0;line-height:.38824rem}.pc .footer-nav-li a{color:#a0a0a0;cursor:pointer}.pc .footer-right{width:35%;height:5.95294rem;padding:0 0 0 .47059rem}.pc .footer-email-title,.pc .footer-qrcode-title{margin-top:.14118rem}.pc .footer-email-desc{font-size:.21176rem;line-height:.32941rem;margin-bottom:.14118rem}.pc .footer-email-input input{width:3.71765rem;height:.56471rem;font-size:.21176rem;margin-right:.12941rem}.pc .footer-email-input input::-webkit-input-placeholder{font-size:.21176rem}.pc .footer-qrcode-list{display:flex}.pc .footer-qrcode-list .footer-qrcode-item{margin-right:.11765rem}.pc .footer-qrcode-list .footer-qrcode-img{width:1.88235rem;height:auto}.pc .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.pc .footer-qrcode-list .footer-qrcode-name{font-size:.21176rem;color:#a0a0a0}.pc .footer-follow-ul{width:100%}.pc .footer-follow-ul a{display:block;margin-right:.11765rem;margin-bottom:.11765rem;font-size:0}.pc .footer-follow-ul img{width:.58824rem;height:.58824rem}.pc .footer-address-info{line-height:.23529rem;margin:.05882rem 0}.pc .footer-info{line-height:.32941rem}.pc .footer-bottom{width:100%;height:.77647rem;background-color:#000}.pc .footer-bottom-content{margin:0 auto;padding:.23529rem .23529rem 0;width:16.07059rem;height:100%;display:flex;justify-content:space-between;font-size:.15294rem;font-weight:400;color:#a0a0a0;border-top:.01176rem solid #6d6d6d}.pc .footer-bottom-content a{display:inline-block;color:#a0a0a0;font-weight:400;font-size:.15294rem}.pc .terms-box{margin-left:.54118rem;display:flex}.pc .terms-box a{margin:0 .09412rem}.mobile .footer-container{height:11.76471rem}.mobile .footer-right{padding:0;width:100%}.mobile .footer-email-group,.mobile .footer-right{display:flex;flex-direction:column;align-items:center}.mobile .footer-email-title,.mobile .footer-qrcode-title{font-size:.58824rem;margin-bottom:.25882rem}.mobile .footer-email-success{font-size:.51765rem;margin-top:1.17647rem;margin-bottom:1.27059rem}.mobile .footer-email-desc{width:5.52941rem;font-size:.35294rem;line-height:.47059rem;text-align:center;margin-bottom:.75294rem}.mobile .footer-email-input{flex-direction:column;align-items:center}.mobile .footer-email-input input{width:7.35294rem;height:.70588rem;margin-bottom:.47059rem;font-size:.32941rem}.mobile .footer-email-input input::-webkit-input-placeholder{font-size:.32941rem}.mobile .subscribe-btn{width:2.75294rem;height:.70588rem;border-radius:.07059rem;font-size:.32941rem}.mobile .footer-email-warning{font-size:.29412rem;margin-top:.18824rem}.mobile .footer-qrcode-title{text-align:center}.mobile .footer-qrcode-list{display:flex}.mobile .footer-qrcode-list .footer-qrcode-item{margin-right:.35294rem}.mobile .footer-qrcode-list .footer-qrcode-img{width:3.05882rem;height:auto}.mobile .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.mobile .footer-qrcode-list .footer-qrcode-name{margin-top:.11765rem;font-size:.35294rem;color:#a0a0a0;text-align:center}.mobile .footer-follow{margin-top:.82353rem;width:100%}.mobile .footer-follow-ul{width:80%;margin:0 auto;justify-content:center}.mobile .footer-follow-ul a{margin-right:.23529rem}.mobile .footer-follow-ul a:nth-child(5){margin-right:0}.mobile .footer-follow-ul img{width:1.05882rem;height:1.05882rem}.mobile .footer-qrcode-img{width:2.82353rem;height:2.82353rem;margin:0 auto}.mobile .footer-qrcode-img img{width:100%;height:auto;max-height:100%}.mobile .footer-info-wrapper{width:95%;margin-top:.47059rem;font-size:.23529rem;text-align:center}.mobile .footer-address-info{line-height:.35294rem;margin:.05882rem 0}.mobile .footer-info{line-height:.44706rem}.mobile .footer-bottom{display:none}.mobile .footer-nav{background-color:#fff;border-top:.03529rem solid #eee}.mobile .footer-nav-item:nth-child(3) .footer-nav-title a{display:block}.mobile .footer-nav-title{position:relative;padding:0 0 0 .71765rem;font-size:.36471rem;line-height:1.10588rem;font-weight:500;color:#a6a6a6;height:1.10588rem;border-bottom:.03529rem solid #eee}.mobile .footer-nav-title a{color:#a6a6a6}.mobile .footer-nav-title.active .footer-nav-btn{transform:rotate(90deg)}.mobile .footer-nav-title.active+.footer-nav-ul{display:block}.mobile .footer-nav-btn{position:absolute;width:.2rem;height:.36471rem;top:.35294rem;right:.41176rem;background-image:url(/assets/arrow2.png)}.mobile .footer-nav-ul{display:none;border-bottom:.03529rem solid #eee}.mobile .footer-nav-li{font-size:.25882rem;font-weight:400;color:#a0a0a0;line-height:.65882rem;padding:0 0 0 .91765rem}.mobile .footer-nav-li a{color:#a0a0a0}.product-demo-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(2rem,1fr));grid-gap:.16471rem;gap:.16471rem;margin:.21176rem 0 .32941rem}.product-demo-item{display:flex;flex-direction:column;align-items:center;justify-content:flex-start;text-decoration:none;color:#1f2937;background:#fff;border:.01176rem solid #e5e7eb;border-radius:.14118rem;overflow:hidden;transition:transform .2s ease,border-color .2s ease;height:100%}.product-demo-item:hover{transform:translateY(-.03529rem);border-color:#93c5fd}.product-demo-item img{width:100%;height:1.41176rem;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;display:block;background:#f8fafc;box-shadow:none!important;flex-shrink:0}.product-demo-item span{display:block;width:100%;padding:.11765rem;font-size:.15294rem;line-height:1.4;font-weight:600;margin-top:auto;text-align:center}.scene-application-card{position:relative;display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.12fr);align-items:stretch;min-height:4rem;color:#0f172a;text-decoration:none;border-radius:.23529rem;overflow:hidden;background-color:#f8fafc;border:none;box-shadow:0 .21176rem .47059rem rgba(15,23,42,.1);border:.01176rem solid rgba(148,163,184,.22)}.scene-application-card--scene1{background-image:linear-gradient(180deg,rgba(15,23,42,.08),rgba(15,23,42,.56)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:50%}.scene-application-card--scene2{background-image:linear-gradient(180deg,rgba(15,23,42,.1),rgba(15,23,42,.58)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:64%}.scene-application-card:hover{color:#0f172a}.scene-application-card,.scene-application-card .scene-application-card__title,.scene-application-card p,.scene-application-card span:not(.scene-application-card__button){color:#0f172a!important}.scene-application-card__media{position:relative;display:flex;align-items:center;justify-content:center;min-height:100%;overflow:hidden;padding:.18824rem .21176rem .18824rem .14118rem;line-height:0}.scene-application-card__media img{flex:none;width:88%;max-width:4.94118rem;max-width:100%;height:auto;max-height:100%;display:block;margin:0!important;padding:0!important;border:.01176rem solid rgba(148,163,184,.34);border-radius:.16471rem;box-shadow:0 .11765rem .28235rem rgba(15,23,42,.16);vertical-align:top;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center}.scene-application-card__content{position:relative;z-index:1;display:flex;flex-direction:column;justify-content:center;grid-row-gap:.14118rem;row-gap:.14118rem;width:100%;max-width:5.17647rem;min-height:100%;padding:.32941rem .30588rem .28235rem;background:linear-gradient(180deg,hsla(0,0%,100%,.96),rgba(248,250,252,.9))}.scene-application-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-gap:.21176rem;gap:.21176rem;margin:.21176rem 0 .32941rem}.scene-application-card__title{margin:.09412rem 0 0;font-size:.32941rem;line-height:1.15;font-weight:700;text-align:center;color:#0f172a!important;text-shadow:none}.scene-application-card__desc{margin:0;font-size:.17647rem;line-height:1.6;text-align:center;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden;text-overflow:ellipsis;color:rgba(30,41,59,.9)!important;text-shadow:none}.scene-application-card__button{display:inline-flex;align-items:center;justify-content:center;align-self:center;margin-top:0;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content;min-width:1.22353rem;padding:.11765rem .18824rem;font-size:.16471rem;line-height:1;font-weight:600;white-space:nowrap;color:#fff!important;background:#2563eb;border-radius:11.75294rem;box-shadow:0 .09412rem .21176rem rgba(37,99,235,.28)}.scene-application-card .scene-application-card__button{color:#fff!important}.mobile .product-demo-grid{grid-template-columns:repeat(3,minmax(0,1fr));grid-gap:.09412rem;gap:.09412rem}.mobile .product-demo-item{border-radius:.09412rem}.mobile .product-demo-item img{height:auto;aspect-ratio:1/1;-o-object-fit:contain;object-fit:contain;-o-object-position:center;object-position:center;padding:.09412rem;box-shadow:none!important}.mobile .product-demo-item span{padding:.07059rem .07059rem .09412rem;font-size:.21176rem;line-height:1.4;text-align:center;word-break:break-word}.mobile .scene-application-card{grid-template-columns:1fr;grid-template-rows:2.35294rem minmax(0,1fr);min-height:4.58824rem;margin:0;border-radius:.16471rem}.mobile .scene-application-card__media{order:1;min-height:2.35294rem;padding:.11765rem .14118rem}.mobile .scene-application-card__media img{width:100%;max-width:none;max-height:none}.mobile .scene-application-grid{grid-template-columns:1fr;grid-gap:.16471rem;gap:.16471rem}.mobile .scene-application-card__content{order:2;max-width:none;justify-content:center;padding:.23529rem .21176rem;background:linear-gradient(180deg,hsla(0,0%,100%,.97),rgba(248,250,252,.93));grid-row-gap:.11765rem;row-gap:.11765rem}.mobile .scene-application-card__title{font-size:.25882rem;line-height:1.2;margin-top:.07059rem}.mobile .scene-application-card__desc{font-size:.15294rem;line-height:1.5;-webkit-line-clamp:4}.mobile .scene-application-card__button{min-width:1.17647rem;margin-top:.09412rem;padding:.10588rem .16471rem;font-size:.15294rem}.project-item{display:flex;height:1.96471rem;margin:.11765rem 0}.project-item .project-img{width:1.96471rem;height:1.96471rem;position:relative;overflow:hidden;text-align:center}.project-item .project-img img{height:100%;font-size:.09412rem}.project-item .project-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.project-item .project-contents{flex:1;background-color:#efefef;padding:0 .38824rem;position:relative;display:flex;flex-direction:column;justify-content:center}.project-item .project-contents .project-title{font-size:.25882rem;font-weight:700;line-height:.27059rem}.project-item .project-contents .project-title a{color:#238dfb}.project-item .project-contents .project-desc{margin-top:.15294rem;font-size:.22353rem;font-weight:400;color:#717171;line-height:.29412rem}.saerch-fliter-container{height:1.17647rem;border-bottom:.04706rem dashed #e5e5e5;display:flex}.saerch-fliter-container .search-fliter-title{font-size:.21176rem;font-weight:400;color:#434343;width:1.50588rem;margin-right:.58824rem}.saerch-fliter-container .search-fliter-options{flex:1;display:flex;flex-wrap:wrap}.saerch-fliter-container .search-fliter-options .fliter-option{font-size:.18824rem;font-weight:400;color:#959595;padding:0 .35294rem 0 0;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.saerch-fliter-container .search-fliter-options .fliter-option.active{color:#0064c2}.mobile .saerch-fliter-container{height:2.82353rem;margin-top:.35294rem}.dev-layout{flex-wrap:wrap;justify-content:space-between;margin-bottom:.70588rem;flex-direction:column}.dev-container,.dev-layout{display:flex;width:100%}.mobile .dev-container{flex-direction:column;min-height:60vh}.dev-info-container{margin:.70588rem .23529rem;display:flex;color:#5f5d5d;width:3.52941rem;overflow:hidden;flex-direction:column}.dev-info-container .dev-contents{display:flex;flex-direction:column;align-items:center;text-align:center}.dev-info-container .dev-title{font-size:.47059rem;padding:.35294rem}.dev-info-container .dev-desc{font-size:.18824rem;padding:.35294rem;line-height:.28235rem;font-weight:300;height:1.17647rem}.dev-info-container .dev-button{width:1.64706rem;height:.47059rem;background:#0064c2;border-radius:.05882rem;color:#fff;text-align:center}.dev-info-container .dev-banner{padding:.05882rem;overflow:hidden;border-radius:.11765rem}.dev-info-container .dev-banner img{box-shadow:0 0 .23529rem 0 #efefef;background-size:cover;width:5.29412rem;transition:all .25s ease;border-radius:.11765rem}.dev-info-container .dev-banner img:hover{transform:scale(1.1)}.mobile .dev-info-container{width:100%;flex-direction:row}@-webkit-keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@-webkit-keyframes fade-in{0%{opacity:0}to{opacity:1}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}@-webkit-keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}@keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}.float-icon-container{position:fixed;right:23PX;bottom:80PX;z-index:6;height:120PX;width:50PX}.float-icon-container .totop-icon{position:absolute;top:0;left:0}.float-icon-container .menu-icon{position:absolute;top:70PX;left:0}.float-icon-container .menu-icon.active,.float-icon-container .menu-icon.active:hover{background-color:#2f495e}.float-icon-container .menu-icon,.float-icon-container .totop-icon{width:50PX;height:50PX;display:flex;align-items:center;justify-content:center;border-radius:50%;background-color:#0870d1;box-shadow:0 0 .35294rem -.02353rem rgba(19,41,75,.14),0 .14118rem .15294rem -.02353rem rgba(19,41,75,.13),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.13),0 .02353rem .02353rem -.02353rem rgba(19,41,75,.12);cursor:pointer;z-index:200}.float-icon-container .menu-icon svg,.float-icon-container .totop-icon svg{width:50PX;height:50PX}.float-icon-container .menu-icon svg path,.float-icon-container .totop-icon svg path{fill:#fefefe}.float-icon-container .menu-icon:hover,.float-icon-container .totop-icon:hover{background-color:#058ce6}.markdown .hljs{color:#263445;background:0 0}.markdown .hljs-comment,.markdown .hljs-quote{color:#687789;font-style:normal}.markdown .hljs-addition,.markdown .hljs-keyword,.markdown .hljs-selector-tag{color:#b4233f;font-weight:500}.markdown .hljs-link,.markdown .hljs-literal,.markdown .hljs-number,.markdown .hljs-regexp{color:#1769aa}.markdown .hljs-doctag,.markdown .hljs-meta .hljs-meta-string,.markdown .hljs-string{color:#16705a}.markdown .hljs-name,.markdown .hljs-section,.markdown .hljs-selector-class,.markdown .hljs-selector-id,.markdown .hljs-title{color:#6f52a2}.markdown .hljs-attr,.markdown .hljs-attribute,.markdown .hljs-template-variable,.markdown .hljs-variable{color:#8a5a00}.markdown .hljs-built_in,.markdown .hljs-builtin-name,.markdown .hljs-class .hljs-title,.markdown .hljs-type{color:#9a4d16}.markdown .hljs-bullet,.markdown .hljs-meta,.markdown .hljs-meta .hljs-keyword,.markdown .hljs-selector-attr,.markdown .hljs-selector-pseudo,.markdown .hljs-subst,.markdown .hljs-symbol{color:#526579}.markdown .hljs-deletion{color:#b4233f}.markdown .hljs-formula{background:#eaf1f7}.markdown .hljs-emphasis{font-style:italic}.markdown .hljs-strong{font-weight:600}/*!
- * Viewer.js v1.11.6
- * https://fengyuanchen.github.io/viewerjs
- *
- * Copyright 2015-present Chen Fengyuan
- * Released under the MIT license
- *
- * Date: 2023-09-17T03:16:35.830Z
- */.viewer-close:before,.viewer-flip-horizontal:before,.viewer-flip-vertical:before,.viewer-fullscreen-exit:before,.viewer-fullscreen:before,.viewer-next:before,.viewer-one-to-one:before,.viewer-play:before,.viewer-prev:before,.viewer-reset:before,.viewer-rotate-left:before,.viewer-rotate-right:before,.viewer-zoom-in:before,.viewer-zoom-out:before{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAARgAAAAUCAYAAABWOyJDAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAALEgAACxIB0t1+/AAAABx0RVh0U29mdHdhcmUAQWRvYmUgRmlyZXdvcmtzIENTNui8sowAAAQPSURBVHic7Zs/iFxVFMa/0U2UaJGksUgnIVhYxVhpjDbZCBmLdAYECxsRFBTUamcXUiSNncgKQbSxsxH8gzAP3FU2jY0kKKJNiiiIghFlccnP4p3nPCdv3p9778vsLOcHB2bfveeb7955c3jvvNkBIMdxnD64a94GHMfZu3iBcRynN7zAOI7TG15gHCeeNUkr8zaxG2lbYDYsdgMbktBsP03jdQwljSXdtBhLOmtjowC9Mg9L+knSlcD8TNKpSA9lBpK2JF2VdDSR5n5J64m0qli399hNFMUlpshQii5jbXTbHGviB0nLNeNDSd9VO4A2UdB2fp+x0eCnaXxWXGA2X0au/3HgN9P4LFCjIANOJdrLr0zzZ+BEpNYDwKbpnQMeAw4m8HjQtM6Z9qa917zPQwFr3M5KgA6J5rTJCdFZJj9/lyvGhsDvwFNVuV2MhhjrK6b9bFiE+j1r87eBl4HDwCF7/U/k+ofAX5b/EXBv5JoLMuILzf3Ap6Z3EzgdqHMCuF7hcQf4HDgeoHnccncqdK/TvSDWffFXI/exICY/xZyqc6XLWF1UFZna4gJ7q8BsRvgd2/xXpo6P+D9dfT7PpECtA3cnWPM0GXGFZh/wgWltA+cDNC7X+AP4GzjZQe+k5dRxuYPeiuXU7e1qwLpDz7dFjXKRaSwuMLvAlG8zZlG+YmiK1HoFqT7wP2z+4Q45TfEGcMt01xLoNZEBTwRqD4BLpnMLeC1A41UmVxsXgXeBayV/Wx20rpTyrpnWRft7p6O/FdqzGrDukPNtkaMoMo3FBdBSQMOnYBCReyf05s126fU9ytfX98+mY54Kxnp7S9K3kj6U9KYdG0h6UdLbkh7poFXMfUnSOyVvL0h6VtIXHbS6nOP+s/Zm9mvyXW1uuC9ohZ72E9uDmXWLJOB1GxsH+DxPftsB8B6wlGDN02TAkxG6+4D3TWsbeC5CS8CDFce+AW500LhhOW2020TRjK3b21HEmgti9m0RonxbdMZeVzV+/4tF3cBpP7E9mKHNL5q8h5g0eYsCMQz0epq8gQrwMXAgcs0FGXGFRcB9wCemF9PkbYqM/Bas7fxLwNeJPdTdpo4itQti8lPMqTpXuozVRVXPpbHI3KkNTB1NfkL81j2mvhDp91HgV9MKuRIqrykj3WPq4rHyL+axj8/qGPmTqi6F9YDlHOvJU6oYcTsh/TYSzWmTE6JT19CtLTJt32D6CmHe0eQn1O8z5AXgT4sx4Vcu0/EQecMydB8z0hUWkTd2t4CrwNEePqMBcAR4mrBbwyXLPWJa8zrXmmLEhNBmfpkuY2102xxrih+pb+ieAb6vGhuA97UcJ5KR8gZ77K+99xxeYBzH6Q3/Z0fHcXrDC4zjOL3hBcZxnN74F+zlvXFWXF9PAAAAAElFTkSuQmCC);background-repeat:no-repeat;background-size:280px;color:transparent;display:block;font-size:0;height:20px;line-height:0;width:20px}.viewer-zoom-in:before{background-position:0 0;content:"Zoom In"}.viewer-zoom-out:before{background-position:-20px 0;content:"Zoom Out"}.viewer-one-to-one:before{background-position:-40px 0;content:"One to One"}.viewer-reset:before{background-position:-60px 0;content:"Reset"}.viewer-prev:before{background-position:-80px 0;content:"Previous"}.viewer-play:before{background-position:-100px 0;content:"Play"}.viewer-next:before{background-position:-120px 0;content:"Next"}.viewer-rotate-left:before{background-position:-140px 0;content:"Rotate Left"}.viewer-rotate-right:before{background-position:-160px 0;content:"Rotate Right"}.viewer-flip-horizontal:before{background-position:-180px 0;content:"Flip Horizontal"}.viewer-flip-vertical:before{background-position:-200px 0;content:"Flip Vertical"}.viewer-fullscreen:before{background-position:-220px 0;content:"Enter Full Screen"}.viewer-fullscreen-exit:before{background-position:-240px 0;content:"Exit Full Screen"}.viewer-close:before{background-position:-260px 0;content:"Close"}.viewer-container{bottom:0;direction:ltr;font-size:0;left:0;line-height:0;overflow:hidden;position:absolute;right:0;-webkit-tap-highlight-color:transparent;top:0;touch-action:none;-webkit-touch-callout:none;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.viewer-container ::-moz-selection,.viewer-container::-moz-selection{background-color:transparent}.viewer-container ::selection,.viewer-container::selection{background-color:transparent}.viewer-container:focus{outline:0}.viewer-container img{display:block;height:auto;max-height:none!important;max-width:none!important;min-height:0!important;min-width:0!important;width:100%}.viewer-canvas{bottom:0;left:0;overflow:hidden;position:absolute;right:0;top:0}.viewer-canvas>img{height:auto;margin:15px auto;max-width:90%!important;width:auto}.viewer-footer{bottom:0;left:0;overflow:hidden;position:absolute;right:0;text-align:center}.viewer-navbar{background-color:rgba(0,0,0,.5);overflow:hidden}.viewer-list{box-sizing:content-box;height:50px;margin:0;overflow:hidden;padding:1px 0}.viewer-list>li{color:transparent;cursor:pointer;float:left;font-size:0;height:50px;line-height:0;opacity:.5;overflow:hidden;transition:opacity .15s;width:30px}.viewer-list>li:focus,.viewer-list>li:hover{opacity:.75}.viewer-list>li:focus{outline:0}.viewer-list>li+li{margin-left:1px}.viewer-list>.viewer-loading{position:relative}.viewer-list>.viewer-loading:after{border-width:2px;height:20px;margin-left:-10px;margin-top:-10px;width:20px}.viewer-list>.viewer-active,.viewer-list>.viewer-active:focus,.viewer-list>.viewer-active:hover{opacity:1}.viewer-player{background-color:#000;bottom:0;cursor:none;display:none;right:0;z-index:1}.viewer-player,.viewer-player>img{left:0;position:absolute;top:0}.viewer-toolbar>ul{display:inline-block;margin:0 auto 5px;overflow:hidden;padding:6px 3px}.viewer-toolbar>ul>li{background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;float:left;height:24px;overflow:hidden;transition:background-color .15s;width:24px}.viewer-toolbar>ul>li:focus,.viewer-toolbar>ul>li:hover{background-color:rgba(0,0,0,.8)}.viewer-toolbar>ul>li:focus{box-shadow:0 0 3px #fff;outline:0;position:relative;z-index:1}.viewer-toolbar>ul>li:before{margin:2px}.viewer-toolbar>ul>li+li{margin-left:1px}.viewer-toolbar>ul>.viewer-small{height:18px;margin-bottom:3px;margin-top:3px;width:18px}.viewer-toolbar>ul>.viewer-small:before{margin:-1px}.viewer-toolbar>ul>.viewer-large{height:30px;margin-bottom:-3px;margin-top:-3px;width:30px}.viewer-toolbar>ul>.viewer-large:before{margin:5px}.viewer-tooltip{background-color:rgba(0,0,0,.8);border-radius:10px;color:#fff;display:none;font-size:12px;height:20px;left:50%;line-height:20px;margin-left:-25px;margin-top:-10px;position:absolute;text-align:center;top:50%;width:50px}.viewer-title{color:#ccc;display:inline-block;font-size:12px;line-height:1.2;margin:5px 5%;max-width:90%;min-height:14px;opacity:.8;overflow:hidden;text-overflow:ellipsis;transition:opacity .15s;white-space:nowrap}.viewer-title:hover{opacity:1}.viewer-button{-webkit-app-region:no-drag;background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;height:80px;overflow:hidden;position:absolute;right:-40px;top:-40px;transition:background-color .15s;width:80px}.viewer-button:focus,.viewer-button:hover{background-color:rgba(0,0,0,.8)}.viewer-button:focus{box-shadow:0 0 3px #fff;outline:0}.viewer-button:before{bottom:15px;left:15px;position:absolute}.viewer-fixed{position:fixed}.viewer-open{overflow:hidden}.viewer-show{display:block}.viewer-hide{display:none}.viewer-backdrop{background-color:rgba(0,0,0,.5)}.viewer-invisible{visibility:hidden}.viewer-move{cursor:move;cursor:-webkit-grab;cursor:grab}.viewer-fade{opacity:0}.viewer-in{opacity:1}.viewer-transition{transition:all .3s}@-webkit-keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}.viewer-loading:after{-webkit-animation:viewer-spinner 1s linear infinite;animation:viewer-spinner 1s linear infinite;border:4px solid hsla(0,0%,100%,.1);border-left-color:hsla(0,0%,100%,.5);border-radius:50%;content:"";display:inline-block;height:40px;left:50%;margin-left:-20px;margin-top:-20px;position:absolute;top:50%;width:40px;z-index:1}@media (max-width:767px){.viewer-hide-xs-down{display:none}}@media (max-width:991px){.viewer-hide-sm-down{display:none}}@media (max-width:1199px){.viewer-hide-md-down{display:none}}.nuxt-progress{position:fixed;top:0;left:0;right:0;height:.02353rem;width:0;opacity:1;transition:width .1s,opacity .4s;background-color:#000;z-index:999999}.nuxt-progress.nuxt-progress-notransition{transition:none}.nuxt-progress-failed{background-color:red}.side-bar{width:2.47059rem;position:sticky;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.side-bar .side-bar-title{height:.82353rem;width:2.47059rem;background-image:url(/assets/sidebar-title.jpg);background-size:cover}.side-bar .side-bar-title p{height:.21176rem;font-size:.28235rem;font-weight:700;color:#fff;line-height:.82353rem;text-align:center}.side-bar .side-bar-contents{cursor:pointer;border-bottom:.02353rem solid #e5e5e5;border-left:.02353rem solid #e5e5e5;border-right:.02353rem solid #e5e5e5}.side-bar .side-bar-contents .side-bar-collapse{position:relative;height:.50588rem;overflow:hidden;transition:all .2s ease;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.side-bar .side-bar-contents .side-bar-collapse .collapse-title{font-size:.18824rem;font-weight:400;color:#434343;line-height:.50588rem;padding-left:.24706rem;border-top:.01176rem solid #edf1f4;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.side-bar .side-bar-contents .side-bar-collapse .collapse-title.active{color:#409eff}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn{position:absolute;height:.11765rem;width:.11765rem;box-shadow:.02353rem -.02353rem 0 #82a5d7;background-color:#fff;top:.2rem;right:.18824rem;transform:rotate(45deg);transition:all .25s ease}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn.collapse-btn-active{transform:translate(.04706rem,-.04706rem) rotate(135deg)}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents{border-bottom:.01176rem solid #edf1f4}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item{padding-left:.38824rem;line-height:.44706rem;color:#838383;font-size:.16471rem}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active{color:#409eff;background-color:#f6f7f8;position:relative}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active:after{content:" ";width:.04706rem;height:.04706rem;background:#82a5d7;border-radius:50%;position:absolute;top:50%;left:.17647rem;transform:translateY(-50%)}.page-header-container{margin-bottom:.35294rem;width:100%}.page-header-container .page-header-content{display:flex;align-content:center;position:relative}.page-header-container .page-header-content .page-header-arrow-icon{width:.28235rem;height:.32941rem;padding-top:.02353rem;color:#2f495e;font-size:.23529rem;transition:all .2s ease}.page-header-container .page-header-content .header-arrow-container{width:.17647rem;height:.17647rem;background-image:url(/assets/arrow3.png);background-size:cover}.page-header-container .page-header-content .page-header-arrow-icon:hover{color:#007bff}.page-header-container .page-header-content .page-header-item{color:#858585;font-size:.18824rem;font-weight:500;display:flex;height:.35294rem;line-height:.35294rem;cursor:pointer;align-items:center}.page-header-container .page-header-content .page-header-item .page-header-tag{margin:0 .09412rem;transition:all .2s ease}.page-header-container .page-header-content .page-header-item .page-header-tag.active{color:#2f495e}.page-header-container .page-header-content .page-header-item .page-header-tag:hover{color:#007bff}.mobile .page-header-container{margin-top:.35294rem}.search-box{display:flex;grid-gap:.11765rem;gap:.11765rem;margin-bottom:.28235rem;position:relative;align-items:center}.search-box input{flex:1;min-width:7.05882rem;height:.51765rem;background:#edf1f4;border-radius:.09412rem;border:.01176rem solid #d5dee8;padding:0 .18824rem;font-size:.17647rem;color:#253443;outline:0;z-index:3;transition:border-color .2s ease,box-shadow .2s ease}.search-box input:focus{border-color:#0064c2;box-shadow:0 0 0 .03529rem rgba(0,100,194,.12157)}.search-box .search-btn{width:1.55294rem;height:.51765rem;background:#0064c2;border-radius:.09412rem;border:none;cursor:pointer;transition:background-color .2s ease}.search-box .search-btn:hover{background:#0a5aaa}.search-box .search-btn p{margin:0;line-height:.51765rem;font-size:.18824rem;font-weight:700;color:#fff}.search-box .search-cover{position:fixed;top:0;left:0;right:0;bottom:0;z-index:2;background-color:rgba(25,25,25,.1098);-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem)}.search-result-container{overflow:hidden}.search-result-container::-webkit-scrollbar{width:.14118rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.search-result-container .el-tabs__item{display:table-cell;font-size:.21176rem;font-weight:600}.search-result-container .el-tabs__active-bar{height:.04706rem}.search-result-container{width:100%;min-height:4.47059rem;max-height:7.05882rem;overflow-y:auto;background-color:#fff;position:absolute;top:.63529rem;border:.01176rem solid #e2e8f0;border-radius:.11765rem;box-shadow:0 .11765rem .17647rem -.03529rem rgba(0,0,0,.10196),0 .04706rem .07059rem -.02353rem rgba(0,0,0,.05098);transition:all .25s ease;color:#2f495e;z-index:3;padding:.14118rem;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.search-result-container .search-title{height:.70588rem;font-size:.29412rem;padding:.17647rem;border-bottom:.01176rem solid #d9d9d9}.search-result-container .search-result-contents{display:flex;align-items:flex-start;grid-gap:.11765rem;gap:.11765rem;padding:.14118rem;border-bottom:.01176rem solid #edf2f7;position:relative}.search-result-container .search-result-contents svg{display:inline;font-size:.23529rem;color:#409eff;padding-right:.11765rem}.search-result-container .search-result-contents:hover{background-color:#f3f8fd}.search-result-container .search-result-content{flex:1;display:flex;flex-direction:column;justify-content:center;position:relative;transition:all .25s ease}.search-result-container .search-result-name{font-size:.18824rem;text-align:left;font-weight:700;color:#409eff;line-height:1.4}.search-result-container .search-result-sku{font-size:.16471rem;line-height:1.6;color:#5b5b5b;margin-top:.04706rem}.search-result-container .search-result-key{font-size:.18824rem;font-weight:700;color:#2f495e;margin-top:.04706rem}.search-result-container .search-result-key .search-result-highlight{color:#409eff}.search-result-container .search-result-key .search-result-key-tag{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#5b5b5b;padding:.02353rem .11765rem;border:.01176rem solid #5b5b5b;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container .search-result-key .search-result-key-tag.active{color:#409eff;border:.01176rem solid #409eff}.search-result-container .search-result-image{width:1.31765rem;height:1.31765rem;margin:0 .21176rem 0 .04706rem}.search-result-container .search-result-eol-tag{position:absolute;width:.41176rem;height:.41176rem;border-radius:50%;top:5%;left:.35294rem;background-color:#2f495e;color:#fff;font-size:.15294rem;font-weight:700;line-height:.41176rem;text-align:center}.search-result-container .search-result-recommand-box{margin-top:.14118rem}.search-result-container .search-result-recommand-box .search-result-recommand-item{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#409eff;padding:.04706rem .11765rem;border:.01176rem solid #409eff;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container:before{display:block;position:absolute;content:"";width:.16471rem;height:.16471rem;background:#fff;z-index:1000;top:-.08235rem;left:calc(50% - .08235rem);border-top:.01176rem solid #d9d9d9;border-right:.01176rem solid #d9d9d9;transform:rotate(-45deg);border-radius:.02353rem}.mobile .search-box{margin-bottom:.09412rem;width:100%;grid-gap:.09412rem;gap:.09412rem}.mobile .search-box input{height:.65882rem;font-size:.2rem}.mobile .search-box .search-btn{width:2.11765rem;height:.65882rem;background:#0064c2;border-radius:.09412rem}.mobile .search-box .search-btn p{margin:0;line-height:.65882rem;font-size:.21176rem;font-weight:700;color:#fff}.mobile .search-result-container{top:.75294rem}.search-result-container .tabs{display:flex;grid-gap:.07059rem;gap:.07059rem;width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .14118rem;padding:.09412rem .14118rem;border-radius:0;background:hsla(0,0%,100%,.9);border:0;border-bottom:.01176rem solid #e6edf5;-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem);position:sticky;top:-.14118rem;z-index:6}.search-result-container .tabs:after{content:"";position:absolute;left:0;right:0;top:0;bottom:0;background:0 0;z-index:-1}.search-result-container .tabs button{min-width:1.27059rem;padding:.10588rem .18824rem;border-radius:.11765rem;font-size:.16471rem;font-weight:600;color:#516578;background:hsla(0,0%,100%,.6);border:.01176rem solid #d7e3ef;line-height:1.2;overflow:hidden;transition:color .2s ease,background-color .2s ease,box-shadow .2s ease}.search-result-container .tabs button:first-child,.search-result-container .tabs button:last-child{border-radius:.11765rem}.search-result-container .tabs button:hover{color:#2f4f6f;background:#f8fbff;border-color:#cddded}.search-result-container .tabs button.active{color:#0f4f8e;background:#fff;border:.01176rem solid #c8d9eb;border-radius:.11765rem;box-shadow:0 .02353rem .09412rem rgba(0,100,194,.16078)}.search-result-container .tab-content{padding:.11765rem .09412rem .09412rem;background:0 0}.search-result-container .search-result-contents{border-radius:.09412rem;transition:background-color .2s ease,box-shadow .2s ease}.search-result-container .search-result-contents:hover{box-shadow:inset 0 0 0 .01176rem #dbe9f8}.search-result-contents-list{padding-bottom:.82353rem}.search-result-view-all-wrap{position:sticky;bottom:0;z-index:4;display:flex;justify-content:center;padding:.11765rem .09412rem .07059rem;background:linear-gradient(0deg,#fff 70%,hsla(0,0%,100%,0))}.search-result-view-all-btn{display:inline-block;min-width:2.82353rem;text-align:center;padding:.12941rem .21176rem;border-radius:.28235rem;background:#0064c2;color:#fff;font-size:.17647rem;font-weight:700;text-decoration:none;box-shadow:0 .04706rem .14118rem rgba(0,100,194,.25);transition:background-color .2s ease}.search-result-view-all-btn:hover{background:#0a5aaa}.mobile .search-result-container .tabs{width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .11765rem;padding:.09412rem .11765rem}.mobile .search-result-container .tabs button{flex:1;min-width:0;padding:.14118rem .11765rem;font-size:.17647rem}.mobile .search-result-container .tab-content{padding:.09412rem .04706rem .07059rem}.search-result-container.search-result-embedded{position:relative;top:auto;max-height:none;min-height:0;padding:0;box-shadow:none;-webkit-animation:none;animation:none}.search-result-container.search-result-embedded:before{display:none}.search-result-loading{padding:.09412rem .04706rem;display:flex;flex-direction:column}.search-result-loading-header{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;color:#516578;font-size:.16471rem;margin:0 0 .11765rem}.search-result-loading-text{min-width:0;font-size:.16471rem;font-weight:400;line-height:.23529rem}.search-result-loading-dot{width:.09412rem;height:.09412rem;border-radius:50%;background:#409eff;-webkit-animation:search-loading-pulse 1s ease-in-out infinite;animation:search-loading-pulse 1s ease-in-out infinite}.search-result-loading-list{display:flex;flex-direction:column;grid-gap:.11765rem;gap:.11765rem}.search-result-loading-item{padding:.14118rem;border-radius:.09412rem;border:.01176rem solid #edf2f7;background:#fbfdff}.search-result-loading-line{height:.11765rem;border-radius:11.75294rem;margin-bottom:.09412rem;background:linear-gradient(90deg,#e9f0f7 20%,#f5f9fd 45%,#e9f0f7 70%);background-size:2.82353rem 100%;-webkit-animation:search-loading-shimmer 1.1s linear infinite;animation:search-loading-shimmer 1.1s linear infinite}.search-result-loading-line.is-title{width:52%;height:.14118rem}.search-result-loading-line.is-short{width:36%;margin-bottom:0}@-webkit-keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@-webkit-keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}@keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}.search-result-loading-text[data-v-2b770079]{min-width:0;font-size:.16471rem!important;font-weight:400;line-height:.23529rem}.tab-panel{border:.01176rem solid #e5e5e5;padding:.09412rem;border-radius:.09412rem}.tabs{display:flex;grid-gap:.09412rem;gap:.09412rem;margin-bottom:.18824rem}.tabs button{padding:.11765rem .21176rem;border:none;border-bottom:.04706rem solid transparent;background:#f9f9f9;cursor:pointer;transition:.2s}.tabs button.active{border-color:#007bff;color:#007bff}.tab-content{padding:.18824rem;background:#fefefe;border-radius:.09412rem}.search-result-container .tab-panel{border:0}.carousel-container[data-v-6e07f87d]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-6e07f87d]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-6e07f87d]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-6e07f87d]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-6e07f87d]{flex-shrink:0;width:33.333%;text-align:center;cursor:pointer}.preview-image img[data-v-6e07f87d]{max-width:100%;height:auto;margin:0}.arrow[data-v-6e07f87d]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-6e07f87d]{left:0;transform:rotateY(180deg)}.arrow.right[data-v-6e07f87d]{right:0}.carousel-thumbnails[data-v-6e07f87d]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-6e07f87d]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-6e07f87d]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-6e07f87d]{width:100%;margin:0;height:auto}.clickable-area[data-v-6e07f87d]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-6e07f87d]{left:0}.clickable-area.right[data-v-6e07f87d]{right:0}.carousel-container[data-v-7d51a79c]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-7d51a79c]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-7d51a79c]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-7d51a79c]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-7d51a79c]{flex-shrink:0;width:100%;text-align:center;cursor:pointer}.preview-image img[data-v-7d51a79c]{width:100%;height:auto;margin:0}.arrow[data-v-7d51a79c]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-7d51a79c]{left:0;transform:translateY(-50%) rotateY(180deg)}.arrow.right[data-v-7d51a79c]{right:0;transform:translateY(-50%)}.carousel-thumbnails[data-v-7d51a79c]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-7d51a79c]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-7d51a79c]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-7d51a79c]{width:100%;margin:0;height:auto}.clickable-area[data-v-7d51a79c]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-7d51a79c]{left:0}.clickable-area.right[data-v-7d51a79c]{right:0}.corner-marker[data-v-7d51a79c]{position:absolute;bottom:.11765rem;left:.11765rem;background-color:rgba(0,0,0,.5);color:#fff;padding:.05882rem .11765rem;border-radius:.05882rem;z-index:2}.video-gallery-island[data-v-5e05839f]{min-width:0;width:100%}.page-tools[data-v-39baf185]{width:2.35294rem;margin-bottom:.16471rem;border:.01176rem solid #dfeaf5;border-radius:.11765rem;background:#f8fbfe;box-shadow:0 .07059rem .21176rem rgba(19,41,75,.08);overflow:visible}.page-tools-title[data-v-39baf185]{height:.4rem;line-height:.4rem;padding:0 .14118rem;border-bottom:.01176rem solid #e5eef7;color:#2f495e;font-size:.15294rem;font-weight:700}.page-tools-actions[data-v-39baf185]{display:flex;flex-direction:column;grid-gap:.09412rem;gap:.09412rem;padding:.11765rem;align-items:stretch}.page-tools-action[data-v-39baf185]{display:inline-flex;align-items:center;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;height:.43529rem;width:100%;padding:0 .11765rem;border:.01176rem solid #d6e5f3;border-radius:.08235rem;background:#fff;color:#238dfb;font-size:.15294rem;font-weight:700;transition:background-color .2s ease,border-color .2s ease,transform .2s ease}.page-tools-action .page-tools-icon[data-v-39baf185]{width:.21176rem;height:.21176rem;flex:0 0 auto;fill:currentColor;display:block}.page-tools-action[data-v-39baf185]:after{content:"";width:.08235rem;height:.08235rem;margin-left:auto;border-top:.02353rem solid;border-right:.02353rem solid;transform:rotate(45deg);opacity:.45}.page-tools-action[data-v-39baf185]:hover{background:#eaf4ff;border-color:#b9d8f4;transform:translateY(-.01176rem)}.page-tools.mobile[data-v-39baf185]{width:auto;margin:.09412rem 0 .18824rem;border:0;background:0 0;box-shadow:none}.page-tools.mobile .page-tools-actions[data-v-39baf185]{flex-direction:row;padding:0}.page-tools.mobile .page-tools-action[data-v-39baf185]{width:.63529rem;min-width:.63529rem;height:.42353rem;padding:0;background:#edf6ff;border-color:#b7d8f5;justify-content:center}.page-tools.mobile .page-tools-action[data-v-39baf185]:after{display:none}.markdown-action-menu[data-v-5d6a4f8a]{position:relative;display:flex;justify-content:flex-end;margin:-.14118rem 0 .21176rem;z-index:20}.markdown-action-trigger[data-v-5d6a4f8a]{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;height:.47059rem;padding:0 .16471rem;border:.01176rem solid #b9cfe5;border-radius:.07059rem;background:linear-gradient(135deg,#0064c2,#238dfb);color:#fff;font-size:.16471rem;font-weight:700;cursor:pointer;transition:background-color .2s ease,border-color .2s ease}.markdown-action-trigger svg[data-v-5d6a4f8a]{width:.18824rem;height:.18824rem}.markdown-action-trigger[data-v-5d6a4f8a]:hover{background:linear-gradient(135deg,#0059ad,#167ce8);border-color:#82b6ec}.markdown-action-dropdown[data-v-5d6a4f8a]{position:fixed;z-index:2147483000;width:3.52941rem;overflow:hidden;border:.01176rem solid #c8dced;border-radius:.11765rem;background:#fff;box-shadow:0 .18824rem .44706rem rgba(18,62,111,.16),0 .02353rem .09412rem rgba(24,84,140,.08)}.markdown-action-item[data-v-5d6a4f8a]{display:flex;width:100%;grid-gap:.16471rem;gap:.16471rem;align-items:flex-start;padding:.17647rem .18824rem;border:0;border-bottom:.01176rem solid #e6edf5;background:0 0;color:#2f495e;text-align:left;cursor:pointer;transition:background-color .15s ease}.markdown-action-item svg[data-v-5d6a4f8a]{flex:0 0 auto;width:.2rem;height:.2rem;margin-top:.02353rem;color:#238dfb}.markdown-action-item strong[data-v-5d6a4f8a]{display:block;font-size:.17647rem;line-height:.23529rem}.markdown-action-item small[data-v-5d6a4f8a]{display:block;margin-top:.02353rem;color:#6f8193;font-size:.15294rem;line-height:.21176rem}.markdown-action-item[data-v-5d6a4f8a]:last-child{border-bottom:0}.markdown-action-item[data-v-5d6a4f8a]:hover{background:#f3f8fe}.markdown-action-menu.placement-sidebar[data-v-5d6a4f8a]{justify-content:center;margin:.14118rem 0 0}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;justify-content:center;background:#edf6ff;border-color:#c7dff7;color:#0064c2}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#dfefff;border-color:#9fc7ef}.markdown-action-menu.placement-sidebar .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.05882rem}.markdown-action-menu.placement-anchor[data-v-5d6a4f8a]{justify-content:flex-start;margin:0 0 .11765rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:center;padding:0 .11765rem;background:#f5f9fd;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-anchor .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.placement-toolbox[data-v-5d6a4f8a]{width:100%;flex:1;justify-content:flex-start;margin:0}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;padding:0 .11765rem;background:#fff;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]{flex:0 0 auto}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{width:.16471rem;height:.16471rem;margin-left:auto;opacity:.55}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-toolbox .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.compact[data-v-5d6a4f8a]{justify-content:flex-start;margin:.09412rem 0 .18824rem}.markdown-action-menu.compact .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center;padding:0;background:#edf6ff;border-color:#b7d8f5;color:#0064c2}.markdown-action-menu.compact .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.52941rem;max-width:calc(100vw - .37647rem)}.markdown-action-menu.compact.placement-toolbox[data-v-5d6a4f8a]{flex:0 0 auto;margin:0}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{margin-left:0}</style><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer/state.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer/payload.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/manifest.js" as="script">
-  </head>
-  <body>
-    <div data-server-rendered="true" id="__nuxt"><!----><div id="__layout"><div class="device-hydration-sensitive"><div class="pc"><header langdata="[object Object]" lang="en"><!----> <!----> <div class="header-container"><a href="https://m5stack.com/" class="logo"><img src="/assets/m5logo.svg" alt="M5Stack"></a> <div class="header-nav"><div class="header-nav-ul"><!----> <li data-id="solution" class="header-nav-item"><a class="header-nav-item-a disabledHover">Solution</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="store" class="header-nav-item"><a href="https://shop.m5stack.com" class="header-nav-item-a">Store</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="software" class="header-nav-item"><a class="header-nav-item-a disabledHover">Software</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="document" class="header-nav-item"><a class="header-nav-item-a disabledHover">Documentation</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="aboutus" class="header-nav-item"><a class="header-nav-item-a disabledHover">About Us</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="contact" class="header-nav-item"><a class="header-nav-item-a disabledHover">Contact</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----></div></div> <div class="language-option-box"><div class="current-language"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 1.32 1.32" fill="currentColor" aria-hidden="true" class="icon"><g><path d="M0.66 0c0.18,0 0.35,0.07 0.47,0.19 0.12,0.12 0.19,0.28 0.19,0.47 0,0.18 -0.07,0.35 -0.19,0.47 -0.12,0.12 -0.28,0.19 -0.47,0.19 -0.18,0 -0.35,-0.07 -0.47,-0.19 -0.12,-0.12 -0.19,-0.28 -0.19,-0.47 0,-0.18 0.07,-0.35 0.19,-0.47 0.12,-0.12 0.28,-0.19 0.47,-0.19zm0.39 0.27c-0.1,-0.1 -0.24,-0.16 -0.39,-0.16 -0.15,0 -0.29,0.06 -0.39,0.16 -0.1,0.1 -0.16,0.24 -0.16,0.39 0,0.15 0.06,0.29 0.16,0.39 0.1,0.1 0.24,0.16 0.39,0.16 0.15,0 0.29,-0.06 0.39,-0.16 0.1,-0.1 0.16,-0.24 0.16,-0.39 0,-0.15 -0.06,-0.29 -0.16,-0.39z"></path> <path d="M0.09 0.51c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.09 0.92c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.62 1.21c0.02,0.02 0.02,0.06 0,0.08 -0.02,0.02 -0.06,0.02 -0.08,0 -0.07,-0.06 -0.13,-0.16 -0.16,-0.27 -0.04,-0.11 -0.06,-0.23 -0.06,-0.36 0,-0.13 0.02,-0.26 0.06,-0.36 0.04,-0.11 0.1,-0.21 0.16,-0.27 0.02,-0.02 0.06,-0.02 0.08,0 0.02,0.02 0.02,0.06 -0,0.08 -0.06,0.05 -0.1,0.13 -0.14,0.23 -0.03,0.09 -0.05,0.21 -0.05,0.33 0,0.12 0.02,0.23 0.05,0.33 0.03,0.1 0.08,0.18 0.14,0.23z"></path> <path d="M0.78 1.29c-0.02,0.02 -0.06,0.02 -0.08,-0 -0.02,-0.02 -0.02,-0.06 0,-0.08 0.06,-0.05 0.1,-0.13 0.14,-0.23 0.03,-0.09 0.05,-0.21 0.05,-0.33 0,-0.12 -0.02,-0.23 -0.05,-0.33 -0.03,-0.1 -0.08,-0.18 -0.14,-0.23 -0.02,-0.02 -0.02,-0.06 -0,-0.08 0.02,-0.02 0.06,-0.02 0.08,-0 0.07,0.06 0.13,0.16 0.16,0.27 0.04,0.11 0.06,0.23 0.06,0.36 0,0.13 -0.02,0.26 -0.06,0.36 -0.04,0.11 -0.1,0.21 -0.16,0.27z"></path></g></svg> <div>English</div> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg></div> <div class="language-dropdown-wrapper"><div class="language-dropdown"><div class="language-item active">English</div> <div class="language-item">简体中文</div> <div class="language-item">日本語</div></div></div></div></div></header> <div class="docs-layouts"><div class="docs-layouts-sidebar"><div class="side-bar"><div class="side-bar-title"><p>CONTENTS</p></div> <div class="side-bar-contents"></div></div></div> <div class="docs-layouts-body"><div class="page-header-container"><!----></div> <!----> <div class="search-box"><div id="search"></div> <input placeholder="Product Name / SKU"> <div class="search-result-container" style="display:none" data-v-2b770079><a class="search-result-contents" data-v-2b770079><div class="search-result-content" data-v-2b770079><div class="search-result-name" data-v-2b770079>No Results Found</div> <div class="search-result-sku" data-v-2b770079>Hot Searches</div> <div class="search-result-key" data-v-2b770079><div class="search-result-recommand-box" data-v-2b770079><div data-key="Camera" class="search-result-recommand-item" data-v-2b770079>
-            Camera
-          </div><div data-key="WiFi" class="search-result-recommand-item" data-v-2b770079>
-            WiFi
-          </div><div data-key="RS485" class="search-result-recommand-item" data-v-2b770079>
-            RS485
-          </div><div data-key="RS232" class="search-result-recommand-item" data-v-2b770079>
-            RS232
-          </div><div data-key="Relay" class="search-result-recommand-item" data-v-2b770079>
-            Relay
-          </div><div data-key="LoRaWAN" class="search-result-recommand-item" data-v-2b770079>
-            LoRaWAN
-          </div><div data-key="GPS" class="search-result-recommand-item" data-v-2b770079>
-            GPS
-          </div><div data-key="NB-IoT" class="search-result-recommand-item" data-v-2b770079>
-            NB-IoT
-          </div><div data-key="LTE" class="search-result-recommand-item" data-v-2b770079>
-            LTE
-          </div><div data-key="GSM" class="search-result-recommand-item" data-v-2b770079>
-            GSM
-          </div><div data-key="Zigbee" class="search-result-recommand-item" data-v-2b770079>
-            Zigbee
-          </div><div data-key="Servo" class="search-result-recommand-item" data-v-2b770079>
-            Servo
-          </div><div data-key="StepMotor" class="search-result-recommand-item" data-v-2b770079>
-            StepMotor
-          </div><div data-key="Ethernet" class="search-result-recommand-item" data-v-2b770079>
-            Ethernet
-          </div><div data-key="E-Paper" class="search-result-recommand-item" data-v-2b770079>
-            E-Paper
-          </div></div></div></div></a> <div class="tab-panel" style="display:none" data-v-2b770079><div class="tabs"><button>
-      Product
-    </button><button>
-      Contents
-    </button></div> <div class="tab-content"><div style="display:none"></div><div style="display:none"></div></div></div></div> <button class="search-btn"><p>Search</p></button> <div class="search-cover" style="display:none"></div></div> <div class="viewer"><div class="markdown"><h1 id="cardputer" data-id="Cardputer">Cardputer</h1> <p><span class="product-sku">SKU:K132</span></p><div class="carousel-container" data-v-6e07f87d><div class="carousel-preview" data-v-6e07f87d><div class="clickable-area left" data-v-6e07f87d></div> <button class="arrow left" data-v-6e07f87d></button> <div class="carousel-images" data-v-6e07f87d><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-6e07f87d><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/K132-main-pictures_01.jpg" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-60261bcd-a23f-40e6-994d-ad97477dcec4.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-bceba3da-490a-41d8-9927-64d0279a3cb1.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-7e59fa08-5dec-48db-acc9-18559185ac7c.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-8147e39a-60dc-478c-af36-52c1953c438e.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-e3288169-9100-44f4-becd-afe1556f56b0.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-a354b178-8c1e-4e60-8338-77efe96ea8df.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-200999cf-cf5d-463d-911d-7b4c2f4222c1.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-e095a0f7-0c8c-414e-86bb-55e0148e55e9.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/16.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/17.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/18.webp" alt="Preview" data-v-6e07f87d></div></div></div> <button class="arrow right" data-v-6e07f87d></button> <div class="clickable-area right" data-v-6e07f87d></div></div> <div class="carousel-thumbnails" data-v-6e07f87d><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/K132-main-pictures_01.jpg" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-60261bcd-a23f-40e6-994d-ad97477dcec4.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-bceba3da-490a-41d8-9927-64d0279a3cb1.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-7e59fa08-5dec-48db-acc9-18559185ac7c.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-8147e39a-60dc-478c-af36-52c1953c438e.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-e3288169-9100-44f4-becd-afe1556f56b0.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-a354b178-8c1e-4e60-8338-77efe96ea8df.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-200999cf-cf5d-463d-911d-7b4c2f4222c1.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-e095a0f7-0c8c-414e-86bb-55e0148e55e9.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/16.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/17.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/18.webp" alt="Thumbnail" data-v-6e07f87d></div></div></div> <h2 id="description" data-id="Description">Description</h2> <p><strong>Cardputer</strong> is a card-sized computer designed for engineers, featuring an M5StampS3 as the main controller.<br>For human-machine interaction, it is equipped with a 56-key keyboard and a 1.14-inch TFT screen. The onboard SPM1423 digital MEMS microphone supports recording or wake-up functions, while the built-in cavity speaker enables audio playback. An infrared emitter provides IR control capability.<br>Expansion is provided via a Grove port for custom sensor connection, and a microSD card slot allows storage expansion.<br>Power is supplied by an internal 120 mAh battery plus a 1400 mAh battery in the base, greatly extending battery life. Integrated charge, boost and buck circuits are included.<br>The magnetic base can attach to metal surfaces and offers LEGO-compatible mounting holes.<br>Cardputer is ideal for rapid functional prototyping, industrial control, smart-home systems and more.</p><h2 id="note" data-id="Note">Note</h2> <div class="error"><div class="error-title">Disassembly Notice </div> <div class="error-content"> When removing the StampS3 module from the front panel, be very careful with the FPC cable and connector on the back. Gently pull it out to avoid damaging the screen connector. Refer to the operation video in the <a target="_blank" href="/en/accessory/Cardputer%20Accessory%20Kit">Cardputer Accessory Kit</a>.</div></div><h2 id="tutorial" data-id="Tutorial">Tutorial</h2> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/arduino/arduino_banner_01.png" alt="Arduino IDE"><a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-desc">This tutorial shows you how to program and control the Cardputer using the Arduino IDE.</div></div></div> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/uiflow2/uiflow2.0_banner_01.png" alt="UiFlow2"><a target="_blank" href="/en/uiflow2/cardputer/program">UiFlow2</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/uiflow2/cardputer/program">UiFlow2</a></div> <div class="learn-desc">This tutorial shows you how to control the Cardputer using the UiFlow2 graphical programming platform.</div></div></div><h2 id="features" data-id="Features">Features</h2> <ul><li>M5StampS3 microcontroller</li> <li>56-key keyboard</li> <li>1.14-inch TFT screen</li> <li>Cavity speaker and SPM1423 digital MEMS microphone</li> <li>Infrared emitter for IR control</li> <li>HY2.0-4P port for connecting and expanding I2C sensors</li> <li>microSD card slot for storage expansion</li> <li>Built-in 120 mAh battery plus 1400 mAh battery in the base for long battery life</li> <li>Magnetic base with LEGO-compatible mounting holes</li> <li>Development Platform<ul><li>UiFlow2</li> <li>Arduino IDE</li> <li>ESP-IDF</li> <li>PlatformIO</li></ul></li></ul> <h2 id="includes" data-id="Includes">Includes</h2> <ul><li>1 x Cardputer</li> <li>1 x Hex Key L-Shape 2.0mm (For M2 Screw)</li></ul> <h2 id="applications" data-id="Applications">Applications</h2> <ul><li>Rapid functional verification and prototyping</li> <li>Industrial control and automation</li> <li>Smart-home control systems</li> <li>Data acquisition and sensor monitoring</li> <li>Embedded system development and education</li> <li>Wireless communication and IoT projects</li></ul> <h2 id="specifications" data-id="Specifications">Specifications</h2> <div class="table-container"><table><thead><tr><th>Specification</th> <th>Parameter</th></tr></thead><tbody><tr><td>SoC</td> <td>ESP32-S3FN8 @ Xtensa® 32-bit LX7 dual-core processor, clock frequency 240MHz</td></tr> <tr><td>USB</td> <td>USB OTG, USB Serial/JTAG</td></tr> <tr><td>Flash</td> <td>8MB</td></tr> <tr><td>Wi-Fi</td> <td>2.4 GHz Wi-Fi</td></tr> <tr><td>Storage</td> <td>SD Card</td></tr> <tr><td>Keyboard</td> <td>56 keys (4 x 14)</td></tr> <tr><td>Buttons</td> <td>1 x Reset button + 1 x User button</td></tr> <tr><td>Grove</td> <td>1 x HY2.0-4P</td></tr> <tr><td>Battery Capacity</td> <td>120 mAh + 1400 mAh (in base)</td></tr> <tr><td>Screen</td> <td>ST7789V2 @ 1.14 inch, 240 x 135 px</td></tr> <tr><td>Speaker</td> <td>8 Ω @ 1 W I2S @ NS4168</td></tr> <tr><td>Microphone</td> <td>MEMS microphone @ SPM1423</td></tr> <tr><td>IR Emitting Distance</td> <td>410 cm at ∠0°, 170 cm at ∠45°, 66 cm at ∠90°</td></tr> <tr><td>Sleep Current</td> <td>DC 4.2 V @ 0.26 µA</td></tr> <tr><td>Working Current</td> <td>IR mode: DC 4.2 V @ 255.6 mA; Keyboard mode: DC 4.2 V @ 165.7 mA</td></tr> <tr><td>Operating Temperature</td> <td>0 ~ 40 °C</td></tr> <tr><td>Product Size</td> <td>84.0 x 54.0 x 19.7 mm</td></tr> <tr><td>Product Weight</td> <td>92.3 g</td></tr> <tr><td>Package Size</td> <td>145.7 x 95.0 x 20.7 mm</td></tr> <tr><td>Gross Weight</td> <td>109.9 g</td></tr></tbody></table></div><h2 id="learn" data-id="Learn">Learn</h2> <h3 id="download-mode" data-id="Download Mode">Download Mode</h3> <p>If you want to enter download mode, set the power switch on the side of the Cardputer to the <code>OFF</code> position, then press and hold the <code>G0</code> button before powering on. After supplying power to the device, release the button, and the device will enter download mode.</p><img alt="schematics" src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/cardputer%20(2).gif" width="30%"> <h3 id="charging-notes" data-id="Charging Notes">Charging Notes</h3> <p>When charging the Cardputer, please switch the power to <code>ON</code>.</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/K132-01.jpg" width="60%"> <h2 id="schematics" data-id="Schematics">Schematics</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5Cardputer.pdf">Cardputer Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5cardputer_Base.pdf">Cardputer Base Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2.pdf">Stamp-S3 Schematics PDF</a></li></ul> <div class="carousel-container" data-v-7d51a79c><div class="carousel-preview" data-v-7d51a79c><div class="clickable-area left" data-v-7d51a79c></div> <button class="arrow left" data-v-7d51a79c></button> <div class="carousel-images" data-v-7d51a79c><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-7d51a79c><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5Cardputer_sch_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5Cardputer_sch_02.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5cardputer_Base_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2_sch_01.png" alt="Preview" data-v-7d51a79c></div></div></div> <button class="arrow right" data-v-7d51a79c></button> <div class="clickable-area right" data-v-7d51a79c></div> <div class="corner-marker" data-v-7d51a79c>1/4</div></div> <div class="carousel-thumbnails" data-v-7d51a79c><div class="thumbnail active" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5Cardputer_sch_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5Cardputer_sch_02.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/481/Sch_M5cardputer_Base_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2_sch_01.png" alt="Thumbnail" data-v-7d51a79c></div></div></div> <h2 id="pinmap" data-id="PinMap">PinMap</h2> <h3 id="spm1423-mic" data-id="SPM1423 MIC">SPM1423 MIC</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G46</th> <th>G43</th> <th>3.3V</th> <th>GND</th></tr></thead><tbody><tr><td>SPM1423</td> <td>DAT</td> <td>CLK</td> <td>VCC</td> <td>GND</td></tr></tbody></table></div><h3 id="microsd-socket" data-id="microSD Socket">microSD Socket</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G12</th> <th>G14</th> <th>G40</th> <th>G39</th></tr></thead><tbody><tr><td>microSD Socket</td> <td>CS</td> <td>MOSI</td> <td>CLK</td> <td>MISO</td></tr></tbody></table></div><h3 id="st7789v2--rgb-led" data-id="ST7789V2  RGB LED">ST7789V2 & RGB LED</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G38</th> <th>G33</th> <th>G34</th> <th>G35</th> <th>G36</th> <th>G37</th></tr></thead><tbody><tr><td>ST7789V2</td> <td>DISP_BL</td> <td>RST</td> <td>RS</td> <td>DAT</td> <td>SCK</td> <td>CS</td></tr> <tr><td>RGB LED</td> <td>VDD</td> <td></td> <td></td> <td></td> <td></td> <td></td></tr></tbody></table></div><h3 id="keyboard--battery-detect" data-id="Keyboard  Battery Detect">Keyboard & Battery Detect</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G10</th> <th>G7/G6/G5/G4/G3/G15/G13</th> <th>G11/G9/G8</th></tr></thead><tbody><tr><td>Battery Detect (ADC)</td> <td>ADC</td> <td></td> <td></td></tr> <tr><td>74HC138</td> <td></td> <td>Y7~Y0</td> <td>A2/A1/A0</td></tr></tbody></table></div><h3 id="speaker--ir" data-id="Speaker  IR">Speaker & IR</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G41</th> <th>G42</th> <th>G43</th> <th>G44</th></tr></thead><tbody><tr><td>NS4168 (Speaker)</td> <td>BCLK</td> <td>SDATA</td> <td>LRCLK</td> <td></td></tr> <tr><td>IR</td> <td></td> <td></td> <td></td> <td>TX</td></tr></tbody></table></div><h3 id="hy20-4p" data-id="HY2.0-4P">HY2.0-4P</h3> <div class="grove-table-container"><div class="table-container"><table><thead><tr><th>HY2.0-4P</th> <th>Black</th> <th>Red</th> <th>Yellow</th> <th>White</th></tr></thead><tbody><tr><td>PORT.CUSTOM</td> <td>GND</td> <td>5V</td> <td>G2</td> <td>G1</td></tr></tbody></table></div></div><h2 id="model-size" data-id="Model Size">Model Size</h2> <img alt="module size" src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-401ac270-d997-4164-ae79-d28be7a3dfaf.png" width="100%"> <h2 id="structure" data-id="Structure">Structure</h2> <ul><li><a target="_blank" href="https://github.com/m5stack/M5_Hardware/tree/master/Products/K132_Cardputer/Structures">Cardputer Structure Files</a></li></ul> <h2 id="datasheets" data-id="Datasheets">Datasheets</h2> <ul><li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/SPM1423HM4H-B_datasheet_en.pdf">SPM1423</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/NS4168_CN_datasheet.pdf">NS4168</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf">ST7789V2</a></li></ul> <h2 id="softwares" data-id="Softwares">Softwares</h2> <h3 id="arduino" data-id="Arduino">Arduino</h3> <ul><li><a target="_blank" href="/en/arduino/m5cardputer/program">Cardputer Arduino Quick Start</a></li> <li><a target="_blank" href="https://github.com/m5stack/M5Cardputer">Cardputer Arduino Library</a></li></ul> <h3 id="uiflow2" data-id="UiFlow2">UiFlow2</h3> <ul><li><a target="_blank" href="/en/uiflow2/cardputer/program">Cardputer UiFlow2 Quick Start</a></li></ul> <h3 id="platformio" data-id="PlatformIO">PlatformIO</h3> <div class="code-block-wrapper"><div class="code-line-container"><pre><code class="hljs language-bash">[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-          -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code></pre> <button class="copy-all-btn"><code>[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-          -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code> <div class="fa-solid fa-copy"></div></button></div></div> <h3 id="esp-idf" data-id="ESP-IDF">ESP-IDF</h3> <ul><li><a target="_blank" href="https://github.com/m5stack/M5Cardputer-UserDemo">Cardputer Factory Firmware</a></li></ul> <h3 id="easyloader" data-id="Easyloader">Easyloader</h3> <div class="table-container"><table><thead><tr><th>Easyloader</th> <th>Download</th> <th>Note</th></tr></thead><tbody><tr><td>Cardputer User Demo Easyloader</td> <td><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/Cardputer.exe">download</a></td> <td>/</td></tr></tbody></table></div><h2 id="video" data-id="Video">Video</h2> <div class="video-gallery-island" data-v-5e05839f></div> <h2 id="product-comparison" data-id="Product Comparison">Product Comparison</h2> <p>To compare information on the Cardputer series products, you can visit the <a target="_blank" href="/en/products_selector/m5cardputer_compare?select=K132">Product Selection Table</a>, check the target products, and get the comparison results. The selection table covers key information such as core parameters and functional features, and supports comparison of multiple products simultaneously.</p></div> <!----> <!----> <!----></div></div> <div class="docs-layouts-anchor"><div class="page-tools" data-v-39baf185><div class="page-tools-title" data-v-39baf185>Page Tools</div> <div class="page-tools-actions" data-v-39baf185><a href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/Cardputer.pdf" target="_blank" rel="nofollow noopener noreferrer" title="Download PDF" class="page-tools-action page-tools-pdf" data-v-39baf185><svg viewBox="0 0 24 24" aria-hidden="true" class="page-tools-icon" data-v-39baf185><path d="M6 2h8l4 4v16H6V2zm7 1.8V7h3.2L13 3.8zM8.4 12.2h1.5c1 0 1.7-.6 1.7-1.6S10.9 9 9.9 9H7v6h1.4v-2.8zm0-1.1v-1h1.3c.3 0 .5.2.5.5s-.2.5-.5.5H8.4zm4.1 3.9h1.8c1.7 0 2.8-1.1 2.8-3s-1.1-3-2.8-3h-1.8v6zm1.4-1.2v-3.6h.4c.9 0 1.4.6 1.4 1.8s-.5 1.8-1.4 1.8h-.4zm4.1 1.2h1.4v-2.4h2.1v-1.2h-2.1v-1.2h2.4V9H18v6z" data-v-39baf185></path></svg> <span data-v-39baf185>PDF</span></a> <div class="markdown-action-menu placement-toolbox" data-v-5d6a4f8a data-v-39baf185><button type="button" title="Copy page" class="markdown-action-trigger" data-v-5d6a4f8a><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><rect x="9" y="9" width="13" height="13" rx="2"></rect><path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1"></path></svg> <span data-v-5d6a4f8a>Copy page</span> <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><polyline points="6 9 12 15 18 9"></polyline></svg></button> <!----></div></div></div></div></div> <footer><div class="footer-container"><div class="footer-content-wrap"><div class="footer-nav"><div class="footer-nav-item"><div data-id="0" class="footer-nav-title"><a class="footer-nav-title-a">
-        About Us
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/about-us">About M5Stack</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?page=1">News</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?type=blog&page=1">Blog</a></li><li class="footer-nav-li"><a href="https://m5stack.com/events">Events</a></li><li class="footer-nav-li"><a href="https://m5stack.com/contact">Contact Us</a></li></ul></div><div class="footer-nav-item"><div data-id="1" class="footer-nav-title"><a class="footer-nav-title-a">
-        Where to buy
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/distributor">Distributors</a></li><li class="footer-nav-li"><a href="https://shop.m5stack.com/">Official Store</a></li><li class="footer-nav-li"><a href="https://m5stack.aliexpress.com/store/911661199">AliExpress</a></li><li class="footer-nav-li"><a href="https://www.amazon.com/shops/m5stack">Amazon</a></li><li class="footer-nav-li"><a href="https://m5stack.taobao.com/">Taobao</a></li></ul></div><div class="footer-nav-item"><div data-id="2" class="footer-nav-title"><a class="footer-nav-title-a">
-        Solution
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/business">For Business</a></li><li class="footer-nav-li"><a href="https://m5stack.com/developers">For Developers</a></li></ul></div><div class="footer-nav-item"><div data-id="3" class="footer-nav-title"><a class="footer-nav-title-a">
-        Software
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://flow.m5stack.com/">UiFlow1</a></li><li class="footer-nav-li"><a href="https://uiflow2.m5stack.com/">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/uiflow/m5burner/intro">M5Burner</a></li><li class="footer-nav-li"><a href="https://block-designer.m5stack.com/">Block Designer</a></li><li class="footer-nav-li"><a href="/en/guide/ezdata/ezdata_v2">EzData 2.0</a></li><li class="footer-nav-li"><a href="/en/guide/easyloader/easyloader_packer">EasyLoader Packer</a></li><li class="footer-nav-li"><a href="/en/guide/develop_tools/vlw_font_creator">VLW Font Creator</a></li><li class="footer-nav-li"><a href="/en/download">Device USB Driver</a></li></ul></div><div class="footer-nav-item"><div data-id="4" class="footer-nav-title"><a class="footer-nav-title-a">
-        Documentation
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="/en/products">Product Documents</a></li><li class="footer-nav-li"><a href="/en/uiflow/uiflow_web">UiFlow1</a></li><li class="footer-nav-li"><a href="/en/uiflow2/uiflow_web">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/arduino/arduino_ide">Arduino</a></li><li class="footer-nav-li"><a href="/en/esp_idf/esp_idf">ESP-IDF</a></li><li class="footer-nav-li"><a href="/en/stackflow/overview">StackFlow AI</a></li><li class="footer-nav-li"><a href="/en/homeassistant/overview">Home Assistant</a></li><li class="footer-nav-li"><a href="https://github.com/nanoframework/nanoFramework.M5Stack">nanoFramework</a></li><li class="footer-nav-li"><a href="/en/guide/product_guide">Product Guide</a></li><li class="footer-nav-li"><a href="/en/certification">Product Certifications</a></li><li class="footer-nav-li"><a href="/en/product_i2c_addr">I2C Table</a></li><li class="footer-nav-li"><a href="/en/products_selector/m5core_compare">Product Selector</a></li><li class="footer-nav-li"><a href="https://github.com/m5stack/M5_Hardware">Hardware Design Files</a></li><li class="footer-nav-li"><a href="/en/history">Release History</a></li><li class="footer-nav-li"><a href="/en/compatible_stack">Stack Compatibility</a></li><li class="footer-nav-li"><a href="/en/learn/extension/module">Stack Screw Length</a></li></ul></div></div> <div class="footer-right"><div class="footer-email-group"><p class="footer-email-title">
-              Stay in the Loop
-            </p> <p class="footer-email-desc">
-              Weekly updates on new products, innovations, and announcements.
-            </p> <div class="footer-email-input"><input placeholder="Enter Email address" autocomplete="off" class="email-input"> <button type="button" class="subscribe-btn">
-                Subscribe
-              </button></div> <p class="footer-email-warning" style="display:none">
-              Email is invalid!
-            </p></div> <div class="footer-email-success" style="display:none">
-            Thanks for subscribing
-          </div> <div class="footer-follow"><div class="footer-follow-ul"><a href="https://x.com/M5Stack"><img src="/assets/footer/sociallist10.svg" alt></a><a href="https://www.linkedin.com/company/m5stack"><img src="/assets/footer/sociallist2.svg" alt></a><a href="https://www.instagram.com/m5stack"><img src="/assets/footer/sociallist8.svg" alt></a><a href="https://www.facebook.com/M5Stack"><img src="/assets/footer/sociallist7.svg" alt></a><a href="https://www.youtube.com/m5stack"><img src="/assets/footer/sociallist5.svg" alt></a><a href="https://www.tiktok.com/@m5stack"><img src="/assets/footer/tiktok.svg" alt></a><a href="https://www.hackster.io/m5stack"><img src="/assets/footer/sociallist3.svg" alt></a><a href="https://discord.gg/ysQAWBUE9Q"><img src="/assets/footer/sociallist4.svg" alt></a><a href="https://github.com/m5stack"><img src="/assets/footer/sociallist6.svg" alt></a></div></div> <div class="footer-info-wrapper"><div class="footer-info">
-            M5Stack Technology Co., Ltd
-          </div> <div class="footer-address-info">
-            Address: 
-             Block A10, Expo Bay South Coast, Fuhai Street, Bao'an District, Shenzhen, China
-          </div> <div class="footer-info">
-            TEL: 
-            +86 755 8657 5379
-          </div> <div class="footer-info">
-            Email: 
-            support@m5stack.com
-          </div></div></div></div></div> <div class="footer-bottom"><div class="footer-bottom-content"><div class="footer-copy">
-        Copyright ©
-        <a href="https://m5stack.com/">M5Stack Technology Co., Ltd.</a>
-        All rights reserved.
-      </div> <div class="terms-box"><!----> <a href="https://shop.m5stack.com/policies/privacy-policy">Privacy Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/terms-of-service">Terms of Service</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/shipping-policy">Shipping Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/refund-policy">Refund Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/pages/payment-method">Payment Method</a></div> <div class="beian"><a href="https://beian.miit.gov.cn/">粤ICP备16010631号</a></div></div></div> <!----></footer> <div class="float-icon-container"><div class="totop-icon"><svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 280 280" xmlns:xlink="http://www.w3.org/1999/xlink" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M143 70l58 69c1,1 1,3 1,4 -1,1 -2,2 -4,2l-20 0c-2,0 -4,2 -4,4l1 57c0,2 -2,4 -4,4l-62 0c-2,0 -4,-2 -4,-4l1 -57c0,-2 -2,-4 -4,-4l-20 0c-2,0 -3,-1 -4,-2 -1,-1 0,-3 1,-4l58 -69c1,-1 2,-1 3,-1 1,0 2,1 3,1z" class="fil1"></path></g></svg></div> <div class="menu-icon" style="display:none"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 800 800" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M253 229l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 370l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 511l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path></g></svg></div></div></div></div></div></div><script defer src="/_nuxt/static/1788504562/en/core/Cardputer/state.js"></script><script src="/_nuxt/41d5c62.js" defer></script><script src="/_nuxt/c970150.js" defer></script><script src="/_nuxt/5a34d22.js" defer></script><script src="/_nuxt/a352c6d.js" defer></script><script src="/_nuxt/b9c4bc6.js" defer></script>
-  </body>
-</html>
diff --git a/devices/m5stack/cardputer-v1.0/certification-and-compliance.md b/devices/m5stack/cardputer-v1.0/certification-and-compliance.md
deleted file mode 100644
index b4978b3..0000000
--- a/devices/m5stack/cardputer-v1.0/certification-and-compliance.md
+++ /dev/null
@@ -1,124 +0,0 @@
-# Certification and compliance — cardputer-v1.0
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-One Cardputer grant covers the family; it does not distinguish v1.0 from v1.1.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5CARDPUTER` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5CARDPUTER`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-07-22** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-07-22 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5CARDPUTER` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 1,811,474 | `daafa38179323ddb…` |
-| `ID-Label-Location-Info-FCC-ID-Label.pdf` | 467,757 | `fcdfbce02de768d7…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,588,902 | `04d0f83f4d202d9f…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE.pdf` | 126,467 | `6c89ae08c922ccde…` |
-| `Test-Report-Antenna-Specification.pdf` | 822,846 | `0728acb7f328e39c…` |
-| `Users-Manual-User-Manual.pdf` | 3,165,025 | `629df489491ef940…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5CARDPUTER/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5CARDPUTER/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cardputer-v1.0/market-and-pricing.md b/devices/m5stack/cardputer-v1.0/market-and-pricing.md
deleted file mode 100644
index 1720b39..0000000
--- a/devices/m5stack/cardputer-v1.0/market-and-pricing.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Market and pricing — cardputer-v1.0
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| [EOL] M5Stack Cardputer Kit w/ M5StampS3 | 2023-10-13 | Default Title | `K132` | **USD 23.90** | ❌ no |
-| [EOL] Cardputer Accessory Kit (M5StampS3 + Display) | 2024-08-12 | Default Title | `A145` | **USD 9.95** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 23.90, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/m5stack-cardputer-kit-w-m5stamps3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-`K132` is the **complete kit** (StampS3 + keyboard + shell); `A145` is the **accessory kit only** (no Stamp). ⚠ These are *not* comparable — one is a whole device at USD 23.90, the other a USD 9.95 parts bundle. Both are `[EOL]`, `available: false`.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cardputer-v1.1/README.md b/devices/m5stack/cardputer-v1.1/README.md
deleted file mode 100644
index f732bb4..0000000
--- a/devices/m5stack/cardputer-v1.1/README.md
+++ /dev/null
@@ -1,195 +0,0 @@
-# M5Stack Cardputer v1.1 (K132-V11)
-
-> **SKU `K132-V11`** · product id **`1127`** · Shopify `8741357388033`
-> Launched **2025-03-07** · **marked `[EOL]` on M5Stack's own store as of 2026-09-04**, yet still
-> listed at **$29.90** — the same price as the ADV that replaces it.
-> Core module: **Stamp-S3A** (`Sch_StampS3_v0.3.3`). Research snapshot **2026-09-04**.
-
-The middle Cardputer. It is a **module refresh of the v1.0, not a new board**: M5Stack publishes
-the *same mainboard schematic file* for both, and its own comparison table lists only
-module-level differences.
-
-This record is deliberately lighter than the ADV's. Everything the two share — display, microSD,
-IR, Grove, USB, power train — is documented once, in depth, at
-[`../cardputer-adv/`](../cardputer-adv/README.md), and linked from here rather than repeated.
-
----
-
-## Identity
-
-| Field | Value | Evidence |
-|---|---|---|
-| Name | Cardputer v1.1 | product page |
-| SKU | `K132-V11` | product page |
-| Store title | **`[EOL]` M5Stack Cardputer with M5StampS3 v1.1** | Shopify, 2026-09-04 |
-| Core module | **Stamp-S3A** | product page + comparison table |
-| SoC | ESP32-S3FN8, 8 MB flash, **no PSRAM** | spec table |
-| Mainboard schematic | `…/1127/Sch_M5Cardputer.pdf` — **byte-identical to the v1.0's** | SHA-256 `6016c1fe…`, 717 743 B |
-| Base schematic | `…/1127/M5Cardputer_Base.pdf` — likewise identical | `29542fe1…`, 24 076 B |
-| Size / weight | 84.0 × 54.0 × 19.7 mm, 90.0 g | spec table |
-| Battery | **120 mAh internal + 1400 mAh in the base** | spec table |
-| Includes | 1 × Cardputer v1.1, 1 × **1.5 mm** hex key (the v1.0 shipped a **2.0 mm** one) | product page |
-
-## What actually changed from v1.0
-
-M5Stack's own comparison table, verbatim in substance:
-
-| | Cardputer v1.0 | **Cardputer v1.1** |
-|---|---|---|
-| Core module | StampS3 | **Stamp-S3A** |
-| RGB LED control | "Powered immediately upon power-on" | "**shares power with screen backlight**, optimized control logic" |
-| Antenna | standard | "optimized … better signal reception" |
-| Boot key | 2.6 × 1.6 × 0.55 mm | **4.0 × 3.0 × 2.0 mm** |
-| Power consumption | standard | "optimized for lower" |
-
-Corroborated by the two Stamp schematics:
-
-| | StampS3 `v0.2` | **Stamp-S3A `v0.3.3`** |
-|---|---|---|
-| 3.3 V rail | `M2` = **Murata `MUN3CAD01-SC` µPOL** 1 A power module | **JoulWatt `JW5712`** buck, 0–0.6 A, `VSEL` strapped |
-| Load switch | **SGM2578** (U2) | **AW35122FDR** (U2), enabled by `DISP_BL` |
-| **WS2812 supply** | **`VDD_3V3`** (always on) | **`BL_3V3`** (switched backlight rail) |
-| Solder jumper JP4 at the WS2812 | present | removed |
-| Crystal load caps | 12 pF / 10 pF | 12 pF / 12 pF |
-
-Sleep current improves from **0.26 µA to 0.15 µA**; both figures are vendor claims under
-unstated conditions.
-
-## ⚠ The RGB LED / backlight interaction
-
-Only the v1.1 page states it, and it applies verbatim to the ADV as well:
-
-> "Since RGB and LCD backlight share the same power source, when the LCD backlight brightness is
-> below 100%, RGB will not be powered properly. Please use the RGB function when the backlight is
-> at full brightness."
-
-Mechanism: G38 (`DISP_BL`) → **AW35122FDR** enable → `BL_3V3` → LCD backlight **and** WS2812.
-PWM-dimming the backlight chops the LED's supply. On the **v1.0** the WS2812 sits on the
-always-on `VDD_3V3` and this does not happen — so this is a *regression* introduced by the
-Stamp-S3A, traded for the lower sleep current.
-
-## The keyboard — 74HC138 GPIO matrix
-
-The whole reason the ADV exists. See [`../cardputer-adv/features/keyboard.md`](../cardputer-adv/features/keyboard.md)
-for the full comparison and the proof that the two matrices are electrically identical.
-
-```
-ESP32-S3 G8/G9/G11 ──► 74HC138 (U7) A0/A1/A2
-                        /E1, /E2 → GND ;  E3 → +3.3V
-                        Y0..Y7 ──► R34..R27 (22 Ω 1 %) ──► the 8-line Y bus
-56 × SW-PB (S1..S56) matrix
-7 sense lines ──► G13, G15, G3, G4, G5, G6, G7   (INPUT_PULLUP)
-```
-
-Read from the rendered sheet: U7 pin 1 = `A0` ← **G8**, pin 2 = `A1` ← **G9**,
-pin 3 = `A2` ← **G11**, pins 4/5 = `/E1`,`/E2` → GND, pin 6 = `E3` → +3.3 V,
-pin 7 = `Y7` → R27, pins 9–15 = `Y6..Y0` → R28…R34, pin 16 = `VCC`, pin 8 = `GND`.
-
-Vendor driver, [`IOMatrix.cpp`](https://github.com/m5stack/M5Cardputer/blob/f1392858b9994c3547120e602a57d3553d16ab01/src/utility/Keyboard/KeyboardReader/IOMatrix.cpp):
-
-```cpp
-const std::vector<int> output_list = {8, 9, 11};                  // 74HC138 A0,A1,A2
-const std::vector<int> input_list  = {13, 15, 3, 4, 5, 6, 7};     // 7 sense lines
-const Chart_t X_map_chart[7] = {{1,0,1},{2,2,3},{4,4,5},{8,6,7},{16,8,9},{32,10,11},{64,12,13}};
-…
-for (int i = 0; i < 8; i++) { set_output(output_list, i); input_value = get_input(input_list); … }
-coor.x = (i > 3) ? X_map_chart[j].x_1 : X_map_chart[j].x_2;
-coor.y = (i > 3) ? (i - 4) : i;  coor.y = -coor.y + 3;
-```
-
-Scanning is **fully synchronous polling**: eight address settings per `update()`, seven
-`digitalRead()`s each, no interrupt, no debounce hardware. Sense lines are `INPUT_PULLUP` and the
-switch pulls low, so `pin_value = (digitalRead(pin) == 1) ? 0 : 1`.
-
-**Cost: ten GPIOs**, which is why the v1.x has no expansion beyond the Grove port.
-
-## Audio — NS4168 + SPM1423, no codec
-
-| | v1.x | ADV |
-|---|---|---|
-| Speaker | **NS4168** I²S class-D → 8 Ω 1 W cavity | ES8311 codec + NS4150B |
-| Mic | **SPM1423** PDM MEMS | analog MEMS via the codec ADC |
-| 3.5 mm jack | **none** | present |
-| I²S pins | G41 `BCLK`, G43 `LRCK`, G42 `SDATA`, G46 mic `DAT`, G43 mic `CLK` | same four pins |
-
-M5Unified sets only `pin_data_in = G46` and `pin_ws = G43` for the mic on the v1.x — **no
-`pin_bck`**, because a PDM microphone needs a clock and a data line, not a full I²S frame.
-The ADV row adds `pin_bck = GPIO_NUM_41`.
-
-Because the pins are the same, **v1.x audio code appears to "almost work" on an ADV**: the I²S
-peripheral configures fine and nothing comes out, because the codec was never enabled.
-
-Datasheets M5Stack links for this board: `SPM1423HM4H-B_datasheet_en.pdf`,
-`NS4168_CN_datasheet.pdf` (Chinese only), `ST7789V2_SPEC_V1.0.pdf`. They file under the
-components: [`knowles/spm1423hm4h-b`](../../../components/knowles/spm1423hm4h-b/README.md),
-[`nsiway/ns4168`](../../../components/nsiway/ns4168/README.md),
-[`sitronix/st7789v2`](../../../components/sitronix/st7789v2/README.md).
-
-## Pin map
-
-| Function | Pins |
-|---|---|
-| Keyboard drive (74HC138 A0/A1/A2) | G8, G9, G11 |
-| Keyboard sense | G13, G15, G3, G4, G5, G6, G7 |
-| Battery ADC | G10 |
-| microSD | CS G12, MOSI G14, SCK G40, MISO G39 |
-| Display | BL G38, RST G33, DC G34, MOSI G35, SCK G36, CS G37 |
-| RGB LED | G21 |
-| Speaker (NS4168) | BCLK G41, LRCLK G43, SDATA G42 |
-| Mic (SPM1423) | CLK G43, DAT G46 |
-| IR TX | G44 |
-| Grove | G1, G2 |
-| Boot | G0 |
-| **Internal I²C** | **none** (`_pin_table_i2c_ex_in` = `255, 255`) |
-
-Everything except the keyboard rows is identical to the ADV.
-
-## Components
-
-| Part | Designator | Record |
-|---|---|---|
-| 74HC138 | U7 | [`generic/74hc138`](../../../components/generic/74hc138/README.md) |
-| NS4168 | — | [`nsiway/ns4168`](../../../components/nsiway/ns4168/README.md) |
-| SPM1423HM4H-B | M1 | [`knowles/spm1423hm4h-b`](../../../components/knowles/spm1423hm4h-b/README.md) |
-| ST7789V2 | on the FPC | [`sitronix/st7789v2`](../../../components/sitronix/st7789v2/README.md) |
-| ESP32-S3FN8 | in the module | [`espressif/esp32-s3fn8`](../../../components/espressif/esp32-s3fn8/README.md) |
-| Stamp-S3A | module | [`m5stack/stamp-s3a`](../../../components/m5stack/stamp-s3a/README.md) |
-| AW35122FDR / JW5712 / SGM2578 | on the module | [`awinic/aw35122`](../../../components/awinic/aw35122/README.md) · [`joulwatt/jw5712`](../../../components/joulwatt/jw5712/README.md) · [`sgmicro/sgm2578`](../../../components/sgmicro/sgm2578/README.md) |
-| WS2812 | U3 on the module | [`worldsemi/ws2812`](../../../components/worldsemi/ws2812/README.md) |
-| TP4057 / SY7088 / SY8089 / CN809J | U1 / U2 / U4 / U3 | [`generic/tp4057`](../../../components/generic/tp4057/README.md) · [`silergy/sy7088`](../../../components/silergy/sy7088/README.md) · [`silergy/sy8089`](../../../components/silergy/sy8089/README.md) · [`consonance/cn809`](../../../components/consonance/cn809/README.md) |
-| LP3218DT1G | Q1–Q3 | [`unidentified/cardputer/lp3218dt1g`](../../../components/unidentified/cardputer/lp3218dt1g/README.md) |
-
-## Development
-
-Identical to the ADV — same PlatformIO profile, same download-mode procedure, same
-`M5Cardputer` library, which autodetects and installs `IOMatrixKeyboardReader` instead.
-See [`../cardputer-adv/development.md`](../cardputer-adv/development.md).
-
-Factory firmware: `github.com/m5stack/M5Cardputer-UserDemo` **`main`** branch
-(`a34d7ebcd508fb903a2b1123be8c8b54abd55d07`, 2026-07-17) — *not* the `CardputerADV` branch.
-EasyLoader: `m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/Cardputer.exe`
-(**shared with the v1.0** — a further instance of the vendor guide's "variant assets live under
-the parent product" pattern).
-
-## Community firmware
-
-Broadest support of any Cardputer: Bruce, Launcher, Marauder, **Evil-M5Project**, NEMO,
-MicroHydra and every emulator all target it. It loses upstream **Meshtastic** (ADV-only variant)
-and every 2026 ADV-only project. Full matrix:
-[`../cardputer-adv/compatibility-and-status.md`](../cardputer-adv/compatibility-and-status.md).
-
-## Should you buy one?
-
-**No, not at $29.90 with the ADV at the same price** — see
-[`../cardputer-adv/comparisons-and-recommendations.md`](../cardputer-adv/comparisons-and-recommendations.md) §1.
-The only defensible reasons are a firmware that has not been ported (Evil-M5Project's ADV
-support is unconfirmed; NEMO has no ADV config) or a deliberate wish for the simpler,
-fully-GPIO keyboard.
-
-## Sources
-
-Product page `https://docs.m5stack.com/en/core/Cardputer%20V1.1` (retrieved 2026-09-04,
-snapshot at `artifacts/docs-en-core-Cardputer-V1.1.html`);
-schematics `artifacts/schematic/` (`6016c1fe…`, `29542fe1…`);
-`M5Cardputer` @ `f1392858`; `M5Unified` @ `8530f537`; Shopify `<handle>.json` 2026-09-04.
-Full table: [`../cardputer-adv/sources.md`](../cardputer-adv/sources.md).
diff --git a/devices/m5stack/cardputer-v1.1/artifacts/docs-en-core-Cardputer-V1.1.html b/devices/m5stack/cardputer-v1.1/artifacts/docs-en-core-Cardputer-V1.1.html
deleted file mode 100644
index b8eee1e..0000000
--- a/devices/m5stack/cardputer-v1.1/artifacts/docs-en-core-Cardputer-V1.1.html
+++ /dev/null
@@ -1,113 +0,0 @@
-<!doctype html>
-<html data-n-head-ssr lang="en" data-n-head="%7B%22lang%22:%7B%22ssr%22:%22en%22%7D%7D">
-  <head>
-    <title>m5-docs</title><meta data-n-head="ssr" charset="utf-8"><meta data-n-head="ssr" name="viewport" content="width=device-width,initial-scale=1,minimum-scale=1,user-scalable=no"><meta data-n-head="ssr" data-hid="description" name="description" content="The reference docs for M5Stack products. Quick start, get the detailed information or instructions such as IDE,UIFLOW,Arduino. The tutorials for M5Burner, Firmware, Burning, programming. ESP32,M5StickC,StickV, StickT,M5ATOM."><link data-n-head="ssr" rel="icon" type="image/x-icon" href="/favicon.ico"><script data-n-head="ssr" data-hid="device-preload-detector">!function(){try{var e=document.documentElement;if(!e)return;var d=e.clientWidth||Number.POSITIVE_INFINITY,i=Number(window.innerWidth||0)||Number.POSITIVE_INFINITY,a=Math.min(d,i)<1024;e.classList.add(a?"device-preload-mobile":"device-preload-desktop"),a&&(e.classList.add("device-preload-pending"),window.__m5DevicePreloadReady=function(){e.classList.remove("device-preload-pending"),e.classList.add("device-preload-ready")})}catch(e){}}()</script><script data-n-head="ssr" src="https://cloud.umami.is/script.js" data-website-id="38e73ff2-ec10-4a8f-bfe2-c22a381ce306" defer></script><script data-n-head="ssr" src="/script/ga.js"></script><script data-n-head="ssr" src="/script/global.js"></script><script data-n-head="ssr" src="/public/esp-web-tools/install-button.js?module" type="module"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/marked.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/highlight.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-chat/index.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-qa/index.js"></script><link rel="preload" href="/_nuxt/41d5c62.js" as="script"><link rel="preload" href="/_nuxt/5a34d22.js" as="script"><link rel="preload" href="/_nuxt/a352c6d.js" as="script"><link rel="preload" href="/_nuxt/b9c4bc6.js" as="script"><link rel="preload" href="/_nuxt/c970150.js" as="script"><style data-vue-ssr-id="0b40e9c2:0 afa51714:0 73039f54:0 2576b79a:0 69f1b16c:0 17a511fe:0 3d88442c:0 3afe6180:0 786f8504:0 1af4924a:0 e762b0ec:0 e646c77c:0 4a658548:0 5f76b520:0 3e555512:0 4e0caf6f:0 060bbeb3:0 3ddd7ff2:0 bb0e6f22:0 27d15a7c:0 2c0daf93:0 d1c8934a:0 09fcdd3b:0 3231c87d:0 8716e91a:0 09d04477:0">body,html{width:100%;margin:0;padding:0}html.device-preload-mobile.device-preload-pending{background:linear-gradient(180deg,#f7f9fc,#eef3f8)}html.device-preload-mobile.device-preload-pending body{background:0 0}html.device-preload-mobile.device-preload-pending body:before{content:"";position:fixed;top:0;right:0;bottom:0;left:0;z-index:9999;pointer-events:none;background:linear-gradient(180deg,hsla(0,0%,100%,.92),rgba(243,247,251,.98)),radial-gradient(circle at top right,rgba(0,100,194,.08),transparent 38%)}html.device-preload-mobile.device-preload-pending body:after{content:"";position:fixed;left:50%;top:50%;width:.63529rem;height:.63529rem;margin-left:-.31765rem;margin-top:-.31765rem;z-index:10000;pointer-events:none;border:.04706rem solid rgba(35,141,251,.18);border-top-color:#238dfb;border-radius:50%;box-shadow:0 0 0 .09412rem rgba(35,141,251,.08);-webkit-animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite;animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite}html.device-preload-mobile.device-preload-pending .device-hydration-sensitive{opacity:0;visibility:hidden}html.device-preload-mobile.device-preload-ready body:after,html.device-preload-mobile.device-preload-ready body:before{opacity:0;transition:opacity .22s ease}html.device-preload-mobile.device-preload-ready .device-hydration-sensitive{visibility:visible;opacity:1;transition:opacity .18s ease}@-webkit-keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@-webkit-keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}@keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}html{overflow:hidden;overflow-y:auto}html::-webkit-scrollbar{width:.14118rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}@font-face{font-family:SourceCodePro;src:url(https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/font/SourceCodePro-Regular.ttf)}body,button{font-family:SourceCodePro,Microsoft YaHei;line-height:inherit;box-sizing:border-box}body,button,input{font-family:SourceCodePro,Microsoft YaHei,sans-serif}a{outline:0}.product_pic img{width:33%}.page-enter-active,.page-leave-active{transition:opacity .5s}.page-enter,.page-leave-active{opacity:0}.bounce-enter-active{-webkit-animation:bounce-in .8s;animation:bounce-in .8s}.bounce-leave-active{-webkit-animation:bounce-out .5s;animation:bounce-out .5s}@-webkit-keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@-webkit-keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}body,button,html[lang=zh-cn] footer,html[lang=zh-cn] header,input{font-family:Microsoft YaHei,sans-serif}html[lang=en] footer,html[lang=en] header{font-family:Montserrat,Microsoft YaHei,sans-serif}@font-face{font-family:Montserrat;font-weight:400;font-style:normal;src:url(/assets/fonts/Montserrat-Regular.woff2) format("woff2"),url(/assets/fonts/Montserrat-Regular.woff) format("woff"),url(/assets/fonts/Montserrat-Regular.otf) format("opentype"),url(/assets/fonts/Montserrat-Regular.ttf) format("truetype")}@font-face{font-family:Montserrat;font-weight:500;font-style:normal;src:url(/assets/fonts/Montserrat-Medium.woff2) format("woff2"),url(/assets/fonts/Montserrat-Medium.woff) format("woff"),url(/assets/fonts/Montserrat-Medium.otf) format("opentype"),url(/assets/fonts/Montserrat-Medium.ttf) format("truetype")}*{margin:0;padding:0;box-sizing:border-box}html{height:auto!important;font-size:10vw;line-height:1}@media screen and (max-width:320px){html{font-size:32PX}}@media screen and (min-width:540px){html{font-size:44PX}}@media screen and (min-width:860px){html{font-size:48PX}}@media screen and (min-width:960px){html{font-size:49PX}}@media screen and (min-width:1024px){html{font-size:52PX}}@media screen and (min-width:1175px){html{font-size:53PX}}@media screen and (min-width:1280px){html{font-size:56PX}}@media screen and (min-width:1366px){html{font-size:63PX}}@media screen and (min-width:1400px){html{font-size:68PX}}@media screen and (min-width:1440px){html{font-size:69PX}}@media screen and (min-width:1540px){html{font-size:73PX}}@media screen and (min-width:1680px){html{font-size:75PX}}@media screen and (min-width:1920px){html{font-size:75PX}}@media screen and (min-width:2560px){html{font-size:85PX}}body{-webkit-font-smoothing:subpixel-antialiased}li{list-style-type:none}img,li{-webkit-user-drag:none}img{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}a{text-decoration:none;-webkit-user-drag:none}a,button{outline:0}button{border:none;background-color:transparent;cursor:pointer}.fade-enter-active,.fade-leave-active{transition:opacity .5s}.fade-enter,.fade-leave-to{opacity:0}.markdown.guide img{box-shadow:0 -.07059rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);margin-top:.17647rem;margin-bottom:.58824rem;margin-left:.11765rem}.markdown.guide .blockly_svg{box-shadow:unset;margin:.17647rem 0 .05882rem;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content}.docs-layouts{padding-top:.58824rem;display:flex;justify-content:center;position:relative;margin-bottom:.35294rem}.docs-layouts .docs-layouts-sidebar{position:sticky;top:1.17647rem;left:0;height:-webkit-max-content;height:-moz-max-content;height:max-content;z-index:2;background-color:#fff}.docs-layouts .docs-layouts-title{display:flex;flex-direction:row;margin-bottom:.11765rem;align-items:center;width:100%;height:.47059rem;border-bottom:.03529rem solid #f5f5f5}.docs-layouts .docs-layouts-title .docs-layouts-icon{background-color:#238dfb;border-radius:.11765rem;display:flex;justify-content:center;align-items:center;height:.35294rem;width:.35294rem;margin-right:.11765rem}.docs-layouts .docs-layouts-title .docs-layouts-icon img{width:.23529rem;height:.23529rem}.docs-layouts .docs-layouts-title p{font-size:.23529rem;font-weight:700;color:#2f495e;line-height:.35294rem}.docs-layouts .docs-layouts-body{width:14.11765rem;min-width:0;max-width:100%;margin:0 .29412rem}.docs-layouts .docs-layouts-anchor{position:sticky;top:1.2rem;right:0;z-index:1;background-color:#fff;height:80vh;overflow-y:scroll}@media screen and (max-width:1200px){.docs-layouts .docs-layouts-anchor{display:none}}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar{width:.14118rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.mobile .docs-layouts{padding:.35294rem;display:flex}.mobile .docs-layouts .docs-layouts-body{width:100%;min-width:0;max-width:100%;margin:0}.mobile .docs-layouts .docs-layouts-sidebar{position:fixed;height:100vh;width:5.17647rem;top:0;padding:.47059rem .35294rem;left:auto;left:-100%;box-shadow:.11765rem .23529rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);transition:all .25s ease;z-index:5}.mobile .docs-layouts .docs-layouts-sidebar.active{left:0}.default{color:#3f3f46}.primary{color:#006fee}.secondary{color:#9353d3}.success{color:#17c964}.warning{color:#f5a524}.danger{color:#f31260}.markdown{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-column-gap:.18824rem;-moz-column-gap:.18824rem;column-gap:.18824rem;min-width:0;max-width:100%;overflow:hidden;word-break:break-word;padding-bottom:.35294rem;color:#4f5f6f;font-size:.18824rem;font-weight:400}.markdown>*{grid-column:1/-1}.markdown .product-sku{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .product-date,.markdown .product-sku{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.09412rem 0 .09412rem .09412rem;display:inline-block}.markdown .product-date{background-color:#efefef;color:#345b83}.markdown .tag-green{background-color:#f0fff4;color:#00c58e}.markdown .tag-blue,.markdown .tag-green{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.11765rem;display:inline-block}.markdown .tag-blue{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .tag-orange{font-size:.23529rem;margin:.23529rem .23529rem .23529rem 0;border-radius:.03529rem;padding:.02353rem .11765rem;background-color:#f8b013;color:#fff;cursor:pointer}.markdown .product-title{display:flex;align-items:center}.markdown .product-title span{color:#2f495e}.markdown .shop-title{display:flex;justify-content:space-between;position:relative;margin:.02353rem 0 0 .09412rem;background:#007bff;border-radius:.05882rem;color:#2f495e}.markdown .shop-title .shop-text{width:0;height:.47059rem;line-height:.47059rem;font-size:.2rem;text-align:center;color:#fff;overflow:hidden;transition:all .2s ease}.markdown .shop-title .shop-icon{position:relative;width:.47059rem;height:.47059rem;font-size:.35294rem;text-align:center;display:inline-block}.markdown .shop-title .shop-icon img{width:.35294rem;height:100%;display:inline-block}.markdown .shop-title .shop-icon:before{content:"";position:absolute;top:50%;right:-.32941rem;width:0;height:0;border-left:.23529rem solid transparent;border-right:.23529rem solid transparent;border-bottom:.23529rem solid #007bff;transform:translateY(-50%) rotate(90deg);display:none}.markdown .shop-title .shop-icon.eol:before{display:none}.markdown .shop-title:hover{color:#238dfb}.markdown .shop-title:hover .shop-text{width:2.35294rem}.markdown .shop-title:hover .shop-icon:before{display:block}.markdown .shop-title:hover .shop-icon.eol:before{display:none}.markdown .eol-title{display:flex;align-items:center;position:relative;margin:.02353rem 0 0 .08235rem;padding:0 .17647rem;height:.47059rem;line-height:.47059rem;background-color:#2f495e;border-radius:.05882rem}.markdown .eol-title .eol-text{font-size:.2rem;color:#fff}.markdown video{display:block;width:50%;margin-bottom:.35294rem}.markdown .video-iframe{margin:.23529rem 0;height:5.88235rem}.markdown .video-iframe iframe{width:50%;height:100%}.markdown .video-iframe>a{font-size:.23529rem;display:block;margin-bottom:.23529rem}.markdown a{color:#238dfb}.markdown h1{margin-top:.28235rem;margin-bottom:.21176rem;font-size:.54118rem;line-height:1.25}.markdown h1,.markdown h2{font-weight:600;color:#2f495e}.markdown h2{margin-top:.42353rem;margin-bottom:.18824rem;font-size:.35294rem;line-height:1.35;padding:0 .42353rem .11765rem .16471rem;position:relative;border-bottom:.01176rem solid #dfe5ec;cursor:pointer;transition:all .3s}.markdown h2:after{content:"";width:.03529rem;top:.04706rem;bottom:.16471rem;background:#238dfb;position:absolute;left:0}.markdown h2:before{content:"";position:absolute;background-image:url(/assets/link.svg);width:.29412rem;height:.29412rem;background-size:.29412rem;top:.08235rem;right:.05882rem;opacity:0;transition:opacity .3s}.markdown h2:hover{color:#0064c2}.markdown h2:hover:before{opacity:1}.markdown h3{margin-top:.32941rem;margin-bottom:.16471rem;font-size:.28235rem;color:#34495e;line-height:1.4}.markdown h3,.markdown h4{font-weight:600;position:relative}.markdown h4{margin-top:.28235rem;margin-bottom:.14118rem;font-size:.23529rem;color:#43566a;line-height:1.45}.markdown h5{margin-top:.23529rem;margin-bottom:.11765rem;font-size:.21176rem;font-weight:600;color:#526579;position:relative;line-height:1.5}.markdown ul{margin-bottom:.23529rem}.markdown ul ul{margin-bottom:.11765rem}.markdown ul li{list-style-type:circle;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f}.markdown ol{margin-bottom:.23529rem}.markdown ol li{list-style-type:decimal;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f;padding-left:.05882rem}.markdown ol li::marker{color:#6f6f6f;font-weight:700}.markdown code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;position:relative;color:#263445;font-size:.18824rem}.markdown :not(pre)>code{padding:.02353rem .05882rem;color:#165f8f;background:#eef3f7;border:.01176rem solid #dfe5ec;border-radius:.04706rem;font-size:.92em;font-weight:500}.markdown p{color:#4f5f6f;font-size:.18824rem;font-weight:400;line-height:.31765rem;margin-bottom:.16471rem}.markdown mark{background-color:#ffe051;color:#000}.markdown img{margin-bottom:.35294rem}.markdown>img:not([width]):not([class]){max-width:100%}.markdown .hljs{margin:.05882rem 0 .35294rem;font-size:.18824rem;line-height:.32941rem;white-space:pre;padding:.23529rem .29412rem;overflow-x:auto;overflow-y:hidden;border-radius:.07059rem;background-color:transparent;font-family:SourceCodePro,Microsoft YaHei;width:100%}.markdown .language-bash,.markdown .language-cpp,.markdown .language-diff,.markdown .language-dts,.markdown .language-json,.markdown .language-python,.markdown .language-shell{margin:0;font-size:.18824rem;line-height:.32941rem;white-space:pre;overflow-x:auto;overflow-y:hidden;background-color:transparent;display:block;width:100%}.markdown table thead,.markdown table tr{border-top:.01176rem solid #aabfdc}.markdown .normal-blockquote{box-shadow:-.05882rem 0 0 0 #238dfb;background-color:#fbfcfe;padding:.23529rem;margin:.17647rem 0 .17647rem .05882rem}.markdown .normal-blockquote p{font-weight:500;margin:0}.markdown .table-container{display:block;width:100%;min-width:0;max-width:100%;overflow-x:auto;overflow-y:hidden;overscroll-behavior-inline:contain;-webkit-overflow-scrolling:touch}.markdown table{border:none;display:table;min-width:100%;overflow:auto;margin:.11765rem 0 .35294rem}.markdown table thead{height:.58824rem;background:linear-gradient(-90deg,#1186de,#0064c2)}.markdown table thead tr{line-height:.58824rem;font-size:.18824rem;font-weight:700;color:#fff}.markdown table thead tr th{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr{line-height:.58824rem;font-size:.18824rem;color:#7d7d7d}.markdown table tbody tr td{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr:nth-child(odd){background-color:#fbfcfe}.markdown table tbody tr:nth-child(2n){background-color:#edf4fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table{border:.01176rem solid #e6ebf2;border-collapse:separate;border-spacing:0;border-radius:.07059rem;overflow:hidden;box-shadow:none}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead{height:auto;background:#1f6fe5}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr{border:0;line-height:1.4;font-size:.17647rem;font-weight:600;color:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr th{padding:.10588rem .17647rem;border:0;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr{border:0;line-height:1.5;color:#2c2f36}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td{padding:.10588rem .17647rem;border:0;border-right:.01176rem solid #e6ebf2;border-bottom:.01176rem solid #e6ebf2;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td:last-child{border-right:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(odd){background:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(2n){background:#f7f9fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:last-child td{border-bottom:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:hover{background:#eef3ff}.markdown .compare-table-container .table-container table thead{background:#fff!important}.markdown .compare-table-container .table-container table thead th{color:#2f495e;text-align:center!important;vertical-align:bottom}.markdown .compare-table-container .table-container table thead th a{align-items:center}.markdown .compare-table-container .table-container table thead th img{display:block;width:1.76471rem;height:1.76471rem;-o-object-fit:contain;object-fit:contain;margin:0 auto .35294rem}.markdown .compare-table-container .table-container table thead th:first-child{text-align:center!important;vertical-align:middle}.markdown .compare-table-container .table-container table tbody td:first-child,.markdown .compare-table-container .table-container table tbody td:not(:first-child){text-align:center!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(odd):hover{background:#fff!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(2n):hover{background:#f7f9fc!important}.markdown .table-text-align-left table td,.markdown .table-text-align-left table th{text-align:left}.markdown .table-text-align-right table td,.markdown .table-text-align-right table th{text-align:right}.markdown .markdown-ol li{list-style-type:decimal}.markdown .error,.markdown .tip,.markdown .warn{font-size:.21176rem;border-bottom-right-radius:.02353rem;margin:.11765rem .11765rem .11765rem 0;position:relative;background-color:#fff;box-shadow:.02353rem 0 .08235rem .01176rem #efefef;display:flex;flex-direction:column;color:#838383;font-size:.18824rem;font-weight:400;line-height:.37647rem;border-radius:.07059rem;overflow:hidden}.markdown .error .error-content,.markdown .error .tip-content,.markdown .error .warn-content,.markdown .tip .error-content,.markdown .tip .tip-content,.markdown .tip .warn-content,.markdown .warn .error-content,.markdown .warn .tip-content,.markdown .warn .warn-content{padding:.23529rem}.markdown .error .tip-title,.markdown .tip .tip-title,.markdown .warn .tip-title{height:.41176rem;background-color:rgba(35,141,251,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#238dfb}.markdown .error .warn-title,.markdown .tip .warn-title,.markdown .warn .warn-title{height:.41176rem;background-color:rgba(253,184,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#c69000}.markdown .error .error-title,.markdown .tip .error-title,.markdown .warn .error-title{height:.41176rem;background-color:rgba(253,45,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#ff1616}.markdown .tip:before{background-image:url(/assets/tip.svg)}.markdown .tip:before,.markdown .warn:before{content:"";position:absolute;width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .warn:before{background-image:url(/assets/warning.svg)}.markdown .error:before{content:"";position:absolute;background-image:url(/assets/error.svg);width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .tip{border-left:.07059rem solid #238dfb}.markdown .warn{border-left:.07059rem solid #fdb802}.markdown .error{border-left:.07059rem solid rgba(253,2,2,.83922)}.markdown .learn{display:flex;grid-column:auto;width:100%;height:2.07059rem;margin:.09412rem 0;overflow:hidden;background:#fff;border:.01176rem solid #d3dde9;border-radius:.07059rem;transition:border-color .2s ease,box-shadow .2s ease,transform .2s ease}.markdown .learn:hover{border-color:#8ab4eb;box-shadow:0 .04706rem .14118rem rgba(31,111,229,.1);transform:translateY(-.01176rem)}.markdown .learn:hover .learn-contents{background:#f6f9fe}.markdown .learn .learn-img{flex:0 0 42%;min-height:0;position:relative;overflow:hidden;text-align:center;background:#f7f9fc;border-right:.01176rem solid #e6ebf2}.markdown .learn .learn-img img{display:block;width:100%;max-width:none;box-shadow:none;margin:0;height:100%;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;font-size:.09412rem}.markdown .learn .learn-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.markdown .learn .learn-contents{flex:1;min-width:0;padding:.23529rem;position:relative;display:flex;flex-direction:column;justify-content:center;background:#fbfcfe;transition:background-color .2s ease}.markdown .learn .learn-contents .learn-title{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:2;font-size:.21176rem;font-weight:600;line-height:.29412rem}.markdown .learn .learn-contents .learn-title a{color:#1f6fe5}.markdown .learn .learn-contents .learn-desc{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:3;margin-top:.09412rem;font-size:.18824rem;font-weight:400;color:#5d6673;line-height:.28235rem}.markdown .learn [\:not-has\(\%2B.learn\)]{grid-column:1/-1}.markdown .learn :not(:has(+.learn)){grid-column:1/-1}.markdown .learn [\:not-has\(\%2B.learn\)] .learn-img{flex-basis:2.82353rem}.markdown .learn :not(:has(+.learn)) .learn-img{flex-basis:2.82353rem}.mobile .markdown{grid-template-columns:minmax(0,1fr)}.mobile .markdown p{font-size:.21176rem}.mobile .markdown .learn{flex-direction:row;height:1.88235rem;max-width:none}.mobile .markdown .learn .learn-img{flex:0 0 40%;width:auto;min-height:0;aspect-ratio:auto;border-right:.01176rem solid #e6ebf2;border-bottom:0}.mobile .markdown .learn .learn-contents{padding:.14118rem .16471rem}.mobile .markdown .learn .learn-contents .learn-title{font-size:.18824rem;line-height:.25882rem;-webkit-line-clamp:2}.mobile .markdown .learn .learn-contents .learn-desc{margin-top:.07059rem;font-size:.16471rem;line-height:.24706rem;-webkit-line-clamp:3}@media screen and (max-width:900px){.markdown{grid-template-columns:minmax(0,1fr)}.markdown .learn .learn-img{flex-basis:2.82353rem}}.mobile video{width:100%;margin-bottom:.35294rem}.mobile .video-iframe{margin:.23529rem 0;height:5.88235rem}.mobile .video-iframe iframe{width:100%;height:100%}.easyloader-box{display:flex;flex-direction:row;width:100%}.easyloader-box>div{position:relative;width:50%;overflow:hidden}.easyloader-box p{margin:.11765rem .29412rem;color:#fff}.easyloader-box p:last-child{overflow-y:scroll;height:20%;font-size:.11765rem}.easyloader-mask{position:absolute;right:0;bottom:.07059rem;height:100%;width:100%;background-color:#000;opacity:.7;transition:all .3s;display:flex;flex-direction:column;justify-content:center;display:none}.easyloader-mask a{margin-top:.58824rem;text-align:center}.video_play{bottom:-100%}.easyloader-btn{position:absolute;display:flex;flex-direction:row;justify-content:space-around;bottom:7%;width:100%;padding:0 .23529rem;font-size:.23529rem}.easyloader-btn a{width:1.05882rem;text-align:center;padding:.02353rem .11765rem;background-color:#007bff;color:#fff!important;border-radius:.11765rem;font-size:.17647rem}.easyloader-btn a:hover{background-color:#45a9ff}@media screen and (max-width:768px){.easyloader-box{flex-direction:column;width:100%}.easyloader-box>div{width:100%}}.code-block-wrapper{display:flex;flex-direction:column;position:relative;margin:.16471rem 0 .23529rem;border:.01176rem solid #dfe5ec;border-radius:.07059rem;overflow:hidden;background:#f7f9fb}.code-block-header{display:flex;justify-content:space-between;align-items:center;min-height:.44706rem;padding:.04706rem .14118rem;background:#f0f3f6;border-bottom:.01176rem solid #dfe5ec}.code-block-header .language-label{font-size:.15294rem;color:#526579;font-weight:500}.copy-all-btn{display:flex;align-items:center;grid-gap:.11765rem;gap:.11765rem;justify-content:center;background:0 0;border:none;border-radius:.05882rem;padding:.07059rem;font-size:.16471rem;cursor:pointer;transition:all .2s;width:.37647rem;height:.37647rem;color:#526579}.copy-all-btn svg{width:100%;height:100%}.copy-all-btn code{display:none}.copy-all-btn:hover{color:#1769aa;background:#e4ebf2}.copy-all-btn.focus-visible,.copy-all-btn:focus-visible{color:#1769aa;background:#e4ebf2;outline:.02353rem solid #1769aa;outline-offset:.02353rem}.code-block-container{display:flex;overflow:auto;background:#f7f9fb;align-items:flex-start}.code-block-wrapper.code-block-limited .code-block-container,.code-block-wrapper.code-block-limited .code-line-container{max-height:560px;max-height:var(--code-max-height,560px);overflow:auto;transition:max-height .35s ease}.code-block-wrapper:not(.is-collapsed).code-block-limited .code-block-container,.code-block-wrapper:not(.is-collapsed).code-block-limited .code-line-container{max-height:16.47059rem}.code-toggle-btn{display:flex;align-items:center;justify-content:center;width:100%;min-height:.49412rem;padding:.09412rem .14118rem .11765rem;border:0;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(240,244,249,.96));color:#6b7f93;cursor:pointer;transition:background .2s ease,color .2s ease;position:relative;z-index:2}.code-toggle-btn.focus-visible,.code-toggle-btn:focus-visible,.code-toggle-btn:hover{outline:0;color:#2d7be9;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(228,238,248,.98))}.code-toggle-icon{font-size:.17647rem;line-height:1;transition:transform .25s ease,color .2s ease}.code-block-wrapper:not(.is-collapsed) .code-toggle-icon,.code-toggle-icon{transform:translateY(-.01176rem)}.code-block-fade{position:absolute;left:0;right:0;bottom:.49412rem;height:1.29412rem;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(247,249,251,.96));pointer-events:none;transition:opacity .2s ease;z-index:1}.code-block-wrapper.is-collapsed .code-block-fade{opacity:1}.code-block-wrapper:not(.is-collapsed) .code-block-fade{opacity:0}.markdown .code-block-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-block-container code.hljs{margin:0!important;padding:0!important;border-radius:0;background:0 0;line-height:.32941rem;font-size:.18824rem;white-space:pre}.markdown .code-line-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-line-container code.hljs{margin:0!important;padding:0!important;line-height:.32941rem;font-size:.18824rem;white-space:pre;width:100%;border-radius:0;background-color:transparent}.code-line-container{display:flex;background:#f7f9fb;align-items:center;position:relative;padding:.18824rem .21176rem}.code-line-container .copy-all-btn{opacity:.45;position:absolute;top:.11765rem;right:.11765rem;transition:all .2s}.code-line-container pre{overflow-x:auto}.code-line-container:hover .copy-all-btn,.code-line-container[focus-within] .copy-all-btn{opacity:1}.code-line-container:focus-within .copy-all-btn,.code-line-container:hover .copy-all-btn{opacity:1}@media (hover:none){.code-line-container .copy-all-btn{opacity:1}.markdown .learn:hover{border-color:#d3dde9;box-shadow:none;transform:none}.markdown .learn:hover .learn-contents{background:#fbfcfe}}.line-numbers{padding:.11765rem .09412rem;text-align:right;background:#f3f6f9;color:#8491a0;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;border-right:.01176rem solid #dfe5ec;font-family:SourceCodePro,Microsoft YaHei,sans-serif;line-height:.32941rem;min-width:.51765rem}.line-number{display:block;height:.32941rem}.code-content{flex:1;overflow:auto;padding:.11765rem .17647rem;line-height:.32941rem}.code-block-container,.code-content,.code-line-container pre{scrollbar-color:#c5cfda transparent;scrollbar-width:thin}.code-block-container::-webkit-scrollbar,.code-content::-webkit-scrollbar,.code-line-container pre::-webkit-scrollbar{width:.09412rem;height:.09412rem}.code-block-container::-webkit-scrollbar-thumb,.code-content::-webkit-scrollbar-thumb,.code-line-container pre::-webkit-scrollbar-thumb{background:#c5cfda;border-radius:.04706rem}.code-block-container::-webkit-scrollbar-track,.code-content::-webkit-scrollbar-track,.code-line-container pre::-webkit-scrollbar-track{background:0 0}.code-line{display:block;min-height:.32941rem;line-height:.32941rem;white-space:pre;font-weight:700;font-family:SourceCodePro,Microsoft YaHei,sans-serif}.code-line:hover{background-color:#eaf1f7;cursor:pointer}pre code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;font-size:.18824rem;overflow-y:auto;font-family:SourceCodePro;display:block;width:100%;color:#263445;line-height:.32941rem}code.hljs{background:0 0}pre{position:relative}pre .copy-btn{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;opacity:0;position:absolute;right:.05882rem;top:.05882rem;cursor:pointer;padding:.05882rem;border-radius:.03529rem;transition:.3s;background:hsla(0,0%,100%,.2);width:1.52941rem;height:.58824rem;color:#0064c2}pre .copy-btn:active{background:hsla(0,0%,99.2%,.575)}pre .copy-btn .icon{width:.35294rem;position:absolute;left:70%;top:70%;transform:translate(-50%,-50%)}pre .copy-success-text{color:#fff;position:absolute;font-size:.14118rem;top:.70588rem;font-weight:200;font-family:SourceCodePro,Microsoft YaHei;-webkit-animation:successCopy .5s ease 1 both;animation:successCopy .5s ease 1 both;color:#0064c2}@-webkit-keyframes successCopy{0%{right:0}to{right:.29412rem}}@keyframes successCopy{0%{right:0}to{right:.29412rem}}pre:hover .copy-btn{opacity:1}.files_download{display:flex;flex-direction:row;justify-content:space-evenly;flex-wrap:wrap;margin:.52941rem}.files_download .item{display:flex;justify-content:center;width:2.35294rem;box-shadow:.04706rem .04706rem .08235rem 0 #cecece;transition:all .25s ease}.files_download .item:hover{transform:scale(1.2)}.card-container{display:flex;justify-content:flex-start;margin-bottom:.35294rem;align-items:flex-start}.card-container .card-item{margin:.23529rem;width:3.52941rem;display:flex;flex-direction:column;justify-content:center;align-items:center;color:#fff;transition:all .25s ease}.card-container .card-item .card-cover{height:1.76471rem;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1)}.card-container .card-item .card-cover,.card-container .card-item .card-cover-img{width:100%;display:flex;align-items:center;justify-content:center;font-size:.28235rem;font-weight:700;margin-bottom:.11765rem;border-radius:.11765rem}.card-container .card-item .card-cover-img{position:relative}.card-container .card-item .card-cover-img .card-cover-content{display:none;padding:.11765rem}.card-container .card-item .card-cover-img .card-cover-content .card-cover-btn{display:block;text-align:center;background-color:#0064c2;color:#fff;font-size:.2rem;padding:.11765rem .17647rem;border-radius:.04706rem}.card-container .card-item .card-cover-img img{width:100%;box-shadow:none;margin:0}.card-container .card-item .card-cover-img:hover .card-cover-content{display:flex;flex-direction:column;justify-content:space-around;align-items:center;position:absolute;top:0;left:0;bottom:0;right:0;background-color:rgba(0,0,0,.5098)}.card-container .card-item .card-desc{padding:.17647rem;text-align:center;font-size:.17647rem;color:#2f495e}.card-container .card-item .card-desc a{display:block;text-align:left;color:#333;line-height:.23529rem}.card-container .card-item .card-desc a:hover{text-decoration:underline;color:#238dfb}.card-container .card-item:hover{transform:translateY(-.05882rem)}.card-container .linear-blue{background:linear-gradient(45deg,#09f,#6cf)}.card-container .linear-gray{background:linear-gradient(45deg,#f2f2f2,#ccc);color:#333}.card-container .linear-orange{background:linear-gradient(45deg,#fc0,#f90)}.card-container-video{display:flex;flex-wrap:wrap;grid-gap:.23529rem;gap:.23529rem;margin:.47059rem 0}.card-container-video li{list-style-type:none}.card-container-video .card-item-video{width:22%;position:relative;border-radius:.07059rem;overflow:hidden;transition:transform .3s ease;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1);background-color:#fff}.card-container-video .card-item-video:hover{transform:translateY(-.05882rem);box-shadow:0 .09412rem .18824rem rgba(0,0,0,.15)}.card-container-video .card-item-video:hover .card-cover-content{opacity:1}.card-container-video .card-item-video .card-cover-img{position:relative;width:100%;padding-top:56.25%;background-color:#e7e7e7;overflow:hidden}.card-container-video .card-item-video .card-cover-img img{position:absolute;top:50%;left:50%;width:100%;height:100%;-o-object-fit:cover;object-fit:cover;transform:translate(-50%,-50%);min-width:100%;min-height:100%;transition:transform .3s ease;margin:0}.card-container-video .card-item-video .card-desc-video{padding:.11765rem;text-align:center;font-weight:700}.card-container-video .card-item-video .card-cover-content{position:absolute;top:0;left:0;width:100%;height:100%;display:flex;justify-content:center;align-items:center;background-color:rgba(0,0,0,.5);opacity:0;transition:opacity .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn{display:inline-block;padding:.09412rem .18824rem;margin:0 .11765rem;background-color:#fb7299;color:#fff;border-radius:.04706rem;text-decoration:none;font-size:.16471rem;transition:background-color .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn.youtube{background-color:#f03}.card-container-video .card-item-video .card-cover-content .card-cover-btn.bilibili{background-color:#ff85ad}.mobile .card-item-video{width:40%}.mobile .card-desc-video{font-size:.29412rem}.directory-links-container{display:flex;flex-direction:column}.directory-links-item{page-break-inside:avoid;-moz-column-break-inside:avoid;break-inside:avoid;margin:.11765rem;padding:.17647rem;border-radius:.05882rem;box-shadow:0 0 .05882rem rgba(0,0,0,.1)}.directory-links-body{display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(3.52941rem,1fr));position:relative}.directory-links-item h3{margin-top:0;margin-bottom:.11765rem}.directory-links-item ul{list-style-type:none;padding:0;margin:.18824rem .11765rem}.directory-links-item ul li{margin-bottom:.05882rem}.directory-links-item ul li a{text-decoration:none;color:#333}.directory-links-item ul li a:hover{text-decoration:underline;color:#238dfb}.header-nav .dropdown-icon-wrapper,.pc .nav-dropdown .dropdown-content-right,.pc .nav-dropdown .dropdown-image .image-button{display:flex;justify-content:center;align-items:center}.pc .header-nav-ul .header-nav-item a:hover{color:#0064c2}.mobile .mobile-nav-icon,.mobile .mobile-return-icon{background-repeat:no-repeat;background-size:100% 100%}header{width:100%;position:relative;background-color:#fff;border-bottom:.01176rem solid #e5e5e5;overflow:visible}.header-container{position:relative;margin:0 auto;padding:0 1.17647rem 0 0;width:15.64706rem;height:.70588rem;display:flex;align-items:center;justify-content:flex-end;font-size:.25882rem}.header-container .logo{position:absolute;left:.08235rem;display:block;width:2.08235rem;height:.41176rem;font-size:0;line-height:1;cursor:pointer}.header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.header-nav .dropdown-icon-wrapper{margin-right:.18824rem;width:.25882rem;height:.25882rem}.header-nav .dropdown-icon-wrapper .dropdown-icon{width:auto;height:auto;max-width:100%;max-height:100%;font-size:0}.language-option-box{position:absolute;height:.70588rem;right:-.65882rem;font-size:0;background-color:#fff}.language-option-box .icon{margin-right:.07059rem;width:.2rem;height:auto;color:#434343}.language-option-box .current-language{height:calc(100% - .02353rem);color:#434343;font-size:.22353rem;font-weight:700;display:flex;align-items:center;cursor:pointer;box-sizing:content-box}.language-option-box .language-dropdown-wrapper{display:none;position:fixed;top:.70588rem;padding-top:.11765rem;box-sizing:border-box;width:19.76471rem;left:50%;transform:translateX(-50%);z-index:99999}.language-option-box .language-dropdown-wrapper .language-dropdown{position:absolute;top:.11765rem;right:1.29412rem;width:1.52941rem;color:#434343;background-color:#fff;border-radius:.11765rem;overflow:hidden;box-shadow:0 .09412rem .28235rem rgba(0,0,0,.08);opacity:0;transition:opacity .2s ease}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item{font-size:.21176rem;font-weight:700;line-height:.54118rem;text-align:center;cursor:pointer}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item:hover{color:#0064c2}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item.active{background-color:#dedede}.language-option-box:hover .current-language{border-bottom:.03529rem solid #0064c2}.language-option-box:hover .current-language .header-arrow-btn{transform:rotate(-180deg)}.language-option-box:hover .language-dropdown-wrapper{display:block}.language-option-box:hover .language-dropdown{opacity:1}.disabledHover{cursor:auto!important}.disabledHover a:hover,.disabledHover li:hover,.disabledHover:hover{color:#434343!important}.pc .show-mb{display:none}.pc .header-nav{height:100%;display:flex;align-items:center}.pc .header-nav-ul{height:100%;display:flex;flex-direction:row}.pc .header-nav-ul .header-nav-item{margin-right:.30588rem;padding-left:.23529rem;height:calc(100% - .02353rem);display:flex;align-items:center;font-size:.22353rem;font-weight:700;color:#434343;cursor:pointer;box-sizing:content-box}.pc .header-nav-ul .header-nav-item.active,.pc .header-nav-ul .header-nav-item:hover{border-bottom:.03529rem solid #0064c2}.pc .header-nav-ul .header-nav-item.active .header-arrow-btn,.pc .header-nav-ul .header-nav-item:hover .header-arrow-btn{transform:rotate(-180deg)}.pc .header-nav-ul .header-nav-item:last-of-type{margin-right:0}.pc .header-nav-ul .header-nav-item a{position:relative;color:#434343}.pc .header-arrow-btn{margin-left:.07059rem;width:.11765rem;height:auto;color:#3a3a3a;font-size:0;transition:all .3s ease}.pc .nav-dropdown{position:fixed;left:50%;width:16.70588rem;max-width:calc(100vw - .47059rem);height:3.52941rem;display:flex;transform:translateX(-50%);background-color:#fff;border-radius:.23529rem;z-index:9999}.pc .nav-dropdown .dropdown-content-left{position:relative;padding:.47059rem .32941rem 0;width:calc(100% - 7.45882rem);height:100%;display:flex;justify-content:space-around}.pc .nav-dropdown .dropdown-content-right{width:7.45882rem;height:100%;background-color:#eee;border-radius:0 .23529rem .23529rem 0}.pc .nav-dropdown .dropdown-image{position:relative;width:7.05882rem;border-radius:.23529rem;font-size:0;overflow:hidden}.pc .nav-dropdown .dropdown-image img{width:100%;height:auto}.pc .nav-dropdown .dropdown-image .image-button{position:absolute;left:50%;bottom:.35294rem;transform:translateX(-50%);width:2.35294rem;height:.42353rem;font-size:.18824rem;color:#fff;background-color:#0064c2;border-radius:.04706rem}.pc .nav-dropdown .dropdown-image .image-button:hover{background-color:#058ce6}.pc .nav-dropdown .dropdown-image .image-button .image-icon{margin-right:.11765rem;width:.24706rem;height:auto}.pc .nav-dropdown .dropdown-item{width:3.29412rem;display:flex;flex-direction:column;flex-wrap:wrap}.pc .nav-dropdown .dropdown-item-li{padding-left:.16471rem;display:flex;align-items:center;font-size:.23529rem;font-weight:700;line-height:.70588rem;color:#434343}.pc .nav-dropdown .dropdown-item-li.border{border-bottom:.02353rem solid #dbdbdb}.pc .nav-dropdown .dropdown-item-li:hover{color:#0064c2}.pc .nav-dropdown .dropdown-item-child{margin-top:.18824rem;padding-left:.18824rem;display:flex;flex-direction:column}.pc .nav-dropdown .dropdown-child-li{margin-bottom:.14118rem;display:flex;align-items:center;font-size:.21176rem;font-weight:500;white-space:nowrap;color:#434343}.pc .nav-dropdown .dropdown-child-li:hover{color:#0064c2}.pc header #store{height:4.70588rem}.pc header #store .dropdown-item:first-child{width:2.21176rem}.pc header #store .dropdown-item:first-child .dropdown-child-li:nth-child(2) .dropdown-icon-wrapper{height:.32941rem}.pc header #store .dropdown-item:nth-child(2){width:4.65882rem;height:3.05882rem;border-bottom:.02353rem solid #dbdbdb}.pc header #store .dropdown-item:nth-child(2) .dropdown-item-child{width:90%;height:2rem;flex-wrap:wrap}.pc header #store .dropdown-item:nth-child(3),.pc header #store .dropdown-item:nth-child(4){position:absolute;bottom:.47059rem}.pc header #store .dropdown-item:nth-child(3){right:3.38824rem;width:2.04706rem}.pc header #store .dropdown-item:nth-child(3) .dropdown-icon-wrapper{margin-right:.14118rem;width:.32941rem}.pc header #store .dropdown-item:nth-child(4){right:.75294rem;width:2.58824rem}.pc header #software{height:4rem}.pc header #software .dropdown-content-left{width:calc(100% - 6.03529rem)}.pc header #software .dropdown-content-right{width:6.03529rem}.pc header #software .dropdown-image{width:5.58824rem}.pc header #software .dropdown-item:first-child{width:3.17647rem}.pc header #software .dropdown-item:nth-child(2){width:2.82353rem}.pc header #software .dropdown-item:nth-child(3){width:2.91765rem}.pc header #document{height:4.47059rem}.pc header #document .dropdown-content-left{width:100%}.pc header #document .dropdown-item:first-child .dropdown-item-child,.pc header #document .dropdown-item:nth-child(2) .dropdown-item-child{height:2rem;flex-wrap:wrap}.pc header #document .dropdown-item:first-child{width:4.65882rem}.pc header #document .dropdown-item:nth-child(2){width:5.01176rem}.pc header #document .dropdown-item:nth-child(3){width:3.76471rem}.pc header #aboutus{height:4.21176rem}.pc header #contact{height:1.05882rem;background-color:transparent}.pc header #contact .dropdown-content-left{position:absolute;padding:.09412rem 0;right:1.29412rem;width:2rem;height:1.05882rem;flex-direction:column;background-color:#fff;border-radius:.11765rem}.pc header #contact .dropdown-item{width:100%}.pc header #contact .dropdown-item .dropdown-item-li{padding-left:0;width:100%;justify-content:center;font-size:.21176rem;line-height:.42353rem}.mobile .show-pc,.mobile .snize-sticky-searchbox{display:none}.mobile header{height:1.10588rem;border-bottom:unset}.mobile .header-container{padding:0 .35294rem;width:100%;max-width:100%;height:1.10588rem;justify-content:unset;z-index:9999;box-shadow:0 0 .18824rem 0 hsla(0,0%,51.4%,.15)}.mobile .header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.mobile .mobile-nav-icon{width:.54118rem;height:.54118rem;background-image:url(/assets/menu.png);transition:all .28s ease}.mobile .mobile-nav-icon.active{transform:rotate(90deg)}.mobile .mobile-return-icon{position:absolute;left:1.2rem;width:.32941rem;height:.32941rem;background-image:url(/assets/return.png)}.mobile .logo{left:50%;width:2.47059rem;height:.48235rem;transform:translateX(-50%)}.mobile .header-nav{display:none;position:absolute;top:1.10588rem;left:0;padding:.18824rem 0 1.01176rem;width:5.17647rem;max-width:100%;background-color:#fff;z-index:9998}.mobile .header-nav.show{display:block}.mobile .header-nav-ul{margin-bottom:.23529rem}.mobile .header-nav-ul .header-nav-item{position:relative;padding-left:.47059rem;height:1.10588rem;font-size:.36471rem;font-weight:400;line-height:1.10588rem}.mobile .header-nav-ul .header-nav-item,.mobile .header-nav-ul .header-nav-item a{color:#434343}.mobile .header-nav-ul .header-nav-item.selected{background-color:#f7f7f7}.mobile .header-nav-ul .header-nav-item.active .header-mbnav-btn{transform:rotate(90deg)}.mobile .header-nav-ul .header-nav-item.active+.nav-dropdown{display:block}.mobile .header-mbnav-btn{position:absolute;width:.58824rem;height:.58824rem;top:.23529rem;right:.23529rem;background-image:url(/assets/arrow3.png);background-repeat:no-repeat;background-size:50% 50%;background-position:50%}.mobile .nav-dropdown{display:none;position:relative}.mobile .nav-dropdown .dropdown-content-left{width:100%}.mobile .nav-dropdown .dropdown-icon-wrapper{width:.47059rem;height:.47059rem}.mobile .nav-dropdown .dropdown-item-li{padding-left:.71765rem;width:100%;height:.88235rem;display:flex;align-items:center;font-size:.32941rem;font-weight:400;color:#434343}.mobile .nav-dropdown .dropdown-child-li{padding-left:.89412rem;width:100%;height:.82353rem;display:flex;align-items:center;font-size:.30588rem;line-height:.82353rem;white-space:nowrap;color:#434343}.mobile .language-option-box{height:1.10588rem;right:.25882rem}.mobile .language-option-box .icon{width:.35294rem}.mobile .language-option-box .current-language{font-size:.30588rem;font-weight:500}.mobile .language-option-box .language-dropdown-wrapper{width:100%;top:1.10588rem;padding-top:.11765rem;box-sizing:border-box}.mobile .language-option-box .language-dropdown{right:.11765rem;width:2.23529rem}.mobile .language-option-box .language-dropdown .language-item{font-size:.35294rem;font-weight:500;line-height:.70588rem}.header-nav-dd-pc-enter-active,.header-nav-dd-pc-leave-active{transition:opacity .2s ease-out,transform .22s cubic-bezier(.4,0,.2,1)}.header-nav-dd-pc-enter,.header-nav-dd-pc-leave-to{opacity:0;transform:translateX(-50%) translateY(-.09412rem)!important}.header-nav-dd-pc-enter-to,.header-nav-dd-pc-leave{opacity:1;transform:translateX(-50%) translateY(0)!important}.header-nav-dd-mb-enter-active,.header-nav-dd-mb-leave-active{transition:opacity .18s ease-out}.header-nav-dd-mb-enter,.header-nav-dd-mb-leave-to{opacity:0}.viewer-open .mobile .header-container,.viewer-open .mobile .language-dropdown-wrapper,.viewer-open .mobile .language-option-box{z-index:1!important}.viewer-open .mobile .language-option-box{pointer-events:none}.title-level2{height:.32941rem;font-size:.35294rem;font-weight:400;color:#434343;line-height:.32941rem;padding-left:.22353rem;position:relative;display:flex;justify-content:space-between;margin:.58824rem 0}.title-level2 .title-level2-desc{font-size:.18824rem;font-weight:400}.title-level2:after{content:"";width:.04706rem;height:.35294rem;background:#0064c2;position:absolute;left:0}.title-level3{height:.27059rem;font-size:.29412rem;font-weight:400;color:#434343;line-height:.27059rem;padding-left:.14118rem;position:relative;display:flex;justify-content:space-between;margin:.47059rem 0 .35294rem}.title-level3 .title-level3-desc{font-size:.14118rem;font-weight:400}.pc .product-list-container .Products{display:flex;flex-wrap:wrap;margin-bottom:.70588rem}.pc .product-list-container .ProductItem{border-top:.01176rem solid #e5e5e5;border-bottom:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(2n),.pc .product-list-container .ProductItem:nth-child(2n-1){border-right:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(3n){border-right:0 solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(n+4){border-top:0 solid #e5e5e5}.pc .product-list-container .ProductItem{height:4.51765rem;width:4.65882rem;text-align:center;position:relative}.pc .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.pc .product-list-container .ProductItem .ProductPic{text-align:center;width:2.35294rem;height:2.35294rem}.pc .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.pc .product-list-container .ProductItem .ProductName{margin-top:.11765rem;line-height:.29412rem;height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343}.pc .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto .17647rem;width:2.47059rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.23529rem;text-overflow:clip;overflow:hidden}.pc .product-list-container .ProductItem .product-btn-group{width:1.76471rem;height:.35294rem;border-radius:.17647rem;margin:auto;display:flex}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.29412rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.35294rem;font-size:.18824rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.47059rem;height:.35294rem;background-size:.23529rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.pc .product-list-container .ProductLinks{padding:0 .17647rem;font-size:.18824rem;display:grid;justify-content:start;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(2.82353rem,1fr));position:relative;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink:hover{color:#409eff;-webkit-text-decoration-line:underline;text-decoration-line:underline}.mobile .product-list-container{text-align:left}.mobile .product-list-container .ProductItem{text-align:center;height:5.17647rem;width:50%;border:.02353rem solid #e5e5e5;background-color:#fff;position:relative}.mobile .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.mobile .product-list-container .ProductItem .ProductPic{margin:.11765rem auto;text-align:center;width:2.82353rem;height:2.82353rem}.mobile .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.mobile .product-list-container .ProductItem .ProductName{height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343;line-height:.28235rem}.mobile .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto;display:block;width:2.36471rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.25882rem;overflow:hidden}.mobile .product-list-container .ProductItem .product-btn-group{width:2.35294rem;height:.47059rem;border-radius:.17647rem;margin:auto;display:flex}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.64706rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.47059rem;font-size:.23529rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.70588rem;height:.47059rem;background-size:.29412rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.mobile .product-list-container .ProductLinks{padding:.11765rem .17647rem;font-size:.25882rem;display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fit,minmax(3.52941rem,1fr));position:relative;margin-bottom:.14118rem;background-color:#fff}.mobile .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.14118rem}.product-list-container.hideEol .ProductItem.EOL{display:none}.footer-email-input input::-webkit-input-placeholder{font-family:Microsoft YaHei,sans-serif}.subscribe-btn{display:flex;justify-content:center;align-items:center}.pc .footer-bottom-content a:hover,.pc .footer-nav-li a:hover{color:#0064c2}.subscribe-btn:hover{background-color:#0074e1}.mobile .footer-nav-btn{background-repeat:no-repeat;background-size:100% 100%}.footer-container{width:100%;color:#fff;background-color:#000}.footer-content-wrap{height:100%;display:flex;align-items:center}.footer-email-title,.footer-qrcode-title{font-size:.32941rem;margin-bottom:.21176rem;font-weight:500;color:#fff}.footer-email-desc{font-weight:400;color:#f1f1f1}.footer-email-input{display:flex}.footer-email-input input{background:hsla(0,0%,60%,.55);border:.01176rem solid #0077c8;border-radius:.04706rem;padding:0 .23529rem;color:#fff;outline:0}.footer-email-input input::-webkit-input-placeholder{font-weight:400;color:#a0a0a0}.subscribe-btn{background:#0077c8;width:1.55294rem;height:.56471rem;font-size:.21176rem;font-weight:500;color:#fff;border-radius:.07059rem}.footer-follow{margin-top:.42353rem;width:90%}.footer-follow-ul{display:flex;flex-wrap:wrap}.footer-info-wrapper{margin-top:.47059rem;font-size:.16471rem;color:#a0a0a0}.footer-email-warning{margin-top:.11765rem;display:none;font-size:.18824rem;color:#ff2529}.footer-email-success{margin-top:.35294rem;margin-bottom:1.15294rem;display:none;font-size:.35294rem;color:#fff}.pc .footer-container{height:8.23529rem}.pc .footer-content-wrap{width:15.64706rem;margin:0 auto}.pc .footer-nav{padding:.70588rem 0 .11765rem;width:65%;height:100%;display:flex;flex-direction:column;flex-wrap:wrap}.pc .footer-nav-item{margin:0 0 .47059rem}.pc .footer-nav-title{margin-bottom:.18824rem;font-size:.29412rem;font-weight:500;color:#fff}.pc .footer-nav-title a{color:#fff}.pc .footer-nav-li{font-size:.21176rem;font-weight:400;color:#a0a0a0;line-height:.38824rem}.pc .footer-nav-li a{color:#a0a0a0;cursor:pointer}.pc .footer-right{width:35%;height:5.95294rem;padding:0 0 0 .47059rem}.pc .footer-email-title,.pc .footer-qrcode-title{margin-top:.14118rem}.pc .footer-email-desc{font-size:.21176rem;line-height:.32941rem;margin-bottom:.14118rem}.pc .footer-email-input input{width:3.71765rem;height:.56471rem;font-size:.21176rem;margin-right:.12941rem}.pc .footer-email-input input::-webkit-input-placeholder{font-size:.21176rem}.pc .footer-qrcode-list{display:flex}.pc .footer-qrcode-list .footer-qrcode-item{margin-right:.11765rem}.pc .footer-qrcode-list .footer-qrcode-img{width:1.88235rem;height:auto}.pc .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.pc .footer-qrcode-list .footer-qrcode-name{font-size:.21176rem;color:#a0a0a0}.pc .footer-follow-ul{width:100%}.pc .footer-follow-ul a{display:block;margin-right:.11765rem;margin-bottom:.11765rem;font-size:0}.pc .footer-follow-ul img{width:.58824rem;height:.58824rem}.pc .footer-address-info{line-height:.23529rem;margin:.05882rem 0}.pc .footer-info{line-height:.32941rem}.pc .footer-bottom{width:100%;height:.77647rem;background-color:#000}.pc .footer-bottom-content{margin:0 auto;padding:.23529rem .23529rem 0;width:16.07059rem;height:100%;display:flex;justify-content:space-between;font-size:.15294rem;font-weight:400;color:#a0a0a0;border-top:.01176rem solid #6d6d6d}.pc .footer-bottom-content a{display:inline-block;color:#a0a0a0;font-weight:400;font-size:.15294rem}.pc .terms-box{margin-left:.54118rem;display:flex}.pc .terms-box a{margin:0 .09412rem}.mobile .footer-container{height:11.76471rem}.mobile .footer-right{padding:0;width:100%}.mobile .footer-email-group,.mobile .footer-right{display:flex;flex-direction:column;align-items:center}.mobile .footer-email-title,.mobile .footer-qrcode-title{font-size:.58824rem;margin-bottom:.25882rem}.mobile .footer-email-success{font-size:.51765rem;margin-top:1.17647rem;margin-bottom:1.27059rem}.mobile .footer-email-desc{width:5.52941rem;font-size:.35294rem;line-height:.47059rem;text-align:center;margin-bottom:.75294rem}.mobile .footer-email-input{flex-direction:column;align-items:center}.mobile .footer-email-input input{width:7.35294rem;height:.70588rem;margin-bottom:.47059rem;font-size:.32941rem}.mobile .footer-email-input input::-webkit-input-placeholder{font-size:.32941rem}.mobile .subscribe-btn{width:2.75294rem;height:.70588rem;border-radius:.07059rem;font-size:.32941rem}.mobile .footer-email-warning{font-size:.29412rem;margin-top:.18824rem}.mobile .footer-qrcode-title{text-align:center}.mobile .footer-qrcode-list{display:flex}.mobile .footer-qrcode-list .footer-qrcode-item{margin-right:.35294rem}.mobile .footer-qrcode-list .footer-qrcode-img{width:3.05882rem;height:auto}.mobile .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.mobile .footer-qrcode-list .footer-qrcode-name{margin-top:.11765rem;font-size:.35294rem;color:#a0a0a0;text-align:center}.mobile .footer-follow{margin-top:.82353rem;width:100%}.mobile .footer-follow-ul{width:80%;margin:0 auto;justify-content:center}.mobile .footer-follow-ul a{margin-right:.23529rem}.mobile .footer-follow-ul a:nth-child(5){margin-right:0}.mobile .footer-follow-ul img{width:1.05882rem;height:1.05882rem}.mobile .footer-qrcode-img{width:2.82353rem;height:2.82353rem;margin:0 auto}.mobile .footer-qrcode-img img{width:100%;height:auto;max-height:100%}.mobile .footer-info-wrapper{width:95%;margin-top:.47059rem;font-size:.23529rem;text-align:center}.mobile .footer-address-info{line-height:.35294rem;margin:.05882rem 0}.mobile .footer-info{line-height:.44706rem}.mobile .footer-bottom{display:none}.mobile .footer-nav{background-color:#fff;border-top:.03529rem solid #eee}.mobile .footer-nav-item:nth-child(3) .footer-nav-title a{display:block}.mobile .footer-nav-title{position:relative;padding:0 0 0 .71765rem;font-size:.36471rem;line-height:1.10588rem;font-weight:500;color:#a6a6a6;height:1.10588rem;border-bottom:.03529rem solid #eee}.mobile .footer-nav-title a{color:#a6a6a6}.mobile .footer-nav-title.active .footer-nav-btn{transform:rotate(90deg)}.mobile .footer-nav-title.active+.footer-nav-ul{display:block}.mobile .footer-nav-btn{position:absolute;width:.2rem;height:.36471rem;top:.35294rem;right:.41176rem;background-image:url(/assets/arrow2.png)}.mobile .footer-nav-ul{display:none;border-bottom:.03529rem solid #eee}.mobile .footer-nav-li{font-size:.25882rem;font-weight:400;color:#a0a0a0;line-height:.65882rem;padding:0 0 0 .91765rem}.mobile .footer-nav-li a{color:#a0a0a0}.product-demo-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(2rem,1fr));grid-gap:.16471rem;gap:.16471rem;margin:.21176rem 0 .32941rem}.product-demo-item{display:flex;flex-direction:column;align-items:center;justify-content:flex-start;text-decoration:none;color:#1f2937;background:#fff;border:.01176rem solid #e5e7eb;border-radius:.14118rem;overflow:hidden;transition:transform .2s ease,border-color .2s ease;height:100%}.product-demo-item:hover{transform:translateY(-.03529rem);border-color:#93c5fd}.product-demo-item img{width:100%;height:1.41176rem;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;display:block;background:#f8fafc;box-shadow:none!important;flex-shrink:0}.product-demo-item span{display:block;width:100%;padding:.11765rem;font-size:.15294rem;line-height:1.4;font-weight:600;margin-top:auto;text-align:center}.scene-application-card{position:relative;display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.12fr);align-items:stretch;min-height:4rem;color:#0f172a;text-decoration:none;border-radius:.23529rem;overflow:hidden;background-color:#f8fafc;border:none;box-shadow:0 .21176rem .47059rem rgba(15,23,42,.1);border:.01176rem solid rgba(148,163,184,.22)}.scene-application-card--scene1{background-image:linear-gradient(180deg,rgba(15,23,42,.08),rgba(15,23,42,.56)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:50%}.scene-application-card--scene2{background-image:linear-gradient(180deg,rgba(15,23,42,.1),rgba(15,23,42,.58)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:64%}.scene-application-card:hover{color:#0f172a}.scene-application-card,.scene-application-card .scene-application-card__title,.scene-application-card p,.scene-application-card span:not(.scene-application-card__button){color:#0f172a!important}.scene-application-card__media{position:relative;display:flex;align-items:center;justify-content:center;min-height:100%;overflow:hidden;padding:.18824rem .21176rem .18824rem .14118rem;line-height:0}.scene-application-card__media img{flex:none;width:88%;max-width:4.94118rem;max-width:100%;height:auto;max-height:100%;display:block;margin:0!important;padding:0!important;border:.01176rem solid rgba(148,163,184,.34);border-radius:.16471rem;box-shadow:0 .11765rem .28235rem rgba(15,23,42,.16);vertical-align:top;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center}.scene-application-card__content{position:relative;z-index:1;display:flex;flex-direction:column;justify-content:center;grid-row-gap:.14118rem;row-gap:.14118rem;width:100%;max-width:5.17647rem;min-height:100%;padding:.32941rem .30588rem .28235rem;background:linear-gradient(180deg,hsla(0,0%,100%,.96),rgba(248,250,252,.9))}.scene-application-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-gap:.21176rem;gap:.21176rem;margin:.21176rem 0 .32941rem}.scene-application-card__title{margin:.09412rem 0 0;font-size:.32941rem;line-height:1.15;font-weight:700;text-align:center;color:#0f172a!important;text-shadow:none}.scene-application-card__desc{margin:0;font-size:.17647rem;line-height:1.6;text-align:center;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden;text-overflow:ellipsis;color:rgba(30,41,59,.9)!important;text-shadow:none}.scene-application-card__button{display:inline-flex;align-items:center;justify-content:center;align-self:center;margin-top:0;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content;min-width:1.22353rem;padding:.11765rem .18824rem;font-size:.16471rem;line-height:1;font-weight:600;white-space:nowrap;color:#fff!important;background:#2563eb;border-radius:11.75294rem;box-shadow:0 .09412rem .21176rem rgba(37,99,235,.28)}.scene-application-card .scene-application-card__button{color:#fff!important}.mobile .product-demo-grid{grid-template-columns:repeat(3,minmax(0,1fr));grid-gap:.09412rem;gap:.09412rem}.mobile .product-demo-item{border-radius:.09412rem}.mobile .product-demo-item img{height:auto;aspect-ratio:1/1;-o-object-fit:contain;object-fit:contain;-o-object-position:center;object-position:center;padding:.09412rem;box-shadow:none!important}.mobile .product-demo-item span{padding:.07059rem .07059rem .09412rem;font-size:.21176rem;line-height:1.4;text-align:center;word-break:break-word}.mobile .scene-application-card{grid-template-columns:1fr;grid-template-rows:2.35294rem minmax(0,1fr);min-height:4.58824rem;margin:0;border-radius:.16471rem}.mobile .scene-application-card__media{order:1;min-height:2.35294rem;padding:.11765rem .14118rem}.mobile .scene-application-card__media img{width:100%;max-width:none;max-height:none}.mobile .scene-application-grid{grid-template-columns:1fr;grid-gap:.16471rem;gap:.16471rem}.mobile .scene-application-card__content{order:2;max-width:none;justify-content:center;padding:.23529rem .21176rem;background:linear-gradient(180deg,hsla(0,0%,100%,.97),rgba(248,250,252,.93));grid-row-gap:.11765rem;row-gap:.11765rem}.mobile .scene-application-card__title{font-size:.25882rem;line-height:1.2;margin-top:.07059rem}.mobile .scene-application-card__desc{font-size:.15294rem;line-height:1.5;-webkit-line-clamp:4}.mobile .scene-application-card__button{min-width:1.17647rem;margin-top:.09412rem;padding:.10588rem .16471rem;font-size:.15294rem}.project-item{display:flex;height:1.96471rem;margin:.11765rem 0}.project-item .project-img{width:1.96471rem;height:1.96471rem;position:relative;overflow:hidden;text-align:center}.project-item .project-img img{height:100%;font-size:.09412rem}.project-item .project-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.project-item .project-contents{flex:1;background-color:#efefef;padding:0 .38824rem;position:relative;display:flex;flex-direction:column;justify-content:center}.project-item .project-contents .project-title{font-size:.25882rem;font-weight:700;line-height:.27059rem}.project-item .project-contents .project-title a{color:#238dfb}.project-item .project-contents .project-desc{margin-top:.15294rem;font-size:.22353rem;font-weight:400;color:#717171;line-height:.29412rem}.saerch-fliter-container{height:1.17647rem;border-bottom:.04706rem dashed #e5e5e5;display:flex}.saerch-fliter-container .search-fliter-title{font-size:.21176rem;font-weight:400;color:#434343;width:1.50588rem;margin-right:.58824rem}.saerch-fliter-container .search-fliter-options{flex:1;display:flex;flex-wrap:wrap}.saerch-fliter-container .search-fliter-options .fliter-option{font-size:.18824rem;font-weight:400;color:#959595;padding:0 .35294rem 0 0;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.saerch-fliter-container .search-fliter-options .fliter-option.active{color:#0064c2}.mobile .saerch-fliter-container{height:2.82353rem;margin-top:.35294rem}.dev-layout{flex-wrap:wrap;justify-content:space-between;margin-bottom:.70588rem;flex-direction:column}.dev-container,.dev-layout{display:flex;width:100%}.mobile .dev-container{flex-direction:column;min-height:60vh}.dev-info-container{margin:.70588rem .23529rem;display:flex;color:#5f5d5d;width:3.52941rem;overflow:hidden;flex-direction:column}.dev-info-container .dev-contents{display:flex;flex-direction:column;align-items:center;text-align:center}.dev-info-container .dev-title{font-size:.47059rem;padding:.35294rem}.dev-info-container .dev-desc{font-size:.18824rem;padding:.35294rem;line-height:.28235rem;font-weight:300;height:1.17647rem}.dev-info-container .dev-button{width:1.64706rem;height:.47059rem;background:#0064c2;border-radius:.05882rem;color:#fff;text-align:center}.dev-info-container .dev-banner{padding:.05882rem;overflow:hidden;border-radius:.11765rem}.dev-info-container .dev-banner img{box-shadow:0 0 .23529rem 0 #efefef;background-size:cover;width:5.29412rem;transition:all .25s ease;border-radius:.11765rem}.dev-info-container .dev-banner img:hover{transform:scale(1.1)}.mobile .dev-info-container{width:100%;flex-direction:row}@-webkit-keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@-webkit-keyframes fade-in{0%{opacity:0}to{opacity:1}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}@-webkit-keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}@keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}.float-icon-container{position:fixed;right:23PX;bottom:80PX;z-index:6;height:120PX;width:50PX}.float-icon-container .totop-icon{position:absolute;top:0;left:0}.float-icon-container .menu-icon{position:absolute;top:70PX;left:0}.float-icon-container .menu-icon.active,.float-icon-container .menu-icon.active:hover{background-color:#2f495e}.float-icon-container .menu-icon,.float-icon-container .totop-icon{width:50PX;height:50PX;display:flex;align-items:center;justify-content:center;border-radius:50%;background-color:#0870d1;box-shadow:0 0 .35294rem -.02353rem rgba(19,41,75,.14),0 .14118rem .15294rem -.02353rem rgba(19,41,75,.13),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.13),0 .02353rem .02353rem -.02353rem rgba(19,41,75,.12);cursor:pointer;z-index:200}.float-icon-container .menu-icon svg,.float-icon-container .totop-icon svg{width:50PX;height:50PX}.float-icon-container .menu-icon svg path,.float-icon-container .totop-icon svg path{fill:#fefefe}.float-icon-container .menu-icon:hover,.float-icon-container .totop-icon:hover{background-color:#058ce6}.markdown .hljs{color:#263445;background:0 0}.markdown .hljs-comment,.markdown .hljs-quote{color:#687789;font-style:normal}.markdown .hljs-addition,.markdown .hljs-keyword,.markdown .hljs-selector-tag{color:#b4233f;font-weight:500}.markdown .hljs-link,.markdown .hljs-literal,.markdown .hljs-number,.markdown .hljs-regexp{color:#1769aa}.markdown .hljs-doctag,.markdown .hljs-meta .hljs-meta-string,.markdown .hljs-string{color:#16705a}.markdown .hljs-name,.markdown .hljs-section,.markdown .hljs-selector-class,.markdown .hljs-selector-id,.markdown .hljs-title{color:#6f52a2}.markdown .hljs-attr,.markdown .hljs-attribute,.markdown .hljs-template-variable,.markdown .hljs-variable{color:#8a5a00}.markdown .hljs-built_in,.markdown .hljs-builtin-name,.markdown .hljs-class .hljs-title,.markdown .hljs-type{color:#9a4d16}.markdown .hljs-bullet,.markdown .hljs-meta,.markdown .hljs-meta .hljs-keyword,.markdown .hljs-selector-attr,.markdown .hljs-selector-pseudo,.markdown .hljs-subst,.markdown .hljs-symbol{color:#526579}.markdown .hljs-deletion{color:#b4233f}.markdown .hljs-formula{background:#eaf1f7}.markdown .hljs-emphasis{font-style:italic}.markdown .hljs-strong{font-weight:600}/*!
- * Viewer.js v1.11.6
- * https://fengyuanchen.github.io/viewerjs
- *
- * Copyright 2015-present Chen Fengyuan
- * Released under the MIT license
- *
- * Date: 2023-09-17T03:16:35.830Z
- */.viewer-close:before,.viewer-flip-horizontal:before,.viewer-flip-vertical:before,.viewer-fullscreen-exit:before,.viewer-fullscreen:before,.viewer-next:before,.viewer-one-to-one:before,.viewer-play:before,.viewer-prev:before,.viewer-reset:before,.viewer-rotate-left:before,.viewer-rotate-right:before,.viewer-zoom-in:before,.viewer-zoom-out:before{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAARgAAAAUCAYAAABWOyJDAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAALEgAACxIB0t1+/AAAABx0RVh0U29mdHdhcmUAQWRvYmUgRmlyZXdvcmtzIENTNui8sowAAAQPSURBVHic7Zs/iFxVFMa/0U2UaJGksUgnIVhYxVhpjDbZCBmLdAYECxsRFBTUamcXUiSNncgKQbSxsxH8gzAP3FU2jY0kKKJNiiiIghFlccnP4p3nPCdv3p9778vsLOcHB2bfveeb7955c3jvvNkBIMdxnD64a94GHMfZu3iBcRynN7zAOI7TG15gHCeeNUkr8zaxG2lbYDYsdgMbktBsP03jdQwljSXdtBhLOmtjowC9Mg9L+knSlcD8TNKpSA9lBpK2JF2VdDSR5n5J64m0qli399hNFMUlpshQii5jbXTbHGviB0nLNeNDSd9VO4A2UdB2fp+x0eCnaXxWXGA2X0au/3HgN9P4LFCjIANOJdrLr0zzZ+BEpNYDwKbpnQMeAw4m8HjQtM6Z9qa917zPQwFr3M5KgA6J5rTJCdFZJj9/lyvGhsDvwFNVuV2MhhjrK6b9bFiE+j1r87eBl4HDwCF7/U/k+ofAX5b/EXBv5JoLMuILzf3Ap6Z3EzgdqHMCuF7hcQf4HDgeoHnccncqdK/TvSDWffFXI/exICY/xZyqc6XLWF1UFZna4gJ7q8BsRvgd2/xXpo6P+D9dfT7PpECtA3cnWPM0GXGFZh/wgWltA+cDNC7X+AP4GzjZQe+k5dRxuYPeiuXU7e1qwLpDz7dFjXKRaSwuMLvAlG8zZlG+YmiK1HoFqT7wP2z+4Q45TfEGcMt01xLoNZEBTwRqD4BLpnMLeC1A41UmVxsXgXeBayV/Wx20rpTyrpnWRft7p6O/FdqzGrDukPNtkaMoMo3FBdBSQMOnYBCReyf05s126fU9ytfX98+mY54Kxnp7S9K3kj6U9KYdG0h6UdLbkh7poFXMfUnSOyVvL0h6VtIXHbS6nOP+s/Zm9mvyXW1uuC9ohZ72E9uDmXWLJOB1GxsH+DxPftsB8B6wlGDN02TAkxG6+4D3TWsbeC5CS8CDFce+AW500LhhOW2020TRjK3b21HEmgti9m0RonxbdMZeVzV+/4tF3cBpP7E9mKHNL5q8h5g0eYsCMQz0epq8gQrwMXAgcs0FGXGFRcB9wCemF9PkbYqM/Bas7fxLwNeJPdTdpo4itQti8lPMqTpXuozVRVXPpbHI3KkNTB1NfkL81j2mvhDp91HgV9MKuRIqrykj3WPq4rHyL+axj8/qGPmTqi6F9YDlHOvJU6oYcTsh/TYSzWmTE6JT19CtLTJt32D6CmHe0eQn1O8z5AXgT4sx4Vcu0/EQecMydB8z0hUWkTd2t4CrwNEePqMBcAR4mrBbwyXLPWJa8zrXmmLEhNBmfpkuY2102xxrih+pb+ieAb6vGhuA97UcJ5KR8gZ77K+99xxeYBzH6Q3/Z0fHcXrDC4zjOL3hBcZxnN74F+zlvXFWXF9PAAAAAElFTkSuQmCC);background-repeat:no-repeat;background-size:280px;color:transparent;display:block;font-size:0;height:20px;line-height:0;width:20px}.viewer-zoom-in:before{background-position:0 0;content:"Zoom In"}.viewer-zoom-out:before{background-position:-20px 0;content:"Zoom Out"}.viewer-one-to-one:before{background-position:-40px 0;content:"One to One"}.viewer-reset:before{background-position:-60px 0;content:"Reset"}.viewer-prev:before{background-position:-80px 0;content:"Previous"}.viewer-play:before{background-position:-100px 0;content:"Play"}.viewer-next:before{background-position:-120px 0;content:"Next"}.viewer-rotate-left:before{background-position:-140px 0;content:"Rotate Left"}.viewer-rotate-right:before{background-position:-160px 0;content:"Rotate Right"}.viewer-flip-horizontal:before{background-position:-180px 0;content:"Flip Horizontal"}.viewer-flip-vertical:before{background-position:-200px 0;content:"Flip Vertical"}.viewer-fullscreen:before{background-position:-220px 0;content:"Enter Full Screen"}.viewer-fullscreen-exit:before{background-position:-240px 0;content:"Exit Full Screen"}.viewer-close:before{background-position:-260px 0;content:"Close"}.viewer-container{bottom:0;direction:ltr;font-size:0;left:0;line-height:0;overflow:hidden;position:absolute;right:0;-webkit-tap-highlight-color:transparent;top:0;touch-action:none;-webkit-touch-callout:none;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.viewer-container ::-moz-selection,.viewer-container::-moz-selection{background-color:transparent}.viewer-container ::selection,.viewer-container::selection{background-color:transparent}.viewer-container:focus{outline:0}.viewer-container img{display:block;height:auto;max-height:none!important;max-width:none!important;min-height:0!important;min-width:0!important;width:100%}.viewer-canvas{bottom:0;left:0;overflow:hidden;position:absolute;right:0;top:0}.viewer-canvas>img{height:auto;margin:15px auto;max-width:90%!important;width:auto}.viewer-footer{bottom:0;left:0;overflow:hidden;position:absolute;right:0;text-align:center}.viewer-navbar{background-color:rgba(0,0,0,.5);overflow:hidden}.viewer-list{box-sizing:content-box;height:50px;margin:0;overflow:hidden;padding:1px 0}.viewer-list>li{color:transparent;cursor:pointer;float:left;font-size:0;height:50px;line-height:0;opacity:.5;overflow:hidden;transition:opacity .15s;width:30px}.viewer-list>li:focus,.viewer-list>li:hover{opacity:.75}.viewer-list>li:focus{outline:0}.viewer-list>li+li{margin-left:1px}.viewer-list>.viewer-loading{position:relative}.viewer-list>.viewer-loading:after{border-width:2px;height:20px;margin-left:-10px;margin-top:-10px;width:20px}.viewer-list>.viewer-active,.viewer-list>.viewer-active:focus,.viewer-list>.viewer-active:hover{opacity:1}.viewer-player{background-color:#000;bottom:0;cursor:none;display:none;right:0;z-index:1}.viewer-player,.viewer-player>img{left:0;position:absolute;top:0}.viewer-toolbar>ul{display:inline-block;margin:0 auto 5px;overflow:hidden;padding:6px 3px}.viewer-toolbar>ul>li{background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;float:left;height:24px;overflow:hidden;transition:background-color .15s;width:24px}.viewer-toolbar>ul>li:focus,.viewer-toolbar>ul>li:hover{background-color:rgba(0,0,0,.8)}.viewer-toolbar>ul>li:focus{box-shadow:0 0 3px #fff;outline:0;position:relative;z-index:1}.viewer-toolbar>ul>li:before{margin:2px}.viewer-toolbar>ul>li+li{margin-left:1px}.viewer-toolbar>ul>.viewer-small{height:18px;margin-bottom:3px;margin-top:3px;width:18px}.viewer-toolbar>ul>.viewer-small:before{margin:-1px}.viewer-toolbar>ul>.viewer-large{height:30px;margin-bottom:-3px;margin-top:-3px;width:30px}.viewer-toolbar>ul>.viewer-large:before{margin:5px}.viewer-tooltip{background-color:rgba(0,0,0,.8);border-radius:10px;color:#fff;display:none;font-size:12px;height:20px;left:50%;line-height:20px;margin-left:-25px;margin-top:-10px;position:absolute;text-align:center;top:50%;width:50px}.viewer-title{color:#ccc;display:inline-block;font-size:12px;line-height:1.2;margin:5px 5%;max-width:90%;min-height:14px;opacity:.8;overflow:hidden;text-overflow:ellipsis;transition:opacity .15s;white-space:nowrap}.viewer-title:hover{opacity:1}.viewer-button{-webkit-app-region:no-drag;background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;height:80px;overflow:hidden;position:absolute;right:-40px;top:-40px;transition:background-color .15s;width:80px}.viewer-button:focus,.viewer-button:hover{background-color:rgba(0,0,0,.8)}.viewer-button:focus{box-shadow:0 0 3px #fff;outline:0}.viewer-button:before{bottom:15px;left:15px;position:absolute}.viewer-fixed{position:fixed}.viewer-open{overflow:hidden}.viewer-show{display:block}.viewer-hide{display:none}.viewer-backdrop{background-color:rgba(0,0,0,.5)}.viewer-invisible{visibility:hidden}.viewer-move{cursor:move;cursor:-webkit-grab;cursor:grab}.viewer-fade{opacity:0}.viewer-in{opacity:1}.viewer-transition{transition:all .3s}@-webkit-keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}.viewer-loading:after{-webkit-animation:viewer-spinner 1s linear infinite;animation:viewer-spinner 1s linear infinite;border:4px solid hsla(0,0%,100%,.1);border-left-color:hsla(0,0%,100%,.5);border-radius:50%;content:"";display:inline-block;height:40px;left:50%;margin-left:-20px;margin-top:-20px;position:absolute;top:50%;width:40px;z-index:1}@media (max-width:767px){.viewer-hide-xs-down{display:none}}@media (max-width:991px){.viewer-hide-sm-down{display:none}}@media (max-width:1199px){.viewer-hide-md-down{display:none}}.nuxt-progress{position:fixed;top:0;left:0;right:0;height:.02353rem;width:0;opacity:1;transition:width .1s,opacity .4s;background-color:#000;z-index:999999}.nuxt-progress.nuxt-progress-notransition{transition:none}.nuxt-progress-failed{background-color:red}.side-bar{width:2.47059rem;position:sticky;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.side-bar .side-bar-title{height:.82353rem;width:2.47059rem;background-image:url(/assets/sidebar-title.jpg);background-size:cover}.side-bar .side-bar-title p{height:.21176rem;font-size:.28235rem;font-weight:700;color:#fff;line-height:.82353rem;text-align:center}.side-bar .side-bar-contents{cursor:pointer;border-bottom:.02353rem solid #e5e5e5;border-left:.02353rem solid #e5e5e5;border-right:.02353rem solid #e5e5e5}.side-bar .side-bar-contents .side-bar-collapse{position:relative;height:.50588rem;overflow:hidden;transition:all .2s ease;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.side-bar .side-bar-contents .side-bar-collapse .collapse-title{font-size:.18824rem;font-weight:400;color:#434343;line-height:.50588rem;padding-left:.24706rem;border-top:.01176rem solid #edf1f4;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.side-bar .side-bar-contents .side-bar-collapse .collapse-title.active{color:#409eff}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn{position:absolute;height:.11765rem;width:.11765rem;box-shadow:.02353rem -.02353rem 0 #82a5d7;background-color:#fff;top:.2rem;right:.18824rem;transform:rotate(45deg);transition:all .25s ease}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn.collapse-btn-active{transform:translate(.04706rem,-.04706rem) rotate(135deg)}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents{border-bottom:.01176rem solid #edf1f4}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item{padding-left:.38824rem;line-height:.44706rem;color:#838383;font-size:.16471rem}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active{color:#409eff;background-color:#f6f7f8;position:relative}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active:after{content:" ";width:.04706rem;height:.04706rem;background:#82a5d7;border-radius:50%;position:absolute;top:50%;left:.17647rem;transform:translateY(-50%)}.page-header-container{margin-bottom:.35294rem;width:100%}.page-header-container .page-header-content{display:flex;align-content:center;position:relative}.page-header-container .page-header-content .page-header-arrow-icon{width:.28235rem;height:.32941rem;padding-top:.02353rem;color:#2f495e;font-size:.23529rem;transition:all .2s ease}.page-header-container .page-header-content .header-arrow-container{width:.17647rem;height:.17647rem;background-image:url(/assets/arrow3.png);background-size:cover}.page-header-container .page-header-content .page-header-arrow-icon:hover{color:#007bff}.page-header-container .page-header-content .page-header-item{color:#858585;font-size:.18824rem;font-weight:500;display:flex;height:.35294rem;line-height:.35294rem;cursor:pointer;align-items:center}.page-header-container .page-header-content .page-header-item .page-header-tag{margin:0 .09412rem;transition:all .2s ease}.page-header-container .page-header-content .page-header-item .page-header-tag.active{color:#2f495e}.page-header-container .page-header-content .page-header-item .page-header-tag:hover{color:#007bff}.mobile .page-header-container{margin-top:.35294rem}.search-box{display:flex;grid-gap:.11765rem;gap:.11765rem;margin-bottom:.28235rem;position:relative;align-items:center}.search-box input{flex:1;min-width:7.05882rem;height:.51765rem;background:#edf1f4;border-radius:.09412rem;border:.01176rem solid #d5dee8;padding:0 .18824rem;font-size:.17647rem;color:#253443;outline:0;z-index:3;transition:border-color .2s ease,box-shadow .2s ease}.search-box input:focus{border-color:#0064c2;box-shadow:0 0 0 .03529rem rgba(0,100,194,.12157)}.search-box .search-btn{width:1.55294rem;height:.51765rem;background:#0064c2;border-radius:.09412rem;border:none;cursor:pointer;transition:background-color .2s ease}.search-box .search-btn:hover{background:#0a5aaa}.search-box .search-btn p{margin:0;line-height:.51765rem;font-size:.18824rem;font-weight:700;color:#fff}.search-box .search-cover{position:fixed;top:0;left:0;right:0;bottom:0;z-index:2;background-color:rgba(25,25,25,.1098);-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem)}.search-result-container{overflow:hidden}.search-result-container::-webkit-scrollbar{width:.14118rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.search-result-container .el-tabs__item{display:table-cell;font-size:.21176rem;font-weight:600}.search-result-container .el-tabs__active-bar{height:.04706rem}.search-result-container{width:100%;min-height:4.47059rem;max-height:7.05882rem;overflow-y:auto;background-color:#fff;position:absolute;top:.63529rem;border:.01176rem solid #e2e8f0;border-radius:.11765rem;box-shadow:0 .11765rem .17647rem -.03529rem rgba(0,0,0,.10196),0 .04706rem .07059rem -.02353rem rgba(0,0,0,.05098);transition:all .25s ease;color:#2f495e;z-index:3;padding:.14118rem;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.search-result-container .search-title{height:.70588rem;font-size:.29412rem;padding:.17647rem;border-bottom:.01176rem solid #d9d9d9}.search-result-container .search-result-contents{display:flex;align-items:flex-start;grid-gap:.11765rem;gap:.11765rem;padding:.14118rem;border-bottom:.01176rem solid #edf2f7;position:relative}.search-result-container .search-result-contents svg{display:inline;font-size:.23529rem;color:#409eff;padding-right:.11765rem}.search-result-container .search-result-contents:hover{background-color:#f3f8fd}.search-result-container .search-result-content{flex:1;display:flex;flex-direction:column;justify-content:center;position:relative;transition:all .25s ease}.search-result-container .search-result-name{font-size:.18824rem;text-align:left;font-weight:700;color:#409eff;line-height:1.4}.search-result-container .search-result-sku{font-size:.16471rem;line-height:1.6;color:#5b5b5b;margin-top:.04706rem}.search-result-container .search-result-key{font-size:.18824rem;font-weight:700;color:#2f495e;margin-top:.04706rem}.search-result-container .search-result-key .search-result-highlight{color:#409eff}.search-result-container .search-result-key .search-result-key-tag{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#5b5b5b;padding:.02353rem .11765rem;border:.01176rem solid #5b5b5b;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container .search-result-key .search-result-key-tag.active{color:#409eff;border:.01176rem solid #409eff}.search-result-container .search-result-image{width:1.31765rem;height:1.31765rem;margin:0 .21176rem 0 .04706rem}.search-result-container .search-result-eol-tag{position:absolute;width:.41176rem;height:.41176rem;border-radius:50%;top:5%;left:.35294rem;background-color:#2f495e;color:#fff;font-size:.15294rem;font-weight:700;line-height:.41176rem;text-align:center}.search-result-container .search-result-recommand-box{margin-top:.14118rem}.search-result-container .search-result-recommand-box .search-result-recommand-item{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#409eff;padding:.04706rem .11765rem;border:.01176rem solid #409eff;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container:before{display:block;position:absolute;content:"";width:.16471rem;height:.16471rem;background:#fff;z-index:1000;top:-.08235rem;left:calc(50% - .08235rem);border-top:.01176rem solid #d9d9d9;border-right:.01176rem solid #d9d9d9;transform:rotate(-45deg);border-radius:.02353rem}.mobile .search-box{margin-bottom:.09412rem;width:100%;grid-gap:.09412rem;gap:.09412rem}.mobile .search-box input{height:.65882rem;font-size:.2rem}.mobile .search-box .search-btn{width:2.11765rem;height:.65882rem;background:#0064c2;border-radius:.09412rem}.mobile .search-box .search-btn p{margin:0;line-height:.65882rem;font-size:.21176rem;font-weight:700;color:#fff}.mobile .search-result-container{top:.75294rem}.search-result-container .tabs{display:flex;grid-gap:.07059rem;gap:.07059rem;width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .14118rem;padding:.09412rem .14118rem;border-radius:0;background:hsla(0,0%,100%,.9);border:0;border-bottom:.01176rem solid #e6edf5;-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem);position:sticky;top:-.14118rem;z-index:6}.search-result-container .tabs:after{content:"";position:absolute;left:0;right:0;top:0;bottom:0;background:0 0;z-index:-1}.search-result-container .tabs button{min-width:1.27059rem;padding:.10588rem .18824rem;border-radius:.11765rem;font-size:.16471rem;font-weight:600;color:#516578;background:hsla(0,0%,100%,.6);border:.01176rem solid #d7e3ef;line-height:1.2;overflow:hidden;transition:color .2s ease,background-color .2s ease,box-shadow .2s ease}.search-result-container .tabs button:first-child,.search-result-container .tabs button:last-child{border-radius:.11765rem}.search-result-container .tabs button:hover{color:#2f4f6f;background:#f8fbff;border-color:#cddded}.search-result-container .tabs button.active{color:#0f4f8e;background:#fff;border:.01176rem solid #c8d9eb;border-radius:.11765rem;box-shadow:0 .02353rem .09412rem rgba(0,100,194,.16078)}.search-result-container .tab-content{padding:.11765rem .09412rem .09412rem;background:0 0}.search-result-container .search-result-contents{border-radius:.09412rem;transition:background-color .2s ease,box-shadow .2s ease}.search-result-container .search-result-contents:hover{box-shadow:inset 0 0 0 .01176rem #dbe9f8}.search-result-contents-list{padding-bottom:.82353rem}.search-result-view-all-wrap{position:sticky;bottom:0;z-index:4;display:flex;justify-content:center;padding:.11765rem .09412rem .07059rem;background:linear-gradient(0deg,#fff 70%,hsla(0,0%,100%,0))}.search-result-view-all-btn{display:inline-block;min-width:2.82353rem;text-align:center;padding:.12941rem .21176rem;border-radius:.28235rem;background:#0064c2;color:#fff;font-size:.17647rem;font-weight:700;text-decoration:none;box-shadow:0 .04706rem .14118rem rgba(0,100,194,.25);transition:background-color .2s ease}.search-result-view-all-btn:hover{background:#0a5aaa}.mobile .search-result-container .tabs{width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .11765rem;padding:.09412rem .11765rem}.mobile .search-result-container .tabs button{flex:1;min-width:0;padding:.14118rem .11765rem;font-size:.17647rem}.mobile .search-result-container .tab-content{padding:.09412rem .04706rem .07059rem}.search-result-container.search-result-embedded{position:relative;top:auto;max-height:none;min-height:0;padding:0;box-shadow:none;-webkit-animation:none;animation:none}.search-result-container.search-result-embedded:before{display:none}.search-result-loading{padding:.09412rem .04706rem;display:flex;flex-direction:column}.search-result-loading-header{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;color:#516578;font-size:.16471rem;margin:0 0 .11765rem}.search-result-loading-text{min-width:0;font-size:.16471rem;font-weight:400;line-height:.23529rem}.search-result-loading-dot{width:.09412rem;height:.09412rem;border-radius:50%;background:#409eff;-webkit-animation:search-loading-pulse 1s ease-in-out infinite;animation:search-loading-pulse 1s ease-in-out infinite}.search-result-loading-list{display:flex;flex-direction:column;grid-gap:.11765rem;gap:.11765rem}.search-result-loading-item{padding:.14118rem;border-radius:.09412rem;border:.01176rem solid #edf2f7;background:#fbfdff}.search-result-loading-line{height:.11765rem;border-radius:11.75294rem;margin-bottom:.09412rem;background:linear-gradient(90deg,#e9f0f7 20%,#f5f9fd 45%,#e9f0f7 70%);background-size:2.82353rem 100%;-webkit-animation:search-loading-shimmer 1.1s linear infinite;animation:search-loading-shimmer 1.1s linear infinite}.search-result-loading-line.is-title{width:52%;height:.14118rem}.search-result-loading-line.is-short{width:36%;margin-bottom:0}@-webkit-keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@-webkit-keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}@keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}.search-result-loading-text[data-v-2b770079]{min-width:0;font-size:.16471rem!important;font-weight:400;line-height:.23529rem}.tab-panel{border:.01176rem solid #e5e5e5;padding:.09412rem;border-radius:.09412rem}.tabs{display:flex;grid-gap:.09412rem;gap:.09412rem;margin-bottom:.18824rem}.tabs button{padding:.11765rem .21176rem;border:none;border-bottom:.04706rem solid transparent;background:#f9f9f9;cursor:pointer;transition:.2s}.tabs button.active{border-color:#007bff;color:#007bff}.tab-content{padding:.18824rem;background:#fefefe;border-radius:.09412rem}.search-result-container .tab-panel{border:0}.carousel-container[data-v-6e07f87d]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-6e07f87d]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-6e07f87d]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-6e07f87d]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-6e07f87d]{flex-shrink:0;width:33.333%;text-align:center;cursor:pointer}.preview-image img[data-v-6e07f87d]{max-width:100%;height:auto;margin:0}.arrow[data-v-6e07f87d]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-6e07f87d]{left:0;transform:rotateY(180deg)}.arrow.right[data-v-6e07f87d]{right:0}.carousel-thumbnails[data-v-6e07f87d]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-6e07f87d]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-6e07f87d]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-6e07f87d]{width:100%;margin:0;height:auto}.clickable-area[data-v-6e07f87d]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-6e07f87d]{left:0}.clickable-area.right[data-v-6e07f87d]{right:0}.carousel-container[data-v-7d51a79c]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-7d51a79c]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-7d51a79c]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-7d51a79c]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-7d51a79c]{flex-shrink:0;width:100%;text-align:center;cursor:pointer}.preview-image img[data-v-7d51a79c]{width:100%;height:auto;margin:0}.arrow[data-v-7d51a79c]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-7d51a79c]{left:0;transform:translateY(-50%) rotateY(180deg)}.arrow.right[data-v-7d51a79c]{right:0;transform:translateY(-50%)}.carousel-thumbnails[data-v-7d51a79c]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-7d51a79c]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-7d51a79c]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-7d51a79c]{width:100%;margin:0;height:auto}.clickable-area[data-v-7d51a79c]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-7d51a79c]{left:0}.clickable-area.right[data-v-7d51a79c]{right:0}.corner-marker[data-v-7d51a79c]{position:absolute;bottom:.11765rem;left:.11765rem;background-color:rgba(0,0,0,.5);color:#fff;padding:.05882rem .11765rem;border-radius:.05882rem;z-index:2}.video-gallery-island[data-v-5e05839f]{min-width:0;width:100%}.page-tools[data-v-39baf185]{width:2.35294rem;margin-bottom:.16471rem;border:.01176rem solid #dfeaf5;border-radius:.11765rem;background:#f8fbfe;box-shadow:0 .07059rem .21176rem rgba(19,41,75,.08);overflow:visible}.page-tools-title[data-v-39baf185]{height:.4rem;line-height:.4rem;padding:0 .14118rem;border-bottom:.01176rem solid #e5eef7;color:#2f495e;font-size:.15294rem;font-weight:700}.page-tools-actions[data-v-39baf185]{display:flex;flex-direction:column;grid-gap:.09412rem;gap:.09412rem;padding:.11765rem;align-items:stretch}.page-tools-action[data-v-39baf185]{display:inline-flex;align-items:center;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;height:.43529rem;width:100%;padding:0 .11765rem;border:.01176rem solid #d6e5f3;border-radius:.08235rem;background:#fff;color:#238dfb;font-size:.15294rem;font-weight:700;transition:background-color .2s ease,border-color .2s ease,transform .2s ease}.page-tools-action .page-tools-icon[data-v-39baf185]{width:.21176rem;height:.21176rem;flex:0 0 auto;fill:currentColor;display:block}.page-tools-action[data-v-39baf185]:after{content:"";width:.08235rem;height:.08235rem;margin-left:auto;border-top:.02353rem solid;border-right:.02353rem solid;transform:rotate(45deg);opacity:.45}.page-tools-action[data-v-39baf185]:hover{background:#eaf4ff;border-color:#b9d8f4;transform:translateY(-.01176rem)}.page-tools.mobile[data-v-39baf185]{width:auto;margin:.09412rem 0 .18824rem;border:0;background:0 0;box-shadow:none}.page-tools.mobile .page-tools-actions[data-v-39baf185]{flex-direction:row;padding:0}.page-tools.mobile .page-tools-action[data-v-39baf185]{width:.63529rem;min-width:.63529rem;height:.42353rem;padding:0;background:#edf6ff;border-color:#b7d8f5;justify-content:center}.page-tools.mobile .page-tools-action[data-v-39baf185]:after{display:none}.markdown-action-menu[data-v-5d6a4f8a]{position:relative;display:flex;justify-content:flex-end;margin:-.14118rem 0 .21176rem;z-index:20}.markdown-action-trigger[data-v-5d6a4f8a]{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;height:.47059rem;padding:0 .16471rem;border:.01176rem solid #b9cfe5;border-radius:.07059rem;background:linear-gradient(135deg,#0064c2,#238dfb);color:#fff;font-size:.16471rem;font-weight:700;cursor:pointer;transition:background-color .2s ease,border-color .2s ease}.markdown-action-trigger svg[data-v-5d6a4f8a]{width:.18824rem;height:.18824rem}.markdown-action-trigger[data-v-5d6a4f8a]:hover{background:linear-gradient(135deg,#0059ad,#167ce8);border-color:#82b6ec}.markdown-action-dropdown[data-v-5d6a4f8a]{position:fixed;z-index:2147483000;width:3.52941rem;overflow:hidden;border:.01176rem solid #c8dced;border-radius:.11765rem;background:#fff;box-shadow:0 .18824rem .44706rem rgba(18,62,111,.16),0 .02353rem .09412rem rgba(24,84,140,.08)}.markdown-action-item[data-v-5d6a4f8a]{display:flex;width:100%;grid-gap:.16471rem;gap:.16471rem;align-items:flex-start;padding:.17647rem .18824rem;border:0;border-bottom:.01176rem solid #e6edf5;background:0 0;color:#2f495e;text-align:left;cursor:pointer;transition:background-color .15s ease}.markdown-action-item svg[data-v-5d6a4f8a]{flex:0 0 auto;width:.2rem;height:.2rem;margin-top:.02353rem;color:#238dfb}.markdown-action-item strong[data-v-5d6a4f8a]{display:block;font-size:.17647rem;line-height:.23529rem}.markdown-action-item small[data-v-5d6a4f8a]{display:block;margin-top:.02353rem;color:#6f8193;font-size:.15294rem;line-height:.21176rem}.markdown-action-item[data-v-5d6a4f8a]:last-child{border-bottom:0}.markdown-action-item[data-v-5d6a4f8a]:hover{background:#f3f8fe}.markdown-action-menu.placement-sidebar[data-v-5d6a4f8a]{justify-content:center;margin:.14118rem 0 0}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;justify-content:center;background:#edf6ff;border-color:#c7dff7;color:#0064c2}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#dfefff;border-color:#9fc7ef}.markdown-action-menu.placement-sidebar .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.05882rem}.markdown-action-menu.placement-anchor[data-v-5d6a4f8a]{justify-content:flex-start;margin:0 0 .11765rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:center;padding:0 .11765rem;background:#f5f9fd;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-anchor .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.placement-toolbox[data-v-5d6a4f8a]{width:100%;flex:1;justify-content:flex-start;margin:0}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;padding:0 .11765rem;background:#fff;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]{flex:0 0 auto}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{width:.16471rem;height:.16471rem;margin-left:auto;opacity:.55}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-toolbox .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.compact[data-v-5d6a4f8a]{justify-content:flex-start;margin:.09412rem 0 .18824rem}.markdown-action-menu.compact .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center;padding:0;background:#edf6ff;border-color:#b7d8f5;color:#0064c2}.markdown-action-menu.compact .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.52941rem;max-width:calc(100vw - .37647rem)}.markdown-action-menu.compact.placement-toolbox[data-v-5d6a4f8a]{flex:0 0 auto;margin:0}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{margin-left:0}</style><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer%20V1.1/state.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/en/core/Cardputer%20V1.1/payload.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/manifest.js" as="script">
-  </head>
-  <body>
-    <div data-server-rendered="true" id="__nuxt"><!----><div id="__layout"><div class="device-hydration-sensitive"><div class="pc"><header langdata="[object Object]" lang="en"><!----> <!----> <div class="header-container"><a href="https://m5stack.com/" class="logo"><img src="/assets/m5logo.svg" alt="M5Stack"></a> <div class="header-nav"><div class="header-nav-ul"><!----> <li data-id="solution" class="header-nav-item"><a class="header-nav-item-a disabledHover">Solution</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="store" class="header-nav-item"><a href="https://shop.m5stack.com" class="header-nav-item-a">Store</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="software" class="header-nav-item"><a class="header-nav-item-a disabledHover">Software</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="document" class="header-nav-item"><a class="header-nav-item-a disabledHover">Documentation</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="aboutus" class="header-nav-item"><a class="header-nav-item-a disabledHover">About Us</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="contact" class="header-nav-item"><a class="header-nav-item-a disabledHover">Contact</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----></div></div> <div class="language-option-box"><div class="current-language"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 1.32 1.32" fill="currentColor" aria-hidden="true" class="icon"><g><path d="M0.66 0c0.18,0 0.35,0.07 0.47,0.19 0.12,0.12 0.19,0.28 0.19,0.47 0,0.18 -0.07,0.35 -0.19,0.47 -0.12,0.12 -0.28,0.19 -0.47,0.19 -0.18,0 -0.35,-0.07 -0.47,-0.19 -0.12,-0.12 -0.19,-0.28 -0.19,-0.47 0,-0.18 0.07,-0.35 0.19,-0.47 0.12,-0.12 0.28,-0.19 0.47,-0.19zm0.39 0.27c-0.1,-0.1 -0.24,-0.16 -0.39,-0.16 -0.15,0 -0.29,0.06 -0.39,0.16 -0.1,0.1 -0.16,0.24 -0.16,0.39 0,0.15 0.06,0.29 0.16,0.39 0.1,0.1 0.24,0.16 0.39,0.16 0.15,0 0.29,-0.06 0.39,-0.16 0.1,-0.1 0.16,-0.24 0.16,-0.39 0,-0.15 -0.06,-0.29 -0.16,-0.39z"></path> <path d="M0.09 0.51c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.09 0.92c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.62 1.21c0.02,0.02 0.02,0.06 0,0.08 -0.02,0.02 -0.06,0.02 -0.08,0 -0.07,-0.06 -0.13,-0.16 -0.16,-0.27 -0.04,-0.11 -0.06,-0.23 -0.06,-0.36 0,-0.13 0.02,-0.26 0.06,-0.36 0.04,-0.11 0.1,-0.21 0.16,-0.27 0.02,-0.02 0.06,-0.02 0.08,0 0.02,0.02 0.02,0.06 -0,0.08 -0.06,0.05 -0.1,0.13 -0.14,0.23 -0.03,0.09 -0.05,0.21 -0.05,0.33 0,0.12 0.02,0.23 0.05,0.33 0.03,0.1 0.08,0.18 0.14,0.23z"></path> <path d="M0.78 1.29c-0.02,0.02 -0.06,0.02 -0.08,-0 -0.02,-0.02 -0.02,-0.06 0,-0.08 0.06,-0.05 0.1,-0.13 0.14,-0.23 0.03,-0.09 0.05,-0.21 0.05,-0.33 0,-0.12 -0.02,-0.23 -0.05,-0.33 -0.03,-0.1 -0.08,-0.18 -0.14,-0.23 -0.02,-0.02 -0.02,-0.06 -0,-0.08 0.02,-0.02 0.06,-0.02 0.08,-0 0.07,0.06 0.13,0.16 0.16,0.27 0.04,0.11 0.06,0.23 0.06,0.36 0,0.13 -0.02,0.26 -0.06,0.36 -0.04,0.11 -0.1,0.21 -0.16,0.27z"></path></g></svg> <div>English</div> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg></div> <div class="language-dropdown-wrapper"><div class="language-dropdown"><div class="language-item active">English</div> <div class="language-item">简体中文</div> <div class="language-item">日本語</div></div></div></div></div></header> <div class="docs-layouts"><div class="docs-layouts-sidebar"><div class="side-bar"><div class="side-bar-title"><p>CONTENTS</p></div> <div class="side-bar-contents"></div></div></div> <div class="docs-layouts-body"><div class="page-header-container"><!----></div> <!----> <div class="search-box"><div id="search"></div> <input placeholder="Product Name / SKU"> <div class="search-result-container" style="display:none" data-v-2b770079><a class="search-result-contents" data-v-2b770079><div class="search-result-content" data-v-2b770079><div class="search-result-name" data-v-2b770079>No Results Found</div> <div class="search-result-sku" data-v-2b770079>Hot Searches</div> <div class="search-result-key" data-v-2b770079><div class="search-result-recommand-box" data-v-2b770079><div data-key="Camera" class="search-result-recommand-item" data-v-2b770079>
-            Camera
-          </div><div data-key="WiFi" class="search-result-recommand-item" data-v-2b770079>
-            WiFi
-          </div><div data-key="RS485" class="search-result-recommand-item" data-v-2b770079>
-            RS485
-          </div><div data-key="RS232" class="search-result-recommand-item" data-v-2b770079>
-            RS232
-          </div><div data-key="Relay" class="search-result-recommand-item" data-v-2b770079>
-            Relay
-          </div><div data-key="LoRaWAN" class="search-result-recommand-item" data-v-2b770079>
-            LoRaWAN
-          </div><div data-key="GPS" class="search-result-recommand-item" data-v-2b770079>
-            GPS
-          </div><div data-key="NB-IoT" class="search-result-recommand-item" data-v-2b770079>
-            NB-IoT
-          </div><div data-key="LTE" class="search-result-recommand-item" data-v-2b770079>
-            LTE
-          </div><div data-key="GSM" class="search-result-recommand-item" data-v-2b770079>
-            GSM
-          </div><div data-key="Zigbee" class="search-result-recommand-item" data-v-2b770079>
-            Zigbee
-          </div><div data-key="Servo" class="search-result-recommand-item" data-v-2b770079>
-            Servo
-          </div><div data-key="StepMotor" class="search-result-recommand-item" data-v-2b770079>
-            StepMotor
-          </div><div data-key="Ethernet" class="search-result-recommand-item" data-v-2b770079>
-            Ethernet
-          </div><div data-key="E-Paper" class="search-result-recommand-item" data-v-2b770079>
-            E-Paper
-          </div></div></div></div></a> <div class="tab-panel" style="display:none" data-v-2b770079><div class="tabs"><button>
-      Product
-    </button><button>
-      Contents
-    </button></div> <div class="tab-content"><div style="display:none"></div><div style="display:none"></div></div></div></div> <button class="search-btn"><p>Search</p></button> <div class="search-cover" style="display:none"></div></div> <div class="viewer"><div class="markdown"><h1 id="cardputer-v11" data-id="Cardputer v1.1">Cardputer v1.1</h1> <p><span class="product-sku">SKU:K132-V11</span></p><div class="carousel-container" data-v-6e07f87d><div class="carousel-preview" data-v-6e07f87d><div class="clickable-area left" data-v-6e07f87d></div> <button class="arrow left" data-v-6e07f87d></button> <div class="carousel-images" data-v-6e07f87d><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-6e07f87d><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_01.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_02.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_03.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_04.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_05.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_06.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_07.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_08.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_09.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_10.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_11.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_12.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_13.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_14.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_15.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_16.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_17.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_17.webp" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132-V11.webp" alt="Preview" data-v-6e07f87d></div></div></div> <button class="arrow right" data-v-6e07f87d></button> <div class="clickable-area right" data-v-6e07f87d></div></div> <div class="carousel-thumbnails" data-v-6e07f87d><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_01.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_02.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_03.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_04.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_05.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_06.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_07.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_08.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_09.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_10.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_11.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_12.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_13.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_14.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_15.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_16.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_17.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_17.webp" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132-V11.webp" alt="Thumbnail" data-v-6e07f87d></div></div></div> <h2 id="description" data-id="Description">Description</h2> <p><strong>Cardputer v1.1</strong> is a high-performance card computer designed for engineers, offering a comprehensive upgrade over the original Cardputer. The new version adopts the brand new <strong>Stamp-S3A</strong> main controller, with optimized antenna and button design for the core module, significantly improving system stability and user operation experience.
-In terms of control and interaction, it features a <strong>56-key</strong> keyboard and a 1.14-inch <strong>TFT</strong> display for efficient operation and display; a built-in SPM1423 digital MEMS <strong>microphone</strong> supports recording and wake-up functions, while a cavity <strong>speaker</strong> outputs audio; an infrared emitter enables external <strong>infrared</strong> control interactions.
-For expansion, the built-in Grove interface allows for custom sensor extensions; storage is supported via a Micro <strong>SD</strong> card slot for storage expansion. The power system consists of a built-in 120mAh battery and a 1400mAh base <strong>lithium battery</strong>, with integrated charging and power conversion circuits for greatly improved battery life. The base has an integrated magnet for metal surface attachment and is compatible with LEGO hole extensions.
-This product is applicable to scenarios such as rapid function verification for engineers, industrial control, and home control systems.</p><h2 id="tutorial" data-id="Tutorial">Tutorial</h2> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/arduino/arduino_banner_01.png" alt="Arduino IDE"> <a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/arduino/m5cardputer/program">Arduino IDE</a></div> <div class="learn-desc"> This tutorial will introduce how to program and control the Cardputer v1.1 device using the Arduino IDE.</div></div></div> <div class="learn"><div class="learn-img"><img src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/img/uiflow2/uiflow2.0_banner_01.png" alt="UiFlow2"> <a target="_blank" href="/en/uiflow2/cardputer/program">UiFlow2</a></div> <div class="learn-contents"><div class="learn-title"><a target="_blank" href="/en/uiflow2/cardputer/program">UiFlow2</a></div> <div class="learn-desc"> This tutorial will introduce how to control the Cardputer v1.1 device using the UiFlow2 graphical programming platform.</div></div></div><h2 id="note" data-id="Note">Note</h2> <ul><li>LCD and RGB LED usage note: Since RGB and LCD backlight share the same power source, when the LCD backlight brightness is below 100%, RGB will not be powered properly. Please use the RGB function when the backlight is at full brightness.</li></ul> <h2 id="features" data-id="Features">Features</h2> <ul><li>Stamp-S3A microcontroller</li> <li>56-key keyboard</li> <li>1.14-inch TFT display</li> <li>Cavity speaker and SPM1423 digital MEMS microphone</li> <li>Infrared emitter for infrared control interactions</li> <li>HY2.0-4P interface</li> <li>microSD card slot</li> <li>Built-in 120mAh and base 1400mAh lithium batteries</li> <li>Base with magnets</li> <li>LEGO hole expansion compatibility</li> <li>Development Platform<ul><li>UiFlow2</li> <li>Arduino IDE</li> <li>ESP-IDF</li> <li>PlatformIO</li></ul></li></ul> <h2 id="includes" data-id="Includes">Includes</h2> <ul><li>1 x Cardputer V1.1</li> <li>1 x Hex Key L-Shape 1.5mm (For M2 Screw)</li></ul> <h2 id="applications" data-id="Applications">Applications</h2> <ul><li>Rapid function verification and prototyping</li> <li>Industrial control and automation</li> <li>Home control systems</li> <li>Data acquisition and sensor monitoring</li> <li>Embedded system development and learning</li> <li>Wireless communication and IoT projects</li></ul> <h2 id="specifications" data-id="Specifications">Specifications</h2> <div class="table-container"><table><thead><tr><th>Specification</th> <th>Parameter</th></tr></thead><tbody><tr><td>SoC</td> <td>ESP32-S3FN8 @ Xtensa® 32-bit LX7 dual-core processor, clock frequency 240MHz</td></tr> <tr><td>USB</td> <td>USB OTG, USB Serial/JTAG</td></tr> <tr><td>Flash</td> <td>8MB</td></tr> <tr><td>Wi-Fi</td> <td>2.4 GHz Wi-Fi</td></tr> <tr><td>External Storage Expansion</td> <td>microSD</td></tr> <tr><td>Keyboard</td> <td>56 keys (4 x 14)</td></tr> <tr><td>Buttons</td> <td>1 x Reset button + 1 x User button</td></tr> <tr><td>Grove</td> <td>1 x HY2.0-4P</td></tr> <tr><td>Battery Capacity</td> <td>120mAh + 1400mAh (in base)</td></tr> <tr><td>Display</td> <td>ST7789V2@1.14 Inch, 240 x 135px</td></tr> <tr><td>Cavity Speaker</td> <td>8Ω@1W<br>I2S@NS4168</td></tr> <tr><td>Microphone</td> <td>MEMS microphone @SPM1423</td></tr> <tr><td>Infrared Transmission Distance</td> <td>Infrared transmission distance at ∠0° (straight line): 410cm <br>At ∠90°: 66cm<br>At ∠45°: 170cm</td></tr> <tr><td>Sleep Current</td> <td>DC 4.2V@0.15uA</td></tr> <tr><td>Operating Current</td> <td>In IR transmission mode: DC 4.2V/148.07mA <br>In key mode: DC 4.2V/138.93mA</td></tr> <tr><td>Operating Temperature</td> <td>0 ~ 40°C</td></tr> <tr><td>Product Size</td> <td>84.0 x 54.0 x 19.7mm</td></tr> <tr><td>Product Weight</td> <td>90.0g</td></tr> <tr><td>Package Size</td> <td>145.7 x 95.0 x 20.7mm</td></tr> <tr><td>Gross Weight</td> <td>106.8g</td></tr></tbody></table></div><h2 id="learn" data-id="Learn">Learn</h2> <h3 id="enter-download-mode" data-id="Enter Download Mode">Enter Download Mode</h3> <p>To enter download mode, set the side power switch of the Cardputer v1.1 to the <code>OFF</code> position, then hold down the <code>G0</code> button before powering on the device, release it after the device is powered on, and the device will enter download mode.</p> <img alt="schematics" src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/cardputer%20(2).gif" width="30%"> <h3 id="rgb-led-power-supply" data-id="RGB LED Power Supply">RGB LED Power Supply</h3> <div class="warn"><div class="warn-title">RGB LED Power Supply Instructions</div> <div class="warn-content">The device uses <strong>Stamp-S3A</strong> as its main controller. To optimize overall power consumption, Stamp-S3A adds an independent electronic switch for the RGB LED power supply compared with the previous Stamp-S3. Before controlling the RGB LED in software, set GPIO38, which controls this switch, to a high level.</div></div><h3 id="charging-notes" data-id="Charging Notes">Charging Notes</h3> <p>When charging the Cardputer v1.1, please switch the power to <code>ON</code>.</p><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132-V11_21.jpg" width="60%"> <h3 id="disassembly-notes" data-id="Disassembly Notes">Disassembly Notes</h3> <p>When removing the Stamp-S3A on the panel, be careful with the FPC cable and connector on the back. Gently lift them up, otherwise the socket for the display connection may be damaged. Refer to the operation video in <a target="_blank" href="/en/accessory/Cardputer%20Accessory%20Kit">Cardputer Accessory Kit</a> for guidance.</p><h2 id="schematics" data-id="Schematics">Schematics</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer.pdf">Cardputer V1.1 Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/M5Cardputer_Base.pdf">Cardputer V1.1 Base Schematics PDF</a></li> <li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf">Stamp-S3A Schematics PDF</a></li></ul> <div class="carousel-container" data-v-7d51a79c><div class="carousel-preview" data-v-7d51a79c><div class="clickable-area left" data-v-7d51a79c></div> <button class="arrow left" data-v-7d51a79c></button> <div class="carousel-images" data-v-7d51a79c><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-7d51a79c><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer_sch_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer_sch_02.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/M5Cardputer_Base_sch_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Preview" data-v-7d51a79c></div></div></div> <button class="arrow right" data-v-7d51a79c></button> <div class="clickable-area right" data-v-7d51a79c></div> <div class="corner-marker" data-v-7d51a79c>1/4</div></div> <div class="carousel-thumbnails" data-v-7d51a79c><div class="thumbnail active" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer_sch_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/Sch_M5Cardputer_sch_02.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/M5Cardputer_Base_sch_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3_page_01.png" alt="Thumbnail" data-v-7d51a79c></div></div></div> <h2 id="pinmap" data-id="PinMap">PinMap</h2> <h3 id="spm1423-mic" data-id="SPM1423 MIC">SPM1423 MIC</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G46</th> <th>G43</th> <th>3.3V</th> <th>GND</th></tr></thead><tbody><tr><td>SPM1423</td> <td>DAT</td> <td>CLK</td> <td>VCC</td> <td>GND</td></tr></tbody></table></div><h3 id="microsd-socket" data-id="microSD Socket">microSD Socket</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G12</th> <th>G14</th> <th>G40</th> <th>G39</th></tr></thead><tbody><tr><td>microSD Socket</td> <td>CS</td> <td>MOSI</td> <td>CLK</td> <td>MISO</td></tr></tbody></table></div><h3 id="st7789v2--rgb-led" data-id="ST7789V2  RGB LED">ST7789V2 & RGB LED</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G38</th> <th>G33</th> <th>G34</th> <th>G35</th> <th>G36</th> <th>G37</th></tr></thead><tbody><tr><td>ST7789V2</td> <td>DISP_BL</td> <td>RST</td> <td>RS</td> <td>DAT</td> <td>SCK</td> <td>CS</td></tr> <tr><td>RGB LED</td> <td>VDD</td> <td></td> <td></td> <td></td> <td></td> <td></td></tr></tbody></table></div><h3 id="keyboard--battery-detect" data-id="Keyboard  Battery Detect">Keyboard & Battery Detect</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G10</th> <th>G7/G6/G5/G4/G3/G15/G13</th> <th>G11/G9/G8</th></tr></thead><tbody><tr><td>Battery Detect(ADC)</td> <td>ADC</td> <td></td> <td></td></tr> <tr><td>74HC138</td> <td></td> <td>Y7~Y0</td> <td>A2/A1/A0</td></tr></tbody></table></div><h3 id="speaker--ir" data-id="Speaker  IR">Speaker & IR</h3> <div class="table-container"><table><thead><tr><th>ESP32-S3FN8</th> <th>G41</th> <th>G42</th> <th>G43</th> <th>G44</th></tr></thead><tbody><tr><td>NS4168 (Speaker)</td> <td>BCLK</td> <td>SDATA</td> <td>LRCLK</td> <td></td></tr> <tr><td>IR</td> <td></td> <td></td> <td></td> <td>TX</td></tr></tbody></table></div><h3 id="hy20-4p" data-id="HY2.0-4P">HY2.0-4P</h3> <div class="grove-table-container"><div class="table-container"><table><thead><tr><th>HY2.0-4P</th> <th>Black</th> <th>Red</th> <th>Yellow</th> <th>White</th></tr></thead><tbody><tr><td>PORT.CUSTOM</td> <td>GND</td> <td>5V</td> <td>G2</td> <td>G1</td></tr></tbody></table></div></div><h2 id="model-size" data-id="Model Size">Model Size</h2> <img alt="module size" src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-401ac270-d997-4164-ae79-d28be7a3dfaf.png" width="100%"> <h2 id="structure" data-id="Structure">Structure</h2> <ul><li><a target="_blank" href="https://github.com/m5stack/M5_Hardware/tree/master/Products/K132-V11_Cardputer_v1.1/Structures">Cardputer v1.1 Structure Files</a></li></ul> <h2 id="datasheets" data-id="Datasheets">Datasheets</h2> <ul><li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/SPM1423HM4H-B_datasheet_en.pdf">SPM1423</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/NS4168_CN_datasheet.pdf">NS4168</a></li> <li><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf">ST7789V2</a></li></ul> <h2 id="softwares" data-id="Softwares">Softwares</h2> <h3 id="arduino" data-id="Arduino">Arduino</h3> <ul><li><a target="_blank" href="/en/arduino/m5cardputer/program">Cardputer v1.1 Arduino Quick Start</a></li> <li><a target="_blank" href="https://github.com/m5stack/M5Cardputer">Cardputer v1.1 Arduino Library</a></li></ul> <h3 id="uiflow2" data-id="UiFlow2">UiFlow2</h3> <ul><li><a target="_blank" href="/en/uiflow2/cardputer/program">Cardputer v1.1 UiFlow2 Quick Start</a></li></ul> <h3 id="platformio" data-id="PlatformIO">PlatformIO</h3> <div class="code-block-wrapper"><div class="code-line-container"><pre><code class="hljs language-bash">[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code></pre> <button class="copy-all-btn"><code>[env:m5stack-cardputer]
-platform = espressif32@6.7.0
-board = esp32-s3-devkitc-1
-framework = arduino
-upload_speed = 1500000
-build_flags =
-    -DESP32S3
-    -DCORE_DEBUG_LEVEL=5
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-
-lib_deps =
-    M5Cardputer=https://github.com/m5stack/M5Cardputer</code> <div class="fa-solid fa-copy"></div></button></div></div> <h3 id="esp-idf" data-id="ESP-IDF">ESP-IDF</h3> <ul><li><a target="_blank" href="https://github.com/m5stack/M5Cardputer-UserDemo">Cardputer v1.1 Factory Firmware</a></li></ul> <h3 id="easyloader" data-id="Easyloader">Easyloader</h3> <div class="table-container"><table><thead><tr><th>Easyloader</th> <th>Download</th> <th>Note</th></tr></thead><tbody><tr><td>Cardputer v1.1 User Demo Easyloader</td> <td><a target="_blank" href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/Cardputer/Cardputer.exe">download</a></td> <td>/</td></tr></tbody></table></div><h2 id="video" data-id="Video">Video</h2> <div class="video-gallery-island" data-v-5e05839f></div> <h2 id="product-comparison" data-id="Product Comparison">Product Comparison</h2> <div class="compare-table-container"><div class="table-container"><table><thead><tr><th>Product Compare</th> <th><a target="_blank" href="/en/core/Cardputer%20V1.1">Cardputer v1.1</a><br><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1127/K132_v11_04.webp" alt="Cardputer v1.1"></th> <th><a target="_blank" href="/en/core/Cardputer">Cardputer</a><br><img src="https://static-cdn.m5stack.com/resource/docs/products/core/Cardputer/img-a02d6727-4fa1-4b38-90e6-75e401d507de.webp" alt="Cardputer"></th></tr></thead><tbody><tr><td>Core Module</td> <td>Stamp-S3A</td> <td>StampS3</td></tr> <tr><td>RGB LED Control Logic</td> <td>RGB LED shares power with screen backlight, optimized control logic</td> <td>Powered immediately upon power-on</td></tr> <tr><td>Antenna Design</td> <td>Optimized antenna design, better signal reception</td> <td>Standard antenna design</td></tr> <tr><td>StampS3 Module Boot Key</td> <td>Improved key feel, key size 4.0 x 3.0 x 2.0mm</td> <td>Key size 2.6 x 1.6 x 0.55mm</td></tr> <tr><td>Power Consumption</td> <td>Optimized for lower power consumption</td> <td>Standard design</td></tr></tbody></table></div></div><p>To compare information on the Cardputer series products, you can visit the <a target="_blank" href="/en/products_selector/m5cardputer_compare?select=K132-V11">Product Selection Table</a>, check the target products, and get the comparison results. The selection table covers key information such as core parameters and functional features, and supports comparison of multiple products simultaneously.</p><h2 id="version-change" data-id="Version Change">Version Change</h2> <div class="table-container"><table><thead><tr><th>Release Date</th> <th>Product Changes</th></tr></thead><tbody><tr><td>2025.8.2</td> <td>Key operating force changed from 260gf to 160gf</td></tr> <tr><td>/</td> <td>First release</td></tr></tbody></table></div></div> <!----> <!----> <!----></div></div> <div class="docs-layouts-anchor"><div class="page-tools" data-v-39baf185><div class="page-tools-title" data-v-39baf185>Page Tools</div> <div class="page-tools-actions" data-v-39baf185><a href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/Cardputer V1.1.pdf" target="_blank" rel="nofollow noopener noreferrer" title="Download PDF" class="page-tools-action page-tools-pdf" data-v-39baf185><svg viewBox="0 0 24 24" aria-hidden="true" class="page-tools-icon" data-v-39baf185><path d="M6 2h8l4 4v16H6V2zm7 1.8V7h3.2L13 3.8zM8.4 12.2h1.5c1 0 1.7-.6 1.7-1.6S10.9 9 9.9 9H7v6h1.4v-2.8zm0-1.1v-1h1.3c.3 0 .5.2.5.5s-.2.5-.5.5H8.4zm4.1 3.9h1.8c1.7 0 2.8-1.1 2.8-3s-1.1-3-2.8-3h-1.8v6zm1.4-1.2v-3.6h.4c.9 0 1.4.6 1.4 1.8s-.5 1.8-1.4 1.8h-.4zm4.1 1.2h1.4v-2.4h2.1v-1.2h-2.1v-1.2h2.4V9H18v6z" data-v-39baf185></path></svg> <span data-v-39baf185>PDF</span></a> <div class="markdown-action-menu placement-toolbox" data-v-5d6a4f8a data-v-39baf185><button type="button" title="Copy page" class="markdown-action-trigger" data-v-5d6a4f8a><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><rect x="9" y="9" width="13" height="13" rx="2"></rect><path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1"></path></svg> <span data-v-5d6a4f8a>Copy page</span> <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><polyline points="6 9 12 15 18 9"></polyline></svg></button> <!----></div></div></div></div></div> <footer><div class="footer-container"><div class="footer-content-wrap"><div class="footer-nav"><div class="footer-nav-item"><div data-id="0" class="footer-nav-title"><a class="footer-nav-title-a">
-        About Us
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/about-us">About M5Stack</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?page=1">News</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?type=blog&page=1">Blog</a></li><li class="footer-nav-li"><a href="https://m5stack.com/events">Events</a></li><li class="footer-nav-li"><a href="https://m5stack.com/contact">Contact Us</a></li></ul></div><div class="footer-nav-item"><div data-id="1" class="footer-nav-title"><a class="footer-nav-title-a">
-        Where to buy
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/distributor">Distributors</a></li><li class="footer-nav-li"><a href="https://shop.m5stack.com/">Official Store</a></li><li class="footer-nav-li"><a href="https://m5stack.aliexpress.com/store/911661199">AliExpress</a></li><li class="footer-nav-li"><a href="https://www.amazon.com/shops/m5stack">Amazon</a></li><li class="footer-nav-li"><a href="https://m5stack.taobao.com/">Taobao</a></li></ul></div><div class="footer-nav-item"><div data-id="2" class="footer-nav-title"><a class="footer-nav-title-a">
-        Solution
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/business">For Business</a></li><li class="footer-nav-li"><a href="https://m5stack.com/developers">For Developers</a></li></ul></div><div class="footer-nav-item"><div data-id="3" class="footer-nav-title"><a class="footer-nav-title-a">
-        Software
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://flow.m5stack.com/">UiFlow1</a></li><li class="footer-nav-li"><a href="https://uiflow2.m5stack.com/">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/uiflow/m5burner/intro">M5Burner</a></li><li class="footer-nav-li"><a href="https://block-designer.m5stack.com/">Block Designer</a></li><li class="footer-nav-li"><a href="/en/guide/ezdata/ezdata_v2">EzData 2.0</a></li><li class="footer-nav-li"><a href="/en/guide/easyloader/easyloader_packer">EasyLoader Packer</a></li><li class="footer-nav-li"><a href="/en/guide/develop_tools/vlw_font_creator">VLW Font Creator</a></li><li class="footer-nav-li"><a href="/en/download">Device USB Driver</a></li></ul></div><div class="footer-nav-item"><div data-id="4" class="footer-nav-title"><a class="footer-nav-title-a">
-        Documentation
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="/en/products">Product Documents</a></li><li class="footer-nav-li"><a href="/en/uiflow/uiflow_web">UiFlow1</a></li><li class="footer-nav-li"><a href="/en/uiflow2/uiflow_web">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/arduino/arduino_ide">Arduino</a></li><li class="footer-nav-li"><a href="/en/esp_idf/esp_idf">ESP-IDF</a></li><li class="footer-nav-li"><a href="/en/stackflow/overview">StackFlow AI</a></li><li class="footer-nav-li"><a href="/en/homeassistant/overview">Home Assistant</a></li><li class="footer-nav-li"><a href="https://github.com/nanoframework/nanoFramework.M5Stack">nanoFramework</a></li><li class="footer-nav-li"><a href="/en/guide/product_guide">Product Guide</a></li><li class="footer-nav-li"><a href="/en/certification">Product Certifications</a></li><li class="footer-nav-li"><a href="/en/product_i2c_addr">I2C Table</a></li><li class="footer-nav-li"><a href="/en/products_selector/m5core_compare">Product Selector</a></li><li class="footer-nav-li"><a href="https://github.com/m5stack/M5_Hardware">Hardware Design Files</a></li><li class="footer-nav-li"><a href="/en/history">Release History</a></li><li class="footer-nav-li"><a href="/en/compatible_stack">Stack Compatibility</a></li><li class="footer-nav-li"><a href="/en/learn/extension/module">Stack Screw Length</a></li></ul></div></div> <div class="footer-right"><div class="footer-email-group"><p class="footer-email-title">
-              Stay in the Loop
-            </p> <p class="footer-email-desc">
-              Weekly updates on new products, innovations, and announcements.
-            </p> <div class="footer-email-input"><input placeholder="Enter Email address" autocomplete="off" class="email-input"> <button type="button" class="subscribe-btn">
-                Subscribe
-              </button></div> <p class="footer-email-warning" style="display:none">
-              Email is invalid!
-            </p></div> <div class="footer-email-success" style="display:none">
-            Thanks for subscribing
-          </div> <div class="footer-follow"><div class="footer-follow-ul"><a href="https://x.com/M5Stack"><img src="/assets/footer/sociallist10.svg" alt></a><a href="https://www.linkedin.com/company/m5stack"><img src="/assets/footer/sociallist2.svg" alt></a><a href="https://www.instagram.com/m5stack"><img src="/assets/footer/sociallist8.svg" alt></a><a href="https://www.facebook.com/M5Stack"><img src="/assets/footer/sociallist7.svg" alt></a><a href="https://www.youtube.com/m5stack"><img src="/assets/footer/sociallist5.svg" alt></a><a href="https://www.tiktok.com/@m5stack"><img src="/assets/footer/tiktok.svg" alt></a><a href="https://www.hackster.io/m5stack"><img src="/assets/footer/sociallist3.svg" alt></a><a href="https://discord.gg/ysQAWBUE9Q"><img src="/assets/footer/sociallist4.svg" alt></a><a href="https://github.com/m5stack"><img src="/assets/footer/sociallist6.svg" alt></a></div></div> <div class="footer-info-wrapper"><div class="footer-info">
-            M5Stack Technology Co., Ltd
-          </div> <div class="footer-address-info">
-            Address: 
-             Block A10, Expo Bay South Coast, Fuhai Street, Bao'an District, Shenzhen, China
-          </div> <div class="footer-info">
-            TEL: 
-            +86 755 8657 5379
-          </div> <div class="footer-info">
-            Email: 
-            support@m5stack.com
-          </div></div></div></div></div> <div class="footer-bottom"><div class="footer-bottom-content"><div class="footer-copy">
-        Copyright ©
-        <a href="https://m5stack.com/">M5Stack Technology Co., Ltd.</a>
-        All rights reserved.
-      </div> <div class="terms-box"><!----> <a href="https://shop.m5stack.com/policies/privacy-policy">Privacy Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/terms-of-service">Terms of Service</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/shipping-policy">Shipping Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/refund-policy">Refund Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/pages/payment-method">Payment Method</a></div> <div class="beian"><a href="https://beian.miit.gov.cn/">粤ICP备16010631号</a></div></div></div> <!----></footer> <div class="float-icon-container"><div class="totop-icon"><svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 280 280" xmlns:xlink="http://www.w3.org/1999/xlink" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M143 70l58 69c1,1 1,3 1,4 -1,1 -2,2 -4,2l-20 0c-2,0 -4,2 -4,4l1 57c0,2 -2,4 -4,4l-62 0c-2,0 -4,-2 -4,-4l1 -57c0,-2 -2,-4 -4,-4l-20 0c-2,0 -3,-1 -4,-2 -1,-1 0,-3 1,-4l58 -69c1,-1 2,-1 3,-1 1,0 2,1 3,1z" class="fil1"></path></g></svg></div> <div class="menu-icon" style="display:none"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 800 800" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M253 229l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 370l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 511l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path></g></svg></div></div></div></div></div></div><script defer src="/_nuxt/static/1788504562/en/core/Cardputer%20V1.1/state.js"></script><script src="/_nuxt/41d5c62.js" defer></script><script src="/_nuxt/c970150.js" defer></script><script src="/_nuxt/5a34d22.js" defer></script><script src="/_nuxt/a352c6d.js" defer></script><script src="/_nuxt/b9c4bc6.js" defer></script>
-  </body>
-</html>
diff --git a/devices/m5stack/cardputer-v1.1/artifacts/schematic/M5Cardputer_Base.pdf b/devices/m5stack/cardputer-v1.1/artifacts/schematic/M5Cardputer_Base.pdf
deleted file mode 100644
index d63ee76..0000000
Binary files a/devices/m5stack/cardputer-v1.1/artifacts/schematic/M5Cardputer_Base.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-v1.1/artifacts/schematic/Sch_M5Cardputer.pdf b/devices/m5stack/cardputer-v1.1/artifacts/schematic/Sch_M5Cardputer.pdf
deleted file mode 100644
index 60995e3..0000000
Binary files a/devices/m5stack/cardputer-v1.1/artifacts/schematic/Sch_M5Cardputer.pdf and /dev/null differ
diff --git a/devices/m5stack/cardputer-v1.1/certification-and-compliance.md b/devices/m5stack/cardputer-v1.1/certification-and-compliance.md
deleted file mode 100644
index ab03977..0000000
--- a/devices/m5stack/cardputer-v1.1/certification-and-compliance.md
+++ /dev/null
@@ -1,159 +0,0 @@
-# Certification and compliance — cardputer-v1.1
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-No v1.1-specific grant. `2AN3WM5CARDPUTER` (2024-07-22) is the only non-ADV Cardputer filing.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5CARDPUTER` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AN3WM5STAMPS3A`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5CARDPUTER`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2024-07-22** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2024-07-22 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5CARDPUTER` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 1,811,474 | `daafa38179323ddb…` |
-| `ID-Label-Location-Info-FCC-ID-Label.pdf` | 467,757 | `fcdfbce02de768d7…` |
-| `Internal-Photos-Internal-Photos.pdf` | 1,588,902 | `04d0f83f4d202d9f…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE.pdf` | 126,467 | `6c89ae08c922ccde…` |
-| `Test-Report-Antenna-Specification.pdf` | 822,846 | `0728acb7f328e39c…` |
-| `Users-Manual-User-Manual.pdf` | 3,165,025 | `629df489491ef940…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5CARDPUTER/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5CARDPUTER/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AN3WM5STAMPS3A`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2025-02-13** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2025-02-13 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5STAMPS3A` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 2,142,184 | `6910fdc8e5f46913…` |
-| `ID-Label-Location-Info-label-and-location.pdf` | 69,357 | `60d9ccb36cc10e2a…` |
-| `Internal-Photos-Internal-Photos.pdf` | 2,778,287 | `e6512283b0e419c2…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE-20cm-.pdf` | 176,710 | `db49d95ade5911cc…` |
-| `Test-Report-AiTDG-241205002W1-Test-Report-BLE.pdf` | 959,274 | `027dd133c4ac00b6…` |
-| `Users-Manual-User-Manual.pdf` | 2,308,121 | `e9056d899bdd6cda…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5STAMPS3A/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5STAMPS3A/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cardputer-v1.1/market-and-pricing.md b/devices/m5stack/cardputer-v1.1/market-and-pricing.md
deleted file mode 100644
index 07fc4a9..0000000
--- a/devices/m5stack/cardputer-v1.1/market-and-pricing.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Market and pricing — cardputer-v1.1
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| [EOL] M5Stack Cardputer with M5StampS3 v1.1 | 2025-03-07 | Default Title | `K132-V11` | **USD 29.90** | ✅ yes |
-| Cardputer Accessory Kit v1.1 (M5StampS3A + Display) | 2025-07-04 | Default Title | `A145-V033` | **USD 9.95** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 29.90, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/m5stack-cardputer-with-m5stamps3-v1-1`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-`K132-V11` complete kit vs `A145-V033` accessory-only. **Normalised: the USD 29.90 figure is the complete kit.** ⚠ The kit is `[EOL]`-titled yet still `available: true` — the store's EOL tag and its stock flag disagree.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/cardputer-zero/README.md b/devices/m5stack/cardputer-zero/README.md
deleted file mode 100644
index 58d9bdc..0000000
--- a/devices/m5stack/cardputer-zero/README.md
+++ /dev/null
@@ -1,133 +0,0 @@
-# M5Stack CardputerZero (C154 / C155-Lite)
-
-> **SKU `C154`** (with 32 GB microSD) and **`C155`** (`-Lite`, no card) · product id **`1243`**
-> Schematic `C154-CardputerZERO_SCH_V0.6.1_20260702.pdf`
-> ⚠ **M5Stack's own page carries a "Work in progress" banner**: *"This product's packaging and
-> software development are not yet complete. Final features and documentation are subject to
-> change."* Crowdfunded on Kickstarter in spring 2026; not generally on sale as of **2026-09-04**.
-> Research snapshot **2026-09-04**.
-
-**This is not a faster Cardputer. It is a different computer that happens to be the same shape.**
-Where every other Cardputer is an ESP32-S3 microcontroller, the CardputerZero is a **Raspberry Pi
-Compute Module 0** running Linux — quad-core Cortex-A53, 512 MB LPDDR2, a camera, Ethernet, USB
-host, an RTC and a fuel gauge.
-
-This record is deliberately light: the product is unfinished, its documentation says so, and
-committing detail now would be committing to something that will change. What is recorded here
-is the identity, the confirmed architecture, and — most usefully — **what it shares with the
-Cardputer ADV**.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| SKUs | `C154` (32 GB card included) · `C155` **`-Lite`** (no card) |
-| Core | **Raspberry Pi Compute Module 0 (CM0)** |
-| CPU | RP3A0 (BCM2837), quad-core Cortex-A53 @ 1 GHz, ARMv8-A aarch64 |
-| RAM | **512 MB LPDDR2** |
-| Storage | microSD only |
-| Display | **1.9″ ST7789v3, 320 × 170** |
-| Keyboard | **46 keys** (not 56), **TCA8418RTWR @ `0x34`** |
-| Camera | **IMX219 CSI 4-lane, 8 MP (3280 × 2464)** |
-| IMU | **BMI270 @ `0x68`** + **BMM150 magnetometer @ `0x10`** |
-| **RTC** | **RX8130CE @ `0x32`** |
-| **Fuel gauge** | **BQ27220YZFR** |
-| I/O expander | **M5IOE1 @ `0x4F`** |
-| Audio | **ES8389** codec, MEMS mic, **AW8737A** amp, 1 W 8 Ω, **3.5 mm TRRS** with CTIA/OMTP switching |
-| Video | 1080p30 out; H.264/MPEG-4 1080p30 decode, H.264 1080p30 encode |
-| Network | 2.4 GHz Wi-Fi b/g/n + **10/100 Ethernet** via **SR9900A** USB-Ethernet |
-| USB | **GL852G-OHY60 hub**, 1 × USB-A, 2 × USB-C, physical **Host/Slave toggle**, OTG on the right port |
-| IR | **transmitter *and* receiver** |
-| Expansion | **EXT 2.54-14P** + HY2.0-4P with **switchable I²C/UART** (< 500 mA on 5 V) |
-| Battery | 3.7 V **1750 mAh with integrated NTC** |
-| Idle power | **2.5 W** |
-| Supply | 5 V @ 2 A recommended |
-| Size | 84.0 × 54.0 × **23.1 mm** |
-
-## What it shares with the Cardputer ADV
-
-Three things, and they are worth knowing because they are reusable knowledge:
-
-1. **The TCA8418RTWR keypad scanner at `0x34`.** Same part, same address, 46 keys instead of 56.
-   → [`../cardputer-adv/features/keyboard.md`](../cardputer-adv/features/keyboard.md),
-   [`texas-instruments/tca8418`](../../../components/texas-instruments/tca8418/README.md).
-2. **The BMI270 IMU** — but at **`0x68`**, not the ADV's `0x69` (`SDO` strapped the other way),
-   and here it carries a **BMM150 magnetometer on its auxiliary I²C interface**, which the ADV's
-   BMI270 has pinned out but unpopulated.
-3. **The EXT 2.54-14P connector**, with the same physical shape and the same
-   `5VIN / GND / 5VOUT / I2C_SDA / I2C_SCL / UART` positions on the right column.
-
-## ⚠ The EXT header is *not* pin-compatible with the ADV's
-
-Same connector, different left column, and the UART pair is **swapped relative to the ADV's
-product page**:
-
-| Position | Cardputer ADV | CardputerZero |
-|---|---|---|
-| L1 | `RESET` G3 | **`HAT_P0`** — `USB4_D_P` **or** `GPIO26`, switchable |
-| L2 | `INT` G4 | **`HAT_P1`** — `USB4_D_N` **or** `GPIO23` |
-| L3 | `BUSY` G6 | `G22` |
-| L4 | `SCK` G40 | `SPI0_CLK` G11 |
-| L5 | `MOSI` G14 | `SPI0_MOSI` G10 |
-| L6 | `MISO` G39 | `SPI0_MISO` G9 |
-| L7 | `CS` G5 | `SPI0_CS1` G7 |
-| R1–R3 | `5VIN`, `GND`, `5VOUT` | **same** |
-| R4/R5 | `I2C_SDA` G8 / `I2C_SCL` G9 | `I2C1_SDA` G2 / `I2C1_SCL` G3 |
-| R6 | **`UART_TX`** G13 | **`UART_RXD`** G15 |
-| R7 | **`UART_RX`** G15 | **`UART_TXD`** G14 |
-
-**A CAP board that uses only power + I²C has a chance of working on both. One that uses
-`RESET`/`INT`/`BUSY` — i.e. the Cap LoRa-1262 and the Cap CC1101 — does not.** And the UART pair
-is reversed, so even a serial-only board needs its TX/RX swapping.
-
-The `HAT_P0`/`HAT_P1` pins are genuinely novel: `PYG1_HAT_SW` on the M5IOE1 switches them between
-**GPIO** (default) and **USB Hub port 4**, so a CardputerZero HAT can be a USB device.
-`PYG13_HAT_EN` gates the port's power.
-
-## Architecture highlights
-
-* **M5IOE1** (`0x4F`) — M5Stack's own I/O expander, already documented at
-  [`components/m5stack/m5ioe1`](../../../components/m5stack/m5ioe1/README.md) from the PaperMono
-  pass. Here it owns LCD reset and backlight PWM, the shared **keyboard + USB-hub reset**
-  (`PYG3_KB_HUB_RST`), the CTIA/OMTP microphone switch (`PYG6_MIC_SW`), Grove 5 V enable, HAT
-  enable and switching, power detect/enable, and three **CAPS/SHIFT/FN/SYM indicator LEDs** —
-  something no ESP32 Cardputer has.
-* **USB Host/Slave is a physical switch.** In Slave mode the hub is disconnected and the USB-A
-  port, the left USB-C, the HAT USB pins and Ethernet all go away.
-* **Headphone detect reaches a CPU GPIO** (`G17`) and the amplifier is enabled from `G24` — where
-  the ADV does the same job entirely in hardware and software cannot see it.
-* **RX8130CE RTC** — the ADV has no RTC at all. → [`components/seiko-epson`](../../../components/seiko-epson/) (part record not created by this pass).
-
-## Software
-
-`https://docs.m5stack.com/en/guide/linux/cardputerzero/image` (flashing) and `…/adb`
-(ADB debugging); application template at `github.com/CardputerZero/Template`; SDK and kernel
-pages both say *"coming soon…"*. M5Stack also maintains `m5stack/CardputerZeroRepository`.
-Community index: `UnAneOnyme/CardputerZeroCollection` (CC0-1.0).
-
-## Community
-
-r/CardPuterZero exists as a separate subreddit. The Kickstarter announcement threads are among
-the largest in the family: *"CARDPUTER ZERO 😱"* (r/CardPuter 2026-03-06, ↑698/105),
-*"CardputerZero KickStarter !!!"* (2026-04-16, ↑283/**140 comments**), and an AMA
-(2026-04-17, ↑151/114). *"Cardputer Zero is the same thickness as the ADV!"* (2026-05-05, ↑370).
-
-The recurring confusion is exactly the one this record exists to clear up. u/G33K_FISH,
-r/CardPuter 2026-05-31: *"FYI, the ADV and the Zero are different. The Zero will be linux based.
-You can do things on the Zero you can not do on the ADV and vise versa."*
-And a skeptical counterpoint from r/CardPuterZero (2026-07-16): *"Everyone is waiting for the
-Cardputer Zero, but you know that your phone can do the same…"* (41 comments).
-
-## Not researched in this pass
-
-The schematic (`…/1243/C154-CardputerZERO_SCH_V0.6.1_20260702.pdf`), the sticker design files
-(`…/1243/CardputerZero_Labels.zip`), the Linux image, the ADB guide and the application template
-were all **identified and not fetched**. A device whose vendor says its features are subject to
-change does not warrant a full-depth record yet. When it ships, the two things worth doing first
-are parsing that schematic and diffing the EXT header against this table.
-
-## Sources
-
-`https://docs.m5stack.com/en/CardputerZero` (retrieved 2026-09-04, snapshot at
-`artifacts/docs-en-CardputerZero.html`); Reddit threads cited inline.
-Full table: [`../cardputer-adv/sources.md`](../cardputer-adv/sources.md).
diff --git a/devices/m5stack/cardputer-zero/artifacts/docs-en-CardputerZero.html b/devices/m5stack/cardputer-zero/artifacts/docs-en-CardputerZero.html
deleted file mode 100644
index 9851469..0000000
--- a/devices/m5stack/cardputer-zero/artifacts/docs-en-CardputerZero.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<!doctype html>
-<html data-n-head-ssr lang="en" data-n-head="%7B%22lang%22:%7B%22ssr%22:%22en%22%7D%7D">
-  <head>
-    <title>m5-docs</title><meta data-n-head="ssr" charset="utf-8"><meta data-n-head="ssr" name="viewport" content="width=device-width,initial-scale=1,minimum-scale=1,user-scalable=no"><meta data-n-head="ssr" data-hid="description" name="description" content="The reference docs for M5Stack products. Quick start, get the detailed information or instructions such as IDE,UIFLOW,Arduino. The tutorials for M5Burner, Firmware, Burning, programming. ESP32,M5StickC,StickV, StickT,M5ATOM."><link data-n-head="ssr" rel="icon" type="image/x-icon" href="/favicon.ico"><script data-n-head="ssr" data-hid="device-preload-detector">!function(){try{var e=document.documentElement;if(!e)return;var d=e.clientWidth||Number.POSITIVE_INFINITY,i=Number(window.innerWidth||0)||Number.POSITIVE_INFINITY,a=Math.min(d,i)<1024;e.classList.add(a?"device-preload-mobile":"device-preload-desktop"),a&&(e.classList.add("device-preload-pending"),window.__m5DevicePreloadReady=function(){e.classList.remove("device-preload-pending"),e.classList.add("device-preload-ready")})}catch(e){}}()</script><script data-n-head="ssr" src="https://cloud.umami.is/script.js" data-website-id="38e73ff2-ec10-4a8f-bfe2-c22a381ce306" defer></script><script data-n-head="ssr" src="/script/ga.js"></script><script data-n-head="ssr" src="/script/global.js"></script><script data-n-head="ssr" src="/public/esp-web-tools/install-button.js?module" type="module"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/marked.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/highlight.min.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-chat/index.js"></script><script data-n-head="ssr" src="https://static-cdn.m5stack.com/resource/public/compressed/libs/widget-qa/index.js"></script><link rel="preload" href="/_nuxt/41d5c62.js" as="script"><link rel="preload" href="/_nuxt/5a34d22.js" as="script"><link rel="preload" href="/_nuxt/a352c6d.js" as="script"><link rel="preload" href="/_nuxt/b9c4bc6.js" as="script"><link rel="preload" href="/_nuxt/c970150.js" as="script"><style data-vue-ssr-id="0b40e9c2:0 afa51714:0 73039f54:0 2576b79a:0 69f1b16c:0 17a511fe:0 3d88442c:0 3afe6180:0 786f8504:0 1af4924a:0 e762b0ec:0 e646c77c:0 4a658548:0 5f76b520:0 3e555512:0 4e0caf6f:0 060bbeb3:0 3ddd7ff2:0 bb0e6f22:0 27d15a7c:0 2c0daf93:0 d1c8934a:0 09fcdd3b:0 8716e91a:0 09d04477:0">body,html{width:100%;margin:0;padding:0}html.device-preload-mobile.device-preload-pending{background:linear-gradient(180deg,#f7f9fc,#eef3f8)}html.device-preload-mobile.device-preload-pending body{background:0 0}html.device-preload-mobile.device-preload-pending body:before{content:"";position:fixed;top:0;right:0;bottom:0;left:0;z-index:9999;pointer-events:none;background:linear-gradient(180deg,hsla(0,0%,100%,.92),rgba(243,247,251,.98)),radial-gradient(circle at top right,rgba(0,100,194,.08),transparent 38%)}html.device-preload-mobile.device-preload-pending body:after{content:"";position:fixed;left:50%;top:50%;width:.63529rem;height:.63529rem;margin-left:-.31765rem;margin-top:-.31765rem;z-index:10000;pointer-events:none;border:.04706rem solid rgba(35,141,251,.18);border-top-color:#238dfb;border-radius:50%;box-shadow:0 0 0 .09412rem rgba(35,141,251,.08);-webkit-animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite;animation:device-preload-spin .9s linear infinite,device-preload-breathe 1.4s ease-in-out infinite}html.device-preload-mobile.device-preload-pending .device-hydration-sensitive{opacity:0;visibility:hidden}html.device-preload-mobile.device-preload-ready body:after,html.device-preload-mobile.device-preload-ready body:before{opacity:0;transition:opacity .22s ease}html.device-preload-mobile.device-preload-ready .device-hydration-sensitive{visibility:visible;opacity:1;transition:opacity .18s ease}@-webkit-keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes device-preload-spin{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@-webkit-keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}@keyframes device-preload-breathe{0%,to{box-shadow:0 0 0 .09412rem rgba(35,141,251,.08)}50%{box-shadow:0 0 0 .16471rem rgba(35,141,251,.04)}}html{overflow:hidden;overflow-y:auto}html::-webkit-scrollbar{width:.14118rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}html::-webkit-scrollbar-thumb,html::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}@font-face{font-family:SourceCodePro;src:url(https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/assets/font/SourceCodePro-Regular.ttf)}body,button{font-family:SourceCodePro,Microsoft YaHei;line-height:inherit;box-sizing:border-box}body,button,input{font-family:SourceCodePro,Microsoft YaHei,sans-serif}a{outline:0}.product_pic img{width:33%}.page-enter-active,.page-leave-active{transition:opacity .5s}.page-enter,.page-leave-active{opacity:0}.bounce-enter-active{-webkit-animation:bounce-in .8s;animation:bounce-in .8s}.bounce-leave-active{-webkit-animation:bounce-out .5s;animation:bounce-out .5s}@-webkit-keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-in{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@-webkit-keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}@keyframes bounce-out{0%{transform:scale(1)}50%{transform:scale(1.01)}to{transform:scale(1)}}body,button,html[lang=zh-cn] footer,html[lang=zh-cn] header,input{font-family:Microsoft YaHei,sans-serif}html[lang=en] footer,html[lang=en] header{font-family:Montserrat,Microsoft YaHei,sans-serif}@font-face{font-family:Montserrat;font-weight:400;font-style:normal;src:url(/assets/fonts/Montserrat-Regular.woff2) format("woff2"),url(/assets/fonts/Montserrat-Regular.woff) format("woff"),url(/assets/fonts/Montserrat-Regular.otf) format("opentype"),url(/assets/fonts/Montserrat-Regular.ttf) format("truetype")}@font-face{font-family:Montserrat;font-weight:500;font-style:normal;src:url(/assets/fonts/Montserrat-Medium.woff2) format("woff2"),url(/assets/fonts/Montserrat-Medium.woff) format("woff"),url(/assets/fonts/Montserrat-Medium.otf) format("opentype"),url(/assets/fonts/Montserrat-Medium.ttf) format("truetype")}*{margin:0;padding:0;box-sizing:border-box}html{height:auto!important;font-size:10vw;line-height:1}@media screen and (max-width:320px){html{font-size:32PX}}@media screen and (min-width:540px){html{font-size:44PX}}@media screen and (min-width:860px){html{font-size:48PX}}@media screen and (min-width:960px){html{font-size:49PX}}@media screen and (min-width:1024px){html{font-size:52PX}}@media screen and (min-width:1175px){html{font-size:53PX}}@media screen and (min-width:1280px){html{font-size:56PX}}@media screen and (min-width:1366px){html{font-size:63PX}}@media screen and (min-width:1400px){html{font-size:68PX}}@media screen and (min-width:1440px){html{font-size:69PX}}@media screen and (min-width:1540px){html{font-size:73PX}}@media screen and (min-width:1680px){html{font-size:75PX}}@media screen and (min-width:1920px){html{font-size:75PX}}@media screen and (min-width:2560px){html{font-size:85PX}}body{-webkit-font-smoothing:subpixel-antialiased}li{list-style-type:none}img,li{-webkit-user-drag:none}img{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}a{text-decoration:none;-webkit-user-drag:none}a,button{outline:0}button{border:none;background-color:transparent;cursor:pointer}.fade-enter-active,.fade-leave-active{transition:opacity .5s}.fade-enter,.fade-leave-to{opacity:0}.markdown.guide img{box-shadow:0 -.07059rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);margin-top:.17647rem;margin-bottom:.58824rem;margin-left:.11765rem}.markdown.guide .blockly_svg{box-shadow:unset;margin:.17647rem 0 .05882rem;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content}.docs-layouts{padding-top:.58824rem;display:flex;justify-content:center;position:relative;margin-bottom:.35294rem}.docs-layouts .docs-layouts-sidebar{position:sticky;top:1.17647rem;left:0;height:-webkit-max-content;height:-moz-max-content;height:max-content;z-index:2;background-color:#fff}.docs-layouts .docs-layouts-title{display:flex;flex-direction:row;margin-bottom:.11765rem;align-items:center;width:100%;height:.47059rem;border-bottom:.03529rem solid #f5f5f5}.docs-layouts .docs-layouts-title .docs-layouts-icon{background-color:#238dfb;border-radius:.11765rem;display:flex;justify-content:center;align-items:center;height:.35294rem;width:.35294rem;margin-right:.11765rem}.docs-layouts .docs-layouts-title .docs-layouts-icon img{width:.23529rem;height:.23529rem}.docs-layouts .docs-layouts-title p{font-size:.23529rem;font-weight:700;color:#2f495e;line-height:.35294rem}.docs-layouts .docs-layouts-body{width:14.11765rem;min-width:0;max-width:100%;margin:0 .29412rem}.docs-layouts .docs-layouts-anchor{position:sticky;top:1.2rem;right:0;z-index:1;background-color:#fff;height:80vh;overflow-y:scroll}@media screen and (max-width:1200px){.docs-layouts .docs-layouts-anchor{display:none}}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar{width:.14118rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb,.docs-layouts .docs-layouts-anchor::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.mobile .docs-layouts{padding:.35294rem;display:flex}.mobile .docs-layouts .docs-layouts-body{width:100%;min-width:0;max-width:100%;margin:0}.mobile .docs-layouts .docs-layouts-sidebar{position:fixed;height:100vh;width:5.17647rem;top:0;padding:.47059rem .35294rem;left:auto;left:-100%;box-shadow:.11765rem .23529rem .23529rem -.02353rem rgba(19,41,75,.15),.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.14),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.14),-.04706rem 0 .05882rem -.02353rem rgba(19,41,75,.13);transition:all .25s ease;z-index:5}.mobile .docs-layouts .docs-layouts-sidebar.active{left:0}.default{color:#3f3f46}.primary{color:#006fee}.secondary{color:#9353d3}.success{color:#17c964}.warning{color:#f5a524}.danger{color:#f31260}.markdown{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-column-gap:.18824rem;-moz-column-gap:.18824rem;column-gap:.18824rem;min-width:0;max-width:100%;overflow:hidden;word-break:break-word;padding-bottom:.35294rem;color:#4f5f6f;font-size:.18824rem;font-weight:400}.markdown>*{grid-column:1/-1}.markdown .product-sku{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .product-date,.markdown .product-sku{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.09412rem 0 .09412rem .09412rem;display:inline-block}.markdown .product-date{background-color:#efefef;color:#345b83}.markdown .tag-green{background-color:#f0fff4;color:#00c58e}.markdown .tag-blue,.markdown .tag-green{font-size:.23529rem;border-radius:.03529rem;padding:.02353rem .11765rem;margin:.11765rem;display:inline-block}.markdown .tag-blue{background-color:rgba(35,141,251,.07843);color:#238dfb}.markdown .tag-orange{font-size:.23529rem;margin:.23529rem .23529rem .23529rem 0;border-radius:.03529rem;padding:.02353rem .11765rem;background-color:#f8b013;color:#fff;cursor:pointer}.markdown .product-title{display:flex;align-items:center}.markdown .product-title span{color:#2f495e}.markdown .shop-title{display:flex;justify-content:space-between;position:relative;margin:.02353rem 0 0 .09412rem;background:#007bff;border-radius:.05882rem;color:#2f495e}.markdown .shop-title .shop-text{width:0;height:.47059rem;line-height:.47059rem;font-size:.2rem;text-align:center;color:#fff;overflow:hidden;transition:all .2s ease}.markdown .shop-title .shop-icon{position:relative;width:.47059rem;height:.47059rem;font-size:.35294rem;text-align:center;display:inline-block}.markdown .shop-title .shop-icon img{width:.35294rem;height:100%;display:inline-block}.markdown .shop-title .shop-icon:before{content:"";position:absolute;top:50%;right:-.32941rem;width:0;height:0;border-left:.23529rem solid transparent;border-right:.23529rem solid transparent;border-bottom:.23529rem solid #007bff;transform:translateY(-50%) rotate(90deg);display:none}.markdown .shop-title .shop-icon.eol:before{display:none}.markdown .shop-title:hover{color:#238dfb}.markdown .shop-title:hover .shop-text{width:2.35294rem}.markdown .shop-title:hover .shop-icon:before{display:block}.markdown .shop-title:hover .shop-icon.eol:before{display:none}.markdown .eol-title{display:flex;align-items:center;position:relative;margin:.02353rem 0 0 .08235rem;padding:0 .17647rem;height:.47059rem;line-height:.47059rem;background-color:#2f495e;border-radius:.05882rem}.markdown .eol-title .eol-text{font-size:.2rem;color:#fff}.markdown video{display:block;width:50%;margin-bottom:.35294rem}.markdown .video-iframe{margin:.23529rem 0;height:5.88235rem}.markdown .video-iframe iframe{width:50%;height:100%}.markdown .video-iframe>a{font-size:.23529rem;display:block;margin-bottom:.23529rem}.markdown a{color:#238dfb}.markdown h1{margin-top:.28235rem;margin-bottom:.21176rem;font-size:.54118rem;line-height:1.25}.markdown h1,.markdown h2{font-weight:600;color:#2f495e}.markdown h2{margin-top:.42353rem;margin-bottom:.18824rem;font-size:.35294rem;line-height:1.35;padding:0 .42353rem .11765rem .16471rem;position:relative;border-bottom:.01176rem solid #dfe5ec;cursor:pointer;transition:all .3s}.markdown h2:after{content:"";width:.03529rem;top:.04706rem;bottom:.16471rem;background:#238dfb;position:absolute;left:0}.markdown h2:before{content:"";position:absolute;background-image:url(/assets/link.svg);width:.29412rem;height:.29412rem;background-size:.29412rem;top:.08235rem;right:.05882rem;opacity:0;transition:opacity .3s}.markdown h2:hover{color:#0064c2}.markdown h2:hover:before{opacity:1}.markdown h3{margin-top:.32941rem;margin-bottom:.16471rem;font-size:.28235rem;color:#34495e;line-height:1.4}.markdown h3,.markdown h4{font-weight:600;position:relative}.markdown h4{margin-top:.28235rem;margin-bottom:.14118rem;font-size:.23529rem;color:#43566a;line-height:1.45}.markdown h5{margin-top:.23529rem;margin-bottom:.11765rem;font-size:.21176rem;font-weight:600;color:#526579;position:relative;line-height:1.5}.markdown ul{margin-bottom:.23529rem}.markdown ul ul{margin-bottom:.11765rem}.markdown ul li{list-style-type:circle;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f}.markdown ol{margin-bottom:.23529rem}.markdown ol li{list-style-type:decimal;margin-left:.35294rem;font-size:.18824rem;line-height:.31765rem;color:#4f5f6f;padding-left:.05882rem}.markdown ol li::marker{color:#6f6f6f;font-weight:700}.markdown code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;position:relative;color:#263445;font-size:.18824rem}.markdown :not(pre)>code{padding:.02353rem .05882rem;color:#165f8f;background:#eef3f7;border:.01176rem solid #dfe5ec;border-radius:.04706rem;font-size:.92em;font-weight:500}.markdown p{color:#4f5f6f;font-size:.18824rem;font-weight:400;line-height:.31765rem;margin-bottom:.16471rem}.markdown mark{background-color:#ffe051;color:#000}.markdown img{margin-bottom:.35294rem}.markdown>img:not([width]):not([class]){max-width:100%}.markdown .hljs{margin:.05882rem 0 .35294rem;font-size:.18824rem;line-height:.32941rem;white-space:pre;padding:.23529rem .29412rem;overflow-x:auto;overflow-y:hidden;border-radius:.07059rem;background-color:transparent;font-family:SourceCodePro,Microsoft YaHei;width:100%}.markdown .language-bash,.markdown .language-cpp,.markdown .language-diff,.markdown .language-dts,.markdown .language-json,.markdown .language-python,.markdown .language-shell{margin:0;font-size:.18824rem;line-height:.32941rem;white-space:pre;overflow-x:auto;overflow-y:hidden;background-color:transparent;display:block;width:100%}.markdown table thead,.markdown table tr{border-top:.01176rem solid #aabfdc}.markdown .normal-blockquote{box-shadow:-.05882rem 0 0 0 #238dfb;background-color:#fbfcfe;padding:.23529rem;margin:.17647rem 0 .17647rem .05882rem}.markdown .normal-blockquote p{font-weight:500;margin:0}.markdown .table-container{display:block;width:100%;min-width:0;max-width:100%;overflow-x:auto;overflow-y:hidden;overscroll-behavior-inline:contain;-webkit-overflow-scrolling:touch}.markdown table{border:none;display:table;min-width:100%;overflow:auto;margin:.11765rem 0 .35294rem}.markdown table thead{height:.58824rem;background:linear-gradient(-90deg,#1186de,#0064c2)}.markdown table thead tr{line-height:.58824rem;font-size:.18824rem;font-weight:700;color:#fff}.markdown table thead tr th{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr{line-height:.58824rem;font-size:.18824rem;color:#7d7d7d}.markdown table tbody tr td{padding:0 .05882rem;min-width:1.17647rem;text-align:center}.markdown table tbody tr:nth-child(odd){background-color:#fbfcfe}.markdown table tbody tr:nth-child(2n){background-color:#edf4fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table{border:.01176rem solid #e6ebf2;border-collapse:separate;border-spacing:0;border-radius:.07059rem;overflow:hidden;box-shadow:none}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead{height:auto;background:#1f6fe5}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr{border:0;line-height:1.4;font-size:.17647rem;font-weight:600;color:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table thead tr th{padding:.10588rem .17647rem;border:0;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr{border:0;line-height:1.5;color:#2c2f36}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td{padding:.10588rem .17647rem;border:0;border-right:.01176rem solid #e6ebf2;border-bottom:.01176rem solid #e6ebf2;text-align:left}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr td:last-child{border-right:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(odd){background:#fff}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:nth-child(2n){background:#f7f9fc}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:last-child td{border-bottom:0}.markdown .table-container:not(.table-download):not(.table-i2c):not(.table-selector) table tbody tr:hover{background:#eef3ff}.markdown .compare-table-container .table-container table thead{background:#fff!important}.markdown .compare-table-container .table-container table thead th{color:#2f495e;text-align:center!important;vertical-align:bottom}.markdown .compare-table-container .table-container table thead th a{align-items:center}.markdown .compare-table-container .table-container table thead th img{display:block;width:1.76471rem;height:1.76471rem;-o-object-fit:contain;object-fit:contain;margin:0 auto .35294rem}.markdown .compare-table-container .table-container table thead th:first-child{text-align:center!important;vertical-align:middle}.markdown .compare-table-container .table-container table tbody td:first-child,.markdown .compare-table-container .table-container table tbody td:not(:first-child){text-align:center!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(odd):hover{background:#fff!important}.markdown .m5-bus-table-container .table-container table tbody tr:nth-child(2n):hover{background:#f7f9fc!important}.markdown .table-text-align-left table td,.markdown .table-text-align-left table th{text-align:left}.markdown .table-text-align-right table td,.markdown .table-text-align-right table th{text-align:right}.markdown .markdown-ol li{list-style-type:decimal}.markdown .error,.markdown .tip,.markdown .warn{font-size:.21176rem;border-bottom-right-radius:.02353rem;margin:.11765rem .11765rem .11765rem 0;position:relative;background-color:#fff;box-shadow:.02353rem 0 .08235rem .01176rem #efefef;display:flex;flex-direction:column;color:#838383;font-size:.18824rem;font-weight:400;line-height:.37647rem;border-radius:.07059rem;overflow:hidden}.markdown .error .error-content,.markdown .error .tip-content,.markdown .error .warn-content,.markdown .tip .error-content,.markdown .tip .tip-content,.markdown .tip .warn-content,.markdown .warn .error-content,.markdown .warn .tip-content,.markdown .warn .warn-content{padding:.23529rem}.markdown .error .tip-title,.markdown .tip .tip-title,.markdown .warn .tip-title{height:.41176rem;background-color:rgba(35,141,251,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#238dfb}.markdown .error .warn-title,.markdown .tip .warn-title,.markdown .warn .warn-title{height:.41176rem;background-color:rgba(253,184,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#c69000}.markdown .error .error-title,.markdown .tip .error-title,.markdown .warn .error-title{height:.41176rem;background-color:rgba(253,45,2,.27843);padding-left:.58824rem;line-height:.41176rem;font-weight:700;color:#ff1616}.markdown .tip:before{background-image:url(/assets/tip.svg)}.markdown .tip:before,.markdown .warn:before{content:"";position:absolute;width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .warn:before{background-image:url(/assets/warning.svg)}.markdown .error:before{content:"";position:absolute;background-image:url(/assets/error.svg);width:.37647rem;height:.37647rem;background-size:.37647rem;top:.01176rem;left:.11765rem}.markdown .tip{border-left:.07059rem solid #238dfb}.markdown .warn{border-left:.07059rem solid #fdb802}.markdown .error{border-left:.07059rem solid rgba(253,2,2,.83922)}.markdown .learn{display:flex;grid-column:auto;width:100%;height:2.07059rem;margin:.09412rem 0;overflow:hidden;background:#fff;border:.01176rem solid #d3dde9;border-radius:.07059rem;transition:border-color .2s ease,box-shadow .2s ease,transform .2s ease}.markdown .learn:hover{border-color:#8ab4eb;box-shadow:0 .04706rem .14118rem rgba(31,111,229,.1);transform:translateY(-.01176rem)}.markdown .learn:hover .learn-contents{background:#f6f9fe}.markdown .learn .learn-img{flex:0 0 42%;min-height:0;position:relative;overflow:hidden;text-align:center;background:#f7f9fc;border-right:.01176rem solid #e6ebf2}.markdown .learn .learn-img img{display:block;width:100%;max-width:none;box-shadow:none;margin:0;height:100%;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;font-size:.09412rem}.markdown .learn .learn-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.markdown .learn .learn-contents{flex:1;min-width:0;padding:.23529rem;position:relative;display:flex;flex-direction:column;justify-content:center;background:#fbfcfe;transition:background-color .2s ease}.markdown .learn .learn-contents .learn-title{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:2;font-size:.21176rem;font-weight:600;line-height:.29412rem}.markdown .learn .learn-contents .learn-title a{color:#1f6fe5}.markdown .learn .learn-contents .learn-desc{display:-webkit-box;overflow:hidden;-webkit-box-orient:vertical;-webkit-line-clamp:3;margin-top:.09412rem;font-size:.18824rem;font-weight:400;color:#5d6673;line-height:.28235rem}.markdown .learn [\:not-has\(\%2B.learn\)]{grid-column:1/-1}.markdown .learn :not(:has(+.learn)){grid-column:1/-1}.markdown .learn [\:not-has\(\%2B.learn\)] .learn-img{flex-basis:2.82353rem}.markdown .learn :not(:has(+.learn)) .learn-img{flex-basis:2.82353rem}.mobile .markdown{grid-template-columns:minmax(0,1fr)}.mobile .markdown p{font-size:.21176rem}.mobile .markdown .learn{flex-direction:row;height:1.88235rem;max-width:none}.mobile .markdown .learn .learn-img{flex:0 0 40%;width:auto;min-height:0;aspect-ratio:auto;border-right:.01176rem solid #e6ebf2;border-bottom:0}.mobile .markdown .learn .learn-contents{padding:.14118rem .16471rem}.mobile .markdown .learn .learn-contents .learn-title{font-size:.18824rem;line-height:.25882rem;-webkit-line-clamp:2}.mobile .markdown .learn .learn-contents .learn-desc{margin-top:.07059rem;font-size:.16471rem;line-height:.24706rem;-webkit-line-clamp:3}@media screen and (max-width:900px){.markdown{grid-template-columns:minmax(0,1fr)}.markdown .learn .learn-img{flex-basis:2.82353rem}}.mobile video{width:100%;margin-bottom:.35294rem}.mobile .video-iframe{margin:.23529rem 0;height:5.88235rem}.mobile .video-iframe iframe{width:100%;height:100%}.easyloader-box{display:flex;flex-direction:row;width:100%}.easyloader-box>div{position:relative;width:50%;overflow:hidden}.easyloader-box p{margin:.11765rem .29412rem;color:#fff}.easyloader-box p:last-child{overflow-y:scroll;height:20%;font-size:.11765rem}.easyloader-mask{position:absolute;right:0;bottom:.07059rem;height:100%;width:100%;background-color:#000;opacity:.7;transition:all .3s;display:flex;flex-direction:column;justify-content:center;display:none}.easyloader-mask a{margin-top:.58824rem;text-align:center}.video_play{bottom:-100%}.easyloader-btn{position:absolute;display:flex;flex-direction:row;justify-content:space-around;bottom:7%;width:100%;padding:0 .23529rem;font-size:.23529rem}.easyloader-btn a{width:1.05882rem;text-align:center;padding:.02353rem .11765rem;background-color:#007bff;color:#fff!important;border-radius:.11765rem;font-size:.17647rem}.easyloader-btn a:hover{background-color:#45a9ff}@media screen and (max-width:768px){.easyloader-box{flex-direction:column;width:100%}.easyloader-box>div{width:100%}}.code-block-wrapper{display:flex;flex-direction:column;position:relative;margin:.16471rem 0 .23529rem;border:.01176rem solid #dfe5ec;border-radius:.07059rem;overflow:hidden;background:#f7f9fb}.code-block-header{display:flex;justify-content:space-between;align-items:center;min-height:.44706rem;padding:.04706rem .14118rem;background:#f0f3f6;border-bottom:.01176rem solid #dfe5ec}.code-block-header .language-label{font-size:.15294rem;color:#526579;font-weight:500}.copy-all-btn{display:flex;align-items:center;grid-gap:.11765rem;gap:.11765rem;justify-content:center;background:0 0;border:none;border-radius:.05882rem;padding:.07059rem;font-size:.16471rem;cursor:pointer;transition:all .2s;width:.37647rem;height:.37647rem;color:#526579}.copy-all-btn svg{width:100%;height:100%}.copy-all-btn code{display:none}.copy-all-btn:hover{color:#1769aa;background:#e4ebf2}.copy-all-btn.focus-visible,.copy-all-btn:focus-visible{color:#1769aa;background:#e4ebf2;outline:.02353rem solid #1769aa;outline-offset:.02353rem}.code-block-container{display:flex;overflow:auto;background:#f7f9fb;align-items:flex-start}.code-block-wrapper.code-block-limited .code-block-container,.code-block-wrapper.code-block-limited .code-line-container{max-height:560px;max-height:var(--code-max-height,560px);overflow:auto;transition:max-height .35s ease}.code-block-wrapper:not(.is-collapsed).code-block-limited .code-block-container,.code-block-wrapper:not(.is-collapsed).code-block-limited .code-line-container{max-height:16.47059rem}.code-toggle-btn{display:flex;align-items:center;justify-content:center;width:100%;min-height:.49412rem;padding:.09412rem .14118rem .11765rem;border:0;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(240,244,249,.96));color:#6b7f93;cursor:pointer;transition:background .2s ease,color .2s ease;position:relative;z-index:2}.code-toggle-btn.focus-visible,.code-toggle-btn:focus-visible,.code-toggle-btn:hover{outline:0;color:#2d7be9;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(228,238,248,.98))}.code-toggle-icon{font-size:.17647rem;line-height:1;transition:transform .25s ease,color .2s ease}.code-block-wrapper:not(.is-collapsed) .code-toggle-icon,.code-toggle-icon{transform:translateY(-.01176rem)}.code-block-fade{position:absolute;left:0;right:0;bottom:.49412rem;height:1.29412rem;background:linear-gradient(180deg,rgba(247,249,251,0),rgba(247,249,251,.96));pointer-events:none;transition:opacity .2s ease;z-index:1}.code-block-wrapper.is-collapsed .code-block-fade{opacity:1}.code-block-wrapper:not(.is-collapsed) .code-block-fade{opacity:0}.markdown .code-block-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-block-container code.hljs{margin:0!important;padding:0!important;border-radius:0;background:0 0;line-height:.32941rem;font-size:.18824rem;white-space:pre}.markdown .code-line-container pre{margin:0;padding:0;line-height:.32941rem;background:0 0}.markdown .code-line-container code.hljs{margin:0!important;padding:0!important;line-height:.32941rem;font-size:.18824rem;white-space:pre;width:100%;border-radius:0;background-color:transparent}.code-line-container{display:flex;background:#f7f9fb;align-items:center;position:relative;padding:.18824rem .21176rem}.code-line-container .copy-all-btn{opacity:.45;position:absolute;top:.11765rem;right:.11765rem;transition:all .2s}.code-line-container pre{overflow-x:auto}.code-line-container:hover .copy-all-btn,.code-line-container[focus-within] .copy-all-btn{opacity:1}.code-line-container:focus-within .copy-all-btn,.code-line-container:hover .copy-all-btn{opacity:1}@media (hover:none){.code-line-container .copy-all-btn{opacity:1}.markdown .learn:hover{border-color:#d3dde9;box-shadow:none;transform:none}.markdown .learn:hover .learn-contents{background:#fbfcfe}}.line-numbers{padding:.11765rem .09412rem;text-align:right;background:#f3f6f9;color:#8491a0;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;border-right:.01176rem solid #dfe5ec;font-family:SourceCodePro,Microsoft YaHei,sans-serif;line-height:.32941rem;min-width:.51765rem}.line-number{display:block;height:.32941rem}.code-content{flex:1;overflow:auto;padding:.11765rem .17647rem;line-height:.32941rem}.code-block-container,.code-content,.code-line-container pre{scrollbar-color:#c5cfda transparent;scrollbar-width:thin}.code-block-container::-webkit-scrollbar,.code-content::-webkit-scrollbar,.code-line-container pre::-webkit-scrollbar{width:.09412rem;height:.09412rem}.code-block-container::-webkit-scrollbar-thumb,.code-content::-webkit-scrollbar-thumb,.code-line-container pre::-webkit-scrollbar-thumb{background:#c5cfda;border-radius:.04706rem}.code-block-container::-webkit-scrollbar-track,.code-content::-webkit-scrollbar-track,.code-line-container pre::-webkit-scrollbar-track{background:0 0}.code-line{display:block;min-height:.32941rem;line-height:.32941rem;white-space:pre;font-weight:700;font-family:SourceCodePro,Microsoft YaHei,sans-serif}.code-line:hover{background-color:#eaf1f7;cursor:pointer}pre code{font-weight:400;font-family:SourceCodePro,Microsoft YaHei,sans-serif;font-size:.18824rem;overflow-y:auto;font-family:SourceCodePro;display:block;width:100%;color:#263445;line-height:.32941rem}code.hljs{background:0 0}pre{position:relative}pre .copy-btn{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;opacity:0;position:absolute;right:.05882rem;top:.05882rem;cursor:pointer;padding:.05882rem;border-radius:.03529rem;transition:.3s;background:hsla(0,0%,100%,.2);width:1.52941rem;height:.58824rem;color:#0064c2}pre .copy-btn:active{background:hsla(0,0%,99.2%,.575)}pre .copy-btn .icon{width:.35294rem;position:absolute;left:70%;top:70%;transform:translate(-50%,-50%)}pre .copy-success-text{color:#fff;position:absolute;font-size:.14118rem;top:.70588rem;font-weight:200;font-family:SourceCodePro,Microsoft YaHei;-webkit-animation:successCopy .5s ease 1 both;animation:successCopy .5s ease 1 both;color:#0064c2}@-webkit-keyframes successCopy{0%{right:0}to{right:.29412rem}}@keyframes successCopy{0%{right:0}to{right:.29412rem}}pre:hover .copy-btn{opacity:1}.files_download{display:flex;flex-direction:row;justify-content:space-evenly;flex-wrap:wrap;margin:.52941rem}.files_download .item{display:flex;justify-content:center;width:2.35294rem;box-shadow:.04706rem .04706rem .08235rem 0 #cecece;transition:all .25s ease}.files_download .item:hover{transform:scale(1.2)}.card-container{display:flex;justify-content:flex-start;margin-bottom:.35294rem;align-items:flex-start}.card-container .card-item{margin:.23529rem;width:3.52941rem;display:flex;flex-direction:column;justify-content:center;align-items:center;color:#fff;transition:all .25s ease}.card-container .card-item .card-cover{height:1.76471rem;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1)}.card-container .card-item .card-cover,.card-container .card-item .card-cover-img{width:100%;display:flex;align-items:center;justify-content:center;font-size:.28235rem;font-weight:700;margin-bottom:.11765rem;border-radius:.11765rem}.card-container .card-item .card-cover-img{position:relative}.card-container .card-item .card-cover-img .card-cover-content{display:none;padding:.11765rem}.card-container .card-item .card-cover-img .card-cover-content .card-cover-btn{display:block;text-align:center;background-color:#0064c2;color:#fff;font-size:.2rem;padding:.11765rem .17647rem;border-radius:.04706rem}.card-container .card-item .card-cover-img img{width:100%;box-shadow:none;margin:0}.card-container .card-item .card-cover-img:hover .card-cover-content{display:flex;flex-direction:column;justify-content:space-around;align-items:center;position:absolute;top:0;left:0;bottom:0;right:0;background-color:rgba(0,0,0,.5098)}.card-container .card-item .card-desc{padding:.17647rem;text-align:center;font-size:.17647rem;color:#2f495e}.card-container .card-item .card-desc a{display:block;text-align:left;color:#333;line-height:.23529rem}.card-container .card-item .card-desc a:hover{text-decoration:underline;color:#238dfb}.card-container .card-item:hover{transform:translateY(-.05882rem)}.card-container .linear-blue{background:linear-gradient(45deg,#09f,#6cf)}.card-container .linear-gray{background:linear-gradient(45deg,#f2f2f2,#ccc);color:#333}.card-container .linear-orange{background:linear-gradient(45deg,#fc0,#f90)}.card-container-video{display:flex;flex-wrap:wrap;grid-gap:.23529rem;gap:.23529rem;margin:.47059rem 0}.card-container-video li{list-style-type:none}.card-container-video .card-item-video{width:22%;position:relative;border-radius:.07059rem;overflow:hidden;transition:transform .3s ease;box-shadow:0 .04706rem .09412rem rgba(0,0,0,.1);background-color:#fff}.card-container-video .card-item-video:hover{transform:translateY(-.05882rem);box-shadow:0 .09412rem .18824rem rgba(0,0,0,.15)}.card-container-video .card-item-video:hover .card-cover-content{opacity:1}.card-container-video .card-item-video .card-cover-img{position:relative;width:100%;padding-top:56.25%;background-color:#e7e7e7;overflow:hidden}.card-container-video .card-item-video .card-cover-img img{position:absolute;top:50%;left:50%;width:100%;height:100%;-o-object-fit:cover;object-fit:cover;transform:translate(-50%,-50%);min-width:100%;min-height:100%;transition:transform .3s ease;margin:0}.card-container-video .card-item-video .card-desc-video{padding:.11765rem;text-align:center;font-weight:700}.card-container-video .card-item-video .card-cover-content{position:absolute;top:0;left:0;width:100%;height:100%;display:flex;justify-content:center;align-items:center;background-color:rgba(0,0,0,.5);opacity:0;transition:opacity .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn{display:inline-block;padding:.09412rem .18824rem;margin:0 .11765rem;background-color:#fb7299;color:#fff;border-radius:.04706rem;text-decoration:none;font-size:.16471rem;transition:background-color .3s ease}.card-container-video .card-item-video .card-cover-content .card-cover-btn.youtube{background-color:#f03}.card-container-video .card-item-video .card-cover-content .card-cover-btn.bilibili{background-color:#ff85ad}.mobile .card-item-video{width:40%}.mobile .card-desc-video{font-size:.29412rem}.directory-links-container{display:flex;flex-direction:column}.directory-links-item{page-break-inside:avoid;-moz-column-break-inside:avoid;break-inside:avoid;margin:.11765rem;padding:.17647rem;border-radius:.05882rem;box-shadow:0 0 .05882rem rgba(0,0,0,.1)}.directory-links-body{display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(3.52941rem,1fr));position:relative}.directory-links-item h3{margin-top:0;margin-bottom:.11765rem}.directory-links-item ul{list-style-type:none;padding:0;margin:.18824rem .11765rem}.directory-links-item ul li{margin-bottom:.05882rem}.directory-links-item ul li a{text-decoration:none;color:#333}.directory-links-item ul li a:hover{text-decoration:underline;color:#238dfb}.header-nav .dropdown-icon-wrapper,.pc .nav-dropdown .dropdown-content-right,.pc .nav-dropdown .dropdown-image .image-button{display:flex;justify-content:center;align-items:center}.pc .header-nav-ul .header-nav-item a:hover{color:#0064c2}.mobile .mobile-nav-icon,.mobile .mobile-return-icon{background-repeat:no-repeat;background-size:100% 100%}header{width:100%;position:relative;background-color:#fff;border-bottom:.01176rem solid #e5e5e5;overflow:visible}.header-container{position:relative;margin:0 auto;padding:0 1.17647rem 0 0;width:15.64706rem;height:.70588rem;display:flex;align-items:center;justify-content:flex-end;font-size:.25882rem}.header-container .logo{position:absolute;left:.08235rem;display:block;width:2.08235rem;height:.41176rem;font-size:0;line-height:1;cursor:pointer}.header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.header-nav .dropdown-icon-wrapper{margin-right:.18824rem;width:.25882rem;height:.25882rem}.header-nav .dropdown-icon-wrapper .dropdown-icon{width:auto;height:auto;max-width:100%;max-height:100%;font-size:0}.language-option-box{position:absolute;height:.70588rem;right:-.65882rem;font-size:0;background-color:#fff}.language-option-box .icon{margin-right:.07059rem;width:.2rem;height:auto;color:#434343}.language-option-box .current-language{height:calc(100% - .02353rem);color:#434343;font-size:.22353rem;font-weight:700;display:flex;align-items:center;cursor:pointer;box-sizing:content-box}.language-option-box .language-dropdown-wrapper{display:none;position:fixed;top:.70588rem;padding-top:.11765rem;box-sizing:border-box;width:19.76471rem;left:50%;transform:translateX(-50%);z-index:99999}.language-option-box .language-dropdown-wrapper .language-dropdown{position:absolute;top:.11765rem;right:1.29412rem;width:1.52941rem;color:#434343;background-color:#fff;border-radius:.11765rem;overflow:hidden;box-shadow:0 .09412rem .28235rem rgba(0,0,0,.08);opacity:0;transition:opacity .2s ease}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item{font-size:.21176rem;font-weight:700;line-height:.54118rem;text-align:center;cursor:pointer}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item:hover{color:#0064c2}.language-option-box .language-dropdown-wrapper .language-dropdown .language-item.active{background-color:#dedede}.language-option-box:hover .current-language{border-bottom:.03529rem solid #0064c2}.language-option-box:hover .current-language .header-arrow-btn{transform:rotate(-180deg)}.language-option-box:hover .language-dropdown-wrapper{display:block}.language-option-box:hover .language-dropdown{opacity:1}.disabledHover{cursor:auto!important}.disabledHover a:hover,.disabledHover li:hover,.disabledHover:hover{color:#434343!important}.pc .show-mb{display:none}.pc .header-nav{height:100%;display:flex;align-items:center}.pc .header-nav-ul{height:100%;display:flex;flex-direction:row}.pc .header-nav-ul .header-nav-item{margin-right:.30588rem;padding-left:.23529rem;height:calc(100% - .02353rem);display:flex;align-items:center;font-size:.22353rem;font-weight:700;color:#434343;cursor:pointer;box-sizing:content-box}.pc .header-nav-ul .header-nav-item.active,.pc .header-nav-ul .header-nav-item:hover{border-bottom:.03529rem solid #0064c2}.pc .header-nav-ul .header-nav-item.active .header-arrow-btn,.pc .header-nav-ul .header-nav-item:hover .header-arrow-btn{transform:rotate(-180deg)}.pc .header-nav-ul .header-nav-item:last-of-type{margin-right:0}.pc .header-nav-ul .header-nav-item a{position:relative;color:#434343}.pc .header-arrow-btn{margin-left:.07059rem;width:.11765rem;height:auto;color:#3a3a3a;font-size:0;transition:all .3s ease}.pc .nav-dropdown{position:fixed;left:50%;width:16.70588rem;max-width:calc(100vw - .47059rem);height:3.52941rem;display:flex;transform:translateX(-50%);background-color:#fff;border-radius:.23529rem;z-index:9999}.pc .nav-dropdown .dropdown-content-left{position:relative;padding:.47059rem .32941rem 0;width:calc(100% - 7.45882rem);height:100%;display:flex;justify-content:space-around}.pc .nav-dropdown .dropdown-content-right{width:7.45882rem;height:100%;background-color:#eee;border-radius:0 .23529rem .23529rem 0}.pc .nav-dropdown .dropdown-image{position:relative;width:7.05882rem;border-radius:.23529rem;font-size:0;overflow:hidden}.pc .nav-dropdown .dropdown-image img{width:100%;height:auto}.pc .nav-dropdown .dropdown-image .image-button{position:absolute;left:50%;bottom:.35294rem;transform:translateX(-50%);width:2.35294rem;height:.42353rem;font-size:.18824rem;color:#fff;background-color:#0064c2;border-radius:.04706rem}.pc .nav-dropdown .dropdown-image .image-button:hover{background-color:#058ce6}.pc .nav-dropdown .dropdown-image .image-button .image-icon{margin-right:.11765rem;width:.24706rem;height:auto}.pc .nav-dropdown .dropdown-item{width:3.29412rem;display:flex;flex-direction:column;flex-wrap:wrap}.pc .nav-dropdown .dropdown-item-li{padding-left:.16471rem;display:flex;align-items:center;font-size:.23529rem;font-weight:700;line-height:.70588rem;color:#434343}.pc .nav-dropdown .dropdown-item-li.border{border-bottom:.02353rem solid #dbdbdb}.pc .nav-dropdown .dropdown-item-li:hover{color:#0064c2}.pc .nav-dropdown .dropdown-item-child{margin-top:.18824rem;padding-left:.18824rem;display:flex;flex-direction:column}.pc .nav-dropdown .dropdown-child-li{margin-bottom:.14118rem;display:flex;align-items:center;font-size:.21176rem;font-weight:500;white-space:nowrap;color:#434343}.pc .nav-dropdown .dropdown-child-li:hover{color:#0064c2}.pc header #store{height:4.70588rem}.pc header #store .dropdown-item:first-child{width:2.21176rem}.pc header #store .dropdown-item:first-child .dropdown-child-li:nth-child(2) .dropdown-icon-wrapper{height:.32941rem}.pc header #store .dropdown-item:nth-child(2){width:4.65882rem;height:3.05882rem;border-bottom:.02353rem solid #dbdbdb}.pc header #store .dropdown-item:nth-child(2) .dropdown-item-child{width:90%;height:2rem;flex-wrap:wrap}.pc header #store .dropdown-item:nth-child(3),.pc header #store .dropdown-item:nth-child(4){position:absolute;bottom:.47059rem}.pc header #store .dropdown-item:nth-child(3){right:3.38824rem;width:2.04706rem}.pc header #store .dropdown-item:nth-child(3) .dropdown-icon-wrapper{margin-right:.14118rem;width:.32941rem}.pc header #store .dropdown-item:nth-child(4){right:.75294rem;width:2.58824rem}.pc header #software{height:4rem}.pc header #software .dropdown-content-left{width:calc(100% - 6.03529rem)}.pc header #software .dropdown-content-right{width:6.03529rem}.pc header #software .dropdown-image{width:5.58824rem}.pc header #software .dropdown-item:first-child{width:3.17647rem}.pc header #software .dropdown-item:nth-child(2){width:2.82353rem}.pc header #software .dropdown-item:nth-child(3){width:2.91765rem}.pc header #document{height:4.47059rem}.pc header #document .dropdown-content-left{width:100%}.pc header #document .dropdown-item:first-child .dropdown-item-child,.pc header #document .dropdown-item:nth-child(2) .dropdown-item-child{height:2rem;flex-wrap:wrap}.pc header #document .dropdown-item:first-child{width:4.65882rem}.pc header #document .dropdown-item:nth-child(2){width:5.01176rem}.pc header #document .dropdown-item:nth-child(3){width:3.76471rem}.pc header #aboutus{height:4.21176rem}.pc header #contact{height:1.05882rem;background-color:transparent}.pc header #contact .dropdown-content-left{position:absolute;padding:.09412rem 0;right:1.29412rem;width:2rem;height:1.05882rem;flex-direction:column;background-color:#fff;border-radius:.11765rem}.pc header #contact .dropdown-item{width:100%}.pc header #contact .dropdown-item .dropdown-item-li{padding-left:0;width:100%;justify-content:center;font-size:.21176rem;line-height:.42353rem}.mobile .show-pc,.mobile .snize-sticky-searchbox{display:none}.mobile header{height:1.10588rem;border-bottom:unset}.mobile .header-container{padding:0 .35294rem;width:100%;max-width:100%;height:1.10588rem;justify-content:unset;z-index:9999;box-shadow:0 0 .18824rem 0 hsla(0,0%,51.4%,.15)}.mobile .header-container .logo img{width:100%;height:100%;-o-object-fit:contain;object-fit:contain}.mobile .mobile-nav-icon{width:.54118rem;height:.54118rem;background-image:url(/assets/menu.png);transition:all .28s ease}.mobile .mobile-nav-icon.active{transform:rotate(90deg)}.mobile .mobile-return-icon{position:absolute;left:1.2rem;width:.32941rem;height:.32941rem;background-image:url(/assets/return.png)}.mobile .logo{left:50%;width:2.47059rem;height:.48235rem;transform:translateX(-50%)}.mobile .header-nav{display:none;position:absolute;top:1.10588rem;left:0;padding:.18824rem 0 1.01176rem;width:5.17647rem;max-width:100%;background-color:#fff;z-index:9998}.mobile .header-nav.show{display:block}.mobile .header-nav-ul{margin-bottom:.23529rem}.mobile .header-nav-ul .header-nav-item{position:relative;padding-left:.47059rem;height:1.10588rem;font-size:.36471rem;font-weight:400;line-height:1.10588rem}.mobile .header-nav-ul .header-nav-item,.mobile .header-nav-ul .header-nav-item a{color:#434343}.mobile .header-nav-ul .header-nav-item.selected{background-color:#f7f7f7}.mobile .header-nav-ul .header-nav-item.active .header-mbnav-btn{transform:rotate(90deg)}.mobile .header-nav-ul .header-nav-item.active+.nav-dropdown{display:block}.mobile .header-mbnav-btn{position:absolute;width:.58824rem;height:.58824rem;top:.23529rem;right:.23529rem;background-image:url(/assets/arrow3.png);background-repeat:no-repeat;background-size:50% 50%;background-position:50%}.mobile .nav-dropdown{display:none;position:relative}.mobile .nav-dropdown .dropdown-content-left{width:100%}.mobile .nav-dropdown .dropdown-icon-wrapper{width:.47059rem;height:.47059rem}.mobile .nav-dropdown .dropdown-item-li{padding-left:.71765rem;width:100%;height:.88235rem;display:flex;align-items:center;font-size:.32941rem;font-weight:400;color:#434343}.mobile .nav-dropdown .dropdown-child-li{padding-left:.89412rem;width:100%;height:.82353rem;display:flex;align-items:center;font-size:.30588rem;line-height:.82353rem;white-space:nowrap;color:#434343}.mobile .language-option-box{height:1.10588rem;right:.25882rem}.mobile .language-option-box .icon{width:.35294rem}.mobile .language-option-box .current-language{font-size:.30588rem;font-weight:500}.mobile .language-option-box .language-dropdown-wrapper{width:100%;top:1.10588rem;padding-top:.11765rem;box-sizing:border-box}.mobile .language-option-box .language-dropdown{right:.11765rem;width:2.23529rem}.mobile .language-option-box .language-dropdown .language-item{font-size:.35294rem;font-weight:500;line-height:.70588rem}.header-nav-dd-pc-enter-active,.header-nav-dd-pc-leave-active{transition:opacity .2s ease-out,transform .22s cubic-bezier(.4,0,.2,1)}.header-nav-dd-pc-enter,.header-nav-dd-pc-leave-to{opacity:0;transform:translateX(-50%) translateY(-.09412rem)!important}.header-nav-dd-pc-enter-to,.header-nav-dd-pc-leave{opacity:1;transform:translateX(-50%) translateY(0)!important}.header-nav-dd-mb-enter-active,.header-nav-dd-mb-leave-active{transition:opacity .18s ease-out}.header-nav-dd-mb-enter,.header-nav-dd-mb-leave-to{opacity:0}.viewer-open .mobile .header-container,.viewer-open .mobile .language-dropdown-wrapper,.viewer-open .mobile .language-option-box{z-index:1!important}.viewer-open .mobile .language-option-box{pointer-events:none}.title-level2{height:.32941rem;font-size:.35294rem;font-weight:400;color:#434343;line-height:.32941rem;padding-left:.22353rem;position:relative;display:flex;justify-content:space-between;margin:.58824rem 0}.title-level2 .title-level2-desc{font-size:.18824rem;font-weight:400}.title-level2:after{content:"";width:.04706rem;height:.35294rem;background:#0064c2;position:absolute;left:0}.title-level3{height:.27059rem;font-size:.29412rem;font-weight:400;color:#434343;line-height:.27059rem;padding-left:.14118rem;position:relative;display:flex;justify-content:space-between;margin:.47059rem 0 .35294rem}.title-level3 .title-level3-desc{font-size:.14118rem;font-weight:400}.pc .product-list-container .Products{display:flex;flex-wrap:wrap;margin-bottom:.70588rem}.pc .product-list-container .ProductItem{border-top:.01176rem solid #e5e5e5;border-bottom:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(2n),.pc .product-list-container .ProductItem:nth-child(2n-1){border-right:.01176rem solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(3n){border-right:0 solid #e5e5e5}.pc .product-list-container .ProductItem:nth-child(n+4){border-top:0 solid #e5e5e5}.pc .product-list-container .ProductItem{height:4.51765rem;width:4.65882rem;text-align:center;position:relative}.pc .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.pc .product-list-container .ProductItem .ProductPic{text-align:center;width:2.35294rem;height:2.35294rem}.pc .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.pc .product-list-container .ProductItem .ProductName{margin-top:.11765rem;line-height:.29412rem;height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343}.pc .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto .17647rem;width:2.47059rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.23529rem;text-overflow:clip;overflow:hidden}.pc .product-list-container .ProductItem .product-btn-group{width:1.76471rem;height:.35294rem;border-radius:.17647rem;margin:auto;display:flex}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.29412rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.35294rem;font-size:.18824rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.pc .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.47059rem;height:.35294rem;background-size:.23529rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.pc .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.pc .product-list-container .ProductLinks{padding:0 .17647rem;font-size:.18824rem;display:grid;justify-content:start;grid-auto-flow:dense;grid-template-columns:repeat(auto-fill,minmax(2.82353rem,1fr));position:relative;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.11765rem}.pc .product-list-container .ProductLinks .ProductLink:hover{color:#409eff;-webkit-text-decoration-line:underline;text-decoration-line:underline}.mobile .product-list-container{text-align:left}.mobile .product-list-container .ProductItem{text-align:center;height:5.17647rem;width:50%;border:.02353rem solid #e5e5e5;background-color:#fff;position:relative}.mobile .product-list-container .ProductItem .product-main-link{display:block;color:inherit;text-decoration:none}.mobile .product-list-container .ProductItem .ProductPic{margin:.11765rem auto;text-align:center;width:2.82353rem;height:2.82353rem}.mobile .product-list-container .ProductItem .ProductEolTag{position:absolute;width:.47059rem;height:.47059rem;border-radius:50%;top:5%;right:25%;background-color:#2f495e;color:#fff;font-size:.21176rem;font-weight:700;line-height:.47059rem}.mobile .product-list-container .ProductItem .ProductName{height:.58824rem;font-size:.25882rem;font-weight:400;color:#434343;line-height:.28235rem}.mobile .product-list-container .ProductItem .ProductDesc{margin:.11765rem auto;display:block;width:2.36471rem;height:.47059rem;font-size:.16471rem;font-weight:400;color:#959595;line-height:.25882rem;overflow:hidden}.mobile .product-list-container .ProductItem .product-btn-group{width:2.35294rem;height:.47059rem;border-radius:.17647rem;margin:auto;display:flex}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view{width:1.64706rem;background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:.17647rem 0 0 .17647rem;line-height:.47059rem;font-size:.23529rem;font-weight:400;color:#fff;position:relative;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:hover{background-color:#fff;color:#0064c2}.mobile .product-list-container .ProductItem .product-btn-group .product-btn-view:after{content:" ";width:.01176rem;height:.23529rem;background:#fff;opacity:.3;position:absolute;right:-.02353rem;top:50%;transform:translateY(-50%)}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop{padding:.05882rem .11765rem;width:.70588rem;height:.47059rem;background-size:.29412rem;background-position:50%;background-repeat:no-repeat;background-image:url(/assets/cart-w.png);background-color:#0064c2;border:.01176rem solid #0064c2;border-radius:0 .17647rem .17647rem 0;transition:all .25s ease}.mobile .product-list-container .ProductItem .product-btn-group .product-icon-shop:hover{background-image:url(/assets/cart-b.png);background-color:#fff}.mobile .product-list-container .ProductLinks{padding:.11765rem .17647rem;font-size:.25882rem;display:grid;grid-auto-flow:dense;grid-template-columns:repeat(auto-fit,minmax(3.52941rem,1fr));position:relative;margin-bottom:.14118rem;background-color:#fff}.mobile .product-list-container .ProductLinks .ProductLink{color:#333;margin-bottom:.14118rem}.product-list-container.hideEol .ProductItem.EOL{display:none}.footer-email-input input::-webkit-input-placeholder{font-family:Microsoft YaHei,sans-serif}.subscribe-btn{display:flex;justify-content:center;align-items:center}.pc .footer-bottom-content a:hover,.pc .footer-nav-li a:hover{color:#0064c2}.subscribe-btn:hover{background-color:#0074e1}.mobile .footer-nav-btn{background-repeat:no-repeat;background-size:100% 100%}.footer-container{width:100%;color:#fff;background-color:#000}.footer-content-wrap{height:100%;display:flex;align-items:center}.footer-email-title,.footer-qrcode-title{font-size:.32941rem;margin-bottom:.21176rem;font-weight:500;color:#fff}.footer-email-desc{font-weight:400;color:#f1f1f1}.footer-email-input{display:flex}.footer-email-input input{background:hsla(0,0%,60%,.55);border:.01176rem solid #0077c8;border-radius:.04706rem;padding:0 .23529rem;color:#fff;outline:0}.footer-email-input input::-webkit-input-placeholder{font-weight:400;color:#a0a0a0}.subscribe-btn{background:#0077c8;width:1.55294rem;height:.56471rem;font-size:.21176rem;font-weight:500;color:#fff;border-radius:.07059rem}.footer-follow{margin-top:.42353rem;width:90%}.footer-follow-ul{display:flex;flex-wrap:wrap}.footer-info-wrapper{margin-top:.47059rem;font-size:.16471rem;color:#a0a0a0}.footer-email-warning{margin-top:.11765rem;display:none;font-size:.18824rem;color:#ff2529}.footer-email-success{margin-top:.35294rem;margin-bottom:1.15294rem;display:none;font-size:.35294rem;color:#fff}.pc .footer-container{height:8.23529rem}.pc .footer-content-wrap{width:15.64706rem;margin:0 auto}.pc .footer-nav{padding:.70588rem 0 .11765rem;width:65%;height:100%;display:flex;flex-direction:column;flex-wrap:wrap}.pc .footer-nav-item{margin:0 0 .47059rem}.pc .footer-nav-title{margin-bottom:.18824rem;font-size:.29412rem;font-weight:500;color:#fff}.pc .footer-nav-title a{color:#fff}.pc .footer-nav-li{font-size:.21176rem;font-weight:400;color:#a0a0a0;line-height:.38824rem}.pc .footer-nav-li a{color:#a0a0a0;cursor:pointer}.pc .footer-right{width:35%;height:5.95294rem;padding:0 0 0 .47059rem}.pc .footer-email-title,.pc .footer-qrcode-title{margin-top:.14118rem}.pc .footer-email-desc{font-size:.21176rem;line-height:.32941rem;margin-bottom:.14118rem}.pc .footer-email-input input{width:3.71765rem;height:.56471rem;font-size:.21176rem;margin-right:.12941rem}.pc .footer-email-input input::-webkit-input-placeholder{font-size:.21176rem}.pc .footer-qrcode-list{display:flex}.pc .footer-qrcode-list .footer-qrcode-item{margin-right:.11765rem}.pc .footer-qrcode-list .footer-qrcode-img{width:1.88235rem;height:auto}.pc .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.pc .footer-qrcode-list .footer-qrcode-name{font-size:.21176rem;color:#a0a0a0}.pc .footer-follow-ul{width:100%}.pc .footer-follow-ul a{display:block;margin-right:.11765rem;margin-bottom:.11765rem;font-size:0}.pc .footer-follow-ul img{width:.58824rem;height:.58824rem}.pc .footer-address-info{line-height:.23529rem;margin:.05882rem 0}.pc .footer-info{line-height:.32941rem}.pc .footer-bottom{width:100%;height:.77647rem;background-color:#000}.pc .footer-bottom-content{margin:0 auto;padding:.23529rem .23529rem 0;width:16.07059rem;height:100%;display:flex;justify-content:space-between;font-size:.15294rem;font-weight:400;color:#a0a0a0;border-top:.01176rem solid #6d6d6d}.pc .footer-bottom-content a{display:inline-block;color:#a0a0a0;font-weight:400;font-size:.15294rem}.pc .terms-box{margin-left:.54118rem;display:flex}.pc .terms-box a{margin:0 .09412rem}.mobile .footer-container{height:11.76471rem}.mobile .footer-right{padding:0;width:100%}.mobile .footer-email-group,.mobile .footer-right{display:flex;flex-direction:column;align-items:center}.mobile .footer-email-title,.mobile .footer-qrcode-title{font-size:.58824rem;margin-bottom:.25882rem}.mobile .footer-email-success{font-size:.51765rem;margin-top:1.17647rem;margin-bottom:1.27059rem}.mobile .footer-email-desc{width:5.52941rem;font-size:.35294rem;line-height:.47059rem;text-align:center;margin-bottom:.75294rem}.mobile .footer-email-input{flex-direction:column;align-items:center}.mobile .footer-email-input input{width:7.35294rem;height:.70588rem;margin-bottom:.47059rem;font-size:.32941rem}.mobile .footer-email-input input::-webkit-input-placeholder{font-size:.32941rem}.mobile .subscribe-btn{width:2.75294rem;height:.70588rem;border-radius:.07059rem;font-size:.32941rem}.mobile .footer-email-warning{font-size:.29412rem;margin-top:.18824rem}.mobile .footer-qrcode-title{text-align:center}.mobile .footer-qrcode-list{display:flex}.mobile .footer-qrcode-list .footer-qrcode-item{margin-right:.35294rem}.mobile .footer-qrcode-list .footer-qrcode-img{width:3.05882rem;height:auto}.mobile .footer-qrcode-list .footer-qrcode-img img{width:100%;height:auto}.mobile .footer-qrcode-list .footer-qrcode-name{margin-top:.11765rem;font-size:.35294rem;color:#a0a0a0;text-align:center}.mobile .footer-follow{margin-top:.82353rem;width:100%}.mobile .footer-follow-ul{width:80%;margin:0 auto;justify-content:center}.mobile .footer-follow-ul a{margin-right:.23529rem}.mobile .footer-follow-ul a:nth-child(5){margin-right:0}.mobile .footer-follow-ul img{width:1.05882rem;height:1.05882rem}.mobile .footer-qrcode-img{width:2.82353rem;height:2.82353rem;margin:0 auto}.mobile .footer-qrcode-img img{width:100%;height:auto;max-height:100%}.mobile .footer-info-wrapper{width:95%;margin-top:.47059rem;font-size:.23529rem;text-align:center}.mobile .footer-address-info{line-height:.35294rem;margin:.05882rem 0}.mobile .footer-info{line-height:.44706rem}.mobile .footer-bottom{display:none}.mobile .footer-nav{background-color:#fff;border-top:.03529rem solid #eee}.mobile .footer-nav-item:nth-child(3) .footer-nav-title a{display:block}.mobile .footer-nav-title{position:relative;padding:0 0 0 .71765rem;font-size:.36471rem;line-height:1.10588rem;font-weight:500;color:#a6a6a6;height:1.10588rem;border-bottom:.03529rem solid #eee}.mobile .footer-nav-title a{color:#a6a6a6}.mobile .footer-nav-title.active .footer-nav-btn{transform:rotate(90deg)}.mobile .footer-nav-title.active+.footer-nav-ul{display:block}.mobile .footer-nav-btn{position:absolute;width:.2rem;height:.36471rem;top:.35294rem;right:.41176rem;background-image:url(/assets/arrow2.png)}.mobile .footer-nav-ul{display:none;border-bottom:.03529rem solid #eee}.mobile .footer-nav-li{font-size:.25882rem;font-weight:400;color:#a0a0a0;line-height:.65882rem;padding:0 0 0 .91765rem}.mobile .footer-nav-li a{color:#a0a0a0}.product-demo-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(2rem,1fr));grid-gap:.16471rem;gap:.16471rem;margin:.21176rem 0 .32941rem}.product-demo-item{display:flex;flex-direction:column;align-items:center;justify-content:flex-start;text-decoration:none;color:#1f2937;background:#fff;border:.01176rem solid #e5e7eb;border-radius:.14118rem;overflow:hidden;transition:transform .2s ease,border-color .2s ease;height:100%}.product-demo-item:hover{transform:translateY(-.03529rem);border-color:#93c5fd}.product-demo-item img{width:100%;height:1.41176rem;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center;display:block;background:#f8fafc;box-shadow:none!important;flex-shrink:0}.product-demo-item span{display:block;width:100%;padding:.11765rem;font-size:.15294rem;line-height:1.4;font-weight:600;margin-top:auto;text-align:center}.scene-application-card{position:relative;display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.12fr);align-items:stretch;min-height:4rem;color:#0f172a;text-decoration:none;border-radius:.23529rem;overflow:hidden;background-color:#f8fafc;border:none;box-shadow:0 .21176rem .47059rem rgba(15,23,42,.1);border:.01176rem solid rgba(148,163,184,.22)}.scene-application-card--scene1{background-image:linear-gradient(180deg,rgba(15,23,42,.08),rgba(15,23,42,.56)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:50%}.scene-application-card--scene2{background-image:linear-gradient(180deg,rgba(15,23,42,.1),rgba(15,23,42,.58)),url(https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1230/dial_ha_demo_01.jpg);background-position:64%}.scene-application-card:hover{color:#0f172a}.scene-application-card,.scene-application-card .scene-application-card__title,.scene-application-card p,.scene-application-card span:not(.scene-application-card__button){color:#0f172a!important}.scene-application-card__media{position:relative;display:flex;align-items:center;justify-content:center;min-height:100%;overflow:hidden;padding:.18824rem .21176rem .18824rem .14118rem;line-height:0}.scene-application-card__media img{flex:none;width:88%;max-width:4.94118rem;max-width:100%;height:auto;max-height:100%;display:block;margin:0!important;padding:0!important;border:.01176rem solid rgba(148,163,184,.34);border-radius:.16471rem;box-shadow:0 .11765rem .28235rem rgba(15,23,42,.16);vertical-align:top;-o-object-fit:cover;object-fit:cover;-o-object-position:center;object-position:center}.scene-application-card__content{position:relative;z-index:1;display:flex;flex-direction:column;justify-content:center;grid-row-gap:.14118rem;row-gap:.14118rem;width:100%;max-width:5.17647rem;min-height:100%;padding:.32941rem .30588rem .28235rem;background:linear-gradient(180deg,hsla(0,0%,100%,.96),rgba(248,250,252,.9))}.scene-application-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));grid-gap:.21176rem;gap:.21176rem;margin:.21176rem 0 .32941rem}.scene-application-card__title{margin:.09412rem 0 0;font-size:.32941rem;line-height:1.15;font-weight:700;text-align:center;color:#0f172a!important;text-shadow:none}.scene-application-card__desc{margin:0;font-size:.17647rem;line-height:1.6;text-align:center;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden;text-overflow:ellipsis;color:rgba(30,41,59,.9)!important;text-shadow:none}.scene-application-card__button{display:inline-flex;align-items:center;justify-content:center;align-self:center;margin-top:0;width:-webkit-fit-content;width:-moz-fit-content;width:fit-content;min-width:1.22353rem;padding:.11765rem .18824rem;font-size:.16471rem;line-height:1;font-weight:600;white-space:nowrap;color:#fff!important;background:#2563eb;border-radius:11.75294rem;box-shadow:0 .09412rem .21176rem rgba(37,99,235,.28)}.scene-application-card .scene-application-card__button{color:#fff!important}.mobile .product-demo-grid{grid-template-columns:repeat(3,minmax(0,1fr));grid-gap:.09412rem;gap:.09412rem}.mobile .product-demo-item{border-radius:.09412rem}.mobile .product-demo-item img{height:auto;aspect-ratio:1/1;-o-object-fit:contain;object-fit:contain;-o-object-position:center;object-position:center;padding:.09412rem;box-shadow:none!important}.mobile .product-demo-item span{padding:.07059rem .07059rem .09412rem;font-size:.21176rem;line-height:1.4;text-align:center;word-break:break-word}.mobile .scene-application-card{grid-template-columns:1fr;grid-template-rows:2.35294rem minmax(0,1fr);min-height:4.58824rem;margin:0;border-radius:.16471rem}.mobile .scene-application-card__media{order:1;min-height:2.35294rem;padding:.11765rem .14118rem}.mobile .scene-application-card__media img{width:100%;max-width:none;max-height:none}.mobile .scene-application-grid{grid-template-columns:1fr;grid-gap:.16471rem;gap:.16471rem}.mobile .scene-application-card__content{order:2;max-width:none;justify-content:center;padding:.23529rem .21176rem;background:linear-gradient(180deg,hsla(0,0%,100%,.97),rgba(248,250,252,.93));grid-row-gap:.11765rem;row-gap:.11765rem}.mobile .scene-application-card__title{font-size:.25882rem;line-height:1.2;margin-top:.07059rem}.mobile .scene-application-card__desc{font-size:.15294rem;line-height:1.5;-webkit-line-clamp:4}.mobile .scene-application-card__button{min-width:1.17647rem;margin-top:.09412rem;padding:.10588rem .16471rem;font-size:.15294rem}.project-item{display:flex;height:1.96471rem;margin:.11765rem 0}.project-item .project-img{width:1.96471rem;height:1.96471rem;position:relative;overflow:hidden;text-align:center}.project-item .project-img img{height:100%;font-size:.09412rem}.project-item .project-img a{opacity:0;position:absolute;top:0;left:0;right:0;bottom:0}.project-item .project-contents{flex:1;background-color:#efefef;padding:0 .38824rem;position:relative;display:flex;flex-direction:column;justify-content:center}.project-item .project-contents .project-title{font-size:.25882rem;font-weight:700;line-height:.27059rem}.project-item .project-contents .project-title a{color:#238dfb}.project-item .project-contents .project-desc{margin-top:.15294rem;font-size:.22353rem;font-weight:400;color:#717171;line-height:.29412rem}.saerch-fliter-container{height:1.17647rem;border-bottom:.04706rem dashed #e5e5e5;display:flex}.saerch-fliter-container .search-fliter-title{font-size:.21176rem;font-weight:400;color:#434343;width:1.50588rem;margin-right:.58824rem}.saerch-fliter-container .search-fliter-options{flex:1;display:flex;flex-wrap:wrap}.saerch-fliter-container .search-fliter-options .fliter-option{font-size:.18824rem;font-weight:400;color:#959595;padding:0 .35294rem 0 0;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.saerch-fliter-container .search-fliter-options .fliter-option.active{color:#0064c2}.mobile .saerch-fliter-container{height:2.82353rem;margin-top:.35294rem}.dev-layout{flex-wrap:wrap;justify-content:space-between;margin-bottom:.70588rem;flex-direction:column}.dev-container,.dev-layout{display:flex;width:100%}.mobile .dev-container{flex-direction:column;min-height:60vh}.dev-info-container{margin:.70588rem .23529rem;display:flex;color:#5f5d5d;width:3.52941rem;overflow:hidden;flex-direction:column}.dev-info-container .dev-contents{display:flex;flex-direction:column;align-items:center;text-align:center}.dev-info-container .dev-title{font-size:.47059rem;padding:.35294rem}.dev-info-container .dev-desc{font-size:.18824rem;padding:.35294rem;line-height:.28235rem;font-weight:300;height:1.17647rem}.dev-info-container .dev-button{width:1.64706rem;height:.47059rem;background:#0064c2;border-radius:.05882rem;color:#fff;text-align:center}.dev-info-container .dev-banner{padding:.05882rem;overflow:hidden;border-radius:.11765rem}.dev-info-container .dev-banner img{box-shadow:0 0 .23529rem 0 #efefef;background-size:cover;width:5.29412rem;transition:all .25s ease;border-radius:.11765rem}.dev-info-container .dev-banner img:hover{transform:scale(1.1)}.mobile .dev-info-container{width:100%;flex-direction:row}@-webkit-keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@keyframes swing-in-top-fwd{0%{transform:rotateX(-100deg);transform-origin:top;opacity:0}to{transform:rotateX(0);transform-origin:top;opacity:1}}@-webkit-keyframes fade-in{0%{opacity:0}to{opacity:1}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}@-webkit-keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}@keyframes scroll-text{0%{transform:translateX(0)}20%{transform:translateX(0)}80%{transform:translateX(calc(100% - 2.11765rem))}to{transform:translateX(calc(100% - 2.11765rem))}}.float-icon-container{position:fixed;right:23PX;bottom:80PX;z-index:6;height:120PX;width:50PX}.float-icon-container .totop-icon{position:absolute;top:0;left:0}.float-icon-container .menu-icon{position:absolute;top:70PX;left:0}.float-icon-container .menu-icon.active,.float-icon-container .menu-icon.active:hover{background-color:#2f495e}.float-icon-container .menu-icon,.float-icon-container .totop-icon{width:50PX;height:50PX;display:flex;align-items:center;justify-content:center;border-radius:50%;background-color:#0870d1;box-shadow:0 0 .35294rem -.02353rem rgba(19,41,75,.14),0 .14118rem .15294rem -.02353rem rgba(19,41,75,.13),0 .07059rem .07059rem -.02353rem rgba(19,41,75,.13),0 .02353rem .02353rem -.02353rem rgba(19,41,75,.12);cursor:pointer;z-index:200}.float-icon-container .menu-icon svg,.float-icon-container .totop-icon svg{width:50PX;height:50PX}.float-icon-container .menu-icon svg path,.float-icon-container .totop-icon svg path{fill:#fefefe}.float-icon-container .menu-icon:hover,.float-icon-container .totop-icon:hover{background-color:#058ce6}.markdown .hljs{color:#263445;background:0 0}.markdown .hljs-comment,.markdown .hljs-quote{color:#687789;font-style:normal}.markdown .hljs-addition,.markdown .hljs-keyword,.markdown .hljs-selector-tag{color:#b4233f;font-weight:500}.markdown .hljs-link,.markdown .hljs-literal,.markdown .hljs-number,.markdown .hljs-regexp{color:#1769aa}.markdown .hljs-doctag,.markdown .hljs-meta .hljs-meta-string,.markdown .hljs-string{color:#16705a}.markdown .hljs-name,.markdown .hljs-section,.markdown .hljs-selector-class,.markdown .hljs-selector-id,.markdown .hljs-title{color:#6f52a2}.markdown .hljs-attr,.markdown .hljs-attribute,.markdown .hljs-template-variable,.markdown .hljs-variable{color:#8a5a00}.markdown .hljs-built_in,.markdown .hljs-builtin-name,.markdown .hljs-class .hljs-title,.markdown .hljs-type{color:#9a4d16}.markdown .hljs-bullet,.markdown .hljs-meta,.markdown .hljs-meta .hljs-keyword,.markdown .hljs-selector-attr,.markdown .hljs-selector-pseudo,.markdown .hljs-subst,.markdown .hljs-symbol{color:#526579}.markdown .hljs-deletion{color:#b4233f}.markdown .hljs-formula{background:#eaf1f7}.markdown .hljs-emphasis{font-style:italic}.markdown .hljs-strong{font-weight:600}/*!
- * Viewer.js v1.11.6
- * https://fengyuanchen.github.io/viewerjs
- *
- * Copyright 2015-present Chen Fengyuan
- * Released under the MIT license
- *
- * Date: 2023-09-17T03:16:35.830Z
- */.viewer-close:before,.viewer-flip-horizontal:before,.viewer-flip-vertical:before,.viewer-fullscreen-exit:before,.viewer-fullscreen:before,.viewer-next:before,.viewer-one-to-one:before,.viewer-play:before,.viewer-prev:before,.viewer-reset:before,.viewer-rotate-left:before,.viewer-rotate-right:before,.viewer-zoom-in:before,.viewer-zoom-out:before{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAARgAAAAUCAYAAABWOyJDAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAALEgAACxIB0t1+/AAAABx0RVh0U29mdHdhcmUAQWRvYmUgRmlyZXdvcmtzIENTNui8sowAAAQPSURBVHic7Zs/iFxVFMa/0U2UaJGksUgnIVhYxVhpjDbZCBmLdAYECxsRFBTUamcXUiSNncgKQbSxsxH8gzAP3FU2jY0kKKJNiiiIghFlccnP4p3nPCdv3p9778vsLOcHB2bfveeb7955c3jvvNkBIMdxnD64a94GHMfZu3iBcRynN7zAOI7TG15gHCeeNUkr8zaxG2lbYDYsdgMbktBsP03jdQwljSXdtBhLOmtjowC9Mg9L+knSlcD8TNKpSA9lBpK2JF2VdDSR5n5J64m0qli399hNFMUlpshQii5jbXTbHGviB0nLNeNDSd9VO4A2UdB2fp+x0eCnaXxWXGA2X0au/3HgN9P4LFCjIANOJdrLr0zzZ+BEpNYDwKbpnQMeAw4m8HjQtM6Z9qa917zPQwFr3M5KgA6J5rTJCdFZJj9/lyvGhsDvwFNVuV2MhhjrK6b9bFiE+j1r87eBl4HDwCF7/U/k+ofAX5b/EXBv5JoLMuILzf3Ap6Z3EzgdqHMCuF7hcQf4HDgeoHnccncqdK/TvSDWffFXI/exICY/xZyqc6XLWF1UFZna4gJ7q8BsRvgd2/xXpo6P+D9dfT7PpECtA3cnWPM0GXGFZh/wgWltA+cDNC7X+AP4GzjZQe+k5dRxuYPeiuXU7e1qwLpDz7dFjXKRaSwuMLvAlG8zZlG+YmiK1HoFqT7wP2z+4Q45TfEGcMt01xLoNZEBTwRqD4BLpnMLeC1A41UmVxsXgXeBayV/Wx20rpTyrpnWRft7p6O/FdqzGrDukPNtkaMoMo3FBdBSQMOnYBCReyf05s126fU9ytfX98+mY54Kxnp7S9K3kj6U9KYdG0h6UdLbkh7poFXMfUnSOyVvL0h6VtIXHbS6nOP+s/Zm9mvyXW1uuC9ohZ72E9uDmXWLJOB1GxsH+DxPftsB8B6wlGDN02TAkxG6+4D3TWsbeC5CS8CDFce+AW500LhhOW2020TRjK3b21HEmgti9m0RonxbdMZeVzV+/4tF3cBpP7E9mKHNL5q8h5g0eYsCMQz0epq8gQrwMXAgcs0FGXGFRcB9wCemF9PkbYqM/Bas7fxLwNeJPdTdpo4itQti8lPMqTpXuozVRVXPpbHI3KkNTB1NfkL81j2mvhDp91HgV9MKuRIqrykj3WPq4rHyL+axj8/qGPmTqi6F9YDlHOvJU6oYcTsh/TYSzWmTE6JT19CtLTJt32D6CmHe0eQn1O8z5AXgT4sx4Vcu0/EQecMydB8z0hUWkTd2t4CrwNEePqMBcAR4mrBbwyXLPWJa8zrXmmLEhNBmfpkuY2102xxrih+pb+ieAb6vGhuA97UcJ5KR8gZ77K+99xxeYBzH6Q3/Z0fHcXrDC4zjOL3hBcZxnN74F+zlvXFWXF9PAAAAAElFTkSuQmCC);background-repeat:no-repeat;background-size:280px;color:transparent;display:block;font-size:0;height:20px;line-height:0;width:20px}.viewer-zoom-in:before{background-position:0 0;content:"Zoom In"}.viewer-zoom-out:before{background-position:-20px 0;content:"Zoom Out"}.viewer-one-to-one:before{background-position:-40px 0;content:"One to One"}.viewer-reset:before{background-position:-60px 0;content:"Reset"}.viewer-prev:before{background-position:-80px 0;content:"Previous"}.viewer-play:before{background-position:-100px 0;content:"Play"}.viewer-next:before{background-position:-120px 0;content:"Next"}.viewer-rotate-left:before{background-position:-140px 0;content:"Rotate Left"}.viewer-rotate-right:before{background-position:-160px 0;content:"Rotate Right"}.viewer-flip-horizontal:before{background-position:-180px 0;content:"Flip Horizontal"}.viewer-flip-vertical:before{background-position:-200px 0;content:"Flip Vertical"}.viewer-fullscreen:before{background-position:-220px 0;content:"Enter Full Screen"}.viewer-fullscreen-exit:before{background-position:-240px 0;content:"Exit Full Screen"}.viewer-close:before{background-position:-260px 0;content:"Close"}.viewer-container{bottom:0;direction:ltr;font-size:0;left:0;line-height:0;overflow:hidden;position:absolute;right:0;-webkit-tap-highlight-color:transparent;top:0;touch-action:none;-webkit-touch-callout:none;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.viewer-container ::-moz-selection,.viewer-container::-moz-selection{background-color:transparent}.viewer-container ::selection,.viewer-container::selection{background-color:transparent}.viewer-container:focus{outline:0}.viewer-container img{display:block;height:auto;max-height:none!important;max-width:none!important;min-height:0!important;min-width:0!important;width:100%}.viewer-canvas{bottom:0;left:0;overflow:hidden;position:absolute;right:0;top:0}.viewer-canvas>img{height:auto;margin:15px auto;max-width:90%!important;width:auto}.viewer-footer{bottom:0;left:0;overflow:hidden;position:absolute;right:0;text-align:center}.viewer-navbar{background-color:rgba(0,0,0,.5);overflow:hidden}.viewer-list{box-sizing:content-box;height:50px;margin:0;overflow:hidden;padding:1px 0}.viewer-list>li{color:transparent;cursor:pointer;float:left;font-size:0;height:50px;line-height:0;opacity:.5;overflow:hidden;transition:opacity .15s;width:30px}.viewer-list>li:focus,.viewer-list>li:hover{opacity:.75}.viewer-list>li:focus{outline:0}.viewer-list>li+li{margin-left:1px}.viewer-list>.viewer-loading{position:relative}.viewer-list>.viewer-loading:after{border-width:2px;height:20px;margin-left:-10px;margin-top:-10px;width:20px}.viewer-list>.viewer-active,.viewer-list>.viewer-active:focus,.viewer-list>.viewer-active:hover{opacity:1}.viewer-player{background-color:#000;bottom:0;cursor:none;display:none;right:0;z-index:1}.viewer-player,.viewer-player>img{left:0;position:absolute;top:0}.viewer-toolbar>ul{display:inline-block;margin:0 auto 5px;overflow:hidden;padding:6px 3px}.viewer-toolbar>ul>li{background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;float:left;height:24px;overflow:hidden;transition:background-color .15s;width:24px}.viewer-toolbar>ul>li:focus,.viewer-toolbar>ul>li:hover{background-color:rgba(0,0,0,.8)}.viewer-toolbar>ul>li:focus{box-shadow:0 0 3px #fff;outline:0;position:relative;z-index:1}.viewer-toolbar>ul>li:before{margin:2px}.viewer-toolbar>ul>li+li{margin-left:1px}.viewer-toolbar>ul>.viewer-small{height:18px;margin-bottom:3px;margin-top:3px;width:18px}.viewer-toolbar>ul>.viewer-small:before{margin:-1px}.viewer-toolbar>ul>.viewer-large{height:30px;margin-bottom:-3px;margin-top:-3px;width:30px}.viewer-toolbar>ul>.viewer-large:before{margin:5px}.viewer-tooltip{background-color:rgba(0,0,0,.8);border-radius:10px;color:#fff;display:none;font-size:12px;height:20px;left:50%;line-height:20px;margin-left:-25px;margin-top:-10px;position:absolute;text-align:center;top:50%;width:50px}.viewer-title{color:#ccc;display:inline-block;font-size:12px;line-height:1.2;margin:5px 5%;max-width:90%;min-height:14px;opacity:.8;overflow:hidden;text-overflow:ellipsis;transition:opacity .15s;white-space:nowrap}.viewer-title:hover{opacity:1}.viewer-button{-webkit-app-region:no-drag;background-color:rgba(0,0,0,.5);border-radius:50%;cursor:pointer;height:80px;overflow:hidden;position:absolute;right:-40px;top:-40px;transition:background-color .15s;width:80px}.viewer-button:focus,.viewer-button:hover{background-color:rgba(0,0,0,.8)}.viewer-button:focus{box-shadow:0 0 3px #fff;outline:0}.viewer-button:before{bottom:15px;left:15px;position:absolute}.viewer-fixed{position:fixed}.viewer-open{overflow:hidden}.viewer-show{display:block}.viewer-hide{display:none}.viewer-backdrop{background-color:rgba(0,0,0,.5)}.viewer-invisible{visibility:hidden}.viewer-move{cursor:move;cursor:-webkit-grab;cursor:grab}.viewer-fade{opacity:0}.viewer-in{opacity:1}.viewer-transition{transition:all .3s}@-webkit-keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}@keyframes viewer-spinner{0%{transform:rotate(0)}to{transform:rotate(1turn)}}.viewer-loading:after{-webkit-animation:viewer-spinner 1s linear infinite;animation:viewer-spinner 1s linear infinite;border:4px solid hsla(0,0%,100%,.1);border-left-color:hsla(0,0%,100%,.5);border-radius:50%;content:"";display:inline-block;height:40px;left:50%;margin-left:-20px;margin-top:-20px;position:absolute;top:50%;width:40px;z-index:1}@media (max-width:767px){.viewer-hide-xs-down{display:none}}@media (max-width:991px){.viewer-hide-sm-down{display:none}}@media (max-width:1199px){.viewer-hide-md-down{display:none}}.nuxt-progress{position:fixed;top:0;left:0;right:0;height:.02353rem;width:0;opacity:1;transition:width .1s,opacity .4s;background-color:#000;z-index:999999}.nuxt-progress.nuxt-progress-notransition{transition:none}.nuxt-progress-failed{background-color:red}.side-bar{width:2.47059rem;position:sticky;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.side-bar .side-bar-title{height:.82353rem;width:2.47059rem;background-image:url(/assets/sidebar-title.jpg);background-size:cover}.side-bar .side-bar-title p{height:.21176rem;font-size:.28235rem;font-weight:700;color:#fff;line-height:.82353rem;text-align:center}.side-bar .side-bar-contents{cursor:pointer;border-bottom:.02353rem solid #e5e5e5;border-left:.02353rem solid #e5e5e5;border-right:.02353rem solid #e5e5e5}.side-bar .side-bar-contents .side-bar-collapse{position:relative;height:.50588rem;overflow:hidden;transition:all .2s ease;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.side-bar .side-bar-contents .side-bar-collapse .collapse-title{font-size:.18824rem;font-weight:400;color:#434343;line-height:.50588rem;padding-left:.24706rem;border-top:.01176rem solid #edf1f4;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.side-bar .side-bar-contents .side-bar-collapse .collapse-title.active{color:#409eff}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn{position:absolute;height:.11765rem;width:.11765rem;box-shadow:.02353rem -.02353rem 0 #82a5d7;background-color:#fff;top:.2rem;right:.18824rem;transform:rotate(45deg);transition:all .25s ease}.side-bar .side-bar-contents .side-bar-collapse .collapse-btn.collapse-btn-active{transform:translate(.04706rem,-.04706rem) rotate(135deg)}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents{border-bottom:.01176rem solid #edf1f4}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item{padding-left:.38824rem;line-height:.44706rem;color:#838383;font-size:.16471rem}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active{color:#409eff;background-color:#f6f7f8;position:relative}.side-bar .side-bar-contents .side-bar-collapse .collapse-contents .collapse-contents-item.active:after{content:" ";width:.04706rem;height:.04706rem;background:#82a5d7;border-radius:50%;position:absolute;top:50%;left:.17647rem;transform:translateY(-50%)}.page-header-container{margin-bottom:.35294rem;width:100%}.page-header-container .page-header-content{display:flex;align-content:center;position:relative}.page-header-container .page-header-content .page-header-arrow-icon{width:.28235rem;height:.32941rem;padding-top:.02353rem;color:#2f495e;font-size:.23529rem;transition:all .2s ease}.page-header-container .page-header-content .header-arrow-container{width:.17647rem;height:.17647rem;background-image:url(/assets/arrow3.png);background-size:cover}.page-header-container .page-header-content .page-header-arrow-icon:hover{color:#007bff}.page-header-container .page-header-content .page-header-item{color:#858585;font-size:.18824rem;font-weight:500;display:flex;height:.35294rem;line-height:.35294rem;cursor:pointer;align-items:center}.page-header-container .page-header-content .page-header-item .page-header-tag{margin:0 .09412rem;transition:all .2s ease}.page-header-container .page-header-content .page-header-item .page-header-tag.active{color:#2f495e}.page-header-container .page-header-content .page-header-item .page-header-tag:hover{color:#007bff}.mobile .page-header-container{margin-top:.35294rem}.search-box{display:flex;grid-gap:.11765rem;gap:.11765rem;margin-bottom:.28235rem;position:relative;align-items:center}.search-box input{flex:1;min-width:7.05882rem;height:.51765rem;background:#edf1f4;border-radius:.09412rem;border:.01176rem solid #d5dee8;padding:0 .18824rem;font-size:.17647rem;color:#253443;outline:0;z-index:3;transition:border-color .2s ease,box-shadow .2s ease}.search-box input:focus{border-color:#0064c2;box-shadow:0 0 0 .03529rem rgba(0,100,194,.12157)}.search-box .search-btn{width:1.55294rem;height:.51765rem;background:#0064c2;border-radius:.09412rem;border:none;cursor:pointer;transition:background-color .2s ease}.search-box .search-btn:hover{background:#0a5aaa}.search-box .search-btn p{margin:0;line-height:.51765rem;font-size:.18824rem;font-weight:700;color:#fff}.search-box .search-cover{position:fixed;top:0;left:0;right:0;bottom:0;z-index:2;background-color:rgba(25,25,25,.1098);-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem)}.search-result-container{overflow:hidden}.search-result-container::-webkit-scrollbar{width:.14118rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-track{-webkit-box-shadow:#cbd5e1;border-radius:.09412rem;cursor:pointer}.search-result-container::-webkit-scrollbar-thumb,.search-result-container::-webkit-scrollbar-thumb:window-inactive{background:#cbd5e1}.search-result-container .el-tabs__item{display:table-cell;font-size:.21176rem;font-weight:600}.search-result-container .el-tabs__active-bar{height:.04706rem}.search-result-container{width:100%;min-height:4.47059rem;max-height:7.05882rem;overflow-y:auto;background-color:#fff;position:absolute;top:.63529rem;border:.01176rem solid #e2e8f0;border-radius:.11765rem;box-shadow:0 .11765rem .17647rem -.03529rem rgba(0,0,0,.10196),0 .04706rem .07059rem -.02353rem rgba(0,0,0,.05098);transition:all .25s ease;color:#2f495e;z-index:3;padding:.14118rem;-webkit-animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both;animation:swing-in-top-fwd .5s cubic-bezier(.175,.885,.32,1.275) both}.search-result-container .search-title{height:.70588rem;font-size:.29412rem;padding:.17647rem;border-bottom:.01176rem solid #d9d9d9}.search-result-container .search-result-contents{display:flex;align-items:flex-start;grid-gap:.11765rem;gap:.11765rem;padding:.14118rem;border-bottom:.01176rem solid #edf2f7;position:relative}.search-result-container .search-result-contents svg{display:inline;font-size:.23529rem;color:#409eff;padding-right:.11765rem}.search-result-container .search-result-contents:hover{background-color:#f3f8fd}.search-result-container .search-result-content{flex:1;display:flex;flex-direction:column;justify-content:center;position:relative;transition:all .25s ease}.search-result-container .search-result-name{font-size:.18824rem;text-align:left;font-weight:700;color:#409eff;line-height:1.4}.search-result-container .search-result-sku{font-size:.16471rem;line-height:1.6;color:#5b5b5b;margin-top:.04706rem}.search-result-container .search-result-key{font-size:.18824rem;font-weight:700;color:#2f495e;margin-top:.04706rem}.search-result-container .search-result-key .search-result-highlight{color:#409eff}.search-result-container .search-result-key .search-result-key-tag{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#5b5b5b;padding:.02353rem .11765rem;border:.01176rem solid #5b5b5b;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container .search-result-key .search-result-key-tag.active{color:#409eff;border:.01176rem solid #409eff}.search-result-container .search-result-image{width:1.31765rem;height:1.31765rem;margin:0 .21176rem 0 .04706rem}.search-result-container .search-result-eol-tag{position:absolute;width:.41176rem;height:.41176rem;border-radius:50%;top:5%;left:.35294rem;background-color:#2f495e;color:#fff;font-size:.15294rem;font-weight:700;line-height:.41176rem;text-align:center}.search-result-container .search-result-recommand-box{margin-top:.14118rem}.search-result-container .search-result-recommand-box .search-result-recommand-item{cursor:pointer;margin:.07059rem .07059rem 0 0;font-size:.15294rem;display:inline-block;color:#409eff;padding:.04706rem .11765rem;border:.01176rem solid #409eff;border-radius:.05882rem;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.search-result-container:before{display:block;position:absolute;content:"";width:.16471rem;height:.16471rem;background:#fff;z-index:1000;top:-.08235rem;left:calc(50% - .08235rem);border-top:.01176rem solid #d9d9d9;border-right:.01176rem solid #d9d9d9;transform:rotate(-45deg);border-radius:.02353rem}.mobile .search-box{margin-bottom:.09412rem;width:100%;grid-gap:.09412rem;gap:.09412rem}.mobile .search-box input{height:.65882rem;font-size:.2rem}.mobile .search-box .search-btn{width:2.11765rem;height:.65882rem;background:#0064c2;border-radius:.09412rem}.mobile .search-box .search-btn p{margin:0;line-height:.65882rem;font-size:.21176rem;font-weight:700;color:#fff}.mobile .search-result-container{top:.75294rem}.search-result-container .tabs{display:flex;grid-gap:.07059rem;gap:.07059rem;width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .14118rem;padding:.09412rem .14118rem;border-radius:0;background:hsla(0,0%,100%,.9);border:0;border-bottom:.01176rem solid #e6edf5;-webkit-backdrop-filter:blur(.04706rem);backdrop-filter:blur(.04706rem);position:sticky;top:-.14118rem;z-index:6}.search-result-container .tabs:after{content:"";position:absolute;left:0;right:0;top:0;bottom:0;background:0 0;z-index:-1}.search-result-container .tabs button{min-width:1.27059rem;padding:.10588rem .18824rem;border-radius:.11765rem;font-size:.16471rem;font-weight:600;color:#516578;background:hsla(0,0%,100%,.6);border:.01176rem solid #d7e3ef;line-height:1.2;overflow:hidden;transition:color .2s ease,background-color .2s ease,box-shadow .2s ease}.search-result-container .tabs button:first-child,.search-result-container .tabs button:last-child{border-radius:.11765rem}.search-result-container .tabs button:hover{color:#2f4f6f;background:#f8fbff;border-color:#cddded}.search-result-container .tabs button.active{color:#0f4f8e;background:#fff;border:.01176rem solid #c8d9eb;border-radius:.11765rem;box-shadow:0 .02353rem .09412rem rgba(0,100,194,.16078)}.search-result-container .tab-content{padding:.11765rem .09412rem .09412rem;background:0 0}.search-result-container .search-result-contents{border-radius:.09412rem;transition:background-color .2s ease,box-shadow .2s ease}.search-result-container .search-result-contents:hover{box-shadow:inset 0 0 0 .01176rem #dbe9f8}.search-result-contents-list{padding-bottom:.82353rem}.search-result-view-all-wrap{position:sticky;bottom:0;z-index:4;display:flex;justify-content:center;padding:.11765rem .09412rem .07059rem;background:linear-gradient(0deg,#fff 70%,hsla(0,0%,100%,0))}.search-result-view-all-btn{display:inline-block;min-width:2.82353rem;text-align:center;padding:.12941rem .21176rem;border-radius:.28235rem;background:#0064c2;color:#fff;font-size:.17647rem;font-weight:700;text-decoration:none;box-shadow:0 .04706rem .14118rem rgba(0,100,194,.25);transition:background-color .2s ease}.search-result-view-all-btn:hover{background:#0a5aaa}.mobile .search-result-container .tabs{width:calc(100% + .28235rem);margin:-.14118rem -.14118rem .11765rem;padding:.09412rem .11765rem}.mobile .search-result-container .tabs button{flex:1;min-width:0;padding:.14118rem .11765rem;font-size:.17647rem}.mobile .search-result-container .tab-content{padding:.09412rem .04706rem .07059rem}.search-result-container.search-result-embedded{position:relative;top:auto;max-height:none;min-height:0;padding:0;box-shadow:none;-webkit-animation:none;animation:none}.search-result-container.search-result-embedded:before{display:none}.search-result-loading{padding:.09412rem .04706rem;display:flex;flex-direction:column}.search-result-loading-header{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;color:#516578;font-size:.16471rem;margin:0 0 .11765rem}.search-result-loading-text{min-width:0;font-size:.16471rem;font-weight:400;line-height:.23529rem}.search-result-loading-dot{width:.09412rem;height:.09412rem;border-radius:50%;background:#409eff;-webkit-animation:search-loading-pulse 1s ease-in-out infinite;animation:search-loading-pulse 1s ease-in-out infinite}.search-result-loading-list{display:flex;flex-direction:column;grid-gap:.11765rem;gap:.11765rem}.search-result-loading-item{padding:.14118rem;border-radius:.09412rem;border:.01176rem solid #edf2f7;background:#fbfdff}.search-result-loading-line{height:.11765rem;border-radius:11.75294rem;margin-bottom:.09412rem;background:linear-gradient(90deg,#e9f0f7 20%,#f5f9fd 45%,#e9f0f7 70%);background-size:2.82353rem 100%;-webkit-animation:search-loading-shimmer 1.1s linear infinite;animation:search-loading-shimmer 1.1s linear infinite}.search-result-loading-line.is-title{width:52%;height:.14118rem}.search-result-loading-line.is-short{width:36%;margin-bottom:0}@-webkit-keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@keyframes search-loading-shimmer{0%{background-position:-2.82353rem 0}to{background-position:2.82353rem 0}}@-webkit-keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}@keyframes search-loading-pulse{0%,to{opacity:.4;transform:scale(1)}50%{opacity:1;transform:scale(1.18)}}.search-result-loading-text[data-v-2b770079]{min-width:0;font-size:.16471rem!important;font-weight:400;line-height:.23529rem}.tab-panel{border:.01176rem solid #e5e5e5;padding:.09412rem;border-radius:.09412rem}.tabs{display:flex;grid-gap:.09412rem;gap:.09412rem;margin-bottom:.18824rem}.tabs button{padding:.11765rem .21176rem;border:none;border-bottom:.04706rem solid transparent;background:#f9f9f9;cursor:pointer;transition:.2s}.tabs button.active{border-color:#007bff;color:#007bff}.tab-content{padding:.18824rem;background:#fefefe;border-radius:.09412rem}.search-result-container .tab-panel{border:0}.carousel-container[data-v-6e07f87d]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-6e07f87d]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-6e07f87d]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-6e07f87d]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-6e07f87d]{flex-shrink:0;width:33.333%;text-align:center;cursor:pointer}.preview-image img[data-v-6e07f87d]{max-width:100%;height:auto;margin:0}.arrow[data-v-6e07f87d]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-6e07f87d]{left:0;transform:rotateY(180deg)}.arrow.right[data-v-6e07f87d]{right:0}.carousel-thumbnails[data-v-6e07f87d]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-6e07f87d]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-6e07f87d]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-6e07f87d]{width:100%;margin:0;height:auto}.clickable-area[data-v-6e07f87d]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-6e07f87d]{left:0}.clickable-area.right[data-v-6e07f87d]{right:0}.carousel-container[data-v-7d51a79c]{display:flex;flex-direction:column;align-items:flex-start;width:100%;margin:auto}.carousel-preview[data-v-7d51a79c]{position:relative;width:100%;display:flex;align-items:center;justify-content:space-between;margin-bottom:.29412rem;overflow:hidden}.carousel-images[data-v-7d51a79c]{flex:1;overflow:hidden;position:relative}.image-wrapper[data-v-7d51a79c]{display:flex;width:100%;transition:transform .5s ease}.preview-image[data-v-7d51a79c]{flex-shrink:0;width:100%;text-align:center;cursor:pointer}.preview-image img[data-v-7d51a79c]{width:100%;height:auto;margin:0}.arrow[data-v-7d51a79c]{position:absolute;top:50%;transform:translateY(-50%);background:hsla(0,0%,92.2%,.87059);color:#fff;border:none;padding:.11765rem;cursor:pointer;z-index:2;height:.58824rem;width:.47059rem;background-image:url(/assets/arrow2.png);background-repeat:no-repeat;background-size:auto 70%;background-position:50%}.arrow.left[data-v-7d51a79c]{left:0;transform:translateY(-50%) rotateY(180deg)}.arrow.right[data-v-7d51a79c]{right:0;transform:translateY(-50%)}.carousel-thumbnails[data-v-7d51a79c]{display:flex;flex-wrap:wrap;grid-gap:.11765rem;gap:.11765rem;margin-top:.11765rem;align-items:flex-start}.thumbnail[data-v-7d51a79c]{width:.94118rem;height:.94118rem;opacity:.5;cursor:pointer;transition:opacity .3s ease}.thumbnail.active[data-v-7d51a79c]{opacity:1;border:.02353rem solid #0870d1}.thumbnail img[data-v-7d51a79c]{width:100%;margin:0;height:auto}.clickable-area[data-v-7d51a79c]{position:absolute;top:0;bottom:0;width:10%;z-index:1;cursor:pointer}.clickable-area.left[data-v-7d51a79c]{left:0}.clickable-area.right[data-v-7d51a79c]{right:0}.corner-marker[data-v-7d51a79c]{position:absolute;bottom:.11765rem;left:.11765rem;background-color:rgba(0,0,0,.5);color:#fff;padding:.05882rem .11765rem;border-radius:.05882rem;z-index:2}.page-tools[data-v-39baf185]{width:2.35294rem;margin-bottom:.16471rem;border:.01176rem solid #dfeaf5;border-radius:.11765rem;background:#f8fbfe;box-shadow:0 .07059rem .21176rem rgba(19,41,75,.08);overflow:visible}.page-tools-title[data-v-39baf185]{height:.4rem;line-height:.4rem;padding:0 .14118rem;border-bottom:.01176rem solid #e5eef7;color:#2f495e;font-size:.15294rem;font-weight:700}.page-tools-actions[data-v-39baf185]{display:flex;flex-direction:column;grid-gap:.09412rem;gap:.09412rem;padding:.11765rem;align-items:stretch}.page-tools-action[data-v-39baf185]{display:inline-flex;align-items:center;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;height:.43529rem;width:100%;padding:0 .11765rem;border:.01176rem solid #d6e5f3;border-radius:.08235rem;background:#fff;color:#238dfb;font-size:.15294rem;font-weight:700;transition:background-color .2s ease,border-color .2s ease,transform .2s ease}.page-tools-action .page-tools-icon[data-v-39baf185]{width:.21176rem;height:.21176rem;flex:0 0 auto;fill:currentColor;display:block}.page-tools-action[data-v-39baf185]:after{content:"";width:.08235rem;height:.08235rem;margin-left:auto;border-top:.02353rem solid;border-right:.02353rem solid;transform:rotate(45deg);opacity:.45}.page-tools-action[data-v-39baf185]:hover{background:#eaf4ff;border-color:#b9d8f4;transform:translateY(-.01176rem)}.page-tools.mobile[data-v-39baf185]{width:auto;margin:.09412rem 0 .18824rem;border:0;background:0 0;box-shadow:none}.page-tools.mobile .page-tools-actions[data-v-39baf185]{flex-direction:row;padding:0}.page-tools.mobile .page-tools-action[data-v-39baf185]{width:.63529rem;min-width:.63529rem;height:.42353rem;padding:0;background:#edf6ff;border-color:#b7d8f5;justify-content:center}.page-tools.mobile .page-tools-action[data-v-39baf185]:after{display:none}.markdown-action-menu[data-v-5d6a4f8a]{position:relative;display:flex;justify-content:flex-end;margin:-.14118rem 0 .21176rem;z-index:20}.markdown-action-trigger[data-v-5d6a4f8a]{display:inline-flex;align-items:center;grid-gap:.09412rem;gap:.09412rem;height:.47059rem;padding:0 .16471rem;border:.01176rem solid #b9cfe5;border-radius:.07059rem;background:linear-gradient(135deg,#0064c2,#238dfb);color:#fff;font-size:.16471rem;font-weight:700;cursor:pointer;transition:background-color .2s ease,border-color .2s ease}.markdown-action-trigger svg[data-v-5d6a4f8a]{width:.18824rem;height:.18824rem}.markdown-action-trigger[data-v-5d6a4f8a]:hover{background:linear-gradient(135deg,#0059ad,#167ce8);border-color:#82b6ec}.markdown-action-dropdown[data-v-5d6a4f8a]{position:fixed;z-index:2147483000;width:3.52941rem;overflow:hidden;border:.01176rem solid #c8dced;border-radius:.11765rem;background:#fff;box-shadow:0 .18824rem .44706rem rgba(18,62,111,.16),0 .02353rem .09412rem rgba(24,84,140,.08)}.markdown-action-item[data-v-5d6a4f8a]{display:flex;width:100%;grid-gap:.16471rem;gap:.16471rem;align-items:flex-start;padding:.17647rem .18824rem;border:0;border-bottom:.01176rem solid #e6edf5;background:0 0;color:#2f495e;text-align:left;cursor:pointer;transition:background-color .15s ease}.markdown-action-item svg[data-v-5d6a4f8a]{flex:0 0 auto;width:.2rem;height:.2rem;margin-top:.02353rem;color:#238dfb}.markdown-action-item strong[data-v-5d6a4f8a]{display:block;font-size:.17647rem;line-height:.23529rem}.markdown-action-item small[data-v-5d6a4f8a]{display:block;margin-top:.02353rem;color:#6f8193;font-size:.15294rem;line-height:.21176rem}.markdown-action-item[data-v-5d6a4f8a]:last-child{border-bottom:0}.markdown-action-item[data-v-5d6a4f8a]:hover{background:#f3f8fe}.markdown-action-menu.placement-sidebar[data-v-5d6a4f8a]{justify-content:center;margin:.14118rem 0 0}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;justify-content:center;background:#edf6ff;border-color:#c7dff7;color:#0064c2}.markdown-action-menu.placement-sidebar .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#dfefff;border-color:#9fc7ef}.markdown-action-menu.placement-sidebar .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.05882rem}.markdown-action-menu.placement-anchor[data-v-5d6a4f8a]{justify-content:flex-start;margin:0 0 .11765rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:center;padding:0 .11765rem;background:#f5f9fd;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-anchor .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-anchor .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.placement-toolbox[data-v-5d6a4f8a]{width:100%;flex:1;justify-content:flex-start;margin:0}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:100%;height:.43529rem;justify-content:flex-start;grid-gap:.10588rem;gap:.10588rem;padding:0 .11765rem;background:#fff;border-color:#d6e5f3;color:#238dfb;font-size:.15294rem}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]{flex:0 0 auto}.markdown-action-menu.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{width:.16471rem;height:.16471rem;margin-left:auto;opacity:.55}.markdown-action-menu.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]:hover{background:#eaf4ff;border-color:#b9d8f4}.markdown-action-menu.placement-toolbox .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.29412rem}.markdown-action-menu.compact[data-v-5d6a4f8a]{justify-content:flex-start;margin:.09412rem 0 .18824rem}.markdown-action-menu.compact .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center;padding:0;background:#edf6ff;border-color:#b7d8f5;color:#0064c2}.markdown-action-menu.compact .markdown-action-dropdown[data-v-5d6a4f8a]{width:3.52941rem;max-width:calc(100vw - .37647rem)}.markdown-action-menu.compact.placement-toolbox[data-v-5d6a4f8a]{flex:0 0 auto;margin:0}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger[data-v-5d6a4f8a]{width:.63529rem;height:.42353rem;justify-content:center}.markdown-action-menu.compact.placement-toolbox .markdown-action-trigger svg[data-v-5d6a4f8a]:last-child{margin-left:0}</style><link rel="preload" href="/_nuxt/static/1788504562/en/CardputerZero/state.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/en/CardputerZero/payload.js" as="script"><link rel="preload" href="/_nuxt/static/1788504562/manifest.js" as="script">
-  </head>
-  <body>
-    <div data-server-rendered="true" id="__nuxt"><!----><div id="__layout"><div class="device-hydration-sensitive"><div class="pc"><header langdata="[object Object]" lang="en"><!----> <!----> <div class="header-container"><a href="https://m5stack.com/" class="logo"><img src="/assets/m5logo.svg" alt="M5Stack"></a> <div class="header-nav"><div class="header-nav-ul"><!----> <li data-id="solution" class="header-nav-item"><a class="header-nav-item-a disabledHover">Solution</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="store" class="header-nav-item"><a href="https://shop.m5stack.com" class="header-nav-item-a">Store</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="software" class="header-nav-item"><a class="header-nav-item-a disabledHover">Software</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="document" class="header-nav-item"><a class="header-nav-item-a disabledHover">Documentation</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="aboutus" class="header-nav-item"><a class="header-nav-item-a disabledHover">About Us</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----><li data-id="contact" class="header-nav-item"><a class="header-nav-item-a disabledHover">Contact</a> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg> <!----></li> <!----></div></div> <div class="language-option-box"><div class="current-language"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 1.32 1.32" fill="currentColor" aria-hidden="true" class="icon"><g><path d="M0.66 0c0.18,0 0.35,0.07 0.47,0.19 0.12,0.12 0.19,0.28 0.19,0.47 0,0.18 -0.07,0.35 -0.19,0.47 -0.12,0.12 -0.28,0.19 -0.47,0.19 -0.18,0 -0.35,-0.07 -0.47,-0.19 -0.12,-0.12 -0.19,-0.28 -0.19,-0.47 0,-0.18 0.07,-0.35 0.19,-0.47 0.12,-0.12 0.28,-0.19 0.47,-0.19zm0.39 0.27c-0.1,-0.1 -0.24,-0.16 -0.39,-0.16 -0.15,0 -0.29,0.06 -0.39,0.16 -0.1,0.1 -0.16,0.24 -0.16,0.39 0,0.15 0.06,0.29 0.16,0.39 0.1,0.1 0.24,0.16 0.39,0.16 0.15,0 0.29,-0.06 0.39,-0.16 0.1,-0.1 0.16,-0.24 0.16,-0.39 0,-0.15 -0.06,-0.29 -0.16,-0.39z"></path> <path d="M0.09 0.51c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.09 0.92c-0.03,0 -0.05,-0.02 -0.05,-0.05 0,-0.03 0.02,-0.05 0.05,-0.05l1.14 0c0.03,0 0.05,0.02 0.05,0.05 0,0.03 -0.02,0.05 -0.05,0.05l-1.14 0z"></path> <path d="M0.62 1.21c0.02,0.02 0.02,0.06 0,0.08 -0.02,0.02 -0.06,0.02 -0.08,0 -0.07,-0.06 -0.13,-0.16 -0.16,-0.27 -0.04,-0.11 -0.06,-0.23 -0.06,-0.36 0,-0.13 0.02,-0.26 0.06,-0.36 0.04,-0.11 0.1,-0.21 0.16,-0.27 0.02,-0.02 0.06,-0.02 0.08,0 0.02,0.02 0.02,0.06 -0,0.08 -0.06,0.05 -0.1,0.13 -0.14,0.23 -0.03,0.09 -0.05,0.21 -0.05,0.33 0,0.12 0.02,0.23 0.05,0.33 0.03,0.1 0.08,0.18 0.14,0.23z"></path> <path d="M0.78 1.29c-0.02,0.02 -0.06,0.02 -0.08,-0 -0.02,-0.02 -0.02,-0.06 0,-0.08 0.06,-0.05 0.1,-0.13 0.14,-0.23 0.03,-0.09 0.05,-0.21 0.05,-0.33 0,-0.12 -0.02,-0.23 -0.05,-0.33 -0.03,-0.1 -0.08,-0.18 -0.14,-0.23 -0.02,-0.02 -0.02,-0.06 -0,-0.08 0.02,-0.02 0.06,-0.02 0.08,-0 0.07,0.06 0.13,0.16 0.16,0.27 0.04,0.11 0.06,0.23 0.06,0.36 0,0.13 -0.02,0.26 -0.06,0.36 -0.04,0.11 -0.1,0.21 -0.16,0.27z"></path></g></svg> <div>English</div> <svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" version="1.1" viewBox="0 0 3.59 2.11" fill="currentColor" aria-hidden="true" class="header-arrow-btn show-pc"><g><path d="M3.05 0.09c0.12,-0.12 0.32,-0.12 0.45,0 0.12,0.12 0.12,0.32 0,0.45l-1.48 1.48c-0.12,0.12 -0.32,0.12 -0.45,0l-1.48 -1.48c-0.12,-0.12 -0.12,-0.32 0,-0.45 0.12,-0.12 0.32,-0.12 0.45,0l1.25 1.25 1.25 -1.25z"></path></g></svg></div> <div class="language-dropdown-wrapper"><div class="language-dropdown"><div class="language-item active">English</div> <div class="language-item">简体中文</div> <div class="language-item">日本語</div></div></div></div></div></header> <div class="docs-layouts"><div class="docs-layouts-sidebar"><div class="side-bar"><div class="side-bar-title"><p>CONTENTS</p></div> <div class="side-bar-contents"></div></div></div> <div class="docs-layouts-body"><div class="page-header-container"><!----></div> <!----> <div class="search-box"><div id="search"></div> <input placeholder="Product Name / SKU"> <div class="search-result-container" style="display:none" data-v-2b770079><a class="search-result-contents" data-v-2b770079><div class="search-result-content" data-v-2b770079><div class="search-result-name" data-v-2b770079>No Results Found</div> <div class="search-result-sku" data-v-2b770079>Hot Searches</div> <div class="search-result-key" data-v-2b770079><div class="search-result-recommand-box" data-v-2b770079><div data-key="Camera" class="search-result-recommand-item" data-v-2b770079>
-            Camera
-          </div><div data-key="WiFi" class="search-result-recommand-item" data-v-2b770079>
-            WiFi
-          </div><div data-key="RS485" class="search-result-recommand-item" data-v-2b770079>
-            RS485
-          </div><div data-key="RS232" class="search-result-recommand-item" data-v-2b770079>
-            RS232
-          </div><div data-key="Relay" class="search-result-recommand-item" data-v-2b770079>
-            Relay
-          </div><div data-key="LoRaWAN" class="search-result-recommand-item" data-v-2b770079>
-            LoRaWAN
-          </div><div data-key="GPS" class="search-result-recommand-item" data-v-2b770079>
-            GPS
-          </div><div data-key="NB-IoT" class="search-result-recommand-item" data-v-2b770079>
-            NB-IoT
-          </div><div data-key="LTE" class="search-result-recommand-item" data-v-2b770079>
-            LTE
-          </div><div data-key="GSM" class="search-result-recommand-item" data-v-2b770079>
-            GSM
-          </div><div data-key="Zigbee" class="search-result-recommand-item" data-v-2b770079>
-            Zigbee
-          </div><div data-key="Servo" class="search-result-recommand-item" data-v-2b770079>
-            Servo
-          </div><div data-key="StepMotor" class="search-result-recommand-item" data-v-2b770079>
-            StepMotor
-          </div><div data-key="Ethernet" class="search-result-recommand-item" data-v-2b770079>
-            Ethernet
-          </div><div data-key="E-Paper" class="search-result-recommand-item" data-v-2b770079>
-            E-Paper
-          </div></div></div></div></a> <div class="tab-panel" style="display:none" data-v-2b770079><div class="tabs"><button>
-      Product
-    </button><button>
-      Contents
-    </button></div> <div class="tab-content"><div style="display:none"></div><div style="display:none"></div></div></div></div> <button class="search-btn"><p>Search</p></button> <div class="search-cover" style="display:none"></div></div> <div class="viewer"><div class="markdown"><h1 id="cardputerzero" data-id="CardputerZero">CardputerZero</h1> <div class="warn"><div class="warn-title">Work in progress </div> <div class="warn-content"> This product's packaging and software development are not yet complete. Final features and documentation are subject to change. We appreciate your understanding.</div></div><p><span class="product-sku">SKU:C154</span></p><div class="carousel-container" data-v-6e07f87d><div class="carousel-preview" data-v-6e07f87d><div class="clickable-area left" data-v-6e07f87d></div> <button class="arrow left" data-v-6e07f87d></button> <div class="carousel-images" data-v-6e07f87d><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-6e07f87d><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_01.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_02.jpg" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_03.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_04.jpg" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_05.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_06.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_07.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_08.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_09.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_10.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_11.png" alt="Preview" data-v-6e07f87d></div><div class="preview-image" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_12.png" alt="Preview" data-v-6e07f87d></div></div></div> <button class="arrow right" data-v-6e07f87d></button> <div class="clickable-area right" data-v-6e07f87d></div></div> <div class="carousel-thumbnails" data-v-6e07f87d><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_01.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_02.jpg" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail active" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_03.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_04.jpg" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_05.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_06.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_07.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_08.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_09.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_10.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_11.png" alt="Thumbnail" data-v-6e07f87d></div><div class="thumbnail" data-v-6e07f87d><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_12.png" alt="Thumbnail" data-v-6e07f87d></div></div></div> <h2 id="description" data-id="Description">Description</h2> <p><strong>CardputerZero</strong> is a pocket-sized <strong>Linux</strong> personal computer designed for makers and developers, built on the <strong>Raspberry Pi CM0</strong> platform. It integrates a quad-core Cortex-A53 processor, a 1.9-inch display, a 46-key matrix keyboard, an 8MP camera, an IMU, and an RTC, delivering a near-complete development terminal experience in a handheld form factor. It also features Wi-Fi, Bluetooth, Ethernet, microSD, a switchable Host/Slave USB architecture, and modular expansion capabilities via I2C/UART/SPI/GPIO. Combined with audio/video codec support and a battery-powered design, it enables an all-in-one solution for on-the-go development, edge data collection, and multimedia interaction. Typical use cases include: mobile penetration testing and operations terminals, IoT device debugging and field deployment, portable AI/vision prototyping, maker project development, and outdoor data collection with rapid human-machine interaction.</p><h2 id="features" data-id="Features">Features</h2> <ul><li>Core Performance:<ul><li>Raspberry Pi Compute Module 0 (CM0)</li> <li>RP3A0 (BCM2837), Quad-core Cortex-A53 @ 1 GHz</li> <li>512 MB LPDDR2</li></ul></li> <li>Human-Machine Interface:<ul><li>1.9" LCD, resolution 320 x 170</li> <li>46-key matrix keyboard</li> <li>IMX219 8MP camera</li> <li>BMI270 IMU + BMM150 magnetometer</li> <li>IR transmitter + receiver</li></ul></li> <li>Network Connectivity:<ul><li>2.4 GHz Wi-Fi 802.11 b/g/n</li> <li>10/100M Ethernet</li></ul></li> <li>USB Expansion:<ul><li>Supports Host / Slave mode switching</li> <li>1x USB-A 2.0</li> <li>2x USB Type-C 2.0, with USB OTG support on the right-side port</li></ul></li> <li>External Expansion:<ul><li>1x microSD card slot</li> <li>1x HY2.0-4P port with switchable I2C / UART</li> <li>EXT 2.54-14P expansion bus with SPI, UART, I2C, USB, and GPIO support</li></ul></li> <li>Audio & Video:<ul><li>ES8389 audio codec</li> <li>1x MEMS microphone</li> <li>1W @ 8Ω speaker</li> <li>3.5mm TRRS audio input/output jack</li> <li>Supports 1080P 30fps video output and codec</li></ul></li> <li>Power Management:<ul><li>Built-in DC 3.7V@1750mAh lithium battery with integrated NTC</li> <li>BQ27220YZFR battery gauge</li> <li>RX8130CE RTC</li></ul></li></ul> <h2 id="includes" data-id="Includes">Includes</h2> <div class="tip"><div class="tip-title">Product Note</div> <div class="tip-content">The standard CardputerZero includes a 32GB microSD card, whereas the CardputerZero-Lite does not include a microSD card and requires one to be purchased separately.</div></div><h3 id="cardputerzero-skuc154" data-id="CardputerZero (SKU:C154)">CardputerZero (SKU:C154)</h3> <ul><li>1 x CardputerZero</li> <li>1 x 32GB microSD Card</li></ul> <h3 id="cardputerzero-lite-skuc155" data-id="CardputerZero-Lite (SKU:C155)">CardputerZero-Lite (SKU:C155)</h3> <ul><li>1 x CardputerZero-Lite</li></ul> <h2 id="applications" data-id="Applications">Applications</h2> <ul><li>Operations terminal</li> <li>IoT device debugging</li> <li>Portable AI / vision prototyping</li> <li>Maker project development</li></ul> <h2 id="specifications" data-id="Specifications">Specifications</h2> <div class="table-container"><table><thead><tr><th>Specification</th> <th>Parameter</th></tr></thead><tbody><tr><td>Core</td> <td>Raspberry Pi Compute Module 0 (CM0)</td></tr> <tr><td>CPU</td> <td>RP3A0 (BCM2837), Quad-Core Cortex-A53 @ 1 GHz, ARMv8-A (aarch64)</td></tr> <tr><td>RAM</td> <td>512 MB LPDDR2</td></tr> <tr><td>Storage</td> <td>microSD</td></tr> <tr><td>Wi-Fi</td> <td>2.4 GHz Wi-Fi 802.11 b/g/n</td></tr> <tr><td>Ethernet</td> <td>10/100M Ethernet, SR9900A USB 2.0 to Ethernet chip</td></tr> <tr><td>Display</td> <td>1.9" LCD @ ST7789v3, resolution 320 x 170</td></tr> <tr><td>Camera</td> <td>IMX219 CSI 4-Lane 8MP (3280 x 2464)</td></tr> <tr><td>IMU & Magnetometer</td> <td>BMI270 + BMM150</td></tr> <tr><td>RTC</td> <td>RX8130CE</td></tr> <tr><td>Infrared</td> <td>IR transmitter + receiver</td></tr> <tr><td>Keyboard</td> <td>46-key matrix keyboard</td></tr> <tr><td>Audio Codec</td> <td>ES8389</td></tr> <tr><td>Microphone</td> <td>1x MEMS microphone</td></tr> <tr><td>Speaker</td> <td>AW8737A speaker amplifier + 1W @ 8Ω speaker</td></tr> <tr><td>Audio Interface</td> <td>3.5mm TRRS audio input/output jack, recommended for 35Ω impedance headphones</td></tr> <tr><td>Video Output</td> <td>1x digital HD audio/video output, supports 1080P 30fps</td></tr> <tr><td>Video Codec</td> <td>H.264 / MPEG-4 1080P 30fps decoding, H.264 1080P 30fps encoding</td></tr> <tr><td>Expansion Interface</td> <td>EXT 2.54-14P expansion bus, 1x HY2.0-4P port (switchable I2C / UART, maximum 5V output current &lt; 500mA)</td></tr> <tr><td>USB Ports</td> <td>1x USB-A 2.0, 2x USB Type-C 2.0, supports Host / Slave switching and USB OTG</td></tr> <tr><td>USB Hub Chip</td> <td>GL852G-OHY60 USB 2.0 Hub</td></tr> <tr><td>Battery Gauge</td> <td>BQ27220YZFR</td></tr> <tr><td>Idle Power Consumption</td> <td>2.5W</td></tr> <tr><td>Built-in Battery</td> <td>DC 3.7V @ 1750mAh with integrated NTC</td></tr> <tr><td>Power Supply</td> <td>Recommended 5V @ 2A for power/charging</td></tr> <tr><td>Product Size</td> <td>84.0 x 54.0 x 23.1mm</td></tr> <tr><td>Product Weight</td> <td>Work in progress</td></tr> <tr><td>Package Size</td> <td>Work in progress</td></tr> <tr><td>Gross Weight</td> <td>Work in progress</td></tr></tbody></table></div><h2 id="learn" data-id="Learn">Learn</h2> <h3 id="power-supply" data-id="Power Supply">Power Supply</h3> <h2 id="schematics" data-id="Schematics">Schematics</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702.pdf">CardputerZero Schematics PDF</a></li></ul> <div class="carousel-container" data-v-7d51a79c><div class="carousel-preview" data-v-7d51a79c><div class="clickable-area left" data-v-7d51a79c></div> <button class="arrow left" data-v-7d51a79c></button> <div class="carousel-images" data-v-7d51a79c><div class="image-wrapper" style="transform:translateX(0);transition:transform .5s ease" data-v-7d51a79c><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_01.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_02.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_03.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_04.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_05.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_06.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_07.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_08.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_09.png" alt="Preview" data-v-7d51a79c></div><div class="preview-image" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_10.png" alt="Preview" data-v-7d51a79c></div></div></div> <button class="arrow right" data-v-7d51a79c></button> <div class="clickable-area right" data-v-7d51a79c></div> <div class="corner-marker" data-v-7d51a79c>1/10</div></div> <div class="carousel-thumbnails" data-v-7d51a79c><div class="thumbnail active" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_01.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_02.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_03.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_04.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_05.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_06.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_07.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_08.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_09.png" alt="Thumbnail" data-v-7d51a79c></div><div class="thumbnail" data-v-7d51a79c><img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZERO_SCH_V0.6.1_20260702_page_10.png" alt="Thumbnail" data-v-7d51a79c></div></div></div> <h2 id="pinmap" data-id="PinMap">PinMap</h2> <h3 id="display" data-id="Display">Display</h3> <div class="table-container"><table><thead><tr><th>CM0</th> <th>G10</th> <th>G11</th> <th>G25</th> <th>G8</th> <th>G5</th></tr></thead><tbody><tr><td>ST7789v3</td> <td>MOSI</td> <td>SCLK</td> <td>DC</td> <td>CS</td> <td>TE</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>ST7789v3</th> <th>LCD_RST</th> <th>BL</th></tr></thead><tbody><tr><td>M5IOE1</td> <td>PYG12_LCD_RST</td> <td>PYG10_BL_PWM</td></tr></tbody></table></div><p>The display reset is controlled by <code>PYG12_LCD_RST</code> on the <code>M5IOE1</code> I/O expander, while <code>PYG10_BL_PWM</code> controls the display backlight.</p><h3 id="audio" data-id="Audio">Audio</h3> <div class="table-container"><table><thead><tr><th>CM0</th> <th>G20_I2S_DIN</th> <th>G19_I2S_LRCK</th> <th>G18_I2S_BLCK</th> <th>G21_I2S_DOUT</th> <th>G2_I2C1_SDA</th> <th>G3_I2C1_SCL</th></tr></thead><tbody><tr><td>ES8389(0x10)</td> <td>DOUT</td> <td>LRCK</td> <td>BCLK</td> <td>MCLK/DIN</td> <td>SDA</td> <td>SCL</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>CM0</th> <th>G24</th></tr></thead><tbody><tr><td>AW8737A</td> <td>EN</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>CM0</th> <th>G17</th></tr></thead><tbody><tr><td>3.5mm Headphone</td> <td>HP_DET</td></tr></tbody></table></div><p>The 3.5mm audio input/output jack supports plug detection. When <code>HP_DET</code> detects a headphone plug, the system automatically switches the audio output route. When no headphone is connected, the <strong>AW8737A</strong> speaker amplifier is enabled. The amplifier enable signal is controlled by <strong>GPIO G24 on the CM0</strong>.</p><h3 id="usb-20" data-id="USB 2.0">USB 2.0</h3> <p>CardputerZero expands the CM0's internal USB interface resources via a USB Hub, enabling multiple USB ports and an Ethernet interface.</p><p>A physical Host / Slave toggle switch is located on the left side of the device. When in Slave mode, the USB Hub chip is disconnected; in this state, the left-side USB-A, USB Type-C ports, the HAT-P0/P1 USB interface on the top EXT 2.54-14P expansion bus, and the Ethernet interface will be unavailable.</p><ul><li>Slave mode:<ul><li>CM0 USB is connected to the USB Type-C port on the right side of the device.</li></ul></li> <li>Host mode:<ul><li>CM0 USB is connected to the internal USB Hub, which further expands into 4 USB ports.</li> <li>USB1 from the Hub is routed through a USB-ETH chip to provide Ethernet functionality.</li> <li>USB2 ~ 4 from the Hub are used for the USB-A port, USB Type-C port, and the HAT-P0/P1 USB interface on the top EXT 2.54-14P expansion bus, respectively.</li></ul></li></ul> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/cardputerzero_usb_sch_01.png" width="70%"> <h3 id="hmi" data-id="HMI">HMI</h3> <div class="table-container"><table><thead><tr><th>CM0</th> <th>G2_I2C1_SDA</th> <th>G3_I2C1_SCL</th> <th>G27</th></tr></thead><tbody><tr><td>Keyboard - TCA8418RTWR (0x34)</td> <td>SDA</td> <td>SCL</td> <td>KB_INT</td></tr> <tr><td>IMU - BMI270 (0x68)</td> <td>SDA</td> <td>SCL</td> <td></td></tr> <tr><td>RTC - RX8130CE (0x32)</td> <td>SDA</td> <td>SCL</td> <td></td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>BMI270</th> <th>BMI_SDA</th> <th>BMI_SCL</th></tr></thead><tbody><tr><td>BMM150 (0x10)</td> <td>SDA</td> <td>SCL</td></tr></tbody></table></div><h3 id="power-control" data-id="Power Control">Power Control</h3> <div class="table-container"><table><thead><tr><th>CM0</th> <th>G4</th></tr></thead><tbody><tr><td>GROVE_FUNC_SW</td> <td>I2C/UART_SW</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>CM0</th> <th>G6</th></tr></thead><tbody><tr><td>SWITCH</td> <td>SW_DET</td></tr></tbody></table></div><p><code>G6_SW_DET</code> is used to read the switch detection signal.</p><h3 id="m5ioe1" data-id="M5IOE1">M5IOE1</h3> <div class="table-container"><table><thead><tr><th>CM0</th> <th>G2_I2C1_SDA</th> <th>G3_I2C1_SCL</th> <th>G16</th></tr></thead><tbody><tr><td>M5IOE1 (0x4F)</td> <td>SDA</td> <td>SCL</td> <td>NRST</td></tr></tbody></table></div><ul><li>Power Status</li></ul> <div class="table-container"><table><thead><tr><th>M5IOE1</th> <th>PYG2</th> <th>PYG4</th> <th>PYG5</th> <th>PYG14</th></tr></thead><tbody><tr><td>POWER</td> <td>HW_DET</td> <td>GROVE_EN</td> <td>PWR_DET</td> <td>PWR_EN</td></tr></tbody></table></div><ul><li>Peripheral Reset</li></ul> <div class="table-container"><table><thead><tr><th>M5IOE1</th> <th>PYG3</th> <th>PYG6</th></tr></thead><tbody><tr><td>KEYBOARD & USB_HUB</td> <td>KB_HUB_RST</td> <td></td></tr> <tr><td>MIC</td> <td></td> <td>MIC_SW</td></tr></tbody></table></div><p><code>PYG3_KB_HUB_RST</code> is the shared reset control signal for the <code>TCA8418RTWR</code> keyboard controller and the <code>GL852G-OHY60</code> USB Hub.</p><p><code>PYG6_MIC_SW</code> switches the microphone channel of the 3.5mm TRRS interface between the <code>CTIA / OMTP</code> standards.</p><div class="table-container"><table><thead><tr><th>PYG6_MIC_SW</th> <th>Standard</th></tr></thead><tbody><tr><td>LOW</td> <td>CTIA</td></tr> <tr><td>HIGH</td> <td>OMTP</td></tr></tbody></table></div><ul><li>HAT P0/P1 Function Switch</li></ul> <div class="table-container"><table><thead><tr><th>M5IOE1</th> <th>PYG1</th></tr></thead><tbody><tr><td>SW</td> <td>PYG1_HAT_SW</td></tr></tbody></table></div><div class="table-container"><table><thead><tr><th>M5IOE1</th> <th>PYG13</th></tr></thead><tbody><tr><td>HAT_EN</td> <td>PYG13_HAT_EN</td></tr></tbody></table></div><p><code>PYG13_HAT_EN</code> controls the HAT interface enable state.</p><div class="table-container"><table><thead><tr><th>PYG13_HAT_EN</th> <th>HAT PORT POWER</th></tr></thead><tbody><tr><td>LOW</td> <td>OFF</td></tr> <tr><td>HIGH</td> <td>ON</td></tr></tbody></table></div><ul><li>CAPS LOCKS Indicator LEDs</li></ul> <div class="table-container"><table><thead><tr><th>M5IOE1</th> <th>PYG8</th> <th>PYG9</th> <th>PYG11</th></tr></thead><tbody><tr><td>KEY_LED1</td> <td>SHIFT_LED</td> <td></td> <td></td></tr> <tr><td>KEY_LED2</td> <td></td> <td>FN_LED</td> <td></td></tr> <tr><td>KEY_LED3</td> <td></td> <td></td> <td>SYM_LED</td></tr></tbody></table></div><h3 id="ir-tx--rx" data-id="IR TX  RX">IR TX & RX</h3> <div class="table-container"><table><thead><tr><th>CM0</th> <th>G12</th> <th>G13</th></tr></thead><tbody><tr><td>IR</td> <td>IR_TX</td> <td>IR_RX</td></tr></tbody></table></div><h3 id="hy20-4p" data-id="HY2.0-4P">HY2.0-4P</h3> <div class="grove-table-container"><div class="table-container"><table><thead><tr><th>HY2.0-4P</th> <th>Black</th> <th>Red</th> <th>Yellow</th> <th>White</th></tr></thead><tbody><tr><td>UART / I2C</td> <td>GND</td> <td>5V</td> <td>G14_UART_TXD / G2_I2C1_SDA</td> <td>G15_UART_RXD / G3_I2C1_SCL</td></tr></tbody></table></div></div><p>The HY2.0-4P interface function is switched via <code>G4_I2C/UART_SW</code> on the <code>CM0</code>. The default function is <code>UART</code>.</p><div class="table-container"><table><thead><tr><th>G4_I2C/UART_SW</th> <th>GROVE FUNC</th></tr></thead><tbody><tr><td>LOW</td> <td>UART</td></tr> <tr><td>HIGH</td> <td>I2C1</td></tr></tbody></table></div><p>The 5V output on the interface is enabled via <code>PYG4_GROVE_EN</code> on the <code>M5IOE1</code>. (Maximum supply current &lt; 500mA)</p><h3 id="ext-254-14p" data-id="EXT 2.54-14P">EXT 2.54-14P</h3> <div class="m5-bus-table-container core"><div class="table-container"><table><thead><tr><th>FUNC</th> <th>PIN</th> <th>LEFT</th> <th>RIGHT</th> <th>PIN</th> <th>FUNC</th></tr></thead><tbody><tr><td>USB4_D_P / G26</td> <td>HAT_P0</td> <td>1</td> <td>2</td> <td class="VCC">5VIN</td> <td class="empty"></td></tr> <tr><td>USB4_D_N / G23</td> <td>HAT_P1</td> <td>3</td> <td>4</td> <td class="GND">GND</td> <td class="empty"></td></tr> <tr><td class="empty"></td> <td>G22</td> <td>5</td> <td>6</td> <td class="VCC">5VOUT</td> <td class="empty"></td></tr> <tr><td class="SPI">SPI0_CLK</td> <td>G11</td> <td>7</td> <td>8</td> <td>G2</td> <td class="I2C">I2C1_SDA</td></tr> <tr><td class="SPI">SPI0_MOSI</td> <td>G10</td> <td>9</td> <td>10</td> <td>G3</td> <td class="I2C">I2C1_SCL</td></tr> <tr><td class="SPI">SPI0_MISO</td> <td>G9</td> <td>11</td> <td>12</td> <td>G15</td> <td class="UART">UART_RXD</td></tr> <tr><td class="SPI">SPI0_CS1</td> <td>G7</td> <td>13</td> <td>14</td> <td>G14</td> <td class="UART">UART_TXD</td></tr></tbody></table></div></div><p>The <code>PYG1_HAT_SW</code> pin on the <code>M5IOE1</code> I/O expander switches the <code>HAT_P0</code> and <code>HAT_P1</code> pins between <code>USB / GPIO</code> functions. The default function is <code>GPIO</code>.</p><div class="table-container"><table><thead><tr><th>PYG1_HAT_SW</th> <th>EXT HAT_P0/P1 FUNC</th></tr></thead><tbody><tr><td>LOW</td> <td>GPIO26 / GPIO23</td></tr> <tr><td>HIGH</td> <td>USB Hub - USB4</td></tr></tbody></table></div><h2 id="appearance-stickers" data-id="Appearance Stickers">Appearance Stickers</h2> <ul><li><a target="_blank" href="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/CardputerZero_Labels.zip">CardputerZero Sticker Design Files CDR</a></li></ul> <h2 id="softwares" data-id="Softwares">Softwares</h2> <h3 id="quick-start" data-id="Quick Start">Quick Start</h3> <ul><li><a target="_blank" href="/en/guide/linux/cardputerzero/image">CardputerZero Image Flashing</a></li> <li><a target="_blank" href="/en/guide/linux/cardputerzero/adb">CardputerZero ADB Connection and Debugging</a></li> <li><a target="_blank" href="https://github.com/CardputerZero/Template">CardputerZero Application Development Template</a></li></ul> <h3 id="sdk" data-id="SDK">SDK</h3> <p>coming soon...</p><h3 id="kernel" data-id="Kernel">Kernel</h3> <p>coming soon...</p><h2 id="product-comparison" data-id="Product Comparison">Product Comparison</h2> <div class="compare-table-container"><div class="table-container"><table><thead><tr><th>Product Compare</th> <th><a target="_blank" href="/en/CardputerZero">CardputerZero</a> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1243/C154-CardputerZero-main-pictures_04.jpg" alt="CardputerZero"></th> <th><a href="#todo">CardputerZero-Lite</a> <img src="https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1145/coming-soon.png" alt="CardputerZero-Lite"></th></tr></thead><tbody><tr><td>Core</td> <td>Raspberry Pi CM0</td> <td>Raspberry Pi CM0</td></tr> <tr><td>Wi-Fi & BT</td> <td>✅</td> <td>✅</td></tr> <tr><td>IR Transmitter + Receiver</td> <td>✅</td> <td>✅</td></tr> <tr><td>8MP Camera</td> <td>✅</td> <td>❌</td></tr> <tr><td>IMU BMI270 + BMM150</td> <td>✅</td> <td>❌</td></tr> <tr><td>Includes 32GB microSD</td> <td>✅</td> <td>❌</td></tr></tbody></table></div></div></div> <!----> <!----> <!----></div></div> <div class="docs-layouts-anchor"><div class="page-tools" data-v-39baf185><div class="page-tools-title" data-v-39baf185>Page Tools</div> <div class="page-tools-actions" data-v-39baf185><a href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/CardputerZero.pdf" target="_blank" rel="nofollow noopener noreferrer" title="Download PDF" class="page-tools-action page-tools-pdf" data-v-39baf185><svg viewBox="0 0 24 24" aria-hidden="true" class="page-tools-icon" data-v-39baf185><path d="M6 2h8l4 4v16H6V2zm7 1.8V7h3.2L13 3.8zM8.4 12.2h1.5c1 0 1.7-.6 1.7-1.6S10.9 9 9.9 9H7v6h1.4v-2.8zm0-1.1v-1h1.3c.3 0 .5.2.5.5s-.2.5-.5.5H8.4zm4.1 3.9h1.8c1.7 0 2.8-1.1 2.8-3s-1.1-3-2.8-3h-1.8v6zm1.4-1.2v-3.6h.4c.9 0 1.4.6 1.4 1.8s-.5 1.8-1.4 1.8h-.4zm4.1 1.2h1.4v-2.4h2.1v-1.2h-2.1v-1.2h2.4V9H18v6z" data-v-39baf185></path></svg> <span data-v-39baf185>PDF</span></a> <div class="markdown-action-menu placement-toolbox" data-v-5d6a4f8a data-v-39baf185><button type="button" title="Copy page" class="markdown-action-trigger" data-v-5d6a4f8a><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><rect x="9" y="9" width="13" height="13" rx="2"></rect><path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1"></path></svg> <span data-v-5d6a4f8a>Copy page</span> <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" data-v-5d6a4f8a><polyline points="6 9 12 15 18 9"></polyline></svg></button> <!----></div></div></div></div></div> <footer><div class="footer-container"><div class="footer-content-wrap"><div class="footer-nav"><div class="footer-nav-item"><div data-id="0" class="footer-nav-title"><a class="footer-nav-title-a">
-        About Us
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/about-us">About M5Stack</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?page=1">News</a></li><li class="footer-nav-li"><a href="https://m5stack.com/explore?type=blog&page=1">Blog</a></li><li class="footer-nav-li"><a href="https://m5stack.com/events">Events</a></li><li class="footer-nav-li"><a href="https://m5stack.com/contact">Contact Us</a></li></ul></div><div class="footer-nav-item"><div data-id="1" class="footer-nav-title"><a class="footer-nav-title-a">
-        Where to buy
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/distributor">Distributors</a></li><li class="footer-nav-li"><a href="https://shop.m5stack.com/">Official Store</a></li><li class="footer-nav-li"><a href="https://m5stack.aliexpress.com/store/911661199">AliExpress</a></li><li class="footer-nav-li"><a href="https://www.amazon.com/shops/m5stack">Amazon</a></li><li class="footer-nav-li"><a href="https://m5stack.taobao.com/">Taobao</a></li></ul></div><div class="footer-nav-item"><div data-id="2" class="footer-nav-title"><a class="footer-nav-title-a">
-        Solution
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://m5stack.com/business">For Business</a></li><li class="footer-nav-li"><a href="https://m5stack.com/developers">For Developers</a></li></ul></div><div class="footer-nav-item"><div data-id="3" class="footer-nav-title"><a class="footer-nav-title-a">
-        Software
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="https://flow.m5stack.com/">UiFlow1</a></li><li class="footer-nav-li"><a href="https://uiflow2.m5stack.com/">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/uiflow/m5burner/intro">M5Burner</a></li><li class="footer-nav-li"><a href="https://block-designer.m5stack.com/">Block Designer</a></li><li class="footer-nav-li"><a href="/en/guide/ezdata/ezdata_v2">EzData 2.0</a></li><li class="footer-nav-li"><a href="/en/guide/easyloader/easyloader_packer">EasyLoader Packer</a></li><li class="footer-nav-li"><a href="/en/guide/develop_tools/vlw_font_creator">VLW Font Creator</a></li><li class="footer-nav-li"><a href="/en/download">Device USB Driver</a></li></ul></div><div class="footer-nav-item"><div data-id="4" class="footer-nav-title"><a class="footer-nav-title-a">
-        Documentation
-      </a> <!----></div> <ul class="footer-nav-ul"><li class="footer-nav-li"><a href="/en/products">Product Documents</a></li><li class="footer-nav-li"><a href="/en/uiflow/uiflow_web">UiFlow1</a></li><li class="footer-nav-li"><a href="/en/uiflow2/uiflow_web">UiFlow2</a></li><li class="footer-nav-li"><a href="/en/arduino/arduino_ide">Arduino</a></li><li class="footer-nav-li"><a href="/en/esp_idf/esp_idf">ESP-IDF</a></li><li class="footer-nav-li"><a href="/en/stackflow/overview">StackFlow AI</a></li><li class="footer-nav-li"><a href="/en/homeassistant/overview">Home Assistant</a></li><li class="footer-nav-li"><a href="https://github.com/nanoframework/nanoFramework.M5Stack">nanoFramework</a></li><li class="footer-nav-li"><a href="/en/guide/product_guide">Product Guide</a></li><li class="footer-nav-li"><a href="/en/certification">Product Certifications</a></li><li class="footer-nav-li"><a href="/en/product_i2c_addr">I2C Table</a></li><li class="footer-nav-li"><a href="/en/products_selector/m5core_compare">Product Selector</a></li><li class="footer-nav-li"><a href="https://github.com/m5stack/M5_Hardware">Hardware Design Files</a></li><li class="footer-nav-li"><a href="/en/history">Release History</a></li><li class="footer-nav-li"><a href="/en/compatible_stack">Stack Compatibility</a></li><li class="footer-nav-li"><a href="/en/learn/extension/module">Stack Screw Length</a></li></ul></div></div> <div class="footer-right"><div class="footer-email-group"><p class="footer-email-title">
-              Stay in the Loop
-            </p> <p class="footer-email-desc">
-              Weekly updates on new products, innovations, and announcements.
-            </p> <div class="footer-email-input"><input placeholder="Enter Email address" autocomplete="off" class="email-input"> <button type="button" class="subscribe-btn">
-                Subscribe
-              </button></div> <p class="footer-email-warning" style="display:none">
-              Email is invalid!
-            </p></div> <div class="footer-email-success" style="display:none">
-            Thanks for subscribing
-          </div> <div class="footer-follow"><div class="footer-follow-ul"><a href="https://x.com/M5Stack"><img src="/assets/footer/sociallist10.svg" alt></a><a href="https://www.linkedin.com/company/m5stack"><img src="/assets/footer/sociallist2.svg" alt></a><a href="https://www.instagram.com/m5stack"><img src="/assets/footer/sociallist8.svg" alt></a><a href="https://www.facebook.com/M5Stack"><img src="/assets/footer/sociallist7.svg" alt></a><a href="https://www.youtube.com/m5stack"><img src="/assets/footer/sociallist5.svg" alt></a><a href="https://www.tiktok.com/@m5stack"><img src="/assets/footer/tiktok.svg" alt></a><a href="https://www.hackster.io/m5stack"><img src="/assets/footer/sociallist3.svg" alt></a><a href="https://discord.gg/ysQAWBUE9Q"><img src="/assets/footer/sociallist4.svg" alt></a><a href="https://github.com/m5stack"><img src="/assets/footer/sociallist6.svg" alt></a></div></div> <div class="footer-info-wrapper"><div class="footer-info">
-            M5Stack Technology Co., Ltd
-          </div> <div class="footer-address-info">
-            Address: 
-             Block A10, Expo Bay South Coast, Fuhai Street, Bao'an District, Shenzhen, China
-          </div> <div class="footer-info">
-            TEL: 
-            +86 755 8657 5379
-          </div> <div class="footer-info">
-            Email: 
-            support@m5stack.com
-          </div></div></div></div></div> <div class="footer-bottom"><div class="footer-bottom-content"><div class="footer-copy">
-        Copyright ©
-        <a href="https://m5stack.com/">M5Stack Technology Co., Ltd.</a>
-        All rights reserved.
-      </div> <div class="terms-box"><!----> <a href="https://shop.m5stack.com/policies/privacy-policy">Privacy Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/terms-of-service">Terms of Service</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/shipping-policy">Shipping Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/policies/refund-policy">Refund Policy</a><span class="terms-sep">|</span> <a href="https://shop.m5stack.com/pages/payment-method">Payment Method</a></div> <div class="beian"><a href="https://beian.miit.gov.cn/">粤ICP备16010631号</a></div></div></div> <!----></footer> <div class="float-icon-container"><div class="totop-icon"><svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 280 280" xmlns:xlink="http://www.w3.org/1999/xlink" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M143 70l58 69c1,1 1,3 1,4 -1,1 -2,2 -4,2l-20 0c-2,0 -4,2 -4,4l1 57c0,2 -2,4 -4,4l-62 0c-2,0 -4,-2 -4,-4l1 -57c0,-2 -2,-4 -4,-4l-20 0c-2,0 -3,-1 -4,-2 -1,-1 0,-3 1,-4l58 -69c1,-1 2,-1 3,-1 1,0 2,1 3,1z" class="fil1"></path></g></svg></div> <div class="menu-icon" style="display:none"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" width="800px" height="800px" version="1.1" viewBox="0 0 800 800" style="shape-rendering:geometricPrecision;text-rendering:geometricPrecision;image-rendering:optimizeQuality;fill-rule:evenodd;clip-rule:evenodd"><g id="图层_x0020_1"><metadata id="CorelCorpID_0Corel-Layer"></metadata> <path d="M253 229l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 370l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path> <path d="M253 511l293 0c17,0 30,14 30,30l0 0c0,17 -14,30 -30,30l-293 0c-17,0 -30,-14 -30,-30l0 0c0,-17 14,-30 30,-30z" class="fil2"></path></g></svg></div></div></div></div></div></div><script defer src="/_nuxt/static/1788504562/en/CardputerZero/state.js"></script><script src="/_nuxt/41d5c62.js" defer></script><script src="/_nuxt/c970150.js" defer></script><script src="/_nuxt/5a34d22.js" defer></script><script src="/_nuxt/a352c6d.js" defer></script><script src="/_nuxt/b9c4bc6.js" defer></script>
-  </body>
-</html>
diff --git a/devices/m5stack/cardputer-zero/certification-and-compliance.md b/devices/m5stack/cardputer-zero/certification-and-compliance.md
deleted file mode 100644
index b09a889..0000000
--- a/devices/m5stack/cardputer-zero/certification-and-compliance.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Certification and compliance — cardputer-zero
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-⚠ **No FCC grant found, and no such product in M5Stack's own store.** See §4.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/cardputer-zero/market-and-pricing.md b/devices/m5stack/cardputer-zero/market-and-pricing.md
deleted file mode 100644
index 7974ccc..0000000
--- a/devices/m5stack/cardputer-zero/market-and-pricing.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Market and pricing — cardputer-zero
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-**None — the product was not found in the vendor's catalogue.** See the normalisation note below.
-
-### Normalisation and caveats
-
-⚠ **No product matching 'Cardputer Zero' exists in M5Stack's store.** The full catalogue (664 products, all three `/products.json` pages) was searched for `zero`, `cardputer.?zero` and `cardputer`. 14 Cardputer-family products matched; **none is a 'Zero'.** Combined with the absence of any FCC grant, this record's subject may be misnamed or unreleased.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/dinmeter-v1.1/README.md b/devices/m5stack/dinmeter-v1.1/README.md
deleted file mode 100644
index e17f63e..0000000
--- a/devices/m5stack/dinmeter-v1.1/README.md
+++ /dev/null
@@ -1,219 +0,0 @@
-# M5Stack DinMeter v1.1 (SKU K134-V11)
-
-> **Product ID** `K134-V11` · **Announced** 2026-01-30 · **Status** current, in stock at
-> USD 24.50 (2026-09-04) · **Research retrieval date** 2026-09-04
-
-**This is a scoped revision record, not a duplicate.** The DinMeter v1.1 is the original
-[DinMeter (K134)](../dinmeter/README.md) carrier board with a different core module soldered on
-it. Everything the two share — pinouts, buses, power tree, feature guides, development
-workflow, factory firmware, mechanical envelope — lives in the K134 record and is **not
-repeated here**. This document covers only what is actually different, and the evidence for why
-the list is that short.
-
----
-
-## Why not a second full record
-
-M5Stack publishes the following under v1.1 names:
-
-| Asset | v1.1 URL / path | SHA-256 | Same as v1.0? |
-|---|---|---|---|
-| Schematic PDF | `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf` | `03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070` | **byte-identical** |
-| Structure model | `m5stack/M5_Hardware` → `Products/K134-V11_DinMeter_v1.1/Structures/DinMeter_v1.1.stl` | `90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7` | **byte-identical** |
-| Dimension drawing | `.../1211/K134-din_meter_asm_v1.pdf` | `db42c8a995b6d0bf…` | **same file, same URL** as v1.0 |
-| GPIO PinMap | v1.1 doc page | — | **identical assignments** |
-
-Note the v1.1 schematic's own filename: `K134-V11_DIN_Meter_**v1.0**_2025_11_25…`. Even the
-name says v1.0.
-
-So the carrier PCB documentation **has not been revised**. Writing a second full record would
-require asserting board-level differences that no published document supports. See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) for what that does and does not license us to
-conclude.
-
----
-
-## The change
-
-| | DinMeter (K134) | DinMeter v1.1 (K134-V11) |
-|---|---|---|
-| Core module | [**Stamp-S3**](../../../components/m5stack/stamp-s3/README.md) (`S007`) | [**Stamp-S3A**](../../../components/m5stack/stamp-s3a/README.md) (`S007-V033`) |
-| Display controller (per docs) | **ST7789V2** | **ST7789P3** |
-| Package size | 136.0 × 93.0 × 23.0 mm | 136.0 × 95.0 × 24.0 mm |
-| Gross weight | 47.0 g | 44.9 g |
-| Bundle | adhesive tape, 250 mAh cell, sticker, DC-JACK terminal, back bracket | 250 mAh cell, **2.54-2P terminal**, **plastic back clip**, adhesive tape, **pin sticker** |
-| Everything electrical | — | **unchanged** |
-
-The vendor's own "Product Comparison" table on the v1.1 page has exactly **one** row:
-*Main Controller — Stamp-S3A vs Stamp-S3*. It does not mention the display controller.
-
-### 1. Stamp-S3 → Stamp-S3A
-
-Fully documented, from both schematics, at
-[`components/m5stack/stamp-s3a/README.md`](../../../components/m5stack/stamp-s3a/README.md).
-Summary of what a DinMeter owner actually experiences:
-
-| Aspect | Effect on DinMeter v1.1 |
-|---|---|
-| **Sleep current** | `VIN_5V` sleep drops 310.89 µA → **6.84 µA** (vendor figures, method unstated). The most useful change for a battery-backed panel meter |
-| **Standby current** | 33.5 mA → **25.5 mA** |
-| **RGB LED** | ⚠ **Requires `GPIO38 = HIGH` before it will light.** See below |
-| **Antenna** | Rebuilt matching network; vendor claims better reception, publishes no figure |
-| **Regulator** | µPOL module → discrete buck + external 2.2 µH inductor |
-| **GPIO map** | **Unchanged** |
-| **PSRAM / flash** | **Unchanged** — ESP32-S3FN8, 8 MB flash, no PSRAM, on both |
-| **Firmware source compatibility** | **Compatible**, except RGB LED |
-
-> #### ⚠ The RGB LED will not light with stock M5Unified
->
-> On Stamp-S3A the WS2812B-2020's supply comes from `BL_3V3`, gated by an AW35122FDR load switch
-> whose enable is ESP32-S3 **GPIO38**. On Stamp-S3 the LED was on the always-on `VDD_3V3`.
->
-> M5Unified (master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`, 2026-09-04) maps
-> `board_M5DinMeter → GPIO_NUM_21` for the RGB LED (`src/M5Unified.cpp:246`) and contains **no
-> GPIO38 enable step for any board**. There is no `board_M5DinMeter_v11` and no
-> `board_M5StampS3A` enum. A v1.1 unit therefore identifies as `board_M5DinMeter` and the LED
-> path is missing its power-enable.
->
-> **Status: `inferred` — predicted from vendor documentation + schematic + source read. Not
-> reproduced on hardware.** Workaround (`not-tested`):
-> ```cpp
-> pinMode(38, OUTPUT); digitalWrite(38, HIGH); delay(1);   // then drive GPIO21 as usual
-> ```
-
-### 2. ST7789V2 → ST7789P3
-
-| Source | v1.0 | v1.1 |
-|---|---|---|
-| Features list | "ST7789v2 screen" | "**ST7789P3** display" |
-| Specification row *Display Driver* | `ST7789V2` | `ST7789P3` |
-| PinMap section heading | `ST7789V2` | `ST7789P3` |
-| *Datasheets* section | links `ST7789V2_SPEC_V1.0.pdf` | **no display datasheet at all** |
-| Product Comparison table | — | **does not mention the display** |
-
-The change is real in the documentation and consistent across three places on the page. But
-M5Stack **withdrew the datasheet link** rather than replacing it, publishes no ST7789P3
-document, and did not list the display in its own comparison table. The pin assignments
-(CS G7, SCK G6, RS G4, MOSI G5, RESET G8, BL G9) and the resolution (135 × 240) are identical.
-
-Practically: both are Sitronix ST7789-family SPI TFT controllers with the same command set for
-everything an application does. M5GFX/LovyanGFX drives both through its ST7789 panel class;
-M5Unified's `board_M5DinMeter` display path is unchanged. **No API difference is expected**, and
-none was found. → [`components/sitronix/st7789p3/README.md`](../../../components/sitronix/st7789p3/README.md)
-
-### 3. Packaging and bundle
-
-The v1.1 box is 2 mm wider and 1 mm taller but 2.1 g lighter, and the accessory list changed:
-the "DC-JACK terminal input (6-36V)" became a "2.54-2P Terminal", the "back bracket" became a
-"plastic back clip", and a "pin sticker" replaced the "silk-screened sticker". Cosmetic/logistics
-changes with no electrical meaning. **[DOC]**
-
----
-
-## Identity and variants
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketed name | **DinMeter v1.1** | docs page title, 2026-09-04 |
-| SKU | **`K134-V11`** | docs page header; shop variant `sku: "K134-V11"` |
-| Documentation | <https://docs.m5stack.com/en/core/DinMeter_v1.1> (HTTP 200) | verified 2026-09-04 |
-| Shop listing | <https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a> | HTTP 200 |
-| Shop product id / variant id | `9014041182465` / `47570426593537` | `…/…​.js` JSON |
-| Created / published | `2026-01-30T10:02:16+08:00` / `2026-01-30T12:30:47+08:00` | shop JSON |
-| Tags | `ESP32-S3`, `STAMP` | shop JSON |
-| Shipping weight | 70 g | shop JSON |
-| Price | **USD 24.50**, in stock | shop JSON, 2026-09-04 |
-| Regional variants | none found | — |
-
----
-
-## Key specifications (v1.1 page, where they differ from v1.0)
-
-Identical to v1.0 except as noted:
-
-| Specification | v1.1 value | Same as v1.0? |
-|---|---|---|
-| SoC | ESP32-S3FN8 @ 240 MHz | ✔ |
-| Flash | 8 MB | ✔ |
-| PSRAM | none | ✔ |
-| Display driver | **ST7789P3** | ✘ (was ST7789V2) |
-| Resolution | 135 × 240 | ✔ |
-| DC input | 6 – 36 V | ✔ |
-| Charging current | 100 mA | ✔ |
-| Grove load | PORT.A 5 V @ 220 mA, PORT.B 5 V @ 220 mA | ✔ |
-| Standby current (battery) | DC 4.2 V @ 38.4 µA | ✔ — **note:** unchanged despite the module's much lower sleep current, because the board latches the battery *off* rather than sleeping |
-| Battery socket | 1.25 mm-2P | ✔ |
-| Operating temp | 0 – 40 °C | ✔ |
-| Product size / weight | 53.0 × 30.0 × 32.0 mm / 17.8 g | ✔ |
-| Package size / gross | 136.0 × 95.0 × 24.0 mm / 44.9 g | ✘ |
-
-The unchanged 38.4 µA standby figure is worth pausing on: it is quoted identically on both
-pages, which is consistent with it being a *board* measurement dominated by the latch circuit
-rather than by the module. **[INF]**
-
----
-
-## New in the v1.1 documentation
-
-The v1.1 page carries three "Learn" sections the v1.0 page does not, all of which are useful
-and all of which apply to v1.0 too except the last:
-
-- **Power On/Off** — reworded but equivalent: wake by WAKE button or RTC IRQ; firmware must set
-  HOLD (GPIO46) high during init; power off with RST or `GPIO46 = 0`.
-- **Download Mode** — hold `G0` on the Stamp-S3A before power-up.
-- **RGB LED Power Supply** — **new and v1.1-specific.** The GPIO38 requirement, quoted in full
-  in [`components/m5stack/stamp-s3a/README.md` §3](../../../components/m5stack/stamp-s3a/README.md#3-change-1--the-rgb-led-is-no-longer-always-powered-firmware-visible).
-
----
-
-## Everything else
-
-| Topic | Where |
-|---|---|
-| Full GPIO map, buses, power tree, designator census | [`../dinmeter/pinouts-and-buses.md`](../dinmeter/pinouts-and-buses.md) |
-| Arduino / ESP-IDF / UiFlow2 / MicroPython | [`../dinmeter/development.md`](../dinmeter/development.md) |
-| Feature guides (encoder, display, RTC, buzzer, power, Grove, Wi-Fi/BLE, mounting, RGB) | [`../dinmeter/features/`](../dinmeter/features/README.md) |
-| Factory firmware and restore | [`../dinmeter/factory-firmware.md`](../dinmeter/factory-firmware.md) |
-| Projects and community | [`../dinmeter/projects-and-community.md`](../dinmeter/projects-and-community.md) |
-| Comparisons (Waveshare knob, M5Dial, DIY) | [`../dinmeter/comparisons-and-recommendations.md`](../dinmeter/comparisons-and-recommendations.md) |
-| Coverage, resources/conflicts, compatibility | [`../dinmeter/coverage.md`](../dinmeter/coverage.md), [`../dinmeter/resources-and-conflicts.md`](../dinmeter/resources-and-conflicts.md), [`../dinmeter/compatibility-and-status.md`](../dinmeter/compatibility-and-status.md) |
-| Research log, commands, sources | [`../dinmeter/research-log.md`](../dinmeter/research-log.md), [`../dinmeter/commands.md`](../dinmeter/commands.md), [`../dinmeter/sources.md`](../dinmeter/sources.md) |
-| Media provenance | [`../dinmeter/media.md`](../dinmeter/media.md) |
-| **v1.1-specific conflicts** | [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-| **v1.1-specific pricing** | [`market-and-pricing.md`](market-and-pricing.md) |
-| **v1.1-specific sources** | [`sources.md`](sources.md) |
-
----
-
-## Artifact layout
-
-```
-devices/m5stack/dinmeter-v1.1/artifacts/
-├── schematic/
-│   └── K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf   433 658 B  03ec3353…
-│       ^ deliberately retained despite being byte-identical to the v1.0 file:
-│         the duplication under two URLs and two filenames IS the finding
-├── mechanical/
-│   └── DinMeter_v1.1.stl                                           573 284 B  90f04d6a…
-│       ^ likewise byte-identical to DinMeter.stl
-└── docs/
-    ├── docs-en-core-DinMeter_v1.1.pdf → archive/…               11 261 000 B  617a9ea8…
-    ├── docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.md                 placeholder
-    └── docs-en-core-DinMeter_v1.1.txt                               6 438 B   page text
-```
-
-**Intentional duplication, recorded:** ~1.0 MB is byte-identical to files under
-`devices/m5stack/dinmeter/artifacts/`. Deduplicating would destroy the evidence that M5Stack
-published the same bytes twice. The documentation PDF, by contrast, is genuinely different
-content.
-
-## Components fitted (deltas only)
-
-| Function | v1.1 part | Record |
-|---|---|---|
-| Core module | **Stamp-S3A** `S007-V033` | [`components/m5stack/stamp-s3a`](../../../components/m5stack/stamp-s3a/README.md) |
-| Display controller | **ST7789P3** | [`components/sitronix/st7789p3`](../../../components/sitronix/st7789p3/README.md) |
-
-All other fitted parts are as listed in the
-[K134 key-specification table](../dinmeter/README.md#key-specifications) — same schematic, same
-BOM as far as anything published shows.
diff --git a/devices/m5stack/dinmeter-v1.1/acquisition/README.md b/devices/m5stack/dinmeter-v1.1/acquisition/README.md
deleted file mode 100644
index 3c02e45..0000000
--- a/devices/m5stack/dinmeter-v1.1/acquisition/README.md
+++ /dev/null
@@ -1,114 +0,0 @@
-# DinMeter v1.1 — acquisition
-
-Machine-readable form: [`manifest.json`](manifest.json). Component artifacts (the Stamp-S3A
-schematic, dimensions, STL, pin map) and all shared-carrier artifacts are manifested in
-[`../../dinmeter/acquisition/`](../../dinmeter/acquisition/README.md).
-
-**All 8 downloads returned HTTP 200 on 2026-09-04 and validated by magic bytes. Zero failures.**
-
----
-
-## 0. Prerequisites
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-GH="$(gh auth token)"
-```
-
-## 1. v1.1 documents
-
-```bash
-cd devices/m5stack/dinmeter-v1.1/artifacts
-
-curl -fSL -A "$UA" -o schematic/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf \
-  'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf'
-# expect 433658 B, sha256 03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070
-#   ^ IDENTICAL to the v1.0 schematic. Verify this - it is one of the record's key findings.
-
-curl -fSL -o mechanical/DinMeter_v1.1.stl \
-  'https://raw.githubusercontent.com/m5stack/M5_Hardware/a240115c94b19ecf647f229c47fa9a8ce46ccdc4/Products/K134-V11_DinMeter_v1.1/Structures/DinMeter_v1.1.stl'
-# expect 573284 B, sha256 90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7
-#   ^ IDENTICAL to DinMeter.stl.
-
-curl -fSL -A "$UA" -o docs/docs-en-core-DinMeter_v1.1.pdf \
-  'https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/DinMeter_v1.1.pdf'
-# expect 11261000 B, sha256 617a9ea8039ed1fced04cf68de4e12ccd1759140f5f440778b0638b2cc811b46
-#   ^ ARCHIVED for size; the placeholder in docs/ holds the recovery URLs. Genuinely v1.1 content.
-```
-
-**Validate before trusting:**
-```bash
-python3 -c "
-import sys
-for f in sys.argv[1:]:
-    m=open(f,'rb').read(5); print('OK ' if m==b'%PDF-' else 'BAD', f)" schematic/*.pdf docs/*.pdf
-```
-
-## 2. Reproducing the byte-identity findings
-
-Two commands establish three of this record's central conclusions. **Run them.**
-
-```bash
-sha256sum schematic/K134-V11_*.pdf ../../dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf
-sha256sum mechanical/DinMeter_v1.1.stl ../../dinmeter/artifacts/mechanical/DinMeter.stl
-```
-Both pairs must match. If a future fetch produces *different* hashes, M5Stack has finally
-published v1.1-specific assets — which would be a significant change, and this record should be
-revised.
-
-## 3. Media
-
-One WebP from the docs CDN and four images from the shop listing.
-
-> **⚠ The four shop URLs end `.webp` but the CDN serves JPEG.** Shopify content-negotiates the
-> format and ignores the path extension. They are stored locally as `.jpg` so the extension
-> matches the content; the URLs in the manifest are exactly as served.
->
-> **Validate by magic bytes, never by URL suffix.**
-
-```bash
-python3 - <<'EOF'
-import json,urllib.request,hashlib,os
-m=json.load(open('../media/manifest.json'))
-for im in m['images']:
-    p=os.path.join('..',im['local_path'])
-    urllib.request.urlretrieve(im['direct_url'], p)
-    b=open(p,'rb').read()
-    ok = (b[:4]==b'RIFF' and b[8:12]==b'WEBP') or b[:3]==b'\xff\xd8\xff'
-    assert ok, ('bad magic', p, b[:8])
-    print('sha match' if hashlib.sha256(b).hexdigest()==im['sha256'] else 'HASH DIFFERS', p)
-EOF
-```
-Shopify serves through a mutable CDN with a `?v=` cache-buster; a hash change there is expected
-over time and is **not** the same kind of signal as §2.
-
-## 4. Not acquired
-
-| Artifact | Why | Reacquisition |
-|---|---|---|
-| **A v1.1-specific schematic** | **Does not exist.** M5Stack serves the v1.0 file | **lost** |
-| **A v1.1-specific STL or footprint** | Does not exist | **lost** |
-| **ST7789P3 datasheet** | Not published by Sitronix or any mirror; M5Stack removed the display datasheet link rather than replacing it | **lost** |
-| **Stamp-S3A `U4` part number** | Not printed on the schematic, not stated on any page | **lost** |
-| **v1.1 factory-firmware binary** | M5Burner only; no stable URL | **manual** |
-| **UiFlow2 firmware binary** | Same | **manual** |
-| **Gerbers / PCB / BOM** | M5Stack publishes schematics and STLs only | **blocked** |
-
-## 5. Verify
-
-```bash
-cd devices/m5stack/dinmeter-v1.1
-python3 - <<'EOF'
-import json,hashlib,os
-m=json.load(open('acquisition/manifest.json')); bad=0
-for a in m['artifacts']:
-    p=a['destination'].replace('devices/m5stack/dinmeter-v1.1/','')
-    if a['disposition']=='archive':
-        print('skip (archived; placeholder holds the hash):', p); continue
-    if not os.path.exists(p): print('MISSING', p); bad+=1; continue
-    got=hashlib.sha256(open(p,'rb').read()).hexdigest()
-    if a['expected_sha256'] and got!=a['expected_sha256']: print('HASH MISMATCH', p); bad+=1
-print('failures:', bad)
-EOF
-```
-`not-tested` from a clean clone.
diff --git a/devices/m5stack/dinmeter-v1.1/acquisition/manifest.json b/devices/m5stack/dinmeter-v1.1/acquisition/manifest.json
deleted file mode 100644
index 106e1a6..0000000
--- a/devices/m5stack/dinmeter-v1.1/acquisition/manifest.json
+++ /dev/null
@@ -1,200 +0,0 @@
-{
- "$schema-note": "Acquisition manifest for devices/m5stack/dinmeter-v1.1. Component and shared-carrier artifacts are manifested in devices/m5stack/dinmeter/acquisition/manifest.json.",
- "device": "m5stack/dinmeter-v1.1",
- "generated": "2026-09-04",
- "retrieval_agent": "curl 8.x with a Chrome-131 User-Agent for m5stack.com and cdn.shopify.com; gh auth token for api.github.com",
- "artifacts": [
-  {
-   "id": "V-A-01",
-   "kind": "schematic",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf",
-   "expected_sha256": "03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070",
-   "expected_bytes": 433658,
-   "destination": "devices/m5stack/dinmeter-v1.1/artifacts/schematic/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "filename says v1.0; no revision date printed inside",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "BYTE-IDENTICAL to devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf (03ec3353...). Retained deliberately: the duplication under two URLs and two filenames IS the finding. Validated %PDF."
-  },
-  {
-   "id": "V-A-02",
-   "kind": "cad",
-   "url": "https://raw.githubusercontent.com/m5stack/M5_Hardware/a240115c94b19ecf647f229c47fa9a8ce46ccdc4/Products/K134-V11_DinMeter_v1.1/Structures/DinMeter_v1.1.stl",
-   "expected_sha256": "90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7",
-   "expected_bytes": 573284,
-   "destination": "devices/m5stack/dinmeter-v1.1/artifacts/mechanical/DinMeter_v1.1.stl",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "repo HEAD a240115c94b19ecf647f229c47fa9a8ce46ccdc4 (2026-08-17)",
-   "license": "unknown - m5stack/M5_Hardware has no LICENSE file (checked 2026-09-04)",
-   "license_evidence": "absence of LICENSE at the pinned commit",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/m5stack/M5_Hardware",
-   "commit": "a240115c94b19ecf647f229c47fa9a8ce46ccdc4",
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "BYTE-IDENTICAL to DinMeter.stl (90f04d6a...). Retained deliberately, same reason as V-A-01."
-  },
-  {
-   "id": "V-A-03",
-   "kind": "documentation",
-   "url": "https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/DinMeter_v1.1.pdf",
-   "expected_sha256": "617a9ea8039ed1fced04cf68de4e12ccd1759140f5f440778b0638b2cc811b46",
-   "expected_bytes": 11261000,
-   "destination": "devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unversioned; the server re-renders per request",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "archive",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [
-    "https://docs.m5stack.com/en/core/DinMeter_v1.1 (Page Tools -> PDF)"
-   ],
-   "reacquisition": "automatic",
-   "notes": "ARCHIVED for size (11.3 MB). Placeholder at the same path carries the hash and recovery URLs. GENUINELY v1.1-specific content, unlike V-A-01/02."
-  },
-  {
-   "id": "V-A-04",
-   "kind": "derived",
-   "url": null,
-   "expected_sha256": "a2c9954b3ebfb0f87d8e249f4ccfa7dc7764758210f774abb55b7181cf1475c2",
-   "expected_bytes": 6438,
-   "destination": "devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.txt",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "captured 2026-09-04",
-   "license": "derived work of the v1.1 product page",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [],
-   "reacquisition": "manual",
-   "notes": "Text extraction of the v1.1 product page - the source of the ST7789P3 naming, the GPIO38 note and the specification table."
-  },
-  {
-   "id": "V-A-05-01",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-   "expected_sha256": "82916ce50a40391698e3f15e57c2effe21ffcd81324601fec53e4a1459f7276f",
-   "expected_bytes": 24884,
-   "destination": "devices/m5stack/dinmeter-v1.1/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - no Last-Modified returned",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Validated by magic bytes. Not visually rendered in this pass."
-  },
-  {
-   "id": "V-A-05-02",
-   "kind": "image",
-   "url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.webp?v=1769738162",
-   "expected_sha256": "c70624568aba92dcb4b006495dd7d895fa2b202b8db7f32c474b1cc0cec0c1e0",
-   "expected_bytes": 82773,
-   "destination": "devices/m5stack/dinmeter-v1.1/media/shop-1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.jpg",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - no Last-Modified returned",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-  },
-  {
-   "id": "V-A-05-03",
-   "kind": "image",
-   "url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/4_65d27f99-973d-475b-97ef-db7c49e92619.webp?v=1769738162",
-   "expected_sha256": "40b2c4d3b9f960b1466ae1e8b80d81f5e5d7ce1a0f61941b2304193aa30e6e9c",
-   "expected_bytes": 239490,
-   "destination": "devices/m5stack/dinmeter-v1.1/media/shop-4_65d27f99-973d-475b-97ef-db7c49e92619.jpg",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - no Last-Modified returned",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-  },
-  {
-   "id": "V-A-05-04",
-   "kind": "image",
-   "url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.webp?v=1770110459",
-   "expected_sha256": "7a57a9b3cafea316a45621a1957cd3cc8fd229fbc3d6378d581f06880f179b02",
-   "expected_bytes": 58714,
-   "destination": "devices/m5stack/dinmeter-v1.1/media/shop-6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.jpg",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - no Last-Modified returned",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-  },
-  {
-   "id": "V-A-05-05",
-   "kind": "image",
-   "url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/9_8ec2f1c1-19bc-482b-851b-580bd9d86244.webp?v=1770110459",
-   "expected_sha256": "6d4df52a29ff2a347780772a968be8de494a0e021b08652ae021f423c1e30936",
-   "expected_bytes": 64105,
-   "destination": "devices/m5stack/dinmeter-v1.1/media/shop-9_8ec2f1c1-19bc-482b-851b-580bd9d86244.jpg",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - no Last-Modified returned",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-  }
- ],
- "counts": {
-  "total": 9,
-  "downloaded": 8,
-  "derived_locally": 1,
-  "archived": 1,
-  "failed_downloads": 0,
-  "byte_identical_to_v1_0": 2,
-  "bytes_in_repo": 1483346,
-  "bytes_archived": 11261000
- }
-}
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf b/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf
deleted file mode 120000
index 516e0dc..0000000
--- a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.link b/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.link
deleted file mode 120000
index b88d97f..0000000
--- a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-docs-en-core-DinMeter_v1.1.pdf
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.md b/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.md
deleted file mode 100644
index 1d90ede..0000000
--- a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# ARCHIVED — `docs-en-core-DinMeter_v1.1.pdf`
-
-Printable export of the official M5Stack **DinMeter v1.1 (SKU K134-V11)** product
-documentation page.
-
-| Field | Value |
-|---|---|
-| Original repository path | `devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf` |
-| Archived to | `archive/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf` |
-| SHA-256 | `617a9ea8039ed1fced04cf68de4e12ccd1759140f5f440778b0638b2cc811b46` |
-| Byte size | 11 261 000 |
-| Media type | PDF (validated: `%PDF` magic, parsed with pdfminer.six 20260107) |
-| Retrieved | 2026-09-04 |
-| Upstream version/date | **Not versioned.** Page first published 2026-01-30 (shop listing `created_at`); capture reflects the page as served 2026-09-04 |
-| Publisher | M5Stack Technology Co., Ltd |
-| Licence | **unknown** — vendor copyright asserted, no licence grant |
-| Redistribution status | `unknown` |
-| Disposition | `repository` → archived for size |
-| Why moved | Size (11.3 MB, almost entirely product photography). All text is extracted into the sibling `docs-en-core-DinMeter_v1.1.txt` (retained) and into [`../../README.md`](../../README.md). |
-| Reproducible? | Content yes, bytes no — server re-renders per request |
-| Reacquisition | `automatic` |
-
-## Reacquisition
-
-1. **Vendor CDN, direct:**
-   ```bash
-   curl -fSL -o docs-en-core-DinMeter_v1.1.pdf \
-     'https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/DinMeter_v1.1.pdf'
-   ```
-2. **Rendered page:** <https://docs.m5stack.com/en/core/DinMeter_v1.1> (HTTP 200, 2026-09-04) → *Page Tools → PDF*.
-3. **Internet Archive:** no confirmed capture; use `https://web.archive.org/save/https://docs.m5stack.com/en/core/DinMeter_v1.1`.
-
-## Note on the v1.0/v1.1 asset pair
-
-The v1.1 documentation page links a *schematic* PDF at
-`https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf`
-that is **byte-identical** (SHA-256 `03ec3353…`) to the v1.0 schematic served from
-`.../500/DIN_Meter_v1.0.pdf`. The two `.stl` structure files are byte-identical too. See
-[`../../gaps-and-conflicts.md`](../../gaps-and-conflicts.md). This archived *documentation*
-PDF, by contrast, is genuinely v1.1-specific content.
-
-## Also see
-
-- [`../../acquisition/manifest.json`](../../acquisition/manifest.json)
-- v1.0 counterpart: [`devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.md`](../../../dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.md)
diff --git a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.txt b/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.txt
deleted file mode 100644
index 28a8aad..0000000
--- a/devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.txt
+++ /dev/null
@@ -1,294 +0,0 @@
-id="document" class="header-nav-item">Documentation 
- About Us 
- Contact 
- English
- English
- 简体中文
- 日本語
- CONTENTS
- 
- 
- No Results Found
- Hot Searches
- Camera
- WiFi
- RS485
- RS232
- Relay
- LoRaWAN
- GPS
- NB-IoT
- LTE
- GSM
- Zigbee
- Servo
- StepMotor
- Ethernet
- E-Paper
- 
- Product
- Contents
- 
- Search
- DinMeter v1.1
- SKU:K134-V11
- 
- 
- 
- Description
- DinMeter v1.1 is an iterative upgrade of the DinMeter product, with the core enhancement being the main control module upgraded from Stamp-S3 to Stamp-S3A. DinMeter v1.1 adopts the 1/32 DIN standard digital meter cutout size, allowing direct installation into reserved mounting openings of mainstream equipment such as industrial control cabinets and PLC control boxes, without the need for custom brackets or panel modifications. This significantly reduces integration cost and assembly time. It supports two mounting methods—double-sided adhesive and screw hole fixation—to meet installation requirements in different scenarios. The product integrates a 1.14-inch ST7789 display and a rotary encoder with button, enabling precise knob position tracking and interactive operation. An onboard RTC real-time clock, buzzer, and function buttons support scheduled reminders and wake-up functions. The power supply design is flexible, supporting a wide DC input range of 6 ~ 36V, and includes a lithium battery interface with charging circuitry to adapt to various power scenarios. In addition, the development board provides PORT.A and PORT.B expansion interfaces for easy connection of I2C and GPIO peripherals, making it suitable for various embedded instrumentation display and control input applications.
-Tutorial
- Arduino IDE
- Arduino IDE
- This tutorial introduces how to program and control the DinMeter v1.1 device using Arduino IDE. 
- UiFlow2
- UiFlow2
- This tutorial introduces how to control the DinMeter v1.1 device using the UiFlow2 graphical programming platform. 
-Features
- ST7789P3 display
- Stamp-S3A as the main controller
- Rotary encoder
- Wide voltage input
- Reserved PORT.A and PORT.B interfaces
- Lithium battery interface (rechargeable)
- 1/32 DIN standard (45 x 22.5mm)
- Two mounting methods:Double-sided adhesive
- Screw hole fixation
- Development PlatformUiFlow2
- Arduino IDE
- ESP-IDF
- PlatformIO
- Includes
- 1 x DinMeter v1.1
- 1 x 250mAh Polymer Lithium Battery
- 1 x 2.54-2P Terminal
- 1 x Plastic Back Clip
- 1 x Adhesive Tape
- 1 x Pin Sticker
- Applications
- Smart home monitoring and control systems
- Access control systems
- Industrial control
- Maker and DIY projects
- Specifications
- Specification
- Parameter
- | SoC
- ESP32-S3FN8 @ Xtensa® 32-bit LX7 dual-core processor, clock frequency 240MHz
- Flash
- 8MB
- Wi-Fi
- 2.4 GHz Wi-Fi
- USB
- USB OTG, USB Serial/JTAG
- Wide Voltage Input Range
- 6 ~ 36V
- Display Driver
- ST7789P3
- Display Resolution
- 135 x 240
- Charging Current
- 100mA
- Grove Load Capability
- PORT.A Load: DC 5V@220mA | PORT.B Load: DC 5V@220mA
- Standby Current (Battery Power)
- DC 4.2V@38.4uA
- Battery Socket Specification
- 1.25mm-2P
- Power Supply Methods
- USB / DC Power / Battery
- Operating Temperature
- 0 ~ 40°C
- Product Size
- 53.0 x 30.0 x 32.0mm
- Product Weight
- 17.8g
- Package Size
- 136.0 x 95.0 x 24.0mm
- Gross Weight
- 44.9g
-Learn
- Power On/Off
- Power On: When powered only by the battery, the device can be woken up by pressing the WAKE button or via an RTC scheduled interrupt (IRQ). After the wake-up signal is triggered, the initialization program must set the HOLD (GPIO46) pin to high level (1) to maintain power supply; otherwise, the device will return to sleep.
- Power Off: When there is no USB external power (battery power only), the device can be powered off using either of the following methods:
-(1) Press the RST button;
-(2) The program actively sets the HOLD (GPIO46) pin to low level (0) to cut off battery power.
- Download Mode
- To enter download mode, press and hold the G0 button on the Stamp-S3A before powering on, then release it after power is applied.
- RGB LED Power Supply
- RGB LED Power Supply Instructions
- The device uses Stamp-S3A as its main controller. To optimize overall power consumption, Stamp-S3A adds an independent electronic switch for the RGB LED power supply compared with the previous Stamp-S3. Before controlling the RGB LED in software, set GPIO38, which controls this switch, to a high level.
-Power Supply
- Three power supply methods are provided: USB / DC / BAT
- DIN Size Standard
- Schematics
- DinMeter v1.1 Schematics PDF
- 
- 
- 1/1
- 
- PinMap
- RTC8563 & ENCODER
- ESP32-S3FN8
- G12
- G11
- G40
- G41
- G3
- G42
- | RTC8563
- SCL
- SDA
- 
- 
- ENCODER
- 
- B
- A
- 
- BEEP
- 
- 
- beep
- BUTTON (ENCODER)
- 
- 
- BTN(WAKE)
-ST7789P3
- ESP32-S3FN8
- G7
- G6
- G4
- G5
- G8
- G9
- | ST7789P3
- CS
- SCK
- RS
- MOSI
- RESET
- BL
-HY2.0-4P
- HY2.0-4P
- Black
- Red
- Yellow
- White
- | PORT.A
- GND
- 5V
- G13
- G15
- PORT.B
- GND
- 5V
- G2
- G1
-Model Size
- DinMeter v1.1 Model Size PDF
- Structure
- DinMeter v1.1 Structure Files
- Datasheets
- BM8563
- tp4057
- Spec of external DC power connector
- Lithium battery seat
- Softwares
- Quick Start
- DinMeter v1.1 Arduino Quick Start
- Arduino
- DinMeter v1.1 Arduino Driver Library
- DinMeter v1.1 Factory Firmware
- UiFlow2
- DinMeter v1.1 UiFlow2 Quick Start
- Easyloader
- Easyloader
- Download
- Note
- | DinMeter User Demo Easyloader
- download
- /
-Video
- Product Comparison
- Product Compare
- DinMeter v1.1 
- DinMeter 
- | Main Controller
- Stamp-S3A
- Stamp-S3
- 
- Page Tools
- PDF Copy page 
- 
- About Us
- About M5Stack
-News
-Blog
-Events
-Contact Us
- Where to buy
- Distributors
-Official Store
-AliExpress
-Amazon
-Taobao
- Solution
- For Business
-For Developers
- Software
- UiFlow1
-UiFlow2
-M5Burner
-Block Designer
-EzData 2.0
-EasyLoader Packer
-VLW Font Creator
-Device USB Driver
- Documentation
- Product Documents
-UiFlow1
-UiFlow2
-Arduino
-ESP-IDF
-StackFlow AI
-Home Assistant
-nanoFramework
-Product Guide
-Product Certifications
-I2C Table
-Product Selector
-Hardware Design Files
-Release History
-Stack Compatibility
-Stack Screw Length
- 
- Stay in the Loop
- 
- Weekly updates on new products, innovations, and announcements.
- 
- Subscribe
- 
- Email is invalid!
- 
- Thanks for subscribing
- 
- 
- M5Stack Technology Co., Ltd
- 
- Address: 
- Block A10, Expo Bay South Coast, Fuhai Street, Bao'an District, Shenzhen, China
- 
- TEL: 
- +86 755 8657 5379
- 
- Email: 
- support@m5stack.com
- 
- Copyright ©
- M5Stack Technology Co., Ltd.
- All rights reserved.
- Privacy Policy| Terms of Service| Shipping Policy| Refund Policy| Payment Method
- 粤ICP备16010631号
- 
- 
diff --git a/devices/m5stack/dinmeter-v1.1/artifacts/mechanical/DinMeter_v1.1.stl b/devices/m5stack/dinmeter-v1.1/artifacts/mechanical/DinMeter_v1.1.stl
deleted file mode 100644
index 0928d71..0000000
Binary files a/devices/m5stack/dinmeter-v1.1/artifacts/mechanical/DinMeter_v1.1.stl and /dev/null differ
diff --git a/devices/m5stack/dinmeter-v1.1/artifacts/schematic/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf b/devices/m5stack/dinmeter-v1.1/artifacts/schematic/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf
deleted file mode 100644
index 6dced46..0000000
Binary files a/devices/m5stack/dinmeter-v1.1/artifacts/schematic/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf and /dev/null differ
diff --git a/devices/m5stack/dinmeter-v1.1/certification-and-compliance.md b/devices/m5stack/dinmeter-v1.1/certification-and-compliance.md
deleted file mode 100644
index 46d6918..0000000
--- a/devices/m5stack/dinmeter-v1.1/certification-and-compliance.md
+++ /dev/null
@@ -1,159 +0,0 @@
-# Certification and compliance — dinmeter-v1.1
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: no grant found.** See §2 for the controls that make this a real absence, and §4 for what it does and does not imply.
-
-**No FCC ID specific to v1.1.** The only DinMeter grant is `2AN3WM5DINMETER` (2024-07-23), which pre-dates the v1.1 product listing (Shopify `published_at` 2026-01-30). Either v1.1 ships under the existing grant as a permissive change, or it is not separately authorised. **Not resolved here** — no Class II Permissive Change filing appears under `2AN3W`.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ❌ **no grant found** (controlled — §2) |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AN3WM5DINMETER`, `2AN3WM5STAMPS3A`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5DINMETER`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2412-2462 MHz Original Equipment 2024-07-23** |
-| Application purpose | Final Action Date 2412-2462 MHz Original Equipment 2024-07-23 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5DINMETER` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 2,123,431 | `b5aac335a6631663…` |
-| `ID-Label-Location-Info-FCC-ID-Label.pdf` | 357,530 | `87bc3655794390cc…` |
-| `Internal-Photos-Internal-Photos.pdf` | 3,674,683 | `7e0be459cbbf21a4…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE.pdf` | 126,464 | `aeb323a16a2ad99c…` |
-| `Test-Report-Antenna-Specification.pdf` | 822,846 | `0728acb7f328e39c…` |
-| `Users-Manual-User-Manual.pdf` | 2,021,122 | `b472ab81821318a6…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5DINMETER/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5DINMETER/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AN3WM5STAMPS3A`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2025-02-13** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2025-02-13 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5STAMPS3A` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 2,142,184 | `6910fdc8e5f46913…` |
-| `ID-Label-Location-Info-label-and-location.pdf` | 69,357 | `60d9ccb36cc10e2a…` |
-| `Internal-Photos-Internal-Photos.pdf` | 2,778,287 | `e6512283b0e419c2…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE-20cm-.pdf` | 176,710 | `db49d95ade5911cc…` |
-| `Test-Report-AiTDG-241205002W1-Test-Report-BLE.pdf` | 959,274 | `027dd133c4ac00b6…` |
-| `Users-Manual-User-Manual.pdf` | 2,308,121 | `e9056d899bdd6cda…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5STAMPS3A/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5STAMPS3A/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/dinmeter-v1.1/commands.md b/devices/m5stack/dinmeter-v1.1/commands.md
deleted file mode 100644
index 6e26430..0000000
--- a/devices/m5stack/dinmeter-v1.1/commands.md
+++ /dev/null
@@ -1,135 +0,0 @@
-# DinMeter v1.1 — command ledger
-
-The full ledger — environment, extraction tooling, the Altium double-draw trap, GitHub,
-Reddit and the blocked forum — is **[`../dinmeter/commands.md`](../dinmeter/commands.md)**.
-This page holds the commands that produced the v1.1-specific findings.
-
-Status: `executed-success` · `executed-failed` · `reported-working` · `inferred` · `not-tested`.
-
----
-
-## 1. The byte-identity checks — the highest-value commands in the pass
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-
-curl -fSL -A "$UA" -o v1.0-schematic.pdf \
-  'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/500/DIN_Meter_v1.0.pdf'
-curl -fSL -A "$UA" -o v1.1-schematic.pdf \
-  'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf'
-sha256sum v1.0-schematic.pdf v1.1-schematic.pdf
-```
-`executed-success`:
-```
-03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070  v1.0-schematic.pdf
-03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070  v1.1-schematic.pdf
-```
-
-```bash
-RAW=https://raw.githubusercontent.com/m5stack/M5_Hardware/a240115c94b19ecf647f229c47fa9a8ce46ccdc4
-curl -fsSL -o DinMeter.stl      "$RAW/Products/K134_DinMeter/Structures/DinMeter.stl"
-curl -fsSL -o DinMeter_v1.1.stl "$RAW/Products/K134-V11_DinMeter_v1.1/Structures/DinMeter_v1.1.stl"
-curl -fsSL -o Stamp-S3.stl      "$RAW/Products/S007_Stamp-S3/Structures/Stamp-S3.stl"
-curl -fsSL -o Stamp-S3A.stl     "$RAW/Products/S007-V033_Stamp-S3A/Structures/Stamp-S3A.stl"
-sha256sum *.stl
-```
-`executed-success` — two identical pairs:
-```
-90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7  DinMeter.stl
-90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7  DinMeter_v1.1.stl
-f72c1af2d42930fc57a3db1bd3282568a3952095f77539016a12437d59d7df5d  Stamp-S3.stl
-f72c1af2d42930fc57a3db1bd3282568a3952095f77539016a12437d59d7df5d  Stamp-S3A.stl
-```
-
-**Three findings, two commands.** Had the files simply been filed by name, all three would have
-been recorded as "v1.1 documentation obtained".
-
-## 2. Enumerating what M5_Hardware actually publishes
-
-```bash
-curl -sS -H "Authorization: Bearer $(gh auth token)" \
-  'https://api.github.com/repos/m5stack/M5_Hardware/git/trees/master?recursive=1' \
-| python3 -c "
-import json,sys
-d=json.load(sys.stdin); print('paths',len(d['tree']),'truncated',d.get('truncated'))
-for t in sorted(x['path'] for x in d['tree']):
-    if any(k in t for k in ('DinMeter','K134','S007','Stamp-S3','StampS3')): print(' ',t)"
-```
-`executed-success` — 931 paths, not truncated. Result: **`Stamp-S3-SMD`, `Stamp-S3-DIP`,
-`Stamp-S3_PIN1.27_Socket`, `Stamp-S3_PIN2.54_DIP` footprints exist; there is NO Stamp-S3A
-footprint and no `Stamp-S3A.step`.** Another negative finding, established by enumeration rather
-than by searching for what was expected.
-
-## 3. The two Stamp schematics, parsed and diffed
-
-```bash
-for f in Sch_M5StampS3_v0.2 Sch_StampS3_v0.3.3-StampS3A; do
-  /tmp/opencode/.pdfvenv/bin/python /tmp/opencode/pdf_bbox.py "$f.pdf" > "$f.bbox.xml"
-  python3 parse_dinmeter_sch.py "$f.bbox.xml" | head -4
-done
-```
-`executed-success`:
-```
-Sch_M5StampS3_v0.2         words=927 plain=594 CO=54 PI=229 NL=50   -> 54 designators
-Sch_StampS3_v0.3.3-StampS3A words=961 plain=609 CO=59 PI=243 NL=50  -> 59 designators
-```
-
-The diff (retained as
-[`components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt`](../../../components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt)):
-```
-removed: D6 JP1 JP4 M2 R3 R6 R17
-added:   C15 C16 C18 C19 C20 C24 C25 L4 L6 L7 U4
-```
-
-## 4. Proving the DC-DC conflict
-
-```bash
-for f in Sch_M5StampS3_v0.2 Sch_StampS3_v0.3.3-StampS3A; do
-  printf '%-32s ' "$f"; grep -c 'MUN3CAD01-SC' "$f.bbox.xml"
-done
-```
-`executed-success`: **1** on v0.2, **0** on v0.3.3 — while the Stamp-S3A product page still lists
-`DC-DC: MUN3CAD01-SC`. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md) V4.
-
-## 5. Establishing the RGB-LED prediction — a source read, not a test
-
-```bash
-grep -n "board_M5StampS3A\|board_M5DinMeter_v11\|GPIO_NUM_38" M5Unified/src/*.cpp M5Unified/src/**/*.cpp
-# executed-success: NO MATCHES for any of the three
-
-grep -n -A2 "_pin_table_other0" M5Unified/src/M5Unified.cpp | grep DinMeter
-# executed-success: { board_t::board_M5DinMeter   , GPIO_NUM_21 },   (line 246)
-```
-at master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`. **`inferred`** for the consequence; the
-grep itself is `executed-success`.
-
-## 6. Pricing and lifecycle
-
-```bash
-for s in m5stack-din-meter-v1-1-with-m5stamps3a m5stack-din-meter-w-m5stamps3 \
-         m5stamp-esp32s3-module m5stamps3a-with-2-54-header-pin; do
-  curl -sS -A "$UA" -L "https://shop.m5stack.com/products/$s.js" | python3 -c "
-import json,sys; d=json.load(sys.stdin); v=d['variants'][0]
-print(f\"{d['title'][:46]:<48} sku={v.get('sku'):<20} \${int(v['price'])/100:<6} avail={v['available']} pub={d.get('published_at','')[:10]}\")"
-done
-```
-`executed-success`:
-```
-M5Stack Din Meter v1.1 with M5StampS3A     sku=K134-V11            $24.5  avail=True  pub=2026-01-30
-[EOL] M5Stack Din Meter w/ M5StampS3       sku=K134                $24.5  avail=False pub=2024-03-08
-[EOL] M5Stamp ESP32S3 Module               sku=S007                $7.5   avail=False pub=2023-02-10
-M5StampS3A with 2.54 Header Pin            sku=S007-PIN254-V033    $7.5   avail=True  pub=2025-09-11
-```
-The `[EOL]` prefixes are M5Stack's own title text.
-
-## 7. For the reader — `not-tested`
-
-```cpp
-// The one test that would settle this record's biggest open question, on a v1.1 unit:
-pinMode(38, OUTPUT); digitalWrite(38, HIGH); delay(1);   // then drive GPIO21
-// Run it once with these lines and once without. Report the difference.
-```
-
-Flash backup, restore and build commands are identical to v1.0's:
-[`../dinmeter/commands.md` §10](../dinmeter/commands.md) and
-[`factory-firmware.md`](factory-firmware.md).
diff --git a/devices/m5stack/dinmeter-v1.1/community.md b/devices/m5stack/dinmeter-v1.1/community.md
deleted file mode 100644
index 9eb7a5c..0000000
--- a/devices/m5stack/dinmeter-v1.1/community.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# DinMeter v1.1 — community
-
-→ **[`projects-and-community.md`](projects-and-community.md)** (v1.1 specifics) and
-**[`../dinmeter/projects-and-community.md`](../dinmeter/projects-and-community.md)** (the full
-catalogue).
-
----
-
-## Summary
-
-**There is no v1.1-specific community.** No repository, board file, build flag or forum thread
-anywhere distinguishes DinMeter v1.1 from v1.0, and the only social artefact referencing the
-revision is M5Stack's own r/M5Stack launch post of 2026-01-30 — 22–23 points, **one comment**.
-
-That is a rational outcome: the firmware is compatible, so from a developer's point of view there
-was nothing to say. The cost is that the **one** genuine behavioural change — the RGB LED
-needing `GPIO38 = HIGH` — has gone entirely unremarked in public, and remains a prediction rather
-than a confirmed report.
-
-The device family's community is small in absolute terms: 13 third-party GitHub repositories, one
-substantial firmware port (`bmorcelli/Launcher`, ★2054), and no ESPHome, Tasmota or Meshtastic
-support. M5Stack's own forum could **not** be enumerated (search API returns HTTP 401; the HTML
-search page is a NodeBB JavaScript shell), so it is a blocked source rather than an empty one.
-
-**Prevalence caveat:** this describes public, indexed activity on GitHub and Reddit on
-2026-09-04. Chinese-language platforms and video sources were declared exclusions.
diff --git a/devices/m5stack/dinmeter-v1.1/comparisons-and-recommendations.md b/devices/m5stack/dinmeter-v1.1/comparisons-and-recommendations.md
deleted file mode 100644
index d4ee765..0000000
--- a/devices/m5stack/dinmeter-v1.1/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# DinMeter v1.1 — comparisons and recommendations
-
-The full comparison — against the **Waveshare ESP32-S3-Knob-Touch-LCD-1.8**, the **M5Dial**, a
-**DIY encoder + ESP32 build**, the alternatives-by-tier table and the DIN-cutout-versus-DIN-rail
-explanation — is in
-**[`../dinmeter/comparisons-and-recommendations.md`](../dinmeter/comparisons-and-recommendations.md)**
-and applies to v1.1 unchanged: same enclosure, same cutout, same 6–36 V input, same display size,
-same price.
-
-This page answers only the questions that are specific to the revision.
-
----
-
-## 1. v1.1 versus v1.0 — should you upgrade?
-
-| Your situation | Answer | Why |
-|---|---|---|
-| You own a working v1.0 | **No** | The gains are module-level sleep figures you cannot use. The board's own standby is **38.4 µA on both revisions** — identical on both product pages — because the DinMeter *cuts the battery with a latch* rather than sleeping the SoC. See [`performance.md` §2](performance.md#2-the-important-row-is-the-last-one) |
-| You are buying new | **v1.1** | It is the only one in stock. `K134` and `S007` are both marked `[EOL]` by M5Stack |
-| You run continuously on battery (no latch) | **Marginal yes** | ~33.5 mA → ~25.5 mA awake ⇒ roughly **7.4 h → 9.8 h** on the bundled 250 mA·h cell. Vendor figures, unmeasured |
-| You are deploying in a metal cabinet with marginal Wi-Fi | **Possibly** | The antenna match was genuinely rebuilt (3 → 6 matching positions). But M5Stack publishes **no dBi and no method**, and nothing here corroborates the claim. Do not pay for it sight-unseen; measure |
-| You need to match an existing fleet on K134 | Buy v1.1 anyway | Firmware compatibility is complete except the RGB LED, and that is a two-line fix. Insisting on K134 buys nothing and the vendor no longer sells it |
-| You are designing a new board around a Stamp | **Stamp-S3A**, USD 7.50 | The S3 is EOL. Budget **0.6 A** on the 3.3 V rail, not 1 A, and add the GPIO38 line if you want the LED |
-
-**The honest summary: v1.1 is a straight replacement, not an upgrade.** Same price, same
-capability, slightly better awake power, one new line of code if you use the LED. There is no
-scenario in which replacing a working v1.0 with a v1.1 is worth USD 24.50.
-
-## 2. Does the revision change any of the external comparisons?
-
-**No.** Every axis on which the DinMeter competes — the 1/32 DIN cutout (45 × 22.5 mm), the
-6–36 V screw-terminal input, the battery-backed RTC that can power the board back on, the
-detented knob, the 135 × 240 display, the absence of PSRAM and touch, the 0–40 °C range, and the
-USD 24.50 price — is **identical between v1.0 and v1.1**.
-
-| Competitor | Does v1.1 change the verdict? |
-|---|---|
-| Waveshare ESP32-S3-Knob-Touch-LCD-1.8 | **No.** The Waveshare still has 8 MB PSRAM, a 360 × 360 round touchscreen, audio in/out, haptics, microSD, a second MCU for Bluetooth Classic — and still cannot be panel-mounted or run from 24 V |
-| M5Dial v1.1 (USD 34.90) | **No.** Still +USD 10.40 for round + touch, still 5 V only, still no panel cutout. Note both products are now on their own "v1.1" — the M5Dial's is a separate SKU (`K130-V11`) and was **not** researched here |
-| DIY encoder + ESP32 (≈ USD 10–18) | **No.** The enclosure and the standard aperture remain the part you cannot buy |
-| M5Stack StamPLC (USD 42.90) | **No.** Still DIN-*rail*, not DIN-cutout — a different problem |
-
-→ [`../dinmeter/comparisons-and-recommendations.md`](../dinmeter/comparisons-and-recommendations.md)
-
-## 3. Who should buy a DinMeter v1.1
-
-Unchanged from v1.0, and worth restating because it is narrow and specific:
-
-**Buy it if** you have a 1/32 DIN aperture in an existing panel — a dead Omron/Autonics/Fuji
-panel meter in a machine door is the canonical case — or you have 12/24 V and no 5 V, and you
-want a detented knob as the primary input with timekeeping that survives power loss.
-
-**Do not buy it if** you need PSRAM, touch, a bigger screen, more than ~6 free GPIOs, operation
-outside 0–40 °C, or ESPHome/Tasmota/Meshtastic support. And do not buy it as a *first* ESP32
-board — the GPIO46 power latch will catch you and the failure looks like a hardware fault.
-
-## 4. One caution specific to v1.1
-
-If you buy v1.1 and the RGB LED does not light, **it is not faulty**. Add:
-
-```cpp
-pinMode(38, OUTPUT); digitalWrite(38, HIGH); delay(1);
-```
-
-before driving GPIO21. No framework does this for you.
-→ [`../dinmeter/features/rgb-led.md`](../dinmeter/features/rgb-led.md)
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered.
-
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — the Stamp-S3 → Stamp-S3A delta this record documents is used there as the
-  general lesson for battery designs: a **45× board sleep-current improvement**
-  (310.89 µA → 6.84 µA on `VIN_5V`, vendor figures, method unstated) that came
-  entirely from the power tree, and that cost the RGB LED its always-on supply.
-  The guide's wider point is that **this repository has no ESP32-C3, ESP32-S3 or
-  ESP32-P4 deep-sleep figure at all** — every sleep number available here,
-  including these two, is a board-level vendor claim under unstated conditions.
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — where the DinMeter family sits among every device record, and the observation
-  that its v1.1 is the repository's cleanest example of a vendor **re-serving
-  byte-identical assets under a new revision's filenames**.
diff --git a/devices/m5stack/dinmeter-v1.1/compatibility-and-status.md b/devices/m5stack/dinmeter-v1.1/compatibility-and-status.md
deleted file mode 100644
index fc2c91b..0000000
--- a/devices/m5stack/dinmeter-v1.1/compatibility-and-status.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# DinMeter v1.1 — compatibility and status
-
-Shared rows (library versions, third-party firmware, peripherals, known-bad combinations) are in
-**[`../dinmeter/compatibility-and-status.md`](../dinmeter/compatibility-and-status.md)** and apply
-unchanged. This page is the v1.1 delta.
-
-**No v1.1 hardware was available.** Nothing below is a firsthand test.
-
----
-
-## 1. Does v1.0 firmware run on v1.1?
-
-**Yes, unmodified, with exactly one exception.**
-
-| Subsystem | v1.1 status | Basis |
-|---|---|---|
-| Boot / download mode | **works** | identical vendor instruction on both Stamp pages |
-| Toolchain / target (`esp32s3`, 8 MB, no PSRAM) | **works** | vendor spec, both revisions |
-| M5Unified board detection | **works** — enumerates as `board_M5DinMeter` | no v1.1 or S3A enum exists at master `8530f537…` |
-| Display | **works** | identical pins, resolution, GRAM gap, `INVON`, driver path |
-| Rotary encoder | **works** | identical pins |
-| Encoder button / WAKE | **works** | identical |
-| Buzzer | **works** | identical |
-| RTC (BM8563, 0x51) | **works** | identical |
-| Power hold (GPIO46) | **works** | identical |
-| Battery ADC | **works** | identical |
-| PORT.A / PORT.B | **works** | identical |
-| Wi-Fi / BLE API | **works** | same SoC, same stack |
-| Wi-Fi / BLE *performance* | **unknown** | antenna match rebuilt; vendor claims better, publishes no figure |
-| **RGB LED** | **fails (predicted)** | needs `GPIO38 = HIGH`; no framework does it |
-
-## 2. The one incompatibility, in full
-
-| Field | Value |
-|---|---|
-| Symptom | RGB LED does not light. No error, no warning, no compile failure |
-| Affects | K134-V11 only |
-| Cause | Stamp-S3A moved the WS2812B-2020's supply from the always-on `VDD_3V3` to the switched `BL_3V3`, gated by an AW35122FDR whose enable is GPIO38. The AW35122's `EN` has an internal ~7.1 MΩ pull-down, so the rail defaults off |
-| Why no framework saves you | M5Unified master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb` (2026-09-04): `board_M5DinMeter → GPIO_NUM_21` at `src/M5Unified.cpp:246`; **no GPIO38 enable step for any board**; no `board_M5StampS3A`; no v1.1 board enum |
-| Workaround | `pinMode(38, OUTPUT); digitalWrite(38, HIGH); delay(1);` before driving GPIO21 |
-| Portable? | Yes — GPIO38 is unconnected on the v1.0 carrier, so the same code is safe on both |
-| **Evidence status** | **`inferred`** — vendor documentation + schematic + source read. **Not reproduced on hardware** |
-| Reported upstream? | **No.** No M5Unified issue or PR addressing it was found on 2026-09-04 |
-
-## 3. Framework support, v1.1-specific
-
-| Framework | Status | Note |
-|---|---|---|
-| `M5DinMeter` 1.0.0 + M5Unified 0.2.21 | works, except the LED | no v1.1 release exists; the library is unchanged since 2024-03-07 |
-| `espressif/esp-board-manager` @ `2beb9b22…` | expected to work; **untested on v1.1** | its `board_info.yaml` says `version: 1.0.0` and it was written against the v1.0 page. Every pin it models is unchanged, so nothing in it is *wrong* for v1.1 — it simply does not know about GPIO38 |
-| UiFlow2 / `uiflow-micropython` | expected to work | the DinMeter target is not versioned by board revision |
-| `bmorcelli/Launcher` | expected to work | `m5stack-dinmeter` target makes no revision distinction |
-
-**No framework anywhere distinguishes v1.0 from v1.1.** That is convenient for compatibility and
-is precisely why the LED change is a silent failure.
-
-## 4. Module-level status (Stamp-S3A)
-
-| Item | Status | Note |
-|---|---|---|
-| ESP32-S3FN8, 8 MB, no PSRAM | unchanged | |
-| 23 broken-out GPIOs | unchanged, same list | |
-| USB-C native | unchanged | same `J2`, same `R1`/`R2` 5.1 kΩ CC |
-| 3.3 V rail current | **reduced: 1 A → 0.6 A** | undisclosed by the vendor; see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) V4 |
-| Rear LCD FPC numbering | **possibly reversed** | unresolved; irrelevant to the DinMeter |
-| Module footprint | believed unchanged | no Stamp-S3A footprint published; STLs byte-identical; but the spec table says 26 mm vs 24 mm |
-| Sleep current | much improved (vendor figures) | 310.89 → 6.84 µA on `VIN_5V` |
-
-## 5. What is untested — which is everything
-
-| Category | Status |
-|---|---|
-| Any v1.1 hardware in hand | **none** |
-| The RGB-LED/GPIO38 prediction | **not verified** ← highest-value test |
-| Any firmware built or flashed | **none** |
-| Any electrical or RF measurement | **none** |
-| Antenna improvement claim | **not tested** |
-| Teardown / chip-marking confirmation | **none** |
-| Whether the v1.1 PCB really is the v1.0 PCB | **not verified** |
-
-## 6. If you have a v1.1 unit — three tests, ten minutes
-
-1. **`pinMode(38,OUTPUT); digitalWrite(38,HIGH);` then drive GPIO21.** Does the LED light? Does
-   it light *without* the GPIO38 line? Two runs settle the record's biggest open question.
-2. **Flash a binary built for v1.0 unmodified.** Confirms or refutes the source-compatibility
-   verdict in [`stamp-s3-to-s3a-delta.md` §8](stamp-s3-to-s3a-delta.md#8-does-existing-dinmeter-firmware-run-unmodified).
-3. **Measure the Grove 5 V rail** on `J3` pin 3 — 5.00 V or ≈ 5.38 V? Settles a conflict that
-   applies to both revisions.
-
-Results belong here and in [`../dinmeter/compatibility-and-status.md`](../dinmeter/compatibility-and-status.md).
diff --git a/devices/m5stack/dinmeter-v1.1/coverage.md b/devices/m5stack/dinmeter-v1.1/coverage.md
deleted file mode 100644
index d0e530e..0000000
--- a/devices/m5stack/dinmeter-v1.1/coverage.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# DinMeter v1.1 — feature coverage
-
-The full 20-capability matrix, the "not present" list and the coverage summary are in
-**[`../dinmeter/coverage.md`](../dinmeter/coverage.md)** and apply to v1.1 unchanged, because the
-carrier's capability set is unchanged.
-
-This page records the v1.1-specific coverage status.
-
----
-
-## 1. Capabilities whose coverage differs
-
-| Capability | v1.0 status | v1.1 status | Gap |
-|---|---|---|---|
-| **RGB LED** | works out of the box | **needs `GPIO38 = HIGH` — predicted, unverified** | ⚠ **No example exists anywhere**, official or community. The one feature that changed is the one feature nobody has demonstrated |
-| **Display** | ST7789V2, datasheet retained | **ST7789P3, no datasheet exists** | Command-compatibility assumed, not verified |
-| Wi-Fi / BLE *performance* | — | antenna match rebuilt; vendor claims better | **Unmeasured**; no figure published |
-| Everything else (18 capabilities) | — | **identical** | as v1.0 |
-
-## 2. Coverage summary
-
-| Metric | v1.1 |
-|---|---:|
-| Advertised/fitted capabilities | 20 (same set as v1.0) |
-| With a task-oriented feature guide | 20 / 20 (all in the v1.0 record, linked from [`features/README.md`](features/README.md)) |
-| With official v1.1-specific documentation | **3** — the RGB-LED/GPIO38 note, Power On/Off, Download Mode |
-| With an official example built for v1.1 | **0** — no v1.1-specific example exists |
-| With a community example built for v1.1 | **0** — no project distinguishes the revisions |
-| **Build-tested here** | **0** |
-| **Hardware-tested here** | **0** |
-| v1.1-specific gaps recorded | 8, in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-
-## 3. Evidence coverage for the delta itself
-
-This is where v1.1 coverage is actually strong, so it is worth stating what *is* established:
-
-| Delta claim | Evidence | Status |
-|---|---|---|
-| Module changed Stamp-S3 → Stamp-S3A | vendor comparison table + both schematics | **established** |
-| RGB LED moved to a switched rail gated by GPIO38 | vendor prose ×2 + net reading in both schematics | **established** |
-| That this breaks stock M5Unified | grep of M5Unified master `8530f537…` | **inferred** (source read; not reproduced) |
-| DC-DC replaced (`M2` → `U4` + external inductor) | designator diff + net/ball reading | **established** |
-| DC-DC current rating 1 A → 0.6 A | datasheet (`M2`) vs sheet annotation (`U4`) | **established** |
-| Antenna match rebuilt | designator diff + value reading | **established** (topology); values indicative |
-| Antenna *performs* better | vendor claim only | **unverified** |
-| No PSRAM on either | vendor spec + Launcher `build_unflags` | **established** |
-| USB path unchanged | identical designators and nets on both sheets | **established** |
-| Pin compatibility | identical 23-IO list + no new footprint + identical STL | **established**, with the 24/26 mm caveat |
-| Price unchanged | shop JSON, both SKUs | **established** |
-| Existing firmware runs unmodified | pin-by-pin comparison + board-enum grep | **established** except the LED |
-| Display controller renamed | vendor page ×3 places | **established** |
-| ST7789P3 ≡ ST7789V2 in behaviour | absence of contrary evidence | **inferred** |
-| Carrier PCB physically unchanged | byte-identical published assets | **NOT established** — only the *documentation* is unchanged |
-
-## 4. The gaps worth closing, in order
-
-1. **Test the RGB LED on a v1.1 unit** (with and without the GPIO38 line). Converts the single
-   most consequential inference in the record into a measurement. Ten minutes.
-2. **Flash a v1.0-built binary onto a v1.1 unit.** Confirms the source-compatibility verdict.
-3. **OCR or read `S007-V033_PinMap_01.jpg`.** Settles the rear-FPC numbering question.
-4. **Photograph a v1.1 PCB.** The only way to test whether the carrier really is unchanged.
-5. **RSSI comparison, v1.0 vs v1.1.** The only way to test the antenna claim.
-
-→ [`../dinmeter/coverage.md`](../dinmeter/coverage.md) for the full matrix.
diff --git a/devices/m5stack/dinmeter-v1.1/development.md b/devices/m5stack/dinmeter-v1.1/development.md
deleted file mode 100644
index 1780c61..0000000
--- a/devices/m5stack/dinmeter-v1.1/development.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# DinMeter v1.1 — development
-
-**The toolchain, board target, libraries, build/flash/monitor procedure and download-mode
-sequence are identical to the DinMeter v1.0's.**
-→ **[`../dinmeter/development.md`](../dinmeter/development.md)** is the full guide.
-
-This page states only the v1.1 deltas, and the evidence that the rest is genuinely the same.
-
----
-
-## 1. Do existing DinMeter builds run on v1.1? — **Yes, except one thing**
-
-| Aspect | v1.1 | Basis |
-|---|---|---|
-| Target / toolchain | `esp32s3`, 8 MB flash, **no PSRAM** — unchanged | vendor spec; Bruce/Launcher `build_unflags = -DBOARD_HAS_PSRAM` |
-| M5Unified board enum | `board_M5DinMeter` — **unchanged**; there is no v1.1 enum and no `board_M5StampS3A` at master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb` | grep of `src/`, `executed-success` |
-| `M5DinMeter` library | **1.0.0**, unchanged; no v1.1 release, no v1.1 code path | GitHub API, HEAD `8ccbad72…` |
-| Display / encoder / button / buzzer / RTC / Grove / power hold | all unchanged | PinMap comparison + M5Unified source |
-| Download mode | hold `G0` on the module while applying power — **identical wording on both Stamp pages** | vendor docs |
-| Partition layout | unchanged (none published for either) | — |
-| **RGB LED** | **needs `GPIO38 = HIGH` first, or it stays dark** | §2 |
-
-**A binary built for v1.0 boots and runs on v1.1.** No recompilation is required. Nothing in the
-build system needs to change.
-
-## 2. The one change you must make — only if you use the RGB LED
-
-```cpp
-// Portable across v1.0 and v1.1. On v1.0 GPIO38 is unconnected on the carrier,
-// so driving it is harmless.
-pinMode(38, OUTPUT);
-digitalWrite(38, HIGH);
-delay(1);              // AW35122 typical rise 165 us
-// ... then drive GPIO21 with your WS2812 library of choice
-```
-`not-tested`. Evidence chain:
-[`stamp-s3-to-s3a-delta.md` §3](stamp-s3-to-s3a-delta.md#3-change-1--the-rgb-led-is-no-longer-always-powered-the-only-source-compatibility-break).
-
-**Nothing else in any framework needs a change**, and no framework currently *makes* this change
-for you.
-
-## 3. Still true, and still the first thing to get right
-
-Raise **GPIO46** in `setup()` or the board switches itself off on battery power the moment you
-release the knob. `M5.begin()` does it via M5Unified's power-hold table
-(`M5Unified.cpp:282`, `board_M5DinMeter → GPIO_NUM_46`). Bare ESP-IDF or bare Arduino: do it
-yourself, first thing.
-
-→ [`../dinmeter/development.md` §0](../dinmeter/development.md#0-the-one-thing-to-do-first)
-
-## 4. Framework support status for v1.1 specifically
-
-| Framework | v1.1 status | Note |
-|---|---|---|
-| Arduino + `M5DinMeter` 1.0.0 + M5Unified | **works**, except the RGB LED | no v1.1-specific release exists |
-| ESP-IDF + `espressif/esp-board-manager` | `board_info.yaml` declares `version: 1.0.0` and was written against the v1.0 page; **nothing in it is wrong for v1.1** — every pin it models is unchanged | untested on v1.1 hardware |
-| UiFlow2 | supported; the DinMeter target in `m5stack/uiflow-micropython` is not versioned by board revision | — |
-| `bmorcelli/Launcher` | its `m5stack-dinmeter` target makes no revision distinction | ships as `Launcher-m5stack-dinmeter.bin` |
-| PlatformIO | M5Stack's own factory project uses generic `esp32-s3-devkitc-1`; nothing revision-specific | — |
-
-**No framework distinguishes v1.0 from v1.1 anywhere.** That is convenient and it is also
-exactly why the RGB-LED change is a silent failure rather than a compile error.
-
-## 5. Everything else
-
-Versions, install commands, the Arduino FQBN caveat, the ESP-IDF route, the UiFlow2 relationship,
-serial/USB/download-mode detail, and the bricking-and-power risk table are all in
-**[`../dinmeter/development.md`](../dinmeter/development.md)** and apply verbatim.
diff --git a/devices/m5stack/dinmeter-v1.1/factory-firmware.md b/devices/m5stack/dinmeter-v1.1/factory-firmware.md
deleted file mode 100644
index 85eceeb..0000000
--- a/devices/m5stack/dinmeter-v1.1/factory-firmware.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# DinMeter v1.1 — factory firmware
-
-**The factory firmware, its source, its licence, its panel configuration and the backup/restore
-procedure are the same as the DinMeter v1.0's.**
-→ **[`../dinmeter/factory-firmware.md`](../dinmeter/factory-firmware.md)**
-
----
-
-## What is v1.1-specific
-
-| Item | Status |
-|---|---|
-| Source repository | **`m5stack/M5DinMeter-UserDemo`, unchanged.** Last push 2024-03-04, release `V0.1` — i.e. **22 months before the v1.1 launched**. No v1.1 branch, tag, commit or fork exists |
-| EasyLoader entry | Both product pages list the same "DinMeter User Demo Easyloader" | 
-| Prebuilt binary | **Still no stable download URL.** M5Burner only |
-| Binary hash / build date / partition table | **unknown** for both revisions |
-| Does the v1.0 image run on v1.1? | **Yes** — same target, same pin map, same board enum. The RGB LED will not light (the firmware does not raise GPIO38), but the factory demo's LED behaviour is not documented, so it may never have driven it |
-
-**The most informative fact here is the date.** M5Stack shipped DinMeter v1.1 on 2026-01-30 using
-factory-firmware source last touched on 2024-03-04. That is a strong, independent signal that the
-carrier is unchanged: if the board had been revised, the evaluation firmware would have needed
-attention.
-
-## Backing up before you overwrite
-
-Same procedure, same warning — there is no vendor-published binary with a stable URL, so read the
-flash out first. All `not-tested`:
-
-```bash
-# Download mode: hold G0 on the Stamp-S3A while applying power, release after.
-esptool.py --chip esp32s3 -p /dev/ttyACM0 -b 460800 read_flash 0 0x800000 dinmeter-v11-factory-backup.bin
-sha256sum dinmeter-v11-factory-backup.bin
-```
-
-**If you do this, please record the hash and the flash layout.** No dump of either revision's
-factory image exists in this record, and a v1.1 dump would additionally settle whether the
-shipped image differs from the v1.0's at all.
-
-→ Full detail, licence analysis and the LovyanGFX panel configuration:
-[`../dinmeter/factory-firmware.md`](../dinmeter/factory-firmware.md)
diff --git a/devices/m5stack/dinmeter-v1.1/features/README.md b/devices/m5stack/dinmeter-v1.1/features/README.md
deleted file mode 100644
index d7c2e96..0000000
--- a/devices/m5stack/dinmeter-v1.1/features/README.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# DinMeter v1.1 — feature guides
-
-**All nine feature guides live in the v1.0 record and apply verbatim to v1.1**, because the
-carrier board, its GPIO map and its peripherals are unchanged. They are not duplicated here.
-
-→ **[`../../dinmeter/features/`](../../dinmeter/features/README.md)**
-
-| Guide | v1.1 delta |
-|---|---|
-| [Rotary encoder and buttons](../../dinmeter/features/rotary-encoder-and-buttons.md) | none |
-| [Display](../../dinmeter/features/display.md) | controller named **ST7789P3** instead of ST7789V2; same pins, same 135 × 240, same GRAM gap (+52, +40), same `INVON`, same driver path. **No ST7789P3 datasheet exists** |
-| [RTC and timekeeping](../../dinmeter/features/rtc-and-timekeeping.md) | none |
-| [Buzzer](../../dinmeter/features/buzzer.md) | none |
-| [Power and battery](../../dinmeter/features/power-and-battery.md) | none at board level. The **module's** sleep current improves ~45× on `VIN_5V`, but the board's own 38.4 µA standby figure is **unchanged on both product pages** — because the board cuts the battery with a latch rather than sleeping the SoC |
-| [PORT.A / PORT.B expansion](../../dinmeter/features/porta-portb-expansion.md) | none |
-| [Wi-Fi and BLE](../../dinmeter/features/wifi-and-ble.md) | same radio and API. The module's antenna matching network was rebuilt and M5Stack claims *"better signal reception"* — **with no figure and no method**. Neither corroborated nor refuted |
-| [**RGB LED**](../../dinmeter/features/rgb-led.md) | ⚠ **THE ONE REAL CHANGE.** Requires `GPIO38 = HIGH` before the LED will light. Silent failure otherwise |
-| [DIN mounting and mechanical](../../dinmeter/features/din-mounting-and-mechanical.md) | none — the published STL is byte-identical. Packaging differs (136 × 95 × 24 mm, 44.9 g gross vs 136 × 93 × 23 mm, 47.0 g) and the bundle names changed |
-
-## If you read one thing
-
-[`../stamp-s3-to-s3a-delta.md`](../stamp-s3-to-s3a-delta.md) — the complete, schematic-derived
-Stamp-S3 → Stamp-S3A change list, which *is* the v1.1 product.
diff --git a/devices/m5stack/dinmeter-v1.1/gaps-and-conflicts.md b/devices/m5stack/dinmeter-v1.1/gaps-and-conflicts.md
deleted file mode 100644
index 9dab7c9..0000000
--- a/devices/m5stack/dinmeter-v1.1/gaps-and-conflicts.md
+++ /dev/null
@@ -1,161 +0,0 @@
-# DinMeter v1.1 — gaps and conflicts
-
-v1.1-specific items. Everything that applies to both revisions — the Grove wire-colour conflict,
-the three unmarked designators, the Grove 5 V rail arithmetic, the untraced GPIO14/39 network,
-and the full negative-result table — is in
-**[`../dinmeter/gaps-and-conflicts.md`](../dinmeter/gaps-and-conflicts.md)**.
-
----
-
-## V1 · ⚠ The RGB LED almost certainly does not work with stock M5Unified — **predicted, unverified**
-
-**The most consequential open question in this record.**
-
-| Evidence | Says |
-|---|---|
-| M5Stack, DinMeter v1.1 page | *"Stamp-S3A adds an independent electronic switch for the RGB LED power supply… Before controlling the RGB LED in software, set **GPIO38**, which controls this switch, to a high level."* |
-| M5Stack, Stamp-S3A page comparison table | S3A: *"RGB LED power is multiplexed with the reserved screen FPC bus backlight"*; S3: *"Powered as soon as power is applied"* |
-| `Sch_StampS3_v0.3.3.pdf` | `U3` (WS2812B-2020) `VDD` ← **`BL_3V3`**, the output of `U2` (AW35122FDR), whose `EN` is `DISP_BL` = GPIO38 |
-| `Sch_M5StampS3_v0.2.pdf` | `U3` `VDD` ← `VDD_3V3` — always on |
-| AW35122 datasheet | `EN` has an internal ~7.1 MΩ **pull-down** ⇒ the rail defaults **off** |
-| M5Unified master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb` (2026-09-04) | `_pin_table_other0` → `{ board_M5DinMeter, GPIO_NUM_21 }` (`src/M5Unified.cpp:246`); **no `board_M5StampS3A`, no v1.1 board enum, and no GPIO38 enable step for any board** |
-
-**Conclusion:** a v1.1 unit enumerates as `board_M5DinMeter`, takes the v1.0 LED path, and the
-rail is never enabled — so the LED stays dark.
-
-**Status: `inferred`. NOT reproduced on hardware.** No v1.1 unit was available.
-
-**Why it matters more than it looks:** the failure is *silent*. Code compiles, links, boots and
-runs; the LED simply does nothing. The natural diagnosis is "faulty LED" or "broken library",
-neither of which is true.
-
-**What would settle it:** two lines on a real v1.1 unit —
-```cpp
-pinMode(38, OUTPUT); digitalWrite(38, HIGH); delay(1);   // then drive GPIO21
-```
-Result belongs in [`compatibility-and-status.md`](compatibility-and-status.md).
-
----
-
-## V2 · ⚠ No v1.1 schematic, STL or footprint exists — **established**
-
-| Asset | v1.1 URL / path | Same bytes as v1.0? |
-|---|---|---|
-| Schematic | `…/1211/K134-V11_DIN_Meter_**v1.0**_2025_11_25_17_15_58.pdf` | **yes** — SHA-256 `03ec3353…6e4c070` |
-| Structure STL | `Products/K134-V11_DinMeter_v1.1/Structures/DinMeter_v1.1.stl` | **yes** — SHA-256 `90f04d6a…` |
-| Dimension drawing | *the same URL as v1.0* | yes |
-
-Even the v1.1 schematic's own filename says `v1.0`.
-
-**What this licenses:** M5Stack has published no v1.1-specific board documentation. **It does not
-prove the PCB is unchanged.** The two boards could differ in ways no published document shows —
-different passives, a different encoder supplier, a different panel vendor.
-
-**Corroborating (but not proving) that it really is unchanged:** the PinMap is identical
-signal-for-signal; M5Unified has one board enum; the factory firmware has not been touched since
-2024-03-04, 22 months before the v1.1 shipped; and the same pattern holds one level down, where
-`Stamp-S3A.stl` is byte-identical to `Stamp-S3.stl` and **no Stamp-S3A footprint exists at all**.
-
-**What would settle it:** a v1.1 schematic from M5Stack, or a teardown photograph of a v1.1 PCB
-next to a v1.0 one.
-
----
-
-## V3 · ⚠ ST7789P3 — named three times, documented nowhere
-
-The v1.1 page names `ST7789P3` in the Features list, the *Display Driver* specification row and
-the PinMap section heading. It then **removes** the display datasheet link that the v1.0 page
-carried (`ST7789V2_SPEC_V1.0.pdf`) and replaces it with **nothing** — the v1.1 *Datasheets*
-section lists BM8563, tp4057, the DC connector and the battery seat, and no display part.
-
-And M5Stack's own v1.0↔v1.1 "Product Comparison" table has **one row** — *Main Controller* — and
-does not mention the display at all.
-
-No ST7789P3 datasheet was located from Sitronix or any mirror.
-
-**Working assumption:** command-compatible with ST7789V2. Supported by identical pins, identical
-resolution, an unchanged driver path, M5Unified having no ST7789P3 branch, and M5Stack's own
-factory firmware using the *generic* `lgfx::Panel_ST7789` class rather than a V2-specific one.
-**That is absence of contrary evidence, not verification.** `inferred`.
-
-→ [`components/sitronix/st7789p3`](../../../components/sitronix/st7789p3/README.md)
-
----
-
-## V4 · ⚠ The Stamp-S3A page's DC-DC row is stale
-
-It lists `DC-DC: MUN3CAD01-SC` and links that datasheet from the **`S007 StampS3`** directory —
-the Stamp-S3's own path.
-
-The string `MUN3CAD01` **does not occur anywhere** in `Sch_StampS3_v0.3.3.pdf`. Designator `M2`
-is absent. The regulator there is `U4`: an 8-ball part with `VIN`/`EN`/`SW`/`VOS`/`VSEL1`/
-`VSEL2`/`VSEL3`/`GND`, annotated **`IOUT: 0~0.6A`**, driving an external 2.2 µH inductor (`L4`,
-`MWTC201608S2R2`). A µPOL module has an integrated inductor and an `FB` pin, not `SW` and `VSEL`
-straps, and is rated 1 A.
-
-**Resolution: the schematic wins; the spec row was carried over unedited.** `U4`'s part number is
-left **unidentified** rather than guessed —
-[`components/unidentified/m5stack-stamp-s3a/dcdc-u4`](../../../components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md).
-
-**Undisclosed consequence:** the new regulator is **0.6 A** where the old one was **1 A**. M5Stack
-mentions this nowhere. It is unlikely to matter on a DinMeter (the carrier makes its own 3.3 V)
-but it matters for anyone designing with a bare Stamp-S3A.
-
----
-
-## V5 · ⚠ Stamp-S3A: 24 mm or 26 mm
-
-Vendor tables: Stamp-S3 = 24.0 × 18.0 × 4.7 mm; Stamp-S3A = **26.0** × 18.0 × 4.7 mm. But the two
-published STLs are byte-identical, `m5stack/M5_Hardware` publishes **no Stamp-S3A footprint**, and
-M5Stack ships the S3A on a DinMeter carrier whose published assets are unchanged.
-
-A 2 mm growth would break every host PCB. `inferred`: the 26.0 is probably a documentation error.
-**Not established.** Measure a real part before laying out a board.
-
----
-
-## V6 · ⚠ The rear FPC connectors are numbered in opposite directions
-
-`J1` (12 P) and `J3` (8 P) on the Stamp carry the same nets in the same physical order on both
-revisions, but their pin **numbers** run opposite ways — `J1` pin 1 = `VIN_5V` on v0.2, pin **12**
-on v0.3.3.
-
-**Unresolved:** either the connector was physically re-oriented (an existing display flex would
-mate backwards) or the symbol was renumbered with the footprint mirrored (nothing changed).
-Evidence leans to the latter — same connector part number, no new footprint, identical STLs — but
-that is inference.
-
-**Does not affect the DinMeter**, which does not use the Stamp's rear header. Does affect anyone
-attaching a flex to a bare Stamp-S3A: check
-[`S007-V033_PinMap_01.jpg`](../../../components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg)
-first. **That image was not OCR'd in this pass** — reading it would settle this.
-
----
-
-## V7 · The antenna claim is unquantified
-
-M5Stack: *"Optimized antenna design with better signal reception"* vs *"Conventional antenna
-design"*. **No dBi, no RSSI comparison, no method, no test conditions.**
-
-The schematics do show a real change — the match went from 3 elements
-(`L1` 2.2 nH, `C1` 2.2 pF, `C2` 2.0 pF) to 6 positions plus a filter on `CHIP_PU`, and
-`PROANT440` no longer appears as the `ANT1` value. So *something* was done. Whether it helps, and
-by how much, is **unmeasured**.
-
-This matters more than usual here, because the DinMeter is designed to be installed **behind a
-panel**, often in a metal cabinet — the worst RF case. **What would settle it:** RSSI at a fixed
-distance, v1.0 vs v1.1, same firmware, same AP.
-
----
-
-## V8 · Nothing about v1.1 has been tested on hardware
-
-No v1.1 unit was available. Every v1.1-specific claim in this record is derived from vendor
-documentation, published schematics and source code. See
-[`compatibility-and-status.md`](compatibility-and-status.md) §5.
-
-## Related
-
-[`../dinmeter/gaps-and-conflicts.md`](../dinmeter/gaps-and-conflicts.md) (items shared by both
-revisions) · [`stamp-s3-to-s3a-delta.md`](stamp-s3-to-s3a-delta.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md)
diff --git a/devices/m5stack/dinmeter-v1.1/market-and-pricing.md b/devices/m5stack/dinmeter-v1.1/market-and-pricing.md
deleted file mode 100644
index 51f65e7..0000000
--- a/devices/m5stack/dinmeter-v1.1/market-and-pricing.md
+++ /dev/null
@@ -1,136 +0,0 @@
-# DinMeter v1.1 — market and pricing
-
-All observations **2026-09-04**, from `shop.m5stack.com`'s Shopify JSON (`/products/<slug>.js`).
-USD, item price only, excluding shipping, tax and duty. Global store.
-
-Full market context, competitor prices and caveats:
-[`../dinmeter/market-and-pricing.md`](../dinmeter/market-and-pricing.md).
-
----
-
-## 1. The listing
-
-| Field | Value |
-|---|---|
-| Title | **M5Stack Din Meter v1.1 with M5StampS3A** |
-| Slug | `m5stack-din-meter-v1-1-with-m5stamps3a` |
-| SKU | **`K134-V11`** |
-| Shopify product id | `9014041182465` |
-| Variant id | `47570426593537` |
-| **Price** | **USD 24.50** |
-| Availability | **in stock** |
-| Created | `2026-01-30T10:02:16+08:00` |
-| Published | `2026-01-30T12:30:47+08:00` |
-| Tags | `ESP32-S3`, `STAMP` |
-| Shipping weight | 70 g |
-| Barcode | none |
-
-## 2. The headline: same price, and the old one is gone
-
-| Product | SKU | Price | Availability |
-|---|---|---|---|
-| **DinMeter v1.1** | K134-V11 | **USD 24.50** | in stock |
-| `[EOL]` DinMeter | K134 | USD 24.50 | **out of stock** |
-| `[EOL]` Stamp-S3 | S007 | USD 7.50 | **out of stock** |
-| Stamp-S3A | S007-V033 | USD 7.50 | in stock |
-
-**No premium was charged for the module upgrade.** Identical price, better module, and the older
-SKU withdrawn. From a buyer's point of view there is no decision to make: v1.1 is the only
-option, and it costs what the old one did.
-
-The `[EOL]` prefix is **M5Stack's own**, present in the title string returned by the API — not an
-inference.
-
-## 3. Lifecycle reading
-
-The DinMeter K134 and the Stamp-S3 S007 went end-of-life **together**. The Stamp-S3A appeared
-2025-09-11; the DinMeter v1.1 followed 4½ months later on 2026-01-30.
-
-That ordering is exactly what you would expect if the carrier was re-released to consume a new
-module whose predecessor was being retired — a **module-lifecycle event, not a product
-refresh** — and it is consistent with every other piece of evidence: no new schematic, no new
-STL, no new footprint, no new library release, no new board enum, and factory firmware untouched
-since 2024.
-
-## 4. Is it worth upgrading from v1.0?
-
-| Your situation | Answer |
-|---|---|
-| You own a working v1.0 | **No.** The only functional gains are module-level sleep-current figures, and the *board* still cuts its battery with a latch at 38.4 µA — a figure **identical on both product pages**. You would be paying USD 24.50 for a microamp improvement you cannot use |
-| You are buying new | **v1.1, obviously** — it is the only one in stock, at the same price |
-| You need K134 specifically to match a fleet | Vendor stock is gone. Distributors may hold some; **no distributor inventory was surveyed** (declared exclusion). Firmware compatibility is not a reason to insist on K134 — see [`compatibility-and-status.md`](compatibility-and-status.md) |
-| You are designing a new board around a Stamp | Use the **Stamp-S3A** (USD 7.50, in stock). Budget **0.6 A** on the 3.3 V rail, not 1 A, and add the GPIO38 line if you want the LED |
-
-## 5. Other Stamp-S3A products, same date
-
-| Product | Price | Note |
-|---|---|---|
-| M5StampS3A ESP32S3 Module (SMD) | USD 7.50 | |
-| M5StampS3A with 1.27 Header Pin | USD 7.50 | |
-| M5StampS3A with 2.54 Header Pin | USD 7.50 | SKU `S007-PIN254-V033`, published 2025-09-11 |
-| Air Quality Kit v1.1 with M5StampS3A (SEN55, SCD40) | USD 89.90 | the other v1.1-suffixed carrier M5Stack refreshed |
-
-The Air Quality Kit's parallel "v1.1 with M5StampS3A" naming is worth noting: **M5Stack applied
-the same module-substitution-and-rename treatment to more than one product**, which further
-supports reading the DinMeter v1.1 as a fleet-wide module transition rather than a redesign.
-
-## 6. Caveats
-
-Single seller (`shop.m5stack.com` only), item price only, no currency conversion, no price
-history available from the public JSON, one observation on one date, no used/refurbished market
-found, no clones found (a negative search result, not proof of absence), and **no distributor or
-marketplace sweep**. See [`../dinmeter/market-and-pricing.md`](../dinmeter/market-and-pricing.md) §6.
-
----
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| M5Stack Din Meter v1.1 with M5StampS3A | 2026-01-30 | Default Title | `K134-V11` | **USD 24.50** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 24.50, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `K134-V11`. Same USD 24.50 as the EOL v1.0 kit — **the revision did not change the price**.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/dinmeter-v1.1/media.md b/devices/m5stack/dinmeter-v1.1/media.md
deleted file mode 100644
index eedcf82..0000000
--- a/devices/m5stack/dinmeter-v1.1/media.md
+++ /dev/null
@@ -1,84 +0,0 @@
-# DinMeter v1.1 — images and provenance
-
-Machine-readable records: [`media/manifest.json`](media/manifest.json).
-
-**The family's product photography lives in the v1.0 record**
-([`../dinmeter/media.md`](../dinmeter/media.md), 10 images) and is not duplicated here. This page
-covers the five v1.1-specific images and one acquisition finding worth recording.
-
----
-
-## What is retained
-
-| # | File | Source | Format |
-|---|---|---|---|
-| 1 | `img-dff307df-….webp` | `static-cdn.m5stack.com` — the **only** image the v1.1 documentation page references that the v1.0 page does not | WebP |
-| 2–5 | `shop-{1,4,6,9}_….jpg` | `cdn.shopify.com`, from the v1.1 shop listing | **JPEG** |
-
-| Field | Value |
-|---|---|
-| Creator / rightsholder | **M5Stack Technology Co., Ltd** — corporate product photography, no individual credited |
-| Retrieved | 2026-09-04, all HTTP 200 |
-| Published/updated | **unknown** — no `Last-Modified` in the captured responses |
-| Licence | **unknown.** No statement on either page; footer asserts `Copyright © M5Stack Technology Co., Ltd. All rights reserved.` |
-| Redistribution status | `unknown` |
-| Disposition | `repository`, **unstaged pending user review** |
-| Modifications to bytes | **none** |
-
-## ⚠ Acquisition finding: Shopify serves JPEG under `.webp` URLs
-
-The four shop images have canonical URLs ending **`.webp`**:
-
-```
-https://cdn.shopify.com/s/files/1/0056/7689/2250/files/1_3a27efc4-…-dcf2d5d8f3f3.webp?v=1769738162
-```
-
-but the bytes returned begin `ff d8 ff e1 … Exif` — **JPEG**, not WebP. Shopify's CDN
-content-negotiates the image format and ignores the extension in the path.
-
-The magic-byte check caught it. The files were **renamed locally to `.jpg`** so the extension
-matches the content; the bytes are unmodified and the canonical URL is recorded exactly as
-served, with a `format_mismatch_note` on each manifest record.
-
-This is precisely the failure the research method warns about — *never save a file under an
-extension that misdescribes its content* — and it is worth knowing for any future M5Stack (or
-Shopify) image acquisition: **validate by magic bytes, not by URL suffix.** Recorded in
-[`../../../vendors/m5stack/README.md`](../../../vendors/m5stack/README.md) as a durable vendor
-trap.
-
-## Caveat on the captions
-
-The files were validated by magic bytes and hashed but **not visually rendered** in this pass —
-no image decoder was invoked. The manifest's captions are therefore generic ("Shop listing image
-4") rather than describing what each frame shows. Writing "rear view showing the DC terminal" for
-a file nobody looked at would be fabricated provenance.
-
-Rendering them and replacing the captions is a five-minute job that would materially improve this
-record.
-
-## ⚠ The real gap: nothing distinguishes v1.1 visually
-
-Searched and **not found**:
-
-| Wanted | Found |
-|---|---|
-| A v1.1 PCB photograph | **none** |
-| A v1.1 teardown at any stage | **none** |
-| A **side-by-side v1.0 / v1.1 comparison** photograph | **none** |
-| A photograph showing a Stamp-S3A soldered to a DinMeter carrier | **none** |
-| A readable shot of the Stamp-S3A's `U4` marking | **none** |
-
-That last one matters: a photograph of `U4`'s top marking is one of only two realistic ways to
-identify the Stamp-S3A's regulator
-([`components/unidentified/m5stack-stamp-s3a/dcdc-u4`](../../../components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md)),
-and a v1.0/v1.1 board comparison is the **only** way to test whether the carrier really is
-unchanged — the published assets being byte-identical proves only that the *documentation* is
-([`gaps-and-conflicts.md`](gaps-and-conflicts.md) V2).
-
-## Related images held elsewhere
-
-| Image | Where | Note |
-|---|---|---|
-| Stamp-S3A official pin map (`S007-V033_PinMap_01.jpg`, 693 286 B) | [`components/m5stack/stamp-s3a/artifacts/`](../../../components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg) | **Not OCR'd.** Reading it would settle the rear-FPC numbering question in [`stamp-s3-to-s3a-delta.md` §6b](stamp-s3-to-s3a-delta.md) |
-| Stamp-S3 official pin map (`S007_PinMap_01.jpg`) | [`components/m5stack/stamp-s3/artifacts/`](../../../components/m5stack/stamp-s3/artifacts/S007_PinMap_01.jpg) | the comparison baseline |
-| 10 × DinMeter product photography | [`../dinmeter/media/`](../dinmeter/media/) | applies to both revisions |
diff --git a/devices/m5stack/dinmeter-v1.1/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp b/devices/m5stack/dinmeter-v1.1/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp
deleted file mode 100644
index 607cb0e..0000000
Binary files a/devices/m5stack/dinmeter-v1.1/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter-v1.1/media/manifest.json b/devices/m5stack/dinmeter-v1.1/media/manifest.json
deleted file mode 100644
index f7a5dc1..0000000
--- a/devices/m5stack/dinmeter-v1.1/media/manifest.json
+++ /dev/null
@@ -1,140 +0,0 @@
-{
-  "$schema-note": "Image provenance manifest for devices/m5stack/dinmeter-v1.1. The bulk of the family's product photography is filed under devices/m5stack/dinmeter/media/ and is not duplicated here.",
-  "device": "m5stack/dinmeter-v1.1",
-  "generated": "2026-09-04",
-  "global_notes": [
-    "Retrieved 2026-09-04. Every file returned HTTP 200 and was validated by magic bytes.",
-    "IMPORTANT: the four shop.m5stack.com images have URLs ending .webp but the Shopify CDN served JPEG bytes. They were renamed locally to .jpg so the extension matches the content. Bytes unmodified; canonical URLs recorded as served. See format_mismatch_note.",
-    "Creator/rightsholder: M5Stack Technology Co., Ltd. No individual photographer credited.",
-    "Licence UNKNOWN; redistribution status unknown; disposition repository (unstaged pending review).",
-    "No image was cropped, rotated, annotated or watermark-stripped.",
-    "Captions are generic: the files were validated and hashed but NOT visually rendered in this pass. Describing frames nobody looked at would be fabricated provenance.",
-    "Shopify URLs carry a ?v= cache-buster that is part of the URL as served; it is retained.",
-    "GAP: no teardown, bare-PCB, or v1.1-vs-v1.0 comparison photograph was found anywhere."
-  ],
-  "images": [
-    {
-      "local_path": "media/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-      "filename": "img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-      "sha256": "82916ce50a40391698e3f15e57c2effe21ffcd81324601fec53e4a1459f7276f",
-      "bytes": 24884,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "doc-v1.1",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/DinMeter_v1.1",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (no Last-Modified in the captured response)",
-      "applies_to_revision": "K134-V11 (DinMeter v1.1)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "The only image the v1.1 documentation page references that the v1.0 page does not",
-      "alt_text": "Product image referenced by the M5Stack DinMeter v1.1 documentation page."
-    },
-    {
-      "local_path": "media/shop-1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.jpg",
-      "filename": "shop-1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.jpg",
-      "sha256": "c70624568aba92dcb4b006495dd7d895fa2b202b8db7f32c474b1cc0cec0c1e0",
-      "bytes": 82773,
-      "format": "JPEG (validated: ff d8 ff e1 magic, EXIF)",
-      "magic_ok": true,
-      "kind": "shop-v1.1",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.webp?v=1769738162",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (no Last-Modified in the captured response)",
-      "applies_to_revision": "K134-V11 (DinMeter v1.1)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none to the bytes; local FILENAME EXTENSION corrected from .webp to .jpg",
-      "caption": "Shop listing image 1 (primary product shot)",
-      "alt_text": "M5Stack DinMeter v1.1 shop listing photograph.",
-      "format_mismatch_note": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-    },
-    {
-      "local_path": "media/shop-4_65d27f99-973d-475b-97ef-db7c49e92619.jpg",
-      "filename": "shop-4_65d27f99-973d-475b-97ef-db7c49e92619.jpg",
-      "sha256": "40b2c4d3b9f960b1466ae1e8b80d81f5e5d7ce1a0f61941b2304193aa30e6e9c",
-      "bytes": 239490,
-      "format": "JPEG (validated: ff d8 ff e1 magic, EXIF)",
-      "magic_ok": true,
-      "kind": "shop-v1.1",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/4_65d27f99-973d-475b-97ef-db7c49e92619.webp?v=1769738162",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (no Last-Modified in the captured response)",
-      "applies_to_revision": "K134-V11 (DinMeter v1.1)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none to the bytes; local FILENAME EXTENSION corrected from .webp to .jpg",
-      "caption": "Shop listing image 4 (largest asset captured)",
-      "alt_text": "M5Stack DinMeter v1.1 shop listing photograph.",
-      "format_mismatch_note": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-    },
-    {
-      "local_path": "media/shop-6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.jpg",
-      "filename": "shop-6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.jpg",
-      "sha256": "7a57a9b3cafea316a45621a1957cd3cc8fd229fbc3d6378d581f06880f179b02",
-      "bytes": 58714,
-      "format": "JPEG (validated: ff d8 ff e1 magic, EXIF)",
-      "magic_ok": true,
-      "kind": "shop-v1.1",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.webp?v=1770110459",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (no Last-Modified in the captured response)",
-      "applies_to_revision": "K134-V11 (DinMeter v1.1)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none to the bytes; local FILENAME EXTENSION corrected from .webp to .jpg",
-      "caption": "Shop listing image 6",
-      "alt_text": "M5Stack DinMeter v1.1 shop listing photograph.",
-      "format_mismatch_note": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-    },
-    {
-      "local_path": "media/shop-9_8ec2f1c1-19bc-482b-851b-580bd9d86244.jpg",
-      "filename": "shop-9_8ec2f1c1-19bc-482b-851b-580bd9d86244.jpg",
-      "sha256": "6d4df52a29ff2a347780772a968be8de494a0e021b08652ae021f423c1e30936",
-      "bytes": 64105,
-      "format": "JPEG (validated: ff d8 ff e1 magic, EXIF)",
-      "magic_ok": true,
-      "kind": "shop-v1.1",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a",
-      "direct_url": "https://cdn.shopify.com/s/files/1/0056/7689/2250/files/9_8ec2f1c1-19bc-482b-851b-580bd9d86244.webp?v=1770110459",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (no Last-Modified in the captured response)",
-      "applies_to_revision": "K134-V11 (DinMeter v1.1)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none to the bytes; local FILENAME EXTENSION corrected from .webp to .jpg",
-      "caption": "Shop listing image 9",
-      "alt_text": "M5Stack DinMeter v1.1 shop listing photograph.",
-      "format_mismatch_note": "URL ends .webp but the CDN served JPEG bytes (magic ff d8 ff e1, with an EXIF/TIFF header). Shopify content-negotiates image format and ignores the extension in the path. The file was renamed locally from .webp to .jpg so the extension matches the content; the bytes are unmodified and the canonical URL is recorded as served."
-    }
-  ],
-  "counts": {
-    "retained": 5,
-    "webp": 1,
-    "jpeg": 4,
-    "teardown": 0,
-    "pcb": 0,
-    "revision_comparison": 0,
-    "url_extension_mismatches": 4
-  }
-}
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter-v1.1/media/shop-1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.jpg b/devices/m5stack/dinmeter-v1.1/media/shop-1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.jpg
deleted file mode 100644
index 6bb1914..0000000
Binary files a/devices/m5stack/dinmeter-v1.1/media/shop-1_3a27efc4-667e-411f-a608-dcf2d5d8f3f3.jpg and /dev/null differ
diff --git a/devices/m5stack/dinmeter-v1.1/media/shop-4_65d27f99-973d-475b-97ef-db7c49e92619.jpg b/devices/m5stack/dinmeter-v1.1/media/shop-4_65d27f99-973d-475b-97ef-db7c49e92619.jpg
deleted file mode 100644
index c3eca92..0000000
Binary files a/devices/m5stack/dinmeter-v1.1/media/shop-4_65d27f99-973d-475b-97ef-db7c49e92619.jpg and /dev/null differ
diff --git a/devices/m5stack/dinmeter-v1.1/media/shop-6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.jpg b/devices/m5stack/dinmeter-v1.1/media/shop-6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.jpg
deleted file mode 100644
index 59a10c7..0000000
Binary files a/devices/m5stack/dinmeter-v1.1/media/shop-6_d69930e8-d6ef-4d72-ad63-26be4b24e7d1.jpg and /dev/null differ
diff --git a/devices/m5stack/dinmeter-v1.1/media/shop-9_8ec2f1c1-19bc-482b-851b-580bd9d86244.jpg b/devices/m5stack/dinmeter-v1.1/media/shop-9_8ec2f1c1-19bc-482b-851b-580bd9d86244.jpg
deleted file mode 100644
index 74fb0db..0000000
Binary files a/devices/m5stack/dinmeter-v1.1/media/shop-9_8ec2f1c1-19bc-482b-851b-580bd9d86244.jpg and /dev/null differ
diff --git a/devices/m5stack/dinmeter-v1.1/performance.md b/devices/m5stack/dinmeter-v1.1/performance.md
deleted file mode 100644
index cc75dd1..0000000
--- a/devices/m5stack/dinmeter-v1.1/performance.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# DinMeter v1.1 — performance
-
-**Nothing was measured.** No v1.1 hardware was available. Shared silicon limits, derivable
-arithmetic and the full "not measured" list are in
-**[`../dinmeter/performance.md`](../dinmeter/performance.md)**.
-
----
-
-## 1. What actually changed, numerically
-
-Module-level only, and **all vendor claims with no published method** — no instrument, no sample
-count, no clock or radio state, no ambient temperature.
-
-| Workload | Stamp-S3 (v1.0) | Stamp-S3A (v1.1) | Δ |
-|---|---|---|---|
-| Sleep, `VIN_5V` | 310.89 µA | **6.84 µA** | **−97.8 %** |
-| Sleep, USB-C | 400.67 µA | **88.82 µA** | −77.8 % |
-| Standby, `VIN_5V` | 33.56 mA | **25.53 mA** | −23.9 % |
-| Standby, USB-C | 33.04 mA | **25.54 mA** | −22.7 % |
-| **Board standby (latched off, battery)** | **38.4 µA** | **38.4 µA** | **unchanged** |
-
-## 2. The important row is the last one
-
-**The board's own standby figure did not change.** M5Stack quotes `DC 4.2 V @ 38.4 µA` on *both*
-product pages, unchanged, while the module figures on the same pages *did* change.
-
-That is internally consistent and worth understanding: the DinMeter **cuts the battery with a
-latch** (GPIO46 → `Q4` → the `Q3`/`Q6` power path) rather than putting the SoC to sleep. In the
-latched-off state the module is not sleeping — it is **unpowered**. The residual 38.4 µA is the
-carrier's own LDO, dividers and latch network, and the module's sleep current does not enter into
-it.
-
-**Practical consequence: for the DinMeter's headline use case — a panel meter that wakes on an
-RTC alarm — the Stamp-S3A's dramatic sleep improvement buys you nothing.** It matters if you
-keep the module powered and use ESP32 sleep modes instead of the latch, which is not how this
-board is designed to be used.
-
-This is the single most useful thing in this document, and it is the opposite of what the
-headline "−98 % sleep current" suggests.
-
-## 3. Battery arithmetic, both revisions
-
-Bundled cell: 250 mA·h.
-
-| Mode | v1.0 | v1.1 |
-|---|---|---|
-| Continuously awake, radio up | 33.56 mA → **≈ 7.4 h** | 25.53 mA → **≈ 9.8 h** |
-| Latched off between RTC wakes | 38.4 µA → ≈ 271 days | 38.4 µA → **≈ 271 days (same)** |
-| 10 s awake per minute | ≈ 5.6 mA → ≈ 1.9 days | ≈ 4.3 mA → ≈ 2.4 days |
-
-`inferred` from vendor figures ÷ nominal capacity. Ignores ageing, the 3.0 V cut-off, converter
-efficiency at low load and wake inrush. **Do not design to these.**
-
-So the honest summary of the upgrade's power benefit: **roughly +30 % awake runtime, and no
-change at all to standby**.
-
-## 4. What is claimed but unmeasured
-
-| Claim | Source | Status |
-|---|---|---|
-| *"Optimized antenna design with better signal reception"* | Stamp-S3A page | **No dBi, no RSSI, no method.** The schematics do show a real topology change (3 → 6 matching positions plus a `CHIP_PU` filter, and `PROANT440` no longer named), so *something* was done — but whether it helps, and by how much, is unknown |
-| ST7789P3 performs like ST7789V2 | inferred | **Unverified** — no datasheet exists |
-
-The antenna claim matters more here than it would elsewhere: the DinMeter is designed to be
-installed **behind a panel**, often in a metal cabinet, which is the worst RF case. A real link-
-margin improvement would be genuinely valuable. It is simply not evidenced.
-
-## 5. Everything else
-
-Display throughput arithmetic, framebuffer cost (64 800 B with no PSRAM), silicon limits and the
-full list of unmeasured workloads:
-[`../dinmeter/performance.md`](../dinmeter/performance.md).
-
-## 6. If you have both revisions — the two measurements worth taking
-
-1. **RSSI at a fixed distance from the same AP, same firmware, v1.0 vs v1.1.** The only way to
-   test the antenna claim, and nobody appears to have done it.
-2. **Current in each state with a µA-capable meter.** Confirms or destroys the vendor figures —
-   in particular whether the board standby really is identical across revisions.
diff --git a/devices/m5stack/dinmeter-v1.1/pinouts-and-buses.md b/devices/m5stack/dinmeter-v1.1/pinouts-and-buses.md
deleted file mode 100644
index 923b8fb..0000000
--- a/devices/m5stack/dinmeter-v1.1/pinouts-and-buses.md
+++ /dev/null
@@ -1,109 +0,0 @@
-# DinMeter v1.1 — pinouts and buses
-
-**The GPIO map is identical to the DinMeter v1.0's, in every respect.**
-→ **[`../dinmeter/pinouts-and-buses.md`](../dinmeter/pinouts-and-buses.md)** is the full,
-schematic-derived reference: all 31 Stamp pads, every bus, the complete power tree, the
-designator census and the Grove wire-colour conflict. This page records only what is
-v1.1-specific, and the evidence that the rest genuinely is unchanged.
-
----
-
-## 1. Why one pinout document serves both
-
-| Evidence | Finding |
-|---|---|
-| Published schematic | The file linked from the v1.1 page (`.../1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf`) is **byte-identical** to the v1.0 file (`.../500/DIN_Meter_v1.0.pdf`), SHA-256 `03ec3353…6e4c070`. Its own filename contains `_v1.0_` |
-| Published STL | `DinMeter_v1.1.stl` is **byte-identical** to `DinMeter.stl`, SHA-256 `90f04d6a…` |
-| Dimension drawing | **The same URL** is linked from both pages |
-| Vendor PinMap | Identical assignments, signal for signal (compared below) |
-| M5Unified | **One** board enum, `board_M5DinMeter`, serves both. There is no v1.1 variant at master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb` (2026-09-04) |
-
-So the carrier's documentation has not been revised. That does **not** prove the PCB is
-unchanged — it proves the documentation is. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-## 2. The v1.1 PinMap, compared line by line
-
-Both product pages' PinMap tables, side by side. **Every assignment matches.**
-
-| Block | v1.0 page | v1.1 page | Same? |
-|---|---|---|---|
-| RTC SCL | G12 | G12 | ✔ |
-| RTC SDA | G11 | G11 | ✔ |
-| ENCODER B | G40 | G40 | ✔ |
-| ENCODER A | G41 | G41 | ✔ |
-| BEEP | G3 | G3 | ✔ |
-| BTN (WAKE) | G42 | G42 | ✔ |
-| Display CS | G7 | G7 | ✔ |
-| Display SCK | G6 | G6 | ✔ |
-| Display RS (D/C) | G4 | G4 | ✔ |
-| Display MOSI | G5 | G5 | ✔ |
-| Display RESET | G8 | G8 | ✔ |
-| Display BL | G9 | G9 | ✔ |
-| PORT.A | G13 / G15 | G13 / G15 | ✔ |
-| PORT.B | G2 / G1 | G2 / G1 | ✔ |
-| HOLD | GPIO46 | GPIO46 | ✔ |
-| **Section heading** | `ST7789V2` | **`ST7789P3`** | ✘ — the *only* difference in the whole table |
-
-## 3. What is v1.1-specific
-
-### 3.1 GPIO38 — new, internal to the module, and required for the RGB LED
-
-| Pin | v1.0 (Stamp-S3) | v1.1 (Stamp-S3A) |
-|---|---|---|
-| **GPIO38** (`DISP_BL`, inside the module) | Gates the Stamp's rear LCD-FPC backlight rail **only**. Unused on the DinMeter carrier | Gates `BL_3V3`, which now also supplies the **WS2812B-2020 RGB LED**. **Must be driven high** before the LED will light |
-
-GPIO38 is **not** one of the Stamp's 23 broken-out IOs and appears nowhere on the DinMeter
-carrier schematic. It is entirely internal, so there is no conflict — on this board it has
-exactly one job.
-
-Evidence and code: [`stamp-s3-to-s3a-delta.md` §3](stamp-s3-to-s3a-delta.md#3-change-1--the-rgb-led-is-no-longer-always-powered-the-only-source-compatibility-break)
-and [`../dinmeter/features/rgb-led.md`](../dinmeter/features/rgb-led.md).
-
-### 3.2 The display controller name
-
-`ST7789V2` → `ST7789P3`. Same six pins, same 135 × 240, same driver path, same GRAM gap
-(+52, +40) and same `INVON` requirement. **No datasheet exists for the ST7789P3** — see
-[`components/sitronix/st7789p3`](../../../components/sitronix/st7789p3/README.md).
-
-### 3.3 Everything internal to the module that changed
-
-Not visible from the carrier, but it is what you are actually buying:
-
-| Item | v1.0 | v1.1 |
-|---|---|---|
-| Module DC-DC | `M2` MUN3CAD01-SC, **1 A**, integrated inductor | `U4` unidentified 8-ball buck, **0.6 A**, external `L4` 2.2 µH |
-| Module load switch `U2` | SGM2578 (alt `WS4622C-4/TR`) | **AW35122FDR** |
-| Antenna match | 3 elements, `ANT1` = `PROANT440` | 6 positions + an `ESP_EN` filter, `ANT1` **unlabelled** |
-| Rear FPC pin numbering | `J1` pin 1 = `VIN_5V` | `J1` pin **12** = `VIN_5V` (**unresolved** whether physical) |
-
-Full treatment: [`stamp-s3-to-s3a-delta.md`](stamp-s3-to-s3a-delta.md).
-
-## 4. Quick reference — the pins you actually use
-
-Reproduced here so you do not have to open two documents for the common case. **Authoritative
-version, with per-pin evidence, is in
-[`../dinmeter/pinouts-and-buses.md`](../dinmeter/pinouts-and-buses.md) §2.**
-
-| Function | GPIO |
-|---|---|
-| Display: MOSI / SCLK / CS / D-C / RESET / backlight | 5 / 6 / 7 / 4 / 8 / 9 |
-| Encoder A / B | 41 / 40 |
-| Encoder push-button (also WAKE) | 42 |
-| Buzzer | 3 |
-| RTC I²C SDA / SCL (**internal bus**) | 11 / 12 |
-| PORT.A I²C SDA / SCL (**external bus**) | 13 / 15 |
-| PORT.B signals | 1 / 2 |
-| Battery ADC (divider ÷2) | 10 |
-| **Power hold — raise this in `setup()`** | **46** |
-| Stamp `G0` button / boot strap | 0 |
-| **RGB LED data** (internal) | 21 |
-| **RGB LED power enable (internal) — v1.1 only** | **38** |
-| Free, unlabelled on the schematic | 43, 44 (UART0) |
-| ⚠ Advertised free but **not** free — latch network fitted | 14, 39 |
-
-## Related
-
-[`../dinmeter/pinouts-and-buses.md`](../dinmeter/pinouts-and-buses.md) ·
-[`../dinmeter/resources-and-conflicts.md`](../dinmeter/resources-and-conflicts.md) ·
-[`stamp-s3-to-s3a-delta.md`](stamp-s3-to-s3a-delta.md) ·
-[`components/m5stack/stamp-s3a`](../../../components/m5stack/stamp-s3a/README.md)
diff --git a/devices/m5stack/dinmeter-v1.1/product-history-and-family.md b/devices/m5stack/dinmeter-v1.1/product-history-and-family.md
deleted file mode 100644
index 328861a..0000000
--- a/devices/m5stack/dinmeter-v1.1/product-history-and-family.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# DinMeter v1.1 — product history and family
-
-Full family treatment, the M5Dial/Capsule/AirQ relationship, culture and the naming traps are in
-**[`../dinmeter/product-history-and-family.md`](../dinmeter/product-history-and-family.md)**.
-
----
-
-## The v1.1 timeline
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2023-02-10 | Stamp-S3 (`S007`) listed | shop `.js` |
-| 2024-03-08 | **DinMeter (`K134`) listed**, USD 24.50 | shop `.js` |
-| **2025-09-11** | **Stamp-S3A (`S007-…-V033`) listed**, USD 7.50 | shop `.js` |
-| **2026-01-30** | **DinMeter v1.1 (`K134-V11`) announced.** Shop `created_at 10:02:16+08:00`, `published_at 12:30:47+08:00`; official r/M5Stack weekly post the same day | shop `.js` + Reddit — **two independent sources** |
-| 2026-09-04 | Observed: `K134` and `S007` **both `[EOL]` and out of stock**; `K134-V11` and `S007-V033` in stock | shop `.js` |
-
-## What the ordering tells you
-
-**The module came first, by 4½ months.** Stamp-S3A shipped 2025-09-11; the DinMeter v1.1
-followed on 2026-01-30; and the Stamp-S3 and DinMeter K134 went end-of-life **together**.
-
-That is a **module-lifecycle event**, not a product refresh. Every other artefact agrees:
-
-| Signal | Reading |
-|---|---|
-| No v1.1 schematic — the file served is byte-identical to v1.0's | the carrier was not redesigned |
-| No v1.1 STL — byte-identical to v1.0's | the enclosure was not redesigned |
-| No new KiCad footprint for the Stamp-S3A | the module drops into the same pads |
-| `M5DinMeter` library still `1.0.0` (2024-03-07) | no software work was needed |
-| M5Unified has one board enum for both | no software work was needed |
-| Factory-firmware source untouched since **2024-03-04** — 22 months before the v1.1 shipped | the evaluation firmware needed no attention |
-| Vendor's own comparison table has **one row**: *Main Controller* | M5Stack says so itself |
-| Price identical at USD 24.50 | no repositioning |
-
-## M5Stack did this to more than one product
-
-The shop also lists **"Air Quality Kit v1.1 with M5StampS3A (SEN55, SCD40)"** at USD 89.90 —
-the same `vN.N with M5StampS3A` naming pattern applied to a different carrier.
-
-So the DinMeter v1.1 is one instance of a **fleet-wide module transition**, not a decision about
-the DinMeter specifically. That framing is useful: it predicts, correctly, that the changes would
-be whatever the module forced and nothing more.
-
-## The "A" in Stamp-S3A
-
-Three independent signals say the "A" is a marketing label for **board revision v0.3.3 of the
-same `S007` product**, not a new part:
-
-1. SKU: `S007` → **`S007-V033`**
-2. Schematic filename: `Sch_M5StampS3_v0.2.pdf` → **`Sch_StampS3_v0.3.3.pdf`** (no "A" in it)
-3. Repository path: `Products/S007-V033_Stamp-S3A/`
-
-And the schematics bear it out — 48 of 59 designators are common, the SoC, crystal, USB
-receptacle, CC resistors, both FPC headers, the RGB LED, the button and the antenna designator
-are all unchanged. See [`stamp-s3-to-s3a-delta.md`](stamp-s3-to-s3a-delta.md) §1–2.
-
-## Naming traps specific to v1.1
-
-| Trap | Detail |
-|---|---|
-| Doc URL | v1.0 is `/en/core/**M5DinMeter**`; v1.1 is `/en/core/**DinMeter_v1.1**`. `/en/core/DinMeter` is a **404** |
-| Shop slug | v1.0 is `m5stack-din-meter-**w**-m5stamps3`; v1.1 is `m5stack-din-meter-v1-1-**with**-m5stamps3a` |
-| Stamp-S3A schematic filename | `Sch_StampS3_v0.3.3.pdf` — searching for "S3A" will not find it |
-| v1.1 schematic filename | `K134-V11_DIN_Meter_**v1.0**_2025_11_25_17_15_58.pdf` — it says v1.0 because it *is* v1.0 |
-| Stamp docs path | `/en/core/Stamp-S3A`, **not** `/en/stamp/…` (that path 404s) |
-
-## Community
-
-**No community project, board file or fork anywhere distinguishes v1.1 from v1.0.** Searched
-2026-09-04; see [`research-log.md`](research-log.md) §4. That is unsurprising given that the
-firmware is compatible — and it is also why the RGB-LED change has gone unremarked.
-
-→ [`../dinmeter/product-history-and-family.md`](../dinmeter/product-history-and-family.md)
diff --git a/devices/m5stack/dinmeter-v1.1/projects-and-community.md b/devices/m5stack/dinmeter-v1.1/projects-and-community.md
deleted file mode 100644
index c374a83..0000000
--- a/devices/m5stack/dinmeter-v1.1/projects-and-community.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# DinMeter v1.1 — projects and community
-
-**Every project, firmware port, forum attempt and social trace found for this device family is
-catalogued in [`../dinmeter/projects-and-community.md`](../dinmeter/projects-and-community.md).**
-It applies to v1.1 without amendment, because **no project anywhere distinguishes the two
-revisions**.
-
----
-
-## The v1.1-specific finding: nothing is v1.1-specific
-
-Searched 2026-09-04 (method in [`research-log.md`](research-log.md) §1):
-
-| Looked for | Result |
-|---|---|
-| A repository targeting DinMeter v1.1 specifically | **none** |
-| A board file, `#ifdef` or build flag distinguishing the revisions | **none** — `bmorcelli/Launcher`'s `m5stack-dinmeter` target, `espressif/esp-board-manager`'s `m5stack_dinmeter`, and `m5stack/M5DinMeter` all make no distinction |
-| A community project mentioning Stamp-S3A on a DinMeter | **none** |
-| An M5Unified issue or PR about the GPIO38 RGB-LED change | **none found** |
-| Reddit discussion of v1.1 beyond the launch post | **none** |
-| M5Stack forum threads | **inaccessible** — search API HTTP 401, HTML is a NodeBB JS shell |
-
-**One relevant social artefact exists for v1.1:**
-
-| Date | Sub | Score | Comments | Post | Evidence type |
-|---|---|---:|---:|---|---|
-| **2026-01-30** | r/M5Stack | 22–23 | **1** | ["Check out what's new this week!"](https://old.reddit.com/r/M5Stack/comments/1qr0ju2/check_out_whats_new_this_week/) — M5Stack's own weekly-products post announcing DinMeter v1.1 alongside the LLM-8850 Kit | **marketing** (vendor-posted) |
-
-Its body text is the same paragraph as the product page. It corroborates the launch date, which
-independently matches the shop listing's `created_at`. **That is the entire public discussion of
-this revision.**
-
-## Why that matters
-
-Compatibility is a good thing — but it means **nobody has hit the RGB-LED change yet, or if they
-have, they have not written it down where it is indexable**. The prediction in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) V1 is unconfirmed *and* uncontradicted, and it
-will stay that way until someone with a v1.1 unit tries it.
-
-If you are that person, the test is two lines and ten minutes, and it would be the single most
-useful contribution anyone could make to this record.
-
-## Ecosystem status (unchanged from v1.0)
-
-| Platform | DinMeter support |
-|---|---|
-| `bmorcelli/Launcher` (★2054, MIT) | **yes** — CI-built target, ships as `Launcher-m5stack-dinmeter.bin` via M5Burner |
-| `espressif/esp-board-manager` | **yes** — full ESP-IDF board definition |
-| `m5stack/uiflow-micropython` (UiFlow2) | **yes** |
-| `viniciusbo/m5-palnagotchi` (★81) | yes, as one of many targets |
-| **ESPHome** | **no** — 0 code-search hits |
-| **Tasmota** | **no** — 0 |
-| **Meshtastic** | **no** — 0 |
-| `pr3y/Bruce` (upstream Bruce) | **no** — the port is in `bmorcelli/Launcher`, not Bruce |
-
-→ [`../dinmeter/projects-and-community.md`](../dinmeter/projects-and-community.md) for the full
-catalogue with per-project evidence types, and
-[`../dinmeter/examples/catalog.json`](../dinmeter/examples/catalog.json) for dispositions.
diff --git a/devices/m5stack/dinmeter-v1.1/research-log.md b/devices/m5stack/dinmeter-v1.1/research-log.md
deleted file mode 100644
index bc09dcc..0000000
--- a/devices/m5stack/dinmeter-v1.1/research-log.md
+++ /dev/null
@@ -1,76 +0,0 @@
-# DinMeter v1.1 — research log
-
-The full log — every query, every source class, every negative result, the schematic-parsing
-method and its failure modes, and the declared exclusions — is
-**[`../dinmeter/research-log.md`](../dinmeter/research-log.md)**. Both revisions were researched
-in a single pass on **2026-09-04**.
-
-This page records only what was v1.1-specific.
-
----
-
-## 1. v1.1-specific discovery
-
-| Query / action | Result |
-|---|---|
-| `GET https://docs.m5stack.com/en/core/DinMeter_v1.1` | HTTP 200, 142 090 B |
-| `GET https://docs.m5stack.com/en/core/DinMeter` | **HTTP 404** — negative control |
-| Sitemap filtered for `Din` | **6 URLs only**: `/en/core/M5DinMeter`, `/en/core/DinMeter_v1.1`, 9 Arduino tutorial pages and 1 UiFlow2 page. **There is no separate v1.1 tutorial set** — the v1.1 page links the same `/en/arduino/m5dinmeter/*` pages |
-| `GET .../products/m5stack-din-meter-v1-1-with-m5stamps3a.js` | HTTP 200 — SKU, price, launch date |
-| `GET .../products/m5stack-din-meter-with-m5stamps3.js` | **HTTP 404** — wrong slug guess |
-| `GET .../products/m5stack-din-meter-w-m5stamps3.js` | HTTP 200 — `[EOL]`, out of stock. Slug recovered from a link in `bmorcelli/Launcher`'s README, **not** from M5Stack |
-| GitHub repo search for a v1.1-specific project | **none exist.** No repository, board file or fork distinguishes v1.1 from v1.0 |
-| `grep -r "StampS3A\|board_M5DinMeter" M5Unified/src` | **no v1.1 or S3A enum.** A negative finding, and the load-bearing evidence for the predicted RGB-LED failure |
-
-## 2. The three findings that came from hashing rather than reading
-
-Each was discovered by `sha256sum` during acquisition, not by comparing documents:
-
-1. **v1.1 schematic ≡ v1.0 schematic.** Two URLs, two filenames, one file (`03ec3353…`).
-2. **`DinMeter_v1.1.stl` ≡ `DinMeter.stl`** (`90f04d6a…`).
-3. **`Stamp-S3A.stl` ≡ `Stamp-S3.stl`** (`f72c1af2…`), and `m5stack/M5_Hardware` publishes **no
-   Stamp-S3A footprint at all**.
-
-Without hashing, all three would have been recorded as "v1.1 documentation obtained". This is
-the single strongest argument in the whole pass for hashing every artifact at acquisition time.
-
-## 3. The delta method
-
-Both Stamp schematics were fetched, their Altium `CO`/`PI`/`NL` marker layers parsed with the
-same glyph-deduplicating extractor used for the carrier board, and the two designator censuses
-diffed:
-
-```
-Stamp-S3 v0.2      : 55 designators (54 CO + C26 from visible text only)
-Stamp-S3A v0.3.3   : 59 designators
-removed (7) : D6, JP1, JP4, M2, R3, R6, R17
-added  (11) : C15, C16, C18, C19, C20, C24, C25, L4, L6, L7, U4
-common (48)
-```
-
-Then each changed IC was read net-by-net (`U2`, `U3`, `U4`/`M2`, `ANT1`, `J1`, `J3`) and the
-readings cross-checked against the vendor's two-row comparison table and the DinMeter v1.1 page's
-GPIO38 note. Result: [`stamp-s3-to-s3a-delta.md`](stamp-s3-to-s3a-delta.md). Retained diff:
-[`components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt`](../../../components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt).
-
-## 4. Searched and found nothing (v1.1-specific)
-
-| Question | Result |
-|---|---|
-| ST7789P3 datasheet | **not found** anywhere — Sitronix, M5Stack mirrors, general web |
-| Stamp-S3A `U4` part number | **not printed on the schematic**; not stated on any page |
-| A v1.1-specific schematic, STL, footprint or BOM | **none published** |
-| A v1.1-specific library release or board enum | **none** |
-| A v1.1 teardown or PCB photograph | **none found** |
-| A v1.1-specific community project | **none** |
-| An M5Unified issue/PR about the GPIO38 RGB-LED change | **none found** |
-| M5Stack forum threads about v1.1 | **inaccessible** — API HTTP 401, HTML is a NodeBB JS shell |
-
-## 5. Exclusions
-
-Same as the shared log: no hardware, no teardown, no RF or electrical measurement, no
-regulatory-database search, no video/blog/Chinese-platform search, no distributor price sweep,
-and the vendor forum was inaccessible. Additionally: **the Stamp-S3A pin-map JPEG was not
-OCR'd**, which is what would settle the rear-FPC numbering question.
-
-→ [`../dinmeter/research-log.md` §9](../dinmeter/research-log.md)
diff --git a/devices/m5stack/dinmeter-v1.1/resources-and-conflicts.md b/devices/m5stack/dinmeter-v1.1/resources-and-conflicts.md
deleted file mode 100644
index 4f0c79c..0000000
--- a/devices/m5stack/dinmeter-v1.1/resources-and-conflicts.md
+++ /dev/null
@@ -1,66 +0,0 @@
-# DinMeter v1.1 — resources and conflicts
-
-**The GPIO budget, peripheral budget, real conflicts, feature-combination analysis, power budget
-and flash layout are identical to the v1.0's** — same carrier, same pin map, same peripherals.
-
-→ **[`../dinmeter/resources-and-conflicts.md`](../dinmeter/resources-and-conflicts.md)**
-
----
-
-## v1.1 deltas
-
-### 1. One more internal pin has a job: GPIO38
-
-| Pin | v1.0 | v1.1 |
-|---|---|---|
-| **GPIO38** (internal to the Stamp module) | Gates the module's rear LCD-FPC backlight rail only. **Unused** on the DinMeter carrier | Gates `BL_3V3`, which also supplies the module's **WS2812B-2020 RGB LED**. Must be high for the LED to light |
-
-**No conflict.** GPIO38 is not one of the Stamp's 23 broken-out IOs, appears nowhere on the
-DinMeter carrier schematic, and nothing else can want it. On this board it has exactly one job:
-turning the status LED on.
-
-Cost: one `pinMode` + one `digitalWrite` at boot. No timer, no channel, no bus.
-
-### 2. Less 3.3 V headroom inside the module
-
-| | Stamp-S3 | Stamp-S3A |
-|---|---|---|
-| Module regulator | `M2` MUN3CAD01-SC | `U4` unidentified 8-ball buck |
-| Rated output | **1 A** | **0.6 A** |
-| Inductor | integrated | external `L4` 2.2 µH |
-| Output set by | `R6`/`R17` feedback divider | `VSEL1/2/3` pin straps |
-
-**A 40 % reduction in the module's 3.3 V budget, disclosed nowhere by M5Stack** — not in either
-specification table, not in the two-row comparison.
-
-**Unlikely to matter on a DinMeter:** the carrier generates its own `+3.3V` from `U4`
-BL8075CB5TR33 for the RTC, pull-ups and LCD FPC, and only draws the module's `3V3` pin lightly.
-**It does matter** for anyone taking 3.3 V out of a bare Stamp-S3A to power external loads.
-
-`inferred` from the `IOUT: 0~0.6A` annotation on the v0.3.3 sheet. See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) V4.
-
-### 3. Rear LCD FPC numbering — possibly reversed, irrelevant here
-
-`J1`/`J3` on the module are numbered in opposite directions between v0.2 and v0.3.3 for the same
-net order. **Unresolved** whether physical.
-
-**Does not affect the DinMeter**, which uses its own `FPC1` on the carrier and never touches the
-Stamp's rear header. Relevant only to bare-module users. See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) V6.
-
-### 4. Nothing else changed
-
-| Resource | v1.1 |
-|---|---|
-| 23 broken-out GPIOs | **identical list** |
-| Free user pins | **6** — GPIO1, 2, 13, 15 (Grove) + 43, 44 (UART0, unverified) |
-| ⚠ Advertised-free-but-not | **GPIO14, GPIO39** — latch networks fitted on both revisions |
-| SPI hosts / I²C / LEDC / PCNT / RMT / ADC | unchanged |
-| LEDC timer conflict (backlight vs buzzer) | **unchanged — still the one conflict that will surprise you** |
-| JTAG pins consumed by encoder + button | unchanged |
-| Flash / partitions | unchanged; still nothing published by M5Stack |
-| Power rails and limits | unchanged at board level |
-
-→ [`../dinmeter/resources-and-conflicts.md`](../dinmeter/resources-and-conflicts.md) for the
-complete tables.
diff --git a/devices/m5stack/dinmeter-v1.1/sources.md b/devices/m5stack/dinmeter-v1.1/sources.md
deleted file mode 100644
index 137185d..0000000
--- a/devices/m5stack/dinmeter-v1.1/sources.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# DinMeter v1.1 — sources
-
-v1.1-specific rows. The shared source table — vendor documentation, schematics, component
-datasheets, board support, community — is
-**[`../dinmeter/sources.md`](../dinmeter/sources.md)** (rows S-01 … S-37) and is not repeated.
-
-Schema: `ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path`.
-All retrievals 2026-09-04.
-
----
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| V-01 | DinMeter v1.1 product documentation (SKU K134-V11) | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/DinMeter_v1.1> | 2026-09-04 | page created ~2026-01-30; unversioned thereafter | **The primary v1.1 source.** Stamp-S3A, ST7789P3, the full specification table, the identical PinMap, Power On/Off, Download Mode, the **RGB LED / GPIO38** note, and the one-row Product Comparison table | JS-rendered; content extracted from the server-sent `#document` block. HTTP 200 | `artifacts/docs/docs-en-core-DinMeter_v1.1.txt` |
-| V-02 | DinMeter v1.1 documentation, printable export | M5Stack | primary | official PDF | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/DinMeter_v1.1.pdf` | 2026-09-04 | unversioned; regenerated per request | Same content plus product photography | 11 261 000 B, SHA-256 `617a9ea8039ed1fced04cf68de4e12ccd1759140f5f440778b0638b2cc811b46`. `%PDF` validated. **Archived** | [placeholder](artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.md) |
-| V-03 | DinMeter v1.1 "schematic" | M5Stack | primary | schematic | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf` | 2026-09-04 | **filename says `v1.0`** | That **no v1.1-specific schematic is published**. SHA-256 `03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070` — **byte-identical** to the v1.0 file at `.../500/DIN_Meter_v1.0.pdf` | 433 658 B. Retained deliberately despite the duplication: the duplication *is* the finding | `artifacts/schematic/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf` |
-| V-04 | DinMeter v1.1 structure model | M5Stack | primary | repository (STL) | `m5stack/M5_Hardware` → `Products/K134-V11_DinMeter_v1.1/Structures/DinMeter_v1.1.stl` | 2026-09-04 | HEAD `a240115c94b19ecf647f229c47fa9a8ce46ccdc4` (2026-08-17) | That no v1.1-specific mechanical model exists. SHA-256 `90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7` — **byte-identical** to `DinMeter.stl` | 573 284 B. Repository has **no `LICENSE` file** | `artifacts/mechanical/DinMeter_v1.1.stl` |
-| V-05 | M5Stack shop listing, DinMeter v1.1 | M5Stack | primary | store listing | `https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a.js` | 2026-09-04 | created 2026-01-30T10:02:16+08:00; published 2026-01-30T12:30:47+08:00 | **The launch date**, SKU `K134-V11`, USD 24.50, in stock, product id 9014041182465, variant 47570426593537, tags `ESP32-S3`/`STAMP`, shipping weight 70 g | Shopify JSON; price in USD; **no price history available** | `scratch/m5stack-dinmeter/shop/` |
-| V-06 | M5Stack shop listing, DinMeter K134 | M5Stack | primary | store listing | `https://shop.m5stack.com/products/m5stack-din-meter-w-m5stamps3.js` | 2026-09-04 | published 2024-03-08 | Title **`[EOL] M5Stack Din Meter w/ M5StampS3`**, `available: false` — i.e. **the predecessor is discontinued** | Slug uses `-w-`, not `-with-`; recovered from a link in `bmorcelli/Launcher`'s README, not from M5Stack | `scratch/m5stack-dinmeter/shop/` |
-| V-07 | Stamp-S3A product documentation | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/Stamp-S3A> | 2026-09-04 | — | The two-row Product Comparison table (RGB LED control logic; antenna design), 23 IOs identical to Stamp-S3, **26 × 18 × 4.7 mm**, and the improved power figures | ⚠ Its `DC-DC: MUN3CAD01-SC` row is **contradicted** by V-08 | `scratch/m5stack-dinmeter/docs/pages/` |
-| V-08 | Stamp-S3A schematic, board rev **v0.3.3** | M5Stack | primary | schematic | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf` | 2026-09-04 | v0.3.3 | **The evidence base for the whole v1.1 delta**: `U2` = AW35122FDR, `U3` WS2812B `VDD` ← `BL_3V3`, `U4` unidentified buck + `L4` 2.2 µH, rebuilt antenna match, `M2`/`D6`/`R3`/`R6`/`R17`/`JP1`/`JP4` removed | 369 766 B, SHA-256 `2f9610aecc5a5d2ee51b33c75df31cf90c7639d2997e7a2bb147ba8d46b46966`. **Filename says `StampS3`, not `StampS3A`** | `components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf` |
-| V-09 | Stamp-S3 schematic, board rev **v0.2** | M5Stack | primary | schematic | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2.pdf` | 2026-09-04 | v0.2 | The baseline the delta is measured against: `M2` = MUN3CAD01-SC, `U2` = SGM2578/`WS4622C-4/TR`, `U3` WS2812B `VDD` ← `VDD_3V3`, `ANT1` = PROANT440 | 348 884 B, SHA-256 `6d92e1aef6577838b9abffcf1adf6c86e1b0c8374fcd372af451bb58ef19eb94` | `components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.pdf` |
-| V-10 | Designator diff, Stamp-S3 v0.2 ↔ Stamp-S3A v0.3.3 | derived (this research pass) | derived | analysis | — | 2026-09-04 | 7 removed / 11 added / 48 common, from a complete `CO`-marker census of both sheets plus visible designator text | Derived from V-08 and V-09; regenerable — see [`../dinmeter/commands.md`](../dinmeter/commands.md) | `components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt` |
-| V-11 | Stamp-S3A dimension drawing | M5Stack | primary | drawing | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/STAMP-S3A.pdf` | 2026-09-04 | — | Module mechanical envelope | 95 380 B, SHA-256 `27ba520610b03e41…` | `components/m5stack/stamp-s3a/artifacts/STAMP-S3A-dimensions.pdf` |
-| V-12 | Stamp-S3A / Stamp-S3 structure models | M5Stack | primary | repository | `m5stack/M5_Hardware` @ `a240115c…` | 2026-09-04 | 2026-08-17 | `Stamp-S3A.stl` is **byte-identical** to `Stamp-S3.stl` (SHA-256 `f72c1af2d42930fc…`), and **no Stamp-S3A KiCad footprint exists** at that commit | Contradicts the vendor's 24 mm vs 26 mm size tables | `components/m5stack/stamp-s3{,a}/artifacts/` |
-| V-13 | Stamp-S3A official pin map | M5Stack | primary | diagram | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/S007-V033_PinMap_01.jpg` | 2026-09-04 | — | Official module pin map | 693 286 B. **NOT OCR'd in this pass** — reading it would settle the FPC-numbering question | `components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg` |
-| V-14 | Shop listings: Stamp-S3, Stamp-S3A | M5Stack | primary | store listing | `shop.m5stack.com/products/{m5stamp-esp32s3-module,m5stamps3a-with-2-54-header-pin}.js` | 2026-09-04 | 2023-02-10 / **2025-09-11** | Stamp-S3 = **`[EOL]`, out of stock**, USD 7.50; Stamp-S3A USD 7.50, in stock, published **2025-09-11** — i.e. 4½ months before the DinMeter v1.1 | Shopify JSON | `scratch/m5stack-dinmeter/shop/` |
-| V-15 | `m5stack/M5Unified` — absence of a v1.1 board enum | M5Stack | primary | repository | <https://github.com/m5stack/M5Unified> | 2026-09-04 | master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb` | **A negative finding, established by grep**: there is no `board_M5DinMeter_v11`, no `board_M5StampS3A`, and no GPIO38 enable step for any board. `_pin_table_other0` gives `board_M5DinMeter → GPIO_NUM_21` at `src/M5Unified.cpp:246` | The basis for the predicted RGB-LED failure; a source read, **not** a hardware test | *(reproducible from the commit)* |
-| V-16 | "Check out what's new this week!" | u/M5Stack (official) | community | social post | <https://old.reddit.com/r/M5Stack/comments/1qr0ju2/check_out_whats_new_this_week/> | 2026-09-04 | **2026-01-30** | Independent corroboration of the launch date | **marketing**, vendor-posted; 22–23 points, **1 comment**. Retrieved via `old.reddit.com` with UA `WhatsApp/2.23.20.0` (200) where `www.reddit.com` returns 403 | — |
-
----
-
-## Evidence notes
-
-- **The v1.1 delta rests almost entirely on V-08 vs V-09** — two schematics, parsed and diffed.
-  The vendor's own prose (V-01, V-07) agrees with the schematic reading on the RGB-LED change and
-  the antenna change, and **contradicts** it on the DC-DC part.
-- **V-03, V-04 and V-12 are negative findings established by hashing**, not by reading. They are
-  the reason this record is scoped as a revision document rather than a second full record.
-- **V-15 is a negative finding established by grep.** It is the load-bearing evidence for the
-  predicted RGB-LED failure, and it is a source read — not a test.
-- **Nothing in this record was verified on v1.1 hardware.**
diff --git a/devices/m5stack/dinmeter-v1.1/stamp-s3-to-s3a-delta.md b/devices/m5stack/dinmeter-v1.1/stamp-s3-to-s3a-delta.md
deleted file mode 100644
index b7f3f99..0000000
--- a/devices/m5stack/dinmeter-v1.1/stamp-s3-to-s3a-delta.md
+++ /dev/null
@@ -1,334 +0,0 @@
-# Stamp-S3 → Stamp-S3A: the complete delta
-
-**Why this document exists.** The DinMeter v1.1 is the DinMeter with a different core module
-soldered on it. Nothing else about the product changed that any published document shows. So
-"what is a Stamp-S3A?" *is* "what is a DinMeter v1.1?", and it deserves to be answered from
-primary evidence rather than from the two-row marketing table M5Stack provides.
-
-**Method.** Both modules' Altium-published schematics were fetched and their invisible
-`CO`/`PI`/`NL` marker layers parsed, giving a complete reference-designator census of each sheet
-and a net-level reading of every IC. The two censuses were diffed. Board-support source
-(M5Unified, Espressif's `esp-board-manager`, Bruce/Launcher) was read at pinned commits. Vendor
-prose was used only where it says something the schematics cannot.
-
-**Not measured.** No Stamp-S3A or DinMeter v1.1 hardware was available. Every current figure
-below is the vendor's.
-
-| Evidence marker | Meaning |
-|---|---|
-| **[SCH-3]** | `Sch_M5StampS3_v0.2.pdf` (Stamp-S3), SHA-256 `6d92e1aef6577838…`, parsed |
-| **[SCH-A]** | `Sch_StampS3_v0.3.3.pdf` (Stamp-S3A), SHA-256 `2f9610aecc5a5d2e…`, parsed |
-| **[DOC]** | `docs.m5stack.com` / `shop.m5stack.com`, retrieved 2026-09-04 |
-| **[SRC]** | Source at a cited `file:line` / pinned commit |
-| **[INF]** | Inference, reasoning stated |
-
----
-
-## 1. The answer in one table
-
-| Property | Stamp-S3 (`S007`) | Stamp-S3A (`S007-V033`) | Changed? | Evidence |
-|---|---|---|---|---|
-| **Board revision** | v0.2 | **v0.3.3** | ✔ | schematic filenames |
-| **SoC** | ESP32-S3FN8, LX7 ×2 @ 240 MHz | ESP32-S3FN8, LX7 ×2 @ 240 MHz | ✘ | **[DOC]**, **[SCH-3]**/**[SCH-A]** `U1` symbol on both |
-| **Flash** | 8 MB in-package | 8 MB in-package | ✘ | **[DOC]** |
-| **PSRAM** | **none** | **none** | ✘ | **[DOC]** (no PSRAM row on either page); `FN8` has none in package; Bruce/Launcher `build_unflags = -DBOARD_HAS_PSRAM` **[SRC]** |
-| **USB** | native USB-C on the module, `J2`, `R1`/`R2` 5.1 kΩ CC, `F1` fuse, `D14`, `JP3` | **identical designators, identical nets** | ✘ | **[SCH-3]**/**[SCH-A]** |
-| **Broken-out GPIOs** | 23: G0, G1–G15, G39–G44, G46 | **same 23, same list** | ✘ | **[DOC]** both pages, character-for-character |
-| **Pin pitch / mounting** | 2.54 mm + 1.27 mm; SMT/DIP/fly-wire | same | ✘ | **[DOC]** |
-| **Rear LCD FPC** | 0.5 mm, 12 P (`J1`) or 8 P (`J3`), `HDGC/0.5K-HX-8PWB/NC` | same connector, **pin numbering runs the other way** | ⚠ | **[SCH-3]**/**[SCH-A]**, §6 |
-| **RGB LED part** | WS2812B-2020 ×1, data GPIO21 | WS2812B-2020 ×1, data GPIO21 | ✘ | **[DOC]**, **[SCH]** `U3` on both |
-| **RGB LED supply** | `VDD_3V3` — **always on** | **`BL_3V3` — switched, needs GPIO38 high** | **✔ ← the only firmware-visible change** | §3 |
-| **Backlight/LED load switch** | `U2` = SGM2578 (alt `WS4622C-4/TR`) | `U2` = **AW35122FDR** | ✔ | §3 |
-| **DC-DC** | `M2` = MUN3CAD01-SC µPOL module, 1 A, integrated inductor, FB divider `R6`/`R17` | `U4` = **unidentified 8-ball buck**, `IOUT: 0~0.6A`, external `L4` 2.2 µH, `VSEL1/2/3` straps | ✔ | §5 |
-| **Antenna** | `ANT1` = **PROANT440**, 3-element match | `ANT1` **no part text**, 6-element match + `ESP_EN` filter | ✔ | §4 |
-| **User button** | ×1, GPIO0 | ×1, GPIO0 | ✘ | **[DOC]**, `S1` on both |
-| **Sleep, `VIN_5V`** | 310.89 µA | **6.84 µA** | ✔ **−98 %** | **[DOC]** |
-| **Sleep, USB-C** | 400.67 µA | **88.82 µA** | ✔ **−78 %** | **[DOC]** |
-| **Standby, `VIN_5V`** | 33.56 mA | **25.53 mA** | ✔ −24 % | **[DOC]** |
-| **Size** | 24.0 × 18.0 × 4.7 mm | 26.0 × 18.0 × 4.7 mm | ⚠ **contradicted by identical STLs** | §7 |
-| **Weight** | 3.0 g | 2.9 g | ✔ | **[DOC]** |
-| **Price** | USD 7.50 | **USD 7.50** | ✘ | shop `.js`, 2026-09-04 |
-| **Availability** | **`[EOL]`, out of stock** | in stock | ✔ | shop `.js`, 2026-09-04 |
-| **Shop first published** | 2023-02-10 | 2025-09-11 | — | shop `.js` |
-| **M5Unified board enum** | `board_M5StampS3` | **no `board_M5StampS3A` exists** — an S3A enumerates as `board_M5StampS3` | ✘ | **[SRC]** master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb` |
-
----
-
-## 2. The designator diff
-
-A complete `CO`-marker census of each sheet, plus visible designator text to catch markers the
-parser's negative-lookbehind rule discards. Retained at
-[`../../../components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt`](../../../components/m5stack/stamp-s3a/artifacts/stamp-s3-vs-s3a-designator-diff.txt).
-
-| | Count | Designators |
-|---|---:|---|
-| Stamp-S3 v0.2 total | 55 | — |
-| Stamp-S3A v0.3.3 total | 59 | — |
-| **Removed** | 7 | `D6`, `JP1`, `JP4`, **`M2`**, `R3`, `R6`, `R17` |
-| **Added** | 11 | `C15`, `C16`, `C18`, `C19`, `C20`, `C24`, `C25`, **`L4`**, `L6`, `L7`, **`U4`** |
-| **Common** | 48 | `ANT1`, `C1`–`C14`, `C17`, `C21`–`C23`, `C26`, `D1`–`D4`, `D14`, `F1`, `J1`–`J3`, `JP2`, `JP3`, `L1`–`L3`, `L5`, `M1`, `PHD1`, `R1`, `R2`, `R4`, `R5`, `R7`, `R16`, `S1`, `U1`, `U2`, `U3`, `X1` |
-
-Note what is **common**: the SoC (`U1`), the crystal (`X1`), the USB receptacle (`J2`), the CC
-resistors (`R1`/`R2`), both FPC headers (`J1`/`J3`), the RGB LED (`U3`), the button (`S1`), the
-antenna designator (`ANT1`) and the load switch designator (`U2`). This is a **revision, not a
-redesign** — which is exactly what the `S007` / `S007-V033` SKU relationship and the
-`v0.2` → `v0.3.3` schematic numbering already implied.
-
-Every added part clusters in two places: around `U4` (the new regulator and its passives) and
-around `ANT1` (the new match). Every removed part is a support component for the parts they
-replaced.
-
----
-
-## 3. Change 1 — the RGB LED needs GPIO38 *(the only source-compatibility break)*
-
-`U2` is the load switch feeding the rear LCD-FPC backlight rail. On **both** revisions its
-enable is `DISP_BL` = **ESP32-S3 GPIO38** (`U1` pad 43). What changed is the *part* and, far
-more importantly, **what its output feeds**.
-
-| | Stamp-S3 v0.2 | Stamp-S3A v0.3.3 |
-|---|---|---|
-| `U2` value text | `SGM2578` @ (520.5, 121.4) + `WS4622C-4/TR` @ (528.4, 128.6) | `AW35122FDR` @ (523.1, 121.4) |
-| `U2` `EN` (ball B2) | `DISP_BL` ← GPIO38 | `DISP_BL` ← GPIO38 |
-| `U2` `VOUT` (ball A1) | FPC backlight rail only | **`BL_3V3`** |
-| `U3` WS2812B-2020 `VDD` | **`VDD_3V3`** (always on) | **`BL_3V3`** (switched) |
-| `U3` `DI` | `SK_DIN` ← GPIO21 | `SK_DIN` ← GPIO21 |
-| Local decoupling | `C3` 100 nF/25 V | `C3` 100 nF/25 V |
-
-**[SCH-3]** `U3` `VDD` net `VDD_3V3`@(607.1,125.0) · **[SCH-A]** `U3` `VDD` net `BL_3V3`@(606.4,207.7).
-
-The vendor says the same thing in prose, on the DinMeter v1.1 page: **[DOC]**
-
-> "The device uses Stamp-S3A as its main controller. To optimize overall power consumption,
-> Stamp-S3A adds an independent electronic switch for the RGB LED power supply compared with the
-> previous Stamp-S3. Before controlling the RGB LED in software, set **GPIO38**, which controls
-> this switch, to a high level."
-
-and on the Stamp-S3A page's comparison table: *"RGB LED power is multiplexed with the reserved
-screen FPC bus backlight"* vs *"Powered as soon as power is applied"*.
-
-Schematic and prose agree exactly. This is the strongest-evidenced claim in this document.
-
-### Why it bites
-
-The AW35122's `EN` has an internal **~7.1 MΩ pull-down** (see
-[`components/awinic/aw35122`](../../../components/awinic/aw35122/README.md) §1.1), so `BL_3V3`
-comes up **off** at reset. Existing DinMeter firmware that lights the LED will run, compile and
-appear healthy — and the LED will simply stay dark.
-
-Worse, **M5Unified will not save you.** At master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`
-(2026-09-04):
-
-- `_pin_table_other0` (RGB LED) has `{ board_M5DinMeter, GPIO_NUM_21 }` at
-  `src/M5Unified.cpp:246`. **[SRC]**
-- There is **no `board_M5DinMeter_v11`** and **no `board_M5StampS3A`** enum anywhere in `src/`.
-  **[SRC]** (grep, `executed-success`)
-- There is **no GPIO38 enable step for any board** in the RGB-LED path. **[SRC]**
-
-So a v1.1 unit enumerates as `board_M5DinMeter`, gets GPIO21 for the LED, and never gets the
-rail turned on.
-
-**Status: `inferred`.** Predicted from vendor documentation + schematic + source read. **Not
-reproduced on hardware** — no v1.1 unit was available. If you have one, this is the first thing
-to test, and the result belongs in
-[`compatibility-and-status.md`](compatibility-and-status.md).
-
-### Portable workaround
-
-```cpp
-// Safe on both revisions. On Stamp-S3, GPIO38 is unconnected to anything the carrier
-// uses and driving it high is harmless; on Stamp-S3A it enables BL_3V3.
-pinMode(38, OUTPUT);
-digitalWrite(38, HIGH);
-delay(1);                 // let the rail settle before the first WS2812 frame
-// ... now drive GPIO21 as usual
-```
-`not-tested`. The 1 ms settle is prudence, not a documented requirement; the AW35122's typical
-rise time is 165 µs.
-
-> **On the DinMeter specifically, GPIO38 has exactly one job.** The DinMeter carrier does not use
-> the Stamp's rear FPC header at all — it drives its own 1.14 in panel backlight from **GPIO9**
-> through its **own** AW35122FDR (`U6`). GPIO38 is entirely internal to the module. So there is
-> no conflict and no cost: raise it once at boot and forget it.
-
----
-
-## 4. Change 2 — the antenna front end was rebuilt
-
-| | Stamp-S3 v0.2 | Stamp-S3A v0.3.3 |
-|---|---|---|
-| `ANT1` part text | **`PROANT440`** @ (75.1, 55.7) | **none printed** |
-| Match elements, `ANT1` → `ESP_LNA` | `L1` 2.2 nH, `C1` 2.2 pF, `C2` 2.0 pF — 3 elements | `L6` (0 R), `C19`, `C20` (**`NC`**), `L1` 2.7 nH, `C2` 2.2 pF, `C1` 1.8 pF — 6 positions, one unpopulated |
-| Extra network at `U1` pad 4 (`CHIP_PU`/`ESP_EN`) | none | `L7` 0 R + `C24` (3 pF) |
-| `C9` (crystal network) | 10 pF | 12 pF |
-| `C8` | 100 nF/25 V | 3 pF/25 V |
-| `L2` adjacent values | `12 pF`, `2 nH` | `2 nH` |
-
-**[SCH-3]** / **[SCH-A]**, value text nearest each `CO` marker.
-
-Two honest caveats:
-
-1. **Value-to-designator association is nearest-neighbour** and the antenna corner is dense.
-   `C19 ≈ 4.3 nH` is physically wrong for a capacitor and almost certainly belongs to `L6`.
-   Treat individual values as indicative; treat the **topology** change (3 → 6 positions plus a
-   `CHIP_PU` filter) as solid.
-2. **`PROANT440` does not appear anywhere on the v0.3.3 sheet** — searched in both single and
-   double-struck glyph forms, zero hits. Either the antenna part changed or its value text was
-   dropped from the drawing. **Not established which.**
-
-The vendor's claim is *"Optimized antenna design with better signal reception"* vs
-*"Conventional antenna design"* — **qualitative, with no dBi figure, no RSSI comparison and no
-test method**. Nothing found corroborates or refutes it. If you need the number, measure it.
-
----
-
-## 5. Change 3 — the regulator was replaced *(and the spec page is stale)*
-
-| | Stamp-S3 v0.2 | Stamp-S3A v0.3.3 |
-|---|---|---|
-| Designator | `M2` | `U4` |
-| Part | **`MUN3CAD01-SC`** — µPOL module: 1 A, 2.7–5.5 V in, 0.8–4.0 V out, 93 % peak η, **integrated inductor**, 2.9 × 2.3 × 1.05 mm | **not printed on the sheet** |
-| Pins | 6: `EN`, `GND`, `VIN`, `GND`, `FB`, `VOUT` | 8 balls: `A1 SW`, `A2 VIN`, `B1 EN`, `B2 GND`, `C1 VSEL1`, `C2 VOS`, `D1 VSEL2`, `D2 VSEL3` |
-| Sheet annotation | — | **`IOUT: 0~0.6A`** @ (209.4, 452.6) |
-| External inductor | none | **`L4` = `MWTC201608S2R2`** (2.2 µH, 2016-metric) |
-| Output set by | `R6` 100 kΩ / `R17` 22.1 kΩ feedback divider | **pin straps** `VSEL1/2/3`; `R6`, `R17` **deleted** |
-| Support passives | `C21`, `C22` 10 µF | `C15` 1 nF, `C16` 10 µF, `C18` 100 nF, `C21`/`C22`/`C25` 10 µF |
-
-### ⚠ The Stamp-S3A page still lists `MUN3CAD01-SC`
-
-Its specification table gives `DC-DC: MUN3CAD01-SC` and links
-`…/resource/docs/datasheet/Stamp/**S007 StampS3**/MUN3CAD01-SC.pdf` — the Stamp-S3's own
-directory. **[DOC]**
-
-But the string `MUN3CAD01` **does not occur anywhere** in `Sch_StampS3_v0.3.3.pdf`, `M2` is
-absent from the sheet, and the fitted part has `SW` + an external inductor + `VSEL` straps,
-which a µPOL module does not have. The two are not the same device.
-
-**Reading:** the row was carried over unedited. The schematic wins. `U4`'s part number is left
-**unidentified** rather than guessed —
-[`components/unidentified/m5stack-stamp-s3a/dcdc-u4/`](../../../components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md).
-No candidate part number is asserted anywhere in this repository.
-
-### The consequence nobody mentions
-
-**The new regulator is rated 0.6 A; the old one was 1 A.** That is a *reduction* in 3.3 V
-headroom, and the vendor does not mention it in either specification table or in the comparison
-row. It is unlikely to matter on a DinMeter (the carrier makes its own 3.3 V from `U4`
-BL8075CB5TR33 and only draws the module's `3V3` pin lightly), but it matters for anyone using a
-bare Stamp-S3A to power external 3.3 V loads. **`inferred` from the sheet annotation.**
-
----
-
-## 6. Change 4 — support parts, and the FPC numbering question
-
-| | v0.2 | v0.3.3 |
-|---|---|---|
-| `D6` 1N4148WT on `ESP_EN` | present | **removed** |
-| `L7` 0 R + `C24` on `ESP_EN` | — | **added** |
-| `R3` 10 kΩ/1 % on GPIO2 | present | **removed** |
-| `JP1`, `JP4` | present | **removed** |
-| `R7` 10 kΩ, `R16` 100 kΩ, `C23` 1 µF on `ESP_EN` | present | present |
-
-### The FPC headers are numbered in opposite directions
-
-`J1` (12 P) and `J3` (8 P) carry the **same nets in the same physical order** on both
-revisions, but their pin numbers run opposite ways:
-
-| Net | v0.2 pin | v0.3.3 pin |
-|---|---:|---:|
-| `J1` `VIN_5V` | 1 | **12** |
-| `J1` `DISP_CS` | 12 | **1** |
-| `J3` `DISP_CS` | 8 | **1** |
-| `J3` GPIO2 node | 1 | **8** |
-
-**[SCH-3]** / **[SCH-A]** from `PIJ10x` / `PIJ30x` markers.
-
-**Unresolved.** Either (a) the connector was physically re-oriented, in which case an existing
-display flex mates backwards, or (b) the symbol was renumbered and the footprint mirrored with
-it, in which case nothing changed. The schematic alone cannot distinguish them.
-
-Evidence leans to **(b)**: same connector part number, `m5stack/M5_Hardware` publishes **no
-Stamp-S3A footprint** at commit `a240115c94b19ecf647f229c47fa9a8ce46ccdc4`, and `Stamp-S3A.stl`
-is byte-identical to `Stamp-S3.stl`. **[INF]**
-
-**Irrelevant to the DinMeter** — the carrier does not use the Stamp's rear header. Relevant to
-anyone attaching a display flex to a bare Stamp-S3A: verify against
-[`S007-V033_PinMap_01.jpg`](../../../components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg)
-before powering up.
-
----
-
-## 7. Mechanical — 24 mm or 26 mm?
-
-| | Stamp-S3 | Stamp-S3A |
-|---|---|---|
-| Vendor size | 24.0 × 18.0 × 4.7 mm | **26.0** × 18.0 × 4.7 mm |
-| Published STL | `Stamp-S3.stl` | `Stamp-S3A.stl` |
-| STL SHA-256 | `f72c1af2d42930fc57a3db1bd3282568a3952095f77539016a12437d59d7df5d` | **identical** |
-| Published KiCad footprint | `Stamp-S3-SMD` / `-DIP` / `_PIN1.27_Socket` / `_PIN2.54_DIP` | **none** |
-
-**One of these is wrong and M5Stack has not said which.** A 2 mm growth would break every host
-PCB — and yet M5Stack ships the Stamp-S3A on a DinMeter carrier whose published PCB assets are
-unchanged from v1.0. That argues the footprint did not grow and the `26.0` is a documentation
-error. **`inferred`, not established.**
-
-If you are laying out for a Stamp-S3A: measure a real part, or ask M5Stack. Do not trust either
-number.
-
----
-
-## 8. Does existing DinMeter firmware run unmodified?
-
-**Yes — with one exception, and it is a silent one.**
-
-| Aspect | Verdict | Basis |
-|---|---|---|
-| Toolchain / target | Identical: `esp32s3`, 8 MB flash, **no PSRAM** | **[DOC]**; Bruce/Launcher `build_unflags = -DBOARD_HAS_PSRAM` **[SRC]** |
-| Board enum | Unchanged — v1.1 enumerates as `board_M5DinMeter`; M5Unified has no v1.1 or S3A variant | **[SRC]** master `8530f537…` |
-| Display (ST7789, GPIO4-9, gap 52/40, `INVON`, 40 MHz) | Unchanged | **[DOC]**, carrier schematic |
-| Rotary encoder (GPIO41/40) | Unchanged | **[DOC]**, **[SRC]** |
-| Button / wake (GPIO42) | Unchanged | **[SRC]** `M5Unified.cpp:3502-3505` |
-| Buzzer (GPIO3) | Unchanged | **[SRC]** `M5Unified.cpp:2921-2928` |
-| RTC (BM8563, GPIO11/12, 0x51) | Unchanged | **[SRC]** `M5Unified.cpp:96` |
-| PORT.A / PORT.B | Unchanged | **[SRC]** `M5Unified.cpp:96, 159` |
-| Power hold (GPIO46) | Unchanged | **[SRC]** `M5Unified.cpp:282` |
-| Battery ADC (GPIO10, ÷2) | Unchanged | **[SRC]** Bruce/Launcher `ANALOG_BAT_PIN=10`, *"ratio 2.0, matching M5Unified's board table"* |
-| Boot / download (`G0` held at power-on) | Unchanged | **[DOC]** identical wording on both Stamp pages |
-| Flash layout / partitions | Unchanged | no vendor change published |
-| **RGB LED (GPIO21)** | **Silently dark without `GPIO38 = HIGH`** | §3 |
-| Wi-Fi / BLE API | Unchanged; RF *performance* may differ | §4 |
-
-**So: do not recompile anything.** A binary built for DinMeter v1.0 will boot and run on v1.1.
-The only user-visible difference is that the Stamp's status LED stays off — which will read as
-"the LED is broken", not as "the firmware is wrong", and that is precisely why it is worth
-documenting loudly.
-
-Conversely, firmware written for v1.1 with the GPIO38 line in it runs unchanged on v1.0, because
-GPIO38 is unconnected on the older module's carrier path and driving it is harmless.
-
----
-
-## 9. What this means for a buyer
-
-- If you already own a DinMeter v1.0: **there is no reason to upgrade** unless you run on a
-  battery and care about a 300 µA → 7 µA sleep improvement, which on a device that already
-  latches its battery *off* at 38.4 µA is largely theoretical.
-- If you are buying now: **v1.1 is the only option.** Both `K134` and `S007` are marked `[EOL]`
-  and out of stock on `shop.m5stack.com` (2026-09-04).
-- Price is unchanged at USD 24.50.
-- If you are designing a *new* board around a Stamp module: use the S3A (the S3 is EOL), budget
-  for **0.6 A** on the 3.3 V rail rather than 1 A, and add the GPIO38 line if you want the LED.
-
----
-
-## Sources for this document
-
-Full rows with class, retrieval date and what each establishes: [`sources.md`](sources.md) and
-[`../dinmeter/sources.md`](../dinmeter/sources.md).
-
-Component records: [`components/m5stack/stamp-s3`](../../../components/m5stack/stamp-s3/README.md) ·
-[`components/m5stack/stamp-s3a`](../../../components/m5stack/stamp-s3a/README.md) ·
-[`components/awinic/aw35122`](../../../components/awinic/aw35122/README.md) ·
-[`components/sgmicro/sgm2578`](../../../components/sgmicro/sgm2578/README.md) ·
-[`components/murata/mun3cad01-sc`](../../../components/murata/mun3cad01-sc/README.md) ·
-[`components/unidentified/m5stack-stamp-s3a/dcdc-u4`](../../../components/unidentified/m5stack-stamp-s3a/dcdc-u4/README.md)
diff --git a/devices/m5stack/dinmeter/README.md b/devices/m5stack/dinmeter/README.md
deleted file mode 100644
index cdd90aa..0000000
--- a/devices/m5stack/dinmeter/README.md
+++ /dev/null
@@ -1,422 +0,0 @@
-# M5Stack DinMeter (SKU K134)
-
-> **Product ID** `K134` · **PCB/board revision** not printed on any published document — the
-> published schematic is titled `DIN_Meter_v1.0` · **Region** single worldwide SKU ·
-> **Status** superseded by [DinMeter v1.1 (K134-V11)](../dinmeter-v1.1/README.md) and no longer
-> listed on `shop.m5stack.com` (verified 2026-09-04) · **Research retrieval date** 2026-09-04
-
-A 1/32-DIN panel-cutout instrument head: a bright **orange rotary encoder knob** over a 1.14 in
-135 × 240 IPS LCD, on a carrier board that accepts 6–36 V DC, charges a Li-ion cell, keeps time
-with a battery-backed RTC and exposes two Grove ports. The compute is not on the carrier: it is
-an [M5Stamp-S3](../../../components/m5stack/stamp-s3/README.md) module soldered as `M1`.
-
-This record covers **K134, the original**. The revision that replaced it is documented
-separately at [`devices/m5stack/dinmeter-v1.1/`](../dinmeter-v1.1/README.md); read
-[§ Why two records](#why-two-records-and-not-one-or-three) before assuming they differ more than
-they do.
-
----
-
-## Evidence labelling
-
-Every consequential claim below carries one of these markers. Nothing is asserted from a
-candidate list or a near-miss part number.
-
-| Marker | Meaning | Evidence status |
-|---|---|---|
-| **[SCH]** | Read out of `K134_DIN_Meter_v1.0-schematic.pdf` by parsing Altium's invisible `CO`/`PI`/`NL` marker layer plus the visible text, cited by designator | `executed-success` for the extraction; `not-tested` electrically |
-| **[SRC]** | Read out of vendor or framework source at a cited `file:line` | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | `docs.m5stack.com` / `shop.m5stack.com`, retrieved 2026-09-04 | `not-tested` |
-| **[COM]** | Community source, non-authoritative | as stated per item |
-| **[INF]** | Inference, with the reasoning given | `inferred` |
-
-**No hardware was in hand for this pass.** Nothing below is `executed-success` on the device
-itself. Where a command is given it is labelled.
-
----
-
-## Identity and variants
-
-| Property | Value | Evidence |
-|---|---|---|
-| Marketed name | **DinMeter** (the docs page id is `M5DinMeter`; the page title is `DinMeter`) | **[DOC]** |
-| SKU | **K134** | **[DOC]** page header `SKU:K134`; **[SRC]** `m5stack/M5_Hardware` path `Products/K134_DinMeter/` |
-| Documentation URL | <https://docs.m5stack.com/en/core/M5DinMeter> | **[DOC]** HTTP 200 |
-| ⚠ Path trap | `https://docs.m5stack.com/en/core/DinMeter` returns **HTTP 404** — the obvious guess is wrong | **[DOC]** verified 2026-09-04 (negative control) |
-| Core module fitted | **Stamp-S3**, schematic symbol `STAMP-S3-SMD`, designator `M1`, 31 pads | **[SCH]** |
-| Display controller | **ST7789V2** | **[DOC]** specification row; datasheet mirrored by M5Stack |
-| Successor | DinMeter v1.1, SKU `K134-V11`, Stamp-S3A + ST7789P3 | **[DOC]** |
-| Regional/bundle variants | **None found.** One SKU, one bundle | **[DOC]** |
-| PCB revision markings | **Not established.** No teardown photograph of the silkscreen was inspected in this pass; the schematic PDF is titled `DIN_Meter_v1.0` and that is the only revision string published | **[SCH]**, **[INF]** for the gap |
-
-### Bundle contents
-
-1 × DinMeter, 1 × adhesive tape, 1 × 250 mAh polymer Li-ion battery, 1 × silk-screened sticker,
-1 × DC-JACK terminal input (6–36 V), 1 × back bracket. **[DOC]**
-
----
-
-## Why two records, and not one or three
-
-The evidence for "how different is v1.1?" is unusually blunt, and it points the opposite way
-from what two SKUs and two documentation pages suggest:
-
-| Asset | v1.0 (K134) | v1.1 (K134-V11) | SHA-256 |
-|---|---|---|---|
-| Schematic PDF | `.../500/DIN_Meter_v1.0.pdf` | `.../1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf` | **identical** — `03ec3353…6e4c070` |
-| Structure/STL | `Products/K134_DinMeter/…/DinMeter.stl` | `Products/K134-V11_DinMeter_v1.1/…/DinMeter_v1.1.stl` | **identical** — `90f04d6a…4aef00fbf7` |
-| Full GPIO PinMap | 12 signals | 12 signals | **identical assignments** |
-
-Two different URLs, two different filenames, the same bytes. M5Stack has published **no
-v1.1-specific schematic and no v1.1-specific mechanical model** — it re-served the v1.0 files
-under v1.1 names. **[SCH]** **[SRC]**
-
-So the honest structure is: **one full record (this one) plus a scoped revision record.**
-Writing a second full record would mean asserting differences the published evidence does not
-support. The revision record documents what genuinely changed — the core module, the display
-controller part number, and the consequences of both — and links here for everything shared.
-
----
-
-## What it is and visual identification
-
-Front: a **matte-orange knurled rotary knob** occupying roughly the left third of the face,
-with the 1.14 in landscape LCD to its right behind a rectangular window. The knob is the single
-most identifiable feature and the reason the device is recognisable from a thumbnail; no other
-M5Stack product pairs an orange knob with a DIN-cutout body. Body is dark grey/black plastic,
-53.0 × 30.0 × 32.0 mm, 17.8 g. **[DOC]**
-
-Rear: USB-C at one end, a 2-pin green screw terminal for 6–36 V DC, two HY2.0-4P Grove sockets
-(PORT.A red / PORT.B black), a 1.25 mm 2-pin JST battery socket, and a removable plastic back
-clip for mounting.
-
-Panel face: the 1/32 DIN standard cutout is **45 × 22.5 mm**. **[DOC]** That is the whole point
-of the industrial-design decision — it drops into an existing instrument panel, PLC cabinet or
-control box aperture with no bracket and no filing.
-
-See [`media.md`](media.md) for the retained images with full provenance.
-
----
-
-## Product history, family and culture
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2024-02-21 | `m5stack/M5DinMeter` Arduino library repository created — earliest dated artefact | **[SRC]** GitHub API `created_at` |
-| 2024-03-01 | `m5stack/M5DinMeter-UserDemo` repository created | **[SRC]** |
-| 2024-03-04 | UserDemo release `V0.1` published (the factory-firmware source) | **[SRC]** |
-| 2024-03-07 | M5DinMeter library release `1.0.0`; all six bundled examples dated `2024-03-07` | **[SRC]** |
-| 2026-01-30 | **DinMeter v1.1 announced.** Shop listing `created_at 2026-01-30T10:02:16+08:00`; r/M5Stack weekly-new-products post the same day | **[DOC]** **[COM]** |
-| 2026-08-03 | Last push to `m5stack/M5DinMeter` (library still `1.0.0`, no new release) | **[SRC]** |
-| 2026-09-04 | K134 absent from `shop.m5stack.com` search; only `m5stack-din-meter-v1-1-with-m5stamps3a` is listed | **[DOC]** |
-
-**Family.** The DinMeter is the flat, panel-mount member of a small M5Stack cluster that shares
-a single M5Unified code path: `board_M5Dial`, `board_M5DinMeter` and `board_M5Capsule` appear in
-the *same switch cases* for button reading, buzzer configuration and power-hold. **[SRC]**
-`M5Unified/src/M5Unified.cpp:3500-3506`, `:2921-2929`, `:2398-2402`. The M5Dial is the round
-one; the DinMeter is the rectangular DIN one; the AirQ is the boxy sensor one. All are Stamp-S3
-carriers. The `M5DinMeter.h` header guard is literally `#define M5DIAL_H` and its pin macros are
-named `DIAL_ENCODER_PIN_A/B` — the library was copied from M5Dial and the lineage was never
-cleaned up. **[SRC]** `M5DinMeter/src/M5DinMeter.h:1,8-9`.
-
-**Culture.** There barely is one. See [`projects-and-community.md`](projects-and-community.md):
-a broad search found **five** third-party GitHub repositories naming the device and **one**
-relevant Reddit post in the whole of `old.reddit.com`. This is a quiet, professional-niche
-product, not a maker phenomenon.
-
----
-
-## Key specifications
-
-Each functional part links to its component record.
-
-| Specification | Parameter | Component record | Evidence |
-|---|---|---|---|
-| Core module | **M5Stamp-S3** (`STAMP-S3-SMD`, `M1`) | [`components/m5stack/stamp-s3`](../../../components/m5stack/stamp-s3/README.md) | **[SCH]** **[DOC]** |
-| SoC | **ESP32-S3FN8**, Xtensa LX7 dual-core @ 240 MHz | [`components/espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) (same silicon family; **`FN8` = 8 MB in-package flash, no PSRAM**) | **[DOC]** |
-| Flash | 8 MB, in-package | ↑ | **[DOC]** |
-| PSRAM | **None.** `FN8` has no in-package PSRAM and none is fitted on either board | ↑ | **[DOC]** **[SCH]** (no PSRAM designator in the 84-part census) |
-| Wi-Fi / BLE | 2.4 GHz Wi-Fi + Bluetooth 5 LE (SoC), 3D antenna on the module | [`stamp-s3`](../../../components/m5stack/stamp-s3/README.md) | **[DOC]** |
-| Display | 1.14 in IPS, **135 × 240**, **ST7789V2**, SPI, 8-pin 0.5 mm FPC (`FPC1`, `FPC-0.5-8P`) | [`components/sitronix/st7789v2`](../../../components/sitronix/st7789v2/README.md) | **[DOC]** **[SCH]** |
-| Backlight switch | **AW35122FDR** load switch (`U6`), gate = `LCD_BL` | [`components/awinic/aw35122`](../../../components/awinic/aw35122/README.md) | **[SCH]** |
-| Rotary encoder | Incremental quadrature + push switch, on connector `J5` — **part number not published** | [`components/unidentified/m5stack-dinmeter/rotary-encoder`](../../../components/unidentified/m5stack-dinmeter/rotary-encoder/README.md) | **[SCH]** |
-| RTC | **BM8563** (`U5`), I²C 0x51, 32.768 kHz `Y2` ±20 ppm 12.5 pF | [`components/generic/bm8563`](../../../components/generic/bm8563/README.md) | **[SCH]** **[DOC]** |
-| Buzzer | Magnetic buzzer `LS1`, driven by `Q5` SS8050 NPN + `R25` 470 Ω, flyback `D6` 1N4148WT — **part number not published** | [`components/unidentified/m5stack-dinmeter/buzzer`](../../../components/unidentified/m5stack-dinmeter/buzzer/README.md) | **[SCH]** |
-| Wide-input DC-DC | **ME3116AM6G** (`U1`), 6–36 V → +5VIN, `L1` 10 µH, FB `R5` 56 kΩ / `R6` 10 kΩ | [`components/microne/me3116am6g`](../../../components/microne/me3116am6g/README.md) | **[SCH]** |
-| Battery charger | **TP4057** (`U2`), linear Li-ion, `R13` 3.3 kΩ programme resistor | [`components/generic/tp4057`](../../../components/generic/tp4057/README.md) | **[SCH]** **[DOC]** |
-| Battery boost | **SY7088** (`U3`), boost to +5VOUT, `L4` 1.5 µH, FB `R16` 52.3 kΩ / `R18` 15 kΩ | [`components/silergy/sy7088`](../../../components/silergy/sy7088/README.md) | **[SCH]** |
-| 3.3 V LDO | **BL8075CB5TR33** (`U4`) → +3.3V | [`components/belling/bl8075`](../../../components/belling/bl8075/README.md) | **[SCH]** |
-| Reset supervisor | **CN809J** (`U7`) on +5VIN | see [`pinouts-and-buses.md`](pinouts-and-buses.md) §Power | **[SCH]** |
-| USB | ESP32-S3 native USB OTG / Serial-JTAG, USB-C on the Stamp module | [`stamp-s3`](../../../components/m5stack/stamp-s3/README.md) | **[DOC]** **[SCH]** |
-| DC input | **6 – 36 V**, 2-pin 2.54 mm screw terminal `J1`, reverse/clamp `D13`+`D12` B5819W | [`pinouts-and-buses.md`](pinouts-and-buses.md) | **[DOC]** **[SCH]** |
-| Charge current | 100 mA | **[DOC]** |
-| Grove load | PORT.A 5 V @ 220 mA max; PORT.B 5 V @ 220 mA max | **[DOC]** |
-| Standby current | DC 4.2 V @ **38.4 µA** (battery power, latched off) | **[DOC]** |
-| Battery socket | 1.25 mm 2-pin (`J2`) | **[DOC]** **[SCH]** |
-| Power sources | USB / DC terminal / Li-ion battery | **[DOC]** |
-| Operating temperature | 0 – 40 °C | **[DOC]** |
-| Size / weight | 53.0 × 30.0 × 32.0 mm / 17.8 g; panel cutout 45 × 22.5 mm (1/32 DIN) | **[DOC]** |
-
-The specification table is the vendor's; the *component* column is not. Every part number in it
-was read off the schematic, matched to a designator, and cross-checked against the value text
-printed beside that designator. The full census is in
-[`artifacts/schematic/K134_DIN_Meter_v1.0-designator-value-census.txt`](artifacts/schematic/K134_DIN_Meter_v1.0-designator-value-census.txt).
-
----
-
-## Architecture and components
-
-The board is a **three-rail power tree feeding a single Stamp-S3 module**, with a latching
-power switch that the firmware must hold on.
-
-```
- J1 6–36 V ──D13/D12──► U1 ME3116AM6G buck ──► +5VIN ──┬──► U7 CN809J supervisor (RESET)
- (screw terminal)                                       │
-                                                        ├──► M1 pin13 "5V"  (Stamp-S3 VIN_5V)
- USB-C (on Stamp) ──────────────────────────────────────┘
-                                                             Stamp-S3 internal:
- J2 Li-ion 1.25-2P ──► U2 TP4057 charger ──► VBAT_OUT ──►      MUN3CAD01-SC → VDD_3V3
-                          U3 SY7088 boost ──► +5VOUT ──► J3/J4 Grove 5 V rails
-                          U4 BL8075CB5TR33 ──► +3.3V   ──► U5 RTC, pull-ups, FPC1 LCD
- Q3/Q6 AP40P05 P-FETs + Q4 LN2324DT2AG  =  battery power path / HOLD latch (G46)
-```
-
-**Power latch.** `HOLD` is `M1` pin 27 = **GPIO46**. **[SCH]** With no USB present, the board is
-held on only while GPIO46 is high; the wake sources are the encoder push-button (`WAKE`,
-GPIO42) and the RTC `INT` line. Drive GPIO46 low, or press RST, and the board disconnects the
-battery. This is the single most important thing to know before writing firmware — see
-[`features/power-and-battery.md`](features/power-and-battery.md).
-
-**Two I²C buses, not one.** The RTC sits on an *internal* bus (GPIO11/12) that is **not** the
-Grove PORT.A bus (GPIO13/15). **[SRC]** `M5Unified/src/M5Unified.cpp:96`. A Grove I²C unit
-cannot collide with the RTC.
-
-**GPIO38 and GPIO21 are inside the module.** Neither is broken out on the Stamp-S3's 23 IO pins,
-and neither appears on the DinMeter schematic. GPIO38 drives the Stamp's LCD-FPC backlight
-switch and GPIO21 drives its WS2812B RGB LED. **[SCH]** `Sch_M5StampS3_v0.2` `U1` pins 43 and
-27. This matters enormously for the v1.1 delta — see
-[`../dinmeter-v1.1/README.md`](../dinmeter-v1.1/README.md).
-
-Full wiring table: [`pinouts-and-buses.md`](pinouts-and-buses.md).
-Contention analysis: [`resources-and-conflicts.md`](resources-and-conflicts.md).
-
----
-
-## Common tasks / How do I...?
-
-| I want to… | Guide |
-|---|---|
-| Read the orange knob and its push-button | [`features/rotary-encoder-and-buttons.md`](features/rotary-encoder-and-buttons.md) |
-| Draw on the 135 × 240 screen, set brightness | [`features/display.md`](features/display.md) |
-| Keep time across power-off, wake on a schedule | [`features/rtc-and-timekeeping.md`](features/rtc-and-timekeeping.md) |
-| Make it beep | [`features/buzzer.md`](features/buzzer.md) |
-| Run it from 24 V, or from the battery, and not have it switch itself off | [`features/power-and-battery.md`](features/power-and-battery.md) |
-| Hang an I²C sensor or a GPIO peripheral off the Grove ports | [`features/porta-portb-expansion.md`](features/porta-portb-expansion.md) |
-| Get Wi-Fi or BLE up | [`features/wifi-and-ble.md`](features/wifi-and-ble.md) |
-| Mount it in a panel / on DIN rail | [`features/din-mounting-and-mechanical.md`](features/din-mounting-and-mechanical.md) |
-| Blink the RGB LED (and why it may not work on v1.1) | [`features/rgb-led.md`](features/rgb-led.md) |
-| Build and flash anything at all | [`development.md`](development.md) |
-| Put the factory firmware back | [`factory-firmware.md`](factory-firmware.md) |
-
----
-
-## Common uses and representative projects
-
-Demonstrated, with running code (**[COM]**, each a firsthand project by its author):
-
-- **`no-body-in-particular/m5din-hikoki`** (★25, C++, last push 2026-05-05) — a HiKOKI power-tool
-  battery analyser. The most-starred DinMeter project found anywhere.
-- **`Shark17e/M5DinMeter-KilnController`** (★1, C++, 2026-08-08) — ceramic-kiln PID controller
-  with auto-correction. Exactly the panel-instrument use case the form factor is for.
-- **`TuF3i/DinMeterDock`** (C, 2026-06-27) — a desktop dock controller.
-- **`kaz-mac/M5Authenticator`** — TOTP authenticator with a dedicated `DinMeterUI.h`.
-- **`aoiastro/susuFW`** — a multi-function firmware for the DinMeter.
-- **`bmorcelli/Launcher` / BruceDevices "Bruce"** — the DinMeter appears as a build target in
-  the Bruce pentest-firmware CI matrix.
-
-Vendor-intended, from the product page: smart-home monitoring and control, access control,
-industrial control, maker/DIY. **[DOC]**
-
-Full catalogue with lineage and disposition: [`projects-and-community.md`](projects-and-community.md).
-
----
-
-## Distinctive strengths
-
-- **The 1/32 DIN cutout is the product.** 45 × 22.5 mm is a real, existing aperture size in
-  installed panels. Nothing else in the ESP32 hobby/prosumer space drops into one.
-- **6–36 V input on-board.** No brick, no buck module glued to the back. A 24 V PLC cabinet
-  rail feeds it directly.
-- **A knob with real detents on a device that also has a battery, an RTC and a screen.** The
-  combination is what makes it a *meter* rather than a display.
-- **Genuinely low standby** — 38.4 µA latched off on battery **[DOC]**, because the latch cuts
-  the battery rather than sleeping the SoC.
-- **First-class framework support.** M5Unified has a `board_M5DinMeter` enum member with I²C,
-  Grove, buzzer, button, RGB and power-hold table entries. **[SRC]** Espressif's own
-  `esp-board-manager` ships a complete `m5stack_dinmeter` board definition. **[SRC]**
-
-## Shortcomings and constraints
-
-- **No PSRAM.** ESP32-S3FN8. Anything wanting a large LVGL framebuffer, a camera or a big TLS
-  heap will feel it. **[DOC]**
-- **Only 8 usable free GPIOs**, and four of them are the two Grove ports. The 23 Stamp IOs are
-  mostly consumed: display 6, encoder 2, RTC 2, buzzer 1, button 1, hold 1, battery ADC 1.
-- **The power latch is a footgun.** Fail to raise GPIO46 in `setup()` and the device dies the
-  moment you release the knob. Every first-time user hits this. **[DOC]** documents it; nothing
-  enforces it.
-- **The Arduino library is a thin M5Dial copy** with a stale header guard and no release since
-  `1.0.0` (2024-03-07). **[SRC]**
-- **Documentation is inconsistent about the Grove wire colours** — see
-  [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §1.
-- **0–40 °C operating range** rules out unheated outdoor cabinets. **[DOC]**
-- **The rotary encoder part number is not published**, so a replacement knob/encoder cannot be
-  sourced from the documentation alone.
-- **K134 is discontinued.** New units are v1.1 only.
-
----
-
-## Performance summary
-
-There are **no independent benchmarks of this device**, and none were produced in this pass. What
-exists is the vendor's two power figures and the silicon's headline numbers. Treat everything
-else as unmeasured. Details, method notes and what would need measuring:
-[`performance.md`](performance.md).
-
----
-
-## Pricing and availability
-
-| Date | Region | Seller | Item | Price | Status |
-|---|---|---|---|---|---|
-| 2026-09-04 | Global | shop.m5stack.com | **DinMeter (K134)** | — | **Not listed.** Shop search for "din meter" returns only the v1.1 SKU |
-| 2026-09-04 | Global | shop.m5stack.com | DinMeter v1.1 (K134-V11) | **USD 24.50** | In stock |
-
-Full observations, competitor prices, and the caveats: [`market-and-pricing.md`](market-and-pricing.md).
-
----
-
-## Competitors, equivalents and clones
-
-Detailed treatment — including the **Waveshare ESP32-S3-Knob-Touch-LCD-1.8** already documented
-in this repository, the M5Dial, and a roll-your-own encoder+ESP32 build — is in
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md). Short version: the
-Waveshare is a better *knob*, the M5Dial is a better *dial*, and neither fits a 1/32 DIN
-aperture or takes 36 V.
-
-No clones of the DinMeter were found on AliExpress or elsewhere in this pass. **[INF]** — that
-is a negative search result, not proof of absence; see [`research-log.md`](research-log.md).
-
----
-
-## Launch-era versus current market fit
-
-**2024 (launch).** Nothing else offered a DIN-cutout ESP32-S3 head with a knob at any price. The
-comparison set was "build it yourself" or "buy an industrial HMI at 10×". Strong fit.
-
-**2026 (now).** Still essentially uncontested on the *form factor*, but the SKU you can actually
-buy is v1.1. If your reason for choosing it is the cutout and the 6–36 V input, it remains the
-only sensible answer. If your reason is "a knob with a screen", the field has widened
-considerably and the DinMeter is neither the cheapest nor the nicest. See
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md).
-
-## When to use / when not to use
-
-**Use it when:** you have a 1/32 DIN aperture; you have 12/24 V available and no 5 V; you want a
-detented knob as the primary input; you need timekeeping across power loss; you are building a
-setpoint/monitor head rather than a general computer.
-
-**Do not use it when:** you need PSRAM, a camera, more than ~8 free GPIOs, an operating range
-outside 0–40 °C, a touchscreen, or a display larger than 1.14 in. Do not use it as a *first*
-ESP32 board — the power latch will bite.
-
-## Alternatives by tier
-
-See [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) § Alternatives by
-tier, which is dated and scoped by workload rather than repeated here.
-
----
-
-## Images and teardown/PCB views
-
-Ten official product images retained with full provenance; **no teardown or bare-PCB photograph
-of the DinMeter was located in this pass** — a real gap, recorded as such. See
-[`media.md`](media.md) and [`media/manifest.json`](media/manifest.json).
-
----
-
-## Community, editorial and project coverage
-
-[`projects-and-community.md`](projects-and-community.md) — including the searched-and-empty
-results, which are findings in their own right.
-
----
-
-## Documentation map
-
-| File | What is in it |
-|---|---|
-| [`pinouts-and-buses.md`](pinouts-and-buses.md) | Every net, every Stamp pad, cited to schematic designator or `file:line` |
-| [`development.md`](development.md) | Arduino / ESP-IDF / UiFlow2 / MicroPython, with honest command status |
-| [`factory-firmware.md`](factory-firmware.md) | What ships on it, where the source is, how to restore |
-| [`features/`](features/README.md) | Nine task-oriented guides |
-| [`coverage.md`](coverage.md) | Feature → hardware → docs → example → guide → test status |
-| [`resources-and-conflicts.md`](resources-and-conflicts.md) | GPIO/bus/timer/peripheral contention |
-| [`compatibility-and-status.md`](compatibility-and-status.md) | Working / partial / untested, keyed by revision and library version |
-| [`gaps-and-conflicts.md`](gaps-and-conflicts.md) | **Read this.** Four documented source conflicts |
-| [`sources.md`](sources.md) | Full source table with class, dates and what each establishes |
-| [`research-log.md`](research-log.md) | Every query, including the ones that found nothing |
-| [`commands.md`](commands.md) | Command ledger with execution status |
-| [`market-and-pricing.md`](market-and-pricing.md) | Dated, normalised price observations |
-| [`performance.md`](performance.md) | What is known, what is not, and what to measure |
-| [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) | vs Waveshare knob, M5Dial, DIY |
-| [`projects-and-community.md`](projects-and-community.md) | Every project, repo, port and forum trace found |
-| [`media.md`](media.md) | Image provenance |
-| [`examples/`](examples/best.md) | Example survey, catalogue and selection |
-| [`acquisition/`](acquisition/README.md) | Clean-clone reacquisition, machine-readable manifest |
-
-## Artifact layout
-
-```
-devices/m5stack/dinmeter/artifacts/
-├── schematic/
-│   ├── K134_DIN_Meter_v1.0-schematic.pdf            433 658 B  03ec3353…  ← primary evidence
-│   ├── K134_DIN_Meter_v1.0-schematic.bbox.xml        73 682 B  parsed marker layer
-│   ├── parse_dinmeter_sch.py                          3 198 B  the parser (re-runnable)
-│   ├── K134_DIN_Meter_v1.0-designator-value-census.txt          85 designators → values
-│   ├── K134_DIN_Meter_v1.0-designator-census.txt               full CO/PI/NL census + gaps
-│   ├── K134_DIN_Meter_v1.0-plaintext-layout.txt                sheet as readable rows
-│   └── M1-stamp-s3-pinout-from-schematic.txt                   all 31 Stamp pads
-├── mechanical/
-│   ├── K134-din_meter_asm_v1-dimensions.pdf         117 405 B  db42c8a9…
-│   └── DinMeter.stl                                 573 284 B  90f04d6a…  (= v1.1's file)
-├── docs/
-│   ├── docs-en-core-M5DinMeter.pdf → archive/…      7 459 888 B  8b3db00a…  ARCHIVED
-│   ├── docs-en-core-M5DinMeter.pdf.ARCHIVED.md        placeholder (recovery URLs, hash)
-│   └── docs-en-core-M5DinMeter.txt                    5 214 B  extracted page text
-└── source-snapshots/
-    ├── M5DinMeter-8ccbad72….tar.gz                    8 532 B  Arduino library @ HEAD
-    ├── M5DinMeter-UserDemo-d2fdfe44….tar.gz          74 231 B  factory-firmware source
-    └── dinmeter-board_{info,devices,peripherals}.yaml          Espressif esp-board-manager
-```
-
-Chip datasheets are **component** artifacts and live under `components/<vendor>/<part>/artifacts/`,
-not here — see the key-specification table for the links.
-
-## Known conflicts and unresolved identities
-
-Four, all documented with evidence and with what would settle them, in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md):
-
-1. **PORT.A / PORT.B wire colours.** The vendor PinMap and the schematic + M5Unified imply
-   opposite yellow/white assignments. Unresolved.
-2. **`S1`, `R20`, `Y1`** appear as visible designator text on the schematic with no recoverable
-   `CO`/`PI` marker. Partly an extraction limit, partly possibly real.
-3. **v1.1 assets are v1.0 assets.** Byte-identical schematic and STL under v1.1 filenames.
-4. **Stamp-S3A "DC-DC: MUN3CAD01-SC"** is contradicted by the v0.3.3 schematic, which contains
-   no such string. Carried into the [Stamp-S3A record](../../../components/m5stack/stamp-s3a/README.md).
-
----
-
-*Researched 2026-09-04. No hardware in hand. Vendor documentation, published Altium schematics,
-vendor and framework source, and a broad public-source sweep; see
-[`research-log.md`](research-log.md) for depth and exclusions.*
diff --git a/devices/m5stack/dinmeter/acquisition/README.md b/devices/m5stack/dinmeter/acquisition/README.md
deleted file mode 100644
index d8a1175..0000000
--- a/devices/m5stack/dinmeter/acquisition/README.md
+++ /dev/null
@@ -1,177 +0,0 @@
-# DinMeter — acquisition
-
-How to reproduce every artifact in this record from a clean clone. Machine-readable form:
-[`manifest.json`](manifest.json).
-
-**Everything below was executed successfully on 2026-09-04**, except where marked. All 20
-downloads returned HTTP 200 and validated by magic bytes; **zero failures**.
-
----
-
-## 0. Prerequisites
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-GH="$(gh auth token)"          # api.github.com limits per identity: 60/h -> 5000/h
-```
-
-No fallback User-Agent was needed for any `m5stack.com` host. `api.github.com` requires the token
-(no UA helps — the limit is per identity, and a 403 there carries `X-RateLimit-Remaining: 0`).
-
-## 1. Vendor documents — in execution order
-
-```bash
-cd devices/m5stack/dinmeter/artifacts
-
-# PRIMARY EVIDENCE: the schematic
-curl -fSL -A "$UA" -o schematic/K134_DIN_Meter_v1.0-schematic.pdf \
-  'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/500/DIN_Meter_v1.0.pdf'
-# expect 433658 B, sha256 03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070
-
-curl -fSL -A "$UA" -o mechanical/K134-din_meter_asm_v1-dimensions.pdf \
-  'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-din_meter_asm_v1.pdf'
-# expect 117405 B, sha256 db42c8a995b6d0bf8032ee32f60e65307dca42c7c48898b1760e183c0706e579
-
-# Documentation PDF (large -> archived; see the placeholder in docs/)
-curl -fSL -A "$UA" -o docs/docs-en-core-M5DinMeter.pdf \
-  'https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/M5DinMeter.pdf'
-# expect 7459888 B, sha256 8b3db00abbc7e31762c503b36d8406fd8c6e21bdd23f89538989031ca1b70b3a
-```
-
-**Validate before trusting** — M5Stack's CDN returns HTML for a wrong path with a 200 in some
-cases:
-
-```bash
-python3 -c "
-import sys
-for f in sys.argv[1:]:
-    m=open(f,'rb').read(5)
-    print('OK ' if m==b'%PDF-' else 'BAD', m, f)" schematic/*.pdf mechanical/*.pdf docs/*.pdf
-```
-
-## 2. Mechanical model (GitHub raw, pinned)
-
-```bash
-curl -fSL -o mechanical/DinMeter.stl \
- 'https://raw.githubusercontent.com/m5stack/M5_Hardware/a240115c94b19ecf647f229c47fa9a8ce46ccdc4/Products/K134_DinMeter/Structures/DinMeter.stl'
-# expect 573284 B, sha256 90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7
-# NOTE: this is byte-identical to Products/K134-V11_DinMeter_v1.1/Structures/DinMeter_v1.1.stl
-```
-
-## 3. Source snapshots (pinned commits)
-
-```bash
-curl -fSL -H "Authorization: Bearer $GH" \
-  -o source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz \
-  'https://api.github.com/repos/m5stack/M5DinMeter/tarball/8ccbad7297beb82a140f812e5606e060d8a5e0dc'
-# expect 8532 B, sha256 de47c4109635870506bb7a02040db496f82e5bbb22a5b1befe600a3985eb0f02
-
-curl -fSL -H "Authorization: Bearer $GH" \
-  -o source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz \
-  'https://api.github.com/repos/m5stack/M5DinMeter-UserDemo/tarball/d2fdfe44e9baf810f82335faa6f5962e9fc59a44'
-# expect 74231 B, sha256 af58e2cdaf565bb3f97daeadd02843a4cd3dc72f504446aa842d865eb9c4ec72
-```
-
-> **⚠ GitHub tarballs are not byte-stable across time.** `api.github.com/.../tarball/<sha>`
-> re-generates the archive, and gzip/mtime differences mean the SHA-256 above may not reproduce
-> even from the same commit. **The commit hash is the identity; the archive hash is a
-> convenience.** If they disagree, verify the *contents* against the commit.
-
-### Board-support files (small, high value)
-
-```bash
-for f in board_info board_devices board_peripherals; do
-  curl -fSL -o "source-snapshots/dinmeter-$f.yaml" \
-   "https://raw.githubusercontent.com/espressif/esp-board-manager/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/m5stack_boards/m5stack_dinmeter/$f.yaml"
-done
-# NOTE: the originals were fetched from the MOVING 'main' ref; the pinned form above is preferred.
-
-curl -fSL -o source-snapshots/launcher-m5stack-dinmeter-platformio.ini \
- 'https://raw.githubusercontent.com/bmorcelli/Launcher/main/boards/m5stack-dinmeter/platformio.ini'
-# ⚠ fetched from the MOVING 'main' ref on 2026-09-04. A future fetch may differ. No release was pinned at capture.
-```
-
-## 4. Media
-
-Ten WebP images from `static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/`. Filenames,
-URLs and hashes: [`../media/manifest.json`](../media/manifest.json).
-
-```bash
-python3 - <<'EOF'
-import json,urllib.request,hashlib,os
-m=json.load(open('../media/manifest.json'))
-for im in m['images']:
-    p=os.path.join('..',im['local_path'])
-    urllib.request.urlretrieve(im['direct_url'], p)
-    b=open(p,'rb').read()
-    assert b[:4]==b'RIFF' and b[8:12]==b'WEBP', p
-    assert hashlib.sha256(b).hexdigest()==im['sha256'], p
-    print('ok', p)
-EOF
-```
-
-## 5. Regenerating the derived analysis
-
-Seven files under `artifacts/schematic/` are derived from the schematic PDF, not downloaded.
-
-```bash
-# pdfminer.six is required. On a host without poppler/pypdf:
-uv venv /tmp/.pdfvenv && uv pip install --python /tmp/.pdfvenv/bin/python pdfminer.six
-# NOTE: pymupdf installs but fails to import on NixOS (missing libstdc++.so.6). pdfminer.six is pure Python and works.
-
-/tmp/.pdfvenv/bin/python <path-to>/pdf_bbox.py \
-    artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf \
-  > artifacts/schematic/K134_DIN_Meter_v1.0-schematic.bbox.xml
-
-python3 artifacts/schematic/parse_dinmeter_sch.py \
-    artifacts/schematic/K134_DIN_Meter_v1.0-schematic.bbox.xml \
-  > artifacts/schematic/K134_DIN_Meter_v1.0-designator-census.txt
-```
-
-**`pdf_bbox.py` must deduplicate glyphs** on rounded `(x0,y0,x1,y1,char)`. Altium draws the
-marker layer twice at identical coordinates; without dedup the copies interleave and `PIJ10101`
-extracts as `PPIIJJ110011` — legible-looking and wrong. See [`../commands.md`](../commands.md) §4.
-
-## 6. Component artifacts — fetched here but filed elsewhere
-
-Filed by what they *describe*, not by what was being researched:
-
-| Artifact | Lives at |
-|---|---|
-| ST7789V2 datasheet (3 216 854 B) | `components/sitronix/st7789v2/artifacts/` |
-| BM8563 datasheet (590 599 B) | `components/generic/bm8563/artifacts/` |
-| TP4057 datasheet (628 588 B) | `components/generic/tp4057/artifacts/` |
-| MUN3CAD01-SC datasheet (2 045 960 B) | `components/murata/mun3cad01-sc/artifacts/` |
-| Stamp-S3 schematic, footprints, STL, STEP, pin map | `components/m5stack/stamp-s3/artifacts/` |
-| Stamp-S3A schematic, dimensions, STL, pin map | `components/m5stack/stamp-s3a/artifacts/` |
-
-## 7. Not acquired
-
-| Artifact | Why | Reacquisition |
-|---|---|---|
-| **Factory firmware binary** | Distributed only through M5Burner, which resolves images at run time from an undocumented endpoint | **manual** — run M5Burner, search "DinMeter", *DinMeter User Demo Easyloader*. Or rebuild from the MIT source (A-14) |
-| **UiFlow2 firmware binary** | Same channel, same problem | **manual** |
-| **ST7789P3 datasheet** | Does not exist publicly; M5Stack removed the display datasheet link on the v1.1 page rather than replacing it | **lost** |
-| **ME3116AM6G / SY7088 / BL8075 / SGM2578 datasheets** | Not published by any locatable source | **lost** |
-| **Gerbers / PCB / BOM** | M5Stack publishes schematics and STLs only | **blocked** |
-| **M5Unified / M5GFX source** | Large and canonical; reproducible from the commits in [`../sources.md`](../sources.md) | **automatic** |
-
-## 8. Verify
-
-```bash
-cd devices/m5stack/dinmeter
-python3 - <<'EOF'
-import json,hashlib,os
-m=json.load(open('acquisition/manifest.json')); bad=0
-for a in m['artifacts']:
-    p=a['destination'].replace('devices/m5stack/dinmeter/','')
-    if a['disposition']=='archive':
-        print('skip (archived, placeholder holds the hash):', p); continue
-    if not os.path.exists(p): print('MISSING', p); bad+=1; continue
-    got=hashlib.sha256(open(p,'rb').read()).hexdigest()
-    if a['expected_sha256'] and got!=a['expected_sha256']:
-        print('HASH MISMATCH', p); bad+=1
-print('failures:', bad)
-EOF
-```
-`not-tested` from a clean clone; it is the same logic used to build the manifest, run in reverse.
diff --git a/devices/m5stack/dinmeter/acquisition/manifest.json b/devices/m5stack/dinmeter/acquisition/manifest.json
deleted file mode 100644
index 34e9db1..0000000
--- a/devices/m5stack/dinmeter/acquisition/manifest.json
+++ /dev/null
@@ -1,839 +0,0 @@
-{
- "$schema-note": "Acquisition manifest for devices/m5stack/dinmeter. Machine-readable provenance for every artifact, tracked or not. Fields per the hardware-device-research acquisition-manifest requirement.",
- "device": "m5stack/dinmeter",
- "generated": "2026-09-04",
- "retrieval_agent": "curl 8.x with a Chrome-131 User-Agent for m5stack.com hosts; gh auth token for api.github.com",
- "artifacts": [
-  {
-    "id": "fcc-2AN3WM5DINMETER-7497866",
-    "kind": "regulatory-exhibit",
-    "canonical_url": "https://fccid.io/2AN3WM5DINMETER/Test-Report/Antenna-Specification-7497866.pdf",
-    "fallback_urls": [
-     "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497866",
-     "https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497866.pdf",
-     "https://fccid.io/2AN3WM5DINMETER",
-     "https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/Test-Report/Antenna-Specification-7497866.pdf"
-    ],
-    "sha256": "0728acb7f328e39ceb9c466d8ca99689211002d4f3dda9a1f4c452dd7ebb498c",
-    "bytes": 822846,
-    "destination": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf",
-    "retrieved": "2026-09-11",
-    "upstream_version_or_date": "2024-07-23",
-    "fcc_id": "2AN3WM5DINMETER",
-    "fcc_document_id": "7497866",
-    "exhibit_type": "Test Report",
-    "exhibit_title_as_filed": "Antenna Specification",
-    "grant_date": "2024-07-23",
-    "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-    "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-    "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-    "license_evidence": "FCC Equipment Authorization System publication",
-    "redistribution_status": "allowed",
-    "disposition": "archive",
-    "repo_state": "placeholder-only",
-    "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf",
-    "placeholder": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf.ARCHIVED.md",
-    "extraction": null,
-    "target_hardware": "devices/m5stack/dinmeter",
-    "reacquisition": "automatic",
-    "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-    "last_verified": "2026-09-11",
-    "notes": "Filed by the round-2 index merge, 2026-09-11."
-   },
-   {
-    "id": "fcc-2AN3WM5DINMETER-7497872",
-    "kind": "regulatory-exhibit",
-    "canonical_url": "https://fccid.io/2AN3WM5DINMETER/External-Photos/External-Photos-7497872.pdf",
-    "fallback_urls": [
-     "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497872",
-     "https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497872.pdf",
-     "https://fccid.io/2AN3WM5DINMETER",
-     "https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/External-Photos/External-Photos-7497872.pdf"
-    ],
-    "sha256": "b5aac335a6631663b90352c1edbc7926522235682d3b73c91db7731c2a0d5f0e",
-    "bytes": 2123431,
-    "destination": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf",
-    "retrieved": "2026-09-11",
-    "upstream_version_or_date": "2024-07-23",
-    "fcc_id": "2AN3WM5DINMETER",
-    "fcc_document_id": "7497872",
-    "exhibit_type": "External Photos",
-    "exhibit_title_as_filed": "External Photos",
-    "grant_date": "2024-07-23",
-    "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-    "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-    "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-    "license_evidence": "FCC Equipment Authorization System publication",
-    "redistribution_status": "allowed",
-    "disposition": "archive",
-    "repo_state": "placeholder-only",
-    "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf",
-    "placeholder": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf.ARCHIVED.md",
-    "extraction": null,
-    "target_hardware": "devices/m5stack/dinmeter",
-    "reacquisition": "automatic",
-    "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-    "last_verified": "2026-09-11",
-    "notes": "Filed by the round-2 index merge, 2026-09-11."
-   },
-   {
-    "id": "fcc-2AN3WM5DINMETER-7497876",
-    "kind": "regulatory-exhibit",
-    "canonical_url": "https://fccid.io/2AN3WM5DINMETER/Label/FCC-ID-Label-7497876.pdf",
-    "fallback_urls": [
-     "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497876",
-     "https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497876.pdf",
-     "https://fccid.io/2AN3WM5DINMETER",
-     "https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/Label/FCC-ID-Label-7497876.pdf"
-    ],
-    "sha256": "87bc3655794390cccabd01307810bd9f4f15ef515e23fbdf07b4efea395ef968",
-    "bytes": 357530,
-    "destination": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-id-label.pdf",
-    "retrieved": "2026-09-11",
-    "upstream_version_or_date": "2024-07-23",
-    "fcc_id": "2AN3WM5DINMETER",
-    "fcc_document_id": "7497876",
-    "exhibit_type": "ID Label/Location Info",
-    "exhibit_title_as_filed": "FCC ID Label",
-    "grant_date": "2024-07-23",
-    "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-    "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-    "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-    "license_evidence": "FCC Equipment Authorization System publication",
-    "redistribution_status": "allowed",
-    "disposition": "repository",
-    "repo_state": "untracked",
-    "archived_to": null,
-    "placeholder": null,
-    "extraction": null,
-    "target_hardware": "devices/m5stack/dinmeter",
-    "reacquisition": "automatic",
-    "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-    "last_verified": "2026-09-11",
-    "notes": "Filed by the round-2 index merge, 2026-09-11."
-   },
-   {
-    "id": "fcc-2AN3WM5DINMETER-7497877",
-    "kind": "regulatory-exhibit",
-    "canonical_url": "https://fccid.io/2AN3WM5DINMETER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7497877.pdf",
-    "fallback_urls": [
-     "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497877",
-     "https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497877.pdf",
-     "https://fccid.io/2AN3WM5DINMETER",
-     "https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7497877.pdf"
-    ],
-    "sha256": "aeb323a16a2ad99ca84494c240a74dbc768636ef8cbbbc5d6679a9b675ae617a",
-    "bytes": 126464,
-    "destination": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf",
-    "retrieved": "2026-09-11",
-    "upstream_version_or_date": "2024-07-23",
-    "fcc_id": "2AN3WM5DINMETER",
-    "fcc_document_id": "7497877",
-    "exhibit_type": "RF Exposure Info",
-    "exhibit_title_as_filed": "FCC RF Exposure-MPE",
-    "grant_date": "2024-07-23",
-    "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-    "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-    "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-    "license_evidence": "FCC Equipment Authorization System publication",
-    "redistribution_status": "allowed",
-    "disposition": "archive",
-    "repo_state": "placeholder-only",
-    "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf",
-    "placeholder": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md",
-    "extraction": null,
-    "target_hardware": "devices/m5stack/dinmeter",
-    "reacquisition": "automatic",
-    "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-    "last_verified": "2026-09-11",
-    "notes": "Filed by the round-2 index merge, 2026-09-11."
-   },
-   {
-    "id": "fcc-2AN3WM5DINMETER-7497875",
-    "kind": "regulatory-exhibit",
-    "canonical_url": "https://fccid.io/2AN3WM5DINMETER/Internal-Photos/Internal-Photos-7497875.pdf",
-    "fallback_urls": [
-     "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497875",
-     "https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497875.pdf",
-     "https://fccid.io/2AN3WM5DINMETER",
-     "https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/Internal-Photos/Internal-Photos-7497875.pdf"
-    ],
-    "sha256": "7e0be459cbbf21a434a79b0d2aeeabb1442673990231927b6e0cda72abe1f198",
-    "bytes": 3674683,
-    "destination": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-internal-photos.pdf",
-    "retrieved": "2026-09-11",
-    "upstream_version_or_date": "2024-07-23",
-    "fcc_id": "2AN3WM5DINMETER",
-    "fcc_document_id": "7497875",
-    "exhibit_type": "Internal Photos",
-    "exhibit_title_as_filed": "Internal Photos",
-    "grant_date": "2024-07-23",
-    "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-    "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-    "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-    "license_evidence": "FCC Equipment Authorization System publication",
-    "redistribution_status": "allowed",
-    "disposition": "repository",
-    "repo_state": "untracked",
-    "archived_to": null,
-    "placeholder": null,
-    "extraction": null,
-    "target_hardware": "devices/m5stack/dinmeter",
-    "reacquisition": "automatic",
-    "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-    "last_verified": "2026-09-11",
-    "notes": "Filed by the round-2 index merge, 2026-09-11."
-   },
-   {
-    "id": "fcc-2AN3WM5DINMETER-7497882",
-    "kind": "regulatory-exhibit",
-    "canonical_url": "https://fccid.io/2AN3WM5DINMETER/User-Manual/User-Manual-7497882.pdf",
-    "fallback_urls": [
-     "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497882",
-     "https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497882.pdf",
-     "https://fccid.io/2AN3WM5DINMETER",
-     "https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/User-Manual/User-Manual-7497882.pdf"
-    ],
-    "sha256": "b472ab81821318a605ad749b318b9ec0626926669b567d756dd8b2378898015e",
-    "bytes": 2021122,
-    "destination": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf",
-    "retrieved": "2026-09-11",
-    "upstream_version_or_date": "2024-07-23",
-    "fcc_id": "2AN3WM5DINMETER",
-    "fcc_document_id": "7497882",
-    "exhibit_type": "Users Manual",
-    "exhibit_title_as_filed": "User Manual",
-    "grant_date": "2024-07-23",
-    "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-    "test_firm": "Dongguan Yaxu (AiT) Technology Limited",
-    "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-    "license_evidence": "FCC Equipment Authorization System publication",
-    "redistribution_status": "allowed",
-    "disposition": "archive",
-    "repo_state": "placeholder-only",
-    "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf",
-    "placeholder": "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf.ARCHIVED.md",
-    "extraction": null,
-    "target_hardware": "devices/m5stack/dinmeter",
-    "reacquisition": "automatic",
-    "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-    "last_verified": "2026-09-11",
-    "notes": "Filed by the round-2 index merge, 2026-09-11."
-   },
-  {
-   "id": "A-01",
-   "kind": "schematic",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/500/DIN_Meter_v1.0.pdf",
-   "expected_sha256": "03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070",
-   "expected_bytes": 433658,
-   "destination": "devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "titled DIN_Meter_v1.0; no revision date printed",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "PRIMARY EVIDENCE for the whole record. Validated: %PDF magic, 1 page, text layer parsed and cross-checked against visible headings. Byte-identical to A-11 (the v1.1 'schematic')."
-  },
-  {
-   "id": "A-02",
-   "kind": "derived",
-   "url": null,
-   "expected_sha256": "6d3f94edaf04ffecc140061a3b6758312e7aab7c6fc71c9862eacb42aed262f4",
-   "expected_bytes": 73682,
-   "destination": "devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.bbox.xml",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "derived 2026-09-04",
-   "license": "derived work of A-01",
-   "license_evidence": "n/a",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "manual",
-   "notes": "poppler -bbox-compatible XML emitted from A-01 with pdfminer.six 20260107, glyphs deduplicated. Regenerable; see commands.md."
-  },
-  {
-   "id": "A-03",
-   "kind": "tool",
-   "url": null,
-   "expected_sha256": "c40e99daf6281d1dccd35ba8234c1f978d44d73301febf5c02b8c9859f9e20ad",
-   "expected_bytes": 3198,
-   "destination": "devices/m5stack/dinmeter/artifacts/schematic/parse_dinmeter_sch.py",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "written 2026-09-04",
-   "license": "authored for this repository",
-   "license_evidence": "n/a",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "n/a",
-   "notes": "Altium CO/PI/NL marker parser. Re-runnable against A-02."
-  },
-  {
-   "id": "A-04",
-   "kind": "derived",
-   "url": null,
-   "expected_sha256": "84fb10aa812db82b2fd6561916d522a8085c664e19b0c7cad3904a6d86d55cd9",
-   "expected_bytes": 4085,
-   "destination": "devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-value-census.txt",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "derived 2026-09-04",
-   "license": "derived work of A-01",
-   "license_evidence": "n/a",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "manual",
-   "notes": "85 designators to nearby value text."
-  },
-  {
-   "id": "A-05",
-   "kind": "derived",
-   "url": null,
-   "expected_sha256": "74df72775c2aaf07c2c53109364a453d64b10ea7c95f8fc8663e6e4d6d08fbbf",
-   "expected_bytes": 31431,
-   "destination": "devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-census.txt",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "derived 2026-09-04",
-   "license": "derived work of A-01",
-   "license_evidence": "n/a",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "manual",
-   "notes": "Full CO/PI/NL census plus designator-sequence gap analysis."
-  },
-  {
-   "id": "A-06",
-   "kind": "derived",
-   "url": null,
-   "expected_sha256": "5174562c85e605a487c348eca8cb1841490be7fdc983340f51e840a7629dfa58",
-   "expected_bytes": 6908,
-   "destination": "devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-plaintext-layout.txt",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "derived 2026-09-04",
-   "license": "derived work of A-01",
-   "license_evidence": "n/a",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "manual",
-   "notes": "The sheet rendered as positioned text rows - readable like a drawing."
-  },
-  {
-   "id": "A-07",
-   "kind": "derived",
-   "url": null,
-   "expected_sha256": "d37e81441cbff887e1d7ad8d2e8b7e35c585630b666be809ed1e89e287d5bd30",
-   "expected_bytes": 3403,
-   "destination": "devices/m5stack/dinmeter/artifacts/schematic/M1-stamp-s3-pinout-from-schematic.txt",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "derived 2026-09-04",
-   "license": "derived work of A-01",
-   "license_evidence": "n/a",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "manual",
-   "notes": "All 31 M1 (Stamp-S3-SMD) pads with row-matched pin names and nets."
-  },
-  {
-   "id": "A-08",
-   "kind": "drawing",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-din_meter_asm_v1.pdf",
-   "expected_sha256": "db42c8a995b6d0bf8032ee32f60e65307dca42c7c48898b1760e183c0706e579",
-   "expected_bytes": 117405,
-   "destination": "devices/m5stack/dinmeter/artifacts/mechanical/K134-din_meter_asm_v1-dimensions.pdf",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unversioned",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Dimension/assembly drawing. THE SAME URL is linked from both the v1.0 and v1.1 product pages."
-  },
-  {
-   "id": "A-09",
-   "kind": "cad",
-   "url": "https://raw.githubusercontent.com/m5stack/M5_Hardware/a240115c94b19ecf647f229c47fa9a8ce46ccdc4/Products/K134_DinMeter/Structures/DinMeter.stl",
-   "expected_sha256": "90f04d6a0ae2cbb6f888065382da46ab1d699188ccebf1510963cc4aef00fbf7",
-   "expected_bytes": 573284,
-   "destination": "devices/m5stack/dinmeter/artifacts/mechanical/DinMeter.stl",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "repo HEAD a240115c94b19ecf647f229c47fa9a8ce46ccdc4 (2026-08-17)",
-   "license": "unknown - m5stack/M5_Hardware has no LICENSE file (checked 2026-09-04)",
-   "license_evidence": "absence of LICENSE at the pinned commit",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/m5stack/M5_Hardware",
-   "commit": "a240115c94b19ecf647f229c47fa9a8ce46ccdc4",
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Byte-identical to A-12 (DinMeter_v1.1.stl). Both retained deliberately: the duplication is the finding."
-  },
-  {
-   "id": "A-10",
-   "kind": "documentation",
-   "url": "https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/M5DinMeter.pdf",
-   "expected_sha256": "8b3db00abbc7e31762c503b36d8406fd8c6e21bdd23f89538989031ca1b70b3a",
-   "expected_bytes": 7459888,
-   "destination": "devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unversioned; server re-renders per request",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "archive",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [
-    "https://docs.m5stack.com/en/core/M5DinMeter (Page Tools -> PDF)"
-   ],
-   "reacquisition": "automatic",
-   "notes": "ARCHIVED for size (7.5 MB). Placeholder at the same path with recovery URLs. Content extracted to docs-en-core-M5DinMeter.txt, retained in-repo."
-  },
-  {
-   "id": "A-10b",
-   "kind": "derived",
-   "url": null,
-   "expected_sha256": "015daf70c53daae2f80f898f5f3c47e555ccb54c899e2278065260c100fd0d45",
-   "expected_bytes": 5214,
-   "destination": "devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.txt",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "captured 2026-09-04",
-   "license": "derived work of the product page",
-   "license_evidence": "n/a",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "manual",
-   "notes": "Text extraction of the v1.0 product page."
-  },
-  {
-   "id": "A-13",
-   "kind": "source-snapshot",
-   "url": "https://api.github.com/repos/m5stack/M5DinMeter/tarball/8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "expected_sha256": "de47c4109635870506bb7a02040db496f82e5bbb22a5b1befe600a3985eb0f02",
-   "expected_bytes": 8532,
-   "destination": "devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "HEAD 8ccbad7297beb82a140f812e5606e060d8a5e0dc; latest release 1.0.0 (2024-03-07)",
-   "license": "UNKNOWN - the repository has NO LICENSE file and GitHub reports no licence. The README credits MIT only for M5GFX/M5Unified and 'original' for the bundled PJRC Encoder",
-   "license_evidence": "absence of LICENSE at the pinned commit",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/m5stack/M5DinMeter",
-   "commit": "8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "release_tag": "1.0.0",
-   "extraction": null,
-   "fallback_urls": [
-    "https://github.com/m5stack/M5DinMeter/archive/8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz"
-   ],
-   "reacquisition": "automatic",
-   "notes": "The Arduino library plus all six official examples."
-  },
-  {
-   "id": "A-14",
-   "kind": "source-snapshot",
-   "url": "https://api.github.com/repos/m5stack/M5DinMeter-UserDemo/tarball/d2fdfe44e9baf810f82335faa6f5962e9fc59a44",
-   "expected_sha256": "af58e2cdaf565bb3f97daeadd02843a4cd3dc72f504446aa842d865eb9c4ec72",
-   "expected_bytes": 74231,
-   "destination": "devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "HEAD d2fdfe44e9baf810f82335faa6f5962e9fc59a44; release V0.1 (2024-03-04)",
-   "license": "MIT ((c) 2024 M5Stack) - MIXED-LICENCE ARCHIVE: bundles PJRC Encoder, ESP32Encoder, I2C_BM8563 and Button, each with its own licence file under lib/",
-   "license_evidence": "LICENSE at repository root; per-library licence files under lib/",
-   "redistribution_status": "conditional - preserve notices",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/m5stack/M5DinMeter-UserDemo",
-   "commit": "d2fdfe44e9baf810f82335faa6f5962e9fc59a44",
-   "release_tag": "V0.1",
-   "extraction": null,
-   "fallback_urls": [
-    "https://github.com/m5stack/M5DinMeter-UserDemo/archive/d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz"
-   ],
-   "reacquisition": "automatic",
-   "notes": "The factory-firmware source. Contains ft_disp_lgfx_cfg.hpp, the authoritative raw-LovyanGFX panel config."
-  },
-  {
-   "id": "A-15-board_info",
-   "kind": "board-support",
-   "url": "https://raw.githubusercontent.com/espressif/esp-board-manager/main/m5stack_boards/m5stack_dinmeter/board_info.yaml",
-   "expected_sha256": "e15d9260da578e8ebdcd6cb050e6eab5be3e8d7ecdb7142937257cd2de475018",
-   "expected_bytes": 177,
-   "destination": "devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_info.yaml",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "repo HEAD 2beb9b22b0892b343bd555a1ebc9929a7edce8fc (2026-09-03)",
-   "license": "not verified at file level; esp-board-manager is an Espressif project",
-   "license_evidence": "not checked in this pass",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/espressif/esp-board-manager",
-   "commit": "2beb9b22b0892b343bd555a1ebc9929a7edce8fc",
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [
-    "https://raw.githubusercontent.com/espressif/esp-board-manager/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/m5stack_boards/m5stack_dinmeter/board_info.yaml"
-   ],
-   "reacquisition": "automatic",
-   "notes": "Espressif's own ESP-IDF board definition. NOTE the URL uses the MOVING 'main' ref; the pinned form is https://raw.githubusercontent.com/espressif/esp-board-manager/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/..."
-  },
-  {
-   "id": "A-15-board_devices",
-   "kind": "board-support",
-   "url": "https://raw.githubusercontent.com/espressif/esp-board-manager/main/m5stack_boards/m5stack_dinmeter/board_devices.yaml",
-   "expected_sha256": "b6dd27252f9fe372327f71243b84a9a0effc843e7d78f4871d94ef66f606c03f",
-   "expected_bytes": 2176,
-   "destination": "devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_devices.yaml",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "repo HEAD 2beb9b22b0892b343bd555a1ebc9929a7edce8fc (2026-09-03)",
-   "license": "not verified at file level; esp-board-manager is an Espressif project",
-   "license_evidence": "not checked in this pass",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/espressif/esp-board-manager",
-   "commit": "2beb9b22b0892b343bd555a1ebc9929a7edce8fc",
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [
-    "https://raw.githubusercontent.com/espressif/esp-board-manager/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/m5stack_boards/m5stack_dinmeter/board_devices.yaml"
-   ],
-   "reacquisition": "automatic",
-   "notes": "Espressif's own ESP-IDF board definition. NOTE the URL uses the MOVING 'main' ref; the pinned form is https://raw.githubusercontent.com/espressif/esp-board-manager/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/..."
-  },
-  {
-   "id": "A-15-board_peripherals",
-   "kind": "board-support",
-   "url": "https://raw.githubusercontent.com/espressif/esp-board-manager/main/m5stack_boards/m5stack_dinmeter/board_peripherals.yaml",
-   "expected_sha256": "a09f81cf383d14d2290b1627ea6352905a17eb4ac0aaa39fdff52931e2a61dc1",
-   "expected_bytes": 5014,
-   "destination": "devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "repo HEAD 2beb9b22b0892b343bd555a1ebc9929a7edce8fc (2026-09-03)",
-   "license": "not verified at file level; esp-board-manager is an Espressif project",
-   "license_evidence": "not checked in this pass",
-   "redistribution_status": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/espressif/esp-board-manager",
-   "commit": "2beb9b22b0892b343bd555a1ebc9929a7edce8fc",
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [
-    "https://raw.githubusercontent.com/espressif/esp-board-manager/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/m5stack_boards/m5stack_dinmeter/board_peripherals.yaml"
-   ],
-   "reacquisition": "automatic",
-   "notes": "Espressif's own ESP-IDF board definition. NOTE the URL uses the MOVING 'main' ref; the pinned form is https://raw.githubusercontent.com/espressif/esp-board-manager/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/..."
-  },
-  {
-   "id": "A-16",
-   "kind": "board-support",
-   "url": "https://raw.githubusercontent.com/bmorcelli/Launcher/main/boards/m5stack-dinmeter/platformio.ini",
-   "expected_sha256": "f07ad1e769990de8aa31e0c2c67ed0edffc23f92e2746447a91a7c6b315836b8",
-   "expected_bytes": 1601,
-   "destination": "devices/m5stack/dinmeter/artifacts/source-snapshots/launcher-m5stack-dinmeter-platformio.ini",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "main branch as of 2026-09-04 (no release pinned at capture)",
-   "license": "MIT",
-   "license_evidence": "repository LICENSE",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "upstream_repository": "https://github.com/bmorcelli/Launcher",
-   "commit": "main (unpinned at capture)",
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Independent corroboration of display pins, GRAM offsets, battery divider ratio 2.0 and no-PSRAM; also the SD-over-Grove demonstration. WARNING: fetched from the MOVING 'main' ref - a future fetch may differ."
-  },
-  {
-   "id": "A-17-01",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp",
-   "expected_sha256": "d1b53d2e662ff8c5d0c0fda67721d3b8eac1af131b91166cd7093b4de3988b71",
-   "expected_bytes": 24358,
-   "destination": "devices/m5stack/dinmeter/media/img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-02",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-71baa86c-292a-4905-ad68-f2733320e4ab.webp",
-   "expected_sha256": "093479d5ad0fe5e5ce3ebd1c11cb2fbaa46a39303972780c0cdbb0296c1c4713",
-   "expected_bytes": 11666,
-   "destination": "devices/m5stack/dinmeter/media/img-71baa86c-292a-4905-ad68-f2733320e4ab.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-03",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp",
-   "expected_sha256": "f36fa045c7c3193eb67aad1ae33a76a029c5b80d62e89c7539f1d8b8521ecadd",
-   "expected_bytes": 20488,
-   "destination": "devices/m5stack/dinmeter/media/img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-04",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp",
-   "expected_sha256": "c3ddcde9ab961823a86c02ee9dcd85439dc5e0809b04264dd37ebb22a2b9632a",
-   "expected_bytes": 27418,
-   "destination": "devices/m5stack/dinmeter/media/img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-05",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp",
-   "expected_sha256": "1fc457e99c7b6525eddeeb10ccf6ad500f2d57bcdd28a8670c95593746d2571e",
-   "expected_bytes": 101360,
-   "destination": "devices/m5stack/dinmeter/media/img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-06",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-af3c8884-3669-4305-af73-979e32fe176f.webp",
-   "expected_sha256": "06d73cd30da9b7404f33c48318f4d7c12a64ae2f6740909a700aef09f4f7024c",
-   "expected_bytes": 39006,
-   "destination": "devices/m5stack/dinmeter/media/img-af3c8884-3669-4305-af73-979e32fe176f.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-07",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp",
-   "expected_sha256": "d351219482f348e45c765b3e5b3de72d63d5e3e0e71e30f581c76bad7d1fd024",
-   "expected_bytes": 36126,
-   "destination": "devices/m5stack/dinmeter/media/img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-08",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp",
-   "expected_sha256": "4f9a7f4c0fe095da08ad2eced07b6f15fa7abafc802fed4dca3488cef103eef2",
-   "expected_bytes": 12974,
-   "destination": "devices/m5stack/dinmeter/media/img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-09",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp",
-   "expected_sha256": "ebecbc8cdf08f8a7b807b30cd5507d59758f2fc75186dd80eea485f91ccb4fdf",
-   "expected_bytes": 34452,
-   "destination": "devices/m5stack/dinmeter/media/img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  },
-  {
-   "id": "A-17-10",
-   "kind": "image",
-   "url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-   "expected_sha256": "82916ce50a40391698e3f15e57c2effe21ffcd81324601fec53e4a1459f7276f",
-   "expected_bytes": 24884,
-   "destination": "devices/m5stack/dinmeter/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-   "retrieved": "2026-09-04",
-   "upstream_version_or_date": "unknown - CDN returned no Last-Modified",
-   "license": "unknown - no licence statement on the source page or in the file; M5Stack asserts copyright in its page footer",
-   "license_evidence": "none found",
-   "redistribution_status": "unknown",
-   "disposition": "repository (unstaged pending review)",
-   "repo_state": "untracked",
-   "upstream_repository": null,
-   "commit": null,
-   "release_tag": null,
-   "extraction": null,
-   "fallback_urls": [],
-   "reacquisition": "automatic",
-   "notes": "Official product photograph. Validated RIFF/WEBP. Not visually rendered in this pass - see media.md."
-  }
- ],
- "counts": {
-  "total": 27,
-  "downloaded": 20,
-  "derived_locally": 7,
-  "archived": 1,
-  "failed_downloads": 0,
-  "bytes_in_repo": 1676731,
-  "bytes_archived": 7459888
- }
-}
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf.ARCHIVED.md b/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 39843fb..0000000
--- a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5DINMETER-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 822,846 B (0.78 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 822,846 B (0.78 MiB) |
-| SHA-256 | `0728acb7f328e39ceb9c466d8ca99689211002d4f3dda9a1f4c452dd7ebb498c` |
-| FCC ID | **`2AN3WM5DINMETER`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 7497866 |
-| Upstream publication date | 2024-07-23 |
-| Grant date | 2024-07-23 |
-| Equipment class | M5DinMeter, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5DINMETER/Test-Report/Antenna-Specification-7497866.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497866>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497866.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5DINMETER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/Test-Report/Antenna-Specification-7497866.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf" \
-   "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5DINMETER/Test-Report/Antenna-Specification-7497866.pdf" -o "2AN3WM5DINMETER-antenna-specification.pdf"
-echo "0728acb7f328e39ceb9c466d8ca99689211002d4f3dda9a1f4c452dd7ebb498c  2AN3WM5DINMETER-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf.ARCHIVED.md b/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 12340c4..0000000
--- a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5DINMETER-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 2,123,431 B (2.03 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,123,431 B (2.03 MiB) |
-| SHA-256 | `b5aac335a6631663b90352c1edbc7926522235682d3b73c91db7731c2a0d5f0e` |
-| FCC ID | **`2AN3WM5DINMETER`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 7497872 |
-| Upstream publication date | 2024-07-23 |
-| Grant date | 2024-07-23 |
-| Equipment class | M5DinMeter, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5DINMETER/External-Photos/External-Photos-7497872.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497872>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497872.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5DINMETER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/External-Photos/External-Photos-7497872.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf" \
-   "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5DINMETER/External-Photos/External-Photos-7497872.pdf" -o "2AN3WM5DINMETER-external-photos.pdf"
-echo "b5aac335a6631663b90352c1edbc7926522235682d3b73c91db7731c2a0d5f0e  2AN3WM5DINMETER-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-id-label.pdf b/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-id-label.pdf
deleted file mode 100644
index d615621..0000000
Binary files a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-id-label.pdf and /dev/null differ
diff --git a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md b/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md
deleted file mode 100644
index 3d9b7e0..0000000
--- a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 126,464 B (0.12 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 126,464 B (0.12 MiB) |
-| SHA-256 | `aeb323a16a2ad99ca84494c240a74dbc768636ef8cbbbc5d6679a9b675ae617a` |
-| FCC ID | **`2AN3WM5DINMETER`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | FCC RF Exposure-MPE |
-| FCC document id | 7497877 |
-| Upstream publication date | 2024-07-23 |
-| Grant date | 2024-07-23 |
-| Equipment class | M5DinMeter, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5DINMETER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7497877.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497877>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497877.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5DINMETER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7497877.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf" \
-   "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5DINMETER/RF-Exposure-Info/FCC-RF-Exposure-MPE-7497877.pdf" -o "2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf"
-echo "aeb323a16a2ad99ca84494c240a74dbc768636ef8cbbbc5d6679a9b675ae617a  2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-internal-photos.pdf b/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-internal-photos.pdf
deleted file mode 100644
index a5221de..0000000
Binary files a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-internal-photos.pdf and /dev/null differ
diff --git a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf.ARCHIVED.md b/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 47cfc32..0000000
--- a/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5DINMETER-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 2,021,122 B (1.93 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,021,122 B (1.93 MiB) |
-| SHA-256 | `b472ab81821318a605ad749b318b9ec0626926669b567d756dd8b2378898015e` |
-| FCC ID | **`2AN3WM5DINMETER`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 7497882 |
-| Upstream publication date | 2024-07-23 |
-| Grant date | 2024-07-23 |
-| Equipment class | M5DinMeter, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5DINMETER/User-Manual/User-Manual-7497882.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=7497882>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5DINMETER/7497882.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5DINMETER>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5DINMETER/User-Manual/User-Manual-7497882.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf" \
-   "devices/m5stack/dinmeter/artifacts/certification/2AN3WM5DINMETER-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5DINMETER/User-Manual/User-Manual-7497882.pdf" -o "2AN3WM5DINMETER-user-manual.pdf"
-echo "b472ab81821318a605ad749b318b9ec0626926669b567d756dd8b2378898015e  2AN3WM5DINMETER-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/dinmeter/artifacts/certification/README.md b/devices/m5stack/dinmeter/artifacts/certification/README.md
deleted file mode 100644
index e08f9eb..0000000
--- a/devices/m5stack/dinmeter/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5DINMETER`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5DINMETER`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2024-07-23** |
-| Equipment class | M5DinMeter, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Source page | <https://fccid.io/2AN3WM5DINMETER> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5DINMETER-fcc-id-label.pdf` | 357,530 | `87bc3655794390cccabd01307810bd9f4f15ef515e23fbdf07b4efea395ef968` | ID Label/Location Info |
-| `2AN3WM5DINMETER-internal-photos.pdf` | 3,674,683 | `7e0be459cbbf21a434a79b0d2aeeabb1442673990231927b6e0cda72abe1f198` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5DINMETER-antenna-specification.pdf.ARCHIVED.md`](2AN3WM5DINMETER-antenna-specification.pdf.ARCHIVED.md) | 822,846 | Test Report |
-| [`2AN3WM5DINMETER-external-photos.pdf.ARCHIVED.md`](2AN3WM5DINMETER-external-photos.pdf.ARCHIVED.md) | 2,123,431 | External Photos |
-| [`2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md`](2AN3WM5DINMETER-fcc-rf-exposure-mpe.pdf.ARCHIVED.md) | 126,464 | RF Exposure Info |
-| [`2AN3WM5DINMETER-user-manual.pdf.ARCHIVED.md`](2AN3WM5DINMETER-user-manual.pdf.ARCHIVED.md) | 2,021,122 | Users Manual |
-
-Archived total: **4 files, 4.86 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 3.85 MiB** |
-| Archived | **4 files, 4.86 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf b/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf
deleted file mode 120000
index 99d455c..0000000
--- a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.link b/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.link
deleted file mode 120000
index 824dfff..0000000
--- a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-docs-en-core-M5DinMeter.pdf
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.md b/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.md
deleted file mode 100644
index 8a6e7be..0000000
--- a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# ARCHIVED — `docs-en-core-M5DinMeter.pdf`
-
-Printable ("PDF" page-tool) export of the official M5Stack **DinMeter (SKU K134)** product
-documentation page, generated server-side by `docs.m5stack.com`.
-
-| Field | Value |
-|---|---|
-| Original repository path | `devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf` |
-| Archived to | `archive/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.pdf` |
-| SHA-256 | `8b3db00abbc7e31762c503b36d8406fd8c6e21bdd23f89538989031ca1b70b3a` |
-| Byte size | 7 459 888 |
-| Media type | PDF (validated: `%PDF` magic, opens in pdfminer.six 20260107) |
-| Retrieved | 2026-09-04 |
-| Upstream version/date | **Not versioned.** M5Stack regenerates this file from the live page; the capture reflects the page as served on 2026-09-04 |
-| Publisher | M5Stack Technology Co., Ltd |
-| Licence | **unknown** — no licence statement on the page or in the PDF. Marketing/technical documentation, vendor copyright asserted in the page footer (`Copyright © M5Stack Technology Co., Ltd. All rights reserved.`) |
-| Redistribution status | `unknown` |
-| Disposition | `repository` → archived for size (7.5 MB of embedded product photography for ~5 KB of text) |
-| Why moved | Size. Every fact it carries has been extracted into [`../../README.md`](../../README.md), [`../../pinouts-and-buses.md`](../../pinouts-and-buses.md) and the sibling text capture `docs-en-core-M5DinMeter.txt`, which is retained in the repository. |
-| Reproducible? | **Yes, but not byte-stably.** The server re-renders on each request; a fresh fetch will differ in the PDF `/ID` and creation date. The *content* is reproducible while the page exists. |
-| Reacquisition | `automatic` |
-
-## Reacquisition
-
-Two independent hosts, most reliable first:
-
-1. **Vendor CDN (Alibaba OSS), direct** — the durable, machine-fetchable form:
-   ```bash
-   curl -fSL -o docs-en-core-M5DinMeter.pdf \
-     'https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/M5DinMeter.pdf'
-   ```
-   Path template (see [`vendors/m5stack/README.md`](../../../../../vendors/m5stack/README.md)):
-   `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/<section>/<PageId>.pdf`
-2. **The rendered page itself**, via the "PDF" button in *Page Tools*:
-   <https://docs.m5stack.com/en/core/M5DinMeter> (retrieved 2026-09-04, HTTP 200).
-   Note the page id is `M5DinMeter`, **not** `DinMeter` — `https://docs.m5stack.com/en/core/DinMeter`
-   returns **HTTP 404** (verified 2026-09-04; this is the negative control for the path pattern).
-3. **Internet Archive** — no capture was confirmed at the time of writing; submitting
-   `https://web.archive.org/save/https://docs.m5stack.com/en/core/M5DinMeter` is the fallback.
-
-## Also see
-
-- Full acquisition record: [`../../acquisition/manifest.json`](../../acquisition/manifest.json)
-- Text extraction retained in-repo: `docs-en-core-M5DinMeter.txt` (5 214 bytes)
-- The v1.1 counterpart, archived under the same convention:
-  [`devices/m5stack/dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.md`](../../../dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.pdf.ARCHIVED.md)
diff --git a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.txt b/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.txt
deleted file mode 100644
index 81d07b6..0000000
--- a/devices/m5stack/dinmeter/artifacts/docs/docs-en-core-M5DinMeter.txt
+++ /dev/null
@@ -1,279 +0,0 @@
-id="document" class="header-nav-item">Documentation 
- About Us 
- Contact 
- English
- English
- 简体中文
- 日本語
- CONTENTS
- 
- 
- No Results Found
- Hot Searches
- Camera
- WiFi
- RS485
- RS232
- Relay
- LoRaWAN
- GPS
- NB-IoT
- LTE
- GSM
- Zigbee
- Servo
- StepMotor
- Ethernet
- E-Paper
- 
- Product
- Contents
- 
- Search
- DinMeter
- SKU:K134
- 
- 
- 
- Description
- DinMeter is an embedded development board that adheres to the 1/32DIN standard, featuring a 1.14-inch ST7789 screen and a built-in rotary encoder with buttons for precise knob position recording. Additionally, it includes an RTC circuit, an onboard buzzer, and buttons for device interaction and wake-up alerts. The product is designed to support DC input ranging from 6V to 36V and includes a lithium battery interface and charging circuit to accommodate various power supply needs. The reserved PORT.A and PORT.B interfaces allow for easy expansion of I2C and GPIO devices. This product is suitable for applications such as parameter measurement and detection, smart home control, IoT projects, smart wearables, access control, industrial control, and educational maker projects.
-Tutorial
- Arduino IDE
- Arduino IDE
- This tutorial will introduce how to program and control the DinMeter device using the Arduino IDE. 
- UiFlow2
- UiFlow2
- This tutorial will introduce how to control the DinMeter device through the UiFlow2 graphical programming platform. 
-Features
- ST7789v2 screen
- M5StampS3 as the main controller
- Rotary encoder
- Wide voltage input
- Reserved PORTA and PORTB interfaces
- Lithium battery interface (rechargeable)
- 1/32DIN standard (45 x 22.5mm)
- Development PlatformUiFlow2
- Arduino IDE
- ESP-IDF
- PlatformIO
- Includes
- 1 x DinMeter
- 1 x Adhesive tape
- 1 x 250mAh polymer lithium battery
- 1 x Silk-screened sticker
- 1 x DC-JACK terminal input (6-36V)
- 1 x Back bracket
- Applications
- Smart home detection and control systems
- Access control systems
- Industrial control
- Maker and DIY projects
- Specifications
- Specification
- Parameter
- | SoC
- ESP32-S3FN8 @ Xtensa® 32-bit LX7 dual-core processor, clock frequency 240MHz
- Flash
- 8MB
- Wi-Fi
- 2.4 GHz Wi-Fi
- USB
- USB OTG, USB Serial/JTAG
- Wide Voltage Input Range
- 6 ~ 36V
- Display Driver
- ST7789V2
- Display Resolution
- 135 x 240
- Charging Current
- 100mA
- Grove Load Capacity
- PORT.A Load Capacity: DC 5V/Max:220mA | PORT.B Load Capacity: DC 5V/Max:220mA
- Standby Current (Battery Powered)
- DC 4.2V@38.4uA
- Battery Socket Specification
- 1.25mm-2p
- Power Supply Method
- USB/DC Power Supply / Battery
- Operating Temperature
- 0 ~ 40°C
- Product Size
- 53.0 x 30.0 x 32.0mm
- Product Weight
- 17.8g
- Package Size
- 136.0 x 93.0 x 23.0mm
- Gross Weight
- 47.0g
-Learn
- Power On/Off Operation 
- Power On: The device can be woken up by pressing the "WAKE" button or by an RTC-triggered IRQ signal. After the wake-up signal is triggered, the program initialization must set the hold(G46) pin to high (1) to maintain power; otherwise, the device will re-enter sleep mode. | Power Off: When there is no external USB power supply, press the RST button to power off, or set HOLD(GPIO46)=0 in the program to power off.
- Download Mode 
- To enter download mode, hold the G0 button on the StampS3 before powering on, then release it after powering up.
- Power Supply Methods | Three power supply methods: USB/DC/BAT
- Din Size Standard
- Schematics
- DinMeter Schematics PDF
- 
- 
- 1/1
- 
- PinMap
- RTC8563 & ENCODER
- ESP32-S3FN8
- G12
- G11
- G40
- G41
- G3
- G42
- | RTC8563
- SCL
- SDA
- 
- 
- ENCODER
- 
- B
- A
- 
- BEEP
- 
- 
- beep
- BUTTON (ENCODER)
- 
- 
- BTN(WAKE)
-ST7789V2
- ESP32-S3FN8
- G7
- G6
- G4
- G5
- G8
- G9
- | ST7789V2
- CS
- SCK
- RS
- MOSI
- RESET
- BL
-HY2.0-4P
- HY2.0-4P
- Black
- Red
- Yellow
- White
- | PORT.A
- GND
- 5V
- G13
- G15
- PORT.B
- GND
- 5V
- G2
- G1
-Model Size
- DinMeter Model Size PDF
- Structure
- DinMeter Structure Files
- Datasheets
- BM8563
- tp4057
- ST7789V2
- Spec of external DC power connector
- Lithium battery seat
- Softwares
- Quick Start
- DinMeter Arduino Quick Start
- Arduino
- DinMeter Arduino Driver Library
- DinMeter Factory Firmware
- UiFlow2
- DinMeter UiFlow2 Quick Start
- Easyloader
- Easyloader
- Download Link
- Notes
- | DinMeter User Demo Easyloader
- download
- /
-Video
- 
- Page Tools
- PDF Copy page 
- 
- About Us
- About M5Stack
-News
-Blog
-Events
-Contact Us
- Where to buy
- Distributors
-Official Store
-AliExpress
-Amazon
-Taobao
- Solution
- For Business
-For Developers
- Software
- UiFlow1
-UiFlow2
-M5Burner
-Block Designer
-EzData 2.0
-EasyLoader Packer
-VLW Font Creator
-Device USB Driver
- Documentation
- Product Documents
-UiFlow1
-UiFlow2
-Arduino
-ESP-IDF
-StackFlow AI
-Home Assistant
-nanoFramework
-Product Guide
-Product Certifications
-I2C Table
-Product Selector
-Hardware Design Files
-Release History
-Stack Compatibility
-Stack Screw Length
- 
- Stay in the Loop
- 
- Weekly updates on new products, innovations, and announcements.
- 
- Subscribe
- 
- Email is invalid!
- 
- Thanks for subscribing
- 
- 
- M5Stack Technology Co., Ltd
- 
- Address: 
- Block A10, Expo Bay South Coast, Fuhai Street, Bao'an District, Shenzhen, China
- 
- TEL: 
- +86 755 8657 5379
- 
- Email: 
- support@m5stack.com
- 
- Copyright ©
- M5Stack Technology Co., Ltd.
- All rights reserved.
- Privacy Policy| Terms of Service| Shipping Policy| Refund Policy| Payment Method
- 粤ICP备16010631号
- 
- 
diff --git a/devices/m5stack/dinmeter/artifacts/mechanical/DinMeter.stl b/devices/m5stack/dinmeter/artifacts/mechanical/DinMeter.stl
deleted file mode 100644
index 0928d71..0000000
Binary files a/devices/m5stack/dinmeter/artifacts/mechanical/DinMeter.stl and /dev/null differ
diff --git a/devices/m5stack/dinmeter/artifacts/mechanical/K134-din_meter_asm_v1-dimensions.pdf b/devices/m5stack/dinmeter/artifacts/mechanical/K134-din_meter_asm_v1-dimensions.pdf
deleted file mode 100644
index 30700aa..0000000
Binary files a/devices/m5stack/dinmeter/artifacts/mechanical/K134-din_meter_asm_v1-dimensions.pdf and /dev/null differ
diff --git a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-census.txt b/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-census.txt
deleted file mode 100644
index 0f422f7..0000000
--- a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-census.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-raw CO bodies: 85
-['C1', 'C10', 'C15', 'C16', 'C17', 'C18', 'C19', 'C2', 'C21', 'C24', 'C25', 'C26', 'C27', 'C28', 'C29', 'C3', 'C30', 'C31', 'C32', 'C33', 'C4', 'C5', 'C6', 'C7', 'C8', 'D1', 'D10', 'D11', 'D12', 'D13', 'D2', 'D3', 'D4', 'D5', 'D6', 'D7', 'D8', 'D9', 'FPC1', 'J1', 'J2', 'J3', 'J4', 'J5', 'L1', 'L4', 'LS1', 'M', 'M1', 'Q1', 'Q3', 'Q4', 'Q5', 'Q6', 'R1', 'R10', 'R11', 'R12', 'R13', 'R14', 'R15', 'R16', 'R17', 'R18', 'R19', 'R2', 'R23', 'R24', 'R25', 'R3', 'R4', 'R5', 'R6', 'R7', 'R8', 'R9', 'S4', 'U1', 'U2', 'U3', 'U4', 'U5', 'U6', 'U7', 'Y2']
-
-PI-implied designators not in CO: ['C1001', 'C1002', 'C101', 'C102', 'C1501', 'C1502', 'C1601', 'C1602', 'C1701', 'C1702', 'C1801', 'C1802', 'C1901', 'C1902', 'C201', 'C202', 'C2101', 'C2102', 'C2401', 'C2402', 'C2501', 'C2502', 'C2601', 'C2602', 'C2702', 'C2801', 'C2802', 'C2901', 'C2902', 'C3001', 'C3002', 'C301', 'C302', 'C3101', 'C3102', 'C3201', 'C3202', 'C3301', 'C3302', 'C401', 'C402', 'C501', 'C502', 'C602', 'C701', 'C702', 'C801', 'C802', 'D1001', 'D1002', 'D101', 'D102', 'D1101', 'D1102', 'D1201', 'D1202', 'D1301', 'D1302', 'D20', 'D301', 'D302', 'D401', 'D501', 'D502', 'D601', 'D602', 'D701', 'D702', 'D801', 'D802', 'D901', 'D902', 'FPC101', 'FPC1010', 'FPC102', 'FPC103', 'FPC104', 'FPC105', 'FPC106', 'FPC107', 'FPC108', 'FPC109', 'J101', 'J102', 'J20', 'J201', 'J301', 'J302', 'J303', 'J304', 'J401', 'J402', 'J403', 'J404', 'J501', 'J502', 'J503', 'J504', 'J505', 'L101', 'L102', 'L40', 'L401', 'LS101', 'LS102', 'M101', 'M1010', 'M1011', 'M1012', 'M1013', 'M1014', 'M1015', 'M1016', 'M1017', 'M1018', 'M1019', 'M102', 'M1020', 'M1021', 'M1022', 'M1023', 'M1024', 'M1025', 'M1026', 'M1027', 'M1028', 'M1029', 'M103', 'M1030', 'M1031', 'M104', 'M105', 'M106', 'M107', 'M108', 'M109', 'Q103', 'Q107', 'Q301', 'Q302', 'Q303', 'Q403', 'Q4074', 'Q4081652', 'Q501', 'Q502', 'Q503', 'Q601', 'Q602', 'Q603', 'R1001', 'R1002', 'R101', 'R102', 'R1101', 'R1102', 'R1201', 'R1202', 'R1301', 'R1302', 'R1401', 'R1402', 'R1501', 'R1502', 'R1601', 'R1602', 'R1701', 'R1702', 'R1801', 'R1802', 'R1901', 'R1902', 'R201', 'R202', 'R2301', 'R2302', 'R2401', 'R2402', 'R2501', 'R301', 'R302', 'R40', 'R402', 'R501', 'R502', 'R601', 'R602', 'R701', 'R702', 'R801', 'R802', 'R901', 'R902', 'S401', 'S402', 'U10', 'U102', 'U103', 'U105', 'U106', 'U201', 'U202', 'U203', 'U204', 'U205', 'U206', 'U302', 'U303', 'U304', 'U305', 'U306', 'U307', 'U308', 'U309', 'U401', 'U402', 'U403', 'U404', 'U405', 'U501', 'U502', 'U503', 'U504', 'U505', 'U506', 'U507', 'U508', 'U60', 'U701', 'U702', 'U703', 'Y201', 'Y202']
-
-designator-shaped plain text: ['C1', 'C10', 'C15', 'C16', 'C17', 'C18', 'C19', 'C2', 'C21', 'C24', 'C25', 'C26', 'C27', 'C28', 'C29', 'C3', 'C30', 'C31', 'C32', 'C33', 'C4', 'C5', 'C6', 'C601', 'C7', 'C8', 'D1', 'D10', 'D11', 'D12', 'D13', 'D2', 'D3', 'D4', 'D5', 'D6', 'D7', 'D8', 'D9', 'FPC1', 'J1', 'J2', 'J3', 'J4', 'J5', 'L1', 'L4', 'LS1', 'M1', 'Q1', 'Q3', 'Q4', 'Q5', 'Q6', 'R1', 'R10', 'R11', 'R12', 'R13', 'R14', 'R15', 'R16', 'R17', 'R18', 'R19', 'R2', 'R20', 'R23', 'R24', 'R25', 'R3', 'R4', 'R5', 'R6', 'R7', 'R8', 'R9', 'S1', 'S4', 'TP4057', 'U1', 'U104', 'U2', 'U3', 'U301', 'U4', 'U5', 'U6', 'U7', 'Y1', 'Y2']
-
-in plain text but NOT a CO designator: ['C601', 'R20', 'S1', 'TP4057', 'U104', 'U301', 'Y1']
-in CO but no plain-text label: []
-
-sequence gaps (designator numbering):
-  C: present=[1, 2, 3, 4, 5, 6, 7, 8, 10, 15, 16, 17, 18, 19, 21, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 601]  missing=[9, 11, 12, 13, 14, 20, 22, 23, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329, 330, 331, 332, 333, 334, 335, 336, 337, 338, 339, 340, 341, 342, 343, 344, 345, 346, 347, 348, 349, 350, 351, 352, 353, 354, 355, 356, 357, 358, 359, 360, 361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, 373, 374, 375, 376, 377, 378, 379, 380, 381, 382, 383, 384, 385, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 396, 397, 398, 399, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 420, 421, 422, 423, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 439, 440, 441, 442, 443, 444, 445, 446, 447, 448, 449, 450, 451, 452, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 468, 469, 470, 471, 472, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487, 488, 489, 490, 491, 492, 493, 494, 495, 496, 497, 498, 499, 500, 501, 502, 503, 504, 505, 506, 507, 508, 509, 510, 511, 512, 513, 514, 515, 516, 517, 518, 519, 520, 521, 522, 523, 524, 525, 526, 527, 528, 529, 530, 531, 532, 533, 534, 535, 536, 537, 538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 548, 549, 550, 551, 552, 553, 554, 555, 556, 557, 558, 559, 560, 561, 562, 563, 564, 565, 566, 567, 568, 569, 570, 571, 572, 573, 574, 575, 576, 577, 578, 579, 580, 581, 582, 583, 584, 585, 586, 587, 588, 589, 590, 591, 592, 593, 594, 595, 596, 597, 598, 599, 600]
-  D: present=[1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13]  missing=[]
-  FPC: present=[1]  missing=[]
-  J: present=[1, 2, 3, 4, 5]  missing=[]
-  L: present=[1, 4]  missing=[2, 3]
-  LS: present=[1]  missing=[]
-  M: present=[1]  missing=[]
-  Q: present=[1, 3, 4, 5, 6]  missing=[2]
-  R: present=[1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 23, 24, 25]  missing=[21, 22]
-  S: present=[1, 4]  missing=[2, 3]
-  TP: present=[4057]  missing=[1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329, 330, 331, 332, 333, 334, 335, 336, 337, 338, 339, 340, 341, 342, 343, 344, 345, 346, 347, 348, 349, 350, 351, 352, 353, 354, 355, 356, 357, 358, 359, 360, 361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, 373, 374, 375, 376, 377, 378, 379, 380, 381, 382, 383, 384, 385, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 396, 397, 398, 399, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 420, 421, 422, 423, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 439, 440, 441, 442, 443, 444, 445, 446, 447, 448, 449, 450, 451, 452, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 468, 469, 470, 471, 472, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487, 488, 489, 490, 491, 492, 493, 494, 495, 496, 497, 498, 499, 500, 501, 502, 503, 504, 505, 506, 507, 508, 509, 510, 511, 512, 513, 514, 515, 516, 517, 518, 519, 520, 521, 522, 523, 524, 525, 526, 527, 528, 529, 530, 531, 532, 533, 534, 535, 536, 537, 538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 548, 549, 550, 551, 552, 553, 554, 555, 556, 557, 558, 559, 560, 561, 562, 563, 564, 565, 566, 567, 568, 569, 570, 571, 572, 573, 574, 575, 576, 577, 578, 579, 580, 581, 582, 583, 584, 585, 586, 587, 588, 589, 590, 591, 592, 593, 594, 595, 596, 597, 598, 599, 600, 601, 602, 603, 604, 605, 606, 607, 608, 609, 610, 611, 612, 613, 614, 615, 616, 617, 618, 619, 620, 621, 622, 623, 624, 625, 626, 627, 628, 629, 630, 631, 632, 633, 634, 635, 636, 637, 638, 639, 640, 641, 642, 643, 644, 645, 646, 647, 648, 649, 650, 651, 652, 653, 654, 655, 656, 657, 658, 659, 660, 661, 662, 663, 664, 665, 666, 667, 668, 669, 670, 671, 672, 673, 674, 675, 676, 677, 678, 679, 680, 681, 682, 683, 684, 685, 686, 687, 688, 689, 690, 691, 692, 693, 694, 695, 696, 697, 698, 699, 700, 701, 702, 703, 704, 705, 706, 707, 708, 709, 710, 711, 712, 713, 714, 715, 716, 717, 718, 719, 720, 721, 722, 723, 724, 725, 726, 727, 728, 729, 730, 731, 732, 733, 734, 735, 736, 737, 738, 739, 740, 741, 742, 743, 744, 745, 746, 747, 748, 749, 750, 751, 752, 753, 754, 755, 756, 757, 758, 759, 760, 761, 762, 763, 764, 765, 766, 767, 768, 769, 770, 771, 772, 773, 774, 775, 776, 777, 778, 779, 780, 781, 782, 783, 784, 785, 786, 787, 788, 789, 790, 791, 792, 793, 794, 795, 796, 797, 798, 799, 800, 801, 802, 803, 804, 805, 806, 807, 808, 809, 810, 811, 812, 813, 814, 815, 816, 817, 818, 819, 820, 821, 822, 823, 824, 825, 826, 827, 828, 829, 830, 831, 832, 833, 834, 835, 836, 837, 838, 839, 840, 841, 842, 843, 844, 845, 846, 847, 848, 849, 850, 851, 852, 853, 854, 855, 856, 857, 858, 859, 860, 861, 862, 863, 864, 865, 866, 867, 868, 869, 870, 871, 872, 873, 874, 875, 876, 877, 878, 879, 880, 881, 882, 883, 884, 885, 886, 887, 888, 889, 890, 891, 892, 893, 894, 895, 896, 897, 898, 899, 900, 901, 902, 903, 904, 905, 906, 907, 908, 909, 910, 911, 912, 913, 914, 915, 916, 917, 918, 919, 920, 921, 922, 923, 924, 925, 926, 927, 928, 929, 930, 931, 932, 933, 934, 935, 936, 937, 938, 939, 940, 941, 942, 943, 944, 945, 946, 947, 948, 949, 950, 951, 952, 953, 954, 955, 956, 957, 958, 959, 960, 961, 962, 963, 964, 965, 966, 967, 968, 969, 970, 971, 972, 973, 974, 975, 976, 977, 978, 979, 980, 981, 982, 983, 984, 985, 986, 987, 988, 989, 990, 991, 992, 993, 994, 995, 996, 997, 998, 999, 1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010, 1011, 1012, 1013, 1014, 1015, 1016, 1017, 1018, 1019, 1020, 1021, 1022, 1023, 1024, 1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, 1033, 1034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 1043, 1044, 1045, 1046, 1047, 1048, 1049, 1050, 1051, 1052, 1053, 1054, 1055, 1056, 1057, 1058, 1059, 1060, 1061, 1062, 1063, 1064, 1065, 1066, 1067, 1068, 1069, 1070, 1071, 1072, 1073, 1074, 1075, 1076, 1077, 1078, 1079, 1080, 1081, 1082, 1083, 1084, 1085, 1086, 1087, 1088, 1089, 1090, 1091, 1092, 1093, 1094, 1095, 1096, 1097, 1098, 1099, 1100, 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110, 1111, 1112, 1113, 1114, 1115, 1116, 1117, 1118, 1119, 1120, 1121, 1122, 1123, 1124, 1125, 1126, 1127, 1128, 1129, 1130, 1131, 1132, 1133, 1134, 1135, 1136, 1137, 1138, 1139, 1140, 1141, 1142, 1143, 1144, 1145, 1146, 1147, 1148, 1149, 1150, 1151, 1152, 1153, 1154, 1155, 1156, 1157, 1158, 1159, 1160, 1161, 1162, 1163, 1164, 1165, 1166, 1167, 1168, 1169, 1170, 1171, 1172, 1173, 1174, 1175, 1176, 1177, 1178, 1179, 1180, 1181, 1182, 1183, 1184, 1185, 1186, 1187, 1188, 1189, 1190, 1191, 1192, 1193, 1194, 1195, 1196, 1197, 1198, 1199, 1200, 1201, 1202, 1203, 1204, 1205, 1206, 1207, 1208, 1209, 1210, 1211, 1212, 1213, 1214, 1215, 1216, 1217, 1218, 1219, 1220, 1221, 1222, 1223, 1224, 1225, 1226, 1227, 1228, 1229, 1230, 1231, 1232, 1233, 1234, 1235, 1236, 1237, 1238, 1239, 1240, 1241, 1242, 1243, 1244, 1245, 1246, 1247, 1248, 1249, 1250, 1251, 1252, 1253, 1254, 1255, 1256, 1257, 1258, 1259, 1260, 1261, 1262, 1263, 1264, 1265, 1266, 1267, 1268, 1269, 1270, 1271, 1272, 1273, 1274, 1275, 1276, 1277, 1278, 1279, 1280, 1281, 1282, 1283, 1284, 1285, 1286, 1287, 1288, 1289, 1290, 1291, 1292, 1293, 1294, 1295, 1296, 1297, 1298, 1299, 1300, 1301, 1302, 1303, 1304, 1305, 1306, 1307, 1308, 1309, 1310, 1311, 1312, 1313, 1314, 1315, 1316, 1317, 1318, 1319, 1320, 1321, 1322, 1323, 1324, 1325, 1326, 1327, 1328, 1329, 1330, 1331, 1332, 1333, 1334, 1335, 1336, 1337, 1338, 1339, 1340, 1341, 1342, 1343, 1344, 1345, 1346, 1347, 1348, 1349, 1350, 1351, 1352, 1353, 1354, 1355, 1356, 1357, 1358, 1359, 1360, 1361, 1362, 1363, 1364, 1365, 1366, 1367, 1368, 1369, 1370, 1371, 1372, 1373, 1374, 1375, 1376, 1377, 1378, 1379, 1380, 1381, 1382, 1383, 1384, 1385, 1386, 1387, 1388, 1389, 1390, 1391, 1392, 1393, 1394, 1395, 1396, 1397, 1398, 1399, 1400, 1401, 1402, 1403, 1404, 1405, 1406, 1407, 1408, 1409, 1410, 1411, 1412, 1413, 1414, 1415, 1416, 1417, 1418, 1419, 1420, 1421, 1422, 1423, 1424, 1425, 1426, 1427, 1428, 1429, 1430, 1431, 1432, 1433, 1434, 1435, 1436, 1437, 1438, 1439, 1440, 1441, 1442, 1443, 1444, 1445, 1446, 1447, 1448, 1449, 1450, 1451, 1452, 1453, 1454, 1455, 1456, 1457, 1458, 1459, 1460, 1461, 1462, 1463, 1464, 1465, 1466, 1467, 1468, 1469, 1470, 1471, 1472, 1473, 1474, 1475, 1476, 1477, 1478, 1479, 1480, 1481, 1482, 1483, 1484, 1485, 1486, 1487, 1488, 1489, 1490, 1491, 1492, 1493, 1494, 1495, 1496, 1497, 1498, 1499, 1500, 1501, 1502, 1503, 1504, 1505, 1506, 1507, 1508, 1509, 1510, 1511, 1512, 1513, 1514, 1515, 1516, 1517, 1518, 1519, 1520, 1521, 1522, 1523, 1524, 1525, 1526, 1527, 1528, 1529, 1530, 1531, 1532, 1533, 1534, 1535, 1536, 1537, 1538, 1539, 1540, 1541, 1542, 1543, 1544, 1545, 1546, 1547, 1548, 1549, 1550, 1551, 1552, 1553, 1554, 1555, 1556, 1557, 1558, 1559, 1560, 1561, 1562, 1563, 1564, 1565, 1566, 1567, 1568, 1569, 1570, 1571, 1572, 1573, 1574, 1575, 1576, 1577, 1578, 1579, 1580, 1581, 1582, 1583, 1584, 1585, 1586, 1587, 1588, 1589, 1590, 1591, 1592, 1593, 1594, 1595, 1596, 1597, 1598, 1599, 1600, 1601, 1602, 1603, 1604, 1605, 1606, 1607, 1608, 1609, 1610, 1611, 1612, 1613, 1614, 1615, 1616, 1617, 1618, 1619, 1620, 1621, 1622, 1623, 1624, 1625, 1626, 1627, 1628, 1629, 1630, 1631, 1632, 1633, 1634, 1635, 1636, 1637, 1638, 1639, 1640, 1641, 1642, 1643, 1644, 1645, 1646, 1647, 1648, 1649, 1650, 1651, 1652, 1653, 1654, 1655, 1656, 1657, 1658, 1659, 1660, 1661, 1662, 1663, 1664, 1665, 1666, 1667, 1668, 1669, 1670, 1671, 1672, 1673, 1674, 1675, 1676, 1677, 1678, 1679, 1680, 1681, 1682, 1683, 1684, 1685, 1686, 1687, 1688, 1689, 1690, 1691, 1692, 1693, 1694, 1695, 1696, 1697, 1698, 1699, 1700, 1701, 1702, 1703, 1704, 1705, 1706, 1707, 1708, 1709, 1710, 1711, 1712, 1713, 1714, 1715, 1716, 1717, 1718, 1719, 1720, 1721, 1722, 1723, 1724, 1725, 1726, 1727, 1728, 1729, 1730, 1731, 1732, 1733, 1734, 1735, 1736, 1737, 1738, 1739, 1740, 1741, 1742, 1743, 1744, 1745, 1746, 1747, 1748, 1749, 1750, 1751, 1752, 1753, 1754, 1755, 1756, 1757, 1758, 1759, 1760, 1761, 1762, 1763, 1764, 1765, 1766, 1767, 1768, 1769, 1770, 1771, 1772, 1773, 1774, 1775, 1776, 1777, 1778, 1779, 1780, 1781, 1782, 1783, 1784, 1785, 1786, 1787, 1788, 1789, 1790, 1791, 1792, 1793, 1794, 1795, 1796, 1797, 1798, 1799, 1800, 1801, 1802, 1803, 1804, 1805, 1806, 1807, 1808, 1809, 1810, 1811, 1812, 1813, 1814, 1815, 1816, 1817, 1818, 1819, 1820, 1821, 1822, 1823, 1824, 1825, 1826, 1827, 1828, 1829, 1830, 1831, 1832, 1833, 1834, 1835, 1836, 1837, 1838, 1839, 1840, 1841, 1842, 1843, 1844, 1845, 1846, 1847, 1848, 1849, 1850, 1851, 1852, 1853, 1854, 1855, 1856, 1857, 1858, 1859, 1860, 1861, 1862, 1863, 1864, 1865, 1866, 1867, 1868, 1869, 1870, 1871, 1872, 1873, 1874, 1875, 1876, 1877, 1878, 1879, 1880, 1881, 1882, 1883, 1884, 1885, 1886, 1887, 1888, 1889, 1890, 1891, 1892, 1893, 1894, 1895, 1896, 1897, 1898, 1899, 1900, 1901, 1902, 1903, 1904, 1905, 1906, 1907, 1908, 1909, 1910, 1911, 1912, 1913, 1914, 1915, 1916, 1917, 1918, 1919, 1920, 1921, 1922, 1923, 1924, 1925, 1926, 1927, 1928, 1929, 1930, 1931, 1932, 1933, 1934, 1935, 1936, 1937, 1938, 1939, 1940, 1941, 1942, 1943, 1944, 1945, 1946, 1947, 1948, 1949, 1950, 1951, 1952, 1953, 1954, 1955, 1956, 1957, 1958, 1959, 1960, 1961, 1962, 1963, 1964, 1965, 1966, 1967, 1968, 1969, 1970, 1971, 1972, 1973, 1974, 1975, 1976, 1977, 1978, 1979, 1980, 1981, 1982, 1983, 1984, 1985, 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026, 2027, 2028, 2029, 2030, 2031, 2032, 2033, 2034, 2035, 2036, 2037, 2038, 2039, 2040, 2041, 2042, 2043, 2044, 2045, 2046, 2047, 2048, 2049, 2050, 2051, 2052, 2053, 2054, 2055, 2056, 2057, 2058, 2059, 2060, 2061, 2062, 2063, 2064, 2065, 2066, 2067, 2068, 2069, 2070, 2071, 2072, 2073, 2074, 2075, 2076, 2077, 2078, 2079, 2080, 2081, 2082, 2083, 2084, 2085, 2086, 2087, 2088, 2089, 2090, 2091, 2092, 2093, 2094, 2095, 2096, 2097, 2098, 2099, 2100, 2101, 2102, 2103, 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119, 2120, 2121, 2122, 2123, 2124, 2125, 2126, 2127, 2128, 2129, 2130, 2131, 2132, 2133, 2134, 2135, 2136, 2137, 2138, 2139, 2140, 2141, 2142, 2143, 2144, 2145, 2146, 2147, 2148, 2149, 2150, 2151, 2152, 2153, 2154, 2155, 2156, 2157, 2158, 2159, 2160, 2161, 2162, 2163, 2164, 2165, 2166, 2167, 2168, 2169, 2170, 2171, 2172, 2173, 2174, 2175, 2176, 2177, 2178, 2179, 2180, 2181, 2182, 2183, 2184, 2185, 2186, 2187, 2188, 2189, 2190, 2191, 2192, 2193, 2194, 2195, 2196, 2197, 2198, 2199, 2200, 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216, 2217, 2218, 2219, 2220, 2221, 2222, 2223, 2224, 2225, 2226, 2227, 2228, 2229, 2230, 2231, 2232, 2233, 2234, 2235, 2236, 2237, 2238, 2239, 2240, 2241, 2242, 2243, 2244, 2245, 2246, 2247, 2248, 2249, 2250, 2251, 2252, 2253, 2254, 2255, 2256, 2257, 2258, 2259, 2260, 2261, 2262, 2263, 2264, 2265, 2266, 2267, 2268, 2269, 2270, 2271, 2272, 2273, 2274, 2275, 2276, 2277, 2278, 2279, 2280, 2281, 2282, 2283, 2284, 2285, 2286, 2287, 2288, 2289, 2290, 2291, 2292, 2293, 2294, 2295, 2296, 2297, 2298, 2299, 2300, 2301, 2302, 2303, 2304, 2305, 2306, 2307, 2308, 2309, 2310, 2311, 2312, 2313, 2314, 2315, 2316, 2317, 2318, 2319, 2320, 2321, 2322, 2323, 2324, 2325, 2326, 2327, 2328, 2329, 2330, 2331, 2332, 2333, 2334, 2335, 2336, 2337, 2338, 2339, 2340, 2341, 2342, 2343, 2344, 2345, 2346, 2347, 2348, 2349, 2350, 2351, 2352, 2353, 2354, 2355, 2356, 2357, 2358, 2359, 2360, 2361, 2362, 2363, 2364, 2365, 2366, 2367, 2368, 2369, 2370, 2371, 2372, 2373, 2374, 2375, 2376, 2377, 2378, 2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2437, 2438, 2439, 2440, 2441, 2442, 2443, 2444, 2445, 2446, 2447, 2448, 2449, 2450, 2451, 2452, 2453, 2454, 2455, 2456, 2457, 2458, 2459, 2460, 2461, 2462, 2463, 2464, 2465, 2466, 2467, 2468, 2469, 2470, 2471, 2472, 2473, 2474, 2475, 2476, 2477, 2478, 2479, 2480, 2481, 2482, 2483, 2484, 2485, 2486, 2487, 2488, 2489, 2490, 2491, 2492, 2493, 2494, 2495, 2496, 2497, 2498, 2499, 2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2526, 2527, 2528, 2529, 2530, 2531, 2532, 2533, 2534, 2535, 2536, 2537, 2538, 2539, 2540, 2541, 2542, 2543, 2544, 2545, 2546, 2547, 2548, 2549, 2550, 2551, 2552, 2553, 2554, 2555, 2556, 2557, 2558, 2559, 2560, 2561, 2562, 2563, 2564, 2565, 2566, 2567, 2568, 2569, 2570, 2571, 2572, 2573, 2574, 2575, 2576, 2577, 2578, 2579, 2580, 2581, 2582, 2583, 2584, 2585, 2586, 2587, 2588, 2589, 2590, 2591, 2592, 2593, 2594, 2595, 2596, 2597, 2598, 2599, 2600, 2601, 2602, 2603, 2604, 2605, 2606, 2607, 2608, 2609, 2610, 2611, 2612, 2613, 2614, 2615, 2616, 2617, 2618, 2619, 2620, 2621, 2622, 2623, 2624, 2625, 2626, 2627, 2628, 2629, 2630, 2631, 2632, 2633, 2634, 2635, 2636, 2637, 2638, 2639, 2640, 2641, 2642, 2643, 2644, 2645, 2646, 2647, 2648, 2649, 2650, 2651, 2652, 2653, 2654, 2655, 2656, 2657, 2658, 2659, 2660, 2661, 2662, 2663, 2664, 2665, 2666, 2667, 2668, 2669, 2670, 2671, 2672, 2673, 2674, 2675, 2676, 2677, 2678, 2679, 2680, 2681, 2682, 2683, 2684, 2685, 2686, 2687, 2688, 2689, 2690, 2691, 2692, 2693, 2694, 2695, 2696, 2697, 2698, 2699, 2700, 2701, 2702, 2703, 2704, 2705, 2706, 2707, 2708, 2709, 2710, 2711, 2712, 2713, 2714, 2715, 2716, 2717, 2718, 2719, 2720, 2721, 2722, 2723, 2724, 2725, 2726, 2727, 2728, 2729, 2730, 2731, 2732, 2733, 2734, 2735, 2736, 2737, 2738, 2739, 2740, 2741, 2742, 2743, 2744, 2745, 2746, 2747, 2748, 2749, 2750, 2751, 2752, 2753, 2754, 2755, 2756, 2757, 2758, 2759, 2760, 2761, 2762, 2763, 2764, 2765, 2766, 2767, 2768, 2769, 2770, 2771, 2772, 2773, 2774, 2775, 2776, 2777, 2778, 2779, 2780, 2781, 2782, 2783, 2784, 2785, 2786, 2787, 2788, 2789, 2790, 2791, 2792, 2793, 2794, 2795, 2796, 2797, 2798, 2799, 2800, 2801, 2802, 2803, 2804, 2805, 2806, 2807, 2808, 2809, 2810, 2811, 2812, 2813, 2814, 2815, 2816, 2817, 2818, 2819, 2820, 2821, 2822, 2823, 2824, 2825, 2826, 2827, 2828, 2829, 2830, 2831, 2832, 2833, 2834, 2835, 2836, 2837, 2838, 2839, 2840, 2841, 2842, 2843, 2844, 2845, 2846, 2847, 2848, 2849, 2850, 2851, 2852, 2853, 2854, 2855, 2856, 2857, 2858, 2859, 2860, 2861, 2862, 2863, 2864, 2865, 2866, 2867, 2868, 2869, 2870, 2871, 2872, 2873, 2874, 2875, 2876, 2877, 2878, 2879, 2880, 2881, 2882, 2883, 2884, 2885, 2886, 2887, 2888, 2889, 2890, 2891, 2892, 2893, 2894, 2895, 2896, 2897, 2898, 2899, 2900, 2901, 2902, 2903, 2904, 2905, 2906, 2907, 2908, 2909, 2910, 2911, 2912, 2913, 2914, 2915, 2916, 2917, 2918, 2919, 2920, 2921, 2922, 2923, 2924, 2925, 2926, 2927, 2928, 2929, 2930, 2931, 2932, 2933, 2934, 2935, 2936, 2937, 2938, 2939, 2940, 2941, 2942, 2943, 2944, 2945, 2946, 2947, 2948, 2949, 2950, 2951, 2952, 2953, 2954, 2955, 2956, 2957, 2958, 2959, 2960, 2961, 2962, 2963, 2964, 2965, 2966, 2967, 2968, 2969, 2970, 2971, 2972, 2973, 2974, 2975, 2976, 2977, 2978, 2979, 2980, 2981, 2982, 2983, 2984, 2985, 2986, 2987, 2988, 2989, 2990, 2991, 2992, 2993, 2994, 2995, 2996, 2997, 2998, 2999, 3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010, 3011, 3012, 3013, 3014, 3015, 3016, 3017, 3018, 3019, 3020, 3021, 3022, 3023, 3024, 3025, 3026, 3027, 3028, 3029, 3030, 3031, 3032, 3033, 3034, 3035, 3036, 3037, 3038, 3039, 3040, 3041, 3042, 3043, 3044, 3045, 3046, 3047, 3048, 3049, 3050, 3051, 3052, 3053, 3054, 3055, 3056, 3057, 3058, 3059, 3060, 3061, 3062, 3063, 3064, 3065, 3066, 3067, 3068, 3069, 3070, 3071, 3072, 3073, 3074, 3075, 3076, 3077, 3078, 3079, 3080, 3081, 3082, 3083, 3084, 3085, 3086, 3087, 3088, 3089, 3090, 3091, 3092, 3093, 3094, 3095, 3096, 3097, 3098, 3099, 3100, 3101, 3102, 3103, 3104, 3105, 3106, 3107, 3108, 3109, 3110, 3111, 3112, 3113, 3114, 3115, 3116, 3117, 3118, 3119, 3120, 3121, 3122, 3123, 3124, 3125, 3126, 3127, 3128, 3129, 3130, 3131, 3132, 3133, 3134, 3135, 3136, 3137, 3138, 3139, 3140, 3141, 3142, 3143, 3144, 3145, 3146, 3147, 3148, 3149, 3150, 3151, 3152, 3153, 3154, 3155, 3156, 3157, 3158, 3159, 3160, 3161, 3162, 3163, 3164, 3165, 3166, 3167, 3168, 3169, 3170, 3171, 3172, 3173, 3174, 3175, 3176, 3177, 3178, 3179, 3180, 3181, 3182, 3183, 3184, 3185, 3186, 3187, 3188, 3189, 3190, 3191, 3192, 3193, 3194, 3195, 3196, 3197, 3198, 3199, 3200, 3201, 3202, 3203, 3204, 3205, 3206, 3207, 3208, 3209, 3210, 3211, 3212, 3213, 3214, 3215, 3216, 3217, 3218, 3219, 3220, 3221, 3222, 3223, 3224, 3225, 3226, 3227, 3228, 3229, 3230, 3231, 3232, 3233, 3234, 3235, 3236, 3237, 3238, 3239, 3240, 3241, 3242, 3243, 3244, 3245, 3246, 3247, 3248, 3249, 3250, 3251, 3252, 3253, 3254, 3255, 3256, 3257, 3258, 3259, 3260, 3261, 3262, 3263, 3264, 3265, 3266, 3267, 3268, 3269, 3270, 3271, 3272, 3273, 3274, 3275, 3276, 3277, 3278, 3279, 3280, 3281, 3282, 3283, 3284, 3285, 3286, 3287, 3288, 3289, 3290, 3291, 3292, 3293, 3294, 3295, 3296, 3297, 3298, 3299, 3300, 3301, 3302, 3303, 3304, 3305, 3306, 3307, 3308, 3309, 3310, 3311, 3312, 3313, 3314, 3315, 3316, 3317, 3318, 3319, 3320, 3321, 3322, 3323, 3324, 3325, 3326, 3327, 3328, 3329, 3330, 3331, 3332, 3333, 3334, 3335, 3336, 3337, 3338, 3339, 3340, 3341, 3342, 3343, 3344, 3345, 3346, 3347, 3348, 3349, 3350, 3351, 3352, 3353, 3354, 3355, 3356, 3357, 3358, 3359, 3360, 3361, 3362, 3363, 3364, 3365, 3366, 3367, 3368, 3369, 3370, 3371, 3372, 3373, 3374, 3375, 3376, 3377, 3378, 3379, 3380, 3381, 3382, 3383, 3384, 3385, 3386, 3387, 3388, 3389, 3390, 3391, 3392, 3393, 3394, 3395, 3396, 3397, 3398, 3399, 3400, 3401, 3402, 3403, 3404, 3405, 3406, 3407, 3408, 3409, 3410, 3411, 3412, 3413, 3414, 3415, 3416, 3417, 3418, 3419, 3420, 3421, 3422, 3423, 3424, 3425, 3426, 3427, 3428, 3429, 3430, 3431, 3432, 3433, 3434, 3435, 3436, 3437, 3438, 3439, 3440, 3441, 3442, 3443, 3444, 3445, 3446, 3447, 3448, 3449, 3450, 3451, 3452, 3453, 3454, 3455, 3456, 3457, 3458, 3459, 3460, 3461, 3462, 3463, 3464, 3465, 3466, 3467, 3468, 3469, 3470, 3471, 3472, 3473, 3474, 3475, 3476, 3477, 3478, 3479, 3480, 3481, 3482, 3483, 3484, 3485, 3486, 3487, 3488, 3489, 3490, 3491, 3492, 3493, 3494, 3495, 3496, 3497, 3498, 3499, 3500, 3501, 3502, 3503, 3504, 3505, 3506, 3507, 3508, 3509, 3510, 3511, 3512, 3513, 3514, 3515, 3516, 3517, 3518, 3519, 3520, 3521, 3522, 3523, 3524, 3525, 3526, 3527, 3528, 3529, 3530, 3531, 3532, 3533, 3534, 3535, 3536, 3537, 3538, 3539, 3540, 3541, 3542, 3543, 3544, 3545, 3546, 3547, 3548, 3549, 3550, 3551, 3552, 3553, 3554, 3555, 3556, 3557, 3558, 3559, 3560, 3561, 3562, 3563, 3564, 3565, 3566, 3567, 3568, 3569, 3570, 3571, 3572, 3573, 3574, 3575, 3576, 3577, 3578, 3579, 3580, 3581, 3582, 3583, 3584, 3585, 3586, 3587, 3588, 3589, 3590, 3591, 3592, 3593, 3594, 3595, 3596, 3597, 3598, 3599, 3600, 3601, 3602, 3603, 3604, 3605, 3606, 3607, 3608, 3609, 3610, 3611, 3612, 3613, 3614, 3615, 3616, 3617, 3618, 3619, 3620, 3621, 3622, 3623, 3624, 3625, 3626, 3627, 3628, 3629, 3630, 3631, 3632, 3633, 3634, 3635, 3636, 3637, 3638, 3639, 3640, 3641, 3642, 3643, 3644, 3645, 3646, 3647, 3648, 3649, 3650, 3651, 3652, 3653, 3654, 3655, 3656, 3657, 3658, 3659, 3660, 3661, 3662, 3663, 3664, 3665, 3666, 3667, 3668, 3669, 3670, 3671, 3672, 3673, 3674, 3675, 3676, 3677, 3678, 3679, 3680, 3681, 3682, 3683, 3684, 3685, 3686, 3687, 3688, 3689, 3690, 3691, 3692, 3693, 3694, 3695, 3696, 3697, 3698, 3699, 3700, 3701, 3702, 3703, 3704, 3705, 3706, 3707, 3708, 3709, 3710, 3711, 3712, 3713, 3714, 3715, 3716, 3717, 3718, 3719, 3720, 3721, 3722, 3723, 3724, 3725, 3726, 3727, 3728, 3729, 3730, 3731, 3732, 3733, 3734, 3735, 3736, 3737, 3738, 3739, 3740, 3741, 3742, 3743, 3744, 3745, 3746, 3747, 3748, 3749, 3750, 3751, 3752, 3753, 3754, 3755, 3756, 3757, 3758, 3759, 3760, 3761, 3762, 3763, 3764, 3765, 3766, 3767, 3768, 3769, 3770, 3771, 3772, 3773, 3774, 3775, 3776, 3777, 3778, 3779, 3780, 3781, 3782, 3783, 3784, 3785, 3786, 3787, 3788, 3789, 3790, 3791, 3792, 3793, 3794, 3795, 3796, 3797, 3798, 3799, 3800, 3801, 3802, 3803, 3804, 3805, 3806, 3807, 3808, 3809, 3810, 3811, 3812, 3813, 3814, 3815, 3816, 3817, 3818, 3819, 3820, 3821, 3822, 3823, 3824, 3825, 3826, 3827, 3828, 3829, 3830, 3831, 3832, 3833, 3834, 3835, 3836, 3837, 3838, 3839, 3840, 3841, 3842, 3843, 3844, 3845, 3846, 3847, 3848, 3849, 3850, 3851, 3852, 3853, 3854, 3855, 3856, 3857, 3858, 3859, 3860, 3861, 3862, 3863, 3864, 3865, 3866, 3867, 3868, 3869, 3870, 3871, 3872, 3873, 3874, 3875, 3876, 3877, 3878, 3879, 3880, 3881, 3882, 3883, 3884, 3885, 3886, 3887, 3888, 3889, 3890, 3891, 3892, 3893, 3894, 3895, 3896, 3897, 3898, 3899, 3900, 3901, 3902, 3903, 3904, 3905, 3906, 3907, 3908, 3909, 3910, 3911, 3912, 3913, 3914, 3915, 3916, 3917, 3918, 3919, 3920, 3921, 3922, 3923, 3924, 3925, 3926, 3927, 3928, 3929, 3930, 3931, 3932, 3933, 3934, 3935, 3936, 3937, 3938, 3939, 3940, 3941, 3942, 3943, 3944, 3945, 3946, 3947, 3948, 3949, 3950, 3951, 3952, 3953, 3954, 3955, 3956, 3957, 3958, 3959, 3960, 3961, 3962, 3963, 3964, 3965, 3966, 3967, 3968, 3969, 3970, 3971, 3972, 3973, 3974, 3975, 3976, 3977, 3978, 3979, 3980, 3981, 3982, 3983, 3984, 3985, 3986, 3987, 3988, 3989, 3990, 3991, 3992, 3993, 3994, 3995, 3996, 3997, 3998, 3999, 4000, 4001, 4002, 4003, 4004, 4005, 4006, 4007, 4008, 4009, 4010, 4011, 4012, 4013, 4014, 4015, 4016, 4017, 4018, 4019, 4020, 4021, 4022, 4023, 4024, 4025, 4026, 4027, 4028, 4029, 4030, 4031, 4032, 4033, 4034, 4035, 4036, 4037, 4038, 4039, 4040, 4041, 4042, 4043, 4044, 4045, 4046, 4047, 4048, 4049, 4050, 4051, 4052, 4053, 4054, 4055, 4056]
-  U: present=[1, 2, 3, 4, 5, 6, 7, 104, 301]  missing=[8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300]
-  Y: present=[1, 2]  missing=[]
diff --git a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-value-census.txt b/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-value-census.txt
deleted file mode 100644
index ac6d4da..0000000
--- a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-designator-value-census.txt
+++ /dev/null
@@ -1,85 +0,0 @@
-designator | CO x,y | nearby plain text (r<=22, ordered by distance)
-C1     (  397.0,  378.7)  ['C1', '100nF', 'WAKE']
-C2     (  440.0,  443.7)  ['C2', '100nF']
-C3     (  527.0,  443.7)  ['C3', '100nF']
-C4     (  563.0,  493.7)  ['C4', '100nF', '+3.3V']
-C5     (  794.0,  392.7)  ['C5', '100nF', '+5VOUT']
-C6     (  440.0,   41.1)  ['C6', 'C601', 'I', '1', '1']
-C7     (  188.0,   68.7)  ['C7', '100nF']
-C8     (  311.0,   68.7)  ['C8', '100nF']
-C10    (  521.0,   98.7)  ['C10', 'B5819W']
-C15    (   45.5,  140.7)  ['C15', '10uF', 'GND', '0.8Ω']
-C16    (  319.5,  162.7)  ['C16', '10uF']
-C17    (  405.5,  162.7)  ['C17', '10uF']
-C18    (  694.0,  169.7)  ['C18', '22uF']
-C19    (  528.5,  176.7)  ['C19', '22uF', '3015']
-C21    (  168.0,  198.7)  ['C21', '10uF', '10KΩ']
-C24    (  276.0,   68.7)  ['C24', '10uF/35V']
-C25    (  578.5,   83.1)  ['C25', '10uF']
-C26    (  196.5,  284.7)  ['C26', '100nF', 'VBAT_IN']
-C27    (   81.5,  480.7)  ['C27', '2701', '2C', '0I', '10uF']
-C28    (   59.5,  329.7)  ['C28', 'GND', '6.0pF']
-C29    (   59.5,  365.7)  ['C29', '6.0pF', '6.0pF']
-C30    (  715.5,  292.1)  ['C30', '22uF']
-C31    (  744.5,  292.1)  ['C31', '100nF', '+3.3V']
-C32    (  506.5,  299.7)  ['C32', '100nF']
-C33    (  535.5,  299.7)  ['C33', '22uF']
-D1     (  210.0,  111.7)  ['D1']
-D2     (  442.5,  198.7)  ['D2']
-D3     (  325.0,  205.7)  ['D3', 'GND']
-D4     (  325.0,  241.7)  ['D4', 'B5819WT', 'BTNPID402']
-D5     (  197.0,  363.7)  ['D5']
-D6     (  110.0,  429.1)  ['D6', '1N4148WT']
-D7     (  110.0,  504.7)  ['D7', '1N4148WT']
-D8     (  721.5,  147.7)  ['D8']
-D9     (  476.5,   39.7)  ['D9']
-D10    (  254.5,  299.7)  ['D10', '10KΩ']
-D11    (  528.5,   61.7)  ['D11', 'GND']
-D12    (  248.5,   65.7)  ['D12', 'SD36', 'SL']
-D13    (  211.0,   39.7)  ['D13']
-FPC1   (  676.0,  364.7)  ['FPC1', 'FPC-0.5-8P', '2']
-J1     (  124.0,   40.7)  ['J1', '1', '1']
-J2     (  664.5,   54.7)  ['J2', '2']
-J3     (  773.0,  429.7)  ['J3', '1', 'GND', 'IIC_SCL', '2']
-J4     (  773.0,  494.7)  ['J4', 'I', '1', '2', 'O', 'GND']
-J5     (  455.0,  350.7)  ['J5', '1', 'b1']
-L1     (  470.0,   65.7)  ['L1', '3015', 'B5819W', 'R5']
-L4     (  527.5,  144.7)  ['L4', '3015']
-LS1    (  153.5,  439.7)  ['LS1']
-M1     (  282.0,  386.7)  ['M1', '1', 'G1', '2']
-Q1     (  708.0,   54.7)  ['Q1', 'IQ108', '1', '6', '5', '2', '2']
-Q3     (  195.0,  139.1)  ['Q3', 'SS34']
-Q4     (  378.0,  298.7)  ['Q4', 'LN2324DT2AG']
-Q5     (  140.0,  486.7)  ['Q5', 'SS8050']
-Q6     (  360.0,  139.1)  ['Q6', 'GND']
-R1     (  422.0,  371.7)  ['R1', '10KΩ', 'BTN', 'WAKE']
-R2     (  466.0,  436.7)  ['R2', '10KΩ', 'I', 'N', '_']
-R3     (  494.5,  436.7)  ['R3', '10KΩ', 'I', 'N', '_']
-R4     (  333.0,   59.1)  ['R4', '100KΩ', 'P', '1I']
-R5     (  455.0,   80.7)  ['R5', '56KΩ', '3015', '100nF', 'L1']
-R6     (  419.0,  102.7)  ['R6', '10KΩ', 'FB', '3']
-R7     (  754.0,   76.7)  ['R7', '1MΩ', '4', 'VBAT_IN', 'BATADC']
-R8     (  729.0,   88.1)  ['R8', '1MΩ']
-R9     (  174.5,  506.1)  ['R9', '10KΩ', 'Y1']
-R10    (  176.0,  527.7)  ['R10', '10KΩ', '10KΩ', 'R9']
-R11    (   41.5,  112.7)  ['R11', '0.8Ω', 'GND']
-R12    (  485.5,  145.7)  ['R12', '0Ω']
-R13    (  431.0,  162.7)  ['R13', '3.3KΩ']
-R14    (  286.5,  170.1)  ['R14', '100KΩ']
-R15    (  344.5,  170.1)  ['R15', '100KΩ']
-R16    (  661.5,  170.1)  ['R16', '52.3KΩ']
-R17    (  142.5,  198.7)  ['R17', '10KΩ']
-R18    (  661.5,  198.7)  ['R18', '15KΩ', '52.3KΩ']
-R19    (  207.5,  206.1)  ['R19', '100KΩ']
-R23    (  330.0,  328.7)  ['R23', '100KΩ']
-R24    (  142.5,  393.7)  ['R24', '10Ω', '+3.3V']
-R25    (   53.5,  484.7)  ['R25', '470Ω', '0I', '2C']
-S4     (  426.0,  486.7)  ['S4', 'GND', 'SW-PB']
-U1     (  369.0,   40.7)  ['U1', '5', 'VIN']
-U2     (   95.0,  141.7)  ['U2', '4', 'TP4057']
-U3     (  578.0,  141.7)  ['U3', '1', 'U301', 'LX', '2', '2I', 'LX', 'P']
-U4     (  585.0,  271.1)  ['U4', '1', 'VIN', '2', 'GND']
-U5     (   66.0,  263.7)  ['U5', '1', 'OSCI', '2']
-U6     (  599.5,  472.7)  ['U6', 'A2', 'VIN']
-U7     (   73.5,   83.7)  ['U7', '3', 'VCC']
-Y2     (   93.5,  356.7)  ['Y2', '2', '32.768KHz', '1']
diff --git a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-plaintext-layout.txt b/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-plaintext-layout.txt
deleted file mode 100644
index 29ac17a..0000000
--- a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-plaintext-layout.txt
+++ /dev/null
@@ -1,131 +0,0 @@
-y=  31.2 | [109]1  [315]2  [523]3  [729]4
-y=  42.0 | [124]J1  [212]D13  [287]+VIN  [370]U1  [441]C6  [477]D9
-y=  49.2 | [359]5  [424]1  [731]LP3218DT1G
-y=  51.8 | [430]1  [431]I  [436]C601
-y=  52.8 | [137]1  [377]VIN  [406]BST  [519]GND
-y=  56.4 | [104]6V~36V  [664]J2  [709]Q1  [748]VBAT_IN
-y=  60.0 | [136]2  [334]R4
-y=  64.3 | [219]B5819W  [237]SL  [359]4  [446]100nF  [485]B5819W  [504]SL  [529]D11  [589]+5VIN
-y=  67.2 | [250]D12  [351]P  [353]1I  [362]U104  [375]EN  [471]L1  [677]2  [697]2  [706]IQ108  [712]1  [712]6  [712]5  [712]2  [740]4
-y=  70.8 | [131]Header  [143]2  [189]C7  [277]C24  [312]C8  [424]6
-y=  74.4 | [252]SD36  [340]100KΩ  [407]LX  [677]1
-y=  77.3 | [193]100nF  [285]10uF/35V  [316]100nF  [755]R7
-y=  80.4 | [474]3015  [489]10uH
-y=  82.5 | [456]R5  [580]C25
-y=  85.4 | [35]+5VIN  [74]U7  [359]2  [424]3  [536]B5819W  [554]SL  [671]Header  [683]2  [758]1MΩ
-y=  89.0 | [378]GND  [408]FB  [730]R8
-y=  92.6 | [13]A  [64]3  [581]10uF  [768]BATADC  [827]A
-y=  96.2 | [82]VCC  [461]56KΩ
-y=  99.8 | [128]2  [265]GND  [301]GND  [387]ME3116AM6G  [522]C10
-y= 103.4 | [106]RESET  [733]1MΩ
-y= 107.0 | [64]1  [157]GND  [236]GND  [420]R6
-y= 110.6 | [83]GND  [211]D1  [387]GND  [555]GND
-y= 114.2 | [43]R11  [179]+5VIN  [568]GND  [698]GND
-y= 117.1 | [424]10KΩ
-y= 121.4 | [44]0.8Ω  [81]CN809J  [352]GND  [523]22uF
-y= 128.6 | [56]GND
-y= 136.5 | [214]SS34
-y= 142.2 | [46]C15  [196]Q3  [361]Q6
-y= 142.9 | [96]U2  [157]VBAT_IN  [220]AP40P05  [386]AP40P05  [452]VBAT_OUT  [579]U3
-y= 146.0 | [82]4  [487]R12  [528]L4
-y= 149.4 | [48]10uF  [110]TP4057  [568]1  [626]8  [722]D8
-y= 152.8 | [560]P  [562]2I  [571]U301  [584]LX  [607]OUT
-y= 157.3 | [568]2  [626]7
-y= 160.2 | [485]0Ω  [531]3015  [547]1.5uH  [584]LX  [607]OUT  [762]+5VOUT
-y= 162.4 | [85]VCC  [121]3  [320]C16  [407]C17  [432]R13  [568]6
-y= 168.1 | [102]BAT  [322]10uF  [408]10uF  [583]IN  [695]C18
-y= 171.7 | [35]GND  [50]1  [288]R14  [345]R15  [435]3.3KΩ  [663]R16  [725]SS34
-y= 175.3 | [70]CHRG
-y= 178.9 | [49]5  [121]6  [292]100KΩ  [350]100KΩ  [529]C19  [568]3  [668]52.3KΩ  [696]22uF
-y= 182.5 | [72]STDBY  [100]PROG  [584]EN
-y= 185.4 | [531]22uF  [626]5
-y= 189.7 | [610]FB
-y= 191.8 | [85]GND  [308]GND  [395]GND  [568]4
-y= 199.7 | [169]C21  [444]D2  [587]GND
-y= 200.5 | [144]R17  [568]9  [663]R18  [683]GND
-y= 203.6 | [82]2  [148]10KΩ  [589]PGND
-y= 206.9 | [170]10uF  [208]R19  [326]D3  [517]GND  [665]15KΩ
-y= 214.8 | [213]100KΩ  [271]INT  [586]SY7088
-y= 229.2 | [13]B  [336]B5819WT  [561]GND  [827]B
-y= 236.4 | [85]GND  [136]GND  [157]GND  [424]GND  [605]Vout=1.2V*(R1/R2+1)  [654]GND
-y= 243.6 | [200]GND  [246]S1  [326]D4
-y= 251.3 | [309]BTNPID402
-y= 260.4 | [252]SW-PB
-y= 265.4 | [67]U5  [185]VBAT_IN  [265]+3.3V  [336]B5819WT
-y= 272.6 | [35]OSCI  [57]1  [128]8  [229]GND  [586]U4
-y= 276.2 | [76]OSCI  [109]VDD
-y= 279.8 | [36]OSCO  [56]2  [128]7  [249]R20  [576]1  [633]5
-y= 283.4 | [77]OSCO  [103]CLKOUT  [198]C26  [593]VIN  [611]VOUT  [758]+3.3V
-y= 287.0 | [33]INT  [57]3  [128]6  [154]IN_SCL  [575]2
-y= 290.6 | [74]INT  [110]SCL  [251]10KΩ  [594]GND
-y= 294.2 | [56]4  [128]5  [154]IN_SDA  [201]100nF  [575]3  [633]4  [716]C30  [745]C31
-y= 297.8 | [74]VSS  [110]SDA  [591]EN  [616]NC
-y= 300.6 | [255]D10  [325]HOLD  [379]Q4  [508]C32  [536]C33  [718]22uF  [748]100nF
-y= 308.6 | [76]RTC8563  [224]WAKE  [397]LN2324DT2AG  [511]100nF  [538]22uF  [606]BL8075CB5TR33
-y= 315.7 | [49]GND  [186]GND
-y= 323.7 | [264]B5819WT  [705]GND  [734]GND
-y= 330.8 | [61]C28  [331]R23
-y= 337.3 | [114]OSCI  [186]+3.3V  [335]100KΩ  [496]GND  [525]GND  [561]GND
-y= 340.9 | [26]GND
-y= 347.6 | [82]2
-y= 351.0 | [63]6.0pF  [455]J5
-y= 358.2 | [95]Y2  [404]WAKE  [430]BTN  [446]1  [503]2  [637]0
-y= 362.5 | [461]b1  [488]b2  [533]GND  [637]1
-y= 366.1 | [13]C  [106]32.768KHz  [134]±20ppm  [155]12.5pF  [198]D5  [323]GND  [366]GND  [678]FPC1  [827]C
-y= 366.8 | [61]C29  [82]1
-y= 372.6 | [220]PESDNC2FD3V3B
-y= 373.3 | [115]OSCO  [136]+3.3V  [423]R1  [594]LCD_CS  [619]1  [640]0  [686]FPC-0.5-8P  [784]+5VOUT
-y= 376.9 | [26]GND  [460]A  [489]B  [632]1  [640]1
-y= 379.7 | [398]C1  [427]10KΩ  [662]2
-y= 384.1 | [648]2  [707]+3.3V
-y= 386.9 | [63]6.0pF  [284]M1  [402]100nF  [597]LCD_SCK  [619]3
-y= 390.5 | [457]3  [471]4  [485]5  [632]3
-y= 394.8 | [144]R24  [232]GI  [273]1  [662]4  [685]LCD_MOSI  [794]C5
-y= 398.4 | [289]G1  [648]4  [799]100nF
-y= 402.0 | [144]10Ω  [234]GO  [272]2  [416]+3.3V  [462]Rotary  [481]encode  [594]LCD_RS  [619]5
-y= 405.6 | [296]G2  [632]5
-y= 409.2 | [186]GND  [235]beep  [273]3  [388]GND  [662]6  [687]LCD_RESET
-y= 412.8 | [289]G3  [648]6
-y= 416.4 | [241]LCD_RS  [272]4  [457]A  [474]GND  [485]B  [618]7
-y= 420.2 | [296]G4  [457]_  [485]_  [567]GND  [632]7
-y= 423.8 | [245]LCD_MOSI  [273]5  [457]N  [485]N  [662]8  [688]FPC_LCD_BL  [784]GND
-y= 425.8 | [457]I  [485]I
-y= 430.3 | [111]D6  [289]G5  [640]9  [648]8
-y= 431.0 | [244]LCD_SCK  [272]6  [380]+3.3V  [772]J3
-y= 434.6 | [296]G6
-y= 437.5 | [123]1N4148WT  [241]LCD_CS  [272]7  [361]28  [466]R2  [495]R3  [747]SCL  [763]1
-y= 441.1 | [155]LS1  [289]G7  [342]3V3  [637]9  [787]IIC_SCL
-y= 445.4 | [247]LCD_RESET  [273]8  [361]27  [389]HOLD  [441]C2  [471]10KΩ  [499]10KΩ  [528]C3  [747]SDA  [762]2
-y= 449.0 | [296]G8  [334]G46  [787]IIC_SDA
-y= 452.6 | [241]LCD_BL  [272]9  [361]26  [446]100nF  [532]100nF  [763]3
-y= 456.2 | [289]G9  [336]G43/Tx  [734]+5VOUT  [781]VCC
-y= 459.8 | [249]BATADC  [271]10  [361]25  [390]WAKE  [762]4
-y= 464.1 | [158]Buzzer  [297]G10  [324]G42/MTMS  [782]GND
-y= 467.0 | [243]GND  [271]11  [361]24  [460]+3.3V  [489]+3.3V
-y= 470.6 | [292]GND  [336]G44/Rx
-y= 474.2 | [248]IN_SDA  [271]12  [361]23  [388]IN_A  [431]GND  [517]GND  [553]+3.3V  [600]U6  [785]HY-2.0_IIC
-y= 477.8 | [297]G11  [325]G41/MTDI
-y= 481.4 | [271]13  [361]22  [587]A2  [657]A1  [696]FPC_LCD_BL  [755]GND
-y= 482.1 | [82]C27
-y= 487.7 | [29]NLbeep  [54]R25  [142]Q5  [211]+5VIN  [289]5V  [342]EN  [426]S4  [607]VIN  [633]VOUT
-y= 488.6 | [30]beep  [70]0I  [71]2C  [76]2701  [247]IN_SCL  [271]14  [361]21  [388]IN_B
-y= 492.2 | [297]G12  [323]G40/MTDO
-y= 495.0 | [148]SS8050  [163]Y1  [243]SDA  [271]15  [361]20  [564]C4  [657]B2  [688]LCD_BL  [772]J4
-y= 498.6 | [56]470Ω  [290]G13  [335]G0/Boot  [638]EN
-y= 502.9 | [13]D  [84]10uF  [256]G14  [271]16  [361]19  [386]G39  [568]100nF  [737]GI  [763]1  [827]D
-y= 505.8 | [111]D7  [297]G14  [323]G39/MTCK  [433]SW-PB  [776]I
-y= 507.3 | [175]R9  [206]G14  [242]SCL  [271]17  [361]18  [588]B1  [738]GO  [762]2
-y= 513.0 | [123]1N4148WT
-y= 513.7 | [290]G15  [340]GND  [609]GND  [777]O
-y= 517.3 | [763]3
-y= 520.2 | [180]10KΩ  [294]D-  [316]D+  [337]PGND  [734]+5VOUT  [781]VCC
-y= 524.5 | [467]GND  [616]AW35122FDR  [762]4
-y= 528.8 | [177]R10  [782]GND
-y= 531.7 | [206]G39  [380]GND  [553]GND
-y= 535.0 | [291]9  [312]0  [334]1
-y= 538.1 | [291]2  [312]3  [334]3  [784]HY-2.0_IO
-y= 541.8 | [180]10KΩ
-y= 547.5 | [303]STAMP-S3-SMD  [755]GND
-y= 553.3 | [100]GND  [136]GND  [157]GND
-y= 560.5 | [337]GND
-y= 564.1 | [109]1  [315]2  [523]3  [729]4
diff --git a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.bbox.xml b/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.bbox.xml
deleted file mode 100644
index 8b1c41b..0000000
--- a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.bbox.xml
+++ /dev/null
@@ -1,905 +0,0 @@
-<?xml version="1.0"?>
-<pdf2xml>
-<page width="842.00" height="595.00" number="1">
-<word xMin="107.4573" yMin="28.0139" xMax="110.6904" yMax="34.4853">1</word>
-<word xMin="313.9766" yMin="28.0139" xMax="317.2098" yMax="34.4853">2</word>
-<word xMin="521.4555" yMin="28.0139" xMax="524.6886" yMax="34.4853">3</word>
-<word xMin="728.2148" yMin="28.0139" xMax="731.4479" yMax="34.4853">4</word>
-<word xMin="206.9998" yMin="36.2076" xMax="215.0010" yMax="43.2090">COD13</word>
-<word xMin="473.9998" yMin="36.2081" xMax="479.0010" yMax="43.2090">COD9</word>
-<word xMin="120.9998" yMin="37.2080" xMax="127.0010" yMax="44.2090">COJ1</word>
-<word xMin="365.9998" yMin="37.2080" xMax="372.0010" yMax="44.2090">COU1</word>
-<word xMin="207.2390" yMin="38.0804" xMax="218.3753" yMax="44.5518">D13</word>
-<word xMin="473.9632" yMin="38.0804" xMax="481.7468" yMax="44.5518">D9</word>
-<word xMin="436.9999" yMin="37.0949" xMax="443.0013" yMax="45.0960">COC6</word>
-<word xMin="121.6090" yMin="38.7995" xMax="127.2373" yMax="45.2708">J1</word>
-<word xMin="279.6767" yMin="38.7995" xMax="294.9424" yMax="45.2708">+VIN</word>
-<word xMin="366.5060" yMin="38.7995" xMax="374.2895" yMax="45.2708">U1</word>
-<word xMin="437.9842" yMin="39.5184" xMax="445.5893" yMax="45.9897">C6</word>
-<word xMin="357.8710" yMin="45.9897" xMax="361.1042" yMax="52.4611">5</word>
-<word xMin="422.6332" yMin="45.9897" xMax="425.8663" yMax="52.4611">1</word>
-<word xMin="712.3840" yMin="45.9897" xMax="749.6235" yMax="52.4611">LP3218DT1G</word>
-<word xMin="141.0000" yMin="50.7715" xMax="158.0003" yMax="52.7740">PIJ101</word>
-<word xMin="192.0000" yMin="50.7714" xMax="209.0003" yMax="52.7740">PID1301</word>
-<word xMin="213.0000" yMin="50.7713" xMax="231.0003" yMax="52.7740">PID1302</word>
-<word xMin="350.0000" yMin="50.7713" xMax="368.0003" yMax="52.7740">PIU105</word>
-<word xMin="415.0000" yMin="50.7719" xMax="430.8336" yMax="52.7740">PIU10P</word>
-<word xMin="429.1666" yMin="50.7715" xMax="432.0003" yMax="52.7719">1</word>
-<word xMin="430.8333" yMin="50.7734" xMax="432.6669" yMax="52.7737">I</word>
-<word xMin="432.6666" yMin="50.7723" xMax="440.0003" yMax="52.7734">C601</word>
-<word xMin="444.0000" yMin="50.7725" xMax="454.0003" yMax="52.7740">PIC602</word>
-<word xMin="458.0000" yMin="50.7713" xMax="476.0003" yMax="52.7740">PID902</word>
-<word xMin="480.0000" yMin="50.7715" xMax="497.0003" yMax="52.7740">PID901</word>
-<word xMin="135.7607" yMin="49.5849" xMax="138.9938" yMax="56.0562">1</word>
-<word xMin="371.5430" yMin="49.5849" xMax="382.9173" yMax="56.0562">VIN</word>
-<word xMin="400.0864" yMin="49.5849" xMax="412.0232" yMax="56.0562">BST</word>
-<word xMin="512.1009" yMin="49.5849" xMax="526.1096" yMax="56.0562">GND</word>
-<word xMin="661.9998" yMin="51.2081" xMax="667.0010" yMax="58.2090">COJ2</word>
-<word xMin="704.9998" yMin="51.2080" xMax="711.0010" yMax="58.2090">COQ1</word>
-<word xMin="92.8258" yMin="53.1801" xMax="115.4566" yMax="59.6514">6V~36V</word>
-<word xMin="662.0134" yMin="53.1801" xMax="667.6417" yMax="59.6514">J2</word>
-<word xMin="705.1882" yMin="53.1801" xMax="712.9717" yMax="59.6514">Q1</word>
-<word xMin="734.6909" yMin="53.1801" xMax="761.6322" yMax="59.6514">VBAT_IN</word>
-<word xMin="141.0000" yMin="57.6582" xMax="158.0005" yMax="60.6610">PIJ102</word>
-<word xMin="329.9999" yMin="55.0949" xMax="336.0013" yMax="63.0960">COR4</word>
-<word xMin="135.0411" yMin="56.7753" xMax="138.2743" yMax="63.2466">2</word>
-<word xMin="330.5270" yMin="57.4943" xMax="338.1320" yMax="63.9656">R4</word>
-<word xMin="523.9998" yMin="58.2075" xMax="533.0010" yMax="65.2090">COD11</word>
-<word xMin="234.9997" yMin="49.0785" xMax="238.0027" yMax="66.0790">PID1202</word>
-<word xMin="437.9842" yMin="59.6514" xMax="454.5122" yMax="66.1227">100nF</word>
-<word xMin="524.3338" yMin="59.6514" xMax="535.2302" yMax="66.1227">D11</word>
-<word xMin="357.6312" yMin="60.3705" xMax="360.8644" yMax="66.8418">4</word>
-<word xMin="580.7009" yMin="60.3705" xMax="599.0207" yMax="66.8418">+5VIN</word>
-<word xMin="176.9998" yMin="56.8695" xMax="180.0015" yMax="66.8700">PIC702</word>
-<word xMin="263.9998" yMin="56.8695" xMax="267.0015" yMax="66.8700">PIC2402</word>
-<word xMin="299.9998" yMin="56.8695" xMax="303.0015" yMax="66.8700">PIC802</word>
-<word xMin="207.2390" yMin="61.0895" xMax="231.0655" yMax="67.5608">B5819W</word>
-<word xMin="234.0620" yMin="61.0895" xMax="241.5474" yMax="67.5608">SL</word>
-<word xMin="473.9632" yMin="61.0895" xMax="497.7897" yMax="67.5608">B5819W</word>
-<word xMin="500.7862" yMin="61.0895" xMax="508.2716" yMax="67.5608">SL</word>
-<word xMin="321.0000" yMin="64.6592" xMax="332.0005" yMax="67.6610">PIR402</word>
-<word xMin="343.0000" yMin="64.6596" xMax="351.3338" yMax="67.6610">PIR40</word>
-<word xMin="350.0000" yMin="64.6605" xMax="353.0005" yMax="67.6610">P</word>
-<word xMin="351.3333" yMin="64.6593" xMax="356.0005" yMax="67.6605">1I</word>
-<word xMin="356.0000" yMin="64.6580" xMax="368.0005" yMax="67.6600">U104</word>
-<word xMin="682.0000" yMin="64.6586" xMax="699.0005" yMax="67.6610">PIJ20P</word>
-<word xMin="696.1667" yMin="64.6582" xMax="699.0005" yMax="67.6586">2</word>
-<word xMin="699.0000" yMin="64.6580" xMax="714.0005" yMax="67.6605">IQ108</word>
-<word xMin="711.0000" yMin="64.6580" xMax="714.0005" yMax="67.6585">1</word>
-<word xMin="711.0000" yMin="64.6580" xMax="714.0005" yMax="67.6585">6</word>
-<word xMin="711.0000" yMin="64.6580" xMax="714.0005" yMax="67.6585">5</word>
-<word xMin="711.0000" yMin="64.6580" xMax="714.0005" yMax="67.6585">2</word>
-<word xMin="725.0000" yMin="64.6582" xMax="742.0005" yMax="67.6610">PIQ107</word>
-<word xMin="739.1667" yMin="64.6582" xMax="742.0005" yMax="67.6586">4</word>
-<word xMin="243.9998" yMin="62.2075" xMax="253.0010" yMax="69.2090">COD12</word>
-<word xMin="466.9998" yMin="62.2080" xMax="473.0010" yMax="69.2090">COL1</word>
-<word xMin="244.6571" yMin="63.9656" xMax="255.7935" yMax="70.4370">D12</word>
-<word xMin="371.5430" yMin="63.9656" xMax="380.0437" yMax="70.4370">EN</word>
-<word xMin="467.4870" yMin="63.9656" xMax="474.5521" yMax="70.4370">L1</word>
-<word xMin="675.6854" yMin="63.9656" xMax="678.9186" yMax="70.4370">2</word>
-<word xMin="184.9998" yMin="65.2080" xMax="191.0010" yMax="72.2090">COC7</word>
-<word xMin="271.9998" yMin="65.2076" xMax="280.0010" yMax="72.2090">COC24</word>
-<word xMin="307.9998" yMin="65.2080" xMax="314.0010" yMax="72.2090">COC8</word>
-<word xMin="185.6516" yMin="66.8418" xMax="193.2566" yMax="73.3131">C7</word>
-<word xMin="272.2410" yMin="66.8418" xMax="282.8982" yMax="73.3131">C24</word>
-<word xMin="308.2200" yMin="66.8418" xMax="315.8251" yMax="73.3131">C8</word>
-<word xMin="746.9998" yMin="63.8697" xMax="749.0015" yMax="73.8700">PIR702</word>
-<word xMin="121.6090" yMin="67.5608" xMax="140.4655" yMax="74.0321">Header</word>
-<word xMin="141.9656" yMin="67.5608" xMax="145.1988" yMax="74.0321">2</word>
-<word xMin="422.6332" yMin="67.5608" xMax="425.8663" yMax="74.0321">6</word>
-<word xMin="415.0000" yMin="71.6582" xMax="432.0005" yMax="74.6610">PIU106</word>
-<word xMin="458.0000" yMin="71.6592" xMax="469.0005" yMax="74.6610">PIL101</word>
-<word xMin="494.0000" yMin="71.6592" xMax="505.0005" yMax="74.6610">PIL102</word>
-<word xMin="509.0000" yMin="71.6582" xMax="526.0005" yMax="74.6610">PID1101</word>
-<word xMin="530.0000" yMin="71.6580" xMax="548.0005" yMax="74.6610">PID1102</word>
-<word xMin="682.0000" yMin="71.6582" xMax="699.0005" yMax="74.6610">PIJ201</word>
-<word xMin="330.5270" yMin="70.4370" xMax="349.7009" yMax="76.9083">100KΩ</word>
-<word xMin="244.6571" yMin="71.1560" xMax="259.3861" yMax="77.6273">SD36</word>
-<word xMin="403.4444" yMin="71.1560" xMax="411.9450" yMax="77.6273">LX</word>
-<word xMin="676.1651" yMin="71.1560" xMax="679.3983" yMax="77.6273">1</word>
-<word xMin="750.9998" yMin="73.2080" xMax="757.0010" yMax="80.2090">COR7</word>
-<word xMin="185.6516" yMin="74.0321" xMax="202.1795" yMax="80.5035">100nF</word>
-<word xMin="272.2410" yMin="74.0321" xMax="298.4639" yMax="80.5035">10uF/35V</word>
-<word xMin="308.2200" yMin="74.0321" xMax="324.7479" yMax="80.5035">100nF</word>
-<word xMin="751.2413" yMin="74.7512" xMax="758.8463" yMax="81.2225">R7</word>
-<word xMin="176.9998" yMin="70.7565" xMax="180.0017" yMax="81.7570">PIC701</word>
-<word xMin="263.9998" yMin="70.7565" xMax="267.0017" yMax="81.7570">PIC2401</word>
-<word xMin="299.9998" yMin="70.7565" xMax="303.0017" yMax="81.7570">PIC801</word>
-<word xMin="565.9998" yMin="70.7565" xMax="569.0017" yMax="81.7570">PIC2502</word>
-<word xMin="467.4870" yMin="77.1480" xMax="480.7785" yMax="83.6193">3015</word>
-<word xMin="482.0957" yMin="77.1480" xMax="496.5835" yMax="83.6193">10uH</word>
-<word xMin="451.9998" yMin="77.2080" xMax="458.0010" yMax="84.2090">COR5</word>
-<word xMin="453.0954" yMin="79.3051" xMax="460.7004" yMax="85.7764">R5</word>
-<word xMin="573.9999" yMin="79.0944" xMax="583.0013" yMax="87.0960">COC25</word>
-<word xMin="70.9998" yMin="80.2081" xMax="76.0010" yMax="87.2090">COU7</word>
-<word xMin="574.7044" yMin="81.4622" xMax="585.3616" yMax="87.9335">C25</word>
-<word xMin="234.9997" yMin="69.9655" xMax="238.0028" yMax="87.9660">PID1201</word>
-<word xMin="25.9049" yMin="82.1812" xMax="44.2246" yMax="88.6526">+5VIN</word>
-<word xMin="70.9985" yMin="82.1812" xMax="78.7820" yMax="88.6526">U7</word>
-<word xMin="357.8710" yMin="82.1812" xMax="361.1042" yMax="88.6526">2</word>
-<word xMin="422.6332" yMin="82.1812" xMax="425.8663" yMax="88.6526">3</word>
-<word xMin="662.0134" yMin="82.1812" xMax="680.8698" yMax="88.6526">Header</word>
-<word xMin="682.3700" yMin="82.1812" xMax="685.6032" yMax="88.6526">2</word>
-<word xMin="751.2413" yMin="82.1812" xMax="765.1465" yMax="88.6526">1MΩ</word>
-<word xMin="524.3338" yMin="82.9003" xMax="548.1603" yMax="89.3716">B5819W</word>
-<word xMin="551.1568" yMin="82.9003" xMax="558.6422" yMax="89.3716">SL</word>
-<word xMin="350.0000" yMin="86.6580" xMax="368.0005" yMax="89.6610">PIU102</word>
-<word xMin="415.0000" yMin="86.6582" xMax="432.0005" yMax="89.6610">PIU103</word>
-<word xMin="444.0000" yMin="86.6593" xMax="454.0005" yMax="89.6610">PIR501</word>
-<word xMin="466.0000" yMin="86.6593" xMax="476.0005" yMax="89.6610">PIR502</word>
-<word xMin="725.9999" yMin="84.0949" xMax="732.0013" yMax="92.0960">COR8</word>
-<word xMin="371.5430" yMin="85.7764" xMax="385.5517" yMax="92.2477">GND</word>
-<word xMin="404.4039" yMin="85.7764" xMax="412.3096" yMax="92.2477">FB</word>
-<word xMin="726.7756" yMin="86.4955" xMax="734.3807" yMax="92.9668">R8</word>
-<word xMin="574.7044" yMin="88.6526" xMax="588.1188" yMax="95.1239">10uF</word>
-<word xMin="717.9997" yMin="78.0785" xMax="721.0027" yMax="95.0790">PIQ103</word>
-<word xMin="11.0336" yMin="89.3716" xMax="15.7023" yMax="95.8429">A</word>
-<word xMin="62.6035" yMin="89.3716" xMax="65.8366" yMax="95.8429">3</word>
-<word xMin="755.5588" yMin="89.3716" xMax="780.9475" yMax="95.8429">BATADC</word>
-<word xMin="825.3580" yMin="89.3716" xMax="830.0267" yMax="95.8429">A</word>
-<word xMin="565.9998" yMin="85.8695" xMax="569.0015" yMax="95.8700">PIC2501</word>
-<word xMin="746.9998" yMin="85.8697" xMax="749.0015" yMax="95.8700">PIR701</word>
-<word xMin="55.0000" yMin="93.6582" xMax="72.0005" yMax="96.6610">PIU703</word>
-<word xMin="718.0000" yMin="93.6593" xMax="728.0005" yMax="96.6610">PIR802</word>
-<word xMin="739.0000" yMin="93.6593" xMax="749.0005" yMax="96.6610">PIR801</word>
-<word xMin="453.0954" yMin="92.2477" xMax="469.1558" yMax="98.7191">56KΩ</word>
-<word xMin="76.0356" yMin="92.9668" xMax="89.4493" yMax="99.4381">VCC</word>
-<word xMin="516.9998" yMin="95.2076" xMax="525.0010" yMax="102.2090">COC10</word>
-<word xMin="127.3656" yMin="96.5620" xMax="130.5988" yMax="103.0333">2</word>
-<word xMin="258.8088" yMin="96.5620" xMax="272.8175" yMax="103.0333">GND</word>
-<word xMin="294.7878" yMin="96.5620" xMax="308.7965" yMax="103.0333">GND</word>
-<word xMin="366.5060" yMin="96.5620" xMax="407.5775" yMax="103.0333">ME3116AM6G</word>
-<word xMin="119.0000" yMin="100.6580" xMax="137.0005" yMax="103.6610">PIU702</word>
-<word xMin="517.1380" yMin="97.2810" xMax="527.7951" yMax="103.7523">C10</word>
-<word xMin="726.7756" yMin="99.4380" xMax="740.6808" yMax="105.9093">1MΩ</word>
-<word xMin="415.9998" yMin="99.2080" xMax="422.0010" yMax="106.2090">COR6</word>
-<word xMin="96.6636" yMin="100.1571" xMax="116.4208" yMax="106.6284">RESET</word>
-<word xMin="416.8766" yMin="100.8761" xMax="424.4816" yMax="107.3474">R6</word>
-<word xMin="32.9998" yMin="99.8695" xMax="36.0015" yMax="109.8700">PIR1102</word>
-<word xMin="62.8433" yMin="103.7522" xMax="66.0765" yMax="110.2236">1</word>
-<word xMin="150.6320" yMin="103.7522" xMax="164.6407" yMax="110.2236">GND</word>
-<word xMin="229.7858" yMin="103.7522" xMax="243.7945" yMax="110.2236">GND</word>
-<word xMin="55.0000" yMin="107.6582" xMax="72.0005" yMax="110.6610">PIU701</word>
-<word xMin="408.0000" yMin="107.6593" xMax="418.0005" yMax="110.6610">PIR602</word>
-<word xMin="429.0000" yMin="107.6592" xMax="440.0005" yMax="110.6610">PIR601</word>
-<word xMin="509.0000" yMin="107.6593" xMax="519.0005" yMax="110.6610">PIC1002</word>
-<word xMin="523.0000" yMin="107.6593" xMax="533.0005" yMax="110.6610">PIC1001</word>
-<word xMin="76.0356" yMin="107.3474" xMax="90.0442" yMax="113.8187">GND</word>
-<word xMin="380.1780" yMin="107.3474" xMax="394.1866" yMax="113.8187">GND</word>
-<word xMin="548.0799" yMin="107.3474" xMax="562.0886" yMax="113.8187">GND</word>
-<word xMin="206.9998" yMin="108.2080" xMax="213.0010" yMax="115.2090">COD1</word>
-<word xMin="36.9998" yMin="109.2075" xMax="46.0010" yMax="116.2090">COR11</word>
-<word xMin="207.2390" yMin="110.2236" xMax="215.0225" yMax="116.6949">D1</word>
-<word xMin="37.8979" yMin="110.9426" xMax="48.3158" yMax="117.4139">R11</word>
-<word xMin="170.0607" yMin="110.9426" xMax="188.3805" yMax="117.4139">+5VIN</word>
-<word xMin="561.2722" yMin="110.9426" xMax="575.2809" yMax="117.4139">GND</word>
-<word xMin="691.0365" yMin="110.9426" xMax="705.0451" yMax="117.4139">GND</word>
-<word xMin="416.8766" yMin="113.8187" xMax="432.9370" yMax="120.2901">10KΩ</word>
-<word xMin="517.1380" yMin="117.4139" xMax="530.5524" yMax="123.8852">22uF</word>
-<word xMin="37.8979" yMin="118.1330" xMax="50.8447" yMax="124.6043">0.8Ω</word>
-<word xMin="70.9985" yMin="118.1330" xMax="92.1945" yMax="124.6043">CN809J</word>
-<word xMin="345.1584" yMin="118.1330" xMax="359.1670" yMax="124.6043">GND</word>
-<word xMin="192.0000" yMin="122.6582" xMax="209.0005" yMax="125.6610">PID101</word>
-<word xMin="213.0000" yMin="122.6580" xMax="231.0005" yMax="125.6610">PID102</word>
-<word xMin="49.6510" yMin="125.3233" xMax="63.6597" yMax="131.7946">GND</word>
-<word xMin="32.9998" yMin="121.8695" xMax="36.0015" yMax="131.8700">PIR1101</word>
-<word xMin="32.9998" yMin="128.8695" xMax="36.0015" yMax="138.8700">PIC1502</word>
-<word xMin="207.2390" yMin="133.2327" xMax="220.7704" yMax="139.7040">SS34</word>
-<word xMin="191.9999" yMin="135.0949" xMax="198.0013" yMax="143.0960">COQ3</word>
-<word xMin="356.9999" yMin="135.0949" xMax="363.0013" yMax="143.0960">COQ6</word>
-<word xMin="192.8474" yMin="137.5469" xMax="200.6309" yMax="144.0182">Q3</word>
-<word xMin="357.8710" yMin="137.5469" xMax="365.6545" yMax="144.0182">Q6</word>
-<word xMin="40.9998" yMin="137.2075" xMax="50.0010" yMax="144.2090">COC15</word>
-<word xMin="91.9998" yMin="138.2080" xMax="98.0010" yMax="145.2090">COU2</word>
-<word xMin="574.9998" yMin="138.2080" xMax="581.0010" yMax="145.2090">COU3</word>
-<word xMin="41.4958" yMin="138.9850" xMax="52.1529" yMax="145.4563">C15</word>
-<word xMin="92.8258" yMin="139.7040" xMax="100.6093" yMax="146.1754">U2</word>
-<word xMin="143.6761" yMin="139.7040" xMax="170.6174" yMax="146.1754">VBAT_IN</word>
-<word xMin="207.9586" yMin="139.7040" xMax="232.7459" yMax="146.1754">AP40P05</word>
-<word xMin="373.7017" yMin="139.7040" xMax="398.4891" yMax="146.1754">AP40P05</word>
-<word xMin="435.8255" yMin="139.7040" xMax="469.2337" yMax="146.1754">VBAT_OUT</word>
-<word xMin="575.4240" yMin="139.7040" xMax="583.2075" yMax="146.1754">U3</word>
-<word xMin="79.1212" yMin="144.4180" xMax="85.5875" yMax="147.6537">4</word>
-<word xMin="524.9998" yMin="141.2081" xMax="530.0010" yMax="148.2090">COL4</word>
-<word xMin="480.9998" yMin="142.2075" xMax="490.0010" yMax="149.2090">COR12</word>
-<word xMin="525.0534" yMin="143.2992" xMax="532.1185" yMax="149.7705">L4</word>
-<word xMin="481.8786" yMin="144.0182" xMax="492.5357" yMax="150.4896">R12</word>
-<word xMin="718.9998" yMin="144.2081" xMax="724.0010" yMax="151.2090">COD8</word>
-<word xMin="82.9997" yMin="135.0785" xMax="86.0027" yMax="152.0790">PIU204</word>
-<word xMin="41.4958" yMin="146.1754" xMax="54.9102" yMax="152.6467">10uF</word>
-<word xMin="718.8602" yMin="146.1754" xMax="726.6437" yMax="152.6467">D8</word>
-<word xMin="32.9998" yMin="142.8695" xMax="36.0015" yMax="152.8700">PIC1501</word>
-<word xMin="100.0216" yMin="146.8944" xMax="120.4985" yMax="153.3657">TP4057</word>
-<word xMin="567.2687" yMin="146.8944" xMax="570.5019" yMax="153.3657">1</word>
-<word xMin="624.5952" yMin="146.8944" xMax="627.8284" yMax="153.3657">8</word>
-<word xMin="177.0000" yMin="151.7713" xMax="195.0003" yMax="153.7740">PIQ303</word>
-<word xMin="206.0000" yMin="151.7715" xMax="223.0003" yMax="153.7740">PIQ302</word>
-<word xMin="343.0000" yMin="151.7715" xMax="360.0003" yMax="153.7740">PIQ602</word>
-<word xMin="372.0000" yMin="151.7715" xMax="389.0003" yMax="153.7740">PIQ603</word>
-<word xMin="473.0000" yMin="151.7725" xMax="483.0003" yMax="153.7740">PIR1201</word>
-<word xMin="494.0000" yMin="151.7723" xMax="505.0003" yMax="153.7740">PIR1202</word>
-<word xMin="516.0000" yMin="151.7725" xMax="526.0003" yMax="153.7740">PIL401</word>
-<word xMin="552.0000" yMin="151.7727" xMax="560.3336" yMax="153.7740">PIL40</word>
-<word xMin="559.0000" yMin="151.7736" xMax="562.0003" yMax="153.7740">P</word>
-<word xMin="560.3333" yMin="151.7725" xMax="565.0003" yMax="153.7736">2I</word>
-<word xMin="565.0000" yMin="151.7713" xMax="577.0003" yMax="153.7731">U301</word>
-<word xMin="617.0000" yMin="151.7715" xMax="634.0003" yMax="153.7740">PIU308</word>
-<word xMin="580.4610" yMin="150.4896" xMax="588.9616" yMax="156.9609">LX</word>
-<word xMin="600.3694" yMin="150.4896" xMax="613.6603" yMax="156.9609">OUT</word>
-<word xMin="566.7890" yMin="154.0847" xMax="570.0222" yMax="160.5561">2</word>
-<word xMin="624.5952" yMin="154.0847" xMax="627.8284" yMax="160.5561">7</word>
-<word xMin="306.9998" yMin="150.8695" xMax="310.0015" yMax="160.8700">PIC1602</word>
-<word xMin="392.9998" yMin="150.8695" xMax="396.0015" yMax="160.8700">PIC1702</word>
-<word xMin="421.9998" yMin="150.8695" xMax="425.0015" yMax="160.8700">PIR1302</word>
-<word xMin="559.0000" yMin="158.6580" xMax="577.0005" yMax="161.6610">PIU302</word>
-<word xMin="617.0000" yMin="158.6582" xMax="634.0005" yMax="161.6610">PIU307</word>
-<word xMin="703.0000" yMin="158.6580" xMax="721.0005" yMax="161.6610">PID801</word>
-<word xMin="725.0000" yMin="158.6582" xMax="742.0005" yMax="161.6610">PID802</word>
-<word xMin="525.0534" yMin="156.2419" xMax="538.3449" yMax="162.7132">3015</word>
-<word xMin="539.6621" yMin="156.2419" xMax="555.8266" yMax="162.7132">1.5uH</word>
-<word xMin="481.8786" yMin="156.9609" xMax="490.0358" yMax="163.4322">0Ω</word>
-<word xMin="580.4610" yMin="157.6799" xMax="588.9616" yMax="164.1512">LX</word>
-<word xMin="600.3694" yMin="157.6799" xMax="613.6603" yMax="164.1512">OUT</word>
-<word xMin="749.8022" yMin="157.6799" xMax="774.5889" yMax="164.1512">+5VOUT</word>
-<word xMin="78.9139" yMin="159.1180" xMax="92.3277" yMax="165.5893">VCC</word>
-<word xMin="314.9998" yMin="159.2075" xMax="324.0010" yMax="166.2090">COC16</word>
-<word xMin="400.9998" yMin="159.2075" xMax="410.0010" yMax="166.2090">COC17</word>
-<word xMin="426.9998" yMin="159.2076" xMax="435.0010" yMax="166.2090">COR13</word>
-<word xMin="315.4158" yMin="160.5561" xMax="326.0730" yMax="167.0274">C16</word>
-<word xMin="401.7654" yMin="160.5561" xMax="412.4226" yMax="167.0274">C17</word>
-<word xMin="120.1698" yMin="161.2751" xMax="123.4030" yMax="167.7464">3</word>
-<word xMin="426.9507" yMin="161.2751" xMax="437.6078" yMax="167.7464">R13</word>
-<word xMin="566.7890" yMin="161.2751" xMax="570.0222" yMax="167.7464">6</word>
-<word xMin="277.9998" yMin="157.8695" xMax="281.0015" yMax="167.8700">PIR1402</word>
-<word xMin="335.9998" yMin="157.8695" xMax="339.0015" yMax="167.8700">PIR1502</word>
-<word xMin="652.9998" yMin="157.8695" xMax="656.0015" yMax="167.8700">PIR1602</word>
-<word xMin="681.9998" yMin="157.8695" xMax="685.0015" yMax="167.8700">PIC1802</word>
-<word xMin="112.0000" yMin="165.6580" xMax="130.0005" yMax="168.6610">PIU203</word>
-<word xMin="559.0000" yMin="165.6580" xMax="577.0005" yMax="168.6610">PIU306</word>
-<word xMin="96.4237" yMin="164.8703" xMax="108.5176" yMax="171.3416">BAT</word>
-<word xMin="580.4610" yMin="164.8703" xMax="587.3444" yMax="171.3416">IN</word>
-<word xMin="689.9998" yMin="166.2076" xMax="698.0010" yMax="173.2090">COC18</word>
-<word xMin="281.9999" yMin="166.0944" xMax="291.0013" yMax="174.0960">COR14</word>
-<word xMin="339.9999" yMin="166.0944" xMax="349.0013" yMax="174.0960">COR15</word>
-<word xMin="656.9999" yMin="166.0944" xMax="666.0013" yMax="174.0960">COR16</word>
-<word xMin="315.4158" yMin="167.7464" xMax="328.8302" yMax="174.2177">10uF</word>
-<word xMin="401.7654" yMin="167.7464" xMax="415.1798" yMax="174.2177">10uF</word>
-<word xMin="690.0771" yMin="167.7464" xMax="700.7342" yMax="174.2177">C18</word>
-<word xMin="28.0636" yMin="168.4655" xMax="42.0722" yMax="174.9368">GND</word>
-<word xMin="48.4517" yMin="168.4655" xMax="51.6849" yMax="174.9368">1</word>
-<word xMin="283.0347" yMin="168.4655" xMax="293.6918" yMax="174.9368">R14</word>
-<word xMin="306.9998" yMin="164.8695" xMax="310.0015" yMax="174.8700">PIC1601</word>
-<word xMin="340.6011" yMin="168.4655" xMax="351.2582" yMax="174.9368">R15</word>
-<word xMin="392.9998" yMin="164.8695" xMax="396.0015" yMax="174.8700">PIC1701</word>
-<word xMin="426.9507" yMin="168.4655" xMax="444.6878" yMax="174.9368">3.3KΩ</word>
-<word xMin="515.9998" yMin="164.8695" xMax="519.0015" yMax="174.8700">PIC1902</word>
-<word xMin="657.6959" yMin="168.4655" xMax="668.3530" yMax="174.9368">R16</word>
-<word xMin="40.0000" yMin="172.6580" xMax="58.0005" yMax="175.6610">PIU201</word>
-<word xMin="718.8602" yMin="169.1845" xMax="732.3917" yMax="175.6558">SS34</word>
-<word xMin="61.6440" yMin="172.0606" xMax="79.6663" yMax="178.5320">CHRG</word>
-<word xMin="523.9998" yMin="173.2075" xMax="533.0010" yMax="180.2090">COC19</word>
-<word xMin="198.9997" yMin="164.0785" xMax="202.0027" yMax="181.0790">PIQ301</word>
-<word xMin="364.9997" yMin="164.0785" xMax="368.0027" yMax="181.0790">PIQ601</word>
-<word xMin="524.3338" yMin="174.9368" xMax="534.9910" yMax="181.4081">C19</word>
-<word xMin="690.0771" yMin="174.9368" xMax="703.4914" yMax="181.4081">22uF</word>
-<word xMin="421.9998" yMin="171.8695" xMax="425.0015" yMax="181.8700">PIR1301</word>
-<word xMin="681.9998" yMin="171.8695" xMax="685.0015" yMax="181.8700">PIC1801</word>
-<word xMin="47.9720" yMin="175.6558" xMax="51.2051" yMax="182.1271">5</word>
-<word xMin="120.1698" yMin="175.6558" xMax="123.4030" yMax="182.1271">6</word>
-<word xMin="283.0347" yMin="175.6558" xMax="302.2086" yMax="182.1271">100KΩ</word>
-<word xMin="340.6011" yMin="175.6558" xMax="359.7750" yMax="182.1271">100KΩ</word>
-<word xMin="567.0289" yMin="175.6558" xMax="570.2621" yMax="182.1271">3</word>
-<word xMin="657.6959" yMin="175.6558" xMax="678.5459" yMax="182.1271">52.3KΩ</word>
-<word xMin="40.0000" yMin="179.6580" xMax="58.0005" yMax="182.6610">PIU205</word>
-<word xMin="112.0000" yMin="179.6580" xMax="130.0005" yMax="182.6610">PIU206</word>
-<word xMin="559.0000" yMin="179.6580" xMax="577.0005" yMax="182.6610">PIU303</word>
-<word xMin="61.6440" yMin="179.2510" xMax="82.8374" yMax="185.7223">STDBY</word>
-<word xMin="92.1062" yMin="179.2510" xMax="109.4683" yMax="185.7223">PROG</word>
-<word xMin="580.4610" yMin="179.2510" xMax="588.9616" yMax="185.7223">EN</word>
-<word xMin="524.3338" yMin="182.1271" xMax="537.7482" yMax="188.5985">22uF</word>
-<word xMin="277.9998" yMin="178.8695" xMax="281.0015" yMax="188.8700">PIR1401</word>
-<word xMin="335.9998" yMin="178.8695" xMax="339.0015" yMax="188.8700">PIR1501</word>
-<word xMin="515.9998" yMin="178.8695" xMax="519.0015" yMax="188.8700">PIC1901</word>
-<word xMin="652.9998" yMin="178.8695" xMax="656.0015" yMax="188.8700">PIR1601</word>
-<word xMin="624.5952" yMin="182.8462" xMax="627.8284" yMax="189.3175">5</word>
-<word xMin="617.0000" yMin="187.7715" xMax="634.0003" yMax="189.7740">PIU305</word>
-<word xMin="606.1260" yMin="186.4414" xMax="614.0317" yMax="192.9127">FB</word>
-<word xMin="78.6741" yMin="188.5984" xMax="92.6827" yMax="195.0697">GND</word>
-<word xMin="421.9997" yMin="177.9655" xMax="425.0028" yMax="195.9660">PID20A</word>
-<word xMin="301.9837" yMin="190.0365" xMax="315.9923" yMax="196.5078">GND</word>
-<word xMin="388.3332" yMin="190.0365" xMax="402.3419" yMax="196.5078">GND</word>
-<word xMin="566.7890" yMin="190.0365" xMax="570.0222" yMax="196.5078">4</word>
-<word xMin="133.9998" yMin="186.8695" xMax="137.0015" yMax="196.8700">PIR1701</word>
-<word xMin="154.9998" yMin="186.8695" xMax="158.0015" yMax="196.8700">PIC2102</word>
-<word xMin="652.9998" yMin="186.8695" xMax="656.0015" yMax="196.8700">PIR1802</word>
-<word xMin="559.0000" yMin="194.6580" xMax="577.0005" yMax="197.6610">PIU304</word>
-<word xMin="580.4610" yMin="193.6316" xMax="594.4697" yMax="200.1030">GND</word>
-<word xMin="137.9998" yMin="195.2075" xMax="147.0010" yMax="202.2090">COR17</word>
-<word xMin="163.9998" yMin="195.2076" xMax="172.0010" yMax="202.2090">COC21</word>
-<word xMin="439.9998" yMin="195.2081" xMax="445.0010" yMax="202.2090">COD2</word>
-<word xMin="656.9998" yMin="195.2075" xMax="666.0010" yMax="202.2090">COR18</word>
-<word xMin="164.0642" yMin="196.5078" xMax="174.7213" yMax="202.9791">C21</word>
-<word xMin="440.1429" yMin="196.5078" xMax="447.9265" yMax="202.9791">D2</word>
-<word xMin="138.8789" yMin="197.2268" xMax="149.5360" yMax="203.6981">R17</word>
-<word xMin="566.7890" yMin="197.2268" xMax="570.0222" yMax="203.6981">9</word>
-<word xMin="657.6959" yMin="197.2268" xMax="668.3530" yMax="203.6981">R18</word>
-<word xMin="676.6449" yMin="197.2268" xMax="690.6535" yMax="203.6981">GND</word>
-<word xMin="198.9998" yMin="193.8695" xMax="202.0015" yMax="203.8700">PIR1902</word>
-<word xMin="559.0000" yMin="201.6580" xMax="577.0005" yMax="204.6610">PIU309</word>
-<word xMin="79.1212" yMin="201.9408" xMax="85.5875" yMax="205.1765">2</word>
-<word xMin="580.4610" yMin="200.8220" xMax="598.0624" yMax="207.2933">PGND</word>
-<word xMin="321.9998" yMin="202.2080" xMax="328.0010" yMax="209.2090">COD3</word>
-<word xMin="82.9997" yMin="193.0785" xMax="86.0027" yMax="210.0790">PIU202</word>
-<word xMin="202.9999" yMin="202.0944" xMax="212.0013" yMax="210.0960">COR19</word>
-<word xMin="164.0642" yMin="203.6981" xMax="177.4786" yMax="210.1695">10uF</word>
-<word xMin="322.6116" yMin="203.6981" xMax="330.3951" yMax="210.1695">D3</word>
-<word xMin="138.8789" yMin="200.8695" xMax="158.0015" yMax="210.8885">10KΩPIC2101</word>
-<word xMin="203.6411" yMin="204.4172" xMax="214.2983" yMax="210.8885">R19</word>
-<word xMin="510.9016" yMin="204.4172" xMax="524.9103" yMax="210.8885">GND</word>
-<word xMin="657.6959" yMin="204.4172" xMax="673.7563" yMax="210.8885">15KΩ</word>
-<word xMin="421.9997" yMin="200.0785" xMax="425.0027" yMax="217.0790">PID20K</word>
-<word xMin="133.9998" yMin="207.8695" xMax="137.0015" yMax="217.8700">PIR1702</word>
-<word xMin="652.9998" yMin="207.8695" xMax="656.0015" yMax="217.8700">PIR1801</word>
-<word xMin="203.6411" yMin="211.6075" xMax="222.8150" yMax="218.0789">100KΩ</word>
-<word xMin="265.7648" yMin="211.6075" xMax="276.4213" yMax="218.0789">INT</word>
-<word xMin="575.4240" yMin="211.6075" xMax="596.6193" yMax="218.0789">SY7088</word>
-<word xMin="307.0000" yMin="215.6582" xMax="324.0005" yMax="218.6610">PID302</word>
-<word xMin="329.0000" yMin="215.6582" xMax="346.0005" yMax="218.6610">PID301</word>
-<word xMin="198.9998" yMin="214.8695" xMax="202.0015" yMax="224.8700">PIR1901</word>
-<word xMin="11.5133" yMin="225.9882" xMax="15.8264" yMax="232.4596">B</word>
-<word xMin="554.0765" yMin="225.9882" xMax="568.0851" yMax="232.4596">GND</word>
-<word xMin="825.8377" yMin="225.9882" xMax="830.1508" yMax="232.4596">B</word>
-<word xMin="322.6116" yMin="226.7073" xMax="350.0327" yMax="233.1786">B5819WT</word>
-<word xMin="78.6741" yMin="233.1786" xMax="92.6827" yMax="239.6499">GND</word>
-<word xMin="129.0447" yMin="233.1786" xMax="143.0533" yMax="239.6499">GND</word>
-<word xMin="150.6320" yMin="233.1786" xMax="164.6407" yMax="239.6499">GND</word>
-<word xMin="417.3563" yMin="233.1786" xMax="431.3650" yMax="239.6499">GND</word>
-<word xMin="575.4240" yMin="233.1786" xMax="635.5343" yMax="239.6499">Vout=1.2V*(R1/R2+1)</word>
-<word xMin="647.8617" yMin="233.1786" xMax="661.8703" yMax="239.6499">GND</word>
-<word xMin="321.9998" yMin="238.2080" xMax="328.0010" yMax="245.2090">COD4</word>
-<word xMin="243.2179" yMin="239.6499" xMax="250.1046" yMax="246.1212">S1</word>
-<word xMin="322.6116" yMin="239.6499" xMax="330.3951" yMax="246.1212">D4</word>
-<word xMin="193.8068" yMin="240.3690" xMax="207.8155" yMax="246.8403">GND</word>
-<word xMin="293.9998" yMin="246.2075" xMax="303.0010" yMax="253.2090">NLBTN</word>
-<word xMin="294.5480" yMin="247.7989" xMax="324.0003" yMax="254.7740">BTNPID402</word>
-<word xMin="329.0000" yMin="252.7715" xMax="346.0003" yMax="254.7740">PID401</word>
-<word xMin="243.2179" yMin="257.1464" xMax="262.6195" yMax="263.6177">SW-PB</word>
-<word xMin="62.9998" yMin="260.2080" xMax="69.0010" yMax="267.2090">COU5</word>
-<word xMin="63.8028" yMin="262.1797" xMax="71.5863" yMax="268.6510">U5</word>
-<word xMin="172.4593" yMin="262.1797" xMax="199.4006" yMax="268.6510">VBAT_IN</word>
-<word xMin="257.3697" yMin="262.1797" xMax="273.7735" yMax="268.6510">+3.3V</word>
-<word xMin="322.6116" yMin="262.8987" xMax="350.0327" yMax="269.3700">B5819WT</word>
-<word xMin="26.9999" yMin="267.0939" xMax="39.0013" yMax="275.0960">NLOSCI</word>
-<word xMin="581.9999" yMin="267.0949" xMax="588.0013" yMax="275.0960">COU4</word>
-<word xMin="27.8238" yMin="269.3700" xMax="42.6737" yMax="275.8413">OSCI</word>
-<word xMin="55.6475" yMin="269.3700" xMax="58.8807" yMax="275.8413">1</word>
-<word xMin="127.3656" yMin="269.3700" xMax="130.5988" yMax="275.8413">8</word>
-<word xMin="222.5900" yMin="269.3700" xMax="236.5986" yMax="275.8413">GND</word>
-<word xMin="582.6198" yMin="269.3700" xMax="590.4033" yMax="275.8413">U4</word>
-<word xMin="47.0000" yMin="273.6580" xMax="65.0005" yMax="276.6610">PIU501</word>
-<word xMin="119.0000" yMin="273.6580" xMax="137.0005" yMax="276.6610">PIU508</word>
-<word xMin="68.8398" yMin="272.9652" xMax="83.6897" yMax="279.4365">OSCI</word>
-<word xMin="102.6600" yMin="272.9652" xMax="116.6687" yMax="279.4365">VDD</word>
-<word xMin="243.9376" yMin="273.6842" xMax="254.5947" yMax="280.1556">R20</word>
-<word xMin="26.9998" yMin="275.2069" xMax="39.0010" yMax="282.2090">NLOSCO</word>
-<word xMin="183.9998" yMin="272.8695" xMax="187.0015" yMax="282.8700">PIC2602</word>
-<word xMin="27.8238" yMin="276.5604" xMax="44.9460" yMax="283.0317">OSCO</word>
-<word xMin="55.1678" yMin="276.5604" xMax="58.4010" yMax="283.0317">2</word>
-<word xMin="127.3656" yMin="276.5604" xMax="130.5988" yMax="283.0317">7</word>
-<word xMin="574.4645" yMin="276.5604" xMax="577.6977" yMax="283.0317">1</word>
-<word xMin="631.7911" yMin="276.5604" xMax="635.0242" yMax="283.0317">5</word>
-<word xMin="47.0000" yMin="280.6580" xMax="65.0005" yMax="283.6610">PIU502</word>
-<word xMin="119.0000" yMin="280.6580" xMax="137.0005" yMax="283.6610">PIU507</word>
-<word xMin="566.0000" yMin="280.6580" xMax="584.0005" yMax="283.6610">PIU401</word>
-<word xMin="624.0000" yMin="280.6580" xMax="642.0005" yMax="283.6610">PIU405</word>
-<word xMin="68.8398" yMin="280.1556" xMax="85.9620" yMax="286.6269">OSCO</word>
-<word xMin="90.1873" yMin="280.1556" xMax="116.4109" yMax="286.6269">CLKOUT</word>
-<word xMin="587.6568" yMin="280.1556" xMax="599.0311" yMax="286.6269">VIN</word>
-<word xMin="603.0078" yMin="280.1556" xMax="620.8491" yMax="286.6269">VOUT</word>
-<word xMin="749.8022" yMin="280.1556" xMax="766.2059" yMax="286.6269">+3.3V</word>
-<word xMin="191.9998" yMin="281.2075" xMax="201.0010" yMax="288.2090">COC26</word>
-<word xMin="26.9998" yMin="282.2075" xMax="36.0010" yMax="289.2090">NLINT</word>
-<word xMin="141.9998" yMin="282.2059" xMax="160.0010" yMax="289.2090">NLIN0SCL</word>
-<word xMin="192.8474" yMin="283.0317" xMax="203.5045" yMax="289.5030">C26</word>
-<word xMin="702.9998" yMin="279.8695" xMax="706.0015" yMax="289.8700">PIC3002</word>
-<word xMin="731.9998" yMin="279.8695" xMax="735.0015" yMax="289.8700">PIC3102</word>
-<word xMin="27.8238" yMin="283.7507" xMax="38.4803" yMax="290.2221">INT</word>
-<word xMin="55.4076" yMin="283.7507" xMax="58.6408" yMax="290.2221">3</word>
-<word xMin="127.3656" yMin="283.7507" xMax="130.5988" yMax="290.2221">6</word>
-<word xMin="143.1963" yMin="283.7507" xMax="165.2711" yMax="290.2221">IN_SCL</word>
-<word xMin="573.9848" yMin="283.7507" xMax="577.2180" yMax="290.2221">2</word>
-<word xMin="47.0000" yMin="288.7713" xMax="65.0003" yMax="290.7740">PIU503</word>
-<word xMin="119.0000" yMin="288.7713" xMax="137.0003" yMax="290.7740">PIU506</word>
-<word xMin="566.0000" yMin="288.7713" xMax="584.0003" yMax="290.7740">PIU402</word>
-<word xMin="243.9376" yMin="286.6269" xMax="259.9980" yMax="293.0982">10KΩ</word>
-<word xMin="68.8398" yMin="287.3459" xMax="79.4963" yMax="293.8172">INT</word>
-<word xMin="104.5789" yMin="287.3459" xMax="116.3554" yMax="293.8172">SCL</word>
-<word xMin="587.6568" yMin="287.3459" xMax="601.6655" yMax="293.8172">GND</word>
-<word xMin="710.9999" yMin="288.0944" xMax="720.0013" yMax="296.0960">COC30</word>
-<word xMin="739.9999" yMin="288.0944" xMax="749.0013" yMax="296.0960">COC31</word>
-<word xMin="141.9998" yMin="289.2059" xMax="160.0010" yMax="296.2090">NLIN0SDA</word>
-<word xMin="192.8474" yMin="290.2221" xMax="209.3753" yMax="296.6934">100nF</word>
-<word xMin="711.6644" yMin="290.2221" xMax="722.3215" yMax="296.6934">C30</word>
-<word xMin="740.4476" yMin="290.2221" xMax="751.1048" yMax="296.6934">C31</word>
-<word xMin="364.9997" yMin="278.9655" xMax="368.0028" yMax="296.9660">PIQ4081652</word>
-<word xMin="55.1678" yMin="290.9411" xMax="58.4010" yMax="297.4124">4</word>
-<word xMin="127.3656" yMin="290.9411" xMax="130.5988" yMax="297.4124">5</word>
-<word xMin="143.1963" yMin="290.9411" xMax="166.0664" yMax="297.4124">IN_SDA</word>
-<word xMin="574.2247" yMin="290.9411" xMax="577.4578" yMax="297.4124">3</word>
-<word xMin="631.7911" yMin="290.9411" xMax="635.0242" yMax="297.4124">4</word>
-<word xMin="183.9998" yMin="287.8695" xMax="187.0015" yMax="297.8700">PIC2601</word>
-<word xMin="493.9998" yMin="287.8695" xMax="497.0015" yMax="297.8700">PIC3202</word>
-<word xMin="522.9998" yMin="287.8695" xMax="526.0015" yMax="297.8700">PIC3302</word>
-<word xMin="47.0000" yMin="295.6580" xMax="65.0005" yMax="298.6610">PIU504</word>
-<word xMin="119.0000" yMin="295.6580" xMax="137.0005" yMax="298.6610">PIU505</word>
-<word xMin="566.0000" yMin="295.6580" xMax="584.0005" yMax="298.6610">PIU403</word>
-<word xMin="624.0000" yMin="295.6580" xMax="642.0005" yMax="298.6610">PIU404</word>
-<word xMin="68.8398" yMin="294.5363" xMax="80.8174" yMax="301.0076">VSS</word>
-<word xMin="103.6195" yMin="294.5363" xMax="116.4312" yMax="301.0076">SDA</word>
-<word xMin="587.6568" yMin="294.5363" xMax="596.1575" yMax="301.0076">EN</word>
-<word xMin="612.1225" yMin="294.5363" xMax="621.2252" yMax="301.0076">NC</word>
-<word xMin="374.9998" yMin="295.2080" xMax="381.0010" yMax="302.2090">COQ4</word>
-<word xMin="249.9998" yMin="296.2075" xMax="259.0010" yMax="303.2090">COD10</word>
-<word xMin="315.9998" yMin="296.2071" xMax="327.0010" yMax="303.2090">NLHOLD</word>
-<word xMin="375.8605" yMin="296.6934" xMax="383.6440" yMax="303.1647">Q4</word>
-<word xMin="501.9998" yMin="296.2075" xMax="511.0010" yMax="303.2090">COC32</word>
-<word xMin="530.9998" yMin="296.2075" xMax="540.0010" yMax="303.2090">COC33</word>
-<word xMin="250.4138" yMin="297.4124" xMax="261.5501" yMax="303.8837">D10</word>
-<word xMin="502.7464" yMin="297.4124" xMax="513.4036" yMax="303.8837">C32</word>
-<word xMin="531.5296" yMin="297.4124" xMax="542.1867" yMax="303.8837">C33</word>
-<word xMin="711.6644" yMin="297.4124" xMax="725.0788" yMax="303.8837">22uF</word>
-<word xMin="740.4476" yMin="297.4124" xMax="756.9756" yMax="303.8837">100nF</word>
-<word xMin="316.1354" yMin="298.1315" xMax="333.9760" yMax="304.6028">HOLD</word>
-<word xMin="702.9998" yMin="294.8695" xMax="706.0015" yMax="304.8700">PIC3001</word>
-<word xMin="731.9998" yMin="294.8695" xMax="735.0015" yMax="304.8700">PIC3101</word>
-<word xMin="336.0000" yMin="302.6582" xMax="353.0005" yMax="305.6610">PIQ403</word>
-<word xMin="375.8605" yMin="303.8837" xMax="418.8474" yMax="310.3551">LN2324DT2AG</word>
-<word xMin="214.9999" yMin="303.0941" xMax="226.0013" yMax="311.0960">NLWAKE</word>
-<word xMin="502.7464" yMin="304.6028" xMax="519.2743" yMax="311.0741">100nF</word>
-<word xMin="531.5296" yMin="304.6028" xMax="544.9440" yMax="311.0741">22uF</word>
-<word xMin="63.8028" yMin="305.3218" xMax="88.8300" yMax="311.7931">RTC8563</word>
-<word xMin="215.1543" yMin="305.3218" xMax="233.7146" yMax="311.7931">WAKE</word>
-<word xMin="582.6198" yMin="305.3218" xMax="630.3988" yMax="311.7931">BL8075CB5TR33</word>
-<word xMin="493.9998" yMin="301.8695" xMax="497.0015" yMax="311.8700">PIC3201</word>
-<word xMin="522.9998" yMin="301.8695" xMax="526.0015" yMax="311.8700">PIC3301</word>
-<word xMin="235.0000" yMin="309.6582" xMax="252.0005" yMax="312.6610">PID1001</word>
-<word xMin="256.0000" yMin="309.6580" xMax="274.0005" yMax="312.6610">PID1002</word>
-<word xMin="42.4552" yMin="312.5122" xMax="56.4638" yMax="318.9835">GND</word>
-<word xMin="179.4152" yMin="312.5122" xMax="193.4239" yMax="318.9835">GND</word>
-<word xMin="364.9997" yMin="308.0785" xMax="368.0027" yMax="325.0790">PIQ4074</word>
-<word xMin="320.9998" yMin="315.8695" xMax="324.0015" yMax="325.8700">PIR2302</word>
-<word xMin="698.2323" yMin="319.7025" xMax="712.2409" yMax="326.1738">GND</word>
-<word xMin="727.0154" yMin="319.7025" xMax="741.0241" yMax="326.1738">GND</word>
-<word xMin="250.4138" yMin="320.4216" xMax="277.8349" yMax="326.8929">B5819WT</word>
-<word xMin="325.9998" yMin="325.2076" xMax="334.0010" yMax="332.2090">COR23</word>
-<word xMin="54.9998" yMin="326.2075" xMax="64.0010" yMax="333.2090">COC28</word>
-<word xMin="326.2095" yMin="326.8929" xMax="336.8667" yMax="333.3642">R23</word>
-<word xMin="55.8874" yMin="327.6119" xMax="66.5445" yMax="334.0832">C28</word>
-<word xMin="107.2174" yMin="334.0832" xMax="122.0673" yMax="340.5546">OSCI</word>
-<word xMin="178.2159" yMin="334.0832" xMax="194.6197" yMax="340.5546">+3.3V</word>
-<word xMin="326.2095" yMin="334.0832" xMax="345.3835" yMax="340.5546">100KΩ</word>
-<word xMin="489.3142" yMin="334.0832" xMax="503.3229" yMax="340.5546">GND</word>
-<word xMin="518.0975" yMin="334.0832" xMax="532.1061" yMax="340.5546">GND</word>
-<word xMin="554.0765" yMin="334.0832" xMax="568.0851" yMax="340.5546">GND</word>
-<word xMin="47.0000" yMin="338.6592" xMax="58.0005" yMax="341.6610">PIC2801</word>
-<word xMin="62.0000" yMin="338.6593" xMax="72.0005" yMax="341.6610">PIC2802</word>
-<word xMin="19.6685" yMin="337.6783" xMax="33.6772" yMax="344.1497">GND</word>
-<word xMin="320.9998" yMin="337.8695" xMax="324.0015" yMax="347.8700">PIR2301</word>
-<word xMin="79.1212" yMin="345.9875" xMax="85.5875" yMax="349.2232">2</word>
-<word xMin="82.9997" yMin="337.0785" xMax="86.0027" yMax="354.0790">PIY202</word>
-<word xMin="55.8874" yMin="347.7448" xMax="70.9785" yMax="354.2162">6.0pF</word>
-<word xMin="451.9998" yMin="347.2080" xMax="458.0010" yMax="354.2090">COJ5</word>
-<word xMin="453.0954" yMin="348.4639" xMax="458.7237" yMax="354.9352">J5</word>
-<word xMin="90.9998" yMin="353.2081" xMax="96.0010" yMax="360.2090">COY2</word>
-<word xMin="633.9172" yMin="357.2525" xMax="640.3836" yMax="360.4881">0</word>
-<word xMin="183.9997" yMin="344.0785" xMax="187.0027" yMax="361.0790">PID501</word>
-<word xMin="91.3866" yMin="354.9352" xMax="99.1701" yMax="361.4065">Y2</word>
-<word xMin="395.2892" yMin="355.6542" xMax="413.8494" yMax="362.1256">WAKE</word>
-<word xMin="424.0723" yMin="355.6542" xMax="436.8840" yMax="362.1256">BTN</word>
-<word xMin="444.7003" yMin="355.6542" xMax="447.9335" yMax="362.1256">1</word>
-<word xMin="502.0268" yMin="355.6542" xMax="505.2600" yMax="362.1256">2</word>
-<word xMin="437.0000" yMin="360.7715" xMax="454.0003" yMax="362.7740">PIJ501</word>
-<word xMin="494.0000" yMin="360.7713" xMax="512.0003" yMax="362.7740">PIJ502</word>
-<word xMin="633.9172" yMin="360.3682" xMax="640.3836" yMax="363.6039">1</word>
-<word xMin="458.1324" yMin="359.2494" xMax="464.4791" yMax="365.7207">b1</word>
-<word xMin="484.9967" yMin="359.2494" xMax="491.3434" yMax="365.7207">b2</word>
-<word xMin="526.4925" yMin="359.2494" xMax="540.5012" yMax="365.7207">GND</word>
-<word xMin="193.9998" yMin="360.2080" xMax="200.0010" yMax="367.2090">COD5</word>
-<word xMin="669.9998" yMin="361.2069" xMax="682.0010" yMax="368.2090">COFPC1</word>
-<word xMin="91.3866" yMin="362.1256" xMax="122.2776" yMax="368.5969">32.768KHz</word>
-<word xMin="123.4777" yMin="362.1256" xMax="145.5124" yMax="368.5969">±20ppm</word>
-<word xMin="146.7086" yMin="362.1256" xMax="164.9126" yMax="368.5969">12.5pF</word>
-<word xMin="194.2866" yMin="362.1256" xMax="202.0701" yMax="368.5969">D5</word>
-<word xMin="638.9997" yMin="350.9655" xMax="642.0028" yMax="368.9660">PIFPC1010</word>
-<word xMin="54.9998" yMin="362.2075" xMax="64.0010" yMax="369.2090">COC29</word>
-<word xMin="11.2734" yMin="362.8446" xMax="15.5864" yMax="369.3159">C</word>
-<word xMin="316.3752" yMin="362.8446" xMax="330.3839" yMax="369.3159">GND</word>
-<word xMin="359.5501" yMin="362.8446" xMax="373.5587" yMax="369.3159">GND</word>
-<word xMin="670.6483" yMin="362.8446" xMax="685.4685" yMax="369.3159">FPC1</word>
-<word xMin="825.5979" yMin="362.8446" xMax="829.9109" yMax="369.3159">C</word>
-<word xMin="414.9998" yMin="359.8695" xMax="418.0015" yMax="369.8700">PIR102</word>
-<word xMin="55.8874" yMin="363.5636" xMax="66.5445" yMax="370.0350">C29</word>
-<word xMin="79.1212" yMin="367.0793" xMax="85.5875" yMax="370.3149">1</word>
-<word xMin="418.9998" yMin="368.2080" xMax="425.0010" yMax="375.2090">COR1</word>
-<word xMin="194.2866" yMin="369.3159" xMax="246.2590" yMax="375.7872">PESDNC2FD3V3B</word>
-<word xMin="82.9997" yMin="359.0785" xMax="86.0027" yMax="376.0790">PIY201</word>
-<word xMin="107.2174" yMin="370.0350" xMax="124.3396" yMax="376.5063">OSCO</word>
-<word xMin="127.8454" yMin="370.0350" xMax="144.2491" yMax="376.5063">+3.3V</word>
-<word xMin="419.7549" yMin="370.0350" xMax="427.3600" yMax="376.5063">R1</word>
-<word xMin="582.6198" yMin="370.0350" xMax="606.8110" yMax="376.5063">LCD_CS</word>
-<word xMin="617.6393" yMin="370.0350" xMax="620.8725" yMax="376.5063">1</word>
-<word xMin="670.6483" yMin="370.0350" xMax="701.5457" yMax="376.5063">FPC-0.5-8P</word>
-<word xMin="772.1091" yMin="370.0350" xMax="796.8959" yMax="376.5063">+5VOUT</word>
-<word xMin="385.9998" yMin="366.8695" xMax="389.0015" yMax="376.8700">PIC102</word>
-<word xMin="637.5151" yMin="374.2696" xMax="643.9815" yMax="377.5053">0</word>
-<word xMin="47.0000" yMin="374.6592" xMax="58.0005" yMax="377.6610">PIC2901</word>
-<word xMin="62.0000" yMin="374.6593" xMax="72.0005" yMax="377.6610">PIC2902</word>
-<word xMin="610.0000" yMin="374.6582" xMax="627.0005" yMax="377.6610">PIFPC101</word>
-<word xMin="19.6685" yMin="373.6301" xMax="33.6772" yMax="380.1015">GND</word>
-<word xMin="631.0715" yMin="373.6301" xMax="634.3047" yMax="380.1015">1</word>
-<word xMin="637.5151" yMin="377.3854" xMax="643.9815" yMax="380.6211">1</word>
-<word xMin="393.9998" yMin="375.2080" xMax="400.0010" yMax="382.2090">COC1</word>
-<word xMin="457.8926" yMin="375.7872" xMax="462.5613" yMax="382.2586">A</word>
-<word xMin="467.2471" yMin="375.7872" xMax="482.0964" yMax="382.2586">COM</word>
-<word xMin="487.1555" yMin="375.7872" xMax="491.4686" yMax="382.2586">B</word>
-<word xMin="394.5696" yMin="376.5063" xMax="402.1746" yMax="382.9776">C1</word>
-<word xMin="419.7549" yMin="377.2253" xMax="435.8153" yMax="383.6966">10KΩ</word>
-<word xMin="660.5742" yMin="377.2253" xMax="663.8074" yMax="383.6966">2</word>
-<word xMin="653.0000" yMin="381.6582" xMax="670.0005" yMax="384.6610">PIFPC102</word>
-<word xMin="646.6624" yMin="380.8205" xMax="649.8956" yMax="387.2918">2</word>
-<word xMin="699.4316" yMin="380.8205" xMax="715.8354" yMax="387.2918">+3.3V</word>
-<word xMin="183.9997" yMin="373.0785" xMax="187.0027" yMax="390.0790">PID502</word>
-<word xMin="55.8874" yMin="383.6966" xMax="70.9785" yMax="390.1680">6.0pF</word>
-<word xMin="278.9998" yMin="383.2080" xMax="285.0010" yMax="390.2090">COM1</word>
-<word xMin="394.5696" yMin="383.6966" xMax="411.0975" yMax="390.1680">100nF</word>
-<word xMin="133.9998" yMin="380.8695" xMax="137.0015" yMax="390.8700">PIR2402</word>
-<word xMin="280.1564" yMin="384.4157" xMax="289.1976" yMax="390.8870">M1</word>
-<word xMin="385.9998" yMin="380.8695" xMax="389.0015" yMax="390.8700">PIC101</word>
-<word xMin="414.9998" yMin="380.8695" xMax="418.0015" yMax="390.8700">PIR101</word>
-<word xMin="582.6198" yMin="384.4157" xMax="611.5598" yMax="390.8870">LCD_SCK</word>
-<word xMin="617.3995" yMin="384.4157" xMax="620.6327" yMax="390.8870">3</word>
-<word xMin="782.9998" yMin="380.8695" xMax="786.0015" yMax="390.8700">PIC502</word>
-<word xMin="610.0000" yMin="388.6582" xMax="627.0005" yMax="391.6610">PIFPC103</word>
-<word xMin="453.7824" yMin="388.8900" xMax="460.2487" yMax="392.1256">3</word>
-<word xMin="482.5657" yMin="389.1297" xMax="489.0320" yMax="392.3653">5</word>
-<word xMin="468.1741" yMin="389.3694" xMax="474.6404" yMax="392.6050">4</word>
-<word xMin="631.0715" yMin="388.0109" xMax="634.3047" yMax="394.4822">3</word>
-<word xMin="790.9998" yMin="389.2080" xMax="797.0010" yMax="396.2090">COC5</word>
-<word xMin="457.9997" yMin="380.0785" xMax="461.0027" yMax="397.0790">PIJ503</word>
-<word xMin="472.9997" yMin="380.0785" xMax="476.0027" yMax="397.0790">PIJ504</word>
-<word xMin="486.9997" yMin="380.0785" xMax="490.0027" yMax="397.0790">PIJ505</word>
-<word xMin="137.9998" yMin="390.2075" xMax="147.0010" yMax="397.2090">COR24</word>
-<word xMin="228.9998" yMin="390.2080" xMax="235.0010" yMax="397.2090">NLGI</word>
-<word xMin="791.0580" yMin="390.8870" xMax="798.6631" yMax="397.3583">C5</word>
-<word xMin="138.8789" yMin="391.6060" xMax="149.5360" yMax="398.0774">R24</word>
-<word xMin="229.5459" yMin="391.6060" xMax="236.2496" yMax="398.0774">GI</word>
-<word xMin="271.7613" yMin="391.6060" xMax="274.9944" yMax="398.0774">1</word>
-<word xMin="660.5742" yMin="391.6060" xMax="663.8074" yMax="398.0774">4</word>
-<word xMin="669.2092" yMin="391.6060" xMax="701.7801" yMax="398.0774">LCD_MOSI</word>
-<word xMin="264.0000" yMin="396.7715" xMax="281.0003" yMax="398.7740">PIM101</word>
-<word xMin="653.0000" yMin="396.7715" xMax="670.0003" yMax="398.7740">PIFPC104</word>
-<word xMin="285.1935" yMin="395.2012" xMax="292.9770" yMax="401.6725">G1</word>
-<word xMin="646.6624" yMin="395.2012" xMax="649.8956" yMax="401.6725">4</word>
-<word xMin="228.9998" yMin="397.2080" xMax="235.0010" yMax="404.2090">NLGO</word>
-<word xMin="791.0580" yMin="398.0774" xMax="807.5860" yMax="404.5487">100nF</word>
-<word xMin="138.8789" yMin="398.7964" xMax="150.1497" yMax="405.2677">10Ω</word>
-<word xMin="229.5459" yMin="398.7964" xMax="238.7650" yMax="405.2677">GO</word>
-<word xMin="271.2816" yMin="398.7964" xMax="274.5148" yMax="405.2677">2</word>
-<word xMin="408.7213" yMin="398.7964" xMax="425.1251" yMax="405.2677">+3.3V</word>
-<word xMin="582.6198" yMin="398.7964" xMax="606.8110" yMax="405.2677">LCD_RS</word>
-<word xMin="617.3995" yMin="398.7964" xMax="620.6327" yMax="405.2677">5</word>
-<word xMin="782.9998" yMin="395.8695" xMax="786.0015" yMax="405.8700">PIC501</word>
-<word xMin="264.0000" yMin="403.6582" xMax="281.0005" yMax="406.6610">PIM102</word>
-<word xMin="453.0954" yMin="400.2345" xMax="471.0155" yMax="406.7058">Rotary</word>
-<word xMin="472.2551" yMin="400.2345" xMax="490.9331" yMax="406.7058">encode</word>
-<word xMin="610.0000" yMin="403.6582" xMax="627.0005" yMax="406.6610">PIFPC105</word>
-<word xMin="292.3893" yMin="402.3916" xMax="300.1728" yMax="408.8629">G2</word>
-<word xMin="631.0715" yMin="402.3916" xMax="634.3047" yMax="408.8629">5</word>
-<word xMin="179.4152" yMin="405.9867" xMax="193.4239" yMax="412.4581">GND</word>
-<word xMin="229.5459" yMin="405.9867" xMax="241.6405" yMax="412.4581">beep</word>
-<word xMin="271.5214" yMin="405.9867" xMax="274.7546" yMax="412.4581">3</word>
-<word xMin="381.1374" yMin="405.9867" xMax="395.1460" yMax="412.4581">GND</word>
-<word xMin="660.5742" yMin="405.9867" xMax="663.8074" yMax="412.4581">6</word>
-<word xMin="669.2092" yMin="405.9867" xMax="705.2519" yMax="412.4581">LCD_RESET</word>
-<word xMin="133.9998" yMin="402.8695" xMax="137.0015" yMax="412.8700">PIR2401</word>
-<word xMin="264.0000" yMin="410.6582" xMax="281.0005" yMax="413.6610">PIM103</word>
-<word xMin="653.0000" yMin="410.6582" xMax="670.0005" yMax="413.6610">PIFPC106</word>
-<word xMin="285.1935" yMin="409.5819" xMax="292.9770" yMax="416.0532">G3</word>
-<word xMin="646.6624" yMin="409.5819" xMax="649.8956" yMax="416.0532">6</word>
-<word xMin="453.7824" yMin="412.1403" xMax="460.2487" yMax="416.8125">A</word>
-<word xMin="482.5657" yMin="412.4962" xMax="489.0320" yMax="416.8125">B</word>
-<word xMin="228.9998" yMin="412.2061" xMax="246.0010" yMax="419.2090">NLLCD0RS</word>
-<word xMin="229.5459" yMin="413.1771" xMax="253.7371" yMax="419.6484">LCD_RS</word>
-<word xMin="271.2816" yMin="413.1771" xMax="274.5148" yMax="419.6484">4</word>
-<word xMin="467.7269" yMin="413.1771" xMax="481.7355" yMax="419.6484">GND</word>
-<word xMin="617.1596" yMin="413.1771" xMax="620.3927" yMax="419.6484">7</word>
-<word xMin="453.7824" yMin="416.9324" xMax="460.2487" yMax="420.1680">_</word>
-<word xMin="482.5657" yMin="416.9324" xMax="489.0320" yMax="420.1680">_</word>
-<word xMin="264.0000" yMin="417.6582" xMax="281.0005" yMax="420.6610">PIM104</word>
-<word xMin="610.0000" yMin="417.6582" xMax="627.0005" yMax="420.6610">PIFPC107</word>
-<word xMin="292.3893" yMin="417.0119" xMax="300.1728" yMax="423.4832">G4</word>
-<word xMin="560.3128" yMin="417.0119" xMax="574.3215" yMax="423.4832">GND</word>
-<word xMin="631.0715" yMin="417.0119" xMax="634.3047" yMax="423.4832">7</word>
-<word xMin="453.7824" yMin="420.2893" xMax="460.2487" yMax="424.9616">N</word>
-<word xMin="482.5657" yMin="420.2893" xMax="489.0320" yMax="424.9616">N</word>
-<word xMin="228.9998" yMin="419.2051" xMax="252.0010" yMax="426.2090">NLLCD0MOSI</word>
-<word xMin="668.9998" yMin="419.2040" xMax="698.0010" yMax="426.2090">NLFPC0LCD0BL</word>
-<word xMin="453.7824" yMin="424.7241" xMax="460.2487" yMax="426.8790">I</word>
-<word xMin="482.5657" yMin="424.7241" xMax="489.0320" yMax="426.8790">I</word>
-<word xMin="229.5459" yMin="420.6071" xMax="262.1168" yMax="427.0784">LCD_MOSI</word>
-<word xMin="271.5214" yMin="420.6071" xMax="274.7546" yMax="427.0784">5</word>
-<word xMin="660.5742" yMin="420.6071" xMax="663.8074" yMax="427.0784">8</word>
-<word xMin="669.2092" yMin="420.6071" xMax="708.5464" yMax="427.0784">FPC_LCD_BL</word>
-<word xMin="777.6259" yMin="420.6071" xMax="791.6345" yMax="427.0784">GND</word>
-<word xMin="264.0000" yMin="425.7715" xMax="281.0003" yMax="427.7740">PIM105</word>
-<word xMin="653.0000" yMin="425.7715" xMax="670.0003" yMax="427.7740">PIFPC108</word>
-<word xMin="637.5151" yMin="425.8005" xMax="643.9815" yMax="429.0362">9</word>
-<word xMin="285.1935" yMin="424.2023" xMax="292.9770" yMax="430.6736">G5</word>
-<word xMin="646.9022" yMin="424.2023" xMax="650.1354" yMax="430.6736">8</word>
-<word xMin="97.9998" yMin="420.8695" xMax="101.0015" yMax="430.8700">PID602</word>
-<word xMin="106.9999" yMin="425.0950" xMax="113.0013" yMax="433.0960">COD6</word>
-<word xMin="228.9998" yMin="426.2056" xMax="249.0011" yMax="433.2090">NLLCD0SCK</word>
-<word xMin="769.9998" yMin="426.2080" xMax="776.0010" yMax="433.2090">COJ3</word>
-<word xMin="107.9370" yMin="427.0784" xMax="115.7205" yMax="433.5497">D6</word>
-<word xMin="229.5459" yMin="427.7974" xMax="258.4860" yMax="434.2688">LCD_SCK</word>
-<word xMin="271.2816" yMin="427.7974" xMax="274.5148" yMax="434.2688">6</word>
-<word xMin="372.7423" yMin="427.7974" xMax="389.1461" yMax="434.2688">+3.3V</word>
-<word xMin="769.9504" yMin="427.7974" xMax="775.5787" yMax="434.2688">J3</word>
-<word xMin="457.9998" yMin="424.8695" xMax="461.0015" yMax="434.8700">PIR202</word>
-<word xMin="486.9998" yMin="424.8695" xMax="490.0015" yMax="434.8700">PIR302</word>
-<word xMin="264.0000" yMin="432.6582" xMax="281.0005" yMax="435.6610">PIM106</word>
-<word xMin="292.3893" yMin="431.3926" xMax="300.1728" yMax="437.8639">G6</word>
-<word xMin="228.9998" yMin="433.2061" xMax="246.0010" yMax="440.2090">NLLCD0CS</word>
-<word xMin="462.9998" yMin="433.2080" xMax="469.0010" yMax="440.2090">COR2</word>
-<word xMin="491.9998" yMin="433.2081" xMax="497.0010" yMax="440.2090">COR3</word>
-<word xMin="107.9370" yMin="434.2688" xMax="138.9501" yMax="440.7401">1N4148WT</word>
-<word xMin="229.5459" yMin="434.9878" xMax="253.7371" yMax="441.4591">LCD_CS</word>
-<word xMin="271.2816" yMin="434.9878" xMax="274.5148" yMax="441.4591">7</word>
-<word xMin="357.8710" yMin="434.9878" xMax="364.2177" yMax="441.4591">28</word>
-<word xMin="463.1695" yMin="434.9878" xMax="470.7745" yMax="441.4591">R2</word>
-<word xMin="491.9527" yMin="434.9878" xMax="499.5578" yMax="441.4591">R3</word>
-<word xMin="741.1672" yMin="434.9878" xMax="752.9437" yMax="441.4591">SCL</word>
-<word xMin="761.7951" yMin="434.9878" xMax="765.0283" yMax="441.4591">1</word>
-<word xMin="428.9998" yMin="431.8695" xMax="432.0015" yMax="441.8700">PIC202</word>
-<word xMin="515.9998" yMin="431.8695" xMax="519.0015" yMax="441.8700">PIC302</word>
-<word xMin="264.0000" yMin="439.6582" xMax="281.0005" yMax="442.6610">PIM107</word>
-<word xMin="350.0000" yMin="439.6580" xMax="368.0005" yMax="442.6610">PIM1028</word>
-<word xMin="754.0000" yMin="439.6582" xMax="771.0005" yMax="442.6610">PIJ301</word>
-<word xMin="633.9172" yMin="439.7018" xMax="640.3836" yMax="442.9375">9</word>
-<word xMin="148.9998" yMin="436.2075" xMax="158.0010" yMax="443.2090">COLS1</word>
-<word xMin="149.6726" yMin="437.8639" xMax="160.3912" yMax="444.3353">LS1</word>
-<word xMin="285.1935" yMin="438.5830" xMax="292.9770" yMax="445.0543">G7</word>
-<word xMin="336.5235" yMin="438.5830" xMax="347.6598" yMax="445.0543">3V3</word>
-<word xMin="775.2273" yMin="438.5830" xMax="798.9788" yMax="445.0543">IIC_SCL</word>
-<word xMin="436.9998" yMin="440.2080" xMax="443.0010" yMax="447.2090">COC2</word>
-<word xMin="523.9998" yMin="440.2080" xMax="530.0010" yMax="447.2090">COC3</word>
-<word xMin="437.9842" yMin="441.4591" xMax="445.5893" yMax="447.9304">C2</word>
-<word xMin="524.3338" yMin="441.4591" xMax="531.9389" yMax="447.9304">C3</word>
-<word xMin="228.9999" yMin="440.0915" xMax="255.0013" yMax="448.0960">NLLCD0RESET</word>
-<word xMin="638.9997" yMin="431.0785" xMax="642.0027" yMax="448.0790">PIFPC109</word>
-<word xMin="229.5459" yMin="442.1782" xMax="265.5886" yMax="448.6495">LCD_RESET</word>
-<word xMin="271.5214" yMin="442.1782" xMax="274.7546" yMax="448.6495">8</word>
-<word xMin="357.8710" yMin="442.1782" xMax="364.2177" yMax="448.6495">27</word>
-<word xMin="380.8976" yMin="442.1782" xMax="398.7382" yMax="448.6495">HOLD</word>
-<word xMin="463.1695" yMin="442.1782" xMax="479.2299" yMax="448.6495">10KΩ</word>
-<word xMin="491.9527" yMin="442.1782" xMax="508.0132" yMax="448.6495">10KΩ</word>
-<word xMin="741.1672" yMin="442.1782" xMax="753.9789" yMax="448.6495">SDA</word>
-<word xMin="761.3154" yMin="442.1782" xMax="764.5486" yMax="448.6495">2</word>
-<word xMin="134.0000" yMin="446.6582" xMax="151.0005" yMax="449.6610">PILS101</word>
-<word xMin="264.0000" yMin="446.6582" xMax="281.0005" yMax="449.6610">PIM108</word>
-<word xMin="350.0000" yMin="446.6580" xMax="368.0005" yMax="449.6610">PIM1027</word>
-<word xMin="754.0000" yMin="446.6582" xMax="771.0005" yMax="449.6610">PIJ302</word>
-<word xMin="292.3893" yMin="445.7733" xMax="300.1728" yMax="452.2447">G8</word>
-<word xMin="328.8479" yMin="445.7733" xMax="339.9843" yMax="452.2447">G46</word>
-<word xMin="775.2273" yMin="445.7733" xMax="800.0140" yMax="452.2447">IIC_SDA</word>
-<word xMin="97.9998" yMin="442.8695" xMax="101.0015" yMax="452.8700">PID601</word>
-<word xMin="437.9842" yMin="448.6495" xMax="454.5122" yMax="455.1208">100nF</word>
-<word xMin="524.3338" yMin="448.6495" xMax="540.8617" yMax="455.1208">100nF</word>
-<word xMin="228.9998" yMin="448.2061" xMax="246.0010" yMax="455.2090">NLLCD0BL</word>
-<word xMin="229.5459" yMin="449.3685" xMax="254.0345" yMax="455.8398">LCD_BL</word>
-<word xMin="271.2816" yMin="449.3685" xMax="274.5148" yMax="455.8398">9</word>
-<word xMin="357.8710" yMin="449.3685" xMax="364.2177" yMax="455.8398">26</word>
-<word xMin="761.5553" yMin="449.3685" xMax="764.7885" yMax="455.8398">3</word>
-<word xMin="428.9998" yMin="445.8695" xMax="432.0015" yMax="455.8700">PIC201</word>
-<word xMin="457.9998" yMin="445.8695" xMax="461.0015" yMax="455.8700">PIR201</word>
-<word xMin="486.9998" yMin="445.8695" xMax="490.0015" yMax="455.8700">PIR301</word>
-<word xMin="515.9998" yMin="445.8695" xMax="519.0015" yMax="455.8700">PIC301</word>
-<word xMin="134.0000" yMin="453.6582" xMax="151.0005" yMax="456.6610">PILS102</word>
-<word xMin="264.0000" yMin="453.6582" xMax="281.0005" yMax="456.6610">PIM109</word>
-<word xMin="350.0000" yMin="453.6580" xMax="368.0005" yMax="456.6610">PIM1026</word>
-<word xMin="754.0000" yMin="453.6582" xMax="771.0005" yMax="456.6610">PIJ303</word>
-<word xMin="285.1935" yMin="452.9637" xMax="292.9770" yMax="459.4350">G9</word>
-<word xMin="326.9291" yMin="452.9637" xMax="346.9268" yMax="459.4350">G43/Tx</word>
-<word xMin="722.2182" yMin="452.9637" xMax="747.0049" yMax="459.4350">+5VOUT</word>
-<word xMin="775.2273" yMin="452.9637" xMax="788.6411" yMax="459.4350">VCC</word>
-<word xMin="235.9998" yMin="455.2059" xMax="254.0010" yMax="462.2090">NLBATADC</word>
-<word xMin="236.7418" yMin="456.5589" xMax="262.1305" yMax="463.0302">BATADC</word>
-<word xMin="267.9235" yMin="456.5589" xMax="274.2702" yMax="463.0302">10</word>
-<word xMin="357.8710" yMin="456.5589" xMax="364.2177" yMax="463.0302">25</word>
-<word xMin="380.8976" yMin="456.5589" xMax="399.4579" yMax="463.0302">WAKE</word>
-<word xMin="761.3154" yMin="456.5589" xMax="764.5486" yMax="463.0302">4</word>
-<word xMin="264.0000" yMin="461.7714" xMax="281.0003" yMax="463.7740">PIM1010</word>
-<word xMin="350.0000" yMin="461.7713" xMax="368.0003" yMax="463.7740">PIM1025</word>
-<word xMin="754.0000" yMin="461.7715" xMax="771.0003" yMax="463.7740">PIJ304</word>
-<word xMin="292.3893" yMin="460.1541" xMax="303.5256" yMax="466.6254">G10</word>
-<word xMin="307.9802" yMin="460.1541" xMax="340.0751" yMax="466.6254">G42/MTMS</word>
-<word xMin="775.2273" yMin="460.1541" xMax="789.2360" yMax="466.6254">GND</word>
-<word xMin="149.6726" yMin="460.8731" xMax="168.1107" yMax="467.3444">Buzzer</word>
-<word xMin="235.9998" yMin="462.2075" xMax="245.0010" yMax="469.2090">NLGND</word>
-<word xMin="236.7418" yMin="463.7492" xMax="250.7504" yMax="470.2206">GND</word>
-<word xMin="268.6431" yMin="463.7492" xMax="274.7499" yMax="470.2206">11</word>
-<word xMin="357.8710" yMin="463.7492" xMax="364.2177" yMax="470.2206">24</word>
-<word xMin="451.8961" yMin="463.7492" xMax="468.2999" yMax="470.2206">+3.3V</word>
-<word xMin="480.9192" yMin="463.7492" xMax="497.3229" yMax="470.2206">+3.3V</word>
-<word xMin="264.0000" yMin="468.6582" xMax="281.0005" yMax="471.6610">PIM1011</word>
-<word xMin="350.0000" yMin="468.6580" xMax="368.0005" yMax="471.6610">PIM1024</word>
-<word xMin="285.1935" yMin="467.3444" xMax="299.2021" yMax="473.8157">GND</word>
-<word xMin="326.4493" yMin="467.3444" xMax="346.9256" yMax="473.8157">G44/Rx</word>
-<word xMin="379.9998" yMin="469.2069" xMax="392.0010" yMax="476.2090">NLIN0A</word>
-<word xMin="596.9998" yMin="469.2081" xMax="602.0010" yMax="476.2090">COU6</word>
-<word xMin="236.7418" yMin="470.9396" xMax="259.6118" yMax="477.4109">IN_SDA</word>
-<word xMin="268.1634" yMin="470.9396" xMax="274.5101" yMax="477.4109">12</word>
-<word xMin="357.8710" yMin="470.9396" xMax="364.2177" yMax="477.4109">23</word>
-<word xMin="380.8976" yMin="470.9396" xMax="395.6253" yMax="477.4109">IN_A</word>
-<word xMin="424.5521" yMin="470.9396" xMax="438.5607" yMax="477.4109">GND</word>
-<word xMin="510.9016" yMin="470.9396" xMax="524.9103" yMax="477.4109">GND</word>
-<word xMin="545.6813" yMin="470.9396" xMax="562.0851" yMax="477.4109">+3.3V</word>
-<word xMin="597.0114" yMin="470.9396" xMax="604.7949" yMax="477.4109">U6</word>
-<word xMin="769.9504" yMin="470.9396" xMax="800.8471" yMax="477.4109">HY-2.0_IIC</word>
-<word xMin="264.0000" yMin="475.6582" xMax="281.0005" yMax="478.6610">PIM1012</word>
-<word xMin="350.0000" yMin="475.6580" xMax="368.0005" yMax="478.6610">PIM1023</word>
-<word xMin="292.3893" yMin="474.5348" xMax="303.2863" yMax="481.0061">G11</word>
-<word xMin="310.3787" yMin="474.5348" xMax="340.0734" yMax="481.0061">G41/MTDI</word>
-<word xMin="133.9997" yMin="467.0785" xMax="137.0027" yMax="484.0790">PIQ503</word>
-<word xMin="76.9998" yMin="477.2075" xMax="86.0010" yMax="484.2090">COC27</word>
-<word xMin="268.4033" yMin="478.1300" xMax="274.7500" yMax="484.6013">13</word>
-<word xMin="357.8710" yMin="478.1300" xMax="364.2177" yMax="484.6013">22</word>
-<word xMin="583.5792" yMin="478.1300" xMax="591.3627" yMax="484.6013">A2</word>
-<word xMin="653.3784" yMin="478.1300" xMax="661.1619" yMax="484.6013">A1</word>
-<word xMin="676.4050" yMin="478.1300" xMax="715.7423" yMax="484.6013">FPC_LCD_BL</word>
-<word xMin="748.8427" yMin="478.1300" xMax="762.8513" yMax="484.6013">GND</word>
-<word xMin="77.4748" yMin="478.8490" xMax="88.1319" yMax="485.3203">C27</word>
-<word xMin="264.0000" yMin="482.6582" xMax="281.0005" yMax="485.6610">PIM1013</word>
-<word xMin="350.0000" yMin="482.6580" xMax="368.0005" yMax="485.6610">PIM1022</word>
-<word xMin="574.0000" yMin="482.6570" xMax="598.0005" yMax="485.6610">PIU60A2</word>
-<word xMin="646.0000" yMin="482.6570" xMax="670.0005" yMax="485.6610">PIU60A1</word>
-<word xMin="48.9998" yMin="481.2075" xMax="58.0010" yMax="488.2090">COR25</word>
-<word xMin="202.6816" yMin="481.7251" xMax="221.0014" yMax="488.1965">+5VIN</word>
-<word xMin="285.1935" yMin="481.7251" xMax="292.9757" yMax="488.1965">5V</word>
-<word xMin="338.4424" yMin="481.7251" xMax="346.9430" yMax="488.1965">EN</word>
-<word xMin="602.2883" yMin="481.7251" xMax="613.6625" yMax="488.1965">VIN</word>
-<word xMin="624.5952" yMin="481.7251" xMax="642.4365" yMax="488.1965">VOUT</word>
-<word xMin="49.4112" yMin="482.4442" xMax="60.0683" yMax="488.9155">R25</word>
-<word xMin="136.9998" yMin="483.2080" xMax="143.0010" yMax="490.2090">COQ5</word>
-<word xMin="422.9998" yMin="483.2080" xMax="429.0010" yMax="490.2090">COS4</word>
-<word xMin="138.1593" yMin="484.6012" xMax="145.9428" yMax="491.0725">Q5</word>
-<word xMin="423.3528" yMin="484.6012" xMax="430.2394" yMax="491.0725">S4</word>
-<word xMin="23.9998" yMin="484.2071" xMax="35.0010" yMax="491.2090">NLbeep</word>
-<word xMin="379.9998" yMin="484.2069" xMax="392.0010" yMax="491.2090">NLIN0B</word>
-<word xMin="24.2259" yMin="485.3202" xMax="36.3205" yMax="491.7916">beep</word>
-<word xMin="236.7418" yMin="485.3202" xMax="258.8165" yMax="491.7916">IN_SCL</word>
-<word xMin="267.9235" yMin="485.3202" xMax="274.2702" yMax="491.7916">14</word>
-<word xMin="357.8710" yMin="485.3202" xMax="364.2177" yMax="491.7916">21</word>
-<word xMin="380.8976" yMin="485.3202" xMax="395.2696" yMax="491.7916">IN_B</word>
-<word xMin="551.9998" yMin="481.8695" xMax="555.0015" yMax="491.8700">PIC402</word>
-<word xMin="40.0000" yMin="489.6593" xMax="50.0005" yMax="492.6610">PIR2501</word>
-<word xMin="62.0000" yMin="489.6598" xMax="70.4291" yMax="492.6610">PIR25P</word>
-<word xMin="69.1429" yMin="489.6596" xMax="71.8576" yMax="492.6608">0I</word>
-<word xMin="70.5714" yMin="489.6593" xMax="73.2862" yMax="492.6605">2C</word>
-<word xMin="73.2857" yMin="489.6593" xMax="79.0005" yMax="492.6603">2701</word>
-<word xMin="83.0000" yMin="489.6592" xMax="94.0005" yMax="492.6610">PIC2702</word>
-<word xMin="112.0000" yMin="489.6580" xMax="130.0005" yMax="492.6610">PIQ501</word>
-<word xMin="264.0000" yMin="489.6582" xMax="281.0005" yMax="492.6610">PIM1014</word>
-<word xMin="350.0000" yMin="489.6580" xMax="368.0005" yMax="492.6610">PIM1021</word>
-<word xMin="292.3893" yMin="488.9154" xMax="303.5256" yMax="495.3867">G12</word>
-<word xMin="307.9802" yMin="488.9154" xMax="339.9510" yMax="495.3867">G40/MTDO</word>
-<word xMin="559.9998" yMin="490.2080" xMax="566.0010" yMax="497.2090">COC4</word>
-<word xMin="235.9998" yMin="491.2075" xMax="245.0010" yMax="498.2090">NLSDA</word>
-<word xMin="769.9998" yMin="491.2080" xMax="776.0010" yMax="498.2090">COJ4</word>
-<word xMin="138.1593" yMin="491.7916" xMax="158.6356" yMax="498.2629">SS8050</word>
-<word xMin="159.9527" yMin="491.7916" xMax="167.7363" yMax="498.2629">Y1</word>
-<word xMin="560.3128" yMin="491.7916" xMax="567.9179" yMax="498.2629">C4</word>
-<word xMin="236.7418" yMin="492.5106" xMax="249.5535" yMax="498.9819">SDA</word>
-<word xMin="268.1634" yMin="492.5106" xMax="274.5101" yMax="498.9819">15</word>
-<word xMin="357.8710" yMin="492.5106" xMax="364.2177" yMax="498.9819">20</word>
-<word xMin="653.3784" yMin="492.5106" xMax="660.9835" yMax="498.9819">B2</word>
-<word xMin="676.4050" yMin="492.5106" xMax="700.8937" yMax="498.9819">LCD_BL</word>
-<word xMin="769.9504" yMin="492.5106" xMax="775.5787" yMax="498.9819">J4</word>
-<word xMin="264.0000" yMin="497.7714" xMax="281.0003" yMax="499.7740">PIM1015</word>
-<word xMin="350.0000" yMin="497.7713" xMax="368.0003" yMax="499.7740">PIM1020</word>
-<word xMin="408.0000" yMin="497.7715" xMax="425.0003" yMax="499.7740">PIS401</word>
-<word xMin="444.0000" yMin="497.7715" xMax="461.0003" yMax="499.7740">PIS402</word>
-<word xMin="646.0000" yMin="497.7704" xMax="670.0003" yMax="499.7740">PIU60B2</word>
-<word xMin="49.4112" yMin="495.3867" xMax="64.0348" yMax="501.8581">470Ω</word>
-<word xMin="285.1935" yMin="496.1058" xMax="296.3298" yMax="502.5771">G13</word>
-<word xMin="324.7704" yMin="496.1058" xMax="346.9246" yMax="502.5771">G0/Boot</word>
-<word xMin="633.9498" yMin="496.1058" xMax="642.4504" yMax="502.5771">EN</word>
-<word xMin="77.4748" yMin="498.9819" xMax="90.8892" yMax="505.4532">10uF</word>
-<word xMin="560.3128" yMin="498.9819" xMax="576.8407" yMax="505.4532">100nF</word>
-<word xMin="11.2734" yMin="499.7009" xMax="15.9421" yMax="506.1723">D</word>
-<word xMin="251.1333" yMin="499.7009" xMax="262.2696" yMax="506.1723">G14</word>
-<word xMin="267.9235" yMin="499.7009" xMax="274.2702" yMax="506.1723">16</word>
-<word xMin="357.8710" yMin="499.7009" xMax="364.2177" yMax="506.1723">19</word>
-<word xMin="380.8976" yMin="499.7009" xMax="392.0339" yMax="506.1723">G39</word>
-<word xMin="733.9714" yMin="499.7009" xMax="740.6750" yMax="506.1723">GI</word>
-<word xMin="761.7951" yMin="499.7009" xMax="765.0283" yMax="506.1723">1</word>
-<word xMin="825.5979" yMin="499.7009" xMax="830.2666" yMax="506.1723">D</word>
-<word xMin="97.9998" yMin="496.8695" xMax="101.0015" yMax="506.8700">PID702</word>
-<word xMin="551.9998" yMin="496.8695" xMax="555.0015" yMax="506.8700">PIC401</word>
-<word xMin="264.0000" yMin="504.6582" xMax="281.0005" yMax="507.6610">PIM1016</word>
-<word xMin="350.0000" yMin="504.6580" xMax="368.0005" yMax="507.6610">PIM1019</word>
-<word xMin="754.0000" yMin="504.6582" xMax="771.0005" yMax="507.6610">PIJ401</word>
-<word xMin="106.9998" yMin="501.2080" xMax="113.0010" yMax="508.2090">COD7</word>
-<word xMin="423.3528" yMin="501.8581" xMax="442.7543" yMax="508.3294">SW-PB</word>
-<word xMin="107.9370" yMin="502.5771" xMax="115.7205" yMax="509.0484">D7</word>
-<word xMin="292.3893" yMin="503.2961" xMax="303.5256" yMax="509.7674">G14</word>
-<word xMin="307.9802" yMin="503.2961" xMax="339.7111" yMax="509.7674">G39/MTCK</word>
-<word xMin="775.2273" yMin="503.2961" xMax="777.3806" yMax="509.7674">I</word>
-<word xMin="171.9999" yMin="502.0951" xMax="177.0013" yMax="510.0960">COR9</word>
-<word xMin="171.9796" yMin="504.0152" xMax="179.5846" yMax="510.4865">R9</word>
-<word xMin="199.9998" yMin="505.2075" xMax="209.0010" yMax="512.2090">NLG14</word>
-<word xMin="235.9998" yMin="505.2075" xMax="245.0010" yMax="512.2090">NLSCL</word>
-<word xMin="133.9997" yMin="496.0785" xMax="137.0027" yMax="513.0790">PIQ502</word>
-<word xMin="200.7628" yMin="506.8913" xMax="211.8991" yMax="513.3626">G14</word>
-<word xMin="236.7418" yMin="506.8913" xMax="248.5182" yMax="513.3626">SCL</word>
-<word xMin="268.1634" yMin="506.8913" xMax="274.5101" yMax="513.3626">17</word>
-<word xMin="357.8710" yMin="506.8913" xMax="364.2177" yMax="513.3626">18</word>
-<word xMin="584.5387" yMin="506.8913" xMax="592.1437" yMax="513.3626">B1</word>
-<word xMin="733.9714" yMin="506.8913" xMax="743.1904" yMax="513.3626">GO</word>
-<word xMin="761.3154" yMin="506.8913" xMax="764.5486" yMax="513.3626">2</word>
-<word xMin="163.0000" yMin="511.6593" xMax="173.0005" yMax="514.6610">PIR902</word>
-<word xMin="184.0000" yMin="511.6592" xMax="195.0005" yMax="514.6610">PIR901</word>
-<word xMin="264.0000" yMin="511.6582" xMax="281.0005" yMax="514.6610">PIM1017</word>
-<word xMin="350.0000" yMin="511.6580" xMax="368.0005" yMax="514.6610">PIM1018</word>
-<word xMin="574.0000" yMin="511.6570" xMax="598.0005" yMax="514.6610">PIU60B1</word>
-<word xMin="754.0000" yMin="511.6582" xMax="771.0005" yMax="514.6610">PIJ402</word>
-<word xMin="107.9370" yMin="509.7674" xMax="138.9501" yMax="516.2388">1N4148WT</word>
-<word xMin="285.1935" yMin="510.4865" xMax="296.3298" yMax="516.9578">G15</word>
-<word xMin="333.1654" yMin="510.4865" xMax="347.1741" yMax="516.9578">GND</word>
-<word xMin="602.2883" yMin="510.4865" xMax="616.2969" yMax="516.9578">GND</word>
-<word xMin="775.2273" yMin="510.4865" xMax="779.8960" yMax="516.9578">O</word>
-<word xMin="761.5553" yMin="514.0817" xMax="764.7885" yMax="520.5530">3</word>
-<word xMin="754.0000" yMin="518.6582" xMax="771.0005" yMax="521.6610">PIJ403</word>
-<word xMin="171.9796" yMin="516.9578" xMax="188.0400" yMax="523.4291">10KΩ</word>
-<word xMin="722.2182" yMin="517.6768" xMax="747.0049" yMax="524.1482">+5VOUT</word>
-<word xMin="775.2273" yMin="517.6768" xMax="788.6411" yMax="524.1482">VCC</word>
-<word xMin="291.1900" yMin="519.1149" xMax="298.1329" yMax="525.5862">D-</word>
-<word xMin="312.0578" yMin="519.1149" xMax="320.4944" yMax="525.5862">D+</word>
-<word xMin="329.0879" yMin="519.1149" xMax="346.6892" yMax="525.5862">PGND</word>
-<word xMin="460.5311" yMin="521.2720" xMax="474.5397" yMax="527.7433">GND</word>
-<word xMin="597.0114" yMin="521.2720" xMax="636.2904" yMax="527.7433">AW35122FDR</word>
-<word xMin="761.3154" yMin="521.2720" xMax="764.5486" yMax="527.7433">4</word>
-<word xMin="97.9998" yMin="517.8695" xMax="101.0015" yMax="527.8700">PID701</word>
-<word xMin="754.0000" yMin="525.6582" xMax="771.0005" yMax="528.6610">PIJ404</word>
-<word xMin="171.9998" yMin="524.2076" xMax="180.0010" yMax="531.2090">COR10</word>
-<word xMin="775.2273" yMin="524.8672" xMax="789.2360" yMax="531.3385">GND</word>
-<word xMin="171.9796" yMin="525.5862" xMax="182.6367" yMax="532.0576">R10</word>
-<word xMin="199.9998" yMin="527.2075" xMax="209.0010" yMax="534.2090">NLG39</word>
-<word xMin="200.7628" yMin="528.4624" xMax="211.8991" yMax="534.9337">G39</word>
-<word xMin="373.9416" yMin="528.4624" xMax="387.9503" yMax="534.9337">GND</word>
-<word xMin="546.8806" yMin="528.4624" xMax="560.8893" yMax="534.9337">GND</word>
-<word xMin="163.0000" yMin="533.7725" xMax="173.0003" yMax="535.7740">PIR1002</word>
-<word xMin="184.0000" yMin="533.7723" xMax="195.0003" yMax="535.7740">PIR1001</word>
-<word xMin="331.2140" yMin="532.9367" xMax="337.6803" yMax="536.1723">1</word>
-<word xMin="288.0393" yMin="533.4161" xMax="294.5056" yMax="536.6517">9</word>
-<word xMin="309.6266" yMin="533.4161" xMax="316.0929" yMax="536.6517">0</word>
-<word xMin="331.2140" yMin="536.0525" xMax="337.6803" yMax="539.2882">3</word>
-<word xMin="288.0393" yMin="536.5319" xMax="294.5056" yMax="539.7675">2</word>
-<word xMin="309.6266" yMin="536.5319" xMax="316.0929" yMax="539.7675">3</word>
-<word xMin="291.9997" yMin="523.9655" xMax="295.0028" yMax="541.9660">PIM1029</word>
-<word xMin="313.9997" yMin="523.9655" xMax="317.0028" yMax="541.9660">PIM1030</word>
-<word xMin="335.9997" yMin="523.9655" xMax="339.0028" yMax="541.9660">PIM1031</word>
-<word xMin="769.9504" yMin="535.6527" xMax="798.8076" yMax="542.1241">HY-2.0_IO</word>
-<word xMin="171.9796" yMin="538.5289" xMax="188.0400" yMax="545.0002">10KΩ</word>
-<word xMin="748.8427" yMin="542.8431" xMax="762.8513" yMax="549.3144">GND</word>
-<word xMin="280.1564" yMin="544.2812" xMax="326.4967" yMax="550.7525">STAMP-S3-SMD</word>
-<word xMin="93.0657" yMin="550.0335" xMax="107.0743" yMax="556.5048">GND</word>
-<word xMin="129.0447" yMin="550.0335" xMax="143.0533" yMax="556.5048">GND</word>
-<word xMin="150.6320" yMin="550.0335" xMax="164.6407" yMax="556.5048">GND</word>
-<word xMin="330.7668" yMin="557.2238" xMax="344.7755" yMax="563.6951">GND</word>
-<word xMin="107.4573" yMin="560.8190" xMax="110.6904" yMax="567.2903">1</word>
-<word xMin="313.9766" yMin="560.8190" xMax="317.2098" yMax="567.2903">2</word>
-<word xMin="521.4555" yMin="560.8190" xMax="524.6886" yMax="567.2903">3</word>
-<word xMin="728.2148" yMin="560.8190" xMax="731.4479" yMax="567.2903">4</word>
-</page>
-</pdf2xml>
diff --git a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf b/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf
deleted file mode 100644
index 6dced46..0000000
Binary files a/devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf and /dev/null differ
diff --git a/devices/m5stack/dinmeter/artifacts/schematic/M1-stamp-s3-pinout-from-schematic.txt b/devices/m5stack/dinmeter/artifacts/schematic/M1-stamp-s3-pinout-from-schematic.txt
deleted file mode 100644
index 3d13711..0000000
--- a/devices/m5stack/dinmeter/artifacts/schematic/M1-stamp-s3-pinout-from-schematic.txt
+++ /dev/null
@@ -1,33 +0,0 @@
-M1 (STAMP-S3-SMD) pin pads found: 31 -> [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31]
-pad x range 272.50014999999996 359.00025
-  pin  1  x=  272.5 y=  397.8  L=['R24', 'GI']  R=['G1', '4', '4', 'LCD_MOSI']
-  pin  2  x=  272.5 y=  405.2  L=['10Ω', 'GO']  R=['G2', '+3.3V', 'Rotary', 'encode', 'LCD_RS', '5', '5']
-  pin  3  x=  272.5 y=  412.2  L=['GND', 'beep']  R=['G3', 'GND', 'A', 'B', '6', '6', 'LCD_RESET']
-  pin  4  x=  272.5 y=  419.2  L=['LCD_RS']  R=['G4', '_', 'GND', '_', 'GND', '7', '7']
-  pin  5  x=  272.5 y=  426.8  L=['LCD_MOSI']  R=['G5', 'I', 'I', '9', '8', '8', 'FPC_LCD_BL', 'GND']
-  pin  6  x=  272.5 y=  434.2  L=['LCD_SCK']  R=['G6', '+3.3V', 'J3']
-  pin  7  x=  272.5 y=  441.2  L=['LS1', 'LCD_CS']  R=['G7', '3V3', '28', 'R2', 'R3', '9', 'SCL', '1', 'IIC_SCL']
-  pin  8  x=  272.5 y=  448.2  L=['LCD_RESET']  R=['G8', 'G46', '27', 'HOLD', '10KΩ', '10KΩ', 'SDA', '2', 'IIC_SDA']
-  pin  9  x=  272.5 y=  455.2  L=['LCD_BL']  R=['G9', 'G43/Tx', '26', '+5VOUT', '3', 'VCC']
-  pin 10  x=  272.5 y=  462.8  L=['Buzzer', 'BATADC', '10']  R=['G10', 'G42/MTMS', '25', 'WAKE', '4', 'GND']
-  pin 11  x=  272.5 y=  470.2  L=['GND']  R=['GND', 'G44/Rx', '24', '+3.3V', '+3.3V']
-  pin 12  x=  272.5 y=  477.2  L=['IN_SDA', '12']  R=['G11', 'G41/MTDI', '23', 'IN_A', 'GND', 'GND', '+3.3V', 'U6', 'HY-2.0_IIC']
-  pin 13  x=  272.5 y=  484.2  L=['R25', 'C27', '+5VIN']  R=['5V', 'EN', '22', 'A2', 'VIN', 'VOUT', 'A1', 'FPC_LCD_BL', 'GND']
-  pin 14  x=  272.5 y=  491.2  L=['beep', '0I', '2C', '2701', 'IN_SCL', '14']  R=['G12', 'G40/MTDO', '21', 'IN_B']
-  pin 15  x=  272.5 y=  498.8  L=['470Ω', 'SDA', '15']  R=['G13', 'G0/Boot', '20', 'EN', 'B2', 'LCD_BL', 'J4']
-  pin 16  x=  272.5 y=  506.2  L=['D7', 'R9']  R=['G14', 'G39/MTCK', 'SW-PB', 'I']
-  pin 17  x=  272.5 y=  513.2  L=['1N4148WT', 'G14', 'SCL', '17']  R=['G15', 'GND', '18', 'B1', 'GND', 'GO', '2', 'O']
-  pin 18  x=  359.0 y=  513.2  L=['1N4148WT', 'G14', 'SCL', '17', 'G15', 'GND']  R=['18', 'B1', 'GND', 'GO', '2', 'O']
-  pin 19  x=  359.0 y=  506.2  L=['D7', 'R9', 'G14', 'G39/MTCK']  R=['SW-PB', 'I']
-  pin 20  x=  359.0 y=  498.8  L=['470Ω', 'SDA', '15', 'G13', 'G0/Boot']  R=['20', 'EN', 'B2', 'LCD_BL', 'J4']
-  pin 21  x=  359.0 y=  491.2  L=['beep', '0I', '2C', '2701', 'IN_SCL', '14', 'G12', 'G40/MTDO']  R=['21', 'IN_B']
-  pin 22  x=  359.0 y=  484.2  L=['R25', 'C27', '+5VIN', '13', '5V', 'EN']  R=['22', 'A2', 'VIN', 'VOUT', 'A1', 'FPC_LCD_BL', 'GND']
-  pin 23  x=  359.0 y=  477.2  L=['IN_SDA', '12', 'G11', 'G41/MTDI']  R=['23', 'IN_A', 'GND', 'GND', '+3.3V', 'U6', 'HY-2.0_IIC']
-  pin 24  x=  359.0 y=  470.2  L=['GND', '11', 'GND', 'G44/Rx']  R=['24', '+3.3V', '+3.3V']
-  pin 25  x=  359.0 y=  462.8  L=['Buzzer', 'BATADC', '10', 'G10', 'G42/MTMS']  R=['25', 'WAKE', '4', 'GND']
-  pin 26  x=  359.0 y=  455.2  L=['LCD_BL', '9', 'G9', 'G43/Tx']  R=['26', '+5VOUT', '3', 'VCC']
-  pin 27  x=  359.0 y=  448.2  L=['LCD_RESET', '8', 'G8', 'G46']  R=['27', 'HOLD', '10KΩ', '10KΩ', 'SDA', '2', 'IIC_SDA']
-  pin 28  x=  359.0 y=  441.2  L=['LS1', 'LCD_CS', '7', 'G7', '3V3']  R=['28', 'R2', 'R3', '9', 'SCL', '1', 'IIC_SCL']
-  pin 29  x=  293.5 y=  533.0  L=['G39', '9']  R=['0', '1', 'GND', 'GND']
-  pin 30  x=  315.5 y=  533.0  L=['G39', '9', '0']  R=['1', 'GND', 'GND']
-  pin 31  x=  337.5 y=  533.0  L=['G39', '9', '0', '1']  R=['GND', 'GND']
diff --git a/devices/m5stack/dinmeter/artifacts/schematic/parse_dinmeter_sch.py b/devices/m5stack/dinmeter/artifacts/schematic/parse_dinmeter_sch.py
deleted file mode 100644
index e319882..0000000
--- a/devices/m5stack/dinmeter/artifacts/schematic/parse_dinmeter_sch.py
+++ /dev/null
@@ -1,81 +0,0 @@
-#!/usr/bin/env python3
-"""Parse the M5Stack DinMeter (K134) Altium-published schematic PDF bbox XML.
-
-Altium's PDF publisher emits an invisible marker layer:
-  CO<designator>       component outline
-  PI<designator><pin>  pin instance
-  NL<netname>          net label
-Non-alphanumerics are replaced by '0' in markers, so markers locate objects;
-the human-readable text beside them supplies the real name.
-
-Usage: parse_dinmeter_sch.py <bbox.xml>
-"""
-import re, sys, math, html, json
-
-WORD = re.compile(r'<word xMin="([\d.\-]+)" yMin="([\d.\-]+)" xMax="([\d.\-]+)" yMax="([\d.\-]+)">(.*?)</word>')
-MARKER = re.compile(r'(?<![A-Za-z])(CO|PI|NL)([A-Z0-9]+)')
-
-def load(path):
-    out=[]
-    for m in WORD.finditer(open(path,encoding='utf-8',errors='replace').read()):
-        x0,y0,x1,y1=(float(m.group(i)) for i in range(1,5))
-        out.append({'x':(x0+x1)/2,'y':(y0+y1)/2,'x0':x0,'y0':y0,'x1':x1,'y1':y1,
-                    't':html.unescape(m.group(5))})
-    return out
-
-def split_markers(words):
-    plain,co,pi,nl=[],[],[],[]
-    for w in words:
-        for mm in MARKER.finditer(w['t']):
-            kind,body=mm.group(1),mm.group(2)
-            rec=dict(w); rec['body']=body
-            (co if kind=='CO' else pi if kind=='PI' else nl).append(rec)
-        rest=MARKER.sub(' ',w['t']).strip()
-        if rest:
-            rec=dict(w); rec['t']=rest; plain.append(rec)
-    return plain,co,pi,nl
-
-def designators(co):
-    d=set()
-    for c in co:
-        m=re.match(r'([A-Z]+[0-9]+)',c['body'])
-        if m: d.add(m.group(1))
-    return d
-
-def split_pin(body,desigs):
-    c=[d for d in desigs if body.startswith(d) and body[len(d):].isdigit()]
-    if not c: return None,None
-    best=max(c,key=len)
-    return best, body[len(best):].lstrip('0') or '0'
-
-def near(w,pool,r):
-    out=[(math.hypot(p['x']-w['x'],p['y']-w['y']),p) for p in pool]
-    out=[o for o in out if o[0]<=r]; out.sort(key=lambda z:z[0]); return out
-
-if __name__=='__main__':
-    ws=load(sys.argv[1])
-    plain,co,pi,nl=split_markers(ws)
-    des=designators(co)
-    print(f"# words={len(ws)} plain={len(plain)} CO={len(co)} PI={len(pi)} NL={len(nl)}")
-    print(f"# designators ({len(des)}):")
-    print(json.dumps(sorted(des,key=lambda d:(re.match(r'[A-Z]+',d).group(),int(re.search(r'\d+',d).group())))))
-    print("\n## net labels (NL markers, with nearest plain text)")
-    seen=set()
-    for n in sorted(nl,key=lambda z:(z['y'],z['x'])):
-        cands=near(n,plain,14)
-        txt=cands[0][1]['t'] if cands else ''
-        key=(n['body'],txt)
-        if key in seen: continue
-        seen.add(key)
-        print(f"  NL{n['body']:<18} x={n['x']:7.1f} y={n['y']:7.1f}  text={txt!r}")
-    print("\n## pin instances -> nearest plain text (pin name / net)")
-    rows=[]
-    for p in pi:
-        d,pn=split_pin(p['body'],des)
-        cands=near(p,plain,16)
-        nls=near(p,nl,16)
-        rows.append((d or '?',int(pn) if pn and pn.isdigit() else 0,p['x'],p['y'],
-                     [c[1]['t'] for c in cands[:3]],
-                     [c[1]['body'] for c in nls[:2]]))
-    for d,pn,x,y,txts,nls in sorted(rows,key=lambda r:(r[0],r[1])):
-        print(f"  {d:<6} pin {pn:<3} x={x:7.1f} y={y:7.1f}  near={txts}  NL={nls}")
diff --git a/devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz b/devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz
deleted file mode 100644
index f888429..0000000
Binary files a/devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz and /dev/null differ
diff --git a/devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz b/devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz
deleted file mode 100644
index 61a41ce..0000000
Binary files a/devices/m5stack/dinmeter/artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz and /dev/null differ
diff --git a/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_devices.yaml b/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_devices.yaml
deleted file mode 100644
index f8a1c53..0000000
--- a/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_devices.yaml
+++ /dev/null
@@ -1,75 +0,0 @@
-# Devices Configuration for M5Stack Din Meter
-#
-# Source: M5Stack Din Meter official documentation (pin map)
-# Reference: https://docs.m5stack.com/en/core/M5DinMeter
-#
-# The ST7789V2 panel is driven by the esp_lcd_panel_st7789 driver built into
-# ESP-IDF's esp_lcd component, so no extra dependency is declared.
-#
-devices:
-  # ---------- Power latch (GPIO46, active-high) ----------
-  # Held HIGH the board stays on; released it powers itself down.
-  - name: power_hold
-    type: power_ctrl
-    sub_type: gpio
-    peripherals:
-      - gpio_name: gpio_power_hold
-        active_level: 1
-
-  # ---------- 1.14" 135x240 IPS LCD (ST7789V2, SPI) ----------
-  # The visible window is offset inside the controller's 240x320 GRAM
-  # (column +52, row +40). bmgr's display model has no offset field; the
-  # application applies it via the panel gap API.
-  - name: display_lcd
-    chip: st7789
-    type: display_lcd
-    sub_type: spi
-    version: default
-    config:
-      swap_xy: false
-      mirror_x: false
-      mirror_y: false
-      x_max: 135
-      y_max: 240
-      invert_color: true              # ST7789V2 panel on M5Stack needs inversion
-      need_reset: true
-      io_spi_config:
-        cs_gpio_num: 7
-        dc_gpio_num: 4
-        spi_mode: 0
-        pclk_hz: 40000000
-        trans_queue_depth: 10
-        lcd_cmd_bits: 8
-        lcd_param_bits: 8
-      lcd_panel_config:
-        reset_gpio_num: 8
-        rgb_ele_order: LCD_RGB_ELEMENT_ORDER_RGB
-        bits_per_pixel: 16
-        flags:
-          reset_active_high: false
-        vendor_config: NULL
-    peripherals:
-      - spi_name: spi_display
-
-  # ---------- LCD backlight (GPIO9 via LEDC) ----------
-  - name: lcd_brightness
-    type: ledc_ctrl
-    version: default
-    config:
-      default_percent: 100
-    peripherals:
-      - ledc_name: ledc_backlight
-
-  # ---------- Encoder push button / wake key (GPIO42, active-low) ----------
-  - name: wake_button
-    type: button
-    sub_type: gpio
-    version: default
-    config:
-      active_level: 0
-      enable_power_save: false
-      disable_pull: false
-      long_press_time: 2000
-      short_press_time: 100
-    peripherals:
-      - gpio_name: gpio_button_wake
diff --git a/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_info.yaml b/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_info.yaml
deleted file mode 100644
index 7212327..0000000
--- a/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_info.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-board: m5stack_dinmeter
-chip: esp32s3
-version: 1.0.0
-description: "M5Stack Din Meter (1.14 inch 135x240 ST7789V2 LCD, rotary encoder, buzzer, DIN rail)"
-manufacturer: "M5Stack"
diff --git a/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml b/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml
deleted file mode 100644
index f252963..0000000
--- a/devices/m5stack/dinmeter/artifacts/source-snapshots/dinmeter-board_peripherals.yaml
+++ /dev/null
@@ -1,141 +0,0 @@
-# Peripherals Configuration for M5Stack Din Meter
-#
-# Source: M5Stack Din Meter official documentation (pin map)
-# Reference: https://docs.m5stack.com/en/core/M5DinMeter
-#
-# Core: M5StampS3 module — ESP32-S3FN8, 8 MB in-package flash, no PSRAM.
-#
-# One internal I2C bus on GPIO11 (SDA) / GPIO12 (SCL) carries the BM8563 RTC
-# (7-bit 0x51).
-#
-# Power is latched by GPIO46: the firmware must drive it HIGH early or the
-# board switches itself off when the encoder button is released.
-#
-# The display and encoder wiring is the same family layout as the M5Dial.
-#
-peripherals:
-  # Internal I2C bus: BM8563 RTC
-  - name: i2c_master
-    type: i2c
-    role: master
-    config:
-      port: 0
-      pins:
-        sda: 11
-        scl: 12
-
-  # ST7789V2 LCD bus. Write-only panel, so no MISO line is wired.
-  - name: spi_display
-    type: spi
-    role: master
-    config:
-      spi_bus_config:
-        spi_port: SPI2_HOST
-        sclk_io_num: 6
-        mosi_io_num: 5
-        miso_io_num: -1
-        max_transfer_sz: 6480   # 135 * 24 lines * 2 bytes
-
-  # LCD backlight (GPIO9, PWM dimmable)
-  - name: ledc_backlight
-    type: ledc
-    config:
-      gpio_num: 9
-      channel: LEDC_CHANNEL_0
-      timer_sel: LEDC_TIMER_0
-      freq_hz: 5000
-      duty_resolution: LEDC_TIMER_10_BIT
-      speed_mode: LEDC_LOW_SPEED_MODE
-
-  # Passive buzzer (GPIO3). A passive buzzer is driven by a PWM tone, so the
-  # LEDC channel is the peripheral; there is no bmgr buzzer device type, and
-  # ledc_ctrl models a duty percentage rather than a frequency.
-  # The vendor pin table renders GPIO3 and GPIO42 in adjacent rows; M5Unified
-  # settles it: board_M5DinMeter sets spk_cfg.pin_data_out = GPIO_NUM_3 with
-  # spk_cfg.buzzer = true (M5Unified.cpp, _set_speaker branch), and reads the
-  # encoder button as !gpio_in(GPIO_NUM_42) (_update_button_state).
-  - name: ledc_buzzer
-    type: ledc
-    config:
-      gpio_num: 3
-      channel: LEDC_CHANNEL_1
-      timer_sel: LEDC_TIMER_1
-      freq_hz: 4000
-      duty: 0
-      duty_resolution: LEDC_TIMER_10_BIT
-      speed_mode: LEDC_LOW_SPEED_MODE
-
-  # Rotary encoder, quadrature on GPIO41 (A) and GPIO40 (B).
-  # Both channels are counted so one detent is four counts and the direction
-  # is unambiguous. Each pin is therefore both an edge input on one channel
-  # and a level input on the other, which is the IDF rotary-decoder pattern —
-  # the generator's IO-conflict note about GPIO40/41 is expected here.
-  - name: pcnt_encoder
-    type: pcnt
-    config:
-      unit_config:
-        low_limit: -1000
-        high_limit: 1000
-        intr_priority: 0
-        flags:
-          accum_count: true
-          # No en_step_notify_up / en_step_notify_down here on purpose: those
-          # pcnt_unit_config_t fields exist only under SOC_PCNT_SUPPORT_STEP_NOTIFY,
-          # which the ESP32-S3 does not have, and bmgr's periph_pcnt generator emits
-          # the field whenever the key is PRESENT — even when false. Keeping them
-          # (both were false) breaks the build with
-          # "'struct <anonymous>' has no member named 'en_step_notify_up'".
-      filter_config:
-        max_glitch_ns: 1000
-      channel_count: 2
-      channel_list:
-        - channel: 0
-          channel_config:
-            edge_gpio_num: 41    # encoder A
-            level_gpio_num: 40   # encoder B
-          pos_act: PCNT_CHANNEL_EDGE_ACTION_DECREASE
-          neg_act: PCNT_CHANNEL_EDGE_ACTION_INCREASE
-          high_act: PCNT_CHANNEL_LEVEL_ACTION_KEEP
-          low_act: PCNT_CHANNEL_LEVEL_ACTION_INVERSE
-        - channel: 1
-          channel_config:
-            edge_gpio_num: 40    # encoder B
-            level_gpio_num: 41   # encoder A
-          pos_act: PCNT_CHANNEL_EDGE_ACTION_INCREASE
-          neg_act: PCNT_CHANNEL_EDGE_ACTION_DECREASE
-          high_act: PCNT_CHANNEL_LEVEL_ACTION_KEEP
-          low_act: PCNT_CHANNEL_LEVEL_ACTION_INVERSE
-      watch_point_count: 3
-      watch_point_list: [-1000, 0, 1000]
-
-  # Power latch (GPIO46). Must be driven HIGH to keep the board powered.
-  - name: gpio_power_hold
-    type: gpio
-    role: io
-    config:
-      pin: 46
-      mode: GPIO_MODE_OUTPUT
-      default_level: 1
-
-  # Encoder push button, also the wake key (GPIO42, active-low)
-  - name: gpio_button_wake
-    type: gpio
-    version: default
-    role: io
-    config:
-      pin: 42
-      mode: GPIO_MODE_INPUT
-      pull_up: true
-      pull_down: false
-
-  # ----------------------------------------------------------------------
-  # Not modeled:
-  # - BM8563 RTC (I2C 7-bit 0x51): no bmgr device type; the i2c_master
-  #   above is its bus
-  # - HY2.0-4P PORT.A (GPIO13 yellow / GPIO15 white) and PORT.B
-  #   (GPIO2 yellow / GPIO1 white), each with 5V and GND
-  # - 6-36 V DC screw terminal on the DIN-rail base, the on-board Li-Po
-  #   charger (100 mA) and the battery connector
-  # - RESET button (EN pin, handled in hardware)
-  # - USB Type-C is the ESP32-S3's native USB OTG / Serial-JTAG (console path)
-  # ----------------------------------------------------------------------
diff --git a/devices/m5stack/dinmeter/artifacts/source-snapshots/launcher-m5stack-dinmeter-platformio.ini b/devices/m5stack/dinmeter/artifacts/source-snapshots/launcher-m5stack-dinmeter-platformio.ini
deleted file mode 100644
index 457b213..0000000
--- a/devices/m5stack/dinmeter/artifacts/source-snapshots/launcher-m5stack-dinmeter-platformio.ini
+++ /dev/null
@@ -1,69 +0,0 @@
-; PlatformIO Project Configuration File
-;
-;   Build options: build flags, source filter
-;   Upload options: custom upload port, speed and extra flags
-;   Library options: dependencies, extra library storages
-;   Advanced options: extra scripting
-;
-; Please visit documentation for the other options and examples
-; https://docs.platformio.org/page/projectconf.html
-
-[env:m5stack-dinmeter]
-board = esp32s3
-board_build.arduino.memory_type = qio_qspi
-board_build.partitions = support_files/custom_8Mb.csv
-board_upload.flash_size = 8MB
-board_upload.maximum_size = 8388608
-build_src_filter =${env.build_src_filter} +<../boards/m5stack-dinmeter>
-build_flags =
-	${env.build_flags}
-	-DM5STACK
-	-DARDUINO_USB_MODE=1
-	-DARDUINO_USB_CDC_ON_BOOT=1
-
-	-DDEVICE_NAME='"M5Stack DinMeter"'
-	-DOTA_TAG='"dinmeter"'
-
-	-D HAS_ENCODER=1
-	-D LAUNCHER_DEFAULT_SPIFFS_THRESHOLD=0x2F0000
-	-DROTATION=3
-
-	-DUSE_ARDUINO_GFX=1
-	-D TFT_DATABUS_N=0             # Arduino_HWSPI
-	-D TFT_DISPLAY_DRIVER_N=1      # Arduino_ST7789
-	-DTFT_WIDTH=135
-	-DTFT_HEIGHT=240
-	-DTFT_CS=7
-	-DTFT_DC=4
-	-DTFT_RST=8
-	-DTFT_MOSI=5
-	-DTFT_SCLK=6
-	-DTFT_MISO=-1
-	-DTFT_BL=9
-
-	-D TFT_IPS=1
-	-D TFT_COL_OFS1=52
-	-D TFT_ROW_OFS1=40
-	-D TFT_COL_OFS2=53
-	-D TFT_ROW_OFS2=40
-
-	-DSDCARD_CS=13
-	-DSDCARD_SCK=15
-	-DSDCARD_MISO=2
-	-DSDCARD_MOSI=1
-
-	; No PMIC on DinMeter: battery is a plain ADC divider on GPIO10 (ratio 2.0,
-	; matching M5Unified's board table), read by mykeyboard.cpp's weak getBattery().
-	-DANALOG_BAT_PIN=10
-
-build_unflags =
-	-DBOARD_HAS_PSRAM
-
-lib_deps =
-	${env.lib_deps}
-	mathertel/RotaryEncoder @1.5.3
-
-lib_ignore =
-	SensorLib
-	XPowersLib
-
diff --git a/devices/m5stack/dinmeter/certification-and-compliance.md b/devices/m5stack/dinmeter/certification-and-compliance.md
deleted file mode 100644
index e9e020f..0000000
--- a/devices/m5stack/dinmeter/certification-and-compliance.md
+++ /dev/null
@@ -1,159 +0,0 @@
-# Certification and compliance — dinmeter
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-The DinMeter is granted in its own right. The M5StampS3A module it carries has a separate grant.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5DINMETER` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
-**Supporting / related grants:** `2AN3WM5STAMPS3A`.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5DINMETER`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2412-2462 MHz Original Equipment 2024-07-23** |
-| Application purpose | Final Action Date 2412-2462 MHz Original Equipment 2024-07-23 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5DINMETER` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 2,123,431 | `b5aac335a6631663…` |
-| `ID-Label-Location-Info-FCC-ID-Label.pdf` | 357,530 | `87bc3655794390cc…` |
-| `Internal-Photos-Internal-Photos.pdf` | 3,674,683 | `7e0be459cbbf21a4…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE.pdf` | 126,464 | `aeb323a16a2ad99c…` |
-| `Test-Report-Antenna-Specification.pdf` | 822,846 | `0728acb7f328e39c…` |
-| `Users-Manual-User-Manual.pdf` | 2,021,122 | `b472ab81821318a6…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5DINMETER/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5DINMETER/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
-### `2AN3WM5STAMPS3A`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2402-2480 MHz Original Equipment 2025-02-13** |
-| Application purpose | Final Action Date 2402-2480 MHz Original Equipment 2025-02-13 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11) |
-| Test firm | Dongguan Yaxu (AiT) Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 17 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5STAMPS3A` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 2,142,184 | `6910fdc8e5f46913…` |
-| `ID-Label-Location-Info-label-and-location.pdf` | 69,357 | `60d9ccb36cc10e2a…` |
-| `Internal-Photos-Internal-Photos.pdf` | 2,778,287 | `e6512283b0e419c2…` |
-| `RF-Exposure-Info-FCC-RF-Exposure-MPE-20cm-.pdf` | 176,710 | `db49d95ade5911cc…` |
-| `Test-Report-AiTDG-241205002W1-Test-Report-BLE.pdf` | 959,274 | `027dd133c4ac00b6…` |
-| `Users-Manual-User-Manual.pdf` | 2,308,121 | `e9056d899bdd6cda…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5STAMPS3A/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5STAMPS3A/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/dinmeter/commands.md b/devices/m5stack/dinmeter/commands.md
deleted file mode 100644
index beff829..0000000
--- a/devices/m5stack/dinmeter/commands.md
+++ /dev/null
@@ -1,233 +0,0 @@
-# DinMeter — command ledger
-
-Every consequential command from this research pass, with status. Shell `bash 5.x` on NixOS,
-`curl 8.x`, `python3 3.14.7`, `git`/`gh` present, 2026-09-04.
-
-Status vocabulary: `executed-success` · `executed-failed` · `reported-working` · `inferred` ·
-`not-tested`.
-
----
-
-## 1. Environment — what was missing, and the way round it
-
-```bash
-which pdftotext pdfinfo qpdf mutool pdfimages     # executed-failed: none present
-python3 -c "import pypdf"                          # executed-failed: ModuleNotFoundError
-python3 -m pip --version                           # executed-failed: No module named pip
-uv venv /tmp/opencode/.pdfvenv                     # executed-success
-uv pip install --python /tmp/opencode/.pdfvenv/bin/python pdfminer.six pymupdf   # executed-success (install)
-/tmp/opencode/.pdfvenv/bin/python -c "import fitz" # executed-failed: ImportError: libstdc++.so.6: cannot open shared object file
-/tmp/opencode/.pdfvenv/bin/python -c "import pdfminer; print(pdfminer.__version__)"  # executed-success: 20260107
-```
-
-**Diagnosis:** `pymupdf`'s compiled extension needs a `libstdc++` that is not on this NixOS host.
-`pdfminer.six` is pure Python and works. Corrected approach: use `pdfminer.six` and emit
-poppler-compatible bbox XML so the repository's existing Altium tooling conventions still apply.
-
-Also absent: `file`, `xxd`. Use `curl -w '%{content_type}'` and a Python magic-byte check instead.
-
-## 2. Vendor documentation
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-
-# negative control -- the obvious URL is wrong
-curl -sS -A "$UA" -o /dev/null -w '%{http_code}\n' -L https://docs.m5stack.com/en/core/DinMeter
-# executed-success -> 404
-
-curl -sS -A "$UA" -o docs-en-core-M5DinMeter.html   -L https://docs.m5stack.com/en/core/M5DinMeter    # 200, 139501 B
-curl -sS -A "$UA" -o docs-en-core-DinMeter_v1.1.html -L https://docs.m5stack.com/en/core/DinMeter_v1.1 # 200, 142090 B
-# executed-success both
-```
-
-Extraction: the pages are Vue/Nuxt shells but the content **is** in the served HTML under
-`id="document"`. Naive tag-stripping loses it; slicing from that anchor first works.
-
-```bash
-curl -sS -A "$UA" -o sitemap.xml -L https://docs.m5stack.com/sitemap.xml   # executed-success: 200, 499000 B, 5703 <loc>
-```
-**This is the only reliable way to enumerate M5Stack product pages** — `/en/products` is a JS
-shell with no product links in its HTML.
-
-## 3. Artifact acquisition
-
-```bash
-dl(){ code=$(curl -sS -A "$UA" -L -o "$2" -w '%{http_code}' "$1"); printf '%s %s %s\n' "$code" "$(stat -c%s "$2")" "$2"; }
-
-dl 'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/500/DIN_Meter_v1.0.pdf' K134_DIN_Meter_v1.0-schematic.pdf
-dl 'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf' K134-V11-schematic.pdf
-dl 'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2.pdf' Sch_M5StampS3_v0.2.pdf
-dl 'https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf' Sch_StampS3_v0.3.3-StampS3A.pdf
-# ... 19 files total, all executed-success, all HTTP 200
-sha256sum *.pdf   # executed-success
-```
-
-**The finding that came out of hashing rather than reading:**
-
-```
-03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070  K134_DIN_Meter_v1.0-schematic.pdf
-03ec335396e4f527119f89f697fca9887505dc1b28077871b2fb361ba6e4c070  K134-V11-schematic.pdf
-```
-Two URLs, two filenames, **one file**. Same again for `Stamp-S3.stl` / `Stamp-S3A.stl` and
-`DinMeter.stl` / `DinMeter_v1.1.stl`.
-
-Magic-byte validation (no `file(1)` on this host):
-```bash
-python3 -c "
-import sys
-for f in sys.argv[1:]:
-    print(open(f,'rb').read(5), f)" *.pdf     # executed-success: b'%PDF-' for all
-```
-
-## 4. Schematic parsing
-
-```bash
-# emit poppler `pdftotext -bbox`-compatible XML from pdfminer.six
-/tmp/opencode/.pdfvenv/bin/python /tmp/opencode/pdf_bbox.py K134_DIN_Meter_v1.0-schematic.pdf \
-  > K134_DIN_Meter_v1.0-schematic.bbox.xml
-# executed-success: 900 <word> elements, 1 page
-
-python3 artifacts/schematic/parse_dinmeter_sch.py K134_DIN_Meter_v1.0-schematic.bbox.xml
-# executed-success: words=900 plain=553 CO=85 PI=238 NL=25
-```
-
-### The failure worth preserving
-
-The **first** parse produced designators like `PPIIJJ110011` and `LP3218DT1GPPIIJJ110011`.
-
-**Diagnosis:** Altium's PDF publisher draws the invisible marker layer **twice** at identical
-coordinates. The word-grouping step interleaved the two copies character by character, yielding
-*human-legible but wrong* text — the most dangerous kind of extraction failure, because it does
-not look broken.
-
-**Fix:** deduplicate glyphs on rounded `(x0, y0, x1, y1, char)` before grouping. `executed-success`
-after the fix; the pre-fix output was discarded, not published.
-
-### Proving absence
-
-```bash
-python3 -c "
-from pdfminer.high_level import extract_text; import re
-t=re.sub(r'\s+','',extract_text('K134_DIN_Meter_v1.0-schematic.pdf'))
-def dbl(s): return ''.join(c*2 for c in s)
-for p in ['COS1','COR20','COY1','COQ2','COS4','COU1','COM1']:
-    print(p,'single=',t.count(p),'doubled=',t.count(dbl(p)))"
-# executed-success:
-#   COS1 0/0   COR20 0/0   COY1 0/0   COQ2 0/0
-#   COS4 1/0   COU1 1/0    COM1 1/0
-```
-A **complete** census, not a search for expected parts. Result recorded in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) §2.
-
-## 5. GitHub (authenticated — `api.github.com` limits per identity, no UA helps)
-
-```bash
-T="$(gh auth token)"
-curl -sS -H "Authorization: Bearer $T" -G \
-  --data-urlencode 'q=DinMeter in:name,description,readme' --data 'per_page=50' \
-  https://api.github.com/search/repositories                       # executed-success: 19
-curl -sS -H "Authorization: Bearer $T" -G \
-  --data-urlencode 'q=repo:esphome/esphome dinmeter' \
-  https://api.github.com/search/code                               # executed-success: 0
-
-gh api repos/m5stack/M5DinMeter                                    # executed-success
-curl -sSL -H "Authorization: Bearer $T" \
-  -o M5DinMeter-8ccbad72….tar.gz \
-  https://api.github.com/repos/m5stack/M5DinMeter/tarball/8ccbad7297beb82a140f812e5606e060d8a5e0dc
-# executed-success: 8532 B, sha256 de47c4109635870506bb7a02040db496f82e5bbb22a5b1befe600a3985eb0f02
-
-curl -sSL -o dinmeter-board_peripherals.yaml \
-  https://raw.githubusercontent.com/espressif/esp-board-manager/main/m5stack_boards/m5stack_dinmeter/board_peripherals.yaml
-# executed-success: 5014 B
-```
-
-## 6. Shop / pricing
-
-```bash
-curl -sS -A "$UA" -L https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a.js
-# executed-success -> K134-V11, price 2450 (USD 24.50), available true, created 2026-01-30
-curl -sS -A "$UA" -L https://shop.m5stack.com/products/m5stack-din-meter-with-m5stamps3.js
-# executed-failed: HTTP 404 -- wrong slug guess
-curl -sS -A "$UA" -L https://shop.m5stack.com/products/m5stack-din-meter-w-m5stamps3.js
-# executed-success -> "[EOL] M5Stack Din Meter w/ M5StampS3", K134, 2450, available FALSE
-```
-The working slug was recovered from a link in `bmorcelli/Launcher`'s README, not from M5Stack.
-
-Suggest-endpoint enumeration (note the brackets **must** be percent-encoded — a raw `[` makes
-curl try to parse a range):
-```bash
-curl -sS -A "$UA" -L 'https://shop.m5stack.com/search/suggest.json?q=din+meter&resources%5Btype%5D=product&resources%5Blimit%5D=10'
-# executed-success
-curl -sS -A "$UA" -L 'https://shop.m5stack.com/search/suggest.json?q=din meter&resources[type]=product'
-# executed-failed: curl: (3) bad range in position 70
-```
-
-## 7. Reddit
-
-```bash
-curl -sS -A 'WhatsApp/2.23.20.0' -G \
-  --data-urlencode 'q=DinMeter' --data 'limit=50&sort=relevance&t=all&raw_json=1' \
-  https://old.reddit.com/search.json          # executed-success: 200, 838509 B
-```
-`www.reddit.com` returns 403 to automated clients; `old.reddit.com` with the WhatsApp
-link-preview UA returns 200. Consistent with this repository's existing access table.
-
-## 8. M5Stack forum — both attempts failed
-
-```bash
-curl -sS -A "$UA" -L 'https://community.m5stack.com/api/search?term=dinmeter&in=titlesposts'
-# executed-failed: HTTP 401
-# {"status":{"code":"not-authorised","message":"A valid login session was not found. Please log in and try again."}}
-
-curl -sS -A "$UA" -L 'https://community.m5stack.com/search?term=dinmeter&in=titlesposts'
-# executed-success (HTTP 200, 16986 B) but useless: NodeBB JS shell, no results in the HTML
-```
-Recorded rather than worked around. Rotating User-Agents would not help — this is
-authentication, not bot-blocking, and per the repository's retrieval policy UA substitution must
-not be used to bypass access controls.
-
-## 9. Repository hygiene
-
-```bash
-find vendors/m5stack/README.md -mmin -30            # executed-success: empty -> safe to append
-find components/awinic/aw35122/README.md -mmin -30  # executed-success: empty -> safe to append a Used By row
-git status --porcelain                              # executed-success (read-only)
-```
-No state-changing git command was run at any point in this pass.
-
----
-
-## 10. Commands for the reader — **none of these were run here**
-
-Everything below is `not-tested` on the device and is labelled so.
-
-```bash
-# Back up the factory image BEFORE overwriting it. There is no vendor-published binary.
-esptool.py --chip esp32s3 -p /dev/ttyACM0 -b 460800 read_flash 0 0x800000 dinmeter-factory-backup.bin
-# not-tested
-
-# Identify the chip and flash size
-esptool.py --chip esp32s3 -p /dev/ttyACM0 flash_id            # not-tested
-
-# Restore
-esptool.py --chip esp32s3 -p /dev/ttyACM0 write_flash 0 dinmeter-factory-backup.bin   # not-tested
-
-# Arduino
-arduino-cli board listall | grep -i din      # not-tested -- run this to LEARN the FQBN;
-                                             # `m5stack:esp32:m5stack_dinmeter` is a GUESS
-arduino-cli compile -b <fqbn> sketch/        # not-tested
-arduino-cli upload -b <fqbn> -p /dev/ttyACM0 sketch/          # not-tested
-
-# ESP-IDF
-idf.py set-target esp32s3 && idf.py build && idf.py -p /dev/ttyACM0 flash monitor   # not-tested
-
-# Download mode (hardware step, not a command)
-#   hold the G0 button on the Stamp module, apply power, release G0.   reported-working (vendor)
-```
-
-## 11. Reusable scripts checked in
-
-| Script | Purpose | Status |
-|---|---|---|
-| [`artifacts/schematic/parse_dinmeter_sch.py`](artifacts/schematic/parse_dinmeter_sch.py) | Parse the Altium `CO`/`PI`/`NL` marker layer from bbox XML: designator census, net labels, pin→net mapping | `executed-success` |
-| [`acquisition/README.md`](acquisition/README.md) | Clean-clone reacquisition, in execution order | commands `not-tested` from a clean clone |
diff --git a/devices/m5stack/dinmeter/community.md b/devices/m5stack/dinmeter/community.md
deleted file mode 100644
index 7525474..0000000
--- a/devices/m5stack/dinmeter/community.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# DinMeter — community
-
-This device's community coverage is documented in full at
-**[`projects-and-community.md`](projects-and-community.md)**, which is the single catalogue of
-repositories, firmware ports, forum attempts and social evidence, with each item labelled by
-evidence type (demonstrable project · reproduced documentation · firsthand report · hearsay ·
-marketing).
-
-This page exists so that the skill's standard filename resolves, and to state the headline
-without making the reader open another file.
-
----
-
-## The one-paragraph summary
-
-**There is very little public community around the DinMeter, and that is a measured finding
-rather than a search failure.** On 2026-09-04 a GitHub repository search
-(`DinMeter in:name,description,readme`, 50 results/page) returned **19 repositories**, of which
-**13** genuinely target the device; `old.reddit.com/search.json` across four query forms and
-~200 inspected results returned **exactly one** relevant post — M5Stack's own launch
-announcement, with one comment; and **ESPHome, Tasmota and Meshtastic each returned zero**
-code-search hits. M5Stack's own forum could **not** be enumerated (its search API returns HTTP
-401 and its HTML search page is a JavaScript shell), so it is a *blocked* source rather than an
-empty one, and it is the largest single gap in this record.
-
-## The three things worth knowing
-
-1. **`bmorcelli/Launcher` (★2054, MIT) is the only substantial third-party firmware.** The
-   DinMeter is a first-class board target in its release CI and ships as
-   `Launcher-m5stack-dinmeter.bin` via M5Burner. Its board file is also an *independent*
-   corroboration of the display pins, the GRAM offsets, the battery-divider ratio and the
-   absence of PSRAM — from an author with no reason to copy M5Stack's table wrongly.
-2. **The projects that exist are single-purpose instruments** — a ceramic-kiln PID controller, a
-   power-tool battery analyser, a heater controller, a TOTP authenticator, a BLE volume knob.
-   Nine of thirteen are one-person tools. That is the product being used exactly as its
-   panel-mount, 6–36 V design intends.
-3. **Do not expect home-automation firmware.** No ESPHome, no Tasmota, no Meshtastic. If you want
-   Home Assistant integration you will write it, or use M5Stack's own UiFlow2 route.
-
-## Prevalence caveat
-
-"Almost no community" describes *public, indexed* activity on GitHub and Reddit on 2026-09-04.
-The vendor forum was inaccessible, and Chinese-language platforms (Bilibili, CSDN, Taobao Q&A)
-and video sources were **declared exclusions** and not searched. Do not read this as "nobody uses
-it" — read it as "there is no public scene to lean on when you get stuck."
-
-→ **[`projects-and-community.md`](projects-and-community.md)** for the full catalogue, the
-per-project evidence types, the exact queries, and the negative results.
diff --git a/devices/m5stack/dinmeter/comparisons-and-recommendations.md b/devices/m5stack/dinmeter/comparisons-and-recommendations.md
deleted file mode 100644
index acec625..0000000
--- a/devices/m5stack/dinmeter/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,219 +0,0 @@
-# DinMeter — comparisons and recommendations
-
-**Dated 2026-09-04.** Prices are the observations in [`market-and-pricing.md`](market-and-pricing.md).
-Applies to the DinMeter family (K134 / K134-V11); where the two differ it is noted.
-
-**Scope discipline.** Nothing below is called "equivalent" unless the interfaces, electrical
-behaviour and software requirements actually align for the stated workload. Where they do not,
-it says *partial substitute* and names what is missing. No benchmark comparison is offered,
-because **no device in this comparison was benchmarked here** — see
-[`performance.md`](performance.md).
-
----
-
-## 1. The one-sentence answer
-
-> Buy a DinMeter if you have a **1/32 DIN panel aperture** or a **12/24 V supply and no 5 V**.
-> If you have neither, buy something else — as a knob-with-a-screen it is beaten on almost every
-> axis by devices costing similar money.
-
-Those two attributes are not incidental features; they are the entire reason the product exists,
-and no competitor in this comparison has either.
-
----
-
-## 2. Versus the Waveshare ESP32-S3-Knob-Touch-LCD-1.8
-
-The closest thing to a like-for-like "ESP32 knob" competitor documented in this repository:
-[`devices/waveshare/esp32-s3-knob-touch-lcd-1.8/`](../../waveshare/esp32-s3-knob-touch-lcd-1.8/README.md).
-
-| | **M5Stack DinMeter** (K134-V11) | **Waveshare ESP32-S3-Knob-Touch-LCD-1.8** (31623) |
-|---|---|---|
-| Price (2026-09-04) | **USD 24.50** | see the Waveshare record's market section |
-| Form factor | 53 × 30 × 32 mm rectangular, **1/32 DIN panel cutout 45 × 22.5 mm** | 66 mm diameter × 22 mm, **CNC-machined metal**, desktop puck |
-| Main MCU | ESP32-S3**FN8** — 8 MB flash, **no PSRAM** | ESP32-S3**R8** — **8 MB PSRAM** + 16 MB external W25Q128 flash |
-| Second MCU | none | **ESP32-U4WDH** — a whole second SoC, the board's only source of **Bluetooth Classic (BR/EDR)** |
-| Display | 1.14 in **135 × 240** SPI, ST7789V2/P3 | 1.8 in **360 × 360** round QSPI, ST77916/SH8601 |
-| Touch | **none** | CST816D capacitive |
-| Knob | **detented incremental quadrature encoder + push** | **two** Alps SSCM110100 *directional switches* — not conventional encoders, and each is readable only by its own MCU |
-| Audio out | magnetic buzzer only | PCM5100A stereo DAC → 3.5 mm line out |
-| Audio in | none | PDM microphone |
-| Haptics | none | DRV2605L + LRA |
-| Storage | none | microSD, 4-bit SDMMC |
-| **DC input** | **6 – 36 V** on a screw terminal | **5 V USB only** |
-| Battery | 1S Li-ion socket + TP4057 charger + power-path + boost, latched off at **38.4 µA** | optional 102035 LiPo; charger/power-path **not identified** in that record |
-| RTC | **BM8563, battery-backed, wakes the board from off** | **none** |
-| Expansion | **2 × Grove HY2.0** (I²C + GPIO), 5 V @ 220 mA each | 2 × PH1.27 10-pin headers, **exact pinout not published** |
-| USB | native USB-C on the module | USB-C where **plug orientation selects which MCU you talk to** |
-| Enclosure | plastic | **CNC metal** |
-| ESPHome | **no** | **yes** (that record has a dedicated ESPHome confirmation document) |
-| Community | ~13 GitHub projects, 1 Reddit post | materially larger |
-
-### What that table actually means
-
-**The Waveshare is a better knob. The DinMeter is a better instrument.**
-
-Choose the Waveshare when the device sits on a desk and the *interaction* is the point: 360 × 360
-round display, touch, haptics, audio in and out, Bluetooth Classic media control. It has 8 MB of
-PSRAM, so LVGL with a full framebuffer is comfortable. It looks and feels like a product.
-
-Choose the DinMeter when the device goes **inside something**: a panel, a cabinet, a machine.
-Everything the Waveshare adds is irrelevant there, and three things the DinMeter has are not
-available at any price on the Waveshare — the DIN cutout, the 6–36 V input, and a
-battery-backed RTC that can power the board back on.
-
-**They are not substitutes.** Do not treat "ESP32-S3 + knob + LCD" as a category. A Waveshare
-knob cannot be panel-mounted into a 1/32 DIN aperture and cannot be run from a 24 V rail without
-an external converter; a DinMeter cannot play Bluetooth audio, has no touch, and has 1/12th the
-pixel count.
-
-**One shared caution.** Both records carry an unresolved display-controller identity: the
-Waveshare's panel is marketed ST77916 but driven by an SH8601 compatibility driver; the DinMeter
-v1.1's ST7789P3 has **no published datasheet at all**. Neither vendor is rigorous here.
-
----
-
-## 3. Versus the M5Stack Dial (K130-V11)
-
-The DinMeter's own sibling, and the more instructive comparison — they share a software path.
-
-| | **DinMeter** (K134-V11) | **M5Dial v1.1** (K130-V11) |
-|---|---|---|
-| Price (2026-09-04) | **USD 24.50** | **USD 34.90** |
-| Shape | rectangular, panel-mount | round puck |
-| Display | 1.14 in 135 × 240 | 1.28 in 240 × 240 round |
-| Touch | none | **yes (FT3267)** |
-| Knob | encoder + push | encoder + push |
-| DC input | **6 – 36 V** | 5 V |
-| RTC | BM8563 | BM8563 |
-| Buzzer | yes | yes |
-| Grove ports | PORT.A + PORT.B | PORT.A + PORT.B |
-| Core module | Stamp-S3A | Stamp-S3 family |
-| M5Unified enum | `board_M5DinMeter` | `board_M5Dial` |
-
-**They are the same board in two shells.** M5Unified handles them in the *same switch cases* for
-button reading, buzzer configuration, power hold and I²C
-(`M5Unified.cpp:96, 159, 246, 282, 2398, 2921, 3502`), and the DinMeter's Arduino library is a
-literal copy of the M5Dial's — its header guard is still `#define M5DIAL_H` and its pin macros
-are still named `DIAL_ENCODER_PIN_A/B`.
-
-**So the decision is purely mechanical and electrical:**
-
-- Need a **round** face, a **touchscreen**, or 240 × 240? → M5Dial, and pay USD 10.40 more.
-- Need a **panel aperture** or **12/24 V**? → DinMeter. The Dial cannot do either.
-- Neither? → DinMeter, because it is cheaper and the software is identical.
-
----
-
-## 4. Versus rolling your own (encoder + ESP32 + display)
-
-The honest competitor for most hobby use.
-
-| | **DinMeter** (USD 24.50) | **DIY: ESP32-S3 board + EC11 + 1.14 in ST7789** |
-|---|---|---|
-| Parts cost | 24.50, one SKU | ≈ 6–12 for a generic S3 board + ≈ 1 encoder + ≈ 3–5 display ≈ **10–18** |
-| Time | zero | a weekend, plus a case |
-| 6–36 V input | included | + a 24 V buck module (≈ 1–3) and the board space for it |
-| Li-ion charge + power path + boost + latch | included, and the latch design is genuinely good | + a charger board, and you will not get 38.4 µA standby |
-| RTC + crystal + battery backup | included | + a DS3231/PCF8563 module |
-| Enclosure to a **standard panel cutout** | included | this is the part you cannot buy |
-| Certification / EMC | M5Stack's problem | yours |
-| Software | M5Unified + Espressif board def + vendor examples, all working | you write the board file |
-| Reproducibility across units | one SKU | you own the BOM forever |
-
-**Build it yourself when** it is a one-off on a bench, cost dominates, or you need something the
-DinMeter cannot do (PSRAM, a bigger screen, more GPIOs, a camera).
-
-**Buy the DinMeter when** it goes into a panel, when there will be more than one, when someone
-other than you will maintain it, or when you want to be doing application work by lunchtime. The
-enclosure and the cutout are the part that is genuinely hard to reproduce, and they are most of
-what you are paying for.
-
----
-
-## 5. Alternatives by tier (2026-09-04, global pricing, hobbyist/prosumer)
-
-| Tier | Pick | Why | Watch out for |
-|---|---|---|---|
-| **Cheapest working knob UI** | Generic ESP32-S3 + EC11 + 1.14 in ST7789 | ≈ USD 10–18 | No case, no cutout, no RTC, no wide input |
-| **Panel-mount instrument, 12/24 V** | **DinMeter v1.1**, USD 24.50 | The only product in this list that fits a 1/32 DIN aperture and takes 36 V | No PSRAM, no touch, 0–40 °C, ~8 free GPIOs |
-| **Desktop knob, richest UI** | Waveshace ESP32-S3-Knob-Touch-LCD-1.8 | 360 × 360 round + touch + haptics + audio + PSRAM + Bluetooth Classic | Dual-MCU complexity; USB orientation selects the MCU; 5 V only |
-| **Round M5 knob with touch** | M5Dial v1.1, USD 34.90 | Same software as DinMeter, adds touch and a round 240 × 240 | +USD 10.40, 5 V only, no panel cutout |
-| **Battery-first Stamp project** | Bare **Stamp-S3A**, USD 7.50 | 6.84 µA sleep on `VIN_5V`; you supply the rest | You are designing a board; budget 0.6 A on 3.3 V, not 1 A |
-| **Home Assistant, no code** | Not this device | ESPHome supports neither DinMeter nor M5Dial out of the box | See [`projects-and-community.md`](projects-and-community.md) §1 |
-| **Industrial DIN-rail PLC-ish** | M5Stack StamPLC, USD 42.90 | DIN-*rail* (not panel-cutout), relays, CAN, RS485 | Different problem entirely — rail-mounted controller, not a panel head |
-
----
-
-## 6. The DIN question, stated properly, because it is the whole point
-
-**"DIN" in this product's name means the panel-cutout standard, not the rail.** That distinction
-costs people money.
-
-- **1/32 DIN** (DIN 43700) specifies a panel aperture of **45 × 22.5 mm**. That aperture exists,
-  already cut, in an enormous installed base of instrument panels, PLC cabinet doors, machine
-  consoles and process racks — because it is what a generation of temperature controllers and
-  panel meters used. The DinMeter drops into one.
-- **DIN rail** (TS-35) is the 35 mm hat-rail inside the cabinet. The DinMeter does **not** clip
-  to it. M5Stack's own DIN-rail product is the StamPLC.
-
-If you are retrofitting a machine and there is a dead Omron/Autonics/Fuji panel meter in the
-front door, the DinMeter is a straight swap into that hole, powered from the 24 V that was
-already feeding the old unit, and you can be showing a modern UI with Wi-Fi in it the same
-afternoon. **That is the use case, and nothing else in this comparison can do it.**
-
-Conversely: if you do not have that hole, you are paying for an enclosure shape you will not use,
-and one of the cheaper options above is a better buy.
-
-Mechanical detail: [`features/din-mounting-and-mechanical.md`](features/din-mounting-and-mechanical.md).
-
----
-
-## 7. Who should *not* buy it
-
-- Anyone who needs **PSRAM** — a large LVGL framebuffer, a camera, a heavy TLS workload. There
-  is none, on either revision.
-- Anyone who needs a **touchscreen**, or more than 135 × 240 pixels.
-- Anyone who needs **more than ~8 free GPIOs** — four of the free ones are the two Grove ports.
-- Anyone deploying outside **0 – 40 °C**. An unheated cabinet in winter, or a sealed panel in
-  summer sun, is outside spec.
-- Anyone who wants **ESPHome/Tasmota/Meshtastic** to work today. None of them support it.
-- **First-time ESP32 users.** The GPIO46 power latch will catch you, and the failure looks like
-  a hardware fault.
-
----
-
-## 8. Clones
-
-**None found.** No AliExpress or marketplace clone of the DinMeter was located on 2026-09-04.
-That is a **negative search result**, not proof of absence — see
-[`research-log.md`](research-log.md) for the queries run. The likely reason is that the value is
-in the enclosure and the DIN fit rather than in a copyable PCB, and the volumes are small.
-
----
-
-## Related
-
-[`market-and-pricing.md`](market-and-pricing.md) · [`performance.md`](performance.md) ·
-[`projects-and-community.md`](projects-and-community.md) ·
-[`../dinmeter-v1.1/stamp-s3-to-s3a-delta.md`](../dinmeter-v1.1/stamp-s3-to-s3a-delta.md) ·
-[`devices/waveshare/esp32-s3-knob-touch-lcd-1.8/`](../../waveshare/esp32-s3-knob-touch-lcd-1.8/README.md)
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered.
-
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — a buyer-oriented survey of every device record in the repository. The DinMeter
-  sits outside its four shopping groups (it is a panel-mount instrument, not a
-  handheld) and is carried in the completeness section, with the v1.0/v1.1
-  byte-identical-assets finding preserved as the headline.
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — the Stamp-S3 → Stamp-S3A change documented in this tree is used there as the
-  worked example that **board sleep current is dominated by the power tree, not the
-  SoC**: 310.89 µA → 6.84 µA on `VIN_5V`, bought by swapping a µPOL module for a
-  discrete buck and moving the WS2812 onto a switched rail — and paid for with the
-  RGB LED's always-on supply.
diff --git a/devices/m5stack/dinmeter/compatibility-and-status.md b/devices/m5stack/dinmeter/compatibility-and-status.md
deleted file mode 100644
index ca25f30..0000000
--- a/devices/m5stack/dinmeter/compatibility-and-status.md
+++ /dev/null
@@ -1,96 +0,0 @@
-# DinMeter — compatibility and status
-
-Keyed by hardware revision and software version. **No entry in this document is a firsthand
-hardware test by this research pass** — none was possible. Every row states whose evidence it is.
-
-Status vocabulary: **works** · **partial** · **fails** · **untested** · **conflicting**.
-
----
-
-## 1. Framework and library versions
-
-| Software | Version | K134 (Stamp-S3) | K134-V11 (Stamp-S3A) | Evidence |
-|---|---|---|---|---|
-| `M5DinMeter` | **1.0.0** (2024-03-07, the only release) | works | works | vendor-published; **no v1.1-specific changes** in the library, HEAD `8ccbad72…` still `version=1.0.0` |
-| `M5Unified` | ≥ 0.1.13 declared; 0.2.21 current | works | works **except the RGB LED** | source read at master `8530f537…` |
-| `M5GFX` | 0.2.28 current | works | works | via M5Unified |
-| `LovyanGFX` | **1.1.12** (pinned by M5Stack's own factory project) | works | works | `M5DinMeter-UserDemo/platformio.ini` |
-| `SmoothUIToolKit` | **1.0.1** (pinned by the same) | works | works | same |
-| `mathertel/RotaryEncoder` | **1.5.3** | works | works | `bmorcelli/Launcher` board file |
-| PlatformIO `espressif32` | **6.3.1** (pinned by M5Stack) | works | works | same |
-| Arduino M5Stack board package | **2.1.1** (named in every vendor example header) | works | works | vendor examples, all dated 2024-03-07 |
-| ESP-IDF + `esp-board-manager` | HEAD `2beb9b22…` (2026-09-03) | works | untested | Espressif board definition exists and is complete |
-| UiFlow2 / `uiflow-micropython` | current | works | works | DinMeter in both CI configs |
-| MicroPython (vanilla) | any | **not supported** | not supported | no board port upstream |
-| `mattytrentini/chipboard` MicroPython | — | untested | untested | board YAML exists, not evaluated |
-
-## 2. The one known incompatibility
-
-| Item | Revision | Status | Detail |
-|---|---|---|---|
-| **RGB LED via stock M5Unified** | **K134-V11 only** | **fails (predicted)** | Stamp-S3A moves the WS2812B's supply onto the switched `BL_3V3` rail, gated by GPIO38. M5Unified at master `8530f537…` has no GPIO38 enable step for any board, no `board_M5StampS3A` and no v1.1 board enum, so a v1.1 unit takes the v1.0 code path and the LED stays dark. **`inferred` — not reproduced on hardware.** Workaround: `pinMode(38,OUTPUT); digitalWrite(38,HIGH);` before driving GPIO21 |
-
-Everything else in the API surface is unchanged between revisions — see
-[`../dinmeter-v1.1/stamp-s3-to-s3a-delta.md`](../dinmeter-v1.1/stamp-s3-to-s3a-delta.md) §8 for
-the pin-by-pin verdict table.
-
-## 3. Third-party firmware
-
-| Project | Version/commit | Status | Evidence type |
-|---|---|---|---|
-| `bmorcelli/Launcher` | `main`, board `m5stack-dinmeter`, last push 2026-09-04 | **works** — in the release CI matrix and distributed as `Launcher-m5stack-dinmeter.bin` (MD5 `bccbefef5284357a2a7c3c7cc196fd98`) via M5Burner | demonstrable project. ⚠ **The project's own README contradicts itself**, listing the port once as `[x]` and once as `[ ] (Beta)`. The CI matrix and the MD5 map both say it ships |
-| `viniciusbo/m5-palnagotchi` | last push 2026-01-28 | untested here; `palnagotchi/ui.h` references M5DinMeter | demonstrable project |
-| `pr3y/Bruce` (upstream) | — | **no DinMeter support** — `repo:pr3y/Bruce dinmeter` → 0 results. Easy to confuse with Launcher | negative result |
-| ESPHome / Tasmota / Meshtastic | any | **no support** — 0 code-search hits in each | negative result |
-
-## 4. Peripherals reported working
-
-| Peripheral | On | Status | Evidence |
-|---|---|---|---|
-| Grove I²C units on PORT.A | both | works | vendor design intent + `Ex_I2C` in the library |
-| **SD card bit-banged across both Grove ports** | both | **works** | `bmorcelli/Launcher` ships it: `SDCARD_CS=13, SCK=15, MISO=2, MOSI=1`. Consumes all four free Grove pins |
-| 250 mA·h bundled Li-ion cell | both | works | shipped in the box |
-| Larger 1S Li-ion cells | both | untested | charger is 100 mA fixed; larger cells simply charge slower |
-
-## 5. Known-bad and cautionary combinations
-
-| Combination | Status | Why |
-|---|---|---|
-| Backlight and buzzer on the **same LEDC timer** | **fails** (visibly) | Channels on one timer share a frequency; retuning the buzzer changes backlight PWM. Espressif's board definition separates them (timer 0 / timer 1) |
-| Pin-based JTAG + encoder | **fails** | GPIO39–42 are all occupied. Use USB-Serial-JTAG |
-| Repurposing GPIO14 or GPIO39 | **risky** | The vendor PinMap implies they are free; the schematic shows 10 kΩ + 1N4148WT networks tied into the power latch. Circuit not fully traced |
-| External pull-up on GPIO46 | **fails to boot** | Strapping pin, pulled down by design on the Stamp module |
-| Enabling PSRAM in a build | **fails** | There is none, on either revision |
-| Battery operation without setting GPIO46 high | **fails** | The board switches itself off. The single most common first-time failure |
-| `esp-board-manager` PCNT with `en_step_notify_*` set | **build fails** | Those fields need `SOC_PCNT_SUPPORT_STEP_NOTIFY`, which the ESP32-S3 lacks. Espressif's own board file documents this |
-| 36 V continuous on the DC terminal | **cautionary** | `C24` is rated 35 V — 103 % at the ceiling |
-| 5 V-max peripheral on a Grove port | **cautionary** | The boost's divider computes to ≈ 5.38 V against a "5 V" spec |
-
-## 6. Conflicting reports
-
-| Item | Source A | Source B | Resolution |
-|---|---|---|---|
-| Backlight PWM frequency | M5Stack's own factory firmware: **200 Hz**, LEDC channel 7 | Espressif `esp-board-manager`: **5 kHz**, channel 0 / timer 0 | Both work. 200 Hz can be visible as flicker in person and on video. **Unresolved**; prefer 5 kHz |
-| Grove wire colours | vendor PinMap: yellow = G13 | schematic + M5Unified: yellow = G15 (SCL) | **Unresolved.** No practical impact via M5Unified/UiFlow2. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §1 |
-| Launcher DinMeter port maturity | README `[x] Port to M5-DinMeter` | README `[ ] (Beta) M5-DinMeter port` | The CI matrix builds it and the binary ships. Treat as **working, self-described as beta** |
-| Stamp-S3A DC-DC | product page: `MUN3CAD01-SC` | schematic v0.3.3: an unidentified 8-ball buck + external inductor, `IOUT: 0~0.6A` | **Schematic wins.** The spec row was carried over unedited |
-| Stamp-S3A length | spec table: 26.0 mm | STL byte-identical to Stamp-S3's, no new footprint | **Unresolved.** Probably a doc error; measure a real part |
-
-## 7. What is untested, and it is nearly everything
-
-| Category | Status |
-|---|---|
-| Any firmware built here | **none** |
-| Any firmware flashed here | **none** |
-| Any electrical measurement | **none** |
-| Any RF measurement | **none** |
-| Any thermal measurement | **none** |
-| Any timing/throughput measurement | **none** |
-| Any teardown / visual chip-marking confirmation | **none** |
-
-**This record is a documentary and source-code analysis.** It is thorough about what can be
-established from published documents, schematics and code, and it is worth exactly nothing as
-evidence about how a physical unit behaves. Every claim is labelled accordingly.
-
-If you have hardware, the five highest-value tests are listed in
-[`coverage.md`](coverage.md) §4.
diff --git a/devices/m5stack/dinmeter/coverage.md b/devices/m5stack/dinmeter/coverage.md
deleted file mode 100644
index dd305ba..0000000
--- a/devices/m5stack/dinmeter/coverage.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# DinMeter — feature coverage matrix
-
-Applies to K134 and K134-V11. **Zero claims in this record are hardware-tested** — no device was
-available. The "Hardware test" column is therefore uniformly `none`, stated plainly rather than
-left blank.
-
-Legend — Evidence: **O** official docs · **S** schematic · **F** framework/board-support source ·
-**C** community project. Build/Test: `none` = not attempted here.
-
----
-
-## 1. Advertised and fitted capabilities
-
-| Capability | Hardware | Official docs | Official example | Community example | Feature guide | Build test | Hardware test | Gap |
-|---|---|---|---|---|---|---|---|---|
-| **Rotary encoder** | encoder on `J5` → GPIO41/40 | O ✔ (PinMap) | ✔ `examples/Basic/encoder` | ✔ Launcher, KilnController, BLE knob | [rotary-encoder-and-buttons](features/rotary-encoder-and-buttons.md) | none | **none** | Encoder part number unpublished; detents/rev unknown |
-| **Encoder push-button / WAKE** | GPIO42 | O ✔ | ✔ `examples/Basic/button` | ✔ | [rotary-encoder-and-buttons](features/rotary-encoder-and-buttons.md) | none | **none** | — |
-| **Stamp `G0` button** | GPIO0 | O ✔ (download mode) | — | ✔ Launcher | [rotary-encoder-and-buttons](features/rotary-encoder-and-buttons.md) | none | **none** | — |
-| **Display** | ST7789V2/P3, GPIO4–8 | O ✔ | ✔ `examples/Basic/display` | ✔ Launcher, UserDemo | [display](features/display.md) | none | **none** | **ST7789P3 has no datasheet**; no measured frame rate |
-| **Backlight / dimming** | GPIO9 → `U6` AW35122FDR | O ✘ (not documented) | — | ✔ UserDemo (`Light_PWM`), esp-board-manager | [display](features/display.md) | none | **none** | ⚠ PWM freq conflict: 200 Hz (UserDemo) vs 5 kHz (Espressif) |
-| **RTC / timekeeping** | BM8563, GPIO11/12, 0x51 | O ✔ | ✔ `examples/Basic/rtc` (with NTP) | — | [rtc-and-timekeeping](features/rtc-and-timekeeping.md) | none | **none** | Datasheet is a derived document (stray `MAX1937`) |
-| **RTC alarm wake-from-off** | `INT` → power latch | O ✔ | ✔ `examples/Basic/wakeup` | — | [rtc-and-timekeeping](features/rtc-and-timekeeping.md) | none | **none** | — |
-| **Buzzer** | `LS1` via `Q5`, GPIO3 | O ✔ | ✔ `examples/Basic/buzzer` | — | [buzzer](features/buzzer.md) | none | **none** | Part number, resonant frequency, SPL all unpublished |
-| **6–36 V DC input** | `U1` ME3116AM6G | O ✔ | — | — | [power-and-battery](features/power-and-battery.md) | none | **none** | No datasheet; `C24` rated 35 V vs 36 V spec |
-| **Li-ion charging** | `U2` TP4057, 100 mA | O ✔ | — | — | [power-and-battery](features/power-and-battery.md) | none | **none** | 4.24 V float, not 4.20 V |
-| **Battery voltage sense** | GPIO10, ÷2 | O ✘ | — | ✔ Launcher (`ANALOG_BAT_PIN=10`, ratio 2.0) | [power-and-battery](features/power-and-battery.md) | none | **none** | Not in the vendor PinMap at all |
-| **Power latch (GPIO46)** | `Q4` LN2324DT2AG | O ✔ (Learn) | ✔ `examples/Basic/wakeup` | ✔ esp-board-manager | [power-and-battery](features/power-and-battery.md) | none | **none** | — |
-| **PORT.A (I²C)** | `J3`, GPIO15/13 | O ⚠ (colours disputed) | — | ✔ Launcher (as SD SPI) | [porta-portb-expansion](features/porta-portb-expansion.md) | none | **none** | ⚠ Yellow/white conflict unresolved |
-| **PORT.B (GPIO)** | `J4`, GPIO1/2 | O ⚠ | — | ✔ Launcher | [porta-portb-expansion](features/porta-portb-expansion.md) | none | **none** | Same conflict |
-| **Wi-Fi** | ESP32-S3 + module antenna | O ✔ (tutorial page) | ✔ within `examples/Basic/rtc` | ✔ many | [wifi-and-ble](features/wifi-and-ble.md) | none | **none** | No RF measurement; S3A antenna claim unverified |
-| **BLE** | ESP32-S3 (BLE 5, **no Classic**) | O ✔ | — | ✔ `tarmn3/m5dinmeter-ble-volume-knob` | [wifi-and-ble](features/wifi-and-ble.md) | none | **none** | — |
-| **RGB LED** | WS2812B-2020 in the Stamp, GPIO21 | O ✔ (v1.1 page only) | — | — | [rgb-led](features/rgb-led.md) | none | **none** | ⚠ **v1.1 needs GPIO38 high — predicted, unverified** |
-| **USB (native CDC/JTAG)** | ESP32-S3 OTG, USB-C on the Stamp | O ✔ | — | ✔ Launcher (`ARDUINO_USB_MODE=1`) | [development](development.md) §5 | none | **none** | — |
-| **DIN panel mounting** | 1/32 DIN, 45 × 22.5 mm | O ✔ | — | — | [din-mounting-and-mechanical](features/din-mounting-and-mechanical.md) | none | **none** | Bezel dims, panel-thickness range, IP rating unpublished |
-| **Deep-sleep / power-off** | latch, 38.4 µA | O ✔ | ✔ `examples/Basic/wakeup` | — | [power-and-battery](features/power-and-battery.md) | none | **none** | Vendor figure, no method |
-
-## 2. Capabilities the device does **not** have
-
-Stated positively so the absence is a finding rather than an omission. All from the 84-part
-designator census plus the vendor specification tables.
-
-| Not present | Evidence |
-|---|---|
-| PSRAM | `ESP32-S3FN8`; no PSRAM row on either page; Launcher `build_unflags = -DBOARD_HAS_PSRAM` |
-| microSD / storage | no connector designator (Launcher bit-bangs one across the Grove ports) |
-| Touch | no controller designator; not in any spec table |
-| Microphone / speaker / codec | only `LS1`, a magnetic buzzer |
-| IMU / accelerometer | no designator |
-| Environmental sensors | no designator |
-| USB-UART bridge | USB is the SoC's own peripheral |
-| Bluetooth Classic (BR/EDR) | ESP32-S3 silicon limitation |
-| External antenna connector | no designator on either Stamp schematic |
-| RGB LED on the *carrier* | the WS2812B is inside the Stamp module |
-| DIN-**rail** mounting | it is a panel-cutout device; see the mounting guide |
-
-## 3. Coverage summary
-
-| Metric | Count |
-|---|---:|
-| Advertised/fitted capabilities enumerated | **20** |
-| With a task-oriented feature guide | **20 / 20** |
-| With a natural-language entry in the README "How do I…?" index | **20 / 20** |
-| With official vendor documentation | 16 / 20 |
-| With an official vendor example | 7 / 20 |
-| With a community example | 10 / 20 |
-| **Build-tested here** | **0 / 20** |
-| **Hardware-tested here** | **0 / 20** |
-| With an open gap recorded | 12 / 20 |
-
-## 4. The gaps that would move the needle most
-
-Ranked by value to the next person:
-
-1. **Verify the RGB-LED/GPIO38 prediction on a real v1.1 unit.** One line of code, five minutes,
-   and it converts the single most consequential `inferred` claim in this record into a
-   measurement. → [`compatibility-and-status.md`](compatibility-and-status.md)
-2. **Photograph the rear silkscreen / pin sticker.** Settles the PORT.A/B wire-colour conflict
-   that has stood since the M5Dial.
-3. **Measure the Grove 5 V rail.** 5.00 V or 5.38 V — a meter on `J3` pin 3.
-4. **Teardown photographs.** Would confirm the encoder, the buzzer, `U4` on the Stamp-S3A, and
-   whether the v1.1 PCB really is the v1.0 PCB.
-5. **Build one vendor example.** Would give this record its first `executed-success` on the
-   software path and confirm or refute the guessed Arduino FQBN.
diff --git a/devices/m5stack/dinmeter/development.md b/devices/m5stack/dinmeter/development.md
deleted file mode 100644
index 93a9773..0000000
--- a/devices/m5stack/dinmeter/development.md
+++ /dev/null
@@ -1,286 +0,0 @@
-# DinMeter — development
-
-Applies to **K134 and K134-V11** unless a row says otherwise. Every command carries a status:
-`executed-success` · `executed-failed` · `reported-working` · `inferred` · `not-tested`.
-
-> **No DinMeter hardware was available for this pass.** Nothing below is `executed-success` on
-> the device. Build and flash commands are `inferred` from vendor documentation, vendor project
-> files and framework documentation, and are labelled as such. The command ledger in
-> [`commands.md`](commands.md) records exactly what *was* run (all of it acquisition and
-> analysis) and what was not.
-
----
-
-## 0. The one thing to do first
-
-```cpp
-void setup() {
-    auto cfg = M5.config();
-    DinMeter.begin(cfg, true);   // <- this calls M5.begin(), which raises GPIO46 (HOLD)
-    ...
-}
-```
-
-On battery power the board is only alive while **GPIO46 is high**. `M5.begin()` does it for you
-via M5Unified's power-hold table (`_pin_table_other1`, `board_M5DinMeter → GPIO_NUM_46`,
-`M5Unified/src/M5Unified.cpp:282`). If you write bare ESP-IDF or bare Arduino without
-M5Unified, **you must do it yourself, before anything slow**:
-
-```c
-gpio_set_direction(GPIO_NUM_46, GPIO_MODE_OUTPUT);
-gpio_set_level(GPIO_NUM_46, 1);
-```
-`inferred` from the vendor Learn section and `esp-board-manager`'s `gpio_power_hold`
-(`default_level: 1`).
-
-Symptom if you forget: the board runs for as long as you hold the knob in, then dies. On USB it
-works fine, which makes the bug look like a "battery problem".
-
----
-
-## 1. Arduino — M5Unified + M5DinMeter (the vendor path)
-
-### Versions
-
-| Component | Version | Evidence |
-|---|---|---|
-| Board package | **M5Stack Arduino Board Manager v2.1.1** — the version every vendor example header names | `M5DinMeter/examples/Basic/*/*.ino` header comments, all dated 2024-03-07 |
-| Board target | `M5Stack-Din-Meter` (M5Stack board package) — **not verified**; the vendor examples do not name a board FQBN | `inferred` |
-| `M5DinMeter` | **1.0.0** — the only release, tagged 2024-03-07. Repo HEAD `8ccbad7297beb82a140f812e5606e060d8a5e0dc` (pushed 2026-08-03) is still `version=1.0.0` | `library.properties:2`; GitHub API |
-| `M5Unified` | `>= 0.1.13` declared; latest release **0.2.21** (2026-08-26) | `M5DinMeter/library.json:16` |
-| `M5GFX` | pulled in by M5Unified; latest **0.2.28** (2026-08-25) | GitHub API |
-
-`M5DinMeter` declares exactly one dependency (`depends=M5Unified`) and its licence file lists
-M5GFX (MIT), M5Unified (MIT) and the bundled `Encoder` (PJRC, MIT). The library itself carries
-**no `LICENSE` file** and GitHub reports no licence for the repository.
-
-### What the library actually is
-
-45 lines of header and 23 of implementation. It is a façade over M5Unified plus one vendored
-third-party encoder driver:
-
-```cpp
-// M5DinMeter/src/M5DinMeter.h
-#define DIAL_ENCODER_PIN_A 41
-#define DIAL_ENCODER_PIN_B 40
-class M5DinMeter {
-  M5GFX &Display = M5.Display;   Power_Class &Power = M5.Power;
-  RTC8563_Class &Rtc = M5.Rtc;   Speaker_Class &Speaker = M5.Speaker;
-  Button_Class &BtnA = M5.BtnA;
-  I2C_Class &In_I2C = m5::In_I2C;   // internal bus  (GPIO12/11) - RTC
-  I2C_Class &Ex_I2C = m5::Ex_I2C;   // external bus  (GPIO15/13) - PORT.A
-  ENCODER Encoder = ENCODER(DIAL_ENCODER_PIN_A, DIAL_ENCODER_PIN_B);
-  void begin(m5::M5Unified::config_t cfg, bool enableEncoder = false);
-  void update(void);
-};
-extern m5::M5DinMeter DinMeter;
-```
-
-**Note `enableEncoder` defaults to `false`.** `DinMeter.begin(cfg)` will not start the encoder;
-you need `DinMeter.begin(cfg, true)`. Every vendor example that reads the knob passes `true`.
-
-### Install
-
-```bash
-# Arduino IDE: Library Manager -> "M5DinMeter"          (reported-working; vendor instruction)
-# or, pinned to the exact snapshot analysed here:
-git clone https://github.com/m5stack/M5DinMeter.git ~/Arduino/libraries/M5DinMeter
-git -C ~/Arduino/libraries/M5DinMeter checkout 8ccbad7297beb82a140f812e5606e060d8a5e0dc
-```
-`inferred` — the clone form was not run; the tarball of that exact commit **was** fetched and is
-retained at
-[`artifacts/source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz`](artifacts/source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz)
-(SHA-256 `de47c4109635870506bb7a02040db496f82e5bbb22a5b1befe600a3985eb0f02`, `executed-success`).
-
-### Build, flash, monitor
-
-```bash
-arduino-cli core install m5stack:esp32                                   # not-tested
-arduino-cli lib install M5DinMeter                                       # not-tested
-arduino-cli compile -b m5stack:esp32:m5stack_dinmeter sketch/            # not-tested; FQBN unverified
-arduino-cli upload  -b m5stack:esp32:m5stack_dinmeter -p /dev/ttyACM0 sketch/   # not-tested
-arduino-cli monitor -p /dev/ttyACM0 -c baudrate=115200                   # not-tested
-```
-
-**The FQBN `m5stack:esp32:m5stack_dinmeter` is a guess and is flagged as such.** M5Stack's own
-documentation gives IDE instructions only; no vendor source in this pass names the FQBN. Verify
-with `arduino-cli board listall | grep -i din`.
-
-### PlatformIO
-
-The vendor's own factory-firmware project uses a **generic** board, not a DinMeter board:
-
-```ini
-; m5stack/M5DinMeter-UserDemo/platformio.ini  (executed-success: read from the retained snapshot)
-[env:esp32-s3-devkitc-1]
-platform = espressif32@6.3.1
-board = esp32-s3-devkitc-1
-framework = arduino
-board_build.f_cpu = 240000000L
-monitor_speed = 115200
-monitor_filters = esp32_exception_decoder
-lib_deps =
-    lovyan03/LovyanGFX @ 1.1.12
-    forairaaaaa/SmoothUIToolKit @ 1.0.1
-```
-
-That is a useful, working, *pinned* starting point — and it tells you something: **you do not
-need a DinMeter board definition.** `esp32-s3-devkitc-1` with `f_cpu` pinned is enough, because
-everything board-specific is pin numbers.
-
----
-
-## 2. ESP-IDF
-
-There is **no M5Stack ESP-IDF component** for the DinMeter. There are two credible routes.
-
-### 2a. Espressif's `esp-board-manager` (recommended — it is a real, maintained board definition)
-
-`espressif/esp-board-manager` ships `m5stack_boards/m5stack_dinmeter/` with three YAML files
-that between them define the whole board. Fetched at repository HEAD
-`2beb9b22b0892b343bd555a1ebc9929a7edce8fc` (2026-09-03) and retained at
-[`artifacts/source-snapshots/`](artifacts/source-snapshots/) (`executed-success`).
-
-What it gives you, ready to use:
-
-| Definition | Value |
-|---|---|
-| `board_info.yaml` | `board: m5stack_dinmeter`, `chip: esp32s3`, `version: 1.0.0` |
-| `spi_display` | `SPI2_HOST`, SCLK 6, MOSI 5, MISO −1, `max_transfer_sz: 6480` |
-| `display_lcd` | `chip: st7789`, 135 × 240, CS 7, DC 4, RST 8, mode 0, **40 MHz**, `invert_color: true`, 16 bpp, RGB order |
-| `ledc_backlight` | GPIO9, ch 0, timer 0, **5 kHz**, 10-bit |
-| `ledc_buzzer` | GPIO3, ch 1, timer 1, **4 kHz**, 10-bit |
-| `pcnt_encoder` | edge 41 / level 40 and edge 40 / level 41, `max_glitch_ns: 1000`, ±1000, `accum_count: true`, watch points −1000/0/1000 |
-| `i2c_master` | port 0, SDA 11, SCL 12 (the RTC bus) |
-| `gpio_power_hold` | GPIO46, output, `default_level: 1` |
-| `gpio_button_wake` | GPIO42, input, pull-up, active-low, long-press 2000 ms |
-
-Its own comments are unusually candid and worth reading — they document the GRAM gap
-(**column +52, row +40**, applied by the application via the panel gap API because the board
-model has no offset field), the reason both PCNT channels are used, and an ESP32-S3-specific
-build trap:
-
-> "No `en_step_notify_up` / `en_step_notify_down` here on purpose: those `pcnt_unit_config_t`
-> fields exist only under `SOC_PCNT_SUPPORT_STEP_NOTIFY`, which the ESP32-S3 does not have, and
-> bmgr's `periph_pcnt` generator emits the field whenever the key is PRESENT — even when false.
-> Keeping them (both were false) breaks the build with `'struct <anonymous>' has no member named
-> 'en_step_notify_up'`."
-
-It also records what it deliberately does **not** model: the BM8563 RTC (no device type — the
-I²C bus is provided, the driver is yours), both Grove ports, the DC input, the charger, the RST
-button, and USB.
-
-```bash
-idf.py set-target esp32s3                                    # not-tested
-idf.py -DBOARD=m5stack_dinmeter build flash monitor          # not-tested; consult esp-board-manager's own README for the exact invocation
-```
-
-### 2b. Plain ESP-IDF
-
-Nothing about the board needs a BSP. Target `esp32s3`, **no PSRAM**, 8 MB flash, and the pin map
-from [`pinouts-and-buses.md`](pinouts-and-buses.md). Use `esp_lcd_panel_st7789` (built in), the
-`pcnt` driver for the encoder, `ledc` for backlight and buzzer, `i2c_master` for the RTC.
-
-```bash
-idf.py set-target esp32s3 && idf.py menuconfig
-#   Serial flasher config -> Flash size -> 8 MB
-#   Component config -> ESP PSRAM -> [ ] Support for external SPI RAM   (there is none)
-idf.py build && idf.py -p /dev/ttyACM0 flash monitor          # not-tested
-```
-
----
-
-## 3. UiFlow2 (and how it relates to the Arduino path)
-
-M5Stack documents a UiFlow2 tutorial for the DinMeter at
-`https://docs.m5stack.com/en/uiflow2/m5dinmeter/program` (HTTP 200, 2026-09-04) and lists
-UiFlow2 first among the supported development platforms on both product pages.
-
-**How the two relate — this trips people up.** UiFlow2 is *not* a layer over the Arduino
-library. It is a **MicroPython firmware** (`m5stack/uiflow-micropython`, which has a
-`build-firmware.yml` CI workflow and a `.gitlab-ci.yml` that both reference DinMeter) which you
-flash **in place of** your Arduino sketch, using **M5Burner**. The relationship is:
-
-| | Arduino / M5DinMeter | UiFlow2 |
-|---|---|---|
-| What is on the flash | your compiled sketch | a MicroPython interpreter + the UiFlow2 runtime |
-| How you program | compile & upload | drag blocks in a browser, push over Wi-Fi/USB |
-| Underlying HAL | M5Unified (C++) | M5Stack's MicroPython bindings, which wrap the *same* M5GFX/M5Unified C++ code |
-| Switching between them | reflash — they are mutually exclusive images | reflash |
-| Pin map | identical | identical |
-
-So the pin assignments and the GPIO46 hold requirement in this document apply verbatim to
-UiFlow2; only the API surface differs.
-
-**Getting UiFlow2 firmware:** M5Burner (desktop app, from `docs.m5stack.com` → Software →
-M5Burner) is the vendor's distribution channel; it downloads images at run time from an M5Stack
-endpoint rather than from a documented static URL. **No stable direct download URL for a
-DinMeter UiFlow2 binary was located in this pass** — recorded as a gap in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) §7.
-
----
-
-## 4. MicroPython
-
-Two routes:
-
-1. **UiFlow2** (§3) — M5Stack's own MicroPython fork with board bindings. The supported path.
-2. **`mattytrentini/chipboard`** ships `boards/m5stack_din_meter.yaml`, a community board
-   definition for generic MicroPython. **[COM]** — not evaluated, not built. Recorded in
-   [`examples/catalog.json`](examples/catalog.json) as a discovered candidate.
-
-Vanilla `micropython/micropython` has **no** DinMeter board port (searched 2026-09-04).
-
----
-
-## 5. Serial, USB and download mode
-
-| Aspect | Value | Evidence |
-|---|---|---|
-| USB connector | USB-C, **on the Stamp module**, not on the carrier | Stamp-S3 schematic `J2` |
-| USB peripheral | ESP32-S3 native **USB OTG / USB-Serial-JTAG** — there is **no UART bridge chip** | vendor spec row; no bridge designator in the 84-part census |
-| Port on Linux | typically `/dev/ttyACM*` (CDC-ACM), not `/dev/ttyUSB*` | `inferred` from the native-USB architecture |
-| Monitor baud | 115200 (vendor project setting) | `M5DinMeter-UserDemo/platformio.ini` |
-| **Download mode** | **hold the `G0` button on the Stamp module while applying power, release after power is applied** | vendor Learn section, both product pages, identical wording for Stamp-S3 and Stamp-S3A |
-| Reset | `S4` RST button on the carrier drives the Stamp's `EN` | DinMeter schematic |
-| JTAG | USB-Serial-JTAG is available; the classic JTAG pins (GPIO39–42, `MTCK/MTDO/MTDI/MTMS`) are **all in use** — 40/41 encoder, 42 button — so pin-based JTAG is not practical | schematic + `pinouts-and-buses.md` |
-
-Because USB is the SoC's own peripheral, **a crashed or sleeping application takes the serial
-port with it.** If the port disappears, use download mode.
-
----
-
-## 6. Bricking and power risks
-
-| Risk | Why | Mitigation |
-|---|---|---|
-| **Board switches off mid-flash on battery** | GPIO46 low = battery disconnected | Flash over USB, which bypasses the latch |
-| **Forgetting the GPIO46 hold** | see §0 | `M5.begin()`, or set it manually first thing |
-| **Pulling GPIO46 high externally** | It is an ESP32-S3 strapping pin, pulled *down* by design on the Stamp module; high at reset prevents boot | Never fit an external pull-up; drive it only after boot |
-| **36 V on the DC terminal** | `C24`, the input bulk cap, is rated **35 V** — 103 % of the spec ceiling | Treat 36 V as absolute maximum, not a working point. Stay ≤ 30 V for continuous use (`inferred`, engineering judgement, not a vendor statement) |
-| **Reverse polarity on the DC terminal** | `D13`/`D12` Schottkys are fitted, but their rating was not read | Do not rely on it; get the polarity right |
-| **5 V-max peripheral on a Grove port** | the boost's own divider computes to ≈ 5.38 V, while the spec says 5 V | Measure before connecting. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §6 |
-| **Losing the factory firmware** | there is no vendor-published pre-built binary with a documented URL | Read the flash out *before* you overwrite it: `esptool.py read_flash 0 0x800000 backup.bin` (`not-tested`). See [`factory-firmware.md`](factory-firmware.md) |
-
----
-
-## 7. Firmware image metadata
-
-| Field | Value |
-|---|---|
-| Target MCU | ESP32-S3 (`esp32s3`), Xtensa LX7 dual-core |
-| Flash | 8 MB, in-package (`ESP32-S3FN8`) |
-| PSRAM | **none** — do not enable it |
-| CPU frequency | 240 MHz (`board_build.f_cpu = 240000000L`) |
-| Flash mode / freq | not stated by the vendor; ESP32-S3 default QIO 80 MHz applies unless changed |
-| Partition table | **not published.** Not stated on either product page, not in the UserDemo `platformio.ini`, which means PlatformIO's `esp32-s3-devkitc-1` default applies to that project |
-| Bootloader | stock ESP-IDF second-stage bootloader (framework-supplied) |
-
----
-
-## Related
-
-- [`features/`](features/README.md) — per-capability procedures
-- [`commands.md`](commands.md) — everything actually executed, with output
-- [`coverage.md`](coverage.md) — which features have a build/test status
-- [`examples/best.md`](examples/best.md) — which example to start from
diff --git a/devices/m5stack/dinmeter/driver-vs-document-audit.md b/devices/m5stack/dinmeter/driver-vs-document-audit.md
deleted file mode 100644
index ef751c1..0000000
--- a/devices/m5stack/dinmeter/driver-vs-document-audit.md
+++ /dev/null
@@ -1,99 +0,0 @@
-# DinMeter — vendor driver read against the schematic
-
-**Audited:** 2026-09-07 · workflow step 10.
-
-**Sources read side by side**
-
-| Role | Path / identity |
-|---|---|
-| Schematic | `artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf`, traced in [`schematic-netlist.md`](schematic-netlist.md) |
-| Vendor driver | `artifacts/source-snapshots/M5DinMeter-8ccbad7297beb82a140f812e5606e060d8a5e0dc.tar.gz` → `m5stack-M5DinMeter-8ccbad7/` |
-
----
-
-## A. Agreements — the driver matches the sheet
-
-| Claim | Source | Schematic | Verdict |
-|---|---|---|---|
-| `#define DIAL_ENCODER_PIN_A 41` | `src/M5DinMeter.h:8` | `J5.3` (`A`) → net `IN_A` → module pad 23, pin name **`G41/MTDI`** | ✅ |
-| `#define DIAL_ENCODER_PIN_B 40` | `src/M5DinMeter.h:9` | `J5.5` (`B`) → net `IN_B` → module pad 21, pin name **`G40/MTDO`** | ✅ |
-| Buzzer on GPIO3 (`spk_cfg.pin_data_out = GPIO_NUM_3`, M5Unified) | — | net `beep` → module pad 3, pin name `G3` | ✅ |
-| Buzzer modelled as a driven tone source, not on/off | M5Unified / ESP-IDF board support | base drive is **AC-coupled through `C27` 10 µF**; a DC level cannot reach the transistor | ✅ and now *explained* by the hardware |
-
-## B. Findings
-
-### 1. `pinMode(INPUT_PULLUP)` on lines that already carry 10 kΩ pull-ups — **inert**
-
-`src/utility/Encoder.h`, `ENCODER::begin()`:
-
-```cpp
-pinMode(_pin1, INPUT_PULLUP);
-pinMode(_pin2, INPUT_PULLUP);
-```
-
-The schematic fits `R2` and `R3`, both 10 kΩ, from `IN_A`/`IN_B` to `+3.3V`. The ESP32-S3's
-internal pull-up (nominally ~45 kΩ) lands in parallel, giving ≈ 8.2 kΩ. That is a stiffer
-pull-up than designed, not a fault, and it slightly *helps* the RC settling discussed next.
-Harmless; recorded because it changes the filter time constant and someone measuring edge shapes
-will otherwise be puzzled.
-
-### 2. The 2 ms settling delay is about 2.4 time constants, not 5 — **inert, borderline**
-
-Same function:
-
-```cpp
-// allow time for a passive R-C filter to charge
-// through the pullup resistors, before reading
-// the initial state
-delayMicroseconds(2000);
-```
-
-The comment shows the author knew an RC filter might be present. On this board it is: `C2` and
-`C3`, 100 nF, from `IN_A`/`IN_B` to `GND`.
-
-With the parallel pull-up of ≈ 8.2 kΩ, τ ≈ 8.2 kΩ × 100 nF ≈ **0.82 ms**. A 2 000 µs delay is
-≈ 2.4 τ, i.e. the node reaches ≈ **91 %** of the rail before the initial quadrature state is
-latched. It will read high — 91 % of 3.3 V is 3.0 V, far above V_IH — so the code is correct in
-practice. But the margin is 2.4 τ where the conventional figure is 5 τ, and the value is
-hard-coded in a library shared across boards with different filter components. **Inert here;
-a trap if this Encoder copy is reused with a larger capacitor.**
-
-This is also the first *quantitative* statement about the encoder input filter available
-anywhere in this record, and it has a second consequence: the RC corner is
-1/(2π · 8.2 kΩ · 100 nF) ≈ **194 Hz**, which is the hardware ceiling on edge rate regardless of
-how fast the ISR is.
-
-### 3. The encoder consumes two of the four JTAG pins — **active, by design, undocumented**
-
-`GPIO41` = `MTDI`, `GPIO40` = `MTDO`, as printed on the module footprint's own pin names. Calling
-`DinMeter.begin(true)` attaches `CHANGE` interrupts to both. **An external JTAG probe and the
-rotary encoder cannot be used at the same time.** Neither the header, the driver, nor the product
-documentation says so.
-
-Note also that `GPIO41`/`MTDI` is sampled at reset on ESP32 parts for eFuse-configurable boot
-behaviour; on the ESP32-S3 the strapping pins are 0, 3, 45 and 46, so `MTDI` is **not** a strap
-here and the 10 kΩ pull-up is safe. Checked rather than assumed.
-
-### 4. `M5DinMeter::begin()` does nothing but forward — **not a defect**
-
-`src/M5DinMeter.cpp:7-19` calls `M5.begin()` then optionally `Encoder.begin()`. There is no
-board-specific power-up ordering in this library at all; everything is in M5Unified. So there is
-no ordering here to compare against a datasheet — stated explicitly, because "no finding" and
-"not checked" are different and only one of them is useful.
-
-### 5. The encoder is polled through an ISR that never reports loss — **inert**
-
-`Encoder::update()` is a 16-state quadrature decoder with `+2`/`-2` cases for "assume pin1 edges
-only" — i.e. it *detects* that it missed an intermediate state and guesses a direction rather
-than flagging it. On a hand-turned knob behind a 194 Hz RC filter this will not fire. There is no
-error counter, so a fast spin degrades silently. Worth knowing; not worth fixing.
-
-## C. Not checked
-
-- **`M5DinMeter-UserDemo`** (also snapshotted) was not audited.
-- **`U5` `RTC8563` initialisation against the RTC's register map** was not audited. The RTC is on
-  the internal bus (`IN_SDA`/`IN_SCL` → `G11`/`G12`) with `Y2` 32.768 kHz ±20 ppm 12.5 pF and
-  `C28`/`C29` 6.0 pF loading capacitors. The 12.5 pF crystal against 6.0 pF fitted loading is the
-  obvious thing to examine next — nominal C_L for a 12.5 pF crystal needs roughly 2 × (12.5 − C_stray)
-  per leg, which 6.0 pF is in the right region for, but this was **not** worked through and is
-  recorded as an open item rather than a result.
diff --git a/devices/m5stack/dinmeter/examples/best.md b/devices/m5stack/dinmeter/examples/best.md
deleted file mode 100644
index 6efcb28..0000000
--- a/devices/m5stack/dinmeter/examples/best.md
+++ /dev/null
@@ -1,133 +0,0 @@
-# DinMeter — selected examples
-
-**7 selected from 22 catalogued** ([`catalog.json`](catalog.json), search method in
-[`search-log.md`](search-log.md)). Selection is for *coverage and quality*, not popularity.
-
-> **None of these were built or run.** No toolchain was installed and no hardware was available.
-> Every `build_status` in the catalogue is `not-attempted`, and that is stated rather than
-> implied.
-
----
-
-## The portfolio, and why each is in it
-
-| # | Example | Role in the portfolio | Where |
-|---|---|---|---|
-| **OFF-08** | `esp-board-manager` `m5stack_dinmeter` | **Best reference configuration and best documentation.** Start here for ESP-IDF | [Espressif](https://github.com/espressif/esp-board-manager/tree/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/m5stack_boards/m5stack_dinmeter) · [vendored](../artifacts/source-snapshots/) |
-| **OFF-01** | `encoder.ino` | Best minimal example of the defining feature | [pinned](https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/encoder/encoder.ino) |
-| **OFF-02** | `display.ino` | Best minimal display example | [pinned](https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/display/display.ino) |
-| **OFF-03** | `rtc.ino` | Best *integrated* vendor example — RTC + Wi-Fi + SNTP + display | [pinned](https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/rtc/rtc.ino) |
-| **OFF-04** | `wakeup.ino` | **Limit/architecture example** — the GPIO46 latch and RTC wake-from-off | [pinned](https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/wakeup/wakeup.ino) |
-| **OFF-07** | `M5DinMeter-UserDemo` | Best complete application; the raw-LovyanGFX reference | [pinned](https://github.com/m5stack/M5DinMeter-UserDemo/tree/d2fdfe44e9baf810f82335faa6f5962e9fc59a44) · [vendored](../artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz) |
-| **COM-01** | `bmorcelli/Launcher` DinMeter board | **Independent cross-check** + a distinct implementation approach + Grove-pin-reuse limit test | [board file](https://github.com/bmorcelli/Launcher/blob/main/boards/m5stack-dinmeter/platformio.ini) · [vendored](../artifacts/source-snapshots/launcher-m5stack-dinmeter-platformio.ini) |
-
-## Coverage check
-
-| Feature | Covered by | Gap |
-|---|---|---|
-| Rotary encoder | OFF-01 (Arduino/PJRC), OFF-08 (IDF/PCNT), COM-01 (mathertel) — **three distinct approaches** | — |
-| Button / WAKE | OFF-01, OFF-04, OFF-08 | — |
-| Display | OFF-02 (M5GFX), OFF-07 (raw LovyanGFX), OFF-08 (esp_lcd), COM-01 (Arduino_GFX) — **four approaches** | — |
-| Backlight / dimming | OFF-07, OFF-08, COM-01 | — |
-| RTC + NTP | OFF-03 | — |
-| RTC alarm wake-from-off | OFF-04 | — |
-| Buzzer | OFF-01 (in context), OFF-08 (LEDC) | — |
-| Power latch (GPIO46) | OFF-04, OFF-08 | — |
-| Battery ADC | COM-01 only | **No vendor example** |
-| Wi-Fi | OFF-03 | — |
-| BLE | — | **No selected example.** COM-07 exists but is unlicensed |
-| PORT.A / PORT.B | COM-01 (as SD SPI) | **No simple Grove I²C example** |
-| **RGB LED** | — | **No example anywhere**, and this is the one feature with a known v1.1 break |
-| DIN mounting | n/a (mechanical) | — |
-
-**Three genuine gaps**, stated rather than papered over: no licensed BLE example, no plain Grove
-I²C example, and **no RGB-LED example at all** — which is unfortunate, because that is exactly
-where DinMeter v1.1 diverges. See [`../features/rgb-led.md`](../features/rgb-led.md).
-
-## Why these, and not the popular ones
-
-- `no-body-in-particular/m5din-hikoki` (★25) is the most-starred DinMeter application and is
-  **not selected**: it is a domain-specific instrument that teaches nothing about the board that
-  OFF-01/02/03 do not.
-- `viniciusbo/m5-palnagotchi` (★81) is the most-starred repository touching the device and is
-  **not selected**: DinMeter is one target among many, with nothing device-specific to learn.
-- `tarmn3/m5dinmeter-ble-volume-knob` is the **only** BLE example and is **not selected** because
-  it declares **no licence**. Pointing people at unlicensed code to copy is not a favour. It is
-  catalogued, and reading it is fine.
-- **Popularity was not treated as authority.** OFF-08, the best item in the portfolio, is a
-  directory of three YAML files with no stars at all.
-
-## Notes on each selection
-
-### OFF-08 — Espressif's board definition · *read this first*
-
-Not an "example" in the usual sense: three YAML files that define the whole board for ESP-IDF.
-It is nonetheless the highest-value item found, because its comments document things M5Stack does
-not:
-
-- **the GRAM gap** (column +52, row +40) and that the application must apply it via the panel gap
-  API, because the board model has no offset field;
-- **the two-channel PCNT quadrature pattern**, and that GPIO40/41 appearing double-booked is
-  expected and correct;
-- **a genuine build break** — `en_step_notify_up`/`_down` exist only under
-  `SOC_PCNT_SUPPORT_STEP_NOTIFY`, which the ESP32-S3 lacks, so emitting them (even as `false`)
-  fails compilation;
-- **the GPIO3-vs-GPIO42 ambiguity** in M5Stack's own pin table, resolved by citing M5Unified;
-- **what it deliberately does not model** — the RTC device, both Grove ports, the charger, USB.
-
-One caution: its Grove wire-colour note derives from M5Stack's disputed PinMap (its own header
-says so), so it must **not** be counted as independent corroboration on that point.
-
-### OFF-01 — `encoder.ino`
-
-The one thing to notice: `DinMeter.begin(cfg, true)`. The `enableEncoder` parameter **defaults to
-`false`**, so `begin(cfg)` leaves the knob dead. It also shows the click-per-detent pattern
-(`Speaker.tone(8000, 20)`), which is how the device feels right.
-
-### OFF-04 — `wakeup.ino` · *the architecture lesson*
-
-`Power.timerSleep(5)` is not an ESP32 deep sleep. It programmes the BM8563 alarm and then
-**releases the GPIO46 latch**, cutting the battery. That is why the board's standby figure is
-38.4 µA rather than a typical deep-sleep number, and why forgetting to hold GPIO46 makes the
-device switch itself off. Read this example before writing anything battery-powered.
-
-### OFF-07 — `M5DinMeter-UserDemo` · *the factory firmware*
-
-MIT, all dependencies pinned (`espressif32@6.3.1`, `LovyanGFX 1.1.12`, `SmoothUIToolKit 1.0.1`).
-`ft_disp_lgfx_cfg.hpp` is the authoritative raw-LovyanGFX configuration and uses
-`lgfx::Panel_ST7789` — the generic class, not a V2-specific one, which is part of why the v1.1
-ST7789P3 is expected to behave identically.
-
-**Mixed-licence archive:** the MIT at the root does not cover the bundled `lib/` trees (PJRC
-`Encoder`, `ESP32Encoder`, `I2C_BM8563`, `Button`), each of which ships its own licence file.
-
-### COM-01 — `bmorcelli/Launcher` · *the independent check*
-
-Different author, different graphics library (`Arduino_GFX`, not M5GFX), different encoder
-library (`mathertel/RotaryEncoder 1.5.3`), and a CI matrix that builds it on every release. It
-agrees with the schematic on every point it touches — display pins, GRAM offsets, battery divider
-ratio 2.0, no PSRAM — which is the strongest available corroboration short of hardware.
-
-It is also a **limit test**: it bit-bangs an SD card across *both* Grove ports
-(`SDCARD_CS=13 SCK=15 MISO=2 MOSI=1`), consuming all four free user pins. That is the only
-evidenced way to get storage onto this board, and it shows exactly what it costs.
-
-## What was vendored, and what was not
-
-| Vendored (3) | Why |
-|---|---|
-| `M5DinMeter` @ `8ccbad72…` (8 532 B) | tiny; contains all six official examples |
-| `M5DinMeter-UserDemo` @ `d2fdfe44…` (74 231 B) | MIT, small, and the factory image's only public form |
-| `esp-board-manager` DinMeter YAMLs (7 367 B) | tiny, and the single best reference |
-| `launcher-m5stack-dinmeter-platformio.ini` (1 601 B) | one file; the corroboration is the point |
-
-**Not vendored:** `M5Unified` and `M5GFX` (large, canonical, and reproducible from the pinned
-commits recorded in [`../sources.md`](../sources.md)); all COM-02…COM-10 application projects
-(links and immutable-revision notes retained in the catalogue instead).
-
-## If you build one thing
-
-Build **OFF-04 (`wakeup.ino`)** on a real unit. It exercises the encoder button, the RTC, the
-power latch and the display in ~40 lines, and it is the fastest way to confirm that the whole
-device-specific architecture works on your board. Then add the two lines from
-[`../features/rgb-led.md`](../features/rgb-led.md) and settle the outstanding v1.1 question.
diff --git a/devices/m5stack/dinmeter/examples/catalog.json b/devices/m5stack/dinmeter/examples/catalog.json
deleted file mode 100644
index 9003cb6..0000000
--- a/devices/m5stack/dinmeter/examples/catalog.json
+++ /dev/null
@@ -1,834 +0,0 @@
-{
- "$schema-note": "Example catalogue for M5Stack DinMeter (K134 / K134-V11). Every meaningful discovered example has a disposition, including rejected and inaccessible candidates.",
- "device": [
-  "m5stack/dinmeter",
-  "m5stack/dinmeter-v1.1"
- ],
- "generated": "2026-09-04",
- "global": {
-  "build_environment": "none - no toolchain installed and no hardware available during this pass",
-  "all_build_statuses": "not-attempted",
-  "framework_versions_referenced": {
-   "arduino_board_package": "M5Stack Arduino Board Manager v2.1.1 (named in every vendor example header)",
-   "M5DinMeter": "1.0.0",
-   "M5Unified": ">=0.1.13 declared; 0.2.21 current",
-   "M5GFX": "0.2.28 current",
-   "platformio_platform": "espressif32@6.3.1 (pinned by M5Stack's factory project)",
-   "LovyanGFX": "1.1.12 (pinned)",
-   "SmoothUIToolKit": "1.0.1 (pinned)",
-   "mathertel/RotaryEncoder": "1.5.3 (pinned by Launcher)"
-  }
- },
- "examples": [
-  {
-   "id": "OFF-01",
-   "title": "encoder.ino",
-   "author": "SeanKwok (shaoxiang@m5stack.com), M5Stack",
-   "source_class": "primary",
-   "url": "https://github.com/m5stack/M5DinMeter/blob/main/examples/Basic/encoder/encoder.ino",
-   "immutable_url": "https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/encoder/encoder.ino",
-   "commit": "8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "release": "1.0.0",
-   "file_date": "2024-03-07",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-08-03",
-   "device": "K134 (applies unchanged to K134-V11)",
-   "framework": "Arduino, M5Stack board pkg v2.1.1",
-   "features": [
-    "rotary encoder",
-    "button",
-    "display",
-    "buzzer"
-   ],
-   "resources": [
-    "GPIO41",
-    "GPIO40",
-    "GPIO42",
-    "GPIO4-9",
-    "GPIO3"
-   ],
-   "dependencies": {
-    "M5DinMeter": "1.0.0",
-    "M5Unified": ">=0.1.13"
-   },
-   "license": "unknown",
-   "license_evidence": "No LICENSE file exists at the pinned commit and GitHub reports no licence for m5stack/M5DinMeter. The README lists MIT only for M5GFX and M5Unified, and 'original' for the bundled PJRC Encoder.",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Shows the enableEncoder=true argument, the single most common omission",
-    "Demonstrates read/readAndReset/write and pressedFor(5000)",
-    "Adds a 20 ms 8 kHz click per detent - a good UX pattern"
-   ],
-   "pitfalls": [
-    "begin() defaults enableEncoder=false",
-    "x4 decoding: one detent is four counts, and the example does not say so"
-   ],
-   "selected": true,
-   "selection_reason": "Best minimal example for the device's defining feature."
-  },
-  {
-   "id": "OFF-02",
-   "title": "display.ino",
-   "author": "SeanKwok (shaoxiang@m5stack.com), M5Stack",
-   "source_class": "primary",
-   "url": "https://github.com/m5stack/M5DinMeter/blob/main/examples/Basic/display/display.ino",
-   "immutable_url": "https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/display/display.ino",
-   "commit": "8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "release": "1.0.0",
-   "file_date": "2024-03-07",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-08-03",
-   "device": "K134 (applies unchanged to K134-V11)",
-   "framework": "Arduino, M5Stack board pkg v2.1.1",
-   "features": [
-    "display"
-   ],
-   "resources": [
-    "SPI2_HOST",
-    "GPIO4-9"
-   ],
-   "dependencies": {
-    "M5DinMeter": "1.0.0",
-    "M5Unified": ">=0.1.13"
-   },
-   "license": "unknown",
-   "license_evidence": "No LICENSE file exists at the pinned commit and GitHub reports no licence for m5stack/M5DinMeter. The README lists MIT only for M5GFX and M5Unified, and 'original' for the bundled PJRC Encoder.",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Shortest path to pixels",
-    "Shows both DinMeter.Display and a raw LovyanGFX* draw function"
-   ],
-   "pitfalls": [
-    "Does not show setRotation or setBrightness",
-    "Hides the GRAM offset - M5GFX applies it internally, which conceals something you must know if you drop to raw LovyanGFX"
-   ],
-   "selected": true,
-   "selection_reason": "Best minimal display example."
-  },
-  {
-   "id": "OFF-03",
-   "title": "rtc.ino",
-   "author": "SeanKwok (shaoxiang@m5stack.com), M5Stack",
-   "source_class": "primary",
-   "url": "https://github.com/m5stack/M5DinMeter/blob/main/examples/Basic/rtc/rtc.ino",
-   "immutable_url": "https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/rtc/rtc.ino",
-   "commit": "8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "release": "1.0.0",
-   "file_date": "2024-03-07",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-08-03",
-   "device": "K134 (applies unchanged to K134-V11)",
-   "framework": "Arduino, M5Stack board pkg v2.1.1",
-   "features": [
-    "RTC",
-    "Wi-Fi",
-    "SNTP",
-    "display"
-   ],
-   "resources": [
-    "GPIO11",
-    "GPIO12",
-    "radio"
-   ],
-   "dependencies": {
-    "M5DinMeter": "1.0.0",
-    "M5Unified": ">=0.1.13",
-    "WiFi": "Arduino core"
-   },
-   "license": "unknown",
-   "license_evidence": "No LICENSE file exists at the pinned commit and GitHub reports no licence for m5stack/M5DinMeter. The README lists MIT only for M5GFX and M5Unified, and 'original' for the bundled PJRC Encoder.",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "The only vendor example exercising two subsystems together (RTC + Wi-Fi)",
-    "Handles the esp_sntp.h / sntp.h header split across IDF versions with __has_include",
-    "Explicitly recommends keeping the RTC in UTC",
-    "Lands the time-set on a second boundary"
-   ],
-   "pitfalls": [
-    "Hardcoded SSID/password placeholders",
-    "Busy-waits on WiFi.status()"
-   ],
-   "selected": true,
-   "selection_reason": "Best integrated example; also the de-facto Wi-Fi example."
-  },
-  {
-   "id": "OFF-04",
-   "title": "wakeup.ino",
-   "author": "SeanKwok (shaoxiang@m5stack.com), M5Stack",
-   "source_class": "primary",
-   "url": "https://github.com/m5stack/M5DinMeter/blob/main/examples/Basic/wakeup/wakeup.ino",
-   "immutable_url": "https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/wakeup/wakeup.ino",
-   "commit": "8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "release": "1.0.0",
-   "file_date": "2024-03-07",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-08-03",
-   "device": "K134 (applies unchanged to K134-V11)",
-   "framework": "Arduino, M5Stack board pkg v2.1.1",
-   "features": [
-    "power latch",
-    "RTC alarm",
-    "power-off",
-    "button"
-   ],
-   "resources": [
-    "GPIO46",
-    "GPIO42",
-    "RTC"
-   ],
-   "dependencies": {
-    "M5DinMeter": "1.0.0",
-    "M5Unified": ">=0.1.13"
-   },
-   "license": "unknown",
-   "license_evidence": "No LICENSE file exists at the pinned commit and GitHub reports no licence for m5stack/M5DinMeter. The README lists MIT only for M5GFX and M5Unified, and 'original' for the bundled PJRC Encoder.",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Demonstrates the most device-specific behaviour there is: timerSleep() programmes the BM8563 alarm and then RELEASES the GPIO46 latch - a power-off with an alarm, not an ESP32 deep sleep",
-    "Comments show all three timerSleep overloads and powerOff()"
-   ],
-   "pitfalls": [
-    "Does not explain why the board dies if GPIO46 is not held - the failure mode most users hit first"
-   ],
-   "selected": true,
-   "selection_reason": "Best example of the board's defining power architecture; a limit-testing example in practice."
-  },
-  {
-   "id": "OFF-05",
-   "title": "buzzer.ino",
-   "author": "SeanKwok (shaoxiang@m5stack.com), M5Stack",
-   "source_class": "primary",
-   "url": "https://github.com/m5stack/M5DinMeter/blob/main/examples/Basic/buzzer/buzzer.ino",
-   "immutable_url": "https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/buzzer/buzzer.ino",
-   "commit": "8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "release": "1.0.0",
-   "file_date": "2024-03-07",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-08-03",
-   "device": "K134 (applies unchanged to K134-V11)",
-   "framework": "Arduino, M5Stack board pkg v2.1.1",
-   "features": [
-    "buzzer"
-   ],
-   "resources": [
-    "GPIO3",
-    "LEDC"
-   ],
-   "dependencies": {
-    "M5DinMeter": "1.0.0",
-    "M5Unified": ">=0.1.13"
-   },
-   "license": "unknown",
-   "license_evidence": "No LICENSE file exists at the pinned commit and GitHub reports no licence for m5stack/M5DinMeter. The README lists MIT only for M5GFX and M5Unified, and 'original' for the bundled PJRC Encoder.",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Minimal; shows tone(freq, ms)"
-   ],
-   "pitfalls": [
-    "Blocking delay(1000) between tones"
-   ],
-   "selected": false,
-   "selection_reason": "Superseded for portfolio purposes by OFF-01, which uses the buzzer in context. Retained for completeness."
-  },
-  {
-   "id": "OFF-06",
-   "title": "button.ino",
-   "author": "SeanKwok (shaoxiang@m5stack.com), M5Stack",
-   "source_class": "primary",
-   "url": "https://github.com/m5stack/M5DinMeter/blob/main/examples/Basic/button/button.ino",
-   "immutable_url": "https://github.com/m5stack/M5DinMeter/blob/8ccbad7297beb82a140f812e5606e060d8a5e0dc/examples/Basic/button/button.ino",
-   "commit": "8ccbad7297beb82a140f812e5606e060d8a5e0dc",
-   "release": "1.0.0",
-   "file_date": "2024-03-07",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-08-03",
-   "device": "K134 (applies unchanged to K134-V11)",
-   "framework": "Arduino, M5Stack board pkg v2.1.1",
-   "features": [
-    "button",
-    "display",
-    "buzzer"
-   ],
-   "resources": [
-    "GPIO42"
-   ],
-   "dependencies": {
-    "M5DinMeter": "1.0.0",
-    "M5Unified": ">=0.1.13"
-   },
-   "license": "unknown",
-   "license_evidence": "No LICENSE file exists at the pinned commit and GitHub reports no licence for m5stack/M5DinMeter. The README lists MIT only for M5GFX and M5Unified, and 'original' for the bundled PJRC Encoder.",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Shows wasPressed/wasReleased"
-   ],
-   "pitfalls": [
-    "Redundant with OFF-01"
-   ],
-   "selected": false,
-   "selection_reason": "Subsumed by OFF-01."
-  },
-  {
-   "id": "OFF-07",
-   "title": "M5DinMeter-UserDemo (factory firmware)",
-   "author": "Forairaaaaa / M5Stack",
-   "source_class": "primary",
-   "url": "https://github.com/m5stack/M5DinMeter-UserDemo",
-   "immutable_url": "https://github.com/m5stack/M5DinMeter-UserDemo/tree/d2fdfe44e9baf810f82335faa6f5962e9fc59a44",
-   "commit": "d2fdfe44e9baf810f82335faa6f5962e9fc59a44",
-   "release": "V0.1",
-   "release_date": "2024-03-04",
-   "retrieved": "2026-09-04",
-   "last_activity": "2024-03-04",
-   "device": "K134 (the shipped image)",
-   "framework": "Arduino via PlatformIO, espressif32@6.3.1, board esp32-s3-devkitc-1",
-   "features": [
-    "display",
-    "encoder",
-    "button",
-    "buzzer",
-    "RTC",
-    "Wi-Fi",
-    "BLE",
-    "GPIO/Grove",
-    "game"
-   ],
-   "resources": [
-    "all board peripherals"
-   ],
-   "dependencies": {
-    "lovyan03/LovyanGFX": "1.1.12",
-    "forairaaaaa/SmoothUIToolKit": "1.0.1"
-   },
-   "license": "MIT (LICENSE, (c) 2024 M5Stack) - MIXED-LICENCE ARCHIVE: bundles PJRC Encoder, ESP32Encoder, I2C_BM8563 and Button, each with its own licence file under lib/",
-   "license_evidence": "LICENSE at repository root; per-library LICENSE / licence.txt under lib/",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "The only complete integrated application",
-    "Contains ft_disp_lgfx_cfg.hpp - the authoritative raw-LovyanGFX panel config (offset 52/40, invert true, 40 MHz write, backlight PWM 200 Hz on channel 7)",
-    "Every dependency pinned, so it should be reproducible",
-    "MIT, so it is a legitimate starting point"
-   ],
-   "pitfalls": [
-    "Uses a generic esp32-s3-devkitc-1 board, not a DinMeter profile",
-    "No partition table specified",
-    "Untouched since 2024-03-04",
-    "Its 200 Hz backlight PWM conflicts with Espressif's 5 kHz"
-   ],
-   "vendored": true,
-   "local_path": "artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz",
-   "selected": true,
-   "selection_reason": "Best integrated application, and the reference for the raw-LovyanGFX path."
-  },
-  {
-   "id": "OFF-08",
-   "title": "espressif/esp-board-manager - m5stack_dinmeter board definition",
-   "author": "Espressif Systems",
-   "source_class": "primary",
-   "url": "https://github.com/espressif/esp-board-manager/tree/main/m5stack_boards/m5stack_dinmeter",
-   "immutable_url": "https://github.com/espressif/esp-board-manager/tree/2beb9b22b0892b343bd555a1ebc9929a7edce8fc/m5stack_boards/m5stack_dinmeter",
-   "commit": "2beb9b22b0892b343bd555a1ebc9929a7edce8fc",
-   "commit_date": "2026-09-03",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-09-03",
-   "device": "K134 (board_info version 1.0.0)",
-   "framework": "ESP-IDF",
-   "features": [
-    "display",
-    "backlight",
-    "encoder (PCNT)",
-    "buzzer (LEDC)",
-    "RTC bus",
-    "power hold",
-    "wake button"
-   ],
-   "resources": [
-    "SPI2_HOST",
-    "LEDC ch0/timer0 + ch1/timer1",
-    "PCNT 1 unit / 2 channels",
-    "I2C port 0",
-    "GPIO46",
-    "GPIO42"
-   ],
-   "dependencies": {
-    "esp-idf": "unspecified; uses the built-in esp_lcd_panel_st7789"
-   },
-   "license": "not verified at file level; esp-board-manager is an Espressif project (their projects are typically Apache-2.0)",
-   "license_evidence": "not checked in this pass - recorded as unverified rather than assumed",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "The most accurate technical description of this board that exists anywhere, vendor documentation included",
-    "Documents the GRAM gap (column +52, row +40) and why the application must apply it",
-    "Documents the two-channel PCNT quadrature pattern and why GPIO40/41 look double-booked",
-    "Documents a real ESP32-S3 build break: en_step_notify_* require SOC_PCNT_SUPPORT_STEP_NOTIFY",
-    "Resolves the vendor pin table's GPIO3-vs-GPIO42 ambiguity by citing M5Unified source",
-    "Explicitly lists what it does NOT model"
-   ],
-   "pitfalls": [
-    "Its Grove wire-colour note derives from M5Stack's disputed PinMap, so it is a reproduction and not independent corroboration",
-    "Does not model the RTC device, the Grove ports, the charger or USB"
-   ],
-   "vendored": true,
-   "local_path": "artifacts/source-snapshots/dinmeter-board_{info,devices,peripherals}.yaml",
-   "selected": true,
-   "selection_reason": "Best maintained and reproducible ESP-IDF starting point; also, in practice, the best documentation."
-  },
-  {
-   "id": "COM-01",
-   "title": "bmorcelli/Launcher - m5stack-dinmeter board target",
-   "author": "Bruno Morcelli",
-   "source_class": "community",
-   "url": "https://github.com/bmorcelli/Launcher/blob/main/boards/m5stack-dinmeter/platformio.ini",
-   "immutable_url": "branch link only - no release was pinned at capture time; content captured 2026-09-04",
-   "commit": "main as of 2026-09-04",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-09-04",
-   "stars": 2054,
-   "device": "K134/K134-V11",
-   "framework": "Arduino via PlatformIO",
-   "features": [
-    "display",
-    "encoder",
-    "battery ADC",
-    "SD card over both Grove ports",
-    "USB CDC"
-   ],
-   "resources": [
-    "GPIO4-9",
-    "GPIO40/41",
-    "GPIO10",
-    "GPIO1/2/13/15"
-   ],
-   "dependencies": {
-    "mathertel/RotaryEncoder": "1.5.3"
-   },
-   "license": "MIT",
-   "license_evidence": "repository LICENSE",
-   "build_status": "not-attempted here, but built by the project's own CI (.github/workflows/main.yml includes { env: \"m5stack-dinmeter\" })",
-   "run_status": "reported-working - distributed as Launcher-m5stack-dinmeter.bin, MD5 bccbefef5284357a2a7c3c7cc196fd98, mapped in support_files/m5burner_post.py",
-   "test_environment": "the project's GitHub Actions matrix",
-   "strengths": [
-    "Independent corroboration of the display pins, the GRAM offsets (52/40 and 53/40), the battery divider ratio 2.0, and the absence of PSRAM",
-    "Demonstrates a software-SPI SD card across BOTH Grove ports (CS=13 SCK=15 MISO=2 MOSI=1) - the only evidenced way to add storage to this board",
-    "Publishes a real partition layout (custom_8Mb.csv, SPIFFS threshold 0x2F0000)",
-    "Actively maintained; last push the day of capture"
-   ],
-   "pitfalls": [
-    "The project README contradicts itself: the port is listed once as [x] and once as [ ] (Beta)",
-    "Uses generic board = esp32s3 rather than a DinMeter profile"
-   ],
-   "vendored": true,
-   "local_path": "artifacts/source-snapshots/launcher-m5stack-dinmeter-platformio.ini",
-   "selected": true,
-   "selection_reason": "Best independent cross-check of the pin map, and a practical limit-testing example for Grove-pin reuse."
-  },
-  {
-   "id": "COM-02",
-   "title": "no-body-in-particular/m5din-hikoki",
-   "author": "no-body-in-particular",
-   "source_class": "community",
-   "url": "https://github.com/no-body-in-particular/m5din-hikoki",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-05-05",
-   "stars": 25,
-   "device": "DinMeter",
-   "framework": "Arduino/C++",
-   "features": [
-    "display",
-    "encoder",
-    "external measurement"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "not recorded at capture",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Most-starred DinMeter application found anywhere",
-    "A real instrument use case: HiKOKI power-tool battery analyser"
-   ],
-   "pitfalls": [
-    "Not inspected in depth in this pass"
-   ],
-   "selected": false,
-   "selection_reason": "Highest-profile community application; catalogued but not read line-by-line."
-  },
-  {
-   "id": "COM-03",
-   "title": "Shark17e/M5DinMeter-KilnController",
-   "author": "Shark17e",
-   "source_class": "community",
-   "url": "https://github.com/Shark17e/M5DinMeter-KilnController",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-08-08",
-   "stars": 1,
-   "device": "DinMeter",
-   "framework": "Arduino/C++",
-   "features": [
-    "display",
-    "encoder",
-    "PID control",
-    "temperature curves"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "NOASSERTION",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "The archetypal use case: a panel-mounted process controller",
-    "Most recently active application project"
-   ],
-   "pitfalls": [
-    "Licence not asserted, so code should not be copied without asking",
-    "Italian-language documentation"
-   ],
-   "selected": false,
-   "selection_reason": "Best illustration of the intended use; not needed for feature coverage.",
-   "created": "2026-08-06"
-  },
-  {
-   "id": "COM-04",
-   "title": "kaz-mac/M5Authenticator",
-   "author": "kaz-mac",
-   "source_class": "community",
-   "url": "https://github.com/kaz-mac/M5Authenticator",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2025-04-26",
-   "stars": 2,
-   "device": "DinMeter",
-   "framework": "Arduino/C++",
-   "features": [
-    "display",
-    "encoder",
-    "RTC",
-    "TOTP"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "MIT",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Uses the RTC for something that genuinely needs accurate time",
-    "Has a DinMeter-specific UI layer (src/DinMeterUI.h) worth reading"
-   ],
-   "pitfalls": [
-    "Japanese-language documentation"
-   ],
-   "selected": false,
-   "selection_reason": "Good RTC-in-anger example; not selected only because coverage was already complete."
-  },
-  {
-   "id": "COM-05",
-   "title": "viniciusbo/m5-palnagotchi",
-   "author": "Vinicius Bo",
-   "source_class": "community",
-   "url": "https://github.com/viniciusbo/m5-palnagotchi",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-01-28",
-   "stars": 81,
-   "device": "DinMeter",
-   "framework": "Arduino/C++",
-   "features": [
-    "display",
-    "Wi-Fi"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "MIT",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Second-most-starred project touching the device"
-   ],
-   "pitfalls": [
-    "DinMeter is one of many targets; nothing DinMeter-specific to learn"
-   ],
-   "selected": false,
-   "selection_reason": "Multi-board project; adds no DinMeter-specific technique.",
-   "created": "2024-02-14",
-   "lineage": "forked by pfefferle/palnagotchi (star 1, 2026-03)"
-  },
-  {
-   "id": "COM-06",
-   "title": "TuF3i/DinMeterDock",
-   "author": "TuF3i",
-   "source_class": "community",
-   "url": "https://github.com/TuF3i/DinMeterDock",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2026-06-27",
-   "stars": 0,
-   "device": "DinMeter",
-   "framework": "C",
-   "features": [
-    "display",
-    "encoder"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "MIT",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Clean hardware-abstraction split (src/Config.h, src/Hardware/Display.h)"
-   ],
-   "pitfalls": [
-    "Chinese-language documentation"
-   ],
-   "selected": false,
-   "selection_reason": "Catalogued.",
-   "created": "2026-06-26"
-  },
-  {
-   "id": "COM-07",
-   "title": "tarmn3/m5dinmeter-ble-volume-knob",
-   "author": "tarmn3",
-   "source_class": "community",
-   "url": "https://github.com/tarmn3/m5dinmeter-ble-volume-knob",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2025-12-10",
-   "stars": 0,
-   "device": "DinMeter",
-   "framework": "Arduino/C++",
-   "features": [
-    "encoder",
-    "BLE HID"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "none declared",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "The only BLE example found for this device"
-   ],
-   "pitfalls": [
-    "No licence declared - do not copy code from it without asking"
-   ],
-   "selected": false,
-   "selection_reason": "Only BLE example, but unlicensed, which makes it a poor thing to point people at for copying."
-  },
-  {
-   "id": "COM-08",
-   "title": "aoiastro/susuFW",
-   "author": "aoiastro",
-   "source_class": "community",
-   "url": "https://github.com/aoiastro/susuFW",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2025-09-26",
-   "stars": 1,
-   "device": "DinMeter",
-   "framework": "unknown",
-   "features": [
-    "multi-function firmware"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "none recorded",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Purpose-built multi-function firmware for this device"
-   ],
-   "pitfalls": [
-    "Not inspected; Japanese-language"
-   ],
-   "selected": false,
-   "selection_reason": "Catalogued."
-  },
-  {
-   "id": "COM-09",
-   "title": "shi78ge/DinMeter-chan",
-   "author": "shi78ge",
-   "source_class": "community",
-   "url": "https://github.com/shi78ge/DinMeter-chan",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "2024-04-15",
-   "stars": 1,
-   "device": "DinMeter",
-   "framework": "Arduino/C++",
-   "features": [
-    "display"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "NOASSERTION",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "Historically the first third-party project, about five weeks after launch"
-   ],
-   "pitfalls": [
-    "Stale since 2024",
-    "Licence not asserted"
-   ],
-   "selected": false,
-   "selection_reason": "Historical interest only.",
-   "created": "2024-04-14"
-  },
-  {
-   "id": "COM-10",
-   "title": "mattytrentini/chipboard - boards/m5stack_din_meter.yaml",
-   "author": "Matt Trentini",
-   "source_class": "community",
-   "url": "https://github.com/mattytrentini/chipboard/blob/main/boards/m5stack_din_meter.yaml",
-   "immutable_url": "branch link only; no commit pinned at capture",
-   "retrieved": "2026-09-04",
-   "last_activity": "unknown",
-   "stars": 0,
-   "device": "DinMeter",
-   "framework": "MicroPython",
-   "features": [
-    "MicroPython board definition"
-   ],
-   "resources": [],
-   "dependencies": {},
-   "license": "not recorded",
-   "license_evidence": "GitHub repository licence field",
-   "build_status": "not-attempted",
-   "run_status": "not-attempted",
-   "test_environment": "none",
-   "strengths": [
-    "The only non-UiFlow MicroPython route found"
-   ],
-   "pitfalls": [
-    "Not evaluated",
-    "Vanilla micropython/micropython has no DinMeter port"
-   ],
-   "selected": false,
-   "selection_reason": "Catalogued as the only generic-MicroPython lead; unverified."
-  },
-  {
-   "id": "REJ-01",
-   "title": "whatnick/din_meter_atm90e26",
-   "author": "whatnick",
-   "source_class": "community",
-   "url": "https://github.com/whatnick/din_meter_atm90e26",
-   "retrieved": "2026-09-04",
-   "device": "NOT THIS DEVICE",
-   "framework": "KiCad + Arduino",
-   "license": "n/a",
-   "build_status": "n/a",
-   "run_status": "n/a",
-   "features": [],
-   "resources": [],
-   "dependencies": {},
-   "strengths": [],
-   "pitfalls": [],
-   "selected": false,
-   "selection_reason": "REJECTED - false positive. An unrelated ATM90E26 DIN-rail energy meter whose Gerber files dominate GitHub code-search results for 'din_meter'. Recorded so the next agent does not re-chase it."
-  },
-  {
-   "id": "REJ-02",
-   "title": "EVerest / SmartEVSE-3 din_msgDefDatatypes.c",
-   "author": "various",
-   "source_class": "community",
-   "url": "https://github.com/EVerest/EVerest",
-   "retrieved": "2026-09-04",
-   "device": "NOT THIS DEVICE",
-   "framework": "C",
-   "license": "n/a",
-   "build_status": "n/a",
-   "run_status": "n/a",
-   "features": [],
-   "resources": [],
-   "dependencies": {},
-   "strengths": [],
-   "pitfalls": [],
-   "selected": false,
-   "selection_reason": "REJECTED - false positive. EV-charging DIN 70121 protocol code matching 'din_'."
-  },
-  {
-   "id": "INA-01",
-   "title": "M5Stack community forum threads",
-   "author": "various",
-   "source_class": "community",
-   "url": "https://community.m5stack.com/search?term=dinmeter",
-   "retrieved": "2026-09-04",
-   "device": "DinMeter",
-   "framework": "n/a",
-   "license": "n/a",
-   "build_status": "n/a",
-   "run_status": "n/a",
-   "features": [],
-   "resources": [],
-   "dependencies": {},
-   "strengths": [],
-   "pitfalls": [],
-   "selected": false,
-   "selection_reason": "INACCESSIBLE - the search API returns HTTP 401 (login required) and the HTML search page is a NodeBB JavaScript shell with no results in the served markup. Blocked, not empty."
-  },
-  {
-   "id": "INA-02",
-   "title": "UiFlow2 DinMeter project",
-   "author": "M5Stack",
-   "source_class": "primary",
-   "url": "https://docs.m5stack.com/en/uiflow2/m5dinmeter/program",
-   "retrieved": "2026-09-04",
-   "device": "DinMeter",
-   "framework": "UiFlow2 / MicroPython",
-   "license": "n/a",
-   "build_status": "n/a",
-   "run_status": "n/a",
-   "features": [],
-   "resources": [],
-   "dependencies": {},
-   "strengths": [],
-   "pitfalls": [],
-   "selected": false,
-   "selection_reason": "INACCESSIBLE as source - UiFlow2 is a browser block editor; the tutorial has no downloadable project file, and the runtime firmware is distributed only through M5Burner with no stable URL."
-  }
- ],
- "counts": {
-  "total": 22,
-  "official": 8,
-  "community": 10,
-  "rejected": 2,
-  "inaccessible": 2,
-  "selected": 7,
-  "vendored": 3,
-  "built_here": 0,
-  "hardware_tested_here": 0
- }
-}
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter/examples/search-log.md b/devices/m5stack/dinmeter/examples/search-log.md
deleted file mode 100644
index c0fb4da..0000000
--- a/devices/m5stack/dinmeter/examples/search-log.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# DinMeter — example search log
-
-**Snapshot 2026-09-04.** Every search that contributed to [`catalog.json`](catalog.json),
-including the ones that returned nothing.
-
-## Official sources
-
-| Source | Method | Result |
-|---|---|---|
-| `m5stack/M5DinMeter` `examples/` | tarball @ `8ccbad7297beb82a140f812e5606e060d8a5e0dc` | **6 examples**, all under `examples/Basic/`, all dated 2024-03-07 |
-| `m5stack/M5DinMeter-UserDemo` | tarball @ `d2fdfe44e9baf810f82335faa6f5962e9fc59a44` | **1 integrated application** with 8 test components |
-| `docs.m5stack.com/en/arduino/m5dinmeter/*` | 9 pages fetched, all HTTP 200 | Tutorial prose mirroring the six examples plus `battery`, `wifi`, `program` |
-| `docs.m5stack.com/en/uiflow2/m5dinmeter/program` | fetched, HTTP 200 | UiFlow2 tutorial (block-based; no downloadable source project) |
-| `espressif/esp-board-manager` | raw fetch @ `2beb9b22b0892b343bd555a1ebc9929a7edce8fc` | **3 YAML board files** — not "examples" but the single best reference configuration |
-
-## Community searches
-
-| Query | Endpoint | Results | Kept |
-|---|---|---:|---:|
-| `DinMeter in:name,description,readme` | GitHub repo search, 50/page | 19 | 13 |
-| `DinMeter` | GitHub repo search | 5 | — (subset) |
-| `M5DinMeter` | GitHub repo search | 6 | — (subset) |
-| `din meter m5stack` | GitHub repo search | 2 | — (subset) |
-| `M5DinMeter extension:h` | GitHub code search | 9 files / 6 repos | 4 new |
-| `DinMeter in:file language:yaml` | GitHub code search | 94 | 3 (rest are false positives) |
-| `din_meter` | GitHub code search | 109 | 1 (dominated by `whatnick/din_meter_atm90e26`, unrelated) |
-| `repo:bmorcelli/Launcher dinmeter` | GitHub code search | 6 | 1 repo, high value |
-| `repo:esphome/esphome dinmeter` | GitHub code search | **0** | — |
-| `repo:arendst/Tasmota dinmeter` | GitHub code search | **0** | — |
-| `repo:meshtastic/firmware dinmeter` / `din_meter` | GitHub code search | **0** / **0** | — |
-| `repo:pr3y/Bruce dinmeter` | GitHub code search | **0** | — |
-| `DinMeter`, `Din Meter M5Stack`, `M5Stack knob DIN`, `subreddit:M5Stack dinmeter` | `old.reddit.com/search.json` | ~200 inspected | 1 (marketing) |
-| `dinmeter` | `community.m5stack.com` API + HTML | **HTTP 401** / JS shell | **blocked** |
-
-## Deduplication and lineage
-
-- **6 Launcher forks** (`notyetaperson/Evilware`, `darkLabz001/Dark-Div-Launcher`,
-  `TeslaDeathStar/ESP32-Launcher-ES3C28P`, `ry-ops/tab5-launcher`,
-  `JunFactorya04/M-5Laucher{,2}`) inherit the DinMeter board file from `bmorcelli/Launcher`.
-  Catalogued once, with lineage noted; not counted as independent examples.
-- `pfefferle/palnagotchi` is a fork of `viniciusbo/m5-palnagotchi`. Lineage recorded.
-
-## Naming traps that cost time
-
-| Trap | Cost |
-|---|---|
-| `din_meter` → `whatnick/din_meter_atm90e26` (unrelated ATM90E26 energy meter, ~15 Gerber files) | ~40 % of one code-search page |
-| `din_meter` → EV-charging **DIN 70121** (`din_msgDefDatatypes.c`, EVerest / SmartEVSE) | noise |
-| "DIN meter" on Reddit → **ski-binding release settings** (r/Skigear) | 1 of 2 relevant-looking hits |
-| Bruce vs Launcher | `pr3y/Bruce` has **no** DinMeter support; `bmorcelli/Launcher` does |
-
-## Declared exclusions
-
-No video, blog, Hackaday.io, Chinese-platform, or package-registry-wide search was performed.
-The vendor forum was inaccessible. See [`../research-log.md`](../research-log.md) §9.
-
-## Build status
-
-**Zero examples were built, statically validated or run.** No toolchain was installed and no
-hardware was available. Every catalogue entry's `build_status` is `not-attempted`.
diff --git a/devices/m5stack/dinmeter/factory-firmware.md b/devices/m5stack/dinmeter/factory-firmware.md
deleted file mode 100644
index 6c4249f..0000000
--- a/devices/m5stack/dinmeter/factory-firmware.md
+++ /dev/null
@@ -1,150 +0,0 @@
-# DinMeter — factory firmware
-
-Applies to K134 and K134-V11. **Nothing here was flashed or executed.**
-
----
-
-## 1. Summary
-
-| Field | Value |
-|---|---|
-| What ships on it | The **M5DinMeter UserDemo** hardware-evaluation firmware |
-| Source | <https://github.com/m5stack/M5DinMeter-UserDemo> — **open, MIT** |
-| Source commit analysed | `d2fdfe44e9baf810f82335faa6f5962e9fc59a44` (repo HEAD, last push 2024-03-04) |
-| Release | `V0.1`, published 2024-03-04 |
-| Target MCU | ESP32-S3 (`esp32s3`), 8 MB flash, **no PSRAM** |
-| Framework | Arduino via PlatformIO, `platform = espressif32@6.3.1` |
-| CPU | `board_build.f_cpu = 240000000L` |
-| Board profile used by the vendor | **`esp32-s3-devkitc-1`** — a generic S3 board, not a DinMeter profile |
-| Distribution of the **binary** | **M5Burner only** — "DinMeter User Demo Easyloader" on both product pages |
-| ⚠ Prebuilt binary URL | **None located.** M5Burner resolves images at run time from an undocumented endpoint |
-| Local snapshot | [`artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz`](artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44e9baf810f82335faa6f5962e9fc59a44.tar.gz) — 74 231 B, SHA-256 `af58e2cdaf565bb3f97daeadd02843a4cd3dc72f504446aa842d865eb9c4ec72` |
-
-> **⚠ Back up before you overwrite.** There is no vendor-published factory image with a stable
-> URL. If you flash your own firmware without reading the flash out first, the *binary* is gone —
-> though the **source is public and MIT-licensed**, so you can rebuild an equivalent. That is a
-> materially better position than most vendor firmware. See §5.
-
-## 2. What it does
-
-`src/main.cpp` is 24 lines: construct a `FactoryTest`, call `init()`, then a view loop. The
-substance is in `src/factory_test/components/`:
-
-| Component | Tests |
-|---|---|
-| `ft_disp_test.cpp` | display |
-| `ft_key_test.cpp` | encoder button / keys |
-| `ft_io_test.cpp` | GPIO / Grove ports |
-| `ft_rtc_test.cpp` | BM8563 RTC |
-| `ft_wifi_test.cpp` | Wi-Fi scan/connect |
-| `ft_ble_test.cpp` | BLE |
-| `ft_arkanoid.cpp` | a playable Arkanoid — the demo that shows off the knob |
-| `ft_disp_lgfx_cfg.hpp` | the LovyanGFX panel configuration |
-
-Plus a `src/view/` UI layer with PNG assets converted to headers (`bat_panel`,
-`icon_brightness`, `icon_display`, …).
-
-## 3. The panel configuration — the most reusable thing in it
-
-`src/factory_test/components/ft_disp_lgfx_cfg.hpp`, verbatim values:
-
-```cpp
-#define LCD_MOSI_PIN 5   #define LCD_SCLK_PIN 6   #define LCD_DC_PIN  4
-#define LCD_CS_PIN   7   #define LCD_RST_PIN  8   #define LCD_BL_PIN  9
-#define LCD_MISO_PIN -1  #define LCD_BUSY_PIN -1
-
-lgfx::Panel_ST7789 _panel_instance;
-lgfx::Bus_SPI      _bus_instance;
-lgfx::Light_PWM    _light_instance;
-
-cfg.freq_write   = 40000000;      // 40 MHz
-cfg.invert       = true;          // INVON
-cfg.panel_width  = 135;  cfg.panel_height = 240;
-cfg.offset_x     = 52;   cfg.offset_y     = 40;     // the GRAM gap
-// backlight:
-cfg.pin_bl = 9; cfg.invert = false; cfg.freq = 200; cfg.pwm_channel = 7;
-```
-
-Note `lgfx::Panel_ST7789` — **the generic ST7789 panel class**, not a V2-specific one. That is
-one reason to expect the v1.1 ST7789P3 to behave the same.
-
-Note also `freq = 200` for the backlight PWM, where Espressif's board definition uses 5 kHz. See
-[`compatibility-and-status.md`](compatibility-and-status.md) §6.
-
-## 4. Licensing
-
-| Item | Licence | Evidence |
-|---|---|---|
-| `M5DinMeter-UserDemo` itself | **MIT**, © 2024 M5Stack | `LICENSE` in the repository |
-| `lib/Button/` | has its own `LICENSE` | bundled |
-| `lib/ESP32Encoder/` | `licence.txt` | bundled |
-| `lib/I2C_BM8563/` | has its own `LICENSE` | bundled |
-| `lib/` vendored trees generally | **mixed-licence** | the archive's own MIT does not cover its bundled dependencies |
-| PNG/asset headers | not separately licensed | assumed to follow the project MIT |
-| **The compiled binary** distributed via M5Burner | terms not stated | — |
-
-Redistribution status of the **source snapshot**: `allowed` (MIT), with the standard obligation
-to preserve the notice — the retained tarball contains `LICENSE` unmodified. Disposition:
-`repository`.
-
-Redistribution status of the **binary**: `unknown` — it could not be obtained.
-
-## 5. Backing up and restoring — all `not-tested`
-
-```bash
-# 1. Enter download mode: hold G0 on the Stamp module, apply power, release G0.
-#    (reported-working -- vendor instruction, both product pages)
-
-# 2. Read the whole 8 MB flash out BEFORE doing anything else.
-esptool.py --chip esp32s3 -p /dev/ttyACM0 -b 460800 \
-    read_flash 0 0x800000 dinmeter-factory-backup.bin        # not-tested
-
-sha256sum dinmeter-factory-backup.bin                        # record it
-
-# 3. Restore later
-esptool.py --chip esp32s3 -p /dev/ttyACM0 -b 460800 \
-    write_flash 0 dinmeter-factory-backup.bin                # not-tested
-```
-
-**Or rebuild from source** — the better option, and available because M5Stack open-sourced it:
-
-```bash
-git clone https://github.com/m5stack/M5DinMeter-UserDemo
-cd M5DinMeter-UserDemo
-git checkout d2fdfe44e9baf810f82335faa6f5962e9fc59a44
-pio run -e esp32-s3-devkitc-1 -t upload                      # not-tested
-```
-`platform`, `LovyanGFX 1.1.12` and `SmoothUIToolKit 1.0.1` are all pinned in the project file, so
-this should be reproducible. **Not verified.**
-
-**Or reflash the vendor image** with M5Burner → search "DinMeter" → *DinMeter User Demo
-Easyloader*. `reported-working` — this is the vendor's documented route, not tested here.
-
-## 6. Image metadata — mostly unknown
-
-| Field | Value |
-|---|---|
-| Version/build identifier | **unknown** — the binary was not obtained; the *source* release is `V0.1` |
-| Build date | unknown |
-| SHA-256 of the shipped image | **unknown** |
-| Byte size | unknown |
-| Flash offsets | not published; PlatformIO's `esp32-s3-devkitc-1` defaults apply to this project |
-| Partition table | **not published**. The project file sets no `board_build.partitions` |
-| Bootloader | stock ESP-IDF second-stage, framework-supplied |
-| Companion images | unknown |
-
-**This is a genuine gap**, recorded rather than glossed: without the binary there is no hash to
-compare a dumped flash against.
-
-## 7. Third-party alternative
-
-`bmorcelli/Launcher` ships `Launcher-m5stack-dinmeter.bin` through the same M5Burner channel,
-with a published MD5 (`bccbefef5284357a2a7c3c7cc196fd98`, from
-`support_files/m5burner_post.py`). Its partition layout **is** published:
-`support_files/custom_8Mb.csv`, `maximum_size = 8388608`, SPIFFS threshold `0x2F0000`. See
-[`projects-and-community.md`](projects-and-community.md) §2.
-
-## Related
-
-[`development.md`](development.md) · [`examples/best.md`](examples/best.md) ·
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) §7
diff --git a/devices/m5stack/dinmeter/features/README.md b/devices/m5stack/dinmeter/features/README.md
deleted file mode 100644
index 8878578..0000000
--- a/devices/m5stack/dinmeter/features/README.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# DinMeter — feature guides
-
-Task-oriented guides, one per capability. Each answers a natural question and states its
-evidence status, applicable revisions and framework versions.
-
-Applies to **K134 and K134-V11** unless a guide says otherwise — the two boards share a
-byte-identical published schematic and an identical GPIO map.
-
-| Guide | Question it answers | Hardware |
-|---|---|---|
-| [`rotary-encoder-and-buttons.md`](rotary-encoder-and-buttons.md) | How do I read the orange knob and its press? | encoder on `J5` → GPIO41/40/42 |
-| [`display.md`](display.md) | How do I draw on the screen and dim it? | ST7789V2/P3 on `FPC1` → GPIO4-9 |
-| [`rtc-and-timekeeping.md`](rtc-and-timekeeping.md) | How do I keep time and wake on a schedule? | BM8563 `U5` → GPIO11/12 |
-| [`buzzer.md`](buzzer.md) | How do I make it beep? | `LS1` via `Q5` → GPIO3 |
-| [`power-and-battery.md`](power-and-battery.md) | How do I run it from 24 V or a cell, and why does it keep switching off? | `U1`/`U2`/`U3`/`U4`, latch on GPIO46 |
-| [`porta-portb-expansion.md`](porta-portb-expansion.md) | How do I hang a sensor off the Grove ports? | `J3`/`J4` → GPIO13/15 and GPIO1/2 |
-| [`wifi-and-ble.md`](wifi-and-ble.md) | How do I get on the network? | ESP32-S3 radio + module antenna |
-| [`rgb-led.md`](rgb-led.md) | How do I light the status LED — and why doesn't it work on v1.1? | WS2812B-2020 inside the Stamp, GPIO21 (+GPIO38 on v1.1) |
-| [`din-mounting-and-mechanical.md`](din-mounting-and-mechanical.md) | How do I mount it in a panel? | 1/32 DIN, 45 × 22.5 mm cutout |
-
-**Global evidence caveat.** No DinMeter hardware was available for this research pass. Code in
-these guides is `inferred` or `reported-working` (i.e. it is the vendor's own example code)
-unless a line says otherwise. None of it was compiled or run here.
-
-See also [`../coverage.md`](../coverage.md) for the feature → evidence → gap matrix, and
-[`../resources-and-conflicts.md`](../resources-and-conflicts.md) for what collides with what.
diff --git a/devices/m5stack/dinmeter/features/buzzer.md b/devices/m5stack/dinmeter/features/buzzer.md
deleted file mode 100644
index a6b49a4..0000000
--- a/devices/m5stack/dinmeter/features/buzzer.md
+++ /dev/null
@@ -1,129 +0,0 @@
-# How do I make the DinMeter beep?
-
-**Applies to:** K134 and K134-V11 (identical).
-**Evidence status:** wiring `executed-success` from the schematic; GPIO confirmed by two
-independent sources; code `reported-working` (vendor examples). **Last verified:** 2026-09-04.
-
----
-
-## Hardware path
-
-```
-ESP32-S3 GPIO3 ──"beep"──► R25 470Ω ──► Q5 SS8050 (NPN, low-side) ──► LS1 buzzer ──► +5VIN
-                                                                        D6 1N4148WT flyback
-```
-
-The flyback diode across `LS1` means this is an **electro-magnetic (inductive) buzzer, not a
-piezo**. It is **passive**: it needs a square wave. Writing a DC level makes one click.
-
-Component: [`components/unidentified/m5stack-dinmeter/buzzer`](../../../../components/unidentified/m5stack-dinmeter/buzzer/README.md)
-— the part number is not published.
-
-## Which GPIO — and why that needed checking
-
-The vendor PinMap renders `BEEP` (G3) and `BTN(WAKE)` (G42) in adjacent rows of the same table,
-which is easy to misread. Espressif's board definition flags exactly this and resolves it from
-M5Unified:
-
-> *"The vendor pin table renders GPIO3 and GPIO42 in adjacent rows; M5Unified settles it:
-> `board_M5DinMeter` sets `spk_cfg.pin_data_out = GPIO_NUM_3` with `spk_cfg.buzzer = true`
-> (`M5Unified.cpp`, `_set_speaker` branch), and reads the encoder button as
-> `!gpio_in(GPIO_NUM_42)` (`_update_button_state`)."*
-
-The schematic agrees: `M1` pad 3 = `G3`, net `beep`. **Buzzer = GPIO3. Button = GPIO42.**
-
-## Arduino
-
-```cpp
-#include "M5DinMeter.h"
-void setup() {
-    auto cfg = M5.config();
-    DinMeter.begin(cfg, true);
-}
-void loop() {
-    DinMeter.Speaker.tone(10000, 100);   // 10 kHz for 100 ms
-    delay(1000);
-    DinMeter.Speaker.tone(4000, 20);     // 4 kHz for 20 ms
-    delay(1000);
-}
-```
-Verbatim from `M5DinMeter/examples/Basic/buzzer/buzzer.ino` (release 1.0.0).
-`reported-working`.
-
-`DinMeter.Speaker` is a reference to `M5.Speaker`, a `Speaker_Class` (`M5DinMeter.h:24`), which
-M5Unified configures for this board as:
-
-```cpp
-// M5Unified/src/M5Unified.cpp:2921-2928
-case board_t::board_M5Dial:
-case board_t::board_M5DinMeter:
-  if (cfg.internal_spk) {
-    spk_cfg.pin_data_out  = GPIO_NUM_3;
-    spk_cfg.buzzer        = true;
-    spk_cfg.magnification = 48;
-  }
-  break;
-```
-
-`buzzer = true` puts `Speaker_Class` into square-wave mode rather than PWM-audio mode, so
-`tone()` works but `playWav()` / `playRaw()` will be a buzz, not speech. `magnification = 48`
-is the vendor's volume scaling.
-
-Useful idiom, from `encoder.ino` — a 20 ms click at 8 kHz per detent gives the knob tactile
-audio feedback:
-```cpp
-if (newPosition != oldPosition) DinMeter.Speaker.tone(8000, 20);
-```
-
-## ESP-IDF
-
-There is no "buzzer" abstraction; use **LEDC**. Espressif's board definition supplies the
-configuration and explains why:
-
-> *"A passive buzzer is driven by a PWM tone, so the LEDC channel is the peripheral; there is no
-> bmgr buzzer device type, and `ledc_ctrl` models a duty percentage rather than a frequency."*
-
-| Field | Value |
-|---|---|
-| `gpio_num` | 3 |
-| `channel` | `LEDC_CHANNEL_1` |
-| `timer_sel` | `LEDC_TIMER_1` |
-| `freq_hz` | 4000 (starting point; change per note) |
-| `duty` | 0 (silent until you raise it) |
-| `duty_resolution` | `LEDC_TIMER_10_BIT` |
-| `speed_mode` | `LEDC_LOW_SPEED_MODE` |
-
-Change pitch with `ledc_set_freq()`, change loudness with duty (50 % is loudest for a square
-wave). `inferred` for the loudness statement.
-
-## Frequencies
-
-The vendor's own examples use **4 000 Hz**, **8 000 Hz** and **10 000 Hz**. The buzzer's
-resonant frequency — where it is loudest — is **not published**, and a magnetic buzzer's output
-falls off sharply away from resonance. If loudness matters, sweep and measure. `not-tested`.
-
-## Resource cost and conflicts
-
-| Resource | Used |
-|---|---|
-| GPIO | 3 |
-| LEDC | channel 1 + **timer 1** |
-
-⚠ **The backlight also wants LEDC** (channel 0, timer 0). They are on different timers by
-design, so both work together — but if you write your own LEDC setup, do not put the backlight
-and the buzzer on the same timer: changing the buzzer's frequency would change the backlight's
-PWM frequency too. This is the only real resource conflict on the board. See
-[`../resources-and-conflicts.md`](../resources-and-conflicts.md).
-
-**Power note.** `LS1` is driven from `+5VIN`. On battery-only operation that rail comes from a
-boost; expect the buzzer to be quieter and to load the boost during a tone.
-
-## Pitfalls
-
-| Symptom | Cause |
-|---|---|
-| One click, then silence | DC level instead of a square wave — it is a passive buzzer |
-| Silent | `cfg.internal_spk` disabled, or duty still 0 |
-| Backlight flickers when the buzzer sounds | you put both on the same LEDC timer |
-| Very quiet | off resonance, or running on battery |
-| Tone blocks the UI | `Speaker.tone()` is non-blocking in M5Unified; `delay()` after it is what blocks |
diff --git a/devices/m5stack/dinmeter/features/din-mounting-and-mechanical.md b/devices/m5stack/dinmeter/features/din-mounting-and-mechanical.md
deleted file mode 100644
index 2f210f1..0000000
--- a/devices/m5stack/dinmeter/features/din-mounting-and-mechanical.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# How do I mount the DinMeter?
-
-**Applies to:** K134 and K134-V11 — **byte-identical published STL** (SHA-256 `90f04d6a…`), same
-53 × 30 × 32 mm body, same cutout.
-**Evidence status:** dimensions from the vendor drawing and specification tables; **no unit was
-physically fitted to a panel here**. **Last verified:** 2026-09-04.
-
----
-
-## "DIN" here means the panel cutout, not the rail
-
-This is the single most common misunderstanding about the product, and it costs people money.
-
-| | What it means | Does the DinMeter do it? |
-|---|---|---|
-| **1/32 DIN** (DIN 43700 panel-cutout series) | A standard **aperture** cut into a panel: **45 × 22.5 mm** | **Yes — this is the product** |
-| **DIN rail** (TS-35 / EN 60715 hat rail) | The 35 mm rail inside a cabinet that breakers clip onto | **No.** M5Stack's rail-mount product is the StamPLC |
-
-The 1/32 DIN aperture is the size a generation of panel meters and temperature controllers
-(Omron E5C, Autonics TZN, Fuji PXR and their many imitators) used, so it exists — already cut,
-already wired, often already fed with 24 V — in a very large installed base of machine consoles,
-process racks and cabinet doors. **Dropping a modern Wi-Fi UI into that hole with no panel work
-is the entire product thesis.**
-
-## Numbers
-
-| Property | Value | Source |
-|---|---|---|
-| Panel cutout | **45.0 × 22.5 mm** (1/32 DIN) | both product pages, Features list |
-| Body | **53.0 × 30.0 × 32.0 mm** | both spec tables |
-| Weight | 17.8 g | both spec tables |
-| Depth behind the panel | ~32 mm minus the bezel — **allow ~35 mm clear** including the DC terminal and Grove cables | `inferred` from the body depth; the drawing was not dimensioned to a bezel line here |
-| Package (v1.0) | 136.0 × 93.0 × 23.0 mm, 47.0 g gross | v1.0 spec table |
-| Package (v1.1) | 136.0 × 95.0 × 24.0 mm, 44.9 g gross | v1.1 spec table |
-| Operating temperature | **0 – 40 °C** | both spec tables |
-
-Vendor drawing: [`../artifacts/mechanical/K134-din_meter_asm_v1-dimensions.pdf`](../artifacts/mechanical/K134-din_meter_asm_v1-dimensions.pdf)
-(117 405 B, SHA-256 `db42c8a995b6d0bf…`).
-3D model: [`../artifacts/mechanical/DinMeter.stl`](../artifacts/mechanical/DinMeter.stl)
-(573 284 B, SHA-256 `90f04d6a0ae2cbb6…`) — use it for clearance checks, not for tolerancing.
-
-## Two mounting methods
-
-The v1.1 page states them explicitly; the v1.0 bundle contains the same means under different
-names.
-
-| Method | Bundled part | When to use |
-|---|---|---|
-| **Screw-hole fixation** | v1.0 "back bracket" / v1.1 "plastic back clip" | Permanent installs, anything that vibrates, anything a person will push against |
-| **Double-sided adhesive** | adhesive tape (both bundles) | Thin panels, prototypes, non-load-bearing faces |
-
-Use the clip for anything real. A 17.8 g device on a machine that vibrates will eventually part
-company with adhesive tape, and it will take its 24 V wiring with it.
-
-## Connectors and clearances
-
-Everything is on the back:
-
-| Item | Note |
-|---|---|
-| **DC screw terminal** `J1` (2-pin 2.54 mm, `DB2EK-2.54-2P-GN-S`, green) | 6–36 V. **Strain-relieve it** — it is a screw terminal on a small body |
-| USB-C | on the Stamp module; used for flashing and 5 V |
-| PORT.A / PORT.B | HY2.0-4P, need ~10 mm of cable bend radius each |
-| Battery | 1.25 mm 2-pin JST-style; the bundled cell tucks inside |
-| Back clip | removable |
-
-**Plan for depth.** Body depth plus a right-angle DC wire plus two Grove cables is realistically
-45–55 mm behind the panel face. In a shallow door, check before you commit.
-
-## Environmental reality check
-
-- **0 – 40 °C is narrow.** A sealed cabinet in summer sun exceeds it; an unheated outbuilding in
-  winter goes below it. Neither is a "maybe" — it is outside the vendor's stated range.
-- **No IP rating is published.** There is no gasket in the bundle and none is mentioned. Treat
-  the front face as **not sealed**: no washdown, no coolant mist, no dust-laden air without
-  your own gasket.
-- The Wi-Fi antenna is **behind the panel**, inside whatever the enclosure is made of. If that is
-  steel, expect attenuation — see [`wifi-and-ble.md`](wifi-and-ble.md).
-
-## Pitfalls
-
-| Mistake | Consequence |
-|---|---|
-| Buying it expecting DIN-rail mounting | It does not clip to a rail. Buy a StamPLC |
-| Not checking rear depth | It will not close the door |
-| Adhesive mounting on a vibrating machine | It falls out |
-| Assuming an IP rating | None is published |
-| 36 V continuous | `C24`, the buck input capacitor, is rated **35 V**. Treat 36 V as absolute maximum; see [`power-and-battery.md`](power-and-battery.md) |
-| Deploying outside 0–40 °C | Outside spec |
-
-## Unresolved
-
-- **Bezel dimensions and panel-thickness range are not published.** The maximum panel thickness
-  the clip accommodates is unknown. Measure before ordering for a specific panel.
-- No IP/NEMA rating published.
-- No vibration or shock rating published.
-- The published STL is **identical for v1.0 and v1.1**, so it cannot be used to detect any
-  mechanical revision — see [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md) §3.
diff --git a/devices/m5stack/dinmeter/features/display.md b/devices/m5stack/dinmeter/features/display.md
deleted file mode 100644
index a1eccc0..0000000
--- a/devices/m5stack/dinmeter/features/display.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# How do I draw on the DinMeter's screen?
-
-**Applies to:** K134 (**ST7789V2**) and K134-V11 (**ST7789P3**) — identical pins, identical
-resolution, identical driver path.
-**Evidence status:** pin assignments and panel geometry `executed-success` from three
-independent sources that agree exactly; code `reported-working` (vendor-published) or
-`inferred`. **Last verified:** 2026-09-04.
-
----
-
-## Hardware path
-
-```
-ESP32-S3  SPI2_HOST ──► FPC1 (FPC-0.5-8P) ──► 1.14" IPS 135×240, ST7789V2 (v1.0) / ST7789P3 (v1.1)
-   GPIO6 SCLK, GPIO5 MOSI, GPIO7 CS, GPIO4 D/C, GPIO8 RESET     [no MISO — write-only]
-   GPIO9 ──► U6 AW35122FDR load switch ──► FPC1 pin 8 ──► backlight LED string
-```
-
-Components: [`sitronix/st7789v2`](../../../../components/sitronix/st7789v2/README.md) ·
-[`sitronix/st7789p3`](../../../../components/sitronix/st7789p3/README.md) ·
-[`awinic/aw35122`](../../../../components/awinic/aw35122/README.md)
-
-## The three numbers that matter
-
-Three independent sources agree, which is why these can be stated flatly:
-
-| Setting | Value | M5Stack's own factory firmware | Espressif's board definition |
-|---|---|---|---|
-| **GRAM offset** | **x +52, y +40** | `cfg.offset_x = 52; cfg.offset_y = 40;` | *"column +52, row +40"*, applied via the panel gap API |
-| **Colour inversion** | **on** (`INVON`, 0x21) | `cfg.invert = true;` | `invert_color: true` — *"ST7789V2 panel on M5Stack needs inversion"* |
-| **SPI write clock** | **40 MHz** | `cfg.freq_write = 40000000;` | `pclk_hz: 40000000` |
-
-Sources: `m5stack/M5DinMeter-UserDemo` `src/factory_test/components/ft_disp_lgfx_cfg.hpp`
-(commit `d2fdfe44e9baf810f82335faa6f5962e9fc59a44`), and
-`espressif/esp-board-manager` `board_devices.yaml` (`2beb9b22b…`).
-
-**Get the offset wrong and the image is displaced and wraps.** It is the single most common
-ST7789-on-a-small-panel bug.
-
-## Panel geometry
-
-| Property | Value |
-|---|---|
-| Physical | 1.14 in IPS |
-| Native orientation | **135 wide × 240 tall** (portrait) |
-| Controller GRAM | 240 × 320 — the panel is a window inside it |
-| Colour | 16 bpp RGB565 |
-| Vendor examples' rotation | `setRotation(1)` → **240 × 135 landscape**, which is how the product is used |
-| MISO | not wired — you **cannot read** the framebuffer or the controller back |
-
----
-
-## Arduino — M5DinMeter / M5GFX
-
-```cpp
-#include "M5DinMeter.h"
-void setup() {
-    auto cfg = M5.config();
-    DinMeter.begin(cfg, false);            // display comes up inside M5.begin()
-    DinMeter.Display.setRotation(1);       // 240x135 landscape
-    DinMeter.Display.setBrightness(128);   // 0..255, drives GPIO9 PWM
-    DinMeter.Display.setTextColor(GREEN);
-    DinMeter.Display.setTextDatum(middle_center);
-    DinMeter.Display.setTextFont(&fonts::Orbitron_Light_32);
-    DinMeter.Display.drawString("42.0 V",
-        DinMeter.Display.width()/2, DinMeter.Display.height()/2);
-}
-```
-Adapted from `M5DinMeter/examples/Basic/display/display.ino` and `button.ino`
-(release 1.0.0). `reported-working`.
-
-`DinMeter.Display` is a reference to `M5.Display` (`M5DinMeter.h:20`), i.e. an `M5GFX` — the
-full LovyanGFX API: `fillRect`, `drawCircle`, sprites (`M5Canvas`), `pushImage`, `drawPng`,
-fonts, `startWrite`/`endWrite` batching.
-
-**Raw LovyanGFX** (no M5Unified) is also viable and is what the factory firmware does — see
-`ft_disp_lgfx_cfg.hpp`, which builds a `LGFX_Device` with `Panel_ST7789` + `Bus_SPI` +
-`Light_PWM`. Pinned at `lovyan03/LovyanGFX @ 1.1.12`.
-
-## Backlight
-
-| Path | Detail |
-|---|---|
-| M5GFX | `Display.setBrightness(0..255)` |
-| Factory firmware | `Light_PWM`, `pin_bl = 9`, `invert = false`, **`freq = 200`**, `pwm_channel = 7` |
-| esp-board-manager | LEDC **channel 0, timer 0, 5 kHz, 10-bit**, `default_percent: 100` |
-
-⚠ **The two vendor-adjacent sources disagree on PWM frequency: 200 Hz vs 5 kHz.** Both work —
-200 Hz can be visible as flicker to some people and in video; 5 kHz cannot. Neither is
-authoritative over the other. Pick 5 kHz unless you have a reason not to. `not-tested`.
-
-The backlight is *off* at reset: the AW35122FDR's `EN` has an internal ~7.1 MΩ pull-down, so
-nothing lights until firmware drives GPIO9. That is why there is no white flash at boot.
-
-## ESP-IDF
-
-`esp_lcd_panel_st7789` is built into ESP-IDF; no extra component is needed (Espressif's board
-definition says so explicitly). Bus: `SPI2_HOST`, `max_transfer_sz: 6480` (= 135 × 24 lines ×
-2 bytes). Then:
-
-```c
-esp_lcd_panel_set_gap(panel, 52, 40);      // ← the offset
-esp_lcd_panel_invert_color(panel, true);   // ← INVON
-```
-`inferred` from the board definition's own comment that *"bmgr's display model has no offset
-field; the application applies it via the panel gap API."*
-
-## Resource cost and conflicts
-
-| Resource | Used |
-|---|---|
-| GPIO | 4, 5, 6, 7, 8 (bus) + 9 (backlight) |
-| SPI host | `SPI2_HOST` — the *only* SPI peripheral used on this board, so it is yours alone |
-| LEDC | 1 channel + 1 timer for the backlight; the buzzer wants another (ch 1/timer 1) |
-| DMA | optional; `max_transfer_sz` 6480 suggests a 24-line band buffer |
-| RAM | 135 × 240 × 2 = **64 800 B** for a full framebuffer. **There is no PSRAM**, so a full-screen sprite is ~63 KB of the ESP32-S3's ~512 KB SRAM. Band buffers are the sensible default |
-
-**No conflicts** with the encoder, RTC, buzzer or Grove ports. Display + Wi-Fi + encoder + RTC
-simultaneously is fine; the constraint is SRAM, not pins.
-
-## Pitfalls
-
-| Symptom | Cause |
-|---|---|
-| Image shifted and wrapping | GRAM gap not set to (52, 40) |
-| Colours inverted | `INVON` not applied |
-| Nothing visible, backlight dark | GPIO9 never driven; `EN` pull-down keeps the switch off |
-| Reads return garbage | MISO is not wired — the panel is write-only. Keep your own shadow buffer |
-| Tearing on fast updates | no TE line is wired; use sprites/band buffers and `startWrite`/`endWrite` |
-| Portrait when you wanted landscape | `setRotation(1)` |
-
-## Unresolved
-
-- **ST7789P3 has no datasheet.** Command-compatibility with ST7789V2 is assumed, not verified.
-  See [`components/sitronix/st7789p3`](../../../../components/sitronix/st7789p3/README.md).
-- No measured frame rate at 40 MHz for this panel. Nothing was benchmarked. See
-  [`../performance.md`](../performance.md).
diff --git a/devices/m5stack/dinmeter/features/porta-portb-expansion.md b/devices/m5stack/dinmeter/features/porta-portb-expansion.md
deleted file mode 100644
index defeb7a..0000000
--- a/devices/m5stack/dinmeter/features/porta-portb-expansion.md
+++ /dev/null
@@ -1,97 +0,0 @@
-# How do I connect things to PORT.A and PORT.B?
-
-**Applies to:** K134 and K134-V11 (identical).
-**Evidence status:** GPIO assignments `executed-success` (schematic + M5Unified agree); wire
-colours **unresolved** — see the warning. **Last verified:** 2026-09-04.
-
----
-
-## What you get
-
-Two HY2.0-4P ("Grove") sockets on the back:
-
-| Port | Connector | Signals | GPIO | Intended for | Rail |
-|---|---|---|---|---|---|
-| **PORT.A** (red) | `J3` `HY-2.0_IIC` | `IIC_SCL`, `IIC_SDA` | **15**, **13** | I²C units | `+5VOUT` |
-| **PORT.B** (black) | `J4` `HY-2.0_IO` | `GI`, `GO` | **1**, **2** | plain GPIO / ADC / PWM | `+5VOUT` |
-
-- Load limit **5 V @ 220 mA per port**.
-- PORT.A carries 10 kΩ pull-ups (`R2`, `R3`) to `+3.3V`. **These are 3.3 V-logic buses on a 5 V
-  power pin** — the usual M5Stack arrangement. Do not drive 5 V logic into them.
-- The 5 V comes from the `U3` SY7088 boost when running on battery.
-
-```cpp
-DinMeter.Ex_I2C.begin();                          // PORT.A  (GPIO15/13) - external
-DinMeter.In_I2C.begin();                          // internal (GPIO12/11) - the RTC
-```
-`M5DinMeter.h:28,31`. **These are separate buses.** A Grove unit cannot collide with the RTC even
-if it answers at 0x51.
-
-## ⚠ The wire-colour conflict — read before hand-wiring
-
-The vendor PinMap renders:
-
-| | Black | Red | Yellow | White |
-|---|---|---|---|---|
-| PORT.A | GND | 5V | **G13** | **G15** |
-| PORT.B | GND | 5V | **G2** | **G1** |
-
-The schematic says `J3` pin 1 = `IIC_SCL` → GPIO15 and pin 2 = `IIC_SDA` → GPIO13; `J4` pin 1 =
-`GI` → GPIO1 and pin 2 = `GO` → GPIO2. Under the Grove convention (pin 1 = yellow, pin 2 =
-white) that makes **yellow = GPIO15 = SCL** and **yellow = GPIO1**, i.e. the opposite of the
-table. M5Unified agrees with the schematic: `EX SCL = GPIO_NUM_15`, `EX SDA = GPIO_NUM_13`
-(`M5Unified.cpp:96`).
-
-**Unresolved.** Full analysis in [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md) §1.
-
-**Practical consequence: none, if you use a Grove cable and a Grove unit** — the cable and the
-software both do the right thing. It matters only if you cut a cable and wire to bare pins, in
-which case: **buzz it out with a meter first.**
-
-## Using the ports as something else
-
-Both ports are ordinary GPIOs. The most striking demonstration is Bruce/Launcher, which builds a
-**software SPI SD-card interface across both ports at once**:
-
-```ini
-; bmorcelli/Launcher  boards/m5stack-dinmeter/platformio.ini
--DSDCARD_CS=13    -DSDCARD_SCK=15     ; PORT.A
--DSDCARD_MISO=2   -DSDCARD_MOSI=1     ; PORT.B
-```
-`reported-working` — that target is in the project's CI matrix and ships as
-`Launcher-m5stack-dinmeter.bin`. It is the only evidenced way to get storage onto this board,
-and it costs you both ports.
-
-Other uses that follow from the pin capabilities: GPIO1/2 are ADC1 channels (so PORT.B can be
-two analogue inputs), all four are LEDC-capable (PWM out), and any of them can be a UART or a
-1-Wire line.
-
-## Resource cost and conflicts
-
-| Resource | Used |
-|---|---|
-| GPIO | 13, 15 (PORT.A); 1, 2 (PORT.B) |
-| I²C ports | 1 (if you use PORT.A as I²C) — the ESP32-S3 has 2, and the RTC has the other |
-| Rail | shared 220 mA per port from `+5VOUT` |
-
-**No conflict with anything else on the board.** Display, encoder, RTC, buzzer and both ports
-can all run simultaneously — this is the one board where the pin budget is tight but the
-*peripheral* budget is not.
-
-**The real constraint is quantity.** Four signals total. If you need five, you are out.
-
-## Pitfalls
-
-| Symptom | Cause |
-|---|---|
-| Grove unit not found on `Ex_I2C` | You initialised `In_I2C` (the RTC bus) instead |
-| Unit works on USB, browns out on battery | 220 mA limit, and the boost has to supply it |
-| 5 V sensor reads wrong / damaged | The signal pins are **3.3 V**, only the power pin is 5 V |
-| Hand-wired I²C dead | The yellow/white conflict — swap and retry |
-| Grove rail measures 5.38 V not 5.0 V | Expected: `U3`'s divider computes to 5.38 V. See [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md) §6 |
-
-## Related
-
-[`components/silergy/sy7088`](../../../../components/silergy/sy7088/README.md) (the 5 V boost) ·
-[`../pinouts-and-buses.md` §5](../pinouts-and-buses.md#5-grove-ports--and-the-colour-conflict) ·
-[`../resources-and-conflicts.md`](../resources-and-conflicts.md)
diff --git a/devices/m5stack/dinmeter/features/power-and-battery.md b/devices/m5stack/dinmeter/features/power-and-battery.md
deleted file mode 100644
index c04980d..0000000
--- a/devices/m5stack/dinmeter/features/power-and-battery.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# How do I power the DinMeter — and why does it keep switching itself off?
-
-**Applies to:** K134 and K134-V11 (identical power circuit — same schematic bytes).
-**Evidence status:** power tree `executed-success` from the schematic; latch behaviour
-`reported-working` (vendor documentation, restated identically on both product pages and
-independently modelled by Espressif); current figures are **vendor claims with no stated
-method**. **Last verified:** 2026-09-04.
-
----
-
-## The short answer to "why does it switch off"
-
-**GPIO46 is a power latch.** On battery power the board stays alive only while GPIO46 is
-**high**. Raise it in `setup()`, first thing:
-
-```cpp
-DinMeter.begin(cfg, true);   // M5.begin() raises GPIO46 for you (M5Unified.cpp:282)
-```
-or, without M5Unified:
-```c
-gpio_set_direction(GPIO_NUM_46, GPIO_MODE_OUTPUT);
-gpio_set_level(GPIO_NUM_46, 1);          // inferred; esp-board-manager: gpio_power_hold, default_level 1
-```
-
-On USB it works without this, because USB feeds the rail directly. That is why the bug always
-shows up as "it only fails on battery".
-
----
-
-## Three ways in
-
-| Source | Connector | Range | Path |
-|---|---|---|---|
-| **DC** | `J1`, 2-pin 2.54 mm screw terminal (`DB2EK-2.54-2P-GN-S`, green) | **6 – 36 V** | `D13`/`D12` → `U1` **ME3116AM6G** buck → `+5VIN` |
-| **USB** | USB-C **on the Stamp module** | 5 V | directly onto `+5VIN` |
-| **Battery** | `J2`, 1.25 mm 2-pin | 1S Li-ion; 250 mA·h cell bundled | `U2` **TP4057** charger; `Q3`/`Q6` AP40P05 power path; `U3` **SY7088** boost → `+5VOUT` |
-
-Rails produced:
-
-| Rail | From | Feeds |
-|---|---|---|
-| `+5VIN` | `U1` buck, or USB | Stamp pad 13, `U2` charger, `U7` CN809J supervisor, buzzer `LS1` |
-| `+5VOUT` | `U3` boost from `VBAT_OUT` | **both Grove ports**, pin 3 |
-| `+3.3V` | `U4` **BL8075CB5TR33** LDO from `VBAT_IN` | RTC `U5`, I²C and encoder pull-ups, LCD `FPC1` |
-
-Note `+3.3V` comes off the **battery** node, not `+5VIN` — which is why the RTC keeps time while
-the board is latched off.
-
-## Charging
-
-| Property | Value | Source |
-|---|---|---|
-| Charger | TP4057 linear, SOT23-6 | schematic `U2` |
-| Programme resistor | `R13` = 3.3 kΩ | schematic |
-| Charge current | **100 mA** | vendor spec row |
-| Float voltage | **4.24 V ±1 %** | TP4057 datasheet — note, *not* 4.20 V |
-| Bundled cell | 250 mA·h polymer Li-ion → ~0.4 C | vendor bundle list |
-| Status | `CHRG` / `STDBY` pins → indicator LEDs `D1`/`D2`/`D3` | schematic |
-| Battery sense | `R7`/`R8` 1 MΩ divider → **GPIO10** (`BATADC`) | schematic |
-
-`DinMeter.Power.getBatteryVoltage()` / `getBatteryLevel()` (M5Unified `Power_Class`, which has a
-`board_M5DinMeter` case at `utility/Power_Class.cpp:572`). `reported-working`.
-
-## The latch, precisely
-
-Vendor text, DinMeter v1.1 page (the v1.0 page says the same in different words):
-
-> **Power On:** When powered only by the battery, the device can be woken up by pressing the
-> WAKE button or via an RTC scheduled interrupt (IRQ). After the wake-up signal is triggered,
-> the initialization program **must set the HOLD (GPIO46) pin to high level (1)** to maintain
-> power supply; otherwise, the device will return to sleep.
->
-> **Power Off:** When there is no USB external power (battery power only) — (1) press the RST
-> button; (2) the program actively sets the HOLD (GPIO46) pin to low level (0).
-
-Circuit: `HOLD` (Stamp pad 27 = GPIO46) → `Q4` **LN2324DT2AG**, which gates the `Q3`/`Q6`
-AP40P05 P-channel power path. Wake sources reach the same node through `D4` (from the encoder
-button `BTN`) and from the RTC `INT`. **[SCH]**
-
-**Two wake sources, and that is the design.** A panel meter that sleeps at 38.4 µA and wakes on
-an RTC alarm to take a reading is exactly what this circuit is for.
-
-## Sleeping
-
-```cpp
-DinMeter.Power.timerSleep(5);                              // seconds
-// DinMeter.Power.timerSleep(const rtc_time_t&);
-// DinMeter.Power.timerSleep(const rtc_date_t&, const rtc_time_t&);
-// DinMeter.Power.powerOff();                              // hard shutdown via the latch
-```
-Verbatim from `M5DinMeter/examples/Basic/wakeup/wakeup.ino` (release 1.0.0). `reported-working`.
-`timerSleep` programmes the BM8563 alarm and then releases the latch — so this is not an ESP32
-deep sleep, it is a *power-off with an alarm*. That is why the standby figure is microamps
-rather than the ~10 µA an ESP32-S3 deep sleep would give plus regulator quiescent.
-
-## Numbers, with their caveats
-
-| Figure | Value | Caveat |
-|---|---|---|
-| Standby, battery | **DC 4.2 V @ 38.4 µA** | Vendor. **Identical on v1.0 and v1.1** pages, which is consistent with it being dominated by the carrier's latch/LDO rather than by the module |
-| DC input | 6 – 36 V | Vendor |
-| Charge current | 100 mA | Vendor |
-| Grove load | 5 V @ 220 mA per port | Vendor |
-| Grove rail, computed | **≈ 5.38 V** from `U3`'s own divider and the formula printed on the sheet | See [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md) §6. **Measure before connecting anything 5 V-max** |
-| Module sleep (S3 → S3A) | 310.89 µA → **6.84 µA** on `VIN_5V` | Vendor, method unstated. Does not change the *board* standby figure, because the board cuts the battery entirely |
-
-**None of these were measured here.** No instrument, no hardware.
-
-## Safety and design constraints
-
-- **`C24`, the buck input bulk capacitor, is rated 35 V** while the spec ceiling is 36 V. At
-  36 V it sits at 103 % of rating. Treat 36 V as an absolute maximum, not an operating point;
-  ≤ 30 V continuous is the prudent reading (`inferred` engineering judgement, **not** a vendor
-  statement).
-- Reverse-polarity Schottkys `D13`/`D12` are fitted but their ratings were not read. Do not rely
-  on them.
-- The DC terminal is a **screw terminal on a 32 mm-deep body**. Strain-relieve the cable.
-- 0 – 40 °C operating range. A sealed panel in direct sun will exceed that.
-
-## Pitfalls
-
-| Symptom | Cause |
-|---|---|
-| Dies when you let go of the knob (battery) | GPIO46 not held |
-| Works on USB, dies on battery | same |
-| Won't boot at all after you added a pull-up to GPIO46 | GPIO46 is a strapping pin; high at reset stops the chip booting. Remove it |
-| Battery reads 0 V | GPIO10 ADC not configured, or you are reading before `M5.begin()` |
-| Grove peripheral browns out | 220 mA per port; the boost is not unlimited |
-| Cell charges to 4.24 V, not 4.20 V | TP4057's documented float voltage. Expected |
-
-## Related
-
-[`components/microne/me3116am6g`](../../../../components/microne/me3116am6g/README.md) ·
-[`components/generic/tp4057`](../../../../components/generic/tp4057/README.md) ·
-[`components/silergy/sy7088`](../../../../components/silergy/sy7088/README.md) ·
-[`components/belling/bl8075`](../../../../components/belling/bl8075/README.md) ·
-[`rtc-and-timekeeping.md`](rtc-and-timekeeping.md) (the other wake source)
diff --git a/devices/m5stack/dinmeter/features/rgb-led.md b/devices/m5stack/dinmeter/features/rgb-led.md
deleted file mode 100644
index 71efdee..0000000
--- a/devices/m5stack/dinmeter/features/rgb-led.md
+++ /dev/null
@@ -1,109 +0,0 @@
-# How do I light the RGB LED — and why doesn't it work on v1.1?
-
-**Applies to:** K134 (works out of the box) and **K134-V11 (needs an extra line)**.
-**Evidence status:** `executed-success` for the schematic net reading; the v1.1 failure mode is
-**`inferred`** — predicted from vendor documentation + schematic + a source read, and **not
-reproduced on hardware**. **Last verified:** 2026-09-04.
-
----
-
-## Where the LED is
-
-**Not on the carrier board.** The DinMeter's own 84-part designator census contains no LED
-driver and no addressable LED. The RGB LED is **inside the Stamp module**:
-
-```
-Stamp module:  ESP32-S3 GPIO21 ──"SK_DIN"──► U3  WS2812B-2020  ──"SK_DOUT"──► (unused)
-                                              VDD ← ???  ← this is what changed
-```
-
-- Part: **WS2812B-2020**, ×1, stated on both Stamp product pages.
-- Data: **GPIO21**, `U1` pad 27 on both Stamp schematics.
-- M5Unified: `_pin_table_other0` → `{ board_M5DinMeter, GPIO_NUM_21 }`, `M5Unified.cpp:246`.
-- **GPIO21 is not one of the Stamp's 23 broken-out IOs** — it is internal, so nothing on the
-  DinMeter carrier can conflict with it.
-
-## The difference between the two revisions
-
-| | DinMeter (K134) — Stamp-S3 v0.2 | DinMeter v1.1 (K134-V11) — Stamp-S3A v0.3.3 |
-|---|---|---|
-| WS2812B `VDD` | **`VDD_3V3`** — always powered | **`BL_3V3`** — switched |
-| Switch | — | `U2` **AW35122FDR** load switch |
-| Switch enable | — | `DISP_BL` = **GPIO38** |
-| Default state at reset | LED powered | **LED unpowered** (AW35122 `EN` has a ~7.1 MΩ internal pull-down) |
-| Works with stock M5Unified? | **yes** | **predicted no** |
-
-M5Stack states it plainly on the v1.1 page:
-
-> "Stamp-S3A adds an independent electronic switch for the RGB LED power supply compared with the
-> previous Stamp-S3. Before controlling the RGB LED in software, set **GPIO38**, which controls
-> this switch, to a high level."
-
-## Portable code — works on both
-
-```cpp
-#include <M5DinMeter.h>
-
-void setup() {
-    auto cfg = M5.config();
-    DinMeter.begin(cfg, true);
-
-    // Stamp-S3A (DinMeter v1.1): enable the BL_3V3 rail that feeds the WS2812B.
-    // On Stamp-S3 (DinMeter v1.0) GPIO38 is unused by the carrier, so this is harmless.
-    pinMode(38, OUTPUT);
-    digitalWrite(38, HIGH);
-    delay(1);                       // AW35122 typ. rise 165 us; 1 ms is comfortable
-
-    // ... then drive GPIO21 with your WS2812 library of choice
-}
-```
-`not-tested`. The 1 ms settle is prudence, not a documented requirement.
-
-Any WS2812 driver works: `FastLED`, `Adafruit_NeoPixel`, `Freenove_WS2812_Lib`, or ESP-IDF's
-`led_strip` RMT/SPI backend. Nothing here is board-specific beyond the pin numbers.
-
-## Why this is worth a whole page
-
-The failure is **silent and misattributed**. On a v1.1 unit, code that worked on v1.0 compiles,
-links, boots, runs, and the LED simply does not light. Nothing errors. The natural conclusion is
-"the LED is faulty" or "my library is broken", and neither is true.
-
-And **M5Unified will not rescue you**, at master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`
-(2026-09-04):
-
-- there is **no `board_M5DinMeter_v11`** and **no `board_M5StampS3A`** enum (grep of `src/`,
-  `executed-success`);
-- the RGB-LED table has one entry for `board_M5DinMeter` and it is just `GPIO_NUM_21`;
-- **no board in the whole table has a power-enable step.**
-
-So a v1.1 unit enumerates as `board_M5DinMeter` and gets the v1.0 behaviour. If someone with a
-v1.1 unit tests this, the result belongs in
-[`../compatibility-and-status.md`](../compatibility-and-status.md) and would be the single most
-valuable addition to this record.
-
-## Resource cost and conflicts
-
-| Resource | Used |
-|---|---|
-| GPIO | 21 (data, internal) + **38 on v1.1** (enable, internal) |
-| RMT / SPI channel | 1, if you use a hardware-timed driver |
-
-**No conflicts.** Neither pin is available to the carrier or to the Grove ports, so nothing else
-can want them. On the DinMeter, GPIO38 has exactly one job.
-
-## Pitfalls
-
-| Symptom | Cause |
-|---|---|
-| LED dark on a new (v1.1) unit, code unchanged | GPIO38 not raised. **This is the one** |
-| LED dark on v1.0 | genuinely a fault, or the wrong pin |
-| First frame wrong colour after enabling | rail had not settled — add the delay |
-| LED stays lit in sleep, wasting current on v1.0 | it is on the always-on rail; that is the design M5Stack changed |
-
-## Related
-
-[`../../dinmeter-v1.1/stamp-s3-to-s3a-delta.md`](../../dinmeter-v1.1/stamp-s3-to-s3a-delta.md) §3
-(the full evidence chain) ·
-[`components/m5stack/stamp-s3a`](../../../../components/m5stack/stamp-s3a/README.md) ·
-[`components/awinic/aw35122`](../../../../components/awinic/aw35122/README.md) ·
-[`components/sgmicro/sgm2578`](../../../../components/sgmicro/sgm2578/README.md)
diff --git a/devices/m5stack/dinmeter/features/rotary-encoder-and-buttons.md b/devices/m5stack/dinmeter/features/rotary-encoder-and-buttons.md
deleted file mode 100644
index 47e3f4b..0000000
--- a/devices/m5stack/dinmeter/features/rotary-encoder-and-buttons.md
+++ /dev/null
@@ -1,170 +0,0 @@
-# How do I read the orange knob and its button?
-
-**Applies to:** DinMeter K134 and K134-V11 (identical hardware and pin map).
-**Evidence status:** vendor example code (`reported-working` — it is M5Stack's own, shipped and
-released); pin assignments `executed-success` from schematic + two independent source trees;
-nothing run on hardware here. **Last verified:** 2026-09-04.
-
----
-
-## Hardware path
-
-```
-orange knob  →  encoder module on connector J5  →  IN_A / IN_B  →  Stamp pads 23 / 21
-                                                                 →  ESP32-S3 GPIO41 / GPIO40
-             ↘  integrated push switch (b1/b2)  →  BTN → WAKE   →  Stamp pad 25 → GPIO42
-                                                                 ↘ D4 → power-latch wake
-```
-
-- Pull-ups: `R2`, `R3` = 10 kΩ (A, B) and `R1` = 10 kΩ (button) to `+3.3V`; `C1` = 100 nF
-  debounce on the button. **No other debounce hardware is fitted.**
-- The encoder is **not** soldered to the main PCB — it plugs into a 7-pad connector `J5`.
-- The encoder part number is **not published**:
-  [`components/unidentified/m5stack-dinmeter/rotary-encoder`](../../../../components/unidentified/m5stack-dinmeter/rotary-encoder/README.md).
-- **The button is also the wake key.** Pressing it can power the whole board back on from a
-  latched-off state.
-
-## Buttons available
-
-| Button | Where | GPIO | M5Unified name | Notes |
-|---|---|---|---|---|
-| Knob press | in the encoder | **42** | `M5.BtnA` / `DinMeter.BtnA` | active-low; also a wake source |
-| `G0` | **on the Stamp module** | **0** | `M5.BtnB` | boot/download button; usable as a normal button at runtime |
-| `RST` (`S4`) | carrier | — | — | hardware reset, drives the Stamp's `EN`. Also the power-off button on battery |
-
-M5Unified reads both in one place:
-```cpp
-// M5Unified/src/M5Unified.cpp:3500-3506
-case board_t::board_M5Capsule:
-case board_t::board_M5Dial:
-case board_t::board_M5DinMeter:
-  use_rawstate_bits = 0b00011;
-  btn_rawstate_bits = ((!m5gfx::gpio_in(GPIO_NUM_42)) & 1)
-                    | ((!m5gfx::gpio_in(GPIO_NUM_0)) & 1) << 1;
-  break;
-```
-and configures GPIO42 as an input at init (`M5Unified.cpp:2398-2402`).
-
----
-
-## Arduino — M5DinMeter (the short way)
-
-```cpp
-#include "M5DinMeter.h"
-
-void setup() {
-    auto cfg = M5.config();
-    DinMeter.begin(cfg, /* enableEncoder = */ true);   // <- true, or the encoder never starts
-    DinMeter.Display.setRotation(1);
-    DinMeter.Display.setTextDatum(middle_center);
-    DinMeter.Display.setTextFont(&fonts::Orbitron_Light_32);
-    DinMeter.Display.setTextSize(2);
-}
-
-long oldPosition = -999;
-
-void loop() {
-    DinMeter.update();
-    long newPosition = DinMeter.Encoder.read();
-    if (newPosition != oldPosition) {
-        DinMeter.Speaker.tone(8000, 20);      // click feedback
-        DinMeter.Display.clear();
-        oldPosition = newPosition;
-        DinMeter.Display.drawString(String(newPosition),
-            DinMeter.Display.width()/2, DinMeter.Display.height()/2);
-    }
-    if (DinMeter.BtnA.wasPressed())      DinMeter.Encoder.readAndReset();
-    if (DinMeter.BtnA.pressedFor(5000))  DinMeter.Encoder.write(100);
-}
-```
-Verbatim from `M5DinMeter/examples/Basic/encoder/encoder.ino` (release 1.0.0, 2024-03-07).
-`reported-working` — vendor-published, not run here.
-
-**API surface** (from the vendored PJRC `Encoder`, MIT, v1.2):
-`read()`, `readAndReset()`, `write(long)`. `Button_Class` gives `wasPressed()`,
-`wasReleased()`, `isPressed()`, `pressedFor(ms)`, `wasClicked()`, `wasHold()`.
-
-**Counts.** x4 decoding — **one detent is four counts**. Divide by 4 for detent-level UI, or
-accept 4× sensitivity. Detents-per-revolution is not published.
-
-`DIAL_ENCODER_PIN_A 41` / `DIAL_ENCODER_PIN_B 40` are `#define`s in `M5DinMeter.h:8-9`; the
-`ENCODER` member is constructed with them at `:33`. There is no way to change them without
-editing the library, and no reason to.
-
----
-
-## ESP-IDF — PCNT (the better way for anything real)
-
-The PJRC library is interrupt-driven and costs a pair of ISRs. The ESP32-S3's **pulse counter**
-does it in hardware. Espressif's own board definition uses PCNT; its configuration, verbatim:
-
-| Field | Value |
-|---|---|
-| channels | 2 |
-| ch 0 | `edge_gpio_num: 41` (A), `level_gpio_num: 40` (B); pos → DECREASE, neg → INCREASE; high → KEEP, low → INVERSE |
-| ch 1 | `edge_gpio_num: 40` (B), `level_gpio_num: 41` (A); pos → INCREASE, neg → DECREASE; high → KEEP, low → INVERSE |
-| filter | `max_glitch_ns: 1000` |
-| limits | −1000 … +1000, `accum_count: true` |
-| watch points | −1000, 0, +1000 |
-
-Source: `espressif/esp-board-manager` `m5stack_boards/m5stack_dinmeter/board_peripherals.yaml`
-@ `2beb9b22b0892b343bd555a1ebc9929a7edce8fc`, retained at
-[`../artifacts/source-snapshots/dinmeter-board_peripherals.yaml`](../artifacts/source-snapshots/dinmeter-board_peripherals.yaml).
-
-Two traps that file documents, both worth repeating:
-
-1. **Each pin is used twice** — as an edge input on one channel and a level input on the other.
-   A conflict checker will flag GPIO40/41 as double-booked. That is the standard IDF
-   rotary-decoder pattern and is correct.
-2. **Do not set `en_step_notify_up` / `en_step_notify_down`**, even to `false`. Those fields only
-   exist under `SOC_PCNT_SUPPORT_STEP_NOTIFY`, which **the ESP32-S3 does not have**; a generator
-   that emits them unconditionally breaks the build with
-   `'struct <anonymous>' has no member named 'en_step_notify_up'`.
-
-The button in IDF: GPIO42, input, pull-up, active-low, `long_press_time: 2000`,
-`short_press_time: 100` — same source, `gpio_button_wake`.
-
----
-
-## Decision table
-
-| Approach | Use when | Cost |
-|---|---|---|
-| `DinMeter.Encoder` (PJRC, Arduino) | Arduino, simple UI, you already use M5Unified | 2 GPIO ISRs; fine at human speeds |
-| ESP-IDF PCNT | IDF, or you need zero-CPU counting, or the knob is spun fast | one PCNT unit + 2 channels of the ESP32-S3's 4 |
-| `ESP32Encoder` (bundled in `M5DinMeter-UserDemo/lib/`) | you want PCNT *from Arduino* | third-party, vendored by M5Stack in the factory-firmware project |
-| Bare GPIO polling | never | misses transitions |
-
----
-
-## Resource cost and conflicts
-
-| Resource | Used |
-|---|---|
-| GPIO | 41, 40 (encoder), 42 (button), 0 (Stamp button) |
-| Interrupts | 2 (PJRC path) or 0 (PCNT path) |
-| PCNT units | 1 of 4, 2 channels (PCNT path) |
-| Timers | none |
-
-**Conflicts:** GPIO40/41/42 are the ESP32-S3 JTAG pins (`MTDO`/`MTDI`/`MTMS`). Using pin-based
-JTAG debug is therefore impossible while the knob works. USB-Serial-JTAG is unaffected.
-Nothing else on the board contends. See [`../resources-and-conflicts.md`](../resources-and-conflicts.md).
-
----
-
-## Debugging and pitfalls
-
-| Symptom | Likely cause |
-|---|---|
-| `Encoder.read()` always 0 | `begin()` called without `true` |
-| Counts jump by 4 per detent | correct — x4 decoding. Divide |
-| Direction inverted | swap A/B, or negate; there is no vendor-defined "positive" direction |
-| Button seems to reset the app | you are on battery and GPIO46 is not held — the press is waking it, not resetting it. See [`power-and-battery.md`](power-and-battery.md) |
-| Jitter at rest | the 1 kΩ-ish pull-ups plus 1 µs glitch filter are usually enough; if not, raise `max_glitch_ns` |
-| JTAG adapter cannot attach | GPIO39-42 are occupied. Use USB-Serial-JTAG |
-
-## Unresolved
-
-- Detents per revolution, counts per revolution, rated rotational life, switch rated operations
-  — **all unknown**, because the encoder part is unidentified.
-- Whether the orange cap is part of the encoder or a separate moulding — unknown.
diff --git a/devices/m5stack/dinmeter/features/rtc-and-timekeeping.md b/devices/m5stack/dinmeter/features/rtc-and-timekeeping.md
deleted file mode 100644
index cbef94e..0000000
--- a/devices/m5stack/dinmeter/features/rtc-and-timekeeping.md
+++ /dev/null
@@ -1,130 +0,0 @@
-# How do I keep time on the DinMeter and wake it on a schedule?
-
-**Applies to:** K134 and K134-V11 (identical).
-**Evidence status:** wiring `executed-success` (schematic + M5Unified + esp-board-manager all
-agree); code `reported-working` (vendor example). **Last verified:** 2026-09-04.
-
----
-
-## Hardware path
-
-```
-BM8563 (U5, SOP8)  ──I²C──►  ESP32-S3   SCL GPIO12 / SDA GPIO11   [INTERNAL bus, address 0x51]
-   Y2 32.768 kHz ±20 ppm 12.5 pF, C28/C29 6.0 pF
-   VDD ← +3.3V (from U4 BL8075, fed from VBAT_IN → survives the power latch opening)
-   INT (open drain) ──► power-latch wake path
-```
-
-Component: [`components/generic/bm8563`](../../../../components/generic/bm8563/README.md)
-(functionally an NXP [PCF8563](../../../../components/nxp/pcf8563/artifacts/pcf8563-datasheet-rev-11.pdf)).
-
-**The RTC is not on PORT.A.** Internal bus GPIO11/12; PORT.A is GPIO13/15. A Grove I²C unit
-cannot collide with it — even one that happens to answer at 0x51.
-
-## Arduino
-
-```cpp
-#include <M5DinMeter.h>
-void setup() {
-    DinMeter.begin();
-    if (!DinMeter.Rtc.isEnabled()) { /* RTC not found */ }
-
-    // direct set:  { {YYYY, MM, DD}, {hh, mm, ss} }
-    DinMeter.Rtc.setDateTime({{2026, 9, 4}, {12, 34, 56}});
-}
-void loop() {
-    auto dt = DinMeter.Rtc.getDateTime();
-    Serial.printf("%04d/%02d/%02d %02d:%02d:%02d\n",
-        dt.date.year, dt.date.month, dt.date.date,
-        dt.time.hours, dt.time.minutes, dt.time.seconds);
-    delay(500);
-}
-```
-`DinMeter.Rtc` is a reference to `M5.Rtc`, an `RTC8563_Class` (`M5DinMeter.h:23`).
-`reported-working` — the full NTP-synchronising version is
-`M5DinMeter/examples/Basic/rtc/rtc.ino`, which is worth reading for its handling of the
-`esp_sntp.h` / `sntp.h` header split across IDF versions.
-
-**Keep the RTC in UTC.** The vendor example says so explicitly: *"It is recommended to set UTC
-for the RTC and ESP32 internal clocks."* Do timezone conversion with `configTzTime` +
-`localtime()`, not by storing local time in the RTC.
-
-### NTP sync, condensed from the vendor example
-
-```cpp
-WiFi.begin(SSID, PASS);  while (WiFi.status() != WL_CONNECTED) delay(500);
-configTzTime("UTC-8", "0.pool.ntp.org", "1.pool.ntp.org", "2.pool.ntp.org");
-while (sntp_get_sync_status() != SNTP_SYNC_STATUS_COMPLETED) delay(1000);
-time_t t = time(nullptr) + 1;
-while (t > time(nullptr)) ;          // land on a second boundary
-DinMeter.Rtc.setDateTime(gmtime(&t));
-```
-
-## Alarms and waking the board
-
-This is the interesting part. The BM8563's open-drain `INT` is wired into the **power-latch wake
-path**, so an alarm can bring the device back from a fully latched-off state — not from a sleep
-mode, from *off*.
-
-```cpp
-DinMeter.Power.timerSleep(60);                     // wake in 60 s
-DinMeter.Power.timerSleep(rtc_time_t{7, 30, 0});   // wake at 07:30
-DinMeter.Power.timerSleep(rtc_date_t{...}, rtc_time_t{...});
-```
-`reported-working` (`examples/Basic/wakeup/wakeup.ino`). Internally these programme the BM8563
-alarm/timer and then release GPIO46.
-
-Lower-level: `M5.Rtc.setAlarmIRQ(...)` and `M5.Rtc.clearIRQ()` in `RTC8563_Class`.
-
-## ESP-IDF
-
-**There is no ESP-IDF driver for the BM8563**, and Espressif's board definition says so:
-
-> *"Not modeled: BM8563 RTC (I2C 7-bit 0x51): no bmgr device type; the `i2c_master` above is its
-> bus"*
-
-You get the bus (port 0, SDA 11, SCL 12) and write the register access yourself, or port
-`I2C_BM8563` — which M5Stack vendors into its own factory-firmware project at
-`M5DinMeter-UserDemo/lib/I2C_BM8563/` (retained in
-[`../artifacts/source-snapshots/`](../artifacts/source-snapshots/)). The register map is the
-PCF8563's.
-
-## BM8563 essentials
-
-| Property | Value |
-|---|---|
-| Address | write `0xA2` / read `0xA3` → **7-bit `0x51`** |
-| Bus speed | ≤ 400 kbit/s |
-| Supply | 1.5 – 5.5 V (here 3.3 V) |
-| Sleep current | typ. 0.25 µA @ 3.0 V |
-| `INT` | **open drain** — needs a pull-up (the schematic shows a 10 kΩ at the `R20` position) |
-| `CLKOUT` | programmable 32.768 kHz / 1024 / 32 / 1 Hz — **not wired on this board** |
-| Century flag | present; the driver handles it |
-
-⚠ The datasheet M5Stack mirrors carries a stray `MAX1937` string in its header — a sign it was
-derived by editing another part's document. The address and register information is corroborated
-by the PCF8563 datasheet and by M5Unified's implementation, so it is trustworthy; other
-electrical tables in it are worth double-checking.
-
-## Resource cost and conflicts
-
-GPIO 11, 12; one I²C port; no timers, no interrupts by default (the `INT` line goes to the power
-circuit, not to a GPIO you can poll). **No conflicts.** The RTC coexists with the display, the
-encoder, Wi-Fi and both Grove ports.
-
-## Pitfalls
-
-| Symptom | Cause |
-|---|---|
-| `isEnabled()` false | Wrong bus — you used `Ex_I2C` (GPIO13/15) instead of `In_I2C` (GPIO11/12) |
-| Time resets on power loss | The `+3.3V` rail comes from `VBAT_IN`; with **no battery fitted** and no USB/DC, the RTC has no supply |
-| Alarm never fires | Alarm flag not cleared from the previous event; call `clearIRQ()` |
-| Time drifts | Crystal is ±20 ppm ≈ ±1.7 s/day worst case. Re-sync from NTP |
-| Local time stored in RTC then wrong after DST | Store UTC |
-
-## Unresolved
-
-- Whether the board loads the BM8563's `CLKOUT` — it appears unconnected but was not fully
-  traced.
-- The exact `R20` pull-up on `INT` has designator text but no recoverable schematic marker; see
-  [`../pinouts-and-buses.md` §6](../pinouts-and-buses.md#6-reference-designator-census-and-three-that-do-not-resolve).
diff --git a/devices/m5stack/dinmeter/features/wifi-and-ble.md b/devices/m5stack/dinmeter/features/wifi-and-ble.md
deleted file mode 100644
index fca48c4..0000000
--- a/devices/m5stack/dinmeter/features/wifi-and-ble.md
+++ /dev/null
@@ -1,116 +0,0 @@
-# How do I get the DinMeter onto the network?
-
-**Applies to:** K134 (Stamp-S3) and K134-V11 (Stamp-S3A).
-**Evidence status:** capability from silicon and vendor documentation; code
-`reported-working` (vendor example). **Radio performance was not measured.**
-**Last verified:** 2026-09-04.
-
----
-
-## What the radio is
-
-| Property | Value | Evidence |
-|---|---|---|
-| SoC | ESP32-S3FN8 | vendor spec row |
-| Wi-Fi | **2.4 GHz 802.11 b/g/n only** — no 5 GHz, no Wi-Fi 6 | vendor spec row + ESP32-S3 datasheet |
-| Bluetooth | **BLE 5 only.** The ESP32-S3 has **no Bluetooth Classic (BR/EDR)** — silicon-level, unfixable in software | ESP32-S3 datasheet |
-| Antenna | on the **Stamp module**, "2.4 GHz 3D antenna", `ANT1` | Stamp product pages |
-| Antenna part | Stamp-S3: `PROANT440`. **Stamp-S3A: no part text on the schematic** | schematics |
-| External antenna connector | **none** | no connector designator on either sheet |
-
-**No A2DP, no HFP, no SPP, no Bluetooth media keys.** If you wanted a Bluetooth *audio* knob,
-this is the wrong device — see
-[`../comparisons-and-recommendations.md`](../comparisons-and-recommendations.md) §2, where the
-Waveshare knob solves it by soldering a second SoC onto the board.
-
-BLE HID *is* possible and is what `tarmn3/m5dinmeter-ble-volume-knob` does.
-
-## Arduino
-
-Standard ESP32 Arduino; nothing DinMeter-specific:
-
-```cpp
-#include <WiFi.h>
-#include <M5DinMeter.h>
-
-void setup() {
-    auto cfg = M5.config();
-    DinMeter.begin(cfg, true);            // raises GPIO46 - do this first, always
-    WiFi.begin("ssid", "password");
-    while (WiFi.status() != WL_CONNECTED) { delay(500); }
-    DinMeter.Display.print("Connected.");
-}
-```
-Pattern taken from `M5DinMeter/examples/Basic/rtc/rtc.ino`, which is also the NTP example — see
-[`rtc-and-timekeeping.md`](rtc-and-timekeeping.md).
-
-M5Stack documents a dedicated tutorial at `docs.m5stack.com/en/arduino/m5dinmeter/wifi`
-(HTTP 200, 2026-09-04).
-
-**BLE:** `NimBLE-Arduino` or the ESP32 Arduino `BLEDevice` stack. Nothing board-specific.
-
-## ESP-IDF
-
-`esp_wifi` and `esp_nimble` as normal, target `esp32s3`. Espressif's `esp-board-manager`
-DinMeter definition models **no radio at all** — because there is nothing board-specific to
-model.
-
-## The memory constraint that will actually bite you
-
-**There is no PSRAM.** ESP32-S3FN8, on both revisions, confirmed three ways: no PSRAM row on
-either product page; `FN8` has none in package; Bruce/Launcher explicitly does
-`build_unflags = -DBOARD_HAS_PSRAM`.
-
-So you are sharing the ESP32-S3's internal SRAM between:
-
-| Consumer | Rough cost |
-|---|---|
-| Wi-Fi stack + lwIP | tens of KB, more with many sockets |
-| TLS session (mbedTLS) | **~20–50 KB per connection**, dominated by the record buffers |
-| BLE (NimBLE) | ~30–40 KB |
-| A full 135 × 240 × 16 bpp framebuffer | **64 800 B** |
-
-Running Wi-Fi + TLS + BLE + a full-screen sprite simultaneously is where a PSRAM-less S3 gets
-uncomfortable. The mitigations are the usual ones: band buffers instead of a full framebuffer
-(see [`display.md`](display.md)), `MBEDTLS_SSL_MAX_CONTENT_LEN` reduced from 16384, and not
-running Wi-Fi and BLE concurrently unless you must.
-
-**Not measured here.** No heap profiling was done. These are the standard ESP32-S3 constraints,
-stated so you plan for them; the numbers are indicative.
-
-## Coexistence
-
-Wi-Fi and BLE share the single 2.4 GHz radio. ESP-IDF's coexistence arbiter handles it, at the
-cost of throughput and latency on both. Nothing about the DinMeter changes this.
-
-## Antenna and enclosure — the thing that is genuinely device-specific
-
-The DinMeter is designed to be **installed inside a metal panel or cabinet**, with only its
-53 × 30 mm face exposed through a 45 × 22.5 mm aperture. The antenna is on the Stamp module,
-*behind* the panel.
-
-That is a materially worse RF environment than a desktop puck, and it is the one place where
-the Stamp-S3A's rebuilt antenna match might matter. M5Stack claims *"better signal reception"*
-for the S3A with **no figure and no method**. Nothing here corroborates or refutes it.
-
-**If you are deploying into a steel cabinet, budget for testing the link margin.** There is no
-external antenna option, so the mitigations are placement, keeping the door open to RF, or an
-external AP nearby. `inferred` — no RF measurement was performed.
-
-## Resource cost and conflicts
-
-GPIO: **none** — the radio is entirely on-die and the antenna is inside the module. There is no
-pin conflict with the display, encoder, RTC, buzzer or Grove ports. The constraints are RAM,
-power and RF environment, not pins.
-
-**Power:** the vendor's "standby" figures (33.5 mA on Stamp-S3, 25.5 mA on Stamp-S3A) are the
-number to plan around when the radio is up. Compare with 38.4 µA latched off. If you are running
-on the bundled 250 mA·h cell, Wi-Fi-always-on is roughly a **10-hour** device; duty-cycled with
-RTC wake it is a months-long device. That arithmetic is `inferred` from vendor figures, not
-measured.
-
-## Related
-
-[`power-and-battery.md`](power-and-battery.md) · [`rtc-and-timekeeping.md`](rtc-and-timekeeping.md)
-(RTC wake is how you make the battery last) ·
-[`components/m5stack/stamp-s3a`](../../../../components/m5stack/stamp-s3a/README.md) §4 (the antenna change)
diff --git a/devices/m5stack/dinmeter/gaps-and-conflicts.md b/devices/m5stack/dinmeter/gaps-and-conflicts.md
deleted file mode 100644
index 934746c..0000000
--- a/devices/m5stack/dinmeter/gaps-and-conflicts.md
+++ /dev/null
@@ -1,196 +0,0 @@
-# DinMeter — gaps, conflicts and unresolved identities
-
-**Snapshot 2026-09-04.** Applies to K134 and K134-V11 unless stated. Conflicts are recorded, not
-resolved by preference; each says what evidence would settle it.
-
----
-
-## 1. ⚠ PORT.A / PORT.B wire colours — **unresolved**
-
-**The claim in dispute:** which physical Grove wire carries which signal.
-
-| Source | Class | Says |
-|---|---|---|
-| M5Stack DinMeter PinMap (both v1.0 and v1.1 pages) | primary | PORT.A `Yellow=G13, White=G15`; PORT.B `Yellow=G2, White=G1` |
-| M5Stack **M5Dial** PinMap | primary | **the same table**, `Yellow=G13, White=G15` |
-| DinMeter schematic, `PIJ30x`/`PIJ40x` markers | primary | `J3` pin1 = `IIC_SCL` → GPIO15, pin2 = `IIC_SDA` → GPIO13; `J4` pin1 = `GI` → GPIO1, pin2 = `GO` → GPIO2 |
-| `M5Unified.cpp:96` | primary (framework) | `board_M5DinMeter`: **EX SCL = GPIO_NUM_15, EX SDA = GPIO_NUM_13** |
-| `M5Unified.cpp:157-160` | primary (framework) | port-B table, comment `p1 close to 5V`, values `GPIO_NUM_1, GPIO_NUM_2` |
-| `espressif/esp-board-manager` `board_peripherals.yaml` | community | "PORT.A (GPIO13 yellow / GPIO15 white) and PORT.B (GPIO2 yellow / GPIO1 white)" — **but its own header says `Source: M5Stack Din Meter official documentation (pin map)`**, so it is a *reproduction* of the disputed table, not corroboration |
-
-**The analysis.** Under the Grove standard (connector pin 1 = yellow, pin 2 = white), the
-schematic makes yellow = GPIO15 = SCL and white = GPIO13 = SDA — the opposite of the vendor
-table. Every M5Stack PORT.A elsewhere is documented as *yellow = SCL, white = SDA*; if the
-DinMeter really put SDA on yellow, a standard Grove I²C unit would receive SDA on its SCL pin
-and nothing would work. Since Grove units demonstrably do work on M5Dial and DinMeter, the most
-likely reading is that **the vendor table's Yellow/White columns are transposed**.
-
-**Status: `inferred`, not established.** Two possibilities remain: (a) the table is wrong, or
-(b) M5Stack's HY2.0 symbol numbers pin 1 at the black end, in which case the table is right and
-the Grove-pin-1 assumption is wrong.
-
-**Consequence:** *none* for anyone using M5Unified, UiFlow2 or a Grove cable — the software
-drives the right pins and the cable is symmetric in the right way. It matters **only** for
-hand-wiring to bare leads.
-
-**What would settle it:** a photograph of the DinMeter's bundled pin sticker or rear silkscreen;
-or M5Stack's PCB/Gerber files, which are not published.
-
----
-
-## 2. ⚠ Three designators with no marker layer — **partly an extraction limit**
-
-`S1`, `R20` and `Y1` appear as visible text on the schematic with **no `CO` and no `PI`
-marker** anywhere in the document. Searched exhaustively in both single and double-struck glyph
-forms; zero hits for `COS1`, `COR20`, `COY1`.
-
-| Text | Position | Adjacent | Assessment |
-|---|---|---|---|
-| `S1` | (246.7, 242.9) | `SW-PB` 16.8 units below — the identical designator/part spacing that `S4` uses | A drawn WAKE push-button. **Not asserted as DNP** |
-| `R20` | (249.3, 276.9) | `10 kΩ` below, on the RTC `INT` net | Almost certainly a real pull-up on `INT` |
-| `Y1` | (163.8, 495.0) | immediately right of `SS8050` on the same baseline, under `COQ5`/`Q5` | **Probably not a designator at all** — `Y1` is the SOT-23 marking code for an SS8050 NPN |
-
-**Context that matters:** ~20 `PI` markers are missing overall (238 recovered vs ~260 expected
-for 84 parts), because Altium glues some markers to adjacent text in a way the parser's
-negative-lookbehind rule — which is required to stop `GPIO0` parsing as a `PI` marker — must
-discard. So an **extraction loss is the more likely explanation** for `S1` and `R20`.
-
-**Not established.** Settled by a higher-fidelity PDF parse, or by a photograph of the board.
-
----
-
-## 3. ⚠ M5Stack publishes v1.0 assets under v1.1 filenames — **established, and it is a finding**
-
-| Asset | v1.0 URL | v1.1 URL | SHA-256 |
-|---|---|---|---|
-| Schematic | `…/500/DIN_Meter_v1.0.pdf` | `…/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf` | **identical** `03ec3353…6e4c070` |
-| Structure STL | `Products/K134_DinMeter/…/DinMeter.stl` | `Products/K134-V11_DinMeter_v1.1/…/DinMeter_v1.1.stl` | **identical** `90f04d6a…4aef00fbf7` |
-| Dimension drawing | `…/1211/K134-din_meter_asm_v1.pdf` | **the same URL** | — |
-
-The v1.1 schematic's own filename contains `_v1.0_`.
-
-**What this licenses us to conclude:** M5Stack has published **no v1.1-specific board
-documentation**. It does **not** prove the PCB is unchanged — it proves the *documentation* is.
-The two boards could differ in ways no published document shows.
-
-**What would settle it:** a v1.1 schematic, or a teardown photograph of a v1.1 PCB.
-
-This is why this repository holds **one full record plus a scoped revision record**, rather than
-two full records asserting differences the evidence cannot support.
-
-Same pattern at module level: `Stamp-S3.stl` and `Stamp-S3A.stl` are byte-identical
-(`f72c1af2…`), and `m5stack/M5_Hardware` publishes **no Stamp-S3A footprint** at all.
-
----
-
-## 4. ⚠ ST7789P3 has no datasheet — **gap**
-
-The DinMeter v1.1 page names `ST7789P3` in three places (Features, spec row, PinMap heading) and
-**removes the display datasheet link** the v1.0 page had, replacing it with nothing. No ST7789P3
-document was located from Sitronix or any mirror. The vendor's own v1.0↔v1.1 comparison table
-does not mention the display at all.
-
-Command-compatibility with ST7789V2 is **assumed** — same pins, same resolution, same driver
-path, and M5Unified has no ST7789P3 branch. That is weak positive evidence, not verification.
-See [`components/sitronix/st7789p3`](../../../components/sitronix/st7789p3/README.md).
-
-**What would settle it:** an ST7789P3 datasheet, or a teardown photograph of a v1.1 unit's
-controller marking.
-
----
-
-## 5. ⚠ Stamp-S3A: 24 mm or 26 mm — **unresolved**
-
-Vendor spec tables: Stamp-S3 = 24.0 × 18.0 × 4.7 mm, Stamp-S3A = **26.0** × 18.0 × 4.7 mm.
-But the two published STLs are byte-identical and no new footprint was published — and M5Stack
-ships the S3A on a DinMeter carrier whose published assets are unchanged. A 2 mm growth would be
-a breaking change for any host PCB.
-
-`inferred`: the `26.0` is probably a documentation error. **Not established.** Measure a real
-part before laying out a board.
-
----
-
-## 6. ⚠ Grove 5 V rail: 5.00 V or 5.38 V — **arithmetic conflict inside one M5Stack document**
-
-The DinMeter spec row says the Grove rail is **DC 5 V** @ 220 mA. The schematic prints, beside
-`U3` (SY7088 boost), the formula **`Vout = 1.2 V × (R1/R2 + 1)`**, and fits `R16` = 52.3 kΩ,
-`R18` = 15 kΩ. That evaluates to **1.2 × (52.3/15 + 1) ≈ 5.38 V** — about 7.6 % high.
-
-Both are primary M5Stack statements. Possible explanations: the divider is not the pair assumed
-(nearest-neighbour value association could be wrong), the reference is not 1.2 V in practice, or
-the rail really is ~5.38 V and the spec is rounded.
-
-**Consequence:** real, if you are attaching a peripheral with a hard 5 V maximum to a Grove port.
-**Measure the rail before connecting it.**
-
-**What would settle it:** a multimeter on `J3` pin 3.
-
----
-
-## 7. ⚠ No stable URL for the UiFlow2 firmware binary — **gap**
-
-M5Stack distributes UiFlow2 and the DinMeter EasyLoader image through **M5Burner**, a desktop
-application that resolves images at run time from an undocumented endpoint. No stable static
-download URL for a DinMeter UiFlow2 or factory binary was located.
-
-**Consequence:** the factory firmware cannot be archived here, and cannot be reacquired without
-running M5Burner. See [`factory-firmware.md`](factory-firmware.md).
-
----
-
-## 8. Untraced circuit: the `G14` / `G39` diode-OR network
-
-Stamp pads 16 (`G14`) and 19 (`G39`) each sit on a 10 kΩ + 1N4148WT network (`R9`/`D7`,
-`R10`/`D6`?) tied into the power-latch region. The most plausible reading is a diode-OR of wake
-sources into the latch, but **the nets were not fully traced** in this pass and no vendor
-document mentions either pin.
-
-**Consequence:** GPIO14 and GPIO39 are documented in the vendor PinMap as free, but they are
-**not** free — they have hardware on them. Do not repurpose them without tracing the circuit.
-
----
-
-## 9. Sources searched with no result (negative findings, recorded so they are not re-chased)
-
-| Question | Searched | Result |
-|---|---|---|
-| ESPHome support | `repo:esphome/esphome dinmeter` | **0** |
-| Tasmota support | `repo:arendst/Tasmota dinmeter` | **0** |
-| Meshtastic support | `repo:meshtastic/firmware dinmeter`, `din_meter` | **0** each |
-| Bruce upstream support | `repo:pr3y/Bruce dinmeter` | **0** — the port lives in `bmorcelli/Launcher` |
-| ME3116AM6G datasheet | web + aggregators | **not found** |
-| SY7088 datasheet | web + aggregators | **not found** |
-| BL8075 datasheet | web + aggregators | **not found** |
-| SGM2578 datasheet | web + aggregators | **not found** |
-| Stamp-S3A `U4` part number | schematic + vendor pages | **not printed anywhere** |
-| Rotary encoder part number | schematic + both product pages | **not published** |
-| Buzzer `LS1` part number | schematic + both product pages | **not published** |
-| DinMeter teardown / bare-PCB photograph | image and web search | **none found** |
-| AliExpress clones | marketplace search | **none found** |
-| M5Stack forum threads | `community.m5stack.com` API + HTML | **HTTP 401 / JS shell — blocked, not empty** |
-
----
-
-## 10. Confirmed-correct: things that were checked and found already right
-
-Recorded so nobody re-investigates them.
-
-| Claim | Verified against | Verdict |
-|---|---|---|
-| Encoder A = GPIO41, B = GPIO40 | schematic + `M5DinMeter.h:8-9` + `esp-board-manager` + Bruce | **correct**, four independent sources |
-| Buzzer = GPIO3, **not** GPIO42 | schematic + `M5Unified.cpp:2921-2928` | **correct**; the vendor table's adjacent rows make this easy to misread, and Espressif's board file flags it explicitly |
-| Power hold = GPIO46, active high | schematic + `M5Unified.cpp:282` + vendor Learn + `esp-board-manager` | **correct** |
-| Display GRAM offset (52, 40), `INVON`, 40 MHz | M5Stack's own factory firmware + `esp-board-manager` + Bruce/Launcher | **correct**, three independent sources |
-| Battery ADC on GPIO10, divider ratio 2.0 | schematic `R7`/`R8` 1 MΩ + 1 MΩ + Bruce/Launcher comment | **correct** |
-| Internal I²C (RTC) ≠ external I²C (PORT.A) | schematic + `M5Unified.cpp:96` | **correct** |
-| No PSRAM | vendor spec (`FN8`) + Bruce `build_unflags = -DBOARD_HAS_PSRAM` | **correct** |
-| ESP32-S3 datasheet already in this repo | SHA-256 `b6db403d…` matches `components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf` | **duplicate — not re-added**, extra URL recorded instead |
-
----
-
-## Related
-
-[`../dinmeter-v1.1/gaps-and-conflicts.md`](../dinmeter-v1.1/gaps-and-conflicts.md) ·
-[`research-log.md`](research-log.md) · [`sources.md`](sources.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md)
diff --git a/devices/m5stack/dinmeter/market-and-pricing.md b/devices/m5stack/dinmeter/market-and-pricing.md
deleted file mode 100644
index 725e712..0000000
--- a/devices/m5stack/dinmeter/market-and-pricing.md
+++ /dev/null
@@ -1,158 +0,0 @@
-# DinMeter — market and pricing
-
-All observations **2026-09-04**, from `shop.m5stack.com`'s Shopify JSON endpoints (`/products/<slug>.js`),
-which give SKU, price, availability and publication dates directly rather than through rendered
-HTML. Prices are **USD, item price only**, excluding shipping, tax and duty. Region: the global
-M5Stack store.
-
----
-
-## 1. Launch pricing
-
-| Product | SKU | Shop first published | Launch price | Evidence |
-|---|---|---|---|---|
-| **DinMeter** | `K134` | **2024-03-08** | USD 24.50 | shop `.js` `published_at`; the price observed today is the same figure and no price history is available, so treat "launch price" as *the current price of an EOL listing*, not as a verified 2024 observation |
-| **DinMeter v1.1** | `K134-V11` | **2026-01-30** | USD 24.50 | shop `.js` `created_at 2026-01-30T10:02:16+08:00`, `published_at 2026-01-30T12:30:47+08:00` |
-| Stamp-S3 | `S007` | 2023-02-10 | USD 7.50 | shop `.js` |
-| Stamp-S3A | `S007-PIN254-V033` | 2025-09-11 | USD 7.50 | shop `.js` |
-
-**The v1.1 launched at exactly the same price as the v1.0.** No premium was charged for the
-module upgrade.
-
-The 2026-01-30 launch date is corroborated independently by the official r/M5Stack weekly-products
-post of the same day.
-
-## 2. Current observations — 2026-09-04
-
-| Date | Region | Seller | Item | Configuration | Condition | Price | Ship | Stock | Genuine? |
-|---|---|---|---|---|---|---|---|---|---|
-| 2026-09-04 | Global | shop.m5stack.com | **`[EOL]` M5Stack Din Meter w/ M5StampS3** | K134, full bundle | new | USD 24.50 | n/a | **out of stock** | genuine |
-| 2026-09-04 | Global | shop.m5stack.com | **M5Stack Din Meter v1.1 with M5StampS3A** | K134-V11, full bundle | new | **USD 24.50** | not captured | **in stock** | genuine |
-| 2026-09-04 | Global | shop.m5stack.com | `[EOL]` M5Stamp ESP32S3 Module | S007 | new | USD 7.50 | — | **out of stock** | genuine |
-| 2026-09-04 | Global | shop.m5stack.com | M5StampS3A ESP32S3 Module | S007-V033 | new | USD 7.50 | — | in stock | genuine |
-| 2026-09-04 | Global | shop.m5stack.com | M5StampS3A with 1.27 / 2.54 Header Pin | S007-PIN127/254-V033 | new | USD 7.50 each | — | in stock | genuine |
-
-**The `[EOL]` prefix is M5Stack's own**, present in the product title string returned by the API.
-It is not an inference.
-
-Shipping weight for K134-V11 is **70 g** per the Shopify variant record.
-
-## 3. Competitor and sibling prices, same source and date
-
-| Product | SKU | Price | Note |
-|---|---|---|---|
-| **DinMeter v1.1** | K134-V11 | **USD 24.50** | — |
-| M5Stack Dial v1.1 | K130-V11 | USD 34.90 | +USD 10.40 for round + touch, but 5 V only |
-| StamPLC Controller w/ M5StampS3 | — | USD 42.90 | DIN-**rail** controller — different product category |
-| Air Quality Kit v1.1 w/ M5StampS3A | — | USD 89.90 | another Stamp-S3A carrier |
-| M5StampS3 BAT Module | — | USD 9.95 | — |
-| M5StampS3 BreakOut | — | USD 1.95 | — |
-| M5Stack VA Meter w/ M5StampS3 | — | USD 29.90 | the other Stamp-S3 instrument |
-
-## 4. What the numbers mean
-
-**USD 24.50 for what is in the box.** The bundle includes the device, a 250 mA·h Li-ion cell, a
-screw terminal, a back clip, adhesive tape and a pin sticker. Priced against components, the
-board alone (ESP32-S3 module, ST7789 panel, encoder, RTC, three converters, charger) is roughly
-what you would pay for the parts — the enclosure, the DIN fit and the assembly are effectively
-free. That is unusual and is the strongest value argument for the product.
-
-**The USD 10.40 gap to the M5Dial** buys a round 240 × 240 display and a touchscreen, and costs
-you the DIN cutout and the 6–36 V input. See
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) §3.
-
-**A DIY equivalent lands around USD 10–18** in parts and cannot produce the enclosure. §4 of the
-comparisons document works this through.
-
-## 5. Availability and lifecycle
-
-| | Status 2026-09-04 |
-|---|---|
-| DinMeter K134 | **EOL, out of stock** at the vendor |
-| DinMeter v1.1 K134-V11 | current, in stock |
-| Stamp-S3 S007 | **EOL, out of stock** |
-| Stamp-S3A S007-V033 | current, in stock |
-
-So the K134 and the Stamp-S3 went end-of-life **together**, which is consistent with the v1.1
-being a module-substitution driven by the module's own lifecycle rather than by a product
-redesign. The Stamp-S3A appeared 2025-09-11, and the DinMeter v1.1 followed 4½ months later on
-2026-01-30 — the ordering you would expect if the carrier was re-released to consume the new
-module.
-
-**If you need a K134 specifically** (e.g. to match an existing deployment), the vendor no longer
-sells it. Distributors may still hold stock; **no distributor inventory was surveyed in this
-pass** — a declared exclusion.
-
-## 6. Caveats on these observations
-
-- **Single seller.** Only `shop.m5stack.com` was surveyed. Mouser, DigiKey, Amazon, AliExpress
-  and regional distributors were **not** checked. Do not read these as market-wide prices.
-- **Item price only.** Shipping from Shenzhen, import VAT/duty and any distributor margin are
-  excluded and can be a large fraction of a USD 24.50 item.
-- **No currency conversion** was performed; all figures are the store's USD.
-- **No price history.** Shopify's public JSON gives the current price only. The "launch price"
-  rows are the current price of a listing published on that date, not an archived observation.
-- **No used/refurbished market observed.** None found; not systematically searched.
-- **No clones found.** Negative search result, not proof of absence — see
-  [`research-log.md`](research-log.md).
-- **Sample size is one observation per product on one date.** No range, no variance.
-
-## Related
-
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) ·
-[`product-history-and-family.md`](product-history-and-family.md) ·
-[`../dinmeter-v1.1/market-and-pricing.md`](../dinmeter-v1.1/market-and-pricing.md)
-
----
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| [EOL] M5Stack Din Meter w/ M5StampS3 | 2024-03-08 | Default Title | `K134` | **USD 24.50** | ❌ no |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 24.50, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/m5stack-din-meter-w-m5stamps3`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `K134`. This is the **original** DinMeter kit. It is flagged `[EOL]` in the store title and `available: false` — superseded by v1.1.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/dinmeter/media.md b/devices/m5stack/dinmeter/media.md
deleted file mode 100644
index ea468a5..0000000
--- a/devices/m5stack/dinmeter/media.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# DinMeter — images and provenance
-
-Machine-readable records: [`media/manifest.json`](media/manifest.json).
-Applies to K134; the one v1.1-referenced asset is flagged in the manifest.
-
----
-
-## What is retained
-
-**Ten official product images**, all WebP, all retrieved 2026-09-04 from
-`static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/`, all HTTP 200, all validated by
-`RIFF`…`WEBP` magic bytes. Total ≈ 333 KB.
-
-| Field | Value |
-|---|---|
-| Creator / rightsholder | **M5Stack Technology Co., Ltd** — corporate product photography; no individual photographer is credited |
-| Source pages | <https://docs.m5stack.com/en/core/M5DinMeter> and <https://docs.m5stack.com/en/core/DinMeter_v1.1> |
-| Retrieved | 2026-09-04 |
-| Published/updated | **unknown** — the CDN returned no `Last-Modified` in the captured response |
-| Licence | **unknown.** No licence statement on the page or in the files; the footer asserts `Copyright © M5Stack Technology Co., Ltd. All rights reserved.` |
-| Redistribution status | `unknown` |
-| Disposition | `repository`, **unstaged pending user review** |
-| Modifications | **none** — bytes exactly as served. Nothing cropped, rotated, annotated or watermark-stripped |
-
-Per-file SHA-256, byte size, caption and alt text are in the manifest.
-
-## An honest caveat on the captions
-
-The WebP files were validated by magic bytes and hashed, but **not visually rendered** in this
-pass — no image decoder was invoked. So the manifest's captions are generic ("M5Stack DinMeter
-product photograph") for nine of the ten, rather than describing what each specific frame shows.
-
-That is deliberate. Writing "rear view showing the DC terminal" for a file nobody looked at would
-be a fabricated observation dressed as provenance. The one detailed caption
-(`img-1f3aa8b5…`) describes the composition stated by the page context, and is labelled in the
-manifest as such.
-
-**To improve this:** render each file and replace the captions. It is a five-minute job for
-anyone with a browser and it would materially improve the record.
-
-## ⚠ The real gap: no teardown, no PCB, no port close-up
-
-Searched and **not found**, from any source:
-
-| Wanted | Found |
-|---|---|
-| Bare-PCB photograph (front) | **none** |
-| Bare-PCB photograph (back) | **none** |
-| Teardown at any stage | **none** |
-| Close-up of the encoder body's marking | **none** |
-| Close-up of `LS1` (buzzer) marking | **none** |
-| Rear port/label close-up at readable resolution | **none** |
-| Photograph of the bundled pin sticker | **none** |
-| Revision markings / silkscreen | **none** |
-
-This is the **single most consequential media gap in the record**, because photographs would
-settle four separate open questions at once:
-
-1. The **rotary encoder's** manufacturer and part number
-   ([`components/unidentified/m5stack-dinmeter/rotary-encoder`](../../../components/unidentified/m5stack-dinmeter/rotary-encoder/README.md))
-2. The **buzzer `LS1`**'s part number
-   ([`components/unidentified/m5stack-dinmeter/buzzer`](../../../components/unidentified/m5stack-dinmeter/buzzer/README.md))
-3. The **PORT.A / PORT.B wire-colour conflict**, from the rear silkscreen or the pin sticker
-   ([`gaps-and-conflicts.md`](gaps-and-conflicts.md) §1)
-4. Whether the **v1.1 PCB really is the v1.0 PCB**, which the byte-identical published assets
-   cannot establish ([`gaps-and-conflicts.md`](gaps-and-conflicts.md) §3)
-
-## Related images held under components
-
-Not duplicated here; filed by what they describe:
-
-| Image | Where |
-|---|---|
-| Stamp-S3 official pin map (`S007_PinMap_01.jpg`, 631 459 B) | [`components/m5stack/stamp-s3/artifacts/`](../../../components/m5stack/stamp-s3/artifacts/S007_PinMap_01.jpg) |
-| Stamp-S3A official pin map (`S007-V033_PinMap_01.jpg`, 693 286 B) | [`components/m5stack/stamp-s3a/artifacts/`](../../../components/m5stack/stamp-s3a/artifacts/S007-V033_PinMap_01.jpg) |
-
-Both are **JPEG diagrams that were not OCR'd** in this pass. Reading the Stamp-S3A pin map is the
-other thing that would settle the FPC-numbering question in
-[`../dinmeter-v1.1/stamp-s3-to-s3a-delta.md`](../dinmeter-v1.1/stamp-s3-to-s3a-delta.md) §6.
-
-## Image search that was not performed
-
-- No reverse-image search for community teardowns.
-- No video sources (a teardown video frame would count as evidence with proper attribution).
-- No Chinese-language platforms, where M5Stack teardowns often appear first.
-
-All declared exclusions — see [`research-log.md`](research-log.md) §9.
diff --git a/devices/m5stack/dinmeter/media/img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp b/devices/m5stack/dinmeter/media/img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp
deleted file mode 100644
index c3fe9c7..0000000
Binary files a/devices/m5stack/dinmeter/media/img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-71baa86c-292a-4905-ad68-f2733320e4ab.webp b/devices/m5stack/dinmeter/media/img-71baa86c-292a-4905-ad68-f2733320e4ab.webp
deleted file mode 100644
index 3b29c51..0000000
Binary files a/devices/m5stack/dinmeter/media/img-71baa86c-292a-4905-ad68-f2733320e4ab.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp b/devices/m5stack/dinmeter/media/img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp
deleted file mode 100644
index 1804d24..0000000
Binary files a/devices/m5stack/dinmeter/media/img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp b/devices/m5stack/dinmeter/media/img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp
deleted file mode 100644
index fdb5683..0000000
Binary files a/devices/m5stack/dinmeter/media/img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp b/devices/m5stack/dinmeter/media/img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp
deleted file mode 100644
index 14681c9..0000000
Binary files a/devices/m5stack/dinmeter/media/img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-af3c8884-3669-4305-af73-979e32fe176f.webp b/devices/m5stack/dinmeter/media/img-af3c8884-3669-4305-af73-979e32fe176f.webp
deleted file mode 100644
index 54d15a1..0000000
Binary files a/devices/m5stack/dinmeter/media/img-af3c8884-3669-4305-af73-979e32fe176f.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp b/devices/m5stack/dinmeter/media/img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp
deleted file mode 100644
index 0412979..0000000
Binary files a/devices/m5stack/dinmeter/media/img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp b/devices/m5stack/dinmeter/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp
deleted file mode 100644
index 607cb0e..0000000
Binary files a/devices/m5stack/dinmeter/media/img-dff307df-3121-4405-b12f-eee5e136a321.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp b/devices/m5stack/dinmeter/media/img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp
deleted file mode 100644
index 9084679..0000000
Binary files a/devices/m5stack/dinmeter/media/img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp b/devices/m5stack/dinmeter/media/img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp
deleted file mode 100644
index 6ec1570..0000000
Binary files a/devices/m5stack/dinmeter/media/img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/manifest-schematic-crops.json b/devices/m5stack/dinmeter/media/manifest-schematic-crops.json
deleted file mode 100644
index 104af03..0000000
--- a/devices/m5stack/dinmeter/media/manifest-schematic-crops.json
+++ /dev/null
@@ -1,71 +0,0 @@
-{
-  "$schema-note": "Image provenance manifest for images DERIVED from retained schematic PDFs by local rasterisation. Kept separate from media/manifest.json so that no pre-existing file is modified; an index owner may merge them.",
-  "device": "m5stack/dinmeter",
-  "generated": "2026-09-07",
-  "generator": "2026-09-07 schematic net-tracing pass; poppler 26.06.0 + ImageMagick",
-  "global_notes": [
-    "These are NOT photographs and NOT vendor-published images. Each is a crop of a page the vendor published as a vector PDF, rasterised locally at 300 dpi.",
-    "pdfimages could not be used: pdfimages -list reports ZERO embedded rasters in every source PDF here. The drawings are vector, so pdftoppm plus a crop is the only route. This is recorded because reaching for pdfimages is the obvious wrong first move.",
-    "Copyright in the underlying drawing remains with the vendor named in creator_rightsholder. Licence is UNKNOWN: no licence statement appears in any of the source PDFs. Redistribution status unknown; disposition repository, unstaged pending user review.",
-    "Every image is reproducible byte-for-byte from the retained artifact using the recorded generation_command, so none of them is uniquely held here.",
-    "Each image exists because it settles a specific documented question; see why_retained."
-  ],
-  "images": [
-    {
-      "local_path": "media/schematic-J5-rotary-encoder-5pin.png",
-      "filename": "schematic-J5-rotary-encoder-5pin.png",
-      "sha256": "b4167b0734edd67d383daeb7a1f04cf5d8d87997a00b5362aae0abd8cd5a1b5d",
-      "bytes": 31921,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export; 1 page; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 700x420+1780+1440 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "700x420+1780+1440",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "K134 (DinMeter v1.0); the v1.1 sheet extracts identically",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: rotary encoder connector J5, five pins",
-      "alt_text": "Schematic detail of a yellow symbol J5 captioned 'Rotary encode'. The upper half shows a switch contact between pins labelled b1 and b2, pin 1 going left to net BTN and pin 2 right to GND. The lower half shows three pins labelled A, COM and B, numbered 3, 4 and 5, with A and B dropping to nets IN_A and IN_B and 10 kilohm pull-ups R2 and R3, and COM going to GND.",
-      "why_retained": "Corrects the recorded seven-pad reading: the symbol has five pins. Establishes the topology as a three-terminal quadrature encoder with common grounded plus an integrated push switch."
-    },
-    {
-      "local_path": "media/schematic-LS1-buzzer-drive.png",
-      "filename": "schematic-LS1-buzzer-drive.png",
-      "sha256": "06c2bb060746ad433e3cd0ad103f054101f5c0251816dea478b36464ad6fb506",
-      "bytes": 32274,
-      "format": "PNG (validated: \\x89PNG magic)",
-      "magic_ok": true,
-      "kind": "schematic detail (derived)",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "not applicable - derived locally from a retained artifact",
-      "derived_from": "artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf",
-      "derived_from_page": 1,
-      "source_pdf_metadata": "Altium Designer export; 1 page; pdfimages -list reports ZERO embedded rasters",
-      "generation_command": "nix-shell -p poppler-utils imagemagick --run 'pdftoppm -f 1 -l 1 -r 300 -png <pdf> /tmp/page && magick /tmp/page-1.png -crop 750x480+60+1750 +repage -bordercolor white -border 14 -strip <out>'",
-      "crop_geometry_px_at_300dpi": "750x480+60+1750",
-      "render_dpi": 300,
-      "retrieved": "2026-09-07",
-      "published_or_updated": "inherits the source PDF's date; see source_pdf_metadata",
-      "applies_to_revision": "K134 (DinMeter v1.0); the v1.1 sheet extracts identically",
-      "licence": "unknown",
-      "licence_evidence": "none found; the source PDF carries the vendor's own title block and no licence statement",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "DERIVED IMAGE. Rasterised from the vendor's vector PDF at 300 dpi with pdftoppm, cropped to the stated geometry, given a 14 px white border, and stripped of metadata. No content was altered, annotated, rotated or retouched. The command above reproduces the file exactly.",
-      "caption": "Schematic crop: buzzer LS1 and its drive circuit",
-      "alt_text": "Schematic detail showing a buzzer symbol LS1 captioned 'Buzzer' with diode D6 1N4148WT drawn anti-parallel across it, both between the supply rail and the collector of transistor Q5, an SS8050 NPN. The base path runs from net beep through resistor R25 470 ohm and then through capacitor C27 10 microfarad in series, with diode D7 1N4148WT clamping the base node to ground.",
-      "why_retained": "Shows C27 is a series coupling capacitor in the base path rather than bulk decoupling, and shows D6 as a flyback catch diode, which establishes the transducer as inductive (magnetic) rather than piezo."
-    }
-  ]
-}
diff --git a/devices/m5stack/dinmeter/media/manifest.json b/devices/m5stack/dinmeter/media/manifest.json
deleted file mode 100644
index 8637478..0000000
--- a/devices/m5stack/dinmeter/media/manifest.json
+++ /dev/null
@@ -1,244 +0,0 @@
-{
-  "$schema-note": "Image provenance manifest. One record per retained image. Fields follow the hardware-device-research media-provenance requirements.",
-  "device": "m5stack/dinmeter",
-  "generated": "2026-09-04",
-  "generator": "manual, during the 2026-09-04 DinMeter research pass",
-  "global_notes": [
-    "All images were retrieved 2026-09-04 from static-cdn.m5stack.com, the CDN that serves docs.m5stack.com's product pages. Each returned HTTP 200 and RIFF/WEBP magic bytes.",
-    "Creator/rightsholder: M5Stack Technology Co., Ltd (corporate product photography; no individual photographer is credited anywhere on the page).",
-    "Licence: UNKNOWN. No licence statement appears on the product page or in the image metadata; the page footer asserts 'Copyright (c) M5Stack Technology Co., Ltd. All rights reserved.'",
-    "Redistribution status: unknown. Disposition: repository (unstaged pending user review).",
-    "No image was cropped, rotated, annotated, watermark-removed or otherwise modified. Bytes are exactly as served.",
-    "Individual captions are generic where the specific subject of a photograph could not be determined without rendering it. This is stated rather than guessed: the WebP files were validated by magic bytes but not visually inspected in this pass.",
-    "GAP: no teardown photograph, no bare-PCB photograph and no rear/port close-up of the DinMeter was located from any source. See media.md."
-  ],
-  "images": [
-    {
-      "local_path": "media/img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp",
-      "filename": "img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp",
-      "sha256": "d1b53d2e662ff8c5d0c0fda67721d3b8eac1af131b91166cd7093b4de3988b71",
-      "bytes": 24358,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "front",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-1f3aa8b5-36dd-4dd7-8359-9f13f1f399dc.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product hero \u2014 DinMeter front three-quarter",
-      "alt_text": "DinMeter seen from the front and slightly above: dark rectangular body, bright orange knurled rotary knob on the left, 1.14-inch landscape LCD on the right."
-    },
-    {
-      "local_path": "media/img-71baa86c-292a-4905-ad68-f2733320e4ab.webp",
-      "filename": "img-71baa86c-292a-4905-ad68-f2733320e4ab.webp",
-      "sha256": "093479d5ad0fe5e5ce3ebd1c11cb2fbaa46a39303972780c0cdbb0296c1c4713",
-      "bytes": 11666,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-71baa86c-292a-4905-ad68-f2733320e4ab.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp",
-      "filename": "img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp",
-      "sha256": "f36fa045c7c3193eb67aad1ae33a76a029c5b80d62e89c7539f1d8b8521ecadd",
-      "bytes": 20488,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-852a5a75-f6b9-4ec7-8a5a-9f402b73d568.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp",
-      "filename": "img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp",
-      "sha256": "c3ddcde9ab961823a86c02ee9dcd85439dc5e0809b04264dd37ebb22a2b9632a",
-      "bytes": 27418,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-a76fdd1f-9d4c-46a6-b112-ea0c2119f1dc.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp",
-      "filename": "img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp",
-      "sha256": "1fc457e99c7b6525eddeeb10ccf6ad500f2d57bcdd28a8670c95593746d2571e",
-      "bytes": 101360,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-ae5aaf34-6458-47c7-89ee-280ec06fb542.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view (largest asset on the page)",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-af3c8884-3669-4305-af73-979e32fe176f.webp",
-      "filename": "img-af3c8884-3669-4305-af73-979e32fe176f.webp",
-      "sha256": "06d73cd30da9b7404f33c48318f4d7c12a64ae2f6740909a700aef09f4f7024c",
-      "bytes": 39006,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-af3c8884-3669-4305-af73-979e32fe176f.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp",
-      "filename": "img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp",
-      "sha256": "d351219482f348e45c765b3e5b3de72d63d5e3e0e71e30f581c76bad7d1fd024",
-      "bytes": 36126,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-d8f8f858-0614-4829-b462-d1b1c4decfab.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp",
-      "filename": "img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp",
-      "sha256": "4f9a7f4c0fe095da08ad2eced07b6f15fa7abafc802fed4dca3488cef103eef2",
-      "bytes": 12974,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-e313bbbd-0330-430b-9aee-3f8d54ba8d8f.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp",
-      "filename": "img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp",
-      "sha256": "ebecbc8cdf08f8a7b807b30cd5507d59758f2fc75186dd80eea485f91ccb4fdf",
-      "bytes": 34452,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/M5DinMeter",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-f6f2cf5f-8b72-49b4-8d6c-c48467810e89.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134 (DinMeter v1.0)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Product view",
-      "alt_text": "M5Stack DinMeter product photograph."
-    },
-    {
-      "local_path": "media/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-      "filename": "img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-      "sha256": "82916ce50a40391698e3f15e57c2effe21ffcd81324601fec53e4a1459f7276f",
-      "bytes": 24884,
-      "format": "WebP (validated: RIFF....WEBP magic)",
-      "magic_ok": true,
-      "kind": "product-v1.1",
-      "creator_rightsholder": "M5Stack Technology Co., Ltd",
-      "source_page": "https://docs.m5stack.com/en/core/DinMeter_v1.1",
-      "direct_url": "https://static-cdn.m5stack.com/resource/docs/products/core/M5DinMeter/img-dff307df-3121-4405-b12f-eee5e136a321.webp",
-      "retrieved": "2026-09-04",
-      "published_or_updated": "unknown (CDN serves no Last-Modified date in the captured response)",
-      "applies_to_revision": "K134-V11 (DinMeter v1.1)",
-      "licence": "unknown",
-      "licence_evidence": "none found; vendor copyright asserted in the page footer",
-      "redistribution_status": "unknown",
-      "disposition": "repository (unstaged pending user review)",
-      "modifications": "none",
-      "caption": "Image referenced from the DinMeter v1.1 page",
-      "alt_text": "Image served from the M5DinMeter media directory and referenced by the DinMeter v1.1 documentation page."
-    }
-  ],
-  "counts": {
-    "retained": 10,
-    "teardown": 0,
-    "pcb": 0,
-    "port_closeup": 0,
-    "annotated": 0
-  }
-}
\ No newline at end of file
diff --git a/devices/m5stack/dinmeter/media/schematic-J5-rotary-encoder-5pin.png b/devices/m5stack/dinmeter/media/schematic-J5-rotary-encoder-5pin.png
deleted file mode 100644
index 3c9cce2..0000000
Binary files a/devices/m5stack/dinmeter/media/schematic-J5-rotary-encoder-5pin.png and /dev/null differ
diff --git a/devices/m5stack/dinmeter/media/schematic-LS1-buzzer-drive.png b/devices/m5stack/dinmeter/media/schematic-LS1-buzzer-drive.png
deleted file mode 100644
index c9f29a0..0000000
Binary files a/devices/m5stack/dinmeter/media/schematic-LS1-buzzer-drive.png and /dev/null differ
diff --git a/devices/m5stack/dinmeter/performance.md b/devices/m5stack/dinmeter/performance.md
deleted file mode 100644
index 78c86fd..0000000
--- a/devices/m5stack/dinmeter/performance.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# DinMeter — performance
-
-**Nothing in this document was measured.** No hardware was available. This page exists to state
-exactly what is known, what is claimed by whom, what can be derived arithmetically, and what
-would have to be measured — rather than to present an unmeasured device as characterised.
-
----
-
-## 1. Vendor-claimed figures
-
-Every one of these is a **vendor claim with no published method** — no instrument, no sample
-count, no clock/radio/peripheral state, no ambient temperature.
-
-| Workload | Device/config | Figure | Source | Status |
-|---|---|---|---|---|
-| Standby (latched off, battery) | DinMeter, DC 4.2 V | **38.4 µA** | both product pages | official claim |
-| Sleep | Stamp-S3, `VIN_5V` | 310.89 µA | Stamp-S3 page | official claim |
-| Sleep | **Stamp-S3A**, `VIN_5V` | **6.84 µA** | Stamp-S3A page | official claim |
-| Sleep | Stamp-S3, USB-C | 400.67 µA | Stamp-S3 page | official claim |
-| Sleep | **Stamp-S3A**, USB-C | **88.82 µA** | Stamp-S3A page | official claim |
-| Standby (active, radio state unstated) | Stamp-S3, `VIN_5V` | 33.56 mA | Stamp-S3 page | official claim |
-| Standby | **Stamp-S3A**, `VIN_5V` | **25.53 mA** | Stamp-S3A page | official claim |
-| Grove port load | either port | 5 V @ 220 mA max | both product pages | official claim |
-| Charge current | — | 100 mA | both product pages | official claim |
-
-**Two decimal places on an unspecified method is not precision, it is formatting.** Treat
-`6.84 µA` as "single-digit microamps under some sleep configuration".
-
-**Note the 38.4 µA figure is identical on the v1.0 and v1.1 pages** despite the module's sleep
-current improving ~45×. That is internally consistent: the board *cuts the battery* with a latch
-rather than sleeping the SoC, so the residual is dominated by the carrier's LDO and latch
-network, not by the module. It is also a useful cross-check that M5Stack did not simply
-copy-paste the number — the module numbers *did* change on the same pages.
-
-## 2. Silicon limits (not measurements)
-
-| Property | Value | Source |
-|---|---|---|
-| CPU | Xtensa LX7 dual-core, up to **240 MHz** | ESP32-S3 datasheet |
-| SRAM | ~512 KB internal | ESP32-S3 datasheet |
-| **PSRAM** | **none** | `ESP32-S3FN8`; confirmed by `build_unflags = -DBOARD_HAS_PSRAM` in `bmorcelli/Launcher` |
-| Flash | 8 MB in-package | vendor spec |
-| Display SPI clock as configured | **40 MHz** | three independent sources agree |
-| Wi-Fi | 2.4 GHz 802.11 b/g/n | ESP32-S3 datasheet |
-| Bluetooth | BLE 5 only, **no Classic** | ESP32-S3 datasheet |
-
-## 3. Derivable arithmetic (labelled as such, not as measurement)
-
-**Display throughput ceiling.** 135 × 240 × 16 bpp = 64 800 B = 518 400 bits per full frame. At
-40 MHz SPI with zero overhead that is **≈ 77 full frames/s**. Real figures will be materially
-lower — SPI transaction overhead, DMA setup, `startWrite`/`endWrite` batching, and the CPU time
-to *produce* the pixels. `inferred` arithmetic; **no frame rate was measured**.
-
-**Framebuffer cost.** A full-screen `M5Canvas` sprite is **64 800 B** of the ESP32-S3's ~512 KB
-SRAM, with no PSRAM to spill into. Espressif's board definition sizes its SPI transfers at
-`max_transfer_sz: 6480` = 135 × 24 lines × 2 B, i.e. a **24-line band buffer** — a deliberate
-choice on a PSRAM-less part, and the right default.
-
-**Battery life, first-order.** Bundled cell is 250 mA·h.
-
-| Duty | Current | Runtime |
-|---|---|---|
-| Continuously awake with radio (Stamp-S3A standby figure) | 25.53 mA | **≈ 9.8 h** |
-| Continuously awake (Stamp-S3 figure) | 33.56 mA | ≈ 7.4 h |
-| Latched off between RTC wakes | 38.4 µA | **≈ 271 days** at zero duty |
-| 10 s awake per minute | ≈ 4.3 mA average | ≈ 2.4 days |
-
-`inferred` from vendor figures ÷ nominal capacity. Ignores cell ageing, the 3.0 V cut-off,
-converter efficiency at low load, and the inrush of waking. **Do not design to these**; they
-show the shape of the problem, which is that this device is only a long-life device if you use
-the RTC latch.
-
-## 4. Stamp-S3 → Stamp-S3A, as a percentage
-
-| Metric | S3 | S3A | Δ |
-|---|---|---|---|
-| Sleep, `VIN_5V` | 310.89 µA | 6.84 µA | **−97.8 %** |
-| Sleep, USB-C | 400.67 µA | 88.82 µA | **−77.8 %** |
-| Standby, `VIN_5V` | 33.56 mA | 25.53 mA | −23.9 % |
-| Standby, USB-C | 33.04 mA | 25.54 mA | −22.7 % |
-
-Mechanistically consistent with the two power changes found in the schematics: a modern buck IC
-with selectable light-load modes replacing a fixed µPOL module, plus removing the WS2812B-2020's
-quiescent draw from the always-on 3.3 V rail (a WS2812B-2020 idles around 0.6–1 mA). That
-accounts for roughly the standby delta on its own. **`inferred` — not decomposed, not measured.**
-
-## 5. What was NOT measured
-
-Stated as a list so no reader mistakes silence for a null result.
-
-| Workload | Status |
-|---|---|
-| Boot time | **not measured** |
-| Display frame rate, fill rate, tearing | **not measured** |
-| Encoder maximum tracked rotation rate | **not measured** |
-| SPI throughput at 40 MHz | **not measured** |
-| Wi-Fi throughput, RSSI, range | **not measured** |
-| **RF: whether the Stamp-S3A antenna is actually better** | **not measured** — the vendor's claim is qualitative and uncorroborated |
-| BLE latency / connection interval | **not measured** |
-| Actual current in any state | **not measured** |
-| Buzzer SPL and resonant frequency | **not measured** |
-| Grove 5 V rail actual voltage (5.00 or ≈5.38 V?) | **not measured** — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §6 |
-| Thermal behaviour, throttling | **not measured** |
-| Behaviour at 36 V input | **not measured** |
-| Charge-cycle profile | **not measured** |
-| Battery runtime, real | **not measured** |
-
-## 6. If you have hardware — the measurements worth taking, in order
-
-1. **Current in each state**, with a µA-capable meter: latched off, idle with radio off, Wi-Fi
-   associated, display on at full brightness. Confirms or destroys the entire battery story.
-2. **Grove rail voltage** on `J3` pin 3. One reading, settles a documented conflict.
-3. **Display frame rate** for a full-screen fill and for a band-buffered update.
-4. **Wi-Fi RSSI at a fixed distance, v1.0 vs v1.1** — the only way to test the antenna claim.
-5. **Buzzer SPL swept 1–12 kHz** — finds the resonance the datasheet does not exist to state.
-
-Each records device revision, software versions, method, environment, sample count, units and
-variability. Results belong here and in
-[`compatibility-and-status.md`](compatibility-and-status.md).
-
-## Related
-
-[`features/power-and-battery.md`](features/power-and-battery.md) ·
-[`resources-and-conflicts.md`](resources-and-conflicts.md) ·
-[`../dinmeter-v1.1/stamp-s3-to-s3a-delta.md`](../dinmeter-v1.1/stamp-s3-to-s3a-delta.md)
diff --git a/devices/m5stack/dinmeter/pinouts-and-buses.md b/devices/m5stack/dinmeter/pinouts-and-buses.md
deleted file mode 100644
index 2ba6a99..0000000
--- a/devices/m5stack/dinmeter/pinouts-and-buses.md
+++ /dev/null
@@ -1,332 +0,0 @@
-# DinMeter — pinouts and buses
-
-Applies to **both** K134 (v1.0) and K134-V11 (v1.1). The two boards share a byte-identical
-published schematic (SHA-256 `03ec3353…`) and an identical vendor PinMap; see
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) §3.
-
-**Evidence markers** as in [`README.md`](README.md#evidence-labelling).
-
----
-
-## 1. How this table was derived
-
-The schematic is an Altium PDF publication. Altium emits an invisible marker layer —
-`CO<designator>`, `PI<designator><pin>`, `NL<netname>` — at every component outline, pin
-instance and net label. Those markers were extracted with a glyph-position parse
-([`artifacts/schematic/parse_dinmeter_sch.py`](artifacts/schematic/parse_dinmeter_sch.py),
-`executed-success`), deduplicated (Altium draws the marker layer twice; without dedup the text
-interleaves as `PPIIJJ110011` instead of `PIJ10101`), and each `M1` pad was matched to the
-visible pin-name and net-label text on its own row.
-
-**Text-layer validation.** Before transcribing any value, the extracted text was checked against
-known headings visible in the document: the sheet-frame zone letters `A`/`B`/`C`/`D` and numbers
-`1`–`4` appear at the expected page-frame coordinates, `TP4057`, `SY7088`, `BL8075CB5TR33`,
-`ME3116AM6G`, `STAMP-S3-SMD`, `RTC8563` and `32.768KHz ±20ppm 12.5pF` all render as legible
-strings in the right places, and the marker bodies decode to designators that match the visible
-designator text 84 times out of 85. The text layer is sound. **[SCH]**
-
-**Completeness.** 85 `CO` bodies (one of which is a truncated bare `M`, i.e. `M1`), 238 `PI`
-markers, 25 `NL` markers, 553 visible text runs. All 31 `M1` pads were recovered. A back-of-
-envelope pin count for 84 parts is ~260, so roughly 20 `PI` markers were **not** recovered —
-Altium glues some markers to adjacent text in a way the negative-lookbehind rule (needed to stop
-`GPIO0` parsing as a `PI` marker) discards. Every `M1`, `J3`, `J4`, `J5`, `FPC1`, `U5` and `U6`
-pad *was* recovered, so no table below rests on a missing marker.
-
----
-
-## 2. `M1` — Stamp-S3 module, all 31 pads
-
-Read directly from the `PIM10xx` pin markers with their row-matched pin names and net labels.
-**[SCH]** Cross-checked against the vendor PinMap **[DOC]** and against
-`M5Unified/src/M5Unified.cpp` **[SRC]**; agreements and the one disagreement are noted.
-
-| `M1` pad | Stamp pin name | ESP32-S3 GPIO | Board net | Function | Direction | Cross-check |
-|---:|---|---|---|---|---|---|
-| 1 | `G1` | GPIO1 | `GI` | **PORT.B** signal 1 | I/O | **[SRC]** `M5Unified.cpp:159` port-B p1 |
-| 2 | `G2` | GPIO2 | `GO` | **PORT.B** signal 2 | I/O | **[SRC]** `:159` port-B p2 |
-| 3 | `G3` | GPIO3 | `beep` | **Buzzer** drive → `Q5` base via `R25` 470 Ω | O | **[SRC]** `:2921-2928` `spk_cfg.pin_data_out = GPIO_NUM_3` |
-| 4 | `G4` | GPIO4 | `LCD_RS` | Display D/C | O | **[DOC]** `RS`; **[SRC]** `dc_gpio_num: 4` |
-| 5 | `G5` | GPIO5 | `LCD_MOSI` | Display SPI MOSI | O | **[SRC]** `mosi_io_num: 5` |
-| 6 | `G6` | GPIO6 | `LCD_SCK` | Display SPI SCLK | O | **[SRC]** `sclk_io_num: 6` |
-| 7 | `G7` | GPIO7 | `LCD_CS` | Display chip select | O | **[SRC]** `cs_gpio_num: 7` |
-| 8 | `G8` | GPIO8 | `LCD_RESET` | Display reset, active-low | O | **[SRC]** `reset_gpio_num: 8` |
-| 9 | `G9` | GPIO9 | `LCD_BL` | Backlight enable → `U6` AW35122FDR | O | **[SRC]** `ledc_backlight gpio_num: 9` |
-| 10 | `G10` | GPIO10 | `BATADC` | Battery voltage sense, `R7`/`R8` 1 MΩ divider | AI | **[SCH]** |
-| 11 | `GND` | — | `GND` | Ground | P | **[SCH]** |
-| 12 | `G11` | GPIO11 | `IN_SDA` | **Internal I²C SDA** (RTC) | I/O | **[SRC]** `:96` In SDA |
-| 13 | `5V` | — | `+5VIN` | Module 5 V supply in | P | **[SCH]** |
-| 14 | `G12` | GPIO12 | `IN_SCL` | **Internal I²C SCL** (RTC) | I/O | **[SRC]** `:96` In SCL |
-| 15 | `G13` | GPIO13 | `SDA` | **PORT.A** — see §5 | I/O | **[SRC]** `:96` EX SDA |
-| 16 | `G14` | GPIO14 | `G14` | Power-latch OR network (`D7` 1N4148WT + `R9` 10 kΩ) | I/O | **[SCH]** |
-| 17 | `G15` | GPIO15 | `SCL` | **PORT.A** — see §5 | I/O | **[SRC]** `:96` EX SCL |
-| 18 | `GND` | — | `GND` | Ground | P | **[SCH]** |
-| 19 | `G39/MTCK` | GPIO39 | `G39` | Power-latch OR network (`D6`?/`R10` 10 kΩ) — see §4 | I/O | **[SCH]** |
-| 20 | `G0/Boot` | GPIO0 | — | Boot strap; **the button is on the Stamp**, not the carrier | I | **[DOC]**; **[SRC]** `:3504` BtnB |
-| 21 | `G40/MTDO` | GPIO40 | `IN_B` | **Encoder channel B**, `R3` 10 kΩ pull-up | I | **[SRC]** `M5DinMeter.h:9` `DIAL_ENCODER_PIN_B 40` |
-| 22 | `EN` | — | — | Module reset, driven by `S4` RST | I | **[SCH]** |
-| 23 | `G41/MTDI` | GPIO41 | `IN_A` | **Encoder channel A**, `R2` 10 kΩ pull-up | I | **[SRC]** `M5DinMeter.h:8` `DIAL_ENCODER_PIN_A 41` |
-| 24 | `G44/Rx` | GPIO44 | *(none)* | **Free — no net label on the sheet** | — | **[SCH]** |
-| 25 | `G42/MTMS` | GPIO42 | `WAKE` | **Encoder push-button / wake key**, `R1` 10 kΩ pull-up, `C1` 100 nF | I | **[SRC]** `:3502-3505` `!gpio_in(GPIO_NUM_42)` = BtnA |
-| 26 | `G43/Tx` | GPIO43 | *(none)* | **Free — no net label on the sheet** | — | **[SCH]** |
-| 27 | `G46` | GPIO46 | `HOLD` | **Power latch, active-high** → `Q4` LN2324DT2AG | O | **[SRC]** `:282` POWER_HOLD `GPIO_NUM_46`; **[DOC]** |
-| 28 | `3V3` | — | `3V3` | Module 3.3 V (from `U4` BL8075) | P | **[SCH]** |
-| 29 | *(GND)* | — | `GND` | Ground pad | P | **[SCH]** rotated pin number |
-| 30 | *(GND)* | — | `GND` | Ground pad | P | **[SCH]** |
-| 31 | *(GND)* | — | `GND` | Ground pad | P | **[SCH]** |
-
-> **Pads 29–31.** Their pin numbers are drawn rotated, so the glyphs extract stacked (`9`+`2`,
-> `0`+`3`, `1`+`3`) and read bottom-up as 29 / 30 / 31. All three sit on `GND`. This is a
-> reading of rotated text, not an inference: the three pad markers `PIM1029`, `PIM1030`,
-> `PIM1031` are present at the corresponding coordinates. **[SCH]**
-
-> **Pads 24 and 26 (GPIO43/GPIO44, the UART0 pins) carry no net label.** That is a *blank cell*,
-> not a drawn no-connect marker, so it is "unknown but almost certainly unused" rather than a
-> designer's positive assertion. Treat them as probably-free but verify with a meter before
-> relying on them. **[SCH]** **[INF]**
-
----
-
-## 3. Bus summary
-
-| Bus | Signals | GPIO | Peripheral | Address / mode | Evidence |
-|---|---|---|---|---|---|
-| **Internal I²C** | SCL / SDA | 12 / 11 | `U5` BM8563 RTC | 7-bit **0x51** (`0xA2` write / `0xA3` read) | **[SRC]** `M5Unified.cpp:96`, `esp-board-manager` `board_peripherals.yaml`; **[DOC]** BM8563 datasheet |
-| **External I²C (PORT.A)** | SCL / SDA | **15 / 13** per M5Unified | user Grove units | 100/400 kHz | **[SRC]** `M5Unified.cpp:96` |
-| **Display SPI** | SCLK / MOSI / CS / DC / RST | 6 / 5 / 7 / 4 / 8 | `FPC1` → ST7789V2 | `SPI2_HOST`, mode 0, ≤ 40 MHz, **write-only (no MISO)** | **[SRC]** `esp-board-manager` `spi_display`; **[DOC]** |
-| **Backlight PWM** | `LCD_BL` | 9 | `U6` AW35122FDR → panel LED | LEDC ch 0, timer 0, 5 kHz, 10-bit | **[SRC]** `esp-board-manager` `ledc_backlight` |
-| **Buzzer PWM** | `beep` | 3 | `Q5` SS8050 → `LS1` | LEDC ch 1, timer 1, ~4 kHz; M5Unified uses `magnification 48`, `buzzer = true` | **[SRC]** `M5Unified.cpp:2921-2928` |
-| **Quadrature encoder** | A / B | 41 / 40 | rotary encoder on `J5` | PCNT 2-channel, `max_glitch_ns 1000`, ±1000 limits | **[SRC]** `esp-board-manager` `pcnt_encoder` |
-| **PORT.B GPIO** | sig1 / sig2 | 1 / 2 | user | plain GPIO / ADC / PWM | **[SRC]** `M5Unified.cpp:159` |
-| **USB** | D+ / D− | 19 / 20 | native USB-OTG / Serial-JTAG, USB-C **on the Stamp module** | — | **[SCH]** Stamp `U1` pins 25/26 |
-
----
-
-## 4. Power tree and the latch
-
-| Designator | Part | Role | Key passives | Evidence |
-|---|---|---|---|---|
-| `J1` | 2-pin 2.54 mm screw terminal (`DB2EK-2.54-2P-GN-S`, Ningbo Dibo, green) | **6–36 V DC input** | — | **[SCH]** **[DOC]** |
-| `D13`, `D12`, `D11`, `D9` | B5819W / SD36 Schottky | input protection / clamp | — | **[SCH]** |
-| `U1` | **ME3116AM6G** | wide-input buck → `+5VIN` | `L1` 10 µH (3015), `C24` 10 µF/35 V, FB `R5` 56 kΩ / `R6` 10 kΩ | **[SCH]** |
-| `U7` | **CN809J** | reset supervisor on `+5VIN` | — | **[SCH]** |
-| `J2` | 1.25 mm 2-pin JST-style (`1.25WT-2P`) | Li-ion battery | — | **[SCH]** **[DOC]** |
-| `U2` | **TP4057** | linear Li-ion charger, 4.24 V float | `R13` 3.3 kΩ (PROG), `D1`/`D2`/`D3` status LEDs | **[SCH]** |
-| `Q3`, `Q6` | **AP40P05** P-channel MOSFET | battery power path (`VBAT_IN` → `VBAT_OUT`) | `R14`/`R15` 100 kΩ | **[SCH]** |
-| `Q4` | **LN2324DT2AG** | `HOLD` (GPIO46) gate for the latch | `R23` 100 kΩ | **[SCH]** |
-| `U3` | **SY7088** | boost `VBAT_OUT` → `+5VOUT` | `L4` 1.5 µH, FB `R16` 52.3 kΩ / `R18` 15 kΩ, `C18`/`C19` 22 µF | **[SCH]** |
-| `U4` | **BL8075CB5TR33** | 3.3 V LDO → `+3.3V` | `C30` 22 µF, `C31` 100 nF | **[SCH]** |
-| `S1` | `SW-PB` "WAKE" | wake button symbol — **no marker layer, see §6** | `R1` 10 kΩ | **[SCH]** |
-| `S4` | `SW-PB` "RST" | module reset | — | **[SCH]** |
-| `R7`, `R8` | 1 MΩ each | `BATADC` divider → GPIO10 | — | **[SCH]** |
-
-The vendor prints `Vout = 1.2 V × (R1/R2 + 1)` beside `U3`. With `R16` = 52.3 kΩ and `R18` =
-15 kΩ that gives **1.2 × (52.3/15 + 1) ≈ 5.38 V** on `+5VOUT` — the Grove rail. **[SCH]** plus
-arithmetic; the vendor states the rail as "5 V" **[DOC]**. If you are powering something
-voltage-sensitive from a Grove port, measure it.
-
-**Latch behaviour, from the vendor Learn section** **[DOC]**:
-
-- *Power on (battery only):* press **WAKE**, or let the RTC `INT` fire. Firmware must then set
-  `HOLD` (GPIO46) high **during initialisation**, or the board falls back asleep.
-- *Power off (no USB):* press **RST**, or set GPIO46 low in software.
-
-`G14` (pad 16) and `G39` (pad 19) each sit on a 10 kΩ + 1N4148WT network tied into this
-circuit. Their exact role — most plausibly a diode-OR of wake sources into the latch — was
-**not fully traced** in this pass and is recorded as a gap. **[SCH]** **[INF]**
-
----
-
-## 5. Grove ports — and the colour conflict
-
-Schematic pin order, read from `PIJ30x` / `PIJ40x`: **[SCH]**
-
-| Connector | pin 1 | pin 2 | pin 3 | pin 4 |
-|---|---|---|---|---|
-| `J3` `HY-2.0_IIC` (**PORT.A**) | `IIC_SCL` → `M1`.17 = **GPIO15** | `IIC_SDA` → `M1`.15 = **GPIO13** | `VCC` = `+5VOUT` | `GND` |
-| `J4` `HY-2.0_IO` (**PORT.B**) | `GI` → `M1`.1 = **GPIO1** | `GO` → `M1`.2 = **GPIO2** | `VCC` = `+5VOUT` | `GND` |
-
-Pull-ups `R2`, `R3` = 10 kΩ on PORT.A. Load limit 5 V @ 220 mA per port. **[DOC]**
-
-> ### ⚠ Conflict: which wire is which
->
-> The vendor PinMap renders PORT.A as `Black=GND, Red=5V, Yellow=G13, White=G15` and PORT.B as
-> `Black=GND, Red=5V, Yellow=G2, White=G1`. **[DOC]**
->
-> Under the Grove convention (connector pin 1 = yellow = SCL, pin 2 = white = SDA) the schematic
-> says the opposite: **yellow = GPIO15 = SCL, white = GPIO13 = SDA**, and PORT.B yellow = GPIO1.
-> M5Unified agrees with the schematic reading — `EX SCL = GPIO_NUM_15, EX SDA = GPIO_NUM_13`
-> **[SRC]** `M5Unified.cpp:96` — and its port-B table lists GPIO1 first under the comment
-> `p1 close to 5V`. **[SRC]** `:157-160`
->
-> **This is unresolved.** It does not affect anyone using M5Unified or UiFlow2, which drive the
-> correct pins either way. It affects only hand-wiring to bare Grove leads. Full analysis,
-> including the M5Dial cross-check (same table, same ambiguity) and what would settle it, is in
-> [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §1.
-
----
-
-## 6. Reference-designator census, and three that do not resolve
-
-A **complete** census was taken rather than a search for expected parts, so that gaps are
-themselves evidence. Full listing:
-[`artifacts/schematic/K134_DIN_Meter_v1.0-designator-census.txt`](artifacts/schematic/K134_DIN_Meter_v1.0-designator-census.txt).
-
-**84 designators carry a `CO` component-outline marker:**
-C1–C8, C10, C15–C19, C21, C24–C33 · D1–D13 · FPC1 · J1–J5 · L1, L4 · LS1 · M1 · Q1, Q3–Q6 ·
-R1–R19, R23–R25 · S4 · U1–U7 · Y2.
-
-**Three designators appear as visible text with no `CO` and no `PI` marker anywhere in the
-document** (searched in both single and double-struck glyph forms; zero hits):
-
-| Text | Position | Adjacent text | Assessment |
-|---|---|---|---|
-| `S1` | (246.7, 242.9) | `SW-PB` 16.8 units below — the same designator/part spacing `S4` uses | A drawn WAKE push-button whose marker layer was not emitted or not recovered. **Not** asserted as DNP |
-| `R20` | (249.3, 276.9) | `10 kΩ` below, sitting on the RTC `INT` net | Almost certainly a real 10 kΩ pull-up on `INT` |
-| `Y1` | (163.8, 495.0) | immediately right of `SS8050` on the same baseline, under `COQ5`/`Q5` | **Probably not a designator.** `Y1` is the SOT-23 marking code for an SS8050 NPN; this reads as M5Stack annotating the marking |
-
-Whether these are extraction losses or genuine absences is **not established**. Roughly 20 `PI`
-markers are missing overall for the same reason, so an extraction loss is the more likely
-explanation for `S1` and `R20`. Recorded in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §2.
-
-`Q2`, `L2`, `L3`, `R21`, `R22`, `S2`, `S3`, `C9`, `C11`–`C14`, `C20`, `C22`, `C23`, `U8`+ have
-**no marker and no visible text** — they are simply unused numbers in the designator sequence.
-
----
-
-## 7. What is *not* on this board
-
-Enumerated so the absence is a positive statement rather than an oversight:
-
-- **No PSRAM** — no designator, and `ESP32-S3FN8` has none in package. **[SCH]** **[DOC]**
-- **No SD card** — no SDMMC connector designator.
-- **No USB-UART bridge** — USB is the SoC's own OTG/Serial-JTAG, on the Stamp. **[DOC]**
-- **No microphone, speaker or codec** — the only audio device is the magnetic buzzer `LS1`.
-- **No touch controller** — the LCD is display-only; the knob is the input.
-- **No accelerometer/IMU, no environmental sensor.**
-- **No RGB LED on the carrier** — the WS2812B-2020 is *inside* the Stamp module on GPIO21.
-  **[SCH]** `Sch_M5StampS3_v0.2` `U3`.
-
----
-
-## Related
-
-- [`resources-and-conflicts.md`](resources-and-conflicts.md) — what collides with what
-- [`components/m5stack/stamp-s3/README.md`](../../../components/m5stack/stamp-s3/README.md) — the module's own pinout
-- [`components/m5stack/stamp-s3a/README.md`](../../../components/m5stack/stamp-s3a/README.md) — and what changed in v1.1
-
----
-
-# 2026-09-07 — additions and corrections from schematic net tracing
-
-Appended beneath the existing tables; **nothing above is altered, reworded or reordered.** Full
-trace with coordinates: [`schematic-netlist.md`](schematic-netlist.md). Method:
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md).
-Corrections indexed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-Applies to **v1.0 and v1.1** alike: the two schematic PDFs extract to the same 873 words and the
-same 26 `NL` tokens.
-
-## ⚠ Correction — `J5` (rotary encoder) has **five** pins, not seven
-
-`python3 trace.py grep <bbox> '^PIJ5'` returns `PIJ501`…`PIJ505` and nothing further; a 300 dpi
-render confirms five pins. Any statement elsewhere that `J5` is a 7-pad connector is superseded.
-
-| Pin | Symbol name | Token | Net | GPIO |
-|---|---|---|---|---|
-| 1 | `b1` | `PIJ501` @ 445.50, 361.91 | `BTN` → `WAKE` | **GPIO42** (`G42/MTMS`, pad 25) |
-| 2 | `b2` | `PIJ502` @ 503.00, 361.91 | `GND` | — |
-| 3 | `A` | `PIJ503` @ 459.50, 389.77 | `IN_A` | **GPIO41** (`G41/MTDI`, pad 23) |
-| 4 | `COM` | `PIJ504` @ 474.50, 389.77 | `GND` | — |
-| 5 | `B` | `PIJ505` @ 488.50, 389.77 | `IN_B` | **GPIO40** (`G40/MTDO`, pad 21) |
-
-A single 5-terminal part: 3-terminal quadrature encoder with COM grounded, plus an integrated
-push switch. `R2`/`R3` 10 kΩ pull-ups to `+3.3V`; `C2`/`C3` 100 nF to `GND`.
-
-> **Resource conflict not previously recorded:** GPIO41 is `MTDI` and GPIO40 is `MTDO`. **The
-> encoder occupies two of the four JTAG pins**; an external JTAG probe and the encoder cannot be
-> used at the same time. GPIO41 is *not* a strapping pin on the ESP32-S3 (straps are 0, 3, 45,
-> 46), so the pull-up is safe — checked, not assumed.
->
-> **Input bandwidth ceiling:** 10 kΩ external ∥ ~45 kΩ internal (the driver also enables
-> `INPUT_PULLUP`) ≈ 8.2 kΩ, with 100 nF ⇒ τ ≈ 0.82 ms, corner ≈ **194 Hz**. Firmware cannot
-> exceed this.
-
-## ⚠ The Grove 5 V rail is designed to **5.38 V**, and the arithmetic is the vendor's own
-
-`U3` is an **`SY7088`** boost (value @ 586, 215.2). The sheet prints its formula at (605, 236.7):
-
-```
-Vout = 1.2V * (R1/R2 + 1)
-```
-
-with `R16` **52.3 kΩ** (@ 663–668, 179.0) over `R18` **15 kΩ** (@ 663–666, 207.7):
-
-```
-Vout = 1.2 x (52.3 / 15 + 1) = 1.2 x 4.4867 = 5.384 V
-```
-
-**This is not an extraction error and not a mistake to be corrected — it is what the sheet
-specifies.** The same idiom appears on the Cardputer ADV, whose SY7088 divider (`R4` 75 kΩ /
-`R6` 22 kΩ) gives 5.29 V. Two M5Stack boards, two deliberately-high 5 V rails.
-
-**Practical consequence:** a Grove peripheral on this port sees ≈ 5.4 V. Anything specified as
-5 V ± 5 % (4.75–5.25 V) is **outside its rated input range on this port.** USB's own upper limit
-is 5.25 V. Check before blaming the peripheral.
-
-## Buzzer drive — `C27` is a series coupling capacitor
-
-All five drive-path tokens share y = 491.37, in x order:
-`R25.1`(45) → `R25.2`(67) → `C27.1`(74) → `C27.2`(89) → `Q5.base`(121).
-
-```
-beep (G3) ── R25 470Ω ── C27 10µF ──┬── Q5 base (SS8050 NPN, low-side)
-                                    └── D7 1N4148WT (cathode up) ── GND
-LS1 (Buzzer) between +5VIN and Q5 collector, with D6 1N4148WT anti-parallel across it
-```
-
-⚠ `C27` is **in series with the base**, not local bulk decoupling. High-pass corner ≈ 34 Hz. The
-transducer therefore **cannot be driven with a DC level** — it needs a waveform. `D6`'s presence
-as a flyback catch diode confirms the load is inductive (magnetic), not piezo.
-
-## Module footprint `M1` — complete pad map
-
-Left column, pads 1–17:
-
-| Pad | Pin name | Net | | Pad | Pin name | Net |
-|---|---|---|---|---|---|---|
-| 1 | `G1` | `GI` | | 10 | `G10` | `BATADC` |
-| 2 | `G2` | `GO` | | 11 | `GND` | `GND` |
-| 3 | `G3` | **`beep`** | | 12 | `G11` | `IN_SDA` |
-| 4 | `G4` | `LCD_RS` | | 13 | `5V` | `+5VIN` |
-| 5 | `G5` | `LCD_MOSI` | | 14 | `G12` | `IN_SCL` |
-| 6 | `G6` | `LCD_SCK` | | 15 | `G13` | `SDA` |
-| 7 | `G7` | `LCD_CS` | | 16 | `G14` | `G14` |
-| 8 | `G8` | `LCD_RESET` | | 17 | `G15` | `SCL` |
-| 9 | `G9` | `LCD_BL` | | | | |
-
-Right column, pads 18–28:
-
-| Pad | Pin name | Net | | Pad | Pin name | Net |
-|---|---|---|---|---|---|---|
-| 18 | `GND` | `GND` | | 24 | `G44/Rx` | — |
-| 19 | `G39/MTCK` | `G39` | | 25 | `G42/MTMS` | **`WAKE`** |
-| 20 | `G0/Boot` | — | | 26 | `G43/Tx` | — |
-| 21 | `G40/MTDO` | **`IN_B`** | | 27 | `G46` | `HOLD` |
-| 22 | `EN` | — | | 28 | `3V3` | `3V3` |
-| 23 | `G41/MTDI` | **`IN_A`** | | | | |
-
-**Two I²C buses, clearly separated by the sheet:** `IN_SDA`/`IN_SCL` on `G11`/`G12` (internal, to
-`U5` `RTC8563`) and `SDA`/`SCL` on `G13`/`G15` (external Grove, to `J4`).
-
-## Named parts recovered
-
-`U1` `ME3116AM6G` buck · `U2` `TP4057` charger · `U3` `SY7088` Grove boost ·
-`U4` `BL8075CB5TR33` 3.3 V regulator · `U5` `RTC8563` · `U6` load switch on the Grove rail ·
-`U7` `CN809J` reset supervisor · `Q3`/`Q6` `AP40P05` P-FET · `Q4` `LN2324DT2AG` ·
-`Q5` `SS8050` · `D1`/`D9`/`D11` `B5819W SL` · `D2`–`D5`,`D10` `B5819WT` · `D8` `SS34` ·
-`D12` `SD36` · `Y2` 32.768 kHz ±20 ppm 12.5 pF with `C28`/`C29` 6.0 pF · `FPC1` `FPC-0.5-8P` ·
-`J1` `Header 2` `6V~36V` · `J3`/`J4` `HY-2.0_IIC`.
-
-> `Y1` next to `Q5` is the **SOT-23 top mark of the SS8050**, not a crystal — this confirms the
-> existing note in § 6 above.
diff --git a/devices/m5stack/dinmeter/product-history-and-family.md b/devices/m5stack/dinmeter/product-history-and-family.md
deleted file mode 100644
index 3ebb32d..0000000
--- a/devices/m5stack/dinmeter/product-history-and-family.md
+++ /dev/null
@@ -1,115 +0,0 @@
-# DinMeter — product history, family and culture
-
-Dated timeline from primary evidence. Where a date is a *proxy* (a repository creation date, a
-shop `published_at`) it says so rather than presenting it as an announcement date.
-
----
-
-## 1. Timeline
-
-| Date | Event | Evidence | Kind |
-|---|---|---|---|
-| 2023-02-10 | **Stamp-S3 (`S007`) listed** on shop.m5stack.com | shop `.js` `published_at` | proxy for launch |
-| 2024-02-21 | `m5stack/M5DinMeter` repository created — the earliest DinMeter artefact anywhere | GitHub API `created_at` | firm |
-| 2024-03-01 | `m5stack/M5DinMeter-UserDemo` repository created | GitHub API | firm |
-| 2024-03-04 | UserDemo release **`V0.1`** — the factory firmware | GitHub release | firm |
-| 2024-03-07 | `M5DinMeter` release **`1.0.0`**; all six examples dated the same day | GitHub release + file headers | firm |
-| **2024-03-08** | **DinMeter (`K134`) listed on the shop** at USD 24.50 | shop `.js` `published_at` | proxy for launch |
-| 2024-04-14/15 | `shi78ge/DinMeter-chan` — the first third-party project, ~5 weeks after launch | GitHub | firm |
-| 2025-04-26 | `kaz-mac/M5Authenticator` with a dedicated `DinMeterUI.h` | GitHub | firm |
-| **2025-09-11** | **Stamp-S3A (`S007-…-V033`) listed** | shop `.js` | proxy for launch |
-| 2025-09-26 | `aoiastro/susuFW` last push | GitHub | firm |
-| 2025-12-10 | `tarmn3/m5dinmeter-ble-volume-knob` | GitHub | firm |
-| **2026-01-30** | **DinMeter v1.1 (`K134-V11`) announced.** Shop `created_at 10:02:16+08:00`, `published_at 12:30:47+08:00`; official r/M5Stack weekly post the same day | shop `.js` + Reddit | firm, two sources |
-| 2026-06-27 | `TuF3i/DinMeterDock` | GitHub | firm |
-| 2026-08-03 | Last push to `m5stack/M5DinMeter` — still `version=1.0.0`, no new release | GitHub | firm |
-| 2026-08-08 | `Shark17e/M5DinMeter-KilnController` | GitHub | firm |
-| 2026-09-03 | `espressif/esp-board-manager` DinMeter board definition at HEAD `2beb9b22…` | GitHub | firm |
-| **2026-09-04** | Observed: **`K134` and `S007` both marked `[EOL]` and out of stock**; `K134-V11` and `S007-V033` in stock | shop `.js` | firm |
-
-### What the timeline shows
-
-**The v1.1 is a module-lifecycle event, not a product refresh.** The Stamp-S3A appeared
-2025-09-11; the DinMeter v1.1 followed 4½ months later; and the Stamp-S3 and DinMeter K134 went
-`[EOL]` together. M5Stack re-released the carrier to consume the new module, at the same price,
-with the same PCB documentation. That reading is consistent with every artefact: no new
-schematic, no new STL, no new footprint, no new library release, no new M5Unified board enum.
-
-**The Arduino library has not been touched functionally since launch.** Release `1.0.0`,
-2024-03-07; HEAD in 2026 is still `1.0.0`. Whatever maintenance happens, happens in M5Unified.
-
-## 2. Family
-
-The DinMeter sits in a tight M5Stack cluster of **Stamp-S3 carriers with a knob and a small
-LCD**, and they share a single code path.
-
-| Product | SKU | Shape | Display | Touch | Input voltage | Distinguishing feature |
-|---|---|---|---|---|---|---|
-| **DinMeter** | K134 / K134-V11 | rectangular, panel-mount | 1.14 in 135 × 240 | no | **6–36 V** | **1/32 DIN cutout** |
-| M5Dial | K130 / K130-V11 | round puck | 1.28 in 240 × 240 round | **yes** | 5 V | round + touch |
-| M5Capsule | — | capsule | — | — | 5 V | shares the same M5Unified switch cases |
-| M5AirQ | — | box | — | — | 5 V | air-quality sensors |
-| VA Meter | — | — | — | — | — | voltage/current instrument, Stamp-S3 |
-| StamPLC | — | DIN-**rail** | — | — | — | relays, CAN, RS485 — different category |
-
-**The shared code path is literal.** M5Unified handles `board_M5Dial`, `board_M5DinMeter` and
-`board_M5Capsule` in the *same switch cases* for buttons (`M5Unified.cpp:3502`), buzzer
-(`:2921`), pin setup (`:2400`) and power hold (`:282`), and gives Dial and DinMeter identical
-I²C (`:96`) and Port-B (`:159`) rows.
-
-**And the lineage is visible in the source.** `M5DinMeter.h` opens with `#define M5DIAL_H` and
-defines `DIAL_ENCODER_PIN_A` / `DIAL_ENCODER_PIN_B`. The library was copied from the M5Dial's and
-the names were never changed. That is not a criticism — it is the clearest possible statement
-that the two are the same device in different shells.
-
-## 3. Positioning and intended audience
-
-M5Stack's own applications list, identical in spirit on both pages: smart-home monitoring and
-control, access control, industrial control, maker/DIY.
-
-The v1.1 description is more explicit about the thesis than the v1.0's was:
-
-> "…adopts the 1/32 DIN standard digital meter cutout size, allowing direct installation into
-> reserved mounting openings of mainstream equipment such as **industrial control cabinets and
-> PLC control boxes, without the need for custom brackets or panel modifications**. This
-> significantly reduces integration cost and assembly time."
-
-That is a **retrofit** pitch aimed at people with existing panels — a narrower and more
-industrial audience than most M5Stack products, and it explains the community profile in §4.
-
-## 4. Culture — there isn't much of one, and that is informative
-
-A broad sweep on 2026-09-04 found **13 third-party GitHub repositories** genuinely targeting the
-device, **one** Reddit post in the entire index (M5Stack's own launch announcement, with one
-comment), **no** ESPHome/Tasmota/Meshtastic support, and a vendor forum that could not be
-enumerated (HTTP 401).
-
-The projects that do exist are revealing: a kiln controller, a power-tool battery analyser, a
-heater controller, a TOTP authenticator, a BLE volume knob, a desktop dock. **Nine of thirteen
-are one-person, single-purpose instruments.** That is a product being used precisely as
-intended, by people who had a panel and a problem — not a platform with a scene around it.
-
-The one genuine ecosystem contribution is `bmorcelli/Launcher` (★2054), which carries the
-DinMeter as a first-class board target in its release CI.
-
-Full catalogue and evidence types: [`projects-and-community.md`](projects-and-community.md).
-
-## 5. Naming traps this product creates
-
-Worth recording, because each cost search time:
-
-| Trap | Detail |
-|---|---|
-| `docs.m5stack.com/en/core/**DinMeter**` | **404.** The page id is `M5DinMeter`; only the *v1.1* page uses `DinMeter_v1.1` |
-| Shop slug | `m5stack-din-meter-**w**-m5stamps3`, not `-with-`. The v1.1 uses `-with-` |
-| "DIN" | Means the **panel cutout** (DIN 43700, 45 × 22.5 mm), **not** DIN rail |
-| `din_meter` as a search term | Collides with `whatnick/din_meter_atm90e26` (an unrelated ATM90E26 energy meter) and with EV-charging **DIN 70121** protocol code |
-| "DIN meter" on Reddit | Overwhelmingly **ski-binding release settings** |
-| Stamp-S3A schematic filename | `Sch_StampS3_v0.3.3.pdf` — no "A" in it |
-| Stamp docs path | `/en/core/StampS3`, **not** `/en/stamp/…` |
-
-## Related
-
-[`market-and-pricing.md`](market-and-pricing.md) · [`projects-and-community.md`](projects-and-community.md) ·
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) ·
-[`../dinmeter-v1.1/stamp-s3-to-s3a-delta.md`](../dinmeter-v1.1/stamp-s3-to-s3a-delta.md)
diff --git a/devices/m5stack/dinmeter/projects-and-community.md b/devices/m5stack/dinmeter/projects-and-community.md
deleted file mode 100644
index 6d3d85e..0000000
--- a/devices/m5stack/dinmeter/projects-and-community.md
+++ /dev/null
@@ -1,216 +0,0 @@
-# DinMeter — projects, community and ecosystem
-
-**Retrieved 2026-09-04.** Search depth, queries and negative results are in
-[`research-log.md`](research-log.md). Applies to K134 and K134-V11 — no project found
-distinguishes between them.
-
-Every item is labelled by evidence type: **demonstrable project** (code exists and builds are
-published) · **reproduced documentation** (restates the vendor) · **firsthand report** ·
-**hearsay** · **marketing**.
-
----
-
-## 1. The headline: this device has almost no public community
-
-That is a finding, not a gap in the search. Stated precisely, with the sample:
-
-| Search | Result |
-|---|---|
-| GitHub repository search, `DinMeter in:name,description,readme` | **19 repositories**, of which **13** actually target the device (the rest are Launcher forks that inherit the board list, or false positives on "DIN") |
-| GitHub code search, `M5DinMeter extension:h` | 9 files across 6 repositories |
-| `old.reddit.com/search.json`, three query forms, 150 results inspected | **exactly one** relevant post |
-| `community.m5stack.com` search | API returns HTTP 401 (login required); HTML search page returns 200 but is a JS shell — **no thread could be enumerated** |
-| ESPHome | **zero** — `repo:esphome/esphome dinmeter` → 0 results |
-| Tasmota | **zero** — `repo:arendst/Tasmota dinmeter` → 0 results |
-| Meshtastic | **zero** — `repo:meshtastic/firmware dinmeter` and `din_meter` → 0 results each |
-
-For comparison, the same repository holds a Waveshare knob device with an
-[ESPHome confirmation document](../../waveshare/esp32-s3-knob-touch-lcd-1.8/esphome-and-clone-confirmation.md)
-because that ecosystem exists. **The DinMeter's does not.** If you need Home Assistant
-integration you will be writing it yourself, or using M5Stack's own UiFlow2 → Home Assistant
-path.
-
-**Prevalence caveat.** "Almost no community" is a statement about *public, indexed* activity on
-GitHub and Reddit on 2026-09-04. M5Stack's own forum could not be enumerated (see above), and
-Chinese-language platforms (Bilibili, CSDN, Taobao Q&A) were not searched. Do not read this as
-"nobody uses it".
-
----
-
-## 2. Firmware platforms that support it
-
-### Bruce / M5Launcher — `bmorcelli/Launcher` ★2054 · MIT · **demonstrable project**
-
-The most significant third-party support by a wide margin, and the only one with CI-built
-binaries.
-
-| Field | Value |
-|---|---|
-| Repository | <https://github.com/bmorcelli/Launcher> |
-| Created / last push | 2024-02-10 / **2026-09-04** (actively maintained) |
-| Board target | `boards/m5stack-dinmeter/platformio.ini` |
-| CI | `.github/workflows/main.yml` builds `{ env: "m5stack-dinmeter" }` on every release |
-| Distributed as | `Launcher-m5stack-dinmeter.bin`, MD5 `bccbefef5284357a2a7c3c7cc196fd98`, mapped in `support_files/m5burner_post.py` — i.e. **shipped through M5Burner** |
-| Status in README | listed twice, once as `[x] Port to M5-DinMeter` and once as `[ ] (Beta) M5-DinMeter port` — **the README contradicts itself**; the CI matrix and the MD5 map both say it ships |
-
-Its board file is also a genuinely useful **independent corroboration** of the pin map, from a
-party with no reason to copy M5Stack's table wrongly. Retained at
-[`artifacts/source-snapshots/`](artifacts/source-snapshots/) — key lines:
-
-```ini
-board = esp32s3
-board_upload.flash_size = 8MB
-build_unflags = -DBOARD_HAS_PSRAM          ; ← confirms: no PSRAM
--DARDUINO_USB_MODE=1  -DARDUINO_USB_CDC_ON_BOOT=1
--D HAS_ENCODER=1   -DROTATION=3
--DTFT_WIDTH=135 -DTFT_HEIGHT=240 -D TFT_IPS=1
--DTFT_CS=7 -DTFT_DC=4 -DTFT_RST=8 -DTFT_MOSI=5 -DTFT_SCLK=6 -DTFT_MISO=-1 -DTFT_BL=9
--D TFT_COL_OFS1=52  -D TFT_ROW_OFS1=40     ; ← the GRAM gap, third independent source
--D TFT_COL_OFS2=53  -D TFT_ROW_OFS2=40
--DSDCARD_CS=13 -DSDCARD_SCK=15 -DSDCARD_MISO=2 -DSDCARD_MOSI=1
-; No PMIC on DinMeter: battery is a plain ADC divider on GPIO10 (ratio 2.0,
-; matching M5Unified's board table)
--DANALOG_BAT_PIN=10
-lib_deps = mathertel/RotaryEncoder @1.5.3
-```
-
-Two things worth extracting:
-
-1. **It bit-bangs an SD card across both Grove ports.** `SDCARD_CS=13`, `SCK=15` (PORT.A) and
-   `MISO=2`, `MOSI=1` (PORT.B). That is a real, shipped demonstration that the four Grove signals
-   can be used as a software SPI bus — see
-   [`features/porta-portb-expansion.md`](features/porta-portb-expansion.md).
-2. **It confirms the battery divider ratio is 2.0**, matching the schematic's `R7`/`R8` 1 MΩ +
-   1 MΩ pair. Independent of M5Stack.
-
-A separate note in `boards/lilygo-t-lora-pager/interface.cpp` says that board's quadrature pins
-are *"swapped on purpose … opposite to lilygo-t-embed-cc1101/m5stack-dinmeter"* — so the
-DinMeter's A/B ordering is treated as the reference convention in that codebase.
-
-**Forks that inherit DinMeter support** (lineage preserved, not separately verified):
-`notyetaperson/Evilware`, `darkLabz001/Dark-Div-Launcher`,
-`TeslaDeathStar/ESP32-Launcher-ES3C28P`, `ry-ops/tab5-launcher`, `JunFactorya04/M-5Laucher{,2}`.
-These are copies of the board list, not independent ports.
-
-### `viniciusbo/m5-palnagotchi` ★81 · MIT · **demonstrable project**
-
-A Pwnagotchi companion. Created 2024-02-14, last push 2026-01-28. `palnagotchi/ui.h` references
-`M5DinMeter`. Fork `pfefferle/palnagotchi` ★1 (2026-03) carries the same. The second-most-starred
-project touching the device.
-
-### UiFlow2 / MicroPython — `m5stack/uiflow-micropython` · **vendor**
-
-DinMeter appears in both `.gitlab-ci.yml` and `.github/workflows/build-firmware.yml`. This is
-the vendor's own MicroPython firmware and the backing for the UiFlow2 tutorial at
-`docs.m5stack.com/en/uiflow2/m5dinmeter/program`.
-
-### `mattytrentini/chipboard` · **demonstrable project (unverified)**
-
-`boards/m5stack_din_meter.yaml` — a board definition for generic MicroPython. Not built or
-evaluated here. Vanilla `micropython/micropython` has **no** DinMeter port.
-
-### `espressif/esp-board-manager` · **vendor-adjacent, primary**
-
-Not a "project" so much as first-party ESP-IDF board support from Espressif:
-`m5stack_boards/m5stack_dinmeter/{board_info,board_devices,board_peripherals}.yaml`, HEAD
-`2beb9b22b0892b343bd555a1ebc9929a7edce8fc` (2026-09-03). Its comments are the single best
-technical writing about this board that exists anywhere, M5Stack included — it documents the
-GRAM offset, the PCNT decoder pattern, an ESP32-S3-specific build break, and it resolves the
-GPIO3/GPIO42 ambiguity in M5Stack's own pin table by citing M5Unified. Fully quoted in
-[`development.md`](development.md) §2a.
-
----
-
-## 3. Application projects
-
-| Project | Stars | Language | Licence | Last push | What it is | Evidence type |
-|---|---:|---|---|---|---|---|
-| [`no-body-in-particular/m5din-hikoki`](https://github.com/no-body-in-particular/m5din-hikoki) | **25** | C++ | — | 2026-05-05 | HiKOKI power-tool battery analyser | demonstrable project |
-| [`Shark17e/M5DinMeter-KilnController`](https://github.com/Shark17e/M5DinMeter-KilnController) | 1 | C++ | NOASSERTION | 2026-08-08 | Ceramic-kiln controller: PID with auto-correction, temperature curves | demonstrable project |
-| [`kaz-mac/M5Authenticator`](https://github.com/kaz-mac/M5Authenticator) | 2 | C | MIT | 2025-04-26 | TOTP 2FA device; has a dedicated `src/DinMeterUI.h` | demonstrable project |
-| [`TuF3i/DinMeterDock`](https://github.com/TuF3i/DinMeterDock) | 0 | C | MIT | 2026-06-27 | Desktop dock controller (Chinese) | demonstrable project |
-| [`aoiastro/susuFW`](https://github.com/aoiastro/susuFW) | 1 | — | — | 2025-09-26 | Multi-function firmware for the DinMeter (Japanese) | demonstrable project |
-| [`shi78ge/DinMeter-chan`](https://github.com/shi78ge/DinMeter-chan) | 1 | C++ | NOASSERTION | 2024-04-15 | Character/mascot display — the earliest third-party project found, six weeks after launch | demonstrable project |
-| [`tarmn3/m5dinmeter-ble-volume-knob`](https://github.com/tarmn3/m5dinmeter-ble-volume-knob) | 0 | C++ | none | 2025-12-10 | BLE HID volume knob | demonstrable project |
-| [`Yuichiroh-Kobayashi/DinMeter_ScrambleMDtest`](https://github.com/Yuichiroh-Kobayashi/DinMeter_ScrambleMDtest) | 0 | — | MIT | 2026-06-03 | test sketch | demonstrable project |
-| [`todateman/Chibi-T_Furoshiki_Heater`](https://github.com/todateman/Chibi-T_Furoshiki_Heater) | 1 | C++ | NOASSERTION | 2026-08-15 | Heater controller | demonstrable project |
-| [`AH2005NA/m5stick-shark`](https://github.com/AH2005NA/m5stick-shark) | — | C++ | — | — | `Defines.h` references M5DinMeter | demonstrable project |
-| [`jd3096-mpy/micropython-Coin-Operated-Beverage-Machine`](https://github.com/jd3096-mpy/micropython-Coin-Operated-Beverage-Machine) | 0 | Python | MIT | 2025-07-10 | MicroPython vending machine | demonstrable project |
-| [`3110/m5stack-platformio-boilerplate-code`](https://github.com/3110/m5stack-platformio-boilerplate-code) | — | C++ | — | — | `include/main.hpp` includes a DinMeter branch | demonstrable project |
-
-**Observations across the set.** Nine of the twelve are one-person single-purpose instruments —
-a kiln, a battery tester, a heater, a volume knob, an authenticator. That is the DinMeter being
-used for exactly what it looks like it is for. There is no framework, no library ecosystem, no
-"awesome-dinmeter" list, and no project has more than 25 stars.
-
-**Nationality skew.** Of the identifiable authors, the projects are Japanese, Italian, Chinese
-and Brazilian. This is a product with a distributed, low-density user base rather than a
-concentrated scene.
-
----
-
-## 4. Reddit
-
-Searched via `old.reddit.com/search.json` with UA `WhatsApp/2.23.20.0` (which returns HTTP 200
-where `www.reddit.com` returns 403 — see
-[`../../../ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md)). Three
-query forms, ~150 results inspected, plus a subreddit-restricted pass.
-
-**One relevant result in the entire index:**
-
-| Date | Sub | Score | Comments | Post | Type |
-|---|---|---:|---:|---|---|
-| 2026-01-30 | r/M5Stack | 22–23 | 1 | ["Check out what's new this week!"](https://old.reddit.com/r/M5Stack/comments/1qr0ju2/check_out_whats_new_this_week/) — the official M5Stack weekly-products post announcing DinMeter v1.1 alongside the LLM-8850 Kit | **marketing** (vendor-posted) |
-
-Its body text is the same paragraph as the v1.1 product page. It has **one** comment. This is
-the *entire* Reddit footprint of the product line and it corroborates the launch date
-(2026-01-30), which independently matches the shop listing's `created_at`.
-
-The other search hits matching "DIN meter" were about **ski-binding release settings**
-(r/Skigear) — a genuine homonym trap worth recording so the next agent does not re-chase it.
-
----
-
-## 5. M5Stack community forum — could not be enumerated
-
-| Attempt | Result |
-|---|---|
-| `https://community.m5stack.com/api/search?term=dinmeter&in=titlesposts` | **HTTP 401** — `{"status":{"code":"not-authorised","message":"A valid login session was not found."}}` |
-| `https://community.m5stack.com/search?term=dinmeter&in=titlesposts` (browser UA) | HTTP 200, 16 986 bytes — a NodeBB **JS shell**; no results in the served HTML |
-
-The forum runs NodeBB with its search API behind authentication. **No forum thread could be
-cited.** This is a blocked source, not an empty one, and it is the largest single gap in this
-document. What would fix it: an authenticated session, or Google's `site:community.m5stack.com`
-index.
-
----
-
-## 6. Other sources searched with nothing found
-
-| Source | Query | Result |
-|---|---|---|
-| Hackaday / Hackaday.io | project search | no DinMeter project located |
-| ESPHome | `repo:esphome/esphome dinmeter` | 0 |
-| Tasmota | `repo:arendst/Tasmota dinmeter` | 0 |
-| Meshtastic | `repo:meshtastic/firmware {dinmeter,din_meter}` | 0 each |
-| `pr3y/Bruce` (upstream Bruce) | `repo:pr3y/Bruce dinmeter` | 0 — **support is in `bmorcelli/Launcher`, not in Bruce upstream**. Easy to get wrong |
-| AliExpress clones | product search | none found (negative result, not proof of absence) |
-| YouTube / video | not systematically searched | **declared exclusion** |
-| Bilibili / CSDN / Chinese platforms | not searched | **declared exclusion** |
-
----
-
-## 7. What a new user should actually do
-
-1. Start from the **vendor examples** in `m5stack/M5DinMeter` — six of them, one per feature.
-   See [`examples/best.md`](examples/best.md).
-2. For ESP-IDF, read **Espressif's board definition** before writing anything; it will save you
-   the GRAM offset and the PCNT build break.
-3. If you want a ready-made multi-tool, flash **Launcher** via M5Burner.
-4. Do **not** expect ESPHome, Tasmota or Meshtastic. They do not support it.
-
-## Related
-
-[`community.md`](community.md) · [`examples/best.md`](examples/best.md) ·
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) ·
-[`research-log.md`](research-log.md)
diff --git a/devices/m5stack/dinmeter/research-log.md b/devices/m5stack/dinmeter/research-log.md
deleted file mode 100644
index 04fc8e6..0000000
--- a/devices/m5stack/dinmeter/research-log.md
+++ /dev/null
@@ -1,190 +0,0 @@
-# DinMeter — research log
-
-**Snapshot date: 2026-09-04.** Single research pass, no hardware in hand. Covers K134 and
-K134-V11 together. Every query is recorded, including the ones that returned nothing — those are
-the ones that stop the next agent repeating the work.
-
----
-
-## 1. Source classes searched
-
-| Class | Searched? | Depth |
-|---|---|---|
-| Manufacturer product pages / docs | ✔ | Both product pages, both Stamp pages, 9 Arduino tutorial pages, 1 UiFlow2 page, the full 5 703-URL sitemap |
-| Manufacturer schematics / CAD / downloads | ✔ | 3 schematics, 2 dimension drawings, 4 STL/STEP/footprint files, 7 datasheet mirrors |
-| Manufacturer repositories | ✔ | `M5DinMeter`, `M5DinMeter-UserDemo`, `M5Unified`, `M5GFX`, `M5_Hardware`, `uiflow-micropython` |
-| Component-manufacturer pages / datasheets | ✔ partial | 4 obtained; **4 not found** (ME3116AM6G, SY7088, BL8075, SGM2578) |
-| Standards / certification databases | ✘ | **Declared exclusion.** No FCC/CE search was run |
-| Framework / SDK / registry docs | ✔ | M5Unified, M5GFX, `esp-board-manager`, PlatformIO registry (via project files), MicroPython |
-| Authorized distributors / mirrors | ✔ partial | M5Stack's own store only; no Mouser/DigiKey/Aliexpress price sweep |
-| Community repositories | ✔ | GitHub repo + code search, several query forms |
-| Forums | ⚠ **blocked** | `community.m5stack.com` returns HTTP 401 on its API and a JS shell on HTML |
-| Reddit | ✔ | 4 query forms, ~200 results inspected |
-| Blogs / reviews / videos | ✘ | **Declared exclusion** — not systematically searched |
-| Chinese-language platforms | ✘ | **Declared exclusion** — Bilibili, CSDN, Taobao not searched |
-| Web archives | ✔ minimal | No captures needed; nothing was dead |
-
----
-
-## 2. Vendor documentation — URL discovery
-
-The `/en/products` index is a JavaScript shell and contains **no product links** in its served
-HTML (565 615 B fetched, 8 path matches, all generic). **The sitemap is the only way to
-enumerate.**
-
-| Query | Result |
-|---|---|
-| `GET https://docs.m5stack.com/en/core/DinMeter` | **HTTP 404** ← negative control; the obvious guess is wrong |
-| `GET https://docs.m5stack.com/en/core/M5DinMeter` | HTTP 200, 139 501 B ← the v1.0 page |
-| `GET https://docs.m5stack.com/en/core/DinMeter_v1.1` | HTTP 200, 142 090 B |
-| `GET https://docs.m5stack.com/en/stamp/StampS3` | **HTTP 404** ← negative control; Stamp pages live under `/en/core/`, not `/en/stamp/` |
-| `GET https://docs.m5stack.com/en/stamp/{Stamp-S3A,M5StampS3,stamps3,StampS3A}` | **HTTP 404** ×4 |
-| `GET https://docs.m5stack.com/en/core/StampS3` | HTTP 200 |
-| `GET https://docs.m5stack.com/sitemap.xml` | HTTP 200, 499 000 B, **5 703 URLs** |
-| `GET https://docs.m5stack.com/en/sitemap.xml` | **HTTP 404** |
-| `GET https://docs.m5stack.com/sitemap_index.xml` | **HTTP 404** |
-
-Sitemap filtered for `Stamp` → 73 URLs, for `Din` → **6** (only `M5DinMeter` and `DinMeter_v1.1`
-under `/en/core/`, plus 9 `/en/arduino/m5dinmeter/*` and 1 `/en/uiflow2/m5dinmeter/program`).
-
-All 20 subsequently fetched doc pages returned HTTP 200. No fallback User-Agent was needed for
-any `m5stack.com` host — the Chrome-131 UA was used throughout as the standing convention.
-
-## 3. Artifact acquisition
-
-19 files fetched, **all HTTP 200**, all validated by magic bytes. No failed downloads, no HTML
-served under a `.pdf` extension. Full hash/size table:
-[`acquisition/manifest.json`](acquisition/manifest.json).
-
-**Two byte-identity discoveries made during acquisition** (both found by hashing, not by
-reading):
-
-1. `.../500/DIN_Meter_v1.0.pdf` and `.../1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf`
-   → same SHA-256 `03ec3353…`. Different hosts paths, different filenames, same bytes.
-2. `Stamp-S3.stl` and `Stamp-S3A.stl`, and `DinMeter.stl` and `DinMeter_v1.1.stl` → identical
-   within each pair.
-
-And one **deduplication against the existing repository**: the ESP32-S3 datasheet fetched from
-`m5stack-doc…/472/esp32-s3_datasheet_en.pdf` has SHA-256 `b6db403d…`, matching
-`components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf` already
-held. Not re-added; the extra URL was recorded instead.
-
-## 4. Schematic analysis
-
-No `pdftotext`/poppler, no `pypdf`, no `pymupdf` on this host. `pymupdf` installed but failed to
-import (`libstdc++.so.6` missing). **`pdfminer.six 20260107` in a `uv` venv worked.**
-
-A poppler-`-bbox`-compatible XML emitter was written (`/tmp/opencode/pdf_bbox.py`) and a
-DinMeter-specific parser retained at
-[`artifacts/schematic/parse_dinmeter_sch.py`](artifacts/schematic/parse_dinmeter_sch.py).
-
-**One real trap, recorded because it produces plausible-looking wrong output:** Altium draws its
-marker layer **twice** at identical coordinates. Without glyph deduplication the two copies
-interleave, so `PIJ10101` extracts as `PPIIJJ110011` — human-legible-ish, and completely wrong.
-The first parse pass produced exactly this and was discarded. Dedupe key: rounded
-`(x0, y0, x1, y1, char)`.
-
-**Text-layer validation before transcription:** the page-frame zone letters `A`–`D` and numbers
-`1`–`4` land at the expected coordinates, and `TP4057`, `SY7088`, `BL8075CB5TR33`,
-`ME3116AM6G`, `STAMP-S3-SMD`, `RTC8563`, `32.768KHz ±20ppm 12.5pF` all render as legible strings
-in the right places. 84 of 85 marker-derived designators match visible designator text.
-
-**Completeness accounting:** 85 `CO`, 238 `PI`, 25 `NL`, 553 visible text runs. ~260 `PI` markers
-expected for 84 parts ⇒ ~20 not recovered, caused by the negative-lookbehind rule that prevents
-`GPIO0` parsing as a `PI` marker. All `M1` (31), `J3`, `J4`, `J5`, `FPC1`, `U5`, `U6` pads were
-recovered, so no published table rests on a missing marker.
-
-**Absence proven, not assumed:** searched for `COS1`, `COR20`, `COY1`, `COQ2`, `COL2`, `COL3`,
-`COR21`, `COR22`, `COS2`, `COS3`, `COU8`, `COD14`, `COJ6` in both single and double-struck glyph
-forms — **zero hits for all**. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §2.
-
-## 5. GitHub
-
-Authenticated via `gh auth token` throughout (`api.github.com` limits per identity; no
-User-Agent helps).
-
-| Query | Endpoint | Result |
-|---|---|---|
-| `DinMeter` | repo search | 5 |
-| `M5DinMeter` | repo search | 6 |
-| `din meter m5stack` | repo search | 2 |
-| `DinMeter in:name,description,readme` | repo search, 50/page | **19** ← the productive form |
-| `DinMeter in:file language:yaml` | code search | 94 (mostly false positives on unrelated YAML) |
-| `din_meter` | code search | 109 (dominated by `whatnick/din_meter_atm90e26`, an unrelated ATM90E26 energy meter) |
-| `M5DinMeter extension:h` | code search | 9 files / 6 repos |
-| `repo:esphome/esphome dinmeter` | code search | **0** |
-| `repo:arendst/Tasmota dinmeter` | code search | **0** |
-| `repo:meshtastic/firmware dinmeter` | code search | **0** |
-| `repo:meshtastic/firmware din_meter` | code search | **0** |
-| `repo:pr3y/Bruce dinmeter` | code search | **0** ← support is in `bmorcelli/Launcher`, not Bruce upstream |
-| `repo:bmorcelli/Launcher dinmeter` | code search | **6** ← the productive one |
-
-**Naming traps found:** `din_meter` collides with `whatnick/din_meter_atm90e26` (an unrelated
-KiCad energy-meter project) and with EV-charging DIN 70121 code (`din_msgDefDatatypes.c` in
-EVerest/SmartEVSE). `DinMeter` also matches ski-binding "DIN meter" discussions on Reddit.
-
-## 6. Reddit
-
-`old.reddit.com/search.json` with UA `WhatsApp/2.23.20.0` — HTTP 200 on every request, where
-`www.reddit.com` is documented in this repository as returning 403.
-
-| Query | Results returned | Relevant |
-|---|---:|---:|
-| `DinMeter` | 50 | 1 |
-| `Din Meter M5Stack` | 50 | 1 (same post) |
-| `M5Stack knob DIN` | ~25 | 0 |
-| `subreddit:M5Stack dinmeter` | 7 | 1 (same post) |
-| `subreddit:esp32 dinmeter` | **0** | 0 |
-| `din meter stamps3` | 50 | 0 |
-
-**One relevant post in the entire index** — the official 2026-01-30 weekly-products
-announcement. Recorded in [`projects-and-community.md`](projects-and-community.md) §4.
-
-## 7. M5Stack community forum — blocked
-
-| Attempt | Result |
-|---|---|
-| `https://community.m5stack.com/api/search?term=dinmeter&in=titlesposts` | **HTTP 401** — `{"status":{"code":"not-authorised",…}}` |
-| `https://community.m5stack.com/search?term=dinmeter&in=titlesposts` (Chrome-131 UA) | HTTP 200, 16 986 B — NodeBB **JS shell**, no results in served HTML |
-
-**No forum thread could be cited.** Largest single gap in this record. Would need an
-authenticated session or a search-engine index.
-
-## 8. Component datasheets — four failures
-
-| Part | Where searched | Result |
-|---|---|---|
-| ME3116AM6G | vendor pages, aggregators, general web | **not found** |
-| SY7088 | as above | **not found** |
-| BL8075(CB5TR33) | as above | **not found** |
-| SGM2578 | as above | **not found** |
-| Stamp-S3A `U4` | schematic (no part text), vendor pages | **no part number exists to search for** |
-| ST7789P3 | Sitronix, M5Stack mirrors, general web | **not found** — M5Stack removed the display datasheet link on the v1.1 page rather than replacing it |
-
-All five are recorded as `unidentified` or schematic-only component records rather than guessed.
-
-## 9. Explicit exclusions
-
-Declared so the coverage claim is honest:
-
-- **No hardware.** Nothing was flashed, measured, probed or photographed.
-- **No teardown.** No PCB photograph, no chip marking confirmed visually. Every part number
-  rests on schematic value text.
-- **No RF measurement.** The Stamp-S3A antenna claim is neither confirmed nor refuted.
-- **No FCC/CE/regulatory database search.**
-- **No video, blog or review search.**
-- **No Chinese-language platform search.**
-- **No marketplace price sweep** beyond `shop.m5stack.com`.
-- **Forum inaccessible** (§7).
-- **Pin-map JPEGs not OCR'd** — which is what would settle the Grove wire-colour conflict.
-
-## 10. Stopping criterion
-
-Two consecutive broad passes over GitHub and Reddit returned only duplicates and the same
-homonym noise (`din_meter_atm90e26`, DIN 70121, ski bindings). The remaining unresolved items
-all require either **hardware in hand** (teardown, meter, RF), **an authenticated forum
-session**, or **documents the manufacturers have not published**. Continuing the same search
-classes would not have produced new qualifying sources.
-
-This is a **reproducible broad-coverage snapshot dated 2026-09-04**, not a claim that no other
-resource exists.
diff --git a/devices/m5stack/dinmeter/resources-and-conflicts.md b/devices/m5stack/dinmeter/resources-and-conflicts.md
deleted file mode 100644
index 9e61f99..0000000
--- a/devices/m5stack/dinmeter/resources-and-conflicts.md
+++ /dev/null
@@ -1,151 +0,0 @@
-# DinMeter — resources and conflicts
-
-Applies to K134 and K134-V11 (identical GPIO map). Evidence: schematic + `M5Unified` +
-`espressif/esp-board-manager` + `bmorcelli/Launcher`, all cross-checked. `not-tested` on hardware.
-
----
-
-## 1. Complete GPIO budget
-
-The Stamp-S3 breaks out **23** IOs. Here is every one of them.
-
-| GPIO | Owner | Free? | Notes |
-|---:|---|---|---|
-| 0 | Stamp `G0` button / boot strap | ⚠ shared | Usable as `M5.BtnB` at runtime; **must be high at reset** |
-| 1 | **PORT.B** signal | ✔ user | ADC1, LEDC-capable |
-| 2 | **PORT.B** signal | ✔ user | ADC1, LEDC-capable |
-| 3 | Buzzer `LS1` | ✘ | via `Q5` SS8050 |
-| 4 | Display D/C | ✘ | |
-| 5 | Display MOSI | ✘ | |
-| 6 | Display SCLK | ✘ | |
-| 7 | Display CS | ✘ | |
-| 8 | Display RESET | ✘ | |
-| 9 | Display backlight enable | ✘ | drives `U6` AW35122FDR |
-| 10 | Battery ADC (`R7`/`R8` 1 MΩ + 1 MΩ, **ratio 2.0**) | ✘ | ADC1 |
-| 11 | **Internal** I²C SDA (RTC) | ✘ | |
-| 12 | **Internal** I²C SCL (RTC) | ✘ | |
-| 13 | **PORT.A** — SDA per M5Unified | ✔ user | 10 kΩ pull-up fitted |
-| 14 | Power-latch OR network (`D7`, `R9`) | ⚠ **not free** | Vendor PinMap implies free; hardware is fitted. **Do not repurpose** |
-| 15 | **PORT.A** — SCL per M5Unified | ✔ user | 10 kΩ pull-up fitted |
-| 39 | Power-latch OR network (`R10`) | ⚠ **not free** | Same caution as GPIO14 |
-| 40 | Encoder B | ✘ | `MTDO` |
-| 41 | Encoder A | ✘ | `MTDI` |
-| 42 | Encoder push-button / WAKE | ✘ | `MTMS`, also a wake source |
-| 43 | **UART0 TX** | ✔ **free** | **No net label on the schematic** — a blank cell, not a drawn no-connect. Probably free; verify with a meter |
-| 44 | **UART0 RX** | ✔ **free** | Same caveat |
-| 46 | **Power hold** | ✘ | Strapping pin. Never fit an external pull-up |
-
-**Free for the user: 6 pins** — GPIO1, 2, 13, 15 (the two Grove ports) and GPIO43, 44 (UART0,
-unverified). Plus GPIO0 if you can share it with the boot strap.
-
-### Internal to the Stamp module — invisible to the carrier
-
-| GPIO | Function | Notes |
-|---:|---|---|
-| 19, 20 | USB D−/D+ | native USB-C |
-| 21 | WS2812B-2020 RGB LED data | see [`features/rgb-led.md`](features/rgb-led.md) |
-| 33–38 | Rear LCD FPC (`DISP_RST/RS/MOSI/SCK/CS/BL`) | GPIO38 is the LED power enable **on Stamp-S3A** |
-
-These are the pins an ESP32-S3**R8** spends on octal PSRAM. The `FN8` has none, which is why
-M5Stack could route them to the module's rear header — and why there is no PSRAM.
-
----
-
-## 2. Peripheral budget
-
-| Peripheral | Total on ESP32-S3 | Used by the board | Free |
-|---|---:|---:|---|
-| SPI host | 2 usable (`SPI2`, `SPI3`) | **1** (`SPI2_HOST`, display) | 1 |
-| I²C | 2 | **1** (internal, RTC) + 1 if you use PORT.A | 0–1 |
-| LEDC channel | 8 | **2** (backlight ch 0, buzzer ch 1) | 6 |
-| LEDC timer | 4 | **2** (timer 0 backlight, timer 1 buzzer) | 2 |
-| PCNT unit | 4 | **1** if you use the IDF encoder path | 3 |
-| RMT channel | 8 | 1 if you drive the RGB LED via RMT | 7 |
-| ADC1 channel | 10 | **1** (GPIO10 battery) + up to 2 on PORT.B | — |
-| GPIO interrupt | many | 2 if you use the Arduino encoder path | — |
-| DMA | — | display, optional | — |
-
----
-
-## 3. Real conflicts
-
-Only three exist. Everything else composes freely.
-
-### 3.1 LEDC timer sharing — backlight vs buzzer
-
-Both want LEDC. Espressif's board definition puts them on **different timers by design**
-(backlight ch 0 / timer 0; buzzer ch 1 / timer 1) because **channels on the same timer share a
-frequency**. If you write your own LEDC setup and put them together, changing the buzzer's pitch
-changes the backlight's PWM frequency — usually visible as a brightness step or flicker.
-
-**Mitigation:** keep them on separate timers. This is the only conflict that will actually
-surprise you.
-
-### 3.2 JTAG pins are all consumed
-
-GPIO39 (`MTCK`), 40 (`MTDO`), 41 (`MTDI`), 42 (`MTMS`) are the ESP32-S3's pin-based JTAG. All
-four have hardware on them (encoder ×2, button, latch network). **Pin-based JTAG debugging is
-not possible while the knob works.**
-
-**Mitigation:** use **USB-Serial-JTAG**, which is on GPIO19/20 inside the module and unaffected.
-
-### 3.3 GPIO14 and GPIO39 are advertised free but are not
-
-The vendor PinMap lists the Stamp's 23 IOs and does not mark GPIO14 or GPIO39 as used. The
-schematic shows both carrying a 10 kΩ + 1N4148WT network tied into the power-latch region.
-**Repurposing them risks defeating the wake/latch circuit.** The circuit was not fully traced —
-see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §8.
-
----
-
-## 4. Combinations, evaluated
-
-Not one feature at a time — the combinations people actually build.
-
-| Combination | Pin conflict? | Other constraint | Verdict |
-|---|---|---|---|
-| Display + encoder + button | none | — | **fine** |
-| Display + encoder + buzzer | none | LEDC timers must differ (§3.1) | **fine, with care** |
-| Display + RTC + Wi-Fi | none | RAM: framebuffer 64.8 KB + Wi-Fi stack, **no PSRAM** | **fine with band buffers**; a full-screen sprite + TLS is tight |
-| Display + Wi-Fi + TLS + BLE | none | **RAM.** ~65 KB fb + ~40 KB NimBLE + 20–50 KB per TLS session on ~512 KB SRAM | **tight** — profile it |
-| Both Grove ports as SD-card SPI | consumes all 4 free Grove pins | — | **demonstrated** by Bruce/Launcher (`SDCARD_CS=13, SCK=15, MISO=2, MOSI=1`) |
-| Grove I²C + Grove GPIO simultaneously | none | 220 mA per port from a shared boost | **fine** |
-| Everything at once + battery | none | 25.5–33.5 mA standby on a 250 mA·h cell ≈ 8–10 h | **works, but plan the duty cycle** |
-| Pin-based JTAG + encoder | **yes, hard** | — | **impossible.** Use USB-Serial-JTAG |
-
----
-
-## 5. Power budget
-
-| Rail | Source | Limit | Consumers |
-|---|---|---|---|
-| `+5VIN` | `U1` ME3116AM6G buck (6–36 V) **or** USB | not published | Stamp pad 13, charger, supervisor, buzzer |
-| `+5VOUT` | `U3` SY7088 boost from battery | **220 mA per Grove port** (vendor) | PORT.A + PORT.B pin 3 |
-| `+3.3V` | `U4` BL8075CB5TR33 LDO from `VBAT_IN` | not published | RTC, pull-ups, LCD FPC |
-| Module `VDD_3V3` | inside the Stamp: MUN3CAD01-SC (**1 A**) on S3, unidentified buck (**0.6 A**) on S3A | see left | ESP32-S3, RGB LED, module FPC |
-
-⚠ **The Stamp-S3A's internal regulator is rated 0.6 A where the Stamp-S3's was 1 A.** Not
-mentioned in either vendor spec table. Unlikely to matter on a DinMeter (the carrier makes its
-own 3.3 V), but it is a reduction. See
-[`../dinmeter-v1.1/stamp-s3-to-s3a-delta.md`](../dinmeter-v1.1/stamp-s3-to-s3a-delta.md) §5.
-
-⚠ **`C24`, the buck input capacitor, is rated 35 V against a 36 V input spec** — 103 % of
-rating at the ceiling. Treat 36 V as an absolute maximum.
-
----
-
-## 6. Flash and partitions
-
-8 MB, no PSRAM. **M5Stack publishes no partition table.** Two known-working third-party layouts:
-
-| Project | Layout |
-|---|---|
-| `M5DinMeter-UserDemo` | PlatformIO `esp32-s3-devkitc-1` default (unstated in the project file) |
-| `bmorcelli/Launcher` | `support_files/custom_8Mb.csv`, `board_upload.maximum_size = 8388608`, SPIFFS threshold `0x2F0000` |
-
----
-
-## Related
-
-[`pinouts-and-buses.md`](pinouts-and-buses.md) · [`coverage.md`](coverage.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md) · [`features/`](features/README.md)
diff --git a/devices/m5stack/dinmeter/schematic-netlist.md b/devices/m5stack/dinmeter/schematic-netlist.md
deleted file mode 100644
index 617c777..0000000
--- a/devices/m5stack/dinmeter/schematic-netlist.md
+++ /dev/null
@@ -1,194 +0,0 @@
-# DinMeter — net list traced from `K134_DIN_Meter_v1.0-schematic.pdf`
-
-**Traced:** 2026-09-07 · **Method:**
-[`guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md`](../../../guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md)
-· **Tool:** poppler 26.06.0, plus 300 dpi `pdftoppm` crops.
-
-**New file.** It does not replace `pinouts-and-buses.md`. Corrections to existing claims are
-appended there and listed in
-[`scratch/schematic-tracing/corrections-requiring-review.md`](../../../scratch/schematic-tracing/corrections-requiring-review.md).
-
-Applies equally to **DinMeter v1.1**: `K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58-schematic.pdf`
-extracts to the same 873 words and the same 26 `NL` tokens.
-
-## 0. Traceability
-
-1 page, `Creator: Altium Designer`, **0 embedded rasters**, 873 words, 26 `NL` tokens, full
-`CO`/`PI` coverage. **Fully traceable.**
-
----
-
-## 1. `J5` — the rotary encoder connector. **Five pins, not seven.**
-
-`python3 trace.py grep <bbox> '^PIJ5'` returns exactly five tokens, and a 300 dpi render of the
-symbol shows five pins:
-
-| Pin | Symbol name | Token @ coordinate | Net | Termination |
-|---|---|---|---|---|
-| 1 | `b1` | `PIJ501` @ 445.50, 361.91 | **`BTN`** (@ 430, 359.2) | → `WAKE` → module pad 25 → **GPIO42** |
-| 2 | `b2` | `PIJ502` @ 503.00, 361.91 | `GND` (@ 533, 362.5) | — |
-| 3 | `A` | `PIJ503` @ 459.50, 389.77 | **`IN_A`** (@ 457, 419.9) | → module pad 23 → **GPIO41**; `R2` 10 kΩ to `+3.3V`, `C2` 100 nF to `GND` |
-| 4 | `COM` | `PIJ504` @ 474.50, 389.77 | `GND` (@ 475, 416.7) | — |
-| 5 | `B` | `PIJ505` @ 488.50, 389.77 | **`IN_B`** (@ 486, 419.9) | → module pad 21 → **GPIO40**; `R3` 10 kΩ to `+3.3V`, `C3` 100 nF to `GND` |
-
-The value field reads `Rotary encode` (@ 462–482, 403.8). The push switch (`b1`/`b2`) is drawn
-as a separate contact *inside the same symbol*, above the A/COM/B group — not as a second
-connector.
-
-**Topology now established:** a standard 3-terminal incremental quadrature encoder
-(A / COM / B) with its common pin **grounded**, A and B pulled up by 10 kΩ and RC-filtered by
-100 nF, plus an integrated 2-terminal momentary push switch wired between `BTN` and `GND`.
-
-The `IN_A`/`IN_B` → GPIO mapping comes from the module footprint `M1`: the net labels sit at
-x ≈ 388 on the right-hand pin column (x = 361 numbers, x ≈ 324 pin names): `IN_A` @ y 474.5 →
-pad 23 → pin name `G41/MTDI`; `IN_B` @ y 488.6 → pad 21 → `G40/MTDO`.
-
-> **Resource note, from those pin names:** the encoder occupies **`MTDI` (GPIO41)** and
-> **`MTDO` (GPIO40)**. Those are two of the ESP32-S3's four JTAG pins. Using the encoder and an
-> external JTAG probe simultaneously is impossible on this board.
-
-## 2. `LS1` — the buzzer. **AC-coupled base drive, inductive load.**
-
-| Element | Value | Tokens |
-|---|---|---|
-| `LS1` | value field `Buzzer`, 2 pads | `PILS101` @ 142.50, 448.37 · `PILS102` @ 142.50, 455.37 |
-| `D6` | `1N4148WT`, **anti-parallel across `LS1`** | `PID602` @ 99.50, 426.57 · `PID601` @ 99.50, 448.57 |
-| `Q5` | `SS8050` NPN (`Y1` beside it is the SOT-23 top mark, not a designator) | `PIQ503` collector @ 135.50, 476.77 · `PIQ501` base @ 121, 491.37 · `PIQ502` emitter @ 135.50, 505.77 → `GND` @ 553.60 |
-| `R25` | 470 Ω | `PIR2501` @ 45, 491.37 · `PIR2502` @ 67, 491.37 |
-| `C27` | **10 µF, in series** | `PIC2701` @ 74, 491.37 · `PIC2702` @ 89, 491.37 |
-| `D7` | `1N4148WT`, base clamp | `PID702` cathode @ 99.50, 502.57 · `PID701` anode @ 99.50, 523.57 → `GND` |
-| Supply | `+5VIN` | |
-
-All five drive-path pin tokens share **y = 491.37** and run left to right in x: `R25.1`(45) →
-`R25.2`(67) → `C27.1`(74) → `C27.2`(89) → `Q5.base`(121). The chain is therefore
-
-```
-beep ── R25 470Ω ── C27 10µF ──┬── Q5 base
-                               └── D7 (cathode up) ── GND
-```
-
-**Findings this establishes:**
-
-- `C27` is **in series with the base drive, not a decoupling capacitor.** The base is
-  AC-coupled; `D7` clamps the negative excursion. The high-pass corner is
-  1 / (2π · 470 Ω · 10 µF) ≈ **34 Hz**, so the whole audio band passes.
-- The **flyback diode `D6` across `LS1` means the load is inductive** — an electromagnetic
-  (magnetic) transducer, not a piezo. A piezo would need no catch diode.
-- AC coupling plus a GPIO-driven tone confirms a **passive** transducer requiring a driven
-  waveform, consistent with M5Unified modelling it as a PWM tone source.
-
-Control net: `beep` (`NLbeep` @ 29.50, 488.20) → module pad 3 → pin name `G3` → **GPIO3**.
-
-## 3. `U3` — the Grove 5 V boost. **The rail is designed to 5.38 V.**
-
-`U3` is an **`SY7088`** (value @ 586, 215.2). Its printed formula, at (605, 236.7), is
-
-```
-Vout = 1.2V * (R1/R2 + 1)
-```
-
-The divider is `R16` **52.3 kΩ** (@ 663–668, 179.0) over `R18` **15 kΩ** (@ 663–666, 207.7),
-with `FB` at `U3` pin (`LX`/`OUT`/`IN`/`EN`/`FB`/`PGND`/`GND` symbol, x ≈ 568–626).
-
-```
-Vout = 1.2 × (52.3 / 15 + 1) = 1.2 × 4.4867 = 5.384 V
-```
-
-**The arithmetic is correct and the sheet means it.** The rail labelled `+5VOUT` is a nominal
-**5.38 V**, not 5.00 V. This is a design choice, not an extraction error: the same vendor uses
-the same idiom on the Cardputer ADV, where `R4` 75 kΩ / `R6` 22 kΩ on an SY7088 gives
-1.2 × (75/22 + 1) = **5.29 V**. Two boards, two deliberately-high 5 V rails.
-
-Practical consequence: a Grove peripheral on this port sees **~5.4 V**, which is inside USB's
-5.25 V upper limit by margin only if the peripheral tolerates it. Anything specified as
-"5 V ± 5 %" (4.75–5.25 V) is **out of specification on this port.** Worth knowing before
-blaming a peripheral.
-
-## 4. Module footprint `M1` — complete pad map
-
-Left column, pads 1–17 (pin tokens at x = 272.50, net labels ~2.8 pt above the wire at
-x ≈ 233–257):
-
-| Pad | Pin name | Net |
-|---|---|---|
-| 1 | `G1` | `GI` |
-| 2 | `G2` | `GO` |
-| 3 | `G3` | **`beep`** |
-| 4 | `G4` | `LCD_RS` |
-| 5 | `G5` | `LCD_MOSI` |
-| 6 | `G6` | `LCD_SCK` |
-| 7 | `G7` | `LCD_CS` |
-| 8 | `G8` | `LCD_RESET` |
-| 9 | `G9` | `LCD_BL` |
-| 10 | `G10` | `BATADC` |
-| 11 | `GND` | `GND` |
-| 12 | `G11` | `IN_SDA` |
-| 13 | `5V` | `+5VIN` |
-| 14 | `G12` | `IN_SCL` |
-| 15 | `G13` | `SDA` |
-| 16 | `G14` | `G14` |
-| 17 | `G15` | `SCL` |
-
-Right column, pads 18–28 (pin numbers at x ≈ 361, pin names at x ≈ 324–342, net labels at
-x ≈ 386–390):
-
-| Pad | Pin name | Net |
-|---|---|---|
-| 18 | `GND` | `GND` |
-| 19 | `G39/MTCK` | `G39` |
-| 20 | `G0/Boot` | — |
-| 21 | `G40/MTDO` | **`IN_B`** |
-| 22 | `EN` | — |
-| 23 | `G41/MTDI` | **`IN_A`** |
-| 24 | `G44/Rx` | — |
-| 25 | `G42/MTMS` | **`WAKE`** |
-| 26 | `G43/Tx` | — |
-| 27 | `G46` | `HOLD` |
-| 28 | `3V3` | `3V3` |
-
-Two distinct I²C buses are visible: **`IN_SDA`/`IN_SCL`** (pads 12/14 → `G11`/`G12`, the internal
-bus, to `U5` `RTC8563`) and **`SDA`/`SCL`** (pads 15/17 → `G13`/`G15`, the external Grove bus to
-`J4`).
-
-## 5. Designator census with values, as printed
-
-| Des | Value / part | Function |
-|---|---|---|
-| `U1` | `ME3116AM6G` | wide-input buck (`VIN`/`BST`/`EN`/`LX`/`FB`/`GND`), `L1` 10 µH `3015` |
-| `U2` | `TP4057` | Li-ion charger — `BAT`, `CHRG`, `STDBY`, `PROG`, `VCC`, `GND` |
-| `U3` | `SY7088` | Grove 5 V boost — §3 |
-| `U4` | `BL8075CB5TR33` | 3.3 V regulator (`VIN`/`VOUT`/`EN`/`NC`/`GND`) |
-| `U5` | `RTC8563` | RTC — `OSCI`, `OSCO`, `INT`, `VSS`, `VDD`, `CLKOUT`, `SCL`, `SDA` |
-| `U6` | — | load switch (`EN`/`VIN`/`VOUT`, `A1`/`A2`) on the Grove rail |
-| `U7` | `CN809J` | reset supervisor — `RESET`, `VCC`, `GND` |
-| `Q1` | — | `VBAT_IN` path |
-| `Q3`, `Q6` | `AP40P05` | P-FET, `VBAT_IN` → `VBAT_OUT` |
-| `Q4` | `LN2324DT2AG` | `HOLD` latch |
-| `Q5` | `SS8050` | buzzer driver — §2 |
-| `D1`,`D9`,`D11` | `B5819W SL` | Schottky |
-| `D2`,`D3`,`D4`,`D5`,`D10` | `B5819WT` | Schottky, wake/latch network |
-| `D6`,`D7` | `1N4148WT` | §2 |
-| `D8` | `SS34` | |
-| `D12` | `SD36` | |
-| `Y1` | (top mark of `Q5`) | — **not a crystal** |
-| `Y2` | 32.768 kHz ±20 ppm 12.5 pF | RTC crystal, `C28`/`C29` 6.0 pF |
-| `J1` | `Header 2`, `6V~36V` | DIN-rail supply input |
-| `J3`,`J4` | `HY-2.0_IIC` | Grove ports |
-| `J5` | `Rotary encode` | §1 |
-| `FPC1` | `FPC-0.5-8P` | LCD — `LCD_CS`, `LCD_SCK`, `LCD_MOSI`, `LCD_RS`, `LCD_RESET`, `FPC_LCD_BL` |
-| `LS1` | `Buzzer` | §2 |
-| `S1`,`S4` | `SW-PB` | `BTN` |
-| `M1` | Stamp module | §4 |
-
----
-
-## Reproducing
-
-```bash
-nix-shell -p poppler-utils --run 'pdftotext -bbox-layout \
-  "devices/m5stack/dinmeter/artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf" /tmp/din.xhtml'
-cd scratch/schematic-tracing
-python3 netlist.py /tmp/din.xhtml --des J5
-python3 trace.py   col /tmp/din.xhtml --x 143 --tol 8      # the LS1 / Q5 column
-python3 render.py  /tmp/din.xhtml --x0 430 --x1 580 --y0 345 --y1 430
-```
diff --git a/devices/m5stack/dinmeter/sources.md b/devices/m5stack/dinmeter/sources.md
deleted file mode 100644
index ad9ee53..0000000
--- a/devices/m5stack/dinmeter/sources.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# DinMeter — sources
-
-Schema per the research method: `ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path`.
-
-`Class` ∈ `primary` · `authorized mirror` · `credible mirror` · `standard` · `community`.
-All retrievals 2026-09-04 unless stated. Covers **both** K134 and K134-V11; the v1.1 record's
-own additions are in [`../dinmeter-v1.1/sources.md`](../dinmeter-v1.1/sources.md).
-
----
-
-## Vendor product documentation
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| S-01 | DinMeter product documentation (SKU K134) | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/M5DinMeter> | 2026-09-04 | unversioned; page regenerated per request | Full specification table, PinMap, Learn (power on/off, download mode), datasheet links, bundle contents | Rendered client-side; content extracted from the server-sent `#document` block. **`/en/core/DinMeter` returns HTTP 404** — negative control | `artifacts/docs/docs-en-core-M5DinMeter.txt` |
-| S-02 | DinMeter documentation, printable export | M5Stack | primary | official PDF | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/en/core/M5DinMeter.pdf` | 2026-09-04 | unversioned | Same content plus product photography | 7 459 888 B, SHA-256 `8b3db00a…`; **archived** | [placeholder](artifacts/docs/docs-en-core-M5DinMeter.pdf.ARCHIVED.md) |
-| S-03 | DinMeter v1.1 product documentation (K134-V11) | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/DinMeter_v1.1> | 2026-09-04 | page created ~2026-01-30 | ST7789P3, Stamp-S3A, RGB-LED/GPIO38 note, product-comparison table | as S-01 | `../dinmeter-v1.1/artifacts/docs/docs-en-core-DinMeter_v1.1.txt` |
-| S-04 | DinMeter schematic | M5Stack | primary | schematic (Altium PDF) | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/500/DIN_Meter_v1.0.pdf` | 2026-09-04 | titled `DIN_Meter_v1.0` | **The primary evidence for this record.** 84 designators, complete `M1` pinout, full power tree | 1 sheet, 433 658 B, SHA-256 `03ec3353…`. `%PDF` validated; text layer validated against visible headings | `artifacts/schematic/K134_DIN_Meter_v1.0-schematic.pdf` |
-| S-05 | DinMeter v1.1 "schematic" | M5Stack | primary | schematic | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf` | 2026-09-04 | filename says `v1.0` | **Byte-identical to S-04.** Establishes that no v1.1 schematic is published | same hash as S-04 | `../dinmeter-v1.1/artifacts/schematic/…` |
-| S-06 | DinMeter dimension/assembly drawing | M5Stack | primary | drawing | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1211/K134-din_meter_asm_v1.pdf` | 2026-09-04 | unversioned | Mechanical envelope | 117 405 B, `db42c8a9…`. **The same URL is linked from both product pages** | `artifacts/mechanical/K134-din_meter_asm_v1-dimensions.pdf` |
-| S-07 | DinMeter structure model | M5Stack | primary | repository (STL) | `m5stack/M5_Hardware` → `Products/K134_DinMeter/Structures/DinMeter.stl` | 2026-09-04 | HEAD `a240115c94b19ecf647f229c47fa9a8ce46ccdc4`, 2026-08-17 | 3D envelope | 573 284 B, `90f04d6a…`; **byte-identical to `DinMeter_v1.1.stl`**. Repo has **no `LICENSE`** | `artifacts/mechanical/DinMeter.stl` |
-| S-08 | M5Stack shop listing, DinMeter (K134) | M5Stack | primary | store listing | `https://shop.m5stack.com/products/m5stack-din-meter-w-m5stamps3.js` | 2026-09-04 | published 2024-03-08 | Title **`[EOL] M5Stack Din Meter w/ M5StampS3`**, SKU `K134`, USD 24.50, **`available: false`** | Shopify JSON; price is USD | `scratch/m5stack-dinmeter/shop/` |
-| S-09 | M5Stack shop listing, DinMeter v1.1 | M5Stack | primary | store listing | `https://shop.m5stack.com/products/m5stack-din-meter-v1-1-with-m5stamps3a.js` | 2026-09-04 | created 2026-01-30T10:02:16+08:00 | SKU `K134-V11`, USD 24.50, in stock, product id 9014041182465, tags `ESP32-S3`/`STAMP` | as S-08 | `scratch/m5stack-dinmeter/shop/` |
-| S-10 | `docs.m5stack.com` sitemap | M5Stack | primary | sitemap | <https://docs.m5stack.com/sitemap.xml> | 2026-09-04 | — | **5 703 URLs.** The only reliable way to enumerate product pages; the `/en/products` index is a JS shell | 499 000 B | `scratch/m5stack-dinmeter/docs/` |
-
-## Stamp module documentation
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| S-11 | Stamp-S3 product documentation (S007) | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/StampS3> | 2026-09-04 | — | ESP32-S3FN8, 8 MB, MUN3CAD01-SC, WS2812B-2020, PROANT-class 3D antenna, 23 IOs, 24 × 18 × 4.7 mm, power figures | — | `scratch/m5stack-dinmeter/docs/` |
-| S-12 | Stamp-S3A product documentation (S007-V033) | M5Stack | primary | official page | <https://docs.m5stack.com/en/core/Stamp-S3A> | 2026-09-04 | — | Same 23 IOs, **26 × 18 × 4.7 mm**, improved power figures, **the two-row product-comparison table** | ⚠ Its `DC-DC: MUN3CAD01-SC` row is contradicted by S-14 | `scratch/m5stack-dinmeter/docs/pages/` |
-| S-13 | Stamp-S3 schematic, board rev **v0.2** | M5Stack | primary | schematic | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/522/Sch_M5StampS3_v0.2.pdf` | 2026-09-04 | v0.2 | `M2` = MUN3CAD01-SC, `U2` = SGM2578/WS4622C-4, `U3` WS2812 on `VDD_3V3`, `ANT1` = PROANT440 | 348 884 B, `6d92e1ae…` | `components/m5stack/stamp-s3/artifacts/Sch_M5StampS3_v0.2.pdf` |
-| S-14 | Stamp-S3A schematic, board rev **v0.3.3** | M5Stack | primary | schematic | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/Sch_StampS3_v0.3.3.pdf` | 2026-09-04 | v0.3.3 | `U4` unidentified buck + `L4`, `U2` = AW35122FDR, `U3` WS2812 on **`BL_3V3`**, rebuilt antenna match | 369 766 B, `2f9610ae…`. **Filename says `StampS3`, not `StampS3A`** | `components/m5stack/stamp-s3a/artifacts/Sch_StampS3_v0.3.3-StampS3A.pdf` |
-| S-15 | Stamp-S3A dimension drawing | M5Stack | primary | drawing | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1150/STAMP-S3A.pdf` | 2026-09-04 | — | Mechanical | 95 380 B, `27ba5206…` | `components/m5stack/stamp-s3a/artifacts/STAMP-S3A-dimensions.pdf` |
-| S-16 | Stamp-S3 / Stamp-S3A pin-map images | M5Stack | primary | diagram | `…/684/S007_PinMap_01.jpg`, `…/1150/S007-V033_PinMap_01.jpg` | 2026-09-04 | — | Official pin maps | JPEG; **not OCR'd** in this pass | `components/m5stack/stamp-s3{,a}/artifacts/` |
-| S-17 | Stamp-S3 / Stamp-S3A STL models | M5Stack | primary | repository | `m5stack/M5_Hardware` @ `a240115c…` | 2026-09-04 | 2026-08-17 | **Byte-identical to each other** (`f72c1af2…`); no Stamp-S3A footprint exists | no `LICENSE` in repo | `components/m5stack/stamp-s3{,a}/artifacts/` |
-| S-18 | Stamp-S3 KiCad footprints | M5Stack | primary | repository | `m5stack/M5_Hardware` → `KiCad/Footprints/M5Stack.pretty/Stamp-S3-{SMD,DIP}.kicad_mod` | 2026-09-04 | @ `a240115c…` | The DinMeter `M1` footprint | no `LICENSE` | `components/m5stack/stamp-s3/artifacts/` |
-| S-19 | Stamp-S3 STEP model | M5Stack | primary | repository | `m5stack/M5_Hardware` → `KiCad/3D/M5Stack.3dshapes/Stamp-S3.step` | 2026-09-04 | @ `a240115c…` | 3D solid | 2 904 597 B, `7f29337c…`; **archived** | [placeholder](../../../components/m5stack/stamp-s3/artifacts/Stamp-S3.step.ARCHIVED.md) |
-| S-20 | Shop listings: Stamp-S3, Stamp-S3A, M5Dial v1.1 | M5Stack | primary | store listing | `shop.m5stack.com/products/{m5stamp-esp32s3-module,m5stamps3a-with-2-54-header-pin,m5stack-dial-v1-1}.js` | 2026-09-04 | 2023-02-10 / 2025-09-11 / 2025-03-07 | Stamp-S3 = **`[EOL]`, unavailable**, USD 7.50; Stamp-S3A USD 7.50 in stock; M5Dial v1.1 USD 34.90 | Shopify JSON | `scratch/m5stack-dinmeter/shop/` |
-
-## Component datasheets (filed under their components)
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Version | Establishes | Limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| S-21 | ST7789V2 datasheet | Sitronix | authorized mirror (M5Stack-hosted) | datasheet | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf` | 2026-09-04 | **V1.0, 2016/11** | Display controller | 3 216 854 B, `89376784…`. No Sitronix-hosted copy located | `components/sitronix/st7789v2/artifacts/` |
-| S-22 | BM8563 datasheet | unattributed (no vendor on page 1) | authorized mirror | datasheet | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/BM8563_V1.1_cn.pdf` | 2026-09-04 | V1.1 | RTC: address 0x51, 1.5–5.5 V, 0.25 µA | 590 599 B, `a847c85a…`. **Chinese only** — primary source. ⚠ carries a stray `MAX1937` string in its header (derived document) | `components/generic/bm8563/artifacts/` |
-| S-23 | TP4057 datasheet | unattributed | authorized mirror | datasheet | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/M5DinMeter/tp4057.pdf` | 2026-09-04 | unversioned | Charger: SOT23-6, 500 mA max, **4.24 V float** | 628 588 B, `c949a7c3…`. Chinese only. Note M5Stack files a *chip* datasheet under a *product* path | `components/generic/tp4057/artifacts/` |
-| S-24 | MUN3CAD01-SC datasheet | Murata (inferred from the µPOL trademark; no vendor name on page 1) | authorized mirror | datasheet | `https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/Stamp/S007%20StampS3/MUN3CAD01-SC.pdf` | 2026-09-04 | unversioned | 1 A µPOL, 2.7–5.5 V in, 0.8–4.0 V out, 2.9 × 2.3 × 1.05 mm | 2 045 960 B, `90e2ecbd…` | `components/murata/mun3cad01-sc/artifacts/` |
-| S-25 | ESP32-S3 datasheet | Espressif | authorized mirror | datasheet | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf` | 2026-09-04 | v2.0 | SoC | **Byte-identical** (`b6db403d…`) to `components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf` already held. **Not duplicated**; URL recorded only | *(existing)* |
-| S-26 | DC terminal `DB2EK-2.54-2P-GN-S` | 宁波地博电气有限公司 (Ningbo Dibo Electric) | authorized mirror | datasheet | `…/resource/docs/products/core/M5Dial/DB2EK-2.54-2P-GN-S%202.54mm%202Pin%20Green.pdf` | 2026-09-04 | — | The 6–36 V screw terminal | 383 085 B, `ed6e82d9…`. Filed under M5Dial's path but linked from DinMeter's page | `scratch/m5stack-dinmeter/docs/` |
-| S-27 | Battery socket `1.25WT-2P` | unattributed | authorized mirror | datasheet | `…/resource/docs/products/core/M5Dial/1.25WT-2P.pdf` | 2026-09-04 | — | The battery connector | 1 110 811 B, `743d2118…`. **No text layer** — image-only scan | `scratch/m5stack-dinmeter/docs/` |
-
-## Software and board support
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Commit / release | Establishes | Limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| S-28 | `m5stack/M5DinMeter` Arduino library | M5Stack | primary | repository | <https://github.com/m5stack/M5DinMeter> | 2026-09-04 | HEAD `8ccbad7297beb82a140f812e5606e060d8a5e0dc`; release `1.0.0` (2024-03-07) | Encoder pins 41/40, the six vendor examples, the M5Unified façade | **No `LICENSE` file**; GitHub reports no licence. Header guard is `M5DIAL_H` (copied from M5Dial) | `artifacts/source-snapshots/M5DinMeter-8ccbad72….tar.gz` |
-| S-29 | `m5stack/M5DinMeter-UserDemo` | M5Stack | primary | repository | <https://github.com/m5stack/M5DinMeter-UserDemo> | 2026-09-04 | HEAD `d2fdfe44e9baf810f82335faa6f5962e9fc59a44`; release `V0.1` (2024-03-04) | **The factory-firmware source.** LovyanGFX config (offset 52/40, invert, 40 MHz, BL PWM 200 Hz ch 7), the eight factory tests, pinned deps | **MIT** (`LICENSE`, © 2024 M5Stack). Mixed-licence: bundles PJRC `Encoder`, `ESP32Encoder`, `I2C_BM8563`, `Button` | `artifacts/source-snapshots/M5DinMeter-UserDemo-d2fdfe44….tar.gz` |
-| S-30 | `m5stack/M5Unified` | M5Stack | primary | repository | <https://github.com/m5stack/M5Unified> | 2026-09-04 | master `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`; latest release 0.2.21 (2026-08-26) | `board_M5DinMeter` tables: I²C `:96`, Port B `:159`, RGB `:246`, power-hold `:282`, pinMode `:2400`, speaker `:2921`, buttons `:3502` | MIT. **No `board_M5StampS3A`, no v1.1 board enum** | *(read from a fetched tarball; not vendored — reproducible from the commit)* |
-| S-31 | `espressif/esp-board-manager` — `m5stack_dinmeter` | Espressif | primary | repository | <https://github.com/espressif/esp-board-manager> | 2026-09-04 | HEAD `2beb9b22b0892b343bd555a1ebc9929a7edce8fc` (2026-09-03) | **The best technical description of this board anywhere**: GRAM gap 52/40, PCNT decoder, LEDC configs, the GPIO3-vs-GPIO42 resolution, an ESP32-S3 build trap | Its own header cites M5Stack's PinMap as source, so its Grove colour note is a *reproduction*, not corroboration | `artifacts/source-snapshots/dinmeter-board_{info,devices,peripherals}.yaml` |
-| S-32 | `bmorcelli/Launcher` — DinMeter board file | Bruno Morcelli | community | repository | <https://github.com/bmorcelli/Launcher> | 2026-09-04 | `main`, board `boards/m5stack-dinmeter/platformio.ini`; ★2054; last push 2026-09-04 | **Independent corroboration** of display pins, GRAM offsets, battery divider ratio 2.0, no-PSRAM; and an SD-over-Grove demonstration | MIT. Community, but a *shipped, CI-built* target — MD5 `bccbefef5284357a2a7c3c7cc196fd98` → `Launcher-m5stack-dinmeter.bin` | `artifacts/source-snapshots/launcher-m5stack-dinmeter-platformio.ini` |
-| S-33 | DinMeter Arduino tutorials | M5Stack | primary | official page | `docs.m5stack.com/en/arduino/m5dinmeter/{program,display,encoder,rtc,buzzer,button,battery,wakeup,wifi}` | 2026-09-04 | — | Per-feature vendor tutorials, 9 pages, all HTTP 200 | JS-rendered | `scratch/m5stack-dinmeter/docs/pages/` |
-| S-34 | DinMeter UiFlow2 tutorial | M5Stack | primary | official page | <https://docs.m5stack.com/en/uiflow2/m5dinmeter/program> | 2026-09-04 | — | UiFlow2 is supported | — | `scratch/m5stack-dinmeter/docs/pages/` |
-
-## Community
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Date | Establishes | Evidence type |
-|---|---|---|---|---|---|---|---|---|---|
-| S-35 | "Check out what's new this week!" | u/M5Stack (official) | community | forum/social post | <https://old.reddit.com/r/M5Stack/comments/1qr0ju2/check_out_whats_new_this_week/> | 2026-09-04 | **2026-01-30** | The v1.1 launch date, corroborating the shop `created_at` | **marketing** (vendor-posted); 22–23 points, **1 comment** |
-| S-36 | GitHub repository search, `DinMeter` | GitHub | community | repository | GitHub Search API | 2026-09-04 | — | 19 repositories, 13 genuinely targeting the device | catalogued in [`projects-and-community.md`](projects-and-community.md) |
-| S-37 | `community.m5stack.com` search | M5Stack | primary | forum | `…/api/search?term=dinmeter` and `…/search?term=dinmeter` | 2026-09-04 | — | **API HTTP 401 (login required); HTML is a NodeBB JS shell.** Blocked, not empty | negative result |
-
----
-
-## Notes on evidence quality
-
-- **The schematic is the backbone of this record.** Where the vendor's prose and the schematic
-  disagree (Grove colours, Stamp-S3A DC-DC, Grove rail voltage), the schematic is treated as the
-  stronger evidence and the disagreement is recorded in
-  [`gaps-and-conflicts.md`](gaps-and-conflicts.md) rather than resolved silently.
-- **Espressif's `esp-board-manager` is the most useful secondary source** and is unusually
-  candid, but its Grove wire-colour note derives from M5Stack's disputed table and must not be
-  counted as an independent confirmation.
-- **`bmorcelli/Launcher` is genuinely independent** — different author, different toolchain,
-  shipped binaries — and agrees with the schematic on every point it touches.
-- **Nothing in this record was tested on hardware.**
diff --git a/devices/m5stack/papermono-lite/README.md b/devices/m5stack/papermono-lite/README.md
deleted file mode 100644
index b6878ba..0000000
--- a/devices/m5stack/papermono-lite/README.md
+++ /dev/null
@@ -1,410 +0,0 @@
-# M5Stack PaperMono-Lite
-
-> **SKU `C153-Lite`** (as the documentation writes it) / **`C153-LITE`** (as the
-> Shopify record writes it) · **USD 55.00** · white case · **no NFC, no LoRa** ·
-> announced and on sale **2026-08-21** alongside the PaperMono · documentation
-> published **2026-08-20** · at the research snapshot of **2026-09-01** it was
-> **out of stock at the official store and listed by no reseller anywhere**.
-
-## Read the PaperMono record first
-
-**This is a variant record, not a standalone one.** The PaperMono-Lite is the
-same board as the [PaperMono](../papermono/README.md) with two radios removed and
-a different case colour. Everything about the SoC, the panel, the power
-architecture, the two auxiliary microcontrollers, the pin map, the boot behaviour
-and the development workflow is identical, and is documented **once**, there:
-
-| Document | Applies to the Lite? |
-|---|---|
-| [`../papermono/README.md`](../papermono/README.md) | **Yes**, except the NFC and LoRa rows of the specification table and the NFC/LoRa lines of the architecture diagram |
-| [`../papermono/pinouts-and-buses.md`](../papermono/pinouts-and-buses.md) | **Mostly.** See [what does not apply](#which-papermono-documents-apply-unchanged) — six ESP32-S3 GPIOs, two M5IOE1 pins, one M5PM1 GPIO, one I²C address and two connectors are radio-related and are unverified on this variant |
-| [`../papermono/power-architecture.md`](../papermono/power-architecture.md) | **Yes**, except the LoRa rail (`3V3_L2_LoRa`, M5PM1 `G2`) and the NFC load switch. The five power states, the charger, the frontlight and every wake source are unchanged |
-| [`../papermono/pin-naming-and-the-pyg-ambiguity.md`](../papermono/pin-naming-and-the-pyg-ambiguity.md) | **Yes, in full, and it matters more here** — see [below](#the-pyg-hazard-is-worse-on-the-lite-not-better) |
-| [`../papermono/gaps-and-conflicts.md`](../papermono/gaps-and-conflicts.md) | **Yes**, except G5 (the missing `Stamp-LoRa-1262` datasheet) and G1 (the missing NFC schematic sheet), which are not Lite problems |
-| [`../papermono/sources.md`](../papermono/sources.md) | **Yes.** Sources **S04**, **S05**, **S06**, **S16**, **S17**, **S49** and **S89** are Lite-specific; every ID cited below is defined there |
-| [`../papermono/research-log.md`](../papermono/research-log.md) · [`../papermono/commands.md`](../papermono/commands.md) | **Yes** — one research pass covered both SKUs |
-
-**Nothing in this record was verified against physical hardware.** No
-PaperMono-Lite exists in this session and none could be bought.
-
-## Identity
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | PaperMono-Lite | vendor product page (S04) |
-| SKU | **`C153-Lite`** on `docs.m5stack.com`; **`C153-LITE`** in the Shopify record | S04, S49 — **the case differs between the vendor's own two systems** |
-| Internal firmware name | **`Lite`**, against **`Pro`** for the full model | `M5PaperMono-UserDemo/main/hal/hal_board.cpp` (S41) — note the vendor's *firmware* calls the C153 "Pro" although the *product* is just "PaperMono" |
-| Manufacturer | M5Stack Technology Co., Ltd (Shenzhen) | vendor site |
-| Case colour | **White** | vendor comparison table |
-| Store price | **USD 55.00** | S49 |
-| Store status 2026-09-01 | Out of stock, `inventory_quantity = 0`, `inventory_policy = "deny"` | S49 |
-| Store record created / published | `2026-08-18T14:26:42+08:00` / `2026-08-21T12:00:09+08:00` | S49 — created three minutes *before* and published one second *before* the PaperMono |
-| Documentation published | 2026-08-20, category "Controllers" | S13 |
-| Schematic asset | `PaperMono-Lite_PRJ_V0.6.2_20260522.pdf` — **`PRJ`, 4 sheets** | S04, S16 — **not retrieved**; see [gaps](#gaps-specific-to-this-record) |
-
-No certification identifier is published for this SKU either: `/en/certification`
-(S11) returns zero matches for `PaperMono`, `C153` **and** `C153-Lite`. That is a
-verified negative, not a failed search.
-
-## The vendor's own comparison table
-
-Reproduced complete and verbatim from S04. **Both product pages carry the
-identical table**, so this is the vendor's considered statement of the difference.
-
-| Product Compare | PaperMono | PaperMono-Lite |
-|---|---|---|
-| Main Controller | ESP32-S3R8 | ESP32-S3R8 |
-| Display | 3.97" 4-level grayscale black-and-white E-Paper, 480x800 | 3.97" 4-level grayscale black-and-white E-Paper, 480x800 |
-| Touch | FT6336G | FT6336G |
-| Front Light | Integrated | Integrated |
-| Wi-Fi | 2.4 GHz | 2.4 GHz |
-| **NFC** | **ST25R3916** | **❌** |
-| **LoRa** | **Stamp LoRa-1262** | **❌** |
-| Expansion Storage | microSD | microSD |
-| IMU | BMI270 | BMI270 |
-| RTC | RX8130CE | RX8130CE |
-| Battery | 1150mAh | 1150mAh |
-| **Shell Color** | **Gray** | **White** |
-
-Four rows of that table carry the entire product difference: **NFC, LoRa, shell
-colour — and the price, which the table does not show.** The two radios are the
-whole of the **USD 10.00** delta.
-
-## What the comparison table leaves out
-
-The table above is accurate and incomplete. Diffing the two pages' **full
-specification tables** recovers five further differences the vendor does not
-surface, all established from primary vendor text (S01 against S04):
-
-| Specification | PaperMono | PaperMono-Lite | Delta |
-|---|---|---|---|
-| **Product Weight** | **74.7 g** | **72.4 g** | **−2.3 g** |
-| **Gross Weight** | **91.3 g** | **88.9 g** | **−2.4 g** |
-| SoC clock wording | "240MHz" | "**up to** 240MHz" | wording only |
-| NFC row | `ST25R3916 (ISO14443A/B, FeliCa™, ISO15693)` | **row absent entirely** | the Lite table has no NFC row at all |
-| LoRa row | `SX1262 (Stamp LoRa-1262), 868–923 MHz, FPC ant.` | **row absent entirely** | likewise |
-| **Schematic asset** | `PaperMono_SCH_V0.6.2_20260522.pdf` — **`SCH`, 6 sheets** | `PaperMono-Lite_PRJ_V0.6.2_20260522.pdf` — **`PRJ`, 4 sheets** | different naming convention and **two fewer sheets** |
-| Model-size asset | `1267/C153_PaperMono_model_size.pdf` | `1268/C153-Lite_PaperMono-Lite_model_size.pdf` | separate mechanical drawings |
-| Datasheets listed | 7 (incl. ST25R3916 and SX1261/2) | **5** | the Lite drops the two radio datasheets |
-| PinMap sections | includes **RFID** and **LoRa** blocks | **both blocks absent** | |
-| PlatformIO env | `[env:m5stack-papermono]` | `[env:m5stack-papermono-lite]` | |
-| PlatformIO `lib_deps` | 5 libraries, incl. `M5Unit-NFC` and `RadioLib` | **3 libraries** | |
-| Applications listed | E-Reader, Signage, Access Control, Identity Auth, Intelligent Transport | E-reader, Electronic shelf label, Information display terminal, **Portable control panel**, **Low-power IoT node** | entirely different positioning |
-| Shipping weight (Shopify) | 100 g | 98 g | S48 / S49 |
-
-**The weight difference is the most useful number here**, because it is a
-*measurement* rather than a marketing statement: 2.3 g is the mass of the NFC
-sub-board, its crystal and antenna, and the `Stamp-LoRa-1262-mini` module with its
-FPC antenna. It is consistent with those parts being genuinely absent rather than
-merely unpopulated on an otherwise identical assembly — though **the schematic
-that would settle that (S16) was not retrieved**, so this remains `inferred`.
-
-Two sheets fewer is the other quantitative hint. The PaperMono schematic
-concatenates three Altium documents: the main project (sheets 1–4), the KEY/RGB
-sub-board (sheet 5) and the NFC sub-board (sheet 6, itself explicitly numbered
-`2/2` with sheet 1 missing). A four-sheet Lite `PRJ` is exactly what you would
-expect if the **NFC document were dropped entirely** and one main-board sheet
-consolidated — but that is arithmetic on a page count, not a reading of the file.
-`inferred`, and it is precisely why S16 is the highest-value untaken lead in this
-record.
-
-## Things that are identical, and look as though they should not be
-
-These are worth stating explicitly, because each one is a reasonable assumption
-that is **wrong**.
-
-- **The battery is 1150 mAh on both.** The Lite does not get a smaller cell. The
-  2.3 g it saves is radio hardware, not capacity.
-- **The physical dimensions are identical** — 62.0 × 101.0 × 8.0 mm product,
-  113.2 × 69.6 × 21.0 mm package. Same enclosure, different colour.
-- **Both pages link the *same* EasyLoader binary, and it lives under the
-  PaperMono's asset folder**: `…/1267/C153-PaperMono-UserDemo_0x00.exe` — note
-  **`1267`** (PaperMono), not `1268` (Lite). The Lite page has its own asset
-  folder for images, the schematic and the mechanical drawing, but not for
-  firmware. (S40; the file itself was not retrieved.)
-- **Both pages link the same two M5Burner firmware records**, and the official
-  one's API metadata reads, verbatim:
-
-  ```json
-  "firmwareName": "PaperMono UserDemo",
-  "firmwareDescription": "PaperMono / PaperMono-Lite UserDemo",
-  "sourceType": "OFFICIAL"
-  ```
-
-  **One image serves both SKUs** (S33). The vendor's link label for it —
-  "PaperMono-Lite Factory Firmware Restoration" — is also mislabelled in the same
-  way as the PaperMono's: the artifact is a demo application, not a factory-reset
-  image.
-- **Both pages link the same two GitHub repositories**, `M5PaperMono-UserDemo`
-  (S41) and `M5PaperMono-OTP-Demo` (S42). The OTP demo's README covers both SKUs
-  by name.
-- **The M5GFX refresh timings are the same four numbers** — 4.71 / 0.45 / 0.34 /
-  0.07 s — and **the Lite page's own caption still says "laboratory test results
-  for *PaperMono*"**. The Lite figures appear to be copied rather than separately
-  measured. `inferred`, and a good reason not to treat either set as a
-  Lite-specific measurement.
-- **The UiFlow2 tutorial is one shared page** whose title is literally
-  "PaperMono / PaperMono-Lite : Flash Firmware & Run Code" (S09) — and it states
-  no required firmware version, no block list and no limitations for either SKU.
-- **The Arduino tutorial pages are the PaperMono's**, linked from the Lite page
-  under Lite-flavoured titles (S07, S08). The power-management tutorial therefore
-  documents the LoRa rail enable and the NFC enable pin to Lite readers as though
-  they were theirs.
-
-## How the two variants are actually told apart in software
-
-This is the part with real engineering consequences, and it is established from
-vendor source rather than vendor prose (S41, S47).
-
-**M5GFX cannot distinguish them.** Its board-detection probe reads four I²C
-addresses and masks the NFC bit out deliberately:
-
-```c
-static constexpr uint8_t stopwatch_i2c_addr_list[] = {
-  0x32u, // RX8130
-  0x68u, // BMI270
-  0x15u, // Touch CST820 (for StopWatch)
-  0x50u, // NFC (for PaperMono Pro)
-};
-const bool is_papermono = (i2c_result & ~1u) == ~0b0011u; // no CST820, with NFC == PaperMono,PaperMono Pro
-```
-
-Both variants therefore resolve to the **single enum `board_M5PaperMono`**, which
-is confirmed afterwards by reading the M5PM1 and M5IOE1 device IDs. From the
-graphics library's point of view there is one board.
-
-**Only the application layer distinguishes them**, and it does so twice over:
-
-1. **An NFC identity probe** — register **`0x7F`** is read and compared against
-   expected type **`0x05`** (`main/hal/hal_board.cpp:22-23`, used at `:145`).
-2. **A write-failure fallback** — the firmware powers the NFC rail through M5IOE1
-   `PYG4` and, if either that write or the RGB LED is unavailable, declares the
-   board `Lite`:
-
-   ```c
-   void Hal::detectBoardVariant()
-       if (!_rgb_ready) { _board_variant = BoardVariant::Lite; return; }
-       m5ioe1_err_t err = M5IOE1_OK;
-       ioe1.digitalWriteWithRes(NFC_EN_PIN, HIGH, &err);
-       if (err != M5IOE1_OK) { _board_variant = BoardVariant::Lite; return; }
-   ```
-
-**Three consequences worth planning around**, all `inferred` from source and
-`not-tested`:
-
-- **Variant detection is a negative test.** "Lite" is what the firmware concludes
-  when the NFC probe *fails*. Any unrelated fault on the I²C bus, on the M5IOE1,
-  or on the RGB LED path can therefore make a **full PaperMono report itself as a
-  Lite**. If you branch on the variant, branch conservatively.
-- **A board-enum check is not a capability check.** Code that asks M5GFX which
-  board it is running on will get `board_M5PaperMono` on a Lite and may then try
-  to talk to hardware that is not fitted. Probe `0x50` yourself.
-- **The PlatformIO `lib_deps` difference is a build-time hint, not a guard.**
-  Nothing stops a Lite build from including `M5Unit-NFC` and `RadioLib`; they will
-  simply find nothing.
-
-## The `PYG` hazard is *worse* on the Lite, not better
-
-The naming ambiguity documented in
-[`../papermono/pin-naming-and-the-pyg-ambiguity.md`](../papermono/pin-naming-and-the-pyg-ambiguity.md)
-applies unchanged — the same two custom chips, the same inverted `PYG` convention
-— with one twist that is specific to this variant.
-
-The PaperMono page says the frontlight is driven by "`PYG3_BL_PWM` of the M5PM1";
-**the Lite page says "`G3_WAKEin` of M5PM1"** for the identical pin. Both are
-correct: the PaperMono page quotes the *net name*, the Lite page quotes the
-*symbol pin name*, and the schematic shows both on M5PM1 pin 13. But a reader who
-holds only the Lite page has never seen the `PYG3_BL_PWM` form, and a reader who
-holds only the PaperMono page may write to **M5IOE1 IO3** — which is the e-paper
-3.3 V rail enable, and cutting it stops the display silently.
-
-On the Lite specifically:
-
-- **`PYG4` still exists on the M5IOE1** and the vendor firmware still writes to it
-  as `NFC_EN` — that write is precisely the probe that fails and identifies the
-  board as a Lite. It is *not* a spare pin, and it is *not* absent.
-- **M5PM1 `G2` (`PYG2_LoRa_EN`)** and **M5IOE1 `PYG2` / `PYG10`** (LoRa antenna
-  switch and reset) are documented on the PaperMono pages that the Lite page links
-  to. Whether those nets are still routed on the Lite PCB is **unknown** — S16 was
-  not retrieved.
-
-Use this repository's convention throughout, on both variants: **`M5PM1.G3`** for
-the frontlight PWM, **`M5IOE1.IO3`** for the e-paper rail enable, and never a bare
-`PYG<n>`.
-
-## Which PaperMono documents apply unchanged
-
-**Apply in full:**
-
-- The five power states, every rail and enable, charging, the frontlight, and all
-  wake sources — [`power-architecture.md`](../papermono/power-architecture.md),
-  minus the LoRa rail.
-- The ESP32-S3 pin map for everything that is not a radio: I²C on GPIO47/48,
-  SPI2 to the e-paper on GPIO14–18, microSD on GPIO8–13, USB on GPIO19/20, UART0
-  on GPIO43/44, PDM on GPIO45/46, buzzer on GPIO42, buttons on GPIO2/3.
-- Boot, reset and download mode — including that the **M5PM1, not a button**,
-  drives GPIO0, and that no separate reset button exists.
-- The I²C bus and its two traps: the IP2315 charger gated off the bus behind
-  M5IOE1 `IO11`, and the M5IOE1's own undocumented address.
-- Every e-paper caution: the 40 MHz-versus-20 MHz clock conflict, the vendor's own
-  "M5GFX waveforms are currently unstable" warning, one full refresh per ten
-  partial refreshes, and the DC-imbalance damage risk.
-- The mandatory octal PSRAM build setting, and the absence of an OTA partition.
-
-**Do not apply:**
-
-- The **LoRa** sections anywhere in this record set — SPI1 on GPIO38–41, `DIO1` on
-  GPIO5, `BUSY` on GPIO21, the `U14` `Stamp-LoRa-1262-mini` connector, M5PM1 `G2`,
-  M5IOE1 `IO2` and `IO10`, and the `868–923 MHz` regulatory note.
-- The **NFC** sections — the `0x50` I²C device, `G6_RFID_INT` on GPIO6, the `J3`
-  board-to-board connector to the NFC sub-board, schematic sheet 6, and the
-  ST25R3916 component record as a *fitted part*.
-- Anything derived from schematic sheet 6, and the open gap about its missing
-  sheet 1/2.
-
-**Unknown, and marked so rather than assumed:** whether the six radio-related
-ESP32-S3 GPIOs, the two M5IOE1 pins and the one M5PM1 GPIO are left floating,
-tied off, or repurposed on the Lite PCB. Only S16 can answer that.
-
-## Components
-
-The Lite carries the same parts as the PaperMono **minus the two radio
-subsystems**. Records are shared; nothing below is Lite-specific silicon.
-
-| Function | Part | Record |
-|---|---|---|
-| SoC | ESP32-S3R8, 8 MB octal PSRAM in package | [esp32-s3r8](../../../components/espressif/esp32-s3r8/README.md) |
-| Flash | XM25UH128DHIQT, 16 MB SPI NOR | [xm25uh128dhiqt](../../../components/xmc/xm25uh128dhiqt/README.md) |
-| Panel | DKE `DEPG0397BBS770F3`, 3.97" 480 × 800 | [depg0397bbs770f3](../../../components/dke/depg0397bbs770f3/README.md) |
-| Display controller | Solomon Systech SSD1677 | [ssd1677](../../../components/solomon-systech/ssd1677/README.md) |
-| Frontlight driver | Awinic AW9967 boost WLED driver | [aw9967](../../../components/awinic/aw9967/README.md) |
-| Touch | FocalTech FT6336G, I²C `0x38` | [ft6336g](../../../components/focaltech/ft6336g/README.md) |
-| Power management | M5PM1, I²C `0x6E` | [m5pm1](../../../components/m5stack/m5pm1/README.md) |
-| I/O expander | M5IOE1, I²C `0x4F` | [m5ioe1](../../../components/m5stack/m5ioe1/README.md) |
-| Silicon behind both | Puya PY32L020F15U6 | [py32l020f15u6](../../../components/puya/py32l020f15u6/README.md) |
-| IMU | Bosch BMI270, I²C `0x68` (`0x69` accepted) | [bmi270](../../../components/bosch-sensortec/bmi270/README.md) |
-| RTC | Seiko Epson RX8130CE, I²C `0x32` | record not yet written — datasheet at `components/seiko-epson/rx8130ce/artifacts/` |
-| Charger | Injoinic IP2315, I²C `0x75`, gated off the bus | [ip2315](../../../components/injoinic/ip2315/README.md) |
-| USB OVP load switch | Awinic AW32901FCR | [aw32901](../../../components/awinic/aw32901/README.md) |
-| Main buck | Joulwatt JW5712 | [jw5712](../../../components/joulwatt/jw5712/README.md) |
-| LDOs (×4) | SSP7615-33DFR | [ssp7615-33dfr](../../../components/generic/ssp7615-33dfr/README.md) |
-| Load switches | Awinic AW35122FDR | [aw35122](../../../components/awinic/aw35122/README.md) |
-| Bus gate / level translator | Awinic AW39112DNR | [aw39112](../../../components/awinic/aw39112/README.md) |
-| Microphone | `LMD4737T261-AC02` PDM MEMS — ⚠ no datasheet found | [lmd4737t261-ac02](../../../components/generic/lmd4737t261-ac02-pdm-microphone/README.md) |
-| RGB LED | `RS-C1415MBAR` — ⚠ no datasheet found; red is on/off only | [rs-c1415mbar](../../../components/generic/rs-c1415mbar-rgb-led/README.md) |
-| Crystal | `CN4040M000157A530001`, 40 MHz — ⚠ no datasheet found | [crystal](../../../components/generic/cn4040m000157a530001-40mhz-crystal/README.md) |
-
-**Not fitted on this variant:** the **ST25R3916** NFC front end and the
-[Stamp LoRa-1262](../../../components/m5stack/stamp-lora-1262/README.md) module
-with its **SX1262** transceiver. Component records for the ST25R3916 and the
-SX1262 are **not yet written** — their datasheets are retained at
-`components/stmicroelectronics/st25r3916/artifacts/` and
-`components/semtech/sx1262/artifacts/` and are catalogued as S23 and S24. Those
-parts describe the PaperMono; they do **not** describe this board.
-
-> **Used By / back-link note.** Each component record above carries a **Used By**
-> section naming the devices that contain it. Those sections currently name the
-> **PaperMono (C153)** as the fitted board, because that is the schematic the
-> parts were read from (S14). **They apply to the PaperMono-Lite (C153-Lite)
-> equally**, on the strength of the vendor's own specification tables — but not on
-> the strength of a Lite schematic, which has not been read. When S16 is
-> retrieved, the shared components should gain an explicit `C153-Lite` mention and
-> the two radio records should gain an explicit exclusion. Recorded here rather
-> than edited into twenty component records on an inference.
-
-## Availability
-
-| Seller | SKU | Price | Stock, 2026-09-01 |
-|---|---|---|---|
-| shop.m5stack.com | `C153-LITE` | **USD 55.00** | Out of stock, `inventory_quantity = 0` |
-| every reseller checked | — | — | **no listing found anywhere** |
-
-The Pi Hut, OpenELAB (.io and .de), Switch Science, Adafruit, Reichelt, Botland,
-Core Electronics, MakerLab, Elektor and BerryBase all returned **zero results**
-for the Lite, while several of them do list the full PaperMono (S53–S55).
-Whether that is a distribution decision or simply lag is **not established**.
-Mouser, DigiKey and TinyTronics were bot-walled and returned no determination.
-
-Two details worth keeping apart:
-
-- The Lite's storefront inventory counter reads exactly **`0`**, while the
-  PaperMono's reads **`−129`**. The two SKUs are in different inventory states;
-  the negative is *consistent with* oversell but is not proof of it.
-- **The first public sell-out report is about the Lite, not the PaperMono**:
-  posted at 2026-08-21 04:09 UTC, **nine minutes** after the storefront published
-  (S72). The poster went on to publish the strongest third-party project on this
-  hardware (S89), which is why that ownership claim is corroborated across two
-  independent surfaces.
-
-## Community evidence specific to the Lite
-
-There is very little, and what exists is disproportionately valuable.
-
-- **`MagicCube/free-ink-on-paper-mono` (S89) runs on a PaperMono-Lite (C153-Lite),
-  not the full board.** Its README claims a complete verified hardware path — RTC
-  time from the RX8130, battery/USB/charging telemetry from the M5PM1, touch and
-  physical buttons, frontlight held at 127/255, async e-ink refresh with periodic
-  full cleanup, and "verified disabling of M5PM1's dangerous default single-click
-  reset". Independently corroborated on that last point by
-  `Free-Ink/freeink-sdk`'s `PaperMonoBoard.h` (S90). **These claims were read, not
-  reproduced.** Neither citation is pinned to a commit — a recorded defect.
-- **One widely repeated factual error concerns this SKU.** A launch article
-  (S79) described a **$55** model with NFC and LoRa. $55 is the Lite, which has
-  neither; the NFC/LoRa model is $65. If you find that claim repeated, it traces
-  to a single roundup post.
-- Everything else in
-  [`../papermono/README.md`](../papermono/README.md#community-editorial-and-project-coverage)
-  applies: zero written reviews, one hands-on video, and the real signal being
-  code rather than articles.
-
-## Should you buy the Lite instead?
-
-**Yes, unless you specifically need the radios.** That is the whole calculus, and
-it is unusually clean because the vendor has changed exactly one thing:
-
-- **Take the Lite** if you want an e-paper platform with a frontlight, touch, an
-  IMU, an RTC, a microphone, microSD and a genuinely hardware-level low-power
-  architecture. You save USD 10 and 2.3 g and lose nothing else — same SoC, same
-  panel, same battery, same enclosure, same firmware image.
-- **Take the PaperMono** if NFC or LoRa is load-bearing. USD 10 for an ST25R3916
-  and an SX1262 module is a good price for both, and they cannot be added
-  afterwards: **there is no expansion connector on either board.** Every GPIO is
-  committed, and the only route in is the shared I²C bus.
-- **Take neither** for a reading device or a fast/high-fidelity display. Four grey
-  levels, 480 × 800, and the vendor's own conservative refresh guidance apply
-  equally to both. The [PaperS3 comparison](../papermono/README.md#product-history-family-and-culture)
-  is the one that matters, and it is a trade rather than an upgrade.
-
-The Lite's *positioning* differs too, and the vendor is explicit about it: the
-PaperMono's application list leads with access control and identity
-authentication — radio applications — while the Lite's leads with electronic
-shelf labels, information displays and low-power IoT nodes. That is a coherent
-split, not marketing noise.
-
-## Gaps specific to this record
-
-- **The Lite schematic (S16) was not retrieved.** It is the only thing that can
-  establish what the board actually omits rather than what the comparison table
-  says it omits, whether the radio nets are still routed, and what the two "extra"
-  PaperMono sheets contained. **The single highest-value action for a follow-up
-  pass.**
-- **The Lite mechanical drawing (S17) was not retrieved.** The identical outline
-  dimensions are a marketing claim, not a measurement.
-- **No Lite-specific measurement of anything exists** — not refresh timing (the
-  published numbers are captioned as PaperMono results), not power, not battery
-  life. This is the same gap the PaperMono has, compounded.
-- **No product or teardown photograph** is held. The vendor's imagery is not
-  licensed for redistribution and no independent teardown existed at the snapshot
-  date.
-- **The 2.3 g delta is the only quantitative evidence** that the radio hardware is
-  genuinely absent rather than depopulated. It is good evidence and it is not
-  proof.
-- **No certification identifier** exists for this SKU (S11). Less consequential
-  than for the PaperMono, since the Lite ships no radio beyond the ESP32-S3's own
-  2.4 GHz — but still unpublished.
-
-## Related
-
-- [PaperMono (C153)](../papermono/README.md) — **the full record; read it first**
-- [PaperMono sources](../papermono/sources.md) · [research log](../papermono/research-log.md) · [command ledger](../papermono/commands.md)
-- [Devices index](../../README.md) · [Components index](../../../components/README.md)
diff --git a/devices/m5stack/papermono/README.md b/devices/m5stack/papermono/README.md
deleted file mode 100644
index 6fbd761..0000000
--- a/devices/m5stack/papermono/README.md
+++ /dev/null
@@ -1,395 +0,0 @@
-# M5Stack PaperMono
-
-> **SKU C153** · schematic revision **V0.6.2** (file dated 2026-05-22) ·
-> announced and on sale **2026-08-21** · documentation published 2026-08-20 ·
-> current at research snapshot **2026-09-01**, at which point the product was
-> **out of stock at the official store**.
-> Sibling variant: [PaperMono-Lite](../papermono-lite/README.md) (SKU C153-LITE).
-
-An ESP32-S3 development board built around a 3.97-inch touch e-paper panel with
-an integrated frontlight, a five-state hardware power manager, NFC and LoRa. It
-is best understood as a battery-first low-power platform that happens to have a
-display, rather than an e-paper display board that happens to have a battery.
-
-## Contents
-
-| Document | What is in it |
-|---|---|
-| [**`features/`**](features/README.md) | **Task-oriented guides — one per fitted capability. Start here to build something** |
-| [`pinouts-and-buses.md`](pinouts-and-buses.md) | Complete ESP32-S3 pin map, I²C/SPI buses, expander pins, connectors, boot behaviour |
-| [`power-architecture.md`](power-architecture.md) | The five power states, every rail and its enable, charging, frontlight, wake sources |
-| [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md) | Why `PYG3` means two different pins, and how to avoid the resulting hazard |
-| [`development.md`](development.md) | Frameworks and exact versions, board target, the verbatim PlatformIO block, libraries, build/flash/monitor, port selection, restore offsets — and the **bricking and bootstrapping risks** |
-| [`factory-firmware.md`](factory-firmware.md) | Both shipped images parsed: headers, partition maps, build metadata, notable strings, what the device does on power-up, and why the official image is **not reproducible** |
-| [`resources-and-conflicts.md`](resources-and-conflicts.md) | Every GPIO, bus, address, SPI host, partition and rail — and what breaks when features run together |
-| [`coverage.md`](coverage.md) | Every capability mapped to hardware, docs, examples and test status |
-| [`compatibility-and-status.md`](compatibility-and-status.md) | Working / partial / failing / untested, keyed by hardware and library version |
-| [`performance.md`](performance.md) | The vendor's four refresh timings, the panel's optical and electrical figures, ESP32-S3 silicon claims — and the **inventory of everything nobody has measured** |
-| [`product-history-and-family.md`](product-history-and-family.md) | The dated timeline with its evidence row by row, the M5Paper lineage, and why **PaperMono is not a successor to the PaperS3** |
-| [`market-and-pricing.md`](market-and-pricing.md) | Launch and current pricing kept separate, every observation dated with seller, tax, stock and source; the confirmed-not-sold and no-determination lists |
-| [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) | Competitors and substitutes by workload and price tier, launch-era vs current fit, use / do-not-use guidance, alternatives by tier |
-| [`community.md`](community.md) | Every coverage item by medium and **evidence type**; the claims that failed checking, and the ones that survived |
-| [`media.md`](media.md) · [`media/manifest.json`](media/manifest.json) | Visual identification: what was sought, why **no imagery is retained**, and exactly what a future pass should capture |
-| [**`examples/`**](examples/best.md) | The 43-project population with **every repository pinned to a commit**, the selected portfolio, and the search log |
-| [`projects-and-community.md`](projects-and-community.md) | Third-party firmware and software targeting this board, classified by whether it was actually demonstrated on hardware |
-| [`bill-of-materials.md`](bill-of-materials.md) | The full designator census from the schematic — 290 placed components, 230 designators, and what the gaps mean |
-| [`gaps-and-conflicts.md`](gaps-and-conflicts.md) | Every recorded contradiction and open question |
-| [`sources.md`](sources.md) | Source table with classes, retrieval dates and versions |
-| [`research-log.md`](research-log.md) | Every service, query, filter and disposition; retrieval findings; the stopping criterion |
-| [`commands.md`](commands.md) | Command ledger — every command with its tool version and execution status |
-
-Vendor documentation-sourcing guides produced by this pass:
-[`vendors/m5stack`](../../../vendors/m5stack/README.md) ·
-[`vendors/dke`](../../../vendors/dke/README.md).
-
-## Identity and variants
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | PaperMono | vendor product page |
-| SKU | C153 | vendor product page, store listing |
-| Manufacturer | M5Stack Technology Co., Ltd (Shenzhen) | vendor site |
-| Schematic revision | V0.6.2, dated 2026-05-22 | schematic filename and title blocks |
-| Sub-board revisions | KEY/RGB sheet dated 2026-04-14; NFC sheet rev V0.2 dated 2026-07-28 | schematic title blocks |
-| Case colour | Grey | vendor comparison table |
-| Variant | PaperMono-Lite, SKU C153-LITE, white case, no NFC, no LoRa | vendor comparison table |
-
-There is exactly one hardware revision in evidence. No regional variants were
-found, and no FCC/CE/TELEC identifier appears anywhere on M5Stack's site —
-`/en/certification` returns zero matches for both `PaperMono` and `C153`. That
-is a verified negative, not a failed search.
-
-**Do not read PaperMono as a successor to the M5PaperS3.** See
-[product history](#product-history-family-and-culture).
-
-## What it is and visual identification
-
-A closed handheld slab, 62.0 × 101.0 × 8.0 mm, 74.7 g, with the e-paper panel
-occupying most of the front face, a USB-C port, two user buttons plus a power
-button, and a side RGB indicator. There is **no expansion connector** — no
-Grove port, no M-Bus — which is unusual for an M5Stack core and materially
-limits what can be added to it.
-
-Internally it is **three PCBs plus three flexible assemblies**: a main board, a
-KEY/RGB/microphone sub-board, an NFC sub-board, and FPC connections to the
-e-paper panel, the touch layer and the frontlight, with the LoRa radio on a
-plug-in `Stamp-LoRa-1262-mini` module. See
-[`pinouts-and-buses.md`](pinouts-and-buses.md#board-set--this-is-not-one-pcb).
-
-> **Images: an explicit gap.** No product, teardown or PCB photograph has been
-> retained in this record. The vendor's product imagery is not licensed for
-> redistribution and no independent teardown existed at the snapshot date. The
-> only visual hardware evidence held here is the vendor schematic and the
-> mechanical drawing. Recorded rather than filled with unattributed images.
-
-## Product history, family and culture
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2026-04-14 | KEY/RGB sub-board schematic dated | schematic title block |
-| 2026-05-22 | Main schematic V0.6.2 dated | schematic filename |
-| 2026-06-08 | Schematic PDF created | PDF metadata |
-| 2026-07-28 | NFC sub-board schematic V0.2 dated; schematic PDF last modified | title block, PDF metadata |
-| 2026-08-06 | Factory firmware image built | `esp_app_desc_t` in the shipped binary |
-| 2026-08-10 | UserDemo repository HEAD commit | `c1099107…` |
-| 2026-08-18 | Store record created | Shopify metadata |
-| 2026-08-20 | Documentation published under "Controllers" | vendor release history |
-| 2026-08-21 | Store published; vendor blog announcement; first independent sell-out report nine minutes later | store metadata, community |
-| 2026-08-29 | First hands-on video published | community |
-
-The M5Paper line: **M5Paper** (ESP32, 4.7" IT8951), **M5PaperS3** (ESP32-S3,
-4.7", 16 grey levels, 1800 mAh, expansion port — now end-of-life), then
-**PaperMono** and **PaperMono-Lite**. Relative to the PaperS3 the PaperMono has
-**about 35 % fewer pixels, 4 grey levels instead of 16, a smaller battery and no
-expansion port**, while adding a frontlight, NFC, LoRa and the M5PM1 power
-system. It is a repositioning, not an upgrade, and describing it as a successor —
-as several launch articles did — is not supported by the vendor's own
-specifications.
-
-## Key specifications
-
-| Specification | Value | Component record |
-|---|---|---|
-| SoC | ESP32-S3R8, Xtensa LX7 dual-core @ 240 MHz, bare die in 56-pin QFN | [esp32-s3r8](../../../components/espressif/esp32-s3r8/README.md) |
-| Flash | 16 MB external SPI NOR (`XM25UH128DHIQT`), quad-capable | [xm25uh128dhiqt](../../../components/xmc/xm25uh128dhiqt/README.md) |
-| PSRAM | 8 MB octal, in package — **mandatory in the build config** | [esp32-s3r8](../../../components/espressif/esp32-s3r8/README.md) |
-| Wireless | 2.4 GHz Wi-Fi + Bluetooth LE (ESP32-S3 radio) | — |
-| Display | 3.97" e-paper, 480 × 800, 235 DPI, 4-level greyscale, DKE `DEPG0397BBS770F3` | [depg0397bbs770f3](../../../components/dke/depg0397bbs770f3/README.md) |
-| Display controller | Solomon Systech SSD1677, 4-wire SPI | [ssd1677](../../../components/solomon-systech/ssd1677/README.md) |
-| Frontlight | AW9967 boost, 15 V rail, PWM dimmed from the M5PM1 | [aw9967](../../../components/awinic/aw9967/README.md) |
-| Touch | FocalTech FT6336G, I²C `0x38` | [ft6336g](../../../components/focaltech/ft6336g/README.md) |
-| Power management | M5PM1, I²C `0x6E` — a `PY32L020F15U6` running M5Stack firmware | [m5pm1](../../../components/m5stack/m5pm1/README.md) |
-| I/O expander | M5IOE1, I²C `0x4F` — same silicon | [m5ioe1](../../../components/m5stack/m5ioe1/README.md) |
-| IMU | Bosch BMI270, I²C `0x68` | [bmi270](../../../components/bosch-sensortec/bmi270/README.md) |
-| RTC | Seiko Epson RX8130CE, I²C `0x32` | [rx8130ce](../../../components/seiko-epson/rx8130ce/README.md) |
-| NFC | ST ST25R3916, I²C `0x50` — ISO14443A/B, FeliCa, ISO15693 | [st25r3916](../../../components/stmicroelectronics/st25r3916/README.md) |
-| LoRa | `Stamp LoRa-1262` module (Semtech SX1262), 868–923 MHz, FPC antenna | [stamp-lora-1262](../../../components/m5stack/stamp-lora-1262/README.md) |
-| Charger | Injoinic IP2315, I²C `0x75` — **gated off the bus by default** | [ip2315](../../../components/injoinic/ip2315/README.md) |
-| Storage | microSD, 4-bit SDMMC on GPIO8–13 | — |
-| Audio | PDM microphone `LMD4737T261-AC02`; buzzer on GPIO42 | [mic](../../../components/generic/lmd4737t261-ac02-pdm-microphone/README.md) |
-| Battery | 1150 mAh Li-ion; 2-wire connector. Thermistor `R15` is on the **mainboard**, not in the pack | [cell](../../../components/generic/papermono-1150mah-liion-cell/README.md) |
-| Buttons | 2 user + 1 power (on / off / reset / boot) | — |
-| Size / weight | 62.0 × 101.0 × 8.0 mm, 74.7 g | vendor |
-
-Two specifications are worth qualifying rather than repeating. **"4-level
-greyscale"** is M5Stack's claim and the vendor OTP demo does implement a working
-four-grey mode, but the DKE panel manual's own optical table reads
-`GN — 2Grey Level`; the contradiction is unresolved and recorded. **Bluetooth**
-is a capability of the ESP32-S3 silicon, not something M5Stack lists in the
-PaperMono specification table — one launch article's "Bluetooth 5.0 LE + Mesh"
-line is that publication's inference, not a vendor spec.
-
-## Architecture and components
-
-```
-                 ┌──────────────┐
-   USB-C ──▶ OVP │  IP2315      │──▶ battery 1150 mAh
-   5.95 V        │  charger     │      │
-                 └──────┬───────┘      │
-                    I²C │ (gated)      ▼
-                        │         VBUS_L0 / VBAT_L0
-                        │              │
-   ┌────────────────────┴──────────────┴────────────────────┐
-   │  M5PM1  (PY32L020F15U6)   I²C 0x6E   ── owns L0..L2     │
-   │  reset + boot straps + rail enables + wake logic        │
-   └───┬────────────────────────────────────────────────────┘
-       │ SOC_RESET, BOOT_OUT
-       ▼
-   ┌───────────────┐   SPI2   ┌──────────┐   FPC   ┌──────────────┐
-   │  ESP32-S3R8   │─────────▶│ SSD1677  │────────▶│ DKE 3.97" EPD│
-   │  16 MB flash  │          └──────────┘         └──────────────┘
-   │  8 MB OPI RAM │   SPI1   ┌──────────────────┐
-   │               │─────────▶│ Stamp LoRa-1262  │
-   │               │  SDMMC   ┌──────────┐
-   │               │─────────▶│ microSD  │
-   └───┬───────────┘          └──────────┘
-       │ I²C  GPIO47/48  (one bus, seven devices)
-       ├── 0x32 RX8130CE RTC ──── nIRQ ──▶ M5PM1 G0
-       ├── 0x38 FT6336G touch
-       ├── 0x4F M5IOE1 expander ─── 14 pins: panel/touch/SD/mic power,
-       │                             resets, LED, LoRa reset + ant switch
-       ├── 0x50 ST25R3916 NFC
-       ├── 0x68 BMI270 IMU ──────── INT1 ──▶ M5PM1 G4
-       ├── 0x6E M5PM1
-       └── 0x75 IP2315   (behind a level translator, normally disconnected)
-```
-
-The defining structural fact is that **two auxiliary microcontrollers sit
-between the application processor and most of the board.** Panel power, panel
-reset, touch power and reset, microSD power and detect, microphone power, NFC
-enable, LoRa reset and antenna switch, two of three LED colours, and the
-charger's bus access are all behind the M5IOE1. Reset, boot mode, rail enables
-and every deep wake source are behind the M5PM1. Neither is optional.
-
-## Common tasks / How do I…?
-
-Every fitted capability has a task-oriented guide under
-[**`features/`**](features/README.md). **Nothing in them was tested on hardware** — see
-[Known gaps](#known-gaps).
-
-| Task | Guide |
-|---|---|
-| Drive the e-paper reliably (and not damage it) | [`features/epaper-display.md`](features/epaper-display.md) |
-| Set frontlight brightness | [`features/frontlight.md`](features/frontlight.md) |
-| Read touch input | [`features/touch.md`](features/touch.md) |
-| Read the buttons, drive the RGB indicator | [`features/buttons-and-rgb-led.md`](features/buttons-and-rgb-led.md) |
-| Put the device to sleep and wake it | [`features/power-and-sleep.md`](features/power-and-sleep.md) |
-| Read the battery, control charging | [`features/battery-and-charging.md`](features/battery-and-charging.md) |
-| Get on Wi-Fi, use BLE | [`features/wifi-and-bluetooth.md`](features/wifi-and-bluetooth.md) |
-| Send and receive LoRa | [`features/lora.md`](features/lora.md) |
-| Set up NFC | [`features/nfc.md`](features/nfc.md) |
-| Read motion, wake on it | [`features/imu.md`](features/imu.md) |
-| Keep time, schedule a wake-up | [`features/rtc.md`](features/rtc.md) |
-| Mount a microSD card | [`features/microsd.md`](features/microsd.md) |
-| Record audio | [`features/microphone.md`](features/microphone.md) |
-| Make a noise | [`features/buzzer.md`](features/buzzer.md) |
-| Flash it, get a serial console | [`features/usb-and-serial.md`](features/usb-and-serial.md) |
-| Use the I/O expander safely | [`features/io-expander.md`](features/io-expander.md) |
-| Understand which GPIO does what | [`pinouts-and-buses.md`](pinouts-and-buses.md) |
-| Avoid the `PYG3` pin-naming hazard | [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md) |
-| Work out what conflicts with what | [`resources-and-conflicts.md`](resources-and-conflicts.md) |
-| Check whether something is known to work | [`compatibility-and-status.md`](compatibility-and-status.md) |
-| Find M5Stack's documentation for another product | [`vendors/m5stack`](../../../vendors/m5stack/README.md) |
-
-## Development
-
-- **Frameworks**: Arduino (arduino-esp32 3.3.10) and ESP-IDF **5.5.1**. UiFlow2
-  is advertised, but the UiFlow2 page states no required firmware version, no
-  block list and no limitations — a genuine documentation gap, confirmed by
-  full-text search rather than assumed.
-- **Libraries**: `M5Unified`, `M5GFX`, `M5PM1`, `M5IOE1`, `M5Unit-NFC`,
-  `RadioLib` 7.2.1.
-- **The vendor's `M5Unified#develop` requirement is stale.** `board_M5PaperMono`
-  is byte-identical on `master` and `develop` and ships in released tags
-  M5Unified 0.2.21 and M5GFX 0.2.28.
-- **Octal PSRAM is mandatory** (`board_build.arduino.memory_type = qio_opi`).
-  Without it M5GFX aborts display init with `"M5PaperMono need OPI-PSRAM
-  enabled"` and you get a blank screen on working hardware.
-- **Partitions**: single `factory` app at offset `0xF00000`, ~15 MB, **no OTA
-  slot** in either vendor project.
-- **Download mode**: hold the power button ~2 s until the red LED blinks.
-- **E-paper waveforms**: M5Stack's own note says the M5GFX waveforms "are
-  currently unstable" and recommends the panel maker's OTP waveform example
-  instead. This is corroborated in-tree — M5GFX `develop` has replaced the LUTs,
-  leaving the previous `lut_quality` commented out. Do roughly one full refresh
-  per ten partial refreshes, and never run continuous partial refreshes: the
-  vendor warns of irreversible DC-imbalance damage.
-
-## Factory firmware
-
-Two images were retrieved from the M5Burner API and validated by content
-(ESP32 image magic `0xE9`), held in [`artifacts/firmware/`](artifacts/firmware/):
-
-| Image | Bytes | SHA-256 | Build identity |
-|---|---|---|---|
-| `C153-PaperMono-UserDemo-v1.2.bin` | 2,868,208 | `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | `PaperMono-UserDemo`, version **`c78f6c5-dirty`**, IDF v5.5.1, 2026-08-06 |
-| `crosspoint-paper-mono-cjk-1.5.0-RC.bin` | 10,319,500 | `e2dee32b468da1d743b9fe8889eca959f5c0acdbe09c8f4cc3e69c69f8ebe935` | `crosspoint-reader-mono`, `paper-mono-v2-15-g87a191f`, IDF 5.5.2 — third-party e-reader |
-
-The official image reports **`-dirty`**: it was built from an uncommitted tree
-and is therefore **not reproducible from any published commit**. That is why the
-binaries are retained here rather than referenced. Source for the demo is at
-`m5stack/M5PaperMono-UserDemo` (HEAD `c1099107271d31a0678d661a896e2b04dbb331ea`,
-2026-08-10), but it will not reproduce these bytes.
-
-The vendor link labelled "PaperMono Factory Reset Firmware" resolves to a
-firmware record named "PaperMono UserDemo" — the same image, differently
-labelled.
-
-## Pricing and availability
-
-All observations dated **2026-09-01**. Not currency-converted: three VAT regimes,
-not comparable.
-
-| Seller | SKU | Price | Stock |
-|---|---|---|---|
-| shop.m5stack.com | C153 | **USD 65.00** | out of stock |
-| shop.m5stack.com | C153-LITE | **USD 55.00** | out of stock |
-| thepihut.com | C153 | GBP 62.40 incl. VAT | out of stock |
-| openelab.io / .de | M5-C153 | EUR 79.95 | listed available, title says "Pre-sale" |
-
-The NFC + LoRa hardware is the entire USD 10 difference between the two SKUs.
-Confirmed **not** sold by Amazon, AliExpress, Switch Science, Adafruit,
-Reichelt, Botland or Core Electronics. Mouser, DigiKey and TinyTronics were
-bot-walled and returned no determination — an explicit gap, not a negative.
-
-It sold out within minutes of the store opening and had not restocked eleven
-days later. The vendor said "two or three months" on 2026-08-22; one publication
-reported "next year". Both are recorded; they conflict. A widely repeated claim
-that the delay is due to an e-ink driver IC shortage was **checked against the
-cited post and its full reply chain and does not appear there** — it is hearsay.
-
-## Community, editorial and project coverage
-
-Eleven days after launch: **zero written reviews, one hands-on video** (Volos
-Projects, 2026-08-29, carrying a vendor affiliate link and self-described as a
-first look). Everything written — LinuxGizmos, CNX-Software, Liliputing,
-MuyLinux, Tux Machines — traces back to a single vendor blog post and is
-reproduced marketing copy. Hackaday published nothing. Two independent broad
-search passes reached the same conclusion.
-
-The real early signal is code rather than articles: four third-party GitHub
-projects appeared within eleven days, two with credible hardware validation
-(`MagicCube/free-ink-on-paper-mono` and `Free-Ink/freeink-sdk`), independently
-corroborating an M5PM1 single-click-reset behaviour.
-
-One widely repeated factual error worth flagging: a launch article stated the
-USD 55 model has NFC and LoRa. It does not — that is the Lite.
-
-## Distinctive strengths
-
-- A genuine hardware low-power architecture, not a sleep mode: five states, wake
-  on RTC/motion/touch/keys with the application processor unpowered.
-- Frontlit e-paper with touch at this size and price is uncommon.
-- NFC and LoRa on the same board as an e-paper reader is, as far as this survey
-  found, unique in the class.
-- Complete published schematic, and vendor datasheets for both custom chips —
-  better hardware disclosure than most comparable products.
-
-## Shortcomings and constraints
-
-- **No expansion connector at all.** Every GPIO is committed; anything added has
-  to share the I²C bus.
-- Vendor acknowledges its own display waveforms are unstable and recommends
-  bypassing its graphics library for refresh configuration.
-- Two auxiliary MCUs mean two more firmware surfaces, two more documentation
-  sets, and a naming ambiguity that can silently cut panel power.
-- 4 grey levels and 480 × 800 are a step down from the PaperS3 it sits beside.
-- No OTA partition in either vendor project.
-- No certification identifiers published.
-- Out of stock since launch day with conflicting restock guidance.
-- Official firmware not reproducible from published source.
-
-## When to use / when not to use
-
-**Use it** for battery-powered, long-idle, event-driven applications — access
-control and identity terminals, e-paper signage with LoRa telemetry, sensor
-displays that wake on motion or schedule — where the power architecture is the
-point and the display is a low-duty output.
-
-**Do not use it** where you need a fast or high-fidelity e-paper display
-(4 grey levels, and the vendor's own refresh guidance is conservative), where
-you need to attach external hardware (no expansion port), where you need field
-updates (no OTA partition as shipped), or where you need regulatory paperwork
-(none published). For a general e-paper development board with expansion, prefer
-Inkplate or the [Waveshare ESP32-S3-ePaper-3.97](../../waveshare/esp32-s3-epaper-3.97/README.md)
-(same SoC, memory and panel size, with headers and an audio path instead of
-radios); for a reading device, this is a
-development board, not a reader.
-
-## Known gaps
-
-This is a **broad-coverage snapshot dated 2026-09-01**, not a claim of
-completeness. Not done in this pass, and honestly outstanding:
-
-- [`performance.md`](performance.md) — **now written, and its content is mostly absence**:
-  no current in any power state, no battery runtime, no Wi-Fi/SD/LoRa throughput, and the
-  vendor's four refresh timings are lab figures for a LUT set that may no longer be the
-  shipped one. The page inventories every missing measurement rather than inventing any
-- `examples/` catalogue — the vendor and third-party examples are referenced by upstream
-  URL and commit in [`coverage.md`](coverage.md), but none is vendored here
-- Acquisition manifest and downloader — **present** at
-  [`acquisition/`](acquisition/README.md); note its artifact IDs (`S10`, `S11`, `S30`, `S31`, …)
-  predate the renumbering in [`sources.md`](sources.md) (`S14`, `S15`, `S38`, `S39`, …) and
-  have not been reconciled. Hashes, sizes and URLs agree in both
-- **No product or teardown imagery retained** — recorded, with the reasons and a work list,
-  in [`media.md`](media.md) and [`media/manifest.json`](media/manifest.json)
-- Component records for `stmicroelectronics/st25r3916` and `seiko-epson/rx8130ce` are
-  **stubs** — the datasheet artifacts are held, the write-ups are not done
-- Nothing verified on physical hardware: **every behavioural claim in this
-  record — including in every `features/` guide — is `inferred`, `reported-working` or
-  read from source, never `executed-success` against a device**
-
-Written in this pass: [`features/`](features/README.md) (16 guides),
-[`coverage.md`](coverage.md), [`resources-and-conflicts.md`](resources-and-conflicts.md),
-[`compatibility-and-status.md`](compatibility-and-status.md), and the vendor guides
-[`vendors/m5stack`](../../../vendors/m5stack/README.md) and
-[`vendors/dke`](../../../vendors/dke/README.md).
-
-Added subsequently, on the same 2026-09-01 evidence base and with nothing new retrieved:
-[`development.md`](development.md), [`factory-firmware.md`](factory-firmware.md),
-[`product-history-and-family.md`](product-history-and-family.md),
-[`market-and-pricing.md`](market-and-pricing.md),
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md),
-[`community.md`](community.md), [`performance.md`](performance.md),
-[`media.md`](media.md) and [`media/manifest.json`](media/manifest.json).
-
-See [`gaps-and-conflicts.md`](gaps-and-conflicts.md) for the full conflict list.
-
-## Artifact layout
-
-```
-artifacts/
-├── schematic/PaperMono_SCH_V0.6.2_20260522.pdf      1,462,039 B  6 sheets, Altium
-├── mechanical/C153_PaperMono_model_size.pdf            21,346 B
-└── firmware/
-    ├── C153-PaperMono-UserDemo-v1.2.bin            2,868,208 B
-    ├── crosspoint-paper-mono-cjk-1.5.0-RC.bin     10,319,500 B
-    └── esp-image-analysis.txt
-```
-
-Component-owned documents are filed under the component they describe, not here:
-the DKE panel manual, the SSD1677, M5PM1, M5IOE1, ST25R3916, SX1262, RX8130CE,
-BMI270 and ESP32-S3 datasheets each live in their own component record's
-`artifacts/`. Several are M5Stack mirrors of other vendors' documents and are
-named and labelled as such, because the revision M5Stack serves is not always
-the current one — the BMI270 mirror is five years behind Bosch's.
diff --git a/devices/m5stack/papermono/acquisition/README.md b/devices/m5stack/papermono/acquisition/README.md
deleted file mode 100644
index 0a25e61..0000000
--- a/devices/m5stack/papermono/acquisition/README.md
+++ /dev/null
@@ -1,112 +0,0 @@
-# PaperMono — acquisition
-
-How to reconstruct every artifact for this device record from a clean clone.
-Manifest: [`manifest.json`](manifest.json) · Downloader: [`fetch.py`](fetch.py)
-
-All retrieval dates are **2026-09-01**. Nothing here was flashed to or measured
-on physical hardware.
-
-## Quick start
-
-```bash
-cd devices/m5stack/papermono/acquisition
-python3 fetch.py --verify-only     # CI / post-clone check; downloads nothing
-python3 fetch.py                   # fetch anything missing (disposition=repository)
-python3 fetch.py --reference-only  # also attempt reference-only entries
-```
-
-`fetch.py` is standard library only. It validates HTTP status, magic bytes,
-byte size **and** SHA-256 before installing atomically, is idempotent, and never
-stages or commits. Verified passing for all 14 repository artifacts on
-2026-09-01.
-
-## Where things live
-
-Artifacts are filed under the component they **describe**, not under this
-device. The manifest's `owned_by` field names that owner. This manifest lives
-here because the PaperMono research is what caused the fetch.
-
-| Count | Disposition |
-|---|---|
-| 14 | `repository` — present in the tree, hashed, verified |
-| 10 | `reference-only` — 7 GitHub repositories, 3 unobtainable datasheets |
-
-| Count | Reacquisition |
-|---|---|
-| 21 | `automatic` |
-| 3 | `lost` |
-
-## Execution order for a clean clone
-
-1. **Device artifacts** — schematic and mechanical PDFs from
-   `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/`. `automatic`.
-2. **Firmware** — via the M5Burner API (see trap below). `automatic`.
-3. **Component datasheets** — nine files, each into its owning component's
-   `artifacts/`. `automatic`, except ST which needs a specific user agent.
-4. **Source repositories** — not vendored; clone at the pinned commits below.
-5. **Unobtainable** — three parts, recorded as `lost` with their search ledgers.
-
-## Source repositories (not vendored, pinned)
-
-```bash
-git clone https://github.com/m5stack/M5PaperMono-UserDemo && git -C M5PaperMono-UserDemo checkout c1099107271d31a0678d661a896e2b04dbb331ea
-git clone https://github.com/m5stack/M5PaperMono-OTP-Demo  && git -C M5PaperMono-OTP-Demo  checkout c7c02554f89fd06f80d988b805b2a59050c78a46
-git clone https://github.com/m5stack/M5PM1                 && git -C M5PM1                 checkout be9a5456c007c333e7ac963f33bfde1ffa5d82ee
-git clone https://github.com/m5stack/M5IOE1                && git -C M5IOE1                checkout 846eec7d05e25c09013be2acdb8804487f48a62e
-git clone https://github.com/m5stack/M5_Hardware           && git -C M5_Hardware           checkout a240115c94b19ecf647f229c47fa9a8ce46ccdc4
-git clone https://github.com/m5stack/M5Unified             # master 8530f53
-git clone https://github.com/m5stack/M5GFX                 # master d91077b
-```
-
-All seven are MIT; retain their `LICENSE` files with any vendored copy.
-`M5_Hardware` is listed because its **absence of a C153 entry is the finding** —
-verified at that commit, dated 2026-08-17.
-
-## Retrieval traps that will bite a re-runner
-
-| Host | Trap | Workaround |
-|---|---|---|
-| `st.com` | Chrome 131 and ClaudeBot UAs get a TLS stream reset | use UA `WhatsApp/2.23.20.0` |
-| `datasheet.lcsc.com` | returns **HTTP 200 with `text/html`** for PDF URLs | check `%PDF` magic bytes, never the status code |
-| `burner.m5stack.com` | `/api/firmwares/{id}` returns `401 请先登录` | `/api/v1/firmwares/{id}` is public; `/versions/{vid}/download` 302s to a CDN object named by a **numeric id**, not the `binFileName` the API reports |
-| `semtech.com` | canonical datasheet is behind a Salesforce JS/POST shell | **`blocked`** — three strategies failed; the M5Stack mirror is what is held |
-| `support.epson.biz` | serves the **English** manual under a `_cn` filename | `_cn` = Epson's China site, not Chinese language |
-| `api.github.com` | 60 requests/hour unauthenticated; 403s look like bot-blocking | authenticate (`gh auth token`); check `X-RateLimit-Remaining` before rotating UAs |
-
-`fetch.py` refuses to write a non-matching body under a `.pdf` or `.bin`
-extension, so an error page cannot be silently saved as a datasheet.
-
-## Reacquisition marked `lost`
-
-No datasheet could be located for `CN4040M000157A530001` (40 MHz crystal),
-`LMD4737T261-AC02` (PDM microphone) or `RS-C1415MBAR` (RGB LED), across 11+
-services. For the latter two the only occurrences anywhere on the public web are
-M5Stack's own pages. Instructions are not omitted — there are none. The search
-ledgers are in the component records and in
-[`../research-log.md`](../research-log.md).
-
-## Licence decision needing user review
-
-Both Epson RX8130CE manuals carry an **explicit no-redistribution notice** and
-are marked `redistribution: restricted` while being **held in the repository**.
-They were retained because the diff between revisions is itself a finding
-(`ETM50E-10` *deletes* items (1)–(7) of §14.4.2, so the older mirror carries more
-text; all registers, thresholds and timings are identical). This is flagged for a
-decision rather than silently resolved either way.
-
-Everything else is `unknown` (the normal case for vendor datasheets) or MIT
-(the repositories).
-
-## Firmware notes
-
-Both images are ESP32 images (magic `0xE9`), validated by content before being
-given a `.bin` extension.
-
-The official `C153-PaperMono-UserDemo-v1.2.bin` reports version
-**`c78f6c5-dirty`** — built from an uncommitted tree, therefore **not
-reproducible from any published commit**. That is why the bytes are retained
-here rather than merely referenced.
-
-Flashing commands in the manifest are marked **`inferred`, not verified**. No
-device was flashed in this pass. Prefer M5Burner over a hand-rolled
-`esptool.py` invocation.
diff --git a/devices/m5stack/papermono/acquisition/fetch.py b/devices/m5stack/papermono/acquisition/fetch.py
deleted file mode 100755
index 1e36c48..0000000
--- a/devices/m5stack/papermono/acquisition/fetch.py
+++ /dev/null
@@ -1,139 +0,0 @@
-#!/usr/bin/env python3
-"""Acquisition downloader for the M5Stack PaperMono record.
-
-Driven only by ``manifest.json`` beside this file. Standard library only.
-
-Contract (see .agents/skills/hardware-device-research/SKILL.md):
-  * fetches ``repository`` entries by default; ``reference-only`` needs --reference-only
-  * never changes a recorded disposition
-  * refuses redirects to non-http(s) schemes
-  * downloads to a temp file, validates status / magic / size / SHA-256,
-    and only then installs atomically
-  * idempotent: verifies an existing file before skipping it
-  * prints acquired / cached / skipped / failed
-  * --verify-only checks what is already on disk and downloads nothing
-  * never stages or commits anything
-
-Several of these hosts filter automated clients. The escalation ladder that was
-observed to work on 2026-09-01, in order:
-    (1) the default UA below
-    (2) Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
-        (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
-    (3) WhatsApp/2.23.20.0        <- required by ST (st.com); Chrome and
-                                    ClaudeBot get a TLS stream reset
-Known traps: datasheet.lcsc.com returns HTTP 200 with text/html for PDF URLs,
-so magic bytes are checked rather than status; burner.m5stack.com/api/v1/... is
-public while /api/... returns 401; Semtech's canonical download is behind a
-Salesforce JS/POST shell and is recorded 'blocked' rather than fetched.
-"""
-
-import argparse, hashlib, json, os, shutil, sys, tempfile, urllib.error, urllib.request
-
-HERE = os.path.dirname(os.path.abspath(__file__))
-ROOT = os.path.abspath(os.path.join(HERE, "..", "..", "..", ".."))
-UA = ("Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 "
-      "(KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36")
-MAGIC = {".pdf": b"%PDF-", ".bin": b"\xe9"}
-
-
-def expected_magic(path):
-    return MAGIC.get(os.path.splitext(path)[1].lower())
-
-
-def check(path, entry):
-    """Return (ok, reason) for a file already on disk."""
-    if not os.path.exists(path):
-        return False, "absent"
-    blob = open(path, "rb").read()
-    magic = expected_magic(path)
-    if magic and not blob.startswith(magic):
-        return False, f"magic mismatch (expected {magic!r}, got {blob[:5]!r})"
-    if entry.get("bytes") is not None and len(blob) != entry["bytes"]:
-        return False, f"size {len(blob)} != expected {entry['bytes']}"
-    if entry.get("sha256"):
-        got = hashlib.sha256(blob).hexdigest()
-        if got != entry["sha256"]:
-            return False, f"sha256 {got[:16]}… != expected {entry['sha256'][:16]}…"
-    return True, "verified"
-
-
-def fetch(url, dest, entry):
-    req = urllib.request.Request(url, headers={"User-Agent": UA})
-    with urllib.request.urlopen(req, timeout=120) as resp:
-        if resp.status != 200:
-            raise OSError(f"HTTP {resp.status}")
-        if not resp.geturl().startswith(("http://", "https://")):
-            raise OSError(f"refusing redirect to unsupported scheme: {resp.geturl()}")
-        blob = resp.read()
-    magic = expected_magic(dest)
-    if magic and not blob.startswith(magic):
-        # This is the LCSC / vendor-portal failure: HTTP 200 with an HTML body.
-        raise OSError(f"content is not {magic!r} — refusing to save an error page "
-                      f"under this extension (first bytes {blob[:16]!r})")
-    if entry.get("bytes") is not None and len(blob) != entry["bytes"]:
-        raise OSError(f"size {len(blob)} != expected {entry['bytes']}")
-    if entry.get("sha256"):
-        got = hashlib.sha256(blob).hexdigest()
-        if got != entry["sha256"]:
-            raise OSError(f"sha256 {got} != expected {entry['sha256']}")
-    os.makedirs(os.path.dirname(dest), exist_ok=True)
-    fd, tmp = tempfile.mkstemp(dir=os.path.dirname(dest))
-    with os.fdopen(fd, "wb") as fh:
-        fh.write(blob)
-    os.replace(tmp, dest)          # atomic install, only after validation
-    return len(blob)
-
-
-def main():
-    ap = argparse.ArgumentParser(description=__doc__,
-                                 formatter_class=argparse.RawDescriptionHelpFormatter)
-    ap.add_argument("--verify-only", action="store_true",
-                    help="check files already on disk; download nothing (CI / post-clone)")
-    ap.add_argument("--reference-only", action="store_true",
-                    help="also attempt entries whose disposition is reference-only")
-    ap.add_argument("--manifest", default=os.path.join(HERE, "manifest.json"))
-    args = ap.parse_args()
-
-    man = json.load(open(args.manifest, encoding="utf-8"))
-    tally = {"acquired": [], "cached": [], "skipped": [], "failed": []}
-
-    for e in man["artifacts"]:
-        dest_rel, eid = e.get("destination"), e["id"]
-        if not dest_rel:
-            tally["skipped"].append(f"{eid} no destination ({e['reacquisition']})")
-            continue
-        if e["disposition"] != "repository" and not args.reference_only:
-            tally["skipped"].append(f"{eid} {dest_rel} (disposition={e['disposition']})")
-            continue
-        dest = os.path.join(ROOT, dest_rel)
-        ok, why = check(dest, e)
-        if ok:
-            tally["cached"].append(f"{eid} {dest_rel}")
-            continue
-        if args.verify_only:
-            tally["failed"].append(f"{eid} {dest_rel}: {why}")
-            continue
-        if e["reacquisition"] in ("lost", "blocked") or not e.get("url"):
-            tally["skipped"].append(f"{eid} {dest_rel} (reacquisition={e['reacquisition']})")
-            continue
-        urls = [e["url"]] + list(e.get("fallback_urls") or [])
-        for url in urls:
-            try:
-                n = fetch(url, dest, e)
-                tally["acquired"].append(f"{eid} {dest_rel} ({n:,} B)")
-                break
-            except (OSError, urllib.error.URLError) as exc:
-                last = f"{url}: {exc}"
-        else:
-            tally["failed"].append(f"{eid} {dest_rel}: {last}")
-
-    for k in ("acquired", "cached", "skipped", "failed"):
-        print(f"\n{k.upper()} ({len(tally[k])})")
-        for line in tally[k]:
-            print("  ", line)
-    print(f"\nThis tool does not stage or commit. Repository root: {ROOT}")
-    return 1 if tally["failed"] else 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())
diff --git a/devices/m5stack/papermono/acquisition/manifest.json b/devices/m5stack/papermono/acquisition/manifest.json
deleted file mode 100644
index 3b3ccd6..0000000
--- a/devices/m5stack/papermono/acquisition/manifest.json
+++ /dev/null
@@ -1,586 +0,0 @@
-{
- "schema": "hardware-doc/acquisition-manifest/1",
- "device": "M5Stack PaperMono (SKU C153)",
- "device_record": "devices/m5stack/papermono",
- "generated": "2026-09-01",
- "hardware_revision": "schematic V0.6.2",
- "note": "Artifacts are filed under the component they DESCRIBE, not under this device. 'owned_by' names that owner; this manifest lives here because this device caused the fetch.",
- "licence_summary": {
-  "restricted": [
-   "S29 - Epson RX8130CE application manual ETM50E-10: explicit no-redistribution notice, retained in-repository. USER REVIEW REQUESTED.",
-   "S24 - Epson ETM50E-09 mirror: same notice applies to the underlying document."
-  ],
-  "unknown": "All other datasheets and both firmware images. This is the normal case and is not a defect.",
-  "allowed": "All seven GitHub repositories are MIT.",
-  "obligations_worth_preserving": "MIT LICENSE files must be retained with any vendored copy of the repositories."
- },
- "artifacts": [
-  {
-   "id": "A01",
-   "source_id": "S14",
-   "kind": "schematic",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/PaperMono_SCH_V0.6.2_20260522.pdf",
-   "fallback_urls": [],
-   "destination": "devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf",
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "V0.6.2",
-   "upstream_date": "2026-05-22 (filename); PDF created 2026-06-08, modified 2026-07-28",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "6 sheets, Altium export. Concatenates 3 separate SchDocs; designators restart per document. NFC document sheet 1/2 is absent.",
-   "bytes": 1462039,
-   "sha256": "b5abecac97cb043a6d1af7a673f2111d40d9254b0b5108635cb924d9b37ad6fa",
-   "magic_ok": true
-  },
-  {
-   "id": "A02",
-   "source_id": "S15",
-   "kind": "mechanical drawing",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/C153_PaperMono_model_size.pdf",
-   "fallback_urls": [],
-   "destination": "devices/m5stack/papermono/artifacts/mechanical/C153_PaperMono_model_size.pdf",
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "unknown",
-   "upstream_date": null,
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": null,
-   "bytes": 21346,
-   "sha256": "b833a3e52594a3175bc131006d41a3eb5662be5936d0b2f25030180033a6703b",
-   "magic_ok": true
-  },
-  {
-   "id": "A03",
-   "source_id": "S38",
-   "kind": "firmware image",
-   "url": "https://burner.m5stack.com/api/v1/firmwares/2089640807996628993/versions/2089640808000823298/download",
-   "fallback_urls": [
-    "https://m5burner-cdn.m5stack.com/community/1/2089640807996628993/2089640808000823298/bin/2089640808000823299.bin"
-   ],
-   "destination": "devices/m5stack/papermono/artifacts/firmware/C153-PaperMono-UserDemo-v1.2.bin",
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "c78f6c5-dirty",
-   "upstream_date": "2026-08-06",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "Official image reports '-dirty': built from an uncommitted tree, therefore NOT reproducible from any published commit. Retained for that reason.",
-   "target_mcu": "ESP32-S3",
-   "app_name": "PaperMono-UserDemo",
-   "idf_version": "esp-idf v5.5.1",
-   "image_role": "merged factory image (esp_app_desc_t at 0x20)",
-   "flash_offset": "0x0 as a merged image; the factory app partition is at 0xF00000",
-   "companion_images": "none required - merged",
-   "flash_command_status": "inferred, NOT verified - no hardware was flashed in this pass",
-   "flash_command": "esptool.py --chip esp32s3 write_flash 0x0 <file>   # inferred; prefer M5Burner",
-   "bytes": 2868208,
-   "sha256": "72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa",
-   "magic_ok": true
-  },
-  {
-   "id": "A04",
-   "source_id": "S39",
-   "kind": "firmware image",
-   "url": "https://burner.m5stack.com/api/v1/firmwares/2091144466157694978/versions/2091144466157694979/download",
-   "fallback_urls": [
-    "https://m5burner-cdn.m5stack.com/community/3966/2091144466157694978/2091144466157694979/bin/2091144466157694980.bin"
-   ],
-   "destination": "devices/m5stack/papermono/artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin",
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "paper-mono-v2-15-g87a191f",
-   "upstream_date": "unknown",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "Third-party CrossPoint e-reader firmware. Partitions: app0 + 4 MB cjkfont + spiffs + coredump.",
-   "target_mcu": "ESP32-S3",
-   "app_name": "crosspoint-reader-mono",
-   "idf_version": "esp-idf 5.5.2.260206",
-   "image_role": "merged factory image (esp_app_desc_t at 0x20)",
-   "flash_offset": "0x0 as a merged image; the factory app partition is at 0xF00000",
-   "companion_images": "none required - merged",
-   "flash_command_status": "inferred, NOT verified - no hardware was flashed in this pass",
-   "flash_command": "esptool.py --chip esp32s3 write_flash 0x0 <file>   # inferred; prefer M5Burner",
-   "bytes": 10319500,
-   "sha256": "e2dee32b468da1d743b9fe8889eca959f5c0acdbe09c8f4cc3e69c69f8ebe935",
-   "magic_ok": true
-  },
-  {
-   "id": "A05",
-   "source_id": "S25",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1207/M5PM1_Datasheet_EN.pdf",
-   "fallback_urls": [],
-   "destination": "components/m5stack/m5pm1/artifacts/m5pm1-chip-user-manual-v1.9-en.pdf",
-   "owned_by": "components/m5stack/m5pm1",
-   "retrieved": "2026-09-01",
-   "upstream_version": "V1.9",
-   "upstream_date": null,
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "M5Stack custom chip; publisher Shenzhen Mingzhan Information Technology Co., Ltd",
-   "bytes": 814731,
-   "sha256": "c6daffd0ab89d8de50c0a19f35f94321bc6c9511ad017dd242a3e765d88a96b6",
-   "magic_ok": true
-  },
-  {
-   "id": "A06",
-   "source_id": "S26",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1210/IO_Expander_Datasheet_EN.pdf",
-   "fallback_urls": [],
-   "destination": "components/m5stack/m5ioe1/artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf",
-   "owned_by": "components/m5stack/m5ioe1",
-   "retrieved": "2026-09-01",
-   "upstream_version": "V1.4",
-   "upstream_date": null,
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "M5Stack custom chip; same publisher",
-   "bytes": 398463,
-   "sha256": "9204d99cb2e03395ffc905e05fbeddf7f9f25de5698a31a65fa439dee700d8d2",
-   "magic_ok": true
-  },
-  {
-   "id": "A07",
-   "source_id": "S24",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf",
-   "fallback_urls": [],
-   "destination": "components/semtech/sx1262/artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf",
-   "owned_by": "components/semtech/sx1262",
-   "retrieved": "2026-09-01",
-   "upstream_version": "Rev 2.2",
-   "upstream_date": "2024-12",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "M5Stack MIRROR of a Semtech document. Semtech canonical download is behind a Salesforce JS/POST shell: BLOCKED. Semtech's page lists a 2025-04-07 revision, so mirror currency is UNRESOLVED.",
-   "bytes": 4459535,
-   "sha256": "6d783125dbef567954ce53095ad068d0950b2a8de52f95bb2cfde4146c4306c2",
-   "magic_ok": true
-  },
-  {
-   "id": "A08",
-   "source_id": "S23",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_EN.pdf",
-   "fallback_urls": [],
-   "destination": "components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf",
-   "owned_by": "components/stmicroelectronics/st25r3916",
-   "retrieved": "2026-09-01",
-   "upstream_version": "DS12484 Rev 8",
-   "upstream_date": "2023-05-08",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "M5Stack MIRROR, verified BYTE-IDENTICAL to ST's canonical file. ST requires UA 'WhatsApp/2.23.20.0'; Chrome and ClaudeBot get a stream reset.",
-   "bytes": 2241765,
-   "sha256": "1170f4d74ff501917262ae42bf81c60c38c11d121e2ea2af6b1e845433befef1",
-   "magic_ok": true
-  },
-  {
-   "id": "A09",
-   "source_id": "S22",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1132/RX8130CE_cn-Register-Datasheet.pdf",
-   "fallback_urls": [],
-   "destination": "components/seiko-epson/rx8130ce/artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf",
-   "owned_by": "components/seiko-epson/rx8130ce",
-   "retrieved": "2026-09-01",
-   "upstream_version": "ETM50E-09",
-   "upstream_date": "2025-06-30",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "Despite the '_cn' filename this is Epson's ENGLISH manual; '_cn' denotes Epson's China site. No Chinese edition exists.",
-   "bytes": 2283323,
-   "sha256": "7157dc5692e5e0d84203027b600858e57880ef7a38b9c7d7f8c661a93fc8f3f5",
-   "magic_ok": true
-  },
-  {
-   "id": "A10",
-   "source_id": "S20",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/SSD1677.pdf",
-   "fallback_urls": [],
-   "destination": "components/solomon-systech/ssd1677/artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf",
-   "owned_by": "components/solomon-systech/ssd1677",
-   "retrieved": "2026-09-01",
-   "upstream_version": "Rev 1.0 (Advance Information)",
-   "upstream_date": "2018-11",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "46 pages but numbers itself n/47; Producer 'PDFill', not a Solomon Systech export. Provenance UNRESOLVED.",
-   "bytes": 3602487,
-   "sha256": "daf8b726f822f6907529386b8af6fbea6ec5e8ecc7b7af361340be911d632544",
-   "magic_ok": true
-  },
-  {
-   "id": "A11",
-   "source_id": "S21",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/EPD_Module_User_Manual.pdf",
-   "fallback_urls": [],
-   "destination": "components/dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf",
-   "owned_by": "components/dke/depg0397bbs770f3",
-   "retrieved": "2026-09-01",
-   "upstream_version": "unknown (drawing REV A0, 2024-09-29)",
-   "upstream_date": null,
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "DKE Holding Company Limited. NO TEXT LAYER - vector-outlined text; pdftotext returns nothing. Must be rendered with pdftoppm and read as images.",
-   "bytes": 8666208,
-   "sha256": "6b65f56d5d549a132e5c807eef329fb3e997feab04ac06e8a107f01591618130",
-   "magic_ok": true
-  },
-  {
-   "id": "A12",
-   "source_id": "S19",
-   "kind": "datasheet",
-   "url": "https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/app/Stamp%20Fly/BMI270.PDF",
-   "fallback_urls": [],
-   "destination": "components/bosch-sensortec/bmi270/artifacts/bst-bmi270-ds000-05-rev1.3-m5stack-mirror.pdf",
-   "owned_by": "components/bosch-sensortec/bmi270",
-   "retrieved": "2026-09-01",
-   "upstream_version": "rev 1.3 (BST-BMI270-DS000-05)",
-   "upstream_date": "2020-11",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "M5Stack MIRROR five years behind Bosch's current rev 1.6 (2026-03, DS000-08) already held in the same directory. This older revision is the one the board was documented against.",
-   "bytes": 3830973,
-   "sha256": "3ab915ed1d81d0eaa5ff1d1aed62b2b491260c9d59afbf79bb23fb477e015612",
-   "magic_ok": true
-  },
-  {
-   "id": "A13",
-   "source_id": "S18",
-   "kind": "datasheet",
-   "url": "https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf",
-   "fallback_urls": [],
-   "destination": "components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf",
-   "owned_by": "components/espressif/esp32-s3r8",
-   "retrieved": "2026-09-01",
-   "upstream_version": "v2.0",
-   "upstream_date": "2025-04",
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "FOURTH distinct ESP32-S3 datasheet file in this repository - four different SHA-256 values across revisions v2.2 / v2.0 / two byte-different v1.6 exports.",
-   "bytes": 1083807,
-   "sha256": "b6db403d6d5db8d1b4db0c8390ff7e0a7db714b8388e986e1c64bff563f76b61",
-   "magic_ok": true
-  },
-  {
-   "id": "A14",
-   "source_id": null,
-   "kind": "datasheet",
-   "url": "https://support.epson.biz/td/api/doc_check.php?dl=app_RX8130CE&lang=en",
-   "fallback_urls": [],
-   "destination": "components/seiko-epson/rx8130ce/artifacts/rx8130ce-application-manual-etm50e-10-en-epson.pdf",
-   "owned_by": "components/seiko-epson/rx8130ce",
-   "retrieved": "2026-09-01",
-   "upstream_version": "ETM50E-10",
-   "upstream_date": "2026-01-30",
-   "licence": "proprietary - explicit no-redistribution notice",
-   "licence_evidence": "notice printed in the document",
-   "redistribution": "restricted",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "reacquisition": "automatic",
-   "notes": "RETAINED DESPITE A RESTRICTED NOTICE - flagged for user review. Kept because the diff against ETM50E-09 is itself the finding: -10 DELETES items (1)-(7) of section 14.4.2; the older mirror carries MORE text. All registers, thresholds and timings identical.",
-   "bytes": 2008845,
-   "sha256": "db027a5fa2dd17b333da81e95063764eb5536d2878c63b64949348d2ec4b8a22",
-   "magic_ok": true,
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  },
-  {
-   "id": "A15",
-   "source_id": null,
-   "kind": "datasheet",
-   "url": null,
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "components/generic",
-   "retrieved": "2026-09-01",
-   "upstream_version": "unknown",
-   "upstream_date": null,
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "lost",
-   "notes": "Negative result, recorded deliberately. Search ledger is in the component record and research-log.md.",
-   "omission_reason": "no datasheet located on any of 11+ services",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition",
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  },
-  {
-   "id": "A16",
-   "source_id": null,
-   "kind": "datasheet",
-   "url": null,
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "components/generic",
-   "retrieved": "2026-09-01",
-   "upstream_version": "unknown",
-   "upstream_date": null,
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "lost",
-   "notes": "Negative result, recorded deliberately. Search ledger is in the component record and research-log.md.",
-   "omission_reason": "the only web occurrences anywhere are M5Stack's own pages",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition",
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  },
-  {
-   "id": "A17",
-   "source_id": null,
-   "kind": "datasheet",
-   "url": null,
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "components/generic",
-   "retrieved": "2026-09-01",
-   "upstream_version": "unknown",
-   "upstream_date": null,
-   "licence": "unknown",
-   "licence_evidence": "no notice located in document",
-   "redistribution": "unknown",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "lost",
-   "notes": "Negative result, recorded deliberately. Search ledger is in the component record and research-log.md.",
-   "omission_reason": "the only web occurrences anywhere are M5Stack's own pages",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition",
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  },
-  {
-   "id": "A18",
-   "source_id": "S41",
-   "kind": "source repository",
-   "url": "https://github.com/m5stack/M5PaperMono-UserDemo",
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "main@c1099107271d31a0678d661a896e2b04dbb331ea",
-   "upstream_date": "2026-08-10",
-   "licence": "MIT",
-   "licence_evidence": "LICENSE file in repository root",
-   "redistribution": "allowed",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "automatic",
-   "notes": null,
-   "clone": "git clone https://github.com/m5stack/M5PaperMono-UserDemo && git -C M5PaperMono-UserDemo checkout c1099107271d31a0678d661a896e2b04dbb331ea",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition"
-  },
-  {
-   "id": "A19",
-   "source_id": null,
-   "kind": "source repository",
-   "url": "https://github.com/m5stack/M5PaperMono-OTP-Demo",
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "main@c7c02554f89fd06f80d988b805b2a59050c78a46",
-   "upstream_date": "2026-08-20",
-   "licence": "MIT",
-   "licence_evidence": "LICENSE file in repository root",
-   "redistribution": "allowed",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "automatic",
-   "notes": null,
-   "clone": "git clone https://github.com/m5stack/M5PaperMono-OTP-Demo && git -C M5PaperMono-OTP-Demo checkout c7c02554f89fd06f80d988b805b2a59050c78a46",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition",
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  },
-  {
-   "id": "A20",
-   "source_id": "S43",
-   "kind": "source repository",
-   "url": "https://github.com/m5stack/M5PM1",
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "main@be9a5456c007c333e7ac963f33bfde1ffa5d82ee",
-   "upstream_date": "2026-05-29",
-   "licence": "MIT",
-   "licence_evidence": "LICENSE file in repository root",
-   "redistribution": "allowed",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "automatic",
-   "notes": null,
-   "clone": "git clone https://github.com/m5stack/M5PM1 && git -C M5PM1 checkout be9a5456c007c333e7ac963f33bfde1ffa5d82ee",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition"
-  },
-  {
-   "id": "A21",
-   "source_id": "S44",
-   "kind": "source repository",
-   "url": "https://github.com/m5stack/M5IOE1",
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "main@846eec7d05e25c09013be2acdb8804487f48a62e",
-   "upstream_date": "2026-05-29",
-   "licence": "MIT",
-   "licence_evidence": "LICENSE file in repository root",
-   "redistribution": "allowed",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "automatic",
-   "notes": null,
-   "clone": "git clone https://github.com/m5stack/M5IOE1 && git -C M5IOE1 checkout 846eec7d05e25c09013be2acdb8804487f48a62e",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition"
-  },
-  {
-   "id": "A22",
-   "source_id": null,
-   "kind": "source repository",
-   "url": "https://github.com/m5stack/M5_Hardware",
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "master@a240115c94b19ecf647f229c47fa9a8ce46ccdc4",
-   "upstream_date": "2026-08-17",
-   "licence": "MIT",
-   "licence_evidence": "LICENSE file in repository root",
-   "redistribution": "allowed",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "automatic",
-   "notes": "M5_Hardware product tree stops at C152 and contains NO C153 entry as of this commit - verified absence, so no machine-readable netlist exists for this board.",
-   "clone": "git clone https://github.com/m5stack/M5_Hardware && git -C M5_Hardware checkout a240115c94b19ecf647f229c47fa9a8ce46ccdc4",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition",
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  },
-  {
-   "id": "A23",
-   "source_id": null,
-   "kind": "source repository",
-   "url": "https://github.com/m5stack/M5Unified",
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "master@8530f53",
-   "upstream_date": "unknown",
-   "licence": "MIT",
-   "licence_evidence": "LICENSE file in repository root",
-   "redistribution": "allowed",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "automatic",
-   "notes": null,
-   "clone": "git clone https://github.com/m5stack/M5Unified && git -C M5Unified checkout 8530f53",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition",
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  },
-  {
-   "id": "A24",
-   "source_id": null,
-   "kind": "source repository",
-   "url": "https://github.com/m5stack/M5GFX",
-   "fallback_urls": [],
-   "destination": null,
-   "owned_by": "devices/m5stack/papermono",
-   "retrieved": "2026-09-01",
-   "upstream_version": "master@d91077b",
-   "upstream_date": "unknown",
-   "licence": "MIT",
-   "licence_evidence": "LICENSE file in repository root",
-   "redistribution": "allowed",
-   "disposition": "reference-only",
-   "repo_state": "not-downloaded",
-   "reacquisition": "automatic",
-   "notes": null,
-   "clone": "git clone https://github.com/m5stack/M5GFX && git -C M5GFX checkout d91077b",
-   "bytes": null,
-   "sha256": null,
-   "_note_missing": "not present in tree; see reacquisition",
-   "_note_source_id": "no confident match in sources.md; left null rather than guessed"
-  }
- ],
- "id_scheme": "Manifest entries use an 'A##' namespace, deliberately DISTINCT from the 'S##' IDs in sources.md, which is the canonical human-facing source table. Each entry carries `source_id` giving its sources.md row where a confident match exists, else null. The two schemes previously both used 'S##' and genuinely crossed over, so an ID followed from one file into the other landed on the wrong row -- the defect recorded as conflict C23. The distinct namespace makes that mistake impossible."
-}
\ No newline at end of file
diff --git a/devices/m5stack/papermono/artifacts/firmware/C153-PaperMono-UserDemo-v1.2.bin b/devices/m5stack/papermono/artifacts/firmware/C153-PaperMono-UserDemo-v1.2.bin
deleted file mode 100644
index a005a80..0000000
Binary files a/devices/m5stack/papermono/artifacts/firmware/C153-PaperMono-UserDemo-v1.2.bin and /dev/null differ
diff --git a/devices/m5stack/papermono/artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin b/devices/m5stack/papermono/artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin
deleted file mode 100644
index adc30f3..0000000
Binary files a/devices/m5stack/papermono/artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin and /dev/null differ
diff --git a/devices/m5stack/papermono/artifacts/firmware/esp-image-analysis.txt b/devices/m5stack/papermono/artifacts/firmware/esp-image-analysis.txt
deleted file mode 100644
index cc0b461..0000000
--- a/devices/m5stack/papermono/artifacts/firmware/esp-image-analysis.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-==========================================================================
-C153-PaperMono-UserDemo-v1.2.bin  (2868208 bytes)
--- bootloader image header @0x0 --
-    {'offset': '0x0', 'magic': '0xe9', 'segments': 3, 'flash_mode': 'DIO', 'flash_size': '16MB', 'flash_freq': '80MHz', 'entry': '0x403c8924', 'chip_id': '9 (ESP32-S3)', 'min_rev': 0}
--- app image header @0x10000 --
-    {'offset': '0x10000', 'magic': '0xe9', 'segments': 7, 'flash_mode': 'DIO', 'flash_size': '16MB', 'flash_freq': '80MHz', 'entry': '0x40375bec', 'chip_id': '9 (ESP32-S3)', 'min_rev': 0}
--- partition table @0x8000 --
-    nvs              type=data(1) subtype=0x02 addr=0x009000 size=0x006000 (24K)
-    phy_init         type=data(1) subtype=0x01 addr=0x00f000 size=0x001000 (4K)
-    factory          type=app(0) subtype=0x00 addr=0x010000 size=0xf00000 (15360K)
--- esp_app_desc_t --
-    {'at': '0x10020', 'app_version': 'c78f6c5-dirty', 'project_name': 'PaperMono-UserDemo', 'build_time': '16:12:13', 'build_date': 'Aug  6 2026', 'idf_version': 'v5.5.1'}
-==========================================================================
-crosspoint-paper-mono-cjk-1.5.0-RC.bin  (10319500 bytes)
--- bootloader image header @0x0 --
-    {'offset': '0x0', 'magic': '0xe9', 'segments': 3, 'flash_mode': 'DIO', 'flash_size': '16MB', 'flash_freq': '80MHz', 'entry': '0x403c88b8', 'chip_id': '9 (ESP32-S3)', 'min_rev': 0}
--- app image header @0x10000 --
-    {'offset': '0x10000', 'magic': '0xe9', 'segments': 7, 'flash_mode': 'DIO', 'flash_size': '16MB', 'flash_freq': '80MHz', 'entry': '0x40375fe0', 'chip_id': '9 (ESP32-S3)', 'min_rev': 0}
--- partition table @0x8000 --
-    nvs              type=data(1) subtype=0x02 addr=0x009000 size=0x005000 (20K)
-    app0             type=app(0) subtype=0x00 addr=0x010000 size=0x640000 (6400K)
-    cjkfont          type=data(1) subtype=0x40 addr=0x650000 size=0x400000 (4096K)
-    spiffs           type=data(1) subtype=0x82 addr=0xc90000 size=0x360000 (3456K)
-    coredump         type=data(1) subtype=0x03 addr=0xff0000 size=0x010000 (64K)
--- esp_app_desc_t --
-    {'at': '0x10020', 'app_version': 'paper-mono-v2-15-g87a191f', 'project_name': 'crosspoint-reader-mono', 'build_time': '19:58:33', 'build_date': 'Aug 22 2026', 'idf_version': '5.5.2.260206'}
diff --git a/devices/m5stack/papermono/artifacts/mechanical/C153_PaperMono_model_size.pdf b/devices/m5stack/papermono/artifacts/mechanical/C153_PaperMono_model_size.pdf
deleted file mode 100644
index 19e15f1..0000000
Binary files a/devices/m5stack/papermono/artifacts/mechanical/C153_PaperMono_model_size.pdf and /dev/null differ
diff --git a/devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf b/devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf
deleted file mode 100644
index 7c66d7c..0000000
Binary files a/devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf and /dev/null differ
diff --git a/devices/m5stack/papermono/bill-of-materials.md b/devices/m5stack/papermono/bill-of-materials.md
deleted file mode 100644
index ec9da9c..0000000
--- a/devices/m5stack/papermono/bill-of-materials.md
+++ /dev/null
@@ -1,743 +0,0 @@
-# M5Stack PaperMono — bill of materials
-
-> A **290-component, 230-designator census** recovered from
-> [`PaperMono_SCH_V0.6.2_20260522.pdf`](artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf),
-> the only schematic M5Stack publishes for the [PaperMono](README.md) (SKU C153).
-> Research snapshot **2026-09-01**. **No hardware was in the loop** and this is
-> **not a vendor BOM** — see [§2, Method and its limits](#2-method-and-its-limits)
-> before using any quantity or value here for procurement.
-
----
-
-## Evidence labelling
-
-| Marker | Meaning | Status |
-|---|---|---|
-| **[SCH-M]** | Recovered from the Altium PDF's invisible `CO`/`PI` marker layer, then **checked against a rendered page image** | `executed-success` for the extraction |
-| **[SCH-T]** | Read from the PDF text layer *only* (adjacency to a symbol), **not** confirmed against a rendered image | `executed-success` for the extraction; the *attribution to a designator* is `inferred` |
-| **[SCH-V]** | Read directly off a page rendered to PNG at 200 dpi and inspected as an image | `executed-success` |
-| **[DS]** | A component datasheet held under that component's `artifacts/` | `not-tested` |
-| **[INF]** | Inference, flagged as such | `inferred` |
-
-Nothing here is `reported-working`: no PaperMono was measured, probed or powered.
-
----
-
-## 1. Headline counts
-
-| Quantity | Value |
-|---|---:|
-| **Placed components** (sheet-scoped instances) | **290** |
-| **Distinct reference-designator strings** | **230** |
-| Sheets carrying components | 5 of 6 (sheet 1 is a block diagram and carries none) |
-| Separate Altium documents concatenated into the PDF | **3** |
-| Components with a component record in this repository | **56** |
-| Components deliberately left without a record (ordinary passives) | **221** |
-| Components **unidentified** after searching | **13** |
-
-Per sheet:
-
-| Sheet | Document | Placed components |
-|---:|---|---:|
-| 1 | main project — architecture/block diagram, power-state table | **0** |
-| 2 | main project — USB-C, protection, charger, rails, frontlight boost | **93** |
-| 3 | main project — ESP32-S3, flash, RF front end, test points | **52** |
-| 4 | main project — RTC, IMU, buzzer, NFC/LoRa interfaces, TP, EPD, microSD | **79** |
-| 5 | `PaperMono KEY RGB.SchDoc` — keys, RGB LED, PDM microphone | **23** |
-| 6 | `02 Paper Mono NFC.SchDoc` — ST25R3916 NFC front end | **43** |
-
----
-
-## 2. Method and its limits
-
-**Read this before quoting a number from this page.**
-
-The census comes from the **Altium `CO` (component-outline) marker layer** that
-Altium Designer's PDF publisher embeds as invisible text at every placed symbol.
-That has three consequences that a reader must hold onto:
-
-1. **It captures placed symbols, not a purchased BOM.** A `CO` marker says "a
-   symbol with this designator sits here". It says nothing about whether the pad
-   is populated at assembly. Parts whose value string reads `NC` are *drawn* and
-   *counted* here but are **not fitted** — there are **11** of them (§8).
-   Conversely, anything M5Stack fits that has no schematic symbol (test coupons,
-   shield cans, the LoRa module's own internals) is invisible to this method.
-
-2. **Values come from text adjacency, not from a parsed netlist.** Altium writes
-   the designator and the value as two ordinary text objects near the symbol.
-   Pairing them is a nearest-neighbour guess. It is right the overwhelming
-   majority of the time and it is *wrong* where symbols are packed tightly —
-   which on this schematic means the charger block on sheet 2 and the microSD
-   block on sheet 4. Every value in this document that is load-bearing for a
-   component record was re-read from a **rendered page image** and is marked
-   **[SCH-V]**; the rest are **[SCH-T]** and should be treated as good but
-   unconfirmed.
-
-3. **Tolerances and dielectrics are only as good as the string.** `100nF/25V`
-   tells you capacitance and voltage. It does not tell you X5R vs X7R, case size,
-   or the DC-bias derating that actually determines whether a 22 µF/10 V 0603 is
-   4 µF at 4.2 V. **No case sizes appear anywhere in this PDF.** Resistor
-   tolerance is uniformly printed `/1%`; capacitor tolerance is never printed.
-
-### 2.1 ⚠ Two parser artefacts had to be repaired — and one of them refutes a claim
-
-`tools/altium_pdf_netlist.py` matches a marker prefix (`CO`, `PI`, `NL`) anywhere
-in a word not preceded by a letter. Its docstring already warns that `GPIO0`
-parses as `G` + `PI`-marker `O0`, and guards that with a negative lookbehind. The
-guard does **not** cover ordinary schematic text that *begins* with those letters,
-and this schematic contains two such strings:
-
-| Raw word in the PDF | Where | Mis-read as | Reality |
-|---|---|---|---|
-| `CON2_SMD` | sheet 2, at `J2` | a component **`N2`** | the battery connector's **footprint label** **[SCH-V]** |
-| `PIN1` … `PIN24` (24 words) | sheet 4, at `J5` | pin markers **`N1` … `N24`** | the FPC symbol's **pin-name labels** **[SCH-V]** |
-
-> ⚠ **There is no `N`-series on this board, so "`N1` is missing" is not a finding.**
-> An earlier reading of this census recorded `N1` as a gap alongside the five
-> missing resistors. It is not a gap: **`N1` never existed, and neither did `N2`.**
-> The battery connector is `J2` and nothing else. Confirmed by rendering sheet 2
-> at 200 dpi and reading the symbol, which shows a 2-pin connector labelled `J2`
-> with `CON2_SMD` printed beneath it as the footprint name. Date 2026-09-01.
-
-### The second defect: a designator with no digits disappears
-
-`designators()` keeps only marker bodies matching `[A-Z]+[0-9]+`. **A designator
-with no number is silently dropped.** This board has one:
-
-| Marker | Where | Pin markers | Reality |
-|---|---|---|---|
-| **`COUSB`** | sheet 2 | **16 × `PIUSB01`…`PIUSB016`** | the **USB-C receptacle**, designated **`USB`** |
-| `CORE` | sheet 1 | **none** | the block-diagram word **"CORE"** — a phantom, like `CON2_SMD` |
-
-The pin markers are what separate the two: a real component's outline marker is
-accompanied by pin markers, and 16 of them is exactly a 16-contact USB-C
-receptacle. `CORE` has none, and sheet 1 genuinely carries no components.
-
-> ⚠ **The USB-C receptacle's reference designator is `USB`, not `U1`.** An
-> earlier reading of this census recorded it as a second `U1` on sheet 2 —
-> because `TYPEC-302-BRP16SC08` sits above the symbol and `USB` below it, and the
-> IP2315's `U1` is the nearest designator-shaped string. **Refuted** by the
-> marker layer: sheet 2 contains exactly one `CO` marker with body `U1` (the
-> IP2315, whose adjacent text is `CC1 / NC/1% / CC2 / DM`) and one with body
-> `USB`. **Sheet 2 has one `U1`, not two.** Date 2026-09-01.
-
-### The third defect: eight clipped markers on sheet 6
-
-**On sheet 6 only**, `pdftotext` drops the leading glyph of eight `CO` markers:
-
-```
-x=506.50 'PIC1802'   x=511.00 'COC18'   x=512.30 'C18'    <- intact
-x=463.50 'PIC1602'   x=467.64  'OC16'   x=469.14 'C16'    <- leading C dropped
-```
-
-Eight capacitors — `C1`, `C16`, `C17`, `C19`, `C21`, `C24`, `C25`, `C27` — were
-therefore missing from the raw census. **They are placed parts, not gaps.** With
-them restored, sheet 6 holds 43 components and its `C` series runs `C1`–`C31`
-unbroken.
-
-This is the [method's own warning](../../../.agents/skills/hardware-device-research/SKILL.md)
-about trusting a text layer, landing **three times** on one document. The corrected census
-is produced by [`scratch/m5stack-papermono/tools/census.py`](../../../scratch/m5stack-papermono/tools/census.py),
-which repairs both defects and prints the gap analysis below. **[SCH-M]**
-
----
-
-## 3. ⚠ Designators repeat across sheets — a designator alone is meaningless
-
-The published PDF is **three separate Altium documents printed back to back**,
-not one six-sheet project. Each document numbers its designators from 1.
-
-| Sheets | Document | Evidence |
-|---|---|---|
-| 1–4 | the main project | continuous numbering `C1`–`C85`, `U1`–`U21`, `R1`–`R68` across the four sheets |
-| 5 | `PaperMono KEY RGB.SchDoc` | title block, sheet 5: `File: Y:\AD.Prj\..\PaperMono KEY RGB.SchDoc`, dated **2026-04-14** **[SCH-T]** |
-| 6 | `02 Paper Mono NFC.SchDoc` | title block, sheet 6: `File: Y:\AD.Prj\..\02 Paper Mono NFC.SchDoc`, `Paper Mono NFC`, `2/2`, `V0.2`, dated **2026-07-28** **[SCH-T]** |
-
-So the same string names different parts:
-
-| Designator | Sheet 2 (main) | Sheet 5 (KEY/RGB) | Sheet 6 (NFC) |
-|---|---|---|---|
-| **`U1`** | [Injoinic IP2315](../../../components/injoinic/ip2315/README.md) charger — **and nothing else; the receptacle is `USB`** | [LMD4737T261-AC02](../../../components/generic/lmd4737t261-ac02-pdm-microphone/README.md) PDM microphone | [AW35122FDR](../../../components/awinic/aw35122/README.md) load switch |
-| **`J1`** | frontlight connector, 6-pin | [`AXE612124D`](../../../components/panasonic/axe612124d/README.md) board-to-board | [`BTB0.408-10PLBDR-G41`](../../../components/generic/btb0.408-10plbdr-g41/README.md) board-to-board |
-| **`LED1`** | charger status LED net | [RS-C1415MBAR](../../../components/generic/rs-c1415mbar-rgb-led/README.md) RGB LED | — |
-| **`C1`** | 100 nF/25 V | 100 nF/10 V | 10 nF |
-| **`R1`** | `NC/1%` (IP2315 `CC1`) | 10 kΩ (power-button pull-up) | 0 Ω (NFC 3V3 link) |
-| **`L1`** | `FTC252012S2R2MBCA` 2.2 µH | 2 nH | 270 nH ±5% |
-
-and there are three different `U1`s, two `X1`s, two `ANT1`s and two `LED1`s.
-
-> **Cite every part as `<designator> sheet <n>`.** "`U1`" is ambiguous;
-> "`U1` sheet 2" is not. Every row in this document does so, and so should any
-> record, issue report or firmware comment that refers to this board.
-
----
-
-## 4. ⚠ Gaps in the designator sequence — what is and is not evidence
-
-Enumerating the *complete* set per document, rather than searching for the parts
-one expects, is what makes a gap meaningful. The corrected census finds gaps in
-**exactly one** prefix, in **exactly one** document:
-
-| Document | Prefix | Present | Highest | **Gaps** |
-|---|---|---:|---|---|
-| main (2–4) | `R` | 63 | `R68` | **`R46`, `R48`, `R55`, `R56`, `R57`** |
-| main (2–4) | `C` `U` `D` `L` `Q` `J` `TP` `TVS` `ANT` `BUZZER` `FT` `LED` `X` | — | — | none |
-| KEY RGB (5) | all | — | — | none |
-| NFC (6) | all | — | — | none |
-
-**Verification of the five.** `R46`, `R48`, `R55`, `R56` and `R57` appear
-**nowhere in the PDF** — not as a `CO` marker, not as a `PI` marker, not as
-visible text, on any of the six sheets. This was tested by scanning every
-extracted word on every page for those literals, not by looking where they were
-expected. **[SCH-M]**
-
-**What the gaps most likely mean.** Honestly: the most probable explanation is
-the dullest one.
-
-- **Most likely — parts deleted during design.** All five sit inside `R42`–`R68`,
-  which is the *sheet 4* resistor block. Sheet 4 is present and complete; its
-  other 22 resistors are all there. A gap inside a range whose sheet is published
-  means the symbol was placed and later removed, and Altium does not renumber on
-  delete. `R55`–`R57` being three *consecutive* numbers is the signature of one
-  small sub-circuit being taken out in a single edit. **[INF]**
-- **Possible — annotation churn.** A re-annotation pass that renumbered some
-  parts can leave holes without anything having been deleted. Indistinguishable
-  from the above without the source project. **[INF]**
-- **Unlikely here — an unpublished sheet.** This is the explanation the method
-  warns to look for, and it is the right one elsewhere in this device's record:
-  the NFC document announces itself as sheet **`2/2`**, so **NFC sheet 1 of 2 is
-  genuinely unpublished** (see [`gaps-and-conflicts.md`](gaps-and-conflicts.md)
-  R8). But a missing sheet would take a *contiguous block* of designators with
-  it, across several prefixes at once. Five scattered resistors and no missing
-  `C`, `U`, `D` or `Q` is not that pattern. **[INF]**
-
-**What cannot be concluded.** Nothing here establishes what the deleted parts
-*were*. Do not infer a depopulated feature from them. Resolving this needs the
-Altium source project or a photographed bare PCB showing unpopulated pads — the
-schematic alone cannot answer it.
-
----
-
-## 5. Sheet 2 — USB-C input, protection, charging, rails, frontlight boost (92)
-
-### 5.1 Integrated circuits and actives
-
-| Ref | Part | Function | Record |
-|---|---|---|---|
-| `U1` | `IP2315` | 1S Li-ion synchronous buck charger, I²C `0x75`, **gated off the bus** | [injoinic/ip2315](../../../components/injoinic/ip2315/README.md) |
-| `U2` | `AW32901FCR` | USB-input OVP load switch, 5.95 V threshold | [awinic/aw32901](../../../components/awinic/aw32901/README.md) |
-| `U3` | `AW39112DNR` | 2-bit level translator — the charger's I²C gate | [awinic/aw39112](../../../components/awinic/aw39112/README.md) |
-| `U4` | `SSP7615-33DFR` | 3.3 V/400 mA LDO → `3V3_L0` (always-on rail) | [generic/ssp7615-33dfr](../../../components/generic/ssp7615-33dfr/README.md) |
-| `U5` | `SSP7615-33DFR` | 3.3 V LDO → `EPD_3V3_L3` | idem |
-| `U6` | `SSP7615-33DFR` | 3.3 V LDO → `3V3_L1` | idem |
-| `U7` | `M5PM1` | power-management coprocessor, I²C `0x6E` (Puya PY32L020F15U6 inside) | [m5stack/m5pm1](../../../components/m5stack/m5pm1/README.md) |
-| `U8` | `AW35122FDR` | 1.5 A load switch → `TF_3V3_L3` (microSD) | [awinic/aw35122](../../../components/awinic/aw35122/README.md) |
-| `U9` | `SSP7615-33DFR` | 3.3 V LDO → `3V3_L2_LoRa` | [generic/ssp7615-33dfr](../../../components/generic/ssp7615-33dfr/README.md) |
-| `U10` | `JW5712` | 600 mA buck → `3V3_L2`, the main system rail | [joulwatt/jw5712](../../../components/joulwatt/jw5712/README.md) |
-| `U11` | `AW9967DNR` | boost WLED driver — the e-paper frontlight, `BL_15V_L3B` | [awinic/aw9967](../../../components/awinic/aw9967/README.md) |
-
-### 5.2 Discrete semiconductors
-
-| Ref | Part | Circuit role | Record |
-|---|---|---|---|
-| `D1` | `DSK34` | Schottky at the IP2315 `LX`/`DM` node **[SCH-T]** — role not confirmed visually | **unidentified**, §9 |
-| `D2` | `RB162VAM-20TR` | **frontlight boost rectifier**: `L3` → `D2` → `R27` → `BL_15V_L3B` **[SCH-V]** | [rohm/rb162vam-20tr](../../../components/rohm/rb162vam-20tr/README.md) |
-| `Q1` | `CJ3439KDW` | **complementary N+P pair — the gated battery-sense divider.** `Q1A` (N) gate = `BAT_ADC_EN`; its drain pulls `Q1B` (P) gate low through `R3` = 1 MΩ; `Q1B` connects `VBAT_L0` to the `R5`/`R12` 1 kΩ + 1 kΩ divider feeding `BAT_ADC` **[SCH-V]** | [changjing/cj3439kdw](../../../components/changjing/cj3439kdw/README.md) |
-| `Q2` | `SK2302AAT` | N-channel; gate = `VUSB_IN`, source = GND, drain = `Q5` gate. **USB-presence detector** **[SCH-V]** | [generic/sk2302aat](../../../components/generic/sk2302aat/README.md) |
-| `Q5` | `SK2301AAT` | P-channel high side; source = `VBAT_L0`, drain = `VBAT_DET`, gate held up by `R45` = 100 kΩ. **Connects the battery to `VBAT_DET` only while USB is present** **[SCH-V]** | [generic/sk2301aat](../../../components/generic/sk2301aat/README.md) |
-| `TVS1` | `ESD5311` | ESD clamp on **`USB_N`** **[SCH-V]** | [generic/esd5311](../../../components/generic/esd5311/README.md) |
-| `TVS2` | `ESD5311` | ESD clamp on **`USB_P`** **[SCH-V]** | idem |
-| `LED1` | — | charger status LED on the IP2315 `LED1/SCL` net **[SCH-T]** | **unidentified**, §9 |
-
-### 5.3 Connectors
-
-| Ref | Part | Pins | Carries | Record |
-|---|---|---:|---|---|
-| **`USB`** | `TYPEC-302-BRP16SC08` | 16 | USB-C receptacle: `VBUS`, `GND`, `CC1`, `CC2`, `DP1/DP2`, `DN1/DN2`, `SBU1/SBU2`, 4× shell | [generic/typec-302-brp16sc08](../../../components/generic/typec-302-brp16sc08/README.md) |
-| `J1` | — | 6 | frontlight: `BL_15V_L3B`, `BL_FB`, `PYG3_BL_PWM` | **unidentified**, §9 |
-| `J2` | `CON2_SMD` | 2 | **battery only** — pin 2 `VBAT_L0`, pin 1 GND, `C13` = 22 µF/10 V across **[SCH-V]** | [generic/papermono-1150mah-liion-cell](../../../components/generic/papermono-1150mah-liion-cell/README.md) |
-
-> **The USB-C receptacle's designator is the bare string `USB`** — no number.
-> That is legal in Altium and unusual in practice, and it is why a naive census
-> misses the part entirely (§2.1). Its symbol carries `TYPEC-302-BRP16SC08` above
-> and `USB` below; the IP2315's carries `IP2315（无后缀）`. **[SCH-V]**
->
-> ⚠ [`pinouts-and-buses.md`](pinouts-and-buses.md) lists this connector as
-> "`U1` (sheet 2)". That is the mis-attribution described in §2.1; the designator
-> is `USB`. Not corrected there by this pass — recorded here. Date 2026-09-01.
-
-### 5.4 Inductors — no records, and why
-
-Per the method, ordinary passives get a record only where they affect firmware,
-signal integrity, calibration, safety or a published interface. These are
-switching-converter magnetics: the converter's record already documents the
-topology, and the inductor value is a design parameter of that converter rather
-than an independent interface. **No records were created.**
-
-| Ref | Part | Value | Circuit role |
-|---|---|---|---|
-| `L1` | `FTC252012S2R2MBCA` | 2.2 µH | **IP2315 buck output inductor** — `LX` (pins 11–14) → `VBAT_L0` **[SCH-T]** |
-| `L2` | `FTC201610S2R2MBCA` | 2.2 µH | **JW5712 buck output inductor** — `SW` → `3V3_L2` **[SCH-V]** |
-| `L3` | `FTC201610S100MBCA` | 10 µH | **AW9967 boost inductor** — `EPD_3V3_L3` → `SW`, then `D2` → `BL_15V_L3B` **[SCH-V]** |
-
-`FTC` and `SPH` are shielded-power-inductor series codes; the numeric field
-encodes case size and inductance (`201610` = 2.0 × 1.6 × 1.0 mm, `S100` = 10 µH,
-`S2R2` = 2.2 µH). No manufacturer is printed on the schematic and none was
-established. **[INF]**
-
-### 5.5 Passives — no records
-
-**38 capacitors** `C1`–`C38` and **31 resistors** (`R1`–`R29`, `R45`). Values
-**[SCH-T]** unless marked.
-
-| Ref | Value | Where it sits |
-|---|---|---|
-| `C1` | 100 nF/25 V | `VUSB_IN` local decoupling |
-| `C2`, `C3` | 22 µF/10 V ×2 | `VBAT_L0` bulk at the charger output |
-| `C4` | 100 nF/25 V | `VBAT_DET` |
-| `C5` | 1 µF/25 V | IP2315 `nACOK` area |
-| `C6` | 1 µF/25 V | IP2315 `OVLO` area |
-| `C7` | 100 nF/25 V | **`BAT_ADC` filter**, with `R5`/`R12` **[SCH-V]** |
-| `C8`–`C11` | 22 µF/10 V ×4 | `VSYS` bulk |
-| `C12` | 100 nF/25 V | `5VIN_ADC` filter |
-| `C13` | 22 µF/10 V | **across the battery connector `J2`** **[SCH-V]** |
-| `C14`, `C15` | 10 µF/10 V ×2 | `U4` LDO in/out (`3V3_L0`) |
-| `C16`, `C17` | 10 µF/10 V ×2 | `U5` LDO in/out (`EPD_3V3_L3`) |
-| `C18`, `C19` | 10 µF/10 V ×2 | `U6` LDO in/out (`3V3_L1`) |
-| `C20`, `C21` | 10 µF/10 V ×2 | `U8` load-switch in/out (`TF_3V3_L3`) |
-| `C22`, `C23` | 10 µF/10 V ×2 | `U9` LDO in/out (`3V3_L2_LoRa`) |
-| `C24` | **33 pF/50 V** | AW9967 boost output snubber/feedforward **[SCH-V]** |
-| `C25` | **1 µF/50 V** | **the frontlight rail's only real output capacitor** **[SCH-V]** |
-| `C26` | **`NC/50V`** | frontlight output — **not fitted** **[SCH-V]** |
-| `C27`–`C29` | 10 µF/10 V ×3 | `3V3_L2` bulk |
-| `C30`–`C32` | 22 µF/10 V ×3 | `VBUS_L0` bulk |
-| `C33` | 1 nF/50 V | `VBUS_L0` HF bypass |
-| `C34`–`C36` | 22 µF/10 V ×3 | JW5712 input bulk |
-| `C37` | 100 nF/25 V | M5PM1 `VCC` decoupling |
-| `C38` | 10 µF/10 V | M5PM1 `VCC` bulk |
-| `R1`, `R2` | **`NC/1%`** | **IP2315 `CC1`/`CC2` series — not fitted; this is why there is no USB-PD** **[SCH-V]** |
-| `R3` | 1 MΩ | `Q1B` gate pull-up to `VBAT_L0` **[SCH-V]** |
-| **`R4`** | **5.1 kΩ** | **USB-C `CC1` pulldown (Rd)** **[SCH-V]** |
-| `R5`, `R12` | 1 kΩ, 1 kΩ | **`BAT_ADC` divider — 2:1** **[SCH-V]** |
-| `R6` | `NC/1%` | IP2315 `nACOK` — not fitted |
-| `R7` | 10 kΩ | IP2315 `VSYS`/`OVLO` area |
-| `R8`, `R13` | `NC` | charger I²C `CHG_SYS_SCL`/`SDA` series — **not fitted** |
-| `R9` | 100 kΩ | `Q2` gate pulldown **[SCH-V]** |
-| `R10` | `0R/1%` | IP2315 `OVLO` link |
-| `R11` | 100 kΩ | `Q1A` gate pulldown on `BAT_ADC_EN` **[SCH-V]** |
-| **`R14`** | **5.1 kΩ** | **USB-C `CC2` pulldown (Rd)** **[SCH-V]** |
-| `R15` | **`100K-RNTC`** | **NTC thermistor on IP2315 `NTC` (pin 26) → GND** **[SCH-V]** |
-| `R16` | 82 kΩ | **parallel/linearising resistor on the same `NTC` node** **[SCH-V]** |
-| `R17` | **15 kΩ** | **IP2315 `ICHGSET` (pin 27) → GND — the charge-current programming resistor** **[SCH-V]** |
-| `R18` | `NC/1%` | IP2315 `LED3` (pin 10) → GND — **not fitted** **[SCH-V]** |
-| `R19`, `R21` | 10 kΩ, 10 kΩ | `5VIN_ADC` divider |
-| `R20` | `0R/1%` | `VBUS_L0`/`VBAT_L0` link |
-| `R22` | 100 kΩ | `PYB_CHG_IIC` / `U3` `OE` |
-| `R23`, `R24`, `R26`, `R28` | 1 MΩ ×4 | LDO / load-switch `EN` pulldowns (`U5`, `U6`, `U9`, `U10`) |
-| `R25` | `NC/1%` | `U8` `EN` — not fitted |
-| `R27` | `0R/1%` | link between the boost output and `BL_15V_L3B` **[SCH-V]** |
-| `R29` | 18 Ω | **AW9967 `BL_FB` current-set resistor** |
-| `R45` | 100 kΩ | `Q5` gate pull-up to `VBAT_L0` **[SCH-V]** |
-
-> ⚠ **`R17` = 15 kΩ resolves an open question in the
-> [IP2315 record](../../../components/injoinic/ip2315/README.md#4-2--the-ntc-and-ichgset-network).**
-> That record could not tell from the text layer which of `R17`/`R18` reached
-> `ICHGSET`. Rendering the block at 200 dpi settles it: **`R17` is on `ICHGSET`,
-> `R18` is on `LED3` and is not fitted.** The conflict the record raises stands
-> and is now sharper — **15 kΩ is not one of the four values the IP2315 datasheet
-> tabulates for `ICHGSET`** (51 k / 130 k / 180 k / NC), so the programmed charge
-> current cannot be read off the datasheet table at all. Sheet 1 annotates
-> `充电电流 0.5C` ("charge current 0.5 C"), ≈ 575 mA for the 1150 mAh cell.
-> **[SCH-V]** + **[INF]**
-
----
-
-## 6. Sheet 3 — application processor, flash, RF front end, test points (52)
-
-### 6.1 Integrated circuits
-
-| Ref | Part | Function | Record |
-|---|---|---|---|
-| `U12` | `ESP32-S3R8` | application SoC, 8 MB in-package octal PSRAM | [espressif/esp32-s3r8](../../../components/espressif/esp32-s3r8/README.md) |
-| `U13` | `XM25UH128DHIQT` | 128 Mbit (16 MB) SPI NOR flash | [xmc/xm25uh128dhiqt](../../../components/xmc/xm25uh128dhiqt/README.md) |
-| `X1` | `CN4040M000157A530001` | 40 MHz crystal, ESP32-S3 main oscillator | [generic/cn4040m000157a530001-40mhz-crystal](../../../components/generic/cn4040m000157a530001-40mhz-crystal/README.md) |
-| `FT1` | `ICMF062P900MFR` | **USB common-mode choke** on `USB_N`/`USB_P` before the S3 | **unidentified**, §9 |
-| `ANT1` | — | 2.4 GHz antenna, fed through `L5` (0 Ω) and the `L4`/`C41`/`C42` match | **unidentified**, §9 |
-
-### 6.2 RF match and crystal load — no records
-
-| Ref | Part / value | Circuit role |
-|---|---|---|
-| `L4` | `LQP03TN2N6B02D` | **RF matching series inductor** (Murata LQP03TN 0201 thin-film, `2N6` = 2.6 nH). The schematic *also* prints `2nH` beside this group; the two strings disagree and the discrepancy is not resolved **[SCH-T]** |
-| `L5` | `0R/1%` | link between `ANT1` and the match — a 50 Ω pass-through / measurement break |
-| `L6` | `2nH` | RF match shunt, marked `50Ω` |
-| `L7` | `24nH` | crystal-network inductor at `XTAL_P`/`XTAL_N` |
-| `C39`, `C40` | `GRM0335C1H2R0BA01D` (2.0 pF), `GRM0335C1H1R8BA01D` (1.8 pF) | **Murata GRM0335 0201 C0G RF capacitors** in the antenna match |
-| `C41`, `C42` | **`NC(TBD)`** | **match tuning positions, deliberately left open and marked "to be determined"** — the clearest statement in the document that the antenna match was still being characterised at V0.6.2 **[SCH-T]** |
-| `C45`, `C50` | 24 pF ×2 | 40 MHz crystal load capacitors |
-
-No records: these are the RF matching network and the crystal load. The match is
-a board-level property documented in the device's RF section, not a component
-interface; the caps are commodity C0G parts whose only relevant property (value)
-is already stated. The **`NC(TBD)`** positions are the interesting part and they
-belong to the board, not to a component.
-
-### 6.3 Passives and test points — no records
-
-**19 capacitors** `C43`–`C57` (plus `C39`–`C42` above), **12 resistors**
-`R30`–`R41`, **15 test points** `TP1`–`TP12` on this sheet (`TP13`–`TP15` on
-sheet 4).
-
-| Ref | Value | Role |
-|---|---|---|
-| `C43`, `C44` | 100 nF/25 V, 10 µF/10 V | `VDD3P3` decoupling |
-| `C46`–`C49` | 10 µF/10 V, 1 µF/25 V, 100 nF/25 V ×2 | S3 supply decoupling |
-| `C51`, `C52` | 100 nF/25 V, 10 µF/10 V | `VDD3P3_CPU` |
-| `C53` | 1 µF/25 V | `CHIP_PU` / `SOC_RESET` RC |
-| `C54`, `C55` | 100 nF/25 V, 10 µF/10 V | `VDD3P3_RTC` |
-| `C56`, `C57` | 1 µF/25 V, 100 nF/25 V | NOR flash `VDD_NOR` decoupling |
-| `R30` | 499 Ω | `G44_U0_RX` series |
-| `R31`, `R32`, `R33` | 10 kΩ, 10 kΩ, 10 kΩ | `SOC_RESET`, `G0_BOOT_OUT` pull-ups |
-| **`R34`, `R35`, `R38`, `R39`, `R40`, `R41`, `R47`** | **22 Ω ×7** | **series damping** on SPI, e-paper SPI, USB `D+`/`D−` and the RTC I²C — the board's standard signal-integrity value |
-| `R36`, `R37` | **2.2 kΩ ×2** | **system I²C bus pull-ups** to `3V3_L2` (`G47_SYS_SDA` / `G48_SYS_SCL`) |
-| `TP1`–`TP12` | — | rails and debug: `VBUS_L0`, `3V3_L0`, `3V3_L1`, `3V3_L2`, `3V3_L2_LoRa`, `GND`, `G43_U0_TX`, `G44_U0_RX`, `SOC_RESET`, `G0_BOOT_OUT`, `BAT_ADC_EN`, `PY_LED_R` **[SCH-T]** |
-
----
-
-## 7. Sheet 4 — RTC, IMU, buzzer, radios, touch, e-paper, microSD (79)
-
-### 7.1 Integrated circuits and modules
-
-| Ref | Part | Function | Record |
-|---|---|---|---|
-| `U14` | `Stamp-LoRa-1262-mini` | LoRa module (Semtech SX1262 inside) — **not fitted on the Lite** | [m5stack/stamp-lora-1262](../../../components/m5stack/stamp-lora-1262/README.md) |
-| `U15` | `BMI270` | 6-axis IMU, I²C `0x68` | [bosch-sensortec/bmi270](../../../components/bosch-sensortec/bmi270/README.md) |
-| `U16` | `RX8130CE` | RTC, I²C `0x32` | [seiko-epson/rx8130ce](../../../components/seiko-epson/rx8130ce/README.md) |
-| `U17` | `M5IOE1` | I/O expander coprocessor, I²C `0x4F` | [m5stack/m5ioe1](../../../components/m5stack/m5ioe1/README.md) |
-| `U18` | `AW35122FDR` | load switch → `TP_VDD` (touch) | [awinic/aw35122](../../../components/awinic/aw35122/README.md) |
-| `U19` | `AW39112DNR` | 2-bit translator — the self-isolating touch I²C branch | [awinic/aw39112](../../../components/awinic/aw39112/README.md) |
-| `U20` | — | **microSD socket**, 9 contacts + shell. **No part number on the schematic** | [generic/micro-sd-sdmmc](../../../components/generic/micro-sd-sdmmc/README.md) (interface); part **unidentified**, §9 |
-| `U21` | `AW35122FDR` | load switch → `PDM_VDD` (microphone) | [awinic/aw35122](../../../components/awinic/aw35122/README.md) |
-
-### 7.2 Connectors
-
-| Ref | Part | Pins | Carries | Record |
-|---|---|---:|---|---|
-| `J3` | `BTB0.408-10PLBDR-G41` | 10 + 4 tabs | to the **NFC sub-board**: 3V3, GND, I²C, `G6_RFID_INT`, `PYB_NFC_EN` | [generic/btb0.408-10plbdr-g41](../../../components/generic/btb0.408-10plbdr-g41/README.md) |
-| `J4` | — | 8 | **touch panel FPC** — `TP_VDD`, `TP_SYS_SDA/SCL`, `G4_TP_INT`, `PYB_TP_RST` | **unidentified**, §9; controller: [focaltech/ft6336g](../../../components/focaltech/ft6336g/README.md) |
-| `J5` | `FPC0.5-SMT-24P-B` | 24 | **e-paper panel FPC** — 4-wire SPI, `BUSY`, `RST`, and the panel's own boost network | [generic/fpc0.5-smt-24p-b](../../../components/generic/fpc0.5-smt-24p-b/README.md) · panel: [dke/depg0397bbs770f3](../../../components/dke/depg0397bbs770f3/README.md) |
-| `J6` | `AXE512127D` | 12 + 4 tabs | to the **KEY/RGB/PDM sub-board** | [panasonic/axe512127d](../../../components/panasonic/axe512127d/README.md) |
-| `BUZZER1` | `ER103` | 2 | **magnetic buzzer**, `+` on `3V3_L1` | **unidentified**, §9 |
-
-### 7.3 Discrete semiconductors
-
-| Ref | Part | Circuit role | Record |
-|---|---|---|---|
-| `Q3` | `SK2302AAT` | N-channel **buzzer low-side driver**: gate = `G42_BB_PWM` with `R50` = 10 kΩ pulldown, source = GND, drain = `BUZZER1` `−` **[SCH-V]** | [generic/sk2302aat](../../../components/generic/sk2302aat/README.md) |
-| `Q4` | `CJ2310` | N-channel **e-paper bias switch** — the external NMOS for the SSD1677's on-chip DC/DC. Gate = `J5`.2 `GDR`, drain = `L8`/`D4`, source = `RESE` sense node through `R59` = 1.2 Ω **[SCH-V]** | [changjing/cj2310](../../../components/changjing/cj2310/README.md) |
-| `D3` | `1N4148WS` | **flyback clamp across the buzzer** — anode on `Q3`'s drain, cathode on the `3V3_L1` side **[SCH-V]** | [generic/1n4148ws](../../../components/generic/1n4148ws/README.md) |
-| `D4` | `1N5819WS` | **e-paper boost rectifier** → `PREVGH` **[SCH-V]** | [generic/1n5819ws](../../../components/generic/1n5819ws/README.md) |
-| `D5` | `1N5819WS` | **inverting charge-pump diode** — `PREVGL` → flying node **[SCH-V]** | idem |
-| `D6` | `1N5819WS` | **inverting charge-pump diode** — flying node → GND **[SCH-V]** | idem |
-| `TVS3`–`TVS9` | `ESD5311` ×7 | **ESD clamps on the microSD interface**, one per line — see §7.5 | [generic/esd5311](../../../components/generic/esd5311/README.md) |
-
-### 7.4 The e-paper bias generator, as drawn **[SCH-V]**
-
-Worth stating as a circuit because three of the six diodes and one of the five
-MOSFETs on this board exist only to serve it, and because it matches the DKE
-panel manual's own typical application circuit:
-
-```
-EPD_3V3_L3 ──[ L8  33 µH ]──┬──▶|── D4 ──┬── PREVGH   (C72 10 µF/25 V)
-   SPH252010H330MT          │            │
-                            │            └──┤ C67 10 µF/25 V ├──┬── D5 ──┘
-                       Q4 drain                                 │
-   J5.2 GDR ──┬── Q4 gate                                       └── D6 ── GND
-              │   CJ2310                                        │
-          R58 10 kΩ                                           PREVGL (C73 10 µF/25 V)
-              │
-             GND       Q4 source ── R59 1.2 Ω ── GND
-                                 └── J5.3 RESE  (peak-current sense back to the panel)
-```
-
-`L8` = `SPH252010H330MT`, 33 µH. **No inductor record**: like `L1`–`L3` it is a
-converter design parameter, and the converter is inside the panel's SSD1677.
-
-### 7.5 microSD ESD and pull-ups **[SCH-T]**, clamps **[SCH-V]**
-
-| Line | ESD clamp | Pull-up | Value |
-|---|---|---|---|
-| `G9_TF_DATA2` | `TVS3` | `R62` | 4.7 kΩ |
-| `G8_TF_DATA3` | `TVS4` | `R63` | 4.7 kΩ |
-| `G12_TF_CMD` | `TVS5` | `R64` | 4.7 kΩ |
-| `G13_TF_CLK` | `TVS6` | `R65` | 4.7 kΩ |
-| `G11_TF_DATA0` | `TVS7` | `R66` | 4.7 kΩ |
-| `G10_TF_DATA1` | `TVS8` | `R67` | 4.7 kΩ |
-| `PYB_TF_DET` | `TVS9` | `R68` | **1 MΩ** — card-detect, not a bus line |
-
-The sheet's own note: *"The `PYB_TF_DET` pin uses an internal pull-up to detect a
-ground connection. It identifies card insertion and wakes up the ESP32."*
-**[SCH-T]**
-
-### 7.6 Passives — no records
-
-**28 capacitors** `C58`–`C85`, **25 resistors** (`R42`–`R44`, `R47`, `R49`–`R54`,
-`R58`–`R68`), **3 test points** `TP13`–`TP15` (`PYB_PDM_EN`, `PYB_TP_EN`, `RST`).
-
-| Ref | Value | Role |
-|---|---|---|
-| `C58`, `C59` | 10 µF/10 V ×2 | IMU / NFC-connector rail decoupling |
-| `C60`–`C62` | 1 µF/25 V ×3 | RTC decoupling |
-| `C63`, `C64` | 100 nF/25 V ×2 | IMU decoupling |
-| `C65` | 10 µF/10 V | LoRa module `VIN_3V3` |
-| `C66`, `C68` | 10 µF/10 V ×2 | `TP_VDD` in/out |
-| **`C67`** | **10 µF/25 V** | **e-paper charge-pump flying capacitor** **[SCH-V]** |
-| `C69`, `C70` | 10 µF/10 V, 100 nF/25 V | M5IOE1 decoupling |
-| `C71`, `C72`, `C73` | 10 µF/25 V ×3 | `EPD_3V3_L3`, `PREVGH`, `PREVGL` **[SCH-V]** |
-| `C74`, `C75` | 4.7 µF/25 V ×2 | at `J5`.4/.5 — panel `VDHR` |
-| `C76` | 10 µF/10 V | `3V3_L2` at the `J6` sub-board connector |
-| `C77`–`C84` | 10 µF/25 V, 1 µF/25 V, 4.7 µF/25 V (mixed) | **`J5`.17–.24 panel rail decoupling** — `VDDD`, `VSH`, `VGH`, `VSL`, `VGL`, `VCOM`; values as the DKE manual specifies |
-| `C85` | 10 µF/10 V | `PDM_VDD` |
-| `R42`, `R43`, `R44` | 10 Ω, 100 kΩ, 22 Ω | IMU/`J3` area **[SCH-T]** — see §9 caveat |
-| `R47` | 22 Ω | RTC `PYG0_RTC_INT` series |
-| `R49` | 100 kΩ | RTC interrupt pull-up to `3V3_L0` |
-| `R50` | 10 kΩ | `Q3` buzzer gate pulldown **[SCH-V]** |
-| `R51`, `R53` | 10 kΩ ×2 | M5IOE1 `NRST` / `G7_PYB_IRQ` |
-| `R52`, `R54` | `NC/1%`, 100 kΩ | M5IOE1 `ADD_SET` — **`R52` not fitted**, `R54` fitted: this pair sets the expander's I²C address |
-| `R58` | 10 kΩ | `Q4` gate pulldown **[SCH-V]** |
-| **`R59`** | **1.2 Ω** | **e-paper DC/DC current-sense resistor (`RESE`)** **[SCH-V]** |
-| `R60`, `R61` | `0R/1%` ×2 | links on `G18_EINK_BUSY` and `PYB_EINK_RST` |
-| `R62`–`R68` | see §7.5 | microSD |
-
----
-
-## 8. Sheets 5 and 6 — the two sub-boards
-
-### 8.1 Sheet 5 — `PaperMono KEY RGB.SchDoc` (23)
-
-| Ref | Part / value | Function | Record |
-|---|---|---|---|
-| `U1` | `LMD4737T261-AC02` | PDM MEMS microphone | [generic/lmd4737t261-ac02-pdm-microphone](../../../components/generic/lmd4737t261-ac02-pdm-microphone/README.md) |
-| `LED1` | `RS-C1415MBAR` | side RGB indicator | [generic/rs-c1415mbar-rgb-led](../../../components/generic/rs-c1415mbar-rgb-led/README.md) |
-| `J1` | `AXE612124D` | board-to-board header, mates `J6` sheet 4 | [panasonic/axe612124d](../../../components/panasonic/axe612124d/README.md) |
-| `S1`, `S2`, `S3` | `SW` | tactile switches: power button, `G2_KEY1`, `G3_KEY2` | **unidentified**, §9 |
-| `DR1` | `ESD5311` | ESD clamp on **`PWR_BTN`** | [generic/esd5311](../../../components/generic/esd5311/README.md) |
-| `DR2` | `ESD5311` | ESD clamp on **`G2_KEY1`** | idem |
-| `DR3` | `ESD5311` | ESD clamp on **`G3_KEY2`** | idem |
-| `R1` | 10 kΩ | **`PWR_BTN` pull-up to `3V3_L0`** — the always-on rail |
-| `R2`, `R5` | 10 kΩ ×2 | `G2_KEY1`, `G3_KEY2` pull-ups **to `3V3_L2`** |
-| `R3`, `R4` | 22 Ω ×2 | series damping on `G46_PDM_DAT`, `G45_PDM_CLK` |
-| `R6`, `R7`, `R8` | 560 Ω, 820 Ω, 1 kΩ | RGB LED ballast — blue, green, red |
-| `C1`, `C3`, `C4` | 100 nF/10 V ×3 | switch debounce at `S1`, `S2`, `S3` |
-| `C2` | 100 nF/10 V | `PDM_VDD` decoupling |
-| `C5` | 10 µF/10 V | `3V3_L2` bulk |
-| `L1` | 2 nH | `PDM_VDD` feed — no record (supply bead) |
-
-> **The power button pulls up to `3V3_L0` while the two user keys pull up to
-> `3V3_L2`.** `3V3_L0` is the always-on rail and `3V3_L2` is switched off in the
-> deep states, so **only the power button can be sensed when the system is at its
-> lowest power level.** That is consistent with sheet 1's power-state table,
-> which lists the power button as the `L0`/`L1` wake path and the keys only from
-> `L2`. **[SCH-T]** + **[INF]**
-
-### 8.2 Sheet 6 — `02 Paper Mono NFC.SchDoc` (43)
-
-| Ref | Part / value | Function | Record |
-|---|---|---|---|
-| `U2` | `ST25R3916-AQWT` | NFC reader/writer + card emulation, I²C `0x50` | [stmicroelectronics/st25r3916](../../../components/stmicroelectronics/st25r3916/README.md) |
-| `U1` | `AW35122FDR` | load switch gating `VCC_3V3` for the whole sub-board | [awinic/aw35122](../../../components/awinic/aw35122/README.md) |
-| `X1` | **`27.12MHZ(XL7EL89CMI-111YLC)`** | **27.12 MHz crystal — the NFC carrier reference** | [generic/xl7el89cmi-111ylc-27.12mhz-crystal](../../../components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md) |
-| `J1` | `BTB0.408-10PLBDR-G41` | board-to-board, mates `J3` sheet 4 | [generic/btb0.408-10plbdr-g41](../../../components/generic/btb0.408-10plbdr-g41/README.md) |
-| `ANT1` | — | **PCB loop antenna**: 4 turns, 25 × 25 mm, 0.25 mm trace, 0.3 mm gap, 17 µm (0.5 oz) copper — stated as a layout note on the sheet | **unidentified** (it is copper, not a part), §9 |
-| `L1`, `L2` | 270 nH ±5% ×2 | **EMC filter inductors** on `RFO1`/`RFO2` |
-| `C14`, `C15` | 10 pF ×2 | **27.12 MHz crystal load capacitors** on `XTO`/`XTI` |
-| `C2`–`C13` | 220 pF, 10 pF, 150 pF, 680 pF, 160 pF (mixed) | **the antenna matching and EMC filter bank** — `RFI_P`/`RFI_N`, `ANT1_P`/`ANT1_N` |
-| `C16`–`C31` | 10 nF / 10 µF alternating ×16 | ST25R3916 supply decoupling (`VDD_AM`, `VDD_TX`, `VDD_RF`, `VDD_A`, `VDD_D`, `VDD_IO`, `VDD_DR`) |
-| `C1` | 10 µF | `VCC_3V3` bulk at the load switch |
-| `R1` | 0 Ω | `3V3_L2` → `U1` input link |
-| `R2` | `NC` | `PYB_RFID_RST` → `U1` `EN` — **not fitted** |
-| `R3`, `R5` | 2 Ω ×2 | **antenna series damping** on `ANT1_P` / `ANT1_N` |
-| `R4` | 0 Ω | `I2C_EN` tied to `VCC_3V3` — **selects I²C, not SPI** |
-
-> `R4` = 0 Ω to `VCC_3V3` on `I2C_EN` is the interface selection. The sheet spells
-> it out: *"`I2C_EN`=VDD; I2C mode / `I2C_EN`=GND; SPI mode"*. **[SCH-T]**
-
-### 8.3 The 11 `NC` positions — drawn but not fitted
-
-Counted in the 289 because they are placed symbols; **not on the board**.
-
-| Ref | Sheet | Value | What not fitting it means |
-|---|---:|---|---|
-| `R1`, `R2` | 2 | `NC/1%` | **No USB-PD.** The IP2315's `CC1`/`CC2` never reach the connector |
-| `R6` | 2 | `NC/1%` | IP2315 `nACOK` unused |
-| `R8`, `R13` | 2 | `NC` | charger I²C series links open — part of why `0x75` is off the bus |
-| `R18` | 2 | `NC/1%` | IP2315 `LED3` unused |
-| `R25` | 2 | `NC/1%` | `U8` `EN` pulldown omitted |
-| `C26` | 2 | `NC/50V` | frontlight output capacitance reduced to `C25` alone |
-| `C41`, `C42` | 3 | `NC(TBD)` | **antenna match positions left open and explicitly "TBD"** |
-| `R52` | 4 | `NC/1%` | M5IOE1 address strap left at its default |
-| `R2` | 6 | `NC` | `PYB_RFID_RST` does **not** drive the NFC load switch through this resistor |
-
-> ⚠ **`R2` sheet 6 = `NC` deserves attention.** The device record establishes
-> ([`gaps-and-conflicts.md`](gaps-and-conflicts.md) R9) that `PYB_NFC_EN` and
-> `PYB_RFID_RST` are the same wire across the board-to-board pair, and that it
-> drives a load-switch enable rather than a reset. The resistor drawn in that
-> path is **not fitted**, and `R2`'s other end is marked `NC` too. What actually
-> enables `U1` sheet 6 was **not resolved** from this PDF and is listed in §9.
-
----
-
-## 9. Unidentified — 12 positions, and what would resolve each
-
-Per the method, **no part number is guessed**. Each of these is a real placed
-component whose part could not be established from the published evidence.
-
-| Ref | Sheet | What the schematic says | What would resolve it |
-|---|---:|---|---|
-| `D1` | 2 | `DSK34` | A `DSK34` marking search returned nothing conclusive. A photograph of the top marking, or M5Stack's BOM |
-| `LED1` | 2 | no part string | Board photo; it is the charger's status LED |
-| `J1` | 2 | no part string, 6-pin | Board photo of the frontlight connector, or a replacement-part listing |
-| `FT1` | 3 | `ICMF062P900MFR` | A common-mode choke; the code resembles a `0603`/`90 Ω` USB CMC but **no manufacturer was established**. Vendor cross-reference needed |
-| `ANT1` | 3 | no part string | Whether it is a chip antenna or PCB trace is not shown. A board photo settles it |
-| `J4` | 4 | no part string, 8-pin FPC | Board photo; the mating flex is part of the touch panel assembly |
-| `U20` | 4 | `MicroSD` only | Board photo of the socket; the *interface* is fully documented |
-| `BUZZER1` | 4 | `ER103` | `ER103` looks like a series code for a 10 mm magnetic buzzer but no vendor was confirmed |
-| `S1`, `S2`, `S3` | 5 | `SW` only | Board photo, or the mechanical drawing |
-| `ANT1` | 6 | layout note only | It is a **PCB trace loop**, not a purchased part; "unidentified" is the wrong frame — there is nothing to buy |
-| `L1`–`L3`, `L8` | 2, 4 | `FTC…`, `SPH…` series codes | Series codes without a manufacturer prefix. An LCSC/Digi-Key cross-reference on the full code |
-| `U1` sheet 6 enable | 6 | `R2` = `NC` | What drives `U1`'s `EN` when `R2` is unfitted. Needs NFC sheet **1 of 2**, which is unpublished |
-
-Three further caveats that are **not** identity questions but are unresolved:
-
-- **`R42`, `R43`, `R44` values** (sheet 4). The text layer renders these as
-  fragmented single characters (`1 0 R / 1 %`, `2 2 R / 1 %`) because they sit in
-  a dense area. 10 Ω / 100 kΩ / 22 Ω is the reading, **[SCH-T]** only, and it was
-  not confirmed against a rendered image.
-- **`J4`'s pin numbering** (sheet 4). The signal set is solid; the 1-to-8 order is
-  not, and is [deliberately not asserted](../../../components/focaltech/ft6336g/README.md#41-signals-at-j4-sch-sheet-4).
-- **Capacitor dielectrics and case sizes.** Absent from the document entirely.
-
----
-
-## 10. What has a component record
-
-**56 of the 290** placed components resolve to a record; **13** are unidentified
-(§9); the remaining **221** are ordinary passives left without one. The
-[component index](../../../components/README.md) is the entry point; these are
-the ones this board contributes.
-
-**Created before this pass:** IP2315 · AW32901FCR · AW39112DNR ×2 · AW35122FDR ×4
-· AW9967DNR · SSP7615-33DFR ×4 · JW5712 · M5PM1 · M5IOE1 · PY32L020F15U6 ·
-ESP32-S3R8 · XM25UH128DHIQT · 40 MHz crystal · BMI270 · RX8130CE · FT6336G ·
-DEPG0397BBS770F3 · SSD1677 · Stamp-LoRa-1262 · SX1262 · ST25R3916 ·
-LMD4737T261-AC02 · RS-C1415MBAR.
-
-**Created by this pass (2026-09-01):**
-
-| Record | Instances | Designators |
-|---|---:|---|
-| [`TYPEC-302-BRP16SC08`](../../../components/generic/typec-302-brp16sc08/README.md) | 1 | **`USB`** sheet 2 |
-| [`FPC0.5-SMT-24P-B`](../../../components/generic/fpc0.5-smt-24p-b/README.md) | 1 | `J5` sheet 4 |
-| [`AXE512127D`](../../../components/panasonic/axe512127d/README.md) | 1 | `J6` sheet 4 |
-| [`AXE612124D`](../../../components/panasonic/axe612124d/README.md) | 1 | `J1` sheet 5 |
-| [`BTB0.408-10PLBDR-G41`](../../../components/generic/btb0.408-10plbdr-g41/README.md) | 2 | `J3` sheet 4 · `J1` sheet 6 |
-| [`ESD5311`](../../../components/generic/esd5311/README.md) | **12** | `TVS1`, `TVS2` sheet 2 · `TVS3`–`TVS9` sheet 4 · `DR1`–`DR3` sheet 5 |
-| [`SK2301AAT`](../../../components/generic/sk2301aat/README.md) | 1 | `Q5` sheet 2 |
-| [`SK2302AAT`](../../../components/generic/sk2302aat/README.md) | 2 | `Q2` sheet 2 · `Q3` sheet 4 |
-| [`CJ2310`](../../../components/changjing/cj2310/README.md) | 1 | `Q4` sheet 4 |
-| [`CJ3439KDW`](../../../components/changjing/cj3439kdw/README.md) | 1 | `Q1` sheet 2 |
-| [`RB162VAM-20TR`](../../../components/rohm/rb162vam-20tr/README.md) | 1 | `D2` sheet 2 |
-| [`1N4148WS`](../../../components/generic/1n4148ws/README.md) | 1 | `D3` sheet 4 |
-| [`1N5819WS`](../../../components/generic/1n5819ws/README.md) | 3 | `D4`, `D5`, `D6` sheet 4 |
-| [`XL7EL89CMI-111YLC` 27.12 MHz](../../../components/generic/xl7el89cmi-111ylc-27.12mhz-crystal/README.md) | 1 | `X1` sheet 6 |
-| [`100K-RNTC` thermistor](../../../components/generic/100k-rntc-thermistor/README.md) | 1 | `R15` sheet 2 |
-| [1150 mAh Li-ion cell](../../../components/generic/papermono-1150mah-liion-cell/README.md) | 1 | at `J2` sheet 2 |
-
----
-
-## 11. ⚠ Conflict raised by this pass — the NTC does not measure the cell
-
-Several places in this device's record describe the battery as **"NTC-sensed"**
-and put the thermistor **at `J2`**, for example
-[`README.md`](README.md) ("1150 mAh Li-ion, NTC-sensed"),
-[`features/battery-and-charging.md`](features/battery-and-charging.md)
-("battery (J2, 1150 mAh + 100K NTC)") and
-[`pinouts-and-buses.md`](pinouts-and-buses.md) ("`J2` … Battery, with a
-`100K-RNTC` thermistor").
-
-**The schematic does not support the thermistor being in the battery pack.**
-**[SCH-V]**
-
-| Claim | Evidence |
-|---|---|
-| `J2` has **two pins only** | Rendered at 200 dpi: a 2-contact symbol, pin 2 → `VBAT_L0`, pin 1 → GND, `CON2_SMD` printed beneath, `C13` = 22 µF/10 V across. There is no third contact and no thermistor pin |
-| `R15` (`100K-RNTC`) is a **board part** | It carries a reference designator in the `R` series, is placed on sheet 2 beside the IP2315, and connects `NTC` (pin 26) to GND in parallel with `R16` = 82 kΩ |
-
-So the arrangement is: **a 100 kΩ NTC soldered to the mainboard on the charger's
-`NTC` pin**, not a thermistor inside the cell reaching the board through the
-connector. Two consequences, both safety-relevant, both `inferred`:
-
-1. **What is being measured is board temperature near the charger, not cell
-   temperature.** Those track each other loosely at best, and diverge exactly when
-   it matters — a cell going into thermal runaway heats faster than the PCB
-   beneath it.
-2. **A replacement cell needs no thermistor**, and fitting a 3-wire pack would not
-   improve the protection, because there is nowhere for the third wire to go.
-
-**This conflict is recorded, not resolved.** It is possible M5Stack places `R15`
-physically under the cell so that it is thermally coupled to it; nothing in a
-schematic can show that, and a board photograph or a thermal measurement would
-settle it. The wording in the records above should be read as "the charger has
-NTC-based temperature qualification", which is true, rather than "the battery
-pack contains a thermistor", which this evidence does not support. Date
-2026-09-01. See also the
-[battery record](../../../components/generic/papermono-1150mah-liion-cell/README.md)
-and the [thermistor record](../../../components/generic/100k-rntc-thermistor/README.md).
-
----
-
-## 12. Reproducing this census
-
-```bash
-cd scratch/m5stack-papermono
-nix-shell -p poppler-utils --run '
-  for n in 1 2 3 4 5 6; do
-    pdftotext -bbox -f $n -l $n \
-      pdf/PaperMono_SCH_V0.6.2_20260522.pdf pdf/bbox-p$n.xml
-  done'
-python3 tools/census.py          # corrected counts + gap analysis
-python3 tools/co_values.py       # designator -> adjacent-text dump
-python3 ../../tools/altium_pdf_render_sheet.py 4      # a sheet as ordered text
-python3 ../../tools/altium_pdf_pin_table.py 4 J5      # one component's pins
-```
-
-To re-read a block as an image, which is what **[SCH-V]** means:
-
-```bash
-nix-shell -p poppler-utils -p imagemagick --run '
-  pdftoppm -r 200 -png -f 2 -l 2 pdf/PaperMono_SCH_V0.6.2_20260522.pdf out
-  magick out-2.png -crop 400x260+1850+230 +repage -resize 250% crop.png'
-```
-
-`executed-success` for all of the above on 2026-09-01.
-
----
-
-## 13. Authoritative sources
-
-| ID | Title | Publisher | Class | URL | Retrieved | Version | Establishes |
-|---|---|---|---|---|---|---|---|
-| S1 | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | **V0.6.2**, 6 sheets, A4 landscape, Altium | the entire census, every value and every net cited here. Local: [`artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf`](artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf) |
-| S2 | PaperMono product page | M5Stack | primary | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | — | 1150 mAh cell capacity; SKU C153 |
-
-Component datasheets acquired for the records created by this pass are hashed in
-each component's own **Local artifacts** table, and indexed from
-[`sources.md`](sources.md).
-
-## Related pages
-
-- [PaperMono device record](README.md) — start here
-- [`pinouts-and-buses.md`](pinouts-and-buses.md) — the wiring tables this BOM supports
-- [`power-architecture.md`](power-architecture.md) — what the rails on sheet 2 do
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — board-wide unresolved items
-- [Component index](../../../components/README.md)
diff --git a/devices/m5stack/papermono/commands.md b/devices/m5stack/papermono/commands.md
deleted file mode 100644
index a3f4a84..0000000
--- a/devices/m5stack/papermono/commands.md
+++ /dev/null
@@ -1,895 +0,0 @@
-# PaperMono — command ledger
-
-> ## No command in this ledger was run against physical hardware.
->
-> **There is no PaperMono in this session and none could be bought — the product
-> has been out of stock since nine minutes after launch.** Every command below
-> operates on *documents, archives and binaries*: HTTP fetches, PDF parsing,
-> `git` clones, hash checks and static binary inspection. The one section that
-> describes touching a device — [Vendor build and flash procedure](#vendor-build-and-flash-procedure)
-> — is transcribed from vendor documentation and is marked **`reported-working`**,
-> which means *the vendor says so and nobody here has tried it*.
->
-> Nothing in this file may be cited as evidence of device behaviour.
-
-## Status vocabulary
-
-| Status | Meaning |
-|---|---|
-| **`executed-success`** | Run in this session; the stated output was observed |
-| **`executed-failed`** | Run; failed. Recorded because the failure is the finding |
-| **`reported-working`** | Published by the vendor or a third party as working. **Not run here** |
-| **`inferred`** | Reconstructed from observed artifacts; plausible but not itself executed as written |
-| **`not-tested`** | Written down, never run, no external claim either |
-
-## Environment
-
-Every `executed-*` command below was run on this host on **2026-09-01**.
-
-| | |
-|---|---|
-| OS / kernel | Linux 6.18.44 (NixOS) |
-| Shell | GNU bash 5.3.15(1)-release, x86_64-pc-linux-gnu |
-| `curl` | **8.21.0** (OpenSSL 3.6.3, zlib 1.3.2, brotli 1.2.0, zstd 1.5.7), release 2026-06-24 |
-| `python3` | **3.14.7** (confirmed by the `cpython-314` bytecode cache left beside the tools) |
-| `git` | **2.55.0** |
-| `gh` | **2.97.0** (nixpkgs) |
-| `sha256sum`, `od`, `stat` | GNU coreutils **9.11** |
-| `pdftotext`, `pdftoppm`, `pdfinfo` | poppler **26.06.0**, supplied ephemerally by `nix-shell -p poppler-utils` — **not installed on the host** |
-
-> **A version caveat worth stating.** The user-agent ladder used by the fetch
-> helpers hardcodes the string `curl/8.5.0`. That is a *chosen identity*, not this
-> host's real default, which is `curl/8.21.0`. Wherever this record says "plain
-> curl worked", it means "a request identifying itself as `curl/8.5.0` worked".
-
-## Paths
-
-All working directories are given **as this repository sees them** — relative to
-the `hardware-doc` repository root:
-
-| Path here | What it is |
-|---|---|
-| `scratch/m5stack-papermono/` | the working tree for this pass (a symlink into `../repo-archive/scratch/hardware-doc/`) |
-| `devices/m5stack/papermono/artifacts/` | the artifacts kept in this repository |
-| `tools/` | the repo's parsers, including the three Altium tools below |
-
-From the *consuming* repository the same paths are reachable as
-`doc/hardware/scratch/…` and `doc/hardware/tools/…`.
-
----
-
-## Contents
-
-- [1. Artifact acquisition and content validation](#1-artifact-acquisition-and-content-validation)
-- [2. PDF text, metadata and raster extraction](#2-pdf-text-metadata-and-raster-extraction)
-- [3. Altium PDF tooling](#altium-pdf-tooling)
-- [4. M5Burner firmware retrieval](#4-m5burner-firmware-retrieval)
-- [5. Firmware image inspection](#5-firmware-image-inspection)
-- [6. Source repository acquisition and verification](#6-source-repository-acquisition-and-verification)
-- [7. Vendor build and flash procedure](#vendor-build-and-flash-procedure)
-- [8. The vendor PlatformIO configuration, verbatim](#8-the-vendor-platformio-configuration-verbatim)
-
----
-
-## 1. Artifact acquisition and content validation
-
-### 1.1 Fetch a vendor document and record its provenance
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Retrieve the PDFs and HTML pages listed in [`sources.md`](sources.md) and record status, decoded size, SHA-256 and retrieval time in a `.meta` sidecar beside each file |
-| **Working directory** | `scratch/m5stack-papermono/docs/` |
-| **Shell / OS** | bash 5.3.15 on Linux 6.18.44 |
-| **Tool + version** | `curl` 8.21.0; `sha256sum`/`stat` coreutils 9.11 |
-| **Prerequisites** | Network access. No credentials — every URL in this record is public |
-| **Generated files** | `<outbase>.html`, `<outbase>.headers`, `<outbase>.meta` |
-| **Status** | **`executed-success`** — 13 documentation pages, 9 store URLs and 5 M5Burner URLs; every one returned on the **first** request with the Chrome 131 UA, no fallback needed |
-| **Date** | 2026-09-01 |
-
-```bash
-# _tools/fetch.sh <url> <outbase>
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-curl -sSL --compressed --max-time 90 \
-  -A "$UA" \
-  -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' \
-  -H 'Accept-Language: en-US,en;q=0.9' \
-  -D "${out}.headers" \
-  -o "${out}.html" \
-  -w '%{http_code}|%{size_download}|%{content_type}|%{url_effective}' \
-  "$url"
-```
-
-Full script: `scratch/m5stack-papermono/docs/_tools/fetch.sh`.
-
-> **Record the decoded size, not `%{size_download}`.** With `--compressed`, curl's
-> `size_download` is the **gzipped wire size**, which will not match the SHA-256
-> you take over the file on disk. The helper records `bytes` from
-> `stat -c%s` and keeps the wire figure separately as `wire_bytes`. Every byte
-> count in [`sources.md`](sources.md) is the decoded on-disk size.
-
-### 1.2 Validate a downloaded document by content, not by extension
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Establish that a file claiming to be a PDF *is* a PDF, and that a firmware download is an ESP32 image rather than an HTML error page |
-| **Working directory** | `scratch/m5stack-papermono/pdf/` (PDFs) · `…/docs/firmware/` (binaries) |
-| **Shell / OS** | bash 5.3.15 on Linux |
-| **Tool + version** | `od`, `head`, `sha256sum`, `stat` — coreutils 9.11 |
-| **Prerequisites** | The file downloaded |
-| **Expected output** | `%PDF` for a PDF; `e9` for an ESP32 image; no `<html`/`<?xml` in the first 512 bytes |
-| **Status** | **`executed-success`** — all 11 PDFs began `%PDF`; both binaries began `0xE9`; **no download was rejected** |
-| **Date** | 2026-09-01 |
-
-```bash
-# PDF magic — check the bytes, never the Content-Type
-head -c 4 PaperMono_SCH_V0.6.2_20260522.pdf            # -> %PDF
-
-# ESP32 image magic
-od -An -tx1 -N1 C153-PaperMono-UserDemo-v1.2.bin       # -> e9
-
-# no HTML/XML error page hiding behind a 200
-head -c 512 C153-PaperMono-UserDemo-v1.2.bin | tr -d '\0' | grep -c -iE '<html|<\?xml|<!doctype'   # -> 0
-
-# size and fingerprint
-stat -c%s C153-PaperMono-UserDemo-v1.2.bin             # -> 2868208
-sha256sum C153-PaperMono-UserDemo-v1.2.bin
-# -> 72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa
-```
-
-> **Why this is not paranoia.** `datasheet.lcsc.com` returns **HTTP 200 with
-> `Content-Type: text/html`** for URLs that do serve a real PDF — status and
-> content-type both lie, and only the leading `%PDF` tells the truth. The same
-> discipline applied here caught nothing, which is itself the result worth
-> recording: *zero rejections across 13 downloads.* The helper writes a rejected
-> payload to `<name>.REJECTED.txt` rather than deleting it; no such file exists.
-
-### 1.3 Hash every retained artifact
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Produce the fingerprints quoted in [`sources.md`](sources.md) and in each component record |
-| **Working directory** | `scratch/m5stack-papermono/pdf/` |
-| **Tool + version** | coreutils 9.11 |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-for f in *.pdf *.PDF; do
-  printf '%s | %s bytes | ' "$f" "$(stat -c%s "$f")"
-  sha256sum "$f" | cut -c1-64
-done
-```
-
-Observed, in full:
-
-```
-C153_PaperMono_model_size.pdf              |    21346 | b833a3e52594a3175bc131006d41a3eb5662be5936d0b2f25030180033a6703b
-DS_SX1261_2_V2-2-m5stack-mirror.pdf        |  4459535 | 6d783125dbef567954ce53095ad068d0950b2a8de52f95bb2cfde4146c4306c2
-EPD_Module_User_Manual.pdf                 |  8666208 | 6b65f56d5d549a132e5c807eef329fb3e997feab04ac06e8a107f01591618130
-esp32-s3_datasheet_en-m5stack-mirror.pdf   |  1083807 | b6db403d6d5db8d1b4db0c8390ff7e0a7db714b8388e986e1c64bff563f76b61
-M5IOE1_IO_Expander_Datasheet_EN.pdf        |   398463 | 9204d99cb2e03395ffc905e05fbeddf7f9f25de5698a31a65fa439dee700d8d2
-M5PM1_Datasheet_EN.pdf                     |   814731 | c6daffd0ab89d8de50c0a19f35f94321bc6c9511ad017dd242a3e765d88a96b6
-PaperMono_SCH_V0.6.2_20260522.pdf          |  1462039 | b5abecac97cb043a6d1af7a673f2111d40d9254b0b5108635cb924d9b37ad6fa
-RX8130CE_cn-Register-Datasheet-m5stack-…   |  2283323 | 7157dc5692e5e0d84203027b600858e57880ef7a38b9c7d7f8c661a93fc8f3f5
-SSD1677-m5stack-mirror.pdf                 |  3602487 | daf8b726f822f6907529386b8af6fbea6ec5e8ecc7b7af361340be911d632544
-ST25R3916_EN-m5stack-mirror.pdf            |  2241765 | 1170f4d74ff501917262ae42bf81c60c38c11d121e2ea2af6b1e845433befef1
-BMI270-m5stack-mirror.PDF                  |  3830973 | 3ab915ed1d81d0eaa5ff1d1aed62b2b491260c9d59afbf79bb23fb477e015612
-```
-
----
-
-## 2. PDF text, metadata and raster extraction
-
-Poppler is **not installed on this host**; every invocation is wrapped in
-`nix-shell -p poppler-utils`, which is why the wrapper appears verbatim below
-rather than being elided.
-
-### 2.1 Document metadata and page counts
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Establish each document's own revision, producer and date — the `Published/updated` column of [`sources.md`](sources.md) |
-| **Working directory** | `scratch/m5stack-papermono/pdf/` |
-| **Tool + version** | `pdfinfo`, poppler 26.06.0, via `nix-shell` |
-| **Prerequisites** | Nix with a channel able to resolve `poppler-utils`; network on first use |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-nix-shell -p poppler-utils --run "pdfinfo PaperMono_SCH_V0.6.2_20260522.pdf"
-```
-
-Observed (abridged) — and load-bearing, because it establishes the schematic's
-export chain and sheet count:
-
-```
-Title:           New Output
-Creator:         Altium Designer
-Producer:        llPDFLib 3.x
-CreationDate:    Mon Jun  8 19:00:00 2026 CDT
-ModDate:         Mon Jul 27 22:00:05 2026 CDT
-Pages:           6
-```
-
-Three metadata reads that became findings:
-
-```bash
-nix-shell -p poppler-utils --run "pdfinfo SSD1677-m5stack-mirror.pdf"
-# Producer: PDFill: Free PDF Writer and Tools   CreationDate: 2019-01-09   Pages: 46
-#   -> not a Solomon Systech export; and the document numbers itself n/47
-
-nix-shell -p poppler-utils --run "pdfinfo EPD_Module_User_Manual.pdf"
-# Producer: iLovePDF                            ModDate: 2026-08-21        Pages: 30
-#   -> a re-processed copy; cover carries no revision at all
-
-nix-shell -p poppler-utils --run "pdfinfo C153_PaperMono_model_size.pdf"
-# Producer: Adobe PDF Library 18.0.4            CreationDate: 2026-08-20   Pages: 1
-```
-
-### 2.2 Layout-preserving text extraction
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Read revision blocks, register tables and specification tables out of the datasheets and the schematic without opening a viewer |
-| **Working directory** | `scratch/m5stack-papermono/` |
-| **Tool + version** | `pdftotext`, poppler 26.06.0 |
-| **Prerequisites** | The PDFs from §1 |
-| **Generated files** | `pdf/sch-p{1..6}.txt`, `pdf/sch-all.txt` (557 153 B), `pdf/model-size.txt` |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-# whole schematic, and one file per sheet
-nix-shell -p poppler-utils --run "pdftotext -layout pdf/PaperMono_SCH_V0.6.2_20260522.pdf pdf/sch-all.txt"
-for p in 1 2 3 4 5 6; do
-  nix-shell -p poppler-utils --run \
-    "pdftotext -f $p -l $p -layout pdf/PaperMono_SCH_V0.6.2_20260522.pdf pdf/sch-p$p.txt"
-done
-
-# mechanical drawing
-nix-shell -p poppler-utils --run "pdftotext -layout pdf/C153_PaperMono_model_size.pdf pdf/model-size.txt"
-```
-
-**`-layout` is not optional here.** Without it, the schematic's title blocks and
-the datasheets' revision tables lose their column association and become
-unreadable; the same applies to the vendor HTML pages, whose specifications live
-in `<table>` elements (the HTML-to-text helper preserves cells joined with ` | `
-for exactly this reason).
-
-Revision extraction, verbatim, for the rows in [`sources.md`](sources.md):
-
-```bash
-nix-shell -p poppler-utils --run \
-  "pdftotext -f 1 -l 1 -layout BMI270-m5stack-mirror.PDF -"
-# Document revision      1.3
-# Document release date  Nov 2020
-# Document number        BST-BMI270-DS000-05
-
-nix-shell -p poppler-utils --run \
-  "pdftotext -f 155 -l 160 -layout ST25R3916_EN-m5stack-mirror.pdf -" | grep -E 'DS12484 Rev'
-# DS12484 Rev 8            -> revision history table dates rev 8 at 08-May-2023
-
-nix-shell -p poppler-utils --run \
-  "pdftotext -layout DS_SX1261_2_V2-2-m5stack-mirror.pdf -" | grep -m1 'Rev 2.2'
-# Data Sheet  Rev 2.2  Semtech     (footer DS.SX1261-2.W.APP, Dec 2024)
-
-nix-shell -p poppler-utils --run \
-  "pdftotext -f 1 -l 1 -layout RX8130CE_cn-Register-Datasheet-m5stack-mirror.pdf -"
-# ETM50E-09  -- and the body is English despite the _cn filename
-```
-
-> **A gotcha in the mechanical drawing.** `pdf/model-size.txt` comes back as
-> `６２`, `１０１`, `４．８９` — the dimensions are typeset in **full-width CJK
-> numerals**. The text is faithful; it is simply not comparable to ASCII digits
-> without normalisation. Do not conclude the extraction failed.
-
-### 2.3 Word bounding boxes — the input to the Altium tooling
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Produce the per-page XML that the three schematic parsers consume. **Nothing in §3 works without this step** |
-| **Working directory** | `scratch/m5stack-papermono/` |
-| **Tool + version** | `pdftotext`, poppler 26.06.0 |
-| **Generated files** | `pdf/bbox-p{1..6}.xml` (61 006 / 101 824 / 59 009 / 107 504 / 25 060 / 49 966 B) |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-for p in 1 2 3 4 5 6; do
-  nix-shell -p poppler-utils --run \
-    "pdftotext -f $p -l $p -bbox pdf/PaperMono_SCH_V0.6.2_20260522.pdf pdf/bbox-p$p.xml"
-done
-```
-
-### 2.4 Rasterising pages for human reading
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Render sheets and manual pages as images so that extraction results could be **checked by eye** before being asserted. This is the verification step that makes §3 admissible |
-| **Working directory** | `scratch/m5stack-papermono/` |
-| **Tool + version** | `pdftoppm`, poppler 26.06.0 |
-| **Generated files** | `sheets/sch-1.png`, `sheets/sch-2.png` (2339 × 1653 each) · `epd-pages/pg-01…pg-26.png` |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-# schematic sheets 1-2 at 200 dpi -> 2339 x 1653 px for A4 landscape
-nix-shell -p poppler-utils --run \
-  "pdftoppm -f 1 -l 2 -r 200 -png pdf/PaperMono_SCH_V0.6.2_20260522.pdf sheets/sch"
-
-# DKE panel manual, pages 1-10 at 130 dpi -> 1075 x 1521 px for A4 portrait
-nix-shell -p poppler-utils --run \
-  "pdftoppm -f 1 -l 10 -r 130 -png pdf/EPD_Module_User_Manual.pdf epd-pages/pg"
-
-# the pinout and waveform pages again at 140 dpi, where 130 was not legible
-nix-shell -p poppler-utils --run \
-  "pdftoppm -f 15 -l 20 -r 140 -png pdf/EPD_Module_User_Manual.pdf epd-pages/pg"
-```
-
-Cropped renders of dense regions of sheet 2 (`sheets/p2-rails.png` 1498 × 1587,
-`sheets/p2-chargeblock.png` 1511 × 1545) were produced the same way with
-`pdftoppm`'s crop window:
-
-```bash
-nix-shell -p poppler-utils --run \
-  "pdftoppm -f 2 -l 2 -r 200 -x <X> -y <Y> -W <W> -H <H> -png \
-     pdf/PaperMono_SCH_V0.6.2_20260522.pdf sheets/p2-rails"
-```
-
-**Status for the crop specifically: `executed-success` in form, `inferred` in the
-exact window.** The crop rectangles were chosen by eye, one region at a time, and
-the individual `-x/-y/-W/-H` values were not recorded. The command shape is
-reproducible; the precise framing of those two PNGs is not.
-
----
-
-## Altium PDF tooling
-
-Three parsers in [`tools/`](../../../tools/) recover structure from the published
-schematic. They exist because of a **negative result**: `m5stack/M5_Hardware`
-contains no C153 directory, so there is no `.kicad_pcb`, no `.SchDoc` and no
-netlist — the PDF is the only schematic that exists.
-
-**What they actually do.** Altium's PDF publisher emits *invisible* marker text at
-schematic objects: `CO<designator>` at a component outline, `PI<designator><pin>`
-at a pin instance, `NL<netname>` at a net label. Non-alphanumerics are replaced by
-`0`, so the markers are lossy (`G0_BOOT_OUT` → `NLG00BOOT0OUT`) and serve only to
-*locate* objects; the human-readable text beside them supplies the real name.
-
-> ### Read this before trusting any output
->
-> **These tools recover text adjacency, not electrical connectivity.** An
-> unlabelled wire-only connection is invisible to them. Dense regions of sheet 2
-> produced readings that had to be corrected against the rendered sheet (§2.4).
-> **Every pin assertion in this record was cross-checked** either against a
-> rendered sheet or against a second independent source — the vendor firmware,
-> the vendor product page, or the DKE panel manual's own pinout. Where only the
-> extraction supported a claim, the claim is marked `inferred`.
-
-### Prerequisites common to all three
-
-- `pdf/bbox-p{1..6}.xml` from §2.3, **in the current working directory**
-- a `tools/` directory in the current working directory containing
-  `altium_pdf_netlist.py` (the other two `sys.path.insert(0, 'tools')` and import
-  from it)
-- `python3` 3.14.7; **no third-party packages** — the parsers are pure standard
-  library (`re`, `sys`, `math`, `json`, `html`)
-
-> **Filename note, stated because it affects reproduction.** These were run from
-> the scratch tree, where the same three files are named `altium_pdf_words.py`,
-> `pin_table.py` and `render_sheet.py`. The copies now in [`tools/`](../../../tools/)
-> are byte-identical apart from the renamed import
-> (`altium_pdf_words` → `altium_pdf_netlist`) — verified by `diff`. The commands
-> below are written against the **repository** names; the runs recorded as
-> `executed-success` used the scratch names.
-
-### 3.1 `altium_pdf_netlist.py` — marker classification and designator census
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Parse the bbox XML into word records, split glued marker/text runs, and enumerate every reference designator in the document. Also the shared library for the other two tools |
-| **Working directory** | `scratch/m5stack-papermono/` |
-| **Tool + version** | `python3` 3.14.7 |
-| **Expected output** | `total distinct designators: <n>` followed by a sorted JSON list |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-python3 tools/altium_pdf_netlist.py
-```
-
-This is where the board-set finding came from: designators **restart per
-document**, so the census contains three different `U1`s, two `X1`s and two
-`ANT1`s. **A designator is meaningful only together with its sheet number** — the
-PDF concatenates three separate Altium projects (main board, KEY/RGB sub-board,
-NFC sub-board).
-
-> **One regex detail is load-bearing.** The marker pattern uses a negative
-> lookbehind, `(?<![A-Za-z])(CO|PI|NL)([A-Z0-9]+)`. Without it, `GPIO0` parses as
-> `G` + a `PI` marker `O0`, and `SPI2_MOSI` as `S` + a `PI` marker `2` — which
-> silently eats pin names on every MCU sheet. Altium emits each marker as its own
-> text object, so a genuine marker is never preceded by a letter.
-
-### 3.2 `altium_pdf_pin_table.py` — per-component pin/net table
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | For one component on one sheet, list every pin with the text inside the symbol body (the pin name) and the text outside it (the attached net). **This is the tool that produced the pin tables in [`pinouts-and-buses.md`](pinouts-and-buses.md) and resolved the `PYG` ambiguity** |
-| **Working directory** | `scratch/m5stack-papermono/` |
-| **Invocation** | `python3 tools/altium_pdf_pin_table.py <page> <designator> [row-band]` — the optional third argument is the vertical tolerance in points, default `3.5` |
-| **Tool + version** | `python3` 3.14.7 |
-| **Generated files** | `pins/p<page>-<designator>.txt` × 43 |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-# the M5PM1 power-management coprocessor on sheet 2
-python3 tools/altium_pdf_pin_table.py 2 U7 > pins/p2-U7.txt
-
-# the M5IOE1 I/O expander on sheet 4 -- the other half of the PYG finding
-python3 tools/altium_pdf_pin_table.py 4 U17 > pins/p4-U17.txt
-
-# the ESP32-S3R8 on sheet 3
-python3 tools/altium_pdf_pin_table.py 3 U12 > pins/p3-U12.txt
-
-# the e-paper FPC connector on sheet 4, cross-checked against the DKE manual p.7
-python3 tools/altium_pdf_pin_table.py 4 J5 > pins/p4-J5.txt
-
-# everything that mattered, in one sweep
-for spec in 2:U1 2:U2 2:U3 2:U4 2:U5 2:U6 2:U7 2:U8 2:U9 2:U10 2:U11 2:J1 2:J2 2:N2 \
-            3:U12 3:U13 3:X1 3:FT1 3:ANT1 \
-            4:U14 4:U15 4:U16 4:U17 4:U18 4:U19 4:U20 4:U21 4:J3 4:J4 4:J5 4:J6 4:BUZZER1 \
-            5:LED1 5:S1 5:S2 5:S3 5:U1 \
-            6:U1 6:U2 6:J1 6:X1 6:ANT1; do
-  p="${spec%%:*}"; d="${spec##*:}"
-  python3 tools/altium_pdf_pin_table.py "$p" "$d" > "pins/p${p}-${d}.txt"
-done
-```
-
-Observed head of `pins/p2-U7.txt` — the rows that settled the naming question:
-
-```
-# U7 on sheet 2: 21 pin markers, x span 595..762
-  pin |      x | inside symbol (pin name)            | outside (net / value)
---------------------------------------------------------------------------------
-    3 |  595.0 | 3 G0_WAKEin(INT0/2)_IRQout_NEOPIXEL | PYG0_RTC_INT …
-   12 |  595.0 | G4_WAKEin(INT3/4)_IRQout_PWM        | 12 PYG4_IMU_INT …
-   13 |  595.0 | G3_WAKEin(INT3/4)_IRQout_PWM 唤醒源二选一 | 13 PYG3_BL_PWM …
-   17 |  595.0 | G1_IRQout_ADC VCC                   | 17 G1_PY_IRQ …
-   20 |  595.0 | G2_WAKEin(INT0/2)_IRQout_ADC 唤醒源二选一 | 20 PYG2_LoRa_EN …
-```
-
-On the M5PM1 the **symbol pin names** are `G<n>_…` and the **nets** are `PYG<n>_…`;
-on the M5IOE1 (`p4-U17.txt`) it is the other way round. That inversion is the whole
-of [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md),
-and it **refuted** an earlier conclusion in this same session that the vendor page
-was defective.
-
-Three empty results were also produced and are kept deliberately:
-`pins/p2-U1.txt`, `p2-U2.txt`, `p2-U8.txt`, `p5-U1.txt`, `p6-U1.txt`,
-`p6-U2.txt`, `p4-U18.txt`, `p4-U21.txt` are 32–33 bytes — the tool prints
-`no pin markers for <D> on page <N>` and exits 0 rather than guessing.
-**`executed-success` with an empty result is not `executed-failed`.**
-
-### 3.3 `altium_pdf_render_sheet.py` — ordered text rendering of a sheet
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Render a sheet as row-ordered text with the invisible markers stripped and re-attached inline as `[D.pin]` / `<D>`, so a whole sheet can be read — and a §3.2 result checked — without a PDF viewer |
-| **Working directory** | `scratch/m5stack-papermono/` |
-| **Invocation** | `python3 tools/altium_pdf_render_sheet.py <page> [row-tolerance]` — tolerance in points, default `3.0` |
-| **Tool + version** | `python3` 3.14.7 |
-| **Generated files** | `pdf/render-p{1..6}.txt` (6 256 / 8 340 / 5 176 / 8 421 / 2 196 / 4 147 B) |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-for p in 1 2 3 4 5 6; do
-  python3 tools/altium_pdf_render_sheet.py "$p" > "pdf/render-p$p.txt"
-done
-
-# a looser row tolerance for the dense power sheet
-python3 tools/altium_pdf_render_sheet.py 2 4.0 | less
-```
-
-Observed head of `pdf/render-p2.txt`:
-
-```
-  31.6 | 1  2  3  4
-  52.1 | TYPEC  PROTECTION  CHARG  ADC_DET
-  62.6 | <U1>  <L1>  VBAT_L0
-  69.9 | CC1  R1  [R10.1]  [R10.2]  NC/1%  [U10.2]  2  CC1  LX  [U10.11]  11  [L1.1]  [L1.2]
-```
-
-The `<U1>` and `[R10.1]` annotations are the tool's own — component outlines and
-pin instances re-attached from the markers it stripped.
-
-### 3.4 A fourth tool that exists in scratch but not in the repository
-
-`scratch/m5stack-papermono/tools/altium_bom.py` builds a
-designator → nearby-text report. It was **run** (`executed-success`) and used as a
-cross-check on component values, but it was not promoted into
-[`tools/`](../../../tools/) because adjacency to a component outline is a much
-weaker signal than adjacency to a pin marker, and its output required more manual
-correction than it saved. Recorded so nobody re-writes it.
-
----
-
-## 4. M5Burner firmware retrieval
-
-### 4.1 Recovering the API from the SPA bundle
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | The firmware pages are React shells with an empty `<div id="root">`. The download endpoint is not in the HTML |
-| **Working directory** | `scratch/m5stack-papermono/docs/burner/` |
-| **Tool + version** | `curl` 8.21.0, `grep` |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-# 1. the page: 2735 bytes, no content
-curl -sSL -A "$UA" 'https://burner.m5stack.com/firmware/2089640807996628993/' -o fw.html
-
-# 2. follow the module graph: index -> http -> firmware
-curl -sSL -A "$UA" 'https://burner.m5stack.com/assets/index-DpEo0Py5.js'    -o js-index.js
-curl -sSL -A "$UA" 'https://burner.m5stack.com/assets/http-ChO34QIa.js'     -o js-http.js
-curl -sSL -A "$UA" 'https://burner.m5stack.com/assets/firmware-C6nFrscE.js' -o js-firmware.js
-
-grep -o 'var Kn = [^;]*' js-http.js
-# var Kn = `${`/api`.replace(/\/$/,``)}/v1`
-```
-
-**The asset filenames are build-hashed and will change on the next deploy.** The
-durable finding is the *shape*: the API base is `/api/v1`, and
-
-```bash
-curl -s -A "$UA" 'https://burner.m5stack.com/api/firmwares/2089640807996628993'
-# {"msg":"请先登录"}    <- 401, auth-walled          [executed-failed, and that is the finding]
-
-curl -s -A "$UA" 'https://burner.m5stack.com/api/v1/firmwares/2089640807996628993'
-# 200, full JSON                                     [executed-success]
-```
-
-### 4.2 Public metadata
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Establish firmware identity, source type, developer, version and `binFileName` — sources S33–S36 |
-| **Working directory** | `scratch/m5stack-papermono/docs/burner/` |
-| **Tool + version** | `curl` 8.21.0 |
-| **Prerequisites** | None. **No authentication** |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-for id in 2089640807996628993 2091144466157694978; do
-  curl -sSL -A "$UA" "https://burner.m5stack.com/api/v1/firmwares/$id"          -o "api-$id-detail.json"
-  curl -sSL -A "$UA" "https://burner.m5stack.com/api/v1/firmwares/$id/versions" -o "api-$id-versions.json"
-done
-```
-
-Observed, and the reason [`README.md`](README.md) says the vendor's
-"Factory Reset Firmware" link is mislabelled:
-
-```json
-"firmwareName": "PaperMono UserDemo",
-"firmwareDescription": "PaperMono / PaperMono-Lite UserDemo",
-"sourceType": "OFFICIAL"
-```
-
-— one image serves both SKUs, and it is a demo application, not a factory-reset
-image.
-
-### 4.3 Download, with content validation before naming
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Retrieve the two firmware images (S38, S39) |
-| **Working directory** | `scratch/m5stack-papermono/docs/firmware/` |
-| **Tool + version** | `curl` 8.21.0, `od`/`sha256sum`/`stat` coreutils 9.11 |
-| **Prerequisites** | The version ids from §4.2 |
-| **Generated files** | `<name>.bin` and `<name>.bin.meta`; on failure `<name>.REJECTED.txt` |
-| **Status** | **`executed-success`** — both images, `first_byte=0xe9`, **no rejections** |
-| **Date** | 2026-09-01T05:05:22Z and 05:05:25Z |
-
-```bash
-# _tools/getfw.sh <firmwareId> <versionId> <outname>
-
-# 1. the API 302s; capture the Location header rather than following it blind
-api="https://burner.m5stack.com/api/v1/firmwares/${fid}/versions/${vid}/download"
-loc=$(curl -sS -D - -o /dev/null -A "$UA" --max-time 30 "$api" \
-      | tr -d '\r' | awk 'tolower($1)=="location:"{print $2}')
-
-# 2. fetch to a temp file with NO extension
-code=$(curl -sSL -A "$UA" --max-time 300 -o "$tmp" -w '%{http_code}|%{content_type}' "$loc")
-
-# 3. validate by content, then and only then name it .bin
-magic=$(od -An -tx1 -N1 "$tmp" | tr -d ' \n')      # must be e9
-head -c 512 "$tmp" | grep -qiE '<html|<\?xml'      # must not match
-[ "$(stat -c%s "$tmp")" -ge 4096 ] || exit 1
-mv "$tmp" "${name}.bin"
-```
-
-Invoked as:
-
-```bash
-./_tools/getfw.sh 2089640807996628993 2089640808000823298 C153-PaperMono-UserDemo-v1.2
-./_tools/getfw.sh 2091144466157694978 2091144466157694979 crosspoint-paper-mono-cjk-1.5.0-RC
-```
-
-Resulting `.meta`, verbatim:
-
-```
-api_url=https://burner.m5stack.com/api/v1/firmwares/2089640807996628993/versions/2089640808000823298/download
-cdn_url=https://m5burner-cdn.m5stack.com/community/1/2089640807996628993/2089640808000823298/bin/2089640808000823299.bin
-http_status=200
-content_type=application/macbinary
-bytes=2868208
-sha256=72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa
-first_byte=0xe9
-validation=ESP32-image(magic 0xE9)
-retrieved_utc=2026-09-01T05:05:22Z
-```
-
-> **Note the CDN object name.** It is `2089640808000823299.bin` — the version id
-> **plus one** — and bears no resemblance to the `binFileName` the API reports
-> (`C153-PaperMono-ESP32S3R8-UserDemo-V1.2-yaozhenquan-8300e309-20260806_0x00.bin`).
-> Naming the local file after the API's `binFileName` would have been reasonable
-> and wrong; the local names are chosen and the mapping is recorded in the `.meta`.
-> Also note `content_type: application/macbinary`, which is meaningless — one more
-> reason to validate the bytes.
-
----
-
-## 5. Firmware image inspection
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Parse the ESP32 image header, the partition table at `0x8000` and `esp_app_desc_t` at `0x10020`; recover corroborating log strings |
-| **Working directory** | `scratch/m5stack-papermono/docs/firmware/` |
-| **Tool + version** | `python3` 3.14.7 (`_tools/espimg.py`, standard library only); `strings` (GNU binutils) |
-| **Prerequisites** | The `.bin` files from §4.3. **`esptool` was not used and no serial port was opened** |
-| **Generated files** | `esp-image-analysis.txt`, `*.strings.txt` |
-| **Status** | **`executed-success`** — static analysis of a file on disk only |
-| **Date** | 2026-09-01 |
-
-```bash
-python3 ../_tools/espimg.py C153-PaperMono-UserDemo-v1.2.bin       > esp-image-analysis.txt
-python3 ../_tools/espimg.py crosspoint-paper-mono-cjk-1.5.0-RC.bin >> esp-image-analysis.txt
-
-strings -n 6 C153-PaperMono-UserDemo-v1.2.bin > C153-PaperMono-UserDemo-v1.2.strings.txt
-grep -E 'PaperMono|M5PM1|M5IOE1|BMI270|RX8130' C153-PaperMono-UserDemo-v1.2.strings.txt
-```
-
-Observed — and this is the **independent corroboration** of the pin map, because
-it comes from the vendor's compiled artifact rather than the vendor's prose:
-
-```
-I (%lu) %s: [Autodetect] board_M5PaperMono
-[I][%s] M5PM1 initialized at address 0x%02X (I2C: %lu Hz)
-[I][%s] M5IOE1 initialized at address 0x%02X (I2C: %lu Hz)
-I (%lu) %s: PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge
-I (%lu) %s: PM1 shutdown, wake by RX8130 timer  -> PM1 G0 falling edge
-```
-
-The last two confirm **M5PM1 G0 = RTC wake** and **M5PM1 G4 = IMU wake**, and that
-these pins belong to the M5PM1 and not the expander. Note the firmware authors
-write `PM1 G4`, not `PYG4` — the correct nomenclature, unlike the documentation.
-
-`esp_app_desc_t` for the official image:
-
-```
-project_name  PaperMono-UserDemo
-app_version   c78f6c5-dirty
-build_date    Aug  6 2026  16:12:13
-idf_version   v5.5.1
-```
-
-> **`-dirty` means this binary is not reproducible.** It was built from an
-> uncommitted working tree, so no commit of `m5stack/M5PaperMono-UserDemo` will
-> regenerate these bytes. That is why the image is retained in
-> [`artifacts/firmware/`](artifacts/firmware/) rather than referenced by URL.
-
----
-
-## 6. Source repository acquisition and verification
-
-| Field | Value |
-|---|---|
-| **Source / purpose** | Acquire the vendor libraries and demos (S41–S47) and check two specific vendor claims |
-| **Working directory** | `scratch/m5stack-papermono/repos/` |
-| **Tool + version** | `git` 2.55.0; `gh` 2.97.0 for metadata |
-| **Prerequisites** | `gh auth login` already done. **The token is never printed and appears nowhere in this repository** — reference it only as `$(gh auth token)` at point of use |
-| **Status** | **`executed-success`** |
-| **Date** | 2026-09-01 |
-
-```bash
-cd scratch/m5stack-papermono/repos
-
-git clone https://github.com/m5stack/M5PaperMono-UserDemo.git
-git clone https://github.com/m5stack/M5PaperMono-OTP-Demo.git
-git clone https://github.com/m5stack/M5PM1.git
-git clone https://github.com/m5stack/M5IOE1.git
-
-# ~128 MB repo -- blobless, path search only
-git clone --filter=blob:none --no-checkout https://github.com/m5stack/M5_Hardware.git
-
-# both branches needed for the master/develop comparison
-git clone https://github.com/m5stack/M5Unified.git && git -C M5Unified fetch origin develop:develop
-git clone https://github.com/m5stack/M5GFX.git     && git -C M5GFX     fetch origin develop:develop
-
-# metadata: default branch, HEAD, dates, licence, size
-for r in M5PaperMono-UserDemo M5PaperMono-OTP-Demo M5PM1 M5IOE1 M5_Hardware M5Unified M5GFX; do
-  gh api "repos/m5stack/$r" --jq '{name,default_branch,pushed_at,size,license:.license.spdx_id}'
-done
-```
-
-Verification of the two headline findings:
-
-```bash
-# the negative: no C153 anywhere in the published hardware repo
-git -C M5_Hardware ls-tree -r --name-only HEAD | grep -iE 'papermono|c153'
-# -> no output, exit 1.  EXPECTED. This is the result, not a failure.
-
-git -C M5_Hardware ls-tree -r --name-only HEAD | grep -oE 'C1[0-9]{2}' | sort -u | tail
-# -> ... C149 C151 C152     (the SKU sequence stops one short of C153)
-
-# the refutation: PaperMono support is on master AND in the release tags,
-# so the vendor's "#develop" build requirement is stale
-git -C M5GFX     grep -n 'board_M5PaperMono' master -- src/lgfx/boards.hpp
-git -C M5Unified grep -q  'board_M5PaperMono' 0.2.21 -- src/ && echo "in tag 0.2.21"
-git -C M5GFX     grep -q  'board_M5PaperMono' 0.2.28 -- src/ && echo "in tag 0.2.28"
-```
-
-**Nothing in these repositories was compiled, flashed or executed.** Every pin,
-register and address taken from them is transcribed from source text at a cited
-`file:line`.
-
-> **Authenticate rather than rotate user agents.** `api.github.com` limits per
-> identity: 60/h unauthenticated, **5 000/h** with a token. One recursive tree
-> listing can exhaust 60 in a single call, and the resulting 403s carry
-> `X-RateLimit-Remaining: 0` and look exactly like bot-blocking. Check that
-> header before reaching for a UA.
-
----
-
-## Vendor build and flash procedure
-
-> ### `reported-working` — transcribed from vendor documentation, **not executed**
->
-> No device exists in this session. Nothing below has been compiled, flashed,
-> observed to boot, or observed to fail. It is reproduced so that the vendor's
-> instructions can be compared against the vendor's own artifacts — which is how
-> three of the conflicts in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) were
-> found.
-
-| Field | Value |
-|---|---|
-| **Source** | [`docs.m5stack.com/en/arduino/papermono/program`](https://docs.m5stack.com/en/arduino/papermono/program) (S07) and the product page (S01) |
-| **Working directory** | a PlatformIO or Arduino project directory — n/a here |
-| **Shell / OS** | vendor does not state; Arduino IDE is cross-platform |
-| **Tool + version** | Arduino IDE with the M5Stack board package; or PlatformIO with `platform = espressif32@6.12.0`. **The vendor states no Arduino IDE version and no board-package version anywhere** |
-| **Prerequisites** | A PaperMono; a USB-C cable; the libraries below |
-| **Expected output** | Sketch uploads; the example runs on the panel |
-| **Status** | **`reported-working`** |
-| **Date of transcription** | 2026-09-01 |
-
-**1. Install the libraries.** The Arduino page names seven:
-
-```
-M5Unified   M5GFX   M5PM1   M5IOE1   M5UnitUnified   M5Unit-NFC   RadioLib
-```
-
-— "then install all prompted dependencies." **No versions are given for any of
-them.** Note the conflict: `M5UnitUnified` is required here but absent from the
-PlatformIO `lib_deps` on both product pages, while the product pages pin
-`M5Unified` to `#develop`, which this page never mentions — and §6 above shows
-that pin is unnecessary as of the snapshot date.
-
-**2. Select the board.** *"Select the **M5PaperMono** board."* Independently
-corroborated: the shipped binary contains `[Autodetect] board_M5PaperMono` (§5).
-
-**3. Enter download mode.**
-
-```
-Press and hold the power button for about 2 seconds until the red LED flashes,
-then release. The device is ready for firmware flashing.
-```
-
-That is the product page (S01) and the UiFlow2 page (S09), which agree. **The
-Arduino page disagrees**, saying "the reset button on the side … until the side
-LED starts blinking". The schematic shows three switches on the KEY/RGB sub-board
-— `S1` (`PWR_BTN`), `S2` (`G2_KEY1`), `S3` (`G3_KEY2`) — and **no separate reset
-button**, so the power-button reading is correct and the Arduino page is wrong.
-`inferred`, `not-tested`.
-
-**4. Upload.** The page says to open the **`BarGraph`** example and click Upload.
-A bar-graph demo corresponds to none of the 14 advertised API sub-pages and reads
-as boilerplate carried over from another product. Reproduced because it is what
-the vendor says; flagged because it is probably not what you want.
-
-**5. Power control**, from S01/S04:
-
-```
-Power on / reset : briefly press the power button once
-Power off        : press the power button twice in succession
-```
-
-**Two `not-tested` hazards to know before you flash anything:**
-
-- **Octal PSRAM is mandatory.** Without
-  `board_build.arduino.memory_type = qio_opi`, M5GFX aborts display init with
-  `"M5PaperMono need OPI-PSRAM enabled"` — a **blank screen on working hardware**
-  with a single log line, which presents as dead hardware rather than as a build
-  error.
-- **Neither vendor project has an OTA partition.** The official image is a single
-  15 360 K `factory` app. There is no field-update path as shipped.
-
----
-
-## 8. The vendor PlatformIO configuration, verbatim
-
-Reproduced exactly as published on the PaperMono product page (S01). **Status:
-`reported-working`** — it is the only build configuration M5Stack publishes
-anywhere, and it has not been built here.
-
-```ini
-[env:m5stack-papermono]
-platform = espressif32@6.12.0
-board = esp32-s3-devkitm-1
-framework = arduino
-board_build.partitions = default_16MB.csv
-board_upload.flash_size = 16MB
-board_upload.maximum_size = 16777216
-board_build.arduino.memory_type = qio_opi
-build_flags =
-    -DESP32S3
-    -DBOARD_HAS_PSRAM
-    -mfix-esp32-psram-cache-issue
-    -DCORE_DEBUG_LEVEL=0
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-lib_deps =
-    M5Unified = https://github.com/m5stack/M5Unified#develop
-    M5PM1 = https://github.com/m5stack/M5PM1
-    M5IOE1 = https://github.com/m5stack/M5IOE1
-    M5Unit-NFC=https://github.com/m5stack/M5Unit-NFC
-    RadioLib = https://github.com/jgromes/RadioLib
-```
-
-The PaperMono-Lite page (S04) publishes the same block with two differences and
-nothing else: the environment is `[env:m5stack-papermono-lite]`, and
-`M5Unit-NFC` and `RadioLib` are absent from `lib_deps`.
-
-Four observations about this block, all `inferred` from evidence elsewhere in
-this record:
-
-1. **`board = esp32-s3-devkitm-1`** — there is no PlatformIO board definition for
-   the PaperMono; a generic devkit board is used and reconfigured by the flags.
-2. **`board_build.arduino.memory_type = qio_opi`** selects QIO flash + OPI PSRAM.
-   The **shipped factory binary's header reports flash mode `DIO`.** The hardware
-   supports QIO — all four data lines are routed and the flash's `QE` bit is set
-   at the factory — and `sdkconfig.defaults` in the vendor's own ESP-IDF project
-   pins no flash mode, so the DIO header is an IDF default rather than a hardware
-   limit. Documented build config and vendor artifact nonetheless disagree.
-3. **`M5Unified#develop`** is stale — see §6.
-4. **`M5UnitUnified` is missing**, though the Arduino page requires it.
-
-For comparison, the vendor's actual ESP-IDF factory-firmware project (S41) does
-**not** use PlatformIO at all: it is ESP-IDF **5.5.1** with arduino-esp32
-**3.3.10** as a managed component, and it pins ten dependencies at exact commits
-in `repos.json` — including `RadioLib` 7.2.1 at `b91c6af112e423dcb14529ade5827802a14e1015`,
-`M5GFX` `develop` at `02107b828acb3eb782fccd747863638d64c876d7` and `M5Unified`
-`develop` at `2fe93c0c64f12f916e73a0605c86bf1241c06a6b`. **That, not the
-PlatformIO block, is what actually built the shipped image** — and even it will
-not reproduce it, because the image is `-dirty`.
-
----
-
-## Related
-
-- [`sources.md`](sources.md) — every artifact these commands produced or consumed
-- [`research-log.md`](research-log.md) — what was searched, and the retrieval gotchas
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — the conflicts these commands surfaced
-- [`../../../tools/`](../../../tools/) — the parsers themselves
diff --git a/devices/m5stack/papermono/community.md b/devices/m5stack/papermono/community.md
deleted file mode 100644
index a047bce..0000000
--- a/devices/m5stack/papermono/community.md
+++ /dev/null
@@ -1,277 +0,0 @@
-# Community, editorial and project coverage — M5Stack PaperMono
-
-> Snapshot **2026-09-01**, eleven days after launch. Two consecutive broad search passes.
->
-> ## The finding, stated before the evidence
->
-> **At the snapshot date there were zero written independent reviews of this device.** One
-> hands-on video existed, published on day 8, self-described as a first look, carrying a vendor
-> affiliate link. **Every written article traces back to a single vendor blog post.** Hackaday
-> published nothing. Hackster returned nothing reachable. Tom's Hardware returned nothing.
->
-> That is not a criticism of the press. It is a direct consequence of the supply situation:
-> **you cannot review hardware nobody can buy**, and this product was purchasable for
-> approximately nine minutes ([`market-and-pricing.md` §7](market-and-pricing.md#7-availability-history)).
-> A 162-point Hacker News thread and 61 590 video views indicate the opposite of disinterest.
->
-> **The real independent signal is code, not articles** — and it is genuinely strong (§4).
-
-## What this page is, and what it is not
-
-This page catalogues **coverage** — who said what about this device, in what medium, and what
-kind of evidence it is. Its companion, [`projects-and-community.md`](projects-and-community.md),
-covers the **projects themselves** in depth: what each one builds, how, and against which
-hardware.
-
-> **That companion was being written by a parallel session at the time this page was created.**
-> If the link above does not resolve in your checkout, that pass has not landed. Nothing on this
-> page depends on it; §4 here summarises each project's *evidentiary* value only, and deliberately
-> stops short of describing what the code does.
-
-Also related but distinct: [`gaps-and-conflicts.md`](gaps-and-conflicts.md) holds every conflict
-in the whole record; §6 below extracts the subset that came from community claims.
-
-## Contents
-
-- [1. Evidence-type key](#1-evidence-type-key)
-- [2. Written and video coverage](#2-written-and-video-coverage)
-- [3. Discussion threads](#3-discussion-threads)
-- [4. Third-party code — the strongest independent evidence](#4-third-party-code--the-strongest-independent-evidence)
-- [5. Where the conversation is not happening](#5-where-the-conversation-is-not-happening)
-- [6. Claims examined and rejected](#6-claims-examined-and-rejected)
-- [7. Community claims that survived checking](#7-community-claims-that-survived-checking)
-- [8. Prevalence — what the numbers do and do not support](#8-prevalence--what-the-numbers-do-and-do-not-support)
-- [9. Retrieval limitations](#9-retrieval-limitations)
-
----
-
-## 1. Evidence-type key
-
-The method requires each contribution to be classified by what kind of evidence it is, and
-explicitly states that popularity and production quality do not increase authority.
-
-| Code | Meaning |
-|---|---|
-| **M** | **Firsthand measurement** — a number someone produced from an instrument or an instrumented run |
-| **O** | **Firsthand ownership / use report** — "I have one and it did X" |
-| **RD** | **Reproduced documentation** — accurate restatement of a vendor document, adding nothing |
-| **P** | **Demonstrable project** — code that exists and can be read |
-| **I** | **Informed interpretation** — a reasoned inference from documents, correctly flagged or not |
-| **Op** | **Opinion** |
-| **H** | **Hearsay** — attributed to a source the speaker cannot produce |
-| **U** | **Unsupported assertion** |
-| **V** | **Vendor-published** — the origin, not independent coverage |
-
-**Across every item catalogued on this page, the count of `M` — firsthand measurement — is
-one**, and it is a *self-reported* validation claim in a repository README rather than an
-instrumented measurement (§4). There is no measured number about this device from anyone.
-
-## 2. Written and video coverage
-
-| # | Title | Author / channel | Publisher | Date (UTC) | Medium | Evidence | Source |
-|---|---|---|---|---|---|---|---|
-| 1 | "M5Stack Launches PaperMono: A Compact E-Ink Development Terminal for Connected Projects" | M5Stack | shop.m5stack.com | 2026-08-21 | vendor blog | **V** — **the origin of nearly all other written coverage** | S50 |
-| 2 | "New Arrivals: PaperMono & PaperMono-Lite" | M5Stack | YouTube | 2026-08-21 06:59 · 16 938 views | video | **V** | S81 |
-| 3 | "ESP32-S3 handhelds with 3.97-inch e-paper and optional LoRa/NFC" | Giorgio Mendoza | **LinuxGizmos** | 2026-08-21 05:19 · 5 665 views | blog | **RD** — spec restatement, no hardware | S76 |
-| 4 | "M5Stack Paper Mono – An ESP32-S3 e-paper development board with 3.97-inch touchscreen, LoRa, and NFC" | Jean-Luc Aufranc | **CNX-Software** | 2026-08-21 16:43 (mod. 08-22) | blog | **RD + two small `O`/`I` observations** — see below | S77 |
-| 5 | "Dispositivo portátil ESP32-S3 con papel electrónico de 3,97 pulgadas y LoRa/NFC opcional" | — | **MuyLinux** (ES) | 2026-08-23 21:48 | blog | **RD** — a machine-flavoured translation of #3; renders "frontlight" as *faro* ("beacon") | S78 |
-| 6 | "Lilbits: More phone-sized E Ink gadgets" | Brad Linder | **Liliputing** | 2026-08-28 12:10 | blog roundup | **RD**, and **contains a price/configuration error** (§6) | S79 |
-| 7 | **"M5Stack PaperMono: The Ultimate ESP32 Pocket Gadget?"** | **Volos Projects** | YouTube | **2026-08-29 16:21 · 61 590 views** | video | **O + Op** — **the only hands-on found anywhere** | S80 |
-| 8 | "Unboxing multiple M5Stack products in one time!" | IAMLIUBO | YouTube | 2026-08-25 · **145 views** | video | **O** — genuine unboxing including both SKUs, negligible reach, no spec claims | S82 |
-| 9 | Tux Machines aggregator items (≥ 4 URLs) | — | news.tuxmachines.org | 2026-08-21/22 | aggregator | **RD** — verbatim re-syndication of #3. **Rejected as coverage**; noted only because it inflates search-result counts | S83 |
-
-### The two independent observations in the entire written corpus
-
-Both are CNX-Software's, and both are small enough to quote in full:
-
-1. **"epd_fastest – 0.07 s; note: ghosting visible in demo"** — an observation of **the vendor's
-   demo video**, not of hardware. Evidence type **I**, correctly scoped by CNX itself. It is
-   nonetheless the only thing anyone has said about this display's real-world behaviour, and it
-   is consistent with the vendor's own precaution to perform a full refresh every ~10 partial
-   refreshes.
-2. **"It's not listed on AliExpress (anymore)"** — an availability observation, **independently
-   reproduced here on 2026-09-01** (S58). Evidence type **O**, and it holds.
-
-CNX also has a **dimension conflict** with the vendor: 101 × 61 × 7.95 mm against the docs'
-62.0 × 101.0 × 8.0 mm. Neither was measured; the vendor figure is used throughout this record.
-
-### On the one hands-on video
-
-Volos Projects (day 8, 61 590 views) is the only person who has been seen holding one and
-talking about it. Two caveats that must travel with any citation of it:
-
-- **The description carries a vendor referral link** (`?ref=kmjp2x8a`) — a disclosed commercial
-  relationship, which does not invalidate anything but must be recorded.
-- **It repeats "built-in backlight".** The device has a **frontlight**, which is a different
-  thing on a reflective display: it lights the page from the front, and the panel itself is
-  pure-reflective with no backlight of any kind. A small error, but it is the kind that
-  propagates.
-
-It is self-described as a first look. **No timing, current, range or battery figure appears in
-it.** Evidence type **O + Op**, not **M**.
-
-## 3. Discussion threads
-
-| Venue | Thread | Date | Engagement | Evidence | Value |
-|---|---|---|---|---|---|
-| **Hacker News** | ["M5Stack Launches PaperMono"](https://news.ycombinator.com/item?id=49468593) | 2026-08-27 | **162 points, 58 comments** | **Op + H**, one adjacent **O** | The largest discussion anywhere, and it contains **no firsthand PaperMono measurement at all**. Recurring themes: M5Stack's hardware is good and its software is half-baked; everything is out of stock; XTEINK X4 Pro comparisons. `fmajid` gives a firsthand **PaperS3** ownership report ("clearer screen than my Pocketbook Verse") — adjacent, not this device. `dmitrygr` floats porting rePalm. `RobotToaster` raises Meshtastic/MeshCore support as an **open question**, not a claim. Also the origin of the driver-IC hearsay (§6) |
-| **Hacker News** | [earlier submission of the same URL](https://news.ycombinator.com/item?id=49390702) | 2026-08-21 | 2 points, 1 comment | — | **Duplicate.** The submitter later notes it was ~8 h post-announcement and already sold out |
-| **r/M5Stack** | ["Paper Mono coming August 21st"](https://old.reddit.com/r/M5Stack/comments/1vquxa5/paper_mono_coming_august_21st/) | 2026-08-17 | 198 score, 22 comments | **P-claims + Op** | Pre-launch leak from a vendor YouTube Short. The most valuable content in any thread: the `bb_epaper` and freeink.org support claims (§6), and Larry Bank's **correct and precise** statement of the PaperS3/PaperMono panel difference (parallel 4.7"/960×540 against SPI 3.97"/800×480) |
-| **r/M5Stack** | ["Check out what's new this week!"](https://old.reddit.com/r/M5Stack/comments/1vuaneb/check_out_whats_new_this_week/) | 2026-08-21 | 75 score, 17 comments | **V + O + Op** | The vendor's own launch post. Vendor states pre-orders "reached the limit". Multiple independent **failed-purchase** reports (`shackburger`, `9mini-paralyses`). u/async2 surfaces the openelab.de pre-order — the lead that produced the EUR 79.95 observation. u/Tsixom's PaperS3 comparison, **verified accurate line by line** (§7) |
-| r/hackernews, r/hypeurls | "M5Stack Launches PaperMono" | 2026-08-27/28 | 2 and 1 score | — | **Automated HN mirrors. Not independent coverage.** These are the *only* two hits for a site-wide Reddit search of `papermono` |
-| **X / Twitter** | [@henry19840301](https://x.com/henry19840301/status/2090652363434647738) | **2026-08-21 04:09** | 87 likes, 23 665 views | **O — the strongest ownership evidence anywhere** | "Got lucky on Friday — the new M5Stack PaperMono Lite sold out in just one second. And YES I got one!" plus **four photographs**. The author is `github.com/MagicCube`, who then published a hardware-validated project (§4). Ownership corroborated across two independent surfaces |
-| **X / Twitter** | [@berryxia](https://x.com/berryxia/status/2091105450494238837) | 2026-08-22 10:09 | 2 likes, 569 views | **O** (failed purchase) | Asks M5Stack for a restock, reports stock already gone |
-| **X / Twitter** | [@M5Stack](https://x.com/M5Stack/status/2091116748686922069) | 2026-08-22 10:54 | 300 views | **V** | 「要等两三个月了」 — the primary restock statement (§6) |
-| **community.m5stack.com** | — | — | — | — | **Inaccessible.** `/api/search` → **HTTP 401** "A valid login session was not found"; `/search?term=` → 302. `/api/recent` is open and returned 198 topics with **no PaperMono topic** in that window. **No determination possible** (S85) |
-
-**The `community.m5stack.com` row is the most consequential gap on this page.** The vendor's own
-forum is where owner reports for M5Stack products typically appear first, and it is the one venue
-that could not be searched at all. Its absence from this catalogue is an **auth-wall, not a
-negative** — do not read "nothing on the vendor forum" into it. The `/api/recent` window is 198
-topics deep and is a weak negative at best.
-
-## 4. Third-party code — the strongest independent evidence
-
-**Four third-party projects plus a third-party SDK appeared within eleven days of launch.** That
-is the strongest evidence anywhere that units actually shipped and ran. All dates from the GitHub
-API, retrieved 2026-09-01.
-
-| Repository | Created / pushed | Stars | Evidence | What it establishes |
-|---|---|---|---|---|
-| **`MagicCube/free-ink-on-paper-mono`** (S89) | 2026-08-25 / 08-27 | 3 | **M(self-reported) + P + O — the strongest single item** | FreeInk UI on a **PaperMono-Lite**. The README claims a complete verified hardware path: RX8130 time, M5PM1 battery/USB-power/charging telemetry, touch and physical buttons, light/dark switching, **frontlight held at 127/255**, async e-ink refresh with periodic full cleanup, a rectangular-refresh test bed with a PR-ready SDK patch, and "**verified disabling of M5PM1's dangerous default single-click reset**". Author = **Henry Li / @henry19840301**, the same person who posted the 04:09 UTC purchase photographs — **ownership corroborated across two unrelated surfaces** |
-| **`Free-Ink/freeink-sdk`** (S90) | — | — | **I(informed by hardware) + P** | `libs/hardware/BoardConfig/include/PaperMonoBoard.h` is a detailed board bring-up sequencing the **M5PM1 and M5IOE1** — including disabling the PMIC's single-click reset **while preserving its hardware long-hold download escape**. That level of detail is not obtainable from a spec sheet. **Independently corroborates the same M5PM1 finding as the row above** — two sources, one hardware behaviour |
-| **`MingRZou/PaperMono-Launcher`** (S91) | 2026-08-30 | 1 | **P + O** | Self-described "**hardware-validated**", with a photograph captioned "PaperMono-Launcher on real hardware". Explicitly a **port** of [`bmorcelli/Launcher`](https://github.com/bmorcelli/Launcher) from the PaperS3 — concrete evidence that the two platforms are **not drop-in compatible** |
-| **`EggUncle/PaperMonoCalendar`** (S92) | 2026-08-31 | 0 | **P**; ownership **claimed, not shown** | Landscape calendar firmware for C153 with BLE activity tiles and RTC sync. **Commendably honest**: the README states its preview images are software-generated, *not device photographs* (「非设备实拍」), and that all displayed data is fictional sample data. It describes itself as extracted from a real-device project but **shows no hardware** |
-| **`hectorzin/M5PaperMono-HomeAssistant-ESPHome`** (S93) | 2026-08-27 / 09-01 | 0 | **P**, early WIP | ESPHome "fase 1" minimal hardware test (SSD1677 + FT6336G via M5IOE1). **Honest about its own uncertainty** — the display/touch rotation section is labelled "**hipótesis de prueba**", i.e. unverified at time of writing |
-| **`MarsTechHAN/crosspoint-reader-mono`** (S95) | — | — | **P** | The upstream of the CrossPoint e-reader build distributed through M5Burner. A working binary was **published one day after launch** and is retained in this record — see [`factory-firmware.md` §3](factory-firmware.md#3-the-community-image--crosspoint-paper-mono-cjk-150-rc). Note the M5Burner *uploader* is `IAMLIUBO`/`imliubo`, a different person, whose home directory appears in the binary's build paths |
-| `crosspoint-reader/crosspoint-reader` (S94) | — | — | **P**, roadmap only | `ROADMAP.md:40` lists PaperMono among "ESP32-S3 class hardware (X4 Pro, PaperMono, Seeed Sticky)" targets. **Roadmap, not shipped support** |
-| `tanakamasayuki/M5Stack-Arduino-Check` (S96) | — | — | **RD of a toolchain** | Contains `3.3.9/variants/m5stack_papermono/pins_arduino.h` — evidence that the board variant exists in arduino-esp32 3.3.9 |
-
-### What the code evidence supports, and what it does not
-
-**Supported.** Units shipped and boot. The M5PM1 and M5IOE1 can be driven from third-party code.
-The frontlight can be set. The RTC reports time. Battery and charge telemetry can be read from
-the M5PM1. Touch and both buttons respond. Async e-ink refresh with periodic full cleanup works
-well enough to build a UI on. The M5PM1's default single-click reset is disruptive enough that
-**two independent projects disable it** — and one of them documents how to do so without losing
-the download-mode escape.
-
-**Not supported.** Any *number*. No project reports a current, a battery runtime, a refresh time,
-a Wi-Fi throughput, a LoRa range or a temperature. Every claim above is a **self-reported
-functional assertion in a README**, which is real evidence and is not a measurement.
-
-**One claim is unresolved and should not be repeated.** Larry Bank (`bitbank2`) wrote on
-2026-08-17 — four days *before* launch — "I already support the Paper Mono and Paper Color in my
-`bb_epaper` library … I'm also adding both to `trmnl-firmware` (TRMNL BYOD support)", and u/Diirge
-wrote "We also support this in the freeink.org sdk as it's what powers crosspoint." Both were
-necessarily written against documentation and schematics rather than hardware. **A GitHub code
-search of `bitbank2/bb_epaper` for "PaperMono" returned 0 matches on 2026-09-01** (S97). The
-support may be under a different identifier, on an unpushed branch, or it may not have landed.
-**Do not cite `bb_epaper` PaperMono support as fact.** The freeink.org half of the claim *is*
-separately supported — see the `freeink-sdk` row.
-
-## 5. Where the conversation is not happening
-
-Negative results, each from a search that returned a working result page. These are results.
-
-| Venue | Query | Result |
-|---|---|---|
-| **Hackaday** | `hackaday.com/wp-json/wp/v2/search?search=papermono` | **`[]`** — nothing. For contrast the same endpoint returns two older posts for `m5paper` (2021-11-12 weather display; 2026-07-21 "20 FPS on E-Paper Display Without Help") (S84) |
-| **Reddit, site-wide** | `papermono` | **Two results, both bot mirrors of the HN post.** The only genuine discussion is two threads in the vendor's own subreddit |
-| r/esp32, r/eink, r/ereader, r/CrossPointReader, r/einkesp32 | various | **Zero** PaperMono results |
-| Tom's Hardware, Adafruit blog | — | Nothing reachable |
-| **Hackster.io** | `papermono` | `/search?q=` returns 200 but is a **JS shell**; `/search.json` and `/api/v2/projects` both return HTML. **No working path found — inaccessible, not negative** (S87) |
-| **Bluesky** | `app.bsky.feed.searchPosts` | **403 for every user agent tried.** Inaccessible (S86) |
-
-> **A retrieval trap worth reusing.** Reddit tokenises `papermono` and `paper mono` differently.
-> `papermono` returned **0** results within r/M5Stack while `paper mono` returned the two real
-> threads. **Always search both the closed-up and the spaced spelling** of a compound product
-> name, in every subreddit. Recorded in [`research-log.md`](research-log.md) and the crawler
-> access table.
-
-## 6. Claims examined and rejected
-
-Every row here was checked against its own citation. This table is the community-sourced subset
-of [`gaps-and-conflicts.md`](gaps-and-conflicts.md#claims-examined-and-rejected); that page is
-canonical.
-
-| Claim | Source | Evidence type of the claim | Why rejected |
-|---|---|---|---|
-| **"Restock is 2–3 months because they're out of eink driver IC"** | HN `big_toast`, 2026-08-27, citing `x.com/M5Stack/status/2091116748686922069` | **H** | **The cited tweet was retrieved in full, with its parent and thread root.** It says only 「要等两三个月了」 ("two or three months"). The parent merely asks for a restock; the root is a marketing post. **The driver-IC reason appears nowhere in the cited chain.** This is the clearest example on the page of a plausible mechanism attaching itself to a real statement |
-| "I can't remember where I read it, but … they didn't expect a restock until next year" | HN `notatoad`, 2026-08-27 | **H**, self-flagged | Honestly flagged by its own author as unsourced. Recorded, not used |
-| **"$55 … with … NFC, LoRa"** | **Liliputing**, 2026-08-28 | **U** | Factually wrong. **$55 is the Lite, which has neither.** The NFC/LoRa model is $65 |
-| **"PaperMono is the successor to / an upgrade over the PaperS3"** | several launch articles; implied by the naming | **U** | Contradicted by the vendor's own specifications on every measurable display and power axis: **~35 % fewer pixels, 4 grey levels vs 16, 1150 mAh vs 1800 mAh, no expansion port** — and the PaperS3 is **cheaper**. See [`product-history-and-family.md` §4](product-history-and-family.md#4-papermono-is-not-a-successor-to-the-papers3) |
-| **"Bluetooth 5.0 LE + Mesh connectivity"** | CNX-Software, 2026-08-21 | **I** | A reasonable inference from the SoC — the ESP32-S3 does have BLE 5 and Mesh — but **not a vendor claim.** M5Stack's specification tables for both SKUs list **only** "2.4 GHz Wi-Fi", and no BLE bring-up for this board appears in any vendor document or example. Publication inference, presented as specification |
-| **"Half the price of the XTEINK X4 Pro"** | HN `NDlurker`, 2026-08-27 | **U** (the ratio); **I** (the compatibility half) | **No X4 Pro price was captured**, so the ratio is unverifiable. More fundamentally, a sealed reader and a development board are not comparable on price. The *CrossPoint compatibility* half is separately supported |
-| **"Sold out in one second"** | @henry19840301, 2026-08-21, repeated on HN | **Op** / colloquial | The checkable fact is a **nine-minute gap** between storefront publication and the sell-out report. HN user `bahmboo` made the same point at the time. **Record the nine minutes** |
-| **`bb_epaper` supports PaperMono** | `bitbank2` on r/M5Stack, 2026-08-17 | **U**, pre-launch | **0 code-search matches on 2026-09-01** (§4). Unresolved rather than refuted — it may exist elsewhere |
-
-**Six of eight rejected claims come from written or forum sources; none comes from the code.**
-That asymmetry is the practical lesson of this page: on an eleven-day-old product with no
-supply, the repositories are more reliable than the articles.
-
-## 7. Community claims that survived checking
-
-Recorded with the same rigour, because confirming that someone was right is also a result.
-
-| Claim | Source | How it was checked | Outcome |
-|---|---|---|---|
-| **u/Tsixom's PaperS3-vs-PaperMono specification comparison** | r/M5Stack, 2026-08-21 | Checked **line by line** against `docs.m5stack.com` | **Accurate on every point** |
-| Larry Bank's statement of the panel difference — parallel 4.7"/960×540 against SPI 3.97"/800×480 | r/M5Stack, 2026-08-17 | Against both vendor product pages | **Correct and precise**, four days before launch |
-| u/poulpy123: "More expensive, smaller screen and lower resolution that the previous version" | r/M5Stack | Against vendor specifications | **Correct**, and reached independently of this record |
-| **The M5PM1's default single-click reset is disruptive** | `MagicCube/free-ink-on-paper-mono` **and** `Free-Ink/freeink-sdk`, independently | Two unrelated projects describe and disable the same behaviour; the M5PM1 register map supports the mechanism | **Corroborated ×2.** The strongest community-sourced *behavioural* finding in this record, and it is now reflected in [`features/buttons-and-rgb-led.md` §6](features/buttons-and-rgb-led.md#6-the-power-button) |
-| CNX-Software: "not listed on AliExpress (anymore)" | CNX-Software, 2026-08-21 | Independently reproduced 2026-09-01 (S58) | **Holds** |
-| u/async2 surfaces the openelab.de pre-order | r/M5Stack, 2026-08-21 | Retrieved directly; EUR 79.95 "(Vorverkauf)" | **Holds** — this lead produced a row in [`market-and-pricing.md`](market-and-pricing.md#2-current-observations--papermono-c153) |
-
-## 8. Prevalence — what the numbers do and do not support
-
-The method warns that anecdotes establish that an experience *occurred*, not how common it is,
-and that prevalence wording requires a defensible sample.
-
-**What can be said with the sample inspected:**
-
-- **Three independent failed-purchase reports** were found across the two r/M5Stack threads and X
-  (`shackburger`, `9mini-paralyses`, @berryxia), plus one successful purchase (@henry19840301)
-  and one unboxing showing both SKUs (IAMLIUBO). **Sample: two Reddit threads, one HN thread and
-  a targeted X search.** That is enough to say purchases both succeeded and failed on launch day.
-  It is **not** enough to say anything about a rate.
-- **Two of six third-party projects claim hardware validation** and one of those shows a
-  photograph. Sample: six repositories, which is the complete set found by GitHub search and code
-  search on 2026-09-01.
-- **Zero of fifty-eight Hacker News comments contain a firsthand PaperMono measurement.** That is
-  a complete enumeration of one thread, and it is the most defensible prevalence statement on this
-  page precisely because the denominator is known.
-
-**What cannot be said:** anything about reliability, yield, defect rates, real battery life, or
-how the device performs for any workload. Nobody has reported using one for longer than a video.
-
-## 9. Retrieval limitations
-
-Stated so the next pass does not mistake a wall for a finding.
-
-| Limitation | Effect |
-|---|---|
-| **`community.m5stack.com` is auth-walled** (HTTP 401) | The vendor's own forum — the likeliest first home for owner reports — is **entirely unsearched**. This is the largest hole in the catalogue |
-| **Hackster.io has no working search path** | JS shell; `/search.json` and `/api/v2/projects` both return HTML |
-| **Bluesky's public XRPC API returned 403 to every user agent** | The crawler access table's ✓ for Bluesky evidently refers to `bsky.app` HTML, not the API |
-| **DuckDuckGo and Marginalia were both unusable** on 2026-09-01 | DDG returned an HTTP 202 anomaly page — *not* a 403, and easy to mistake for success; Marginalia served a bot-wait interstitial. **Mojeek was the only general web search engine that worked**, and it is how LinuxGizmos, Liliputing and MuyLinux were found at all |
-| **Mojeek result counts are inflated by re-syndication** | Tux Machines dominated pages 2–5. Read the URLs, not the count |
-| **Two passes, one snapshot date** | Everything here describes **2026-09-01**. It is a reproducible broad-coverage snapshot, not proof that no other coverage exists, and it is a statement about an eleven-day-old out-of-stock product |
-| **Videos were not watched in full** | Timestamps were not recorded for either video; the classification of the Volos video rests on its title, description, framing and the absence of numeric claims in the retrieved metadata |
-
-**Re-run this sweep after the restock.** Almost every "zero" on this page is a consequence of
-supply rather than of the product, and the two repositories with hardware validation
-(`MagicCube/free-ink-on-paper-mono` and `Free-Ink/freeink-sdk`) are the highest-value independent
-sources in existence for this device until that changes.
-
-## Related
-
-- [`projects-and-community.md`](projects-and-community.md) — the projects themselves, in depth *(written by a parallel pass; see the note at the top of this page)*
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — the canonical conflict list, including every claim rejected above
-- [`product-history-and-family.md`](product-history-and-family.md) — the dated chronology these items sit in
-- [`market-and-pricing.md`](market-and-pricing.md) — the sell-out evidence and the restock conflict
-- [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) — the XTEINK and PaperS3 comparisons the community makes
-- [`factory-firmware.md`](factory-firmware.md) — the community CrossPoint image, parsed
-- [`compatibility-and-status.md`](compatibility-and-status.md) — community reports keyed to version
-- [`research-log.md`](research-log.md) — every service, query, filter and disposition
-- [`sources.md`](sources.md) — S50, S68–S97
diff --git a/devices/m5stack/papermono/comparisons-and-recommendations.md b/devices/m5stack/papermono/comparisons-and-recommendations.md
deleted file mode 100644
index 1c5aaca..0000000
--- a/devices/m5stack/papermono/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,459 +0,0 @@
-# Comparisons, equivalents and recommendations — M5Stack PaperMono
-
-> Research snapshot **2026-09-01**. **Nothing here was tested against hardware, on either side of
-> any comparison.** Every claim is either a vendor specification, a reading of a schematic or
-> source tree, or an explicit inference — and the labels say which.
->
-> ## The word "equivalent" is used exactly once on this page, and it is a denial
->
-> The method's rule is that something is "equivalent" only when interfaces, electrical behaviour,
-> performance **and** software requirements align for a **stated workload**. On that test, **no
-> device examined here is equivalent to the PaperMono for any workload.** The honest labels are
-> *partial substitute*, *different tier*, or *not a substitute*, and they are applied per workload
-> rather than per product.
-
-## Contents
-
-- [1. The four workloads this page reasons about](#1-the-four-workloads-this-page-reasons-about)
-- [2. The field, in one table](#2-the-field-in-one-table)
-- [3. In-family — M5PaperS3 and M5Paper](#3-in-family--m5papers3-and-m5paper)
-- [4. Same tier — LilyGO T5 series](#4-same-tier--lilygo-t5-series)
-- [5. Waveshare — gap closed 2026-09-01](#5-waveshare--gap-closed-2026-09-01)
-- [6. Adjacent tier — Inkplate (Soldered Electronics)](#6-adjacent-tier--inkplate-soldered-electronics)
-- [7. Different tier — finished appliances and sealed e-readers](#7-different-tier--finished-appliances-and-sealed-e-readers)
-- [8. Clones](#8-clones)
-- [9. Launch-era market fit versus current market fit](#9-launch-era-market-fit-versus-current-market-fit)
-- [10. Use this when / do not use this when](#10-use-this-when--do-not-use-this-when)
-- [11. Alternatives by tier](#11-alternatives-by-tier)
-- [12. Evidence limitations](#12-evidence-limitations)
-
----
-
-## 1. The four workloads this page reasons about
-
-Comparing "e-paper ESP32 boards" as a category produces nonsense, because the category contains
-objects that share a display technology and nothing else. Everything below is scoped to one of
-four workloads:
-
-| # | Workload | What actually decides it |
-|---|---|---|
-| **W1** | **Reading / rendering** — an e-reader, a dashboard, a calendar, anything where the page is the product | Pixels, grey levels, diagonal, refresh quality, battery |
-| **W2** | **Battery-first event-driven sensing** — wake on schedule or motion, show something, sleep for hours or days | Sleep-state architecture, wake sources, quiescent current, battery |
-| **W3** | **Connected identity / telemetry terminal** — NFC read, LoRa uplink, access control | Radios on the board, antenna arrangement, regulatory paperwork |
-| **W4** | **General e-paper development** — attach a sensor, prototype something, learn | Expansion I/O, free GPIO, documentation, library maturity, availability |
-
-The PaperMono is designed for **W2 and W3** — that is what its applications list says (E-Reader,
-E-Paper Signage, Access Control Terminal, Identity Authentication Device, Intelligent
-Transportation Terminal) and what its hardware is: a five-state power state machine, NFC, LoRa,
-and a display that holds its image with no power. The market read it as **W1**
-([`product-history-and-family.md` §7](product-history-and-family.md#7-positioning-audience-and-product-culture)).
-**It is a poor W4 device, and that is not a subtlety — it has no expansion connector at all.**
-
-## 2. The field, in one table
-
-Prices are as observed on the dates given, in the seller's own currency. **Not
-currency-converted** — see [`market-and-pricing.md` §3](market-and-pricing.md#3-why-there-is-no-converted-comparison).
-
-| Device | Price (observed) | Display | Radios | Expansion | Substitute for PaperMono at… | Internal record |
-|---|---|---|---|---|---|---|
-| **M5Stack PaperMono** `C153` | USD 65.00, 2026-09-01, out of stock | 3.97" 480×800, 4 grey, touch, **frontlight** | Wi-Fi 4, BLE, **LoRa SX1262**, **NFC ST25R3916** | **none** | — | this record |
-| **M5Stack PaperMono-Lite** `C153-LITE` | USD 55.00, 2026-09-01, out of stock | same | Wi-Fi 4, BLE | none | **W1, W2** — same board, no radios | [record](../papermono-lite/README.md) |
-| **M5Stack PaperS3** `C139` | USD 59.00, 2026-09-01, **`[EOL]`** | 4.7" 960×540, **16 grey**, two-point touch | Wi-Fi 4, BLE | HC1.25-4PLT (2 GPIO) | **W1 — better.** Not W3 | §3 |
-| **LilyGO T5 E-Paper S3 Pro** | 81.36–88.71, currency unconfirmed, 2026-09-01 | e-paper + touch | Wi-Fi, BLE, **LoRa** (433/868/915/920, ± GPS) | yes | **W3 partial**, **W2 unknown** | none — §4 |
-| **LilyGO T5 e-Paper 4.7" v2.3** | 38.99–44.50, currency unconfirmed | 4.7" | Wi-Fi, BLE | yes | **W4 partial** | none — §4 |
-| **Soldered Inkplate 5 Gen 2** | EUR 74.95 board / **EUR 99.95 with enclosure + battery**, 2026-08-24 | 5.2" **1280×720**, no touch, no frontlight | Wi-Fi, BLE (ESP32-WROVER) | **easyC/Qwiic + broken-out GPIO** | **W4 — better. W1 — better resolution, no frontlight** | [Inkplate 5](../../soldered-electronics/inkplate-5/README.md) · [Gen 2](../../soldered-electronics/inkplate-5-gen2/README.md) |
-| **[Waveshare ESP32-S3-ePaper-3.97](../../waveshare/esp32-s3-epaper-3.97/README.md)** | **USD 34.99–47.99**, 2026-09-01, in stock, 3 SKUs | 3.97" **800×480**, 4 grey, **SSD1677**, no touch, no frontlight | Wi-Fi 4, BLE 5 | **none** — schematic-verified | **closest like-for-like. W4 — no better** | §5 — same SoC, same memory, same panel size and controller |
-| **ZeroWriter Ink** | **USD 285**, Crowd Supply, funded 2024-10-17 | 5.2" 1280×720 | Wi-Fi (disabled by default) | — (finished appliance) | **not a substitute for any of W1–W4** | [record](../../zerowriter/zerowriter-ink/README.md) |
-| **Tanmatsu** | EUR 99.17 ex-VAT / **EUR 119.99 inc. 21 % NL VAT** | **MIPI DSI LCD — not e-paper** | Wi-Fi, BLE, **LoRa**, 802.15.4 | yes | **W3 partial only** | [record](../../nicolai-electronics/tanmatsu/README.md) |
-| **XTEINK X4 / X4 Pro** | **not captured** | sealed consumer reader | — | none | **not a substitute — sealed firmware** | none |
-| **reMarkable / Kindle class** | not captured | large sealed readers | — | none | **not a substitute** | none |
-
-**Read the "Substitute for PaperMono at…" column as the whole point of the table.** Two products
-in this list beat the PaperMono at reading, one beats it at development, and **none of them
-matches it at W3** — an e-paper board with NFC *and* LoRa *and* a frontlight *and* a hardware
-power state machine was not found anywhere in this survey. That is the PaperMono's actual
-position, and it is narrow.
-
-## 3. In-family — M5PaperS3 and M5Paper
-
-The full comparison table lives in
-[`product-history-and-family.md` §4](product-history-and-family.md#4-papermono-is-not-a-successor-to-the-papers3),
-because it is a family fact before it is a purchasing one. The purchasing summary:
-
-| Workload | Verdict | Why |
-|---|---|---|
-| **W1 reading/rendering** | **PaperS3, clearly** | ~35 % more pixels (518 400 vs 384 000), **16 grey levels vs 4**, two-point touch with gestures, 4.7" vs 3.97", **1800 mAh vs 1150 mAh**, and **USD 6 cheaper** |
-| **W2 battery-first sensing** | **PaperMono** | The five-state M5PM1 architecture with RTC and IMU interrupts terminating on the *power manager* has no counterpart on the PaperS3. But see the enormous caveat below |
-| **W3 connected terminal** | **PaperMono, uncontested** | The PaperS3 has no LoRa and no NFC |
-| **W4 development** | **PaperS3** | It has an expansion port (HC1.25-4PLT, 3V3 + GND + 2 GPIO). The PaperMono has **none** |
-
-> ### The W2 verdict is architectural, not measured — and this matters
->
-> **M5Stack publishes power figures for the PaperS3 (9.28 µA low-power / 949.58 µA standby /
-> 154.02 mA operating, at DC 4.2 V) and publishes none at all for the PaperMono.** So the
-> comparison that would settle W2 — the one axis where the PaperMono is supposed to win — cannot
-> be made from vendor data, and nobody has measured it independently. The claim "PaperMono is
-> better for battery-first work" rests entirely on **reading the schematic and believing that
-> more power domains and hardware wake paths beat fewer**. That is a reasonable belief. It is
-> **not a measurement**, and it is the single most important untested claim in this record.
-> See [`performance.md`](performance.md).
-
-**Neither is purchasable.** The PaperS3 is `[EOL]` at M5Stack's own store; the PaperMono is out
-of stock. This comparison tells you what the product line lost, not what to buy today.
-
-**They are not software-compatible.** Different panel interface (parallel `ED047TC1` vs SPI
-`SSD1677`), different touch controller (GT911 vs FT6336G), different RTC (BM8563 vs RX8130CE),
-plus two auxiliary microcontrollers the PaperS3 does not have. The demonstration is
-`MingRZou/PaperMono-Launcher` — an explicit port of a PaperS3 launcher, published 2026-08-30.
-**Porting is real work; budget for it.**
-
-The original **M5Paper** family (`K049`, `K049-B`, `K049-C`) is ESP32, not S3, at 4.7"/960×540.
-`K049` and `K049-C` are `[EOL]`; `K049-B` is still listed at USD 85.00. Its display controller
-is commonly said to be an IT8951 — **that attribution appears on no M5Stack page retrieved in
-this pass and is recorded as unverified.**
-
-## 4. Same tier — LilyGO T5 series
-
-The closest *external* match, and the only third-party e-paper board found that also carries
-LoRa.
-
-| | **LilyGO T5 E-Paper S3 Pro** | **PaperMono** |
-|---|---|---|
-| Price observed 2026-09-01 | **81.36–88.71** — *currency unconfirmed, see below* | USD 65.00 |
-| Published | 2024-11-14 | 2026-08-21 |
-| SoC | ESP32-S3 | ESP32-S3R8 |
-| LoRa | **yes**, 433 / 868 / 915 / 920 MHz variants, some with **GPS** | yes, SX1262 868–923 MHz, FPC antenna |
-| NFC | **no** | **yes**, ST25R3916 |
-| Frontlight | **no** | **yes** |
-| Expansion | yes | **none** |
-| Regional SKUs | **yes** — `H752-*` (China), `USH752-*` (US), `DEH752-*` (EU), at ~$4.50 premium | none |
-| Availability 2026-09-01 | listed | **out of stock** |
-| Internal record | **none** — not researched in this knowledge base | this record |
-
-There is also a **T5 E-Paper S3 Pro Lite** (`K273`, 71.31, published 2026-02-28) — the obvious
-counterpart to the PaperMono-Lite — and the older **T5 e-Paper 4.7" v2.3** at 38.99–44.50, whose
-variants differ on touch and on whether pins are pre-soldered. The small **T5 V2.3.1 / T5s 2.7"**
-boards at 13.04 / 13.91 are a different tier entirely: bare small-panel boards, no enclosure, no
-battery.
-
-> **Currency caveat, and it is not a small one.** `www.lilygo.cc` returned product JSON with
-> numeric prices but **no currency token was present in the fetched markup** — `cart.js`
-> redirected, there was no JSON-LD `priceCurrency` and no `Shopify.currency` object. The
-> storefront presents USD to an unauthenticated visitor, but **that was not confirmed from the
-> retrieved bytes.** Treat every LilyGO number above as *storefront numeric price, currency
-> unconfirmed*. It would be dishonest to write "$81.36" here.
-
-**Verdict by workload.** For **W3** the T5 S3 Pro is a **partial substitute**: it does LoRa, with
-proper regional band SKUs the PaperMono does not offer, but it has **no NFC**, so it covers half
-the workload. For **W4** it is **better** — it has expansion. For **W1** no determination: the
-panel and grey-level details were not captured. For **W2** no determination: no power
-architecture information was gathered, and LilyGO has no record in this knowledge base at all.
-
-**This is the most important gap on the page.** The nearest external competitor is undocumented
-here, so the comparison rests on a storefront listing rather than on a schematic. A LilyGO T5
-S3 Pro record would be the highest-value addition to this knowledge base for anyone weighing
-the PaperMono.
-
-## 5. Waveshare — gap closed 2026-09-01
-
-**Previously this section recorded a gap:** the knowledge base held four
-Waveshare device records and every one was an **LCD** board, so this record's own
-"prefer … a Waveshare ESP32 e-paper board" advice was unsupported. That was
-conflict C24.
-
-It is now closed. [**Waveshare ESP32-S3-ePaper-3.97**](../../waveshare/esp32-s3-epaper-3.97/README.md)
-is a real e-paper board and is the closest like-for-like comparison to the
-PaperMono that exists anywhere in this survey:
-
-| | Waveshare ESP32-S3-ePaper-3.97 | PaperMono |
-|---|---|---|
-| SoC | ESP32-S3R8 | ESP32-S3R8 |
-| PSRAM / flash | 8 MB / 16 MB | 8 MB / 16 MB |
-| Panel | 3.97", 800 × 480, 4 grey | 3.97", 480 × 800, 4 grey |
-| Active area | 86.40 × 51.84 mm | 51.84 × 86.40 mm |
-| Distinguishing hardware | audio codec + mic, SHTC3 temp/humidity, QMI8658A IMU, rotary switch, RTC backup-cell header | **NFC, LoRa, frontlight**, touch, 5-state hardware power manager, enclosure |
-| **Expansion** | **none** | **none** |
-| Radios | Wi-Fi + BLE | Wi-Fi + BLE + **LoRa + NFC** |
-| Panel controller | **SSD1677** | **SSD1677** |
-| PMIC | **AXP2101** (marketed as "TG28") | M5PM1 + M5IOE1 |
-| Price, 2026-09-01 | **USD 34.99–47.99**, in stock | USD 65.00, out of stock |
-| Form | bare development board | finished product in a case |
-
-**The active areas match to 0.01 mm**, transposed, the DPI matches exactly at 235,
-and **both panels carry an SSD1677** — so the two boards plausibly carry the same
-3.97" panel. That is still `inferred`, not established: **Waveshare publishes no
-panel supplier or part number** anywhere. A photograph of the FPC marking on either
-board would settle it.
-See [C-WS8](../../waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws8--is-this-the-same-panel-as-the-papermonos).
-
-> ### ⚠ Corrected 2026-09-01 — the Waveshare board has no expansion either
->
-> An earlier version of this section said the Waveshare board has "headers" and
-> advised taking it *"if the job is to add hardware"*. **That was written before its
-> schematic was read, and it is wrong.**
->
-> The complete connector census is **one USB-C, three PH1.25-2P power/speaker JSTs,
-> the panel FPC and a microSD socket**. No 2.54 mm header, no Qwiic/easyC, no
-> broken-out GPIO. Every usable GPIO is committed, and GPIO35–37 are consumed by the
-> module's octal PSRAM.
->
-> **On W4 the two boards are equally bad.** Neither is the answer to "I need to
-> attach something".
-> ([C-WS1](../../waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards))
->
-> **Waveshare's actual expansion answer is a different, much smaller board.** The
-> [ESP32-S3-ePaper-1.54](../../waveshare/esp32-s3-epaper-1.54/README.md) and
-> [ESP32-C6-ePaper-1.54](../../waveshare/esp32-c6-epaper-1.54/README.md) do carry a
-> **2 × 6, 2.54 mm header** — at **200 × 200**, which is 40 000 pixels against this
-> board's 384 000, for USD 15.99–22.99. That is a real option, and it is a real
-> trade: **you give up 90 % of the display to get the header.**
-
-**Which to choose, by workload.**
-
-| Workload | Take | Why |
-|---|---|---|
-| **W1 reading/rendering** | **Waveshare**, narrowly | Same pixels, same controller, same grey depth, **USD 17–30 cheaper and actually in stock**. The PaperMono answers back with **touch and a frontlight**, which the Waveshare board has neither of — for reading in the dark the PaperMono wins outright |
-| **W2 battery-first sensing** | **PaperMono**, on architecture | Its five-state M5PM1 power manager has no counterpart. But the Waveshare board has an **AXP2101** with programmable rails, a power-key controller and a charged RTC backup cell — a real power architecture, just not a state machine. **Neither has published current figures, so this is unmeasured on both sides** |
-| **W3 connected terminal** | **PaperMono, uncontested** | No LoRa, no NFC on the Waveshare board |
-| **W4 development/expansion** | **Neither — take an Inkplate** | Both have zero expansion. See §6 |
-| **Voice / environmental sensing** | **Waveshare, uncontested** | ES8311 codec, microphone, NS4150B amplifier + speaker, SHTC3, QMI8658A IMU. The PaperMono has no audio path and no environmental sensor |
-
-Neither is a substitute for the other on the other's workload, and calling either
-"better" without naming a workload would be unsupportable.
-
-**Caveats on this comparison, stated plainly.** Nothing here was measured on
-hardware, on either side. The two boards' refresh timings — Waveshare
-3.5 s full / 2.8 s fast / 0.6 s partial, PaperMono 4.71 / 0.34 / 0.07 s via M5GFX —
-are **not comparable as published**: different methods, different waveforms, neither
-independently measured, and Waveshare's own *panel* manual gives different numbers
-again (3 s / 0.3 s at 23 °C) than its board pages
-([C-WS6](../../waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws6--refresh-times-disagree-between-module-and-panel-documents)).
-**Neither vendor publishes a board-level power figure in any state**, so the W2 row
-above is architectural reasoning, not evidence.
-
-## 6. Adjacent tier — Inkplate (Soldered Electronics)
-
-This knowledge base has **full technical records** for the Inkplate 5 and Inkplate 5 Gen 2,
-including parsed KiCad BOMs and netlist-verified pin maps — so this is the one external
-comparison that rests on primary design data rather than a store listing.
-
-| | **Soldered Inkplate 5 Gen 2** | **PaperMono** |
-|---|---|---|
-| Price observed 2026-08-24 | **EUR 74.95** board · **EUR 99.95** with enclosure + battery | USD 65.00 (bare unit, enclosed, battery included) |
-| Processor | **ESP32-WROVER** (original ESP32, module) | ESP32-S3R8 (bare die, QFN56) |
-| Panel | 5.2" **`ED052TC4`, 1280 × 720 (921 600 px)** | 3.97" `SSD1677`, 480 × 800 (384 000 px) |
-| Pixel advantage | **+140 % over PaperMono** | — |
-| Grey levels | **8**, per Soldered's own `features.rst` family table | 4 (vendor claim; the panel manual's optical table says 2 — [C1](gaps-and-conflicts.md#c1--4-grey-levels-versus-2)) |
-| Vendor refresh figures | **full 1.13 s · fast 0.26 s** | `epd_quality` **4.71 s** · `epd_text` 0.45 s · `epd_fast` 0.34 s · `epd_fastest` 0.07 s |
-| Touch | **none** | FT6336G, single-point |
-| Frontlight | **none** | **yes** |
-| LoRa / NFC | **none** | **yes / yes** |
-| I/O expander | **PCAL6416AHF** @ 0x20 (a standard NXP part) | **M5IOE1** @ 0x4F (M5Stack proprietary) |
-| RTC | PCF85063A | RX8130CE |
-| USB | **CH340C USB-UART bridge** | native ESP32-S3 USB |
-| Expansion | **easyC / Qwiic connector + broken-out GPIO** | **none** |
-| Design files | **TAPR Open Hardware License — full KiCad sources published, redistribution permitted** | **Schematic PDF only.** No C153 directory exists in `m5stack/M5_Hardware` (S45, verified negative) |
-| Availability 2026-09-01 | listed | out of stock since launch |
-
-### What this comparison is actually about
-
-**Compare the EUR 99.95 bundle, not the EUR 74.95 board.** The PaperMono is a finished enclosed
-device with a battery; the bare Inkplate is not. Comparing a bare board to an enclosed product is
-the most common way this class of comparison goes wrong.
-
-**For W1 (reading), the Inkplate 5 Gen 2 is the better display by a wide margin** — 2.4× the
-pixels at a larger diagonal, with an EPD PMIC that gives proper multi-level greyscale. It has no
-frontlight and no touch, so it is a better *page* and a worse *interface*.
-
-**For W4 (development), the Inkplate is better in a way that is hard to overstate.** It has an
-expansion connector, broken-out GPIO, a **standard** I/O expander with a public NXP datasheet,
-and — critically — **published KiCad sources under the TAPR OHL**. This record exists only
-because a schematic PDF's invisible Altium marker text could be parsed; the Inkplate records
-exist because the netlist could be read directly. That is a durable difference in how much you
-can find out about a board you own.
-
-**For W2 and W3, the Inkplate is not a substitute at all.** No LoRa, no NFC, and an ESP32-WROVER
-with a conventional power path rather than a five-state hardware state machine.
-
-**Where the PaperMono genuinely wins**: frontlight, touch, radios, size (101 × 62 × 8 mm against
-a 5.2" device), and the power architecture — subject to the same caveat as everywhere else, that
-the power architecture has never been measured.
-
-> ### Do not build a refresh-speed ranking out of those two rows
->
-> The table above is the only place in this record where two vendors' refresh timings sit side by
-> side, and the temptation to conclude "the Inkplate refreshes four times faster" is exactly the
-> kind of comparison the method forbids. Both sets are **vendor-published laboratory figures for
-> unstated configurations**, produced by different companies on different panels with different
-> controllers and different waveform sources, and **neither has been independently reproduced**.
->
-> Worse for the PaperMono side specifically: its four numbers are M5GFX figures for **a LUT set
-> that may no longer be the shipped one** — M5GFX `develop` has replaced `lut_quality` and
-> `lut_text` outright — and M5Stack's own advice is to bypass M5GFX and use the panel maker's OTP
-> waveforms instead, for which **no timing is published at all**. See
-> [`performance.md` §2](performance.md#2-the-vendors-m5gfx-refresh-timings).
->
-> What the rows *do* legitimately support: both vendors consider sub-second partial refresh
-> normal for their products, and the PaperMono's slowest published mode (4.71 s) is in the same
-> region as the DKE panel manual's own **4-second maximum image update time**, which is a
-> different source agreeing about the order of magnitude. That is as far as the evidence goes.
-
-## 7. Different tier — finished appliances and sealed e-readers
-
-Listed because they get named as competitors, **not because they are substitutes**.
-
-| Device | Price | Why it is a different tier |
-|---|---|---|
-| **[ZeroWriter Ink](../../zerowriter/zerowriter-ink/README.md)** | **USD 285**, Crowd Supply, funded 2024-10-17, 585 backers, $147 538 | A **finished writing appliance**: 5.2" 1280×720, hot-swappable 60 % mechanical keyboard, **two ESP32s**, boots straight into a text file, no wireless by default. Its mainboard is a **respin** of the Inkplate 5 Gen 2 — 8 parts added, 14 removed, 20 values changed against the stock board — not the stock product. Comparable to the PaperMono only in the loosest "e-paper + ESP32" sense |
-| **[Tanmatsu](../../nicolai-electronics/tanmatsu/README.md)** | **EUR 99.17 ex-VAT / EUR 119.99 inc. 21 % NL VAT** ([pricing](../../nicolai-electronics/tanmatsu/pricing-and-dimensions.md)) | ESP32-**P4** handheld with a QWERTY keyboard and LoRa, but a **MIPI DSI LCD — not e-paper**. Overlaps the PaperMono on "hackable pocket terminal with LoRa" and on nothing else. If your W3 requirement is LoRa telemetry with a keyboard and you do not need the display to hold its image unpowered, this is a serious alternative; if the e-paper is the point, it is not one |
-| **XTEINK X4 / X4 Pro** | **not captured** | A **sealed consumer e-reader** with locked-down firmware, raised repeatedly on Hacker News as the PaperMono's competitor. **You cannot put your own application on it.** The comparison the community makes is a *price* comparison between a reader and a development board, which is not a like-for-like comparison at all |
-| **reMarkable / Kindle class** | not captured | Finished consumer readers, much larger panels, no user firmware. Raised only in passing |
-
-> **A claim examined and rejected.** An HN commenter wrote that the PaperMono "is competition for
-> the new XTEINK X4 Pro. **Cost about half the price** and is compatible with Crosspoint too."
-> **No X4 Pro price was captured in this pass**, so the ratio is unverifiable — and more
-> importantly the workloads do not align: one is a sealed reader, one is a development board that
-> ships no reader firmware. The *CrossPoint compatibility* half of the claim is separately
-> supported: a CrossPoint build for the PaperMono exists and is retained in
-> [`artifacts/firmware/`](artifacts/firmware/) — see
-> [`factory-firmware.md` §3](factory-firmware.md#3-the-community-image--crosspoint-paper-mono-cjk-150-rc).
-
-## 8. Clones
-
-**None found.** No clone or compatible listing for the PaperMono was located on AliExpress,
-Amazon or any marketplace checked on 2026-09-01
-([`market-and-pricing.md` §11](market-and-pricing.md#11-used-clone-and-marketplace-supply)).
-
-At eleven days old that establishes nothing. Two structural observations for a later pass, both
-`inferred`:
-
-- The board depends on **two M5Stack-proprietary parts** (M5PM1, M5IOE1) that are not sold as
-  components and have no second source. A drop-in clone would have to replace them and rewrite
-  the board support, which is a much higher barrier than cloning a WROVER-plus-PCAL6416 design.
-- The **schematic is published but the EDA sources are not** — `m5stack/M5_Hardware` has no C153
-  directory at all (S45). That raises the effort to reproduce the layout without preventing it.
-
-General guidance on identifying siblings and variants is in
-[`guides/markets/clones-and-variants.md`](../../../guides/markets/clones-and-variants.md); note
-its own stated limitation that its methodology is derived from documented failure modes rather
-than validated practice.
-
-## 9. Launch-era market fit versus current market fit
-
-The method requires launch-era fit to use **contemporaneous** evidence and current fit to use
-evidence dated to the snapshot. Here they are eleven days apart, which makes the exercise
-unusually clean — and unusually thin.
-
-### Launch era (2026-08-21), using contemporaneous evidence
-
-At launch the PaperMono entered a field where:
-
-- Its own predecessor, the **PaperS3, was already `[EOL]`** (store status as read 2026-09-01;
-  the EOL marker's own date is not published). So M5Stack had no 4.7" e-paper S3 board to sell.
-- The nearest external LoRa-plus-e-paper board, the **LilyGO T5 E-Paper S3 Pro**, had been on
-  sale since 2024-11-14 at a listed 81.36–88.71 (currency unconfirmed) — **higher than USD 65.00
-  on the face of the numbers**, without NFC or a frontlight.
-- **Demand exceeded supply immediately**: sold out within nine minutes of storefront
-  publication, with the vendor stating pre-orders "reached the limit".
-
-**Launch-era fit: strong, on the evidence of the sell-out.** That is the honest reading — a
-nine-minute sell-out and a 162-point Hacker News thread are demand signals. What they are *not*
-is evidence that the product is good: **nobody had used one.** Every article published in the
-first week traces to a single vendor blog post
-([`community.md`](community.md)).
-
-### Current (2026-09-01)
-
-| Factor | State |
-|---|---|
-| Purchasable? | **No.** Out of stock at the manufacturer and at every reseller with stock evidence; two EU listings are pre-orders |
-| Restock | **Contested** — vendor "two or three months" (primary), CNX-Software "next year" (second-hand) |
-| Independent validation | **Zero written reviews. One hands-on video with an affiliate link.** No measurements of any kind |
-| Software maturity | Vendor **warns against its own graphics library's waveforms**; M5GFX `develop` has replaced the LUTs; no OTA partition; UiFlow2 advertised but undocumented |
-| Third-party momentum | **Real** — four projects and a CrossPoint reader build within eleven days, two with credible hardware validation |
-| Regulatory | **No FCC/CE/TELEC identifier published anywhere** (S11, verified negative) |
-
-**Current fit: unbuyable, unreviewed, and improving from the community side rather than the
-vendor side.** The most defensible current recommendation for almost every reader is *wait* —
-not because the hardware looks bad, but because there is no evidence about it that anyone
-outside M5Stack has produced, and you cannot buy it in order to produce any.
-
-## 10. Use this when / do not use this when
-
-Scoped by workload, constraint, date and region. All recommendations are dated **2026-09-01** and
-are **global** unless a region is named, because the manufacturer sells from a single Shopify
-market.
-
-### Use it when
-
-| Scenario | Why | Constraint you are accepting |
-|---|---|---|
-| **W3 — you need NFC *and* LoRa *and* e-paper on one battery-powered board** (access control, identity terminal, ticketing) | **Nothing else found in this survey does all three.** ST25R3916 covers ISO14443A/B, FeliCa and ISO15693; SX1262 covers 868–923 MHz | **No published certification of any kind**, so you cannot ship this into a regulated market on M5Stack's paperwork. Which card types actually interoperate is **untested by anyone** |
-| **W2 — long-idle, event-driven, wake on schedule or motion** | The five-state M5PM1 architecture keeps the RTC and IMU interrupts on the *power manager*, so the ESP32-S3 can be unpowered between events. The RTC is on the always-on `3V3_L0` rail and keeps time even in shipping mode | **No current figure exists for any state.** You are buying an architecture, not a measured battery life |
-| **You want frontlit e-paper with touch at this size and price** | Uncommon in this class; the PaperS3 and the Inkplates have no frontlight | 4 grey levels, 480×800, and the vendor's own refresh guidance is conservative |
-| **You want a finished, pocketable enclosed device rather than a bare board** | 101 × 62 × 8 mm, 74.7 g, battery and case included at USD 65.00 | Enclosed also means no expansion, and nothing to solder to |
-| **You want an ESP32-S3 e-paper platform whose custom silicon is actually documented** | M5Stack publishes vendor-authored manuals for **both** the M5PM1 and the M5IOE1 — better disclosure than most products with proprietary parts | Both manuals are internally inconsistent in recorded ways ([C4](gaps-and-conflicts.md#c4--the-m5ioe1s-i²c-address-is-not-in-its-own-manual), [C12](gaps-and-conflicts.md#c12--m5pm1-manual-internal-inconsistencies)) |
-
-### Do not use it when
-
-| Scenario | Why | Use instead |
-|---|---|---|
-| **W1 — reading or high-fidelity rendering is the product** | 384 000 px and 4 grey levels, against 518 400 px / 16 grey on the PaperS3 and 921 600 px on the Inkplate 5 Gen 2. And M5Stack **warns that its own refresh waveforms are unstable** | **Inkplate 5 Gen 2** (EUR 99.95 with case and battery) for resolution; **PaperS3** if you can find one, though it is `[EOL]` |
-| **W4 — you need to attach hardware** | **There is no expansion connector of any kind.** No Grove, no M-Bus, no broken-out GPIO. Every ESP32-S3 pin is committed. Anything you add shares the one I²C bus or takes over an M5IOE1 pin | **Inkplate 5 / Gen 2** (easyC/Qwiic + broken-out GPIO, and **published KiCad sources**); **LilyGO T5** series |
-| **You need field updates** | **No OTA partition** in either vendor project — single 15 MiB `factory` app. Updating a deployed unit means a cable | Anything, if you repartition first. This is a configuration choice you must make **before** shipping ([`development.md` §8.4](development.md#84-there-is-no-ota-partition)) |
-| **You need regulatory paperwork** | `/en/certification` returns HTTP 200 with **zero** matches for `PaperMono` and `C153`. A device with two radios and no published identifier | A vendor that publishes one. Note the Inkplate records include a [regulatory and SKU write-up](../../soldered-electronics/inkplate-5/regulatory-and-skus.md); the PaperMono has nothing equivalent |
-| **You need it now, or on a schedule** | Out of stock since day one, contested restock guidance, one reseller pre-order at EUR 79.95 with no stated delivery date | Anything in stock |
-| **You want a reading appliance rather than a development board** | It ships a demo launcher, not reader firmware. The CrossPoint community build exists but is a **community RC**, uploaded one day after launch, with no independent validation | **ZeroWriter Ink** (USD 285) if you want a finished writing appliance; a sealed consumer reader if you want a reader |
-| **You need Bluetooth Classic** | The ESP32-S3 has **no BR/EDR at all** — this is a hardware absence, not a software one, and no library can add it | See the [ESP32-S3R8 record's Classic Bluetooth section](../../../components/espressif/esp32-s3r8/README.md#radio-capabilities-and-the-classic-bluetooth-limitation) |
-
-## 11. Alternatives by tier
-
-Dated 2026-09-01. Prices in the seller's currency, unconverted.
-
-| Tier | Recommendation | Price observed | Caveat |
-|---|---|---|---|
-| **Budget** | LilyGO **T5 e-Paper 4.7" v2.3** | 38.99–44.50, **currency unconfirmed** | No internal record; variants differ on touch and pin soldering |
-| **Budget, small panel** | LilyGO **T5 V2.3.1 / T5s 2.7"** | 13.04 / 13.91, currency unconfirmed | Bare boards — no case, no battery. A different product class |
-| **Mainstream development** | **Soldered Inkplate 5 Gen 2** | EUR 99.95 with enclosure and battery | Best-documented option in this list: TAPR OHL, full KiCad sources, netlist-verified [record](../../soldered-electronics/inkplate-5-gen2/README.md) |
-| **Low-power / battery-first** | **PaperMono** — on architecture | USD 65.00, unbuyable | **Unmeasured.** If the requirement is quantified battery life, the PaperS3's *published* 9.28 µA / 949.58 µA / 154.02 mA figures are the only numbers in the family that exist |
-| **Compact / pocketable** | **PaperMono** or **PaperMono-Lite** | USD 65.00 / 55.00, both unbuyable | The Lite saves USD 10 by removing exactly NFC and LoRa |
-| **Radios (LoRa)** | **LilyGO T5 E-Paper S3 Pro** | 81.36–88.71, currency unconfirmed | **Has proper regional band SKUs** (`H752-*` CN / `USH752-*` US / `DEH752-*` EU), which the PaperMono does not. No NFC |
-| **Radios (LoRa + keyboard, non-e-paper)** | **[Tanmatsu](../../nicolai-electronics/tanmatsu/README.md)** | EUR 119.99 inc. VAT | LCD, not e-paper — the display does not hold its image unpowered |
-| **Finished appliance** | **[ZeroWriter Ink](../../zerowriter/zerowriter-ink/README.md)** | USD 285 | Not a development board. Two ESP32s, mechanical keyboard, boots into a text file |
-| **Professional / regulated deployment** | **None of the above from this record** | — | No device compared here has published certification that was verified in this pass. This is a genuine gap, not a recommendation to proceed |
-
-## 12. Evidence limitations
-
-State these before using anything above as a purchasing input:
-
-1. **Nothing was tested on hardware — on any device in this comparison.** Not the PaperMono, not
-   the Inkplates, not the LilyGOs.
-2. **LilyGO prices have no confirmed currency.** The numbers are storefront numerics.
-3. **LilyGO and Waveshare e-paper boards have no record in this knowledge base**, so the two
-   nearest external competitors are compared from listings, not from design data.
-4. **The Inkplate comparison is the only one resting on primary design data** (parsed KiCad BOMs
-   and netlists) — and its price observation is dated **2026-08-24**, eight days before the
-   PaperMono observations.
-5. **No power, battery-life or refresh measurement exists for the PaperMono**, so every W2
-   comparison is architectural reasoning ([`performance.md`](performance.md)).
-6. **The XTEINK X4 Pro — the comparison the community actually makes — was never priced.**
-7. **The applicable market genre guides contain no prices at all** by their own policy:
-   [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) and
-   [`guides/markets/README.md`](../../../guides/markets/README.md). Their vendor-reliability
-   assessments apply to M5Stack as a vendor and are worth reading; their positioning claims are
-   labelled inference and should not be inherited as conclusions.
-8. **The PaperMono is absent from
-   [`guides/markets/device-comparison-matrix.md`](../../../guides/markets/device-comparison-matrix.md)**,
-   which was compiled 2026-08-30 over fourteen devices. That matrix is an aggregation and the
-   device record wins where they disagree — but the PaperMono row simply does not exist yet.
-   **Adding it is an outstanding task for whoever next touches that page.**
-
-## Related
-
-- [`product-history-and-family.md`](product-history-and-family.md) — the in-family comparison in full
-- [`market-and-pricing.md`](market-and-pricing.md) — every price observation, with its tax and stock caveats
-- [`performance.md`](performance.md) — why the W2 verdict cannot be settled
-- [`community.md`](community.md) — the XTEINK and PaperS3-successor claims, examined
-- [`coverage.md`](coverage.md) · [`compatibility-and-status.md`](compatibility-and-status.md) — what works, and how well it is known
-- [`guides/markets/`](../../../guides/markets/README.md) — vendor reliability, clones and variants
-- [`sources.md`](sources.md) — S11, S48–S58, S68, S77, S79
diff --git a/devices/m5stack/papermono/compatibility-and-status.md b/devices/m5stack/papermono/compatibility-and-status.md
deleted file mode 100644
index 6d62943..0000000
--- a/devices/m5stack/papermono/compatibility-and-status.md
+++ /dev/null
@@ -1,266 +0,0 @@
-# Compatibility and status — M5Stack PaperMono
-
-> What is known to work, what is known to fail, and by which hardware and software
-> version.
-> Snapshot **2026-09-01**.
-
-> ## ⚠ Almost everything here is `untested`
->
-> **No PaperMono was in hand.** Nothing below was verified on a device by this research.
-> Statuses come from vendor documentation, source read at cited `file:line`, parsed
-> firmware binaries, and a small number of third-party reports — each labelled. The table
-> is deliberately dominated by `untested`; that is the accurate picture, not an
-> incomplete one.
-
-Evidence labels: **official** (vendor states it) · **source** (read in vendor code) ·
-**binary** (recovered from a shipped image) · **schematic** · **reported** (third party,
-firsthand) · **inferred** · **absent** (searched for, not found).
-
-## 1. Hardware revisions
-
-| Rev | Date | Evidence | Compatibility impact |
-|---|---|---|---|
-| **V0.6.2** | file dated **2026-05-22**, PDF exported 2026-06-08, last modified 2026-07-28 | schematic filename and title blocks | **The only revision in evidence** |
-| KEY/RGB sub-board | 2026-04-14 | title block | — |
-| NFC sub-board **V0.2** | 2026-07-28 | title block, marked **sheet 2/2** | Sheet 1 unpublished |
-
-**There is exactly one hardware revision.** No regional variants were found, and **no
-FCC/CE/TELEC identifier appears anywhere on M5Stack's site** — `/en/certification`
-returns HTTP 200 with zero matches for both `PaperMono` and `C153`. That is a **verified
-negative**, not a failed search.
-
-## 2. SKU variants
-
-| SKU | Price (2026-09-01) | NFC | LoRa | Case | Weight |
-|---|---|:-:|:-:|---|---|
-| **C153** PaperMono | USD 65.00 | ✅ ST25R3916 | ✅ Stamp LoRa-1262 | Grey | 74.7 g |
-| **C153-LITE** PaperMono-Lite | USD 55.00 | ❌ | ❌ | White | 72.4 g |
-
-Everything else is identical, **including the 1150 mAh battery** — the Lite does not get a
-smaller cell. The USD 10 delta is entirely NFC + LoRa.
-
-| Compatibility fact | Status |
-|---|---|
-| One firmware image serves both | **official** — the M5Burner API description is literally `"PaperMono / PaperMono-Lite UserDemo"` |
-| M5GFX **cannot** distinguish them | **source** — both map to `board_M5PaperMono`; NFC is masked out of the detection test (`M5GFX.cpp:1945`) |
-| The application layer **can** | **source** — `hal_board.cpp:160–172` writes M5IOE1 `IO4` and reads NFC register `0x7F` expecting `0x05` |
-| SKU case differs between vendor systems | `C153-Lite` in the docs, `C153-LITE` on Shopify |
-| ⚠ Store handles say `800x480`; every docs page says `480x800` | **official**, both — marketing landscape vs driver portrait |
-
-## 3. Software stack support
-
-| Stack | Version | Board | Display | Touch | Power | LoRa | NFC | Status |
-|---|---|:-:|:-:|:-:|:-:|:-:|:-:|---|
-| **ESP-IDF** | **5.5.1** | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | **source** — both vendor projects' `dependencies.lock` |
-| **arduino-esp32** | **3.3.10** (managed component) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | **source** — same lock file |
-| **M5Unified** | **0.2.21** | ✅ | ✅ | ✅ | ✅ | — | — | **source** — `board_M5PaperMono` present in the release tag |
-| **M5GFX** | **0.2.28** | ✅ | ✅ | ✅ | — | — | — | **source** — idem |
-| M5PM1 | **1.0.7** | — | — | — | ✅ | — | — | **official** registry `m5stack/m5pm1` |
-| M5IOE1 | **1.0.9** | — | — | — | ✅ | ✅ | ✅ | **official** registry `m5stack/m5ioe1` |
-| RadioLib | **7.2.1** pinned (`b91c6af1…`), **patched** | — | — | — | — | ✅ | — | **source** — `repos.json` |
-| M5Unit-NFC | **0.1.0** (`93745b54…`), patched | — | — | — | — | — | ✅ | **source** |
-| M5UnitUnified | **0.5.5** (`bf711f37…`), patched | — | — | — | — | — | ✅ | **source** |
-| PlatformIO | `espressif32@6.12.0`, `board = esp32-s3-devkitm-1` | ⚠ | ⚠ | ⚠ | ⚠ | ⚠ | ⚠ | **official** — but **no dedicated PlatformIO board definition exists** |
-| Arduino IDE | M5Stack board package, board **`M5PaperMono`** | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | **official** + **binary** (`[Autodetect] board_M5PaperMono`) |
-| arduino-esp32 core variant | `3.3.9/variants/m5stack_papermono/pins_arduino.h` | ✅ | — | — | — | — | — | **reported** via `tanakamasayuki/M5Stack-Arduino-Check` |
-| **UiFlow2** | **unspecified** | ⚠ | ⚠ | ⚠ | ⚠ | ⚠ | ⚠ | **official but empty** — no firmware version, no block list, no limitations published |
-| ESPHome | — | ⚠ | ⚠ | ⚠ | ⚠ | — | — | **reported**, early WIP; the author labels the display/touch rotation section a *test hypothesis* |
-| MicroPython / CircuitPython / Zephyr / NuttX / Rust | — | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | **absent** — nothing located |
-
-### 3.1 ⚠ Version-specific report: the `#develop` requirement is stale
-
-The vendor's PlatformIO snippet pins
-`M5Unified = https://github.com/m5stack/M5Unified#develop`.
-
-**Verified `executed-success` on 2026-09-01:**
-
-- `board_M5PaperMono = 29` is **byte-identical** on `master` and `develop`
-  (`M5GFX/src/lgfx/boards.hpp:40`).
-- `LED_PaperMono_Class.cpp` / `.hpp` are **byte-identical** between branches.
-- `board_M5PaperMono` **is present in release tags M5Unified 0.2.21 and M5GFX 0.2.28**,
-  both on `master`.
-- The `master`↔`develop` deltas touching PaperMono are unrelated fixes, not board support.
-
-**Caveat, preserved deliberately:** this is true *as of the branch SHAs recorded on
-2026-09-01*. The docs may have been accurate when written — the M5GFX board-id commit
-`3c2552d9` is dated 2026-04-10 and the M5Unified one `09a1c135` 2026-07-16.
-
-### 3.2 ⚠ Version-specific report: the factory firmware is not built from released libraries
-
-`repos.json` pins M5GFX and M5Unified to `develop` **at commits older than either current
-branch head**:
-
-| Component | Pinned commit | Current `develop` head (2026-09-01) |
-|---|---|---|
-| M5GFX | `02107b828acb3eb782fccd747863638d64c876d7` | `8d6e8b3e0e9629e0bf0702d263e9263b588b6075` |
-| M5Unified | `2fe93c0c64f12f916e73a0605c86bf1241c06a6b` | `98c81b182f10760fe5313c31982cf975dfd73bda` |
-
-So **the shipped factory firmware was built against a different e-paper waveform table
-than either current branch.** Anyone comparing display behaviour against a factory device
-is not comparing like with like. `inferred` from the pinned SHAs vs current heads.
-
-Compounding it: the shipped image's `esp_app_desc_t` reports **`c78f6c5-dirty`** — built
-from an uncommitted tree, therefore **not reproducible from any published commit**.
-
-### 3.3 ⚠ Version-specific report: M5GFX has replaced the waveform LUTs
-
-`diff` of `src/lgfx/v1/panel/Panel_SSD1677.cpp` between `master` and `develop`,
-114 changed lines, `executed-success`:
-
-- **`lut_quality` wholly replaced** on `develop`, with the previous 17-line table **left
-  commented out in-tree**. The frame-rate row changed from `0x22 × 5` to `0xFF × 5` and
-  all four grayscale rows differ.
-- **`lut_text` replaced**, its comment rewritten from *"Text: 64-frame absolute four-gray
-  waveform for Mode 1"* to *"GC1 binary full-refresh waveform used by epd_text"*, and a
-  new `Panel_SSD1677_4Gray::_refresh_mode1_text()` path added, with `epd_text` dispatch
-  switched to it.
-- That new path **ignores its first parameter** (`(void)planeL;`), forcing the "old plane"
-  to zero rather than using the previous frame, with a comment explaining it is deliberate
-  ("Match the source binary text test") — which reads like a test scaffold promoted into
-  production. `inferred`.
-
-**Consequence:** the vendor's published refresh timings (4.71 / 0.45 / 0.34 / 0.07 s)
-correspond to some specific unnamed build and **must not be treated as characteristic of
-any version you can check out**. `inferred`.
-
-## 4. Known-failing, hazardous and problematic
-
-### 4.1 Vendor states its own e-paper waveforms are unstable — **official**
-
-> "The e-paper driver waveforms for PaperMono in the M5GFX library are **currently
-> unstable**. It is recommended to prioritize the e-paper manufacturer's OTP example below
-> for refresh configuration to achieve better panel life and refresh stability."
-
-Corroborated in-tree by §3.3. **Status: unresolved, live issue.** Mitigation: use
-[`M5PaperMono-OTP-Demo`](https://github.com/m5stack/M5PaperMono-OTP-Demo).
-
-### 4.2 Continuous partial refresh causes irreversible panel damage — **official**
-
-M5Stack: *"Avoid uninterrupted continuous partial fast refreshes, to prevent long-term DC
-imbalance from causing irreversible damage to the panel."* Do roughly one full refresh per
-ten partials. **This is the only destructive failure mode on the board reachable from
-ordinary application code.**
-
-Related, and **recoverable**: after prolonged repeated refreshing, black deposited pixels
-may appear from ink-particle physics. Leave the panel idle, then do one full refresh.
-
-### 4.3 M5GFX drives the panel above its rated clock — **schematic + official datasheets**
-
-40 MHz in M5GFX vs a **20 MHz** maximum in both the SSD1677 datasheet §12.1 and the DKE
-panel manual p. 16, and 20 MHz in the vendor's own OTP demo. **Unresolved, untested, and
-the first thing to measure** if you are chasing refresh artefacts.
-
-### 4.4 Blank screen without octal PSRAM — **source**
-
-`M5GFX.cpp:2025`/`:2030` log `"M5PaperMono need OPI-PSRAM enabled"`, reset the panel and
-touch objects, and continue. The board is **correctly identified** with a completely dark
-screen — and `CORE_DEBUG_LEVEL=0` in the vendor's own published build flags compiles the
-log line out. **A build misconfiguration that presents as dead hardware.**
-
-### 4.5 IP2315 bus interference at low battery — **official**
-
-*"if the VBAT voltage is too low, the IP2315 may not initialize into I2C mode properly,
-which can interfere with other devices on the same I2C bus."* Documented recovery: a short
-press of the power button. Mitigation is structural in M5Unified — gate on, 64-attempt
-scan, transact, gate off.
-
-### 4.6 The `PYG3` collision can silently cut panel power — **schematic**
-
-`PYG3` is an M5PM1 **net** (frontlight PWM) and an M5IOE1 **pin** (e-paper rail enable).
-Both are live; a mistake is silent, not inert. Compounded by `M5IOE1_PIN_3 = 2`.
-See [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md).
-
-### 4.7 Default single-click reset is disruptive — **reported ×2**
-
-Two independent third-party projects — `MagicCube/free-ink-on-paper-mono` (which describes
-itself as having a *complete verified hardware path* on a **C153-LITE**) and
-`Free-Ink/freeink-sdk` — report explicitly **disabling the M5PM1's default single-click
-reset** while preserving the long-hold download escape. `pm1.setSingleResetDisable(true)`.
-
-**This is the strongest independent behavioural corroboration in the entire record**: two
-projects, two authors, the same finding, one of them with photographic ownership evidence
-cross-linked to a dated purchase post.
-
-### 4.8 Vendor documentation contradictions — **official vs official**
-
-| # | Contradiction | Resolution |
-|---|---|---|
-| C-1 | Docs use `PYG<n>` for **M5PM1** pins in ≥4 places, though `PYG` is also the M5IOE1's pin-name prefix | Both usages are accurate at different layers of the schematic. **The defect is ambiguity, not error** |
-| C-2 | PaperMono page: frontlight via `PYG3_BL_PWM`; Lite page: via `G3_WAKEin` | **Both correct** — different layers of the same drawing, faithfully translated into all three languages |
-| C-4 | Prose says the IMU interrupt is **active-high**; code, comments and the shipped binary say **active-low** | **Prose is wrong** |
-| C-5 | Product + UiFlow2 pages say **power button** for download mode; Arduino page says **"reset button on the side"** | **No reset button exists.** Arduino page is wrong |
-| C-7 | Arduino page requires `M5UnitUnified`; PlatformIO `lib_deps` omits it. Product pages pin `#develop`; Arduino page never mentions it | Install both; ignore the `#develop` pin (§3.1) |
-| C-8 | PlatformIO sets `qio_opi`; both shipped binaries report **DIO** | **Not a defect** — hardware supports QIO; DIO is an IDF default because `sdkconfig.defaults` pins no flash mode |
-| C-10 | "PaperMono Factory Reset Firmware" resolves to a record named "PaperMono UserDemo" | Same image, different label |
-| C-11 | The IP2315 bus hazard and `M5IOE1_PIN_11` appear **only** on the product page, not on the dedicated power page | Coverage gap in the page most likely to be read |
-| C-12 | PaperMono is absent from `/en/product_i2c_addr` **and** `/en/certification`, both HTTP 200 | Real omissions, verified negatives |
-
-### 4.9 Documentation omissions found by reading the code — **source**
-
-- **M5IOE1 `IO4` = NFC power enable** is used by the firmware and **never mentioned** in
-  the docs' expander pin list.
-- **M5IOE1 `IO7` = `ADD_SET`** likewise omitted.
-- **USB (GPIO19/20) and UART0 (GPIO43/44)** are absent from every vendor pin table.
-- Docs mention `G0_BOOT_OUT` and the M5IOE1 `G7` interrupt; **the UserDemo references
-  neither**. Not contradicted — **unexercised**. A negative result.
-- `M5GFX.cpp:2096`'s comment `// Set LOW io11, HIGH io13,14` is **wrong** — the mask covers
-  P13/P14 only, and `bitOn` cannot set anything low.
-- `Power_Class.cpp` says **"IP2316"** twice while the constant is `ip2315_i2c_addr`. Typo.
-
-### 4.10 Third-party library support claimed but not found — **unresolved**
-
-On 2026-08-17, four days *before* launch, `bitbank2` publicly claimed
-*"I already support the Paper Mono and Paper Color in my `bb_epaper` library"*. A GitHub
-code search of `bitbank2/bb_epaper` for `PaperMono` returned **0 matches** on 2026-09-01.
-Support may be under a different identifier, in an unpushed branch, or may not have
-landed. **Do not cite `bb_epaper` support as fact.**
-
-## 5. Accessory and platform compatibility
-
-| Item | Status | Note |
-|---|---|---|
-| **Any expansion accessory** | ❌ **impossible** | **No Grove port, no M-Bus, no header of any kind** |
-| M5Stack HATs / Units | ❌ | Nothing to plug them into |
-| PaperS3 firmware | ❌ **not drop-in** | `MingRZou/PaperMono-Launcher` is an explicit *port* of a PaperS3 project — concrete evidence the platforms differ. Larry Bank's public summary of the difference (PaperS3: parallel, 4.7", 960×540; PaperMono: SPI, 3.97", 800×480) was verified accurate |
-| CrossPoint e-reader | ⚠ community image exists | `crosspoint-paper-mono-cjk-1.5.0-RC.bin`, third-party, repartitions the flash entirely. `crosspoint-reader` upstream lists PaperMono on its **roadmap only** |
-| microSD cards | ⚠ **no documented limit** | No capacity or filesystem limit published by M5Stack |
-| USB-C PD chargers | ❌ | **No PD.** 5 V only, OVP at 5.95 V |
-| Meshtastic / MeshCore | ❌ unknown | Raised as an open question in the largest community thread and **not answered** |
-
-## 6. Untested / unknown — the honest list
-
-| Item | Why it matters |
-|---|---|
-| **Everything** | No device was available. This is the header row, not a footnote |
-| Actual refresh times on any current library version | The four published figures are lab results for an unnamed build (§3.3) |
-| **Current draw in any of the five power states** | The entire product pitch is low power, and **no figure exists from anyone** |
-| Battery runtime under any workload | idem |
-| Whether the 40 MHz panel clock causes the refresh instability | §4.3 — the single most valuable experiment |
-| 4 grey levels vs 2 | M5Stack markets four; the DKE manual's optical table says `GN — 2Grey Level` |
-| Which NFC card types actually read, and at what range | Four technologies advertised, **zero reports** |
-| LoRa range, throughput, RF output, regional legality | No module datasheet, no certification, no report |
-| Wi-Fi throughput, range, antenna | No antenna is documented anywhere |
-| microSD throughput and capacity limits | No figure from anyone |
-| Display + SD + Wi-Fi concurrently | No pin conflict; DMA/PSRAM/rail contention unmeasured |
-| Whether GPIO3/45/46 strap exposure causes real boot failures | `inferred` hazard, unconfirmed |
-| Whether the M5IOE1 GPIO7 interrupt works at all | **No vendor code exercises it** |
-| Whether NFC/LoRa genuinely act as L2 wake sources | Sheet 1 says yes; no firmware demonstrates it |
-| Whether the frontlight audibly whines at 5 kHz | Below the AW9967's rated 10–100 kHz range |
-| M5IOE1 address `0x4F` vs its manual's `0x6F`–`0x76` | Unresolved |
-| Restock date | Vendor said "two or three months" (2026-08-22); CNX-Software reported "next year". Both recorded, neither preferred |
-
-## 7. Claims examined and rejected
-
-| Claim | Source | Why rejected |
-|---|---|---|
-| Restock delayed by an e-ink driver IC shortage | widely repeated | The cited post and its **full reply chain** were retrieved; the reason **does not appear in them**. Hearsay |
-| "$55 with NFC and LoRa" | Liliputing | $55 is the Lite, which has neither |
-| PaperMono is the successor to / an upgrade over PaperS3 | several launch articles | Contradicted by the vendor's own specs: ~35 % fewer pixels, 4 vs 16 grey levels, 1150 vs 1800 mAh, no expansion port. A **repositioning**, not an upgrade |
-| "Bluetooth 5.0 LE + Mesh" | CNX-Software | The publication's inference from the SoC; **not in M5Stack's specification table** |
-| "Half the price of the XTEINK X4 Pro" | launch coverage | No X4 Pro price captured; a sealed reader vs a development board is not like-for-like |
-
-## Related
-
-- [`coverage.md`](coverage.md) · [`resources-and-conflicts.md`](resources-and-conflicts.md) · [`features/README.md`](features/README.md)
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — the full conflict register with resolutions
-- [`README.md`](README.md) · [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md)
diff --git a/devices/m5stack/papermono/coverage.md b/devices/m5stack/papermono/coverage.md
deleted file mode 100644
index a275b6c..0000000
--- a/devices/m5stack/papermono/coverage.md
+++ /dev/null
@@ -1,112 +0,0 @@
-# Feature coverage — M5Stack PaperMono
-
-> Every advertised and fitted capability, mapped to hardware, documentation, examples,
-> its feature guide and test status.
-> Hardware revision **V0.6.2** · snapshot **2026-09-01**.
-
-> ## ⚠ Every row's test status is `not-tested`
->
-> **There is no PaperMono in hand and there never was in this research pass.** Nothing in
-> this table has been built, flashed, run or measured on a device. No row reaches
-> `built`, `hw-tested` or `limit-tested`, and the columns for those are therefore
-> uniformly `not-tested` rather than left ambiguous.
->
-> What *is* evidenced is: the schematic (parsed), the vendor libraries and firmware source
-> (read at cited `file:line`), the vendor documentation pages (retrieved and hashed), and
-> two shipped firmware binaries (retrieved and parsed). Where a claim rests only on
-> M5Stack saying so, it is marked **V**; where it rests on reading their code, **S**.
-
-Evidence key — **P** primary design data (schematic) · **S** vendor source read at
-`file:line` · **V** vendor documentation · **F** shipped firmware binary ·
-**C** community report · **I** inferred.
-
-## 1. Fitted and advertised capabilities
-
-| Capability | Hardware | Official docs | Official example | Community example | Feature guide | Build test | HW test | Limit test | Gaps |
-|---|---|---|---|---|---|---|---|---|---|
-| **E-paper display** | [DKE DEPG0397BBS770F3](../../../components/dke/depg0397bbs770f3/README.md) + [SSD1677](../../../components/solomon-systech/ssd1677/README.md) | ✅ product page + "E-Paper Driver Notes" | ✅ **[`M5PaperMono-OTP-Demo`](https://github.com/m5stack/M5PaperMono-OTP-Demo)** (vendor-recommended) + M5GFX | ✅ 4 third-party projects, 2 claiming hardware validation | [`epaper-display.md`](features/epaper-display.md) | `not-tested` | `not-tested` | `not-tested` | **Vendor calls its own M5GFX waveforms unstable**; 40 vs 20 MHz clock; 4-vs-2 grey levels; OTP waveform coverage unpublished |
-| **Frontlight** | [AW9967](../../../components/awinic/aw9967/README.md) + M5PM1 `G3` | ✅ one line on the product page | ⚠ only inside M5GFX | ✅ one project holds it at 127/255 | [`frontlight.md`](features/frontlight.md) | `not-tested` | `not-tested` | `not-tested` | 5 kHz PWM below the AW9967's 10–100 kHz range; squared gamma; stale `Iset` annotation; **no current figure** |
-| **Touch** | [FT6336G](../../../components/focaltech/ft6336g/README.md) | ✅ incl. the coordinate limit | ⚠ only via M5GFX | ✅ claimed by one project | [`touch.md`](features/touch.md) | `not-tested` | `not-tested` | `not-tested` | Usable area **X 5–475 / Y 5–795**; no accuracy or latency data |
-| **User buttons ×2** | GPIO2 / GPIO3 | ✅ PinMap | ✅ `app_keyboard` in the UserDemo | ✅ | [`buttons-and-rgb-led.md`](features/buttons-and-rgb-led.md) | `not-tested` | `not-tested` | `not-tested` | GPIO3 is a strapping pin; wake-source role unconfirmed |
-| **Power button** | M5PM1 `BTN_PU` | ✅, but **three vendor pages disagree** on the name | ✅ `app_shutdown` | ✅ two projects disable single-click reset | [`buttons-and-rgb-led.md`](features/buttons-and-rgb-led.md) | `not-tested` | `not-tested` | `not-tested` | Arduino page invents a "reset button on the side" |
-| **RGB LED** | M5PM1 `LED_EN_PP` (red) + M5IOE1 `IO8`/`IO9` | ✅ incl. the no-PWM caveat | ✅ `app_rgb` | ❌ | [`buttons-and-rgb-led.md`](features/buttons-and-rgb-led.md) | `not-tested` | `not-tested` | `not-tested` | **Red has no PWM**; M5Unified also writes blue binary; LED part `RS-C1415MBAR` has **no datasheet** |
-| **Power management / 5 states** | [M5PM1](../../../components/m5stack/m5pm1/README.md) | ✅ dedicated page + 4 sketches | ✅ `app_sleep_wake`, `app_shutdown`, 4 M5PM1 library examples | ✅ `Free-Ink/freeink-sdk` board bring-up | [`power-and-sleep.md`](features/power-and-sleep.md) | `not-tested` | `not-tested` | `not-tested` | **No current figure for any state**; L3A/L3B distinction unclear; `3V3_L0` enable unread |
-| **Battery + charging** | [IP2315](../../../components/injoinic/ip2315/README.md) + [AW32901](../../../components/awinic/aw32901/README.md) | ✅ incl. the bus hazard (product page only) | ✅ `app_battery` | ✅ one project reports battery/charge telemetry | [`battery-and-charging.md`](features/battery-and-charging.md) | `not-tested` | `not-tested` | `not-tested` | `ICHGSET` resistor unresolved; **no runtime figure**; no fuel gauge |
-| **USB / serial / flashing** | GPIO19/20 + UART0 GPIO43/44 | ⚠ **absent from the PinMap** — schematic only | ✅ build instructions in the OTP demo README | ✅ | [`usb-and-serial.md`](features/usb-and-serial.md) | `not-tested` | `not-tested` | `not-tested` | **No USB-PD**; QIO documented vs DIO shipped; no OTA slot |
-| **Wi-Fi 2.4 GHz** | ESP32-S3R8 | ✅ one spec line | ✅ `app_wifi_scan` | ✅ | [`wifi-and-bluetooth.md`](features/wifi-and-bluetooth.md) | `not-tested` | `not-tested` | `not-tested` | **No throughput, range or antenna data at all**; no certification |
-| **Bluetooth LE** | ESP32-S3R8 | ❌ **not in any vendor spec table** | ❌ none | ⚠ one project claims BLE tiles, shows no hardware | [`wifi-and-bluetooth.md`](features/wifi-and-bluetooth.md) | `not-tested` | `not-tested` | `not-tested` | **Undocumented by the vendor.** "Bluetooth 5.0 LE + Mesh" is a publication's inference |
-| **LoRa (C153 only)** | [Stamp LoRa-1262](../../../components/m5stack/stamp-lora-1262/README.md) / SX1262 | ✅ PinMap + spec | ✅ `app_lora` (RadioLib 7.2.1) | ❌ | [`lora.md`](features/lora.md) | `not-tested` | `not-tested` | `not-tested` | **No module datasheet exists**; `SX_ANT_SW` semantics unknown; **no regional band plan, no certification**; TCXO only `inferred` |
-| **NFC (C153 only)** | [ST25R3916](../../../components/stmicroelectronics/st25r3916/) | ✅ PinMap + spec | ✅ `app_nfc_scan` (M5Unit-NFC) | ❌ | [`nfc.md`](features/nfc.md) | `not-tested` | `not-tested` | `not-tested` | **Which card types actually work is unknown**; NFC schematic sheet 1/2 unpublished (but sheet 2/2 does carry the full front end) |
-| **IMU** | [BMI270](../../../components/bosch-sensortec/bmi270/README.md) | ✅, but **polarity stated wrongly** | ✅ `app_imu` + the vendor wake sketch | ❌ | [`imu.md`](features/imu.md) | `not-tested` | `not-tested` | `not-tested` | Vendor prose says active-high; code and binary say active-low. Mirrored datasheet 5 years stale |
-| **RTC** | [RX8130CE](../../../components/seiko-epson/rx8130ce/) | ✅ PinMap | ✅ `app_clock` | ✅ one project reports RTC time working | [`rtc.md`](features/rtc.md) | `not-tested` | `not-tested` | `not-tested` | **No vendor code demonstrates RTC wake end to end**; the M5Stack mirror is in fact Epson's English manual ETM50E-09, served under a `_cn` filename |
-| **microSD** | 4-bit SDMMC, GPIO8–13 | ✅ PinMap + detect semantics | ✅ `app_tf_card` | ✅ CrossPoint uses `/​.crosspoint/` on the card | [`microsd.md`](features/microsd.md) | `not-tested` | `not-tested` | `not-tested` | **No throughput figure**; no documented capacity or filesystem limit |
-| **PDM microphone** | `LMD4737T261-AC02` | ✅ PinMap | ✅ `app_mic_wave` | ❌ | [`microphone.md`](features/microphone.md) | `not-tested` | `not-tested` | `not-tested` | **No datasheet exists**; GPIO45/46 are strapping pins; only 16 kHz exercised |
-| **Buzzer** | GPIO42 | ✅ PinMap | ✅ `app_buzzer` | ❌ | [`buzzer.md`](features/buzzer.md) | `not-tested` | `not-tested` | `not-tested` | Buzzer part unidentified; resonant frequency unknown |
-| **I/O expander** | [M5IOE1](../../../components/m5stack/m5ioe1/README.md) | ✅ dedicated page + datasheet | ✅ 3 library examples + all HAL code | ✅ `Free-Ink/freeink-sdk` | [`io-expander.md`](features/io-expander.md) | `not-tested` | `not-tested` | `not-tested` | `M5IOE1_PIN_3 = 2`; address `0x4F` vs the manual's `0x6F`–`0x76`; `IO7` omitted from the PinMap; **GPIO7 interrupt path unexercised** |
-| **PSRAM (8 MB octal)** | ESP32-S3R8, in package | ✅ spec line | ✅ implied by every build | ✅ | [`epaper-display.md` §7](features/epaper-display.md#7-octal-psram-is-mandatory--and-the-failure-looks-like-dead-hardware) | `not-tested` | `not-tested` | `not-tested` | **Mandatory** — M5GFX aborts without it. Bandwidth unmeasured |
-| **Flash (16 MB)** | [XM25UH128DHIQT](../../../components/xmc/xm25uh128dhiqt/README.md) | ✅ spec line | ✅ `partitions.csv` in both projects | ✅ CrossPoint repartitions entirely | [`microsd.md` §9](features/microsd.md#9-alternatives-for-storage) | `not-tested` | `not-tested` | `not-tested` | **No OTA slot, no filesystem** as shipped |
-
-## 2. Capabilities with no example and no documentation — flagged as gaps
-
-| Capability | Status | Detail |
-|---|---|---|
-| **UiFlow2** | ⚠ **advertised, undocumented — the clearest gap** | M5Stack lists UiFlow2 support and publishes a page for it. That page states **no required firmware version, no minimum UiFlow2 version, no PaperMono-specific block list, and no limitations** other than browser-pairing caveats. Confirmed by full-text search of the retrieved 265 KB page — a genuine documentation gap, not a retrieval failure. **No feature guide was written**, because there is nothing to write from. [`gaps-and-conflicts.md` G4](gaps-and-conflicts.md#g4--uiflow2-support-is-advertised-but-undocumented) |
-| **OTA update** | ❌ absent by construction | Single `factory` partition. Neither vendor project has an OTA slot |
-| **Bluetooth LE** | ⚠ silicon-only | Not in any vendor spec table, no example anywhere (§1) |
-| **NFC card emulation** | ⚠ API exists, never used | `cfg.emulation` is set `false` in all vendor code |
-| **M5IOE1 ADC ×4, PWM3/4, NeoPixel, temperature sensor, retention RAM** | ⚠ fitted silicon, unused | All fourteen expander pins are digital assignments on this board |
-| **M5PM1 retention RAM (32 B), NeoPixel, watchdog** | ⚠ fitted, unused | No vendor code exercises them |
-| **JTAG / hardware debug** | ❌ not evaluated | Not investigated in this pass. GPIO39–42 (the ESP32-S3 JTAG group) carry LoRa SPI and the buzzer, so it is likely unavailable — **`inferred`, unconfirmed** |
-| **Certification** | ❌ **verified negative** | `/en/certification` returns HTTP 200 with **zero** matches for `PaperMono` and `C153` |
-| **Product I²C address table** | ❌ **verified negative** | `/en/product_i2c_addr` returns 200 with zero matches, despite seven fitted I²C devices |
-| **Product/teardown imagery** | ❌ none retained | Vendor imagery is not licensed for redistribution; no independent teardown existed at the snapshot date |
-| **Performance characterisation** | ❌ `performance.md` not written | Nothing to put in it — see §4 |
-
-## 3. Example inventory
-
-| Source | What exists |
-|---|---|
-| **`m5stack/M5PaperMono-UserDemo`** | The factory firmware. HEAD `c1099107…` (2026-08-10), MIT, ESP-IDF 5.5.1. **Fifteen demo apps**: battery, brightness, buzzer, clock, IMU, keyboard, LoRa, mic wave, NFC scan, RGB, shutdown, sleep/wake, TF card, WiFi scan. The single richest source of pin evidence, because the HAL declares pins as named constants |
-| **`m5stack/M5PaperMono-OTP-Demo`** | HEAD `c7c02554…` (2026-08-20), MIT. Minimal SSD1677 driver using only OTP waveforms. **Vendor-recommended over M5GFX** |
-| `m5stack/M5PM1` | 1.0.7. Examples: `basic_power_adc`, `gpio_pwm`, `neopixel`, `usb_interrupt_sleep` |
-| `m5stack/M5IOE1` | 1.0.9. Examples: `interrupt_hardware`, `interrupt_polling`, `pin_test` |
-| Vendor docs page sketches | Four verbatim sketches on the M5PM1/M5IOE1 power page |
-| **Community** | `MagicCube/free-ink-on-paper-mono` (hardware-validated, Lite) · `MingRZou/PaperMono-Launcher` (hardware-validated) · `EggUncle/PaperMonoCalendar` (no hardware shown) · `hectorzin/M5PaperMono-HomeAssistant-ESPHome` (early WIP, self-labelled hypothesis) · `Free-Ink/freeink-sdk` (board bring-up) · `crosspoint-reader` (roadmap only) |
-
-> **No example is vendored into this record.** `examples/` under this device record is
-> empty; everything above is referenced by upstream URL and commit. That is a deliberate
-> gap, recorded rather than papered over.
-
-> ⚠ **The factory firmware is not reproducible.** Its `esp_app_desc_t` reports
-> `c78f6c5-dirty` — built from an uncommitted tree. And it pins M5GFX/M5Unified to
-> `develop` commits **older than either current branch head**, so it was built against a
-> different waveform table than anything you can check out today.
-
-## 4. Summary — and the honest bottom line
-
-- **21 fitted or advertised capabilities tracked**, covered by **16 feature guides**.
-  Every fitted capability has a guide or an explicit documented-absence.
-- **Zero rows are hardware-tested.** Zero rows are even *build*-tested. This is the single
-  largest limitation of the entire research pass and it is not recoverable without a
-  device.
-- **Four capabilities have official examples but no community example**: LoRa, NFC,
-  microphone, buzzer. Eleven days after launch that is unsurprising, but it means the only
-  evidence they work is that M5Stack wrote code for them.
-- **One advertised capability has neither documentation nor an example: UiFlow2.**
-- **No `performance.md` exists**, because there is nothing measured to put in one. No
-  refresh time we can stand behind, no current in any power state, no Wi-Fi throughput, no
-  SD throughput, no LoRa range, no battery runtime. The vendor's four refresh numbers are
-  lab figures for an unnamed build.
-
-The pattern in the missing rows is not random. The board is eleven days old, sold out
-within minutes, and has **one hands-on video and zero written reviews**. Everything
-written about it traces to a single vendor blog post. The real early signal is code —
-four third-party GitHub projects, two with credible hardware validation, independently
-corroborating the M5PM1 single-click-reset behaviour. That is a statement about
-2026-09-01, not a permanent property of the product.
-
-## Related
-
-- [`features/README.md`](features/README.md) · [`resources-and-conflicts.md`](resources-and-conflicts.md) · [`compatibility-and-status.md`](compatibility-and-status.md)
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) · [`README.md`](README.md)
-- [`vendors/m5stack`](../../../vendors/m5stack/README.md) · [`vendors/dke`](../../../vendors/dke/README.md)
diff --git a/devices/m5stack/papermono/development.md b/devices/m5stack/papermono/development.md
deleted file mode 100644
index 13abeba..0000000
--- a/devices/m5stack/papermono/development.md
+++ /dev/null
@@ -1,527 +0,0 @@
-# Development and recovery — M5Stack PaperMono
-
-> Board **C153**, schematic revision **V0.6.2** · research snapshot **2026-09-01**.
->
-> ## ⚠ Nothing on this page was executed against hardware
->
-> **There is no PaperMono in this session and there never was.** Every command below is
-> `reported-working` (transcribed from a vendor document or a vendor README) or `inferred`
-> (derived from the build files, the shipped binary, or standard framework behaviour).
-> **No command on this page carries `executed-success`**, because the only things executed
-> in this pass were static analyses of files on disk — those are ledgered in
-> [`commands.md`](commands.md), which is the authoritative record of what actually ran.
-
-This is the §9 development-and-recovery record: what to build with, what versions, what to
-flash, through which port, how to put the factory image back, and what can leave you with a
-board you cannot talk to. It **consolidates and cross-links** rather than repeats:
-
-| For | Go to |
-|---|---|
-| Port wiring, USB-PD absence, console behaviour, debugging symptoms | [`features/usb-and-serial.md`](features/usb-and-serial.md) |
-| The verbatim command ledger with tool versions and execution status | [`commands.md`](commands.md) |
-| What is inside the shipped images, and the restore evidence | [`factory-firmware.md`](factory-firmware.md) |
-| GPIO map, strapping pins, bus ownership | [`pinouts-and-buses.md`](pinouts-and-buses.md) · [`resources-and-conflicts.md`](resources-and-conflicts.md) |
-| Per-capability API guides | [`features/`](features/README.md) |
-
-## Contents
-
-- [1. Supported frameworks and exact versions](#1-supported-frameworks-and-exact-versions)
-- [2. Board target and profile](#2-board-target-and-profile)
-- [3. The vendor PlatformIO block, verbatim](#3-the-vendor-platformio-block-verbatim)
-- [4. Required libraries and versions](#4-required-libraries-and-versions)
-- [5. Build, flash and monitor](#5-build-flash-and-monitor)
-- [6. USB, UART and debug-port selection](#6-usb-uart-and-debug-port-selection)
-- [7. Factory restore and flash offsets](#7-factory-restore-and-flash-offsets)
-- [8. Known bricking and bootstrapping risks](#8-known-bricking-and-bootstrapping-risks)
-- [9. What is not established](#9-what-is-not-established)
-
----
-
-## 1. Supported frameworks and exact versions
-
-| Framework | Minimum / recommended | Evidence | Status |
-|---|---|---|---|
-| **ESP-IDF** | **5.5.1** | `M5PaperMono-UserDemo/dependencies.lock` (`idf: version: 5.5.1`); `M5PaperMono-OTP-Demo/README.md` states "ESP-IDF v5.5.1"; the shipped binary's `esp_app_desc_t` reports `idf_version v5.5.1` — **three independent confirmations** (S41, S42, S38) | `reported-working` |
-| **arduino-esp32** | **3.3.10** as an ESP-IDF managed component | `M5PaperMono-UserDemo/dependencies.lock` (S41) | `reported-working` |
-| **arduino-esp32** | **3.3.9** is the earliest core in evidence that carries the board variant | `tanakamasayuki/M5Stack-Arduino-Check` contains `3.3.9/variants/m5stack_papermono/pins_arduino.h` (S96) | `inferred` |
-| **PlatformIO** | `platform = espressif32@6.12.0`, `framework = arduino` | vendor product page (S01), reproduced verbatim in §3 | `reported-working` |
-| **Arduino IDE** | **no version stated anywhere** | S07 names no IDE version and no board-package version | gap |
-| **UiFlow2** | **advertised, undocumented** | S09 states no required firmware version, no block list, no limitations — established by full-text search of the retrieved page, so this is a documentation gap, not a retrieval failure ([G4](gaps-and-conflicts.md#g4--uiflow2-support-is-advertised-but-undocumented)) | gap |
-
-**Both arduino-esp32 rows are true, and they are not in conflict.** 3.3.10 is what the vendor's
-own ESP-IDF project pins as a managed component and is therefore what built the shipped image;
-3.3.9 is the earliest *Arduino core* release in which a third-party inventory shows the
-`m5stack_papermono` variant directory existing. They are statements about two different
-artifacts, recorded separately so a later pass does not "resolve" one of them as an error —
-see [C17](gaps-and-conflicts.md#c17--arduino-esp32-version-differs-between-sources).
-
-**Newer ESP-IDF demonstrably works, from community evidence.** The third-party CrossPoint
-image ([`factory-firmware.md` §3](factory-firmware.md#3-the-community-image--crosspoint-paper-mono-cjk-150-rc)) reports `idf_version 5.5.2.260206` and boots on the same board.
-That is one data point from a shipped binary, not a support statement: **5.5.1 remains the
-only version M5Stack pins.**
-
-## 2. Board target and profile
-
-| Layer | Identifier | Where it comes from |
-|---|---|---|
-| Arduino IDE board menu | **`M5PaperMono`** | S07; independently corroborated by the string `[Autodetect] board_M5PaperMono` in the shipped binary (S38) |
-| arduino-esp32 variant directory | **`m5stack_papermono`** | S96 (`3.3.9/variants/…/pins_arduino.h`) |
-| M5Unified / M5GFX board enum | **`board_M5PaperMono`** (`= 29` in M5Unified) | S46, S47 |
-| PlatformIO board | **`esp32-s3-devkitm-1`** — a generic devkit, reconfigured by flags | S01 |
-| ESP-IDF target | `esp32s3` | both `sdkconfig.defaults` and `dependencies.lock` (S41, S42) |
-
-**There is no PlatformIO board definition for the PaperMono.** The vendor uses a generic
-ESP32-S3 devkit profile and fixes it up with `board_build.*` and `build_flags`. Practical
-consequence: PlatformIO will not warn you about anything board-specific — not the flash size,
-not the PSRAM mode, not the partition scheme. Every one of those is your responsibility, and
-getting the PSRAM one wrong produces a board that looks dead (§8).
-
-**M5GFX cannot tell a C153 from a C153-LITE.** Both map to the single enum
-`board_M5PaperMono`, with NFC masked out of the detection test (`M5GFX.cpp:1945`). Variant
-detection is an *application-layer* job: the factory firmware powers the NFC rail through
-M5IOE1 `PYG4` and reads the ST25R3916 identity register, declaring `Lite` if either step
-fails (`hal_board.cpp:160–172`, S41). If your code needs to know which SKU it is running on,
-you must do the same thing yourself. `inferred` from source; `not-tested`.
-
-## 3. The vendor PlatformIO block, verbatim
-
-Reproduced exactly as published on the PaperMono product page (S01). It is the only build
-configuration M5Stack publishes anywhere. **`reported-working`; not built here.**
-
-```ini
-[env:m5stack-papermono]
-platform = espressif32@6.12.0
-board = esp32-s3-devkitm-1
-framework = arduino
-board_build.partitions = default_16MB.csv
-board_upload.flash_size = 16MB
-board_upload.maximum_size = 16777216
-board_build.arduino.memory_type = qio_opi
-build_flags =
-    -DESP32S3
-    -DBOARD_HAS_PSRAM
-    -mfix-esp32-psram-cache-issue
-    -DCORE_DEBUG_LEVEL=0
-    -DARDUINO_USB_CDC_ON_BOOT=1
-    -DARDUINO_USB_MODE=1
-lib_deps =
-    M5Unified = https://github.com/m5stack/M5Unified#develop
-    M5PM1 = https://github.com/m5stack/M5PM1
-    M5IOE1 = https://github.com/m5stack/M5IOE1
-    M5Unit-NFC=https://github.com/m5stack/M5Unit-NFC
-    RadioLib = https://github.com/jgromes/RadioLib
-```
-
-The **PaperMono-Lite** page (S04) publishes the same block with exactly two differences: the
-environment is `[env:m5stack-papermono-lite]`, and `M5Unit-NFC` and `RadioLib` are absent from
-`lib_deps`.
-
-### Five things to change or know about this block
-
-| # | Line | What is wrong or worth knowing |
-|---|---|---|
-| 1 | `board_build.arduino.memory_type = qio_opi` | **Do not remove this.** The `opi` half is load-bearing (§8.1). The `qio` half is cosmetic on this board: the shipped binaries report **DIO** in their image headers, `sdkconfig.defaults` pins no flash mode, and the hardware supports QIO either way — [R2](gaps-and-conflicts.md#r2--qio-versus-dio-flash--resolved) |
-| 2 | `M5Unified#develop` | **Stale.** `board_M5PaperMono` is byte-identical on `master` and `develop` and ships in released tags M5Unified 0.2.21 / M5GFX 0.2.28 — [R5](gaps-and-conflicts.md#r5--m5unifieddevelop-requirement--resolved-the-instruction-is-stale). Use the release |
-| 3 | `M5UnitUnified` absent | The Arduino quick-start page (S07) lists it among seven required libraries; this block omits it. If you follow the Arduino page and the PlatformIO block at once you get two different dependency sets |
-| 4 | `-DCORE_DEBUG_LEVEL=0` | Compiles out the diagnostics you need — including M5GFX's `"M5PaperMono need OPI-PSRAM enabled"`. **Raise it to 3 or 4 while bringing a board up** |
-| 5 | `board_build.partitions = default_16MB.csv` | This is the *Arduino* default 16 MB scheme, which has **two OTA app slots**. It is **not** the layout the factory image uses (a single 15 MiB `factory` app, no OTA). The two vendor projects and the vendor build block disagree about the flash map — see [`factory-firmware.md` §4](factory-firmware.md#4-partition-maps--three-different-layouts-are-in-evidence) |
-
-Point 5 is the one that is easy to miss and hard to debug later. Nothing breaks at build time;
-you simply end up with a different flash geometry from the shipped product, which matters the
-moment you try to compare behaviour against the factory image or restore it.
-
-## 4. Required libraries and versions
-
-The vendor names libraries without versions in every place it names them. The versions below
-come from the release tags and, where the shipped firmware is concerned, from the exact commits
-pinned in `M5PaperMono-UserDemo/repos.json` (S41).
-
-| Library | Release tag (2026-09-01) | Commit pinned by the factory firmware | Role |
-|---|---|---|---|
-| **M5Unified** | **0.2.21** (2026-08-26) | `develop` @ `2fe93c0c64f12f916e73a0605c86bf1241c06a6b` | Board abstraction, I²C bring-up, button/RTC/IMU wrappers |
-| **M5GFX** | **0.2.28** (2026-08-25) | `develop` @ `02107b828acb3eb782fccd747863638d64c876d7` | Panel driver, expander bring-up, frontlight PWM |
-| **M5PM1** | **1.0.7** (repo HEAD `be9a5456c007c333e7ac963f33bfde1ffa5d82ee`) | registry `m5stack/m5pm1` 1.0.7 | Power manager — rails, wake, shutdown, PWM |
-| **M5IOE1** | **1.0.9** (repo HEAD `846eec7d05e25c09013be2acdb8804487f48a62e`) | registry `m5stack/m5ioe1` 1.0.9 | I/O expander — panel/touch/SD/mic power, resets, LEDs |
-| **M5Unit-NFC** | no release tag located | `0.1.0` @ `93745b547364f310cd64b5155a870103a7800a5d` | ST25R3916 driver (C153 only) |
-| **RadioLib** | **7.2.1** | `7.2.1` @ `b91c6af112e423dcb14529ade5827802a14e1015` | SX1262 LoRa stack (C153 only) |
-| M5UnitUnified | — | `0.5.5` @ `bf711f370047cf16355b00005450ef615fab36e2` | Required by S07, absent from the PlatformIO block |
-| M5Utility | — | `0.1.0` @ `5b5ed9626bc4c1cf81ec6039a34e33c901b5b68f` | transitive |
-| M5HAL | — | `0.1.2` @ `0f06f9d3134706ce030fd5515601cce65a267233` | transitive |
-| mooncake | — | `v2.3.3` @ `572a7e488641f1c3f22e85d65c27f095ecf27d12` | App framework used by the factory demo |
-| LGFX_Fonts | — | `1.1.2` @ `253cf549fe0b1aa932be68fe06a13c3077918d61` | Fonts |
-| Arduino_BMI270_BMM150 | — | `1.2.3` @ `a599119044554015e06735f9d7187fc56295b9b6` | A *third* BMI270 driver in the same tree |
-
-**Two things about this table matter more than the numbers.**
-
-*The factory firmware does not build from released libraries.* It pins `develop` branch commits
-of M5Unified and M5GFX, fetches ten repositories with `fetch_repos.py` rather than vendoring
-them, and applies eight local patches. Those patches were read in full: they are **build
-plumbing only** — `arduino-esp32` → `espressif__arduino-esp32` in CMake, plus dropping a
-duplicate `m5gfx` dependency — and **no pin, register or waveform is patched**. That is a
-genuinely useful negative result: all PaperMono board knowledge lives upstream in
-M5GFX/M5Unified, none of it is private to the firmware, so a release-tag build has the same
-board support the factory image does. Recorded also in
-[`compatibility-and-status.md` §3.2](compatibility-and-status.md#32--version-specific-report-the-factory-firmware-is-not-built-from-released-libraries).
-
-*RadioLib's licence is not MIT.* The demo repositories are MIT, but RadioLib is LGPL-3.0
-upstream and is fetched into `components/` rather than vendored. Nobody in this pass verified
-what obligations that creates for a derived binary; it is flagged, `not-tested`, and it is the
-one licence question on this board that could actually matter to a product.
-
-## 5. Build, flash and monitor
-
-### 5.1 ESP-IDF — the path the vendor actually used
-
-`reported-working`, transcribed from `M5PaperMono-OTP-Demo/README.md` (S42):
-
-```bash
-idf.py set-target esp32s3
-idf.py build
-idf.py -p PORT flash
-```
-
-For the **UserDemo** (S41) the dependencies are not vendored, so they must be fetched first:
-
-```bash
-python3 fetch_repos.py     # clones 10 repos at pinned commits into components/, applies patches/
-idf.py set-target esp32s3
-idf.py build
-idf.py -p PORT flash
-```
-
-`inferred` — `fetch_repos.py` was read but **not run**, and the UserDemo README was not read in
-full for build steps.
-
-Monitoring is not in either README. Standard IDF usage would be:
-
-```bash
-idf.py -p PORT monitor          # inferred; console baud not stated by the vendor anywhere
-idf.py -p PORT flash monitor    # inferred
-```
-
-`inferred`, `not-tested`. The vendor's M5Burner page (S09) exposes a `BaudRate` field but does
-not say what value the device uses; the ESP-IDF default is 115200 and nothing in
-`sdkconfig.defaults` overrides it, so 115200 is the reasonable first guess — **an inference,
-not a reading**.
-
-### 5.2 PlatformIO
-
-`inferred` (standard PlatformIO usage against the vendor's own env block; not run):
-
-```bash
-pio run -e m5stack-papermono                 # build
-pio run -e m5stack-papermono -t upload       # build + flash
-pio device monitor -b 115200                 # console
-```
-
-### 5.3 Arduino IDE
-
-`reported-working`, from S07:
-
-1. Install the M5Stack board package.
-2. Install seven libraries: `M5Unified`, `M5GFX`, `M5PM1`, `M5IOE1`, `M5UnitUnified`,
-   `M5Unit-NFC`, `RadioLib` — "then install all prompted dependencies". **No versions given
-   for any of them**; use §4.
-3. Select the **`M5PaperMono`** board.
-4. Enter download mode (§6.3).
-5. The page tells you to open the **`BarGraph`** example and click Upload. A bar-graph demo
-   corresponds to none of the 14 advertised API sub-pages and reads as boilerplate carried
-   over from another product. Reproduced because it is what the vendor says; **flagged
-   because it is probably not what you want.**
-
-### 5.4 M5Burner / EasyLoader — the GUI route
-
-M5Burner is also how UiFlow2 firmware is installed. Two PaperMono images are listed
-(§7 and [`factory-firmware.md`](factory-firmware.md)). A Windows EasyLoader executable
-`C153-PaperMono-UserDemo_0x00.exe` is linked from **both** the PaperMono and the
-PaperMono-Lite pages, and it lives under PaperMono's asset folder `1267/`, not the Lite's
-`1268/` — corroborating that **one image serves both SKUs** (S40, S33). The executable was
-**not retrieved**; a Windows binary was out of scope for this pass.
-
-> ⚠ **M5Burner's device filter will not protect you.** Both listings carry
-> `deviceName: "Paper"` — the same family key used across M5Stack's Paper line. The catalogue
-> therefore does not distinguish a PaperMono image from an M5Paper or PaperS3 image.
-> `inferred` from the M5Burner API records (S33, S35); `not-tested`.
-
-## 6. USB, UART and debug-port selection
-
-Full wiring, the USB-PD analysis and the debugging symptom table are in
-[`features/usb-and-serial.md`](features/usb-and-serial.md). The selection decision in short:
-
-| Port | Pins | Use it when |
-|---|---|---|
-| **Native USB** (CDC) | **GPIO19 D− / GPIO20 D+**, via the `FT1` common-mode filter | Normal flashing and console. This is what `-DARDUINO_USB_CDC_ON_BOOT=1` makes `Serial` |
-| **UART0** | **GPIO43 TX (499 Ω series `R30`) / GPIO44 RX** | Boot-time and crash debugging. **Not brought out to any connector** — using it means probing the board |
-| External JTAG (MTDI/MTCK/MTMS/MTDO) | GPIO39–42 | **Unavailable.** Those pins carry LoRa SPI CLK/MISO/NSS and the buzzer |
-| USB-Serial/JTAG (built into the ESP32-S3, on the native USB pins) | GPIO19/20 | Probably available, and the only debug path that does not require desoldering. **`inferred`, unverified** |
-
-**Neither USB nor UART0 appears on the vendor's product-page pin tables.** Both are established
-from the schematic alone (S14). That omission is recorded in
-[R6](gaps-and-conflicts.md#r6--the-vendor-product-pages-pin-tables-are-accurate--confirmed-correct).
-
-**On the JTAG row, be precise about what is and is not established.** The *external* JTAG pin
-group is definitively consumed — GPIO39/40/41 are LoRa SPI and GPIO42 is the buzzer, read from
-the schematic. The *internal* USB-Serial/JTAG controller is a documented ESP32-S3 peripheral on
-the same GPIO19/20 pads, and the vendor's `-DARDUINO_USB_MODE=1` flag is what selects the
-hardware CDC/JTAG path rather than TinyUSB in arduino-esp32 — but **that mapping was not
-verified against arduino-esp32's own board definitions in this pass**, and no debug session has
-been reported by anyone on this board. Treat "you can debug over USB" as a plausible
-expectation to test first, not as a documented capability.
-
-**Practical consequence of native USB.** The serial port disappears on every reset, crash,
-sleep and USB reconfiguration, and comes back as a new device. Early boot output before CDC
-enumerates is lost. UART0 does not have this problem, which is exactly why it is worth the
-probe wires when something fails before `app_main`.
-
-## 7. Factory restore and flash offsets
-
-### 7.1 The offsets
-
-From parsing the shipped image (`executed-success` as a static analysis — [`commands.md` §5](commands.md#5-firmware-image-inspection)) and from `partitions.csv` in both vendor projects
-(S41, S42):
-
-| Region | Offset | Size | Contents |
-|---|---|---|---|
-| Second-stage bootloader | `0x0000` | — | ESP32-S3 image, magic `0xE9`, 3 segments, entry `0x403c8924` |
-| Partition table | `0x8000` | — | 3 entries |
-| `nvs` (data/nvs) | `0x9000` | `0x6000` (24 K) | Wi-Fi credentials, NTP and timezone settings |
-| `phy_init` (data/phy) | `0xF000` | `0x1000` (4 K) | RF calibration |
-| `factory` (app/factory) | `0x10000` | `0xF00000` (15 360 K) | The application |
-| *(unallocated)* | `0xF10000` | ~960 K | Free to the end of the 16 MB device |
-
-`esp_app_desc_t` sits at `0x10020`, i.e. 0x20 into the app image, which is where the version,
-project name, build date and IDF version were read from.
-
-### 7.2 Restoring the official image
-
-**The retained `.bin` is a merged whole-flash image, not an app-only image.** Three independent
-indications: the parse finds a bootloader header at `0x0`, a partition table at `0x8000` and an
-app header at `0x10000` inside the one file; the vendor's own object name ends `_0x00.bin`
-(S34); and the file is 2 868 208 bytes — far larger than the app alone would be at that offset.
-
-**Authoritative route** (`reported-working` — this is what the vendor supports):
-
-> Use **M5Burner** or the **EasyLoader** executable, select the *PaperMono UserDemo* firmware,
-> put the board in download mode (§6.3 / [`features/usb-and-serial.md` §3](features/usb-and-serial.md#3--download-mode-is-the-power-button--there-is-no-reset-button)),
-> and flash. This is the only restore path M5Stack documents.
-
-**Inferred equivalent** (`inferred`, **never executed, on any board**):
-
-```bash
-# INFERRED. Not run here. Verify the port and the chip before trusting this.
-esptool.py --chip esp32s3 --port PORT --baud 921600 \
-  write_flash --flash_mode dio --flash_freq 80m --flash_size 16MB \
-  0x0 C153-PaperMono-UserDemo-v1.2.bin
-```
-
-The `--flash_mode dio --flash_freq 80m --flash_size 16MB` values are the ones the image's own
-header reports, so they are the self-consistent choice; `0x0` follows from §7.2's three
-indications. **Nothing about this command has been observed to work.** It is written down
-because the method requires reacquisition and recovery instructions to exist rather than be
-silently omitted — not because it has been validated.
-
-### 7.3 What "factory reset" does and does not mean here
-
-| Claim | Reality |
-|---|---|
-| The vendor link is labelled "PaperMono **Factory Reset** Firmware" | It resolves to a M5Burner record named **"PaperMono UserDemo"** — the same image, differently labelled ([C11](gaps-and-conflicts.md#c11--mislabelled-firmware-link)) |
-| Flashing it "resets" the device | It replaces the application. Whether `nvs` (Wi-Fi credentials, timezone) survives depends on the tool and offsets used; a whole-flash write at `0x0` includes the image's own `nvs` region and would overwrite it. `inferred` |
-| It restores the M5PM1 | **No.** The power manager runs its own firmware in its own part and is not touched by anything you flash into the ESP32-S3 (§8.3) |
-
-## 8. Known bricking and bootstrapping risks
-
-Five of these are recoverable, one is not, and one is a hardware kill. Ordered by how likely
-you are to hit them.
-
-### 8.1 Octal PSRAM is mandatory — and the failure looks like dead hardware
-
-`M5GFX/src/M5GFX.cpp:2072–2081` aborts display initialisation and logs
-`"M5PaperMono need OPI-PSRAM enabled"` when either `CONFIG_ESP32S3_SPIRAM_SUPPORT` or
-`CONFIG_SPIRAM_MODE_OCT` is missing. The board is still identified, the firmware still runs,
-**the screen simply stays blank**.
-
-Compounding it: the vendor's own `build_flags` set `-DCORE_DEBUG_LEVEL=0`, which compiles that
-message out. **The default configuration hides the message that explains the symptom.**
-
-- PlatformIO: keep `board_build.arduino.memory_type = qio_opi`.
-- ESP-IDF: `CONFIG_SPIRAM=y` and `CONFIG_SPIRAM_MODE_OCT=y` (both are in the vendor's
-  `sdkconfig.defaults`).
-- Recovery: rebuild. Nothing is damaged. `inferred` from source; `not-tested`.
-
-### 8.2 GPIO3, GPIO45 and GPIO46 are strapping pins carrying user-facing signals
-
-| GPIO | Strap function | Also carries | Who drives it |
-|---|---|---|---|
-| **GPIO0** | boot mode select | M5PM1 `BOOT_OUT_OD` | the power manager — by design |
-| **GPIO3** | JTAG source select strap | **User button B** (`G3_KEY2`) | the user's finger |
-| **GPIO45** | `VDD_SPI` voltage select strap | **PDM microphone clock** | the ESP32-S3 itself |
-| **GPIO46** | boot-message routing strap | **PDM microphone data** | the microphone, whenever `PDM_VDD` is up |
-
-**Holding user button B across a reset perturbs a strapping pin**, and a microphone that is
-still powered and clocking across a reset perturbs two more. The vendor firmware does explicitly
-release the mic pins before reconfiguring them ([`features/microphone.md` §2](features/microphone.md#-2-both-microphone-pins-are-esp32-s3-strapping-pins)), but nothing in
-any vendor code guards the button-B case.
-
-This is a **bootstrapping** hazard rather than a bricking one on paper: straps are sampled at
-reset and the board should come back on the next clean reset. It is listed here because the
-symptom — "it sometimes does not come up, and it seems to depend on how I was holding it" — is
-extremely easy to misdiagnose as flaky hardware. `inferred` from the pin map; `not-tested`.
-Also in [`resources-and-conflicts.md` §9](resources-and-conflicts.md#9-boot-straps).
-
-### 8.3 The M5PM1 owns reset and the boot strap — this is the real bricking vector
-
-`CHIP_PU` carries `SOC_RESET` from the M5PM1, and GPIO0 is driven by its open-drain
-`BOOT_OUT_OD`. **The power manager, not a button, puts the ESP32-S3 into download mode.** There
-is no separate reset button on the board — the schematic shows exactly three switches on the
-KEY/RGB sub-board (`S1` `PWR_BTN`, `S2` `G2_KEY1`, `S3` `G3_KEY2`) and nothing else.
-
-Three consequences, in increasing order of seriousness:
-
-1. **If the M5PM1 will not assert the boot strap, you cannot flash the board at all.** Your
-   escape hatch is a peripheral, and it is behind an I²C bus that your own firmware also drives.
-2. **The M5PM1 has its own firmware-update mode**, entered by `SYS_CMD` `0x0C` `CMD=11` or by a
-   long press — and it is **lockable** through `BTN_CFG_1[7] DL_LOCK`. Writing that lock bit
-   from application code is a plausible way to remove your own recovery path. Nothing in this
-   pass tested it and nobody has reported doing it; it is called out because the register exists
-   and is writable over the same bus everything else uses.
-3. **Third-party projects disable the M5PM1's default single-click reset**, which two
-   independent sources describe as disruptive
-   (`MagicCube/free-ink-on-paper-mono` calls it "M5PM1's dangerous default single-click reset";
-   `Free-Ink/freeink-sdk`'s `PaperMonoBoard.h` does the same). Note what the freeink SDK is
-   careful to do: it disables single-click reset **while preserving the hardware long-hold
-   download escape**. If you copy the first half of that and not the second, you have removed
-   the only documented way back into download mode. **Copy both halves.**
-
-### 8.4 There is no OTA partition
-
-Both vendor projects ship a single `factory` app and no OTA slot, no `otadata`, and no
-filesystem. **The product as shipped has no field-update path.** If you intend to ship
-something, decide your partition layout at the start, because changing it later means a
-full reflash of every unit in the field — which for this board means a cable and a hand.
-
-The community CrossPoint image does something different again (`app0` + a dedicated 4 MB
-`cjkfont` partition + SPIFFS + coredump), which is direct evidence that repartitioning works —
-see [`factory-firmware.md` §4](factory-firmware.md#4-partition-maps--three-different-layouts-are-in-evidence).
-
-### 8.5 The `PYG3` collision can silently cut panel power
-
-`PYG3` denotes **M5IOE1 pin 3** (`PYB_EPD_EN`, the e-paper 3.3 V rail enable) *and* **M5PM1 G3**
-(`PYG3_BL_PWM`, the frontlight PWM). The vendor documentation uses the same token for both, on
-the same page. Writing a "frontlight" value to the wrong chip switches off the display's power
-rail. Compounding it, the M5IOE1 library's pin labels are 1-based while its enum values are
-0-based (`M5IOE1_PIN_3 = 2`), so passing a documentation `PYG<n>` straight into the API reaches
-pin *n+1*.
-
-**Read [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md) before
-writing any expander or PMIC code.** This is recoverable in software, but the symptom is a
-blank screen, which is also the symptom of §8.1 and of forgetting to enable the rail at all.
-
-### 8.6 Continuous partial refresh can destroy the panel — permanently
-
-This is the one item on this page that is not recoverable by reflashing. M5Stack's own
-precautions (S01) state that **uninterrupted continuous partial fast refreshes cause long-term
-DC imbalance and irreversible panel damage**, and that custom external waveforms must maintain
-DC balance for the same reason. Their software recommendation is roughly **one full refresh per
-ten partial refreshes**.
-
-Two things make this more than boilerplate:
-
-- **M5Stack says its own M5GFX waveforms are "currently unstable"** and recommends the panel
-  maker's OTP example instead. That is corroborated in-tree: M5GFX `develop` has *replaced* the
-  LUTs, leaving 17 lines of the previous `lut_quality` commented out.
-- **M5GFX drives the panel at 40 MHz** while both the SSD1677 datasheet (§12.1) and the DKE
-  panel manual (p. 16) independently state a **20 MHz** maximum write clock, and the vendor's
-  own OTP demo uses 20 MHz ([C3](gaps-and-conflicts.md#c3--spi-clock-exceeds-the-panels-rated-maximum)).
-
-If you are writing a refresh loop, start from
-[`features/epaper-display.md`](features/epaper-display.md) and the OTP demo, not from M5GFX
-defaults.
-
-### 8.7 A low battery can wedge the I²C bus
-
-The IP2315 charger's I²C mode depends on its bus pins being pulled to `VBAT`. The vendor
-documents that at low battery it may fail to enter I²C mode and disturb the other six devices
-on the shared bus. It is therefore **gated off the bus by default** through M5IOE1 `IO11`
-(`PYB_CHG_IIC`); attach it, transact, detach. The vendor's documented recovery from a wedged
-bus is a short press of the power button.
-
-**An I²C scan that does not find `0x75` is behaving correctly.** Details in
-[`power-architecture.md`](power-architecture.md#the-charger-is-normally-off-the-i²c-bus).
-
-## 8b. Two bring-up traps reported by a Rust porter — added 2026-09-11
-
-From `ciniml/paper_name_plate`'s `DESIGN.ja.md`. **Both sit in that document's
-§2.4 「未確定事項 / リスク」 — "Undetermined items / risks" — and carry neither the
-author's `実機確認済み` ("verified on real hardware") stamp nor a date**, unlike a
-dozen other findings in the same file that do. The author is demonstrably
-disciplined about applying that stamp, so its absence is meaningful.
-
-**Grade these as an experienced porter's practical caution, not as verified
-behaviour.** They are recorded because the failure modes are expensive and
-non-obvious, not because they are proven.
-
-### Trap 1 — `espflash monitor` / `espflash reset` can strand the board in download mode
-
-> 「`espflash monitor` / `espflash reset` の USB-JTAG リセットは PM1 管理のダウンロード
-> モード（`boot:0x21`）に落ち、本体ボタンを押すまで復帰しない。」
-
-*"The USB-JTAG reset of `espflash monitor` / `espflash reset` drops into the
-PM1-managed download mode (`boot:0x21`) and does not recover until you press the
-device's physical button."*
-
-**Practical consequence:** after flashing, reboot with the **physical button**,
-and read logs with a serial reader that **does not touch DTR/RTS**. This is
-specific to the PaperMono because download mode is arbitrated by the M5PM1, not
-by the usual auto-reset transistor pair — see
-[`commands.md`](commands.md) §"Enter download mode" and the vendor-page conflict
-recorded as C-5 in [`compatibility-and-status.md`](compatibility-and-status.md).
-
-### Trap 2 — the I²C speed setting survives an ESP32 reset
-
-> 「PM1/IOE1 の SPD ビット(400 kHz)は常時給電のため ESP32 リセット後も残り、100 kHz
-> アクセスが部分的に失敗する。`main.rs` の `recover_i2c_speed` が 400 kHz で SPD を戻す。
-> `I2C_CFG` 書き込み直後は 5 ms 待つ（次トランザクションが NACK になる）。」
-
-*"Because PM1/IOE1 are permanently powered, the SPD bit (400 kHz) persists even
-after an ESP32 reset, and 100 kHz access partially fails. `recover_i2c_speed` in
-`main.rs` restores SPD at 400 kHz. Wait 5 ms immediately after writing `I2C_CFG`
-(the next transaction will NACK)."*
-
-This is the more insidious of the two. The bus starts at 100 kHz and is raised to
-400 kHz after bring-up (needed to meet the NFC tag-emulation response deadline).
-Because **the expander and PMIC are on always-on rails**, they keep the fast-mode
-bit across a host reset — so a fresh boot's 100 kHz probing **partially** fails.
-Partially, which is the worst kind.
-
-**⚠ The source never says where the SPD bit is.** Its register maps list
-M5IOE1 `I2C_CFG (0x23)` and M5PM1 `I2C_CFG (0x09)` documenting only *"low 4 bits
-= sleep"* / *"sleep timeout"*. No address or bit index for SPD appears anywhere
-in the document, and `pm1.rs` / `ioe1.rs` were not captured. **A porter cannot
-act on this without reading that source.** Recorded as a lead, not a recipe.
-
-Cross-check against this knowledge base's own
-[M5IOE1 register map](../../../components/m5stack/m5ioe1/README.md) before
-relying on either address.
-
-## 9. What is not established
-
-- **Nothing here was run.** No build, no flash, no monitor, no recovery, on any board.
-- **No console baud rate is documented** by the vendor for any framework.
-- **JTAG/debugging has not been demonstrated by anyone**, in any source located. The external
-  pin group is definitively consumed; the USB-Serial/JTAG path is inferred and untested.
-- **The `-DARDUINO_USB_MODE=1` semantic was not verified** against arduino-esp32's own board
-  definitions in this pass.
-- **UiFlow2 has no documented version floor, block list or limitation** — the vendor page is
-  empty of all three ([G4](gaps-and-conflicts.md#g4--uiflow2-support-is-advertised-but-undocumented)).
-- **RadioLib's LGPL-3.0 obligations were not analysed**, only noticed.
-- **No one has reported a flashing session on real PaperMono hardware** in any source found in
-  two broad passes — see [`community.md`](community.md).
-
-## Related
-
-- [`commands.md`](commands.md) — the command ledger, with tool versions and true execution status
-- [`factory-firmware.md`](factory-firmware.md) — what is in the shipped images, and restore evidence
-- [`features/usb-and-serial.md`](features/usb-and-serial.md) — ports, console, flashing routes, debugging
-- [`compatibility-and-status.md`](compatibility-and-status.md) — version-keyed working/failing reports
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — every conflict cited above
-- [`sources.md`](sources.md) — S01, S04, S07, S09, S14, S38, S40–S47, S96
diff --git a/devices/m5stack/papermono/examples/best.md b/devices/m5stack/papermono/examples/best.md
deleted file mode 100644
index 7a69abc..0000000
--- a/devices/m5stack/papermono/examples/best.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# PaperMono — selected examples
-
-> Portfolio selected 2026-09-01 from the 43-entry population in
-> [`catalog.json`](catalog.json). Population research is in
-> [`../projects-and-community.md`](../projects-and-community.md); feature-to-evidence
-> mapping is in [`../coverage.md`](../coverage.md).
-
-> **Nothing here was built, flashed or run.** There is no PaperMono in this
-> project. Every selection is a judgement from reading source and repository
-> metadata — `inferred`, never `executed-success`. Build status for every entry
-> in the catalogue is `not-built`.
-
-**No example source is vendored.** The catalogue records canonical URLs, pinned
-commit SHAs and immutable tree URLs instead. All 43 repositories resolved and
-were pinned; none were gone or private.
-
-## The portfolio
-
-| # | Project | Commit | Licence | Why it is here |
-|---|---|---|---|---|
-| 1 | [`m5stack/M5PaperMono-UserDemo`](https://github.com/m5stack/M5PaperMono-UserDemo) | `c1099107` | MIT | The only artifact exercising **NFC, LoRa, IMU, RTC, PDM, buzzer, RGB and the M5PM1/M5IOE1 power path together** |
-| 2 | [`m5stack/M5PaperMono-OTP-Demo`](https://github.com/m5stack/M5PaperMono-OTP-Demo) | `c7c02554` | MIT | Best e-paper diagnostic — drives the panel from built-in OTP waveforms |
-| 3 | [`m5stack/M5PM1`](https://github.com/m5stack/M5PM1) | `be9a5456` | MIT | The register documentation for a custom chip that has none |
-| 4 | [`m5stack/M5IOE1`](https://github.com/m5stack/M5IOE1) | `846eec7d` | MIT | Same; also the source of the `PIN_n` off-by-one trap |
-| 5 | [`m5stack/M5GFX`](https://github.com/m5stack/M5GFX) | `d91077b9` | MIT | The shipped display path, board probe and OPI-PSRAM abort |
-| 6 | [`m5stack/M5Unified`](https://github.com/m5stack/M5Unified) | `8530f537` | MIT | Defines `board_M5PaperMono`; cheapest route to a working build |
-| 7 | [`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader) | `e6139861` | MIT | Best integrated third-party application shipping PaperMono support |
-| 8 | [`Free-Ink/freeink-sdk`](https://github.com/Free-Ink/freeink-sdk) | `24003795` | MIT | Cleanest illustration of how a PaperMono port is structured |
-| 9 | [`MagicCube/free-ink-on-paper-mono`](https://github.com/MagicCube/free-ink-on-paper-mono) | `34cc8794` | **none** | **Negative example — see below** |
-
-Nine selected, plus one deliberate negative. Ten of 43.
-
-## Why the negative example is here
-
-`free-ink-on-paper-mono` demonstrates FreeInk running on this exact board and
-carries an unmerged partial-refresh patch that is directly relevant to the
-device's known refresh problems. It is also the single most tempting thing in
-the population to copy from.
-
-**It has no `LICENSE` file.** Absent an explicit grant, the code is
-all-rights-reserved by default. Read it for technique; do not copy it. It is
-selected precisely so that this is recorded rather than discovered later by
-someone who has already pasted from it.
-
-Nine other repositories in the catalogue likewise carry no detected licence —
-`escape-hatch`, `m5stack-board-id`, `PaperMonoCalendar`, `learning-paper-mono`,
-`buddy-watch`, `M5PaperMono-HomeAssistant-ESPHome`, `PaperMono`,
-`claude-desktop-buddy`. One apparent case is **not** real: `esphome/esphome`
-reports `NOASSERTION` because GitHub's detector cannot classify its split
-GPLv3/custom licence. That distinction is recorded per-entry.
-
-## Feature coverage, and what is not covered
-
-| Feature | Covered by | Confidence |
-|---|---|---|
-| E-paper, waveforms, refresh | #2, #5, #9 | good — three independent implementations |
-| Touch | #1, #5 | adequate |
-| Power states, M5PM1 | #1, #3 | good |
-| I/O expander | #1, #4 | good |
-| NFC | **#1 only** | thin |
-| LoRa | **#1 only** | thin |
-| IMU, RTC, microSD, PDM, buzzer, RGB | #1, #6 | adequate |
-| Wi-Fi / BLE | #7 | generic ESP32-S3, nothing board-specific |
-| Frontlight | #1, #5 | adequate |
-
-**NFC and LoRa rest on a single artifact each — the vendor's own demo.** There
-is no independent implementation of either on this board. If that demo is wrong,
-nothing in the population contradicts it, and this record inherits the error.
-That is the most important limitation of the whole example survey.
-
-## Slots the method asks for that could not be filled
-
-Stated rather than padded:
-
-- **No integrated application demonstrated on PaperMono hardware by an
-  independent author.** `crosspoint-reader` ships support; whether it has been
-  run on this board is not established here.
-- **No performance or resource-limit example.** Nothing in the population
-  measures refresh timing, current draw, memory pressure or concurrency.
-- **No negative example of a *failure mode*** — the one negative entry is a
-  licensing hazard, not a demonstrated technical failure.
-- **No example exercising realistic feature combinations** (e-paper + microSD +
-  Wi-Fi concurrently, or LoRa + Wi-Fi). See
-  [`../resources-and-conflicts.md`](../resources-and-conflicts.md).
-
-The population is days old — the device shipped 2026-08-21 and this snapshot is
-2026-09-01 — so these gaps reflect the world, not the search.
-
-## Reacquisition
-
-```bash
-# pinned clone of any selected example
-git clone https://github.com/<owner>/<repo> && git -C <repo> checkout <commit>
-```
-
-Commits are in the table above and in every catalogue entry as `commit` /
-`immutable_url`. See [`search-log.md`](search-log.md) for how the population was
-found.
diff --git a/devices/m5stack/papermono/examples/catalog.json b/devices/m5stack/papermono/examples/catalog.json
deleted file mode 100644
index dc83712..0000000
--- a/devices/m5stack/papermono/examples/catalog.json
+++ /dev/null
@@ -1,1753 +0,0 @@
-{
-  "schema": "hardware-doc/example-catalog/1",
-  "device": "M5Stack PaperMono (SKU C153)",
-  "device_record": "devices/m5stack/papermono",
-  "generated": "2026-09-01",
-  "population_source": "devices/m5stack/papermono/projects-and-community.md",
-  "hardware_available": false,
-  "note": "No example was built, flashed or run: there is no PaperMono in this project. Every entry is static inspection only. Source is NOT vendored in this pass — links and pinned commits are recorded instead, per the size policy in SIZE-AUDIT.md.",
-  "class_legend": {
-    "D": "demonstrated on PaperMono hardware by its author",
-    "S": "upstream project that ships PaperMono support",
-    "V": "official M5Stack vendor example / binary",
-    "P": "proposed or explicitly untested PaperMono support",
-    "C": "copy, fork or vendored tree",
-    "N": "adjacent / negative example — not PaperMono-targeting"
-  },
-  "count": 43,
-  "examples": [
-    {
-      "id": "EX01",
-      "title": "esphome",
-      "author": "esphome",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/esphome/esphome",
-      "immutable_url": "https://github.com/esphome/esphome/tree/b8480b8424a3b6248c234ed0f78291813129e144",
-      "commit": "b8480b8424a3b6248c234ed0f78291813129e144",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-02",
-      "created": "2018-04-06",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 11627,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "GitHub reports NOASSERTION; ESPHome ships a split GPLv3 / custom licence that GitHub's detector does not classify. Not 'unlicensed'.",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "ESPHome is a system to control your ESP32, ESP8266, BK72xx, RP2040 by simple yet powerful configuration files ",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX02",
-      "title": "crosspoint-reader",
-      "author": "crosspoint-reader",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/crosspoint-reader/crosspoint-reader",
-      "immutable_url": "https://github.com/crosspoint-reader/crosspoint-reader/tree/e6139861a2a8c634aa18c333b7e214ee51a9965c",
-      "commit": "e6139861a2a8c634aa18c333b7e214ee51a9965c",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2025-12-03",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 7490,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Open-source e-reader firmware",
-      "selected": true,
-      "selection_reason": "The most substantial third-party firmware that ships PaperMono support, MIT, actively maintained. Best integrated application in the population."
-    },
-    {
-      "id": "EX03",
-      "title": "Launcher",
-      "author": "bmorcelli",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/bmorcelli/Launcher",
-      "immutable_url": "https://github.com/bmorcelli/Launcher/tree/69fdc7d127f516766f0406b609091b90887b83cf",
-      "commit": "69fdc7d127f516766f0406b609091b90887b83cf",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2024-02-10",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 2047,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Firmware Launcher for ESP32 boards like: M5Stack, Lilygo, Marauder and CYD devices.",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX04",
-      "title": "trmnl-firmware",
-      "author": "usetrmnl",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/usetrmnl/trmnl-firmware",
-      "immutable_url": "https://github.com/usetrmnl/trmnl-firmware/tree/8f84e23002197fefb4a53eb3a1d8a10657e0b583",
-      "commit": "8f84e23002197fefb4a53eb3a1d8a10657e0b583",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-02",
-      "created": "2024-01-13",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 1154,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "GPL-3.0",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "TRMNL ePaper device firmware",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX05",
-      "title": "ESPHomeDesigner",
-      "author": "koosoli",
-      "class": "P",
-      "class_meaning": "proposed or explicitly untested PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/koosoli/ESPHomeDesigner",
-      "immutable_url": "https://github.com/koosoli/ESPHomeDesigner/tree/0d82d6763c36b23cfd153d44126d8cd2b7d09425",
-      "commit": "0d82d6763c36b23cfd153d44126d8cd2b7d09425",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-26",
-      "created": "2025-11-12",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 1064,
-      "language": "JavaScript",
-      "is_fork": false,
-      "archived": false,
-      "license": "GPL-3.0",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "A visual drag-and-drop editor for ESPHome displays (E-Ink, OLED, LCD, Touch), running as a Home Assistant inte",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX06",
-      "title": "M5Unified",
-      "author": "m5stack",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/M5Unified",
-      "immutable_url": "https://github.com/m5stack/M5Unified/tree/8530f5377d782e4a25a6c482de2e71c3f75ca8eb",
-      "commit": "8530f5377d782e4a25a6c482de2e71c3f75ca8eb",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-02",
-      "created": "2021-10-09",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 689,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Unified library for M5Stack series",
-      "selected": true,
-      "selection_reason": "Board abstraction that defines board_M5PaperMono; the cheapest route to a working build."
-    },
-    {
-      "id": "EX07",
-      "title": "M5GFX",
-      "author": "m5stack",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/M5GFX",
-      "immutable_url": "https://github.com/m5stack/M5GFX/tree/d91077b9a607b59404e4e4a49f775c792bfae382",
-      "commit": "d91077b9a607b59404e4e4a49f775c792bfae382",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-27",
-      "created": "2021-05-28",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 372,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Graphics library for M5Stack series",
-      "selected": true,
-      "selection_reason": "The display path the vendor ships, including the board-probe identification and the OPI-PSRAM abort. Needed even if you ultimately bypass its waveforms."
-    },
-    {
-      "id": "EX08",
-      "title": "freeink-sdk",
-      "author": "Free-Ink",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/Free-Ink/freeink-sdk",
-      "immutable_url": "https://github.com/Free-Ink/freeink-sdk/tree/24003795381a6c23630a26472ae3b06550333e71",
-      "commit": "24003795381a6c23630a26472ae3b06550333e71",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-02",
-      "created": "2026-06-03",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 245,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "A hardware-independent SDK for building e-paper reader firmware.",
-      "selected": true,
-      "selection_reason": "The hardware-independent SDK underneath much of the ecosystem; the cleanest example of how a PaperMono port is structured."
-    },
-    {
-      "id": "EX09",
-      "title": "uiflow-micropython",
-      "author": "m5stack",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/uiflow-micropython",
-      "immutable_url": "https://github.com/m5stack/uiflow-micropython/tree/587e134c61b31431335351e04ebfc05f69064bb7",
-      "commit": "587e134c61b31431335351e04ebfc05f69064bb7",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-31",
-      "created": "2022-01-10",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 207,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "uiflow micropython project",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX10",
-      "title": "bb_epaper",
-      "author": "bitbank2",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/bitbank2/bb_epaper",
-      "immutable_url": "https://github.com/bitbank2/bb_epaper/tree/bfb8dbca98f21e438d8cb23d306b057f516b6819",
-      "commit": "bfb8dbca98f21e438d8cb23d306b057f516b6819",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2024-09-11",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 205,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "GPL-3.0",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "A frustration-free library for working with all 24-pin eink panels",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX11",
-      "title": "crossmux",
-      "author": "0x1abin",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/0x1abin/crossmux",
-      "immutable_url": "https://github.com/0x1abin/crossmux/tree/85f7696b3ee51e0a067cdc012cfabc2783616f3a",
-      "commit": "85f7696b3ee51e0a067cdc012cfabc2783616f3a",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-02",
-      "created": "2026-05-09",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 161,
-      "language": "C",
-      "is_fork": true,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "CrossMux is a community fork of CrossPoint Reader that turns the device into more than a reader — it adds an A",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX12",
-      "title": "witchhunt-reader",
-      "author": "jpirnay",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/jpirnay/witchhunt-reader",
-      "immutable_url": "https://github.com/jpirnay/witchhunt-reader/tree/06dbd15baeacbe784d104a3c3e962d48d89adb3e",
-      "commit": "06dbd15baeacbe784d104a3c3e962d48d89adb3e",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-05-28",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 159,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Witch(hunt) Reader ",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX13",
-      "title": "esphome-yaml",
-      "author": "m5stack",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/esphome-yaml",
-      "immutable_url": "https://github.com/m5stack/esphome-yaml/tree/c515c83edc1aa16f11e0297d95a8528ae485931c",
-      "commit": "c515c83edc1aa16f11e0297d95a8528ae485931c",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-21",
-      "created": "2025-10-10",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 70,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "M5Stack ESPHome Integrations",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX14",
-      "title": "crosspoint-simulator",
-      "author": "crosspoint-reader",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/crosspoint-reader/crosspoint-simulator",
-      "immutable_url": "https://github.com/crosspoint-reader/crosspoint-simulator/tree/6aa3b5476f783953bff4ae8aa0b84d9a64dd07ef",
-      "commit": "6aa3b5476f783953bff4ae8aa0b84d9a64dd07ef",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-30",
-      "created": "2026-03-17",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 54,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Simulate Crosspoint firmware without flashing onto your device",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX15",
-      "title": "crosspoint-tools",
-      "author": "crosspoint-reader",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/crosspoint-reader/crosspoint-tools",
-      "immutable_url": "https://github.com/crosspoint-reader/crosspoint-tools/tree/a3f0abf6a06fe0abe9309b3e0ff3c25aea11579a",
-      "commit": "a3f0abf6a06fe0abe9309b3e0ff3c25aea11579a",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-05-15",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 34,
-      "language": "JavaScript",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Website and tools for CrossPoint & Xteink devices",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX16",
-      "title": "midad-by-foulad",
-      "author": "sfoulad",
-      "class": "P",
-      "class_meaning": "proposed or explicitly untested PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/sfoulad/midad-by-foulad",
-      "immutable_url": "https://github.com/sfoulad/midad-by-foulad/tree/ef3b455c3aa9ea06204cabbae717b05bc28c1803",
-      "commit": "ef3b455c3aa9ea06204cabbae717b05bc28c1803",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-07-02",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 31,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Midad by Foulad — Arabic-first e-reader firmware for Xteink X4/X3. Fork of CrossPoint Reader with full Arabic ",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX17",
-      "title": "M5PaperMono-UserDemo",
-      "author": "m5stack",
-      "class": "V",
-      "class_meaning": "official M5Stack vendor example / binary",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/M5PaperMono-UserDemo",
-      "immutable_url": "https://github.com/m5stack/M5PaperMono-UserDemo/tree/c1099107271d31a0678d661a896e2b04dbb331ea",
-      "commit": "c1099107271d31a0678d661a896e2b04dbb331ea",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-10",
-      "created": "2026-05-07",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 10,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "M5Stack PaperMono user demo for hardware evaluation.",
-      "selected": true,
-      "selection_reason": "Only artifact that exercises NFC, LoRa, IMU, RTC, PDM, buzzer, RGB and the M5PM1/M5IOE1 power path together. It is the reference for every board-specific pin and register in this record."
-    },
-    {
-      "id": "EX18",
-      "title": "escape-hatch",
-      "author": "crosspoint-reader",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/crosspoint-reader/escape-hatch",
-      "immutable_url": "https://github.com/crosspoint-reader/escape-hatch/tree/90841adf6304354d1393936d1ca203294b76c09b",
-      "commit": "90841adf6304354d1393936d1ca203294b76c09b",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-22",
-      "created": "2026-06-23",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 9,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "A minimal SD-Card firmware flasher for X3/X4 devices at just 400kb",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX19",
-      "title": "CrossDiTo",
-      "author": "dito94",
-      "class": "C",
-      "class_meaning": "copy, fork or vendored tree",
-      "source_class": "community",
-      "canonical_url": "https://github.com/dito94/CrossDiTo",
-      "immutable_url": "https://github.com/dito94/CrossDiTo/tree/4506e2e9516dc1330695cb6f4c337e7d12a7fe55",
-      "commit": "4506e2e9516dc1330695cb6f4c337e7d12a7fe55",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-21",
-      "created": "2026-08-21",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 5,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Personal Xteink X4 Pro firmware fork of CrossInk 1.5.",
-      "selected": false,
-      "selection_reason": "Not selected: copy/fork of a selected upstream; lineage recorded instead."
-    },
-    {
-      "id": "EX20",
-      "title": "M5PM1",
-      "author": "m5stack",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/M5PM1",
-      "immutable_url": "https://github.com/m5stack/M5PM1/tree/be9a5456c007c333e7ac963f33bfde1ffa5d82ee",
-      "commit": "be9a5456c007c333e7ac963f33bfde1ffa5d82ee",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-05-29",
-      "created": "2026-01-04",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 5,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "M5Stack PMIC chip PM1 driver library",
-      "selected": true,
-      "selection_reason": "The M5PM1 is a custom chip with no public datasheet beyond a user manual; this library IS the register documentation. Required for any power-state work."
-    },
-    {
-      "id": "EX21",
-      "title": "M5IOE1",
-      "author": "m5stack",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/M5IOE1",
-      "immutable_url": "https://github.com/m5stack/M5IOE1/tree/846eec7d05e25c09013be2acdb8804487f48a62e",
-      "commit": "846eec7d05e25c09013be2acdb8804487f48a62e",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-05-29",
-      "created": "2026-01-04",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 4,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "M5Stack IO Extension IOE1 Chip Driver Library",
-      "selected": true,
-      "selection_reason": "Same rationale as M5PM1. Also the source of the PIN_n off-by-one trap documented in pin-naming-and-the-pyg-ambiguity.md."
-    },
-    {
-      "id": "EX22",
-      "title": "free-ink-on-paper-mono",
-      "author": "MagicCube",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/MagicCube/free-ink-on-paper-mono",
-      "immutable_url": "https://github.com/MagicCube/free-ink-on-paper-mono/tree/34cc879427d5fc0b35f6af5084d4e7a003457665",
-      "commit": "34cc879427d5fc0b35f6af5084d4e7a003457665",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-27",
-      "created": "2026-08-25",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 4,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Local Loop Engineering and WYSIWYG FreeInk UI demos for M5Stack PaperMono-Lite",
-      "selected": true,
-      "selection_reason": "NEGATIVE EXAMPLE — selected deliberately. Demonstrates FreeInk on PaperMono and carries an unmerged partial-refresh patch, but has NO LICENSE FILE, so its code is all-rights-reserved and must not be copied. Read for technique, not for reuse."
-    },
-    {
-      "id": "EX23",
-      "title": "m5stack-board-id",
-      "author": "m5stack",
-      "class": "S",
-      "class_meaning": "upstream project that ships PaperMono support",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/m5stack-board-id",
-      "immutable_url": "https://github.com/m5stack/m5stack-board-id/tree/f7e2d4a4f34dfd1fb9be0630b4102cb67d3d4cca",
-      "commit": "f7e2d4a4f34dfd1fb9be0630b4102cb67d3d4cca",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-17",
-      "created": "2023-08-25",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 3,
-      "language": null,
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX24",
-      "title": "eego-a4-template-firmware",
-      "author": "Lakphy",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/Lakphy/eego-a4-template-firmware",
-      "immutable_url": "https://github.com/Lakphy/eego-a4-template-firmware/tree/404f7b8d49dfae5d3914a96f8d23b198b9381ca0",
-      "commit": "404f7b8d49dfae5d3914a96f8d23b198b9381ca0",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-07-26",
-      "created": "2026-07-26",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 2,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Open-source EEGO A4 hardware template firmware with diagnostics, drivers, examples, safe flashing, and recover",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX25",
-      "title": "M5PaperMono-OTP-Demo",
-      "author": "m5stack",
-      "class": "V",
-      "class_meaning": "official M5Stack vendor example / binary",
-      "source_class": "primary",
-      "canonical_url": "https://github.com/m5stack/M5PaperMono-OTP-Demo",
-      "immutable_url": "https://github.com/m5stack/M5PaperMono-OTP-Demo/tree/c7c02554f89fd06f80d988b805b2a59050c78a46",
-      "commit": "c7c02554f89fd06f80d988b805b2a59050c78a46",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-20",
-      "created": "2026-08-20",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 2,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "",
-      "selected": true,
-      "selection_reason": "The vendor's own answer to its warning that M5GFX waveforms are unstable: drives the panel from built-in OTP waveforms. Minimal, single-purpose, and the best e-paper diagnostic starting point."
-    },
-    {
-      "id": "EX26",
-      "title": "PaperMono-Launcher",
-      "author": "MingRZou",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/MingRZou/PaperMono-Launcher",
-      "immutable_url": "https://github.com/MingRZou/PaperMono-Launcher/tree/daf3edcee4f8669e2adf7a58bc174d62e4e40f42",
-      "commit": "daf3edcee4f8669e2adf7a58bc174d62e4e40f42",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-30",
-      "created": "2026-08-30",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 2,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Hardware-validated PaperMono-focused Launcher development",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX27",
-      "title": "crosspoint-x-reader",
-      "author": "Belphemur",
-      "class": "P",
-      "class_meaning": "proposed or explicitly untested PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/Belphemur/crosspoint-x-reader",
-      "immutable_url": "https://github.com/Belphemur/crosspoint-x-reader/tree/40c74b0e4042ca750baf9e54b3011d1ae2e896a5",
-      "commit": "40c74b0e4042ca750baf9e54b3011d1ae2e896a5",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-02",
-      "created": "2026-08-25",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 1,
-      "language": "C",
-      "is_fork": true,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Open-source e-reader firmware",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX28",
-      "title": "crosspoint-reader-mono",
-      "author": "MarsTechHAN",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/MarsTechHAN/crosspoint-reader-mono",
-      "immutable_url": "https://github.com/MarsTechHAN/crosspoint-reader-mono/tree/87a191fcea17a9658686083187765c600ad03866",
-      "commit": "87a191fcea17a9658686083187765c600ad03866",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-12",
-      "created": "2026-07-29",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 1,
-      "language": "C",
-      "is_fork": true,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Firmware for the Xteink X3 and X4 e-readers",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX29",
-      "title": "freeink-sdk-mono",
-      "author": "MarsTechHAN",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/MarsTechHAN/freeink-sdk-mono",
-      "immutable_url": "https://github.com/MarsTechHAN/freeink-sdk-mono/tree/f5518c7a39d3956dbc9d43be508bf9edae8f222d",
-      "commit": "f5518c7a39d3956dbc9d43be508bf9edae8f222d",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-12",
-      "created": "2026-07-29",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 1,
-      "language": "C++",
-      "is_fork": true,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "A hardware-independent SDK for building e-paper reader firmware.",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX30",
-      "title": "Inkkit",
-      "author": "mohitagw15856",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/mohitagw15856/Inkkit",
-      "immutable_url": "https://github.com/mohitagw15856/Inkkit/tree/5e2f741868eb3d3609ad9b72e74afca2e7cba1fd",
-      "commit": "5e2f741868eb3d3609ad9b72e74afca2e7cba1fd",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-07-31",
-      "created": "2026-07-29",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 1,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Shared device-layer HAL for freeink-sdk e-ink firmware (Xteink X4/X3, ESP32-C3): one tested, header-first Plat",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX31",
-      "title": "renvo",
-      "author": "tinyrange",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/tinyrange/renvo",
-      "immutable_url": "https://github.com/tinyrange/renvo/tree/1215bdd5d69824b924d06572ad4476460dbff044",
-      "commit": "1215bdd5d69824b924d06572ad4476460dbff044",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-06-22",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 1,
-      "language": "Go",
-      "is_fork": false,
-      "archived": false,
-      "license": "Apache-2.0",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Retargetable Go compiler",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX32",
-      "title": "freeink-sdk",
-      "author": "Belphemur",
-      "class": "P",
-      "class_meaning": "proposed or explicitly untested PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/Belphemur/freeink-sdk",
-      "immutable_url": "https://github.com/Belphemur/freeink-sdk/tree/089bd85a71bed6e0e5ef635dbae3da56dd12a2fd",
-      "commit": "089bd85a71bed6e0e5ef635dbae3da56dd12a2fd",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-08-28",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": true,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "A hardware-independent SDK for building e-paper reader firmware.",
-      "selected": true,
-      "selection_reason": "The hardware-independent SDK underneath much of the ecosystem; the cleanest example of how a PaperMono port is structured."
-    },
-    {
-      "id": "EX33",
-      "title": "sticky-rs",
-      "author": "canardleteer",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/canardleteer/sticky-rs",
-      "immutable_url": "https://github.com/canardleteer/sticky-rs/tree/abf4be23435cbf8d0d4897e464b7cf08f14e4aaa",
-      "commit": "abf4be23435cbf8d0d4897e464b7cf08f14e4aaa",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-08-29",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "Rust",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Seeed Sticky Embedded Rust Repository ",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX34",
-      "title": "PaperMonoCalendar",
-      "author": "EggUncle",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/EggUncle/PaperMonoCalendar",
-      "immutable_url": "https://github.com/EggUncle/PaperMonoCalendar/tree/53385729b35249c4fe4f8a3f2d7ded6ad2de5696",
-      "commit": "53385729b35249c4fe4f8a3f2d7ded6ad2de5696",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-31",
-      "created": "2026-08-31",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "M5Stack PaperMono calendar firmware with BLE activity tiles, pixel clock and RTC sync",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX35",
-      "title": "inkback-freeink-sdk",
-      "author": "goodyttoor",
-      "class": "C",
-      "class_meaning": "copy, fork or vendored tree",
-      "source_class": "community",
-      "canonical_url": "https://github.com/goodyttoor/inkback-freeink-sdk",
-      "immutable_url": "https://github.com/goodyttoor/inkback-freeink-sdk/tree/d26ab55af1c67d451de99f08280a6de83608fd0b",
-      "commit": "d26ab55af1c67d451de99f08280a6de83608fd0b",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-18",
-      "created": "2026-07-28",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "InkBack's FreeInk SDK fork — InkMotion (PSRAM multi-buffer, damage windows, ghost budget) and X4 Pro display w",
-      "selected": false,
-      "selection_reason": "Not selected: copy/fork of a selected upstream; lineage recorded instead."
-    },
-    {
-      "id": "EX36",
-      "title": "learning-paper-mono",
-      "author": "GOROman",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/GOROman/learning-paper-mono",
-      "immutable_url": "https://github.com/GOROman/learning-paper-mono/tree/21abc4ec84f17b3966bc7c936f78a1e4facc6372",
-      "commit": "21abc4ec84f17b3966bc7c936f78a1e4facc6372",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-02",
-      "created": "2026-09-02",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX37",
-      "title": "buddy-watch",
-      "author": "hawkymisc",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/hawkymisc/buddy-watch",
-      "immutable_url": "https://github.com/hawkymisc/buddy-watch/tree/b28c7d06b5c0a39651dcf837c8b2192c6984b2d8",
-      "commit": "b28c7d06b5c0a39651dcf837c8b2192c6984b2d8",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-24",
-      "created": "2026-08-22",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "M5Stack StopWatch firmware: Codex Micro controller + Claude Desktop Hardware Buddy on one watch, with a boot-t",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX38",
-      "title": "M5PaperMono-HomeAssistant-ESPHome",
-      "author": "hectorzin",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/hectorzin/M5PaperMono-HomeAssistant-ESPHome",
-      "immutable_url": "https://github.com/hectorzin/M5PaperMono-HomeAssistant-ESPHome/tree/c144086af7291f6340422361534e9374fa4d2bdd",
-      "commit": "c144086af7291f6340422361534e9374fa4d2bdd",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-08-27",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX39",
-      "title": "TamaInk",
-      "author": "HenryBaby",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/HenryBaby/TamaInk",
-      "immutable_url": "https://github.com/HenryBaby/TamaInk/tree/49751164e1fece0e7c0e8460942c121e68c3919b",
-      "commit": "49751164e1fece0e7c0e8460942c121e68c3919b",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-31",
-      "created": "2026-07-31",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "AGPL-3.0",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "An attempt at a Tamagotchi P1 emulator running on an Xteink X3/X4. ",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX40",
-      "title": "SeeSeeBook",
-      "author": "LuoIsHere",
-      "class": "D",
-      "class_meaning": "demonstrated on PaperMono hardware by its author",
-      "source_class": "community",
-      "canonical_url": "https://github.com/LuoIsHere/SeeSeeBook",
-      "immutable_url": "https://github.com/LuoIsHere/SeeSeeBook/tree/64bc8332628f00d025a6f68e72fe951d9db9f44f",
-      "commit": "64bc8332628f00d025a6f68e72fe951d9db9f44f",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-08-28",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX41",
-      "title": "PaperMono",
-      "author": "namelessmucguy",
-      "class": "N",
-      "class_meaning": "adjacent / negative example — not PaperMono-targeting",
-      "source_class": "community",
-      "canonical_url": "https://github.com/namelessmucguy/PaperMono",
-      "immutable_url": "https://github.com/namelessmucguy/PaperMono/tree/ed2a1dae2fcd2f9fddb1ccdf87f7aecef274985d",
-      "commit": "ed2a1dae2fcd2f9fddb1ccdf87f7aecef274985d",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-09-01",
-      "created": "2026-09-01",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "project for esp32 s3 - PaperMono",
-      "selected": false,
-      "selection_reason": "Not selected: adjacent or non-PaperMono work, retained for lineage and to prevent re-investigation."
-    },
-    {
-      "id": "EX42",
-      "title": "claude-desktop-buddy",
-      "author": "shelbeeely",
-      "class": "P",
-      "class_meaning": "proposed or explicitly untested PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/shelbeeely/claude-desktop-buddy",
-      "immutable_url": "https://github.com/shelbeeely/claude-desktop-buddy/tree/15d5e2c947686151453d9c849217442096b384d0",
-      "commit": "15d5e2c947686151453d9c849217442096b384d0",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-22",
-      "created": "2026-08-20",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": true,
-      "archived": false,
-      "license": null,
-      "license_evidence": "NO LICENSE FILE DETECTED — all rights reserved by default; do not copy code",
-      "device_target": "M5Stack PaperMono (C153), schematic rev V0.6.2",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "Reference and an example for the Bluetooth API for makers in Claude Cowork & Claude Code Desktop",
-      "selected": false,
-      "selection_reason": "Not selected: superseded by a broader selected example covering the same features."
-    },
-    {
-      "id": "EX43",
-      "title": "esphome-xteink",
-      "author": "vjFaLk",
-      "class": "C",
-      "class_meaning": "copy, fork or vendored tree",
-      "source_class": "community",
-      "canonical_url": "https://github.com/vjFaLk/esphome-xteink",
-      "immutable_url": "https://github.com/vjFaLk/esphome-xteink/tree/b36c09f2f3926c07aeb4b91ff4371db94037ef79",
-      "commit": "b36c09f2f3926c07aeb4b91ff4371db94037ef79",
-      "retrieved": "2026-09-01",
-      "last_activity": "2026-08-30",
-      "created": "2026-08-30",
-      "release_tag": null,
-      "_note_release_tag": "not collected in this pass",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub licence detection",
-      "device_target": "other / not PaperMono",
-      "build_status": "not-built",
-      "run_status": "not-tested",
-      "test_environment": "none — no PaperMono hardware exists in this project",
-      "evidence_status": "inferred (static inspection of the repository only)",
-      "description": "ESPHome components for Xteink X4 / X3 / X4 Pro e-paper readers, built on the FreeInk SDK",
-      "selected": false,
-      "selection_reason": "Not selected: copy/fork of a selected upstream; lineage recorded instead."
-    },
-    {
-      "id": "EX44",
-      "title": "paper_name_plate",
-      "author": "ciniml",
-      "class": "A",
-      "class_meaning": "active third-party project targeting PaperMono",
-      "source_class": "community",
-      "canonical_url": "https://github.com/ciniml/paper_name_plate",
-      "immutable_url": "https://github.com/ciniml/paper_name_plate/tree/7eac75dfc9a8c34509e383fd256473cf95bc5b52",
-      "commit": "7eac75dfc9a8c34509e383fd256473cf95bc5b52",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-06",
-      "created": "2026-09-05",
-      "release_tag": "v0.1.0",
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 0,
-      "language": "Rust",
-      "is_fork": false,
-      "archived": false,
-      "license": "NOASSERTION",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11; NOASSERTION = no licence file present, all rights reserved by default",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "Bare-metal Rust name-badge firmware. NFC Type-2 tag emulation, BLE full-screen image push (protocol v2, ~12-14 s), 4-greyscale e-paper at a measured 95 ms/update. Its DESIGN.ja.md is the most detailed third-party bring-up record for this board.",
-      "selected": true,
-      "selection_reason": "Most detailed third-party bring-up record; primary source for multiple device findings",
-      "default_branch": "master",
-      "forks": 0,
-      "size_kb": 157,
-      "language_breakdown": "Rust 96%, Python 3%",
-      "topics": [],
-      "build_system": "Cargo (bare-metal, esp-hal 1.1, esp-radio + bleps)",
-      "upstream_description": "M5Stack PaperMono name plate firmware in bare-metal Rust (e-paper, NFC tag emulation, BLE)",
-      "notes": "Author stamps hardware-verified findings with 実機確認済み and dates. Source of the IOE1 bit positions, the espflash download-mode trap, the I2C SPD-persistence trap, and the disputed esp-hal 1.1 light-sleep report. Contains a Rust analogue of the M5Unit-NFC unclamped-FIFO defect (t2t_emu.rs:397) which panics rather than corrupting.",
-      "commit_date": "2026-09-06",
-      "commit_subject": "README: flashing a release",
-      "analysed_at_commit": "7eac75dfc9a8c34509e383fd256473cf95bc5b52",
-      "analysed_at_note": "same as current HEAD at time of retrieval",
-      "prior_refs": [
-        {
-          "commit": "7eac75dfc9a8c34509e383fd256473cf95bc5b52",
-          "date": "2026-09-06",
-          "subject": "README: flashing a release",
-          "provenance": "handoff 03-new-projects.md, 2026-09-11; and this project's Rust code review",
-          "resolves": true,
-          "verified": "2026-09-11",
-          "url": "https://github.com/ciniml/paper_name_plate/tree/7eac75dfc9a8c34509e383fd256473cf95bc5b52"
-        }
-      ],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    },
-    {
-      "id": "EX45",
-      "title": "papermono-rs",
-      "author": "canardleteer",
-      "class": "A",
-      "class_meaning": "active third-party project targeting PaperMono",
-      "source_class": "community",
-      "canonical_url": "https://github.com/canardleteer/papermono-rs",
-      "immutable_url": "https://github.com/canardleteer/papermono-rs/tree/06e1e5ed67a05ba8f968b730a49b36b5d5fef9fb",
-      "commit": "06e1e5ed67a05ba8f968b730a49b36b5d5fef9fb",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-20",
-      "created": "2026-09-01",
-      "release_tag": null,
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 0,
-      "language": "Rust",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "Bare-metal Rust/Embassy board crate. SX1262 LoRa driver behind --features c153, a 104-slot US915 channel energy sweeper and a packet sniffer; m5pm1 and m5ioe1 driver crates.",
-      "selected": true,
-      "selection_reason": "Only MIT-licensed Rust board crate; working LoRa and PMIC/expander drivers",
-      "default_branch": "main",
-      "forks": 0,
-      "size_kb": 6154,
-      "language_breakdown": "Rust 98%, Python 1%",
-      "topics": [
-        "e-ink",
-        "eink",
-        "embedded",
-        "epaper",
-        "esp32-s3",
-        "m5stack",
-        "no-std",
-        "paper-mono",
-        "papermono",
-        "rust",
-        "ssd1677"
-      ],
-      "build_system": "Cargo workspace (no_std, Embassy)",
-      "upstream_description": "PaperMono Embedded Rust Repository",
-      "notes": "Documents the LoRa power-up timings the vendor HAL leaves implicit (15 ms rail settle, 20 ms TCXO/boot). States PaperMono-Lite's LoRa pads are unpopulated test pads. MIT-licensed, so usable as a reference unlike most of this population.",
-      "commit_date": "2026-09-20",
-      "commit_subject": "Merge pull request #1 from canardleteer/dev/canardleteer/nfc",
-      "analysed_at_commit": "67ee512024de",
-      "analysed_at_note": "⚠ documentation claims in this knowledge base were read at this earlier ref, NOT at `commit` — the repo moved afterwards",
-      "prior_refs": [
-        {
-          "commit": "67ee512024de",
-          "date": "2026-09-06",
-          "subject": "docs: audit and register st25r3916 chip crate",
-          "provenance": "handoff 03-new-projects.md 2026-09-11; LoRa/LED findings in features/lora.md were read at this ref",
-          "resolves": true,
-          "verified": "2026-09-11",
-          "url": "https://github.com/canardleteer/papermono-rs/tree/67ee512024de"
-        }
-      ],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    },
-    {
-      "id": "EX46",
-      "title": "mono-note-mini",
-      "author": "atreyap31-cell",
-      "class": "A",
-      "class_meaning": "active third-party project targeting PaperMono",
-      "source_class": "community",
-      "canonical_url": "https://github.com/atreyap31-cell/mono-note-mini",
-      "immutable_url": "https://github.com/atreyap31-cell/mono-note-mini/tree/b871239c6921876aca60ac0a6e2bc23dd4c2ce91",
-      "commit": "b871239c6921876aca60ac0a6e2bc23dd4c2ce91",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-17",
-      "created": "2026-08-24",
-      "release_tag": null,
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 0,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "NOASSERTION",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11; NOASSERTION = no licence file present, all rights reserved by default",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "Voice-only note-taking companion. Ships firmware, a companion server, 3D-printable case files and a GitHub Pages manual — unusually complete for this population.",
-      "selected": true,
-      "selection_reason": "Third-party PaperMono application shipping firmware, server and enclosure together",
-      "default_branch": "main",
-      "forks": 0,
-      "size_kb": 15193,
-      "language_breakdown": "C 45%, C++ 28%, HTML 14%, Python 6%",
-      "topics": [],
-      "build_system": "firmware/ + server/ + case/ (no root build file)",
-      "upstream_description": "Squiggly Note Pala edition - voice-only note companion for the ESP32 e-paper device",
-      "notes": "No licence file: all rights reserved by default. Homepage https://atreyap31-cell.github.io/mono-note-mini/ carries a manual.",
-      "commit_date": "2026-09-17",
-      "commit_subject": "feat: the screen turns off on USB, and the device can be switched",
-      "analysed_at_commit": "ae84a34da775",
-      "analysed_at_note": "⚠ documentation claims in this knowledge base were read at this earlier ref, NOT at `commit` — the repo moved afterwards",
-      "prior_refs": [
-        {
-          "commit": "ae84a34da775",
-          "date": "2026-09-06",
-          "subject": "feat: unlock your notes by saying a phrase",
-          "provenance": "handoff 03-new-projects.md, 2026-09-11",
-          "resolves": true,
-          "verified": "2026-09-11",
-          "url": "https://github.com/atreyap31-cell/mono-note-mini/tree/ae84a34da775"
-        }
-      ],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    },
-    {
-      "id": "EX47",
-      "title": "crossplay-papermono",
-      "author": "fperuzzo72",
-      "class": "P",
-      "class_meaning": "proposed or explicitly untested PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/fperuzzo72/crossplay-papermono",
-      "immutable_url": "https://github.com/fperuzzo72/crossplay-papermono/tree/8dc6bf2048bf7cc2d1811ec156547c5596f0604b",
-      "commit": "8dc6bf2048bf7cc2d1811ec156547c5596f0604b",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-11",
-      "created": "2026-09-11",
-      "release_tag": null,
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 2,
-      "language": "C",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "CrossPlay port to PaperMono, forked from upstream ma-r-s/crossplay. Adds [env:papermono] on esp32-s3-devkitc1-n16r8 with dio_opi memory, CROSSPOINT_WAIT_FOR_USB_SERIAL, USE_BLOCK_DEVICE_INTERFACE=1 for 1-bit SDMMC via SdFat, and a 16384-byte render task stack matching the X4 Pro.",
-      "selected": true,
-      "selection_reason": "Hands-on port with a dedicated build env; no report of it running on hardware",
-      "default_branch": "papermono-bringup",
-      "forks": 1,
-      "size_kb": 430923,
-      "language_breakdown": "C 46%, C++ 38%, Python 7%, Shell 3%",
-      "topics": [],
-      "build_system": "PlatformIO — [env:papermono] and [env:papermono-gh_release]",
-      "upstream_description": "CrossPlay no M5Stack Paper Mono: bring-up a partir de ma-r-s/crossplay",
-      "notes": "The platformio.ini comment states the render stack is required: 'Without it this env [crashes]'. Default branch IS papermono-bringup. Created and pushed the same day it was found — a moving target. Nobody has reported it running on hardware.",
-      "commit_date": "2026-09-11",
-      "commit_subject": "Point the update check at this fork's releases",
-      "analysed_at_commit": "8dc6bf2048bf7cc2d1811ec156547c5596f0604b",
-      "analysed_at_note": "same as current HEAD at time of retrieval",
-      "prior_refs": [
-        {
-          "commit": "8dc6bf2048bf7cc2d1811ec156547c5596f0604b",
-          "date": "2026-09-11",
-          "subject": "Point the update check at this fork's releases",
-          "provenance": "handoff 04-corrections-needed.md C4, 2026-09-11",
-          "resolves": true,
-          "verified": "2026-09-11",
-          "url": "https://github.com/fperuzzo72/crossplay-papermono/tree/8dc6bf2048bf7cc2d1811ec156547c5596f0604b"
-        }
-      ],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    },
-    {
-      "id": "EX48",
-      "title": "m5-touch-card",
-      "author": "Corvelis",
-      "class": "A",
-      "class_meaning": "active third-party project targeting PaperMono",
-      "source_class": "community",
-      "canonical_url": "https://github.com/Corvelis/m5-touch-card",
-      "immutable_url": "https://github.com/Corvelis/m5-touch-card/tree/fc20a442858e5fb74ac940e039230e96317cc11f",
-      "commit": "fc20a442858e5fb74ac940e039230e96317cc11f",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-08",
-      "created": "2026-09-07",
-      "release_tag": "untagged-bf0c3d10730b0cdac435",
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 0,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "NFC business-card exchange between PaperMono and StackChan, with a Flutter smartphone editor app (Dart 22%, Swift 5%). Demo videos recorded on real hardware, uncut and at original speed.",
-      "selected": true,
-      "selection_reason": "NFC exchange demonstrated on hardware; one of three independent Japanese name-badge projects",
-      "default_branch": "main",
-      "forks": 0,
-      "size_kb": 28340,
-      "language_breakdown": "C++ 55%, Dart 22%, Python 9%, Swift 5%",
-      "topics": [
-        "e-paper",
-        "esp32-s3",
-        "flutter",
-        "m5stack",
-        "nfc",
-        "papermono",
-        "stackchan"
-      ],
-      "build_system": "CMake (ESP-IDF) + Flutter companion app",
-      "upstream_description": "PaperMonoとｽﾀｯｸﾁｬﾝで、タッチして名刺交換。NFC対応ファームウェアとスマホ編集アプリ。",
-      "notes": "Ships protocol/specification.md, SECURITY.md and distribution-review.en.md. Provides relinking instructions — consistent with an LGPL §6 obligation, though the README never names LGPL and THIRD_PARTY_NOTICES was not read. Reports the idle CPU entering light sleep, which is the counter-example to paper_name_plate's esp-hal light-sleep report.",
-      "commit_date": "2026-09-08",
-      "commit_subject": "Trim README notices and remove contribution section",
-      "analysed_at_commit": "fc20a442858e5fb74ac940e039230e96317cc11f",
-      "analysed_at_note": "same as current HEAD at time of retrieval",
-      "prior_refs": [
-        {
-          "commit": "fc20a442858e5fb74ac940e039230e96317cc11f",
-          "date": "2026-09-08",
-          "subject": "Trim README notices",
-          "provenance": "handoff 03/08, 2026-09-11",
-          "resolves": true,
-          "verified": "2026-09-11",
-          "url": "https://github.com/Corvelis/m5-touch-card/tree/fc20a442858e5fb74ac940e039230e96317cc11f"
-        }
-      ],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    },
-    {
-      "id": "EX49",
-      "title": "Nostos",
-      "author": "osprey74",
-      "class": "A",
-      "class_meaning": "active third-party project targeting PaperMono",
-      "source_class": "community",
-      "canonical_url": "https://github.com/osprey74/Nostos",
-      "immutable_url": "https://github.com/osprey74/Nostos/tree/13c6b20a5097fb720079401196cc7a949f7f22a7",
-      "commit": "13c6b20a5097fb720079401196cc7a949f7f22a7",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-18",
-      "created": "2026-09-10",
-      "release_tag": null,
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 0,
-      "language": "Rust",
-      "is_fork": false,
-      "archived": false,
-      "license": "NOASSERTION",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11; NOASSERTION = no licence file present, all rights reserved by default",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "Offline breadcrumb / return-navigation device. Receives and decodes Meshtastic LoRa traffic — on-air header parse, AES-CTR decrypt, Position protobuf decode — and renders on e-ink. A custom receiver, not a Meshtastic firmware port.",
-      "selected": true,
-      "selection_reason": "Only known Meshtastic reception on this board; independent radio and LED corroboration",
-      "default_branch": "main",
-      "forks": 0,
-      "size_kb": 510,
-      "language_breakdown": "Rust 84%, C++ 12%, Python 2%",
-      "topics": [],
-      "build_system": "Cargo workspace (crates/nostos-meshtastic, firmware/nostos-fw)",
-      "upstream_description": "Offline breadcrumb/return-navigation on M5Stack PaperMono (Meshtastic RX + e-ink). Ecosystem peer of cardputer",
-      "notes": "Radio config differs from the vendor demo in every parameter: 923.000 MHz / BW 125 kHz / SF9 / CR 4-5 / sync 0x3A vs factory 868.0 / 62.5 / SF12 / 4-8 / 0x34 — an independent cross-check that the documented bring-up is not vendor folklore. Its led.rs comment independently confirms the RGB LED is three discrete lines and explicitly not WS2812. No licence file.",
-      "commit_date": "2026-09-18",
-      "commit_subject": "feat(nostos-fw): 設定タブに「記録」行 + csv2gpx.py",
-      "analysed_at_commit": "56acd5eb1718",
-      "analysed_at_note": "⚠ documentation claims in this knowledge base were read at this earlier ref, NOT at `commit` — the repo moved afterwards",
-      "prior_refs": [
-        {
-          "commit": "56acd5eb1718",
-          "date": "2026-09-13",
-          "subject": "fix(nostos-fw): パネル初期化を工場相当に強化・コールドブート固着",
-          "provenance": "this project 2026-09-11; the Meshtastic radio config and LED corroboration in features/lora.md and buttons-and-rgb-led.md were read at this ref",
-          "resolves": true,
-          "verified": "2026-09-11",
-          "url": "https://github.com/osprey74/Nostos/tree/56acd5eb1718"
-        }
-      ],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    },
-    {
-      "id": "EX50",
-      "title": "CardCase-For-M5Paper",
-      "author": "mitsuharu",
-      "class": "A",
-      "class_meaning": "active third-party project targeting PaperMono",
-      "source_class": "community",
-      "canonical_url": "https://github.com/mitsuharu/CardCase-For-M5Paper",
-      "immutable_url": "https://github.com/mitsuharu/CardCase-For-M5Paper/tree/8feef619d15a248a1249ca35db6497aabf407e6e",
-      "commit": "8feef619d15a248a1249ca35db6497aabf407e6e",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-07",
-      "created": "2025-03-28",
-      "release_tag": "0.1.0",
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 1,
-      "language": "C++",
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "Displays SD-card images on M5Stack e-paper devices and receives images over WiFi and NFC. The only project found supporting four M5Paper generations from one codebase — v1.1, S3, Color and Mono — each with its own PlatformIO env.",
-      "selected": true,
-      "selection_reason": "Broadest device coverage of any third-party project; MIT; only found via Japanese sources",
-      "default_branch": "main",
-      "forks": 0,
-      "size_kb": 2932,
-      "language_breakdown": "C++ 59%, TypeScript 35%, C 2%",
-      "topics": [],
-      "build_system": "PlatformIO — [env:M5Paper] [env:M5PaperS3] [env:M5PaperColor] [env:M5PaperMono] [env:native]",
-      "upstream_description": "M5Stack の電子ペーパー端末を対象に SD カードに保存した画像を選択表示する。さらに WiFi や NFC から受信した画像も表示する。",
-      "notes": "Predates the PaperMono (created 2025-03-28) and was extended to it rather than started fresh. Carries a [env:native] host-test environment and a TypeScript web component (35%) with a GitHub Pages site. Found only via Japanese-language search (Qiita); invisible to every English sweep.",
-      "commit_date": "2026-09-07",
-      "commit_subject": "Merge pull request #34 from mitsuharu/feature/card-layout",
-      "analysed_at_commit": "8feef619d15a248a1249ca35db6497aabf407e6e",
-      "analysed_at_note": "same as current HEAD at time of retrieval",
-      "prior_refs": [],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    },
-    {
-      "id": "EX51",
-      "title": "M5PaperMonoLite",
-      "author": "CitizenRacer",
-      "class": "P",
-      "class_meaning": "proposed or explicitly untested PaperMono support",
-      "source_class": "community",
-      "canonical_url": "https://github.com/CitizenRacer/M5PaperMonoLite",
-      "immutable_url": "https://github.com/CitizenRacer/M5PaperMonoLite/tree/dd97e9104806d48f5cb3d15f2bf9661523a04ac4",
-      "commit": "dd97e9104806d48f5cb3d15f2bf9661523a04ac4",
-      "default_branch": "main",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-04",
-      "created": null,
-      "release_tag": null,
-      "_note_release_tag": "collected 2026-09-11 via GitHub releases API",
-      "stars": 0,
-      "forks": 0,
-      "size_kb": 23,
-      "language": "C++",
-      "language_breakdown": "C++ 67%, Python 32%",
-      "topics": [],
-      "is_fork": false,
-      "archived": false,
-      "license": "MIT",
-      "license_evidence": "GitHub API license.spdx_id, 2026-09-11",
-      "build_system": "ESPHome external component (Python + C++)",
-      "upstream_description": "An attempt at esphome support for the M5PaperMonoLite. NB: I have no idea what I'm doing.",
-      "device_target": "m5stack-papermono",
-      "build_status": "not-attempted",
-      "run_status": "not-attempted",
-      "test_environment": "none — no PaperMono hardware in this project",
-      "evidence_status": "metadata and build config verified via GitHub API 2026-09-11; source read only where cited in the device record; never built, flashed or run",
-      "description": "ESPHome external-component support for the M5PaperMono **Lite** variant — the SKU that ships without LoRa and without NFC.",
-      "notes": "Author's own description: 'NB: I have no idea what I'm doing.' Tiny (23 KB). Targets the Lite specifically, which distinguishes it from hectorzin's ESPHome work on the full C153. Treat as exploratory.",
-      "selected": true,
-      "selection_reason": "Only project targeting the Lite variant specifically; author flags it as exploratory",
-      "commit_date": "2026-09-04",
-      "commit_subject": "Load split_buffer for PaperMono display",
-      "analysed_at_commit": "dd97e9104806d48f5cb3d15f2bf9661523a04ac4",
-      "analysed_at_note": "same as current HEAD at time of retrieval",
-      "prior_refs": [
-        {
-          "commit": "dd97e9104806d48f5cb3d15f2bf9661523a04ac4",
-          "date": "2026-09-04",
-          "subject": "Load split_buffer for PaperMono display",
-          "provenance": "handoff 04-corrections-needed.md pin list, 2026-09-11 — owner was unresolved there, identified as CitizenRacer via GitHub search",
-          "resolves": true,
-          "verified": "2026-09-11",
-          "url": "https://github.com/CitizenRacer/M5PaperMonoLite/tree/dd97e9104806d48f5cb3d15f2bf9661523a04ac4"
-        }
-      ],
-      "_note_prior_refs": "Superseded pins are retained deliberately. All were confirmed to still resolve on GitHub 2026-09-11. If the repository is deleted, renamed or force-pushed, these are the refs to search for in forks or archives."
-    }
-  ],
-  "selected_count": 10
-}
diff --git a/devices/m5stack/papermono/examples/search-log.md b/devices/m5stack/papermono/examples/search-log.md
deleted file mode 100644
index 3ef3442..0000000
--- a/devices/m5stack/papermono/examples/search-log.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# PaperMono — example and project search log
-
-> Search cutoff **2026-09-01**. The device shipped 2026-08-21, so the entire
-> population is at most eleven days old.
->
-> Most rows below are **consolidated from the earlier discovery passes** recorded
-> in [`../research-log.md`](../research-log.md) and
-> [`../projects-and-community.md`](../projects-and-community.md), rather than
-> re-run. Rows marked **[new]** were executed during this cataloguing pass on
-> 2026-09-01. The distinction matters: consolidated rows inherit their original
-> retrieval dates and any staleness that came with them.
-
-## Newly executed in this pass
-
-| # | Service | Query / endpoint | Depth | Disposition |
-|---|---|---|---|---|
-| N1 | GitHub REST API **[new]** | `GET /repos/{owner}/{repo}` for all 43 repositories named in `projects-and-community.md` | 43/43 | **useful** — identity, licence, stars, dates |
-| N2 | GitHub REST API **[new]** | `GET /repos/{owner}/{repo}/commits?per_page=1` for the same 43 | 43/43 | **useful** — HEAD SHA for every entry |
-
-**Result: 43 of 43 repositories resolved. None gone, none private, none
-archived.** This closes a recorded defect of the previous pass, which cited
-third-party repositories without pinning any commit.
-
-Authentication was required: `api.github.com` limits to 60 requests/hour
-unauthenticated, and 86 calls were needed. `gh auth token` raises this to 5,000.
-A first serial attempt was abandoned as too slow and replaced with a 16-way
-parallel pass.
-
-## Consolidated from earlier passes
-
-| # | Service | Query | Depth | Disposition |
-|---|---|---|---|---|
-| C1 | GitHub repo search | `papermono`, `paper mono`, `PaperMono`, `C153`, `M5PaperMono` | multiple pages | useful — core population |
-| C2 | GitHub code search | `board_M5PaperMono`, `m5stack_papermono`, `DEPG0397BBS770F3` | full | useful — found upstreams shipping support |
-| C3 | GitHub org listing | `m5stack`, `crosspoint-reader`, `Free-Ink` | full | useful |
-| C4 | M5Burner API | `burner.m5stack.com/api/v1/firmwares/...` | 4 PaperMono entries | useful — two binaries retrieved and validated |
-| C5 | Reddit | `old.reddit.com/search.json` (UA `WhatsApp/2.23.20.0`) — `papermono` **and** `paper mono` | site-wide + r/esp32, r/eink | thin — two results, both bot mirrors of one HN post |
-| C6 | Hacker News | `hn.algolia.com/api/v1/search?query=papermono` | full | one post |
-| C7 | Mojeek | `M5Stack PaperMono` and variants | 5 pages | useful — surfaced LinuxGizmos, Liliputing, MuyLinux |
-| C8 | YouTube | `M5Stack PaperMono` | first pages | one hands-on video (Volos Projects, 2026-08-29) |
-| C9 | Hackaday `wp-json` | `papermono` | full | **dead** — `[]`, Hackaday published nothing |
-| C10 | `community.m5stack.com` | search | — | **inaccessible** — 401, auth-walled |
-| C11 | hackster.io | various | — | **inaccessible** — no working retrieval path found |
-| C12 | DuckDuckGo / Marginalia | `papermono` | — | **rejected** — 202 anomaly / bot-wait |
-
-## Known exclusions
-
-- **GitLab, Codeberg, SourceHut and Gitea instances were not searched.** Recorded
-  as a gap, not as absence of evidence.
-- **Discord** (M5Stack and e-ink community servers) was not searched — not
-  publicly indexable without joining.
-- **Chinese-language platforms** (Gitee, Bilibili, CSDN) were not searched. Given
-  M5Stack is a Shenzhen company with a large domestic community, this is the most
-  likely place for uncatalogued work, and is the single biggest known hole.
-- Release tags were **not** collected per repository; only HEAD commits. Recorded
-  as `null` with a note in every catalogue entry.
-
-## Stopping criterion
-
-Discovery stopped when two consecutive broad passes returned only duplicates of
-the already-catalogued population and vendor marketing copy. The binding
-constraint is the world, not the search: eleven days after launch there were zero
-written independent reviews and one video.
-
-This is a **reproducible broad-coverage snapshot dated 2026-09-01**, not a claim
-that no other project exists. The exclusions above — particularly the
-Chinese-language platforms — are the places to look first in a later pass.
-
-## Cross-references
-
-- [`catalog.json`](catalog.json) — all 43 entries with pinned commits
-- [`best.md`](best.md) — the selected portfolio and why
-- [`../projects-and-community.md`](../projects-and-community.md) — the prose analysis and classification
-- [`../coverage.md`](../coverage.md) — feature-to-evidence map
diff --git a/devices/m5stack/papermono/factory-firmware.md b/devices/m5stack/papermono/factory-firmware.md
deleted file mode 100644
index 0289ed7..0000000
--- a/devices/m5stack/papermono/factory-firmware.md
+++ /dev/null
@@ -1,471 +0,0 @@
-# Factory firmware — M5Stack PaperMono
-
-> Two whole-flash ESP32-S3 images for SKU **C153 / C153-LITE**, retrieved from the M5Burner
-> public API on **2026-09-01** and retained in [`artifacts/firmware/`](artifacts/firmware/).
-> Both were validated by content (`0xE9` ESP32 image magic), parsed, and mined for strings
-> **before** anything was written here.
->
-> ## ⚠ Nothing was flashed, and nothing was run
->
-> Every parse on this page is `executed-success` **as static analysis of a file on disk**
-> ([`commands.md` §5](commands.md#5-firmware-image-inspection)). Every statement about what the
-> device *does* when these bytes run is `inferred` from strings and source, never observed.
-> No serial port was opened in this session; `esptool` was never invoked.
-
-## Contents
-
-- [1. Both images at a glance](#1-both-images-at-a-glance)
-- [2. The official image — `C153-PaperMono-UserDemo-v1.2.bin`](#2-the-official-image--c153-papermono-userdemo-v12bin)
-- [3. The community image — `crosspoint-paper-mono-cjk-1.5.0-RC.bin`](#3-the-community-image--crosspoint-paper-mono-cjk-150-rc)
-- [4. Partition maps — three different layouts are in evidence](#4-partition-maps--three-different-layouts-are-in-evidence)
-- [5. What the device does on power-up](#5-what-the-device-does-on-power-up)
-- [6. Why `c78f6c5-dirty` means not reproducible](#6-why-c78f6c5-dirty-means-not-reproducible)
-- [7. Flashing and recovery — authoritative versus inferred](#7-flashing-and-recovery--authoritative-versus-inferred)
-- [8. Provenance, distribution and licensing](#8-provenance-distribution-and-licensing)
-- [9. Open questions](#9-open-questions)
-
----
-
-## 1. Both images at a glance
-
-The fields the method requires to be prominent, for both images:
-
-| Field | `C153-PaperMono-UserDemo-v1.2.bin` | `crosspoint-paper-mono-cjk-1.5.0-RC.bin` |
-|---|---|---|
-| **Target MCU** | **ESP32-S3** (`chip_id 9`), `min_rev 0` | **ESP32-S3** (`chip_id 9`), `min_rev 0` |
-| **Compatible hardware** | **C153 and C153-LITE** — one image serves both; the variant is detected at runtime | PaperMono (M5Burner lists `deviceName: Paper`) |
-| **Image role** | **Merged whole-flash image**: second-stage bootloader + partition table + application in one file | **Merged whole-flash image**, same structure |
-| **Expected flash offset** | **`0x0`** | **`0x0`** |
-| **Companion images required** | **None.** Bootloader and partition table are inside the file | **None** |
-| **Version identifier** | app version **`c78f6c5-dirty`**, M5Burner version **v1.2** | app version **`paper-mono-v2-15-g87a191f`**, M5Burner version **1.5.0-RC** |
-| **Build date** | **2026-08-06 16:12:13** | **2026-08-22 19:58:33** |
-| **SDK / toolchain** | **ESP-IDF v5.5.1** | **ESP-IDF 5.5.2.260206**, built through **PlatformIO** with the arduino-esp32 framework |
-| **Project name** | `PaperMono-UserDemo` | `crosspoint-reader-mono` |
-| **Flash settings in header** | **DIO**, 80 MHz, 16 MB | **DIO**, 80 MHz, 16 MB |
-| **Bootloader entry** | `0x403c8924` | `0x403c88b8` |
-| **App entry** | `0x40375bec` | `0x40375fe0` |
-| **Segments** (bootloader / app) | 3 / 7 | 3 / 7 |
-| **Byte size** | **2 868 208** | **10 319 500** |
-| **SHA-256** | `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa` | `e2dee32b468da1d743b9fe8889eca959f5c0acdbe09c8f4cc3e69c69f8ebe935` |
-| **Class** | primary (vendor, `sourceType: OFFICIAL`) — **S38** | community (`sourceType: COMMUNITY`) — **S39** |
-| **Local path** | [`artifacts/firmware/C153-PaperMono-UserDemo-v1.2.bin`](artifacts/firmware/C153-PaperMono-UserDemo-v1.2.bin) | [`artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin`](artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin) |
-
-**Both hashes were recomputed from the retained files on 2026-09-01 and match the values in
-[`acquisition/manifest.json`](acquisition/manifest.json) and [`sources.md`](sources.md).**
-
-Reading this table practically: the two images are the same *shape* — whole-flash, ESP32-S3,
-DIO/80 MHz/16 MB, three-plus-seven segments — and differ in everything above that line. Anything
-you learn about flashing one applies mechanically to the other. What does **not** transfer is
-the flash *map*: they carve the 16 MB up completely differently (§4), so writing one over the
-other leaves stale partitions from the previous occupant anywhere the new table does not reach.
-
-**Both images report DIO although the vendor's published build config says `qio_opi`.** The
-hardware supports QIO — all four flash data lines are routed and the fitted
-`XM25UH128DHIQT`'s `QE` bit is factory-set — and `sdkconfig.defaults` pins no flash mode, so
-DIO is an ESP-IDF default rather than a hardware limit. Not a defect; resolved as
-[R2](gaps-and-conflicts.md#r2--qio-versus-dio-flash--resolved).
-
-## 2. The official image — `C153-PaperMono-UserDemo-v1.2.bin`
-
-### 2.1 Headers, as parsed
-
-```
--- bootloader image header @0x0 --
-  magic 0xe9  segments 3  flash_mode DIO  flash_size 16MB  flash_freq 80MHz
-  entry 0x403c8924  chip_id 9 (ESP32-S3)  min_rev 0
-
--- app image header @0x10000 --
-  magic 0xe9  segments 7  flash_mode DIO  flash_size 16MB  flash_freq 80MHz
-  entry 0x40375bec  chip_id 9 (ESP32-S3)  min_rev 0
-
--- esp_app_desc_t @0x10020 --
-  project_name  PaperMono-UserDemo
-  app_version   c78f6c5-dirty
-  build_time    16:12:13
-  build_date    Aug  6 2026
-  idf_version   v5.5.1
-```
-
-`min_rev 0` means the image declares no minimum silicon revision, so it will load on any
-ESP32-S3 stepping. That is the permissive default and carries no information about which
-stepping the board actually carries — the package marking is not published and no unit was in
-hand.
-
-### 2.2 M5Burner catalogue metadata
-
-From the public API (S33, S34 — `/api/v1/firmwares/{id}` is open, while `/api/firmwares/{id}`
-returns `401 请先登录`):
-
-| Field | Value |
-|---|---|
-| `firmwareId` | `2089640807996628993` |
-| `firmwareName` | **"PaperMono UserDemo"** |
-| `firmwareDescription` | **"PaperMono / PaperMono-Lite UserDemo"** |
-| `sourceType` | `OFFICIAL`; developer `m5stack`, `userId 1` |
-| `sourceUrl` | `null` |
-| Categories | "Development & Learning", "E-books & Reading" |
-| `uploadedAt` / `publishTime` | **2026-08-18T17:09:29+08:00** |
-| `versionName` | **v1.2** |
-| `binFileName` | `C153-PaperMono-ESP32S3R8-UserDemo-V1.2-yaozhenquan-8300e309-20260806_0x00.bin` |
-| `deviceName` | `Paper` |
-| `downloadCount` | **16** (point-in-time, 2026-09-01) |
-
-Three things fall straight out of this record.
-
-**The description is the proof that one image serves both SKUs.** *"PaperMono / PaperMono-Lite
-UserDemo"* — and the EasyLoader executable both product pages link (S40) lives under
-PaperMono's asset folder `1267/`, not the Lite's `1268/`. That is why the firmware performs
-runtime variant detection (§5).
-
-**The catalogue's `binFileName` is not the name of the object served, and it embeds a
-*different* build identifier.** The served object is `…/bin/2089640808000823299.bin`; the
-catalogue name encodes a developer (`yaozhenquan`), a build id **`8300e309`** and the date
-`20260806`. But `esp_app_desc_t` inside those same bytes says **`c78f6c5-dirty`**. Two
-identifiers, same artifact, and they do not agree — recorded as an open question in §9 rather
-than resolved by picking one.
-
-**The `_0x00` suffix is the vendor's own statement of the flash offset**, and it corroborates
-the parse: this is a whole-flash image written at `0x0`.
-
-### 2.3 Notable strings, and what they establish
-
-Extracted with `strings -n 6` — 8 192 lines, working copy at
-`scratch/m5stack-papermono/docs/firmware/C153-PaperMono-UserDemo-v1.2.strings.txt`
-(regenerable from the retained `.bin` by [`commands.md` §5](commands.md#5-firmware-image-inspection)).
-These are the rows that establish something the vendor's prose does not.
-
-| String | What it establishes |
-|---|---|
-| `I (%lu) %s: [Autodetect] board_M5PaperMono` | The board enum the Arduino board name maps to — independent corroboration of the target in [`development.md` §2](development.md#2-board-target-and-profile) |
-| `[I][%s] M5PM1 initialized at address 0x%02X (I2C: %lu Hz)` | The M5PM1 address and bus clock are read from the device at runtime, not hard-coded in prose |
-| `[I][%s] M5IOE1 initialized at address 0x%02X (I2C: %lu Hz)` | Same for the expander |
-| `PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge` | **M5PM1 G4 = IMU wake, and it is falling-edge.** The vendor's prose says the IMU interrupt is active-high; the code and this binary both say active-low ([R3](gaps-and-conflicts.md#r3--bmi270-interrupt-polarity--resolved-against-the-vendor-prose)) |
-| `PM1 shutdown, wake by RX8130 timer -> PM1 G0 falling edge` | **M5PM1 G0 = RTC wake.** Also that these are *M5PM1* pins, not expander pins |
-| `ESP32 deep sleep, wake by touch INT GPIO%d low` | Touch wake is an **ESP32-S3 EXT0** wake, i.e. a different mechanism from the two M5PM1 wakes |
-| `IMU wake line still active, shutdown canceled` · `RTC wake line still active, shutdown canceled` | The firmware **refuses to shut down while a wake line is asserted** — a real design decision that prevents an immediate self-wake |
-| `W (%lu) %s: M5PM1/M5IOE1 init failed; RGB/NFC/TF controls are disabled` | Confirms the architectural claim: without the two auxiliary MCUs you lose LED, NFC and card control |
-| `I (%lu) %s: NFC identity probe: ok=%d identity=0x%02X type=0x%02X rev=0x%02X` | The runtime SKU probe (§5) |
-| `I (%lu) %s: Board variant detected: %s` | …and that its result is logged |
-| `Found %luMB PSRAM device` · `SPI SRAM memory test OK` | PSRAM is brought up and **tested** at boot |
-| `/sdcard`, `NO FOUND` / `CARD FOUND` / `DET READ FAIL` | The microSD mount point and the card-detect state machine's three outcomes |
-| `time.google.com`, `time.nist.gov`, `pool.ntp.org` | The three NTP servers the clock app tries |
-| `QWERTYUIOP` / `asdfghjkl` / `@#$&*()'"` | There is an **on-screen keyboard** — for SSID and password entry |
-| `FeliCa Lite-S`, `FeliCa Lite`, `Tag-it HF-I Pro` | Tag-type names the NFC app can print. **Evidence of intent, not of interoperability** — no card has been read on a real board by anyone |
-| `AppBattery` `AppBrightness` `AppBuzzer` `AppClock` `AppImu` `AppLora` `AppMicWave` `AppNfcScan` `AppRgb` `AppShutdown` `AppSleepWake` `AppTfCard` `AppWifiScan` | The thirteen application symbols that survive in the binary |
-
-On that last row: the source analysis of `M5PaperMono-UserDemo/main/apps/` records **fifteen**
-application directories, including a keyboard app. Only thirteen `App…` class-name strings
-survive in the shipped binary — the keyboard, for instance, is visible only through its layout
-strings. **Do not read "thirteen" as a count of features**; it is a count of symbols that
-happened to survive compilation. `inferred`.
-
-### 2.4 The build environment left no developer path in the binary
-
-Every IDF source path in the official image is stripped to a `//IDF/components/…` prefix — for
-example `//IDF/components/esp_psram/system_layer/esp_psram.c`. No home directory, no user name,
-no absolute build path appears anywhere. Contrast §3.3, where the community image leaks its
-builder's home directory in full. Recorded because it is the kind of detail that identifies a
-build system, and because it is the *only* thing in the official binary that resembles build
-provenance beyond `esp_app_desc_t`.
-
-## 3. The community image — `crosspoint-paper-mono-cjk-1.5.0-RC`
-
-Retained because it is **not vendor firmware and is not reproducible**, and because it is the
-only independent binary evidence that units actually shipped and ran third-party code.
-
-### 3.1 Headers, as parsed
-
-```
--- bootloader image header @0x0 --
-  magic 0xe9  segments 3  flash_mode DIO  flash_size 16MB  flash_freq 80MHz
-  entry 0x403c88b8  chip_id 9 (ESP32-S3)  min_rev 0
-
--- app image header @0x10000 --
-  magic 0xe9  segments 7  flash_mode DIO  flash_size 16MB  flash_freq 80MHz
-  entry 0x40375fe0  chip_id 9 (ESP32-S3)  min_rev 0
-
--- esp_app_desc_t @0x10020 --
-  project_name  crosspoint-reader-mono
-  app_version   paper-mono-v2-15-g87a191f
-  build_time    19:58:33
-  build_date    Aug 22 2026
-  idf_version   5.5.2.260206
-```
-
-**`paper-mono-v2-15-g87a191f` is a `git describe` string**, and it is the interesting contrast
-with the official image: it names tag `paper-mono-v2`, **15** commits of distance, and commit
-**`87a191f`**. That is enough to identify a source revision. The official image's
-`c78f6c5-dirty` is not (§6). The community build is, on this narrow measure, better documented
-than the vendor build.
-
-### 3.2 M5Burner catalogue metadata
-
-| Field | Value |
-|---|---|
-| `firmwareId` | `2091144466157694978` |
-| `firmwareName` | **"CrossPoint-PaperMono-CJK"** |
-| `sourceType` | `COMMUNITY`; developer **`IAMLIUBO`**, `userId 3966`, website `https://github.com/imliubo` |
-| `sourceUrl` | `https://github.com/MarsTechHAN/crosspoint-reader-mono` |
-| `uploadedAt` | **2026-08-22T20:44:29+08:00** — one day after launch |
-| `versionName` | **1.5.0-RC**; description 「针对PaperMono做了CJK的优化, 与官方版本有所不同」 ("CJK optimisation for PaperMono; differs from the official version") |
-| `binFileName` | `crosspoint-paper-mono-full-with-cjk.bin` |
-| `downloadCount` | **24** (point-in-time, 2026-09-01) |
-
-**The uploader and the upstream author are different people.** `sourceUrl` points at
-`MarsTechHAN/crosspoint-reader-mono` while the uploading account is `IAMLIUBO`. Do not read a
-M5Burner `sourceUrl` as the identity of the person who built the bytes.
-
-**The community image had been downloaded more times than the official one** — 24 against 16,
-as counted on 2026-09-01. Both counters are tiny and point-in-time, so this establishes almost
-nothing about popularity; it is recorded because it is a *measured* number in a record that has
-very few of them, and because it is consistent with the community's interest in this board
-being reader-shaped rather than dev-board-shaped.
-
-### 3.3 Notable strings
-
-| String | What it establishes |
-|---|---|
-| `/Users/imliubo/.platformio/packages/framework-arduinoespressif32/libraries/Wire/src/Wire.cpp` (and `SPI`, `WiFi`, `Network…`) | **Built with PlatformIO and the arduino-esp32 framework, on macOS, by `imliubo`** — which independently corroborates the M5Burner developer record's `github.com/imliubo` website field. Two unrelated surfaces, same identity |
-| `CrossPoint version: 1.5.0-paper-mono` | The application's own version string, matching the catalogue |
-| `cjkfont`, `Built-in CJK font partition not found`, `Could not mmap %u-byte CJK font` | The 4 MB `cjkfont` partition is **memory-mapped**, not read through a filesystem |
-| `stbtt__GetGlyphShapeTT`, `stbtt_FindGlyphIndex` | Font rasterisation is `stb_truetype` |
-| `/.crosspoint/settings.json`, `/opds.json`, `/recent.json`, `/wifi.json`, `/koreader.json` | It keeps its state in a `.crosspoint` directory **on the microSD card**, and it interoperates with **KOReader** progress data and **OPDS** catalogues |
-| `/.fonts`, `.cpfont`, `/.cover.jpg`, `/.cover.png` | User fonts and book covers are read from the card too |
-| `OTA app partition slot`, `ota data partition invalid, falling back to factory` | These are stock IDF bootloader strings and are present in **both** images. **They do not mean OTA is configured** — the partition table is what decides that, and neither image has an `otadata` partition (§4) |
-
-That last row is worth stating plainly because it is an easy misreading: finding OTA strings in
-a binary tells you the bootloader was compiled with OTA support, which it always is. It says
-nothing about whether the flash map has anywhere to put a second app.
-
-## 4. Partition maps — three different layouts are in evidence
-
-### 4.1 The shipped official layout (= both vendor projects' `partitions.csv`)
-
-| Name | Type | SubType | Offset | Size | |
-|---|---|---|---:|---:|---|
-| `nvs` | data (1) | `0x02` nvs | `0x009000` | `0x006000` | 24 K |
-| `phy_init` | data (1) | `0x01` phy | `0x00F000` | `0x001000` | 4 K |
-| `factory` | app (0) | `0x00` factory | `0x010000` | `0xF00000` | **15 360 K** |
-
-~960 K of the 16 MB device is left unallocated above the app. **No OTA slot, no `otadata`, no
-SPIFFS/FAT partition, no coredump partition.** `M5PaperMono-UserDemo/partitions.csv` and
-`M5PaperMono-OTP-Demo/partitions.csv` are the same three lines, and the shipped binary's table
-matches them exactly — so the published source and the shipped bytes agree about the flash map
-even though they disagree about the application (§6).
-
-### 4.2 The community CrossPoint layout
-
-| Name | Type | SubType | Offset | Size | |
-|---|---|---|---:|---:|---|
-| `nvs` | data (1) | `0x02` nvs | `0x009000` | `0x005000` | 20 K |
-| `app0` | app (0) | `0x00` factory | `0x010000` | `0x640000` | 6 400 K |
-| `cjkfont` | data (1) | `0x40` *(custom)* | `0x650000` | `0x400000` | 4 096 K |
-| `spiffs` | data (1) | `0x82` spiffs | `0xC90000` | `0x360000` | 3 456 K |
-| `coredump` | data (1) | `0x03` coredump | `0xFF0000` | `0x010000` | 64 K |
-
-Note `app0` carries subtype `0x00` — it is a **factory** app under an OTA-style name, and there
-is no `otadata`, so this image has no OTA path either despite the naming.
-
-**These offsets are not arbitrary.** `app0` at `0x10000` sized `0x640000`, the next partition
-starting at `0x650000`, `spiffs` at `0xC90000` and `coredump` at `0xFF0000` are exactly the
-arrangement of arduino-esp32's stock `default_16MB.csv`, with the **`app1` OTA slot repurposed
-as the 4 MB `cjkfont` partition** and `otadata` dropped. Combined with the PlatformIO build
-paths in §3.3, the reading is that CrossPoint started from the Arduino default 16 MB scheme and
-edited it. **`inferred` from offsets and sizes — no copy of `default_16MB.csv` was retrieved in
-this pass to diff against.**
-
-### 4.3 The layout the vendor's own build block would give you
-
-The published PlatformIO block sets `board_build.partitions = default_16MB.csv` — that same
-Arduino default scheme, which is **not** the three-entry layout the product actually ships. So
-the vendor's build instructions and the vendor's product disagree about the flash map.
-
-Practical consequences, in order of how much they will cost you:
-
-- **Building from the vendor's PlatformIO block does not reproduce the shipped geometry.** You
-  get a smaller app slot, an unused second app slot and a SPIFFS partition the product does not
-  have.
-- **Writing one whole-flash image over another leaves debris.** Flashing CrossPoint over the
-  official image and back again does not clear regions the new table does not describe;
-  `nvs` in particular starts at the same offset in all three layouts but is 24 K in one and
-  20 K in another.
-- **If you intend to ship, pick the map first.** With no OTA slot, changing it later means
-  physically reflashing every unit — see
-  [`development.md` §8.4](development.md#84-there-is-no-ota-partition).
-
-## 5. What the device does on power-up
-
-Reconstructed from the string ordering in the official image and from the HAL source (S41).
-**`inferred` throughout — no boot has been observed.**
-
-1. **Second-stage bootloader** at `0x0` validates and loads the app at `0x10000`.
-2. **PSRAM is found and memory-tested** — `Found %luMB PSRAM device`, `Speed: %dMHz`,
-   `SPI SRAM memory test OK`, then pools are added to the heap allocator. If the build lacks
-   octal PSRAM support the display later refuses to initialise
-   ([`development.md` §8.1](development.md#81-octal-psram-is-mandatory--and-the-failure-looks-like-dead-hardware)).
-3. **`M5.begin()`** runs — `M5.begin start` … `M5.begin done board=%d display_count=%d`. Board
-   autodetection prints `[Autodetect] board_M5PaperMono`. Display init failure is reported
-   distinctly as `count=0` versus a wrong size.
-4. **Peripheral bring-up, with retries** — `Board peripheral init attempt %u/%u`, initialising
-   M5PM1 and M5IOE1 (each with its own failure log), the IMU (`IMU init attempt %u/%u`), and the
-   buzzer. A combined failure degrades gracefully:
-   `M5PM1/M5IOE1 init failed; RGB/NFC/TF controls are disabled`.
-5. **SKU detection** — the NFC rail is powered through M5IOE1 `PYG4` and the ST25R3916's
-   identity register is read (`NFC identity probe: ok=… identity=… type=… rev=…`, expecting
-   `ic_type 0x05`). Failure at either step means `Lite`. The result is logged as
-   `Board variant detected: %s`, with values `Pro` / `Lite` in the source — note the firmware
-   calls the C153 **"Pro"** although the product is just "PaperMono".
-6. **The application launcher** runs the thirteen-plus demo apps listed in §2.3.
-7. **Sleep and shutdown** are guarded: before entering M5PM1 shutdown the firmware verifies the
-   selected wake line is idle and **cancels the shutdown if it is not**, then arms either
-   `PM1 G4` (IMU, falling) or `PM1 G0` (RTC timer, falling). ESP32-S3 deep sleep uses touch
-   `EXT0` on GPIO4 instead.
-
-The load-bearing observation here is step 4: **this firmware is written to survive its own
-auxiliary microcontrollers failing.** That is not defensive boilerplate — the M5PM1 and M5IOE1
-sit between the application processor and most of the board, so a bus problem at boot has to
-degrade rather than hang. It is also an indirect confirmation of how much of the board is behind
-those two chips.
-
-## 6. Why `c78f6c5-dirty` means not reproducible
-
-`esp_app_desc_t.app_version` is populated by ESP-IDF from `git describe` at build time. The
-`-dirty` suffix is `git describe`'s own marker for **"the working tree contained uncommitted
-modifications when this was built"**.
-
-So the official image was built from `c78f6c5` **plus an unknown set of uncommitted edits**.
-The consequences are exact:
-
-- **No commit of `m5stack/M5PaperMono-UserDemo` will regenerate these bytes.** The published
-  HEAD is `c1099107271d31a0678d661a896e2b04dbb331ea` (2026-08-10, "update firmware v1.2") —
-  four days *after* the image's build date of 2026-08-06, and a different object from `c78f6c5`
-  in any case.
-- **The delta is not published and cannot be recovered.** `git describe` records that
-  modifications existed, never what they were.
-- **Byte-for-byte reproduction is impossible even with the right tree**, because ESP-IDF stamps
-  the build time into the image; but that is the *lesser* problem. The substantive problem is
-  that the source state itself is unknown.
-- **Therefore the bytes are the artifact.** This is precisely the case
-  [`SIZE-AUDIT.md`](../../../SIZE-AUDIT.md) describes as irreplaceable: the image is retained in
-  the repository rather than referenced by URL, because a URL to a CDN object is not a
-  recovery plan for something no source tree can rebuild.
-
-**A short digression worth having, because it is a general trap.** `-dirty` here is *not*
-evidence of sloppiness that invalidates the firmware — vendors ship builds from working trees
-routinely and the binary is perfectly valid. What it invalidates is the *audit chain*: you
-cannot diff this image against source, cannot confirm the published repository is what runs on
-the device, and cannot rebuild it to add a fix. If you need a reproducible baseline for this
-board, build from the published HEAD and accept that you are building **something adjacent to**
-the shipped firmware, not the shipped firmware.
-
-By contrast, the community image's `paper-mono-v2-15-g87a191f` carries no `-dirty` marker and
-names a commit. Whether that commit is reachable in the public repository was **not checked**
-in this pass.
-
-## 7. Flashing and recovery — authoritative versus inferred
-
-### 7.1 Authoritative — what M5Stack actually documents
-
-> Use **M5Burner** (or the Windows **EasyLoader** executable `C153-PaperMono-UserDemo_0x00.exe`,
-> S40), select the *PaperMono UserDemo* firmware, put the device in download mode by
-> **holding the power button about 2 seconds until the red LED blinks**, then release and flash.
-
-`reported-working` — transcribed from S01, S04 and S09. **Not executed.** The Arduino
-quick-start page (S07) contradicts the download-mode instruction by referring to "the reset
-button on the side"; there is no reset button on this board, and that page is wrong
-([R4](gaps-and-conflicts.md#r4--download-mode-control--resolved-on-the-balance-of-evidence)).
-
-M5Burner's own device filter lists both images under `deviceName: "Paper"`, the family key
-shared with the rest of M5Stack's Paper line, so **the catalogue will not stop you selecting an
-image meant for a different Paper product.** `inferred` from the API records; `not-tested`.
-
-### 7.2 Inferred — the `esptool` equivalent
-
-**Never executed, on any board.** Written down because the method requires recovery
-instructions to exist rather than be silently omitted, and because the vendor route is
-Windows-GUI-shaped.
-
-```bash
-# INFERRED. NOT VERIFIED. Confirm the port and chip before running anything like this.
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-  write_flash --flash_mode dio --flash_freq 80m --flash_size 16MB \
-  0x0 C153-PaperMono-UserDemo-v1.2.bin
-```
-
-Where each argument comes from:
-
-| Argument | Evidence |
-|---|---|
-| `--chip esp32s3` | `chip_id 9` in both image headers |
-| `0x0` | Bootloader header **is** at offset 0 in the file; the vendor's own object name ends `_0x00.bin` |
-| `--flash_mode dio`, `--flash_freq 80m`, `--flash_size 16MB` | The image's own header fields — self-consistent by construction |
-| `/dev/ttyACM0` | A guess. Native USB CDC enumerates as ACM on Linux; **the device was never enumerated here** |
-| `--baud 921600` | A conventional value. **Not documented by the vendor for this board** |
-
-### 7.3 Verifying what is on a board
-
-`inferred`; not run:
-
-```bash
-esptool.py --chip esp32s3 --port PORT read_flash 0x10020 256 desc.bin   # esp_app_desc_t
-esptool.py --chip esp32s3 --port PORT read_flash 0x8000 0xC00 ptab.bin  # partition table
-```
-
-Parsing either with [`commands.md` §5](commands.md#5-firmware-image-inspection)'s tooling
-identifies the running application and its flash map. Both offsets are established from the
-parses above.
-
-### 7.4 What a reflash does not fix
-
-**The M5PM1 runs its own firmware in its own part** (a `PY32L020F15U6`) and nothing you write
-into the ESP32-S3's flash touches it. It owns `SOC_RESET` and the GPIO0 boot strap. If the
-power manager is misconfigured — for example with its download mode locked through
-`BTN_CFG_1[7] DL_LOCK` — reflashing the application processor is not the recovery path, because
-you cannot get the application processor into download mode in the first place. See
-[`development.md` §8.3](development.md#83-the-m5pm1-owns-reset-and-the-boot-strap--this-is-the-real-bricking-vector).
-
-## 8. Provenance, distribution and licensing
-
-| | Official image | Community image |
-|---|---|---|
-| Retrieved | 2026-09-01T05:05:22Z | 2026-09-01T05:05:25Z |
-| API URL | `burner.m5stack.com/api/v1/firmwares/2089640807996628993/versions/2089640808000823298/download` | `…/2091144466157694978/versions/2091144466157694979/download` |
-| CDN URL (after 302) | `m5burner-cdn.m5stack.com/community/1/2089640807996628993/2089640808000823298/bin/2089640808000823299.bin` | `m5burner-cdn.m5stack.com/community/3966/2091144466157694978/2091144466157694979/bin/2091144466157694980.bin` |
-| HTTP status / content type | 200, `application/macbinary` | 200, `application/macbinary` |
-| Validation | first byte `0xE9` — **ESP32 image**, not an HTML error page | same |
-| Licence | **unknown** — no notice in the image or the API record | **unknown** — the upstream project is open source; the *binary* carries no notice |
-| Redistribution | `unknown` | `unknown` |
-| Disposition | `repository` | `repository` |
-| Reacquisition | `automatic` (two URLs recorded) | `automatic` (two URLs recorded) |
-
-`application/macbinary` is the CDN's content type for an opaque blob and means nothing about the
-file; this is exactly the case where validating by **content** rather than by extension or
-content-type matters, and both files were validated by magic byte before being named.
-
-> **A numbering inconsistency to be aware of.** [`acquisition/manifest.json`](acquisition/manifest.json)
-> refers to these two images as **`S30`** and **`S31`**, whereas [`sources.md`](sources.md) —
-> which is the current, canonical source table — calls them **`S38`** and **`S39`**. The
-> manifest predates the source table's renumbering. **This page uses the `sources.md` IDs.**
-> The hashes, byte sizes and URLs agree in both files, so nothing is ambiguous about *which*
-> artifact is meant.
-
-## 9. Open questions
-
-| # | Question | Why it is open |
-|---|---|---|
-| 1 | **`8300e309` versus `c78f6c5-dirty`** | The M5Burner `binFileName` and the in-image `esp_app_desc_t` carry different build identifiers for the same bytes. Neither is a commit in `M5PaperMono-UserDemo`'s published history that was checked. Possibly a CI build id, possibly a commit in an internal GitLab (both demo repos have squashed histories whose HEAD message is literally `Merge GitLab initial history`) |
-| 2 | **Is `87a191f` reachable publicly?** | The community image names a commit; whether it exists in `MarsTechHAN/crosspoint-reader-mono` was not checked |
-| 3 | **Does the M5Burner record's `nvs` survive a reflash?** | Depends on tool and offsets; not tested |
-| 4 | **What is in the ~960 K unallocated tail** of the official layout? | Nothing in the partition table describes it; the region was not dumped |
-| 5 | **Is there an M5PM1 firmware image anywhere?** | None was located. The power manager's firmware is not distributed through M5Burner and no update artifact for it was found |
-| 6 | **The EasyLoader executable was not retrieved** | A Windows binary was out of scope. The *finding* is that both product pages link the same file from PaperMono's asset folder (S40) |
-
-## Related
-
-- [`development.md`](development.md) — frameworks, versions, build/flash/monitor, bricking risks
-- [`features/usb-and-serial.md`](features/usb-and-serial.md) — ports, download mode, flashing routes
-- [`resources-and-conflicts.md` §5](resources-and-conflicts.md#5-memory-flash-and-partitions) — flash and partition resources
-- [`commands.md` §4](commands.md#4-m5burner-firmware-retrieval) and [§5](commands.md#5-firmware-image-inspection) — how these files were retrieved and parsed
-- [`acquisition/manifest.json`](acquisition/manifest.json) · [`acquisition/README.md`](acquisition/README.md) — machine-readable provenance
-- [`sources.md`](sources.md) — S31–S40 (M5Burner), S41–S42 (vendor source)
-- [`community.md`](community.md) — who built the community image, and what that establishes
diff --git a/devices/m5stack/papermono/features/README.md b/devices/m5stack/papermono/features/README.md
deleted file mode 100644
index 49f0f1d..0000000
--- a/devices/m5stack/papermono/features/README.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# Feature guides — M5Stack PaperMono
-
-Task-oriented guides. Each answers "how do I use X on this board", and states what it
-costs you in pins, bus bandwidth and power, what it collides with, and which of its
-limits are **silicon**, **board**, **framework** or **observed**.
-
-> **Read this first.** There is **no PaperMono in hand**. Nothing in any guide below is
-> `executed-success` on a device. Code sketches derived from M5Stack's own libraries are
-> marked `inferred`; procedures M5Stack publishes as working are marked
-> `reported-working`. No flash sequence, API call or register write here has been
-> verified electrically. Snapshot **2026-09-01**, hardware revision **V0.6.2**.
-
-| Guide | Covers | Headline gotcha |
-|---|---|---|
-| [`epaper-display.md`](epaper-display.md) | SSD1677 + DKE panel, refresh modes, OTP waveforms | **Vendor says its own M5GFX waveforms are unstable**; continuous partial refresh destroys the panel |
-| [`frontlight.md`](frontlight.md) | AW9967 boost, brightness, gamma | Driven from the **M5PM1**, not the expander — and `PYG3` means the other chip |
-| [`touch.md`](touch.md) | FT6336G, coordinates, wake-on-touch | Usable area is **X 5–475, Y 5–795** — a dead border you cannot widen |
-| [`buttons-and-rgb-led.md`](buttons-and-rgb-led.md) | Two user keys, power button, RGB indicator | **Red has no PWM** — the LED is not a full-colour indicator |
-| [`power-and-sleep.md`](power-and-sleep.md) | Five power states, wake sources, shutdown | RTC and IMU interrupts land on the **M5PM1**, not the ESP32-S3 |
-| [`battery-and-charging.md`](battery-and-charging.md) | IP2315, battery ADC, charge state | `0x75` **not appearing in an I²C scan is correct** — the charger is gated off the bus |
-| [`wifi-and-bluetooth.md`](wifi-and-bluetooth.md) | 2.4 GHz Wi-Fi, BLE | Bluetooth is a **silicon** capability M5Stack never specifies |
-| [`lora.md`](lora.md) | Stamp LoRa-1262 / SX1262 via RadioLib | Sub-GHz — it does **not** share the Wi-Fi radio. Regional bands are undocumented |
-| [`nfc.md`](nfc.md) | ST25R3916, ISO14443A/B, FeliCa, ISO15693 | **Not fitted on the Lite**; which card types were actually tested is unknown |
-| [`imu.md`](imu.md) | BMI270, motion wake | Its interrupt goes to the **power manager**, and vendor prose has the polarity wrong |
-| [`rtc.md`](rtc.md) | RX8130CE, alarms, timed wake | Alarm wake works with the ESP32-S3 **unpowered** |
-| [`microsd.md`](microsd.md) | 4-bit SDMMC on GPIO8–13 | Power (IO14) and detect (IO1) are both behind the **expander** |
-| [`microphone.md`](microphone.md) | PDM mic, I²S | On **GPIO45/46 — both strapping pins** |
-| [`buzzer.md`](buzzer.md) | Magnetic buzzer on GPIO42 | LEDC only; there is **no speaker and no amplifier** |
-| [`usb-and-serial.md`](usb-and-serial.md) | USB CDC, UART0, download mode | **No USB-PD.** Download mode is the **power button**, not a reset button |
-| [`io-expander.md`](io-expander.md) | M5IOE1 — the chip everything else goes through | `M5IOE1_PIN_3 = 2`, and `PYG3` denotes two different pins |
-
-## Cross-cutting constraints
-
-Four facts shape every design on this board:
-
-1. **There is no free GPIO and no expansion connector.** No Grove port, no M-Bus, no
-   header. Anything you add shares the single I²C bus or steals an expander pin.
-   See [`../resources-and-conflicts.md`](../resources-and-conflicts.md).
-2. **Two auxiliary microcontrollers sit between the application processor and the
-   board.** Panel power, panel reset, touch power and reset, microSD power and detect,
-   microphone power, NFC enable, LoRa reset and antenna switch, two LED colours and the
-   charger's bus gate are behind the [M5IOE1](io-expander.md); reset, boot mode, rail
-   enables and every deep wake source are behind the
-   [M5PM1](power-and-sleep.md). Neither is optional.
-3. **`PYG<n>` is ambiguous and the ambiguity is dangerous.** Read
-   [`../pin-naming-and-the-pyg-ambiguity.md`](../pin-naming-and-the-pyg-ambiguity.md)
-   before acting on any vendor pin name.
-4. **Octal PSRAM is a hard build requirement.** Without `qio_opi`, M5GFX aborts display
-   init with `"M5PaperMono need OPI-PSRAM enabled"` and you get a blank screen on
-   working hardware.
-
-## Deliberately short guides
-
-Three guides are short because the evidence is thin, and say so rather than padding:
-
-- **UiFlow2 has no guide at all.** M5Stack advertises UiFlow2 support and publishes a
-  page that states no required firmware version, no block list and no limitations. That
-  is a documented gap, confirmed by full-text search, not a retrieval failure. Tracked
-  in [`../coverage.md`](../coverage.md) and `gaps-and-conflicts.md` G4.
-- [`lora.md`](lora.md) — **regional band configuration is undocumented.** One wideband
-  868–923 MHz SKU, no per-region variant, no certification, no module datasheet.
-- [`nfc.md`](nfc.md) — **no evidence exists about which card types were actually
-  tested.** The library exposes four technology layers; nobody has reported results.
-
-## Related
-
-- [`../README.md`](../README.md) — device overview and the "How do I…?" index
-- [`../coverage.md`](../coverage.md) · [`../resources-and-conflicts.md`](../resources-and-conflicts.md) · [`../compatibility-and-status.md`](../compatibility-and-status.md)
-- [`../pinouts-and-buses.md`](../pinouts-and-buses.md) · [`../power-architecture.md`](../power-architecture.md) · [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md)
-- [`vendors/m5stack`](../../../../vendors/m5stack/README.md) — how to find M5Stack documentation
diff --git a/devices/m5stack/papermono/features/battery-and-charging.md b/devices/m5stack/papermono/features/battery-and-charging.md
deleted file mode 100644
index cfde69c..0000000
--- a/devices/m5stack/papermono/features/battery-and-charging.md
+++ /dev/null
@@ -1,263 +0,0 @@
-# Battery and charging — M5Stack PaperMono
-
-> **How do I read the battery, control charging, and why is the charger missing from my
-> I²C scan?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-## 1. Capability summary and the hardware path
-
-A 1150 mAh Li-ion cell with an NTC thermistor, charged from USB-C through an
-over-voltage protector and an I²C-capable charger, with battery voltage read by the
-power-management chip's own ADC.
-
-```
-USB-C ──▶ AW32901FCR (U2, OVP 5.95 V) ──▶ IP2315 charger (U1) ──▶ battery (J2, 1150 mAh + 100K NTC)
-                                              ↕ I²C 0x75
-                                      U3 level translator (VBAT-referenced)
-                                              ↕ OE = PYB_CHG_IIC
-                                          M5IOE1 IO11   ◀── the gate
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Charger | Injoinic **IP2315**, I²C `0x75` | [`components/injoinic/ip2315`](../../../../components/injoinic/ip2315/README.md) |
-| USB input protection | Awinic **AW32901FCR**, `OVP = 5.95 V` | [`components/awinic/aw32901`](../../../../components/awinic/aw32901/README.md) |
-| Bus gate | M5IOE1 `IO11` | [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) · [`io-expander.md`](io-expander.md) |
-| Battery telemetry | M5PM1 `BAT_ADC_EN` / `BAT_ADC_IN`, registers `0x22`/`0x23` | [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) |
-| Cell | 1150 mAh Li-ion at `J2`, `100K-RNTC` thermistor | — |
-
-> **Naming trap.** `VBUS_L0` is **not** USB VBUS. USB 5 V is `VUSB_IN`; `VBUS_L0` is the
-> internal battery/system bus, tied to `VBAT_L0` through a 0 Ω link (`R20`). Reading
-> `VBUS` as "USB power" inverts the entire tree.
-
-## 2. ⚠ The charger is normally *off* the I²C bus — and a scan not finding `0x75` is correct
-
-**This is the board's sharpest design quirk, and M5Stack documents it themselves.**
-
-The IP2315's I²C pins are also its LED driver pins, and I²C mode requires them to be
-pulled to **`VBAT`**, not to the 3.3 V logic rail. The schematic solves this with `U3`, a
-dual-bit bidirectional level translator bridging the system bus (`G47_SYS_SDA` /
-`G48_SYS_SCL`) to a `VBAT`-referenced charger bus (`CHG_SYS_SDA` / `CHG_SYS_SCL`). **Its
-output enable is `PYB_CHG_IIC`, driven by M5IOE1 `IO11`.**
-
-M5Stack's own warning, verbatim from the product page:
-
-> "The I2C operating mode of the charging chip IP2315 depends on the I2C pins being
-> pulled up to VBAT voltage. Connecting the device to USB triggers mode detection; **if
-> the VBAT voltage is too low, the IP2315 may not initialize into I2C mode properly,
-> which can interfere with other devices on the same I2C bus.** M5IOE1 controls the
-> connection between the IP2315 and the system I2C bus via `PYG11_PWM3`: during device
-> operation, **do not keep the IP2315 mounted on the I2C bus for extended periods;
-> disconnect it promptly after communication** to avoid reducing bus communication
-> stability. **If an I2C bus communication anomaly occurs, you can reset the device by
-> briefly pressing the power button** to restore normal bus operation."
-
-So:
-
-- **`0x75` will not appear in an ordinary I²C scan.** That is the intended state, not a
-  fault. Do not "fix" it.
-- The IP2315 datasheet additionally documents a bus-lockup mechanism involving a **missing
-  NACK on the final byte of a read** — presumably the specific failure the gate exists to
-  avoid.
-- **Recovery from a wedged bus is a short press of the power button**, which resets the
-  device via the M5PM1.
-
-> The dedicated Arduino power-management page **never mentions `M5IOE1_PIN_11` at all**.
-> Neither of its two pin tables lists it. A reader working only from that page would not
-> know the gate exists. The hazard note lives only on the product page.
-
-### How M5Unified handles it
-
-`M5Unified/src/utility/Power_Class.cpp:66–96` — the mitigation is structural, not
-advisory:
-
-```cpp
-static void set_papermono_ip2315_enabled(bool enable) {
-  M5.getIOExpander(0).digitalWrite(M5IOE1_Class::gpio11, enable);
-}
-
-static bool wait_papermono_ip2315_ready(void) {
-  m5gfx::delay(2);
-  for (int i = 0; i < 64; ++i) {              // 64 attempts
-    if (M5.In_I2C.scanID(ip2315_i2c_addr, i2c_freq)) { return true; }
-  }
-  return false;
-}
-```
-
-Every charger access is bracketed: gate on → wait for the device to appear → transact →
-gate off. **Callers that talk to the charger without going through this will simply not
-find it.**
-
-## 3. Reading the battery and charge state
-
-### Voltage
-
-The battery voltage does **not** come from the charger. It comes from the M5PM1's ADC:
-
-```cpp
-int16_t mv = M5.Power.getBatteryVoltage();     // what the factory firmware uses
-                                               // hal.cpp:114 -> M5.Power.getBatteryVoltage()
-```
-
-or directly, `pm1.readVbat(uint16_t* mv)` — registers `VBAT_L`/`VBAT_H` (`0x22`/`0x23`),
-in millivolts, the high byte carrying 4 bits. Companion readings: `readVin()`
-(`0x24`/`0x25`), `read5VInOut()` (`0x26`/`0x27`), `readVref()` (`0x20`/`0x21`).
-
-**There is no fuel gauge and no coulomb counter.** The factory firmware derives a
-percentage from a filtered voltage in `app_battery.cpp:155` (`getBatteryPercent`) — a
-lookup on voltage, with all the accuracy that implies under load.
-
-### Charge state
-
-`M5.Power.isCharging()` on this board does something specific and worth reproducing
-(`Power_Class.cpp:2714–2740`):
-
-1. Read the M5PM1 power source. **If neither `vin` nor `vinout` is present, return
-   discharging** without touching the charger at all. (`PWR_SRC` is a bitmap; the battery
-   bit can coexist with VIN.)
-2. Otherwise gate the IP2315 on, wait for it, read register **`0xC7`**, test **bit 7**,
-   gate it off.
-
-M5Stack's own in-code comment records measured values:
-
-```
-// its state in REG_CHG_STAT(0xC7): bit7 = charging in progress (measured:
-// 0x82 charging / 0x45 charge-complete / 0x00 charge-disabled).
-```
-
-That is the closest thing to a hardware-measured fact in the whole software stack — but
-it is **M5Stack's** measurement, `reported-working`, not ours.
-
-### Enabling and disabling charging
-
-`M5.Power.setBatteryCharge(bool)` → IP2315 register **`0x01` bit 0**, again with the
-gate bracketed (`Power_Class.cpp:2398–2410`).
-
-> Two comments in `Power_Class.cpp` say **"IP2316"** while the address constant is named
-> `ip2315_i2c_addr` and the schematic part is an **IP2315**. A typo in M5Unified, not a
-> second part. Noted so nobody goes looking for an IP2316 datasheet.
-
-## 4. Charging parameters — mostly unresolved
-
-| Parameter | Value | Status |
-|---|---|---|
-| Cell capacity | **1150 mAh** | vendor spec |
-| Charge current | Sheet 1 annotates `充电电流 0.5C` → **~575 mA** | **`inferred`** from the annotation and capacity |
-| `ICHGSET` programming resistor | **Not resolved from the schematic** | Open gap |
-| Input | USB Type-C, **DC 5 V** | vendor spec |
-| OVP | **5.95 V** | schematic annotation on `U2` |
-| NTC | `100K-RNTC` at `J2` | schematic |
-| Charge-complete detection | IP2315 `0xC7` bit 7 | M5Unified source + M5Stack's measured note |
-
-So the 0.5 C figure rests on a single schematic annotation, with the resistor that would
-confirm it unread. Treat it as approximate.
-
-## 5. ⚠ There is no USB-PD
-
-The USB-C connector carries the standard **5.1 kΩ CC pulldowns** (`R14` on CC2) that
-advertise a plain sink, but the **IP2315's own `CC1`/`CC2` sense pins are unpopulated**
-(`R1`, `R2` marked `NC`). Combined with the 5.95 V OVP upstream, this is a **5 V-only
-input**; the charger's PD capability is deliberately depopulated.
-
-*(Two earlier readings of this circuit disagreed — one saw only the `NC` resistors and
-concluded there were no CC resistors at all. Both resistor groups exist; they are on
-different parts. Recorded so the question is not re-opened.)*
-
-Practical consequence: **any USB-C source will supply 5 V and nothing more.** A PD-only
-charger that refuses to provide 5 V without negotiation will not charge this board.
-
-## 6. Resources consumed
-
-| Resource | Value |
-|---|---|
-| I²C address | `0x75`, **gated**, on the shared bus |
-| Expander pin | `IO11` — the gate. `PWM3`-capable, used here as a digital output |
-| M5PM1 pins | `BAT_ADC_EN_OD`, `BAT_ADC_IN`, `5VIN_ADC_IN`, `5VOUT_ADC_IN`, `CHG_EN_PP` |
-| M5PM1 registers | `0x22`/`0x23` VBAT, `0x24`/`0x25` VIN, `0x26`/`0x27` 5VINOUT, `0x04` `PWR_SRC`, `0x08` `BATT_LVP` |
-| IP2315 registers used by M5Unified | `0x01` bit 0 (charge enable), `0xC7` bit 7 (charge status) |
-| ESP32-S3 GPIO | **none** |
-
-## 7. Minimal procedure (`inferred`)
-
-```cpp
-#include <M5Unified.h>
-
-void setup() { M5.begin(M5.config()); }
-
-void loop() {
-  M5.update();
-  int16_t mv = M5.Power.getBatteryVoltage();          // millivolts, from the M5PM1 ADC
-  auto chg   = M5.Power.isCharging();                 // gates the IP2315 on and off for you
-  // ... render sparingly; see epaper-display.md on refresh discipline
-  delay(5000);
-}
-```
-
-If you must talk to the IP2315 yourself, **bracket every access**:
-
-```cpp
-auto& ioe1 = M5.getIOExpander(0);
-ioe1.digitalWrite(M5IOE1_Class::gpio11, true);        // gate ON
-/* ... wait for 0x75 to appear, then transact, briefly ... */
-ioe1.digitalWrite(M5IOE1_Class::gpio11, false);       // gate OFF - do not skip this
-```
-
-`M5IOE1_Class::gpio11` is M5Unified's own expander enum, which is **not** the M5IOE1
-library's `M5IOE1_PIN_*` enum. See [`io-expander.md`](io-expander.md) before mixing them.
-
-## 8. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (IP2315)** | I²C pins double as LED driver pins and must be `VBAT`-referenced; a missing NACK on a final read byte can wedge the bus |
-| **Board** | The charger is **gated off the bus** and only reachable through M5IOE1 `IO11` |
-| **Board** | **No USB-PD** — CC sense pins depopulated (§5); 5.95 V OVP |
-| **Board** | No fuel gauge. Voltage-only state of charge |
-| **Framework (M5Unified)** | 64-attempt scan loop before giving up on the charger; `isCharging()` short-circuits when there is no external supply |
-| **Observed (M5Stack)** | `0xC7` = `0x82` charging / `0x45` complete / `0x00` disabled |
-| **Unknown** | Charge current (0.5 C `inferred`), `ICHGSET` resistor, actual runtime on any workload |
-
-## 9. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Charger + six other I²C devices | ⚠ **the documented hazard on this board** | Leave the gate open and bus stability degrades. Open it, transact, close it |
-| Charger access + [NFC](nfc.md) polling | ⚠ | Both are on the one bus, and NFC polling is chatty. Do not gate the charger on inside an NFC scan window |
-| Charger + [sleep](power-and-sleep.md) | ✅ | Charging proceeds independently of the M5PM1 power state |
-| Charging + [display](epaper-display.md) + [Wi-Fi](wifi-and-bluetooth.md) | ⚠ unmeasured | No current budget exists for any combination |
-| Charger + very low battery | ⚠ **the specific documented failure** | The IP2315 may fail to enter I²C mode and disturb the other six devices |
-| Charger + USB-PD-only supply | ❌ | §5 |
-
-## 10. Debugging
-
-| Symptom | Cause |
-|---|---|
-| `0x75` absent from an I²C scan | **Correct behaviour** (§2). Assert `IO11` first |
-| Other I²C devices become unreliable | The gate was left open. Close it |
-| Bus wedged entirely | **Short press of the power button** — M5Stack's documented recovery |
-| `isCharging()` always false with USB plugged in | The M5PM1 `PWR_SRC` short-circuit fires first; check `getPowerSource()` |
-| Board will not charge from a particular charger | PD-only source; there is no PD here (§5) |
-| Battery percentage jumps under load | Voltage-only estimation with no coulomb counting |
-
-## 11. Unresolved questions
-
-- **`ICHGSET` resistor value**, and therefore the real charge current.
-- **No runtime figure exists** for any workload, in any state.
-- Whether the NTC is actually used for charge-current derating, or only monitored.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; battery and charger identical on C153 and C153-LITE (**both are 1150 mAh** — the Lite does not get a smaller cell) |
-| Framework range | M5Unified 0.2.21 · M5PM1 1.0.7 · M5IOE1 1.0.9 |
-| Evidence | Gating hazard: **vendor-documented**, `reported-working`. M5Unified behaviour and register numbers: **read from source**. Charge current: **`inferred`**. Sketch: **`inferred`** |
-| Confidence | High on the bus-gate mechanism; **low on every electrical figure** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../power-architecture.md#charging-and-usb-input`](../power-architecture.md#charging-and-usb-input)
-- [`power-and-sleep.md`](power-and-sleep.md) · [`io-expander.md`](io-expander.md) · [`usb-and-serial.md`](usb-and-serial.md)
-- [`components/injoinic/ip2315`](../../../../components/injoinic/ip2315/README.md) · [`components/awinic/aw32901`](../../../../components/awinic/aw32901/README.md) · [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md)
diff --git a/devices/m5stack/papermono/features/buttons-and-rgb-led.md b/devices/m5stack/papermono/features/buttons-and-rgb-led.md
deleted file mode 100644
index ca0c41e..0000000
--- a/devices/m5stack/papermono/features/buttons-and-rgb-led.md
+++ /dev/null
@@ -1,247 +0,0 @@
-# Buttons and RGB LED — M5Stack PaperMono
-
-> **How do I read the buttons, and why can the indicator not show the colour I asked for?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-## 1. Capability summary and the hardware path
-
-Three switches and one side-mounted RGB indicator, all on the **KEY/RGB/microphone
-sub-board** (`PaperMono KEY RGB.SchDoc`, dated 2026-04-14), reaching the main board
-through the 16-pin board-to-board connector `J6`.
-
-```
-S2 (KEY1) ──────────────▶ ESP32-S3 GPIO2      Button A
-S3 (KEY2) ──────────────▶ ESP32-S3 GPIO3      Button B  (also a strapping pin)
-S1 (PWR_BTN) ───────────▶ M5PM1 BTN_PU        on / off / reset / boot
-
-RGB LED (RS-C1415MBAR)
-   red   ◀── M5PM1  LED_EN_PP     <- no PWM
-   green ◀── M5IOE1 IO8  (PWM2)
-   blue  ◀── M5IOE1 IO9  (PWM1)
-```
-
-| Element | Where | Record |
-|---|---|---|
-| User keys | ESP32-S3 GPIO2 / GPIO3 | [`../pinouts-and-buses.md`](../pinouts-and-buses.md#esp32-s3-complete-pin-map) |
-| Power button | M5PM1 `BTN_PU` | [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) |
-| LED red die | M5PM1 `LED_EN_PP` | idem |
-| LED green / blue dies | M5IOE1 `IO8` / `IO9` | [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) · [`io-expander.md`](io-expander.md) |
-| LED part | `RS-C1415MBAR` | **No datasheet exists** — the only web occurrences anywhere are M5Stack's own pages |
-
-## 2. ⚠ The red die has no PWM, so the colour set is limited
-
-M5Stack says so themselves, on the product page:
-
-> "The RGB LED indicator on the side of the PaperMono body consists of three color LED
-> dies, with the **red LED connected to `LED_EN_PP` of the M5PM1**. After the device is
-> powered on, it will light up according to the M5PM1 default behavior. **Since
-> `LED_EN_PP` does not support PWM output mode configuration, the adjustable colors of
-> this indicator will be limited.**"
-
-This is a **board** limit — the red die is wired to a pin that is not a PWM output — and
-it cannot be worked around in software. What you actually get:
-
-| Channel | Control | Levels |
-|---|---|---|
-| **Red** | M5PM1 `LED_EN_PP`, via `PWR_CFG` (`0x06`) bit 4 | **on / off only** |
-| Green | M5IOE1 `IO8`, PWM channel 2, 12-bit duty | graded |
-| Blue | M5IOE1 `IO9`, PWM channel 1, 12-bit duty | graded |
-
-So the indicator is best treated as **a red status light with a two-channel graded
-accent**, not as a colour display. Any colour that needs partial red — orange, pink,
-warm white, most pastels — is not reachable. Full red, full white-ish (R+G+B all on),
-and the green/blue half of the colour wheel are.
-
-### M5Unified is more limited still
-
-`M5Unified/src/utility/led/LED_PaperMono_Class.cpp:53–80` implements `display()` as:
-
-- **red** — threshold: `bitOn`/`bitOff` M5PM1 register `0x06` bit 4 at a 2048 cutoff
-- **blue** — `ioe1.digitalWrite(gpio9, b >= 2048)` — **binary, not PWM**
-- **green** — `ioe1.setPwmDuty12bit(pwm_ch2, g, normal, g > 0)` — the only true PWM channel
-
-So through `M5.Led` the indicator is **red on/off × blue on/off × green graded**: eight
-base combinations with one dimmable axis. Brightness is applied as
-`br = (brightness+1)²`, the same squared curve as the [frontlight](frontlight.md#51-the-brightness-curve-is-squared-not-linear).
-
-The vendor's own factory firmware does it differently — `hal_board.cpp:25–28` assigns
-**green → `M5IOE1_PWM_CH2` and blue → `M5IOE1_PWM_CH1`**, both at 5 kHz
-(`RGB_PWM_FREQ_HZ = 5000`), i.e. two graded channels. **Nothing documents why M5Unified
-does not PWM blue.** The M5IOE1 manual's exclusion table lists `IO8 & IO9` as mutually
-exclusive **for interrupts**, not for PWM, so a hardware reason is not evident. If you
-want graded blue, drive the M5IOE1 directly as the factory firmware does. `inferred`,
-`not-tested`.
-
-## 3. Prerequisites
-
-| Item | Value |
-|---|---|
-| M5Unified | 0.2.21 — `M5.BtnA` / `M5.BtnB` and `M5.Led` are wired up by board autodetect |
-| M5IOE1 library | 1.0.9 if you drive green/blue directly |
-| M5PM1 library | 1.0.7 if you configure the power button or the red die directly |
-| Power state | User keys and the RGB LED red channel live in **L2**; green/blue are behind the expander in **L3B** |
-
-## 4. Resources consumed
-
-| Resource | Value |
-|---|---|
-| ESP32-S3 GPIO | **GPIO2** (KEY1), **GPIO3** (KEY2) |
-| M5PM1 | `BTN_PU` input; `LED_EN_PP` output; registers `0x06` `PWR_CFG`, `0x13` `GPIO_DRV`, `0x48` `BTN_STATUS`, `0x49`/`0x4A` `BTN_CFG_1/2`, `0x45` `IRQ_MASK3` |
-| M5IOE1 | `IO8` (PWM2), `IO9` (PWM1); registers `0x1B`–`0x1E` duty, `0x25`/`0x26` frequency |
-| PWM frequency | **5000 Hz** in the factory firmware. The M5IOE1's `PWM_FREQ` is **shared by all four channels** |
-
-> **GPIO3 is a strapping pin.** Holding Button B during reset perturbs the ESP32-S3 boot
-> straps. The vendor firmware does not appear to guard against this. `inferred` from the
-> pin map, `not-tested`. See [`usb-and-serial.md`](usb-and-serial.md).
-
-## 5. Minimal procedure (`inferred`)
-
-```cpp
-#include <M5Unified.h>
-
-void setup() {
-  M5.begin(M5.config());
-  M5.Led.setBrightness(64);
-}
-
-void loop() {
-  M5.update();                                  // required; polls buttons and touch
-
-  if (M5.BtnA.wasPressed()) { M5.Led.setColor(0, 0x00FF00); M5.Led.display(); }  // green
-  if (M5.BtnB.wasPressed()) { M5.Led.setColor(0, 0xFF0000); M5.Led.display(); }  // red
-  if (M5.BtnA.pressedFor(1000)) { /* long press */ }
-}
-```
-
-`M5.Led` reports `getCount() == 1` and `led_type_fullcolor`
-(`LED_PaperMono_Class.hpp`) — the "fullcolor" claim is the class's, and §2 is why it
-overstates the hardware.
-
-Direct expander control, as the factory firmware does it (`hal_board.cpp:25–28`,
-`inferred` as a sketch):
-
-```cpp
-#include <M5IOE1.h>
-M5IOE1 ioe1;
-ioe1.begin(&M5.In_I2C, 0x4F, M5IOE1_I2C_FREQ_100K);
-ioe1.setPwmFrequency(5000);
-ioe1.setPwmDuty12bit(M5IOE1_PWM_CH2, 2048, ...);   // green,  IO8
-ioe1.setPwmDuty12bit(M5IOE1_PWM_CH1, 2048, ...);   // blue,   IO9
-```
-
-> ⚠ **M5IOE1 outputs default to open-drain** (`GPIO_DRV_L = 0xFF`, `GPIO_DRV_H = 0x3F`),
-> **including PWM**. Switch the pin to push-pull before expecting a drive. M5Unified does
-> this with `setHighImpedance(pin, false)`.
-
-## 6. The power button
-
-The power button is **not on the ESP32-S3 at all** — it is an input to the M5PM1, and the
-M5PM1 owns what it does.
-
-| Action | Effect | Source |
-|---|---|---|
-| One short press | Power on / **reset** | vendor product page |
-| Two presses in succession | Power off | vendor product page |
-| Hold ~2 s until the red LED blinks | **Download mode** | vendor product page + UiFlow2 page |
-| Short press | Documented recovery from a wedged I²C bus | vendor product page |
-
-> **The single-click reset is aggressive, and third parties disable it.** Two independent
-> hardware-validated third-party projects (`MagicCube/free-ink-on-paper-mono` and
-> `Free-Ink/freeink-sdk`) report explicitly disabling the M5PM1's default single-click
-> reset while preserving the long-hold download escape. The library call is
-> `pm1.setSingleResetDisable(bool)`. This is the strongest independent behavioural
-> corroboration in the whole record: two projects, two authors, the same finding.
-> `reported-working` by them, `not-tested` here.
-
-The M5PM1 also exposes `btnSetConfig(m5pm1_btn_type_t, m5pm1_btn_delay_t)`,
-`btnGetState(bool*)` and `btnGetFlag(bool*)` (`M5PM1/src/M5PM1.h`), and button interrupts
-are masked through `IRQ_MASK3` (`0x45`) with status in `BTN_STATUS` (`0x48`).
-
-> **There is no separate reset button.** The schematic shows exactly three switches on the
-> sub-board (`S1` `PWR_BTN`, `S2` `G2_KEY1`, `S3` `G3_KEY2`). M5Stack's Arduino tutorial
-> page refers to "the reset button on the side"; that page is wrong, and two other vendor
-> pages plus the spec table say power button. Resolved in
-> [`../gaps-and-conflicts.md` R4](../gaps-and-conflicts.md#r4--download-mode-control--resolved-on-the-balance-of-evidence).
-
-## 7. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Board** | Red die on a non-PWM pin — colour set permanently limited (§2) |
-| **Board** | GPIO3 (Button B) is an ESP32-S3 strapping pin |
-| **Board** | Green/blue live behind I²C. **No I²C, no green or blue.** Red survives, because it is on the M5PM1 |
-| **Firmware (M5PM1)** | The red die follows "M5PM1 default behaviour" at power-on before your code runs |
-| **Framework (M5Unified)** | Only green is PWM'd; blue is binary (§2) |
-| **Framework (M5IOE1)** | One shared `PWM_FREQ` register across all four channels |
-| **Observed** | Single-click reset disabled by two independent third-party projects (§6) |
-| **Unknown** | The LED part `RS-C1415MBAR` has **no obtainable datasheet**, so forward voltages, current limits and colour coordinates are unknown |
-
-## 8. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Buttons + [download mode](usb-and-serial.md) | ⚠ | GPIO3 is a strapping pin; holding Button B across reset perturbs the straps |
-| RGB green/blue + everything else on I²C | ✅ addresses distinct | But every LED update is an I²C transaction — do not animate it in a tight loop while [NFC](nfc.md) is polling |
-| RGB + [microSD](microsd.md) / [mic](microphone.md) / [touch](touch.md) | ✅ | Different expander pins; the vendor's warning is about *reconfiguring* pins M5Unified already owns |
-| RGB red + power state L2 | ✅ | Red is on the M5PM1 and available whenever the M5PM1 is alive |
-| RGB green/blue + power state below L3B | ❌ | The expander's own rail and the LED drive go down with L3B |
-| Buttons + [sleep](power-and-sleep.md) | ⚠ | Sheet 1 lists KEY1/KEY2 as M5PM1 wake inputs, but the UserDemo drives its wake from GPIO2/GPIO3 as *ESP32-S3* pins. Which path is live in which state is **not established** |
-
-## 9. Debugging
-
-| Symptom | Cause |
-|---|---|
-| `M5.BtnA` never fires | `M5.update()` not called in `loop()` |
-| Board will not enter download mode | You are looking for a reset button that does not exist (§6) |
-| Board resets when you tap the power button | That is the documented behaviour. Disable it with `setSingleResetDisable(true)` if it is in your way |
-| LED shows the wrong colour | §2 — red is binary. Ask for a colour with partial red and you get full red or none |
-| LED does nothing at all | M5IOE1 outputs default open-drain; set push-pull |
-| Blue will not dim | You are on `M5.Led`, which writes blue as a binary level (§2) |
-| Board boots into the wrong mode occasionally | Button B (GPIO3) held during reset |
-
-## 10. Unresolved questions
-
-- **Are KEY1/KEY2 genuinely M5PM1 wake sources, or only ESP32-S3 inputs?** Sheet 1 says
-  wake-capable; the firmware only uses them as host GPIOs. Unresolved.
-- **Why does M5Unified not PWM blue?** No documented reason (§2).
-- **No datasheet for `RS-C1415MBAR`.** Electrical limits unknown.
-
-
-### ⚠ Both driver chips have a NeoPixel engine. This board does not use it.
-
-A real trap when reading the component records alongside this page: **the M5IOE1
-and the M5PM1 each contain a working WS2812 driver**, and neither drives this LED.
-
-| Chip | NeoPixel facility | Used for the RGB LED? |
-|---|---|---|
-| M5IOE1 | `LED_CFG` `0x24`, `LED_RAM` `0x30`–`0x6F` (32 × RGB565), output on `IO14` | **No** |
-| M5PM1 | `NEO_CFG` `0x50`, MUX on `IO0` | **No** |
-
-The PaperMono's RGB LED is **three discrete dies on three separate lines** — red
-on the M5PM1's `LED_EN_PP`, green and blue on M5IOE1 `IO8`/`IO9`. There is no
-data line and no RMT involvement. Those engines exist for *other* FreeInk-family
-boards; on this one `IO14` is microSD power and `IO0` is the RTC interrupt.
-
-Independently corroborated by `osprey74/Nostos` (`firmware/nostos-fw/src/led.rs`),
-whose own comment reads: 緑=M5IOE1 `PYG8` / 青=M5IOE1 `PYG9` / 赤=M5PM1 `LED_EN`
-（3 線独立・**WS2812 ではない**） — *"three independent lines, **not WS2812**"*.
-
-**Consequence:** `FastLED`, `Adafruit_NeoPixel` and `smart_leds` are all the wrong
-tool here. Across ten PaperMono repositories there is **zero** WS2812/SK6812 use
-in any LED path.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**. ⚠ The factory firmware uses the RGB LED's availability as one of its **Pro-vs-Lite discriminators** (`hal_board.cpp:162`) |
-| Framework range | M5Unified 0.2.21 · M5IOE1 1.0.9 · M5PM1 1.0.7 |
-| Evidence | Red-die limitation: **vendor-documented**, `reported-working`. Wiring: **schematic**. M5Unified behaviour: **read from source**. Single-click-reset behaviour: **community-reported**, two independent projects. Sketches: **`inferred`** |
-| Confidence | High on the wiring and the colour limitation; medium on the API sketches |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md`](../pinouts-and-buses.md) · [`../power-architecture.md`](../power-architecture.md)
-- [`power-and-sleep.md`](power-and-sleep.md) · [`usb-and-serial.md`](usb-and-serial.md) · [`io-expander.md`](io-expander.md) · [`frontlight.md`](frontlight.md)
-- [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) · [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md)
diff --git a/devices/m5stack/papermono/features/buzzer.md b/devices/m5stack/papermono/features/buzzer.md
deleted file mode 100644
index b37565c..0000000
--- a/devices/m5stack/papermono/features/buzzer.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# Buzzer — M5Stack PaperMono
-
-> **How do I make a noise?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-**This is a short guide because the feature is small.** One pin, one LEDC channel, no
-amplifier, no codec, and no acoustic specification from anyone.
-
-## 1. Capability summary and the hardware path
-
-A buzzer on the KEY/RGB sub-board, driven directly from an ESP32-S3 GPIO through the
-LEDC (PWM) peripheral. Net `G42_BB_PWM`, reaching the sub-board through `J6`.
-
-```
-ESP32-S3 GPIO42 ──LEDC PWM──▶ buzzer (on the KEY/RGB sub-board, via J6)
-```
-
-There is **no** speaker, **no** amplifier and **no** DAC on this board. `M5.Speaker` is
-not the right abstraction here; the vendor drives LEDC directly.
-
-## 2. Prerequisites and resources
-
-| Item | Value |
-|---|---|
-| ESP-IDF | 5.5.1 — `driver/ledc.h` |
-| ESP32-S3 GPIO | **GPIO42** — the only pin involved |
-| Power state | L2 — the buzzer is on the ESP32-S3's own rail; no expander pin, no switched supply |
-
-Vendor LEDC allocation (`M5PaperMono-UserDemo/main/hal/hal_buzzer.cpp:17–29`):
-
-| Setting | Value |
-|---|---|
-| Speed mode | `LEDC_LOW_SPEED_MODE` |
-| **Timer** | **`LEDC_TIMER_3`** |
-| **Channel** | **`LEDC_CHANNEL_7`** |
-| Resolution | `LEDC_TIMER_10_BIT` |
-| Duty when sounding | **512** (50 %) |
-| Default frequency | 2000 Hz |
-| Frequency clamp | **40 Hz – 12 000 Hz**, enforced in software |
-
-**Timer 3 and channel 7 are deliberately at the top of the range** so they do not collide
-with anything a user allocates from channel 0 upward. Keep that convention.
-
-## 3. Minimal procedure (`inferred`)
-
-Direct LEDC, matching the vendor's `setBuzzerOutput()` (`hal_buzzer.cpp:186–195`):
-
-```c
-#include <driver/ledc.h>
-
-ledc_timer_config_t t = {};
-t.speed_mode = LEDC_LOW_SPEED_MODE;
-t.duty_resolution = LEDC_TIMER_10_BIT;
-t.timer_num = LEDC_TIMER_3;
-t.freq_hz = 2000;
-t.clk_cfg = LEDC_AUTO_CLK;
-ledc_timer_config(&t);
-
-ledc_channel_config_t c = {};
-c.gpio_num = GPIO_NUM_42;
-c.speed_mode = LEDC_LOW_SPEED_MODE;
-c.channel = LEDC_CHANNEL_7;
-c.timer_sel = LEDC_TIMER_3;
-c.duty = 0;
-ledc_channel_config(&c);
-
-// tone
-ledc_set_freq (LEDC_LOW_SPEED_MODE, LEDC_TIMER_3, 1000);
-ledc_set_duty (LEDC_LOW_SPEED_MODE, LEDC_CHANNEL_7, 512);   // 50 %
-ledc_update_duty(LEDC_LOW_SPEED_MODE, LEDC_CHANNEL_7);
-
-// silence
-ledc_stop(LEDC_LOW_SPEED_MODE, LEDC_CHANNEL_7, 0);
-```
-
-The factory firmware wraps this in a FreeRTOS task with a 6-deep command queue,
-supporting `playBuzzer(freq, ms)`, `playBuzzerSweep(start, end, ms)`,
-`playBuzzerPattern(tones, count)`, `stopBuzzer()` and `setBuzzerMuted(bool)` — with sweep
-steps updated every 2 ms. That structure is worth copying if you want non-blocking tones;
-it is application code, not a library.
-
-## 4. Limits
-
-| Class | Limit |
-|---|---|
-| **Board** | **Square wave only.** 50 % duty, one channel — no volume control, no waveform, no polyphony |
-| **Board** | No amplifier, no speaker, no line out |
-| **Framework (vendor app)** | 40 Hz – 12 kHz clamp, 10-bit resolution |
-| **Unknown** | The buzzer part is not identified in any document retrieved. **Its resonant frequency is unknown**, so the loudest tone is unknown |
-
-Because the resonant frequency is undocumented, "which frequency is loudest" is an
-empirical question nobody has answered. Magnetic buzzers of this size typically peak
-around 2–4 kHz, and the vendor's 2000 Hz default is consistent with that — but that is a
-guess about a part we cannot name, `inferred` and worth nothing without a measurement.
-
-## 5. Conflicts
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Buzzer + your own `ledcWrite`/LEDC use | ⚠ | Vendor uses **timer 3, channel 7**. Start your allocations at 0 |
-| Buzzer + [microphone](microphone.md) | ✅ works, acoustically obvious | The buzzer is audible in any recording |
-| Buzzer + [sleep](power-and-sleep.md) | ⚠ | The vendor's shutdown path explicitly **drives GPIO42 low** (`app_shutdown.cpp:118–119`) before powering down. Do the same, or you may leave it energised |
-| Buzzer + [display](epaper-display.md) | ✅ | Unrelated |
-
-## 6. Debugging
-
-| Symptom | Cause |
-|---|---|
-| No sound | Duty left at 0, or `ledc_update_duty()` not called |
-| Sound continues after shutdown | GPIO42 not driven low before the rail drops |
-| Your PWM elsewhere stopped working | You reused timer 3 or channel 7 |
-| Very quiet at some frequencies | Off-resonance; the resonant frequency is undocumented |
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; fitted on both C153 and C153-LITE |
-| Framework range | ESP-IDF 5.5.1 · arduino-esp32 3.3.10 |
-| Evidence | Pin and LEDC allocation: **read from vendor source** (`hal_buzzer.cpp`), `executed-success`. Sketch: **`inferred`**. Acoustics: **unknown** |
-| Confidence | High on the wiring and driver setup; **none on loudness or tone quality** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md`](../pinouts-and-buses.md) · [`microphone.md`](microphone.md) · [`power-and-sleep.md`](power-and-sleep.md) · [`../resources-and-conflicts.md`](../resources-and-conflicts.md)
diff --git a/devices/m5stack/papermono/features/epaper-display.md b/devices/m5stack/papermono/features/epaper-display.md
deleted file mode 100644
index ab0afb4..0000000
--- a/devices/m5stack/papermono/features/epaper-display.md
+++ /dev/null
@@ -1,326 +0,0 @@
-# E-paper display — M5Stack PaperMono
-
-> **How do I draw on the screen, and how do I do it without damaging the panel?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-The single most important sentence on this page: **M5Stack says its own M5GFX waveforms
-for this panel are unstable and recommends bypassing them.** Everything else follows
-from that.
-
-## 1. Capability summary and the hardware path
-
-A 3.97-inch monochrome electrophoretic panel, 480 × 800 at 235 DPI, marketed as
-4-level greyscale, with an integrated [frontlight](frontlight.md) and a
-[capacitive touch layer](touch.md) on separate FPCs.
-
-```
-ESP32-S3  ──SPI2 (write-only)──▶  SSD1677 controller  ──▶  DKE DEPG0397BBS770F3 panel
-   │                                    ▲
-   │                                    │ RST  ◀── M5IOE1 IO5
-   │                                    │ 3V3  ◀── M5IOE1 IO3  (EPD_3V3_L3B rail)
-   └── GPIO18 BUSY ◀────────────────────┘
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Panel | DKE `DEPG0397BBS770F3` (vendor demo says `DEPG0397BBS770F3HP-XM`) | [`components/dke/depg0397bbs770f3`](../../../../components/dke/depg0397bbs770f3/README.md) |
-| Controller | Solomon Systech SSD1677, 4-wire SPI | [`components/solomon-systech/ssd1677`](../../../../components/solomon-systech/ssd1677/README.md) |
-| Rail enable + reset | M5IOE1 `IO3` / `IO5` | [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) · [`io-expander.md`](io-expander.md) |
-| Panel 3.3 V LDO | `U5` SSP7615-33DFR, 400 mA | [`../power-architecture.md`](../power-architecture.md#rails-and-what-produces-them) |
-| Host | ESP32-S3R8 | [`components/espressif/esp32-s3r8`](../../../../components/espressif/esp32-s3r8/README.md) |
-
-**There is no MISO.** The link is write-only; the only status you get back is the
-`BUSY` line on GPIO18.
-
-## 2. Prerequisites and exact versions
-
-| Item | Value | Why it matters |
-|---|---|---|
-| ESP-IDF | **5.5.1** | Both vendor projects' `dependencies.lock` |
-| arduino-esp32 | **3.3.10** (managed component) | idem |
-| M5Unified | **0.2.21** | `board_M5PaperMono` ships in this release tag |
-| M5GFX | **0.2.28** | idem |
-| PSRAM | **8 MB octal, `CONFIG_SPIRAM_MODE_OCT=y`** | **Mandatory.** See §7 |
-| Flash | 16 MB, single `factory` app at `0x10000`, size `0xF00000` | No OTA slot |
-
-PlatformIO, as published by M5Stack:
-
-```ini
-[env:m5stack-papermono]
-platform = espressif32@6.12.0
-board = esp32-s3-devkitm-1
-framework = arduino
-board_build.partitions = default_16MB.csv
-board_upload.flash_size = 16MB
-board_build.arduino.memory_type = qio_opi     ; <- QIO flash + OPI PSRAM. Not optional.
-build_flags = -DESP32S3 -DBOARD_HAS_PSRAM -mfix-esp32-psram-cache-issue
-              -DARDUINO_USB_CDC_ON_BOOT=1 -DARDUINO_USB_MODE=1
-lib_deps =
-    M5Unified = https://github.com/m5stack/M5Unified#develop
-    M5PM1 = https://github.com/m5stack/M5PM1
-    M5IOE1 = https://github.com/m5stack/M5IOE1
-```
-
-> **The `#develop` pin is stale.** `board_M5PaperMono` is byte-identical on `master` and
-> `develop` and ships in released tags M5Unified 0.2.21 / M5GFX 0.2.28. Verified
-> 2026-09-01; see [`../gaps-and-conflicts.md` R5](../gaps-and-conflicts.md#r5--m5unifieddevelop-requirement--resolved-the-instruction-is-stale).
-> You may still want `develop` for unrelated behavioural fixes, but not for board support.
-
-## 3. Resources consumed
-
-| Resource | Value |
-|---|---|
-| SPI bus | **SPI2_HOST**, MOSI GPIO14, SCLK GPIO15, DC GPIO17, CS GPIO16, 3-wire mode, SPI mode 0 |
-| Clock | **40 MHz write** in M5GFX; **20 MHz** in the vendor OTP demo — see §8 |
-| Status line | GPIO18 `BUSY`, input only |
-| Expander pins | `IO3` rail enable, `IO5` reset (both behind I²C `0x4F`) |
-| Rail | `EPD_3V3_L3B`, part of power state **L3A/L3B** |
-| PSRAM | M5GFX framebuffers; OTP demo allocates `3 × 48 000 = 144 000 B` with `MALLOC_CAP_SPIRAM` |
-| Series resistor | 22 Ω on SCLK (`R38`) |
-
-Panel RAM packing (OTP demo): MSB-first, **100 bytes per row × 480 rows**; in monochrome
-RAM **1 = white, 0 = black**. Four-grey encoding across two planes is
-`white=00, light=10, dark=01, black=11`.
-
-## 4. Orientation — the axis trap
-
-**The controller is addressed 800 × 480; the panel is natively 480 × 800 portrait.**
-
-| Layer | Geometry |
-|---|---|
-| Vendor product page, spec table | `480 × 800` |
-| Store title and URL handle | `800x480` |
-| M5GFX panel config | `panel_width = 800`, `panel_height = 480`, **`offset_rotation = 3`** |
-| Vendor OTP demo raw driver | works natively in `800 × 480`, RAM X = visible vertical |
-
-Through M5GFX you see 480 × 800 and the rotation is done for you. **Anyone writing a raw
-SSD1677 driver from the docs' `480 × 800` figure will get the axes transposed.**
-
-## 5. Minimal procedure — M5GFX (`inferred`)
-
-Derived from `M5GFX/src/M5GFX.cpp:2030–2146` and the vendor's own published sketch
-shape. **Not run on hardware.**
-
-```cpp
-#include <M5Unified.h>
-
-void setup() {
-  auto cfg = M5.config();
-  M5.begin(cfg);                       // brings up I²C, M5PM1, M5IOE1,
-                                       // the EPD rail (IO3) and the panel reset (IO5)
-
-  M5.Display.setEpdMode(epd_mode_t::epd_text);   // quality | text | fast | fastest
-  M5.Display.setRotation(0);                     // 480 x 800 portrait as presented
-  M5.Display.setTextDatum(middle_center);
-  M5.Display.setFont(&fonts::FreeSansBold18pt7b);
-  M5.Display.drawString("hello", M5.Display.width() / 2, M5.Display.height() / 2);
-  M5.Display.display();                          // push
-}
-
-void loop() { M5.update(); }
-```
-
-`M5.begin()` performs the expander bring-up itself, in raw register writes rather than
-through the M5IOE1 library — `M5GFX.cpp:2088–2096` sets `IO5`/`IO6` and `IO13`/`IO14` to
-output, drives `IO3` high, sets those pins push-pull, then pulses `IO5`/`IO6` low for
-8 ms to reset the panel and the touch controller together.
-
-> One of those comments is wrong. `M5GFX.cpp:2096` reads
-> `// Set LOW io11, HIGH io13,14` on a `bitOn` of register `0x06` with mask `0b00110000`
-> — register `0x06` is `GPIO_OUT_H` covering P14–P9, so the mask is P13 and P14 only, and
-> `bitOn` cannot set anything low. The code is right, the comment is not. Do not
-> reverse-engineer the expander map from M5GFX comments.
-
-### Refresh modes
-
-| Mode | `epd_mode_t` | Vendor lab figure |
-|---|---|---|
-| Quality | `epd_quality = 1` | 4.71 s |
-| Text | `epd_text = 2` | 0.45 s |
-| Fast | `epd_fast = 3` | 0.34 s |
-| Fastest | `epd_fastest = 4` | 0.07 s |
-
-> ⚠ **These four numbers are vendor laboratory figures for a LUT set that may no longer
-> be the shipped one.** M5GFX `develop` has *replaced* `lut_quality` and `lut_text`
-> outright, leaving 17 lines of the previous `lut_quality` commented out in-tree, and
-> added a new `_refresh_mode1_text()` code path. The factory firmware pins a M5GFX commit
-> (`02107b82…`) older than either current branch. So the published timings correspond to
-> some specific unnamed build and **should not be treated as characteristic of any
-> version you can check out today**. Vendor claim, `not-tested`, and known to be
-> version-sensitive.
->
-> The same four numbers appear on the PaperMono-Lite page, whose own caption still says
-> *"laboratory test results for **PaperMono**"* — they were copied, not separately
-> measured.
-
-## 6. Minimal procedure — the OTP path (`reported-working` as a vendor recommendation, `inferred` as code)
-
-**This is what M5Stack tells you to use.** `M5PaperMono-OTP-Demo` bypasses M5GFX's panel
-driver entirely, talks to the SSD1677 directly over SPI2 at 20 MHz, and **uploads no LUT
-at all** — it uses only the controller's factory-programmed OTP waveforms. Verified by
-enumerating all 24 `write_command`/`write_register` call sites: none is the SSD1677
-LUT-write command `0x32`.
-
-Reset, through the expander rather than an ESP32 pin
-(`M5PaperMono-OTP-Demo/components/EDP_OTP_LUT_demo/src/EDP_SPI.cpp`):
-
-```c
-auto& ioe = M5.getIOExpander(0);
-ioe.setHighImpedance(2, false);  ioe.setDirection(2, true);  ioe.digitalWrite(2, true);   // IO3: EPD 3V3
-ioe.setHighImpedance(4, false);  ioe.setDirection(4, true);
-ioe.digitalWrite(4, false);  vTaskDelay(pdMS_TO_TICKS(10));                                // IO5: EPD RST
-ioe.digitalWrite(4, true);   vTaskDelay(pdMS_TO_TICKS(10));
-```
-
-Note the raw `2` and `4`: the demo bypasses the library enum on purpose, with the comment
-`// M5IOE1 uses zero-based pin indexes.` See [`io-expander.md`](io-expander.md).
-
-Controller init (`EDP_OTP_LUT_demo.cpp:206–224`, comments are M5Stack's):
-
-```c
-write_command(0x12);                                  // SOFT RESET
-write_register(0x18, {0x80});                         // Internal temperature sensor
-write_register(0x0C, {0xAE,0xC7,0xC3,0xC0,0x80});     // Booster soft-start
-write_register(0x01, {0xDF,0x01,0x02});               // 480 gate outputs
-write_register(0x3C, {0x01});                         // Border waveform
-write_register(0x21, {0x00});                         // Normal RAM display mode
-```
-
-Four-grey init differs: data-entry mode `0x02` instead of `0x03`, plus
-`write_register(0x1A, {0x5A})` — a forced "grey-mode temperature value" that selects the
-OTP grayscale waveform bank instead of letting the internal sensor pick one. That reading
-is `inferred` from the vendor comment and SSD1677 convention; it was not checked against
-the datasheet.
-
-Refresh triggers — the `0x22` Display Update Control value selects waveform and scope:
-
-| Mode | `0x22` | Then |
-|---|---|---|
-| Partial refresh | `0xF8` | `0x20` Master Activation; border floated first with `0x3C = 0x80` |
-| Partial, follow-up | `0x14` | `0x20` |
-| Mono full refresh | `0xFF` | `0x21 = 0x00`, then `0x20` |
-| Four-grey full refresh | `0xD7` | after `0x24` and `0x26` RAM writes, then `0x20` |
-
-The demo issues `0x10 {0x01}` (deep sleep) after every refresh.
-
-## 7. Octal PSRAM is mandatory — and the failure looks like dead hardware
-
-`M5GFX.cpp:2025` / `:2030`:
-
-```
-E ... M5PaperMono need OPI-PSRAM enabled
-```
-
-If `CONFIG_ESP32S3_SPIRAM_SUPPORT` or `CONFIG_SPIRAM_MODE_OCT` is missing, M5GFX **still
-identifies the board**, then resets the panel and touch objects and jumps to
-`init_clear`. You get a correctly-detected board, a completely blank screen, and one log
-line that is easy to miss at `CORE_DEBUG_LEVEL=0` — which is exactly what the vendor's
-own PlatformIO snippet sets.
-
-**Framework limit**, fixable in the build config: `board_build.arduino.memory_type = qio_opi`
-(PlatformIO) or `CONFIG_SPIRAM=y` + `CONFIG_SPIRAM_MODE_OCT=y` (ESP-IDF).
-
-## 8. Panel safety — the rules that are not optional
-
-All four are M5Stack's own words, reproduced from the product page. `reported-working`
-as guidance; the failure modes were not reproduced here.
-
-1. **Avoid direct sunlight and prolonged sun exposure.** "High temperatures or strong UV
-   can damage the panel." This is a **physics/board** limit, not a software one.
-2. **Roughly one full refresh per ten partial fast refreshes**, to clear accumulated
-   ghosting.
-3. **Never run uninterrupted continuous partial fast refreshes.** M5Stack: long-term DC
-   imbalance causes **irreversible damage**. This is the single destructive failure mode
-   on the board, and it is reachable from ordinary application code — an animation loop
-   is enough.
-4. **If you upload custom waveforms, DC balance is your responsibility.** "Otherwise,
-   irreversible damage may be caused to the panel." The OTP path exists precisely so you
-   do not have to take that on.
-
-A recoverable relative of (2), also from the vendor: after prolonged repeated refreshing,
-black deposited pixels may appear from ink-particle physics. Leave the panel idle a
-while, then do one full refresh.
-
-## 9. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (SSD1677)** | 20 MHz maximum write clock (§12.1); 680 gate outputs — the board configures 480 |
-| **Silicon (panel)** | Electrophoretic; image persists unpowered; DC imbalance is cumulative and irreversible |
-| **Board** | Write-only SPI, no MISO. Panel rail and reset only reachable through I²C. 22 Ω on SCLK |
-| **Framework (M5GFX)** | Drives 40 MHz — **above both the SSD1677 and DKE ratings**. Four LUT modes. `offset_rotation = 3` |
-| **Framework (M5GFX)** | Aborts silently without OPI PSRAM (§7) |
-| **Observed / reported** | Vendor states its own waveforms are "currently unstable"; corroborated in-tree by the `master`→`develop` LUT replacement |
-| **Unresolved** | 4 grey levels (M5Stack) vs `GN — 2Grey Level` in the DKE manual's own optical table |
-
-### The clock conflict, stated plainly
-
-M5GFX writes at **40 MHz** (`M5GFX.cpp:2114`). The SSD1677 datasheet §12.1 **and** the DKE
-panel manual p. 16 **independently** state a **20 MHz** maximum, and the vendor's own OTP
-demo uses 20 MHz. This is a 2× overclock of a rated bus limit in the vendor's own
-graphics library, in the same library the vendor says has refresh problems.
-
-It is not proven to be the cause of anything. It is the **first thing worth measuring**
-if you have hardware and are chasing refresh artefacts. Tracked as
-[`../gaps-and-conflicts.md` C3](../gaps-and-conflicts.md#c3--spi-clock-exceeds-the-panels-rated-maximum).
-
-## 10. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Display + [touch](touch.md) | ✅ intended | Different buses. M5GFX resets both together on `IO5`/`IO6` |
-| Display + [microSD](microsd.md) | ✅ no pin conflict | SDMMC is GPIO8–13, panel is GPIO14–18. Both draw from the L3B domain; both power enables are expander pins, so both need a working I²C bus |
-| Display + [Wi-Fi](wifi-and-bluetooth.md) | ⚠ untested together | No pin conflict. A full refresh is seconds of SPI DMA alongside a radio duty cycle; no measurement exists |
-| Display + [LoRa](lora.md) | ✅ separate SPI hosts | Panel on `SPI2_HOST`, LoRa on `SPI3_HOST` |
-| Display + [frontlight](frontlight.md) | ✅ | Different chips entirely — panel rail on M5IOE1 `IO3`, frontlight PWM on M5PM1 `G3` |
-| Display + deep sleep | ✅ by design | The image persists with the rail off. Turn the rail off *after* `BUSY` clears |
-| **Writing "PYG3" to the expander expecting brightness** | ❌ **silent panel death** | You just cut `EPD_3V3_L3B`. Nothing reports an error. See [`../pin-naming-and-the-pyg-ambiguity.md`](../pin-naming-and-the-pyg-ambiguity.md) |
-
-## 11. Debugging
-
-| Symptom | Likely cause |
-|---|---|
-| Blank screen, board otherwise fine | **OPI PSRAM not enabled** (§7). Check the log at `CORE_DEBUG_LEVEL≥3` |
-| Blank screen, no log line | `EPD_3V3_L3B` never enabled — the enable has a 1 MΩ pulldown and defaults **off** |
-| Panel stops updating mid-session | Something wrote M5IOE1 `IO3` low. Nine times in ten this is the `PYG3` mix-up |
-| `BUSY` never clears | Panel not out of reset (`IO5`), or the rail is off, or SPI is going nowhere (no MISO to tell you) |
-| Ghosting builds up | You are past ~10 partial refreshes. Do a full one |
-| Refresh looks wrong on one build, fine on another | Different M5GFX commit → different LUTs. Pin the commit |
-| Axes transposed in a hand-written driver | 480 × 800 is the *rotated* view; the controller is 800 × 480 |
-
-## 12. Alternatives and when to choose each
-
-| Approach | Choose when | Cost |
-|---|---|---|
-| **M5GFX / `M5.Display`** | You want fonts, sprites, LVGL-adjacent conveniences and touch integration for free | The unstable-LUT warning; 40 MHz clock; needs OPI PSRAM |
-| **Vendor OTP demo path** | You care about panel lifetime and refresh stability — **the vendor's own recommendation** | You write your own drawing layer. No fonts, no sprites |
-| Third-party drivers (`bb_epaper`, ESPHome `SSD1677`) | Existing ecosystem integration | PaperMono support is **claimed but unverified**; see [`../compatibility-and-status.md`](../compatibility-and-status.md) |
-
-## 13. Unresolved questions
-
-- **How many of the panel's 34 waveform slots are OTP-programmed, and over what
-  temperature span?** Unpublished. Outside the programmed range the failure is a silent
-  no-refresh.
-- **Is it really four grey levels?** The vendor demo implements a working four-grey mode;
-  the panel manual's optical table says two. Unresolved.
-- **`DEPG0397BBS770F3` vs `DEPG0397BBS770F3HP-XM`** — the suffix is undocumented.
-- **DKE's mechanical drawing note 3 (`800 gate × 480 source`) is provably backwards** —
-  800 gate lines would exceed the SSD1677's 680 gate outputs, and the firmware configures
-  480 gates.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2** (SKU C153 and C153-LITE; the panel is identical on both) |
-| Framework range | ESP-IDF 5.5.1 · arduino-esp32 3.3.10 · M5Unified 0.2.21 · M5GFX 0.2.28 |
-| Evidence | Pin map and register sequences: **read from vendor source at cited `file:line`**. Safety rules: **`reported-working`** (vendor). Code sketches: **`inferred`**. Timings: **vendor lab figures, version-sensitive, `not-tested`** |
-| Confidence | High on wiring and register sequences; **low on timing and refresh quality** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md`](../pinouts-and-buses.md#spi-buses) · [`../power-architecture.md`](../power-architecture.md) · [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md)
-- [`frontlight.md`](frontlight.md) · [`touch.md`](touch.md) · [`io-expander.md`](io-expander.md) · [`power-and-sleep.md`](power-and-sleep.md)
-- [`components/dke/depg0397bbs770f3`](../../../../components/dke/depg0397bbs770f3/README.md) · [`components/solomon-systech/ssd1677`](../../../../components/solomon-systech/ssd1677/README.md)
-- [`vendors/dke`](../../../../vendors/dke/README.md) — how the panel manual was obtained, and why `pdftotext` returns nothing
diff --git a/devices/m5stack/papermono/features/frontlight.md b/devices/m5stack/papermono/features/frontlight.md
deleted file mode 100644
index 396974a..0000000
--- a/devices/m5stack/papermono/features/frontlight.md
+++ /dev/null
@@ -1,172 +0,0 @@
-# Frontlight — M5Stack PaperMono
-
-> **How do I set the frontlight brightness, and why is the curve strange?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-## 1. Capability summary and the hardware path
-
-An LED frontlight bonded to the e-paper stack, driven by a boost converter producing a
-15 V rail, dimmed by a PWM input from the **power-management chip** — not from the
-ESP32-S3 and not from the I/O expander.
-
-```
-M5PM1 GPIO3 (PWM0) ──▶ AW9967 boost (U11) ──▶ BL_15V_L3B ──▶ frontlight FPC (J1)
-                              ▲
-                              └── BL_FB current feedback, set by R29
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Dimming PWM source | M5PM1 `G3`, net `PYG3_BL_PWM`, pin 13 | [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) |
-| Boost driver | Awinic **AW9967**, designator `U11` | [`components/awinic/aw9967`](../../../../components/awinic/aw9967/README.md) |
-| Connector | `J1`, 6-pin — `PYG3_BL_PWM`, `BL_FB`, `BL_15V_L3B` | [`../pinouts-and-buses.md`](../pinouts-and-buses.md#connectors) |
-
-> ⚠ **`PYG3` is the most dangerous token in this device's documentation.** On the
-> **M5PM1** it is the *net* name of the frontlight PWM pin. On the **M5IOE1** it is the
-> *symbol pin* name of the **e-paper 3.3 V rail enable**. Writing to the wrong one cuts
-> the display's power and reports no error. Read
-> [`../pin-naming-and-the-pyg-ambiguity.md`](../pin-naming-and-the-pyg-ambiguity.md)
-> before touching either.
-
-## 2. Prerequisites
-
-| Item | Value |
-|---|---|
-| M5Unified / M5GFX | 0.2.21 / 0.2.28 — `Light_M5PaperMono` is registered as the board's backlight class |
-| M5PM1 library | 1.0.7 (registry `m5stack/m5pm1`) if you drive it directly |
-| Power state | **L3B** — the boost rail belongs to the top state; enabled during `M5.begin()` |
-| I²C | The M5PM1 at `0x6E` must be reachable. No I²C, no dimming |
-
-## 3. Resources consumed
-
-| Resource | Value |
-|---|---|
-| M5PM1 GPIO | `G3`, driven as **PWM0** (`GPIO_FUNC0` bit pattern `0xC0`, `GPIO_DRV` bit 3 cleared → push-pull) |
-| M5PM1 registers | `0x13` drive, `0x16` function, `0x30`/`0x31` PWM0 duty, `0x34`/`0x35` PWM frequency |
-| PWM frequency | **5000 Hz**, written by M5GFX |
-| ESP32-S3 GPIO | **none** — this costs you no host pin at all |
-| Rail | `BL_15V_L3B` (state L3B) |
-
-## 4. Minimal procedure (`inferred`)
-
-The M5GFX route is one call:
-
-```cpp
-#include <M5Unified.h>
-
-void setup() {
-  M5.begin(M5.config());
-  M5.Display.setBrightness(128);   // 0-255; see §5 - this is NOT half brightness
-}
-```
-
-`M5.Display.setBrightness(0)` writes `0x31 = 0` and turns the boost off.
-
-Driving the M5PM1 directly, if you want a different frequency or a linear curve
-(shape taken from the vendor's published M5PM1 examples; `inferred`):
-
-```cpp
-#include <M5PM1.h>
-M5PM1 pm1;
-
-pm1.begin(&M5.In_I2C, M5PM1_DEFAULT_ADDR, M5PM1_I2C_FREQ_100K);
-pm1.gpioSetDrive(M5PM1_GPIO_NUM_3, M5PM1_GPIO_DRIVE_PUSHPULL);
-pm1.gpioSetFunc (M5PM1_GPIO_NUM_3, M5PM1_GPIO_FUNC_PWM);
-pm1.setPwmFrequency(20000);                       // inside the AW9967's rated 10-100 kHz
-pm1.setPwmDuty12bit(M5PM1_PWM_CH0, 2048, false, true);   // ~50 % linear
-```
-
-The API names above are transcribed from `M5PM1/src/M5PM1.h`
-(`setPwmFrequency`, `setPwmDuty12bit`, `analogWrite`, `gpioSetFunc`, `gpioSetDrive`).
-**The channel constant spelling was not verified** — the header's PWM channel enum was
-not read in this pass, and the M5PM1 manual is internally inconsistent about
-PWM0/PWM1 versus PWM1/PWM2 naming. Check it before compiling.
-
-## 5. Three things M5GFX does that will surprise you
-
-All three are software or documentation issues, not hardware faults, and all three are
-fixable without touching the board.
-
-### 5.1 The brightness curve is squared, not linear
-
-`M5GFX.cpp:849`: `br = brightness * brightness`, then the duty registers get
-`(br >> 4) & 0xFF` and `(br >> 12) | 0x10`. A commented-out linear write sits directly
-above it at `:847`.
-
-So **`setBrightness(128)` is roughly a quarter of full output, not half.** If your UI
-shows a linear slider, it is lying to the user. Apply a square-root correction, or write
-the registers yourself.
-
-### 5.2 The PWM frequency is below the driver's rated range
-
-M5GFX programs `0x34`/`0x35` to **5000 Hz**. The AW9967 datasheet specifies a
-**10–100 kHz** dimming input range. Below the specified range, dimming linearity and
-audible behaviour are not guaranteed — a 5 kHz square wave into an inductor-based boost
-converter is inside the audible band.
-
-**Framework limit**, not a board limit. Rewriting `0x34`/`0x35` to 20–50 kHz after
-`M5.begin()` is a one-line change. Untested — nobody has reported whether the PaperMono
-audibly whines. Tracked as
-[`../gaps-and-conflicts.md` C5](../gaps-and-conflicts.md#c5--frontlight-pwm-frequency-below-the-drivers-rated-range).
-
-### 5.3 The schematic's own current annotation is stale
-
-The sheet-2 note claims `Iset = 15 mA` with `Rset = 11 R`. The **fitted `R29` is 18 Ω**,
-which gives roughly **11 mA**, and the note's arithmetic is internally inconsistent with
-its own formula. Treat the annotation as stale; treat 11 mA as the better estimate,
-`inferred` and unmeasured.
-
-## 6. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (AW9967)** | 10–100 kHz rated dimming input |
-| **Board** | LED current set by `R29 = 18 Ω` → ~11 mA. Not adjustable in software |
-| **Board** | Boost rail lives in state **L3B**; there is no way to light the frontlight from L0/L1/L2 |
-| **Framework** | 5 kHz PWM (out of range) and a squared gamma curve |
-| **Observed** | One third-party project (`MagicCube/free-ink-on-paper-mono`, hardware-validated on a Lite) holds the frontlight at a fixed **127/255**. That is the only real-world brightness setting anyone has published |
-
-**No power figure exists.** Nobody has published frontlight current draw or its effect on
-battery life, and none was derived here.
-
-## 7. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Frontlight + [display](epaper-display.md) | ✅ the intended pairing | Different chips: panel rail is M5IOE1 `IO3`, frontlight is M5PM1 `G3` |
-| Frontlight + deep sleep | ❌ mutually exclusive | The boost rail is L3B; sleeping drops below it |
-| Frontlight + [battery life](battery-and-charging.md) | ⚠ unquantified | An always-on LED string on a 1150 mAh cell. No measurement exists |
-| Frontlight + other M5PM1 PWM users | ⚠ shared frequency | The M5PM1's `PWM_FREQ` register is **global to both its PWM channels** — you cannot give the frontlight 20 kHz and another channel 1 kHz |
-| Frontlight PWM + M5PM1 I²C idle-sleep | ⚠ | M5Stack documents that I²C idle sleep is disabled while PWM is enabled on the companion M5IOE1; the M5PM1 manual carries the same restriction |
-
-## 8. Debugging
-
-| Symptom | Cause |
-|---|---|
-| No light at any brightness | Not in state L3B; or `M5.begin()` was skipped; or the M5PM1 is unreachable on I²C |
-| **Screen went blank when you changed brightness** | You wrote **M5IOE1 `IO3`** instead of M5PM1 `G3`. You cut the panel rail |
-| Brightness "feels wrong" in the low half | The squared curve (§5.1) |
-| Audible whine | 5 kHz PWM below the AW9967's rated range (§5.2). Unconfirmed on hardware |
-| Brightness changes but never reaches full | 12-bit duty; check you are writing both duty bytes together |
-
-## 9. Alternatives
-
-There are none. The frontlight has exactly one control path — M5PM1 `G3` → AW9967 — and
-no host GPIO reaches it. Your only choices are *how* you drive that PWM (M5GFX's curve,
-or your own register writes).
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; frontlight is fitted on both C153 and C153-LITE |
-| Framework range | M5Unified 0.2.21 · M5GFX 0.2.28 · M5PM1 library 1.0.7 |
-| Evidence | Wiring: **schematic**, `executed-success` extraction. M5GFX behaviour: **read from source** at `M5GFX.cpp:819–856`. Code sketch: **`inferred`**, and one identifier explicitly unverified |
-| Confidence | High on the signal path; **medium on the API sketch**; low on anything electrical |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../power-architecture.md#frontlight`](../power-architecture.md#frontlight) · [`../pin-naming-and-the-pyg-ambiguity.md`](../pin-naming-and-the-pyg-ambiguity.md)
-- [`epaper-display.md`](epaper-display.md) · [`power-and-sleep.md`](power-and-sleep.md) · [`io-expander.md`](io-expander.md)
-- [`components/awinic/aw9967`](../../../../components/awinic/aw9967/README.md) · [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md)
diff --git a/devices/m5stack/papermono/features/imu.md b/devices/m5stack/papermono/features/imu.md
deleted file mode 100644
index a42d460..0000000
--- a/devices/m5stack/papermono/features/imu.md
+++ /dev/null
@@ -1,207 +0,0 @@
-# IMU — M5Stack PaperMono
-
-> **How do I read motion, and how do I wake the board on it?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-**This guide is short.** Reading the IMU is ordinary; the one PaperMono-specific fact —
-that its interrupt goes to the power manager rather than the ESP32-S3 — is the whole
-point, and the vendor's own prose gets its polarity wrong.
-
-## 1. Capability summary and the hardware path
-
-A Bosch six-axis IMU on the shared system I²C bus, powered from the **L1** rail so it
-stays alive in a state where the application processor does not.
-
-```
-BMI270 (I2C 0x68, alt 0x69)
-   ├─ SDA/SCL ──▶ system I²C bus (GPIO47/48), clocked at 100 kHz for this device
-   ├─ INT1 ─────▶ PYG4_IMU_INT ──▶ M5PM1 pin 12 (G4)     <- NOT the ESP32-S3
-   └─ VDD   ◀─── 3V3_L1 (SSP7615-33DFR U6), enabled by M5PM1 LDO3V3_EN_PP
-```
-
-| Element | Part | Record |
-|---|---|---|
-| IMU | Bosch Sensortec **BMI270**, `0x68` (alt `0x69`) | [`components/bosch-sensortec/bmi270`](../../../../components/bosch-sensortec/bmi270/README.md) |
-| Interrupt destination | **M5PM1 `G4`** | [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) · [`power-and-sleep.md`](power-and-sleep.md) |
-
-## 2. ⚠ INT1 lands on the power manager, not the ESP32-S3
-
-There is **no path from the BMI270 to any ESP32-S3 GPIO**. If you configure
-`esp_sleep_enable_ext0_wakeup()` on a pin expecting a motion interrupt, nothing will ever
-arrive.
-
-That is not an oversight — it is the design. It is what allows the board to be woken by a
-motion event **while the ESP32-S3 has no power at all** (state L1). The shipped factory
-binary carries the confirming log line:
-
-```
-PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge
-```
-
-## 3. ⚠ The interrupt is active-**low**; vendor prose says otherwise and is wrong
-
-| Source | Says |
-|---|---|
-| Vendor prose, power-management page §1 | *"Rotating the device then triggers the **active-high** IMU interrupt to wake the M5PM1"* |
-| Vendor **code** on the same page | `intPinConfig.pin_cfg[0].lvl = BMI2_INT_ACTIVE_LOW;` and `pm1.gpioSetWakeEdge(M5PM1_GPIO_NUM_4, M5PM1_GPIO_WAKE_FALLING)` |
-| Vendor code comment, second sketch | `// active - low` |
-| Vendor narrative, end of §4 | *"maps the interrupt to **active-low** INT1"* |
-| **Shipped binary** | `PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge` |
-
-**Four sources say active-low; one prose sentence says active-high.** The prose is the sole
-outlier and it is wrong. Resolved in
-[`../gaps-and-conflicts.md` R3](../gaps-and-conflicts.md#r3--bmi270-interrupt-polarity--resolved-against-the-vendor-prose).
-
-Use **`BMI2_INT_ACTIVE_LOW`** and **`M5PM1_GPIO_WAKE_FALLING`**.
-
-## 4. Prerequisites
-
-| Item | Value |
-|---|---|
-| Reading motion | **M5Unified `M5.Imu`** — `imu.begin(&M5.In_I2C, M5.getBoard())`, `imu.update()`, `imu.getType()` (`hal_imu.cpp:23–40`) |
-| Configuring wake | **SparkFun BMI270 Arduino Library** — `https://github.com/sparkfun/SparkFun_BMI270_Arduino_Library`, which is what the vendor's published wake sketch uses. **Not an M5Stack library** |
-| Also pinned by the firmware | `Arduino_BMI270_BMM150` **1.2.3**, commit `a599119044554015e06735f9d7187fc56295b9b6`, patched — a *third* BMI270 driver in the same ecosystem |
-| M5PM1 | 1.0.7 |
-
-> Three different BMI270 drivers appear across M5Stack's own material: M5Unified's
-> internal one, SparkFun's (in the published wake example), and `Arduino_BMI270_BMM150`
-> (pinned in the factory firmware). They are not interchangeable. Pick one per project.
-
-## 5. Resources consumed
-
-| Resource | Value |
-|---|---|
-| I²C address | **`0x68`**, probed also at **`0x69`** (`app_sleep_wake.cpp:59–60`) |
-| I²C speed | **100 kHz** for this device (`BMI270_I2C_FREQ_HZ = 100000`) — notably slower than the RTC and NFC at 400 kHz |
-| M5PM1 pin | `G4`, input, pull-up, wake-enabled, falling edge |
-| ESP32-S3 GPIO | **none** |
-| Rail | `3V3_L1` — alive in state **L1** and above |
-
-## 6. Minimal procedures
-
-### 6.1 Reading motion (`inferred`)
-
-```cpp
-#include <M5Unified.h>
-
-void setup() {
-  M5.begin(M5.config());
-  // M5Unified brings the IMU up itself; hal_imu.cpp retries begin() and update()
-}
-
-void loop() {
-  M5.update();
-  if (M5.Imu.update()) {
-    auto d = M5.Imu.getImuData();
-    // d.accel.x/y/z, d.gyro.x/y/z
-  }
-}
-```
-
-### 6.2 Wake on motion with the ESP32-S3 unpowered (`reported-working` as a vendor fragment)
-
-The load-bearing lines, from M5Stack's own power-management page. Full sequence and the
-`ldoSetPowerHold` rationale are in
-[`power-and-sleep.md` §6.2](power-and-sleep.md#62-shut-down-and-wake-on-motion-keeping-l1-alive).
-
-```cpp
-Wire1.setPins(M5.getPin(m5::pin_name_t::in_i2c_sda), M5.getPin(m5::pin_name_t::in_i2c_scl));
-pm1.begin(&M5.In_I2C, M5PM1_DEFAULT_ADDR, M5PM1_I2C_FREQ_100K);
-pm1.gpioSetWakeEnable(M5PM1_GPIO_NUM_4, true);
-pm1.gpioSetWakeEdge  (M5PM1_GPIO_NUM_4, M5PM1_GPIO_WAKE_FALLING);   // active-low
-pm1.setSingleResetDisable(false);
-
-while (imu.beginI2C(BMI2_I2C_PRIM_ADDR, Wire1) != BMI2_OK) { /* retry */ }
-imu.disableFeature(BMI2_ANY_MOTION);
-/* ... tune any-motion ... */
-bmi2_int_pin_config intPinConfig;
-intPinConfig.pin_type              = BMI2_INT1;
-intPinConfig.int_latch             = BMI2_INT_NON_LATCH;
-intPinConfig.pin_cfg[0].lvl        = BMI2_INT_ACTIVE_LOW;      // <- not active-high
-intPinConfig.pin_cfg[0].od         = BMI2_INT_PUSH_PULL;
-intPinConfig.pin_cfg[0].output_en  = BMI2_INT_OUTPUT_ENABLE;
-intPinConfig.pin_cfg[0].input_en   = BMI2_INT_INPUT_DISABLE;
-imu.setInterruptPinConfig(intPinConfig);
-imu.mapInterruptToPin(BMI2_ANY_MOTION_INT, BMI2_INT1);
-
-pm1.setLdoEnable(true);      // keep L1 alive across shutdown
-pm1.ldoSetPowerHold(true);
-pm1.setLedEnLevel(true);
-pm1.shutdown();
-```
-
-Any-motion tuning constants, quoted from the vendor's own commented-out code:
-`any_motion.threshold` 1 LSB = **0.48 mg** (default 83 mg); `any_motion.duration`
-1 LSB = **20 ms** (default 100 ms).
-
-### 6.3 Chained wake — M5PM1 stays awake and routes the IRQ to the host
-
-If you want the M5PM1 alive and the ESP32-S3 woken by it rather than shut down:
-
-```cpp
-pm1.irqClearGpioAll(); pm1.irqClearSysAll(); pm1.irqClearBtnAll();
-pm1.irqSetGpioMaskAll(M5PM1_IRQ_MASK_ENABLE);
-pm1.irqSetGpioMask(M5PM1_IRQ_GPIO4, M5PM1_IRQ_MASK_DISABLE);   // unmask GPIO4
-pm1.gpioSetMode(M5PM1_GPIO_NUM_4, M5PM1_GPIO_MODE_INPUT);
-pm1.gpioSetPull(M5PM1_GPIO_NUM_4, M5PM1_GPIO_PULL_UP);
-
-pm1.gpioSetMode (M5PM1_GPIO_NUM_1, M5PM1_GPIO_MODE_OUTPUT);
-pm1.gpioSetDrive(M5PM1_GPIO_NUM_1, M5PM1_GPIO_DRIVE_PUSHPULL);
-pm1.gpioSetFunc (M5PM1_GPIO_NUM_1, M5PM1_GPIO_FUNC_IRQ);       // -> ESP32-S3 GPIO1
-
-pinMode(GPIO_NUM_1, INPUT_PULLUP);
-attachInterrupt(GPIO_NUM_1, pm1_irq_handler, FALLING);
-// or: esp_sleep_enable_ext0_wakeup(GPIO_NUM_1, 0); rtc_gpio_pullup_en(GPIO_NUM_1);
-```
-
-Note that `M5.Power.deepSleep(us, touch_wakeup=true)` **replaces** GPIO1 with GPIO4 as the
-EXT0 pin — so this pattern and touch wake are mutually exclusive on one call. See
-[`touch.md` §6](touch.md#6-wake-on-touch).
-
-## 7. Limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (BMI270)** | 6-axis accel + gyro. No magnetometer on this board — the `BMM150` half of the pinned `Arduino_BMI270_BMM150` library has nothing to talk to |
-| **Board** | INT1 goes only to the M5PM1 (§2) |
-| **Board** | Runs at **100 kHz** on a bus whose other devices run at 400 kHz |
-| **Documentation** | The vendor prose has the interrupt polarity backwards (§3) |
-| **Documentation** | The M5Stack-mirrored BMI270 datasheet is **five years behind Bosch's** current revision — use Bosch's |
-| **Observed** | Nothing. No orientation-detection, drift or calibration report exists for this board |
-
-## 8. Conflicts
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| IMU + [RTC](rtc.md) wake | ✅ | Different M5PM1 GPIOs — `G4` and `G0`. Both can be enabled |
-| IMU + [touch](touch.md) wake | ⚠ different levels | IMU wakes from L1; touch only from L2 |
-| IMU + other I²C devices | ✅ addresses distinct | But the 100 kHz requirement means IMU transactions are slower |
-| IMU + [sleep](power-and-sleep.md) | ✅ the intended pattern | Needs `setLdoEnable(true)` + `ldoSetPowerHold(true)` |
-| IMU + `M5.Power.deepSleep(touch_wakeup=true)` | ❌ chained path lost | §6.3 |
-| IMU + charger on the bus | ⚠ | The general I²C hazard applies |
-
-## 9. Debugging
-
-| Symptom | Cause |
-|---|---|
-| Wake-on-motion never fires | Wrong polarity — you used the prose's active-**high** (§3); or you configured wake on an ESP32-S3 pin (§2) |
-| IMU disappears after shutdown | L1 not held: `ldoSetPowerHold(true)` |
-| Not found at `0x68` | Try `0x69`; the firmware probes both |
-| Erratic reads | Bus speed — this device wants 100 kHz |
-| Wake fires constantly | `any_motion.threshold` too low; 1 LSB = 0.48 mg |
-| Two BMI270 libraries fight | Pick one (§4) |
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; the BMI270 is fitted on both C153 and C153-LITE |
-| Framework range | M5Unified 0.2.21 · M5PM1 1.0.7 · SparkFun BMI270 library (unpinned by the vendor) · `Arduino_BMI270_BMM150` 1.2.3 in the factory build |
-| Evidence | Wiring: **schematic**. Polarity: **code + shipped binary**, three-way corroborated. Wake sketch: **`reported-working`** (vendor-published), `not-tested` here |
-| Confidence | High on the interrupt path and polarity; **none on sensor behaviour** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`power-and-sleep.md`](power-and-sleep.md) · [`rtc.md`](rtc.md) · [`touch.md`](touch.md) · [`../power-architecture.md`](../power-architecture.md)
-- [`components/bosch-sensortec/bmi270`](../../../../components/bosch-sensortec/bmi270/README.md) · [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md)
diff --git a/devices/m5stack/papermono/features/io-expander.md b/devices/m5stack/papermono/features/io-expander.md
deleted file mode 100644
index cd706fd..0000000
--- a/devices/m5stack/papermono/features/io-expander.md
+++ /dev/null
@@ -1,271 +0,0 @@
-# I/O expander (M5IOE1) — M5Stack PaperMono
-
-> **How do I use the expander, and how do I avoid the two numbering traps that will
-> silently target the wrong pin?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-> ## ⚠ Read this first
->
-> Two independent off-by-one hazards meet on this chip:
->
-> 1. **`M5IOE1_PIN_3 = 2`** — the label is 1-based, the enum value is 0-based. Passing a
->    documentation `PYG<n>` straight into the API reaches pin **n+1**.
-> 2. **`PYG3` denotes an M5IOE1 pin *and* an M5PM1 net**, and they are different signals.
->    Intending frontlight brightness and writing M5IOE1 `IO3` **cuts power to the e-paper
->    panel**, silently.
->
-> **[`../pin-naming-and-the-pyg-ambiguity.md`](../pin-naming-and-the-pyg-ambiguity.md) is
-> required reading before you write to this chip.**
-
-## 1. Capability summary and why it is not optional
-
-The M5IOE1 is a custom M5Stack part — the **same `PY32L020F15U6` silicon as the
-[M5PM1](../../../../components/m5stack/m5pm1/README.md)**, running different firmware —
-offering 14 GPIOs, four 12-bit ADC channels, four PWM channels, a NeoPixel driver, a die
-temperature sensor and 32 bytes of retention RAM, on I²C `0x4F`.
-
-On the PaperMono it is a load-bearing structural element, not a convenience. Behind it
-sit:
-
-| Function | Pin | Guide |
-|---|---|---|
-| microSD card detect | `IO1` | [`microsd.md`](microsd.md) |
-| LoRa antenna switch | `IO2` | [`lora.md`](lora.md) |
-| **E-paper 3.3 V rail enable** | `IO3` | [`epaper-display.md`](epaper-display.md) |
-| NFC power enable | `IO4` | [`nfc.md`](nfc.md) |
-| E-paper reset | `IO5` | [`epaper-display.md`](epaper-display.md) |
-| Touch reset | `IO6` | [`touch.md`](touch.md) |
-| Own I²C address select (`ADD_SET`) | `IO7` | §4 |
-| RGB green (PWM2) | `IO8` | [`buttons-and-rgb-led.md`](buttons-and-rgb-led.md) |
-| RGB blue (PWM1) | `IO9` | idem |
-| LoRa reset | `IO10` | [`lora.md`](lora.md) |
-| **IP2315 charger I²C bus gate** | `IO11` | [`battery-and-charging.md`](battery-and-charging.md) |
-| Microphone power enable | `IO12` | [`microphone.md`](microphone.md) |
-| Touch power enable | `IO13` | [`touch.md`](touch.md) |
-| microSD power enable | `IO14` | [`microsd.md`](microsd.md) |
-
-**Losing I²C means losing the ability to power-cycle the display.**
-
-Component record: [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md).
-Interrupt output `OD_INTOUT` → ESP32-S3 **GPIO7**.
-
-## 2. ⚠ Trap 1: `M5IOE1_PIN_3 = 2`
-
-`M5IOE1/src/M5IOE1.h:31–45`:
-
-```c
-M5IOE1_PIN_NC = -1,
-M5IOE1_PIN_1  = 0,
-M5IOE1_PIN_2  = 1,
-M5IOE1_PIN_3  = 2,     // <-- M5IOE1.h:34
-...
-M5IOE1_PIN_14 = 13,
-```
-
-Compare the companion chip, `M5PM1/src/M5PM1.h:410`:
-
-```c
-M5PM1_GPIO_NUM_3 = 3,   // label equals value
-```
-
-**Two custom chips on one board with opposite label↔value conventions**, and nothing in
-any vendor document says so.
-
-So: documentation label `PYG3` = manual pin `IO3` = enum `M5IOE1_PIN_3` = **raw value 2**
-= **register bit 2**. Passing the literal `3` where the enum was expected targets `IO4` —
-on this board, that swaps *e-paper power enable* for *NFC power enable*.
-
-There is also **no `M5IOE1_PIN_0`**. `M5IOE1.h` defines `_1 … _14` and
-`M5IOE1_MAX_GPIO_PINS 14`. A documentation reference to `PYG0` (e.g. `PYG0_RTC_INT`)
-**cannot** denote an M5IOE1 pin under any reading — it is an M5PM1 pin the docs
-mislabelled with the expander's prefix.
-
-### The three ways vendor code sidesteps it
-
-| Style | Example | Note |
-|---|---|---|
-| **Library enum** — the safe form | `ioe1.digitalWrite(M5IOE1_PIN_3, HIGH)` | Factory firmware. Use the constant, never a literal |
-| **Raw zero-based values** | `ioe.digitalWrite(2, true)` | Vendor OTP demo, with the explicit comment `// M5IOE1 uses zero-based pin indexes.` (`EDP_SPI.cpp:36–38`) |
-| **Raw register bit masks** | `lgfx::i2c::bitOn(port, 0x4F, 0x05, 0b00000100, freq)` | M5GFX (`M5GFX.cpp:2088–2096`). Avoids the enum entirely |
-
-A **fourth** naming system exists: M5Unified's own expander abstraction uses
-`M5IOE1_Class::gpio11`, which is *not* the M5IOE1 library's enum. Four naming systems for
-fourteen pins. Name the chip and the system every time.
-
-## 3. ⚠ Trap 2: outputs default to open-drain
-
-`GPIO_DRV_L = 0xFF`, `GPIO_DRV_H = 0x3F` at reset — **every** GPIO output defaults to
-open-drain, **including PWM and NeoPixel**. With no external pull-up, an "output" you set
-high does nothing.
-
-Both vendor paths handle it explicitly:
-
-```cpp
-ioe1.setDriveMode(TF_EN_PIN, M5IOE1_DRIVE_PUSHPULL);          // factory firmware
-ioe.setHighImpedance(IOE_EPD_ENABLE, false);                  // OTP demo / M5Unified
-lgfx::i2c::bitOff(port, 0x4F, 0x13, 0b00110100, freq);        // M5GFX, raw
-```
-
-A third related rule: **peripheral occupancy overrides the GPIO registers.** When a pin is
-claimed by ADC, PWM, I²C, SWD or NeoPixel, its `GPIO_M_x` / `GPIO_O_x` bits become
-inoperative.
-
-## 4. ⚠ The address is `0x4F`, and the chip's own manual disagrees
-
-Everything on this board — firmware, product page, M5GFX, M5Unified — uses **`0x4F`**.
-The M5IOE1 V1.4 manual states the address range **`0x6F`–`0x76`** in three separate
-places, the chip's `IO7` is genuinely wired to an `ADD_SET` divider, and the vendor
-library constant is named `M5IOE1_DEFAULT_ADDR_2` with an autodetect that sweeps
-**both** ranges (`M5IOE1.h:80–81`).
-
-Unresolved. Tracked as
-[`../gaps-and-conflicts.md` C4](../gaps-and-conflicts.md#c4--the-m5ioe1s-i²c-address-is-not-in-its-own-manual).
-Practically: use `M5IOE1_DEFAULT_ADDR` / `0x4F` and let the library autodetect if it
-fails. Note that `IO7` (`ADD_SET`) is **not listed on the vendor product page** — one of
-that page's only two omissions.
-
-## 5. Prerequisites
-
-| Item | Value |
-|---|---|
-| M5IOE1 library | **1.0.9** (registry `m5stack/m5ioe1`) |
-| M5Unified | 0.2.21 — brings the expander up during `M5.begin()` and exposes it as `M5.getIOExpander(0)` |
-| I²C | Shared bus GPIO47/48, brought up at **100 kHz** ("device default", per the shipped binary's own log string) |
-| Power state | The expander is on `3V3_L2`; it is alive whenever the ESP32-S3 is |
-
-## 6. Resources consumed
-
-| Resource | Value |
-|---|---|
-| I²C address | `0x4F` on the shared bus |
-| ESP32-S3 GPIO | **GPIO7** — `OD_INTOUT`. **The factory firmware does not use it** (`M5IOE1_INT_MODE_DISABLED`, `hal_board.cpp:62`) and polls instead |
-| Free expander pins | **None.** All fourteen are assigned |
-| Unused capabilities | All four ADC channels, PWM3/PWM4 as PWM, the NeoPixel output, the temperature sensor, the retention RAM and the `AW8737A` pulse register are **all unexercised on this board** |
-
-Register map summary (full table in the [component record](../../../../components/m5stack/m5ioe1/README.md)):
-direction `0x03`/`0x04`, output `0x05`/`0x06`, input `0x07`/`0x08`, pull-up `0x09`/`0x0A`,
-pull-down `0x0B`/`0x0C`, interrupt enable/polarity/status `0x0D`–`0x12`, drive
-`0x13`/`0x14`, ADC `0x15`–`0x17`, temperature `0x18`–`0x1A`, PWM duty `0x1B`–`0x22`,
-I²C config `0x23`, LED config `0x24`, PWM frequency `0x25`/`0x26`. Low byte covers P8–P1,
-high byte P14–P9 in `[5:0]`.
-
-## 7. Minimal procedure (`inferred`)
-
-```cpp
-#include <M5Unified.h>
-#include <M5IOE1.h>
-
-M5IOE1 ioe1;
-
-void setup() {
-  M5.begin(M5.config());                       // M5Unified already owns the expander
-
-  ioe1.begin(&M5.In_I2C, M5IOE1_DEFAULT_ADDR, M5IOE1_I2C_FREQ_100K, M5IOE1_INT_MODE_DISABLED);
-
-  ioe1.pinMode(M5IOE1_PIN_4, OUTPUT);                       // NFC enable
-  ioe1.setDriveMode(M5IOE1_PIN_4, M5IOE1_DRIVE_PUSHPULL);   // <- do not skip
-  m5ioe1_err_t err = M5IOE1_OK;
-  ioe1.digitalWriteWithRes(M5IOE1_PIN_4, HIGH, &err);
-  if (err != M5IOE1_OK) { /* on the real board this means "probably a Lite" - see §9 */ }
-}
-```
-
-API names are transcribed from the factory firmware and the vendor's published examples:
-`begin`, `pinMode`, `setDriveMode`, `setPullMode`, `digitalWrite`,
-`digitalWriteWithRes`, `digitalRead`, `digitalReadWithRes`, `setPwmFrequency`,
-`setPwmDuty12bit`, `setDirection`, `setHighImpedance`, `setLogLevel`.
-
-## 8. ⚠ M5Unified already owns most of these pins
-
-M5Stack's own warning, verbatim:
-
-> "The pins associated with the e-paper display, touch controller, microSD, and PDM
-> microphone are **already used by M5Unified**. Before modifying them, ensure that the
-> corresponding peripheral has stopped, or the peripheral may stop working or require
-> reinitialization."
-
-That covers `IO3`, `IO5`, `IO6`, `IO12`, `IO13`, `IO14` — six of the fourteen. Add
-`IO11` (charger gate, owned by `M5.Power`) and there are only seven pins M5Unified is not
-already driving, all of which belong to LoRa, NFC or the LED.
-
-**There is no spare expander pin on this board**, just as there is no spare GPIO.
-
-## 9. The expander is the Pro-vs-Lite discriminator
-
-`hal_board.cpp:160–172` — the factory firmware decides which SKU it is running on by
-trying to drive `IO4` (NFC enable) and watching for an error:
-
-```cpp
-void Hal::detectBoardVariant() {
-    if (!_rgb_ready) { _board_variant = BoardVariant::Lite; return; }
-    m5ioe1_err_t err = M5IOE1_OK;
-    ioe1.digitalWriteWithRes(NFC_EN_PIN, HIGH, &err);
-    if (err != M5IOE1_OK) { _board_variant = BoardVariant::Lite; return; }
-}
-```
-
-combined with an NFC identity read (register `0x7F`, expected type `0x05`).
-
-**M5GFX cannot distinguish Pro from Lite** — both map to the single enum
-`board_M5PaperMono`, with NFC masked out of the detection test (`M5GFX.cpp:1945`). Only
-the application layer can tell.
-
-## 10. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Firmware (M5IOE1)** | Off-by-one enum (§2); open-drain default (§3); address disagreement with its own manual (§4) |
-| **Firmware (M5IOE1)** | Interrupt exclusion groups — interrupts cannot be enabled simultaneously within `IO1&IO6`, `IO2&IO3`, `IO7&IO12`, `IO8&IO9`, `IO10&IO14`, `IO11&IO13`. **`IO2&IO3` and `IO11&IO13` both straddle live PaperMono signals** |
-| **Firmware (M5IOE1)** | One shared `PWM_FREQ` register for all four PWM channels; I²C idle-sleep is disabled outright while PWM is enabled |
-| **Board** | All 14 pins assigned. No expansion header |
-| **Framework** | Four different pin-naming systems (§2) |
-| **Framework** | The factory firmware **polls** rather than using `OD_INTOUT`; the GPIO7 interrupt path is therefore **unexercised by any vendor code** |
-| **Observed** | Nothing. No hardware report exists about expander behaviour on this board |
-
-## 11. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Expander + everything | ⚠ **it is the single point of failure** | Panel, touch, SD, mic, NFC, LoRa and charger access all route through it |
-| Interrupt on `IO11` + interrupt on `IO13` | ❌ | Documented exclusion pair — charger gate vs touch power |
-| Interrupt on `IO2` + interrupt on `IO3` | ❌ | LoRa antenna switch vs e-paper rail |
-| PWM on green (`IO8`) + PWM on blue (`IO9`) | ✅ *probably* | The documented exclusion for this pair is on **interrupts**, not PWM. M5Unified nonetheless PWMs only green. See [`buttons-and-rgb-led.md`](buttons-and-rgb-led.md) |
-| Expander + charger gate held open | ⚠ | The one documented bus-stability hazard |
-| Expander + M5Unified-owned pins | ⚠ | §8 — stop the peripheral first |
-
-## 12. Debugging
-
-| Symptom | Cause |
-|---|---|
-| **Screen went blank when you changed something unrelated** | You wrote `IO3`. §2 or the `PYG3` ambiguity |
-| NFC stopped working when you meant to touch the display rail | Off-by-one: you passed a literal and hit `IO4` |
-| An output does nothing | Still open-drain (§3) |
-| `0x4F` not found | Try the library autodetect; the manual claims `0x6F`–`0x76` (§4) |
-| A peripheral dies after you drive "its" expander pin | M5Unified owns it (§8) |
-| `digitalWriteWithRes` returns an error on a Pro | You are probably on a Lite (§9) |
-| Interrupt on GPIO7 never fires | The chip defaults to polling in vendor code; and `INT_OUT` is **open-drain and needs a pull-up** |
-
-## 13. Unresolved questions
-
-- **The manual's `0x6F`–`0x76` address range vs the board's `0x4F`** (§4).
-- **`PYB_NFC_EN` is annotated "spare GPIO"** on schematic sheet 4 while the firmware uses
-  it as the NFC enable. Likely a stale annotation; unresolved.
-- Whether the GPIO7 interrupt path works at all on this board — **no vendor code exercises
-  it**.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**. Fitted on both C153 and C153-LITE; `IO2`/`IO4`/`IO10` are unused on the Lite |
-| Framework range | M5IOE1 1.0.9 · M5Unified 0.2.21 · M5GFX 0.2.28 |
-| Evidence | Pin map: **schematic + firmware, cross-confirmed**. Off-by-one: **`M5IOE1.h:34`**, `executed-success` read. Register map: **vendor manual V1.4**. Sketch: **`inferred`** |
-| Confidence | High. This is the best-evidenced part of the board — three independent sources agree on the pin map |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pin-naming-and-the-pyg-ambiguity.md`](../pin-naming-and-the-pyg-ambiguity.md) — **read before writing to this chip**
-- [`../pinouts-and-buses.md#m5ioe1-expander-pins`](../pinouts-and-buses.md#m5ioe1-expander-pins) · [`../resources-and-conflicts.md`](../resources-and-conflicts.md)
-- [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) · [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) · [`components/puya/py32l020f15u6`](../../../../components/puya/py32l020f15u6/README.md)
-- [`vendors/m5stack`](../../../../vendors/m5stack/README.md) — where the M5IOE1 datasheet lives, including the Chinese-only edition
diff --git a/devices/m5stack/papermono/features/lora.md b/devices/m5stack/papermono/features/lora.md
deleted file mode 100644
index 7e6fb16..0000000
--- a/devices/m5stack/papermono/features/lora.md
+++ /dev/null
@@ -1,304 +0,0 @@
-# LoRa — M5Stack PaperMono
-
-> **Common guide:** [`guides/lora`](../../../../guides/lora/README.md) holds the device-independent LoRa material — standards, silicon choice, antenna and matching, libraries and debugging.
->
-> **Applicability:** the standard approach **applies with deltas**. On this board reset and antenna-switch control run through the M5IOE1 I/O expander, the `3V3_L2_LoRa` rail is enabled by the M5PM1 power-management MCU, **no datasheet exists for the Stamp LoRa-1262 module**, and the vendor firmware selects **LDO regulation**, which roughly doubles receive current.
-
-> **How do I send and receive a LoRa packet?**
-> Hardware revision **V0.6.2** (SKU **C153 only** — not fitted on the Lite) ·
-> snapshot **2026-09-01** · nothing tested on hardware.
-
-> **Regional band configuration is a documented gap.** One wideband 868–923 MHz SKU, no
-> per-region variant, **no module datasheet anywhere**, and **no published certification
-> of any kind**. §7 says what that means; the guide is deliberately short there rather
-> than inventing regional guidance.
-
-## 1. Capability summary and the hardware path
-
-A plug-in `Stamp-LoRa-1262-mini` module carrying a Semtech SX1262, on its own SPI bus,
-with its power rail switched by the [power manager](power-and-sleep.md) and its reset and
-antenna switch behind the [I/O expander](io-expander.md).
-
-```
-ESP32-S3 ──SPI3_HOST──▶ Stamp-LoRa-1262 (U14, 13-pin) ──▶ FPC antenna
-   GPIO38 MOSI, GPIO39 SCK, GPIO40 MISO, GPIO41 NSS
-   GPIO21 ◀── BUSY
-   GPIO5  ◀── DIO1 / LORA_IRQ
-                   ▲ SX_NRST   ◀── M5IOE1 IO10
-                   ▲ SX_ANT_SW ◀── M5IOE1 IO2
-                   ▲ VIN_3V3   ◀── 3V3_L2_LoRa (SSP7615-33DFR U9), enabled by M5PM1 G2
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Module | M5Stack `Stamp-LoRa-1262-mini`, designator `U14` | [`components/m5stack/stamp-lora-1262`](../../../../components/m5stack/stamp-lora-1262/README.md) |
-| Radio | Semtech **SX1262** | (module-internal) |
-| Rail enable | **M5PM1 `G2`** (`PYG2_LoRa_EN`) | [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) |
-| Reset / antenna switch | M5IOE1 `IO10` / `IO2` | [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) |
-| Antenna | built-in FPC | vendor spec; no part identified |
-
-> **Bus naming.** The schematic net names say `SPI1` (`G38_SPI1_MOSI` etc.), but the
-> firmware opens **`SPI3_HOST`** (`hal_lora.cpp:22`). Both are correct in their own
-> namespace — the schematic labels are M5Stack's, `SPI3_HOST` is ESP-IDF's. The e-paper's
-> `SPI2` labels happen to coincide with `SPI2_HOST`, which makes the LoRa mismatch easy
-> to miss. Recorded because it will confuse anyone reading the two side by side.
-
-## 2. Prerequisites and exact versions
-
-| Item | Value | Note |
-|---|---|---|
-| **RadioLib** | **7.2.1**, commit `b91c6af112e423dcb14529ade5827802a14e1015` | What the factory firmware pins |
-| RadioLib in the published PlatformIO snippet | **unpinned** — `https://github.com/jgromes/RadioLib` | ⚠ pulls `master`, not 7.2.1 |
-| M5PM1 / M5IOE1 | 1.0.7 / 1.0.9 | Needed for the rail and reset |
-| ESP-IDF | 5.5.1 | |
-
-> The vendor's own build **patches RadioLib to remove `idf_component.yml`** so it builds
-> as a plain component rather than a managed one. If you are reproducing factory
-> behaviour, use the pinned commit **and** expect that patch.
->
-> **Licence note, flagged not confirmed:** RadioLib is LGPL-3.0 upstream while the M5Stack
-> demo carrying it is MIT. Not verified in this pass.
-
-There is **no M5Stack-specific LoRa library**. `hal_lora.cpp` is a thin wrapper that
-implements a `RadioLibHal` over ESP-IDF SPI/GPIO and hands six pin numbers to RadioLib.
-
-## 3. Resources consumed
-
-| Resource | Value |
-|---|---|
-| ESP32-S3 GPIO | **six**: GPIO38, 39, 40, 41 (SPI), GPIO21 (`BUSY`), GPIO5 (`DIO1`) |
-| SPI host | **`SPI3_HOST`**, **8 MHz** (`LORA_SPI_FREQ_HZ = 8000000`) |
-| Series resistor | 22 Ω on SCK (`R34`) |
-| Expander pins | `IO10` reset, `IO2` antenna switch |
-| M5PM1 pin | `G2`, rail enable |
-| Rail | `3V3_L2_LoRa`, an SSP7615-33DFR LDO rated 400 mA |
-| Interrupt | GPIO5, `GPIO_INTR_POSEDGE` in the vendor's RadioLibHal |
-
-## 4. Bring-up order matters
-
-The module has a **hard power cut** independent of the SX1262's own sleep modes. Nothing
-in the vendor documentation states the ordering explicitly; it follows from the wiring
-and is exactly what the factory firmware does (`hal_lora.cpp:299–319`):
-
-1. **M5PM1 `G2` → output high** — power the module.
-2. **M5IOE1 `IO2` (antenna switch) → output, push-pull, HIGH.**
-3. **M5IOE1 `IO10` (`SX_NRST`) → output, push-pull, LOW → `delay(100)` → HIGH →
-   `delay(20)`.**
-4. Only then open SPI and call RadioLib.
-
-Skipping step 1 or 3 gives you a radio that appears absent. Both steps require a working
-I²C bus.
-
-## 5. The vendor's exact radio configuration
-
-`hal_lora.cpp:32–43` and `:333–344`. `executed-success` on the read; `not-tested`.
-
-| Parameter | Value |
-|---|---|
-| Frequency | **868.0 MHz** |
-| Bandwidth | **62.5 kHz** |
-| Spreading factor | **12** |
-| Coding rate | **8** (4/8) |
-| Sync word | **`0x34`** |
-| TX power | **22 dBm** |
-| Preamble | 10 symbols |
-| **TCXO voltage** | **3.0 V** |
-| Regulator | **LDO** (`useRegulatorLDO = true`) |
-| Current limit | **140 mA** |
-| Max packet | 255 bytes |
-| `setDio2AsRfSwitch` | **true** |
-
-```cpp
-radio.begin(868.0f, 62.5f, 12, 8, 0x34, 22, 10, 3.0f, true);
-radio.setDio2AsRfSwitch(true);
-radio.setCurrentLimit(140.0f);
-radio.setPacketReceivedAction(loraSetRxFlag);
-radio.startReceive();
-```
-
-> **This partially resolves an open question in the module record.** The
-> [Stamp-LoRa-1262 record §5 G3](../../../../components/m5stack/stamp-lora-1262/README.md)
-> records TCXO-vs-XTAL as unknown, and warns that getting it wrong produces a radio that
-> initialises and then fails to transmit. The vendor firmware passes
-> **`tcxoVoltage = 3.0f`**, which in RadioLib configures `DIO3` as a **3.0 V TCXO
-> supply**. So the module almost certainly fits a TCXO on `DIO3`. `inferred` from the
-> firmware, `not-tested` — but it is the value to start from, and changing it blindly is
-> exactly the mistake the module record warns about.
->
-> `setDio2AsRfSwitch(true)` likewise says `DIO2` drives an internal RF switch. That is
-> *not* the same signal as `SX_ANT_SW` on M5IOE1 `IO2`, whose semantics remain
-> undocumented (module record G4) — the firmware sets it HIGH once and never touches it
-> again.
-
-Note this is a **very slow, very robust** configuration: SF12 at 62.5 kHz is on the order
-of a few tens of bits per second. It is a range demo, not a throughput default.
-
-## 6. Minimal procedure (`inferred`)
-
-```cpp
-// after the bring-up sequence in section 4:
-auto hal    = new PaperMonoRadioLibHal(GPIO_NUM_39, GPIO_NUM_40, GPIO_NUM_38);  // sck, miso, mosi
-auto module = new Module(hal, GPIO_NUM_41, GPIO_NUM_5, RADIOLIB_NC, GPIO_NUM_21);
-auto radio  = new SX1262(module);                        // NSS, DIO1, RST=NC, BUSY
-
-int st = radio->begin(868.0f, 62.5f, 12, 8, 0x34, 22, 10, 3.0f, true);
-if (st != RADIOLIB_ERR_NONE) { /* fail */ }
-radio->setDio2AsRfSwitch(true);
-radio->setCurrentLimit(140.0f);
-radio->setPacketReceivedAction(onRx);
-radio->startReceive();
-```
-
-**`RST` is passed as `RADIOLIB_NC`** — RadioLib never resets the module, because reset is
-an expander pin. You must do it yourself (§4).
-
-## 7. Regional bands, certification and legality — the honest position
-
-**This section is short because the evidence is thin, not because the topic is minor.**
-
-| Question | Answer |
-|---|---|
-| Band the SKU claims | **868 MHz – 923 MHz**, one wideband range |
-| Regional variants | **None.** One SKU, one default variant, both products |
-| What the firmware uses | **868.0 MHz**, hard-coded — the EU band |
-| Regional band plan support | **Not documented anywhere.** No LoRaWAN region table, no channel plan, no duty-cycle handling in any vendor code |
-| Certification | **None published.** `/en/certification` returns HTTP 200 with **zero** matches for `PaperMono` and `C153`. No FCC ID, CE, IC, RCM or TELEC/MIC identifier appears on any of the 13 documentation pages, either product page, or either store listing |
-| Module datasheet | **Does not exist in any form located.** M5Stack's datasheet list links the *Semtech chip* datasheet, not a module document |
-
-So: RF output power at the connector, antenna gain, the internal matching network, and
-the module's supply current are all **unknown**, and **there is no regulatory paperwork to
-point at**. A single wideband SKU spanning EU 868, US 915 and JP 920 allocations, with no
-per-region variant and no certification, is worth flagging to anyone intending to deploy
-the radio rather than experiment with it on a bench.
-
-Meshtastic/MeshCore support was raised as an open question in the largest community
-discussion of this board and **was not answered**. No LoRaWAN stack has been demonstrated
-on it.
-
-## 8. Limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (SX1262)** | 255-byte packets; TCXO configuration must match the module or the radio fails silently after apparently initialising |
-| **Board** | **LoRa is not fitted on the PaperMono-Lite.** The entire USD 10 price delta is NFC + LoRa |
-| **Board** | Reset and antenna switch behind I²C — **no I²C, no LoRa reset** |
-| **Board** | Rail enable behind the M5PM1 — **no I²C, no LoRa power** |
-| **Board** | Module pins 11–13 carry pad markers but **no printed name, no net label and no drawn no-connect glyph**. Recorded as *unlabelled*, which is not the same as *proven no-connect* |
-| **Framework** | RadioLib unpinned in the published config vs 7.2.1 pinned in the firmware |
-| **Observed** | **Nothing.** No range, throughput, sensitivity or current measurement exists from anyone |
-
-## 9. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| **LoRa + [Wi-Fi](wifi-and-bluetooth.md)** | ✅ **they do not share a radio** | LoRa is **sub-GHz, 868–923 MHz**, on a separate SX1262 with its own FPC antenna. Wi-Fi/BLE is **2.4 GHz** inside the ESP32-S3. Different bands, different antennas, different peripherals (`SPI3_HOST` vs the internal radio). There is no coexistence scheduling to do. What they *do* share is CPU time and the battery |
-| LoRa + [display](epaper-display.md) | ✅ | Separate SPI hosts — `SPI3_HOST` vs `SPI2_HOST` |
-| LoRa + [microSD](microsd.md) | ✅ | SD is SDMMC, not SPI |
-| LoRa + [NFC](nfc.md) | ✅ RF-wise | 13.56 MHz vs sub-GHz. Both need the shared I²C bus for their enables |
-| LoRa TX + [battery](battery-and-charging.md) | ⚠ unquantified | 22 dBm on a 400 mA LDO with a 140 mA current limit set in software. No measurement exists |
-| LoRa + [sleep](power-and-sleep.md) | ⚠ | Sheet 1 lists LoRa as an **L2 wake source**, but **no vendor firmware exercises that path**. Untested |
-| LoRa + expander interrupts on `IO2`/`IO3` | ❌ | Documented M5IOE1 interrupt exclusion pair — LoRa antenna switch vs e-paper rail |
-| LoRa + expander interrupts on `IO10`/`IO14` | ❌ | Same — LoRa reset vs microSD power |
-
-## 10. Debugging
-
-| Symptom | Cause |
-|---|---|
-| `begin()` returns an error | Rail not enabled (M5PM1 `G2`); or reset never released (M5IOE1 `IO10`); or the bring-up order was wrong (§4) |
-| Initialises, then never transmits or receives | **The classic TCXO mismatch.** Use `tcxoVoltage = 3.0f` as the firmware does; do not "simplify" it to 0 |
-| No interrupt on RX | GPIO5 `DIO1`; the vendor HAL registers `GPIO_INTR_POSEDGE` and skips registration entirely if the GPIO ISR service is not installed |
-| Works, but glacially | SF12 / BW 62.5 kHz is the vendor default (§5). Change it deliberately |
-| Different behaviour from the factory demo | The published PlatformIO snippet pulls RadioLib `master`, not 7.2.1 |
-| Radio disappears after a sleep cycle | The rail is M5PM1-owned; re-run the whole bring-up |
-
-## 11. Unresolved questions
-
-- **`SX_ANT_SW` semantics.** Whether it selects TX/RX paths, enables a PA/LNA, or switches
-  antenna connectors is stated nowhere. The firmware sets it HIGH and forgets it.
-- **Module pins 11–13.** Unlabelled.
-- **TCXO confirmed only by inference** from the firmware's `3.0f` (§5).
-- **No regional band plan, no certification, no module datasheet** (§7).
-- Whether LoRa genuinely works as an L2 wake source.
-
-
-## 12. Software that actually exists — added 2026-09-11
-
-Prior sweeps recorded **"zero LoRa implementations found"**. That was a
-search-term artifact: searching `papermono` rather than `lora` surfaces three
-working radios immediately.
-
-| Project | Stack | What it does |
-|---|---|---|
-| **`m5stack/M5PaperMono-UserDemo`** @ `c109910` | ESP-IDF + **RadioLib** | The factory demo. Full TX/RX app in `main/apps/app_lora/`; HAL in `main/hal/hal_lora.cpp` |
-| **`canardleteer/papermono-rs`** @ `67ee512` | Rust / Embassy, bare-metal SX1262 | Behind `--features c153`. Includes a **104-slot US915 channel energy sweeper** and a packet sniffer |
-| **`osprey74/Nostos`** @ `56acd5e` | Rust | **Receives Meshtastic traffic** — on-air header parse, AES-CTR decrypt, Position protobuf decode |
-
-### `Nostos` is the most interesting of the three
-
-`crates/nostos-meshtastic` implements a *custom* Meshtastic receiver — it is not
-Meshtastic firmware. Its radio config differs from the vendor's in every
-parameter:
-
-| | Factory demo | Nostos (Meshtastic RX) |
-|---|---|---|
-| Frequency | 868.0 MHz | **923.000 MHz** |
-| Bandwidth | 62.5 kHz | **125 kHz** |
-| Spreading factor | SF12 | **SF9** |
-| Coding rate | 4/8 | **4/5** |
-| Sync word | `0x34` | **`0x3A`** |
-
-That is a second, independently-chosen configuration on this exact hardware —
-useful as a cross-check that the bring-up sequence in §4 is not vendor-specific
-folklore.
-
-### Meshtastic upstream does **not** support this device
-
-`meshtastic/firmware` has **no PaperMono or M5Paper variant** (code search for
-`papermono` in that repo: 0 results). M5Stack devices that *are* supported
-include **`m5stack_coreink`** — an ESP32 e-paper device — plus `m5stack_core`,
-`cores3`, `cardputer_adv`, `unitc6l` and `stamp-c3`. The single `m5paper` hit is
-a URL in a comment in `variants/esp32/m5stack_coreink/variant.h:96`, pointing at
-the *old* M5Paper schematic.
-
-**Porting is feasible but not trivial.** Every pin is known and the SX1262 is a
-first-class Meshtastic radio — but `SX_NRST`, `SX_ANT_SW` and the rail enable all
-sit **behind two I²C chips**, whereas Meshtastic's variant system expects plain
-GPIOs. That indirection, not the radio, is the work.
-
-### Partial answer to the `SX_ANT_SW` question (§11)
-
-Still not *documented* anywhere, but the vendor HAL's own comment names the
-intent — `hal_lora.cpp:299-313` drives it HIGH during bring-up with the comment
-**"engage FPC antenna"**:
-
-```c
-ioe1.digitalWriteWithRes(LORA_ANT_SW_IOE1_PIN, HIGH, &ioe_err);  // engage FPC antenna
-ioe1.digitalWriteWithRes(LORA_RST_IOE1_PIN,    LOW,  &ioe_err);
-ioe1.digitalWriteWithRes(LORA_RST_IOE1_PIN,    HIGH, &ioe_err);  // release reset
-```
-
-So it is **an antenna-path enable for the onboard FPC antenna**, set once and
-left — consistent with "the firmware sets it HIGH and forgets it". Whether it
-additionally selects between TX/RX paths or gates a PA/LNA remains **unknown**;
-the comment is the vendor's, not a datasheet, and no module datasheet exists.
-
-`papermono-rs` documents the timings the vendor code leaves implicit:
-reset LOW → ant-sw HIGH → rail HIGH → **15 ms settle** → reset HIGH →
-**20 ms TCXO/boot settle**.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**, **SKU C153 only**. ❌ Not fitted on C153-LITE |
-| Framework range | RadioLib **7.2.1** (pinned) · ESP-IDF 5.5.1 · M5PM1 1.0.7 · M5IOE1 1.0.9 |
-| Evidence | Pin map: **schematic + firmware, cross-confirmed**. Radio parameters: **read from vendor source** at cited `file:line`, `executed-success`. TCXO: **`inferred`** from the firmware. Regional/regulatory: **verified negative** |
-| Confidence | High on wiring and the vendor's radio config; **none on RF performance or legality in any region** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md#spi-buses`](../pinouts-and-buses.md#spi-buses) · [`../power-architecture.md`](../power-architecture.md) · [`../resources-and-conflicts.md`](../resources-and-conflicts.md)
-- [`wifi-and-bluetooth.md`](wifi-and-bluetooth.md) · [`nfc.md`](nfc.md) · [`io-expander.md`](io-expander.md) · [`power-and-sleep.md`](power-and-sleep.md)
-- [`components/m5stack/stamp-lora-1262`](../../../../components/m5stack/stamp-lora-1262/README.md)
-- [**`guides/lora`**](../../../../guides/lora/README.md) — the device-independent companion to this page (see the applicability note at the top): SF/BW/CR against airtime and battery, LoRa vs LoRaWAN vs Meshtastic, regional band plans and duty cycle, `BUSY`/TCXO/RF-switch mechanics, and generic failure signatures. ⚠ Its §5.6 finds that **current RadioLib implements all four of Semtech's mandatory errata workarounds** — but that was verified on `master` (7.7.1), **not** on the **7.2.1** pinned here
diff --git a/devices/m5stack/papermono/features/microphone.md b/devices/m5stack/papermono/features/microphone.md
deleted file mode 100644
index 617939b..0000000
--- a/devices/m5stack/papermono/features/microphone.md
+++ /dev/null
@@ -1,204 +0,0 @@
-# Microphone — M5Stack PaperMono
-
-> **How do I record audio, and why do the pins matter more than usual?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-## 1. Capability summary and the hardware path
-
-A single PDM microphone on the KEY/RGB sub-board, read by the ESP32-S3's I²S peripheral
-in PDM RX mode, with its supply switched by the [I/O expander](io-expander.md).
-
-```
-LMD4737T261-AC02 (PDM mic)  ──DAT──▶ ESP32-S3 GPIO46
-                            ◀─CLK─── ESP32-S3 GPIO45
-                            ◀─VDD─── PDM_VDD, AW35122 load switch (U21), M5IOE1 IO12
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Microphone | `LMD4737T261-AC02` | [`components/generic/lmd4737t261-ac02-pdm-microphone`](../../../../components/generic/lmd4737t261-ac02-pdm-microphone/README.md) |
-| Power switch | Awinic `AW35122` (`U21`) | [`components/awinic/aw35122`](../../../../components/awinic/aw35122/README.md) |
-| Power enable | M5IOE1 `IO12` | [`io-expander.md`](io-expander.md) |
-| Connector | `J6` (16-pin B2B to the sub-board) | [`../pinouts-and-buses.md`](../pinouts-and-buses.md#connectors) |
-
-> **No datasheet for `LMD4737T261-AC02` exists.** The only web occurrences anywhere are
-> M5Stack's own pages. Sensitivity, SNR, AOP, frequency response, supply current and
-> supported clock range are all **unknown**. Nothing about audio quality can be stated
-> here.
-
-## 2. ⚠ Both microphone pins are ESP32-S3 strapping pins
-
-**GPIO45 and GPIO46 are strapping pins.** They are sampled at reset to select boot
-behaviour (`VDD_SPI` voltage and boot-message routing on the ESP32-S3), and here they
-carry the PDM clock and data.
-
-Consequences:
-
-- **Anything driving GPIO45 or GPIO46 across a reset perturbs the straps.** The vendor
-  firmware does not appear to guard against this. `inferred` from the pin map;
-  `not-tested`.
-- The microphone is a *data source* on GPIO46 and the ESP32-S3 drives the clock on
-  GPIO45, so in normal operation neither is driven by an external part during boot — but
-  the mic's own output stage is on GPIO46, and its state at reset depends on whether
-  `PDM_VDD` is up.
-- The factory firmware **explicitly releases both pins** before reconfiguring
-  (`hal_mic.cpp:56–62`):
-
-```c
-static void releaseMicPins() {
-    gpio_reset_pin(GPIO_NUM_46);
-    gpio_set_direction(GPIO_NUM_46, GPIO_MODE_INPUT);
-    gpio_set_pull_mode(GPIO_NUM_46, GPIO_FLOATING);
-    gpio_reset_pin(GPIO_NUM_45);
-}
-```
-
-That routine exists for a reason. Copy it.
-
-Note that GPIO3 (Button B) is a **third** strapping pin on this board — see
-[`usb-and-serial.md`](usb-and-serial.md) and
-[`buttons-and-rgb-led.md`](buttons-and-rgb-led.md).
-
-## 3. Prerequisites
-
-| Item | Value |
-|---|---|
-| M5Unified | 0.2.21 — `M5.Mic` |
-| M5IOE1 | 1.0.9, for `PDM_VDD` |
-| ESP-IDF | 5.5.1 |
-| Power state | **L3B** |
-
-## 4. Resources consumed
-
-| Resource | Value |
-|---|---|
-| ESP32-S3 GPIO | **GPIO45** (`PDM_CLK`), **GPIO46** (`PDM_DAT`) — both strapping pins |
-| I²S peripheral | **`I2S_NUM_0`** in the factory firmware |
-| Expander pin | `IO12` (`PDM_VDD_EN`) |
-| Rail | `PDM_VDD` (state L3B) |
-| DMA | `dma_buf_len = 128`, `dma_buf_count = 8` |
-
-## 5. The vendor's exact configuration
-
-Transcribed from `M5PaperMono-UserDemo/main/hal/hal_mic.cpp:12–96`. `executed-success`
-on the read; `not-tested` on hardware.
-
-| Setting | Value |
-|---|---|
-| Sample rate | **16 000 Hz** |
-| I²S port | `I2S_NUM_0` |
-| `pin_ws` | GPIO45 (the PDM clock lands on `WS`) |
-| `pin_data_in` | GPIO46 |
-| `pin_mck` / `pin_bck` | `I2S_PIN_NO_CHANGE` |
-| `input_channel` | `m5::input_channel_t::input_only_right` |
-| `over_sampling` | 1 |
-| `magnification` | 2 |
-| `dma_buf_len` / `dma_buf_count` | 128 / 8 |
-
-`input_only_right` is worth noting: the microphone appears on the **right** PDM channel.
-Configuring a stereo or left-channel capture gets you silence.
-
-## 6. Minimal procedure (`inferred`)
-
-```cpp
-#include <M5Unified.h>
-#include <M5IOE1.h>
-
-static int16_t buf[512];
-
-bool initMic() {
-  M5.Mic.end();
-  ioe1.digitalWrite(M5IOE1_PIN_12, LOW);   delay(20);   // power-cycle the mic
-  ioe1.digitalWrite(M5IOE1_PIN_12, HIGH);  delay(20);
-  releaseMicPins();                                     // see section 2
-
-  auto c = M5.Mic.config();
-  c.pin_mck = I2S_PIN_NO_CHANGE;  c.pin_bck = I2S_PIN_NO_CHANGE;
-  c.pin_ws  = GPIO_NUM_45;        c.pin_data_in = GPIO_NUM_46;
-  c.i2s_port      = I2S_NUM_0;
-  c.input_channel = m5::input_channel_t::input_only_right;
-  c.sample_rate   = 16000;
-  c.over_sampling = 1;
-  c.magnification = 2;
-  c.dma_buf_len   = 128;  c.dma_buf_count = 8;
-  M5.Mic.config(c);
-  return M5.Mic.begin();
-}
-
-void record() {
-  M5.Mic.record(buf, 512, 16000, false);
-  while (M5.Mic.isRecording()) { delay(1); }    // vendor waits with a 160 ms timeout
-}
-```
-
-The **power-cycle before `begin()`** is not decoration — the vendor's `initMic()` does
-exactly that, with 20 ms settling on each side.
-
-## 7. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (ESP32-S3)** | PDM RX is available on `I2S_NUM_0`. `I2S_NUM_1` exists but does not do PDM RX — so **the microphone and an I²S playback path cannot both use instance 0** |
-| **Board** | Both pins are strapping pins (§2) |
-| **Board** | **Mono, one microphone.** No stereo, no beamforming |
-| **Board** | Supply switchable, so the mic can be fully powered down |
-| **Framework** | Vendor configures 16 kHz / right channel only; other rates were not exercised by any vendor code |
-| **Unknown** | Every acoustic parameter — no datasheet exists |
-
-## 8. There is no audio output path for this
-
-The PaperMono has a **[buzzer](buzzer.md), not a speaker**. There is no codec, no
-amplifier and no DAC output on the board.
-
-Curiously, **both** custom chips' register maps expose an `AW8737A_PULSE` register
-(M5PM1 `0x53`, M5IOE1 `0x90`) — an audio-amplifier control — with no corresponding
-amplifier anywhere in the PaperMono BOM. These are almost certainly generic features of
-the shared `PY32L020F15U6` firmware rather than anything populated on C153. `inferred`.
-
-There is also a version delta worth knowing: M5Unified `develop` contains a change
-described in its own diff as *"Keep Audio Power (M5IOE1_G3) on: cutting it forces another
-codec…"*. **That comment is about a different board** — on the PaperMono, M5IOE1 `IO3` is
-the e-paper rail. Do not read it as PaperMono audio guidance.
-
-## 9. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Mic + [buzzer](buzzer.md) | ✅ | Different peripherals — I²S vs LEDC — and the buzzer will be audible in the recording |
-| Mic + I²S playback | ❌ **not on the same instance** | PDM RX occupies `I2S_NUM_0`. There is nothing to play to anyway |
-| Mic + [display](epaper-display.md) refresh | ⚠ untested | No pin conflict; both are DMA clients |
-| Mic + [sleep](power-and-sleep.md) below L3B | ❌ | `PDM_VDD` is an L3B rail |
-| Mic pins + reset/boot | ⚠ | Strapping pins (§2) |
-| Mic + [Wi-Fi](wifi-and-bluetooth.md) | ⚠ untested | The usual DMA/CPU contention; no measurement exists |
-
-## 10. Debugging
-
-| Symptom | Cause |
-|---|---|
-| `M5.Mic.begin()` fails | `PDM_VDD` off (`IO12`); or the pins were left claimed — call `releaseMicPins()` |
-| Silence, no error | Wrong channel — the mic is on `input_only_right` |
-| Board boots into an odd mode after a recording session | GPIO45/46 strap perturbation (§2) |
-| Level too low / too high | `magnification = 2` in the vendor config; there is no hardware gain control |
-| Distortion | Unknown — no AOP figure exists for this microphone |
-
-## 11. Unresolved questions
-
-- **No acoustic specification exists at all** for `LMD4737T261-AC02`.
-- Whether sample rates other than 16 kHz work — nothing exercises them.
-- Whether the strapping-pin exposure causes real boot failures in practice.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; the microphone is fitted on both C153 and C153-LITE |
-| Framework range | M5Unified 0.2.21 · ESP-IDF 5.5.1 · M5IOE1 1.0.9 |
-| Evidence | Pin map and I²S configuration: **read from vendor source** at cited `file:line`. Strapping-pin hazard: **`inferred`** from the pin map. Sketch: **`inferred`** |
-| Confidence | High on wiring and the exact vendor config; **zero on audio quality** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md`](../pinouts-and-buses.md) · [`../resources-and-conflicts.md`](../resources-and-conflicts.md)
-- [`buzzer.md`](buzzer.md) · [`io-expander.md`](io-expander.md) · [`usb-and-serial.md`](usb-and-serial.md) · [`power-and-sleep.md`](power-and-sleep.md)
-- [`components/generic/lmd4737t261-ac02-pdm-microphone`](../../../../components/generic/lmd4737t261-ac02-pdm-microphone/README.md) · [`components/awinic/aw35122`](../../../../components/awinic/aw35122/README.md)
diff --git a/devices/m5stack/papermono/features/microsd.md b/devices/m5stack/papermono/features/microsd.md
deleted file mode 100644
index 3fe9c78..0000000
--- a/devices/m5stack/papermono/features/microsd.md
+++ /dev/null
@@ -1,201 +0,0 @@
-# microSD — M5Stack PaperMono
-
-> **How do I mount the card, and why does nothing happen when I try?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-## 1. Capability summary and the hardware path
-
-A microSD slot wired for **4-bit SDMMC** — not SPI — with its power rail and its
-card-detect switch both behind the [I/O expander](io-expander.md).
-
-```
-ESP32-S3  ──4-bit SDMMC, GPIO8-13──▶  microSD slot
-                                          ▲
-              TF_3V3_L3B (AW35122 U8) ────┤ power,  enabled by M5IOE1 IO14
-              card-detect switch ─────────┘ sensed by M5IOE1 IO1 (LOW = inserted)
-```
-
-| Signal | GPIO | Note |
-|---|---|---|
-| `DAT3` | **GPIO8** | |
-| `DAT2` | **GPIO9** | |
-| `DAT1` | **GPIO10** | |
-| `DAT0` | **GPIO11** | |
-| `CMD` | **GPIO12** | |
-| `CLK` | **GPIO13** | 22 Ω series (`R35`) |
-| Power enable | M5IOE1 **`IO14`** | `TF_EN` |
-| Card detect | M5IOE1 **`IO1`** | `TF_DET`, **low = inserted** |
-
-Confirmed by two independent sources: `M5PaperMono-UserDemo/main/hal/hal_tf_card.cpp:17–22`
-and `M5Unified/src/M5Unified.cpp:216` (the `board_M5PaperMono` SD pin set, identical on
-`master` and `develop`).
-
-Power switch: [`components/awinic/aw35122`](../../../../components/awinic/aw35122/README.md).
-Expander: [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md).
-
-## 2. Card detect
-
-M5Stack, on the product page:
-
-> "`TF_DET` is pulled up by the microSD power domain. When the card slot switch is closed,
-> the detection pin is pulled low to identify microSD card insertion."
-
-Two consequences that follow from *"pulled up by the microSD power domain"*:
-
-- **Card detect only works while `TF_3V3_L3B` is on.** If you drop the card's power to
-  save current, you also lose the ability to see whether a card is present.
-- The factory firmware sets `IO1` as an input with a **pull-up enabled on the expander**
-  (`hal_tf_card.cpp:34–37`) rather than relying solely on the card rail.
-
-The vendor's own bring-up leaves the card **powered off** by default:
-
-```cpp
-ioe1.pinMode(TF_EN_PIN, OUTPUT);                        // M5IOE1_PIN_14
-ioe1.pinMode(TF_DET_PIN, INPUT);                        // M5IOE1_PIN_1
-ioe1.setDriveMode(TF_EN_PIN, M5IOE1_DRIVE_PUSHPULL);
-ioe1.setPullMode(TF_DET_PIN, M5IOE1_PULL_UP);
-ioe1.digitalWriteWithRes(TF_EN_PIN, LOW, &err);         // power OFF at init
-```
-
-M5GFX, by contrast, drives `IO14` **high** during board bring-up
-(`M5GFX.cpp:2096`, mask bit 13). So depending on which library initialised the board, the
-card rail may or may not already be on. Check, do not assume.
-
-> A relevant version delta: M5Unified `develop` **removes an SD-card power-on block** from
-> `Power_Class.cpp` around line 364 relative to `master`. If SD power behaviour changes
-> between two of your builds, that is where to look.
-
-## 3. Prerequisites
-
-| Item | Value |
-|---|---|
-| ESP-IDF | 5.5.1 — `driver/sdmmc_host.h`, `esp_vfs_fat.h`, `sdmmc_cmd.h` |
-| M5Unified | 0.2.21 |
-| M5IOE1 | 1.0.9 |
-| FATFS config | The vendor's `sdkconfig.defaults` sets `CONFIG_FATFS_LFN_HEAP=y`, `CONFIG_FATFS_MAX_LFN=255`, `CONFIG_FATFS_API_ENCODING_UTF_8=y`, `CONFIG_FATFS_CODEPAGE_DYNAMIC=y` |
-| Power state | **L3B** |
-
-The UTF-8 / long-filename settings are worth copying: they are why the factory firmware
-handles CJK filenames, and their absence is a common cause of "the file is there but I
-cannot open it".
-
-## 4. Resources consumed
-
-| Resource | Value |
-|---|---|
-| ESP32-S3 GPIO | **six**: GPIO8–GPIO13 |
-| Peripheral | **SDMMC host**, slot config `width = 4` |
-| Expander pins | `IO14` power, `IO1` detect |
-| Rail | `TF_3V3_L3B` (state L3B) |
-| Mount point | `/sdcard` in the factory firmware |
-| Heap | `max_files = 8`, `allocation_unit_size = 16 * 1024` |
-
-**Six GPIOs is the largest single GPIO allocation on the board.** Dropping to 1-bit mode
-would free GPIO8–GPIO10, but there is no header to expose them on, so there is nothing to
-gain.
-
-## 5. Minimal procedure (`inferred`)
-
-Transcribed in shape from `hal_tf_card.cpp:142–157`. **Not run on hardware.**
-
-```c
-#include <driver/sdmmc_host.h>
-#include <esp_vfs_fat.h>
-#include <sdmmc_cmd.h>
-
-// 1. power the card and check detect, both through the expander
-ioe1.setDriveMode(M5IOE1_PIN_14, M5IOE1_DRIVE_PUSHPULL);
-ioe1.digitalWrite(M5IOE1_PIN_14, HIGH);         // TF_EN on
-vTaskDelay(pdMS_TO_TICKS(10));
-bool inserted = (ioe1.digitalRead(M5IOE1_PIN_1) == LOW);   // LOW = card present
-
-// 2. mount
-esp_vfs_fat_sdmmc_mount_config_t mount_config = {};
-mount_config.format_if_mount_failed = false;    // vendor default - do not reformat a user's card
-mount_config.max_files              = 8;
-mount_config.allocation_unit_size   = 16 * 1024;
-
-sdmmc_host_t host               = SDMMC_HOST_DEFAULT();
-sdmmc_slot_config_t slot_config = SDMMC_SLOT_CONFIG_DEFAULT();
-slot_config.width = 4;
-slot_config.clk = GPIO_NUM_13;  slot_config.cmd = GPIO_NUM_12;
-slot_config.d0  = GPIO_NUM_11;  slot_config.d1  = GPIO_NUM_10;
-slot_config.d2  = GPIO_NUM_9;   slot_config.d3  = GPIO_NUM_8;
-
-sdmmc_card_t* card = NULL;
-esp_err_t ret = esp_vfs_fat_sdmmc_mount("/sdcard", &host, &slot_config, &mount_config, &card);
-```
-
-Remember the [expander off-by-one](io-expander.md#2--trap-1-m5ioe1_pin_3--2): use
-`M5IOE1_PIN_14` and `M5IOE1_PIN_1`, never the literals `14` and `1`.
-
-## 6. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (ESP32-S3)** | One SDMMC host; 4-bit mode uses six pins |
-| **Board** | Power and detect both behind I²C. **No I²C, no card** |
-| **Board** | 22 Ω series on `CLK` only |
-| **Framework** | `SDMMC_HOST_DEFAULT()` — the vendor does **not** override `max_freq_khz`, so the card runs at the IDF default |
-| **Framework** | `format_if_mount_failed = false` in vendor code |
-| **Observed** | **Nothing.** No throughput figure, no capacity limit, no filesystem compatibility report exists from anyone |
-
-**No card capacity or filesystem limit is documented by M5Stack anywhere.** The usual
-ESP-IDF FATFS constraints apply — exFAT is not supported by the stock driver, so cards
-larger than 32 GB generally need reformatting to FAT32 — but that is a general ESP-IDF
-statement, `inferred`, not a PaperMono finding.
-
-## 7. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| microSD + [display](epaper-display.md) | ✅ no pin conflict | SDMMC GPIO8–13, panel GPIO14–18. Both in L3B; both power enables are expander pins |
-| **microSD + display + [Wi-Fi](wifi-and-bluetooth.md)** | ⚠ **untested, and the interesting case** | No pin conflict at all. The pressure is on GDMA, PSRAM bandwidth and the L3B rail simultaneously: a full e-paper refresh is seconds of SPI DMA, SDMMC is a second DMA client, and Wi-Fi is a third plus an RF current draw. **Nobody has run this.** See [`../resources-and-conflicts.md`](../resources-and-conflicts.md) |
-| microSD + [LoRa](lora.md) | ✅ | Different SPI host; LoRa is on `SPI3_HOST`, SD is not on SPI at all |
-| microSD + [sleep](power-and-sleep.md) | ⚠ **unmount first** | The rail is L3B. Dropping it under an open file is a corruption path |
-| microSD + card removal | ⚠ | Detect is polled, not interrupt-driven, in vendor code. Hot-removal during a write is not protected |
-| microSD + [charger](battery-and-charging.md) access | ⚠ | Unrelated buses, but both need the expander; do not gate the charger inside a mount sequence |
-
-## 8. Debugging
-
-| Symptom | Cause |
-|---|---|
-| Card never detected | `TF_EN` (`IO14`) is low — the vendor's own init leaves it off |
-| Detect reads "inserted" with no card | Card rail off, so the pull-up domain is dead; or you inverted the sense (**low = inserted**) |
-| Mount fails | Card not FAT32; `format_if_mount_failed = false` so it will not silently reformat |
-| Filenames with non-ASCII characters fail | Missing `CONFIG_FATFS_API_ENCODING_UTF_8` / `CONFIG_FATFS_MAX_LFN=255` |
-| Card works under one library, not another | M5GFX drives `IO14` high at bring-up; the factory HAL drives it low. Check who initialised |
-| Corruption after sleep | Rail dropped with files open |
-| SD power behaves differently between builds | M5Unified `develop` removed an SD power-on block relative to `master` |
-
-## 9. Alternatives for storage
-
-| Option | Size | Use when |
-|---|---|---|
-| **microSD** | unspecified by the vendor | Bulk data, book files, logs |
-| **NVS** | 24 KB partition at `0x9000` | Settings, credentials |
-| Flash free space | ~960 KB unallocated above the app | Nothing uses it as shipped |
-| PSRAM | 8 MB octal | Volatile buffers only — and the display needs it |
-
-> **There is no SPIFFS, no FATFS-in-flash and no OTA slot** in either vendor project. The
-> partition table is three entries: `nvs` 24 KB, `phy_init` 4 KB, and a single
-> `factory` app of `0xF00000` (15 MiB) at `0x10000`. By contrast the third-party
-> CrossPoint e-reader image repartitions entirely — 6400 KB app, a 4096 KB `cjkfont`
-> partition, SPIFFS and a coredump region — which is a good demonstration that the layout
-> is a firmware choice, not a hardware constraint.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; microSD is fitted on both C153 and C153-LITE |
-| Framework range | ESP-IDF 5.5.1 · M5Unified 0.2.21 · M5IOE1 1.0.9 |
-| Evidence | Pin map: **two independent sources** (`hal_tf_card.cpp`, `M5Unified.cpp:216`), `executed-success` read. Detect semantics: **vendor-documented**. Mount sketch: **`inferred`** |
-| Confidence | High on wiring; **no performance evidence at all** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md`](../pinouts-and-buses.md) · [`../resources-and-conflicts.md`](../resources-and-conflicts.md)
-- [`io-expander.md`](io-expander.md) · [`power-and-sleep.md`](power-and-sleep.md) · [`epaper-display.md`](epaper-display.md)
-- [`components/awinic/aw35122`](../../../../components/awinic/aw35122/README.md) · [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md)
diff --git a/devices/m5stack/papermono/features/nfc.md b/devices/m5stack/papermono/features/nfc.md
deleted file mode 100644
index 97941a8..0000000
--- a/devices/m5stack/papermono/features/nfc.md
+++ /dev/null
@@ -1,247 +0,0 @@
-# NFC — M5Stack PaperMono
-
-> **Common guide:** [`guides/nfc`](../../../../guides/nfc/README.md) holds the device-independent NFC material — standards, silicon choice, antenna and matching, libraries and debugging.
->
-> **Applicability:** the standard approach **applies with deltas**. On this board the chip is power-gated through the M5IOE1 I/O expander, the net named `PYB_RFID_RST` is a **load-switch enable rather than a reset** (the ST25R3916 has no reset pin), the reader sits on the shared system I²C bus at `0x50`, and **one sheet of the NFC front-end schematic was never published**.
-
-> **How do I set up NFC on this device?**
-> Hardware revision **V0.6.2** (SKU **C153 only** — not fitted on the Lite) ·
-> snapshot **2026-09-01** · nothing tested on hardware.
-
-> **This guide is short on results and says so.** The API surface and the wiring are well
-> evidenced. **Which card types have actually been read on a real PaperMono is unknown** —
-> no vendor test report, no community report, no measurement. §8.
-
-## 1. Capability summary and the hardware path
-
-An ST NFC reader/writer front end on its own sub-board, on the shared system I²C bus,
-with an interrupt line to the ESP32-S3 and its supply enabled through the
-[I/O expander](io-expander.md).
-
-```
-ST25R3916 (I2C 0x50, NFC sub-board)
-   ├─ SDA/SCL ──▶ system I²C bus (GPIO47/48)
-   ├─ IRQ ─────▶ ESP32-S3 GPIO6
-   ├─ enable ◀── M5IOE1 IO4 (PYB_NFC_EN)
-   └─ 3V3_L2 ◀── main board, via J3 (10-pin B2B)
-```
-
-| Element | Part | Record |
-|---|---|---|
-| NFC front end | ST **ST25R3916**, I²C `0x50` | [`components/stmicroelectronics/st25r3916/`](../../../../components/stmicroelectronics/st25r3916/) — **record is written**: the datasheet artifact is held, the write-up is not yet done |
-| Power enable | M5IOE1 `IO4` | [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) |
-| Sub-board | `02 Paper Mono NFC.SchDoc`, rev **V0.2**, dated 2026-07-28 | [`../pinouts-and-buses.md`](../pinouts-and-buses.md#board-set--this-is-not-one-pcb) |
-| Connector | `J3`, `BTB0.408-10PLBDR-G41` | idem |
-
-Advertised card technologies (vendor specification table):
-**ISO14443A, ISO14443B, FeliCa™, ISO15693.**
-
-> ⚠ **Sheet 1 of 2 of the NFC schematic is not published.** The included sheet is
-> explicitly numbered `2/2`. **The NFC front-end matching network, antenna and crystal
-> details on sheet 1 are undocumented, not absent.** Recorded as
-> [`../gaps-and-conflicts.md` G1](../gaps-and-conflicts.md#g1--nfc-schematic-sheet-1-of-2-is-not-published).
-
-## 2. Prerequisites
-
-| Item | Value |
-|---|---|
-| **M5Unit-NFC** | pinned at **`0.1.0`**, commit `93745b547364f310cd64b5155a870103a7800a5d`, **patched** by the vendor build |
-| **M5UnitUnified** | **`0.5.5`**, commit `bf711f37…`, patched |
-| M5Utility | `0.1.0` |
-| M5IOE1 | 1.0.9, for `IO4` |
-| Header | `#include <M5UnitUnifiedNFC.h>` |
-
-> ⚠ **Two vendor pages disagree about `M5UnitUnified`.** The Arduino quick-start page tells
-> you to install it; the PlatformIO `lib_deps` on both product pages **omits it entirely**
-> while listing `M5Unit-NFC`. The factory firmware needs both. Install both.
->
-> Also note the PlatformIO block pins nothing — a library-manager install gives you
-> current releases, not the commits the factory firmware was built against.
-
-## 3. Resources consumed
-
-| Resource | Value |
-|---|---|
-| I²C address | **`0x50`** on the shared bus, at **400 kHz** (`NFC_I2C_FREQ_HZ = 400000`) |
-| ESP32-S3 GPIO | **GPIO6** — `IRQ`. The scan app runs with `using_irq = false` and polls |
-| Expander pin | `IO4` (`PYB_NFC_EN`) |
-| Rail | `3V3_L2` — NFC is powered in state **L2** |
-| Task | The factory scan app uses a **16 KB stack** task at priority 4 |
-
-> Schematic sheet 4 annotates `PYB_NFC_EN` as a **"spare GPIO"** while the factory
-> firmware uses it as the NFC enable. Likely a stale annotation; unresolved
-> ([C8](../gaps-and-conflicts.md#c8--pyb_nfc_en-annotated-spare-gpio)).
-
-## 4. Identity probe and the Pro-vs-Lite discriminator
-
-The firmware confirms the part is present by reading register **`0x7F`** and comparing
-against expected type **`0x05`** (`hal_board.cpp:22–23`, used at `:145`).
-
-That probe, together with a write to `IO4`, is **how the firmware tells a PaperMono from a
-PaperMono-Lite** (`hal_board.cpp:160–172`). See
-[`io-expander.md` §9](io-expander.md#9-the-expander-is-the-pro-vs-lite-discriminator).
-
-**M5GFX cannot make this distinction** — it masks NFC out of its board-detection test
-(`M5GFX.cpp:1945`) so both SKUs land on the single enum `board_M5PaperMono`. Only the
-application layer can tell.
-
-## 5. Minimal procedure (`inferred`)
-
-Transcribed in shape from `M5PaperMono-UserDemo/main/apps/app_nfc_scan/app_nfc_scan.cpp`.
-**Not run on hardware.**
-
-```cpp
-#include <M5Unified.h>
-#include <M5UnitUnifiedNFC.h>
-#include <M5IOE1.h>
-
-m5::unit::UnitUnified s_hub;
-m5::unit::UnitNFC     s_nfc;
-m5::nfc::NFCLayerA    s_a{s_nfc};      // ISO14443A
-m5::nfc::NFCLayerB    s_b{s_nfc};      // ISO14443B
-m5::nfc::NFCLayerF    s_f{s_nfc};      // FeliCa
-m5::nfc::NFCLayerV    s_v{s_nfc};      // ISO15693
-
-bool nfcBegin() {
-  ioe1.pinMode(M5IOE1_PIN_4, OUTPUT);
-  ioe1.setDriveMode(M5IOE1_PIN_4, M5IOE1_DRIVE_PUSHPULL);
-  m5ioe1_err_t err = M5IOE1_OK;
-  ioe1.digitalWriteWithRes(M5IOE1_PIN_4, HIGH, &err);   // power the NFC sub-board
-  if (err != M5IOE1_OK) return false;                   // -> this is a Lite
-
-  auto cfg      = s_nfc.config();
-  cfg.emulation = false;
-  cfg.mode      = m5::nfc::NFC::A;
-  cfg.using_irq = false;                                // vendor polls; GPIO6 unused
-  s_nfc.config(cfg);
-
-  return s_hub.add(s_nfc, M5.In_I2C) && s_hub.begin();
-}
-
-void scanA() {
-  s_hub.update();
-  std::vector<...> piccs;
-  if (s_a.detect(piccs, /*timeout_ms=*/180) && !piccs.empty()) {
-    auto& picc = piccs.front();
-    Serial.println(picc.uidAsString().c_str());
-  }
-}
-```
-
-Switching technology mid-run, as the vendor app does:
-
-```cpp
-s_nfc.disableField();
-auto cfg = s_nfc.config(); cfg.emulation = false; cfg.mode = mode; s_nfc.config(cfg);
-s_nfc.configureNFCMode(mode);
-s_nfc.begin();
-s_hub.update();
-```
-
-Per-layer detect signatures, exactly as the vendor calls them:
-
-| Layer | Call |
-|---|---|
-| A | `s_a.detect(piccs, timeout_ms)` |
-| B | `s_b.detect(piccs, 0x00, 4, timeout_ms)` |
-| F (FeliCa) | `s_f.detect(piccs, m5::nfc::f::TimeSlot::Slot16, timeout_ms)` |
-| V (ISO15693) | `s_v.detect(piccs, timeout_ms)` |
-
-## 6. The vendor's scan timings
-
-`app_nfc_scan.cpp:21–28`. Worth copying because they encode the polling rhythm someone
-tuned:
-
-| Constant | Value |
-|---|---|
-| `NFC_A_SCAN_WINDOW_MS` | **3500** — type A gets far the longest window |
-| `NFC_OTHER_SCAN_WINDOW_MS` | 900 |
-| `NFC_DETECT_TIMEOUT_MS` | 180 |
-| `NFC_DETECT_GAP_MS` | 60 |
-| `NFC_MODE_STABLE_MS` | 200 |
-| `NFC_TOUCH_COOLDOWN_MS` | 300 |
-
-The app cycles through modes, calls `disableField()` between them, and rate-limits UI
-updates — which on an e-paper device is not optional. See
-[`epaper-display.md` §8](epaper-display.md#8-panel-safety--the-rules-that-are-not-optional).
-
-## 7. Limits
-
-| Class | Limit |
-|---|---|
-| **Board** | **Not fitted on the PaperMono-Lite.** NFC + LoRa is the entire USD 10 SKU delta |
-| **Board** | The NFC sub-board is powered from `3V3_L2` and enabled via I²C. **No I²C, no NFC** |
-| **Board** | Sheet 1 of the NFC schematic is unpublished — matching network and antenna undocumented (§1) |
-| **Board** | **No certification of any kind is published**, including for the 13.56 MHz emitter |
-| **Framework** | Vendor uses **polling**, `using_irq = false`. The GPIO6 interrupt path is **unexercised by any vendor code** |
-| **Framework** | Card emulation is exposed (`cfg.emulation`) but **set false everywhere** in vendor code and never demonstrated |
-| **Observed** | **Nothing** (§8) |
-
-## 8. ⚠ What has actually been tested: nothing that we can see
-
-This is the honest state of the evidence, and it is the reason this guide is short:
-
-- **M5Stack advertises ISO14443A, ISO14443B, FeliCa and ISO15693.** That is a
-  specification-table claim, `not-tested`.
-- The library exposes four layer classes matching those four technologies, and the vendor
-  demo cycles through all four. **That the code path exists is not evidence that a card
-  was read.**
-- **No vendor test report, no card compatibility list, no community report, and no
-  hands-on account** mentions reading any specific tag on a PaperMono. Two broad
-  independent community passes found one hands-on video (a first look, with an affiliate
-  link) and no written review at all.
-- The scan-window asymmetry (3500 ms for type A vs 900 ms for the others) is the only
-  indirect hint that type A is the primary case, and even that is an inference from a
-  constant.
-
-So: **do not assume MIFARE Classic, MIFARE DESFire, NTAG, FeliCa or a specific ISO15693
-tag family works until you have tried it.** No read range figure exists either. If you
-have hardware, this is the single highest-value thing in this record to go and measure.
-
-## 9. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| NFC + [Wi-Fi](wifi-and-bluetooth.md)/[LoRa](lora.md) | ✅ RF-wise | 13.56 MHz vs 2.4 GHz vs sub-GHz. No spectral interaction |
-| **NFC + [charger](battery-and-charging.md) on the shared I²C bus** | ⚠ **the combination to be careful with** | Both are on the **one** I²C bus. NFC polling is chatty — the vendor app runs 180 ms detect calls with 60 ms gaps for seconds at a time — and gating the IP2315 onto that bus is the **one documented bus-stability hazard on this board**. Do not open the charger gate inside an NFC scan window; batch charger reads between scans, and close the gate immediately. If the bus wedges, the documented recovery is a short press of the power button |
-| NFC + [touch](touch.md) | ⚠ bandwidth | Same bus, distinct addresses. Touch is latency-sensitive; a long NFC transaction adds jitter |
-| NFC + [display](epaper-display.md) | ✅ | Different buses; but rate-limit your UI |
-| NFC + [sleep](power-and-sleep.md) | ⚠ | Sheet 1 lists NFC as an L2 wake source; **no vendor firmware exercises it**. Untested |
-| NFC + the [expander](io-expander.md) | ⚠ | `IO4` is the enable, and `IO4` is one of only two expander pins the vendor product page omits |
-
-## 10. Debugging
-
-| Symptom | Cause |
-|---|---|
-| `0x50` absent from an I²C scan | `IO4` not asserted — or you have a **Lite**, which has no NFC at all |
-| `digitalWriteWithRes(IO4, …)` errors | Same — that error *is* the Lite detection (§4) |
-| Identity probe fails | Read `0x7F`, expect `0x05` |
-| No cards detected in any mode | Field disabled, or wrong layer for the card. Try type A first |
-| Other I²C devices misbehave during scanning | Bus contention — see §9, especially the charger gate |
-| `M5UnitUnified` missing at compile time | The PlatformIO snippet omits it; install it anyway (§2) |
-
-## 11. Unresolved questions
-
-- **Which card types actually work, and at what range** (§8).
-- **NFC schematic sheet 1** — antenna, matching, crystal.
-- Whether the GPIO6 interrupt path works; nothing uses it.
-- Whether card **emulation** works; the flag exists, nothing sets it.
-- The `PYB_NFC_EN` "spare GPIO" annotation.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**, **SKU C153 only**. ❌ Not fitted on C153-LITE |
-| Framework range | M5Unit-NFC 0.1.0 (pinned, patched) · M5UnitUnified 0.5.5 · M5Unified 0.2.21 · M5IOE1 1.0.9 |
-| Evidence | Address, IRQ pin, enable pin, identity probe: **read from vendor source**, `executed-success`. API and timings: **read from the vendor demo**. Card compatibility: **`not-tested` and unreported by anyone** |
-| Confidence | High on the wiring and API shape; **zero on real-world tag reading** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md#i²c-bus--the-one-shared-bus`](../pinouts-and-buses.md#i²c-bus--the-one-shared-bus) · [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md)
-- [`io-expander.md`](io-expander.md) · [`battery-and-charging.md`](battery-and-charging.md) · [`lora.md`](lora.md) · [`power-and-sleep.md`](power-and-sleep.md)
-- [`components/stmicroelectronics/st25r3916/`](../../../../components/stmicroelectronics/st25r3916/) (stub) · [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md)
-- [`vendors/m5stack`](../../../../vendors/m5stack/README.md) — the ST25R3916 datasheet exists in **EN and ZH editions** on M5Stack's CDN; only the zh_CN product page links the ZH one
-- [**`guides/nfc`**](../../../../guides/nfc/README.md) — the device-independent companion to this page (see the applicability note at the top): the standards landscape, antenna and matching, the operation-byte pattern, software stacks and generic failure signatures
diff --git a/devices/m5stack/papermono/features/power-and-sleep.md b/devices/m5stack/papermono/features/power-and-sleep.md
deleted file mode 100644
index a3c8c7d..0000000
--- a/devices/m5stack/papermono/features/power-and-sleep.md
+++ /dev/null
@@ -1,345 +0,0 @@
-# Power and sleep — M5Stack PaperMono
-
-> **How do I put this thing to sleep, and how do I get it to wake up again?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-This is the board's defining feature. Most ESP32 boards have a regulator and a sleep
-mode; the PaperMono has a **five-state power state machine implemented in a second
-microcontroller** that owns the ESP32-S3's reset and boot straps. In power terms the
-application processor is a peripheral of the power manager, not the other way round.
-
-## 1. Capability summary and the hardware path
-
-| Element | Part | Record |
-|---|---|---|
-| Power manager | **M5PM1**, I²C `0x6E` — a Puya `PY32L020F15U6` running M5Stack firmware | [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) |
-| Underlying silicon | `PY32L020F15U6` Cortex-M0+ | [`components/puya/py32l020f15u6`](../../../../components/puya/py32l020f15u6/README.md) |
-| Rail switching for L3B | **M5IOE1**, I²C `0x4F` | [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) · [`io-expander.md`](io-expander.md) |
-| Wake: alarm | RX8130CE RTC → M5PM1 `G0` | [`rtc.md`](rtc.md) |
-| Wake: motion | BMI270 IMU → M5PM1 `G4` | [`imu.md`](imu.md) |
-| Wake: touch | FT6336G → ESP32-S3 GPIO4 | [`touch.md`](touch.md) |
-| Wake: button | `PWR_BTN` → M5PM1 `BTN_PU` | [`buttons-and-rgb-led.md`](buttons-and-rgb-led.md) |
-
-## 2. The five power states
-
-Schematic sheet 1 tabulates them as columns. Names are M5Stack's.
-
-| State | Name | What is powered | Wakes on |
-|---|---|---|---|
-| **L0** | Shipping | Charger, protection, `3V3_L0`. M5PM1 alive | Power button, USB insertion |
-| **L1** | Standby | + `3V3_L1` — **RTC and IMU** | Power button, **RTC alarm**, **IMU motion** |
-| **L2** | DeepSleep | + `3V3_L2` — ESP32-S3, touch, NFC, keys, expander | + touch, keys, NFC, LoRa |
-| **L3A** | Core active | + e-paper rail `EPD_3V3_L3B` | — |
-| **L3B** | All active | + frontlight, microSD, microphone | — |
-
-Transitions, as M5Stack states them:
-
-- **Into L0** — the ESP32-S3 issues an I²C shutdown command to the M5PM1.
-- **L0 → L1** is automatic.
-- **L1 → L2** is enabled by the M5PM1 on a single power-button click, an IMU interrupt,
-  or an RTC interrupt.
-- **L3** switches are asserted by the ESP32-S3 through the M5IOE1.
-
-> **The tree is parallel, not cascaded.** M5Stack: *"The PaperMono multi-level power
-> switching design is **not a series structure**. The power inputs for the L1 ~ L3B
-> switches all originate from the L0 (`SYS_VBUS`) source rather than from the preceding
-> power level, allowing each level to be controlled independently."*
->
-> And: *"After the M5PM1 powers on, L1, L2, and L3A are enabled automatically. During
-> M5Unified initialization, the M5IOE1 is then controlled to enable L3B."*
->
-> L2 versus L3A is a **state** distinction, not a separate rail: *"When the ESP32-S3 is
-> sleeping, the power system is at level L2. When the ESP32-S3 is operating, it is at
-> level L3A."* Whether L3A and L3B are genuinely separate switch groups is
-> [not fully resolved](../power-architecture.md#what-is-not-established) — the rails they
-> name overlap.
-
-## 3. ⚠ RTC and IMU interrupts terminate on the M5PM1, not the ESP32-S3
-
-**This is the structural fact that makes the whole architecture work, and it is easy to
-miss.**
-
-| Source | Lands on | Consequence |
-|---|---|---|
-| RX8130CE `nIRQ` | net `PYG0_RTC_INT` → **M5PM1 pin 3 (`G0`)** | An alarm can wake the board with the ESP32-S3 **unpowered** |
-| BMI270 `INT1` | net `PYG4_IMU_INT` → **M5PM1 pin 12 (`G4`)** | Motion can wake the board with the ESP32-S3 **unpowered** |
-| FT6336G `INT` | ESP32-S3 **GPIO4** | Touch wake requires the ESP32-S3 to be at least in its own light/deep sleep — i.e. state L2 |
-| M5PM1 IRQ out | `G1` → ESP32-S3 **GPIO1** | The M5PM1 routes its own interrupts to the host when the host is awake |
-
-There is **no path from the RTC or the IMU to an ESP32-S3 GPIO**. If you write
-`esp_sleep_enable_ext0_wakeup()` on a pin expecting an RTC alarm, nothing will ever
-arrive. You must configure the wake on the **M5PM1** instead.
-
-The shipped factory binary confirms both intent and polarity:
-
-```
-PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge
-PM1 shutdown, wake by RX8130 timer  -> PM1 G0 falling edge
-```
-
-## 4. Prerequisites
-
-| Item | Value |
-|---|---|
-| M5PM1 library | **1.0.7** (registry `m5stack/m5pm1`) |
-| M5IOE1 library | **1.0.9** |
-| M5Unified | 0.2.21 — `_pmic = pmic_t::pmic_m5pm1`, `_rtcIntPin = GPIO_NUM_1`, `_wakeupPin = GPIO_NUM_1` for this board |
-| I²C speed | M5PM1 and M5IOE1 are brought up at **100 kHz** by both M5Unified and the factory firmware |
-
-## 5. The API surface
-
-Transcribed from `M5PM1/src/M5PM1.h` and M5Stack's published power-management page.
-`executed-success` for the extraction; **`inferred`** for any sketch built from them.
-
-```
-pm1.begin(&M5.In_I2C, M5PM1_DEFAULT_ADDR, M5PM1_I2C_FREQ_100K)
-
-/* rails */
-pm1.setLdoEnable(bool)          // L1  (3V3_L1_EN)  - RTC + IMU
-pm1.setDcdcEnable(bool)         // L2  (3V3_L2_EN)  - ESP32-S3 and friends
-pm1.setBoostEnable(bool)
-pm1.ldoSetPowerHold(bool)       // retain L1 across shutdown
-pm1.boostSetPowerHold(bool)
-pm1.gpioSetPowerHold(pin, bool)
-
-/* shutdown, reset, timers */
-pm1.shutdown()
-pm1.setSingleResetDisable(bool)
-pm1.timerSet(uint32_t seconds, m5pm1_tim_action_t action)
-pm1.timerClear()
-pm1.setI2cSleepTime(uint8_t seconds)
-pm1.wdtSet(uint8_t timeout_sec) / pm1.wdtFeed() / pm1.wdtGetCount(uint8_t*)
-
-/* GPIO + wake */
-pm1.gpioSetMode / gpioSetPull / gpioSetDrive / gpioSetFunc / gpioSetOutput / gpioGetInput
-pm1.gpioSetWakeEnable(M5PM1_GPIO_NUM_n, bool)
-pm1.gpioSetWakeEdge(M5PM1_GPIO_NUM_n, M5PM1_GPIO_WAKE_FALLING)
-
-/* interrupts */
-pm1.irqClearGpioAll / irqClearSysAll / irqClearBtnAll
-pm1.irqSetGpioMaskAll / irqSetSysMaskAll / irqSetBtnMaskAll / irqSetGpioMask
-
-/* telemetry */
-pm1.readVbat(uint16_t* mv) / readVin / read5VInOut / readVref / readTemperature
-pm1.getPowerSource(m5pm1_pwr_src_t*) / getWakeSource(uint8_t*, cleanType)
-```
-
-Timer actions, verbatim from the vendor page:
-
-```cpp
-typedef enum {
-    M5PM1_TIM_ACTION_STOP     = 0b000,  // Stop, no action
-    M5PM1_TIM_ACTION_FLAG     = 0b001,  // Set flag only
-    M5PM1_TIM_ACTION_REBOOT   = 0b010,  // System reboot
-    M5PM1_TIM_ACTION_POWERON  = 0b011,  // Power on
-    M5PM1_TIM_ACTION_POWEROFF = 0b100   // Power off
-} m5pm1_tim_action_t;
-```
-
-## 6. Minimal procedures
-
-### 6.1 Timed power-off / power-on (`reported-working` — vendor's own sketch)
-
-Reproduced from `docs.m5stack.com/en/arduino/papermono/m5pm1_m5ioe1`. This is the one
-procedure here that M5Stack publishes as working. It has still **not been run on
-hardware in this record**.
-
-```cpp
-#include <M5Unified.h>
-#include <M5PM1.h>
-M5PM1 pm1;
-
-void setup() {
-  auto cfg = M5.config();
-  cfg.clear_display = false;
-  M5.begin(cfg);
-  const m5pm1_err_t err = pm1.begin(&M5.In_I2C, M5PM1_DEFAULT_ADDR, M5PM1_I2C_FREQ_100K);
-  if (err != M5PM1_OK) { /* halt */ }
-  M5.Display.setEpdMode(epd_mode_t::epd_fast);
-  M5.Display.drawString("BtnA: power on after 10s", M5.Display.width()/2, 280);
-}
-
-void loop() {
-  M5.update();
-  if (M5.BtnA.wasPressed()) {                 // shut down, come back in 10 s
-    pm1.timerSet(10, M5PM1_TIM_ACTION_POWERON);
-    pm1.shutdown();
-  }
-  if (M5.BtnB.wasPressed()) {                 // stay up 10 s, then power off
-    pm1.timerSet(10, M5PM1_TIM_ACTION_POWEROFF);
-  }
-}
-```
-
-### 6.2 Shut down and wake on motion, keeping L1 alive (`reported-working` as a vendor fragment)
-
-The important part is `setLdoEnable(true)` + `ldoSetPowerHold(true)` **before**
-`shutdown()` — that is what keeps the IMU powered in a state where the ESP32-S3 is not.
-
-```cpp
-pm1.gpioSetWakeEnable(M5PM1_GPIO_NUM_4, true);
-pm1.gpioSetWakeEdge  (M5PM1_GPIO_NUM_4, M5PM1_GPIO_WAKE_FALLING);   // active-low INT1
-pm1.setSingleResetDisable(false);
-
-/* ... configure BMI270 any-motion on INT1, active-low, push-pull ... */
-
-pm1.setLdoEnable(true);      // L1 on
-pm1.ldoSetPowerHold(true);   // and keep it on through shutdown
-pm1.setLedEnLevel(true);
-pm1.shutdown();
-```
-
-Full BMI270 configuration is in [`imu.md`](imu.md).
-
-### 6.3 ESP32-S3 deep sleep via M5Unified
-
-```cpp
-M5.Power.deepSleep(seconds_us, /* touch_wakeup = */ true);
-```
-
-> ⚠ **`touch_wakeup` substitutes, it does not add.** On this board M5Unified swaps the
-> EXT0 wake pin from GPIO1 (the M5PM1 IRQ) to GPIO4 (the touch INT) when
-> `touch_wakeup` is true (`Power_Class.cpp:1654`, `:1786`). You get touch wake **instead
-> of** the M5PM1 interrupt path, not as well as. `executed-success` on the source read.
-
-## 7. Two operational traps
-
-### 7.1 The first I²C transaction after M5PM1 idle-sleep fails
-
-M5Stack, verbatim:
-
-> "After it enters sleep, the **first communication from the ESP32-S3 is used to wake the
-> M5PM1 and therefore fails.** Valid communication completes on the next attempt after
-> wakeup."
-
-Their own firmware works around it by calling `pm1.setI2cSleepTime(0)` **twice** in a row
-(`hal_board.cpp:38–39`) — the first call is the sacrifice. If you have retry-free I²C
-code, `setI2cSleepTime` will look intermittently broken.
-
-### 7.2 Every optional rail defaults off
-
-Each switched LDO carries a **1 MΩ pulldown on its enable** (`R24`, `R26`, `R23`), so
-every optional rail is **off** on cold power-up. That is the correct failure mode for a
-battery product, and it means firmware must explicitly bring up the panel rail before the
-display responds. **A blank screen is the expected result of forgetting.**
-
-## 8. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Board** | RTC and IMU interrupts do not reach the ESP32-S3 at all (§3) |
-| **Board** | The M5PM1 owns `CHIP_PU` and the GPIO0 boot strap. **You cannot reset yourself independently of it** |
-| **Firmware (M5PM1)** | The register map is a *firmware API*, not silicon. Addresses moved between revisions — read `SW_REV` (`0x03`) before assuming a layout |
-| **Firmware (M5PM1)** | First I²C transaction after idle-sleep fails (§7.1) |
-| **Framework (M5Unified)** | `touch_wakeup` substitutes the wake pin (§6.3) |
-| **Observed** | Default single-click reset is aggressive enough that **two independent third-party projects disable it** — `pm1.setSingleResetDisable(true)` |
-| **Unknown** | **No current figure of any kind exists** for any state (§10) |
-
-## 9. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Sleep + [display](epaper-display.md) | ✅ ideal | The e-paper image persists with the rail off. Wait for `BUSY` to clear, then drop the rail |
-| Sleep + [RTC alarm](rtc.md) | ✅ down to **L1** | The intended low-power pattern |
-| Sleep + [motion wake](imu.md) | ✅ down to **L1** | idem. Requires `ldoSetPowerHold(true)` |
-| Sleep + [touch wake](touch.md) | ✅ only in **L2** | Touch does not reach the M5PM1 |
-| Touch wake + M5PM1 IRQ wake, same call | ❌ | §6.3 |
-| Sleep + [microSD](microsd.md) mounted | ⚠ unmount first | The card's rail is L3B; dropping it under an open file is a corruption path |
-| Sleep + [LoRa](lora.md) RX | ⚠ | The LoRa rail is switched by M5PM1 `G2`; sheet 1 lists LoRa as an L2 wake source, but no firmware exercises that path |
-| Sleep + [charging](battery-and-charging.md) | ✅ | The IP2315 charges independently of the M5PM1 state |
-| Sleep + [frontlight](frontlight.md) | ❌ | The boost rail is L3B |
-
-## 10. Debugging
-
-| Symptom | Cause |
-|---|---|
-| Wake-on-alarm never fires | You configured the wake on an ESP32-S3 GPIO. It has to be M5PM1 `G0` (§3) |
-| Wake-on-motion never fires | Same, on `G4`; **or** you used the vendor prose's active-**high** polarity, which is wrong — see [`imu.md`](imu.md) |
-| Board wakes but the IMU is dead | You did not `ldoSetPowerHold(true)`; L1 went down with everything else |
-| `setI2cSleepTime` appears to fail | §7.1 — retry once |
-| Board resets on a single power-button tap | Documented behaviour; `setSingleResetDisable(true)` |
-| Display blank after a state transition | The panel rail (M5IOE1 `IO3`) defaults off and must be re-asserted (§7.2) |
-| I²C bus wedged | Documented recovery is a **short press of the power button**. See [`battery-and-charging.md`](battery-and-charging.md) |
-
-## 10b. ESP32 light sleep — a disputed report, and the dispute is inside one source
-
-Two third-party projects appear to disagree about whether ESP32 light sleep works
-on this board. **The disagreement is weaker than it first looks**, and the reason
-is worth recording as a method lesson.
-
-### The claim
-
-`ciniml/paper_name_plate`'s `DESIGN.ja.md` §2.6, dated 2026-09-05:
-
-> 「light sleep は esp-hal 1.1 でこの基板では戻ってこないため不採用（JOURNAL 2026-09-05）。」
->
-> *"Light sleep was not adopted because on esp-hal 1.1 it does not return on this
-> board (JOURNAL 2026-09-05)."*
-
-`不採用` = "not adopted / rejected". Specific, dated, names the HAL version.
-
-### The counter-example
-
-`Corvelis/m5-touch-card` (C++) states in its README: *"While dark, controls lock
-and the idle CPU enters light sleep."* The Japanese original agrees —
-「通信などの処理がないときはライトスリープ」, *"light sleep when there is no processing
-such as communication"*.
-
-### ⚠ But the same Rust document says something different elsewhere
-
-§2.3, step 8 of the **same file**:
-
-> 「未: ESP32 light sleep（USB ログが止まるため保留）、PM1 タイマー起床。」
->
-> *"Not done: ESP32 light sleep (**on hold because USB logging stops**), PM1 timer
-> wake."*
-
-`保留` = "deferred / on hold" — a **completely different and much weaker reason**
-than "does not return". The two statements coexist, unreconciled, in the shipped
-document. The 2026-09-05 entry is later and presumably supersedes the earlier
-one, but both are present.
-
-### Assessment
-
-A prior analysis quoted only the stronger statement and graded it *"specific,
-dated, names the HAL version, and cost them a design change"* — concluding the
-fault localises to **esp-hal rather than the silicon**. That conclusion may well
-be right, but it rests on:
-
-1. the stronger of **two conflicting statements** in one document,
-2. a **JOURNAL entry that was never captured** — only a one-line citation of one,
-3. an attribution of `m5-touch-card`'s stack to ESP-IDF-Arduino that is
-   **unverified** (its `CMakeLists.txt` was not read).
-
-**Recorded as: unresolved.** What is reasonably supported is that *one Rust porter
-using esp-hal 1.1 chose not to ship light sleep*, and that *a C++ project reports
-using it*. Anything stronger — particularly "esp-hal is at fault" — is not
-established. Deep sleep is unaffected and is what both the vendor firmware and
-this page's §2 describe.
-
-## 11. What is not established
-
-- **No current or battery-life figure of any kind is published, and none was measured.**
-  The state table says what is *powered*, never what it *costs*. This is the largest
-  single gap in the record for a board whose entire pitch is low power.
-- Whether L3A and L3B are separate switch groups or a documentation distinction.
-- Whether KEY1/KEY2 are genuinely M5PM1 wake inputs (sheet 1 says so; no firmware uses
-  them that way).
-- The `U4` (`3V3_L0`) enable net could not be read with confidence.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; the power architecture is identical on C153 and C153-LITE |
-| Framework range | M5Unified 0.2.21 · M5PM1 1.0.7 · M5IOE1 1.0.9 · ESP-IDF 5.5.1 |
-| Evidence | State table and rails: **schematic**, `executed-success` extraction. API list: **vendor page + library header**. §6.1/§6.2 sketches: **`reported-working`** (vendor-published) but **`not-tested`** here. Interrupt polarity: **corroborated by the shipped binary** |
-| Confidence | High on structure and wiring; **zero on power consumption**, which is unmeasured |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../power-architecture.md`](../power-architecture.md) — rails, enables, charging, the full wake table
-- [`../pin-naming-and-the-pyg-ambiguity.md`](../pin-naming-and-the-pyg-ambiguity.md)
-- [`rtc.md`](rtc.md) · [`imu.md`](imu.md) · [`touch.md`](touch.md) · [`battery-and-charging.md`](battery-and-charging.md) · [`io-expander.md`](io-expander.md)
-- [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) · [`components/puya/py32l020f15u6`](../../../../components/puya/py32l020f15u6/README.md)
diff --git a/devices/m5stack/papermono/features/rtc.md b/devices/m5stack/papermono/features/rtc.md
deleted file mode 100644
index 7d8de86..0000000
--- a/devices/m5stack/papermono/features/rtc.md
+++ /dev/null
@@ -1,186 +0,0 @@
-# RTC — M5Stack PaperMono
-
-> **How do I keep time, and how do I schedule a wake-up?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-**This guide is short.** Keeping time is ordinary; the PaperMono-specific fact is that
-the RTC's alarm interrupt goes to the **power manager**, so a scheduled wake works with
-the ESP32-S3 completely unpowered.
-
-## 1. Capability summary and the hardware path
-
-A Seiko Epson RTC on the shared system I²C bus, powered from the **L1** rail.
-
-```
-RX8130CE (I2C 0x32)
-   ├─ SDA/SCL ──▶ system I²C bus (GPIO47/48), 400 kHz
-   ├─ nIRQ ─────▶ PYG0_RTC_INT ──▶ M5PM1 pin 3 (G0)     <- NOT the ESP32-S3
-   └─ VDD   ◀─── 3V3_L1, enabled by M5PM1 LDO3V3_EN_PP
-```
-
-| Element | Part | Record |
-|---|---|---|
-| RTC | Seiko Epson **RX8130CE**, `0x32` | [`components/seiko-epson/rx8130ce/`](../../../../components/seiko-epson/rx8130ce/) — **record is written**: the datasheet artifact is held, the write-up is not yet done |
-| Interrupt destination | **M5PM1 `G0`** | [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md) · [`power-and-sleep.md`](power-and-sleep.md) |
-
-## 2. ⚠ The alarm interrupt lands on the power manager
-
-As with the [IMU](imu.md), there is **no path from the RTC to any ESP32-S3 GPIO**.
-Configuring an ESP32 wake source for an RTC alarm will never fire.
-
-The shipped factory binary confirms both destination and polarity:
-
-```
-PM1 shutdown, wake by RX8130 timer  -> PM1 G0 falling edge
-```
-
-M5Unified sets the board up accordingly (`Power_Class.cpp:528` onward):
-`_rtcIntPin = GPIO_NUM_1` — note that is the **M5PM1's IRQ output to the host**, not the
-RTC line — with `setGPIOIRQMaskBits(0x1E)` to *enable GPIO0's interrupt and disable the
-other four*, `G0` configured as a plain input, and `G1` configured as a push-pull IRQ
-output toward the ESP32-S3.
-
-So the chain when the host is awake is:
-**RX8130CE `nIRQ` → M5PM1 `G0` → M5PM1 `G1` → ESP32-S3 GPIO1.**
-When the host is asleep in L1, the chain stops at the M5PM1 and the M5PM1 powers the host
-back up.
-
-## 3. Prerequisites
-
-| Item | Value |
-|---|---|
-| M5Unified | 0.2.21 — `M5.Rtc`, backed by `RX8130_Class` at **400 kHz** (`RTC_Class.cpp:60`) |
-| M5PM1 | 1.0.7, for wake configuration |
-
-The factory firmware just aliases it: `m5::RTC_Class& rtc = M5.Rtc;` (`hal.h:70`).
-
-## 4. Resources consumed
-
-| Resource | Value |
-|---|---|
-| I²C address | **`0x32`** on the shared bus at **400 kHz** (`RX8130_I2C_FREQ_HZ = 400000`) |
-| M5PM1 pin | `G0`, input, wake-enabled, falling edge |
-| ESP32-S3 GPIO | **none** directly; GPIO1 carries the M5PM1's IRQ when the host is awake |
-| Rail | `3V3_L1` — alive in state **L1** and above |
-| RTC RAM | The factory firmware uses **4 bytes from `0x20`** (`RX8130_RAM_BASE = 0x20`, `RX8130_RAM_SIZE = 4`) |
-
-Two other retention stores exist and are unused on this board: the M5PM1's **32 bytes**
-at `0xA0`–`0xBF`, and the M5IOE1's **32 bytes** at `0x70`–`0x8F`. Both survive states in
-which the ESP32-S3 is unpowered, which makes them useful for cross-sleep state — nothing
-in vendor firmware touches them.
-
-## 5. Minimal procedure (`inferred`)
-
-```cpp
-#include <M5Unified.h>
-
-void setup() {
-  M5.begin(M5.config());
-
-  auto dt = M5.Rtc.getDateTime();          // as used at app_clock.cpp:563, :1123
-  // ... set it:
-  // m5::rtc_datetime_t t{{2026,9,1,2},{12,0,0}};
-  // M5.Rtc.setDateTime(&t);               // app_clock.cpp:1043
-}
-```
-
-`M5Unified`'s `RX8130_Class` exposes `getDateTime`, `setDateTime`,
-`setTimerIRQ(uint32_t msec)`, `setAlarmIRQ(date, time)`, `getIRQstatus()`, `clearIRQ()`,
-`disableIRQ()` and **`getVoltLow()`** (`RX8130_Class.cpp:37`, `:94`, `:119`, `:212`,
-`:272`, `:280`, `:287`, `:295`).
-
-`getVoltLow()` is the one worth wiring into a first-boot path: it tells you the RTC lost
-its supply and the time is not trustworthy.
-
-## 6. Scheduled wake — two routes
-
-### 6.1 The M5PM1's own timer (simpler)
-
-The M5PM1 has an independent 31-bit second timer and does not need the RTC at all:
-
-```cpp
-pm1.timerSet(600, M5PM1_TIM_ACTION_POWERON);   // wake in 10 minutes
-pm1.shutdown();
-```
-
-Actions: `STOP`, `FLAG`, `REBOOT`, `POWERON`, `POWEROFF`. Registers `0x38`–`0x3B` counter,
-`0x3C` config, `0x3D` reload key (`0xA5`). This is the vendor's own published sketch —
-see [`power-and-sleep.md` §6.1](power-and-sleep.md#61-timed-power-off--power-on-reported-working--vendors-own-sketch).
-
-### 6.2 The RX8130CE alarm (calendar-accurate)
-
-Use the RTC when you need a wall-clock alarm — "07:30 every weekday" — rather than an
-elapsed interval:
-
-```cpp
-M5.Rtc.setAlarmIRQ(&date, &time);
-pm1.gpioSetWakeEnable(M5PM1_GPIO_NUM_0, true);
-pm1.gpioSetWakeEdge  (M5PM1_GPIO_NUM_0, M5PM1_GPIO_WAKE_FALLING);
-pm1.setLdoEnable(true);
-pm1.ldoSetPowerHold(true);       // keep L1 (and therefore the RTC) alive
-pm1.shutdown();
-```
-
-`inferred` — this composes the vendor's IMU-wake pattern with `G0` instead of `G4`. The
-factory firmware **disables** both wake sources at startup
-(`clearPm1WakeIrqState()`, `hal_board.cpp:42–43`), so it does not itself demonstrate the
-RTC-wake path end to end. The shipped binary's log string shows the path exists.
-
-### Decision table
-
-| Need | Use |
-|---|---|
-| "Wake me in N seconds" | **M5PM1 timer** (§6.1) — no RTC involvement, vendor-demonstrated |
-| "Wake me at 07:30" | **RX8130CE alarm** (§6.2) |
-| "Reboot if I hang" | M5PM1 **watchdog** — `wdtSet(sec)` / `wdtFeed()`, registers `0x0A`/`0x0B` |
-| Periodic host-side tick while awake | `setTimerIRQ(msec)` on the RTC, routed via M5PM1 `G1` → GPIO1 |
-
-## 7. Limits
-
-| Class | Limit |
-|---|---|
-| **Board** | `nIRQ` goes only to the M5PM1 (§2) |
-| **Board** | The RTC is on `3V3_L1`. **In state L0 (shipping) the RTC is not powered** — there is no separate coin cell or supercap in evidence. Time is lost on a full L0 transition |
-| **Documentation** | The only RTC datasheet mirrored by M5Stack is **Chinese-language** (`RX8130CE_cn-Register-Datasheet.pdf`) |
-| **Framework** | M5Unified drives it at 400 kHz |
-| **Observed** | Nothing. No drift, accuracy or long-term timekeeping report exists |
-
-> The L0 consequence is worth restating: the vendor's state table puts only the charger,
-> protection and `3V3_L0` in L0, with L1 (RTC + IMU) above it. So the deepest state costs
-> you the clock. If your product must keep time indefinitely, **do not go to L0** —
-> `ldoSetPowerHold(true)` keeps L1 up.
-
-## 8. Conflicts
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| RTC + [IMU](imu.md) wake | ✅ | Different M5PM1 GPIOs (`G0` / `G4`); both can be enabled |
-| RTC + [touch](touch.md) wake | ⚠ | RTC wakes from L1, touch only from L2 |
-| RTC + other I²C devices | ✅ | Distinct addresses; 400 kHz |
-| RTC + state L0 | ❌ | RTC unpowered (§7) |
-| RTC + [charger](battery-and-charging.md) bus access | ⚠ | The usual shared-bus hazard |
-
-## 9. Debugging
-
-| Symptom | Cause |
-|---|---|
-| Alarm never wakes the board | Configured on an ESP32-S3 pin instead of M5PM1 `G0` (§2) |
-| Time resets on every power cycle | You reached **L0**; the RTC rail is L1 (§7) |
-| `getVoltLow()` true | RTC supply was lost — treat the time as invalid |
-| Wake fires but the RTC is dead afterwards | `ldoSetPowerHold(true)` not set |
-| Interrupt latched forever | `clearIRQ()` after handling |
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; the RX8130CE is fitted on both C153 and C153-LITE |
-| Framework range | M5Unified 0.2.21 · M5PM1 1.0.7 |
-| Evidence | Wiring: **schematic**. Wake destination and polarity: **shipped binary + firmware**. `M5.Rtc` API: **read from `RX8130_Class`**. §6.2 sketch: **`inferred`** — no vendor code demonstrates RTC wake end to end |
-| Confidence | High on the interrupt path; medium on the alarm-wake sketch; **none on accuracy** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`power-and-sleep.md`](power-and-sleep.md) · [`imu.md`](imu.md) · [`../power-architecture.md#wake-sources-and-how-they-reach-the-m5pm1`](../power-architecture.md#wake-sources-and-how-they-reach-the-m5pm1)
-- [`components/seiko-epson/rx8130ce/`](../../../../components/seiko-epson/rx8130ce/) (stub) · [`components/m5stack/m5pm1`](../../../../components/m5stack/m5pm1/README.md)
diff --git a/devices/m5stack/papermono/features/touch.md b/devices/m5stack/papermono/features/touch.md
deleted file mode 100644
index 2b17be8..0000000
--- a/devices/m5stack/papermono/features/touch.md
+++ /dev/null
@@ -1,202 +0,0 @@
-# Touch — M5Stack PaperMono
-
-> **How do I read touch input, and why can I not press the edge of the screen?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-## 1. Capability summary and the hardware path
-
-A self-capacitance projected-capacitive touch layer laminated to the e-paper stack,
-read by a FocalTech controller on the shared system I²C bus, with an interrupt line
-straight to the ESP32-S3 that doubles as a **wake source**.
-
-```
-FT6336G (I2C 0x38)  ──SDA/SCL──▶ system I²C bus (GPIO47/48)
-      │  INT ─────────────────▶ ESP32-S3 GPIO4     (wake source)
-      │  RSTN ◀──────────────── M5IOE1 IO6
-      └  VDD  ◀──────────────── TP_VDD, AW35122 load switch, enabled by M5IOE1 IO13
-```
-
-| Element | Part | Record |
-|---|---|---|
-| Touch controller | FocalTech **FT6336G**, I²C `0x38` | [`components/focaltech/ft6336g`](../../../../components/focaltech/ft6336g/README.md) |
-| Reset + power enable | M5IOE1 `IO6` / `IO13` | [`components/m5stack/m5ioe1`](../../../../components/m5stack/m5ioe1/README.md) · [`io-expander.md`](io-expander.md) |
-| Power switch | Awinic `AW35122` load switch (`U18`) | [`components/awinic/aw35122`](../../../../components/awinic/aw35122/README.md) |
-| Connector | `J4`, 8-pin FPC | [`../pinouts-and-buses.md`](../pinouts-and-buses.md#connectors) |
-
-## 2. ⚠ The effective touch area is smaller than the display
-
-**This is the fact that will cost you a UI redesign if you learn it late.**
-
-M5Stack, on the product page:
-
-> "The touch IC firmware internally shrinks the touch boundary. The effective touch
-> coordinate range is limited to: **X-axis: 5 ~ 475** (total width 480 px),
-> **Y-axis: 5 ~ 795** (total height 800 px)."
-
-| Axis | Panel | **Usable touch** | Dead border |
-|---|---|---|---|
-| X | 0 – 479 (480 px) | **5 – 475** (471 px) | 5 px leading, 4 px trailing |
-| Y | 0 – 799 (800 px) | **5 – 795** (791 px) | 5 px leading, 4 px trailing |
-
-This is a property of firmware **inside the touch controller**. It is not mechanical, it
-is not a driver setting, and **a host cannot widen it.** Consequences:
-
-- **Never place a hit target within 5 px of any screen edge.** A button drawn flush to
-  the edge has a strip that cannot be pressed.
-- **Edge-swipe gestures that begin at coordinate 0 will never register.** If your UI
-  design leans on edge swipes, it will not work here.
-- Full-screen "tap anywhere to wake" is fine. Corner affordances are not.
-
-### Does M5GFX compensate? No — and that is the right answer
-
-M5GFX configures the touch object with `x_min = 0, x_max = 479, y_min = 0, y_max = 799`
-(`M5GFX/src/M5GFX.cpp:2135–2138`). That is an **identity mapping** — the controller's raw
-coordinates are passed through unscaled.
-
-So there is **no scale error and no systematic offset**: reported coordinates are true
-pixel coordinates. The only consequence is that values below 5 or above 475 / 795 are
-never emitted. This resolves an open question left in the
-[FT6336G component record §4.4](../../../../components/focaltech/ft6336g/README.md),
-which speculated about a possible ~2 % scale error from a full-range assumption. There is
-no rescale, so there is no such error. `executed-success` on the source read;
-`not-tested` on hardware.
-
-## 3. Prerequisites
-
-| Item | Value |
-|---|---|
-| M5Unified / M5GFX | 0.2.21 / 0.2.28 — `lgfx::Touch_FT5x06` is registered automatically for `board_M5PaperMono` |
-| Power state | **L3B** — `TP_VDD` comes up via M5IOE1 `IO13` during `M5.begin()` |
-| I²C | Bus configured by M5GFX at **400 kHz** for the touch object, on `I2C_NUM_1` |
-
-## 4. Resources consumed
-
-| Resource | Value |
-|---|---|
-| I²C address | **`0x38`** on the shared bus (GPIO47 SDA / GPIO48 SCL) |
-| I²C port / speed | `I2C_NUM_1`, `freq = 400000` in the M5GFX touch config |
-| ESP32-S3 GPIO | **GPIO4** — `INT`, also the deep-sleep touch-wake pin |
-| Expander pins | `IO6` reset, `IO13` `TP_VDD` enable |
-| Rail | `TP_VDD` (state L3B) |
-
-## 5. Minimal procedure (`inferred`)
-
-```cpp
-#include <M5Unified.h>
-
-void setup() {
-  M5.begin(M5.config());          // touch comes up with the display
-  M5.Display.setEpdMode(epd_mode_t::epd_fast);
-}
-
-void loop() {
-  M5.update();                    // required - polls the touch controller
-  if (M5.Touch.getCount() > 0) {
-    auto t = M5.Touch.getDetail();
-    if (t.wasPressed()) {
-      M5.Display.fillCircle(t.x, t.y, 6, TFT_BLACK);
-      M5.Display.display();
-    }
-  }
-}
-```
-
-`M5.Touch.getCount()`, `M5.Touch.getDetail()` and `M5.Touch.getTouchPointRaw()` are the
-three entry points the vendor's own firmware uses
-(`M5PaperMono-UserDemo/main/hal/hal_touch.cpp:15`, `:20`, `:28`).
-
-**Do not redraw the whole screen on every touch.** See
-[`epaper-display.md` §8](epaper-display.md#8-panel-safety--the-rules-that-are-not-optional):
-one full refresh per ten partials, and never a continuous partial-refresh loop. Touch
-handling is exactly the code path that produces such a loop by accident.
-
-## 6. Wake on touch
-
-Sheet 1 of the schematic marks touch as an **L2 wake source**, and M5Unified implements
-it in an unusual way worth knowing about:
-
-```cpp
-// M5Unified/src/utility/Power_Class.cpp:1654, :1786
-uint_fast8_t wpin = _wakeupPin;                 // GPIO_NUM_1 (M5PM1 IRQ) by default
-if (touch_wakeup && (M5.getBoard() == board_t::board_M5PaperMono)) {
-  wpin = GPIO_NUM_4;                            // ... becomes the touch INT instead
-}
-```
-
-**The `touch_wakeup` argument to `M5.Power.deepSleep()` does not add touch wake — it
-substitutes it.** On this board it *replaces* the M5PM1 IRQ (GPIO1) as the EXT0 wake pin
-with the touch INT (GPIO4). If you pass `touch_wakeup = true`, you get touch wake and you
-lose the M5PM1's interrupt-driven wake path on the same call. `executed-success` on the
-source read; `not-tested`.
-
-Deeper sleep states (L1, L0) power the ESP32-S3 down entirely, and touch is not among the
-sources that reach the M5PM1 — those are the power button, the
-[RTC](rtc.md) and the [IMU](imu.md). See [`power-and-sleep.md`](power-and-sleep.md).
-
-## 7. Silicon / board / framework / observed limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (FT6336G)** | **2 touch points maximum**, self-capacitance. No reliable independent tracking of two points — the classic two-point ghosting ambiguity applies. No pinch-zoom you should trust |
-| **Silicon (FT6336G)** | 31 channels, panels **≤ 4.0 inch**. The 3.97" panel is at the ceiling |
-| **Silicon (FT6336G)** | Controller firmware inset of 5 px on every edge (§2) — **unchangeable** |
-| **Silicon (FT6336G)** | "Monitor mode" closes the I²C port; design for interrupt-driven reads rather than tight polling |
-| **Board** | `RSTN` is behind the I²C expander. **Resetting touch requires a working I²C bus** — awkward when the reason you want to reset is that the bus is unhappy |
-| **Board** | `TP_VDD` can be cut (M5IOE1 `IO13`); after a power cycle the driver must be re-initialised |
-| **Framework** | M5GFX passes raw coordinates through unscaled (§2) |
-| **Observed** | None. **Nobody has reported touch behaviour on real hardware** beyond one third-party project claiming touch works |
-
-### The FT6336G datasheet does not contain the register map or the I²C address
-
-Worth stating because it changes how you plan: you **cannot** write a driver for this
-part from FocalTech's datasheet. Use `lgfx::Touch_FT5x06`, LVGL's FT6x06 driver,
-`Adafruit_FT6206`, or read Linux's `drivers/input/touchscreen/edt-ft5x06.c`, which is the
-de-facto public documentation of the register interface.
-
-## 8. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| Touch + [display](epaper-display.md) | ✅ intended | M5GFX resets both together by pulsing M5IOE1 `IO5`/`IO6` |
-| Touch + six other I²C devices | ✅ | All addresses distinct. FT6336G tolerates 10 kHz–400 kHz, and the bus runs 100 kHz (IMU, M5PM1, M5IOE1) to 400 kHz (RTC, NFC, touch) per transaction |
-| Touch + [NFC](nfc.md) | ⚠ bandwidth, not address | NFC polling is chatty on the same single bus. No measurement exists |
-| Touch + [charger](battery-and-charging.md) access | ⚠ | Gating the IP2315 onto the bus is the one documented bus-stability hazard on this board. Keep it brief |
-| Touch wake + M5PM1 IRQ wake | ❌ mutually exclusive on one `deepSleep()` call | §6 — `touch_wakeup` substitutes GPIO4 for GPIO1 |
-| Touch + deep sleep below L2 | ❌ | Touch is not a wake source that reaches the M5PM1 |
-
-## 9. Debugging
-
-| Symptom | Cause |
-|---|---|
-| No touches at all | `TP_VDD` not enabled (M5IOE1 `IO13`), or touch reset (`IO6`) still asserted |
-| Touch worked, then stopped after you poked the expander | You changed `IO6` or `IO13`. M5Stack's own warning: *"The pins associated with the e-paper display, touch controller, microSD, and PDM microphone are already used by M5Unified. Before modifying them, ensure that the corresponding peripheral has stopped"* |
-| A button at the screen edge never fires | §2 — the 5 px dead border |
-| Coordinates look mirrored or transposed | Display rotation vs `offset_rotation = 0` on the touch object; the panel is rotated in software but the touch layer is not |
-| Second finger tracks erratically | Self-capacitance two-point ghosting — **silicon limit** |
-| `0x38` missing from an I²C scan | Power (`IO13`) is off, or the scan ran before `M5.begin()` |
-
-## 10. Unresolved questions
-
-- **`J4`'s pin ordering was not resolved** from the schematic.
-- **Nobody has reported real touch accuracy, latency or rejection behaviour** on a
-  PaperMono. One third-party project
-  (`MagicCube/free-ink-on-paper-mono`) claims a verified touch path on a Lite; no detail.
-- Whether the display's rotation and the touch layer's orientation agree in every
-  `setRotation()` value was not checked. A third-party ESPHome port explicitly labels its
-  display/touch rotation section *"hipótesis de prueba"* — test hypothesis.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; touch is fitted on both C153 and C153-LITE |
-| Framework range | M5Unified 0.2.21 · M5GFX 0.2.28 (touch is registered by board autodetect) |
-| Evidence | Coordinate limit: **vendor-documented**, `reported-working`. Wiring and M5GFX config: **read from source**. Code sketch: **`inferred`** |
-| Confidence | High on the coordinate limit and the wiring; **none on real-world touch quality** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md#i²c-bus--the-one-shared-bus`](../pinouts-and-buses.md#i²c-bus--the-one-shared-bus)
-- [`epaper-display.md`](epaper-display.md) · [`power-and-sleep.md`](power-and-sleep.md) · [`io-expander.md`](io-expander.md)
-- [`components/focaltech/ft6336g`](../../../../components/focaltech/ft6336g/README.md) · [`components/awinic/aw35122`](../../../../components/awinic/aw35122/README.md)
diff --git a/devices/m5stack/papermono/features/usb-and-serial.md b/devices/m5stack/papermono/features/usb-and-serial.md
deleted file mode 100644
index 9da2443..0000000
--- a/devices/m5stack/papermono/features/usb-and-serial.md
+++ /dev/null
@@ -1,220 +0,0 @@
-# USB and serial — M5Stack PaperMono
-
-> **How do I flash it, get a serial console, and why will I not find a reset button?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-## 1. Capability summary and the hardware path
-
-Native USB from the ESP32-S3, plus a conventional UART0, plus a USB-C connector that
-carries power and data and **nothing else**.
-
-```
-USB-C (U1, TYPEC-302-BRP16SC08)
-   ├─ D-/D+ ──▶ FT1 common-mode filter ──▶ ESP32-S3 GPIO19 / GPIO20   (native USB)
-   └─ VBUS  ──▶ AW32901FCR OVP 5.95 V  ──▶ IP2315 charger
-
-ESP32-S3 GPIO43 (U0TXD, 499 Ω series R30) ──┐
-ESP32-S3 GPIO44 (U0RXD)                   ──┴─ UART0, not brought to any connector
-
-M5PM1 BOOT_OUT_OD ──▶ ESP32-S3 GPIO0   (boot strap)
-M5PM1 SOC_RESET   ──▶ ESP32-S3 CHIP_PU (reset)
-```
-
-| Signal | GPIO | Note |
-|---|---|---|
-| USB D− | **GPIO19** | via `FT1` common-mode filter |
-| USB D+ | **GPIO20** | via `FT1` |
-| UART0 TX | **GPIO43** | 499 Ω series (`R30`) |
-| UART0 RX | **GPIO44** | |
-| Boot strap | **GPIO0** | driven by the **M5PM1**, not a button |
-| Reset | `CHIP_PU` | driven by the **M5PM1** |
-
-**None of these four appear on the vendor's product-page pin tables.** USB (GPIO19/20)
-and UART0 (GPIO43/44) are established from the schematic only — the product page is
-otherwise accurate but omits them.
-
-## 2. ⚠ There is no USB-PD
-
-The connector carries the standard **5.1 kΩ CC pulldowns** (`R14` on CC2) advertising a
-plain sink, but the **IP2315's own `CC1`/`CC2` sense pins are unpopulated** (`R1`, `R2`
-marked `NC`). Combined with the 5.95 V OVP upstream, this is a **plain 5 V input** and the
-charger's PD capability is deliberately depopulated.
-
-| What is present | What is not |
-|---|---|
-| CC pulldowns on the **connector** → the board advertises itself as a 5 V sink | CC sense resistors on the **charger** → no PD negotiation of any kind |
-| Over-voltage protection at 5.95 V | Any voltage above 5 V |
-
-Practical consequence: **a PD-only source that will not supply 5 V without negotiation
-will not charge this board.** See [`battery-and-charging.md`](battery-and-charging.md).
-
-*(Two earlier readings of this circuit disagreed — one concluded there were no CC
-resistors at all. Both resistor groups exist and they are on different parts. Recorded so
-the question is not re-opened.)*
-
-## 3. ⚠ Download mode is the power button — there is no reset button
-
-```
-Hold the power button ~2 seconds until the red LED blinks, then release.
-```
-
-This is stated by the **product page** (EN, zh_CN and ja) and by the **UiFlow2 page**.
-The **Arduino quick-start page contradicts it**, saying *"press and hold the reset button
-on the side of the device"*.
-
-**The Arduino page is wrong.** The schematic shows exactly three switches on the KEY/RGB
-sub-board — `S1` (`PWR_BTN`), `S2` (`G2_KEY1`), `S3` (`G3_KEY2`) — and **no separate reset
-button**. The specification table lists *"2× user buttons + 1× power button (ON / OFF /
-RESET / BOOT)"*: one physical multi-function button. Resolved in
-[`../gaps-and-conflicts.md` R4](../gaps-and-conflicts.md#r4--download-mode-control--resolved-on-the-balance-of-evidence);
-marked resolved but `not-tested`.
-
-**The mechanism matters.** GPIO0 is driven by the M5PM1's open-drain `BOOT_OUT_OD`, and
-`CHIP_PU` carries `SOC_RESET` from the same chip. So **the power manager, not a physical
-button, puts the ESP32-S3 into download mode.** If the M5PM1 is unhappy, you cannot flash
-the board — and the M5PM1's own firmware-update mode is a separate thing again
-(`SYS_CMD` `0x0C` `CMD=11`, or a long press, lockable via `BTN_CFG_1[7] DL_LOCK`).
-
-Other button behaviour: one short press = power on / reset; two presses in succession =
-power off. Third-party projects disable the single-click reset — see
-[`buttons-and-rgb-led.md` §6](buttons-and-rgb-led.md#6-the-power-button).
-
-## 4. ⚠ Three strapping pins carry user-facing signals
-
-| GPIO | Strap | Also carries |
-|---|---|---|
-| **GPIO0** | boot mode | driven by M5PM1 `BOOT_OUT_OD` — by design |
-| **GPIO3** | strapping | **User button B** |
-| **GPIO45** | strapping (`VDD_SPI`) | **PDM microphone clock** |
-| **GPIO46** | strapping (boot messages) | **PDM microphone data** |
-
-Driving the microphone or holding button B during reset perturbs the straps. The vendor
-firmware does not appear to guard against this. `inferred` from the pin map,
-`not-tested`. The factory firmware does explicitly release the mic pins before
-reconfiguring them — see [`microphone.md` §2](microphone.md#-2-both-microphone-pins-are-esp32-s3-strapping-pins).
-
-## 5. Serial console and USB CDC
-
-The published build configuration selects **native USB CDC as the console**:
-
-```ini
-build_flags = -DARDUINO_USB_CDC_ON_BOOT=1
-              -DARDUINO_USB_MODE=1
-```
-
-So `Serial` is the USB CDC device, not UART0. Consequences of native USB, which are
-normal and not faults:
-
-- **The serial port disappears** on reset, crash, sleep or any USB reconfiguration, and
-  reappears as a new device. Auto-reconnecting terminals help.
-- Early boot output before CDC enumerates is lost. **UART0 on GPIO43/44 does not vanish**
-  and is the reliable channel for boot-time debugging — but it is **not brought to any
-  connector**, so using it means probing the board.
-- `CORE_DEBUG_LEVEL=0` in the vendor's own snippet means M5GFX's diagnostic messages —
-  including `"M5PaperMono need OPI-PSRAM enabled"` — are compiled out. **Raise it when
-  something does not work.**
-
-## 6. Flashing
-
-| Route | Notes |
-|---|---|
-| **`idf.py -p PORT flash`** | The OTP demo README's own instruction: `idf.py set-target esp32s3` → `idf.py build` → `idf.py -p PORT flash`. `reported-working` (vendor README); **not run here** |
-| **PlatformIO** | Use the published `[env:m5stack-papermono]` block. `board = esp32-s3-devkitm-1` — there is **no dedicated PlatformIO board definition** |
-| **Arduino IDE** | Install the M5Stack board package, select the **`M5PaperMono`** board. Corroborated independently: the shipped binary contains `[Autodetect] board_M5PaperMono` |
-| **M5Burner / EasyLoader** | The vendor's GUI route; also how UiFlow2 firmware is installed |
-
-Flash geometry: **16 MB**, single `factory` app at `0x10000` of size `0xF00000`
-(15 MiB), plus `nvs` 24 KB at `0x9000` and `phy_init` 4 KB at `0xf000`. **No OTA slot, no
-filesystem partition** in either vendor project — so **the shipped firmware is not
-field-updatable over the air as built**.
-
-> **QIO vs DIO.** The vendor's PlatformIO snippet specifies `qio_opi`; both shipped
-> binaries report **DIO** in their ESP image headers. The hardware supports QIO — all
-> four flash data lines are routed and the `Q` in `XM25UH128DHIQT` denotes a factory-set
-> QE bit — and `sdkconfig.defaults` pins no flash mode, so DIO is an ESP-IDF default, not
-> a hardware limit. Not a defect. Resolved in
-> [`../gaps-and-conflicts.md` R2](../gaps-and-conflicts.md#r2--qio-versus-dio-flash--resolved).
-
-## 7. Resources consumed
-
-| Resource | Value |
-|---|---|
-| ESP32-S3 GPIO | GPIO19, GPIO20 (USB); GPIO43, GPIO44 (UART0) |
-| Peripheral | USB-Serial-JTAG / TinyUSB; `UART_NUM_0` |
-| Connector | `U1` `TYPEC-302-BRP16SC08` |
-| Filter | `FT1` common-mode choke on D±  |
-
-USB is **not** used for anything else on this board — no UVC, no MSC, no HID in any
-vendor firmware. The silicon supports them; nobody has demonstrated them here.
-
-## 8. Limits
-
-| Class | Limit |
-|---|---|
-| **Silicon (ESP32-S3)** | Native USB 1.1 full speed. No USB host in any vendor configuration |
-| **Board** | **No USB-PD** (§2). 5 V only, OVP at 5.95 V |
-| **Board** | UART0 is not exposed on any connector |
-| **Board** | Reset and boot strap are owned by the M5PM1 — you cannot force download mode without it |
-| **Framework** | `CORE_DEBUG_LEVEL=0` in the vendor snippet hides the diagnostics you need |
-| **Framework** | No OTA partition as shipped |
-| **Observed** | Nothing. **No one has reported a flashing session on real hardware in any source located** |
-
-## 9. Conflicts
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| USB CDC + UART0 | ✅ independent | Different peripherals and pins |
-| USB + [charging](battery-and-charging.md) | ✅ simultaneous | Same connector, separate paths |
-| Download mode + [button B](buttons-and-rgb-led.md) held | ⚠ | GPIO3 strap (§4) |
-| Download mode + [microphone](microphone.md) active across reset | ⚠ | GPIO45/46 straps (§4) |
-| USB CDC + deep sleep | ⚠ expected | The CDC device disappears; this is normal |
-| USB + a PD-only charger | ❌ | §2 |
-
-## 10. Debugging
-
-| Symptom | Cause |
-|---|---|
-| Cannot find the reset button | **There isn't one.** Use the power button (§3) |
-| Board will not enter download mode | Hold the power button until the **red LED blinks** — releasing early does nothing |
-| Serial port vanishes | Native USB. Expected |
-| No boot log at all | `CORE_DEBUG_LEVEL=0`; or CDC had not enumerated yet. UART0 does not have this problem |
-| Blank screen, everything else fine | **Look for `M5PaperMono need OPI-PSRAM enabled`** — which you will not see at debug level 0. See [`epaper-display.md` §7](epaper-display.md#7-octal-psram-is-mandatory--and-the-failure-looks-like-dead-hardware) |
-| Board does not charge from a given supply | PD-only source (§2) |
-| Flashed image will not run | Check `board_build.arduino.memory_type = qio_opi` and the 16 MB partition scheme |
-
-## 11. Recovering the factory image
-
-Two images were retrieved from the M5Burner public API and are retained in
-[`../artifacts/firmware/`](../artifacts/firmware/):
-
-| Image | Bytes | Build identity |
-|---|---|---|
-| `C153-PaperMono-UserDemo-v1.2.bin` | 2,868,208 | `PaperMono-UserDemo`, version **`c78f6c5-dirty`**, IDF v5.5.1, 2026-08-06 |
-| `crosspoint-paper-mono-cjk-1.5.0-RC.bin` | 10,319,500 | third-party `crosspoint-reader-mono` e-reader |
-
-> The official image reports **`-dirty`**: built from an uncommitted tree, therefore **not
-> reproducible from any published commit** of `m5stack/M5PaperMono-UserDemo`. That is why
-> the bytes are retained rather than referenced.
->
-> Also: the vendor link labelled **"PaperMono Factory Reset Firmware"** resolves to a
-> firmware record named **"PaperMono UserDemo"** — the same image, differently labelled.
-> It restores the demo application; it is not a distinct factory-reset payload.
-
-How to fetch such images yourself is in
-[`vendors/m5stack` §M5Burner API](../../../../vendors/m5stack/README.md).
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; USB, UART and boot path are identical on C153 and C153-LITE |
-| Framework range | ESP-IDF 5.5.1 · arduino-esp32 3.3.10 · PlatformIO `espressif32@6.12.0` |
-| Evidence | USB/UART pins: **schematic only** (absent from vendor pin tables). Download mode: **vendor-documented**, `reported-working`, with one contradicting vendor page. Flash geometry: **read from both projects' `partitions.csv` and from the shipped binaries' partition tables**, `executed-success` |
-| Confidence | High on wiring and partitioning; **nothing about flashing has been executed on a device** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`../pinouts-and-buses.md#boot-reset-and-download-mode`](../pinouts-and-buses.md#boot-reset-and-download-mode) · [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md)
-- [`battery-and-charging.md`](battery-and-charging.md) · [`buttons-and-rgb-led.md`](buttons-and-rgb-led.md) · [`microphone.md`](microphone.md) · [`power-and-sleep.md`](power-and-sleep.md)
-- [`components/xmc/xm25uh128dhiqt`](../../../../components/xmc/xm25uh128dhiqt/README.md) · [`components/espressif/esp32-s3r8`](../../../../components/espressif/esp32-s3r8/README.md)
diff --git a/devices/m5stack/papermono/features/wifi-and-bluetooth.md b/devices/m5stack/papermono/features/wifi-and-bluetooth.md
deleted file mode 100644
index d74ddbd..0000000
--- a/devices/m5stack/papermono/features/wifi-and-bluetooth.md
+++ /dev/null
@@ -1,217 +0,0 @@
-# Wi-Fi and Bluetooth — M5Stack PaperMono
-
-> **How do I get on the network?**
-> Hardware revision **V0.6.2** · snapshot **2026-09-01** · nothing tested on hardware.
-
-**This is a short guide.** The radio is the ESP32-S3's own, there is nothing
-PaperMono-specific about using it, and no measurement of any kind exists for this board.
-What follows is the board-specific delta and nothing else.
-
-## 1. Capability summary and the hardware path
-
-**2.4 GHz Wi-Fi and Bluetooth LE, both from the ESP32-S3R8 die**
-([`components/espressif/esp32-s3r8`](../../../../components/espressif/esp32-s3r8/README.md)),
-which is a bare QFN die on the main board rather than a shielded module.
-
-| Item | Status |
-|---|---|
-| **Wi-Fi 2.4 GHz** | Listed in M5Stack's specification table |
-| **Bluetooth LE** | **A silicon capability M5Stack never lists.** Not in the spec table, not in the feature list, not in the comparison table |
-| Wi-Fi 5 GHz / 6 | Not present — ESP32-S3 is 2.4 GHz only |
-| Bluetooth Classic | Not present — ESP32-S3 has **no** BR/EDR. No A2DP, HFP or SPP |
-| Antenna | Not identified in any retrieved document (see §5) |
-
-> **"Bluetooth 5.0 LE + Mesh" is a publication's inference, not a vendor spec.** One
-> launch article printed it; M5Stack's own specification table does not mention Bluetooth
-> at all. BLE certainly works — it is in the silicon — but nobody has demonstrated it on
-> this board, and no vendor statement backs any particular profile claim. Recorded in
-> [`../gaps-and-conflicts.md`](../gaps-and-conflicts.md#claims-examined-and-rejected).
->
-> Independent corroboration that BLE is at least being used: one third-party project,
-> `EggUncle/PaperMonoCalendar`, describes BLE activity tiles — though its README is
-> explicit that its preview images are software-generated, **not device photographs**.
-
-## 2. Prerequisites
-
-Nothing board-specific. arduino-esp32 3.3.10 or ESP-IDF 5.5.1, `WiFi.h` or
-`esp_wifi`/NimBLE as usual. The vendor's `sdkconfig.defaults` additionally enables
-`CONFIG_LWIP_IP_FORWARD=y` and `CONFIG_LWIP_IPV4_NAPT=y` — NAT/routing — for reasons the
-firmware never uses. Inherited from a template, `inferred`.
-
-## 3. Minimal procedure
-
-The factory firmware's Wi-Fi scan app is plain arduino-esp32 (`app_wifi_scan.cpp`):
-
-```cpp
-#include <WiFi.h>
-
-WiFi.mode(WIFI_STA);
-WiFi.disconnect(false, false);
-WiFi.scanDelete();
-bool started = (WiFi.scanNetworks(/*async=*/true, /*show_hidden=*/true) == WIFI_SCAN_RUNNING);
-// ... later
-int n = WiFi.scanComplete();
-for (int i = 0; i < n; ++i) {
-  auto ssid = WiFi.SSID(i);
-  auto rssi = WiFi.RSSI(i);
-  bool secure = WiFi.encryptionType(i) != WIFI_AUTH_OPEN;
-}
-WiFi.scanDelete();
-```
-
-**The asynchronous scan matters on this board more than on most.** A blocking scan is
-seconds of nothing, and on an e-paper device you cannot show a spinner cheaply — every
-progress update is a panel refresh, and
-[refresh discipline](epaper-display.md#8-panel-safety--the-rules-that-are-not-optional)
-says you must not loop partial refreshes. Scan asynchronously and redraw once.
-
-Standard approaches apply unchanged for everything else: STA/AP mode, WPA2/WPA3, ESP-NOW,
-NimBLE or Bluedroid, provisioning. There is no PaperMono-specific setup step.
-
-## 4. Resources consumed
-
-| Resource | Value |
-|---|---|
-| ESP32-S3 GPIO | **none** — the radio is internal |
-| RAM | The Wi-Fi and BLE stacks take internal SRAM out of the 512 KB, competing with the display driver's own allocations |
-| PSRAM | Not required by the radio, but the display **mandates OPI PSRAM** anyway |
-| Power | Unquantified. Wi-Fi TX bursts are the largest transient load on the board |
-
-## 5. Limits
-
-| Class | Limit |
-|---|---|
-| **Silicon** | 2.4 GHz only; **no Bluetooth Classic**; single radio shared between Wi-Fi and BLE with the usual coexistence scheduling |
-| **Board** | The ESP32-S3 is a **bare die, not a shielded module**, alongside a [LoRa module](lora.md) and an [NFC front end](nfc.md) — three radios in a 62 × 101 × 8 mm slab |
-| **Board** | **No antenna part is identified** in any retrieved document. The LoRa module has a stated FPC antenna; the 2.4 GHz antenna is not described anywhere |
-| **Board** | **No certification identifier of any kind is published.** `docs.m5stack.com/en/certification` returns HTTP 200 with **zero** matches for `PaperMono` and `C153` — a verified negative, not a failed search |
-| **Framework** | None specific |
-| **Observed** | **Nothing at all.** No throughput, range, sensitivity or power measurement exists from M5Stack or from any independent source |
-
-## 6. Conflicts and simultaneous use
-
-| Combination | Verdict | Mechanism |
-|---|---|---|
-| **Wi-Fi + [LoRa](lora.md)** | ✅ **they do not share a radio** | Wi-Fi/BLE is 2.4 GHz on the ESP32-S3 die; LoRa is **sub-GHz (868–923 MHz)** on a separate SX1262 module with its own antenna. There is no RF contention between them and no shared peripheral — LoRa is on `SPI3_HOST`, the radio is internal. The only shared resources are CPU time and the power budget |
-| Wi-Fi + BLE | ⚠ coexistence | One 2.4 GHz radio, time-sliced. Standard ESP32-S3 behaviour; enable modem sleep |
-| **Wi-Fi + [display](epaper-display.md) refresh + [microSD](microsd.md)** | ⚠ **untested and worth testing** | No pin conflict whatsoever. The contention is GDMA channels, PSRAM bandwidth and the L3B rail during a multi-second refresh. **Nobody has run this combination.** See [`../resources-and-conflicts.md`](../resources-and-conflicts.md) |
-| Wi-Fi + [battery](battery-and-charging.md) | ⚠ unquantified | TX bursts on a 1150 mAh cell with no published current figure |
-| Wi-Fi + [NFC](nfc.md) | ✅ no RF interaction | 13.56 MHz vs 2.4 GHz. Both compete for CPU and the single I²C bus, not for spectrum |
-| Wi-Fi + [sleep](power-and-sleep.md) | ✅ standard | Modem sleep, then the M5PM1 states below it |
-
-## 7. Debugging
-
-Nothing board-specific. The one PaperMono-flavoured trap is that
-`CORE_DEBUG_LEVEL=0` in the vendor's published build flags hides the logs you would use
-to diagnose anything — see [`usb-and-serial.md`](usb-and-serial.md).
-
-## 7b. A working BLE image-transfer protocol — third-party, added 2026-09-11
-
-`ciniml/paper_name_plate` implements full-screen image push over BLE in Rust
-(`esp-radio` + `bleps`, `src/app/ble.rs`). Dated 2026-09-04 in its design
-document and described as implemented with a measured figure — **~12–14 s for a
-full screen from a PC** — though it carries no explicit hardware-verified stamp.
-Recorded as *reported working*, not verified.
-
-It is worth documenting because it solves three problems this board actually has.
-
-### Protocol v2 — a windowed, acknowledged transfer
-
-```
-START  : 10 w h len crc32 ack_every
-DATA   : off:u16 | payload          (BLE Write Command, sent ack_every at a time)
-STATUS : state received expected    (notification — ACK/NAK)
-COMMIT : CRC32 verified, notified, then the display updates
-```
-
-Out-of-order DATA is **discarded and the expected offset is notified**, so the
-client rewinds rather than the device reassembling. The same windowed mechanism
-carries text content via `CTRL 11 len crc32 ack_every`, sending UTF-8
-`name\nemail\ngithub\nx\nnote\nurl`.
-
-### Two implementation details that are not obvious
-
-> 「GATT テーブルは手組みで DATA/CTRL に Write-Without-Response(0x04) を宣言
-> （Android Chrome が高速書き込みを許可する条件）。bleps は `mtu128`（`Data` の 256B
-> バッファを超えないため）。」
-
-*"The GATT table is hand-assembled to declare **Write-Without-Response (0x04)** on
-DATA/CTRL — **the condition under which Android Chrome permits fast writes**.
-`bleps` is set to `mtu128` so as not to exceed `Data`'s 256-byte buffer."*
-
-The first is a browser-compatibility constraint, not a BLE one: **Web Bluetooth
-on Android Chrome only grants fast writes if the characteristic advertises
-Write-Without-Response.** That is the kind of detail that costs a day.
-
-### BLE and NFC contend for one core
-
-> 「BLE と NFC タグエミュレーションは 1 コアで競合するため、BLE 接続中は NFC 待受を
-> 止めて BLE を優先する」
-
-*"BLE and NFC tag emulation contend on a single core, so while BLE is connected
-the NFC listen is stopped and BLE is prioritised"* (`tick_light`). During
-reception everything except the HCI pump is halted.
-
-**This is a real constraint for anyone planning to run both**, and it is not
-visible from the schematic — it is a CPU-time conflict, not a bus or pin one.
-Compare [`nfc.md`](nfc.md) and the resource table in
-[`../resources-and-conflicts.md`](../resources-and-conflicts.md).
-
-### The memory ceiling is the interesting part
-
-> 「ヒープ ~155KB に BLE スタック + 受信画像 48KB + 表示中画像 48KB は入らないため、
-> 8KB を超える画像は描画・保存後にヒープから捨て、再描画時にフラッシュから読み直す」
-
-*"A ~155 KB heap cannot hold the BLE stack plus a 48 KB received image plus a
-48 KB displayed image, so images over 8 KB are dropped from the heap after being
-drawn and saved, and re-read from flash on redraw"* (`draw_plate` / `trim_image`).
-Flash writes split header and data into two writes **to avoid making a copy**.
-
-This is a concrete data point on the recurring PaperMono question of whether
-PSRAM is needed: **a project that does not enable PSRAM has to stream through
-flash to fit two framebuffers and a BLE stack.** See
-[`power-and-sleep.md`](power-and-sleep.md) and the PSRAM discussion in
-[`epaper-display.md`](epaper-display.md).
-
-### Power behaviour reported alongside it
-
-- Main-loop busy-wait replaced with esp-rtos task sleep (idle hook = WFI, 1 kHz
-  tick). Their heartbeat reports `idle=NN%` — **~98 % at rest**.
-- NFC chip accessed over I²C **only** when its IRQ pin (GPIO6) is high, during a
-  reader exchange, or on a 250 ms safety poll. Touch read only when INT (GPIO4)
-  is low. HCI pumped only when the receive queue is non-empty.
-- BLE advertising interval **200–250 ms**. TF card power (`TF_EN`) switched off.
-- **Deep sleep** after 120 s idle **and** 60 s since boot **and** USB host absent
-  — the last detected via the **USB-JTAG SOF frame counter**. Wake sources are
-  RTC-IO: NFC IRQ (GPIO6 high), touch INT (GPIO4 low), buttons A/B (GPIO2/3 low),
-  plus a 6-hour timer. Wake is a reset, and `run()` checks
-  `reset_reason == CoreDeepSleep` to skip the e-paper initial refresh and
-  frontlight blink, since the panel holds its image.
-
-Image transfer over NFC also exists for small images (**≤ ~630 B**), as an
-`image/x-plate` MIME record or `B64:<base64>` text — see [`nfc.md`](nfc.md).
-
-## 8. What is not established
-
-- **No Wi-Fi or BLE measurement of any kind exists for this board.**
-- **No antenna is documented.** Type, placement, gain and the effect of the metal-adjacent
-  handheld form factor are all unknown.
-- **No regulatory approval is published**, for Wi-Fi, BLE or LoRa.
-- Whether any BLE profile has been demonstrated on a real device — one third-party
-  project claims BLE tiles but shows no hardware.
-
-## Applicability
-
-| Field | Value |
-|---|---|
-| Hardware revision | **V0.6.2**; identical on C153 and C153-LITE |
-| Framework range | arduino-esp32 3.3.10 · ESP-IDF 5.5.1 |
-| Evidence | Capability: **silicon-level**, plus M5Stack's Wi-Fi spec line. Scan sketch: **read from vendor source** (`app_wifi_scan.cpp`). Everything performance-related: **absent** |
-| Confidence | High that it works (it is stock ESP32-S3); **zero on how well** |
-| Last verified | **2026-09-01** |
-
-## Related
-
-- [`lora.md`](lora.md) — the other radio, and why it is not in competition with this one
-- [`nfc.md`](nfc.md) · [`power-and-sleep.md`](power-and-sleep.md) · [`../resources-and-conflicts.md`](../resources-and-conflicts.md)
-- [`components/espressif/esp32-s3r8`](../../../../components/espressif/esp32-s3r8/README.md)
diff --git a/devices/m5stack/papermono/gaps-and-conflicts.md b/devices/m5stack/papermono/gaps-and-conflicts.md
deleted file mode 100644
index 9673955..0000000
--- a/devices/m5stack/papermono/gaps-and-conflicts.md
+++ /dev/null
@@ -1,710 +0,0 @@
-# PaperMono — gaps, conflicts and refuted hypotheses
-
-> Research snapshot **2026-09-01**. Nothing in this record was verified against
-> physical hardware; there is no PaperMono in hand. Every behavioural claim
-> elsewhere in this device record is `inferred`, `reported-working`, or read
-> from vendor source — never `executed-success` on a device.
-
-This file exists so that a later pass does not re-investigate settled questions
-and does not silently resolve unsettled ones. Conflicts are recorded, not
-arbitrated, except where primary evidence genuinely settles them — and those are
-marked **resolved** with the artifact that did it.
-
-## Resolved by primary evidence
-
-### R1 — `PYG3` is an M5PM1 net *and* an M5IOE1 pin — **resolved**
-
-An earlier pass in this session concluded the vendor's PaperMono page was
-defective for saying the frontlight is driven by `PYG3_BL_PWM` "of the M5PM1",
-reasoning from the Arduino libraries that `PYG` was an M5IOE1-only prefix, and
-that the PaperMono-Lite page (which says `G3_WAKEin` of M5PM1) was the correct
-one.
-
-**Refuted.** Schematic sheets 2 and 4 show the two chips use the `PYG` prefix at
-*opposite layers*: on the M5IOE1 it is the symbol pin name (nets are `PYB_*`);
-on the M5PM1 it is the net name (pin names are `G<n>_…`). Both vendor pages are
-accurate; they quote different layers. The defect is ambiguity, not error.
-Full write-up and the hazard it creates:
-[`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md).
-Refuting artifact `PaperMono_SCH_V0.6.2_20260522.pdf`; date 2026-09-01.
-
-### R2 — QIO versus DIO flash — **resolved**
-
-The vendor PlatformIO snippet specifies `qio_opi`; the shipped factory image
-reports **DIO** in its header. The schematic shows all four flash data lines
-routed (`NOR_DI`, `NOR_DO`, `NOR_WP`, `NOR_HOLD`) and the `Q` in
-`XM25UH128DHIQT` denotes a factory-set QE bit, so **the hardware supports QIO**.
-`sdkconfig.defaults` pins no flash mode, so the DIO header is an ESP-IDF default,
-not a hardware limitation. Not a defect; a build-configuration artefact.
-
-### R3 — BMI270 interrupt polarity — **resolved against the vendor prose**
-
-Vendor prose says the IMU interrupt is active-high. The vendor's own code
-(`BMI2_INT_ACTIVE_LOW` + `WAKE_FALLING`) and the shipped binary's log string
-(`PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge`) both say
-active-low / falling. The prose is the sole outlier and is wrong.
-
-### R4 — download-mode control — **resolved on the balance of evidence**
-
-The product page and specification table say the power button; the Arduino
-tutorial page refers to "the reset button on the side". The schematic shows
-three switches on the KEY/RGB sub-board — `S1` (`PWR_BTN`), `S2` (`G2_KEY1`),
-`S3` (`G3_KEY2`) — and **no separate reset button**. The power-button reading is
-correct; the Arduino page is wrong. Marked resolved but `not-tested`.
-
-### R5 — `M5Unified#develop` requirement — **resolved, the instruction is stale**
-
-`board_M5PaperMono = 29` is byte-identical on `master` and `develop`, and board
-support ships in released tags M5Unified 0.2.21 and M5GFX 0.2.28. The
-master↔develop deltas are unrelated fixes. The vendor's `#develop` pin is
-unnecessary as of the snapshot date.
-
-### R6 — the vendor product page's pin tables are accurate — **confirmed correct**
-
-Recorded because confirming existing documentation is a result. Every GPIO,
-every I²C address and every expander assignment on the product page matches the
-schematic. The page has exactly two **omissions** (not errors): M5IOE1 `PYG4`
-(NFC enable, which the firmware uses) and `PYG7` (`ADD_SET`). It additionally
-omits USB (GPIO19/20) and UART0 (GPIO43/44), which the schematic supplies.
-
-### R7 — RTC rail: the vendor block diagram is wrong — **resolved**
-
-Schematic sheet 1's power-state matrix places the RX8130CE RTC on `3V3_L1`.
-Sheet 4 shows its `VBAT`, `VIO`, `VDD` and `VOUT` pins all tied to one node on
-**`3V3_L0`**, the always-on rail, with the `nIRQ` pull-up also to `3V3_L0`. The
-IMU beside it genuinely is on `3V3_L1`. The circuit is right and the block
-diagram is wrong; the RTC therefore keeps time in L0 shipping mode. Recorded in
-[`power-architecture.md`](power-architecture.md). Additionally, `VBAT` tied to
-`VDD` means **there is no separate backup cell**, which makes M5Unified's
-`CHGEN=1` backup-charge enable a no-op. Sheet 4 also carries **drawn
-no-connect markers** on the RTC's `nRSTO` and `FOUT` — positive assertions, not
-omissions.
-
-### R8 — the NFC front end *is* published — **resolved**
-
-An earlier reading of this record assumed the NFC matching network was
-undocumented because NFC schematic sheet 1 of 2 is missing. **Refuted.** Sheet 1
-is genuinely absent, but the released sheet `2/2` carries the complete front
-end: `ST25R3916-AQWT`, a 27.12 MHz crystal, the L/C matching bank, series
-resistors, the load switch and an antenna construction note (4 turns,
-25 × 25 mm, 0.25 mm trace, 0.3 mm gap, 17 µm copper). What sheet 1 contains
-remains unknown. Date 2026-09-01.
-
-### R9 — `PYB_NFC_EN` is a power cut, not a reset — **resolved**
-
-`PYB_NFC_EN` on the main board and `PYB_RFID_RST` on the NFC sub-board are the
-same wire across the `BTB0.408-10PLBDR-G41` mating pair. It drives a load-switch
-enable, and the ST25R3916 **has no reset pin in any package** — so asserting it
-removes power rather than resetting the device. The `_RST` half of the name is
-misleading.
-
-### R10 — the firmware's "register `0x7F`" is not a register — **resolved**
-
-`0x7F` is the mode byte `0x40 | 0x3F`: an ST25R3916 read-register command
-targeting the IC identity register at `3Fh`. `0x05` is the returned `ic_type`.
-Confirmed independently from the ST datasheet's command table and from
-`M5Unit-NFC`'s own `OP_READ_REGISTER` / `REG_IC_IDENTITY` constants.
-
-
-### R11 — IP2315 charge-programming resistor — **resolved**
-
-`R17` = 15 kΩ sits on `ICHGSET`; `R18` on `LED3` is `NC`. This closes half of G9.
-It also **sharpens** conflict C18: 15 kΩ is not one of the values tabulated in
-the IP2315 datasheet, so the resulting charge current cannot be read off the
-table directly and the sheet-1 annotation `充电电流 0.5C` remains the only
-statement of intent.
-
-### R12 — the battery connector has no NTC pin — **resolved, and it corrects this record**
-
-`J2` is a **2-contact** `CON2_SMD` carrying only `VBAT_L0` and ground. The
-`100K-RNTC` thermistor is **`R15`, a mainboard part on the IP2315's `NTC` pin
-(26)**. Four places in this record previously said the battery was "NTC-sensed"
-at `J2`; that was **wrong** and has been corrected in `README.md`,
-`pinouts-and-buses.md` and `power-architecture.md`. Whether `R15` is thermally
-coupled to the cell by board layout is not established — so pack temperature
-protection is, on this evidence, weaker than the earlier wording implied.
-
-### R13 — both USB-C CC pulldowns are fitted — **resolved**
-
-There are **two** 5.1 kΩ Rd pulldowns, `R4` on `CC1` and `R14` on `CC2`, not one.
-The conclusion is unchanged (a plain 5 V sink, no PD, IP2315 CC pins
-depopulated) but the earlier record named only `R14`.
-
-### R14 — the USB-C receptacle's designator is `USB` — **resolved**
-
-Not `U1`. The bare string `USB` is the reference designator; `TYPEC-302-BRP16SC08`
-is the part number printed above the symbol. `pinouts-and-buses.md` previously
-listed it as `U1` on sheet 2, which collided with the real `U1` on that sheet.
-This also explains why the automated designator census missed it: the extraction
-filtered on `[A-Z]+[0-9]+`, which a purely alphabetic designator cannot match.
-
-### R15 — the "missing `N1`" is a parser artifact, not a design gap — **resolved**
-
-An earlier reading reported `N1` missing from the designator sequence. `N`-series
-designators **do not exist on this board**: `CON2_SMD` (J2's footprint label) and
-`PIN1`…`PIN24` (J5's pin labels) were being mis-parsed as components. The
-genuine designator gaps are **`R46`, `R48`, `R55`, `R56`, `R57`** only, absent
-from every word on every sheet, and most consistent with parts deleted during
-design (`R55`–`R57` being consecutive) rather than an unpublished sheet — a
-missing sheet would remove a contiguous block across several prefixes, which is
-not what is observed. Corrected component count: **290 placed components, 230
-distinct designators.**
-
-
-### R16 — an independent third party confirms this record's pin map — **corroboration, 2026-09-07**
-
-[`ciniml/paper_name_plate`](https://github.com/ciniml/paper_name_plate) (HEAD
-`7eac75dfc9`) is bare-metal Rust firmware for this board whose `DESIGN.md` was
-derived independently. It agrees with this record on **every previously contested
-point**:
-
-- **`PYGn` is 1-based** — *"docs' `PYGn` = 1-based"*, and it states the 0-based
-  index alongside each pin (*"IO5 (0-based index 4)"*). Confirms R1/R15.
-- **Frontlight is M5PM1 GPIO3 → PWM0** — confirms R1 and the vendor page, and
-  independently refutes the earlier claim that the page was defective.
-- **`IO4 = NFC_EN`, `IO10 = LoRa RST`, `IO2 = LoRa ANT SW`** — the three expander
-  pins this record identified as absent from the FreeInk SDK.
-- LoRa SPI pin set, IP2315 bus hazard, and the SSD1677 4-gray OTP path
-  (`0x1A=0x5A` + `0x22=0xD7`) all match.
-
-Two new facts from it: recovering the panel from deep sleep **requires a hardware
-reset via IOE1 IO5**, and the shared I²C bus runs **PM1/IOE1 at 100 kHz but
-touch and NFC at 400 kHz**.
-
-**It also demonstrates NFC working on this board** — a 28.9 KB ST25R3916 driver
-with Type 2 Tag emulation. NFC is no longer resting on the vendor demo alone.
-
-### C25 — SSD1677 booster parameter — **RESOLVED 2026-09-11: both are correct**
-
-**Not a defect in either implementation.** The SSD1677 datasheet (Rev 1.0,
-command table p. 24/47) defines command `0x0C` *Booster Soft-start Control* as
-taking **five** data bytes `A[7:0] B[7:0] C[7:0] D[7:0] E[7:0]`, and documents
-**exactly two** permitted settings:
-
-| Setting | A | B | C | D | **E** |
-|---|---|---|---|---|---|
-| **Level 1** | AE | C7 | C3 | C0 | **40** |
-| **Level 2** | AE | C7 | C3 | C0 | **80** |
-
-The command *"is used to control the inrush current for the booster… **Two level
-of strengths can be selected**"*. The disputed fifth byte is the strength
-selector, and both observed values are tabulated.
-
-**What each implementation sends** (both verified in source, `executed-success`):
-
-| Implementation | Value | Level | Evidence |
-|---|---|---|---|
-| `m5stack/M5PaperMono-OTP-Demo` @ `c7c0255` | **`0x80`** | **Level 2** | `components/EDP_OTP_LUT_demo/src/EDP_OTP_LUT_demo.cpp:221` **and** `:336` — twice, consistently |
-| `ciniml/paper_name_plate` @ `7eac75d` | **`0x40`** | **Level 1** | `src/ssd1677/mod.rs:187`, and `DESIGN.md` line 60 agrees |
-
-Both are internally consistent. This record's earlier `0x80` came from the vendor
-demo and was correct; `ciniml`'s `0x40` is equally valid and simply selects the
-weaker booster soft-start.
-
-**The sibling controllers decode this command in full; the SSD1677 does not.**
-SSD1680 (Rev 0.14, p.22), SSD1681 (Rev 0.13, p.22) and SSD1683 (Rev 1.0, pp.23-24)
-all document `0x0C` with a complete bit-field table — but in a **4-byte** form:
-
-| Field | Meaning |
-|---|---|
-| `A/B/C bit[6:4]` | **Driving strength**, `000` = 1 (weakest) … `111` = 8 (strongest) |
-| `A/B/C bit[3:0]` | **Min off-time of GDR**, `0100` = 2.6 … `1111` = 16.5 [time units] |
-| `D[5:4] / [3:2] / [1:0]` | **Duration** of phases 3 / 2 / 1: `00` = 10 ms … `11` = 40 ms |
-
-So the command is a **three-phase soft ramp of the external boost converter**:
-each phase sets how hard `GDR` drives the switching MOSFET and the minimum
-off-time (which caps duty cycle, hence peak inductor current), for a programmed
-number of milliseconds. Start weak, get stronger — so the 47 µH inductor doesn't
-slam inrush through the 2.2 Ω sense resistor into empty rail capacitors.
-
-**Applying that decode to the SSD1677's bytes gives a partial fit:**
-
-| Byte | Value | Strength | Min off-time | Fit |
-|---|---|---|---|---|
-| A | `0xAE` | 3 | 13.8 | consistent |
-| B | `0xC7` | 5 | 4.6 | consistent |
-| C | `0xC3` | 5 | *(`0011` = NA)* | ⚠ low nibble illegal in the 4-byte table |
-| D | `0xC0` | — | — | ✗ **incompatible** — the family's duration byte requires bits 7:6 = `00`; `0xC0` sets both |
-
-A, B and C have the *form* of per-phase soft-start bytes with a sensible
-weak→strong progression (3, 5, 5). D does not fit the family's duration encoding,
-and E has no counterpart at all. **The SSD1677 uses a different, undocumented
-5-byte encoding** — there is no bit table anywhere in its 47 pages.
-
-**The most likely reading of E is a one-hot strength selector** (`E[6]` = Level 1,
-`E[7]` = Level 2), and there is evidence for it in the wild: **Waveshare's own
-SSD1677 driver for the 3.7" panel ships `AE C7 C3 C0 C0`** — *both* bits set, a
-value that appears nowhere in the datasheet (`EPD_3in7.c:204-209`, verified
-directly). Under a two-value enum, `0xC0` is meaningless; under one-hot it is
-coherent. **This is inferred and unverified.**
-
-**What everyone else actually sends** — and `ciniml` is the lone outlier:
-
-| Project | Panel | E byte |
-|---|---|---|
-| Waveshare `EPD_10in2b.c` | 10.2" 960×640 | `0x80` |
-| Waveshare `EPD_3in7.c` | 3.7" 280×480 | **`0xC0`** (undocumented) |
-| GxEPD2 `GxEPD2_426_GDEQ0426T82` | 4.26" | `0x80` |
-| `osptek` vendor demo | 4.26" | `0x80` |
-| `bootdsc/fastwave` (measurement-driven) | 4.26" | `0x80` |
-| **`m5stack/M5PaperMono-OTP-Demo`** | PaperMono | **`0x80`** |
-| **`ciniml/paper_name_plate`** | PaperMono | **`0x40`** |
-
-`0x80` is the de-facto standard across Good Display's, Waveshare's and Seeed's own
-reference code, on three different panel sizes. There is **no size correlation** —
-the smallest panel gets the odd `0xC0`.
-
-### What the booster command physically drives — added 2026-09-11
-
-The SSD16xx application circuit explains why a *soft-start* command exists at all,
-and it is more elegant than "there is a boost converter". From a Chinese
-walkthrough of an SSD16xx-family panel
-([CSDN `sandwich_iot`, 2021-11-04](https://blog.csdn.net/sandwich_iot/article/details/121136582)),
-cross-checked against the SSD1677 datasheet's own application circuit:
-
-**One MOSFET, driven by `GDR`, generates both supply polarities.**
-
-| Phase | Positive rail (→ `VGH`) | Negative rail (→ `VGL`) |
-|---|---|---|
-| Q1 **on** | L1 current ramps linearly through sense resistor R2 to GND; C1 supplies the load | C2 discharges through D2; D2's cathode sits at **−(3.3 V + Vs)** |
-| Q1 **off** | L1's back-EMF `Vs` adds to 3.3 V; D3 conducts, feeding the load and recharging C1 | C2 charges through D1 to ≈ 3.3 V + Vs |
-
-So the positive rail is a **textbook boost** and the negative rail is a
-**charge-pump inversion of the same switch node**. `RESE` closes the current-sense
-loop.
-
-The pin descriptions make the dependency chain explicit:
-
-> `VGH` — *"positive gate drive voltage **and the supply pin for `VSH1`**"*
-> `VGL` — *"negative gate drive voltage, **and supply pin for `VCOM` and `VSL`**"*
-
-**That is the point.** You generate only two rails, and the source drivers and
-`VCOM` are *derived* from them. Every pixel voltage on the panel traces back to
-that single MOSFET. An inrush surge at start-up therefore disturbs **everything at
-once** — which is exactly what a three-phase soft-start with per-phase drive
-strength and minimum off-time exists to prevent.
-
-This is the mechanism behind the `0x0C` fields decoded above, and it makes the
-"strength" semantics concrete: the setting controls **how hard `GDR` switches Q1
-into the `RESE` current limit**, per phase.
-
-### Related voltage registers, for context
-
-The sibling SSD1683 documents the rails that the booster feeds
-([CSDN `weixin_43550576`, 2024-04-04](https://blog.csdn.net/weixin_43550576/article/details/137375815)
-— the free original; see the caution below):
-
-| Cmd | Register | Default |
-|---|---|---|
-| `0x03` | `VGH` gate drive | `00h`, range 10–20 V |
-| `0x04` | `VSH1` / `VSH2` / `VSL` source drive | `41h` (≈15 V) / `A8h` (≈5 V) / `32h` (≈−15 V) |
-| `0x2C` | `VCOM` | `00h` |
-
-In an **external waveform** (LUT) blob, these are not written separately — they
-are the **trailing bytes of the LUT array**: a 227-byte waveform payload followed
-by six parameter bytes (`0x3F`, VGH, VSH1, VSH2, VSL, VCOM). That is the SSD1683
-analogue of the familiar 153-byte SSD1681 LUT layout, and it means **changing a
-waveform silently changes the rail voltages** unless you preserve those six bytes.
-
-> ⚠ **Source caution.** Three CSDN articles titled *"SSD1683 driver voltage
-> parameter optimisation"* are AI-generated rewrites of the single free 2024
-> original cited above, two of them behind a VIP paywall. The rewrites add
-> plausible-sounding claims the original does not make — e.g. that `00h`
-> "corresponds to the middle value" — which could not be corroborated.
-> **Cite the original, not the rewrites.**
-
-### The negative finding stands
-
-**Across eight retrieved CSDN documents there is not one mention of `0x0C`,
-`booster`, or 软启动 (soft-start).** A search for `SSD1677` returns 69 hits, of
-which exactly one is a genuine SSD1677 article; the rest match on the digit
-string. The Chinese-language corpus does **not** discuss this command.
-
-**No measurement distinguishing Level 1 from Level 2 exists in public anywhere** —
-not in the datasheet, not in any driver, not in any writeup. A current probe on
-VCI during the boost ramp would produce the first.
-
-**Practical meaning** (inferred from the mechanism above, not measured). Level 2
-ramps harder — rails reach operating voltage sooner, at the cost of higher inrush;
-Level 1 is gentler, which matters for a weak or high-impedance supply. On a battery device
-sharing rails with radios, the gentler setting is a defensible choice — and
-`ciniml` also drives the panel through the M5IOE1-gated `EPD_3V3_L3B` rail, where
-inrush interacts with the load switch. **Neither is "the right answer"; they are a
-tuning decision.**
-
-**How to validate on hardware** (none of this was done — no device):
-
-1. **Scope the `EPD_3V3_L3B` rail** during panel power-up with each setting;
-   compare peak inrush and settle time.
-2. **Watch `BUSY`** — measure time from `0x20` Master Activation to BUSY release
-   for a full refresh under each. Level 2 should reach operating voltage sooner.
-3. **Vary temperature.** Booster behaviour is temperature-dependent, and the SSD1677
-   has an internal sensor (`0x18 0x80`); a setting that works at room temperature
-   may not at 0 °C.
-4. **Check for artefacts** — insufficient boost shows as weak blacks or incomplete
-   clearing, not as an error code.
-5. **Low battery is the real test.** Inrush margin is worst at minimum cell
-   voltage; test near the cut-off, not on a full charge.
-
-Recorded as a **specification-permitted variation**, not a conflict. The original
-entry is kept below for history.
-
-### C25-original — SSD1677 booster parameter disagreement
-
-`paper_name_plate`'s `DESIGN.md` gives the init as `0x0C AE C7 C3 C0 **40**`.
-This record's OTP-demo analysis has `0x0C = {0xAE, 0xC7, 0xC3, 0xC0, **0x80**}`.
-The fifth byte differs. One is wrong, or they derive from different sources.
-**Unresolved** — check against `M5PaperMono-OTP-Demo` directly before relying on
-either.
-
-## Unresolved conflicts
-
-### C1 — 4 grey levels versus 2
-
-M5Stack markets "4-level greyscale" and the vendor OTP demo implements a working
-four-grey mode with a distinct update-control value (`0xD7`) and a
-grey-mode temperature register write (`0x1A = 0x5A`). The DKE panel manual's own
-optical specification table reads `GN — 2Grey Level`, and its overview describes
-1-bit black and white. Three readings are possible — a stale manual template, a
-panel binned for mono with usable grey, or a marketing overstatement — and
-nothing in evidence chooses between them. **Unresolved.**
-
-### C2 — panel part number
-
-Manual cover and mechanical drawing say `DEPG0397BBS770F3`. The
-`M5PaperMono-OTP-Demo` README calls the fitted panel
-`DEPG0397BBS770F3HP-XM`. The suffix is undocumented. **Unresolved.**
-
-### C3 — SPI clock exceeds the panel's rated maximum
-
-M5GFX drives the panel at **40 MHz**. The SSD1677 datasheet (§12.1) and the DKE
-manual (p. 16) *independently* state a 20 MHz maximum write clock, and the
-vendor's own OTP demo uses 20 MHz. This may or may not be a factor in the
-refresh instability M5Stack itself warns about. **Unresolved, untested, and the
-most likely single cause worth investigating first.**
-
-### C4 — the M5IOE1's I²C address is not in its own manual
-
-Everything uses `0x4F`. The M5IOE1 V1.4 manual states the range `0x6F`–`0x76` in
-three places, the chip's `IO7` is genuinely wired to an `ADD_SET` divider, and
-the vendor library constant is named `..._ADDR_2` with an autodetect sweeping
-both ranges. **Unresolved.**
-
-### C5 — frontlight PWM frequency below the driver's rated range
-
-M5GFX programs the M5PM1 PWM at 5 kHz; the AW9967 datasheet specifies a
-10–100 kHz dimming input. Compounded by a squared gamma curve applied in
-software. **Unresolved; software-only fix if real.**
-
-### C6 — frontlight current annotation contradicts the fitted part
-
-The schematic note claims `Iset = 15 mA` with `Rset = 11 R`, but the fitted
-`R29` is 18 Ω, giving roughly 11 mA — and the note's own arithmetic is
-internally inconsistent. Annotation appears stale. **Unresolved.**
-
-### C7 — restock timing
-
-Vendor said "two or three months" (2026-08-22); CNX-Software reported "next
-year". Both recorded, neither preferred.
-
-### C8 — `PYB_NFC_EN` annotated "spare GPIO"
-
-Schematic sheet 4 annotates the net as a spare GPIO while the factory firmware
-uses it as the NFC enable. **Unresolved**; likely a stale annotation.
-
-### C9 — SSD1677 mirror integrity
-
-The M5Stack-hosted SSD1677 PDF has 46 pages but numbers itself `n/47`, and its
-PDF Producer is `PDFill` rather than a Solomon Systech export. It is also marked
-"Advance Information", Rev 1.0, Nov 2018. Treat as a re-processed copy of a
-preliminary document. **Unresolved provenance.**
-
-### C10 — DKE drawing note reversed
-
-DKE's mechanical drawing note 3 reads `800 gate × 480 source`, which is provably
-backwards: 800 gate lines would exceed the SSD1677's 680 gate outputs, and the
-firmware configures 480 gates via `0x01 = {0xDF,0x01,0x02}`. The drawing note is
-wrong; the arithmetic is in the component record.
-
-### C11 — mislabelled firmware link
-
-The vendor link "PaperMono Factory Reset Firmware" resolves to a record named
-"PaperMono UserDemo". Same image, different label.
-
-### C12 — M5PM1 manual internal inconsistencies
-
-PWM0/1 versus PWM1/2 naming; NeoPixel buffer documented at `0x60` in one place
-and `0x36` in another; an appendix citing pre-`SW:6` register addresses;
-`SW_REV` default disagreeing with the changelog. Documented in the component
-record. **Unresolved.**
-
-## Open questions and missing evidence
-
-### G1 — NFC schematic sheet 1 of 2 is not published
-
-The included NFC sheet is explicitly numbered `2/2`. Sheet 1 is absent from the
-released PDF. NFC front-end details not visible on sheet 6 are **undocumented,
-not absent**.
-
-### G2 — no certification identifiers exist on the vendor site
-
-`/en/certification` returns HTTP 200 and **zero** matches for `PaperMono` and
-`C153`. Verified negative.
-
-### G3 — the product I²C address table omits this board
-
-`/en/product_i2c_addr` returns 200 with zero matches, despite seven I²C devices.
-
-### G4 — UiFlow2 support is advertised but undocumented
-
-The UiFlow2 page states no required firmware version, no block list and no
-limitations. Confirmed by full-text search, not a retrieval failure.
-
-### G5 — no `Stamp-LoRa-1262` module datasheet exists anywhere located
-
-Consequently TCXO-versus-XTAL and the semantics of `SX_ANT_SW` are unknown.
-Module pins 11–13 carry pad markers but **no printed name, no net label, and no
-drawn no-connect glyph** — recorded as *unlabelled*, which is not the same as
-*proven no-connect*.
-
-### G6 — three parts have no obtainable datasheet
-
-`CN4040M000157A530001` (crystal), `LMD4737T261-AC02` (microphone) and
-`RS-C1415MBAR` (RGB LED). For the latter two the only web occurrences anywhere
-are M5Stack's own pages. Full search ledgers are in the component records.
-
-### G7 — no power or battery-life figure exists
-
-The power-state table says what is *powered*, never what it *costs*. No vendor
-figure, no independent measurement, none derived here.
-
-### G8 — DKE's OTP waveform contents are unpublished
-
-How many of the 34 WS/TR slots are programmed, and over what temperature span,
-is not documented — a silent no-refresh failure mode outside the programmed
-range.
-
-### G9 — unresolved schematic details (narrowed 2026-09-01)
-
-Still open: `J4` pin ordering; the PDM `SELECT` net; the JW5712 `VSEL` truth
-table; the `U4` (`3V3_L0`) enable net; PY32L020 QFN20 pin 1 orientation. Each is
-left unfilled rather than guessed.
-
-**Closed since first writing:** the IP2315 `ICHGSET` resistor is **`R17` = 15 kΩ**
-(with `R18` = `NC` on `LED3`) — see R11 below.
-
-### G10 — no independent technical coverage existed at the snapshot date
-
-One hands-on video with an affiliate link; every written article traces to one
-vendor blog post. Two broad passes agreed. This is a statement about 2026-09-01,
-not a permanent property.
-
-## Claims examined and rejected
-
-| Claim | Source | Why rejected |
-|---|---|---|
-| Restock delayed by an e-ink driver IC shortage | widely repeated | The cited post and its full reply chain were retrieved; the reason **does not appear in them**. Hearsay. |
-| "$55 with NFC and LoRa" | Liliputing | $55 is the Lite, which has neither. |
-| PaperMono is the successor to / an upgrade over PaperS3 | several launch articles | Contradicted by the vendor's own specs: ~35 % fewer pixels, 4 vs 16 grey levels, 1150 vs 1800 mAh, no expansion port. A repositioning, not an upgrade. |
-| "Bluetooth 5.0 LE + Mesh" | CNX-Software | Publication's inference from the SoC; not in M5Stack's specification table. |
-| "Half the price of the XTEINK X4 Pro" | launch coverage | No X4 Pro price was captured, and a sealed reader versus a development board is not a like-for-like comparison. |
-
-## Method limitations worth knowing
-
-The schematic netlist was recovered from Altium's invisible `CO`/`PI`/`NL`
-marker text in the published PDF, paired by spatial adjacency
-([`tools/altium_pdf_pin_table.py`](../../../tools/altium_pdf_pin_table.py)).
-This recovers **text adjacency, not electrical connectivity**: unlabelled
-wire-only connections are invisible to it, and dense areas of sheet 2 produced
-readings that had to be corrected by rendering the sheet and reading it. Every
-pin assertion in this record was cross-checked that way or against a second
-independent source (vendor firmware, vendor product page, or the DKE panel
-manual's own pinout). Where only the extraction supported a claim, it is marked
-`inferred`.
-
-### C13 — M5Unified `getVoltLow()` reads the wrong RTC flag
-
-`getVoltLow()` returns `0x1D & 0x80`, which is **`VBLF`** (backup battery low),
-not **`VLF`** (bit 1: oscillation stopped, register contents invalid). After a
-power-on reset `VLF=1` and `VBLF=0`, so the call returns `false` on precisely
-the occasion it is used to detect. Latent rather than active, and this record's
-own `features/rtc.md` previously recommended it for that purpose. Source: the
-RX8130CE application manual against the M5Unified source.
-
-### C14 — RX8130CE `BFVSEL` encoded two contradictory ways
-
-Tables 38 and 39 of the Epson application manual encode `BFVSEL` transposed
-relative to each other, in **both** revisions `ETM50E-09` and `-10`. Safety-adjacent
-where a rechargeable backup cell is fitted — though on this board none is.
-**Unresolved.**
-
-### C15 — SX1262 datasheet figure text is legible but wrong
-
-Figure fonts in the SX1261/2 datasheet carry a uniform **+31 code-point offset**:
-`LoRa(R)` extracts as `-P3B¥`. Body text and tables extract cleanly. This is
-exactly the glyph-offset failure the method warns about; nothing in this record
-was transcribed from a figure in that document.
-
-### C16 — Semtech mirror currency unresolved
-
-Semtech's product page lists a datasheet dated 2025-04-07; the copy held is
-Rev 2.2 (Dec 2024). The canonical download sits behind a Salesforce JS/POST
-shell and three retrieval strategies failed. Status **blocked**, not "not
-checked".
-
-### C17 — arduino-esp32 version differs between sources
-
-`M5PaperMono-UserDemo` pins arduino-esp32 **3.3.10**; `M5Stack-Arduino-Check`
-shows the `m5stack_papermono` variant in **3.3.9**. Both are true statements
-about different artifacts; recorded so it is not later "resolved" as an error.
-
-### C18 — IP2315 charge current cannot be read from the datasheet table
-
-`ICHGSET` = 15 kΩ (`R17`) is **not** a tabulated value in the IP2315 datasheet,
-so the programmed charge current is not directly derivable. Sheet 1's annotation
-`充电电流 0.5C` (~575 mA for the 1150 mAh cell) is the only statement of intent
-and is **unverified against the part**. Unresolved.
-
-### C19 — the NFC board-to-board halves disagree on pin numbering
-
-The `BTB0.408-10PLBDR-G41` mating pair is numbered such that a literal 1↔1
-mating would short 3V3 to GND. One half's numbering must be mirrored, but the
-schematic does not say which. **Unresolved, and worth care before probing.**
-
-### C20 — official firmware carries two disagreeing build identifiers
-
-M5Burner's `binFileName` embeds `…-yaozhenquan-8300e309-20260806_0x00.bin`
-while the `esp_app_desc_t` inside those same bytes says `c78f6c5-dirty`.
-**Neither is a commit in the published `M5PaperMono-UserDemo` history.**
-Unresolved.
-
-### C21 — vendor PlatformIO block disagrees with the shipped flash map
-
-The vendor snippet sets `board_build.partitions = default_16MB.csv`, the Arduino
-stock scheme. The shipped image and both vendor `partitions.csv` files use a
-three-entry layout with a single ~15 MiB `factory` app. Following the published
-snippet does not reproduce the shipped partition table.
-
-### C22 — the vendor publishes power figures for the neighbouring products, not this one
-
-M5Stack lists consumption for the **PaperS3** (9.28 µA / 949.58 µA / 154.02 mA at
-4.2 V, 0–40 °C) and the **PaperColor** (92.53 µA / 211.97 mA). The PaperMono
-specification table has **no power row and no operating-temperature row**
-(verified negative by full-text search). So G7's "no figure exists" is true but
-incomplete: the vendor supplies the figure for the products either side of this
-one, which makes the omission look deliberate rather than accidental.
-
-### C23 — source-ID numbering diverged between two files — **RESOLVED 2026-09-02**
-
-**Closed by giving the two files disjoint namespaces.** `acquisition/manifest.json`
-now uses an **`A##`** namespace and carries a `source_id` field pointing at the
-canonical `sources.md` **`S##`** row for each artifact (16 of 24 mapped; the other
-8 are reference-only entries with no `sources.md` row, left `null` rather than
-guessed).
-
-This was worse than a simple offset and worth recording: the two schemes
-**crossed over**. Manifest `S20` was the M5PM1 manual while `sources.md` `S20` is
-the SSD1677; manifest `S22`/`S24` were the reciprocal swap of `sources.md`
-`S24`/`S22`. Following an ID from one file into the other therefore landed on a
-*plausible but wrong* artifact — the most dangerous kind of error, because it
-does not look like one.
-
-Renumbering the manifest to match was rejected as the fix: three other documents
-cite manifest entries, and a blind renumber through a crossing-over mapping is
-exactly how a silent mis-citation gets introduced. Disjoint namespaces make the
-mistake structurally impossible instead.
-
-`acquisition/fetch.py --verify-only` re-run after the change: **0 failed**.
-
-The original defect, for the history:
-
-### C23-original — source-ID numbering diverged between two files in this record
-
-`acquisition/manifest.json` and `sources.md` use different `S##` numbering for
-the same artifacts (schematic `S10` vs `S14`; firmware `S30`/`S31` vs
-`S38`/`S39`; datasheets `S20`–`S29` vs `S18`–`S26`). Hashes, sizes and URLs agree
-in both, so no artifact is ambiguous, but an ID followed from one file into the
-other lands on the wrong row. **`sources.md` is canonical**; the manifest's IDs
-are superseded and should be renumbered in a future pass.
-
-### C24 — Waveshare alternative was unbacked — **RESOLVED 2026-09-01**
-
-**Closed** by writing
-[`devices/waveshare/esp32-s3-epaper-3.97`](../../waveshare/esp32-s3-epaper-3.97/README.md),
-a real Waveshare **e-paper** ESP32-S3 board: same SoC, same 8 MB PSRAM / 16 MB
-flash, same 3.97" 4-greyscale panel, and an active area matching the PaperMono's
-DKE panel to 0.01 mm. The recommendation is now backed by an internal record.
-
-Two things surfaced while closing it, both recorded in that record: the two
-boards may well carry **the same panel** (`inferred`, not established), and
-Waveshare's **MediaWiki API currently returns a PHP parse error with HTTP 200**,
-which breaks the enumeration route this knowledge base's own Waveshare vendor
-guide recommends.
-
-#### Addendum, second pass 2026-09-01 — the recommendation is backed, but half of it is refuted
-
-The Waveshare record was revisited the same day once its **schematic**, **panel
-manual** and **official example repository** were located on
-`docs.waveshare.com` — a host the first pass had not checked. Three findings change
-what C24 should be read as saying:
-
-1. **C24 is genuinely closed.** The recommendation now rests on a real internal
-   record backed by primary design data, not on a store listing. Price **USD
-   34.99–47.99** (2026-09-01), panel controller **SSD1677** — *the same controller as
-   the PaperMono's own panel*, which strengthens the same-panel inference to a
-   four-way match (active area, resolution, DPI, controller).
-
-2. **But the *reason* the README gave for the recommendation is wrong for that
-   board.** `README.md` recommends a Waveshare board for e-paper development **"with
-   expansion"**. The Waveshare board that actually competes with a PaperMono has
-   **no expansion header at all** — its complete connector census is one USB-C, three
-   PH1.25-2P power/speaker JSTs, the panel FPC and a microSD socket, with every
-   usable GPIO committed. On expansion it is **no better than the PaperMono**.
-   See [C-WS1](../../waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards).
-
-3. **Waveshare's expansion answer exists, at a different size.** The
-   [ESP32-S3-ePaper-1.54](../../waveshare/esp32-s3-epaper-1.54/README.md) and
-   [ESP32-C6-ePaper-1.54](../../waveshare/esp32-c6-epaper-1.54/README.md) both carry a
-   **2 × 6, 2.54 mm header** — at **200 × 200**, i.e. 40 000 pixels against the
-   PaperMono's 384 000. The honest recommendation is therefore *"a Waveshare **1.54-inch**
-   e-paper board, if you will trade 90 % of the display for a header"*, which is a
-   materially different piece of advice from the one the README currently gives.
-
-**Status: resolved for the record-exists question, and the residual advice defect is
-tracked as [C25](#c25--the-expansion-recommendation-is-still-imprecise) rather than
-folded silently back into C24.**
-
-A fourth finding, unrelated to the recommendation but recorded here because it came
-out of the same pass: Waveshare's marketing names the board's PMIC **"TG28"**, while
-the schematic and Waveshare's own firmware both say **X-Powers AXP2101**
-([C-WS2](../../waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws2--tg28-versus-axp2101)).
-
-### C25 — the expansion recommendation is still imprecise
-
-`README.md`'s *when not to use* says: *"For a general e-paper development board with
-expansion, prefer Inkplate or a Waveshare ESP32 e-paper board."*
-
-C24 established that a Waveshare ESP32 e-paper board now **exists** in this knowledge
-base. C25 records what remains wrong with the sentence:
-
-- **"a Waveshare ESP32 e-paper board" is too vague to act on.** Of the seven in the
-  catalogue, only the two 1.54-inch models have expansion headers, and they are
-  200 × 200 devices. Pointed at the like-for-like board, a reader gets **no
-  expansion** — the exact thing the sentence promised.
-- **The Inkplate half remains sound.** Inkplate 5 / Gen 2 have easyC/Qwiic *and*
-  broken-out GPIO *and* published KiCad sources, so for W4 they are still the better
-  recommendation, and by a wider margin than before.
-
-**Not resolved by rewriting the README sentence in this pass** — that is a
-recommendation change, and the evidence for it is now written down in
-[comparisons §5](comparisons-and-recommendations.md) where a reader will meet it.
-Recorded so the imprecision is not lost.
-
-The original defect, for the history:
-
-### C24-original — this record recommended a Waveshare alternative it could not support
-
-`README.md`'s *when not to use* suggests "prefer Inkplate or a Waveshare ESP32
-e-paper board". The Inkplate half is backed by internal records; **the Waveshare
-half is not** — all four Waveshare records in this knowledge base are LCD boards,
-not e-paper. Recorded as an unbacked inference rather than silently deleted.
diff --git a/devices/m5stack/papermono/market-and-pricing.md b/devices/m5stack/papermono/market-and-pricing.md
deleted file mode 100644
index c3add0e..0000000
--- a/devices/m5stack/papermono/market-and-pricing.md
+++ /dev/null
@@ -1,332 +0,0 @@
-# Market and pricing — M5Stack PaperMono
-
-> **Every observation on this page is dated 2026-09-01 (UTC)** unless a row says otherwise.
-> Eleven days after launch, at which point **both SKUs were out of stock at the official store
-> and had been for all but nine minutes of the product's commercial life.**
->
-> ## Three rules this page follows, stated up front
->
-> 1. **Launch pricing and current pricing are kept separate.** For this product they happen to
->    coincide — see [§1](#1-launch-pricing-versus-current-pricing) — and that is itself recorded
->    rather than glossed over.
-> 2. **No currency conversion is performed anywhere.** Three sellers, three currencies, three VAT
->    regimes, three shipping arrangements. A converted "equivalent" would be a fabricated number
->    ([§3](#3-why-there-is-no-converted-comparison)).
-> 3. **PaperMono and PaperMono-Lite are never merged**, and bare units are never merged with
->    bundles. They are distinct SKUs at distinct prices.
-
-## Contents
-
-- [1. Launch pricing versus current pricing](#1-launch-pricing-versus-current-pricing)
-- [2. Current observations — PaperMono (C153)](#2-current-observations--papermono-c153)
-- [3. Why there is no converted comparison](#3-why-there-is-no-converted-comparison)
-- [4. Current observations — PaperMono-Lite (C153-LITE)](#4-current-observations--papermono-lite-c153-lite)
-- [5. Method — where these numbers came from](#5-method--where-these-numbers-came-from)
-- [6. Stock evidence, and what the −129 means](#6-stock-evidence-and-what-the-129-means)
-- [7. Availability history](#7-availability-history)
-- [8. Restock: the vendor and the press disagree](#8-restock-the-vendor-and-the-press-disagree)
-- [9. Confirmed not sold](#9-confirmed-not-sold)
-- [10. No determination possible](#10-no-determination-possible)
-- [11. Used, clone and marketplace supply](#11-used-clone-and-marketplace-supply)
-- [12. What this pricing picture is worth](#12-what-this-pricing-picture-is-worth)
-- [13. Gaps](#13-gaps)
-
----
-
-## 1. Launch pricing versus current pricing
-
-The method requires these to be recorded separately. For an eleven-day-old product they are the
-same numbers, and the honest statement is *why*:
-
-| | Launch (2026-08-21) | Current (2026-09-01) |
-|---|---|---|
-| PaperMono `C153`, M5Stack store | **USD 65.00** | **USD 65.00** |
-| PaperMono-Lite `C153-LITE`, M5Stack store | **USD 55.00** | **USD 55.00** |
-| Evidence | Shopify `published_at` 2026-08-21T12:00:10+08:00 with the price field as read on 2026-09-01 | Shopify `price` field, read 2026-09-01 |
-| Confidence | **Inferred, not observed.** Shopify exposes no price history | **Observed** |
-
-**The launch row is an inference and must be read as one.** Shopify's product JSON gives the
-current price and the publication timestamp, not a price history. The product has been out of
-stock since minutes after launch, so there has been no commercial reason to reprice it, and no
-source anywhere reports a price change. That is a reasonable basis for saying the launch price
-equals the current price — and it is still an inference. **Nobody observed the price on
-2026-08-21.**
-
-These are **MSRP / list prices at the manufacturer's own store**. There is no crowdfunding
-price, no introductory price, no observed street price, and no discount in evidence: the product
-has never been in a state where a street price could form.
-
-## 2. Current observations — PaperMono (C153)
-
-| Field | Observation 1 | Observation 2 | Observation 3 | Observation 4 |
-|---|---|---|---|---|
-| **Date** | 2026-09-01 | 2026-09-01 | 2026-09-01 | 2026-09-01 |
-| **Seller** | **M5Stack official store** | **The Pi Hut** | **OpenELAB (.io)** | **OpenELAB (.de)** |
-| **Region** | Global — a single Shopify market (`market_setup_type: single_market`) | UK | International / EU | Germany |
-| **Condition** | new | new | new | new |
-| **Configuration** | **Bare unit.** The vendor "Includes" list is literally `1 x PaperMono` — no bundle, no accessories | Bare unit, SKU `C153` | Bare unit, SKU `M5-C153`, barcode `17841945721489` | Same SKU |
-| **Genuine / clone** | **genuine — manufacturer direct** | genuine — listed M5Stack reseller | genuine — listed reseller | genuine — listed reseller |
-| **Item price** | **65.00** | **62.40** | **79.95** | **79.95** |
-| **Currency** | **USD** (confirmed: `Shopify.currency.active = "USD"`) | **GBP** | **EUR** (`Shopify.currency.active = "EUR"`) | **EUR** |
-| **Tax treatment** | **not stated pre-checkout** | page markup says **`incl. VAT`** for domestic, with an `excl. VAT` toggle for international | not stated | not stated |
-| **Shipping** | not shown pre-checkout | not shown | not shown | not shown |
-| **Stock evidence** | **Out of stock.** `product.available = false`; variant `50199717249281`, `inventory_policy = "deny"`, **`inventory_quantity = -129`** | **Out of stock.** JSON-LD `availability: http://schema.org/OutOfStock`; page carries "Sold out" / "Pre-order" / "Coming soon" | **`available = true`, but the title itself is suffixed "(Pre-sale)"** — a pre-order, not stock on hand | Same, suffixed **"(Vorverkauf)"** |
-| **Listing created** | `2026-08-18T14:29:31+08:00` | `2026-08-21T11:15:48+01:00` | `2026-08-21T06:12:30+02:00` | `2026-08-21T06:13:28+02:00` |
-| **Source** | S48 | S53 | S54 | S55 |
-
-### What these four rows actually mean
-
-**None of them is a purchasable unit on 2026-09-01.** Two say "out of stock" outright, and two
-say "available" while their own titles say "pre-sale". The OpenELAB rows are the trap: a naive
-scrape reads `available: true` and reports EUR 79.95 as a live price. It is a **pre-order at an
-announced price**, which is a different commercial object from stock on a shelf, and it is
-recorded as such.
-
-**The Pi Hut's number is the only one whose tax treatment is stated**, and it is stated as
-*inclusive*. So GBP 62.40 and USD 65.00 are not the same kind of number even before exchange
-rates enter the picture: one contains UK VAT and one does not contain any sales tax at all.
-
-**The EUR 79.95 rows carry a reseller markup of unknown composition.** Whether the gap over the
-manufacturer price is VAT, import duty, margin, or all three is not established — none of the
-three sellers exposes a tax breakdown pre-checkout.
-
-## 3. Why there is no converted comparison
-
-The method explicitly warns against merging observations "into one range without explicit
-normalization". Here, normalisation is not available:
-
-| Obstacle | Detail |
-|---|---|
-| **Three currencies** | USD, GBP, EUR — each confirmed from the storefront's own currency token, not assumed |
-| **Three tax regimes** | M5Stack: not stated. The Pi Hut: **incl. VAT** (UK), with an explicit ex-VAT toggle for international buyers. OpenELAB: not stated |
-| **Three shipping arrangements** | None of the three shows shipping before checkout. A US-direct order, a UK domestic order and an EU pre-order have materially different landed costs |
-| **Two commercial states** | Two out-of-stock listings and two pre-orders |
-| **No conversion date would be honest** | A rate on 2026-09-01 applied to a price that includes VAT in one row and excludes it in another produces a number that is wrong in a way the reader cannot see |
-
-**So: read each row on its own terms.** The one comparison that *is* safe is the internal one —
-`C153` at USD 65.00 against `C153-LITE` at USD 55.00, same seller, same currency, same day,
-same tax treatment. **That USD 10 buys exactly the NFC and LoRa hardware** and nothing else;
-everything else about the two boards is identical
-([`product-history-and-family.md` §6](product-history-and-family.md#6-papermono-and-papermono-lite)).
-
-## 4. Current observations — PaperMono-Lite (C153-LITE)
-
-| Field | Value |
-|---|---|
-| **Date** | 2026-09-01 |
-| **Seller** | M5Stack official store |
-| **Region** | Global (single Shopify market) |
-| **Condition / configuration** | New; bare unit. "Includes": `1 x PaperMono-Lite` |
-| **Genuine / clone** | genuine — manufacturer direct |
-| **Item price** | **55.00 USD** |
-| **Tax / shipping** | not stated pre-checkout |
-| **Stock evidence** | **Out of stock.** `product.available = false`; variant `50199714988289`, `inventory_policy = "deny"`, **`inventory_quantity = 0`** |
-| **Listing created / published** | `2026-08-18T14:26:42+08:00` / `2026-08-21T12:00:09+08:00` |
-| **Source** | S49 |
-
-**No Lite listing was found at any reseller anywhere.** The Pi Hut, OpenELAB (.io and .de),
-Switch Science, Adafruit, Reichelt, Botland and Core Electronics all returned zero results for
-it, on the same day those same sellers were checked for the full model. Whether that is a
-distribution decision or simply lag is **not established** — it is eleven days old and the full
-model reached three resellers, so lag is plausible but unevidenced.
-
-**Note the two SKUs are in different inventory states**: `-129` for the C153, exactly `0` for
-the Lite. That difference is the single most interesting number on this page (§6).
-
-## 5. Method — where these numbers came from
-
-Every M5Stack-family price was taken from **Shopify storefront JSON** rather than rendered page
-text:
-
-| Endpoint | Gives |
-|---|---|
-| `/products/<handle>.json` | `price`, `sku`, `created_at`, `published_at`, variant IDs |
-| `/search/suggest.json` | `product.available` (a boolean) |
-| Product page HTML | the *Stoq / RestockRocket* app embeds `window._RestockRocketConfig.variantsInventoryQuantity` and `variantsInventoryPolicy` — **exact per-variant on-hand counts, including negatives** |
-
-This matters for reproducibility: a screenshot of a price is a claim, a `price` field with a
-`published_at` beside it is a record. `shop.m5stack.com` served all of this to a plain
-`curl/8.5.0` with no user-agent rotation needed.
-
-The RestockRocket detail is a general technique, not an M5Stack quirk — any Shopify store
-running that app leaks per-variant on-hand counts in its product HTML. It is what produced the
-`-129`, and it is worth looking for before concluding that a store exposes only a boolean.
-Recorded for reuse in [`research-log.md`](research-log.md) and the vendor guide
-[`vendors/m5stack`](../../../vendors/m5stack/README.md).
-
-## 6. Stock evidence, and what the −129 means
-
-Shopify reports a **negative** on-hand quantity when fulfilled or accepted orders exceed counted
-stock.
-
-**The literal, defensible statement is:** *the storefront's inventory counter for variant
-`50199717249281` stood at **−129** on 2026-09-01.* Evidence type: **firsthand measurement of
-vendor storefront data.**
-
-**The interpretation is weaker than the measurement**, and the two must not be conflated:
-
-- It is **consistent with** 129 units of oversell or backorder, which would match the vendor's
-  own statement that pre-orders "reached the limit" (S71) and the community's independent
-  reports of a capped pre-order batch.
-- It is **also consistent with** a stock-count correction, a fulfilment adjustment, or a
-  migration artefact. Shopify negatives arise from several mechanisms.
-- Therefore: **corroborating evidence, not proof of a 129-unit backlog.** Evidence type for the
-  interpretation: **inferred.**
-
-The contrast with the Lite's exact `0` is what makes the number interesting at all. Two SKUs
-launched in the same second, from the same store, in different inventory states eleven days
-later. That is a real, measured asymmetry between the two products' demand or allocation — and
-this record does **not** know which.
-
-`inventory_policy = "deny"` on both means the store refuses to sell past zero, which is why
-neither is purchasable regardless of the counter's sign.
-
-## 7. Availability history
-
-| Date | State | Evidence |
-|---|---|---|
-| 2026-08-18 06:29 UTC | Both storefront records created, unpublished | Shopify `created_at` (S48, S49) |
-| **2026-08-21 04:00 UTC** | **Both SKUs published.** Lite at 12:00:09 +08:00, full model at 12:00:10 +08:00 | Shopify `published_at` |
-| **2026-08-21 04:09 UTC** | **First independent sell-out report — nine minutes later**, with photographs | @henry19840301 (S72) |
-| 2026-08-21 08:44 UTC | Vendor posts to r/M5Stack; later states pre-orders **"reached the limit"** | Reddit (S71) |
-| 2026-08-21 ~12:00 UTC | HN submitter reports it was already out of stock ~8 h post-announcement | HN (S69) |
-| 2026-08-21 | Multiple independent failed-purchase reports: `shackburger` ("woke up … saw the launch email and it was already sold out"), `9mini-paralyses` ("probably the quickest sellout on their site that I've seen") | r/M5Stack (S71) |
-| 2026-08-22 10:09 UTC | @berryxia reports stock gone, asks for restock | X (S73) |
-| **2026-09-01** | **Still out of stock. Eleven days.** | Shopify (S48, S49) |
-
-> **On "sold out in one second".** That phrasing originated with the buyer who posted at 04:09
-> UTC and was repeated on Hacker News, where another user pushed back on it at the time. **The
-> checkable fact is a nine-minute gap** between storefront publication and a sell-out report,
-> which is an upper bound on how long stock lasted, not a measurement of it. Record the nine
-> minutes. Evidence type: **firsthand ownership report** for the purchase, **opinion/colloquial**
-> for the "one second".
-
-## 8. Restock: the vendor and the press disagree
-
-| Date | Source | Statement | Evidence type |
-|---|---|---|---|
-| 2026-08-21 | **CNX-Software** | "The company says the quantity is limited, and **the next batch will be available next year**." | **Reproduced vendor statement, second-hand** — CNX neither quotes nor links a vendor source |
-| **2026-08-22 10:54 UTC** | **@M5Stack on X**, replying to @berryxia | 「要等两三个月了」 — ***"you'll have to wait two or three months"*** | **Direct vendor statement, primary** (S74) |
-| 2026-08-21 | u/No-Connection1900 (M5Stack's Reddit account) | pre-orders "reached the limit" | Direct vendor statement, primary (S71) |
-| 2026-08-27 | HN user `notatoad` | "i can't remember where i read it, but a few days ago i saw they didn't expect a restock until next year" | **Hearsay, self-flagged as unsourced** |
-
-**Both recorded; neither preferred.** "Two or three months" from 2026-08-22 lands in
-October–November 2026; "next year" is at least January 2027. They are not reconcilable and no
-evidence chooses between them. Tracked as
-[C7](gaps-and-conflicts.md#c7--restock-timing).
-
-> ### The e-ink driver IC shortage claim is hearsay — checked and rejected
->
-> HN user `big_toast` wrote on 2026-08-27 that "M5Stack's twitter says 2 to 3 months to restock
-> **because they're out of eink driver ic**", citing
-> `x.com/M5Stack/status/2091116748686922069`.
->
-> **That tweet was retrieved in full, along with its parent and the thread root.** It says only
-> 「要等两三个月了」. The parent (@berryxia, 10:09 UTC) merely asks for a restock. The thread root
-> (@M5Stack, 07:49 UTC) is a "PaperMono vs PaperMono-Lite" marketing post. **The driver-IC
-> reason does not appear anywhere in the cited chain.**
->
-> This is the one place in this record where a widely repeated commercial explanation was
-> checked against its own citation and failed. Do not propagate it without a new source.
-
-## 9. Confirmed not sold
-
-All checked 2026-09-01. **These negatives are as valuable as the positives**, and they are
-negatives — each search returned HTTP 200 with a working result page.
-
-| Seller | Query | Result |
-|---|---|---|
-| **Amazon.com** | `m5stack papermono` | Page reports "5 results": an A5 loose-leaf paper refill and four unrelated M5Stack items. **No PaperMono listing** (S57) |
-| **AliExpress** | `wholesale-papermono` | One product returned — M5Stack **PaperColor** at US $127.91 / $182.87 from third-party sellers. **No PaperMono or Lite** (S58). Independently corroborates CNX-Software's 2026-08-21 note that it is "not listed on AliExpress (anymore)" |
-| **Switch Science** (JP, official M5 distributor) | `PaperMono` | 「PaperMono」の検索結果**0件** (S59) |
-| **Adafruit** | `papermono` | "No products found for 'papermono'" (S60) |
-| **Reichelt** | `papermono` | "Die Suche nach papermono hatte **0 Treffer**" (S61) |
-| **Botland** | `papermono` | 0 products (S62) |
-| **Core Electronics** (AU) | `papermono` | 0 products (S63) |
-| Secondary sweep — MakerLab Electronics, Elektor, BerryBase, Robu.in, Cytron, MC Hobby | various | no listings (S67) |
-
-**The AliExpress row deserves a second look.** It returned PaperColor at **$127.91 and $182.87**
-— against M5Stack's own $75.00 for that product. That is what third-party marketplace pricing of
-this vendor's e-paper boards looks like: roughly **1.7× to 2.4× the manufacturer price**. It is
-one product and two listings on one day, so it is an **illustration, not a rate**, but it is the
-only marketplace datapoint anywhere in this pass and it is worth knowing before assuming a
-marketplace restock would be cheap.
-
-## 10. No determination possible
-
-Recorded separately from §9 so a later pass does not mistake a bot-wall for an absence.
-
-| Seller | Result | Why it matters |
-|---|---|---|
-| **Mouser** | 13.9 KB bot-denial page (S64) | **On M5Stack's own distributor list** (`m5stack.com/distributor`, S56) |
-| **DigiKey** | HTTP 403 (S65) | Also on the distributor list |
-| **TinyTronics** | HTTP 403 (S66) | — |
-
-**Absence at Mouser and DigiKey is genuinely unknown, not negative.** One adjacent datapoint:
-a YouTube creator reported on 2026-07-14 that **DigiKey still stocked the EOL M5Paper v1.1** —
-evidence that DigiKey carries this product family, not that it carries PaperMono.
-
-Next steps for a later pass are known: Mouser publishes a **Search API** and DigiKey has an
-OAuth API. Neither was used here.
-
-## 11. Used, clone and marketplace supply
-
-**There is none, and the reason is structural.**
-
-| Market | Finding |
-|---|---|
-| Used / refurbished | **No observation anywhere.** No eBay, marketplace or forum sale was located |
-| Clones / compatibles | **None found.** No clone listing on AliExpress or Amazon |
-| Liquidation | not applicable — the product is eleven days old |
-
-A device that has been purchasable for approximately nine minutes cannot have a secondary
-market. **This is a statement about 2026-09-01, not a property of the product**, and it is the
-row most likely to change first after a restock.
-
-The absence of clones is likewise uninformative at eleven days. What *would* be informative
-later: this board's two custom chips (M5PM1, M5IOE1) are M5Stack-proprietary parts, which is a
-practical barrier to a drop-in clone in a way that a WROVER-and-expander design is not.
-`inferred`.
-
-## 12. What this pricing picture is worth
-
-Four conclusions a buyer can actually use, each with its limits stated:
-
-1. **The list price is USD 65.00 (C153) / USD 55.00 (C153-LITE), direct from the manufacturer.**
-   Firm, measured, single-source-but-authoritative.
-2. **You cannot buy one.** Firm on 2026-09-01, at every seller checked, including two that say
-   "available" and mean "pre-order".
-3. **A reseller pre-order at EUR 79.95 is the only route with a stated availability path** — and
-   it is a pre-order against an unrestocked product with contested restock guidance, so the
-   delivery date is effectively unknown.
-4. **Price comparison against alternatives is not meaningful from this data alone.** Not because
-   the alternatives are unknown — see
-   [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) — but because a
-   price you cannot transact at is not a price. The nearest in-family alternative, the PaperS3 at
-   USD 59.00, is **EOL** and equally unpurchasable.
-
-The one genuinely durable commercial fact here is the **USD 10 delta between the two SKUs**,
-because it is a same-seller, same-day, same-currency, same-tax comparison of two products that
-differ in exactly two components. Everything else on this page has a caveat attached to it.
-
-## 13. Gaps
-
-| Gap | Why it matters | Next step |
-|---|---|---|
-| **Mouser / DigiKey / TinyTronics unknown** | All are or are adjacent to listed M5Stack distributors; bot-walled, so absence is unproven | Mouser Search API; DigiKey OAuth API |
-| **No Lite listing at any reseller** | Distribution decision or lag is unresolved | Re-check after restock |
-| **No price history for any row** | Shopify exposes none; the launch-price row in §1 is therefore an inference | Wayback captures of the product pages, if any exist |
-| **Tax and shipping unresolved at three of four sellers** | Landed cost is the number a buyer actually pays, and it is unknown for USD and EUR rows | Requires a checkout simulation, which was not attempted |
-| **XTEINK X4 Pro not priced** | It is the comparison the community actually makes ([`community.md`](community.md)) | `xteink.com` product page, linked from a 2026-01-24 YouTube description |
-| **Waveshare e-paper line not priced** | Named as a competitor; this knowledge base's Waveshare records cover **LCD** boards only | See [`comparisons-and-recommendations.md` §5](comparisons-and-recommendations.md#5-waveshare--an-explicit-gap-not-a-verdict) |
-| **No used or clone market observation** | Nothing to observe yet (§11) | Re-run after restock |
-
-## Related
-
-- [`product-history-and-family.md`](product-history-and-family.md) — the dated launch chronology these prices sit in
-- [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) — what else the money buys, by tier
-- [`community.md`](community.md) — the sell-out reports and the rejected shortage claim, as evidence
-- [`../papermono-lite/README.md`](../papermono-lite/README.md) — the USD 55 variant
-- [`gaps-and-conflicts.md` C7](gaps-and-conflicts.md#c7--restock-timing) — the restock conflict
-- [`research-log.md`](research-log.md) — every query, filter and disposition, including the bot-walls
-- [`sources.md`](sources.md) — S48–S67 (retail), S71–S79 (statements and coverage)
diff --git a/devices/m5stack/papermono/media.md b/devices/m5stack/papermono/media.md
deleted file mode 100644
index c47db68..0000000
--- a/devices/m5stack/papermono/media.md
+++ /dev/null
@@ -1,213 +0,0 @@
-# Media and visual identification — M5Stack PaperMono
-
-> Snapshot **2026-09-01**. Machine-readable index: [`media/manifest.json`](media/manifest.json).
->
-> ## ⚠ **Zero images are retained. That is the finding, and it is deliberate.**
->
-> **No product photograph, no teardown, no PCB view and no revision-marking image is held in this
-> record**, for two reasons that are different in kind and must not be conflated:
->
-> 1. **The only imagery that exists is vendor product photography**, and it is **not licensed for
->    redistribution** — M5Stack states no licence for it anywhere.
-> 2. **No independent teardown, PCB photograph or component close-up existed at the snapshot
->    date.** Nobody has opened one in public. That is a **verified absence** (§3), not a failed
->    search.
->
-> The visual evidence this record *does* hold is the **vendor schematic** and the **mechanical
-> drawing** (§4). Both are primary design documents, both are retained, and between them they
-> establish the board's construction and its outline — but neither tells you what the product
-> looks like or how to identify one in hand.
-
-## Contents
-
-- [1. What was sought](#1-what-was-sought)
-- [2. Where it was looked for](#2-where-it-was-looked-for)
-- [3. Why nothing is retained](#3-why-nothing-is-retained)
-- [4. The visual evidence that is held](#4-the-visual-evidence-that-is-held)
-- [5. Derived renders that exist but are not media](#5-derived-renders-that-exist-but-are-not-media)
-- [6. What a future pass should capture](#6-what-a-future-pass-should-capture)
-- [7. Rules for whoever fills this in](#7-rules-for-whoever-fills-this-in)
-- [8. What can be said about the product's appearance without a photograph](#8-what-can-be-said-about-the-products-appearance-without-a-photograph)
-
----
-
-## 1. What was sought
-
-The method's visual-identification list, and the status of each class for this device:
-
-| # | Image class | Status | Why it matters here |
-|---|---|---|---|
-| 1 | **Front** — the product as sold | **exists, vendor-only, not retained** | Basic identification |
-| 2 | **Back** | **not located** | Where a revision marking or regulatory label would be — and **no certification identifier is published for this board at all** (S11), so a photograph of the back is currently the *only* possible route to one |
-| 3 | **Ports and labels** | **not located** | USB-C position, the side RGB indicator, the three switches |
-| 4 | **Enclosure open** | **not located** | The board is described as three PCBs plus three flexible assemblies; nothing shows how they sit |
-| 5 | **Teardown stages** | **none exists** | Verified absence at the snapshot date |
-| 6 | **PCB front** | **none exists** | Would confirm fitted parts against the schematic, including the `Stamp-LoRa-1262-mini` module |
-| 7 | **PCB back** | **none exists** | — |
-| 8 | **Revision markings** | **none exists** | **Only one hardware revision (V0.6.2) is in evidence, and it comes from a schematic filename.** There is no way to tell one board from another in hand |
-| 9 | **Component close-ups** | **none exists** | **Three parts have no obtainable datasheet** — the `CN4040M000157A530001` crystal, the `LMD4737T261-AC02` microphone and the `RS-C1415MBAR` RGB LED ([G6](gaps-and-conflicts.md#g6--three-parts-have-no-obtainable-datasheet)). A sharp photograph of a top marking is the most likely route to identifying any of them |
-| 10 | **Representative use** | **exists, vendor and one video, not retained** | — |
-
-**Rows 5–9 are the ones that would change what this record knows.** Rows 1, 3 and 10 are
-marketing; rows 6–9 are evidence.
-
-## 2. Where it was looked for
-
-Imagery was not searched for as a separate exercise; it was **sought as part of the two broad
-coverage passes** logged in [`research-log.md`](research-log.md) and catalogued in
-[`community.md`](community.md). What that covered, and what it returned:
-
-| Venue | Imagery outcome |
-|---|---|
-| **`docs.m5stack.com`** (13 pages, EN/zh_CN/ja) | Vendor product photography and PinMap diagrams present. **Not retained** — no licence stated (§3) |
-| **`shop.m5stack.com`** product pages and blog | Vendor product photography. Same |
-| **M5Burner API** | Both firmware records carry a `coverUrl` on `m5burner-cdn.m5stack.com`. **Not retrieved** — they are vendor/community catalogue artwork, and their licence is likewise unstated |
-| **Hackaday, Hackster, Tom's Hardware, Adafruit blog** | **No article at all**, therefore no photography. Hackaday's search API returns `[]`; Hackster's search is a JS shell with no working path |
-| **YouTube** | **Two videos**: the vendor's launch clip and one hands-on (Volos Projects, 2026-08-29). **No frames were extracted** — a video frame is a derivative of a copyrighted work and its provenance would be no clearer than the source |
-| **X / Twitter** | **Four photographs** of a PaperMono-Lite in @henry19840301's 2026-08-21 purchase post — the **only known independent photography of the product**. Individual, unlicensed, and of an unboxing rather than of the hardware's construction |
-| **r/M5Stack, Hacker News** | No teardown, no PCB photograph, no revision marking |
-| **GitHub — five third-party projects** | `MingRZou/PaperMono-Launcher` carries **one photograph** captioned "PaperMono-Launcher on real hardware" — a running screen, not a hardware view. `EggUncle/PaperMonoCalendar` is explicit that its previews are **software-generated, not device photographs** (「非设备实拍」) |
-| **`community.m5stack.com`** | **Auth-walled** (HTTP 401). The vendor forum is the likeliest home for owner photographs and **could not be searched** |
-| **Regulatory databases** | **Not searched.** M5Stack publishes no certification identifier (S11), and an FCC grantee-database search **was not attempted** — see §6 |
-
-**Two of those rows are the leads.** The vendor forum is inaccessible rather than empty, and the
-FCC database was never tried. Both could yield internal photographs.
-
-## 3. Why nothing is retained
-
-| Reason | Applies to | Detail |
-|---|---|---|
-| **Licence unknown, redistribution not permitted** | All vendor product photography, PinMap diagrams, store imagery, M5Burner cover art | M5Stack states no licence for its imagery on any page retrieved. Under the method's own labels that is `redistribution: unknown` — and **`unknown` is not permission.** The method is explicit that licensing is metadata rather than a gate *on acquisition*; it is nonetheless a gate on **redistribution**, and committing a vendor's product photography into a published repository is redistribution |
-| **Individual's copyright** | @henry19840301's four purchase photographs | One person's photographs posted to a social account. Cited as evidence in [`community.md`](community.md); not copied |
-| **Derivative of a copyrighted video** | Frames from either YouTube video | Extracting frames would produce an image whose provenance is a video the record has no rights to |
-| **Does not exist** | **Teardown, PCB front/back, enclosure-open, revision markings, component close-ups** | **A verified absence at 2026-09-01**, consistent with a product that has been purchasable for approximately nine minutes ([`market-and-pricing.md` §7](market-and-pricing.md#7-availability-history)). You cannot tear down hardware nobody can buy |
-
-**The distinction between the first three rows and the last matters.** The first three are
-*rights* problems — the images exist and a future pass with permission, or a fair-use judgement
-the user makes, could retain them. The last is an *evidence* problem, and no amount of permission
-fixes it. **Only new hardware in someone's hands fixes it.**
-
-**No watermark was removed from anything, no image was altered, and no image-search result is
-presented as provenance** — because no image was taken at all.
-
-## 4. The visual evidence that is held
-
-Two documents, both primary, both in the repository:
-
-| Artifact | Path | Bytes | SHA-256 | What it shows visually |
-|---|---|---|---|---|
-| **Schematic V0.6.2** | [`artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf`](artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf) | 1 462 039 | `b5abecac97cb043a6d1af7a673f2111d40d9254b0b5108635cb924d9b37ad6fa` | **6 sheets, Altium export.** Sheet 1 is a block diagram with the power-state matrix; sheets 2–4 the main board; sheet 5 the KEY/RGB/PDM sub-board; sheet 6 the NFC sub-board (numbered **2/2** — sheet 1 of that document is absent). This is what establishes that **the product is three PCBs plus three flexible assemblies** |
-| **Mechanical drawing** | [`artifacts/mechanical/C153_PaperMono_model_size.pdf`](artifacts/mechanical/C153_PaperMono_model_size.pdf) | 21 346 | `b833a3e52594a3175bc131006d41a3eb5662be5936d0b2f25030180033a6703b` | **1 page.** Outline dimensions, corner radii and port positions — the closest thing to a picture of the object that this record holds |
-
-Both are M5Stack-published, licence **unknown**, disposition **repository**, retrieved
-**2026-09-01**. Provenance in [`acquisition/manifest.json`](acquisition/manifest.json) and
-[`sources.md`](sources.md) (S14, S15).
-
-> **A retrieval quirk in the mechanical drawing, recorded because it will bite the next reader.**
-> Its dimensions are typeset in **full-width CJK numerals**, so text extraction yields `６２`
-> rather than `62`. Human-legible, not machine-comparable without normalisation. This is a mild
-> instance of exactly the failure mode the method warns about — trusting a PDF text layer you
-> have not validated.
-
-## 5. Derived renders that exist but are not media
-
-Rendering the retained PDFs produced page images during this pass. **They are working files, not
-media, and they are deliberately not promoted into `media/`:**
-
-| Working set | Location | What it is |
-|---|---|---|
-| Schematic sheet renders and crops | `scratch/m5stack-papermono/sheets/` (~4.0 MB) | 200 dpi renders of sheets 1, 2 and 4, plus crops of the charge block, the rails, the RTC and the EPD boost circuit. These were how the [RTC rail error](gaps-and-conflicts.md#r7--rtc-rail-the-vendor-block-diagram-is-wrong--resolved) was found — the text extraction was ambiguous and the sheet had to be *looked at* |
-| Panel-manual page renders | `scratch/m5stack-papermono/epd-pages/` (~3.7 MB) | 22 page images of the DKE panel manual, which belongs to the [panel component](../../../components/dke/depg0397bbs770f3/README.md), not to this device |
-
-**Why they are not retained.** They are **derived and exactly reproducible** from artifacts the
-repository already holds, by a documented command
-([`commands.md` §2.4](commands.md#24-rasterising-pages-for-human-reading)). Storing ~7.7 MB of
-regenerable raster alongside the 1.5 MB source it was generated from is the case
-[`SIZE-AUDIT.md`](../../../SIZE-AUDIT.md) exists to prevent. **Nothing is lost by their absence**
-— which is precisely what cannot be said of the missing photographs in §3.
-
-## 6. What a future pass should capture
-
-Ordered by how much each would change what this record knows. This is a work list, not a wish
-list.
-
-### 6.1 With hardware in hand
-
-| # | Shot | What it would settle |
-|---|---|---|
-| 1 | **PCB front and back, sharp, whole-board, with a scale reference** | Confirms the fitted BOM against the schematic — including whether the `Stamp-LoRa-1262-mini` module and the `ST25R3916-AQWT` are the parts drawn. **The schematic was recovered from invisible Altium marker text by spatial adjacency**, which yields *text adjacency, not electrical connectivity*; a photograph is an independent check on every part it shows |
-| 2 | **Macro close-ups of three top markings**: the 40 MHz crystal (`X1`), the PDM microphone, the RGB LED | The **only realistic route** to identifying `CN4040M000157A530001`, `LMD4737T261-AC02` and `RS-C1415MBAR`, whose only web occurrences anywhere are M5Stack's own pages ([G6](gaps-and-conflicts.md#g6--three-parts-have-no-obtainable-datasheet)) |
-| 3 | **The NFC sub-board, both faces** | **NFC schematic sheet 1 of 2 is not published** ([G1](gaps-and-conflicts.md#g1--nfc-schematic-sheet-1-of-2-is-not-published)). A photograph is the only available substitute for the missing sheet, and would show the antenna construction the released sheet describes in a note (4 turns, 25 × 25 mm, 0.25 mm trace, 0.3 mm gap, 17 µm copper) |
-| 4 | **The `Stamp-LoRa-1262-mini` module, close** | **No module datasheet exists anywhere.** A photograph could settle **TCXO versus XTAL** by showing whether a TCXO can is fitted — one of the record's named unknowns ([G5](gaps-and-conflicts.md#g5--no-stamp-lora-1262-module-datasheet-exists-anywhere-located)) |
-| 5 | **The back of the enclosure, and any label** | The only possible source of a regulatory identifier, since M5Stack publishes none ([G2](gaps-and-conflicts.md#g2--no-certification-identifiers-exist-on-the-vendor-site)) |
-| 6 | **Enclosure-open, showing the three-board arrangement and the three FPCs** | The record asserts the construction from title blocks and connector lists. Nothing has verified it |
-| 7 | **Any silkscreen revision marking** | There is currently **no way to distinguish hardware revisions in hand** |
-| 8 | **Panel photographs at 1, 2 and 4 grey levels, fixed lighting, with a grey step wedge** | Would bear directly on [C1](gaps-and-conflicts.md#c1--4-grey-levels-versus-2) — the vendor markets 4 grey levels and the panel manual's optical table says 2 |
-| 9 | **Ghosting series**: a fixed pattern after 1, 5, 10, 20, 50 partial refreshes, with and without the vendor's 1-in-10 full refresh | The only independent observation that exists about this display is CNX-Software's "ghosting visible in demo" — of a *video*. See [`performance.md` §7](performance.md#7-what-would-actually-settle-these-questions) |
-| 10 | **Frontlight on and off, same scene, same exposure** | Nothing shows what the frontlight actually does |
-
-### 6.2 Without hardware
-
-| # | Action | Why it is worth trying |
-|---|---|---|
-| 11 | **Search the FCC (and CE / TELEC) grantee databases** for M5Stack filings covering C153 | **Never attempted in this pass.** FCC filings routinely include **internal photographs, external photographs and label-location exhibits** — which would supply items 1, 5 and 7 above **with clear public-record provenance**. This is the single highest-value untaken imagery lead, and it needs no hardware |
-| 12 | **Re-check `community.m5stack.com` with an account** | Auth-walled at HTTP 401; the vendor forum is the likeliest first home for owner photographs |
-| 13 | **Re-run the search after the restock** | Every "none exists" on this page is a consequence of supply |
-| 14 | **Retrieve the Lite's schematic** `PaperMono-Lite_PRJ_V0.6.2_20260522.pdf` (S16) | Not fetched. `PRJ`-named with **4 sheets** against the full model's 6 — it may render differently and show different views |
-| 15 | **Ask M5Stack for permission to redistribute product imagery** | Turns a rights problem into a solved one for items 1, 3 and 10 |
-
-## 7. Rules for whoever fills this in
-
-So that a later pass does not have to re-derive the policy:
-
-1. **Record provenance at acquisition time, not afterwards.** Every retained image needs
-   creator/rightsholder where known, **source page** *and* **direct URL**, publication date,
-   retrieval date, applicable device revision, licence and the evidence for it, redistribution
-   status, modification history, local path, **caption** and **alt text**. The manifest schema in
-   [`media/manifest.json`](media/manifest.json) has a field for each; fill them or write
-   `unknown`, never omit them.
-2. **Captions explain what the image demonstrates**, plus any crop, annotation, rotation or
-   processing. "Front of the device" is not a caption; "front face showing the USB-C port on the
-   lower edge and the side RGB indicator" is.
-3. **Never remove a watermark**, and **never present an image-search result as provenance** —
-   the page an image was *found* on is not necessarily its source.
-4. **A vendor image with no stated licence is `unknown`, and `unknown` is not permission.**
-   Record the URL and the metadata; retain the bytes only on an explicit decision, and record who
-   made it.
-5. **Prefer images that establish something over images that look good.** A blurry photograph of
-   a legible top marking is worth more to this record than a studio product shot.
-6. **Hash everything**, and note whether the file is byte-identical to something already held
-   elsewhere in the repository — the `shared-assets/` pool exists for that.
-
-## 8. What can be said about the product's appearance without a photograph
-
-For identification purposes, from the mechanical drawing, the schematic and the vendor
-specification table — **all `not-tested`, none observed**:
-
-- **A closed handheld slab**, **62.0 × 101.0 × 8.0 mm**, **74.7 g** (Lite: 72.4 g), grey case
-  (Lite: **white**).
-- The **3.97-inch e-paper panel occupies most of the front face**; 480 × 800 portrait,
-  approximately 235 DPI.
-- **A USB-C port** (`U1`, `TYPEC-302-BRP16SC08`).
-- **Three switches on one sub-board**: `S1` `PWR_BTN`, `S2` `G2_KEY1` (Button A), `S3` `G3_KEY2`
-  (Button B). **There is no reset button** — the vendor's own Arduino page is wrong about this
-  ([R4](gaps-and-conflicts.md#r4--download-mode-control--resolved-on-the-balance-of-evidence)).
-- **A side RGB indicator** — three LED dies, of which **only green and blue can be dimmed**; red
-  is driven by the M5PM1's `LED_EN_PP`, which has no PWM mode.
-- **No expansion connector of any kind** — no Grove, no M-Bus. Visually, there is nothing on the
-  edges but the USB-C port and the buttons.
-- Package: 113.2 × 69.6 × 21.0 mm, gross 91.3 g.
-
-**One dimensional conflict is on record.** CNX-Software published 101 × 61 × 7.95 mm against the
-vendor's 62.0 × 101.0 × 8.0 mm. Neither was measured; this record uses the vendor's figures
-throughout.
-
-## Related
-
-- [`media/manifest.json`](media/manifest.json) — the schema, empty, with the reason recorded in it
-- [`README.md`](README.md) — the device overview, which carries the same "images: an explicit gap" note
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — G1, G2, G5, G6 and C1, each of which a photograph would help settle
-- [`community.md`](community.md) — where the photographs that do exist were found, and who owns them
-- [`commands.md` §2.4](commands.md#24-rasterising-pages-for-human-reading) — how to regenerate the derived renders in §5
-- [`acquisition/manifest.json`](acquisition/manifest.json) — provenance for the two retained documents
-- [`sources.md`](sources.md) — S11, S14, S15, S16, S72, S80–S82, S85, S87, S91, S92
diff --git a/devices/m5stack/papermono/media/manifest.json b/devices/m5stack/papermono/media/manifest.json
deleted file mode 100644
index 7fbca40..0000000
--- a/devices/m5stack/papermono/media/manifest.json
+++ /dev/null
@@ -1,107 +0,0 @@
-{
-  "device": "m5stack/papermono",
-  "device_record": "devices/m5stack/papermono",
-  "product": "M5Stack PaperMono (SKU C153) and PaperMono-Lite (SKU C153-LITE)",
-  "hardware_revision": "schematic V0.6.2",
-  "retrieved": "2026-09-01",
-  "count": 0,
-  "images": [],
-
-  "status": "EMPTY BY DECISION, NOT BY OMISSION",
-
-  "rights": "No imagery is retained. M5Stack states no licence for its product photography, PinMap diagrams, store imagery or M5Burner cover art on any page retrieved on 2026-09-01, so its redistribution status is 'unknown' - and 'unknown' is not permission. The only known independent photography is four unboxing photos in a private individual's 2026-08-21 social post (@henry19840301). No independent teardown, PCB photograph, enclosure-open view, revision marking or component close-up existed at the snapshot date: that is a verified absence, not a failed search. No watermark was removed, no image was altered and no image-search result is presented as provenance, because no image was taken.",
-
-  "reason_empty": [
-    "LICENCE - all vendor imagery carries no stated licence; redistribution status 'unknown'; committing it to a published repository would be redistribution.",
-    "THIRD-PARTY COPYRIGHT - the only independent photographs are an individual's social-media unboxing shots, cited as evidence in community.md rather than copied.",
-    "DERIVATIVE - frames from the two YouTube videos would inherit a rights problem and add no provenance.",
-    "DOES NOT EXIST - teardown, PCB front/back, enclosure-open, revision markings and component close-ups have never been published by anyone. The product was purchasable for approximately nine minutes on 2026-08-21 and was still out of stock at the snapshot date."
-  ],
-
-  "narrative": "devices/m5stack/papermono/media.md",
-
-  "visual_evidence_held_elsewhere": [
-    {
-      "kind": "schematic",
-      "file": "devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf",
-      "source_id": "S14",
-      "bytes": 1462039,
-      "sha256": "b5abecac97cb043a6d1af7a673f2111d40d9254b0b5108635cb924d9b37ad6fa",
-      "pages": 6,
-      "licence": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "shows": "Block diagram with the power-state matrix (sheet 1); main board (sheets 2-4); KEY/RGB/PDM sub-board (sheet 5); NFC sub-board (sheet 6, numbered 2/2 - sheet 1 of that document is absent from the published PDF).",
-      "note": "Not media, but it is the primary visual evidence of the board's construction."
-    },
-    {
-      "kind": "mechanical drawing",
-      "file": "devices/m5stack/papermono/artifacts/mechanical/C153_PaperMono_model_size.pdf",
-      "source_id": "S15",
-      "bytes": 21346,
-      "sha256": "b833a3e52594a3175bc131006d41a3eb5662be5936d0b2f25030180033a6703b",
-      "pages": 1,
-      "licence": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "shows": "Outline dimensions, corner radii and port positions.",
-      "note": "Dimensions are typeset in full-width CJK numerals, so text extraction yields '\uff16\uff12' rather than '62'. Legible to a human, not machine-comparable without normalisation."
-    }
-  ],
-
-  "derived_renders_not_retained": {
-    "reason": "Exactly reproducible from artifacts the repository already holds, by the documented command in commands.md section 2.4. Storing ~7.7 MB of regenerable raster beside its 1.5 MB source is what SIZE-AUDIT.md exists to prevent.",
-    "locations": [
-      "scratch/m5stack-papermono/sheets/ - 200 dpi renders and crops of schematic sheets 1, 2 and 4 (~4.0 MB)",
-      "scratch/m5stack-papermono/epd-pages/ - 22 page renders of the DKE panel manual, which belongs to components/dke/depg0397bbs770f3 (~3.7 MB)"
-    ]
-  },
-
-  "schema": {
-    "note": "Per-image record format for whoever fills this in. Every field is required. Where a value is not known, write the string \"unknown\" - do not omit the key. This extends the minimal {file,url,bytes,sha256,renamed_from} shape used by older manifests in this repository to the full field set required by the research method's visual-identification rules.",
-    "image_record": {
-      "file": "string - filename within devices/m5stack/papermono/media/",
-      "caption": "string - what the image DEMONSTRATES, plus any crop, annotation, rotation or processing applied. Not a label",
-      "alt_text": "string - descriptive alternative text for the embedded image",
-      "creator": "string - creator or rightsholder where known, else \"unknown\"",
-      "source_page": "string - the page the image was published on (NOT an image-search result page)",
-      "url": "string - direct URL to the image file",
-      "published": "string - YYYY-MM-DD publication date of the image or its page, else \"unknown\"",
-      "retrieved": "string - YYYY-MM-DD retrieval date",
-      "applies_to": "string - device SKU and hardware revision the image depicts, e.g. \"C153, schematic V0.6.2\", or \"unknown\"",
-      "licence": "string - licence expression or name, else \"unknown\"",
-      "licence_evidence": "string - where the licence was seen: a LICENSE file, a page footer, a notice inside the document, or \"none located\"",
-      "redistribution": "string - one of: allowed | conditional | restricted | unknown",
-      "disposition": "string - one of: repository | archive | reference-only",
-      "modifications": "string - crop, rotation, annotation, resize, format conversion, or \"none\"",
-      "renamed_from": "string or null - the original upstream filename if the file was renamed",
-      "bytes": "integer",
-      "sha256": "string - lowercase hex",
-      "source_id": "string or null - the S## row in sources.md, if one exists",
-      "shows": "string - which of the visual-identification classes this satisfies: front | back | ports-and-labels | enclosure-open | teardown-stage | pcb-front | pcb-back | revision-marking | component-close-up | representative-use | other"
-    }
-  },
-
-  "wanted": [
-    { "shows": "pcb-front",         "priority": 1,  "settles": "Confirms the fitted BOM against a schematic whose connectivity was recovered from invisible Altium marker text by spatial adjacency - text adjacency, not electrical connectivity" },
-    { "shows": "pcb-back",          "priority": 1,  "settles": "Same" },
-    { "shows": "component-close-up","priority": 2,  "settles": "Top markings of CN4040M000157A530001 (crystal), LMD4737T261-AC02 (PDM microphone) and RS-C1415MBAR (RGB LED) - three parts with no obtainable datasheet anywhere (gaps-and-conflicts.md G6)" },
-    { "shows": "pcb-front",         "priority": 3,  "settles": "NFC sub-board, both faces - schematic sheet 1 of 2 is unpublished (G1); a photograph is the only available substitute" },
-    { "shows": "component-close-up","priority": 4,  "settles": "Stamp-LoRa-1262-mini module - could settle TCXO versus XTAL, which no datasheet anywhere establishes (G5)" },
-    { "shows": "back",              "priority": 5,  "settles": "Any regulatory label. M5Stack publishes no certification identifier for this board (G2), so the enclosure is the only possible source" },
-    { "shows": "enclosure-open",    "priority": 6,  "settles": "The three-PCB-plus-three-FPC construction, currently asserted from title blocks and connector lists and never verified" },
-    { "shows": "revision-marking",  "priority": 7,  "settles": "There is currently no way to distinguish hardware revisions in hand; only V0.6.2 is in evidence, from a schematic filename" },
-    { "shows": "other",             "priority": 8,  "settles": "Panel at 1, 2 and 4 grey levels under fixed lighting with a grey step wedge - bears on C1, the 4-grey-versus-2-grey conflict" },
-    { "shows": "other",             "priority": 9,  "settles": "Ghosting series after 1, 5, 10, 20, 50 partial refreshes, with and without the vendor's 1-in-10 full refresh" },
-    { "shows": "other",             "priority": 10, "settles": "Frontlight on and off, same scene and exposure - nothing shows what the frontlight actually does" },
-    { "shows": "front",             "priority": 11, "settles": "Basic identification. Requires either a licence grant from M5Stack or independent photography" }
-  ],
-
-  "leads_not_requiring_hardware": [
-    "FCC / CE / TELEC grantee databases - NEVER ATTEMPTED in this pass. FCC filings routinely include internal photographs, external photographs and label-location exhibits with clear public-record provenance. This is the highest-value untaken imagery lead and it needs no hardware.",
-    "community.m5stack.com - auth-walled at HTTP 401; the vendor forum is the likeliest first home for owner photographs.",
-    "PaperMono-Lite_PRJ_V0.6.2_20260522.pdf (sources.md S16) - not fetched; PRJ-named with 4 sheets against the full model's 6, so it may render different views.",
-    "Re-run after the restock - every 'does not exist' here is a consequence of supply, not of the product.",
-    "Request redistribution permission from M5Stack for product imagery."
-  ]
-}
diff --git a/devices/m5stack/papermono/performance.md b/devices/m5stack/papermono/performance.md
deleted file mode 100644
index cba5f2a..0000000
--- a/devices/m5stack/papermono/performance.md
+++ /dev/null
@@ -1,377 +0,0 @@
-# Performance — M5Stack PaperMono
-
-> Research snapshot **2026-09-01**.
->
-> ## ⚠ Read this before anything else on this page
->
-> **No performance measurement of this device exists.** Not from M5Stack, not from any
-> independent party, and not from this research pass. There is **no** power figure for any of its
-> five power states, **no** battery runtime, **no** boot time, **no** Wi-Fi or LoRa throughput or
-> range, **no** microSD throughput, **no** NFC read latency and **no** thermal data.
->
-> This page therefore contains **four kinds of number and no measurements**:
->
-> | Kind | What it is | Where it appears |
-> |---|---|---|
-> | **Official claim** | The vendor states it; nobody has reproduced it | §2 |
-> | **Component specification** | A component maker's datasheet figure, under *that maker's* conditions | §3 |
-> | **Silicon claim** | A property of the ESP32-S3 die, not of this board | §4 |
-> | **Absence** | Nothing exists. **The largest section on this page** | §5 |
->
-> **There is no fifth column.** Nothing here is an independent measurement, a locally reproduced
-> result or an estimate. Where a comparison cannot be supported it is marked **unresolved**
-> rather than given invented precision.
-
-## Contents
-
-- [1. Why this page exists in this state](#1-why-this-page-exists-in-this-state)
-- [2. The vendor's M5GFX refresh timings](#2-the-vendors-m5gfx-refresh-timings)
-- [3. Component-level specifications](#3-component-level-specifications)
-- [4. ESP32-S3 silicon claims — not device measurements](#4-esp32-s3-silicon-claims--not-device-measurements)
-- [5. What does not exist](#5-what-does-not-exist)
-- [6. The asymmetry inside M5Stack's own catalogue](#6-the-asymmetry-inside-m5stacks-own-catalogue)
-- [7. What would actually settle these questions](#7-what-would-actually-settle-these-questions)
-- [8. Reasoning that is available without measurement](#8-reasoning-that-is-available-without-measurement)
-
----
-
-## 1. Why this page exists in this state
-
-The PaperMono's defining engineering feature is a **five-state hardware power architecture**
-implemented in a second microcontroller, with the RTC and IMU interrupts terminating on the power
-manager so the application processor can be unpowered between events
-([`power-architecture.md`](power-architecture.md)). It is marketed for "low-power IoT and embedded
-applications".
-
-**And no current figure for any of those five states has ever been published or measured.**
-
-The power-state table in the vendor's own schematic says what is *powered* in each state. It
-never says what it *costs*. That gap is tracked as
-[G7](gaps-and-conflicts.md#g7--no-power-or-battery-life-figure-exists) and it is the single most
-consequential unknown about this product: the one specification that would justify choosing it
-over its own predecessor is the one nobody has.
-
-Writing a plausible number here would be worse than writing none. So the deliverable of this page
-is the **inventory of absence** in §5, plus the honest labelling of the few numbers that do exist.
-
-## 2. The vendor's M5GFX refresh timings
-
-These four numbers are the only performance figures M5Stack publishes for this board.
-
-| Refresh mode | `epd_mode_t` | Vendor figure |
-|---|---|---|
-| Quality | `epd_quality = 1` | **4.71 s** |
-| Text | `epd_text = 2` | **0.45 s** |
-| Fast | `epd_fast = 3` | **0.34 s** |
-| Fastest | `epd_fastest = 4` | **0.07 s** |
-
-Source: the PaperMono product page (S01), under the heading *"M5GFX LUT Refresh Speed"*, with the
-vendor's own caption: *"The following data is the laboratory test result of PaperMono under
-different M5GFX refresh modes. The actual refresh time may vary depending on the display content
-and operating environment, and is provided for reference only."*
-
-**Evidence status: official claim, `not-tested`.** Now the four qualifications that must travel
-with these numbers.
-
-### 2.1 The configuration is unstated
-
-The vendor gives no temperature, no supply voltage, no test pattern, no SPI clock, no library
-version, no sample count and no variability. E-paper refresh time is strongly
-content-dependent — the vendor says so itself — so "0.34 s" without a pattern is not a
-reproducible figure. Compare the DKE panel manual, which at least states its own method: its
-4-second maximum image update time is measured at 23 °C for a transition from a horizontal
-2-scale pattern to a vertical 2-scale pattern, with the instrument named.
-
-### 2.2 They may be for a LUT set that is no longer shipped
-
-This is the qualification that matters most.
-
-- **M5Stack states that the M5GFX waveforms for the PaperMono "are currently unstable"** and
-  recommends the panel maker's OTP example instead, *for better panel life and refresh
-  stability* (S01).
-- **M5GFX `develop` has replaced the LUTs**, leaving 17 lines of the previous `lut_quality`
-  commented out in-tree, and has added a new `_refresh_mode1_text()` code path (S47).
-- **The factory firmware pins a M5GFX commit (`02107b82…`) older than either current branch.**
-
-So the published timings correspond to some specific, unnamed build. **They should not be treated
-as characteristic of any version you can check out today**, and they cannot be reproduced without
-knowing which LUTs produced them.
-
-### 2.3 The vendor-recommended path has no timings at all
-
-M5Stack's own advice is to bypass M5GFX and drive the panel with the SSD1677's factory-programmed
-OTP waveforms (`M5PaperMono-OTP-Demo`, S42). **No timing is published for that path anywhere.**
-The four numbers above therefore describe the code path the vendor tells you not to use, and the
-path it tells you to use is uncharacterised.
-
-### 2.4 The same four numbers appear on the Lite's page, uncorrected
-
-The PaperMono-Lite product page (S04) carries the identical four figures **with a caption that
-still says "laboratory test results for PaperMono"**. They were copied, not separately measured.
-Harmless — the two boards share a panel — but it establishes that these numbers are a single
-measurement event, not a body of data.
-
-### 2.5 What they are still good for
-
-Read as an **order-of-magnitude guide to the shape of the trade-off**, they are useful and they
-are corroborated in kind: a full-quality refresh is *seconds*, a partial refresh is *tenths of a
-second*, and the ratio between them is roughly 15–70×. The DKE panel manual's independent
-4-second maximum image update time sits in the same region as `epd_quality`'s 4.71 s, which is
-weak but real cross-source agreement about the magnitude.
-
-**One independent observation exists about refresh quality, and it is not a measurement.**
-CNX-Software noted "epd_fastest – 0.07 s; **note: ghosting visible in demo**" — an observation of
-M5Stack's own demo *video*, not of hardware. Consistent with the vendor's own precaution to
-perform a full refresh after roughly ten partial refreshes.
-
-## 3. Component-level specifications
-
-These are **component-maker figures under that maker's own conditions**. They constrain what the
-board can do; they are not statements about the board.
-
-### 3.1 The DKE panel's optical figures
-
-From the panel manual's optical table (**p. 5**, measured with an Eye-One Pro spectrophotometer):
-
-| Symbol | Parameter | Conditions | Min | Typ | Max | Unit |
-|---|---|---|---:|---:|---:|---|
-| `KS` | Black state L* | | – | **24** | 30 | |
-| `WS` | White state L* | | **58** | **62** | – | |
-| `WS` | **White ghosting ΔL** | Full display mode | – | **1** | – | |
-| `WS` | White ghosting ΔL | Partial display mode | – | **1** | – | |
-| `WS` | White ghosting ΔL | Full-partial display mode | – | **1** | – | |
-| `R` | **White reflectivity** | White | **26** | **30** | – | **%** |
-| `CR` | **Contrast ratio** | **Indoor** | **5** | **7** | – | |
-| `GN` | **`2Grey Level`** | – | – | – | – | |
-| `Life` | | 23 ± 3 °C, 55 ± 10 %RH | | **5 years** | | |
-
-`CR` is defined by the manual as surface reflectance with all white pixels divided by surface
-reflectance with all black pixels.
-
-**How to read these.** A contrast ratio of 5–7 with 26–30 % white reflectance is an **e-paper**
-figure, not an LCD figure — roughly newsprint. It is specified **indoor**; a reflective display
-generally improves in daylight, but that is not what this row states and no outdoor figure
-exists. The ghosting ΔL of typically 1 is the manufacturer's claim under **its own waveform**,
-which matters enormously — see the note below.
-
-**The `GN — 2Grey Level` row is an unresolved conflict.** M5Stack markets 4-level greyscale and
-its OTP demo implements a working four-grey mode; the manual's optical table says two, and the
-manual's overview describes 1-bit black and white. Three readings are plausible and nothing in
-evidence chooses between them. The least-risky assumption is that `GN` documents the *optically
-characterised* levels rather than the achievable ones — under which four-grey works but **the
-optical figures above do not apply to the intermediate levels**. Full analysis in the
-[panel component record](../../../components/dke/depg0397bbs770f3/README.md) and
-[C1](gaps-and-conflicts.md#c1--4-grey-levels-versus-2).
-
-**The 5-year life figure is a storage/ambient statement, not a refresh-count endurance rating.**
-The manual gives **no maximum refresh count anywhere** — which is exactly the number you would
-want when choosing between refresh modes on a device the vendor warns can be permanently damaged
-by continuous partial refresh.
-
-### 3.2 The DKE panel's electrical figures
-
-From the manual **p. 10, §6.2**, conditions `VSS = 0 V`, `VCI = 3.0 V`, `TOPR = 23 °C`:
-
-| Parameter | Symbol | Conditions | Typ | Max | Unit |
-|---|---|---|---:|---:|---|
-| Typical operating current | `Iopr_VCI` | VCI = 3.0 V | – | **12** | mA |
-| **Image update time** | – | 23 °C | – | **4** | **sec** |
-| Typical peak current | `Iopr_VCI` | 2.3–3.6 V | **120** | – | mA |
-| Deep-sleep mode current | `Idslp_VCI` | DC/DC off, no clock, no input load, RAM not retained | – | **1 … 5** | µA |
-
-Operating temperature `TOPR` **0 to +50 °C**; storage `TSTG` −25 to +70 °C.
-
-> ⚠ **The most consequential sentence in the panel's electrical section is note 3:** *"the listed
-> electrical characteristics are only guaranteed under the controller & waveform provided by
-> DKE"*. **M5GFX does not use that waveform** — it uploads its own LUTs from flash. So every
-> figure in this table, including the 4-second update time, the 120 mA peak and the 12 mA
-> operating current, is **untested for the M5GFX path**. The vendor's own recommendation to prefer
-> the OTP demo follows directly from this sentence.
-
-**Practical reading.** The 120 mA peak is the number that matters for battery and rail design: a
-refresh is a current *event*, not a steady load, and it lands on the `EPD_3V3_L3B` rail alongside
-whatever else is in the L3B group. The 1–5 µA deep-sleep figure is what makes an e-paper device
-plausible at all in state L0/L1 — but it is the **panel's** contribution, and the board also
-contains an always-on LDO, an M5PM1, an RTC and a charger. **The board-level idle current is not
-the panel's deep-sleep current, and nobody has measured the difference.**
-
-The panel's **0 to +50 °C operating range is the binding environmental constraint** on the whole
-device: the SSD1677 die is rated −25 to +85 °C, so reasoning from the controller datasheet alone
-over-estimates the envelope by 25 °C at one end and 35 °C at the other. Below 0 °C the ink is out
-of specification and the OTP waveform bank does not extend there.
-
-### 3.3 Other component figures that constrain the board
-
-| Constraint | Figure | Source | Why it matters here |
-|---|---|---|---|
-| **SSD1677 maximum write clock** | **20 MHz** | SSD1677 datasheet §12.1 **and** DKE manual p. 16, independently | **M5GFX drives it at 40 MHz.** The vendor's own OTP demo uses 20 MHz. Unresolved, untested, and the most likely single cause worth investigating first for refresh instability — [C3](gaps-and-conflicts.md#c3--spi-clock-exceeds-the-panels-rated-maximum) |
-| **AW9967 dimming input range** | **10–100 kHz** | AW9967 datasheet | **M5GFX programs the M5PM1 PWM at 5 kHz** — below the specified range, so dimming linearity and audible behaviour are not guaranteed. Software-fixable — [C5](gaps-and-conflicts.md#c5--frontlight-pwm-frequency-below-the-drivers-rated-range) |
-| **Frontlight current** | schematic note claims `Iset = 15 mA` at `Rset = 11 R`; **fitted `R29` is 18 Ω**, giving roughly **11 mA** | schematic (S14) | The annotation is internally inconsistent with its own formula and appears stale. **Neither figure has been measured** — [C6](gaps-and-conflicts.md#c6--frontlight-current-annotation-contradicts-the-fitted-part) |
-| **Charge current** | sheet 1 annotates `充电电流 0.5C` ≈ **575 mA** for the 1150 mAh cell | schematic (S14) | `inferred` from the annotation and the cell capacity. **The `ICHGSET` programming resistor was not resolved**, so this rests on the annotation alone |
-| **Rail current limits** | `3V3_L2` DC-DC **600 mA**; the switched LDOs **400 mA** each | schematic (S14) | These are the headroom figures a designer needs. **What the board actually draws from them is unknown** |
-| **Battery capacity** | **1150 mAh** | vendor specification | Against the PaperS3's 1800 mAh |
-
-**None of these has been measured on a PaperMono.** They are datasheet and schematic readings.
-
-## 4. ESP32-S3 silicon claims — not device measurements
-
-These are properties of the die, and they are included so that nobody reasons from a device
-absence to a silicon absence. **A silicon capability is not a device measurement**, and the method
-requires the two to stay distinct.
-
-| Property | Value | Note |
-|---|---|---|
-| Cores / clock | 2 × Xtensa LX7, **up to 240 MHz** | `CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_240=y` in the vendor's `sdkconfig.defaults`, so the shipped firmware does run at 240 MHz |
-| Internal SRAM | 512 KB | |
-| PSRAM | **8 MB octal, in package** | **Mandatory** on this board — M5GFX refuses to initialise the display without it |
-| Flash | 16 MB external `XM25UH128DHIQT`, quad-capable | Header reports DIO; hardware supports QIO ([R2](gaps-and-conflicts.md#r2--qio-versus-dio-flash--resolved)) |
-| Wi-Fi | **802.11 b/g/n, 2.4 GHz only** (Wi-Fi 4), 20/40 MHz channels | |
-| Bluetooth | **Bluetooth 5 LE and Mesh. No Classic (BR/EDR) — a hardware absence** | No IDF version, Arduino core or library can add BR/EDR. See the [component record](../../../components/espressif/esp32-s3r8/README.md#radio-capabilities-and-the-classic-bluetooth-limitation) |
-| Vector extensions | **PIE** 128-bit SIMD (TRM ch. 1) | Relevant to pixel-format conversion for the framebuffer. **Not known to be used by any code on this board** |
-
-**Two warnings about using this table.**
-
-*Do not translate silicon numbers into device numbers.* "240 MHz dual-core" says nothing about
-this board's boot time, and "Wi-Fi 4" says nothing about its throughput through an FPC antenna
-inside a plastic case beside an e-paper panel. Antenna performance is a board property and **no
-antenna characterisation exists for this board at all**.
-
-*One silicon-level caveat applies directly and is worth checking.* The in-package octal PSRAM is
-subject to the ESP32-S3's documented **120 MHz octal-PSRAM temperature fragility** — see
-[`guides/espressif/esp-idf-peripheral-capabilities.md`](../../../guides/espressif/esp-idf-peripheral-capabilities.md#43-esp32-s3--120-mhz-octal-psram-is-temperature-fragile).
-Nothing in the vendor's `sdkconfig.defaults` selects 120 MHz PSRAM, so the shipped configuration
-is not exposed to it; a build that raises the PSRAM clock would be. `inferred`, `not-tested`.
-
-## 5. What does not exist
-
-**This is the deliverable of this page.** Every row is an explicit gap, not an omission.
-
-| Workload | What is missing | Vendor figure? | Independent figure? | Derived here? |
-|---|---|---|---|---|
-| **Power — state L0 (shipping)** | quiescent current | **none** | none | none |
-| **Power — state L1 (standby)** | current with RTC + IMU alive | **none** | none | none |
-| **Power — state L2 (deep sleep)** | current with the ESP32-S3 powered but asleep | **none** | none | none |
-| **Power — L3A / L3B (active)** | current with panel / frontlight / SD / mic up | **none** | none | none |
-| **Battery runtime** | hours or days in any duty cycle | **none** | none | none |
-| **Frontlight power** | current at any brightness | **none** — and even the *design* current is contested (§3.3) | none | none |
-| **Boot time** | cold boot to first pixel; wake-from-L1 to first pixel | **none** | none | none |
-| **Wi-Fi** | throughput, range, RSSI, antenna pattern, TX current | **none** | none | none |
-| **Bluetooth LE** | anything at all — **BLE is not even in the vendor's specification table** | **none** | none | none |
-| **LoRa** | range, link budget, sensitivity, TX current, TCXO vs XTAL, `SX_ANT_SW` semantics | **none**; **no `Stamp-LoRa-1262` module datasheet exists anywhere** ([G5](gaps-and-conflicts.md#g5--no-stamp-lora-1262-module-datasheet-exists-anywhere-located)) | none | none |
-| **NFC** | read range, read latency, which card types actually interoperate | **none** | none | none |
-| **microSD** | read/write throughput, capacity or filesystem limits | **none** | none | none |
-| **Microphone** | SNR, sensitivity, sample rates beyond the 16 kHz the demo uses | **none** — **no datasheet for `LMD4737T261-AC02` exists anywhere** ([G6](gaps-and-conflicts.md#g6--three-parts-have-no-obtainable-datasheet)) | none | none |
-| **Touch** | latency, accuracy, report rate | **none** | none | none |
-| **Display (OTP path)** | refresh timings for the path the vendor **recommends** | **none** (§2.3) | none | none |
-| **Display endurance** | maximum refresh count before degradation | **none** — the panel manual omits it | none | none |
-| **Thermal** | any temperature, anywhere, under any load | **none** — **no operating-temperature range is published for the product at all** | none | none |
-| **PSRAM / memory bandwidth** | framebuffer fill rate, DMA contention | **none** | none | none |
-| **Concurrent workloads** | e-paper refresh + microSD + Wi-Fi together | **none** | none | none |
-
-**Every cell in the last three columns is empty**, and the vendor column is empty for every row.
-That is twenty-odd workloads with zero data points.
-
-The concurrency row deserves separate mention because it is the case most worth testing first,
-and [`resources-and-conflicts.md` §10](resources-and-conflicts.md#10-realistic-simultaneous-use-scenarios)
-already works out *why*: there is no pin conflict between an e-paper refresh, an SDMMC transfer
-and Wi-Fi, so the pressure lands on **GDMA clients**, **PSRAM bandwidth**, and the **`3V3_L2`
-600 mA rail and the battery** — a Wi-Fi TX burst on top of an SD write burst on top of a 120 mA
-panel peak, with no published figure for any of the three. **Nobody has demonstrated this
-combination.**
-
-## 6. The asymmetry inside M5Stack's own catalogue
-
-This is the most damning single fact on the page, and it is a measurement of the *documentation*,
-not of the device.
-
-| Product | Vendor-published power consumption | Vendor-published operating temperature |
-|---|---|---|
-| **M5PaperS3** (`C139`) | **Low-power mode: DC 4.2 V / 9.28 µA** (main power off, gyroscope in low-power mode)<br>**Standby: DC 4.2 V / 949.58 µA** (main power off, gyroscope on)<br>**Operating: DC 4.2 V / 154.02 mA** (main power on) | **0 ~ 40 °C** |
-| **M5Paper Color** (`C151`) | **Standby: 92.53 µA**<br>**Full load: 211.97 mA** | not stated |
-| **PaperMono** (`C153`) | **— nothing. The specification table has no power-consumption row at all** | **— nothing** |
-| **PaperMono-Lite** (`C153-LITE`) | **— nothing** | **— nothing** |
-
-Retrieved from `docs.m5stack.com` product pages, 2026-09-01. The PaperMono absence is a **verified
-negative**: a full-text search of the retrieved 153 939-byte page finds zero occurrences of
-"Power Consumption" and zero of "temperature" outside the sun-exposure precaution.
-
-**M5Stack publishes two-decimal-place current figures for the two immediately adjacent products
-in the same product line, and none whatsoever for the one whose headline feature is a five-state
-power-management system.** No explanation for this is available and none should be invented — a
-new product's characterisation may simply not be finished. But the consequence is concrete: the
-PaperS3's numbers are the only power data that exists anywhere in this family, and they are for a
-**different board with a different power architecture, a different RTC, no I/O expander and no
-M5PM1**.
-
-> **Do not use the PaperS3 figures as a proxy for the PaperMono.** They come from a board that
-> has none of the PaperMono's five-state hardware, and the PaperMono adds an always-on LDO, an
-> always-powered RTC, an M5PM1 and an M5IOE1 that the PaperS3 does not have. The direction of the
-> difference is not even obvious: more always-on silicon could plausibly make the PaperMono's
-> deepest state *worse*, while its ability to remove power from whole domains could make it much
-> better. **Nothing in evidence says which.**
-
-The PaperColor rows are worth a second glance for a different reason: at 92.53 µA standby it is
-**an order of magnitude worse than the PaperS3's 9.28 µA low-power figure** — which shows that
-these numbers vary by 10× across boards from the same vendor in the same line, and therefore that
-extrapolating one to another is not a small approximation.
-
-## 7. What would actually settle these questions
-
-For whoever gets hardware. Ordered by value per unit of effort.
-
-| # | Measurement | Method | Why first |
-|---|---|---|---|
-| 1 | **Current in each of L0, L1, L2, L3A, L3B** | Series shunt or a source-meter at the battery connector `J2`; hold each state through the M5PM1 API | It is the product's headline claim and it has **never been measured**. One afternoon closes the biggest gap in this record |
-| 2 | **Refresh timing on the OTP path** at 20 MHz, against M5GFX at 40 MHz | Instrument `BUSY` (GPIO18) with a scope or a GPIO toggle; run the OTP demo and an M5GFX build | Tests [C3](gaps-and-conflicts.md#c3--spi-clock-exceeds-the-panels-rated-maximum) — the clock overrun — **and** produces the timings the recommended path lacks |
-| 3 | **Ghosting after N partial refreshes**, with and without the vendor's 1-in-10 full refresh | Photograph a fixed pattern under fixed lighting at intervals | Tests the vendor's own precaution, and the one independent observation that exists (CNX's "ghosting visible in demo") |
-| 4 | **Frontlight current at 0/64/128/255** | Shunt on `BL_15V_L3B` | Settles [C6](gaps-and-conflicts.md#c6--frontlight-current-annotation-contradicts-the-fitted-part) — 15 mA annotation against ~11 mA from the fitted `R29` — and characterises the squared gamma curve |
-| 5 | **Battery runtime at a stated duty cycle** — e.g. wake on RTC every 15 min, refresh, sleep | Run to cut-off, log timestamps to microSD | The number every buyer actually wants. Meaningless without (1) |
-| 6 | **Boot and wake latency** | GPIO toggle at first line of `app_main` and at refresh completion | Cheap; nobody has it |
-| 7 | **Concurrent e-paper + microSD + Wi-Fi** | The scenario in [`resources-and-conflicts.md` §10](resources-and-conflicts.md#10-realistic-simultaneous-use-scenarios) | The most likely place a real application falls over |
-| 8 | **LoRa range and TX current** at a stated SF/BW/power | Field test with a known counterpart | Also the only way to resolve whether the module has a TCXO |
-| 9 | **NFC interoperability** across ISO14443A/B, FeliCa, ISO15693 cards | Read a set of known cards | The vendor claims four standards; **none has been demonstrated** |
-| 10 | **Thermal under sustained Wi-Fi TX and refresh** | Thermocouple or IR, ambient stated | No thermal data of any kind exists, and the panel is only rated to +50 °C |
-
-**Whoever does (1) should publish it.** It is the highest-value missing datum about this product
-in the world, and it requires one board and a meter.
-
-## 8. Reasoning that is available without measurement
-
-Three things can be said honestly from architecture alone, provided they are labelled as such.
-
-**The display costs nothing to hold.** An e-paper panel is bistable — it retains its image with
-no power. So the useful mental model is that a refresh is a **current event** (120 mA peak per
-the panel manual, under DKE's waveform) rather than a continuous load, and a static page costs
-whatever the *rest* of the board costs. This is the reason the power architecture, not the
-display, is the interesting engineering. **`inferred` from the panel's bistability; no board-level
-figure exists.**
-
-**The always-on set is small and is enumerable from the schematic.** In state L0 the powered
-items are the charger, the protection circuitry, the `3V3_L0` LDO, the M5PM1, and — because the
-vendor's own block diagram is wrong about this — the **RX8130CE RTC**, whose `VBAT`, `VIO`, `VDD`
-and `VOUT` are all tied to `3V3_L0`
-([R7](gaps-and-conflicts.md#r7--rtc-rail-the-vendor-block-diagram-is-wrong--resolved)). That is a
-short list, and it is the list a measurement of (1) would be attributing current to. **What each
-contributes is unknown.**
-
-**Every optional rail defaults off.** Each switched LDO carries a 1 MΩ pulldown on its enable
-(`R24`, `R26`, `R23`), so a cold power-up brings nothing up beyond L0. That is the correct
-failure mode for a battery product, and it means the *floor* of the board's consumption is
-architecturally low. It says nothing about the actual value.
-
-**What cannot be reasoned to:** any number. Do not multiply a datasheet's typical current by a
-duty cycle and present the result as a battery life. That is the exact failure the method's
-"distinguish official claims, silicon limits, estimates and measurements" rule exists to prevent,
-and it is why no estimate appears anywhere on this page.
-
-## Related
-
-- [`power-architecture.md`](power-architecture.md) — the five states, every rail and its enable, and what is *not* established
-- [`features/epaper-display.md`](features/epaper-display.md) — the refresh modes and the OTP path
-- [`features/power-and-sleep.md`](features/power-and-sleep.md) — how to reach each state from code
-- [`resources-and-conflicts.md` §10](resources-and-conflicts.md#10-realistic-simultaneous-use-scenarios) — concurrent-use analysis, all untested
-- [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) — why the battery-first verdict cannot be settled
-- [`components/dke/depg0397bbs770f3`](../../../components/dke/depg0397bbs770f3/README.md) — the panel's full optical and electrical tables, with DKE's note 3
-- [`components/espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) — silicon capabilities and their limits
-- [`gaps-and-conflicts.md` G7](gaps-and-conflicts.md#g7--no-power-or-battery-life-figure-exists) — the canonical gap entry
-- [`sources.md`](sources.md) — S01, S04, S14, S20, S21, S47
diff --git a/devices/m5stack/papermono/pin-naming-and-the-pyg-ambiguity.md b/devices/m5stack/papermono/pin-naming-and-the-pyg-ambiguity.md
deleted file mode 100644
index 10e2dcc..0000000
--- a/devices/m5stack/papermono/pin-naming-and-the-pyg-ambiguity.md
+++ /dev/null
@@ -1,152 +0,0 @@
-# PaperMono pin naming: why `PYG3` means two different things
-
-> **Status:** resolved from primary evidence (official schematic), 2026-09-01.
-> This document exists because three independent readings of the vendor
-> documentation reached three different conclusions, two of them wrong. The
-> underlying fact is small and the consequence is not: acting on the wrong
-> reading of `PYG3` cuts power to the e-paper panel instead of dimming the
-> frontlight.
-
-Related: [`pinouts-and-buses.md`](pinouts-and-buses.md) ·
-[`components/m5stack/m5pm1`](../../../components/m5stack/m5pm1/README.md) ·
-[`components/m5stack/m5ioe1`](../../../components/m5stack/m5ioe1/README.md) ·
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md)
-
-## The short version
-
-The PaperMono carries **two** M5Stack custom chips, and the schematic uses the
-`PYG` prefix for **both** — but at different layers of the drawing.
-
-| Chip | `PYG<n>` appears as | The other layer is |
-|---|---|---|
-| **M5IOE1** (I/O expander, I²C `0x4F`) | the **symbol pin name** — `PYG1` … `PYG14` | net names, which are `PYB_<function>` |
-| **M5PM1** (power management, I²C `0x6E`) | the **net name** — `PYG0_RTC_INT`, `PYG2_LoRa_EN`, `PYG3_BL_PWM`, `PYG4_IMU_INT` | symbol pin names, which are `G<n>_WAKEin(...)_IRQout_<cap>` |
-
-The convention is *inverted* between the two chips. So the bare token `PYG3`
-denotes an M5IOE1 **pin** and an M5PM1 **net**, in the same document, and they
-are not the same signal:
-
-| Token | On M5IOE1 it is | On M5PM1 it is |
-|---|---|---|
-| `PYG2` | pin 11 → `PYB_LoRa_ANT_SW` (LoRa antenna switch) | pin 20 → `PYG2_LoRa_EN` (LoRa rail enable) |
-| `PYG3` | pin 14 → `PYB_EPD_EN` (**e-paper 3.3 V rail enable**) | pin 13 → `PYG3_BL_PWM` (**frontlight brightness PWM**) |
-| `PYG4` | pin 16 → `PYB_NFC_EN` (NFC enable) | pin 12 → `PYG4_IMU_INT` (IMU wake interrupt) |
-
-`PYG0` exists only on the M5PM1 — the M5IOE1's pins start at `PYG1`, and its
-Arduino library has no `PIN_0` constant. `PYG5`–`PYG14` exist only on the
-M5IOE1. The collision is confined to `PYG2`, `PYG3` and `PYG4`.
-
-## Evidence
-
-Recovered from the official schematic
-[`artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf`](artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf)
-using [`tools/altium_pdf_pin_table.py`](../../../tools/altium_pdf_pin_table.py),
-which pairs Altium's invisible `PI<designator><pin>` markers with the
-human-readable text sharing their row. Evidence status: `executed-success`
-(the extraction was run; the readings below were then checked against the
-rendered sheet).
-
-**M5PM1 — designator `U7`, sheet 2.** Symbol pin name on the left, attached net
-on the right:
-
-| Pin | Symbol pin name | Net |
-|---|---|---|
-| 3 | `G0_WAKEin(INT0/2)_IRQout_NEOPIXEL` | `PYG0_RTC_INT` |
-| 12 | `G4_WAKEin(INT3/4)_IRQout_PWM` | `PYG4_IMU_INT` |
-| 13 | `G3_WAKEin(INT3/4)_IRQout_PWM` | `PYG3_BL_PWM` |
-| 17 | `G1_IRQout_ADC` | `G1_PY_IRQ` |
-| 20 | `G2_WAKEin(INT0/2)_IRQout_ADC` | `PYG2_LoRa_EN` |
-
-Note pin 17: its net is `G1_PY_IRQ`, **not** `PYG1_…`. The M5PM1 net prefix is
-not applied consistently even within its own symbol — which is part of why the
-pattern is easy to miss.
-
-**M5IOE1 — designator `U17`, sheet 4.** The relationship is the other way round:
-
-| Pin | Symbol pin name | Net |
-|---|---|---|
-| 7 | `PYG1` | `PYB_TF_DET` |
-| 11 | `PYG2_ADC1` | `PYB_LoRa_ANT_SW` |
-| 12 | `PYG8_PWM2` | `PYB_LED_G` |
-| 13 | `PYG9_PWM1` | `PYB_LED_B` |
-| 14 | `PYG3` | `PYB_EPD_EN` |
-| 15 | `PYG13` | `PYB_TP_EN` |
-| 16 | `PYG4_ADC2` | `PYB_NFC_EN` |
-| 17 | `PYG5_ADC3` | `PYB_EINK_RST` |
-| 18 | `PYG6` | `PYB_TP_RST` |
-| 19 | `PYG7_ADC4` | `ADD_SET` |
-| 20 | `PYG10_PWM4` | `PYB_LoRa_RST` |
-| 10 | `PYG11_PWM3` | `PYB_CHG_IIC` |
-| 5 | `PYG12` | `PYB_PDM_EN` |
-| 3 | `PYG14` | `PYB_TF_EN` |
-
-The `_ADC<n>` and `_PWM<n>` suffixes match the M5IOE1 manual's channel tables
-position for position, which independently confirms that `PYG<n>` on this symbol
-is the expander's `IO<n>`.
-
-## Where the prefix comes from
-
-Schematic sheet 1 lists the board's device classes, and gives both custom chips
-the same underlying part: **`PY32L020F15U6`**, annotated `PY32L020F15U6_IIC` — a
-Puya PY32 Cortex-M0+ microcontroller running M5Stack firmware, not an ASIC. See
-[`components/puya/py32l020f15u6`](../../../components/puya/py32l020f15u6/README.md).
-
-`PY` is therefore *the die*, not *the role*, and `PYG<n>` reads as "PY32 GPIO n".
-Applying that prefix to two different PY32s in one design is what produces the
-ambiguity. `PYB_*` appears to be the companion prefix for signals crossing out of
-a PY32 into the rest of the board, but M5Stack does not document either
-convention, so this reading is `inferred`.
-
-## What the vendor documentation actually says — a correction
-
-An earlier pass in this research session concluded that the vendor's PaperMono
-product page was **defective** where it says the frontlight is driven by
-"`PYG3_BL_PWM` of the M5PM1", on the reasoning that `PYG` is an M5IOE1-only
-prefix (the M5PM1 Arduino library defines only `M5PM1_GPIO_NUM_0…_4` and no
-`PYG` identifier appears in it). It further concluded that the PaperMono-Lite
-page, which calls the same pin "`G3_WAKEin` of M5PM1", was the correct one.
-
-**That conclusion is refuted.** The schematic shows `PYG3_BL_PWM` is a real net
-name on M5PM1 pin 13. Both vendor pages are correct; they simply quote different
-layers of the same drawing — the PaperMono page quotes the net name, the
-PaperMono-Lite page quotes the symbol pin name. The Arduino library is a third
-naming system again, and its silence about `PYG` is evidence about the library,
-not about the schematic.
-
-Recorded here per the evidence rules: a refuted hypothesis is written down with
-what refuted it and the date, so it is not re-investigated. Date of refutation
-2026-09-01; refuting artifact `PaperMono_SCH_V0.6.2_20260522.pdf`, sheets 2 and 4.
-
-The vendor documentation is, on this point, **already correct**. The defect is
-in its ambiguity, not its accuracy.
-
-## The practical hazard
-
-Both readings of `PYG3` are live pins that do something, so a mistake is silent
-rather than inert:
-
-- Intending **frontlight brightness** and writing to **M5IOE1 IO3** removes the
-  e-paper panel's 3.3 V supply. The display stops updating; nothing reports an
-  error.
-- Intending **e-paper power** and writing to **M5PM1 G3** changes backlight
-  brightness and leaves the panel powered.
-
-A second, independent off-by-one compounds this. In the vendor Arduino
-libraries the two chips number their pins differently:
-
-- `M5IOE1_PIN_3 = 2` — the label is 1-based, the enum value 0-based
-- `M5PM1_GPIO_NUM_3 = 3` — label and value agree
-
-So passing a documentation "`PYG<n>`" straight into the M5IOE1 API reaches pin
-*n+1*. See the warning sections in the two component records for the exact
-`file:line` citations.
-
-## Recommendation
-
-Never write `PYG<n>` without naming the chip. In this knowledge base the
-convention is:
-
-- **`M5PM1.G3`** for the power-management chip's GPIO 3 (frontlight PWM)
-- **`M5IOE1.IO3`** for the expander's IO 3 (e-paper rail enable)
-
-and the raw schematic tokens are quoted only when citing the schematic directly.
diff --git a/devices/m5stack/papermono/pinouts-and-buses.md b/devices/m5stack/papermono/pinouts-and-buses.md
deleted file mode 100644
index c4c906c..0000000
--- a/devices/m5stack/papermono/pinouts-and-buses.md
+++ /dev/null
@@ -1,310 +0,0 @@
-# PaperMono — pinouts, buses and architecture
-
-> Board: M5Stack PaperMono, SKU C153. Hardware revision as documented:
-> schematic **V0.6.2**, file dated 2026-05-22, PDF exported 2026-06-08 and last
-> modified 2026-07-28.
-> Research snapshot 2026-09-01.
-
-Primary source for everything on this page is the official schematic,
-[`artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf`](artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf),
-read with [`tools/altium_pdf_pin_table.py`](../../../tools/altium_pdf_pin_table.py).
-Where the vendor product page or the vendor firmware says something different,
-both are given and the disagreement is recorded rather than settled by
-preference.
-
-**Read [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md) before
-using any `PYG*` name from vendor documentation.** The same token denotes
-different pins on the two custom chips.
-
-## Contents
-
-- [Board set — this is not one PCB](#board-set--this-is-not-one-pcb)
-- [ESP32-S3 complete pin map](#esp32-s3-complete-pin-map)
-- [Pins that are not available](#pins-that-are-not-available)
-- [I²C bus](#i²c-bus--the-one-shared-bus)
-- [SPI buses](#spi-buses)
-- [M5IOE1 expander pins](#m5ioe1-expander-pins)
-- [M5PM1 power-manager pins](#m5pm1-power-manager-pins)
-- [Connectors](#connectors)
-- [Boot, reset and download mode](#boot-reset-and-download-mode)
-
-## Board set — this is not one PCB
-
-The schematic PDF concatenates **three separate Altium documents**, which is
-directly visible in the title blocks and in the fact that reference designators
-restart per document (there are three different `U1`s, two `X1`s, two `ANT1`s).
-Treat a designator as meaningful only together with its sheet number.
-
-| Sheets | Document | Title block | What it is |
-|---|---|---|---|
-| 1–4 | main project (title block left blank) | — | Main board: block diagram, power, MCU, peripherals |
-| 5 | `PaperMono KEY RGB.SchDoc` | dated 2026-04-14 | Sub-board: 2 user keys, power button, RGB LED, PDM microphone |
-| 6 | `02 Paper Mono NFC.SchDoc` | rev **V0.2**, dated 2026-07-28, marked **sheet 2/2** | Sub-board: ST25R3916 NFC reader, its crystal and antenna |
-
-**Sheet 1 of 2 of the NFC document is not present in the published PDF.** The
-included sheet is explicitly numbered `2/2`. This is an omission in the vendor's
-export, not an absence of circuitry — treat NFC front-end details not visible on
-sheet 6 as undocumented rather than as not-fitted. Recorded as an open gap in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-Off-board assemblies reach the main board through connectors rather than being
-drawn: the e-paper panel, the touch panel, the frontlight, and the LoRa module.
-
-## ESP32-S3 complete pin map
-
-The MCU is a bare **ESP32-S3R8** die in a 56-pin QFN (designator `U12`, sheet 3),
-not a module — 8 MB in-package octal PSRAM, no in-package flash. Component
-record: [`components/espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md).
-
-Every row below was read from the schematic symbol. `—` means the pin carries no
-net label on the sheet.
-
-| GPIO | Pin | Net | Function | Notes |
-|---|---|---|---|---|
-| GPIO0 | 5 | `G0_BOOT_OUT` | Boot strap, driven by M5PM1 `BOOT_OUT_OD` | strapping pin |
-| GPIO1 | 6 | `G1_PY_IRQ` | M5PM1 interrupt to host | |
-| GPIO2 | 7 | `G2_KEY1` | User button A | also an M5PM1 wake source |
-| GPIO3 | 8 | `G3_KEY2` | User button B | strapping pin; also an M5PM1 wake source |
-| GPIO4 | 9 | `G4_TP_INT` | Touch controller interrupt | |
-| GPIO5 | 10 | `G5_LoRa_INT` | LoRa `DIO1` / IRQ | |
-| GPIO6 | 11 | `G6_RFID_INT` | ST25R3916 IRQ | |
-| GPIO7 | 12 | `G7_PYB_IRQ` | M5IOE1 `OD_INTOUT` interrupt | |
-| GPIO8 | 13 | `G8_TF_DATA3` | microSD DAT3 | |
-| GPIO9 | 14 | `G9_TF_DATA2` | microSD DAT2 | |
-| GPIO10 | 15 | `G10_TF_DATA1` | microSD DAT1 | |
-| GPIO11 | 16 | `G11_TF_DATA0` | microSD DAT0 | |
-| GPIO12 | 17 | `G12_TF_CMD` | microSD CMD | |
-| GPIO13 | 18 | `G13_TF_CLK` | microSD CLK | 22 Ω series (`R35`) |
-| GPIO14 | 19 | `G14_SPI2_MOSI` | E-paper SDA (SPI data) | |
-| GPIO15 | 21 | `G15_SPI2_CLK` | E-paper SCL (SPI clock) | 22 Ω series (`R38`) |
-| GPIO16 | 22 | `G16_EINK_CS` | E-paper CSB | |
-| GPIO17 | 23 | `G17_EINK_DC` | E-paper D/C | |
-| GPIO18 | 24 | `G18_EINK_BUSY` | E-paper BUSY_N | input |
-| GPIO19 | 25 | `G19_USB_N` | USB D− | via `FT1` common-mode filter |
-| GPIO20 | 26 | `G20_USB_P` | USB D+ | via `FT1` common-mode filter |
-| GPIO21 | 27 | `G21_LoRa_BUSY` | LoRa `BUSY` | |
-| GPIO26 | 28 | — | not connected | in-package flash CS, unused |
-| GPIO33 | 38 | — | **reserved** | octal PSRAM |
-| GPIO34 | 39 | — | **reserved** | octal PSRAM |
-| GPIO35 | 40 | — | **reserved** | octal PSRAM |
-| GPIO36 | 41 | — | **reserved** | octal PSRAM |
-| GPIO37 | 42 | — | **reserved** | octal PSRAM |
-| GPIO38 | 43 | `G38_SPI1_MOSI` | LoRa SPI MOSI | |
-| GPIO39 | 44 | `G39_SPI1_CLK` | LoRa SPI CLK | 22 Ω series (`R34`) |
-| GPIO40 | 45 | `G40_SPI1_MISO` | LoRa SPI MISO | |
-| GPIO41 | 47 | `G41_LoRa_NSS` | LoRa chip select | |
-| GPIO42 | 48 | `G42_BB_PWM` | Buzzer drive | |
-| GPIO43 | 49 | `G43_U0_TX` | UART0 TX | 499 Ω series (`R30`) |
-| GPIO44 | 50 | `G44_U0_RX` | UART0 RX | |
-| GPIO45 | 51 | `G45_PDM_CLK` | PDM microphone clock | strapping pin |
-| GPIO46 | 52 | `G46_PDM_DAT` | PDM microphone data | strapping pin |
-| GPIO47 | 37 | `G47_SYS_SDA` | **System I²C SDA** | 2.2 kΩ pull-up (`R36`) |
-| GPIO48 | 36 | `G48_SYS_SCL` | **System I²C SCL** | 2.2 kΩ pull-up (`R37`) |
-
-Flash interface (dedicated pins, sheet 3): `SPICLK` p33 → `NOR_SCK`,
-`SPICS0` p32 → `NOR_CS`, `SPID` p35 → `NOR_DI`, `SPIQ` p34 → `NOR_DO`,
-`SPIWP` p31 → `NOR_WP`, `SPIHD` p30 → `NOR_HOLD`. Supply `VDD_SPI` p29.
-`CHIP_PU` p4 carries `SOC_RESET`. Crystal `XTAL_P`/`XTAL_N` p54/p53 to a 40 MHz
-`CN4040M000157A530001` with 24 pF loading caps.
-
-This matches the vendor product page's pin tables everywhere the two overlap.
-The schematic additionally establishes **USB (GPIO19/20)** and **UART0
-(GPIO43/44)**, which the product page does not list at all.
-
-### Prose: what this map means in practice
-
-Nearly every GPIO is committed. Of the 45 pins the ESP32-S3 brings out on this
-package, five are consumed by in-package octal PSRAM, six by the microSD slot in
-4-bit mode, five by the e-paper, six by LoRa, two by USB, two by UART0, two by
-I²C, two by the microphone, one by the buzzer, and the remainder by buttons and
-the six interrupt lines from the expander, power manager, touch, IMU, RTC and
-NFC. **There is no free GPIO on a header, and there is no expansion header at
-all** — unlike most M5Stack cores, the PaperMono exposes no Grove or M-Bus
-connector. Any additional peripheral has to go on the shared I²C bus or take
-over one of the M5IOE1's expander pins.
-
-The consequence for firmware authors is that the M5IOE1 is not an optional
-convenience. Panel power, panel reset, touch power, touch reset, microSD power,
-card detect, microphone power, NFC enable, LoRa reset, LoRa antenna switch, two
-of the three LED colours and the charger's bus gate are *all* behind it. Losing
-I²C means losing the ability to power-cycle the display.
-
-## Pins that are not available
-
-| Pins | Why |
-|---|---|
-| GPIO33–GPIO37 | Octal PSRAM. The ESP32-S3**R8** carries 8 MB OPI PSRAM in package and these five pins are consumed by it. |
-| GPIO26 | In-package flash chip select on other ESP32-S3 variants; unconnected here. |
-| GPIO22–GPIO25, GPIO27–GPIO32 | Do not exist on the ESP32-S3. |
-
-**Octal PSRAM is a hard build requirement, not a preference.** M5GFX aborts
-display initialisation with `"M5PaperMono need OPI-PSRAM enabled"` if the build
-does not select it. The failure presents as a blank screen on an otherwise
-working board with a single log line — a build misconfiguration that looks like
-dead hardware. Set `board_build.arduino.memory_type = qio_opi`.
-
-## I²C bus — the one shared bus
-
-A single I²C bus on **GPIO47 (SDA) / GPIO48 (SCL)**, pulled up by 2.2 kΩ to
-`3V3_L2`, carries seven devices.
-
-| Address | Device | Component record | Notes |
-|---|---|---|---|
-| `0x32` | RX8130CE RTC | [record](../../../components/seiko-epson/rx8130ce/README.md) | `nIRQ` → M5PM1 G0 |
-| `0x38` | FT6336G touch | [record](../../../components/focaltech/ft6336g/README.md) | on the touch FPC |
-| `0x4F` | M5IOE1 I/O expander | [record](../../../components/m5stack/m5ioe1/README.md) | address is **undocumented** — see below |
-| `0x50` | ST25R3916 NFC | [record](../../../components/stmicroelectronics/st25r3916/README.md) | on the NFC sub-board |
-| `0x68` | BMI270 IMU | [record](../../../components/bosch-sensortec/bmi270/README.md) | alternate `0x69`; bus clocked at **100 kHz** for this device |
-| `0x6E` | M5PM1 power manager | [record](../../../components/m5stack/m5pm1/README.md) | |
-| `0x75` | IP2315 charger | [record](../../../components/injoinic/ip2315/README.md) | **normally gated off the bus** — see below |
-
-All seven addresses were confirmed both in the vendor firmware source and on the
-vendor product page; none conflict.
-
-**Two traps on this bus.**
-
-*The charger is not always present.* The IP2315's I²C mode depends on its bus
-pins being pulled to `VBAT`, and the vendor documents that a low battery can
-leave it failing to enter I²C mode and disturbing everyone else on the bus. The
-M5IOE1's `IO11` (`PYB_CHG_IIC`) gates the charger onto the bus, and the vendor's
-guidance is to attach it only for the duration of a transaction. A scan that does
-not first assert that gate will simply not find `0x75`, and that is correct
-behaviour, not a fault. The IP2315 datasheet additionally documents a bus-lockup
-mechanism involving a missing NACK on the final read byte, which is presumably
-why the gate exists at all.
-
-*The expander's address is not in its own manual.* Everything — firmware,
-product page, this board — uses `0x4F`, but the M5IOE1 V1.4 manual states the
-address range `0x6F`–`0x76` in three separate places, and the chip's `IO7` is
-genuinely wired to an `ADD_SET` divider. The vendor library constant is even
-named `..._ADDR_2` and its autodetect sweeps both ranges. Unresolved; see
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-## SPI buses
-
-Two SPI peripherals plus the dedicated flash interface.
-
-| Bus | Signals | Device | Clock |
-|---|---|---|---|
-| SPI2 | GPIO14 MOSI, GPIO15 CLK, GPIO16 CS, GPIO17 DC, GPIO18 BUSY | E-paper (SSD1677) | M5GFX drives **40 MHz**; vendor OTP demo uses 20 MHz |
-| SPI1 | GPIO38 MOSI, GPIO39 CLK, GPIO40 MISO, GPIO41 NSS | Stamp LoRa-1262 | RadioLib default |
-| SPI0 | dedicated `SPICLK/CS0/D/Q/WP/HD` | XM25UH128DHIQT 16 MB NOR flash | quad-capable |
-
-The e-paper link is **write-only** — there is no MISO, and status is read
-through the `BUSY` line alone.
-
-**A clock conflict worth knowing about.** M5GFX runs the panel at 40 MHz, while
-the SSD1677 datasheet (§12.1) and the DKE panel manual (p. 16) *both* state a
-20 MHz maximum write clock, and the vendor's own OTP demo uses 20 MHz. This may
-be a factor in the refresh instability M5Stack itself warns about. Recorded as a
-conflict; not tested on hardware.
-
-Flash is wired for quad operation — all four data lines are routed — and the
-`Q` in `XM25UH128DHIQT` denotes a factory-set QE bit. The vendor PlatformIO
-snippet accordingly specifies `qio_opi`. The shipped factory image nevertheless
-reports **DIO** in its header; since `sdkconfig.defaults` pins no flash mode,
-that is an ESP-IDF default rather than a hardware limit. The hardware supports
-QIO.
-
-## M5IOE1 expander pins
-
-I²C `0x4F`, interrupt on `OD_INTOUT` → ESP32-S3 GPIO7. Vendor firmware polls it
-(`M5IOE1_INT_MODE_DISABLED`) rather than using the interrupt.
-
-| Pin (symbol) | Net | Function |
-|---|---|---|
-| `PYG1` | `PYB_TF_DET` | microSD card detect (pulled up by the card's own power domain; low = inserted) |
-| `PYG2_ADC1` | `PYB_LoRa_ANT_SW` | LoRa antenna switch |
-| `PYG3` | `PYB_EPD_EN` | **E-paper 3.3 V rail enable** |
-| `PYG4_ADC2` | `PYB_NFC_EN` | NFC enable |
-| `PYG5_ADC3` | `PYB_EINK_RST` | E-paper reset |
-| `PYG6` | `PYB_TP_RST` | Touch reset |
-| `PYG7_ADC4` | `ADD_SET` | Own I²C address select |
-| `PYG8_PWM2` | `PYB_LED_G` | RGB green |
-| `PYG9_PWM1` | `PYB_LED_B` | RGB blue |
-| `PYG10_PWM4` | `PYB_LoRa_RST` | LoRa reset |
-| `PYG11_PWM3` | `PYB_CHG_IIC` | IP2315 I²C bus gate |
-| `PYG12` | `PYB_PDM_EN` | Microphone power enable |
-| `PYG13` | `PYB_TP_EN` | Touch power enable |
-| `PYG14` | `PYB_TF_EN` | microSD power enable |
-
-Two of these are **absent from the vendor product page's pin tables**: `PYG4`
-(NFC enable, used by the firmware) and `PYG7` (`ADD_SET`). The product page is
-otherwise complete and accurate.
-
-> **Off-by-one.** In the vendor Arduino library `M5IOE1_PIN_3 = 2` — the label is
-> 1-based, the enum value 0-based. `M5PM1_GPIO_NUM_3 = 3` does not do this.
-> Passing a documentation `PYG<n>` straight into the M5IOE1 API silently reaches
-> pin *n+1*.
-
-## M5PM1 power-manager pins
-
-I²C `0x6E`, interrupt on `G1_PY_IRQ` → ESP32-S3 GPIO1. Five GPIOs; see the
-[component record](../../../components/m5stack/m5pm1/README.md) for the full
-21-pad table and register map.
-
-| Pin | Symbol name | Net | Function |
-|---|---|---|---|
-| 3 | `G0_WAKEin(INT0/2)_IRQout_NEOPIXEL` | `PYG0_RTC_INT` | RTC alarm — wake source |
-| 17 | `G1_IRQout_ADC` | `G1_PY_IRQ` | Interrupt out to host |
-| 20 | `G2_WAKEin(INT0/2)_IRQout_ADC` | `PYG2_LoRa_EN` | LoRa rail enable |
-| 13 | `G3_WAKEin(INT3/4)_IRQout_PWM` | `PYG3_BL_PWM` | **Frontlight brightness PWM** |
-| 12 | `G4_WAKEin(INT3/4)_IRQout_PWM` | `PYG4_IMU_INT` | IMU interrupt — wake source |
-
-Rail enables and analogue inputs are separate pins: `LDO3V3_EN_PP`,
-`DCDC3V3_EN_PP`, `BOOST5V_EN_PP`, `CHG_EN_PP`, `BAT_ADC_EN_OD`, `BAT_ADC_IN`,
-`5VIN_ADC_IN`, `5VOUT_ADC_IN`, `LED_EN_PP`, `BTN_PU`, `BOOT_OUT_OD`. See
-[`power-architecture.md`](power-architecture.md).
-
-The IMU and RTC interrupts land on the **power manager**, not on the ESP32-S3.
-That is what allows the board to be woken from its deepest states by a motion
-event or an alarm while the application processor is unpowered.
-
-## Connectors
-
-| Ref | Sheet | Part | Pins | Carries |
-|---|---|---|---|---|
-| `J5` | 4 | `FPC0.5-SMT-24P-B` | 24 | E-paper panel — SPI, BUSY, RST, DC, CS, and the panel's own boost rails (`GDR`, `RESE`, `VDHR`, `VSH`, `VGH`, `VSL`, `VGL`, `VCOM`) |
-| `J4` | 4 | — | 8 | Touch panel FPC — `TP_SYS_SDA`, `TP_SYS_SCL`, `G4_TP_INT`, `PYB_TP_RST`, `TP_VDD` |
-| `J1` | 2 | — | 6 | Frontlight — `PYG3_BL_PWM`, `BL_FB`, `BL_15V_L3B` |
-| `J6` | 4 | `AXE512127D` | 12 + 4 tabs | Board-to-board to the KEY/RGB/PDM sub-board — keys, `PWR_BTN`, `PY_LED_R`, `PYB_LED_G/B`, PDM clock and data |
-| `J3` | 4 | `BTB0.408-10PLBDR-G41` | 10 | Board-to-board to the NFC sub-board — I²C, `G6_RFID_INT`, `PYB_NFC_EN`, `3V3_L2` |
-| `U14` | 4 | `Stamp-LoRa-1262-mini` | 13 | LoRa module — SPI, `SX_BUSY`, `LORA_IRQ`, `SX_NRST`, `SX_ANT_SW`, `VIN_3V3` |
-| `J2` | 2 | `CON2_SMD` | 2 | Battery **only** — pin 2 `VBAT_L0`, pin 1 GND. **No thermistor pin**; see note below |
-| `USB` | 2 | `TYPEC-302-BRP16SC08` | 16 | USB-C receptacle. **Its designator is the bare string `USB`, not `U1`** |
-
-> **The battery connector has no NTC pin.** `J2` is a 2-contact part carrying
-> only `VBAT_L0` and ground. The `100K-RNTC` thermistor is **`R15`, a mainboard
-> component on the IP2315's `NTC` pin (26)** — so pack temperature is inferred
-> from a thermistor near the charger, not sensed inside the cell. Whether `R15`
-> is thermally coupled to the cell by layout is not established from the
-> schematic. Earlier revisions of this record said "NTC-sensed at `J2`"; that was
-> wrong. Source: [`bill-of-materials.md`](bill-of-materials.md).
-
-The e-paper FPC pinout matches the DKE panel manual's Input/Output Pin
-Assignment table (p. 7) position for position — an independent cross-check that
-the schematic extraction is being read correctly.
-
-**USB-C is power and data only.** The CC resistors are marked `NC` on the
-schematic, so there is no USB-PD negotiation; combined with an upstream ~5.95 V
-OVP this is a plain 5 V input.
-
-## Boot, reset and download mode
-
-- `CHIP_PU` is driven by `SOC_RESET`; the M5PM1 owns the reset.
-- GPIO0 is driven by the M5PM1's open-drain `BOOT_OUT_OD`, so **the power
-  manager, not a physical button, puts the ESP32-S3 into download mode.**
-- Documented user procedure: hold the power button about 2 s until the red LED
-  blinks, then release.
-- Power on / reset: one short press. Power off: two presses in succession.
-- GPIO3, GPIO45 and GPIO46 are strapping pins that also carry user button B and
-  the PDM microphone. Driving the microphone or holding button B during reset
-  perturbs straps; the vendor firmware does not appear to guard against this.
-  `inferred` from the pin map, `not-tested`.
-
-The product page and the Arduino tutorial page disagree about which control
-enters download mode — the former says the power button, the latter refers to a
-"reset button on the side". The schematic shows three switches on the KEY/RGB
-sub-board (`S1` `PWR_BTN`, `S2` `G2_KEY1`, `S3` `G3_KEY2`) and no separate reset
-button, which supports the power-button reading. Recorded in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
diff --git a/devices/m5stack/papermono/power-architecture.md b/devices/m5stack/papermono/power-architecture.md
deleted file mode 100644
index c5ab314..0000000
--- a/devices/m5stack/papermono/power-architecture.md
+++ /dev/null
@@ -1,219 +0,0 @@
-# PaperMono — power architecture
-
-> Source: official schematic `PaperMono_SCH_V0.6.2_20260522.pdf`, sheets 1
-> (block diagram / power-state matrix) and 2 (power circuits), read as rendered
-> images at 200 dpi as well as by text extraction. Research snapshot 2026-09-01.
-> Evidence status `executed-success` for extraction, `not-tested` for every
-> current, timing and behavioural claim — nothing here was measured on hardware.
-
-Related: [`pinouts-and-buses.md`](pinouts-and-buses.md) ·
-[`components/m5stack/m5pm1`](../../../components/m5stack/m5pm1/README.md) ·
-[`components/injoinic/ip2315`](../../../components/injoinic/ip2315/README.md) ·
-[`components/awinic/aw9967`](../../../components/awinic/aw9967/README.md)
-
-## Why this board has a power architecture at all
-
-Most ESP32 boards have a regulator and a charger. The PaperMono has a
-**five-state power state machine implemented in a second microcontroller**, and
-that is the single most important thing to understand about the product. The
-e-paper panel holds its image with no power at all, so the interesting engineering
-is not in driving the display — it is in switching almost everything else off
-while remaining able to wake on a touch, a button, a motion event, an RTC alarm,
-a LoRa packet, an NFC field or a card insertion.
-
-The state machine lives in the **M5PM1**, which schematic sheet 1 identifies as a
-`PY32L020F15U6` — a Puya Cortex-M0+ microcontroller running M5Stack firmware,
-not a fixed-function PMIC. It owns the ESP32-S3's reset and boot straps, so in
-power terms the application processor is a peripheral of the power manager
-rather than the other way round.
-
-## The five power states
-
-Sheet 1 tabulates them as columns. Names are the vendor's.
-
-| State | Name | What is on | Wakes on |
-|---|---|---|---|
-| **L0** | Shipping | Charger, protection, `3V3_L0` only. M5PM1 alive. | Power button, USB insertion |
-| **L1** | Standby | + `3V3_L1` — RTC and IMU powered | Power button, RTC alarm, IMU motion |
-| **L2** | DeepSleep | + `3V3_L2` — ESP32-S3, touch, NFC, keys, expander | + touch, keys, NFC, LoRa |
-| **L3A** | Core active | + e-paper rail `EPD_3V3_L3B` | — |
-| **L3B** | All active | + frontlight `BL_15V_L3B`, microSD `TF_3V3_L3B`, microphone `PDM_VDD` | — |
-
-The vendor's stated transitions:
-
-- **Into L0** — the ESP32-S3 issues an I²C shutdown command to the M5PM1.
-- **L0 → L1** is automatic.
-- **L1 → L2** is enabled by the M5PM1 on a single power-button click, an IMU
-  interrupt, or an RTC interrupt.
-- **L3** switches are asserted by the ESP32-S3 through the M5IOE1.
-
-Sheet 1's own annotation for the button behaviour is `开机` (power on) beside
-`PWR_BTN`, and `唤醒` (wake) beside the L2 wake sources.
-
-## Rails and what produces them
-
-| Rail | Source | Enable | Feeds |
-|---|---|---|---|
-| `VUSB_IN` | USB-C connector | — | input only |
-| `VBUS_L0` | battery bus after protection; tied to `VBAT_L0` through `R20` (0 Ω) | — | everything downstream |
-| `3V3_L0` | `U4` SSP7615-33DFR LDO, 400 mA | always on | M5PM1, always-on logic |
-| `3V3_L1` | `U6` SSP7615-33DFR LDO, 400 mA | `3V3_L1_EN` ← M5PM1 `LDO3V3_EN_PP` | IMU (**not** the RTC — see below) |
-| `3V3_L2` | `U10` JW5712 DC-DC, 600 mA, `L2` = 2.2 µH | `3V3_L2_EN` ← M5PM1 `DCDC3V3_EN_PP` | ESP32-S3, I²C bus pull-ups, keys, NFC sub-board |
-| `3V3_L2_LoRa` | `U9` SSP7615-33DFR LDO, 400 mA | `PYG2_LoRa_EN` ← **M5PM1 G2** | Stamp LoRa-1262 |
-| `EPD_3V3_L3B` | `U5` SSP7615-33DFR LDO, 400 mA | `PYB_EPD_EN` ← **M5IOE1 IO3** | e-paper panel |
-| `BL_15V_L3B` | `U11` AW9967 boost | `PYG3_BL_PWM` ← **M5PM1 G3**, feedback `BL_FB` | frontlight |
-| `TF_3V3_L3B` | `U8` AW35122 load switch | `PYB_TF_EN` ← M5IOE1 IO14 | microSD |
-| `TP_VDD` | `U18` AW35122 load switch | `PYB_TP_EN` ← M5IOE1 IO13 | touch controller |
-| `PDM_VDD` | `U21` AW35122 load switch | `PYB_PDM_EN` ← M5IOE1 IO12 | PDM microphone |
-| `VDD_NOR` | from `3V3_L2` domain | — | SPI NOR flash |
-
-Each switched LDO carries a 1 MΩ pulldown on its enable (`R24`, `R26`, `R23`),
-so every optional rail defaults **off** on cold power-up. That is the correct
-failure mode for a battery product, and it means firmware must explicitly bring
-up the panel rail before the display will respond — a blank screen is the
-expected result of forgetting.
-
-> **Naming trap.** `VBUS_L0` is *not* USB VBUS. USB 5 V is `VUSB_IN`; `VBUS_L0`
-> is the internal battery/system bus, tied to `VBAT_L0` through a 0 Ω link
-> (`R20`). Reading `VBUS` as "USB power" inverts the entire tree.
-
-### The RTC is on `3V3_L0`, not `3V3_L1` — the vendor block diagram is wrong
-
-Sheet 1's power-state matrix places both the RTC and the IMU on `3V3_L1`, i.e.
-powered from state L1 upward. Reading the actual circuit on **sheet 4**
-contradicts this for the RTC.
-
-The RX8130CE (`U16`) has `VBAT` (pin 10), `VIO` (pin 1), `VDD` (pin 8) and
-`VOUT` (pin 9) **all tied to the same node, and that node is `3V3_L0`** — the
-always-on rail. Its `nIRQ` pull-up (`R49`, 100 kΩ) also goes to `3V3_L0`. The
-IMU beside it genuinely is on `3V3_L1`.
-
-This is architecturally the *better* arrangement — an RTC that loses power in
-shipping mode would be useless — so the block diagram is the document at fault,
-not the board. Evidence: sheet 4 rendered at 200 dpi and read directly;
-`executed-success` for the extraction, `not-tested` electrically.
-
-Two consequences follow:
-
-- **The RTC keeps time in L0.** Sheet 1 implies it does not.
-- **There is no separate backup cell.** `VBAT` is tied to `VDD`, so the
-  RX8130CE's backup-supply input is the main rail. M5Unified's `begin()` sets
-  `CHGEN=1`, enabling the backup-charge path — into a node that is already the
-  supply. At best a no-op; it is not charging a coin cell, because there isn't
-  one. Flagged rather than asserted as a defect: `inferred`.
-
-Also worth recording because the method distinguishes them: `nRSTO` (pin 5) and
-`FOUT` (pin 4) carry **drawn no-connect markers**. That is a positive assertion
-by the designer that they are unused, not a blank cell that merely tells us
-nothing.
-
-## Charging and USB input
-
-```
-USB-C  →  AW32901FCR (OVP = 5.95 V, surge protection)  →  IP2315 charger  →  battery
-                                                              ↕ I²C @ 0x75
-                                                         via U3 level translator
-                                                         gated by M5IOE1 IO11
-```
-
-- **`U2` AW32901FCR** sits on the USB input. Its schematic annotation reads
-  `OVP = 5.95V`. This is **input over-voltage and surge protection, not battery
-  protection** — a distinction worth stating because the part sits where a
-  battery protector normally would.
-- **`U10`… no: `U10` is the DC-DC.** The charger is the Injoinic **IP2315**,
-  identifiable by its `LED1/SCL`, `LED2/SDA`, `VSYS`, `LX`, `CC1`, `CC2`, `HLED`
-  and `nACOK` pins. Sheet 1 annotates the charge current as `充电电流 0.5C`
-  — 0.5 C, i.e. about 575 mA for the 1150 mAh cell. `inferred` from the
-  annotation and the cell capacity. The programming resistor is now resolved:
-  **`R17` = 15 kΩ on `ICHGSET`** (and `R18` = `NC` on `LED3`), a value that does
-  not appear in the IP2315 datasheet's tabulated set — recorded as a conflict.
-- **No USB-PD.** The connector carries **both** standard 5.1 kΩ CC pulldowns
-  (`R4` on CC1 **and** `R14` on CC2) that advertise a plain sink, but the **IP2315's own `CC1`/`CC2`
-  sense pins are unpopulated** (`R1`, `R2` marked `NC`). Combined with the
-  5.95 V OVP upstream, this is a 5 V-only input; the charger's PD capability is
-  deliberately depopulated. *(Two earlier readings of this circuit disagreed —
-  one saw only the `NC` resistors and concluded there were no CC resistors at
-  all. Both resistor groups exist and they are on different parts.)*
-- Battery connects at `J2` (`CON2_SMD`), a **2-contact** part carrying only
-  `VBAT_L0` and ground. The `100K-RNTC` thermistor is **`R15` on the mainboard**,
-  at the IP2315's `NTC` pin — not inside the pack. Capacity 1150 mAh, per the vendor specification.
-
-### The charger is normally *off* the I²C bus
-
-This is the board's sharpest design quirk and it is documented by M5Stack
-themselves.
-
-The IP2315's I²C pins must be pulled to `VBAT`, not to the 3.3 V logic rail. The
-schematic solves this with **`U3`, a dual-bit bidirectional level translator**
-(`VCCA`/`VCCB`/`A1`/`B1`/`A2`/`B2`/`OE`) bridging the system bus
-(`G47_SYS_SDA` / `G48_SYS_SCL`) to a `VBAT`-referenced charger bus
-(`CHG_SYS_SDA` / `CHG_SYS_SCL`). Its **output enable is `PYB_CHG_IIC`, driven by
-M5IOE1 IO11.**
-
-So `0x75` is only present on the bus while firmware has asserted that pin. The
-vendor's guidance is to attach the charger, transact, and detach promptly,
-because leaving it attached degrades bus stability — and if the battery is too
-low the IP2315 may fail to enter I²C mode at all and disturb the other six
-devices. The IP2315 datasheet documents a bus-lockup mechanism involving a
-missing NACK on the final byte of a read, which is presumably the specific
-failure being avoided.
-
-**Consequence for anyone writing an I²C scanner:** not finding `0x75` is normal.
-The vendor's documented recovery from a wedged bus is a short press of the power
-button, which resets the device.
-
-## Frontlight
-
-The e-paper frontlight is a boost converter (`U11`, Awinic **AW9967**) producing
-`BL_15V_L3B` from the L3B domain, with current feedback on `BL_FB` set by `R29`
-and brightness controlled by a PWM input from **M5PM1 G3** (`PYG3_BL_PWM`).
-
-Two independent observations about how M5Stack drives it, both worth knowing
-before trusting the brightness curve:
-
-- M5GFX programs the M5PM1's PWM at **5 kHz** (registers `0x34`/`0x35`), while
-  the AW9967 datasheet specifies a **10–100 kHz** dimming input range. Below the
-  specified range, dimming linearity and audible behaviour are not guaranteed.
-- M5GFX applies a **squared gamma curve** to the requested brightness before
-  writing the duty registers (`0x30`/`0x31`), so `setBrightness(128)` is roughly
-  a quarter of full output, not half.
-- The schematic's own note claims `Iset = 15 mA` at 100 % duty with
-  `Rset = 11 R`, but the fitted `R29` is **18 Ω**, which gives roughly 11 mA. The
-  note's arithmetic is also internally inconsistent with its own formula. Treat
-  the annotation as stale.
-
-All three are software or documentation issues rather than hardware faults, and
-all three are fixable without touching the board.
-
-## Wake sources and how they reach the M5PM1
-
-| Source | Path | Note |
-|---|---|---|
-| Power button | `PWR_BTN` → M5PM1 `BTN_PU` | single press = on/reset, double press = off |
-| RTC RX8130CE | `nIRQ` → `PYG0_RTC_INT` → **M5PM1 G0** | alarm/timer wake from L1 |
-| IMU BMI270 | `INT1` → `PYG4_IMU_INT` → **M5PM1 G4** | motion wake from L1 |
-| Touch FT6336G | `G4_TP_INT` → ESP32-S3 GPIO4 | "touch-to-wake supported" per sheet 1; wakes from L2 |
-| Keys | `G2_KEY1`, `G3_KEY2` → ESP32-S3 | also listed as M5PM1 wake inputs on sheet 1 |
-| LoRa, NFC, microSD insert | to ESP32-S3 | sheet 1 marks LoRa, NFC and card-detect as wake-capable |
-
-The critical structural point is that **the RTC and IMU interrupts do not go to
-the ESP32-S3 at all.** They terminate on the power manager. That is what makes
-an alarm-driven or motion-driven wake possible from a state in which the
-application processor has no power.
-
-The shipped factory firmware's own log string confirms the intent and the
-polarity: `PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge`. Note that
-the vendor's prose documentation describes this interrupt as *active-high*,
-while the code (`BMI2_INT_ACTIVE_LOW` + `WAKE_FALLING`) and the shipped binary
-both say active-low. The prose is the outlier.
-
-## What is not established
-
-- No current or battery-life figure of any kind is published, and none was
-  measured. The state table says what is *powered*, not what it *costs*.
-- The IP2315 charge-current programming resistor was not resolved from the
-  schematic, so the 0.5 C figure rests on the sheet-1 annotation alone.
-- The `U4` (`3V3_L0`) enable net could not be read with confidence; it is drawn
-  as permanently enabled, but that is `inferred`.
-- Whether L3A and L3B are genuinely separate switch groups or a documentation
-  distinction is not clear from the schematic; the rails they name overlap.
diff --git a/devices/m5stack/papermono/product-history-and-family.md b/devices/m5stack/papermono/product-history-and-family.md
deleted file mode 100644
index a0d88a5..0000000
--- a/devices/m5stack/papermono/product-history-and-family.md
+++ /dev/null
@@ -1,314 +0,0 @@
-# Product history, family and culture — M5Stack PaperMono
-
-> Research snapshot **2026-09-01**, eleven days after launch. Every date below comes from a
-> machine-readable field — a Shopify `published_at`, a GitHub API `created_at`, a PDF `ModDate`,
-> a JSON-LD `datePublished`, a schematic title block or an `esp_app_desc_t` — rather than from
-> prose that says "in August". Where a date is an approximation of something else, that is said.
->
-> The README carries a nine-row summary of this timeline. **This page is the evidenced version**:
-> what each row rests on, what it does and does not establish, and the family comparison in full.
-
-## Contents
-
-- [1. The timeline, row by row, with its evidence](#1-the-timeline-row-by-row-with-its-evidence)
-- [2. What the design dates tell you](#2-what-the-design-dates-tell-you)
-- [3. The M5Paper family](#3-the-m5paper-family)
-- [4. PaperMono is not a successor to the PaperS3](#4-papermono-is-not-a-successor-to-the-papers3)
-- [5. What is shared across the family, and what is not](#5-what-is-shared-across-the-family-and-what-is-not)
-- [6. PaperMono and PaperMono-Lite](#6-papermono-and-papermono-lite)
-- [7. Positioning, audience and product culture](#7-positioning-audience-and-product-culture)
-- [8. What is not established](#8-what-is-not-established)
-
----
-
-## 1. The timeline, row by row, with its evidence
-
-All timestamps normalised to UTC where the source carried a zone.
-
-| Date (UTC) | Event | Evidence | What it establishes — and what it does not |
-|---|---|---|---|
-| **2026-04-14** | KEY/RGB sub-board schematic dated | Sheet 5 title block, `PaperMono KEY RGB.SchDoc` (S14) | The sub-board carrying both user keys, the power button, the RGB LED and the PDM microphone was drawn by this date. It is a *title-block* date — the date someone typed, not a commit |
-| **2026-05-07** | `m5stack/M5PaperMono-UserDemo` repository created on GitHub | GitHub API `created_at` (S41) | **The earliest public trace of the product**, 3½ months before launch. Creation of an empty or private-then-public repo, not publication of its contents |
-| **2026-05-22** | Main schematic **V0.6.2** dated | Filename `PaperMono_SCH_V0.6.2_20260522.pdf` (S14) | The revision in the published PDF. A filename date; the PDF itself was created later |
-| **2026-06-08** | Schematic PDF created | PDF `CreationDate` (S14) | When the export was produced — 17 days after the design date it carries |
-| **2026-07-28** | NFC sub-board schematic **V0.2** dated; schematic PDF last modified | Sheet 6 title block and PDF `ModDate` (S14) | The NFC sub-board is the **latest-revised** part of the design. The PDF was re-exported the same day the NFC sheet is dated, which is why the NFC sheet is V0.2 while the main project is V0.6.2 |
-| **2026-08-06 16:12:13** | Factory firmware image built | `esp_app_desc_t` in the shipped binary (S38) | An exact build timestamp from the artifact itself — the most precise date in this table. Built from an **uncommitted tree** ([`factory-firmware.md` §6](factory-firmware.md#6-why-c78f6c5-dirty-means-not-reproducible)) |
-| **2026-08-10 17:28:58 +08:00** | `M5PaperMono-UserDemo` HEAD commit `c1099107…` ("update firmware v1.2") | GitHub API (S41) | The published source moved **four days after** the shipped image was built, and does not correspond to it |
-| **2026-08-17** | Leak: r/M5Stack post "Paper Mono coming August 21st", citing an M5Stack YouTube Short | Reddit (S70) | The launch date was public four days early, **from the vendor's own channel**. In the same thread, third-party library authors claim support — necessarily written against documentation, not hardware |
-| **2026-08-18 06:29 UTC** (14:29 +08:00) | Both storefront products created, unpublished | Shopify `created_at` (S48, S49) | The Lite record was created **three minutes before** the PaperMono's (14:26:42 vs 14:29:31 +08:00) |
-| **2026-08-18 09:09 UTC** (17:09 +08:00) | Factory firmware uploaded to M5Burner as v1.2 | M5Burner API `uploadedAt` (S33, S34) | Twelve days after the image was built |
-| **2026-08-20** | `m5stack/M5PaperMono-OTP-Demo` repository created | GitHub API (S42) | The panel-maker OTP waveform example — the code M5Stack recommends **over its own graphics library** — appeared one day before launch |
-| **2026-08-20** | Documentation published under category "Controllers" | `/en/history` (S13) | The docs release date, distinct from both Shopify dates. Also the mechanical drawing's PDF `CreationDate`/`ModDate` (S15) |
-| **2026-08-21 04:00 UTC** (12:00 +08:00) | **Store publishes both SKUs**; vendor blog announcement | Shopify `published_at` (S48, S49); blog `<time datetime>` (S50) | The commercial launch instant. The Lite published **one second before** the PaperMono (12:00:09 vs 12:00:10) |
-| **2026-08-21 04:09 UTC** | First independent buyer reports the Lite already sold out — **nine minutes later** | @henry19840301, with four photographs (S72) | The checkable fact is a **9-minute gap** between publication and a sell-out report. The poster's own phrase was "sold out in just one second"; that is colloquial, and the nine minutes is what the evidence supports |
-| **2026-08-21 05:19 UTC** | LinuxGizmos article published — **1 h 19 min after the store**, but with a **byline dated Aug 20** | JSON-LD `datePublished` (S76) | The byline predating publication is consistent with an embargoed press push. It does **not** establish that the article was written before launch, only that a date field says so |
-| **2026-08-21 04:12 UTC** (06:12 +02:00) · **10:15 UTC** (11:15 +01:00) | OpenELAB (.io, then .de a minute later) and The Pi Hut list the product | Shopify `created_at` (S53–S55) | Resellers listed within hours — OpenELAB **twelve minutes** after the store published. None had stock |
-| **2026-08-21 06:59 UTC** | M5Stack YouTube "New Arrivals: PaperMono & PaperMono-Lite" | YouTube `uploadDate` (S81) | Vendor video, 16 938 views at snapshot |
-| **2026-08-21 08:44 UTC** | M5Stack posts to r/M5Stack; later states pre-orders "reached the limit" | Reddit API (S71) | **A direct vendor statement**, primary, that the batch was capped |
-| **2026-08-21 ~12:00 UTC** | First Hacker News submission — 2 points, 1 comment | HN (S69) | Landed ~8 h post-announcement and already out of stock |
-| **2026-08-21 16:43 UTC** | CNX-Software article (modified 08-22) | WP REST `date` (S77) | Contains the only two independent observations in any written piece (§7) |
-| **2026-08-22 07:49 UTC** | M5Stack X post "PaperMono vs PaperMono-Lite" | fxtwitter API (S75) | Vendor marketing; the thread root of the restock exchange |
-| **2026-08-22 10:09 UTC** | @berryxia asks for a restock, reports stock gone the previous day | fxtwitter API (S73) | Second independent failed-purchase report |
-| **2026-08-22 10:54 UTC** | **M5Stack replies 「要等两三个月了」 — "you'll have to wait two or three months"** | fxtwitter API (S74) | **The primary vendor restock statement.** It conflicts with CNX-Software's "next year" ([C7](gaps-and-conflicts.md#c7--restock-timing)). Note also: the widely repeated claim that the delay is an e-ink driver IC shortage **does not appear anywhere in this tweet or its reply chain**, which was retrieved in full |
-| **2026-08-22 12:44 UTC** (20:44 +08:00) | Community CrossPoint e-reader image uploaded to M5Burner | M5Burner API (S35) | **One day after launch, a third party had working firmware published.** Built 2026-08-22 19:58:33 |
-| **2026-08-23 21:48 UTC** | MuyLinux (ES) publishes a translation of the LinuxGizmos piece | JSON-LD (S78) | Re-syndication, not coverage |
-| **2026-08-25** | `MagicCube/free-ink-on-paper-mono` created | GitHub API (S89) | First third-party project. Author is the same person as the 2026-08-21 purchase report — ownership corroborated across two surfaces |
-| **2026-08-27** | `hectorzin/M5PaperMono-HomeAssistant-ESPHome` created | GitHub API (S93) | ESPHome bring-up, explicitly labelled a test hypothesis by its own author |
-| **2026-08-27 17:50 UTC** | Hacker News front page — **162 points, 58 comments** | HN Algolia (S68) | The largest discussion anywhere, and it contains **no firsthand PaperMono measurement at all** |
-| **2026-08-28 12:10 UTC** | Liliputing Lilbits roundup mention | JSON-LD (S79) | Contains the "$55 with NFC and LoRa" error (§6) |
-| **2026-08-29 16:21 UTC** | **Volos Projects hands-on video** — the only one found | YouTube `uploadDate` (S80) | Day 8. Self-described first look; carries a vendor referral link |
-| **2026-08-30** | `MingRZou/PaperMono-Launcher` created | GitHub API (S91) | Self-described hardware-validated; a **port** of a PaperS3 launcher (§4) |
-| **2026-08-31** | `EggUncle/PaperMonoCalendar` created | GitHub API (S92) | Honest about showing software-generated previews rather than device photographs |
-| **2026-09-01** | **Research snapshot.** Both SKUs still out of stock at the official store | Shopify `product.available = false` (S48, S49) | Out of stock for all but nine minutes of its commercial life |
-
-### What this timeline is not
-
-It is a **reproducible broad-coverage snapshot dated 2026-09-01**, not proof that nothing else
-happened. Two things in particular are outside it: `community.m5stack.com` is auth-walled
-(`/api/search` → HTTP 401), so the vendor's own forum — the likeliest first home for owner
-reports — could not be searched at all; and Mouser, DigiKey and TinyTronics were bot-walled, so
-their listing dates are unknown rather than absent.
-
-## 2. What the design dates tell you
-
-Three readings the raw table does not make obvious.
-
-**The product was in the open, quietly, for 3½ months.** The UserDemo repository was created on
-2026-05-07 and the schematic is dated 2026-05-22. Anyone watching `github.com/m5stack` had the
-product name in May. That is unremarkable for M5Stack but it is the kind of fact that resolves
-"when did this leak" questions later.
-
-**The NFC sub-board is the youngest part of the design.** Main project V0.6.2 dated 2026-05-22;
-NFC sub-board V0.2 dated 2026-07-28, and the PDF re-exported that same day. Ten weeks of
-divergence between the two, on the one sub-assembly whose schematic is also **incomplete in the
-published PDF** — the included NFC sheet is explicitly numbered `2/2` and sheet 1 is absent
-([G1](gaps-and-conflicts.md#g1--nfc-schematic-sheet-1-of-2-is-not-published)). Those two facts
-are consistent with the NFC section being the last thing finished, which is a plausible reason
-an export missed a sheet. **`inferred`; there is no statement from M5Stack about it.**
-
-**The published source does not correspond to the shipped firmware, and the dates show it.**
-Image built 2026-08-06 from a `-dirty` tree; repository HEAD committed 2026-08-10. Whatever was
-in the working tree on 6 August was never published as such. See
-[`factory-firmware.md` §6](factory-firmware.md#6-why-c78f6c5-dirty-means-not-reproducible).
-
-**M5Stack develops on an internal GitLab and publishes to GitHub.** Both demo repositories have
-squashed three-commit histories and the OTP demo's HEAD message is literally
-`Merge GitLab initial history`. Upstream history is therefore **not available** — which is why
-`created_at` on a GitHub repo is the earliest date this record can offer rather than a real
-project start.
-
-## 3. The M5Paper family
-
-Every row from M5Stack's own storefront JSON (`shop.m5stack.com/products/<handle>.json`) and
-documentation pages, retrieved **2026-09-01**.
-
-| Product | SKU | Store price 2026-09-01 | Storefront published | Store status | Display | Notes |
-|---|---|---|---|---|---|---|
-| **CoreInk** | `K048` | USD 29.90 | 2020-11-06 | active | 1.54" e-paper | Not a "Paper"-series device; included so the e-paper line is complete |
-| **M5Paper** | `K049` | USD 85.00 | **2020-11-27** | **`[EOL]`** in title | 4.7", 960 × 540 | **ESP32**, not S3 |
-| **M5Paper V1.1** | `K049-B` | USD 85.00 | 2021-06-23 | active | 4.7", 960 × 540 | Still listed as non-EOL although the original is EOL |
-| **M5Paper COMM Edition** | `K049-C` | USD 79.00 | 2022-01-17 | **`[EOL]`** | 4.7" | Comms-oriented variant |
-| **M5PaperS3** | `C139` | USD 59.00 | **2024-12-13** | **`[EOL]`** | 4.7" `EPD_ED047TC1`, 960 × 540, **16-level** grey, GT911 two-point touch | ESP32-S3R8, **1800 mAh**, BM8563 RTC, BMI270, 1 button, no frontlight, HC1.25-4PLT expansion port |
-| **M5Paper Color** | `C151` | USD 75.00 | 2026-05-15 | active | 4" E Ink **Spectra 6** `ED2208-DOA (EL040EF1)`, 400 × 600 | ESP32-S3R8, 1250 mAh, ES8311 codec + speaker + mic, SHT40, 3 user buttons, RX8130CE RTC |
-| **PaperMono** | `C153` | USD 65.00 | **2026-08-21** | active, out of stock | 3.97" `SSD1677`, 480 × 800, **4-level** grey, FT6336G touch, **frontlight** | ESP32-S3R8, 1150 mAh, NFC + LoRa, BMI270, **M5PM1** PMIC, **M5IOE1** expander, RX8130CE RTC, PDM mic |
-| **PaperMono-Lite** | `C153-LITE` | USD 55.00 | **2026-08-21** | active, out of stock | same panel, touch and frontlight | Identical **minus NFC and LoRa**. 72.4 g against 74.7 g |
-
-> **`published_at` is a proxy, and here is why it is a good one for this vendor.** Shopify does
-> not expose an availability date, only when the storefront record went public. For PaperMono
-> that timestamp agrees to within an hour with the vendor blog post, the vendor YouTube upload
-> and the first independent buyer report — three unrelated sources. That validation was done for
-> the one product where it was possible; for the 2020–2024 rows the proxy is **unvalidated** and
-> should be read as "the store record went live then", not "the product shipped then".
-
-> **The original M5Paper's display controller is *not* established here.** A commonly repeated
-> attribution is `IT8951`. It appears on **no M5Stack page retrieved in this pass**, and
-> `docs.m5stack.com/en/core/Paper` is a JavaScript shell that returned no content. Recorded as
-> **unverified** rather than repeated. What M5Stack's current documentation does state is that
-> the *PaperS3's* panel is `EPD_ED047TC1`.
-
-### What the family table means in practice
-
-Two of the four generations of the 4.7-inch line are **`[EOL]`** at the snapshot date, including
-the PaperS3 — the newest of them, published only twenty months earlier. The line M5Stack is
-actually selling into today is **not** the 4.7-inch one: it is PaperColor at 4 inches and
-PaperMono at 3.97 inches, both smaller, both at lower resolution than the 960 × 540 boards they
-replace in the catalogue.
-
-That is the family-level observation worth carrying away: **M5Stack's e-paper line got smaller
-and cheaper, not bigger and sharper.** Whether that is component sourcing, cost, or a read of
-the market is not established by anything in evidence.
-
-## 4. PaperMono is not a successor to the PaperS3
-
-Several launch articles described it as one, and the naming invites it. **The vendor's own
-specification tables contradict it on every measurable display and power axis.**
-
-| | **M5PaperS3** (`C139`) | **PaperMono** (`C153`) | Which is better for that axis |
-|---|---|---|---|
-| Store price 2026-09-01 | USD 59.00 | USD 65.00 | **PaperS3**, by $6 |
-| Store status 2026-09-01 | **`[EOL]`** — not purchasable new | active but **out of stock** | Neither is purchasable |
-| Panel | 4.7" `EPD_ED047TC1`, **parallel** interface | 3.97" `SSD1677`, **SPI** | — |
-| Resolution | **960 × 540 = 518 400 px** | 480 × 800 = **384 000 px** | **PaperS3 — ~35 % more pixels** |
-| Greyscale | **16 levels** | **4 levels** | **PaperS3** |
-| Touch | GT911, **two-point + gestures** | FT6336G, single point, active area clipped to X 5–475 / Y 5–795 | **PaperS3** |
-| Frontlight | **none** | **integrated** | **PaperMono** |
-| Battery | **1800 mAh** | **1150 mAh** | **PaperS3 — ~57 % more capacity** |
-| LoRa / NFC | none | **SX1262 868–923 MHz + ST25R3916** | **PaperMono** |
-| Microphone | none | **PDM mic** | **PaperMono** |
-| User buttons | 1 (power / reset / download) | **2 user + 1 power** | **PaperMono** |
-| Expansion port | **HC1.25-4PLT** (3V3 + GND + 2 × GPIO) | **none at all** | **PaperS3** |
-| Power management | conventional | **M5PM1 five-state hardware state machine** | **PaperMono** |
-| I/O expander | none | **M5IOE1** | depends — capability *and* a mandatory dependency |
-| Published power figures | **yes** — 9.28 µA / 949.58 µA / 154.02 mA at DC 4.2 V | **none published** | **PaperS3** ([`performance.md`](performance.md)) |
-| Size / weight | 121.5 × 67.7 × 7.7 mm, 89.0 g | 101.0 × 62.0 × 8.0 mm, 74.7 g | **PaperMono** for pocketability |
-
-**This is a trade, not an upgrade, and the direction of the trade is clear.** If the workload is
-*rendering* — a reader, a dashboard, a calendar, anything where pixels and grey levels are the
-product — the PaperS3 is the better display, has the better battery, and is cheaper. The
-PaperMono wins where you need the **radios**, the **frontlight**, the **power architecture**, or
-the **size**. Nothing about the newer product supersedes the older one on the axes the older one
-was good at.
-
-Two qualifications that matter as much as the table:
-
-- **The PaperS3 is EOL.** So this comparison mostly tells you what the line lost, not what to
-  buy. Neither device could be purchased new from M5Stack on 2026-09-01.
-- **They are not software-compatible either.** Different panel interface (parallel vs SPI),
-  different display controller, different touch controller (GT911 vs FT6336G), different RTC
-  (BM8563 vs RX8130CE), and two auxiliary microcontrollers the older board does not have. The
-  concrete demonstration is `MingRZou/PaperMono-Launcher` (S91) — an explicit **port** of
-  `bmorcelli/Launcher` from the PaperS3. Somebody had to do work; that is what "not a successor"
-  means in practice.
-
-The community reached the same conclusion independently and correctly: u/poulpy123 ("More
-expensive, smaller screen and lower resolution that the previous version"), and u/Tsixom, whose
-spec comparison on r/M5Stack was **checked line by line against `docs.m5stack.com` and is
-accurate on every point**. Recorded in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md#claims-examined-and-rejected) as a rejected
-claim, and in [`community.md`](community.md) as one of the few community contributions that
-survives checking.
-
-## 5. What is shared across the family, and what is not
-
-| Element | Shared with | Not shared |
-|---|---|---|
-| **ESP32-S3R8** SoC, 16 MB flash, 8 MB octal PSRAM | PaperS3, PaperColor, PaperMono, PaperMono-Lite | The original M5Paper line is plain **ESP32** |
-| **BMI270** IMU | PaperS3, PaperMono | PaperColor (no IMU in its spec table) |
-| **RX8130CE** RTC | **PaperColor and PaperMono** | PaperS3 uses **BM8563** |
-| Product-line **name** | all of them | — |
-| Panel, display controller, touch controller | **nothing** — every generation differs | — |
-| **M5PM1** power manager, **M5IOE1** expander | PaperMono and PaperMono-Lite only, in this family | Neither appears on PaperS3 or PaperColor. (The M5PM1 does appear elsewhere in M5Stack's catalogue — the site-wide I²C table lists `M5PM1 (0x6e)` for **StickS3 (K150)**) |
-| Frontlight | PaperMono and PaperMono-Lite only | — |
-| Firmware | **nothing** | Ports are real work (§4) |
-
-The M5PM1 detail is worth pausing on. Its library's `LICENSE` is dated **2025** while both demo
-repositories and the M5IOE1 library are dated 2026, and the site-wide I²C address table
-independently places an M5PM1 on the StickS3. Together those say the power manager is a
-**reusable M5Stack building block that predates this product**, not something designed for it.
-`inferred`. That matters for a buyer: it is more likely to be maintained across products than a
-one-off, and its documentation quirks
-([C12](gaps-and-conflicts.md#c12--m5pm1-manual-internal-inconsistencies)) are quirks you will
-meet again on other M5Stack boards.
-
-## 6. PaperMono and PaperMono-Lite
-
-The full variant record is [`../papermono-lite/README.md`](../papermono-lite/README.md). The
-family-level facts:
-
-| | PaperMono `C153` | PaperMono-Lite `C153-LITE` |
-|---|---|---|
-| Price | USD 65.00 | USD 55.00 |
-| Case | grey | white |
-| NFC (ST25R3916) | yes | **no** |
-| LoRa (Stamp LoRa-1262) | yes | **no** |
-| Weight | 74.7 g | 72.4 g |
-| Schematic asset | `PaperMono_SCH_V0.6.2_20260522.pdf`, **6 sheets** | `PaperMono-Lite_PRJ_V0.6.2_20260522.pdf`, **4 sheets**, `PRJ` not `SCH` — **not retrieved** (S16) |
-| Firmware | **the same image**, `PaperMono / PaperMono-Lite UserDemo` | same |
-| Internal firmware name | **`Pro`** | **`Lite`** |
-| Storefront record created | 2026-08-18T14:29:31+08:00 | 2026-08-18T14:26:42+08:00 |
-| Inventory counter 2026-09-01 | **−129** | **0** |
-
-**The USD 10 difference buys exactly the NFC and LoRa hardware.** Everything else — panel,
-touch, frontlight, battery, SoC, both auxiliary microcontrollers, the power architecture — is
-identical, and one firmware image serves both, detecting the variant at runtime by probing for
-the NFC chip ([`factory-firmware.md` §5](factory-firmware.md#5-what-the-device-does-on-power-up)).
-
-Two details that only appear when you look at both records together:
-
-- **The vendor's own systems disagree about the SKU string**: `C153-Lite` on
-  `docs.m5stack.com`, `C153-LITE` in the Shopify record.
-- **The firmware calls the full model "Pro"** although no M5Stack marketing material does.
-  If you see `Pro` in a log, that is a C153.
-
-**One widely propagated error to know about.** Liliputing (2026-08-28) described the device as
-"a **$55** … with … NFC, LoRa". $55 is the **Lite**, which has neither. The NFC/LoRa model is
-$65. Recorded in [`gaps-and-conflicts.md`](gaps-and-conflicts.md#claims-examined-and-rejected)
-and [`community.md`](community.md).
-
-## 7. Positioning, audience and product culture
-
-**How M5Stack positions it.** The product page's own applications list is: *E-Reader, E-Paper
-Signage, Access Control Terminal, Identity Authentication Device, Intelligent Transportation
-Terminal* (S01). The blog announcement calls it *"A Compact E-Ink Development Terminal for
-Connected Projects"* (S50). Read those together and the intent is clear: the **radios and the
-power architecture** are the product, and the display is a low-duty output. Two of the five
-listed applications are NFC applications.
-
-**How the market read it.** As an e-reader. The 162-point HN thread is dominated by comparisons
-to sealed consumer readers (the XTEINK X4 Pro repeatedly), the single hands-on video frames it
-as a "pocket gadget", and the first two third-party projects to appear were an **e-reader
-firmware port** and a **reader UI**. The gap between the vendor's framing and the audience's is
-the most interesting cultural fact about this launch, and it is visible in the artifacts rather
-than asserted: a third party had CrossPoint reader firmware published **one day after launch**,
-before any written coverage of the hardware existed.
-
-**M5Stack's disclosure culture, stated fairly.** This board is unusually well documented for its
-class in some respects and unusually badly in others, and both are worth recording because they
-are the vendor's pattern, not this product's accident:
-
-| Good | Bad |
-|---|---|
-| Complete published schematic (6 sheets) | **No C153 directory in `m5stack/M5_Hardware`** — the SKU sequence stops at C152, so there is no machine-readable netlist (S45, a verified negative) |
-| Vendor-authored datasheets for **both** custom chips (M5PM1, M5IOE1) | Both manuals are internally inconsistent; the M5IOE1's own manual states an I²C address range the board does not use ([C4](gaps-and-conflicts.md#c4--the-m5ioe1s-i²c-address-is-not-in-its-own-manual)) |
-| Firmware source published, MIT | The shipped image is `-dirty` and not reproducible from it |
-| The vendor **publishes a warning against its own graphics library's waveforms** and points you at the panel maker's example instead | …which means the recommended path bypasses the vendor's own library |
-| Pin tables on the product page are accurate everywhere they overlap the schematic ([R6](gaps-and-conflicts.md#r6--the-vendor-product-pages-pin-tables-are-accurate--confirmed-correct)) | They omit USB, UART0 and two expander pins; and the `PYG<n>` notation is ambiguous between two chips ([`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md)) |
-| Published power-consumption figures for **PaperS3** and **PaperColor** | **None for PaperMono** — the one board whose headline feature is its power architecture ([`performance.md`](performance.md)) |
-| — | **No certification identifier published** for this board: `/en/certification` returns HTTP 200 with zero matches for `PaperMono` and `C153` (S11, a verified negative) |
-
-The last two rows are the ones a buyer should weigh. A product sold on low power that publishes
-no power figure, and a radio product that publishes no regulatory identifier, are both gaps the
-vendor has filled for adjacent products in its own catalogue.
-
-**CNX-Software's two independent contributions** are the only added value in any written piece,
-and both are small: an observation that **ghosting is visible in the vendor's own demo video**
-(an observation of a video, not of hardware), and that the product is **not listed on
-AliExpress** (independently reproduced here on 2026-09-01). CNX also disagrees with the vendor
-on dimensions — 101 × 61 × 7.95 mm against the docs' 62.0 × 101.0 × 8.0 mm.
-
-## 8. What is not established
-
-- **No announcement or preorder milestone before 2026-08-17** was found. The 2026-05-07
-  repository creation is a trace, not an announcement.
-- **No discontinuation or lifecycle statement** exists for PaperMono; it is eleven days old.
-- **The restock date is contested and unresolved** — vendor "two or three months" (primary,
-  2026-08-22) against CNX-Software's "next year" (second-hand, unlinked)
-  ([C7](gaps-and-conflicts.md#c7--restock-timing)).
-- **The original M5Paper's display controller** is unverified (§3).
-- **The Lite's schematic was not retrieved** (S16) — it is `PRJ`-named with 4 sheets against the
-  full model's 6, and is the highest-value untaken lead for the family record.
-- **`community.m5stack.com` could not be searched** (HTTP 401), so vendor-forum history is a
-  blank in this timeline rather than an absence.
-- **No hardware revision other than V0.6.2 is in evidence**, and no regional variants were
-  found.
-
-## Related
-
-- [`README.md`](README.md) — the summary timeline this page evidences
-- [`../papermono-lite/README.md`](../papermono-lite/README.md) — the variant record
-- [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) — competitors outside the family
-- [`market-and-pricing.md`](market-and-pricing.md) — dated pricing and availability
-- [`community.md`](community.md) — coverage, evidence types, and the claims that failed checking
-- [`performance.md`](performance.md) — including the published-figures asymmetry within the family
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — every conflict cited here
-- [`sources.md`](sources.md) — S01, S04, S11, S13–S17, S33–S42, S45, S48–S50, S68–S81, S89–S93
diff --git a/devices/m5stack/papermono/projects-and-community.md b/devices/m5stack/papermono/projects-and-community.md
deleted file mode 100644
index 6bbe546..0000000
--- a/devices/m5stack/papermono/projects-and-community.md
+++ /dev/null
@@ -1,475 +0,0 @@
-# PaperMono — third-party firmware, software projects and community venues
-
-> **Retrieval snapshot 2026-09-02 (UTC).** Every row was re-retrieved on this date unless a
-> different date is given on the row. This pass supersedes and in several places **corrects**
-> the 2026-09-01 community sweep recorded in the device
-> [`README.md`](README.md#community-editorial-and-project-coverage); the corrections are
-> collected in [§8](#8-what-this-pass-changes-in-the-existing-record).
->
-> **No PaperMono hardware was available to this pass.** Nothing below was built, flashed or
-> executed. Every project was assessed by **static inspection of published source, published
-> binaries, repository metadata and author statements**. Where a project is described as
-> "runs on hardware", that is *the author's* evidence, classified below — never this record's.
->
-> Companion files: [`examples/catalog.json`](examples/catalog.json) (machine-readable, one
-> entry per example including the rejected ones) · [`examples/search-log.md`](examples/search-log.md)
-> (every query and disposition) · [`examples/best.md`](examples/best.md) (the selected portfolio).
-
----
-
-## 1. Headline findings
-
-1. **The CrossPoint reader is open source, and its PaperMono support is upstream.**
-   The binary held at
-   [`artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin`](artifacts/firmware/)
-   traces, by exact commit hash, to **[`MarsTechHAN/crosspoint-reader-mono`](https://github.com/MarsTechHAN/crosspoint-reader-mono)
-   at `87a191fcea17a9658686083187765c600ad03866`** — a public MIT fork of
-   **[`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader)**
-   (MIT, 7,487 stars, homepage <https://crosspointreader.com>). Full derivation in
-   [§3](#3-crosspoint-the-source-repository-question-answered).
-2. **The ecosystem is roughly five times larger than the previous pass recorded.** That pass
-   found "four third-party GitHub repositories and one YouTube video". This pass finds
-   **9 projects with firsthand PaperMono hardware evidence**, **13 upstream frameworks/
-   libraries that ship a PaperMono target**, and **2 official vendor demos**, among
-   **129 distinct repositories surfaced** by GitHub search and **48 inspected in detail**.
-3. **Support landed *before* the product did.** `crosspoint-reader` merged PaperMono support
-   into `develop` on **2026-08-16**, five days before launch; M5Stack merged PaperMono
-   changes into M5Unified from **2026-07-17** and into M5GFX from **2026-07-14**; the
-   `m5stack_papermono` Arduino board id shipped in M5Stack Arduino core **3.3.9**. A
-   pre-retail hardware-beta channel demonstrably existed
-   ([§4.4](#44-the-hardware-beta-channel)).
-4. **The independent written-coverage picture is unchanged and still bleak.** Zero written
-   reviews, one hands-on video (Volos Projects, vendor affiliate link, self-described first
-   look), all written articles traceable to one vendor blog post. Re-verified 2026-09-02.
-5. **The first independent end-user photographs of third-party firmware on retail hardware
-   appeared on 2026-09-01/02**, on r/xteinkereader, not on any venue the previous pass
-   searched ([§6.3](#63-reddit)).
-6. **M5GFX's board-autodetect source names an unannounced "PaperMono Pro".** No such SKU
-   exists on the M5Stack store, docs site or M5Burner device list. See
-   [§8](#8-what-this-pass-changes-in-the-existing-record).
-
----
-
-## 2. How projects are classified here
-
-The method requires that demonstrated work is not mixed with claims. Six classes are used,
-and every project in [§4](#4-the-project-population) carries exactly one.
-
-| Class | Meaning | Bar |
-|---|---|---|
-| **D — Demonstrated** | The author presents firsthand evidence of the code running on a PaperMono or PaperMono-Lite | A device photograph, a measured number that cannot come from a datasheet, a factory-flash dump, an explicit "verified on hardware" statement backed by matching commit history, or a published flashable binary plus a bug report containing device-specific observations |
-| **S — Shipped target** | An upstream framework, library or firmware that carries a first-class PaperMono build target, merged and released, but where *this record* found no firsthand hardware evidence from the maintainers themselves | A merged board profile, build environment, board id, or driver on a default branch or in a release |
-| **V — Vendor** | Published by M5Stack | — |
-| **P — Proposal / untested** | PaperMono support written but explicitly not validated, or validated only by compilation | Author's own statement, or absence of any hardware claim in a compile-only artefact |
-| **C — Copy** | A mirror, vendored tree or re-publication of someone else's PaperMono code, adding nothing | — |
-| **R — Rejected** | Surfaced by search, not a PaperMono project | See [§5](#5-rejected-false-positives-and-adjacent-work) |
-
-Evidence-type letters used inside rows follow the existing record's key:
-`M` firsthand measurement · `O` firsthand ownership · `P` demonstrable project ·
-`Op` opinion · `H` hearsay · `V` vendor-published.
-
-> **A standing caveat on all of class D.** "Demonstrated" means *the author demonstrated it*.
-> None of it was reproduced here. Where an author's claim is unusually specific (a measured
-> refresh time, a register value) that raises confidence that hardware was present; it does
-> not make the number correct.
-
----
-
-## 3. CrossPoint: the source-repository question, answered
-
-The previous pass recorded CrossPoint as *"roadmap, not shipped support"*. That is wrong, and
-the correction is fully evidenced.
-
-### 3.1 Provenance chain for the held binary
-
-| Link | Evidence | Retrieved |
-|---|---|---|
-| The binary's build id is `paper-mono-v2-15-g87a191f`, app name `crosspoint-reader-mono` | strings extracted in the prior pass, `scratch/m5stack-papermono/docs/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.strings.txt` | 2026-09-01 |
-| The M5Burner listing for it declares `sourceUrl` = `https://github.com/MarsTechHAN/crosspoint-reader-mono` | `https://burner.m5stack.com/api/v1/firmwares/2091144466157694978` | 2026-09-02 |
-| That repository's `develop` head is **`87a191fcea17a9658686083187765c600ad03866`** — the `g87a191f` in the build id | `git ls-remote https://github.com/MarsTechHAN/crosspoint-reader-mono.git` | 2026-09-02 |
-| It carries an annotated tag **`paper-mono-v2`** (tag object `296eaff965382e4bd2f982fa83f1370c7a8d9ff3`, commit `efbfa3a08605af7bbf77b8e1d19e9ccab5bc43e7`), making `git describe` = `paper-mono-v2-15-g87a191f` exactly | same `ls-remote` | 2026-09-02 |
-| Its `platformio.ini` defines `[env:paper_mono]` with `-DCROSSPOINT_VERSION="1.5.0-paper-mono"` — matching the binary strings `CrossPoint version: 1.5.0-paper-mono` and `CrossPoint-ESP32-1.5.0-paper-mono` | `https://raw.githubusercontent.com/MarsTechHAN/crosspoint-reader-mono/develop/platformio.ini` | 2026-09-02 |
-| It is a **fork of `crosspoint-reader/crosspoint-reader`** (GitHub `parent` field), created 2026-07-29, last pushed 2026-08-12 | GitHub API `/repos/MarsTechHAN/crosspoint-reader-mono` | 2026-09-02 |
-| Its submodule `freeink-sdk` is repointed to **`MarsTechHAN/freeink-sdk-mono`** at `f5518c7a39d3956dbc9d43be508bf9edae8f222d`; HEAD commit `87a191f`'s message is *"chore: bump freeink-sdk to the 5% Li-ion SoC curve — Picks up f5518c7…"* | GitHub contents API + commit API | 2026-09-02 |
-
-**Answer.** CrossPoint is **open source, MIT-licensed**. Homepage <https://crosspointreader.com>.
-Canonical repository <https://github.com/crosspoint-reader/crosspoint-reader>. The specific
-M5Burner build held in this record was produced from the public fork
-<https://github.com/MarsTechHAN/crosspoint-reader-mono> at commit `87a191f`, against the
-public SDK fork <https://github.com/MarsTechHAN/freeink-sdk-mono> at `f5518c7`.
-
-### 3.2 Upstream also ships PaperMono
-
-Upstream `crosspoint-reader/crosspoint-reader` (`develop`, head
-`e6139861a2a8c634aa18c333b7e214ee51a9965c`, 2026-09-01) carries:
-
-- `[env:papermono]`, `[env:papermono-gh_release]`, `[env:papermono-gh_release_rc]` in
-  `platformio.ini`, on `board = esp32-s3-devkitc1-n16r8`, `memory_type = dio_opi`, with
-  `-DFREEINK_DEVICE_PAPERMONO=1`, `-DFREEINK_CAP_USB_MSC=1`, `-DBOARD_HAS_PSRAM`,
-  `-DUSB_PRODUCT="CrossPoint_Paper_Mono"`;
-- `src/network/FirmwareBoardTag.cpp`, which derives the OTA compatibility tag
-  `CROSSPOINT-BOARD-V1:papermono;` from `FREEINK_DEVICE_PAPERMONO`;
-- `ROADMAP.md:40`, whose "pluggable per-device SDK layers" item is now struck through and
-  marked **Done**, listing PaperMono among the shipped ESP32-S3 targets.
-
-The enabling change is **PR #2983 "feat: Add support for x4pro & papermono devices"** by
-[@itsthisjustin](https://github.com/itsthisjustin), **merged into `develop` 2026-08-16
-01:22 UTC** (merge commit `bbca4886c97a251480ea908aad00ea16dc3d8b75`), from branch
-`feat-x4-papermono-support`. An earlier attempt, PR #2675 (2026-07-22), was closed unmerged.
-
-> **A stale third-party claim.** `jpirnay/witchhunt-reader`'s
-> [`docs/x4pro_support.md`](https://github.com/jpirnay/witchhunt-reader/blob/master/docs/x4pro_support.md)
-> states that PR #2983 is *"still open — it is on neither `develop` nor `master`"*. That was
-> true when written; it is **false as of 2026-09-02**. Do not propagate it.
-
-### 3.3 The CrossPoint constellation
-
-| Repository | Role | Licence | Head (2026-09-02) | PaperMono? |
-|---|---|---|---|---|
-| [`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader) | Upstream reader firmware | MIT | `e6139861a2a8c634aa18c333b7e214ee51a9965c` | **Yes** — 3 build envs |
-| [`MarsTechHAN/crosspoint-reader-mono`](https://github.com/MarsTechHAN/crosspoint-reader-mono) | Fork that produced the held M5Burner binary | MIT | `87a191fcea17a9658686083187765c600ad03866` | **Yes** — `[env:paper_mono]`, `[env:paper_mono_lab]` |
-| [`Free-Ink/freeink-sdk`](https://github.com/Free-Ink/freeink-sdk) | The HAL CrossPoint builds on | MIT | `fad70f28a982c978737410e535a4f7276ce28c19` | **Yes** — `PaperMonoBoard.h`, `PaperMonoDriver.cpp` |
-| [`MarsTechHAN/freeink-sdk-mono`](https://github.com/MarsTechHAN/freeink-sdk-mono) | SDK fork pinned by the above | MIT | `f5518c7a39d3956dbc9d43be508bf9edae8f222d` | **Yes** |
-| [`crosspoint-reader/crosspoint-simulator`](https://github.com/crosspoint-reader/crosspoint-simulator) | Desktop simulator of the firmware | MIT | `6aa3b5476f783953bff4ae8aa0b84d9a64dd07ef` | **Yes** — `simulator_papermono` / `-DSIMULATOR_DEVICE_PAPERMONO` |
-| [`crosspoint-reader/crosspoint-tools`](https://github.com/crosspoint-reader/crosspoint-tools) | Web installer / tooling | MIT | `a3f0abf6a06fe0abe9309b3e0ff3c25aea11579a` | Mentions papermono in the worker |
-| [`crosspoint-reader/escape-hatch`](https://github.com/crosspoint-reader/escape-hatch) | 400 KB SD-card recovery flasher | **none** | `90841adf6304354d1393936d1ca203294b76c09b` | Carries `FirmwareBoardTag.cpp`; targets X3/X4 |
-| [`0x1abin/crossmux`](https://github.com/0x1abin/crossmux) | Fork with a **PaperMono Hardware Beta** channel | MIT | `85f7696b3ee51e0a067cdc012cfabc2783616f3a` | **Yes** — 4 papermono envs |
-| [`Belphemur/crosspoint-x-reader`](https://github.com/Belphemur/crosspoint-x-reader) | Fork, X4-Pro-focused | MIT | `4547187dc29cca731352147a63877c24184fe1fc` | Inherits 3 papermono envs |
-| [`sfoulad/midad-by-foulad`](https://github.com/sfoulad/midad-by-foulad) | Arabic-focused derivative | MIT | `ef3b455c3aa9ea06204cabbae717b05bc28c1803` | Inherits 3 papermono envs |
-
-Forks that do **not** carry a PaperMono target — and so are *not* PaperMono projects despite
-appearing in searches — are listed in [§5](#5-rejected-false-positives-and-adjacent-work):
-`eszter007/matcha-reader`, `jpirnay/witchhunt-reader`, `aBER0724/crosspoint-reader-cjk`,
-`juicecultus/crosspoint-reader-papers3`, `dito94/CrossDiTo`.
-
----
-
-## 4. The project population
-
-### 4.1 Class D — demonstrated on PaperMono hardware (9)
-
-| Project | Author | Licence | Framework | Head commit | What the hardware evidence is | What it demonstrates about the device |
-|---|---|---|---|---|---|---|
-| [`MagicCube/free-ink-on-paper-mono`](https://github.com/MagicCube/free-ink-on-paper-mono) | Henry Li ([@henry19840301](https://x.com/henry19840301)) | **none published** | PlatformIO / Arduino / FreeInk SDK | `34cc879427d5fc0b35f6af5084d4e7a003457665` (2026-08-27) | `M+O+P`. Author posted dated purchase photographs 2026-08-21 04:09 UTC; his SDK patch was **merged upstream** as [freeink-sdk PR #58](https://github.com/Free-Ink/freeink-sdk/pull/58), 2026-08-26 | RX8130 time, M5PM1 battery/USB/charge telemetry, touch + buttons, light/dark whole-screen inversion, frontlight held at 127/255, async refresh with periodic full cleanup, **disabling M5PM1's default single-click reset**, rectangular (window) partial refresh |
-| [`MingRZou/PaperMono-Launcher`](https://github.com/MingRZou/PaperMono-Launcher) | MingRZou | MIT | PlatformIO / Arduino / M5Unified 0.2.21 | `daf3edcee4f8669e2adf7a58bc174d62e4e40f42` (2026-08-30), release `v0.1.0` | `P+O+M`. Repo carries `docs/images/papermono-launcher-real-hardware.jpg`; **published on M5Burner** as firmware `2094259851119865857`, binary `PaperMono-Launcher-v0.1.0.bin`; author's [crossmux issue #218](https://github.com/0x1abin/crossmux/issues/218) reports firsthand device behaviour (enters S3 download mode, detected as 16 MB flash / 8 MB PSRAM); his [Launcher PR #416](https://github.com/bmorcelli/Launcher/pull/416) was **merged upstream** 2026-08-29 | Launcher UI, touch/buttons/SD/frontlight, SSD1677 refresh policy with periodic full cleanup, protected payload partition install + boot + return-to-launcher, F1-v1 FullFlash wrapper handling |
-| [`hectorzin/M5PaperMono-HomeAssistant-ESPHome`](https://github.com/hectorzin/M5PaperMono-HomeAssistant-ESPHome) | hectorzin | **none published** | ESPHome ≥ 2026.6.x (ESP-IDF) | `c144086af7291f6340422361534e9374fa4d2bdd` (2026-09-01) | `M+P`. README states **measured** refresh times (PARTIAL ≈ 0.9 s, FULL ≈ 4.3 s) and a specific interrupt route; those are not published vendor figures | **The only measured refresh timings found anywhere.** Also: BMI270 INT1 → M5PM1 GPIO4 → ESP32 GPIO1 motion path; frontlight at 30 % on activity with timeout; ESP32 light sleep with Wi-Fi off; M5PM1 SHUTDOWN for quiet hours; M5IOE1 pin numbering as ESPHome sees it (EPD power 2, EPD reset 4, touch reset 5, touch power 12) at I²C `0x4F` |
-| [`GOROman/learning-paper-mono`](https://github.com/GOROman/learning-paper-mono) | GOROman | **none published** | PlatformIO / Arduino / M5GFX + M5Unified + RadioLib | `21abc4ec84f17b3966bc7c936f78a1e4facc6372` (2026-09-02) | `M+O+P`. Steps 1–4 marked done with 「実機表示確認済み」 (*verified displaying on the actual device*); a **16 MB factory flash dump** is described as taken and kept out of git; a two-device LoRa link to a Cardputer ADV is parameterised | Step-by-step per-feature bring-up: display, touch, buzzer, **LoRa TX/RX**, frontlight 0–10 steps, window partial refresh. Records the LoRa pin map (SPI3 SCK 39 / MISO 40 / MOSI 38, NSS 41, DIO1 5, BUSY 21; power via M5PM1 GPIO2; RST/ANT-SW via M5IOE1 pins 10/2) and the demo radio settings (868 MHz, BW 62.5 k, SF12, CR8, sync 0x34, 22 dBm, TCXO 3.0 V) |
-| [`tinyrange/renvo`](https://github.com/tinyrange/renvo) — [issue #444](https://github.com/tinyrange/renvo/issues/444) + [PR #445](https://github.com/tinyrange/renvo/pull/445) | Vbitz (Joshua Scarsbrook) | Apache-2.0 | Renvo (Rust/`.rtg`), `esp32s3/xtensa_lx7` backend | repo head `1215bdd5d69824b924d06572ad4476460dbff044`; **PR #445 open, unmerged**, 56 files, +7,190 lines | `M+P`. A structured bring-up plan whose checkboxes are ticked with hardware-specific outcomes ("hardware-confirm enable and shutdown-off behavior", "hardware-test a two-pixel touch-trails example"), plus explicit factory-flash backup and JEDEC RDID capacity detection | The most systematic independent bring-up: board registration, M5PM1 + M5IOE1 drivers with transaction tests, bounded 100 kHz software I²C, SSD1677 protocol driver over bounded 20 MHz SPI2 mode 0, OTP full/partial/4-gray refresh with a mandatory monochrome baseline and automatic full-refresh recovery after ten partials, FT6336G driver with active-area normalisation, serial and touch **hardware oracles** |
-| [`MarsTechHAN/crosspoint-reader-mono`](https://github.com/MarsTechHAN/crosspoint-reader-mono) + [`freeink-sdk-mono`](https://github.com/MarsTechHAN/freeink-sdk-mono) | Han (MarsTechHAN) | MIT | PlatformIO / Arduino (pioarduino 55.03.37) | `87a191fcea17a9658686083187765c600ad03866` / `f5518c7a39d3956dbc9d43be508bf9edae8f222d` | `P`. A **shipped, downloadable binary** on M5Burner (24→27 downloads), plus a `[env:paper_mono_lab]` bare-metal SSD1677 characterisation harness, a serial waveform lab (`CMD:WAVE`), a sleep lab (`CMD:WRIST`) and touch-probe tracing — instrumentation that is pointless without a device | A complete EPUB reader on the device: CJK font pipeline (`.cpfont`, PSRAM glyph arena raised 128→512 slots for Han pages), WebDAV/OPDS/KOSync networking, USB MSC file transfer, native 1-bit SDMMC via SdFat block-device interface |
-| [`EggUncle/PaperMonoCalendar`](https://github.com/EggUncle/PaperMonoCalendar) | EggUncle | **none published** | Arduino CLI 1.4.1 / M5GFX | `53385729b35249c4fe4f8a3f2d7ded6ad2de5696` (2026-08-31) | `P`, **partial**. README states v2 activity sync and `HUB / SYNCED` are 「已在 PaperMono 上确认」 (*confirmed on PaperMono*) and the date format was user-confirmed; v3 RTC calibration is explicitly **compiled and flashed but not yet accepted on device** | Landscape 800×480 calendar, BLE activity tiles, RTC sync, four-level black/white dither used as pseudo-grey, PSRAM canvas then push, minute-scoped partial updates with a "every 10th update use quality" counter. **Pins an exact toolchain**: M5Stack ESP32 core 3.3.9, M5Unified 0.2.21, M5GFX 0.2.28, M5PM1 1.0.7, M5IOE1 1.0.9 |
-| [`LuoIsHere/SeeSeeBook`](https://github.com/LuoIsHere/SeeSeeBook) | LuoIsHere | MIT | ESP-IDF (devcontainer), M5GFX `M5Canvas` for rasterising only | `64bc8332628f00d025a6f68e72fe951d9db9f44f` (2026-09-01) | `P`, **implied not asserted**. No photograph and no explicit claim, but the commit log is daily iteration on device-shaped problems — *"harden PaperMono I2C recovery"*, *"serialize internal i2c and isolate ip2315 sessions"*, *"fix some display bugs"* — which is not how a paper design evolves. Classified D with that caveat stated | A cleanly layered device port: `m5_hal/paper_mono/` (display, touch, RTC, battery, storage, internal I²C) built on its **own SSD1677 OTP driver ported from `m5stack/M5PaperMono-OTP-Demo` at the pinned commit `c7c02554f89fd06f80d988b805b2a59050c78a46`**, deliberately bypassing M5GFX's `Panel_SSD1677_4Gray` waveforms. Scene-aware regional refresh policy; async SD browser |
-| [`0x1abin/crossmux`](https://github.com/0x1abin/crossmux) | 0x1abin | MIT | PlatformIO / Arduino | `85f7696b3ee51e0a067cdc012cfabc2783616f3a` (2026-09-02) | `P`, **channel demonstrated, validation unanswered**. Published a `hardware-beta-papermono` / `papermono_cn` web-installer channel **before retail units were widely out**; the direct question "has this been tested on retail PaperMono hardware?" ([issue #218](https://github.com/0x1abin/crossmux/issues/218), 2026-08-24) is **still open and unanswered** on 2026-09-02 | That a pre-retail PaperMono firmware distribution channel existed. Also the source of the SSD1683→SSD1677 documentation correction ([PR #221](https://github.com/0x1abin/crossmux/pull/221), merged 2026-08-24) |
-
-### 4.2 Class S — upstream targets that ship PaperMono support (13)
-
-These are not "PaperMono projects"; they are the substrate the projects above stand on. Each
-carries a merged, released PaperMono target.
-
-| Project | Licence | Head (2026-09-02) | The PaperMono artefact | Note |
-|---|---|---|---|---|
-| [`Free-Ink/freeink-sdk`](https://github.com/Free-Ink/freeink-sdk) | MIT | `fad70f28a982c978737410e535a4f7276ce28c19` | `libs/hardware/BoardConfig/include/PaperMonoBoard.h`, `libs/display/FreeInkDisplay/src/driver/PaperMonoDriver.{h,cpp}`, `M5Pm1.h`, `M5Ioe1.h` | The single richest third-party description of the board's power topology. Sequences the PMIC and expander itself so consumer firmware never touches them; disables the PMIC single-click reset while **preserving the hardware long-hold download escape**. Describes the frontlight as PMIC 12-bit PWM driving an **AW9967** boost LED driver fed from the EPD rail — so the light only runs while EPD power is on |
-| [`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader) | MIT | `e6139861a2a8c634aa18c333b7e214ee51a9965c` | 3 `papermono` envs; `FirmwareBoardTag.cpp` | See [§3.2](#32-upstream-also-ships-papermono) |
-| [`crosspoint-reader/crosspoint-simulator`](https://github.com/crosspoint-reader/crosspoint-simulator) | MIT | `6aa3b5476f783953bff4ae8aa0b84d9a64dd07ef` | `simulator_papermono` target, `-DSIMULATOR_DEVICE_PAPERMONO` | Added by [PR #34](https://github.com/crosspoint-reader/crosspoint-simulator/pull/34) (@lpla), merged **2026-08-20 — the day before launch**. Exposes FT6336-compatible touch/swipe, RTC and single-channel frontlight state. **The only way to exercise PaperMono UI code without hardware** |
-| [`m5stack/M5Unified`](https://github.com/m5stack/M5Unified) | MIT | `8530f5377d782e4a25a6c482de2e71c3f75ca8eb`, release **0.2.21** (2026-08-26) | `board_M5PaperMono`, `LED_PaperMono_Class`, `M5IOE1_Class`, PaperMono paths in `Power_Class` / `RTC_Class` | PaperMono PRs by @TinyuZhao merged **2026-07-17** (#279), **2026-07-23** (#286, touch wake-up), **2026-07-27** (#289, SD card power) |
-| [`m5stack/M5GFX`](https://github.com/m5stack/M5GFX) | MIT | `d91077b9a607b59404e4e4a49f775c792bfae382`, release **0.2.28** (2026-08-25) | `board_M5PaperMono` in `lgfx/boards.hpp`; autodetect + `Light_M5PaperMono` in `M5GFX.cpp` | SSD1677 LUT tuning PRs by @zhenquan-yao merged **2026-07-14** (#223, fastest mode) and **2026-08-27** (#272, text/quality modes). Aborts with `"M5PaperMono need OPI-PSRAM enabled"` if octal PSRAM is off — see [`features/epaper-display.md`](features/epaper-display.md) |
-| [`m5stack/uiflow-micropython`](https://github.com/m5stack/uiflow-micropython) | MIT | `587e134c61b31431335351e04ebfc05f69064bb7`, release **2.5.2** | `m5stack/boards/M5STACK_PaperMono/` (`board.json`, `mpconfigboard.cmake/.h`, `sdkconfig.board`, `manifest.py`, boot artwork), `tests/display/test_papermono_startup.py`, `docs/source/hardware/{lora,nfc}.rst` | **MicroPython/UIFlow2 is a fully supported PaperMono path and the previous pass missed it entirely.** Shipped on M5Burner as `UIFlow2.0 PaperMono` v2.5.1 (2026-08-18) and v2.5.2 (2026-08-28) |
-| [`m5stack/M5PM1`](https://github.com/m5stack/M5PM1) | MIT | `be9a5456c007c333e7ac963f33bfde1ffa5d82ee`, release **1.0.7** | Standalone PMIC driver, in the Arduino library registry | Usable directly from PlatformIO (`library.json`) — GOROman's project does exactly that |
-| [`m5stack/M5IOE1`](https://github.com/m5stack/M5IOE1) | MIT | `846eec7d05e25c09013be2acdb8804487f48a62e`, release **1.0.9** | Standalone expander driver, in the Arduino library registry | See [`features/io-expander.md`](features/io-expander.md) |
-| [`m5stack/esphome-yaml`](https://github.com/m5stack/esphome-yaml) | MIT | `c515c83edc1aa16f11e0297d95a8528ae485931c` | `components/m5ioe1/` external component (switch, light, output, sensor) | The bridge that makes PaperMono possible in ESPHome at all; `hectorzin`'s project depends on it |
-| [`m5stack/m5stack-board-id`](https://github.com/m5stack/m5stack-board-id) | **none** | `f7e2d4a4f34dfd1fb9be0630b4102cb67d3d4cca` | papermono board id added by [PR #2](https://github.com/m5stack/m5stack-board-id/pull/2), 2026-04-08 | The **earliest public trace of the product found by this pass — four and a half months before launch**, and earlier than the UserDemo repository's 2026-05-07 creation |
-| [`bitbank2/bb_epaper`](https://github.com/bitbank2/bb_epaper) | GPL-3.0 | `bfb8dbca98f21e438d8cb23d306b057f516b6819`, release **2.1.11** | `EPD_M5_PAPER_MONO`, `EPD_M5_PAPER_MONO_4GRAY` product enums in `src/bb_epaper.h`; M5IOE1 GPIO sequencing in `src/bb_epaper.cpp` | **Resolves an explicit open question in the existing record.** The previous pass searched `PaperMono` and got zero hits; the code spells it `M5_PAPER_MONO`. Sequence recorded in source: IOE1 `0x4f` pin 3 → EPD 3V3 LDO on, pin 5 toggled for EPD reset, panel type `EP426_800x480` / `_4GRAY`; commented-out lines for touch enable (13), uSD enable (14), touch reset (6) |
-| [`usetrmnl/trmnl-firmware`](https://github.com/usetrmnl/trmnl-firmware) | GPL-3.0 | `8f84e23002197fefb4a53eb3a1d8a10657e0b583`, release **v1.8.16** | `EPD_M5_PAPER_MONO` referenced in `src/display.cpp` | **Confirms the second half of Larry Bank's 2026-08-17 pre-launch claim** (bb_epaper *and* TRMNL BYOD). Whether a shipping TRMNL PaperMono device profile exists was not established |
-| [`bmorcelli/Launcher`](https://github.com/bmorcelli/Launcher) | MIT | `69fdc7d127f516766f0406b609091b90887b83cf`, release **2.8.0** | `boards/m5stack-paper-mono/{platformio.ini,interface.cpp}` | README line 102 marks *"Port to M5-Paper Mono"* **done**. Env: `-DTFT_WIDTH=480 -DTFT_HEIGHT=800 -DROTATION=0 -DDIMMER_SETUP=30 -DHAS_2_BUTTONS=1 -DHAS_TOUCH=1`, `memory_type=qio_opi`, `M5Unified ^0.2.21`, and a **4-bit `SD_MMC`** map: CLK 13, CMD 12, D0 11, D1 10, D2 9, D3 8 |
-
-### 4.3 Class V — official vendor examples and binaries (2 repositories, 4 M5Burner entries)
-
-| Artefact | Where | Version / commit | Note |
-|---|---|---|---|
-| [`m5stack/M5PaperMono-UserDemo`](https://github.com/m5stack/M5PaperMono-UserDemo) | GitHub, MIT | `c1099107271d31a0678d661a896e2b04dbb331ea` (2026-08-10) | Factory firmware, ESP-IDF 5.5.1, fifteen demo apps. One fork exists — `Tr2e/M5PaperMono-UserDemo` — and it is **byte-identical** (GitHub compare: `status: identical, ahead 0, behind 0`) |
-| [`m5stack/M5PaperMono-OTP-Demo`](https://github.com/m5stack/M5PaperMono-OTP-Demo) | GitHub, MIT | `c7c02554f89fd06f80d988b805b2a59050c78a46` (2026-08-20) | Minimal SSD1677 driver using only the panel's OTP waveforms; vendor-recommended over M5GFX. Reused verbatim by SeeSeeBook |
-| `PaperMono UserDemo` v1.2 | M5Burner id `2089640807996628993` | `C153-PaperMono-ESP32S3R8-UserDemo-V1.2-yaozhenquan-8300e309-20260806_0x00.bin`, uploaded 2026-08-18, **18 downloads** | Binary held locally |
-| `UIFlow2.0 PaperMono` v2.5.1 / v2.5.2 | M5Burner id `2089633464953118721` | `…uiflow-efa3815d-…-v2.5.1-20260818.bin` / `…uiflow-428a68d0-…-v2.5.2-20260828.bin`, **3 downloads total** | Build ids embed uiflow-micropython commit prefixes |
-
-### 4.4 The hardware-beta channel
-
-Three independent facts establish that PaperMono units reached third-party developers before
-retail availability, which is why so much software existed on day one:
-
-1. `crosspoint-reader` merged PaperMono support **2026-08-16**, five days before launch
-   (PR #2983); the simulator profile landed **2026-08-20**, one day before.
-2. `0x1abin/crossmux` published a firmware channel literally named
-   **`hardware-beta-papermono`**, referenced in [issue #218](https://github.com/0x1abin/crossmux/issues/218)
-   on 2026-08-24.
-3. M5Stack's own libraries carry PaperMono changes from **2026-07-14** (M5GFX) and
-   **2026-07-17** (M5Unified), and the board id from **2026-04-08**.
-
-### 4.5 Class P — proposals and explicitly untested support (4)
-
-| Project | Licence | Head | Why it is a proposal, not a demonstration |
-|---|---|---|---|
-| [`koosoli/ESPHomeDesigner`](https://github.com/koosoli/ESPHomeDesigner) | GPL-3.0 | `0d82d6763c36b23cfd153d44126d8cd2b7d09425`, release `v1.0.0-rc.42` (2026-08-26) | **The author flags it himself**, and does so well: *"The profile is flagged untested — the device launched only days ago and no community ESPHome config exists yet."* Also honestly states what is missing: battery level, frontlight dimming and deep sleep are not wired "because they run through the M5PM1 PMIC, which has no ESPHome component at this time" |
-| [`shelbeeely/claude-desktop-buddy`](https://github.com/shelbeeely/claude-desktop-buddy) | NOASSERTION (fork of `anthropics/claude-desktop-buddy`) | `15d5e2c947686151453d9c849217442096b384d0` | [PR #4](https://github.com/shelbeeely/claude-desktop-buddy/pull/4) "Add M5Stack Paper Mono support (env:papermono)", merged **2026-08-21 — launch day**. The PR body's own verification is *reading* `PaperMonoBoard.h`: "Verified end-to-end (read `PaperMonoBoard.h` in full)… **zero new `setup()` code** was needed". Three files, no device |
-| [`Belphemur/crosspoint-x-reader`](https://github.com/Belphemur/crosspoint-x-reader) + [`Belphemur/freeink-sdk`](https://github.com/Belphemur/freeink-sdk) | MIT | `4547187dc29cca731352147a63877c24184fe1fc` / `089bd85a71bed6e0e5ef635dbae3da56dd12a2fd` | Very active fork (release v1.9.1, 2026-09-01) but **every PaperMono-adjacent PR in it is X4-Pro work**; the papermono envs are inherited from upstream, unexercised |
-| [`sfoulad/midad-by-foulad`](https://github.com/sfoulad/midad-by-foulad) | MIT | `ef3b455c3aa9ea06204cabbae717b05bc28c1803`, release `v1.8.57` | Same: 3 inherited papermono envs; the project's own hardware-test RC branches are explicitly X4 Pro |
-
-### 4.6 Class C — copies and vendored trees (3 named + ~15 unnamed)
-
-Recorded so they are not mistaken for independent evidence.
-
-| Repository | What it is |
-|---|---|
-| [`goodyttoor/inkback-freeink-sdk`](https://github.com/goodyttoor/inkback-freeink-sdk) | A **detached copy** of `Free-Ink/freeink-sdk` (GitHub does not mark it a fork; `default_branch = inkback/inkmotion`), README and MIT licence preserved, `PaperMonoBoard.h`/`PaperMonoDriver` carried along unchanged. Head `d26ab55af1c67d451de99f08280a6de83608fd0b`, last pushed 2026-08-18 |
-| [`dito94/CrossDiTo`](https://github.com/dito94/CrossDiTo) | A CrossPoint derivative that **vendors `freeink-sdk/` in-tree** rather than as a submodule. Its own `platformio.ini` has 7 envs and **no papermono env** — the PaperMono files are dead weight |
-| [`vjFaLk/esphome-xteink`](https://github.com/vjFaLk/esphome-xteink) | Wraps the whole FreeInk SDK as an ESPHome external component under `components/xteink/sdk/`. Targets Xteink; PaperMono files carried, not exercised |
-| ~15 further repositories | Vendored `M5GFX`/`M5Unified` under `.pio/libdeps/`, `managed_components/` or `components/` — e.g. `infinitechris/esPod`, `jedld/slam_burger`, `myendless1/stack-chan`, `MarkRanton1917/rForth-M5Cardputer`, `scsagentclub/WorldCupLive_ESP`, `Notorious-Squirrel/NS-DOS`, `popolony2k/maritaca-e88-controller`, `kirikak2/midori`, `mdodkins/soledex`. They match `board_M5PaperMono` because the library defines it, not because they use it. **These inflate every GitHub code-search count for this device** |
-
-### 4.7 The useful negative example
-
-[`hawkymisc/buddy-watch`](https://github.com/hawkymisc/buddy-watch) (NOASSERTION, head
-`b28c7d06b5c0a39651dcf837c8b2192c6984b2d8`) is a **M5StopWatch** project, not a PaperMono
-project — and that is exactly why it matters. Its
-[`docs/LAUNCHER.md`](https://github.com/hawkymisc/buddy-watch/blob/main/docs/LAUNCHER.md)
-documents an infinite recursion in
-`Panel_SSD1677_4Gray::display → IPanel::endWrite → display`, diagnosed as **M5GFX
-misidentifying a StopWatch as a PaperMono**: the two boards share the I²C detect block
-(RX8130 `0x32`, BMI270 `0x68`), so when the StopWatch's CST820 touch controller fails to
-answer, M5GFX falls through to `board_M5PaperMono` and instantiates an SSD1677 panel that
-is not there. The recorded root cause is that **M5IOE1 P4 (TP_RST) stayed LOW across an ESP
-reset** (observed `ioe1_out_l=0xB5`, bit 3 clear) — because the IOE1 and PM1 retain state
-independently of the ESP32-S3.
-
-This is a genuine, reproducible-in-principle pitfall for PaperMono work too: the same
-autodetect path, the same latching expander. See
-[`features/io-expander.md`](features/io-expander.md) and
-[`features/epaper-display.md`](features/epaper-display.md).
-
----
-
-## 5. Rejected: false positives and adjacent work
-
-Recorded because a future pass will hit the same search results.
-
-| Item | Why rejected |
-|---|---|
-| [`namelessmucguy/PaperMono`](https://github.com/namelessmucguy/PaperMono) (created 2026-09-01) | **Named for the device, contains none of it.** `app/main/app_main.c` is Espressif's stock `hello_world` example verbatim (CC0 header intact); `app/sdkconfig` even sets `CONFIG_ESPTOOLPY_FLASHSIZE_2MB` — wrong for a 16 MB board. A placeholder, not a project |
-| `harshalpawar/PaperMono-Nerd-Font`, `paper-design/paper-mono`, `Homebrew/homebrew-cask` `font-paper-mono.rb`, `internet-development/www-sacred`, `cosscom/coss`, `rpamis/comet`, `pexllecn/pexllecn`, `tlap9/multiclonage`, `rutopio/mahjong-font` | **A typeface also called "Paper Mono".** Responsible for a large share of the 1,274 `papermono` code-search hits |
-| `PaperMonoid/PaperMonoid` | Username collision, 2023 |
-| [`esphome/esphome`](https://github.com/esphome/esphome) | **Identifier collision.** `epaper_spi`'s C++ class for monochrome panels is called `EPaperMono`; `models/ssd1677.py` exists because Seeed's reTerminal E1004 uses SSD1677. Upstream ESPHome has **no PaperMono board support** — `is:issue papermono repo:esphome/esphome` returns **0** |
-| [`HenryBaby/TamaInk`](https://github.com/HenryBaby/TamaInk) | `verification/freeink-display-drivers/` includes a `papermono` row in a **compile-only** driver matrix. The README states plainly: *"X4 Pro and other devices are unsupported"* |
-| [`canardleteer/sticky-rs`](https://github.com/canardleteer/sticky-rs) | Seeed reTerminal Sticky. Mentions PaperMono only inside a comparative catalogue of FreeInk/CrossPoint targets |
-| [`Lakphy/eego-a4-template-firmware`](https://github.com/Lakphy/eego-a4-template-firmware), [`mohitagw15856/Inkkit`](https://github.com/mohitagw15856/Inkkit) | Carry `M5Pm1.h` inherited from the FreeInk lineage; neither defines `FREEINK_DEVICE_PAPERMONO` nor includes `PaperMonoBoard.h`. Different devices |
-| `eszter007/matcha-reader`, `jpirnay/witchhunt-reader`, `aBER0724/crosspoint-reader-cjk`, `juicecultus/crosspoint-reader-papers3` | CrossPoint forks with **no papermono build env** at their current heads. `matcha-reader` PR #117 (2026-08-16, closed) proposed one; `crosspoint-reader-papers3` is the **PaperS3** port, a different board |
-| `Tr2e/M5PaperMono-UserDemo` | Fork of the vendor demo, verified byte-identical to upstream |
-| `78/xiaozhi-esp32`, `m5stack/m5stack-linux-dtoverlays`, `zephyrproject-rtos/zephyr`, `nanoframework/*`, `tuya/TuyaOpen`, `lshaf/unigeek`, `PFalko/m5stack-papercolor-esphome`, and the whole M5StopWatch cluster | Surfaced by `M5PM1`/`M5IOE1` searches. Those chips are shared with the StickS3, StopWatch, PaperColor and CoreP4. **A Zephyr `regulator_m5pm1.c` driver exists** — relevant to the chip, not to this board |
-| `koosoli/ESPHomeDesigner` copies in `DrBlokmeister/HASS_NUC` | A user's Home Assistant config directory containing the add-on |
-
----
-
-## 6. Community venues and what their evidence is worth
-
-### 6.1 M5Burner — the community firmware listing
-
-The full catalogue was enumerated on 2026-09-02 via `https://burner.m5stack.com/api/v1/firmwares`
-with `pageNum`/`pageSize` paging: **2,373 firmwares total, of which exactly 4 are PaperMono**.
-This is a complete census of that venue, not a sample.
-
-| Firmware | id | Source type | Uploader | Uploaded | Downloads | Declared source |
-|---|---|---|---|---|---|---|
-| `PaperMono UserDemo` v1.2 | `2089640807996628993` | OFFICIAL | m5stack (userId 1) | 2026-08-18 | 18 | — |
-| `UIFlow2.0 PaperMono` v2.5.2 | `2089633464953118721` | OFFICIAL | m5stack | 2026-08-18 (v2.5.2 2026-08-28) | 3 | — |
-| `CrossPoint-PaperMono-CJK` 1.5.0-RC | `2091144466157694978` | **COMMUNITY** | **IAMLIUBO** (userId 3966, <https://github.com/imliubo>) | 2026-08-22 | 27 | `https://github.com/MarsTechHAN/crosspoint-reader-mono` |
-| `PaperMono Launcher` v0.1.0 | `2094259851119865857` | **COMMUNITY** | **MingRZou** (userId 256310) | 2026-08-31 | 1 | `https://github.com/MingRZou/PaperMono-Launcher` |
-
-M5Burner's device registry contains **both** a legacy `Paper` device (`1897100000000000013`)
-and a distinct `PaperMono` device (`2093000000000000020`); only the Launcher uses the latter,
-which is why a naive device-filtered query misses three of the four.
-
-> **Do not read those download counts as popularity.** 27 downloads of the top community
-> build eleven days after launch is consistent with a product that was purchasable for nine
-> minutes. It is a measure of unit scarcity, not of interest.
-
-### 6.2 M5Stack forum and Discord
-
-`community.m5stack.com` remains **auth-walled and unusable**: `/api/search?term=papermono`
-returns HTTP 401 *"A valid login session was not found"* (re-checked 2026-09-02).
-`/api/recent` is open and returned 20 topics with **zero** PaperMono topics in the window.
-**No determination is possible** about forum activity — this is an inaccessible source, not
-a negative result.
-
-The M5Stack Discord was not searchable by any unauthenticated method available to this pass.
-Recorded as an unexamined venue.
-
-### 6.3 Reddit
-
-Reddit tokenises the two spellings differently, so both were searched in every subreddit.
-
-| Query | Result (2026-09-02) |
-|---|---|
-| sitewide `papermono` | 3 threads: two automated HN mirrors (r/hackernews, r/hypeurls) + **one new**: [r/xteinkereader "M5Stack PaperMono"](https://old.reddit.com/r/xteinkereader/comments/1w472fk/m5stack_papermono/) |
-| sitewide `"paper mono" m5stack` | 5 threads: the above plus the two r/M5Stack threads already recorded |
-| r/M5Stack `papermono` / `paper mono` | Still only [`1vquxa5`](https://old.reddit.com/r/M5Stack/comments/1vquxa5/paper_mono_coming_august_21st/) and [`1vuaneb`](https://old.reddit.com/r/M5Stack/comments/1vuaneb/check_out_whats_new_this_week/) |
-| r/eink, r/CrossPointReader | 0 relevant |
-
-**The new thread matters.** [r/xteinkereader `1w472fk`](https://old.reddit.com/r/xteinkereader/comments/1w472fk/m5stack_papermono/)
-(u/arghya1988, 2026-09-01 09:39 UTC, 8 points, 9 comments) drew a reply from
-**u/WolfieLee90**, who wrote: *"I managed to pick one up when they opened orders and received
-it yesterday. I got the Lite model that does not have LoRa and NFC. I will be flashing it with
-Crosspoi[nt]"* — and then, on 2026-09-02, posted **two further photographs: CrossPoint running
-with the frontlight on, and a side-by-side comparison against an Xteink X4.** Evidence type
-`O` (firsthand ownership) with images.
-
-This is **the first independent end-user evidence of third-party firmware on retail PaperMono
-hardware** found anywhere. It is a forum photo, not a measurement: no timings, no current
-draw, no battery figures.
-
-Also on that thread, u/mba2016kid gives a correct availability summary ("sold out the initial
-batch and won't have more for a couple months") and an opinion on build quality; and
-u/arghya1988's premise contains **the same $55/NFC/LoRa conflation Liliputing published** —
-$55 is the Lite, which has neither. See
-[`README.md`](README.md#community-editorial-and-project-coverage).
-
-### 6.4 Video
-
-Re-checked on YouTube 2026-09-02 (`M5Stack PaperMono`, `PaperMono`, sorted by upload date).
-**No new PaperMono project video exists.** The population is unchanged since the previous pass:
-
-| Video | Channel | Published | Views 2026-09-02 (2026-09-01) | Evidence |
-|---|---|---|---|---|
-| [M5Stack PaperMono: The Ultimate ESP32 Pocket Gadget?](https://youtu.be/sRlGOgX9KOA) | **Volos Projects** | 2026-08-29 | **72,122** (61,590) | `O + Op`. The only hands-on. **Description carries a vendor referral link (`?ref=kmjp2x8a`)** — a disclosed commercial relationship. Self-described first look, not a measurement review. Repeats "backlight" for what is a *frontlight* |
-| [New Arrivals: PaperMono & PaperMono-Lite](https://youtu.be/0-qQ0y-WEek) | M5Stack | 2026-08-21 | 18,101 (16,938) | `V` |
-| [Super Cool products! Let's unboxing!](https://youtu.be/gX4cTpS2gUA) | IAMLIUBO | 2026-08-25 | 173 (145) | `O`. Note this is **the same person who uploaded the CrossPoint CJK build to M5Burner** — an M5Stack-affiliated account, not an independent reviewer |
-
-### 6.5 Written coverage
-
-Unchanged and re-verified 2026-09-02: `hackaday.com/wp-json/wp/v2/search?search=papermono`
-returns `[]`. `hackaday.io/search?term=papermono` now **302-redirects to a sign-in page** —
-newly auth-walled, so no determination. `hackster.io/search?q=papermono` returns a JavaScript
-shell with no server-rendered results. GitLab.com `/api/v4/projects?search=papermono` returns
-an empty array (`/api/v4/search` requires auth). PlatformIO registry, npm and the Arduino
-library registry contain **no PaperMono library** — the Arduino registry's only textual match,
-`PDLS_EXT3_Basic_Fast`, is a Pervasive Displays "paper monochrome" library.
-
-Every written article about this device still traces to
-[one vendor blog post](https://shop.m5stack.com/blogs/news/m5stack-launches-papermono-a-compact-e-ink-development-terminal-for-connected-projects).
-
----
-
-## 7. Prevalence, stated honestly
-
-- **129 distinct repositories** were surfaced across 17 GitHub code queries, 4 repository
-  queries and 4 issue/PR queries (raw counts in [`examples/search-log.md`](examples/search-log.md)).
-- **48 repositories were inspected in detail** — metadata, default-branch head commit,
-  licence file, README, and where relevant `platformio.ini`, board headers and commit logs.
-- Of those 48: **9 are class D**, **13 class S**, **2 class V** (plus 4 M5Burner binaries),
-  **4 class P**, **3 class C** (plus ~15 unnamed vendored copies), **1 useful negative**, and
-  the remainder rejected.
-- **M5Burner: 4 PaperMono firmwares out of a complete enumeration of 2,373.**
-- **Reddit: 3 threads sitewide for `papermono`, 5 for `"paper mono" m5stack`.**
-- **YouTube: 1 independent hands-on video, with a disclosed affiliate link.**
-
-**No star count, download count or view count in this document should be read as evidence of
-adoption.** The device was purchasable for approximately nine minutes on 2026-08-21 and has
-been out of stock since. The largest third-party PaperMono repository has **4 stars**; the
-frameworks that carry PaperMono targets have thousands, but those stars belong to the
-frameworks. Nothing here was measured against a user population, because there effectively
-is not one yet.
-
----
-
-## 8. What this pass changes in the existing record
-
-| Existing statement | Where | Correction (2026-09-02) |
-|---|---|---|
-| CrossPoint PaperMono support is *"roadmap, not shipped support"* | prior market sweep §4.3 | **Wrong.** Merged into `crosspoint-reader` `develop` on 2026-08-16 (PR #2983); three `papermono` build envs on the default branch; a shipped M5Burner binary since 2026-08-22. [§3](#3-crosspoint-the-source-repository-question-answered) |
-| *"A GitHub code search of `bitbank2/bb_epaper` for 'PaperMono' returned 0 matches… Unresolved; do not cite `bb_epaper` support as fact"* | prior market sweep §4.3 | **Resolved: support exists.** The identifiers are `EPD_M5_PAPER_MONO` and `EPD_M5_PAPER_MONO_4GRAY`, with M5IOE1 power/reset sequencing in `src/bb_epaper.cpp`. The TRMNL half of the same claim also holds (`usetrmnl/trmnl-firmware/src/display.cpp`) |
-| *"the community evidence base for PaperMono is currently four GitHub repositories and one YouTube video"* | prior market sweep §4.5; echoed in [`README.md`](README.md#community-editorial-and-project-coverage) | **Understated by roughly 5×.** 9 hardware-evidenced projects, 13 upstream targets, 2 vendor demos, 4 M5Burner binaries. The video count is correct |
-| `EggUncle/PaperMonoCalendar` — *"ownership claimed not shown"* | prior market sweep §4.3 | **Partly superseded.** Preview images remain software-generated (the README still says so, commendably), but the README now states v2 sync and `HUB / SYNCED` are confirmed on a PaperMono, and v3 is flashed but not yet accepted |
-| `hectorzin/…-ESPHome` — *"early WIP… labelled 'hipótesis de prueba'"* | prior market sweep §4.3 | **Superseded.** Now carries measured refresh timings, a specific IMU-interrupt route, light-sleep and PMIC-shutdown power policy. The rotation section is still honestly hedged |
-| Third-party repository commit hashes were not captured | brief; prior `coverage.md` | **Fixed.** Every repository in [`examples/catalog.json`](examples/catalog.json) is pinned to a full 40-character default-branch head SHA retrieved 2026-09-02 |
-| MicroPython / UIFlow2 support not recorded | absent from prior passes | **New.** `m5stack/uiflow-micropython` carries a complete `M5STACK_PaperMono` board plus `tests/display/test_papermono_startup.py`, shipped on M5Burner as v2.5.1/v2.5.2 |
-| Earliest public trace of the product is the UserDemo repo, 2026-05-07 | [`README.md`](README.md) product history | **Earlier trace found.** `m5stack/m5stack-board-id` [PR #2](https://github.com/m5stack/m5stack-board-id/pull/2), *"Add papercolor, papermono and stopwatch"*, **2026-04-08** |
-| Only two variants exist (C153, C153-LITE) | [`README.md`](README.md#identity-and-variants) | **An unexplained third name appears in vendor source.** `m5stack/M5GFX` `src/M5GFX.cpp` at `d91077b9a607b59404e4e4a49f775c792bfae382` contains, at line 1893, `0x50u, // NFC (for PaperMono Pro)` and at line 1899 `// no CST820, with NFC == PaperMono,PaperMono Pro`. **No "PaperMono Pro" SKU exists** on `shop.m5stack.com` (search suggest returns only PaperMono and PaperMono Lite), on `docs.m5stack.com` (`/en/core/PaperMono-Pro` → 404) or in the M5Burner device registry. Evidence class: **vendor source comment only.** Do not treat as a product |
-| Display controller naming | [`features/epaper-display.md`](features/epaper-display.md) | The FreeInk/CrossPoint tree called the controller **SSD1683** in build comments until [crossmux PR #221](https://github.com/0x1abin/crossmux/pull/221) corrected it to SSD1677 on 2026-08-24. **Upstream `crosspoint-reader/crosspoint-reader`'s `platformio.ini` still says `SSD1683 800x480`** in the `[env:papermono]` header comment at head `e6139861`. A comment-only defect, but it will mislead a reader |
-| microSD bus width | [`features/microsd.md`](features/microsd.md) | **Two upstream projects disagree.** `bmorcelli/Launcher` configures `-DSD_MMC_4BIT=1` with D0–D3 on GPIO 11/10/9/8; `Free-Ink/freeink-sdk` and `MarsTechHAN/crosspoint-reader-mono` describe **native 1-bit SDMMC**. Both are software choices on the same 4-bit-capable wiring, but a reader copying one into the other's stack will get a mount failure |
-| Touch controller naming | [`features/touch.md`](features/touch.md) | GOROman's notes call it **FT5x06**, the vendor and everyone else call it **FT6336G**. `Free-Ink/freeink-sdk`'s README reconciles this explicitly: it handles "the **FT5x06 family** (Paper Mono's FT6336)". Not a conflict, a family name |
-
----
-
-## 8b. CrossPlay — added 2026-09-02
-
-[`ma-r-s/crossplay`](https://github.com/ma-r-s/crossplay) is a personal fork of
-CrossPoint Reader (MIT, ★15, branch `xteink`, HEAD checked 2026-09-02) that adds
-roughly 26 games and small tools alongside the reader. It is relevant here for
-one concrete reason: **`platformio.ini` carries `papermono`,
-`papermono-gh_release` and `papermono-gh_release_rc` build environments.**
-
-Classification: **Class P — proposed or explicitly untested PaperMono support.**
-
-> **Update 2026-09-11 — this remains correct for *upstream* CrossPlay, but a
-> dedicated port now exists.** `fperuzzo72/crossplay-papermono` was created and
-> pushed **2026-09-11**, MIT, on a branch named `papermono-bringup`, with commits
-> that tune the render task stack to 16384 to match the X4 Pro, wire up release
-> environments, and repoint the updater. That is hands-on bring-up, not a
-> build-flag claim.
->
-> **Nobody has yet reported it working on hardware**, so the port is recorded as
-> its own entry rather than reclassifying upstream CrossPlay. Re-check this — a
-> port that appeared *during* a research pass is a moving target.
-The environments exist in the build configuration, but the fork's own
-`LOCAL_SCOPE.md` describes only the Xteink X4 Pro and Seeed reTerminal Sticky as
-its targets, and **no report of anyone running CrossPlay on a PaperMono was
-found**. It is not Class D; nothing demonstrates it on this hardware.
-
-Full record: [`software/applications/crossplay`](../../../software/applications/crossplay/README.md),
-including a divergence analysis (2,391 ahead / 65 behind upstream, but −862
-deletions — an overwhelmingly *additive* fork) and a seam-by-seam assessment of
-which of its changes could be upstreamed as patches.
-
-## 8c. `osprey74/Nostos` — Meshtastic reception — added 2026-09-11
-
-Absent from every prior sweep, and the most technically ambitious third-party use
-of this board's radio found so far.
-
-| | |
-|---|---|
-| Repository | `osprey74/Nostos` @ `56acd5e` |
-| Language | Rust |
-| What it does | **Receives and decodes Meshtastic traffic** on the onboard SX1262 |
-
-`crates/nostos-meshtastic` performs on-air header parsing, **AES-CTR decryption**
-and **Position protobuf decoding**. It is a *custom receiver*, **not** a
-Meshtastic firmware port — upstream `meshtastic/firmware` has no PaperMono
-variant (see [`features/lora.md`](features/lora.md) §12).
-
-Its radio configuration differs from the vendor demo in every parameter —
-923.000 MHz / BW 125 kHz / SF9 / CR 4-5 / sync `0x3A` versus the factory
-868.0 MHz / BW 62.5 kHz / SF12 / CR 4/8 / sync `0x34` — which makes it a useful
-independent cross-check that the documented bring-up sequence is not
-vendor-specific folklore.
-
-It also independently corroborates the RGB LED wiring, with a comment stating in
-Japanese that the LED is three independent lines and **not** a WS2812 — see
-[`features/buttons-and-rgb-led.md`](features/buttons-and-rgb-led.md).
-
-**Not run, not verified on hardware.** Classified by source reading only.
-
-## 9. Cross-references
-
-- Device overview and identity: [`README.md`](README.md)
-- Per-feature guides, which these projects are the working examples for:
-  [`features/README.md`](features/README.md) —
-  [display](features/epaper-display.md) ·
-  [frontlight](features/frontlight.md) ·
-  [touch](features/touch.md) ·
-  [LoRa](features/lora.md) ·
-  [microSD](features/microsd.md) ·
-  [I/O expander](features/io-expander.md) ·
-  [power and sleep](features/power-and-sleep.md) ·
-  [RTC](features/rtc.md) ·
-  [IMU](features/imu.md)
-- Capability-to-evidence matrix: [`coverage.md`](coverage.md)
-- Contradictions ledger: [`gaps-and-conflicts.md`](gaps-and-conflicts.md)
-- Source classes and retrieval dates: [`sources.md`](sources.md)
-- Machine-readable example catalogue: [`examples/catalog.json`](examples/catalog.json)
-- Search method and stopping criterion: [`examples/search-log.md`](examples/search-log.md)
-- Selected portfolio: [`examples/best.md`](examples/best.md)
diff --git a/devices/m5stack/papermono/research-log.md b/devices/m5stack/papermono/research-log.md
deleted file mode 100644
index 806b49e..0000000
--- a/devices/m5stack/papermono/research-log.md
+++ /dev/null
@@ -1,462 +0,0 @@
-# PaperMono — research log
-
-> **Search cutoff: 2026-09-01 (UTC).** Nothing published after that date is in
-> this record. Every query below was executed on 2026-09-01 unless a row says
-> otherwise. **No query, fetch or command in this pass touched physical
-> hardware.**
-
-This is the ledger of *what was looked for and what came back*, including the
-things that came back empty. It exists so that a later pass can tell the
-difference between "not found" and "not looked for", and does not repeat 94
-queries to rediscover that Hackaday published nothing.
-
-Companion documents: [`sources.md`](sources.md) (what was kept, with IDs) ·
-[`commands.md`](commands.md) (what was run, with execution status) ·
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) (what disagrees).
-
-## Contents
-
-- [Disposition key](#disposition-key)
-- [Method — the user-agent ladder](#method--the-user-agent-ladder)
-- [Pass 1 — vendor documentation](#pass-1--vendor-documentation-docsm5stackcom)
-- [Pass 2 — vendor storefront](#pass-2--vendor-storefront-shopm5stackcom)
-- [Pass 3 — M5Burner firmware distribution](#pass-3--m5burner-firmware-distribution)
-- [Pass 4 — vendor source repositories](#pass-4--vendor-source-repositories-github)
-- [Pass 5 — community, social, forums, news](#pass-5--community-social-forums-news)
-- [Pass 6 — retailers and distributors](#pass-6--retailers-and-distributors)
-- [Pass 7 — press, video and third-party code](#pass-7--press-video-and-third-party-code)
-- [Dead links and recovery attempts](#dead-links-and-recovery-attempts)
-- [Retrieval findings worth reusing](#retrieval-findings-worth-reusing)
-- [Not attempted, and why](#not-attempted-and-why)
-- [Stopping criterion](#stopping-criterion)
-- [Query-count summary](#query-count-summary)
-
-## Disposition key
-
-| Disposition | Meaning |
-|---|---|
-| **useful** | Retrieved and admitted as evidence; appears in [`sources.md`](sources.md) |
-| **duplicate** | Retrieved, but the same content already held by a better path |
-| **rejected** | Retrieved and **not** admitted — re-syndication, noise, or a body that is not what the status code implies |
-| **inaccessible** | Bot-walled, auth-walled or a JavaScript shell. **No determination possible** — this is *not* a negative |
-| **dead** | 404 / 302-to-nowhere / subreddit gone |
-| **negative-confirmed** | Successfully retrieved, with full content, and the thing sought is **genuinely absent**. A result, not a failure |
-
-The distinction between **inaccessible** and **negative-confirmed** is the most
-load-bearing thing in this file. Mouser returning a bot-wall (§6) and Adafruit
-returning "No products found" (§6) look similar in a terminal and mean opposite
-things.
-
-## Method — the user-agent ladder
-
-Applied in order, stopping at the first HTTP 200 with a plausible body:
-
-```
-curl/8.5.0
-  → Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
-  → WhatsApp/2.23.20.0
-  → Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot
-  → Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ClaudeBot/1.0; +claudebot@anthropic.com
-```
-
-Two honest caveats about that ladder:
-
-- **`curl/8.5.0` is a hardcoded string, not this host's real default.** The
-  documenting host runs curl **8.21.0**. The first rung is therefore a *chosen*
-  identity like every other rung, and "plain curl worked" in this log means "a
-  request identifying itself as `curl/8.5.0` worked".
-- A 200 obtained on a later rung is **not** evidence that the resource works
-  normally for ordinary clients. Where that distinction mattered — the vendor's
-  own sites — it is stated: `docs.m5stack.com`, `shop.m5stack.com` and
-  `burner.m5stack.com` all served 200 to the **first** request.
-
-Helpers: [`scratch/m5stack-papermono/docs/_tools/fetch.sh`](../../../scratch/m5stack-papermono/docs/_tools/fetch.sh)
-(single-UA, records status/bytes/sha256/date to a `.meta` sidecar) and
-`scratch/m5stack-papermono/market/_raw/fetch.sh` (rotates the ladder and prints
-the status of every rung).
-
-## Pass 1 — vendor documentation (`docs.m5stack.com`)
-
-Chrome 131 UA throughout; no fallback required on any page.
-
-| # | Exact query / endpoint | Filters | HTTP | Result depth | Disposition | Notes → ID |
-|---|---|---|---|---|---|---|
-| 1.1 | `/en/core/PaperMono` | — | 200 | 153 939 B, full page | **useful** | → S01 |
-| 1.2 | `/en/core/PaperMono-Lite` | — | 200 | 151 608 B | **useful** | → S04. Basis of the whole variant record |
-| 1.3 | `/zh_CN/core/PaperMono` | — | 200 | 152 668 B | **useful** | → S02. The only substantive delta is CN-language datasheet links |
-| 1.4 | `/ja/core/PaperMono` | — | 200 | 156 234 B | **useful** | → S03 |
-| 1.5 | `/zh_CN/core/PaperMono-Lite` | — | 200 | 150 365 B | **useful** | → S05 |
-| 1.6 | `/ja/core/PaperMono-Lite` | — | 200 | 153 791 B | **useful** | → S06 |
-| 1.7 | `/en/arduino/papermono/program` | — | 200 | 321 758 B | **useful** | → S07 |
-| 1.8 | `/en/arduino/papermono/m5pm1_m5ioe1` | — | 200 | 416 888 B | **useful** | → S08. Richest single vendor page |
-| 1.9 | `/en/uiflow2/papermono/program` | — | 200 | 265 217 B | **useful** | → S09 |
-| 1.10 | `/en/products` | — | 200 | 560 714 B | **useful** | → S10. Confirms exactly two SKUs |
-| 1.11 | `/en/certification`, full-text search for `PaperMono`, `C153` | — | 200 | 382 669 B, **0 / 0 matches** | **negative-confirmed** | → S11 |
-| 1.12 | `/en/product_i2c_addr`, full-text search for `PaperMono`, `C153` | — | 200 | 312 908 B, **0 / 0 matches** | **negative-confirmed** | → S12 |
-| 1.13 | `/en/history` | — | 200 | 137 555 B | **useful** | → S13. Both SKUs dated 2026-08-20, category "Controllers" |
-| 1.14 | `/en/core/PaperS3` | — | 200 | 30 KB | **useful** | Verified every claim in the community's PaperS3 comparison |
-| 1.15 | `/en/core/PaperColor` | — | 200 | 30 KB | **useful** | Lineage context: Spectra 6, 400×600, 1250 mAh |
-| 1.16 | `/en/core/CoreInk` | — | 200 | — | **useful** | Lineage context |
-| 1.17 | `/en/core/Paper` | — | **404** | — | **dead** | The original M5Paper has no page at this slug. See [dead links](#dead-links-and-recovery-attempts) |
-| 1.18 | `/en/core/{papermono,papermono-lite,CoreInk}` (lower case) | — | **302** | — | *note* | Slugs are case-sensitive; lower case redirects to CamelCase. Not an error, but it silently rewrites your URL |
-| 1.19 | `/en/core/{papermono_lite,PaperMonoLite}` | — | **404** | — | **dead** | Underscore and concatenated forms do not exist |
-| 1.20 | Full-text search of the extracted S09 text for a firmware version, a block list, or a limitation | — | — | **0 matches** | **negative-confirmed** | UiFlow2 support is advertised and undocumented. **Verified by search, not assumed** |
-| 1.21 | Cross-language diff: table-row counts, `G\d+` / `PYG\d+` / `0x..` token sets, numeric specs, asset URL sets across all six product pages | — | — | 89/89/89 rows; **empty symmetric difference** on tokens in all four language pairs | **useful** | Establishes the three languages are faithful translations — so the frontlight naming defect is in the *source content*, not a translation error |
-
-### Vendor design artifacts and datasheets
-
-| # | Exact endpoint | HTTP | Depth | Disposition | Notes → ID |
-|---|---|---|---|---|---|
-| 1.22 | `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/PaperMono_SCH_V0.6.2_20260522.pdf` | 200 | 1 462 039 B, 6 sheets | **useful** | → S14 |
-| 1.23 | `…/1267/C153_PaperMono_model_size.pdf` | 200 | 21 346 B, 1 page | **useful** | → S15 |
-| 1.24 | `…/472/esp32-s3_datasheet_en.pdf` | 200 | 1 083 807 B, 84 pp | **useful** | → S18 |
-| 1.25 | `m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/app/Stamp%20Fly/BMI270.PDF` | 200 | 3 830 973 B, 162 pp | **useful** | → S19. Note the path: a **Stamp Fly** asset, which is how it went five years stale |
-| 1.26 | `…/1267/SSD1677.pdf` | 200 | 3 602 487 B, 46 pp | **useful** | → S20 |
-| 1.27 | `…/1267/EPD_Module_User_Manual.pdf` | 200 | 8 666 208 B, 30 pp | **useful** | → S21 |
-| 1.28 | `…/1132/RX8130CE_cn-Register-Datasheet.pdf` | 200 | 2 283 323 B, 70 pp | **useful** | → S22. Filename says `_cn`; content is the English ETM50E-09 |
-| 1.29 | `…/1205/ST25R3916_EN.pdf` | 200 | 2 241 765 B, 160 pp | **useful** | → S23 |
-| 1.30 | `…/1177/DS_SX1261_2_V2-2.pdf` | 200 | 4 459 535 B, 118 pp | **useful** | → S24. Describes the **chip**; no module datasheet exists |
-| 1.31 | `…/1207/M5PM1_Datasheet_EN.pdf` | 200 | 814 731 B, 35 pp | **useful** | → S25 |
-| 1.32 | `…/1210/IO_Expander_Datasheet_EN.pdf` | 200 | 398 463 B, 12 pp | **useful** | → S26 |
-| 1.33 | `…/1268/PaperMono-Lite_PRJ_V0.6.2_20260522.pdf` | — | — | **not attempted** | URL harvested from S04 only. → S16. **The highest-value untaken lead for the Lite** |
-| 1.34 | `…/1268/C153-Lite_PaperMono-Lite_model_size.pdf` | — | — | **not attempted** | → S17 |
-| 1.35 | `…/1207/M5PM1_Datasheet_CN.pdf`, `…/1210/IO_Expander_Datasheet_CN.pdf`, `…/1205/ST25R3916_ZH.pdf`, `…/472/esp32-s3_datasheet_cn.pdf` | — | — | **not attempted** | zh_CN-only variants harvested from S02. → S27–S30. A CN↔EN diff of the two M5-designed chips' manuals is the best remaining route to settling the pin-nomenclature question |
-| 1.36 | `…/1267/C153-PaperMono-UserDemo_0x00.exe` | — | — | **not attempted** | Windows executable, out of scope. → S40. **The finding is that both product pages link the same file, under `1267/`** |
-
-## Pass 2 — vendor storefront (`shop.m5stack.com`)
-
-Plain `curl/8.5.0` was sufficient throughout — no UA rotation needed.
-
-| # | Exact query | HTTP | Depth | Disposition | Notes |
-|---|---|---|---|---|---|
-| 2.1 | `/search/suggest.json?q=papermono&resources[type]=product&resources[limit]=10` | 200 | 2 products | **useful** | Both SKUs, prices, `available:false` |
-| 2.2 | `/search?q=papermono` | 200 | 448 043 B, 4 results | **useful** | → S51. **The only way the real handles were found** |
-| 2.3 | `/search?q=paper` | 200 | 521 KB | **useful** | Enumerated the whole e-paper line including PaperColor and every EOL M5Paper variant |
-| 2.4 | `/products/m5papermono-with-lora-nfc-800x480-3-97-eink-display` and `.json` | 200 ×2 | 703 507 / 20 925 B | **useful** | → S48 |
-| 2.5 | `/products/papermono-lite-dev-kit-800x480-3-97-e-ink-display` and `.json` | 200 ×2 | 693 406 / 19 938 B | **useful** | → S49 |
-| 2.6 | `/products/<handle>.json` × 8 handles across the e-paper lineage | 200 ×8 | full | **useful** | `sku`, `price`, `created_at`, `published_at` for the complete family table |
-| 2.7 | `/products/papermono` | **404** | 389 759 B | **dead** | Handle does not exist |
-| 2.8 | `/products/papermono-lite` | **404** | 389 759 B | **dead** | Handle does not exist |
-| 2.9 | `/products/m5stack-papermono` | **404** | 389 759 B | **dead** | Handle does not exist |
-| 2.10 | `/blogs/news/m5stack-launches-papermono-…` | 200 | 448 198 B | **useful** | → S50. `<time datetime="2026-08-21">`; this theme emits no JSON-LD `datePublished` |
-| 2.11 | `/blogs/news.atom` | 200 | 30 entries, back to 2021 | **useful** | → S52 |
-| 2.12 | `m5stack.com/distributor` | 200 | 101 KB, 37 domains extracted | **useful** | → S56. Seed list for pass 6 |
-
-> **The three 404s are worth a note.** All three returned **exactly 389 759 bytes**
-> with **three different SHA-256 values** — a templated Shopify 404 carrying a
-> per-request nonce. Byte-length equality is not content equality; hash them.
-
-## Pass 3 — M5Burner firmware distribution
-
-| # | Exact endpoint | HTTP | Depth | Disposition | Notes |
-|---|---|---|---|---|---|
-| 3.1 | `burner.m5stack.com/firmware/2089640807996628993/` | 200 | 2 735 B | **useful (weakly)** | → S31. React shell, empty `<div id="root">`; only the `og:` tags carry information |
-| 3.2 | `burner.m5stack.com/firmware/2091144466157694978/` | 200 | 3 407 B | **useful (weakly)** | → S32 |
-| 3.3 | `/assets/index-DpEo0Py5.js` → `/assets/http-ChO34QIa.js` → `/assets/firmware-C6nFrscE.js` | 200 ×3 | 230 198 / 47 846 / 17 403 B | **useful** | → S37. Reversed to recover the API base and the endpoint shapes |
-| 3.4 | `/api/firmwares/2089640807996628993` | **401** | `{"msg":"请先登录"}` | **inaccessible** | The obvious path is auth-walled |
-| 3.5 | `/api/v1/firmwares/2089640807996628993` | 200 | 1 209 B | **useful** | → S33. **`/api/v1` is public where `/api` is not** |
-| 3.6 | `/api/v1/firmwares/2089640807996628993/versions` | 200 | 641 B | **useful** | → S34 |
-| 3.7 | `/api/v1/firmwares/2091144466157694978` and `/versions` | 200 ×2 | 1 460 / 638 B | **useful** | → S35, S36 |
-| 3.8 | `/api/v1/firmwares/{id}/versions/{vid}/download` ×2 | **302** → CDN, then 200 | 2 868 208 / 10 319 500 B | **useful** | → S38, S39. Both validated by content before being given a `.bin` extension |
-
-## Pass 4 — vendor source repositories (GitHub)
-
-Authenticated through `gh auth token` (5 000 req/h). The token was never printed
-and is not recorded anywhere in this repository.
-
-| # | Exact query / command | Depth | Disposition | Notes |
-|---|---|---|---|---|
-| 4.1 | `gh api repos/m5stack/{M5PaperMono-UserDemo,M5PaperMono-OTP-Demo,M5PM1,M5IOE1,M5_Hardware}` | 5 repos | **useful** | All five exist, are public, none empty → S41–S45 |
-| 4.2 | `git clone` of the four small repos + `--filter=blob:none --no-checkout` for `M5_Hardware` | full trees | **useful** | The blobless clone was a deliberate size choice: 348 KB against ~127 MB |
-| 4.3 | `git -C M5_Hardware ls-tree -r --name-only HEAD \| grep -iE 'papermono\|c153'` | 369-file tree | **negative-confirmed** | **0 matches.** → S45 |
-| 4.4 | `… \| grep -i 'paper'` | same | **negative-confirmed** | 3 matches, none C153 (`C139_PaperS3`, `C151_PaperColor`, `K049-B_Paper_v1.1`) |
-| 4.5 | `… \| grep -oE 'C1[0-9]{2}' \| sort -u \| tail` | same | **useful** | SKU sequence reaches **C152** and stops. The gap is at exactly the right place to be meaningful |
-| 4.6 | `git clone` M5Unified and M5GFX, then `fetch origin develop:develop` | both branches | **useful** | → S46, S47 |
-| 4.7 | `git -C M5GFX grep -n 'board_M5PaperMono' master -- src/lgfx/boards.hpp` | — | **useful** | Board support is on `master`, refuting the vendor's `#develop` requirement |
-| 4.8 | `git -C M5Unified grep -q 'board_M5PaperMono' 0.2.21 -- src/` and the same for M5GFX `0.2.28` | — | **useful** | Support ships in the **released tags** |
-| 4.9 | `grep -rE 'GPIO_NUM_0\b' main/` in the UserDemo | 2 hits | **useful** | Both benign; the `G0_BOOT_OUT` path is never exercised by the demo |
-
-**A search that was *not* run and should have been:** no commit SHA was recorded
-for any **third-party** repository (S89–S96). Those citations are therefore not
-pinned and cannot be re-resolved byte-for-byte. Recorded as a defect of this pass.
-
-## Pass 5 — community, social, forums, news
-
-| # | Service | Exact query | Filters | UA | HTTP | Depth | Disposition | Notes |
-|---|---|---|---|---|---|---|---|---|
-| 5.1 | old.reddit.com | `/search.json?q=papermono&sort=new&limit=100` | site-wide, `sort=new` | WhatsApp/2.23.20.0 | 200 | 100 requested, **2 returned** | **useful (scarcity)** | Both results are bot mirrors (r/hackernews, r/hypeurls). **That is the entire site-wide footprint** |
-| 5.2 | old.reddit.com | `/r/{esp32,eink,M5Stack,ereader}/search.json?q=papermono&restrict_sr=1&t=all` | per-sub, all time | WhatsApp | 200 ×4 | 100 requested each | **negative-confirmed** | **0 results in every subreddit — including r/M5Stack** |
-| 5.3 | old.reddit.com | same four subs, `q=paper mono` | per-sub, all time | WhatsApp | 200 ×4 | 100 each | **useful** | **Tokenisation gotcha:** the spaced form returned the two real r/M5Stack threads that `papermono` missed entirely. r/esp32 (5 hits) and r/eink (3) were unrelated. → S70, S71 |
-| 5.4 | old.reddit.com | `/r/M5Stack/comments/1vquxa5/….json?limit=60` | full comment tree | WhatsApp | 200 | 22 comments | **useful** | → S70 |
-| 5.5 | old.reddit.com | `/r/M5Stack/comments/1vuaneb/….json?limit=60` | full comment tree | WhatsApp | 200 | 17 comments | **useful** | → S71. Produced the openelab.de lead |
-| 5.6 | old.reddit.com | `/r/{CrossPointReader,einkesp32}/search.json?q=papermono` | per-sub | WhatsApp | 200 ×2 | 100 each | **negative-confirmed** | 0 in both — **including the CrossPoint community that lists PaperMono on its own roadmap** |
-| 5.7 | old.reddit.com | **second broad pass**: `M5Stack e-ink`, `papermono lite`, `M5 PaperMono`, `C153 m5stack` | `t=year` | WhatsApp | 200 ×4 | 100 each | **useful (scarcity)** | 24 / 0 / 7 / 0 results. **Only new item was a thread already found.** This is the pass that made the scarcity conclusion defensible |
-| 5.8 | hn.algolia.com | `/api/v1/search?query=papermono&hitsPerPage=50` | — | curl | 200 | 9 hits | **useful** | 2 real submissions; the rest false positives (fonts, "Papermoon") |
-| 5.9 | hn.algolia.com | `/api/v1/search?query="M5Paper"&hitsPerPage=50` | — | curl | 200 | 42 hits | **useful (context)** | Historical HN interest in the line, 2020–2021 |
-| 5.10 | hn.algolia.com | `/api/v1/items/49468593` | — | curl | 200 | **full nested tree, 58 comments in one request** | **useful** | → S68. Also surfaced the two X URLs |
-| 5.11 | api.fxtwitter.com | `/M5Stack/status/2091116748686922069` | — | Chrome | 200 | full JSON | **useful** | → S74. Vendor restock statement, verbatim |
-| 5.12 | api.fxtwitter.com | `/henry19840301/status/2090652363434647738` | — | Chrome | 200 | full JSON | **useful** | → S72 |
-| 5.13 | api.fxtwitter.com | `/i/status/2091105450494238837` (chain parent) | — | Chrome | 200 | full JSON | **useful** | → S73. **This is the fetch that disproved the "e-ink driver IC" attribution** |
-| 5.14 | api.fxtwitter.com | `/i/status/2091070115001315474` (chain root) | — | Chrome | 200 | full JSON | **useful** | → S75 |
-| 5.15 | x.com | `/M5Stack/status/…`, `/henry19840301/status/…` direct | — | Chrome | 200 | 132 / 188 KB | **rejected** | Gzipped JS shell; `grep` reports "binary file matches". Superseded by 5.11–5.14 |
-| 5.16 | community.m5stack.com | `/api/search?term=papermono&in=titlesposts` | — | Chrome | **401** | — | **inaccessible** | `{"code":"not-authorised"}` |
-| 5.17 | community.m5stack.com | `/search?term=papermono` | — | Chrome | **302** | — | **inaccessible** | Redirects to login |
-| 5.18 | community.m5stack.com | `/api/recent` | — | Chrome | 200 | 198 topics | **negative-confirmed (narrow)** | Open, and no PaperMono topic in the recent window. **A window is not a search** — → S85 |
-| 5.19 | public.api.bsky.app | `/xrpc/app.bsky.feed.searchPosts?q=papermono&limit=50` | — | curl, Chrome, WhatsApp | **403** ×3 | — | **inaccessible** | → S86. No working UA found |
-
-## Pass 6 — retailers and distributors
-
-Seed list: the 37 domains extracted from `m5stack.com/distributor` (2.12).
-
-| # | Seller | Exact query | UA | HTTP | Disposition | Result |
-|---|---|---|---|---|---|---|
-| 6.1 | shop.m5stack.com | see pass 2 | curl | 200 | **useful** | USD 65.00 / 55.00, both out of stock |
-| 6.2 | openelab.de | `/search/suggest.json?q=papermono` | Chrome | 200 | **useful** | EUR 79.95, "Vorverkauf" |
-| 6.3 | openelab.io | `/search/suggest.json?q=papermono` | Chrome | 200 | **useful** | EUR 79.95, "Pre-sale" |
-| 6.4 | openelab.{io,de} | `/products/….json` | Chrome | 200 ×2 | **useful** | SKU `M5-C153`, barcode, listing timestamps → S54, S55 |
-| 6.5 | thepihut.com | `/search/suggest.json?q=papermono` | Chrome | 200 | **useful** | GBP 62.40, `available:false` |
-| 6.6 | thepihut.com | `/products/m5stack-papermono` + `.json` | Chrome | 200 ×2 | **useful** | `schema.org/OutOfStock`; incl./excl. VAT toggle confirmed in markup → S53 |
-| 6.7 | **amazon.com** | `/s?k=m5stack+papermono` | Chrome **+ `--compressed`** | 200 | **negative-confirmed** | "5 results", none is PaperMono → S57. **The first attempt, without `--compressed`, returned raw gzip and was nearly misread as a block** |
-| 6.8 | amazon.com | `/s?k=m5stack+m5paper` (control) | Chrome | 200 | **rejected** | 1 330-byte stub — rate-limited on the second consecutive query |
-| 6.9 | **aliexpress.com** | `/w/wholesale-papermono.html` | Chrome | 200 | **negative-confirmed** | Only M5Stack **PaperColor** ($127.91 / $182.87). → S58 |
-| 6.10 | aliexpress.com | `/w/wholesale-m5stack%20paper%20mono.html` | Chrome | 200 | **rejected** | 50 titles, all unrelated commodity parts — the query broke into noise |
-| 6.11 | **switch-science.com** | `/search?q=PaperMono` | Chrome | 200 | **negative-confirmed** | 「PaperMono」の検索結果**0件** → S59 |
-| 6.12 | switch-science.com | `/search/suggest.json?q=PaperMono` | Chrome | **417** | **inaccessible** | Expectation Failed; the HTML path works instead |
-| 6.13 | **adafruit.com** | `/?q=papermono` | Chrome | 200 | **negative-confirmed** | "No products found for 'papermono'" → S60 |
-| 6.14 | **reichelt.com** | `/index.html?ACTION=446&SEARCH=papermono` | Chrome | 200 | **negative-confirmed** | "Die Suche nach papermono hatte 0 Treffer" → S61 |
-| 6.15 | **botland.store** | `/search?controller=search&s=papermono` | Chrome | 200 | **negative-confirmed** | 20 string matches, all locale-switch URL echoes; **0 products** → S62 |
-| 6.16 | **core-electronics.com.au** | `/catalogsearch/result/?q=papermono` | Chrome | 200 | **negative-confirmed** | 0 products → S63 |
-| 6.17 | mouser.com | `/c/?q=papermono` | Chrome | 200 (13.9 KB) | **inaccessible** | Bot-denial page, 0 content matches → S64 |
-| 6.18 | digikey.com | `/en/products/filter/keyword?keywords=papermono` | Chrome | **403** | **inaccessible** | → S65 |
-| 6.19 | tinytronics.nl | `/en/search?query=papermono`, `/search/suggest.json` | Chrome | **403** ×2 | **inaccessible** | → S66 |
-| 6.20 | robu.in | `/search/suggest.json?q=papermono` | Chrome | **403** | **inaccessible** | → S67 |
-| 6.21 | makerlab-electronics.com | `/search/suggest.json?q=papermono` | Chrome | 200 | **negative-confirmed** | 0 products |
-| 6.22 | elektor.com | `/search/suggest.json?q=papermono` | Chrome | 200 | **negative-confirmed** | 0 products |
-| 6.23 | berrybase.de | `/search?sSearch=papermono` | Chrome | 200 (8 MB) | **negative-confirmed** | 0 occurrences of the term in 8 MB of markup |
-| 6.24 | core-electronics, botland, cytron, berrybase, mchobby | `/search/suggest.json` | Chrome | **404** ×5 | *note* | Not Shopify, or the endpoint is disabled — use each site's native search path |
-
-### Competitor pricing (for the comparison sections)
-
-| # | Service | Query | HTTP | Disposition | Result |
-|---|---|---|---|---|---|
-| 6.25 | soldered.com | `/search/suggest.json?q=inkplate`; `/products/inkplate-5-gen2.json` | 200 ×2 | **useful** | EUR confirmed from `Shopify.currency`. **Two variants** — board EUR 74.95, **with enclosure + battery EUR 99.95**; the bundle is the fair comparator against an enclosed device |
-| 6.26 | lilygo.cc | `/search/suggest.json?q={t5,epaper}`; three `/products/….json` | 200 ×5 | **useful** | Per-variant LoRa band / GPS / region SKUs. `suggest.json`'s `price` is `price_min` and **understates the real range** |
-| 6.27 | lilygo.cc | `/cart.js`, homepage, product page — currency probe | 301 / 200 | **inconclusive** | **No currency token in any fetched markup.** Recorded as "currency unconfirmed" rather than assumed USD |
-| 6.28 | internal knowledge base | `devices/soldered-electronics/inkplate-5{,-gen2}`, `devices/zerowriter/zerowriter-ink`, `devices/nicolai-electronics/tanmatsu` | — | **useful** | Cited as internal cross-links; not re-researched |
-| 6.29 | internal knowledge base | `devices/waveshare/` | — | **gap** | Existing records cover ESP32-P4/S3 **LCD** boards only, not the e-paper line. A same-diagonal Waveshare 3.97″ ESP32-S3 e-paper board demonstrably exists (r/eink, 2026-06-06) and is unpriced here |
-
-## Pass 7 — press, video and third-party code
-
-| # | Service | Exact query | Filters | HTTP | Depth | Disposition | Result |
-|---|---|---|---|---|---|---|---|
-| 7.1 | cnx-software.com | `/wp-json/wp/v2/search?search=papermono&per_page=20` | — | 200 | 1 hit | **useful** | Post id 175726 |
-| 7.2 | cnx-software.com | `/wp-json/wp/v2/posts/175726` | — | 200 | full content | **useful** | `date` 2026-08-21T16:43:25, `modified` 08-22 → S77 |
-| 7.3 | cnx-software.com | `/?s=papermono` (HTML) | — | 200 | 1 result | **duplicate** | Same article; the API path is strictly better |
-| 7.4 | **hackaday.com** | `/wp-json/wp/v2/search?search=papermono&per_page=20` | — | 200 | **`[]`** | **negative-confirmed** | **Hackaday published nothing** → S84 |
-| 7.5 | hackaday.com | `/wp-json/wp/v2/search?search=m5paper` | — | 200 | 2+ hits | **useful (context)** | 2021 weather display; 2026-07-21 "20 FPS on E-Paper Display Without Help" |
-| 7.6 | hackster.io | `/search?q=papermono` | — | 200 (69 KB) | **inaccessible** | JS shell; all 11 term matches are login-redirect URLs |
-| 7.7 | hackster.io | `/search.json?q=papermono`, `/api/v2/projects?search=papermono` | — | 200 / 404 | **inaccessible** | Both return HTML, not JSON. **No working path found** → S87 |
-| 7.8 | youtube.com | `/results?search_query=M5Stack+PaperMono&sp=CAI%3D` | **sort: newest** | 200 | 20 videos | **useful** | Parsed `ytInitialData` for titles, channels, dates, view counts |
-| 7.9 | youtube.com | `/watch?v=…` × 6 (`sRlGOgX9KOA`, `0-qQ0y-WEek`, `gX4cTpS2gUA`, `zTieK3pia6M`, `oPbOK90aJEo`, `cEkv_CP2SlU`) | — | 200 ×6 | full | **useful** | Exact `uploadDate`, `viewCount`, `shortDescription`. **Revealed the `?ref=` affiliate parameter in the only hands-on video** → S80–S82 |
-| 7.10 | **mojeek.com** | `/search?q=papermono` | pages 1–5 | 200 | "243 results" | **useful** | → S88. **The only general web engine that worked.** Pages 2–5 were almost entirely Tux Machines re-syndication → **rejected** |
-| 7.11 | html.duckduckgo.com | `/html/?q=papermono+m5stack` | — | **202** | 14 KB | **inaccessible** | Anomaly/challenge page. **Not a 403 — easy to mistake for success** |
-| 7.12 | lite.duckduckgo.com | `/lite/?q="PaperMono"+review` | — | **202** | 14 KB | **inaccessible** | Same |
-| 7.13 | search.marginalia.nu | `/search?query=papermono` | — | 200 | — | **inaccessible** | Bot-wait interstitial with a 5 s JS redirect. Unusable without JS |
-| 7.14 | **linuxgizmos.com** | article URL | — | Chrome **403** → curl/8.5.0 **200** | full | **useful** | → S76. **Inverted UA behaviour** |
-| 7.15 | liliputing.com | `/lilbits-more-phone-sized-e-ink-gadgets/` | — | 200 | full | **useful** | → S79. Contains the $55/NFC/LoRa conflation |
-| 7.16 | muylinux.xyz | article URL | — | 200 | full | **useful** | → S78 |
-| 7.17 | news.tuxmachines.org | ≥6 URLs surfaced by 7.10 | — | — | — | **rejected** | Verbatim aggregator re-syndication. Adds nothing; inflates counts |
-| 7.18 | api.github.com | `/search/repositories?q=papermono&per_page=50` | — | 200 | 6 hits | **useful** | 4 third-party + 1 M5Stack + 1 unrelated font |
-| 7.19 | api.github.com | `/search/repositories?q=M5PaperMono` | — | 200 | 3 hits | **useful** | Adds `hectorzin/M5PaperMono-HomeAssistant-ESPHome` → S93 |
-| 7.20 | api.github.com | `/search/repositories?q=paper+mono` | — | 200 | **311 hits** | **rejected** | Dominated by "monocular … paper" ML repos. **Query too loose** — the spaced form that rescues a Reddit search ruins a GitHub one |
-| 7.21 | api.github.com | `/search/code?q=PaperMono+in:file+-org:m5stack&per_page=30` | excl. `org:m5stack` | 200 | 1 196 hits, **15 read** | **useful** | Found S90, S94, S96. Many false positives from the "Paper Mono" *font* and from vendored copies of `M5Unified/…/LED_PaperMono_Class.*` |
-| 7.22 | api.github.com | `/search/code?q=PaperMono+repo:bitbank2/bb_epaper` | — | 200 | **0** | **negative-confirmed** | → S97. **Contradicts the author's public 2026-08-17 support claim.** Left unresolved |
-| 7.23 | raw.githubusercontent.com | `README.md` × 4 third-party repos | — | 200 ×4 | full | **useful** | Hardware-validation claims; `EggUncle`'s honest "not a device photo" disclaimer |
-| 7.24 | raw.githubusercontent.com | `Free-Ink/freeink-sdk/…/PaperMonoBoard.h` | — | 200 | full | **useful** | → S90. Strongest code-level third-party hardware evidence — **but fetched without pinning a ref** |
-| 7.25 | raw.githubusercontent.com | `crosspoint-reader/…/ROADMAP.md` | — | 200 | full | **useful** | → S94. Line 40 is a roadmap target, not shipped support |
-| 7.26 | raw.githubusercontent.com | `bitbank2/bb_epaper/README.md` | — | 200 | full | **negative-confirmed** | 0 matches for `papermono`, `paper mono`, `papercolor` |
-| 7.27 | freeink.org | `/` | — | 200 | 964 B | **rejected** | JS-only shell; the GitHub org is the usable source |
-
-## Dead links and recovery attempts
-
-| Target | What happened | Recovery attempted | Outcome |
-|---|---|---|---|
-| `docs.m5stack.com/en/core/Paper` | **404** — the original M5Paper has no page at this slug | Tried `/en/core/{papermono_lite,PaperMonoLite}` and the lower-case forms to establish the site's slug rules; queried the store instead | The store carries `K049` and `K049-B` listings, so the product is documented commercially but **not** at that docs slug. Left as `dead`; the docs page for the original M5Paper was **not** located |
-| `shop.m5stack.com/products/{papermono, papermono-lite, m5stack-papermono}` | **404** ×3 | Recovered via `/search?q=papermono` (2.2) | **Recovered.** The real handles are `m5papermono-with-lora-nfc-800x480-3-97-eink-display` and `papermono-lite-dev-kit-800x480-3-97-e-ink-display` |
-| `old.reddit.com/r/eink_displays/…` | **302** — subreddit does not exist or was renamed | Searched r/eink, r/esp32, r/ereader, r/CrossPointReader, r/einkesp32 instead | **Superseded**, not recovered. The renamed target was not identified |
-| `burner.m5stack.com/firmware/<id>/` | 200 but content-free React shell | Read the SPA bundle to find the API; then `/api/firmwares/{id}` → 401; then `/api/v1/firmwares/{id}` → 200 | **Recovered in full** |
-| `x.com/<user>/status/<id>` | 200 but a gzipped JS shell | `api.fxtwitter.com` | **Recovered in full**, including the reply chain |
-| `www.hackster.io/search?q=papermono` | 200 but a JS shell; `/search.json` and `/api/v2/projects` both return HTML | Three paths tried | **Not recovered.** No working path found |
-| `public.api.bsky.app/xrpc/…` | 403 to three UAs | Full ladder | **Not recovered.** One post is known only second-hand, from an embed inside S79 |
-| `community.m5stack.com` search | 401 / 302 | `/api/recent` | **Partially recovered** — a 198-topic recent window, which is not a search |
-
-**No Wayback submissions were made, and none were needed.** Every source in this
-pass is a live, well-mirrored commercial, vendor or aggregator site; none meets
-the "few copies online / fragile host" bar for archiving. The vendor's own PDF
-assets on `m5stack-doc.oss-cn-shenzhen.aliyuncs.com` are the closest call — they
-sit on a single CDN under numeric asset-folder ids that will be reused — and
-submitting **S14, S16, S25, S26 and S27–S28** to `web.archive.org/save/` is a
-reasonable next action for a future pass, particularly S16 and S27–S28, which
-have not been retrieved here at all.
-
-## Retrieval findings worth reusing
-
-These generalise beyond this device. They belong in
-[`ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md) as
-well as here.
-
-**Paths that work where the obvious one does not**
-
-- **`api.fxtwitter.com/i/status/<id>` returns complete tweet JSON** — text,
-  author, `created_at`, likes/views, and `replying_to_status` for chain-walking —
-  where `x.com/<user>/status/<id>` serves a gzipped JS shell that `grep` reports
-  as "binary file matches". The `/i/` form resolves a bare status id **without
-  knowing the author handle**, which is what made it possible to walk from a
-  quoted tweet up to its parent and root. That is exactly how the "e-ink driver
-  IC shortage" claim was checked and found to be absent from the chain it cited.
-  Chrome UA.
-- **`burner.m5stack.com/api/v1/firmwares/{id}` is public; `/api/firmwares/{id}`
-  is auth-walled** (`401 {"msg":"请先登录"}`). The version-neutral path looks like
-  the canonical one and is the wrong one. `…/versions` and
-  `…/versions/{vid}/download` follow the same rule; the download 302s to a
-  numeric CDN object whose name is **not** the `binFileName` the API reports.
-- **`old.reddit.com/search.json` with UA `WhatsApp/2.23.20.0` works where
-  `www.reddit.com` returns 403.** Re-confirmed in this session.
-- **`hn.algolia.com/api/v1/items/<id>` returns the entire nested comment tree in
-  one unauthenticated request.** No UA needed.
-- **WordPress `/wp-json/wp/v2/search` + `/posts/<id>`** is open on both
-  `cnx-software.com` and `hackaday.com`, gives `date`, `modified` and full
-  rendered content, and yields *machine-readable negatives* — an empty `[]` is a
-  far stronger statement than an empty-looking search page.
-- **Shopify storefronts leak more than they render.** `/products/<handle>.json`,
-  `/search/suggest.json` and `/blogs/news.atom` are open on most Shopify stores
-  and give `sku`, `price`, `created_at`, `published_at`. Additionally, stores
-  running the **Stoq / RestockRocket** app embed
-  `window._RestockRocketConfig.variantsInventoryQuantity` and
-  `variantsInventoryPolicy` **directly in the product page HTML** — exact
-  per-variant on-hand counts including negatives. That is where the `−129` came
-  from. **`/search/suggest.json` is not universal**: 404 on non-Shopify stores,
-  403 on some, and `price` there is `price_min`, which understates a multi-variant
-  range.
-- **`mojeek.com/search?q=` was the only general web search engine that worked**
-  (Chrome UA) while DuckDuckGo HTML *and* Lite returned **HTTP 202** challenge
-  pages and Marginalia served a JS bot-wait interstitial. Read the URLs, not the
-  result count — aggregator re-syndication inflated it fivefold here.
-
-**Gotchas that will cost you an hour**
-
-- **`linuxgizmos.com` inverts the usual ladder: bare `curl/8.5.0` → 200, Chrome
-  131 → 403.** The browser UA is not always the safe default. Always try the
-  plain agent before concluding a site is hostile.
-- **Reddit tokenises `papermono` and `paper mono` differently.** `papermono`
-  returned **0** results in r/M5Stack while `paper mono` returned the two real
-  threads. **Search both the closed-up and spaced spellings of any compound
-  product name, in every subreddit.** The opposite holds on GitHub, where the
-  spaced form (`paper mono`) returned 311 mostly-irrelevant hits.
-- **`amazon.com/s?k=` needs `curl --compressed`.** Without it curl returns raw
-  gzip that looks like binary garbage and reads exactly like a bot-block. Amazon
-  was never blocking. It *does* rate-limit the second consecutive query to a
-  ~1.3 KB stub, so budget one query per session.
-- **`datasheet.lcsc.com` returns HTTP 200 with `Content-Type: text/html` for PDF
-  URLs.** Status and content-type both lie. **Check the first bytes for `%PDF`**,
-  not the response metadata — the same discipline applied to the firmware images
-  here, which were checked for the ESP32 magic byte `0xE9` before being given a
-  `.bin` extension.
-- **`community.m5stack.com` (NodeBB) search is auth-walled**: `/api/search` →
-  401, `/search?term=` → 302. `/api/recent` is open and is the only usable
-  window, but a recent-topics window is not a search.
-- **`hackster.io` has no working machine path.** `/search?q=` is a JS shell;
-  `/search.json` and `/api/v2/projects` return HTML with a JSON-looking URL.
-- **`switch-science.com/search/suggest.json` returns HTTP 417.** The plain HTML
-  search works and states result counts in words (「…の検索結果0件」), which is
-  better evidence than an empty array.
-- **`public.api.bsky.app` 403s every UA tried**, which contradicts a ✓ for
-  Bluesky in the access table — that ✓ evidently refers to `bsky.app` HTML, not
-  the public XRPC API.
-- **Byte-length equality is not content equality.** Three Shopify 404s came back
-  at exactly 389 759 bytes with three different hashes.
-- **GitHub rate limits are per identity, and no UA helps.** Use
-  `gh api` / `Authorization: Bearer $(gh auth token)` — 60/h becomes 5 000/h.
-  A 403 carrying `X-RateLimit-Remaining: 0` looks exactly like bot-blocking;
-  check the header before rotating agents.
-
-## Not attempted, and why
-
-| Target | Reason | Expected yield |
-|---|---|---|
-| FCC / IC / CE grantee databases | S11 establishes only that *M5Stack* publishes nothing. A grantee search by company name is the obvious next step and was not run | **High.** The device carries a wideband 868–923 MHz radio on a single SKU |
-| The 14 Arduino API sub-pages (`battery`, `display`, `nfc`, `lora`, `wakeup`, …) | Enumerated from S07, not fetched | Medium |
-| `PaperMono-Lite_PRJ_V0.6.2_20260522.pdf` (S16) | Not fetched | **High** — it is the only way to know what the Lite's board actually omits rather than what the marketing table says |
-| zh_CN-only datasheets (S27–S30) | Not fetched | **High** for S27/S28 — the CN editions of the two M5-designed chips could settle the pin-nomenclature question at the silicon level |
-| Mouser / DigiKey product APIs | Both require API keys not available in this session | Medium — would convert two "no determination" rows into determinations |
-| Taobao (`m5stack.taobao.com`) | Listed distributor; needs CN-region handling | Medium |
-| Tom's Hardware | Nothing surfaced via Mojeek, CNX, HN, Reddit or YouTube; their on-site search is JS-driven and was not forced | Low |
-| Adafruit *blog* (`blog.adafruit.com`) | The Adafruit **store** returned a clean negative; the blog was not separately queried | Low |
-| Hackaday.io projects (distinct from hackaday.com) | Not queried | Low |
-| Google / Bing | Mojeek succeeded; further engine rotation was unnecessary | Low |
-| `web.archive.org/save` submissions | None of the community/press sources meets the scarcity bar. The vendor PDF assets arguably do — see [dead links](#dead-links-and-recovery-attempts) | Medium, deferred |
-| Anything on physical hardware | **No PaperMono exists in this session, and none could be bought — the product has been out of stock since nine minutes after launch** | — |
-
-## Stopping criterion
-
-**Stated plainly: two consecutive broad passes returned only vendor marketing
-copy, its re-syndication, and duplicates of items already held.**
-
-The second pass (5.7) was run specifically as an independent check on the first,
-using four different query formulations and a `t=year` filter across the same
-services. It produced **one** item, which had already been found. Pages 2–5 of
-the only working web search engine (7.10) were, after deduplication, entirely
-Tux Machines re-syndicating a single LinuxGizmos article that itself restates a
-single vendor blog post.
-
-What that yields, as of 2026-09-01 — eleven days after launch:
-
-- **Zero written reviews.** Not one article anywhere puts hands on the hardware.
-- **One hands-on video**, published on day 8, self-described as a first look, and
-  carrying a vendor referral link.
-- **Zero Hackaday coverage** (a machine-readable `[]`), zero reachable Hackster
-  coverage, zero Tom's Hardware coverage.
-- **Two Reddit results site-wide for `papermono`, both bot mirrors of an HN
-  post.** The only genuine Reddit discussion is two threads in the vendor's own
-  subreddit.
-- **No measured power figure exists anywhere**, vendor included.
-- No teardown, no battery-life test, no independent refresh-rate verification, no
-  LoRa range test, no NFC interoperability test.
-- **Four third-party GitHub projects and one SDK**, two with credible
-  hardware-validation evidence. **That is where the real independent signal is.**
-
-This is the expected shape for an eleven-day-old product that has been out of
-stock for all but nine minutes of its commercial life: *you cannot review
-hardware nobody can buy.* The near-total absence of independent measurement is a
-consequence of supply, not of disinterest — a 162-point HN thread and 61 590
-video views say the opposite of disinterest.
-
-**The stopping criterion is therefore about saturation, not completeness.** The
-searchable surface was exhausted; the *knowable* surface was not. Anyone
-re-running this after a restock should expect the community sections to change
-substantially and the vendor sections not to.
-
-## Query-count summary
-
-| Category | Distinct queries | useful | negative-confirmed | inaccessible | rejected / duplicate / dead |
-|---|---|---|---|---|---|
-| Vendor documentation + artifacts | 36 | 26 | 3 | 0 | 3 (+ 4 not attempted) |
-| Vendor storefront | 12 | 9 | 0 | 0 | 3 |
-| M5Burner | 8 | 7 | 0 | 1 | 0 |
-| Vendor source repositories | 9 | 6 | 3 | 0 | 0 |
-| Community / social / forum | 19 | 12 | 3 | 3 | 1 |
-| Retailers / distributors | 24 | 6 | 9 | 5 | 4 |
-| Competitor pricing | 5 | 3 | 0 | 0 | 2 (1 inconclusive, 1 gap) |
-| Press / video / code | 27 | 16 | 4 | 4 | 3 |
-| **Total** | **140** | **85** | **22** | **13** | **16** |
-
-The market/community subset of this table (94 distinct queries across 30+
-services) is the figure quoted in [`README.md`](README.md); the totals above add
-the documentation, artifact, firmware and repository passes.
-
-## Related
-
-- [`sources.md`](sources.md) — what was kept, with stable IDs
-- [`commands.md`](commands.md) — what was run, with execution status
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — what the sources disagree about
-- [`../../../ai-crawler-site-access-table.md`](../../../ai-crawler-site-access-table.md) — the durable home for the retrieval findings above
diff --git a/devices/m5stack/papermono/resources-and-conflicts.md b/devices/m5stack/papermono/resources-and-conflicts.md
deleted file mode 100644
index 0df89b8..0000000
--- a/devices/m5stack/papermono/resources-and-conflicts.md
+++ /dev/null
@@ -1,250 +0,0 @@
-# Resources and conflicts — M5Stack PaperMono
-
-> Who owns which GPIO, bus, address, SPI host, partition and rail — and what happens when
-> features run together.
-> Hardware revision **V0.6.2** · snapshot **2026-09-01**.
-> Limits are labelled **silicon** / **board** / **framework** / **observed**.
-> **Nothing here was measured on hardware.**
-
-## 1. The headline: there is no free GPIO and no expansion connector
-
-**Every usable ESP32-S3 pin on this board is committed, and there is no header of any
-kind — no Grove port, no M-Bus, no expansion connector.** That is unusual for an M5Stack
-core and it is the constraint that shapes every design decision on this product.
-
-| Disposition | Count | Pins |
-|---|---:|---|
-| E-paper (SPI2 + DC/CS/BUSY) | 5 | 14, 15, 16, 17, 18 |
-| microSD (4-bit SDMMC) | 6 | 8, 9, 10, 11, 12, 13 |
-| LoRa (SPI + BUSY + IRQ) | 6 | 5, 21, 38, 39, 40, 41 |
-| **Reserved — in-package octal PSRAM** | 5 | **33, 34, 35, 36, 37** |
-| Interrupts in (PM1, touch, NFC, IOE1) | 4 | 1, 4, 6, 7 |
-| USB (native) | 2 | 19, 20 |
-| UART0 | 2 | 43, 44 |
-| System I²C | 2 | 47, 48 |
-| PDM microphone | 2 | 45, 46 |
-| User buttons | 2 | 2, 3 |
-| Buzzer | 1 | 42 |
-| Boot strap from the M5PM1 | 1 | 0 |
-| Unconnected | 1 | 26 |
-| Do not exist on the ESP32-S3 | — | 22–25, 27–32 |
-| **Free** | **0** | **—** |
-
-**Anything you add must go on the shared I²C bus, or take over one of the M5IOE1's
-fourteen expander pins — all of which are also assigned.** There is no spare expander pin
-either. See [`features/io-expander.md` §8](features/io-expander.md#8--m5unified-already-owns-most-of-these-pins).
-
-## 2. The single I²C bus and its seven addresses
-
-**GPIO47 SDA / GPIO48 SCL, pulled up by 2.2 kΩ (`R36`, `R37`) to `3V3_L2`.** One bus,
-seven devices, no second bus anywhere on the board.
-
-| Address | Device | Speed used | Owner | Notes |
-|---|---|---|---|---|
-| `0x32` | RX8130CE RTC | 400 kHz | `M5.Rtc` | `nIRQ` → **M5PM1 `G0`** |
-| `0x38` | FT6336G touch | 400 kHz | M5GFX `Touch_FT5x06` on `I2C_NUM_1` | `INT` → GPIO4 |
-| `0x4F` | M5IOE1 expander | **100 kHz** | M5Unified + your code | Address **contradicted by its own manual** (`0x6F`–`0x76`) |
-| `0x50` | ST25R3916 NFC | 400 kHz | `M5Unit-NFC` | C153 only. Identity: reg `0x7F` == `0x05` |
-| `0x68` | BMI270 IMU | **100 kHz** | `M5.Imu` | alt `0x69`, probed. `INT1` → **M5PM1 `G4`** |
-| `0x6E` | M5PM1 power manager | **100 kHz** | `M5.Power` + your code | IRQ → GPIO1 |
-| `0x75` | IP2315 charger | 100 kHz | `M5.Power`, **gated** | **Absent from a scan unless M5IOE1 `IO11` is asserted** |
-
-All seven addresses were confirmed in **both** the vendor firmware source and the vendor
-product page; none conflict.
-
-### Bus arbitration rules that matter
-
-1. **Speed is per-transaction.** The IMU, M5PM1 and M5IOE1 are driven at 100 kHz while the
-   RTC, NFC and touch run at 400 kHz. Any master transaction sets the rate for that
-   transaction only. The FT6336G tolerates 10 kHz–400 kHz, so it is safe throughout.
-2. **The charger must be gated on, transacted with, and gated off.** Leaving it attached
-   degrades bus stability — M5Stack's words — and a low battery can leave the IP2315
-   failing to enter I²C mode and **disturbing the other six devices**. The IP2315
-   datasheet documents a bus-lockup mechanism involving a missing NACK on the final read
-   byte. M5Unified brackets every access with a 64-attempt readiness scan.
-3. **Recovery from a wedged bus is a short press of the power button** (vendor-documented),
-   which resets the device through the M5PM1.
-4. **The M5PM1's first transaction after I²C idle-sleep fails by design.** Its own
-   firmware uses that transaction to wake up. M5Stack's code calls
-   `setI2cSleepTime(0)` twice for this reason.
-5. **Losing this bus loses the display, touch, microSD, microphone, NFC, LoRa reset,
-   battery telemetry and the ability to sleep.** It is a single point of failure with no
-   redundancy.
-
-## 3. SPI — two hosts, and a naming mismatch
-
-| ESP-IDF host | Schematic net names | Device | Clock | Notes |
-|---|---|---|---|---|
-| **`SPI2_HOST`** | `G14_SPI2_MOSI`, `G15_SPI2_CLK` | E-paper SSD1677 | **40 MHz** in M5GFX, **20 MHz** in the OTP demo | 3-wire, **write-only** — no MISO. 22 Ω on SCLK (`R38`) |
-| **`SPI3_HOST`** | `G38_SPI1_MOSI`, `G39_SPI1_CLK` | Stamp LoRa-1262 | **8 MHz** | ⚠ **schematic says "SPI1", firmware opens `SPI3_HOST`** |
-| SPI0 (dedicated) | `NOR_*` | XM25UH128DHIQT flash | 80 MHz per the image header | Quad-capable; ships configured DIO |
-
-**The two hosts are genuinely independent**, so e-paper refresh and LoRa traffic do not
-contend for a bus. The `SPI1`/`SPI3_HOST` mismatch is a naming collision between M5Stack's
-schematic labels and ESP-IDF's host numbering — made confusing by the fact that the
-e-paper's `SPI2` label *does* coincide with `SPI2_HOST`.
-
-**microSD is not on SPI at all** — it is the SDMMC peripheral in 4-bit mode.
-
-> ⚠ **M5GFX drives the panel at 40 MHz.** The SSD1677 datasheet §12.1 **and** the DKE panel
-> manual p. 16 independently state a **20 MHz** maximum write clock, and the vendor's own
-> OTP demo uses 20 MHz. A 2× overclock of a rated bus limit, in the same library the
-> vendor says has refresh problems. **Unresolved, untested, and the most likely single
-> cause worth investigating first.**
-
-## 4. SDMMC
-
-| Item | Value |
-|---|---|
-| Peripheral | SDMMC host, `slot_config.width = 4` |
-| Pins | CLK 13, CMD 12, D0 11, D1 10, D2 9, D3 8 |
-| Frequency | **`SDMMC_HOST_DEFAULT()`** — the vendor does **not** override `max_freq_khz` |
-| Mount | `/sdcard`, `max_files = 8`, `allocation_unit_size = 16 KiB`, `format_if_mount_failed = false` |
-| Power | M5IOE1 `IO14` (`TF_EN`) — **left LOW by the factory HAL, driven HIGH by M5GFX** |
-| Detect | M5IOE1 `IO1` (`TF_DET`), **low = inserted**, pulled up by the card's own power domain |
-
-## 5. Memory, flash and partitions
-
-| Resource | Size | Notes |
-|---|---|---|
-| Internal SRAM | 512 KB | Shared with the Wi-Fi/BLE stacks and the display driver |
-| **PSRAM** | **8 MB octal, in package** | **Mandatory.** Consumes GPIO33–37. Without `CONFIG_SPIRAM_MODE_OCT`, M5GFX aborts display init |
-| Flash | 16 MB external NOR | Quad-capable; **ships configured DIO** |
-
-Partition table — **identical in both vendor projects**:
-
-```
-# Name,   Type, SubType, Offset,  Size,     Flags
-nvs,      data, nvs,     0x9000,  0x6000,     (24 KiB)
-phy_init, data, phy,     0xf000,  0x1000,     ( 4 KiB)
-factory,  app,  factory, 0x10000, 0xF00000,   (15 MiB)
-```
-
-- **One `factory` app at `0xF00000`. No OTA slot. No SPIFFS, no FATFS-in-flash, no
-  coredump partition.** The shipped firmware is **not field-updatable over the air**.
-- ~960 KB of flash above the app is unallocated and unused.
-- The third-party CrossPoint image repartitions entirely (6400 KB app, 4096 KB `cjkfont`,
-  SPIFFS, coredump) — proof this is a firmware choice, not a hardware constraint.
-
-## 6. Timers, PWM and DMA
-
-| Resource | Total | Used by the board | Left |
-|---|---:|---|---|
-| **LEDC timers** | 4 | **`LEDC_TIMER_3`** — buzzer | 3 |
-| **LEDC channels** | 8 low-speed | **`LEDC_CHANNEL_7`** — buzzer | 7 |
-| I²S | 2 | **`I2S_NUM_0`** — PDM microphone RX | `I2S_NUM_1`, which **cannot do PDM RX** (silicon) |
-| GDMA | 5 in / 5 out | E-paper SPI, SDMMC, I²S, Wi-Fi | Tight under a display + SD + Wi-Fi load. **Unmeasured** |
-| **M5PM1 PWM** | 2 channels, **one shared frequency register** | PWM0 → frontlight, 5 kHz | PWM1 free, but forced to the same frequency |
-| **M5IOE1 PWM** | 4 channels, **one shared frequency register** | PWM2 → LED green, PWM1 → LED blue, 5 kHz | PWM3 (`IO11`) and PWM4 (`IO10`) are used as digital lines |
-| M5IOE1 ADC | 4 channels | none — `IO2`/`IO4`/`IO5`/`IO7` are all digital or `ADD_SET` | all four, if you repurpose a pin you cannot spare |
-| RMT / PCNT / MCPWM / TWAI | full | 0 | Available in silicon, **pin-starved to the point of uselessness** |
-
-**The buzzer's timer 3 / channel 7 allocation is deliberate** — top of the range, so
-user code allocating from 0 upward does not collide. Keep the convention.
-
-## 7. Interrupts
-
-| Line | To | Used? |
-|---|---|---|
-| M5PM1 IRQ (`G1`) | ESP32-S3 **GPIO1** | ✅ M5Unified configures it; the wake path uses it |
-| Touch `INT` | ESP32-S3 **GPIO4** | ✅ M5GFX; also the touch-wake EXT0 pin |
-| NFC `IRQ` | ESP32-S3 **GPIO6** | ❌ **unused** — the vendor scan app sets `using_irq = false` |
-| M5IOE1 `OD_INTOUT` | ESP32-S3 **GPIO7** | ❌ **unused** — the firmware polls (`M5IOE1_INT_MODE_DISABLED`) |
-| LoRa `DIO1` | ESP32-S3 **GPIO5** | ✅ RadioLib, `GPIO_INTR_POSEDGE` |
-| RTC `nIRQ` | **M5PM1 `G0`** | ✅ as a wake source |
-| IMU `INT1` | **M5PM1 `G4`** | ✅ as a wake source, **falling edge / active-low** |
-
-**Two of seven interrupt lines are wired and never used by any vendor code.** The GPIO7
-expander interrupt in particular is unproven on this board, and `INT_OUT` is open-drain
-and needs a pull-up.
-
-**M5IOE1 interrupt exclusion pairs** — interrupts cannot be enabled simultaneously
-within a pair: `IO1&IO6` · `IO2&IO3` · `IO7&IO12` · `IO8&IO9` · `IO10&IO14` ·
-`IO11&IO13`. **Four of those six pairs straddle live PaperMono signals**: SD detect vs
-touch reset, LoRa antenna switch vs e-paper rail, LoRa reset vs SD power, charger gate vs
-touch power.
-
-## 8. Power rails and their owners
-
-| Rail | Source | Enable owner | Feeds | State |
-|---|---|---|---|---|
-| `VUSB_IN` | USB-C | — | input only | — |
-| `VBUS_L0` | battery bus after protection | — | everything downstream | L0 |
-| `3V3_L0` | `U4` SSP7615-33DFR, 400 mA | always on (`inferred`) | M5PM1, always-on logic | L0 |
-| `3V3_L1` | `U6` SSP7615-33DFR, 400 mA | **M5PM1 `LDO3V3_EN_PP`** | **RTC, IMU** | L1 |
-| `3V3_L2` | `U10` JW5712 DC-DC, 600 mA | **M5PM1 `DCDC3V3_EN_PP`** | ESP32-S3, I²C pull-ups, keys, NFC sub-board | L2 |
-| `3V3_L2_LoRa` | `U9` SSP7615-33DFR, 400 mA | **M5PM1 `G2`** | Stamp LoRa-1262 | L2 |
-| `EPD_3V3_L3B` | `U5` SSP7615-33DFR, 400 mA | **M5IOE1 `IO3`** | e-paper panel | L3 |
-| `BL_15V_L3B` | `U11` AW9967 boost | **M5PM1 `G3`** (PWM) | frontlight | L3B |
-| `TF_3V3_L3B` | `U8` AW35122 switch | **M5IOE1 `IO14`** | microSD | L3B |
-| `TP_VDD` | `U18` AW35122 switch | **M5IOE1 `IO13`** | touch controller | L3B |
-| `PDM_VDD` | `U21` AW35122 switch | **M5IOE1 `IO12`** | microphone | L3B |
-| `VDD_NOR` | from `3V3_L2` | — | SPI NOR flash | L2 |
-
-**Every switched LDO carries a 1 MΩ pulldown on its enable** (`R24`, `R26`, `R23`), so
-every optional rail defaults **off** on cold power-up. A blank screen is the expected
-result of forgetting to bring up `EPD_3V3_L3B`.
-
-**Ownership summary:** the M5PM1 owns L0/L1/L2 and the frontlight; the M5IOE1 owns every
-L3B switch except the frontlight. **The ESP32-S3 owns none of its own power.**
-
-Current budget: the largest regulator is the 600 mA `3V3_L2` DC-DC feeding the SoC.
-**No current figure exists for any consumer**, so no meaningful budget can be drawn up.
-That is a gap, not an omission.
-
-## 9. Boot straps
-
-| GPIO | Strap function | Also carries | Risk |
-|---|---|---|---|
-| **GPIO0** | boot mode | **M5PM1 `BOOT_OUT_OD`** | By design — the power manager, not a button, selects download mode |
-| **GPIO3** | strapping | **User button B** | Holding B across reset perturbs the strap |
-| **GPIO45** | `VDD_SPI` select | **PDM mic clock** | Driven by the ESP32-S3 itself |
-| **GPIO46** | boot-message routing | **PDM mic data** | Driven by the microphone; state depends on whether `PDM_VDD` is up |
-
-`CHIP_PU` carries `SOC_RESET` from the M5PM1. **The application processor cannot reset
-itself independently of the power manager.** No vendor firmware guards the GPIO3/45/46
-strap exposure; `inferred`, `not-tested`.
-
-## 10. Realistic simultaneous-use scenarios
-
-Features are evaluated in combination, not in isolation. **None of these has been run.**
-
-| Combination | Verdict | Mechanism and what would actually bite |
-|---|---|---|
-| **E-paper refresh + microSD + Wi-Fi, concurrently** | ⚠ **untested, and the case most worth testing** | **No pin conflict at all** — GPIO14–18, GPIO8–13 and an internal radio. The pressure is elsewhere: (a) **GDMA** — a full refresh is up to ~4.7 s of SPI DMA, SDMMC is a second client, Wi-Fi a third; (b) **PSRAM bandwidth** — the display framebuffers live in octal PSRAM and Wi-Fi buffers compete for internal SRAM; (c) **the `3V3_L2` 600 mA rail and the battery** carry a Wi-Fi TX burst on top of an SD write burst with no published figure for either. Also note the whole L3B group comes up together, so you cannot power-manage the card independently of the panel without expander writes. **Nobody has demonstrated this.** |
-| **LoRa + Wi-Fi** | ✅ **they do not share a radio — say it plainly** | LoRa is **sub-GHz, 868–923 MHz**, on a physically separate SX1262 module with its own FPC antenna, reached over `SPI3_HOST`. Wi-Fi and BLE are **2.4 GHz** inside the ESP32-S3 die. Different bands, different antennas, different peripherals, **no coexistence scheduling required**. What they share is CPU time and the battery. (Wi-Fi and **BLE** *do* share one 2.4 GHz radio and are time-sliced — that is the pair that needs coexistence care, not LoRa.) |
-| **NFC + charger, both on the shared I²C bus** | ⚠ **the genuinely risky pair** | Both are on the **one** bus. NFC polling is sustained and chatty — the vendor app runs 180 ms detect calls with 60 ms gaps across 3500 ms windows for type A — and gating the IP2315 onto the bus is **the one documented bus-stability hazard on this board**, worse still at low battery. **Do not open the charger gate inside an NFC scan window.** Batch charger reads between scans and close the gate immediately. If the bus wedges, the documented recovery is a short press of the power button, i.e. a reset |
-| **Microphone on GPIO45/46, which are strapping pins** | ⚠ **board-level hazard, unguarded** | GPIO45 selects `VDD_SPI` voltage and GPIO46 routes boot messages. The mic's output stage sits on GPIO46 and its state at reset depends on whether `PDM_VDD` is up — which is an expander-controlled rail that firmware may or may not have left asserted. The factory firmware calls `gpio_reset_pin()` on both and floats GPIO46 before reconfiguring, which is the right defensive move, but **nothing guards the reset path itself**. `inferred`, `not-tested` |
-| Display + touch | ✅ intended | M5GFX resets both together on `IO5`/`IO6` |
-| Display + LoRa | ✅ | Separate SPI hosts |
-| Display + frontlight | ✅ | Different chips — and the `PYG3` ambiguity is the only real hazard |
-| Sleep + microSD mounted | ⚠ **unmount first** | The card rail is L3B; dropping it under an open file is a corruption path |
-| Sleep + RTC or IMU wake | ✅ down to **L1** | The intended low-power pattern; requires `ldoSetPowerHold(true)` |
-| Sleep + touch wake | ✅ only in **L2** | Touch does not reach the M5PM1 |
-| Touch wake + M5PM1 IRQ wake, one call | ❌ | `M5.Power.deepSleep(us, touch_wakeup=true)` **substitutes** GPIO4 for GPIO1 |
-| Any two M5IOE1 interrupts from one exclusion pair | ❌ | §7 |
-| Two PWM consumers wanting different frequencies on one expander | ❌ | One shared `PWM_FREQ` register per chip |
-| Buzzer + user LEDC allocation from channel 0 | ✅ | Buzzer sits at timer 3 / channel 7 |
-| Microphone + I²S playback | ❌ (moot) | PDM RX is `I2S_NUM_0`-only — **silicon**. There is no audio output on this board anyway |
-
-## 11. The three constraints that actually bite
-
-**1. There is no free GPIO and no expansion connector.** Not "few" — none, and no header
-to expose one on. Every extension has to be I²C, and the I²C bus already has seven devices
-and one documented stability hazard on it.
-
-**2. Two auxiliary microcontrollers own the board, and one naming collision can kill the
-display.** `PYG3` denotes the M5PM1's frontlight PWM *net* and the M5IOE1's e-paper-rail
-*pin*. Both are live. Writing the wrong one cuts panel power and reports nothing. Compounded
-by `M5IOE1_PIN_3 = 2`. See
-[`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md).
-
-**3. Octal PSRAM is mandatory and its absence looks like dead hardware.** M5GFX identifies
-the board, then silently declines to bring up the panel, logging one line that the
-vendor's own `CORE_DEBUG_LEVEL=0` compiles out.
-
-## Related
-
-- [`pinouts-and-buses.md`](pinouts-and-buses.md) — the underlying pin map and connector table
-- [`power-architecture.md`](power-architecture.md) — rails, states and wake sources in full
-- [`coverage.md`](coverage.md) · [`compatibility-and-status.md`](compatibility-and-status.md) · [`features/README.md`](features/README.md) · [`gaps-and-conflicts.md`](gaps-and-conflicts.md)
diff --git a/devices/m5stack/papermono/sources.md b/devices/m5stack/papermono/sources.md
deleted file mode 100644
index a1081c3..0000000
--- a/devices/m5stack/papermono/sources.md
+++ /dev/null
@@ -1,220 +0,0 @@
-# PaperMono — source table
-
-> Research snapshot **2026-09-01**. Every retrieval in this table was performed on
-> **2026-09-01 (UTC)**. Nothing here was verified against physical hardware.
-> Companion documents: [`research-log.md`](research-log.md) (what was searched and
-> how), [`commands.md`](commands.md) (what was run),
-> [`gaps-and-conflicts.md`](gaps-and-conflicts.md) (what disagrees).
-
-Other documents in this record cite these rows by ID (`S01`, `S02`, …). IDs are
-stable; if a source is later superseded, add a new row rather than editing an old
-one.
-
-## How to read the columns
-
-| Column | Meaning |
-|---|---|
-| **Class** | `primary` — published by the party responsible for the thing described. `authorized mirror` — a copy the originating vendor's partner/customer is entitled to serve, byte-faithful. `credible mirror` — a copy hosted by a third party, genuine but possibly stale or re-processed. `standard` — a specification body's document. `community` — third-party writing, code or discussion. |
-| **Published/updated** | The **document's own** version and date, not the retrieval date. `unknown` where the document does not state one. Where a mirror is behind the originator, both revisions are given. |
-| **Local path** | Path **as this repository sees it**, from the repo root. `scratch/…` is the working store (a symlink into `../repo-archive/scratch/hardware-doc`); it is not guaranteed to survive, and anything load-bearing has been copied into `devices/` or `components/`. |
-
-Three classes of row are deliberately present and are **results, not failures**:
-
-- **Verified negatives** (S11, S12, S45, S57–S63, S84, S97) — a page that
-  successfully returned content and did *not* contain the product establishes an
-  absence. That is a source.
-- **Inaccessible** (S64–S66, S85, S86, S87) — retrieved a bot-wall or auth-wall.
-  No determination is possible; recorded so the next pass does not mistake the
-  gap for a negative.
-- **Recorded but not retrieved** (S16, S17, S27–S30, S40) — the URL is known and
-  the artifact was not fetched in this pass. These are the highest-value untaken
-  leads.
-
----
-
-## Vendor documentation — `docs.m5stack.com`
-
-All thirteen pages returned HTTP 200 to a **first** request with a Chrome 131
-User-Agent; no fallback was needed. Byte sizes and hashes are over the decoded
-on-disk file.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **S01** | PaperMono product page (EN) | M5Stack Technology Co., Ltd | primary | HTML product page | <https://docs.m5stack.com/en/core/PaperMono> | 2026-09-01 | page dated **2026-08-20** in `/en/history`; no page version string | Full specification table, PinMap for every subsystem, M5GFX refresh timings, the PlatformIO `[env:m5stack-papermono]` block, every asset URL, download-mode procedure, e-paper precautions | 153 939 B, `1f442a2295bcd4f0…`. Marketing copy, `not-tested`. Uses the ambiguous `PYG<n>` notation throughout — see [`pin-naming-and-the-pyg-ambiguity.md`](pin-naming-and-the-pyg-ambiguity.md). Omits USB and UART0 pins, M5IOE1 `PYG4` and `PYG7` | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono.{html,txt,meta}`; also `scratch/m5stack-papermono/raw/docs-papermono-en.{html,txt}` |
-| **S02** | PaperMono product page (zh_CN) | M5Stack | primary | HTML product page | <https://docs.m5stack.com/zh_CN/core/PaperMono> | 2026-09-01 | unknown (no version string) | Translation delta baseline; **links Chinese-language M5PM1, M5IOE1, ST25R3916 and ESP32-S3 datasheets that the EN page does not** | 152 668 B, `deb7fbc83bcc25df…`. Table-row count, pin tokens and numeric specs are identical to S01; the only substantive delta is the datasheet language | `scratch/m5stack-papermono/docs/pages/zh_CN-core-PaperMono.{html,txt,meta}` |
-| **S03** | PaperMono product page (ja) | M5Stack | primary | HTML product page | <https://docs.m5stack.com/ja/core/PaperMono> | 2026-09-01 | unknown | Translation delta baseline. **Links the EN datasheets** — there are no JA-localised datasheets | 156 234 B, `a5abd432bd6a9cc4…`. Faithfully reproduces the frontlight naming ambiguity of S01, which is evidence the defect is in the source content, not the translation | `scratch/m5stack-papermono/docs/pages/ja-core-PaperMono.{html,txt,meta}` |
-| **S04** | PaperMono-Lite product page (EN) | M5Stack | primary | HTML product page | <https://docs.m5stack.com/en/core/PaperMono-Lite> | 2026-09-01 | page dated **2026-08-20** in `/en/history` | The entire basis of [`../papermono-lite/README.md`](../papermono-lite/README.md): SKU `C153-Lite`, full spec table, PinMap without RFID/LoRa blocks, the vendor comparison table, the `PRJ` schematic asset, weights 72.4 g / 88.9 g | 151 608 B, `abf259f964c36141…`. Vendor claims, `not-tested`. Its comparison table **omits** the weight, schematic-asset and datasheet-list differences that the full spec tables reveal | `scratch/m5stack-papermono/docs/pages/en-core-PaperMono-Lite.{html,txt,meta}` |
-| **S05** | PaperMono-Lite product page (zh_CN) | M5Stack | primary | HTML product page | <https://docs.m5stack.com/zh_CN/core/PaperMono-Lite> | 2026-09-01 | unknown | Translation delta | 150 365 B, `40c56a8f1c8bcba2…`. Package-size cell reads `113.2 x 69.6 x21.0mm` (missing space) — a typo, not a spec difference | `scratch/m5stack-papermono/docs/pages/zh_CN-core-PaperMono-Lite.{html,txt,meta}` |
-| **S06** | PaperMono-Lite product page (ja) | M5Stack | primary | HTML product page | <https://docs.m5stack.com/ja/core/PaperMono-Lite> | 2026-09-01 | unknown | Translation delta | 153 791 B, `eed7616b6aa17706…` | `scratch/m5stack-papermono/docs/pages/ja-core-PaperMono-Lite.{html,txt,meta}` |
-| **S07** | PaperMono Arduino Quick Start | M5Stack | primary | HTML tutorial | <https://docs.m5stack.com/en/arduino/papermono/program> | 2026-09-01 | unknown | Arduino board name `M5PaperMono`; the seven-library install list including `M5UnitUnified`; the 14 advertised API sub-pages; download-mode wording | 321 758 B, `4f8438a55ce6c43c…`. **Specifies no build settings at all**, contradicts S01/S09 on which button enters download mode ("reset button on the side"), and names a `BarGraph` example that corresponds to no API sub-page. The 14 sub-pages were enumerated but **not fetched** in this pass | `scratch/m5stack-papermono/docs/pages/en-arduino-papermono-program.{html,txt,meta}` |
-| **S08** | PaperMono M5PM1 & M5IOE1 Power Management | M5Stack | primary | HTML tutorial | <https://docs.m5stack.com/en/arduino/papermono/m5pm1_m5ioe1> | 2026-09-01 | unknown | The **L0–L3B power tree and the explicit statement that it is not a series structure**; the M5PM1 API surface; the timer-action enum; the I²C idle-sleep trap; four verbatim sketches; the authoritative M5IOE1 pin table | 416 888 B, `7796d1a13c739e55…`. The single richest vendor page. Contains two self-contradictions: prose says the IMU interrupt is active-high while its own code says `BMI2_INT_ACTIVE_LOW`, and `PYG4` denotes two different chips' pins in two sections. **Omits `M5IOE1_PIN_11`** — the one expander pin with a published bus-stability hazard | `scratch/m5stack-papermono/docs/pages/en-arduino-papermono-m5pm1_m5ioe1.{html,txt,meta}` |
-| **S09** | PaperMono / PaperMono-Lite UiFlow2 Quick Start | M5Stack | primary | HTML tutorial | <https://docs.m5stack.com/en/uiflow2/papermono/program> | 2026-09-01 | unknown | M5Burner flashing flow; the M5Burner configuration fields (`COM`, `BaudRate`, `Server`, Wi-Fi, `SNTP0/1/2`, `Timezone`, `Boot Option`); the Access Code pairing constraints | 265 217 B, `9e4ac6d264c7051c…`. **Shared page for both SKUs.** States **no required firmware version, no block list and no limitations** — established by full-text search of the extracted page, so this is a documentation gap, not a retrieval failure | `scratch/m5stack-papermono/docs/pages/en-uiflow2-papermono-program.{html,txt,meta}` |
-| **S10** | Product index | M5Stack | primary | HTML index | <https://docs.m5stack.com/en/products> | 2026-09-01 | unknown | **Exactly two PaperMono SKUs exist**, and their mapping to store handles | 560 714 B, `c0a310817b0e46eb…`. Index only; no specifications | `scratch/m5stack-papermono/docs/pages/en-products.{html,txt,meta}`; also `scratch/m5stack-papermono/raw/docs-products-en.html` |
-| **S11** | Product Certifications | M5Stack | primary | HTML index | <https://docs.m5stack.com/en/certification> | 2026-09-01 | unknown | **Verified negative — zero matches for `PaperMono` and zero for `C153`.** No FCC, CE, IC, RCM, TELEC or MIC identifier is published for this board | 382 669 B, `6e1e65a6e6d884fd…`. HTTP 200 with full content and other products present, so the absence is real. It does **not** establish that no certification exists — only that M5Stack publishes none. An FCC grantee-database search was **not** attempted | `scratch/m5stack-papermono/docs/pages/en-certification.{html,txt,meta}` |
-| **S12** | Product I²C Address Table | M5Stack | primary | HTML reference table | <https://docs.m5stack.com/en/product_i2c_addr> | 2026-09-01 | unknown | **Verified negative — no PaperMono row**, despite the board carrying seven documented I²C devices. Partial corroboration in the other direction: the table lists `M5PM1 (0x6e)` for **StickS3 (K150)**, independently confirming the M5PM1 address | 312 908 B, `db0e2db3e87dcd09…`. Same caveat as S11: 200 with full content, so the omission is genuine | `scratch/m5stack-papermono/docs/pages/en-product_i2c_addr.{html,txt,meta}` |
-| **S13** | Release History | M5Stack | primary | HTML changelog | <https://docs.m5stack.com/en/history> | 2026-09-01 | unknown | Both products dated **2026-08-20**, category **"Controllers"** — the documentation release date, which is distinct from both the Shopify `created_at` (08-18) and `published_at` (08-21) | 137 555 B, `85bb269465428448…` | `scratch/m5stack-papermono/docs/pages/en-history.{html,txt,meta}` |
-
-## Vendor design artifacts
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **S14** | `PaperMono_SCH_V0.6.2_20260522.pdf` | M5Stack | primary | schematic (Altium PDF export) | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/PaperMono_SCH_V0.6.2_20260522.pdf> (linked from S01) | 2026-09-01 | **V0.6.2, filename-dated 2026-05-22**; PDF `CreationDate` 2026-06-08, `ModDate` 2026-07-28; sheet 5 title block dated 2026-04-14; sheet 6 rev **V0.2** dated 2026-07-28 | **The single most load-bearing source in this record.** Every pin, net, rail, passive value and designator in [`pinouts-and-buses.md`](pinouts-and-buses.md) and [`power-architecture.md`](power-architecture.md); the resolution of the `PYG` ambiguity; that the board is three PCBs; that no separate reset button exists | 1 462 039 B, sha-256 `b5abecac97cb043a6d1af7a673f2111d40d9254b0b5108635cb924d9b37ad6fa`, **6 sheets**, Creator `Altium Designer`, Producer `llPDFLib 3.x`. **Sheet 1 of 2 of the NFC document is missing** — the included NFC sheet is numbered `2/2`. There is **no machine-readable netlist**: S45 shows M5Stack published no C153 EDA source, so connectivity was recovered from invisible Altium marker text (see [`commands.md`](commands.md#altium-pdf-tooling)), which yields *text adjacency, not electrical connectivity* | `devices/m5stack/papermono/artifacts/schematic/PaperMono_SCH_V0.6.2_20260522.pdf` |
-| **S15** | `C153_PaperMono_model_size.pdf` | M5Stack | primary | mechanical drawing | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/C153_PaperMono_model_size.pdf> | 2026-09-01 | no revision or date on the drawing; PDF `CreationDate`/`ModDate` **2026-08-20** | Outline dimensions, corner radii and port positions | 21 346 B, `b833a3e52594a3175bc131006d41a3eb5662be5936d0b2f25030180033a6703b`, 1 page, Producer `Adobe PDF Library 18.0.4`. **Dimensions are typeset in full-width CJK numerals**, so text extraction yields `６２` rather than `62`; readable but not machine-comparable without normalisation | `devices/m5stack/papermono/artifacts/mechanical/C153_PaperMono_model_size.pdf` |
-| **S16** | `PaperMono-Lite_PRJ_V0.6.2_20260522.pdf` | M5Stack | primary | schematic | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1268/PaperMono-Lite_PRJ_V0.6.2_20260522.pdf> (linked from S04) | **not retrieved** | filename revision **V0.6.2**, dated 2026-05-22 | Would establish what the Lite's board actually omits, rather than what the vendor comparison table says it omits | **URL recorded only — not fetched in this pass.** Named `PRJ`, not `SCH`, and the page's own thumbnail carousel shows **4 sheets** against S14's 6. The highest-value untaken lead for the Lite record | — |
-| **S17** | `C153-Lite_PaperMono-Lite_model_size.pdf` | M5Stack | primary | mechanical drawing | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1268/C153-Lite_PaperMono-Lite_model_size.pdf> | **not retrieved** | unknown | Would confirm whether the Lite's outline is genuinely identical to S15 or merely quoted as identical | URL recorded only. The two spec tables give identical product and package sizes, so a difference is not expected — but that is an inference from marketing copy, not a measurement | — |
-
-## Component datasheets and manuals linked from the product pages
-
-Nine documents. **Seven are M5Stack-hosted mirrors of another vendor's document**;
-two (S25, S26) are M5Stack's own primary documentation for its own silicon. The
-revision M5Stack serves is **not always the current one**, so each row states the
-revision *as mirrored*.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **S18** | ESP32-S3 Series Datasheet | Espressif Systems, **mirrored by M5Stack** | credible mirror | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf> | 2026-09-01 | **Version 2.0**, 84 pp | The pin/package data behind the ESP32-S3R8 rows in [`pinouts-and-buses.md`](pinouts-and-buses.md); which S3 variants share the datasheet | 1 083 807 B, `b6db403d6d5db8d1b4db0c8390ff7e0a7db714b8388e986e1c64bff563f76b61`. **This is the revision M5Stack ships to PaperMono users.** Espressif's own current revision differs; the component record holds four different ESP32-S3 datasheet files with four different hashes and explains which to read | `components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v2.0-m5stack-mirror.pdf` |
-| **S19** | BMI270 Data Sheet | Bosch Sensortec, **mirrored by M5Stack** | credible mirror | datasheet | <https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/app/Stamp%20Fly/BMI270.PDF> | 2026-09-01 | **Document revision 1.3, November 2020, BST-BMI270-DS000-05**, 162 pp — against Bosch's current **revision 1.6, March 2026, BST-BMI270-DS000-08**, 150 pp | The IMU register and interrupt behaviour **as M5Stack's engineers had it when the board was designed** | 3 830 973 B, `3ab915ed1d81d0eaa5ff1d1aed62b2b491260c9d59afbf79bb23fb477e015612`. **Five years and four months stale — three document revisions behind.** Note also *where* it is hosted: under the **Stamp Fly** product's asset folder, not a PaperMono folder. That is the mechanism by which a mirror goes stale — nobody refreshes a shared asset when a new board ships. The older document is 12 pages *longer*, so it is retained rather than deduplicated. Read 1.6 for what the silicon does; read 1.3 to understand M5Stack's choices | `components/bosch-sensortec/bmi270/artifacts/bst-bmi270-ds000-05-rev1.3-m5stack-mirror.pdf` (Bosch's 1.6 is alongside as `bst-bmi270-ds000.pdf`) |
-| **S20** | SSD1677 — 960 Source × 680 Gate EPD Display Driver with Controller | Solomon Systech Limited, **mirrored by M5Stack** | authorized mirror | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/SSD1677.pdf> | 2026-09-01 | **Rev 1.0, November 2018**, marked **"Advance Information"** | The display controller's command set, the 20 MHz maximum write clock (§12.1), the 680 gate-output limit that disproves the DKE drawing's `800 gate × 480 source` note | 3 602 487 B, `daf8b726f822f6907529386b8af6fbea6ec5e8ecc7b7af361340be911d632544`. **Provenance is suspect and recorded as such**: the file has 46 pages but numbers itself `n/47`, and its PDF Producer is `PDFill: Free PDF Writer and Tools` with `CreationDate` 2019-01-09 — a re-written copy, not a Solomon Systech export. "Advance Information" means preliminary. Treat numeric limits as indicative | `components/solomon-systech/ssd1677/artifacts/ssd1677-rev1.0-nov2018-m5stack-mirror.pdf` |
-| **S21** | EPD Module User Manual — `DEPG0397BBS770F3` | DKE Holding Company Limited, **mirrored by M5Stack** | authorized mirror | module specification | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/EPD_Module_User_Manual.pdf> | 2026-09-01 | **cover is undated**; the mechanical drawing inside is **REV A0, 2024-09-29**; PDF `ModDate` 2026-08-21 | The panel's FPC pin assignment (p. 7), which matches S14's `J5` position for position; the 20 MHz clock limit (p. 16); the optical table | 8 666 208 B, `6b65f56d5d549a132e5c807eef329fb3e997feab04ac06e8a107f01591618130`, 30 pp. Producer is **`iLovePDF`** — a re-processed copy. Two of this record's unresolved conflicts come from here: its optical table says **`GN — 2Grey Level`** where the vendor markets 4-level greyscale, and its drawing note 3 reads `800 gate × 480 source`, which is provably backwards. **The OTP waveform contents are not published anywhere**, so how many of the 34 WS/TR slots are programmed, and over what temperature span, is unknown | `components/dke/depg0397bbs770f3/artifacts/depg0397bbs770f3-epd-module-user-manual.pdf` |
-| **S22** | RX8130CE Application Manual | Seiko Epson Corporation, **mirrored by M5Stack** | credible mirror | datasheet / register manual | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1132/RX8130CE_cn-Register-Datasheet.pdf> | 2026-09-01 | document number **ETM50E-09**; PDF `CreationDate` 2025-06-23, `ModDate` 2025-07-16; 70 pp | The RTC register map and alarm/timer behaviour behind the `PYG0_RTC_INT` wake path | 2 283 323 B, `7157dc5692e5e0d84203027b600858e57880ef7a38b9c7d7f8c661a93fc8f3f5`. Filename says `_cn` but the served document is the **English** ETM50E manual — the label is wrong, the content is not. Epson's current revision was **not** checked, so mirror lag here is `unknown` | `components/seiko-epson/rx8130ce/artifacts/rx8130ce-register-datasheet-cn-m5stack-mirror.pdf` |
-| **S23** | ST25R3916/ST25R3917 Datasheet | STMicroelectronics, **mirrored by M5Stack** | credible mirror | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_EN.pdf> | 2026-09-01 | **DS12484 Rev 8, 08-May-2023**, 160 pp (document revision history runs rev 1 30-Jan-2019 → rev 8) | The NFC front end's capabilities and I²C interface; the `0x50` address context | 2 241 765 B, `1170f4d74ff501917262ae42bf81c60c38c11d121e2ea2af6b1e845433befef1`. Genuine ST export (`C2 v20.4.0000`), later re-saved through iText. ST's current revision was **not** checked — mirror lag `unknown`. Note the board's NFC schematic sheet 1/2 is missing from S14, so this datasheet is currently the *only* description of the NFC front end | `components/stmicroelectronics/st25r3916/artifacts/st25r3916-datasheet-m5stack-mirror.pdf` |
-| **S24** | SX1261/2 Datasheet — Long Range, Low Power sub-GHz RF Transceiver | Semtech Corporation, **mirrored by M5Stack** | credible mirror | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf> | 2026-09-01 | **Rev 2.2, December 2024**, `DS.SX1261-2.W.APP`, 118 pp | The LoRa transceiver silicon behind the `Stamp LoRa-1262` module | 4 459 535 B, `6d783125dbef567954ce53095ad068d0950b2a8de52f95bb2cfde4146c4306c2`. **This describes the chip, not the module.** No `Stamp-LoRa-1262` module datasheet was located anywhere, so TCXO-versus-XTAL, the module's matching network and the semantics of `SX_ANT_SW` remain undocumented. Semtech's current revision was not checked | `components/semtech/sx1262/artifacts/sx1261-2-datasheet-v2.2-m5stack-mirror.pdf` |
-| **S25** | M5PM1 Chip User Manual | **M5Stack** (imprint: Shenzhen Mingzhan Information Technology Co., Ltd.) | primary | chip manual | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1207/M5PM1_Datasheet_EN.pdf> | 2026-09-01 | **V1.9, 2026-01-22**, 35 pp | The only vendor documentation of the power-management coprocessor: register map, GPIO functions, timer actions, wake logic | 814 731 B, `c6daffd0ab89d8de50c0a19f35f94321bc6c9511ad017dd242a3e765d88a96b6`. Internally inconsistent in four recorded places (PWM0/1 vs PWM1/2 naming; NeoPixel buffer at `0x60` in one place and `0x36` in another; an appendix citing pre-`SW:6` addresses; `SW_REV` default disagreeing with its own changelog). A **Chinese-language edition exists as a distinct document** (S27) and was not retrieved | `components/m5stack/m5pm1/artifacts/m5pm1-chip-user-manual-v1.9-en.pdf` |
-| **S26** | M5IOE1 Chip User Manual | **M5Stack** (imprint: Shenzhen Mingzhan Information Technology Co., Ltd.) | primary | chip manual | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1210/IO_Expander_Datasheet_EN.pdf> | 2026-09-01 | **V1.4, 2025-11-25**, 12 pp | The only vendor documentation of the I/O expander: 14 GPIOs, 4 PWM channels, 12-bit ADC, temperature sensor, NeoPixel RAM, 32 B retention RAM | 398 463 B, `9204d99cb2e03395ffc905e05fbeddf7f9f25de5698a31a65fa439dee700d8d2`. **States the I²C address range `0x6F`–`0x76` in three places, while everything on this board uses `0x4F`** — unresolved, see [`gaps-and-conflicts.md`](gaps-and-conflicts.md#c4--the-m5ioe1s-i²c-address-is-not-in-its-own-manual). A Chinese edition exists (S28) and was not retrieved | `components/m5stack/m5ioe1/artifacts/m5ioe1-chip-user-manual-v1.4-en.pdf` |
-| **S27** | M5PM1 芯片用户手册 (Chinese edition) | M5Stack | primary | chip manual | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1207/M5PM1_Datasheet_CN.pdf> | **not retrieved** | unknown | Linked **only** from the zh_CN page (S02) | URL recorded only. Named the **highest-value untaken lead** of the documentation pass: a CN↔EN diff of S25/S26 could settle the `PYG`/`G<n>` nomenclature at the silicon level, and these are the only vendor documents for these parts | — |
-| **S28** | M5IOE1 IO 扩展芯片用户手册 (Chinese edition) | M5Stack | primary | chip manual | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1210/IO_Expander_Datasheet_CN.pdf> | **not retrieved** | unknown | Linked only from S02 | URL recorded only. Same rationale as S27 | — |
-| **S29** | ST25R3916 数据手册 (Chinese) | STMicroelectronics via M5Stack | credible mirror | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1205/ST25R3916_ZH.pdf> | **not retrieved** | unknown | Linked only from S02 | URL recorded only. Expected to be a translation of S23; not verified | — |
-| **S30** | ESP32-S3 系列芯片数据手册 (Chinese) | Espressif via M5Stack | credible mirror | datasheet | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_cn.pdf> | **not retrieved** | unknown | Linked only from S02 | URL recorded only | — |
-
-## M5Burner — firmware distribution
-
-The firmware pages are React shells with an empty `<div id="root">`; the download
-path was recovered by reading the SPA bundle. **`/api/firmwares/{id}` returns
-`401 {"msg":"请先登录"}`, but `/api/v1/firmwares/{id}` is public** — see
-[`research-log.md`](research-log.md#retrieval-findings-worth-reusing).
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **S31** | M5Burner firmware page — `2089640807996628993` | M5Stack | primary | HTML (SPA shell) | <https://burner.m5stack.com/firmware/2089640807996628993/> | 2026-09-01 | unknown | The `og:` metadata alone shows the record is named **"PaperMono UserDemo"**, not the "Factory Reset Firmware" the product pages label it | 2 735 B, `881e3cc65d241ef7…`. **Carries no content** — JavaScript shell. Useless without S33 | `scratch/m5stack-papermono/docs/burner/fw-2089640807996628993.{html,txt,meta}` |
-| **S32** | M5Burner firmware page — `2091144466157694978` | M5Stack | primary | HTML (SPA shell) | <https://burner.m5stack.com/firmware/2091144466157694978/> | 2026-09-01 | unknown | `og:` tags identify **"CrossPoint-PaperMono-CJK"** | 3 407 B, `553321018582f1d4…`. Same limitation | `scratch/m5stack-papermono/docs/burner/fw-2091144466157694978.{html,txt,meta}` |
-| **S33** | M5Burner public API — firmware detail, `2089640807996628993` | M5Stack | primary | JSON API | <https://burner.m5stack.com/api/v1/firmwares/2089640807996628993> | 2026-09-01 | record `uploadedAt` **2026-08-18T17:09:29+08:00** | `firmwareName` **"PaperMono UserDemo"**, `firmwareDescription` **"PaperMono / PaperMono-Lite UserDemo"** — *one image serves both SKUs* — `sourceType: OFFICIAL`, developer `m5stack` (uid 1), device `Paper`, `downloadCount: 16` | 1 209 B, `c9ffc4cdc06f669d…`. Counters are point-in-time. **This row is the evidence that the vendor link label "PaperMono Factory Reset Firmware" is wrong** | `scratch/m5stack-papermono/docs/burner/api-2089640807996628993-detail.json` |
-| **S34** | M5Burner public API — versions, `2089640807996628993` | M5Stack | primary | JSON API | <https://burner.m5stack.com/api/v1/firmwares/2089640807996628993/versions> | 2026-09-01 | version **v1.2**, `publishTime` **2026-08-18T17:09:29+08:00** | `binFileName` `C153-PaperMono-ESP32S3R8-UserDemo-V1.2-yaozhenquan-8300e309-20260806_0x00.bin`, version id `2089640808000823298` | 641 B, `0c215ac32b3b6e6c…`. The `binFileName` is **not** the name of the object actually served — see S38 | `scratch/m5stack-papermono/docs/burner/api-2089640807996628993-versions.json` |
-| **S35** | M5Burner public API — firmware detail, `2091144466157694978` | M5Stack (hosting a community submission) | primary (of the listing) | JSON API | <https://burner.m5stack.com/api/v1/firmwares/2091144466157694978> | 2026-09-01 | `uploadedAt` **2026-08-22T20:44:30+08:00** | `sourceType: COMMUNITY`, developer `IAMLIUBO` (uid 3966), `sourceUrl` `github.com/MarsTechHAN/crosspoint-reader-mono` | 1 460 B, `1e9c15f595fc544a…`. Establishes provenance of a **third-party** image that the vendor page links | `scratch/m5stack-papermono/docs/burner/api-2091144466157694978-detail.json` |
-| **S36** | M5Burner public API — versions, `2091144466157694978` | M5Stack | primary | JSON API | <https://burner.m5stack.com/api/v1/firmwares/2091144466157694978/versions> | 2026-09-01 | version **1.5.0-RC**, published 2026-08-22 | `binFileName` `crosspoint-paper-mono-full-with-cjk.bin`, version id `2091144466157694979` | 638 B, `5e189874a9950585…` | `scratch/m5stack-papermono/docs/burner/api-2091144466157694978-versions.json` |
-| **S37** | M5Burner SPA bundles — `index-DpEo0Py5.js`, `http-ChO34QIa.js`, `firmware-C6nFrscE.js` | M5Stack | primary | JavaScript | `https://burner.m5stack.com/assets/{index-DpEo0Py5,http-ChO34QIa,firmware-C6nFrscE}.js` | 2026-09-01 | unknown (content-hashed build artifacts) | The API base `` var Kn = `${`/api`.replace(/\/$/,``)}/v1` `` and the Bearer/`skipAuth` scheme — i.e. **how S33–S36 were found at all** | 230 198 B `584dd2aaf715a167…` / 47 846 B `2af1923137bd0198…` / 17 403 B `37c7383f12580238…`. **Filenames are build-hashed and will change on the next deploy**; the *shape* of the API is the durable finding, not these URLs | `scratch/m5stack-papermono/docs/burner/js-{index,http,firmware}.{js,meta}` |
-| **S38** | `C153-PaperMono-UserDemo-v1.2.bin` — official factory image | M5Stack | primary | ESP32 full-flash binary | API `…/firmwares/2089640807996628993/versions/2089640808000823298/download` → 302 → `https://m5burner-cdn.m5stack.com/community/1/2089640807996628993/2089640808000823298/bin/2089640808000823299.bin` | 2026-09-01T05:05:22Z | built **2026-08-06 16:12:13**, IDF **v5.5.1**, app version **`c78f6c5-dirty`** | Independent corroboration of the pin map (`PM1 shutdown, wake by BMI270 INT1 -> PM1 G4 falling edge`, `… wake by RX8130 timer -> PM1 G0 falling edge`), the board enum `board_M5PaperMono`, the M5PM1/M5IOE1 addresses and the 100 kHz default; the partition layout (single 15 360 K `factory`, **no OTA, no filesystem**) | 2 868 208 B, sha-256 `72c290bc2ffa216041b276660277369bd17ecef92315e367d98bb2c96c8428fa`, first byte `0xE9`, `content_type: application/macbinary`. **Tagged `-dirty`: built from an uncommitted tree and therefore not reproducible from any published commit of S41.** That is why the bytes are retained rather than referenced. Header reports flash mode **DIO** although the published build config says `qio_opi` | `devices/m5stack/papermono/artifacts/firmware/C153-PaperMono-UserDemo-v1.2.bin` |
-| **S39** | `crosspoint-paper-mono-cjk-1.5.0-RC.bin` — community e-reader image | Han Wang / `MarsTechHAN`, distributed by M5Stack | community | ESP32 full-flash binary | API `…/firmwares/2091144466157694978/versions/2091144466157694979/download` → 302 → `https://m5burner-cdn.m5stack.com/community/3966/2091144466157694978/2091144466157694979/bin/2091144466157694980.bin` | 2026-09-01T05:05:25Z | built **2026-08-22 19:58:33**, IDF **5.5.2.260206**, app version **`paper-mono-v2-15-g87a191f`** | That a third party shipped working PaperMono firmware within a day of launch; a contrasting partition layout (`app0` + a dedicated 4 MB `cjkfont` + SPIFFS + coredump) | 10 319 500 B, sha-256 `e2dee32b468da1d743b9fe8889eca959f5c0acdbe09c8f4cc3e69c69f8ebe935`, first byte `0xE9`. **Not vendor firmware.** Retained because it is not reproducible and because it is the only independent binary evidence that units shipped | `devices/m5stack/papermono/artifacts/firmware/crosspoint-paper-mono-cjk-1.5.0-RC.bin` |
-| **S40** | `C153-PaperMono-UserDemo_0x00.exe` — EasyLoader | M5Stack | primary | Windows flasher executable | <https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/C153-PaperMono-UserDemo_0x00.exe> | **not retrieved** | unknown | **Both S01 and S04 link this identical file, and it lives under PaperMono's asset folder `1267/`, not the Lite's `1268/`** — corroborating S33's "one image serves both" | URL recorded only; a Windows executable was out of scope. The finding is the *link*, not the payload | — |
-
-## Vendor source repositories — `github.com/m5stack`
-
-All accessed **2026-09-01** with `gh`-supplied authentication (5 000 req/h).
-SHAs are the full HEAD at the moment of cloning; these repositories are live and
-will move.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **S41** | `m5stack/M5PaperMono-UserDemo` — factory firmware source | M5Stack Technology CO LTD | primary | ESP-IDF 5.5.1 source, MIT | <https://github.com/m5stack/M5PaperMono-UserDemo> | 2026-09-01 | branch `main`, HEAD **`c1099107271d31a0678d661a896e2b04dbb331ea`**, commit date **2026-08-10T17:28:58+08:00** (`update firmware v1.2`); repo created 2026-05-07; 3 commits; **no tags, no releases** | **The single richest pin/address source after S14.** `main/hal/` declares every pin as a named constant; `repos.json` pins ten dependencies at exact commits (incl. RadioLib 7.2.1 `b91c6af1…`, M5GFX `develop` `02107b82…`, M5Unified `develop` `2fe93c0c…`) | 78 tracked files, 844 KB excluding `.git`. **Does not vendor its dependencies** — `fetch_repos.py` clones them. **Will not reproduce S38**, which is `-dirty`. Nothing in it was compiled or run here | `scratch/m5stack-papermono/repos/M5PaperMono-UserDemo/` |
-| **S42** | `m5stack/M5PaperMono-OTP-Demo` — e-paper OTP waveform example | M5Stack | primary | ESP-IDF source, MIT | <https://github.com/m5stack/M5PaperMono-OTP-Demo> | 2026-09-01 | branch `main`, HEAD **`c7c02554f89fd06f80d988b805b2a59050c78a46`**, commit date **2026-08-20T19:55:11+08:00** (`Merge GitLab initial history`); repo created 2026-08-20; 3 commits; no tags | **Names the fitted panel as `DEPG0397BBS770F3HP-XM`** — a suffix that appears nowhere in the vendor documentation; drives the SSD1677 directly at **20 MHz** using only OTP waveforms; implements a working 4-grey mode (`0xD7`, `0x1A = 0x5A`) | 17 tracked files, 120 KB excluding `.git`. Deliberately minimal — it bypasses M5GFX entirely. **This is the code M5Stack recommends over its own graphics library**, which is itself the finding | `scratch/m5stack-papermono/repos/M5PaperMono-OTP-Demo/` |
-| **S43** | `m5stack/M5PM1` — power-management chip library | M5Stack | primary | Arduino/ESP-IDF driver, MIT ("Copyright (c) 2025") | <https://github.com/m5stack/M5PM1> | 2026-09-01 | branch `main`, HEAD **`be9a5456c007c333e7ac963f33bfde1ffa5d82ee`**, commit date **2026-05-29T17:58:35+08:00**; 45 commits; tags `1.0.1`–**`1.0.7`** | That the M5PM1 has **exactly five GPIOs** (`M5PM1_GPIO_NUM_0…_4`) and **no `PYG` identifier anywhere** — half of the evidence that settles the naming ambiguity; the full register map | `src/M5PM1.h` is 136 KB and is *itself* the primary documentation for the part — an exhaustively commented bilingual register map. Ships S25 in `docs/`. Nothing compiled or run | `scratch/m5stack-papermono/repos/M5PM1/` |
-| **S44** | `m5stack/M5IOE1` — I/O expander library | M5Stack | primary | Arduino/ESP-IDF driver, MIT | <https://github.com/m5stack/M5IOE1> | 2026-09-01 | branch `main`, HEAD **`846eec7d05e25c09013be2acdb8804487f48a62e`**, commit date **2026-05-29T17:58:35+08:00**; 47 commits; tags `1.0.1`–**`1.0.9`** | `M5IOE1_PIN_1…_14`, `M5IOE1_MAX_GPIO_PINS 14` and **no pin 0** — so `PYG0` cannot denote an expander pin; the ADC/PWM channel tables that match the docs' `PYG<n>_ADC<m>` suffixes 7-for-7; the **off-by-one** (`M5IOE1_PIN_3 = 2`) | Ships S26 in `docs/`. Note a committed `.claude` directory — agent configuration left in a published repo. Nothing compiled or run | `scratch/m5stack-papermono/repos/M5IOE1/` |
-| **S45** | `m5stack/M5_Hardware` — published hardware design files | M5Stack | primary | KiCad/Altium design repository, MIT | <https://github.com/m5stack/M5_Hardware> | 2026-09-01 | branch `master`, HEAD **`a240115c94b19ecf647f229c47fa9a8ce46ccdc4`**, commit date **2026-08-17T15:36:01+08:00**; 369 files in tree | **Verified negative — there is no C153 directory.** `git ls-tree -r` matches zero paths for `papermono` or `c153`; the SKU sequence reaches `C152_StopWatch` and stops; the only Paper-family entries are `C139_PaperS3`, `C151_PaperColor` and `K049-B_Paper_v1.1` | Cloned `--filter=blob:none --no-checkout` (348 KB as cloned; the API reports ~127 MB for a full clone), so the search was **by tree path, not by file content**. The negative is nonetheless solid: a schematic directory would have to exist as a path. **Consequence: S14 is the only schematic, and there is no machine-readable netlist to cross-check the pin map against.** The repo was pushed 2026-08-17, *after* S41's firmware commit, so this is not publication lag | `scratch/m5stack-papermono/repos/M5_Hardware/` |
-| **S46** | `m5stack/M5Unified` — board abstraction library | M5Stack | primary | Arduino/ESP-IDF library, MIT | <https://github.com/m5stack/M5Unified> | 2026-09-01 | `master` HEAD **`8530f5377d782e4a25a6c482de2e71c3f75ca8eb`**; `develop` HEAD **`98c81b182f10760fe5313c31982cf975dfd73bda`** (10 commits ahead); latest release **0.2.21, 2026-08-26** | **Refutes the vendor's `#develop` build requirement**: `board_M5PaperMono` is byte-identical on both branches and ships in the released tag. Also the I²C pin row `{ board_M5PaperMono, GPIO_NUM_48, GPIO_NUM_47, 255, 255 }` and the microSD pin set | 158 files, 6.9 MB. The SCL-before-SDA column order in that row was read from neighbouring board rows, not from the struct definition — `inferred`. Nothing compiled or run | `scratch/m5stack-papermono/repos/M5Unified/` |
-| **S47** | `m5stack/M5GFX` — graphics / panel driver library | M5Stack | primary | Arduino/ESP-IDF library, MIT | <https://github.com/m5stack/M5GFX> | 2026-09-01 | `master` HEAD **`d91077b9a607b59404e4e4a49f775c792bfae382`**; `develop` HEAD **`8d6e8b3e0e9629e0bf0702d263e9263b588b6075`** (11 commits ahead); latest release **0.2.28, 2026-08-25** | The e-paper bus configuration (40 MHz, `pin_rst = GPIO_NUM_NC`), the expander bring-up bit masks whose comments independently confirm the `IO3/IO5/IO6/IO13/IO14` mapping, the `"M5PaperMono need OPI-PSRAM enabled"` abort, the frontlight PWM path — **and that `develop` has replaced the e-paper waveform LUTs, leaving the previous `lut_quality` commented out in-tree** | 294 files, 209 MB for a full clone of both branches. The commented-out LUTs are direct corroboration of M5Stack's own "currently unstable" warning. Branches `copilot/fix-code-for-review-comments`, `feature/lvgl_font_support` and `fhd60` exist and were **not** examined | `scratch/m5stack-papermono/repos/M5GFX/` |
-
-> **Seven repositories, not six.** S41–S45 were the five sought for the PaperMono
-> itself; S46 and S47 were added because the vendor's build instructions pin a
-> branch of them, and checking that claim required both branches of both.
-
-## Store and reseller listings
-
-Prices are **not currency-converted**: three currencies under three VAT regimes
-with three shipping arrangements. Each row stands alone.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **S48** | PaperMono store listing + Shopify product JSON | M5Stack | primary | storefront page / JSON | <https://shop.m5stack.com/products/m5papermono-with-lora-nfc-800x480-3-97-eink-display> and `…-display.json` | 2026-09-01 | `created_at` **2026-08-18T14:29:31+08:00**, `published_at` **2026-08-21T12:00:10+08:00**, `updated_at` 2026-09-01T13:02:02+08:00 | SKU **`C153`**, **USD 65.00**, `schema.org/OutOfStock`, exactly one variant (`Default Title`), shipping weight 100 g, product id `9316360159489`, variant `50199717249281` | 703 507 B `77299ffde91a6db3…` / 20 925 B `0f075e3f55813c7a…`. The page's Stoq/RestockRocket payload exposes `inventory_quantity = -129`; **that is a storefront counter reading, not proof of a 129-unit backlog** — Shopify negatives also arise from stock-count corrections. Note the title says `800x480` where every docs page says `480x800` | `scratch/m5stack-papermono/docs/shop/prod-papermono.{html,txt,meta}`, `…/prod-papermono.json` |
-| **S49** | PaperMono-Lite store listing + Shopify product JSON | M5Stack | primary | storefront page / JSON | <https://shop.m5stack.com/products/papermono-lite-dev-kit-800x480-3-97-e-ink-display> and `…-display.json` | 2026-09-01 | `created_at` **2026-08-18T14:26:42+08:00**, `published_at` **2026-08-21T12:00:09+08:00** | SKU **`C153-LITE`** (upper case, where the docs page says `C153-Lite`), **USD 55.00**, out of stock, one variant, shipping weight 98 g, `inventory_quantity = 0` | 693 406 B `10b51467fc079f04…` / 19 938 B `4b8c721f96722576…`. **The USD 10 delta against S48 is the entire price of NFC + LoRa.** The two SKUs are in *different* inventory states (`0` vs `−129`) | `scratch/m5stack-papermono/docs/shop/prod-papermono-lite.{html,txt,meta}`, `…/prod-papermono-lite.json` |
-| **S50** | "M5Stack Launches PaperMono: A Compact E-Ink Development Terminal for Connected Projects" | M5Stack | primary | vendor blog post | <https://shop.m5stack.com/blogs/news/m5stack-launches-papermono-a-compact-e-ink-development-terminal-for-connected-projects> | 2026-09-01 | `<time datetime="2026-08-21">` | The launch announcement, and the mention of the CrossPoint Reader | 448 198 B, `219f922915e350d6…`. **This single post is the origin of essentially every written article about the product** (see S76–S79). No JSON-LD `datePublished` on this theme | `scratch/m5stack-papermono/docs/shop/blog-launch.{html,txt,meta}` |
-| **S51** | Store search `?q=papermono` | M5Stack | primary | storefront search | <https://shop.m5stack.com/search?q=papermono> | 2026-09-01 | n/a | **The only way the two real product handles were found.** Both marked Out Of Stock | 448 043 B, `649376c136fce2ad…`. Necessary because the obvious handles do not exist: `/products/papermono`, `/products/papermono-lite` and `/products/m5stack-papermono` all return **404** (three responses of exactly 389 759 B with three different hashes — a templated 404 with a per-request nonce) | `scratch/m5stack-papermono/docs/shop/search-papermono.{html,txt,meta}`; the 404 probes at `…/products-{papermono,papermono-lite,m5stack-papermono}.{html,meta}` |
-| **S52** | Store news feed | M5Stack | primary | Atom feed | <https://shop.m5stack.com/blogs/news.atom> | 2026-09-01 | 30 entries, back to 2021 | Dated announcement history; independently confirms the PaperMono post at 2026-08-21 | Feed window is the last 30 entries only | `scratch/m5stack-papermono/market/_raw/blog-news.atom` |
-| **S53** | The Pi Hut — M5Stack PaperMono | The Pi Hut (UK) | primary (of the listing) | storefront page / JSON | <https://thepihut.com/products/m5stack-papermono> | 2026-09-01 | listing created/published **2026-08-21T11:15:48+01:00** | SKU `C153`, **GBP 62.40 incl. VAT** (page offers an `excl. VAT` toggle), `schema.org/OutOfStock` | Reseller listing, not a vendor price. **No Lite listing exists at this or any other reseller found** | `scratch/m5stack-papermono/market/_raw/` |
-| **S54** | OpenELAB (.io) — M5PaperMono | OpenELAB | primary (of the listing) | storefront page / JSON | <https://openelab.io/products/m5stack-m5papermono-with-lora-nfc-800x480-3-97-eink-display> | 2026-09-01 | listing created **2026-08-21T06:12:30+02:00** | SKU `M5-C153`, barcode `17841945721489`, **EUR 79.95**, `Shopify.currency.active = "EUR"` | Listed `available = true` **but the title itself is suffixed "(Pre-sale)"** — this is a pre-order, not stock on hand. Do not read it as availability | `scratch/m5stack-papermono/market/_raw/` |
-| **S55** | OpenELAB (.de) — M5PaperMono | OpenELAB | primary (of the listing) | storefront page / JSON | <https://openelab.de/products/m5stack-m5papermono-with-lora-nfc-800x480-3-97-eink-display> | 2026-09-01 | listing created **2026-08-21T06:13:28+02:00** | Same SKU and **EUR 79.95**, title suffixed "(Vorverkauf)" | Same caveat as S54; the two OpenELAB domains are one listing in two locales | `scratch/m5stack-papermono/market/_raw/` |
-| **S56** | M5Stack distributor list | M5Stack | primary | HTML page | <https://m5stack.com/distributor> | 2026-09-01 | unknown | The 37-domain seed list from which the reseller sweep (S57–S67) was built | 101 KB. Being on this list is why Mouser's and DigiKey's inaccessibility (S64, S65) is an unknown rather than a negative | `scratch/m5stack-papermono/market/_raw/distributor.html` |
-| **S57** | Amazon.com search — `m5stack papermono` | Amazon | community (retail index) | storefront search | <https://www.amazon.com/s?k=m5stack+papermono> | 2026-09-01 | n/a | **Verified negative.** Page reports "5 results" — an A5 loose-leaf paper refill and four unrelated M5Stack items. No PaperMono listing | Required `curl --compressed`; without it the response is raw gzip that reads as a bot-block. **Amazon was never actually blocking.** A second consecutive query was rate-limited to a 1 330-byte stub, so this is one observation, not a repeated one | `scratch/m5stack-papermono/market/_raw/amz.html`, `amz2.html` |
-| **S58** | AliExpress search — `wholesale-papermono` | AliExpress | community (retail index) | storefront search | <https://www.aliexpress.com/w/wholesale-papermono.html> | 2026-09-01 | n/a | **Verified negative.** Only M5Stack **PaperColor** returned (US $127.91 / $182.87, third-party sellers). Independently corroborates CNX-Software's "not listed on AliExpress (anymore)" | A looser query (`m5stack paper mono`) returned 50 unrelated commodity titles and was rejected as noise | `scratch/m5stack-papermono/market/_raw/ali-papermono.html` |
-| **S59** | Switch Science search — `PaperMono` | Switch Science (JP, official M5 distributor) | community (retail index) | storefront search | <https://www.switch-science.com/search?q=PaperMono> | 2026-09-01 | n/a | **Verified negative** — 「PaperMono」の検索結果**0件**, stated explicitly by the page | `/search/suggest.json` returns **HTTP 417**; the HTML search path works and states result counts in words, which is stronger evidence than an empty list | `scratch/m5stack-papermono/market/_raw/` |
-| **S60** | Adafruit search — `papermono` | Adafruit | community (retail index) | storefront search | <https://www.adafruit.com/?q=papermono> | 2026-09-01 | n/a | **Verified negative** — "No products found for 'papermono'" | Adafruit's *blog* was not separately queried — a recorded gap | `scratch/m5stack-papermono/market/_raw/` |
-| **S61** | Reichelt search — `papermono` | Reichelt Elektronik | community (retail index) | storefront search | `https://www.reichelt.com/index.html?ACTION=446&SEARCH=papermono` | 2026-09-01 | n/a | **Verified negative** — "Die Suche nach papermono hatte 0 Treffer" | — | `scratch/m5stack-papermono/market/_raw/` |
-| **S62** | Botland search — `papermono` | Botland | community (retail index) | storefront search | `https://botland.store/search?controller=search&s=papermono` | 2026-09-01 | n/a | **Verified negative** — 0 products (all 20 string matches were locale-switch URL echoes) | Counting raw string matches here would have produced a false positive; the URL echoes had to be read | `scratch/m5stack-papermono/market/_raw/` |
-| **S63** | Core Electronics search — `papermono` | Core Electronics (AU) | community (retail index) | storefront search | `https://core-electronics.com.au/catalogsearch/result/?q=papermono` | 2026-09-01 | n/a | **Verified negative** — 0 products | — | `scratch/m5stack-papermono/market/_raw/` |
-| **S64** | Mouser search — `papermono` | Mouser Electronics | — | storefront search | <https://www.mouser.com/c/?q=papermono> | 2026-09-01 | n/a | **No determination.** HTTP 200 with a 13.9 KB bot-denial page | **Inaccessible, not negative.** Mouser is on M5Stack's own distributor list (S56), so absence is unproven. Mouser publishes a Search API; no key was available in this session | — |
-| **S65** | DigiKey search — `papermono` | DigiKey | — | storefront search | <https://www.digikey.com/en/products/filter/keyword?keywords=papermono> | 2026-09-01 | n/a | **No determination.** HTTP 403 | Inaccessible, not negative. Also on S56. An adjacent datapoint only: a YouTube creator reported on 2026-07-14 that DigiKey still stocked the EOL M5Paper v1.1 — evidence the family is carried, not this board | — |
-| **S66** | TinyTronics search — `papermono` | TinyTronics (NL) | — | storefront search | <https://www.tinytronics.nl/en/search?query=papermono> | 2026-09-01 | n/a | **No determination.** HTTP 403 on both the HTML path and `/search/suggest.json` | Inaccessible, not negative | — |
-| **S67** | Secondary reseller sweep — MakerLab Electronics, Elektor, BerryBase, Robu.in, Cytron, MC Hobby | various | community (retail index) | storefront search | `/search/suggest.json` or native search per site | 2026-09-01 | n/a | MakerLab, Elektor and BerryBase: **verified negative**, 0 products. Robu.in: **403, no determination** | Grouped because each contributes one bit. **`/search/suggest.json` is not universal**: it worked on OpenELAB, The Pi Hut, Soldered, LilyGO, MakerLab and Elektor; **404** on Core Electronics, Botland, Cytron, BerryBase and MC Hobby; **403** on TinyTronics and Robu.in | — |
-
-## Community, editorial and third-party code
-
-Everything in this section is **community class**. The section exists partly to
-record how little of it there is: eleven days after launch there were **zero
-written reviews and one hands-on video**.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **S68** | "M5Stack Launches PaperMono" — Hacker News discussion | Hacker News users | community | forum thread | <https://news.ycombinator.com/item?id=49468593> | 2026-09-01 | thread dated **2026-08-27**, 162 points, 58 comments | The largest discussion anywhere; recurring themes (M5Stack hardware good / software half-baked, everything out of stock, XTEINK X4 Pro comparisons) | **Contains no firsthand PaperMono measurement at all.** One adjacent firsthand *PaperS3* report. It is also the origin of the unsupported "e-ink driver IC shortage" claim. Retrieved as a complete nested tree via `hn.algolia.com/api/v1/items/49468593` | `scratch/m5stack-papermono/market/_raw/hn-49468593.json` |
-| **S69** | Earlier HN submission of the same URL | Hacker News | community | forum thread | <https://news.ycombinator.com/item?id=49390702> | 2026-09-01 | **2026-08-21**, 2 points, 1 comment | Only that the story was posted ~8 h after announcement and was already out of stock | Duplicate of S68's URL; listed so a later pass does not treat it as a second source | — |
-| **S70** | r/M5Stack — "Paper Mono coming August 21st" | u/… (leak thread), r/M5Stack | community | forum thread | <https://old.reddit.com/r/M5Stack/comments/1vquxa5/paper_mono_coming_august_21st/> | 2026-09-01 | **2026-08-17**, score 198, 22 comments | Pre-launch leak from a vendor YouTube Short. Larry Bank's precise, correct statement of the PaperS3/PaperMono panel difference; the `bb_epaper` and freeink.org support claims | Those support claims were made **four days before launch**, so necessarily written against documentation, not hardware. The `bb_epaper` half is **unconfirmed** — see S97 | `scratch/m5stack-papermono/market/_raw/` |
-| **S71** | r/M5Stack — "Check out what's new this week!" | M5Stack (u/No-Connection1900) and commenters | community + vendor statement | forum thread | <https://old.reddit.com/r/M5Stack/comments/1vuaneb/check_out_whats_new_this_week/> | 2026-09-01 | **2026-08-21**, score 75, 17 comments | Vendor's own launch post; **the vendor states pre-orders "reached the limit"**; multiple independent failed-purchase reports; u/async2's openelab.de lead (→ S55); u/Tsixom's PaperS3 comparison, checked line-by-line against the vendor docs here and **accurate on every point** | Vendor statements in a forum are primary as *statements* but were not corroborated elsewhere | `scratch/m5stack-papermono/market/_raw/` |
-| **S72** | @henry19840301 — first independent ownership report | Henry Li (`github.com/MagicCube`) | community | social post | <https://x.com/henry19840301/status/2090652363434647738> | 2026-09-01 | **2026-08-21 04:09 UTC**, 87 likes, 23 665 views | **The strongest ownership evidence anywhere**: purchase photos posted **nine minutes** after the storefront published. The same person then published a hardware-validated project (S89), so ownership is corroborated across two independent surfaces | Retrieved as JSON via `api.fxtwitter.com`; `x.com` itself serves a gzipped JS shell. The post's "sold out in just one second" is colloquial — **the checkable fact is the nine-minute gap** | `scratch/m5stack-papermono/market/_raw/fx-2090652363434647738.json` |
-| **S73** | @berryxia — restock request | @berryxia | community | social post | <https://x.com/berryxia/status/2091105450494238837> | 2026-09-01 | **2026-08-22 10:09 UTC**, 2 likes, 569 views | A failed-purchase report, and — more importantly — **the parent of S74**, which is what allowed the "driver IC shortage" claim to be checked against the actual chain | Retrieved via fxtwitter. Its value is structural: it is the link that disproves a widely repeated claim | `scratch/m5stack-papermono/market/_raw/fx-2091105450494238837.json` |
-| **S74** | @M5Stack — restock guidance | M5Stack | primary (vendor statement) | social post | <https://x.com/M5Stack/status/2091116748686922069> | 2026-09-01 | **2026-08-22 10:54 UTC**, 300 views | The vendor's own restock statement, verbatim: 「要等两三个月了」 — *"you'll have to wait two or three months"* | **The full text says only that.** No reason is given. **The "because they're out of e-ink driver IC" attribution appears nowhere in this post, its parent (S73) or the thread root (S75)** — that is hearsay and must not be propagated. Conflicts with CNX-Software's "next year" (S77); both recorded, neither preferred | `scratch/m5stack-papermono/market/_raw/` |
-| **S75** | @M5Stack — "PaperMono vs PaperMono-Lite" | M5Stack | primary (vendor marketing) | social post | `https://x.com/i/status/2091070115001315474` | 2026-09-01 | **2026-08-22 07:49 UTC** | The root of the S73/S74 chain; a marketing comparison post | Retrieved via `api.fxtwitter.com/i/status/<id>`, which resolves a bare status id without knowing the author handle — the technique that made chain-walking possible | `scratch/m5stack-papermono/market/_raw/fx-root.json` |
-| **S76** | "ESP32-S3 handhelds with 3.97-inch e-paper and optional LoRa/NFC" | Giorgio Mendoza, **LinuxGizmos** | community | article | <https://linuxgizmos.com/esp32-s3-handhelds-with-3-97-inch-e-paper-and-optional-lora-nfc/> | 2026-09-01 | JSON-LD `datePublished` **2026-08-21T05:19:35Z** (byline dated Aug 20) | The earliest article; a restatement of S50 | **Reproduced marketing copy — no hardware.** Retrieval note: this domain **inverts the usual ladder** — bare `curl/8.5.0` returns 200 and a Chrome 131 UA returns **403**. Re-syndicated verbatim by Tux Machines (S83) | `scratch/m5stack-papermono/market/_raw/cov-lg.html` |
-| **S77** | "M5Stack Paper Mono – An ESP32-S3 e-paper development board…" | Jean-Luc Aufranc, **CNX-Software** | community | article | <https://www.cnx-software.com/2026/08/21/m5stack-paper-mono-an-esp32-s3-e-paper-development-board-with-3-97-inch-touchscreen-lora-and-nfc/> | 2026-09-01 | WP REST `date` **2026-08-21T16:43:25**, `modified` 2026-08-22 | Mostly marketing restatement, plus **two genuinely independent observations**: ghosting visible in the vendor's own demo video at `epd_fastest`, and "not listed on AliExpress (anymore)" (reproduced here as S58) | Carries two claims this record rejects: **"Bluetooth 5.0 LE + Mesh"** is CNX's inference from the SoC, not an M5Stack specification; and the restock-"next year" statement is second-hand with no quote or link, conflicting with S74. Also a dimension conflict with the vendor: 101 × 61 × 7.95 mm vs 62.0 × 101.0 × 8.0 mm | `scratch/m5stack-papermono/market/_raw/cnx-post.json` |
-| **S78** | "Dispositivo portátil ESP32-S3 con papel electrónico de 3,97 pulgadas y LoRa/NFC opcional" | **MuyLinux** (ES) | community | article | <https://muylinux.xyz/dispositivo-portatil-esp32-s3-con-papel-electronico-de-397-pulgadas-y-lora-nfc-opcional/> | 2026-09-01 | JSON-LD **2026-08-23T21:48:10Z** | Nothing independent — it is a translation of S76 | Machine-flavoured translation (renders "frontlight" as *faro*, "beacon"). Listed to show the coverage graph is a tree with one root, not a set of independent observations | `scratch/m5stack-papermono/market/_raw/cov-ml.html` |
-| **S79** | "Lilbits: More phone-sized E Ink gadgets" | Brad Linder, **Liliputing** | community | article roundup | <https://liliputing.com/lilbits-more-phone-sized-e-ink-gadgets/> | 2026-09-01 | JSON-LD **2026-08-28T12:10:58Z** | One embedded Bluesky blurb | **Contains a factual error this record explicitly rejects:** it describes a **$55** model with NFC and LoRa. $55 is the **Lite**, which has neither; the NFC/LoRa model is $65 | `scratch/m5stack-papermono/market/_raw/cov-lp.html` |
-| **S80** | "M5Stack PaperMono: The Ultimate ESP32 Pocket Gadget?" | **Volos Projects**, YouTube | community | video | <https://youtu.be/sRlGOgX9KOA> | 2026-09-01 | `uploadDate` **2026-08-29 16:21 UTC**, 61 590 views | **The only hands-on account found anywhere.** Self-described first look | Not a measurement review. **The description carries a vendor referral link (`?ref=kmjp2x8a`)** — a disclosed commercial relationship. Repeats "built-in backlight"; the device has a *frontlight* | — |
-| **S81** | "New Arrivals: PaperMono & PaperMono-Lite" | M5Stack, YouTube | primary (vendor) | video | <https://youtu.be/0-qQ0y-WEek> | 2026-09-01 | `uploadDate` **2026-08-21 06:59 UTC**, 16 938 views | Vendor launch video; one of the three timestamps used to validate the `published_at` proxy | Vendor marketing | — |
-| **S82** | "Unboxing multiple M5Stack products in one time!" | IAMLIUBO, YouTube | community | video | <https://youtu.be/gX4cTpS2gUA> | 2026-09-01 | **2026-08-25**, 145 views | A genuine unboxing including both SKUs — second-order corroboration that units shipped | Negligible reach, no specification claims. Same uploader as the S39 firmware developer | — |
-| **S83** | Tux Machines aggregator items (≥4 URLs) | news.tuxmachines.org | community | aggregator | — | 2026-09-01 | 2026-08-21/22 | Nothing | **Rejected as coverage** — verbatim re-syndication of S76. Recorded only because it dominated pages 2–5 of the Mojeek results (S88) and inflates any result count | — |
-| **S84** | Hackaday search API — `papermono` | Hackaday | community | WordPress REST API | `https://hackaday.com/wp-json/wp/v2/search?search=papermono&per_page=20` | 2026-09-01 | n/a | **Verified negative — returns `[]`. Hackaday has published nothing on the PaperMono.** For contrast the same endpoint returns two older `m5paper` posts (2021-11-12; 2026-07-21) | A clean machine-readable negative, which is why it is worth a row | `scratch/m5stack-papermono/market/_raw/hackaday.json`, `hackaday2.json` |
-| **S85** | `community.m5stack.com` — vendor forum | M5Stack (NodeBB) | — | forum search | `https://community.m5stack.com/api/search?term=papermono&in=titlesposts` | 2026-09-01 | n/a | **No determination.** `/api/search` returns **HTTP 401** `{"code":"not-authorised"}`; `/search?term=` **302**s to login | **Inaccessible.** `/api/recent` *is* open and returned 198 topics with no PaperMono topic in the recent window — that is a window, not a search. The vendor's own forum is where owner reports would first appear, so this is a material gap | — |
-| **S86** | Bluesky public XRPC search — `papermono` | Bluesky | — | JSON API | `https://public.api.bsky.app/xrpc/app.bsky.feed.searchPosts?q=papermono&limit=50` | 2026-09-01 | n/a | **No determination.** HTTP 403 to `curl/8.5.0`, Chrome 131 and WhatsApp UAs alike | Inaccessible. One Bluesky post is known to exist only **second-hand**, from the embed inside S79 (@liliputing.bsky.social, 2026-08-28 08:04) | `scratch/m5stack-papermono/market/_raw/bsky.json` |
-| **S87** | Hackster.io search — `papermono` | Hackster.io | — | site search | <https://www.hackster.io/search?q=papermono> | 2026-09-01 | n/a | **No determination.** 200 but a JS shell; all 11 term matches are login-redirect URLs. `/search.json` and `/api/v2/projects` both return HTML, not JSON | **No working path found.** M5Stack links its own Hackster profile from every docs page footer, so this gap is not trivial | `scratch/m5stack-papermono/market/_raw/hackster.html` |
-| **S88** | Mojeek web search — `papermono` | Mojeek | community | search engine | <https://www.mojeek.com/search?q=papermono> | 2026-09-01 | n/a | "243 results", pages 1–5 read. **The only general web search engine that worked in this session**, and the only way S76, S78 and S79 were found at all | DuckDuckGo (HTML and Lite) returned **HTTP 202** anomaly pages and Marginalia a bot-wait interstitial. The result count is inflated by aggregator re-syndication (S83 dominated pages 2–5) — **read the URLs, not the count** | — |
-| **S89** | `MagicCube/free-ink-on-paper-mono` | Henry Li (`MagicCube`) — the S72 poster | community | source repository | <https://github.com/MagicCube/free-ink-on-paper-mono> | 2026-09-01 | created **2026-08-25**, pushed 2026-08-27, 3 stars; **HEAD SHA not recorded** | **The strongest third-party evidence.** README claims a complete verified hardware path: RX8130 time, M5PM1 battery/USB/charging telemetry, touch and buttons, frontlight held at 127/255, async e-ink refresh with periodic full cleanup — and "verified disabling of M5PM1's dangerous default single-click reset" | Runs on the **Lite (C153-Lite)**, not the full PaperMono. Claims are the author's; the code was read, the behaviour was not reproduced here. Commit SHA `unknown` — not captured in this pass, so this citation is not pinned | — |
-| **S90** | `Free-Ink/freeink-sdk` — `libs/hardware/BoardConfig/include/PaperMonoBoard.h` | Free-Ink | community | source file | `https://raw.githubusercontent.com/Free-Ink/freeink-sdk/…/PaperMonoBoard.h` | 2026-09-01 | **unknown** (no commit or tag recorded) | Detailed M5PM1 + M5IOE1 bring-up sequencing, including disabling the PMIC's single-click reset **while preserving the hardware long-hold download escape** — detail not obtainable from a spec sheet. Independently corroborates the same M5PM1 finding as S89 | Fetched from `raw.githubusercontent.com` without pinning a ref, so **the exact bytes cited cannot be re-resolved**. Recorded as a defect of this pass | — |
-| **S91** | `MingRZou/PaperMono-Launcher` | MingRZou | community | source repository | <https://github.com/MingRZou/PaperMono-Launcher> | 2026-09-01 | created **2026-08-30**, 1 star; HEAD SHA `unknown` | Self-described "hardware-validated" launcher with a photograph captioned "on real hardware". Explicitly a **port** of `bmorcelli/Launcher` from the PaperS3 — concrete evidence the two platforms are *not* drop-in compatible | Photograph not independently verified. SHA not pinned | — |
-| **S92** | `EggUncle/PaperMonoCalendar` | EggUncle | community | source repository | <https://github.com/EggUncle/PaperMonoCalendar> | 2026-09-01 | created **2026-08-31**, 0 stars; HEAD SHA `unknown` | Landscape calendar firmware for C153 with BLE activity tiles and RTC sync | **Commendably honest about its own limits**: the README states its preview images are software-generated, *not* device photographs (「非设备实拍」), and that displayed data is fictional. Ownership claimed, not shown | — |
-| **S93** | `hectorzin/M5PaperMono-HomeAssistant-ESPHome` | hectorzin | community | source repository | <https://github.com/hectorzin/M5PaperMono-HomeAssistant-ESPHome> | 2026-09-01 | created **2026-08-27**, pushed 2026-09-01, 0 stars; HEAD SHA `unknown` | An ESPHome "fase 1" minimal hardware test for C153 (SSD1677 + FT6336G via M5IOE1) | Early work-in-progress, and honest about it — its display/touch rotation section is labelled "**hipótesis de prueba**", i.e. unverified by the author | — |
-| **S94** | `crosspoint-reader/crosspoint-reader` — `ROADMAP.md` | CrossPoint Reader project | community | source file | `https://raw.githubusercontent.com/crosspoint-reader/crosspoint-reader/…/ROADMAP.md` | 2026-09-01 | unknown | Line 40 lists PaperMono among "ESP32-S3 class hardware (X4 Pro, PaperMono, Seeed Sticky)" targets | **Roadmap, not shipped support.** Do not cite as compatibility. Not pinned to a commit | — |
-| **S95** | `MarsTechHAN/crosspoint-reader-mono` | MarsTechHAN | community | source repository | <https://github.com/MarsTechHAN/crosspoint-reader-mono> | 2026-09-01 | version string in the shipped binary: `paper-mono-v2-15-g87a191f`; HEAD SHA `unknown` | The upstream named by S35 for the S39 binary | Repository metadata was not separately retrieved; the version identity comes from the binary's `esp_app_desc_t`, which is the stronger evidence anyway | — |
-| **S96** | `tanakamasayuki/M5Stack-Arduino-Check` | tanakamasayuki | community | source repository | <https://github.com/tanakamasayuki/M5Stack-Arduino-Check> | 2026-09-01 | contains `3.3.9/variants/m5stack_papermono/pins_arduino.h`; HEAD SHA `unknown` | That a `m5stack_papermono` board variant exists in **M5Stack's Arduino core 3.3.9** — a toolchain fact obtainable nowhere else here | Third-party mirror of core contents. Note S41 pins arduino-esp32 **3.3.10** as a managed component, so two core versions are in play | — |
-| **S97** | `bitbank2/bb_epaper` — code search for `PaperMono` | Larry Bank (`bitbank2`) | community | source repository | <https://github.com/bitbank2/bb_epaper> | 2026-09-01 | n/a | **Verified negative — a GitHub code search of the repository returns 0 matches**, and the README returns 0 matches for `papermono`, `paper mono` or `papercolor` | **This contradicts the author's own public support claim of 2026-08-17 (S70).** The support may exist under a different identifier, in an unpushed branch, or may not have landed. **Unresolved — do not cite `bb_epaper` PaperMono support as fact** | — |
-
----
-
-## What is deliberately absent
-
-- **No product, teardown or PCB photograph is held anywhere in this record.** The
-  vendor's imagery is not licensed for redistribution and no independent teardown
-  existed at the snapshot date. Recorded rather than filled with unattributed
-  images.
-- **No FCC/CE grantee-database search** was performed (S11 establishes only that
-  M5Stack publishes nothing).
-- **No measured power figure exists** from any source in this table — vendor
-  included. M5Stack publishes power figures for the PaperS3 and PaperColor but
-  not for this board, and no third party has filled the gap.
-- **The 14 Arduino API sub-pages** advertised by S07 were enumerated but not
-  fetched.
-- **Taobao, Tom's Hardware, Hackaday.io and Adafruit's blog** were not queried.
-  Reasons are in [`research-log.md`](research-log.md#not-attempted-and-why).
-
-## Related
-
-- [`README.md`](README.md) — the device record these sources support
-- [`research-log.md`](research-log.md) — every query, filter and disposition
-- [`commands.md`](commands.md) — every command, with execution status
-- [`gaps-and-conflicts.md`](gaps-and-conflicts.md) — what these sources disagree about
-- [`../papermono-lite/README.md`](../papermono-lite/README.md) — the variant record built from S04
diff --git a/devices/m5stack/stamp-c6lora/README.md b/devices/m5stack/stamp-c6lora/README.md
deleted file mode 100644
index e3b6898..0000000
--- a/devices/m5stack/stamp-c6lora/README.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# M5Stack Stamp C6LoRa (SKU S012)
-
-> **Light record.** Included because the task brief listed it as a candidate for "the older
-> Cardputer LoRa extension" — and the answer is **no: it is a solder-down SMD module, not an
-> expansion board, and it does not attach to any Cardputer.** It matters here for a
-> different reason: it is the third M5Stack product to use a **PI4IOE5V6408** to control an
-> **SX1262** antenna switch, which makes that pattern a house style rather than a one-off.
->
-> Published **2026-03-13**, USD **12.95**. Snapshot 2026-09-04.
-
-## 1. Identity
-
-| Property | Value |
-|---|---|
-| SKU | **S012** |
-| Store title | *M5Stamp C6LoRa Module (ESP32-C6, SX1262)* |
-| **Published** | **2026-03-13** |
-| Price | USD **12.95** |
-| Docs | `https://docs.m5stack.com/en/core/Stamp_C6LoRa` |
-| Form factor | **SMD surface-mount module**, 18.0 × 15.0 × 2.3 mm, **1.7 g** |
-| SoC | ESP32-C6 — RISC-V 160 MHz HP + 20 MHz LP, **16 MB flash**, **Wi-Fi 6** |
-| LoRa | **SX1262**, **850 – 960 MHz**, **+22 dBm**, **−148 dBm** |
-| **LNA** | **SGM13005L4** — a receive low-noise amplifier |
-| **I/O expander** | **PI4IOE5V6408** — *"to control the LoRa module's transceiver circuit and signal amplifier enable function"*, exposing **EXT_P0 … P4** |
-| Antenna | **two IPEX-4** connectors (Wi-Fi + LoRa) |
-| GPIO brought out | **16** — G9/G11/G8/G10/G2/G7/G4/G5/G6/G15/G16/G17/G18/G20/G21/G22 — plus 5 expander pins |
-| Power | DC 3.7–5 V on `BAT`, or DC 3.3 V on `VDD_3V3` |
-| Schematic | `S012-SCH_Sch_M5_C6_Lora_v0.2.3_2025_12_02…pdf` — **v0.2.3, 2025-12-02**, 3 sheets, held in [`artifacts/`](artifacts/) |
-| Toolchain | `pioarduino/platform-espressif32` pinned **`#55.03.37`** in the vendor docs |
-| KiCad footprint | `M5_Hardware/KiCad/Footprints/M5Stack.pretty/Stamp_C6LoRa_SMD.kicad_mod` |
-
-## 2. ❌ Not a Cardputer expansion
-
-It is an SMD module intended to be reflowed onto a carrier PCB. It has no Cap-Bus
-connector, no Grove connector and no enclosure. Where it *does* appear in Cardputer-adjacent
-territory is inside the **[Unit C6L (U202)](../unit-c6l/README.md)**, which is Grove-cabled
-and therefore usable alongside any Cardputer.
-
-## 3. Why it is worth a record anyway — the PI4IOE5V6408 pattern
-
-Three M5Stack products now put an **I²C I/O expander in charge of an SX1262's RF switch**:
-
-| Product | Expander | What it controls |
-|---|---|---|
-| [Cap LoRa-1262 (U214)](../cap-lora-1262/README.md) | `PI4IOE5V6408` @ 0x43 | **P0** → module pin 10 `SW` |
-| **Stamp C6LoRa (S012)** | `PI4IOE5V6408` | transceiver switch **and LNA enable**, EXT_P0–P4 exposed |
-| [M5Stack PaperMono](../papermono/README.md) | `M5IOE1` (different part) | `SX_ANT_SW` on IO2, `SX_NRST` on IO10 |
-
-The recurring design idea: **do not spend host GPIO on RF-path control; put it behind I²C.**
-The recurring consequence: **no I²C, no radio** — an I²C fault takes the RF path down even
-though SPI is fine. Anyone porting M5Stack LoRa hardware should expect this and look for the
-expander before concluding a radio is dead.
-
-Stamp C6LoRa goes further than the Cap by putting the **LNA enable** on the expander too,
-which is a real power-management win (an always-on LNA is exactly what the Cap LoRa-1262
-pays for on its GNSS front end — see
-[`../cap-lora-1262/features/gnss.md` §4](../cap-lora-1262/features/gnss.md)).
-
-## 4. Meshtastic
-
-**No `stamp_c6lora` variant exists upstream.** The relevant variant is
-`variants/esp32c6/m5stack_unitc6l/` — i.e. Meshtastic supports the *product built around*
-this module, not the module itself. `executed-success` on the negative, from the full
-recursive tree listing, 2026-09-04.
-
-## 5. Local artifacts
-
-| File | Bytes | SHA-256 | Source |
-|---|---:|---|---|
-| [`artifacts/S012-Stamp_C6LoRa_SCH_v0.2.3.pdf`](artifacts/S012-Stamp_C6LoRa_SCH_v0.2.3.pdf) | 489 288 | `2dafe92c5090a01aa948c1ce88b17d1237421d09701c1e0a15a122bd9d844d35` | `https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1223/S012-SCH_Sch_M5_C6_Lora_v0.2.3_2025_12_02_19_14_35.pdf`, retrieved 2026-09-04 |
-
-**The schematic was downloaded and bbox-extracted (3 sheets, 508/963/178 words) but not
-decoded** — that was out of scope for this pass. It is here so the next agent does not have
-to re-fetch it. Extraction command in
-[`../cap-lora-1262/commands.md`](../cap-lora-1262/commands.md).
-
-## 6. Related
-
-[`../unit-c6l/README.md`](../unit-c6l/README.md) ·
-[`components/semtech/sx1262`](../../../components/semtech/sx1262/README.md) ·
-[`components/diodes-incorporated/pi4ioe5v6408`](../../../components/diodes-incorporated/pi4ioe5v6408/README.md)
-
-## 7. Sources
-
-| ID | Title | Class | URL | Retrieved |
-|---|---|---|---|---|
-| S-1 | Stamp C6LoRa documentation | primary | `https://docs.m5stack.com/en/core/Stamp_C6LoRa` | 2026-09-04 |
-| S-2 | S012 store listing JSON | primary | `https://shop.m5stack.com/products/m5stamp-c6lora-module-esp32-c6-sx1262.json` | 2026-09-04 |
-| S-3 | Schematic v0.2.3 | primary | see §5 | 2026-09-04 |
-| S-4 | Meshtastic variant tree | primary | `api.github.com/repos/meshtastic/firmware/git/trees/master?recursive=1` | 2026-09-04 (negative result) |
diff --git a/devices/m5stack/stamp-c6lora/acquisition/manifest.json b/devices/m5stack/stamp-c6lora/acquisition/manifest.json
deleted file mode 100644
index 87600b5..0000000
--- a/devices/m5stack/stamp-c6lora/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "devices/m5stack/stamp-c6lora",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AN3WM5STAMPC6LORA-8765564",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPC6LORA/Test-Report/AiTSZ-250812012FW1-FCC-Test-Report-2-4G-WIFI-8765564.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765564",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765564.pdf",
-    "https://fccid.io/2AN3WM5STAMPC6LORA",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/Test-Report/AiTSZ-250812012FW1-FCC-Test-Report-2-4G-WIFI-8765564.pdf"
-   ],
-   "sha256": "f04da403673dd3ba95069c133854f19d984a07c712f749fc126aafa62782ddac",
-   "bytes": 2092093,
-   "destination": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-11-19",
-   "fcc_id": "2AN3WM5STAMPC6LORA",
-   "fcc_document_id": "8765564",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "AiTSZ-250812012FW1_FCC Test Report_2.4G WIFI",
-   "grant_date": "2025-11-19",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Guangdong Asia Hongke Test Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf",
-   "placeholder": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/stamp-c6lora",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPC6LORA-8765567",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPC6LORA/RF-Exposure-Info/AiTSZ-250812012FW5-FCC-RF-EXPOSURE-8765567.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765567",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765567.pdf",
-    "https://fccid.io/2AN3WM5STAMPC6LORA",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/RF-Exposure-Info/AiTSZ-250812012FW5-FCC-RF-EXPOSURE-8765567.pdf"
-   ],
-   "sha256": "00cfed2f15bf7bbf3f4b65723213d0b1896c00b0d4d7305b616a83e2ff8786bc",
-   "bytes": 449566,
-   "destination": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-11-19",
-   "fcc_id": "2AN3WM5STAMPC6LORA",
-   "fcc_document_id": "8765567",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "AiTSZ-250812012FW5_FCC RF EXPOSURE",
-   "grant_date": "2025-11-19",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Guangdong Asia Hongke Test Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf",
-   "placeholder": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/stamp-c6lora",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPC6LORA-8765573",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPC6LORA/External-Photos/EUT-External-photos-8765573.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765573",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765573.pdf",
-    "https://fccid.io/2AN3WM5STAMPC6LORA",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/External-Photos/EUT-External-photos-8765573.pdf"
-   ],
-   "sha256": "c1d9b24c18c383c7c8a090c70d4a6b6e484ab4f2b413fa4a81d4fb6891920ef4",
-   "bytes": 1252196,
-   "destination": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-11-19",
-   "fcc_id": "2AN3WM5STAMPC6LORA",
-   "fcc_document_id": "8765573",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "EUT External photos",
-   "grant_date": "2025-11-19",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Guangdong Asia Hongke Test Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf",
-   "placeholder": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/stamp-c6lora",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPC6LORA-8765574",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPC6LORA/Internal-Photos/EUT-Internal-photos-8765574.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765574",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765574.pdf",
-    "https://fccid.io/2AN3WM5STAMPC6LORA",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/Internal-Photos/EUT-Internal-photos-8765574.pdf"
-   ],
-   "sha256": "947b644d1a168f534d4e6f6a0c467b6cfe0115ccad1296cd11ce5e82d8fb9960",
-   "bytes": 416641,
-   "destination": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-11-19",
-   "fcc_id": "2AN3WM5STAMPC6LORA",
-   "fcc_document_id": "8765574",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "EUT Internal photos",
-   "grant_date": "2025-11-19",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Guangdong Asia Hongke Test Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/stamp-c6lora",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPC6LORA-8765576",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPC6LORA/Label/Label-location-8765576.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765576",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765576.pdf",
-    "https://fccid.io/2AN3WM5STAMPC6LORA",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/Label/Label-location-8765576.pdf"
-   ],
-   "sha256": "c838daa020297b84823ccce6d61d39f8d23a0a81e9437e337ebec49ad951df88",
-   "bytes": 199647,
-   "destination": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-11-19",
-   "fcc_id": "2AN3WM5STAMPC6LORA",
-   "fcc_document_id": "8765576",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label location",
-   "grant_date": "2025-11-19",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Guangdong Asia Hongke Test Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/stamp-c6lora",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5STAMPC6LORA-8765609",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5STAMPC6LORA/User-Manual/User-manual-8765609.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765609",
-    "https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765609.pdf",
-    "https://fccid.io/2AN3WM5STAMPC6LORA",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/User-Manual/User-manual-8765609.pdf"
-   ],
-   "sha256": "30447e175f34062a42acffb08dc49bbb97fa9f4e4a0ea8ca7b071af310dc6038",
-   "bytes": 1928952,
-   "destination": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-11-19",
-   "fcc_id": "2AN3WM5STAMPC6LORA",
-   "fcc_document_id": "8765609",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User manual",
-   "grant_date": "2025-11-19",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Guangdong Asia Hongke Test Technology Limited",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf",
-   "placeholder": "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/stamp-c6lora",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/m5stack/stamp-c6lora/artifacts/S012-Stamp_C6LoRa_SCH_v0.2.3.pdf b/devices/m5stack/stamp-c6lora/artifacts/S012-Stamp_C6LoRa_SCH_v0.2.3.pdf
deleted file mode 100644
index 18d406d..0000000
Binary files a/devices/m5stack/stamp-c6lora/artifacts/S012-Stamp_C6LoRa_SCH_v0.2.3.pdf and /dev/null differ
diff --git a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf.ARCHIVED.md b/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf.ARCHIVED.md
deleted file mode 100644
index 3d43b35..0000000
--- a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 2,092,093 B (2.00 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,092,093 B (2.00 MiB) |
-| SHA-256 | `f04da403673dd3ba95069c133854f19d984a07c712f749fc126aafa62782ddac` |
-| FCC ID | **`2AN3WM5STAMPC6LORA`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | AiTSZ-250812012FW1_FCC Test Report_2.4G WIFI |
-| FCC document id | 8765564 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Stamp C6LORA, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz, 903-914.2 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Guangdong Asia Hongke Test Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA/Test-Report/AiTSZ-250812012FW1-FCC-Test-Report-2-4G-WIFI-8765564.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765564>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765564.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/Test-Report/AiTSZ-250812012FW1-FCC-Test-Report-2-4G-WIFI-8765564.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf" \
-   "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPC6LORA/Test-Report/AiTSZ-250812012FW1-FCC-Test-Report-2-4G-WIFI-8765564.pdf" -o "2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf"
-echo "f04da403673dd3ba95069c133854f19d984a07c712f749fc126aafa62782ddac  2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf.ARCHIVED.md b/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf.ARCHIVED.md
deleted file mode 100644
index df6f0a0..0000000
--- a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 449,566 B (0.43 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 449,566 B (0.43 MiB) |
-| SHA-256 | `00cfed2f15bf7bbf3f4b65723213d0b1896c00b0d4d7305b616a83e2ff8786bc` |
-| FCC ID | **`2AN3WM5STAMPC6LORA`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | AiTSZ-250812012FW5_FCC RF EXPOSURE |
-| FCC document id | 8765567 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Stamp C6LORA, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz, 903-914.2 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Guangdong Asia Hongke Test Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA/RF-Exposure-Info/AiTSZ-250812012FW5-FCC-RF-EXPOSURE-8765567.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765567>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765567.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/RF-Exposure-Info/AiTSZ-250812012FW5-FCC-RF-EXPOSURE-8765567.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf" \
-   "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPC6LORA/RF-Exposure-Info/AiTSZ-250812012FW5-FCC-RF-EXPOSURE-8765567.pdf" -o "2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf"
-echo "00cfed2f15bf7bbf3f4b65723213d0b1896c00b0d4d7305b616a83e2ff8786bc  2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf.ARCHIVED.md b/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index 1876218..0000000
--- a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPC6LORA-eut-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 1,252,196 B (1.19 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,252,196 B (1.19 MiB) |
-| SHA-256 | `c1d9b24c18c383c7c8a090c70d4a6b6e484ab4f2b413fa4a81d4fb6891920ef4` |
-| FCC ID | **`2AN3WM5STAMPC6LORA`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | EUT External photos |
-| FCC document id | 8765573 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Stamp C6LORA, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz, 903-914.2 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Guangdong Asia Hongke Test Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA/External-Photos/EUT-External-photos-8765573.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765573>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765573.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/External-Photos/EUT-External-photos-8765573.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf" \
-   "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPC6LORA/External-Photos/EUT-External-photos-8765573.pdf" -o "2AN3WM5STAMPC6LORA-eut-external-photos.pdf"
-echo "c1d9b24c18c383c7c8a090c70d4a6b6e484ab4f2b413fa4a81d4fb6891920ef4  2AN3WM5STAMPC6LORA-eut-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-internal-photos.pdf b/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-internal-photos.pdf
deleted file mode 100644
index 39474fb..0000000
Binary files a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-eut-internal-photos.pdf and /dev/null differ
diff --git a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-label-location.pdf b/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-label-location.pdf
deleted file mode 100644
index 11f6dd3..0000000
Binary files a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-label-location.pdf and /dev/null differ
diff --git a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf.ARCHIVED.md b/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index d2e5a3b..0000000
--- a/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5STAMPC6LORA-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,928,952 B (1.84 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,928,952 B (1.84 MiB) |
-| SHA-256 | `30447e175f34062a42acffb08dc49bbb97fa9f4e4a0ea8ca7b071af310dc6038` |
-| FCC ID | **`2AN3WM5STAMPC6LORA`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User manual |
-| FCC document id | 8765609 |
-| Upstream publication date | 2025-11-19 |
-| Grant date | 2025-11-19 |
-| Equipment class | M5Stamp C6LORA, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz, 903-914.2 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Guangdong Asia Hongke Test Technology Limited |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA/User-Manual/User-manual-8765609.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8765609>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5STAMPC6LORA/8765609.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5STAMPC6LORA>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5STAMPC6LORA/User-Manual/User-manual-8765609.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf" \
-   "devices/m5stack/stamp-c6lora/artifacts/certification/2AN3WM5STAMPC6LORA-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5STAMPC6LORA/User-Manual/User-manual-8765609.pdf" -o "2AN3WM5STAMPC6LORA-user-manual.pdf"
-echo "30447e175f34062a42acffb08dc49bbb97fa9f4e4a0ea8ca7b071af310dc6038  2AN3WM5STAMPC6LORA-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/stamp-c6lora/artifacts/certification/README.md b/devices/m5stack/stamp-c6lora/artifacts/certification/README.md
deleted file mode 100644
index abfc47d..0000000
--- a/devices/m5stack/stamp-c6lora/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5STAMPC6LORA`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5STAMPC6LORA`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2025-11-19** |
-| Equipment class | M5Stamp C6LORA, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz, 903-914.2 MHz |
-| Test firm | Guangdong Asia Hongke Test Technology Limited |
-| Source page | <https://fccid.io/2AN3WM5STAMPC6LORA> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5STAMPC6LORA-eut-internal-photos.pdf` | 416,641 | `947b644d1a168f534d4e6f6a0c467b6cfe0115ccad1296cd11ce5e82d8fb9960` | Internal Photos |
-| `2AN3WM5STAMPC6LORA-label-location.pdf` | 199,647 | `c838daa020297b84823ccce6d61d39f8d23a0a81e9437e337ebec49ad951df88` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf.ARCHIVED.md`](2AN3WM5STAMPC6LORA-aitsz-250812012fw1-fcc-test-report-2-4g-wifi.pdf.ARCHIVED.md) | 2,092,093 | Test Report |
-| [`2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf.ARCHIVED.md`](2AN3WM5STAMPC6LORA-aitsz-250812012fw5-fcc-rf-exposure.pdf.ARCHIVED.md) | 449,566 | RF Exposure Info |
-| [`2AN3WM5STAMPC6LORA-eut-external-photos.pdf.ARCHIVED.md`](2AN3WM5STAMPC6LORA-eut-external-photos.pdf.ARCHIVED.md) | 1,252,196 | External Photos |
-| [`2AN3WM5STAMPC6LORA-user-manual.pdf.ARCHIVED.md`](2AN3WM5STAMPC6LORA-user-manual.pdf.ARCHIVED.md) | 1,928,952 | Users Manual |
-
-Archived total: **4 files, 5.46 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 0.59 MiB** |
-| Archived | **4 files, 5.46 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/m5stack/stamp-c6lora/certification-and-compliance.md b/devices/m5stack/stamp-c6lora/certification-and-compliance.md
deleted file mode 100644
index f027ead..0000000
--- a/devices/m5stack/stamp-c6lora/certification-and-compliance.md
+++ /dev/null
@@ -1,123 +0,0 @@
-# Certification and compliance — stamp-c6lora
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5STAMPC6LORA` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5STAMPC6LORA`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **2412-2462 MHz Original Equipment 2025-11-19 902.3-914.9 MHz Original Equipment 2025-11-19** |
-| Application purpose | Original Equipment |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11), **902.3-914.9 MHz**, **903-914.2 MHz** |
-| Test firm | Guangdong Asia Hongke Test Technology Limited |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 19 available, 4 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5STAMPC6LORA` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block diagram [Block Diagram]
-- Schematic [Schematics]
-- Operation Description [Operational Description]
-- USA-DueDigilenceLetter_V0.1 [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-EUT-External-photos.pdf` | 1,252,196 | `c1d9b24c18c383c7…` |
-| `ID-Label-Location-Info-Label-location.pdf` | 199,647 | `c838daa020297b84…` |
-| `Internal-Photos-EUT-Internal-photos.pdf` | 416,641 | `947b644d1a168f53…` |
-| `RF-Exposure-Info-AiTSZ-250812012FW5_FCC-RF-EXPOSURE.pdf` | 449,566 | `00cfed2f15bf7bbf…` |
-| `Test-Report-AiTSZ-250812012FW1_FCC-Test-Report_2.4G-WIFI.pdf` | 2,092,093 | `f04da403673dd3ba…` |
-| `Users-Manual-User-manual.pdf` | 1,928,952 | `30447e175f34062a…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5STAMPC6LORA/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5STAMPC6LORA/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/stamp-c6lora/market-and-pricing.md b/devices/m5stack/stamp-c6lora/market-and-pricing.md
deleted file mode 100644
index eb387b2..0000000
--- a/devices/m5stack/stamp-c6lora/market-and-pricing.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Market and pricing — stamp-c6lora
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| M5Stamp C6LoRa Module (ESP32-C6, SX1262) | 2026-03-13 | Default Title | `S012` | **USD 12.95** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 12.95, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/m5stamp-c6lora-module-esp32-c6-sx1262`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `S012`.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/unit-c6l/README.md b/devices/m5stack/unit-c6l/README.md
deleted file mode 100644
index 1df57ff..0000000
--- a/devices/m5stack/unit-c6l/README.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# M5Stack Unit C6L for Meshtastic (SKU U202)
-
-> **Light record, but read §2** — this is the **only** M5Stack LoRa product that gives an
-> *original* Cardputer a working Meshtastic node, and it does it by not being a peripheral
-> at all. Published **2025-10-10**, USD **22.90**. Snapshot 2026-09-04; vendor
-> documentation + upstream Meshtastic; no hardware.
-
-## 1. Identity
-
-| Property | Value |
-|---|---|
-| SKU | **U202** |
-| Store title | *M5Stack C6L Unit for Meshtastic (SX1262, ESP32-C6)* |
-| **Published** | **2025-10-10** |
-| Price | USD **22.90** |
-| Core | **[Stamp C6LoRa](../stamp-c6lora/README.md)** module — ESP32-C6 + SX1262 + RF switch |
-| SoC | ESP32-C6, RISC-V 160 MHz HP core + 20 MHz LP core, **16 MB flash**, **Wi-Fi 6 (2.4 GHz)** |
-| LoRa | **SX1262**, 868 – 923 MHz, **+22 dBm**, **−147 dBm** |
-| Display | **SSD1306** 0.66" OLED, 64 × 48 |
-| Indicators | **WS2812C** RGB LED, buzzer, user button |
-| Protection | **AW32901FCR** over-voltage protection |
-| Antennas | **two SMA** — 2.4 GHz Wi-Fi (84 mm, 3 dBi) and LoRa (108 mm, 3 dBi). Connectors described as *"female thread, female pin"* |
-| Expansion | HY2.0-4P Grove; LEGO-compatible holes |
-| Power | DC 5 V via USB-C **or** via the Grove port |
-| Size / weight | 62.0 × 24.0 × 8.0 mm · 13.6 g (excl. antennas) |
-
-### Power, by state
-
-| State | Current |
-|---|---|
-| Sleep (HY2.0-4P powered) | **696.86 µA** |
-| Sleep (USB-C powered) | 866.42 µA |
-| LoRa RX standby (USB-C) | **85.18 mA** |
-| LoRa max-power continuous TX (USB-C) | **80.02 mA** |
-
-> ⚠ **RX standby draws *more* than continuous TX** in M5Stack's own table (85.18 vs
-> 80.02 mA). That is counter-intuitive but not impossible — the SX1262 in LDO regulation
-> mode has a high receive current, and the transmit figure may be measured with a duty
-> cycle. **The vendor states no measurement conditions.** Recorded as published, flagged as
-> suspicious; do not build a power budget on it without measuring.
-
-## 2. ⭐ Why this is the answer for an *original* Cardputer
-
-Unit C6L **is its own Meshtastic node.** It has its own MCU, its own flash, its own screen,
-its own radio, its own antenna and its own power input. The Grove cable is a *link to a
-companion*, not a peripheral bus.
-
-- **Upstream Meshtastic variant exists:**
-  [`variants/esp32c6/m5stack_unitc6l/`](https://github.com/meshtastic/firmware/tree/master/variants/esp32c6/m5stack_unitc6l)
-  — `variant.h`, `variant.cpp`, `platformio.ini`, `pins_arduino.h`. `executed-success` on
-  the tree listing, 2026-09-04.
-- **Protobuf hardware model:** `meshtastic_HardwareModel_M5STACK_C6L = 111` — the entry
-  immediately before `M5STACK_CARDPUTER_ADV = 112`.
-
-So an original Cardputer running a **client** firmware (MeshClient, `cardtastic`,
-`sigil-03/cardputer-meshtastic-client`, or the `Cardkb_emulator` trick) plus a Unit C6L
-gives you a keyboard-driven Meshtastic experience on hardware that **cannot take a Cap**.
-That is the practical, community-visible route, and it is why the "older LoRa extension for
-the Cardputer" question has a different answer depending on which Cardputer you mean.
-
-⚠ The exact Cardputer↔C6L transport (BLE companion, serial-over-Grove, or both) was **not
-verified** by this pass. Recorded as `inferred` from the architecture; someone should check
-before promising it works.
-
-## 3. Related
-
-- [`../stamp-c6lora/README.md`](../stamp-c6lora/README.md) — the module inside it
-- [`components/semtech/sx1262`](../../../components/semtech/sx1262/README.md)
-- [`components/diodes-incorporated/pi4ioe5v6408`](../../../components/diodes-incorporated/pi4ioe5v6408/README.md) — inside the Stamp module
-- [`../cap-lora-1262/README.md`](../cap-lora-1262/README.md) — the Cardputer-**Adv** alternative
-
-## 4. Gaps
-
-- `docs.m5stack.com` slug not resolved (`/en/unit/UnitC6L` and `/en/unit/Unit-C6L` both
-  **404**). All specification data here comes from the **store listing**, not the
-  documentation page.
-- Schematic, pin map and the Meshtastic variant's contents **not fetched**.
-- The RX-vs-TX current anomaly (§1) unexplained.
-- Cardputer↔C6L pairing mechanics unverified.
-
-## 5. Sources
-
-| ID | Title | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|
-| C-1 | U202 store listing JSON | primary | `https://shop.m5stack.com/products/m5stack-c6l-unit-for-meshtastic-sx1262-esp32-c6.json` | 2026-09-04 | Published 2025-10-10, USD 22.90, full specification |
-| C-2 | Meshtastic repository tree | primary | `api.github.com/repos/meshtastic/firmware/git/trees/master?recursive=1` | 2026-09-04 | `variants/esp32c6/m5stack_unitc6l/` exists (4 files) |
-| C-3 | Meshtastic `mesh.pb.h` | primary | `github.com/meshtastic/firmware/blob/master/src/mesh/generated/meshtastic/mesh.pb.h` | 2026-09-04 | `M5STACK_C6L = 111` |
diff --git a/devices/m5stack/unit-c6l/acquisition/manifest.json b/devices/m5stack/unit-c6l/acquisition/manifest.json
deleted file mode 100644
index 4d307a5..0000000
--- a/devices/m5stack/unit-c6l/acquisition/manifest.json
+++ /dev/null
@@ -1,224 +0,0 @@
-{
- "record": "devices/m5stack/unit-c6l",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2AN3WM5UNITC6L-8610513",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5UNITC6L/Test-Report/Antenna-Specification-8610513.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610513",
-    "https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610513.pdf",
-    "https://fccid.io/2AN3WM5UNITC6L",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/Test-Report/Antenna-Specification-8610513.pdf"
-   ],
-   "sha256": "ff22c8be503d78356926d3b6002d2c502fba2b6d4b3a1fdc126d659253ce05d8",
-   "bytes": 886501,
-   "destination": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-08-26",
-   "fcc_id": "2AN3WM5UNITC6L",
-   "fcc_document_id": "8610513",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Specification",
-   "grant_date": "2025-08-26",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf",
-   "placeholder": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/unit-c6l",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5UNITC6L-8610509",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5UNITC6L/External-Photos/External-Photos-8610509.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610509",
-    "https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610509.pdf",
-    "https://fccid.io/2AN3WM5UNITC6L",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/External-Photos/External-Photos-8610509.pdf"
-   ],
-   "sha256": "da57901ddd9a17f13444016de61985749404dcf83223ce0c57fcbf4b3af0df2b",
-   "bytes": 569103,
-   "destination": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-08-26",
-   "fcc_id": "2AN3WM5UNITC6L",
-   "fcc_document_id": "8610509",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2025-08-26",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf",
-   "placeholder": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/unit-c6l",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5UNITC6L-8610510",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5UNITC6L/Internal-Photos/Internal-Photos-8610510.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610510",
-    "https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610510.pdf",
-    "https://fccid.io/2AN3WM5UNITC6L",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/Internal-Photos/Internal-Photos-8610510.pdf"
-   ],
-   "sha256": "b82365ca19e964d208a3474e9fccb916b4955e308c12acdef4fbbdef8894ad5b",
-   "bytes": 787288,
-   "destination": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-internal-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-08-26",
-   "fcc_id": "2AN3WM5UNITC6L",
-   "fcc_document_id": "8610510",
-   "exhibit_type": "Internal Photos",
-   "exhibit_title_as_filed": "Internal Photos",
-   "grant_date": "2025-08-26",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/unit-c6l",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5UNITC6L-8610515",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5UNITC6L/Label/Label-and-Label-Location-8610515.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610515",
-    "https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610515.pdf",
-    "https://fccid.io/2AN3WM5UNITC6L",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/Label/Label-and-Label-Location-8610515.pdf"
-   ],
-   "sha256": "256bce1055c514bc70b8b7964e69637d3a3ce56b55668cf7ba2ed1dce4e1fec1",
-   "bytes": 362703,
-   "destination": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-label-and-label-location.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-08-26",
-   "fcc_id": "2AN3WM5UNITC6L",
-   "fcc_document_id": "8610515",
-   "exhibit_type": "ID Label/Location Info",
-   "exhibit_title_as_filed": "Label and Label Location",
-   "grant_date": "2025-08-26",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/m5stack/unit-c6l",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5UNITC6L-8610514",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5UNITC6L/RF-Exposure-Info/RF-Exposure-Information-8610514.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610514",
-    "https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610514.pdf",
-    "https://fccid.io/2AN3WM5UNITC6L",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/RF-Exposure-Info/RF-Exposure-Information-8610514.pdf"
-   ],
-   "sha256": "64c244b5def47291adbd108e001458d221d37d5fcab4d9406df19ecfdc90a584",
-   "bytes": 363127,
-   "destination": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-08-26",
-   "fcc_id": "2AN3WM5UNITC6L",
-   "fcc_document_id": "8610514",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Information",
-   "grant_date": "2025-08-26",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf",
-   "placeholder": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/unit-c6l",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2AN3WM5UNITC6L-8610519",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2AN3WM5UNITC6L/User-Manual/User-Manual-8610519.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610519",
-    "https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610519.pdf",
-    "https://fccid.io/2AN3WM5UNITC6L",
-    "https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/User-Manual/User-Manual-8610519.pdf"
-   ],
-   "sha256": "c464ca0b385d85e3e280ac1684752a983dd0700a39cc102a8188bf49c99e8dae",
-   "bytes": 440093,
-   "destination": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2025-08-26",
-   "fcc_id": "2AN3WM5UNITC6L",
-   "fcc_document_id": "8610519",
-   "exhibit_type": "Users Manual",
-   "exhibit_title_as_filed": "User Manual",
-   "grant_date": "2025-08-26",
-   "applicant": "M5Stack Technology Co.,Ltd \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen Accurate Technology Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf",
-   "placeholder": "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/m5stack/unit-c6l",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf.ARCHIVED.md b/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf.ARCHIVED.md
deleted file mode 100644
index 2ba3697..0000000
--- a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5UNITC6L-antenna-specification.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 886,501 B (0.85 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 886,501 B (0.85 MiB) |
-| SHA-256 | `ff22c8be503d78356926d3b6002d2c502fba2b6d4b3a1fdc126d659253ce05d8` |
-| FCC ID | **`2AN3WM5UNITC6L`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Specification |
-| FCC document id | 8610513 |
-| Upstream publication date | 2025-08-26 |
-| Grant date | 2025-08-26 |
-| Equipment class | M5Unit C6L, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5UNITC6L/Test-Report/Antenna-Specification-8610513.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610513>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610513.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5UNITC6L>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/Test-Report/Antenna-Specification-8610513.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf" \
-   "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-antenna-specification.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5UNITC6L/Test-Report/Antenna-Specification-8610513.pdf" -o "2AN3WM5UNITC6L-antenna-specification.pdf"
-echo "ff22c8be503d78356926d3b6002d2c502fba2b6d4b3a1fdc126d659253ce05d8  2AN3WM5UNITC6L-antenna-specification.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf.ARCHIVED.md b/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index e1f4dbc..0000000
--- a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5UNITC6L-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 569,103 B (0.54 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 569,103 B (0.54 MiB) |
-| SHA-256 | `da57901ddd9a17f13444016de61985749404dcf83223ce0c57fcbf4b3af0df2b` |
-| FCC ID | **`2AN3WM5UNITC6L`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 8610509 |
-| Upstream publication date | 2025-08-26 |
-| Grant date | 2025-08-26 |
-| Equipment class | M5Unit C6L, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5UNITC6L/External-Photos/External-Photos-8610509.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610509>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610509.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5UNITC6L>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/External-Photos/External-Photos-8610509.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf" \
-   "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5UNITC6L/External-Photos/External-Photos-8610509.pdf" -o "2AN3WM5UNITC6L-external-photos.pdf"
-echo "da57901ddd9a17f13444016de61985749404dcf83223ce0c57fcbf4b3af0df2b  2AN3WM5UNITC6L-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-internal-photos.pdf b/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-internal-photos.pdf
deleted file mode 100644
index b465b3a..0000000
Binary files a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-internal-photos.pdf and /dev/null differ
diff --git a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-label-and-label-location.pdf b/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-label-and-label-location.pdf
deleted file mode 100644
index 2f54499..0000000
Binary files a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-label-and-label-location.pdf and /dev/null differ
diff --git a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf.ARCHIVED.md b/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf.ARCHIVED.md
deleted file mode 100644
index 8dec41a..0000000
--- a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5UNITC6L-rf-exposure-information.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 363,127 B (0.35 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 363,127 B (0.35 MiB) |
-| SHA-256 | `64c244b5def47291adbd108e001458d221d37d5fcab4d9406df19ecfdc90a584` |
-| FCC ID | **`2AN3WM5UNITC6L`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Information |
-| FCC document id | 8610514 |
-| Upstream publication date | 2025-08-26 |
-| Grant date | 2025-08-26 |
-| Equipment class | M5Unit C6L, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5UNITC6L/RF-Exposure-Info/RF-Exposure-Information-8610514.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610514>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610514.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5UNITC6L>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/RF-Exposure-Info/RF-Exposure-Information-8610514.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf" \
-   "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-rf-exposure-information.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5UNITC6L/RF-Exposure-Info/RF-Exposure-Information-8610514.pdf" -o "2AN3WM5UNITC6L-rf-exposure-information.pdf"
-echo "64c244b5def47291adbd108e001458d221d37d5fcab4d9406df19ecfdc90a584  2AN3WM5UNITC6L-rf-exposure-information.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf.ARCHIVED.md b/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 54e838c..0000000
--- a/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2AN3WM5UNITC6L-user-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 440,093 B (0.42 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 440,093 B (0.42 MiB) |
-| SHA-256 | `c464ca0b385d85e3e280ac1684752a983dd0700a39cc102a8188bf49c99e8dae` |
-| FCC ID | **`2AN3WM5UNITC6L`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | User Manual |
-| FCC document id | 8610519 |
-| Upstream publication date | 2025-08-26 |
-| Grant date | 2025-08-26 |
-| Equipment class | M5Unit C6L, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2AN3WM5UNITC6L/User-Manual/User-Manual-8610519.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8610519>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2AN3WM5UNITC6L/8610519.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2AN3WM5UNITC6L>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2AN3WM5UNITC6L/User-Manual/User-Manual-8610519.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf" \
-   "devices/m5stack/unit-c6l/artifacts/certification/2AN3WM5UNITC6L-user-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2AN3WM5UNITC6L/User-Manual/User-Manual-8610519.pdf" -o "2AN3WM5UNITC6L-user-manual.pdf"
-echo "c464ca0b385d85e3e280ac1684752a983dd0700a39cc102a8188bf49c99e8dae  2AN3WM5UNITC6L-user-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/m5stack/unit-c6l/artifacts/certification/README.md b/devices/m5stack/unit-c6l/artifacts/certification/README.md
deleted file mode 100644
index 989c55b..0000000
--- a/devices/m5stack/unit-c6l/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2AN3WM5UNITC6L`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2AN3WM5UNITC6L`** |
-| Applicant | M5Stack Technology Co.,Ltd 🇨🇳 |
-| Granted | **2025-08-26** |
-| Equipment class | M5Unit C6L, 2402-2480 MHz, 2412-2462 MHz, 902.3-914.9 MHz |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Source page | <https://fccid.io/2AN3WM5UNITC6L> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2AN3WM5UNITC6L-internal-photos.pdf` | 787,288 | `b82365ca19e964d208a3474e9fccb916b4955e308c12acdef4fbbdef8894ad5b` | Internal Photos |
-| `2AN3WM5UNITC6L-label-and-label-location.pdf` | 362,703 | `256bce1055c514bc70b8b7964e69637d3a3ce56b55668cf7ba2ed1dce4e1fec1` | ID Label/Location Info |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2AN3WM5UNITC6L-antenna-specification.pdf.ARCHIVED.md`](2AN3WM5UNITC6L-antenna-specification.pdf.ARCHIVED.md) | 886,501 | Test Report |
-| [`2AN3WM5UNITC6L-external-photos.pdf.ARCHIVED.md`](2AN3WM5UNITC6L-external-photos.pdf.ARCHIVED.md) | 569,103 | External Photos |
-| [`2AN3WM5UNITC6L-rf-exposure-information.pdf.ARCHIVED.md`](2AN3WM5UNITC6L-rf-exposure-information.pdf.ARCHIVED.md) | 363,127 | RF Exposure Info |
-| [`2AN3WM5UNITC6L-user-manual.pdf.ARCHIVED.md`](2AN3WM5UNITC6L-user-manual.pdf.ARCHIVED.md) | 440,093 | Users Manual |
-
-Archived total: **4 files, 2.15 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 1.10 MiB** |
-| Archived | **4 files, 2.15 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/m5stack/unit-c6l/certification-and-compliance.md b/devices/m5stack/unit-c6l/certification-and-compliance.md
deleted file mode 100644
index 3f222c4..0000000
--- a/devices/m5stack/unit-c6l/certification-and-compliance.md
+++ /dev/null
@@ -1,122 +0,0 @@
-# Certification and compliance — unit-c6l
-
-Compiled **2026-09-11** by the certification/market pass. Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware. Where a mark is reported as present it was read from a photograph inside an FCC exhibit.
-
----
-
-## 1. Summary
-
-**FCC: granted.** 1 filing(s) apply directly.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2AN3WM5UNITC6L` |
-| **CE / RED (EU)** | ⚠ no published DoC located; CE mark observed on M5Stack labels (§3) |
-| **UKCA** | ⚠ not determined (§3) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§3) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§3) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§3) |
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Both
-controls were run on **2026-09-11** in the same session, against the same host, with the same tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AC7Z-ESPS3WROOM1U` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2AN3WM5CAPLORA868` | **404** | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**4/4 positive → 200. 5/5 negative → 404.** Raw run: `scratch/market-and-certification/logs/fcc-controls.txt`.
-
-Beyond the ID probes, the whole grantee was enumerated rather than guessed: `2AN3W` yielded
-**59** FCC IDs, `2ASYE` **33**, `2AC7Z` **78**, `2BTR9` **5**. A product absent from a complete
-grantee listing is absent, not merely un-found.
-
----
-
-## 2b. The filings
-
-### `2AN3WM5UNITC6L`
-
-| Field | Value |
-|---|---|
-| Applicant | M5Stack Technology Co.,Ltd |
-| Grantee code | `2AN3W` — registered 2017-10-23, 59 FCC IDs total |
-| Final action date | **902.3-914.9 MHz Original Equipment 2025-08-26** |
-| Application purpose | Final Action Date 902.3-914.9 MHz Original Equipment 2025-08-26 |
-| Frequency ranges | **2402-2480 MHz** (BLE), **2412-2462 MHz** (Wi-Fi 2.4 GHz, US channels 1–11), **902.3-914.9 MHz** |
-| Test firm | Shenzhen Accurate Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Exhibit rows | 16 available, 3 metadata-only |
-| Filing page | `https://fccid.io/2AN3WM5UNITC6L` — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld (confidentiality granted):**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operation Description [Operational Description]
-
-**Exhibits obtained** — US Government public records, redistribution `allowed`. Downloaded 2026-09-11, magic bytes validated (`%PDF-`):
-
-| Exhibit | Bytes | SHA-256 (first 16) |
-|---|---|---|
-| `External-Photos-External-Photos.pdf` | 569,103 | `da57901ddd9a17f1…` |
-| `ID-Label-Location-Info-Label-and-Label-Location.pdf` | 362,703 | `256bce1055c514bc…` |
-| `Internal-Photos-Internal-Photos.pdf` | 787,288 | `b82365ca19e964d2…` |
-| `RF-Exposure-Info-RF-Exposure-Information.pdf` | 363,127 | `64c244b5def47291…` |
-| `Test-Report-Antenna-Specification.pdf` | 886,501 | `ff22c8be503d7835…` |
-| `Users-Manual-User-Manual.pdf` | 440,093 | `c464ca0b385d85e3…` |
-
-Held at `scratch/market-and-certification/fcc/2AN3WM5UNITC6L/` (**unstaged**, 198 MB total for the pass). Reacquire with `https://fccid.io/2AN3WM5UNITC6L/<Type-Slug>/<Doc-Slug>.pdf` and a `curl` UA — see [the method guide](../../../guides/research/finding-certification-records.md).
-
----
-
-## 3. Other jurisdictions
-
-| Regime | Result | Evidence |
-|---|---|---|
-| **EU CE / RED** | ⚠ **No published Declaration of Conformity located.** `shop.m5stack.com/pages/certificate`, `docs.m5stack.com/en/certificate` and `www.lilygo.cc/pages/certification` all **404** (2026-09-11) | CE is a *self-declaration* regime — **there is no database to search**. Absence of a published DoC is not absence of conformity |
-| **CE mark on product** | ✅ **Present.** The FCC `ID Label` exhibit photograph for the Cardputer ADV shows a **CE mark**, an **FCC logo**, a **WEEE crossed-bin** and a recycling mark printed on the M5StampS3A module label | Read visually from the rendered exhibit image, not from a text layer — see the trap in §5 of the method guide |
-| **UKCA** | ⚠ **Not determined.** No UKCA database exists; no UKCA mark was legible on the labels inspected | — |
-| **China SRRC (型号核准)** | ❌ **Not achieved.** `wireless.miit.gov.cn` and `srrccn.org` both **failed to connect** (`000`) on 2026-09-11 | Method failure, **not** an absence finding. Do not read this row as "not SRRC approved" |
-| **China CCC** | ⚠ **Not achieved.** `cnca.gov.cn` reachable (200) but the searchable register was not reached | As above |
-| **Japan MIC 技適** | ⚠ **Not searched.** `tele.soumu.go.jp/giteki/SearchServlet` reachable (**200**, 2026-09-11) but is form-driven and was not queried | The Cardputer has a JP variant, so this is a **real gap**, not an absence |
-| **ISED Canada** | ⚠ **Not achieved.** `sms-sgs.ic.gc.ca` returned **503** on 2026-09-11. No IC number was legible on any label inspected | Retry later |
-
-**Read this table carefully.** Only two rows are findings (`CE mark present`, `no published
-DoC`). Every other row records that *the search did not run*, which is a different thing from
-a negative result.
-
-
----
-
-## 4. What this does **not** establish
-
-- **No hardware was inspected.** The device in front of you may be a different revision than the one the test lab submitted.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit; 47 CFR §2.935 permits an **e-label** in software instead.
-- **Absence of a mark is not absence of a grant.** The reverse error was made about Xteink by the 2026-09-04 sweep and is corrected in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md).
-- **The SRRC, CCC, MIC and ISED rows in §3 are not negative results.** Those searches did not run. Treat them as open work.
-- **Schematics are withheld** on 26 of 26 filings examined, along with block diagrams and operational descriptions. The FCC is not a route to a schematic for these vendors.
-
-## 5. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| C-1 | FCC Equipment Authorization filings | FCC (via fccid.io mirror) | primary (US Govt record), accessed through a mirror | regulatory record | `https://fccid.io/` | 2026-09-11 | Grant existence, dates, frequencies, exhibits |
-| C-2 | Grantee listing, `2AN3W` etc. | FCC / fccid.io | primary via mirror | regulatory record | `https://fccid.io/<grantee>` | 2026-09-11 | Complete enumeration per company |
-| C-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
diff --git a/devices/m5stack/unit-c6l/market-and-pricing.md b/devices/m5stack/unit-c6l/market-and-pricing.md
deleted file mode 100644
index 1f72482..0000000
--- a/devices/m5stack/unit-c6l/market-and-pricing.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Market and pricing — unit-c6l
-
-## Dated price observations — 2026-09-11 (certification/market pass)
-
-Added **2026-09-11**, append-only. Earlier sections above are another session's work and are left exactly as written.
-
-> ⚠ **Date note.** The session brief for this pass said 2026-09-07. The host clock, the `date:` response headers from two independent servers, and the `updated_at` field on every live product below all say **2026-09-11**. The later date is used because it is what actually happened. See `scratch/market-and-certification/README.md`.
-
-### Method and source
-
-Single request to the vendor's Shopify catalogue endpoint, `https://shop.m5stack.com/products.json?limit=250&page=<n>`, retrieved **2026-09-11**. This is the **strongest available evidence**: it returns `published_at`, `updated_at`, every variant, SKU, price and stock flag in one response, with no rendering and no scraping heuristics.
-
-- **MSRP vs street price:** these are the **vendor's own list prices** — MSRP, not street. No discount, coupon or quantity break is reflected.
-- **Currency:** USD as served by the store. No conversion was applied, so no conversion date applies. ⚠ LilyGO's USD prices carry odd cents (e.g. 8.04, 98.79), which is consistent with **machine conversion from CNY**; the underlying CNY price and its conversion date are **not exposed by the endpoint** and are therefore unknown.
-- **Ships from:** Shenzhen, CN.
-- **Stock evidence:** the per-variant `available` boolean, quoted verbatim below.
-- **Condition:** new. **Genuine** — this is the manufacturer's own storefront.
-- **Tax/duty:** not shown by the endpoint; not established.
-
-### Observations
-
-| Product (store title) | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| M5Stack C6L Unit for Meshtastic (SX1262, ESP32-C6) | 2025-10-10 | Default Title | `U202` | **USD 22.90** | ✅ yes |
-
-Citation form required by [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*, for the first row:
-
-> *USD 22.90, 1 unit, retrieved 2026-09-11, `https://shop.m5stack.com/products/m5stack-c6l-unit-for-meshtastic-sx1262-esp32-c6`, ships from Shenzhen, CN*
-
-### Normalisation and caveats
-
-SKU `U202`.
-
-### Coverage not achieved, and why
-
-The task asked for AliExpress, Amazon/eBay, Taobao/JD and used/refurbished sampling. **None was obtained.** Measured 2026-09-11 from this host:
-
-| Channel | Result |
-|---|---|
-| AliExpress search | HTTP 200 but **bot-wall page** |
-| `m5stack.aliexpress.com` | HTTP 200 but **bot-wall page** |
-| eBay search | **HTTP 403** |
-| Amazon search | HTTP 200, **zero prices in the HTML** (JS shell) |
-| Taobao search | HTTP 200, **34 KB SPA shell**, no listings |
-| JD search | HTTP 200, **2.7 KB shell**, no listings |
-| Used / refurbished | **not attempted** — every marketplace above was already blocked |
-
-**No marketplace, clone or used-market price is reported, because none was observed.** A 200 response containing no prices is a failure, not a datum. This leaves the sweep's gap *partially* open: official-store pricing is now dated and complete; **street, clone and used pricing remain unsampled.**
-
-### Sample size
-
-Inspected catalogue: **664 products** (`shop.m5stack.com`), **214** (`www.lilygo.cc`), **25** (`xteink.com`), enumerated in full on 2026-09-11. Statements of the form "no such product exists" above are against that complete enumeration, not against a search-result page.
-
diff --git a/devices/m5stack/unit-lora-e220/README.md b/devices/m5stack/unit-lora-e220/README.md
deleted file mode 100644
index 1a8e755..0000000
--- a/devices/m5stack/unit-lora-e220/README.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# M5Stack LoRa Unit (E220) — U170 (920 MHz / JP) and U170-433 (433 MHz)
-
-> **Light record.** Included because it is one of the *actual* answers to "what LoRa could
-> you attach to a Cardputer before the Cap existed" — a **Grove/UART LoRa modem** that works
-> on **any** M5Stack host with a HY2.0-4P port, including the **original Cardputer**.
-> Snapshot 2026-09-04. Vendor documentation only; no schematic fetched, no hardware.
-
-## 1. Identity
-
-| | U170 | U170-433 |
-|---|---|---|
-| Doc name | **Unit LoRaE220-920** ("JP version") | **Unit LoRaE220-433** |
-| Store title | LoRa Unit with Antenna (E220) | LoRa Unit 433MHz with Antenna (E220) |
-| **Published** | **2023-10-20** | **2024-07-12** |
-| Price | USD 33.00 | USD 12.95 |
-| Module | **E220-900T22S (JP)** — *Telec cert `001-P01730`* | **E220-400T22S** |
-| **Radio chip** | **Semtech LLCC68** | **Semtech LLCC68** |
-| Band | **920.6 – 928.0 MHz** | default **433 MHz**, range **410.125 – 493.125 MHz** |
-| Max TX | **13 dBm** (~20 mW) | **22 dBm**, software-selectable |
-| RX sensitivity | not stated | **−129 dBm** |
-| Interface | **UART**, HY2.0-4P Grove | **UART 115200**, HY2.0-4P Grove |
-| Antenna | 2.5 dBi, 110 mm, **SMA male** | same |
-| Size / weight | 71.4 × 24.0 × 8.0 mm · 19.2 g | 71.4 × 24.0 × 8.0 mm · 19.5 g |
-
-**U170 is the older of the two by nine months and it predates the Cardputer itself by three
-days** (Cardputer K132 published 2023-10-13).
-
-## 2. Why it matters to the Cardputer question
-
-The original Cardputer (K132/K132-V11) has **only** a HY2.0-4P Grove port
-(`PORT.CUSTOM`, G2/G1) and no expansion bus. A **UART** LoRa modem on that port is
-electrically straightforward — G1/G2 are ordinary ESP32-S3 GPIO and can be driven as a
-software or hardware UART.
-
-So the honest statement is: **before the Cardputer-Adv, "LoRa on a Cardputer" meant a
-Grove-attached E220 or LoRaWAN modem, not a LoRa *radio* the host could drive directly.**
-
-⚠ **But it is not a Meshtastic path, and never was.** Meshtastic requires **direct SPI
-access to an SX126x/SX127x/LR11xx**. The E220 hides an LLCC68 behind an **AT-command UART
-modem** with a fixed packet format and DIP-switch modes; the host cannot reach the radio's
-registers. There is no Meshtastic variant for it and there cannot be one without new
-transport code. `executed-success` on the negative: upstream Meshtastic's variant tree has
-no E220/LLCC68 entry of any kind.
-
-## 3. What it is good at
-
-Point-to-point and broadcast serial links. Features named by the vendor: **Wake-on-Radio**
-(wireless wake-up), carrier sensing, communication keys, and four modes selectable with an
-**onboard DIP switch** — transmit, WOR transmit, WOR receive, sleep. That DIP switch is the
-distinguishing usability feature: you can get a working link without writing configuration
-code at all.
-
-Claimed range for U170: *"up to 5 kilometres"* — no method, antenna height or data rate
-given. Treat as marketing.
-
-## 4. Regional variants — the band *is* the SKU
-
-| SKU | Band | Region intent |
-|---|---|---|
-| U170 | 920.6–928.0 MHz | **Japan** — carries a **Telec certification number, `001-P01730`**, printed in the specification table |
-| U170-433 | 410–493 MHz, default 433 | ITU Region 1 ISM / general |
-
-**U170 is the only LoRa product in this whole family with a published regulatory
-identifier.** Every Cap — U201, U214, U219 — has none. Worth noting when comparing them.
-
-## 5. Software
-
-`github.com/m5stack/M5-LoRa-E220` and `github.com/m5stack/M5-LoRa-E220-JP` (both last pushed
-**2025-01-16**). AT-style configuration over UART. RadioLib is **not** applicable — there is
-no SPI to the radio.
-
-## 6. Related components
-
-- **Semtech LLCC68** — a lower-cost SX1262 sibling limited to SF5–SF11. **No component
-  record created** by this pass; see [`components/semtech/sx1262`](../../../components/semtech/sx1262/README.md)
-  for the family context.
-- **Ebyte E220 series** — [`components/ebyte/e220-400t22s`](../../../components/ebyte/e220-400t22s/README.md).
-  The repository already holds a record for the related **[E22-900M22S](../../../components/ebyte/e22-900m22s/README.md)** (E22 = SX1262-based, SPI/UART; E220 = LLCC68-based, UART only) — read both before assuming they are interchangeable.
-
-## 7. Gaps
-
-- Schematics, pinouts and DIP-switch tables **not fetched** (`docs.m5stack.com` slugs for
-  these units were not resolved — `/en/unit/lorae220-433` and `/en/unit/Unit-LoRaE220-JP`
-  both **404**).
-- No firsthand community report of an E220 unit on a Cardputer was found in the 217-post
-  Reddit sample — only generic *"the rf and the ir and the Lora"* accessory mentions
-  ([r/CardPuter 2026-08-30](https://old.reddit.com/r/CardPuter/comments/1w2n1rd/)).
-- Whether M5Stack's Cardputer firmware (M5Launcher/Bruce) exposes these units at all:
-  unknown.
-
-## 8. Sources
-
-| ID | Title | Class | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|
-| E-1 | U170 store listing JSON | primary | `https://shop.m5stack.com/products/lora-unit-jp-version-with-antenna-e220.json` | 2026-09-04 | Published 2023-10-20, USD 33.00, `E220-900T22S (JP) @ Telec (001-P01730)`, LLCC68, 13 dBm |
-| E-2 | U170-433 store listing JSON | primary | `https://shop.m5stack.com/products/lora-unit-433mhz-with-antenna-e220.json` | 2026-09-04 | Published 2024-07-12, USD 12.95, `E220-400T22S@LLCC68`, 22 dBm, −129 dBm, UART 115200 |
-| E-3 | Cardputer documentation | primary | `https://docs.m5stack.com/en/core/Cardputer` | 2026-09-04 | The original Cardputer's only expansion is HY2.0-4P `PORT.CUSTOM` = G2/G1 |
-| E-4 | Meshtastic variant tree | primary | `api.github.com/repos/meshtastic/firmware/git/trees/master?recursive=1` | 2026-09-04 | **Negative:** no LLCC68/E220 variant |
diff --git a/devices/m5stack/unit-lorawan-stm32wle5/README.md b/devices/m5stack/unit-lorawan-stm32wle5/README.md
deleted file mode 100644
index f06e1fe..0000000
--- a/devices/m5stack/unit-lorawan-stm32wle5/README.md
+++ /dev/null
@@ -1,94 +0,0 @@
-# M5Stack LoRaWAN Unit (STM32WLE5) — U184-EU868 / US915 / AS923 / CN470
-
-> **Light record.** The **LoRaWAN** answer for a Grove-equipped M5Stack host, including the
-> original Cardputer. Region is baked into the SKU, which is the correct way to sell a
-> LoRaWAN node. Snapshot 2026-09-04; vendor documentation only, no hardware.
-
-## 1. Identity
-
-| Property | Value |
-|---|---|
-| SKUs | **U184-EU868**, **U184-US915**, **U184-AS923**, **U184-CN470** |
-| **Published** | **2024-12-20** (all four) |
-| Price | USD **21.50** (EU868/US915/AS923), **18.95** (CN470) |
-| Docs | `https://docs.m5stack.com/en/unit/Unit%20LoRaWAN-EU868` |
-| LoRa solution | **STM32WLE5** — 256 KB Flash, 64 KB RAM |
-| Module | **RAK3172** — the docs' Certifications section links *"RAK3172 Module Certification Information"* |
-| Protocol | **LoRaWAN 1.0.3**, **Class A / B / C**; plus LoRa P2P |
-| Activation | **OTAA, ABP** |
-| Interface | **UART, 115200 default, AT commands**, HY2.0-4P **PORT.C** |
-| Grove pinout | Black `GND` · Red `5V` · Yellow **`UART_RX`** · White **`UART_TX`** |
-| RX sensitivity | **−137 dBm** |
-| TX power | max **22 dBm** |
-| P2P range (claimed) | 2 300 m @ 125 kbps · 1 300 m @ 500 kbps |
-| Antenna | 2.8 dBi, 195 mm, **SMA male**, 50 Ω |
-| Size / weight | 71.4 × 24.0 × 8.0 mm · 11.9 g |
-
-### Power, by state (unusually well specified)
-
-| State | Current |
-|---|---|
-| Idle | DC 5 V / **7.23 mA** |
-| **Sleep** | DC 5 V / **28.61 µA** |
-| RX @ 500 kbps | 9.20 mA |
-| TX @ 500 kbps | 11.36 mA |
-| RX @ 125 kbps | 8.43 mA |
-| **TX @ 125 kbps** | **117.16 mA** |
-
-## 2. Predecessor
-
-M5Stack's own comparison table on the same page:
-
-| | **Unit LoRaWAN-EU868 (U184)** | Unit LoRaWAN 868 MHz (U117, **[EOL]**) |
-|---|---|---|
-| Chip | **STM32WLE5** | **ASR6501** |
-| Sensitivity | −137 dBm | −137 dBm |
-| Interface | UART 115200 | UART 115200 |
-| LoRaWAN | **1.0.3, Class A/B/C** | 1.0.1, Class A/C |
-| TX power | max **22 dBm** | max 21 dBm |
-
-The ASR6501 generation (U115 915 MHz / U116 470 MHz / U117 868 MHz, all published
-**2021-05-14**, all now `[EOL]`) predates the Cardputer entirely.
-
-## 3. Cardputer attachability
-
-**Yes, electrically** — it is a UART device on a Grove cable, and both the original
-Cardputer (`PORT.CUSTOM`, G2/G1) and the Cardputer-Adv (`PORT.CUSTOM`, G2/G1, plus the
-Cap's pass-through) can drive it.
-
-**No, for Meshtastic** — an AT-command LoRaWAN modem is a different protocol universe.
-LoRaWAN is star-of-stars to a gateway; Meshtastic is a flooding mesh. They share modulation
-and nothing else.
-
-## 4. Why the region-per-SKU model matters
-
-Contrast with the Caps: **U214 and U219 are single wideband SKUs with no published
-certification**, while U184 splits the product line by regional band plan and points at
-**RAK3172 module certification**. If the wider project needs a *deployable* LoRa link rather
-than a benchtop one, this is the architecture that has the regulatory paperwork behind it —
-at the cost of giving up direct radio control.
-
-## 5. Related
-
-- Siblings: **Atomic DTU LoRaWAN Base** A152-EU868/US915/CN470 (STM32WLE5CC), USD 22.90,
-  published 2025-04-18 — the same silicon in an ATOM-form DTU.
-- **M5Stack LoRaWAN EU868 Module (M148)**, USD 24.90, published 2026-04-24 — Core-bus
-  module, **not Cardputer-attachable**.
-- Libraries: `github.com/m5stack/M5-LoRaWAN`, `M5-LoRaWAN-RAK`, `ATOM_DTU_LoRaWAN` (all last
-  pushed 2025-05-12).
-- Component: [`components/stmicroelectronics/stm32wle5`](../../../components/stmicroelectronics/stm32wle5/README.md)
-
-## 6. Gaps
-
-- Only the **EU868** documentation page was read; US915/AS923/CN470 pages not fetched.
-- Schematic, structure files, AT-command manual and datasheet **located but not fetched**.
-- The RAK3172 certification page (the only regulatory pointer in this family besides the
-  E220-JP's Telec number) **not fetched**.
-- No community report of this unit on any Cardputer.
-
-## 7. Sources
-
-| ID | Title | Class | URL | Retrieved |
-|---|---|---|---|---|
-| W-1 | Unit LoRaWAN-EU868 documentation | primary | `https://docs.m5stack.com/en/unit/Unit%20LoRaWAN-EU868` | 2026-09-04 |
-| W-2 | M5Stack catalogue JSON | primary | `https://shop.m5stack.com/collections/all/products.json` | 2026-09-04 |
diff --git a/devices/nicolai-electronics/tanmatsu/acquisition/README.md b/devices/nicolai-electronics/tanmatsu/acquisition/README.md
index 6debd2c..6375c22 100644
--- a/devices/nicolai-electronics/tanmatsu/acquisition/README.md
+++ b/devices/nicolai-electronics/tanmatsu/acquisition/README.md
@@ -15,7 +15,7 @@ Exits non-zero on any mismatch, so it is usable as a CI or post-clone check.
 ## Re-acquire everything — one command
 
 ```bash
-tools/fetch_sources.sh scratch/tanmatsu/sources
+tools/fetch_sources.sh ../hardware-doc-archive/scratch/tanmatsu/sources
 ```
 
 Clones all twelve repositories at their **pinned commits**, enumerates the badge.team Konsool
@@ -23,7 +23,7 @@ documentation from `sitemap.xml`, and fetches the solder.party product pages. Id
 clones are checked out to the pinned commit rather than re-cloned. ~930 MB.
 
 > **Lesson learned:** the original clones were made under `/tmp` and were destroyed by a system
-> cleanup. Fetch into `scratch/<device>/sources` instead, and keep the
+> cleanup. Fetch into `../hardware-doc-archive/scratch/<device>/sources` instead, and keep the
 > acquisition script **in the repository** so it cannot be lost with the data.
 
 ## Re-acquire step by step
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/keebdeck-keyboard/PROVENANCE.txt b/devices/nicolai-electronics/tanmatsu/artifacts/keebdeck-keyboard/PROVENANCE.txt
index 9e921b6..27f677b 100644
--- a/devices/nicolai-electronics/tanmatsu/artifacts/keebdeck-keyboard/PROVENANCE.txt
+++ b/devices/nicolai-electronics/tanmatsu/artifacts/keebdeck-keyboard/PROVENANCE.txt
@@ -1,3 +1,3 @@
 keebdeck commit: f1c074c47aa48d2eb584dad2ddad2a90ab6b86ed
 retrieved 2026-08-24 from https://github.com/solderparty/keebdeck_keyboard_hw (CERN-OHL v1.2)
-3D STEP models and Eagle/Altium/EasyEDA libraries NOT copied - see archive at ../repo-archive/scratch/tanmatsu/sources/keebdeck_keyboard_hw
+3D STEP models and Eagle/Altium/EasyEDA libraries NOT copied - see archive at ../hardware-doc-archive/scratch/tanmatsu/sources/keebdeck_keyboard_hw
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/ARCHIVED-PRODUCT-PHOTOGRAPHY.md b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/ARCHIVED-PRODUCT-PHOTOGRAPHY.md
index 61cfd83..127d9aa 100644
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/ARCHIVED-PRODUCT-PHOTOGRAPHY.md
+++ b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/ARCHIVED-PRODUCT-PHOTOGRAPHY.md
@@ -2,18 +2,15 @@
 
 **15 images, 5,809,346 bytes**, moved out of the repository on **2026-08-30**. Not deleted.
 
-> **A symlink now stands in for each file at its original path**, pointing through this repo's
-> `archive/` link. With the archive present the paths resolve and the tree behaves as though
-> nothing moved; without it they dangle, and this record is what remains.
+> **These files are absent from the repository.** They are not symlinks and not placeholders-in-place —
+> the paths simply do not exist here any more. This record is the only thing standing in for them,
+> which is why it carries a SHA-256, a byte count and a pinned reacquisition URL for every file.
 >
-> That is why this record still carries a SHA-256, a byte count and a pinned reacquisition URL
-> for every file: **the archive copy is a convenience for whoever holds it, not part of the
-> contract.** It lives outside the repository at a machine-local path, so nothing here may
-> depend on it, and the symlinks are a local nicety rather than a substitute for these hashes.
+> The archive copy is a **convenience for whoever holds it, not part of the contract**: it lives
+> outside the repository at a machine-local path, so nothing here may depend on it.
 
-Even dangling, a symlink says *"this file exists elsewhere"*, where a missing file says nothing.
-But **this record, not the symlink, is the contract**: everything needed to re-obtain and verify
-each file is below.
+link says *"this file exists elsewhere"*, where a missing file says nothing. **This record, not the
+symlink, is the contract**: everything needed to re-obtain and verify each file is below.
 
 ## Why these and not the others
 
@@ -54,34 +51,7 @@ contradiction ("super-speed 480MBit") that had not previously been recorded. Tho
 | `hardware/case/extra4.jpg` | 57,977 | `ad28a3bf7cd1e1ae6000f7f6329c7cbd8b78ccbbb82edd189e62fb837b3984d9` |
 
 Archive root:
-`archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/`
-
-## Sources beyond GitHub
-
-Everything above resolves to GitHub. That is a single custodian and a single company's
-availability decision, so these are recorded as Nicolai Electronics paths that do not depend on it
-(all verified reachable 2026-08-30):
-
-- Vendor documentation (independent of GitHub): <https://nicolaielectronics.nl/docs/tanmatsu/>
-- Vendor site root, if the docs path moves: <https://nicolaielectronics.nl/>
-
-> Vendor pages are **not** equivalent to the pinned commit above: they track the current
-> release, so use them to rediscover the project, then verify against the hashes here.
-
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`Nicolai-Electronics/tanmatsu-documentation`](https://github.com/Nicolai-Electronics/tanmatsu-documentation) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`Nicolai-Electronics/tanmatsu-documentation`](https://github.com/Nicolai-Electronics/tanmatsu-documentation) |
-| Base commit | [`bd3ded51548433bd7d614f5607b7d36f5eed61fa`](https://github.com/Nicolai-Electronics/tanmatsu-documentation/tree/bd3ded51548433bd7d614f5607b7d36f5eed61fa) |
-| Tree at that commit | <https://github.com/Nicolai-Electronics/tanmatsu-documentation/tree/bd3ded51548433bd7d614f5607b7d36f5eed61fa> |
-
-```bash
-git clone https://github.com/Nicolai-Electronics/tanmatsu-documentation
-git -C tanmatsu-documentation checkout bd3ded51548433bd7d614f5607b7d36f5eed61fa
-```
+`../hardware-doc-archive/doc/hardware/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/`
 
 ## Reacquisition
 
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front-2.png b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front-2.png
deleted file mode 120000
index 4a26f73..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front-2.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front-2.png
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front.png b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front.png
deleted file mode 120000
index 461cbec..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/black-front.png
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra1.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra1.jpg
deleted file mode 120000
index 8de8898..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra1.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra1.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra2.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra2.jpg
deleted file mode 120000
index 985b8fb..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra2.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra2.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra3.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra3.jpg
deleted file mode 120000
index 1de0885..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra3.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra3.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra4.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra4.jpg
deleted file mode 120000
index 4fd7a75..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra4.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra4.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra5.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra5.jpg
deleted file mode 120000
index 02b217d..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra5.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/extra5.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main1.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main1.jpg
deleted file mode 120000
index c04bb13..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main1.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main1.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main2.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main2.jpg
deleted file mode 120000
index 4ed251d..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main2.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/case/main2.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/cyberdeck-front.png b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/cyberdeck-front.png
deleted file mode 120000
index 99e0931..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/cyberdeck-front.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/cyberdeck-front.png
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/purple-front.png b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/purple-front.png
deleted file mode 120000
index 1e83b31..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/purple-front.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/purple-front.png
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/red-front.png b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/red-front.png
deleted file mode 120000
index 504d620..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/red-front.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/red-front.png
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side1.png b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side1.png
deleted file mode 120000
index 1142dca..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side1.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side1.png
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side2.png b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side2.png
deleted file mode 120000
index d74f079..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side2.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/hardware/side2.png
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/user_manual/right_side_no_text.jpg b/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/user_manual/right_side_no_text.jpg
deleted file mode 120000
index 1fa9d31..0000000
--- a/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/user_manual/right_side_no_text.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/nicolai-electronics/tanmatsu/artifacts/source-snapshots/tanmatsu-documentation/user_manual/right_side_no_text.jpg
\ No newline at end of file
diff --git a/devices/nicolai-electronics/tanmatsu/bom.md b/devices/nicolai-electronics/tanmatsu/bom.md
index e2dc78d..f5e2dfd 100644
--- a/devices/nicolai-electronics/tanmatsu/bom.md
+++ b/devices/nicolai-electronics/tanmatsu/bom.md
@@ -143,7 +143,7 @@ Two things worth noting:
 - **The Gerbers are dated `2026-02-07`**, eighteen days before the repository's last commit (`640805dd`, 2026-02-25). So the published manufacturing data slightly predates the final commit — check both if you intend to fabricate.
 
 The ZIP is not vendored (it is regenerable from the KiCad source); it lives in the archive at
-`scratch/tanmatsu/sources/tanmatsu-hardware/production/tanmatsu.zip`.
+`../hardware-doc-archive/scratch/tanmatsu/sources/tanmatsu-hardware/production/tanmatsu.zip`.
 
 ## Component records
 
diff --git a/devices/nicolai-electronics/tanmatsu/expansion-boards.md b/devices/nicolai-electronics/tanmatsu/expansion-boards.md
index ab0d531..239c3cf 100644
--- a/devices/nicolai-electronics/tanmatsu/expansion-boards.md
+++ b/devices/nicolai-electronics/tanmatsu/expansion-boards.md
@@ -2,7 +2,7 @@
 
 > What already exists to plug into the two expansion ports, and what you need to build your own.
 > Snapshot **2026-08-24**. All repositories cloned and inspected directly; sources archived under
-> `scratch/tanmatsu/sources/`.
+> `../hardware-doc-archive/scratch/tanmatsu/sources/`.
 > **No hardware was available** — nothing here was built, fitted or powered.
 
 Expansion hardware is developed under the **Konsool** name by Badge.Team, while front panels come
diff --git a/devices/nicolai-electronics/tanmatsu/keyboard.md b/devices/nicolai-electronics/tanmatsu/keyboard.md
index 6af0ee7..0659cf5 100644
--- a/devices/nicolai-electronics/tanmatsu/keyboard.md
+++ b/devices/nicolai-electronics/tanmatsu/keyboard.md
@@ -460,7 +460,7 @@ sheet (86.75 mm) is slightly **wider** than the keypad (85.80 mm).
 | 3D STEP | archive only | `KeebDeck_Keyboard.3dshapes/` (14 MB) — keypad, dome sheet **and `ADBM-A350.step`**, the optical finger-navigation module |
 
 Non-KiCad libraries and the 14 MB of STEP models are in
-`scratch/tanmatsu/sources/keebdeck_keyboard_hw/`; re-fetch with
+`../hardware-doc-archive/scratch/tanmatsu/sources/keebdeck_keyboard_hw/`; re-fetch with
 [`tools/fetch_sources.sh`](tools/fetch_sources.sh).
 
 ### Checklist for building a board around a spare keypad
diff --git a/devices/nicolai-electronics/tanmatsu/pricing-and-dimensions.md b/devices/nicolai-electronics/tanmatsu/pricing-and-dimensions.md
index a97f62f..013e375 100644
--- a/devices/nicolai-electronics/tanmatsu/pricing-and-dimensions.md
+++ b/devices/nicolai-electronics/tanmatsu/pricing-and-dimensions.md
@@ -91,7 +91,7 @@ Computed with [`tools/step_bbox.py`](tools/step_bbox.py), which reads `CARTESIAN
 Reproduce:
 
 ```bash
-python3 tools/step_bbox.py scratch/tanmatsu/sources/tanmatsu-mechanical/tanmatsu.step
+python3 tools/step_bbox.py ../hardware-doc-archive/scratch/tanmatsu/sources/tanmatsu-mechanical/tanmatsu.step
 ```
 
 ### What the measurements show
diff --git a/devices/nicolai-electronics/tanmatsu/tools/fetch_sources.sh b/devices/nicolai-electronics/tanmatsu/tools/fetch_sources.sh
index 207c4d4..513bc94 100755
--- a/devices/nicolai-electronics/tanmatsu/tools/fetch_sources.sh
+++ b/devices/nicolai-electronics/tanmatsu/tools/fetch_sources.sh
@@ -75,4 +75,4 @@ cd ..
 echo
 echo "Done. Sources in: $WORK"
 echo "Archive them outside the repo so a /tmp or worktree clean cannot destroy them:"
-echo "  cp -a \"$WORK\" ../repo-archive/scratch/tanmatsu/sources"
+echo "  cp -a \"$WORK\" ../hardware-doc-archive/scratch/tanmatsu/sources"
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/README.md b/devices/seeed-studio/xiao-esp32s3-sense/README.md
index b654bbb..87890e6 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/README.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/README.md
@@ -188,7 +188,7 @@ artifacts/
 └── wiki-snapshot/   230 markdown files — the complete official wiki source
 ```
 
-Large binaries and media were moved to `archive/` and replaced with `*.ARCHIVED.md` placeholders carrying hashes and multiple recovery URLs. Exact-duplicate files were replaced with `*.DUPLICATE.md` pointers. Nothing was discarded.
+Large binaries and media were moved to `../hardware-doc-archive/` and replaced with `*.ARCHIVED.md` placeholders carrying hashes and multiple recovery URLs. Exact-duplicate files were replaced with `*.DUPLICATE.md` pointers. Nothing was discarded.
 
 ## Provenance note
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/acquisition/README.md b/devices/seeed-studio/xiao-esp32s3-sense/acquisition/README.md
index 0f2ce95..df30f50 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/acquisition/README.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/acquisition/README.md
@@ -64,10 +64,10 @@ Findings, not legal advice. Full per-artifact detail in [`manifest.json`](manife
 |---|---:|---|
 | **`allowed`** | 14 | All schematics and KiCad libraries — **CC BY-SA 4.0**, stated on every schematic sheet |
 | **`conditional`** | 1 | Espressif ESP32-S3 datasheet (attribution) |
-| **`restricted`** | 4 | **OV3660 / OV5640 datasheets and module specs** — explicitly state *"Individuals and/or organizations are not allowed to re-distribute said information."* |
+| **`prohibited`** | 4 | **OV3660 / OV5640 datasheets and module specs** — explicitly state *"Individuals and/or organizations are not allowed to re-distribute said information."* |
 | **`unknown`** | 23 | Firmware bundles, CAD/3D assets, pinout spreadsheets, the reference-design catalogue — Seeed publishes these as support downloads with no stated terms |
 
-**13 artifacts over 1 MB are flagged in `manifest.json` under `review_required`** because they combine size with `restricted` or `unknown` terms. They are currently **staged** in the repository at the user's explicit instruction to keep all documents in place for now. The notable ones:
+**13 artifacts over 1 MB are flagged in `manifest.json` under `review_required`** because they combine size with `prohibited` or `unknown` terms. They are currently **staged** in the repository at the user's explicit instruction to keep all documents in place for now. The notable ones:
 
 - `ov3660-datasheet.pdf` (1.9 MB) and `ov5640-datasheet.pdf` (1.7 MB) — **explicit no-redistribution clause**
 - `xiao-reference-design.pdf` (49.9 MB) — largest single artifact; no stated terms; contains third-party project descriptions
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/acquisition/manifest.json b/devices/seeed-studio/xiao-esp32s3-sense/acquisition/manifest.json
index 9b006e9..8a7d395 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/acquisition/manifest.json
+++ b/devices/seeed-studio/xiao-esp32s3-sense/acquisition/manifest.json
@@ -51,7 +51,7 @@
       "redistribution_status": "allowed",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip",
       "placeholder": "artifacts/schematics/ARCHIVED-SCHEMATIC-ZIPS.md",
       "archived_date": "2026-08-30",
       "note": "ZIP wrapper archived; the full extraction remains in the repository at artifacts/extracted/."
@@ -125,7 +125,7 @@
       "redistribution_status": "allowed",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.1-sch-pcb.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.1-sch-pcb.zip",
       "placeholder": "artifacts/schematics/ARCHIVED-SCHEMATIC-ZIPS.md",
       "archived_date": "2026-08-30",
       "note": "ZIP wrapper archived; the full extraction remains in the repository at artifacts/extracted/."
@@ -161,7 +161,7 @@
       "redistribution_status": "allowed",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-expansion-board-v1.0-sch-pcb.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-expansion-board-v1.0-sch-pcb.zip",
       "placeholder": "artifacts/schematics/ARCHIVED-SCHEMATIC-ZIPS.md",
       "archived_date": "2026-08-30",
       "note": "ZIP wrapper archived; the full extraction remains in the repository at artifacts/extracted/."
@@ -197,7 +197,7 @@
       "redistribution_status": "allowed",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/xiao-esp32s3-plus-v1.1-kicad.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/xiao-esp32s3-plus-v1.1-kicad.zip",
       "placeholder": "artifacts/kicad/ARCHIVED-PLUS-KICAD-ZIP.md",
       "archived_date": "2026-08-30",
       "note": "ZIP wrapper archived; the full extraction remains in the repository at artifacts/extracted/."
@@ -230,7 +230,7 @@
       "license": "OmniVision proprietary",
       "license_evidence": "Datasheet states: \"Individuals and/or organizations are not allowed to re-distribute said information.\"",
       "license_scope": "file",
-      "redistribution_status": "restricted",
+      "redistribution_status": "prohibited",
       "disposition": "repository",
       "repository_state": "staged"
     },
@@ -246,7 +246,7 @@
       "license": "OmniVision proprietary",
       "license_evidence": "Datasheet states: \"Individuals and/or organizations are not allowed to re-distribute said information.\"",
       "license_scope": "file",
-      "redistribution_status": "restricted",
+      "redistribution_status": "prohibited",
       "disposition": "repository",
       "repository_state": "staged"
     },
@@ -262,7 +262,7 @@
       "license": "OmniVision proprietary",
       "license_evidence": "Datasheet states: \"Individuals and/or organizations are not allowed to re-distribute said information.\"",
       "license_scope": "file",
-      "redistribution_status": "restricted",
+      "redistribution_status": "prohibited",
       "disposition": "repository",
       "repository_state": "staged"
     },
@@ -278,7 +278,7 @@
       "license": "OmniVision proprietary",
       "license_evidence": "Datasheet states: \"Individuals and/or organizations are not allowed to re-distribute said information.\"",
       "license_scope": "file",
-      "redistribution_status": "restricted",
+      "redistribution_status": "prohibited",
       "disposition": "repository",
       "repository_state": "staged"
     },
@@ -441,7 +441,7 @@
       "redistribution_status": "unknown",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-3d-model.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-3d-model.zip",
       "placeholder": "artifacts/cad/ARCHIVED-3D-MODELS.md",
       "archived_date": "2026-08-28"
     },
@@ -460,7 +460,7 @@
       "redistribution_status": "unknown",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-sense-3d-model.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-sense-3d-model.zip",
       "placeholder": "artifacts/cad/ARCHIVED-3D-MODELS.md",
       "archived_date": "2026-08-28"
     },
@@ -511,7 +511,7 @@
       "redistribution_status": "unknown",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-20240814.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-20240814.zip",
       "placeholder": "artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md",
       "archived_date": "2026-08-28"
     },
@@ -530,7 +530,7 @@
       "redistribution_status": "unknown",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-20240814.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-20240814.zip",
       "placeholder": "artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md",
       "archived_date": "2026-08-28"
     },
@@ -549,7 +549,7 @@
       "redistribution_status": "unknown",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-legacy.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-legacy.zip",
       "placeholder": "artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md",
       "archived_date": "2026-08-28"
     },
@@ -568,7 +568,7 @@
       "redistribution_status": "unknown",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-legacy.zip",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-legacy.zip",
       "placeholder": "artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md",
       "archived_date": "2026-08-28"
     },
@@ -683,7 +683,7 @@
       "redistribution_status": "unknown",
       "disposition": "archived",
       "repository_state": "not-present",
-      "archive_path": "../repo-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf",
+      "archive_path": "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf",
       "placeholder": "artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.md",
       "archived_date": "2026-08-28"
     },
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/ARCHIVED-3D-MODELS.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/ARCHIVED-3D-MODELS.md
index 84391d1..c2732b7 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/ARCHIVED-3D-MODELS.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/ARCHIVED-3D-MODELS.md
@@ -15,7 +15,7 @@
 > An earlier revision of this record listed the *uncompressed* totals under a plain "Bytes"
 > heading, which would have failed a `sha256sum`/size check on a re-fetched ZIP.
 
-Archive path: `archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/`
+Archive path: `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/`
 
 ## Reacquisition
 
@@ -27,27 +27,6 @@ curl -fsSL "$B/seeed-studio-xiao-esp32s3-3d_model.zip"       -o xiao-esp32s3-3d-
 
 Retrieved 2026-08-24, from the wiki's *Resources → Mechanical Design* section.
 
-## Independent sources
-
-`files.seeedstudio.com` is a single point of failure: every `curl` above resolves to that one
-host, so the commands are one hostname's lifetime from useless. Two independent ways to
-rediscover the links:
-
-- **Seeed wiki page** (separate host, human-readable *Resources* section):  
-  <https://wiki.seeedstudio.com/xiao_esp32s3_getting_started/>
-- **Wiki source on GitHub** — different infrastructure entirely, and the markdown carries the
-  download URLs verbatim, so the links survive even if the rendered wiki changes:  
-  <https://raw.githubusercontent.com/Seeed-Studio/wiki-documents/docusaurus-version/sites/en/docs/Sensor/SeeedStudio_XIAO/SeeedStudio_XIAO_ESP32S3/XIAO_ESP32S3_Getting_Started.md>  
-  (branch `docusaurus-version`; `main` 404s and `master` is a near-empty tree)
-
-> **Filenames carry a date suffix that changes.** This record cites
-> `..._SCH%26PCB_260226.zip`, while the wiki snapshot in
-> [`../wiki-snapshot/`](../wiki-snapshot/) references `..._SCH&PCB_230327.zip` and
-> `XIAO_ESP32S3_ExpBoard_v1.0_SCH&PCB_230324.zip` for the same designs. If a URL 404s, list the
-> *Resources* section rather than assuming the artifact is gone — the suffix has most likely
-> moved on. Match by SHA-256, not by filename.
-
-
 ## What was extracted before archiving
 
 These ZIPs were **initially archived unmined** — checking them first turned up a genuinely
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-3d-model.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-3d-model.zip
deleted file mode 120000
index bd1e7d7..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-3d-model.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-3d-model.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-sense-3d-model.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-sense-3d-model.zip
deleted file mode 120000
index 72a1abb..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-sense-3d-model.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/cad/xiao-esp32s3-sense-3d-model.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/CAMERA-DATASHEETS-MOVED.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/CAMERA-DATASHEETS-MOVED.md
index 4c131fe..604d145 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/CAMERA-DATASHEETS-MOVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/CAMERA-DATASHEETS-MOVED.md
@@ -49,5 +49,5 @@ All hashes re-verified unchanged after the move; all validate as `application/pd
 > ⚠ **The OV3660 datasheet is scarce — do not archive it out of the repository.** It is a
 > **v1.3, May 2011 PRELIMINARY** document that OmniVision does not publish; it reached us through a
 > Seeed mirror that no longer serves it, and **all five independent re-fetch URLs returned 404 on
-> 2026-08-30**. Its redistribution status is `restricted`, which is also why it was **moved rather
+> 2026-08-30**. Its redistribution status is `prohibited`, which is also why it was **moved rather
 > than copied** — a second copy would be the wrong direction on both counts.
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/RELOCATED-ov3660.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/RELOCATED-ov3660.md
index 76e02b6..9ce2053 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/RELOCATED-ov3660.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/RELOCATED-ov3660.md
@@ -6,5 +6,5 @@ module specs).
 
 Short version: both OV3660 PDFs now live under
 [`components/omnivision/ov3660/artifacts/`](../../../../../components/omnivision/ov3660/artifacts/).
-They were **moved, not copied, and not archived** — the document limits redistribution, and the datasheet
+They were **moved, not copied, and not archived** — redistribution is `prohibited`, and the datasheet
 is scarce (all five re-fetch URLs 404 as of 2026-08-30), so it stays in the repository.
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf
deleted file mode 120000
index 16d3635..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.link
deleted file mode 120000
index 8089dfc..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-xiao-reference-design.pdf
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.md
index 26a5f1b..b859517 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf.ARCHIVED.md
@@ -13,18 +13,6 @@
 | Licence | Unstated — Seeed marketing catalogue |
 | Reason archived | Largest file in the repo; **its content is fully extracted into committed Markdown and JSON** |
 
-## Source repository
-
-The Seeed wiki is generated from a public repository, which is a genuinely separate custodian
-from `files.seeedstudio.com` and carries the vendor download URLs verbatim in Markdown:
-
-- Repository: <https://github.com/Seeed-Studio/wiki-documents> (branch `docusaurus-version` —
-  `main` 404s and `master` is a near-empty tree)
-- This device's page in that repo: <https://raw.githubusercontent.com/Seeed-Studio/wiki-documents/docusaurus-version/sites/en/docs/Sensor/SeeedStudio_XIAO/SeeedStudio_XIAO_ESP32S3/XIAO_ESP32S3_Getting_Started.md>
-
-If a `files.seeedstudio.com` link 404s, read the *Resources* section there rather than assuming
-the artifact is gone: the filenames carry date suffixes that drift. **Match by SHA-256.**
-
 ## Reacquisition
 
 ```bash
@@ -34,7 +22,7 @@ curl -fsSL "https://files.seeedstudio.com/wiki/XIAO/XIAO-Reference-Design.pdf" \
 
 Fallbacks, in order: the [XIAO wiki resources section](https://wiki.seeedstudio.com/SeeedStudio_XIAO_Series_Introduction/) · `https://web.archive.org/web/2/https://files.seeedstudio.com/wiki/XIAO/XIAO-Reference-Design.pdf`
 
-Archive copy (if you hold it): `archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf`
+Archive copy (if you hold it): `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/datasheets/xiao-reference-design.pdf`
 
 ## What was extracted before archiving
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md
index eacc179..53f1880 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/ARCHIVED-FIRMWARE-ZIPS.md
@@ -13,7 +13,7 @@
 | `xiao-esp32s3-firmware-20240814.zip` | 8 219 852 | `7e4cc51fca6e5b16393e3bc6ed9d929b8c7e36c8a3107b4750d7991312f3fd68` |
 | `xiao-esp32s3-firmware-legacy.zip` | 8 217 189 | `0383237f78e873dc7d7cd5d5ea559805ea3269b82ec2d62c9874526cf555ceda` |
 
-Archive path: `archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/`
+Archive path: `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/`
 
 > **The four ZIPs are four distinct files.** Note this does *not* contradict the finding below
 > that the 20240814 and legacy *binaries* are identical: the ZIP wrappers differ in the flasher
@@ -33,23 +33,6 @@ curl -fsSL "$B/XIAO-ESP32S3-firmware.zip"                -o xiao-esp32s3-firmwar
 
 Retrieved 2026-08-24. Linked from the wiki's *Resources → Factory Firmware* section.
 
-## Independent sources
-
-Every `curl` above resolves to `files.seeedstudio.com`, so the commands are one hostname's
-lifetime from useless. Two independent ways to rediscover the links:
-
-- **Seeed wiki page** (separate host, *Resources → Factory Firmware*):  
-  <https://wiki.seeedstudio.com/xiao_esp32s3_getting_started/>
-- **Wiki source on GitHub** — different infrastructure, and the markdown carries the download
-  URLs verbatim, so they survive changes to the rendered wiki:  
-  <https://raw.githubusercontent.com/Seeed-Studio/wiki-documents/docusaurus-version/sites/en/docs/Sensor/SeeedStudio_XIAO/SeeedStudio_XIAO_ESP32S3/XIAO_ESP32S3_Getting_Started.md>  
-  (branch `docusaurus-version`; `main` 404s and `master` is a near-empty tree)
-
-> **Filenames carry date suffixes that drift.** The sibling schematic and 3D-model records cite
-> `..._260226.zip` where the wiki snapshot references `..._230327.zip` for the same designs. If a
-> firmware URL 404s, list the *Resources* section rather than assuming the artifact is gone, and
-> **match by SHA-256, not by filename** — the four hashes above are the identity, the names are not.
-
 ## What was extracted before archiving
 
 Everything of value is already in committed Markdown — see [`factory-firmware.md`](../../factory-firmware.md):
@@ -69,7 +52,7 @@ Both extractions contained a **7 671 328-byte Windows `esptool.exe`** (SHA-256 `
 byte-identical to each other — 14.6 MiB for one redundant binary.
 
 > ⚠ **This size and hash are no longer verifiable.** The binary was deleted rather than archived,
-> and no copy survives in `../repo-archive`. The figures above are as recorded at the time
+> and no copy survives in `../hardware-doc-archive`. The figures above are as recorded at the time
 > of deletion and could not be re-checked during the 2026-08-30 audit. The hash is also truncated,
 > and cannot now be completed. To verify, re-fetch a firmware ZIP (above) and re-extract.
 >
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-20240814.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-20240814.zip
deleted file mode 120000
index 4ece72e..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-20240814.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-20240814.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-legacy.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-legacy.zip
deleted file mode 120000
index bc3ac58..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-legacy.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-firmware-legacy.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-20240814.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-20240814.zip
deleted file mode 120000
index 4590373..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-20240814.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-20240814.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-legacy.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-legacy.zip
deleted file mode 120000
index 0e9e80a..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-legacy.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/firmware/xiao-esp32s3-sense-firmware-legacy.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/ARCHIVED-PLUS-KICAD-ZIP.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/ARCHIVED-PLUS-KICAD-ZIP.md
index e76556e..0c4e6a3 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/ARCHIVED-PLUS-KICAD-ZIP.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/ARCHIVED-PLUS-KICAD-ZIP.md
@@ -12,7 +12,7 @@
 | **Size** | 678 481 bytes |
 | Root directory inside the ZIP | `202004052_XIAO ESP32S3 Plus_v1.1_KiCad` (vendor part number `202004052`) |
 | Retrieved | 2026-08-24 |
-| Archive path | `archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/` |
+| Archive path | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/` |
 
 Full details, alongside the three schematic ZIPs archived at the same time, are in
 [`../schematics/ARCHIVED-SCHEMATIC-ZIPS.md`](../schematics/ARCHIVED-SCHEMATIC-ZIPS.md).
@@ -26,18 +26,6 @@ in [`comparisons-and-recommendations.md`](../../comparisons-and-recommendations.
   connector part** — `LBF11-G30P-BOR` rather than the Hirose `DF40C-30DP`.
 - The Plus adds **`ADC_BAT` on GPIO10**, a battery-sense divider the Sense does not have.
 
-## Source repository
-
-The Seeed wiki is generated from a public repository, which is a genuinely separate custodian
-from `files.seeedstudio.com` and carries the vendor download URLs verbatim in Markdown:
-
-- Repository: <https://github.com/Seeed-Studio/wiki-documents> (branch `docusaurus-version` —
-  `main` 404s and `master` is a near-empty tree)
-- This device's page in that repo: <https://raw.githubusercontent.com/Seeed-Studio/wiki-documents/docusaurus-version/sites/en/docs/Sensor/SeeedStudio_XIAO/SeeedStudio_XIAO_ESP32S3/XIAO_ESP32S3_Getting_Started.md>
-
-If a `files.seeedstudio.com` link 404s, read the *Resources* section there rather than assuming
-the artifact is gone: the filenames carry date suffixes that drift. **Match by SHA-256.**
-
 ## Reacquisition
 
 Despite being a KiCad library rather than a schematic, this file is served from the **same wiki
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/xiao-esp32s3-plus-v1.1-kicad.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/xiao-esp32s3-plus-v1.1-kicad.zip
deleted file mode 120000
index 61c95a9..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/xiao-esp32s3-plus-v1.1-kicad.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/kicad/xiao-esp32s3-plus-v1.1-kicad.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/ARCHIVED-SCHEMATIC-ZIPS.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/ARCHIVED-SCHEMATIC-ZIPS.md
index 7338c15..f57e4ac 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/ARCHIVED-SCHEMATIC-ZIPS.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/ARCHIVED-SCHEMATIC-ZIPS.md
@@ -21,7 +21,7 @@ recorded separately in
 [`xiao-esp32s3-v1.4-sch-pcb.zip.DUPLICATE.md`](xiao-esp32s3-v1.4-sch-pcb.zip.DUPLICATE.md).
 Its identical extraction was removed at the same time.
 
-Archive path: `archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/{schematics,kicad}/`
+Archive path: `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/{schematics,kicad}/`
 
 ## Reacquisition
 
@@ -34,27 +34,6 @@ curl -fsSL "$B/XIAO_ESP32S3_ExpBoard_v1.0_SCH%26PCB.zip"                   -o xi
 
 Retrieved **2026-08-24** from the wiki's *Resources → Schematic / PCB* section.
 
-## Independent sources
-
-`files.seeedstudio.com` is a single point of failure: every `curl` above resolves to that one
-host, so the commands are one hostname's lifetime from useless. Two independent ways to
-rediscover the links:
-
-- **Seeed wiki page** (separate host, human-readable *Resources* section):  
-  <https://wiki.seeedstudio.com/xiao_esp32s3_getting_started/>
-- **Wiki source on GitHub** — different infrastructure entirely, and the markdown carries the
-  download URLs verbatim, so the links survive even if the rendered wiki changes:  
-  <https://raw.githubusercontent.com/Seeed-Studio/wiki-documents/docusaurus-version/sites/en/docs/Sensor/SeeedStudio_XIAO/SeeedStudio_XIAO_ESP32S3/XIAO_ESP32S3_Getting_Started.md>  
-  (branch `docusaurus-version`; `main` 404s and `master` is a near-empty tree)
-
-> **Filenames carry a date suffix that changes.** This record cites
-> `..._SCH%26PCB_260226.zip`, while the wiki snapshot in
-> [`../wiki-snapshot/`](../wiki-snapshot/) references `..._SCH&PCB_230327.zip` and
-> `XIAO_ESP32S3_ExpBoard_v1.0_SCH&PCB_230324.zip` for the same designs. If a URL 404s, list the
-> *Resources* section rather than assuming the artifact is gone — the suffix has most likely
-> moved on. Match by SHA-256, not by filename.
-
-
 > ⚠ The expansion-board ZIP is the **Sense daughterboard** design, published under the
 > misleading name `XIAO_ESP32S3_ExpBoard_v1.0_SCH&PCB`. It is not an "expansion board" in the
 > shield sense — see [`sense-daughterboard.md`](../../sense-daughterboard.md). This naming is
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-expansion-board-v1.0-sch-pcb.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-expansion-board-v1.0-sch-pcb.zip
deleted file mode 120000
index 280e546..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-expansion-board-v1.0-sch-pcb.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-expansion-board-v1.0-sch-pcb.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip
deleted file mode 120000
index 0686475..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.1-sch-pcb.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.1-sch-pcb.zip
deleted file mode 120000
index 0219cd9..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.1-sch-pcb.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.1-sch-pcb.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip
deleted file mode 120000
index e6d8566..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip.DUPLICATE.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip.DUPLICATE.md
index 7b201c7..b898886 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip.DUPLICATE.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-v1.4-sch-pcb.zip.DUPLICATE.md
@@ -37,7 +37,7 @@ describing the Sense v1.5 board. See
 ## Restore, if you need the file at this exact path
 
 ```bash
-cp "$HOME/repo-archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip" \
+cp "$HOME/hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/schematics/xiao-esp32s3-sense-v1.5-sch-pcb.zip" \
    xiao-esp32s3-v1.4-sch-pcb.zip
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/TRANSLATIONS.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/TRANSLATIONS.ARCHIVED.md
index b79bbb4..425c9d1 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/TRANSLATIONS.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/TRANSLATIONS.ARCHIVED.md
@@ -20,7 +20,7 @@ find <lang> -type f -exec sha256sum {} \; | sort -k2 | sha256sum
 **Archive path** (repo-relative, so it maps 1:1):
 
 ```
-archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/<lang>/
+../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/<lang>/
 ```
 
 ## Why only English was kept — the translations add nothing
@@ -43,18 +43,6 @@ product**, and no evidence of a non-English-first documentation track. Had a tra
 carried material the English lacked, that would have been a finding and it would have
 stayed in the repository.
 
-## Sources beyond GitHub
-
-Everything above resolves to GitHub. That is a single custodian and a single company's
-availability decision, so these are recorded as Seeed wiki paths that do not depend on it
-(all verified reachable 2026-08-30):
-
-- Rendered wiki: <https://wiki.seeedstudio.com/xiao_esp32s3_getting_started/>
-- Product page: <https://www.seeedstudio.com/XIAO-ESP32S3-Sense-p-5639.html>
-
-> Vendor pages are **not** equivalent to the pinned commit above: they track the current
-> release, so use them to rediscover the project, then verify against the hashes here.
-
 ## Reacquisition
 
 All five languages come from the same source as the English corpus — the wiki is an
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/es b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/es
deleted file mode 120000
index 9cb55a7..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/es
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/es
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/ja b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/ja
deleted file mode 120000
index 9834417..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/ja
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/ja
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/pt-BR b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/pt-BR
deleted file mode 120000
index d2cec9b..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/pt-BR
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/pt-BR
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/zh-CN b/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/zh-CN
deleted file mode 120000
index 842cd4f..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/zh-CN
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/artifacts/wiki-snapshot/sites/zh-CN
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/commands.md b/devices/seeed-studio/xiao-esp32s3-sense/commands.md
index 9e1531b..2f0cc21 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/commands.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/commands.md
@@ -32,7 +32,7 @@ Environment for all executed commands: Linux, bash, Python 3.14, `uvx` for ad-ho
 | 14 | `uvx --from pypdf python tools/extract_showcase.py xiao-reference-design.pdf out.json` | Extract 117 projects + `/Annots` hyperlinks | `executed-success` — 116/117 with URLs |
 | 15 | `python3 tools/diff_vendored_lib.py --vendored <zip> --upstream-repo <o/r> --out <patch>` | Detect patched vs stale vendored libraries | `executed-success` — 1 identical, 2 stale-but-unmodified; found an **expired root CA** |
 | 16 | `python3 tools/dedupe_pointer.py <keep> <dup> "<why>"` | Replace exact-duplicate files with pointer notes | `executed-success` — 4 duplicates, 3.07 MB reclaimed |
-| 17 | `python3 tools/archive_artifact.py --repo-root . --manifest tools/archive-manifest.json` | Move bulky artifacts to `../repo-archive` with recovery placeholders | `executed-success` — 108.86 MB relocated, nothing deleted |
+| 17 | `python3 tools/archive_artifact.py --repo-root . --manifest tools/archive-manifest.json` | Move bulky artifacts to `../hardware-doc-archive` with recovery placeholders | `executed-success` — 108.86 MB relocated, nothing deleted |
 
 Notable failure worth preserving: **`pdftotext` is not installed** in this environment, and there is no system wordlist at `/usr/share/dict/words`. PDF work therefore uses `uvx --from pypdf python`, and the de-kerning vocabulary is built from the PDF's own clean pages rather than a dictionary.
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/ARCHIVED-PAYLOADS.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/ARCHIVED-PAYLOADS.md
index 4a034c8..f8fd9e2 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/ARCHIVED-PAYLOADS.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/ARCHIVED-PAYLOADS.md
@@ -2,14 +2,12 @@
 
 Three large non-source files were moved out of the repository on **2026-08-30**. Not deleted.
 
-> **A symlink now stands in for each file at its original path**, pointing through this repo's
-> `archive/` link. With the archive present the paths resolve and the tree behaves as though
-> nothing moved; without it they dangle, and this record is what remains.
+> **These files are absent from the repository.** They are not symlinks and not placeholders-in-place —
+> the paths simply do not exist here any more. This record is the only thing standing in for them,
+> which is why it carries a SHA-256, a byte count and a pinned reacquisition URL for every file.
 >
-> That is why this record still carries a SHA-256, a byte count and a pinned reacquisition URL
-> for every file: **the archive copy is a convenience for whoever holds it, not part of the
-> contract.** It lives outside the repository at a machine-local path, so nothing here may
-> depend on it, and the symlinks are a local nicety rather than a substitute for these hashes.
+> The archive copy is a **convenience for whoever holds it, not part of the contract**: it lives
+> outside the repository at a machine-local path, so nothing here may depend on it.
 
 ## What was archived
 
@@ -22,7 +20,7 @@ Three large non-source files were moved out of the repository on **2026-08-30**.
 `example_0.gif` and `example_1.gif` were archived earlier, on 2026-08-28.
 
 Archive root:
-`archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/`
+`../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/`
 
 ## What these actually are, and why the split falls where it does
 
@@ -57,40 +55,6 @@ files are the device-relevant part, but they are only ~1 % of the tree, and they
 real code.** The `.cpp` files beside them matter just as much. What made this library big was one
 generated firmware blob and four documentation GIFs — not library code, and not examples.
 
-## Sources beyond GitHub
-
-Everything above resolves to GitHub. That is a single custodian and a single company's
-availability decision, so these are recorded as Seeed paths that do not depend on it
-(all verified reachable 2026-08-30):
-
-- Vendor wiki: <https://wiki.seeedstudio.com/xiao_esp32s3_getting_started/>
-- Product page: <https://www.seeedstudio.com/XIAO-ESP32S3-Sense-p-5639.html>
-- **PlatformIO registry** — independent custodian redistributing this library:
-  <https://registry.platformio.org/libraries/seeed-studio/Seeed_Arduino_SSCMA>
-
-> Vendor pages are **not** equivalent to the pinned commit above: they track the current
-> release, so use them to rediscover the project, then verify against the hashes here.
-
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`Seeed-Studio/Seeed_Arduino_SSCMA`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`Seeed-Studio/Seeed_Arduino_SSCMA`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA) |
-| Base commit | [`65a1b2061e80f1bd3814f688451a66646782fe1f`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA/tree/65a1b2061e80f1bd3814f688451a66646782fe1f) |
-| Tree at that commit | <https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA/tree/65a1b2061e80f1bd3814f688451a66646782fe1f> |
-
-```bash
-git clone https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA
-git -C Seeed_Arduino_SSCMA checkout 65a1b2061e80f1bd3814f688451a66646782fe1f
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.md`](examples/camera_web_server/img/example_0.gif.ARCHIVED.md)
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.md`](examples/camera_web_server/img/example_1.gif.ARCHIVED.md)
-
 ## Reacquisition
 
 | | |
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif
deleted file mode 120000
index 31ad1f9..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.link
deleted file mode 120000
index 8409ba7..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-example_0.gif
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.md
index 589d8a7..eba3736 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif` |
 | Type | file |
 | Size | 3,797,725 B (3.62 MiB) |
 | SHA-256 | `2a19f1b672b6ee57939e66c6d08b5cfc8fdbcb3d722b7906b6617b1a5ce612f2` |
@@ -22,26 +22,6 @@
 | License | MIT |
 | Path within upstream repo | `examples/camera_web_server/img/example_0.gif` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`Seeed-Studio/Seeed_Arduino_SSCMA`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`Seeed-Studio/Seeed_Arduino_SSCMA`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA) |
-| Base commit | [`65a1b2061e80f1bd3814f688451a66646782fe1f`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA/tree/65a1b2061e80f1bd3814f688451a66646782fe1f) |
-| Tree at that commit | <https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA/tree/65a1b2061e80f1bd3814f688451a66646782fe1f> |
-
-```bash
-git clone https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA
-git -C Seeed_Arduino_SSCMA checkout 65a1b2061e80f1bd3814f688451a66646782fe1f
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/ARCHIVED-PAYLOADS.md`](../../../ARCHIVED-PAYLOADS.md)
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.md`](example_1.gif.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -59,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif" \
    "examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif
deleted file mode 120000
index a3c82ad..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.link
deleted file mode 120000
index b6ff2e3..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-example_1.gif
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.md
index 8dec331..cbfd13a 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif` |
 | Type | file |
 | Size | 1,431,430 B (1.37 MiB) |
 | SHA-256 | `34959eb9f66d99745070f66f203578b19c7a08d962f0d1edb7b3429ee98efa92` |
@@ -22,26 +22,6 @@
 | License | MIT |
 | Path within upstream repo | `examples/camera_web_server/img/example_1.gif` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`Seeed-Studio/Seeed_Arduino_SSCMA`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`Seeed-Studio/Seeed_Arduino_SSCMA`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA) |
-| Base commit | [`65a1b2061e80f1bd3814f688451a66646782fe1f`](https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA/tree/65a1b2061e80f1bd3814f688451a66646782fe1f) |
-| Tree at that commit | <https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA/tree/65a1b2061e80f1bd3814f688451a66646782fe1f> |
-
-```bash
-git clone https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA
-git -C Seeed_Arduino_SSCMA checkout 65a1b2061e80f1bd3814f688451a66646782fe1f
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/ARCHIVED-PAYLOADS.md`](../../../ARCHIVED-PAYLOADS.md)
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_0.gif.ARCHIVED.md`](example_0.gif.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -59,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/Seeed-Studio/Seeed_Arduino_SSCMA>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif" \
    "examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_1.gif"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_2.gif b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_2.gif
deleted file mode 120000
index fb2119b..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_2.gif
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_2.gif
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_3.gif b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_3.gif
deleted file mode 120000
index 1b5aaf1..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_3.gif
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/camera_web_server/img/example_3.gif
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/we2_iic_bootloader_recover/firmware.h b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/we2_iic_bootloader_recover/firmware.h
deleted file mode 120000
index ba8a23e..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/we2_iic_bootloader_recover/firmware.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/Seeed_Arduino_SSCMA/examples/we2_iic_bootloader_recover/firmware.h
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models
deleted file mode 120000
index 60b63f1..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models.ARCHIVED.link
deleted file mode 120000
index d6d95cf..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-models
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models.ARCHIVED.md
index f5422cc..df50f9b 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models` |
 | Type | directory |
 | Size | 10,770,720 B (10.27 MiB) |
 | File count | 5 |
@@ -32,21 +32,6 @@
 | `xiao_case_left.stl` | 68,184 | `4c990ce3b2d82f900406553b6008159ccded45a25e38057b9159bca402c737c5` |
 | `xiao_case_right.stl` | 62,484 | `3f84c73f5a1f3b63c5429f52e1a1b028e009c5c5656c925708b9bd7cb12aefbe` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera`](https://github.com/barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera`](https://github.com/barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera) |
-| Base commit | [`442a6971622a406cc5cbd323276f74cfe4c5fe2a`](https://github.com/barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera/tree/442a6971622a406cc5cbd323276f74cfe4c5fe2a) |
-| Tree at that commit | <https://github.com/barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera/tree/442a6971622a406cc5cbd323276f74cfe4c5fe2a> |
-
-```bash
-git clone https://github.com/barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera
-git -C XIAO-ESP32S3-Sense_Retro_Camera checkout 442a6971622a406cc5cbd323276f74cfe4c5fe2a
-```
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -62,11 +47,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/barkinsarikartal/XIAO-ESP32S3-Sense_Retro_Camera>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models" \
    "examples/selected/XIAO-ESP32S3-Sense_Retro_Camera/models"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets
deleted file mode 120000
index 1f792df..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.link
deleted file mode 120000
index f40fe05..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-assets
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.md
index c4ca3db..e7f8566 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/esp32-birdnet-mic/assets` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets` |
 | Type | directory |
 | Size | 4,729,511 B (4.51 MiB) |
 | File count | 4 |
@@ -31,26 +31,6 @@
 | `connection.png` | 1,806,937 | `b86845950142e7e38781f580ca28ab594f91ad49d876ba857d6924c9a48328fc` |
 | `webui.png` | 293,447 | `2ba3381cf813ef30d09950c51081a9f32ad7c37be2a11a68d6a47c61b3e9ca54` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`Sukecz/esp32-birdnet-mic`](https://github.com/Sukecz/esp32-birdnet-mic) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`Sukecz/esp32-birdnet-mic`](https://github.com/Sukecz/esp32-birdnet-mic) |
-| Base commit | [`8552b12aa44487c1cb935467a93ac35ecdc681d6`](https://github.com/Sukecz/esp32-birdnet-mic/tree/8552b12aa44487c1cb935467a93ac35ecdc681d6) |
-| Tree at that commit | <https://github.com/Sukecz/esp32-birdnet-mic/tree/8552b12aa44487c1cb935467a93ac35ecdc681d6> |
-
-```bash
-git clone https://github.com/Sukecz/esp32-birdnet-mic
-git -C esp32-birdnet-mic checkout 8552b12aa44487c1cb935467a93ac35ecdc681d6
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.md`](manual-ota-firmware.ARCHIVED.md)
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.md`](web-flasher.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -66,11 +46,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/Sukecz/esp32-birdnet-mic>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets" \
    "examples/selected/esp32-birdnet-mic/assets"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware
deleted file mode 120000
index f1f3bfa..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.link
deleted file mode 120000
index 34b612e..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-manual-ota-firmware
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.md
index cc9d8de..eb2ffea 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/esp32-birdnet-mic/manual-ota-firmware` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware` |
 | Type | directory |
 | Size | 6,346,672 B (6.05 MiB) |
 | File count | 6 |
@@ -33,26 +33,6 @@
 | `firmware-app-s3.bin` | 1,163,808 | `cd9071f689524d29118f437336a82b496ccec6f1ad0b1c3befc78cada169fcc3` |
 | `firmware-app.bin` | 1,289,024 | `6e300493bcd2c61aa8039650b551a77dce3e8b2029323735e60a8a8933b17732` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`Sukecz/esp32-birdnet-mic`](https://github.com/Sukecz/esp32-birdnet-mic) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`Sukecz/esp32-birdnet-mic`](https://github.com/Sukecz/esp32-birdnet-mic) |
-| Base commit | [`8552b12aa44487c1cb935467a93ac35ecdc681d6`](https://github.com/Sukecz/esp32-birdnet-mic/tree/8552b12aa44487c1cb935467a93ac35ecdc681d6) |
-| Tree at that commit | <https://github.com/Sukecz/esp32-birdnet-mic/tree/8552b12aa44487c1cb935467a93ac35ecdc681d6> |
-
-```bash
-git clone https://github.com/Sukecz/esp32-birdnet-mic
-git -C esp32-birdnet-mic checkout 8552b12aa44487c1cb935467a93ac35ecdc681d6
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.md`](assets.ARCHIVED.md)
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.md`](web-flasher.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -70,11 +50,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/Sukecz/esp32-birdnet-mic/releases>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware" \
    "examples/selected/esp32-birdnet-mic/manual-ota-firmware"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher
deleted file mode 120000
index a870b46..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.link
deleted file mode 120000
index 4a50ba2..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-web-flasher
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.md
index 38efea1..74a73ef 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/esp32-birdnet-mic/web-flasher` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher` |
 | Type | directory |
 | Size | 71,702,460 B (68.38 MiB) |
 | File count | 86 |
@@ -113,26 +113,6 @@
 | `assets/bird.png` | 107,183 | `ef1149ef6472f0ac45e8795a49a34dd965afdc0dce227bc5388d060787b0065c` |
 | `assets/favicon-96x96.png` | 16,335 | `cd53013cb1e5945e4bc3dfce3367de4d87513f3cf7b3cffb71728097f9d772d4` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`Sukecz/esp32-birdnet-mic`](https://github.com/Sukecz/esp32-birdnet-mic) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`Sukecz/esp32-birdnet-mic`](https://github.com/Sukecz/esp32-birdnet-mic) |
-| Base commit | [`8552b12aa44487c1cb935467a93ac35ecdc681d6`](https://github.com/Sukecz/esp32-birdnet-mic/tree/8552b12aa44487c1cb935467a93ac35ecdc681d6) |
-| Tree at that commit | <https://github.com/Sukecz/esp32-birdnet-mic/tree/8552b12aa44487c1cb935467a93ac35ecdc681d6> |
-
-```bash
-git clone https://github.com/Sukecz/esp32-birdnet-mic
-git -C esp32-birdnet-mic checkout 8552b12aa44487c1cb935467a93ac35ecdc681d6
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/assets.ARCHIVED.md`](assets.ARCHIVED.md)
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/manual-ota-firmware.ARCHIVED.md`](manual-ota-firmware.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -150,11 +130,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/Sukecz/esp32-birdnet-mic/releases>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/esp32-birdnet-mic/web-flasher" \
    "examples/selected/esp32-birdnet-mic/web-flasher"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex
deleted file mode 120000
index 73b8b16..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.link
deleted file mode 120000
index c3d5692..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-latex
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.md
index 94ef3ce..f5e65a9 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/on-device-vision-ai/latex` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex` |
 | Type | directory |
 | Size | 7,553,457 B (7.20 MiB) |
 | File count | 7 |
@@ -34,25 +34,6 @@
 | `power-graph.jpg` | 257,729 | `e0f90153ae3c48089fd246e19d52cf7590dae8bafc8f172eccbd98290beb0f1b` |
 | `xiaoml-kit.jpg` | 2,261,602 | `176bf88ceb6e2526b5feda6cadb2369b8bf2266958eecb4493fe30b252b828ac` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`webmcu-ai/on-device-vision-ai`](https://github.com/webmcu-ai/on-device-vision-ai) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`webmcu-ai/on-device-vision-ai`](https://github.com/webmcu-ai/on-device-vision-ai) |
-| Base commit | [`8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e`](https://github.com/webmcu-ai/on-device-vision-ai/tree/8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e) |
-| Tree at that commit | <https://github.com/webmcu-ai/on-device-vision-ai/tree/8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e> |
-
-```bash
-git clone https://github.com/webmcu-ai/on-device-vision-ai
-git -C on-device-vision-ai checkout 8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e
-```
-
-**2 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.md`](main.pdf.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -68,11 +49,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/webmcu-ai/on-device-vision-ai>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex" \
    "examples/selected/on-device-vision-ai/latex"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf
deleted file mode 120000
index 1ce0afc..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.link b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.link
deleted file mode 120000
index 9bce7b7..0000000
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-main.pdf
\ No newline at end of file
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.md b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.md
index 1f2c5a7..65e0583 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `examples/selected/on-device-vision-ai/main.pdf` |
-| Archived to | `archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf` |
 | Type | file |
 | Size | 7,819,852 B (7.46 MiB) |
 | SHA-256 | `e15655073c260720189721035723ae4aef98b6b45a4f1c13f7bc120715a70d7c` |
@@ -22,25 +22,6 @@
 | License | MIT |
 | Path within upstream repo | `main.pdf` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`webmcu-ai/on-device-vision-ai`](https://github.com/webmcu-ai/on-device-vision-ai) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`webmcu-ai/on-device-vision-ai`](https://github.com/webmcu-ai/on-device-vision-ai) |
-| Base commit | [`8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e`](https://github.com/webmcu-ai/on-device-vision-ai/tree/8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e) |
-| Tree at that commit | <https://github.com/webmcu-ai/on-device-vision-ai/tree/8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e> |
-
-```bash
-git clone https://github.com/webmcu-ai/on-device-vision-ai
-git -C on-device-vision-ai checkout 8a8d92ef1157f3c4c6fb260c5b4ef0ac478e715e
-```
-
-**2 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/latex.ARCHIVED.md`](latex.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -58,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/webmcu-ai/on-device-vision-ai>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf" \
+mv "../hardware-doc-archive/doc/hardware/devices/seeed-studio/xiao-esp32s3-sense/examples/selected/on-device-vision-ai/main.pdf" \
    "examples/selected/on-device-vision-ai/main.pdf"
 ```
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/features/camera.md b/devices/seeed-studio/xiao-esp32s3-sense/features/camera.md
index 3904722..ed30689 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/features/camera.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/features/camera.md
@@ -65,7 +65,7 @@ The `esp32-camera` driver probes over SCCB and loads the right register set auto
 
   The AF routine is **not in the sensor's ROM** — a firmware blob must be uploaded to the OV5640's embedded microcontroller over SCCB at every power-up, which is what this library does.
 
-> **Licensing note.** The OV3660 and OV5640 datasheets carry an explicit restriction: *"Individuals and/or organizations are not allowed to re-distribute said information."* They are retained in this tree for research use, but their redistribution status is **`restricted`/`unknown`** and they are flagged for review in [`acquisition/manifest.json`](../acquisition/manifest.json). The specification tables above are factual data extracted from them, not a reproduction of the documents.
+> **Licensing note.** The OV3660 and OV5640 datasheets carry an explicit restriction: *"Individuals and/or organizations are not allowed to re-distribute said information."* They are retained in this tree for research use, but their redistribution status is **`prohibited`/`unknown`** and they are flagged for review in [`acquisition/manifest.json`](../acquisition/manifest.json). The specification tables above are factual data extracted from them, not a reproduction of the documents.
 
 ## 2. Pin wiring
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/sources.md b/devices/seeed-studio/xiao-esp32s3-sense/sources.md
index 2d3a237..fb8a5bd 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/sources.md
+++ b/devices/seeed-studio/xiao-esp32s3-sense/sources.md
@@ -23,8 +23,8 @@ All retrieved **2026-08-24**. `Class`: `primary` · `authorized mirror` · `cred
 | ID | Title | Publisher | Class | Medium | Version | Establishes | Limitations | Local path |
 |---|---|---|---|---|---|---|---|---|
 | C1 | OV2640 datasheet | OmniVision | primary | datasheet | **v1.6, 2006-02-28** | 1600×1200, 2.2 µm, 40 dB S/N, 600 µA standby | "Advanced Information / Preliminary". Redistribution `unknown` | [pdf](../../../components/omnivision/ov2640/artifacts/ov2640-datasheet-v2.2.pdf) |
-| C2 | OV3660 datasheet | OmniVision | primary | datasheet | **v1.3, 2011-05** | 2048×1536, 1/5", 98 mA, 70 dB DR | **PRELIMINARY**, some values TBD. **Redistribution restricted** | [pdf](../../../components/omnivision/ov3660/artifacts/ov3660-datasheet.pdf) — relocated 2026-08-30 to the [component record](../../../components/omnivision/ov3660/README.md) |
-| C3 | OV5640 datasheet | OmniVision | primary | datasheet | **v2.03, 2011-05** | 2592×1944, autofocus, 140 mA | **Redistribution restricted** | [pdf](../../../components/omnivision/ov5640/artifacts/ov5640-datasheet-v2.03.pdf) |
+| C2 | OV3660 datasheet | OmniVision | primary | datasheet | **v1.3, 2011-05** | 2048×1536, 1/5", 98 mA, 70 dB DR | **PRELIMINARY**, some values TBD. **Redistribution prohibited** | [pdf](../../../components/omnivision/ov3660/artifacts/ov3660-datasheet.pdf) — relocated 2026-08-30 to the [component record](../../../components/omnivision/ov3660/README.md) |
+| C3 | OV5640 datasheet | OmniVision | primary | datasheet | **v2.03, 2011-05** | 2592×1944, autofocus, 140 mA | **Redistribution prohibited** | [pdf](../../../components/omnivision/ov5640/artifacts/ov5640-datasheet-v2.03.pdf) |
 | C4 | ESP32-S3 datasheet (Seeed-hosted copy) | Espressif via Seeed | authorized mirror | datasheet | unknown | Strapping pins, ADC units, GPIO limits | **Vendor mirror.** Byte-differs from Espressif's original *and* from Waveshare's mirror — three portals, three revisions. Prefer the [Espressif copy in the component record](../../../components/espressif/esp32-s3r8/README.md) | [pdf](artifacts/datasheets/esp32-s3-datasheet-seeed-copy.pdf) |
 | C5 | ESP-IDF / ESP-IoT-Solution programming guides | Espressif | primary | framework docs | v5.1.4, v5.2.5 | API reference behind the camera, I²S and LEDC guidance used throughout | **Archived, not in the repo** — held under the [ESP32-S3R8 component](../../../components/espressif/esp32-s3r8/README.md), ~77 MiB. Hashes, sizes and download URLs: [`ARCHIVED-FRAMEWORK-GUIDES.md`](../../../components/espressif/esp32-s3r8/artifacts/ARCHIVED-FRAMEWORK-GUIDES.md) | archive |
 
diff --git a/devices/seeed-studio/xiao-esp32s3-sense/tools/archive_artifact.py b/devices/seeed-studio/xiao-esp32s3-sense/tools/archive_artifact.py
index b166024..cc72e1c 100644
--- a/devices/seeed-studio/xiao-esp32s3-sense/tools/archive_artifact.py
+++ b/devices/seeed-studio/xiao-esp32s3-sense/tools/archive_artifact.py
@@ -2,7 +2,7 @@
 """Relocate bulky/duplicate artifacts out of the repository without losing them.
 
 Policy (per user instruction, 2026-08-24): never delete a downloaded artifact.
-Move it to ../repo-archive/ preserving its relative path, and leave a
+Move it to ../hardware-doc-archive/ preserving its relative path, and leave a
 Markdown placeholder in its place carrying everything needed to get the exact
 bytes back: size, SHA-256, mtime, upstream repo + commit + author, and several
 independent recovery URLs.
@@ -20,7 +20,7 @@
 
 import argparse, hashlib, json, os, re, shutil, subprocess, datetime, sys
 
-ARCHIVE = os.path.expanduser("../repo-archive")
+ARCHIVE = os.path.expanduser("../hardware-doc-archive")
 
 
 def sha256(p):
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL
deleted file mode 120000
index aed7a30..0000000
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.link b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.link
deleted file mode 120000
index 8504cd3..0000000
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-PANEL
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.md b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.md
index ed24fc2..ff078a8 100644
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL` |
 | Type | directory |
 | Size | 8,448,768 B (8.06 MiB) |
 | File count | 2 |
@@ -29,26 +29,6 @@
 | `Soldered Inkplate 5 Gen2_panel.kicad_pcb` | 8,443,598 | `051ae713fae953542616dd1f8d8c2ba5ea119f5be02b4096c83ebc6834e98a4c` |
 | `Soldered Inkplate 5 Gen2_panel.kicad_pro` | 5,170 | `423250ecb49901e8a2cbd700b5b560c2c636d02b7a7aed02bf911209bee9bf77` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design) |
-| Base commit | [`7450a321c3beac884dd3053d08eb61ed80828e30`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design/tree/7450a321c3beac884dd3053d08eb61ed80828e30) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design/tree/7450a321c3beac884dd3053d08eb61ed80828e30> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design
-git -C Soldered-Inkplate-5-Gen2-hardware-design checkout 7450a321c3beac884dd3053d08eb61ed80828e30
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.md`](Source 3D files.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -64,11 +44,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL" \
    "devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files
deleted file mode 120000
index 6d10365..0000000
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.link b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.link
deleted file mode 120000
index f76fcb6..0000000
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Source 3D files
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.md b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.md
index f76e9f7..2a94b30 100644
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.md	
+++ b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files` |
 | Type | directory |
 | Size | 2,684,318 B (2.56 MiB) |
 | File count | 2 |
@@ -29,26 +29,6 @@
 | `Soldered Inkplate 5 Gen2 Bottom.step` | 2,602,572 | `20e3be9fb12051ff7bb420b3201ff3bbc77a260655cca4debdce1abfc87bba1d` |
 | `Soldered Inkplate 5 Gen2 Top.step` | 81,746 | `670b189d2ef82108c29b4bd45115ab8fdc4dbb27edaa267d6c9b0172c391d2ae` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design) |
-| Base commit | [`7450a321c3beac884dd3053d08eb61ed80828e30`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design/tree/7450a321c3beac884dd3053d08eb61ed80828e30) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design/tree/7450a321c3beac884dd3053d08eb61ed80828e30> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design
-git -C Soldered-Inkplate-5-Gen2-hardware-design checkout 7450a321c3beac884dd3053d08eb61ed80828e30
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.md`](PANEL.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -64,11 +44,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files" \
    "devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step
deleted file mode 120000
index 435b05c..0000000
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.link b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.link
deleted file mode 120000
index eef3b4b..0000000
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Soldered Inkplate 5 Gen2 3D.step
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md
index 0feb7fc..6520af2 100644
--- a/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md	
+++ b/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step` |
 | Type | file |
 | Size | 30,413,013 B (29.00 MiB) |
 | SHA-256 | `3d403ca00dec23a30a4cc5b5a1490d73c32eb7e0b969732dbe6153fab4d059ed` |
@@ -22,26 +22,6 @@
 | License | NOASSERTION |
 | Path within upstream repo | `OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design) |
-| Base commit | [`7450a321c3beac884dd3053d08eb61ed80828e30`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design/tree/7450a321c3beac884dd3053d08eb61ed80828e30) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design/tree/7450a321c3beac884dd3053d08eb61ed80828e30> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design
-git -C Soldered-Inkplate-5-Gen2-hardware-design checkout 7450a321c3beac884dd3053d08eb61ed80828e30
-```
-
-**3 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/PANEL.ARCHIVED.md`](../../CAD/V1.1.0/PANEL.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/CAD/V1.1.0/Source 3D files.ARCHIVED.md`](../../CAD/V1.1.0/Source 3D files.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -59,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Soldered-Inkplate-5-Gen2-hardware-design>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step" \
    "devices/soldered-electronics/inkplate-5-gen2/artifacts/hardware/soldered-inkplate-5-gen2-hardware-design/OUTPUTS/V1.1.0/Soldered Inkplate 5 Gen2 3D.step"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build
deleted file mode 120000
index d253af6..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.link
deleted file mode 120000
index c795b05..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-build
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.md
index 89e4f3c..b5c342f 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build` |
 | Type | directory |
 | Size | 559,621,577 B (533.70 MiB) |
 | File count | 489 |
@@ -516,25 +516,6 @@
 | `html_old/_static/images/inkplate6plus_back.jpg` | 3,685,029 | `ad199995fac8cfadd6cc7ab6f1d289227c8eb9e516ead0806b48c204902911e0` |
 | `html_old/_static/images/inkplate6plus_front.jpg` | 2,117,906 | `b1ce0df5c4817b87fdbc8d4e7d62399d9d22c445b00eb25125b1117075913da8` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-documentation`](https://github.com/SolderedElectronics/Inkplate-documentation) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-documentation`](https://github.com/SolderedElectronics/Inkplate-documentation) |
-| Base commit | [`1b3d3329915dbddf8f923ce61945d0842cad6c63`](https://github.com/SolderedElectronics/Inkplate-documentation/tree/1b3d3329915dbddf8f923ce61945d0842cad6c63) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-documentation/tree/1b3d3329915dbddf8f923ce61945d0842cad6c63> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-documentation
-git -C Inkplate-documentation checkout 1b3d3329915dbddf8f923ce61945d0842cad6c63
-```
-
-**2 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.md`](source/images.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -552,11 +533,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://inkplate.readthedocs.io>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build" \
    "devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images
deleted file mode 120000
index b857685..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.link
deleted file mode 120000
index 5e798fa..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-images
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.md
index 4494275..6b1789f 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images` |
 | Type | directory |
 | Size | 141,217,541 B (134.68 MiB) |
 | File count | 92 |
@@ -119,25 +119,6 @@
 | `tempera_rear.jpg` | 335,953 | `40d08cdb29af75eb839c53a5e92c39a017c1d6ba6adfade585ae78aee8ebfd01` |
 | `tempera_side.jpg` | 65,605 | `1567358fc116a35a94fe5b38d6c59fb9be291895fb01ce8bcec3fe24b9360b4b` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-documentation`](https://github.com/SolderedElectronics/Inkplate-documentation) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-documentation`](https://github.com/SolderedElectronics/Inkplate-documentation) |
-| Base commit | [`1b3d3329915dbddf8f923ce61945d0842cad6c63`](https://github.com/SolderedElectronics/Inkplate-documentation/tree/1b3d3329915dbddf8f923ce61945d0842cad6c63) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-documentation/tree/1b3d3329915dbddf8f923ce61945d0842cad6c63> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-documentation
-git -C Inkplate-documentation checkout 1b3d3329915dbddf8f923ce61945d0842cad6c63
-```
-
-**2 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/build.ARCHIVED.md`](../build.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -155,11 +136,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://inkplate.readthedocs.io>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images" \
    "devices/soldered-electronics/inkplate-5/artifacts/docs/Inkplate-documentation/source/images"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL
deleted file mode 120000
index 7d5ed61..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.link
deleted file mode 120000
index 8504cd3..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-PANEL
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.md
index 1ffc188..3c7bd9d 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL` |
 | Type | directory |
 | Size | 17,225,271 B (16.43 MiB) |
 | File count | 2 |
@@ -29,27 +29,6 @@
 | `Soldered Inkplate 5_panel.kicad_pcb` | 17,215,006 | `29c7767ff29a09a3d7ff811536882d39d912bb7b72d25171fcf6a32173ff4479` |
 | `Soldered Inkplate 5_panel.kicad_pro` | 10,265 | `b46ab360d3baf338a64e07aadf42822353bf7939e63c9768503800ecfda4f4a7` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) |
-| Base commit | [`80c0d0fe0f14ae7d1e342221ae08a43a4c976611`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design
-git -C Soldered-Inkplate-5-hardware-design checkout 80c0d0fe0f14ae7d1e342221ae08a43a4c976611
-```
-
-**4 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.md`](Source 3D files.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md`](../../OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md`](../../OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -65,11 +44,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL" \
    "devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files
deleted file mode 120000
index 4b16cc6..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.link
deleted file mode 120000
index f76fcb6..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Source 3D files
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.md
index 4efa26b..9dc7e96 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.md	
+++ b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files` |
 | Type | directory |
 | Size | 15,621,056 B (14.90 MiB) |
 | File count | 2 |
@@ -29,27 +29,6 @@
 | `Soldered Inkplate 5 v1.2.0. Case.f3z` | 4,973,763 | `ee59f86de930d1ffd95690a3eaf3953a7845c7aeb795a0e21c7f9c28c904cc64` |
 | `Soldered Inkplate 5 v1.2.0. Case.step` | 10,647,293 | `8fccc458d9cb7386a825a0d6a3bf16affc8aaf0e620ef09961d6d65c85f82b3c` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) |
-| Base commit | [`80c0d0fe0f14ae7d1e342221ae08a43a4c976611`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design
-git -C Soldered-Inkplate-5-hardware-design checkout 80c0d0fe0f14ae7d1e342221ae08a43a4c976611
-```
-
-**4 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.md`](PANEL.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md`](../../OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md`](../../OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -65,11 +44,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files" \
    "devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files
deleted file mode 120000
index 06b6213..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.link
deleted file mode 120000
index c940226..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-3d printable files
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md
index e64c416..8c54cc1 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md	
+++ b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files` |
 | Type | directory |
 | Size | 15,748,484 B (15.02 MiB) |
 | File count | 1 |
@@ -28,27 +28,6 @@
 |---|---:|---|
 | `Soldered Inkplate 5 v1.2.0. Case.stl` | 15,748,484 | `358bf2737cdf0566974a7e6fa7f329343fae0624da545b568f2cdfc46e579514` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) |
-| Base commit | [`80c0d0fe0f14ae7d1e342221ae08a43a4c976611`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design
-git -C Soldered-Inkplate-5-hardware-design checkout 80c0d0fe0f14ae7d1e342221ae08a43a4c976611
-```
-
-**4 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.md`](../../CAD/V1.2.0/PANEL.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.md`](../../CAD/V1.2.0/Source 3D files.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md`](Soldered Inkplate 5 3D.step.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -64,11 +43,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files" \
    "devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step
deleted file mode 120000
index f643231..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.link
deleted file mode 120000
index 2df223c..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Soldered Inkplate 5 3D.step
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md
index 0b34ec8..ef07f3b 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md	
+++ b/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step` |
 | Type | file |
 | Size | 27,802,592 B (26.51 MiB) |
 | SHA-256 | `7ea0a3d53948e734777815e19258492a93cac346c5cf51e3488ec4adc085a124` |
@@ -22,27 +22,6 @@
 | License | NOASSERTION |
 | Path within upstream repo | `OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Soldered-Inkplate-5-hardware-design`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design) |
-| Base commit | [`80c0d0fe0f14ae7d1e342221ae08a43a4c976611`](https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design/tree/80c0d0fe0f14ae7d1e342221ae08a43a4c976611> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design
-git -C Soldered-Inkplate-5-hardware-design checkout 80c0d0fe0f14ae7d1e342221ae08a43a4c976611
-```
-
-**4 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/PANEL.ARCHIVED.md`](../../CAD/V1.2.0/PANEL.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/CAD/V1.2.0/Source 3D files.ARCHIVED.md`](../../CAD/V1.2.0/Source 3D files.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/3d printable files.ARCHIVED.md`](3d printable files.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -60,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Soldered-Inkplate-5-hardware-design>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step" \
    "devices/soldered-electronics/inkplate-5/artifacts/hardware/soldered-inkplate-5-hardware-design/OUTPUTS/V1.2.0/Soldered Inkplate 5 3D.step"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md
index 8c919bf..11ff474 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md
@@ -4,14 +4,12 @@
 deleted. 
 This took the vendored library from **28 MiB to 8.3 MiB while removing no code at all.**
 
-> **A symlink now stands in for each file at its original path**, pointing through this repo's
-> `archive/` link. With the archive present the paths resolve and the tree behaves as though
-> nothing moved; without it they dangle, and this record is what remains.
+> **These files are absent from the repository.** They are not symlinks and not placeholders-in-place —
+> the paths simply do not exist here any more. This record is the only thing standing in for them,
+> which is why it carries a SHA-256, a byte count and a pinned reacquisition URL for every file.
 >
-> That is why this record still carries a SHA-256, a byte count and a pinned reacquisition URL
-> for every file: **the archive copy is a convenience for whoever holds it, not part of the
-> contract.** It lives outside the repository at a machine-local path, so nothing here may
-> depend on it, and the symlinks are a local nicety rather than a substitute for these hashes.
+> The archive copy is a **convenience for whoever holds it, not part of the contract**: it lives
+> outside the repository at a machine-local path, so nothing here may depend on it.
 
 ## What was archived, and what deliberately was not
 
@@ -39,48 +37,6 @@ fixed string, against all authored Markdown outside this tree. **Zero were cited
 > `.` in `image.h` was being read as a regex wildcard. Verified again with fixed-string matching on
 > the full relative path.
 
-## Sources beyond GitHub
-
-Everything above resolves to GitHub. That is a single custodian and a single company's
-availability decision, so these are recorded as Soldered / Inkplate paths that do not depend on it
-(all verified reachable 2026-08-30):
-
-- Vendor documentation: <https://docs.soldered.com/inkplate/>
-- Product category, if the docs path moves: <https://soldered.com/categories/inkplate/>
-- **PlatformIO registry** — a genuinely independent custodian redistributing this library, so
-  it survives both GitHub and the vendor:
-  <https://registry.platformio.org/libraries/e-radionicacom/InkplateLibrary>
-
-> Vendor pages are **not** equivalent to the pinned commit above: they track the current
-> release, so use them to rediscover the project, then verify against the hashes here.
-
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](examples/Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](examples/Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](examples/Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](examples/Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](examples/Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](examples/Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](examples/Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](examples/Inkplate6PLUS.ARCHIVED.md)
-
 ## Reacquisition
 
 | | |
@@ -108,7 +64,7 @@ Library Manager** — among the lowest reacquisition risks in this repository, w
 archiving safe here.
 
 Archive root:
-`archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/`
+`../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/`
 
 ## Restoring a file
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10 b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10
deleted file mode 120000
index 1e32fe9..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.link
deleted file mode 120000
index 65d3a21..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate10
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md
index 2836362..1135011 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10` |
 | Type | directory |
 | Size | 29,644,462 B (28.27 MiB) |
 | File count | 295 |
@@ -322,33 +322,6 @@
 | `Basic/Inkplate10_Image_Converter/Inkplate10_Image_Converter.ino` | 3,759 | `a42fc5ec9b0da263095d4b2ffb1aed9cb26ec3b645c1ee31fb7f4d9df6767ae6` |
 | `Basic/Inkplate10_Image_Converter/image.h` | 758,169 | `d4e322ea7f04a3e998ddad5d8c0923d387fd3770642f149d225c52bd76f51070` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -364,11 +337,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA
deleted file mode 120000
index e764d34..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.link
deleted file mode 120000
index 32fdb08..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate13SPECTRA
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md
index 81c1bad..2bcb585 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA` |
 | Type | directory |
 | Size | 18,984,896 B (18.11 MiB) |
 | File count | 258 |
@@ -285,33 +285,6 @@
 | `Basic/Inkplate13SPECTRA_Partial_Update/Inkplate13SPECTRA_Partial_Update.ino` | 3,991 | `40cea0b5a02c249617cfbcf1e2e3515faa812dd305406d89eb5702aa5894fefb` |
 | `Basic/Inkplate13SPECTRA_Drawing_Graphics/Inkplate13SPECTRA_Drawing_Graphics.ino` | 2,840 | `fa8528cfb0b45580b1a532235c8e72a1804e0b2cb5f70b2ea86c399bd297c493` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -327,11 +300,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2 b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2
deleted file mode 120000
index c0ffa5f..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.link
deleted file mode 120000
index 0b2e8eb..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate2
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md
index 60e42ad..c15591f 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2` |
 | Type | directory |
 | Size | 4,601,464 B (4.39 MiB) |
 | File count | 222 |
@@ -249,33 +249,6 @@
 | `Basic/Inkplate2_Image_Converter/image.h` | 33,954 | `8a0cff1d4d003970ca659e29be348aa030cbe541694aca2e96c48cb2b9935cd4` |
 | `Basic/Inkplate2_TextBox/Inkplate2_TextBox.ino` | 3,252 | `fb2ad198fd0622220178d831fdcbcafe012e1b234c181909db8489a1272c74d3` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -291,11 +264,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA
deleted file mode 120000
index 4718cd2..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.link
deleted file mode 120000
index fffff9c..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate4TEMPERA
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md
index 57063e2..3b12d30 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA` |
 | Type | directory |
 | Size | 11,887,627 B (11.34 MiB) |
 | File count | 236 |
@@ -263,33 +263,6 @@
 | `Basic/Inkplate4TEMPERA_Image_Converter/Inkplate4TEMPERA_Image_Converter.ino` | 3,761 | `a540f6c32dd9f2b17f85aeb57c0e2d28cb6a56d8942ffcb682b0014915355f79` |
 | `Basic/Inkplate4TEMPERA_Image_Converter/image.h` | 275,820 | `f006af7dc5d84189fa1b79b878e44b2ad0de65c16afc9b13a08b3553543cee80` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -305,11 +278,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture1.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture1.h
deleted file mode 120000
index bc4e385..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture1.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture1.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture2.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture2.h
deleted file mode 120000
index 4e35e2d..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture2.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture2.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture3.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture3.h
deleted file mode 120000
index fb19be2..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture3.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/DeepSleep/Inkplate5_Simple_Deep_Sleep/picture3.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/destination.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/destination.jpg
deleted file mode 120000
index 4471d17..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/destination.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/destination.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise.bmp b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise.bmp
deleted file mode 120000
index 977a9bb..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise.bmp
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise.bmp
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise_Mono.bmp b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise_Mono.bmp
deleted file mode 120000
index 44b3dec..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise_Mono.bmp
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/WEB_WiFi/Inkplate5_Show_Pictures_From_Web/neowise_Mono.bmp
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_GIF_From_SD/cat_gif.gif b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_GIF_From_SD/cat_gif.gif
deleted file mode 120000
index d9a5dd5..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_GIF_From_SD/cat_gif.gif
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_GIF_From_SD/cat_gif.gif
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image1.bmp b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image1.bmp
deleted file mode 120000
index 9c86a2a..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image1.bmp
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image1.bmp
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image2.bmp b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image2.bmp
deleted file mode 120000
index ffc6c06..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image2.bmp
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/image2.bmp
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/pyramid.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/pyramid.jpg
deleted file mode 120000
index 834e609..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/pyramid.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Advanced/microSD/Inkplate5_microSD_Pictures/pyramid.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Basic/Inkplate5_Grayscale/image.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Basic/Inkplate5_Grayscale/image.h
deleted file mode 120000
index 2729eb4..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Basic/Inkplate5_Grayscale/image.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Basic/Inkplate5_Grayscale/image.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/demo_image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/demo_image.jpg
deleted file mode 120000
index 8689426..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/demo_image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/demo_image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/image.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/image.h
deleted file mode 120000
index d6ac0f2..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/image.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Diagnostics/Inkplate5_Factory_Programming_VCOM/image.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_News/Fonts/SHARED-ASSETS.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_News/Fonts/SHARED-ASSETS.md
index 6db1be0..bb6ad6c 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_News/Fonts/SHARED-ASSETS.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_News/Fonts/SHARED-ASSETS.md
@@ -57,7 +57,7 @@ cp --remove-destination "$(readlink -f <file>)" <file>
 ```
 
 Or re-fetch from the pool's archive copy:
-`shared-assets/`
+`../hardware-doc-archive/doc/hardware/shared-assets/`
 
 The full set of sharing relationships, including every location that links to each
 entry, is in [`shared-assets/manifest.json`](../../../../../../../../../../../shared-assets/manifest.json).
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_32pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_32pt7b.h
deleted file mode 120000
index 87a9c77..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_32pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_32pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_40pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_40pt7b.h
deleted file mode 120000
index 8dddb41..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_40pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5/Projects/Inkplate5_Quotables/Fonts/exmouth_40pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture1.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture1.h
deleted file mode 120000
index 50a50d1..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture1.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture1.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture2.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture2.h
deleted file mode 120000
index da3e915..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture2.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture2.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture3.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture3.h
deleted file mode 120000
index b33b1f4..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture3.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/DeepSleep/Inkplate5V2_Simple_Deep_Sleep/picture3.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/destination.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/destination.jpg
deleted file mode 120000
index 7d5901e..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/destination.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/destination.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise.bmp b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise.bmp
deleted file mode 120000
index ad464a2..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise.bmp
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise.bmp
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise_Mono.bmp b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise_Mono.bmp
deleted file mode 120000
index 8582ee0..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise_Mono.bmp
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/WEB_WiFi/Inkplate5V2_Show_Pictures_From_Web/neowise_Mono.bmp
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_GIF_From_SD/cat_gif.gif b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_GIF_From_SD/cat_gif.gif
deleted file mode 120000
index abbcfb8..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_GIF_From_SD/cat_gif.gif
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_GIF_From_SD/cat_gif.gif
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures
deleted file mode 120000
index 8cb5b44..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.link
deleted file mode 120000
index 44dd231..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate5V2_microSD_Pictures
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md
index 3112026..06b63c4 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures` |
 | Type | directory |
 | Size | 5,640,314 B (5.38 MiB) |
 | File count | 4 |
@@ -31,33 +31,6 @@
 | `image2.bmp` | 2,764,854 | `4e432257b411e6995f375027e1ba94a99c432d942e8869bdffde1638efbdcfd5` |
 | `pyramid.jpg` | 105,552 | `7a457a1d54d7079ca29a575f099bc331941b391631e0cb70458d845dbd3db4c7` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../../../../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](../../../Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](../../../Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](../../../Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](../../../Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](../../../Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](../../../Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](../../../Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](../../../Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -73,11 +46,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Grayscale/image.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Grayscale/image.h
deleted file mode 120000
index 99c38ea..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Grayscale/image.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Grayscale/image.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Image_Converter/image.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Image_Converter/image.h
deleted file mode 120000
index 7295f6a..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Image_Converter/image.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Basic/Inkplate5V2_Image_Converter/image.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/demo_image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/demo_image.jpg
deleted file mode 120000
index a473b50..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/demo_image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/demo_image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/image.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/image.h
deleted file mode 120000
index b301cad..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/image.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Diagnostics/Inkplate5V2_Factory_Programming_VCOM/image.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSans48pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSans48pt7b.h
deleted file mode 120000
index a26a7f5..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSans48pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSans48pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSansBold48pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSansBold48pt7b.h
deleted file mode 120000
index d9d5cab..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSansBold48pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Google_Calendar/src/fonts/FreeSansBold48pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_News/Fonts/SHARED-ASSETS.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_News/Fonts/SHARED-ASSETS.md
index 6db1be0..bb6ad6c 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_News/Fonts/SHARED-ASSETS.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_News/Fonts/SHARED-ASSETS.md
@@ -57,7 +57,7 @@ cp --remove-destination "$(readlink -f <file>)" <file>
 ```
 
 Or re-fetch from the pool's archive copy:
-`shared-assets/`
+`../hardware-doc-archive/doc/hardware/shared-assets/`
 
 The full set of sharing relationships, including every location that links to each
 entry, is in [`shared-assets/manifest.json`](../../../../../../../../../../../shared-assets/manifest.json).
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSans48pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSans48pt7b.h
deleted file mode 120000
index 99386bc..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSans48pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSans48pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSansBold48pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSansBold48pt7b.h
deleted file mode 120000
index 036cb82..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSansBold48pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/fonts/FreeSansBold48pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/clear_sky.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/clear_sky.png
deleted file mode 120000
index fdbd3bf..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/clear_sky.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/clear_sky.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/fog.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/fog.png
deleted file mode 120000
index 7872804..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/fog.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/fog.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/full_battery.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/full_battery.png
deleted file mode 120000
index e196378..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/full_battery.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/full_battery.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/gray.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/gray.png
deleted file mode 120000
index 188779c..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/gray.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/gray.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/half_battery.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/half_battery.png
deleted file mode 120000
index 0fb6517..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/half_battery.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/half_battery.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/high_battery.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/high_battery.png
deleted file mode 120000
index f69e515..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/high_battery.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/high_battery.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/low_battery.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/low_battery.png
deleted file mode 120000
index 899fc3a..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/low_battery.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/low_battery.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/moon.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/moon.png
deleted file mode 120000
index 1c9cf2b..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/moon.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/moon.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/partly_cloudy.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/partly_cloudy.png
deleted file mode 120000
index f2b0270..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/partly_cloudy.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/partly_cloudy.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/rain.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/rain.png
deleted file mode 120000
index 1bd62e6..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/rain.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/rain.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/snow.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/snow.png
deleted file mode 120000
index 1c4d4c6..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/snow.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/snow.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/storm.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/storm.png
deleted file mode 120000
index 77643d0..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/storm.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/storm.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/thermometer.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/thermometer.png
deleted file mode 120000
index 34f01b3..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/thermometer.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_OpenMeteo_Weather_Station/src/icons/thermometer.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_32pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_32pt7b.h
deleted file mode 120000
index ef07469..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_32pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_32pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_40pt7b.h b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_40pt7b.h
deleted file mode 120000
index 3405b94..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_40pt7b.h
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Projects/Inkplate5V2_Quotables/Fonts/exmouth_40pt7b.h
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6 b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6
deleted file mode 120000
index 8b9ff7d..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.link
deleted file mode 120000
index bbf9e8d..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate6
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md
index 1949722..339973b 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6` |
 | Type | directory |
 | Size | 15,598,988 B (14.88 MiB) |
 | File count | 217 |
@@ -244,33 +244,6 @@
 | `Basic/Inkplate6_TextBox/Roboto_Light_36.h` | 41,632 | `e7dc9d111a4c4647f0f2be79cfd6a4711cd467ff50d3f823ed49b0d5a1a08575` |
 | `Basic/Inkplate6_Partial_Update/Inkplate6_Partial_Update.ino` | 4,768 | `e6d83c0b81eb79dcb79b9d1fc68d98aa3a05d66bd9ba3c8874805610581fd124` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -286,11 +259,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR
deleted file mode 120000
index 7a04c73..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.link
deleted file mode 120000
index 0b8fdad..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate6COLOR
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md
index cb6b59b..cf2d571 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR` |
 | Type | directory |
 | Size | 12,279,896 B (11.71 MiB) |
 | File count | 257 |
@@ -284,33 +284,6 @@
 | `Basic/Inkplate6COLOR_Simple/Inkplate6COLOR_Simple.ino` | 7,261 | `a367d1297dba6ada68459e6bd2e60d88898d6db51555ae5363506ce50de1b2b8` |
 | `Basic/Inkplate6COLOR_Simple/logoImg.h` | 4,230 | `4cf5bd3cf3db60a7ecb41718937d07b04046e04c6eaa89b14593f80e16d988b1` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](Inkplate6FLICK.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -326,11 +299,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK
deleted file mode 120000
index 28bea89..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.link
deleted file mode 120000
index d77eb26..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate6FLICK
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md
index 1758792..6d6d6c9 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK` |
 | Type | directory |
 | Size | 18,571,565 B (17.71 MiB) |
 | File count | 231 |
@@ -258,33 +258,6 @@
 | `Basic/Inkplate6FLICK_Image_Converter/image.h` | 594,469 | `09ea0674a2ae165310d91d91312f215492a0afa2688fec9cc4b156240fd8f4d4` |
 | `Basic/Inkplate6FLICK_Partial_Update/Inkplate6FLICK_Partial_Update.ino` | 4,888 | `677548d52e8dcbcb412ac49a0e0154a2640f713e00b3d6e8b874c679a8e4fa9e` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md`](Inkplate6PLUS.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -300,11 +273,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS
deleted file mode 120000
index efcf105..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.link b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.link
deleted file mode 120000
index d98feb9..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-Inkplate6PLUS
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md
index 0d6f6a8..3212fb5 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS.ARCHIVED.md
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS` |
-| Archived to | `archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS` |
 | Type | directory |
 | Size | 17,999,532 B (17.17 MiB) |
 | File count | 226 |
@@ -253,33 +253,6 @@
 | `Basic/Inkplate6PLUS_Touch_Registers/Inkplate6PLUS_Touch_Registers.ino` | 3,873 | `3c5932a9fb67e4c5f68008e1c10e1492a0f926536828cbaec8c34b26b02f015c` |
 | `Basic/Inkplate6PLUS_Touchscreen_Draw/Inkplate6PLUS_Touchscreen_Draw.ino` | 4,198 | `8f9027737ea8b33eaac3533534279dc6569df4f3148e64fd96f9cf696c8d9154` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-Arduino-library`](https://github.com/SolderedElectronics/Inkplate-Arduino-library) |
-| Base commit | [`1751cbe578522e5ea9ef713f32980186bde38077`](https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-Arduino-library/tree/1751cbe578522e5ea9ef713f32980186bde38077> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-Arduino-library
-git -C Inkplate-Arduino-library checkout 1751cbe578522e5ea9ef713f32980186bde38077
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/ARCHIVED-IMAGE-PAYLOADS.md`](../ARCHIVED-IMAGE-PAYLOADS.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate10.ARCHIVED.md`](Inkplate10.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate13SPECTRA.ARCHIVED.md`](Inkplate13SPECTRA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate2.ARCHIVED.md`](Inkplate2.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate4TEMPERA.ARCHIVED.md`](Inkplate4TEMPERA.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md`](Inkplate5V2/Advanced/microSD/Inkplate5V2_microSD_Pictures.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6.ARCHIVED.md`](Inkplate6.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6COLOR.ARCHIVED.md`](Inkplate6COLOR.ARCHIVED.md)
-- [`devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6FLICK.ARCHIVED.md`](Inkplate6FLICK.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -295,11 +268,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:
   <https://github.com/SolderedElectronics/Inkplate-Arduino-library>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS" \
+mv "../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS" \
    "devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/examples/Inkplate6PLUS"
 ```
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/extras/InkplateImage.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/extras/InkplateImage.jpg
deleted file mode 120000
index 7a12e48..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/extras/InkplateImage.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/extras/InkplateImage.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/BlueDotBME680.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/BlueDotBME680.jpg
deleted file mode 120000
index cb54e87..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/BlueDotBME680.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/BlueDotBME680.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Feather_SD_BME680.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Feather_SD_BME680.jpg
deleted file mode 120000
index a367a07..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Feather_SD_BME680.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Feather_SD_BME680.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_HW_SPI_BME280_bb.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_HW_SPI_BME280_bb.png
deleted file mode 120000
index 1b83be7..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_HW_SPI_BME280_bb.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_HW_SPI_BME280_bb.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_SW_SPI_BME280_bb.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_SW_SPI_BME280_bb.png
deleted file mode 120000
index 85c4721..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_SW_SPI_BME280_bb.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Mega_SW_SPI_BME280_bb.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Micro_BME280_bb.png b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Micro_BME280_bb.png
deleted file mode 120000
index 3917385..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Micro_BME280_bb.png
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/Micro_BME280_bb.png
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/SDLoggerSPIDemo.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/SDLoggerSPIDemo.jpg
deleted file mode 120000
index 45f6480..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/SDLoggerSPIDemo.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/SDLoggerSPIDemo.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/TwoBME680.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/TwoBME680.jpg
deleted file mode 120000
index de8006d..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/TwoBME680.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/TwoBME680.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/adafruit-bme680.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/adafruit-bme680.jpg
deleted file mode 120000
index 05b1a99..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/adafruit-bme680.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/adafruit-bme680.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/bosch-bme680.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/bosch-bme680.jpg
deleted file mode 120000
index 1ddfd58..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/bosch-bme680.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-Arduino-library/src/features/BME680/libs/BME680/Images/bosch-bme680.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/ARCHIVED-PAYLOADS.md b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/ARCHIVED-PAYLOADS.md
index 3bbdb31..5202ff8 100644
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/ARCHIVED-PAYLOADS.md
+++ b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/ARCHIVED-PAYLOADS.md
@@ -2,14 +2,12 @@
 
 **9 files, 7,115,995 bytes (6.79 MiB)** moved out of the repository on **2026-08-30**. Not deleted.
 
-> **A symlink now stands in for each file at its original path**, pointing through this repo's
-> `archive/` link. With the archive present the paths resolve and the tree behaves as though
-> nothing moved; without it they dangle, and this record is what remains.
+> **These files are absent from the repository.** They are not symlinks and not placeholders-in-place —
+> the paths simply do not exist here any more. This record is the only thing standing in for them,
+> which is why it carries a SHA-256, a byte count and a pinned reacquisition URL for every file.
 >
-> That is why this record still carries a SHA-256, a byte count and a pinned reacquisition URL
-> for every file: **the archive copy is a convenience for whoever holds it, not part of the
-> contract.** It lives outside the repository at a machine-local path, so nothing here may
-> depend on it, and the symlinks are a local nicety rather than a substitute for these hashes.
+> The archive copy is a **convenience for whoever holds it, not part of the contract**: it lives
+> outside the repository at a machine-local path, so nothing here may depend on it.
 
 This took the vendored library from **8.5 MiB to 4.2 MiB while removing no Python at all.**
 
@@ -35,33 +33,6 @@ around them.
 **Checked before archiving:** each file was tested by full relative path, as a fixed string,
 against all authored Markdown outside this tree. **Zero were cited.**
 
-## Sources beyond GitHub
-
-Everything above resolves to GitHub. That is a single custodian and a single company's
-availability decision, so these are recorded as Soldered / Inkplate paths that do not depend on it
-(all verified reachable 2026-08-30):
-
-- Vendor documentation: <https://docs.soldered.com/inkplate/>
-- Product category: <https://soldered.com/categories/inkplate/>
-
-> Vendor pages are **not** equivalent to the pinned commit above: they track the current
-> release, so use them to rediscover the project, then verify against the hashes here.
-
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`SolderedElectronics/Inkplate-micropython`](https://github.com/SolderedElectronics/Inkplate-micropython) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`SolderedElectronics/Inkplate-micropython`](https://github.com/SolderedElectronics/Inkplate-micropython) |
-| Base commit | [`4a2b2926`](https://github.com/SolderedElectronics/Inkplate-micropython/tree/4a2b2926) |
-| Tree at that commit | <https://github.com/SolderedElectronics/Inkplate-micropython/tree/4a2b2926> |
-
-```bash
-git clone https://github.com/SolderedElectronics/Inkplate-micropython
-git -C Inkplate-micropython checkout 4a2b2926
-```
-
 ## Reacquisition
 
 | | |
@@ -86,7 +57,7 @@ curl -fsSL "https://raw.githubusercontent.com/SolderedElectronics/Inkplate-micro
 A public MIT-licensed GitHub repository at a pinned commit — low reacquisition risk.
 
 Archive root:
-`archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/`
+`../hardware-doc-archive/doc/hardware/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/`
 
 ## Restoring a file
 
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/docs/inkplate_image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/docs/inkplate_image.jpg
deleted file mode 120000
index c8a5e4c..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/docs/inkplate_image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/docs/inkplate_image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate10/displayimagesd/image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate10/displayimagesd/image.jpg
deleted file mode 120000
index c204dba..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate10/displayimagesd/image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate10/displayimagesd/image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate13spectra/displayimagesd/image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate13spectra/displayimagesd/image.jpg
deleted file mode 120000
index 6143636..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate13spectra/displayimagesd/image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate13spectra/displayimagesd/image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6/displayimagesd/image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6/displayimagesd/image.jpg
deleted file mode 120000
index cee211d..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6/displayimagesd/image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6/displayimagesd/image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6color/displayimagesd/image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6color/displayimagesd/image.jpg
deleted file mode 120000
index 9bdb4df..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6color/displayimagesd/image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6color/displayimagesd/image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6flick/displayimagesd/image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6flick/displayimagesd/image.jpg
deleted file mode 120000
index d7344bd..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6flick/displayimagesd/image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate6flick/displayimagesd/image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate7spectra/displayimagesd/image.jpg b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate7spectra/displayimagesd/image.jpg
deleted file mode 120000
index 7dd706b..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate7spectra/displayimagesd/image.jpg
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/examples/inkplate7spectra/displayimagesd/image.jpg
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate-firmware.bin b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate-firmware.bin
deleted file mode 120000
index d9473da..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate-firmware.bin
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate-firmware.bin
\ No newline at end of file
diff --git a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate13spectra-firmware.bin b/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate13spectra-firmware.bin
deleted file mode 120000
index 6a3de01..0000000
--- a/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate13spectra-firmware.bin
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/soldered-electronics/inkplate-5/artifacts/source-snapshots/Inkplate-micropython/firmware/inkplate13spectra-firmware.bin
\ No newline at end of file
diff --git a/devices/waveshare/e-paper-esp32-driver-board/README.md b/devices/waveshare/e-paper-esp32-driver-board/README.md
deleted file mode 100644
index 785faf1..0000000
--- a/devices/waveshare/e-paper-esp32-driver-board/README.md
+++ /dev/null
@@ -1,127 +0,0 @@
-# Waveshare e-Paper ESP32 Driver Board — *stub*
-
-> **SKU 15823.** Research snapshot **2026-09-01**. **Stub record**: surveyed, not
-> researched in depth. Every claim is a vendor statement (`reported-working`) read
-> from the storefront and legacy wiki. No artifacts retrieved, no hardware in hand.
-
-Created during the [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) pass so
-that the Waveshare ESP32 e-paper population is known rather than re-derived. **It is
-here because it is genuinely relevant, not for completeness** — of Waveshare's seven
-ESP32 e-paper products, this is the one that best fits the phrase "a Waveshare ESP32
-e-paper *driver* board", and it is the oldest and most widely deployed of them.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Name | e-Paper ESP32 Driver Board |
-| SKU | **15823** |
-| Price | **USD 14.99** (observed 2026-09-01, waveshare.com, US region, single unit) |
-| Store | `https://www.waveshare.com/e-paper-esp32-driver-board.htm` |
-| Wiki | `https://www.waveshare.com/wiki/E-Paper_ESP32_Driver_Board` — **legacy wiki, HTTP 200** |
-| `docs.waveshare.com` | **404** — this product is not on the new platform |
-
-## What it is
-
-**Not a board with a screen on it.** It is a small ESP32 carrier with a 24-pin FPC
-connector, sold to drive Waveshare's **raw e-paper panels**, which you buy separately.
-Ships with the driver board, an adapter board and an FFC extension cable.
-
-| Specification | Value |
-|---|---|
-| SoC | **ESP32** (original — not S3, not C6) |
-| Flash | 4 MB |
-| SRAM / ROM | 520 KB / 448 KB |
-| Wi-Fi | 802.11 b/g/n |
-| Bluetooth | **4.2, BR/EDR *and* BLE** |
-| Panel interface | 3-wire or **4-wire SPI (default)** |
-| Operating voltage | 5 V; the 5 V pin accepts **3.6–5.5 V**, so a Li-ion cell works |
-| Operating current | 50–150 mA |
-| Dimensions | **29.46 × 48.25 mm** |
-
-### The panel pin map is fixed
-
-The wiki states plainly: *"the above is the board fixed connection, with no
-additional operation by the user."*
-
-| Panel pin | ESP32 GPIO |
-|---|---|
-| `DIN` (MOSI) | **P14** |
-| `SCLK` | **P13** |
-| `CS` | **P15** |
-| `DC` | **P27** |
-| `RST` | **P26** |
-| `BUSY` | **P25** |
-
-That fixed mapping is the board's whole proposition and also its limit: **the only
-expansion interface is the panel connector.** There is no general-purpose GPIO header
-documented — so, like its bigger sibling, it does not satisfy "e-paper development
-board *with expansion*" in the sense that phrase is normally meant. See
-[C-WS1](../esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards).
-
-## Panel compatibility — the actual reason to buy it
-
-The wiki publishes a demo-per-panel table covering **23 panel models**, which is by
-far the widest e-paper compatibility of anything in this survey:
-
-1.54" · 1.54" (B) · 2.13" · 2.13" (B) · 2.13" (D) · 2.66" · 2.66" (B) · 2.7" ·
-2.7" (B) · 2.9" · 2.9" (B) · 3.7" · 4.01" (F) · 4.2" · 4.2" (B) · 4.26" · 5.65" (F) ·
-5.83" · 5.83" (B) · 7.5" · 7.5" (B) · 13.3" (B) · 13.3" (K)
-
-Each maps to a named demo (`epd1in54_V2-demo`, `epd7in5_V2-demo`, …). The wiki warns
-that each demo targets the **latest** revision of its panel and that older panels need
-the version label on the back checked.
-
-**Note the 3.97-inch panel is absent from that list** — the panel used on the
-[ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) is not among the models this
-driver board documents support for.
-
-## Revision history
-
-The wiki records two hardware changes, which matter because they change the driver you
-need on the host PC:
-
-| Date | Change |
-|---|---|
-| **2024-12-30** | USB connector replaced with **Type-C**. "The hardware is basically compatible" |
-| **2022-07-28** | Serial chip changed **CP2102 → CH343**. *"Please pay attention to the driver selection"* |
-
-So a unit bought before July 2022 needs CP2102 drivers and a later one needs CH343.
-That is the single most likely cause of "the board does not appear as a serial port"
-on this product.
-
-## Software
-
-- Arduino-based; the wiki presents it as usable "just like any other Arduino board".
-- Ships an **Android app** that pushes images over **Bluetooth EDR** — which is why
-  the original ESP32 rather than an S3 is the right choice here: the S3 has no
-  Bluetooth Classic. (This knowledge base documents that constraint at length under
-  [ESP32-S3R8](../../../components/espressif/esp32-s3r8/README.md).)
-- Ships an **HTML host-side page** that pushes images over Wi-Fi.
-- Supports **Floyd–Steinberg dithering** and common image formats (BMP, JPEG, GIF, PNG).
-- Factory e-paper driver is described as open source.
-
-Stated applications: supermarket electronic price tags, electronic name cards, serial
-information display boards.
-
-## Why this is a stub and what would make it a record
-
-Not retrieved: schematic, demo archive, factory firmware, images, pricing history,
-community projects, or any component identification beyond the SoC. **No artifact was
-downloaded**, so there is nothing to hash.
-
-The highest-value next step would be the demo archive and the schematic, both of which
-the legacy wiki's Resources section links.
-
-## Sources
-
-| ID | Title | Class | URL | Retrieved | Version |
-|---|---|---|---|---|---|
-| `D01` | e-Paper ESP32 Driver Board — store listing | primary | `https://www.waveshare.com/e-paper-esp32-driver-board.htm` | 2026-09-01 | `unknown` |
-| `D02` | `E-Paper_ESP32_Driver_Board` wiki | primary | `https://www.waveshare.com/wiki/E-Paper_ESP32_Driver_Board` | 2026-09-01 | revisions dated 20220728, 20241230 |
-
-## See also
-
-- [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) — the integrated-panel board researched in depth
-- [The sibling survey](../esp32-s3-epaper-3.97/README.md#sibling-products)
-- [Waveshare documentation-sourcing guide](../../../vendors/waveshare/README.md)
diff --git a/devices/waveshare/esp32-c6-epaper-1.54/README.md b/devices/waveshare/esp32-c6-epaper-1.54/README.md
deleted file mode 100644
index cb93ff3..0000000
--- a/devices/waveshare/esp32-c6-epaper-1.54/README.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Waveshare ESP32-C6-ePaper-1.54 — *stub*
-
-> **SKUs 34393 / 34394.** Research snapshot **2026-09-01**. **Stub record**:
-> surveyed, not researched in depth. All claims are vendor statements
-> (`reported-working`) from the storefront and `docs.waveshare.com`. No artifacts
-> retrieved, no hardware in hand.
-
-Created during the [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) pass.
-Recorded because it is the **only** e-paper board in this survey that is neither
-Xtensa nor Wi-Fi-4-only, and because it carries a documented **I/O expander** — which
-bears directly on an unresolved question about the 3.97-inch board's schematic.
-
-## Identity
-
-| SKU | Product |
-|---|---|
-| **34393** | ESP32-C6-ePaper-1.54 |
-| **34394** | ESP32-C6-ePaper-1.54-EN |
-
-| Field | Value |
-|---|---|
-| Price | **USD 16.99 – 17.99** (observed 2026-09-01, waveshare.com, US region) |
-| Store | `https://www.waveshare.com/esp32-c6-epaper-1.54.htm` |
-| Docs | `https://docs.waveshare.com/ESP32-C6-ePaper-1.54` — **HTTP 200** |
-
-## Key specifications
-
-| Specification | Value |
-|---|---|
-| SoC | **ESP32-C6** — RISC-V **single-core**, up to 160 MHz |
-| Wireless | **Wi-Fi 6**, Bluetooth 5, **IEEE 802.15.4 (Zigbee 3.0 / Thread)** |
-| Memory | 512 KB HP SRAM, 16 KB LP SRAM, 320 KB ROM, **16 MB flash stacked** |
-| Display | 1.54-inch e-paper, **200 × 200** |
-| Audio | **ES8311** codec + microphone + amplifier + MX1.25 speaker header |
-| RTC | **PCF85063** (back side) |
-| Environment | **SHTC3** |
-| **I/O expander** | **TCA9554** — 8-bit programmable GPIO expander over I²C (back side) |
-| Storage | TF card slot, FAT32 |
-| Power | MX1.25 2-pin Li-ion header |
-| **Expansion** | **2 × 6-pin, 2.54 mm pitch female header** |
-| USB | Type-C, native ESP32-C6 USB |
-
-## What makes it distinct
-
-**Radios.** It is the only board in this survey with **802.15.4** — so Zigbee and
-Thread/Matter are available, and Wi-Fi 6 with them. For a battery-first e-paper
-sensor node joining a Thread mesh, that is a genuinely different proposition from
-everything else here, including the PaperMono (whose long-range story is LoRa, not
-mesh).
-
-**No PSRAM.** The specification lists 512 KB HP SRAM and 16 MB flash with **no
-PSRAM** — unlike the S3 boards. At 200 × 200 × 1 bit a full framebuffer is only 5 KB,
-so this is unlikely to bite for display work, but it rules the board out for anything
-that wanted a large buffer.
-
-**Single-core RISC-V**, so ports of Xtensa-specific code are not automatic.
-
-## Relevance to the 3.97-inch record
-
-The [ESP32-S3-ePaper-3.97 schematic](../esp32-s3-epaper-3.97/pinouts-and-buses.md)
-heads its GPIO allocation column **"IO Expander"** while containing **no I/O expander
-part**. This board *does* fit a **TCA9554** and Waveshare documents it explicitly.
-
-That makes **template reuse across the family the most probable explanation** for the
-stray heading on the 3.97 — but it is an explanation, not evidence. Tracked as
-[C-WS4](../esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws4--io-expander-column-heading-with-no-io-expander-part),
-and deliberately **not** used to invent a TCA9554 on the 3.97-inch board.
-
-## Why this is a stub
-
-Not retrieved: schematic, demo code, images, header pinout, panel controller identity,
-board dimensions. No artifact downloaded, nothing hashed. No `components/ti/tca9554`
-record was created — **this pass never saw that part in design data**, only in vendor
-prose about a board it did not research.
-
-## Sources
-
-| ID | Title | Class | URL | Retrieved | Version |
-|---|---|---|---|---|---|
-| `C01` | ESP32-C6-ePaper-1.54 — store listing | primary | `https://www.waveshare.com/esp32-c6-epaper-1.54.htm` | 2026-09-01 | `unknown` |
-| `C02` | ESP32-C6-ePaper-1.54 — documentation | primary | `https://docs.waveshare.com/ESP32-C6-ePaper-1.54` | 2026-09-01 | `unknown` (Docusaurus, undated) |
-
-## See also
-
-- [ESP32-S3-ePaper-1.54](../esp32-s3-epaper-1.54/README.md) — same size and form, Xtensa, no I/O expander
-- [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) — researched in depth
-- [ESP32-C6-WROOM-1](../../../components/espressif/esp32-c6-wroom-1/README.md) — the C6 module record already in this knowledge base (**this board's exact packaging is not established**)
diff --git a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/README.md b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/README.md
index b82254b..6a5e2b5 100644
--- a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/README.md
+++ b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/README.md
@@ -91,7 +91,7 @@ directory, with **no third-party mirror located**. Unlike Waveshare's `/wiki/com
 are not shared across product lines and would disappear with the product.
 
 Both are good candidates for `https://web.archive.org/save/`. The archived local copy under
-`archive/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals/`
+`../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals/`
 is currently the only guaranteed-identical source for the demo ZIP's exact bytes. The archive
 mirrors the **repository-root** path, so restoring is a straight copy back.
 
diff --git a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/manifest.json b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/manifest.json
index 86836b7..ce79da0 100644
--- a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/manifest.json
+++ b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/acquisition/manifest.json
@@ -39,7 +39,7 @@
       "url": "https://files.waveshare.com/wiki/ESP32-P4-WIFI6-Touch-LCD-XC/ESP32-P4-WIFI6-Touch-LCD-XC-Demo.zip",
       "sha256": "b5319593738e114270852d84be0fdd8ccdc21ef1dac897b15f4fad5069dd66b8",
       "bytes": 117768225,
-      "destination": "../repo-archive/doc/hardware/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals/ESP32-P4-WIFI6-Touch-LCD-XC-Demo.zip",
+      "destination": "../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals/ESP32-P4-WIFI6-Touch-LCD-XC-Demo.zip",
       "retrieved": "2026-08-24",
       "upstream_last_modified": "2025-06-28T09:28:46Z",
       "upstream_version": null,
diff --git a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/bsp-source-findings.md b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/bsp-source-findings.md
index 42d7af4..42d18de 100644
--- a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/bsp-source-findings.md
+++ b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/bsp-source-findings.md
@@ -3,7 +3,7 @@
 > Compiled **2026-08-26** from `waveshareteam/Waveshare-ESP32-components`,
 > `bsp/esp32_p4_wifi6_touch_lcd_xc/` (Apache-2.0, repo 74★, last push 2026-08-25).
 >
-> Local copy: `scratch/esp32-p4-wifi6-touch-lcd-xc/bsp-source/`
+> Local copy: `../hardware-doc-archive/scratch/esp32-p4-wifi6-touch-lcd-xc/bsp-source/`
 >
 > This BSP was found on 2026-08-26 by **code search**, after earlier passes had recorded it as
 > *"resolved by the Component Manager, not vendored"* and stopped. It is the single most
diff --git a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/research-log.md b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/research-log.md
index 33736ca..fb0313f 100644
--- a/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/research-log.md
+++ b/devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/research-log.md
@@ -152,7 +152,7 @@ produce no text token to pair against.
 |---|---|---|
 | 52 | RTC circuit | **Mapped** — `J1` 2-pin, `D2` B5819WS Schottky from `ESP_3V3`, `C39` 1 µF. **No current-limiting resistor** → **C18, a safety finding** |
 | 53 | Re-verify demo ZIP | Re-downloaded 2026-08-26: SHA-256 **matches the recorded manifest hash exactly** — vendor still serving identical bytes |
-| 54 | `/tmp` durability | Set up `/tmp/repo-archive/` after `/tmp/p4r` and `/tmp/hw` were both reclaimed mid-session, losing downloads |
+| 54 | `/tmp` durability | Set up `/tmp/hardware-doc-archive/` after `/tmp/p4r` and `/tmp/hw` were both reclaimed mid-session, losing downloads |
 
 The RTC finding is the clearest example in this research of **why schematic reading pays off**:
 Waveshare's "rechargeable cells only" note reads like a preference in prose. The circuit shows it
diff --git a/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md b/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md
index 7cfdab5..bb0749d 100644
--- a/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md
+++ b/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md
@@ -139,7 +139,7 @@ Upstream `Last-Modified`: schematic **2025-05-26**, demo ZIP **2025-06-28**.
 | Probe 2026-08-24 | `HTTP/1.1 200`, `Content-Length: 117768225` — **matches local byte size exactly** |
 | Extracted | 289 MiB, **5052 files** |
 | Extracted tree digest | `a856b1941de93ba892b244f03f139d958cb200807284f4ed66cd5d74b428c838` |
-| Location | `archive/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals/` |
+| Location | `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals/` |
 
 289 MiB extracted is dominated by three bundled third-party trees that are reproducible from
 upstream and were **not** vendored:
diff --git a/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals b/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals
deleted file mode 120000
index 87ceb72..0000000
--- a/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals
+++ /dev/null
@@ -1 +0,0 @@
-../../../../archive/devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/artifacts/originals
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-epaper-1.54/README.md b/devices/waveshare/esp32-s3-epaper-1.54/README.md
deleted file mode 100644
index 56ebe56..0000000
--- a/devices/waveshare/esp32-s3-epaper-1.54/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Waveshare ESP32-S3-ePaper-1.54 — *stub*
-
-> **SKUs 32298 / 32299 / 34211 / 34212.** Research snapshot **2026-09-01**.
-> **Stub record**: surveyed, not researched in depth. All claims are vendor
-> statements (`reported-working`) from the storefront and `docs.waveshare.com`.
-> No artifacts retrieved, no hardware in hand.
-
-Created during the [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) pass.
-**This board matters for one specific reason:** it is the Waveshare e-paper board
-that actually has an **expansion header**, which the 3.97-inch flagship does not.
-
-## Identity and variants
-
-| SKU | Product | Note |
-|---|---|---|
-| **32298** | ESP32-S3-ePaper-1.54 | |
-| **32299** | ESP32-S3-ePaper-1.54-EN | |
-| **34211** | **ESP32-S3-Touch-ePaper-1.54** | touch variant |
-| **34212** | ESP32-S3-Touch-ePaper-1.54-EN | touch variant |
-
-| Field | Value |
-|---|---|
-| Price | **USD 15.99 – 22.99** (observed 2026-09-01, waveshare.com, US region) |
-| Store | `https://www.waveshare.com/esp32-s3-epaper-1.54.htm` |
-| Docs | `https://docs.waveshare.com/ESP32-S3-ePaper-1.54` — **HTTP 200** |
-
-The `-EN` suffix marks a documentation/packaging variant, consistent with the
-3.97-inch board where `-EN` is the **without-battery** SKU. **Not verified for this
-product.**
-
-## Key specifications
-
-| Specification | Value |
-|---|---|
-| Module | **`ESP32-S3-PICO-1-N8R8`** — 8 MB flash, 8 MB PSRAM stacked |
-| CPU | Xtensa LX7 dual-core, up to 240 MHz |
-| SRAM / ROM | 512 KB / 384 KB |
-| Wireless | 2.4 GHz Wi-Fi, Bluetooth 5 (LE), **onboard chip antenna** |
-| Display | **1.54-inch e-paper, 200 × 200** |
-| Audio | **ES8311** codec + microphone + MX1.25 speaker header + onboard speaker |
-| RTC | **PCF85063** (back side) |
-| Environment | **SHTC3** temperature and humidity |
-| Storage | TF card slot, FAT32 |
-| Power | MX1.25 2-pin Li-ion header |
-| Buttons | PWR and BOOT side buttons |
-| **Expansion** | **2 × 6-pin, 2.54 mm pitch female header** — *"Reserved … for external expansion"* |
-| USB | Type-C, native ESP32-S3 USB |
-
-Note the parts overlap almost exactly with the 3.97-inch board — same codec, same
-RTC, same environmental sensor. Waveshare is clearly building one platform across
-sizes, which is useful: findings transfer between them more readily than usual.
-
-## Why this board is the honest answer to "e-paper development with expansion"
-
-The [PaperMono record](../../m5stack/papermono/README.md) recommends "a Waveshare
-ESP32 e-paper board" for e-paper development **with expansion**. The 3.97-inch board
-— the one that actually competes with a PaperMono on display and price — turns out to
-have **no expansion header at all**
-([C-WS1](../esp32-s3-epaper-3.97/gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards)).
-
-**This one does.** The trade is severe and should be stated plainly:
-
-| | ESP32-S3-ePaper-1.54 | ESP32-S3-ePaper-3.97 | M5Stack PaperMono |
-|---|---|---|---|
-| Panel | 1.54", **200 × 200** | 3.97", 800 × 480 | 3.97", 480 × 800 |
-| Pixels | **40 000** | 384 000 | 384 000 |
-| Expansion | **2 × 6 × 2.54 mm** | none | none |
-| Price (2026-09-01) | USD 15.99–22.99 | USD 34.99–47.99 | USD 65.00 |
-
-**You give up 90 % of the pixels to get the header.** For attaching a sensor and
-learning e-paper that is often the right trade; for anything where the page is the
-product it is not a PaperMono substitute at all.
-
-The header's **pinout is not established** — the docs present it as an image only,
-and no schematic was retrieved. That is the first thing a real record here needs.
-
-## Why this is a stub
-
-Not retrieved: schematic, demo code, images, header pinout, panel controller identity,
-board dimensions, community projects. No artifact downloaded, nothing hashed.
-
-## Sources
-
-| ID | Title | Class | URL | Retrieved | Version |
-|---|---|---|---|---|---|
-| `E01` | ESP32-S3-ePaper-1.54 — store listing | primary | `https://www.waveshare.com/esp32-s3-epaper-1.54.htm` | 2026-09-01 | `unknown` |
-| `E02` | ESP32-S3-ePaper-1.54 — documentation | primary | `https://docs.waveshare.com/ESP32-S3-ePaper-1.54` | 2026-09-01 | `unknown` (Docusaurus, undated) |
-
-## See also
-
-- [ESP32-C6-ePaper-1.54](../esp32-c6-epaper-1.54/README.md) — same size, RISC-V, Wi-Fi 6, **plus a TCA9554 I/O expander**
-- [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) — researched in depth
-- [M5Stack PaperMono comparisons](../../m5stack/papermono/comparisons-and-recommendations.md)
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/README.md b/devices/waveshare/esp32-s3-epaper-3.97/README.md
deleted file mode 100644
index 46b4e39..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/README.md
+++ /dev/null
@@ -1,400 +0,0 @@
-# Waveshare ESP32-S3-ePaper-3.97
-
-> ESP32-S3 e-paper development board, 3.97 inch, 800 × 480, 4-level greyscale.
-> Research snapshot **2026-09-01**. No hardware in hand — every claim here is
-> `reported-working` (vendor-stated) or `inferred`. Nothing is `executed-success`.
-
-This record exists to back a recommendation. The
-[M5Stack PaperMono](../../m5stack/papermono/README.md) record advised readers who
-want a general e-paper development board with expansion to "prefer Inkplate or a
-Waveshare ESP32 e-paper board" — but every Waveshare record in this knowledge
-base was an **LCD** board, so the second half of that advice was unsupported.
-That was tracked as conflict **C24**. This record closes it.
-
----
-
-> ## ⚠ Second pass, 2026-09-01 — read this before the sections below
->
-> This record was **written twice on the same day by two concurrent sessions**. The
-> first pass concluded that Waveshare publishes no documentation, no schematic, no
-> sample code, no price and no panel controller for this board. **All of those
-> absences are false**, and the sections below have been corrected in place.
->
-> **Root cause:** the first pass tested the *legacy* wiki (`waveshare.com/wiki/…`),
-> got a 404, and read that as product-level absence. Waveshare migrated this product
-> to a newer platform — **`docs.waveshare.com/ESP32-S3-ePaper-3.97`, HTTP 200** —
-> which this repository's own
-> [Waveshare sourcing guide §8.2](../../../vendors/waveshare/README.md) already says
-> to *"Check … first"*. A 404 on a deprecated host is evidence about that host.
->
-> **What actually exists**, all retrieved 2026-09-01 and hashed:
->
-> | First pass said | Actually |
-> |---|---|
-> | No documentation | [`docs.waveshare.com/ESP32-S3-ePaper-3.97`](https://docs.waveshare.com/ESP32-S3-ePaper-3.97) + a `Resources-And-Documents` page |
-> | No schematic | **Retained** — [`artifacts/schematic/`](artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf), 257 550 B, `b1203145…` |
-> | No pinout | **Recovered from that schematic** — [`pinouts-and-buses.md`](pinouts-and-buses.md) |
-> | No sample code | [`waveshareteam/ESP32-S3-ePaper-3.97`](https://github.com/waveshareteam/ESP32-S3-ePaper-3.97) @ `9b12d40` — 14 examples + factory firmware |
-> | No price | **USD 34.99 – 47.99**, three SKUs |
-> | No panel controller | **[SSD1677](../../../components/solomon-systech/ssd1677/README.md)** — stated in the panel manual |
-> | Nothing downloaded | **Six PDFs retained and hashed**; see [Artifacts](#artifacts) |
->
-> Two substantive corrections follow from the new evidence, and both matter:
->
-> 1. **The PMIC is an [X-Powers AXP2101](../../../components/x-powers/axp2101/README.md), not the "TG28" the vendor's marketing names** — established from the schematic *and* Waveshare's own firmware. [C-WS2](gaps-and-conflicts.md#c-ws2--tg28-versus-axp2101)
-> 2. **This board has no expansion header of any kind** — so the very recommendation that sent us here is, for this board, *refuted*. [C-WS1](gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards)
->
-> The original claims are preserved as history in
-> [C-WS10](gaps-and-conflicts.md#c-ws10--first-pass-recorded-absences-that-are-not-real)
-> rather than deleted.
-
----
-
-## Why this board specifically
-
-Waveshare currently sells seven ESP32 e-paper products (see
-[Sibling products](#sibling-products)). This one was chosen because it is the
-closest like-for-like comparison to the PaperMono that exists:
-
-| | Waveshare ESP32-S3-ePaper-3.97 | [M5Stack PaperMono](../../m5stack/papermono/README.md) |
-|---|---|---|
-| SoC | ESP32-S3R8 | ESP32-S3R8 |
-| PSRAM / Flash | 8 MB / 16 MB | 8 MB / 16 MB |
-| Panel | 3.97", 800 × 480, 4 grey | 3.97", 480 × 800, 4 grey |
-| **Active area** | **86.40 × 51.84 mm** | **51.84 × 86.40 mm** |
-
-Same SoC, same memory configuration, same panel size, same greyscale depth —
-and the active area matches **to 0.01 mm**, transposed. See
-[Are these the same panel?](#are-these-the-same-panel) below.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Name | ESP32-S3-ePaper-3.97 |
-| Manufacturer | Waveshare Electronics (Shenzhen) |
-| Store page | `https://www.waveshare.com/esp32-s3-epaper-3.97.htm` (retrieved 2026-09-01, HTTP 200) |
-| **Documentation** | **`https://docs.waveshare.com/ESP32-S3-ePaper-3.97`** — HTTP 200. *Corrected 2026-09-01: the legacy `/wiki/` route 404s because the product lives on the newer platform, not because documentation is absent* |
-| **Official source** | **`https://github.com/waveshareteam/ESP32-S3-ePaper-3.97`** @ `9b12d40731a80213b927ee8a421cae4082952819` (2026-03-20). No `LICENSE` file — licence **`unknown`** |
-| **SKUs** | **33552** (with Li battery) · **33810** (`-EN`, without battery) · **33811** (`-Kit`: battery + 16 GB TF card + card reader + USB cable). All three flagged `unsaleable: false` on 2026-09-01 |
-| **Price** | **USD 34.99 – 47.99**, observed **2026-09-01**, waveshare.com, **US region**, single unit, before shipping and duty. *Corrected — the first pass recorded this as unobtainable; the markup uses the JSON key `"sku "` with a trailing space, which a search for `"sku"` misses* |
-| Bundled with every SKU | An **8 Ω 1 W speaker** |
-
-## Key specifications
-
-All from the vendor storefront, retrieved 2026-09-01. Evidence status
-`reported-working` — these are vendor claims, not measurements.
-
-| Specification | Value | Component record |
-|---|---|---|
-| SoC | ESP32-S3R8, Xtensa LX7 dual-core, up to 240 MHz — fitted as an **`ESP32-S3-WROOM-1-N16R8` module** *(module part number from the schematic)* | [esp32-s3r8](../../../components/espressif/esp32-s3r8/README.md) |
-| Memory | 512 KB SRAM, 384 KB ROM, 8 MB **octal** PSRAM, 16 MB external flash. *The storefront's "What's On Board" block swaps these two — [C-WS3](gaps-and-conflicts.md#c-ws3--the-storefront-swaps-flash-and-psram)* | — |
-| Wireless | 2.4 GHz Wi-Fi 802.11 b/g/n, Bluetooth 5 LE, onboard antenna | — |
-| Display | 3.97" e-paper, 800 × 480, black/white, **4 greyscale**, driven by an **SSD1677** | **[3.97inch e-Paper panel](../../../components/waveshare/3.97inch-e-paper/README.md)** · [SSD1677](../../../components/solomon-systech/ssd1677/README.md) |
-| Active area | 86.40 × 51.84 mm; pixel pitch 0.108 mm; **DPI 235** | — |
-| Viewing angle | > 170° | — |
-| Refresh — full | 3.5 s | — |
-| Refresh — fast | 2.8 s | — |
-| Refresh — partial | 0.6 s *(the panel manual says 0.3 s at 23 °C — [C-WS6](gaps-and-conflicts.md#c-ws6--refresh-times-disagree-between-module-and-panel-documents))* | — |
-| Refresh — 4-greyscale | 3.5 s *(panel manual: 3 s at 23 °C)* | — |
-| Refresh power | < 40 mW *(panel manual: 36 mW typical at 3.0 V; 0.003 mW deep sleep; 120 mA peak)* | — |
-| Operating temperature | **0 to +50 °C** *(panel manual — the vendor's board pages state none)* | — |
-| IMU | QMI8658A 6-axis (3-axis accel + 3-axis gyro), `INT1` GPIO39, `INT2` GPIO40 | [qmi8658a](../../../components/qst/qmi8658a/README.md) |
-| RTC | PCF85063**ATL**, interrupt on GPIO45, with a dedicated backup-cell header | [pcf85063a](../../../components/nxp/pcf85063a/README.md) |
-| Environment | SHTC3 temperature and humidity, I²C `0x70` | [shtc3](../../../components/sensirion/shtc3/README.md) |
-| **Power management** | **X-Powers AXP2101** at I²C `0x34` — charger, multi-rail regulator, power-key controller, backup-cell charger. **Waveshare's marketing calls this "TG28"; the schematic and the vendor's own firmware both say AXP2101 — [C-WS2](gaps-and-conflicts.md#c-ws2--tg28-versus-axp2101)** | **[axp2101](../../../components/x-powers/axp2101/README.md)** |
-| Battery | 3.7 V Li-ion on **PH1.25/MX1.25 header `H3`**; charge 200 mA CC to 4.2 V *(firmware default)*. Separate **RTC backup-cell header `H4`**, actively charged at 3.0 V | — |
-| Audio — codec | **ES8311** mono codec, I²S on GPIO13/14/21/47/48 | [es8311](../../../components/everest-semiconductor/es8311/README.md) |
-| Audio — amplifier | **NS4150B** class-D, gated by GPIO39, out to speaker header `H2` | [ns4150b](../../../components/nsiway/ns4150b/README.md) |
-| Audio — input | Onboard microphone, differential `MIC_P`/`MIC_N` to the codec | — |
-| Storage | microSD (TF) slot, socket `TF-07F`, FAT32. **Net names are SPI-style — [C-WS5](gaps-and-conflicts.md#c-ws5--sd-card-spi-names-but-4-bit-nets)** | [micro-sd-sdmmc](../../../components/generic/micro-sd-sdmmc/README.md) |
-| Input | Programmable PWR *(an AXP2101 input, not a GPIO)* and BOOT side buttons; **3-way rotary navigation switch** on GPIO4/5/6 | — |
-| USB | Type-C, receptacle `H1`, **native ESP32-S3 USB on GPIO19/20 — no USB-UART bridge fitted** | [usb-c-interface](../../../components/generic/usb-c-interface/README.md) |
-| **Expansion** | **None.** No 2.54 mm header, no Qwiic/easyC, no broken-out GPIO — [C-WS1](gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards) | — |
-| Operating voltage | 3.3 V | — |
-
-The QMI8658A, PCF85063A and SSD1677 already had records in this knowledge base from
-other boards, and were **reused rather than duplicated** — which is itself a small
-signal about how conventional Waveshare's part selection is. Four records were added
-by the second pass because the parts were newly evidenced *and* their datasheets were
-obtained: [AXP2101](../../../components/x-powers/axp2101/README.md),
-[ES8311](../../../components/everest-semiconductor/es8311/README.md),
-[SHTC3](../../../components/sensirion/shtc3/README.md) and the
-[3.97inch e-Paper panel](../../../components/waveshare/3.97inch-e-paper/README.md);
-plus [NS4150B](../../../components/nsiway/ns4150b/README.md) as identity-only, and a
-stub for [QMI8658A](../../../components/qst/qmi8658a/README.md), whose datasheet had
-been sitting here since 2026-08-23 with no record beside it.
-
-**What the vendor's specification table still does not say**, after the second pass:
-there is **no battery capacity**, **no board-level power consumption in any state**,
-**no board dimensions** and **no enclosure**. The operating-temperature range above
-comes from the *panel* manual, not from any board page. This is a bare development
-board, not a finished product — and unlike the PaperMono it is not sold as one.
-
-## Full technical detail
-
-The second pass produced primary-evidence documents that are too long for this page:
-
-| Document | What is in it |
-|---|---|
-| **[Pinouts and buses](pinouts-and-buses.md)** | The **complete GPIO allocation table** recovered from the schematic and cross-checked against the vendor's driver, the four-device I²C bus, power domains and charge settings, the connector census, and the pin conflicts |
-| **[Development, examples and firmware](development.md)** | The 14 vendor examples, the AXP2101 driver audit, factory-firmware images and offsets, the xiaozhi AI-voice firmware, and licence status |
-| **[Conflicts and gaps](gaps-and-conflicts.md)** | Eleven conflicts and six gaps, including the TG28/AXP2101 identity, the expansion refutation and the panel-identity question |
-| **[Sources](sources.md)** | Twenty sources with class, retrieval date, version and local path; plus every failed retrieval |
-| **[Commands](commands.md)** | Every command that produced a fact here, including the PDF-extraction route that made the schematic readable |
-| **[Acquisition manifest](acquisition/manifest.json)** | Fifteen artifact records with hashes, sizes, licences and dispositions |
-
-## Are these the same panel?
-
-The PaperMono's panel is a **DKE `DEPG0397BBS770F3`** with an active area of
-**51.84 × 86.40 mm**, 480 × 800, 4-level greyscale, driven by an SSD1677
-([component record](../../../components/dke/depg0397bbs770f3/README.md)).
-
-Waveshare states **86.40 × 51.84 mm**, 800 × 480, 4-level greyscale.
-
-Those are the same numbers transposed — portrait versus landscape convention.
-Combined with identical resolution and greyscale depth, the most likely
-explanation is that **both boards use the same 3.97" panel, or two panels built
-to the same specification**, which would be unsurprising: DKE sells to board
-vendors, and 3.97" is an unusual size.
-
-**This is `inferred`, not established — but the second pass strengthened it
-considerably.** The panel manual (Rev 1.0, 2025-04-24) states the controller
-outright: **`4-2: Driver IC: SSD1677`** — the *same controller as the PaperMono's
-panel* — and gives **DPI 235**, which the DKE panel also reports. So the match is now
-four-way: active area to 0.01 mm, resolution, DPI, and controller.
-
-What is *still* missing is the one thing that would settle it: **Waveshare publishes
-no panel supplier or part number** — not on the storefront, not in the docs, not in
-the manual, and not on the schematic's text layer, where the panel appears only as
-FPC connector `J2`. A teardown photograph of the FPC marking on either board would
-close it in seconds.
-
-Recorded as an open question rather than asserted:
-[C-WS8](gaps-and-conflicts.md#c-ws8--is-this-the-same-panel-as-the-papermonos), with
-the panel documented in its own right at
-[`components/waveshare/3.97inch-e-paper`](../../../components/waveshare/3.97inch-e-paper/README.md).
-
-One place the two panel documents **actively disagree**: Waveshare's manual says
-*"800 gate × 480 source"*, while the DKE record derives the opposite from SSD1677
-register values. Low practical impact, but unresolved —
-[C-WS7](gaps-and-conflicts.md#c-ws7--gate-versus-source-orientation).
-
-If it is the same panel, the PaperMono's panel findings transfer — in particular
-the DC-balance hazard, the "roughly one full refresh per ten partial refreshes"
-guidance, and the manual's `2Grey Level` versus marketed 4-grey contradiction.
-
-## Refresh performance compared
-
-This is the one place where both vendors publish numbers for the same panel
-size, so it is worth putting side by side — with the caveat that **neither set
-was independently measured** and the two are not necessarily measured the same
-way.
-
-| Mode | Waveshare (vendor) | PaperMono (vendor, via M5GFX) |
-|---|---|---|
-| Full / quality | 3.5 s | 4.71 s (`epd_quality`) |
-| Fast | 2.8 s | 0.34 s (`epd_fast`) |
-| Partial | 0.6 s | 0.07 s (`epd_fastest`) |
-| 4-greyscale | 3.5 s | — |
-| Text | — | 0.45 s (`epd_text`) |
-
-The two sets are **not comparable as published**. M5Stack's figures are labelled
-lab results for specific M5GFX LUTs — and this knowledge base has already
-recorded that those LUTs may no longer be the ones shipped, and that M5Stack
-itself warns its waveforms are unstable. Waveshare's are unlabelled as to method
-or waveform. Treating "0.07 s versus 0.6 s" as a real eight-fold advantage would
-be unsupportable. See
-[`../../m5stack/papermono/performance.md`](../../m5stack/papermono/performance.md).
-
-## What each board is actually for
-
-The specifications overlap heavily; the design intent does not.
-
-**Waveshare leans into sensing and voice.** An audio codec, a microphone path
-explicitly aimed at online LLM services (DeepSeek, Doubao are named), a
-temperature/humidity sensor, and a rotary navigation switch. Its stated
-applications are voice interaction, e-reader, calendar and weather display.
-
-**PaperMono leans into radio and power.** NFC (ST25R3916), LoRa (SX1262), a
-frontlight, and a five-state hardware power manager built around a second
-microcontroller. It has no audio output, no environmental sensor, and no
-expansion connector at all.
-
-So the honest framing is not "which is better" but this — **and the second pass
-inverted half of it**:
-
-**Neither board has an expansion connector.** The sentence that stood here
-previously — that Waveshare "gives you a development board with headers" — was
-written before the schematic was read, and it is **wrong**. The complete connector
-census is one USB-C, three PH1.25-2P power/speaker JSTs, the panel FPC and a microSD
-socket. No 2.54 mm header, no Qwiic, no broken-out GPIO, and every usable GPIO
-already committed. See [C-WS1](gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards).
-
-What Waveshare actually gives you over the PaperMono is **sensing, sound and a
-backup-battery provision at roughly half the price**; what the PaperMono gives you is
-**radios, a frontlight and an enclosed product with a real power state machine**.
-Neither substitutes for the other on the other's workload, and **neither is a good
-answer to "I need to attach hardware"** — for that, within Waveshare's own catalogue,
-the answer is the 1.54-inch boards, which do carry a 2 × 6 header and give up 90 % of
-the pixels to do it ([ESP32-S3-ePaper-1.54](../esp32-s3-epaper-1.54/README.md),
-[ESP32-C6-ePaper-1.54](../esp32-c6-epaper-1.54/README.md)).
-
-## Sibling products
-
-Waveshare's current ESP32 e-paper line, from the storefront search
-(retrieved 2026-09-01). Only the 3.97" is documented in depth here; the others
-are recorded so the population is known and a future pass need not re-derive it.
-
-| Slug | SKUs | Price, 2026-09-01, US | What it is | Record |
-|---|---|---|---|---|
-| `esp32-s3-epaper-3.97` | 33552 / 33810 / 33811 | **USD 34.99–47.99** | **this record** — 3.97", 800 × 480, ESP32-S3 | — |
-| `e-paper-esp32-driver-board` | 15823 | USD 14.99 | Universal driver board, **original ESP32**, drives **23 documented raw panels** over a 24-pin FPC. Legacy wiki only | [stub](../e-paper-esp32-driver-board/README.md) |
-| `esp32-s3-epaper-1.54` | 32298 / 32299 / **34211 / 34212 (touch)** | USD 15.99–22.99 | 1.54", 200 × 200, ESP32-S3-PICO-1-N8R8. **Has a 2 × 6 2.54 mm expansion header** | [stub](../esp32-s3-epaper-1.54/README.md) |
-| `esp32-c6-epaper-1.54` | 34393 / 34394 | USD 16.99–17.99 | 1.54", 200 × 200, **ESP32-C6 — Wi-Fi 6, Zigbee/Thread**. Expansion header **plus a TCA9554 I/O expander** | [stub](../esp32-c6-epaper-1.54/README.md) |
-| `esp32-s3-epaper-1.54g` | 34585 / 34586 | USD 17.99–18.99 | 1.54", 200 × 200, **`G` = red/yellow/black/white 4-colour** — *confirmed from the page title, no longer a guess* | none |
-| `esp32-s3-epaper-13.3e6` | 34349 | **USD 259.99** | 13.3", **`E6` = E Ink Spectra 6 full colour**, with an ESP32-S3 driver board and audio codec — *confirmed from the page title* | none |
-| `esp32-s3-photopainter` | 32408 / 32753 | USD 82.99–83.99 | 7.3" Spectra 6 photo frame in a wood surround. **An appliance, not a development board** | [stub](../esp32-s3-photopainter/README.md) |
-
-**Corrected 2026-09-01:** the first pass flagged the `g` and `e6` suffixes as
-unverified guesses. Both are now **confirmed from the products' own page titles** —
-`G` is the four-colour (red/yellow/black/white) variant, `E6` is E Ink Spectra 6.
-Prices and SKUs were added in the same pass.
-
-Also in the survey but **not ESP32**: `photopainter` (24708/24709, RP2040-based),
-`photopainter-b` (30068/30315, processor `unknown`) and `e-paper-esp8266-driver-board`
-(14138, ESP8266). Recorded so they are not mistaken for members of this family.
-
-### Which sibling answers "e-paper development with expansion"
-
-**Not this one.** Of the seven, only the two 1.54-inch boards document an expansion
-header, and they do it at 200 × 200 — 40 000 pixels against this board's 384 000.
-That trade is the real finding of the survey and is set out in
-[C-WS1](gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards).
-
-## Documentation status
-
-**Corrected 2026-09-01.** The first pass recorded three "gaps" here that are not
-gaps; see the [banner](#-second-pass-2026-09-01--read-this-before-the-sections-below)
-and [C-WS10](gaps-and-conflicts.md#c-ws10--first-pass-recorded-absences-that-are-not-real).
-What Waveshare publishes for this board is, in fact, better than average for the
-vendor: a documentation site, a schematic, a panel manual, four IC datasheets and an
-official example repository with factory firmware.
-
-**Real gaps that remain**, fully enumerated in
-[gaps-and-conflicts.md](gaps-and-conflicts.md#gaps):
-
-1. **No rendered schematic read** — no PDF rasteriser on this host, so connectivity is
-   text adjacency only (`G1`).
-2. **The 14 vendor examples were enumerated but not retrieved** (`G2`).
-3. **Factory firmware not downloaded** — ~54 MB across four images (`G3`).
-4. **No imagery, and no board dimensions** — the vendor publishes an outline drawing
-   as a figure only (`G4`, `G5`).
-5. **No declared framework versions.** Neither the docs nor the repository state a
-   minimum ESP-IDF or Arduino-core version.
-6. **Nothing hardware-verified** (`G6`).
-
-### Vendor retrieval traps
-
-Two, both folded into [`vendors/waveshare`](../../../vendors/waveshare/README.md)
-because they will affect every future Waveshare pass.
-
-**1 — The legacy wiki no longer holds new products.** `/wiki/ESP32-S3-ePaper-3.97`
-returns **404** while `/wiki/E-Paper_ESP32_Driver_Board` returns 200. The two hosts
-are **disjoint, not layered**: new products are on `docs.waveshare.com`, older ones
-remain on the wiki, and `docs.waveshare.com/E-Paper-ESP32-Driver-Board` is itself a
-404. **Check both hosts before concluding anything is unpublished.**
-
-**2 — Waveshare's MediaWiki API is broken.** As of **2026-09-01**:
-
-```
-https://www.waveshare.com/wiki/api.php?...        → HTTP 200, but body is
-https://www.waveshare.com/wiki/index.php?...      → HTTP 200, but body is
-
-  Parse error: syntax error, unexpected '?' in
-  /yundisk/web/waveshare/dotcom/w/includes/Setup.php on line 472
-```
-
-A **PHP fatal parse error with HTTP 200** — it fails in the worst possible way,
-because any script checking status codes treats it as success. The vendor guide's
-`action=parse&prop=wikitext` route is dead; rendered pretty URLs still work.
-
-**3 — The e-paper category page returns 200 and zero products.** It is JS-rendered.
-Use `/catalogsearch/result/?q=` to enumerate, never the category page. Note that the
-query `esp32 e-ink` returns **nothing** — the storefront does not treat "e-ink" as a
-synonym for "e-Paper".
-
-## Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| W01 | ESP32-S3 3.97inch e-Paper Development Board | Waveshare | primary | store listing | `waveshare.com/esp32-s3-epaper-3.97.htm` | 2026-09-01 | All specifications in this record |
-| W02 | Storefront search `e-paper esp32` | Waveshare | primary | store search | `waveshare.com/catalogsearch/result/?q=e-paper+esp32` | 2026-09-01 | The seven-product sibling population |
-| W03 | Wiki 404s for three slug spellings | Waveshare | primary | wiki | `waveshare.com/wiki/ESP32-S3-ePaper-3.97` | 2026-09-01 | Verified absence of a wiki page |
-| W04 | MediaWiki API PHP parse error | Waveshare | primary | api | `waveshare.com/wiki/api.php` | 2026-09-01 | The retrieval trap above |
-
-**The full source table — twenty rows with class, medium, retrieval date, version,
-what each establishes, its limitations and its local path — is
-[`sources.md`](sources.md).** The four rows above are the first pass's and are kept
-for continuity; `W03`'s "verified absence of a wiki page" is true of the *legacy host
-only* and should be read with
-[C-WS10](gaps-and-conflicts.md#c-ws10--first-pass-recorded-absences-that-are-not-real).
-
-## Artifacts
-
-**Corrected 2026-09-01.** The first pass recorded "no artifacts were retained …
-nothing was downloaded, so nothing needed hashing". **Six PDFs were in fact
-published**, and all six are now retained and hashed. Every one was validated by
-**magic bytes (`%PDF-`), never by HTTP status**.
-
-| Artifact | Bytes | SHA-256 | Filed under | Why there |
-|---|---:|---|---|---|
-| [`ESP32-S3_e-Paper-3.97-schematic.pdf`](artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf) | 257 550 | `b12031451374e2333e8eca2b8290c40b4c67955b1f12df17b96f3ee479e6f0be` | **this device** | Describes this board |
-| [`schematic-text-reflowed.tsv`](artifacts/schematic/schematic-text-reflowed.tsv) | 27 638 | *regenerable — see [commands.md](commands.md)* | **this device** | Derived reading aid, 1 150 positioned tokens |
-| [3.97inch e-Paper manual **Rev 1.0, 2025-04-24**](../../../components/waveshare/3.97inch-e-paper/README.md) | 2 774 287 | `4f756734…` | **component** | Describes a *panel* |
-| [AXP2101 datasheet **V1.4 EN**](../../../components/x-powers/axp2101/README.md) | 1 554 740 | `9e51d16d…` | **component** | Describes a *chip* |
-| [ES8311 datasheet](../../../components/everest-semiconductor/es8311/README.md) | 729 315 | `be42a2cb…` | **component** | Describes a *chip* |
-| [SHTC3 datasheet](../../../components/sensirion/shtc3/README.md) | 928 256 | `d315fe3d…` | **component** | Describes a *chip* |
-| [PCF85063A datasheet **Rev. 6** (Waveshare mirror)](../../../components/nxp/pcf85063a/README.md) | 535 722 | `93b38487…` | **component** | Describes a *chip*; **kept alongside NXP's Rev. 7, which this KB already held** |
-| Storefront + two docs pages | 324 780 | *date-pinned, not hash-pinned* | **this device** | `artifacts/source-snapshots/` |
-
-Four of these are **component** artifacts even though a device pass fetched them —
-filed by what they *describe*, per the method. The device cites each one where it is
-used, so a reader starting here can reach them without knowing which component owns
-them.
-
-**Not downloaded**, recorded with URLs and expected sizes in
-[`acquisition/manifest.json`](acquisition/manifest.json): the two 16 MB factory
-firmware images and the two xiaozhi images (~54 MB total), and the vendor repository
-itself (~50 MB).
-
-**Two downloads failed and were deleted rather than kept under a misleading
-extension** — one returned XML, the other **267 KB of HTML** behind a `.pdf` URL.
-Both are recorded in [`sources.md`](sources.md#failed-and-negative-retrievals).
-
-**Licences:** every artifact above is **`unknown`** — none states terms, and the
-vendor repository has no `LICENSE` file. Recorded as metadata; nothing was omitted
-over licensing.
-
-## Used by / referenced from
-
-**Devices and comparisons**
-
-- [M5Stack PaperMono — comparisons and recommendations](../../m5stack/papermono/comparisons-and-recommendations.md) — §5, where this record replaces "an explicit gap, not a verdict"
-- [M5Stack PaperMono — gaps and conflicts, C24](../../m5stack/papermono/gaps-and-conflicts.md) — the conflict this record closes
-- [M5Stack PaperMono](../../m5stack/papermono/README.md) — the *when not to use* recommendation that started this
-
-**Sibling Waveshare e-paper boards** (stubs created by the same pass)
-
-- [e-Paper ESP32 Driver Board](../e-paper-esp32-driver-board/README.md) · [ESP32-S3-ePaper-1.54](../esp32-s3-epaper-1.54/README.md) · [ESP32-C6-ePaper-1.54](../esp32-c6-epaper-1.54/README.md) · [ESP32-S3-PhotoPainter](../esp32-s3-photopainter/README.md)
-
-**Components this board uses**
-
-| Reused, already in this knowledge base | Added by this pass |
-|---|---|
-| [ESP32-S3R8](../../../components/espressif/esp32-s3r8/README.md) · [SSD1677](../../../components/solomon-systech/ssd1677/README.md) · [PCF85063A](../../../components/nxp/pcf85063a/README.md) · [micro-SD](../../../components/generic/micro-sd-sdmmc/README.md) · [USB-C interface](../../../components/generic/usb-c-interface/README.md) | [AXP2101](../../../components/x-powers/axp2101/README.md) · [3.97inch e-Paper panel](../../../components/waveshare/3.97inch-e-paper/README.md) · [ES8311](../../../components/everest-semiconductor/es8311/README.md) · [SHTC3](../../../components/sensirion/shtc3/README.md) · [NS4150B](../../../components/nsiway/ns4150b/README.md) · [QMI8658A](../../../components/qst/qmi8658a/README.md) *(stub over a pre-existing artifact)* |
-
-**Vendor knowledge**
-
-- [Waveshare documentation-sourcing guide](../../../vendors/waveshare/README.md) — extended with this pass's findings
-- [All devices](../../README.md) · [All components](../../../components/README.md)
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/acquisition/manifest.json b/devices/waveshare/esp32-s3-epaper-3.97/acquisition/manifest.json
deleted file mode 100644
index b2e48a5..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/acquisition/manifest.json
+++ /dev/null
@@ -1,320 +0,0 @@
-{
-  "$comment": "Acquisition manifest — Waveshare ESP32-S3-ePaper-3.97. Covers every useful artifact, retained or not. Schema per hardware-device-research SKILL.md 'Artifact and Acquisition Manifests'. Null means not yet knowable; the reason is stated alongside.",
-  "device": "waveshare/esp32-s3-epaper-3.97",
-  "snapshot_date": "2026-09-01",
-  "hardware_in_hand": false,
-  "repository_root_relative": true,
-  "artifacts": [
-    {
-      "id": "S05",
-      "kind": "schematic",
-      "url": "https://files.waveshare.com/wiki/ESP32-S3-ePaper-3.97/ESP32-S3_e-Paper-3.97-schematic.pdf",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf",
-      "sha256": "b12031451374e2333e8eca2b8290c40b4c67955b1f12df17b96f3ee479e6f0be",
-      "bytes": 257550,
-      "media_type": "application/pdf",
-      "magic_validated": "%PDF-",
-      "retrieved": "2026-09-01",
-      "upstream_version": null,
-      "upstream_version_note": "No revision block found in the extracted text layer; sheet not rendered.",
-      "license": "unknown",
-      "license_evidence": "No notice in the document or on the serving page.",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "target_hardware": "ESP32-S3-ePaper-3.97, all SKUs",
-      "notes": "Primary design evidence. Establishes AXP2101 identity, the GPIO allocation table and the connector census. Altium export; text is one glyph per object. Derived reflow retained beside it.",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S05d",
-      "kind": "derived-extraction",
-      "url": null,
-      "url_note": "Derived locally; not downloadable. Reproduce with tools/pdftext.py + tools/reflow.py, see commands.md section 5.",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/schematic-text-reflowed.tsv",
-      "sha256": null,
-      "sha256_note": "Regenerable output; hash intentionally not pinned because it depends on the reflow thresholds recorded in commands.md.",
-      "bytes": 27638,
-      "retrieved": "2026-09-01",
-      "license": "unknown",
-      "license_evidence": "Derived from S05; inherits its unknown terms.",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "notes": "1150 tokens with x/y positions. Reading aid, not a netlist.",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S06",
-      "kind": "component-datasheet",
-      "url": "https://files.waveshare.com/wiki/3.97inch_e-Paper_HAT%2B/3.97inch_e-Paper.pdf",
-      "destination": "components/waveshare/3.97inch-e-paper/artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf",
-      "sha256": "4f756734dbfa7485c57e7ab7124f59f0afb00ca2600cda24a2285f02e4ab05cf",
-      "bytes": 2774287,
-      "magic_validated": "%PDF-",
-      "retrieved": "2026-09-01",
-      "upstream_version": "Rev 1.0, 2025-04-24 (revision history: 'New creation')",
-      "license": "unknown",
-      "license_evidence": "No stated terms.",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "filed_under": "component",
-      "filed_under_reason": "Describes a panel, not the board. Fetched during device research; filed by what it describes.",
-      "notes": "Establishes Driver IC = SSD1677. Text layer is offset-encoded (+29 / +26); decode with tools/deshift.py and validate against the cover heading before transcribing.",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S10",
-      "kind": "component-datasheet",
-      "url": "https://files.waveshare.com/wiki/common/ES8311.DS.pdf",
-      "destination": "components/everest-semiconductor/es8311/artifacts/es8311-datasheet-waveshare-mirror.pdf",
-      "sha256": "be42a2cb09093378feaccf55c227be579edc5a17786a11cc34254ea91264538a",
-      "bytes": 729315,
-      "magic_validated": "%PDF-",
-      "retrieved": "2026-09-01",
-      "upstream_version": "unknown",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "mirror_of": "Everest Semiconductor original — not obtained this pass",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S11",
-      "kind": "component-datasheet",
-      "url": "https://files.waveshare.com/wiki/common/Pcf85063atl1118-NdPQpTGE-loeW7GbZ7.pdf",
-      "destination": "components/nxp/pcf85063a/artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf",
-      "sha256": "93b384873539e770305b8982bcfa6387eac695650063b6a11279beae7a20602a",
-      "bytes": 535722,
-      "magic_validated": "%PDF-",
-      "retrieved": "2026-09-01",
-      "upstream_version": "NXP Rev. 6, 2015",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "duplicate_analysis": "NOT a duplicate. The knowledge base already holds pcf85063a-datasheet.pdf (726288 B, sha256 a09223dbb64278087ed566ba7597399ef40144da36905f6875d5aaf430f6000b) which is NXP Rev. 7 (2018). Different revision, different bytes. Both retained per SKILL.md step 18 rule 2.",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S12",
-      "kind": "component-datasheet",
-      "url": "https://files.waveshare.com/wiki/common/SHTC3_Datasheet.pdf",
-      "destination": "components/sensirion/shtc3/artifacts/shtc3-datasheet-waveshare-mirror.pdf",
-      "sha256": "d315fe3d00282ece1d8901c0936f8bcbaa87b159bcd0e71f9002d1f03b57a8f1",
-      "bytes": 928256,
-      "magic_validated": "%PDF-",
-      "retrieved": "2026-09-01",
-      "upstream_version": "unknown",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "mirror_of": "Sensirion original — not obtained this pass",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S13",
-      "kind": "component-datasheet",
-      "url": "https://raw.githubusercontent.com/lewisxhe/XPowersLib/master/datasheet/AXP2101_Datasheet_V1.4_en.pdf",
-      "destination": "components/x-powers/axp2101/artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf",
-      "sha256": "9e51d16d84d905c32a001a123be8e6c58213ee21e42d5bdb1458b731dba10f6d",
-      "bytes": 1554740,
-      "magic_validated": "%PDF-",
-      "retrieved": "2026-09-01",
-      "upstream_version": "V1.4, English",
-      "license": "unknown",
-      "license_evidence": "X-Powers document redistributed in an MIT-licensed library repository; the document itself states no terms. The library's licence does not govern the datasheet.",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "mirror_of": "X-Powers primary — no accessible primary URL found in this pass",
-      "failed_attempts": [
-        {"url": "https://files.waveshare.com/wiki/common/AXP2101.pdf", "result": "HTTP 404, body is XML", "retained": false},
-        {"url": "https://github.com/lewisxhe/XPowersLib/raw/master/datasheet/AXP2101_Datasheet_V1.0_en.pdf", "result": "HTTP 404, body is 267330 bytes of HTML", "retained": false}
-      ],
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S01s",
-      "kind": "page-snapshot",
-      "url": "https://www.waveshare.com/esp32-s3-epaper-3.97.htm",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/storefront-esp32-s3-epaper-3.97-2026-09-01.html",
-      "sha256": null,
-      "sha256_note": "Snapshot of a page that changes without notice; pinned by retrieval date, not by hash. Waveshare offers no immutable revision URL for storefront pages.",
-      "bytes": 200095,
-      "retrieved": "2026-09-01",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "notes": "Source of SKUs, prices, variant names, package contents and the flash/PSRAM self-contradiction (C-WS3).",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S02s",
-      "kind": "page-snapshot",
-      "url": "https://docs.waveshare.com/ESP32-S3-ePaper-3.97",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-overview-2026-09-01.html",
-      "bytes": 69131,
-      "sha256": null,
-      "sha256_note": "As S01s — no immutable revision URL is offered by the Docusaurus site.",
-      "retrieved": "2026-09-01",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "S03s",
-      "kind": "page-snapshot",
-      "url": "https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-resources-2026-09-01.html",
-      "bytes": 55554,
-      "sha256": null,
-      "sha256_note": "As S01s.",
-      "retrieved": "2026-09-01",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "repository",
-      "repo_state": "untracked",
-      "notes": "The download index for this product. Highest-yield single page.",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "F01",
-      "kind": "factory-firmware",
-      "url": "https://github.com/waveshareteam/ESP32-S3-ePaper-3.97/raw/9b12d40731a80213b927ee8a421cae4082952819/Firmware/Factory%20procedure/260314.bin",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/firmware/260314.bin",
-      "sha256": null,
-      "sha256_note": "NOT DOWNLOADED. Size is from the GitHub tree listing at the pinned commit; hash cannot be known without fetching.",
-      "bytes": 16777216,
-      "retrieved": null,
-      "upstream_version": "commit 9b12d40731a80213b927ee8a421cae4082952819, 2026-03-20",
-      "target_mcu": "ESP32-S3R8",
-      "image_role": "merged full-flash factory image (16 MB)",
-      "flash_offset": "0x0",
-      "flash_offset_evidence": "Firmware/ReadMe_EN.txt, verbatim: 'Burn the starting address 0x0'",
-      "companion_images": "none — single merged image",
-      "build_date": null,
-      "build_date_note": "Filename resembles 26-03-14 but that is a reading of a filename, not a parsed build identifier.",
-      "sdk_version": null,
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "reference-only",
-      "omission_reason": "2 x 16 MB plus 21 MB of xiaozhi images; not needed for the questions this pass answered. Recorded so a later pass can fetch and parse with tools/esp_image_info.py.",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "F02",
-      "kind": "factory-firmware",
-      "url": "https://github.com/waveshareteam/ESP32-S3-ePaper-3.97/raw/9b12d40731a80213b927ee8a421cae4082952819/Firmware/Factory%20procedure/260304.bin",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/firmware/260304.bin",
-      "sha256": null,
-      "bytes": 16777216,
-      "retrieved": null,
-      "image_role": "merged full-flash factory image, earlier build",
-      "flash_offset": "0x0",
-      "target_mcu": "ESP32-S3R8",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "omission_reason": "As F01.",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "F03",
-      "kind": "third-party-firmware",
-      "url": "https://github.com/waveshareteam/ESP32-S3-ePaper-3.97/raw/9b12d40731a80213b927ee8a421cae4082952819/Firmware/xiaozhi/ESP32-S3_e-Paper-3.97_xiaozhi-xs.bin",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/firmware/ESP32-S3_e-Paper-3.97_xiaozhi-xs.bin",
-      "sha256": null,
-      "bytes": 11179471,
-      "retrieved": null,
-      "image_role": "xiaozhi AI-voice application, e-ink landscape variant",
-      "flash_offset": "0x0",
-      "upstream_project": "https://github.com/78/xiaozhi-esp32",
-      "license": "unknown",
-      "license_evidence": "Waveshare ships the binary and points at the upstream project for source; upstream terms not verified this pass.",
-      "redistribution": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "F04",
-      "kind": "third-party-firmware",
-      "url": "https://github.com/waveshareteam/ESP32-S3-ePaper-3.97/raw/9b12d40731a80213b927ee8a421cae4082952819/Firmware/xiaozhi/ESP32-S3_e-Paper-3.97_xiaozhi.bin",
-      "destination": "devices/waveshare/esp32-s3-epaper-3.97/artifacts/firmware/ESP32-S3_e-Paper-3.97_xiaozhi.bin",
-      "sha256": null,
-      "bytes": 9920235,
-      "retrieved": null,
-      "image_role": "xiaozhi AI-voice application, audio-only variant",
-      "flash_offset": "0x0",
-      "upstream_project": "https://github.com/78/xiaozhi-esp32",
-      "license": "unknown",
-      "redistribution": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic"
-    },
-    {
-      "id": "R01",
-      "kind": "source-repository",
-      "url": "https://github.com/waveshareteam/ESP32-S3-ePaper-3.97",
-      "commit": "9b12d40731a80213b927ee8a421cae4082952819",
-      "commit_date": "2026-03-20T09:30:42Z",
-      "default_branch": "main",
-      "destination": null,
-      "sha256": null,
-      "bytes": 51449856,
-      "bytes_note": "GitHub-reported repository size, ~50 MB, includes the four firmware binaries.",
-      "retrieved": "2026-09-01",
-      "retrieved_note": "Metadata, tree listing and four individual files read via the API. The tree was NOT cloned.",
-      "license": "unknown",
-      "license_evidence": "No LICENSE file present; GitHub API reports license: null.",
-      "redistribution": "unknown",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "vendored_dependencies": [
-        {"name": "XPowersLib", "upstream": "https://github.com/lewisxhe/XPowersLib", "path": "ESP-IDF/08_ESP32-S3_e-Paper-3.97/components/axpPower/src", "version": "unknown", "modification_status": "unknown — not diffed against upstream this pass"},
-        {"name": "SensorLib", "upstream": "https://github.com/lewisxhe/SensorLib", "path": "Arduino/libraries/SensorLib", "version": "unknown", "modification_status": "unknown — not diffed against upstream this pass"}
-      ],
-      "reacquisition": "automatic"
-    }
-  ],
-  "not_acquired": [
-    {
-      "what": "Board product photography, PCB shots, dimension drawing",
-      "why": "Present on docs.waveshare.com as figures under 'Interfaces' and 'Dimensions'; not enumerated in this pass.",
-      "status": "manual",
-      "gap": "G4/G5"
-    },
-    {
-      "what": "Rendered schematic sheet image",
-      "why": "No PDF rasteriser available on this host (no poppler, mutool, pymupdf; no pip).",
-      "status": "blocked",
-      "gap": "G1"
-    },
-    {
-      "what": "The 14 vendor example projects",
-      "why": "Enumerated from the tree; only DEV_Config.h, EPD_3in97.h and axp_prot.cpp/.h read.",
-      "status": "automatic",
-      "gap": "G2"
-    }
-  ],
-  "verification": {
-    "magic_bytes_checked": true,
-    "all_retained_pdfs_begin_with_%PDF": true,
-    "failed_downloads_retained_under_misleading_extension": false,
-    "hash_deduplicated_against_existing_repository": true,
-    "duplicates_found": 0,
-    "near_duplicates_found": 1,
-    "near_duplicate_detail": "pcf85063a Rev.6 (Waveshare) vs Rev.7 (NXP, already held) — both kept, see C-WS11.",
-    "hardware_verified": false
-  }
-}
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf b/devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf
deleted file mode 100644
index 4191b1f..0000000
Binary files a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf and /dev/null differ
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/schematic-text-reflowed.tsv b/devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/schematic-text-reflowed.tsv
deleted file mode 100644
index 326d607..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/schematic/schematic-text-reflowed.tsv
+++ /dev/null
@@ -1,1089 +0,0 @@
-   531.92	    72.34	1
-   531.92	   206.09	2
-   531.92	   340.08	3
-   531.92	   474.06	4
-   531.92	   608.04	5
-   531.92	   742.03	6
-   520.07	   468.01	VCC3V3
-   518.68	   572.46	VCC
-   518.68	   599.67	GND
-   518.68	   758.78	1
-   516.59	   765.52	NC
-   514.96	   364.97	SD
-   514.96	   378.90	_C
-   514.96	   392.37	ard
-   514.96	   740.87	GDR
-   514.96	   758.78	2
-   513.34	    31.64	U
-   513.34	    39.53	SB
-   513.34	   686.43	R1
-   513.34	   765.52	GDR
-   511.94	   552.22	BS
-   511.94	   565.71	3-line SPI4-line SPI
-   511.71	   237.50	R
-   511.71	   245.16	TC
-   511.71	   740.87	RESE
-   511.71	   758.78	3
-   510.32	   686.43	2.2
-   510.32	   765.52	RESE
-   508.23	   758.78	4
-   506.60	   765.52	NC
-   505.21	   459.87	C19
-   505.21	   476.85	C134
-   505.21	   494.07	C16
-   505.21	   509.18	C17
-   505.21	   522.91	C18
-   505.21	   684.81	RESE
-   505.21	   720.63	C14.7uF/25V
-   505.21	   758.78	5
-   503.58	   120.26	D7
-   503.12	   765.52	VSH2
-   501.49	    50.24	A12/B1
-   501.49	    73.50	VBUS
-   501.49	   256.10	RTC_SDA
-   501.49	   276.57	ESP_I2C_SDA
-   501.49	   459.87	10uF
-   501.49	   476.85	100nF
-   501.49	   494.07	10uF
-   501.49	   509.18	1UF
-   501.49	   522.91	100nF
-   501.49	   553.85	BS
-   501.49	   594.55	EPD_VCC
-   501.49	   758.78	6
-   500.10	   684.11	2
-   499.63	    41.17	GND
-   499.63	   206.56	C11
-   499.63	   765.52	TSCL
-   498.01	    50.94	A9/B4
-   498.01	   256.10	RTC_SCL
-   498.01	   276.57	ESP_I2C_SCL
-   498.01	   569.20	R10
-   498.01	   582.69	NC
-   498.01	   758.78	7
-   496.38	    39.78	VBUS
-   496.38	    80.48	R3
-   496.38	   136.08	GND
-   496.38	   657.36	R2
-   496.38	   765.52	TSDA
-   494.52	    51.41	B5
-   494.52	   594.55	GND
-   494.52	   667.83	GDR1
-   494.52	   688.53	Q1
-   494.52	   740.87	BS
-   494.52	   758.78	8
-   492.90	    42.34	CC2
-   492.90	   765.52	BS
-   491.50	   217.96	2
-   491.50	   688.53	BSS138
-   491.27	    56.29	A8
-   491.27	   217.03	32.768KHz (2.0*1.2)
-   491.27	   569.20	R12
-   491.27	   582.69	0R
-   491.27	   740.87	EPD_BUSY9
-   489.41	    40.47	SBU1
-   489.41	    80.48	5.1K
-   489.41	   206.56	22pF
-   489.41	   657.36	1M
-   489.41	   765.52	BUSY
-   488.95	   112.58	LTVS16H5.0ET5G
-   487.79	    51.41	B6
-   487.79	   740.87	EPD_RST10
-   486.16	    42.34	DP2
-   486.16	   221.45	Y1U1
-   486.16	   280.99	VRTC
-   486.16	   470.57	GND
-   486.16	   684.11	3
-   486.16	   765.52	RST
-   484.54	    56.29	A7
-   484.54	    82.58	ESP_USB_N
-   484.54	   654.10	EPD_VCC
-   484.54	   740.87	EPD_DC11
-   482.68	    41.87	DN1
-   482.68	   206.56	C2
-   482.68	   226.33	1
-   482.68	   264.01	10
-   482.68	   765.52	D/C
-   481.05	    56.29	A6
-   481.05	    82.58	ESP_USB_P
-   481.05	   217.96	1
-   481.05	   233.08	OSCI
-   481.05	   252.15	VDD
-   481.05	   380.09	TF1
-   481.05	   429.63	GND
-   481.05	   740.87	EPD_CS12
-   479.43	    42.34	DP1
-   479.43	   210.28	22pF
-   479.43	   226.33	2
-   479.43	   264.01	9
-   479.43	   765.52	CS
-   477.57	    51.41	B7
-   477.57	   233.08	OSCOCLKOUT
-   477.57	   356.59	SD_D2
-   477.57	   376.13	1
-   477.57	   449.40	VCC3V3
-   477.57	   653.87	C3
-   477.57	   740.87	EPD_SCK13
-   475.94	    41.87	DN2
-   475.94	    80.48	R69
-   475.94	   226.33	3
-   475.94	   264.01	8
-   475.94	   382.64	D2
-   475.94	   666.20	L1
-   475.94	   765.52	SCLK
-   474.32	    56.29	A5
-   474.32	   233.08	CLKOE
-   474.32	   254.48	n.c.
-   474.32	   356.59	SD_CS
-   474.32	   376.13	2
-   474.32	   423.82	9
-   474.32	   740.87	EPD_DIN14
-   472.46	    42.34	CC1
-   472.46	   112.12	GND
-   472.46	   210.28	RTC_INT4
-   472.46	   264.01	7RTC_SCL
-   472.46	   382.64	CD/D3
-   472.46	   414.51	CD
-   472.46	   458.48	R1110K
-   472.46	   485.69	SD_CS
-   472.46	   765.52	SDI
-   470.83	    51.41	B8
-   470.83	   233.08	INT
-   470.83	   253.31	SCL
-   470.83	   356.59	SD_MOSI3
-   470.83	   666.20	10uH
-   470.83	   720.63	C121uF/50VEPD_VCC15
-   469.21	    40.47	SBU2
-   469.21	    80.48	5.1K
-   469.21	   226.33	5
-   469.21	   247.03	P
-   469.21	   264.01	6RTC_SDA
-   469.21	   382.64	CMD
-   469.21	   458.48	R8010K
-   469.21	   485.69	SD_CLK
-   469.21	   765.52	VDDIO
-   466.65	     8.37	A
-   466.65	    51.41	A4/B9
-   466.65	    92.81	VBUS
-   466.65	   233.08	VSS
-   466.65	   247.03	ESDA
-   466.65	   356.59	VCC3V3
-   466.65	   376.13	4
-   466.65	   650.84	4.7uF/25V
-   466.65	   757.38	16
-   466.65	   805.30	A
-   465.72	    39.78	VBUS
-   465.72	   288.20	C5
-   465.72	   382.64	VDD
-   465.72	   458.48	R6210K
-   465.72	   485.69	SD_MISO
-   465.72	   765.52	VCI
-   464.10	    50.24	A1/B12
-   464.10	   356.59	SD_CLK
-   464.10	   376.13	5
-   464.10	   512.91	R79
-   464.10	   757.38	17
-   462.70	   288.20	1uF
-   462.70	   677.60	C13
-   462.24	    41.17	GND
-   462.24	   223.77	PCF85063ATL
-   462.24	   382.64	CLK
-   462.24	   458.48	R6310K
-   462.24	   485.69	SD_MOSI
-   462.24	   765.52	VSS
-   460.61	    53.04	MTB
-   460.61	   245.17	1
-   460.61	   356.59	GND
-   460.61	   376.13	6
-   460.61	   512.91	NC
-   460.61	   592.46	EPD_VCC_AXP
-   460.61	   628.75	EPD_VCC
-   460.61	   720.63	C41uF/50V
-   460.61	   757.38	18
-   459.45	   245.17	1
-   458.99	    41.17	GND
-   458.99	   382.64	VSS
-   458.99	   458.48	R6410K
-   458.99	   485.69	SD_D2
-   458.99	   765.52	VDD
-   457.36	   356.59	SD_MISO
-   457.36	   376.13	7
-   457.36	   413.58	D
-   457.36	   757.38	19
-   455.50	   382.64	D0
-   455.50	   458.48	R6510K
-   455.50	   485.69	SD_D1
-   455.50	   765.52	VPP
-   454.34	   413.58	N
-   453.88	    33.26	H1
-   453.88	   356.59	SD_D1
-   453.88	   376.13	8
-   453.88	   608.28	R13
-   453.88	   626.89	NC
-   453.88	   671.31	4.7uF/25V
-   453.88	   720.63	C64.7uF/25V
-   453.88	   757.38	20
-   452.25	   382.64	D1
-   452.25	   413.58	G
-   452.25	   765.52	VSH1
-   450.86	   580.83	Q2
-   450.39	   542.91	VCC3V3
-   450.39	   673.18	D1
-   450.39	   720.63	C74.7uF/25VVGH21
-   449.00	   658.06	D2
-   449.00	   688.53	D3
-   449.00	   765.52	VGH
-   447.14	   373.57	TF
-   447.14	   383.81	 TF-07F
-   447.14	   576.87	2
-   447.14	   590.60	3
-   447.14	   608.28	R17
-   447.14	   626.89	0R
-   447.14	   720.63	C84.7uF/25V
-   447.14	   757.38	22
-   445.52	   411.95	0
-   445.52	   654.80	MBR0530MBR0530MBR0530
-   445.52	   765.52	VSL
-   443.66	    60.48	GND
-   443.66	   411.95	1
-   443.66	   720.63	C94.7uF/25VVGL23
-   442.73	   588.51	SI2301CDS-T1-E3
-   442.03	   242.61	GND
-   442.03	   508.02	GND
-   442.03	   765.52	VGL
-   440.64	   570.83	R20
-   440.64	   720.63	C101uF/50V
-   440.64	   757.38	24
-   438.55	   765.52	VCOM
-   437.15	   570.83	47K
-   435.06	   545.24	R21
-   435.06	   583.85	1
-   433.44	   758.78	0
-   431.81	   541.98	NC/47K
-   431.81	   669.45	VGL
-   431.81	   684.81	VGH
-   431.81	   765.52	0
-   429.03	   763.20	J2
-   425.08	   558.50	R29
-   423.68	   585.48	Q3
-   420.20	   585.48	8050
-   418.11	   558.50	10K
-   418.11	   710.39	²Ì=0+Ø…}5žÈPCB:,´0
-   414.86	    14.65	VBUSjUSBk+e$ÀEÕÈÐ2Ç4*6
-   414.86	   439.87	QMI8658A
-   413.46	   575.94	R30
-   409.98	   575.94	100K
-   409.75	    14.65	VMIDN´AÑÝ0È
-   407.89	   538.03	EPD_VCC_AXP
-   406.26	   173.76	VBUS
-   406.26	   193.07	UP1
-   404.64	    14.65	VSYSjEœ’
-   403.01	   143.75	C25
-   403.01	   155.85	10uF
-   403.01	   187.48	37
-   403.01	   264.01	VSYS
-   401.15	   104.21	GND
-   401.15	   195.63	VBUS
-   401.15	   502.21	VCC3V3
-   399.53	    14.65	SWȯ+XVBUSË+e&ȳ5
-   399.53	   167.01	VMID
-   399.53	   253.78	23
-   399.53	   278.20	C26
-   399.53	   290.07	2.2uF
-   397.90	   241.68	VIN1
-   397.90	   331.70	GND
-   396.04	   143.75	C27
-   396.04	   155.85	10uF
-   396.04	   187.48	36
-   396.04	   450.10	U2
-   396.04	   473.83	QMI8658A
-   394.42	   104.21	GND
-   394.42	   195.63	VMID
-   394.42	   278.20	L2
-   392.79	   253.78	22
-   390.93	   142.13	R14
-   390.93	   157.48	NC/0.01R-1%-0603
-   390.93	   243.08	LX1
-   390.93	   328.21	VCC3V3
-   390.93	   740.87	e-Pap
-   390.93	   767.81	er
-   389.31	    14.65	VBAT+e"un+eÕ
-   389.31	   278.20	1uH/3.5A
-   389.31	   417.77	GND
-   389.31	   445.91	1
-   389.31	   493.60	2
-   387.68	   452.43	SDO/SAO
-   387.68	   483.13	SDx
-   387.68	   581.06	GND
-   385.82	   187.48	34
-   385.82	   253.78	21
-   385.82	   302.16	C28
-   385.82	   314.02	22uF
-   385.82	   417.77	AXIS_SDA
-   385.82	   444.29	14
-   385.82	   493.60	3
-   384.20	   106.30	VSYS
-   384.20	   195.63	VSYS
-   384.20	   243.31	FB1
-   384.20	   331.70	GND
-   384.20	   452.43	SDA
-   384.20	   483.13	SCx
-   382.57	   417.77	AXSI_SCL
-   382.57	   444.29	13
-   380.72	   452.43	SCL
-   379.09	   120.03	C29
-   379.09	   131.89	100nFR15
-   379.09	   157.48	0.01R-1%-0603/NC
-   379.09	   417.77	VCC3V3
-   379.09	   444.29	12
-   379.09	   493.60	10
-   377.46	   104.21	GND
-   377.46	   452.43	CS
-   377.46	   484.30	NC
-   375.84	   253.78	20
-   375.84	   417.77	INT1
-   375.84	   445.91	4
-   375.84	   493.60	11
-   373.98	   227.26	DLDO1/DC1SW
-   373.98	   452.43	INT1
-   373.98	   484.30	NC
-   372.35	   120.03	C32
-   372.35	   131.89	22uFR16
-   372.35	   157.48	NC/0R
-   372.35	   187.48	32
-   372.35	   417.77	AXIS_INT2
-   372.35	   445.91	9
-   372.35	   468.01	O
-   370.73	   104.21	GND
-   370.73	   195.63	GPIO1
-   370.73	   452.43	INT2
-   370.73	   468.01	I
-   368.87	   293.55	AXP_SDA
-   368.87	   315.65	ESP_I2C_SDA
-   368.87	   464.76	DDDD
-   365.62	   293.55	AXP_SCL
-   365.62	   315.65	ESP_I2C_SCL
-   365.62	   464.76	DDNN
-   363.76	   145.61	L4
-   363.76	   464.76	VVGG
-   362.13	   120.03	C34
-   362.13	   131.89	22uF
-   362.13	   187.48	35
-   362.13	   264.01	VSYS
-   360.51	   104.21	GND
-   360.51	   195.63	SW
-   358.88	    34.89	Pow
-   358.88	    55.10	er
-   358.88	   140.50	2.2uH 2.5*2*1.2  3A
-   358.88	   253.78	24
-   358.88	   293.55	PWROKR18
-   358.88	   325.89	NCESP_RESET
-   358.88	   592.92	aveshare
-   358.19	   210.28	AXP2101
-   358.19	   241.68	VIN2
-   358.19	   462.90	8567
-   358.19	   579.43	W
-   355.40	   686.43	LSK1
-   355.40	   705.28	LSK2
-   355.40	   725.75	LSK3
-   355.40	   742.73	LSK4
-   351.92	   173.76	VBAT
-   351.92	   253.78	25
-   351.92	   293.55	CHGLEDR4
-   351.92	   325.89	0RESP_CHG
-   350.29	   243.08	LX2
-   348.66	   143.75	C36
-   348.66	   155.85	2.2uF
-   348.66	   187.48	33
-   346.81	   104.21	GND
-   346.81	   195.63	BAT
-   345.18	   253.78	26
-   345.18	   293.55	AXP_IRQR8
-   345.18	   325.89	0RPWR_IRQ
-   344.25	   560.59	ESP32-S3 e-Paper-3.97
-   343.55	   243.31	FB2
-   341.70	   142.13	R19
-   341.70	   155.85	'+eLkNTC 10K
-   341.70	   187.48	31
-   340.07	   104.21	GND
-   340.07	   195.63	TS
-   340.07	   461.27	VCC3V3
-   334.96	   169.34	CHGLED1
-   333.10	     8.37	B
-   333.10	   195.63	CHGLED
-   333.10	   805.30	B
-   331.48	   421.03	INT1
-   331.48	   456.85	AXIS_INT1
-   329.85	   346.36	H3
-   328.22	    31.64	RTC_INT_ESP
-   328.22	   143.75	C41
-   328.22	   155.85	2.2uF
-   328.22	   188.88	2
-   328.22	   436.38	R9
-   328.22	   450.10	NC
-   326.37	   104.21	GND
-   326.37	   195.63	VREF
-   326.37	   341.94	1
-   324.74	   264.01	VSYS
-   324.74	   320.54	VBAT
-   324.74	   348.68	1
-   323.12	   173.99	VSYS
-   323.12	   341.94	2
-   323.12	   359.85	K2+e"Õ
-   321.49	   253.78	6
-   321.49	   348.68	2
-   319.63	   241.68	VIN3
-   318.24	    27.45	1
-   318.24	   143.75	C43
-   318.24	   155.85	1uF/6.3V
-   318.24	   187.48	17
-   318.24	   693.41	MIC2
-   316.38	   124.68	GND
-   316.38	   195.63	ALDOIN
-   316.38	   345.43	0
-   316.38	   574.32	A
-   316.38	   582.21	udio
-   314.52	   167.01	AudioCTR_VCC
-   314.52	   253.78	5
-   314.52	   318.44	GND
-   314.52	   352.17	0
-   313.13	    31.17	D8
-   313.13	   243.08	LX3
-   311.97	   346.36	PH1.25-2P
-   311.27	   143.75	C44
-   311.27	   155.85	2.2uF/6.3V
-   311.27	   187.48	18
-   309.88	    31.17	B5819WS
-   309.88	   195.63	ALDO1
-   308.25	    27.45	2
-   307.79	   170.04	Audio_VCC
-   307.79	   253.78	4
-   306.16	   243.31	FB3
-   304.30	   143.75	C45
-   304.30	   155.85	2.2uF/6.3V
-   304.30	   187.48	19
-   303.84	   701.09	DDDT
-   302.68	   195.63	ALDO2
-   301.05	   167.25	EPD_VCC_AXP
-   301.05	   450.10	SHTC
-   301.05	   480.06	3
-   301.05	   701.09	DNNA
-   299.42	   701.09	VGGD
-   299.19	    31.64	RTC_INT
-   297.57	   143.75	C14
-   297.57	   155.85	2.2uF/6.3V
-   297.57	   187.48	16
-   297.57	   757.61	C137
-   295.94	   195.63	ALDO3
-   295.94	   327.98	VBA_CKUPH4
-   295.94	   732.49	L5
-   294.31	   264.01	VSYS
-   292.46	    85.37	VCC3V3
-   292.46	   314.02	R61
-   292.46	   331.00	0R
-   292.46	   341.94	1
-   292.46	   666.89	Audio_VCC
-   292.46	   699.46	1234
-   290.83	   187.48	15
-   290.83	   253.78	7
-   290.83	   293.55	VBACKUP
-   290.83	   348.68	1
-   290.83	   732.49	0R
-   289.21	    27.45	2
-   289.21	   195.63	ALDO4
-   289.21	   241.68	VIN4
-   289.21	   341.94	2
-   287.58	   359.85	RTC+e"×
-   287.58	   757.61	1uF
-   287.35	   348.68	2
-   287.35	   460.34	U3SHTC3
-   287.35	   700.16	C55
-   285.72	   683.18	C58
-   284.10	    31.17	D4
-   284.10	   253.78	8
-   284.10	   723.65	C60
-   284.10	   754.12	C61
-   282.70	    92.81	R24
-   282.24	   172.13	VSYS
-   282.24	   243.08	LX4
-   282.24	   345.43	0
-   282.24	   358.22	ÄN´+‰È
-   280.61	    31.17	B5819WS
-   280.61	   318.44	GND
-   280.61	   352.17	0
-   280.61	   455.92	1
-   280.61	   483.37	4
-   280.61	   684.81	100nF
-   280.61	   700.16	10uF
-   280.61	   723.65	NC
-   280.61	   754.12	NC
-   279.22	    27.45	1
-   279.22	    92.81	10K
-   277.82	   346.36	PH1.25-2P
-   277.82	   417.30	VCC3V3
-   277.82	   462.66	VDDVSS
-   277.82	   505.23	GND
-   277.13	   187.48	13
-   277.13	   253.78	9
-   275.50	   101.42	PWR_OUT
-   275.50	   195.63	BLDOIN
-   275.50	   243.31	FB4
-   275.50	   553.85	PA_OUTL+L7
-   275.50	   589.67	0R
-   273.88	   438.24	ESP_I2C_SCL2
-   273.88	   483.37	3ESP_I2C_SDA
-   272.02	   462.66	SCLSDA
-   270.86	    90.49	3
-   270.86	   471.50	P
-   270.39	   187.48	12
-   270.39	   253.78	10
-   270.39	   594.55	C118
-   268.77	   195.63	BLDO1
-   268.77	   234.70	CPUSLDO
-   268.77	   471.50	E
-   267.14	    56.76	R25
-   267.14	   439.40	C50
-   267.14	   620.14	H2
-   265.28	    31.64	PWRON
-   265.28	    80.02	1
-   263.66	   187.48	14
-   263.66	   253.78	11
-   263.66	   439.40	100nF
-   263.66	   581.06	NC/330pF
-   263.66	   604.79	C120
-   262.03	    96.30	T1
-   262.03	   195.63	BLDO2
-   262.03	   227.26	DLDO2/DC4SW
-   262.03	   469.87	5
-   262.03	   614.32	1
-   262.03	   709.23	AGND
-   260.17	    56.76	1K
-   260.17	   620.84	1
-   258.78	    29.77	R26
-   258.55	    92.81	BSS138LT1G(ƒ‡J1)
-   258.55	   571.52	AGND
-   258.55	   614.32	2
-   256.92	    90.49	2
-   256.92	   594.55	C125N
-   256.92	   620.84	2
-   256.92	   681.32	MIC_P
-   255.53	    29.77	510R
-   254.60	   598.74	NC
-   253.44	   264.01	VRTC
-   252.28	   598.74	C/
-   252.28	   617.58	0
-   252.28	   681.32	MIC_N
-   251.11	   605.49	3
-   249.95	   169.34	AXP_SDA39
-   249.95	   253.78	28
-   249.95	   278.20	C46
-   249.95	   290.07	2.2uF
-   249.95	   433.12	GND
-   249.95	   598.74	3/3
-   249.95	   624.33	0
-   248.33	   195.63	SDA
-   248.33	   236.57	RTCLDO
-   248.33	   314.72	GND
-   248.33	   598.74	30
-   246.70	   467.08	GND
-   246.70	   618.51	PH1.25-2P
-   246.24	   598.74	0p
-   244.84	   598.74	pF
-   244.84	   715.05	C74
-   244.84	   744.12	C76
-   243.22	   169.34	AXP_SCL40
-   243.22	   253.78	27
-   243.22	   278.20	C47
-   243.22	   290.07	2.2uF
-   243.22	   598.74	F
-   241.82	   715.05	1uf
-   241.82	   744.12	NC
-   241.59	   195.63	SCK
-   241.59	   234.01	VBACKUP
-   241.59	   314.72	GND
-   241.59	   553.85	PA_OUTL-L8
-   241.59	   587.81	0R
-   239.97	   676.90	AGND
-   238.57	    29.08	Key1
-   236.48	   142.13	R27
-   236.48	   157.48	10K
-   236.48	   169.34	AXP_IRQ38
-   236.48	   260.76	VBACKUP
-   234.86	   121.66	VRTC
-   234.86	   195.63	IRQ
-   234.86	   610.60	AGND
-   229.75	   169.34	PWROK
-   229.75	   187.48	29
-   229.75	   253.78	3
-   227.89	   195.63	PWROK
-   227.89	   240.52	GND1
-   227.89	   311.23	GND
-   222.78	   169.34	PWRON
-   222.78	   187.48	30
-   222.78	   253.78	41
-   221.15	   195.63	PWRON
-   221.15	   240.98	EPAD
-   219.53	   434.75	Pin
-   219.53	   450.54	 Ou
-   219.53	   467.96	t
-   217.90	    24.89	GND
-   217.90	    87.69	GND
-   214.42	   584.55	Audio_SDA
-   214.42	   679.69	MIC_P
-   210.93	   584.55	Audio_SCL
-   210.93	   679.69	MIC_N
-   209.31	   638.52	R71
-   207.68	   647.36	10K
-   205.82	   427.31	M
-   204.20	   592.92	C53C54
-   202.57	   502.90	TP1
-   200.71	   428.70	5V
-   200.71	   443.36	VBUS
-   200.71	   590.13	2
-   200.71	   600.37	2
-   200.71	   721.33	AGND
-   199.32	     8.37	C
-   199.32	   590.13	2
-   199.32	   600.37	2
-   199.32	   619.21	AGND
-   199.32	   805.30	C
-   197.46	   502.90	TP2
-   197.46	   704.11	AGND
-   197.00	   590.13	p
-   197.00	   600.37	p
-   195.60	   427.31	GND
-   195.60	   443.36	GND
-   195.60	   590.13	F
-   195.60	   600.37	F
-   195.60	   658.75	09876
-   195.60	   681.32	C571uF
-   194.44	   655.26	021111
-   192.35	   502.90	TP3
-   192.35	   674.57	U8ES8311
-   190.73	   427.54	3.3V
-   190.73	   443.36	VCC3V3
-   188.87	   718.77	C67C68
-   187.24	   502.90	TP4
-   187.24	   656.89	PEAAND
-   185.62	   428.47	RX
-   185.62	   443.36	ESP_UART_RX
-   185.62	   656.89	E
-   185.62	   670.62	1I
-   185.39	   660.38	CTD
-   185.39	   719.46	11
-   183.76	   588.51	AGND
-   183.76	   663.64	ASCM
-   183.76	   719.46	uu
-   182.13	   502.90	TP5
-   182.13	   670.62	I
-   182.13	   719.46	FF
-   181.44	   663.64	D_V
-   180.51	   428.70	TX
-   180.51	   443.36	ESP_UART_TX
-   180.51	   667.13	CM
-   179.35	   663.64	CI
-   177.02	   502.90	TP6
-   175.86	   667.13	M
-   175.40	   427.54	SDA
-   175.40	   443.36	ESP_I2C_SDA
-   173.54	   667.13	D
-   172.84	   667.13	/
-   171.91	   502.90	TP7
-   170.29	   160.97	WROOM-1/2
-   170.29	   427.77	SCL
-   170.29	   443.36	ESP_I2C_SCL
-   170.29	   667.13	P
-   168.66	    29.77	ES
-   168.66	    43.24	P32-S
-   168.66	    70.88	3
-   168.66	   667.13	1
-   168.43	   629.44	1
-   168.43	   667.13	C
-   168.43	   701.09	15
-   166.80	   502.90	TP8
-   166.80	   636.19	CCLK
-   166.80	   667.13	I
-   166.80	   681.78	ADCVREF
-   165.18	   188.18	ePaper
-   165.18	   214.47	Audio
-   165.18	   240.29	SD Card
-   165.18	   268.90	RTC
-   165.18	   291.00	KEY & LED
-   165.18	   316.58	QMI8658A
-   165.18	   345.19	Power
-   165.18	   369.39	OTS
-   165.18	   428.00	GP0
-   165.18	   443.36	ESP_BOOT
-   165.18	   544.54	VCC3V3
-   165.18	   629.44	2
-   165.18	   701.09	14
-   163.55	   565.48	R43
-   163.55	   636.19	MCLK
-   163.55	   667.13	M
-   163.55	   681.78	DACVREF
-   161.69	   159.11	IO Expander
-   161.69	   502.90	TP9
-   161.69	   629.44	3
-   161.69	   701.09	13
-   161.69	   751.10	C711uFOUTN
-   160.07	    56.76	U7
-   160.07	    70.71	ESP32-S3-WROOM-1-N16R8
-   160.07	   428.00	GP1
-   160.07	   443.36	PWR_OUT
-   160.07	   636.19	PVDD
-   160.07	   687.60	OUTN
-   158.44	   162.59	GP4
-   158.44	   290.07	Button_Up
-   158.44	   629.44	4
-   158.44	   701.09	12
-   158.44	   751.10	C721uFOUTP
-   156.59	   565.48	0R
-   156.59	   636.19	DVDD
-   156.59	   660.38	L
-   156.59	   688.06	OUTP
-   154.96	   162.59	GP5
-   154.96	   286.81	Button_Function
-   154.96	   629.44	5
-   154.96	   660.38	C
-   154.96	   701.09	11
-   154.96	   725.75	0R
-   153.33	   636.19	DGND
-   153.33	   687.60	AVDD
-   152.87	   660.38	S
-   151.48	   162.59	GP6
-   151.48	   288.44	Button_Down
-   151.48	   575.94	C81C82
-   151.48	   660.38	_
-   151.48	   737.61	C83C84
-   149.85	   717.14	R44
-   148.22	   162.59	GP7
-   148.22	   660.38	IC
-   148.22	   710.39	C85Audio_VCC
-   147.99	   239.12	SD_D1
-   147.99	   734.82	2
-   147.99	   745.05	2
-   145.90	   734.82	2
-   145.90	   745.05	2
-   144.74	   162.59	GP15
-   144.74	   239.12	SD_MISO
-   144.74	   575.94	100nF100nF
-   144.74	   660.38	MT
-   144.04	   707.60	1
-   144.04	   734.82	p
-   144.04	   745.05	p
-   142.42	   660.38	/DU
-   142.42	   707.60	u
-   142.42	   734.82	F
-   142.42	   745.05	F
-   141.26	   162.59	GP16
-   141.26	   239.12	SD_CLK
-   141.26	   670.62	ND
-   141.26	   707.60	F
-   140.09	   660.38	KOKI
-   138.93	   673.87	N
-   138.00	   162.59	GP17
-   138.00	   239.12	SD_MOSI
-   138.00	   660.38	LDCD
-   136.38	    36.75	GND
-   136.38	    52.80	1
-   136.38	   114.21	40
-   136.38	   126.77	GND
-   136.38	   660.38	CSRSG
-   134.52	    59.55	GND
-   134.52	   102.58	GND
-   134.52	   162.59	GP18
-   134.52	   239.12	SD_CS
-   134.52	   571.52	AGNDAGND
-   134.52	   602.23	AGND
-   134.52	   660.38	SALDA
-   132.89	    36.75	VCC3V32
-   132.89	   114.21	39
-   132.89	   126.77	GP1
-   131.27	    59.55	3V3
-   131.27	   104.44	IO1
-   131.27	   162.59	GP8
-   131.27	   239.12	SD_D2
-   131.27	   705.97	AGND
-   131.27	   733.19	AGND
-   129.41	    36.75	ESP_EN3
-   129.41	   114.21	38
-   129.41	   126.77	GP2
-   128.02	   658.75	67890
-   127.78	    59.55	EN
-   127.78	   104.44	IO2
-   127.78	   162.59	GP19
-   127.78	   363.34	ESP_USB_N
-   126.16	    36.75	GP4
-   126.16	    52.80	4
-   126.16	   114.21	37
-   126.16	   126.77	GP43
-   126.16	   672.25	1
-   124.30	    59.55	IO4
-   124.30	   101.19	TXD0
-   124.30	   162.59	GP20
-   124.30	   363.34	ESP_USB_P
-   122.68	    36.75	GP5
-   122.68	    52.80	5
-   122.68	   114.21	36
-   122.68	   126.77	GP44
-   122.68	   431.26	KEY
-   122.68	   454.95	 & LED
-   121.05	    59.55	IO5
-   121.05	   101.19	RXD0
-   121.05	   162.59	GP3
-   121.05	   184.69	EPD_BUSY
-   119.19	    36.75	GP6
-   119.19	    52.80	6
-   119.19	   114.21	35
-   119.19	   126.77	GP42
-   117.57	    59.55	IO6
-   117.57	   102.81	IO42
-   117.57	   162.59	GP46
-   117.57	   184.69	EPD_RST
-   117.57	   463.36	C15
-   117.57	   587.81	I2S_MCLK
-   115.94	    36.75	GP7
-   115.94	    52.80	7
-   115.94	   114.21	34
-   115.94	   126.77	GP41
-   114.08	    59.55	IO7
-   114.08	   102.81	IO41
-   114.08	   162.59	GP9
-   114.08	   184.69	EPD_DC
-   114.08	   587.81	I2S_SCLK
-   114.08	   733.42	0.1uF
-   112.46	    36.75	GP15
-   112.46	    52.80	8
-   112.46	   114.21	33
-   112.46	   126.77	GP40
-   110.83	    59.55	IO15
-   110.83	   102.81	IO40
-   110.83	   162.59	GP10
-   110.83	   184.69	EPD_CS
-   110.83	   587.81	I2S_DSOUT
-   110.83	   705.28	OUTP
-   110.83	   732.49	C111
-   110.83	   749.47	R75
-   110.83	   764.82	150KPA_INL+
-   109.20	    36.75	GP16
-   109.20	    52.80	9
-   109.20	   114.21	32
-   109.20	   126.77	GP39
-   109.20	   668.52	AGND
-   107.81	   463.36	100nF
-   107.35	    59.55	IO16
-   107.35	   102.81	IO39
-   107.35	   162.59	GP11
-   107.35	   184.69	EPD_SCK
-   107.35	   587.81	I2S_LRCK
-   107.35	   725.75	C112
-   105.72	    36.75	GP17
-   105.72	    51.17	10
-   105.72	   114.21	31
-   105.72	   126.77	GP38
-   104.09	    59.55	IO17
-   104.09	   102.81	IO38
-   104.09	   162.59	GP12
-   104.09	   184.69	EPD_DIN
-   104.09	   587.81	I2S_DSDIN
-   102.24	    36.75	GP18
-   102.24	    51.41	11
-   102.24	   114.21	30
-   102.24	   126.77	GP37
-   102.24	   434.75	ESP_BOOT
-   100.61	    59.55	IO18
-   100.61	   102.81	IO37
-   100.61	   162.59	GP13
-   100.61	   210.28	I2S_MCLK
-   100.61	   493.37	GND
-   100.61	   725.75	22pF
-    98.98	    36.75	GP8
-    98.98	    51.17	12
-    98.98	   114.21	29
-    98.98	   126.77	GP36
-    98.98	   461.03	Key2
-    97.13	    59.55	IO8
-    97.13	   102.81	IO36
-    97.13	   162.59	GP14
-    97.13	   210.28	I2S_SCLK
-    95.50	    36.75	GP19
-    95.50	    51.17	13
-    95.50	   114.21	28
-    95.50	   126.77	GP35
-    95.50	   616.88	C103
-    95.50	   631.31	C104
-    95.50	   645.73	C105
-    93.88	    59.55	IO19
-    93.88	   102.81	IO35
-    93.88	   162.59	GP21
-    93.88	   210.28	I2S_DSOUT
-    92.02	    36.75	GP20
-    92.02	    51.17	14
-    92.02	   114.21	27
-    92.02	   126.77	GP0
-    91.55	   614.09	2
-    91.55	   628.51	2
-    91.55	   642.94	2
-    90.39	    59.55	IO20
-    90.39	   104.44	IO0
-    90.39	   162.59	GP47
-    90.39	   210.28	I2S_LRCK
-    90.39	   614.09	2
-    90.39	   628.51	2
-    90.39	   642.94	2
-    90.39	   721.33	AGND
-    88.30	    68.39	6012341785
-    88.30	   614.09	p
-    88.30	   628.51	p
-    88.30	   642.94	p
-    86.91	    64.90	349111112444
-    86.91	   162.59	GP48
-    86.91	   210.28	I2S_DSDIN
-    86.91	   614.09	F
-    86.91	   628.51	F
-    86.91	   642.94	F
-    86.91	   722.49	22pF
-    85.28	   114.21	41
-    85.28	   126.77	GND
-    85.28	   705.28	OUTN
-    85.28	   732.49	C1190.1uFR76
-    85.28	   764.82	150KPA_INL-
-    83.66	    64.90	IOIOIOIOIOIOIOIOIOIOIOIOEP
-    83.66	   162.59	GP45
-    83.66	   261.22	RTC_INT_ESP
-    83.66	   449.64	R29
-    82.03	   458.71	K
-    82.03	   476.62	A
-    82.03	   487.55	ESP_LED1
-    82.03	   725.75	C121
-    80.17	   162.59	GP0
-    80.17	   364.97	ESP_BOOT
-    80.17	   420.56	GND
-    76.92	    63.27	567890123456
-    76.92	   162.59	GP35
-    76.92	   370.08	NC
-    76.92	   449.64	4.7K
-    75.53	    63.27	111112222222
-    75.53	   626.89	AGND
-    73.44	   162.59	GP36
-    73.44	   370.08	NC
-    73.44	   575.48	AudioCTR_VCC
-    71.81	   449.64	R30
-    71.81	   463.36	Led2
-    69.95	   162.59	GP37
-    69.95	   370.08	NC
-    69.95	   458.71	K
-    69.95	   476.62	A
-    69.95	   487.55	ESP_LED2
-    66.70	   162.59	GP38
-    66.70	   342.87	PWR_IRQ
-    65.54	     8.37	D
-    65.54	   805.30	D
-    64.61	    66.53	6012341785
-    64.61	   449.64	4.7K
-    64.61	   721.33	AGND
-    63.22	   162.59	GP39
-    63.22	   208.42	AudioCTR_PIN
-    63.22	   315.65	AXIS_INT1
-    62.98	    63.27	349111112444
-    61.36	    63.27	PPPPPPPPPPPP
-    59.73	   162.59	GP40
-    59.73	   315.65	AXIS_INT2
-    59.73	   463.36	Led1
-    59.73	   587.81	R74
-    59.27	    63.27	GGGGGGGGGGGG
-    56.48	   162.59	GP41
-    56.48	   210.28	Audio_SDA
-    56.48	   262.85	RTC_SDA
-    56.48	   315.65	AXIS_SDA
-    56.48	   342.87	AXP_SDA
-    56.48	   363.34	ESP_I2C_SDA
-    56.48	   587.81	NC
-    56.48	   621.77	U9
-    53.00	   162.59	GP42
-    53.00	   210.28	Audio_SCL
-    53.00	   262.85	RTC_SCL
-    53.00	   315.65	AXSI_SCL
-    53.00	   342.87	AXP_SCL
-    53.00	   363.34	ESP_I2C_SCL
-    53.00	   540.12	AudioCTR_PIN
-    53.00	   592.92	AudioCTR_PWR1
-    53.00	   648.52	8PA_OUTL+
-    51.37	   423.82	VCC3V3
-    51.37	   624.33	CTRLOUT+
-    49.75	    87.69	R22
-    49.75	   101.42	4.7K
-    49.75	   162.59	GP43
-    49.75	   290.07	ESP_LED1
-    49.75	   363.34	ESP_UART_RX
-    49.75	   564.08	R23
-    49.75	   577.57	0R
-    49.75	   617.58	2
-    49.75	   648.52	7
-    47.89	    58.85	ESP_I2C_SDA
-    47.89	   624.33	BypassGND
-    46.26	   162.59	GP44
-    46.26	   290.07	ESP_LED2
-    46.26	   363.34	ESP_UART_TX
-    46.26	   488.95	U4
-    46.26	   599.67	PA_INL+3
-    46.26	   648.52	6
-    44.64	    58.85	ESP_I2C_SCL
-    44.64	   624.33	IN+
-    44.64	   636.66	VDD
-    44.64	   721.33	VCC3V3
-    42.78	   112.12	VCC3V3
-    42.78	   162.59	GP2
-    42.78	   342.87	ESP_CHG
-    42.78	   599.67	PA_INL-4
-    42.78	   648.52	5
-    42.78	   657.59	PA_OUTL-C122C123C124
-    41.15	   433.12	R31
-    41.15	   448.47	10KButton_Down
-    41.15	   484.53	B
-    41.15	   505.46	0
-    41.15	   624.33	IN-
-    41.15	   636.19	OUT-
-    39.53	    87.69	R28
-    39.53	   101.42	4.7K
-    39.53	   162.59	GP1
-    39.53	   342.87	PWR_OUT
-    36.04	   621.77	NS4150B
-    36.04	   664.34	10uF 0402
-    36.04	   686.43	100nF1uF
-    34.42	    87.69	R6
-    34.42	   101.42	10K
-    34.42	   433.12	R67
-    34.42	   448.47	10KButton_FunctionC
-    34.42	   505.46	A
-    32.56	    38.38	ESP_RESETESP_EN
-    30.93	   618.51	C126
-    29.31	    38.38	ESP_BOOT
-    29.31	    60.48	GP0
-    29.31	   651.54	AGND
-    27.68	   112.12	VCC3V3
-    27.68	   433.12	R5
-    27.68	   448.47	10KButton_Up
-    27.68	   484.30	D
-    27.68	   618.51	1uF
-    27.68	   755.98	R38
-    25.82	   671.78	AGNDAGNDAGND
-    24.20	    87.69	R7
-    24.20	   101.42	10K
-    24.20	   726.21	AGND
-    24.20	   782.50	GND
-    20.71	   755.98	0R
-    19.09	   511.28	GND
-    17.46	    45.13	ESP_USB_NR72
-    17.46	    79.09	22R
-    17.46	    99.56	GP19
-    17.23	   458.48	WdCd(w9 37J VÊ}
-    13.98	    45.13	ESP_USB_PR70
-    13.98	    79.09	22R
-    13.98	    99.56	GP20
-    13.98	   610.60	AGND
-     3.76	    72.34	1
-     3.76	   206.09	2
-     3.76	   340.08	3
-     3.76	   474.06	4
-     3.76	   608.04	5
-     3.76	   742.03	6
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-overview-2026-09-01.html b/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-overview-2026-09-01.html
deleted file mode 100644
index 2952d3c..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-overview-2026-09-01.html
+++ /dev/null
@@ -1,59 +0,0 @@
-<!doctype html><html lang=en dir=ltr class="docs-wrapper plugin-docs plugin-id-default docs-version-current docs-doc-page docs-doc-id-ESP32/ESP32-S3/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-Overview" data-has-hydrated=false><head><meta charset=UTF-8><meta name=generator content="Docusaurus v3.10.2"><title data-rh=true>ESP32-S3-ePaper-3.97 | WaveShare Documentation Platform</title><meta data-rh=true name=viewport content="width=device-width, initial-scale=1.0"/><meta data-rh=true name=twitter:card content=summary_large_image /><meta data-rh=true property=og:url content=https://docs.waveshare.com/ESP32-S3-ePaper-3.97 /><meta data-rh=true property=og:locale content=en /><meta data-rh=true property=og:locale:alternate content=zh_Hans /><meta data-rh=true name=docusaurus_locale content=en /><meta data-rh=true name=docsearch:language content=en /><meta data-rh=true name=docusaurus_version content=current /><meta data-rh=true name=docusaurus_tag content=docs-default-current /><meta data-rh=true name=docsearch:version content=current /><meta data-rh=true name=docsearch:docusaurus_tag content=docs-default-current /><meta data-rh=true property=og:title content="ESP32-S3-ePaper-3.97 | WaveShare Documentation Platform"/><meta data-rh=true name=description content="This product is a high-performance, highly integrated microcontroller development board designed by Waveshare. It features the ESP32-S3 microcontroller, support"/><meta data-rh=true property=og:description content="This product is a high-performance, highly integrated microcontroller development board designed by Waveshare. It features the ESP32-S3 microcontroller, support"/><meta data-rh=true property=og:image content=https://www.waveshare.net/photo/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-1.jpg /><meta data-rh=true name=twitter:image content=https://www.waveshare.net/photo/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-1.jpg /><link data-rh=true rel=icon href=/img/favicon.ico /><link data-rh=true rel=canonical href=https://docs.waveshare.com/ESP32-S3-ePaper-3.97 /><link data-rh=true rel=alternate href=https://docs.waveshare.com/ESP32-S3-ePaper-3.97 hreflang=en /><link data-rh=true rel=alternate href=https://docs.waveshare.net/ESP32-S3-ePaper-3.97 hreflang=zh-Hans /><link data-rh=true rel=alternate href=https://docs.waveshare.com/ESP32-S3-ePaper-3.97 hreflang=x-default /><link data-rh=true rel=preconnect href=https://HY4GVNM7LI-dsn.algolia.net crossorigin=anonymous /><script data-rh=true type=application/ld+json>{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","item":"https://docs.waveshare.com/ESP32-S3-ePaper-3.97","name":"ESP32-S3-ePaper-3.97","position":1}]}</script><link rel=preconnect href=https://www.google-analytics.com><link rel=preconnect href=https://www.googletagmanager.com><script async src="https://www.googletagmanager.com/gtag/js?id=G-TKD5QQV5MW"></script><script>function gtag(){dataLayer.push(arguments)}window.dataLayer=window.dataLayer||[],gtag("js",new Date),gtag("config","G-TKD5QQV5MW",{})</script><link rel=search type=application/opensearchdescription+xml title="WaveShare Documentation Platform" href=/opensearch.xml><script>window.__COPY_PAGE_BUTTON_OPTIONS__={siteUrl:"https://docs.waveshare.com",customStyles:{},enabledActions:["copy","view","chatgpt","claude","gemini","deepseek"],generateMarkdownRoutes:!1,placement:"auto",mcpServer:null,labels:{chatgpt:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."},claude:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."},gemini:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."},deepseek:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."}},id:"default"}</script><meta property=og:site_name content=WaveShare><script type=application/ld+json>{"@context":"https://schema.org","@type":"WebSite","name":"WaveShare","url":"https://docs.waveshare.com/"}</script><script src=/js/custom.js async></script><link rel=stylesheet href=/assets/css/styles.b8794211.css /><script src=/assets/js/runtime~main.e01613ff.js defer></script><script src=/assets/js/main.5c051813.js defer></script></head><body><svg style="display: none;"><defs>
-<symbol id=theme-svg-external-link viewBox="0 0 24 24"><path fill=currentColor d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"/></symbol>
-</defs></svg>
-<script>!function(){var t=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return window.localStorage.getItem("theme-820")}catch(t){}}();document.documentElement.setAttribute("data-theme",t||"light"),document.documentElement.setAttribute("data-theme-choice",t||"light")}(),function(){try{for(var[t,e]of new URLSearchParams(window.location.search).entries())if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.setAttribute(a,e)}}catch(t){}}()</script><div id=__docusaurus><link rel=preload as=image href=/img/ws-wiki-logo-green.png /><div role=region aria-label="Skip to main content"><a class=skipToContent_fXgn href=#__docusaurus_skipToContent_fallback>Skip to main content</a></div><nav aria-label=Main class="theme-layout-navbar navbar navbar--fixed-top"><div class=navbar__inner><div class="theme-layout-navbar-left navbar__items"><button aria-label="Toggle navigation bar" aria-expanded=false class="navbar__toggle clean-btn" type=button><svg width=30 height=30 viewBox="0 0 30 30" aria-hidden=true><path stroke=currentColor stroke-linecap=round stroke-miterlimit=10 stroke-width=2 d="M4 7h22M4 15h22M4 23h22"/></svg></button><a class=navbar__brand href=/support><div class=navbar__logo><img src=/img/ws-wiki-logo-green.png alt="Waveshare Logo" class="themedComponent_mlkZ themedComponent--light_NVdE"/><img src=/img/ws-wiki-logo-green.png alt="Waveshare Logo" class="themedComponent_mlkZ themedComponent--dark_xIcU"/></div><b class="navbar__title text--truncate"></b></a><a class="navbar__item navbar__link" href=/support>All Documents</a><div class="navbar__item dropdown wrapper_tBGh"><a class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-esp32 href=/ESP32-Series-Products-Intro>ESP32</a></div><div class="navbar__item dropdown wrapper_tBGh"><a class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-raspberryPi href=/Raspberry-Pi-Overview>Raspberry Pi</a></div><div class="navbar__item dropdown wrapper_tBGh"><a class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-displays href=/Displays>Displays</a></div><div class="navbar__item dropdown wrapper_tBGh"><a href=# class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-more role=button>More</a></div></div><div class="theme-layout-navbar-right navbar__items navbar__items--right"><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href=# aria-haspopup=true aria-expanded=false role=button class=navbar__link><svg viewBox="0 0 24 24" width=20 height=20 aria-hidden=true class=iconLanguage_nlXk><path fill=currentColor d="M12.87 15.07l-2.54-2.51.03-.03c1.74-1.94 2.98-4.17 3.71-6.53H17V4h-7V2H8v2H1v1.99h11.17C11.5 7.92 10.44 9.75 9 11.35 8.07 10.32 7.3 9.19 6.69 8h-2c.73 1.63 1.73 3.17 2.98 4.56l-5.09 5.02L4 19l5-5 3.11 3.11.76-2.04zM18.5 10h-2L12 22h2l1.12-3h4.75L21 22h2l-4.5-12zm-2.62 7l1.62-4.33L19.12 17h-3.24z"/></svg>English</a><ul class=dropdown__menu><li><a href=/ESP32-S3-ePaper-3.97 target=_self rel="noopener noreferrer" class="dropdown__link dropdown__link--active" lang=en>English</a><li><a href=https://docs.waveshare.net/ESP32-S3-ePaper-3.97 target=_self rel="noopener noreferrer" class=dropdown__link lang=zh-Hans>中文</a></ul></div><a href=https://github.com/waveshareteam target=_blank rel="noopener noreferrer" class="navbar__item navbar__link header-github-link" aria-label="GitHub repository"></a><div class="toggle_vylO colorModeToggle_DEke"><button class="clean-btn toggleButton_gllP toggleButtonDisabled_aARS" type=button disabled title="system mode" aria-label="Switch between dark and light mode (currently system mode)"><svg viewBox="0 0 24 24" width=24 height=24 aria-hidden=true class="toggleIcon_g3eP lightToggleIcon_pyhR"><path fill=currentColor d="M12,9c1.65,0,3,1.35,3,3s-1.35,3-3,3s-3-1.35-3-3S10.35,9,12,9 M12,7c-2.76,0-5,2.24-5,5s2.24,5,5,5s5-2.24,5-5 S14.76,7,12,7L12,7z M2,13l2,0c0.55,0,1-0.45,1-1s-0.45-1-1-1l-2,0c-0.55,0-1,0.45-1,1S1.45,13,2,13z M20,13l2,0c0.55,0,1-0.45,1-1 s-0.45-1-1-1l-2,0c-0.55,0-1,0.45-1,1S19.45,13,20,13z M11,2v2c0,0.55,0.45,1,1,1s1-0.45,1-1V2c0-0.55-0.45-1-1-1S11,1.45,11,2z M11,20v2c0,0.55,0.45,1,1,1s1-0.45,1-1v-2c0-0.55-0.45-1-1-1C11.45,19,11,19.45,11,20z M5.99,4.58c-0.39-0.39-1.03-0.39-1.41,0 c-0.39,0.39-0.39,1.03,0,1.41l1.06,1.06c0.39,0.39,1.03,0.39,1.41,0s0.39-1.03,0-1.41L5.99,4.58z M18.36,16.95 c-0.39-0.39-1.03-0.39-1.41,0c-0.39,0.39-0.39,1.03,0,1.41l1.06,1.06c0.39,0.39,1.03,0.39,1.41,0c0.39-0.39,0.39-1.03,0-1.41 L18.36,16.95z M19.42,5.99c0.39-0.39,0.39-1.03,0-1.41c-0.39-0.39-1.03-0.39-1.41,0l-1.06,1.06c-0.39,0.39-0.39,1.03,0,1.41 s1.03,0.39,1.41,0L19.42,5.99z M7.05,18.36c0.39-0.39,0.39-1.03,0-1.41c-0.39-0.39-1.03-0.39-1.41,0l-1.06,1.06 c-0.39,0.39-0.39,1.03,0,1.41s1.03,0.39,1.41,0L7.05,18.36z"/></svg><svg viewBox="0 0 24 24" width=24 height=24 aria-hidden=true class="toggleIcon_g3eP darkToggleIcon_wfgR"><path fill=currentColor d="M9.37,5.51C9.19,6.15,9.1,6.82,9.1,7.5c0,4.08,3.32,7.4,7.4,7.4c0.68,0,1.35-0.09,1.99-0.27C17.45,17.19,14.93,19,12,19 c-3.86,0-7-3.14-7-7C5,9.07,6.81,6.55,9.37,5.51z M12,3c-4.97,0-9,4.03-9,9s4.03,9,9,9s9-4.03,9-9c0-0.46-0.04-0.92-0.1-1.36 c-0.98,1.37-2.58,2.26-4.4,2.26c-2.98,0-5.4-2.42-5.4-5.4c0-1.81,0.89-3.42,2.26-4.4C12.92,3.04,12.46,3,12,3L12,3z"/></svg><svg viewBox="0 0 24 24" width=24 height=24 aria-hidden=true class="toggleIcon_g3eP systemToggleIcon_QzmC"><path fill=currentColor d="m12 21c4.971 0 9-4.029 9-9s-4.029-9-9-9-9 4.029-9 9 4.029 9 9 9zm4.95-13.95c1.313 1.313 2.05 3.093 2.05 4.95s-0.738 3.637-2.05 4.95c-1.313 1.313-3.093 2.05-4.95 2.05v-14c1.857 0 3.637 0.737 4.95 2.05z"/></svg></button></div><div class=navbarSearchContainer_Bca1><button type=button class="DocSearch DocSearch-Button" aria-label="Search (Meta+k)" aria-keyshortcuts=Meta+k><span class=DocSearch-Button-Container><svg width=20 height=20 class=DocSearch-Search-Icon viewBox="0 0 24 24" aria-hidden=true><circle cx=11 cy=11 r=8 stroke=currentColor fill=none stroke-width=1.4 /><path d="m21 21-4.3-4.3" stroke=currentColor fill=none stroke-linecap=round stroke-linejoin=round /></svg><span class=DocSearch-Button-Placeholder>Search</span></span><span class=DocSearch-Button-Keys></span></button></div></div></div><div role=presentation class=navbar-sidebar__backdrop></div></nav><div id=__docusaurus_skipToContent_fallback class="theme-layout-main main-wrapper mainWrapper_z2l0"><div class=docsWrapper_hBAB><button aria-label="Scroll back to top" class="clean-btn theme-back-to-top-button backToTopButton_sjWU" type=button></button><div class=docRoot_UBD9><aside class="theme-doc-sidebar-container docSidebarContainer_YfHR"><div class=sidebarViewport_aRkj><div class=sidebar_njMd><nav aria-label="Docs sidebar" class="menu thin-scrollbar menu_SIkG"><ul class="theme-doc-sidebar-menu menu__list"><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-1 menu__list-item sidebar-title"><a class=menu__link href=/ESP32-S3><span class=linkLabel_WmDU>ESP32-S3</span></a><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-AMOLED-1.91><span class=categoryLinkLabel_W154>ESP32-S3-AMOLED-1.91</span></a><button aria-label="Expand sidebar category 'ESP32-S3-AMOLED-1.91'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-AUDIO-Board><span class=categoryLinkLabel_W154>ESP32-S3-AUDIO-Board</span></a><button aria-label="Expand sidebar category 'ESP32-S3-AUDIO-Board'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-CAM-OVxxxx><span class=categoryLinkLabel_W154>ESP32-S3-CAM-OVxxxx</span></a><button aria-label="Expand sidebar category 'ESP32-S3-CAM-OVxxxx'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-DEV-KIT-N8R8><span class=categoryLinkLabel_W154>ESP32-S3-DEV-KIT-N8R8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-DEV-KIT-N8R8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-DualEye-LCD-1.28><span class=categoryLinkLabel_W154>ESP32-S3-DualEye-LCD-1.28</span></a><button aria-label="Expand sidebar category 'ESP32-S3-DualEye-LCD-1.28'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-DualEye-Touch-LCD-1.28><span class=categoryLinkLabel_W154>ESP32-S3-DualEye-Touch-LCD-1.28</span></a><button aria-label="Expand sidebar category 'ESP32-S3-DualEye-Touch-LCD-1.28'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-GEEK><span class=categoryLinkLabel_W154>ESP32-S3-GEEK</span></a><button aria-label="Expand sidebar category 'ESP32-S3-GEEK'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-0.85><span class=categoryLinkLabel_W154>ESP32-S3-LCD-0.85</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-0.85'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-1.9><span class=categoryLinkLabel_W154>ESP32-S3-LCD-1.9</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-1.9'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2.8><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2.8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2.8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2.8B><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2.8B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2.8B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2.8C><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2.8C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2.8C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-Driver-Board><span class=categoryLinkLabel_W154>ESP32-S3-LCD-Driver-Board</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-Driver-Board'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LR1121-XF><span class=categoryLinkLabel_W154>ESP32-S3-LR1121-XF</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LR1121-XF'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Matrix><span class=categoryLinkLabel_W154>ESP32-S3-Matrix</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Matrix'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Pico><span class=categoryLinkLabel_W154>ESP32-S3-Pico</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Pico'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-RGB-Matrix><span class=categoryLinkLabel_W154>ESP32-S3-RGB-Matrix</span></a><button aria-label="Expand sidebar category 'ESP32-S3-RGB-Matrix'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-RLCD-4.2><span class=categoryLinkLabel_W154>ESP32-S3-RLCD-4.2</span></a><button aria-label="Expand sidebar category 'ESP32-S3-RLCD-4.2'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Tiny><span class=categoryLinkLabel_W154>ESP32-S3-Tiny</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Tiny'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.32><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.32</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.32'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.43C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.43C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.43C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.64><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.64</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.64'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.75><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.75</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.75'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.75C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.75C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.75C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.8><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-2.06><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-2.06</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-2.06'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-2.16><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-2.16</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-2.16'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-2.41><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-2.41</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-2.41'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.28><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.28</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.28'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.46><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.46</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.46'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.47><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.47</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.47'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.54><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.54</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.54'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.69><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.69</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.69'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.83><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.83</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.83'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.85><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.85</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.85'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.85B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.85B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.85B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.85C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.85C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.85C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.1><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.1</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.1'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.8><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.8B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.8B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.8B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.8C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.8C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.8C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-3.49><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-3.49</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-3.49'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-3.5><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-3.5</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-3.5'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-3.5B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-3.5B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-3.5B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-4.3><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-4.3</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-4.3'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-4.3B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-4.3B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-4.3B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-4.3C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-4.3C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-4.3C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-5><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-5</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-5'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-7><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-7</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-7'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-7B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-7B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-7B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-7C-BOX><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-7C-BOX</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-7C-BOX'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Zero><span class=categoryLinkLabel_W154>ESP32-S3-Zero</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Zero'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-ePaper-1.54><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-1.54</span></a><button aria-label="Expand sidebar category 'ESP32-S3-ePaper-1.54'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-ePaper-1.54G><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-1.54G</span></a><button aria-label="Expand sidebar category 'ESP32-S3-ePaper-1.54G'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-ePaper-13.3E6><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-13.3E6</span></a><button aria-label="Expand sidebar category 'ESP32-S3-ePaper-13.3E6'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item"><div class="menu__list-item-collapsible menu__list-item-collapsible--active"><a class="categoryLink_byQd menu__link menu__link--sublist menu__link--active" aria-current=page href=/ESP32-S3-ePaper-3.97><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-3.97</span></a><button aria-label="Collapse sidebar category 'ESP32-S3-ePaper-3.97'" aria-expanded=true type=button class="clean-btn menu__caret"></button></div><ul class=menu__list><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/Resources-And-Documents><span class=linkLabel_WmDU>Resources</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/Arduino><span class=linkLabel_WmDU>Working with Arduino</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/ESP-IDF><span class=linkLabel_WmDU>Working with ESP-IDF</span></a><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-2 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" tabindex=0 href=/ESP32-S3-ePaper-3.97/ESP32-AI-Tutorials><span class=categoryLinkLabel_W154>AI Application Tutorial</span></a><button aria-label="Expand sidebar category 'AI Application Tutorial'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/Firmware-Flashing><span class=linkLabel_WmDU>Firmware Flashing and Erasing</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/FAQ><span class=linkLabel_WmDU>FAQ</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/Technical-Support><span class=linkLabel_WmDU>Technical Support</span></a></ul></ul></nav><button type=button title="Collapse sidebar" aria-label="Collapse sidebar" class=collapseSidebarButton_JQG6><svg class=collapseSidebarButtonIcon_Iseg width=13 height=13 viewBox="0 0 14 14" fill=none aria-hidden=true><path d="M6.5 3L3 7l3.5 4M11 3L7.5 7l3.5 4" stroke=currentColor stroke-width=1.5 stroke-linecap=round stroke-linejoin=round /></svg></button></div></div></aside><main class=docMainContainer_TBSr><div class="container padding-top--md padding-bottom--lg"><div id=waveshare_serial_mark style=display:none>ESP32</div><div id=waveshare_model_mark style=display:none>ESP32-S3-ePaper-3.97、ESP32-S3-ePaper-3.97-EN</div><div class=row><div class="col docItemCol_VOVn"><div class=docItemContainer_Djhp><article><nav class="theme-doc-breadcrumbs breadcrumbsContainer_Z_bl" aria-label=Breadcrumbs><ul class=breadcrumbs><li class=breadcrumbs__item><a aria-label="Home page" class=breadcrumbs__link href=/><svg viewBox="0 0 24 24" class=breadcrumbHomeIcon_YNFT><path d="M10 19v-5h4v5c0 .55.45 1 1 1h3c.55 0 1-.45 1-1v-7h1.7c.46 0 .68-.57.33-.87L12.67 3.6c-.38-.34-.96-.34-1.34 0l-8.36 7.53c-.34.3-.13.87.33.87H5v7c0 .55.45 1 1 1h3c.55 0 1-.45 1-1z" fill=currentColor /></svg></a><li class="breadcrumbs__item breadcrumbs__item--active"><span class=breadcrumbs__link>ESP32-S3-ePaper-3.97</span></ul></nav><div class="tocCollapsible_ETCw theme-doc-toc-mobile tocMobile_ITEo"><button type=button class="clean-btn tocCollapsibleButton_TO0P">On this page</button></div><div class=mobileCopyPageButton_e2i6></div><div class="theme-doc-markdown markdown">
-<header><h1>ESP32-S3-ePaper-3.97</h1></header>
-<div style=max-width:450px><p><a href="https://www.waveshare.com/esp32-s3-epaper-3.97.htm?sku=33810" target=_blank rel="noopener noreferrer" class=""><img decoding=async loading=lazy src=https://www.waveshare.net/photo/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-1.jpg alt=esp32S3-ePaper-3.97_MAIN class=img_ev3q /></a></div>
-<p>This product is a high-performance, highly integrated microcontroller development board designed by Waveshare. It features the ESP32-S3 microcontroller, supporting dual-mode Wi-Fi and BLE communication. The board comes with a 3.97inch e-Paper display, which offers extremely low power consumption, is viewable under ambient light, and is suitable for portable devices and long-endurance scenarios. It integrates an RTC real-time clock, an SHTC3 temperature and humidity sensor, a TF card slot, a low-power audio codec chip, and a power management chip. It provides a flexible and reliable development platform for applications such as IoT endpoints, electronic shelf labels, and portable displays.</p>
-<table><thead><tr><th>SKU<th>Product<tbody><tr><td>33552<td>ESP32-S3-ePaper-3.97<tr><td>33810<td>ESP32-S3-ePaper-3.97-EN<tr><td>33811<td>ESP32-S3-ePaper-3.97-Kit</table>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=features>Features<a href=#features class=hash-link aria-label="Direct link to Features" title="Direct link to Features" translate=no>​</a></h2>
-<ul>
-<li class="">Equipped with ESP32-S3R8 high-performance Xtensa 32-bit LX7 dual-core processor, with a clock frequency up to 240MHz</li>
-<li class="">Supports 2.4GHz Wi-Fi (802.11 b/g/n) and Bluetooth 5 (LE) with an onboard antenna.</li>
-<li class="">Built-in 512KB SRAM and 384KB ROM, with stacked 8MB PSRAM and external 16MB Flash</li>
-<li class="">Features a 3.97inch e-paper display with a resolution of 800 × 480, offering high contrast, wide viewing angles, and other characteristics</li>
-<li class="">Onboard audio codec chip supports voice capture and playback, facilitating AI voice interaction applications</li>
-<li class="">Onboard QMI8658 6-axis IMU (3-axis accelerometer and 3-axis gyroscope) enables motion posture detection, step counting, and other functions</li>
-<li class="">Onboard PCF85063 RTC real-time clock and SHTC3 temperature and humidity sensor enable precise RTC time management and environmental monitoring</li>
-<li class="">Onboard TG28 power management chip accepts a 3.7V MX1.25 lithium battery for uninterrupted power supply. A backup battery interface is reserved to ensure RTC functionality continues when the main battery is replaced</li>
-<li class="">The TG28 provides an efficient power management solution, supports outputting multiple configurable voltages, and integrates charging and battery management functions, helping to extend battery life</li>
-<li class="">Utilizes a Type-C interface, improving user convenience and device compatibility</li>
-<li class="">Onboard TF card slot enables storage expansion and fast data transfer, suitable for data logging, media playback, and other scenarios, simplifying circuit design</li>
-<li class="">Onboard rotary button, along with side BOOT and PWR buttons, supports customizable key functions for more flexible development and use</li>
-</ul>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=onboard-resources>Onboard Resources<a href=#onboard-resources class=hash-link aria-label="Direct link to Onboard Resources" title="Direct link to Onboard Resources" translate=no>​</a></h2>
-<div style=max-width:600px><p><img decoding=async loading=lazy src=/assets/images/ESP32-S3-ePaper3.97-details-intro-47c6d645fb8704b42d4fef9cb0e7b857.webp width=960 height=636 class=img_ev3q /></div>
-<ol>
-<li class=""><strong>ESP32-S3-WROOM-1-N16R8</strong> Wi-Fi and Bluetooth SoC, up to 240MHz operating frequency, stacked with 16MB Flash and 8MB PSRAM</li>
-<li class=""><strong>SHTC3 Temperature and Humidity Sensor</strong> Provides ambient temperature and humidity measurement, enabling environmental monitoring function</li>
-<li class=""><strong>PCF85063</strong> RTC clock chip, supporting time-keeping functionality</li>
-<li class=""><strong>Rotary Button</strong> Supports customizable button functions in three directions</li>
-<li class=""><strong>PWR Key</strong> Can be used with programs to control all power functions when powered by a lithium battery</li>
-<li class=""><strong>BOOT Button</strong> Press and hold the BOOT button to power on again to enter download mode</li>
-<li class=""><strong>NS4150B</strong> Audio power amplifier chip</li>
-<li class=""><strong>ES8311</strong> Low-power audio codec chip</li>
-<li class=""><strong>QMI8658</strong> 6-axis IMU includes a 3-axis gyroscope and a 3-axis accelerometer</li>
-<li class=""><strong>MX1.25 Speaker Header</strong></li>
-<li class=""><strong>MX1.25 RTC Backup Battery Header</strong> Used to power the RTC when no battery is connected to the lithium battery interface</li>
-<li class=""><strong>MX1.25 Lithium Battery Header</strong> MX1.25 2PIN connector for connecting a 3.7V lithium battery, supports charging and discharging</li>
-<li class=""><strong>3.97inch e-Paper Display Interface</strong></li>
-<li class=""><strong>TG28</strong> Highly integrated power management chip</li>
-<li class=""><strong>Microphone</strong></li>
-<li class=""><strong>Type-C Interface</strong> Used for program flashing and log printing</li>
-<li class="">**TF Card Slot ** Supports FAT32-formatted TF card for data expansion</li>
-</ol>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=interfaces>Interfaces<a href=#interfaces class=hash-link aria-label="Direct link to Interfaces" title="Direct link to Interfaces" translate=no>​</a></h2>
-<div style=max-width:800px><p><img decoding=async loading=lazy src=/assets/images/ESP32-S3-ePaper-3.97_port-8d43d07f417f4f8f7c63b9dac33008d3.webp width=1339 height=817 class=img_ev3q /></div>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=dimensions>Dimensions<a href=#dimensions class=hash-link aria-label="Direct link to Dimensions" title="Direct link to Dimensions" translate=no>​</a></h2>
-<div style=max-width:600px><p><img decoding=async loading=lazy src="data:image/webp;base64,UklGRvolAABXRUJQVlA4IO4lAADwAgGdASrAAxQCPm00lkmkIqKiINJ5YIANiWlu3L9eD2l4u9s5CEOBJadfzvvHr/nY6/xM6DkQbAaqb4RNRCX5qxOOtrQn/tvX9/sPS86RPPVf6LUgPRJ87m+mfpn+J/rP4teF/+B/Jz0L8t3m32Q+OXx68ofUX+x9Ff5j9nvuX91/cf/DfPb+X/xvi/8T/638p/gI9X/338ueIw2LzC/W75v/oP8P+4X+K9M3+f/Lv3K+uP+M9wD+V/0L/Vf3b92fib/aePT9n/6fsC/zL+zf7L/Q/lp8b/+d/m/yd9x/57/kf/H/mPgK/lX9X/43+E/ez/T///6yfYN+7vsp/uH//xA+WeLfcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvcF7gvaLVB/PSPURYsWLFixYsWLFixYB3TIRdXgHTwJVxLgX5FQTDKB7mAhFwVVT3JgjHeurDRo/BGqLryNVRwwYMGDBgwYMGC/gdcJgyf/Ow/LPFvuC9v12NkaI7R+Y3W3hWNLjJBygk720gOsovJYPnaHCapEsEL2erWl4ChIa7hWF9wCdPSV9JJK7pGgKc4mfGv2hbMaZOQ2mVi0G5xjdOwXuC9wXt/Glt9wXuC9wXuC9wXuC9wXuCrPUkZx7wRfNG4qCfijjVrhHRLPoHbaIxzgP2KR9scytaPD8s8W+4LxjLV8+4L3Be4L3Be4LwjPBL3/ktRZysfXX21vIoFpM/8dVJFToFo7pVD/52H5Z4t9wXtBBvPJuko4TLdi5AIs1y6kvh+xGvmPZYro8VP/kOdzW4k5PJViLsmc6A0MG8c2UixpNFoG78V5C4UmItApPjYz7U33OHTbSVaueQNehUNz73XqM2B7rKB64jHrYaswvr3i33Be4L2jSBBNcg0JCzsCFWJJZWzGQ2C5k73mQp3kd7/3teRXQuqqWnukmZnVbF6ei80V9i7inb8x/BvTbMUhRVnWC3i5Gdz7gvcF7gqci8E2udCqRTSy+XNtnC+Q0bKjt9wYgOXf/p7AGYIvWk7nle8tmnxuKIcWeLfb+NJ2KazF4VG3GFXxq0mYVG06l+deQV6QPIqxeqsWeLfcGEAtLSoYmnalkUQ4s8W+07LBIv7t3PthRDYHQrRuxsFGg+4xQyV8WeLph23Whedh+WeLfadlkaKpjdMYxb8EPiCJP9zXVZOG3AcV/DWD60HakOy9C9wXuC9p2WRpx/KFeLD0FH8iZwBmo7R/Ow/LPDD2k9gINsDVEs8W+4LxjJ5aNlBQJ2SJRQNGOSz4uQRm8Bibj6l3/zsPy0djInkz3brQvOw/LPFvtOyw1C9TwiEwsozFOJLCVeErkSbl3/zsPyzxrmHWN+qoL/1DS2+4L3Be38aTTaoPdqOizQAxZ4t9w2su/+dh+WeLfcAIvjD7x3tKNOUlkMtXz7gvcFPji3i/RmYSVM6SD6LIrEFTGDaVg4r8fcu/+do4XuC9wXuC9wYE5j38MGAsUMkmZ4Se3fhXsPyzxbNOXiPNAN0n7BO6iVr92wICxkD1lUb4LyaZAfBW1pXOj52H5Z4t9wXuCt2zsPy0egH2w7AMpzNXiND6rl+S4f1k2RFhcmYLfgQL8wyfPx9ihQqktHDpYJUSzxb7fyyUds1CilSwmDtghWa/Ow/LPFvuCtGyzxoWJIyLGPmXcWwIddgMerHb7gvcF7TssjSPdIo/+diTGLfcF5InL/aaZFIm4kNyaznCBPOSzxb7gvb+NJkeo9NMDp8NHazIo9E+4L3Be4K0SPuC99jiqjL3+Hd7DS2+4L3Be38aS0+ILW8cdNximRRDizxb7grds7D8s8AX3dgjbYhLMcbD8s8W+4KttgAXGDKGLZXJFEOLPFvuC9v7hyRxkIlQgEXxocZyACiHFni32/jS8TvHYq8s8W+4L3Be4LyCM9C9xbTJHqBZ4t9wXuCrbWkal4y95Ys8W+4L3Be4L3BeSJ2Gmjo7S+h9y7/52H48autEttYpkPCvPuC9wXuC9wXuC9wXvYPx0EcPehfW1XDKIQ/LPFvt+OK9SfSTM/+HhTkS/d05nJf3Qs3szXxOO8EzFv5BDqvnECwW+M4xexF/Gpr0fzsPyzxb4jPu6zuAmXaUPWiwUfc4zoL0td8+WOd73WoGo83Jx8N03PyCEguLl322LFixYsWLFip8z0HHZsWLF2z8+gKn7OZIcO/5R4c77ACiHFni33Be0GFDI7IslClj8mXyfyn9/z/mcOzvOrp5Cjk92iJzRTSl4AyTfsBi6+PFfkzoDFmp38ZDVHKcKkZYxJw3y4++sdF7oYfkaRaascutkveWxZjiTq3h0cZGvvyUHQkwu7dSK2FJnsU/gz6msgM/kh5AASk5Dizxb7gvcGIOhiZp7nmzAS8qUB84V69TKnH3FkOHUnzAZcONOlSKBce7mQfjxQGFJzR+fcF7gvcF7foyUWnzbGqJI/+xFYsWLFixYsWLFeRWmCit7ifqVOYrEmNBrA9XVWLQl9kWzCeT1FpuhHq5NYyjWR0bDQQs6TCxYsWLFixYsWLDj5r4Xbcx0lkRIl36nIEVb6xrEOUSMLYH8Y+SdN/GxeBUa3OnoQrMwTumrcvv7B+/TgW0OLPFvuC9wXuC9wXuC8KGUWM/50ge3eNfnYflni9Ipj4myRIFUnMS/Pwi33Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3Be4L3BeAAAP7/liAAAAAAAAAAAuOeotklk5zWF6Hyox2cgQQn8K6SBAX4Xho5TnlJzHws00dpBsmWmzYxDwQpHTFhgKMtUXegKXnwg6icv7ETgLX/Y145R0I2HZYrqq7BQLZxupllAXvgGbx1Cz14pVH9JPtnp9TmXzp0Xd1Qwsq7Cs7IaEs/IgzmSsUKb+1MeCA4FFQY1XOWvbEGn12Oz53K+/rba6Vls5ZA2uoKEUE86HlYn/zLgPjtdddDJStQc3irBZ/lUAg7Ejj2GZwegPLZVWHdXOSpV6onw2d38zyuvUvu4Wvbsq0cBXmxTQz/sPTaw36Kkm6fhxWABJIc4ISw9t/h9MuFkaXgPCO1sgLzupiACGsxqXea15vRrqZUrA2OujL/b/k/CjrKe8pUnRrCODYIDTV3g3ehs8If5OMmLyGZzUVLrRQkWAnJzqTKyxDs3Ay09+1II8PIIHUVZHeYI+hI7W1ZVtZriCfsq/Rsg/VXeG80hknLfniUq0gve+iew1ChONC2kAC7tz0dP0qU8cxklLBEgfZVTAA4X8a3r+eWL2h4J8qtVyum9IqAVbWv5oQtjU5LubQJHzC3pQbQW4PMTh3BwRrYuqx/9eY2hUJPmK7imPPLwGuNZ5uD/AS8836+RAhRfgEi8ApmeX/f1WAF2DxfLU/YHbIVvLyvp43Av8xmyDyU8qppMNROX8gdposX0xFY2rl0boqe93kA6uitOn/rCAPGOenk42GyqAXHrQq+u2qHmIlB1LEf2O5WnovGd8uS0YOjXX/OrGeoas7jPGH1DfTqy04VBAp6IQ29265RZNErsgzfs0vWhcrjZo4v9nOjMW9R3ahWwHh9gXRj/bQRYL+g+buU9cfpxYeX+RzjPF3905/uoAYAhqufBuuweCxZkmn5h6O//k2iwJChrCDGDD9BaNpnh6UJe7P/h/BdBZ9sHgHMEeyMOsEii4SU59uDRHC70UGWLpYC6vKjV956wDwPHWa4V3exX7rC6dLhXq4w8HkREvHUn5istim8tdreIcCQU2AztsBfw1wQlunA0V/LMln/D/RL53s9FHR0+f/VpT667MjaZqJbV8NaaFmv0QFr5RK1hMunfJDvFrcRxFePJi1Gi530eDPgDFacDS8kzniq9SK2556ZsbeRjXCo5FbotOY5lLDrZXVTRuv9PtOiZFTpaoUCHDxDdxr7eHyj+MWiTH78PT9wLFBlK8bOLXQqUc6jY7+uYYVVbQhrmf1c06odsqYj+OJ5yXPvz421sbpVbPMiJUTBgAAxcKTOl91tKLBIdyq4m/NOzJnQXpGPawynSIDfs51l9rKoolZG611iVSELMVs4w8zNhGtXIYednO1j8Vd1xfa7+2eMwweXAyfA8wUbxtn95BN+rjna7oZZ7SI+XNC/nOIa8fiAJQMyxtI4Q628vhEDMz23QH+N4AXbmANzmUQTiMf1gqmlQBhlNhjdmFRsc3pOieiGFaY7px2FDXPWFXcB2z5vFQCCgAPC6z/nqFHJsqD6b6FlfYdp7CF8CaBLARJ2TFewwHnvYNsOlCYhRr8z/OuOQ/SPxNTdybvHxDI+hbIbdTDq2pTQ+2oVt+n9K+ivz9x1XtWtvCC2EunduucQliri+sTZCcolhypEjj5o/GbUoMifJ5mBKeXMODKx/J3XScAAAg4S8rGYh5ZY75SlvNnATLKjEDpBPtgAijo/REY77Lnp7F0y4G6zdgUqRYJyA4+MMukr8Tx1ACAk3OcGy7alaK7WSP7ltX434DLgrItDSq7kRifcZCPVObnEADZAdKIbvemXf6G6BSM7+iC8D4RfmlC0rN0X/9H2IVFYHC5/C4AZjJujw2skTYxuRpuoobPUkXOtPjCT7P/8rqQdJigpE6s84wrOHwhch6gihNboNLnwmtm8yNTPcoLhshDmvP4uwv/ZY1eXb6RzzEt5LR+Om1rjStrhjRmkDvo4GZTG78BhweBdUhGi2270ixm0d1hvtio80BpPzKNy4ECIqv5/goRdr4TKECN4BY9lGxLr/++pgR+0jtHsKv6QaH38l/hzAIQYCtR03qJh/ZV3yMCgZYt5ksstpAZORbOJL78zByF+zfHzvfYMxt1ydvaPi+3VcaPGww1nEAri0YZZ1CGKn5fhA+X9QPtll04SeacIeR5WEBYPBoEt3u/9amnNhBDAjG7rB+0EWyQROfsMIq64m8HKcia1lWjCMIG6EvMR5y4eVMcQsgSE+uQR+i11doADdXbayAPJ0ogDYkEx5EFLzFQIxGgIjerw8OEnjJzU2Ns5V8wzjgvRzhBDHKnj/yFyX6IHv9DpNeNC5wydlC+EFSCMkB48hlsx+IlSQGK4iNlvB1bD9X8Hq/mPMTHjo/fF55LJe3AEaGWLtOILthQsivtUG8tknpcmRIVf4nYJqGEQZkUvCCdetR5d/mAgvbf5yocaIm73mRu2UMkuVctjxb5776PPuGuw+ZVaPTsDKv1QoqBNZ3SJCtti7r3MWOiWUYpvlP33ghVyu3wg33laR9G5ajBUqL+XC6V4Djg5/vcsO98Wc9GlWErzH4SuYUYCMrujC/fSbcZ9xev/KLuqzfTAP7SymL1xAgIB9rxQDGkzUR/f9KP28Oq13H/CEJLh3OjT+KEGdkd1DCnDDGaPqNVMcwomcB8C9voME8gNPJD/uBSJabSiB37lIHCcjS3CXWx8u4Fw7IWun7KvQa89FHEl+4ltnHtHvmV3ZrNoX0n3J5Wle+tAfcJ63GTf2ZTlBESNPyocZUxQXiW7yZRU+fXghmnG3tgGPSXPTp0VpOwb4ah1WDpqE+h/3eVYf+y7PmQTBz8/RPHQN4+vuCvkouZaZgCQbn54CysStMiLsHEu3Bk/0JoqJU56Z61wXshhS6+b9KgtQRMQ5i0ejpE05am5EeIOvrCUTbXx3vERl01fN3lxlV95IYwA7rix4nyeeuWEvtDMB7cweQODb9L4veeLat+n6Fb9eg8AAKbaQFyN4rC/ZnMsOTYEDKcSKdpYfn+o0OoZcNa6KxIvP/7IpkQYg4NMdOGJRvcEIu3IquixttYzLyAsj042hef+E7QqXqIeO59yEvHsOelG3qKYILCJ1nvjkYUUqTaiVpa4X96AE5t4tpGEBc07qbElDcGkzaYn82YfAlde53YPmGIyNteFucidVfWzT2QMdxIF7k5JDEgd996xKE1kZE0eOOt/rqhcfZaClMDH8+Ge7rDL9J41W2z+AVARR2o7zPW8AjofrKu9+FPPyA+n2NjgniQq/uT6dwoC56bkENts8zrEhTLaeAK2bC0+/2xx3+oxbJwhxPPnY/ockq/HCJtUbjUp8nC2122XxHSnJEnzjjPTB3V3BFjsAtuvPXDQTO//EuoNQqLSABnW/guWHegFrvooS0K4ABNQybwGAU+r3Xn6vEcDdKpbaiy0QhVlndOrPjoILGDyzsFLTLQ/uQM+LtvOLmSTWUM/dfDrAJnP/KbcvocbwylhfLPLZUVVYyOonubd2KOHZ9smZ/u8MqmdcmfTQvHND+tcc7CUDOCeaTH90LMmnrC+6cYNuWuiDBuhbo210npTmG51IfUxj4ee2BEhxXNADSmSboAAAZT183j0+aURqPRO3hcC+9RC03Z1HTjCLy1+WsEdgD/4ReQwb8GoxwAUNjXybO3ID+C+XQpznQlx6ePGp0DDuhsBfjy7KEhH11CMnUKWol7M8WG54wt6MzMw42EY7xjgxMmLL6SjnqmlZrVe1DHl3jOpAOTgSxu7crThBKNQ6aSvuJLmJbVrqgtEuDVsYXCc8TPbs0XgS0frojtOGJC77dRrmdV922MYQcnWpWFQaLgKwWFuqeLgH+xqyq6QFVQ5JpElr21dw/bUBVLBdECG/DI0Ps6iQBgkOSVRw1vHdcB/ltLyliTU2DedyYYCurAK5irc/ijb2vmf//n/e6M4gqwUbaFlElDLij2CsykMAEn11uPy2jUqge+0DTtNqwbHNg5o2XDow6zUQnBDCE3sOIbYFhpvRus0snbXbtTWOpgCmlnKBVCJJWPc4dupLhjc5UZHVmUCjlQfsE+4TPxGfIorGdDQQGT5LkafoBbrMjSifL5yoNBfHU3bBZ2fo8IDSu+QSKJfO1l2/fgaEwV7JGc8O0lNoV2OCqZt2n12B9spiwexy7wG5ZtNhqOl1QJGv80ZgBnGJih+5G96CfrOs+0YZiJgLpP2ydxTu2OzdEE5ua3WaXi20HDFq2wAAHuI+Kv996nqv/SF1ugQofdZftCaoWjCp9cEXEFFxwLlvP4jwxYXWzSXo5yA+hgg43KGhvxMzoUtYAZOl0/WZuL4yly3k1UiRN+30pNg3M78KTnrUg+XNledBuXRbkCroDEJ+fnQXAyZ/3jt3uGlLg951ITgGwbb3yntw36mWVgSJ2gEaQCZKoyK2vKVYv/3u2C4a1UVbfyYLnS+l32PoyBDbGRDW65+6FztpAYZwzvGPBZ49E8AW82w/eKE7lRTQOQBs4teFaFWEurvLyOFvMmMKFEkkSJ+J56keVR9sT8KH+4o19v0rBcRgI/Q0k+7bLP7iquOY9W42S8eCCkeUawMGBPV5fuxStVcB9VmTqK8C5qceVbV6pfTEF7cgABLYOZOQez9eqTGTcMcABsTS3yFV9cSIh6xzQKCUr1hiZHyDWnxz/V9yKBjneHBI/oiRnv8D1Iqwlr/vGoKez/SvwDpVoSwpJKeYHMa1MulINyMDchI8ysmOcuVa1Ph4hJ7Lh7FjXWuwDo6Q5kli1IpLloo2rKU4ZnAe38OC98SkKiE7YI7MVY1Fsbxk5eEI+eWbKWSp4QvGtmP6/88VYU8+U3VR5OyxF2oY7/8MGMljxOSJutTXoX8d+TvstKPg4+FmWewh8ZjNAepLrosrB23oolMyhmdyGMiiqs9o/61MQ1C5broa4qjHLk3CbYV1p+VHG981/QUhH9/Ocw8599eHwkIG3z+Ii+yO/tefd9LKN/4XOMXfWErjb7MickxmHI3474UMNp/obxpndMm/27DqeBgAM5svK3Iuhvv8SHgCBW81jFTjdKEraOJlAhxg1WCqPON0C9dmuyLmqLP3oUw4LawntRRQagSQB6o/3CXzcFWqWbyyMvyUNQkrnGNTH7Ebop48Ugrm6knBRy1qdibeBSQ6J/AAV7eoB3NUojnAGoX5cbX4JlFmLqyPiEXSaRLcMIR7Db30zgJnLtSpI9mUb+g7XnTg7q72tAGqM3Gfm0u6UWyxKNnB4apdwxMOgSF0XPGonCSoT+dck6AAd2S3v5uukBRsLq7PfUFqQVY9qyaTPyX9bfnukX5CtyP0gjCERuS4KnRygqDNTf97zqtbRz0rtKIZglKdmRy0WInVjRxyTDhN7hNmapNMGNfyZ972MvDVIwVJpmJyAwMrFM10ZPFhiBVCG45ulaUmLFJkBzQ9WewOJK6rdJ/h0ygtTdRU1kKRQxxPixS9zEDmVwSYEIortQYz5RiK6wjgZlsvxnwn2vttqM5gMgDeL8/rXMli3BY6tFGZDlh8A8WMln9PqE2liQ8b8hCz7p4mps/PaXyh0RiNZa+tY93o9RcyzWOXPNX2K42i1ygm2/jtDKJhkyx6aoqmQSBtvTEI+4TZLz8rVZTv7kyOE3G4JpRFTggE/SA5W8xBxWMngudviDJx4lXcl6Aw2hwlTbnrHHNmuzCBGG9xBUXwZI8PVYnJt7h60KHiv+inlsMN95qSCh1MFhkOzTUVUQe5B3EjOxQaYZEWZf8kIIMWKV5Zpsf4m9GBtvprg6sCDlA/tplyY1BIOtTsUSvoO31rBqauQ8Nfyu9nbfAAEK4O2+z+a9qRfgS82ggIsTh6uTgmrucpi9hY/kXyggT7gBBcJDFo6fGXWu8rar5vr3TEMC5m885XJ/7FKPcDlO2zbpBNgF4gajn7VoxKNjhq/YcU2HJXWm/x3Nss0UzO4TKP42p4AmZCKfyRww2mAOQbwCVU2Cnl8X79b9soM6Aiy61taIiuwYDXdhopWhMAB1+yKuy7qTD6ZSVFZoCGO7c3OjYJAVUDiwB4/bkTd1USBm7P4OgzIiACHouNfayAB/qbgWJWMy8lFrSXtgAQvMlz7kDS1IPvnzUvhdn4SJc9Bjy5U1zokmRgEiWkApxKjPOUxE+gpdvg7kOWKD0Je0+2utkT0e+tMqhh+q8B8v7lEEVeD8ZX9Cxl5FlzDDtXbY6k+TM7SABLNQ4h4/mKrMfPeChMi7cojKtzrH7NfmK7GTf/qwoRauoxkMjE2njyS8B6Hbw19mWPfiGrESqQqtaLrewARdWSlmTzc7W5fsNq/cTJ3Fv1S57pxxRwqS6AxEZdDEbdwiL+SS/YC10jPD/vN33NsQArzft1nFoC0vHkp6v0k/toRQdexAytwAe/vSIAGOghuGkBsooMBjYRnUHXLaAPmIXstoIJXcoxUToRkAJCB+HO8O/viR39f9gAABRtzp9k/myspqRypv8S72EjGJCMHe/yd8v40w6p6iG6Xb7iOXgIVDb53DA1uRxMABlvOEJauwNVJ932KPKkACy2fBCbbQ+CLm3RzdRBtfu4amUtc6eFwiMtSABEU6Q3GKbcew51L+AAhYJfBZKwgrBeCtBjvnhsGiTvRosLhUBFMyXIgDcDICroG37g9u/gMmpuyKqAsYYfzRBW+nkocnJcBknhjVYTDIVbkgEHFbd+Zsoaipecz+imsnJ8Xa9pdKpDB8dnqPcIKDueHf0MaNkrk/8an7f2NWC1XlYkpm3neNBTpWF3/14NvyZVl1QAWX42vEv62sVPrH34XoE/+kH6zcbEOVaQu6B/qptTXMeIiBmoPh3p2IqIiAz0PrOcEffsThLtArsMoABNIE7yMr+40dy27vnG1u851uXyUfLolxWJsUDGhCjuEdk73WuXC0by+5irgaDfWa/Ezw9Kfco1ka0fOLgT2arwh32NJyhSEVKwTRVYubBeieAR7FNXX4n2ubs9PGzExkN1nYkdKtIprRQc4d00VLUk5V/jZ25dNMTuWWx5AmADn91FiLezQ1gutMoMI7LNGZlZWTAEU6v/YcL06v9hIVaJI3HMkkO5n1Z1JvIdR21IPpUQuEhV/idaiXdst24ub4CWT+TpaKeNVVXkiXu7HZFhXxSPcPoa2A0j1DREjEksPiQpf6ZpGxBM+T9xU9yTtzMn04Gj5LvJLZtmEvBFusRXNaxwUeB3IamDRgRCyo4wd3FvDxUb6LZZRY0CcWyme7mzhOCH11YHEiQZa3/GFiD4zzqMwKH4c0KkPvauCiFhSrNqJEUnBk6FSXfwB9C0ivhNAIlsDObk0NdCGuVEEBUVIvsF7n0ib2D63ogummn+VIsx12xNnfsmUT5DJOcwRHn/1Dm+NMlf/LmFf+538FLfcoWmS9SHYSBb8bJABTM6CKYutdHYwNm+xYt1nlKjRn07qNLHcAF9gh/yn1xr65YhGfzWZmN7x7nySfVlQ39fJ4UV0mvNGu2NfAy+cj+uxo+k0S4wYaLeek3wMCNjRk4IPAtXfvxVZHFukK/F2RAxryRCiXpxSFOpBIc8NAKy55rl+EvQcC5XQn/gTT7JCtcZQQnsIGPwyRNW8vTknRxM6UZQf2T8Mt7sqQDda5lhBu5c+3FWfznHgbUAiww19TDMDhNrN4voLN7TpMzegH8DQ3gyOE8vgHInM+z99WqmHvpgHMjg+YbIqk/KPWrqpqWMRFE/EHkx3AERC8uBGM5xd1dmJAP7xJBGgEfhNWMDQBjzpZcl3uyzuUy42Oiqb/XnA+jdAPFi/5TiwhNckUC9PMBwDCVZKpMamr/exfwgcJy56kTnvLcVDjrOSdPZXvVr2Jhr1OwwJKZqtfv8KAXCltbxJba5K8EmKPuOvOoyIjX3cvUFC0brW2PYdQ/zbBqEg9L6IiiUnoEtESF/yBCZkXoL2nSe3Qybd1SPvsCrU15jUCpBe79clynV2WJ0U4gbNKghq32T7D1/VchU6qipClSx2fV9Z2yAFALpX34maeqRpzZljFeM4RkZS7sfKVckEFpn9yYNo8cPk4pQCVTuWo0lr+TPMEUgsNwJnFnPrXt07vpiRioAkP5Y/kPZ44z1baykAy8FLVgFUoX83jLrLkAWFTSddjdfi7x4qXdZepMO83lejX5zon/nBQwzxBlj+I8FW/gUvoU/TSmrM99u4beBqr7XHYxGkslQGiS0+vwgQ3J0biHbsIVWVAYeS+LyUpHWkV+MIKCRPUaaJdk9GJm9IDqf2IRcZBRbkA9KAw8mYtWFYZR941DJkZ7xGHMyk2Rquq0B83ktzflwFYmjrrRrVY//l327TGqiR27BPsfY6tChFFWbc3sdoQAFDndLRaKFwmpDn682YNhs2xHIezYF9lfEqLfHfgxJTCSk75dPo0u14+9lkVuYoH9/QosKVO9gsJo4OFS0c/lPB4j0OlHGC9p68OQkDrP+IXcm1nVy/qn17oF0f6haw5Z5+xVyKe3RfFXhDtGMBg91VvCxkXmyMI8Wrz4Uc88JCHZJi0qw2tLltvYEKXhfvFTnaqLJTRRzXAb4tgo8AYPHUQmjLINV5CiIIbQ3FIQbS+GTcjZmMbIBgNjh0nw4GcfsDnmOlGjHjOSpQwz1vc/EuVdu8NinQLrEPYP3EB2Y9BmWtr8EWS7AeAN8bsY9rTug1dVPuY5AAPUAAAAAANa+y3wSy6WPIqoXZuubur+IYOqn9twZrxbCENVCwo/8XfbJTn/HooWCCOsBXIxxKq+kpD/r4qetgLccFu9R1R5376qhBPG42g59EAo35klY9BZcGA4AAAAAAHZfAA00yHKoxR7lDD48/YgeDVRPrnGiNl2WcLNmJllc6xseDAfB6vdlJ1EYdXV6e/Ers9TC7A8VX8zOuNyqXaGeBQD5DeAG7xmmX1uByAel5/irt9sbWHwpTy61lC9PSrifINPAQP1qL9gsY082MANlPbECxX/pyNmUmY7RgeB5trUwUC8zWApCaulJuHXwwKbwpi8L8zixqxyHDywtz1wfJ8rUH0iTEkbCrA+RPspaTmhdA5ZW7yckeumF7HHzs+V99AGN2EXXtYwIsl9485wPAp7GyzjlFdeJrCqz0f2BEQ2cvlz4ZMvVmOOr0ysiB6QdBN0hgX+yCpS88tsdwzT4oFj6q868edUWO0YMcOuAxJCTCXAKjeny1Z9on8Nd1Oq1HF8KG6ohrpj/x/MkLpahvT0hfMvNjxk0tSLulLMElz+ACAjbI1C57KXTfSw8XZO5pEXFfhkSyHRbubuw6C/Gtfad/qEwQbpf6UevKes3qpeiicrrg/UPHPfA9SMDC//CK66sg8ynS+qi+Z/8gXFi5rGAegu71z8dc0XuYgZra7lOhy0njr9g4OkN158o3o2hYlMHmmuxwtVjjh3Mf2CYtNDP7MNF4Qc/Hc9d2SZ96+iKcxVDXlP5YYFYHRGYkJVdmQ71jLIGPjreilFSqKnzhowq0DZd0YxBfN1nlemKD89QGUgnQIRHFPD79OVSNKvnOs9rn6c+kxxCNYxWDjqbddGGuqtl6l6NWJuTMR9DVJfYBnnlcvaX5VH2+hVrb03SyeERbeR2KDk2pR38Y4ZP9UfSjSXy6pQoz5ud/ASJ2x7+/z8aHZFi2S02FOUFA967wzm18c2XBfYsedzVaA1riR2MC4726sl9+Tc4v+YZgJfBWEcx/wWeuCpMaRw1+iypvV6IdROmBscIYsPOlZKcq8J0Zxk1nR6ZoF2U5a+w8DMzg1zkRm65Ohq2T46TlPEsFBEUT3XGJ1hJ+T3HtafMpbmTmHfbQ9ubAPu5yjWwyeZz6b31PWROu8XJberHqbqD5fN4ITwxfHlRipauEs3QXBCiCQhVQUHcXdIBp6/2Epiqxtp15kGcrfgt8pt5RW+MLVeX94LhJEoPfao9MD7V1jZJKpXqBI1mBYkr+xLF8OpERrSAv8ZwQ0md18tMC4yXSvzVhSftzAFanDmX9UoflvUIoEKUJy0DjfSQCtz2zH3Xr3tDmAUvvtNw7FvwB9lhstxynU40JaL4pYzi7ERDLvrizv5AIn8Xd03TEdWKfpyQFkCCu41DWe5wkK8jJNJ2oAAAaOwZWNE0dk2uegk6ahK3XYsK8zTxG4ZjZmYhmoVhIaTkAAbNeAJjm6j2WYNhjRwUU2AAAAAAAAAAAAAAA==" width=960 height=532 class=img_ev3q /></div>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=development-methods>Development Methods<a href=#development-methods class=hash-link aria-label="Direct link to Development Methods" title="Direct link to Development Methods" translate=no>​</a></h2>
-<p>The ESP32-S3-ePaper-3.97 supports two development frameworks: Arduino IDE and ESP-IDF, offering flexibility for developers. You can choose the appropriate development tool based on project requirements and personal preference.</p>
-<p>Arduino generally offers a gentler learning curve and may be more approachable for beginners and hobbyists. ESP-IDF provides advanced tooling and finer control over system behavior, making it better suited to complex projects and applications with demanding performance requirements.</p>
-<ul>
-<li class="">
-<p><strong>Arduino IDE</strong> is a convenient, flexible, and easy-to-use open-source electronics prototyping platform. It requires minimal foundational knowledge, allowing for rapid development after a short learning period. Arduino has a vast global community that provides a wealth of open-source code, project examples, tutorials, and rich libraries that encapsulate complex functionalities, enabling developers to implement various features quickly. You can refer to the <strong><a class="" href=/ESP32-S3-ePaper-3.97/Arduino>Working with Arduino</a></strong> to complete the initial setup, and the tutorial also provides related demos for reference.</p>
-</li>
-<li class="">
-<p><strong>ESP-IDF</strong> (Espressif IoT Development Framework) is a professional development framework released by Espressif for its ESP series chips. It is developed based on the C language, including a compiler, debugger, and flashing tool, etc. It supports development via command line or an Integrated Development Environment (such as Visual Studio Code with the Espressif IDF plugin), which provides features like code navigation, project management, and debugging, etc. We recommend using VS Code for development. For the specific configuration process, please refer to the <strong><a class="" href=/ESP32-S3-ePaper-3.97/ESP-IDF>Working with ESP-IDF</a></strong>. The tutorial also provides relevant demos for reference.</p>
-</li>
-</ul></div><div class=feedback-button-container><a href=https://docs.google.com/forms/d/e/1FAIpQLSfayJEZ5J-dp-3Wq_dkWsVRhNuQ6C79_GNV62mYuFW8Mj6U8Q/viewform target=_blank rel="noopener noreferrer" class=feedback-button><svg class=feedback-button__icon xmlns=http://www.w3.org/2000/svg width=16 height=16 viewBox="0 0 24 24" fill=none stroke=currentColor stroke-width=2 stroke-linecap=round stroke-linejoin=round aria-hidden=true><path d="M21 15a2 2 0 0 1-2 2H7l-4 4V5a2 2 0 0 1 2-2h14a2 2 0 0 1 2 2z"/></svg>Give Feedback</a></div></article><nav class="docusaurus-mt-lg pagination-nav" aria-label="Docs pages"><a class="pagination-nav__link pagination-nav__link--prev" href=/ESP32-S3-ePaper-13.3E67/Technical-Support><div class=pagination-nav__sublabel>Previous</div><div class=pagination-nav__label>Support</div></a><a class="pagination-nav__link pagination-nav__link--next" href=/ESP32-S3-ePaper-3.97/Resources-And-Documents><div class=pagination-nav__sublabel>Next</div><div class=pagination-nav__label>Resources</div></a></nav></div></div><div class="col col--3"><div class=copyPageButtonWrapper_ElN1></div><div class="tableOfContents_bqdL thin-scrollbar theme-doc-toc-desktop"><ul class="table-of-contents table-of-contents__left-border"><li><a href=#features class="table-of-contents__link toc-highlight">Features</a><li><a href=#onboard-resources class="table-of-contents__link toc-highlight">Onboard Resources</a><li><a href=#interfaces class="table-of-contents__link toc-highlight">Interfaces</a><li><a href=#dimensions class="table-of-contents__link toc-highlight">Dimensions</a><li><a href=#development-methods class="table-of-contents__link toc-highlight">Development Methods</a></ul></div></div></div></div></main></div></div></div><footer class="theme-layout-footer footer footer--dark"><div class="container container-fluid"><div class=footer-main><div class=footer-brand><a class=footerLogoLink_BH7S href=/support><img src=/img/ws-wiki-logo-green.png alt=Waveshare class="footer__logo themedComponent_mlkZ themedComponent--light_NVdE" height=26 /><img src=/img/ws-wiki-logo-green.png alt=Waveshare class="footer__logo themedComponent_mlkZ themedComponent--dark_xIcU" height=26 /></a><p class=footer-brand__desc>Waveshare product documentation<br/>Tutorials, resources and example code for boards, modules and displays</div><div class=footer-main__links><div class="row footer__links"><div class="theme-layout-footer-column col footer__col"><div class=footer__title>Resources</div><ul class="footer__items clean-list"><li class=footer__item><a class=footer__link-item href=/ESP32-Tutorials-Intro>Tutorials</a><li class=footer__item><a href=https://github.com/waveshareteam target=_blank rel="noopener noreferrer" class=footer__link-item>GitHub<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div><div class="theme-layout-footer-column col footer__col"><div class=footer__title>Information</div><ul class="footer__items clean-list"><li class=footer__item><a href=https://www.youtube.com/channel/UCV_48_r0rplaYB-VqxXB04g target=_blank rel="noopener noreferrer" class=footer__link-item>Youtube<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div><div class="theme-layout-footer-column col footer__col"><div class=footer__title>Where to Buy</div><ul class="footer__items clean-list"><li class=footer__item><a href=https://www.waveshare.com target=_blank rel="noopener noreferrer" class=footer__link-item>Official Store<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div><div class="theme-layout-footer-column col footer__col"><div class=footer__title>About Waveshare</div><ul class="footer__items clean-list"><li class=footer__item><a href=https://www.waveshare.com/about_us target=_blank rel="noopener noreferrer" class=footer__link-item>About Us<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a><li class=footer__item><a href=https://www.waveshare.com/contact_us target=_blank rel="noopener noreferrer" class=footer__link-item>Contact Us<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div></div></div></div><div class="footer__bottom footer-bottom"><div class=footer__copyright>Copyright © 2026 Waveshare</div></div></div></footer></div><!-- Cloudflare Pages Analytics --><script defer src='https://static.cloudflareinsights.com/beacon.min.js' data-cf-beacon='{"token": "55f4d0b7699543be89f12f763c9d92ca"}'></script><!-- Cloudflare Pages Analytics --></body>
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-resources-2026-09-01.html b/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-resources-2026-09-01.html
deleted file mode 100644
index 059514d..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/docs-resources-2026-09-01.html
+++ /dev/null
@@ -1,77 +0,0 @@
-<!doctype html><html lang=en dir=ltr class="docs-wrapper plugin-docs plugin-id-default docs-version-current docs-doc-page docs-doc-id-ESP32/ESP32-S3/ESP32-S3-ePaper-3.97/Resources-And-Documents" data-has-hydrated=false><head><meta charset=UTF-8><meta name=generator content="Docusaurus v3.10.2"><title data-rh=true>Resources | WaveShare Documentation Platform</title><meta data-rh=true name=viewport content="width=device-width, initial-scale=1.0"/><meta data-rh=true name=twitter:card content=summary_large_image /><meta data-rh=true property=og:image content=https://docs.waveshare.com/img/ws-logo-green.png /><meta data-rh=true name=twitter:image content=https://docs.waveshare.com/img/ws-logo-green.png /><meta data-rh=true property=og:url content=https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents /><meta data-rh=true property=og:locale content=en /><meta data-rh=true property=og:locale:alternate content=zh_Hans /><meta data-rh=true name=docusaurus_locale content=en /><meta data-rh=true name=docsearch:language content=en /><meta data-rh=true name=docusaurus_version content=current /><meta data-rh=true name=docusaurus_tag content=docs-default-current /><meta data-rh=true name=docsearch:version content=current /><meta data-rh=true name=docsearch:docusaurus_tag content=docs-default-current /><meta data-rh=true property=og:title content="Resources | WaveShare Documentation Platform"/><meta data-rh=true name=description content="Resources and documents for ESP32-S3-ePaper-3.97, including technical documentation, development resources, and reference materials."/><meta data-rh=true property=og:description content="Resources and documents for ESP32-S3-ePaper-3.97, including technical documentation, development resources, and reference materials."/><link data-rh=true rel=icon href=/img/favicon.ico /><link data-rh=true rel=canonical href=https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents /><link data-rh=true rel=alternate href=https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents hreflang=en /><link data-rh=true rel=alternate href=https://docs.waveshare.net/ESP32-S3-ePaper-3.97/Resources-And-Documents hreflang=zh-Hans /><link data-rh=true rel=alternate href=https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents hreflang=x-default /><link data-rh=true rel=preconnect href=https://HY4GVNM7LI-dsn.algolia.net crossorigin=anonymous /><script data-rh=true type=application/ld+json>{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","item":"https://docs.waveshare.com/ESP32-S3-ePaper-3.97","name":"ESP32-S3-ePaper-3.97","position":1},{"@type":"ListItem","item":"https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents","name":"Resources","position":2}]}</script><link rel=preconnect href=https://www.google-analytics.com><link rel=preconnect href=https://www.googletagmanager.com><script async src="https://www.googletagmanager.com/gtag/js?id=G-TKD5QQV5MW"></script><script>function gtag(){dataLayer.push(arguments)}window.dataLayer=window.dataLayer||[],gtag("js",new Date),gtag("config","G-TKD5QQV5MW",{})</script><link rel=search type=application/opensearchdescription+xml title="WaveShare Documentation Platform" href=/opensearch.xml><script>window.__COPY_PAGE_BUTTON_OPTIONS__={siteUrl:"https://docs.waveshare.com",customStyles:{},enabledActions:["copy","view","chatgpt","claude","gemini","deepseek"],generateMarkdownRoutes:!1,placement:"auto",mcpServer:null,labels:{chatgpt:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."},claude:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."},gemini:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."},deepseek:{prompt:"Please read the following Waveshare documentation page, then answer my questions based on it; if something is not covered by the document, say so instead of guessing. Start with a clear summary and help me understand the key concepts."}},id:"default"}</script><meta property=og:site_name content=WaveShare><script type=application/ld+json>{"@context":"https://schema.org","@type":"WebSite","name":"WaveShare","url":"https://docs.waveshare.com/"}</script><script src=/js/custom.js async></script><link rel=stylesheet href=/assets/css/styles.b8794211.css /><script src=/assets/js/runtime~main.e01613ff.js defer></script><script src=/assets/js/main.5c051813.js defer></script></head><body><svg style="display: none;"><defs>
-<symbol id=theme-svg-external-link viewBox="0 0 24 24"><path fill=currentColor d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"/></symbol>
-</defs></svg>
-<script>!function(){var t=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return window.localStorage.getItem("theme-820")}catch(t){}}();document.documentElement.setAttribute("data-theme",t||"light"),document.documentElement.setAttribute("data-theme-choice",t||"light")}(),function(){try{for(var[t,e]of new URLSearchParams(window.location.search).entries())if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.setAttribute(a,e)}}catch(t){}}()</script><div id=__docusaurus><link rel=preload as=image href=/img/ws-wiki-logo-green.png /><div role=region aria-label="Skip to main content"><a class=skipToContent_fXgn href=#__docusaurus_skipToContent_fallback>Skip to main content</a></div><nav aria-label=Main class="theme-layout-navbar navbar navbar--fixed-top"><div class=navbar__inner><div class="theme-layout-navbar-left navbar__items"><button aria-label="Toggle navigation bar" aria-expanded=false class="navbar__toggle clean-btn" type=button><svg width=30 height=30 viewBox="0 0 30 30" aria-hidden=true><path stroke=currentColor stroke-linecap=round stroke-miterlimit=10 stroke-width=2 d="M4 7h22M4 15h22M4 23h22"/></svg></button><a class=navbar__brand href=/support><div class=navbar__logo><img src=/img/ws-wiki-logo-green.png alt="Waveshare Logo" class="themedComponent_mlkZ themedComponent--light_NVdE"/><img src=/img/ws-wiki-logo-green.png alt="Waveshare Logo" class="themedComponent_mlkZ themedComponent--dark_xIcU"/></div><b class="navbar__title text--truncate"></b></a><a class="navbar__item navbar__link" href=/support>All Documents</a><div class="navbar__item dropdown wrapper_tBGh"><a class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-esp32 href=/ESP32-Series-Products-Intro>ESP32</a></div><div class="navbar__item dropdown wrapper_tBGh"><a class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-raspberryPi href=/Raspberry-Pi-Overview>Raspberry Pi</a></div><div class="navbar__item dropdown wrapper_tBGh"><a class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-displays href=/Displays>Displays</a></div><div class="navbar__item dropdown wrapper_tBGh"><a href=# class=navbar__link aria-haspopup=true aria-expanded=false aria-controls=mega-menu-more role=button>More</a></div></div><div class="theme-layout-navbar-right navbar__items navbar__items--right"><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href=# aria-haspopup=true aria-expanded=false role=button class=navbar__link><svg viewBox="0 0 24 24" width=20 height=20 aria-hidden=true class=iconLanguage_nlXk><path fill=currentColor d="M12.87 15.07l-2.54-2.51.03-.03c1.74-1.94 2.98-4.17 3.71-6.53H17V4h-7V2H8v2H1v1.99h11.17C11.5 7.92 10.44 9.75 9 11.35 8.07 10.32 7.3 9.19 6.69 8h-2c.73 1.63 1.73 3.17 2.98 4.56l-5.09 5.02L4 19l5-5 3.11 3.11.76-2.04zM18.5 10h-2L12 22h2l1.12-3h4.75L21 22h2l-4.5-12zm-2.62 7l1.62-4.33L19.12 17h-3.24z"/></svg>English</a><ul class=dropdown__menu><li><a href=/ESP32-S3-ePaper-3.97/Resources-And-Documents target=_self rel="noopener noreferrer" class="dropdown__link dropdown__link--active" lang=en>English</a><li><a href=https://docs.waveshare.net/ESP32-S3-ePaper-3.97/Resources-And-Documents target=_self rel="noopener noreferrer" class=dropdown__link lang=zh-Hans>中文</a></ul></div><a href=https://github.com/waveshareteam target=_blank rel="noopener noreferrer" class="navbar__item navbar__link header-github-link" aria-label="GitHub repository"></a><div class="toggle_vylO colorModeToggle_DEke"><button class="clean-btn toggleButton_gllP toggleButtonDisabled_aARS" type=button disabled title="system mode" aria-label="Switch between dark and light mode (currently system mode)"><svg viewBox="0 0 24 24" width=24 height=24 aria-hidden=true class="toggleIcon_g3eP lightToggleIcon_pyhR"><path fill=currentColor d="M12,9c1.65,0,3,1.35,3,3s-1.35,3-3,3s-3-1.35-3-3S10.35,9,12,9 M12,7c-2.76,0-5,2.24-5,5s2.24,5,5,5s5-2.24,5-5 S14.76,7,12,7L12,7z M2,13l2,0c0.55,0,1-0.45,1-1s-0.45-1-1-1l-2,0c-0.55,0-1,0.45-1,1S1.45,13,2,13z M20,13l2,0c0.55,0,1-0.45,1-1 s-0.45-1-1-1l-2,0c-0.55,0-1,0.45-1,1S19.45,13,20,13z M11,2v2c0,0.55,0.45,1,1,1s1-0.45,1-1V2c0-0.55-0.45-1-1-1S11,1.45,11,2z M11,20v2c0,0.55,0.45,1,1,1s1-0.45,1-1v-2c0-0.55-0.45-1-1-1C11.45,19,11,19.45,11,20z M5.99,4.58c-0.39-0.39-1.03-0.39-1.41,0 c-0.39,0.39-0.39,1.03,0,1.41l1.06,1.06c0.39,0.39,1.03,0.39,1.41,0s0.39-1.03,0-1.41L5.99,4.58z M18.36,16.95 c-0.39-0.39-1.03-0.39-1.41,0c-0.39,0.39-0.39,1.03,0,1.41l1.06,1.06c0.39,0.39,1.03,0.39,1.41,0c0.39-0.39,0.39-1.03,0-1.41 L18.36,16.95z M19.42,5.99c0.39-0.39,0.39-1.03,0-1.41c-0.39-0.39-1.03-0.39-1.41,0l-1.06,1.06c-0.39,0.39-0.39,1.03,0,1.41 s1.03,0.39,1.41,0L19.42,5.99z M7.05,18.36c0.39-0.39,0.39-1.03,0-1.41c-0.39-0.39-1.03-0.39-1.41,0l-1.06,1.06 c-0.39,0.39-0.39,1.03,0,1.41s1.03,0.39,1.41,0L7.05,18.36z"/></svg><svg viewBox="0 0 24 24" width=24 height=24 aria-hidden=true class="toggleIcon_g3eP darkToggleIcon_wfgR"><path fill=currentColor d="M9.37,5.51C9.19,6.15,9.1,6.82,9.1,7.5c0,4.08,3.32,7.4,7.4,7.4c0.68,0,1.35-0.09,1.99-0.27C17.45,17.19,14.93,19,12,19 c-3.86,0-7-3.14-7-7C5,9.07,6.81,6.55,9.37,5.51z M12,3c-4.97,0-9,4.03-9,9s4.03,9,9,9s9-4.03,9-9c0-0.46-0.04-0.92-0.1-1.36 c-0.98,1.37-2.58,2.26-4.4,2.26c-2.98,0-5.4-2.42-5.4-5.4c0-1.81,0.89-3.42,2.26-4.4C12.92,3.04,12.46,3,12,3L12,3z"/></svg><svg viewBox="0 0 24 24" width=24 height=24 aria-hidden=true class="toggleIcon_g3eP systemToggleIcon_QzmC"><path fill=currentColor d="m12 21c4.971 0 9-4.029 9-9s-4.029-9-9-9-9 4.029-9 9 4.029 9 9 9zm4.95-13.95c1.313 1.313 2.05 3.093 2.05 4.95s-0.738 3.637-2.05 4.95c-1.313 1.313-3.093 2.05-4.95 2.05v-14c1.857 0 3.637 0.737 4.95 2.05z"/></svg></button></div><div class=navbarSearchContainer_Bca1><button type=button class="DocSearch DocSearch-Button" aria-label="Search (Meta+k)" aria-keyshortcuts=Meta+k><span class=DocSearch-Button-Container><svg width=20 height=20 class=DocSearch-Search-Icon viewBox="0 0 24 24" aria-hidden=true><circle cx=11 cy=11 r=8 stroke=currentColor fill=none stroke-width=1.4 /><path d="m21 21-4.3-4.3" stroke=currentColor fill=none stroke-linecap=round stroke-linejoin=round /></svg><span class=DocSearch-Button-Placeholder>Search</span></span><span class=DocSearch-Button-Keys></span></button></div></div></div><div role=presentation class=navbar-sidebar__backdrop></div></nav><div id=__docusaurus_skipToContent_fallback class="theme-layout-main main-wrapper mainWrapper_z2l0"><div class=docsWrapper_hBAB><button aria-label="Scroll back to top" class="clean-btn theme-back-to-top-button backToTopButton_sjWU" type=button></button><div class=docRoot_UBD9><aside class="theme-doc-sidebar-container docSidebarContainer_YfHR"><div class=sidebarViewport_aRkj><div class=sidebar_njMd><nav aria-label="Docs sidebar" class="menu thin-scrollbar menu_SIkG"><ul class="theme-doc-sidebar-menu menu__list"><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-1 menu__list-item sidebar-title"><a class=menu__link href=/ESP32-S3><span class=linkLabel_WmDU>ESP32-S3</span></a><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-AMOLED-1.91><span class=categoryLinkLabel_W154>ESP32-S3-AMOLED-1.91</span></a><button aria-label="Expand sidebar category 'ESP32-S3-AMOLED-1.91'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-AUDIO-Board><span class=categoryLinkLabel_W154>ESP32-S3-AUDIO-Board</span></a><button aria-label="Expand sidebar category 'ESP32-S3-AUDIO-Board'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-CAM-OVxxxx><span class=categoryLinkLabel_W154>ESP32-S3-CAM-OVxxxx</span></a><button aria-label="Expand sidebar category 'ESP32-S3-CAM-OVxxxx'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-DEV-KIT-N8R8><span class=categoryLinkLabel_W154>ESP32-S3-DEV-KIT-N8R8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-DEV-KIT-N8R8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-DualEye-LCD-1.28><span class=categoryLinkLabel_W154>ESP32-S3-DualEye-LCD-1.28</span></a><button aria-label="Expand sidebar category 'ESP32-S3-DualEye-LCD-1.28'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-DualEye-Touch-LCD-1.28><span class=categoryLinkLabel_W154>ESP32-S3-DualEye-Touch-LCD-1.28</span></a><button aria-label="Expand sidebar category 'ESP32-S3-DualEye-Touch-LCD-1.28'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-GEEK><span class=categoryLinkLabel_W154>ESP32-S3-GEEK</span></a><button aria-label="Expand sidebar category 'ESP32-S3-GEEK'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-0.85><span class=categoryLinkLabel_W154>ESP32-S3-LCD-0.85</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-0.85'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-1.9><span class=categoryLinkLabel_W154>ESP32-S3-LCD-1.9</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-1.9'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2.8><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2.8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2.8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2.8B><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2.8B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2.8B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-2.8C><span class=categoryLinkLabel_W154>ESP32-S3-LCD-2.8C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-2.8C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LCD-Driver-Board><span class=categoryLinkLabel_W154>ESP32-S3-LCD-Driver-Board</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LCD-Driver-Board'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-LR1121-XF><span class=categoryLinkLabel_W154>ESP32-S3-LR1121-XF</span></a><button aria-label="Expand sidebar category 'ESP32-S3-LR1121-XF'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Matrix><span class=categoryLinkLabel_W154>ESP32-S3-Matrix</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Matrix'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Pico><span class=categoryLinkLabel_W154>ESP32-S3-Pico</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Pico'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-RGB-Matrix><span class=categoryLinkLabel_W154>ESP32-S3-RGB-Matrix</span></a><button aria-label="Expand sidebar category 'ESP32-S3-RGB-Matrix'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-RLCD-4.2><span class=categoryLinkLabel_W154>ESP32-S3-RLCD-4.2</span></a><button aria-label="Expand sidebar category 'ESP32-S3-RLCD-4.2'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Tiny><span class=categoryLinkLabel_W154>ESP32-S3-Tiny</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Tiny'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.32><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.32</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.32'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.43C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.43C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.43C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.64><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.64</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.64'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.75><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.75</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.75'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.75C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.75C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.75C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-1.8><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-1.8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-1.8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-2.06><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-2.06</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-2.06'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-2.16><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-2.16</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-2.16'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-AMOLED-2.41><span class=categoryLinkLabel_W154>ESP32-S3-Touch-AMOLED-2.41</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-AMOLED-2.41'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.28><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.28</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.28'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.46><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.46</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.46'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.47><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.47</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.47'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.54><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.54</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.54'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.69><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.69</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.69'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.83><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.83</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.83'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.85><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.85</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.85'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.85B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.85B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.85B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-1.85C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-1.85C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-1.85C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.1><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.1</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.1'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.8><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.8</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.8'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.8B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.8B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.8B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-2.8C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-2.8C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-2.8C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-3.49><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-3.49</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-3.49'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-3.5><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-3.5</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-3.5'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-3.5B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-3.5B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-3.5B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-4.3><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-4.3</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-4.3'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-4.3B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-4.3B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-4.3B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-4.3C><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-4.3C</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-4.3C'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-5><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-5</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-5'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-7><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-7</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-7'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-7B><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-7B</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-7B'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Touch-LCD-7C-BOX><span class=categoryLinkLabel_W154>ESP32-S3-Touch-LCD-7C-BOX</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Touch-LCD-7C-BOX'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-Zero><span class=categoryLinkLabel_W154>ESP32-S3-Zero</span></a><button aria-label="Expand sidebar category 'ESP32-S3-Zero'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-ePaper-1.54><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-1.54</span></a><button aria-label="Expand sidebar category 'ESP32-S3-ePaper-1.54'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-ePaper-1.54G><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-1.54G</span></a><button aria-label="Expand sidebar category 'ESP32-S3-ePaper-1.54G'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" href=/ESP32-S3-ePaper-13.3E6><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-13.3E6</span></a><button aria-label="Expand sidebar category 'ESP32-S3-ePaper-13.3E6'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-1 menu__list-item"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist menu__link--active" href=/ESP32-S3-ePaper-3.97><span class=categoryLinkLabel_W154>ESP32-S3-ePaper-3.97</span></a><button aria-label="Collapse sidebar category 'ESP32-S3-ePaper-3.97'" aria-expanded=true type=button class="clean-btn menu__caret"></button></div><ul class=menu__list><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class="menu__link menu__link--active" aria-current=page tabindex=0 href=/ESP32-S3-ePaper-3.97/Resources-And-Documents><span class=linkLabel_WmDU>Resources</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/Arduino><span class=linkLabel_WmDU>Working with Arduino</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/ESP-IDF><span class=linkLabel_WmDU>Working with ESP-IDF</span></a><li class="theme-doc-sidebar-item-category theme-doc-sidebar-item-category-level-2 menu__list-item menu__list-item--collapsed"><div class=menu__list-item-collapsible><a class="categoryLink_byQd menu__link menu__link--sublist" tabindex=0 href=/ESP32-S3-ePaper-3.97/ESP32-AI-Tutorials><span class=categoryLinkLabel_W154>AI Application Tutorial</span></a><button aria-label="Expand sidebar category 'AI Application Tutorial'" aria-expanded=false type=button class="clean-btn menu__caret"></button></div><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/Firmware-Flashing><span class=linkLabel_WmDU>Firmware Flashing and Erasing</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/FAQ><span class=linkLabel_WmDU>FAQ</span></a><li class="theme-doc-sidebar-item-link theme-doc-sidebar-item-link-level-2 menu__list-item"><a class=menu__link tabindex=0 href=/ESP32-S3-ePaper-3.97/Technical-Support><span class=linkLabel_WmDU>Technical Support</span></a></ul></ul></nav><button type=button title="Collapse sidebar" aria-label="Collapse sidebar" class=collapseSidebarButton_JQG6><svg class=collapseSidebarButtonIcon_Iseg width=13 height=13 viewBox="0 0 14 14" fill=none aria-hidden=true><path d="M6.5 3L3 7l3.5 4M11 3L7.5 7l3.5 4" stroke=currentColor stroke-width=1.5 stroke-linecap=round stroke-linejoin=round /></svg></button></div></div></aside><main class=docMainContainer_TBSr><div class="container padding-top--md padding-bottom--lg"><div id=waveshare_serial_mark style=display:none>ESP32</div><div id=waveshare_model_mark style=display:none>ESP32-S3-ePaper-3.97、ESP32-S3-ePaper-3.97-EN</div><div class=row><div class="col docItemCol_VOVn"><div class=docItemContainer_Djhp><article><nav class="theme-doc-breadcrumbs breadcrumbsContainer_Z_bl" aria-label=Breadcrumbs><ul class=breadcrumbs><li class=breadcrumbs__item><a aria-label="Home page" class=breadcrumbs__link href=/><svg viewBox="0 0 24 24" class=breadcrumbHomeIcon_YNFT><path d="M10 19v-5h4v5c0 .55.45 1 1 1h3c.55 0 1-.45 1-1v-7h1.7c.46 0 .68-.57.33-.87L12.67 3.6c-.38-.34-.96-.34-1.34 0l-8.36 7.53c-.34.3-.13.87.33.87H5v7c0 .55.45 1 1 1h3c.55 0 1-.45 1-1z" fill=currentColor /></svg></a><li class=breadcrumbs__item><a class=breadcrumbs__link href=/ESP32-S3-ePaper-3.97><span>ESP32-S3-ePaper-3.97</span></a><li class="breadcrumbs__item breadcrumbs__item--active"><span class=breadcrumbs__link>Resources</span></ul></nav><div class="tocCollapsible_ETCw theme-doc-toc-mobile tocMobile_ITEo"><button type=button class="clean-btn tocCollapsibleButton_TO0P">On this page</button></div><div class=mobileCopyPageButton_e2i6></div><div class="theme-doc-markdown markdown"><header><h1>Resources</h1></header>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=1-hardware-resources><strong>1. Hardware Resources</strong><a href=#1-hardware-resources class=hash-link aria-label="Direct link to 1-hardware-resources" title="Direct link to 1-hardware-resources" translate=no>​</a></h2>
-<p><strong>Development Board Design File</strong></p>
-<ul>
-<li class="">Schematic: <a href=https://files.waveshare.com/wiki/ESP32-S3-ePaper-3.97/ESP32-S3_e-Paper-3.97-schematic.pdf target=_blank rel="noopener noreferrer" class="">ESP32-S3-ePaper-3.97-Schematic.pdf</a></li>
-</ul>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=2-technical-manuals><strong>2. Technical Manuals</strong><a href=#2-technical-manuals class=hash-link aria-label="Direct link to 2-technical-manuals" title="Direct link to 2-technical-manuals" translate=no>​</a></h2>
-<ul>
-<li class="">
-<p><strong>Official ESP32-S3 Chip Manuals</strong></p>
-<ul>
-<li class="">Datasheets:<!-- -->
-<ul>
-<li class=""><a href=https://documentation.espressif.com/esp32-s3_datasheet_cn.pdf target=_blank rel="noopener noreferrer" class="">ESP32-S3 Series Datasheet (Chinese)</a></li>
-<li class=""><a href=https://documentation.espressif.com/esp32-s3_datasheet_en.pdf target=_blank rel="noopener noreferrer" class="">ESP32-S3 Series Datasheet (English)</a></li>
-</ul>
-</li>
-<li class="">Technical Manuals:<!-- -->
-<ul>
-<li class=""><a href=https://documentation.espressif.com/esp32-s3_technical_reference_manual_cn.pdf target=_blank rel="noopener noreferrer" class="">ESP32-S3 Technical Reference Manual (Chinese)</a></li>
-<li class=""><a href=https://documentation.espressif.com/esp32-s3_technical_reference_manual_en.pdf target=_blank rel="noopener noreferrer" class="">ESP32-S3 Technical Reference Manual (English)</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li class="">
-<p><strong>Onboard Component Datasheets</strong></p>
-<ul>
-<li class=""><a href=https://files.waveshare.com/wiki/3.97inch_e-Paper_HAT%2B/3.97inch_e-Paper.pdf target=_blank rel="noopener noreferrer" class="">3.97inch e-Paper Datasheet</a></li>
-<li class=""><a href=https://files.waveshare.com/wiki/common/ES8311.DS.pdf target=_blank rel="noopener noreferrer" class="">ES8311 Datasheet</a></li>
-<li class=""><a href=https://files.waveshare.com/wiki/common/Pcf85063atl1118-NdPQpTGE-loeW7GbZ7.pdf target=_blank rel="noopener noreferrer" class="">PCF85063 Datasheet</a></li>
-<li class=""><a href=https://files.waveshare.com/wiki/common/SHTC3_Datasheet.pdf target=_blank rel="noopener noreferrer" class="">SHTC3 Datasheet</a></li>
-</ul>
-</li>
-</ul>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=Demo><strong>3. Example</strong><a href=#Demo class=hash-link aria-label="Direct link to Demo" title="Direct link to Demo" translate=no>​</a></h2>
-<ul>
-<li class=""><a href=https://github.com/waveshareteam/ESP32-S3-ePaper-3.97 target=_blank rel="noopener noreferrer" class="">ESP32-S3-ePaper-3.97 Example (GitHub)</a></li>
-</ul>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=4-software-tools><strong>4. Software Tools</strong><a href=#4-software-tools class=hash-link aria-label="Direct link to 4-software-tools" title="Direct link to 4-software-tools" translate=no>​</a></h2>
-<ul>
-<li class="">Arduino:<!-- -->
-<ul>
-<li class=""><a href=https://www.arduino.cc/en/software/ target=_blank rel="noopener noreferrer" class="">Arduino IDE Official Download Link</a></li>
-<li class=""><a href=https://docs.espressif.com/projects/arduino-esp32/en/latest/index.html target=_blank rel="noopener noreferrer" class="">ESP32-Arduino Official Documentation</a></li>
-<li class=""><a href=https://drive.google.com/drive/folders/1YhHg8AA_02LFW2OqChk3hbFRV_GVt9Y0 target=_blank rel="noopener noreferrer" class="">Arduino-ESP32 Offline Component Package</a></li>
-</ul>
-</li>
-<li class="">VScode:<!-- -->
-<ul>
-<li class=""><a href=https://code.visualstudio.com/download target=_blank rel="noopener noreferrer" class="">VScode Official Download Link</a></li>
-</ul>
-</li>
-<li class="">Firmware Flashing Tool:<!-- -->
-<ul>
-<li class=""><a href=https://dl.espressif.com/public/flash_download_tool.zip target=_blank rel="noopener noreferrer" class="">Flash_download_tool</a></li>
-</ul>
-</li>
-</ul>
-<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id=5-community-showcase><strong>5. Community Showcase</strong><a href=#5-community-showcase class=hash-link aria-label="Direct link to 5-community-showcase" title="Direct link to 5-community-showcase" translate=no>​</a></h2>
-<div class="theme-admonition theme-admonition-info admonition_xJq3 alert alert--info"><div class=admonitionHeading_Gvgb><span class=admonitionIcon_Rf37><svg viewBox="0 0 14 16"><path fill-rule=evenodd d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"/></svg></span>info</div><div class=admonitionContent_BuS1><p>Check out these amazing projects created by the community! Please note these are independently maintained by their creators.</div></div>
-<!-- -->
-<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id=aimindseye---rustmix-wave-for-waveshare-esp32-s3-e-paper-397>aimindseye - Rustmix Wave for Waveshare ESP32-S3 E-Paper 3.97<a href=#aimindseye---rustmix-wave-for-waveshare-esp32-s3-e-paper-397 class=hash-link aria-label="Direct link to aimindseye - Rustmix Wave for Waveshare ESP32-S3 E-Paper 3.97" title="Direct link to aimindseye - Rustmix Wave for Waveshare ESP32-S3 E-Paper 3.97" translate=no>​</a></h3>
-<ul>
-<li class="">Reddit: <a href=https://www.reddit.com/r/esp32projects/comments/1tyngwy/rustmix_wave_v100_an_opensource_rust_firmware_for/ target=_blank rel="noopener noreferrer" class="">https://www.reddit.com/r/esp32projects/comments/1tyngwy/rustmix_wave_v100_an_opensource_rust_firmware_for/</a></li>
-<li class="">GitHub: <a href=https://github.com/aimindseye/rustmix-wave target=_blank rel="noopener noreferrer" class="">https://github.com/aimindseye/rustmix-wave</a></li>
-</ul>
-<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id=alxv2016---folloup-sticky>alxv2016 - Folloup Sticky<a href=#alxv2016---folloup-sticky class=hash-link aria-label="Direct link to alxv2016 - Folloup Sticky" title="Direct link to alxv2016 - Folloup Sticky" translate=no>​</a></h3>
-<figure style=max-width:500px;margin:0;text-align:center><p><img decoding=async loading=lazy src="https://makerworld.bblmw.com/makerworld/model/US85341093a75fb3/design/e4e3e3fafa4eee8e.jpeg?x-oss-process=image%2Fresize%2Cw_1000%2Fformat%2Cwebp" alt="Folloup Sticky on ESP32-S3-ePaper-3.97" class=img_ev3q />
-<figcaption>Image source: <a href=https://makerworld.com/en/models/3180226-folloup target=_blank rel="noopener noreferrer" class="">Folloup Sticky</a> by alxv2016</figcaption><p></figure>
-<ul>
-<li class="">MakerWorld: <a href=https://makerworld.com/en/models/3180226-folloup target=_blank rel="noopener noreferrer" class="">https://makerworld.com/en/models/3180226-folloup</a></li>
-<li class="">GitHub: <a href=https://github.com/alxv2016/folloup-sticky/tree/folloup-waveshare target=_blank rel="noopener noreferrer" class="">https://github.com/alxv2016/folloup-sticky/tree/folloup-waveshare</a></li>
-</ul></div><div class=feedback-button-container><a href=https://docs.google.com/forms/d/e/1FAIpQLSfayJEZ5J-dp-3Wq_dkWsVRhNuQ6C79_GNV62mYuFW8Mj6U8Q/viewform target=_blank rel="noopener noreferrer" class=feedback-button><svg class=feedback-button__icon xmlns=http://www.w3.org/2000/svg width=16 height=16 viewBox="0 0 24 24" fill=none stroke=currentColor stroke-width=2 stroke-linecap=round stroke-linejoin=round aria-hidden=true><path d="M21 15a2 2 0 0 1-2 2H7l-4 4V5a2 2 0 0 1 2-2h14a2 2 0 0 1 2 2z"/></svg>Give Feedback</a></div></article><nav class="docusaurus-mt-lg pagination-nav" aria-label="Docs pages"><a class="pagination-nav__link pagination-nav__link--prev" href=/ESP32-S3-ePaper-3.97><div class=pagination-nav__sublabel>Previous</div><div class=pagination-nav__label>ESP32-S3-ePaper-3.97</div></a><a class="pagination-nav__link pagination-nav__link--next" href=/ESP32-S3-ePaper-3.97/Arduino><div class=pagination-nav__sublabel>Next</div><div class=pagination-nav__label>Working with Arduino</div></a></nav></div></div><div class="col col--3"><div class=copyPageButtonWrapper_ElN1></div><div class="tableOfContents_bqdL thin-scrollbar theme-doc-toc-desktop"><ul class="table-of-contents table-of-contents__left-border"><li><a href=#1-hardware-resources class="table-of-contents__link toc-highlight"><strong>1. Hardware Resources</strong></a><li><a href=#2-technical-manuals class="table-of-contents__link toc-highlight"><strong>2. Technical Manuals</strong></a><li><a href=#Demo class="table-of-contents__link toc-highlight"><strong>3. Example</strong></a><li><a href=#4-software-tools class="table-of-contents__link toc-highlight"><strong>4. Software Tools</strong></a><li><a href=#5-community-showcase class="table-of-contents__link toc-highlight"><strong>5. Community Showcase</strong></a><ul><li><a href=#aimindseye---rustmix-wave-for-waveshare-esp32-s3-e-paper-397 class="table-of-contents__link toc-highlight">aimindseye - Rustmix Wave for Waveshare ESP32-S3 E-Paper 3.97</a><li><a href=#alxv2016---folloup-sticky class="table-of-contents__link toc-highlight">alxv2016 - Folloup Sticky</a></ul></ul></div></div></div></div></main></div></div></div><footer class="theme-layout-footer footer footer--dark"><div class="container container-fluid"><div class=footer-main><div class=footer-brand><a class=footerLogoLink_BH7S href=/support><img src=/img/ws-wiki-logo-green.png alt=Waveshare class="footer__logo themedComponent_mlkZ themedComponent--light_NVdE" height=26 /><img src=/img/ws-wiki-logo-green.png alt=Waveshare class="footer__logo themedComponent_mlkZ themedComponent--dark_xIcU" height=26 /></a><p class=footer-brand__desc>Waveshare product documentation<br/>Tutorials, resources and example code for boards, modules and displays</div><div class=footer-main__links><div class="row footer__links"><div class="theme-layout-footer-column col footer__col"><div class=footer__title>Resources</div><ul class="footer__items clean-list"><li class=footer__item><a class=footer__link-item href=/ESP32-Tutorials-Intro>Tutorials</a><li class=footer__item><a href=https://github.com/waveshareteam target=_blank rel="noopener noreferrer" class=footer__link-item>GitHub<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div><div class="theme-layout-footer-column col footer__col"><div class=footer__title>Information</div><ul class="footer__items clean-list"><li class=footer__item><a href=https://www.youtube.com/channel/UCV_48_r0rplaYB-VqxXB04g target=_blank rel="noopener noreferrer" class=footer__link-item>Youtube<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div><div class="theme-layout-footer-column col footer__col"><div class=footer__title>Where to Buy</div><ul class="footer__items clean-list"><li class=footer__item><a href=https://www.waveshare.com target=_blank rel="noopener noreferrer" class=footer__link-item>Official Store<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div><div class="theme-layout-footer-column col footer__col"><div class=footer__title>About Waveshare</div><ul class="footer__items clean-list"><li class=footer__item><a href=https://www.waveshare.com/about_us target=_blank rel="noopener noreferrer" class=footer__link-item>About Us<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a><li class=footer__item><a href=https://www.waveshare.com/contact_us target=_blank rel="noopener noreferrer" class=footer__link-item>Contact Us<svg width=13.5 height=13.5 aria-label="(opens in new tab)" class=iconExternalLink_nPIU><use href=#theme-svg-external-link /></svg></a></ul></div></div></div></div><div class="footer__bottom footer-bottom"><div class=footer__copyright>Copyright © 2026 Waveshare</div></div></div></footer></div><!-- Cloudflare Pages Analytics --><script defer src='https://static.cloudflareinsights.com/beacon.min.js' data-cf-beacon='{"token": "55f4d0b7699543be89f12f763c9d92ca"}'></script><!-- Cloudflare Pages Analytics --></body>
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/storefront-esp32-s3-epaper-3.97-2026-09-01.html b/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/storefront-esp32-s3-epaper-3.97-2026-09-01.html
deleted file mode 100644
index 8cb349e..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/artifacts/source-snapshots/storefront-esp32-s3-epaper-3.97-2026-09-01.html
+++ /dev/null
@@ -1,4945 +0,0 @@
-<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<title>ESP32-S3 3.97inch e-Paper Development Board, 800 × 480 Resolution, Supports Wi-Fi / BLE 5, And AI Voice Interaction, Onboard Microphone  | ESP32-S3-ePaper-3.97</title>
-<meta name="description" content="ESP32-S3 3.97inch e-Paper Development Board, 800 × 480 Resolution, Supports Wi-Fi / BLE 5, And AI Voice Interaction, Onboard Microphone | ESP32-S3-ePaper-3.97" />
-<meta name="keywords" content="ESP32-S3 3.97inch e-Paper Development Board, 800 × 480 Resolution, Supports Wi-Fi / BLE 5, And AI Voice Interaction, Onboard Microphone | ESP32-S3-ePaper-3.97" />
-<meta name="robots" content="INDEX,FOLLOW" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" />
-
-<link rel="icon" href="https://www.waveshare.com/media/favicon/default/f64.png" type="image/x-icon" />
-<link rel="shortcut icon" href="https://www.waveshare.com/media/favicon/default/f64.png" type="image/x-icon" />
-
-    <link rel="apple-touch-icon-precomposed" href="https://www.waveshare.com/media/eternal/venedor/default/logo_1.png">
-
-    <link rel="apple-touch-icon-precomposed" href="https://www.waveshare.com/media/eternal/venedor/default/logo_2.png">
-
-    <link rel="apple-touch-icon-precomposed" href="https://www.waveshare.com/media/eternal/venedor/default/logo_3.png">
-
-    <link rel="apple-touch-icon-precomposed" href="https://www.waveshare.com/media/eternal/venedor/default/f64.png">
-
-<!--[if lt IE 7]>
-<script type="text/javascript">
-//<![CDATA[
-    var BLANK_URL = 'https://www.waveshare.com/js/blank.html';
-    var BLANK_IMG = 'https://www.waveshare.com/js/spacer.gif';
-//]]>
-</script>
-<![endif]-->
-
-
-<script type="text/javascript" src="https://www.waveshare.com/js/eternal/jquery/jquery-1.8.2.min.js"></script>
-<script type="text/javascript">
-    jQuery.noConflict();
-</script>
-
-
-        <script type="text/javascript" src="https://www.waveshare.com/js/eternal/bootstrap/3.0.0/js/bootstrap.min.js"></script>
-    <link rel="stylesheet" type="text/css" href="https://www.waveshare.com/js/eternal/bootstrap/3.0.0/css/bootstrap.min.css" media="all" />
-    <link rel="stylesheet" type="text/css" href="https://www.waveshare.com/js/eternal/bootstrap/3.0.0/css/bootstrap-theme.min.css" media="all" />
-    
-<link rel="stylesheet" type="text/css" href="https://www.waveshare.com/media/css_secure/293c454901ec3f3a51800ac5672cab3b.css" />
-<link rel="stylesheet" type="text/css" href="https://www.waveshare.com/media/css_secure/4e0af53d946f5c011886e45e1c2eee52.css" media="all" />
-<link rel="stylesheet" type="text/css" href="https://www.waveshare.com/media/css_secure/d5c134ba4492651131b79ba261d4814f.css" media="print" />
-<script type="text/javascript" src="https://www.waveshare.com/media/js/58de2914cf12cfbd3918685d51d1a502.js"></script>
-<link rel="canonical" href="https://www.waveshare.com/esp32-s3-epaper-3.97.htm" />
-<!--[if IE]>
-<link rel="stylesheet" type="text/css" href="https://www.waveshare.com/media/css_secure/5da8afbecd5be32cffdd10a3e7403e32.css" media="all" />
-<![endif]-->
-<!--[if lt IE 7]>
-<script type="text/javascript" src="https://www.waveshare.com/media/js/52ba41bc47fba14dd32dfc47d89ea138.js"></script>
-<![endif]-->
-<!--[if lt IE 9]>
-<script type="text/javascript" src="https://www.waveshare.com/media/js/1bdc4a9c9fcd5a3b693af2890c4d829a.js"></script>
-<![endif]-->
-<!--[if lte IE 7]>
-<link rel="stylesheet" type="text/css" href="https://www.waveshare.com/media/css_secure/de6fa43e4fd0e992d77d9467e7e8ead5.css" media="all" />
-<![endif]-->
-<!--[if lte IE 8]>
-<link rel="stylesheet" type="text/css" href="https://www.waveshare.com/media/css_secure/60b9a421cce7c9738b817c13069f04e2.css" media="all" />
-<![endif]-->
-
-<script type="text/javascript">
-//<![CDATA[
-Mage.Cookies.path     = '/';
-Mage.Cookies.domain   = '.www.waveshare.com';
-//]]>
-</script>
-
-<script type="text/javascript">
-//<![CDATA[
-optionalZipCountries = ["HK","IE","MO","PA"];
-//]]>
-</script>
-<script type="text/javascript">//<![CDATA[
-        var Translator = new Translate([]);
-        //]]></script><!-- Google tag (gtag.js) -->
-<script async src="https://www.googletagmanager.com/gtag/js?id=G-LRBJJHTXKT"></script>
-<script>
-  window.dataLayer = window.dataLayer || [];
-  function gtag(){dataLayer.push(arguments);}
-  gtag('js', new Date());
-
-  gtag('config', 'G-LRBJJHTXKT');
-</script>
-<script>
-document.addEventListener('DOMContentLoaded', function() {
-  const checkoutForm = document.getElementById('onepagecheckout_orderform');
-  if (checkoutForm) {
-    checkoutForm.addEventListener('submit', function() {
-      gtag('event', 'ws_checkout_from_submit', {
-        'success': '1'
-      });
-    });
-  }
-});
-</script>
-    <script type="text/javascript">
-        var VENEDOR_RESPONSIVE = true;
-    </script>
-<script type="text/javascript">
-    var SPAN_CSS = 'col-sm-';
-    var VENEDOR_HEADER_FIXED = 0;
-    var VENEDOR_HEADER_FIXED_LOGO = 0;
-    var VENEDOR_HEADER_OFFSET = 0;
-    var VENEDOR_MENU_PADDING = 12;
-</script>
-
-<script type='text/javascript' src='https://platform-api.sharethis.com/js/sharethis.js#property=65c85865d77abd0019f02dc9&product=inline-share-buttons' async='async'></script>
-<style type="text/css">
-    div#st-cmp-v2 {
-        display: none;
-    }
-</style>
-</head>
-<body class="2columns  catalog-product-view catalog-product-view product-esp32-s3-epaper-3-97 categorypath-product-htm category-product green bv3 bsl">
-
-
-    <div class="notices-container">
-                    <noscript>
-        <div class="global-site-notice noscript">
-            <div class="notice-inner">
-                <p>
-                    <strong>JavaScript seems to be disabled in your browser.</strong><br />
-                    You must have JavaScript enabled in your browser to utilize the functionality of this website.                </p>
-            </div>
-        </div>
-    </noscript>
-    </div>
-    <div class="header-container">
-        <div class="header-top">
-    <div class="container">
-        <div class="row">
-            <div class="col-xs-12">
-                <div class="header-top-inner">
-                    <!--<div class="block block-currency">
-    <div class="block-title">
-        <span>Select Your Currency</span>
-    </div>
-    <div class="block-content dropdown">
-        <a href="#" class="dropdown-toggle" data-toggle="dropdown" data-hover="dropdown" data-delay="1000" data-close-others="false" title="Select Your Currency">
-            <span class="name">US Dollar</span><span class="symbol">$</span>
-        </a>
-        <ul class="dropdown-menu">
-                                                <li><a tabindex="-1" href="https://www.waveshare.com/directory/currency/switch/currency/AUD/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span class="name">Australian Dollar</span><span class="symbol">AU$</span></a></li>
-                                                                <li><a tabindex="-1" href="https://www.waveshare.com/directory/currency/switch/currency/GBP/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span class="name">British Pound Sterling</span><span class="symbol">£</span></a></li>
-                                                                <li><a tabindex="-1" href="https://www.waveshare.com/directory/currency/switch/currency/CAD/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span class="name">Canadian Dollar</span><span class="symbol">CA$</span></a></li>
-                                                                <li><a tabindex="-1" href="https://www.waveshare.com/directory/currency/switch/currency/EUR/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span class="name">Euro</span><span class="symbol">€</span></a></li>
-                                                                <li><a tabindex="-1" href="https://www.waveshare.com/directory/currency/switch/currency/JPY/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span class="name">Japanese Yen</span><span class="symbol">¥</span></a></li>
-                                                                    
-        </ul>
-    </div>
-</div>-->
-<div class="d-flex align-content-center">
-  <div class="btn-group waveshare-block-currency">
-      <button type="button" class="navbar-left dropdown-toggle d-flex align-content-center" data-toggle="dropdown">$<span class="currency-name hidden-xs"> US Dollar</span><span class="caret"></span></button>
-      <ul class="dropdown-menu" role="menu">
-                                          <li><a href="https://www.waveshare.com/directory/currency/switch/currency/AUD/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span>AU$</span><span> Australian Dollar</span></a></li>
-                                                        <li><a href="https://www.waveshare.com/directory/currency/switch/currency/GBP/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span>£</span><span> British Pound Sterling</span></a></li>
-                                                        <li><a href="https://www.waveshare.com/directory/currency/switch/currency/CAD/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span>CA$</span><span> Canadian Dollar</span></a></li>
-                                                        <li><a href="https://www.waveshare.com/directory/currency/switch/currency/EUR/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span>€</span><span> Euro</span></a></li>
-                                                        <li><a href="https://www.waveshare.com/directory/currency/switch/currency/JPY/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0,/"><span>¥</span><span> Japanese Yen</span></a></li>
-                                                      </ul>
-  </div>
-  <div class="toplinks1 d-flex align-content-center"><a class="navbar-texthidden-xs" href="https://service.waveshare.com"><span class="d-flex align-content-center"><i class="icon-waveshare-supp"></i><span class="hidden-xs">SUPPORT</span></span></a></div>
-</div>
-
-<script type="text/javascript">
-//<![CDATA[
-jQuery(function($) {
-    var venedor_currency_timer;
-    
-    function venedor_resize_currency() {
-        var w1 = $('.block-currency .dropdown-toggle').css('width','auto').innerWidth() + 1;
-        var w2 = $('.block-currency .dropdown-menu').css('width','auto').innerWidth() + 1;
-        if (w1 > w2) {
-            $('.block-currency .dropdown-toggle').css('width', w1 + 'px');
-            $('.block-currency .dropdown-menu').css('width', w1 + 'px');
-        } else {
-            $('.block-currency .dropdown-toggle').css('width', w2 + 'px');
-            $('.block-currency .dropdown-menu').css('width', w2 + 'px');
-        }
-        if (venedor_currency_timer) clearTimeout(venedor_currency_timer); 
-    }
-    
-    $(window).resize(function() {
-        clearTimeout(venedor_currency_timer); 
-        venedor_currency_timer = setTimeout(venedor_resize_currency, 100); 
-    });
-    venedor_resize_currency();
-});
-//]]>
-</script>
-<style>
-.toplinks1 a {
-    color: #5b5e63;
-}
-.toplinks1 a {
-    text-decoration: none;
-    line-height: 36px;
-    margin: 0 20px;
-    display: inline-block;
-    white-space: nowrap;
-}
- </style>
-                        
-
-<!--<ul class="toplinks links">
-            
-			            <li class=" last" ><a href="https://www.waveshare.com/onepagecheckout/" title="Checkout" class="top-link-checkout"><i class="icon-checkout"></i><span>Checkout</span></a></li>
-                    
-			            <li  ><a href="https://www.waveshare.com/checkout/cart/" title="My Cart" class="top-link-cart"><i class="icon-mycart"></i><span>My Cart</span></a></li>
-                                                    
-			            <li class="first" ><a href="https://www.waveshare.com/customer/account/" title="My Account" ><i class="icon-myaccount"></i><span>My Account</span></a></li>
-            </ul>-->
-
-
-<ul class="toplinks links d-flex align-content-center">
-                        <li><a href="https://www.waveshare.com/onepagecheckout/" title="Checkout" class="top-link-checkout d-flex align-content-center"><i class="icon-checkout"></i><span class="hidden-xs">Checkout</span></a></li>
-            <li style="opacity: 0.5;">|</li>
-                                <li><a href="https://www.waveshare.com/checkout/cart/" title="My Cart" class="top-link-cart d-flex align-content-center"><i class="icon-mycart"></i><span class="hidden-xs">My Cart</span></a></li>
-            <li style="opacity: 0.5;">|</li>
-                                        <!-- 未登录 -->
-                  <li>
-            <a href="/customer/account/" title="My Account" class="top-link-myaccount d-flex align-content-center"><i class="icon-myaccount"></i><span>Login/Register</span></a>
-          </li>
-        <!-- 登录了 -->
-        </ul>
-
-<script type="text/javascript">
-  // 购物车 + 货币实时数据：通过 AJAX 获取（绕过 fastcgi_cache）
-  (function() {
-    // 页面加载时先隐藏会变化的区域（避免从缓存值跳变到实际值的闪烁）
-    var style = document.createElement('style');
-    style.textContent = '#mini-cart, .toplinks .count, [data-cart-count="mobile"], .waveshare-block-currency .dropdown-toggle { opacity: 0; transition: opacity 0.3s ease; }';
-    document.head.appendChild(style);
-
-    function showDynamicElements() {
-      jQuery('#mini-cart, .toplinks .count, [data-cart-count="mobile"], .waveshare-block-currency .dropdown-toggle').css('opacity', '1');
-    }
-
-    function refreshCart() {
-      jQuery.ajax({
-        url: '/ajaxcart/index/minicart',
-        type: 'GET',
-        dataType: 'json',
-        cache: false,
-        xhrFields: { withCredentials: true },
-        success: function(data) {
-          var n = parseInt(data && data.count, 10) || 0;
-
-          // 1. 更新桌面端 mini-cart 整体 HTML（包括商品列表 + 金额）
-          if (data.html) {
-            var $parent = jQuery('#mini-cart').parent();
-            jQuery('#mini-cart').remove();
-            $parent.prepend(data.html);
-            jQuery('#mini-cart').css('opacity', '0');
-          }
-
-          // 2. 更新手机端购物车 badge
-          if (n >= 1) {
-            jQuery('[data-cart-count="mobile"]').text(n);
-          } else {
-            jQuery('[data-cart-count="mobile"]').text('');
-          }
-
-          // 3. 更新顶部 toplinks 中 "My Cart (x)" 的数字
-          jQuery('.toplinks a[href*="/checkout/cart"]').each(function() {
-            var $link = jQuery(this);
-            var $span = $link.find('span.hidden-xs');
-            if ($span.length) {
-              $span.find('.count').remove();
-              var title = jQuery.trim($span.text());
-              if (n > 0) {
-                $span.html(title + '<span class="count" style="opacity:0;transition:opacity 0.3s ease;">(' + n + ')</span>');
-              } else {
-                $span.text(title);
-              }
-            }
-          });
-
-          // 4. 更新货币切换器按钮显示（根据用户实际 cookie 对应的货币）
-          if (data.currency_symbol && data.currency_name) {
-            var $btn = jQuery('.waveshare-block-currency .dropdown-toggle');
-            if ($btn.length) {
-              // 保留 caret，重建按钮内容
-              $btn.html(data.currency_symbol + '<span class="currency-name hidden-xs"> ' + data.currency_name + '</span><span class="caret"></span>');
-            }
-          }
-
-          // 淡入显示所有动态元素
-          setTimeout(showDynamicElements, 50);
-        },
-        error: function() {
-          // 请求失败时也要显示（保留缓存值，总比一直隐藏好）
-          showDynamicElements();
-        }
-      });
-    }
-    jQuery(document).ready(refreshCart);
-
-    // 暴露全局函数，加购/切换货币后可调用刷新
-    window.refreshCartCount = refreshCart;
-  })();
-</script>                </div>
-            </div>
-        </div>
-    </div>
-</div>
-<div class="header">
-    <div class="container">
-        <div class="header-center">
-            <div class="row">
-                <div class="col-xs-12">
-                    <div class="header-inner d-flex align-content-center">
-                        <h1 class="logo">
-                            <strong>Waveshare</strong>
-                            <a href="https://www.waveshare.com/" title="Waveshare" class="logo"><img src="https://www.waveshare.com/media/eternal/venedor/default/logo.png" alt="Waveshare"></a>
-                        </h1>
-                        <div class="hidden-xs form-search">
-                            <form id="waveshare-search1" class="waveshare-search1 d-flex justify-content-between align-content-center" role="search" action="https://www.waveshare.com/catalogsearch/result/" method="get">                         
-  <div class="input-group-btn">
-      <input type="text" placeholder="Search" class="form-control dropdown-toggle" data-toggle="dropdown" name="q" autocomplete="off"> <!-- value="" -->
-      <ul class="dropdown-menu waveshare-search-list" style="width: 100%;">
-      </ul>
-  </div>
-  <button type="submit" title="Search" class="button">Search</button>
-</form><span class="waveshare_cart_num" style="display:none;"></span>
-
-<script type="text/javascript">
-//<![CDATA[
-jQuery(function($) {
-    var form_mini_timer;
-    var search_input_width = 160;
-    var input_val = "";
-
-    // add by 20240508
-    $('#waveshare-search1 input').unbind('focus').focus(function(){
-      searchKeyUp();
-    })
-    $('#waveshare-search1 input').unbind('keyup').keyup(function(){
-      searchKeyUp();
-    })
-    function searchKeyUp() {
-      input_val1 = $.trim($('#waveshare-search1 input').val());
-      console.log(input_val);
-      if(input_val1=='') {
-        $('#waveshare-search1 .waveshare-search-list').html('<li><a href="/catalogsearch/advanced/"><div><i class="icon-advanced"></i>Advanced Search</div></a></li>')
-      } else {
-        if(input_val1 != input_val) {
-          input_val = input_val1;
-          $.get("/catalogsearch/ajax/suggest/?v=2&q="+input_val, function(data,status){
-            if(status='success') {
-              $('#waveshare-search1 .waveshare-search-list').html(data)
-            }
-          });
-        }
-        // <li><a href="#"><div><i class="icon-search"></i><span>匹配结果</span></div><div>86815</div></a></li>
-      }
-    }
-
-})
-//]]>
-</script>
-                        </div>
-                        <div class="hidden-xs">
-                          
-<!-- waveshare-mini-cart1 -->
-<div id="mini-cart" class="waveshare-mini-cart block-content dropdown">
-  <div class="dropdown-toggle d-flex align-content-center" data-toggle="dropdown" data-hover="dropdown" data-delay="1000" data-close-others="false" title="You have no items in your shopping cart.">
-        <i class="icon-cart2"></i>
-        <span class="cart-items">0 item(s)</span>
-        <span class="mobile-hide"> - <span class="empty"><span class="price"><span class="price">$0.00</span></span></span></span>
-    </div>
-                <div class="dropdown-menu">
-            <div class="block-content">
-                <div class="empty">You have no items in your shopping cart.</div>
-            </div>
-        </div>
-    </div>
-
-<script type="text/javascript">
-    jQuery('#mini-cart').unbind('click').click(function(){
-        location.href = "/checkout/cart/";
-        return false;
-    })
-</script>
-                        </div>
-                    </div>
-                </div>
-            </div>
-        </div>
-    </div>
-</div>
-<div class="header-bottom">
-    <div class="container">
-        <div class="row">
-            <div class="col-xs-12">
-                <nav class="navbar navbar-default" role="navigation">
-                    <div class="container-fluid"> 
-                        <div class="navbar-header">
-                            <button type="button" class="navbar-toggle waveshare-navbar-toggle" data-toggle="collapse"
-                                    data-target="#ws-navbar-collapse">
-                                <span class="sr-only">Toggle navigation</span>
-                                <span class="icon-waveshare-menu"></span>
-                            </button>
-                            <div class="visible-xs">
-                                <div class="d-flex justify-content-between align-content-center form-search">
-                                    <form id="waveshare-search2" class="waveshare-search1 d-flex justify-content-between align-content-center" role="search" action="https://www.waveshare.com/catalogsearch/result/" method="get">
-                                        <div class="input-group-btn">
-                                            <input type="text" placeholder="Search" class="form-control" autocomplete="off" name="q">
-                                        </div>
-                                        <button type="submit" title="Search" class="button">Search</button>
-                                    </form>
-                                    <div id="waveshare-mini-cart2">
-                                        <a href="/checkout/cart/" class="d-flex align-content-center justify-content-center"><i class="icon-mycart-white"></i><span class="count badge" data-cart-count="mobile"></span></a>
-                                    </div>
-                                </div>
-                            </div>
-                        </div>
-                        <div class="collapse navbar-collapse navbar-left notin" id="ws-navbar-collapse">
-                          
-<ul class="nav navbar-nav">
-  <li class="moveto-last">
-      <a id="ws-show-products" href="/product.htm" class="d-flex align-content-center"><i class="icon-menu "></i><span>PRODUCTS</span></a>
-      <div id="ws-sidebar-home-top" class="waveshare-sidebar-home-top">
-          <nav class="amazonmenu">
-            <ul>
-            <li class="level0 nav-1 first last parent">
-<a href="https://www.waveshare.com/product.htm">
-<span>Products</span>
-</a>
-<ul class="level0">
-<li class="level1 nav-1-1 first parent">
-<a href="https://www.waveshare.com/product/raspberry-pi.htm">
-<span>Raspberry Pi</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-1-1 first parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-1-1 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-5.htm">
-<span>Raspberry Pi 5</span>
-</a>
-</li><li class="level3 nav-1-1-1-2">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-4.htm">
-<span>Raspberry Pi 4</span>
-</a>
-</li><li class="level3 nav-1-1-1-3">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-3.htm">
-<span>Raspberry Pi 3</span>
-</a>
-</li><li class="level3 nav-1-1-1-4">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-400.htm">
-<span>Raspberry Pi 400</span>
-</a>
-</li><li class="level3 nav-1-1-1-5">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-zero-2-w-cat.htm">
-<span>Raspberry Pi Zero 2 W</span>
-</a>
-</li><li class="level3 nav-1-1-1-6">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-zero.htm">
-<span>Raspberry Pi Zero</span>
-</a>
-</li><li class="level3 nav-1-1-1-7">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-pico-cat.htm">
-<span>Raspberry Pi Pico</span>
-</a>
-</li><li class="level3 nav-1-1-1-8">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/compute-module-4-4s-cat.htm">
-<span>Compute Module 4/4S</span>
-</a>
-</li><li class="level3 nav-1-1-1-9">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/compute-module.htm">
-<span>Compute Module 3</span>
-</a>
-</li><li class="level3 nav-1-1-1-10">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-pico-13.htm">
-<span>Raspberry Pi Pico 2</span>
-</a>
-</li><li class="level3 nav-1-1-1-11">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/cm5.htm">
-<span>Compute Module 5</span>
-</a>
-</li><li class="level3 nav-1-1-1-12 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-500-and-kits.htm">
-<span>Raspberry Pi 500</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-2 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-2-13 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays/lcd-oled.htm">
-<span>LCD</span>
-</a>
-</li><li class="level3 nav-1-1-2-14">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays/oled.htm">
-<span>OLED</span>
-</a>
-</li><li class="level3 nav-1-1-2-15 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-3 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-3-16 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/10mp-pixels.htm">
-<span>≥10MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-17">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/8m-pixels.htm">
-<span>8MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-18">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/5m-pixels.htm">
-<span>5MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-19">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/2m-pixels.htm">
-<span>2MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-20">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/global-shutter-cameras.htm">
-<span>Global Shutter Cameras</span>
-</a>
-</li><li class="level3 nav-1-1-3-21">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/usb-cameras.htm">
-<span>USB Cameras</span>
-</a>
-</li><li class="level3 nav-1-1-3-22">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/ai-cameras.htm">
-<span>AI Cameras</span>
-</a>
-</li><li class="level3 nav-1-1-3-23 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/gmsl-cameras.htm">
-<span>GMSL Cameras</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-4 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats.htm">
-<span>HATs</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-4-24 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/iot.htm">
-<span>IoT</span>
-</a>
-</li><li class="level3 nav-1-1-4-25">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/interface-power.htm">
-<span>Interface / Expansion / Power</span>
-</a>
-</li><li class="level3 nav-1-1-4-26">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/motors-relays.htm">
-<span>Motors / Relays / SCR</span>
-</a>
-</li><li class="level3 nav-1-1-4-27">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/ad-da-audio-sensors.htm">
-<span>AD / DA / Audio / Sensors</span>
-</a>
-</li><li class="level3 nav-1-1-4-28">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/led-buttons.htm">
-<span>LED / Buttons</span>
-</a>
-</li><li class="level3 nav-1-1-4-29 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/versatile.htm">
-<span>Versatile</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-5 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/laptop.htm">
-<span>All-in-one</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-5-30 first last">
-<a href="https://www.waveshare.com/product/raspberry-pi/laptop/all-in-one.htm">
-<span>Magic Mirror / All-in-one</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-6">
-<a href="https://www.waveshare.com/product/raspberry-pi/homelab.htm">
-<span>HomeLab</span>
-</a>
-</li><li class="level2 nav-1-1-7 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-7-31 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/robots/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-</li><li class="level3 nav-1-1-7-32 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/robots/robot-arm-control.htm">
-<span>Robot Arm / Control</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-8">
-<a href="https://www.waveshare.com/product/raspberry-pi/portable-gaming.htm">
-<span>Portable Gaming</span>
-</a>
-</li><li class="level2 nav-1-1-9 last parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-9-33 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories/pi-cases.htm">
-<span>Pi Cases</span>
-</a>
-</li><li class="level3 nav-1-1-9-34">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories/display-cases.htm">
-<span>Display Cases</span>
-</a>
-</li><li class="level3 nav-1-1-9-35 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories/wires-power-sd-card.htm">
-<span>Wires / Power / SD Card...</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-2 parent">
-<a href="https://www.waveshare.com/product/ai.htm">
-<span>AI</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-2-10 first parent">
-<a href="https://www.waveshare.com/product/ai/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-10-36 first">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-nano.htm">
-<span>Jetson Nano</span>
-</a>
-</li><li class="level3 nav-1-2-10-37">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-tx2.htm">
-<span>Jetson TX2</span>
-</a>
-</li><li class="level3 nav-1-2-10-38">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-xavier-nx-cata.htm">
-<span>Jetson Xavier NX</span>
-</a>
-</li><li class="level3 nav-1-2-10-39">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-orin.htm">
-<span>Jetson Orin</span>
-</a>
-</li><li class="level3 nav-1-2-10-40">
-<a href="https://www.waveshare.com/product/ai/boards-kits/ai-cameras.htm">
-<span>AI Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-10-41">
-<a href="https://www.waveshare.com/product/ai/boards-kits/ops-computer.htm">
-<span>OPS Computer</span>
-</a>
-</li><li class="level3 nav-1-2-10-42">
-<a href="https://www.waveshare.com/product/ai/boards-kits/raspberry-pi.htm">
-<span>Raspberry Pi</span>
-</a>
-</li><li class="level3 nav-1-2-10-43">
-<a href="https://www.waveshare.com/product/ai/boards-kits/d-robotics.htm">
-<span>D-Robotics</span>
-</a>
-</li><li class="level3 nav-1-2-10-44 last">
-<a href="https://www.waveshare.com/product/ai/boards-kits/luckfox.htm">
-<span>Luckfox</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-11 parent">
-<a href="https://www.waveshare.com/product/ai/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-11-45 first">
-<a href="https://www.waveshare.com/product/ai/displays/lcd-oled.htm">
-<span>LCD</span>
-</a>
-</li><li class="level3 nav-1-2-11-46">
-<a href="https://www.waveshare.com/product/ai/displays/oled.htm">
-<span>OLED</span>
-</a>
-</li><li class="level3 nav-1-2-11-47 last">
-<a href="https://www.waveshare.com/product/ai/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-12 parent">
-<a href="https://www.waveshare.com/product/ai/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-12-48 first">
-<a href="https://www.waveshare.com/product/ai/cameras/single-cameras.htm">
-<span>Single Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-49">
-<a href="https://www.waveshare.com/product/ai/cameras/binocular-cameras.htm">
-<span>Binocular Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-50">
-<a href="https://www.waveshare.com/product/ai/cameras/ai-usb-cameras.htm">
-<span>USB Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-51">
-<a href="https://www.waveshare.com/product/ai/cameras/gmsl-cameras.htm">
-<span>GMSL Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-52 last">
-<a href="https://www.waveshare.com/product/ai/cameras/others.htm">
-<span>Others</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-13 parent">
-<a href="https://www.waveshare.com/product/ai/expansions.htm">
-<span>Expansions</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-13-53 first">
-<a href="https://www.waveshare.com/product/ai/expansions/iot.htm">
-<span>IoT</span>
-</a>
-</li><li class="level3 nav-1-2-13-54">
-<a href="https://www.waveshare.com/product/ai/expansions/motors-relays.htm">
-<span>Motors / Relays / SCR</span>
-</a>
-</li><li class="level3 nav-1-2-13-55">
-<a href="https://www.waveshare.com/product/ai/expansions/ad-da-versatile.htm">
-<span>AD / DA / Versatile</span>
-</a>
-</li><li class="level3 nav-1-2-13-56 last">
-<a href="https://www.waveshare.com/product/ai/expansions/power-supply.htm">
-<span>Power Supply</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-14 parent">
-<a href="https://www.waveshare.com/product/ai/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-14-57 first">
-<a href="https://www.waveshare.com/product/ai/robots/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-</li><li class="level3 nav-1-2-14-58 last">
-<a href="https://www.waveshare.com/product/ai/robots/robot-arm-control.htm">
-<span>Robot Arm / Control</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-15 last parent">
-<a href="https://www.waveshare.com/product/ai/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-15-59 first">
-<a href="https://www.waveshare.com/product/ai/accessories/cases.htm">
-<span>Cases</span>
-</a>
-</li><li class="level3 nav-1-2-15-60 last">
-<a href="https://www.waveshare.com/product/ai/accessories/wires-power-sd-card.htm">
-<span>Wires / Power / SD Card...</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-3 parent">
-<a href="https://www.waveshare.com/product/luckfox.htm">
-<span>Luckfox</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-3-16 first parent">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules.htm">
-<span>Linux Boards / Modules</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-3-16-61 first">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/core3576.htm">
-<span>Omni3576-RK3576</span>
-</a>
-</li><li class="level3 nav-1-3-16-62">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-lyra-23.htm">
-<span>Luckfox Lyra-RK3506</span>
-</a>
-</li><li class="level3 nav-1-3-16-63">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-pico-core1106.htm">
-<span>LuckFox Pico-RV1106</span>
-</a>
-</li><li class="level3 nav-1-3-16-64">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-aura-rv1126.htm">
-<span>Luckfox Aura-RV1126</span>
-</a>
-</li><li class="level3 nav-1-3-16-65">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/core3566-9.htm">
-<span>Core3566-RK3566</span>
-</a>
-</li><li class="level3 nav-1-3-16-66 last">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-lume-t153.htm">
-<span>LuckFox Lume-T153</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-3-17 parent">
-<a href="https://www.waveshare.com/product/luckfox/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-3-17-67 first last">
-<a href="https://www.waveshare.com/product/luckfox/displays/lcd-oled.htm">
-<span>LCD/OLED</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-3-18 last parent">
-<a href="https://www.waveshare.com/product/luckfox/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-3-18-68 first">
-<a href="https://www.waveshare.com/product/luckfox/cameras/3mp-cameras.htm">
-<span>3MP Cameras</span>
-</a>
-</li><li class="level3 nav-1-3-18-69">
-<a href="https://www.waveshare.com/product/luckfox/cameras/8mp-cameras.htm">
-<span>8MP Cameras</span>
-</a>
-</li><li class="level3 nav-1-3-18-70">
-<a href="https://www.waveshare.com/product/luckfox/cameras/5mp-cameras.htm">
-<span>5MP Cameras</span>
-</a>
-</li><li class="level3 nav-1-3-18-71 last">
-<a href="https://www.waveshare.com/product/luckfox/cameras/1mp-cameras.htm">
-<span>1MP Cameras</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-4 parent">
-<a href="https://www.waveshare.com/product/risc-v.htm">
-<span>RISC-V</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-4-19 first parent">
-<a href="https://www.waveshare.com/product/risc-v/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-19-72 first">
-<a href="https://www.waveshare.com/product/risc-v/boards-kits/visionfive2.htm">
-<span>VisionFive2</span>
-</a>
-</li><li class="level3 nav-1-4-19-73 last">
-<a href="https://www.waveshare.com/product/risc-v/boards-kits/visionfive2-lite-7832.htm">
-<span>VisionFive2 Lite</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-4-20 parent">
-<a href="https://www.waveshare.com/product/risc-v/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-20-74 first last">
-<a href="https://www.waveshare.com/product/risc-v/displays/lcd.htm">
-<span>LCD</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-4-21 parent">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories.htm">
-<span>Expansions / Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-21-75 first">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories/audio-sensors.htm">
-<span>Audio / Sensors</span>
-</a>
-</li><li class="level3 nav-1-4-21-76">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories/relays-motors-servos.htm">
-<span>Relays / Motors / Servos</span>
-</a>
-</li><li class="level3 nav-1-4-21-77 last">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories/cooling-fan.htm">
-<span>Cooling Fan</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-4-22 last parent">
-<a href="https://www.waveshare.com/product/risc-v/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-22-78 first last">
-<a href="https://www.waveshare.com/product/risc-v/cameras/8mp-imx219-cameras.htm">
-<span>8MP IMX219 Cameras</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-5 parent">
-<a href="https://www.waveshare.com/product/esp32-related.htm">
-<span>ESP32</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-5-23 first parent">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-5-23-79 first">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-p4.htm">
-<span>ESP32-P4</span>
-</a>
-</li><li class="level3 nav-1-5-23-80">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-s3.htm">
-<span>ESP32-S3</span>
-</a>
-</li><li class="level3 nav-1-5-23-81">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-c6.htm">
-<span>ESP32-C6</span>
-</a>
-</li><li class="level3 nav-1-5-23-82">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-c5.htm">
-<span>ESP32-C5</span>
-</a>
-</li><li class="level3 nav-1-5-23-83">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-c3.htm">
-<span>ESP32-C3</span>
-</a>
-</li><li class="level3 nav-1-5-23-84">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-h2.htm">
-<span>ESP32-H2</span>
-</a>
-</li><li class="level3 nav-1-5-23-85">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-s2-1.htm">
-<span>ESP32-S2</span>
-</a>
-</li><li class="level3 nav-1-5-23-86 last">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-esp8266.htm">
-<span>ESP32</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-5-24 parent">
-<a href="https://www.waveshare.com/product/esp32-related/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-5-24-87 first">
-<a href="https://www.waveshare.com/product/esp32-related/displays/lcd-spi-qspi.htm">
-<span>LCD (SPI/QSPI)</span>
-</a>
-</li><li class="level3 nav-1-5-24-88">
-<a href="https://www.waveshare.com/product/esp32-related/displays/lcd-rgb.htm">
-<span>LCD (RGB)</span>
-</a>
-</li><li class="level3 nav-1-5-24-89">
-<a href="https://www.waveshare.com/product/esp32-related/displays/lcd-mipi.htm">
-<span>LCD (MIPI)</span>
-</a>
-</li><li class="level3 nav-1-5-24-90">
-<a href="https://www.waveshare.com/product/esp32-related/displays/amoled.htm">
-<span>AMOLED</span>
-</a>
-</li><li class="level3 nav-1-5-24-91">
-<a href="https://www.waveshare.com/product/esp32-related/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-</li><li class="level3 nav-1-5-24-92">
-<a href="https://www.waveshare.com/product/esp32-related/displays/rlcd.htm">
-<span>RLCD</span>
-</a>
-</li><li class="level3 nav-1-5-24-93 last">
-<a href="https://www.waveshare.com/product/esp32-related/displays/rgb-led-matrix.htm">
-<span>RGB LED Matrix</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-5-25">
-<a href="https://www.waveshare.com/product/esp32-related/ai-chat.htm">
-<span>AI Chat</span>
-</a>
-</li><li class="level2 nav-1-5-26">
-<a href="https://www.waveshare.com/product/esp32-related/cameras.htm">
-<span>Cameras</span>
-</a>
-</li><li class="level2 nav-1-5-27">
-<a href="https://www.waveshare.com/product/esp32-related/industrial-controller.htm">
-<span>Industrial Controller</span>
-</a>
-</li><li class="level2 nav-1-5-28 last parent">
-<a href="https://www.waveshare.com/product/esp32-related/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-5-28-94 first last">
-<a href="https://www.waveshare.com/product/esp32-related/robots/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-6 parent">
-<a href="https://www.waveshare.com/product/arduino-5.htm">
-<span>Arduino</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-6-29 first parent">
-<a href="https://www.waveshare.com/product/arduino-5/official-arduino.htm">
-<span>Official Arduino®</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-6-29-95 first last parent">
-<a href="https://www.waveshare.com/product/arduino-5/official-arduino/boards-core-boards.htm">
-<span>Boards / Core Boards</span>
-</a>
-<ul class="level3">
-<li class="level4 nav-1-6-29-95-1 first last">
-<a href="https://www.waveshare.com/product/arduino-5/official-arduino/boards-core-boards/arduino-uno-q-1.htm">
-<span>Arduino UNO Q</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level2 nav-1-6-30 last parent">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino.htm">
-<span>Compatible with Arduino®</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-6-30-96 first">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino/arduino-cases.htm">
-<span>Cases</span>
-</a>
-</li><li class="level3 nav-1-6-30-97">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino/arduino-kits.htm">
-<span>Kits</span>
-</a>
-</li><li class="level3 nav-1-6-30-98 last">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino/accessories.htm">
-<span>Accessories</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-7 parent">
-<a href="https://www.waveshare.com/product/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-7-31 first parent">
-<a href="https://www.waveshare.com/product/displays/lcd-oled.htm">
-<span>LCD</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-31-99 first">
-<a href="https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-1.htm">
-<span>5″  - 24.5″</span>
-</a>
-</li><li class="level3 nav-1-7-31-100">
-<a href="https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-2.htm">
-<span>2.8″  - 4.3″</span>
-</a>
-</li><li class="level3 nav-1-7-31-101 last">
-<a href="https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-3.htm">
-<span>0.71″  - 2.4″</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-32 parent">
-<a href="https://www.waveshare.com/product/displays/oled.htm">
-<span>OLED</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-32-102 first">
-<a href="https://www.waveshare.com/product/displays/oled/oled-1.htm">
-<span>5″  - 15.6″</span>
-</a>
-</li><li class="level3 nav-1-7-32-103 last">
-<a href="https://www.waveshare.com/product/displays/oled/oled-3.htm">
-<span>0.49″  - 2.4″</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-33 parent">
-<a href="https://www.waveshare.com/product/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-33-104 first">
-<a href="https://www.waveshare.com/product/displays/e-paper/epaper-1.htm">
-<span>5.65″  - 13.3″</span>
-</a>
-</li><li class="level3 nav-1-7-33-105">
-<a href="https://www.waveshare.com/product/displays/e-paper/epaper-2.htm">
-<span>2.66″  - 5″</span>
-</a>
-</li><li class="level3 nav-1-7-33-106">
-<a href="https://www.waveshare.com/product/displays/e-paper/epaper-3.htm">
-<span>1.02″  - 2.36″</span>
-</a>
-</li><li class="level3 nav-1-7-33-107 last">
-<a href="https://www.waveshare.com/product/displays/e-paper/driver-boards.htm">
-<span>Driver Boards</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-34 parent">
-<a href="https://www.waveshare.com/product/displays/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-34-108 first">
-<a href="https://www.waveshare.com/product/displays/accessories/cables-adapters.htm">
-<span>Cables / Adapters</span>
-</a>
-</li><li class="level3 nav-1-7-34-109">
-<a href="https://www.waveshare.com/product/displays/accessories/cases.htm">
-<span>Cases</span>
-</a>
-</li><li class="level3 nav-1-7-34-110">
-<a href="https://www.waveshare.com/product/displays/accessories/speakers.htm">
-<span>Speakers</span>
-</a>
-</li><li class="level3 nav-1-7-34-111 last">
-<a href="https://www.waveshare.com/product/displays/accessories/stand.htm">
-<span>Stand</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-35 last parent">
-<a href="https://www.waveshare.com/product/displays/usb-monitor.htm">
-<span>USB Monitor</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-35-112 first last">
-<a href="https://www.waveshare.com/product/displays/usb-monitor/2-1-7.htm">
-<span>2.1“ - 7“</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-8 parent">
-<a href="https://www.waveshare.com/product/iot-communication.htm">
-<span>IoT / Communication</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-8-36 first parent">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless.htm">
-<span>Long Range Wireless</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-8-36-113 first">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless/nb-iot-lora.htm">
-<span>NB-IoT / Cat-M / LoRa / LoRaWAN</span>
-</a>
-</li><li class="level3 nav-1-8-36-114">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless/4g-gsm-gprs.htm">
-<span>5G / 4G / Cat-1 / GSM / GPRS</span>
-</a>
-</li><li class="level3 nav-1-8-36-115 last">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless/gnss-gps.htm">
-<span>GNSS / GPS</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-8-37 parent">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless.htm">
-<span>Short Range Wireless</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-8-37-116 first">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/wifi.htm">
-<span>WiFi</span>
-</a>
-</li><li class="level3 nav-1-8-37-117">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/zigbee.htm">
-<span>ZigBee</span>
-</a>
-</li><li class="level3 nav-1-8-37-118">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/bluetooth.htm">
-<span>Bluetooth</span>
-</a>
-</li><li class="level3 nav-1-8-37-119 last">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/nfc-rf.htm">
-<span>NFC / RF</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-8-38 last parent">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter.htm">
-<span>Wired Comm / Converter</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-8-38-120 first">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb.htm">
-<span>USB</span>
-</a>
-</li><li class="level3 nav-1-8-38-121">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs232-uart-rs485.htm">
-<span>USB TO RS232 / RS485  / UART/ CAN</span>
-</a>
-</li><li class="level3 nav-1-8-38-122">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/ethernet.htm">
-<span>Ethernet</span>
-</a>
-</li><li class="level3 nav-1-8-38-123">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/ethernet-to-uart-rs232-rs485.htm">
-<span>Ethernet TO UART / RS232 / RS485</span>
-</a>
-</li><li class="level3 nav-1-8-38-124 last">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/rs232-rs485-can-dali2.htm">
-<span>RS232 / RS485 / CAN / DALI2 </span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-9 parent">
-<a href="https://www.waveshare.com/product/modules.htm">
-<span>Misc Modules</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-9-39 first parent">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video.htm">
-<span>Cameras / Audio / Video</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-39-125 first">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/speech-image-recognition-ai-vision.htm">
-<span>Speech / Image Recognition / AI Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-126">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/mipi-cameras.htm">
-<span>MIPI Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-127">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/usb-cameras.htm">
-<span>USB Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-128">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/gmsl-cameras.htm">
-<span>GMSL Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-129">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/cameras.htm">
-<span>Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-130 last">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/audio-decoder.htm">
-<span>Audio Decoder</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-9-40 parent">
-<a href="https://www.waveshare.com/product/modules/sensors.htm">
-<span>Sensors</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-40-131 first">
-<a href="https://www.waveshare.com/product/modules/sensors/accelerometer-angular-rate-compass.htm">
-<span>Accelerometer / Angular Rate / Compass</span>
-</a>
-</li><li class="level3 nav-1-9-40-132">
-<a href="https://www.waveshare.com/product/modules/sensors/fingerprint-sound-image-gesture.htm">
-<span>Fingerprint / Sound / Image / Gesture</span>
-</a>
-</li><li class="level3 nav-1-9-40-133">
-<a href="https://www.waveshare.com/product/modules/sensors/temperature-humidity-barometer.htm">
-<span>Temperature / Humidity / Barometer</span>
-</a>
-</li><li class="level3 nav-1-9-40-134">
-<a href="https://www.waveshare.com/product/modules/sensors/gas.htm">
-<span>Gas</span>
-</a>
-</li><li class="level3 nav-1-9-40-135">
-<a href="https://www.waveshare.com/product/modules/sensors/light-ranging.htm">
-<span>Light / Ranging / Lidar</span>
-</a>
-</li><li class="level3 nav-1-9-40-136 last">
-<a href="https://www.waveshare.com/product/modules/sensors/others.htm">
-<span>Others</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-9-41 parent">
-<a href="https://www.waveshare.com/product/modules/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-41-137 first">
-<a href="https://www.waveshare.com/product/modules/motors-servos/drivers.htm">
-<span>Drivers</span>
-</a>
-</li><li class="level3 nav-1-9-41-138 last">
-<a href="https://www.waveshare.com/product/modules/motors-servos/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-9-42 last parent">
-<a href="https://www.waveshare.com/product/modules/others.htm">
-<span>Others</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-42-139 first">
-<a href="https://www.waveshare.com/product/modules/others/interface-expansion.htm">
-<span>Interface Expansion</span>
-</a>
-</li><li class="level3 nav-1-9-42-140">
-<a href="https://www.waveshare.com/product/modules/others/led-buttons.htm">
-<span>LED / Buttons</span>
-</a>
-</li><li class="level3 nav-1-9-42-141">
-<a href="https://www.waveshare.com/product/modules/others/storage.htm">
-<span>Storage</span>
-</a>
-</li><li class="level3 nav-1-9-42-142">
-<a href="https://www.waveshare.com/product/modules/others/ad-da.htm">
-<span>AD / DA</span>
-</a>
-</li><li class="level3 nav-1-9-42-143">
-<a href="https://www.waveshare.com/product/modules/others/rtc.htm">
-<span>RTC</span>
-</a>
-</li><li class="level3 nav-1-9-42-144">
-<a href="https://www.waveshare.com/product/modules/others/power-relays.htm">
-<span>Power / Relays / SCR</span>
-</a>
-</li><li class="level3 nav-1-9-42-145 last">
-<a href="https://www.waveshare.com/product/modules/others/laser-module.htm">
-<span>Laser Module</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-10 parent">
-<a href="https://www.waveshare.com/product/robotics.htm">
-<span>Robotics</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-10-43 first parent">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-43-146 first">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/jetson-series-ai-robots.htm">
-<span>Jetson Series AI Robots</span>
-</a>
-</li><li class="level3 nav-1-10-43-147">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/raspberry-pi-robots.htm">
-<span>Raspberry Pi Robots</span>
-</a>
-</li><li class="level3 nav-1-10-43-148">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/arduino-robots.htm">
-<span>Arduino-Related Robots</span>
-</a>
-</li><li class="level3 nav-1-10-43-149 last">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/micro-bit-robots.htm">
-<span>micro:bit Robots</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-44 parent">
-<a href="https://www.waveshare.com/product/robotics/dog-like-robots.htm">
-<span>Dog-like Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-44-150 first last">
-<a href="https://www.waveshare.com/product/robotics/dog-like-robots/raspberry-pi-dog-like-robots.htm">
-<span>Raspberry Pi Dog-like Robots</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-45 parent">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors.htm">
-<span>Drivers / Sensors / Lidar</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-45-151 first">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors/drivers.htm">
-<span>Drivers</span>
-</a>
-</li><li class="level3 nav-1-10-45-152">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors/sensors.htm">
-<span>Sensors</span>
-</a>
-</li><li class="level3 nav-1-10-45-153 last">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors/lidar.htm">
-<span>Lidar</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-46 parent">
-<a href="https://www.waveshare.com/product/robotics/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-46-154 first">
-<a href="https://www.waveshare.com/product/robotics/motors-servos/motors.htm">
-<span>Motors</span>
-</a>
-</li><li class="level3 nav-1-10-46-155 last">
-<a href="https://www.waveshare.com/product/robotics/motors-servos/servos.htm">
-<span>Servos</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-47 parent">
-<a href="https://www.waveshare.com/product/robotics/robot-arm-control.htm">
-<span>Robot Arm / Control</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-47-156 first">
-<a href="https://www.waveshare.com/product/robotics/robot-arm-control/robot-arm.htm">
-<span>Robot Arm</span>
-</a>
-</li><li class="level3 nav-1-10-47-157 last">
-<a href="https://www.waveshare.com/product/robotics/robot-arm-control/pan-tilt-control.htm">
-<span>Pan Tilt Control</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-48">
-<a href="https://www.waveshare.com/product/robotics/remote-controller.htm">
-<span>Remote Controller</span>
-</a>
-</li><li class="level2 nav-1-10-49 last parent">
-<a href="https://www.waveshare.com/product/robotics/robotic-components.htm">
-<span>Robotic Components</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-49-158 first">
-<a href="https://www.waveshare.com/product/robotics/robotic-components/gearing.htm">
-<span>Gearing</span>
-</a>
-</li><li class="level3 nav-1-10-49-159 last">
-<a href="https://www.waveshare.com/product/robotics/robotic-components/chassis-accessories.htm">
-<span>Chassis Accessories</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-11 parent">
-<a href="https://www.waveshare.com/product/mcu-tools.htm">
-<span>MCU / FPGA</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-11-50 first parent">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards.htm">
-<span>Core Boards / Compact Boards</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-50-160 first">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/stm32-core.htm">
-<span>STM32 Core</span>
-</a>
-</li><li class="level3 nav-1-11-50-161">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/stm32-discovery.htm">
-<span>STM32 Discovery</span>
-</a>
-</li><li class="level3 nav-1-11-50-162">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/stm32-nucleo.htm">
-<span>STM32 Nucleo</span>
-</a>
-</li><li class="level3 nav-1-11-50-163">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/lpc-core.htm">
-<span>LPC Core</span>
-</a>
-</li><li class="level3 nav-1-11-50-164">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/beagleboard.htm">
-<span>BeagleBoard</span>
-</a>
-</li><li class="level3 nav-1-11-50-165">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/altera-core.htm">
-<span>ALTERA Core</span>
-</a>
-</li><li class="level3 nav-1-11-50-166">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/arduino.htm">
-<span>Arduino® Compatible</span>
-</a>
-</li><li class="level3 nav-1-11-50-167 last">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/micro-bit-boards.htm">
-<span>micro:bit</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-51 parent">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards.htm">
-<span>Development Boards / Expansions</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-51-168 first">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/stm32-open.htm">
-<span>STM32 Open</span>
-</a>
-</li><li class="level3 nav-1-11-51-169">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/stm32-evk.htm">
-<span>STM32 EVK</span>
-</a>
-</li><li class="level3 nav-1-11-51-170">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/avr-arduino-shields.htm">
-<span>AVR Arduino Shields</span>
-</a>
-</li><li class="level3 nav-1-11-51-171">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/arduino-shields-compatible.htm">
-<span>Arduino Shields Compatible</span>
-</a>
-</li><li class="level3 nav-1-11-51-172">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/displays-buttons-sound.htm">
-<span>Displays / Buttons / Sound</span>
-</a>
-</li><li class="level3 nav-1-11-51-173 last">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/motors-interface.htm">
-<span>Motors / Interface</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-52 parent">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer.htm">
-<span>Debugger / Programmer</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-52-174 first">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/stm32-stm8.htm">
-<span>STM32 / STM8</span>
-</a>
-</li><li class="level3 nav-1-11-52-175">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/avr.htm">
-<span>AVR</span>
-</a>
-</li><li class="level3 nav-1-11-52-176">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/pic.htm">
-<span>PIC</span>
-</a>
-</li><li class="level3 nav-1-11-52-177">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/altera-core.htm">
-<span>ALTERA Core</span>
-</a>
-</li><li class="level3 nav-1-11-52-178 last">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/xilinx.htm">
-<span>XILINX</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-53 parent">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters.htm">
-<span>Programming Adapters</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-53-179 first">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters/stm32.htm">
-<span>STM32</span>
-</a>
-</li><li class="level3 nav-1-11-53-180">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters/stm8.htm">
-<span>STM8</span>
-</a>
-</li><li class="level3 nav-1-11-53-181 last">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters/avr.htm">
-<span>AVR</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-54 last parent">
-<a href="https://www.waveshare.com/product/mcu-tools/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-54-182 first last">
-<a href="https://www.waveshare.com/product/mcu-tools/robots/robot-arm.htm">
-<span>Robot Arm</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-12 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters.htm">
-<span>Sockets / Adapters</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-12-55 first parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters.htm">
-<span>Specific Programming Adapters</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-55-183 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters/stm32-series.htm">
-<span>STM32 Series</span>
-</a>
-</li><li class="level3 nav-1-12-55-184">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters/stm8-series.htm">
-<span>STM8 Series</span>
-</a>
-</li><li class="level3 nav-1-12-55-185 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters/avr-series.htm">
-<span>AVR Series</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-56 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp.htm">
-<span>QFP</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-56-186 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-56-187">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li><li class="level3 nav-1-12-56-188 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp/with-pinheader.htm">
-<span>With Pinheader</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-57 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf.htm">
-<span>QFN / MLF</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-57-189 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-57-190">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li><li class="level3 nav-1-12-57-191 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf/with-pinheader.htm">
-<span>With Pinheader</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-58 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/sop.htm">
-<span>SOP</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-58-192 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/sop/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-58-193 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/sop/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-59 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/ssop-tssop.htm">
-<span>SSOP / TSSOP</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-59-194 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/ssop-tssop/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-59-195 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/ssop-tssop/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-60 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/tsop-msop-sot.htm">
-<span>TSOP / MSOP / SOT</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-60-196 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/tsop-msop-sot/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-60-197 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/tsop-msop-sot/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-61 last parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/plcc.htm">
-<span>PLCC</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-61-198 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/plcc/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-61-199 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/plcc/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-13 last parent">
-<a href="https://www.waveshare.com/product/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-13-62 first parent">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas.htm">
-<span>Adapters / Cables / Antennas</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-62-200 first">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/hdmi.htm">
-<span>HDMI</span>
-</a>
-</li><li class="level3 nav-1-13-62-201">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/usb.htm">
-<span>USB</span>
-</a>
-</li><li class="level3 nav-1-13-62-202">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/serial-cables.htm">
-<span>Serial Cables</span>
-</a>
-</li><li class="level3 nav-1-13-62-203">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/jumper-wires.htm">
-<span>Jumper Wires</span>
-</a>
-</li><li class="level3 nav-1-13-62-204">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/ffc.htm">
-<span>FFC</span>
-</a>
-</li><li class="level3 nav-1-13-62-205 last">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/antennas.htm">
-<span>Antennas</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-13-63 parent">
-<a href="https://www.waveshare.com/product/accessories/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-63-206 first">
-<a href="https://www.waveshare.com/product/accessories/motors-servos/motors.htm">
-<span>Motors</span>
-</a>
-</li><li class="level3 nav-1-13-63-207 last">
-<a href="https://www.waveshare.com/product/accessories/motors-servos/servos.htm">
-<span>Servos</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-13-64 parent">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks.htm">
-<span>Power / Heat Sinks</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-64-208 first">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/power-supply.htm">
-<span>Power Supply</span>
-</a>
-</li><li class="level3 nav-1-13-64-209">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/solar-power.htm">
-<span>Solar Power</span>
-</a>
-</li><li class="level3 nav-1-13-64-210">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/heat-sinks.htm">
-<span>Heat Sinks</span>
-</a>
-</li><li class="level3 nav-1-13-64-211 last">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/cooling-fans.htm">
-<span>Cooling Fans</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-13-65 last parent">
-<a href="https://www.waveshare.com/product/accessories/misc.htm">
-<span>Misc</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-65-212 first">
-<a href="https://www.waveshare.com/product/accessories/misc/raspberry-pi-cases.htm">
-<span>Raspberry Pi Cases</span>
-</a>
-</li><li class="level3 nav-1-13-65-213">
-<a href="https://www.waveshare.com/product/accessories/misc/jetson-nano-cases.htm">
-<span>Jetson Nano Cases</span>
-</a>
-</li><li class="level3 nav-1-13-65-214">
-<a href="https://www.waveshare.com/product/accessories/misc/display-cases.htm">
-<span>Display Cases</span>
-</a>
-</li><li class="level3 nav-1-13-65-215">
-<a href="https://www.waveshare.com/product/accessories/misc/speakers.htm">
-<span>Speakers</span>
-</a>
-</li><li class="level3 nav-1-13-65-216 last">
-<a href="https://www.waveshare.com/product/accessories/misc/storage.htm">
-<span>Storage</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-</li>            </ul>
-          </nav>
-      </div>
-  </li>
-  <li>
-      <a href="https://www.waveshare.com/">
-                        <span>Home</span>
-                </a>
-  </li>
-    <li class="level0 act level-top parent"><a class="level-top" href="/new?dir=desc&amp;order=position"> <span>New Arrivals</span> </a></li>
-<li class="level0 act level-top parent"><a class="level-top" href="/product/displays.htm"> <span>Displays</span> </a></li>
-<li class="level0 act level-top parent"><a class="level-top" href="/product/ai.htm"> <span>AI</span> </a></li>
-<li class="level0 act level-top parent"><a class="level-top" href="/shipping"> <span>Shipping</span> </a></li>
-<li class="level0 act level-top parent"><a class="level-top" href="/payment"> <span>Payment</span> </a></li>
-<li class="level0 act level-top parent"><a class="level-top" href="/customization.html"> <span>Customization</span> </a></li>
-<li class="level0 act level-top parent"><a class="level-top" href="/wiki"> <span>Wiki</span> </a></li>
-<li class="level0 level-top parent"><a class="level-top" href="/shopping_q_a"> <span>Shopping Q&amp;A</span> </a></li></ul>
-
-<script type="text/javascript">
-//<![CDATA[
-var CUSTOMMENU_POPUP_TOP_OFFSET = 50;
-var eternalCustommenuTimerShow = {};
-var eternalCustommenuTimerHide = {};
-var eternalActiveMenu = null;
-eternalCustomMenuMobileToggle();
-//]]>
-jQuery(function($){
-    var $ = jQuery;
-    var timer;
-    function addopen() {
-        clearTimeout(timer); 
-        $('#ws-sidebar-home-top').addClass('open');
-    }
-    function delayedRemoveopen() {
-        timer = setTimeout(function() {
-            $('#ws-sidebar-home-top').removeClass('open');
-        }, 100); 
-    }
-    $('#ws-show-products').on('click mouseenter', addopen);
-    $('#ws-sidebar-home-top').on('mouseenter', addopen);
-    $('#ws-show-products').on('mouseleave', delayedRemoveopen);
-    $('#ws-sidebar-home-top').on('mouseleave', delayedRemoveopen);
-
-    if (!('ontouchstart' in window)) {
-        $('#ws-sidebar-home-top ul.level0 li').hover(
-            function() {
-                $(this).addClass('pick');
-                if ($(this).children('ul').length > 0) {
-                    $(this).children('ul').stop(true, true).show();
-                }
-            }, 
-            function() {
-                $(this).removeClass('pick');
-                if ($(this).children('ul').length > 0) {
-                    $(this).children('ul').stop(true, true).hide();
-                }
-            }
-        );
-    }
-
-    $('#ws-sidebar-home-top li a').click(function(e) {
-        e.stopPropagation();
-    });
-    $('#ws-sidebar-home-top ul.level0 li.parent > ul').hide();
-    $('#ws-sidebar-home-top li > a > span').click(function(e) {
-        if ('ontouchstart' in window) {
-            e.stopPropagation();
-            let $parentLi = $(this).parent().parent();
-            if ($parentLi.children('ul').length > 0) {
-                $parentLi.siblings().find('ul').hide();
-                $parentLi.children('ul').toggle();
-                return false;
-            }
-        }
-    });
-    delayedRemoveopen();
-});
-</script>                        </div>
-                        <!--<a class="navbar-text navbar-right hidden-xs" href="https://service.waveshare.com"><span class="d-flex align-content-center"><i class="icon-waveshare-supp"></i>SUPPORT</span></a>-->
-                    </div>
-                </nav>
-            </div>
-        </div>
-    </div>
-</div>
-
-<style>
-    #nav li a{
-        padding: 12px 12px !important; 
-    }
-    .navbar-collapse.notin {
-      overflow-y: unset !important;
-    }
-</style>    </div>
-    <div class="main-container">
-                                        <div class="breadcrumbs">
-    <div class="container">
-        <ul>
-                            <li class="home">
-                                    <a href="https://www.waveshare.com/" title="Go to Home Page">Home</a>
-                                                    <span>&gt; </span>
-                                </li>
-                            <li class="product">
-                                    <strong>33552</strong>
-                                                </li>
-                    </ul>
-    </div>
-</div>
-                <div class="main">
-            <div class="container">
-                                    <div class="row">                    <div class="col-lg-10 main-content-right main-content">
-                                                
-<script type="text/javascript">
-//<![CDATA[
-var ETERNAL_AJAXCART_PROCESSING = "Please wait...";
-var ETERNAL_AJAXCART_SOMETHING_BAD = "Something bad happened.";
-var ETERNAL_AJAXCART_SELECT_OPTIONS = "Please Select Options";
-var ETERNAL_AJAXCART_ERROR = { bg_color: '#F66F82', color: '#000'};
-//var ETERNAL_AJAXCART_INFO = { bg_color: '#65ae00', color: '#ffffff'};
-var ETERNAL_AJAXCART_INFO = { bg_color: '#1c1d1f', color: '#e8e8e8'};
-var ETERNAL_AJAXCART_WARN = { bg_color: '#1c1d1f', color: '#e8e8e8'};
-var ETERNAL_AJAX_CART = "Add to Cart";
-var ETERNAL_AJAX_WISHLIST = "Add to Wishlist";
-var ETERNAL_AJAX_COMPARE = "Add to Compare";
-//]]>
-</script><script type="text/javascript">
-    var optionsPrice = new Product.OptionsPrice([]);
-</script>
-<div id="messages_product_view"></div>
-<div class="product-view" id="product-view">
-    <div class="product-essential">
-        <form action="https://www.waveshare.com/checkout/cart/add/uenc/aHR0cHM6Ly93d3cud2F2ZXNoYXJlLmNvbS9lc3AzMi1zMy1lcGFwZXItMy45Ny5odG0_X19fU0lEPVU,/product/8067/form_key/8jMM237x0qPatli4/" method="post" id="product_addtocart_form" >
-            <input name="form_key" type="hidden" value="8jMM237x0qPatli4" />
-            <div class="no-display">
-                <input type="hidden" name="product" value="8067" />
-                <input type="hidden" name="related_product" id="related-products-field" value="" />
-            </div>
-
-            <div class="product-essential-inner row">
-                <div class="col-sm-7 product-img-box">
-                    
-<div class="clearfix">
-
-        
-        <div class="more-images">
-        <ul id="moreimages-slider-8067" class="elastislide-list">
-                
-                                            <li>
-                
-                    <a href="https://www.waveshare.com/media/catalog/product/cache/1/image/800x800/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-1_1.jpg"
-                     data-lightbox="lightboxgroup-8067" 
-                    class="cloud-zoom-gallery" 
-                    title="" 
-                    rel="useZoom:'product-zoom-8067', smallImage: 'https://www.waveshare.com/media/catalog/product/cache/1/image/560x560/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-1_1.jpg'"
-                    >
-                        <img src="https://www.waveshare.com/media/catalog/product/cache/1/thumbnail/122x122/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-1_1.jpg" alt=""/>
-                    </a>
-                    
-                </li>
-                                            <li>
-                
-                    <a href="https://www.waveshare.com/media/catalog/product/cache/1/image/800x800/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-2_1.jpg"
-                     data-lightbox="lightboxgroup-8067" 
-                    class="cloud-zoom-gallery" 
-                    title="" 
-                    rel="useZoom:'product-zoom-8067', smallImage: 'https://www.waveshare.com/media/catalog/product/cache/1/image/560x560/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-2_1.jpg'"
-                    >
-                        <img src="https://www.waveshare.com/media/catalog/product/cache/1/thumbnail/122x122/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-2_1.jpg" alt=""/>
-                    </a>
-                    
-                </li>
-                                            <li>
-                
-                    <a href="https://www.waveshare.com/media/catalog/product/cache/1/image/800x800/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-3_1.jpg"
-                     data-lightbox="lightboxgroup-8067" 
-                    class="cloud-zoom-gallery" 
-                    title="" 
-                    rel="useZoom:'product-zoom-8067', smallImage: 'https://www.waveshare.com/media/catalog/product/cache/1/image/560x560/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-3_1.jpg'"
-                    >
-                        <img src="https://www.waveshare.com/media/catalog/product/cache/1/thumbnail/122x122/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-3_1.jpg" alt=""/>
-                    </a>
-                    
-                </li>
-                                            <li>
-                
-                    <a href="https://www.waveshare.com/media/catalog/product/cache/1/image/800x800/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-4_1.jpg"
-                     data-lightbox="lightboxgroup-8067" 
-                    class="cloud-zoom-gallery" 
-                    title="" 
-                    rel="useZoom:'product-zoom-8067', smallImage: 'https://www.waveshare.com/media/catalog/product/cache/1/image/560x560/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-4_1.jpg'"
-                    >
-                        <img src="https://www.waveshare.com/media/catalog/product/cache/1/thumbnail/122x122/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-4_1.jpg" alt=""/>
-                    </a>
-                    
-                </li>
-                                            <li>
-                
-                    <a href="https://www.waveshare.com/media/catalog/product/cache/1/image/800x800/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-5_1.jpg"
-                     data-lightbox="lightboxgroup-8067" 
-                    class="cloud-zoom-gallery" 
-                    title="" 
-                    rel="useZoom:'product-zoom-8067', smallImage: 'https://www.waveshare.com/media/catalog/product/cache/1/image/560x560/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-5_1.jpg'"
-                    >
-                        <img src="https://www.waveshare.com/media/catalog/product/cache/1/thumbnail/122x122/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-5_1.jpg" alt=""/>
-                    </a>
-                    
-                </li>
-                    
-                </ul>
-    </div> <!-- end: more-images -->
-    
-
-    
-
-        <div class="product-image">
-
-            <a href="https://www.waveshare.com/media/catalog/product/cache/1/image/800x800/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-1_1.jpg" class="cloud-zoom" id="product-zoom-8067" rel="position:'inside',lensOpacity:0.5,smoothMove:3,showTitle:0,titleOpacity:0.5,zoomWidth:800,zoomHeight:800,adjustX:0,adjustY:0,tint:'1',tintOpacity:0.5,softFocus:1">
-                <img src="https://www.waveshare.com/media/catalog/product/cache/1/image/560x560/9df78eab33525d08d6e5fb8d27136e95/e/s/esp32-s3-epaper-3.97-1_1.jpg" alt="ESP32-S3 3.97inch e-Paper Development Board, 800 × 480 Resolution, Supports Wi-Fi / BLE 5, And AI Voice Interaction, Onboard Microphone" title="ESP32-S3 3.97inch e-Paper Development Board, 800 × 480 Resolution, Supports Wi-Fi / BLE 5, And AI Voice Interaction, Onboard Microphone" />
-            </a>
-                        
-                                </div>
-    
-        
-
-</div>
-
-<script type="text/javascript">
-//<![CDATA[
-jQuery(function($) {
-    var image_es;
-    var zoom_timer;
-        
-    function resize_cloudzoom() {
-        $(".more-images .cloud-zoom-gallery").first().trigger('mouseenter'); 
-        $(".more-images .cloud-zoom-gallery").first().trigger('touchstart'); 
-                if (image_es) 
-            image_es.destroy();
-        image_es = $('#moreimages-slider-8067').elastislide({
-            orientation : 'vertical',
-           //orientation : 'horizontal',
-            minItems: 4
-        });
-                if (zoom_timer) clearTimeout(zoom_timer);
-    }
-    $(window).load(resize_cloudzoom);
-    $(window).resize(function() {
-        clearTimeout(zoom_timer);
-        zoom_timer = setTimeout(resize_cloudzoom, 200); 
-    });
-});
-//]]>
-</script>
-<style>
-.product-img-box .product-image div#wrap {
-    z-index: 900 !important;
-}
-</style>                </div>
-                <div class="col-sm-5 product-shop">
-                    <div class="cat-link"><a href='https://www.waveshare.com/product/displays/e-paper/epaper-2.htm'>2.66″  - 5″</a>, <a href='https://www.waveshare.com/product/esp32-related/ai-chat.htm'>AI Chat</a>, <a href='https://www.waveshare.com/product/esp32-related/displays/e-paper.htm'>e-Paper</a></div>
-                    <div class="product-name">
-                        <h1>ESP32-S3 3.97inch e-Paper Development Board, 800 × 480 Resolution, Supports Wi-Fi / BLE 5, And AI Voice Interaction, Onboard Microphone</h1>
-                    </div>
-                    <!-- start -->
-                    
-                    
-                    
-                                        
-                    
-                                        <!-- end -->
-
-                                            <div class="price-review">
-                            <div class="add-to-box choose_add-to-box">
-                                                                    <div class="add-to-cart" style="margin: 0 0 0px;">
-    <!-- add by libearxiong 20160502 -->
-    
-
-<span class="waveshare_price-box price-box">
-    <!---->
-        <span class="">
-        <span class="price">$34.99</span> -
-    </span>
-        <span class="regular-price" id="product-price-1">
-        <span class="price">$47.99</span>    </span>
-</span>
-
-    <!-- add by libearxiong 2019041401 -->
-          <span class="waveshare_addtocart_cart">
-        <span>
-                            <button type="button" title="Add to Cart" class="waveshare_addtocart_button button btn-cart" id="waveshare_set_show_select_button">
-                  <span>
-                      <span>Add to Cart</span>
-                  </span>
-              </button>
-                      </span>
-      </span>
-            <script type="text/javascript">
-        //<![CDATA[
-        jQuery(function($) {
-          $('#waveshare_set_show_select_button').click(function() {
-                $('#waveshare_set_show_select_label').show();
-            });
-        })
-        //]]>
-      </script>
-          </div>
-<div class="waveshare_backorder_remarks" style="display: none;" id="waveshare_set_show_select_label">&#8595;Please select all required options below before ordering.</div>
-<!-- add by libearxiong 20200302 -->
-<!--<div class="add-to-cart-extra"></div>-->                                                            </div>
-                                                                        </div>
-                                        <!-- add by libearxiong 20190630 -->
-                                        <div class="waveshare_view_relate"><style type="text/css">
-.block-related input.checkbox {
-    position: inherit;
-    left: 0px;
-    top: 0px;
-    z-index: 10;
-}
-.block {
-    margin: 0 0 0px;
-}
-input[type="checkbox"] {
-    margin-top: 0px;
-}
-.block-related li {
-    padding: 0 0;
-}
-/* #block-related {
-    font-weight: bold;
-} */
-#block-related .price {
-    color: #737373;
-    font-size: 13.3px !important;
-    margin-right: 0px;
-}
-</style></div>
-                                        
-                    
-                    
-                    
-                                            <div class="add-to-box choose_add-to-box" id="waveshare_options">
-                            <!-- add by libearxiong 20190803 -->
-                            <!-- modify by libearxiong 20190922 -->
-                                                                <div class="goods-detail-line mobile-detail clearfix">
-                                        <div class="line-left">
-                                            Version Options                                        </div>
-                                        <div class="line-right">
-                                            <a href="javascript: void(0);" class="tag-text has_goods goods" setIndex="0">Basic Kit (Lithium Batt + TF Card + Card Reader)</a><a href="javascript: void(0);" class="tag-text has_goods goods" setIndex="0">With Lithium Batt</a><a href="javascript: void(0);" class="tag-text has_goods goods" setIndex="0">Without Lithium Batt</a>                                        </div>
-                                    </div>
-                                                        <!--add by libearxiong 20151209-->
-                            
-                            <!-- add by libearxiong 20160502 -->
-                            <!--<h3 class="waveshare_line"></h3>-->
-
-                                                        <div class="add-links-wrap clearfix">
-                                                                
-                                                                    <!-- Social bookmarks from //www.addthis.com/get/sharing  -->
-                                    <!--<div class="addthis-icons clearfix">
-                                    <span>Share: </span>
-                                    <div class="addthis_toolbox addthis_default_style addthis_32x32_style">
-                                    <a class="addthis_button_preferred_1"></a>
-                                    <a class="addthis_button_preferred_2"></a>
-                                    <a class="addthis_button_preferred_3"></a>
-                                    <a class="addthis_button_preferred_4"></a>
-                                    <a class="addthis_button_compact"></a>
-                                    <a class="addthis_counter addthis_bubble_style"></a>
-                                    </div>
-                                    <script type="text/javascript" src="//s7.addthis.com/js/300/addthis_widget.js#pubid=xa-5054e6c6502d114f"></script>
-                                </div>-->
-                                    <div class="addthis-icons clearfix">
-                                        <span>Share: </span>
-                                        <div class="sharethis-inline-share-buttons"></div>
-                                    </div>
-                                                            </div>
-                        </div>
-                                            
-                    
-                                    </div>
-            </div>
-        </form>
-        <script type="text/javascript">
-            //<![CDATA[
-            // add by libearxiong 20190922
-            var waveshare_is_product_set_page = 0;
-            var waveshare_sku_attributes = [{"sku ":"33552","attributes":["With Lithium Batt"],"unsaleable":false},{"sku ":"33810","attributes":["Without Lithium Batt"],"unsaleable":false},{"sku ":"33811","attributes":["Basic Kit (Lithium Batt + TF Card + Card Reader)"],"unsaleable":false}];
-            var waveshare_attributes2sku = {"With Lithium Batt":"33552","Without Lithium Batt":"33810","Basic Kit (Lithium Batt + TF Card + Card Reader)":"33811"};
-            var _product_url = location.origin + '/esp32-s3-epaper-3.97.htm';
-            console.log('_product_url', _product_url);
-            var waveshare_selected_attributes = ["With Lithium Batt"];
-            var sku_init = '';
-            if (waveshare_is_product_set_page == 0 && waveshare_sku_attributes) {
-                waveshare_selected_attributes = [];
-                for (i = 0; i < waveshare_sku_attributes[0].attributes.length; i++) {
-                    waveshare_selected_attributes.push(null);
-                }
-            }
-            console.log(waveshare_is_product_set_page, waveshare_selected_attributes, sku_init);
-            var productAddToCartForm = new VarienForm('product_addtocart_form');
-            productAddToCartForm.submit = function(button, url) {
-                if (this.validator.validate()) {
-                    var form = this.form;
-                    var oldUrl = form.action;
-
-                    if (url) {
-                        form.action = url;
-                    }
-                    var e = null;
-                    try {
-                        this.form.submit();
-                    } catch (e) {}
-                    this.form.action = oldUrl;
-                    if (e) {
-                        throw e;
-                    }
-
-                    if (button && button != 'undefined') {
-                        button.disabled = true;
-                    }
-                }
-            }.bind(productAddToCartForm);
-
-            productAddToCartForm.submitLight = function(button, url) {
-                if (this.validator) {
-                    var nv = Validation.methods;
-                    delete Validation.methods['required-entry'];
-                    delete Validation.methods['validate-one-required'];
-                    delete Validation.methods['validate-one-required-by-name'];
-                    // Remove custom datetime validators
-                    for (var methodName in Validation.methods) {
-                        if (methodName.match(/^validate-datetime-.*/i)) {
-                            delete Validation.methods[methodName];
-                        }
-                    }
-
-                    if (this.validator.validate()) {
-                        if (url) {
-                            this.form.action = url;
-                        }
-                        this.form.submit();
-                    }
-                    Object.extend(Validation.methods, nv);
-                }
-            }.bind(productAddToCartForm);
-            //]]>
-        </script>
-    </div>
-
-    <div class="product-collateral">
-
-        <div class="product-info row">
-                                        <div class="col-sm-12 product-tabs">
-                    <div class="box-additional box-tabs">
-                        <div id="waveshare_tab_reference"></div>
-    <div id="product-tabs" class="ws-product-tabs">
-      <ul class="nav nav-tabs">
-        <li class="active" tab=description><a href="javascript:void(0);">Description</a></li><li tab=package_content><a href="javascript:void(0);">Package Content</a></li>                  <li tab='wiki'><a href="javascript:void(0);">Wiki</a></li> <!-- data-toggle="tab" -->
-              </ul>
-      <!-- 1 产品聚合页|DISCONTINUED|Disabled|Out of Stock等：无购物车 2 BACKORDER 3 Normal -->
-      <ul class="nav nav-tabs" id="waveshare_floatcart_link">
-      </ul>
-    </div>
-    <div class="tab-content" id="waveshare_product_content">
-        <div class="tab-section tab-pane active" id="tab-description">    <h2>Details</h2>
-    <div class="std">
-        <div class="overviewSec">ESP32-S3 3.97inch e-Paper Development Board, 800 × 480 Resolution, Supports Wi-Fi / BLE 5, And AI Voice Interaction, Onboard Microphone</div>
-	<div class="richWrap">
-		<div class="pdT" style="background-color: #e4f1f9;">
-			<div class="richTitle">
-				ESP32-S3 <span style="color: #bf735b;">3.97inch</span> <br>
-				e-Paper Development Board
-			</div>
-			<p class="richDesc">
-				low power, wide viewing angle, paper-like effect without electricity
-			</p>
-			<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-1.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, front view">
-		</div>
-		<div class="pdT" style="background-color: #e4f1f9;">
-			<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-3.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, features">
-			<div><br></div>
-		</div>
-
-		<div class="pdT" style="background-color: #eff6fc;">
-			<div class="richTitle">Version options</div>
-			<div class="richGridWrap richGridWrap-3c richGridWrap-valignTop mgnTB">
-				<div>
-					<img class="round1234" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-2-3.jpg" alt="ESP32-S3-ePaper-3.97, Without Lithium Batt">
-					<p><strong>ESP32-S3-ePaper-3.97-EN</strong><br>
-						Without Lithium Batt
-					</p>
-				</div>
-				<div>
-					<img class="round1234" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-2-2.jpg" alt="ESP32-S3-ePaper-3.97-EN, Comes with a MX1.25 3.7V Lithium Batt">
-					<p><strong>ESP32-S3-ePaper-3.97</strong><br>
-						Comes with a MX1.25 3.7V Lithium Batt<br>
-					</p>
-				</div>
-				<div>
-					<img class="round1234" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-2-1.jpg" alt="ESP32-S3-ePaper-3.97, ESP32-S3-ePaper-3.97-Kit">
-					<p><strong>EESP32-S3-ePaper-3.97-Kit</strong><br>
-						Basic kit, equipped with a MX1.25 3.7V Lithium Batt, USB cable, 16GB TF card and card reader
-					</p>
-				</div>
-			</div>
-		</div>
-
-		<div class="pdT" style="background-color: #eff6fc;">
-			<div class="richTitle" style="color: #1497db;">Features</div>
-			<div class="alignl pdTRBL2">
-				<p>
-				<span>The <strong>ESP32-S3-ePaper-3.97</strong></span> is a high-performance, highly integrated microcontroller development board designed by Waveshare. Equipped with an ESP32-S3 microcontroller, supports dual-mode Wi-Fi and BLE communication. Onboard 3.97inch e-paper display, features ultra-low power consumption and ambient light readability, suitable for portable devices and long-Batt-life scenarios. Integrated with an RTC chip, SHTC3 temperature and humidity sensor, TF card slot, low-power audio codec chip circuit, and Lithium Batt recharge management circuit. It provides a flexible and reliable development platform for IoT terminals, electronic tags, portable displays, and other applications.
-				</p>
-				<ul>
-					<li>Adopts ESP32-S3R8 high-performance Xtensa 32-bit LX7 dual-core processor, up to 240MHz main frequency</li>
-					<li>Supports 2.4GHz Wi-Fi (802.11 b/g/n) and Bluetooth 5 (LE), with onboard antenna</li>
-					<li>Built-in 512KB Static RAM, 384KB ROM, with integrated 8MB PSRAM and external 16MB Flash</li>
-					<li>Onboard 3.97inch e-paper display, 800 × 480 resolution, features high contrast and wide viewing angle</li>
-					<li>Onboard audio codec chip, supports voice capture and playback, enabling AI voice interaction applications</li>
-					<li>Onboard QMI8658 6-axis IMU (3-axis accelerometer and 3-axis gyroscope) for detecting motion gestures, counting steps, etc.</li>
-					<li>Onboard PCF85063 RTC chip and SHTC3 temperature &amp; humidity sensor for accurate RTC management and environmental monitoring</li>
-					<li>Onboard TG28 power management chip, supports 3.7V MX1.25 Lithium Batt for uninterrupted power supply, with a reserved backup Batt header to ensure continuous RTC functionality during main Batt replacement</li>
-					<li>Adopts TG28 chip for efficient power management, supports multiple voltage outputs, Batt charging, Batt management, and Batt life optimization, etc.</li>
-					<li>Type-C port, improving device compatibility, easier to use</li>
-					<li>Onboard TF card slot for storage expansion and rapid data transfer, suitable for data logging, media playback, and other applications, simplifying circuit design</li>
-					<li>Onboard programmable PWR and BOOT side buttons for customized function development</li>
-				</ul>
-			</div>
-			<div><br></div>
-		</div>
-
-		<div class="pdT">
-			<div class="richTitle" style="color: #1497db;">Specifications</div>
-			<table class="tabSty-2 mgnTB alignc pdTRBL2">
-				<tbody>
-					<tr>
-						<th style="width: 25%; color: #1497db;">display panel</th>
-						<td width="25%">e-paper display</td>
-						<th width="30%" style="color: #1497db;">display color</th>
-						<td>black, white</td>
-					</tr>
-					<tr>
-						<th style="color: #1497db;">Operating voltage</th>
-						<td>3.3V</td>
-						<th style="color: #1497db;">grey scale</th>
-						<td>4</td>
-					</tr>
-					<tr>
-						<th style="color: #1497db;">Display size</th>
-						<td>86.40 × 51.84 (mm)</td>
-						<th style="color: #1497db;">full refresh time</th>
-						<td>3.5s</td>
-					</tr>
-					<tr>
-						<th style="color: #1497db;">resolution</th>
-						<td>800 × 480 pixels</td>
-						<th style="color: #1497db;">Fast refresh time</th>
-						<td>2.8s</td>
-					</tr>
-					<tr>
-						<th style="color: #1497db;">viewing angle</th>
-						<td>&gt;170°</td>
-						<th style="color: #1497db;">partial refresh time</th>
-						<td>0.6s</td>
-					</tr>
-					<tr>
-						<th style="color: #1497db;">Refresh power</th>
-						<td>&lt;40mW</td>
-						<th style="color: #1497db;">4 grayscale refresh time</th>
-						<td>3.5s</td>
-					</tr>
-				</tbody>
-			</table>
-		</div>
-
-		<div class="pdT">
-			<div class="richTitle" style="color: #1497db;">
-				Onboard audio codec chip
-			</div>
-			<p class="richDesc">
-				Supports high-quality audio processing, providing clear and high-quality <br>audio input and output
-			</p>
-			<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-5.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, onboard audio codec chip">
-			<img class="round1234" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-5-1.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, onboard audio codec chip">
-			<div><br><br></div>
-		</div>
-
-		<div class="pdT" style="background-color: #e9ecf1; ">
-			<div class="richTitle" style="color: #1497db;">
-				Supports AI Voice Interaction
-			</div>
-			<p class="richDesc">
-				Allows access to online large model platforms such as DeepSeek, Doubao, etc
-			</p>
-			<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-7.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, explains the process of AI speech interaction">
-		</div>
-
-		<div class="pdT" style="background-color: #e9ecf1; ">
-			<div class="richTitle" style="color: #1497db;">
-				Rotary switch for easier page turning
-			</div>
-			<p class="richDesc pdTRBL">
-				Adopts 3-way rotary navigation switch design to reduce repetitive tapping during long reading and browsing
-			</p>
-			<video autoplay playsinline="false" muted loop src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-9.mp4" style="object-fit: none;"></video>
-			<div><br><br></div>
-		</div>
-
-		<div class="pdT">
-			<div class="richTitle" style="color: #1497db;">
-				Application Scenarios
-			</div>
-			<p class="richDesc">
-				Suitable for Voice Interaction and e-Reader, etc
-			</p>
-			<div class="richGridWrap richGridWrap-2c richGridWrap-valignTop mgnTB alignc">
-					<div>
-						<img class="round1234" style="border: 1px solid #ccc;" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-11-1.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, Speech interaction">
-						<p style="font-weight: bold;">Voice Interaction</p>
-					</div>
-					<div>
-						<img class="round1234" style="border: 1px solid #ccc;" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-11-2.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, Supports e-readers">
-						<p style="font-weight: bold;">E-Reader</p>
-					</div>
-					<div>
-						<img class="round1234" style="border: 1px solid #ccc;" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-11-3.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, Electronic calendar">
-						<p style="font-weight: bold;">Electronic Calendar</p>
-					</div>
-					<div>
-						<img class="round1234" style="border: 1px solid #ccc;" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-11-4.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, Supports Weather forecast display">
-						<p style="font-weight: bold;">Weather Forecast Display</p>
-					</div>
-			</div>
-		</div>
-
-		<div class="pdT">
-			<div class="richTitle" style="color: #1497db;">
-				Function Overview
-			</div>
-			<div class="richGridWrap richGridWrap-2c richGridWrap-valignTop mgnTB alignc">
-					<div>
-						<img class="round1234" style="border: 1px solid #ccc;" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-13-1.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, Supports real-time temperature and humidity detection">
-						<p>Supports real-time temperature and humidity detection</p>
-					</div>
-					<div>
-						<img class="round1234" style="border: 1px solid #ccc;" src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-13-2.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, Supports selecting the corresponding time zone">
-						<p>Supports selecting the corresponding time zone</p>
-					</div>
-			</div>
-		</div>
-
-		<div class="pdT">
-			<div class="richTitle" style="color: #1497db;">Supports ESP-IDF, Arduino IDE</div>
-			<p class="richDesc" >
-				Comprehensive SDK, dev resources, and tutorials to help you easily get started
-			</p>
-			<img src="/img/devkit/general/dev_platforms/ESP-IDF.jpg" alt="ESP32-S3-ePaper-3.97, Supports ESP-IDF">
-			<img src="/img/devkit/general/dev_platforms/Arduino-IDE.jpg" alt="ESP32-S3-ePaper-3.97, Supports Arduino">
-			<div><br></div>
-		</div>
-
-		<div>
-			<div class="richTitle"  style="color: #1497db;">What's On Board</div>
-			<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper3.97-details-intro.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, detailed introduction">
-			<div class="richGridWrap richGridWrap-valignTop richGridWrap-2c alignl subBlock bgGrey">
-				<div>
-					<ol>
-						<li><strong>ESP32-S3-WROOM-1-N16R8</strong><br>
-							Wi-Fi and Bluetooth SoC, 240MHz operating frequency, with integrated 8MB Flash and 16MB PSRAM</li>
-						<li><strong>SHTC3 temperature and humidity sensor</strong><br>
-							provides ambient temperature and humidity measurement, enabling environmental monitoring function</li>
-						<li><strong>PCF85063</strong><br>
-							RTC chip with timekeeping function</li>
-						<li><strong>Rotary button</strong><br>
-							supports customizable button functions in three directions</li>
-						<li><strong>PWR button</strong><br>
-							enables power control via software configuration when using Lithium Batt for power supply </li>
-						<li><strong>BOOT button</strong><br>
-							press it when powering on to enter download mode</li>
-						<li><strong>NS4150B</strong><br>
-							Audio amplifier chip</li>
-						
-					</ol>
-				</div>
-				<div>
-					<ol start="8">
-						<li><strong>ES8311</strong><br>
-							low-power audio codec chip</li>
-						<li><strong>QMI8658</strong><br>
-							6-axis IMU includes a 3-axis gyroscope and a 3-axis accelerometer</li>
-						<li><strong>MX1.25 speaker header</strong></li>
-						<li><strong>MX1.25 RTC backup Batt header</strong><br>for powering the RTC when the main Lithium Batt is not connected</li>
-						<li><strong>MX1.25 Lithium Batt header</strong><br>
-							MX1.25 2PIN connector for connecting 3.7V Lithium Batt, supports charging and discharging</li>
-						<li><strong>3.97inch e-paper display interface</strong></li>
-						<li><strong>TG28</strong><br>
-							highly integrated power management chip</li>
-						<li><strong>Microphone</strong></li>
-						<li><strong>Type-C port</strong></li>
-						<li><strong>TF card slot</strong></li>
-					</ol>
-				</div>
-			</div>
-		</div>
-		<br>
-
-		<div class="pdT">
-			<div class="richTitle" style="color: #1497db;">Outline Dimensions</div>
-			<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-details-size.jpg" alt="ESP32-S3 3.97inch e-PaperDevelopment Board, outline dimensions">
-		</div>
-		<br>
-
-		<div>
-			<div class="richTitle">Resources &amp; Services</div>
-			<img src="/img/devkit/LCD/common/res_banner.png">
-			<div class="bgGrey"><strong>Wiki: </strong>
-				<a class="wikilink" href="http://docs.waveshare.com/ESP32-S3-ePaper-3.97" target="_blank">docs.waveshare.com/ESP32-S3-ePaper-3.97</a><br>
-			</div>
-		</div>
-	</div>    </div>
-</div><div class="tab-section tab-pane " id="tab-package_content">        <h2>Quick Overview</h2>
-    <div class="std">
-        <h2>ESP32-S3-ePaper-3.97-EN</h2>
-
-	<ol>
-		<li>ESP32-S3-ePaper-3.97-EN x1</li>
-		<li>8Ω 1W speaker x1</li>
-	</ol>
-	<div class="imgTextWrap">
-		<div>1
-			<a href="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-2.jpg">
-				<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-2_220.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-		<div>2
-			<a href="/img/devkit/general/speaker-8Ω1W-95mm-PH1.25-2PIN.jpg">
-				<img src="/img/devkit/general/speaker-8Ω1W-95mm-PH1.25-2PIN_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-	</div>
-	<div class="sep0px"></div>
-	
-	
-	<h2>ESP32-S3-ePaper-3.97</h2>
-	<!-- <div class="msg msg_warning">
-		* the MX1.25 3.7V Lithium Batt is optional.
-	</div> -->
-	<ol>
-		<li>ESP32-S3-ePaper-3.97 x1</li>
-		<li>8Ω 1W speaker x1</li>
-		<li>Lithium Batt x1</li>
-	</ol>
-	<div class="imgTextWrap">
-		<div>1
-			<a href="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-2.jpg">
-				<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-2_220.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-		<div>2
-			<a href="/img/devkit/general/speaker-8Ω1W-95mm-PH1.25-2PIN.jpg">
-				<img src="/img/devkit/general/speaker-8Ω1W-95mm-PH1.25-2PIN_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-		<div>3
-			<a href="/img/devkit/general/3.7V-1500mA-battery.jpg">
-				<img src="/img/devkit/general/3.7V-1500mA-battery_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-	</div>
-
-	<div class="sep0px"></div>
-
-	<h2>ESP32-S3-ePaper-3.97-Kit</h2>
-	<!-- <div class="msg msg_warning">
-		* the MX1.25 3.7V Lithium Batt is optional.
-	</div> -->
-	<ol>
-		<li>ESP32-S3-ePaper-3.97 x1</li>
-		<li>8Ω 1W speaker x1</li>
-		<li>USB Type-A to Type-C cable ~1m x1</li>
-		<li>16GB TF card x1</li>
-		<li>Card reader x1</li>
-		<li>Lithium Batt x1</li>
-	</ol>
-	<div class="imgTextWrap">
-		<div>1
-			<a href="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-2.jpg">
-				<img src="/img/devkit/LCD/ESP32-S3-ePaper-3.97/ESP32-S3-ePaper-3.97-2_220.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-		<div>2
-			<a href="/img/devkit/general/speaker-8Ω1W-95mm-PH1.25-2PIN.jpg">
-				<img src="/img/devkit/general/speaker-8Ω1W-95mm-PH1.25-2PIN_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-		<div>3
-			<a href="/img/devkit/general/USB-Type-A-to-Type-C-Cable-1m.jpg">
-				<img src="/img/devkit/general/USB-Type-A-to-Type-C-Cable-1m_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-		<div>4
-			<a href="/img/devkit/general/Micro-SD-Card.jpg">
-				<img src="/img/devkit/general/Micro-SD-Card_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-		<div>5
-			<a href="/img/devkit/general/Card-reader-blue.jpg">
-				<img src="/img/devkit/general/Card-reader-blue_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-
-		<div>6
-			<a href="/img/devkit/general/3.7V-1500mA-battery.jpg">
-				<img src="/img/devkit/general/3.7V-1500mA-battery_93.jpg" alt="ESP32-S3-ePaper-3.97">
-			</a>
-		</div>
-	</div>    </div>
-</div>    </div>
-    <div id="waveshare_tabbar" class="wavesahre-tabbar-bg" style="display: none;"></div>
-    <script type="text/javascript">
-    //<![CDATA[
-    var crosssell_slider;
-    var is_mobile = '1';
-    var clickCount = 1;
-    // console.log(new Date(), 1);
-    
-    function getElementLeft(element){
-　　　　var actualLeft = element.offsetLeft;
-　　　　var current = element.offsetParent;
-
-　　　　while (current !== null){
-　　　　　　actualLeft += current.offsetLeft;
-　　　　　　current = current.offsetParent;
-　　　　}
-　　　　return actualLeft;
-　　}
-   
-jQuery(function($) {
-    var wikiHeight = 0;
-    if (!is_mobile) {
-       $('#waveshare_product_content .tab-section').css({ 'border-top': "0" });
-    } else {
-       $('#waveshare_product_content .tab-section').css({ 'border-left': "0", 'border-right': "0", 'padding-left': "0", 'padding-right': "0", "overflow": "auto"});
-    }
-    $('#waveshare_floatcart_link').hide();
-    function setwidth(){
-        if (is_mobile) {
-            $('#product-tabs').width($(window).width());
-        }else{
-            $('#product-tabs').width($('#product-tabs').parent().width() - 2);
-        }
-    }
-    setwidth();
-    $(window).scroll(() => {
-      initStyle();
-    });
-    function initStyle() {
-      if ($(window).scrollTop() >= $('#waveshare_tab_reference').offset().top) { // 浮层
-          $('#waveshare_tabbar').show();
-          $('#product-tabs').addClass('waveshare_tab');
-          $('#waveshare_floatcart_link').show();
-        } else { // 非浮层
-          $('#waveshare_tabbar').hide();
-          $('#product-tabs').removeClass('waveshare_tab');
-          $('#waveshare_floatcart_link').hide();
-        }
-    }
-    
-    initStyle();
-    $('#product-tabs li').unbind('click').click(function() {
-      var tab = $(this).attr('tab');
-      var oldTab = $('#product-tabs .active').attr('tab');
-      var isFlow = $('#product-tabs').hasClass('waveshare_tab');
-      console.log('oldTab:', oldTab, 'tab:', tab);
-      $('#waveshare_product_content .tab-section').hide();
-      var tab_id = '#tab-'+tab;
-      if (tab == 'wiki') {
-        tab_id = '#tab-description';
-      }
-      $(tab_id).show();
-      $('#product-tabs li').removeClass('active');
-      $(this).addClass('active');
-      
-      setTimeout(() => {
-        var toHeight = $('#waveshare_tab_reference').offset().top;
-        if (tab == 'wiki') {
-          toHeight = $('#tab-wiki').offset().top - 50; // wikiHeight;
-          if (!isFlow) {
-            toHeight -= 43.5;
-          }
-        }
-        console.log('currHeight:'+$(window).scrollTop()+' toHeight:'+toHeight);
-        scrollToSpecifiedHeight(toHeight);
-      }, 100);
-    })
-
-    function scrollToSpecifiedHeight(height) {
-      window.scrollTo({
-        top: height,
-        behavior: 'smooth' // 平滑滚动
-      });
-    }
-    
-
-  function newCartDiv(isShow = false) {
-    if (isShow === false) {
-        $('#waveshare_floatcart_link').hide();
-        return false;
-    }
-    if ($('#product-addtocart-button')[0]) { // 如果页面存在cart button时
-      addClassName = ""
-      buttonName = "Add to Cart"
-      if ($('#product-addtocart-button').hasClass("waveshare_backorders")) {
-        addClassName = "waveshare_backorders"
-        buttonName = "Backorder"
-      }
-      $('#waveshare_floatcart_link').html('<li><button type="button" title="Add to Cart" class="button d-flex align-content-center '+addClassName+'" onclick="productAddToCartForm.submit(this)"><i class="icon-mycart-white"></i><span class=" visible-md visible-lg">'+buttonName+'</span></button></li>');
-    }
-  }
-  newCartDiv(true);
-
-  // add tab-wiki
-  $('#tab-description a').each((index, e)=>{
-    if(e.href.includes('//www.waveshare.com/wiki/') || $(e).hasClass('wikilink')) {
-      $('#tab-description a').eq(index).attr('id', 'tab-wiki');
-      wikiHeight = $('#tab-wiki').offset().top - 50;
-      console.log('wikiHeight:'+wikiHeight);
-    }
-  });
-});
-    
-    //]]>    
-    </script>
-<style type="text/css">
-</style>                    </div>
-                </div>
-                        <script type="text/javascript">
-                //<![CDATA[
-                jQuery(function($) {
-                    var venedor_product_timer;
-
-                    function venedor_product_resize() {
-                        if (VENEDOR_RESPONSIVE) {
-                            var winWidth = $(window).innerWidth();
-
-                                                    }
-                        if (venedor_product_timer) clearTimeout(venedor_product_timer);
-                    }
-
-                    $("#goto-reviews, #goto-reviews-form").click(function() {
-                        $("#product-tabs #tab-tabreviews").click();
-                    });
-
-                    $(window).load(venedor_product_resize);
-
-                    $(window).resize(function() {
-                        clearTimeout(venedor_product_timer);
-                        venedor_product_timer = setTimeout(venedor_product_resize, 200);
-                    });
-
-                    function getCanSelectedAttributes(index) {
-                        var canSelectedAttributes = [];
-                        for (k = 0; k < waveshare_sku_attributes.length; k++) {
-                            var attributes = waveshare_sku_attributes[k].attributes;
-
-                            var flag = true;
-                            for (kk = 0; kk < attributes.length; kk++) {
-                                var attribute = attributes[kk];
-                                if (index != kk && waveshare_selected_attributes[kk] && waveshare_selected_attributes[kk] != attribute) {
-                                    flag = false;
-                                }
-                            }
-
-                            currAttribute = attributes[index];
-                            if (flag && !canSelectedAttributes.includes(currAttribute)) {
-                                canSelectedAttributes.push(currAttribute);
-                            }
-                        }
-                        // console.log(waveshare_selected_attributes, waveshare_sku_attributes, index);
-                        return canSelectedAttributes;
-                    }
-
-                    // add by libearxiong 20260530 基于当前已选属性，计算某个set index下哪些选项应该被禁用
-                    // 逻辑：在当前已选属性约束下，找出所有匹配的SKU，如果某选项值对应的所有匹配SKU都是unsaleable，则禁用
-                    function getDisabledAttributes(index) {
-                        var disabledMap = {}; // {attributeValue: {total: n, unsaleableCount: n}}
-                        for (var k = 0; k < waveshare_sku_attributes.length; k++) {
-                            var attributes = waveshare_sku_attributes[k].attributes;
-                            var unsaleable = waveshare_sku_attributes[k].unsaleable;
-
-                            // 检查该SKU是否匹配当前已选的其他属性（排除当前index）
-                            var flag = true;
-                            for (var kk = 0; kk < attributes.length; kk++) {
-                                if (index != kk && waveshare_selected_attributes[kk] && waveshare_selected_attributes[kk] != attributes[kk]) {
-                                    flag = false;
-                                    break;
-                                }
-                            }
-
-                            if (flag) {
-                                var currAttribute = attributes[index];
-                                if (!disabledMap[currAttribute]) {
-                                    disabledMap[currAttribute] = {total: 0, unsaleableCount: 0};
-                                }
-                                disabledMap[currAttribute].total++;
-                                if (unsaleable) {
-                                    disabledMap[currAttribute].unsaleableCount++;
-                                }
-                            }
-                        }
-                        // 返回所有匹配SKU全部unsaleable的选项值列表
-                        var disabledAttributes = [];
-                        for (var attr in disabledMap) {
-                            if (disabledMap[attr].total > 0 && disabledMap[attr].total === disabledMap[attr].unsaleableCount) {
-                                disabledAttributes.push(attr);
-                            }
-                        }
-                        return disabledAttributes;
-                    }
-
-                    // product_set
-                    $('#waveshare_options .goods-detail-line .goods').click(function() {
-                        // add by libearxiong 20260530 禁用的选项不可点击
-                        if ($(this).hasClass('disabled_goods')) {
-                            return false;
-                        }
-                        var attribute = $(this).text();
-                        var index = $(this).attr('setIndex') * 1;
-                        var type = '';
-                        if ($(this).hasClass('has_goods')) {
-                            type = 'add';
-                            waveshare_selected_attributes[index] = attribute;
-                            const sku = waveshare_attributes2sku[waveshare_selected_attributes.join(',')];
-                            // console.log(waveshare_selected_attributes, sku);
-                            if (sku && (sku_init * 1 != sku * 1)) {
-                                window.location.href = _product_url + '?sku=' + sku;
-                            }
-                        } else if ($(this).hasClass('current_goods')) {
-                            waveshare_selected_attributes[index] = null;
-                            type = 'remove';
-                        } else {
-                            return false;
-                        }
-
-                        // 处理Sets
-                        var allSets = $('#waveshare_options .goods-detail-line');
-                        for (i = 0; i < allSets.length; i++) {
-                            someSet = allSets.eq(i);
-                            allAttributes = someSet.find('.goods');
-                            var canSelectedAttributes = getCanSelectedAttributes(i);
-                            var disabledAttributes = getDisabledAttributes(i);
-                            console.log('canSelectedAttributes', canSelectedAttributes, 'disabledAttributes', disabledAttributes);
-                            for (j = 0; j < allAttributes.length; j++) {
-                                someAttribute = allAttributes.eq(j);
-                                if (i === index) { // 当前点击的set
-                                    if (someAttribute.hasClass('current_goods')) {
-                                        someAttribute.removeClass('current_goods').addClass('has_goods');
-                                    }
-                                } else { // 非当前点击的set
-                                    if (!someAttribute.hasClass('current_goods')) { // 只处理非当前选中节点
-                                        var sAttribute = someAttribute.text();
-                                        // 先判断是否应该禁用
-                                        if (disabledAttributes.includes(sAttribute)) {
-                                            someAttribute.removeClass('has_goods').removeClass('no_goods').removeClass('disabled_goods').addClass('disabled_goods');
-                                        } else if (canSelectedAttributes.includes(sAttribute)) {
-                                            someAttribute.removeClass('has_goods').removeClass('no_goods').removeClass('disabled_goods').addClass('has_goods');
-                                        } else {
-                                            someAttribute.removeClass('has_goods').removeClass('no_goods').removeClass('disabled_goods').addClass('no_goods');
-                                        }
-                                    }
-                                }
-                            }
-                        }
-
-                        if (type == 'add') {
-                            $(this).removeClass('has_goods').addClass('current_goods');
-                        }
-                    })
-
-                    // add by libearxiong 20260530 集中页自动选择：如果某个set只有一个可点击选项，则自动选中
-                    if (waveshare_is_product_set_page == 0 && waveshare_sku_attributes) {
-                        autoSelectSingleOptions();
-                    }
-
-                    function autoSelectSingleOptions() {
-                        var allSets = $('#waveshare_options .goods-detail-line');
-                        var hasAutoSelected = false;
-                        for (var i = 0; i < allSets.length; i++) {
-                            if (waveshare_selected_attributes[i]) continue; // 已经选中了，跳过
-                            var disabledAttributes = getDisabledAttributes(i);
-                            var canSelectedAttributes = getCanSelectedAttributes(i);
-                            // 可点击的选项 = 可选且非禁用
-                            var clickableAttributes = [];
-                            for (var j = 0; j < canSelectedAttributes.length; j++) {
-                                if (!disabledAttributes.includes(canSelectedAttributes[j])) {
-                                    clickableAttributes.push(canSelectedAttributes[j]);
-                                }
-                            }
-                            if (clickableAttributes.length === 1) {
-                                // 自动选中该选项
-                                waveshare_selected_attributes[i] = clickableAttributes[0];
-                                hasAutoSelected = true;
-                                // 更新UI：找到对应的DOM元素加上current_goods
-                                var allAttributes = allSets.eq(i).find('.goods');
-                                allAttributes.each(function() {
-                                    if ($(this).text() === clickableAttributes[0]) {
-                                        $(this).removeClass('has_goods').addClass('current_goods');
-                                    }
-                                });
-                            }
-                        }
-                        if (hasAutoSelected) {
-                            // 重新计算所有set的状态
-                            for (var i = 0; i < allSets.length; i++) {
-                                var allAttributes = allSets.eq(i).find('.goods');
-                                var canSelectedAttributes = getCanSelectedAttributes(i);
-                                var disabledAttributes = getDisabledAttributes(i);
-                                for (var j = 0; j < allAttributes.length; j++) {
-                                    var someAttribute = allAttributes.eq(j);
-                                    if (!someAttribute.hasClass('current_goods')) {
-                                        var sAttribute = someAttribute.text();
-                                        if (disabledAttributes.includes(sAttribute)) {
-                                            someAttribute.removeClass('has_goods').removeClass('no_goods').removeClass('disabled_goods').addClass('disabled_goods');
-                                        } else if (canSelectedAttributes.includes(sAttribute)) {
-                                            someAttribute.removeClass('has_goods').removeClass('no_goods').removeClass('disabled_goods').addClass('has_goods');
-                                        } else {
-                                            someAttribute.removeClass('has_goods').removeClass('no_goods').removeClass('disabled_goods').addClass('no_goods');
-                                        }
-                                    }
-                                }
-                            }
-                            // 递归：可能自动选择后又有新的set只剩一个可选
-                            autoSelectSingleOptions();
-                            // 检查是否所有属性都已选中，如果是则跳转
-                            var allSelected = true;
-                            for (var i = 0; i < waveshare_selected_attributes.length; i++) {
-                                if (!waveshare_selected_attributes[i]) {
-                                    allSelected = false;
-                                    break;
-                                }
-                            }
-                            if (allSelected) {
-                                var sku = waveshare_attributes2sku[waveshare_selected_attributes.join(',')];
-                                if (sku) {
-                                    window.location.href = _product_url + '?sku=' + sku;
-                                }
-                            }
-                        }
-                    }
-                });
-
-                // add by libearxiong 20170408
-                if ($('choose')) {
-                    var img_size = ($('choose').getWidth() - 70) / 5;
-                    img_size = document.body.clientWidth > 1280 ? 66 : img_size; // add by libearxiong 20200606
-                    $$('.img_size').each(function(e) {
-                        e.height = img_size;
-                        e.width = img_size;
-                    })
-                }
-
-                //]]>
-            </script>
-        </div>
-        <!-- 删除upsell模块-Related Products -->
-        
-        
-    </div>
-</div>
-<link rel="stylesheet" type="text/css" href="/skin/frontend/venedor/default/css/waveshare/plus.css" />
-<div id="history-price" style="display: none;" class="history-price">
-    <div role="dialog" aria-modal="true" class="el-dialog el-dialog--center" style="width: 400px;">
-        <div class="el-dialog__header">
-            <span class="el-dialog__title title">xxxxxx</span>
-            <button type="button" aria-label="Close" class="el-dialog__headerbtn"><i class="el-dialog__close el-icon el-icon-close"></i></button>
-        </div>
-        <div class="el-dialog__body">
-            <span>History Price</span>
-        </div>
-        <div class="history_line"></div>
-        <div class="type">
-            <div>Retail Price:</div>
-            <ul class="retail" style="padding-left:40px;">
-            </ul>
-        </div>
-        <div class="history_line"></div>
-        <div class="type">
-            <div>Distributor Price:</div>
-            <ul class="agency" style="padding-left:40px;">
-            </ul>
-        </div>
-        <div class="history_line"></div>
-        <div class="el-dialog__footer">
-            <a href="javascript:void(0)" onclick="showDialog.hide()" class="btn btn_c"><span>confirm</span></a>
-        </div>
-    </div>
-</div>
-<style type="text/css">
-    .waveshare_view_relate .old-price .price {
-        text-decoration: auto !important;
-    }
-
-    .product-log-price .toolbar {
-        border-bottom-width: 0px !important;
-        margin-bottom: 10px;
-    }
-
-    .product-log-price .toolbar .submit {
-        background-color: #7bae23;
-        border-color: #7bae23;
-        color: #ffffff;
-    }
-
-    .product-log-price .toolbar .submit:hover {
-        color: #ffffff;
-        -webkit-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.2) inset, 0 1px 2px rgba(0, 0, 0, 0.05);
-        -moz-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.2) inset, 0 1px 2px rgba(0, 0, 0, 0.05);
-        box-shadow: 0 1px 0 rgba(255, 255, 255, 0.2) inset, 0 1px 2px rgba(0, 0, 0, 0.05);
-        border-color: #84bb26;
-        background-color: #84bb26;
-    }
-
-    .product-log-price .retail {
-        padding: auto;
-    }
-
-    .el-dialog {
-        position: relative;
-        margin: 0 auto 50px;
-        background: #fff;
-        border-radius: 2px;
-        box-shadow: 0 1px 3px rgba(0, 0, 0, .3);
-        box-sizing: border-box;
-        width: 50%;
-    }
-
-    .el-dialog--center {
-        text-align: center;
-    }
-
-    .el-dialog__header {
-        padding: 20px 20px 10px;
-    }
-
-    .el-dialog__title {
-        line-height: 24px;
-        font-size: 22px;
-        color: #303133;
-    }
-
-    .el-dialog__headerbtn {
-        position: absolute;
-        top: 20px;
-        right: 20px;
-        padding: 0;
-        background: transparent;
-        border: none;
-        outline: none;
-        cursor: pointer;
-        font-size: 16px;
-    }
-
-    .el-dialog__footer {
-        padding: 10px 20px 20px;
-        text-align: right;
-        box-sizing: border-box;
-    }
-
-    .history_line {
-        line-height: 1.4;
-        margin-bottom: 10px;
-        margin-top: 10px;
-        padding-bottom: 1px;
-        border-bottom: 1px solid #ccc;
-        width: 90%;
-        position: relative;
-        left: 5%;
-    }
-
-    .history-price .type {
-        text-align: left;
-        position: relative;
-        left: 5%;
-    }
-
-    #history-price .el-icon-close:before {
-        content: "";
-    }
-
-    #history-price .el-dialog__body {
-        text-align: center;
-        padding: 0;
-    }
-</style>
-<script type="text/javascript" src="/js/eternal/jquery/showDialog.min.js"></script>
-<script>
-    jQuery(function() {
-        jQuery('.viewProduct').click(function() {
-            var product_id = jQuery(this).attr('product_id');
-            var product_name = jQuery(this).attr('product_name');
-            jQuery.getJSON("/customer/account/getProductHistoryPrice?product_id=" + product_id, function(res) {
-                if (res['code'] !== 0) {
-                    jQuery('#history-price .title').text('Error');
-                    showDialog.show({
-                        id: "history-price",
-                        bgcolor: '#e0e0e0',
-                        opacity: 70
-                    });
-                    return false;
-                }
-                var retail = [];
-                for (var i = 0; i < res.retail.length; i++) {
-                    var obj = res.retail[i];
-                    var html = '<li>' + obj.date + ' ---- $' + obj.value;
-                    retail.push(html + '</li>')
-                }
-
-                maxId = 1000000000;
-                for (var i = 0; i < res.agency.length; i++) {
-                    var obj = res.agency[i];
-                    if (obj.value_plus == 'discount cancelled') {
-                        maxId = obj.id;
-                    } else {
-                        break;
-                    }
-                }
-                var agency = [];
-                for (var i = 0; i < res.agency.length; i++) {
-                    var obj = res.agency[i];
-                    if (obj.id <= maxId) {
-                        var html = '<li>' + obj.date + ' ---- ' + (obj.value_plus == 'discount cancelled' ? '' : '$') + obj.value_plus;
-                        agency.push(html + '</li>')
-                    }
-                }
-                jQuery('#history-price .title').text(product_name);
-                jQuery('#history-price .retail').html(retail.join(''));
-                jQuery('#history-price .agency').html(agency.join(''));
-                showDialog.show({
-                    id: "history-price",
-                    bgcolor: '#e0e0e0',
-                    opacity: 70
-                });
-            });
-        })
-    })
-</script>
-<script type="text/javascript">
-    var lifetime = 3600;
-    var expireAt = Mage.Cookies.expires;
-    if (lifetime > 0) {
-        expireAt = new Date();
-        expireAt.setTime(expireAt.getTime() + lifetime * 1000);
-    }
-    Mage.Cookies.set('external_no_cache', 1, expireAt);
-</script>
-                                            </div>
-                                        <div class="col-lg-2 hidden-md hidden-sm sidebar sidebar-left waveshare-sidebar-comm">
-                        <nav id="mysidebarmenu1" class="amazonmenu">
- 
-
-
- 
-<!--</h4>-->
-<!--</div>--><!--End Of head-->
- 
-<h4 class="no-display">
-Category Navigation:</h4>
-  <!-- nav class="amazonmenu" -->
-<nav id="mysidebarmenu" class="amazonmenu">
-<ul>
-<li class="level0 nav-1 first last parent">
-<a href="https://www.waveshare.com/product.htm">
-<span>Products</span>
-</a>
-<ul class="level0">
-<li class="level1 nav-1-1 first parent">
-<a href="https://www.waveshare.com/product/raspberry-pi.htm">
-<span>Raspberry Pi</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-1-1 first parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-1-1 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-5.htm">
-<span>Raspberry Pi 5</span>
-</a>
-</li><li class="level3 nav-1-1-1-2">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-4.htm">
-<span>Raspberry Pi 4</span>
-</a>
-</li><li class="level3 nav-1-1-1-3">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-3.htm">
-<span>Raspberry Pi 3</span>
-</a>
-</li><li class="level3 nav-1-1-1-4">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-400.htm">
-<span>Raspberry Pi 400</span>
-</a>
-</li><li class="level3 nav-1-1-1-5">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-zero-2-w-cat.htm">
-<span>Raspberry Pi Zero 2 W</span>
-</a>
-</li><li class="level3 nav-1-1-1-6">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-zero.htm">
-<span>Raspberry Pi Zero</span>
-</a>
-</li><li class="level3 nav-1-1-1-7">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-pico-cat.htm">
-<span>Raspberry Pi Pico</span>
-</a>
-</li><li class="level3 nav-1-1-1-8">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/compute-module-4-4s-cat.htm">
-<span>Compute Module 4/4S</span>
-</a>
-</li><li class="level3 nav-1-1-1-9">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/compute-module.htm">
-<span>Compute Module 3</span>
-</a>
-</li><li class="level3 nav-1-1-1-10">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-pico-13.htm">
-<span>Raspberry Pi Pico 2</span>
-</a>
-</li><li class="level3 nav-1-1-1-11">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/cm5.htm">
-<span>Compute Module 5</span>
-</a>
-</li><li class="level3 nav-1-1-1-12 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/boards-kits/raspberry-pi-500-and-kits.htm">
-<span>Raspberry Pi 500</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-2 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-2-13 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays/lcd-oled.htm">
-<span>LCD</span>
-</a>
-</li><li class="level3 nav-1-1-2-14">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays/oled.htm">
-<span>OLED</span>
-</a>
-</li><li class="level3 nav-1-1-2-15 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-3 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-3-16 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/10mp-pixels.htm">
-<span>≥10MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-17">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/8m-pixels.htm">
-<span>8MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-18">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/5m-pixels.htm">
-<span>5MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-19">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/2m-pixels.htm">
-<span>2MP Rolling Shutter</span>
-</a>
-</li><li class="level3 nav-1-1-3-20">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/global-shutter-cameras.htm">
-<span>Global Shutter Cameras</span>
-</a>
-</li><li class="level3 nav-1-1-3-21">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/usb-cameras.htm">
-<span>USB Cameras</span>
-</a>
-</li><li class="level3 nav-1-1-3-22">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/ai-cameras.htm">
-<span>AI Cameras</span>
-</a>
-</li><li class="level3 nav-1-1-3-23 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/cameras/gmsl-cameras.htm">
-<span>GMSL Cameras</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-4 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats.htm">
-<span>HATs</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-4-24 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/iot.htm">
-<span>IoT</span>
-</a>
-</li><li class="level3 nav-1-1-4-25">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/interface-power.htm">
-<span>Interface / Expansion / Power</span>
-</a>
-</li><li class="level3 nav-1-1-4-26">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/motors-relays.htm">
-<span>Motors / Relays / SCR</span>
-</a>
-</li><li class="level3 nav-1-1-4-27">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/ad-da-audio-sensors.htm">
-<span>AD / DA / Audio / Sensors</span>
-</a>
-</li><li class="level3 nav-1-1-4-28">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/led-buttons.htm">
-<span>LED / Buttons</span>
-</a>
-</li><li class="level3 nav-1-1-4-29 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/hats/versatile.htm">
-<span>Versatile</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-5 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/laptop.htm">
-<span>All-in-one</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-5-30 first last">
-<a href="https://www.waveshare.com/product/raspberry-pi/laptop/all-in-one.htm">
-<span>Magic Mirror / All-in-one</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-6">
-<a href="https://www.waveshare.com/product/raspberry-pi/homelab.htm">
-<span>HomeLab</span>
-</a>
-</li><li class="level2 nav-1-1-7 parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-7-31 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/robots/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-</li><li class="level3 nav-1-1-7-32 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/robots/robot-arm-control.htm">
-<span>Robot Arm / Control</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-1-8">
-<a href="https://www.waveshare.com/product/raspberry-pi/portable-gaming.htm">
-<span>Portable Gaming</span>
-</a>
-</li><li class="level2 nav-1-1-9 last parent">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-1-9-33 first">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories/pi-cases.htm">
-<span>Pi Cases</span>
-</a>
-</li><li class="level3 nav-1-1-9-34">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories/display-cases.htm">
-<span>Display Cases</span>
-</a>
-</li><li class="level3 nav-1-1-9-35 last">
-<a href="https://www.waveshare.com/product/raspberry-pi/accessories/wires-power-sd-card.htm">
-<span>Wires / Power / SD Card...</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-2 parent">
-<a href="https://www.waveshare.com/product/ai.htm">
-<span>AI</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-2-10 first parent">
-<a href="https://www.waveshare.com/product/ai/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-10-36 first">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-nano.htm">
-<span>Jetson Nano</span>
-</a>
-</li><li class="level3 nav-1-2-10-37">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-tx2.htm">
-<span>Jetson TX2</span>
-</a>
-</li><li class="level3 nav-1-2-10-38">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-xavier-nx-cata.htm">
-<span>Jetson Xavier NX</span>
-</a>
-</li><li class="level3 nav-1-2-10-39">
-<a href="https://www.waveshare.com/product/ai/boards-kits/jetson-orin.htm">
-<span>Jetson Orin</span>
-</a>
-</li><li class="level3 nav-1-2-10-40">
-<a href="https://www.waveshare.com/product/ai/boards-kits/ai-cameras.htm">
-<span>AI Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-10-41">
-<a href="https://www.waveshare.com/product/ai/boards-kits/ops-computer.htm">
-<span>OPS Computer</span>
-</a>
-</li><li class="level3 nav-1-2-10-42">
-<a href="https://www.waveshare.com/product/ai/boards-kits/raspberry-pi.htm">
-<span>Raspberry Pi</span>
-</a>
-</li><li class="level3 nav-1-2-10-43">
-<a href="https://www.waveshare.com/product/ai/boards-kits/d-robotics.htm">
-<span>D-Robotics</span>
-</a>
-</li><li class="level3 nav-1-2-10-44 last">
-<a href="https://www.waveshare.com/product/ai/boards-kits/luckfox.htm">
-<span>Luckfox</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-11 parent">
-<a href="https://www.waveshare.com/product/ai/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-11-45 first">
-<a href="https://www.waveshare.com/product/ai/displays/lcd-oled.htm">
-<span>LCD</span>
-</a>
-</li><li class="level3 nav-1-2-11-46">
-<a href="https://www.waveshare.com/product/ai/displays/oled.htm">
-<span>OLED</span>
-</a>
-</li><li class="level3 nav-1-2-11-47 last">
-<a href="https://www.waveshare.com/product/ai/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-12 parent">
-<a href="https://www.waveshare.com/product/ai/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-12-48 first">
-<a href="https://www.waveshare.com/product/ai/cameras/single-cameras.htm">
-<span>Single Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-49">
-<a href="https://www.waveshare.com/product/ai/cameras/binocular-cameras.htm">
-<span>Binocular Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-50">
-<a href="https://www.waveshare.com/product/ai/cameras/ai-usb-cameras.htm">
-<span>USB Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-51">
-<a href="https://www.waveshare.com/product/ai/cameras/gmsl-cameras.htm">
-<span>GMSL Cameras</span>
-</a>
-</li><li class="level3 nav-1-2-12-52 last">
-<a href="https://www.waveshare.com/product/ai/cameras/others.htm">
-<span>Others</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-13 parent">
-<a href="https://www.waveshare.com/product/ai/expansions.htm">
-<span>Expansions</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-13-53 first">
-<a href="https://www.waveshare.com/product/ai/expansions/iot.htm">
-<span>IoT</span>
-</a>
-</li><li class="level3 nav-1-2-13-54">
-<a href="https://www.waveshare.com/product/ai/expansions/motors-relays.htm">
-<span>Motors / Relays / SCR</span>
-</a>
-</li><li class="level3 nav-1-2-13-55">
-<a href="https://www.waveshare.com/product/ai/expansions/ad-da-versatile.htm">
-<span>AD / DA / Versatile</span>
-</a>
-</li><li class="level3 nav-1-2-13-56 last">
-<a href="https://www.waveshare.com/product/ai/expansions/power-supply.htm">
-<span>Power Supply</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-14 parent">
-<a href="https://www.waveshare.com/product/ai/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-14-57 first">
-<a href="https://www.waveshare.com/product/ai/robots/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-</li><li class="level3 nav-1-2-14-58 last">
-<a href="https://www.waveshare.com/product/ai/robots/robot-arm-control.htm">
-<span>Robot Arm / Control</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-2-15 last parent">
-<a href="https://www.waveshare.com/product/ai/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-2-15-59 first">
-<a href="https://www.waveshare.com/product/ai/accessories/cases.htm">
-<span>Cases</span>
-</a>
-</li><li class="level3 nav-1-2-15-60 last">
-<a href="https://www.waveshare.com/product/ai/accessories/wires-power-sd-card.htm">
-<span>Wires / Power / SD Card...</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-3 parent">
-<a href="https://www.waveshare.com/product/luckfox.htm">
-<span>Luckfox</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-3-16 first parent">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules.htm">
-<span>Linux Boards / Modules</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-3-16-61 first">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/core3576.htm">
-<span>Omni3576-RK3576</span>
-</a>
-</li><li class="level3 nav-1-3-16-62">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-lyra-23.htm">
-<span>Luckfox Lyra-RK3506</span>
-</a>
-</li><li class="level3 nav-1-3-16-63">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-pico-core1106.htm">
-<span>LuckFox Pico-RV1106</span>
-</a>
-</li><li class="level3 nav-1-3-16-64">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-aura-rv1126.htm">
-<span>Luckfox Aura-RV1126</span>
-</a>
-</li><li class="level3 nav-1-3-16-65">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/core3566-9.htm">
-<span>Core3566-RK3566</span>
-</a>
-</li><li class="level3 nav-1-3-16-66 last">
-<a href="https://www.waveshare.com/product/luckfox/boards-modules/luckfox-lume-t153.htm">
-<span>LuckFox Lume-T153</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-3-17 parent">
-<a href="https://www.waveshare.com/product/luckfox/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-3-17-67 first last">
-<a href="https://www.waveshare.com/product/luckfox/displays/lcd-oled.htm">
-<span>LCD/OLED</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-3-18 last parent">
-<a href="https://www.waveshare.com/product/luckfox/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-3-18-68 first">
-<a href="https://www.waveshare.com/product/luckfox/cameras/3mp-cameras.htm">
-<span>3MP Cameras</span>
-</a>
-</li><li class="level3 nav-1-3-18-69">
-<a href="https://www.waveshare.com/product/luckfox/cameras/8mp-cameras.htm">
-<span>8MP Cameras</span>
-</a>
-</li><li class="level3 nav-1-3-18-70">
-<a href="https://www.waveshare.com/product/luckfox/cameras/5mp-cameras.htm">
-<span>5MP Cameras</span>
-</a>
-</li><li class="level3 nav-1-3-18-71 last">
-<a href="https://www.waveshare.com/product/luckfox/cameras/1mp-cameras.htm">
-<span>1MP Cameras</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-4 parent">
-<a href="https://www.waveshare.com/product/risc-v.htm">
-<span>RISC-V</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-4-19 first parent">
-<a href="https://www.waveshare.com/product/risc-v/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-19-72 first">
-<a href="https://www.waveshare.com/product/risc-v/boards-kits/visionfive2.htm">
-<span>VisionFive2</span>
-</a>
-</li><li class="level3 nav-1-4-19-73 last">
-<a href="https://www.waveshare.com/product/risc-v/boards-kits/visionfive2-lite-7832.htm">
-<span>VisionFive2 Lite</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-4-20 parent">
-<a href="https://www.waveshare.com/product/risc-v/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-20-74 first last">
-<a href="https://www.waveshare.com/product/risc-v/displays/lcd.htm">
-<span>LCD</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-4-21 parent">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories.htm">
-<span>Expansions / Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-21-75 first">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories/audio-sensors.htm">
-<span>Audio / Sensors</span>
-</a>
-</li><li class="level3 nav-1-4-21-76">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories/relays-motors-servos.htm">
-<span>Relays / Motors / Servos</span>
-</a>
-</li><li class="level3 nav-1-4-21-77 last">
-<a href="https://www.waveshare.com/product/risc-v/expansions-accessories/cooling-fan.htm">
-<span>Cooling Fan</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-4-22 last parent">
-<a href="https://www.waveshare.com/product/risc-v/cameras.htm">
-<span>Cameras</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-4-22-78 first last">
-<a href="https://www.waveshare.com/product/risc-v/cameras/8mp-imx219-cameras.htm">
-<span>8MP IMX219 Cameras</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-5 parent">
-<a href="https://www.waveshare.com/product/esp32-related.htm">
-<span>ESP32</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-5-23 first parent">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits.htm">
-<span>Boards / Kits</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-5-23-79 first">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-p4.htm">
-<span>ESP32-P4</span>
-</a>
-</li><li class="level3 nav-1-5-23-80">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-s3.htm">
-<span>ESP32-S3</span>
-</a>
-</li><li class="level3 nav-1-5-23-81">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-c6.htm">
-<span>ESP32-C6</span>
-</a>
-</li><li class="level3 nav-1-5-23-82">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-c5.htm">
-<span>ESP32-C5</span>
-</a>
-</li><li class="level3 nav-1-5-23-83">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-c3.htm">
-<span>ESP32-C3</span>
-</a>
-</li><li class="level3 nav-1-5-23-84">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-h2.htm">
-<span>ESP32-H2</span>
-</a>
-</li><li class="level3 nav-1-5-23-85">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-s2-1.htm">
-<span>ESP32-S2</span>
-</a>
-</li><li class="level3 nav-1-5-23-86 last">
-<a href="https://www.waveshare.com/product/esp32-related/boards-kits/esp32-esp8266.htm">
-<span>ESP32</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-5-24 parent">
-<a href="https://www.waveshare.com/product/esp32-related/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-5-24-87 first">
-<a href="https://www.waveshare.com/product/esp32-related/displays/lcd-spi-qspi.htm">
-<span>LCD (SPI/QSPI)</span>
-</a>
-</li><li class="level3 nav-1-5-24-88">
-<a href="https://www.waveshare.com/product/esp32-related/displays/lcd-rgb.htm">
-<span>LCD (RGB)</span>
-</a>
-</li><li class="level3 nav-1-5-24-89">
-<a href="https://www.waveshare.com/product/esp32-related/displays/lcd-mipi.htm">
-<span>LCD (MIPI)</span>
-</a>
-</li><li class="level3 nav-1-5-24-90">
-<a href="https://www.waveshare.com/product/esp32-related/displays/amoled.htm">
-<span>AMOLED</span>
-</a>
-</li><li class="level3 nav-1-5-24-91">
-<a href="https://www.waveshare.com/product/esp32-related/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-</li><li class="level3 nav-1-5-24-92">
-<a href="https://www.waveshare.com/product/esp32-related/displays/rlcd.htm">
-<span>RLCD</span>
-</a>
-</li><li class="level3 nav-1-5-24-93 last">
-<a href="https://www.waveshare.com/product/esp32-related/displays/rgb-led-matrix.htm">
-<span>RGB LED Matrix</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-5-25">
-<a href="https://www.waveshare.com/product/esp32-related/ai-chat.htm">
-<span>AI Chat</span>
-</a>
-</li><li class="level2 nav-1-5-26">
-<a href="https://www.waveshare.com/product/esp32-related/cameras.htm">
-<span>Cameras</span>
-</a>
-</li><li class="level2 nav-1-5-27">
-<a href="https://www.waveshare.com/product/esp32-related/industrial-controller.htm">
-<span>Industrial Controller</span>
-</a>
-</li><li class="level2 nav-1-5-28 last parent">
-<a href="https://www.waveshare.com/product/esp32-related/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-5-28-94 first last">
-<a href="https://www.waveshare.com/product/esp32-related/robots/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-6 parent">
-<a href="https://www.waveshare.com/product/arduino-5.htm">
-<span>Arduino</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-6-29 first parent">
-<a href="https://www.waveshare.com/product/arduino-5/official-arduino.htm">
-<span>Official Arduino®</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-6-29-95 first last parent">
-<a href="https://www.waveshare.com/product/arduino-5/official-arduino/boards-core-boards.htm">
-<span>Boards / Core Boards</span>
-</a>
-<ul class="level3">
-<li class="level4 nav-1-6-29-95-1 first last">
-<a href="https://www.waveshare.com/product/arduino-5/official-arduino/boards-core-boards/arduino-uno-q-1.htm">
-<span>Arduino UNO Q</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level2 nav-1-6-30 last parent">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino.htm">
-<span>Compatible with Arduino®</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-6-30-96 first">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino/arduino-cases.htm">
-<span>Cases</span>
-</a>
-</li><li class="level3 nav-1-6-30-97">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino/arduino-kits.htm">
-<span>Kits</span>
-</a>
-</li><li class="level3 nav-1-6-30-98 last">
-<a href="https://www.waveshare.com/product/arduino-5/compatible-with-arduino/accessories.htm">
-<span>Accessories</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-7 parent">
-<a href="https://www.waveshare.com/product/displays.htm">
-<span>Displays</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-7-31 first parent">
-<a href="https://www.waveshare.com/product/displays/lcd-oled.htm">
-<span>LCD</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-31-99 first">
-<a href="https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-1.htm">
-<span>5″  - 24.5″</span>
-</a>
-</li><li class="level3 nav-1-7-31-100">
-<a href="https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-2.htm">
-<span>2.8″  - 4.3″</span>
-</a>
-</li><li class="level3 nav-1-7-31-101 last">
-<a href="https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-3.htm">
-<span>0.71″  - 2.4″</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-32 parent">
-<a href="https://www.waveshare.com/product/displays/oled.htm">
-<span>OLED</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-32-102 first">
-<a href="https://www.waveshare.com/product/displays/oled/oled-1.htm">
-<span>5″  - 15.6″</span>
-</a>
-</li><li class="level3 nav-1-7-32-103 last">
-<a href="https://www.waveshare.com/product/displays/oled/oled-3.htm">
-<span>0.49″  - 2.4″</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-33 parent">
-<a href="https://www.waveshare.com/product/displays/e-paper.htm">
-<span>e-Paper</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-33-104 first">
-<a href="https://www.waveshare.com/product/displays/e-paper/epaper-1.htm">
-<span>5.65″  - 13.3″</span>
-</a>
-</li><li class="level3 nav-1-7-33-105">
-<a href="https://www.waveshare.com/product/displays/e-paper/epaper-2.htm">
-<span>2.66″  - 5″</span>
-</a>
-</li><li class="level3 nav-1-7-33-106">
-<a href="https://www.waveshare.com/product/displays/e-paper/epaper-3.htm">
-<span>1.02″  - 2.36″</span>
-</a>
-</li><li class="level3 nav-1-7-33-107 last">
-<a href="https://www.waveshare.com/product/displays/e-paper/driver-boards.htm">
-<span>Driver Boards</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-34 parent">
-<a href="https://www.waveshare.com/product/displays/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-34-108 first">
-<a href="https://www.waveshare.com/product/displays/accessories/cables-adapters.htm">
-<span>Cables / Adapters</span>
-</a>
-</li><li class="level3 nav-1-7-34-109">
-<a href="https://www.waveshare.com/product/displays/accessories/cases.htm">
-<span>Cases</span>
-</a>
-</li><li class="level3 nav-1-7-34-110">
-<a href="https://www.waveshare.com/product/displays/accessories/speakers.htm">
-<span>Speakers</span>
-</a>
-</li><li class="level3 nav-1-7-34-111 last">
-<a href="https://www.waveshare.com/product/displays/accessories/stand.htm">
-<span>Stand</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-7-35 last parent">
-<a href="https://www.waveshare.com/product/displays/usb-monitor.htm">
-<span>USB Monitor</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-7-35-112 first last">
-<a href="https://www.waveshare.com/product/displays/usb-monitor/2-1-7.htm">
-<span>2.1“ - 7“</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-8 parent">
-<a href="https://www.waveshare.com/product/iot-communication.htm">
-<span>IoT / Communication</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-8-36 first parent">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless.htm">
-<span>Long Range Wireless</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-8-36-113 first">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless/nb-iot-lora.htm">
-<span>NB-IoT / Cat-M / LoRa / LoRaWAN</span>
-</a>
-</li><li class="level3 nav-1-8-36-114">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless/4g-gsm-gprs.htm">
-<span>5G / 4G / Cat-1 / GSM / GPRS</span>
-</a>
-</li><li class="level3 nav-1-8-36-115 last">
-<a href="https://www.waveshare.com/product/iot-communication/long-range-wireless/gnss-gps.htm">
-<span>GNSS / GPS</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-8-37 parent">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless.htm">
-<span>Short Range Wireless</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-8-37-116 first">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/wifi.htm">
-<span>WiFi</span>
-</a>
-</li><li class="level3 nav-1-8-37-117">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/zigbee.htm">
-<span>ZigBee</span>
-</a>
-</li><li class="level3 nav-1-8-37-118">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/bluetooth.htm">
-<span>Bluetooth</span>
-</a>
-</li><li class="level3 nav-1-8-37-119 last">
-<a href="https://www.waveshare.com/product/iot-communication/short-range-wireless/nfc-rf.htm">
-<span>NFC / RF</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-8-38 last parent">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter.htm">
-<span>Wired Comm / Converter</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-8-38-120 first">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb.htm">
-<span>USB</span>
-</a>
-</li><li class="level3 nav-1-8-38-121">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs232-uart-rs485.htm">
-<span>USB TO RS232 / RS485  / UART/ CAN</span>
-</a>
-</li><li class="level3 nav-1-8-38-122">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/ethernet.htm">
-<span>Ethernet</span>
-</a>
-</li><li class="level3 nav-1-8-38-123">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/ethernet-to-uart-rs232-rs485.htm">
-<span>Ethernet TO UART / RS232 / RS485</span>
-</a>
-</li><li class="level3 nav-1-8-38-124 last">
-<a href="https://www.waveshare.com/product/iot-communication/wired-comm-converter/rs232-rs485-can-dali2.htm">
-<span>RS232 / RS485 / CAN / DALI2 </span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-9 parent">
-<a href="https://www.waveshare.com/product/modules.htm">
-<span>Misc Modules</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-9-39 first parent">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video.htm">
-<span>Cameras / Audio / Video</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-39-125 first">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/speech-image-recognition-ai-vision.htm">
-<span>Speech / Image Recognition / AI Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-126">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/mipi-cameras.htm">
-<span>MIPI Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-127">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/usb-cameras.htm">
-<span>USB Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-128">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/gmsl-cameras.htm">
-<span>GMSL Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-129">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/cameras.htm">
-<span>Cameras</span>
-</a>
-</li><li class="level3 nav-1-9-39-130 last">
-<a href="https://www.waveshare.com/product/modules/cameras-audio-video/audio-decoder.htm">
-<span>Audio Decoder</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-9-40 parent">
-<a href="https://www.waveshare.com/product/modules/sensors.htm">
-<span>Sensors</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-40-131 first">
-<a href="https://www.waveshare.com/product/modules/sensors/accelerometer-angular-rate-compass.htm">
-<span>Accelerometer / Angular Rate / Compass</span>
-</a>
-</li><li class="level3 nav-1-9-40-132">
-<a href="https://www.waveshare.com/product/modules/sensors/fingerprint-sound-image-gesture.htm">
-<span>Fingerprint / Sound / Image / Gesture</span>
-</a>
-</li><li class="level3 nav-1-9-40-133">
-<a href="https://www.waveshare.com/product/modules/sensors/temperature-humidity-barometer.htm">
-<span>Temperature / Humidity / Barometer</span>
-</a>
-</li><li class="level3 nav-1-9-40-134">
-<a href="https://www.waveshare.com/product/modules/sensors/gas.htm">
-<span>Gas</span>
-</a>
-</li><li class="level3 nav-1-9-40-135">
-<a href="https://www.waveshare.com/product/modules/sensors/light-ranging.htm">
-<span>Light / Ranging / Lidar</span>
-</a>
-</li><li class="level3 nav-1-9-40-136 last">
-<a href="https://www.waveshare.com/product/modules/sensors/others.htm">
-<span>Others</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-9-41 parent">
-<a href="https://www.waveshare.com/product/modules/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-41-137 first">
-<a href="https://www.waveshare.com/product/modules/motors-servos/drivers.htm">
-<span>Drivers</span>
-</a>
-</li><li class="level3 nav-1-9-41-138 last">
-<a href="https://www.waveshare.com/product/modules/motors-servos/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-9-42 last parent">
-<a href="https://www.waveshare.com/product/modules/others.htm">
-<span>Others</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-9-42-139 first">
-<a href="https://www.waveshare.com/product/modules/others/interface-expansion.htm">
-<span>Interface Expansion</span>
-</a>
-</li><li class="level3 nav-1-9-42-140">
-<a href="https://www.waveshare.com/product/modules/others/led-buttons.htm">
-<span>LED / Buttons</span>
-</a>
-</li><li class="level3 nav-1-9-42-141">
-<a href="https://www.waveshare.com/product/modules/others/storage.htm">
-<span>Storage</span>
-</a>
-</li><li class="level3 nav-1-9-42-142">
-<a href="https://www.waveshare.com/product/modules/others/ad-da.htm">
-<span>AD / DA</span>
-</a>
-</li><li class="level3 nav-1-9-42-143">
-<a href="https://www.waveshare.com/product/modules/others/rtc.htm">
-<span>RTC</span>
-</a>
-</li><li class="level3 nav-1-9-42-144">
-<a href="https://www.waveshare.com/product/modules/others/power-relays.htm">
-<span>Power / Relays / SCR</span>
-</a>
-</li><li class="level3 nav-1-9-42-145 last">
-<a href="https://www.waveshare.com/product/modules/others/laser-module.htm">
-<span>Laser Module</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-10 parent">
-<a href="https://www.waveshare.com/product/robotics.htm">
-<span>Robotics</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-10-43 first parent">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots.htm">
-<span>Mobile Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-43-146 first">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/jetson-series-ai-robots.htm">
-<span>Jetson Series AI Robots</span>
-</a>
-</li><li class="level3 nav-1-10-43-147">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/raspberry-pi-robots.htm">
-<span>Raspberry Pi Robots</span>
-</a>
-</li><li class="level3 nav-1-10-43-148">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/arduino-robots.htm">
-<span>Arduino-Related Robots</span>
-</a>
-</li><li class="level3 nav-1-10-43-149 last">
-<a href="https://www.waveshare.com/product/robotics/mobile-robots/micro-bit-robots.htm">
-<span>micro:bit Robots</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-44 parent">
-<a href="https://www.waveshare.com/product/robotics/dog-like-robots.htm">
-<span>Dog-like Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-44-150 first last">
-<a href="https://www.waveshare.com/product/robotics/dog-like-robots/raspberry-pi-dog-like-robots.htm">
-<span>Raspberry Pi Dog-like Robots</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-45 parent">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors.htm">
-<span>Drivers / Sensors / Lidar</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-45-151 first">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors/drivers.htm">
-<span>Drivers</span>
-</a>
-</li><li class="level3 nav-1-10-45-152">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors/sensors.htm">
-<span>Sensors</span>
-</a>
-</li><li class="level3 nav-1-10-45-153 last">
-<a href="https://www.waveshare.com/product/robotics/drivers-sensors/lidar.htm">
-<span>Lidar</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-46 parent">
-<a href="https://www.waveshare.com/product/robotics/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-46-154 first">
-<a href="https://www.waveshare.com/product/robotics/motors-servos/motors.htm">
-<span>Motors</span>
-</a>
-</li><li class="level3 nav-1-10-46-155 last">
-<a href="https://www.waveshare.com/product/robotics/motors-servos/servos.htm">
-<span>Servos</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-47 parent">
-<a href="https://www.waveshare.com/product/robotics/robot-arm-control.htm">
-<span>Robot Arm / Control</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-47-156 first">
-<a href="https://www.waveshare.com/product/robotics/robot-arm-control/robot-arm.htm">
-<span>Robot Arm</span>
-</a>
-</li><li class="level3 nav-1-10-47-157 last">
-<a href="https://www.waveshare.com/product/robotics/robot-arm-control/pan-tilt-control.htm">
-<span>Pan Tilt Control</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-10-48">
-<a href="https://www.waveshare.com/product/robotics/remote-controller.htm">
-<span>Remote Controller</span>
-</a>
-</li><li class="level2 nav-1-10-49 last parent">
-<a href="https://www.waveshare.com/product/robotics/robotic-components.htm">
-<span>Robotic Components</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-10-49-158 first">
-<a href="https://www.waveshare.com/product/robotics/robotic-components/gearing.htm">
-<span>Gearing</span>
-</a>
-</li><li class="level3 nav-1-10-49-159 last">
-<a href="https://www.waveshare.com/product/robotics/robotic-components/chassis-accessories.htm">
-<span>Chassis Accessories</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-11 parent">
-<a href="https://www.waveshare.com/product/mcu-tools.htm">
-<span>MCU / FPGA</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-11-50 first parent">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards.htm">
-<span>Core Boards / Compact Boards</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-50-160 first">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/stm32-core.htm">
-<span>STM32 Core</span>
-</a>
-</li><li class="level3 nav-1-11-50-161">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/stm32-discovery.htm">
-<span>STM32 Discovery</span>
-</a>
-</li><li class="level3 nav-1-11-50-162">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/stm32-nucleo.htm">
-<span>STM32 Nucleo</span>
-</a>
-</li><li class="level3 nav-1-11-50-163">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/lpc-core.htm">
-<span>LPC Core</span>
-</a>
-</li><li class="level3 nav-1-11-50-164">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/beagleboard.htm">
-<span>BeagleBoard</span>
-</a>
-</li><li class="level3 nav-1-11-50-165">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/altera-core.htm">
-<span>ALTERA Core</span>
-</a>
-</li><li class="level3 nav-1-11-50-166">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/arduino.htm">
-<span>Arduino® Compatible</span>
-</a>
-</li><li class="level3 nav-1-11-50-167 last">
-<a href="https://www.waveshare.com/product/mcu-tools/core-boards-compact-boards/micro-bit-boards.htm">
-<span>micro:bit</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-51 parent">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards.htm">
-<span>Development Boards / Expansions</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-51-168 first">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/stm32-open.htm">
-<span>STM32 Open</span>
-</a>
-</li><li class="level3 nav-1-11-51-169">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/stm32-evk.htm">
-<span>STM32 EVK</span>
-</a>
-</li><li class="level3 nav-1-11-51-170">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/avr-arduino-shields.htm">
-<span>AVR Arduino Shields</span>
-</a>
-</li><li class="level3 nav-1-11-51-171">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/arduino-shields-compatible.htm">
-<span>Arduino Shields Compatible</span>
-</a>
-</li><li class="level3 nav-1-11-51-172">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/displays-buttons-sound.htm">
-<span>Displays / Buttons / Sound</span>
-</a>
-</li><li class="level3 nav-1-11-51-173 last">
-<a href="https://www.waveshare.com/product/mcu-tools/development-boards/motors-interface.htm">
-<span>Motors / Interface</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-52 parent">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer.htm">
-<span>Debugger / Programmer</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-52-174 first">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/stm32-stm8.htm">
-<span>STM32 / STM8</span>
-</a>
-</li><li class="level3 nav-1-11-52-175">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/avr.htm">
-<span>AVR</span>
-</a>
-</li><li class="level3 nav-1-11-52-176">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/pic.htm">
-<span>PIC</span>
-</a>
-</li><li class="level3 nav-1-11-52-177">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/altera-core.htm">
-<span>ALTERA Core</span>
-</a>
-</li><li class="level3 nav-1-11-52-178 last">
-<a href="https://www.waveshare.com/product/mcu-tools/debugger-programmer/xilinx.htm">
-<span>XILINX</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-53 parent">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters.htm">
-<span>Programming Adapters</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-53-179 first">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters/stm32.htm">
-<span>STM32</span>
-</a>
-</li><li class="level3 nav-1-11-53-180">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters/stm8.htm">
-<span>STM8</span>
-</a>
-</li><li class="level3 nav-1-11-53-181 last">
-<a href="https://www.waveshare.com/product/mcu-tools/programming-adapters/avr.htm">
-<span>AVR</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-11-54 last parent">
-<a href="https://www.waveshare.com/product/mcu-tools/robots.htm">
-<span>Robots</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-11-54-182 first last">
-<a href="https://www.waveshare.com/product/mcu-tools/robots/robot-arm.htm">
-<span>Robot Arm</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-12 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters.htm">
-<span>Sockets / Adapters</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-12-55 first parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters.htm">
-<span>Specific Programming Adapters</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-55-183 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters/stm32-series.htm">
-<span>STM32 Series</span>
-</a>
-</li><li class="level3 nav-1-12-55-184">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters/stm8-series.htm">
-<span>STM8 Series</span>
-</a>
-</li><li class="level3 nav-1-12-55-185 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/specific-programming-adapters/avr-series.htm">
-<span>AVR Series</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-56 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp.htm">
-<span>QFP</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-56-186 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-56-187">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li><li class="level3 nav-1-12-56-188 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfp/with-pinheader.htm">
-<span>With Pinheader</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-57 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf.htm">
-<span>QFN / MLF</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-57-189 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-57-190">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li><li class="level3 nav-1-12-57-191 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/qfn-mlf/with-pinheader.htm">
-<span>With Pinheader</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-58 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/sop.htm">
-<span>SOP</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-58-192 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/sop/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-58-193 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/sop/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-59 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/ssop-tssop.htm">
-<span>SSOP / TSSOP</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-59-194 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/ssop-tssop/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-59-195 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/ssop-tssop/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-60 parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/tsop-msop-sot.htm">
-<span>TSOP / MSOP / SOT</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-60-196 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/tsop-msop-sot/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-60-197 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/tsop-msop-sot/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-12-61 last parent">
-<a href="https://www.waveshare.com/product/sockets-adapters/plcc.htm">
-<span>PLCC</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-12-61-198 first">
-<a href="https://www.waveshare.com/product/sockets-adapters/plcc/sockets.htm">
-<span>Sockets</span>
-</a>
-</li><li class="level3 nav-1-12-61-199 last">
-<a href="https://www.waveshare.com/product/sockets-adapters/plcc/to-dip.htm">
-<span>TO DIP</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li><li class="level1 nav-1-13 last parent">
-<a href="https://www.waveshare.com/product/accessories.htm">
-<span>Accessories</span>
-</a>
-<ul class="level1">
-<li class="level2 nav-1-13-62 first parent">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas.htm">
-<span>Adapters / Cables / Antennas</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-62-200 first">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/hdmi.htm">
-<span>HDMI</span>
-</a>
-</li><li class="level3 nav-1-13-62-201">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/usb.htm">
-<span>USB</span>
-</a>
-</li><li class="level3 nav-1-13-62-202">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/serial-cables.htm">
-<span>Serial Cables</span>
-</a>
-</li><li class="level3 nav-1-13-62-203">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/jumper-wires.htm">
-<span>Jumper Wires</span>
-</a>
-</li><li class="level3 nav-1-13-62-204">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/ffc.htm">
-<span>FFC</span>
-</a>
-</li><li class="level3 nav-1-13-62-205 last">
-<a href="https://www.waveshare.com/product/accessories/adapters-cables-antennas/antennas.htm">
-<span>Antennas</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-13-63 parent">
-<a href="https://www.waveshare.com/product/accessories/motors-servos.htm">
-<span>Motors / Servos</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-63-206 first">
-<a href="https://www.waveshare.com/product/accessories/motors-servos/motors.htm">
-<span>Motors</span>
-</a>
-</li><li class="level3 nav-1-13-63-207 last">
-<a href="https://www.waveshare.com/product/accessories/motors-servos/servos.htm">
-<span>Servos</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-13-64 parent">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks.htm">
-<span>Power / Heat Sinks</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-64-208 first">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/power-supply.htm">
-<span>Power Supply</span>
-</a>
-</li><li class="level3 nav-1-13-64-209">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/solar-power.htm">
-<span>Solar Power</span>
-</a>
-</li><li class="level3 nav-1-13-64-210">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/heat-sinks.htm">
-<span>Heat Sinks</span>
-</a>
-</li><li class="level3 nav-1-13-64-211 last">
-<a href="https://www.waveshare.com/product/accessories/power-heat-sinks/cooling-fans.htm">
-<span>Cooling Fans</span>
-</a>
-</li>
-</ul>
-</li><li class="level2 nav-1-13-65 last parent">
-<a href="https://www.waveshare.com/product/accessories/misc.htm">
-<span>Misc</span>
-</a>
-<ul class="level2">
-<li class="level3 nav-1-13-65-212 first">
-<a href="https://www.waveshare.com/product/accessories/misc/raspberry-pi-cases.htm">
-<span>Raspberry Pi Cases</span>
-</a>
-</li><li class="level3 nav-1-13-65-213">
-<a href="https://www.waveshare.com/product/accessories/misc/jetson-nano-cases.htm">
-<span>Jetson Nano Cases</span>
-</a>
-</li><li class="level3 nav-1-13-65-214">
-<a href="https://www.waveshare.com/product/accessories/misc/display-cases.htm">
-<span>Display Cases</span>
-</a>
-</li><li class="level3 nav-1-13-65-215">
-<a href="https://www.waveshare.com/product/accessories/misc/speakers.htm">
-<span>Speakers</span>
-</a>
-</li><li class="level3 nav-1-13-65-216 last">
-<a href="https://www.waveshare.com/product/accessories/misc/storage.htm">
-<span>Storage</span>
-</a>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-</li> </ul>
-<!-- /nav -->
-
-</nav>
-<div class="block block-layered-nav">
-    <div class="block-title">
-        <strong><span>Browse By</span></strong>
-    </div>
-    <div class="block-content">
-        <dl id="narrow-by-list2">
-            <dt>Category</dt>
-            <dd>
-                <ol>
-                                                        <li>
-                        <a href="https://www.waveshare.com/product/raspberry-pi.htm">Raspberry Pi</a> (909)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/ai.htm">AI</a> (382)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/luckfox.htm">Luckfox</a> (100)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/risc-v.htm">RISC-V</a> (14)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/esp32-related.htm">ESP32</a> (167)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/arduino-5.htm">Arduino</a> (3)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/displays.htm">Displays</a> (401)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/iot-communication.htm">IoT / Communication</a> (362)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/modules.htm">Misc Modules</a> (306)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/robotics.htm">Robotics</a> (111)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/mcu-tools.htm">MCU / FPGA</a> (142)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/sockets-adapters.htm">Sockets / Adapters</a> (194)
-                    </li>
-                                                                            <li>
-                        <a href="https://www.waveshare.com/product/accessories.htm">Accessories</a> (204)
-                    </li>
-                                                    </ol>
-            </dd>
-        </dl>
-        <script type="text/javascript">decorateDataList('narrow-by-list2')</script>
-    </div>
-</div>
-<style>
-.sidebar a {
-    color: #565656;
-}
-</style>
-                    </div>
-                                        
-                    </div>                            </div>
-        </div>
-    </div>
-    <div class="footer-container">
-        <!--  -->
-        <div class="footer">
-                                <div class="footer-up">
-        <div class="container">
-            <div class="row ws-advantage d-flex justify-content-between">
-                <div>
-                    <div class="advantage-img advantage-img-1"></div>
-                    <p>15 Days Returnable</p>
-                </div>
-                <div>
-                    <div class="advantage-img advantage-img-2"></div>
-                    <p>12 Months Warranty</p>
-                </div>
-                <div>
-                    <div class="advantage-img advantage-img-3"></div>
-                    <p>Trustworthy Brand</p>
-                </div>
-                <div>
-                    <div class="advantage-img advantage-img-4"></div>
-                    <p>Discount for Large Quantity</p>
-                </div>
-                <div>
-                    <div class="advantage-img advantage-img-5"></div>
-                    <p>Worldwide Shipping</p>
-                </div>
-            </div>
-        </div>
-    </div>
-    <div class="footer-top">
-                <div class="container">
-            <div class="row">
-                                <div class="waveshare-col-sm-3 col-md-3 col-sm-4 footer_column footer-column-1"> <!-- col-sm-4 -->
-                    <h3 class="title">INFO & SERVICES</h3>                    <ul>
-<li><a href="https://www.waveshare.com/about_us">About Us</a></li>
-<li><a href="https://www.waveshare.com/contact_us">Contact Us</a></li>
-<li><a href="https://www.waveshare.com/distributors">Distributors</a></li>
-<li><a href="/customization.html">Customization</a></li>
-<li><a href="/join_affiliate.html">Join Affiliate</a></li>
-</ul>                </div>
-                                <div class="waveshare-col-sm-3 col-md-3 col-sm-4 footer_column footer-column-2"> <!-- col-sm-4 -->
-                    <h3 class="title">HELP</h3>                    <ul>
-<li><a href="https://www.waveshare.com/payment">Payment</a></li>
-<li><a href="https://www.waveshare.com/shipping">Shipping</a></li>
-<li><a href="https://www.waveshare.com/warranty_returns">Warranty &amp; Returns</a></li>
-<li><a href="https://www.waveshare.com/privacy_policy">Privacy Policy</a></li>
-<li><a href="https://www.waveshare.com/shopping_q_a">Shopping Q&amp;A</a></li>
-<li><a href="https://service.waveshare.com/">Tech Support</a></li>
-</ul>                </div>
-                                <div class="waveshare-col-sm-3 col-md-3 col-sm-4 footer_column footer-column-3"> <!-- col-sm-4 -->
-                    <h3 class="title">LINKS</h3>                    <ul>
-<li><a href="https://www.waveshare.com/catalog/seo_sitemap/category/">Product Categories</a></li>
-<li><a href="https://www.waveshare.com/catalogsearch/advanced/">Advanced Search</a></li>
-<li><a href="/wiki">WIKI</a></li>
-</ul>                </div>
-                                <div class="clearfix visible-sm"></div>
-                <div id="waveshare_newsletter" class="waveshare-col-sm-4 col-md-3 footer_column footer-column-4 col-sm-12">
-                    <h3 class="title">BE THE FIRST TO KNOW</h3>
-                    <p><!-- modify by libearxiong 20180113 -->
-    <div>
-        <span>Get all the latest information, subscribe now.</span>
-    </div>
-    <form action="https://www.waveshare.com/newsletter/subscriber/new/" method="post" id="footer-newsletter-validate-detail">
-        <div class="block-content">
-            <div class="input-box">
-               <input type="text" name="email" id="newsletter" title="Sign up for our newsletter" class="input-text required-entry validate-email"  placeholder="Enter your email address" />
-            <!--</div>
-            <div class="actions">-->
-                <button type="submit" title="SUBMIT" class="button btn-lg btn-large"><span><span>SUBMIT</span></span></button>
-            </div>
-        </div>
-    </form>
-    <script type="text/javascript">
-    //<![CDATA[
-        var newsletterSubscriberFormDetail = new VarienForm('footer-newsletter-validate-detail');
-    //]]>
-    </script>
-<!--</div>-->
-</p>
-                    <a href="https://www.youtube.com/channel/UCV_48_r0rplaYB-VqxXB04g/videos" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/youtube.svg"/>
-                    </a>
-                    <!--<a href="https://www.facebook.com/Waveshare1" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/facebook.svg"/>
-                    </a>-->
-                    <a href="https://twitter.com/waveshare00" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/twitter.svg"/>
-                    </a>
-                    <!--<a href="https://wavesharejfs.blogspot.com" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/blogspot.svg"/>
-                    </a>-->
-                    <a href="https://www.instagram.com/waveshareelectronics" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/instagram.svg"/>
-                    </a>
-                    <a href="https://www.tiktok.com/@waveshareelectronics" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/tiktok.svg"/>
-                    </a>
-                    <a href="https://www.linkedin.com/company/waveshare/" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/linkin.svg"/>
-                    </a>
-                    <a href="https://github.com/waveshareteam" target="_blank" rel="nofollow noopener noreferrer">
-                        <img width="30px" height="30px" src="/skin/frontend/venedor/default/images/icons/waveshare/github.svg"/>
-                    </a>
-                </div>
-            </div>
-        </div>
-    </div>
-    <div class="footer-bottom">
-        <div class="container">
-            <!--<div class="row">
-                <div class="col-sm-7 social-links">
-                                    </div>
-                <div class="col-sm-5 copyright">
-                    <address></address>
-                                        
-                </div>
-            </div> -->
-            <div class="row">
-                <div class="col-md-6">
-                    <img src="/img/banner/payment.svg" alt="logo about paypal, mastercard, visa and American Express">
-                </div>
-                <div class="col-md-6"><p>Copyright &copy; 2026 Waveshare. All Rights Reserved. </p></div>
-            </div>
-        </div>
-    </div>
-</div>
-<!-- TODO: 测试聊天工具 -->
-<!--<script type="text/javascript" src="https://www.waveshare.com/js/eternal/jquery/jquery-1.8.2.min.js"></script>
-<script type="text/javascript" src="https://static.waveshare.com/wtpkg/ws-chat.js"></script>-->
-<script type="text/javascript">
-//<![CDATA[
-jQuery(function($) {
-    
-    var venedor_sidebar_timer;
-    
-    function venedor_sidebar_resize() {
-        if (VENEDOR_RESPONSIVE) {
-            var winWidth = $(window).innerWidth();
-
-            if (winWidth > 750 && ((!$('body').hasClass('bv3') && winWidth < 963) || ($('body').hasClass('bv3') && winWidth < 975))) {
-                                if ($('.sidebar').hasClass('col-sm-3')) {
-                    $('.sidebar').removeClass('col-sm-3');
-                    $('.sidebar').addClass('col-sm-4');
-                    $('.main-content').removeClass('col-sm-9');
-                    $('.main-content').addClass('col-sm-8');
-                    venedor_resize();
-                }                
-            } else {
-                                if ($('.sidebar').hasClass('col-sm-4')) {
-                    $('.sidebar').removeClass('col-sm-4');
-                    $('.sidebar').addClass('col-sm-3');
-                    $('.main-content').removeClass('col-sm-8');
-                    $('.main-content').addClass('col-sm-9');
-                    venedor_resize();
-                }
-            }
-        }
-        if (venedor_sidebar_timer) clearTimeout(venedor_sidebar_timer);
-    }
-
-    $(window).load(venedor_sidebar_resize);
-    
-    $(window).resize(function() { 
-        clearTimeout(venedor_sidebar_timer); 
-        venedor_sidebar_timer = setTimeout(venedor_sidebar_resize, 200); 
-    });
-    
-    var venedor_timer;
-    
-    function venedor_resize() {
-        $('.subtitle .line').each(function() {
-            w = $(this).prev().width();
-            $(this).css('left', (w + 30) + 'px');
-        });
-        if (VENEDOR_RESPONSIVE) {
-            var winWidth = $(window).innerWidth();
-            if ($('.flexslider').length) {
-                $('.flexslider').each(function() {
-                    var $slider = $(this).data('flexslider');
-                    if ($slider) {
-                        break_default = $slider.data('break_default');
-                        var resized = false;
-                        if (break_default) {
-                            minItems = break_default[0];
-                            maxItems = break_default[0];
-                            itemWidth = break_default[1];
-                            break_points = $slider.data('break_points');
-                            if (break_points) {
-                                for (i = 0; i < break_points.length; i++) {
-                                    if (winWidth < break_points[i][0]) {
-                                        minItems = break_points[i][1];
-                                        maxItems = break_points[i][1];
-                                        itemWidth = break_points[i][2];
-                                    }
-                                }
-                                if ($slider.move != minItems) {
-                                    $slider.setOptions({
-                                        minItems: minItems,
-                                        maxItems: maxItems,
-                                        itemWidth: itemWidth,
-                                        move: minItems
-                                    });
-                                    resized = true;
-                                    setTimeout(function() {
-                                        if ($slider.w > 0 && $slider.h > 0)
-                                            $slider.resize();
-                                    }, 400);
-                                }
-                            }
-                        }
-                        if (!resized)
-                            $slider.resize();
-                    }
-                });
-            }
-        }
-        if (venedor_timer) clearTimeout(venedor_timer); 
-    }
-
-    $(window).load(venedor_resize);
-    $(window).resize(function() {
-        clearTimeout(venedor_timer); 
-        venedor_timer = setTimeout(venedor_resize, 400); 
-    });
-    function setHeight() {
-        // var winWidth = $('.main-slider').innerWidth();
-        // $("#homeslider-sequence").css("height",winWidth/4);
-    }
-//banner autosize start
-    $(window).resize(function() {
-    	setHeight();
-    });
-    setHeight();
-//banner autosize end
-});
-//]]>
-</script>
-<!-- Start of StatCounter Code for Default Guide -->
-<script type="text/javascript">
-var sc_project=5969124; 
-var sc_invisible=0; 
-var sc_security="7aa4f74d"; 
-var sc_https=1; 
-//var scJsHost = (("https:" == document.location.protocol) ?
-//"https://secure." : "http://www.");
-//document.write("<sc"+"ript type='text/javascript' src='" +
-//scJsHost+
-//"statcounter.com/counter/counter.js'></"+"script>");
-</script>
-<script type="text/javascript"
-    src="https://secure.statcounter.com/counter/counter.js"></script>
-<noscript><div class="statcounter"><a title="Web Analytics
-Made Easy - StatCounter" href="http://statcounter.com/"
-target="_blank"><img class="statcounter"
-src="//c.statcounter.com/5969124/0/7aa4f74d/0/" alt="Web
-Analytics Made Easy - StatCounter"></a></div></noscript>
-<!-- End of StatCounter Code for Default Guide -->
-
-<script type="text/javascript">
-jQuery(function($){
-			$('.statcounter').find('img').css('width','1px');
-			$('.statcounter').find('img').css('height','1px');
-
-});
-</script>                
-
-    </div>
-<script type="text/javascript" src="https://static.waveshare.com/wtpkg/ws-chat.js"></script><script>(function(){function c(){var b=a.contentDocument||(a.contentWindow&&a.contentWindow.document);if(b){var d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'a34a7054588e6abb',t:'MTc4ODMzMDM0MA=='};var a=document.createElement('script');a.src='/cdn-cgi/challenge-platform/scripts/jsd/main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.style.visibility='hidden';document.body.appendChild(a);if('loading'!==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!==document.readyState&&(document.onreadystatechange=e,c())}}}})();</script></body>
-</html>
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/commands.md b/devices/waveshare/esp32-s3-epaper-3.97/commands.md
deleted file mode 100644
index 26493c1..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/commands.md
+++ /dev/null
@@ -1,325 +0,0 @@
-# Command ledger — Waveshare ESP32-S3-ePaper-3.97
-
-> Every command that produced a fact in this record, plus the ones that failed.
-> Status vocabulary: `executed-success` · `executed-failed` · `reported-working` ·
-> `inferred` · `not-tested`.
->
-> Environment for all `executed-*` rows: Linux, bash, `curl 8.x`,
-> `python3 3.14.7`, `gh` authenticated. Working directory
-> `hardware-doc/scratch/waveshare-epaper-esp32/` unless noted.
-> Date: **2026-09-01**.
->
-> **No command in this file was run against hardware.** There is no board.
-
-## 0. Shared setup
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-```
-
-A browser User-Agent is required on `www.waveshare.com`; the default `curl/*` agent
-is intermittently blocked. Per this repository's
-[AGENTS.md](../../../AGENTS.md) rule, the plain request was tried first — it worked
-for `files.waveshare.com` and `docs.waveshare.com`, and the UA was set uniformly
-anyway because the vendor guide already records the need.
-Status: `executed-success`.
-
-## 1. Product enumeration
-
-**Purpose:** find every ESP32 e-paper product Waveshare currently sells.
-
-```bash
-curl -sSL -A "$UA" --max-time 90 \
-  'https://www.waveshare.com/catalogsearch/result/?q=e-paper+esp32&limit=200' \
-  | grep -oE 'https://www\.waveshare\.com/[a-zA-Z0-9.\-]+\.htm' | sort -u
-```
-
-Six query families were run: `e-paper esp32`, `epaper esp32-s3`, `photopainter`,
-`e-paper driver board`, `esp32 e-ink`, `e-paper esp32 development board`.
-Result: **seven** ESP32 e-paper products. `esp32 e-ink` returned **nothing** — the
-storefront does not index "e-ink" as a synonym, worth knowing.
-Status: `executed-success`.
-
-**Negative result, recorded because it cost time:**
-
-```bash
-curl -sS -A "$UA" 'https://www.waveshare.com/product/displays/e-paper.htm' \
-  | grep -c 'product-item'      # -> 0
-```
-
-The category page returns **HTTP 200, 244 758 bytes, and zero product links** — the
-grid is JS-rendered. **Use `/catalogsearch/result/?q=` to enumerate, never the
-category page.** Status: `executed-success` (as a negative result).
-
-## 2. SKU and price extraction
-
-**Purpose:** the first pass on this board recorded price as "not established".
-It is in the markup.
-
-```bash
-python3 - <<'EOF'
-import re, html
-s = open('survey/esp32-s3-epaper-3.97.html', encoding='utf-8', errors='replace').read()
-print(sorted(set(re.findall(r'class="price"[^>]*>\s*\$?([\d,.]+)', s))))
-m = re.search(r'waveshare_sku_attributes\s*=\s*(\[.*?\]);', s, re.S)
-print(html.unescape(m.group(1)))
-EOF
-```
-
-Output:
-
-```
-['0.00', '34.99', '47.99']
-[{"sku ":"33552","attributes":["With Lithium Batt"],"unsaleable":false},
- {"sku ":"33810","attributes":["Without Lithium Batt"],"unsaleable":false},
- {"sku ":"33811","attributes":["Basic Kit (Lithium Batt + TF Card + Card Reader)"],"unsaleable":false}]
-```
-
-Note the key is **`"sku "` with a trailing space** — a regex for `"sku"` misses it
-entirely, which is the likeliest reason the first pass found no price. The
-`unsaleable:false` flags establish availability.
-Status: `executed-success`. Extends [vendor guide §8.6](../../../vendors/waveshare/README.md).
-
-## 3. Documentation retrieval
-
-```bash
-curl -sSL -A "$UA" -o docs-overview.html   'https://docs.waveshare.com/ESP32-S3-ePaper-3.97'
-curl -sSL -A "$UA" -o docs-resources.html  'https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents'
-```
-
-Both **HTTP 200**. Docusaurus v3.10.2, **server-rendered** — the text is in the HTML
-and needs no browser. Status: `executed-success`.
-
-Sub-page slugs follow `https://docs.waveshare.com/<PRODUCT>/<Section>`; the sections
-are discoverable by grepping the overview page:
-
-```bash
-grep -oE 'ESP32-S3-ePaper-3\.97/[A-Za-z0-9\-]+' docs-overview.html | sort -u
-# -> Arduino, ESP-IDF, ESP32-AI-Tutorials, FAQ, Firmware-Flashing,
-#    Resources-And-Documents, Technical-Support
-```
-
-**Failed, recorded:**
-
-```bash
-curl -sSL -A "$UA" -o /dev/null -w '%{http_code}\n' \
-  'https://www.waveshare.com/wiki/ESP32-S3-ePaper-3.97'          # 404
-curl -sSL -A "$UA" -o /dev/null -w '%{http_code}\n' \
-  'https://docs.waveshare.com/E-Paper-ESP32-Driver-Board'        # 404
-```
-
-The two hosts are **disjoint**: new products on `docs.`, older ones on `/wiki/`.
-Status: `executed-success` (negative results).
-
-## 4. Artifact download and validation
-
-```bash
-dl() { curl -sSL -A "$UA" --max-time 300 -o "$2" -w '%{http_code} %{size_download} %s\n' "$1"; }
-
-dl 'https://files.waveshare.com/wiki/ESP32-S3-ePaper-3.97/ESP32-S3_e-Paper-3.97-schematic.pdf' schematic.pdf
-dl 'https://files.waveshare.com/wiki/3.97inch_e-Paper_HAT%2B/3.97inch_e-Paper.pdf'             panel.pdf
-dl 'https://files.waveshare.com/wiki/common/ES8311.DS.pdf'                                     es8311.pdf
-dl 'https://files.waveshare.com/wiki/common/Pcf85063atl1118-NdPQpTGE-loeW7GbZ7.pdf'            pcf85063.pdf
-dl 'https://files.waveshare.com/wiki/common/SHTC3_Datasheet.pdf'                               shtc3.pdf
-dl 'https://raw.githubusercontent.com/lewisxhe/XPowersLib/master/datasheet/AXP2101_Datasheet_V1.4_en.pdf' axp2101.pdf
-```
-
-**Validation — by magic bytes, never by status code:**
-
-```bash
-for f in *.pdf; do
-  printf '%-45s %-10s ' "$f" "$(stat -c%s "$f")"
-  head -c 5 "$f" | od -c | head -1
-done
-sha256sum *.pdf
-```
-
-All six begin `%PDF-`. Hashes are in [`sources.md`](sources.md).
-Status: `executed-success`.
-
-**Two failures, both correctly rejected:**
-
-```bash
-curl -sSL -A "$UA" -o axp.tmp 'https://files.waveshare.com/wiki/common/AXP2101.pdf'
-head -c 5 axp.tmp   # -> '<?xml'   HTTP 404
-curl -sSL -A "$UA" -o axp.tmp \
-  'https://github.com/lewisxhe/XPowersLib/raw/master/datasheet/AXP2101_Datasheet_V1.0_en.pdf'
-head -c 5 axp.tmp   # -> newlines (HTML)   HTTP 404, 267 330 bytes
-rm -f axp.tmp
-```
-
-Note the second returned **267 KB of HTML** — a plausible-looking size that would
-have passed any length check. **Neither was retained under a `.pdf` name.**
-Status: `executed-failed`, correctly handled.
-
-The working filename was found by listing the directory through the API rather than
-guessing:
-
-```bash
-curl -sS -H "Authorization: Bearer $(gh auth token)" \
-  'https://api.github.com/repos/lewisxhe/XPowersLib/contents/datasheet'
-```
-
-Status: `executed-success`.
-
-## 5. Schematic text extraction
-
-**The problem:** no `pdftotext`, `pdftoppm`, `mutool`, `qpdf`, `pypdf`, `pymupdf` or
-`pdfminer` on this host, and no `pip`. The repository's own
-`tools/altium_pdf_netlist.py` needs `pdftotext -bbox` XML as input, so it could not
-be used directly.
-
-```bash
-which pdftotext pdftoppm mutool qpdf   # -> nothing
-python3 -c 'import pypdf'              # -> ModuleNotFoundError
-pip install pypdf                      # -> pip: command not found
-```
-
-Status: `executed-failed`. **This is why `tools/pdftext.py` exists.**
-
-**Step 1 — diagnose the PDF.** A naive page-content walker returns zero text:
-
-```bash
-python3 tools/pdftext.py dl/ESP32-S3_e-Paper-3.97-schematic.pdf | wc -l   # -> 0
-```
-
-Which looks exactly like "no text layer" and is **wrong**. The whole sheet lives in a
-**Form XObject**, not in `/Contents`:
-
-```bash
-python3 - <<'EOF'
-import sys; sys.path.insert(0,'tools')
-from pdftext import objects, inflate
-data = open('dl/ESP32-S3_e-Paper-3.97-schematic.pdf','rb').read()
-for num,gen,dic,raw in objects(data):
-    if raw is None: continue
-    d = inflate(dic, raw)
-    print(num, len(raw), len(d) if d else None, d.count(b'BT') if d else 0)
-EOF
-# object 5: /Subtype /Form, 62 453 -> 447 937 bytes inflated, 1 158 BT blocks
-```
-
-Status: `executed-success`. **Generalisable finding — see
-[vendors/waveshare](../../../vendors/waveshare/README.md).**
-
-**Step 2 — extract and reflow.** Altium emits one glyph per `Tj` with its own `Tm`,
-so raw extraction gives 4 318 single characters and 170 distinct strings:
-
-```bash
-python3 - > sch.tsv <<'EOF'
-import sys; sys.path.insert(0,'tools')
-from pdftext import objects, inflate, extract
-data = open('dl/ESP32-S3_e-Paper-3.97-schematic.pdf','rb').read()
-for num,gen,dic,raw in objects(data):
-    if raw is None: continue
-    d = inflate(dic, raw)
-    if d and d.count(b'BT') > 50:
-        for x,y,t in extract(d):
-            print(f'{num}\t{x}\t{y}\t{t}')
-EOF
-
-python3 tools/reflow.py sch.tsv 1.2 4.5 > sch-words2.tsv
-wc -l sch-words2.tsv     # 1 150 tokens
-cut -f3 sch-words2.tsv | sort -u | wc -l   # 628 distinct
-```
-
-Status: `executed-success`. Output retained as
-`artifacts/schematic/schematic-text-reflowed.tsv`.
-
-**Step 3 — read the allocation table** (columns are x-bands):
-
-```bash
-awk -F'\t' '$1<166 && $1>35 && $2>150 && $2<425' sch-words2.tsv | sort -k1,1gr
-```
-
-Produces the GPIO table transcribed in [`pinouts-and-buses.md`](pinouts-and-buses.md).
-Status: `executed-success`.
-
-**Step 4 — the PMIC:**
-
-```bash
-rg -n 'AXP2101|TG28|ALDO|BLDO|DLDO|CPUSLDO|PWRON' sch-words2.tsv
-# 381:  358.19  210.28  AXP2101      <- and no occurrence of TG28 anywhere
-```
-
-Status: `executed-success`. Settles [C-WS2](gaps-and-conflicts.md#c-ws2--tg28-versus-axp2101).
-
-## 6. Panel manual — validating a hostile text layer
-
-The manual's text layer is **human-legible but wrong** if read naively — the exact
-failure the method warns about. Raw extraction yields `LQFKH 3DSHU`.
-
-```bash
-python3 - <<'EOF'
-# Determine the offset from a KNOWN heading: the cover reads "3.97inch e-Paper".
-enc = 'LQFKH'; want = 'inche'
-print({ord(w)-ord(e) for e,w in zip(enc,want)})    # -> {29}
-EOF
-```
-
-A single uniform offset of **+29** across letters *and* digits, and a second subset
-font at **+26**. Decoder: `tools/deshift.py`.
-
-```bash
-python3 tools/deshift.py panel.tsv > panel-dec.txt
-rg -i '3\.97inch|e-Paper' panel-dec.txt | head -3      # validation against the heading
-rg -i 'driver ic|SSD1' panel-dec.txt
-# 66:151  509.4  4-1:Displaymodule3.97«arrayforEPD;4-2:DriverIC:SSD1677;
-```
-
-**Only after the heading validated was any value transcribed.** Status:
-`executed-success`. This is the method's PDF-text-layer rule applied literally, and
-it is what produced the SSD1677 identification.
-
-## 7. Vendor source
-
-```bash
-TOKEN=$(gh auth token)
-H=(-H "Authorization: Bearer $TOKEN" -H 'Accept: application/vnd.github+json')
-SHA=9b12d40731a80213b927ee8a421cae4082952819
-
-curl -sS "${H[@]}" 'https://api.github.com/repos/waveshareteam/ESP32-S3-ePaper-3.97'
-curl -sS "${H[@]}" "https://api.github.com/repos/waveshareteam/ESP32-S3-ePaper-3.97/git/trees/$SHA?recursive=1"
-# 1 217 entries, truncated=false
-
-curl -sSL -H "Authorization: Bearer $TOKEN" -H 'Accept: application/vnd.github.raw' \
-  "https://api.github.com/repos/waveshareteam/ESP32-S3-ePaper-3.97/contents/ESP-IDF/08_ESP32-S3_e-Paper-3.97/components/axpPower/axp_prot.cpp?ref=$SHA"
-```
-
-Authenticating with `gh auth token` avoids the 60 req/hour anonymous limit, per the
-[`web-retrieval-fallback`](../../../.agents/skills/) guidance.
-Status: `executed-success`.
-
-**Pin-map cross-check** — this is the step that makes the pinout trustworthy:
-
-```bash
-curl … contents/Arduino/examples/02_E-Paper_Example/DEV_Config.h?ref=$SHA | grep -E 'EPD_.*_PIN'
-# EPD_SCK_PIN 11 / EPD_MOSI_PIN 12 / EPD_CS_PIN 10
-# EPD_RST_PIN 46 / EPD_DC_PIN 9  / EPD_BUSY_PIN 3
-```
-
-All six match the schematic's allocation table. Status: `executed-success`.
-
-## 8. Duplicate detection against the existing knowledge base
-
-```bash
-sha256sum components/nxp/pcf85063a/artifacts/*.pdf
-# a09223db…  pcf85063a-datasheet.pdf              726 288 B  (already held, NXP, Rev. 7)
-sha256sum dl/PCF85063ATL.pdf
-# 93b38487…                                        535 722 B  (new, Waveshare, Rev. 6)
-```
-
-Different hash **and** different size → per the method, **keep both and investigate**.
-Revisions extracted from each PDF confirmed Rev. 7 (2018) vs Rev. 6 (2015).
-Status: `executed-success`. See
-[C-WS11](gaps-and-conflicts.md#c-ws11--waveshare-mirrors-a-nine-year-old-rtc-datasheet).
-
-## 9. Not run — and why
-
-| Command | Why not | Where recorded |
-|---|---|---|
-| `git clone` of the vendor repo | ~50 MB; API reads answered the questions asked | [G2](gaps-and-conflicts.md#gaps) |
-| Download of `260304.bin` / `260314.bin` | 2 × 16 MB, plus 21 MB of xiaozhi images | [G3](gaps-and-conflicts.md#gaps), [manifest](acquisition/manifest.json) |
-| `tools/esp_image_info.py` on the firmware | Depends on the download above | [G3](gaps-and-conflicts.md#gaps) |
-| Any `esptool` operation | **No hardware.** The flash command in [`development.md`](development.md) is labelled `inferred` and must not be run unverified | [development.md](development.md#flashing) |
-| Rendering schematic page 1 | No rasteriser available on this host | [G1](gaps-and-conflicts.md#gaps) |
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/development.md b/devices/waveshare/esp32-s3-epaper-3.97/development.md
deleted file mode 100644
index 08a81e3..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/development.md
+++ /dev/null
@@ -1,212 +0,0 @@
-# Development, examples and firmware — Waveshare ESP32-S3-ePaper-3.97
-
-> Research snapshot **2026-09-01**. **Nothing here was built, flashed or run.**
-> Every procedure is `reported-working` (it is what the vendor publishes) or
-> `inferred`. There is no `executed-success` claim about the device in this file.
-
-## Target summary
-
-| Field | Value | Evidence |
-|---|---|---|
-| MCU | ESP32-S3R8 in an **`ESP32-S3-WROOM-1-N16R8`** module | schematic part label `S05` |
-| Flash | **16 MB** external (module) | `N16R8` suffix; docs `S02` |
-| PSRAM | **8 MB octal** | `N16R8`; consumes GPIO35–37 |
-| Console / flashing | **USB Type-C → native USB** (GPIO19/20) | schematic `S05` |
-| USB-UART bridge | **none fitted** | no bridge part in the schematic text layer; `inferred` |
-| Download mode | Hold **BOOT**, power on again | docs `S02` |
-| Frameworks | **Arduino IDE** and **ESP-IDF** — vendor supports both | docs `S02` |
-| Board support package | **none published** on the Espressif component registry (unlike some Waveshare boards) | `inferred` from absence in `S03` |
-
-Because there is **no USB-UART bridge**, the serial port disappears when the
-application crashes or when USB-CDC is not initialised. That is the normal
-native-USB ESP32-S3 trade-off, and the BOOT-button entry path is the recovery.
-`inferred` from the connector census — not tested.
-
-## Official examples
-
-From `waveshareteam/ESP32-S3-ePaper-3.97` at commit
-**`9b12d40731a80213b927ee8a421cae4082952819`** (2026-03-20). Enumerated from the
-repository tree; **not cloned, not built** ([G2](gaps-and-conflicts.md#gaps)).
-
-### Arduino — `Arduino/examples/`
-
-| Example | Exercises | Notable contents |
-|---|---|---|
-| `01_Audio_Test` | [ES8311](../../../components/everest-semiconductor/es8311/README.md) codec + mic + [NS4150B](../../../components/nsiway/ns4150b/README.md) | Ships its own `es8311.cpp`/`es8311_reg.h` rather than a library |
-| `02_E-Paper_Example` | **The display** | `EPD_3in97.cpp/.h`, `GUI_Paint`, six fonts incl. two CJK. **This is the reference for the pin map** |
-| `03_I2C_PCF85063` | [RTC](../../../components/nxp/pcf85063a/README.md) | Adds `i2c_bsp.c`, `i2c_equipment.cpp`, `user_config.h` |
-| `04_I2C_SHTC3` | [Temp/humidity](../../../components/sensirion/shtc3/README.md) | |
-| `05_SD_Test` | microSD | **Read this to settle [C-WS5](gaps-and-conflicts.md#c-ws5--sd-card-spi-names-but-4-bit-nets)** |
-| `06_QMI8658A` | [IMU](../../../components/qst/qmi8658a/README.md) | Uses the bundled `SensorLib` |
-
-Bundled library: `Arduino/libraries/SensorLib` — upstream is `lewisxhe/SensorLib`.
-**Version and modification status not determined** in this pass; per the method's
-vendored-dependency rule that is an open item, not an assumption of equivalence.
-
-### ESP-IDF — `ESP-IDF/`
-
-| Project | Exercises |
-|---|---|
-| `01_E-Paper_Example` | Display |
-| `02_Mic_test` | Microphone capture |
-| `03_Music` | Playback through the amplifier |
-| `04_SD_Test` | microSD |
-| `05_QMI8658A` | IMU |
-| `06_I2C_PCF85063` | RTC |
-| `07_I2C_SHTC3` | Temp/humidity |
-| `08_ESP32-S3_e-Paper-3.97` | **The integrated application** — this is the one that contains `components/axpPower/` |
-
-`08_…/components/axpPower/` vendors **XPowersLib** (`lewisxhe`): `XPowersLib.h`,
-`XPowersAXP2101.tpp`, `XPowersCommon.tpp`, `XPowersLibInterface.cpp`, and
-`REG/AXP2101Constants.h` alongside constants for AXP192/AXP202/AXP216, BQ25896,
-SY6970 and HUSB238 that this board does not fit. Waveshare's own wrapper is
-`axp_prot.cpp` / `axp_prot.h`.
-
-**No ESP-IDF or Arduino-core version is declared anywhere** in the repository or the
-docs — no `idf_component.yml` version pin, no `platformio.ini`, no stated minimum.
-That is a genuine gap: contrast the
-[Knob-Touch-LCD board](../esp32-s3-knob-touch-lcd-1.8/development.md), where
-Waveshare states its toolchain versions.
-
-## What the vendor's power code actually does
-
-This is the highest-value read in the repository, because it settles
-[C-WS2](gaps-and-conflicts.md#c-ws2--tg28-versus-axp2101) and gives real numbers.
-From `ESP-IDF/08_ESP32-S3_e-Paper-3.97/components/axpPower/axp_prot.cpp` at `9b12d40`:
-
-```cpp
-static XPowersPMU axp2101;                                    // :14
-axp2101.begin(AXP2101_SLAVE_ADDRESS, read, write)             // :40
-axp2101.setVbusVoltageLimit(XPOWERS_AXP2101_VBUS_VOL_LIM_4V36);  // :46
-axp2101.setVbusCurrentLimit(XPOWERS_AXP2101_VBUS_CUR_LIM_1500MA);// :47
-axp2101.setSysPowerDownVoltage(2600);                         // :50
-axp2101.setDC1Voltage(3300);                                  // :53
-axp2101.setALDO1Voltage(3300); …ALDO2… …ALDO3…                // :55–57
-axp2101.setChargerConstantCurr(XPOWERS_AXP2101_CHG_CUR_200MA);// :102
-axp2101.setChargeTargetVoltage(XPOWERS_AXP2101_CHG_VOL_4V2);  // :106
-axp2101.setWatchdogTimeout(XPOWERS_AXP2101_WDT_TIMEOUT_4S);   // :111
-axp2101.setButtonBatteryChargeVoltage(3000);                  // :116
-axp2101.enableButtonBatteryCharge();                          // :117
-axp2101.setLowBatWarnThreshold(10);                           // :119
-```
-
-Full table in [pinouts-and-buses.md § Power domains](pinouts-and-buses.md#power-domains).
-
-### Audit notes against the AXP2101 datasheet
-
-Read side by side with
-[`components/x-powers/axp2101`](../../../components/x-powers/axp2101/README.md)
-(datasheet V1.4 held). Findings, all `inferred` from reading — none reproduced on
-hardware:
-
-1. **The PMIC watchdog is enabled with a 4 s timeout and routed to a pin**
-   (`:110`–`:112`), and the commented-out `clrWatchdog()` at `:113` means **the
-   sampled code never feeds it**. If `XPOWERS_AXP2101_WDT_IRQ_TO_PIN` only raises
-   `PWR_IRQ` this is benign; if a later configuration promotes it to reset, an
-   application that does not feed the dog gets a 4-second reboot loop. **Flagged as
-   a latent trap, not an active defect** — the mode configured is the IRQ one.
-2. **`setSysPowerDownVoltage(2600)`** is a hard cut-off at 2.6 V system rail. For a
-   single Li-ion that is well below the cell's safe floor, so the *battery*
-   protection is expected to act first — the AXP2101 value is a backstop.
-3. **RTC coin-cell charging is enabled unconditionally** at 3.0 V (`:116`–`:117`).
-   If a user fits a **non-rechargeable** cell to `H4`, this charges a primary cell.
-   Worth a warning in any derived product. `inferred` — the header is documented
-   only as "RTC backup battery".
-4. **Charging is fixed at 200 mA CC / 4.2 V** with no battery-capacity awareness.
-   Fine for the bundled cell; check it if you fit a small one.
-
-## Flashing
-
-### Factory restore
-
-Two images in `Firmware/Factory procedure/`, each **16 777 216 bytes** — a full
-16 MB flash image, so they are merged images:
-
-| File | Bytes | Role |
-|---|---|---|
-| `260304.bin` | 16 777 216 | Full-flash factory image |
-| `260314.bin` | 16 777 216 | Full-flash factory image, later build |
-
-`Firmware/ReadMe_EN.txt`, verbatim:
-
-```
-Burn the website
-https://espressif.github.io/esp-launchpad/
-
-Burn the starting address
-0x0
-```
-
-So: **offset `0x0`**, via ESP Launchpad or equivalently `esptool`. The filenames look
-like dates (`26-03-04`, `26-03-14`) consistent with the repository's commit history,
-but that is a **reading of a filename, not a build identifier** — no image header was
-parsed. `inferred`.
-
-**Inferred equivalent, NOT tested — do not treat as authoritative:**
-
-```bash
-# INFERRED from the vendor's stated offset. Not executed. Back up first.
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-           write_flash 0x0 260314.bin
-```
-
-Neither image was downloaded ([G3](gaps-and-conflicts.md#gaps)); both are recorded in
-[`acquisition/manifest.json`](acquisition/manifest.json) with URLs and expected sizes
-so a later pass can fetch and hash them.
-
-### The xiaozhi AI-voice firmware
-
-`Firmware/xiaozhi/` ships two prebuilt images:
-
-| File | Bytes | Per `ReadMe_EN.txt` |
-|---|---|---|
-| `ESP32-S3_e-Paper-3.97_xiaozhi.bin` | 9 920 235 | "Pure voice, no display" |
-| `ESP32-S3_e-Paper-3.97_xiaozhi-xs.bin` | 11 179 471 | "The e-ink screen is displayed in landscape" |
-
-Upstream source is **`github.com/78/xiaozhi-esp32`**, which the repository README
-points at explicitly ("Please visit the official source code"). This is what the
-storefront means by "AI Voice Interaction" and "access to online large model
-platforms such as DeepSeek, Doubao" — **a third-party open-source assistant firmware,
-not a Waveshare service.** Worth knowing before buying the board for that feature:
-the cloud dependency and its terms are xiaozhi's, not Waveshare's.
-
-**Neither image was downloaded or parsed.** No SHA-256, no partition map, no IDF
-version. Recorded in the acquisition manifest.
-
-## Licensing
-
-| Artifact | Licence | Evidence | Redistribution | Disposition |
-|---|---|---|---|---|
-| `waveshareteam/ESP32-S3-ePaper-3.97` | **`unknown`** | No `LICENSE` file; GitHub API reports `license: null` | `unknown` | reference-only (not vendored) |
-| Bundled `XPowersLib` | upstream is MIT — **not verified in the vendored copy** | `inferred` | `unknown` | not vendored |
-| Bundled `SensorLib` | upstream MIT — **not verified** | `inferred` | `unknown` | not vendored |
-| Schematic PDF | `unknown` — no notice in the document | `unknown` | repository |
-| Panel manual, IC datasheets | `unknown` — vendor documents, no stated terms | `unknown` | repository |
-
-Per the method, licence is **metadata, not a gate**: everything useful was fetched,
-and `unknown` is the ordinary value here. Nothing was omitted over licensing.
-
-Note the contrast with Waveshare's ESP32-P4 repositories, which
-[the vendor guide §8.4](../../../vendors/waveshare/README.md) records as
-**Apache-2.0**. This repository is not licensed. That is a per-repository fact, not a
-vendor-wide one.
-
-## What a first project should do
-
-`inferred` guidance, offered as a starting order rather than a tested procedure:
-
-1. Flash `260314.bin` at `0x0` **after** dumping the existing flash — there is no
-   published guarantee the images match a given board revision.
-2. Build `Arduino/examples/02_E-Paper_Example` first. It is the smallest thing that
-   proves toolchain, USB and panel together, and its pin map is corroborated by the
-   schematic.
-3. Add the AXP2101 early rather than late. On a board where the PMIC owns the panel
-   rail and the power button, ignoring it makes battery behaviour inexplicable.
-4. Treat GPIO43/44 carefully — they are the console *and* the LEDs
-   ([C-WS9 neighbourhood](gaps-and-conflicts.md)).
-
-## See also
-
-- [Device record](README.md) · [Pinouts and buses](pinouts-and-buses.md)
-- [Conflicts](gaps-and-conflicts.md) · [Sources](sources.md) · [Commands](commands.md)
-- [Acquisition manifest](acquisition/manifest.json)
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md b/devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md
deleted file mode 100644
index 7433cef..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md
+++ /dev/null
@@ -1,287 +0,0 @@
-# Conflicts, gaps and unresolved identities — Waveshare ESP32-S3-ePaper-3.97
-
-> Research snapshot **2026-09-01**. Nothing verified against hardware.
-> Conflicts are **recorded, not resolved by preference** — per the
-> [method](../../../.agents/skills/hardware-device-research/SKILL.md#conflict-protocol).
-> Where a trust order is applied it is this repository's existing Waveshare rule
-> ([vendor guide §4](../../../vendors/waveshare/README.md)): **schematic > demo source
-> > wiki/docs > storefront**.
-
-## Contents
-
-| ID | Subject | Status |
-|---|---|---|
-| [C-WS1](#c-ws1--the-expansion-claim-is-backwards) | The board has no expansion header | **resolved — the claim it backed is refuted** |
-| [C-WS2](#c-ws2--tg28-versus-axp2101) | PMIC named `TG28` by marketing, `AXP2101` by schematic and firmware | **resolved in favour of AXP2101** |
-| [C-WS3](#c-ws3--the-storefront-swaps-flash-and-psram) | Storefront says 8 MB flash / 16 MB PSRAM | **resolved — storefront is wrong** |
-| [C-WS4](#c-ws4--io-expander-column-heading-with-no-io-expander-part) | `IO Expander` heading, no such part | **unresolved** |
-| [C-WS5](#c-ws5--sd-card-spi-names-but-4-bit-nets) | SD wired 1-bit SPI or 4-bit? | **unresolved** |
-| [C-WS6](#c-ws6--refresh-times-disagree-between-module-and-panel-documents) | Refresh timings differ panel vs storefront | **unresolved — different measurement scopes** |
-| [C-WS7](#c-ws7--gate-versus-source-orientation) | Panel manual says 800 gate × 480 source | **unresolved — contradicts register evidence next door** |
-| [C-WS8](#c-ws8--is-this-the-same-panel-as-the-papermonos) | Same panel as the PaperMono? | **unresolved — strong circumstantial match** |
-| [C-WS9](#c-ws9--gpio39-carries-two-functions) | GPIO39 double-assigned | **unresolved** |
-| [C-WS10](#c-ws10--first-pass-recorded-absences-that-are-not-real) | An earlier pass in this same session recorded false absences | **resolved — corrected, history kept** |
-| [C-WS11](#c-ws11--waveshare-mirrors-a-nine-year-old-rtc-datasheet) | Waveshare's PCF85063A mirror is Rev. 6 (2015) | **resolved — both copies kept** |
-| [G1–G6](#gaps) | Open gaps | — |
-
----
-
-## C-WS1 — the expansion claim is backwards
-
-**The claim.** The [PaperMono record](../../m5stack/papermono/README.md#when-to-use--when-not-to-use)
-advises that for "a general e-paper development board **with expansion**", a reader
-should "prefer Inkplate or a Waveshare ESP32 e-paper board". That advice is what
-[C24](../../m5stack/papermono/gaps-and-conflicts.md) asked this record to substantiate.
-
-**What the evidence shows.** The ESP32-S3-ePaper-3.97 — the Waveshare board that is
-otherwise the *closest possible* substitute for a PaperMono — **has no expansion
-header at all.** Its complete connector census from the schematic
-([pinouts §"There is no expansion header"](pinouts-and-buses.md#there-is-no-expansion-header))
-is: one USB-C, three PH1.25-2P power/speaker JSTs, the panel FPC, and a microSD
-socket. No 2.54 mm header, no Qwiic/easyC, no broken-out GPIO.
-
-Additionally, **every usable GPIO is committed** — GPIO35–37 are consumed by the
-module's octal PSRAM, and GPIO7 is the only table row without a function, itself
-probably `SD_D1`.
-
-**Resolution.** The Waveshare recommendation is now *backed by an internal record*,
-which is what C24 required — but the specific reason given for it ("with expansion")
-is **refuted for this board**. Recorded rather than quietly reworded.
-
-**Where the claim *is* true.** Waveshare's smaller e-paper boards do carry expansion:
-the [ESP32-S3-ePaper-1.54](../esp32-s3-epaper-1.54/README.md) and
-[ESP32-C6-ePaper-1.54](../esp32-c6-epaper-1.54/README.md) both document a
-"reserved 2 × 6 2.54 mm pitch female header interface for external expansion", and
-the C6 adds a TCA9554 I/O expander. So the honest form of the advice is:
-
-> *For e-paper development **with expansion**, Waveshare's option is a **1.54-inch
-> 200 × 200** board, not a PaperMono-sized one. You trade almost all the display
-> to get the header.*
-
-`inferred` from vendor documentation; the 1.54 boards' schematics were not retrieved
-in this pass.
-
-## C-WS2 — `TG28` versus `AXP2101`
-
-| Source | Says | Class |
-|---|---|---|
-| Storefront "What's On Board" (`S01`) | "**TG28** — highly integrated power management chip" | primary, marketing |
-| `docs.waveshare.com` overview (`S02`) | "Onboard **TG28** power management chip" | primary, documentation |
-| **Schematic** (`S05`) | Part label **`AXP2101`**, with pin nets `ALDOIN`, `ALDO1`–`ALDO4`, `BLDOIN`, `BLDO1`–`BLDO2`, `DLDO1/DC1SW`, `DLDO2/DC4SW`, `CPUSLDO`, `VSYS`, `PWRON`, `PWROK`, `VBACKUP` | **primary, design data** |
-| **Vendor firmware** (`S09`) | Component directory `axpPower/`; `static XPowersPMU axp2101;`; `axp2101.begin(AXP2101_SLAVE_ADDRESS, …)`; vendored `REG/AXP2101Constants.h` and `XPowersAXP2101.tpp` | **primary, source** |
-
-**Resolution: the fitted part is an [X-Powers AXP2101](../../../components/x-powers/axp2101/README.md).**
-The schematic net names are the AXP2101's own pin names and could not plausibly
-belong to a different device, and Waveshare's own firmware drives it through
-XPowersLib's AXP2101 path. Under this repository's Waveshare trust order
-(schematic > demo source > docs > storefront), both of the higher-ranked sources
-agree against both of the lower-ranked ones.
-
-**What `TG28` is remains unexplained.** It may be a package/marking variant, a
-second-source or rebadge, or simply an error propagated from another product's copy.
-No datasheet, product page or registry entry for a PMIC called "TG28" was found in
-this pass. **Do not create a `tg28` component record** — it would be a part number
-promoted from marketing copy, exactly what the method's
-[evidence-discipline rules](../../../.agents/skills/hardware-device-research/SKILL.md#evidence-discipline-and-known-failure-modes)
-forbid.
-
-**Practical consequence:** write firmware against the AXP2101 register map. The
-vendor's own code already does.
-
-## C-WS3 — the storefront swaps flash and PSRAM
-
-| Source | Claim |
-|---|---|
-| Storefront feature bullets | "integrated **8MB PSRAM** and external **16MB Flash**" ✅ |
-| Storefront "What's On Board" | "ESP32-S3-WROOM-1-N16R8 … with integrated **8MB Flash and 16MB PSRAM**" ❌ |
-| `docs.waveshare.com` | "stacked with **16MB Flash and 8MB PSRAM**" ✅ |
-| Schematic part label | `ESP32-S3-WROOM-1-N16R8` |
-
-**Resolution: 16 MB flash, 8 MB PSRAM.** The module part number decides it —
-Espressif's `N16R8` suffix means N=16 MB flash, R8=8 MB PSRAM. The storefront
-contradicts *itself* within one page; the "What's On Board" block is wrong.
-
-Minor, but it is the kind of error that gets copied into a partition table.
-
-## C-WS4 — `IO Expander` column heading with no I/O expander part
-
-The schematic's GPIO allocation table heads its `GPxx` column **"IO Expander"**, yet
-no I/O expander appears anywhere in the extracted text — no TCA9554, PCA95xx or
-PCAL6416.
-
-The sibling [ESP32-C6-ePaper-1.54](../esp32-c6-epaper-1.54/README.md) *does* fit a
-TCA9554 and Waveshare documents it. Most probable explanation: **template reuse from
-a sibling board's schematic**.
-
-**Unresolved.** Text extraction cannot prove absence of a symbol. What would settle
-it: rendering the sheet, or a photograph of the PCB back. Until then **no component
-record has been created**, and no claim of an I/O expander appears in the device
-record. Per the method, a heading is not a reading.
-
-## C-WS5 — SD card: SPI names but 4-bit nets
-
-Net names are SPI-flavoured (`SD_CLK`, `SD_MOSI`, `SD_MISO`, `SD_CS`) but `SD_D1` and
-`SD_D2` are also present — which only make sense in 4-bit SDMMC.
-
-Two readings, both plausible: the board is wired for 4-bit SDMMC and the vendor
-simply named the nets after the SPI roles those pins take in 1-bit mode; or `D1`/`D2`
-are pulled up and unused.
-
-**Unresolved.** The vendor's `04_SD_Test` / `05_SD_Test` examples were not read in
-this pass — that is the cheapest way to settle it and is the first thing a follow-up
-should do. Compare Waveshare's
-[Knob-Touch-LCD-1.8](../esp32-s3-knob-touch-lcd-1.8/README.md), which uses genuine
-4-bit SDMMC.
-
-## C-WS6 — refresh times disagree between module and panel documents
-
-| Mode | Storefront / docs (`S01`, `S02`) | Panel manual (`S06`) |
-|---|---|---|
-| Full | 3.5 s | — |
-| Fast | 2.8 s | — |
-| Partial | 0.6 s | **0.3 s** |
-| 4-greyscale | 3.5 s | **3 s @ 23 °C** |
-
-**Unresolved, and probably not a true contradiction.** The panel manual measures the
-*panel* under a stated condition (23 °C, a defined transition pattern, Tektronix
-TCP0030A probe); the storefront figures are unlabelled as to temperature, waveform or
-whether they include the host's SPI transfer time. A board-level number being slower
-than a panel-level number is expected.
-
-**Do not present either as measured performance.** Both are `reported-working`
-vendor claims obtained under different, partly undisclosed conditions. The
-[PaperMono record makes the same point about its own numbers](../../m5stack/papermono/performance.md),
-and the comparison between the two boards' published refresh figures is therefore
-**not admissible** — see
-[comparisons](../../m5stack/papermono/comparisons-and-recommendations.md).
-
-## C-WS7 — gate versus source orientation
-
-The panel manual states **"4-3: Resolution: 800 gate × 480 source"** (`S06`).
-
-This knowledge base's [DKE DEPG0397BBS770F3 record](../../../components/dke/depg0397bbs770f3/README.md)
-establishes the opposite for the PaperMono's 3.97" panel — **800 source × 480 gate** —
-and does so from *register evidence*: SSD1677 command `0x44` sets `XEA = 0x31F = 799`
-(800 source columns) and `0x01` sets MUX = 480 gate lines, with the 48 000-byte frame
-size confirming it.
-
-**Unresolved.** Either the two panels genuinely differ in scan orientation, or
-Waveshare's manual has the terms transposed. The DKE record already documents that
-*its* manual contradicts its own mechanical drawing on this exact point (§8-C3), so a
-transposition error in a document of this class has precedent.
-
-**Practical impact: low.** Drivers address the framebuffer, and the vendor's
-`EPD_3in97.h` declares `WIDTH 800`, `HEIGHT 480`. The conflict matters only if you
-write your own controller init.
-
-## C-WS8 — is this the same panel as the PaperMono's?
-
-| Property | Waveshare 3.97" (`S06`) | DKE `DEPG0397BBS770F3` |
-|---|---|---|
-| Diagonal | 3.97" | 3.97" |
-| Resolution | 800 × 480 | 480 × 800 |
-| **Active area** | **86.40 × 51.84 mm** | **51.84 × 86.40 mm** |
-| **DPI** | **235** | **235** |
-| **Driver IC** | **SSD1677** | **SSD1677** |
-| Greyscale | 4 | 4 (marketed; manual's optical table says 2) |
-| Pixel pitch | 0.108 × 0.108 mm | — |
-| Outline | 56.24 × 96.62 × 0.92 mm | — |
-| Vendor part number | **not published by Waveshare** | `DEPG0397BBS770F3` |
-
-Active area matches **to 0.01 mm** transposed, DPI matches exactly, and both carry an
-**SSD1677**.
-
-**Still `inferred`, not established.** Waveshare does not name a panel supplier or
-part number anywhere — not on the storefront, not in the docs, not in the manual,
-not on the schematic's text layer. The match is consistent with the same panel, with
-two panels built to one reference design, or with two vendors independently choosing
-a common ESL-market part.
-
-**What would settle it:** a photograph of the FPC marking on either board, or a
-Waveshare-published panel part number. Recorded as an open question in both
-directions rather than asserted — the PaperMono record makes the same match and
-reaches the same non-conclusion.
-
-## C-WS9 — GPIO39 carries two functions
-
-The allocation table puts both `AudioCTR_PIN` (amplifier enable) and `AXIS_INT1`
-(IMU interrupt 1) on **GPIO39**.
-
-If literal, the two cannot coexist: an output gating an amplifier and an input
-taking an interrupt. More likely one of the two is a stale candidate assignment left
-in the table.
-
-**Unresolved.** Text adjacency cannot distinguish. Settle it by rendering the sheet
-or by reading the vendor's `01_Audio_Test` and `05_QMI8658A` examples.
-
-## C-WS10 — first pass recorded absences that are not real
-
-**Kept as history, per the method's requirement to record refuted hypotheses with the
-evidence and date that refuted them.**
-
-An earlier pass on this same board (this record's initial version, written
-2026-09-01) concluded that Waveshare publishes **no wiki page, no pinout, no
-schematic, no sample code, no price and no panel controller** for this product, and
-that "no artifacts were retained … nothing was downloaded". It reasoned from the
-legacy wiki returning 404 and from the MediaWiki API being broken.
-
-**All six absences are false.** What actually exists, retrieved 2026-09-01:
-
-| Claimed absent | Actually | Evidence |
-|---|---|---|
-| Documentation page | `https://docs.waveshare.com/ESP32-S3-ePaper-3.97` — HTTP 200, full docs | `S02` |
-| Schematic | `ESP32-S3_e-Paper-3.97-schematic.pdf`, 257 550 B, valid `%PDF` | `S05`, retained |
-| Pinout | Allocation table drawn on that schematic | [pinouts-and-buses.md](pinouts-and-buses.md) |
-| Sample code | `github.com/waveshareteam/ESP32-S3-ePaper-3.97` — 6 Arduino + 8 ESP-IDF examples, factory firmware | `S09` |
-| Price | **USD 34.99 – 47.99**, three SKUs | `S01` |
-| Panel controller | **SSD1677**, stated in the panel manual | `S06` |
-
-**Root cause — and it is a reusable lesson, not a one-off slip.** The legacy
-`/wiki/` route 404s for this product *because Waveshare migrated it*, and this
-repository's own
-[Waveshare vendor guide §8.2](../../../vendors/waveshare/README.md) already says
-**"There is a newer documentation platform … `docs.waveshare.com/<PRODUCT>` … Check
-it first."** The guide was written 2026-08-24 from the ESP32-P4 pass. It was not
-consulted, and a 404 on the deprecated host was read as product-level absence.
-
-This is precisely the failure mode the method names: **"Prove absence, not just
-presence."** A 404 on one host is evidence about that host.
-
-**Corrected in place**, with the original claims preserved here.
-
-## C-WS11 — Waveshare mirrors a nine-year-old RTC datasheet
-
-Waveshare serves the PCF85063A datasheet from `files.waveshare.com/wiki/common/`.
-Hashed against the copy this knowledge base already held from NXP:
-
-| Copy | Bytes | SHA-256 | Revision |
-|---|---|---|---|
-| NXP original (already held) | 726 288 | `a09223db…` | **Rev. 7**, 2018 |
-| **Waveshare mirror** (new) | 535 722 | `93b38487…` | **Rev. 6**, 2015 |
-
-**Both retained**, per the method's rule that same-document-different-hash means
-keep both and investigate. The Waveshare copy is **three years and one revision
-stale**. It documents what Waveshare ships to its customers; the NXP copy is what
-you should design against.
-
-This is the third independent confirmation of the vendor guide's
-"re-hosted third-party PDFs may be stale" warning.
-
----
-
-## Gaps
-
-| ID | Gap | Why it matters | Cheapest way to close |
-|---|---|---|---|
-| **G1** | **No rendered schematic sheet.** Text extraction only; no `pdftotext`/poppler on this host | Connectivity is inferred from text adjacency, not traced. C-WS4, C-WS9 and the panel-rail question all hinge on it | Render page 1 with any PDF rasteriser and read it |
-| **G2** | **Vendor examples not retrieved.** The 14 Arduino/ESP-IDF examples were enumerated but only `DEV_Config.h`, `EPD_3in97.h` and `axp_prot.cpp` were read | I²C addresses, SD bus width and the GPIO39 conflict are all answerable from them | Clone at `9b12d40` and read |
-| **G3** | **Factory firmware not downloaded.** Two 16 777 216-byte images (`260304.bin`, `260314.bin`) plus two xiaozhi images (9.9 MB, 11.2 MB) | ~54 MB. Would give partition map, IDF version, build date via `tools/esp_image_info.py` | See [acquisition/manifest.json](acquisition/manifest.json) — recorded, not fetched |
-| **G4** | **No imagery retained.** No board photo, no PCB shot, no dimension drawing | Cannot confirm connector census visually; C-WS4 stays open | `docs.waveshare.com` `Interfaces`/`Dimensions` sections carry figures |
-| **G5** | **No board dimensions.** The vendor publishes an outline drawing as an image only; no numeric size found | Enclosure work impossible | Read the dimension figure |
-| **G6** | **Nothing hardware-verified.** No unit in hand | Every behavioural claim is vendor-stated, source-read or inferred | Buy one (USD 34.99) |
-
-## Cross-record links
-
-- Closes [PaperMono C24](../../m5stack/papermono/gaps-and-conflicts.md)
-- Feeds [PaperMono comparisons §5](../../m5stack/papermono/comparisons-and-recommendations.md)
-- Vendor findings folded into [`vendors/waveshare`](../../../vendors/waveshare/README.md)
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/pinouts-and-buses.md b/devices/waveshare/esp32-s3-epaper-3.97/pinouts-and-buses.md
deleted file mode 100644
index 19058d1..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/pinouts-and-buses.md
+++ /dev/null
@@ -1,263 +0,0 @@
-# Pinouts and buses — Waveshare ESP32-S3-ePaper-3.97
-
-> Research snapshot **2026-09-01**. **No hardware in hand.** Every mapping below is
-> read from the published schematic or from the vendor's own driver source. The
-> *extraction* is `executed-success` (the commands are in [`commands.md`](commands.md)
-> and reproducible); the *electrical claims* are `not-tested`.
-
-## Where this comes from
-
-Two independent sources, which agree:
-
-| Source | What it gives | Evidence label |
-|---|---|---|
-| **[SCH]** `artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf` — Altium PDF, 1 sheet, 257 550 B, SHA-256 `b1203145…` | An **allocation table drawn on the sheet itself**, mapping every `GPxx` net to its subsystem | `executed-success` for the text extraction |
-| **[SRC]** `waveshareteam/ESP32-S3-ePaper-3.97` @ `9b12d40`, `Arduino/examples/02_E-Paper_Example/DEV_Config.h` lines 49–54 | The six e-paper pins as `#define`s the vendor actually compiles | `executed-success` for the read |
-
-**They agree on all six e-paper pins.** That cross-check is the reason the e-paper
-rows below are the most trustworthy in this document — two sources produced by
-different Waveshare teams, from different toolchains, matching exactly.
-
-### How the schematic text was recovered
-
-Waveshare's schematic is an Altium PDF publisher export. Per this repository's
-[Waveshare vendor guide §8.7](../../../vendors/waveshare/README.md), these normally
-resist `grep` because each glyph is emitted as its own text object with its own
-transform. There is no `pdftotext` on this host either.
-
-The route that worked — scripts are in [`tools/`](tools/) and the exact invocations
-in [`commands.md`](commands.md):
-
-1. `tools/pdftext.py` — inflate every `FlateDecode` stream, including **Form XObjects**
-   (the entire sheet lives in one XObject here, *not* in `/Contents`; a page-only
-   walker returns zero text and looks like "no text layer"), then interpret the
-   `BT`/`Tm`/`Td`/`Tj`/`TJ` operators to get `(x, y, glyph)`.
-2. `tools/reflow.py` — group glyphs by baseline, sort by x, join runs whose gap is
-   under threshold. 4 318 glyphs → 1 150 tokens.
-
-Result: `artifacts/schematic/schematic-text-reflowed.tsv`, retained so no one has to
-re-derive it.
-
-> **This is a reading aid, not a netlist.** It recovers *text adjacency*, not
-> electrical connectivity. Unlabelled wire-only connections are invisible to it.
-> Every row below is text that appears in the sheet's own allocation table; none of
-> it is traced connectivity. Where it matters, the vendor source corroborates.
-
-## The GPIO allocation table
-
-This is the table Waveshare draws beside the module symbol `U7`
-(`ESP32-S3-WROOM-1-N16R8`), transcribed. Its column headings are the vendor's own:
-`ePaper`, `Audio`, `SD Card`, `RTC`, `KEY & LED`, `QMI8658A`, `Power`, `OTS`.
-
-| GPIO | Net | Subsystem | Direction | Notes |
-|---|---|---|---|---|
-| GPIO0 | `ESP_BOOT` | OTS | in | Strapping pin — BOOT button |
-| GPIO1 | `PWR_OUT` | Power | — | [AXP2101](../../../components/x-powers/axp2101/README.md) domain |
-| GPIO2 | `ESP_CHG` | Power | — | Charge status from AXP2101 |
-| **GPIO3** | **`EPD_BUSY`** | **ePaper** | **in** | **Confirmed by [SRC] `EPD_BUSY_PIN 3`** |
-| GPIO4 | `Button_Up` | KEY & LED | in | Rotary switch, up |
-| GPIO5 | `Button_Function` | KEY & LED | in | Rotary switch, centre/press |
-| GPIO6 | `Button_Down` | KEY & LED | in | Rotary switch, down |
-| GPIO7 | — | — | — | **No assignment in the table.** See [free pins](#is-anything-free) |
-| GPIO8 | `SD_D2` | SD Card | i/o | |
-| **GPIO9** | **`EPD_DC`** | **ePaper** | **out** | **Confirmed by [SRC] `EPD_DC_PIN 9`** |
-| **GPIO10** | **`EPD_CS`** | **ePaper** | **out** | **Confirmed by [SRC] `EPD_CS_PIN 10`** |
-| **GPIO11** | **`EPD_SCK`** | **ePaper** | **out** | **Confirmed by [SRC] `EPD_SCK_PIN 11`** |
-| **GPIO12** | **`EPD_DIN`** | **ePaper** | **out** | SPI MOSI. **Confirmed by [SRC] `EPD_MOSI_PIN 12`** |
-| GPIO13 | `I2S_MCLK` | Audio | out | To [ES8311](../../../components/everest-semiconductor/es8311/README.md) |
-| GPIO14 | `I2S_SCLK` | Audio | out | |
-| GPIO15 | `SD_MISO` | SD Card | in | |
-| GPIO16 | `SD_CLK` | SD Card | out | |
-| GPIO17 | `SD_MOSI` | SD Card | out | |
-| GPIO18 | `SD_CS` | SD Card | out | |
-| GPIO19 | `ESP_USB_N` | OTS | i/o | Native USB D− |
-| GPIO20 | `ESP_USB_P` | OTS | i/o | Native USB D+ |
-| GPIO21 | `I2S_DSOUT` | Audio | out | |
-| GPIO35 | *NC* | OTS | — | Marked **NC** — consumed by the module's octal PSRAM, see [Is anything free?](#is-anything-free) |
-| GPIO36 | *NC* | OTS | — | Marked **NC** |
-| GPIO37 | *NC* | OTS | — | Marked **NC** |
-| GPIO38 | `PWR_IRQ` | Power | in | AXP2101 interrupt |
-| GPIO39 | `AudioCTR_PIN`, `AXIS_INT1` | Audio, QMI8658A | — | **Two functions on one pin** — see [conflicts](#pin-conflicts-and-shared-nets) |
-| GPIO40 | `AXIS_INT2` | QMI8658A | in | IMU interrupt 2 |
-| GPIO41 | `ESP_I2C_SDA` | *(shared bus)* | i/o | `Audio_SDA` + `RTC_SDA` + `AXIS_SDA` + `AXP_SDA` |
-| GPIO42 | `ESP_I2C_SCL` | *(shared bus)* | out | `Audio_SCL` + `RTC_SCL` + `AXSI_SCL` + `AXP_SCL` |
-| GPIO43 | `ESP_LED1`, `ESP_UART_RX` | KEY & LED, OTS | — | UART0 RXD0 also lands here |
-| GPIO44 | `ESP_LED2`, `ESP_UART_TX` | KEY & LED, OTS | — | UART0 TXD0 also lands here |
-| GPIO45 | `RTC_INT_ESP` | RTC | in | [PCF85063A](../../../components/nxp/pcf85063a/README.md) alarm/interrupt |
-| **GPIO46** | **`EPD_RST`** | **ePaper** | **out** | **Confirmed by [SRC] `EPD_RST_PIN 46`** |
-| GPIO47 | `I2S_LRCK` | Audio | out | |
-| GPIO48 | `I2S_DSDIN` | Audio | in | Microphone path |
-
-Source: **[SCH]**, allocation table at sheet coordinates y≈39–162, x≈159–370.
-Bold rows additionally **[SRC]**.
-
-### The one column heading that does not make sense
-
-The `GPxx` column carries the heading **"IO Expander"**. **No I/O expander part
-appears anywhere in the schematic's text layer** — no TCA9554, no PCA95xx, no
-PCAL6416. Its sibling the
-[ESP32-C6-ePaper-1.54](../esp32-c6-epaper-1.54/README.md) *does* fit a TCA9554 and
-Waveshare documents it explicitly, so the most likely reading is that this heading
-is **copied from a sibling board's schematic template**.
-
-Treated as an **unexplained label, not a part**. Per the method's rule against
-promoting a candidate to a finding, no `tca9554` component record was created.
-Tracked as [C-WS4](gaps-and-conflicts.md#c-ws4--io-expander-column-heading-with-no-io-expander-part).
-
-## Buses
-
-### E-paper — 4-wire SPI
-
-| Signal | GPIO | Panel pin role |
-|---|---|---|
-| `EPD_SCK` | 11 | SCL |
-| `EPD_DIN` | 12 | SDA (MOSI; write-only) |
-| `EPD_CS` | 10 | CS# |
-| `EPD_DC` | 9 | D/C# |
-| `EPD_RST` | 46 | RES# |
-| `EPD_BUSY` | 3 | BUSY |
-
-The panel is a **3.97" 800 × 480 module with an [SSD1677](../../../components/solomon-systech/ssd1677/README.md)
-bonded on** — see the [panel component record](../../../components/waveshare/3.97inch-e-paper/README.md).
-The SSD1677 supports 3-wire (9-bit) and 4-wire (8-bit) SPI selected by the `BS1`
-pin; the schematic carries a `BS`/`3-line SPI` / `4-line SPI` annotation and the
-vendor driver defines `D_9PIN 1`, so **4-wire is what the board uses**.
-
-There is **no software-controlled panel power rail**: `DEV_Config.h` sets
-`EPD_PWR_PIN -1`. Panel supply `EPD_VCC` comes from the AXP2101 rail labelled
-`EPD_VCC_AXP` on the sheet, so power gating is a PMIC operation, not a GPIO one.
-`not-tested`.
-
-The panel's high-voltage rails (`VGH`, `VGL`, `VSH1`, `VSH2`, `VSL`, `VCOM`, `VPP`)
-and the boost control pins `GDR` / `RESE` appear on the panel FPC connector `J2`,
-which is the SSD1677's **integrated DC-DC** doing the work — the board supplies no
-separate EPD boost converter. This matches the topology already documented for the
-[PaperMono's panel](../../../components/dke/depg0397bbs770f3/README.md).
-
-### I²C — one bus, four devices
-
-`ESP_I2C_SDA` = **GPIO41**, `ESP_I2C_SCL` = **GPIO42**. Everything shares it:
-
-| Device | Net alias on sheet | Address | Record |
-|---|---|---|---|
-| [AXP2101](../../../components/x-powers/axp2101/README.md) PMIC | `AXP_SDA` / `AXP_SCL` | `0x34` **[SRC]** | via `AXP2101_SLAVE_ADDRESS` |
-| [ES8311](../../../components/everest-semiconductor/es8311/README.md) codec | `Audio_SDA` / `Audio_SCL` | `0x18` (7-bit, `CE`=0) — **`inferred` from the datasheet, not read from board source** | |
-| [PCF85063A](../../../components/nxp/pcf85063a/README.md) RTC | `RTC_SDA` / `RTC_SCL` | `0x51` — **`inferred`** | |
-| [QMI8658A](../../../components/qst/qmi8658a/README.md) IMU | `AXIS_SDA` / `AXSI_SCL` *(vendor's typo)* | `0x6A`/`0x6B` — **`inferred`** | |
-
-Only the AXP2101 address is evidenced from this board's own source. The other three
-are the parts' usual addresses and are **not** confirmed against this board — a
-future pass should read them out of the ESP-IDF examples
-`06_I2C_PCF85063`, `07_I2C_SHTC3`, `05_QMI8658A`.
-
-The [SHTC3](../../../components/sensirion/shtc3/README.md) is also on this bus
-(fixed address `0x70`), though the sheet's allocation table gives it no column.
-
-### I²S — audio
-
-`I2S_MCLK` 13, `I2S_SCLK` 14, `I2S_LRCK` 47, `I2S_DSOUT` 21, `I2S_DSDIN` 48 — a
-standard 5-wire I²S to the ES8311, with `AudioCTR_PIN` on GPIO39 gating the
-[NS4150B](../../../components/nsiway/ns4150b/README.md) amplifier.
-
-### SD card — 1-bit SPI mode, not SDMMC
-
-`SD_CLK` 16, `SD_MOSI` 17, `SD_MISO` 15, `SD_CS` 18, plus `SD_D1` (GPIO7 region)
-and `SD_D2` (GPIO8). **The net names are SPI names** (`MOSI`/`MISO`/`CS`), which is
-a different choice from the 4-bit SDMMC used on Waveshare's
-[Knob-Touch-LCD board](../esp32-s3-knob-touch-lcd-1.8/README.md). `D1`/`D2` being
-present suggests 4-bit wiring exists even if the vendor example drives it as SPI —
-**unresolved**, tracked as [C-WS5](gaps-and-conflicts.md#c-ws5--sd-card-spi-names-but-4-bit-nets).
-
-## Pin conflicts and shared nets
-
-1. **GPIO39 carries two functions** — `AudioCTR_PIN` *and* `AXIS_INT1`. If both the
-   amplifier gate and the IMU interrupt genuinely land on GPIO39, they cannot both
-   be used as intended. Most likely the allocation table lists a *candidate*
-   assignment for one of them. **Unresolved** — needs the rendered sheet or a
-   continuity check. `inferred`.
-2. **GPIO43/44 are UART0 and the LEDs.** `ESP_UART_TX`/`RX` are the console. Driving
-   `ESP_LED1`/`ESP_LED2` on the same pins means **using the LEDs costs you the boot
-   log**, or vice versa.
-3. **One I²C bus for PMIC, codec, RTC and IMU.** A hung transaction takes out power
-   management with it. There is no second bus to fall back on.
-4. **GPIO0 is the BOOT strap** — normal ESP32-S3 caveat.
-
-## Is anything free?
-
-Practically, **no**. This is the single most important fact about the board for
-anyone arriving from the PaperMono comparison.
-
-- **GPIO7** is the only pin with no entry in the allocation table, and even that is
-  ambiguous: `SD_D1` sits at the same table row, so GPIO7 is most likely the SD
-  card's DAT1. **Do not assume GPIO7 is free.** `inferred`.
-- **GPIO35–37 are marked NC**, and that is not spare capacity — the fitted module is
-  an **`ESP32-S3-WROOM-1-N16R8`**, whose 8 MB PSRAM is **octal**, consuming
-  GPIO35/36/37 internally. Waveshare marking them NC is correct and they are not
-  usable. See [ESP32-S3R8](../../../components/espressif/esp32-s3r8/README.md).
-
-### There is no expansion header
-
-The board's only connectors are:
-
-| Designator | Type | Purpose |
-|---|---|---|
-| `H1` | USB Type-C receptacle | Power, native USB, flashing, console |
-| `H2` | **PH1.25-2P** | Speaker output (from NS4150B) |
-| `H3` | **PH1.25-2P** | 3.7 V Li-ion battery |
-| `H4` | **PH1.25-2P** | RTC backup battery (via `R61`, 0 Ω) |
-| `J2` | FPC | The e-paper panel itself |
-| — | microSD socket (`TF-07F`) | Storage |
-
-**No 2.54 mm header, no Qwiic/STEMMA/easyC connector, no broken-out GPIO of any
-kind.** `LSK1`–`LSK4` are solder links and `TP1`–`TP9` are test points, neither of
-which is a user expansion interface.
-
-This directly contradicts the framing that sent this research here — see
-[C-WS1](gaps-and-conflicts.md#c-ws1--the-expansion-claim-is-backwards) and the
-[PaperMono comparison](../../m5stack/papermono/comparisons-and-recommendations.md).
-Waveshare's **1.54-inch** e-paper boards *do* carry a 2×6 2.54 mm header; this one
-does not.
-
-## Power domains
-
-From the AXP2101 rails named on the sheet, cross-read against the vendor's
-`axp_prot.cpp`:
-
-| Rail | Set to | Evidence | Feeds |
-|---|---|---|---|
-| `DC1` | **3300 mV** | **[SRC]** `axp_prot.cpp:53` | `VCC3V3` main logic |
-| `ALDO1` | **3300 mV** | **[SRC]** `:55` | |
-| `ALDO2` | **3300 mV** | **[SRC]** `:56` | |
-| `ALDO3` | **3300 mV** | **[SRC]** `:57` | |
-| `ALDO4` | present on sheet | **[SCH]** | not configured in the sampled source |
-| `BLDO1`, `BLDO2` | present on sheet | **[SCH]** | `EPD_VCC_AXP` is a candidate consumer — **not established** |
-| `VBACKUP` | RTC coin cell, charge target **3000 mV** | **[SRC]** `:116` | `H4` |
-
-Which rail feeds the panel is **not established** from text extraction alone; it
-needs the rendered sheet. Tracked in [gaps-and-conflicts.md](gaps-and-conflicts.md).
-
-Charging, as configured by the vendor firmware **[SRC]** `axp_prot.cpp`:
-
-| Parameter | Value | Line |
-|---|---|---|
-| Precharge current | 50 mA | `:101` |
-| Constant current | **200 mA** | `:102` |
-| Termination current | 25 mA | `:103` |
-| Charge target voltage | **4.2 V** | `:106` |
-| System power-down voltage | 2600 mV | `:50` |
-| VBUS input limit | 4.36 V / **1500 mA** | `:46`–`:47` |
-| Low-battery warning | 10 % | `:119` |
-| PMIC watchdog | 4 s, IRQ to pin | `:110`–`:112` |
-| Power key off / on hold | 4 s / 1 s | `:61`, `:76` |
-
-These are **firmware defaults, not hardware limits** — a user program may change any
-of them. `reported-working` (they are what the shipped code sets; not measured).
-
-## See also
-
-- [Device record](README.md)
-- [Development, examples and firmware](development.md)
-- [Conflicts and unresolved identities](gaps-and-conflicts.md)
-- [Source table](sources.md)
-- [Command ledger](commands.md)
-- [Waveshare documentation-sourcing guide](../../../vendors/waveshare/README.md)
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/sources.md b/devices/waveshare/esp32-s3-epaper-3.97/sources.md
deleted file mode 100644
index cde7569..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/sources.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Sources — Waveshare ESP32-S3-ePaper-3.97
-
-> Retrieval date for every row: **2026-09-01**, unless stated otherwise.
-> `Class` is authority (`primary` / `credible mirror` / `community`);
-> `Medium` is format. Where a publisher gives no version or date, the cell reads
-> **`unknown`** rather than being omitted.
-
-## Primary — Waveshare
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope / limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| `S01` | ESP32-S3 3.97inch e-Paper Development Board | Waveshare | primary | store listing | `https://www.waveshare.com/esp32-s3-epaper-3.97.htm` | 2026-09-01 | `unknown` — no date on page | SKUs 33552/33810/33811, price USD 34.99–47.99, variant names, package contents, panel specs, onboard-part list | Marketing copy. **Self-contradictory on flash/PSRAM ([C-WS3](gaps-and-conflicts.md#c-ws3--the-storefront-swaps-flash-and-psram))** and names the PMIC `TG28` against the schematic ([C-WS2](gaps-and-conflicts.md#c-ws2--tg28-versus-axp2101)) | `artifacts/source-snapshots/storefront-esp32-s3-epaper-3.97-2026-09-01.html` |
-| `S02` | ESP32-S3-ePaper-3.97 — overview | Waveshare Documentation Platform | primary | official docs | `https://docs.waveshare.com/ESP32-S3-ePaper-3.97` | 2026-09-01 | `unknown` — Docusaurus v3.10.2, no doc date | SKU→variant table, feature list, onboard resources, supported frameworks | **This host is the current documentation platform; the legacy `/wiki/` 404s for this product.** No `oldid`-style pinning available | `artifacts/source-snapshots/docs-overview-2026-09-01.html` |
-| `S03` | ESP32-S3-ePaper-3.97 — Resources | Waveshare Documentation Platform | primary | official docs | `https://docs.waveshare.com/ESP32-S3-ePaper-3.97/Resources-And-Documents` | 2026-09-01 | `unknown` | The download set: schematic, panel manual, four IC datasheets, GitHub repo, community projects | The single highest-yield page for this product | `artifacts/source-snapshots/docs-resources-2026-09-01.html` |
-| `S04` | Storefront search, six query families | Waveshare | primary | store search | `https://www.waveshare.com/catalogsearch/result/?q=…` | 2026-09-01 | n/a | The **seven-product** ESP32 e-paper population used for the survey | Search index, not a catalogue export; a product absent from it is not proven absent | not retained (queries in [`commands.md`](commands.md)) |
-| `S05` | `ESP32-S3_e-Paper-3.97-schematic.pdf` | Waveshare | **primary — design data** | schematic | `https://files.waveshare.com/wiki/ESP32-S3-ePaper-3.97/ESP32-S3_e-Paper-3.97-schematic.pdf` | 2026-09-01 | `unknown` — no revision block found in the text layer | **AXP2101 identity, the full GPIO allocation table, the connector census, panel FPC rails** | Altium PDF, 1 sheet, glyph-per-object text. **Text adjacency, not traced connectivity.** No rendered read ([G1](gaps-and-conflicts.md#gaps)) | `artifacts/schematic/ESP32-S3_e-Paper-3.97-schematic.pdf` — 257 550 B, SHA-256 `b12031451374e2333e8eca2b8290c40b4c67955b1f12df17b96f3ee479e6f0be` |
-| `S06` | 3.97inch e-Paper — user manual | Waveshare | **primary** | datasheet/manual | `https://files.waveshare.com/wiki/3.97inch_e-Paper_HAT%2B/3.97inch_e-Paper.pdf` | 2026-09-01 | **Rev 1.0, 2025-04-24** ("New creation") | **Driver IC = SSD1677**, active area 86.40 × 51.84 mm, DPI 235, pixel 0.108 mm, 3-/4-wire SPI, refresh and power figures, temperature ranges | **Text layer is offset-encoded** — two subset fonts at +26/+29. Decoded and validated against the cover heading before any value was transcribed ([C-WS10 method note](gaps-and-conflicts.md)) | `components/waveshare/3.97inch-e-paper/artifacts/3.97inch-e-paper-manual-v1.0-2025-04-24.pdf` — 2 774 287 B, SHA-256 `4f756734dbfa7485c57e7ab7124f59f0afb00ca2600cda24a2285f02e4ab05cf` |
-| `S07` | Legacy wiki 404 for this product | Waveshare | primary | wiki | `https://www.waveshare.com/wiki/ESP32-S3-ePaper-3.97` | 2026-09-01 | n/a | **Negative result**: HTTP 404. The product was never on the legacy wiki, or was migrated off it | A 404 on the deprecated host is **not** evidence of product-level absence — see [C-WS10](gaps-and-conflicts.md#c-ws10--first-pass-recorded-absences-that-are-not-real) | not retained |
-| `S08` | `E-Paper_ESP32_Driver_Board` wiki page | Waveshare | primary | wiki | `https://www.waveshare.com/wiki/E-Paper_ESP32_Driver_Board` | 2026-09-01 | revisions dated 20220728, 20241230 | The driver board's specs, fixed pin map and 23-model panel compatibility list; establishes the legacy wiki still serves 200 for *older* products | Used for the [sibling stub](../e-paper-esp32-driver-board/README.md) | not retained |
-
-## Primary — Waveshare source code
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Version | Establishes | Scope / limitations |
-|---|---|---|---|---|---|---|---|---|---|
-| `S09` | `waveshareteam/ESP32-S3-ePaper-3.97` | Waveshare | **primary — source** | repository | `https://github.com/waveshareteam/ESP32-S3-ePaper-3.97` | 2026-09-01 | commit **`9b12d40731a80213b927ee8a421cae4082952819`**, 2026-03-20; repo created 2026-02-04; default branch `main`; **no `LICENSE` file — licence `unknown`** | E-paper pin map (`DEV_Config.h:49–54`), AXP2101 identity and charge configuration (`axp_prot.cpp`), example inventory, factory firmware images | Read via GitHub API at the pinned commit. **Tree listing and four files read; the examples themselves were not cloned** ([G2](gaps-and-conflicts.md#gaps)) |
-
-## Component-manufacturer documents obtained via Waveshare
-
-Filed under `components/` because **a document is filed by what it describes**, not
-by who served it. Waveshare's copy is retained where it differs from the original.
-
-| ID | Document | Publisher | Class | URL | Retrieved | Version | Local path | Note |
-|---|---|---|---|---|---|---|---|---|
-| `S10` | ES8311 datasheet | Everest Semiconductor, via Waveshare | **credible mirror** | `https://files.waveshare.com/wiki/common/ES8311.DS.pdf` | 2026-09-01 | `unknown` | `components/everest-semiconductor/es8311/artifacts/es8311-datasheet-waveshare-mirror.pdf` | 729 315 B, SHA-256 `be42a2cb…`. Everest original not obtained this pass |
-| `S11` | PCF85063A datasheet | NXP, via Waveshare | **credible mirror** | `https://files.waveshare.com/wiki/common/Pcf85063atl1118-NdPQpTGE-loeW7GbZ7.pdf` | 2026-09-01 | **Rev. 6, 2015** | `components/nxp/pcf85063a/artifacts/pcf85063a-datasheet-rev6-waveshare-mirror.pdf` | 535 722 B, SHA-256 `93b38487…`. **Stale** — KB already holds NXP Rev. 7 (2018). Both kept: [C-WS11](gaps-and-conflicts.md#c-ws11--waveshare-mirrors-a-nine-year-old-rtc-datasheet) |
-| `S12` | SHTC3 datasheet | Sensirion, via Waveshare | **credible mirror** | `https://files.waveshare.com/wiki/common/SHTC3_Datasheet.pdf` | 2026-09-01 | `unknown` | `components/sensirion/shtc3/artifacts/shtc3-datasheet-waveshare-mirror.pdf` | 928 256 B, SHA-256 `d315fe3d…` |
-| `S13` | AXP2101 datasheet V1.4 EN | X-Powers, via `lewisxhe/XPowersLib` | **credible mirror** | `https://raw.githubusercontent.com/lewisxhe/XPowersLib/master/datasheet/AXP2101_Datasheet_V1.4_en.pdf` | 2026-09-01 | **V1.4, English** | `components/x-powers/axp2101/artifacts/axp2101-datasheet-v1.4-en-xpowerslib-mirror.pdf` | 1 554 740 B, SHA-256 `9e51d16d…`. **X-Powers publishes no accessible primary URL found this pass**; two direct attempts failed ([acquisition](acquisition/manifest.json)) |
-
-## Community
-
-Non-authoritative. Listed with what each actually demonstrates.
-
-| ID | Title | Author | Class | Medium | URL | Retrieved | Evidence type | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| `S14` | Rustmix Wave v1.0.0 — open-source Rust firmware | `aimindseye` | community | repository + forum post | `https://github.com/aimindseye/rustmix-wave` · `https://www.reddit.com/r/esp32projects/comments/1tyngwy/` | 2026-09-01 | **demonstrable project** | Third-party firmware for this exact board exists — so the hardware is programmable outside the vendor stack. Linked from Waveshare's own docs `S03` | 
-| `S15` | Folloup Sticky | `alxv2016` | community | repository + model listing | `https://github.com/alxv2016/folloup-sticky/tree/folloup-waveshare` · `https://makerworld.com/en/models/3180226-folloup` | 2026-09-01 | **demonstrable project** | An enclosure and application built on this board |
-| `S16` | `78/xiaozhi-esp32` | `78` | community | repository | `https://github.com/78/xiaozhi-esp32` | 2026-09-01 | **upstream of a vendor-shipped binary** | Waveshare ships two prebuilt xiaozhi images for this board and points at this repo as the source of truth |
-
-Neither `S14` nor `S15` was cloned or built in this pass; both are recorded as
-catalogued-not-inspected. **No prevalence claim is made** — two projects linked by
-the vendor is not a measure of community size.
-
-## Cross-record sources used for comparison
-
-| ID | What | Where |
-|---|---|---|
-| `S17` | DKE `DEPG0397BBS770F3` panel record — active area, DPI, SSD1677, register-derived gate/source orientation | [`components/dke/depg0397bbs770f3`](../../../components/dke/depg0397bbs770f3/README.md) |
-| `S18` | SSD1677 controller record | [`components/solomon-systech/ssd1677`](../../../components/solomon-systech/ssd1677/README.md) |
-| `S19` | M5Stack PaperMono record and its performance/comparison pages | [`devices/m5stack/papermono`](../../m5stack/papermono/README.md) |
-| `S20` | Waveshare documentation-sourcing guide | [`vendors/waveshare`](../../../vendors/waveshare/README.md) |
-
-## Failed and negative retrievals
-
-Recorded because they save the next pass the attempt.
-
-| Target | URL | Result | Reading |
-|---|---|---|---|
-| Wiki page | `waveshare.com/wiki/ESP32-S3-ePaper-3.97` | **404** | Product not on legacy wiki; use `docs.waveshare.com` |
-| `docs` for driver board | `docs.waveshare.com/E-Paper-ESP32-Driver-Board` | **404** | Older products remain on the legacy wiki only — the two hosts are **disjoint**, not layered |
-| `docs` for PhotoPainter | `docs.waveshare.com/ESP32-S3-PhotoPainter` | **404** | ditto |
-| e-paper category page | `waveshare.com/product/displays/e-paper.htm` | 200 but **zero product links** | Category pages are JS-rendered; **use `/catalogsearch/result/?q=`** |
-| AXP2101 datasheet | `files.waveshare.com/wiki/common/AXP2101.pdf` | **404**, body is XML | Not in Waveshare's common pool |
-| AXP2101 datasheet | `github.com/lewisxhe/XPowersLib/raw/master/datasheet/AXP2101_Datasheet_V1.0_en.pdf` | **404**, body is HTML | Wrong filename — actual is `_V1.4_en.pdf`. **Neither was saved under a `.pdf` name** |
-
-## Validation performed
-
-Every retained binary was validated **by content, never by HTTP status**:
-
-```
-%PDF-  ESP32-S3_e-Paper-3.97-schematic.pdf        257 550 B
-%PDF-  3.97inch_e-Paper.pdf                     2 774 287 B
-%PDF-  ES8311.DS.pdf                              729 315 B
-%PDF-  Pcf85063atl…pdf                            535 722 B
-%PDF-  SHTC3_Datasheet.pdf                        928 256 B
-%PDF-  AXP2101_Datasheet_V1.4_en.pdf            1 554 740 B
-```
-
-Two candidate downloads failed this check and were **deleted rather than kept under a
-misleading extension** — see the table above. Commands in [`commands.md`](commands.md).
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/tools/deshift.py b/devices/waveshare/esp32-s3-epaper-3.97/tools/deshift.py
deleted file mode 100644
index 1a55389..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/tools/deshift.py
+++ /dev/null
@@ -1,38 +0,0 @@
-"""Decode Waveshare's offset-encoded PDF text layer.
-
-The 3.97inch e-Paper panel manual embeds two subset fonts whose code points are
-uniformly displaced from the real characters. Decoding is chr(ord(c)+K) with
-K=29 for one font and K=26 for the other. Validated against the known cover
-heading "3.97inch e-Paper" and the section word "Revision History".
-
-Per the method: a text layer must be validated against a known heading before
-any value is transcribed. This script exists so that validation is repeatable.
-"""
-import sys, collections
-
-def dec(s, k):
-    return ''.join(chr(ord(c)+k) if 0 < ord(c)+k < 0x2500 else c for c in s)
-
-WORDS = ('the','and','for','Paper','inch','Display','Panel','Driver','IC','Waveshare',
-         'Revision','Version','Content','Date','Page','Resolution','Voltage','Interface')
-
-def best(s):
-    cands = [(sum(w.lower() in dec(s,k).lower() for w in WORDS), k) for k in (29,26)]
-    cands.sort(reverse=True)
-    return dec(s, cands[0][1]), cands[0][1]
-
-rows = collections.defaultdict(list)
-for l in open(sys.argv[1], encoding='utf-8'):
-    p = l.rstrip('\n').split('\t')
-    if len(p) < 4: continue
-    rows[(p[0], round(float(p[2]),1))].append((float(p[1]), '\t'.join(p[3:])))
-
-lines = []
-for (o,y), v in rows.items():
-    lines.append((o, y, ''.join(t for x,t in sorted(v))))
-lines.sort(key=lambda r: (r[0], -r[1]))
-for o, y, s in lines:
-    d29, d26 = dec(s,29), dec(s,26)
-    # pick the one with more lowercase-looking English
-    pick = d29 if sum(c.islower() for c in d29) >= sum(c.islower() for c in d26) else d26
-    print(f'{o}\t{y}\t{pick}')
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/tools/pdftext.py b/devices/waveshare/esp32-s3-epaper-3.97/tools/pdftext.py
deleted file mode 100644
index ac33b99..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/tools/pdftext.py
+++ /dev/null
@@ -1,155 +0,0 @@
-"""Minimal pure-Python PDF text extractor with positions.
-
-No poppler/pypdf on this host. Parses the xref-free way: scan all stream
-objects, inflate FlateDecode ones, and interpret the content-stream text
-operators (BT/ET, Tf, Td/TD/Tm/T*, Tj/TJ/'/"). Also resolves simple
-/Differences-free WinAnsi text and hex strings.
-
-Emits TSV: page  x  y  text
-This is a reading aid, not an authority -- see AGENTS/skill guidance.
-"""
-import re, sys, zlib
-
-def objects(data):
-    """Yield (objnum, gen, dict_bytes, stream_bytes|None) for every 'N G obj'."""
-    for m in re.finditer(rb'(\d+)\s+(\d+)\s+obj\b', data):
-        start = m.end()
-        endm = re.compile(rb'\bendobj\b').search(data, start)
-        if not endm:
-            continue
-        body = data[start:endm.start()]
-        sm = re.search(rb'\bstream\r?\n', body)
-        stream = None
-        if sm:
-            em = body.rfind(b'endstream')
-            if em > sm.end():
-                stream = body[sm.end():em]
-                if stream.endswith(b'\r\n'): stream = stream[:-2]
-                elif stream.endswith(b'\n') or stream.endswith(b'\r'): stream = stream[:-1]
-            body = body[:sm.start()]
-        yield int(m.group(1)), int(m.group(2)), body, stream
-
-def inflate(dic, raw):
-    if raw is None: return None
-    if b'FlateDecode' not in dic: return raw
-    for trim in (0, 1, 2):
-        try:
-            return zlib.decompress(raw[trim:])
-        except zlib.error:
-            pass
-    try:
-        return zlib.decompressobj().decompress(raw)
-    except zlib.error:
-        return None
-
-STR = re.compile(rb'\((?:\\.|[^()\\])*\)|<[0-9A-Fa-f\s]*>', re.S)
-
-def decode_str(tok):
-    if tok.startswith(b'<'):
-        h = re.sub(rb'\s', b'', tok[1:-1])
-        if len(h) % 2: h += b'0'
-        b = bytes.fromhex(h.decode('ascii'))
-        # heuristics: UTF-16BE if lots of NULs
-        if b[:2] == b'\xfe\xff':
-            return b[2:].decode('utf-16-be', 'replace')
-        if len(b) >= 2 and b.count(0) > len(b) // 3:
-            return b.decode('utf-16-be', 'replace')
-        return b.decode('latin-1', 'replace')
-    s = tok[1:-1]
-    out, i = bytearray(), 0
-    while i < len(s):
-        c = s[i]
-        if c == 0x5c and i + 1 < len(s):
-            n = s[i+1]
-            mp = {0x6e: 10, 0x72: 13, 0x74: 9, 0x62: 8, 0x66: 12}
-            if n in mp: out.append(mp[n]); i += 2; continue
-            if 0x30 <= n <= 0x37:
-                j = i + 1; oct_ = b''
-                while j < len(s) and len(oct_) < 3 and 0x30 <= s[j] <= 0x37:
-                    oct_ += bytes([s[j]]); j += 1
-                out.append(int(oct_, 8) & 0xFF); i = j; continue
-            out.append(n); i += 2; continue
-        out.append(c); i += 1
-    return bytes(out).decode('latin-1', 'replace')
-
-NUM = rb'[-+]?[\d.]+'
-
-def extract(content):
-    """Return list of (x, y, text)."""
-    res = []
-    tm = [1, 0, 0, 1, 0, 0]
-    tlm = list(tm)
-    intext = False
-    # tokenize on operators we care about
-    pat = re.compile(
-        rb'(BT)|(ET)|'
-        rb'(' + NUM + rb')\s+(' + NUM + rb')\s+(' + NUM + rb')\s+(' + NUM + rb')\s+(' + NUM + rb')\s+(' + NUM + rb')\s+Tm|'
-        rb'(' + NUM + rb')\s+(' + NUM + rb')\s+(TD|Td)|'
-        rb'(T\*)|'
-        rb'(\[(?:[^\[\]\\]|\\.)*\])\s*TJ|'
-        rb'((?:\((?:\\.|[^()\\])*\)|<[0-9A-Fa-f\s]*>))\s*Tj', re.S)
-    for m in pat.finditer(content):
-        if m.group(1):
-            intext = True; tm = [1,0,0,1,0,0]; tlm = list(tm); continue
-        if m.group(2):
-            intext = False; continue
-        if m.group(3):
-            tm = [float(m.group(i)) for i in range(3, 9)]; tlm = list(tm); continue
-        if m.group(9):
-            dx, dy = float(m.group(9)), float(m.group(10))
-            tlm = [tlm[0], tlm[1], tlm[2], tlm[3], tlm[4] + dx*tlm[0] + dy*tlm[2], tlm[5] + dx*tlm[1] + dy*tlm[3]]
-            tm = list(tlm); continue
-        if m.group(12):
-            tlm = [tlm[0], tlm[1], tlm[2], tlm[3], tlm[4], tlm[5] - 12]
-            tm = list(tlm); continue
-        txt = None
-        if m.group(13):
-            parts = []
-            for t in STR.finditer(m.group(13)):
-                parts.append(decode_str(t.group(0)))
-            txt = ''.join(parts)
-        elif m.group(14):
-            txt = decode_str(m.group(14))
-        if txt:
-            res.append((round(tm[4], 2), round(tm[5], 2), txt))
-    return res
-
-def main(path):
-    data = open(path, 'rb').read()
-    pages = []
-    # collect content streams in object order; map page objects
-    streams = {}
-    page_objs = []
-    for num, gen, dic, raw in objects(data):
-        if raw is not None:
-            streams[num] = (dic, raw)
-        if re.search(rb'/Type\s*/Page\b', dic):
-            page_objs.append((num, dic))
-    page_objs.sort()
-    if not page_objs:
-        # fall back: dump all streams as one page
-        page_objs = [(0, b'')]
-    for pi, (pnum, pdic) in enumerate(page_objs, 1):
-        refs = []
-        cm = re.search(rb'/Contents\s*(?:(\d+)\s+\d+\s+R|\[(.*?)\])', pdic, re.S)
-        if cm:
-            if cm.group(1):
-                refs = [int(cm.group(1))]
-            else:
-                refs = [int(x) for x in re.findall(rb'(\d+)\s+\d+\s+R', cm.group(2))]
-        content = b''
-        for r in refs:
-            if r in streams:
-                d = inflate(*streams[r])
-                if d: content += d + b'\n'
-        if not content and pnum == 0:
-            for num, (dic, raw) in streams.items():
-                d = inflate(dic, raw)
-                if d and (b'BT' in d): content += d + b'\n'
-        pages.append(extract(content))
-    for i, items in enumerate(pages, 1):
-        for x, y, t in items:
-            print(f'{i}\t{x}\t{y}\t{t}')
-
-if __name__ == '__main__':
-    main(sys.argv[1])
diff --git a/devices/waveshare/esp32-s3-epaper-3.97/tools/reflow.py b/devices/waveshare/esp32-s3-epaper-3.97/tools/reflow.py
deleted file mode 100644
index ce8da3b..0000000
--- a/devices/waveshare/esp32-s3-epaper-3.97/tools/reflow.py
+++ /dev/null
@@ -1,41 +0,0 @@
-"""Reassemble per-glyph PDF text runs into words/lines.
-
-Altium's PDF publisher emits one Tj per glyph with its own Tm, so the raw
-extraction is a bag of single characters. Group by baseline y (rounded to a
-tolerance), sort by x, and join glyphs whose horizontal gap is below a
-threshold; larger gaps become separate tokens.
-
-Reading aid only: text adjacency, not electrical connectivity.
-"""
-import sys, collections
-
-tol   = float(sys.argv[2]) if len(sys.argv) > 2 else 1.2
-gap   = float(sys.argv[3]) if len(sys.argv) > 3 else 3.2
-
-rows = collections.defaultdict(list)
-for line in open(sys.argv[1], encoding='utf-8'):
-    p = line.rstrip('\n').split('\t')
-    if len(p) < 4: continue
-    obj, x, y, t = p[0], float(p[1]), float(p[2]), p[3]
-    rows[(obj, round(y / tol))].append((x, y, t))
-
-out = []
-for (obj, yk), items in rows.items():
-    items.sort()
-    toks, cur, curx = [], '', None
-    lastend = None
-    for x, y, t in items:
-        if lastend is not None and (x - lastend) > gap:
-            if cur: toks.append((curx, cur))
-            cur, curx = '', None
-        if not cur: curx = x
-        cur += t
-        lastend = x + 3.0 * len(t)
-    if cur: toks.append((curx, cur))
-    y = items[0][1]
-    for xx, tk in toks:
-        out.append((y, xx, tk))
-
-out.sort(key=lambda r: (-r[0], r[1]))
-for y, x, t in out:
-    print(f'{y:9.2f}\t{x:9.2f}\t{t}')
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md
index 35b9dce..4533f8f 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md
@@ -194,4 +194,4 @@ Flashing one does **not** touch the other, and a board with mismatched firmware
 
 No community source is retained without a permissive licence; two of the five retained projects declare MIT in prose only and are flagged as such.
 
-**On the original ZIPs (updated 2026-08-24).** All three vendor ZIPs have been moved to `archive/`, each only after (a) a full member-by-member reconciliation against what remains here, and (b) two independent, hash-verified download URLs. The Demo ZIP was the last and most carefully handled: its extraction is *not* complete here — two library trees were removed — so it was archived only once [`tools/restore-demo-deps.sh`](tools/README.md) was verified to reproduce those trees byte-for-byte from upstream. Full records, including what is and is not still on disk, in [`artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md`](artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md). See the root [artifact manifest](../../../artifact-manifest.md) for quantified duplicate storage.
+**On the original ZIPs (updated 2026-08-24).** All three vendor ZIPs have been moved to `../hardware-doc-archive/`, each only after (a) a full member-by-member reconciliation against what remains here, and (b) two independent, hash-verified download URLs. The Demo ZIP was the last and most carefully handled: its extraction is *not* complete here — two library trees were removed — so it was archived only once [`tools/restore-demo-deps.sh`](tools/README.md) was verified to reproduce those trees byte-for-byte from upstream. Full records, including what is and is not still on disk, in [`artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md`](artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md). See the root [artifact manifest](../../../artifact-manifest.md) for quantified duplicate storage.
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/CST816D_datasheet_En_V1.3.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/CST816D_datasheet_En_V1.3.pdf
deleted file mode 120000
index ebc9f01..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/CST816D_datasheet_En_V1.3.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/CST816D_datasheet_En_V1.3.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/Drv2605.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/Drv2605.pdf
deleted file mode 120000
index 5da4f48..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/Drv2605.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/Drv2605.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/README.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/README.md
index a9ac8d6..ccbd37c 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/README.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/README.md
@@ -5,7 +5,7 @@
 
 **This directory is now empty of PDFs.** Every file that was here has been moved — either into
 the matching `components/<vendor>/<part>/artifacts/` record (when it was a genuinely distinct
-document) or to `archive/` (when it was a byte-identical duplicate of a file
+document) or to `../hardware-doc-archive/` (when it was a byte-identical duplicate of a file
 already held in `components/`).
 
 Rationale: a component datasheet belongs in the component record, not in a device record. The
@@ -51,7 +51,7 @@ Totals: **28,392,294 bytes** relocated into `components/`; **3,576,806 bytes** a
 duplicates; 31,969,100 bytes accounted for in total.
 
 Archived files are at
-`archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/`.
+`../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/datasheets/`.
 Nothing was deleted.
 
 ## Why the older Espressif revisions were kept rather than archived
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/Arduino/libraries/lvgl b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/Arduino/libraries/lvgl
deleted file mode 120000
index 794b793..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/Arduino/libraries/lvgl
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/Arduino/libraries/lvgl
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.gitattributes b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.gitattributes
deleted file mode 100644
index 6bfd0d3..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.gitattributes
+++ /dev/null
@@ -1,3 +0,0 @@
-*.hpp linguist-language=C++
-
-
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.github b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.github
deleted file mode 120000
index ff562bf..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.github
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.github
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.gitignore b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.gitignore
deleted file mode 100644
index 4dd2b9c..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/.gitignore
+++ /dev/null
@@ -1,11 +0,0 @@
-.pio
-.vscode
-test
-.travis.yml
-test
-assets
-*.bk
-*.test
-build
-*.old
-sdkconfig
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/CMakeLists.txt b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/CMakeLists.txt
deleted file mode 120000
index 1a524d2..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/CMakeLists.txt
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/CMakeLists.txt
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/Kconfig b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/Kconfig
deleted file mode 120000
index 05db504..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/Kconfig
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/Kconfig
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/LICENSE b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/LICENSE
deleted file mode 120000
index 98b2b82..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/LICENSE
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/LICENSE
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/README.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/README.md
deleted file mode 120000
index 13c54ae..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/README.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/README.md
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/BMA423.PDF b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/BMA423.PDF
deleted file mode 120000
index e7890dc..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/BMA423.PDF
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/BMA423.PDF
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181 Application Note for Archtech.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181 Application Note for Archtech.pdf
deleted file mode 120000
index df04bdb..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181 Application Note for Archtech.pdf	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181 Application Note for Archtech.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181A3OP.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181A3OP.pdf
deleted file mode 120000
index 15b9be4..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181A3OP.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/CM32181A3OP.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/DRV2605.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/DRV2605.pdf
deleted file mode 120000
index 6c55139..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/DRV2605.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/DRV2605.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/GT911 Rev.10.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/GT911 Rev.10.pdf
deleted file mode 120000
index bbe9b45..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/GT911 Rev.10.pdf	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/GT911 Rev.10.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/HYM8563.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/HYM8563.pdf
deleted file mode 120000
index f9a660a..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/HYM8563.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/HYM8563.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/LTR-553ALS-01.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/LTR-553ALS-01.pdf
deleted file mode 120000
index 0676ca8..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/LTR-553ALS-01.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/LTR-553ALS-01.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF85063A.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF85063A.pdf
deleted file mode 120000
index 6100bf3..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF85063A.pdf
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF85063A.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF8563 Datasheet Rev.11.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF8563 Datasheet Rev.11.pdf
deleted file mode 120000
index 5f3d796..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF8563 Datasheet Rev.11.pdf	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/PCF8563 Datasheet Rev.11.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMC6310 Datasheet Rev.C.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMC6310 Datasheet Rev.C.pdf
deleted file mode 120000
index 61eacb1..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMC6310 Datasheet Rev.C.pdf	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMC6310 Datasheet Rev.C.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMI8658A Datasheet Rev A.pdf b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMI8658A Datasheet Rev A.pdf
deleted file mode 120000
index 3a00ba9..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMI8658A Datasheet Rev A.pdf	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/QMI8658A Datasheet Rev A.pdf
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/XL9555 Datasheet Rev2.3.PDF b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/XL9555 Datasheet Rev2.3.PDF
deleted file mode 120000
index 4658320..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/XL9555 Datasheet Rev2.3.PDF	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/datasheet/XL9555 Datasheet Rev2.3.PDF
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/examples b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/examples
deleted file mode 120000
index 36ad8fc..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/examples
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/examples
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/extras b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/extras
deleted file mode 120000
index 521b545..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/extras
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/extras
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/keywords.txt b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/keywords.txt
deleted file mode 120000
index 48d6e0f..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/keywords.txt
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/keywords.txt
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.json b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.json
deleted file mode 120000
index 7f53de8..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.json
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.json
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.properties b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.properties
deleted file mode 120000
index 30dbf22..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.properties
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/library.properties
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/platformio.ini b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/platformio.ini
deleted file mode 120000
index 6af611e..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/platformio.ini
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/platformio.ini
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/src b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/src
deleted file mode 120000
index a459be1..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/src
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/src
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/tools b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/tools
deleted file mode 120000
index 4cf88e9..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/tools
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/03_DRV2605_Test/components/SensorLib/tools
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/ARCHIVED-canon-pcm.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/ARCHIVED-canon-pcm.md
index 4a64442..77f6ea0 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/ARCHIVED-canon-pcm.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/ARCHIVED-canon-pcm.md
@@ -2,31 +2,29 @@
 
 Moved out of the repository on **2026-08-30**. Not deleted. 
 
-> **A symlink now stands in for each file at its original path**, pointing through this repo's
-> `archive/` link. With the archive present the paths resolve and the tree behaves as though
-> nothing moved; without it they dangle, and this record is what remains.
+> **These files are absent from the repository.** They are not symlinks and not placeholders-in-place —
+> the paths simply do not exist here any more. This record is the only thing standing in for them,
+> which is why it carries a SHA-256, a byte count and a pinned reacquisition URL for every file.
 >
-> That is why this record still carries a SHA-256, a byte count and a pinned reacquisition URL
-> for every file: **the archive copy is a convenience for whoever holds it, not part of the
-> contract.** It lives outside the repository at a machine-local path, so nothing here may
-> depend on it, and the symlinks are a local nicety rather than a substitute for these hashes.
+> The archive copy is a **convenience for whoever holds it, not part of the contract**: it lives
+> outside the repository at a machine-local path, so nothing here may depend on it.
 
 | | |
 |---|---|
 | Original path | `ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm` |
 | **SHA-256** | `8e0693da7412f2743b07b285bc46fca879e31222d1db521a8bd6a36e7eeffa41` |
 | **Size** | **5,297,084 bytes** (5.05 MiB) |
-| Archive path | `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm` |
+| Archive path | `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm` |
 
 ## Why this one
 
 It was **54 % of the entire remaining demo tree** and the **only file in it cited by no authored
-document**. Of 140 files in this demo, 139 are referenced by path somewhere in the knowledge base;
+document**. Of 140 files in this demo, 139 are referenced by path somewhere in ``;
 this was the exception. It is a media asset, not board-specific code — nothing about the hardware
 can be learned from it that `audio_bsp.c` does not state directly.
 
 Everything else in this demo stays. The tree had already had **LVGL 8.4.0 and SensorLib removed**
-(see [`../../../../../../vendored-deps/README.md`](../../../../../../vendored-deps/README.md)); what remains is
+(see [`../../../../vendored-deps/README.md`](../../../../vendored-deps/README.md)); what remains is
 Waveshare BSP code, examples and `sdkconfig` snapshots, all heavily cited.
 
 ## Format — derived from the source, not from the file
@@ -69,44 +67,11 @@ unzip -j demo.zip '*/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm'
 sha256sum canon.pcm   # expect 8e0693da7412f2743b07b285bc46fca879e31222d1db521a8bd6a36e7eeffa41
 ```
 
-> ⚠ **Waveshare's own copy is weakly sourced.** The ZIP is vendor-hosted, **unversioned,
-> untagged and carries no LICENSE file anywhere in its 5,052 entries**. Waveshare rotate and
-> silently update these archives, and the wiki sits behind a WAF that required a MediaWiki-API
-> workaround to read. If the hash does not match, you have a different revision of the demo —
-> itself worth recording.
-
-### Independent mirror — verified byte-identical
-
-A third party mirrored the whole demo tree to GitHub, which gives this file something the
-vendor path does not: a **direct, unauthenticated, single-request URL under a different
-custodian**.
-
-```bash
-curl -fsSL "https://raw.githubusercontent.com/mylesdebastion/Waveshare-ESP32-S3-Knob-Touch-LCD-1.8-Demo/HEAD/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm" \
-  -o canon.pcm
-sha256sum canon.pcm   # 8e0693da7412f2743b07b285bc46fca879e31222d1db521a8bd6a36e7eeffa41
-```
-
-**Verified 2026-08-30**, not merely cited: fetched, and the bytes match this record's SHA-256
-and the local archive copy exactly — 5,297,084 bytes, `8e0693da…ffa41` from all three.
-
-- Mirror repository: <https://github.com/mylesdebastion/Waveshare-ESP32-S3-Knob-Touch-LCD-1.8-Demo>
-- Two further third-party trees carrying the same demo, unverified here but worth trying if the
-  above disappears:
-  <https://github.com/nkinnan/Waveshare-ESP32-S3-Knob-Touch-LCD-1.8_and_Guition-K5-Knob-Series-JC3636K518>
-  and <https://github.com/EmbeddedWizardGUI/ESP32-S3-Knob-Touch-LCD-1.8-EN>
-
-> A mirror is a **copy of unknown provenance**, not an authority. It is trustworthy here only
-> because the hash matches; if a future fetch disagrees with the SHA-256 above, believe the hash
-> and treat the mirror as having drifted. Nothing guarantees a third party keeps the repository.
-
-### Vendor rediscovery paths
-
-Both on a different host from `files.waveshare.com` (verified 200, browser UA, 2026-08-30) —
-but the **same custodian**, so this is redundancy of path, not of party:
-
-- Wiki page, *Demo* / *Resources*: <https://www.waveshare.com/wiki/ESP32-S3-Knob-Touch-LCD-1.8>
-- Product page: <https://www.waveshare.com/esp32-s3-knob-touch-lcd-1.8.htm>
+> ⚠ **This is the least reliably reacquirable source in the repository.** The ZIP is
+> vendor-hosted, **unversioned, untagged and carries no LICENSE file anywhere in its 5,052
+> entries**. Waveshare rotate and silently update these archives, and the wiki sits behind a WAF
+> that required a MediaWiki-API workaround to read. If the hash above does not match, you have a
+> different revision of the demo — which is itself worth recording.
 
 ## Restoring a file
 
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm
deleted file mode 120000
index be699a7..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/demo/ESP32-S3-Knob-Touch-LCD-1.8-Demo/ESP-IDF/07_Audio_Test/components/audio_bsp/canon.pcm
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md
index 935ca07..61e6803 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ARCHIVED-ORIGINAL-ZIPS.md
@@ -1,7 +1,7 @@
 # Archived original ZIPs — reacquisition record
 
 > Analysis and archive date: **2026-08-24**. Extended the same day with the Demo ZIP (§3).
-> "Archived" means moved to `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/`,
+> "Archived" means moved to `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/`,
 > preserving this repository's relative path. **Nothing was deleted.**
 
 **Three** of the four original Waveshare downloads in this directory have now been archived.
@@ -31,7 +31,7 @@ archiving defensible. The `README.md` statement should be read as superseded by
 | Field | Value |
 |---|---|
 | Original relative path | `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip` |
-| Archived to | `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip` |
 | What it is | Waveshare's as-shipped **factory firmware images** for both MCUs on this board, distributed as a ZIP from the product wiki's "Demo" section |
 | Archive SHA-256 | `7d29fc1fb356059f7291eccd74bfb5c9fa7538998bc3f5ff811cd87f04c1691c` |
 | Archive size (pre-extract, on-disk ZIP) | **2,032,893 bytes** (1.94 MiB) |
@@ -118,7 +118,7 @@ find . -type f -exec sha256sum {} + | sed 's|  \./|  |' | sort -k2 | sha256sum
 | Field | Value |
 |---|---|
 | Original relative path | `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip` |
-| Archived to | `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip` |
 | What it is | Waveshare's published **schematic for this board, as five PNG page renders**. Not EDA source; not PDF. This is the only schematic Waveshare publishes for the product |
 | Archive SHA-256 | `baa5ac1bf75fbbd86a8135b123ff498bd7db4a5c68184481db6b82cadbaca0e5` |
 | Archive size (pre-extract, on-disk ZIP) | **672,290 bytes** (656.5 KiB) |
@@ -210,7 +210,7 @@ Both Internet Archive captures share the CDX content digest `PY44LGYDHPOB43FTZF5
 | Field | Value |
 |---|---|
 | Original relative path | `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-Demo.zip` |
-| Archived to | `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-Demo.zip` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-Demo.zip` |
 | What it is | Waveshare's complete **demo/example distribution** for this board: the Arduino sketch tree, eight ESP-IDF projects, the two factory firmware binaries, and two bundled third-party libraries |
 | Archive SHA-256 | `11e382444fe93470fbe463829c1e0ebad5bdb5115fd2d72f6159cd7700015030` |
 | Archive size (on-disk ZIP) | **68,704,748 bytes** (65.5 MiB) |
@@ -266,7 +266,7 @@ statements are now superseded:
    identical, zero differing files.** The name-independent content digest of both is
    `b786db26f67146c92028fc5a11c653eaaf3ff813a7150e96f41d9c9060ca7c38`. The only name-level
    differences are the three documented ASCII datasheet renames.
-3. **The archived library trees also still exist** under `archive/`, and
+3. **The archived library trees also still exist** under `../hardware-doc-archive/`, and
    `diff -rq` between them and the freshly restored trees is clean.
 4. **Two independent URLs were downloaded in full and hashed**, both exact matches (below).
 
@@ -366,7 +366,7 @@ The Internet Archive CDX content digest for the capture is
 | | Originally | After BIN + schematic | After Demo ZIP |
 |---|---:|---:|---:|
 | `artifacts/originals/` in repository | 71,476,469 B (68.2 MiB) | 68,771,286 B (65.6 MiB) | **66,538 B (65 KiB)** |
-| Moved to `archive/` | — | 2,705,183 B (2.58 MiB) | **71,409,931 B (68.1 MiB)** |
+| Moved to `../hardware-doc-archive/` | — | 2,705,183 B (2.58 MiB) | **71,409,931 B (68.1 MiB)** |
 
 This directory now holds a single product photograph and these records. Everything else has a
 verified reacquisition path.
@@ -378,20 +378,6 @@ reproducible**: `../../tools/restore-demo-deps.sh` closes the gap from upstream,
 verified against this exact ZIP before it was moved. Combined with two independently
 hash-verified download URLs, the archive is recoverable by four separate routes.
 
-## Source repositories
-
-Waveshare publish no repository for this demo, so the vendor ZIP is the only first-party route.
-Third parties have mirrored the tree to GitHub, which is a different custodian entirely:
-
-- <https://github.com/mylesdebastion/Waveshare-ESP32-S3-Knob-Touch-LCD-1.8-Demo> — full demo
-  tree; one file from it was fetched and **verified byte-identical** to our archived copy on
-  2026-08-30, so the mirror is a real recovery path rather than a hopeful link
-- <https://github.com/nkinnan/Waveshare-ESP32-S3-Knob-Touch-LCD-1.8_and_Guition-K5-Knob-Series-JC3636K518>
-- <https://github.com/EmbeddedWizardGUI/ESP32-S3-Knob-Touch-LCD-1.8-EN>
-
-> A mirror is a copy of unknown provenance. Trust it only where the SHA-256 in this record
-> matches, and expect no guarantee that a third party keeps their repository.
-
 ## Related records
 
 - [`README.md`](./README.md) — acquisition record for all four original downloads. Its
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip
deleted file mode 120000
index 48ed3f6..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-Demo.zip b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-Demo.zip
deleted file mode 120000
index 067daa9..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-Demo.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-Demo.zip
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip
deleted file mode 120000
index f3a8271..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/README.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/README.md
index 4505312..1d36d32 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/README.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/originals/README.md
@@ -16,7 +16,7 @@ In every case the served `Content-Length` matched the local byte size exactly.
 > [`ARCHIVED-ORIGINAL-ZIPS.md` §3](./ARCHIVED-ORIGINAL-ZIPS.md#3-esp32-s3-knob-touch-lcd-18-demozip).
 >
 > `ESP32-S3-Knob-Touch-LCD-1.8-BIN.zip` and `ESP32-S3-Knob-Touch-LCD-1.8-schematic.zip` were moved
-> to `archive/` after their contents were verified byte-identical to trees that
+> to `../hardware-doc-archive/` after their contents were verified byte-identical to trees that
 > remain here, and after Internet Archive mirrors were found and hash-verified. See
 > [`ARCHIVED-ORIGINAL-ZIPS.md`](./ARCHIVED-ORIGINAL-ZIPS.md). **The "single-source risk" note at
 > the end of this file is superseded for all three ZIPs** — each now has multiple working,
@@ -104,6 +104,6 @@ and the product page <https://www.waveshare.com/esp32-s3-knob-touch-lcd-1.8.htm>
 
 See [`../vendored-deps/README.md`](../vendored-deps/README.md). Summary: the bundled
 **LVGL 8.4.0** (158 MiB) and **SensorLib 0.3.1** (43 MiB) trees were moved to
-`archive/`, after being verified as unmodified upstream releases apart from one
+`../hardware-doc-archive/`, after being verified as unmodified upstream releases apart from one
 one-line patch each, both of which are preserved as patch files. All 15 SensorLib datasheets were
 promoted into reusable component records first.
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/CH34XSER_MAC.7z b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/CH34XSER_MAC.7z
deleted file mode 120000
index b48c04e..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/CH34XSER_MAC.7z
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/CH34XSER_MAC.7z
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/README.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/README.md
index c230ff1..845161f 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/README.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/README.md
@@ -1,7 +1,7 @@
 # Tools — archived artifacts and reacquisition record
 
 > Archive/removal date: **2026-08-23**.
-> "Archived" means moved to `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/`,
+> "Archived" means moved to `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/`,
 > preserving this repository's relative path. Nothing was deleted.
 
 All URLs below were enumerated from the local wikitext snapshot
@@ -210,7 +210,7 @@ Secondary sources (WCH is the true origin; Waveshare is a mirror):
 | | Before | After |
 |---|---:|---:|
 | `artifacts/tools/` in repository | 108 MiB | **1.1 MiB** |
-| Moved to `archive/` | — | 106.6 MiB |
+| Moved to `../hardware-doc-archive/` | — | 106.6 MiB |
 | Newly extracted and kept (CH34X PDF) | — | 0.68 MiB |
 
 Net repository reduction: **≈107 MiB**, with every archived byte hash-recorded and
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/flash_download_tool.zip b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/flash_download_tool.zip
deleted file mode 120000
index f64e163..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/flash_download_tool.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/flash_download_tool.zip
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/mjpeg_Conversion_tool_V2.1.zip b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/mjpeg_Conversion_tool_V2.1.zip
deleted file mode 120000
index 4e107a6..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/mjpeg_Conversion_tool_V2.1.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/mjpeg_Conversion_tool_V2.1.zip
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe
deleted file mode 120000
index c57d8c2..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe.REMOVED.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe.REMOVED.md
index ec3c6c2..df3b4f9 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe.REMOVED.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe.REMOVED.md
@@ -5,7 +5,7 @@ This file is a placeholder standing in for a binary that was moved out of the re
 | Field | Value |
 |---|---|
 | Original relative path | `devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe` |
-| Archived to | `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/tools/sscom5.13.1/sscom5.13.1.exe` |
 | Archive date | **2026-08-24** |
 | What it is | The **SSCOM V5.13.1 Windows serial terminal executable** — a 32-bit Windows GUI program. See [`README.md`](./README.md) for what SSCOM is and why it is here at all |
 | SHA-256 | `51ea245a3d07436a86a4449b2791c1f37fa60e181dd128e8d7dd79cc1ad836ce` |
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/vendored-deps/README.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/vendored-deps/README.md
index d4bcdff..27bd842 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/vendored-deps/README.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/artifacts/vendored-deps/README.md
@@ -269,4 +269,4 @@ references. Do not infer from their presence that any of these parts is on this
 
 Redistribution status for all fifteen is `unknown` — they are third-party manufacturer datasheets
 redistributed by SensorLib under its MIT license, but MIT covers SensorLib's own code, **not**
-these bundled third-party documents. They are kept pending review.
+these bundled third-party documents. They are kept unstaged pending review.
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/esphome-and-clone-confirmation.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/esphome-and-clone-confirmation.md
index eb1304f..62d18c0 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/esphome-and-clone-confirmation.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/esphome-and-clone-confirmation.md
@@ -5,7 +5,7 @@
 > Source: [`esphome/devices.esphome.io`](https://github.com/esphome/devices.esphome.io),
 > `src/docs/devices/ESP32S3-1.8-inch-JC3636K518C/index.md`, published **2025-08-22**.
 >
-> Local copy: `scratch/esp32-s3-knob-touch-lcd-1.8/community-probe/`
+> Local copy: `../hardware-doc-archive/scratch/esp32-s3-knob-touch-lcd-1.8/community-probe/`
 
 ## The finding
 
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/SensorLib b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/SensorLib
deleted file mode 120000
index cbd371f..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/SensorLib
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/SensorLib
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/lvgl b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/lvgl
deleted file mode 120000
index 3f83bc4..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/lvgl
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/components/lvgl
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/main/ui/images b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/main/ui/images
deleted file mode 120000
index fc41516..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/main/ui/images
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/BlueKnob-ESP32S3/main/ui/images
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/extras/backgrounds.pdn b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/extras/backgrounds.pdn
deleted file mode 120000
index dd67163..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/extras/backgrounds.pdn
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob-c71c98ff5b/extras/backgrounds.pdn
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob.tar.gz b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob.tar.gz
deleted file mode 120000
index 5876124..0000000
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob.tar.gz
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/BlueKnob.tar.gz
\ No newline at end of file
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/blueknob-vendored-deps/README.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/blueknob-vendored-deps/README.md
index 33b4a9b..2f6fae6 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/blueknob-vendored-deps/README.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/blueknob-vendored-deps/README.md
@@ -2,7 +2,7 @@
 
 > Archive/removal date: **2026-08-23**.
 > "Archived" means moved to
-> `archive/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/`,
+> `../hardware-doc-archive/doc/hardware/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/examples/selected/`,
 > preserving this repository's relative path. Nothing was deleted.
 
 ## What BlueKnob is
@@ -182,7 +182,7 @@ for p in ../../../blueknob-vendored-deps/patches/sensorlib-0.3.1-blueknob-*.patc
 done
 
 # 4. Regenerate ui_img_*.c from BlueKnob-UI/*.spj via SquareLine Studio,
-#    or copy them back from archive/
+#    or copy them back from ../hardware-doc-archive/
 ```
 
 Upstream projects: <https://github.com/lvgl/lvgl> · <https://github.com/lewisxhe/SensorLib>
diff --git a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/sources.md b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/sources.md
index e9088f0..51c2c8f 100644
--- a/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/sources.md
+++ b/devices/waveshare/esp32-s3-knob-touch-lcd-1.8/sources.md
@@ -44,7 +44,7 @@ All files validated by magic bytes.
 
 | Title | URL | Publisher | Retrieved | Version | Local artifact | Notes |
 |---|---|---|---:|---|---|---|
-| CST816D touch controller datasheet (Waveshare mirror) | https://files.waveshare.com/wiki/common/CST816D_datasheet_En_V1.3.pdf | Hynitron via Waveshare | 2026-08-21 | English V1.3 | [`components/hynitron/cst816d/artifacts/cst816d-datasheet-v1.3.pdf`](../../../components/hynitron/cst816d/artifacts/cst816d-datasheet-v1.3.pdf) | **Relocated 2026-08-24.** Byte-identical duplicate of the components/ copy; device-side copy archived to `archive/`. 1098205 B, sha256 `a0b14a06ef5d8205` |
+| CST816D touch controller datasheet (Waveshare mirror) | https://files.waveshare.com/wiki/common/CST816D_datasheet_En_V1.3.pdf | Hynitron via Waveshare | 2026-08-21 | English V1.3 | [`components/hynitron/cst816d/artifacts/cst816d-datasheet-v1.3.pdf`](../../../components/hynitron/cst816d/artifacts/cst816d-datasheet-v1.3.pdf) | **Relocated 2026-08-24.** Byte-identical duplicate of the components/ copy; device-side copy archived to `../hardware-doc-archive/`. 1098205 B, sha256 `a0b14a06ef5d8205` |
 | DRV2605 haptic driver datasheet (Waveshare mirror) | https://files.waveshare.com/wiki/common/Drv2605.pdf | TI via Waveshare | 2026-08-21 | undated mirror | [`components/texas-instruments/drv2605/artifacts/drv2605-datasheet-slos825-2025-06-02.pdf`](../../../components/texas-instruments/drv2605/artifacts/drv2605-datasheet-slos825-2025-06-02.pdf) | **Relocated 2026-08-24.** Verified `ZHCSCW9E` (Chinese, rev. Apr 2018) — **DRV2605 non-L, wrong part**; board fits DRV2605L. Byte-identical duplicate; device-side copy archived. 2478601 B, sha256 `bd7549137c51d8b6` |
 | ESP32-S3 datasheet (Waveshare mirror) | https://files.waveshare.com/wiki/common/Esp32-s3_datasheet_en.pdf | Espressif via Waveshare | 2026-08-21 | undated mirror | [`components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v1.6-waveshare-mirror.pdf`](../../../components/espressif/esp32-s3r8/artifacts/esp32-s3-datasheet-v1.6-waveshare-mirror.pdf) | **Relocated 2026-08-24.** Verified **v1.6**; components/ holds current v2.2. 1186331 B, sha256 `b79310e52e905999` |
 | ESP32-S3 TRM (Waveshare mirror) | https://files.waveshare.com/wiki/common/Esp32-s3_technical_reference_manual_en.pdf | Espressif via Waveshare | 2026-08-21 | undated mirror | [`components/espressif/esp32-s3r8/artifacts/esp32-s3-technical-reference-manual-v1.2-waveshare-mirror.pdf`](../../../components/espressif/esp32-s3r8/artifacts/esp32-s3-technical-reference-manual-v1.2-waveshare-mirror.pdf) | **Relocated 2026-08-24.** Verified **v1.2**; components/ holds current v1.8. 14540185 B, sha256 `47bb075de167d816` |
diff --git a/devices/waveshare/esp32-s3-photopainter/README.md b/devices/waveshare/esp32-s3-photopainter/README.md
deleted file mode 100644
index 1a40c32..0000000
--- a/devices/waveshare/esp32-s3-photopainter/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Waveshare ESP32-S3-PhotoPainter — *stub*
-
-> **SKUs 32408 / 32753.** Research snapshot **2026-09-01**. **Stub record**:
-> surveyed, not researched in depth. All claims are vendor statements
-> (`reported-working`) from the storefront. No artifacts retrieved, no hardware in
-> hand.
-
-Created during the [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) pass.
-Recorded because the PhotoPainter was named as a candidate to research, and the
-survey's finding about it is worth keeping: **it is a finished appliance, not a
-development board**, and so it is not a PaperMono alternative.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Name | ESP32-S3-PhotoPainter |
-| SKUs | **32408**, **32753** |
-| Price | **USD 82.99 – 83.99** (observed 2026-09-01, waveshare.com, US region) |
-| Store | `https://www.waveshare.com/esp32-s3-photopainter.htm` |
-| Docs | `https://docs.waveshare.com/ESP32-S3-PhotoPainter` — **404**; not on the new platform at the snapshot date |
-
-## What it is
-
-A **7.3-inch full-colour e-paper photo frame in a solid wood surround**, marketed on
-"ultra-long standby", 800 × 480 resolution, with an optional battery.
-
-| Specification | Value |
-|---|---|
-| SoC | ESP32-S3 |
-| Panel | **7.3-inch E Ink Spectra 6 (E6)**, full colour |
-| Resolution | 800 × 480 |
-| Enclosure | Solid wood photo frame |
-| Battery | Optional |
-
-**800 × 480 at 7.3 inches is the same pixel count as the 3.97-inch board** — the same
-frame spread over nearly twice the diagonal. It is a viewing-distance product.
-
-## The PhotoPainter family is not one product
-
-The survey turned up **four** distinct listings under this name, only one of which is
-ESP32-based. Recorded because the name alone is ambiguous and conflating them would
-be an error:
-
-| Slug | SKUs | Price (2026-09-01) | Processor |
-|---|---|---|---|
-| `esp32-s3-photopainter` | 32408, 32753 | USD 82.99–83.99 | **ESP32-S3** |
-| `photopainter` | 24708, 24709 | USD 88.99–90.99 | **Raspberry Pi RP2040** — *not ESP32* |
-| `photopainter-b` | 30068, 30315 | USD 92.99–93.99 | **not established** |
-| `rpi-zero-photopainter-acce` | — | — | Raspberry Pi Zero accessory |
-
-The `photopainter` original uses **7.3-inch ACeP 7-colour**; `photopainter-b` and the
-ESP32-S3 version use **Spectra 6 (E6)**. So the family spans two display generations
-*and* at least two processor architectures under one brand.
-
-**`photopainter-b`'s processor was not determined** and is recorded as `unknown`
-rather than assumed from the naming.
-
-## Why it was not chosen as the PaperMono comparison
-
-It fails the test on the two things that matter:
-
-1. **It is not a development board.** It is a framed consumer object. There is no
-   expansion, and the product is the picture on the wall.
-2. **Colour e-paper is a different technology with different constraints.** Spectra 6
-   refresh times are measured in tens of seconds, not the 0.3–3.5 s of the monochrome
-   3.97-inch panel. Comparing it to a PaperMono on refresh, power or interactivity
-   would be comparing unlike things — the sort of false equivalence the
-   [PaperMono comparison page](../../m5stack/papermono/comparisons-and-recommendations.md)
-   is careful to avoid.
-
-The board that *does* serve the comparison is the
-[ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md).
-
-## Why this is a stub
-
-Nothing beyond the storefront was retrieved. No schematic, no demo code, no images,
-no panel identification, no `photopainter-b` processor, no refresh figures, no
-standby-current evidence for the "ultra-long standby" claim.
-
-## Sources
-
-| ID | Title | Class | URL | Retrieved | Version |
-|---|---|---|---|---|---|
-| `P01` | ESP32-S3-PhotoPainter — store listing | primary | `https://www.waveshare.com/esp32-s3-photopainter.htm` | 2026-09-01 | `unknown` |
-| `P02` | PhotoPainter — store listing | primary | `https://www.waveshare.com/photopainter.htm` | 2026-09-01 | `unknown` |
-| `P03` | PhotoPainter (B) — store listing | primary | `https://www.waveshare.com/photopainter-b.htm` | 2026-09-01 | `unknown` |
-| `P04` | `docs.waveshare.com/ESP32-S3-PhotoPainter` → **404** | primary | — | 2026-09-01 | negative result |
-
-## See also
-
-- [ESP32-S3-ePaper-3.97](../esp32-s3-epaper-3.97/README.md) — researched in depth
-- [The sibling survey](../esp32-s3-epaper-3.97/README.md#sibling-products)
diff --git a/devices/xteink/README.md b/devices/xteink/README.md
deleted file mode 100644
index a3d7493..0000000
--- a/devices/xteink/README.md
+++ /dev/null
@@ -1,387 +0,0 @@
-# Xteink (阅星瞳 / 星瞳 "Star Pupil")
-
-> Shenzhen-based compact e-reader brand. Five products established as of the
-> research snapshot **2026-09-04**. Four are ESP32-based and are the hardware
-> targets of the CrossPoint Reader / FreeInk firmware ecosystem; the fifth is an
-> Android device and is a different platform entirely.
-
-## The confirmed family
-
-| Device | SoC | Panel | Size / res | Touch | Frontlight | Record | Depth |
-|---|---|---|---|---|---|---|---|
-| [**X4 Pro**](x4-pro/README.md) | ESP32-S3, 16 MB flash, 8 MB PSRAM | SSD1677 · UC8179 · UC8279 (batch-dependent) | 4.26″ 800×480 | **GT911** | **dual warm/cool** | `x4-pro/` | deep |
-| [**X4**](x4/README.md) | ESP32-C3, 16 MB flash | SSD1677 · UC8179 · UC8279 | 4.26″ 800×480 | none | none | `x4/` | deep |
-| [**X3**](x3/README.md) | ESP32-C3, 16 MB flash | UC8253 · UC8279d | 3.7″ 792×528 | none | none | `x3/` | deep |
-| [**X4 Classic (X4C)**](x4-classic/README.md) | ESP32-S3, 16 MB flash, 8 MB PSRAM | SSD1677 · UC8179 · UC8279 | 4.26″ 800×480 | none | none | `x4-classic/` | medium |
-| [**S4**](s4/README.md) | **Android 11**, 2 GB RAM / 32 GB | not established | not established | yes | yes | `s4/` | **stub** |
-| [**Nano** / Tong Card 瞳卡](nano/README.md) | **none — passive, NFC-powered** | four-colour e-paper, part unknown | not established | n/a | n/a | `nano/` | **stub** |
-
-The **Nano** is not a reader. It is a battery-less NFC-powered e-paper display
-card that snaps to a phone's back, written from a phone app. It is included
-because it is a genuine Xteink product line, it is sold internationally on
-AliExpress, and it is **routinely confused with the X3's embedded NFC tag** —
-which is a completely different thing.
-
-**The X4 Pro and the X4 are different computers.** They share a screen size and a
-brand and nothing else: different SoC architecture (Xtensa LX7 vs RISC-V),
-different flash layout, different input hardware, different charging connector.
-Firmware built for one will not run on the other, and
-[CrossPlay's `OtaUpdater` had to be repointed](../../software/applications/crossplay/README.md)
-specifically because upstream's release URL would flash a C3 image onto an S3.
-
-## Models that do **not** exist
-
-Recorded so they are not re-investigated:
-
-| Name | Verdict | Evidence |
-|---|---|---|
-| **X5** | **Does not exist.** Community speculation about a successor only | 8 Reddit mentions, all wishlist/rumour. One post titled "Got my white (?) X5" was edited by its own author: *"EDIT: It's X4 and not X5."* ([r/xteinkereader `1o8vw7y`](https://old.reddit.com/r/xteinkereader/comments/1o8vw7y/got_my_white_x5/), 2025-10-17) |
-| **X4 Mini** | **Not a SKU.** A colloquial nickname for the X4 | Six uses across r/EDC, r/eink, r/writerDeck. The r/eink video titled "XTEINK X4 mini e-Reader" says in its own body *"the XTEINK X4"* ([`1sba4am`](https://old.reddit.com/r/eink/comments/1sba4am/), 2026-04-03) |
-| **X1 / X2** | **No evidence.** Zero substantive mentions | 3 apparent hits were all false positives (`x2` = "quantity two") |
-| **X4 Plus / Air / Pro Max** | **No evidence** | Not present in the vendor catalogue, the vendor's collection handles, the FreeInk board enum, or 1,798 Reddit posts |
-
-The vendor's own Shopify collection handles are the tightest available list, and
-they are exactly: `x3-series`, `x4-series`, `x4-classic`, `x4-pro-series`
-(plus marketing duplicates `x3-edm`, `x4-edm`, `x4-proedm`, `machine`,
-`homepage-display`, `accessories`, `pocket-e-reader`).
-
-## Naming and transliteration
-
-| Form | Where used |
-|---|---|
-| **Xteink** | Official Latin brand, `xteink.com` |
-| **XTeink**, **XT-eink**, **XTEINK** | All appear in community and repo names; the vendor's own store title is uppercase `XTEINK` |
-| **星瞳** ("Star Pupil") | Chinese product name — [r/ereader `1n5kmpc`](https://old.reddit.com/r/ereader/comments/1n5kmpc/xteink_star_pupil_x4_星瞳x4_first_impressions/) is titled "Xteink Star Pupil X4 (星瞳X4)" |
-| **阅星瞳** | Chinese brand form used by [`sunwoods/Xteink-X3`](https://github.com/sunwoods/Xteink-X3) |
-| **阅星曈** | A **different second character** (曈 "dawn light" vs 瞳 "pupil"), used by [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher) and `AsukaLay/xteink_pdf`. **Both spellings are in live community use.** Search both |
-| **星曈** | Short form with 曈, used by `SamLinBIT/xteink-toolkit` |
-| `XTEink::` | The C++ namespace in the vendor's own stock firmware, recovered by Ghidra |
-
-## Company
-
-A **small team based in Shenzhen**. The founder posts publicly as **"Crusoe"** and
-introduced the company on Reddit on 2025-10-09
-([r/ereader `1o2203h`](https://old.reddit.com/r/ereader/comments/1o2203h/hi_everyone_im_crusoe_from_xteink_a_small_ereader/),
-1,477 points) — *"I'm Crusoe, founder of Xteink, a small team based in Shenzhen."*
-The company is China-first: the S4 launched domestically months before any
-international availability, and firmware/pricing announcements appear on
-Xiaohongshu (RedNote) before they reach the English store.
-
-## Why this family matters
-
-These are the **cheapest programmable e-paper devices with a usable enclosure,
-battery, buttons and SD slot** currently in circulation — $69–$99 new, and
-observed as low as **$16** used ([r/XTEINK `1vrnxnq`](https://old.reddit.com/r/XTEINK/comments/1vrnxnq/), 2026-08-18).
-A bare 4.26″ panel alone typically costs more than a whole X4.
-
-That, plus a stock firmware that turned out to be reverse-engineerable, produced
-an unusually large third-party firmware ecosystem — **~200 public repositories**
-census'd on 2026-09-04. See each device's `projects-and-community.md`.
-
-## Documentation map
-
-| Per-device file | What it holds |
-|---|---|
-| `README.md` | Identity, specs, architecture, market fit, task index |
-| `pinouts-and-buses.md` | Full GPIO/bus tables reconstructed from firmware source |
-| `development.md` | Toolchain, build, flash, unlock, bricking risks |
-| `factory-firmware.md` | Stock images, dumping, restoring, partition layout |
-| `features/` | Task-oriented guides per capability |
-| `sources.md` · `research-log.md` · `commands.md` | Evidence trail |
-| `coverage.md` · `compatibility-and-status.md` · `gaps-and-conflicts.md` | What is and is not established |
-| `projects-and-community.md` · `community.md` | Firmware ecosystem and owner reports |
-| `market-and-pricing.md` · `comparisons-and-recommendations.md` | Dated commercial evidence |
-
-## Shared reading
-
-- [FreeInk SDK board profiles](https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h)
-  — the single most authoritative hardware document for four of these five devices.
-- [CrossPlay](../../software/applications/crossplay/README.md) — a fork analysis
-  that explains the X4 Pro's position as the ecosystem's "design floor".
-- [M5Stack PaperMono](../m5stack/papermono/README.md) — the development-board
-  alternative the community repeatedly compares these to.
-
-## Evidence standard used here
-
-Every board-level pin, address and chip in these records traces to one of:
-**[SDK]** the FreeInk SDK board profile or its `docs/xteink-*-support.md`;
-**[DUMP]** a parsed OEM flash image; **[TD]** a teardown photograph;
-**[VENDOR]** the vendor's own store API or a founder statement; or
-**[COMM]** a community report, always labelled as such.
-
-Vendor **marketing prose is not used as evidence anywhere in this tree.** The
-`xteink.com` product copy is AI/SEO-generated and is demonstrably wrong: the X3
-listing advertises "adjustable warm light settings" and "Cloud sync", and the X3
-has no frontlight at all. See [`x3/gaps-and-conflicts.md`](x3/gaps-and-conflicts.md).
-
----
-
-## Cross-model comparison
-
-Dated **2026-09-04**. Prices are vendor-direct, item-only, worldwide from
-Shenzhen. **Nothing in this table was measured by this research** — see each
-device's `performance.md`.
-
-### The four ESP32 devices
-
-| | [**X3**](x3/README.md) | [**X4**](x4/README.md) | [**X4 Pro**](x4-pro/README.md) | [**X4 Classic**](x4-classic/README.md) |
-|---|---|---|---|---|
-| **Price** | **$69, in stock** | **delisted** (~$69) | **$99, in stock** | **never priced** |
-| SoC | ESP32-C3 (RISC-V) | ESP32-C3 | **ESP32-S3** (Xtensa) | **ESP32-S3** |
-| PSRAM | none | none | **8 MB** | **8 MB** |
-| Flash | 16 MB Puya | 16 MB Puya | 16 MB | 16 MB |
-| Panel | **3.7″ 792×528** | 4.26″ 800×480 | 4.26″ 800×480 | 4.26″ 800×480 |
-| **PPI** | **~257** | ~219 | ~219 | ~219 |
-| Controller | UC8253 · **UC8279d** | SSD1677 · UC8179 · UC8279 | SSD1677 · UC8179 · UC8279 | SSD1677 · UC8179 · UC8279 |
-| Controller selection | live bus probe | live bus probe | live bus probe | **NVS only — no MISO** |
-| Mass | **55 g** | ~74–80 g | unknown | unknown |
-| Battery | **650 mAh** | unknown | unknown | unknown |
-| Touch | ✗ | ✗ | **GT911** | ✗ |
-| Frontlight | ✗ | ✗ | **dual warm/cool** | ✗ |
-| Buttons | 6 (**ADC ladder**) + pwr | 6 (**ADC ladder**) + pwr | **2** + pwr | **6 discrete, ISR** + pwr |
-| RTC | DS-series 0x68 **(unresolved)** | **none** | BM8563 0x51 | BM8563 0x51 |
-| Fuel gauge | **BQ27220** (no profile needed) | **none — bare ADC** | CW2017 (needs BATINFO) | CW2017 |
-| IMU | **QMI8658** | ✗ | ✗ | **QMI8658** |
-| **NFC** | **✅ writable tag** | ✗ | ✗ | ✗ |
-| Storage | SPI, **shared with display** | SPI, **shared**, no power enable | **native SDMMC** | **native SDMMC** |
-| SD sleep power-down | ✅ GPIO13 (active-HIGH) | **✗** | ✅ GPIO5 (active-LOW) | ✅ GPIO6 (active-LOW) |
-| Charging | pogo | **USB-C** | pogo | **unknown** |
-| USB-MSC | — | — | in stock, **unported** | **SDK-supported** |
-| Public firmware image | **4 stock images** (Git LFS) | **1 community dump, archived here** | **none** | **none** |
-| Teardown | **2, both archived here** | none | none | none |
-
-### Five things this table gets wrong if you skim it
-
-1. **"X4 Pro" is not an enhanced X4.** Different SoC architecture, flash layout,
-   input hardware and charging connector. Firmware for one will not run on the
-   other, and upstream release URLs have flashed C3 images onto S3 devices.
-2. **The Pro is not a superset.** It has **no IMU**; the cheaper X3 and its own
-   board sibling both do.
-3. **The cheapest model has the sharpest screen.** ~257 PPI vs ~219.
-4. **The X3 has the best battery instrumentation.** A BQ27220 needing no profile
-   upload, against the Pro's CW2017 (reports 0 % until an 80-byte BATINFO table is
-   written) and the X4's bare ADC.
-5. **GPIO13 means three different things** across the family — SD rail on the X3
-   (active-HIGH), battery power-off latch on the X4, unused on the S3 boards. Never
-   port power code between them.
-
-### Against platforms already in this repository
-
-| Device | Class | Schematic | USB-C | Headers | Unlock | Verdict |
-|---|---|---|---|---|---|---|
-| Xteink X3 / X4 / X4 Pro | **sealed reader** | ✗ (X3: a hand-drawn sketch) | X4 only | ✗ | often needed | Pocketable, cased, battery-managed, cheap |
-| [M5Stack PaperMono](../m5stack/papermono/README.md) | dev board | **✅ published, 6 sheets** | ✅ | ✅ | ✗ | **Better for development.** Bigger, thicker, no enclosure or case ecosystem |
-| [Waveshare ESP32-S3-ePaper-3.97](../waveshare/esp32-s3-epaper-3.97/README.md) | dev board | partial | ✅ | ✅ | ✗ | ESP32-S3 + PSRAM + SSD1677 + a QMI8658 — the closest dev-board analogue to an X3's silicon |
-| [ZeroWriter](../zerowriter/) | DIY appliance | ✅ open | ✅ | ✅ | ✗ | Different purpose: keyboard-first writing appliance |
-
-**These are partial substitutes, not equivalents.** They share "ESP32 driving
-e-paper" and nothing else — no enclosure, no battery management, no case
-ecosystem, no pocketability. The community routinely compares them on price, and
-that comparison is close to meaningless: a dev board is the right answer if you
-want to **build** something, a sealed Xteink if you want to **read** on something
-you can also reflash.
-
-A useful calibration: a community member built an **open-source ESP32-S3 e-paper
-dev kit** — KiCad files, 650 mAh cell, USB-C OTG, 4-bit SDMMC, hand-solderable
-parts — at a *"full unit BOM around $60 including display and battery"*
-([r/XTEINK `1s3osv3`](https://old.reddit.com/r/XTEINK/comments/1s3osv3/),
-2026-03-25, 104 pts). **A DIY equivalent costs roughly what a finished X4 cost.**
-
-### Buying guidance, dated 2026-09-04
-
-| You want… | Buy | Confidence |
-|---|---|---|
-| Sharpest text, lightest, most sensors, cheapest new | **X3, $69** | high |
-| Touch **and** a frontlight | **X4 Pro, $99** | high |
-| **USB-C charging** | **X4, used only** — it is delisted and its accessories are exhausted | high |
-| Six real buttons on an S3, plus an IMU | **X4 Classic** — **if you can find one**; never listed internationally | n/a |
-| Android, apps, a browser, half the price | **S4** — but **no community firmware, ever** | medium |
-| A schematic, headers and no unlock dance | **PaperMono** or a **Waveshare** board | high |
-| To wait | An **"X4 version 2"** was vendor-confirmed for September 2026, spec unknown | **low — hearsay** |
-
-**One warning that applies to every purchase in this family:** USB-lock state is
-**not predictable from the sales channel**. An owner who bought three units
-reported an Amazon X3 unlocked, an official-store X3 **locked**, and an AliExpress
-X4 locked ([r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/),
-2026-08-10, firsthand). Assume you will need the unlock procedure.
-
----
-
-## Cross-references added 2026-09-07
-
-Appended by a cross-cutting synthesis pass. **No line above was changed**, and
-nothing below is a new retrieval or a new measurement — these are syntheses built
-from the records in this tree.
-
-| Document | What it adds that is not here |
-|---|---|
-| [**`firmware-ecosystem.md`**](firmware-ecosystem.md) | **The hardware-side map of CrossPoint / FreeInk / CrossPlay** — which firmware supports which model, at which commit and board target, the full `VER (0x70)` / `FLG (0x71)` panel-controller detection trick and its X4 Classic exception, and a checklist of what a *new* board must provide to be supported |
-| [Handheld and e-ink device landscape, 2026-09](../../guides/markets/handheld-and-eink-device-landscape-2026-09.md) | These four ESP32 devices placed against the PaperMono, the Waveshare e-paper boards and ZeroWriter, with the comparisons that are **not** supportable stated explicitly |
-| [SoC choice for battery e-ink devices](../../guides/hardware/soc-choice-for-battery-eink-devices.md) | Why the C3 → S3 split inside this family matters more than the price difference suggests, with the framebuffer and heap arithmetic — and the finding that **no ESP32-C3 or ESP32-S3 deep-sleep figure exists anywhere in this repository** |
-| [Adding LoRa, NFC and an RGB sidelight to e-ink firmware](../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md) | ⚠ **Why the X3's passive NFC tag is not an NFC reader**, and what adding real radios to this class of firmware would actually cost |
-
----
-
-# ROUND 2 — appended 2026-09-11
-
-> **No line above this rule was changed.** Several statements above are
-> **superseded**, and they are superseded here rather than edited in place, so
-> the 2026-09-04 snapshot stays readable as what was knowable then.
->
-> Retrieval date **2026-09-11**. (The task brief said 2026-09-07; the host clock,
-> the vendor's Shopify `updated_at` and a dated store review all put "now" at or
-> after 2026-09-08. The later date is used. See
-> [`x4-classic/research-log.md`](x4-classic/research-log.md) §0.)
-
-## The headline: the family is **six** products, not five, and the X4 is gone
-
-| # | Device | Status 2026-09-11 | Price | Record |
-|---|---|---|---|---|
-| 1 | [**X4 Pro**](x4-pro/README.md) | listed, in stock | **$99** | deep — **now three independent custodians** |
-| 2 | [**X4 Classic (X4 V2)**](x4-classic/README.md) | **LISTED 2026-09-06, in stock** | **$79** | deep |
-| 3 | [**X3**](x3/README.md) | listed, in stock | **$69** | deep |
-| 4 | [**X4**](x4/README.md) | **withdrawn — product record and all four dedicated accessories removed** | — | deep |
-| 5 | [**X4 Light**](x4-light/README.md) | **FCC-certified 2026-08-13. Never announced, never listed** | — | **NEW — certification-only** |
-| 6 | [**S4**](s4/README.md) | Android, separate platform | — | stub |
-| + | [**Nano / Tong Card**](nano/README.md) | passive NFC card, not a reader | — | stub |
-
-## Three corrections to the tables above
-
-### 1. "X4 v2" was not a future product. It is the X4 Classic.
-
-The buying-guidance table above ends with *"An **'X4 version 2'** was
-vendor-confirmed for September 2026, spec unknown — **low — hearsay**."*
-
-**That is now resolved, and the confidence label was right to be low, because the
-thing being described was mis-modelled rather than mis-dated.** "X4 V2" is the
-vendor's own parenthetical for the X4 Classic:
-
-- vendor Reddit post, 2026-09-03: *"**X4 Classic (X4 V2) is coming soon**"*
-- store product title: `XTEINK X4 Classic (X4 V2) Pocket eReader`
-- four accessory titles, all `XTEINK X4 Classic (X4 V2) …`
-- the product-page FAQ, in prose: *"The **X4 V2** features a built-in magnetic
-  ring on the back…"*
-
-**There is no separate model between the X4 and the X4 Pro.** The FreeInk
-`enum class Board` at HEAD (`9f4d3f9`, 2026-09-10) still contains exactly five
-Xteink entries, and GitHub code search for `"X4R1_CLA"` returns **zero**.
-
-### 2. The X4 Classic collection is populated. The record's headline is superseded.
-
-`x4-classic/README.md` opened with *"contains **no device** — only generic
-accessories."* Correct on 2026-09-04; **wrong from 2026-09-06 19:57:20 −0700**,
-the `published_at` on the vendor's own API.
-
-### 3. "Models that do not exist" needs one line added, and one caveat
-
-The table above is still correct as written: **X5**, **X4 Mini**, **X1/X2** and
-**X4 Plus / Air / Pro Max** remain unevidenced. But its stated method — *"the
-vendor's own Shopify collection handles are the tightest available list"* — **is
-not the tightest list.** The tightest list is the vendor's **FCC grantee code**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| **`2BTR9-X4L`** | **2026-08-13** | **XTEINK X4 Light** ← unlisted, unannounced |
-
-**Procedural lesson worth keeping: enumerate the grantee code, not the product
-name.** `https://fccid.io/2BTR9` lists every device this company has certified
-for the US, including ones it has never mentioned. The 2026-09-04 sweep could
-not do this because no FCC ID had been read off a board and the grantee was
-unknown; the ID was published by a community member on 2026-07-23 and the
-grantee index followed from it.
-
-## Corrected family table
-
-Same evidence conventions as above. **Nothing here was measured by this research.**
-
-| | [**X3**](x3/README.md) | [**X4**](x4/README.md) | [**X4 Classic**](x4-classic/README.md) | [**X4 Pro**](x4-pro/README.md) | [**X4 Light**](x4-light/README.md) |
-|---|---|---|---|---|---|
-| **Price, 2026-09-11** | **$69** | **withdrawn** | **$79** | **$99** | **unpriced** |
-| Listed | 2025-12-11 | — | **2026-09-06** | 2026-07-21 | **never** |
-| **FCC ID** | `2BTR9-XTEINKX3` | `2BTR9-XTEINKX4` | `2BTR9-X4C` | `2BTR9-X4PRO` | **`2BTR9-X4L`** |
-| FCC granted | 2025-12-26 | 2026-01-05 | 2026-07-20 | 2026-06-16 | **2026-08-13** |
-| **FCC internal photos public** | **✅ 2026-06-24** | **✅ 2026-07-04** | 2027-01-16 | 2026-12-12 | 2027-02-09 |
-| SoC | ESP32-C3 | ESP32-C3 | **ESP32-S3** | **ESP32-S3** | **unknown** |
-| PSRAM | none | none | **8 MB** | **8 MB** | unknown |
-| Panel | **3.7″ 792×528** | 4.26″ 800×480 | 4.26″ 800×480 | 4.26″ 800×480 | unknown |
-| **PPI** | **~257** | ~219 | ~219 | ~219 | unknown |
-| **Mass** | **55 g** | ~74–80 g | **68 g** | not published | unknown |
-| **Thickness** | not published | not published | **4.9 mm** | not published | unknown |
-| **Battery** | **650 mAh** | not published | **920 mAh** | not published | unknown |
-| Touch | ✗ | ✗ | ✗ | **GT911** | unknown |
-| Frontlight | ✗ | ✗ | **✗ — settled** | **dual warm/cool** | **unknown; "Light" is not defined by the filing** |
-| Buttons | 6 ADC ladder + pwr | 6 ADC ladder + pwr | **6 discrete ISR + pwr** (+ unused GPIO4) | **2** + pwr | ≥3 visible on the case |
-| IMU | **QMI8658** | ✗ | **QMI8658** | ✗ | unknown |
-| NFC tag | **✅** | ✗ | ✗ | ✗ | unknown |
-| RTC | DS-series **(unresolved)** | **none** | BM8563 | BM8563 | unknown |
-| Gauge | **BQ27220** | bare ADC | CW2017 | CW2017 | unknown |
-| Storage | SPI, shared with display | SPI, shared | **native SDMMC** | **native SDMMC** | unknown |
-| Charging | pogo | **USB-C** | **pogo** | pogo | **pogo — 4 contacts visible in the FCC photos** |
-| Panel selection | live bus probe | live bus probe | **NVS only — no MISO** | live bus probe | unknown |
-| **Antenna** | not read | not read | **KH3216-A35, 2.30 dBi** | not read | **internal, 5.19 dBi** |
-| Wi-Fi | 2.4 GHz | 2.4 GHz | 2.4 GHz | 2.4 GHz | 2.4 GHz, 8.13 dBm max |
-| Public teardown | 2 community + **FCC internal photos** | **FCC internal photos** | **none** | **none** | **none** |
-
-### Where the X4 Classic actually sits
-
-**Between the X4 and the X4 Pro on price, and it is not a compromise between
-them on hardware.** It is the **X4 Pro's board** with the touch layer and the
-frontlight deleted and their GPIOs turned into four more buttons, plus a
-QMI8658 IMU the Pro does not have. What it inherits from the C3 X4 is the
-buttons-only *reading model* and the four bottom keys — not the board.
-
-The community's own one-line summary, offered as criticism and accurate as
-description: *"disadvantages of the X4 + disadvantages of the Pro = Classic"* —
-it keeps the X4's missing frontlight and the Pro's missing USB-C.
-
-## Two family-wide facts established this pass
-
-### The company has a legal identity
-
-**Shenzhen Xiaohu Xingtong Technology Co., Ltd.** — Room 1209, Yichuang
-International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community,
-Guanlan Street, Longhua District, Shenzhen. FCC grantee `2BTR9`, registered
-**2025-12-21**; FRN `0037772233`; responsible party Chen Chu, `chuchen@xteink.cn`.
-
-Two consequences for the naming section above: the romanisation **Xingtong**
-corresponds to **星曈** (the *dawn-light* character), which the table above records
-as a *"different second character"* in live community use — **the company's own
-legal name uses it**. And the filing lists **`xteink.cn`** as the applicant's
-domain, confirming the domain the 2026-09-04 sweep found unreachable at the apex
-but referenced inside X4 firmware (`bofi.xteink.cn`) really is theirs.
-
-### FreeInk halved the display SPI clock
-
-Commit [`39606d5a`](https://github.com/Free-Ink/freeink-sdk/commit/39606d5a),
-2026-09-09, *"Fix e-ink display buffer tracking and optimize SPI writes"*,
-replaced every Xteink profile's `displaySpiHz` with a shared
-`XTEINK_DISPLAY_SPI_HZ = 10000000u` — **20 MHz → 10 MHz** on the X4, X3,
-X3-UC8279, X4 Pro and X4 Classic alike. Anyone carrying a build pinned before
-that commit is clocking the panel twice as fast as upstream now recommends.
-
-## The evidence position has changed materially
-
-`VERIFICATION-xteink.md` §12 named **source concentration** as this tree's
-principal weakness: for the X4 Pro and X4 Classic, every technical claim traced
-to one repository at one commit, with no teardown, schematic or regulatory
-filing.
-
-| Device | 2026-09-04 | 2026-09-11 |
-|---|---|---|
-| X4 Pro | **1 custodian** (FreeInk) | **4** — FreeInk · a **physically dumped unit** ([`kycube/x4pro-emu`](https://github.com/kycube/x4pro-emu)) · an **on-hardware-tested firmware** ([`clackups/draftling`](https://github.com/clackups/draftling)) · **FCC `2BTR9-X4PRO`** |
-| X4 Classic | **1 custodian** (FreeInk) | **3** — FreeInk · **vendor listing + spec block** · **FCC `2BTR9-X4C`**. Still **no board-level second custodian**; the FCC internal photos are embargoed to 2027-01-16 |
-| X3, X4 | teardowns + a flash dump | **+ FCC internal photographs, already public** (2026-06-24 / 2026-07-04) |
-
-**What has not changed: nothing in this tree has been verified on hardware by
-this repository.** Zero devices have been in anyone's hands here. Every
-"confirmed" above means *confirmed by a cited third party*.
-
-## Round-2 verification
-
-[`VERIFICATION-xteink-round2.md`](../../VERIFICATION-xteink-round2.md).
-Proposed additions to shared and protected indexes are staged, unapplied, in
-[`scratch/xteink/index-fragments-round2.md`](../../scratch/xteink/index-fragments-round2.md).
diff --git a/devices/xteink/firmware-ecosystem.md b/devices/xteink/firmware-ecosystem.md
deleted file mode 100644
index ea9483d..0000000
--- a/devices/xteink/firmware-ecosystem.md
+++ /dev/null
@@ -1,449 +0,0 @@
-# Xteink firmware ecosystem — the hardware-side map
-
-> **Which firmware runs on which Xteink board, and what a new board has to provide
-> to be supported.** The [software tree](../../software/README.md) documents these
-> projects as software; this page is the view from the hardware.
->
-> Snapshot **2026-09-07**, from records dated 2026-09-01/04. **Nothing here was
-> built, flashed or run.** Repository facts are `executed-success` on the read;
-> everything about behaviour is `inferred` unless it cites a third party.
-
-## Why this page exists
-
-Four of the five Xteink products are ESP32 devices with **no vendor SDK, no vendor
-board-support package and no vendor documentation of any kind**. Every development
-path in this family is community-built, and the community converged on a single
-stack. If you own one of these devices, the practical question is not "how do I
-program it" — it is "which of these projects already knows about my board, and at
-what commit".
-
-The five products, and where each stands:
-
-| Product | Platform | In the ecosystem? |
-|---|---|---|
-| [**X3**](x3/README.md) | ESP32-C3 | ✅ two board profiles (UC8253 and UC8279d) |
-| [**X4**](x4/README.md) | ESP32-C3 | ✅ — **the device that created the ecosystem** |
-| [**X4 Pro**](x4-pro/README.md) | ESP32-S3 | ✅ — **the design floor**, and the only target of the native-plugin fork |
-| [**X4 Classic**](x4-classic/README.md) | ESP32-S3 | ✅ profile exists; the *product* is not sold internationally |
-| [**S4**](s4/README.md) | **Android 11** | ❌ **and never will be.** Different architecture. No SoC is even identified |
-| [**Nano / Tong Card**](nano/README.md) | **passive, NFC-powered** | ❌ Not a computer. No MCU at all |
-
-⚠ One recurring community error worth killing here: an r/EDC carry post describes
-an *"Xteink S4 e reader (running crosspoint)"*. **CrossPoint is ESP32 firmware and
-cannot run on an Android device.** The [S4 record](s4/README.md) records three
-possible explanations and endorses the mundane one — the owner mislabelled an X3 or
-X4 — because the same corpus contains a post titled "Got my white (?) X5" whose
-author later corrected it to "X4".
-
----
-
-## 1. The stack
-
-```
-open-x4-epaper/community-sdk          MIT · CidVonHighwind et al.
-        │ code derived, re-architected — SSD1677 and UC8253 init sequences and LUTs
-        ▼
-Free-Ink/freeink-sdk                  MIT · ★248 · 95 forks · created 2026-06-03
-        │  ← panel drivers, board profiles, capability gates, device managers, FreeInkBook
-        │  git submodule (branch-pinned in .gitmodules; the SHA is in the gitlink)
-        ▼
-crosspoint-reader/crosspoint-reader   MIT · ★7,538 · 1,621 forks · created 2025-12-03
-        ├── uxjulia/CrossInk                    ★~1,451   X3 · X4 · Sticky
-        ├── ma-r-s/crossplay                    ★~17      C3 · Sticky · X4 Pro · PaperMono
-        ├── mekhontsev/crosspoint-reader        —         X4 Pro only — native plugin host
-        ├── MarsTechHAN/crosspoint-reader-mono  ★1        PaperMono port
-        └── ~9 further named derivatives, most of them detached re-uploads
-```
-
-**Note the inversion at the top: CrossPoint predates its own SDK by six months.**
-FreeInk is a later re-architecture of the SDK CrossPoint was already using, not an
-upstream that CrossPoint adopted from outside. Anyone reading the star counts
-(7,538 vs 248) as "big project depends on small project it found" has the history
-backwards. Full analysis:
-[FreeInk SDK record](../../software/frameworks/freeink-sdk/README.md#lineage--and-why-the-freeink-came-first-reading-is-wrong).
-
-**The FreeInk SDK board profile header is the single most authoritative hardware
-document for four of these five devices.** Every board-level pin, address and chip
-in this tree traces to it, to a parsed OEM flash image, to a teardown photograph,
-to a vendor statement, or to a labelled community report. **Vendor marketing prose
-is not used as evidence anywhere**, because the X3 listing advertises a frontlight
-the device does not have.
-
----
-
-## 2. Support matrix, by firmware
-
-### 2.1 CrossPoint Reader — `crosspoint-reader/crosspoint-reader`, branch `develop`
-
-MIT. Fifteen build environments across five device families, listed on `develop`
-and retrieved **2026-09-04**.
-
-| Env family | PlatformIO board | Device | SoC assumption |
-|---|---|---|---|
-| `default`, `gh_release`, `gh_release_rc`, **`slim`** | `esp32-c3-devkitm-1` | **Xteink X3 / X4 (C3-class)** | RISC-V, **no PSRAM** — *this env sets the project's memory ceiling* |
-| `sticky`, `sticky-gh_release`, `sticky-gh_release_rc` | `esp32-s3-devkitc1-n16r8` | Seeed reTerminal Sticky | S3, 16 MB flash, 8 MB PSRAM |
-| `x4pro`, `x4pro-gh_release`, `x4pro-gh_release_rc` | `esp32-s3-devkitc1-n16r8` | **Xteink X4 Pro** | idem |
-| `x4c`, `x4c-gh_release` | `esp32-s3-devkitc1-n16r8` | **Xteink X4 Classic** | idem |
-| `papermono`, `papermono-gh_release`, `papermono-gh_release_rc` | `esp32-s3-devkitc1-n16r8` | [**M5Stack PaperMono**](../m5stack/papermono/README.md) | idem, and the PaperMono has a **hard OPI-PSRAM requirement** |
-
-Two things fall out of that table:
-
-- **Every S3 target shares one board definition** — `esp32-s3-devkitc1-n16r8`,
-  16 MB flash + 8 MB octal PSRAM. Four physically different products, one memory
-  configuration.
-- **PaperMono support is upstream, not a fork-only capability.** The
-  7,500-star repository builds for a board M5Stack shipped in August 2026.
-
-⚠ **No commit SHA is pinned in the software record.** Identity is by branch. Pin
-`develop`'s HEAD before citing specific code. Likewise `.gitmodules` pins the
-FreeInk SDK **by branch** (`main`); the actual revision lives in the gitlink, so
-**a fork can behave differently from upstream without a single line of fork-owned
-code differing**.
-
-### 2.2 FreeInk SDK — `Free-Ink/freeink-sdk`, branch `main`
-
-MIT. The Xteink records in this tree cite commit
-**`24003795381a6c23630a26472ae3b06550333e71`**. Board profiles and their build
-flags:
-
-| Profile | Build flag | Device | Panel drivers auto-enabled |
-|---|---|---|---|
-| `XTEINK_X3` | `-DFREEINK_DEVICE_X3=1` | X3, UC8253 batches | links **both** X3 drivers |
-| `XTEINK_X3_UC8279` | (same flag) | X3, UC8279d batches from ~2026-07 | idem |
-| `XTEINK_X4` | `-DFREEINK_DEVICE_X4=1` | X4 | SSD1677 · UC8179 · UC8279 |
-| `XTEINK_X4_PRO` | `-DFREEINK_DEVICE_X4PRO=1` | X4 Pro | SSD1677 · UC8179 · **+ `FREEINK_CAP_TOUCH`, `FREEINK_CAP_FRONTLIGHT`** |
-| `XTEINK_X4_CLASSIC` | `-DFREEINK_DEVICE_X4CLASSIC=1` | X4 Classic | SSD1677 · UC8179 · UC8279_X4 · `FREEINK_CAP_RTC` · `FREEINK_BATTERY_I2C_GAUGE` · `FREEINK_SD_SDMMC`; **touch and frontlight left off** |
-| `PAPER_MONO` | — | M5Stack PaperMono | SSD1677 |
-
-Panel drivers shipped in the SDK: **SSD1677, UC8179, UC8253, UC8279, ED2208,
-IT8951**, plus external-library-backed panels.
-
-The SDK's architectural thesis, in its own words: *"Adding a new device means
-adding **data** (a board profile + a driver config), not editing the generic
-code."* That is what makes §4 short.
-
-⚠ **The panel init sequences and waveform LUTs are third-party derived work**,
-credited in `NOTICE` to the OpenX4 E-Paper Community SDK and to CidVonHighwind.
-Worth knowing before treating them as authoritative for a given panel.
-
-### 2.3 CrossPlay — `ma-r-s/crossplay`, branch `xteink`
-
-MIT. Adds ~26 games and tools alongside the reader. Envs:
-
-| Env | Device |
-|---|---|
-| `default`, `gh_release`, `gh_release_rc`, `slim` | C3, inherited from upstream |
-| `sticky`, `gh_release_sticky` | Seeed reTerminal Sticky |
-| **`x4pro`, `gh_release_x4pro`** | **Xteink X4 Pro — the design floor** |
-| `papermono`, `papermono-gh_release`, `papermono-gh_release_rc` | M5Stack PaperMono |
-
-**It consumes a *fork* of the SDK** — `ma-r-s/freeink-sdk`, branch
-`x4pro-measured-insets` — so a port here has two moving upstreams, not one.
-
-⚠ **The `papermono` envs are present in `platformio.ini` and absent from
-`LOCAL_SCOPE.md`, and nobody has reported running CrossPlay on a PaperMono.**
-Recorded as an open question, not as "supported".
-
-**One CrossPlay change is a hardware fact, not a software preference.** Its
-`src/network/OtaUpdater.cpp` repoints the release URL because **upstream's would
-flash a C3 build onto an S3**. That is the sharpest available illustration of why
-"X4 Pro" being an S3 and "X4" being a C3 matters.
-
-### 2.4 The rest, by device
-
-| Project | Devices | Note |
-|---|---|---|
-| `uxjulia/CrossInk` | **X3, X4, Sticky only** | The major second-tier fork. **No PaperMono support.** Notable for having shipped **ESP-NOW straight from an Activity** with no SDK capability gate — the working precedent for bypassing the abstraction |
-| `mekhontsev/crosspoint-reader` + `crosspoint-plugins` + `pagewire` | **X4 Pro only** | MIT. Native C++ ELF plugin host loaded from SD against an ABI. Self-described experimental |
-| `MarsTechHAN/crosspoint-reader-mono` | PaperMono | True fork, ★1 |
-| `juicecultus/crosspoint-reader-papers3` | M5PaperS3 | Detached re-upload, ★67 |
-| `vjFaLk/esphome-xteink` | X4 Pro | Exposes the device to Home Assistant as an ESPHome component |
-| `thepropm/proink-os` | X4 Pro | From-scratch firmware on the FreeInk SDK |
-| `parsimo2010/xteink-ft8` | X4 Pro | FT8 amateur-radio display |
-| `MrStu82/crosspoint-llama-pro` | X4 Pro | Explicitly *"ESP32-S3, GT911 touch, dual warm/cold frontlight"* |
-
-⚠ **Do not measure this ecosystem from GitHub's `/forks` listing.** Of fourteen
-named, actively-discussed derivatives, **only five are GitHub forks**; the other
-nine were re-uploaded as fresh repositories and are detached (`fork: false`,
-`parent: null`), including the top-ten-by-stars CrumBLE and the CJK port. The
-`1,621` figure simultaneously overcounts, because most forks of any popular
-repository carry zero commits. **Enumerate by name.**
-
-### 2.5 A hardware-relevant consequence of fork age
-
-**Being behind upstream is a brick-risk signal in this ecosystem, not a tidiness
-metric.** Xteink revises hardware silently — the X3's controller changed from
-UC8253 to UC8279d around July 2026, and the X4 Pro ships three different
-controllers on identical wiring — and upstream carries the fixes. CrossPoint's own
-1.5 release notes say it directly: *"Other forks will need to pull the latest SDK
-to avoid **soft bricking locked units**."*
-
----
-
-## 3. The panel-controller runtime-detection trick
-
-**This is the mechanism that lets one binary serve several boards, and it is the
-most reusable idea in this whole ecosystem.** It is worth understanding even if you
-never touch an Xteink.
-
-### 3.1 The problem
-
-The X4, X4 Pro and X4 Classic each ship with **at least three different display
-controllers depending on production batch, on identical wiring**: a Solomon Systech
-**SSD1677**, or an UltraChip **UC8179**, or an UltraChip **UC8279**. The X3 ships
-either a **UC8253** or, from around July 2026, a **UC8279d**.
-
-The command sets differ. A firmware that assumes the wrong one produces a panel
-that resets, runs waveforms, and **never develops an image** — a failure mode the
-X4 Pro bring-up spent months on. And **there is no external revision marking that
-tells you which you have before powering the unit on.**
-
-### 3.2 The trick
-
-**UC81xx parts answer the vendor commands `VER (0x70)` and `FLG (0x71)`. The
-SSD16xx family does not answer them at all.**
-
-The SDK exploits that with a bit-banged half-duplex read on the display pins —
-which are normally write-only — after a reset pulse:
-
-1. Bit-bang a half-duplex 4-wire SPI **read** on the display bus after reset.
-2. Issue **`VER (0x70)`** — 5 bytes — and **`FLG (0x71)`** — 1 byte.
-3. Because the SSD family never drives the line, a released SDA floats to a
-   **uniform `0x00` or `0xFF`** through the pull-up.
-4. **Match = UltraChip** when `FLG` is neither `0x00` nor `0xFF`, has `BUSY_N`
-   (bit 0) set, **and** `VER` is non-uniform.
-5. Then **`VER` byte 2 (`LUT_VER`)** discriminates the family member:
-   `0x02` / `0x68` / `0x69` → **UC8279**; anything else → **UC8179**.
-
-```c
-// freeink-sdk XteinkDetect.cpp:113-119, commit 2400379
-bool matchUc81xx(const uint8_t ver[5], uint8_t flg) {
-  if (flg == 0x00 || flg == 0xFF) return false;
-  if ((flg & 0x01) != 0x01) return false;
-  return !verIsFloating(ver);
-}
-```
-
-The probe logs `[XTDET] bus probe VER=… FLG=… -> UltraChip|default|inconclusive`
-over serial, plus the MTP header (`RMTP 0xA2`) when the status line was driven —
-`0xA5` at byte 0 means a UC part with a programmed MTP.
-
-### 3.3 ⚠ A negative result worth keeping
-
-An earlier matcher additionally required `ver[1] != 0`. **A shipping X4 Pro UC8179
-was then observed returning `VER = 00 00 01 FF FF` — a `CHIP_VER` byte of
-`0x00` — and was wrongly rejected.** The matcher now deliberately **does not pin
-any specific `CHIP_VER` value**. Do not reintroduce that check.
-
-Two related questions remain open on the X3 side: what the **UC8253** actually
-answers to `0x70`, and whether production MTP programs `CHIP_VER` to something
-other than `0x03`.
-
-### 3.4 The X4 Classic exception, and why it is dangerous
-
-**The X4 Classic's display bus has no MISO line at all**, so the probe cannot work
-— the released line always floats to `0xFF`. It is the one device in the family
-where **NVS is authoritative**:
-
-```
-NVS namespace hw_calib, key screenType (u8):
-  1 or 0x0B → UC8179
-  2 or 0x0C → UC8279
-  3 / default / unset → SSD1677
-```
-
-The factory writes this once. On every *other* device the SDK reads
-`hw_calib/screenType` **for diagnostics only** and never decides on it, because a
-full-flash image taken from another unit overwrites it and can therefore name the
-wrong panel. On the X4C there is no live check to override it.
-
-> **Consequence: restoring an X4 Classic from someone else's full-flash image can
-> leave it with the wrong panel driver and no way to detect that.**
-
-### 3.5 The same idea, applied to the board itself
-
-The SDK uses a second runtime fingerprint to tell an **X3 from an X4** — they share
-a SoC, a flash size and a firmware binary:
-
-- Probe the C3's secondary I²C bus (**SDA GPIO20 / SCL GPIO0**) for **`0x55`**
-  (BQ27220 fuel gauge), **`0x68`** (DS-series RTC) and **`0x6B`** (QMI8658 IMU).
-- **Find them → X3. Find nothing → X4.** The X4 has no I²C peripherals at all, and
-  that absence *is* the discriminator.
-
-⚠ **That probe must be compiled out on an S3.** On the C3, GPIO20 and GPIO0 are
-ordinary pins; on the **ESP32-S3** they are **USB D+ and a boot strap**. Running
-the C3 fingerprint on an S3 would poke USB D+ and a strapping pin at boot.
-`XteinkDetect` compiles the path to a no-op unless a C3 profile is in the build.
-
-### 3.6 Prior art elsewhere in this repository
-
-The pattern — *probe at boot, branch on capability rather than on a compile-time
-device identity* — recurs:
-
-| Device | Probe | Discriminates |
-|---|---|---|
-| Xteink X4 Pro / X4 / X3 | `VER`/`FLG` on the panel bus | SSD16xx vs UC8179 vs UC8279 |
-| Xteink X3 vs X4 | I²C addresses `0x55`/`0x68`/`0x6B` | which board |
-| [M5Stack PaperMono vs Lite](../m5stack/papermono/features/nfc.md) | write M5IOE1 `IO4`, then read ST25R3916 register `0x7F` expecting `0x05` | Pro vs Lite. ⚠ **M5GFX cannot make this distinction** — it masks NFC out of board detection, so both SKUs land on one enum |
-| [Cardputer ADV vs v1.x](../m5stack/cardputer-adv/README.md#board-autodetect) | drive G8/G9 as input-pulldown and read them | TCA8418 vs 74HC138 keyboard. ⚠ The test is only *"are there pull-ups"* — anything pulling those pins high on a v1.x makes M5GFX declare it an ADV and the keyboard stops working |
-| [Cap LoRa-1262 vs Cap LoRa868](../m5stack/cap-lora-1262/features/io-expander-and-rf-switch.md) | probe I²C `0x43` | which Cap is fitted |
-
-The recurring lesson is in the two ⚠ rows: **a fingerprint that tests a proxy
-rather than the thing itself will eventually misfire.** The `VER`/`FLG` probe is
-the good version because it asks the controller to identify itself.
-
----
-
-## 4. What a new board has to provide to be supported
-
-`inferred` from the SDK's design and from three measured ports. This is the
-checklist to work through before proposing a board.
-
-### 4.1 The measured cost of a port
-
-From the FreeInk SDK record (`reported-working`, measured on real ports):
-
-| Port | Files touched | Lines |
-|---|---|---|
-| Xteink X4 Classic | 7 | +295 |
-| M5Stack PaperS3 | 10 | +397 |
-| OnePage (a new MCU) | 8 | +245 |
-
-**A typical port is 7–10 files and 250–400 lines.** Order matters: the SDK port
-comes first, then the consuming firmware's build environment — CrossPoint's
-`ROADMAP.md` says so explicitly.
-
-⚠ **There is no CI validation for device ports in the SDK**, against CrossPoint's
-multi-environment build matrix. A port can break without the SDK's own tests
-noticing.
-
-### 4.2 The hardware checklist
-
-| # | Requirement | Why | Consequence if absent |
-|---|---|---|---|
-| 1 | **An ESP32-C3 or ESP32-S3** | Those are what the SDK targets in practice | Anything else is a new MCU port (the `OnePage` port is the precedent that it is possible) |
-| 2 | **A supported panel controller** — SSD1677, UC8179, UC8253, UC8279, ED2208 or IT8951 | Drivers ship | A new driver, plus **waveform LUTs, which are the hard part** and are third-party derived work. See [`guides/hardware/e-paper-displays.md`](../../guides/hardware/e-paper-displays.md) |
-| 3 | **PSRAM, if you want the good rendering path** | Multi-buffer rendering, damage-window partial refresh and large book indices need it | On a C3 they are simply unavailable. **The C3 env sets CrossPoint's memory ceiling**, and OTA out-of-memory was *observed* on the X3 — CrossPoint stopped using GitHub releases because of it |
-| 4 | **A MISO line on the display bus**, if you want runtime controller detection | §3 | You inherit the X4 Classic's problem: a stored value is your only source of truth, and it can be wrong |
-| 5 | **An input path the SDK models** — an ADC ladder, discrete GPIOs, or touch | Input manager | CrossPlay's stated design floor is **"two side keys plus touch"**; firmware that works there is expected to degrade gracefully elsewhere |
-| 6 | **Storage** — SPI microSD, or 1-bit SDMMC | `FREEINK_SD_SDMMC` | ⚠ **1-bit SDMMC additionally needs `-DUSE_BLOCK_DEVICE_INTERFACE=1` in the *consumer* build.** A hand-rolled env that forgets it compiles and then fails to mount the card |
-| 7 | **A documented master peripheral rail**, asserted first at boot | e.g. the X4 Pro's **GPIO1**, driven HIGH before any other bring-up | Symptom: *"EPD BUSY never asserts, SD returns 0xFF"* |
-| 8 | **Known enable polarities** | The X4 Pro's touch (GPIO2) and SD (GPIO5) enables are **active-LOW**, the opposite of the usual convention | Driving them HIGH — the naive "enable" — leaves the touch controller silent and breaks every SD block read with error `0x107` |
-| 9 | **A battery power story** | latch, gauge or bare ADC | The X4's **GPIO13 gates the battery MOSFET**, and *"at least one hardware revision in the field does not self-latch"*. Always assert the latch |
-| 10 | **Bezel viewable insets** | Screens draw under the glass without them | The X4 Pro's are `{9,7,3,7}` |
-| 11 | **A flashing route that survives a USB lock** | §5 | Otherwise you cannot get your first image on |
-
-### 4.3 ⚠ The trap: GPIO numbers do not port within this family
-
-Three worked examples from one family, all real:
-
-- **`GPIO13` means three different things.** SD power rail on the X3
-  (**active-HIGH**), battery power-off latch on the X4, unused on the S3 boards.
-  **Never port power code between them.**
-- **The X4 Classic's display pins are a permutation of the X4 Pro's** on the same
-  SoC and the same panel: DC 18 → **14**, RST 14 → **10**, BUSY 6 → **18**. SCLK,
-  MOSI and CS are shared. Porting display code without changing those three
-  produces a panel that resets and never develops an image.
-- **`GPIO0` on an X4 Pro is the Left button *and* the boot strap.** Powering on
-  with Left held enters download mode.
-
-### 4.4 What a board profile actually declares
-
-Read the [X4 Classic record](x4-classic/README.md#development) for a complete
-worked example — it is the shortest and the most explicit, because the whole board
-was decoded from a firmware dump and the SDK records its confidence per pin:
-
-```ini
-[env:x4c]
-extends = base
-board = esp32-s3-devkitc1-n16r8
-board_build.mcu = esp32s3
-build_flags =
-  ${base.build_flags}
-  -DBOARD_HAS_PSRAM
-  -DUSE_BLOCK_DEVICE_INTERFACE=1   ; SD is 1-bit SDMMC
-  -DFREEINK_DEVICE_X4CLASSIC=1
-```
-
-That, plus the profile struct, is the port.
-
-**What the profile has no field for: a radio.** Grepping the SDK for the
-PaperMono's LoRa SPI pins returns nothing, and there is no radio struct. See
-[adding LoRa, NFC and an RGB sidelight](../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-for what that means and what the four missing pin constants are. Note that the SDK
-**does** already carry `T5S3_LORA_CS/IRQ/RST/BUSY` for the LilyGO T5S3 — so a
-second LoRa board already exists to justify a real `FREEINK_CAP_LORA` abstraction.
-
----
-
-## 5. Getting your first image onto the hardware
-
-Firmware support is worthless if the device will not accept a flash. **Many
-Xteink units — X3, X4 and X4 Pro alike — ship from the factory with USB flashing
-disabled.** `esptool` cannot see them. The community calls these "USB-locked".
-
-| Path | What it does | Status |
-|---|---|---|
-| **CrossPointReader.com web flasher** | *"OTA Unlock usb locked stock devices by flashing CrossPoint and CrossInk"* | `reported-working` — 346 pts |
-| **SD-card update** | Drop `update.bin` on the SD root, hold **Power + Up** at boot; the **stock bootloader** picks it up. No cable, no unlock | `reported-working` — ⚠ its own author says *"that path relies on stock-bootloader behavior I don't control, so confirm the button combo for your unit first"* |
-| **Developer-unlocked units** | Xteink sells an explicitly unlocked variant | `reported-working` |
-| `OvermindDL1/xteink-unlocker` | Tauri/Rust desktop app implementing the unlock | not inspected in depth |
-
-⚠ **Lock state is not predictable from the sales channel.** One owner who bought
-three units reported an Amazon X3 unlocked, an official-store X3 **locked**, and an
-AliExpress X4 locked.
-
-⚠ **Make a full-flash backup before you do anything.** Only **one** Xteink factory
-image exists publicly anywhere — the X4's 16 MB dump, archived in this repository.
-**No X4 Pro or X4 Classic stock image was located.**
-
-Per-device detail: [X4 Pro development](x4-pro/development.md) ·
-[factory firmware](x4-pro/factory-firmware.md).
-
----
-
-## 6. Where the hardware and software trees meet
-
-| From here | To there |
-|---|---|
-| [X3](x3/README.md) · [X4](x4/README.md) · [X4 Pro](x4-pro/README.md) · [X4 Classic](x4-classic/README.md) | [CrossPoint Reader](../../software/applications/crosspoint-reader/README.md) — build envs and device support |
-| Board profiles, panel drivers, capability gates | [FreeInk SDK](../../software/frameworks/freeink-sdk/README.md) |
-| X4 Pro as the design floor; the OTA C3/S3 hazard | [CrossPlay](../../software/applications/crossplay/README.md) |
-| Which derivative is a real fork, and what "behind" costs | [Fork network](../../software/ecosystems/crosspoint-freeink/fork-network.md) |
-| Can a plugin reach a bus? (**No** — 81-symbol allow-list, link fails) | [CrossPoint plugin systems](../../software/applications/crosspoint-reader/plugins/README.md) |
-| Adding radios to this class of firmware | [Radios on the PaperMono](../../software/ecosystems/crosspoint-freeink/radios-on-papermono.md) · [the capability guide](../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md) |
-| Running the firmware with no hardware at all | [Simulator build notes](../../software/tooling/crosspoint-simulator-build-notes.md) — ✅ `executed-success` on NixOS |
-| Content pipeline | [Calibre](../../software/tooling/calibre/README.md) |
-| Why the SoC choice constrains all of this | [SoC choice for battery e-ink devices](../../guides/hardware/soc-choice-for-battery-eink-devices.md) |
-| Where these boards sit in the market | [Handheld and e-ink device landscape, 2026-09](../../guides/markets/handheld-and-eink-device-landscape-2026-09.md) |
-
----
-
-## 7. Open questions and evidence boundary
-
-- **Nothing on this page was built, flashed or run.**
-- **No commit SHA is pinned for CrossPoint `develop` or FreeInk `main`** in the
-  software records; the FreeInk commit `2400379…` cited here is the one the Xteink
-  device records read. Pin HEAD before citing code.
-- **Whether the `papermono` envs — upstream's or CrossPlay's — have ever been run
-  on real hardware by anyone is unknown.**
-- **The FreeInk SDK declares `ImuType::None` for the PaperMono** despite a BMI270
-  being fitted and wired. Deliberate or unported: **not established**.
-- **What the UC8253 answers to `0x70`** is not established, and the UC8279d X3
-  variant *"has never been on a bench"* — the SDK's own words.
-- **The X3's RTC is unresolved**: the SDK drives a DS3231, the English teardown
-  captions "DS1307", the Chinese BOM says only "DS-series". All at `0x68`.
-- **The X4 Classic's `GPIO4` role is unknown** — an input, but not
-  interrupt-attached, so not a button.
-- The **74 % single-author concentration** in SDK commits is carried over from an
-  earlier analysis and was **not re-measured**.
-- **No binary size, flash usage, heap figure or build time exists for any
-  environment of any of these projects.**
-
-## See also
-
-[Family index](README.md) · [X3](x3/README.md) · [X4](x4/README.md) ·
-[X4 Pro](x4-pro/README.md) · [X4 Classic](x4-classic/README.md) ·
-[S4](s4/README.md) · [Nano](nano/README.md) ·
-[M5Stack PaperMono](../m5stack/papermono/README.md) ·
-[`software/`](../../software/README.md)
diff --git a/devices/xteink/nano/README.md b/devices/xteink/nano/README.md
deleted file mode 100644
index 2357e99..0000000
--- a/devices/xteink/nano/README.md
+++ /dev/null
@@ -1,153 +0,0 @@
-# Xteink Nano — "Tong Card" (瞳卡)
-
-> A **battery-less, NFC-powered four-colour e-paper display card** that snaps
-> magnetically to the back of a phone. **Not a reader, not an ESP32 device, and
-> not part of the CrossPoint / FreeInk firmware ecosystem.**
-> Research retrieval date **2026-09-04**. **Depth: sourced stub.**
-
-## Why this record exists
-
-The Nano was **missed by the first pass of this research** and surfaced only on a
-second, wider community sweep. It is a genuine fifth Xteink product line, it is
-sold internationally on AliExpress, and it is **the thing people confuse with the
-[X3's embedded NFC tag](../../../components/unidentified/xteink-x3-x4/nfc-tag-iso14443a/README.md)**.
-Recording it prevents that conflation and stops a future pass rediscovering it.
-
-## Identity
-
-| Field | Value | Evidence |
-|---|---|---|
-| Chinese name | **瞳卡** (*tóng kǎ*, "pupil card") | **[COMM]** [r/XTEINK `1smdpjq`](https://old.reddit.com/r/XTEINK/comments/1smdpjq/) |
-| English names in use | **"Tong Card"** (community/AliExpress) · **"Nano"** (Xteink's own app) | **[COMM]** same |
-| Class | Passive **NFC-powered e-paper display card** | **[COMM]** firsthand owner |
-| Display | **Four-colour e-ink** | **[COMM]** firsthand owner |
-| Power | **None — no battery.** Harvested from the phone's NFC field | **[COMM]** |
-| Attachment | Magnetic, phone-back | **[COMM]** |
-| Market | **China-first.** Not listed on `xteink.com` | **[VENDOR]** absence + **[COMM]** |
-| Sales channel observed | **AliExpress** | **[COMM]** |
-
-**The name mapping is established by a single, decisive observation.** A user
-found the string `我的瞳卡` ("My Tong Card") in the *international* build of the
-official Xteink Android app, untranslated, and identified 瞳卡 as *"the chinese
-name of the Nano"* ([r/XTEINK `1smdpjq`](https://old.reddit.com/r/XTEINK/comments/1smdpjq/),
-2026-04-15). That ties the community's "Tong Card" to Xteink's own "Nano".
-
-## What is established, and how
-
-### It works, but not with the international app
-
-> "Basically it is a **four-colour eink display with NFC capability** that allows
-> you to load an image onto it and then snap it onto the back of your phone or
-> other magnetic surface. When I saw one on AE I took a chance and bought one…
-> **So far I haven't been able to** [load an image] **no matter what I have
-> tried.** … unless you have a way of doing this through the official channels I'd
-> hold off getting one at the moment."
-> — [r/xteinkHax `1sbjsr3`](https://old.reddit.com/r/xteinkHax/comments/1sbjsr3/), 2026-04-03, **110 points** · **firsthand ownership**
-
-The blocker is that image upload requires the **China-mainland Xteink app**. A
-second owner reported the same: *"I'm stuck too, got mine and haven't been able to
-find a work around to get onto the China mainland app."* — **firsthand ownership**
-
-### A third-party app works
-
-The same thread resolves it. The original poster confirms:
-
-> "I have an app, **NFC Eink**, that works so I'm good thanks."
-> — **firsthand, demonstrated**
-
-and a third user points to a written procedure:
-`https://www.spokenlikeageek.com/2026/04/09/xteink-tong-card-in-use/`
-(the OP is also its author). **Not retrieved this session** — recorded as an open
-acquisition.
-
-### It is probably a re-badged Waveshare module
-
-> "Try this app, there is a QR code towards the bottom. **I bet it's a waveshare
-> display.** I got one for my wife for Christmas and it's awesome but kind of a
-> pain to get working. `https://www.waveshare.com/wiki/1.54inch_NFC-Powered_e-Paper_(G)`"
-> — [r/xteinkHax `1sbjsr3`](https://old.reddit.com/r/xteinkHax/comments/1sbjsr3/) · **informed interpretation, not verified**
-
-**This is a hypothesis, not a finding**, and it is flagged as such. But it is a
-well-motivated one: Waveshare's "NFC-Powered e-Paper" line is exactly this product
-category — battery-less, NFC-written, multi-colour — and the fact that a
-*third-party* app written for Waveshare-class NFC e-paper successfully drives the
-Tong Card is meaningful circumstantial support.
-
-A competing product the same thread raises, the Vidabay Snap
-(`theverge.com/tech/917067/...`), was tried by the OP and **does not work** —
-*"Thanks for the tip but it doesn't. NFC Eink works but isn't great."* A useful
-negative result: whatever protocol the Tong Card uses, it is not universal across
-NFC e-paper cards.
-
-### Xteink's own app support is partial and wobbly
-
-- The international Android app briefly exposed the Nano wallpaper section
-  **untranslated**, then *"They seem to have removed it with a new update."*
-- On iOS: *"Nano is wallpapers show in the international iOS app, but no upload
-  yet."* — **firsthand ownership**
-
-So as of the snapshot the official international path is **incomplete**.
-
-## What is completely unknown
-
-**Everything at the hardware level.** No teardown, no photograph of the internals,
-no part identification of any kind:
-
-| Unknown | Note |
-|---|---|
-| **NFC front-end / e-paper driver IC** | Not identified |
-| **Display size and resolution** | *"four-colour"* is the only display fact; the suspected Waveshare sibling is 1.54″, **not confirmed for this product** |
-| **Tag type / protocol** | Unknown. Only that "NFC Eink" drives it and the Vidabay app does not |
-| **Price** | Never captured |
-| **Whether Xteink designed it or re-badged it** | Open |
-| **Relationship to the X3's embedded tag** | **None established.** Different products; see below |
-
-## Do not confuse it with the X3's NFC tag
-
-| | **Nano / Tong Card** | **[X3's embedded NFC tag](../../../components/unidentified/xteink-x3-x4/nfc-tag-iso14443a/README.md)** |
-|---|---|---|
-| What | A **separate product** you buy | A **passive tag inside the X3** |
-| Display | Yes — four-colour e-paper | No |
-| Power | Harvested from the phone's NFC field | None needed; it stores bytes |
-| Purpose | Show an image on your phone's back | Trigger a phone automation / store contact info |
-| Written with | The Xteink China app, or "NFC Eink" | Any Android NFC writer app |
-
-The confusion is real and documented: the user who found the Nano section in the
-official app initially *"thought it was for the X3's NFC functionality"*.
-
-## Community and channel notes
-
-Two facts from this thread are worth carrying into the family record:
-
-1. **The post was removed from the official subreddit.** *"(This post was removed
-   by the mods on the official subreddit)"* — and r/xteinkHax exists partly
-   because of that.
-2. **The subreddit split is now explained.** *"r/xteinkreader is the main sub and
-   **it's run by the company**; there's another one r/XTEINK which is opened by
-   supporters"* — **informed community statement**. That is directly relevant to
-   how the community evidence in this tree should be weighted: one of the three
-   subreddits is vendor-operated.
-
-## Sources
-
-| ID | What | URL | Retrieved | Type | Establishes |
-|---|---|---|---|---|---|
-| N01 | "I bought an Xteink Tong Card so you don't have to!" | <https://old.reddit.com/r/xteinkHax/comments/1sbjsr3/> | 2026-09-04 | community, **firsthand ownership** | Product exists; four-colour NFC e-paper; China-app lock-in; NFC Eink works; Vidabay app does not; Waveshare hypothesis; **the official sub removed the post** |
-| N02 | "Xteink Nano option in the official app" | <https://old.reddit.com/r/XTEINK/comments/1smdpjq/> | 2026-09-04 | community, **firsthand** | **瞳卡 = Nano**; the international app briefly exposed it, then removed it; iOS shows wallpapers but cannot upload |
-| N03 | Waveshare 1.54″ NFC-Powered e-Paper (G) wiki | <https://www.waveshare.com/wiki/1.54inch_NFC-Powered_e-Paper_(G)> | **not retrieved** | vendor | The suspected sibling product line — **hypothesis only** |
-| N04 | "Xteink Tong Card in use" | <https://www.spokenlikeageek.com/2026/04/09/xteink-tong-card-in-use/> | **not retrieved** | community blog | A written working procedure, by the N01 poster |
-
-## What would turn this into a real record
-
-In rough order of value:
-
-1. **Retrieve N04 and N03** — cheap, and N04 is a firsthand working procedure.
-2. **A teardown**, or even a photograph of the card's back with markings.
-3. **An Android NFC tag-info dump** (technology list, UID prefix) — 30 seconds for
-   any owner, and it would likely identify the driver IC family outright.
-4. An AliExpress listing capture for price, dimensions and resolution.
-
-## See also
-
-[Family index](../README.md) ·
-[X3 NFC feature guide](../x3/features/nfc.md) — the thing this is *not*
diff --git a/devices/xteink/s4/README.md b/devices/xteink/s4/README.md
deleted file mode 100644
index 65d1fc3..0000000
--- a/devices/xteink/s4/README.md
+++ /dev/null
@@ -1,143 +0,0 @@
-# Xteink S4
-
-> **STUB.** This is an **Android** device, not an ESP32 device, and it is
-> therefore outside the CrossPoint / FreeInk firmware ecosystem that the rest of
-> this tree documents. Research retrieval date **2026-09-04**.
->
-> **State this plainly: no board-level fact about the S4 is established here.**
-> There is no teardown, no firmware dump, no board profile, no schematic and no
-> chip identification of any kind. Everything below is a community-relayed vendor
-> claim.
-
-## Why it has a record at all
-
-Three reasons:
-
-1. It is a **real, shipping Xteink product** and the family index would be wrong
-   without it.
-2. It is the device the community repeatedly says they will buy **instead of** the
-   X4 Pro, so it belongs in that comparison.
-3. Recording it as a **stub with named gaps** stops the next agent from
-   re-discovering it and assuming it was missed.
-
-## Identity
-
-| Field | Value | Evidence |
-|---|---|---|
-| Name | **Xteink S4** | **[COMM]** |
-| Platform | **Android 11** | **[COMM]** AliExpress preorder listing, relayed |
-| Class | Small Android e-ink reader | — |
-| Market | **China first.** *"Android-based S4 in the works, **China-only so far**"* | **[COMM]** [r/XTEINK `1v5gh6x`](https://old.reddit.com/r/XTEINK/comments/1v5gh6x/), 2026-07-24 |
-| Status | Shipping to owners; still not on `xteink.com` | **[COMM]** + **[VENDOR]** absence |
-
-**Not present in the vendor's international catalogue.** The `xteink.com`
-`/products.json` and all 11 collections were retrieved on 2026-09-04 and contain
-**no S4 product and no S4 collection**.
-
-## Claimed specifications — all single-sourced, none verified
-
-From [r/XTEINK `1stni9p`](https://old.reddit.com/r/XTEINK/comments/1stni9p/)
-(2026-04-23, 178 pts), relaying a Chinese announcement image:
-
-| Property | Claim |
-|---|---|
-| Battery | **1400 mAh** |
-| Thickness | **6.98 mm** |
-| Mass | **95 g** |
-| OS | **Android 11** |
-| RAM | **2 GB** |
-| Storage | **32 GB** |
-| Frontlight | **cool / warm** |
-| Attachment | magnetic |
-| Touch | yes |
-
-From [r/XTEINK `1u9ctsr`](https://old.reddit.com/r/XTEINK/comments/1u9ctsr/)
-(2026-06-18), an AliExpress preorder listing: *"android 11, 2gb ram and 32gb
-storage… Price ~$99"* — **conflicts with the ¥299/¥339 Chinese pricing below.**
-
-**No SoC is named in any source.** That is the single most conspicuous gap: an
-Android 11 device with 2 GB/32 GB is almost certainly a Rockchip, Allwinner or
-UNISOC part, but **no source says which and none is asserted here.**
-
-## Pricing
-
-| Date | Price | Market | Source |
-|---|---|---|---|
-| 2026-04-23 | **¥299** (limited to existing X3/X4 owners) · **¥339** regular ≈ **US$50 / €45** | China | [r/XTEINK `1stni9p`](https://old.reddit.com/r/XTEINK/comments/1stni9p/) |
-| 2026-06-18 | **~$99** | AliExpress preorder | [r/XTEINK `1u9ctsr`](https://old.reddit.com/r/XTEINK/comments/1u9ctsr/) — poster themselves says *"don't know how legit it is"* |
-
-**Unresolved conflict.** ¥339 ≈ US$47; the AliExpress figure is roughly double.
-Either the export price carries a large markup, or the listing was not genuine.
-Neither was verified.
-
-## Timeline
-
-| Date | Event | Source |
-|---|---|---|
-| 2025-12-26 | Community digest: *"S4 updates (still in development, no date yet)"*; frontlight is *"the #1 feature request for X5/S4"* | [`1pw0r4y`](https://old.reddit.com/r/xteinkereader/comments/1pw0r4y/) |
-| 2026-04-20 | Price announcement teased for 25 Apr; YouTube shorts posted | [`1sqawqd`](https://old.reddit.com/r/xteinkereader/comments/1sqawqd/), 100 pts |
-| 2026-04-23 | **Price and preorder details drop in China.** Preorders 27 Apr, 8 pm–midnight Beijing time | [`1stni9p`](https://old.reddit.com/r/XTEINK/comments/1stni9p/), 178 pts |
-| 2026-04-23 | "XTEINK S4" discussion thread — **277 pts, 170 comments** | [`1stpb4n`](https://old.reddit.com/r/xteinkereader/comments/1stpb4n/) |
-| 2026-05-04 | **First owner sighting in the wild** — an r/EDC carry post lists *"Xteink S4 e reader (running crosspoint)"* | [`1t3o12l`](https://old.reddit.com/r/EDC/comments/1t3o12l/), 750 pts |
-| 2026-06-13 | *"XTEINK S4, Latest Video (June Production Run)"* — *"Finally a backlight."* | [`1u4ty4q`](https://old.reddit.com/r/XTEINK/comments/1u4ty4q/), 94 pts |
-| 2026-06-18 | AliExpress preorder spotted | [`1u9ctsr`](https://old.reddit.com/r/XTEINK/comments/1u9ctsr/) |
-| 2026-07-06 | Second owner sighting in an r/EDC carry post | [`1uow72f`](https://old.reddit.com/r/EDC/comments/1uow72f/), 129 pts |
-| **2026-09-03** | *"Demo Video of the S4"* — *"Video repost from XTEINK's red note account"* | [`1w6kx38`](https://old.reddit.com/r/XTEINK/comments/1w6kx38/), 41 pts |
-
-## An unresolved anomaly worth flagging
-
-The 2026-05-04 r/EDC post describes an **"Xteink S4 e reader (running
-crosspoint)"**. **CrossPoint is ESP32 firmware. It cannot run on an Android
-device.**
-
-Three possible explanations, none verified:
-1. The owner mislabelled an X3 or X4 as an "S4".
-2. "S4" is being used loosely as a family name.
-3. Something is wrong with the Android characterisation of the S4.
-
-Given the same corpus contains a post explicitly titled *"Got my white (?) X5"*
-that the author later corrected to "X4", **explanation 1 is the most likely** —
-but this is recorded rather than assumed, because if explanation 3 is true, the
-whole platform classification here is wrong.
-
-## Why the community wants it
-
-> "I'm actually interested in the S4 BECAUSE it has android, I wanna get a device
-> that can fit in my pocket and can go online. This is because I want to be able
-> to read from sites like scribblehub and ao3."
-> — [r/ereader `1tszjnb`](https://old.reddit.com/r/ereader/comments/1tszjnb/), 2026-05-31, 72 pts
-
-> "I probably will abandon both once the S4 is released."
-> — [r/xteinkereader `1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/), 412 pts
-
-The appeal is **apps and a browser** in a pocket form factor, plus a frontlight —
-which the X3 and X4 lack and which was the community's top request.
-
-## What would make this a real record
-
-| Needed | Difficulty |
-|---|---|
-| **SoC identification** | Easy for an owner — `Settings → About`, or any device-info app |
-| Build fingerprint / Android build props | Easy for an owner with ADB |
-| Panel size, resolution, controller | Easy for an owner |
-| A teardown | Moderate |
-| Whether the bootloader is unlockable | Moderate |
-| An international listing or price | Depends on the vendor |
-
-**A single owner with ADB access could convert this stub into a substantial
-record in an afternoon.** No such report exists in 1,798 posts.
-
-## Explicit gaps
-
-- **No SoC, RAM type, panel part, panel controller, or any chip whatsoever.**
-- No teardown, no photograph retained, no firmware image, no partition layout.
-- No confirmed international availability or price.
-- No FCC/CE/SRRC record.
-- **No FreeInk/CrossPoint support** and none expected — different architecture.
-- The "running crosspoint" anomaly above is unresolved.
-
-## See also
-
-[Family index](../README.md) ·
-[X4 Pro comparison](../x4-pro/comparisons-and-recommendations.md) — where the S4
-is the strongest non-programmable alternative
diff --git a/devices/xteink/s4/acquisition/README.md b/devices/xteink/s4/acquisition/README.md
deleted file mode 100644
index 7bce1f8..0000000
--- a/devices/xteink/s4/acquisition/README.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# Xteink S4 — acquisition
-
-**No artifact was acquired, and none is known to be publicly available.**
-
-## Clean-clone commands
-
-None.
-
-## Wanted artifacts
-
-| Artifact | Reacquisition | Notes |
-|---|---|---|
-| Any S4 firmware image or `getprop` dump | **`manual`** | Requires an owner with ADB. Would establish the SoC, board name and Android build — the single largest gap |
-| AliExpress / JD listing capture | **`manual`** | Would give price, dimensions, resolution and the charging connector. Chinese marketplaces were a **declared exclusion** this session |
-| Vendor announcement image (the ¥299/¥339 spec sheet) | **`manual`** | Referenced by [r/XTEINK `1stni9p`](https://old.reddit.com/r/XTEINK/comments/1stni9p/); the image itself was not retrieved |
-| "Todo lo que se sabe hasta hoy del Xteink S4" | **`manual`** | Spanish community round-up, [r/microreaders `1t6yeou`](https://old.reddit.com/r/microreaders/comments/1t6yeou/), 2026-05-08 |
-| Xiaohongshu / Douyin vendor posts | **`manual`** | **The vendor's primary channel.** Not searched |
-| YouTube `youtube.com/shorts/-5-tvnOeOk0` and the associated video | **`manual`** | Linked from [r/xteinkereader `1sqawqd`](https://old.reddit.com/r/xteinkereader/comments/1sqawqd/), 2026-04-20 |
-| Teardown | **`lost`** | None exists |
-
-## Verification
-
-`manifest.json` carries an **empty `artifacts` list and a populated `wanted`
-list**, so a verifier can distinguish "nothing fetched" from "nobody looked".
diff --git a/devices/xteink/s4/acquisition/manifest.json b/devices/xteink/s4/acquisition/manifest.json
deleted file mode 100644
index ed84a75..0000000
--- a/devices/xteink/s4/acquisition/manifest.json
+++ /dev/null
@@ -1,88 +0,0 @@
-{
-  "device": "xteink/s4",
-  "generated": "2026-09-04",
-  "note": "Android device, outside the ESP32/FreeInk ecosystem. No artifact acquired; no hardware fact established. All record content is community-relayed vendor claims.",
-  "artifacts": [],
-  "wanted": [
-    {
-      "id": "s4-getprop",
-      "kind": "device-metadata",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/s4/artifacts/",
-      "retrieved": null,
-      "license": "n/a",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Requires an owner with ADB access. `adb shell getprop` would establish SoC, board name and Android build fingerprint.",
-      "notes": "Largest single gap in this record. Two owner sightings exist (r/EDC 2026-05-04 and 2026-07-06) but neither poster provided technical detail."
-    },
-    {
-      "id": "s4-marketplace-listing",
-      "kind": "web-page",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "scratch/xteink/vendor/",
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "AliExpress/JD/Taobao were a declared search exclusion this session.",
-      "notes": "Would resolve the ~2x price conflict (RMB 299/339 vs ~$99) and give dimensions, resolution and charging connector."
-    },
-    {
-      "id": "s4-vendor-spec-image",
-      "kind": "image",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/s4/media/",
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Referenced but not linked in https://old.reddit.com/r/XTEINK/comments/1stni9p/ .",
-      "notes": "The primary source for every claimed spec: 1400 mAh, 6.98 mm, 95 g, Android 11, 2 GB, 32 GB, cool/warm frontlight."
-    },
-    {
-      "id": "s4-spanish-roundup",
-      "kind": "forum-post",
-      "canonical_url": "https://old.reddit.com/r/microreaders/comments/1t6yeou/",
-      "sha256": null,
-      "bytes": null,
-      "destination": "scratch/xteink/reddit/",
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Identified but body not retrieved this session.",
-      "notes": "'Todo lo que se sabe hasta hoy del Xteink S4', 2026-05-08. May cite Chinese primaries."
-    },
-    {
-      "id": "s4-vendor-video",
-      "kind": "video",
-      "canonical_url": "https://www.youtube.com/shorts/-5-tvnOeOk0",
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/s4/media/",
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "prohibited",
-      "disposition": "reference-only",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Linked from r/xteinkereader 1sqawqd, 2026-04-20. Reference-only: third-party video.",
-      "notes": "Vendor promotional short. May show the charging connector and panel."
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/xteink/s4/community.md b/devices/xteink/s4/community.md
deleted file mode 100644
index b91390b..0000000
--- a/devices/xteink/s4/community.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Xteink S4 — community reception
-
-From 2,136 deduplicated Reddit posts retrieved **2026-09-04**. Evidence types:
-**O** firsthand ownership · **P** demonstrable project · **I** informed
-interpretation · **Op** opinion · **H** hearsay.
-
-## The shape of the discussion
-
-The S4 generates **large threads with almost no technical content**. The two
-biggest — 277 points / **170 comments** and 178 points / 65 comments — are
-anticipation and pricing. In 2,136 posts there is **not one hands-on technical
-report, screenshot, benchmark or teardown**.
-
-| Thread | Date | Size | Content |
-|---|---|---|---|
-| ["XTEINK S4"](https://old.reddit.com/r/xteinkereader/comments/1stpb4n/) | 2026-04-23 | **277 pts, 170 c** | Anticipation |
-| ["S4 Price and Preorder Details"](https://old.reddit.com/r/XTEINK/comments/1stni9p/) | 2026-04-23 | 178 pts, 65 c | The spec claims — **I** |
-| ["Price Announcement April 25th"](https://old.reddit.com/r/xteinkereader/comments/1sqawqd/) | 2026-04-20 | 100 pts, 78 c | *"Touch screen, screen light\*, android???"* — **Op**, note the poster's own question marks |
-| ["Latest Video (June Production Run)"](https://old.reddit.com/r/XTEINK/comments/1u4ty4q/) | 2026-06-13 | 94 pts, 69 c | *"Finally a backlight."* — **Op** |
-| ["Available for pre-order on AliExpress"](https://old.reddit.com/r/XTEINK/comments/1u9ctsr/) | 2026-06-18 | 61 pts, 46 c | **H** — *"don't know how legit it is"* |
-| ["Demo Video of the S4"](https://old.reddit.com/r/XTEINK/comments/1w6kx38/) | **2026-09-03** | 41 pts, 12 c | Still promotional, the day before this snapshot |
-
-## What people actually want from it
-
-One request dominates, and it is the same one that has topped the list since 2025:
-
-> "Frontlight support (still the **#1 feature request for X5/S4**)"
-> — [r/xteinkereader `1pw0r4y`](https://old.reddit.com/r/xteinkereader/comments/1pw0r4y/), 2025-12-26 · **I**
-
-Then Android specifically, for online reading:
-
-> "I'm actually interested in the S4 **BECAUSE it has android**… I want to be able
-> to read from sites like scribblehub and ao3."
-> — [r/ereader `1tszjnb`](https://old.reddit.com/r/ereader/comments/1tszjnb/), 2026-05-31, 72 pts · **Op**
-
-## The two owner sightings
-
-Both are **carry-photo posts on r/EDC**, neither has technical content:
-
-| Date | Post | Text | Type |
-|---|---|---|---|
-| 2026-05-04 | [`1t3o12l`](https://old.reddit.com/r/EDC/comments/1t3o12l/), **750 pts** | *"Xteink S4 e reader (**running crosspoint**)"* | **O** — but see the anomaly below |
-| 2026-07-06 | [`1uow72f`](https://old.reddit.com/r/EDC/comments/1uow72f/), 129 pts | *"XTEINK S4"* | **O**, no detail |
-
-**The "running crosspoint" claim is a problem.** CrossPoint is ESP32 firmware and
-cannot run on Android. The most likely reading is model confusion — the same
-corpus contains a post titled *"Got my white (?) X5"* that its author corrected to
-*"It's X4 and not X5"*. But it is **not resolved**, and if the poster is right the
-platform classification in this record is wrong. See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-## It is already shifting purchase decisions
-
-> "I probably will abandon both once the S4 is released."
-> — [r/xteinkereader `1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/), **412 pts**, owner of both an X3 and an X4 · **O + Op**
-
-The X4 Pro's own launch poll asked *"are you going to buy the X4 Pro? Or the S4?"*
-([r/xteinkereader `1uz9mtg`](https://old.reddit.com/r/xteinkereader/comments/1uz9mtg/),
-89 comments) — the vendor's flagship and its cheap Android sibling were framed as
-**alternatives to each other** by the community on launch day.
-
-## Vendor relations, and one dissent
-
-The S4 is also where vendor-community friction surfaces most sharply:
-
-> "…the double standard for different distribution channels and the official
-> team's negative attitude toward the community makes me seriously doubt whether
-> **I'll buy the next S4**."
-> — [r/XTEINK `1vrnxnq`](https://old.reddit.com/r/XTEINK/comments/1vrnxnq/), 2026-08-18 · **O + Op**
-
-Relevant context for weighting all Xteink community evidence: one of the three
-subreddits is **vendor-operated**. Per a community moderator statement,
-*"r/xteinkreader is the main sub and **it's run by the company**; there's another
-one r/XTEINK which is opened by supporters"*
-([r/xteinkHax `1sbjsr3`](https://old.reddit.com/r/xteinkHax/comments/1sbjsr3/)) —
-and r/xteinkHax exists partly because a post was **removed from the official sub**.
-
-## What the community does not have
-
-- **No S4 technical report of any kind.**
-- No SoC identification, no screenshot, no benchmark, no teardown.
-- No confirmed international purchase.
-- No firmware project — expected, since it is not an ESP32 device, but it also
-  means the usual source of hardware truth for this family is absent.
-
-## Non-English coverage
-
-One Spanish-language round-up, *"Todo lo que se sabe hasta hoy del Xteink S4"*
-("everything known about the Xteink S4 so far"), cross-posted to r/microreaders,
-r/XTEINK and r/xteinkHax on 2026-05-08. **Not retrieved in full** — an open
-acquisition.
-
-The vendor's own primary channel is **Xiaohongshu (RedNote)**, explicitly
-identified in the 2026-09-03 demo-video post. That channel was **not searched**;
-it is where S4 evidence actually lives.
diff --git a/devices/xteink/s4/gaps-and-conflicts.md b/devices/xteink/s4/gaps-and-conflicts.md
deleted file mode 100644
index 79c88cd..0000000
--- a/devices/xteink/s4/gaps-and-conflicts.md
+++ /dev/null
@@ -1,131 +0,0 @@
-# Xteink S4 — gaps and conflicts
-
-Snapshot **2026-09-04**.
-
-## The overall state
-
-**No hardware fact about the S4 is established.** Not one chip, not the panel, not
-the panel controller, not the SoC. Everything in this record is a community-relayed
-vendor claim or an ownership sighting.
-
-The record exists because the device is real and is repeatedly used as the reason
-people do *not* buy an X4 Pro — not because anything is known about it.
-
-## Conflict 1 — the price differs by ~2×
-
-| Source | Price | Market | Date |
-|---|---|---|---|
-| S01, relaying a Chinese announcement | **¥299** (limited to X3/X4 owners) / **¥339** regular ≈ **US$45–50** | China | 2026-04-23 |
-| S02, AliExpress listing sighting | **~$99** | export | 2026-06-18 |
-
-**Unresolved.** ¥339 ≈ US$47; the AliExpress figure is roughly double. Possible
-explanations, none verified: an export markup, a bundle, a different
-configuration, or a listing that was not genuine — the poster themselves wrote
-*"don't know how legit it is"*.
-
-**What would settle it:** an actual AliExpress or JD listing capture.
-
-## Conflict 2 — "running crosspoint" on an Android device
-
-The first owner sighting (S07, r/EDC, 2026-05-04, 750 points) describes:
-
-> "Xteink S4 e reader (**running crosspoint**)"
-
-**CrossPoint is ESP32 firmware. It cannot run on an Android device.**
-
-Three explanations, in order of likelihood:
-
-1. **The owner mislabelled an X3 or X4 as an "S4".** Strongly supported by
-   precedent: the same corpus contains a post titled *"Got my white (?) X5"* whose
-   author later edited it to *"EDIT: It's X4 and not X5."* Model confusion is
-   demonstrably common in this community.
-2. "S4" was used loosely as a brand/family name.
-3. **The Android characterisation is wrong** — in which case the entire platform
-   classification in this record is wrong.
-
-**This is not resolved**, and it is flagged prominently because explanation 3
-would invalidate the record's central premise. A second, later carry post (S08,
-2026-07-06) also lists an "XTEINK S4" with no detail, so it does not help.
-
-**What would settle it:** one photograph of an S4 running anything, or one
-`Settings → About` screenshot.
-
-## Gaps — the entire hardware stack
-
-| Unknown | Note |
-|---|---|
-| **SoC** | Not named in **any** source. An Android 11 device with 2 GB/32 GB is almost certainly a Rockchip, Allwinner or UNISOC part — **not asserted**, because guessing a part number is exactly what the research method forbids |
-| **RAM/storage type** | LPDDR? eMMC? Unknown |
-| **Panel** | Size, resolution, PPI, colour depth all unknown |
-| **Panel controller** | Unknown |
-| **Touch controller** | Touch is claimed; the part is unknown |
-| **Frontlight** | Cool/warm claimed; driver unknown |
-| **Charging connector** | **Unknown** — and given the family's pogo-pin controversy, a first-order buyer question |
-| **Radios** | Wi-Fi presumably; BT, cellular unknown |
-| **Bootloader unlockability** | Unknown — the single most important question for this repository's purposes |
-
-## Gaps — everything else
-
-- **No firmware image, no build fingerprint, no partition layout.**
-- **No teardown, no internal photograph, no retained external photograph.**
-- **No confirmed international availability.** Absent from the vendor catalogue and
-  from every collection — a weaker position than even the X4 Classic, which at
-  least has an empty collection provisioned.
-- **No regulatory filing.**
-- **No FreeInk/CrossPoint support**, and none expected.
-
-## What the vendor claims, unverified
-
-From S01 (a relayed promotional image), all **single-sourced and unverified**:
-1400 mAh · 6.98 mm · 95 g · Android 11 · 2 GB RAM · 32 GB storage ·
-cool/warm frontlight · magnetic attachment · touch.
-
-For scale: 95 g and 1400 mAh against the [X3](../x3/README.md)'s 55 g / 650 mAh
-and the [X4](../x4/README.md)'s ~80 g. Internally consistent for a larger,
-lit, Android device — which is weak corroboration, not confirmation.
-
-## How to convert this stub into a real record
-
-Ranked by cost-to-value:
-
-| Action | Cost | Would establish |
-|---|---|---|
-| One owner posts `Settings → About` | minutes | **SoC, Android build, kernel** — the biggest single gap |
-| One owner runs `adb shell getprop` | minutes | Full build fingerprint, board name, panel hints |
-| Capture the AliExpress/JD listing | minutes | Price, dimensions, resolution, connector |
-| Search Xiaohongshu / Douyin (**declared exclusion here**) | moderate | The vendor's actual primary channel |
-| Retrieve S11, the Spanish community round-up | minutes | A secondary summary that may cite primaries |
-| Teardown | high | Everything |
-
-**A single owner with ADB could close most of this in an afternoon. In 2,136
-Reddit posts, nobody has.**
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 74:* - **No regulatory filing.**
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/s4/market-and-pricing.md b/devices/xteink/s4/market-and-pricing.md
deleted file mode 100644
index a97d356..0000000
--- a/devices/xteink/s4/market-and-pricing.md
+++ /dev/null
@@ -1,76 +0,0 @@
-# Xteink S4 — market and pricing
-
-**No dated observation from a primary source exists.** Everything below is
-community-relayed, and the two price points disagree by roughly 2×.
-
-## Observations
-
-| Date | Price | Market / channel | Source | Evidence type |
-|---|---|---|---|---|
-| **2026-04-23** | **¥299** — *"limited to X3/X4 users"* · **¥339** regular ≈ **US$45–50 / €45** | China, vendor-direct; preorders 27 Apr, 8 pm–midnight Beijing time | [r/XTEINK `1stni9p`](https://old.reddit.com/r/XTEINK/comments/1stni9p/), 178 pts | **relayed vendor announcement** (a promotional image read by a redditor) |
-| **2026-06-18** | **~$99** | AliExpress preorder | [r/XTEINK `1u9ctsr`](https://old.reddit.com/r/XTEINK/comments/1u9ctsr/), 61 pts | **hearsay** — poster: *"don't know how legit it is"* |
-| **2026-09-04** | **not listed** | `xteink.com` international store | Shopify `/products.json` + `/collections.json` | **primary** (an absence) |
-
-**Do not merge these into a range.** They describe different markets, one is a
-tiered launch price and one is an unverified marketplace sighting.
-
-## The loyalty-tier detail is worth noting
-
-¥299 was **restricted to existing X3/X4 owners**, with ¥339 as the general price —
-a ~12 % loyalty discount, gated by prior purchase, in a midnight-to-4-hour
-preorder window. That is a Chinese direct-to-consumer launch pattern, and it is
-consistent with everything else about this vendor: **China first, community
-channels first, international last.**
-
-## Channel
-
-| Channel | Status |
-|---|---|
-| `xteink.com` (international) | **Absent.** No product, **no collection** — a weaker position than the [X4 Classic](../x4-classic/market-and-pricing.md), which at least has an empty collection provisioned |
-| China direct | **Primary.** Preorders announced there first |
-| **Xiaohongshu (RedNote)** | **The vendor's own promotional channel** — a 2026-09-03 post is explicitly *"Video repost from XTEINK's red note account"* |
-| AliExpress | One unverified preorder sighting |
-| JD.com / Taobao | **Not searched** — declared exclusion |
-
-## Availability timeline
-
-| Date | Signal |
-|---|---|
-| 2025-12-28 | Community already asking *"Xteink S4 release date?"* |
-| 2026-04-20 | Price announcement teased |
-| 2026-04-23 | Price + preorder details drop **in China** |
-| **2026-05-04** | **First owner sighting** — an r/EDC carry post |
-| 2026-06-13 | *"June Production Run"* video |
-| 2026-06-18 | AliExpress preorder sighting |
-| 2026-07-06 | Second owner sighting |
-| 2026-07-24 | *"Android-based S4 in the works, **China-only so far**"* |
-| **2026-09-03** | Still being promoted — *"Demo Video of the S4"*, the day before this snapshot |
-
-**Shipping to real owners since ~May 2026, still not internationally listed four
-months later.**
-
-## Why it matters commercially to the rest of the family
-
-At ¥339 ≈ **US$47**, the S4 undercuts the [X4 Pro](../x4-pro/market-and-pricing.md)
-at **$99** by roughly half while claiming *more* consumer features — Android,
-apps, a browser, touch, a frontlight, a larger battery.
-
-The community says so directly:
-
-> "I probably will abandon both once the S4 is released."
-> — [r/xteinkereader `1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/), **412 pts** · firsthand owner of both an X3 and an X4
-
-> "I'm actually interested in the S4 **BECAUSE it has android**, I wanna get a
-> device that can fit in my pocket and can go online."
-> — [r/ereader `1tszjnb`](https://old.reddit.com/r/ereader/comments/1tszjnb/), 72 pts
-
-**The counter-argument, which the community does not always make:** the S4 has
-**no FreeInk SDK support, no board profile and no community firmware**. For
-anyone whose reason for buying an Xteink is that it can be reflashed, the S4 is
-not a substitute at any price — it is a different product category.
-
-## Caveats
-
-- **Two prices, ~2× apart, neither verified.** See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-- Currency conversions are approximate and undated.
-- Chinese marketplaces — where the real evidence is — were **not searched**.
diff --git a/devices/xteink/s4/sources.md b/devices/xteink/s4/sources.md
deleted file mode 100644
index 901c22e..0000000
--- a/devices/xteink/s4/sources.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# Xteink S4 — sources
-
-Retrieved **2026-09-04**. **Every row is community-relayed.** There is no vendor
-page, no specification sheet, no teardown, no firmware and no hands-on technical
-report. Read the `Class` and `Evidence type` columns before citing anything here.
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Published | Establishes | Evidence type |
-|---|---|---|---|---|---|---|---|---|---|
-| **S01** | "XTEINK S4 Price and Preorder Details" | r/XTEINK | community | forum, relaying a Chinese announcement image | <https://old.reddit.com/r/XTEINK/comments/1stni9p/> | 2026-09-04 | 2026-04-23, **178 pts**, 65 c | **1400 mAh · 6.98 mm · 95 g · Android 11 · 2 GB RAM · 32 GB storage · cool/warm frontlight · magnetic** · **¥299** (X3/X4 owners) / **¥339** regular; preorders 27 Apr, 8 pm–midnight Beijing | **relayed vendor claim** — the poster is reading a promotional image |
-| **S02** | "Xteink S4 available for pre-order on AliExpress" | r/XTEINK | community | forum, marketplace sighting | <https://old.reddit.com/r/XTEINK/comments/1u9ctsr/> | 2026-09-04 | 2026-06-18, 61 pts, 46 c | Android 11, 2 GB, 32 GB, **"Price ~$99"** | **hearsay** — the poster writes *"don't know how legit it is"* |
-| **S03** | "XTEINK S4" | r/xteinkereader | community | forum | <https://old.reddit.com/r/xteinkereader/comments/1stpb4n/> | 2026-09-04 | 2026-04-23, **277 pts, 170 c** | The largest S4 discussion found | mixed |
-| **S04** | "XTEINK S4 Price Announcement April 25th" | r/xteinkereader | community | forum + YouTube links | <https://old.reddit.com/r/xteinkereader/comments/1sqawqd/> | 2026-09-04 | 2026-04-20, 100 pts, 78 c | *"Touch screen, screen light\*, android???"*; links `youtube.com/shorts/-5-tvnOeOk0` | **relayed**; the asterisk and question marks are the poster's own uncertainty |
-| **S05** | "XTEINK S4, Latest Video (June Production Run)" | r/XTEINK | community | forum | <https://old.reddit.com/r/XTEINK/comments/1u4ty4q/> | 2026-09-04 | 2026-06-13, 94 pts, 69 c | Production run under way; *"Finally a backlight."* | **relayed vendor video** |
-| **S06** | "Demo Video of the S4" | r/XTEINK | community | forum | <https://old.reddit.com/r/XTEINK/comments/1w6kx38/> | 2026-09-04 | **2026-09-03**, 41 pts, 12 c | Still being promoted **the day before this snapshot**; *"Video repost from XTEINK's red note account"* — i.e. **Xiaohongshu is the vendor's primary channel** | **relayed** |
-| **S07** | r/EDC carry post | r/EDC | community | forum, photo carry list | <https://old.reddit.com/r/EDC/comments/1t3o12l/> | 2026-09-04 | 2026-05-04, **750 pts** | *"Xteink S4 e reader (**running crosspoint**)"* — **first owner sighting** | **firsthand ownership claim**, but see the anomaly in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-| **S08** | r/EDC carry post | r/EDC | community | forum, photo carry list | <https://old.reddit.com/r/EDC/comments/1uow72f/> | 2026-09-04 | 2026-07-06, 129 pts | *"XTEINK S4"* in a carry list | **firsthand ownership claim**, no detail |
-| **S09** | "The upcoming XTEINK S4 as a small android ereader" | r/ereader | community | forum | <https://old.reddit.com/r/ereader/comments/1tszjnb/> | 2026-09-04 | 2026-05-31, 72 pts, 66 c | Why buyers want it: apps + browser in a pocket | **opinion** |
-| **S10** | "What are your top reasons for buying a Xteink…" | r/XTEINK | community | forum | <https://old.reddit.com/r/XTEINK/comments/1v5gh6x/> | 2026-09-04 | 2026-07-24 | *"**Android-based S4 in the works, China-only so far**"*; *"Three models in a year, a fourth already brewing"* | **informed interpretation** |
-| **S11** | "Todo lo que se sabe hasta hoy del Xteink S4" | r/microreaders, r/XTEINK, r/xteinkHax | community | forum, Spanish-language summary | <https://old.reddit.com/r/microreaders/comments/1t6yeou/> | 2026-09-04 | 2026-05-08 | A community round-up ("everything known so far") | **not retrieved in full** — recorded as an open acquisition |
-| **S12** | "Xteink S4 release date?" | r/xteinkereader | community | forum | <https://old.reddit.com/r/xteinkereader/comments/1w0000/> (id `1p...`) | 2026-09-04 | 2025-12-28, 10 pts, 9 c | The S4 was already awaited in **December 2025** — a long gestation | **opinion** |
-| **S13** | Xteink Shopify catalogue | **Xteink** | **primary** | store API | <https://www.xteink.com/products.json?limit=250> and `/collections.json` | 2026-09-04 | — | **The S4 is absent from the international catalogue and has no collection** — unlike the X4 Classic, which at least has an empty collection | single-instant snapshot |
-
-## Source classes that returned nothing
-
-| Class | Result |
-|---|---|
-| Vendor product page / spec sheet / manual | **none** |
-| Teardown or internal photography | **none** |
-| Firmware image, board profile, build props | **none** |
-| Any chip identification whatsoever | **none** |
-| Regulatory filing | **none** |
-| GitHub (~200-repo census) | **no S4 project** — expected, since it is not an ESP32 device |
-
-## Not searched — declared exclusions
-
-Xiaohongshu (RedNote), which **S06 identifies as the vendor's primary channel**;
-JD.com; Taobao; AliExpress directly; Bilibili; Douyin. These are where S4 evidence
-would actually be. Their absence here is a **scope limitation, not a finding**.
diff --git a/devices/xteink/x3/README.md b/devices/xteink/x3/README.md
deleted file mode 100644
index bf76abe..0000000
--- a/devices/xteink/x3/README.md
+++ /dev/null
@@ -1,281 +0,0 @@
-# Xteink X3
-
-> SKUs `xteink-x3-white-1` (Mist Gray) and `xteink-x3-black-1` (Space Black) ·
-> **$69.00**, both in stock 2026-09-04 · published **2025-12-11**, shipping from
-> **2026-02-05** · research retrieval date **2026-09-04**.
-
-**The best-documented Xteink device**, because it is the only one with public
-teardowns — two of them, independent, one in English and one in Chinese with a
-hand-drawn schematic.
-
-## Identity and variants
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | **Xteink X3 Pocket eReader** | **[VENDOR]** handle `xteink-x3` |
-| Chinese name | **阅星瞳 X3** / **阅星曈 X3** — *both spellings in live use* | **[CN]** `sunwoods/Xteink-X3` vs `zocs/eink-quick-flasher` |
-| SKUs | `xteink-x3-white-1` (Mist Gray), `xteink-x3-black-1` (Space Black) | **[VENDOR]** |
-| Shipping weight | 58 g packaged | **[VENDOR]** `grams: 58` |
-| Device mass | **55 g** | **[VENDOR]** launch announcement |
-| FreeInk profiles | `XTEINK_X3` (UC8253) and `XTEINK_X3_UC8279` (UC8279d) | **[SDK]** `BoardConfig.h:881–947` |
-| Build flag | `-DFREEINK_DEVICE_X3=1` — links **both** drivers | **[SDK]** |
-| Lifecycle | **Current.** Both colours in stock | **[VENDOR]** |
-
-### Panel-controller variants
-
-| Controller | Batch | Note |
-|---|---|---|
-| **UC8253** | Original | The shipping default |
-| **UC8279d** ("d_B" silicon) | **From ~July 2026** | *"Newer X3 production units (Xteink heads-up, July 2026)"* — the vendor told the community |
-
-Same board, same glass, same pinout — **only the controller changes**. Selected at
-boot by fingerprint. **[SDK]** `docs/xteink-x3-uc8279-support.md:3–7`.
-
-**The UC8279d variant has never been on a bench.** The SDK is explicit:
-*"Everything below is written from the UC8279d_B 0.1 datasheet (Dec 2025) and is
-**Pending hardware validation** — no UC8279 X3 unit has been on the bench yet."*
-
-## What it is and visual identification
-
-The smallest Xteink: a **3.7-inch, 55 g** pocket reader with **six buttons** (four
-front, two side) plus power, a **glass back** with embedded magnets, and a
-**magnetic pogo-pin charging connector**. No touchscreen, no frontlight.
-
-Externally distinguishable from the X4 by size alone — the X3 is materially
-smaller and lighter (55 g vs 80 g) despite having a **higher-resolution** screen.
-
-## Product history
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2025-12-08 | Product record created | **[VENDOR]** |
-| 2025-12-09 | **Announced** — *"builds on everything we learned from building the X4"* | **[COMM]** [r/xteinkereader `1pi6ezd`](https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/) |
-| 2025-12-11 | **Pre-orders open.** *"Super Early Bird units are non-refundable"* | **[COMM]** [`1pjw3ay`](https://old.reddit.com/r/xteinkereader/comments/1pjw3ay/), **[VENDOR]** |
-| **2026-02-05** | Shipping begins | **[COMM]** both announcements |
-| 2026-03-25 | Screen protectors listed | **[VENDOR]** |
-| 2026-04-01 | Magnetic case, 6 colours | **[VENDOR]** |
-| 2026-04-28 | "X3 vs X4 - actual experience comparison", 412 pts | **[COMM]** [`1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/) |
-| 2026-05-15 / 06-19 | Pogo cable and adapter listed separately | **[VENDOR]** |
-| **2026-07-01** | **First public teardown** (13 photos) | **[TD]** [r/xteinkereader `1uksv6s`](https://old.reddit.com/r/xteinkereader/comments/1uksv6s/) |
-| ~2026-07 | Vendor warns of the **UC8279d** panel switch | **[SDK]** |
-| 2026-08-07 | CrossPoint 1.5 *"DOES support the new x3 display variants"* | **[COMM]** [`1vhvtdd`](https://old.reddit.com/r/xteinkereader/comments/1vhvtdd/) |
-| 2026-09-04 | $69, both colours in stock | **[VENDOR]** |
-
-## Key specifications
-
-| Item | Value | Component | Evidence |
-|---|---|---|---|
-| SoC | **ESP32-C3**, no PSRAM | [`espressif/esp32-c3`](../../../components/espressif/esp32-c3/README.md) | **[SDK]**, **[TD]** ×2 |
-| Flash | **Puya 128 Mbit (16 MB)** SPI NOR | [`unidentified/…/spi-nor-flash-128mbit-puya`](../../../components/unidentified/xteink-x3-x4/spi-nor-flash-128mbit-puya/README.md) | **[TD]** EN + **[CN]** |
-| Display | **792 × 528**, 3.7″, **~257 PPI** | — | **[SDK]** `:886–887`, **[VENDOR]** *"250+ PPI"* |
-| Controller | **UC8253**, or **UC8279d** on newer batches | [`ultrachip/uc8253`](../../../components/ultrachip/uc8253/README.md) · [`ultrachip/uc8279`](../../../components/ultrachip/uc8279/README.md) | **[SDK]** |
-| **Fuel gauge** | **TI BQ27220** @ I²C **0x55** | [`texas-instruments/bq27220`](../../../components/texas-instruments/bq27220/README.md) | **[SDK]**, **[CN]** BOM |
-| **RTC** | **DS-series** @ I²C **0x68** — **see conflict** | [`unidentified/…/rtc-ds-series`](../../../components/unidentified/xteink-x3-x4/rtc-ds-series/README.md) | **[SDK]** DS3231 vs **[TD]** "DS1307" |
-| **IMU** | **QMI8658** 6-axis @ I²C **0x6B** (alt 0x6A), `WHO_AM_I = 0x05` | [`qst/qmi8658a`](../../../components/qst/qmi8658a/README.md) | **[SDK]**, **[CN]** BOM |
-| **NFC** | **ISO/IEC 14443A tag** | [`unidentified/…/nfc-tag-iso14443a`](../../../components/unidentified/xteink-x3-x4/nfc-tag-iso14443a/README.md) | **[CN]** BOM + **[VENDOR]** announcement |
-| Charger | **TP4056-class** battery-management IC | [`unidentified/…/battery-charger-tp4056-class`](../../../components/unidentified/xteink-x3-x4/battery-charger-tp4056-class/README.md) | **[CN]** BOM |
-| **Battery** | **650 mAh**, glued to the back cover | [`generic/lipo-102035`](../../../components/generic/) (class only) | **[TD]** photo caption |
-| Storage | microSD over **SPI shared with the display**; **power enable GPIO13** | — | **[SDK]** |
-| Charging | **Magnetic pogo pins**, magnets glued to the back cover | — | **[TD]**, **[VENDOR]** |
-| Touch / frontlight | **none** | — | **[SDK]** |
-| Radios | Wi-Fi + BLE (ESP32-C3) | — | inferred |
-
-**The X3 has more silicon than the X4 and the X4 Pro in three respects**: it is the
-only Xteink with **NFC**, one of two with an **IMU**, and the only one with a
-**BQ27220** (a proper TI impedance-track gauge rather than the Pro's CW2017 or the
-X4's bare ADC).
-
-### Resolution sanity check
-
-√(792² + 528²) = 951.7 px diagonal ÷ 3.7″ = **257 PPI**, which agrees with the
-vendor's *"over 250 PPI"* and is the **highest pixel density in the family**
-(the 4.26″ models are ~219). Two independent figures, arithmetically consistent.
-
-## Architecture and components
-
-```
-ESP32-C3 ── SPI ──┬── UC8253 │ UC8279d ── 792×528 glass
-                  │     SCLK 8 / MOSI 10 / CS 21 / DC 4 / RST 5 / BUSY 6
-                  └── microSD  (same bus; MISO 7, CS 12, rail = GPIO13 active-HIGH)
-         ── I²C SDA 20 / SCL 0 @400 kHz ─┬── BQ27220 fuel gauge   0x55
-                                         ├── DS-series RTC        0x68
-                                         └── QMI8658 IMU          0x6B
-         ├─ ADC ladder ── GPIO1 (Back/Confirm/Left/Right) + GPIO2 (Up/Down)
-         ├─ GPIO3 ─────── Power button
-         ├─ GPIO0 ─────── Battery voltage ADC (÷2)
-         └─ NFC tag ───── passive, ISO 14443A, not on any host bus
-```
-
-**The I²C bus is the X3/X4 discriminator.** `XteinkDetect` probes SDA20/SCL0 for
-0x55, 0x68 and 0x6B; finding them means X3, finding nothing means X4. One C3
-binary drives both devices.
-
-Full tables: [`pinouts-and-buses.md`](pinouts-and-buses.md).
-
-## Distinctive strengths
-
-- **Highest PPI in the family** (~257) and **lightest** (55 g).
-- **The most complete sensor set**: real fuel gauge, RTC, IMU, NFC.
-- **Motion-based page turning** via the gyroscope — a genuine feature the others
-  lack.
-- **SD card can be powered down for sleep** (GPIO13), unlike the X4.
-- **Two independent public teardowns**, including a schematic sketch.
-- **Cheapest currently-purchasable Xteink** at $69.
-
-## Shortcomings and constraints
-
-- **Pogo-pin charging**, like the X4 Pro. No USB-C charge path.
-- **Glass back that cracks.** An owner reported *"My glass cracked a bit on the
-  rear side"* and asked which models have metal backing — **unanswered**
-  ([r/xteinkereader `1w56phf`](https://old.reddit.com/r/xteinkereader/comments/1w56phf/), 2026-09-02).
-- **Buttons feel worse than the X4's**: *"The X3's buttons are somewhat mushy and
-  quieter"* — [r/xteinkereader `1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/).
-- **No PSRAM**, and the X3 is the device where **OTA out-of-memory was actually
-  observed** — CrossPoint stopped using GitHub releases because of it.
-- **The UC8279d variant is unvalidated on hardware** and currently has no
-  grayscale and probably a full flash on every page turn. See
-  [`features/display.md`](features/display.md).
-- **Vendor marketing for this device is false** — see below.
-
-### The vendor's own product page is wrong about this device
-
-The `xteink.com` X3 listing advertises:
-
-> "This tool includes **adjustable warm light settings**. You can transition to
-> bedtime stories with total visual comfort…"
-> "**Cloud sync** keeps your notes organized across all of your many mobile
-> devices."
-
-**The X3 has no frontlight** (`NO_FRONTLIGHT` in the board profile; no frontlight
-in either teardown; the X4 Pro is the only Xteink with one). The copy is
-AI/SEO-generated boilerplate. **No claim from vendor prose is used as evidence
-anywhere in this tree** — this is why.
-
-## Performance summary
-
-| Figure | Value | Status |
-|---|---|---|
-| Display SPI | **20 MHz** = UC8253 datasheet max (`TSCYCW`) | **[SDK]**, in-spec |
-| Prior fork (Witch Reader) | 16 MHz | ~25 % slower on plane writes |
-| Battery | **650 mAh** | **[TD]** |
-| Runtime | **unknown** | — |
-
-No power measurement exists. The teardown author explicitly set out to attach a
-**Nordic Power Profiler Kit II** *"to see if I can make any power optimizations to
-crosspoint firmware"* — **and never posted results.**
-
-## Pricing and availability
-
-**$69.00**, both colours, in stock 2026-09-04. Full accessory pricing and the $16
-used-market anecdote: [`market-and-pricing.md`](market-and-pricing.md).
-
-## Competitors, equivalents and clones
-
-See [`../x4-pro/comparisons-and-recommendations.md`](../x4-pro/comparisons-and-recommendations.md)
-for the family and platform comparison. Within the family the X3 is the value
-pick: it costs the same as the (delisted) X4, has a sharper screen and far more
-sensors, and gives up USB-C and button feel.
-
-## When to use / when not to use
-
-**Use it** for the sharpest, lightest pocket reader in the family, or if you want
-the IMU/NFC/RTC/gauge for a project. **Do not use it** if you need USB-C charging,
-if you want the best button feel, or if your firmware is memory-hungry.
-
-## Images and teardown/PCB views
-
-**Two independent teardowns, both archived.** See [`media.md`](media.md).
-
-## Common tasks / How do I…?
-
-| Task | Guide |
-|---|---|
-| Drive the display; handle UC8253 vs UC8279d | [`features/display.md`](features/display.md) |
-| Read the 6-button ADC ladder | [`../x4/features/buttons.md`](../x4/features/buttons.md) (identical) |
-| Read the fuel gauge | [`features/battery-and-power.md`](features/battery-and-power.md) |
-| Read the IMU / motion page turn | [`features/imu.md`](features/imu.md) |
-| Read the RTC | [`features/rtc.md`](features/rtc.md) |
-| Use the SD card and power it down for sleep | [`features/storage.md`](features/storage.md) |
-| Do anything with the NFC tag | [`features/nfc.md`](features/nfc.md) |
-| Build and flash | [`development.md`](development.md) |
-| Dump / restore stock firmware | [`factory-firmware.md`](factory-firmware.md) |
-
-## Documentation map
-
-[`pinouts-and-buses.md`](pinouts-and-buses.md) ·
-[`development.md`](development.md) ·
-[`factory-firmware.md`](factory-firmware.md) ·
-[`sources.md`](sources.md) ·
-[`coverage.md`](coverage.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md) ·
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) ·
-[`market-and-pricing.md`](market-and-pricing.md) ·
-[`media.md`](media.md).
-Family-wide [research log](../x4-pro/research-log.md) and
-[command ledger](../x4-pro/commands.md).
-
-## Artifact layout
-
-```
-artifacts/teardown/
-├── imgur-2026-07-01/   → archived — 13 photos, English captions, manifest.json
-└── sunwoods-cn/        → archived — 10 photos incl. a hand-drawn SCHEMATIC + upstream README
-```
-
-Both carry `*.ARCHIVED.md` placeholders with per-file SHA-256, sizes and
-reacquisition instructions.
-
-## Known conflicts and unresolved identities
-
-**The RTC.** The FreeInk SDK drives a **DS3231**; the English teardown captions the
-chip **"DS1307"**; the Chinese BOM says only **"DS-series RTC"**. All three are at
-address 0x68. Unresolved — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-The component record is filed under `unidentified/` for exactly this reason.
-
----
-
-## Round 2 — appended 2026-09-11: the X3 has an FCC teardown, and it is public
-
-**No line above was altered.**
-
-| Field | Value |
-|---|---|
-| **FCC ID** | **`2BTR9-XTEINKX3`** |
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, Longhua District, Shenzhen, FRN `0037772233` |
-| Granted | **2025-12-26** — sixteen days before the store listing of 2025-12-11… *no*: the store listing **preceded** the grant. Recorded as-is; both dates come from their own primary sources |
-| Equipment class | DTS, **2412–2462 MHz** |
-| Source | <https://fccid.io/2BTR9-XTEINKX3> |
-
-### The important part: the confidentiality has already expired
-
-| Exhibit | Public from |
-|---|---|
-| **Internal Photos (849.3 KB)** | **2026-06-24 — already public** |
-| **Users Manual (1.3 MB)** | **2026-06-24 — already public** |
-| External Photos, Label, Test Setup Photos, 3 test reports, RF exposure | 2025-12-26 |
-| Block Diagram · Schematics · Operational Description | **permanently confidential** |
-
-**This is a third teardown of the X3**, alongside the two community teardowns
-already archived in this record — and it is the only one produced under a
-regulatory obligation to photograph the board as shipped.
-
-Retained: `artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf`,
-869,708 B, SHA-256
-`b3affd56115e9c3e49428f9727ba194c0eec6705ddd0b039fd9b4ce28b430a45`,
-**16 embedded images**, from
-<https://fccid.io/2BTR9-XTEINKX3/Internal-Photos/Internal-Photos-8932226.pdf>,
-retrieved 2026-09-11 (UA `WhatsApp/2.23.20.0`; a desktop-Chrome UA is served
-403). Validated `%PDF`.
-
-**It has not been read in detail by this pass.** It is retained, hashed and
-cited so the next session can open it against
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) — in particular against
-**conflict #1, the unresolved RTC part** (`DS3231` per firmware vs `DS1307` per a
-teardown caption vs "DS-series" per a Chinese BOM). **A regulatory photograph of
-the RTC's top marking would settle a conflict that has stood since the first
-sweep**, and it is sitting in this repository unread.
-
-`Users Manual` at <https://fccid.io/2BTR9-XTEINKX3/User-Manual/Users-Manual-8932229.pdf>
-is also public and **was not fetched** — it is the vendor's own manual, which
-would be a far better source than the SEO-generated store prose this record
-correctly distrusts.
diff --git a/devices/xteink/x3/acquisition/README.md b/devices/xteink/x3/acquisition/README.md
deleted file mode 100644
index 3de162a..0000000
--- a/devices/xteink/x3/acquisition/README.md
+++ /dev/null
@@ -1,76 +0,0 @@
-# Xteink X3 — acquisition
-
-## Clean-clone commands, in execution order
-
-Both tracked artifact sets are **archived**, so a clean clone sees placeholders
-plus symlinks. To reacquire:
-
-```bash
-# 1. English teardown, 13 images. The album page is a JS shell — enumerate first.
-mkdir -p devices/xteink/x3/artifacts/teardown/imgur-2026-07-01
-curl -fsSL "https://imgur.com/ajaxalbums/getimages/OA6CS2C/hit.json" -o /tmp/album.json
-python3 - <<'PY'
-import json, subprocess
-for i, im in enumerate(json.load(open('/tmp/album.json'))['data']['images'], 1):
-    url = f"https://i.imgur.com/{im['hash']}{im['ext']}"
-    out = f"devices/xteink/x3/artifacts/teardown/imgur-2026-07-01/{i:02d}-{im['hash']}{im['ext']}"
-    subprocess.run(['curl','-fsSL','-m','60',url,'-o',out], check=True)
-PY
-
-# 2. Chinese teardown + schematic sketch, 10 images + README.
-mkdir -p devices/xteink/x3/artifacts/teardown/sunwoods-cn
-for i in 01 02 03 04 05 06 07 08 09 10; do
-  curl -fsSL "https://raw.githubusercontent.com/sunwoods/Xteink-X3/main/readme-img/$i.jpg" \
-       -o "devices/xteink/x3/artifacts/teardown/sunwoods-cn/$i.jpg"
-done
-curl -fsSL "https://raw.githubusercontent.com/sunwoods/Xteink-X3/main/README.md" \
-     -o devices/xteink/x3/artifacts/teardown/sunwoods-cn/README.upstream.md
-```
-
-**Expected failure mode for #1:** scraping `https://imgur.com/a/xteink-x3-teardown-OA6CS2C`
-directly returns **2 of 13** images. The `ajaxalbums` endpoint is undocumented and
-could disappear; if it does, the per-image SHA-256 list in the
-[placeholder](../artifacts/teardown/imgur-2026-07-01.ARCHIVED.md) still identifies
-every file, and the Reddit post remains as a pointer.
-
-## Verify
-
-Per-file SHA-256, byte size and captions are recorded in both placeholders and in
-`manifest.json` inside the archived Imgur directory.
-
-```bash
-python3 tools/archive_artifact.py --repo-root . --manifest <manifest> --verify
-python3 tools/audit_archive.py
-```
-
-## Licensing and disposition
-
-| Artifact set | Licence | Redistribution | Disposition |
-|---|---|---|---|
-| Imgur teardown, 13 images, 18.61 MiB | **unknown** — a Reddit/Imgur user post, no terms stated | **unknown** | archived, **unstaged pending user review** |
-| `sunwoods` teardown + schematic, 10 images, 4.80 MiB | **none declared** — no LICENSE in the repository | **unknown** | archived, **unstaged pending user review** |
-
-Neither uploader stated terms. Both are firsthand photographs of a consumer device
-by their authors.
-
-## Not downloaded, and why
-
-| Artifact | Status | Reacquisition |
-|---|---|---|
-| `x3_en_v1.0.7_full.bin`, `x3_en_v5.2.13_full.bin`, `x3_cn_v5.2.13_full.bin`, `x3_cn_v5.2.13_ota.bin` | **Git LFS pointers** (~130 B each) in [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher/tree/main/firmware) | **`manual`** — needs `git lfs` or the LFS batch API. **The cheapest way to obtain the first X3 firmware image.** Licence: none declared; vendor firmware; redistribution **unknown** |
-| `X3-FLASHER-GUIDE.md` / `-EN.md` | Present in the same repo, not fetched | **`automatic`** — plain raw fetch. The most detailed X3 flashing documentation that exists |
-| An X3 flash dump | **Never obtained** | **`manual`** — dump a USB-unlocked unit |
-| Vendor product imagery | Listing is **live**; URLs are in `scratch/xteink/vendor/products-p1.json` under `products[].images[].src` | **`automatic`** — **capture before the X3 is delisted**, as happened to the X4 |
-| Vendor OTA feed | `http://gotaserver.xteink.com/api/check-update` | **`manual`** — request format unknown |
-
-## The most valuable work needs no network at all
-
-Three open questions could be closed by **reading images already archived here**:
-
-1. `sunwoods-cn/02.jpg` — the schematic sketch — would likely resolve the
-   **GPIO0 / GPIO20 dual-assignment**.
-2. `imgur-2026-07-01/13-Ay3rpJg.jpg` (5760×3240) would test the **"DS1307"**
-   caption against the actual marking.
-3. `imgur-2026-07-01/10-YgdHbR1.jpg` and `11-bgXQoVr.jpg` — captioned *"at an
-   angle to better read the chip labels"* — would likely give the **Puya flash
-   part number**.
diff --git a/devices/xteink/x3/acquisition/manifest.json b/devices/xteink/x3/acquisition/manifest.json
deleted file mode 100644
index 53be036..0000000
--- a/devices/xteink/x3/acquisition/manifest.json
+++ /dev/null
@@ -1,473 +0,0 @@
-{
-  "device": "xteink/x3",
-  "generated": "2026-09-04",
-  "artifacts": [
-   {
-     "id": "fcc-2BTR9-XTEINKX3-8932220",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX3/Test-Report/ANT-Test-Report-8932220.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932220",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932220.pdf",
-      "https://fccid.io/2BTR9-XTEINKX3",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/Test-Report/ANT-Test-Report-8932220.pdf"
-     ],
-     "sha256": "9608834e81bf0f0baf019a5c4c0391fb33c95b56833fe3e0ee5218151327210f",
-     "bytes": 1001831,
-     "destination": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-12-26",
-     "fcc_id": "2BTR9-XTEINKX3",
-     "fcc_document_id": "8932220",
-     "exhibit_type": "Test Report",
-     "exhibit_title_as_filed": "ANT Test Report",
-     "grant_date": "2025-12-26",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf",
-     "placeholder": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX3-8932225",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX3/External-Photos/External-Photos-8932225.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932225",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932225.pdf",
-      "https://fccid.io/2BTR9-XTEINKX3",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/External-Photos/External-Photos-8932225.pdf"
-     ],
-     "sha256": "eee16223c0806e6a529a9abe53421612103c4a4cc491f8ee442dfbf4a5aae3ce",
-     "bytes": 512425,
-     "destination": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-12-26",
-     "fcc_id": "2BTR9-XTEINKX3",
-     "fcc_document_id": "8932225",
-     "exhibit_type": "External Photos",
-     "exhibit_title_as_filed": "External Photos",
-     "grant_date": "2025-12-26",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf",
-     "placeholder": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX3-8932228",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX3/Label/ID-Label-Location-Info-8932228.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932228",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932228.pdf",
-      "https://fccid.io/2BTR9-XTEINKX3",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/Label/ID-Label-Location-Info-8932228.pdf"
-     ],
-     "sha256": "ce6218cf3519448b227e6c7a5a4a6a150362cf5eaa165fda3798ece3481c8204",
-     "bytes": 367446,
-     "destination": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-id-label-location-info.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-12-26",
-     "fcc_id": "2BTR9-XTEINKX3",
-     "fcc_document_id": "8932228",
-     "exhibit_type": "ID Label/Location Info",
-     "exhibit_title_as_filed": "ID Label/Location Info",
-     "grant_date": "2025-12-26",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/xteink/x3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX3-8932226",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX3/Internal-Photos/Internal-Photos-8932226.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932226",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932226.pdf",
-      "https://fccid.io/2BTR9-XTEINKX3",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/Internal-Photos/Internal-Photos-8932226.pdf"
-     ],
-     "sha256": "b3affd56115e9c3e49428f9727ba194c0eec6705ddd0b039fd9b4ce28b430a45",
-     "bytes": 869708,
-     "destination": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-06-24",
-     "fcc_id": "2BTR9-XTEINKX3",
-     "fcc_document_id": "8932226",
-     "exhibit_type": "Internal Photos",
-     "exhibit_title_as_filed": "Internal Photos",
-     "grant_date": "2025-12-26",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/xteink/x3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX3-8932224",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX3/RF-Exposure-Info/RF-Exposure-Info-8932224.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932224",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932224.pdf",
-      "https://fccid.io/2BTR9-XTEINKX3",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/RF-Exposure-Info/RF-Exposure-Info-8932224.pdf"
-     ],
-     "sha256": "78c21f6f8ab043cb08b9c4848c3509bedd7f673dd2ca6c10ce2804c1bc121fed",
-     "bytes": 119149,
-     "destination": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2025-12-26",
-     "fcc_id": "2BTR9-XTEINKX3",
-     "fcc_document_id": "8932224",
-     "exhibit_type": "RF Exposure Info",
-     "exhibit_title_as_filed": "RF Exposure Info",
-     "grant_date": "2025-12-26",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf",
-     "placeholder": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX3-8932229",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX3/User-Manual/Users-Manual-8932229.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932229",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932229.pdf",
-      "https://fccid.io/2BTR9-XTEINKX3",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/User-Manual/Users-Manual-8932229.pdf"
-     ],
-     "sha256": "f3cc9a89924739bc7ab80bdeea2dc52970c327fde0f33e4ff8b2bd739eaf7fa1",
-     "bytes": 1373110,
-     "destination": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-06-24",
-     "fcc_id": "2BTR9-XTEINKX3",
-     "fcc_document_id": "8932229",
-     "exhibit_type": "Users Manual",
-     "exhibit_title_as_filed": "Users Manual",
-     "grant_date": "2025-12-26",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf",
-     "placeholder": "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x3",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-      "id": "x3-teardown-imgur",
-      "kind": "teardown-photography",
-      "canonical_url": "https://imgur.com/a/xteink-x3-teardown-OA6CS2C",
-      "fallback_urls": [
-        "https://imgur.com/ajaxalbums/getimages/OA6CS2C/hit.json",
-        "https://old.reddit.com/r/xteinkereader/comments/1uksv6s/xteink_x3_teardown/"
-      ],
-      "bytes": 19513196,
-      "sha256": null,
-      "file_count": 14,
-      "destination": "devices/xteink/x3/artifacts/teardown/imgur-2026-07-01/",
-      "retrieved": "2026-09-04",
-      "upstream_date": "2026-07-01T17:44:53",
-      "license": "unknown - Reddit/Imgur user post, no terms stated",
-      "license_evidence": "none found",
-      "redistribution_status": "unknown",
-      "disposition": "local-cache",
-      "repo_state": "untracked-symlink-with-placeholder",
-      "archived_to": "archive/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01",
-      "placeholder": "devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.md",
-      "reacquisition": "automatic",
-      "extraction": "none - individual JPEGs plus manifest.json carrying per-image captions",
-      "acquisition_note": "The album HTML is a JS shell yielding only 2 of 13 images. Use the ajaxalbums endpoint to enumerate hashes, then fetch https://i.imgur.com/<hash>.jpg .",
-      "establishes": [
-        "650 mAh battery, glued, connectorised",
-        "pogo magnets glued to the back cover",
-        "ESP32-C3 main CPU",
-        "128 Mbit (16 MB) external flash",
-        "a chip captioned 'DS1307 RTC' - CONFLICTS with the SDK's DS3231",
-        "glass back, removable with heat gun + suction cup",
-        "PCB silkscreen keep-outs where the back-cover magnets sit"
-      ],
-      "members": [
-        {
-          "name": "01-u60Rtxi.jpg",
-          "bytes": 1157440,
-          "sha256": "0cbdb9fa877731b61a114b133a024c7c433264ef1eebea441c9fce5efa5bf4b9"
-        },
-        {
-          "name": "02-tdku70e.jpg",
-          "bytes": 1136501,
-          "sha256": "5eb74bd33e03f742449da5b41359b6b4951126c8526ab02878d5ccf9d74a75b5"
-        },
-        {
-          "name": "03-Q5jsUoi.jpg",
-          "bytes": 1908658,
-          "sha256": "6e076711cabf6d37231cc7dc28e7c8001b1aec5b5108d138cb708e2bd70c6caf"
-        },
-        {
-          "name": "04-WAlvma8.jpg",
-          "bytes": 1615687,
-          "sha256": "af78bf675054744550811f88eeda252acc3e8b64d0fc4d2fce3d3384fb059680"
-        },
-        {
-          "name": "05-lBJtD4I.jpg",
-          "bytes": 740345,
-          "sha256": "97cbad3d4787586d0c7f0698945a99c5af46915b3de0619e3358fac01315c665"
-        },
-        {
-          "name": "06-pcqe4Q0.jpg",
-          "bytes": 1061091,
-          "sha256": "7f8299b06fd938e47c22e1555af0ae340cf557e3093e1b001b563c41321d0c2c"
-        },
-        {
-          "name": "07-QQz92jU.jpg",
-          "bytes": 1175909,
-          "sha256": "0cdc4eefc11f1dd44077b35186971418892c8c7fac5ad1ec3b8149eb758e408f"
-        },
-        {
-          "name": "08-ZkQliFL.jpg",
-          "bytes": 2021156,
-          "sha256": "d1662b9d3effbecbe9ac23ccfd4dd991a046bf4869a32680319f936557392a11"
-        },
-        {
-          "name": "09-Q0UGXpo.jpg",
-          "bytes": 688065,
-          "sha256": "ba1106d72f7b58e27a15cee3cac0dad6a94233902d0207e3cc9be8c2a215f902"
-        },
-        {
-          "name": "10-YgdHbR1.jpg",
-          "bytes": 1935873,
-          "sha256": "2fb568c906bbdf4e3331981e5d1d5fe0b8835c88ac319ed518d081d0de8f02aa"
-        },
-        {
-          "name": "11-bgXQoVr.jpg",
-          "bytes": 2028489,
-          "sha256": "bf11e447d41a133801421793b0c68b2a27cbae10368c30fa50e0556d0974ffa6"
-        },
-        {
-          "name": "12-wKlM8uS.jpg",
-          "bytes": 2003480,
-          "sha256": "4fbe14446f9754b800978abf2039d5691a3ba191219de78c354a413f7a7d2378"
-        },
-        {
-          "name": "13-Ay3rpJg.jpg",
-          "bytes": 2037024,
-          "sha256": "a005cdf12c7907907b4e7a93c09e3161290cf69dd0882bf5a63e46c448a1f39d"
-        },
-        {
-          "name": "manifest.json",
-          "bytes": 3478,
-          "sha256": "e6d63042f523e91759fbf46481fe1ea4e832820b91e0d3ed7e9af73bfb4e1a67"
-        }
-      ]
-    },
-    {
-      "id": "x3-teardown-sunwoods-cn",
-      "kind": "teardown-photography-and-schematic",
-      "canonical_url": "https://github.com/sunwoods/Xteink-X3/tree/main/readme-img",
-      "fallback_urls": [
-        "https://raw.githubusercontent.com/sunwoods/Xteink-X3/main/readme-img/02.jpg",
-        "https://github.com/sunwoods/Xteink-X3"
-      ],
-      "bytes": 5034272,
-      "sha256": null,
-      "file_count": 11,
-      "destination": "devices/xteink/x3/artifacts/teardown/sunwoods-cn/",
-      "retrieved": "2026-09-04",
-      "upstream_repo": "sunwoods/Xteink-X3",
-      "path_in_repo": "readme-img/",
-      "license": "none declared - no LICENSE file in the repository",
-      "license_evidence": "repository tree checked 2026-09-04",
-      "redistribution_status": "unknown",
-      "disposition": "local-cache",
-      "repo_state": "untracked-symlink-with-placeholder",
-      "archived_to": "archive/devices/xteink/x3/artifacts/teardown/sunwoods-cn",
-      "placeholder": "devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.md",
-      "reacquisition": "automatic",
-      "establishes": [
-        "hand-drawn SCHEMATIC SKETCH (02.jpg) - the only schematic-like document for any Xteink device",
-        "BOM: ESP32-C3, PUYA 128 Mbit flash, QMI8658, DS-series RTC, TP4056-class charger, TI BQ27220",
-        "an ISO/IEC 14443A NFC tag - present in no firmware and no English source",
-        "pins measured with a multimeter and cross-checked against CrossPoint source"
-      ],
-      "caveats": [
-        "Schematic uses substitute footprints for some parts (upstream: \u90e8\u5206\u5668\u4ef6\u7528\u5176\u4ed6\u7c7b\u4f3c\u5c01\u88c5\u66ff\u4ee3) - functional sketch, NOT fabrication-accurate",
-        "Some part numbers were borrowed from the CrossPoint project rather than read from markings"
-      ],
-      "members": [
-        {
-          "name": "01.jpg",
-          "bytes": 413548,
-          "sha256": "a6d982ea2571381fb431e90063bdbfb0224b7f9482aa2ccbcd5f8dc86c189997"
-        },
-        {
-          "name": "02.jpg",
-          "bytes": 1265063,
-          "sha256": "09d65eb222c11a5be601d48ca35ea580dbe7e4cce5a751f5f2c376244d92e8e2"
-        },
-        {
-          "name": "03.jpg",
-          "bytes": 508365,
-          "sha256": "efa40a9bcc5a1c40f40a5375d25a110a3868cc64ea4ce3b8e0ad390087a1e3ca"
-        },
-        {
-          "name": "04.jpg",
-          "bytes": 458675,
-          "sha256": "b36a6b60eea4de0f6ed08b0aaad28af77688b2d6d4166ee94711a85180e6df40"
-        },
-        {
-          "name": "05.jpg",
-          "bytes": 787871,
-          "sha256": "82fae7b72354604613028f39f6090d60794e89b345002123e44f3c4e58b41897"
-        },
-        {
-          "name": "06.jpg",
-          "bytes": 755206,
-          "sha256": "56b38759f56431dd3b120466f9163c99b160c3ccc70b494e7dd6bfd1d9567538"
-        },
-        {
-          "name": "07.jpg",
-          "bytes": 239875,
-          "sha256": "ecbd42a7c6660fc2fbdac8dfd831a69646b3e0ec232a6cb3af9f78e88d601258"
-        },
-        {
-          "name": "08.jpg",
-          "bytes": 221681,
-          "sha256": "5f1dc8708057411850d94dcb5d1eb059fdd2d509ee3aea1f10a51e09b2bb330b"
-        },
-        {
-          "name": "09.jpg",
-          "bytes": 235823,
-          "sha256": "3aa7a9c7370cfdc08e21d89383ae24286fc53a1bc53ad983cd8871823d867b20"
-        },
-        {
-          "name": "10.jpg",
-          "bytes": 146545,
-          "sha256": "4849f58f3a2e96c72acd08e635ab01f8b7dc07a303f62b12e5e70a9d9fb4be4a"
-        },
-        {
-          "name": "README.upstream.md",
-          "bytes": 1620,
-          "sha256": "ded2c73ec87ecf306b745d33df70892d6d897e397df09f762adeafb61403f1dd"
-        }
-      ]
-    }
-  ],
-  "wanted": [
-    {
-      "id": "x3-stock-images",
-      "kind": "firmware-image",
-      "canonical_url": "https://github.com/zocs/eink-quick-flasher/tree/main/firmware",
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x3/artifacts/firmware/",
-      "retrieved": null,
-      "upstream_version": "V1.0.7 and V5.2.13 (CN + EN, full and OTA)",
-      "license": "none declared",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Git LFS pointers (~130 bytes each in the tree). Needs git-lfs or the LFS batch API.",
-      "notes": "The X3 is the ONLY Xteink with published FULL-FLASH stock images. Upstream states CN/EN differ only by default UI language."
-    },
-    {
-      "id": "x3-flasher-guide",
-      "kind": "documentation",
-      "canonical_url": "https://raw.githubusercontent.com/zocs/eink-quick-flasher/main/X3-FLASHER-GUIDE-EN.md",
-      "fallback_urls": [
-        "https://raw.githubusercontent.com/zocs/eink-quick-flasher/main/X3-FLASHER-GUIDE.md"
-      ],
-      "sha256": null,
-      "bytes": 13615,
-      "destination": "devices/xteink/x3/artifacts/",
-      "retrieved": null,
-      "license": "MIT (repository)",
-      "redistribution_status": "allowed",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "reason": "Identified but not fetched this session.",
-      "notes": "The most detailed X3 flashing documentation in existence; EN 13,615 B and CN 16,732 B."
-    },
-    {
-      "id": "x3-vendor-imagery",
-      "kind": "image",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x3/media/",
-      "retrieved": null,
-      "license": "vendor, all rights reserved (presumed)",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "reason": "URLs are in scratch/xteink/vendor/products-p1.json under products[].images[].src .",
-      "notes": "CAPTURE BEFORE DELISTING. The X4's vendor imagery was lost when that product was delisted before this research began."
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md b/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md
deleted file mode 100644
index ac85be2..0000000
--- a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX3-ant-test-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,001,831 B (0.96 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,001,831 B (0.96 MiB) |
-| SHA-256 | `9608834e81bf0f0baf019a5c4c0391fb33c95b56833fe3e0ee5218151327210f` |
-| FCC ID | **`2BTR9-XTEINKX3`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | ANT Test Report |
-| FCC document id | 8932220 |
-| Upstream publication date | 2025-12-26 |
-| Grant date | 2025-12-26 |
-| Equipment class | XTEINK X3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX3/Test-Report/ANT-Test-Report-8932220.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932220>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932220.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/Test-Report/ANT-Test-Report-8932220.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf" \
-   "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX3/Test-Report/ANT-Test-Report-8932220.pdf" -o "2BTR9-XTEINKX3-ant-test-report.pdf"
-echo "9608834e81bf0f0baf019a5c4c0391fb33c95b56833fe3e0ee5218151327210f  2BTR9-XTEINKX3-ant-test-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md b/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index ff33144..0000000
--- a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX3-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 512,425 B (0.49 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 512,425 B (0.49 MiB) |
-| SHA-256 | `eee16223c0806e6a529a9abe53421612103c4a4cc491f8ee442dfbf4a5aae3ce` |
-| FCC ID | **`2BTR9-XTEINKX3`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 8932225 |
-| Upstream publication date | 2025-12-26 |
-| Grant date | 2025-12-26 |
-| Equipment class | XTEINK X3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX3/External-Photos/External-Photos-8932225.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932225>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932225.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/External-Photos/External-Photos-8932225.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf" \
-   "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX3/External-Photos/External-Photos-8932225.pdf" -o "2BTR9-XTEINKX3-external-photos.pdf"
-echo "eee16223c0806e6a529a9abe53421612103c4a4cc491f8ee442dfbf4a5aae3ce  2BTR9-XTEINKX3-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-id-label-location-info.pdf b/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-id-label-location-info.pdf
deleted file mode 100644
index 7aa8dd4..0000000
Binary files a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-id-label-location-info.pdf and /dev/null differ
diff --git a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf b/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf
deleted file mode 100644
index 946d019..0000000
Binary files a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf and /dev/null differ
diff --git a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md b/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md
deleted file mode 100644
index ed1fadb..0000000
--- a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX3-rf-exposure-info.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 119,149 B (0.11 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 119,149 B (0.11 MiB) |
-| SHA-256 | `78c21f6f8ab043cb08b9c4848c3509bedd7f673dd2ca6c10ce2804c1bc121fed` |
-| FCC ID | **`2BTR9-XTEINKX3`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Info |
-| FCC document id | 8932224 |
-| Upstream publication date | 2025-12-26 |
-| Grant date | 2025-12-26 |
-| Equipment class | XTEINK X3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX3/RF-Exposure-Info/RF-Exposure-Info-8932224.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932224>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932224.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/RF-Exposure-Info/RF-Exposure-Info-8932224.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf" \
-   "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX3/RF-Exposure-Info/RF-Exposure-Info-8932224.pdf" -o "2BTR9-XTEINKX3-rf-exposure-info.pdf"
-echo "78c21f6f8ab043cb08b9c4848c3509bedd7f673dd2ca6c10ce2804c1bc121fed  2BTR9-XTEINKX3-rf-exposure-info.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md b/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md
deleted file mode 100644
index 3d539de..0000000
--- a/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX3-users-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,373,110 B (1.31 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,373,110 B (1.31 MiB) |
-| SHA-256 | `f3cc9a89924739bc7ab80bdeea2dc52970c327fde0f33e4ff8b2bd739eaf7fa1` |
-| FCC ID | **`2BTR9-XTEINKX3`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | Users Manual |
-| FCC document id | 8932229 |
-| Upstream publication date | 2026-06-24 |
-| Grant date | 2025-12-26 |
-| Equipment class | XTEINK X3, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX3/User-Manual/Users-Manual-8932229.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8932229>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX3/8932229.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX3>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX3/User-Manual/Users-Manual-8932229.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf" \
-   "devices/xteink/x3/artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX3/User-Manual/Users-Manual-8932229.pdf" -o "2BTR9-XTEINKX3-users-manual.pdf"
-echo "f3cc9a89924739bc7ab80bdeea2dc52970c327fde0f33e4ff8b2bd739eaf7fa1  2BTR9-XTEINKX3-users-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x3/artifacts/certification/README.md b/devices/xteink/x3/artifacts/certification/README.md
deleted file mode 100644
index d969375..0000000
--- a/devices/xteink/x3/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2BTR9-XTEINKX3`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-XTEINKX3`** |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Granted | **2025-12-26** |
-| Equipment class | XTEINK X3, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Source page | <https://fccid.io/2BTR9-XTEINKX3> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2BTR9-XTEINKX3-id-label-location-info.pdf` | 367,446 | `ce6218cf3519448b227e6c7a5a4a6a150362cf5eaa165fda3798ece3481c8204` | ID Label/Location Info |
-| `2BTR9-XTEINKX3-internal-photos.pdf` | 869,708 | `b3affd56115e9c3e49428f9727ba194c0eec6705ddd0b039fd9b4ce28b430a45` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md`](2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md) | 1,001,831 | Test Report |
-| [`2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md`](2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md) | 512,425 | External Photos |
-| [`2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md`](2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md) | 119,149 | RF Exposure Info |
-| [`2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md`](2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md) | 1,373,110 | Users Manual |
-
-Archived total: **4 files, 2.87 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 1.18 MiB** |
-| Archived | **4 files, 2.87 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/xteink/x3/artifacts/firmware/zocs-x3-stock-images.NOT-FETCHED.md b/devices/xteink/x3/artifacts/firmware/zocs-x3-stock-images.NOT-FETCHED.md
deleted file mode 100644
index 510a45c..0000000
--- a/devices/xteink/x3/artifacts/firmware/zocs-x3-stock-images.NOT-FETCHED.md
+++ /dev/null
@@ -1,118 +0,0 @@
-# Xteink X3 stock firmware images — acquisition record
-
-**Status: `not-downloaded` into this repository.** This file is a
-**self-sufficient placeholder**: everything needed to obtain and verify all four
-images is here, and **none of it requires `git lfs`, a clone, or access to any
-archive.** Written 2026-09-11.
-
-## Why this file exists
-
-The 2026-09-04 sweep recorded these four images as *"Git LFS blobs that were not
-fetched"* and the verification report listed them as an open gap, noting the
-`.bin` entries in the upstream Git tree are **~130-byte LFS pointer files**, so a
-naive `curl` of the raw URL yields a text stub rather than firmware.
-
-This pass **resolved the acquisition method and verified it end-to-end**, but did
-not vendor the bytes: three of the four are 16 MiB each, they are proprietary
-vendor firmware with no licence, and the repository already archives the
-comparable X4 dump rather than tracking it.
-
-## The four images
-
-Upstream: [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher),
-commit **`79d2f5b8f1df08d2c8fb33146ac5f887790ddb9e`** (HEAD at 2026-09-11),
-directory `firmware/`.
-
-| File | Version | Lang | Type | **Bytes** | **SHA-256 (= the Git-LFS oid)** |
-|---|---|---|---|---:|---|
-| `x3_en_v1.0.7_full.bin` | **V1.0.7** | EN | full 16 MB flash | **16,777,216** | `f631402cceff2a3e39252ca1fc71afee8274b3060afe7f81d2e5dd45413c8b22` |
-| `x3_en_v5.2.13_full.bin` | **V5.2.13** | EN | full 16 MB flash | **16,777,216** | `37efcb7db2422b6c7b86b23b2e82b0fb4453ebde350014e7f8e8ad3f06ca2dac` |
-| `x3_cn_v5.2.13_full.bin` | **V5.2.13** | CN | full 16 MB flash | **16,777,216** | `edfe1e5eb0083b860f82281aa25391a3fdea2a598a1fb618408808a18a6ca9aa` |
-| `x3_cn_v5.2.13_ota.bin` | **V5.2.13** | CN | OTA, app only | **6,254,064** | `0b2cbc4a6414aef4ad6e676b59fdefa3b529189758953765b26df02bac77bcb6` |
-
-**The Git-LFS `oid` *is* the SHA-256 of the file content.** Those hashes are read
-from the pointer files and are therefore usable as integrity checks without ever
-touching LFS.
-
-Two further LFS blobs sit alongside them and are **not** stock firmware:
-`firmware/crosspoint-x3-alpha/{bootloader,firmware,partitions}.bin`.
-
-## Reacquisition — `automatic`, verified working 2026-09-11
-
-**No `git lfs` required.** GitHub's LFS batch API answers unauthenticated:
-
-```bash
-OID=0b2cbc4a6414aef4ad6e676b59fdefa3b529189758953765b26df02bac77bcb6
-SIZE=6254064
-
-curl -s -X POST \
-  "https://github.com/zocs/eink-quick-flasher.git/info/lfs/objects/batch" \
-  -H "Accept: application/vnd.git-lfs+json" \
-  -H "Content-Type: application/vnd.git-lfs+json" \
-  -d "{\"operation\":\"download\",\"transfers\":[\"basic\"],
-       \"objects\":[{\"oid\":\"$OID\",\"size\":$SIZE}]}" -o batch.json
-
-URL=$(python3 -c "import json;print(json.load(open('batch.json'))['objects'][0]['actions']['download']['href'])")
-curl -sL "$URL" -o x3_cn_v5.2.13_ota.bin
-
-sha256sum x3_cn_v5.2.13_ota.bin     # must equal $OID
-```
-
-- **Status: `executed-success`**, 2026-09-11. The OTA image was fetched
-  (HTTP 200, 6,254,064 bytes) and its SHA-256 **matched the oid exactly**.
-- The signed S3 `href` expires in **3600 s**; re-run the batch call, do not cache
-  the URL.
-- To get a pointer for any other file:
-  `gh api "repos/zocs/eink-quick-flasher/contents/firmware/<name>?ref=79d2f5b8f1df08d2c8fb33146ac5f887790ddb9e" --jq .content | base64 -d`
-- Fallback, if the batch API ever refuses: `git lfs` after a normal clone, or
-  `https://github.com/zocs/eink-quick-flasher/raw/79d2f5b/firmware/<name>`
-  (which redirects to `media.githubusercontent.com` for LFS paths).
-
-## What the fetched image establishes
-
-The OTA image was fetched and parsed but **not retained**. Its ESP image header
-and `esp_app_desc_t` read:
-
-| Field | Value |
-|---|---|
-| Magic | `0xE9` — a valid ESP application image |
-| **`chip_id`** | **5 = ESP32-C3** |
-| Segments | 6 |
-| Entry point | `0x40381E52` |
-| `project_name` | **`arduino-lib-builder`** |
-| Version string in the descriptor | `esp-idf: v4.4.7 38eeba213a` |
-| `idf_ver` | **`v4.4.7-dirty`** |
-| Build time/date in descriptor | `12:29:20`, `Mar  5 2024` — the **Arduino core prebuilt** date, not the app's |
-| Strings present | `5.2.13`, `xteink`, `xteink_ble` |
-
-**Two findings:**
-
-1. **`chip_id = 5` independently confirms the X3 is an ESP32-C3**, from a
-   machine-readable field in a vendor image — a second mechanism, alongside the
-   FreeInk profile, the Chinese BOM and the X4's own dump.
-2. **The X3 stock firmware is built on the same Arduino / ESP-IDF v4.4.7 base as
-   the X4's**, which this repository already established by parsing the X4 dump.
-   That is direct support for the existing conclusion that **one codebase serves
-   both C3 models** — the same reason the version number `V5.2.13` appears on
-   both devices.
-
-**`xteink_ble` is a string in an X3 image.** The X3's BLE capability has not been
-characterised anywhere in this tree; this is the first evidence that the stock
-firmware carries a BLE component.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`unknown`** — proprietary vendor firmware redistributed by a third party with no licence statement |
-| Disposition | **`reference-only`** |
-| Repository state | `not-downloaded` |
-| Reacquisition | **`automatic`** — the recipe above, verified 2026-09-11 |
-| Total if fetched | **56,585,712 bytes** across four files |
-
-## Cited from
-
-[`../../factory-firmware.md`](../../factory-firmware.md) ·
-[`../../gaps-and-conflicts.md`](../../gaps-and-conflicts.md) ·
-[`../../commands.md`](../../commands.md) ·
-[`../../sources.md`](../../sources.md) (source **X310**).
diff --git a/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01 b/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01
deleted file mode 120000
index 336b467..0000000
--- a/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01
\ No newline at end of file
diff --git a/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.link b/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.link
deleted file mode 120000
index b5511eb..0000000
--- a/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-imgur-2026-07-01
\ No newline at end of file
diff --git a/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.md b/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.md
deleted file mode 100644
index 1fd7a9f..0000000
--- a/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01.ARCHIVED.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# ARCHIVED: `imgur-2026-07-01`
-
-> This directory was **moved out of the repository**, not deleted.
-> Archived **2026-09-04**.
-
-**Reason:** 19 MB of full-resolution teardown photography; every fact has been extracted into the device record and the album is re-enumerable from Imgur.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x3/artifacts/teardown/imgur-2026-07-01` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01` |
-| Type | directory |
-| Size | 19,513,196 B (18.61 MiB) |
-| File count | 14 |
-| Last modified (mtime) | 2026-09-04 07:36:57Z |
-| Author / committer | Reddit user posting to r/xteinkereader |
-| Published / revised | 2026-07-01 (Imgur per-image timestamp 2026-07-01 17:44:53) |
-| Retrieved | 2026-09-04 |
-| License | Unknown — no terms stated by the uploader. |
-| Difficulty to re-obtain | Moderate. The album URL alone is not enough: `https://imgur.com/a/<id>` is a JavaScript shell and scraping its HTML yields only 2 of the 13 images. |
-| Access notes | Use the undocumented endpoint `https://imgur.com/ajaxalbums/getimages/OA6CS2C/hit.json` to enumerate all 13 image hashes plus captions, dimensions and upload timestamps, then fetch `https://i.imgur.com/<hash>.jpg` for each. A plain browser User-Agent is sufficient; no auth. Per-image SHA-256 values are in the Contents table below and in `manifest.json`. |
-
-## Contents
-
-| File | Bytes | SHA-256 |
-|---|---:|---|
-| `01-u60Rtxi.jpg` | 1,157,440 | `0cbdb9fa877731b61a114b133a024c7c433264ef1eebea441c9fce5efa5bf4b9` |
-| `02-tdku70e.jpg` | 1,136,501 | `5eb74bd33e03f742449da5b41359b6b4951126c8526ab02878d5ccf9d74a75b5` |
-| `03-Q5jsUoi.jpg` | 1,908,658 | `6e076711cabf6d37231cc7dc28e7c8001b1aec5b5108d138cb708e2bd70c6caf` |
-| `04-WAlvma8.jpg` | 1,615,687 | `af78bf675054744550811f88eeda252acc3e8b64d0fc4d2fce3d3384fb059680` |
-| `05-lBJtD4I.jpg` | 740,345 | `97cbad3d4787586d0c7f0698945a99c5af46915b3de0619e3358fac01315c665` |
-| `06-pcqe4Q0.jpg` | 1,061,091 | `7f8299b06fd938e47c22e1555af0ae340cf557e3093e1b001b563c41321d0c2c` |
-| `07-QQz92jU.jpg` | 1,175,909 | `0cdc4eefc11f1dd44077b35186971418892c8c7fac5ad1ec3b8149eb758e408f` |
-| `08-ZkQliFL.jpg` | 2,021,156 | `d1662b9d3effbecbe9ac23ccfd4dd991a046bf4869a32680319f936557392a11` |
-| `09-Q0UGXpo.jpg` | 688,065 | `ba1106d72f7b58e27a15cee3cac0dad6a94233902d0207e3cc9be8c2a215f902` |
-| `10-YgdHbR1.jpg` | 1,935,873 | `2fb568c906bbdf4e3331981e5d1d5fe0b8835c88ac319ed518d081d0de8f02aa` |
-| `11-bgXQoVr.jpg` | 2,028,489 | `bf11e447d41a133801421793b0c68b2a27cbae10368c30fa50e0556d0974ffa6` |
-| `12-wKlM8uS.jpg` | 2,003,480 | `4fbe14446f9754b800978abf2039d5691a3ba191219de78c354a413f7a7d2378` |
-| `13-Ay3rpJg.jpg` | 2,037,024 | `a005cdf12c7907907b4e7a93c09e3161290cf69dd0882bf5a63e46c448a1f39d` |
-| `manifest.json` | 3,478 | `e6d63042f523e91759fbf46481fe1ea4e832820b91e0d3ed7e9af73bfb4e1a67` |
-
-## How to get it back
-
-Independent recovery URLs, most reliable first:
-
-- original download URL:  
-  <https://imgur.com/a/xteink-x3-teardown-OA6CS2C>
-- album manifest JSON — the reliable enumeration path, returns all 13 hashes and captions:  
-  <https://imgur.com/ajaxalbums/getimages/OA6CS2C/hit.json>
-- the Reddit post carrying the link, with the author's context and comments:  
-  <https://old.reddit.com/r/xteinkereader/comments/1uksv6s/xteink_x3_teardown/>
-
-Restore from the local archive:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/teardown/imgur-2026-07-01" \
-   "devices/xteink/x3/artifacts/teardown/imgur-2026-07-01"
-```
-
-If every URL above is dead, try the Wayback Machine:
-
-    https://web.archive.org/web/2/https://imgur.com/a/xteink-x3-teardown-OA6CS2C
-
diff --git a/devices/xteink/x3/artifacts/teardown/sunwoods-cn b/devices/xteink/x3/artifacts/teardown/sunwoods-cn
deleted file mode 120000
index 2ed8550..0000000
--- a/devices/xteink/x3/artifacts/teardown/sunwoods-cn
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/xteink/x3/artifacts/teardown/sunwoods-cn
\ No newline at end of file
diff --git a/devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.link b/devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.link
deleted file mode 120000
index f58c1ab..0000000
--- a/devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-sunwoods-cn
\ No newline at end of file
diff --git a/devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.md b/devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.md
deleted file mode 100644
index cebd4d9..0000000
--- a/devices/xteink/x3/artifacts/teardown/sunwoods-cn.ARCHIVED.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# ARCHIVED: `sunwoods-cn`
-
-> This directory was **moved out of the repository**, not deleted.
-> Archived **2026-09-04**.
-
-**Reason:** 4.9 MB of teardown photography plus a schematic sketch; facts extracted into the device record and the set is re-fetchable from GitHub.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x3/artifacts/teardown/sunwoods-cn` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/teardown/sunwoods-cn` |
-| Type | directory |
-| Size | 5,034,272 B (4.80 MiB) |
-| File count | 11 |
-| Last modified (mtime) | 2026-09-04 07:36:57Z |
-| Upstream repository | sunwoods/Xteink-X3 |
-| Author / committer | GitHub user `sunwoods` |
-| Retrieved | 2026-09-04 |
-| License | None declared (no LICENSE file). |
-| Path within upstream repo | `readme-img/` |
-| Difficulty to re-obtain | Easy — ten plain raw fetches, no auth. |
-| Access notes | Files are named `01.jpg` … `10.jpg`. The schematic sketch is `02.jpg`. The repository description is 收集关于阅星瞳X3的软硬件信息 — note it uses the brand spelling 阅星瞳 (with 瞳), while several other Chinese sources use 阅星曈 (with 曈). |
-
-## Contents
-
-| File | Bytes | SHA-256 |
-|---|---:|---|
-| `01.jpg` | 413,548 | `a6d982ea2571381fb431e90063bdbfb0224b7f9482aa2ccbcd5f8dc86c189997` |
-| `02.jpg` | 1,265,063 | `09d65eb222c11a5be601d48ca35ea580dbe7e4cce5a751f5f2c376244d92e8e2` |
-| `03.jpg` | 508,365 | `efa40a9bcc5a1c40f40a5375d25a110a3868cc64ea4ce3b8e0ad390087a1e3ca` |
-| `04.jpg` | 458,675 | `b36a6b60eea4de0f6ed08b0aaad28af77688b2d6d4166ee94711a85180e6df40` |
-| `05.jpg` | 787,871 | `82fae7b72354604613028f39f6090d60794e89b345002123e44f3c4e58b41897` |
-| `06.jpg` | 755,206 | `56b38759f56431dd3b120466f9163c99b160c3ccc70b494e7dd6bfd1d9567538` |
-| `07.jpg` | 239,875 | `ecbd42a7c6660fc2fbdac8dfd831a69646b3e0ec232a6cb3af9f78e88d601258` |
-| `08.jpg` | 221,681 | `5f1dc8708057411850d94dcb5d1eb059fdd2d509ee3aea1f10a51e09b2bb330b` |
-| `09.jpg` | 235,823 | `3aa7a9c7370cfdc08e21d89383ae24286fc53a1bc53ad983cd8871823d867b20` |
-| `10.jpg` | 146,545 | `4849f58f3a2e96c72acd08e635ab01f8b7dc07a303f62b12e5e70a9d9fb4be4a` |
-| `README.upstream.md` | 1,620 | `ded2c73ec87ecf306b745d33df70892d6d897e397df09f762adeafb61403f1dd` |
-
-## How to get it back
-
-Independent recovery URLs, most reliable first:
-
-- current default branch (may have changed):  
-  <https://github.com/sunwoods/Xteink-X3/tree/HEAD/readme-img/>
-- original download URL:  
-  <https://github.com/sunwoods/Xteink-X3/tree/main/readme-img>
-- direct raw URL pattern — substitute 01..10 for each image; 02 is the schematic:  
-  <https://raw.githubusercontent.com/sunwoods/Xteink-X3/main/readme-img/02.jpg>
-- repository root, including the README that carries the BOM list:  
-  <https://github.com/sunwoods/Xteink-X3>
-
-Restore from the local archive:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x3/artifacts/teardown/sunwoods-cn" \
-   "devices/xteink/x3/artifacts/teardown/sunwoods-cn"
-```
-
-If every URL above is dead, try the Wayback Machine:
-
-    https://web.archive.org/web/2/https://github.com/sunwoods/Xteink-X3/tree/HEAD/readme-img/
-
diff --git a/devices/xteink/x3/certification-and-compliance.md b/devices/xteink/x3/certification-and-compliance.md
deleted file mode 100644
index c708611..0000000
--- a/devices/xteink/x3/certification-and-compliance.md
+++ /dev/null
@@ -1,205 +0,0 @@
-# Certification and compliance — x3
-
-Compiled **2026-09-11** by the round-2 index merge, from the certification pass's findings in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md). Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware.
-
-> **Why this arrived late.** These findings were produced on 2026-09-11 but written into `scratch/` because a sibling agent held `devices/xteink/` at the time. That conflict is over; this file is the properly-filed result.
-
----
-
-## 1. Summary
-
-**FCC: granted.** `2BTR9-XTEINKX3`, 2025-12-26.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2BTR9-XTEINKX3` — granted **2025-12-26** |
-| **CE / RED (EU)** | ⚠ no published DoC located; no database exists to search (§4) |
-| **UKCA** | ⚠ not determined (§4) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§4) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§4) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§4) |
-
-⚠ **This reverses the 2026-09-04 finding of *no FCC/CE filings*.** See §5.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Every
-probe below ran on **2026-09-11**, in one session, against one host, with one tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** — a real Xteink grant |
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** — M5Stack Cardputer |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**Positives → 200. Negatives → 404.** Raw run:
-`scratch/market-and-certification/logs/fcc-controls.txt`.
-
-These controls are the whole basis on which the absence findings below may be read as evidence.
-They are reproduced in each of the five Xteink records rather than referenced once, because a
-reader arriving at one device record must be able to judge that record's evidence without
-chasing a link.
-
-Beyond the ID probes, **the grantee was enumerated in full rather than guessed**: `2BTR9`
-yields **five** FCC IDs and no more. A product absent from a complete grantee listing is
-*absent*, not merely *un-found* — which is exactly the distinction the 2026-09-04 sweep could
-not make, because it had no grantee code to enumerate.
-
-⚠ **A counter-trap worth recording.** `https://fccid.io/2BTR9` prints **"6 FCC IDs"** in its
-page header, but the applications table lists **five**, and exactly five `href="/2BTR9…"` links
-exist in the HTML. The headline counter and the table disagree. **Trust the table.**
-
----
-
-## 3. The whole grantee — `2BTR9`
-
-| Field | Value |
-|---|---|
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** |
-| Grantee code | **`2BTR9`** |
-| Registered | **2025-12-21** |
-| Contact | Chen Chu |
-| Address | Room 1209, Yichuang International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community, Guanlan Street, Longhua District, Shenzhen, China |
-| FCC IDs | **5** |
-
-| FCC ID | Granted | Device | Purpose | Record |
-|---|---|---|---|---|
-| `2BTR9-X4L` | **2026-08-13** | XTEINK X4 Light | Original Equipment | [`x4-light`](../x4-light/README.md) |
-| `2BTR9-X4C` | **2026-07-20** | XTEINK X4 Classic | Original Equipment | [`x4-classic`](../x4-classic/README.md) |
-| `2BTR9-X4PRO` | **2026-06-16** | XTEINK X4 Pro | Original Equipment | [`x4-pro`](../x4-pro/README.md) |
-| `2BTR9-XTEINKX4` | **2026-01-05** | XTEINK X4 | Original Equipment | [`x4`](../x4/README.md) |
-| `2BTR9-XTEINKX3` | **2025-12-26** | XTEINK X3 | Original Equipment | [`x3`](../x3/README.md) |
-
-All five: 2402–2480 MHz (BLE) and 2412–2462 MHz (Wi-Fi, US channels 1–11). Long-term
-confidentiality granted on all five for Schematics, Block Diagram and Operational Description.
-
-**Not granted:** no FCC ID under `2BTR9` corresponds to the [**Xteink S4**](../s4/README.md) or
-the [**Xteink Nano**](../nano/README.md). Against a complete enumeration with passing controls,
-those two devices are **not FCC-authorised as of 2026-09-11**.
-
-Xteink filed **Original Equipment** authorisations, not module-based ones. The internal
-photographs show why: the X4 main PCB carries a **bare QFN SoC with a PCB meander antenna etched
-into the board**, not a drop-in pre-certified Espressif module. A design like that cannot
-inherit a module grant, so the vendor had to certify the whole device. That is consistent with,
-and corroborates, the grant record.
-
-
-### The `2BTR9-XTEINKX3` filing
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-XTEINKX3`** |
-| Device description | XTEINK X3 |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Granted | **2025-12-26** |
-| Frequency ranges | 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Short-term confidentiality | Yes |
-| Exhibit rows | 13 |
-| Filing page | <https://fccid.io/2BTR9-XTEINKX3> — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld:**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-Internal photographs are **public** and held in this record — see `artifacts/certification/`.
-
-**Exhibits obtained** — US Government public records, redistribution **`allowed`**. Downloaded 2026-09-11, magic bytes validated (`%PDF`).
-
-Retained in this record, at [`artifacts/certification/`](artifacts/certification/README.md):
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| [`2BTR9-XTEINKX3-id-label-location-info.pdf`](artifacts/certification/2BTR9-XTEINKX3-id-label-location-info.pdf) | 367,446 | `ce6218cf3519448b227e6c7a5a4a6a15…` | ID Label/Location Info |
-| [`2BTR9-XTEINKX3-internal-photos.pdf`](artifacts/certification/2BTR9-XTEINKX3-internal-photos.pdf) | 869,708 | `b3affd56115e9c3e49428f9727ba194c…` | Internal Photos |
-
-Archived out of the repository, each with a self-sufficient placeholder beside it carrying hash, size, FCC document id and five reacquisition URLs:
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX3-ant-test-report.pdf.ARCHIVED.md) | 1,001,831 | Test Report |
-| [`2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX3-external-photos.pdf.ARCHIVED.md) | 512,425 | External Photos |
-| [`2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX3-rf-exposure-info.pdf.ARCHIVED.md) | 119,149 | RF Exposure Info |
-| [`2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX3-users-manual.pdf.ARCHIVED.md) | 1,373,110 | Users Manual |
-
----
-
-## 4. Other jurisdictions
-
-| Regime | Result |
-|---|---|
-| **FCC (US)** | ✅ **granted** — see §1 |
-| **CE / RED (EU)** | ⚠ No published DoC located; no `xteink.com` certification page exists. CE is self-declared; **there is no database to search** |
-| **CE mark on product** | ⚠ **Not determined** — the `ID Label` exhibits were downloaded but not visually inspected for secondary marks. **Open work** |
-| **UKCA** | ⚠ Not determined; no database exists |
-| **SRRC / CCC (CN)** | ❌ **Not searched** — `wireless.miit.gov.cn` and `srrccn.org` both failed to connect. **Not an absence finding** |
-| **MIC 技適 (JP)** | ⚠ **Not searched** — endpoint reachable, not queried |
-| **ISED (CA)** | ⚠ **Not searched** — `sms-sgs.ic.gc.ca` returned 503 |
-
----
-
-## 5. ⚠ Correction — this supersedes the 2026-09-04 finding
-
-[`VERIFICATION-sweep-2026-09-04.md`](../../../VERIFICATION-sweep-2026-09-04.md) §6 recorded:
-
-> **Certification and regulatory records** were checked only for Xteink (where the finding was
-> that no external CE/FCC marking exists on the devices at all). No positive control was run, so
-> the absence is weaker evidence than it looks.
-
-That self-doubt was justified. The original finding confused **"no mark visible in a product
-photograph"** with **"no grant exists"**. They are different claims and only the first was ever
-tested.
-
-- ✅ **Survives:** "no FCC ID is printed on the exterior of the units we photographed." Not
-  re-tested here, and may well still be true.
-- ❌ **Refuted:** any reading that Xteink devices are uncertified or unauthorised for the US.
-  **Xteink holds five granted Original Equipment authorisations.**
-
-47 CFR §2.935 permits an **e-label** displayed in software instead of a printed mark, which is
-the ordinary arrangement for a device with a screen. **That is a likely explanation and it was
-not verified.**
-
-The original sentences in the sweep report and in the Xteink records have **not been edited**.
-Dated corrections sit beneath them, and every one is listed in
-[`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
----
-
-## 6. What this does **not** establish
-
-- **No hardware was inspected.** No Xteink unit was obtained, opened or powered.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit.
-- **CE is not established.** No published Declaration of Conformity was located and **there is
-  no CE database to search** — CE is a self-declaration regime. Absence of a published DoC is
-  not absence of conformity.
-- **The `ID Label` exhibits were downloaded but not visually inspected for secondary marks.**
-  Whether a CE mark appears on Xteink label artwork is **open work**, and cheap to close.
-- **SRRC / CCC (CN) did not run.** `wireless.miit.gov.cn` and `srrccn.org` both failed to
-  connect (`000`) on 2026-09-11. That is a method failure, **not** an absence finding.
-- **MIC 技適 (JP) did not run.** The endpoint is reachable (200) but form-driven; not queried.
-- **ISED (CA) did not run.** `sms-sgs.ic.gc.ca` returned 503.
-- **Schematics are permanently withheld** on all five filings, along with block diagrams and
-  operational descriptions. **The FCC is not a route to an Xteink schematic.**
-
-
-## 7. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| XC-1 | FCC ID `2BTR9-XTEINKX3` record | US FCC via fccid.io | **primary (regulatory)**, via mirror | regulatory record | <https://fccid.io/2BTR9-XTEINKX3> | 2026-09-11 | Grant existence, date, frequencies, exhibit list, embargo dates |
-| XC-2 | FCC grantee index `2BTR9` | US FCC via fccid.io | primary via mirror | regulatory record | <https://fccid.io/2BTR9> | 2026-09-11 | The complete five-device Xteink certification history |
-| XC-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
-⚠ Deep `fccid.io` paths serve **403 to a Chrome User-Agent** and **200 to `curl/8.5.0`** — an *inverted* block. The honest UA works; the disguised one does not. The **root** `https://fccid.io/` returns 200 to everything, so a reachability probe against the root reports a false success. **Probe a deep path.**
diff --git a/devices/xteink/x3/commands.md b/devices/xteink/x3/commands.md
deleted file mode 100644
index 227da96..0000000
--- a/devices/xteink/x3/commands.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# Xteink X3 — command ledger
-
-Family-wide research commands: [`../x4-pro/commands.md`](../x4-pro/commands.md).
-X4 firmware-analysis commands (reusable here): [`../x4/commands.md`](../x4/commands.md).
-Retrieved **2026-09-04**. **No command was executed against X3 hardware.**
-
-## Executed successfully by this session
-
-| # | Command | Purpose | Status |
-|---|---|---|---|
-| 1 | `curl -sSL "https://imgur.com/ajaxalbums/getimages/OA6CS2C/hit.json"` | **Enumerate the 13-image teardown album.** The album HTML is a JS shell yielding only 2 of 13 | `executed-success` |
-| 2 | `for i in $(seq 1 13); do curl -sSL "https://i.imgur.com/<hash>.jpg" -o …; done` | Fetch all 13 teardown images with captions | `executed-success` |
-| 3 | `for i in 01..10; do curl -sSL "https://raw.githubusercontent.com/sunwoods/Xteink-X3/main/readme-img/$i.jpg"; done` | Fetch the Chinese teardown set **including the schematic sketch (`02.jpg`)** | `executed-success` |
-| 4 | `curl -sSL ".../sunwoods/Xteink-X3/main/README.md"` | The BOM: Puya flash, QMI8658, DS-series RTC, TP4056-class charger, BQ27220, **ISO 14443A NFC tag** | `executed-success` |
-| 5 | `curl -sSL ".../zocs/eink-quick-flasher/main/firmware/README.md"` | Stock versions **V1.0.7** and **V5.2.13**, CN+EN, full **and** OTA | `executed-success` |
-| 6 | `gh api graphql -f query='{repository(owner:"crosspoint-reader",name:"crosspoint-reader"){discussion(number:2259){…}}}'` | **Resolved the NFC tag's nature and purpose.** Repository *search* does not index discussions — GraphQL is required | `executed-success` |
-| 7 | `sha256sum` over all 23 teardown images | Provenance before archiving | `executed-success` |
-| 8 | `python3 tools/archive_artifact.py --repo-root . --manifest …` | Archived both teardown sets with placeholders | `executed-success` |
-
-## Reported working — community
-
-| # | Procedure | Source | Status |
-|---|---|---|---|
-| 9 | Full backup/restore in ~2 min via [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher) GUI, auto COM detect | its README + `X3-FLASHER-GUIDE` (EN and CN) | `reported-working` |
-| 10 | `esptool.py --chip esp32c3 --port /dev/ttyUSB0 --baud 921600 read_flash 0 0x1000000 x3-stock-full.bin` | what #9 automates | `reported-working` |
-| 11 | `esptool.py --chip esp32c3 … write_flash 0 x3-stock-full.bin` | restore | `reported-working` |
-| 12 | Locked unit: reflash via `crosspointreader.com`, or **SD flash** | [r/XTEINK `1uek163`](https://old.reddit.com/r/XTEINK/comments/1uek163/) | `reported-working` |
-| 13 | **Write the NFC tag** with any Android NFC-writer app (e.g. "NFC Tools"), payload = vCard or a URL | [r/xteinkereader `1vit43t`](https://old.reddit.com/r/xteinkereader/comments/1vit43t/) | `reported-working` — *"Used an NFC writer app on my Android phone, created a contact card format…"* |
-| 14 | **iOS**: use **Shortcuts** to *detect* the tag and run an automation. iOS **cannot read/write** it | [discussion #2259](https://github.com/crosspoint-reader/crosspoint-reader/discussions/2259) | `reported-working` |
-
-## Inferred — never executed, never reported
-
-| # | Command | Would establish |
-|---|---|---|
-| 15 | `esptool.py --chip esp32c3 --port /dev/ttyUSB0 flash_id` | **The Puya flash part number** from its JEDEC ID |
-| 16 | I²C read of registers `0x11`/`0x12` at address `0x68` | **Whether the RTC is a DS3231 (returns a temperature) or a DS1307 (does not).** One read settles a three-way conflict |
-| 17 | I²C scan on **SDA 20 / SCL 0 @ 400 kHz** | Confirm 0x55 / 0x68 / 0x6B and therefore the board profile |
-| 18 | Read `0x00` at `0x6B` expecting `0x05` | QMI8658 `WHO_AM_I` |
-| 19 | Android NFC app reporting **tag technology and UID prefix** | The NFC tag's **type and likely part family** |
-| 20 | `pio run -e x3 [-t upload]` | Standard build |
-| 21 | Boot with serial attached, read `[XTDET] bus probe VER=… FLG=… -> …` | **Which panel controller a given unit carries** — the unanswered question in the two-unit comparison |
-
-**Commands 15, 16, 19 and 21 would each close a named open conflict in this
-record, and each takes under a minute on hardware.**
-
-## Build configuration
-
-```ini
-board_build.mcu = esp32c3
-build_flags = -DFREEINK_DEVICE_X3=1          ; links BOTH UC8253 and UC8279 drivers
-              ; optional UC8279 tuning:
-              ; -DFREEINK_UC8279_CONFIG=yourConfig
-```
-
-`-DFREEINK_DEVICE_X3=1` and `-DFREEINK_DEVICE_X4=1` **can coexist**: one C3 binary
-serves X3-UC8253, X3-UC8279d and X4, resolved at boot by `XteinkDetect`.
-
-## Not run, deliberately
-
-| Command | Why |
-|---|---|
-| Any `write_flash` | No hardware |
-| Git-LFS fetch of the four stock X3 images | Deferred; would need `git lfs`. **Cheap to close** |
-| `curl http://gotaserver.xteink.com/api/check-update` | Would contact a vendor server; request format unknown |
diff --git a/devices/xteink/x3/community.md b/devices/xteink/x3/community.md
deleted file mode 100644
index 4d4b1fb..0000000
--- a/devices/xteink/x3/community.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# Xteink X3 — community reception
-
-From **2,136** deduplicated Reddit posts, **2026-09-04**. Types: **O** firsthand
-ownership · **M** firsthand measurement · **P** demonstrable project ·
-**I** informed interpretation · **Op** opinion · **H** hearsay.
-
-## The X3's distinctive contribution: it is the only Xteink anyone opened
-
-Two independent teardowns exist, both of this device, and **both were motivated by
-curiosity rather than repair**. See [`media.md`](media.md). Nothing comparable
-exists for the X4, X4 Pro or X4 Classic.
-
-## The comparison thread that defines it
-
-[r/xteinkereader `1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/),
-2026-04-28, **412 points** — "X3 vs X4 - actual experience comparison" · **O**
-
-> "…the buttons on the X4 are **clickier and louder**. The X3's buttons are
-> somewhat **mushy and quieter**. … Overall If I have to choose 1, I'd go with the
-> X4. However, I probably will abandon both once the S4 is released."
-
-A firsthand comparative ownership report, and the source of the only tactile
-assessment in this tree. Note the conclusion favours the X4 — on feel, not specs.
-
-The counterweight, from an owner of all three models
-([r/XTEINK `1vw6haq`](https://old.reddit.com/r/XTEINK/comments/1vw6haq/), 2026-08-23):
-
-> "The regular X4 definitely feels obsolete (and also literally discontinued).
-> **The x3 is still a better form factor for carrying on the back of the phone**
-> (+ comes in the white/grey color)." · **O**
-
-And from a buyer choosing it deliberately:
-
-> "someone I met had one and they let me see it and **the crispness of the screen
-> was actually what really sold me on it**." · **O + Op**
-
-That crispness is real and arithmetic: ~257 PPI against the 4.26″ models' ~219.
-
-## Owners can see the panel-controller change
-
-This is the most technically valuable community observation about the X3. A user
-bought **two X3s from different channels** and compared them side by side, both on
-CrossInk 1.5.0, both with the supplied screen protector
-([r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/), 2026-08-10,
-41 pts, **36 comments**) · **M**:
-
-> "**The Official Site one on the LEFT** has slightly whiter background and clearer
-> text. It came with a 32gb XTEINK SD card. **Page turns and menus seem slower**,
-> with all settings being equal.
-> **The Amazon.ca one on the RIGHT** has slightly darker background and not as
-> clear text. It came with a 16gb XTEINK SD card. **Page turns and menus seem
-> faster**, with all settings being equal."
-
-**A visible, reproducible, side-by-side difference in contrast and refresh speed
-between two X3 units.** The obvious hypothesis is the
-[UC8253 → UC8279d](features/display.md) transition — but **which unit carries
-which controller was never determined**, and the thread never resolved it. See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-The same thread reveals **at least four distinct back-casing variants**:
-
-| Variant | Reported by |
-|---|---|
-| Black logo + **sticker label** at the bottom | official site |
-| Grey logo + **engraved text** | Amazon.ca, higher serial |
-| **Completely clean back**, no markings | direct, early pre-order |
-| Faint labelling | direct |
-
-> "They'll outsource to a bunch of manufacturers who can meet the specs." · **Op**
-
-And crucially · **O**:
-
-> "X3 from **Amazon**, light grey text, **unlocked** / X3 from their **official
-> website**, light grey text but **locked** for some reason / X4 from
-> **Aliexpress**, dark text, **locked**"
-
-**USB-lock state does not correlate with channel in any predictable way.** You
-cannot know before purchase.
-
-## NFC — the community solved it, not the vendor
-
-The X3's NFC tag went unexplained for months. The resolution came from a firmware
-maintainer and three owners. See [`features/nfc.md`](features/nfc.md) for the full
-evidence. Demonstrated uses:
-
-| Use | Type |
-|---|---|
-| *"I **wrote my contact infos**, in case it get lost"* — via an Android NFC writer app | **O, demonstrated** |
-| *"when I tap my phone to it it **automatically joins the X3 WiFi and opens the crosspoint manager** in the browser! I use it every time when I want to load up a new book."* | **P** |
-| iOS Shortcuts automation opening `http://crosspoint.local/` on tag detection, with screenshot | **P** |
-| *"I knew it could **clone NFC cards**"* | **H — unverified and implausible for a passive tag** |
-
-Key facts, both firsthand: *"**By default there is no data in the nfc tag**"* and
-iOS can **detect but not read/write** it while Android can do both.
-
-## Reliability
-
-| Report | Date | Type |
-|---|---|---|
-| *"My **glass cracked** a bit on the rear side. So it might not have happened if I had black x3."* — asks which models have **metal backing**; **received no authoritative answer** | 2026-09-02 | **O** |
-| *"Do not step full body weight on your new XTEINK"* — r/ereader, 144 pts | 2026-05-02 | **O** |
-
-The teardown independently confirms the back is **glass**, removable with a heat
-gun and suction cup. **No replacement-part source is known.**
-
-## Price and channel anecdotes
-
-> "**Got an X3 for dirt cheap ($16).** Here are my thoughts after a few days of
-> use. … I still flashed **CrossMux** onto it (a Chinese fork of CrossPoint that
-> adds support for online sources like WeChat Read), and the experience has been
-> fantastic. I can manage my library directly through Calibre, exactly like I do
-> with my Kindle. **I'd honestly say 60 % of my positive** [experience]…"
-> — [r/XTEINK `1vrnxnq`](https://old.reddit.com/r/XTEINK/comments/1vrnxnq/), 2026-08-18 · **O**
-
-The same post is the sharpest published criticism of the vendor:
-
-> "…the **double standard for different distribution channels** and the official
-> team's **negative attitude toward the community** makes me seriously doubt
-> whether I'll buy the next S4." · **Op**
-
-**A single $16 anecdote with an unstated channel is not a used-market price** and
-is not treated as one here.
-
-## Reach beyond the dedicated subreddits
-
-r/eink (*"My Xteink X3 Review (vs X4). The Antidote to Smartphones."*, 34 pts;
-*"Crosspoint on X3 - preview with **smooth antialiasing waveforms**"*, 55 pts ·
-**P**), r/ereader, r/kindle (*"Xteink X3 vs Kindle PPW 12th Gen Size
-Comparison"*), r/koreader (multiple sync threads), r/EDC, r/microreaders.
-
-## Weighting caveat
-
-One of the three dedicated subreddits is **vendor-operated** —
-*"r/xteinkreader is the main sub and **it's run by the company**"*
-([r/xteinkHax `1sbjsr3`](https://old.reddit.com/r/xteinkHax/comments/1sbjsr3/) · **I**),
-and r/xteinkHax exists partly because a post was **removed from it**. Positive
-sentiment sampled from that subreddit alone should not be treated as independent.
diff --git a/devices/xteink/x3/comparisons-and-recommendations.md b/devices/xteink/x3/comparisons-and-recommendations.md
deleted file mode 100644
index a34a09a..0000000
--- a/devices/xteink/x3/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# Xteink X3 — comparisons and recommendations
-
-Dated **2026-09-04**. Full cross-model table: [family index](../README.md#cross-model-comparison).
-
-## The X3's case in one paragraph
-
-**The sharpest, lightest and best-instrumented Xteink, and the cheapest one you
-can still buy.** ~257 PPI against the 4.26″ models' ~219; 55 g; a real TI fuel
-gauge, an RTC, an IMU and an NFC tag that none of the S3 models combine. What you
-give up is USB-C charging, button feel, and — on units shipped since ~July 2026 —
-a panel controller whose fast waveforms nobody has tuned yet.
-
-## Within the family
-
-| | **X3** | [X4](../x4/README.md) | [X4 Pro](../x4-pro/README.md) | [X4 Classic](../x4-classic/README.md) |
-|---|---|---|---|---|
-| Price 2026-09-04 | **$69, in stock** | **delisted** | $99 | never priced |
-| Screen | 3.7″ **792×528, ~257 PPI** | 4.26″ 800×480, ~219 | 4.26″ 800×480 | 4.26″ 800×480 |
-| Mass | **55 g** | ~80 g | unknown | unknown |
-| SoC / PSRAM | C3 / none | C3 / none | **S3 / 8 MB** | **S3 / 8 MB** |
-| Charging | pogo | **USB-C** | pogo | unknown |
-| Touch / frontlight | ✗ / ✗ | ✗ / ✗ | **✅ / ✅** | ✗ / ✗ |
-| Fuel gauge | **BQ27220** — best in family, no profile upload | none (bare ADC) | CW2017 (needs BATINFO) | CW2017 |
-| RTC | DS-series 0x68 (**part unresolved**) | **none** | BM8563 | BM8563 |
-| IMU | **✅ QMI8658** | ✗ | ✗ | ✅ |
-| **NFC** | **✅ — only model with it** | ✗ | ✗ | ✗ |
-| SD sleep power-down | **✅ GPIO13** | **✗ — no enable pin** | ✅ | ✅ |
-| Buttons | 6 (ADC ladder) + power | 6 (ADC ladder) + power | 2 + power | 6 discrete + power |
-
-**Three things stand out.** The cheapest model has the **highest pixel density**;
-it has **more sensors than the "Pro"**; and it is the **only one with NFC**.
-
-## Against development platforms in this repository
-
-| Device | Class | Schematic | USB-C | Headers | Verdict vs X3 |
-|---|---|---|---|---|---|
-| **Xteink X3** | sealed reader | **hand-drawn sketch only** | ✗ (pogo) | ✗ | — |
-| [M5Stack PaperMono](../../m5stack/papermono/README.md) | dev board | **✅ published, 6 sheets** | ✅ | ✅ | **Better for development.** Bigger, thicker, no pocketability, no case ecosystem |
-| [Waveshare ESP32-S3-ePaper-3.97](../../waveshare/esp32-s3-epaper-3.97/README.md) | dev board | partial | ✅ | ✅ | **ESP32-S3 with PSRAM**, 3.97″ SSD1677 panel, and it also carries a **QMI8658** — closest silicon analogue to an X3 in dev-board form |
-| [ZeroWriter](../../zerowriter/) | DIY appliance | ✅ open | ✅ | ✅ | Different purpose — keyboard-first writing appliance |
-
-**Partial substitutes, not equivalents.** None is 55 g, none fits in a pocket,
-none has a magnetic back designed to stick to a phone. Conversely the X3 has no
-headers, no schematic worth the name, and often a USB lock.
-
-**The honest framing:** if your goal is to *build* something on e-paper, buy a dev
-board — you get a schematic and no unlock dance. If your goal is to *read* on
-something you can also reprogram, the X3 is the cheapest device in existence that
-does both well.
-
-## Direct competitors named by owners
-
-| Device | Community verdict |
-|---|---|
-| **Murphy 3.7″ (HamGeek/墨菲)** | The closest size competitor. *"Better than XTEINK X4? (Murphy 3.7")"* drew 70 comments; owners call build quality *"pretty dodgy"* and *"unusably thick"* |
-| **EEGO** small readers | Raised as an emerging alternative; the FreeInk SDK carries an EEGO A4 profile |
-| **OBOOK5** | 219 PPI, 1200 mAh, ~23 GB usable, *"smaller than the boox palmas, and cheaper"* |
-| **Boox Picco / Palma** | Android, much more expensive |
-| **Kindle PPW 12th gen** | An r/XTEINK thread does a size comparison; different category |
-
-An r/ereader survey thread — *"After Seeing the Xteink X3, I Want an E-Reader with
-Under 4″ Screen. What's Available, What's Coming?"* — concluded the sub-4″ market
-was *"about to get a bit of a shake-up"*. That was 2026-05-24; the X3 is still the
-best-supported option in it.
-
-## The buying decision that actually matters: which panel
-
-Units shipped from ~**July 2026** carry a **UC8279d** instead of a UC8253. There
-is **no external marking**. Consequences:
-
-- Require **CrossPoint ≥ 1.5** / **CrossInk ≥ 1.5**, or a fork on a current SDK.
-  Older firmware may leave a blank screen, and stale forks on locked units risk a
-  soft brick.
-- Expect **no grayscale** and probably a **full flash on every page turn** until
-  someone tunes UC8279 waveform banks. Only
-  [`anki630/crossmosa-freeink-sdk`](https://github.com/anki630/crossmosa-freeink-sdk)
-  is working on it.
-
-A firsthand two-unit comparison found a real, visible contrast/speed difference
-between X3s bought from different channels — **but never determined which
-controller each had**. See [`performance.md`](performance.md).
-
-## Recommendations
-
-| Scenario | Recommendation | Confidence |
-|---|---|---|
-| **Cheapest currently-buyable Xteink; sharpest text; lightest** | **X3, $69** | high |
-| You want a sensor platform (IMU, RTC, real gauge, NFC) in a case | **X3** — nothing else in the family combines them | high |
-| You want touch and a frontlight | **X4 Pro ($99)**, not the X3 | high |
-| **You need USB-C charging** | **Not the X3.** X4 used, or a dev board | high |
-| You want the best button feel | **X4** (used) — owners call the X3's *"mushy and quieter"* | medium (subjective, single source) |
-| You want maximum firmware maturity | Either C3 model; the X3 needs **≥ 1.5** | high |
-| You are memory-constrained (big books, heavy images) | **An S3 model.** The X3 has no PSRAM and is where OTA OOM was observed | high |
-| You are buying used and want to avoid the panel lottery | **You cannot tell before purchase.** Budget for firmware ≥ 1.5 | high |
-
-## Honest limits
-
-- **Nothing about the X3 was measured**, by this session or anyone. No runtime, no
-  refresh timing, no sleep current — despite a teardown done expressly to measure
-  power.
-- Battery capacity (650 mAh) is a **single-source photograph caption**.
-- Competitor figures are **community-reported**, not verified.
-- The **RTC part is unresolved**, so timekeeping accuracy cannot be compared.
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered.
-
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — the X3 in the pocket-e-ink-reader group alongside the PaperMono, the Waveshare
-  ESP32-S3-ePaper-3.97 and ZeroWriter, with an explicit list of the comparisons the
-  evidence does **not** support (battery life and refresh speed among them).
-- [**Xteink firmware ecosystem**](../firmware-ecosystem.md) — the X3's two board
-  profiles (`XTEINK_X3` for UC8253, `XTEINK_X3_UC8279` for the UC8279d batches),
-  and the **I²C fingerprint at `0x55`/`0x68`/`0x6B` that tells an X3 from an X4**
-  so one C3 binary can serve both.
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — why the C3's missing PSRAM is the constraint behind this device's observed OTA
-  out-of-memory, with the framebuffer arithmetic.
-- [**Adding LoRa, NFC and an RGB sidelight to e-ink firmware**](../../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-  — ⚠ **read §1.3 before planning anything around "the X3 has NFC".** The fitted
-  part is a *passive tag* on no host bus; adding NFC *reading* to an X3 is a
-  hardware modification, not a firmware task.
diff --git a/devices/xteink/x3/compatibility-and-status.md b/devices/xteink/x3/compatibility-and-status.md
deleted file mode 100644
index 1fa6183..0000000
--- a/devices/xteink/x3/compatibility-and-status.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# Xteink X3 — compatibility and status
-
-Snapshot **2026-09-04**.
-
-## Working
-
-Display (UC8253), ADC ladder buttons, microSD with its power rail, BQ27220 gauge,
-QMI8658 IMU, RTC (whatever it is), Wi-Fi, BLE. Widely exercised — the X3 is the
-second-most-targeted device in the ecosystem after the X4.
-
-## Partial
-
-| Item | State |
-|---|---|
-| **UC8279d panel batch** | Driver written **from the datasheet only**. No unit benched. Full/Half/Fast all run the same OTP waveform — likely a **full flash on every page turn**. No grayscale |
-| **Controller fingerprint** | Works, but relies on an untested assumption about what the UC8253 answers to `0x70` |
-| **Deep sleep** | Rail handling correct; **no current measurement exists** |
-| **RTC** | Functions; **the part is not identified**, so accuracy and alarm/temperature capability are unknown |
-| **NFC** | Hardware present; no software, no known purpose |
-
-## Known failures with named causes
-
-| Failure | Version / condition | Note |
-|---|---|---|
-| **OTA out-of-memory** | CrossPoint ≤1.4.0 via GitHub releases | Real, observed. Project stopped using GitHub releases *"as it causes out of memory issues on the x3"* |
-| Blank screen after flashing | Newer UC8279d unit + firmware without that driver | Fixed in CrossPoint 1.5 |
-| Soft brick | Locked unit + fork on a stale SDK | CrossPoint 1.5 release warning |
-| **Rear glass cracking** | Physical | One owner report, unanswered follow-up about metal backing |
-
-## Version-keyed
-
-| Version | Status |
-|---|---|
-| CrossPoint **1.5** (2026-08-07) | **Supports the new X3 display variants.** Recommended minimum for a recently-purchased unit |
-| CrossPoint **1.4.0** (2026-06-24) | X3 OTA problems; use web reflash or SD flash |
-| CrossPoint **1.2.0** | Associated with a documented OTA brick (X4; assumed to apply) |
-| Stock **V5.2.13** | Latest known stock, both CN and EN |
-| Stock **V1.0.7** | Earliest published stock image |
-
-## Hardware-revision keyed
-
-**One known axis: the panel controller.** Units shipped from roughly **July 2026**
-carry a **UC8279d** instead of a UC8253. The vendor gave the community advance
-notice — the only instance found of Xteink pre-announcing a silent hardware change.
-
-**There is no external marking.** A buyer cannot tell before powering on.
-Practical rule: **buy recently → assume UC8279d → require CrossPoint ≥ 1.5 or an
-equivalent.**
-
-## Conflicting reports
-
-The **RTC part** — three sources, three answers, all at address 0x68. See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md). This is the only genuine
-multi-party disagreement in the whole Xteink family, and it exists precisely
-*because* the X3 is the only model with independent teardowns to disagree with.
-
-## Lifecycle
-
-**Current and in stock**, both colours, $69, as of 2026-09-04.
diff --git a/devices/xteink/x3/coverage.md b/devices/xteink/x3/coverage.md
deleted file mode 100644
index 19fddfd..0000000
--- a/devices/xteink/x3/coverage.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Xteink X3 — feature coverage
-
-| Feature | Hardware | Official docs | Community evidence | Guide | Tested | Gaps |
-|---|---|---|---|---|---|---|
-| Display 792×528 (UC8253) | UC8253 | none | SDK, shipping default | [display](features/display.md) | ✅ | Panel module part |
-| Display (UC8279d batch) | UC8279d | none | SDK, **datasheet-only** | [display](features/display.md) | ❌ | **No unit ever benched.** No grayscale, no fast waveforms |
-| Controller fingerprint | VER/FLG probe | none | SDK | [display](features/display.md) | ⚠️ | What UC8253 answers to 0x70 is **unknown** |
-| Buttons (6, ADC ladder) | GPIO1 + GPIO2 | none | SDK, 3 physical devices | [../x4 buttons](../x4/features/buttons.md) | ✅ | — |
-| **IMU / motion page turn** | QMI8658 @0x6B | none | SDK + teardown | [imu](features/imu.md) | ✅ presence | No performance data; no interrupt pin |
-| **RTC** | @0x68 | none | **3 sources disagree on the part** | [rtc](features/rtc.md) | ⚠️ | **Part identity unresolved** |
-| **Fuel gauge** | BQ27220 @0x55 | none | SDK + teardown | [battery](features/battery-and-power.md) | ✅ | Accuracy unmeasured |
-| Battery 650 mAh | — | none | **teardown, single source** | [battery](features/battery-and-power.md) | ✅ | Cell part unknown |
-| microSD + power rail | GPIO 8/10/7/12 + EN13 | none | SDK + factory-firmware RE | [storage](features/storage.md) | ✅ | Max card size |
-| **NFC** | ISO 14443A tag | **vendor claims it** | teardown BOM only | [nfc](features/nfc.md) | ❌ | **Purpose entirely unknown** |
-| Pogo charging | magnets glued to cover | none | teardown + vendor | [battery](features/battery-and-power.md) | ⚠️ | Pinout, voltage, charge-state signal |
-| Wi-Fi / BLE | ESP32-C3 | none | firmware strings (X4 dump) | [../x4 wifi/bt](../x4/features/wifi-and-bluetooth.md) | ✅ | No measurements |
-| Deep sleep | SD rail GPIO13 | none | SDK + factory RE | [battery](features/battery-and-power.md) | ⚠️ | **No current measurement, despite a teardown done expressly to make one** |
-
-## Not fitted
-
-Touch, frontlight, PSRAM, SDMMC, audio, LEDs, GPIO expander, PMIC.
-
-## Advertised features and their status
-
-| Vendor claim (2025-12-09) | Status |
-|---|---|
-| 55 g, 3.7-inch | ✅ consistent |
-| 250+ PPI | ✅ arithmetically confirmed (~257) |
-| Gyroscope for motion page turning | ✅ hardware confirmed; feature implementation not verified |
-| **NFC support** | ⚠️ hardware present; **function unknown** |
-| Magnetic Pogo Pin charging | ✅ confirmed by teardown |
-| Time display and battery percentage | ✅ RTC + BQ27220 present |
-| *"Adjustable warm light settings"* (product page) | ❌ **FALSE — there is no frontlight** |
-| *"Cloud sync"* (product page) | ❌ unsupported; overseas app *"still under development"* per the vendor's own announcement |
-
-## Combination scenarios
-
-| Combination | Status |
-|---|---|
-| Display refresh **+** SD read | Structurally serialised (one SPI bus). Not benchmarked |
-| I²C (gauge + RTC + IMU) **+** SPI | Independent buses; no conflict expected. Untested |
-| OTA **+** low free memory | **Known to fail on this device** |
-
-## Score
-
-**10 of 13** capabilities have citable third-party confirmation.
-**0 of 13** were verified by this session.
-Two are **actively unresolved**: the RTC part and the NFC function.
diff --git a/devices/xteink/x3/development.md b/devices/xteink/x3/development.md
deleted file mode 100644
index d4f1c1a..0000000
--- a/devices/xteink/x3/development.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# Xteink X3 — development
-
-> ESP32-C3. Retrieval **2026-09-04**. **Nothing executed against hardware.**
-
-## Toolchain
-
-| Item | Value | Status |
-|---|---|---|
-| Framework | Arduino-ESP32 under PlatformIO | `reported-working` |
-| Build flag | `-DFREEINK_DEVICE_X3=1` | `reported-working` |
-| Effect | Links **both** X3 drivers — `FREEINK_DRIVER_UC8253_X3` **and** `FREEINK_DRIVER_UC8279`. Which one runs is decided at boot | **[SDK]** |
-| esptool chip | `esp32c3` | `inferred` |
-| Optional | `-DFREEINK_UC8279_CONFIG=yourConfig` to inject a UC8279 config | **[SDK]** |
-
-Nothing extra is needed for the newer panel: *"Build: nothing new."*
-
-## One binary, two devices
-
-`-DFREEINK_DEVICE_X3=1` and `-DFREEINK_DEVICE_X4=1` can coexist:
-`XteinkDetect::selectXteinkDevice()` fingerprints the I²C bus (SDA20/SCL0) for the
-BQ27220, DS-series RTC and QMI8658 and picks the profile at runtime. Then a second
-probe picks the panel controller. **A single C3 image can serve X3-UC8253,
-X3-UC8279d and X4.**
-
-## Build / flash / monitor
-
-```bash
-pio run -e x3                 # inferred
-pio run -e x3 -t upload       # inferred
-pio device monitor -b 115200  # inferred
-```
-
-## USB lock
-
-Same as the rest of the family. See
-[`../x4/development.md`](../x4/development.md#usb-lock). X3-specific note from the
-CrossPoint 1.4.0 release:
-
-> "Seems x3 users are having issues OTA updating. You can simply **reflash from the
-> website if you're unlocked or SD flash if you're locked.** You won't lose any
-> settings. … I'd like to stop using github releases moving forward as it causes
-> **out of memory issues on the x3**."
-> — [r/XTEINK `1uek163`](https://old.reddit.com/r/XTEINK/comments/1uek163/), 2026-06-24
-
-## Bricking risks — X3-specific
-
-| Risk | Note |
-|---|---|
-| **OTA out-of-memory** | **Observed on this device**, not theoretical. No PSRAM. GitHub-release OTA was abandoned because of it |
-| **New panel variant** | Units shipped from ~July 2026 carry a **UC8279d**. Firmware without that driver leaves a blank screen. CrossPoint 1.5 (2026-08-07) added support: *"this release DOES support the new x3 display variants"* |
-| **Stale fork + locked unit** | *"Other forks will need to pull the latest SDK to avoid **soft bricking locked units**"* |
-| **Forgetting the SD rail** | GPIO13 must be driven HIGH in setup, LOW on sleep. Omitting the LOW causes battery drain through sleep |
-| **Running the C3 I²C probe on an S3** | SDA20/SCL0 are USB D+ and a boot strap on S3. The SDK compiles it out; a hand-rolled build must too |
-
-## Debug access
-
-ESP32-C3 USB-serial-JTAG. **Board photographs exist** in
-[`artifacts/teardown/`](media.md) — unlike every other Xteink device, test points
-could in principle be identified from them. **Not attempted.**
-
-## Flashing / backup tooling
-
-| Tool | Note |
-|---|---|
-| [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher) | The best X3 tool: GUI, auto COM detect, **1:1 full-flash backup and restore in ~2 min**, ships stock images, and includes a dedicated `X3-FLASHER-GUIDE` in **both EN and CN** (13.6 KB / 16.7 KB) |
-| `crosspointreader.com` | Web flasher, unlock, flash-to-stock |
-| [`bigbag/papyrix-flasher`](https://github.com/bigbag/papyrix-flasher) | Go CLI with MD5 verification |
-
-## X3-specific projects worth reading
-
-| Project | Why |
-|---|---|
-| [`anki630/crossmosa`](https://github.com/anki630/crossmosa) + [`crossmosa-freeink-sdk`](https://github.com/anki630/crossmosa-freeink-sdk) | 繁體中文 firmware **and its own SDK fork doing "UC8279 waveform tuning"** — the only project actively working the new panel |
-| [`emezrahi/XTeink-X3-Supafast`](https://github.com/emezrahi/XTeink-X3-Supafast) | Refresh-speed work |
-| [`kocha01/xteink-x3-pokiink-fw`](https://github.com/kocha01/xteink-x3-pokiink-fw) | PokiInk fork |
-| [`sermelipharo/x3-trmnl`](https://github.com/sermelipharo/x3-trmnl) | TRMNL BYOD firmware on the CrossPoint HAL |
-| [`evanstoddard/xteink_x3_zephyr`](https://github.com/evanstoddard/xteink_x3_zephyr) | **Zephyr** — the only non-Arduino/non-IDF RTOS attempt found |
-| [`hannah-nula/crosspoint-x3-ble-page-turner`](https://github.com/hannah-nula/crosspoint-x3-ble-page-turner) | *"validated BLE page-turner reconnect support"* |
-| [`wiltodelta/xteink-sugartv`](https://github.com/wiltodelta/xteink-sugartv) | Turns an X3 into a **continuous glucose monitor display** |
-| [`ElendilDrac01/xteink-x3-calibre-stock`](https://github.com/ElendilDrac01/xteink-x3-calibre-stock) | Calibre plugin for **stock** firmware — useful if you do not want to reflash |
-
-## Related
-
-[`factory-firmware.md`](factory-firmware.md) · [`pinouts-and-buses.md`](pinouts-and-buses.md) ·
-[family command ledger](../x4-pro/commands.md)
diff --git a/devices/xteink/x3/factory-firmware.md b/devices/xteink/x3/factory-firmware.md
deleted file mode 100644
index 7c4dba2..0000000
--- a/devices/xteink/x3/factory-firmware.md
+++ /dev/null
@@ -1,152 +0,0 @@
-# Xteink X3 — factory firmware
-
-> **No X3 flash dump was obtained by this session.** Stock images are known to
-> exist publicly but are Git LFS blobs that were not fetched. Retrieved
-> **2026-09-04**.
-
-## Known stock versions
-
-From [`zocs/eink-quick-flasher/firmware/README.md`](https://github.com/zocs/eink-quick-flasher/blob/main/firmware/README.md):
-
-| File | Language | Version | Type | Size |
-|---|---|---|---|---|
-| `x3_en_v1.0.7_full.bin` | EN | **V1.0.7** | full backup | 16 MB |
-| `x3_en_v5.2.13_full.bin` | EN | **V5.2.13** | full backup | 16 MB |
-| `x3_cn_v5.2.13_full.bin` | CN | **V5.2.13** | full backup | 16 MB |
-| `x3_cn_v5.2.13_ota.bin` | CN | V5.2.13 | OTA (app only) | ~6 MB |
-
-The X3 is the **only Xteink with published full-flash images** — the X4 has only
-OTA images in that repository (plus the separate community dump this repo
-archived), and the X4 Pro and X4C have nothing.
-
-**Key fact from that README:**
-
-> "CN/EN 标注仅为默认界面语言不同，固件内容完全一致，刷入后可在设置中切换语言。"
-> *"CN/EN designation only indicates the default UI language. Firmware content is
-> identical; language can be switched in settings after flashing."*
-
-So there is **no regional firmware split** — only a default setting. A CN unit and
-an EN unit run the same code.
-
-**Not downloaded.** The `.bin` entries in the Git tree are **~130-byte Git LFS
-pointers**. Fetching the real blobs needs `git lfs` or the LFS API. Recorded as a
-gap — this is cheap to close and would give the first X3 image.
-
-## Version numbering
-
-V1.0.7 → V5.2.13 on the same device suggests either a renumbering or that V5.x is
-a shared platform version across X3 and X4 (the X4's images are `v5.1.6` and
-`v5.2.13` — **the same V5.2.13 build number appears on both devices**). That is
-consistent with one codebase serving both C3 models, exactly as the community
-firmware does.
-
-## Partition layout
-
-**Not established for the X3.** For reference, the sibling **X4** (same SoC, same
-16 MB flash) uses:
-
-`nvs` `0x9000` · `otadata` `0xE000` · `app0` `0x10000` (6400 KiB) ·
-`app1` `0x650000` (6400 KiB) · `spiffs` `0xC90000` (3456 KiB) ·
-`coredump` `0xFF0000`.
-
-**Inferred, not confirmed,** that the X3 matches. Verify before writing at offsets.
-
-## NVS
-
-The FreeInk SDK reads NVS namespace **`hw_calib`**, key **`screenType`** (u8) for
-diagnostics on the X4 family. Whether the X3 populates it is **not established**.
-Note the SDK's warning that this value is unreliable in the field on devices where
-the display bus can be probed: *"a full-flash from another unit overwrites it, so
-it can name the wrong panel."*
-
-**A practical consequence of that warning specific to this repository's users:**
-if you restore an X3 from *someone else's* `x3_*_full.bin`, you inherit their
-`hw_calib` — so a UC8253 unit can end up claiming to be a UC8279 unit. The X3's
-boot probe reads the live bus and overrides it, but a naive firmware would not.
-
-## Endpoints
-
-Recovered from the **X4** dump and reasonably assumed shared, but **not verified
-on an X3 image**:
-
-| Endpoint | Role |
-|---|---|
-| `http://gotaserver.xteink.com/api/check-update` | OTA check, plain HTTP |
-| `http://bofi.xteink.cn/index.html` | On-device web file manager |
-
-## Dump and restore
-
-```bash
-# reported-working — this is what eink-quick-flasher automates (~2 min for 16 MB)
-esptool.py --chip esp32c3 --port /dev/ttyUSB0 --baud 921600 \
-           read_flash 0 0x1000000 x3-stock-full.bin
-esptool.py --chip esp32c3 --port /dev/ttyUSB0 --baud 921600 \
-           write_flash 0 x3-stock-full.bin
-```
-
-Requires a **USB-unlocked** unit. `zocs/eink-quick-flasher` ships an
-`X3-FLASHER-GUIDE` in English and Chinese — the most detailed X3 flashing
-documentation that exists.
-
-## Artifacts held
-
-**None.** What exists and was not fetched:
-
-| Artifact | Status | Reacquisition |
-|---|---|---|
-| `x3_en_v1.0.7_full.bin` | not fetched | `manual` — Git LFS from `zocs/eink-quick-flasher` |
-| `x3_en_v5.2.13_full.bin` | not fetched | same |
-| `x3_cn_v5.2.13_full.bin` | not fetched | same |
-| `x3_cn_v5.2.13_ota.bin` | not fetched | same |
-
-Licence for all four: **none declared**; they are vendor firmware redistributed by
-a third party. Redistribution status **unknown, probably prohibited**.
-
-## Related
-
-[`development.md`](development.md) · [`../x4/factory-firmware.md`](../x4/factory-firmware.md)
-
----
-
-## Round 2 — 2026-09-11: the LFS gap is closed as an acquisition problem
-
-**No line above was altered.** The statement above — *"**Not downloaded.** The
-`.bin` entries in the Git tree are ~130-byte Git LFS pointers. Fetching the real
-blobs needs `git lfs` or the LFS API… this is cheap to close"* — was right that
-it was cheap. It is now closed **as an acquisition record**:
-
-**[`artifacts/firmware/zocs-x3-stock-images.NOT-FETCHED.md`](artifacts/firmware/zocs-x3-stock-images.NOT-FETCHED.md)**
-
-carries, for all four images, the **exact byte size and exact SHA-256** (the
-Git-LFS `oid` *is* the content SHA-256), the pinned upstream commit
-`79d2f5b8f1df08d2c8fb33146ac5f887790ddb9e`, and a **verified, unauthenticated
-download recipe that does not require `git lfs`**. The placeholder stands alone:
-a reader with neither this repository's archive nor an LFS client can reacquire
-and verify every file from it.
-
-| File | Bytes | SHA-256 |
-|---|---:|---|
-| `x3_en_v1.0.7_full.bin` | 16,777,216 | `f631402cceff2a3e39252ca1fc71afee8274b3060afe7f81d2e5dd45413c8b22` |
-| `x3_en_v5.2.13_full.bin` | 16,777,216 | `37efcb7db2422b6c7b86b23b2e82b0fb4453ebde350014e7f8e8ad3f06ca2dac` |
-| `x3_cn_v5.2.13_full.bin` | 16,777,216 | `edfe1e5eb0083b860f82281aa25391a3fdea2a598a1fb618408808a18a6ca9aa` |
-| `x3_cn_v5.2.13_ota.bin` | 6,254,064 | `0b2cbc4a6414aef4ad6e676b59fdefa3b529189758953765b26df02bac77bcb6` |
-
-**One image was actually fetched and parsed** to prove the method — the 6.25 MB
-CN OTA — and its hash matched its oid exactly. It was **not retained** (unknown
-licence, proprietary vendor firmware). What it establishes:
-
-| Field | Value |
-|---|---|
-| **`chip_id`** | **5 = ESP32-C3** — independent, machine-readable confirmation of the X3's SoC |
-| `project_name` | `arduino-lib-builder`; `idf_ver` **`v4.4.7-dirty`** |
-| Entry / segments | `0x40381E52`, 6 segments |
-| Strings | `5.2.13`, `xteink`, **`xteink_ble`** |
-
-**The X3 and X4 stock firmwares share a build base** — Arduino/ESP-IDF v4.4.7,
-exactly as this repository established by parsing the X4 dump. That is direct
-support for the "one codebase, two C3 models" reading of why `V5.2.13` appears on
-both devices.
-
-**`xteink_ble` is new.** The X3's Bluetooth capability is not characterised
-anywhere in this tree, and this is the first evidence the stock firmware carries
-a BLE component. Recorded as a gap, not a feature claim.
diff --git a/devices/xteink/x3/features/README.md b/devices/xteink/x3/features/README.md
deleted file mode 100644
index 8b1a673..0000000
--- a/devices/xteink/x3/features/README.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# Xteink X3 — feature guides
-
-| Guide | Capability | Evidence |
-|---|---|---|
-| [`display.md`](display.md) | 792×528, UC8253 **or** UC8279d | SDK; UC8279d path **unvalidated on hardware** |
-| [`imu.md`](imu.md) | QMI8658 6-axis, motion page turn | SDK + two teardowns |
-| [`rtc.md`](rtc.md) | DS-series RTC — **part unresolved** | SDK vs teardown conflict |
-| [`battery-and-power.md`](battery-and-power.md) | BQ27220 gauge, 650 mAh, pogo charging | SDK + teardown |
-| [`storage.md`](storage.md) | microSD on the shared SPI bus, with a power rail | SDK |
-| [`nfc.md`](nfc.md) | ISO 14443A tag — **purpose unknown** | Chinese teardown + vendor claim |
-| Buttons | Identical to the X4 | see [`../../x4/features/buttons.md`](../../x4/features/buttons.md) |
-| Wi-Fi / BLE | Identical SoC to the X4 | see [`../../x4/features/wifi-and-bluetooth.md`](../../x4/features/wifi-and-bluetooth.md) |
-
-**Not fitted:** touch, frontlight, audio, LEDs, SDMMC, PSRAM.
diff --git a/devices/xteink/x3/features/battery-and-power.md b/devices/xteink/x3/features/battery-and-power.md
deleted file mode 100644
index 571cf21..0000000
--- a/devices/xteink/x3/features/battery-and-power.md
+++ /dev/null
@@ -1,84 +0,0 @@
-# X3 — battery and power
-
-> **650 mAh**, a real TI fuel gauge, and pogo-pin charging. 2026-09-04.
-
-| Item | Value | Evidence |
-|---|---|---|
-| Battery | **650 mAh**, glued to the back cover, **connectorised** | **[TD]** photos 3 and 4 |
-| Fuel gauge | **TI BQ27220** @ I²C **0x55** | **[SDK]**, **[CN]** BOM |
-| Charger IC | **TP4056-class** | **[CN]** BOM — *"类似TP4056的电池管理芯片"* |
-| Charge connector | **Magnetic pogo pins**; magnets glued to the back cover | **[TD]** photo 3, **[VENDOR]** |
-| SD power rail | **GPIO13, active-HIGH** | **[SDK]**, confirmed by factory-firmware RE |
-| Device mass | **55 g** | **[VENDOR]** |
-
-## The BQ27220 — a real gauge, unlike its siblings
-
-The X3 has the best battery instrumentation in the family:
-
-| Device | Battery sensing |
-|---|---|
-| **X3** | **BQ27220** — TI impedance-track gas gauge, no profile upload needed |
-| X4 | **Bare ADC** on GPIO0 with a ÷2 divider |
-| X4 Pro / X4C | CW2017 — needs an 80-byte BATINFO profile uploaded or it reports 0 % |
-
-`GaugeType::Bq27220`: *"TI command registers, **no profile upload**"*. That makes
-it the least fragile of the three. `XteinkDetect` reads SoC from register `0x2C`
-and voltage from `0x08`.
-
-**No charger IC on the I²C bus** (`chargerAddr = 0`), so charge state is not
-readable over I²C. Unlike the X4 Pro there is also **no charge-STAT GPIO**
-declared. How the stock firmware displays charging state is **not established**.
-
-## The SD power rail — and why it exists
-
-```
-setup():      digitalWrite(13, HIGH)   // power the card
-deep sleep:   digitalWrite(13, LOW)    // cut it
-```
-
-Confirmed by X3 factory-firmware reverse engineering. The SDK spells out the
-consequence of omitting it:
-
-> "Without declaring it, `powerDownRailsForSleep()` has no X3 SD enable to cut, so
-> **the card stays powered through sleep → battery drain.**"
-
-**Polarity trap:** GPIO13 is **active-HIGH** here. The X4 Pro's SD enable (GPIO5)
-and the X4 Classic's (GPIO6) are **active-LOW**. And on the [X4](../../x4/features/battery-and-power.md),
-GPIO13 is the **battery MOSFET latch** — driving it LOW powers the device off.
-**The same pin number means three different things across the family.**
-
-## Pogo charging
-
-The magnets and the pogo pads are **glued to the back cover**, not part of the
-PCB — the PCB has silkscreened keep-out areas where the magnets sit
-(**[TD]** photo 12). That is a deliberate mechanical design, not an afterthought.
-
-Required accessories, sold separately (2026-09-04):
-Magnetic Pogo Pin Charging Cable **$4.99**; Magnetic Charging Adapter **$5.99**.
-
-## The unmeasured measurement
-
-The teardown author's stated purpose was to attach a **Nordic Power Profiler
-Kit II** *"to see if I can make any power optimizations to crosspoint firmware"*.
-
-**No results were ever posted.** This is the closest anyone has come to measuring
-power on any Xteink device, and it produced nothing. Runtime, sleep current and
-active draw are all **unknown**.
-
-## Mechanical fragility
-
-An owner reports the **rear glass cracking**:
-
-> "My glass cracked a bit on the rear side. So it might not have happened if I had
-> black x3."
-> — [r/xteinkereader `1w56phf`](https://old.reddit.com/r/xteinkereader/comments/1w56phf/), 2026-09-02
-
-The same post asks which models have **metal backing** rather than glass and
-**received no authoritative answer**. The teardown confirms the back is glass and
-comes off with a heat gun and suction cup — so replacement is feasible, but no
-part source is known.
-
-## Status
-
-`hardware-confirmed` for capacity, gauge and SD rail. `unknown` for charger part,
-charge-state signalling, runtime and all current draw.
diff --git a/devices/xteink/x3/features/display.md b/devices/xteink/x3/features/display.md
deleted file mode 100644
index 731682f..0000000
--- a/devices/xteink/x3/features/display.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# X3 — display
-
-> **792 × 528**, 3.7″, **~257 PPI** — the highest pixel density in the family.
-> Two possible controllers. 2026-09-04.
-
-| Property | Value |
-|---|---|
-| Resolution | **792 × 528** |
-| Diagonal / PPI | 3.7″ / **~257** (√(792²+528²)=951.7 px ÷ 3.7) |
-| Depth | 1 bpp; **4-level AA path exists on the UC8253 only** |
-| Controller | **UC8253** (original) or **UC8279d** (from ~July 2026) |
-| Bus | SPI shared with the SD card — SCLK 8 / MOSI 10 / CS 21 / DC 4 / RST 5 / BUSY 6 |
-| Clock | **20 MHz** — UC8253 and UC8279 datasheet maximum |
-
-Vendor claim *"over 250 PPI"* and the arithmetic agree — two independent
-confirmations.
-
-## Which controller, and how it is chosen
-
-`detectX3DisplayController()` bit-bangs a half-duplex read of UC8279
-**`VER (0x70)`** and **`FLG (0x71)`** after a reset pulse. Match requires a leading
-`0x00`, a non-floating `CHIP_VER`, and `FLG` idle with `BUSY_N = 1` — **in two
-passes agreeing byte-for-byte**. Anything else conservatively falls back to the
-shipping **UC8253**.
-
-**Two things the SDK admits it does not know** (both marked `Pending`):
-1. **What the UC8253 actually answers to `0x70`.** The matcher relies on the
-   UC815x-family REV placing the revision in the first byte — that is an
-   assumption about the *other* part.
-2. **Whether production MTP programs `CHIP_VER` to something other than `0x03`.**
-   The matcher deliberately does not pin the value, having been burnt on the X4
-   Pro where a shipping unit returned `CHIP_VER = 0x00`.
-
-## The UC8279d driver is unvalidated
-
-Quoted, because it is the most important caveat on this device:
-
-> "Everything below is written from the UC8279d_B 0.1 datasheet (Dec 2025) and is
-> **Pending hardware validation — no UC8279 X3 unit has been on the bench yet.**"
-> — **[SDK]** `docs/xteink-x3-uc8279-support.md:13–14`
-
-Consequences, all pending bench tuning:
-
-- **Full / Half / Fast currently run the same OTP waveform** — likely a full
-  GC-style flash on **every page turn**. Fast turns need custom register banks
-  (`REG=1`, commands `0x20`–`0x24`).
-- **The X3's six tuned UC8253 waveform banks cannot be copied over.** The UC8279
-  LUT format is **group-based** (7-byte groups, 7 groups per LUT in KW mode), not
-  the UC8253's 43-byte format. A porting effort, not a copy.
-- **No grayscale** on UC8279 (`supportsStripGrayscale()` false). The 4-level AA
-  path the X3 reader uses needs UC8279-format gray banks tuned on hardware.
-- `TRES` is programmed 792×528, but the UC8253 init programs **VRES = 600**
-  (the OEM scans the full gate count). If the image is offset or compressed, the
-  SDK suggests trying `0x02 0x58`.
-- `CDI` default drives the border white each refresh (`0x97`); the datasheet
-  default (`0xD7`) floats it.
-
-**Practical reading:** if you have a newer X3, expect worse page-turn behaviour
-than an older one until someone tunes waveforms. `anki630/crossmosa-freeink-sdk`
-is the only project found doing that work.
-
-## UC8253 driver
-
-KW mode (`PSR KW/R = 1`): 1 bpp, `DTM1` = OLD plane, `DTM2` = NEW plane,
-differential refresh. Command set: `PSR`/`PON`/`POF`, `DTM1 0x10`, `DSP 0x11`,
-`DRF 0x12`, `DTM2 0x13`, `CDI 0x50`, `TRES 0x61`, `DSLP 0x07`+`0xA5`.
-
-The UC8279 driver uses a *near-identical* command set — which is why the port
-looks deceptively easy and is not.
-
-## Factory OTP waveforms
-
-v1 uses `PSR REG = 0`: the **4K MTP carries 12 temperature-range LUT sets**, each
-with its own frame rate and rail voltages, and **`TS_AUTO` re-senses temperature
-before every booster enable**. So PWR/PLL/VDCS stay at silicon defaults and every
-refresh is temperature-compensated **by the controller**, not the host.
-
-That is a real advantage over host-authored waveforms and is worth knowing before
-replacing them.
-
-## UC8279 features not wired up
-
-`AUTO (0x17)` — `PON→DRF→POF(→DSLP)` as one command, saving host round-trips on
-sleepy updates. `PBC (0x44)` — panel-break check via the CHKGI/CHKGO loop, if the
-module bonds it. `CRC (0x72)` — MTP integrity check over `0x000–0xFFF`.
-`TSC (0x40)` — on-chip temperature readback.
-
-## Status
-
-`reported-working` for UC8253. **`not-tested` for UC8279d** — datasheet-derived
-only.
diff --git a/devices/xteink/x3/features/imu.md b/devices/xteink/x3/features/imu.md
deleted file mode 100644
index afe7d60..0000000
--- a/devices/xteink/x3/features/imu.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# X3 — IMU (QMI8658)
-
-> Six-axis accelerometer + gyroscope. Powers the advertised **motion-based page
-> turning**. 2026-09-04.
-
-| Property | Value |
-|---|---|
-| Part | **QMI8658** — [`qst/qmi8658a`](../../../../components/qst/qmi8658a/README.md) |
-| Address | **0x6B**, alternate **0x6A** |
-| Bus | I²C SDA **20** / SCL **0** @ 400 kHz |
-| `WHO_AM_I` | register `0x00` == **`0x05`** |
-| Interrupt line | **none** — polled |
-| SDK type | `ImuType::Qmi8658` |
-
-## Corroboration
-
-Three independent sources agree:
-
-1. **[SDK]** `BoardConfig.h:915` — `ImuType::Qmi8658`, address 0x6B
-2. **[SDK]** `XteinkDetect.cpp` — used as an X3-detection fingerprint, checking
-   `WHO_AM_I == 0x05`
-3. **[CN]** `sunwoods/Xteink-X3` BOM — *"QMI8658 姿态传感器"* (attitude sensor)
-
-This is one of the few parts in the whole family confirmed by both firmware and a
-physical teardown.
-
-## What it is used for
-
-The vendor's X3 launch announcement lists *"Built-in **gyroscope** for
-motion-based page turning"* — [r/xteinkereader `1pi6ezd`](https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/),
-2025-12-09. That is a stock-firmware feature.
-
-Whether any community firmware implements it was **not established**.
-
-## Role as a device fingerprint
-
-`XteinkDetect::detectXteinkVerdict()` scores the presence of the QMI8658 (0x6B),
-BQ27220 (0x55) and DS-series RTC (0x68) on SDA20/SCL0. **Finding them means X3;
-finding nothing means X4.** So the IMU is load-bearing for correct board
-selection, not just a feature.
-
-## Limits
-
-- **No interrupt pin**, so wake-on-motion is not available — the part must be
-  polled, which costs power.
-- Shares one I²C bus with the gauge and RTC.
-- No ODR, range or noise figures were measured or reported for this board.
-
-## Cross-device note
-
-The **X4 Classic** also carries a QMI8658 at 0x6B with the same no-interrupt
-arrangement. The **X4 Pro has no IMU at all**, and neither does the X4.
-
-## Status
-
-`hardware-confirmed` for presence and address (firmware + teardown).
-`not-tested` for any performance property.
diff --git a/devices/xteink/x3/features/nfc.md b/devices/xteink/x3/features/nfc.md
deleted file mode 100644
index c0958fe..0000000
--- a/devices/xteink/x3/features/nfc.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# X3 — NFC
-
-> **An ISO/IEC 14443A tag is on the board. Nobody has explained what it does.**
-> This is the largest unexplained hardware feature in the entire Xteink family.
-> 2026-09-04.
-
-## What is established
-
-| Fact | Source |
-|---|---|
-| An **ISO/IEC 14443A NFC Tag** is fitted | **[CN]** [`sunwoods/Xteink-X3`](https://github.com/sunwoods/Xteink-X3) BOM — listed as `***ISO/IEC 14443a NFC Tag`, asterisked by the author as notable |
-| **"NFC support"** is an advertised X3 feature | **[VENDOR]** launch announcement, [r/xteinkereader `1pi6ezd`](https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/) and [`1pjw3ay`](https://old.reddit.com/r/xteinkereader/comments/1pjw3ay/), 2025-12-09/11 |
-
-Component record:
-[`unidentified/xteink-x3-x4/nfc-tag-iso14443a`](../../../../components/unidentified/xteink-x3-x4/nfc-tag-iso14443a/README.md)
-
-## What is not established — which is almost everything
-
-- **The part number.** Unknown.
-- **Whether it is a passive tag or a reader/writer.** The Chinese BOM says *"Tag"*,
-  which implies **passive** — an NFC tag the *phone* reads, not a reader the device
-  uses.
-- **What it is connected to.** It appears in **no** board profile, **no** firmware
-  string, **no** driver, and on **no** host bus in the FreeInk SDK. If it is a
-  passive tag with no I²C interface, that is expected — but it also means firmware
-  cannot use it.
-- **What it is for.** Entirely unknown.
-
-## Candidate explanations — all speculation, none supported
-
-| Hypothesis | Argument for | Argument against |
-|---|---|---|
-| **Phone hand-off** — tap the reader to open the web file manager | The stock firmware serves `http://bofi.xteink.cn/index.html?ip=` — an NFC tag encoding that URL would be a neat pairing gesture | No evidence anyone has observed this |
-| **Case / accessory identification** | The X3 has a strong magnetic-accessory ecosystem | A passive tag on the *device* cannot identify an accessory |
-| **Authenticity / anti-counterfeit** | Common in Shenzhen consumer hardware | No vendor statement |
-| **Manufacturing / QC marker** | Plausible for line tracking | Would not be advertised as a user feature — and it **was** advertised |
-
-The vendor advertising it as a user-facing feature argues against the purely
-internal explanations, and for something a phone interacts with.
-
-## Why no one has investigated
-
-Every community firmware replaces the stock application entirely, and the tag is
-invisible to firmware. The people who could answer this — stock-firmware users
-with an NFC-capable phone — are the least likely to be writing hardware notes.
-
-## How to resolve it, cheaply
-
-**Tap an NFC-capable phone against an X3 and read the tag.** Any NFC-reader app
-will dump the NDEF payload. This is a five-minute experiment that nobody appears
-to have performed, and it would resolve the question completely.
-
-Secondarily: examine the archived teardown photographs
-([`../media.md`](../media.md)) for an antenna coil trace, which would confirm the
-tag is passive and show where it sits.
-
-## Cross-device
-
-Neither the X4, the X4 Pro nor the X4 Classic has NFC. **The X3 is the only
-Xteink device with it.**
-
-## Status
-
-**`unknown`.** Presence: two independent sources. Function: no evidence at all.
diff --git a/devices/xteink/x3/features/rtc.md b/devices/xteink/x3/features/rtc.md
deleted file mode 100644
index b437757..0000000
--- a/devices/xteink/x3/features/rtc.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# X3 — real-time clock
-
-> **The part is not established.** Three sources give three answers, all at I²C
-> address 0x68. 2026-09-04.
-
-| Property | Value |
-|---|---|
-| Address | **0x68** |
-| Bus | I²C SDA **20** / SCL **0** @ 400 kHz |
-| SDK type | `RtcType::Ds3231` |
-| Component record | [`unidentified/xteink-x3-x4/rtc-ds-series`](../../../../components/unidentified/xteink-x3-x4/rtc-ds-series/README.md) |
-
-## The conflict
-
-| Source | Claim |
-|---|---|
-| FreeInk SDK `BoardConfig.h:915` | **DS3231** |
-| Imgur teardown, image 13 caption | **"DS1307 RTC"** |
-| `sunwoods/Xteink-X3` BOM | **"DS系列RTC时钟芯片"** — *DS-series*, unnarrowed |
-
-**The address does not discriminate**: the DS1307 and DS3231 both live at 0x68.
-
-**And the firmware does not either.** `XteinkDetect` probes only
-`DS3231_SEC_REG = 0x00` — the seconds register — which is **identical on both
-parts**. So the SDK's `Ds3231` label is an assumption that has never been
-falsified by the code that appears to test it.
-
-## Why it matters
-
-| | DS1307 | DS3231 |
-|---|---|---|
-| Timekeeping registers | same layout at 0x00–0x06 | same |
-| Accuracy | External crystal, **no compensation** | **Integrated TCXO**, ±2 ppm |
-| Temperature registers | **none** | `0x11`/`0x12` |
-| Alarms | none | two |
-| Nominal supply | 5 V part | 2.3–5.5 V |
-
-Drift on an e-reader that shows a clock is a user-visible difference. Alarms and
-temperature readback are simply absent on one of them.
-
-## How to resolve it
-
-**Read registers `0x11` and `0x12`.** The DS3231 returns a temperature there; the
-DS1307 does not implement them. One I²C read settles it.
-
-Alternatively, a legible photograph of the chip's top marking. The existing
-teardown photo (`13-Ay3rpJg.jpg`, 5760×3240) is archived in this repository and
-**has not been examined at full resolution** — the caption may or may not be
-supported by the image.
-
-## Cross-device note
-
-The S3 devices — [X4 Pro](../../x4-pro/features/rtc.md) and X4 Classic — use a
-**BM8563 at 0x51**, a completely different part at a different address. The
-[X4](../../x4/README.md) has **no RTC at all**.
-
-## Status
-
-**`unresolved`.** Presence and address confirmed; **part identity is not**.
diff --git a/devices/xteink/x3/features/storage.md b/devices/xteink/x3/features/storage.md
deleted file mode 100644
index 8c32e2f..0000000
--- a/devices/xteink/x3/features/storage.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# X3 — microSD storage
-
-> SPI, shared with the display — **but with a power rail the X4 lacks.**
-> 2026-09-04.
-
-| Signal | GPIO |
-|---|---:|
-| SCLK | **8** (shared with EPD) |
-| MOSI | **10** (shared with EPD) |
-| MISO | **7** |
-| CS | **12** |
-| **powerEnable** | **13**, **active-HIGH** |
-
-`separateSpi = false`, `spiHz = 0` → SD manager default. Driver: SdFat.
-
-## The power rail is the X3's advantage
-
-```
-setup():     digitalWrite(13, HIGH)
-deep sleep:  digitalWrite(13, LOW)
-```
-
-Confirmed by factory-firmware reverse engineering. The [X4](../../x4/features/storage.md)
-has **no SD enable at all**, so its card stays powered through sleep. On the X3 you
-can cut it — and if your firmware does not declare the rail, you lose that.
-
-**Polarity:** active-HIGH here; **active-LOW** on both S3 devices. Do not port.
-
-## Bus contention
-
-Panel and card share SCLK 8 / MOSI 10, separated only by chip select. A large card
-transfer stalls display refresh. This is structural on both C3 devices and is the
-main architectural reason the S3 models moved to a dedicated SDMMC slot.
-
-## Not established
-
-Maximum card capacity, filesystem constraints, and whether the stock firmware
-formats or requires a particular partition scheme. There is a Calibre plugin for
-**stock**-firmware X3 cards ([`ElendilDrac01/xteink-x3-calibre-stock`](https://github.com/ElendilDrac01/xteink-x3-calibre-stock))
-and one for CrossPoint-formatted cards
-([`yemM/crosspoint-reader-sd-calibre-plugins`](https://github.com/yemM/crosspoint-reader-sd-calibre-plugins)),
-which implies the two layouts differ — **not confirmed**.
-
-## Status
-
-`reported-working`.
diff --git a/devices/xteink/x3/gaps-and-conflicts.md b/devices/xteink/x3/gaps-and-conflicts.md
deleted file mode 100644
index 92b3388..0000000
--- a/devices/xteink/x3/gaps-and-conflicts.md
+++ /dev/null
@@ -1,143 +0,0 @@
-# Xteink X3 — gaps and conflicts
-
-Snapshot **2026-09-04**.
-
-## Conflict 1 — the RTC part. Three sources, three answers.
-
-| Source | Class | Claim |
-|---|---|---|
-| FreeInk SDK `BoardConfig.h:915` | firmware, driven in production | **`RtcType::Ds3231`** at **0x68** |
-| Imgur teardown, image 13 caption | firsthand photograph of the marking | **"DS1307 RTC"** |
-| `sunwoods/Xteink-X3` BOM | firsthand teardown, Chinese | **"DS系列RTC时钟芯片"** — *DS-series*, deliberately unnarrowed |
-
-**All three are consistent with I²C address 0x68**, which both the DS1307 and the
-DS3231 use — so the address does not discriminate.
-
-**Why this is not trivially resolved:**
-- The DS1307 and DS3231 have **different register maps beyond the timekeeping
-  bytes** and different supply requirements (the DS1307 is nominally a 5 V part;
-  the DS3231 has an integrated TCXO). Getting it wrong affects accuracy and any
-  use of alarms or the temperature register.
-- A firmware driver working does **not** prove the part: `XteinkDetect` only reads
-  `DS3231_SEC_REG = 0x00`, the seconds register, which is **identical on both**.
-  So the SDK's `Ds3231` label may itself be an assumption that has never been
-  falsified.
-- The Chinese author explicitly **refused to narrow it**, which is the behaviour of
-  someone who looked at the marking and could not read it confidently.
-
-**Status: unresolved.** The component is filed as
-[`components/unidentified/xteink-x3-x4/rtc-ds-series/`](../../../components/unidentified/xteink-x3-x4/rtc-ds-series/README.md)
-rather than under Maxim/Analog Devices, per the skill's rule against promoting a
-candidate to a finding.
-
-**What would settle it:** a legible photograph of the chip's top marking, or
-reading register `0x11`/`0x12` — the DS3231's temperature registers, which the
-DS1307 does not have.
-
-## Conflict 2 — GPIO0 and GPIO20 are each assigned twice
-
-| Pin | Assignment A | Assignment B |
-|---:|---|---|
-| **0** | `batteryAdc = 0` | `X3_I2C_SCL = 0` |
-| **20** | `usbDetect = 20` | `X3_I2C_SDA = 20` |
-
-Same SDK, same commit. Both pairs cannot be live.
-
-**Hypothesis (not a finding):** `batteryAdc` and `usbDetect` were copied from the
-X4 profile and are dead here — the X3 has a **BQ27220 gauge** and does not need an
-ADC battery sense.
-
-**What would settle it:** the schematic sketch at
-`artifacts/teardown/sunwoods-cn/02.jpg`, **which is held in this repository and has
-not been read.** This is the cheapest unresolved question in the whole subject.
-
-## Conflict 3 — the vendor's product page describes features the device lacks
-
-The `xteink.com` X3 listing claims *"adjustable warm light settings"* and
-*"Cloud sync"*. **The X3 has no frontlight** — `NO_FRONTLIGHT` in the board
-profile, no frontlight in either teardown, and the X4 Pro is the only Xteink with
-one. The copy is AI/SEO boilerplate.
-
-Recorded prominently because it is the justification for the rule applied across
-this whole tree: **no vendor prose is used as evidence.**
-
-## Conflict 4 — community price
-
-A community post lists the X3 at **$79** ([r/XTEINK `1v5gh6x`](https://old.reddit.com/r/XTEINK/comments/1v5gh6x/),
-2026-07-24) while the vendor API shows **$69.00** on 2026-09-04. Could be a price
-cut, or an error. Not resolved.
-
-## Unresolved identities
-
-| Part | Known | Missing |
-|---|---|---|
-| **ESP32-C3 variant** | Family only, from two teardowns | Exact package/suffix. **No part number asserted** |
-| **Puya flash** | *"PUYA 128Mbit"* | Part number |
-| **Charger IC** | *"TP4056-class"* | Actual part |
-| **NFC tag IC** | *"ISO/IEC 14443A tag"* | Part, and **what it is for** |
-| **Panel module** | Controller only (UC8253 / UC8279d) | Module/glass part number, supplier |
-| **Battery cell** | **650 mAh**, connectorised | Cell part/format |
-
-## The NFC tag — the largest open question about this device
-
-An **ISO/IEC 14443A tag** is on the board and NFC is an advertised feature. But:
-
-- It appears in **no** board profile, **no** firmware string, and **no** driver.
-- It is a **passive tag** — nothing on the host bus.
-- **Nobody has explained what it does.** Candidate uses: accessory/case
-  identification, authenticity, or a "tap to open the file manager" phone hand-off.
-  All speculation.
-
-Not a single English-language source discusses it. See [`features/nfc.md`](features/nfc.md).
-
-## Gaps — firmware
-
-| Item | Status |
-|---|---|
-| Stock X3 images V1.0.7 / V5.2.13 (CN+EN, full **and** OTA) | Exist as **Git LFS blobs** in `zocs/eink-quick-flasher`; **not fetched** |
-| An X3 flash dump | **Not obtained.** Only the X4's was |
-| SPIFFS contents | Not extracted |
-| **UC8279d variant** | *"Pending hardware validation — no UC8279 X3 unit has been on the bench yet"* |
-
-## Gaps — measurement
-
-**No power measurement exists**, despite the teardown being performed expressly to
-make one. No runtime, no sleep current, no refresh timing for the UC8253.
-
-## Gaps — regulatory
-
-No FCC ID, CE or SRRC record read. **Board photographs now exist in this
-repository**, so unlike the other models an FCC/SRRC ID could plausibly be **read
-off the PCB silkscreen** — an unexplored, cheap avenue.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 109:* No FCC ID, CE or SRRC record read. **Board photographs now exist in this
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x3/market-and-pricing.md b/devices/xteink/x3/market-and-pricing.md
deleted file mode 100644
index ecc4ab1..0000000
--- a/devices/xteink/x3/market-and-pricing.md
+++ /dev/null
@@ -1,110 +0,0 @@
-# Xteink X3 — market and pricing
-
-## Current — observed 2026-09-04
-
-Source: `https://www.xteink.com/products.json?limit=250`, retrieved 2026-09-04.
-Item price only; shipping, tax and duty excluded. Ships from Shenzhen worldwide.
-
-| Item | Variant | Price | Stock |
-|---|---|---|---|
-| **Xteink X3 Pocket eReader** | **Mist Gray** (`xteink-x3-white-1`) | **$69.00** | ✅ |
-| **Xteink X3 Pocket eReader** | **Space Black** (`xteink-x3-black-1`) | **$69.00** | ✅ |
-| X3 Magnetic Case | 6 colours | $8.99 | 5/6; **Space Black sold out** |
-| X3 Protective Case | Mist Gray / Mist White | $3.99 | ✅ both |
-| X3 Tempered Glass Protector | 1 / 2 / 3-pack | $4.99 / $7.99 / $9.99 | ✅ all |
-| X3 Matte Screen Protector | 2 / 4 / 6-pack | $3.99 / $5.99 / $8.39 | ✅ all |
-| Magnetic Pogo Pin Charging Cable | — | $4.99 | ✅ |
-| Magnetic Charging Adapter | — | $5.99 | ✅ |
-| eReader Magnetic Reading Light | single / dual | $9.99 / $15.99 | ✅ |
-
-**The X3's accessory supply is materially healthier than the X4 Pro's** (where all
-matte protectors and two of three glass packs are sold out) and incomparably
-healthier than the X4's (**everything** sold out).
-
-**Realistic entry price:** $69 + $4.99 spare pogo cable ≈ **$74**, or ~**$78**
-with a case.
-
-Note the **eReader Magnetic Reading Light** ($9.99) — an external clip-on light.
-It exists because **the X3 has no frontlight**, and it is the vendor's own
-acknowledgement of that, in the same catalogue whose X3 description claims
-"adjustable warm light settings".
-
-## Launch pricing and terms
-
-| Date | Event |
-|---|---|
-| 2025-12-11 | Pre-orders open. **"Super Early Bird" units are non-refundable** |
-| 2026-02-05 | Shipping begins — an **8-week** pre-order-to-ship gap |
-| 2026-06-20 | **20 % off** sale on X3/X4 via the CrossPoint affiliate link — *"the best deal I've seen so far"* |
-| 2026-09-04 | $69.00, both colours in stock |
-
-## Conflicting community price
-
-[r/XTEINK `1v5gh6x`](https://old.reddit.com/r/XTEINK/comments/1v5gh6x/) (2026-07-24)
-lists *"$69 X4, **$79 X3**, $99 X4 Pro"* — the X3 figure **contradicts** the vendor
-API's $69.00 and the ordering is reversed from expectation. Either a price cut
-between July and September, or an error in the post. **Unresolved.**
-
-## Secondhand
-
-One observation: **$16**, 2026-08-18
-([r/XTEINK `1vrnxnq`](https://old.reddit.com/r/XTEINK/comments/1vrnxnq/)),
-described as *"dirt cheap"*, channel not stated, condition not stated.
-
-**A single anecdote.** It is not merged with new pricing and does not establish a
-used-market range. It does suggest the used market for these is soft — the same
-poster's substantive complaint was about vendor conduct, not the device.
-
-## Chinese market
-
-**Not captured.** The vendor is China-first and Chinese pricing is announced on
-Xiaohongshu (RedNote), which was not searched. For scale, the **S4** was announced
-at **¥299 / ¥339** (≈US$45–50), which suggests domestic prices run well below the
-international store's USD figures.
-
-## Channel and warranty
-
-Vendor-direct only. Note the catalogue's service SKUs: `$50 After-sale`,
-`After-sales Fees`, `Exchange Handling Fees`, `Handling Fees`, `Shipping fee`.
-**After-sales service is a paid product.** Budget for it rather than assuming
-warranty coverage — particularly given the rear-glass fragility report.
-
-## Caveats
-
-- Item prices only; **shipping, tax and duty not captured**.
-- Stock is a single-instant snapshot.
-- The $16 figure is one anecdote with unknown channel and condition.
-- No Chinese-market price captured.
-
----
-
-## Dated observation — 2026-09-11, vendor store
-
-Source: **`https://xteink.com/products.json?limit=250&page=1`**, retrieved **2026-09-11** by the
-certification/market pass. Full catalogue enumerated: **25 products**. Currency USD as served, no
-conversion applied. Condition: new, genuine (manufacturer store). Ships from: **not stated by the
-endpoint**. Item price only — shipping, tax and duty not captured.
-
-| Product | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| Xteink X3 Pocket eReader | 2025-12-11 | X3 Mist Gray | `xteink-x3-white` | **USD 69.00** | ✅ |
-| Xteink X3 Pocket eReader | 2025-12-11 | X3 Space Black | `xteink-x3-black` | **USD 69.00** | ✅ |
-| Xteink X3 Pocket eReader | 2025-12-11 | X3 + Mist Gray Base | `xteink-x3B+BW` | **USD 85.00** | ✅ |
-| Xteink X3 Pocket eReader | 2025-12-11 | X3 + Space Black Base | `X3W+BB` | **USD 85.00** | ✅ |
-
-Citation form per [`guides/markets/vendor-comparison.md`](../../../guides/markets/vendor-comparison.md) § *A note on prices*:
-
-> *USD 69.00, 1 unit, retrieved 2026-09-11, `https://xteink.com/products/xteink-x3-pocket-ereader`, ships from CN (origin not stated by vendor)*
-
-**USD 69.00 is unchanged from the 2026-09-04 observation** — two independent reads of the same
-endpoint, one week apart, identical. The community figure of $79 recorded elsewhere in this file
-remains in conflict with the vendor API and is **not** resolved by this observation.
-
-⚠ **Not obtained:** AliExpress, Amazon, eBay, Taobao, JD and used/refurbished were **all blocked
-or JS-shelled** from the research host on 2026-09-11. **No street, clone or used price is
-reported here, because none was observed.** A 200 response containing no prices is a failure, not
-a data point.
-
-⚠ Six **service** line-items in the catalogue (handling fees, shipping fee, after-sale charges)
-are **not products** and must be excluded from any price range — a naive "cheapest item in the
-store" read returns USD 1.00.
diff --git a/devices/xteink/x3/media.md b/devices/xteink/x3/media.md
deleted file mode 100644
index 8d5146b..0000000
--- a/devices/xteink/x3/media.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Xteink X3 — images and teardown views
-
-**The X3 is the only Xteink device with public teardowns — and it has two,
-independent, in different languages.** Both are archived with placeholders.
-
-## Teardown A — English, 13 photos, Imgur
-
-| Field | Value |
-|---|---|
-| Author | Reddit user, posted to r/xteinkereader |
-| Source post | <https://old.reddit.com/r/xteinkereader/comments/1uksv6s/xteink_x3_teardown/> |
-| Album | <https://imgur.com/a/xteink-x3-teardown-OA6CS2C> |
-| Date | **2026-07-01** (Imgur per-image timestamp 17:44:53) |
-| Images | **13**, up to 5760 × 3240 |
-| Local | [`artifacts/teardown/imgur-2026-07-01/`](artifacts/teardown/imgur-2026-07-01.ARCHIVED.md) — archived, 18.61 MiB |
-| Rights | **Unknown** — no terms stated. Unstaged pending review |
-| Stated purpose | Attach a **Nordic Power Profiler Kit II** *"to see if I can make any power optimizations to crosspoint firmware"* |
-
-### What each image establishes
-
-| # | Hash | Author's caption | What it establishes |
-|---:|---|---|---|
-| 1 | `u60Rtxi` | *"The glass back came off pretty easily with a heatgun, suction-cup, and a plastic spudger."* | **Glass back**, adhesive-mounted, serviceable |
-| 3 | `Q5jsUoi` | *"The **650mAh battery** is glued to the back. So are the **magnets for the pogo connector**."* | **Battery capacity** and that the pogo magnets are glued, not soldered |
-| 4 | `WAlvma8` | *"battery connector"* | The cell is connectorised, not soldered — replaceable in principle |
-| 5 | `lBJtD4I` | *"The eink display is a little transparent."* | Panel construction |
-| 6 | `pcqe4Q0` | *"Back of device."* | — |
-| 7 | `QQz92jU` | *"Main PCB"* | Single-board construction |
-| 9 | `Q0UGXpo` | *"bad overview of the esp32-c3"* | **SoC family** |
-| 10 | `YgdHbR1` | *"…ESP32-C3 main CPU. **128MBit (16MB) flash for firmware**."* | SoC + **external flash size** |
-| 12 | `wKlM8uS` | *"Silkscreened off areas of the PCB is where the magnets are on the back plate."* | Magnet keep-outs designed into the PCB |
-| 13 | `Ay3rpJg` | ***"DS1307 RTC"*** | **The RTC conflict** — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-
-Per-image SHA-256 values are in the placeholder's Contents table and in
-`manifest.json` inside the archived directory.
-
-**Retrieval note.** `imgur.com/a/<id>` is a JavaScript shell that yields **2 of 13**
-images when scraped. Use
-`https://imgur.com/ajaxalbums/getimages/OA6CS2C/hit.json` to enumerate hashes and
-captions, then fetch `https://i.imgur.com/<hash>.jpg`.
-
-## Teardown B — Chinese, 10 photos **including a schematic**
-
-| Field | Value |
-|---|---|
-| Author | GitHub user `sunwoods` |
-| Repository | <https://github.com/sunwoods/Xteink-X3> — 收集关于阅星瞳X3的软硬件信息 |
-| Local | [`artifacts/teardown/sunwoods-cn/`](artifacts/teardown/sunwoods-cn.ARCHIVED.md) — archived, 4.80 MiB |
-| Rights | **None declared** — no LICENSE file. Unstaged pending review |
-
-| File | Content |
-|---|---|
-| `01.jpg` | Opened device overview (拆开后的样子) |
-| **`02.jpg`** | **Hand-drawn schematic sketch (原理图示意)** — the only schematic-like document for *any* Xteink device |
-| `03.jpg`, `04.jpg` | **Annotated functional-block overlays** (功能模块标记) |
-| `05`–`10.jpg` | Chip-marking close-ups (细节放大) |
-| `README.upstream.md` | The BOM list, preserved |
-
-**Schematic caveat, stated upstream:** 部分器件用其他类似封装替代 — *"some
-components are substituted with other similar footprints"*. It is a functional
-sketch, **not fabrication-accurate**.
-
-### The BOM this teardown gives
-
-- ESP32-C3
-- **PUYA 128 Mbit Flash**
-- **QMI8658** attitude sensor
-- **DS系列RTC时钟芯片** — "DS-series RTC clock chip" (**deliberately not narrowed**)
-- **类似TP4056的电池管理芯片** — "a TP4056-like battery-management chip"
-- **TI BQ27220 库仑计** — coulomb counter
-- ***ISO/IEC 14443a NFC Tag** — marked with asterisks by the author, i.e. flagged
-  as notable
-
-**The NFC tag appears in no firmware, no board profile and no English-language
-source.** This teardown is the only technical evidence it exists, corroborated
-only by the vendor's launch bullet *"NFC support"*.
-
-## Why two teardowns matter more than one
-
-They agree independently on the ESP32-C3, the 128 Mbit flash and the general
-construction — and they **disagree, usefully, on the RTC**: the English author
-reads a specific `DS1307` marking, the Chinese author declines to narrow past
-"DS-series", and the FreeInk SDK drives a `DS3231`. Three sources, three
-positions, one address (0x68). That disagreement is preserved rather than
-resolved.
-
-## What is still missing
-
-- **No X3 Pro/variant photography** distinguishing the UC8253 and UC8279d batches.
-- **No photograph of the panel's own FPC marking**, which would give the module
-  part number.
-- **The schematic sketch has not been read in detail.** It is held here and could
-  resolve the GPIO0/GPIO20 dual-assignment conflict. Cheapest open action.
-- Vendor product imagery not archived (the listing is live; URLs are in
-  `scratch/xteink/vendor/products-p1.json`).
diff --git a/devices/xteink/x3/performance.md b/devices/xteink/x3/performance.md
deleted file mode 100644
index d4e8050..0000000
--- a/devices/xteink/x3/performance.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Xteink X3 — performance
-
-> **Nothing was measured — by this session, or by anyone.** Retrieved
-> **2026-09-04**. This page mostly documents an absence, and one attempt that
-> failed to produce results.
-
-## Established figures
-
-| Quantity | Value | Status |
-|---|---:|---|
-| Display SPI clock | **20 MHz** — UC8253 datasheet maximum (*"Clock rate up to 20 MHz"*, serial write timing `TSCYCW`); UC8279 rated the same | in-spec, developer-chosen |
-| Prior fork clock (Witch Reader) | 16 MHz | ~25 % slower on plane writes |
-| Battery capacity | **650 mAh** | teardown photograph caption, **single source** |
-| Device mass | **55 g** | vendor announcement |
-| Pixel density | **~257 PPI** | arithmetic: √(792²+528²) = 951.7 px ÷ 3.7″; vendor claims *"over 250 PPI"* |
-
-**No plane-write timing exists for the X3.** The ~38 ms/~19 ms figures in this
-tree are for the **X4's SSD1677 at 800×480**, a different controller and a
-different panel. They are **not** transferable — the X3 has 21 % more pixels
-(418,176 vs 384,000) and a different command family.
-
-## The measurement that was attempted and abandoned
-
-The X3 teardown was performed **expressly to instrument power**:
-
-> "…so I can attach a **Nordic Power Profiler Kit II** to it to see if I can make
-> any power optimizations to crosspoint firmware."
-> — [r/xteinkereader `1uksv6s`](https://old.reddit.com/r/xteinkereader/comments/1uksv6s/), 2026-07-01
-
-**No results were ever posted.** This is the closest anyone has come to measuring
-any Xteink device, and it produced nothing. Recorded so the next person knows the
-attempt was made and where it stopped.
-
-## The one comparative observation that exists
-
-Two X3 units, side by side, both on CrossInk 1.5.0, same settings, same screen
-protector ([r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/),
-2026-08-10) · **firsthand comparative observation, no instrumentation**:
-
-| Unit | Contrast | Speed |
-|---|---|---|
-| Official-site purchase | *"slightly **whiter** background and **clearer** text"* | *"Page turns and menus seem **slower**"* |
-| Amazon.ca purchase, higher serial | *"slightly **darker** background and not as clear text"* | *"Page turns and menus seem **faster**"* |
-
-**A real, visible contrast/speed trade-off between two units of the same model.**
-The obvious hypothesis is the [UC8253 → UC8279d transition](features/display.md);
-**which unit had which controller was never determined.** No numbers, no method,
-n = 1 pair.
-
-If the hypothesis is right, it would be the only user-visible evidence of that
-silent hardware change — which is why it is recorded despite being subjective.
-
-## What has never been measured
-
-Runtime · active current · sleep current (**even though the X3, unlike the X4,
-*can* power down its SD card**) · boot time · page-turn latency · full-refresh
-time · Wi-Fi throughput or range · SD read/write rate · IMU ODR/noise · RTC drift
-(**which would also settle the [DS1307-vs-DS3231 conflict](features/rtc.md)**).
-
-## Known performance failure
-
-**Out-of-memory during OTA**, observed on this device specifically:
-
-> "I'd like to stop using github releases moving forward as **it causes out of
-> memory issues on the x3**."
-> — [r/XTEINK `1uek163`](https://old.reddit.com/r/XTEINK/comments/1uek163/), 2026-06-24
-
-Root cause: the ESP32-C3 has **no PSRAM**. The S3 devices
-([X4 Pro](../x4-pro/README.md), [X4 Classic](../x4-classic/README.md)) have 8 MB
-and do not have this problem.
-
-## Expected but unquantified: the UC8279d penalty
-
-For units shipped from ~July 2026, the SDK states Full/Half/Fast currently run the
-**same OTP waveform**, *"likely a full GC-style flash on every page turn"*, with
-**no grayscale**. If accurate, page turns on a newer X3 are materially slower and
-uglier than on an older one until waveform banks are tuned.
-
-**This is a datasheet-derived expectation, not a measurement**, and it may be what
-the two-unit comparison above was actually seeing — in which case the *faster*
-unit would be the **older UC8253**. Unresolved.
diff --git a/devices/xteink/x3/pinouts-and-buses.md b/devices/xteink/x3/pinouts-and-buses.md
deleted file mode 100644
index 9bb75a7..0000000
--- a/devices/xteink/x3/pinouts-and-buses.md
+++ /dev/null
@@ -1,164 +0,0 @@
-# Xteink X3 — pinouts and buses
-
-> ESP32-C3. From `BoardConfig::XTEINK_X3` / `XTEINK_X3_UC8279`
-> (**[SDK]** `BoardConfig.h:881–947`, commit `24003795381a6c23630a26472ae3b06550333e71`)
-> and `XteinkDetect.cpp`. **Independently corroborated by a multimeter.**
-> Retrieved **2026-09-04**.
-
-Permalink:
-`https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L881-L947`
-
-## The corroboration is unusual and worth stating
-
-The Chinese teardown author writes:
-
-> 主要管脚均使用万用表测量，并于crosspoint项目代码进行交叉验证。
-> *"The main pins were all measured with a multimeter and cross-validated against
-> the CrossPoint project source code."*
-> — [`sunwoods/Xteink-X3`](https://github.com/sunwoods/Xteink-X3) README
-
-That makes the X3 pinout the **only one in this family with independent physical
-verification**. He also credits CrossPoint for part numbers he could not read
-directly, so the **BOM** is a mix of direct reading and borrowed identification —
-treat individual part numbers with more caution than the pins.
-
-## Complete GPIO map
-
-| GPIO | Signal | Dir | Bus / role | Notes |
-|---:|---|---|---|---|
-| **0** | Battery voltage ADC **and** I²C **SCL** | — | **dual-assigned** | See conflict below |
-| **1** | Button ADC ladder group 1 | in | ADC1_CH1 | Back / Confirm / Left / Right |
-| **2** | Button ADC ladder group 2 | in | ADC1_CH2 | Up / Down |
-| **3** | Power button | in | digital | active-LOW |
-| **4** | EPD **DC** | out | display | |
-| **5** | EPD **RST** | out | display | |
-| **6** | EPD **BUSY** | in | display | |
-| **7** | SD **MISO** | in | shared SPI | |
-| **8** | **SCLK** | out | shared SPI | display **and** SD |
-| **10** | **MOSI / SDA** | out/io | shared SPI | display **and** SD. Released to input for the controller-ID read |
-| **12** | SD **CS** | out | shared SPI | |
-| **13** | **SD power enable** | out | power | **active-HIGH.** `digitalWrite(13,HIGH)` in setup; **LOW** on every deep sleep |
-| **20** | I²C **SDA** — *and* `usbDetect` | io | **dual-assigned** | See conflict below |
-| **21** | EPD **CS** | out | display | |
-
-## Two dual-assignment conflicts in the SDK
-
-| GPIO | Assignment A | Assignment B |
-|---:|---|---|
-| **0** | `batteryAdc = 0` (ADC1_CH0, ÷2 divider) | `X3_I2C_SCL = 0` |
-| **20** | `usbDetect = 20` | `X3_I2C_SDA = 20` |
-
-Both pins are given two roles in the **same SDK, same commit**. These cannot both
-be live simultaneously.
-
-**Most likely reading:** the `batteryAdc` and `usbDetect` fields were **copied from
-the X4 profile** when the X3 profile was created, and are dead on this board —
-the X3 has a **BQ27220 fuel gauge** and does not need an ADC for battery voltage
-at all. That is a hypothesis with a strong motive, **not a finding.**
-
-**What would settle it:** reading the schematic sketch
-(`artifacts/teardown/sunwoods-cn/02.jpg`) for what GPIO0 and GPIO20 connect to, or
-a continuity check. **The schematic is held in this repository and has not been
-read in detail** — the cheapest open action on this device.
-
-## Display bus
-
-| Signal | GPIO |
-|---|---:|
-| SCLK | **8** |
-| MOSI / SDA | **10** |
-| CS | **21** |
-| DC | **4** |
-| RST | **5** |
-| BUSY | **6** |
-
-**Identical to the X4.** Only the controller and the panel geometry differ.
-
-Clock **20 MHz** — UC8253 datasheet maximum (*"Clock rate up to 20 MHz"*, serial
-write timing `TSCYCW`; the SDK cites
-`https://www.elecrow.com/download/product/DIE01237S/UC8253_Datasheet.pdf`).
-UC8279 is rated the same. A prior fork (Witch Reader) ran a conservative
-**16 MHz**; 20 MHz is in-spec and ~25 % faster on plane writes.
-
-### Controller fingerprint
-
-`detectX3DisplayController()` bit-bangs a half-duplex 4-wire read on
-**SCLK 8 / SDA 10 / CS 21 / DC 4 / RST 5 / BUSY 6** after a reset pulse, and reads
-UC8279 **`VER (0x70)`** — reserved `0x00`, `CHIP_VER` (datasheet default `0x03`),
-24-bit `LUT_VER` — plus **`FLG (0x71)`**.
-
-Match requires: leading `0x00`, a non-floating `CHIP_VER`, and `FLG` idle with
-`BUSY_N = 1` — **in two passes that agree byte-for-byte**. Anything else
-conservatively resolves to the shipping **UC8253**.
-
-**Two `Pending` items are recorded honestly by the SDK:** what the UC8253 actually
-answers to `0x70`, and whether production MTP programs `CHIP_VER` to something
-other than `0x03` (which is why the matcher deliberately does not pin the value).
-
-## SD card — shared SPI, but with a power rail
-
-| Signal | GPIO |
-|---|---:|
-| SCLK | **8** (shared with display) |
-| MOSI | **10** (shared) |
-| MISO | **7** |
-| CS | **12** |
-| **powerEnable** | **13**, **active-HIGH** |
-
-The power enable is the X3's advantage over the X4, and the SDK explains exactly
-why it matters:
-
-> "Confirmed by X3 factory-firmware RE: `setup()` does `digitalWrite(13,HIGH)`;
-> every deep-sleep does `digitalWrite(13,LOW)`. Without declaring it,
-> `powerDownRailsForSleep()` has no X3 SD enable to cut, so **the card stays
-> powered through sleep → battery drain**."
-
-**Note the polarity difference from the S3 devices:** GPIO13 here is
-**active-HIGH**; the X4 Pro's GPIO5 and the X4 Classic's GPIO6 are **active-LOW**.
-And on the **X4**, GPIO13 is the **battery MOSFET latch**, a completely different
-function. Three models, same pin number, three meanings — **never port power code
-between them.**
-
-## I²C bus — SDA 20 / SCL 0 @ 400 kHz
-
-| Address | Device | Component | Probe used by `XteinkDetect` |
-|---|---|---|---|
-| **0x55** | **BQ27220** fuel gauge | [`texas-instruments/bq27220`](../../../components/texas-instruments/bq27220/README.md) | SoC reg `0x2C`, voltage reg `0x08` |
-| **0x68** | **DS-series RTC** | [`unidentified/…/rtc-ds-series`](../../../components/unidentified/xteink-x3-x4/rtc-ds-series/README.md) | seconds reg `0x00` |
-| **0x6B** (alt **0x6A**) | **QMI8658** 6-axis IMU | [`qst/qmi8658a`](../../../components/qst/qmi8658a/README.md) | `WHO_AM_I` reg `0x00` == **`0x05`** |
-
-**This bus is the X3/X4 discriminator.** One C3 binary serves both devices;
-`XteinkDetect::detectXteinkVerdict()` scores the presence of these three parts.
-Finding them → X3. Finding nothing → X4.
-
-**Safety note:** this probe is compiled **only** for C3 profiles
-(`#define FREEINK_XTEINK_C3 (FREEINK_DEVICE_X4 || FREEINK_DEVICE_X3)`). On an
-ESP32-S3, GPIO20 is USB D+ and GPIO0 is a boot strap, so running it there would be
-actively harmful.
-
-## Input — ADC resistor ladder
-
-**Identical to the X4** — GPIO1 (Back/Confirm/Left/Right) + GPIO2 (Up/Down),
-power on GPIO3 active-LOW, `ADC_11db`. Same thresholds, same three-device
-calibration data. See [`../x4/features/buttons.md`](../x4/features/buttons.md).
-
-Owner-reported difference: the X3's buttons are *"somewhat mushy and quieter"*
-than the X4's — a moulding/switch difference, not an electrical one.
-
-## NFC
-
-An **ISO/IEC 14443A tag** is on the board (**[CN]** BOM) and NFC is an advertised
-feature (**[VENDOR]** launch announcement). It is a **passive tag** — it appears on
-no host bus, in no board profile, and in no firmware. See
-[`features/nfc.md`](features/nfc.md).
-
-## Resource conflicts
-
-| Resource | Contenders |
-|---|---|
-| SPI 8/10 | EPD **and** microSD — only CS separates them |
-| GPIO10 | SPI MOSI **and** the half-duplex controller-ID read (released to input) |
-| GPIO0 | `batteryAdc` **and** I²C SCL — **unresolved** |
-| GPIO20 | `usbDetect` **and** I²C SDA — **unresolved** |
-| GPIO13 | SD rail (X3) vs battery latch (X4) vs unused (S3 models) |
-| ADC1 | battery sense + two button ladders |
diff --git a/devices/xteink/x3/product-history-and-family.md b/devices/xteink/x3/product-history-and-family.md
deleted file mode 100644
index 884f570..0000000
--- a/devices/xteink/x3/product-history-and-family.md
+++ /dev/null
@@ -1,73 +0,0 @@
-# Xteink X3 — product history and family
-
-Full family context: [`../README.md`](../README.md).
-
-## Timeline
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2025-12-08 | Shopify product record created | **[VENDOR]** |
-| **2025-12-09** | **Announced** — *"builds on everything we learned from building the X4 and pushes the idea of true pocket reading even further"*. Spec list: **55 g, 3.7″, 250+ PPI, gyroscope, NFC, magnetic pogo charging, clock + battery %** | **[COMM]** [r/xteinkereader `1pi6ezd`](https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/), 275 pts |
-| 2025-12-11 | **Pre-orders open.** *"Super Early Bird units are **non-refundable**"* | **[COMM]** [`1pjw3ay`](https://old.reddit.com/r/xteinkereader/comments/1pjw3ay/) · **[VENDOR]** |
-| 2025-12-26 | Community digest: X3 shipping confirmed for 5 Feb; *"Frontlight support (still the **#1 feature request**)"* | **[COMM]** |
-| 2025-12-28 | *"Xteink S4 release date?"* — the Android sibling is already awaited | **[COMM]** |
-| **2026-02-05** | **Shipping begins** — an **8-week** pre-order-to-ship gap | **[COMM]** |
-| 2026-02-22 | *"1 Week Review - Happy that I joined the club :)"*, 83 pts | **[COMM]** |
-| 2026-03-22 | *"My Xteink X3 Review (vs X4). The Antidote to Smartphones."* | **[COMM]** r/eink |
-| 2026-03-25 | Screen protectors listed | **[VENDOR]** |
-| 2026-04-01 | Magnetic case, 6 colours | **[VENDOR]** |
-| **2026-04-03** | The **Nano / Tong Card (瞳卡)** surfaces — a separate NFC e-paper product | **[COMM]** [r/xteinkHax `1sbjsr3`](https://old.reddit.com/r/xteinkHax/comments/1sbjsr3/), 110 pts |
-| 2026-04-08 | *"Crosspoint on X3 - preview with **smooth antialiasing waveforms**"* — the 4-level grey path working on UC8253 | **[COMM]** r/eink, 55 pts |
-| **2026-04-28** | *"X3 vs X4 - actual experience comparison"*, **412 pts** | **[COMM]** |
-| 2026-05-15 / 06-19 | Pogo cable ($4.99) and adapter ($5.99) listed **separately** | **[VENDOR]** |
-| **2026-06-03** | NFC question raised on the CrossPoint discussion board; **maintainer establishes the tag is firmware-independent** | **[COMM]** [discussion #2259](https://github.com/crosspoint-reader/crosspoint-reader/discussions/2259) |
-| 2026-06-20 | 20 % off sale via the CrossPoint affiliate link | **[COMM]** |
-| **2026-07-01** | **First public teardown** — 13 images, 650 mAh, ESP32-C3, 128 Mbit Puya flash, *"DS1307 RTC"* | **[TD]** [r/xteinkereader `1uksv6s`](https://old.reddit.com/r/xteinkereader/comments/1uksv6s/) |
-| **~2026-07** | **Vendor warns the community of the UC8253 → UC8279d panel switch** — the only pre-announced silent hardware change found in this family | **[SDK]** `docs/xteink-x3-uc8279-support.md` |
-| **2026-08-07** | **CrossPoint 1.5** — *"this release DOES support the new x3 display variants"*, **763 pts, 305 c** | **[COMM]** |
-| 2026-08-08 | NFC use cases documented by owners | **[COMM]** |
-| **2026-08-10** | Two-unit comparison: **four back-casing variants**, a visible contrast/speed difference, and **lock state uncorrelated with channel** | **[COMM]** [`1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/) |
-| 2026-08-18 | An X3 acquired for **$16**; sharpest published criticism of vendor conduct | **[COMM]** |
-| 2026-09-02 | **Rear glass cracking** report; question about metal backing goes **unanswered** | **[COMM]** |
-| 2026-09-04 | **$69.00**, both colours in stock | **[VENDOR]** |
-
-## Position in the family
-
-The X3 is the **second** device and the vendor's own stated iteration on the X4:
-*"builds on everything we learned from building the X4"*. It went **smaller,
-sharper and better-instrumented** rather than more powerful — the SoC, flash,
-button scheme and shared-SPI architecture are unchanged.
-
-| Relationship | Device |
-|---|---|
-| Predecessor / sibling | [X4](../x4/README.md) — same board family, one C3 binary serves both |
-| Upmarket sibling | [X4 Pro](../x4-pro/README.md) — S3, PSRAM, touch, frontlight |
-| Buttons-only S3 sibling | [X4 Classic](../x4-classic/README.md) — not internationally listed |
-| Android sibling | [S4](../s4/README.md) |
-| Accessory product | [Nano / Tong Card](../nano/README.md) — NFC e-paper card, **often confused with the X3's NFC tag** |
-| Announced successor to the X4 | **"X4 version 2"**, vendor-confirmed for September 2026, spec unknown |
-
-## Manufacturing: outsourced and visibly inconsistent
-
-The four back-casing variants observed by owners — sticker label, engraved text,
-completely clean, faint labelling — across purchases from the official site,
-Amazon.ca, AliExpress and Xianyu, support a community reading:
-
-> "They'll outsource to a bunch of manufacturers who can meet the specs."
-
-Combined with the **panel-controller change** and **unpredictable USB-lock state
-by channel**, the practical conclusion is that **two X3s are not necessarily the
-same device**, and nothing external tells you which you have.
-
-## What "learned from the X4" actually produced
-
-| Change | Direction |
-|---|---|
-| 3.7″ / 792×528 / ~257 PPI vs 4.26″ / 800×480 / ~219 | **sharper, smaller** |
-| 55 g vs ~80 g | **lighter** |
-| BQ27220 gauge vs bare ADC | **better** |
-| RTC added (X4 has none) | **better** |
-| QMI8658 IMU + NFC added | **better** |
-| SD power enable added (GPIO13) | **better** — the X4 cannot sleep its card |
-| **USB-C → magnetic pogo** | **worse, and the most-contested change in the family** |
-| Button feel | **worse** per owners — *"mushy and quieter"* |
diff --git a/devices/xteink/x3/projects-and-community.md b/devices/xteink/x3/projects-and-community.md
deleted file mode 100644
index dbfb692..0000000
--- a/devices/xteink/x3/projects-and-community.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# Xteink X3 — projects
-
-> From the **~200-repository** GitHub census, 2026-09-04. Owner reports are in
-> [`community.md`](community.md). The shared ecosystem is documented once, in
-> [`../x4/projects-and-community.md`](../x4/projects-and-community.md) — this page
-> covers what is **X3-specific**.
-
-## The X3's position in the ecosystem
-
-Almost every project says *"for the Xteink X3 and X4"*. The X3 shares its SoC,
-board layout, ADC ladder and shared-SPI design with the X4, and **one C3 binary
-serves both** — `XteinkDetect` fingerprints the I²C bus at boot. So X3 support is
-usually a by-product of X4 support rather than separate work.
-
-**Except for the panel.** The X3's UC8253 (and now UC8279d) is unique in the
-family, and that is where X3-specific effort concentrates.
-
-## X3-specific projects
-
-| Project | Why it is X3-specific |
-|---|---|
-| [`anki630/crossmosa`](https://github.com/anki630/crossmosa) + [`crossmosa-freeink-sdk`](https://github.com/anki630/crossmosa-freeink-sdk) | ★25. 繁體中文 firmware **and its own SDK fork doing "UC8279 waveform tuning"** — **the only project anywhere working the new X3 panel** |
-| [`emezrahi/XTeink-X3-Supafast`](https://github.com/emezrahi/XTeink-X3-Supafast) | Refresh-speed work on the X3 |
-| [`kocha01/xteink-x3-pokiink-fw`](https://github.com/kocha01/xteink-x3-pokiink-fw) | PokiInk — an X3 CrossPoint fork |
-| [`smalltomatowater-boop/crosspoint-reader-x3`](https://github.com/smalltomatowater-boop/crosspoint-reader-x3) | Japanese UI (Migu1M) **+ a tmux terminal** |
-| [`hannah-nula/crosspoint-x3-ble-page-turner`](https://github.com/hannah-nula/crosspoint-x3-ble-page-turner) | *"validated BLE page-turner **reconnect** support"* — implying default reconnect is fragile |
-| [`sermelipharo/x3-trmnl`](https://github.com/sermelipharo/x3-trmnl) | **TRMNL BYOD** firmware on the CrossPoint HAL |
-| [`evanstoddard/xteink_x3_zephyr`](https://github.com/evanstoddard/xteink_x3_zephyr) | **Zephyr RTOS** — the only non-Arduino/non-IDF attempt in the family |
-| [`wiltodelta/xteink-sugartv`](https://github.com/wiltodelta/xteink-sugartv) | Turns an X3 into a **continuous glucose monitor display** for Home Assistant |
-| [`padge01/xteink-pokemon-game`](https://github.com/padge01/xteink-pokemon-game) | *"reading-powered Pokemon companion game for the Xteink X3, built on CrossInk"* |
-| [`CraigBell/xteink-x3-home-assistant-dashboard`](https://github.com/CraigBell/xteink-x3-home-assistant-dashboard) | HA dashboard |
-| [`Eleecho/CrossInk-XTEInk3-ImageTuning`](https://github.com/Eleecho/CrossInk-XTEInk3-ImageTuning) | `.bmp` rendering tweaks |
-| [`twil09/xteinkos`](https://github.com/twil09/xteinkos) | *"Custom made OS for the Xteink X3 E-reader"* |
-| [`dm807cam/xteink3-bible`](https://github.com/dm807cam/xteink3-bible) | BSB as 66 per-book EPUBs, formatted for small screens |
-| [`nerderer/xteink-x3-somatic-cards`](https://github.com/nerderer/xteink-x3-somatic-cards), [`lmagdanello/xteink-x3-extension`](https://github.com/lmagdanello/xteink-x3-extension), [`twbeatles/xteink-x3-websync`](https://github.com/twbeatles/xteink-x3-websync) | Content and sync tooling |
-| [`sunwoods/Xteink-X3`](https://github.com/sunwoods/Xteink-X3) | **Not software** — the Chinese hardware census and schematic sketch archived in this record |
-| [`ElendilDrac01/xteink-x3-calibre-stock`](https://github.com/ElendilDrac01/xteink-x3-calibre-stock) | Calibre plugin for **stock** firmware — useful if you do not want to reflash |
-
-## The tooling that matters most for the X3
-
-[`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher) — ★12,
-MIT, Python GUI. It is the best-documented X3 tool in existence:
-
-- **1:1 full-flash backup and restore in ~2 minutes**, auto COM detection.
-- Ships **stock images**: `x3_en_v1.0.7_full.bin`, `x3_en_v5.2.13_full.bin`,
-  `x3_cn_v5.2.13_full.bin`, `x3_cn_v5.2.13_ota.bin`.
-- Carries an `X3-FLASHER-GUIDE` in **both English (13.6 KB) and Chinese
-  (16.7 KB)**.
-
-**The X3 is the only Xteink with published full-flash stock images.** The X4 has
-only OTA images there (plus the separate community dump this repo archived); the
-X4 Pro and X4 Classic have nothing.
-
-## The panel-variant problem, in project terms
-
-Units shipped from ~July 2026 carry a **UC8279d**. CrossPoint 1.5 (2026-08-07)
-was the release that added support — *"this release **DOES support the new x3
-display variants** that a few of you have received"* — with the warning that
-*"Other forks will need to pull the latest SDK to avoid **soft bricking locked
-units**"*.
-
-**Practical rule:** on a recently-purchased X3, use CrossPoint ≥ 1.5, CrossInk
-≥ 1.5, or a fork synced to a current FreeInk SDK. An older fork may leave a blank
-screen or worse.
-
-Only `crossmosa-freeink-sdk` is actively tuning UC8279 waveforms; until that
-lands, newer X3s likely run a **full GC-style flash on every page turn** and have
-**no grayscale**. See [`features/display.md`](features/display.md).
-
-## Known X3 failure modes with named causes
-
-| Failure | Cause | Fix |
-|---|---|---|
-| **OTA out-of-memory** | No PSRAM on the ESP32-C3 | CrossPoint stopped using GitHub releases; reflash from the web flasher (unlocked) or SD (locked) |
-| Blank screen after flashing | UC8279d unit + firmware without that driver | CrossPoint ≥ 1.5 |
-| Soft brick on a locked unit | Fork on a stale SDK | Pull the current SDK |
-| Battery drain through sleep | Firmware not declaring the **GPIO13 SD rail** | Declare it; `powerDownRailsForSleep()` then cuts the card |
-
-## See also
-
-[`../x4/projects-and-community.md`](../x4/projects-and-community.md) — the shared
-ecosystem: mainlines, flashers, `.XTC` converters, font tooling, localisation,
-community service sites.
diff --git a/devices/xteink/x3/research-log.md b/devices/xteink/x3/research-log.md
deleted file mode 100644
index 0186a3e..0000000
--- a/devices/xteink/x3/research-log.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Xteink X3 — research log
-
-The **family-wide** log — source classes, Reddit and GitHub depth, dead links,
-stopping criterion — is at [`../x4-pro/research-log.md`](../x4-pro/research-log.md).
-The **second-sweep methodology and what it changed** is documented at
-[`../x4/research-log.md`](../x4/research-log.md). This page records what was
-X3-specific. Snapshot **2026-09-04**.
-
-## X3-specific queries and outcomes
-
-| Target | Depth | Outcome |
-|---|---|---|
-| `xteink x3` (Reddit) | 100 results | Bulk owner material |
-| `xteink teardown`, `xteink teardown chip` | 100 each | **Found the only two Xteink teardowns that exist — both X3** |
-| **`阅星瞳`**, **`星瞳 电纸书`** (Chinese) | 100 each | Surfaced the brand-spelling split (瞳 vs 曈) |
-| `sunwoods/Xteink-X3` repo + tree | full | **Chinese hardware census + hand-drawn schematic + BOM incl. the NFC tag** |
-| Imgur album `OA6CS2C` | full, via `ajaxalbums` | **13 captioned teardown images**, 650 mAh, "DS1307", ESP32-C3, 128 Mbit flash |
-| `zocs/eink-quick-flasher` tree + firmware README | full | **Four published stock X3 images** (V1.0.7, V5.2.13 ×3) — the only Xteink with full-flash stock images published |
-| `xteink nfc` + thread `1vit43t` with comments | full | **NFC purpose resolved** |
-| GitHub **discussion** #2259 via GraphQL | full | **The authoritative NFC statement**, from the CrossInk maintainer |
-| Thread `1vkuhbi` "Which x3 is newer?" with comments | full | **Four back-casing variants; a visible contrast/speed difference between two units; channel-vs-lock-state data** |
-
-## Two retrieval techniques that were essential
-
-**1. Imgur album enumeration.** `https://imgur.com/a/<id>` is a JavaScript shell;
-scraping its HTML yielded **2 of 13** images. The undocumented endpoint
-`https://imgur.com/ajaxalbums/getimages/<id>/hit.json` returns the full album with
-**per-image captions, dimensions and upload timestamps**, unauthenticated, with a
-plain browser UA. Without it, 11 of the 13 teardown photographs — including the
-one captioned "DS1307 RTC" — would have been missed.
-
-**2. GitHub GraphQL for discussions.** `api.github.com/search/*` **does not index
-Discussions**. The single most authoritative statement about the X3's NFC tag
-lives in `crosspoint-reader/crosspoint-reader` discussion **#2259** and is
-reachable only via `gh api graphql`. Repository-only searching missed it entirely
-on the first pass.
-
-Both are recorded in [`commands.md`](commands.md).
-
-## Negative results, deliberately preserved
-
-| Searched for | Result |
-|---|---|
-| X3 **schematic** (formal) | **None.** The `sunwoods` `02.jpg` is a **hand-drawn sketch** whose author warns *"some components are substituted with other similar footprints"* |
-| X3 **flash dump** | **Not obtained.** Four stock images exist as **Git LFS pointers**; blobs not fetched |
-| X3 **partition layout** | **Not established.** Assumed to match the X4's; unverified |
-| **UC8279d unit on a bench** | **Does not exist anywhere** — the SDK states so explicitly |
-| Power measurements | **None**, despite a teardown performed expressly to make them |
-| FCC / CE / SRRC | **None** — and the community explains why: *"Regulatory info is in software on mine, back is clean"* |
-
-## The conflict this device generated
-
-The X3 is the **only Xteink with independent teardowns**, and consequently the
-only one where sources **disagree**: the RTC is called `DS3231` by the firmware,
-`DS1307` by an English teardown caption, and `DS-series` by a Chinese teardown
-that declines to narrow it.
-
-**That is a feature of having more than one source, not a defect.** The other
-models have no conflicts because they have no second opinion.
-
-## Cheapest open actions, ranked
-
-1. **Read `artifacts/teardown/sunwoods-cn/02.jpg`** — held here, unread. Would
-   likely resolve the GPIO0/GPIO20 dual-assignment.
-2. **Examine `13-Ay3rpJg.jpg` (5760×3240) at full resolution** — held here,
-   unread. Would test the "DS1307" caption.
-3. **Examine images 10/11** (*"at an angle to better read the chip labels"*) —
-   would likely give the **Puya flash part number**.
-4. Git-LFS fetch the four stock images.
-5. Query the vendor OTA endpoint.
-
-**Three of the top five require no network access at all** — the evidence is
-already archived in this repository and has simply not been looked at.
-
-## Stopping criterion
-
-Two consecutive passes returned only duplicates for X3 hardware facts. Remaining
-sources require: reading images already held (deferred), an LFS fetch (deferred),
-Chinese marketplaces (declared exclusion), or hardware (unavailable).
-
-**Reproducible broad-coverage snapshot dated 2026-09-04.**
diff --git a/devices/xteink/x3/resources-and-conflicts.md b/devices/xteink/x3/resources-and-conflicts.md
deleted file mode 100644
index 0c21096..0000000
--- a/devices/xteink/x3/resources-and-conflicts.md
+++ /dev/null
@@ -1,117 +0,0 @@
-# Xteink X3 — resources and conflicts
-
-ESP32-C3, 16 MB flash, **no PSRAM**. Snapshot **2026-09-04**.
-
-## GPIO allocation
-
-| GPIO | Owner | Exclusive? |
-|---:|---|---|
-| **0** | **I²C SCL** — *and* `batteryAdc` in the profile | ❌ **contested** |
-| 1 | Button ladder group 1 (ADC1_CH1) | shared ADC1 timing |
-| 2 | Button ladder group 2 (ADC1_CH2) | shared ADC1 timing |
-| 3 | Power button | ✅ |
-| 4 | EPD DC | ✅ |
-| 5 | EPD RST | ✅ |
-| 6 | EPD BUSY | ✅ |
-| 7 | SD MISO | ✅ |
-| **8** | **SPI SCLK** | ❌ display + SD |
-| **10** | **SPI MOSI / SDA** | ❌ display + SD; also released to input for the controller-ID read |
-| 12 | SD CS | ✅ |
-| **13** | **SD power enable, active-HIGH** | ✅ |
-| **20** | **I²C SDA** — *and* `usbDetect` in the profile | ❌ **contested** |
-| 21 | EPD CS | ✅ |
-
-**No free GPIOs identified.**
-
-## Two dual-assignments the SDK does not resolve
-
-| Pin | Assignment A | Assignment B |
-|---:|---|---|
-| **0** | `batteryAdc = 0` (ADC1_CH0, ÷2 divider) | `X3_I2C_SCL = 0` |
-| **20** | `usbDetect = 20` | `X3_I2C_SDA = 20` |
-
-Same SDK, same commit `2400379`. **Both pairs cannot be live.**
-
-**Hypothesis, not a finding:** `batteryAdc` and `usbDetect` were copied from the
-[X4 profile](../x4/pinouts-and-buses.md) and are dead here — the X3 has a
-**BQ27220 fuel gauge** and does not need an ADC battery sense at all.
-
-**What would settle it:** the schematic sketch at
-`artifacts/teardown/sunwoods-cn/02.jpg` — **held in this repository and not yet
-read**. The cheapest unresolved question in the whole Xteink subject.
-
-## Bus contention
-
-**EPD and microSD share SCLK 8 / MOSI 10**, separated only by chip select
-(`separateSpi = false`). Consequences are identical to the
-[X4's](../x4/resources-and-conflicts.md): serialisation, per-transaction clock
-renegotiation, and a controller-ID probe that must run before `EpdBus::begin()`
-and release any retained GPIO hold on RST first.
-
-**Unlike the X4, the X3 can power its card down** — see below.
-
-## I²C bus — SDA 20 / SCL 0 @ 400 kHz
-
-Three devices, one Arduino `Wire` controller (single-bus SoC, so `i2cBus` is
-ignored):
-
-| Address | Device | Consequence of a stalled bus |
-|---|---|---|
-| 0x55 | [BQ27220](../../../components/texas-instruments/bq27220/README.md) gauge | battery reading lost |
-| 0x68 | [DS-series RTC](../../../components/unidentified/xteink-x3-x4/rtc-ds-series/README.md) | clock lost |
-| 0x6B | [QMI8658](../../../components/qst/qmi8658a/README.md) IMU | motion page-turn lost |
-
-**And board identification lost** — `XteinkDetect` uses exactly these three to
-decide X3-vs-X4 at boot. A wedged I²C bus does not merely disable three sensors;
-it can select the wrong board profile.
-
-## ADC1 contention
-
-Button ladder groups on GPIO1 and GPIO2, sequential reads, one global
-`ADC_11db` attenuation. **Only one button per group is detectable at a time**;
-cross-group chords work.
-
-## Power domains
-
-| Domain | Control | Note |
-|---|---|---|
-| **SD card** | **GPIO13, active-HIGH** | `setup()`: HIGH. Every deep sleep: LOW. **Omit the LOW and the card drains the battery through sleep** |
-| Display | controller internal booster | No external PMIC |
-| Battery charge | TP4056-class IC, **no host status GPIO declared** | Drives a red charge LED directly |
-
-### GPIO13 means three different things across the family
-
-| Device | GPIO13 |
-|---|---|
-| **X3** | **SD power enable, active-HIGH** |
-| [X4](../x4/resources-and-conflicts.md) | **Battery MOSFET latch — LOW powers the device off** |
-| X4 Pro / X4 Classic | unused (SD enables are GPIO5 / GPIO6, **active-LOW**) |
-
-**Porting sleep code from an X4 to an X3 would drive GPIO13 LOW to "power off" and
-instead merely cut the SD card. Porting the other way would cut power mid-write.**
-
-## Memory and flash
-
-SRAM ~400 KB · **PSRAM none** · flash 16 MB. Partition layout **not established
-for the X3** — the X4's (`app0` 6400 KiB @ `0x10000`, `spiffs` 3456 KiB @
-`0xC90000`) is a reasonable assumption and **has not been verified**.
-
-**No PSRAM** is the binding constraint, and it is on this device that
-**OTA out-of-memory was actually observed**.
-
-## Panel-controller resource note
-
-Units from ~July 2026 carry a **UC8279d** whose **LUT format is incompatible**
-with the UC8253's: group-based 7-byte groups × 7 groups vs 43-byte LUTs. The X3's
-six tuned waveform banks **cannot be copied over**, and grayscale is unavailable
-until new banks are tuned. See [`features/display.md`](features/display.md).
-
-## Realistic concurrent-use scenarios
-
-| Scenario | Assessment | Status |
-|---|---|---|
-| Page turn while streaming from SD | **Serialised** — one SPI bus | Not benchmarked |
-| Motion page-turn (IMU polling) + display refresh | IMU has **no interrupt**, so it must be polled during refresh | Not benchmarked |
-| Wi-Fi + display refresh | Memory pressure likely; no PSRAM | **OTA is known to fail** |
-| Deep sleep with card inserted | **Works — if firmware declares GPIO13** | Never measured |
-| I²C poll + SPI transfer | Independent buses; no conflict expected | Untested |
diff --git a/devices/xteink/x3/sources.md b/devices/xteink/x3/sources.md
deleted file mode 100644
index a857920..0000000
--- a/devices/xteink/x3/sources.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Xteink X3 — sources
-
-Retrieved **2026-09-04** unless stated.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published | Establishes | Limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **X301** | `BoardConfig.h` `XTEINK_X3` + `XTEINK_X3_UC8279`, L881–947 | Free-Ink | community | source (commit-pinned) | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L881-L947> | 2026-09-04 | commit 2026-09-01 | Pins, both panel profiles, I²C peripherals, SD rail | Third-party RE | `scratch/eink-software/repos/freeink-sdk/` |
-| **X302** | `docs/xteink-x3-uc8279-support.md` | Free-Ink | community | technical note | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/docs/xteink-x3-uc8279-support.md> | 2026-09-04 | same | The UC8279d variant, its detection, and **its explicit unvalidated status** | Datasheet-derived; author states no unit has been benched | same |
-| **X303** | `XteinkDetect.cpp` | Free-Ink | community | source | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/XteinkDetect/src/XteinkDetect.cpp> | 2026-09-04 | same | I²C addresses 0x55/0x68/0x6B, `WHO_AM_I=0x05`, the X3/X4 fingerprint | The RTC probe reads only reg 0x00 — **does not discriminate DS1307 vs DS3231** | same |
-| **X304** | **X3 teardown, 13 images** | Reddit user | community | **teardown, firsthand** | <https://old.reddit.com/r/xteinkereader/comments/1uksv6s/xteink_x3_teardown/> · album <https://imgur.com/a/xteink-x3-teardown-OA6CS2C> | 2026-09-04 | **2026-07-01** | **650 mAh battery**, glued magnets, glass back, ESP32-C3, 128 Mbit flash, **"DS1307 RTC"** | Captions are the photographer's reading; rights unknown | [archived](artifacts/teardown/imgur-2026-07-01.ARCHIVED.md) |
-| **X305** | **`sunwoods/Xteink-X3` — Chinese hardware census + schematic** | GitHub `sunwoods` | community | **teardown + schematic, firsthand** | <https://github.com/sunwoods/Xteink-X3> | 2026-09-04 | — | Full BOM; **ISO 14443A NFC tag**; Puya flash; TP4056-class charger; **a hand-drawn schematic**; pins *measured with a multimeter* | Schematic uses substitute footprints; some part numbers borrowed from CrossPoint rather than read | [archived](artifacts/teardown/sunwoods-cn.ARCHIVED.md) |
-| **X306** | X3 Shopify product record | Xteink | **primary** | store API | <https://www.xteink.com/products.json?limit=250> | 2026-09-04 | created 2025-12-08, published 2025-12-11 | **$69.00**, two SKUs, both in stock, 58 g packaged | **Body prose is AI/SEO and is factually wrong** (claims a frontlight and cloud sync) | `scratch/xteink/vendor/products-p1.json` |
-| **X307** | "X3 Is Coming: Smaller, Lighter…" | Xteink via r/xteinkereader | **primary** (vendor announcement) | forum | <https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/> | 2026-09-04 | 2025-12-09, 275 pts | **55 g, 3.7-inch, 250+ PPI, gyroscope, NFC, pogo charging, clock + battery %** | Vendor marketing, but specific and falsifiable — and the PPI checks out arithmetically | `scratch/xteink/reddit/_merged-posts.json` |
-| **X308** | "Xteink X3 Live Now" | Xteink via r/xteinkereader | **primary** | forum | <https://old.reddit.com/r/xteinkereader/comments/1pjw3ay/> | 2026-09-04 | 2025-12-11, 147 pts | Same spec list; **shipping from 2026-02-05**; Super Early Bird units non-refundable | same | same |
-| **X309** | "X3 vs X4 - actual experience comparison" | r/xteinkereader | community | forum, comparative ownership | <https://old.reddit.com/r/xteinkereader/comments/1syav96/> | 2026-09-04 | 2026-04-28, **412 pts** | X3 buttons *"mushy and quieter"* vs X4's *"clickier and louder"* | Subjective | same |
-| **X310** | `zocs/eink-quick-flasher` firmware README | community dev | community | repository doc | <https://github.com/zocs/eink-quick-flasher/blob/main/firmware/README.md> | 2026-09-04 | — | Stock **V1.0.7** and **V5.2.13** (CN + EN, full **and** OTA); **CN/EN differ only by default UI language** | Files are Git LFS pointers; **blobs not fetched** | `scratch/xteink/firmware/zocs-firmware-README.md` |
-| **X311** | "CrossPoint 1.5 released" | r/xteinkereader | community | forum | <https://old.reddit.com/r/xteinkereader/comments/1vhvtdd/> | 2026-09-04 | 2026-08-07, **763 pts** | *"DOES support the new x3 display variants"*; soft-brick warning for stale forks | Developer statement | same |
-| **X312** | "CrossPoint 1.4.0 released" | r/XTEINK | community | forum | <https://old.reddit.com/r/XTEINK/comments/1uek163/> | 2026-09-04 | 2026-06-24, 350 pts | **X3 OTA out-of-memory**, and the reflash/SD-flash escape | Developer statement | same |
-| **X313** | "Anyone confirm which devices have metal backing?" | r/xteinkereader | community | forum, owner report | <https://old.reddit.com/r/xteinkereader/comments/1w56phf/> | 2026-09-04 | 2026-09-02 | **Rear glass cracked** on an X3 | Single anecdote; question went unanswered | same |
-| **X314** | "Got an X3 for dirt cheap ($16)" | r/XTEINK | community | forum, owner report | <https://old.reddit.com/r/XTEINK/comments/1vrnxnq/> | 2026-09-04 | 2026-08-18, 24 pts | Used pricing; **CrossMux** (a Chinese CrossPoint fork with WeChat Read support); criticism of vendor–community relations | Single anecdote, channel not stated | same |
-| **X315** | `anki630/crossmosa-freeink-sdk` | community dev | community | repository | <https://github.com/anki630/crossmosa-freeink-sdk> | 2026-09-04 | pushed 2026-08-28 | *"UC8279 waveform tuning"* — the only project working the new X3 panel | Not inspected | — |
-
-## Corroboration map
-
-| Claim | Independent sources |
-|---|---|
-| ESP32-C3 | **[SDK]** · **[TD-EN]** photo 10 · **[TD-CN]** BOM |
-| 128 Mbit / 16 MB Puya flash | **[TD-EN]** photo 10 · **[TD-CN]** BOM |
-| QMI8658 IMU @0x6B | **[SDK]** ×2 files · **[TD-CN]** BOM |
-| BQ27220 gauge @0x55 | **[SDK]** ×2 files · **[TD-CN]** BOM |
-| ~257 PPI | **[VENDOR]** *"250+ PPI"* · **arithmetic** from 792×528 / 3.7″ |
-| 650 mAh | **[TD-EN]** photo 3 only — **single source** |
-| NFC tag | **[TD-CN]** BOM · **[VENDOR]** announcement |
-| **RTC part** | **THREE SOURCES DISAGREE** — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-
-## Not used as evidence
-
-`xteink.com` X3 product prose — demonstrably false (advertises a frontlight the
-device does not have).
diff --git a/devices/xteink/x4-classic/README.md b/devices/xteink/x4-classic/README.md
deleted file mode 100644
index 99465e7..0000000
--- a/devices/xteink/x4-classic/README.md
+++ /dev/null
@@ -1,420 +0,0 @@
-# Xteink X4 Classic (X4C)
-
-> **Not listed for international sale.** A `x4-classic` collection exists on
-> `xteink.com` but contains **no device** — only generic accessories.
-> Research retrieval date **2026-09-04**.
-> **Depth: medium.** The board is well documented from a firmware dump; the
-> *product* is barely documented at all.
-
-## Identity and variants
-
-| Field | Value | Evidence |
-|---|---|---|
-| Name | **Xteink X4 Classic**, abbreviated **X4C** | **[SDK]** doc title; **[VENDOR]** collection handle `x4-classic` |
-| Board tag | **`ESP32S3_X4_CLA`** | **[DUMP]** |
-| Board revision string | **`ESP32S3_X4R2_CLA`** | **[DUMP]** — note `R2`, implying at least a revision 2 |
-| Default panel string | `ESP32S3_X4_CLA_SSD1677` | **[DUMP]** |
-| FreeInk profile | `BoardConfig::XTEINK_X4_CLASSIC` / `Board::XteinkX4Classic` | **[SDK]** `BoardConfig.h:1648–1706` |
-| Build flag | `-DFREEINK_DEVICE_X4CLASSIC=1` | **[SDK]** `platformio.sample.ini` `[env:x4c]` |
-| Stock firmware analysed | `flashx4c.bin`, app0 = **`xteink_app` v7.0.11** | **[SDK]** |
-| Vendor collection | `x4-classic` — exists, **contains 4 generic accessories and no device** | **[VENDOR]** |
-
-**This is a real, shipping product** — a stock flash dump exists and was reverse
-engineered — but it appears **not to be sold internationally**. The vendor is
-China-first; the S4 followed the same pattern.
-
-## What it is
-
-**The X4 Pro's board with the touchscreen and frontlight removed, and four extra
-buttons in their place.**
-
-Same ESP32-S3, same 16 MB flash and 8 MB PSRAM, same 800×480 glass, same display
-driver stack, same SDMMC slot, same BM8563 RTC, same CW2017 gauge. Then:
-
-| Removed | Added |
-|---|---|
-| GT911 touchscreen | **Four extra discrete buttons** on the freed GPIOs |
-| Warm/cool frontlight | **A QMI8658 IMU** at 0x6B |
-
-The freed pins are reused directly: touch-power **GPIO2**, SD-power **GPIO5** and
-frontlight **GPIO8/GPIO9** all become buttons.
-
-### Discovered before it was announced
-
-[r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/),
-2026-06-22, **300 points**: *"Did we just spot a new X4 model? Physical buttons +
-frontlight but no touchscreen in the latest video?"* — the community identified a
-buttons-only S3 variant in a vendor video. They were **right about the buttons and
-the absence of touch, and wrong about the frontlight**: the X4C has none.
-
-## Key specifications
-
-| Item | Value | Component | Evidence |
-|---|---|---|---|
-| SoC | **ESP32-S3**, 16 MB flash, 8 MB PSRAM | [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) | **[SDK]**, **[DUMP]** |
-| Display | 800×480 mono e-ink, 4.26″ | — | **[SDK]** |
-| Controller | **SSD1677 · UC8179 · UC8279** | [`solomon-systech/ssd1677`](../../../components/solomon-systech/ssd1677/README.md) · [`ultrachip/uc8179`](../../../components/ultrachip/uc8179/README.md) · [`ultrachip/uc8279`](../../../components/ultrachip/uc8279/README.md) | **[SDK]** |
-| **Controller selection** | **NVS `hw_calib`/`screenType`** — **there is no MISO, so the bus probe cannot work** | — | **[SDK]** |
-| Touch | **none** — stock instantiates `NoTouchDriver` | — | **[DUMP]** |
-| Frontlight | **none** — stock reports *"Frontlight hardware is disabled on this board"* | — | **[DUMP]** |
-| Buttons | **Seven discrete active-low GPIOs**, interrupt-driven | — | **[SDK]** |
-| RTC | **BM8563** @0x51 | [`generic/bm8563`](../../../components/generic/bm8563/README.md) | **[SDK]** |
-| Gauge | **CW2017** @0x63 | [`cellwise/cw2017`](../../../components/cellwise/cw2017/README.md) | **[SDK]** |
-| **IMU** | **QMI8658** @0x6B, `WHO_AM_I = 0x05`, **no interrupt line** | [`qst/qmi8658a`](../../../components/qst/qmi8658a/README.md) | **[DUMP]** RE-confirmed |
-| Storage | **Native SDMMC** 1-bit, power enable **GPIO6 active-LOW** | — | **[SDK]** |
-| USB | Native S3 USB-OTG, D− 19 / D+ 20, **USB-MSC capable** | — | **[SDK]** |
-| Charge STAT | GPIO21, active-HIGH | — | **[SDK]**, polarity **pending** |
-| Radios | **Wi-Fi and BLE present** | — | **[SDK]** — the most explicit radio statement in the family |
-| Audio / LEDs / PMIC / expander | **none** | — | **[SDK]** |
-
-## Pinout
-
-| GPIO | Role | Note |
-|---:|---|---|
-| 0 | Button **Left** (side) → up / prev | |
-| 1 | **Master peripheral/panel rail**, HIGH at boot | |
-| 2 | Button **Right** (bottom key) | *was* touch power on the Pro |
-| 3 | Button **Power** | |
-| **4** | **Plain input, not interrupt-attached** | **Role PENDING** — configured but unused by the SDK |
-| 5 | Button **Left** (bottom key) | *was* SD power on the Pro |
-| 6 | **SD power enable**, **active-LOW** | *was* BUSY-adjacent on the Pro; **not** a display pin |
-| 7 | Button **Right** (side) → down / next | |
-| 8 | Button **Confirm** (bottom key) | *was* frontlight cool |
-| 9 | Button **Back** (bottom key) | *was* frontlight warm |
-| **10** | EPD **RST** | **swapped vs the Pro** |
-| 11 | EPD **MOSI** | write-only, no MISO |
-| 12 | EPD **SCLK** | |
-| 13 | EPD **CS** | |
-| **14** | EPD **DC** | **swapped vs the Pro** |
-| **18** | EPD **BUSY** | **swapped vs the Pro** |
-| 19 / 20 | USB D− / D+ | |
-| 21 | Charge STAT | active-HIGH |
-| 38 / 39 | I²C SCL / SDA @400 kHz | BM8563 0x51 · CW2017 0x63 · QMI8658 0x6B |
-| 40 / 41 / 42 | SDMMC DAT0 / CLK / CMD | |
-
-**The display pins are NOT the same as the X4 Pro's.** DC, RST and BUSY are
-permuted:
-
-| Signal | X4 Pro | **X4 Classic** |
-|---|---:|---:|
-| DC | 18 | **14** |
-| RST | 14 | **10** |
-| BUSY | 6 | **18** |
-
-SCLK 12 / MOSI 11 / CS 13 are shared. `displaySpiHz` is **20 MHz** on both.
-**Porting display code between the two without changing these three pins will
-produce a panel that resets and never develops an image** — the exact failure mode
-the X4 Pro bring-up spent months on.
-
-## The no-MISO consequence
-
-The X4C display bus has **no MISO line at all**, so the UC81xx `VER`/`FLG` probe
-used on every other device in the family **cannot work** — the released line always
-floats to `0xFF`.
-
-So the X4C is the **one device where NVS is authoritative**:
-
-```
-NVS namespace hw_calib, key screenType (u8):
-  1 or 0x0B → UC8179
-  2 or 0x0C → UC8279
-  3 / default / unset → SSD1677
-```
-
-**The factory writes this once.** Its unreliability elsewhere — *"a full-flash from
-another unit overwrites it, so it can name the wrong panel"* — becomes a real
-hazard here, because there is no live check to override it. **Restoring an X4C
-from someone else's full-flash image can leave it with the wrong panel driver and
-no way to detect that.**
-
-## Input
-
-Seven discrete, interrupt-driven, active-low GPIOs. Physical layout = the X4 Pro's
-**two side keys** plus the C3 X4's **four bottom keys**:
-
-| Action | GPIO |
-|---|---:|
-| Up / previous page (side Left) | 0 |
-| Down / next page (side Right) | 7 |
-| Left (bottom key 1) | 5 |
-| Right (bottom key 2) | 2 |
-| Confirm (bottom key 3) | 8 |
-| Back (bottom key 4) | 9 |
-| Power | 3 |
-
-The stock array order is **2, 5, 8, 9** ("Bottom Key 1–4"). The SDK notes the
-mapping was corrected by hardware testing: *"the old GPIO8/9 left/right assignment
-made the physical Confirm/Back keys act as Up/Down."*
-
-**Not an ADC ladder** — unlike the C3 devices, every key is its own GPIO with its
-own interrupt. That is strictly better: chords work, no polling, no calibration.
-
-## Evidence quality and confidence
-
-The SDK is unusually explicit about how it decoded this board from
-`flashx4c.bin`. The single board-init function `FUN_4214c798` constructs the SPI
-bus via `FUN_4214d260(bus,11,12,13,14)` → MOSI 11 / SCLK 12 / CS 13 / DC 14, sets
-up I²C at 39/38, and registers every GPIO. **The GPIO mode argument was decoded
-from unambiguous pins** — SPI drive lines and the GPIO1 rail use mode 1 = OUTPUT,
-the STAT line uses mode 0 = INPUT, buttons use mode 2 = input+ISR.
-
-| Confidence | Items |
-|---|---|
-| **HIGH** | Display MOSI11/SCLK12/CS13/DC14/RST10/BUSY18; GPIO1 rail; all seven button GPIOs; SD enable GPIO6 (pulsed HIGH 80 ms → LOW 120 ms); charge STAT GPIO21; touch **absent**; frontlight **absent**; the three-controller set; `hw_calib/screenType` |
-| **PENDING** | **The role of GPIO4** (an input, but not interrupt-attached, so not a button); charge-STAT polarity; panel orientation |
-
-## Strengths / shortcomings
-
-**Strengths.** S3 + 8 MB PSRAM with **six real navigation keys and an IMU** — the
-only Xteink combining those. Native SDMMC. No touchscreen to fail. Cheaper to
-build than the Pro.
-
-**Shortcomings.** **Not purchasable internationally.** No frontlight. NVS is the
-only panel-controller source of truth, which makes cross-unit flash restores
-dangerous. GPIO4's role is unknown. **No teardown, no photograph, no price, no
-dimensions, no battery figure.**
-
-## Status: what is and is not known
-
-| Known | Not known |
-|---|---|
-| Complete pinout, all peripherals, partitions | **Price** — none ever published |
-| Stock firmware version (`xteink_app` 7.0.11) | **Availability** — no listing anywhere |
-| Board tag and revision string (`ESP32S3_X4R2_CLA`) | **Dimensions, mass, battery capacity** |
-| Full build configuration | **Any photograph of the device** |
-| That it exists and ships | **Whether it is sold under a different name in China** |
-
-## Partitions
-
-16 MB dual-OTA, **identical to the X4 Pro**: `nvs` `0x9000` · `otadata` `0xE000` ·
-`app0` `0x10000` · `app1` `0x7F0000` · `spiffs` `0xFD0000` · `coredump` `0xFE4000`.
-
-## Development
-
-```ini
-[env:x4c]
-extends = base
-board = esp32-s3-devkitc1-n16r8
-board_build.mcu = esp32s3
-build_flags =
-  ${base.build_flags}
-  -DBOARD_HAS_PSRAM
-  -DUSE_BLOCK_DEVICE_INTERFACE=1   ; SD is 1-bit SDMMC; SdFat needs the block-device interface
-  -DFREEINK_DEVICE_X4CLASSIC=1
-```
-Verbatim from `platformio.sample.ini`. `reported-working`.
-
-Auto-enables `FREEINK_DRIVER_SSD1677`, `FREEINK_DRIVER_UC8179`,
-`FREEINK_DRIVER_UC8279_X4`, `FREEINK_CAP_RTC`, `FREEINK_BATTERY_I2C_GAUGE`,
-`FREEINK_SD_SDMMC`. Leaves `FREEINK_CAP_TOUCH` and `FREEINK_CAP_FRONTLIGHT` **off**.
-
-Bricking risks, unlock procedure and toolchain are as the
-[X4 Pro](../x4-pro/development.md) — same SoC, same flash size, same ecosystem —
-**except** that the panel-controller selection cannot self-correct.
-
-## Sources
-
-| ID | What | URL | Retrieved | Establishes |
-|---|---|---|---|---|
-| XC01 | `BoardConfig.h` `XTEINK_X4_CLASSIC` L1615–1706 | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L1615-L1706> | 2026-09-04 | Full pinout, confidence levels, RE offsets |
-| XC02 | `docs/xteink-x4c-support.md` | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/docs/xteink-x4c-support.md> | 2026-09-04 | Board identity, NVS mapping, peripherals, partitions |
-| XC03 | `XteinkDetect.cpp` `applyXteinkDisplayController()` | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/XteinkDetect/src/XteinkDetect.cpp> | 2026-09-04 | The no-MISO special case and NVS mapping |
-| XC04 | `platformio.sample.ini` `[env:x4c]` | same commit | 2026-09-04 | Build flags |
-| XC05 | `x4-classic` collection | <https://www.xteink.com/collections/x4-classic/products.json?limit=250> | 2026-09-04 | **The collection exists and contains no device** |
-| XC06 | "Did we just spot a new X4 model?" | <https://old.reddit.com/r/XTEINK/comments/1ud0d9c/> | 2026-09-04 | Community identified it 2026-06-22, ~1 month pre-launch |
-
-## Gaps
-
-**Everything commercial.** No price, no listing, no photograph, no dimensions, no
-mass, no battery capacity, no availability date, no regional name. The
-**hardware** is better documented than the **product** — an unusual inversion, and
-a direct consequence of the only source being a firmware dump.
-
-Open technical questions: **GPIO4's role**; charge-STAT polarity; panel
-orientation; whether the `R2` in `ESP32S3_X4R2_CLA` implies an R1 that shipped.
-
-## See also
-
-[Family index](../README.md) · [X4 Pro](../x4-pro/README.md) — the board this is
-derived from · [X4](../x4/README.md) — where the four bottom keys come from
-
----
-
-# ROUND 2 — appended 2026-09-11. The X4 Classic launched.
-
-> **Everything above this line is the 2026-09-04 snapshot and has not been
-> altered.** Its headline — *"Not listed for international sale… contains no
-> device"* — was **correct on 2026-09-04 and is now superseded**. This section is
-> a fresh retrieval dated **2026-09-11** (the working session's clock; the task
-> brief said 2026-09-07, and the divergence is recorded in
-> [`research-log.md`](research-log.md) §0 because every `published_at` below is
-> read from the vendor's own API and must be trusted over either).
-
-## The answer, in one table
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | **XTEINK X4 Classic (X4 V2) Pocket eReader** | **[VENDOR]** product title, verbatim |
-| **"X4 V2" is not a separate SKU** | The vendor writes the alias **into its own product titles and FAQ** | **[VENDOR]** — see below |
-| Shopify product id | `9693091135729` | **[VENDOR]** `/products.json` |
-| Handle | `xteink-x4-classic-pocket-ereader` | **[VENDOR]** |
-| **`created_at`** | **2026-08-03 05:06:01 −0700** — drafted a month before launch | **[VENDOR]** |
-| **`published_at`** | **2026-09-06 19:57:20 −0700** | **[VENDOR]** |
-| **Price** | **US$79.00** (`compare_at_price` 89.00) | **[VENDOR]** |
-| SKUs | `X4Classic-gray`, `X4Classic-black` | **[VENDOR]** variant `sku` |
-| Bundle SKUs | `X4CW+BW`, `X4CB+BW`, `X4CW+BB`, `X4CB+BB` — reader + charging base, **US$95.00** (`compare_at` 105.00), added `2026-09-05` | **[VENDOR]** |
-| Colours | **Mist Gray**, **Space Black** | **[VENDOR]** |
-| Ship weight | `grams: 250` (packaged, not device mass) | **[VENDOR]** |
-| Availability | `available: true` on all six variants at retrieval | **[VENDOR]** |
-| FCC ID | **`2BTR9-X4C`**, filed and granted **2026-07-20** | **[REG]** |
-
-**The vendor's own accessory titles settle the naming question.** Four accessories
-published 2026-09-06 are named, verbatim:
-
-- `XTEINK X4 Classic (X4 V2) Tempered Glass Screen Protector` — SKUs `X4C-Tempered-{1,2,3}`
-- `XTEINK X4 Classic (X4 V2) Matte Screen Protector` — SKUs `X4C-Matte-{2,4,6}`
-- `XTEINK X4 Classic (X4 V2) Protective Case` — SKUs `X4C-ProtectiveC-{MW,MG}`
-- `XTEINK X4 Classic (X4 V2) Magnetic Case - Multiple Colors` — SKUs `X4C-MagneticC-{FG,MG,BP,RR,SB,CG}`
-
-and the product-page FAQ uses "X4 V2" in running prose for the same device
-(*"The **X4 V2** features a built-in magnetic ring on the back, with a slightly
-different position from the first-generation X4"*). **The "X4 v2" that the
-2026-09-04 sweep flagged as a vendor-confirmed September 2026 product is this
-device.** It is not a distinct model, and no distinct model exists between the X4
-and the X4 Pro. See [`product-history-and-family.md`](product-history-and-family.md).
-
-## Vendor specification block, retrieved 2026-09-11
-
-Read from the rendered product page's `DETAILS + DIMENSIONS` section, not from the
-`body_html` (which is empty for this product).
-
-| Vendor field | Vendor value | Comment |
-|---|---|---|
-| Display | **4.3 inch** | The firmware and every other Xteink document say **4.26″**. Vendor rounding; see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) §R2-3 |
-| Resolution | **219 PPI** | Mislabelled — 219 PPI is a *density*, not a resolution. It is arithmetically consistent with 800×480 on 4.26″ |
-| **Dimensions** | **114 × 69 × 4.9 mm** | First dimensional figure ever recorded for this device |
-| **Weight** | **68 g** | First mass figure. Lighter than the X3 (55 g is the X3; the X4 is ~74–80 g) |
-| Storage | **bundled 16 GB microSD**, expansion to 256 GB | No internal user storage; matches SDMMC-only design |
-| Connectivity | **Wi-Fi 2.4 GHz & Bluetooth** | Corroborated by the FCC grant (2412–2462 MHz, DTS) and by BLE power in the RF-exposure exhibit |
-| **Ports** | **Pogo Pin** | **No USB-C.** Resolves the "Charging: unknown" gap |
-| **Battery** | **920 mAh** | First capacity figure |
-| Supported formats | EPUB, TXT / BMP / fonts BIN, XTF | The same page's FAQ says *"TXT, EPUB, MOBI, PDF, XTCH, XTC, XTCZ"* — **the page contradicts itself**; recorded, not resolved |
-| Front light | **No** | Confirms the firmware. Refutes the 2026-06-22 community guess |
-| Touchscreen | **No** | Confirms the firmware |
-
-**Box contents** (vendor): 1 × X4 Classic reader · 1 × quick-start guide ·
-1 × microSD card · 1 × matte screen protector · 2 × adhesive metal ring ·
-1 × magnetic charging adapter.
-
-### Two vendor claims that are hardware findings
-
-1. **"Shake-to-Flip lets you turn pages by gently shaking the device."** This is
-   independent, vendor-side corroboration of the **QMI8658 IMU at 0x6B** that the
-   FreeInk profile lists — previously a single-source claim. A buttons-only reader
-   has no other reason to carry a six-axis IMU.
-   → [`qst/qmi8658a`](../../../components/qst/qmi8658a/README.md)
-2. **"built-in magnetic ring on the back, with a slightly different position from
-   the first-generation X4."** The magnet is *in the device*, not in the case, and
-   its position moved relative to the X4. Visible as an oval outline in the FCC
-   external photographs of the sibling X4 Light.
-
-## Regulatory record — the second custodian this record needed
-
-`ESP32S3_X4R2_CLA` and the FreeInk profile were, until now, the only evidence this
-device existed. There is now a US federal one.
-
-| Field | Value |
-|---|---|
-| **FCC ID** | **`2BTR9-X4C`** |
-| Grantee code / product code | `2BTR9` / `X4C` |
-| **Legal applicant** | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** (深圳小狐星曈科技 — note the **曈** spelling) |
-| Applicant address | Room 1209, Yichuang International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community, Guanlan Street, Longhua District, Shenzhen |
-| Applicant FRN | `0037772233` |
-| Responsible party | Chen Chu, `chuchen@xteink.cn` |
-| Related domain on the filing | **`xteink.cn`** — the domain the 2026-09-04 sweep found unreachable at the apex but referenced inside X4 stock firmware (`bofi.xteink.cn`). **The filing confirms it is the company's** |
-| Test lab | Shenzhen BKC Testing Co., Ltd. |
-| Application / final-action date | **2026-07-20** |
-| Equipment class | DTS — Digital Transmission System |
-| Frequency range | **2412–2462 MHz** (2.4 GHz only; no 5 GHz, consistent with ESP32-S3) |
-| BLE conducted peak power | **−0.87 dBm** (ch 0), −1.42 dBm (ch 19) — from the RF-exposure exhibit |
-| **Antenna** | **`KH3216-A35`**, Shenzhen Jinhangbiao Electronics Co., Ltd. — 3216 chip antenna, peak gain **2.30 dBi**, VSWR ≤ 2.0, 50 Ω, omnidirectional, efficiency 69–71.2 % → [`generic/kh3216-a35-chip-antenna`](../../../components/generic/kh3216-a35-chip-antenna/README.md) |
-
-### What the FCC filing does *not* yet give you, and exactly when it will
-
-The applicant filed a short-term confidentiality request. Four exhibits exist in
-the FCC's system but are served as **metadata only**:
-
-| Exhibit | Size | **Public from** |
-|---|---|---|
-| **Internal Photos** | 4.5 MB | **2027-01-16** |
-| External Photos | 825.3 KB | 2027-01-16 |
-| Users Manual | 2.9 MB | 2027-01-16 |
-| Test Setup Photos | 305.6 KB | 2027-01-16 |
-| Block Diagram · Schematics · Operational Description | 55.2 KB / 540.4 KB / 73 KB | **never** — long-term confidentiality, no release date |
-
-**A PCB teardown of this device is dated, not hypothetical: 2027-01-16.** That is
-the cheapest route to resolving the remaining open questions below, and it needs
-no hardware. A community member is already asking for PCB photographs for a
-specific reason ([r/xteinkereader `1wcgqub`](https://old.reddit.com/r/xteinkereader/comments/1wcgqub/),
-2026-09-10) — whether BM8563 `CLKOUT` reaches ESP32-S3 `GPIO15`/`XTAL_32K_P`,
-which would allow a low-power always-on BLE mode. Nobody had opened one at that
-date.
-
-Retained exhibits: [`artifacts/certification/`](artifacts/certification/README.md).
-
-## `R2` in `ESP32S3_X4R2_CLA` — resolved as far as the evidence allows
-
-The 2026-09-04 record flagged this as "implying an earlier revision 1 nobody has
-documented". New evidence changes the reading:
-
-1. An **X4 Pro** stock-firmware dump taken from a physical device on 2026-09-06
-   contains **all four board tags in one binary**: `ESP32S3_X4_TL`,
-   `ESP32S3_X4_TL_SSD1677`, **`ESP32S3_X4_CLA`** and **`ESP32S3_X4R2_CLA`**
-   ([`kycube/x4pro-emu` `docs/device/partitions.md`](https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/partitions.md)).
-   The tags are entries in **one shared vendor codebase compiled for every S3
-   board**, not a per-unit revision stamp. A string's presence therefore says
-   nothing about the unit it was dumped from.
-2. The **FCC grant is a single original-equipment filing**, `2BTR9-X4C`,
-   2026-07-20, with **no Class II permissive change** and no earlier X4C
-   application under grantee `2BTR9`. If an `R1` had been *sold in the US*, it
-   would need its own grant. **There is no such grant.**
-3. The vendor's own marketing calls this device the **second** version of the X4
-   ("X4 V2"), and the X4 has its own FCC ID (`2BTR9-XTEINKX4`, 2026-01-05). The
-   most economical reading of `X4R2` is **"X4, revision 2" — i.e. the X4C *is* the
-   R2, and the R1 is the original C3 X4**, not an unreleased X4C.
-
-**Verdict: `not-resolved, strongly constrained.** Reading (3) is consistent with
-every piece of evidence and requires no unobserved device. An engineering-sample
-X4C R1 that never reached retail cannot be excluded and never will be from public
-sources. **What would settle it:** the `SCH`/`BLOCK` exhibits (permanently
-confidential), an internal photograph showing a silkscreened revision (2027-01-16),
-or a second stock dump from a *known* X4C carrying a different revision string.
-The earlier statement that `R2` "implies an earlier revision 1 nobody has
-documented" is **narrowed**: it implies a revision 1, and revision 1 is most
-likely the plain X4.
-
-## Corrections to the specification table above
-
-| Field above | Was | Now | Source |
-|---|---|---|---|
-| Availability | "Not listed for international sale" | **Listed, in stock, US$79** | **[VENDOR]** |
-| Charging | unknown | **Pogo pin, 4-contact magnetic** | **[VENDOR]** + FCC external photos of the sibling X4L |
-| Dimensions / mass / battery | unknown | **114 × 69 × 4.9 mm · 68 g · 920 mAh** | **[VENDOR]** |
-| Stock firmware analysed | `xteink_app` v7.0.11 | v7.0.11 remains the only **X4C** version seen. The **X4 Pro** desk unit shipped **7.2.4** (2026-08-14) and a **7.5.4** analysis exists. No X4C-specific number is corroborated | **[DUMP]**, third-party |
-| `displaySpiHz` | 20 MHz | **10 MHz** — FreeInk changed every Xteink profile to a shared `XTEINK_DISPLAY_SPI_HZ = 10000000u` in commit `39606d5a` (2026-09-09, *"Fix e-ink display buffer tracking and optimize SPI writes"*) | **[SDK]** |
-
-## New round-2 documents in this record
-
-| File | What it adds |
-|---|---|
-| [`research-log.md`](research-log.md) | Every query, endpoint, UA and failure of the 2026-09-11 pass |
-| [`commands.md`](commands.md) | The Shopify, fccid.io, poppler and GitHub commands, with status labels |
-| [`product-history-and-family.md`](product-history-and-family.md) | The dated X4C timeline from first sighting to launch, and the "X4 v2" naming history |
-| [`community.md`](community.md) | Owner reports, the launch-week thread census, and the pogo/USB-C controversy |
-| [`projects-and-community.md`](projects-and-community.md) | Which firmware projects support the X4C, at which commit |
-| [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) | X4C against X4, X4 Pro, X3 and the Boox Picco |
-| [`performance.md`](performance.md) | What is and is not measured — mostly the latter, stated plainly |
-| [`resources-and-conflicts.md`](resources-and-conflicts.md) | GPIO/bus/rail ownership and the realistic concurrent-use cases |
-| [`examples/`](examples/catalog.json) | Example catalogue, search log and selection |
-| [`media/manifest.json`](media/manifest.json) | Image provenance |
-| [`artifacts/certification/`](artifacts/certification/README.md) | The five public FCC exhibits, hashed |
diff --git a/devices/xteink/x4-classic/acquisition/README.md b/devices/xteink/x4-classic/acquisition/README.md
deleted file mode 100644
index 1cb9936..0000000
--- a/devices/xteink/x4-classic/acquisition/README.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# Xteink X4 Classic — acquisition
-
-**No artifact was acquired for this device, because none is publicly available.**
-
-## Clean-clone commands
-
-None. There is nothing to fetch.
-
-## Wanted artifacts and their status
-
-| Artifact | Reacquisition | Notes |
-|---|---|---|
-| `flashx4c.bin` — the stock dump every fact here derives from | **`blocked`** | Referenced only inside `Free-Ink/freeink-sdk` documentation. No URL exists anywhere. The maintainers hold it privately. Options: ask upstream, or dump a unit |
-| Any X4C OTA package | **`blocked`** | None located |
-| Vendor OTA feed response | **`manual`** | `http://gotaserver.xteink.com/api/check-update` — endpoint recovered from the X4 dump. **Not queried this session.** Would need the model/version request format, which is unknown |
-| The June 2026 vendor video showing the device | **`manual`** | Referenced in [r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/); no stable link captured. Currently the only known imagery |
-| Any photograph | **`lost`** | None exists publicly |
-| A price or listing | **`lost`** | None exists |
-
-## Verification
-
-`manifest.json` in this directory is an **empty artifact list with a populated
-`wanted` list** — deliberately, so a verifier distinguishes "nothing was fetched"
-from "nobody looked".
diff --git a/devices/xteink/x4-classic/acquisition/manifest-fcc-exhibits.json b/devices/xteink/x4-classic/acquisition/manifest-fcc-exhibits.json
deleted file mode 100644
index b43ef89..0000000
--- a/devices/xteink/x4-classic/acquisition/manifest-fcc-exhibits.json
+++ /dev/null
@@ -1,43 +0,0 @@
-{
- "record": "devices/xteink/x4-classic",
- "generated": "2026-09-11",
- "note": "Sibling of `manifest.json`. That file's `artifacts` array is written inline as `[]`, so it cannot be extended without rewriting an existing line; this pass is append-only. Merge on the next non-append-constrained edit.",
- "artifacts": [
-  {
-   "id": "fcc-2BTR9-X4C-9480914",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2BTR9-X4C/Test-Report/Antenna-Report-9480914.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9480914",
-    "https://fcc.report/FCC-ID/2BTR9-X4C/9480914.pdf",
-    "https://fccid.io/2BTR9-X4C",
-    "https://web.archive.org/web/2/https://fccid.io/2BTR9-X4C/Test-Report/Antenna-Report-9480914.pdf"
-   ],
-   "sha256": "720ce021f0d403a69e7095bb5ef29f393cb49a8ad4676f8e2652245ffbd355cb",
-   "bytes": 1548468,
-   "destination": "devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-antenna-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-07-20",
-   "fcc_id": "2BTR9-X4C",
-   "fcc_document_id": "9480914",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Report",
-   "grant_date": "2026-07-20",
-   "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen BKC Testing Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/xteink/x4-classic",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ]
-}
diff --git a/devices/xteink/x4-classic/acquisition/manifest.json b/devices/xteink/x4-classic/acquisition/manifest.json
deleted file mode 100644
index 4da98be..0000000
--- a/devices/xteink/x4-classic/acquisition/manifest.json
+++ /dev/null
@@ -1,58 +0,0 @@
-{
-  "device": "xteink/x4-classic",
-  "generated": "2026-09-04",
-  "note": "No artifact was acquired. Every technical claim derives from Free-Ink/freeink-sdk at commit 24003795381a6c23630a26472ae3b06550333e71, which is a source repository rather than a device artifact.",
-  "artifacts": [],
-  "wanted": [
-    {
-      "id": "x4c-stock-dump",
-      "kind": "firmware-image",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x4-classic/artifacts/firmware/flashx4c.bin",
-      "retrieved": null,
-      "upstream_version": "xteink_app v7.0.11",
-      "license": "unknown (vendor firmware)",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "blocked",
-      "reason": "Referenced only inside the FreeInk SDK documentation; held privately by its authors. No public URL exists.",
-      "target_hardware": "Xteink X4 Classic, board tag ESP32S3_X4_CLA, revision ESP32S3_X4R2_CLA",
-      "notes": "Would confirm: partition layout, GPIO4's role, charge-STAT polarity, and the NVS hw_calib/screenType default as shipped."
-    },
-    {
-      "id": "x4c-vendor-video-2026-06",
-      "kind": "media",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x4-classic/media/",
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Referenced in https://old.reddit.com/r/XTEINK/comments/1ud0d9c/ ; no stable URL captured in the retrieved JSON.",
-      "notes": "Currently the ONLY known imagery of this device anywhere."
-    },
-    {
-      "id": "x4c-ota-feed",
-      "kind": "api-response",
-      "canonical_url": "http://gotaserver.xteink.com/api/check-update",
-      "sha256": null,
-      "bytes": null,
-      "destination": "scratch/xteink/vendor/",
-      "retrieved": null,
-      "license": "n/a",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Endpoint recovered by string extraction from the X4 (ESP32-C3) factory dump. Request format for the X4C is unknown. Not queried this session.",
-      "notes": "Plain HTTP. Would give the current stock version and possibly a download URL."
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-antenna-report.pdf b/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-antenna-report.pdf
deleted file mode 100644
index a741363..0000000
Binary files a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-antenna-report.pdf and /dev/null differ
diff --git a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-confidentiality-request.pdf b/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-confidentiality-request.pdf
deleted file mode 100644
index e742d12..0000000
Binary files a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-confidentiality-request.pdf and /dev/null differ
diff --git a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-label.pdf b/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-label.pdf
deleted file mode 100644
index 5ae9ae5..0000000
Binary files a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-label.pdf and /dev/null differ
diff --git a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-rf-exposure.pdf b/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-rf-exposure.pdf
deleted file mode 100644
index 27ea25c..0000000
Binary files a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-rf-exposure.pdf and /dev/null differ
diff --git a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-test-report.pdf b/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-test-report.pdf
deleted file mode 100644
index b87d3c8..0000000
Binary files a/devices/xteink/x4-classic/artifacts/certification/2BTR9-X4C-test-report.pdf and /dev/null differ
diff --git a/devices/xteink/x4-classic/artifacts/certification/README.md b/devices/xteink/x4-classic/artifacts/certification/README.md
deleted file mode 100644
index 19de921..0000000
--- a/devices/xteink/x4-classic/artifacts/certification/README.md
+++ /dev/null
@@ -1,99 +0,0 @@
-# FCC equipment-authorization exhibits — `2BTR9-X4C`
-
-Retrieved **2026-09-11** from `fccid.io` with UA `WhatsApp/2.23.20.0` (a
-desktop-Chrome UA is served **403**; `fcc.report` is 403 on every UA tried).
-Every file was validated by magic bytes (`%PDF`) before being retained, and text
-was extracted with poppler 26.06.0 and cross-checked against a heading visible in
-the rendered page.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-X4C`** |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. |
-| Grantee code / product code | `2BTR9` / `X4C` |
-| Device description | **XTEINK X4 Classic** |
-| Application / final action | **2026-07-20** |
-| Equipment class | DTS — Digital Transmission System |
-| Frequency range | 2412–2462 MHz |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Source page | <https://fccid.io/2BTR9-X4C> |
-| Grantee index | <https://fccid.io/2BTR9> |
-
-## Retained
-
-| File | Bytes | SHA-256 | What it establishes |
-|---|---:|---|---|
-| `2BTR9-X4C-label.pdf` | 189,803 | `605b978782399a0fdcf267848b5459981fd8069ec6e976e0240aff0bde72ba9c` | Compliance-label artwork and its position; a rear photograph showing the magnet outline and the four-contact pogo pad |
-| `2BTR9-X4C-test-report.pdf` | 3,214,822 | `ce40d2300f5ac63c1fb2bb5f8e79b1afcb4a07017a5a1f2b636821e52dc57c86` | 802.11b/g/n(HT20/HT40) duty cycle, OBW and 6 dB BW measurements, 51 pages. **Measurement data only — the EUT-description section is not in this exhibit** |
-| `2BTR9-X4C-antenna-report.pdf` | 1,548,468 | `720ce021f0d403a69e7095bb5ef29f393cb49a8ad4676f8e2652245ffbd355cb` | **Antenna part identity**: `KH3216-A35`, Shenzhen Jinhangbiao Electronics, peak gain 2.30 dBi, VSWR ≤ 2.0, 50 Ω, efficiency 69–71.2 % |
-| `2BTR9-X4C-rf-exposure.pdf` | 144,966 | `7004f25d9c721f88591842081ac337d0b024745ca7551931fa9d195afc9f92df` | Product name confirmation and **BLE conducted peak power −0.87 dBm (ch 0), −1.42 dBm (ch 19)** — independent evidence that BLE is fitted |
-| `2BTR9-X4C-confidentiality-request.pdf` | 121,559 | `6930195fcd9a7b0fd094a34b27dcf936e94828eeb67cb4dfbcfdd734d47baf19` | The applicant's own short- and long-term confidentiality request — **the document that sets the 2027-01-16 date** |
-
-Original URLs follow the pattern
-`https://fccid.io/2BTR9-X4C/<Type>/<Slug>-<DocumentID>.pdf`:
-
-- `…/Label/Label-and-Information-9480913.pdf`
-- `…/Test-Report/Test-Report-9480917.pdf`
-- `…/Test-Report/Antenna-Report-9480914.pdf`
-- `…/RF-Exposure-Info/RF-Exposure-Report-9480918.pdf`
-- `…/Letter/Short-Long-Term-Confidentiality-Request-9480932.pdf`
-
-## Not retained, because they are not public
-
-| Exhibit | Size reported | Public from |
-|---|---|---|
-| **Internal Photos** | 4.5 MB | **2027-01-16** |
-| External Photos | 825.3 KB | 2027-01-16 |
-| Users Manual | 2.9 MB | 2027-01-16 |
-| Test Setup Photos | 305.6 KB | 2027-01-16 |
-| **Block Diagram** | 55.2 KB | **never** (long-term confidentiality) |
-| **Schematics** | 540.4 KB | **never** |
-| Operational Description | 73 KB | **never** |
-
-Requesting the `.pdf` URL for a *"Metadata only"* exhibit does not return the
-document. **Re-check on or after 2027-01-16** — the internal photographs are the
-cheapest available route to a PCB-level verification of this record.
-
-Two further exhibits were **not** fetched because they are boilerplate:
-`Attestation-of-Covered-Equipment-2-911-d-5-i-ii-9480930.pdf` and
-`Attestation-Statements-of-US-Agent-for-Service-of-Process-2-911-d-7-9480929.pdf`,
-plus `Agent-Authorization-Letter-Template-9480931.pdf`. Their URLs are recorded
-here so the omission is recoverable.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`unknown`** — these are third-party submissions published by a US federal agency as part of a public authorization record. They are routinely mirrored by several commercial sites. **No explicit grant of redistribution was located**, and the FCC's publication is not itself a licence from the applicant |
-| Disposition | `repository`, **unstaged** — pending the user's decision |
-| Total retained | **5 files, 5,219,618 bytes** |
-
-## Cross-references
-
-Cited from [`../../README.md`](../../README.md) (§Regulatory record),
-[`../../media/manifest.json`](../../media/manifest.json),
-[`../../gaps-and-conflicts.md`](../../gaps-and-conflicts.md) and the component
-record [`components/generic/kh3216-a35-chip-antenna`](../../../../../components/generic/kh3216-a35-chip-antenna/README.md).
-
----
-
-## Correction, 2026-09-11 — redistribution is `allowed`, not `unknown`
-
-The *Licensing and disposition* table above records **`unknown`**. That was
-conservative but wrong, and it is superseded:
-
-| Field | Value, as of 2026-09-11 |
-|---|---|
-| Redistribution status | **`allowed`** |
-| Basis | FCC equipment-authorisation exhibits are **US Government public records**, published by the Commission under 47 CFR §2.1033. The agency asserts no copyright, and the exhibits are routinely republished by mirrors. |
-| Scope | Applies to every exhibit in this directory, and to every FCC exhibit elsewhere in this repository. |
-
-**The original rows above are left exactly as written.** This note supersedes
-their redistribution field only; their hashes, sizes and URLs remain correct and
-authoritative.
-
-Confidentiality embargoes are a **separate** matter and are unaffected: exhibits
-the applicant had withheld were never published, so there is nothing to
-redistribute until their release dates.
-
-Logged in [`scratch/index-merge/corrections-requiring-review.md`](../../../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-classic/certification-and-compliance.md b/devices/xteink/x4-classic/certification-and-compliance.md
deleted file mode 100644
index d906da2..0000000
--- a/devices/xteink/x4-classic/certification-and-compliance.md
+++ /dev/null
@@ -1,199 +0,0 @@
-# Certification and compliance — x4-classic
-
-Compiled **2026-09-11** by the round-2 index merge, from the certification pass's findings in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md). Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware.
-
-> **Why this arrived late.** These findings were produced on 2026-09-11 but written into `scratch/` because a sibling agent held `devices/xteink/` at the time. That conflict is over; this file is the properly-filed result.
-
----
-
-## 1. Summary
-
-**FCC: granted.** `2BTR9-X4C`, 2026-07-20.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2BTR9-X4C` — granted **2026-07-20** |
-| **CE / RED (EU)** | ⚠ no published DoC located; no database exists to search (§4) |
-| **UKCA** | ⚠ not determined (§4) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§4) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§4) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§4) |
-
-⚠ **This reverses the 2026-09-04 finding of *no FCC/CE filings*.** See §5.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Every
-probe below ran on **2026-09-11**, in one session, against one host, with one tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** — a real Xteink grant |
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** — M5Stack Cardputer |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**Positives → 200. Negatives → 404.** Raw run:
-`scratch/market-and-certification/logs/fcc-controls.txt`.
-
-These controls are the whole basis on which the absence findings below may be read as evidence.
-They are reproduced in each of the five Xteink records rather than referenced once, because a
-reader arriving at one device record must be able to judge that record's evidence without
-chasing a link.
-
-Beyond the ID probes, **the grantee was enumerated in full rather than guessed**: `2BTR9`
-yields **five** FCC IDs and no more. A product absent from a complete grantee listing is
-*absent*, not merely *un-found* — which is exactly the distinction the 2026-09-04 sweep could
-not make, because it had no grantee code to enumerate.
-
-⚠ **A counter-trap worth recording.** `https://fccid.io/2BTR9` prints **"6 FCC IDs"** in its
-page header, but the applications table lists **five**, and exactly five `href="/2BTR9…"` links
-exist in the HTML. The headline counter and the table disagree. **Trust the table.**
-
----
-
-## 3. The whole grantee — `2BTR9`
-
-| Field | Value |
-|---|---|
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** |
-| Grantee code | **`2BTR9`** |
-| Registered | **2025-12-21** |
-| Contact | Chen Chu |
-| Address | Room 1209, Yichuang International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community, Guanlan Street, Longhua District, Shenzhen, China |
-| FCC IDs | **5** |
-
-| FCC ID | Granted | Device | Purpose | Record |
-|---|---|---|---|---|
-| `2BTR9-X4L` | **2026-08-13** | XTEINK X4 Light | Original Equipment | [`x4-light`](../x4-light/README.md) |
-| `2BTR9-X4C` | **2026-07-20** | XTEINK X4 Classic | Original Equipment | [`x4-classic`](../x4-classic/README.md) |
-| `2BTR9-X4PRO` | **2026-06-16** | XTEINK X4 Pro | Original Equipment | [`x4-pro`](../x4-pro/README.md) |
-| `2BTR9-XTEINKX4` | **2026-01-05** | XTEINK X4 | Original Equipment | [`x4`](../x4/README.md) |
-| `2BTR9-XTEINKX3` | **2025-12-26** | XTEINK X3 | Original Equipment | [`x3`](../x3/README.md) |
-
-All five: 2402–2480 MHz (BLE) and 2412–2462 MHz (Wi-Fi, US channels 1–11). Long-term
-confidentiality granted on all five for Schematics, Block Diagram and Operational Description.
-
-**Not granted:** no FCC ID under `2BTR9` corresponds to the [**Xteink S4**](../s4/README.md) or
-the [**Xteink Nano**](../nano/README.md). Against a complete enumeration with passing controls,
-those two devices are **not FCC-authorised as of 2026-09-11**.
-
-Xteink filed **Original Equipment** authorisations, not module-based ones. The internal
-photographs show why: the X4 main PCB carries a **bare QFN SoC with a PCB meander antenna etched
-into the board**, not a drop-in pre-certified Espressif module. A design like that cannot
-inherit a module grant, so the vendor had to certify the whole device. That is consistent with,
-and corroborates, the grant record.
-
-
-### The `2BTR9-X4C` filing
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-X4C`** |
-| Device description | XTEINK X4 Classic |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Granted | **2026-07-20** |
-| Frequency ranges | 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Short-term confidentiality | Yes |
-| Exhibit rows | 12 |
-| Filing page | <https://fccid.io/2BTR9-X4C> — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld:**
-
-- User Manual [Users Manual 2027-01-16]
-- Internal Photos [Internal Photos 2027-01-16]
-- External Photos [External Photos 2027-01-16]
-- Test Setup Photos [Test Setup Photos 2027-01-16]
-- BLOCK [Block Diagram]
-- SCH [Schematics]
-- Operational Description [Operational Description]
-
-Internal **and external** photographs are **withheld until 2027-01-16**.
-
-**Exhibits obtained** — US Government public records, redistribution **`allowed`**. Downloaded 2026-09-11, magic bytes validated (`%PDF`).
-
-Retained in this record, at [`artifacts/certification/`](artifacts/certification/README.md):
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| [`2BTR9-X4C-antenna-report.pdf`](artifacts/certification/2BTR9-X4C-antenna-report.pdf) | 1,548,468 | `720ce021f0d403a69e7095bb5ef29f39…` | Test Report |
-
----
-
-## 4. Other jurisdictions
-
-| Regime | Result |
-|---|---|
-| **FCC (US)** | ✅ **granted** — see §1 |
-| **CE / RED (EU)** | ⚠ No published DoC located; no `xteink.com` certification page exists. CE is self-declared; **there is no database to search** |
-| **CE mark on product** | ⚠ **Not determined** — the `ID Label` exhibits were downloaded but not visually inspected for secondary marks. **Open work** |
-| **UKCA** | ⚠ Not determined; no database exists |
-| **SRRC / CCC (CN)** | ❌ **Not searched** — `wireless.miit.gov.cn` and `srrccn.org` both failed to connect. **Not an absence finding** |
-| **MIC 技適 (JP)** | ⚠ **Not searched** — endpoint reachable, not queried |
-| **ISED (CA)** | ⚠ **Not searched** — `sms-sgs.ic.gc.ca` returned 503 |
-
----
-
-## 5. ⚠ Correction — this supersedes the 2026-09-04 finding
-
-[`VERIFICATION-sweep-2026-09-04.md`](../../../VERIFICATION-sweep-2026-09-04.md) §6 recorded:
-
-> **Certification and regulatory records** were checked only for Xteink (where the finding was
-> that no external CE/FCC marking exists on the devices at all). No positive control was run, so
-> the absence is weaker evidence than it looks.
-
-That self-doubt was justified. The original finding confused **"no mark visible in a product
-photograph"** with **"no grant exists"**. They are different claims and only the first was ever
-tested.
-
-- ✅ **Survives:** "no FCC ID is printed on the exterior of the units we photographed." Not
-  re-tested here, and may well still be true.
-- ❌ **Refuted:** any reading that Xteink devices are uncertified or unauthorised for the US.
-  **Xteink holds five granted Original Equipment authorisations.**
-
-47 CFR §2.935 permits an **e-label** displayed in software instead of a printed mark, which is
-the ordinary arrangement for a device with a screen. **That is a likely explanation and it was
-not verified.**
-
-The original sentences in the sweep report and in the Xteink records have **not been edited**.
-Dated corrections sit beneath them, and every one is listed in
-[`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
----
-
-## 6. What this does **not** establish
-
-- **No hardware was inspected.** No Xteink unit was obtained, opened or powered.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit.
-- **CE is not established.** No published Declaration of Conformity was located and **there is
-  no CE database to search** — CE is a self-declaration regime. Absence of a published DoC is
-  not absence of conformity.
-- **The `ID Label` exhibits were downloaded but not visually inspected for secondary marks.**
-  Whether a CE mark appears on Xteink label artwork is **open work**, and cheap to close.
-- **SRRC / CCC (CN) did not run.** `wireless.miit.gov.cn` and `srrccn.org` both failed to
-  connect (`000`) on 2026-09-11. That is a method failure, **not** an absence finding.
-- **MIC 技適 (JP) did not run.** The endpoint is reachable (200) but form-driven; not queried.
-- **ISED (CA) did not run.** `sms-sgs.ic.gc.ca` returned 503.
-- **Schematics are permanently withheld** on all five filings, along with block diagrams and
-  operational descriptions. **The FCC is not a route to an Xteink schematic.**
-
-
-## 7. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| XC-1 | FCC ID `2BTR9-X4C` record | US FCC via fccid.io | **primary (regulatory)**, via mirror | regulatory record | <https://fccid.io/2BTR9-X4C> | 2026-09-11 | Grant existence, date, frequencies, exhibit list, embargo dates |
-| XC-2 | FCC grantee index `2BTR9` | US FCC via fccid.io | primary via mirror | regulatory record | <https://fccid.io/2BTR9> | 2026-09-11 | The complete five-device Xteink certification history |
-| XC-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
-⚠ Deep `fccid.io` paths serve **403 to a Chrome User-Agent** and **200 to `curl/8.5.0`** — an *inverted* block. The honest UA works; the disguised one does not. The **root** `https://fccid.io/` returns 200 to everything, so a reachability probe against the root reports a false success. **Probe a deep path.**
diff --git a/devices/xteink/x4-classic/commands.md b/devices/xteink/x4-classic/commands.md
deleted file mode 100644
index 5344491..0000000
--- a/devices/xteink/x4-classic/commands.md
+++ /dev/null
@@ -1,184 +0,0 @@
-# Commands — Xteink X4 Classic (X4C / "X4 V2")
-
-Every command here was run on **2026-09-11** on Linux, `bash`, unless marked
-otherwise. Status labels follow the repository convention:
-`executed-success` · `executed-failed` · `reported-working` · `inferred` ·
-`not-tested`.
-
-**No command in this file touched an Xteink device.** Every `executed-success`
-below is a network fetch, a parse, a hash or a PDF extraction. The device-side
-procedures are inherited from the [X4 Pro](../x4-pro/commands.md) and are marked
-`inferred` here because no X4 Classic has been in anyone's hands in this
-repository.
-
-## 1. Vendor catalogue (Shopify)
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-
-# Whole catalogue with published_at, SKUs, variants, prices, per-variant stock
-curl -s -A "$UA" 'https://xteink.com/products.json?limit=250&page=1' -o products-p1.json
-
-# The device's own record
-python3 - <<'PY'
-import json
-d=json.load(open('products-p1.json'))['products']
-p=[x for x in d if x['handle']=='xteink-x4-classic-pocket-ereader'][0]
-print(p['published_at'], p['created_at'])
-for v in p['variants']:
-    print(f"{v['sku']:20} {v['price']:>7}  compare_at={v['compare_at_price']}  avail={v['available']}  grams={v['grams']}")
-PY
-```
-
-- **Status:** `executed-success`.
-- **Expected output:** `2026-09-06T19:57:20-07:00 2026-08-03T05:06:01-07:00`, then
-  six variants: `X4Classic-gray` and `X4Classic-black` at `79.00`, and four
-  reader+base bundles at `95.00`.
-- **Why this and not the product page:** `published_at` is the only machine-readable
-  launch date the vendor emits. It cannot be back-dated by a theme edit.
-
-```bash
-# Per-collection listings — this is what proves the collection was empty before
-for h in accessories pocket-e-reader homepage-display machine x3-edm x3-series \
-         x4-classic x4-edm x4-pro-series x4-proedm x4-series; do
-  curl -s -A "$UA" "https://xteink.com/collections/$h/products.json?limit=250" -o "coll-$h.json"
-done
-```
-
-- **Status:** `executed-success` (11/11 HTTP 200).
-- **Gotcha:** `collections/<handle>/products.json` silently returns
-  `{"products":[]}` for an empty *or* nonexistent handle. Cross-check against
-  `/collections.json` before concluding a collection does not exist.
-
-## 2. The specification block is only in the HTML
-
-```bash
-curl -sL -A "$UA" 'https://xteink.com/products/xteink-x4-classic-pocket-ereader' \
-  -o x4c-product-page.html      # 919,867 bytes
-
-python3 - <<'PY'
-import re, html
-s = open('x4c-product-page.html', encoding='utf-8', errors='replace').read()
-i = s.find('DETAILS + DIMENSIONS')
-seg = re.sub(r'<(script|style|svg).*?</\1>', ' ', s[i-200:i+4000], flags=re.S)
-seg = html.unescape(re.sub(r'<[^>]+>', '\n', seg))
-print('\n'.join(l.strip() for l in seg.split('\n') if l.strip()))
-PY
-```
-
-- **Status:** `executed-success`.
-- **Expected output:** `Display 4.3 inch / Resolution 219 PPI /
-  Dimensions 114 × 69 × 4.9 mm / Weight 68g / … / Ports Pogo Pin /
-  Battery 920mAh / Front light No / Touchscreen No`.
-- **Why it is needed:** this product's `body_html` is the empty string. The
-  JSON API reports **no specifications whatsoever** for it.
-
-## 3. FCC — the UA matters, and so does validating the PDF
-
-```bash
-UA_OK='WhatsApp/2.23.20.0'
-
-curl -sL -A "$UA_OK" https://fccid.io/2BTR9-X4C  -o x4c.html    # 200
-curl -sL -A "$UA_OK" https://fccid.io/2BTR9      -o grantee.html # 200 — lists ALL Xteink FCC IDs
-
-# The document ids are in the page's own hrefs
-grep -o 'href="/2BTR9[^"]*"' x4c.html | sort -u
-
-# Exhibit download: append .pdf to the href
-curl -sL -A "$UA_OK" \
-  'https://fccid.io/2BTR9-X4C/Test-Report/Test-Report-9480917.pdf' \
-  -o 2BTR9-X4C-test-report.pdf
-
-# ALWAYS validate by content, never by extension
-python3 -c "print(open('2BTR9-X4C-test-report.pdf','rb').read(4))"   # -> b'%PDF'
-```
-
-- **Status:** `executed-success` for all 12 exhibits fetched across five FCC IDs.
-- **Failure modes actually observed, preserved:**
-  - `fccid.io` + desktop-Chrome UA → **403**. `WhatsApp/2.23.20.0` → **200**.
-  - `fcc.report/FCC-ID/2BTR9-X4C` → **403 on four different UAs**. No workaround found.
-  - `apps.fcc.gov/oetcf/eas/reports/GenericSearchResult.cfm?fcc_id=…` → **403**.
-- **Expected surprise:** exhibits marked *"Metadata only"* with a future date are
-  under a short-term confidentiality order. Requesting `<slug>-<id>.pdf` for them
-  does **not** return the document.
-
-## 4. PDF extraction (poppler via nix)
-
-```bash
-nix-shell -p poppler-utils --run 'pdftotext -layout in.pdf out.txt'
-nix-shell -p poppler-utils --run 'pdfinfo in.pdf'
-nix-shell -p poppler-utils --run 'pdfimages -png -f 1 -l 30 in.pdf outdir/p'
-```
-
-- **Status:** `executed-success`. poppler 26.06.0, verified 2026-09-11.
-- **Applied to:** `2BTR9-X4C-{test-report,antenna-report,rf-exposure,label}.pdf`
-  and the sibling X4L/X4Pro/X4/X3 exhibits.
-- **Text-layer validation performed:** the string `XTEINK X4 Classic` extracted
-  from `rf-exposure` matches the heading visible in the rendered page, and the
-  extracted `FCC ID 2BTR9-X4C` matches the page header stamped on every page.
-  **No value in this record was transcribed from an unvalidated text layer.**
-- **Trap:** `pdfinfo` on a saved HTML page emits dozens of
-  `Syntax Error … Illegal character` lines and then *"May not be a PDF file
-  (continuing anyway)"*. Treat that as a failed download, not a damaged PDF.
-
-## 5. Board-definition diff against the SDK at HEAD
-
-```bash
-SHA=9f4d3f9ca675e64cc9d616081f39a33cdefce57e
-gh api "repos/Free-Ink/freeink-sdk/contents/libs/hardware/BoardConfig/include/BoardConfig.h?ref=$SHA" \
-  --jq '.content' | base64 -d > BoardConfig-HEAD.h
-
-# Has a new Xteink board appeared?
-awk '/enum class Board/,/};/' BoardConfig-HEAD.h
-
-# What changed in this profile since the last sweep?
-diff <(awk '/constexpr BoardProfile XTEINK_X4_CLASSIC/,/^};/' BoardConfig-2400379.h) \
-     <(awk '/constexpr BoardProfile XTEINK_X4_CLASSIC/,/^};/' BoardConfig-HEAD.h)
-```
-
-- **Status:** `executed-success`.
-- **Expected output:** the enum is unchanged for Xteink; the profile diff is one
-  line, `20000000` → `XTEINK_DISPLAY_SPI_HZ` (`10000000u`).
-- **Why this is the first check to run:** a new board reaches the SDK **before**
-  it reaches the shop. A silent enum is real evidence that no new SKU exists.
-
-## 6. Proving a string's absence
-
-```bash
-gh api -X GET search/code -f q='"X4R1_CLA"' --jq '.total_count'   # -> 0
-gh api -X GET search/code -f q='"X4R2_CLA" xteink' \
-  --jq '.items[] | "\(.repository.full_name)  \(.path)"'
-```
-
-- **Status:** `executed-success`.
-- **Gotcha:** an unquoted, unscoped query such as `X4R1` returns ~50,000 junk
-  hits (it tokenises). **Quote the exact identifier** and add a scoping term.
-
-## 7. Reddit
-
-```bash
-UA_R='WhatsApp/2.23.20.0'
-curl -s -A "$UA_R" \
-  'https://old.reddit.com/r/XTEINK/search.json?q=%22X4+Classic%22+OR+%22X4+V2%22+OR+X4C&restrict_sr=1&sort=new&limit=100&t=year'
-
-# Comment trees carry the evidence; listings do not
-curl -s -A "$UA_R" 'https://old.reddit.com/r/XTEINK/comments/1v4824q.json?limit=200'
-```
-
-- **Status:** `executed-success`, 11/11 HTTP 200.
-- The FCC ID `2BTR9-X4C` was first published by a community member in a
-  **post body**, not a title — it is invisible to a title-only search.
-
-## 8. Device-side procedures — NOT executed
-
-| Procedure | Status | Note |
-|---|---|---|
-| Enter ROM download mode | `inferred` | The X4C has **no USB-C**. Native USB is on GPIO19/20 and reaches a pad set, not a socket. **The X4 Pro procedure does not transfer**; how a user gets a cable onto an X4C is **unknown and untested** |
-| `esptool chip-id` | `not-tested` on X4C | `executed-success` **on an X4 Pro by a third party** — see [`kycube/x4pro-emu` `docs/device/chip_id.txt`](https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/chip_id.txt) |
-| `esptool read-flash 0 0x1000000 flash.bin` | `reported-working` on X4 Pro | Third party dumped twice and both dumps hashed identically — the right way to prove a dump |
-| `pio run -e x4c -t upload` | `not-tested` | Build env exists in `platformio.sample.ini`; nobody in this repository has built it |
-| CrossPoint OTA install | `reported-working` | [r/CrossPointReader `1wbmagp`](https://old.reddit.com/r/CrossPointReader/comments/1wbmagp/) 2026-09-09, "Xteink X4 Classic support" — community thread, not verified here |
-
-**Do not present any row in that table as a verified X4C procedure.** The only
-hardware-executed commands anywhere in this family were run on an X4 Pro by a
-third party.
diff --git a/devices/xteink/x4-classic/community.md b/devices/xteink/x4-classic/community.md
deleted file mode 100644
index c49b136..0000000
--- a/devices/xteink/x4-classic/community.md
+++ /dev/null
@@ -1,207 +0,0 @@
-# Community and owner reports — Xteink X4 Classic
-
-Snapshot **2026-09-11**. Source: `old.reddit.com` JSON with UA
-`WhatsApp/2.23.20.0`, 11/11 requests HTTP 200. **94 unique posts** naming the X4
-Classic / X4 V2 / X4C were catalogued across six subreddits over a one-year
-window, plus **12 full comment trees**.
-
-**Every claim below is a community report and is labelled by evidence type.**
-Nothing here was measured by this repository. The device is **five days old**
-internationally at the snapshot date, so all owner reports come from either
-pre-release review units or the very first retail batch.
-
-## The sampling caveat that matters most
-
-Three of the six subreddits searched are Xteink-specific, **one of them is
-vendor-operated**, and the vendor runs a pre-release "Experts Program" that
-seeds review units. Two of the three most detailed reviews below say so in
-their own text. Treat the balance of sentiment in those subreddits as
-**unrepresentative**; the negative reactions are, if anything, more notable for
-appearing there at all.
-
-For contrast: `r/eink` returned **0** posts and `r/ereader` returned **1** for
-the same query over a year. This launch is almost invisible outside the
-vendor-adjacent communities.
-
-## Launch-week volume
-
-| Date | Posts naming X4C/X4 V2 in the catalogued set |
-|---|---:|
-| 2026-04-23 → 2026-08-29 | 28 (speculation era) |
-| 2026-09-03 | 2 — **the announcement** |
-| 2026-09-04 | 5 |
-| 2026-09-05 | 13 — **peak**, the review embargo lifting |
-| 2026-09-06 → 09-08 | 16 |
-| 2026-09-09 → 09-11 | 30 |
-
-## The announcement — vendor, firsthand, primary
-
-| Field | Value |
-|---|---|
-| Author | **u/xteink** — the vendor's own account |
-| Post | [r/xteinkereader `1w63yyl`](https://old.reddit.com/r/xteinkereader/comments/1w63yyl/), 2026-09-03, **806 points, 300 comments** |
-| Title | *"We're turning a new page on the X4."* |
-| Body, verbatim and complete | *"A familiar idea, refined for everyday reading. **X4 Classic (X4 V2) is coming soon.** We'll share more details shortly."* |
-
-**This is the vendor stating the two names as one product, three days before
-listing it.** It is the strongest non-API evidence for the naming question and
-it predates the store listing.
-
-The top comments are, almost uniformly, a request for a *different* device:
-
-| Score | Author | Comment |
-|---:|---|---|
-| 210 | u/xtremis | *"Damn, you were swallowed by the Anbernic syndrome! I'm waiting for my X3 DS Pro Plus with integrated stylus 🫠"* |
-| 166 | u/Kiras_ | *"I would be fine with just a better screen contrast and pixel density"* |
-| 92 | u/ashraf_bashir | *"X3 with light, that's it!"* |
-| 77 | u/iclazz169 | *"Need and x3 with light"* |
-| 65 | u/seijurogouu | *"i'd be interested in an X3 Pro. x3 size but with touch and light"* |
-
-**Four of the five highest-scoring replies to the vendor's own launch teaser ask
-for a frontlight.** This is the context for the [X4 Light](../x4-light/README.md)
-filing, which was already at the FCC when this was posted.
-
-## Firsthand owner reviews
-
-### R1 — pre-release unit, positive
-
-[r/XTEINK `1w7wjw2`](https://old.reddit.com/r/XTEINK/comments/1w7wjw2/), u/Which_Heart_983,
-2026-09-05, **279 pts / 120 comments**. Self-identified: *"I was lucky to receive
-this sneak peek version."* **Firsthand use of a vendor-supplied unit.**
-
-Claims, each a subjective firsthand impression unless noted:
-
-- *"surprised me with how light and slim it is… they have managed to make it
-  **slimmer than an X3**"* — consistent with the vendor's 4.9 mm against the
-  X3's published thickness, but **not measured here**.
-- *"In the second picture you can see how much darker the letters are"* —
-  **contrast**, not resolution. The same reviewer confirms, in reply to a direct
-  question about pixel density: **u/scamper_ *"It does not, it's still 219"***.
-  So: same panel density, claimed better contrast. Unresolved whether this is a
-  panel change, a waveform change, or observer bias.
-- *"**button placement is identical to the X4 Pro**"* — two side keys. Agrees
-  with the FreeInk profile's `GPIO0` / `GPIO7` side pair.
-- *"Has a clock"* → the BM8563 RTC. *"**Shake to turn page**"* → the QMI8658 IMU.
-  Both are **owner-observed corroboration of firmware-only claims**.
-- *"Items in the box are identical to the X4 Pro."*
-- Con: *"Pogo pin… the in box connectors are bad. I use the X3 cable."*
-
-### R2 — pre-release unit, mixed
-
-[r/XTEINK `1w8bfew`](https://old.reddit.com/r/XTEINK/comments/1w8bfew/), u/Comprehensive_Oil426,
-2026-09-05, 98 pts. *"I had the privilege of receiving an X4C to review."*
-
-- *"This device is thin! … I thought I might break it if I squeezed too hard"*
-- *"much more faster and intuitive than the X3"* — **stock firmware**, no
-  reflash, no timings given.
-- *"I also feel a slight improvement in the screen resolution"* — **this is the
-  contrast claim restated as a resolution claim, and it is wrong**: the density
-  is unchanged at 219 PPI. A good example of why *"better screen"* reports in
-  this family must be read carefully.
-- Refuses to publish cons yet: *"it would be unfair if it turned out to be a
-  skill issue."*
-
-### R3 — "Experts Program" unit, comparative, the most useful
-
-[r/xteinkereader `1wbxvvg`](https://old.reddit.com/r/xteinkereader/comments/1wbxvvg/),
-u/ajcabrera, 2026-09-09, **201 pts / 39 comments**. Owns X4C **and** X4 **and**
-X4 Pro. **TL;DR in the author's own words: *"It's nice and light, but if you
-already have an X4 or X3, save your coins."***
-
-| Claim | Evidence type |
-|---|---|
-| *"substantially lighter than the X4… reduction in width"* | firsthand comparison, no scale used |
-| *"side buttons on the left and right sides like the X4 Pro makes page scrolling a lot easier"* | firsthand |
-| *"**Both use the same 219 PPI screen** I believe… only noticeable when directly comparing text side-by-side"* | firsthand, **explicitly hedged** |
-| *"**Battery Capacity** — a few extra days from 100 % to 0 % when comparing both devices"* | firsthand, uncontrolled. Consistent with 920 mAh vs the X4's unpublished capacity, but **not a measurement** |
-| *"Stock firmware feels very snappy… prefer the reading speed on stock vs Crosspoint"* | firsthand, subjective |
-
-### R4 — X4 vs X4 Classic side by side
-
-[r/XTEINK `1wdo4sa`](https://old.reddit.com/r/XTEINK/comments/1wdo4sa/), 2026-09-11,
-u/Every_Purpose_1152 owns *"each iteration of the XTEINK devices"*. Cross-posted
-to r/xteinkereader as [`1wdo7xw`](https://old.reddit.com/r/xteinkereader/comments/1wdo7xw/).
-
-### R5 — retail-store review, verbatim from the vendor's own page
-
-Judge.me review on `xteink.com`, reviewer **"anne vla"**, 5 stars, captured
-2026-09-11. **A vendor-hosted review — curation cannot be excluded.** Quoted
-because it is the only side-by-side X4-vs-X4C account outside Reddit:
-
-> *"I already have the original XTEINK X4, in black and decided to go for the
-> Classic in grey. Other than the pogo adapter I didn't expect a big difference
-> but I think there is… The biggest improvement for me is definitely the buttons.
-> The placement of them is different from the V1 and so much better… The only
-> thing I'm not crazy about is the pogo charger. I would still prefer USB-C."*
-
-Note the reviewer's own shorthand: **"the V1"** for the original X4. That usage
-is independent support for the reading of `ESP32S3_X4R2_CLA` given in
-[`README.md`](README.md) §`R2`.
-
-## The two controversies
-
-### 1. Price — the loudest thread is not a review
-
-[r/XTEINK `1w9jzpn`](https://old.reddit.com/r/XTEINK/comments/1w9jzpn/) "X4 Classic price",
-2026-09-07, 60 pts / 49 comments. Dated, region-specific figures from owners:
-
-| Observation | Region | Date | Source |
-|---|---|---|---|
-| X4 Classic **€89**, X4 Pro **€110** | EU | 2026-09-07 | u/macien12, post body |
-| *"earlier batches were widely available closer to €40"* | EU | pre-2026-09 | same, hearsay |
-| X4 bought at **£47.70 ≈ €58** | UK | *"last minute"*, pre-launch | u/wowsomuchempty, firsthand purchase |
-| *"the original X4 at around €60 was unbeatable"* | EU | pre-2026-09 | u/ShrubbyFire1729 |
-| *"the X4C costs about 30 % more than original X4"* | — | 2026-09-10 | u/chicco1973, 40 pts |
-
-**The €89 EU price against the US$79 store price is a tax/region difference, not
-a contradiction** — but neither was normalised by this research, and the €40
-figure is hearsay. See [`market-and-pricing.md`](market-and-pricing.md).
-
-### 2. Pogo pin instead of USB-C
-
-The dominant complaint, and it has a regulatory edge. Two threads:
-
-- [r/xteinkereader `1w9r7rf`](https://old.reddit.com/r/xteinkereader/comments/1w9r7rf/),
-  2026-09-07, **199 pts / 286 comments**: *"the lack of USB-C makes the X3, X4
-  Pro, and X4 Classic illegal to sell in the EU"*. **Contested in its own
-  thread**: u/ShrubbyFire1729 — *"Including the POGO to USB adaptor is enough to
-  satisfy the EU requirement."* **This repository takes no position**; it is a
-  legal question, the arguments are hearsay on both sides, and no directive
-  citation was produced by either side.
-- [r/xteinkereader `1wagbmu`](https://old.reddit.com/r/xteinkereader/comments/1wagbmu/),
-  2026-09-08, **616 pts / 730 comments** — *"A Letter from Crusoe, Founder of
-  XTEINK: Pogo, USB-C, and Where We're Going"*. **The largest thread in the
-  history of this family.** A founder statement; primary, but vendor-sourced.
-
-## Firmware community
-
-| Thread | Date | Content |
-|---|---|---|
-| [r/CrossPointReader `1wbmagp`](https://old.reddit.com/r/CrossPointReader/comments/1wbmagp/) | 2026-09-09 | "Xteink X4 Classic support" |
-| [r/XTEINK `1wctkd6`](https://old.reddit.com/r/XTEINK/comments/1wctkd6/) | 2026-09-10 | "Crosspoint or Crossink? Differences on x4 classic" |
-| [r/xteinkHax `1wdfpij`](https://old.reddit.com/r/xteinkHax/comments/1wdfpij/) | 2026-09-11 | *"Anyone to test my firmware on X4 Classic?"* — a developer **without** the hardware |
-| u/Diirge in `1wbxvvg` | 2026-09-10 | *"CrossPoint sleep screen rendering got much better as of today on the x4c"* — firsthand, dated, on-device |
-
-## The teardown that does not exist yet
-
-[r/xteinkereader `1wcgqub`](https://old.reddit.com/r/xteinkereader/comments/1wcgqub/),
-2026-09-10. A request for *"high-resolution photos of both sides of the PCB,
-ideally with the ESP32-S3 and BM8563 RTC area clearly visible"*, to determine
-**whether BM8563 `CLKOUT` (pin 7) reaches ESP32-S3 `XTAL_32K_P` / GPIO15** — which
-would enable a low-power always-on BLE mode with the CPU in light sleep.
-
-The only reply, u/scarf__barf: *"there's only a handful of units circulating in
-the publics' hands right now… More people will have the X4 Classic delivered in
-~7-10 days."*
-
-**Status: open.** No X4 Classic PCB photograph existed anywhere on 2026-09-10.
-The FCC internal photographs become public **2027-01-16** and will answer it.
-See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-## One thing the community got wrong, preserved
-
-The 2026-06-22 sighting ([r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/),
-300 pts) predicted *"Physical buttons + frontlight but no touchscreen"*. The
-buttons and the absence of touch were right. **The frontlight was wrong**, and
-the vendor's own spec block now says `Front light: No`. The same hope recurred
-through six further threads between June and September and was wrong every time.
diff --git a/devices/xteink/x4-classic/comparisons-and-recommendations.md b/devices/xteink/x4-classic/comparisons-and-recommendations.md
deleted file mode 100644
index e22caa0..0000000
--- a/devices/xteink/x4-classic/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# Comparisons and recommendations — Xteink X4 Classic
-
-Dated **2026-09-11**. Prices are vendor-direct, item-only, worldwide from
-Shenzhen, read from `xteink.com/products.json`. **Nothing here was benchmarked.**
-
-## 1. Against its own family
-
-| | [X3](../x3/README.md) | [X4](../x4/README.md) | **X4 Classic** | [X4 Pro](../x4-pro/README.md) |
-|---|---|---|---|---|
-| **Price, 2026-09-11** | **$69** | **withdrawn** | **$79** | **$99** |
-| Status | in stock | **gone — accessories withdrawn too** | in stock, 9 days old | in stock |
-| SoC | ESP32-C3 | ESP32-C3 | **ESP32-S3** | ESP32-S3 |
-| PSRAM | none | none | **8 MB** | 8 MB |
-| Panel | 3.7″ 792×528 | 4.26″ 800×480 | 4.26″ 800×480 | 4.26″ 800×480 |
-| **PPI** | **~257** | ~219 | ~219 | ~219 |
-| Mass | **55 g** | ~74–80 g | **68 g** | not published |
-| Thickness | not published | not published | **4.9 mm** | not published |
-| Battery | 650 mAh | not published | **920 mAh** | not published |
-| Touch | ✗ | ✗ | ✗ | **GT911** |
-| Frontlight | ✗ | ✗ | ✗ | **dual warm/cool** |
-| Buttons | 6 (ADC ladder) + pwr | 6 (ADC ladder) + pwr | **6 discrete ISR + pwr** | **2** + pwr |
-| IMU | **QMI8658** | ✗ | **QMI8658** | ✗ |
-| NFC tag | **✅** | ✗ | ✗ | ✗ |
-| RTC | DS-series (unresolved) | **none** | BM8563 | BM8563 |
-| Gauge | **BQ27220** | bare ADC | CW2017 | CW2017 |
-| Storage | SPI, shared with display | SPI, shared | **native SDMMC** | native SDMMC |
-| Charging | pogo | **USB-C** | pogo | pogo |
-| Panel selection | live bus probe | live bus probe | **NVS only — no MISO** | live bus probe |
-| **FCC ID** | `2BTR9-XTEINKX3` | `2BTR9-XTEINKX4` | **`2BTR9-X4C`** | `2BTR9-X4PRO` |
-| Public FCC **internal** photos | **✅ since 2026-06-24** | **✅ since 2026-07-04** | **2027-01-16** | **2026-12-12** |
-
-### Reading the table
-
-**The X4 Classic is not an upgrade over the X4 Pro and was never meant to be.**
-It is the X4 Pro's board with the two most expensive parts — the capacitive
-touch layer and the dual-channel frontlight — deleted, the freed GPIOs turned
-into four more buttons, and an IMU added. Priced US$20 below.
-
-**It is also not a straight upgrade over the X4 it replaces.** It gains a much
-faster SoC with PSRAM, native SDMMC, a real RTC, an I²C fuel gauge, an IMU, a
-published 920 mAh cell, six discrete interrupt-driven buttons instead of an ADC
-ladder, and 4.9 mm / 68 g. **It loses USB-C**, and it costs about 30 % more than
-the X4 did at the same list price point. The most-repeated community complaint
-is exactly that trade, and it is a fair one.
-
-**The X3 still has the sharpest screen in the family** (~257 PPI vs ~219) and
-the best battery instrumentation (a BQ27220 that needs no profile upload). The
-X4 Classic's advantages over the X3 are size, speed, memory, storage path and
-capacity — not image quality.
-
-**One thing the Pro does not have and this does: an IMU.** The Pro has no
-QMI8658. If you want motion input on an S3 Xteink, the X4 Classic is the only
-one that has it.
-
-## 2. What it is genuinely better at than anything else in the family
-
-| Use | Why |
-|---|---|
-| **Buttons-only reading on an S3** | Six discrete ISR keys, no touch layer between you and the glass. The Pro has two keys; the C3 X4 has six but on an ADC ladder and a much slower SoC |
-| **Firmware development with real storage** | Native SDMMC *and* 8 MB PSRAM *and* a dual-OTA table with a free 8 MB slot. The X3 and X4 share their SD bus with the display |
-| **Motion input** | The only S3 Xteink with an IMU |
-| **Pocket weight** | 68 g / 4.9 mm for a 4.26″ panel |
-
-## 3. What to buy instead, by need — dated 2026-09-11
-
-| You want… | Buy | Confidence |
-|---|---|---|
-| Sharpest text, lightest, most sensors, cheapest new | **X3, $69** | high |
-| Touch **and** a frontlight | **X4 Pro, $99** | high |
-| **Any frontlight at all** | **Nothing in this family.** Wait for the [X4 Light](../x4-light/README.md), FCC-certified 2026-08-13, **unannounced and unpriced** — or buy a Kindle | **low — the X4L's feature set is not established** |
-| **USB-C** | **Used X4 only.** It is withdrawn and its accessories are gone | high |
-| Six real buttons on an S3, plus an IMU, plus SDMMC | **X4 Classic, $79** | high |
-| A schematic, headers, and no unlock dance | [M5Stack PaperMono](../../m5stack/papermono/README.md) or a Waveshare board | high |
-| Cheapest possible entry into this ecosystem | **Used X4, ~$16–58 observed** | medium |
-
-## 4. Against the outside world
-
-### Boox Picco — the live competitive question
-
-Announced at **US$100**, *expected November 2026*
-([r/XTEINK `1w938ab`](https://old.reddit.com/r/XTEINK/comments/1w938ab/),
-2026-09-06, 282 pts / 175 comments; and
-[`1wdurfy`](https://old.reddit.com/r/XTEINK/comments/1wdurfy/), 2026-09-11).
-
-**This repository has no primary data on the Picco** — no specification page, no
-FCC filing, no teardown was retrieved. The only thing that can honestly be said
-is that a $100 Android-class competitor is expected two months out, and that the
-X4 Classic's $79 is not a comfortable margin against it. **Do not treat any
-X4C-vs-Picco comparison in this repository as evidence.**
-
-### Development boards
-
-The comparison the community makes constantly, and it remains close to
-meaningless:
-
-| | X4 Classic | [PaperMono](../../m5stack/papermono/README.md) | [Waveshare ESP32-S3-ePaper-3.97](../../waveshare/esp32-s3-epaper-3.97/README.md) |
-|---|---|---|---|
-| Class | **sealed reader** | dev board | dev board |
-| Schematic | ✗ (FCC schematic exhibit is **permanently confidential**) | **✅ 6 sheets** | partial |
-| Headers | ✗ | ✅ | ✅ |
-| Enclosure, battery, case ecosystem | **✅** | ✗ | ✗ |
-| Unlock needed | often | ✗ | ✗ |
-| Price | $79 | — | — |
-
-**These are partial substitutes, not equivalents.** A dev board is the right
-answer if you want to *build*; a sealed Xteink if you want to *read* on something
-you can also reflash. The X4 Classic is a slightly better development target
-than its siblings — S3, PSRAM, SDMMC, dual-OTA — and a slightly worse one in one
-specific way: **no MISO on the panel bus**, so a wiped NVS leaves firmware unable
-to identify its own display controller.
-
-## 5. Honest verdict
-
-Buy the X4 Classic if you want a **buttons-only 4.26″ pocket reader on modern
-silicon** and you can live without a frontlight and without USB-C. It is, on the
-vendor's own numbers, the thinnest and second-lightest device in the family, with
-the largest published battery.
-
-Do **not** buy it as an upgrade from an X4 or X3. The most careful reviewer with
-all three devices in hand concluded exactly that — *"if you already have an X4 or
-X3, save your coins"* — and the panel density, which is what most people mean
-when they say "better screen", **has not changed**.
-
-Do **not** buy it expecting the frontlight the community has been asking for
-since April. That is a different, already-certified device that has not been
-announced.
diff --git a/devices/xteink/x4-classic/compatibility-and-status.md b/devices/xteink/x4-classic/compatibility-and-status.md
deleted file mode 100644
index 98217d3..0000000
--- a/devices/xteink/x4-classic/compatibility-and-status.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# Xteink X4 Classic — compatibility and status
-
-Snapshot **2026-09-04**.
-
-## Status in one line
-
-**A fully-specified board with no users.** The FreeInk SDK ships a complete,
-confidence-annotated profile; nobody outside the SDK's authors has been observed
-to own, flash, build for, or write about this device.
-
-## Software support
-
-| Project | X4C support | Evidence |
-|---|---|---|
-| **FreeInk SDK** | ✅ `BoardConfig::XTEINK_X4_CLASSIC`, `[env:x4c]`, all three panel drivers | source |
-| CrossPoint Reader / CrossInk / forks | **inherits** whatever the SDK provides; **no X4C-specific work found** | ~200-repo census |
-| Anything X4C-specific | **none exists** | same |
-
-## Working — by reverse engineering, not by report
-
-Display (all three controllers), seven interrupt-driven buttons, native SDMMC with
-the GPIO6 power cycle, BM8563 RTC, CW2017 gauge, QMI8658 IMU, GPIO1 rail, USB.
-All at **HIGH** confidence in the SDK's own annotation, none demonstrated publicly.
-
-## Partial / pending
-
-| Item | State |
-|---|---|
-| **GPIO4** | Configured as an input by stock, never read. **Role unknown** |
-| **Charge-STAT polarity** | Carried from the X4 Pro, marked `PENDING` |
-| **Panel orientation** | `NO_FLIP`, pending hardware |
-| **Bezel insets** | Inherited from the X4 Pro, *"pending measurement"* |
-| **USB lock** | Family-wide behaviour assumed; **no X4C report exists** |
-
-## The one risk that is worse here than anywhere else
-
-**Panel-controller selection cannot self-correct.** Every other Xteink probes the
-display bus at boot and overrides a wrong NVS value. The X4C has no MISO, so
-`hw_calib/screenType` is authoritative and unchecked. A full-flash restore from
-another unit can leave the device permanently driving the wrong controller.
-
-This turns a routine, safe operation elsewhere in the family into a
-device-specific hazard. See [`factory-firmware.md`](factory-firmware.md).
-
-## Hardware-revision keyed
-
-Two axes, **neither externally visible and neither observed**:
-
-1. **Panel controller** — SSD1677 / UC8179 / UC8279, recorded in NVS.
-2. **Board revision** — the string `ESP32S3_X4R2_CLA` implies at least an `R2`.
-   **No R1 has been seen**, and it is unknown whether one shipped.
-
-## Conflicting reports
-
-One, and it is about identification rather than behaviour: the community that
-first spotted this device in a vendor video reported it as having a **frontlight**
-([r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/), 300 pts).
-The firmware is unambiguous that it does not. **Firmware wins.** See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md), which also records a later
-hearsay claim that a *different* buttons-plus-frontlight model may exist.
-
-## Lifecycle
-
-**Unknown.** A vendor Shopify collection `x4-classic` exists and is **empty of
-devices**. No launch announcement, no price, no listing, no discontinuation
-notice. Either a China-only product, a provisioned-but-unlaunched international
-SKU, or both.
-
----
-
-## Round 2 — status as at 2026-09-11
-
-**No line above was altered.**
-
-| Item | Status | Revision / version | Evidence class |
-|---|---|---|---|
-| **Product exists and is buyable** | ✅ **working** | listed 2026-09-06, US$79 | vendor API |
-| FreeInk SDK `[env:x4c]` | ✅ profile present | commit `9f4d3f9`, 2026-09-10 | source |
-| FreeInk `displaySpiHz` | ⚠ **changed** 20 → **10 MHz** | commit `39606d5a`, 2026-09-09 | source |
-| CrossPoint Reader on X4C | 🟡 **reported-working** | undated build, 2026-09-10 | community, firsthand (u/Diirge: *"CrossPoint sleep screen rendering got much better as of today on the x4c"*) |
-| CrossInk on X4C | ❓ discussed, unverified | — | community ([r/XTEINK `1wctkd6`](https://old.reddit.com/r/XTEINK/comments/1wctkd6/)) |
-| Draftling `xteink_x4_classic` | 🟡 **builds, never run on X4C** | commit `92ba7e5` | author's own statement |
-| Stock firmware | ✅ ships and works | version **unknown** on X4C; v7.0.11 was the dump FreeInk analysed | inference |
-| BM8563 RTC present | ✅ **corroborated** | — | owner: *"Has a clock"* |
-| QMI8658 IMU present | ✅ **corroborated twice** | — | vendor ("Shake-to-Flip"); owner: *"Shake to turn page"* |
-| BLE radio present | ✅ **corroborated** | — | **FCC RF-exposure exhibit**, BLE conducted peak −0.87 dBm |
-| Wi-Fi 2.4 GHz b/g/n | ✅ | 2412–2462 MHz | **FCC grant** |
-| Wi-Fi 5 GHz | ❌ **absent** | — | FCC grant covers 2.4 GHz only |
-| Frontlight | ❌ **absent — settled** | — | vendor spec block `Front light: No`; firmware; two reviews |
-| Touchscreen | ❌ absent | — | vendor spec block; firmware |
-| USB-C | ❌ **absent** | — | vendor spec block `Ports: Pogo Pin` |
-| USB-MSC | ❓ SDK-supported, **no socket on the enclosure** | — | inference from the spec block + FCC label photograph |
-| Panel controller in retail units | ❓ **unknown** | `hw_calib/screenType` is factory-set per unit | — |
-| Anything measured | ❌ **nothing** | — | see [`performance.md`](performance.md) |
-
-### Regression risk introduced since the last snapshot
-
-A firmware built from FreeInk **before** `39606d5a` clocks the panel at 20 MHz;
-upstream now recommends 10 MHz for every Xteink board, and the commit message
-names a display-buffer-tracking bug. Anyone carrying a pinned pre-`39606d5a`
-build should read that commit before blaming the hardware for artefacts.
diff --git a/devices/xteink/x4-classic/coverage.md b/devices/xteink/x4-classic/coverage.md
deleted file mode 100644
index 5711c50..0000000
--- a/devices/xteink/x4-classic/coverage.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# Xteink X4 Classic — feature coverage
-
-Snapshot **2026-09-04**. "Evidence" here means the FreeInk SDK's Ghidra analysis
-of a stock dump, unless stated. **Nothing was tested by this session, and no
-third party has ever reported using this device.**
-
-| Feature | Hardware | Official docs | Community evidence | Guide | Confidence | Gaps |
-|---|---|---|---|---|---|---|
-| Display 800×480 | SSD1677 / UC8179 / UC8279 | none | **none** | [`pinouts`](pinouts-and-buses.md) | **HIGH** (RE) | Panel module part; orientation |
-| **Controller selection** | **NVS `hw_calib/screenType` only** | none | none | [`factory-firmware`](factory-firmware.md) | **HIGH** | **No live probe possible — no MISO** |
-| Buttons ×7, interrupt-driven | GPIO 0/2/3/5/7/8/9 | none | none | [`pinouts`](pinouts-and-buses.md) | **HIGH**, map corrected on hardware | — |
-| **GPIO4** | plain input, no ISR | none | none | — | **PENDING** | **Role entirely unknown** |
-| microSD, native SDMMC 1-bit | 41/42/40 + EN **6** active-LOW | none | none | [`pinouts`](pinouts-and-buses.md) | **HIGH** | Max card size |
-| RTC BM8563 | 0x51 | none | none | [`pinouts`](pinouts-and-buses.md) | **HIGH** | Backup power source |
-| Fuel gauge CW2017 | 0x63 | none | none | [`pinouts`](pinouts-and-buses.md) | **HIGH** | **Battery capacity unknown**; needs BATINFO upload |
-| **IMU QMI8658** | 0x6B, `WHO_AM_I` 0x05, no INT | none | none | [`pinouts`](pinouts-and-buses.md) | **HIGH** (`CTRL1/2/3/7` init RE-confirmed) | No wake-on-motion; no perf data |
-| Charge STAT | GPIO21 | none | none | [`pinouts`](pinouts-and-buses.md) | **med** | **Polarity PENDING** |
-| USB / USB-MSC | D− 19 / D+ 20 | none | none | [`development`](development.md) | **HIGH** per SDK | Never demonstrated |
-| Wi-Fi + BLE | ESP32-S3 | none | none | — | stated by SDK | Never demonstrated |
-| Power rail | GPIO1 HIGH at boot | none | none | [`pinouts`](pinouts-and-buses.md) | **HIGH** | — |
-| **Charging connector** | — | none | none | — | **UNKNOWN** | **USB-C or pogo? Not established** |
-| **Touch** | **absent** | — | — | — | **HIGH** | — |
-| **Frontlight** | **absent** | — | — | — | **HIGH** — stock says *"Frontlight hardware is disabled on this board"* | — |
-
-## Not fitted
-
-Touch, frontlight, audio codec, buzzer, LEDs, PMIC, GPIO expander. Power
-management is direct-GPIO plus the gauge and RTC.
-
-## Combination scenarios
-
-**None assessed** — there is no hardware, no owner and no build report. The
-concerns inherited from the [X4 Pro](../x4-pro/coverage.md) apply structurally
-(display refresh + SDMMC both DMA-heavy; three devices on one `Wire` controller;
-Wi-Fi and BLE sharing one radio), but nothing device-specific can be said.
-
-## Score
-
-**11 of 15** capabilities have HIGH-confidence reverse-engineering evidence.
-**0 of 15** have any community corroboration.
-**0 of 15** were verified by this session.
-**2** are explicitly PENDING in the source itself (GPIO4, STAT polarity).
-**1** first-order buyer question is entirely unanswered (**the charging connector**).
-
----
-
-## Round 2 coverage delta — 2026-09-11
-
-**No line above was altered.**
-
-| Capability | Hardware evidence | Vendor claim | Guide | Example | Tested on X4C? |
-|---|---|---|---|---|---|
-| Display 800×480 | SDK + Draftling | ✅ "4.3 inch / 219 PPI" | [`pinouts-and-buses.md`](pinouts-and-buses.md) | E01, E02, E03 | **no** |
-| Buttons ×7 + GPIO4 | SDK + Draftling | — | [`resources-and-conflicts.md`](resources-and-conflicts.md) | E01, E02 | **no** |
-| microSD (SDMMC 1-bit) | SDK + Draftling | ✅ "16 GB bundled, to 256 GB" | [`resources-and-conflicts.md`](resources-and-conflicts.md) | E01, E02, E03 | **no** |
-| RTC BM8563 @0x51 | SDK | — | — | E01 | **owner-corroborated** ("Has a clock") |
-| Gauge CW2017 @0x63 | SDK + Draftling | ✅ "920 mAh" | — | E01, E02 | **no** |
-| **IMU QMI8658 @0x6B** | SDK | ✅ **"Shake-to-Flip"** | — | **none** | **owner-corroborated** ("Shake to turn page") |
-| Wi-Fi 2.4 GHz | SDK | ✅ | — | — | **FCC-certified** |
-| **BLE** | SDK | ✅ | — | E02 (keyboard, other board) | **FCC-measured** (−0.87 dBm) |
-| Charging, pogo | SDK (`STAT` GPIO21) | ✅ "Ports: Pogo Pin" | — | — | **no** |
-| Deep sleep / EXT1 on GPIO3 | SDK + Draftling | — | [`resources-and-conflicts.md`](resources-and-conflicts.md) §6 | E01, E02 | **no** |
-| USB-MSC | SDK | ✗ not mentioned | — | none | **no socket** |
-| Magnetic phone attachment | — | ✅ "built-in magnetic ring… different position from the first-generation X4" | — | — | owner-corroborated |
-| Frontlight | **absent** | ✅ explicitly "No" | — | — | n/a |
-| Touch | **absent** | ✅ explicitly "No" | — | — | n/a |
-
-### Explicit coverage gaps
-
-1. **The IMU has no feature guide and no example**, despite being the vendor's
-   headline differentiator. This is the largest single hole in the record.
-2. **No `features/` guide exists for any capability of this device.** The
-   directory holds only a `README.md`. The X4 Pro and X3 have full sets; the X4
-   Classic does not, and round 2 did not close that — it is called out here
-   rather than quietly left.
-3. **Zero capabilities have been exercised on X4 Classic hardware by anyone whose
-   work is public**, with the single exception of CrossPoint's sleep-screen
-   rendering, reported in one Reddit comment.
diff --git a/devices/xteink/x4-classic/development.md b/devices/xteink/x4-classic/development.md
deleted file mode 100644
index 588b1c0..0000000
--- a/devices/xteink/x4-classic/development.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Xteink X4 Classic — development
-
-> ESP32-S3, 16 MB flash, 8 MB PSRAM. Retrieval **2026-09-04**.
-> **Nothing executed against hardware — and, unlike the other models, nobody
-> appears to own one outside China.**
-
-## Toolchain
-
-| Item | Value | Status |
-|---|---|---|
-| Framework | Arduino-ESP32 under PlatformIO | `reported-working` |
-| Board | `esp32-s3-devkitc1-n16r8` | `reported-working` **[SDK]** |
-| MCU | `board_build.mcu = esp32s3` | `reported-working` |
-| Build flag | `-DFREEINK_DEVICE_X4CLASSIC=1` | `reported-working` |
-| Also required | **`-DUSE_BLOCK_DEVICE_INTERFACE=1`** in the consumer build | `reported-working` |
-| esptool chip | `esp32s3` | `inferred` |
-| Stock firmware | `xteink_app` **v7.0.11** | **[DUMP]** |
-
-```ini
-[env:x4c]
-extends = base
-board = esp32-s3-devkitc1-n16r8  ; 16 MB flash + 8 MB PSRAM
-board_build.mcu = esp32s3
-build_flags =
-  ${base.build_flags}
-  -DBOARD_HAS_PSRAM
-  ; SD is 1-bit SDMMC (FREEINK_SD_SDMMC auto-enables); SdFat needs its generic
-  ; block-device interface for the FsVolume mount:
-  -DUSE_BLOCK_DEVICE_INTERFACE=1
-  -DFREEINK_DEVICE_X4CLASSIC=1
-```
-Verbatim from `platformio.sample.ini` at commit `2400379`.
-
-**Auto-enabled:** `FREEINK_DRIVER_SSD1677`, `FREEINK_DRIVER_UC8179`,
-`FREEINK_DRIVER_UC8279_X4`, `FREEINK_CAP_RTC`, `FREEINK_BATTERY_I2C_GAUGE`,
-`FREEINK_SD_SDMMC`.
-**Left off:** `FREEINK_CAP_TOUCH`, `FREEINK_CAP_FRONTLIGHT`.
-
-## Build / flash / monitor
-
-```bash
-pio run -e x4c                 # inferred
-pio run -e x4c -t upload       # inferred
-pio device monitor -b 115200   # inferred
-```
-
-## Bricking risks — one is specific to this device and severe
-
-| Risk | Note |
-|---|---|
-| **🔴 Restoring a full-flash image from another unit** | **X4C-specific and the worst risk in the family.** The panel controller is selected **only** from NVS `hw_calib/screenType`, which the factory writes once. There is **no MISO**, so there is no live probe to override a wrong value. A full-flash restore from a different unit overwrites `hw_calib` and can leave the device driving the wrong controller **with no way to detect it**. On every other Xteink, the boot probe silently corrects this. **Preserve NVS, or restore only your own image.** |
-| Wrong display pins when porting from the X4 Pro | DC/RST/BUSY are permuted (14/10/18 vs 18/14/6). Symptom: resets and runs waveforms, never develops an image |
-| Treating GPIO2/5/8/9 as rails or PWM | They are **buttons** here and rails/frontlight on the X4 Pro |
-| Probing GPIO19/20 | Native USB D−/D+ |
-| Holding GPIO0 at reset | Side-Left button **and** boot strap |
-| Repurposing GPIO4 | Role unknown; the stock firmware configures it as an input for a reason nobody has identified |
-| Stale fork on a locked unit | Family-wide; CrossPoint 1.5 warns about soft-bricking locked units |
-
-## USB lock
-
-**Not established for this model.** The X3, X4 and X4 Pro all ship USB-locked on
-many units, and the same unlock paths (crosspointreader.com OTA unlock; SD-card
-`update.bin` with Power+Up at boot; a vendor-sold developer-unlocked variant)
-would be expected to apply. **No X4C owner report exists to confirm any of it.**
-Treat the whole procedure as `inferred` on this device.
-
-See [`../x4-pro/development.md`](../x4-pro/development.md#usb-lock) for what is
-known family-wide.
-
-## Debug access
-
-Native S3 **USB-OTG** on GPIO19/20, USB-CDC. **USB-MSC capable per the SDK** —
-which is more than the X4 Pro, where MSC exists in stock but has not been ported.
-No exposed header, no test points documented, no teardown to look for pads.
-
-## What you cannot do here
-
-- **No touch.** Stock instantiates `NoTouchDriver`.
-- **No frontlight.** Stock reports *"Frontlight hardware is disabled on this
-  board"* — a nice example of the OEM firmware itself telling you the hardware is
-  absent rather than merely unused.
-- **No audio, LEDs, PMIC or GPIO expander.** Power management is direct-GPIO
-  (the GPIO1 rail) plus the CW2017 gauge and BM8563 RTC.
-
-## What you get that the X4 Pro does not
-
-- **Six real navigation buttons**, interrupt-driven, no ADC ladder, no calibration.
-- **A QMI8658 IMU** at 0x6B.
-- **USB-MSC** in the SDK's capability list.
-
-## Starting points
-
-No X4C-specific firmware project was found in a ~200-repository census. The route
-is the FreeInk SDK's `x4c` environment plus any CrossPoint/CrossInk consumer.
-**Nobody has published an X4C build, an X4C bug report, or an X4C flashing guide.**
diff --git a/devices/xteink/x4-classic/examples/best.md b/devices/xteink/x4-classic/examples/best.md
deleted file mode 100644
index 861fbd1..0000000
--- a/devices/xteink/x4-classic/examples/best.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# Selected examples — Xteink X4 Classic
-
-**None of these was built or run by this repository.** Selection is by what each
-one *teaches*, from reading the source. Date **2026-09-11**.
-
-## 1. Start here — `Free-Ink/freeink-sdk`, `[env:x4c]`
-
-Commit [`9f4d3f9`](https://github.com/Free-Ink/freeink-sdk/tree/9f4d3f9ca675e64cc9d616081f39a33cdefce57e) · MIT
-
-```ini
-[env:x4c]
-build_flags = -DFREEINK_DEVICE_X4CLASSIC=1 -DUSE_BLOCK_DEVICE_INTERFACE=1
-```
-
-The board profile is the origin of every other entry, and
-[`docs/xteink-x4c-support.md`](https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/docs/xteink-x4c-support.md)
-is the closest thing to a datasheet this device has.
-
-**Read `XteinkDetect.cpp` before you write a line of display code.** The X4C is
-the one board in the family whose panel bus has no MISO, so the runtime probe
-every sibling uses cannot run and the driver is chosen from NVS
-`hw_calib/screenType` instead. That is the whole risk surface of this device in
-one function.
-
-**Pin your commit.** Between `2400379` (2026-09-01) and `39606d5a` (2026-09-09)
-the recommended `displaySpiHz` halved, 20 MHz → 10 MHz.
-
-## 2. Best alternative approach — `clackups/draftling`
-
-Commit [`92ba7e5`](https://github.com/clackups/draftling/tree/92ba7e514f66bbe42a7fea6d38eff45eed82617b) · MIT
-
-Read [`firmware/main/boards/xteink_x4_classic.h`](https://github.com/clackups/draftling/blob/92ba7e514f66bbe42a7fea6d38eff45eed82617b/firmware/main/boards/xteink_x4_classic.h)
-**side by side with** the FreeInk profile. It is a second author's reading of the
-same reverse engineering, on ESP-IDF rather than Arduino, for an editor rather
-than a reader — so where the two agree, the agreement is worth something, and
-where the header adds commentary it is usually the commentary you wanted:
-
-- why GPIO1 must be raised first and what happens if it is not;
-- that GPIO0 is a boot strap **and** the Left key;
-- that GPIO4 exists on the OEM board and neither project uses it;
-- why the partition table keeps `otadata` — so the stock and CrossPoint OTA
-  updaters can reinstall, which matters enormously on a device with **no USB
-  socket**.
-
-**Negative-example value:** its own `HARDWARE.md` states *"This board has been
-added without on-hardware testing."* Its X4 **Pro** chapter, which *was* tested,
-documents a real asynchronous-DMA bug and a touch-orientation correction. That
-contrast is the best available illustration of how much a blind port can still
-get wrong.
-
-## 3. The integrated application — CrossPoint Reader, `x4c`
-
-[`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader)
-
-What owners actually run. Reported working on X4C hardware by u/Diirge on
-2026-09-10. **This catalogue could not pin a commit for it**, which is a gap, not
-an omission — recorded as `immutable_url: null` in `catalog.json`.
-
-## 4. The one to build if you have no hardware — `kycube/x4pro-emu`
-
-Commit [`bf4b86a`](https://github.com/kycube/x4pro-emu/tree/bf4b86ae0471012d4d07c0bb3042f3f561c9c302) · **no licence stated**
-
-It models the **X4 Pro**, not the X4 Classic. But it boots real stock firmware
-and real CrossPoint under QEMU, with models for the panel, the GT911, the LEDC
-fade, deep sleep and the USB-Serial/JTAG console — and the X4 Classic is the same
-SoC, the same flash map and the same panel stack with **fewer** peripherals.
-
-**Adapting it to the X4 Classic is the cheapest untried way to develop for this
-board**, and nobody has done it. Note the licence: none is stated, so redistribution
-status is `unknown` and it is referenced here, not vendored.
-
-## What no example covers
-
-| Gap | Why it matters |
-|---|---|
-| **QMI8658 / Shake-to-Flip** | The vendor's own headline feature. No example anywhere exercises the IMU on this board |
-| **NVS `screenType` recovery** | The board's worst failure mode — a full-chip erase makes the firmware unable to identify its own display — has no worked example and no documented repair |
-| **USB-MSC** | Enabled in the SDK, no socket on the enclosure, never demonstrated |
-| **Wi-Fi + panel refresh concurrently** | No PMIC, one cell, no measured brown-out margin |
diff --git a/devices/xteink/x4-classic/examples/catalog.json b/devices/xteink/x4-classic/examples/catalog.json
deleted file mode 100644
index e71fa77..0000000
--- a/devices/xteink/x4-classic/examples/catalog.json
+++ /dev/null
@@ -1,144 +0,0 @@
-{
-  "schema": "xteink-example-catalog/1",
-  "device": "xteink/x4-classic",
-  "census_date": "2026-09-11",
-  "census_method": "GitHub code search on 6 exact strings (see ../research-log.md 1.4), plus the CrossPoint/FreeInk repo sets carried over from the 2026-09-04 sweep.",
-  "caveat": "No example in this catalogue has been built or run by this repository. No X4 Classic hardware was available. Every 'status' below is the upstream author's own claim or a dated community report, never a local result.",
-  "examples": [
-    {
-      "id": "X4C-E01",
-      "title": "FreeInk SDK reference build, env x4c",
-      "author": "Free-Ink",
-      "source_class": "community",
-      "canonical_url": "https://github.com/Free-Ink/freeink-sdk",
-      "immutable_url": "https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/platformio.sample.ini",
-      "commit": "9f4d3f9ca675e64cc9d616081f39a33cdefce57e",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-10",
-      "release_or_tag": null,
-      "device_revision": "ESP32S3_X4_CLA (revision string ESP32S3_X4R2_CLA)",
-      "toolchain": "PlatformIO + Arduino-ESP32; exact version not pinned in the sample ini",
-      "features_exercised": ["display SSD1677/UC8179/UC8279", "SDMMC", "BM8563 RTC", "CW2017 gauge", "QMI8658 IMU", "7 discrete buttons", "deep sleep"],
-      "dependencies": ["FREEINK_DRIVER_SSD1677", "FREEINK_DRIVER_UC8179", "FREEINK_DRIVER_UC8279_X4", "USE_BLOCK_DEVICE_INTERFACE=1"],
-      "license": "MIT",
-      "license_evidence": "repository LICENSE",
-      "build_status": "not-tested",
-      "hardware_status": "not-tested",
-      "strengths": "The authoritative board profile. Everything else derives from it.",
-      "pitfalls": "displaySpiHz changed 20 MHz -> 10 MHz at commit 39606d5a (2026-09-09). A build pinned before that clocks the panel twice as fast as upstream now recommends.",
-      "lineage": "origin",
-      "selection": "SELECTED - baseline"
-    },
-    {
-      "id": "X4C-E02",
-      "title": "Draftling writerdeck, board xteink_x4_classic",
-      "author": "clackups",
-      "source_class": "community",
-      "canonical_url": "https://github.com/clackups/draftling",
-      "immutable_url": "https://github.com/clackups/draftling/blob/92ba7e514f66bbe42a7fea6d38eff45eed82617b/firmware/main/boards/xteink_x4_classic.h",
-      "commit": "92ba7e514f66bbe42a7fea6d38eff45eed82617b",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-11",
-      "release_or_tag": null,
-      "device_revision": "X4 Classic / X4 v2",
-      "toolchain": "ESP-IDF, CMakePresets.json in repo",
-      "features_exercised": ["display", "8 buttons", "CW2017", "SDMMC", "BLE keyboard", "dual-OTA partition table"],
-      "dependencies": ["esp-idf", "LVGL", "vendored FastEPD"],
-      "license": "MIT",
-      "license_evidence": "repository LICENSE",
-      "build_status": "reported-working (author builds it in CI)",
-      "hardware_status": "explicitly NOT tested on X4 Classic hardware; the author says so in HARDWARE.md",
-      "strengths": "A second, independent reading of the board profile written for a different application. Names the X4C/X4 v2 equivalence, the DC/RST/BUSY difference from the X4 Pro, and the reason for a dual-OTA table.",
-      "pitfalls": "It is a text editor, not a reader. Its display backend runs the panel at the OEM's 5 MHz, not FreeInk's rate. Blind port for this board.",
-      "lineage": "derived from FreeInk SDK, cited",
-      "selection": "SELECTED - best alternative approach"
-    },
-    {
-      "id": "X4C-E03",
-      "title": "CrossPoint Reader, env x4c",
-      "author": "crosspoint-reader",
-      "source_class": "community",
-      "canonical_url": "https://github.com/crosspoint-reader/crosspoint-reader",
-      "immutable_url": null,
-      "commit": null,
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-11",
-      "device_revision": "X4 Classic",
-      "toolchain": "PlatformIO",
-      "features_exercised": ["display", "buttons", "SDMMC", "sleep screen", "OTA"],
-      "license": "see upstream",
-      "license_evidence": "not re-verified this pass",
-      "build_status": "not-tested",
-      "hardware_status": "reported-working - u/Diirge, r/xteinkereader 1wbxvvg comment p8vlefa, 2026-09-10: 'CrossPoint sleep screen rendering got much better as of today on the x4c'",
-      "strengths": "The firmware most X4C owners will actually run.",
-      "pitfalls": "No commit pinned this pass - the immutable_url is null and that is a real gap in this catalogue.",
-      "lineage": "independent reader firmware, uses the FreeInk board data",
-      "selection": "SELECTED - the integrated application"
-    },
-    {
-      "id": "X4C-E04",
-      "title": "esphome-xteink",
-      "author": "vjFaLk",
-      "source_class": "community",
-      "canonical_url": "https://github.com/vjFaLk/esphome-xteink",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-08",
-      "license": "MIT",
-      "build_status": "not-tested",
-      "hardware_status": "not-tested",
-      "pitfalls": "Vendors the FreeInk SDK verbatim; not an independent implementation. Its own description names X4/X3/X4 Pro, not the X4C.",
-      "lineage": "vendored copy of Free-Ink/freeink-sdk",
-      "selection": "REJECTED - duplicate of E01, no X4C-specific content"
-    },
-    {
-      "id": "X4C-E05",
-      "title": "Inkkit shared HAL",
-      "author": "mohitagw15856",
-      "source_class": "community",
-      "canonical_url": "https://github.com/mohitagw15856/Inkkit",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-04",
-      "license": "MIT",
-      "build_status": "not-tested",
-      "hardware_status": "not-tested",
-      "pitfalls": "src/BoardConfig.h is a copy. Scoped by its own description to 'Xteink X4/X3, ESP32-C3'.",
-      "lineage": "copy of Free-Ink/freeink-sdk",
-      "selection": "REJECTED - duplicate of E01"
-    },
-    {
-      "id": "X4C-E06",
-      "title": "x4pro-emu - QEMU model of the X4 Pro",
-      "author": "kycube",
-      "source_class": "community",
-      "canonical_url": "https://github.com/kycube/x4pro-emu",
-      "immutable_url": "https://github.com/kycube/x4pro-emu/tree/bf4b86ae0471012d4d07c0bb3042f3f561c9c302",
-      "commit": "bf4b86ae0471012d4d07c0bb3042f3f561c9c302",
-      "retrieved": "2026-09-11",
-      "last_activity": "2026-09-07",
-      "license": "none stated - all rights reserved by default",
-      "license_evidence": "GitHub reports no licence; no LICENSE file in the tree",
-      "build_status": "not-tested",
-      "hardware_status": "n/a - it is an emulator, built against a physical X4 Pro",
-      "strengths": "Boots both stock 7.2.4 and CrossPoint 1.6.0 to their home screens. Publishes an eFuse dump, a partition decode and register-level traces.",
-      "pitfalls": "Models the X4 PRO, not the X4 Classic. No radio; WiFi stops itself after ~8 s.",
-      "lineage": "independent",
-      "selection": "NOT AN X4C EXAMPLE - catalogued because it is the nearest runnable target and because building an X4C variant of it is the cheapest untried way to test X4C firmware"
-    }
-  ],
-  "feature_coverage": {
-    "display": "E01, E02, E03",
-    "buttons": "E01, E02, E03",
-    "sdmmc": "E01, E02, E03",
-    "rtc_bm8563": "E01 only",
-    "gauge_cw2017": "E01, E02",
-    "imu_qmi8658": "E01 only - and NOTHING exercises Shake-to-Flip, the vendor's own headline feature",
-    "deep_sleep": "E01, E02",
-    "usb_msc": "E01 claims support; no example and no socket",
-    "wifi_ble": "E02 (BLE keyboard) - untested on this board"
-  },
-  "uncovered": [
-    "QMI8658 motion input / Shake-to-Flip - no example anywhere",
-    "USB-MSC - enabled in the SDK, physically awkward, never demonstrated",
-    "NVS screenType recovery after an accidental full erase - the board's single worst failure mode has no worked example"
-  ]
-}
diff --git a/devices/xteink/x4-classic/examples/search-log.md b/devices/xteink/x4-classic/examples/search-log.md
deleted file mode 100644
index 6ff9511..0000000
--- a/devices/xteink/x4-classic/examples/search-log.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Example search log — Xteink X4 Classic
-
-Date **2026-09-11**. Carrying forward the 2026-09-04 sweep's repository census
-(~200 Xteink-relevant repos) and adding targeted queries for the X4C.
-
-| # | Service | Exact query | Depth | Useful | Notes |
-|---|---|---|---|---|---|
-| 1 | GitHub code search | `"XteinkX4Classic"` | all 8 | 5 | `crosspoint-reader` ×2 (+simulator, +lockscreens fork), `freeink-sdk` ×2, `crosspoint-simulator`, `Inkkit`, `esphome-xteink` |
-| 2 | GitHub code search | `xteink "X4 Classic"` | first 15 of 47 | 4 | surfaced **`clackups/draftling`** — the only project with hand-written X4C files |
-| 3 | GitHub code search | `"X4 V2" xteink` | all 11 | 1 | 9 of 11 hits are inside `clackups/draftling` |
-| 4 | GitHub code search | `"X4R2_CLA" xteink` | all 5 | 2 | surfaced **`kycube/x4pro-emu`** |
-| 5 | GitHub code search | `"X4R1_CLA"` | — | **0 results** | **a negative result, and the useful one** |
-| 6 | GitHub repo metadata | `repos/{clackups/draftling,kycube/x4pro-emu,vjFaLk/esphome-xteink,mohitagw15856/Inkkit}` | — | 4 | dates, licences, stars |
-| 7 | GitHub commits API | `repos/Free-Ink/freeink-sdk/commits?path=…/BoardConfig.h&since=2026-09-01` | all | 2 | `3fe3936d`, `39606d5a` |
-| 8 | old.reddit | 11 searches, 12 comment trees | 100/query | many | see [`../research-log.md`](../research-log.md) §1.6 |
-
-## Rejections and why
-
-| Candidate | Reason |
-|---|---|
-| `vjFaLk/esphome-xteink` | vendored verbatim copy of `freeink-sdk`; deduplicated to E01 |
-| `mohitagw15856/Inkkit` | copied `BoardConfig.h`; deduplicated to E01 |
-| `t0nyz0/crosspoint-reader-lockscreens` | fork of `crosspoint-reader`, lineage preserved, no X4C-specific content |
-| `crosspoint-reader/crosspoint-simulator` | host simulator; carries the board enum but exercises no hardware |
-| `AsukaLay/xteink_pdf`, `SamLinBIT/xteink-toolkit` | host-side file converters; no board code |
-
-## Not searched
-
-- **Gitee, Codeberg, GitLab** — the Chinese-hosted mirrors of this ecosystem were
-  not searched. Given the vendor is China-first, this is a real gap.
-- **Package registries** (PlatformIO Registry, Arduino Library Manager) — no
-  X4C-specific library is expected, and none was looked for.
-- **Bilibili / YouTube** — video examples not surveyed.
-
-## Stopping criterion
-
-Stopped after query 8 returned only repositories already in the catalogue.
-**Two consecutive passes produced no new qualifying candidate.**
-
-## Honest limitation
-
-**Nothing in `catalog.json` was built.** No toolchain was installed, no PlatformIO
-environment was resolved, and no dependency set was pinned by this repository.
-`best.md` is therefore a *reading* recommendation, not a tested one.
diff --git a/devices/xteink/x4-classic/factory-firmware.md b/devices/xteink/x4-classic/factory-firmware.md
deleted file mode 100644
index a79d661..0000000
--- a/devices/xteink/x4-classic/factory-firmware.md
+++ /dev/null
@@ -1,178 +0,0 @@
-# Xteink X4 Classic — factory firmware
-
-> Everything here is read from the FreeInk maintainers' analysis of a stock dump
-> named **`flashx4c.bin`**, which **this session did not obtain**.
-> Retrieved **2026-09-04**.
-
-## Board identity strings
-
-| String | Meaning |
-|---|---|
-| **`ESP32S3_X4_CLA`** | Board tag |
-| **`ESP32S3_X4R2_CLA`** | Board **revision** string — note the `R2` |
-| **`ESP32S3_X4_CLA_SSD1677`** | Default panel string |
-
-`ESP32S3_X4R2_CLA` is the only revision identifier of any kind found for any
-Xteink device. **Whether an R1 shipped is unknown** — it may be an internal
-iteration that never left the factory, or the X4C may already be a second
-revision. Recorded as an open question, not as evidence of two field revisions.
-
-## Version
-
-**`xteink_app` v7.0.11** (app0). For comparison, the X4 Pro's contemporaneous
-firmware was **7.0.8** and later **7.4.4** — so the C-series and Pro share a
-version stream, which is consistent with one codebase serving both S3 boards.
-
-## Partition layout (16 MB, dual-OTA)
-
-`nvs` `0x9000` · `otadata` `0xE000` · `app0` `0x10000` · `app1` `0x7F0000` ·
-`spiffs` `0xFD0000` · `coredump` `0xFE4000`.
-
-**Identical to the [X4 Pro](../x4-pro/factory-firmware.md)** and different from the
-C3 [X4](../x4/factory-firmware.md), which uses 6400 KiB app slots and a 3456 KiB
-SPIFFS.
-
-## NVS `hw_calib/screenType` — the most important byte on this device
-
-| Value | Controller |
-|---:|---|
-| 1 or `0x0B` | [UC8179](../../../components/ultrachip/uc8179/README.md) |
-| 2 or `0x0C` | [UC8279](../../../components/ultrachip/uc8279/README.md) |
-| 3, default, or unset | [SSD1677](../../../components/solomon-systech/ssd1677/README.md) |
-
-Written **once by the factory**. Because the display bus has no MISO, this value
-is not merely a hint — it is the **only** source of truth, and nothing corrects it
-at boot.
-
-**Operational consequence:** a full-flash backup/restore workflow that is safe on
-every other Xteink is **not safe here**. If you restore an image captured from a
-different unit, you import that unit's `hw_calib` and may drive the wrong
-controller. Preferred order:
-
-1. Take **your own** full-flash backup before anything else.
-2. If you must use a foreign image, **preserve and re-write your own `nvs`
-   partition** (`0x9000`, 20 KiB) afterwards.
-3. Verify from the serial log, which prints
-   `[XTDET] X4C: NVS screenType=<n> -> <driver> (no MISO, probe skipped)`.
-
-## What stock does that the SDK does not
-
-- **USB-MSC** — the SDK lists the X4C as USB-MSC capable, so unlike the X4 Pro this
-  is not a gap.
-- Frontlight code paths exist but report *"Frontlight hardware is disabled on this
-  board"* — i.e. the vendor ships one firmware across variants and gates on the
-  board tag. That also explains why the X4 Pro's dump contains a **vestigial ADC
-  button-ladder matcher** for hardware it does not have.
-
-## Dumping and restoring
-
-```bash
-# inferred — not executed; requires a USB-unlocked unit
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-           read_flash 0 0x1000000 x4c-stock-full.bin
-sha256sum x4c-stock-full.bin
-python3 tools/esp_image_info.py x4c-stock-full.bin
-```
-
-```bash
-# inferred — see the NVS warning above before writing a foreign image
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-           write_flash 0 x4c-stock-full.bin
-```
-
-## Artifacts held
-
-**None.**
-
-| Wanted | Status | Reacquisition |
-|---|---|---|
-| `flashx4c.bin` | **Not located publicly.** Referenced only inside the FreeInk SDK's documentation; the maintainers hold it privately | `blocked` — no URL exists. Ask upstream, or dump a unit |
-| Any X4C OTA package | Not located | `blocked` |
-| Vendor OTA feed for this model | Not queried | `manual` — `gotaserver.xteink.com/api/check-update` |
-
-For comparison, an **[X4 factory dump](../x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md)**
-*was* obtained and is archived in this repository. It is a **different device**
-(ESP32-C3) and cannot be flashed here, but it documents the vendor's firmware
-conventions — partition style, OTA endpoints, the Arduino-vs-IDF split.
-
----
-
-## Round 2 — 2026-09-11
-
-**No line above was altered.**
-
-### The board tags are a shared enum, not a per-unit stamp
-
-A **physical Xteink X4 Pro** was dumped twice on 2026-09-06 by a third party, both
-dumps hashing identically
-(`90734554798da8dbe1961bf876a7bf44f2ea66a572ae2ed9b7ed395c9a0143fe`). Its stock
-`xteink_app` binary contains, in one image:
-
-```
-ESP32S3_X4_TL      ESP32S3_X4_TL_SSD1677      ESP32S3_X4_CLA      ESP32S3_X4R2_CLA
-XTEink::SSD1677_800x480    UC8179_800x480    UC8279_800x480    ZHX_UC8279Base
-GT911Driver    BM8563Driver    Cw2017PowerHal
-```
-
-Source:
-[`kycube/x4pro-emu` `docs/device/partitions.md`](https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/partitions.md),
-commit `bf4b86a`.
-
-**Consequence for this record:** finding `ESP32S3_X4R2_CLA` inside a dump tells
-you the vendor builds one firmware for both S3 boards. It does **not** tell you
-the unit it came from is an "R2" of anything. See [`README.md`](README.md) §`R2`.
-
-### Stock-firmware versions across the S3 family
-
-| Version | Board | Built | Toolchain | Source |
-|---|---|---|---|---|
-| `xteink_app` **7.0.11** | **X4 Classic** | unknown | unknown | FreeInk's private `flashx4c.bin` — **the only X4C version ever named** |
-| `xteink_app` **7.2.4** | X4 Pro (desk unit) | **2026-08-14 19:25:05** | **ESP-IDF v6.0.1** | third-party dump, 2026-09-06 |
-| **7.4.4** / package `V7.4.5` | X4 Pro | — | — | conflict already recorded in `VERIFICATION-xteink.md` item 4 |
-| **7.5.4** | X4 Pro | — | — | third-party analysis doc `docs/stock-7.5.4.md` |
-
-**Four different version numbers now exist for the X4 Pro's stock firmware and
-one for the X4 Classic.** They are not reconcilable from public evidence — the
-vendor ships regional and OTA-staged builds, and no changelog is published.
-**No X4 Classic shipping version is corroborated by anyone.**
-
-### Partition layout, now with a hardware witness
-
-The 16 MB dual-OTA layout recorded above matches, exactly, the table read off a
-**physical X4 Pro**:
-
-| Name | Type | Offset | Size |
-|---|---|---|---|
-| `nvs` | data/nvs | `0x009000` | `0x005000` |
-| `otadata` | data/ota | `0x00E000` | `0x002000` |
-| `app0` | app/ota_0 | `0x010000` | `0x7E0000` |
-| `app1` | app/ota_1 | `0x7F0000` | `0x7E0000` |
-| `spiffs` | data/spiffs | `0xFD0000` | `0x014000` |
-| `coredump` | data/coredump | `0xFE4000` | `0x01C000` |
-
-On that unit `otadata` held `seq=1 state=2 (VALID)`, selecting **`app0`**, and
-`app1` was erased `0xFF`. **This is an X4 Pro, not an X4 Classic** — but it is
-the first non-SDK confirmation of the layout anywhere in this family.
-
-### NVS keys seen on the sibling board
-
-`hw_calib` → `screenType` (**the panel identity**), `region` (1 = CN, 2 =
-overseas), `lightDS`. `user_config` → Wi-Fi credentials, `lightBri`, `lightCT`,
-`lightOn`, `timeZone`, `language`, `activate`, `cloud_bind_st`, `otaPromptDay`,
-`pwrTimingVer`. Plus `xteink_sys`, `misc`, `nvs.net80211`, `phy`.
-
-The X4 Classic has no frontlight, so `lightBri` / `lightCT` / `lightDS` are
-expected to be absent or inert there — **not verified**.
-
-### The recovery warning, restated with its new weight
-
-The X4 Classic's panel bus has **no MISO**. `hw_calib/screenType` is the only
-thing that tells firmware which of three controllers is fitted, and it is written
-**at the factory**.
-
-**A full-chip erase destroys it, and there is no documented way to recover it
-except by trial.** On every sibling board a bus probe would repair the mistake
-automatically. On this one it cannot. Preserve `nvs` at `0x9000` across any
-reflash, and note that Draftling keeps an `otadata` partition specifically so the
-stock and CrossPoint OTA updaters can reinstall — which matters far more here
-than on a board with a USB socket, because **the X4 Classic has none**.
diff --git a/devices/xteink/x4-classic/features/README.md b/devices/xteink/x4-classic/features/README.md
deleted file mode 100644
index a4e0570..0000000
--- a/devices/xteink/x4-classic/features/README.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Xteink X4 Classic — feature guides
-
-**No per-feature guides are written for this device, deliberately.**
-
-Every capability is documented in [`pinouts-and-buses.md`](../pinouts-and-buses.md)
-and [`development.md`](../development.md), and there is **no owner, no build
-report and no hardware experience anywhere** to write a task-oriented guide from.
-Writing "how do I use the IMU on an X4 Classic" would mean paraphrasing the X4
-Pro's guide with different pin numbers and implying an experience base that does
-not exist.
-
-Where a capability is shared with a sibling **and the sibling's guide is
-evidence-backed**, use that guide and substitute the pins from this device's
-pinout page:
-
-| Capability | Guide to read | Pin deltas for the X4C |
-|---|---|---|
-| Display, controller variants | [X4 Pro display](../../x4-pro/features/display.md) | **DC 14, RST 10, BUSY 18** (permuted); controller from **NVS only**, no bus probe |
-| microSD (native SDMMC) | [X4 Pro storage](../../x4-pro/features/storage.md) | power enable **GPIO6**, not GPIO5 |
-| Battery / CW2017 gauge | [X4 Pro battery](../../x4-pro/features/battery-and-power.md) | same gauge, same STAT pin; **polarity PENDING** |
-| RTC BM8563 | [X4 Pro RTC](../../x4-pro/features/rtc.md) | identical |
-| IMU QMI8658 | [X3 IMU](../../x3/features/imu.md) | bus is **SDA 39 / SCL 38**, not SDA 20 / SCL 0 |
-| USB | [X4 Pro USB](../../x4-pro/features/usb.md) | **USB-MSC is listed as supported here**, unlike the X4 Pro |
-| Buttons | — | **Seven discrete interrupt-driven GPIOs**, not an ADC ladder. See [`pinouts`](../pinouts-and-buses.md#input--seven-discrete-interrupt-driven-buttons) |
-
-**Not fitted:** touch, frontlight, audio, LEDs, PMIC, GPIO expander.
diff --git a/devices/xteink/x4-classic/gaps-and-conflicts.md b/devices/xteink/x4-classic/gaps-and-conflicts.md
deleted file mode 100644
index c538e87..0000000
--- a/devices/xteink/x4-classic/gaps-and-conflicts.md
+++ /dev/null
@@ -1,237 +0,0 @@
-# Xteink X4 Classic — gaps and conflicts
-
-Snapshot **2026-09-04**. **The defining characteristic of this record is an
-inversion: the hardware is better documented than the product.**
-
-## The inversion, stated plainly
-
-| Well established | Completely unknown |
-|---|---|
-| Every GPIO, with per-pin confidence levels | **Price** |
-| All three I²C peripherals and addresses | **Where or whether you can buy it** |
-| Display pinout, SPI clock, controller-selection mechanism | **Dimensions, mass, battery capacity** |
-| Button map, corrected by hardware testing | **Any photograph of the device** |
-| Partition layout, board tag, revision string, stock version | **Whether it is sold under another name in China** |
-| Build configuration | **Whether anyone outside China owns one** |
-
-This happens because the **only** source is a firmware dump. A dump tells you
-everything about the board and nothing about the product.
-
-## Open technical questions
-
-### 1. GPIO4 — configured, never used
-
-The stock board-init registers GPIO4 as a **plain input, mode 0, not
-interrupt-attached**. It is therefore not a button. The SDK does not read it.
-
-**Nobody knows what it is.** Candidates, none supported: a hall/lid sensor, a
-hardware-variant strap, a second charge/fault line, or a depopulated feature. The
-fact that stock configures it at all argues it is connected to something.
-
-**What would resolve it:** read it on hardware under varied conditions
-(lid/case on and off, charger in and out, magnet nearby), or a teardown.
-
-### 2. Charge-STAT polarity
-
-`batteryChargeStatus = 21`, `batteryChargeStatusActiveHigh = true` — **carried over
-from the X4 Pro** rather than independently confirmed. The SDK marks it `PENDING`.
-
-### 3. Panel orientation
-
-Ships `NO_FLIP`. Pending hardware.
-
-### 4. `ESP32S3_X4R2_CLA` — does an R1 exist?
-
-The board revision string contains `R2`. **No R1 has been observed.** It may be an
-internal iteration, or the shipping X4C may already be a revision-2 board. Nothing
-distinguishes them externally because nothing external has been seen at all.
-
-### 5. Bezel insets are inherited, not measured
-
-`viewableInsets = {9, 7, 3, 7}` are the X4 Pro's values, adopted on the grounds of
-identical glass and explicitly *"pending measurement"*.
-
-## A community claim that does not match the firmware
-
-[r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/) (2026-06-22,
-**300 points**) is the post that first identified this device in a vendor video:
-
-> "Did we just spot a new X4 model? **Physical buttons + frontlight** but no
-> touchscreen in the latest video?"
-
-The community was **right about the buttons and the absence of touch, and wrong
-about the frontlight**. The X4C's `BoardProfile` sets `NO_FRONTLIGHT`, and the
-stock firmware itself reports *"Frontlight hardware is disabled on this board"*.
-Firmware evidence beats video interpretation.
-
-**But there is a live complication.** A separate 2026-08-25 thread about a coming
-"X4 version 2" contains this claim:
-
-> "Leaked versions shows the X4 v2 with pogos and **another X4 with pogos,
-> backlight and no touch**."
-> — [r/xteinkereader `1vxsr0x`](https://old.reddit.com/r/xteinkereader/comments/1vxsr0x/) · **hearsay, unverified**
-
-If a buttons-plus-frontlight-no-touch device genuinely exists, it is **not** the
-X4 Classic documented here — the dump is unambiguous. It would be a *further*
-model. Recorded so that a future pass does not merge them.
-
-## Gaps — commercial
-
-- **No price has ever been published**, in any currency, on any channel.
-- The vendor's own `x4-classic` Shopify collection **exists and contains no
-  device** — only four generic accessories. That is a strong signal the SKU was
-  provisioned for an international launch that has not happened.
-- **No listing was found** on AliExpress, Amazon or Xianyu in this session's
-  searches — though Chinese marketplaces were **not searched directly**, so this
-  is a weak negative.
-
-## Gaps — physical
-
-No teardown, no photograph, no PCB image, no dimensions, no mass, no battery
-capacity, no connector identification, **no evidence of what its charging
-connector even is** (USB-C like the X4, or pogo like the X3 and X4 Pro — the dump
-does not say, and this is a first-order question for a buyer).
-
-## Gaps — regulatory
-
-None read. See the family finding in
-[`../x4-pro/gaps-and-conflicts.md`](../x4-pro/gaps-and-conflicts.md) and the
-X3 record: Xteink devices generally **carry no external CE/FCC marking**, with
-regulatory text placed in software instead.
-
-## Gaps — community
-
-**Zero.** No X4C owner report, bug report, firmware fork, flashing guide, review or
-photograph was found in a corpus of **2,136 Reddit posts** and a
-**~200-repository GitHub census**. This device has no community footprint at all
-outside the FreeInk SDK.
-
-That is itself the finding: **the X4 Classic is documented but not distributed.**
-
----
-
-# Round 2 — 2026-09-11. Gaps closed, gaps opened, conflicts recorded.
-
-**No line above this rule was altered.** Several items above are now answered;
-they are answered *here* rather than edited in place.
-
-## A. Closed
-
-| Was open | Now | Evidence |
-|---|---|---|
-| No price, no listing, no availability | **US$79.00, listed 2026-09-06, in stock** | vendor API `published_at` |
-| No dimensions, mass, battery capacity | **114 × 69 × 4.9 mm · 68 g · 920 mAh** | vendor spec block |
-| Charging connector unknown | **Pogo pin, 4 contacts, magnetic. No USB-C** | vendor spec block; confirmed by the label exhibit's rear photograph |
-| No regional name | **`XTEINK X4 Classic (X4 V2)`** — both names, one product | vendor title, vendor announcement, FCC description |
-| Whether it is sold internationally | **Yes** | — |
-| No photograph of any kind | **One public regulatory photograph** (rear, with label) | `artifacts/certification/2BTR9-X4C-label.pdf` |
-| No regulatory filing found | **FCC ID `2BTR9-X4C`, granted 2026-07-20** | fccid.io |
-| Manufacturer's legal identity unknown | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, Longhua District, Shenzhen, FRN `0037772233` | FCC grantee record |
-| `xteink.cn` unreachable, ownership unproven | **The FCC filing lists `xteink.cn` as the applicant's domain** and the responsible party's e-mail is `chuchen@xteink.cn` | FCC |
-
-## B. `R2` — narrowed, not closed
-
-Detailed in [`README.md`](README.md) §`R2`. In short: the same X4 Pro stock binary
-carries **all four** S3 board tags, so the tags are a shared-codebase enum rather
-than a per-unit revision stamp; `"X4R1_CLA"` returns **zero** results on GitHub
-code search; there is **no earlier X4C FCC grant**; and both the vendor ("X4 V2")
-and owners ("the V1") treat the plain X4 as version 1.
-
-**Most economical reading: `X4R2` = "X4, revision 2", and revision 1 is the C3
-X4.** Not proven. An unreleased engineering-sample X4C R1 cannot be excluded from
-public sources and never will be.
-
-**What would settle it:** the `SCH`/`BLOCK` exhibits (**permanently
-confidential** — never), a silkscreened revision in the internal photographs
-(**2027-01-16**), or a second stock dump from a *known* X4 Classic showing a
-different revision string.
-
-## C. Still open
-
-| # | Gap | What would settle it |
-|---|---|---|
-| R2-1 | **GPIO4's role.** Neither FreeInk nor Draftling uses it; FreeInk calls it *"a plain input (not a button, not used by the SDK)"* | Internal photographs (2027-01-16), or a continuity measurement |
-| R2-2 | **Charge-`STAT` polarity on GPIO21** is `inferred` from a profile field, never observed | A multimeter on a charging unit |
-| R2-3 | **Panel orientation** — no `DisplayOrientation` has been verified on hardware | One photograph of a booted X4C running a known image |
-| R2-4 | **BM8563 `CLKOUT` → ESP32-S3 `XTAL_32K_P`/GPIO15?** Asked publicly 2026-09-10, unanswered. Would enable low-power always-on BLE | Internal photographs, or continuity |
-| R2-5 | **Which panel controller ships in retail units.** `hw_calib/screenType` is set per unit at the factory; the retail distribution is unknown. A physical X4 **Pro** read `screenType = 2` (**UC8279**) on 2026-09-06 — that is one unit of a *different* model | `[XTDET]` console lines from several X4C units |
-| R2-6 | **Chinese-market launch date and price.** JD, Taobao, Xianyu and Xiaohongshu were **not searched** this pass | Those marketplaces |
-| R2-7 | **No X4C-specific stock-firmware version is corroborated.** FreeInk analysed `xteink_app` v7.0.11; a physical X4 **Pro** shipped **7.2.4** (ESP-IDF v6.0.1, built 2026-08-14) and a **7.5.4** analysis exists. The X4C's shipping version is unknown | Any X4C `esptool read-flash` |
-| R2-8 | **Nothing measured.** No refresh time, no deep-sleep current, no page-turn latency, no contrast measurement | See [`performance.md`](performance.md) §4 |
-
-## D. New conflicts, recorded rather than resolved
-
-### R2-C1 — the product page contradicts itself about file formats
-
-| Source | Claim |
-|---|---|
-| Spec block, same page | *"Document: **EPUB, TXT** / Image: BMP / Fonts: BIN, XTF"* |
-| FAQ, same page | *"XTEINK supports **TXT, EPUB, MOBI, PDF, XTCH, XTC, and XTCZ** formats"* |
-
-Both were retrieved from one HTML document on 2026-09-11. The FAQ text is
-brand-wide boilerplate ("XTEINK supports…"), the spec block is device-specific.
-**Neither is treated as authoritative.** This is consistent with the family's
-established finding that `xteink.com` prose is SEO-generated and unreliable — the
-X3 listing still advertises a frontlight the X3 does not have.
-
-### R2-C2 — "4.3 inch" vs 4.26″
-
-The vendor's spec block says **4.3 inch**; the firmware, the FreeInk docs and
-every other record in this tree say **4.26″**. 800×480 at 219 PPI computes to
-4.26″. **Vendor rounding**, recorded for completeness.
-
-### R2-C3 — an "E-ink secondary screen on the back"
-
-The product-page FAQ asks *"How do I customize the E-ink secondary screen on the
-back?"* and answers with instructions for setting a **power-off / sleep
-wallpaper**. There is **no second display**: the answer describes the main panel
-retaining an image when off, which is what e-paper does. The question is
-mis-worded marketing copy. **No evidence of a second panel exists in the board
-profile, the FCC filing, any review or any photograph.** Recorded so it is not
-re-investigated.
-
-### R2-C4 — "better screen" vs unchanged pixel density
-
-Two launch reviewers describe improved contrast; one of them calls it *"a slight
-improvement in the screen resolution"*. **The density is unchanged at 219 PPI**,
-corrected inside the same thread by u/scamper_ (*"It does not, it's still 219"*)
-and independently by u/ajcabrera (*"Both use the same 219 PPI screen"*).
-
-Whether *contrast* improved is **unresolved**: it could be a panel-controller
-batch difference (SSD1677 vs UC8179 vs UC8279 drive the same glass differently),
-a waveform change, the absence of the Pro's touch and frontlight layers — one
-commenter, u/quangvu1991, offers exactly that mechanism — or observer bias on
-vendor-supplied units. **No photometry exists.**
-
-### R2-C5 — EU price vs store price
-
-US$79.00 (vendor API, 2026-09-11) against **€89** reported by an EU buyer the
-same week ([r/XTEINK `1w9jzpn`](https://old.reddit.com/r/XTEINK/comments/1w9jzpn/),
-2026-09-07). Almost certainly VAT and regional pricing, **but it was not
-normalised** and no EU store page was retrieved. Do not quote a single "price"
-for this device without a region.
-
-### R2-C6 — X4 Pro touch orientation: a new disagreement, inherited here
-
-Not an X4C conflict — the X4C has no touch — but it bears on how much to trust
-the shared profile, so it is flagged:
-
-| Source | Claim |
-|---|---|
-| FreeInk `BoardConfig.h` | `swapXY=true, flipX=false, flipY=true` — *"confirmed by corner-tap"* |
-| `kycube/x4pro-emu` `docs/hardware.md` | repeats FreeInk's values and notes the support **doc's** I²C paragraph has INT/RST swapped and is *"stale"* |
-| **`clackups/draftling` `HARDWARE.md`** | *"the FreeInk SDK's starting values (`swapXY=true, flipY=true`) had touches landing **180 degrees opposite** of where the finger was"* — corrected against a physical unit to `MIRROR_X`/`MIRROR_Y` = 1/0 |
-
-Draftling's is the only **on-hardware** claim of the three, but it is made inside
-a different rendering stack with its own orientation convention, so the two are
-not necessarily contradictory. **Recorded as unresolved**, and carried to
-[`../x4-pro/gaps-and-conflicts.md`](../x4-pro/gaps-and-conflicts.md).
-
-## E. A pre-existing statement confirmed correct
-
-The 2026-09-04 record's claim that **the X4 Classic has no frontlight** was
-challenged by the community from June to September and was **right**. The
-vendor's own spec block now reads `Front light: No` and the FAQ says so in
-prose. The conflict listed above as item 8 of `VERIFICATION-xteink.md`
-("X4 Classic reported with a frontlight by the community; firmware says none")
-is **resolved in favour of the firmware**.
diff --git a/devices/xteink/x4-classic/market-and-pricing.md b/devices/xteink/x4-classic/market-and-pricing.md
deleted file mode 100644
index bce4937..0000000
--- a/devices/xteink/x4-classic/market-and-pricing.md
+++ /dev/null
@@ -1,200 +0,0 @@
-# Xteink X4 Classic — market and pricing
-
-## There is no pricing. That is the finding.
-
-Observed **2026-09-04** from `xteink.com`'s Shopify APIs:
-
-- `/products.json` (23 products, complete — pages 2 and 3 empty) contains **no X4
-  Classic**.
-- `/collections.json` **does** list a collection with handle **`x4-classic`**.
-- `/collections/x4-classic/products.json` returns **four products, none of them a
-  device**:
-
-| Product | Price | Note |
-|---|---|---|
-| eReader Magnetic Reading Light | $9.99 / $15.99 | generic, cross-model |
-| eReader Adhesive Metal Ring | $4.99 / $7.99 | generic |
-| Magnetic Charging Adapter for X3 & X4 Pro | $5.99 | **named for other models** |
-| Magnetic Pogo Pin Charging Cable for X3 & X4 Pro | $4.99 | **named for other models** |
-
-**A collection with no device and no device-specific accessories is a provisioned
-SKU, not a product line.** Compare the neighbouring collections, which each carry
-their device plus model-specific cases and protectors:
-
-| Collection | Device present? | Model-specific accessories |
-|---|---|---|
-| `x3-series` | ✅ $69.00 | 6 |
-| `x4-pro-series` | ✅ $99.00 | 6 |
-| `x4-series` | ❌ (delisted) | 4, **all sold out** |
-| **`x4-classic`** | ❌ **never present** | **0** |
-
-The `x4-series` and `x4-classic` collections fail in **different ways**: the X4 is
-an end-of-life signature (device gone, its accessories exhausted), while the X4C
-is a **pre-launch signature** (nothing was ever there).
-
-## A weak, suggestive inference about the charging connector
-
-The two charging accessories in the `x4-classic` collection are both **magnetic
-pogo** parts *"for X3 & X4 Pro"*. That is **not** evidence the X4C uses pogo
-charging — they are the only charging accessories Xteink sells, and they appear in
-several collections. But it is the only signal that exists, and the question
-matters to a buyer.
-
-**Recorded as unresolved**, and flagged in
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) as a first-order unknown.
-
-## Channels searched
-
-| Channel | Result |
-|---|---|
-| `xteink.com` | Collection exists, device does not |
-| Reddit (2,136 posts) | **No purchase report, no price, no listing link** |
-| GitHub (~200 repos) | No X4C project of any kind |
-| AliExpress / Amazon / Xianyu | **Not searched directly** — a declared exclusion, so this negative is weak |
-
-Note that the family *is* sold through several third-party channels — owners
-report buying an X3 from **Amazon.ca**, an X3 from **Xianyu** (Chinese eBay) and
-an X4 from **AliExpress**
-([r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/), 2026-08-10,
-firsthand). So a Chinese-marketplace listing for the X4C is plausible and simply
-was not looked for.
-
-## Family price context, 2026-09-04
-
-| Device | Price |
-|---|---|
-| [X3](../x3/market-and-pricing.md) | **$69.00**, in stock |
-| [X4](../x4/market-and-pricing.md) | **delisted**; was ~$69 |
-| [X4 Pro](../x4-pro/market-and-pricing.md) | **$99.00**, in stock |
-| **X4 Classic** | **never priced** |
-| [S4](../s4/README.md) | ¥299 / ¥339 ≈ US$47 (China, 2026-04) |
-
-If the X4C ever launches internationally, the plausible slot is **between the X3
-and the X4 Pro** — S3 and PSRAM like the Pro, but no touchscreen and no
-frontlight, which are the Pro's two most expensive components. **That is
-reasoning, not evidence.**
-
-## The one dated commercial observation that exists
-
-A vendor Shopify collection named `x4-classic`, containing zero devices, on
-**2026-09-04**. Everything else on this page is an absence.
-
----
-
-# Round 2 — dated pricing, 2026-09-11
-
-**No line above was altered.** Everything above was written when this device had
-no price at all.
-
-## Vendor-direct, read from the store API
-
-All figures `USD`, item-only, worldwide shipping from Shenzhen, retrieved
-**2026-09-11** from `https://xteink.com/products.json?limit=250`.
-
-| SKU | Variant | Price | `compare_at_price` | In stock | Grams |
-|---|---|---:|---:|---|---:|
-| `X4Classic-gray` | Mist Gray | **79.00** | 89.00 | yes | 250 |
-| `X4Classic-black` | Space Black | **79.00** | 89.00 | yes | 250 |
-| `X4CW+BW` | Mist Gray + Mist Gray base | 95.00 | 105.00 | yes | 250 |
-| `X4CB+BW` | Space Black + Mist Gray base | 95.00 | 105.00 | yes | 250 |
-| `X4CW+BB` | Mist Gray + Space Black base | 95.00 | 105.00 | yes | 250 |
-| `X4CB+BB` | Space Black + Space Black base | 95.00 | 105.00 | yes | 250 |
-
-`compare_at_price` is a Shopify "was" field. It is **not evidence of a former
-selling price** — the product was published at 79.00 and has never been listed
-at 89.00. Treat it as a marketing anchor.
-
-`grams: 250` is the **shipping weight**, not the device mass. The vendor's own
-spec block says the device is **68 g**.
-
-## Accessories, published 2026-09-06
-
-| SKU family | Item | Price |
-|---|---|---:|
-| `X4C-Tempered-{1,2,3}` | Tempered glass, 1/2/3-pack | 4.99 / 7.99 / 9.99 |
-| `X4C-Matte-{2,4,6}` | Matte PET, 2/4/6-pack | 3.99 / 5.99 / 8.39 |
-| `X4C-ProtectiveC-{MW,MG}` | Hard polycarbonate case, **14 g** | 3.99 |
-| `X4C-MagneticC-{FG,MG,BP,RR,SB,CG}` | Magnetic case, six colours | 8.99 |
-| `Batterybase-sage` | `XTEINK Base Stand & Charging Adapter for X3, x4 Classic and X4 Pro`, published 2026-09-04 | 19.99 — **out of stock at retrieval** |
-| `XTC2P-1` | Magnetic charging adapter (shared X3 / X4C / X4 Pro) | 5.99 |
-| `x3cable-1` | Magnetic pogo-pin cable (shared) | 4.99 |
-
-**The shared-accessory renaming is itself evidence.** Two accessories that on
-2026-09-04 were titled *"for X3 & X4 Pro"* now read *"for X3, x4 Classic and X4
-Pro"*. The X4 Classic uses the **same pogo interface** as the X3 and the X4 Pro.
-
-## Community-reported prices — other regions, other channels
-
-**Not normalised.** Each row states its own region, date and basis.
-
-| Price | Region | Date | Basis | Source |
-|---|---|---|---|---|
-| **€89** X4C, **€110** X4 Pro | EU | 2026-09-07 | storefront, seen by the buyer | [r/XTEINK `1w9jzpn`](https://old.reddit.com/r/XTEINK/comments/1w9jzpn/) post body, firsthand |
-| *"earlier batches… closer to €40"* (X4) | EU | pre-2026-09 | **hearsay** | same post |
-| **£47.70 ≈ €58** for an X4 | UK | *"last minute"*, pre-launch | **firsthand purchase** | u/wowsomuchempty, 11 pts |
-| *"the original X4 at around €60"* | EU | pre-2026-09 | recollection | u/ShrubbyFire1729, 24 pts |
-| *"about 30 % more than original X4"* | — | 2026-09-10 | derived by the commenter | u/chicco1973, 40 pts |
-
-The US$79 store price and the €89 EU price are **not a contradiction**; they were
-not reconciled for VAT, and no EU storefront page was retrieved. **Do not quote a
-single price for this device without a region and a date.**
-
-## What replaced what
-
-| | X4 (replaced) | X4 Classic |
-|---|---|---|
-| Store status 2026-09-11 | **withdrawn**; product record gone; **all four dedicated accessories gone** | listed, in stock |
-| Last observed list price | ~$69 | **$79** |
-| Observed street/used | as low as **$16** used (2026-08-18), £47.70 new (UK, pre-launch) | none — 5 days old |
-
-**The withdrawal is complete.** On 2026-09-04 the X4's four accessories were
-still in the catalogue (all sold out); on 2026-09-11 the product records
-themselves are gone and the `x4-series` collection contains only a reading light
-and a metal ring — items that fit any device in the family.
-
-## The pricing controversy, stated neutrally
-
-The launch-week price threads are dominated by one argument: that the X4 Classic
-costs meaningfully more than the X4 it replaces while adding nothing the
-community asked for (a frontlight) and removing something it valued (USB-C).
-Counting only figures with a firsthand basis: an X4 was bought in the UK for
-**£47.70** shortly before launch; the X4 Classic lists at **US$79 / €89**.
-
-Against that: the X4 Classic is a **different and substantially more capable
-board** — ESP32-S3 with 8 MB PSRAM against an ESP32-C3 with none, native SDMMC
-against SPI shared with the display, a real RTC and an I²C fuel gauge against
-none and a bare ADC, an IMU, six interrupt-driven keys against an ADC ladder, and
-a published 920 mAh cell. **Both statements are true.** The disagreement is about
-whether that is what buyers of a $69 reader wanted.
-
-## Availability risk
-
-One logistics report worth recording:
-[r/XTEINK `1wdbmkb`](https://old.reddit.com/r/XTEINK/comments/1wdbmkb/),
-2026-09-11 — *"Why would X4 Classic shipment be rejected by airline and sent back
-to xteink?"*. A single firsthand report, almost certainly lithium-battery air
-freight, **not** a pattern. Recorded because it is the only shipping datum that
-exists for this SKU.
-
----
-
-## Cross-reference added by the round-2 index merge, 2026-09-11
-
-The round-2 pricing work above was produced by the Xteink session. The
-certification/market session independently enumerated the same catalogue on the same date and
-agrees: **25 products, X4 Classic published 2026-09-06, USD 79.00 bare / USD 95.00 with base.**
-Two sessions, one endpoint, one date, identical figures. Nothing above is changed by this note.
-
-Two items from that session that are **not** already stated above:
-
-- **The store title is `XTEINK X4 Classic (X4 V2)`.** The vendor is asserting that the Classic
-  *is* the second version of the X4 — which is the strongest single piece of evidence for the
-  replacement relationship argued in *What replaced what*.
-- **Six catalogue line-items are services, not products** (handling fees, shipping fee,
-  after-sale charges). Exclude them from any price range: a naive "cheapest item in the store"
-  read returns **USD 1.00**.
-
-Regulatory record for this device, new on 2026-09-11:
-[`certification-and-compliance.md`](certification-and-compliance.md) — FCC `2BTR9-X4C`, granted
-**2026-07-20**, seven weeks before the store listing. The grant date is an independent
-corroboration of the launch timeline that does not depend on the vendor's own store.
diff --git a/devices/xteink/x4-classic/media.md b/devices/xteink/x4-classic/media.md
deleted file mode 100644
index f330551..0000000
--- a/devices/xteink/x4-classic/media.md
+++ /dev/null
@@ -1,135 +0,0 @@
-# Xteink X4 Classic — images and media
-
-**No image of this device exists in this repository, and none was found anywhere.**
-
-## What was searched
-
-| Target | Where | Result |
-|---|---|---|
-| Teardown / PCB | Reddit, 2,136 posts, terms including `xteink teardown`, `xteink x4 classic`, `xteink x4c` | **none** |
-| Owner photographs | same corpus | **none** |
-| Vendor product imagery | `xteink.com` `/products.json` and the `x4-classic` collection | **The device is not in the catalogue**, so it has no images |
-| GitHub | ~200-repository census | **none** |
-| FCC internal photos | not searched | no FCC ID known — and Xteink devices generally carry **no external regulatory marking** |
-
-## The only visual evidence that has ever been claimed
-
-A vendor **video**, in June 2026, in which the community believed it saw this
-device:
-
-> "Could there actually be three devices shown in the video? First the S4, then
-> the X4 Pro and finally 2 devices placed in the dock at the end. At first I
-> assumed the last one was just the standard X4, but after rewatching it a few
-> times I'm not so sure anymore. The front buttons look identical to the X4, but I
-> keep noticing what looks like a button on the left side."
-> — [r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/), 2026-06-22, **300 points** · *interpretation of a video, not a photograph*
-
-That reading was **partly right** (buttons, no touchscreen; and the side button is
-consistent with GPIO0/GPIO7 being side keys) and **partly wrong** (it reported a
-frontlight; the firmware says there is none).
-
-The video itself was **not retrieved** — the thread does not carry a stable link
-in the retrieved JSON. Recorded as an open acquisition: it is currently the only
-known imagery of this device anywhere.
-
-## What one photograph would settle
-
-| Question | Currently |
-|---|---|
-| **Charging connector** — USB-C or pogo? | **Unknown**, and it is a first-order buyer question |
-| Physical size and mass | Unknown |
-| Whether the back is glass or metal | Unknown |
-| External regulatory marking | Unknown (family precedent: none) |
-| Button arrangement as built | Inferred from the firmware map only |
-
-## Related
-
-The [X3 teardowns](../x3/media.md) are the only Xteink internal photography that
-exists, and they are of a **completely different board** (ESP32-C3, different
-panel, different peripherals). They establish the vendor's construction style —
-glass back, glued cell, glued pogo magnets — and nothing about this device.
-
----
-
-## Round 2 — 2026-09-11
-
-**No line above was altered.** Full provenance for everything below is in
-[`media/manifest.json`](media/manifest.json).
-
-### One photograph is now retained
-
-`artifacts/certification/2BTR9-X4C-label.pdf` — the FCC *ID Label and Location
-Info* exhibit, 189,803 bytes, SHA-256
-`605b978782399a0fdcf267848b5459981fd8069ec6e976e0240aff0bde72ba9c`. It embeds a
-single 1039×779 photograph at 220 ppi.
-
-- **Caption.** The X4 Classic's rear face in Mist White, photographed on a blue
-  mat beside a millimetre rule and its magnetic charging adapter. Visible: the
-  `XTEINK` wordmark, the **oval outline of the internal magnet ring** at the
-  centre, the **four gold pogo contacts** on the bottom edge, two button
-  protrusions on the left edge and one on the right.
-- **Alt text.** *"White rectangular e-reader seen from the back, with a small
-  magnetic charging adapter beside it and a ruler for scale."*
-- **Modifications.** None. Retained as the original PDF; no crop, no rotation,
-  no annotation, no watermark removal.
-- **Rights.** Applicant's photograph, published by the US FCC in a public
-  equipment-authorization record. Redistribution status **`unknown`**;
-  disposition `repository`, **unstaged**.
-
-That photograph is the **first image of an X4 Classic anywhere in this
-repository**. It is also a *product* photograph; it shows nothing internal.
-
-### The images that would actually settle the open questions
-
-| Image class | Status |
-|---|---|
-| **FCC Internal Photos** (4.5 MB) | **Exists. Embargoed to 2027-01-16.** |
-| FCC External Photos (825.3 KB) | Exists. Embargoed to 2027-01-16 |
-| FCC Schematics / Block Diagram | Exist. **Permanently confidential** |
-| Community PCB photographs | **None exist.** Asked for publicly 2026-09-10; the only reply confirms none had been posted |
-| Vendor product photography | 14 images on the Shopify CDN. `reference-only` — vendor marketing, no licence offered |
-| Owner photographs | Several launch-week Reddit galleries, all exterior. `reference-only` — no licence offered by any poster |
-
-### Use the sibling's photographs for form-factor questions
-
-The **X4 Light**'s FCC external photographs are **not** embargoed and are
-retained at
-[`../x4-light/artifacts/certification/2BTR9-X4L-external-photos.pdf`](../x4-light/artifacts/certification/2BTR9-X4L-external-photos.pdf)
-(3,485,136 B, SHA-256 `c6457651f19b4cac…`). They show the same enclosure
-generation — same proportions, same magnet outline, same four-pin pogo pad — in
-both black and white, against a millimetre rule.
-
-**They are a different device.** Use them for the shape of this product family.
-**Do not cite them as evidence about the X4 Classic's dimensions or internals.**
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 13:* | FCC internal photos | not searched | no FCC ID known — and Xteink devices generally carry **no external regulatory marking** |
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-classic/media/manifest.json b/devices/xteink/x4-classic/media/manifest.json
deleted file mode 100644
index 2521456..0000000
--- a/devices/xteink/x4-classic/media/manifest.json
+++ /dev/null
@@ -1,91 +0,0 @@
-{
-  "schema": "xteink-media-manifest/1",
-  "device": "xteink/x4-classic",
-  "compiled": "2026-09-11",
-  "statement": "No photograph of an Xteink X4 Classic is retained in this repository. This manifest records what exists, where, under what rights, and when the definitive images become available. It is deliberately a register of absences.",
-  "images": [
-    {
-      "id": "X4C-IMG-FCC-INT",
-      "what": "FCC Internal Photos - PCB, both sides, the definitive teardown",
-      "status": "EXISTS BUT EMBARGOED",
-      "public_from": "2027-01-16",
-      "size_bytes_reported": 4718592,
-      "size_reported_as": "4.5 MB",
-      "source_page": "https://fccid.io/2BTR9-X4C",
-      "direct_url": null,
-      "rightsholder": "Shenzhen Xiaohu Xingtong Technology Co., Ltd., filed with the US FCC",
-      "local_path": null,
-      "caption": "Not yet public. Short-term confidentiality under the applicant's request of 2026-07-20.",
-      "alt": null
-    },
-    {
-      "id": "X4C-IMG-FCC-EXT",
-      "what": "FCC External Photos",
-      "status": "EXISTS BUT EMBARGOED",
-      "public_from": "2027-01-16",
-      "size_reported_as": "825.3 KB",
-      "source_page": "https://fccid.io/2BTR9-X4C",
-      "local_path": null
-    },
-    {
-      "id": "X4C-IMG-FCC-LABEL",
-      "what": "FCC ID Label and Location Info - contains a photograph of the device rear with the compliance label",
-      "status": "PUBLIC, RETAINED",
-      "retrieved": "2026-09-11",
-      "source_page": "https://fccid.io/2BTR9-X4C",
-      "direct_url": "https://fccid.io/2BTR9-X4C/Label/Label-and-Information-9480913.pdf",
-      "local_path": "../artifacts/certification/2BTR9-X4C-label.pdf",
-      "sha256": "605b978782399a0fdcf267848b5459981fd8069ec6e976e0240aff0bde72ba9c",
-      "bytes": 189803,
-      "embedded_images": 1,
-      "rightsholder": "applicant; published by the US FCC as part of an equipment-authorization record",
-      "redistribution_status": "unknown - US federal publication of a third-party submission; commonly mirrored, no explicit grant located",
-      "disposition": "repository, unstaged",
-      "caption": "Device rear in Mist White with the XTEINK wordmark, the oval magnet outline and the four-contact pogo pad at the bottom edge, photographed beside a millimetre rule with the magnetic charging adapter.",
-      "alt": "White rectangular e-reader, rear view, with a magnetic charging adapter beside it and a ruler for scale."
-    },
-    {
-      "id": "X4C-IMG-VENDOR",
-      "what": "Vendor product photography, 14 images on the Shopify CDN",
-      "status": "PUBLIC, NOT RETAINED",
-      "retrieved": "2026-09-11 (metadata only)",
-      "source_page": "https://xteink.com/products/xteink-x4-classic-pocket-ereader",
-      "example_url": "https://cdn.shopify.com/s/files/1/0759/9344/8689/files/8a4bec83b8bf4fa96b4499b1db6dd84f.jpg?v=1788789486",
-      "rightsholder": "Xteink",
-      "redistribution_status": "prohibited-by-default - vendor marketing imagery, no licence offered",
-      "disposition": "reference-only",
-      "note": "Product images were created 2026-09-05 to 2026-09-08; the Space Black hero image was uploaded 2026-09-07T06:58:05-07:00, one day after the listing went live."
-    },
-    {
-      "id": "X4C-IMG-COMMUNITY",
-      "what": "Owner photographs in launch-week Reddit reviews",
-      "status": "PUBLIC, NOT RETAINED",
-      "examples": [
-        "https://old.reddit.com/r/XTEINK/comments/1w7wjw2/ - thickness comparison against X3 and X4, and a side-by-side text-contrast shot",
-        "https://old.reddit.com/r/XTEINK/comments/1w8bfew/ - in-hand shots; the author links an uncompressed original at https://preview.redd.it/dbzhlleo7tnh1.jpeg",
-        "https://old.reddit.com/r/XTEINK/comments/1wco45y/ - 'X4 Classic with custom housing', 452 points, 2026-09-10",
-        "https://old.reddit.com/r/xteinkereader/comments/1w7tc3g/ - what is in the box"
-      ],
-      "rightsholder": "individual Reddit users",
-      "redistribution_status": "unknown - no licence offered by any poster",
-      "disposition": "reference-only",
-      "note": "All are exterior shots. None shows a PCB."
-    },
-    {
-      "id": "X4C-IMG-PCB-COMMUNITY",
-      "what": "Any community photograph of the X4 Classic PCB",
-      "status": "DOES NOT EXIST",
-      "evidence": "https://old.reddit.com/r/xteinkereader/comments/1wcgqub/ - a direct request for exactly this on 2026-09-10 drew one reply saying no such photographs had been posted and that only a handful of units were in public hands.",
-      "resolves_on": "2027-01-16 via the FCC internal photos, or sooner if an owner opens one"
-    }
-  ],
-  "related_retained_elsewhere": [
-    {
-      "what": "FCC external photographs of the sibling XTEINK X4 Light, which shares the enclosure family, the magnet outline and the four-pin pogo pad",
-      "local_path": "../../x4-light/artifacts/certification/2BTR9-X4L-external-photos.pdf",
-      "sha256": "c6457651f19b4cacf48618ee15abcc50839ffa36d1b13fb98a87bfe0d38106d6",
-      "bytes": 3485136,
-      "why_here": "The X4L exhibits are the best public photographs of this enclosure generation, and they are NOT embargoed. Use them for form-factor questions; do not use them as evidence about the X4 Classic's internals."
-    }
-  ]
-}
diff --git a/devices/xteink/x4-classic/performance.md b/devices/xteink/x4-classic/performance.md
deleted file mode 100644
index 63ce596..0000000
--- a/devices/xteink/x4-classic/performance.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Performance — Xteink X4 Classic
-
-> **Nothing in this document was measured by this repository.** No Xteink X4
-> Classic has been in anyone's hands here. Snapshot **2026-09-11**.
-
-This file exists so that the absence is explicit and so that the few numbers that
-*do* exist are separated by evidence class rather than blended into a ranking.
-
-## 1. What is actually known
-
-| Quantity | Value | Class | Source |
-|---|---|---|---|
-| CPU | ESP32-S3 dual Xtensa LX7, 240 MHz | **silicon spec** | [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) |
-| PSRAM | 8 MB octal | silicon spec | same |
-| Display SPI clock, FreeInk | **10 MHz** since commit `39606d5a` (2026-09-09); was 20 MHz | **source** | [`BoardConfig.h`](https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/libs/hardware/BoardConfig/include/BoardConfig.h) |
-| Display SPI clock, OEM | **5 MHz** on the X4 Pro's OEM driver (`SPISettings 0x4C4B40`); **10 MHz** observed on a physical X4 Pro's stock app (`SPI2 CLOCK 0x70c7`) | **third-party measurement, X4 Pro, not X4C** | [`kycube/x4pro-emu` `docs/hardware.md`](https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/hardware.md) |
-| Frame size | 48,000 B per plane (800×480×1 bpp) | **arithmetic** | — |
-| Plane transfer time at 10 MHz | **≈38 ms** for 48,000 B; 48 ms for a 60,000 B transfer | **third-party measurement on X4 Pro** | same |
-| Battery capacity | **920 mAh** | **vendor claim** | store spec block, 2026-09-11 |
-| Mass | **68 g** | vendor claim | same |
-| Thickness | **4.9 mm** | vendor claim | same |
-
-The 38 ms figure is the **SPI transfer** alone. It is not a refresh time: the
-UC8279/SSD1677 waveform dominates, and for the X4 Pro the FreeInk documentation
-quotes ~1800 ms full / ~500 ms fast **without a device measurement**. Those
-numbers are inherited, not verified, and they are for the Pro.
-
-## 2. What is claimed but not measured
-
-Every one of these is a subjective firsthand impression from a launch-week
-reviewer, most of them using a vendor-supplied pre-release unit. **None has a
-method, a sample count or a unit.**
-
-| Claim | Who | Why it is not a measurement |
-|---|---|---|
-| *"Super fast"*, *"everything feels fast and responsive"* | u/Which_Heart_983, vendor-hosted review | no baseline, no timing |
-| *"much more faster and intuitive than the X3"* | u/Comprehensive_Oil426 | different SoC **and** different firmware version; confounded |
-| *"Stock firmware feels very snappy… prefer the reading speed on stock vs Crosspoint"* | u/ajcabrera | firmware comparison, no timings |
-| *"a few extra days from 100 % to 0 %"* vs the X4 | u/ajcabrera | uncontrolled duty cycle; the X4's capacity is unpublished, so even the ratio is unknown |
-| *"Super long battery life"* | u/Which_Heart_983 | — |
-| *"higher contrast display"* / *"letters are darker"* | u/Which_Heart_983, u/Comprehensive_Oil426 | **plausible and unresolved.** Could be a panel-controller batch difference, a waveform change, or observer bias. No photometry |
-
-**One community claim was actively corrected inside its own thread.** Asked
-whether the pixel density improved, u/scamper_ replied *"It does not, it's still
-219"*, and the most careful reviewer (u/ajcabrera) independently wrote *"Both use
-the same 219 PPI screen I believe"*. **The X4C panel density is unchanged from
-the X4.** Treat any "better screen" report as a contrast claim, not a resolution
-claim.
-
-## 3. What is not known at all
-
-- **No deep-sleep current** for this board, or for any ESP32-C3/ESP32-S3 device in
-  this repository. This gap was already recorded in the family's
-  [SoC-choice guide](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  and is unchanged.
-- **No refresh-time measurement** on an X4 Classic in any mode.
-- **No Wi-Fi throughput or range figure.** The FCC grant gives a **conducted**
-  peak of 8.13 dBm class behaviour for the sibling X4L and a 2.30 dBi antenna for
-  the X4C, which bounds EIRP but says nothing about usable throughput.
-- **No boot time, no page-turn latency, no SD read rate.**
-- **No thermal data.** Not expected to matter; not verified.
-
-## 4. What it would take
-
-| Measurement | Method | Cost |
-|---|---|---|
-| Page-turn latency | High-speed video or a photodiode on the panel, 20 repetitions, report median and p95 | one device |
-| Deep-sleep current | Inline µA meter on the cell, device in shipped state, 10-minute average | one device, opened |
-| Refresh time per mode | `micros()` around `EpdBus` `DRF` → `BUSY` release, per controller variant | one device, reflashed |
-| Contrast vs X4 | Same text, same font, same room, calibrated camera or reflectance meter, both devices | two devices |
-| Battery endurance | Fixed page-turn interval, fixed Wi-Fi state, to cut-off, 3 runs | two devices, weeks |
-
-Until then this file should be read as: **the X4 Classic's performance is
-unmeasured, and the things people say about it are impressions.**
diff --git a/devices/xteink/x4-classic/pinouts-and-buses.md b/devices/xteink/x4-classic/pinouts-and-buses.md
deleted file mode 100644
index 22b13b8..0000000
--- a/devices/xteink/x4-classic/pinouts-and-buses.md
+++ /dev/null
@@ -1,188 +0,0 @@
-# Xteink X4 Classic — pinouts and buses
-
-> ESP32-S3. Reconstructed **entirely from a stock flash dump** (`flashx4c.bin`,
-> app0 = `xteink_app` v7.0.11) by the FreeInk maintainers. **No schematic, no
-> teardown, no photograph of this board exists.** Retrieved **2026-09-04**.
-
-## Evidence and how it was decoded
-
-| Tag | Source |
-|---|---|
-| **[SDK]** | `Free-Ink/freeink-sdk` @ `24003795381a6c23630a26472ae3b06550333e71`, `BoardConfig.h` **L1615–1706** |
-| **[DOC]** | same commit, `docs/xteink-x4c-support.md` |
-| **[RE]** | Ghidra analysis of `flashx4c.bin`; IROM offsets quoted below |
-
-Permalink:
-`https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L1615-L1706`
-
-**The decoding method is worth recording**, because it is reusable on any
-ESP-IDF/Arduino firmware dump. A single board-init function `FUN_4214c798`
-registers every GPIO through one config call whose **mode argument is an opaque
-integer**. The maintainers recovered its meaning by **cross-referencing pins whose
-role was already unambiguous**:
-
-| Mode value | Meaning | Deduced from |
-|---:|---|---|
-| **0** | plain `INPUT` | the charge-STAT line, which cannot be an output |
-| **1** | `OUTPUT` | the SPI drive lines and the GPIO1 rail, which must be outputs |
-| **2** | input + ISR | the buttons, which are interrupt-attached |
-
-That is a clean example of proving an encoding from the constrained cases rather
-than assuming it.
-
-## Complete GPIO map
-
-| GPIO | Signal | Dir | Role | Confidence |
-|---:|---|---|---|---|
-| **0** | Button **Left** (side) → up / previous page | in | digital, active-LOW, ISR | HIGH |
-| **1** | **Master peripheral / panel rail** | out | driven HIGH at boot | HIGH |
-| **2** | Button **Right** (bottom key 2) | in | active-LOW, ISR | HIGH |
-| **3** | Button **Power** | in | active-LOW, ISR | HIGH |
-| **4** | **plain input, NOT interrupt-attached** | in | **role PENDING — not a button, not used by the SDK** | — |
-| **5** | Button **Left** (bottom key 1) | in | active-LOW, ISR | HIGH |
-| **6** | **SD power enable** | out | **ACTIVE-LOW**; pulse HIGH 80 ms → LOW 120 ms, hold LOW | HIGH |
-| **7** | Button **Right** (side) → down / next page | in | active-LOW, ISR | HIGH |
-| **8** | Button **Confirm** (bottom key 3) | in | active-LOW, ISR | HIGH |
-| **9** | Button **Back** (bottom key 4) | in | active-LOW, ISR | HIGH |
-| **10** | EPD **RST** | out | active-low reset pulse | HIGH |
-| **11** | EPD **MOSI** | out | write-only, **no MISO** | HIGH |
-| **12** | EPD **SCLK** | out | | HIGH |
-| **13** | EPD **CS** | out | | HIGH |
-| **14** | EPD **DC** | out | command = LOW, data = HIGH | HIGH |
-| **18** | EPD **BUSY** | in | active-high | HIGH |
-| **19 / 20** | USB **D− / D+** | i/o | native S3 USB-OTG, USB-MSC capable | HIGH |
-| **21** | Charge **STAT** | in | active-HIGH — **polarity PENDING** | med |
-| **38 / 39** | I²C **SCL / SDA** | — | 400 kHz | HIGH |
-| **40 / 41 / 42** | SDMMC **DAT0 / CLK / CMD** | i/o | slot 1, 1-bit | HIGH |
-
-`batteryAdc`, `usbDetect`, `display.powerEnable`: unassigned.
-
-### The RE trail, pin by pin
-
-- `FUN_4214d260(bus, 11, 12, 13, 14)` constructs the SPI display bus → **MOSI 11 /
-  SCLK 12 / CS 13 / DC 14**, and stores GPIO14 as the derived bus's D/C pin.
-- The boot path binds the remaining display tuple as `bus / GPIO10 / GPIO18`;
-  `FUN_42148418` pulses `tuple[1]` **HIGH→LOW→HIGH as RESET** → **RST = 10**,
-  leaving `tuple[2]` = **BUSY = 18**.
-- `FUN_4214d4a8` pulses **GPIO6** HIGH for 80 ms, LOW for 120 ms, then runs SDMMC
-  with the active-low gate held LOW → **SD power enable = 6**.
-- The board init constructs the BM8563 RTC and CW2017 gauge on **I²C SDA 39 /
-  SCL 38 @ 400 kHz**.
-
-## Display bus — and the trap versus the X4 Pro
-
-| Signal | **X4 Classic** | X4 Pro | Same? |
-|---|---:|---:|---|
-| SCLK | 12 | 12 | ✅ |
-| MOSI | 11 | 11 | ✅ |
-| CS | 13 | 13 | ✅ |
-| **DC** | **14** | **18** | ❌ |
-| **RST** | **10** | **14** | ❌ |
-| **BUSY** | **18** | **6** | ❌ |
-
-**Three of six display pins are permuted between two boards that share a chassis,
-a panel and an SoC.** Porting display code across without changing them produces
-a controller that resets and runs full-length waveforms but never develops an
-image — the exact symptom that cost the X4 Pro bring-up months. Treat this table
-as the single most important thing on this page.
-
-`displaySpiHz` = **20 MHz** — chosen as the UC8279 serial-write maximum, to avoid
-throttling full-plane anti-aliasing uploads. `GPIO1` supplies the panel rail.
-No custom LUT, no drive voltages, no external PMIC.
-
-**One command-stream difference from the X4 Pro:** the X4C **omits the UC8279 PLL
-(`0x30`) command** that the X4 Pro programs.
-
-## Panel-controller selection — NVS only
-
-The X4C bus has **no MISO**, so the UC81xx `VER (0x70)` / `FLG (0x71)` probe used
-on every other device in the family **cannot work** — the released line always
-floats to `0xFF`. `applyXteinkDisplayController()` special-cases it:
-
-```
-NVS namespace hw_calib, key screenType (u8):
-   1 or 0x0B → UC8179
-   2 or 0x0C → UC8279
-   3 / default / unset → SSD1677
-```
-
-> "X4 Classic has NO MISO line, so the display-bus probe can never read the
-> controller ID (VER always floats to 0xFF). **NVS `hw_calib/screenType` is the
-> ONLY source of truth here — the factory writes it once.**"
-> — **[SDK]** `XteinkDetect.cpp`
-
-**This is a live hazard.** The same SDK warns that `screenType` is unreliable in
-the field *"a full-flash from another unit overwrites it, so it can name the wrong
-panel"* — and on every other board a live bus probe overrides it. **On the X4C
-there is no override.** Restoring an X4C from another unit's full-flash image can
-silently leave it driving the wrong controller.
-
-## Input — seven discrete interrupt-driven buttons
-
-Physical layout = the X4 Pro's **two side keys** + the C3 X4's **four bottom keys**.
-
-| Action | GPIO | Physical position |
-|---|---:|---|
-| Up / previous page | **0** | side, Left |
-| Down / next page | **7** | side, Right |
-| Left | **5** | bottom key 1 |
-| Right | **2** | bottom key 2 |
-| Confirm | **8** | bottom key 3 |
-| Back | **9** | bottom key 4 |
-| Power | **3** | — |
-
-Stock array order is **2, 5, 8, 9** ("Bottom Key 1–4"). The SDK records that the
-mapping was **corrected by hardware testing**: *"the old GPIO8/9 left/right
-assignment made the physical Confirm/Back keys act as Up/Down."*
-
-**Not an ADC ladder.** Every key is its own GPIO with its own interrupt — strictly
-better than the C3 devices' two-pin resistor ladder: chords work, no polling, no
-per-unit calibration. With all six navigation actions mapped, the UI renders
-side-bezel button hints.
-
-**Note the pin reuse:** GPIO2, 5, 8 and 9 are, on the X4 Pro, **touch power, SD
-power, frontlight cool and frontlight warm** respectively. Firmware that
-unconditionally configures those as outputs will fight four buttons here. Always
-gate on `FREEINK_CAP_TOUCH` / `FREEINK_CAP_FRONTLIGHT`.
-
-## I²C bus — SDA 39 / SCL 38 @ 400 kHz
-
-| Address | Device | Component |
-|---|---|---|
-| **0x51** | BM8563 RTC (PCF8563-register-compatible) | [`generic/bm8563`](../../../components/generic/bm8563/README.md) |
-| **0x63** | CW2017 fuel gauge — **needs an 80-byte BATINFO profile** | [`cellwise/cw2017`](../../../components/cellwise/cw2017/README.md) |
-| **0x6B** | QMI8658 6-axis IMU, `WHO_AM_I` = `0x05`, **no interrupt line** | [`qst/qmi8658a`](../../../components/qst/qmi8658a/README.md) |
-
-The IMU init (`CTRL1/2/3/7` at 0x6B) was RE-confirmed from the dump.
-
-## Storage — native SDMMC
-
-CLK **41**, CMD **42**, DAT0 **40**, slot 1, 1-bit. D1/D2/D3 unused.
-Power enable **GPIO6, active-LOW**: driven HIGH 80 ms, then LOW, held LOW while
-mounted. The block device performs that power cycle and **retries it on mount
-failure** — same pattern as the X4 Pro, different pin.
-
-## Resource conflicts
-
-| Resource | Contenders | Note |
-|---|---|---|
-| I²C 39/38 | BM8563, CW2017, QMI8658 | One `Wire` controller; a stalled bus blocks all three |
-| GPIO0 | Side-Left button **and** the S3 boot strap | Holding it at reset enters download mode |
-| GPIO19/20 | native USB only | **Never probe.** The C3 fingerprint pokes SDA20/SCL0 — D+ and a strap here |
-| GPIO2/5/8/9 | Buttons here; **rails and PWM on the X4 Pro** | The most likely cross-model porting bug |
-| GPIO4 | **unknown** | Configured as an input, never read. Do not repurpose until its role is known |
-
-## Bezel insets
-
-`viewableInsets = {9, 7, 3, 7}` — **carried over from the X4 Pro on the grounds of
-identical glass, and explicitly "pending measurement"**. Not independently
-established for this device.
-
-## What is still PENDING
-
-- **The role of GPIO4** — an input, configured but not interrupt-attached and never
-  read by the SDK.
-- **Charge-STAT polarity** on GPIO21.
-- **Panel mount orientation** (ships `NO_FLIP`).
-- Whether the `R2` in the board revision string `ESP32S3_X4R2_CLA` implies an
-  **R1 that shipped**.
diff --git a/devices/xteink/x4-classic/product-history-and-family.md b/devices/xteink/x4-classic/product-history-and-family.md
deleted file mode 100644
index 61ad133..0000000
--- a/devices/xteink/x4-classic/product-history-and-family.md
+++ /dev/null
@@ -1,117 +0,0 @@
-# Product history and family — Xteink X4 Classic (X4C / "X4 V2")
-
-Snapshot **2026-09-11**. Every dated row below cites a source that carries the
-date itself: a Shopify `published_at`/`created_at`, an FCC final-action date, a
-Git commit timestamp, or a Reddit post timestamp.
-
-## The name
-
-**"X4 Classic" and "X4 V2" are the same product.** This is not an inference:
-
-| Evidence | Date | Form |
-|---|---|---|
-| Vendor Reddit post, verbatim: *"**X4 Classic (X4 V2) is coming soon**"* | 2026-09-03 | primary, vendor |
-| Store product title: `XTEINK X4 Classic (X4 V2) Pocket eReader` | 2026-09-06 | primary, vendor API |
-| Four accessory titles, all `XTEINK X4 Classic (X4 V2) …` | 2026-09-06 | primary, vendor API |
-| Product-page FAQ prose: *"The **X4 V2** features a built-in magnetic ring…"* | 2026-09-11 | primary, vendor |
-| Third-party firmware header comment: *"Xteink X4 Classic (also marketed "X4 v2")"* | 2026-09-11 | independent ([`clackups/draftling`](https://github.com/clackups/draftling/blob/92ba7e514f66bbe42a7fea6d38eff45eed82617b/firmware/main/boards/xteink_x4_classic.h)) |
-| FCC device description: `XTEINK X4 Classic`, product code `X4C` | 2026-07-20 | primary, regulatory |
-
-**The 2026-09-04 record's open item — a "vendor-confirmed X4 v2 for September
-2026, spec unknown" — is closed. It was this device.** No separate X4 v2 exists,
-and none is in certification under that name.
-
-### Naming forms in circulation
-
-| Form | Used by |
-|---|---|
-| **X4 Classic** | Vendor titles, FCC device description, FreeInk, CrossPoint |
-| **X4 V2** / **X4 v2** | Vendor's own parenthetical and FAQ prose; the community from April 2026 onward |
-| **X4C** | FCC **product code**, FreeInk doc filename `xteink-x4c-support.md`, community shorthand |
-| **"V1"** for the original X4 | Owner usage, e.g. the vendor-hosted review *"different from the V1"* |
-| `ESP32S3_X4_CLA` / `ESP32S3_X4R2_CLA` | Board tag and revision string in the stock firmware |
-
-## Dated timeline
-
-| Date | Event | Source class |
-|---|---|---|
-| **2025-12-21** | Grantee `2BTR9` registered with the FCC — *Shenzhen Xiaohu Xingtong Technology Co., Ltd.*, Longhua District, Shenzhen | regulatory |
-| 2025-12-26 | FCC ID `2BTR9-XTEINKX3` granted (**X3**) | regulatory |
-| 2026-01-05 | FCC ID `2BTR9-XTEINKX4` granted (**X4** — the "V1") | regulatory |
-| **2026-04-23** | First public "X4 V2" speculation: [r/xteinkereader `1stt8ak`](https://old.reddit.com/r/xteinkereader/comments/1stt8ak/) *"Looks like they're making a X4 V2 Pro with backlight!"*, 47 pts | community |
-| 2026-04-24 → 2026-08 | ~25 further "X4 v2" threads; the community conflates **X4 V2** (this device) and **X4 V2 Pro** (which became the X4 Pro) | community |
-| **2026-06-16** | FCC ID `2BTR9-X4PRO` granted (**X4 Pro**) | regulatory |
-| **2026-06-22** | [r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/) 300 pts — a buttons-only S3 device spotted in a vendor Rednote video. **Right about buttons and no touch; wrong about a frontlight** | community |
-| 2026-07-20 | **FCC ID `2BTR9-X4C` filed and granted.** Short-term confidentiality on photos/manual to 2027-01-16; **permanent** on schematics and block diagram | regulatory |
-| **2026-07-23** | [r/XTEINK `1v4824q`](https://old.reddit.com/r/XTEINK/comments/1v4824q/) 44 pts — a community member finds the filing and publishes the FCC ID. Predicts: refresh of the X4, buttons only, no touch, **pogo retained**. All four correct | community |
-| 2026-07-21 | X4 Pro listed on `xteink.com` at **US$99** (`published_at`) | vendor API |
-| **2026-08-03 05:06:01 −0700** | X4 Classic product record **created** in Shopify (unpublished draft) | vendor API |
-| **2026-08-13** | **FCC ID `2BTR9-X4L` granted — "XTEINK X4 Light"**, a *sixth* device, still unannounced at this snapshot → [`../x4-light/`](../x4-light/README.md) | regulatory |
-| 2026-08-29 | [r/XTEINK `1w1tcx9`](https://old.reddit.com/r/XTEINK/comments/1w1tcx9/) 80 pts, *"Well well look what we have here"* | community |
-| 2026-08-31 19:22 → 23:43 −0700 | Four X4C accessory records created in Shopify | vendor API |
-| 2026-08-31 | Shopify collection `x4-classic` **published** (still deviceless) | vendor API |
-| **2026-09-01** | FreeInk SDK commit `2400379` — the `XTEINK_X4_CLASSIC` profile as the 2026-09-04 sweep read it | source |
-| **2026-09-03** | **Vendor announcement**, r/xteinkereader `1w63yyl`, 806 pts | vendor |
-| 2026-09-04 | *Prior research snapshot.* `x4-classic` collection contained **4 generic accessories and no device** | vendor API |
-| 2026-09-04 23:22 −0700 | `XTEINK Base Stand & Charging Adapter for X3, x4 Classic and X4 Pro` published, **US$19.99** | vendor API |
-| 2026-09-05 00:17 −0700 | Reader **+ base bundle** variants created, US$95.00 | vendor API |
-| **2026-09-05** | Review embargo lifts — 13 posts in one day, incl. two detailed pre-release reviews | community |
-| **2026-09-06 19:57:20 −0700** | **X4 Classic published — US$79.00, `X4Classic-gray` / `X4Classic-black`** | vendor API |
-| 2026-09-06 20:44 −0700 | Four X4C accessories published | vendor API |
-| 2026-09-08 | Founder letter on pogo vs USB-C, 616 pts / **730 comments** | vendor |
-| **2026-09-09** | FreeInk commit `39606d5a` drops every Xteink `displaySpiHz` from 20 MHz to **10 MHz** | source |
-| 2026-09-10 | First public request for X4C PCB photographs; **nobody has opened one** | community |
-| 2026-09-11 | X4 accessories **withdrawn** from the catalogue; `x4-series` collection reduced to two generic items | vendor API |
-| **2027-01-16** | FCC internal photos, external photos, user manual and test-setup photos become public | scheduled |
-
-## Where it sits in the family
-
-The vendor's own device-only collection (`machine`) on 2026-09-11 contains
-**exactly three products**:
-
-| | X3 | **X4 Classic** | X4 Pro |
-|---|---|---|---|
-| Price | $69 | **$79** | $99 |
-| Published | 2025-12-11 | **2026-09-06** | 2026-07-21 |
-| SoC | ESP32-C3 | **ESP32-S3** | ESP32-S3 |
-| Panel | 3.7″ 792×528 | **4.26″ 800×480** | 4.26″ 800×480 |
-| Touch | ✗ | **✗** | GT911 |
-| Frontlight | ✗ | **✗** | dual warm/cool |
-| Port | pogo | **pogo** | pogo |
-
-**The X4 is not in it.** The X4 Classic did not join the family — it **replaced**
-the X4, and the replacement is complete at the catalogue level: the X4's product
-record is gone, all four of its dedicated accessories are gone, and the
-`x4-series` collection holds only two generic items that fit anything.
-
-### What "Classic" means here, and what it does not
-
-It is **not** a cheaper or cut-down variant. It is the **successor to the
-entry-level model**, priced US$10 above the model it replaces and US$20 below the
-Pro. Its ancestry is split:
-
-- **From the X4 Pro** it takes the entire board: ESP32-S3, 16 MB flash, 8 MB
-  PSRAM, the 4.26″ glass, the three-way panel-controller stack, native SDMMC, the
-  BM8563 RTC, the CW2017 gauge, the pogo charging.
-- **From the C3 X4** it takes the four bottom keys and the buttons-only reading
-  model.
-- **From neither** it takes a QMI8658 IMU (which the X3 has and the Pro does not)
-  and a 920 mAh cell.
-
-The community's own summary, offered as criticism and accurate as description:
-**u/Aelydam, *"disadvantages of the X4 + disadvantages of the Pro = Classic"***
-([`1w7wjw2`](https://old.reddit.com/r/XTEINK/comments/1w7wjw2/), 35 pts) — it
-keeps the X4's missing frontlight and the Pro's missing USB-C.
-
-## The one thing everybody asked for and did not get
-
-A **buttons-only reader with a frontlight** was the single most-requested
-configuration across the whole sample: four of the five top replies to the
-vendor's own announcement, and a recurring thread from April through September.
-The X4 Classic does not have one.
-
-**It is already certified.** `2BTR9-X4L`, *"XTEINK X4 Light"*, granted
-2026-08-13 — six weeks before the X4 Classic shipped, and three weeks before the
-announcement that drew those replies. See [`../x4-light/`](../x4-light/README.md).
-**Whether "Light" means frontlight or lightweight is not established by the
-filing**, and this record does not claim it does.
diff --git a/devices/xteink/x4-classic/projects-and-community.md b/devices/xteink/x4-classic/projects-and-community.md
deleted file mode 100644
index 43fbad1..0000000
--- a/devices/xteink/x4-classic/projects-and-community.md
+++ /dev/null
@@ -1,135 +0,0 @@
-# Firmware projects supporting the Xteink X4 Classic
-
-Census **2026-09-11**. Every entry is pinned to a commit. Support is graded by
-**whether anyone has run it on X4 Classic hardware**, which is the only grade
-that matters for a board whose pinout has never been verified against a physical
-unit.
-
-| Grade | Meaning |
-|---|---|
-| **A** | Built **and** run on a physical X4 Classic by a named party |
-| **B** | Board profile present, built, **never run on X4C hardware** |
-| **C** | Board profile present, copied from another project |
-| **D** | Community reports of it working, no primary artefact |
-
-## The projects
-
-### FreeInk SDK — grade **B**, and the origin of everything
-
-| | |
-|---|---|
-| Repo | [`Free-Ink/freeink-sdk`](https://github.com/Free-Ink/freeink-sdk) |
-| HEAD at census | **`9f4d3f9ca675e64cc9d616081f39a33cdefce57e`**, 2026-09-10 |
-| Stars | 253 |
-| Profile | `BoardConfig::XTEINK_X4_CLASSIC`, `Board::XteinkX4Classic` |
-| Build | `-DFREEINK_DEVICE_X4CLASSIC=1`, env `[env:x4c]` |
-| Doc | [`docs/xteink-x4c-support.md`](https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/docs/xteink-x4c-support.md) |
-| Derived from | A **privately held** X4C OEM flash dump, reverse-engineered in Ghidra |
-
-**Change since the 2026-09-04 snapshot: exactly one line.** Commit
-[`39606d5a`](https://github.com/Free-Ink/freeink-sdk/commit/39606d5a) (2026-09-09,
-*"Fix e-ink display buffer tracking and optimize SPI writes"*) replaced the
-X4C's literal `20000000` `displaySpiHz` with a shared
-`XTEINK_DISPLAY_SPI_HZ = 10000000u` applied to **every** Xteink profile. The
-support doc changed the matching sentence. Nothing else in the profile moved.
-
-**No new Xteink board entered `enum class Board` between `2400379` (2026-09-01)
-and HEAD.** The enum gained `M5PaperS3`, `EegoA4`, `OnePage` and `WsEpaper397` —
-all other vendors. This is the strongest available evidence that **no new Xteink
-SKU exists between the X4 and the X4 Pro** beyond the X4 Classic itself.
-
-### `clackups/draftling` — grade **B** for X4C, grade **A** for X4 Pro
-
-| | |
-|---|---|
-| Repo | [`clackups/draftling`](https://github.com/clackups/draftling) |
-| HEAD at census | `92ba7e514f66bbe42a7fea6d38eff45eed82617b`, pushed **2026-09-11** |
-| Licence | **MIT** · 71 stars · created 2026-06-05 |
-| What it is | A **writerdeck** firmware for ESP32-S3 and ESP32-P4 — an editor, not a reader |
-| X4C files | `firmware/main/boards/xteink_x4_classic.h`, `sdkconfig.defaults.xteink_x4_classic`, `partitions_xteink_x4_classic.csv`, a chapter in `HARDWARE.md` |
-
-**The most useful third-party document about this board.** It is an independent
-*reading* of the FreeInk profile by someone building a different product, which
-surfaces things the profile alone does not:
-
-- It states the naming equivalence in a source comment: *"Xteink X4 Classic
-  (also marketed "X4 v2")"*.
-- It maps the eight inputs to an editor: Power = F1 / 2 s = forget BLE keyboards;
-  side keys = Up/Down; bottom keys = Left/Right/Enter/Esc; **GPIO4 ignored**,
-  matching FreeInk.
-- It names the panel-pin difference from the Pro explicitly: **DC 14, RST 10,
-  BUSY 18** here versus **18 / 14 / 6** on the Pro, with SCLK/MOSI/CS the same.
-- It notes the X4C's UC8279 init **omits the PLL (`0x30`) command** the Pro
-  programs.
-- It keeps a **dual-OTA partition table on purpose**, because the stock and
-  CrossPoint updaters both refuse a table with no `otadata` — *"Partition table
-  has no otadata partition"*. A single-`factory` table leaves the device unable
-  to accept either without a USB reflash, and **the X4 Classic has no USB
-  socket**, which makes that a much worse trap here than on a dev board.
-
-**It is honest about its limits**, verbatim: *"**This board has been added
-without on-hardware testing.**"*
-
-Its **X4 Pro** support, by contrast, is grade **A** and produced two real
-findings — see [`../x4-pro/README.md`](../x4-pro/README.md).
-
-### CrossPoint Reader — grade **D**
-
-[`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader)
-carries `XteinkX4Classic` in `lib/hal/HalGPIO.cpp` and an `x4c` env in
-`platformio.ini`. The simulator mirrors it.
-
-Community evidence of it actually running:
-
-- [r/CrossPointReader `1wbmagp`](https://old.reddit.com/r/CrossPointReader/comments/1wbmagp/),
-  2026-09-09, "Xteink X4 Classic support".
-- u/Diirge, 2026-09-10: *"CrossPoint sleep screen rendering got much better as of
-  today on the x4c fyi"* — **firsthand, dated, on-device**, the single best
-  evidence that CrossPoint runs on an X4C.
-- [r/XTEINK `1wctkd6`](https://old.reddit.com/r/XTEINK/comments/1wctkd6/),
-  2026-09-10, "Crosspoint or Crossink? Differences on x4 classic".
-
-No build log, no flash log and no screenshot from an X4C was retrieved. **Grade D
-is deliberate**: it is very probably working, and this repository has no artefact
-proving it.
-
-### `vjFaLk/esphome-xteink` — grade **C**
-
-ESPHome components (MIT, created 2026-08-30). **Vendors the FreeInk SDK verbatim**
-at `components/xteink/sdk/…/BoardConfig.h`. Not an independent reading; it is the
-same file in a different tree. Useful only as a distribution channel.
-
-### `mohitagw15856/Inkkit` — grade **C**
-
-Shared HAL library (MIT, created 2026-07-29). `src/BoardConfig.h` is a copy. Its
-own description scopes it to *"Xteink X4/X3, ESP32-C3"* — the X4C entry is
-inherited, not targeted.
-
-### `kycube/x4pro-emu` — X4 Pro only, but read it anyway
-
-Not an X4C project. It matters here because the X4 Pro flash dump it publishes
-contains **`ESP32S3_X4_CLA` and `ESP32S3_X4R2_CLA`**, proving the stock firmware
-is one binary family across both boards. See [`README.md`](README.md) §`R2`.
-
-### `x4pro-emu`-adjacent: no X4C emulator exists
-
-A QEMU model of the X4 Pro now exists and boots both stock and CrossPoint. **No
-equivalent exists for the X4 Classic**, and building one would be cheap: same
-SoC, same flash map, same panel stack, fewer peripherals. It is the lowest-cost
-way to test X4C firmware without the hardware, and nobody has done it.
-
-## Independent-custodian count for this record
-
-| Custodian | Independent of FreeInk? | Hardware? |
-|---|---|---|
-| FreeInk SDK | — | private X4C dump, not published |
-| `clackups/draftling` | **reading only** — cites FreeInk as its source | **no** |
-| CrossPoint Reader | no | community reports only |
-| `esphome-xteink`, `Inkkit` | no — verbatim copies | no |
-| **FCC `2BTR9-X4C`** | **yes** | **yes — but photos embargoed to 2027-01-16** |
-| **Vendor store + spec block** | **yes** | product-level only |
-
-**Two genuinely independent custodians now exist** (the FCC grant and the vendor
-listing), where on 2026-09-04 there were none. Neither is a board-level custodian.
-**The hardware claims in this record still rest on a single private firmware
-dump**, and that will remain true until 2027-01-16 or until somebody opens one.
diff --git a/devices/xteink/x4-classic/research-log.md b/devices/xteink/x4-classic/research-log.md
deleted file mode 100644
index a5e2126..0000000
--- a/devices/xteink/x4-classic/research-log.md
+++ /dev/null
@@ -1,148 +0,0 @@
-# Research log — Xteink X4 Classic (X4C / "X4 V2")
-
-Two passes are recorded here. **Pass 1** (2026-09-04) is summarised from the
-sweep that created this record. **Pass 2** (2026-09-11) is this session and is
-logged query-by-query.
-
----
-
-## 0. A date discrepancy, recorded rather than papered over
-
-The task brief for pass 2 stated the date as **2026-09-07**. The host clock read
-**2026-09-11T22:52:42Z**, and the vendor's Shopify API independently returned
-`updated_at: 2026-09-11T15:52:09-07:00` on every product, plus a product image
-created `2026-09-08T23:42:57-07:00` and a Judge.me review created
-`2026-09-08 04:57:34 UTC`.
-
-**Three independent remote sources put "now" at or after 2026-09-08**, so the
-brief's 2026-09-07 is stale and **2026-09-11 is used as the retrieval date
-throughout**. Nothing in this record depends on the difference; the launch date
-(2026-09-06) is read from the vendor's own `published_at` and is unaffected.
-
----
-
-## 1. Pass 2 search ledger — 2026-09-11
-
-### 1.1 Vendor (Shopify), UA `Mozilla/5.0 … Chrome/131.0.0.0`
-
-| # | Endpoint | Result | Disposition |
-|---|---|---|---|
-| V1 | `https://xteink.com/products.json?limit=250&page=1` | 200, 122,443 B, **25 products** | **useful** — the launch evidence |
-| V2 | `…&page=2`, `…&page=3` | 200, 15 B each (`{"products":[]}`) | catalogue is one page |
-| V3 | `https://xteink.com/collections.json?limit=250` | 200, 4,459 B, 11 collections | unchanged from 2026-09-04 |
-| V4 | `https://xteink.com/collections/<handle>/products.json?limit=250` × 11 | all 200 | **useful** — see §1.2 |
-| V5 | `https://xteink.com/products/xteink-x4-classic-pocket-ereader` | 200, 919,867 B HTML | **useful** — the spec block lives here, not in `body_html` |
-| V6 | `…/xteink-x4-classic-pocket-ereader.js` | 200, 15,497 B | duplicate of V1's record |
-
-**Retrieval finding worth reusing:** this product's `body_html` is **empty**. The
-entire specification table is a theme section rendered server-side into the
-product page. An agent that reads only `/products.json` will conclude the vendor
-published no specifications at all. **Fetch the HTML too.**
-
-### 1.2 Collection diff, 2026-09-04 → 2026-09-11
-
-| Collection | 2026-09-04 | 2026-09-11 | Reading |
-|---|---:|---:|---|
-| `x4-classic` | **4** — reading light, metal ring, X3/X4-Pro adapter, X3/X4-Pro cable. **No device** | **10** — device + 4 X4C-specific accessories + charging base | **The launch** |
-| `machine` (devices only) | X3, X4 Pro | **X3 $69 · X4 Classic $79 · X4 Pro $99** | The vendor's own three-device line-up |
-| `homepage-display` | 4 | 4, now **led by the X4 Classic** | Promoted to hero |
-| `x4-series` | accessories | **2 generic accessories only** | The X4 line is finished |
-| `x3-series` | 9 | 10 (+ charging base) | — |
-| `x4-pro-series` | 8 | 9 (+ charging base) | — |
-
-Four X4 accessories that existed on 2026-09-04 are **gone** from the catalogue
-entirely: `xteink-x4-matte-screen-protector`, `xteink-x4-protective-case`,
-`xteink-x4-screen-protector`, `xteink-x4-magnetic-case`. The X4 is not merely
-delisted; its accessories have been withdrawn.
-
-### 1.3 Regulatory — `fccid.io`
-
-| # | Query | Result |
-|---|---|---|
-| R1 | `https://fccid.io/2BTR9-X4C` with Chrome UA | **403** |
-| R2 | same URL with `WhatsApp/2.23.20.0` | **200, 22,338 B** |
-| R3 | `https://fcc.report/FCC-ID/2BTR9-X4C`, four different UAs | **403 on all four** |
-| R4 | `apps.fcc.gov/oetcf/eas/reports/GenericSearchResult.cfm?fcc_id=2BTR9-X4C` | **403** |
-| R5 | `https://fccid.io/2BTR9` (grantee index) | 200 — **five FCC IDs**, including one undocumented product |
-| R6 | `https://fccid.io/<id>/<Type>/<Name>-<docid>.pdf` | **200, `%PDF`** for every public exhibit |
-
-**The single most valuable retrieval trick of this pass.** `fccid.io` blocks a
-desktop-Chrome UA and serves a link-preview UA. The PDF pattern is
-`https://fccid.io/<FCCID>/<Type>/<Slug>-<DocumentID>.pdf`, where `<DocumentID>` is
-the numeric id in the `href` on the FCC ID page. Recorded in
-[`commands.md`](commands.md) and in the repository's
-[crawler access table](../../../ai-crawler-site-access-table.md).
-
-**A trap caught while doing this.** `https://www.crystalfontz.com/controllers/UltraChip/UC8179/478/`
-returns a **valid 477 KB PDF** — which is the *GOODiX GT911 Programming Guide*.
-The path segment `UC8179` is decorative; the trailing number is the only thing
-that selects a document. Validating by magic bytes alone would have filed a
-touch-controller manual as a display-controller datasheet. The correct id for
-UC8179 is `517`, read from the page's own `datasheet-viewer.php?id=` link.
-
-### 1.4 Firmware / board definitions
-
-| # | Query | Result |
-|---|---|---|
-| F1 | `gh api repos/Free-Ink/freeink-sdk/commits/main` | HEAD `9f4d3f9ca675e64cc9d616081f39a33cdefce57e`, 2026-09-10 |
-| F2 | `enum class Board` at that commit | **No new Xteink board.** Still `XteinkX4`, `XteinkX3`, `XteinkX3Uc8279`, `XteinkX4Pro`, `XteinkX4Classic`. New non-Xteink boards: `M5PaperS3`, `EegoA4`, `OnePage`, `WsEpaper397` |
-| F3 | `diff` of `XTEINK_X4_CLASSIC` profile, `2400379` → `9f4d3f9` | **One change**: `displaySpiHz` 20 MHz → shared `XTEINK_DISPLAY_SPI_HZ = 10000000u` |
-| F4 | `commits?path=…/BoardConfig.h&since=2026-09-01` | two: `3fe3936d` (Waveshare board, 09-05), **`39606d5a`** (*"Fix e-ink display buffer tracking and optimize SPI writes"*, 09-09) |
-| F5 | `diff` of `docs/xteink-x4c-support.md` | one line: the same 20 → 10 MHz statement |
-| F6 | code search `"X4R1_CLA"` | **`total_count: 0`** — no `R1` string exists anywhere on GitHub |
-| F7 | code search `"X4R2_CLA" xteink` | 5 hits: `Free-Ink/freeink-sdk` ×2, **`kycube/x4pro-emu`**, `mohitagw15856/Inkkit`, `vjFaLk/esphome-xteink` |
-| F8 | code search `"X4 V2" xteink` | 11 hits, 9 of them in **`clackups/draftling`** |
-| F9 | code search `xteink "X4 Classic"` | 47 hits |
-
-**F6 is a negative result and is the point.** A search that returns zero is the
-strongest available evidence that no public firmware has ever named an X4C R1.
-
-### 1.5 Independent projects found (pass 2 only)
-
-| Repo | Created | Licence | Why it matters |
-|---|---|---|---|
-| [`clackups/draftling`](https://github.com/clackups/draftling) | 2026-06-05 | MIT | ESP32-S3/P4 writerdeck firmware with a **hand-written X4 Classic board header** and a `HARDWARE.md` chapter. Independently states the X4C = "X4 v2" equivalence. **Explicitly untested on X4C hardware**, but **tested on X4 Pro hardware** |
-| [`kycube/x4pro-emu`](https://github.com/kycube/x4pro-emu) | **2026-09-07** | none stated | QEMU emulator built against a **physical X4 Pro**: esptool chip-id, eFuse dump, twice-verified 16 MB flash dump, I²C and LEDC traces |
-| [`vjFaLk/esphome-xteink`](https://github.com/vjFaLk/esphome-xteink) | 2026-08-30 | MIT | ESPHome components; vendors the FreeInk SDK verbatim (not independent) |
-| [`mohitagw15856/Inkkit`](https://github.com/mohitagw15856/Inkkit) | 2026-07-29 | MIT | Shared HAL; copies `BoardConfig.h` (not independent) |
-
-### 1.6 Reddit — `old.reddit.com`, UA `WhatsApp/2.23.20.0`
-
-All 11 requests returned **200**. `www.reddit.com` was not attempted (403
-documented elsewhere in this repository).
-
-| # | Query | Hits |
-|---|---|---|
-| D1–D5 | `search.json?q=…&sort=new&t=month` for `xteink x4 classic`, `x4 v2 xteink`, `xteink x4 classic review`, `xteink new`, `x4 classic` | 100 each; **332 unique**, 213 relevant |
-| D6–D11 | `r/<sub>/search.json?q="X4 Classic" OR "X4 V2" OR X4C&restrict_sr=1&t=year` for r/XTEINK, r/xteinkereader, r/xteinkHax, r/CrossPointReader, r/eink, r/ereader | 41 / 47 / 3 / 2 / 0 / 1 → **94 unique**, spanning 2026-04-23 → 2026-09-11 |
-| D12–D23 | 12 full comment trees (`<permalink>.json?limit=200`) | see [`community.md`](community.md) |
-
-**r/eink returned 0 and r/ereader returned 1** for a launch that generated
-hundreds of posts in the three dedicated subreddits. The X4C conversation is
-almost entirely inside the vendor-adjacent communities; a search restricted to
-the general e-ink subreddits would have missed the launch completely.
-
-### 1.7 Not searched, and why
-
-- **JD.com, Taobao, Xianyu, Xiaohongshu, WeChat shop** — not retrieved. The
-  Chinese-market price and launch date for the X4C are therefore **unknown**, and
-  no figure in this record claims otherwise. Declared exclusion, not an
-  exhausted search.
-- **AliExpress** — not retrieved this pass. The X4C is nine days old
-  internationally; marketplace listings at this age are usually the vendor's own
-  store mirror and add nothing.
-- **Bilibili / YouTube video reviews** — not retrieved. Reddit text reviews were
-  used instead and are cited individually.
-- **`web.archive.org` CDX for `xteink.com`** — timed out at 60 s on 2026-09-04 and
-  was **not retried** this pass. The withdrawn X4 accessory pages are therefore
-  still unrecovered.
-- **`fcc.report`** — 403 on every UA tried. `fccid.io` served the same documents.
-
-## 2. Stopping criterion for pass 2
-
-Stopped when: the vendor API, the vendor HTML, the FCC grantee index and all
-five FCC device pages, the FreeInk SDK at HEAD, GitHub code search on six
-distinct strings, and six subreddits over a one-year window had each been
-searched; and when two further broad Reddit passes returned only duplicates of
-the 94 posts already catalogued. **This is a dated broad-coverage snapshot, not a
-proof that nothing else exists.**
diff --git a/devices/xteink/x4-classic/resources-and-conflicts.md b/devices/xteink/x4-classic/resources-and-conflicts.md
deleted file mode 100644
index a5fbb89..0000000
--- a/devices/xteink/x4-classic/resources-and-conflicts.md
+++ /dev/null
@@ -1,129 +0,0 @@
-# Resources and conflicts — Xteink X4 Classic
-
-Snapshot **2026-09-11**. Pin data from the FreeInk profile
-`BoardConfig::XTEINK_X4_CLASSIC` at commit
-[`9f4d3f9`](https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/libs/hardware/BoardConfig/include/BoardConfig.h)
-and `docs/xteink-x4c-support.md`, **corroborated independently** by
-[`clackups/draftling`'s `xteink_x4_classic.h`](https://github.com/clackups/draftling/blob/92ba7e514f66bbe42a7fea6d38eff45eed82617b/firmware/main/boards/xteink_x4_classic.h),
-a hand-written board header for a different firmware project.
-
-**Both sources derive from the same OEM reverse engineering**, so they are not
-fully independent — Draftling's header names FreeInk as its origin and states
-plainly *"This board has NOT been tested on physical hardware."* They are counted
-here as **one custodian with a second reading**, not two custodians. The full
-tables live in [`pinouts-and-buses.md`](pinouts-and-buses.md); this file is about
-ownership, arbitration and what cannot run at the same time.
-
-## 1. GPIO ownership
-
-| GPIO | Owner | Direction | Contention |
-|---|---|---|---|
-| 0 | **Left / page-up key** | in, pull-up, ISR | **Also the ESP32-S3 boot strap.** Held at reset → download mode. A user pressing Left during a power-on reset will not boot the app |
-| 1 | **Master peripheral rail latch** | out, driven HIGH at boot | **Everything** — panel, SD and the I²C devices are unpowered until this is high. Nothing else may touch it |
-| 2 | **Bottom-right key** | in, pull-up, ISR | On the X4 Pro this pin is the **GT911 touch power enable**. Porting Pro code here drives a button pin as an output |
-| 3 | **Power key** | in, pull-up, ISR | **The only EXT1 deep-sleep wake source.** Also the pin a wake handler must re-sample |
-| 4 | **unassigned discrete input** | in | Role unknown. Neither FreeInk nor Draftling uses it. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-| 5 | **Bottom-left key** | in, pull-up, ISR | On the X4 Pro this is the **SD power gate**. Same porting hazard as GPIO2, in the opposite direction |
-| 6 | **SD power enable**, active-LOW | out | On the X4 Pro this is the panel **BUSY** input. **Three different meanings for GPIO6 across the family** |
-| 7 | **Right / page-down key** | in, pull-up, ISR | — |
-| 8 | **Confirm key** | in, pull-up, ISR | On the X4 Pro this is the **cool frontlight LEDC channel** |
-| 9 | **Back key** | in, pull-up, ISR | On the X4 Pro this is the **warm frontlight LEDC channel** |
-| 10 | **Panel RST** | out | On the X4 Pro GPIO10 is the **GT911 INT / address-select** pin |
-| 11 | Panel MOSI (SPI2) | out | Write-only; **no MISO on this board** |
-| 12 | Panel SCLK (SPI2) | out | — |
-| 13 | Panel CS | out | — |
-| 14 | Panel DC | out | On the X4 Pro GPIO14 is **RST** |
-| 18 | Panel BUSY | in | On the X4 Pro GPIO18 is **DC** |
-| 19 / 20 | Native USB D− / D+ | — | USB-OTG / USB-MSC capable. **There is no USB socket on the enclosure** — the port is pads, not a connector |
-| 21 | Charger `STAT` | in, active-HIGH | Polarity is `inferred` from the profile field, not observed |
-| 38 / 39 | I²C SCL / SDA @ 400 kHz | — | Shared by three devices, see §2 |
-| 40 / 41 / 42 | SDMMC DAT0 / CLK / CMD, slot 1, 1-bit | — | Native peripheral, not bit-banged |
-
-### The three-way GPIO trap, stated once
-
-**GPIO2, GPIO5, GPIO6, GPIO8, GPIO9, GPIO10, GPIO14 and GPIO18 all mean
-something different on the X4 Classic than on the X4 Pro**, even though the two
-boards share a SoC, a panel, a flash size and most of a firmware. Five of them
-change from *output* to *input* or the reverse.
-
-Porting an X4 Pro driver to the X4 Classic without re-reading the profile will
-drive four button pins as outputs (2, 5, 8, 9) and read two output pins as
-inputs. **Never port power or display code between these two boards by pin
-number.** This is the X4 Classic's version of the family-wide GPIO13 hazard
-already recorded in the [family index](../README.md).
-
-## 2. I²C bus — SDA 39 / SCL 38 @ 400 kHz
-
-| Address | Device | Owner | Notes |
-|---|---|---|---|
-| `0x51` | **BM8563 RTC** | timekeeping | PCF8563-register-compatible → [`generic/bm8563`](../../../components/generic/bm8563/README.md) |
-| `0x63` | **CW2017 fuel gauge** | battery | Reports 0 % until an 80-byte BATINFO profile is written to `0x10..0x5F` → [`cellwise/cw2017`](../../../components/cellwise/cw2017/README.md) |
-| `0x6B` | **QMI8658 IMU** | Shake-to-Flip | `WHO_AM_I = 0x05`, **no interrupt line** → [`qst/qmi8658a`](../../../components/qst/qmi8658a/README.md) |
-
-**No address collisions.** All three are on one master; there is no second bus
-and no mux. The IMU has no INT pin, so **Shake-to-Flip must be polled**, which is
-a real power cost on a device that otherwise spends its life in deep sleep. No
-measurement of that cost exists.
-
-The X4 Pro carries the same RTC and gauge at the same addresses **plus** a GT911
-at `0x5D`; the X4 Classic's `0x5D` is empty because the touch controller is not
-fitted and GPIO2 — its power enable on the Pro — is a button here.
-
-## 3. SPI2 (FSPI)
-
-Single master, single slave: the panel. **No MISO.** Consequences:
-
-- The boot-time bus probe used on every other Xteink board (write `0x70`/`0x71`,
-  read the reply on a re-purposed MOSI) **cannot run**. The SDK instead reads NVS
-  `hw_calib/screenType` — `1` = UC8179, `2` = UC8279, `3`/absent = SSD1677.
-- **A wiped or re-initialised NVS silently selects the wrong panel driver** and
-  there is no way for firmware to detect the mistake. This is the single most
-  consequential difference between the X4 Classic and every sibling, and it is
-  why `nvs` must be preserved across a reflash. See
-  [`development.md`](development.md) and
-  [`../firmware-ecosystem.md`](../firmware-ecosystem.md).
-
-## 4. Flash and partitions (16 MB, dual-OTA)
-
-| Partition | Offset | Size |
-|---|---|---|
-| `nvs` | `0x009000` | 20 KB |
-| `otadata` | `0x00E000` | 8 KB |
-| `app0` | `0x010000` | 8,060 KB |
-| `app1` | `0x7F0000` | 8,060 KB |
-| `spiffs` | `0xFD0000` | 80 KB |
-| `coredump` | `0xFE4000` | 112 KB |
-
-The layout is identical to the X4 Pro's, as read from a **physical X4 Pro** by
-[`kycube/x4pro-emu`](https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/partitions.md)
-on 2026-09-06 — the first time this table has had a non-SDK witness anywhere in
-this family. **It has not been read off an X4 Classic.**
-
-**`nvs` at `0x009000` holds the panel identity.** Any flashing procedure that
-erases the whole chip destroys it. Draftling's X4C partition table keeps an
-`otadata` partition specifically so the stock and CrossPoint OTA updaters can
-reinstall themselves afterwards.
-
-## 5. Realistic concurrent-use scenarios
-
-| Scenario | Verdict | Why |
-|---|---|---|
-| Panel refresh **+** SD read | **OK** | Different peripherals: SPI2 vs the SDMMC block. The X4's shared-SPI hazard does **not** apply here |
-| Panel refresh **+** I²C poll | **OK** | Independent buses |
-| SD mounted **+** deep sleep | **needs care** | GPIO6 is held LOW while mounted; the sleep path must release or hold it deliberately |
-| Wi-Fi **+** panel refresh | **untested** | Both are current spikes on one cell with no PMIC. Nobody has measured the brown-out margin |
-| USB-MSC **+** anything | **untested, and physically awkward** | The SDK enables MSC, but the enclosure has no USB socket |
-| Shake-to-Flip **+** deep sleep | **contradictory by construction** | The QMI8658 has no interrupt line wired, so motion cannot wake the device. Shake-to-Flip can only work while awake |
-| Button ISR **+** boot | **hazard** | GPIO0 is both the Left key and the boot strap |
-
-## 6. Power rails
-
-There is **no PMIC and no software power-off latch**. GPIO1 gates the peripheral
-rail; the SoC itself cannot be cut from software. "Off" is `esp_deep_sleep_start()`
-with `EXT1` armed on GPIO3, and the pin states of GPIO1/GPIO6/GPIO10 held through
-sleep with `gpio_hold_en`. Draftling's header says this explicitly:
-*"there is no hardware latch that can fully power this board off from software."*
-
-Charging is **pogo-pin only**, four contacts, magnetic. `STAT` on GPIO21. No
-charger IC is on the I²C bus, so **charge state is only ever a single GPIO
-level** — there is no current, voltage or fault reporting from the charger.
diff --git a/devices/xteink/x4-classic/sources.md b/devices/xteink/x4-classic/sources.md
deleted file mode 100644
index 0f0e462..0000000
--- a/devices/xteink/x4-classic/sources.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# Xteink X4 Classic — sources
-
-Retrieved **2026-09-04**. **Note how short this table is** — and that all but two
-rows are the same repository at the same commit. That concentration is the record's
-central weakness.
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Published | Establishes | Limitations |
-|---|---|---|---|---|---|---|---|---|---|
-| **XC01** | `BoardConfig.h` `XTEINK_X4_CLASSIC` L1615–1706 | Free-Ink | community | source (commit-pinned) | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L1615-L1706> | 2026-09-04 | commit 2026-09-01 | **The complete pinout, with explicit per-pin HIGH/PENDING confidence levels and the Ghidra offsets they came from** | Derived from a firmware dump the authors hold privately; **not independently corroborated by anyone** |
-| **XC02** | `docs/xteink-x4c-support.md` | Free-Ink | community | technical note | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/docs/xteink-x4c-support.md> | 2026-09-04 | same | Board tag, revision string, NVS `screenType` mapping, peripherals, partitions, the UC8279 PLL omission | same |
-| **XC03** | `XteinkDetect.cpp` `applyXteinkDisplayController()` | Free-Ink | community | source | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/XteinkDetect/src/XteinkDetect.cpp> | 2026-09-04 | same | **The no-MISO special case** and the NVS-only controller selection | same |
-| **XC04** | `platformio.sample.ini` `[env:x4c]` | Free-Ink | community | build config | same commit | 2026-09-04 | same | Board target, build flags, the `USE_BLOCK_DEVICE_INTERFACE` requirement | — |
-| **XC05** | `x4-classic` Shopify collection | **Xteink** | **primary** | store API | <https://www.xteink.com/collections/x4-classic/products.json?limit=250> | 2026-09-04 | — | **The collection exists and contains no device** — four generic accessories only. Strong evidence of a provisioned-but-unlaunched international SKU | A single-instant snapshot |
-| **XC06** | "Did we just spot a new X4 model? Physical buttons + frontlight but no touchscreen in the latest video?" | r/XTEINK | community | forum, video interpretation | <https://old.reddit.com/r/XTEINK/comments/1ud0d9c/> | 2026-09-04 | 2026-06-22, **300 pts**, 53 comments | The community identified a buttons-only S3 variant ~1 month before the X4 Pro listing | **Interpretation of a vendor video, not a teardown.** The frontlight claim is **contradicted** by the firmware |
-| **XC07** | "Xteink told me the new X4 version 2 is coming in September" | r/xteinkereader | community | forum, vendor-relayed | <https://old.reddit.com/r/xteinkereader/comments/1vxsr0x/> | 2026-09-04 | 2026-08-25, 52 pts, 42 comments | Vendor confirmed via Instagram that an "X4 version 2" is coming; comment claims leaks show **two** devices with pogo pins, one with backlight and no touch | **Hearsay.** Relevant here only because one leaked device may or may not be this one |
-
-## What is conspicuously absent
-
-| Source class | Result |
-|---|---|
-| Vendor product page | **Does not exist** |
-| Vendor specification, manual, images | **None** |
-| Teardown / photography | **None** |
-| Owner reports | **None in 2,136 Reddit posts** |
-| Firmware forks / projects | **None in a ~200-repo GitHub census** |
-| Marketplace listing | **None found** (Chinese marketplaces not searched directly) |
-| Regulatory filing | **None**; and Xteink devices generally carry no external marking |
-
-**Six of seven source classes returned nothing.** Every technical claim in this
-record traces to one repository at one commit.
-
----
-
-## Round 2 — sources added 2026-09-11
-
-**No row above was altered.** Class: `primary` · `authorized mirror` ·
-`credible mirror` · `standard` · `community`.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **XC07** | `products.json` — whole catalogue | Xteink (Shopify) | **primary** | store API | <https://xteink.com/products.json?limit=250&page=1> | 2026-09-11 | product `published_at` **2026-09-06T19:57:20-07:00**, `created_at` 2026-08-03 | **The launch itself**: US$79.00, SKUs `X4Classic-gray`/`-black`, four bundle SKUs at $95, `available: true` | A live snapshot; prices and stock change | `scratch/xteink/vendor-2026-09-07/products-p1.json` |
-| **XC08** | `collections/x4-classic/products.json` | Xteink (Shopify) | primary | store API | <https://xteink.com/collections/x4-classic/products.json?limit=250> | 2026-09-11 | — | The collection now holds **10** products incl. the device; on 2026-09-04 it held **4 accessories and no device** | — | `scratch/xteink/vendor-2026-09-07/coll-x4-classic.json` |
-| **XC09** | `collections/machine/products.json` | Xteink (Shopify) | primary | store API | <https://xteink.com/collections/machine/products.json?limit=250> | 2026-09-11 | — | The vendor's device-only line-up is **exactly three**: X3 $69, X4 Classic $79, X4 Pro $99. **The X4 is absent** | — | `scratch/xteink/vendor-2026-09-07/coll-machine.json` |
-| **XC10** | X4 Classic product page (rendered HTML) | Xteink | **primary** | official page | <https://xteink.com/products/xteink-x4-classic-pocket-ereader> | 2026-09-11 | — | **The whole specification block**: 4.3″, 219 PPI, 114×69×4.9 mm, 68 g, 920 mAh, Pogo Pin, no frontlight, no touch, 16 GB microSD bundled; plus box contents, the "X4 V2" FAQ prose, Shake-to-Flip and the built-in magnetic ring | `body_html` is **empty** — this data exists only in the rendered page. Vendor prose elsewhere on this store is demonstrably unreliable; the spec **table** is treated as a vendor claim, not as measurement | `scratch/xteink/vendor-2026-09-07/x4-classic-product-page.html` |
-| **XC11** | FCC ID `2BTR9-X4C` record | US FCC, via fccid.io | **primary (regulatory)** | regulatory record | <https://fccid.io/2BTR9-X4C> | 2026-09-11 | granted **2026-07-20** | Legal applicant, address, FRN, `xteink.cn`, test lab, 2412–2462 MHz DTS, the full exhibit list and the **2027-01-16** confidentiality expiry | `fccid.io` is a mirror of the FCC EAS; `apps.fcc.gov` returned 403 so the primary host was not reached directly. **Requires UA `WhatsApp/2.23.20.0`** | `scratch/xteink/fcc/fccid-io-2BTR9-X4C.html` |
-| **XC12** | FCC grantee index `2BTR9` | US FCC, via fccid.io | **primary (regulatory)** | regulatory record | <https://fccid.io/2BTR9> | 2026-09-11 | grantee registered 2025-12-21 | **Five Xteink FCC IDs**, including the previously undocumented **`2BTR9-X4L` "XTEINK X4 Light"** | same | `scratch/xteink/fcc/fccid-io-2BTR9-grantee.html` |
-| **XC13** | X4C Antenna Report | Shenzhen Jinhangbiao Electronics, filed by the applicant | **primary** | test report | <https://fccid.io/2BTR9-X4C/Test-Report/Antenna-Report-9480914.pdf> | 2026-09-11 | 2026-07-20 | Antenna **`KH3216-A35`**, peak gain 2.30 dBi, VSWR ≤2.0, 50 Ω, efficiency 69–71.2 % | Manufacturer's own spec sheet, not an independent measurement of the fitted part | `artifacts/certification/2BTR9-X4C-antenna-report.pdf` |
-| **XC14** | X4C RF Exposure Report | applicant / BKC Testing | **primary** | test report | <https://fccid.io/2BTR9-X4C/RF-Exposure-Info/RF-Exposure-Report-9480918.pdf> | 2026-09-11 | 2026-07-20 | **BLE conducted peak −0.87 dBm** — independent evidence BLE is fitted | — | `artifacts/certification/2BTR9-X4C-rf-exposure.pdf` |
-| **XC15** | Short & Long Term Confidentiality Request | applicant | **primary** | cover letter | <https://fccid.io/2BTR9-X4C/Letter/Short-Long-Term-Confidentiality-Request-9480932.pdf> | 2026-09-11 | 2026-07-20 | Why the internal photos are embargoed and to when | — | `artifacts/certification/2BTR9-X4C-confidentiality-request.pdf` |
-| **XC16** | `BoardConfig.h` at SDK HEAD | Free-Ink | community | source (commit-pinned) | <https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/libs/hardware/BoardConfig/include/BoardConfig.h> | 2026-09-11 | commit 2026-09-10 | **No new Xteink board** in `enum class Board`; `displaySpiHz` now a shared 10 MHz | Same single reverse-engineering lineage as XC01 | `scratch/xteink/sdk-2026-09-11/BoardConfig-9f4d3f9.h` |
-| **XC17** | `docs/xteink-x4c-support.md` at HEAD | Free-Ink | community | source | <https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/docs/xteink-x4c-support.md> | 2026-09-11 | commit 2026-09-10 | One-line change vs `2400379`: the 20→10 MHz statement | — | `scratch/xteink/sdk-2026-09-11/xteink-x4c-support.md` |
-| **XC18** | `xteink_x4_classic.h` | clackups (Draftling) | community | source (commit-pinned) | <https://github.com/clackups/draftling/blob/92ba7e514f66bbe42a7fea6d38eff45eed82617b/firmware/main/boards/xteink_x4_classic.h> | 2026-09-11 | HEAD pushed 2026-09-11 | An **independent reading** of the profile: the X4C/"X4 v2" equivalence, DC/RST/BUSY vs the Pro, the UC8279 PLL omission, the dual-OTA rationale | **Derived from FreeInk and explicitly untested on X4C hardware.** Not an independent custodian | `scratch/xteink/github-2026-09-11/draftling/xteink_x4_classic.h` |
-| **XC19** | `HARDWARE.md` | clackups (Draftling) | community | repository doc | <https://github.com/clackups/draftling/blob/92ba7e514f66bbe42a7fea6d38eff45eed82617b/HARDWARE.md> | 2026-09-11 | 2026-09-11 | Same, in prose; and the **X4 Pro** on-hardware findings | Same limitation for the X4C | `scratch/xteink/github-2026-09-11/draftling/HARDWARE.md` |
-| **XC20** | `docs/device/partitions.md` | kycube (x4pro-emu) | community | **teardown-equivalent (flash dump)** | <https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/partitions.md> | 2026-09-11 | dump 2026-09-06 | A **physical X4 Pro's** stock firmware contains `ESP32S3_X4_CLA` **and** `ESP32S3_X4R2_CLA` — the board tags are a shared-codebase enum, not a per-unit stamp | It is an **X4 Pro**, not an X4C. Applied here only to the `R2` question | `scratch/xteink/github-2026-09-11/x4pro-emu/` |
-| **XC21** | Vendor announcement | u/xteink | **primary (vendor)** | forum post | <https://old.reddit.com/r/xteinkereader/comments/1w63yyl/> | 2026-09-11 | posted **2026-09-03** | *"**X4 Classic (X4 V2) is coming soon**"* — the vendor stating both names as one product | 806 pts. Vendor's own account | `scratch/xteink/reddit-2026-09-11/threads/1w63yyl.json` |
-| **XC22** | FCC-filing discovery post | u/M-W-I et al. | community | forum post | <https://old.reddit.com/r/XTEINK/comments/1v4824q/> | 2026-09-11 | posted **2026-07-23** | The community published `2BTR9-X4C` six weeks before launch and correctly predicted buttons-only, no touch, pogo retained | Speculation clearly labelled as such by its own author | `scratch/xteink/reddit-2026-09-11/threads/1v4824q.json` |
-| **XC23** | Pre-release review | u/Which_Heart_983 | community | review | <https://old.reddit.com/r/XTEINK/comments/1w7wjw2/> | 2026-09-11 | posted 2026-09-05 | Firsthand: thinner than an X3, X4-Pro button placement, **"Has a clock"** (BM8563), **"Shake to turn page"** (QMI8658) | **Vendor-supplied unit**, stated by the author. Subjective throughout | `…/threads/1w7wjw2.json` |
-| **XC24** | Comparative review, owns X4C+X4+X4 Pro | u/ajcabrera | community | review | <https://old.reddit.com/r/xteinkereader/comments/1wbxvvg/> | 2026-09-11 | posted 2026-09-09 | *"Both use the same 219 PPI screen"*; lighter, narrower, longer battery; *"if you already have an X4 or X3, save your coins"* | **"Experts Program"** unit, stated by the author | `…/threads/1wbxvvg.json` |
-| **XC25** | PCB-photograph request | community | community | forum post | <https://old.reddit.com/r/xteinkereader/comments/1wcgqub/> | 2026-09-11 | posted 2026-09-10 | **No X4 Classic PCB photograph existed anywhere** on that date; the open question is BM8563 `CLKOUT` → ESP32-S3 GPIO15 | A negative result | `…/threads/1wcgqub.json` |
-| **XC26** | Vendor-hosted customer review | "anne vla", via Judge.me | community | store review | <https://xteink.com/products/xteink-x4-classic-pocket-ereader> | 2026-09-11 | — | Firsthand X4-vs-X4C: better button placement, thinner, lighter; *"I would still prefer USB-C"*; calls the X4 **"the V1"** | **Vendor-hosted; curation cannot be excluded** | `scratch/xteink/vendor-2026-09-07/x4-classic-product-page.html` |
diff --git a/devices/xteink/x4-light/README.md b/devices/xteink/x4-light/README.md
deleted file mode 100644
index 4d061c1..0000000
--- a/devices/xteink/x4-light/README.md
+++ /dev/null
@@ -1,192 +0,0 @@
-# Xteink X4 Light — FCC ID `2BTR9-X4L`
-
-> **This device has not been announced, listed, priced or reviewed.** It exists
-> as a **granted United States equipment authorization**, dated **2026-08-13**,
-> and as three public exhibits including photographs. Research retrieval date
-> **2026-09-11**.
->
-> **Depth: certification-only.** There is no board profile, no firmware support,
-> no teardown, no price and no vendor statement. Everything below is either read
-> off the FCC record or explicitly labelled as absent.
-
-## Why this record exists
-
-The 2026-09-04 family sweep recorded, under *"Models that do not exist"*, that
-`X4 Plus / Air / Pro Max` had **"No evidence… not present in the vendor
-catalogue, the vendor's collection handles, the FreeInk board enum, or 1,798
-Reddit posts."** That was correct for those three names and remains correct.
-
-It was not correct that the family was closed. Enumerating the vendor's **FCC
-grantee code** — which the earlier sweep could not do, because no FCC ID had been
-read off any board and the grantee was unknown — returns **five** Xteink devices,
-and one of them is a product nobody has written about:
-
-| FCC ID | Granted | Device description | Documented in this repository |
-|---|---|---|---|
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 | [`../x3/`](../x3/README.md) |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 | [`../x4/`](../x4/README.md) |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro | [`../x4-pro/`](../x4-pro/README.md) |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic | [`../x4-classic/`](../x4-classic/README.md) |
-| **`2BTR9-X4L`** | **2026-08-13** | **XTEINK X4 Light** | **this record** |
-
-**The lesson is procedural and worth carrying forward: enumerate the grantee
-code, not the product name.** A vendor's FCC grantee index lists every device it
-has certified for the US, including ones it has never mentioned.
-
-## Identity
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | **XTEINK X4 Light** | **[REG]** FCC device description and the test report's `EUT Name` |
-| FCC ID | **`2BTR9-X4L`** | **[REG]** |
-| Grantee / product code | `2BTR9` / `X4L` | **[REG]** |
-| Model No. (test report) | `XTEINK X4 Light` | **[REG]** |
-| **Hardware Version** | **V1.0** | **[REG]** test report §1.1 |
-| **Software Version** | **V1.0** | **[REG]** test report §1.1 |
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** | **[REG]** |
-| Application / final action | **2026-08-13** | **[REG]** |
-| Test lab / report no. | Shenzhen BKC Testing Co., Ltd. · `BKC26074010GE-2` | **[REG]** |
-| Equipment class | DTS — Digital Transmission System | **[REG]** |
-| Model differences | **`N/A`** — a single model, no variants declared | **[REG]** |
-
-## What "Light" means is **not established**
-
-The filing does not say. Two readings are equally consistent with the evidence:
-
-1. **Frontlight.** This is what the community has asked for continuously since
-   April 2026 and did not get in the X4 Classic. Four of the five top replies to
-   the vendor's own 2026-09-03 announcement were requests for a lit,
-   buttons-only reader. A community post on 2026-08-15 —
-   [r/XTEINK `1vp4mmh`](https://old.reddit.com/r/XTEINK/comments/1vp4mmh/),
-   *"It appears that the X4 with a front light is in development"* — **predates
-   the 2026-08-13 grant by two days**, which is suggestive and nothing more.
-2. **Lightweight.** The X4 Classic is already 68 g and 4.9 mm.
-
-**This record takes no position.** A frontlight would appear in the internal
-photographs and possibly in the user manual — both embargoed until
-**2027-02-09**. Do not repeat "the X4 Light has a frontlight" as though it were
-established; it is a hypothesis with a plausible motive and no evidence.
-
-## What the filing does establish
-
-| Field | Value | Source |
-|---|---|---|
-| **Radio** | 2.4 GHz only, **2412–2462 MHz**, channels 1–11 | test report §1.2 |
-| Modes | 802.11b (DSSS), 802.11g / n HT20 / n HT40 (OFDM) | test report §1.5 |
-| **Max conducted RF output** | **8.13 dBm** | test report §1.1 |
-| **Antenna** | **Internal, maximum gain 5.19 dBi** | test report §1.1 |
-| Power supply | **`Input: DC 5V from adapter`**, **`Adapter: N/A`** — it ships without a PSU | test report §1.1 |
-| Compliance parts tested | 15.203, 15.247(a)(2)(b)(3)(b)(4)(d)(e), 15.205, 15.207, 15.209 — **all PASS** | test report §1.3 |
-| Intended environment | residential, commercial, light industrial | test report §1.1 |
-
-**No Bluetooth exhibit was filed under this ID.** The X4 Classic's RF-exposure
-report contains BLE conducted-power figures; the X4 Light's does not appear to.
-That is **not** evidence that BLE is absent — a separate DSS/BLE filing or a
-module-based approval could cover it — but it is a difference between the two
-records and it is recorded as such.
-
-### The antenna is not the X4 Classic's
-
-| | X4 Classic (`2BTR9-X4C`) | **X4 Light (`2BTR9-X4L`)** |
-|---|---|---|
-| Antenna part | **`KH3216-A35`** (Shenzhen Jinhangbiao) | **not named in the public exhibits** |
-| Max gain | **2.30 dBi** | **5.19 dBi** |
-
-A 5.19 dBi maximum gain against 2.30 dBi is a **different antenna**, not a
-different measurement of the same one. Something about the RF layout or the
-enclosure changed. What, is unknown.
-
-## What it looks like
-
-The X4 Light's **External Photos exhibit is public** — unlike the X4 Classic's,
-which is embargoed. It is retained at
-[`artifacts/certification/2BTR9-X4L-external-photos.pdf`](artifacts/certification/2BTR9-X4L-external-photos.pdf)
-(3,485,136 B, SHA-256 `c6457651f19b4cac…`, **9 embedded images**), photographed
-against a millimetre rule.
-
-Read directly off those photographs:
-
-| Observation | Confidence |
-|---|---|
-| Portrait slab, rounded corners, **≈114 × 69 mm** scaled off the rule | **read from image**, ±2 mm |
-| Two body colours photographed: **black** and **white/silver** | read from image |
-| `XTEINK` wordmark on the rear, upper third | read from image |
-| **An oval magnet outline** centred on the rear — the same feature the X4 Classic's FAQ calls a "built-in magnetic ring" | read from image |
-| **Four gold pogo contacts on the bottom edge.** No USB socket visible on any face | read from image |
-| **Two button protrusions on the left edge, one on the right** | read from image |
-
-**This is the X4 Classic's enclosure generation.** Same proportions, same magnet,
-same four-pin pogo pad, same side-button arrangement. **It is not proof that the
-internals match**, and this record does not claim it.
-
-**Nothing in the external photographs shows a lit screen or a frontlight
-diffuser**, which is the one thing that would settle the naming question. The
-device is photographed powered off.
-
-## Embargo schedule
-
-| Exhibit | Size | **Public from** |
-|---|---|---|
-| External Photos | 3.3 MB | **already public — retained here** |
-| Label and Information | 1.2 MB | already public — retained here |
-| Antenna Report | 1.5 MB | already public |
-| Test Report | 5.7 MB | already public — retained here (1.5 MB variant fetched) |
-| RF Exposure Report | 143 KB | already public |
-| **Internal Photos** | 842.4 KB | **2027-02-09** |
-| Users Manual | 3.9 MB | **2027-02-09** — *the manual will name the features* |
-| Test Setup Photos | 373.7 KB | 2027-02-09 |
-| Block Diagram · Schematics · Operational Description | 53.6 KB / 573.2 KB / 89 KB | **never** |
-
-**Re-check on 2027-02-09.** The user manual is the cheapest route to knowing what
-"Light" means.
-
-## What is completely unknown
-
-- **SoC.** No board profile exists in any firmware project. Not in the FreeInk
-  `enum class Board` at HEAD (`9f4d3f9`, 2026-09-10), not in CrossPoint, not in
-  Draftling, not in any GitHub code-search result. **A new Xteink board normally
-  reaches the SDK before it reaches the shop — this one has reached neither.**
-- **Panel size, resolution, controller.**
-- **Whether it has a frontlight, a touchscreen, an IMU, an RTC, a fuel gauge.**
-- **Price, launch date, market, colours offered for sale.**
-- **Whether it will ship at all.** A granted FCC authorization is a strong signal
-  of intent — it costs real money and is usually filed weeks before launch, which
-  is exactly the pattern the X4 Classic followed (granted 2026-07-20, listed
-  2026-09-06, a 48-day gap). By that precedent an X4 Light would list around
-  **2026-09-30**. **That is an extrapolation from one data point and should be
-  treated as such.**
-
-## Community awareness
-
-Near zero. Across 94 catalogued X4C-related Reddit posts and 332 unique posts
-from a broad launch-week sweep, **no post names "X4 Light"**. Two posts are
-consistent with somebody having seen something:
-
-- [r/XTEINK `1vp4mmh`](https://old.reddit.com/r/XTEINK/comments/1vp4mmh/),
-  2026-08-15 — *"It appears that the X4 with a front light is in development"*
-- [r/XTEINK `1w1tcx9`](https://old.reddit.com/r/XTEINK/comments/1w1tcx9/),
-  2026-08-29, 80 pts — *"Well well look what we have here"*
-
-Neither was fetched in full this pass, and neither is claimed here as evidence
-about the X4L. **The FCC grantee index is, as far as this research can tell, the
-only public place the name "XTEINK X4 Light" appears.**
-
-## Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Published | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| XL01 | FCC ID `2BTR9-X4L` record | US FCC via fccid.io | **primary (regulatory)** | regulatory record | <https://fccid.io/2BTR9-X4L> | 2026-09-11 | 2026-08-13 | Existence, name, applicant, exhibit list, embargo dates |
-| XL02 | FCC grantee index `2BTR9` | US FCC via fccid.io | primary (regulatory) | regulatory record | <https://fccid.io/2BTR9> | 2026-09-11 | — | The complete five-device Xteink certification history |
-| XL03 | Test Report `BKC26074010GE-2` | BKC Testing, filed by applicant | primary | test report | <https://fccid.io/2BTR9-X4L/Test-Report/Test-Report-9556502.pdf> | 2026-09-11 | 2026-08-13 | EUT name, HW/SW V1.0, 8.13 dBm, 5.19 dBi, DC 5 V, channel list, PASS summary |
-| XL04 | External Photos | applicant | primary | photographs | <https://fccid.io/2BTR9-X4L/External-Photos/External-Photos-9556497.pdf> | 2026-09-11 | 2026-08-13 | Form factor, two colours, pogo pad, magnet outline, button layout |
-| XL05 | Label and Information | applicant | primary | photographs | <https://fccid.io/2BTR9-X4L/Label/Label-and-Information-9556498.pdf> | 2026-09-11 | 2026-08-13 | Compliance-label artwork and placement |
-
-Retrieval required UA `WhatsApp/2.23.20.0`; `fccid.io` serves **403** to a
-desktop-Chrome UA and `fcc.report` serves 403 to every UA tried. See
-[`../x4-classic/commands.md`](../x4-classic/commands.md) §3.
-
-## See also
-
-[Family index](../README.md) · [X4 Classic](../x4-classic/README.md) — the
-enclosure generation this belongs to · [X4 Pro](../x4-pro/README.md) — the only
-Xteink with a frontlight today
diff --git a/devices/xteink/x4-light/acquisition/manifest.json b/devices/xteink/x4-light/acquisition/manifest.json
deleted file mode 100644
index c9fa64c..0000000
--- a/devices/xteink/x4-light/acquisition/manifest.json
+++ /dev/null
@@ -1,116 +0,0 @@
-{
- "record": "devices/xteink/x4-light",
- "generated": "2026-09-11",
- "note": "FCC equipment-authorization exhibits filed by the round-2 index merge, 2026-09-11. Exhibits whose `disposition` is `archive` are NOT in the repository; a self-sufficient placeholder sits at `destination` + `.ARCHIVED.md`.",
- "artifacts": [
-  {
-   "id": "fcc-2BTR9-X4L-9556499",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2BTR9-X4L/Test-Report/Antenna-Report-9556499.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9556499",
-    "https://fcc.report/FCC-ID/2BTR9-X4L/9556499.pdf",
-    "https://fccid.io/2BTR9-X4L",
-    "https://web.archive.org/web/2/https://fccid.io/2BTR9-X4L/Test-Report/Antenna-Report-9556499.pdf"
-   ],
-   "sha256": "9de0e036e525f5e6ca232f2e41ee07ffda5192fbe6e75d4bf9840e65ae19de04",
-   "bytes": 1563068,
-   "destination": "devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-08-13",
-   "fcc_id": "2BTR9-X4L",
-   "fcc_document_id": "9556499",
-   "exhibit_type": "Test Report",
-   "exhibit_title_as_filed": "Antenna Report",
-   "grant_date": "2026-08-13",
-   "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen BKC Testing Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf",
-   "placeholder": "devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/xteink/x4-light",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2BTR9-X4L-9556497",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2BTR9-X4L/External-Photos/External-Photos-9556497.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9556497",
-    "https://fcc.report/FCC-ID/2BTR9-X4L/9556497.pdf",
-    "https://fccid.io/2BTR9-X4L",
-    "https://web.archive.org/web/2/https://fccid.io/2BTR9-X4L/External-Photos/External-Photos-9556497.pdf"
-   ],
-   "sha256": "c6457651f19b4cacf48618ee15abcc50839ffa36d1b13fb98a87bfe0d38106d6",
-   "bytes": 3485136,
-   "destination": "devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-08-13",
-   "fcc_id": "2BTR9-X4L",
-   "fcc_document_id": "9556497",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2026-08-13",
-   "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen BKC Testing Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/xteink/x4-light",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2BTR9-X4L-9556503",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2BTR9-X4L/RF-Exposure-Info/RF-Exposure-Report-9556503.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9556503",
-    "https://fcc.report/FCC-ID/2BTR9-X4L/9556503.pdf",
-    "https://fccid.io/2BTR9-X4L",
-    "https://web.archive.org/web/2/https://fccid.io/2BTR9-X4L/RF-Exposure-Info/RF-Exposure-Report-9556503.pdf"
-   ],
-   "sha256": "b9cb6b076a72956e1d0b037e16208dd0f81f26da193a77e55b5d5369ff74d75b",
-   "bytes": 146446,
-   "destination": "devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-08-13",
-   "fcc_id": "2BTR9-X4L",
-   "fcc_document_id": "9556503",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Report",
-   "grant_date": "2026-08-13",
-   "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen BKC Testing Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf",
-   "placeholder": "devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/xteink/x4-light",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ],
- "wanted": []
-}
diff --git a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf.ARCHIVED.md b/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf.ARCHIVED.md
deleted file mode 100644
index 5570742..0000000
--- a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-X4L-antenna-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 1,563,068 B (1.49 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,563,068 B (1.49 MiB) |
-| SHA-256 | `9de0e036e525f5e6ca232f2e41ee07ffda5192fbe6e75d4bf9840e65ae19de04` |
-| FCC ID | **`2BTR9-X4L`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | Antenna Report |
-| FCC document id | 9556499 |
-| Upstream publication date | 2026-08-13 |
-| Grant date | 2026-08-13 |
-| Equipment class | XTEINK X4 Light, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-X4L/Test-Report/Antenna-Report-9556499.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9556499>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-X4L/9556499.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-X4L>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-X4L/Test-Report/Antenna-Report-9556499.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf" \
-   "devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-antenna-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-X4L/Test-Report/Antenna-Report-9556499.pdf" -o "2BTR9-X4L-antenna-report.pdf"
-echo "9de0e036e525f5e6ca232f2e41ee07ffda5192fbe6e75d4bf9840e65ae19de04  2BTR9-X4L-antenna-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-external-photos.pdf b/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-external-photos.pdf
deleted file mode 100644
index 53303ce..0000000
Binary files a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-external-photos.pdf and /dev/null differ
diff --git a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-label.pdf b/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-label.pdf
deleted file mode 100644
index 3eb12b0..0000000
Binary files a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-label.pdf and /dev/null differ
diff --git a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf.ARCHIVED.md b/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf.ARCHIVED.md
deleted file mode 100644
index a4e1e81..0000000
--- a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-X4L-rf-exposure-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 146,446 B (0.14 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 146,446 B (0.14 MiB) |
-| SHA-256 | `b9cb6b076a72956e1d0b037e16208dd0f81f26da193a77e55b5d5369ff74d75b` |
-| FCC ID | **`2BTR9-X4L`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Report |
-| FCC document id | 9556503 |
-| Upstream publication date | 2026-08-13 |
-| Grant date | 2026-08-13 |
-| Equipment class | XTEINK X4 Light, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-X4L/RF-Exposure-Info/RF-Exposure-Report-9556503.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9556503>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-X4L/9556503.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-X4L>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-X4L/RF-Exposure-Info/RF-Exposure-Report-9556503.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf" \
-   "devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-X4L/RF-Exposure-Info/RF-Exposure-Report-9556503.pdf" -o "2BTR9-X4L-rf-exposure-report.pdf"
-echo "b9cb6b076a72956e1d0b037e16208dd0f81f26da193a77e55b5d5369ff74d75b  2BTR9-X4L-rf-exposure-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-test-report.pdf b/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-test-report.pdf
deleted file mode 100644
index 81cadd7..0000000
Binary files a/devices/xteink/x4-light/artifacts/certification/2BTR9-X4L-test-report.pdf and /dev/null differ
diff --git a/devices/xteink/x4-light/artifacts/certification/README.md b/devices/xteink/x4-light/artifacts/certification/README.md
deleted file mode 100644
index 875600c..0000000
--- a/devices/xteink/x4-light/artifacts/certification/README.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# FCC equipment-authorization exhibits — `2BTR9-X4L` (XTEINK X4 Light)
-
-Retrieved **2026-09-11** from `fccid.io` with UA `WhatsApp/2.23.20.0`. All files
-validated by magic bytes (`%PDF`); text extracted with poppler 26.06.0 and
-cross-checked against headings visible in the rendered pages.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-X4L`** |
-| Device description | **XTEINK X4 Light** |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. |
-| Granted | **2026-08-13** |
-| Frequency range | 2412–2462 MHz, DTS |
-| Test report | `BKC26074010GE-2`, Shenzhen BKC Testing Co., Ltd. |
-| Source page | <https://fccid.io/2BTR9-X4L> |
-
-## Retained
-
-| File | Bytes | SHA-256 | Establishes |
-|---|---:|---|---|
-| `2BTR9-X4L-external-photos.pdf` | 3,485,136 | `c6457651f19b4cacf48618ee15abcc50839ffa36d1b13fb98a87bfe0d38106d6` | **The only photographs of this device.** 9 embedded images, black and white units, against a millimetre rule. Rear magnet outline, four-pin pogo pad, side buttons, **no USB socket** |
-| `2BTR9-X4L-label.pdf` | 1,262,117 | `c5be3415bb656997f05b09219829dabeaec0665f27882f3f135cdab3943e82cb` | Compliance-label artwork and placement; one 3451×2588 image at 600 ppi |
-| `2BTR9-X4L-test-report.pdf` | 1,547,812 | `cbe8fc7409534f4913c3dfc3e5d1cf5c4238382b015eb814f97be3588ece98cd` | **EUT description**: name, Hardware V1.0, Software V1.0, 8.13 dBm max conducted, internal antenna 5.19 dBi max gain, `Input: DC 5V from adapter`, `Adapter: N/A`, channel list 1–11, PASS summary |
-
-URLs:
-
-- `https://fccid.io/2BTR9-X4L/External-Photos/External-Photos-9556497.pdf`
-- `https://fccid.io/2BTR9-X4L/Label/Label-and-Information-9556498.pdf`
-- `https://fccid.io/2BTR9-X4L/Test-Report/Test-Report-9556502.pdf`
-
-**Note on the test-report size.** The FCC ID page reports this exhibit as
-**5.7 MB**; the file served at the URL above is **1,547,812 B** and is a complete,
-36-page report ending in its Appendix. The discrepancy is unexplained — possibly
-a different revision, possibly a mirror-side re-compression. **Recorded rather
-than resolved**; re-fetch and compare if it matters.
-
-## Not retained
-
-| Exhibit | Size | Why |
-|---|---|---|
-| Antenna Report | 1.5 MB | public; not fetched. **It would name the antenna part**, which is the most valuable unfetched document in this record |
-| RF Exposure Report | 143 KB | public; not fetched |
-| Attestations ×2, Agent Authorization, Confidentiality Request | 96–180 KB | boilerplate |
-| **Internal Photos** | 842.4 KB | **embargoed to 2027-02-09** |
-| **Users Manual** | 3.9 MB | **embargoed to 2027-02-09** — will name the features |
-| Test Setup Photos | 373.7 KB | embargoed to 2027-02-09 |
-| Block Diagram · Schematics · Operational Description | 53.6 / 573.2 / 89 KB | **permanently confidential** |
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`unknown`** — third-party submissions published by a US federal agency in a public authorization record; routinely mirrored; no explicit grant located |
-| Disposition | `repository`, **unstaged** |
-| Total retained | **3 files, 6,295,065 bytes** |
-
-Cited from [`../../README.md`](../../README.md) and from
-[`../../../x4-classic/media.md`](../../../x4-classic/media.md), which uses these
-photographs for form-factor questions about the shared enclosure generation.
-
----
-
-## Correction, 2026-09-11 — redistribution is `allowed`, not `unknown`
-
-The *Licensing and disposition* table above records **`unknown`**. That was
-conservative but wrong, and it is superseded:
-
-| Field | Value, as of 2026-09-11 |
-|---|---|
-| Redistribution status | **`allowed`** |
-| Basis | FCC equipment-authorisation exhibits are **US Government public records**, published by the Commission under 47 CFR §2.1033. The agency asserts no copyright, and the exhibits are routinely republished by mirrors. |
-| Scope | Applies to every exhibit in this directory, and to every FCC exhibit elsewhere in this repository. |
-
-**The original rows above are left exactly as written.** This note supersedes
-their redistribution field only; their hashes, sizes and URLs remain correct and
-authoritative.
-
-Confidentiality embargoes are a **separate** matter and are unaffected: exhibits
-the applicant had withheld were never published, so there is nothing to
-redistribute until their release dates.
-
-Logged in [`scratch/index-merge/corrections-requiring-review.md`](../../../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-light/certification-and-compliance.md b/devices/xteink/x4-light/certification-and-compliance.md
deleted file mode 100644
index 0d4e17a..0000000
--- a/devices/xteink/x4-light/certification-and-compliance.md
+++ /dev/null
@@ -1,205 +0,0 @@
-# Certification and compliance — x4-light
-
-Compiled **2026-09-11** by the round-2 index merge, from the certification pass's findings in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md). Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware.
-
-> **Why this arrived late.** These findings were produced on 2026-09-11 but written into `scratch/` because a sibling agent held `devices/xteink/` at the time. That conflict is over; this file is the properly-filed result.
-
----
-
-## 1. Summary
-
-**FCC: granted.** `2BTR9-X4L`, 2026-08-13.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2BTR9-X4L` — granted **2026-08-13** |
-| **CE / RED (EU)** | ⚠ no published DoC located; no database exists to search (§4) |
-| **UKCA** | ⚠ not determined (§4) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§4) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§4) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§4) |
-
-⚠ **This reverses the 2026-09-04 finding of *no FCC/CE filings*.** See §5.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Every
-probe below ran on **2026-09-11**, in one session, against one host, with one tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** — a real Xteink grant |
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** — M5Stack Cardputer |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**Positives → 200. Negatives → 404.** Raw run:
-`scratch/market-and-certification/logs/fcc-controls.txt`.
-
-These controls are the whole basis on which the absence findings below may be read as evidence.
-They are reproduced in each of the five Xteink records rather than referenced once, because a
-reader arriving at one device record must be able to judge that record's evidence without
-chasing a link.
-
-Beyond the ID probes, **the grantee was enumerated in full rather than guessed**: `2BTR9`
-yields **five** FCC IDs and no more. A product absent from a complete grantee listing is
-*absent*, not merely *un-found* — which is exactly the distinction the 2026-09-04 sweep could
-not make, because it had no grantee code to enumerate.
-
-⚠ **A counter-trap worth recording.** `https://fccid.io/2BTR9` prints **"6 FCC IDs"** in its
-page header, but the applications table lists **five**, and exactly five `href="/2BTR9…"` links
-exist in the HTML. The headline counter and the table disagree. **Trust the table.**
-
----
-
-## 3. The whole grantee — `2BTR9`
-
-| Field | Value |
-|---|---|
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** |
-| Grantee code | **`2BTR9`** |
-| Registered | **2025-12-21** |
-| Contact | Chen Chu |
-| Address | Room 1209, Yichuang International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community, Guanlan Street, Longhua District, Shenzhen, China |
-| FCC IDs | **5** |
-
-| FCC ID | Granted | Device | Purpose | Record |
-|---|---|---|---|---|
-| `2BTR9-X4L` | **2026-08-13** | XTEINK X4 Light | Original Equipment | [`x4-light`](../x4-light/README.md) |
-| `2BTR9-X4C` | **2026-07-20** | XTEINK X4 Classic | Original Equipment | [`x4-classic`](../x4-classic/README.md) |
-| `2BTR9-X4PRO` | **2026-06-16** | XTEINK X4 Pro | Original Equipment | [`x4-pro`](../x4-pro/README.md) |
-| `2BTR9-XTEINKX4` | **2026-01-05** | XTEINK X4 | Original Equipment | [`x4`](../x4/README.md) |
-| `2BTR9-XTEINKX3` | **2025-12-26** | XTEINK X3 | Original Equipment | [`x3`](../x3/README.md) |
-
-All five: 2402–2480 MHz (BLE) and 2412–2462 MHz (Wi-Fi, US channels 1–11). Long-term
-confidentiality granted on all five for Schematics, Block Diagram and Operational Description.
-
-**Not granted:** no FCC ID under `2BTR9` corresponds to the [**Xteink S4**](../s4/README.md) or
-the [**Xteink Nano**](../nano/README.md). Against a complete enumeration with passing controls,
-those two devices are **not FCC-authorised as of 2026-09-11**.
-
-Xteink filed **Original Equipment** authorisations, not module-based ones. The internal
-photographs show why: the X4 main PCB carries a **bare QFN SoC with a PCB meander antenna etched
-into the board**, not a drop-in pre-certified Espressif module. A design like that cannot
-inherit a module grant, so the vendor had to certify the whole device. That is consistent with,
-and corroborates, the grant record.
-
-
-### The `2BTR9-X4L` filing
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-X4L`** |
-| Device description | XTEINK X4 Light |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Granted | **2026-08-13** |
-| Frequency ranges | 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Short-term confidentiality | Yes |
-| Exhibit rows | 12 |
-| Filing page | <https://fccid.io/2BTR9-X4L> — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld:**
-
-- User Manual [Users Manual 2027-02-09]
-- Internal Photos [Internal Photos 2027-02-09]
-- Test Setup Photos [Test Setup Photos 2027-02-09]
-- BLOCK [Block Diagram]
-- SCH [Schematics]
-- Operational Description [Operational Description]
-
-Internal photographs are **withheld until 2027-02-09**. External photographs are public.
-
-**Exhibits obtained** — US Government public records, redistribution **`allowed`**. Downloaded 2026-09-11, magic bytes validated (`%PDF`).
-
-Retained in this record, at [`artifacts/certification/`](artifacts/certification/README.md):
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| [`2BTR9-X4L-external-photos.pdf`](artifacts/certification/2BTR9-X4L-external-photos.pdf) | 3,485,136 | `c6457651f19b4cacf48618ee15abcc50…` | External Photos |
-
-Archived out of the repository, each with a self-sufficient placeholder beside it carrying hash, size, FCC document id and five reacquisition URLs:
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2BTR9-X4L-antenna-report.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-X4L-antenna-report.pdf.ARCHIVED.md) | 1,563,068 | Test Report |
-| [`2BTR9-X4L-rf-exposure-report.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-X4L-rf-exposure-report.pdf.ARCHIVED.md) | 146,446 | RF Exposure Info |
-
----
-
-## 4. Other jurisdictions
-
-| Regime | Result |
-|---|---|
-| **FCC (US)** | ✅ **granted** — see §1 |
-| **CE / RED (EU)** | ⚠ No published DoC located; no `xteink.com` certification page exists. CE is self-declared; **there is no database to search** |
-| **CE mark on product** | ⚠ **Not determined** — the `ID Label` exhibits were downloaded but not visually inspected for secondary marks. **Open work** |
-| **UKCA** | ⚠ Not determined; no database exists |
-| **SRRC / CCC (CN)** | ❌ **Not searched** — `wireless.miit.gov.cn` and `srrccn.org` both failed to connect. **Not an absence finding** |
-| **MIC 技適 (JP)** | ⚠ **Not searched** — endpoint reachable, not queried |
-| **ISED (CA)** | ⚠ **Not searched** — `sms-sgs.ic.gc.ca` returned 503 |
-
----
-
-## 5. ⚠ Correction — this supersedes the 2026-09-04 finding
-
-[`VERIFICATION-sweep-2026-09-04.md`](../../../VERIFICATION-sweep-2026-09-04.md) §6 recorded:
-
-> **Certification and regulatory records** were checked only for Xteink (where the finding was
-> that no external CE/FCC marking exists on the devices at all). No positive control was run, so
-> the absence is weaker evidence than it looks.
-
-That self-doubt was justified. The original finding confused **"no mark visible in a product
-photograph"** with **"no grant exists"**. They are different claims and only the first was ever
-tested.
-
-- ✅ **Survives:** "no FCC ID is printed on the exterior of the units we photographed." Not
-  re-tested here, and may well still be true.
-- ❌ **Refuted:** any reading that Xteink devices are uncertified or unauthorised for the US.
-  **Xteink holds five granted Original Equipment authorisations.**
-
-47 CFR §2.935 permits an **e-label** displayed in software instead of a printed mark, which is
-the ordinary arrangement for a device with a screen. **That is a likely explanation and it was
-not verified.**
-
-The original sentences in the sweep report and in the Xteink records have **not been edited**.
-Dated corrections sit beneath them, and every one is listed in
-[`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
----
-
-## 6. What this does **not** establish
-
-- **No hardware was inspected.** No Xteink unit was obtained, opened or powered.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit.
-- **CE is not established.** No published Declaration of Conformity was located and **there is
-  no CE database to search** — CE is a self-declaration regime. Absence of a published DoC is
-  not absence of conformity.
-- **The `ID Label` exhibits were downloaded but not visually inspected for secondary marks.**
-  Whether a CE mark appears on Xteink label artwork is **open work**, and cheap to close.
-- **SRRC / CCC (CN) did not run.** `wireless.miit.gov.cn` and `srrccn.org` both failed to
-  connect (`000`) on 2026-09-11. That is a method failure, **not** an absence finding.
-- **MIC 技適 (JP) did not run.** The endpoint is reachable (200) but form-driven; not queried.
-- **ISED (CA) did not run.** `sms-sgs.ic.gc.ca` returned 503.
-- **Schematics are permanently withheld** on all five filings, along with block diagrams and
-  operational descriptions. **The FCC is not a route to an Xteink schematic.**
-
-
-## 7. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| XC-1 | FCC ID `2BTR9-X4L` record | US FCC via fccid.io | **primary (regulatory)**, via mirror | regulatory record | <https://fccid.io/2BTR9-X4L> | 2026-09-11 | Grant existence, date, frequencies, exhibit list, embargo dates |
-| XC-2 | FCC grantee index `2BTR9` | US FCC via fccid.io | primary via mirror | regulatory record | <https://fccid.io/2BTR9> | 2026-09-11 | The complete five-device Xteink certification history |
-| XC-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
-⚠ Deep `fccid.io` paths serve **403 to a Chrome User-Agent** and **200 to `curl/8.5.0`** — an *inverted* block. The honest UA works; the disguised one does not. The **root** `https://fccid.io/` returns 200 to everything, so a reachability probe against the root reports a false success. **Probe a deep path.**
diff --git a/devices/xteink/x4-light/market-and-pricing.md b/devices/xteink/x4-light/market-and-pricing.md
deleted file mode 100644
index 6ae7447..0000000
--- a/devices/xteink/x4-light/market-and-pricing.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Xteink X4 Light — market and pricing
-
-*Created 2026-09-11 by the round-2 index merge.*
-
-## There is no pricing, and there is no product page. That is the finding.
-
-The X4 Light is **certified but not sold**. It was found by enumerating Xteink's FCC grantee
-code `2BTR9`, not by any commercial signal, and as of **2026-09-11** it has no storefront
-presence of any kind.
-
-| Channel | Result, 2026-09-11 |
-|---|---|
-| `xteink.com` `/products.json?limit=250&page=1` | **25 products enumerated, complete.** No X4 Light, under any spelling |
-| `xteink.com` `/collections.json` | **No `x4-light` collection** — unlike the X4 Classic, which had a provisioned empty collection weeks before launch |
-| X4 Light–specific accessories | **none** |
-| AliExpress / Amazon / eBay / Taobao / JD | **not obtained** — all bot-walled or JS-shelled from the research host on 2026-09-11. Not an absence finding |
-| Community (Reddit, GitHub) | no mention located |
-
-**Compare the X4 Classic's pre-launch signature.** On 2026-09-04 the X4 Classic already had a
-provisioned `x4-classic` collection containing accessories, five days before it went on sale. The
-X4 Light has **nothing** — not even an empty collection. On that evidence a launch is **not
-imminent**, though the FCC grant says one is intended.
-
-## The only dated commercial fact that exists
-
-**None.** Every row above is an absence.
-
-The one dated *regulatory* fact is in
-[`certification-and-compliance.md`](certification-and-compliance.md): FCC `2BTR9-X4L`, granted
-**2026-08-13**, applicant Shenzhen Xiaohu Xingtong Technology Co., Ltd., test firm Shenzhen BKC
-Testing Co., Ltd.
-
-## Family price context, 2026-09-11
-
-For whenever it does appear, the slots that are already occupied:
-
-| Device | Vendor price, 2026-09-11 | Status |
-|---|---|---|
-| [X3](../x3/market-and-pricing.md) | **USD 69.00** | on sale |
-| [X4 Classic (X4 V2)](../x4-classic/market-and-pricing.md) | **USD 79.00** | on sale, listed 2026-09-06 |
-| [X4 Pro](../x4-pro/market-and-pricing.md) | **USD 99.00** | on sale |
-| [X4](../x4/market-and-pricing.md) | — | **withdrawn** |
-| **X4 Light** | **—** | **certified 2026-08-13, never listed** |
-
-⚠ **Do not infer a price from the name.** "Light" is a marketing word; this repository has no
-evidence about the X4 Light's specification, let alone its cost. The feature set is
-**unknown** — see [`README.md`](README.md). Guessing that it slots below the X4 Classic because
-of its name would be invention.
-
-## What would resolve this
-
-| Question | What would settle it |
-|---|---|
-| Will it ship? | A `/products.json` entry, or an `x4-light` collection appearing |
-| What is it? | **Internal photographs unlock 2027-02-09.** External photographs are already public and held in this record |
-| Price | A storefront listing. Nothing else observed here can supply one |
-
-## Caveats
-
-- **No marketplace channel was sampled.** The absences above are vendor-store absences only.
-- A granted FCC authorisation is a **strong signal of commercial intent** — it costs real money
-  — but it is **not** a commitment to ship. Products are certified and cancelled.
diff --git a/devices/xteink/x4-pro/README.md b/devices/xteink/x4-pro/README.md
deleted file mode 100644
index 7192b6e..0000000
--- a/devices/xteink/x4-pro/README.md
+++ /dev/null
@@ -1,459 +0,0 @@
-# Xteink X4 Pro
-
-> SKU `X4Pro-Black` · Space Black only · **$99.00** observed 2026-09-04 ·
-> published to the vendor store **2026-07-21** · in production and in stock ·
-> research retrieval date **2026-09-04**.
-
-## Identity and variants
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | **Xteink X4 Pro Pocket eReader** | **[VENDOR]** `products.json`, handle `xteink-x4-pro-pocket-ereader` |
-| Vendor SKU | `X4Pro-Black` | **[VENDOR]** variant `48382782669041` |
-| Colour variants | **One only** — Space Black | **[VENDOR]** single variant |
-| Shipping weight | 250 g (packaged; **not** device mass) | **[VENDOR]** `grams: 250` |
-| Product created / published | 2026-07-07 / **2026-07-21** | **[VENDOR]** |
-| Board tag (stock firmware) | `ESP32S3_X4_TL_SSD1677`, app names itself `XTEink X4 Pro` | **[DUMP]** app1 strings |
-| FreeInk profile | `BoardConfig::XTEINK_X4_PRO`, name string `xteink_x4_pro` | **[SDK]** `BoardConfig.h:1495–1497` |
-| Build flag | `-DFREEINK_DEVICE_X4PRO=1` | **[SDK]** `docs/xteink-x4pro-support.md:13` |
-| Lifecycle | Current flagship. Not discontinued | **[VENDOR]** in stock 2026-09-04 |
-
-### Panel-controller variants — the important one
-
-**The X4 Pro ships with at least three different display controllers depending on
-production batch, on identical wiring.**
-
-| Controller | Maker | Status |
-|---|---|---|
-| **SSD1677** | Solomon Systech | Original batches |
-| **UC8179** | UltraChip | Newer batches. *"the variant every unit benched so far has carried"* |
-| **UC8279** | UltraChip | Newer batches, distinguished by `LUT_VER` |
-
-This is **not** a cosmetic revision — the command sets differ, and a firmware that
-assumes the wrong one produces a panel that resets and runs waveforms but never
-develops an image. The SDK resolves it at boot with a bit-banged half-duplex read
-of the UC81xx `VER (0x70)` / `FLG (0x71)` registers, which the SSD-family does not
-answer at all **[SDK]** `XteinkDetect.cpp:113–119, 366–390`.
-
-There is **no external revision marking** that lets you tell them apart before
-powering the unit on. See [`features/display.md`](features/display.md).
-
-## What it is and visual identification
-
-A sealed, pocket-sized 4.26-inch e-ink reader, roughly the footprint of a large
-phone, in a single black finish. Distinguishing features versus the rest of the
-family, all externally visible:
-
-- **A touchscreen** — the only Xteink ESP32 device with one.
-- **A frontlight** with warm/cool colour-temperature control.
-- **No USB-C port for charging.** It charges over a **magnetic pogo-pin connector**
-  and ships needing a proprietary adapter (`x3-magnetic-pogo-pin-charging-cable`,
-  $4.99; `magnetic-charging-adapter-for-x3`, $5.99) **[VENDOR]**. This is the
-  single most-complained-about design decision — see [`community.md`](community.md).
-- **Only two physical navigation buttons** (side keys) plus power; everything else
-  is touch, including a **capacitive "Home" pad below the glass** that is not a
-  GPIO but a GT911 key bit.
-
-Teardown photography specific to the X4 Pro was **not found**. The board-level
-knowledge below comes from firmware reverse engineering plus on-hardware probing
-by the FreeInk maintainers, which for pin-level facts is stronger evidence than a
-photograph — but it means **no PCB image is held**. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-## Product history, family and culture
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2026-06-13 | S4 "June production run" video also shows unannounced hardware | **[COMM]** [r/XTEINK `1u4ty4q`](https://old.reddit.com/r/XTEINK/comments/1u4ty4q/) |
-| 2026-06-22 | Community spots a **new X4 variant** in vendor video — *"Physical buttons + frontlight but no touchscreen"*, 300 points | **[COMM]** [r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/) |
-| 2026-07-07 | X4 Pro product record created in Shopify | **[VENDOR]** |
-| 2026-07-17 | Public discussion thread, 89 comments, poll "X4 Pro or S4?" | **[COMM]** [r/xteinkereader `1uz9mtg`](https://old.reddit.com/r/xteinkereader/comments/1uz9mtg/) |
-| 2026-07-21 | **Launch.** Listed at $99, described as pre-order with restock 6 Aug | **[VENDOR]** product body + published_at |
-| 2026-07-21 | Pogo-pin backlash thread, 71 comments | **[COMM]** [r/xteinkereader `1v2txxe`](https://old.reddit.com/r/xteinkereader/comments/1v2txxe/) |
-| 2026-07-26/28 | Screen protectors listed (matte, then tempered glass) | **[VENDOR]** |
-| 2026-08-27 | Stock firmware **7.4.4** built (ESP-IDF 6.0.1) | **[SDK]** `docs/xteink-x4pro-support.md:84–87` |
-| 2026-09-04 | In stock at $99; matte protectors and 2/3-packs sold out | **[VENDOR]** |
-
-The X4 Pro is the ecosystem's **design floor**: CrossPlay's `LOCAL_SCOPE.md` names
-it as the reference target and defines the minimum viable input as "two side keys
-plus touch" ([CrossPlay record](../../../software/applications/crossplay/README.md)).
-Firmware that works here is expected to degrade gracefully elsewhere.
-
-## Key specifications
-
-| Item | Value | Component record | Evidence |
-|---|---|---|---|
-| SoC | **ESP32-S3**, 16 MB flash, 8 MB PSRAM | [`espressif/esp32-s3r8`](../../../components/espressif/esp32-s3r8/README.md) | **[SDK]** header §X4 Pro |
-| Display | 800×480 mono e-ink, 4.26″, ~219 PPI | — | **[SDK]** `BoardConfig.h:1500–1501` |
-| Display controller | SSD1677 **or** UC8179 **or** UC8279 | [`solomon-systech/ssd1677`](../../../components/solomon-systech/ssd1677/README.md) · [`ultrachip/uc8179`](../../../components/ultrachip/uc8179/README.md) · [`ultrachip/uc8279`](../../../components/ultrachip/uc8279/README.md) | **[SDK]** |
-| Touch | **GT911** capacitive, I²C 0x5D (alt 0x14), portrait-mounted | [`goodix/gt911`](../../../components/goodix/gt911/README.md) | **[SDK]** `BoardConfig.h:1548–1567` |
-| Frontlight | Dual-channel warm/cool LED, LEDC PWM 25 kHz / 10-bit | — | **[DUMP]** OEM LEDC init |
-| RTC | **BM8563** (PCF8563 register-compatible), I²C 0x51 | [`generic/bm8563`](../../../components/generic/bm8563/README.md) | **[SDK]** hardware-confirmed |
-| Fuel gauge | **CW2017**, I²C 0x63, needs an 80-byte BATINFO profile | [`cellwise/cw2017`](../../../components/cellwise/cw2017/README.md) | **[SDK]** hardware-confirmed |
-| Storage | microSD via **native SDMMC**, 1-bit, slot 1, 40 MHz | [`generic/micro-sd-sdmmc`](../../../components/generic/micro-sd-sdmmc/) | **[SDK]** hardware-confirmed |
-| USB | ESP32-S3 native USB-OTG, D− GPIO19 / D+ GPIO20 | — | **[SDK]** |
-| Charging | **Magnetic pogo pins** — no USB-C charge port | — | **[VENDOR]** + **[COMM]** |
-| Charger STAT | GPIO21, active-HIGH | — | **[DUMP]** `Cw2017PowerHal` vtable slot 3 |
-| Radios | Wi-Fi + BLE (ESP32-S3 integrated) | — | **[SDK]** |
-| IMU | **None** — unlike the X3 and X4C | — | **[SDK]** `sensors.imuType = ImuType::None` |
-| Audio / LEDs / PMIC | **None fitted** | — | **[SDK]** `NO_AUDIO`, `NO_LEDS` |
-
-**Reading the table.** The three-way controller ambiguity is the only entry that
-should change how you write code: everything else is fixed silicon. The absence of
-an IMU is worth noting because the X3 and the X4 Classic both have one — a
-"Pro" model is not a superset of its siblings here.
-
-## Architecture and components
-
-One ESP32-S3 owns everything; there is no coprocessor, no GPIO expander and no
-PMIC. Three subsystems share one I²C bus and one SPI-ish display bus:
-
-```
-ESP32-S3 ── SPI(bit-banged CS/DC) ── EPD controller (SSD1677│UC8179│UC8279) ── 800×480 glass
-         ├─ I²C  SDA39/SCL38 @400k ─┬─ GT911 touch      0x5D   (rail gated by GPIO2, active-LOW)
-         │                          ├─ BM8563 RTC       0x51
-         │                          └─ CW2017 gauge     0x63
-         ├─ SDMMC 1-bit ── microSD (rail gated by GPIO5, active-LOW)
-         ├─ LEDC ch4/ch5 ── frontlight cool(GPIO8) / warm(GPIO9)
-         ├─ native USB   ── D−GPIO19 / D+GPIO20
-         └─ GPIO1 ── master peripheral rail (HIGH), asserted first at boot
-```
-
-**GPIO1 is load-bearing and non-obvious.** The OEM board-init drives it HIGH
-before any other bring-up. Without it the panel rail and the SD slot both stay
-unpowered, and the symptom is "EPD BUSY never asserts, SD returns 0xFF"
-**[SDK]** `BoardConfig.h:1599–1602`.
-
-**Two power enables are active-LOW**, which is the opposite of the convention on
-most boards: GPIO2 (touch) and GPIO5 (SD). Driving them HIGH — the naive "enable"
-— leaves the GT911 silent on the bus and breaks every SD block read with error
-`0x107`.
-
-Full tables: [`pinouts-and-buses.md`](pinouts-and-buses.md).
-
-## Common uses and representative projects
-
-- **As shipped** — a sealed EPUB reader with a Chinese-first stock UI.
-- **Reflashed** — the dominant use. CrossPoint Reader, CrossInk and their forks
-  replace the stock firmware entirely.
-- **As an ESP32-S3 e-paper platform** — `vjFaLk/esphome-xteink` exposes it to
-  Home Assistant as an ESPHome component; `thepropm/proink-os` is a from-scratch
-  firmware; `parsimo2010/xteink-ft8` turns one into an FT8 amateur-radio display.
-
-See [`projects-and-community.md`](projects-and-community.md) for the full census.
-
-## Distinctive strengths
-
-- **The only sub-$100 sealed e-reader with a touchscreen, a frontlight and a
-  fully documented, community-reverse-engineered board.** Every pin below was
-  probed on real hardware.
-- **8 MB PSRAM.** This is the practical difference from the C3 X4: multi-buffer
-  rendering, damage-window partial refresh and large book indices are possible
-  here and are not on a C3.
-- **Native SDMMC** rather than SPI — meaningfully faster card access.
-- **Actively maintained firmware** from several independent projects.
-
-## Shortcomings and constraints
-
-- **Pogo-pin charging with no USB-C charge path.** Lose the adapter and the device
-  is unusable. This is the most-cited complaint in the community.
-- **Ships USB-locked from the factory** on many units — see [`development.md`](development.md).
-- **Panel-controller lottery.** Firmware not carrying all three drivers may brick
-  the display on a newer unit.
-- **No IMU**, so no motion page-turn, unlike its cheaper siblings.
-- **Touch axis mirroring is internally contradicted** in the SDK's own
-  documentation — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-- **No published schematic, no FCC filing located, no teardown photography.**
-
-## Performance summary
-
-**No measurement of this device was made in this session, and no independent
-benchmark was found.** What exists:
-
-| Figure | Value | Status |
-|---|---|---|
-| Display SPI clock, OEM | **5 MHz** (`SPISettings 0x4C4B40`) | **[DUMP]** recovered constant |
-| Display SPI clock, FreeInk | 20 MHz | **[SDK]** chosen, in spec |
-| Plane write @20 MHz (X4, same controller) | ~38 ms/refresh | **[SDK]** comment, `BoardConfig.h:836` |
-| SDMMC | 1-bit, 40 MHz | **[SDK]** |
-| Battery capacity | **unknown** | gap |
-
-The OEM clocking its own panel at **5 MHz when the controller is rated for 20**
-is the single most actionable performance finding: stock firmware leaves roughly
-a 4× margin on the table for RAM writes.
-
-## Pricing and availability
-
-See [`market-and-pricing.md`](market-and-pricing.md). Headline, **2026-09-04**,
-vendor direct, worldwide from Shenzhen: **US$99.00**, Space Black, in stock.
-
-## Competitors, equivalents and clones
-
-See [`comparisons-and-recommendations.md`](comparisons-and-recommendations.md).
-
-## Launch-era versus current market fit
-
-At launch (2026-07-21) the X4 Pro was the only sealed sub-$100 reader with both
-touch and a frontlight that also had a live open-source firmware scene. As of
-2026-09-04 that is still true, but the **S4** — Android 11, frontlight, touch, at
-~¥339 (≈US$50) — undercuts it on paper for anyone who does not care about
-programmability. See [`../s4/README.md`](../s4/README.md).
-
-## When to use / when not to use
-
-**Use it when** you want a pocket e-reader you will reflash, you want touch and a
-frontlight, and you accept a proprietary charging cable. **Do not use it when**
-you need a general-purpose ESP32-S3 dev board (buy a
-[PaperMono](../../m5stack/papermono/README.md) or a Waveshare board — you get
-headers, USB-C, a schematic and no unlock dance), or when you need USB-C charging,
-or when you need an IMU.
-
-## Alternatives by tier
-
-| Tier | Alternative | Why |
-|---|---|---|
-| Cheaper, same family | [X4](../x4/README.md) $69 / [X3](../x3/README.md) $69 | No touch, no frontlight, C3 not S3 |
-| Cheaper, buttons + S3 | [X4 Classic](../x4-classic/README.md) | Same board, no touch/frontlight, **plus** an IMU |
-| Development board | [M5Stack PaperMono](../../m5stack/papermono/README.md) | Schematic published, USB-C, headers, no unlock |
-| Non-programmable | S4, Kobo, Boox | If you will never flash it, programmability is not worth the pogo pin |
-
-## Images and teardown/PCB views
-
-**None held.** No X4 Pro teardown was located. This is a real gap —
-[`media.md`](media.md) records what was searched.
-
-## Community, editorial and project coverage
-
-[`community.md`](community.md) · [`projects-and-community.md`](projects-and-community.md)
-
-## Common tasks / How do I…?
-
-| Task | Guide |
-|---|---|
-| Drive the display / handle the 3-controller lottery | [`features/display.md`](features/display.md) |
-| Read touch and the capacitive Home key | [`features/touch.md`](features/touch.md) |
-| Read the two side buttons and power | [`features/buttons.md`](features/buttons.md) |
-| Control the warm/cool frontlight | [`features/frontlight.md`](features/frontlight.md) |
-| Mount the microSD card | [`features/storage.md`](features/storage.md) |
-| Read battery percentage / charge state | [`features/battery-and-power.md`](features/battery-and-power.md) |
-| Use USB / USB-MSC | [`features/usb.md`](features/usb.md) |
-| Use Wi-Fi and BLE | [`features/wifi-and-bluetooth.md`](features/wifi-and-bluetooth.md) |
-| Read the RTC | [`features/rtc.md`](features/rtc.md) |
-| Build and flash firmware | [`development.md`](development.md) |
-| Unlock a USB-locked unit | [`development.md`](development.md#usb-lock) |
-| Dump / restore stock firmware | [`factory-firmware.md`](factory-firmware.md) |
-
-## Documentation map
-
-[`pinouts-and-buses.md`](pinouts-and-buses.md) ·
-[`development.md`](development.md) ·
-[`factory-firmware.md`](factory-firmware.md) ·
-[`sources.md`](sources.md) ·
-[`research-log.md`](research-log.md) ·
-[`commands.md`](commands.md) ·
-[`coverage.md`](coverage.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md) ·
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) ·
-[`market-and-pricing.md`](market-and-pricing.md) ·
-[`comparisons-and-recommendations.md`](comparisons-and-recommendations.md) ·
-[`projects-and-community.md`](projects-and-community.md) ·
-[`community.md`](community.md) ·
-[`media.md`](media.md)
-
-## Artifact layout
-
-```
-artifacts/
-├── firmware/           (empty — see factory-firmware.md; no X4 Pro image was located)
-└── source-snapshots/   (empty — the FreeInk SDK clone lives in scratch/eink-software/repos/)
-```
-
-**No artifact is held for this device.** The X4 Pro OTA package
-`xteink_app_update_x4pro_7.4.4_20260827_133901.xota` is named in the SDK docs but
-was **not located for download**. See [`factory-firmware.md`](factory-firmware.md).
-
-## Known conflicts and unresolved identities
-
-Summarised in [`gaps-and-conflicts.md`](gaps-and-conflicts.md). The two that
-matter most: the SDK's board header and its own device doc **disagree about
-whether touch axis flipping is confirmed or pending**, and the **battery capacity,
-device mass and dimensions are entirely unestablished**.
-
----
-
-# ROUND 2 — appended 2026-09-11. **The X4 Pro now has three second custodians.**
-
-**No line above was altered.** The record above, and
-[`VERIFICATION-xteink.md`](../../../VERIFICATION-xteink.md) §12, stated the
-central weakness plainly: *"for the X4 Pro and X4 Classic, essentially every
-technical claim traces to one repository at one commit
-(`Free-Ink/freeink-sdk` @ `24003795381a6c23630a26472ae3b06550333e71`), with no
-teardown, schematic or regulatory filing to corroborate it."*
-
-**That is no longer true for the X4 Pro.** Three independent custodians now
-exist, one of them a US federal record and one of them a person with the device
-on a desk running `esptool` against it.
-
-## Custodian 2 — a physical unit, dumped and instrumented
-
-| | |
-|---|---|
-| Who | [`kycube/x4pro-emu`](https://github.com/kycube/x4pro-emu) — a QEMU emulator for the X4 Pro |
-| Commit | **`bf4b86ae0471012d4d07c0bb3042f3f561c9c302`** |
-| Repo created | **2026-09-07** — three days after the first sweep |
-| Licence | **none stated** → redistribution `unknown`, **reference-only**, not vendored |
-| Basis | *"Xteink X4 Pro on the desk"*, read-only operations, 2026-09-06 |
-
-### What it independently confirms
-
-| Claim | Prior evidence | New evidence | Verdict |
-|---|---|---|---|
-| SoC is **ESP32-S3** | FreeInk profile | **`esptool chip-id`: ESP32-S3 (QFN56) rev v0.2, 40 MHz crystal, USB-Serial/JTAG, MAC `98:c3:77:be:ea:30`** | **confirmed on silicon** |
-| **8 MB PSRAM** | FreeInk profile | eFuse `PSRAM_CAP=8M`, `PSRAM_VENDOR=AP_3v3`; boot log *"Embedded PSRAM 8MB"*, octal, 80 MHz | **confirmed** |
-| **16 MB flash** | FreeInk profile, image length | boot log `flash io: qio`; a **16,777,216 B** dump | **confirmed** |
-| Partition table | FreeInk docs | decoded from the dump: `nvs` `0x9000`/`0x5000`, `otadata` `0xE000`/`0x2000`, `app0` `0x10000`/`0x7E0000`, `app1` `0x7F0000`/`0x7E0000`, `spiffs` `0xFD0000`/`0x14000`, `coredump` `0xFE4000`/`0x1C000` | **confirmed** |
-| **GT911 @ 0x5D**, SDA 39 / SCL 38 @ 400 kHz, INT 10, RST 4, power-enable GPIO2 active-low | FreeInk profile | live I²C traces of the stock app | **confirmed** |
-| **BM8563 @ 0x51** | FreeInk profile | I²C map | **confirmed** |
-| **CW2017 @ 0x63**, needs an 80-byte BATINFO to `0x10..0x5F` | FreeInk + a register dump | I²C map, same addresses and behaviour | **confirmed** |
-| Buttons **Left GPIO0, Right GPIO7, Power GPIO3**, active-low `INPUT_PULLUP` | FreeInk, and this repository's own refutation that GPIO7 was a display enable | independent restatement from the running board | **confirmed — the earlier refutation stands** |
-| Frontlight **cool GPIO8 / warm GPIO9**, LEDC 25 kHz 10-bit | FreeInk profile | LEDC register traces of the stock app, including hardware fades | **confirmed, and extended** |
-| SDMMC **CLK 41 / CMD 42 / DAT0 40**, slot 1, 1-bit; **GPIO5** active-low card-power gate | FreeInk profile | same | **confirmed** |
-| Charger `STAT` **GPIO21**, active-high | FreeInk profile | same | restated, still not independently measured |
-| **Panel controller varies by batch; VER/FLG probe** | FreeInk `XteinkDetect.cpp` | this unit: NVS `hw_calib/screenType = 2` → **UC8279**, and CrossPoint on the device printed **`VER=00 0F 68 00 00 FLG=13`** → LUT_VER `0x68` → UC8279 | **confirmed on hardware, twice, by two mechanisms** |
-
-### What it adds that nobody had
-
-- **eFuse state**: no secure boot, no flash encryption, all key purposes `USER`,
-  USB Serial/JTAG enabled. **The X4 Pro is not locked at the silicon level.**
-- **A factory serial in eFuse BLOCK3**: ASCII `X4CB02EN26082416646`.
-- **Stock firmware `xteink_app` 7.2.4**, ESP-IDF **v6.0.1**, built
-  **2026-08-14 19:25:05**; bootloader built 2026-08-14 19:24:53.
-  **This is a fourth version number for X4 Pro stock firmware** — see
-  [`factory-firmware.md`](factory-firmware.md).
-- **Two independent full-flash dumps hashing identically**
-  (`90734554798da8dbe…0143fe`) — the correct way to prove a dump, and the first
-  time it has been done in this family.
-- **The stock app talks to the panel at 10 MHz** (`SPI2 CLOCK 0x70c7`), not the
-  5 MHz the FreeInk comments attribute to the OEM. A 48,000-byte plane takes
-  ≈38 ms.
-- **The stock UC8279 command stream, traced**: `00 37 4D` PSR, `61 03 20 02 58`
-  TRES (**800×600 declared, gates 120–599 used**), `65` GSST, `03 20` PFS,
-  `E1 02`, DTM2/DTM1/DTM2, `50 97` CDI, `E0 02`, `E5 1E`, `04` PON (40 ms),
-  `00 17 4D`, `12` DRF (1.3 s). And the finding that **the old plane is
-  pre-sent immediately after each refresh**, so a trace ending in DTM1 is idle,
-  not stalled.
-- **Frontlight behaviour**: warm channel at 249 ‰ on wake, **fades out 60 s after
-  the last input**, nine colour-temperature presets from Cool 4 to Warm 4 with
-  the two channels mixed at roughly constant total, brightness in 10 % steps.
-  NVS `user_config/lightBri`, `lightCT`, `lightOn`.
-- **The Home pad is a GT911 touch key**, not a GPIO: bit 4 of status `0x814E`,
-  key byte at `0x814F + 8·count`. The stock treats it as **Back, one level**.
-- **NVS `hw_calib/region`**: `1` = CN, `2` = overseas.
-
-### What it corrects
-
-The FreeInk **support document's** I²C paragraph has **INT and RST swapped** and
-is stale; the **struct** is right. Where the two disagree, trust the struct.
-
-## Custodian 3 — a firmware project that tested on hardware
-
-[`clackups/draftling`](https://github.com/clackups/draftling) @
-`92ba7e514f66bbe42a7fea6d38eff45eed82617b`, MIT, 71 stars. Its `HARDWARE.md`
-states, verbatim: ***"This board has been tested on physical hardware after an
-initial blind port."*** Two findings, both of which are things only hardware
-tells you:
-
-1. **A real asynchronous-DMA bug in the shared UC8179/UC8279 path.** A full
-   refresh *"reproducibly painted only the top third or so of the panel"*. Cause:
-   the OLD-plane write reused the same scratch buffer the NEW-plane write had
-   just handed to `esp_lcd_panel_io_tx_color()`, whose transfer is queued
-   asynchronously and could still be in flight when the next line `memset` it.
-   Fixed by streaming the OLD plane's constant white fill from a separate,
-   never-mutated buffer. **Anyone writing a driver for this panel from the same
-   reverse engineering can hit this.**
-2. **A touch-orientation correction made against a physical unit.** FreeInk's
-   `swapXY=true, flipY=true` *"had touches landing 180 degrees opposite of where
-   the finger was"*; Draftling's `TOUCH_MIRROR_X`/`TOUCH_MIRROR_Y` are now `1`/`0`.
-   **This contradicts FreeInk's "confirmed by corner-tap" annotation**, and it is
-   recorded as an open conflict — the two projects use different rendering
-   stacks with different orientation conventions, so they may not actually
-   disagree. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-It also runs the panel at **the OEM's 5 MHz** rather than FreeInk's rate, and
-uses a **dual-OTA partition table on purpose** so the stock and CrossPoint
-updaters can reinstall — they refuse a table with no `otadata`.
-
-## Custodian 4 — the United States FCC
-
-| Field | Value |
-|---|---|
-| **FCC ID** | **`2BTR9-X4PRO`** |
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, Longhua District, Shenzhen, FRN `0037772233` |
-| Granted | **2026-06-16** — five weeks before the store listing of 2026-07-21 |
-| Equipment class | DTS, **2412–2462 MHz** |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Public now | **External Photos (5.1 MB)**, Label and Information (1.1 MB), Antenna Report, Test Report, RF Exposure, attestations |
-| **Internal Photos (1,023 KB)** | **embargoed until 2026-12-12** |
-| Schematics · Block Diagram · Operational Description | **permanently confidential** |
-
-Retained: [`artifacts/certification/`](artifacts/certification/README.md) — the
-external photographs and the label exhibit. **The internal photographs become
-public on 2026-12-12**, which is the dated route to a PCB-level verification of
-the remaining single-source claims.
-
-## What is *still* single-source
-
-Be precise about what has and has not been corroborated:
-
-| Still traces only to FreeInk | Why the new custodians do not help |
-|---|---|
-| **Panel pin assignment** SCLK 12 / MOSI 11 / CS 13 / DC 18 / RST 14 / BUSY 6 | Both new firmware custodians cite FreeInk as their source; neither derived the pins independently |
-| The `XteinkDetect` probe **algorithm** | Same lineage. Its *result* on one unit is now confirmed; the bit-banged procedure is not |
-| Charge-`STAT` polarity on GPIO21 | Restated, never measured |
-| Exact refresh timings (~1800 ms full, ~500 ms fast) | Inherited from FreeInk's docs; the desk unit's own measurement is explicitly marked pending by its author |
-
-**The right summary is: the X4 Pro's *silicon, memory, flash map, I²C map,
-button map, SD path, frontlight behaviour and panel identity* are now
-hardware-confirmed by a third party. Its *panel pinout* is not.**
-
-## Correction to the record above
-
-`displaySpiHz` for the X4 Pro profile changed from **20 MHz to 10 MHz** in
-FreeInk commit
-[`39606d5a`](https://github.com/Free-Ink/freeink-sdk/commit/39606d5a)
-(2026-09-09), now shared as `XTEINK_DISPLAY_SPI_HZ` across every Xteink board.
-The comment that previously justified 20 MHz — *"the OEM clocks the panel at only
-5 MHz… but the SSD1677 handles far more"* — is gone. **Independently, the desk
-unit's stock app was measured running SPI2 at 10 MHz**, so the OEM's own rate on
-at least one shipping unit is 10 MHz, not 5 MHz.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 165:* - **No published schematic, no FCC filing located, no teardown photography.**
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-pro/acquisition/README.md b/devices/xteink/x4-pro/acquisition/README.md
deleted file mode 100644
index 7f9eadb..0000000
--- a/devices/xteink/x4-pro/acquisition/README.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Xteink X4 Pro — acquisition
-
-**No artifact was acquired for this device.** That is not for lack of trying — see
-the table below. The X4 Pro is the family's flagship and has the **thinnest
-artifact position** of any model with a public existence.
-
-## Clean-clone commands
-
-None. Nothing is held.
-
-The one thing worth cloning is the SDK that documents the board, which is a
-*source* dependency rather than a device artifact:
-
-```bash
-git clone https://github.com/Free-Ink/freeink-sdk
-git -C freeink-sdk checkout 24003795381a6c23630a26472ae3b06550333e71
-```
-
-## Wanted artifacts
-
-| Artifact | Reacquisition | Notes |
-|---|---|---|
-| **An X4 Pro stock firmware image** | **`blocked`** | **No public X4 Pro image exists anywhere.** The X3 has four published stock images and the X4 has a community dump; the flagship has neither. Only route: dump a USB-unlocked unit |
-| `xteink_app_update_x4pro_7.4.4_20260827_133901.xota` | **`blocked`** | Named in the FreeInk SDK docs; **no download URL found**. The `.xota` container appears encrypted — the SDK refers to *"the decrypted"* app and the mechanism is undocumented |
-| Vendor OTA feed response | **`manual`** | `http://gotaserver.xteink.com/api/check-update` — endpoint recovered from the **X4** dump. **Not queried.** Request format unknown |
-| Any teardown or PCB photograph | **`lost`** | None exists. Would close **seven** separate unknowns at once — see [`gaps-and-conflicts.md`](../gaps-and-conflicts.md) |
-| Vendor product imagery | **`automatic`** | Listing is **live**; URLs are in `scratch/xteink/vendor/products-p1.json` under `products[].images[].src`. **Capture before delisting** — the X4's imagery was lost exactly that way |
-| FCC / CE / SRRC filing | **`blocked`** | No ID known, and the community reports Xteink devices **carry no external regulatory marking** — regulatory text is placed in software instead |
-
-## Why nothing was downloaded
-
-Not a scope decision. The X4 Pro simply has **no public binary or document** to
-fetch:
-
-- **No vendor SDK, datasheet, manual, schematic or BSP.** Xteink publishes none.
-- **No community firmware dump.** Unlike the X3 and X4.
-- **No teardown.** Unlike the X3.
-- **No regulatory filing.** Unlike almost any consumer radio device.
-
-Everything in this device record derives from **one repository at one commit** —
-`Free-Ink/freeink-sdk` @ `24003795381a6c23630a26472ae3b06550333e71` — plus the
-vendor's Shopify API and Reddit.
-
-## Chip datasheets belong to components, not here
-
-Per the filing rule, datasheets for the SSD1677, UC8179, UC8279, GT911, CW2017,
-BM8563 and ESP32-S3 are **component** artifacts. Their acquisition status is
-recorded in each component record; several are `not-attempted` and are flagged
-there as open.
-
-## Verification
-
-```bash
-python3 tools/audit_archive.py     # confirms nothing archived here is unreferenced
-```
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 28:* | FCC / CE / SRRC filing | **`blocked`** | No ID known, and the community reports Xteink devices **carry no external regulatory marking** — regulatory text is placed in software instead |
->
-> *line 38:* - **No regulatory filing.** Unlike almost any consumer radio device.
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](../certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-pro/acquisition/manifest-fcc-exhibits.json b/devices/xteink/x4-pro/acquisition/manifest-fcc-exhibits.json
deleted file mode 100644
index 50badd8..0000000
--- a/devices/xteink/x4-pro/acquisition/manifest-fcc-exhibits.json
+++ /dev/null
@@ -1,79 +0,0 @@
-{
- "record": "devices/xteink/x4-pro",
- "generated": "2026-09-11",
- "note": "Sibling of `manifest.json`. That file's `artifacts` array is written inline as `[]`, so it cannot be extended without rewriting an existing line; this pass is append-only. Merge on the next non-append-constrained edit.",
- "artifacts": [
-  {
-   "id": "fcc-2BTR9-X4PRO-9386963",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2BTR9-X4PRO/External-Photos/External-Photos-9386963.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9386963",
-    "https://fcc.report/FCC-ID/2BTR9-X4PRO/9386963.pdf",
-    "https://fccid.io/2BTR9-X4PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2BTR9-X4PRO/External-Photos/External-Photos-9386963.pdf"
-   ],
-   "sha256": "2565de437321171cdae9b81fefa061ec508d6fe857fae2ee7ab8e69322cd506c",
-   "bytes": 5317690,
-   "destination": "devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-external-photos.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-06-16",
-   "fcc_id": "2BTR9-X4PRO",
-   "fcc_document_id": "9386963",
-   "exhibit_type": "External Photos",
-   "exhibit_title_as_filed": "External Photos",
-   "grant_date": "2026-06-16",
-   "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen BKC Testing Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "repository",
-   "repo_state": "untracked",
-   "archived_to": null,
-   "placeholder": null,
-   "extraction": null,
-   "target_hardware": "devices/xteink/x4-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  },
-  {
-   "id": "fcc-2BTR9-X4PRO-9386969",
-   "kind": "regulatory-exhibit",
-   "canonical_url": "https://fccid.io/2BTR9-X4PRO/RF-Exposure-Info/RF-Exposure-Report-9386969.pdf",
-   "fallback_urls": [
-    "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9386969",
-    "https://fcc.report/FCC-ID/2BTR9-X4PRO/9386969.pdf",
-    "https://fccid.io/2BTR9-X4PRO",
-    "https://web.archive.org/web/2/https://fccid.io/2BTR9-X4PRO/RF-Exposure-Info/RF-Exposure-Report-9386969.pdf"
-   ],
-   "sha256": "8d10f31b2c17ba2795dcc5dc40ef062205f0110f294de492f48df541ef47da3c",
-   "bytes": 148234,
-   "destination": "devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf",
-   "retrieved": "2026-09-11",
-   "upstream_version_or_date": "2026-06-16",
-   "fcc_id": "2BTR9-X4PRO",
-   "fcc_document_id": "9386969",
-   "exhibit_type": "RF Exposure Info",
-   "exhibit_title_as_filed": "RF Exposure Report",
-   "grant_date": "2026-06-16",
-   "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-   "test_firm": "Shenzhen BKC Testing Co., Ltd.",
-   "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-   "license_evidence": "FCC Equipment Authorization System publication",
-   "redistribution_status": "allowed",
-   "disposition": "archive",
-   "repo_state": "placeholder-only",
-   "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf",
-   "placeholder": "devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf.ARCHIVED.md",
-   "extraction": null,
-   "target_hardware": "devices/xteink/x4-pro",
-   "reacquisition": "automatic",
-   "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-   "last_verified": "2026-09-11",
-   "notes": "Filed by the round-2 index merge, 2026-09-11."
-  }
- ]
-}
diff --git a/devices/xteink/x4-pro/acquisition/manifest.json b/devices/xteink/x4-pro/acquisition/manifest.json
deleted file mode 100644
index 8ede693..0000000
--- a/devices/xteink/x4-pro/acquisition/manifest.json
+++ /dev/null
@@ -1,130 +0,0 @@
-{
-  "device": "xteink/x4-pro",
-  "generated": "2026-09-04",
-  "note": "No artifact acquired. Not a scope decision: no public firmware image, teardown, schematic, datasheet or regulatory filing exists for this device. Every technical claim derives from Free-Ink/freeink-sdk @ 24003795381a6c23630a26472ae3b06550333e71 plus the vendor Shopify API.",
-  "artifacts": [],
-  "wanted": [
-    {
-      "id": "x4pro-stock-dump",
-      "kind": "firmware-image",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x4-pro/artifacts/firmware/",
-      "retrieved": null,
-      "upstream_version": "xteink_app 7.4.4 (ESP-IDF 6.0.1, built 2026-08-27); earlier 7.0.8",
-      "license": "unknown (vendor firmware)",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "blocked",
-      "reason": "No public X4 Pro image exists. The X3 has four published stock images and the X4 has a community dump; the flagship has neither.",
-      "target_hardware": "Xteink X4 Pro, ESP32-S3, 16 MB flash, 8 MB PSRAM",
-      "firmware": {
-        "target_mcu": "ESP32-S3",
-        "image_role": "merged full-flash image",
-        "flash_offset": "0x0",
-        "partitions": [
-          [
-            "nvs",
-            "0x009000",
-            "0x005000"
-          ],
-          [
-            "otadata",
-            "0x00E000",
-            "0x002000"
-          ],
-          [
-            "app0",
-            "0x010000",
-            "0x7E0000"
-          ],
-          [
-            "app1",
-            "0x7F0000",
-            "0x7E0000"
-          ],
-          [
-            "spiffs",
-            "0xFD0000",
-            "0x014000"
-          ],
-          [
-            "coredump",
-            "0xFE4000",
-            "0x01C000"
-          ]
-        ],
-        "companion_images": null,
-        "flash_instructions": "esptool.py --chip esp32s3 --port <port> --baud 921600 write_flash 0 <file>  [INFERRED, not executed]",
-        "notes": "CRITICAL: the dump carries TWO app images for DIFFERENT variants. app0 = ESP32S3_X4_TL (a different, Arduino-era variant with a WRONG pin map). app1 = XTEink X4 Pro / ESP32S3_X4_TL_SSD1677 (the real firmware). otadata selects app1. Every early RE pass read app0 and derived a scrambled display pinout."
-      }
-    },
-    {
-      "id": "x4pro-ota-package",
-      "kind": "firmware-image",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x4-pro/artifacts/firmware/xteink_app_update_x4pro_7.4.4_20260827_133901.xota",
-      "retrieved": null,
-      "upstream_version": "7.4.4 (package metadata claims V7.4.5; the embedded app descriptor is authoritative)",
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "blocked",
-      "reason": "Filename is named in docs/xteink-x4pro-support.md but no download URL was found anywhere.",
-      "notes": "The .xota container appears encrypted - the SDK refers to 'the decrypted ESP32-S3 app'. Mechanism undocumented."
-    },
-    {
-      "id": "x4pro-ota-feed",
-      "kind": "api-response",
-      "canonical_url": "http://gotaserver.xteink.com/api/check-update",
-      "sha256": null,
-      "bytes": null,
-      "destination": "scratch/xteink/vendor/",
-      "retrieved": null,
-      "license": "n/a",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Endpoint recovered by string extraction from the X4 (ESP32-C3) dump; assumed shared brand-wide but unverified for this model. Request format unknown. Not queried this session.",
-      "notes": "Plain HTTP. Would likely give the current stock version and a download URL - the cheapest route to the two blocked firmware entries above."
-    },
-    {
-      "id": "x4pro-teardown",
-      "kind": "teardown-photography",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x4-pro/media/",
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "lost",
-      "reason": "No X4 Pro teardown exists in 2,136 Reddit posts or a ~200-repository GitHub census.",
-      "notes": "Would close SEVEN unknowns simultaneously: battery capacity, mass, dimensions, charger IC, panel module part, antenna type, debug pads."
-    },
-    {
-      "id": "x4pro-vendor-imagery",
-      "kind": "image",
-      "canonical_url": "https://www.xteink.com/products/xteink-x4-pro-pocket-ereader",
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x4-pro/media/",
-      "retrieved": null,
-      "license": "vendor, all rights reserved (presumed)",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "reason": "Deliberately not downloaded: marketing renders establish nothing beyond the text record, and rights are unexamined.",
-      "notes": "URLs are in scratch/xteink/vendor/products-p1.json under products[].images[].src, retrieved 2026-09-04. CAPTURE BEFORE DELISTING - the X4's imagery was lost that way."
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-external-photos.pdf b/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-external-photos.pdf
deleted file mode 100644
index 0473f51..0000000
Binary files a/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-external-photos.pdf and /dev/null differ
diff --git a/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-label.pdf b/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-label.pdf
deleted file mode 100644
index 765a863..0000000
Binary files a/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-label.pdf and /dev/null differ
diff --git a/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf.ARCHIVED.md b/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf.ARCHIVED.md
deleted file mode 100644
index bf48d66..0000000
--- a/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-X4PRO-rf-exposure-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 148,234 B (0.14 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 148,234 B (0.14 MiB) |
-| SHA-256 | `8d10f31b2c17ba2795dcc5dc40ef062205f0110f294de492f48df541ef47da3c` |
-| FCC ID | **`2BTR9-X4PRO`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Report |
-| FCC document id | 9386969 |
-| Upstream publication date | 2026-06-16 |
-| Grant date | 2026-06-16 |
-| Equipment class | XTEINK X4 Pro, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-X4PRO/RF-Exposure-Info/RF-Exposure-Report-9386969.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=9386969>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-X4PRO/9386969.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-X4PRO>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-X4PRO/RF-Exposure-Info/RF-Exposure-Report-9386969.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf" \
-   "devices/xteink/x4-pro/artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-X4PRO/RF-Exposure-Info/RF-Exposure-Report-9386969.pdf" -o "2BTR9-X4PRO-rf-exposure-report.pdf"
-echo "8d10f31b2c17ba2795dcc5dc40ef062205f0110f294de492f48df541ef47da3c  2BTR9-X4PRO-rf-exposure-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x4-pro/artifacts/certification/README.md b/devices/xteink/x4-pro/artifacts/certification/README.md
deleted file mode 100644
index 63005d3..0000000
--- a/devices/xteink/x4-pro/artifacts/certification/README.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# FCC equipment-authorization exhibits — `2BTR9-X4PRO`
-
-Retrieved **2026-09-11** from `fccid.io` with UA `WhatsApp/2.23.20.0`; validated
-by magic bytes (`%PDF`).
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-X4PRO`** |
-| Device description | XTEINK X4 Pro |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. |
-| Granted | **2026-06-16** (store listing followed on 2026-07-21) |
-| Equipment class | DTS, 2412–2462 MHz |
-| Source page | <https://fccid.io/2BTR9-X4PRO> |
-
-## Retained
-
-| File | Bytes | SHA-256 | Establishes |
-|---|---:|---|---|
-| `2BTR9-X4PRO-external-photos.pdf` | 5,317,690 | `2565de437321171cdae9b81fefa061ec508d6fe857fae2ee7ab8e69322cd506c` | 7 embedded images, the largest 5712×4284 at 1107 ppi. Exterior of a retail X4 Pro against a millimetre rule — the highest-resolution public photographs of this device |
-| `2BTR9-X4PRO-label.pdf` | 1,169,828 | `3d404d1cefbfc39fd3edd9a627ff97997c5d53bf951eb291c08f0df8cba32969` | Compliance-label artwork and placement; one 3096×2322 image at 600 ppi |
-
-- `https://fccid.io/2BTR9-X4PRO/External-Photos/External-Photos-9386963.pdf`
-- `https://fccid.io/2BTR9-X4PRO/Label/Label-and-Information-9386964.pdf`
-
-`2BTR9-X4PRO-external-photos.pdf` at 5.3 MB is the **largest single file added to
-the Xteink tree by this pass**. If the repository's size policy requires it to be
-archived, everything needed to reacquire it is in this table and the URL above.
-
-## Not retained
-
-| Exhibit | Size | Why |
-|---|---|---|
-| Antenna Report | 1.5 MB | public, not fetched |
-| Test Report | 3.1 MB | public, not fetched |
-| RF Exposure Report | 144.8 KB | public, not fetched |
-| Attestations, cover letters | 114–179 KB | boilerplate |
-| **Internal Photos** | **1,023 KB** | **embargoed until 2026-12-12** — the document that would corroborate the panel pinout |
-| Users Manual | 2.9 MB | embargoed until 2026-12-12 |
-| Test Setup Photos | 308.8 KB | embargoed until 2026-12-12 |
-| **Schematics** (592.7 KB) · **Block Diagram** (53.8 KB) · Operational Description (56.1 KB) | — | **permanently confidential** |
-
-**Re-check on or after 2026-12-12.** The X4 Pro's internal photographs are the
-earliest of the whole family to be released — before the X4 Classic's
-(2027-01-16) and the X4 Light's (2027-02-09) — and they are the cheapest route
-to closing gap R2-P2.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`unknown`** — third-party submissions published by a US federal agency; routinely mirrored; no explicit grant located |
-| Disposition | `repository`, **unstaged** |
-| Total retained | **2 files, 6,487,518 bytes** |
-
-Cited from [`../../README.md`](../../README.md) (Custodian 4) and
-[`../../gaps-and-conflicts.md`](../../gaps-and-conflicts.md).
-
----
-
-## Correction, 2026-09-11 — redistribution is `allowed`, not `unknown`
-
-The *Licensing and disposition* table above records **`unknown`**. That was
-conservative but wrong, and it is superseded:
-
-| Field | Value, as of 2026-09-11 |
-|---|---|
-| Redistribution status | **`allowed`** |
-| Basis | FCC equipment-authorisation exhibits are **US Government public records**, published by the Commission under 47 CFR §2.1033. The agency asserts no copyright, and the exhibits are routinely republished by mirrors. |
-| Scope | Applies to every exhibit in this directory, and to every FCC exhibit elsewhere in this repository. |
-
-**The original rows above are left exactly as written.** This note supersedes
-their redistribution field only; their hashes, sizes and URLs remain correct and
-authoritative.
-
-Confidentiality embargoes are a **separate** matter and are unaffected: exhibits
-the applicant had withheld were never published, so there is nothing to
-redistribute until their release dates.
-
-Logged in [`scratch/index-merge/corrections-requiring-review.md`](../../../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-pro/certification-and-compliance.md b/devices/xteink/x4-pro/certification-and-compliance.md
deleted file mode 100644
index bab2f10..0000000
--- a/devices/xteink/x4-pro/certification-and-compliance.md
+++ /dev/null
@@ -1,204 +0,0 @@
-# Certification and compliance — x4-pro
-
-Compiled **2026-09-11** by the round-2 index merge, from the certification pass's findings in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md). Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware.
-
-> **Why this arrived late.** These findings were produced on 2026-09-11 but written into `scratch/` because a sibling agent held `devices/xteink/` at the time. That conflict is over; this file is the properly-filed result.
-
----
-
-## 1. Summary
-
-**FCC: granted.** `2BTR9-X4PRO`, 2026-06-16.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2BTR9-X4PRO` — granted **2026-06-16** |
-| **CE / RED (EU)** | ⚠ no published DoC located; no database exists to search (§4) |
-| **UKCA** | ⚠ not determined (§4) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§4) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§4) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§4) |
-
-⚠ **This reverses the 2026-09-04 finding of *no FCC/CE filings*.** See §5.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Every
-probe below ran on **2026-09-11**, in one session, against one host, with one tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** — a real Xteink grant |
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** — M5Stack Cardputer |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**Positives → 200. Negatives → 404.** Raw run:
-`scratch/market-and-certification/logs/fcc-controls.txt`.
-
-These controls are the whole basis on which the absence findings below may be read as evidence.
-They are reproduced in each of the five Xteink records rather than referenced once, because a
-reader arriving at one device record must be able to judge that record's evidence without
-chasing a link.
-
-Beyond the ID probes, **the grantee was enumerated in full rather than guessed**: `2BTR9`
-yields **five** FCC IDs and no more. A product absent from a complete grantee listing is
-*absent*, not merely *un-found* — which is exactly the distinction the 2026-09-04 sweep could
-not make, because it had no grantee code to enumerate.
-
-⚠ **A counter-trap worth recording.** `https://fccid.io/2BTR9` prints **"6 FCC IDs"** in its
-page header, but the applications table lists **five**, and exactly five `href="/2BTR9…"` links
-exist in the HTML. The headline counter and the table disagree. **Trust the table.**
-
----
-
-## 3. The whole grantee — `2BTR9`
-
-| Field | Value |
-|---|---|
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** |
-| Grantee code | **`2BTR9`** |
-| Registered | **2025-12-21** |
-| Contact | Chen Chu |
-| Address | Room 1209, Yichuang International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community, Guanlan Street, Longhua District, Shenzhen, China |
-| FCC IDs | **5** |
-
-| FCC ID | Granted | Device | Purpose | Record |
-|---|---|---|---|---|
-| `2BTR9-X4L` | **2026-08-13** | XTEINK X4 Light | Original Equipment | [`x4-light`](../x4-light/README.md) |
-| `2BTR9-X4C` | **2026-07-20** | XTEINK X4 Classic | Original Equipment | [`x4-classic`](../x4-classic/README.md) |
-| `2BTR9-X4PRO` | **2026-06-16** | XTEINK X4 Pro | Original Equipment | [`x4-pro`](../x4-pro/README.md) |
-| `2BTR9-XTEINKX4` | **2026-01-05** | XTEINK X4 | Original Equipment | [`x4`](../x4/README.md) |
-| `2BTR9-XTEINKX3` | **2025-12-26** | XTEINK X3 | Original Equipment | [`x3`](../x3/README.md) |
-
-All five: 2402–2480 MHz (BLE) and 2412–2462 MHz (Wi-Fi, US channels 1–11). Long-term
-confidentiality granted on all five for Schematics, Block Diagram and Operational Description.
-
-**Not granted:** no FCC ID under `2BTR9` corresponds to the [**Xteink S4**](../s4/README.md) or
-the [**Xteink Nano**](../nano/README.md). Against a complete enumeration with passing controls,
-those two devices are **not FCC-authorised as of 2026-09-11**.
-
-Xteink filed **Original Equipment** authorisations, not module-based ones. The internal
-photographs show why: the X4 main PCB carries a **bare QFN SoC with a PCB meander antenna etched
-into the board**, not a drop-in pre-certified Espressif module. A design like that cannot
-inherit a module grant, so the vendor had to certify the whole device. That is consistent with,
-and corroborates, the grant record.
-
-
-### The `2BTR9-X4PRO` filing
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-X4PRO`** |
-| Device description | XTEINK X4 Pro |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Granted | **2026-06-16** |
-| Frequency ranges | 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen BKC Testing Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Short-term confidentiality | Yes |
-| Exhibit rows | 12 |
-| Filing page | <https://fccid.io/2BTR9-X4PRO> — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld:**
-
-- User Manual [Users Manual 2026-12-12]
-- Internal Photos [Internal Photos 2026-12-12]
-- Test Setup Photos [Test Setup Photos 2026-12-12]
-- BLOCK [Block Diagram]
-- SCH [Schematics]
-- Operational Description [Operational Description]
-
-Internal photographs are **withheld under short-term confidentiality until 2026-12-12**.
-
-**Exhibits obtained** — US Government public records, redistribution **`allowed`**. Downloaded 2026-09-11, magic bytes validated (`%PDF`).
-
-Retained in this record, at [`artifacts/certification/`](artifacts/certification/README.md):
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| [`2BTR9-X4PRO-external-photos.pdf`](artifacts/certification/2BTR9-X4PRO-external-photos.pdf) | 5,317,690 | `2565de437321171cdae9b81fefa061ec…` | External Photos |
-
-Archived out of the repository, each with a self-sufficient placeholder beside it carrying hash, size, FCC document id and five reacquisition URLs:
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2BTR9-X4PRO-rf-exposure-report.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-X4PRO-rf-exposure-report.pdf.ARCHIVED.md) | 148,234 | RF Exposure Info |
-
----
-
-## 4. Other jurisdictions
-
-| Regime | Result |
-|---|---|
-| **FCC (US)** | ✅ **granted** — see §1 |
-| **CE / RED (EU)** | ⚠ No published DoC located; no `xteink.com` certification page exists. CE is self-declared; **there is no database to search** |
-| **CE mark on product** | ⚠ **Not determined** — the `ID Label` exhibits were downloaded but not visually inspected for secondary marks. **Open work** |
-| **UKCA** | ⚠ Not determined; no database exists |
-| **SRRC / CCC (CN)** | ❌ **Not searched** — `wireless.miit.gov.cn` and `srrccn.org` both failed to connect. **Not an absence finding** |
-| **MIC 技適 (JP)** | ⚠ **Not searched** — endpoint reachable, not queried |
-| **ISED (CA)** | ⚠ **Not searched** — `sms-sgs.ic.gc.ca` returned 503 |
-
----
-
-## 5. ⚠ Correction — this supersedes the 2026-09-04 finding
-
-[`VERIFICATION-sweep-2026-09-04.md`](../../../VERIFICATION-sweep-2026-09-04.md) §6 recorded:
-
-> **Certification and regulatory records** were checked only for Xteink (where the finding was
-> that no external CE/FCC marking exists on the devices at all). No positive control was run, so
-> the absence is weaker evidence than it looks.
-
-That self-doubt was justified. The original finding confused **"no mark visible in a product
-photograph"** with **"no grant exists"**. They are different claims and only the first was ever
-tested.
-
-- ✅ **Survives:** "no FCC ID is printed on the exterior of the units we photographed." Not
-  re-tested here, and may well still be true.
-- ❌ **Refuted:** any reading that Xteink devices are uncertified or unauthorised for the US.
-  **Xteink holds five granted Original Equipment authorisations.**
-
-47 CFR §2.935 permits an **e-label** displayed in software instead of a printed mark, which is
-the ordinary arrangement for a device with a screen. **That is a likely explanation and it was
-not verified.**
-
-The original sentences in the sweep report and in the Xteink records have **not been edited**.
-Dated corrections sit beneath them, and every one is listed in
-[`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
----
-
-## 6. What this does **not** establish
-
-- **No hardware was inspected.** No Xteink unit was obtained, opened or powered.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit.
-- **CE is not established.** No published Declaration of Conformity was located and **there is
-  no CE database to search** — CE is a self-declaration regime. Absence of a published DoC is
-  not absence of conformity.
-- **The `ID Label` exhibits were downloaded but not visually inspected for secondary marks.**
-  Whether a CE mark appears on Xteink label artwork is **open work**, and cheap to close.
-- **SRRC / CCC (CN) did not run.** `wireless.miit.gov.cn` and `srrccn.org` both failed to
-  connect (`000`) on 2026-09-11. That is a method failure, **not** an absence finding.
-- **MIC 技適 (JP) did not run.** The endpoint is reachable (200) but form-driven; not queried.
-- **ISED (CA) did not run.** `sms-sgs.ic.gc.ca` returned 503.
-- **Schematics are permanently withheld** on all five filings, along with block diagrams and
-  operational descriptions. **The FCC is not a route to an Xteink schematic.**
-
-
-## 7. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| XC-1 | FCC ID `2BTR9-X4PRO` record | US FCC via fccid.io | **primary (regulatory)**, via mirror | regulatory record | <https://fccid.io/2BTR9-X4PRO> | 2026-09-11 | Grant existence, date, frequencies, exhibit list, embargo dates |
-| XC-2 | FCC grantee index `2BTR9` | US FCC via fccid.io | primary via mirror | regulatory record | <https://fccid.io/2BTR9> | 2026-09-11 | The complete five-device Xteink certification history |
-| XC-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
-⚠ Deep `fccid.io` paths serve **403 to a Chrome User-Agent** and **200 to `curl/8.5.0`** — an *inverted* block. The honest UA works; the disguised one does not. The **root** `https://fccid.io/` returns 200 to everything, so a reachability probe against the root reports a false success. **Probe a deep path.**
diff --git a/devices/xteink/x4-pro/commands.md b/devices/xteink/x4-pro/commands.md
deleted file mode 100644
index 38c1ed2..0000000
--- a/devices/xteink/x4-pro/commands.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Xteink X4 Pro — command ledger
-
-Every command discovered or executed. **No command was executed against X4 Pro
-hardware** — none was available.
-
-## Executed successfully (research, not hardware)
-
-| # | Command | Purpose | Status |
-|---|---|---|---|
-| 1 | `curl -sSL -A "$UA" "https://www.xteink.com/products.json?limit=250&page=N" -o vendor/products-pN.json` | Vendor catalogue + live pricing | `executed-success` 2026-09-04 |
-| 2 | `curl -sSL -A "$UA" "https://www.xteink.com/collections/<handle>/products.json?limit=250"` | Per-line product membership | `executed-success` |
-| 3 | `curl -s -A "WhatsApp/2.23.20.0" "https://old.reddit.com/search.json?q=<q>&limit=100&sort=relevance&t=all"` | Community corpus. **200 on all 23 requests** | `executed-success` |
-| 4 | `curl -s -H "Authorization: Bearer $(gh auth token)" "https://api.github.com/search/repositories?q=xteink&per_page=100&page=N"` | Project census; token avoids the 60/h anonymous limit | `executed-success` |
-| 5 | `curl -sSL "https://imgur.com/ajaxalbums/getimages/<albumid>/hit.json"` | **Enumerate a full Imgur album** — the HTML page yields only 2 of 13 images | `executed-success` |
-| 6 | `python3 tools/archive_artifact.py --repo-root . --manifest <m>.json` | Archive bulky artifacts + write placeholders | `executed-success` |
-| 7 | `python3 tools/link_archived.py --apply` | Create the in-place archive symlinks | `executed-success` |
-
-### Failed, and the fix
-
-| # | Command | Failure | Diagnosis / fix |
-|---|---|---|---|
-| 8 | `curl -m 60 "http://web.archive.org/cdx/search/cdx?url=xteink.com*&limit=3000"` | `curl: (28) Operation timed out after 60000 ms with 0 bytes received` | CDX is slow on wildcard prefix queries. **Not retried.** Try a longer timeout, `matchType=prefix`, or paginate with `&limit=200&resumeKey=` | `executed-failed` |
-| 9 | `curl "https://xteink.cn/"` / `"https://xteink.net/"` | HTTP 000 | Hosts do not resolve/answer. **But `bofi.xteink.cn` appears inside the X4 firmware**, so a subdomain is live even though the apex is not | `executed-failed` |
-| 10 | `python3 tools/archive_artifact.py … ` (first attempt) | `AttributeError: 'str' object has no attribute 'get'` | The manifest's `source` field must be an **object**, not a string, and `notes` must be a **list**. Corrected manifest schema: `{path, reason, notes[], source:{repo,path_in_repo,author,retrieved,license,difficulty,access_notes,url,urls[{url,desc}]}}` | `executed-failed` → fixed |
-
-## Reported working (community, not executed here)
-
-| # | Command / procedure | Source | Status |
-|---|---|---|---|
-| 11 | `pio run -e x4pro` / `-t upload` | FreeInk `platformio.sample.ini` env exists | `reported-working` |
-| 12 | Flash a locked unit: drop `update.bin` on the SD root, **hold Power + Up at boot** | [r/XTEINK `1ult9dy`](https://old.reddit.com/r/XTEINK/comments/1ult9dy/) | `reported-working` — **author warns the button combo is unverified per unit** |
-| 13 | OTA-unlock a USB-locked stock device via crosspointreader.com | [r/xteinkereader `1tl3gnn`](https://old.reddit.com/r/xteinkereader/comments/1tl3gnn/) | `reported-working` |
-| 14 | Reflash from the web flasher if OTA fails: *"You can simply reflash from the website if you're unlocked or SD flash if you're locked"* | [r/XTEINK `1uek163`](https://old.reddit.com/r/XTEINK/comments/1uek163/) | `reported-working` |
-
-## Inferred (never executed, never reported — do not treat as authoritative)
-
-| # | Command | Note |
-|---|---|---|
-| 15 | `esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 read_flash 0 0x1000000 x4pro-stock-full.bin` | Standard 16 MB read. **Requires a USB-unlocked unit** |
-| 16 | `esptool.py --chip esp32s3 … write_flash 0 x4pro-stock-full.bin` | Restore. **There is no public X4 Pro image** — this only works with your own backup |
-| 17 | `python3 tools/esp_image_info.py <dump>.bin` | Parse the image. Helper already in this repo |
-| 18 | `pio device monitor -b 115200` | Serial log over native USB-CDC |
-
-## Build prerequisites
-
-```ini
-board = esp32-s3-devkitc1-n16r8
-board_build.mcu = esp32s3
-build_flags = -DBOARD_HAS_PSRAM -DFREEINK_DEVICE_X4PRO=1
-              -DUSE_BLOCK_DEVICE_INTERFACE=1   ; required for SD, in the consumer build
-```
-
-## Analysis commands used on the sibling X4 dump
-
-Reusable on any Xteink image; run against `x4-oem-flash.bin`:
-
-```python
-# executed-success 2026-09-04 — partition table at 0x8000
-for i in range(0, 0x1000, 32):
-    e = pt[i:i+32]
-    if e[:2] != b'\xAA\x50': break
-    off, size = struct.unpack('<II', e[4:12])
-    label = e[12:28].rstrip(b'\x00').decode()
-
-# executed-success — esp_app_desc_t at partition_offset + 0x20, magic 0xABCD5432
-# fields: version[32]@+16, project[32]@+48, time[16]@+80, date[16]@+96,
-#         idf_ver[32]@+112, elf_sha256[32]@+144
-```
diff --git a/devices/xteink/x4-pro/community.md b/devices/xteink/x4-pro/community.md
deleted file mode 100644
index 82ec238..0000000
--- a/devices/xteink/x4-pro/community.md
+++ /dev/null
@@ -1,108 +0,0 @@
-# Xteink X4 Pro — community reception
-
-> From 1,798 deduplicated Reddit posts retrieved **2026-09-04**. Evidence types:
-> **O** firsthand ownership · **M** firsthand measurement · **P** demonstrable
-> project · **I** informed interpretation · **Op** opinion · **H** hearsay.
-
-## Where the community is
-
-**Three** subreddits with confusingly similar names, plus one project sub:
-
-| Subreddit | Posts in corpus | Character |
-|---|---|---|
-| **r/XTEINK** | 416 | General; heaviest firmware-release traffic |
-| **r/xteinkereader** | 406 | General; heaviest owner-experience traffic |
-| **r/xteinkHax** | 180 | Hacking / firmware development |
-| r/CrossPointReader | 6 | Project-specific |
-
-Spillover into r/ereader (79), r/eink (17), r/EDC (18), r/writerDeck, r/dumbphones,
-r/PaperRepublic, r/Ultralight.
-
-**Searching one subreddit finds roughly a quarter of the material.** This is the
-most practically useful community finding.
-
-## The pogo-pin controversy — the defining X4 Pro thread
-
-[r/xteinkereader `1v2txxe`](https://old.reddit.com/r/xteinkereader/comments/1v2txxe/)
-and its r/XTEINK mirror, both 2026-07-21, **71 and 46 comments**:
-
-> "X4 Pro doesn't use USB-C for charging—it uses the magnetic pogo adapter. …
-> It's enough that I'll happily keep using my original X4 instead of upgrading.
-> … I'm hoping that whatever comes after the X4 Pro—maybe the S4 or another
-> future model—returns to USB-C."
-> — **O + Op**
-
-The poster pre-empts the counter-argument (*"Please don't try to convince me that
-the dongle is 'no big deal'"*), which tells you the argument was expected. This is
-a **firsthand ownership report of a design fact**, and the fact is confirmed
-independently by the vendor selling the adapter and cable as separate SKUs.
-
-**Prevalence not established.** One thread with 71 comments shows the topic is
-contested; it does not show what fraction of owners mind.
-
-## The X4 Classic was found by the community before it was announced
-
-[r/XTEINK `1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/),
-2026-06-22, **300 points**, 53 comments:
-
-> "Did we just spot a new X4 model? Physical buttons + frontlight but no
-> touchscreen in the latest video? … Could there actually be three devices shown
-> in the video? First the S4, then the X4 Pro and finally 2 devices placed in the
-> dock at the end. … The front buttons look identical to the X4, but I keep
-> noticing what looks like a button on the left side."
-> — **I** (informed interpretation of a vendor video)
-
-This predates the X4 Pro's 2026-07-21 listing and correctly identified a
-buttons-only S3 variant. The **frontlight** detail turned out to be wrong — the
-X4 Classic has none. A good illustration of community video-forensics being
-directionally right and specifically wrong.
-
-## Firmware ecosystem sentiment
-
-| Thread | Date | Signal |
-|---|---|---|
-| ["CrossPoint 1.5 has officially been released!"](https://old.reddit.com/r/xteinkereader/comments/1vhvtdd/) | 2026-08-07 | **763 pts, 305 comments.** The largest thread in the corpus. Includes the soft-brick warning for stale forks — **P + I** |
-| ["Tips after 1 Week and 2 Books"](https://old.reddit.com/r/XTEINK/comments/1uz8yiz/) | 2026-07-17 | **723 pts.** The de-facto onboarding post; names the three service sites — **O** |
-| ["To everyone who has donated to CrossPoint"](https://old.reddit.com/r/xteinkereader/comments/1tl3gnn/) | 2026-05-23 | 346 pts. OTA unlock for USB-locked devices — **P** |
-| ["If you're looking to get an X3/X4… support CrossPoint by buying from our site"](https://old.reddit.com/r/xteinkereader/comments/1uan67g/) | 2026-06-20 | 338 pts. **The vendor and the third-party firmware project have a commercial affiliate relationship**, and the vendor sells a "developer unlocked version" — a notably unusual posture for a Chinese consumer-hardware maker |
-| ["Microreader 2.0 (for Xteink X4)"](https://old.reddit.com/r/XTEINK/comments/1tqbcgu/) | 2026-05-28 | 514 pts. Note the emphasis: *"If you have an unlocked X4 (!!!UNLOCKED!!!)"* — **P** |
-
-## Vendor relationship — mixed
-
-The founder **"Crusoe"** introduced the company on r/ereader on 2025-10-09
-([`1o2203h`](https://old.reddit.com/r/ereader/comments/1o2203h/), **1,477 points**):
-*"I'm Crusoe, founder of Xteink, a small team based in Shenzhen."* — **O**
-
-But not all of it is warm. [r/XTEINK `1vrnxnq`](https://old.reddit.com/r/XTEINK/comments/1vrnxnq/)
-(2026-08-18, 24 pts), from a user who bought an X3 for **$16**:
-
-> "the double standard for different distribution channels and the official team's
-> negative attitude toward the community makes me seriously doubt whether I'll buy
-> the next S4."
-> — **O + Op**
-
-Same post, on firmware: *"I still flashed CrossMux onto it (a Chinese fork of
-CrossPoint that adds support for online sources like WeChat Read) … I'd honestly
-say 60% of my positive [experience]…"* — **the stock firmware is not what people
-value.**
-
-## Reliability
-
-[r/XTEINK `1utbw3v`](https://old.reddit.com/r/XTEINK/comments/1utbw3v/),
-2026-07-11, 81 pts, 50 comments: *"After less than 3 months, the device decided to
-self-destruct"* — a careful owner, never dropped, always cased. — **O**
-
-A second thread reports **cracked rear glass** on an X3
-([`1w56phf`](https://old.reddit.com/r/xteinkereader/comments/1w56phf/), 2026-09-02)
-and asks which models have metal backing rather than glass. **Unanswered.**
-
-**Two failure anecdotes across 1,798 posts establishes that failures occur.**
-It does not establish a failure rate, and should not be reported as one.
-
-## What the community does **not** have
-
-- **No X4 Pro teardown.** Repeatedly implied to exist (*"Fiche specs, teardowns,
-  and firmware guides are awesome"*) but no X4 Pro teardown was ever posted.
-- **No power measurements.** The one person who set out to make them
-  ([X3 teardown](../x3/media.md), Nordic PPK II) never posted results.
-- **No independent hardware documentation.** Everything traces to the FreeInk SDK.
diff --git a/devices/xteink/x4-pro/comparisons-and-recommendations.md b/devices/xteink/x4-pro/comparisons-and-recommendations.md
deleted file mode 100644
index 91b817e..0000000
--- a/devices/xteink/x4-pro/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,129 +0,0 @@
-# Xteink X4 Pro — comparisons and recommendations
-
-> Dated **2026-09-04**. Compares against records already in this knowledge base.
-> Prices are item-only, region-worldwide-from-Shenzhen unless stated.
-
-## The category confusion to avoid first
-
-The X4 Pro is a **sealed consumer product**. The PaperMono, Waveshare boards and
-ZeroWriter are **development platforms**. The community routinely compares them on
-price, and that comparison is close to meaningless:
-
-> "Half the price of the XTEINK X4 Pro"
-> — Hacker News on the PaperMono launch, recorded in
-> [`../../m5stack/papermono/comparisons-and-recommendations.md`](../../m5stack/papermono/comparisons-and-recommendations.md)
-
-A dev board has headers, a published schematic, USB-C, no unlock dance and no
-enclosure. A sealed reader has an enclosure, a battery, a case ecosystem and a
-locked bootloader. **Pick by what you are building, not by dollars per pixel.**
-
-Notably, the previous pass on the PaperMono recorded *"the XTEINK X4 Pro — the
-comparison the community actually makes — was never priced."* **It is now: $99.00
-as of 2026-09-04.** See [`market-and-pricing.md`](market-and-pricing.md).
-
-That pass also described the X4 Pro as *"a sealed consumer reader with locked-down
-firmware… **You cannot put your own application on it**"*. **That is now known to
-be wrong**, and this record supersedes it: the X4 Pro runs at least four
-independent open-source firmwares, the vendor sells a developer-unlocked variant,
-and USB-locked units can be unlocked over OTA or flashed from SD. See
-[`development.md`](development.md#usb-lock).
-
-## Against the rest of the Xteink family
-
-| | **X4 Pro** | [X4](../x4/README.md) | [X3](../x3/README.md) | [X4 Classic](../x4-classic/README.md) |
-|---|---|---|---|---|
-| SoC | **ESP32-S3** | ESP32-C3 | ESP32-C3 | **ESP32-S3** |
-| PSRAM | **8 MB** | none | none | **8 MB** |
-| Panel | 4.26″ 800×480 | 4.26″ 800×480 | 3.7″ 792×528 | 4.26″ 800×480 |
-| PPI | ~219 | ~219 | **~257** | ~219 |
-| Touch | **✅ GT911** | ✗ | ✗ | ✗ |
-| Frontlight | **✅ warm/cool** | ✗ | ✗ | ✗ |
-| Buttons | 2 + power | 6 + power (ADC ladder) | 6 + power (ADC ladder) | **6 + power (all discrete)** |
-| IMU | ✗ | ✗ | **✅ QMI8658** | **✅ QMI8658** |
-| RTC | BM8563 @0x51 | **none** | DS-series @0x68 | BM8563 @0x51 |
-| Gauge | CW2017 | none (ADC) | BQ27220 | CW2017 |
-| SD | **SDMMC 1-bit** | SPI (shared with display) | SPI (shared) | **SDMMC 1-bit** |
-| NFC | ✗ | ✗ | **✅ ISO 14443A tag** | ✗ |
-| Charging | **pogo only** | USB-C | pogo | not established |
-| Price | **$99** | delisted | $69 | not listed |
-
-**The three surprises in that table.** The "Pro" has **no IMU** while both cheaper
-siblings do; the X4 has **no RTC at all**; and the **X3 has the highest pixel
-density in the family** despite being the cheapest and smallest.
-
-## Against development platforms in this knowledge base
-
-| Device | Price (dated) | Class | Schematic | USB-C | Headers | Unlock needed | Verdict vs X4 Pro |
-|---|---|---|---|---|---|---|---|
-| **X4 Pro** | $99 (2026-09-04) | sealed reader | ✗ | data only | ✗ | often | — |
-| [M5Stack PaperMono](../../m5stack/papermono/README.md) | see its record | dev board | **✅ published** | ✅ | ✅ | ✗ | **Better for development.** Worse as a reader — no enclosure, no case ecosystem |
-| [Waveshare e-paper ESP32 boards](../../waveshare/) | varies | dev board | partial | ✅ | ✅ | ✗ | Cheapest route to a panel; you supply everything else |
-| [ZeroWriter](../../zerowriter/) | see its record | DIY appliance | ✅ open | ✅ | ✅ | ✗ | Different purpose — a writing appliance, keyboard-first |
-
-**Not equivalents, partial substitutes at most.** They share the "ESP32 driving
-e-paper" workload and nothing else: no shared enclosure, battery management, case
-ecosystem or panel size.
-
-## Against the S4 — the interesting one
-
-The [S4](../s4/README.md) is Xteink's own **Android 11** device: 2 GB RAM, 32 GB
-storage, 1400 mAh, 6.98 mm, 95 g, touch, warm/cool frontlight, at ~**¥339
-(≈US$50)** in China.
-
-On paper it beats the X4 Pro on every consumer axis at half the price. It is
-**not** a substitute if you intend to run your own firmware: it is a different
-platform with no FreeInk SDK support, no board profile, and no community firmware.
-**If you will never flash it, the S4 is probably the better buy** — and the
-community says so, e.g. *"I probably will abandon both once the S4 is released"*
-([r/xteinkereader `1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/), 412 pts).
-
-## Clones
-
-**None found.** No clone or white-label variant of any Xteink device was located
-in this session. Given the price point and Shenzhen origin this is mildly
-surprising and may simply reflect that Chinese marketplaces were not searched —
-see [`research-log.md`](research-log.md).
-
-## Recommendations by scenario
-
-| Scenario | Recommendation | Why |
-|---|---|---|
-| **Pocket reader you intend to reflash, want touch + light** | **X4 Pro**, 2026-09-04, $99 | Nothing else in the family or price bracket has both, with an active firmware scene |
-| Pocket reader, buttons are fine, want the sharpest text | **X3**, $69 | ~257 PPI, plus an IMU and NFC |
-| Pocket reader, buttons, want S3 power and an IMU | **X4 Classic** — **if you can buy one** | Not listed internationally |
-| **Building a product / need a schematic** | **PaperMono** or a Waveshare board | Published schematic, headers, USB-C, no unlock |
-| Want e-paper + Android + apps | **S4** | Different platform; no self-built firmware |
-| **Cannot tolerate a proprietary charging cable** | Not the X4 Pro. X4 (USB-C) if you can find one used | This is the single most common owner complaint |
-| Need an IMU on an S3 | X4 Classic, **not** the X4 Pro | The Pro has none |
-
-## Honest limits of this comparison
-
-- **No X4 Pro was measured.** No benchmark, power figure or runtime exists here or
-  anywhere found.
-- **Battery capacity is unknown**, so battery life cannot be compared at all.
-- PaperMono/Waveshare/ZeroWriter prices are not restated here because they were
-  captured on different dates; follow the links for dated figures.
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered.
-
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — the $30 touch-plus-frontlight premium priced against the rest of the family and
-  against the PaperMono, plus the group-level list of comparisons the evidence does
-  not support.
-- [**Xteink firmware ecosystem**](../firmware-ecosystem.md) — the X4 Pro as the
-  ecosystem's **design floor** and the **only target of the native-ELF plugin
-  fork**, with the full `VER (0x70)` / `FLG (0x71)` controller-detection procedure
-  and the `CHIP_VER = 0x00` negative result that must not be re-broken.
-- [**Adding LoRa, NFC and an RGB sidelight to e-ink firmware**](../../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-  — **the crux**: the native plugin host runs on this device, and its 81-symbol
-  allow-list contains **no I²C, no SPI, no GPIO, no ADC/PWM/LEDC, no Wi-Fi and no
-  filesystem**. Every radio or lighting capability therefore needs a firmware
-  change — but a small, structured one, not a fork of the reader.
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — what the 8 MB PSRAM here actually buys over the C3 siblings, and the pin cost
-  (**GPIO33–37 and `SPICS1` are consumed in-package**) of the `R8` variant.
diff --git a/devices/xteink/x4-pro/compatibility-and-status.md b/devices/xteink/x4-pro/compatibility-and-status.md
deleted file mode 100644
index de0098a..0000000
--- a/devices/xteink/x4-pro/compatibility-and-status.md
+++ /dev/null
@@ -1,94 +0,0 @@
-# Xteink X4 Pro — compatibility and status
-
-Keyed by firmware/SDK version where known. Snapshot **2026-09-04**.
-
-## Working — hardware-confirmed by the FreeInk maintainers
-
-At SDK commit `2400379` (2026-09-01), *"All peripherals are up"*:
-
-| Subsystem | Detail |
-|---|---|
-| Display | Paints with the plain X4 OTP waveform; no custom LUT, no PMIC |
-| Buttons | GPIO 0 / 7 / 3, digital active-low |
-| Frontlight | GPIO8 cool + GPIO9 warm, 25 kHz / 10-bit |
-| RTC | BM8563 @0x51 found and initialising |
-| SDMMC | 1-bit, mounts reliably with the GPIO5 power-cycle retry |
-| GT911 touch | Including the capacitive Home key |
-| CW2017 | Battery percentage, after BATINFO upload |
-
-## Partial
-
-| Item | State |
-|---|---|
-| **Panel orientation** | Ships `NO_FLIP`; mount transform pending hardware |
-| **Touch axis flip** | SDK header and SDK docs disagree — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md) |
-| **Deep-sleep power** | Rails driven off by polarity, but *"worth a power-draw check"* — never measured |
-| **BLE page-turners** | Work, but a fork exists specifically for *"validated reconnect support"*, implying default reconnect is unreliable |
-
-## Not working / not implemented
-
-| Item | State |
-|---|---|
-| **USB-MSC** ("USB Transfer") | Present in stock, **not ported** to the FreeInk SDK |
-| **`usbDetect` / VBUS sense** | Not identified. Stock uses the GPIO21 charge state instead |
-| **`batteryAdc`** | Not isolated |
-| **Grayscale** | 1 bpp only on this board |
-
-## Version-specific reports
-
-| Version | Report |
-|---|---|
-| CrossPoint **1.5** (2026-08-07) | Supports the new X3 display variants. Warns *"Other forks will need to pull the latest SDK to avoid soft bricking locked units"* |
-| CrossPoint **1.4.0** (2026-06-24) | X3 users hit OTA problems; project moved off GitHub releases due to X3 out-of-memory. Not X4 Pro-specific but the same OTA path |
-| Stock **7.4.4** (2026-08-27, IDF 6.0.1) | Uses the X4-compatible `0xFC` fast sequence |
-| Stock, **earlier image** | Used `0xC7` for fast — **a firmware that hard-codes one will misbehave on the other** |
-
-## Hardware-revision keyed
-
-**There is no published PCB revision scheme for the X4 Pro.** The only known
-hardware variation is the **panel controller** (SSD1677 / UC8179 / UC8279), which
-is invisible externally and is resolved at boot.
-
-Consequence: **compatibility claims cannot be keyed to a revision.** A firmware
-either carries all three drivers and the boot probe, or it is a lottery.
-
-## Conflicting reports
-
-None found between independent parties — because there is only **one** party
-producing board-level facts for this device (the FreeInk SDK). The conflicts that
-exist are **internal to that source**.
-
-That is itself a status finding: **this device's hardware documentation has no
-independent corroboration.** No teardown, no schematic, no regulatory filing.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 62:* independent corroboration.** No teardown, no schematic, no regulatory filing.
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-pro/coverage.md b/devices/xteink/x4-pro/coverage.md
deleted file mode 100644
index e90b377..0000000
--- a/devices/xteink/x4-pro/coverage.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Xteink X4 Pro — feature coverage
-
-Snapshot **2026-09-04**. "Tested" means tested by *someone*, cited; nothing was
-tested by this session.
-
-| Feature | Hardware | Official docs | Community evidence | Feature guide | HW-tested | Gaps |
-|---|---|---|---|---|---|---|
-| Display 800×480 | SSD1677 / UC8179 / UC8279 | **none** | FreeInk SDK, hardware-confirmed | [display](features/display.md) | ✅ by SDK authors | Panel module part; orientation |
-| Controller auto-detect | boot `VER`/`FLG` probe | none | SDK + observed `VER=00 00 01 FF FF` | [display](features/display.md) | ✅ | Whether a 4th controller exists |
-| Touch GT911 | 0x5D, INT10/RST4/PWR2 | none | SDK, hardware-confirmed | [touch](features/touch.md) | ✅ | `flipX`/`flipY` conflict |
-| Capacitive Home key | GT911 `0x814E & 0x10` | none | SDK, RE-confirmed vs OEM | [touch](features/touch.md) | ✅ | — |
-| Buttons (2 + power) | GPIO 0/7/3 | none | SDK, pull-up edge test | [buttons](features/buttons.md) | ✅ | — |
-| Frontlight warm/cool | GPIO8/9, LEDC 4/5 | none | SDK, hardware-confirmed | [frontlight](features/frontlight.md) | ✅ | Lux/CCT range unmeasured |
-| microSD (SDMMC 1-bit) | GPIO41/42/40 + EN5 | none | SDK, "CONFIRMED WORKING" | [storage](features/storage.md) | ✅ | Max card size untested |
-| Battery gauge | CW2017 @0x63 | none | SDK, hardware-confirmed | [battery](features/battery-and-power.md) | ✅ | **Capacity unknown** |
-| Charge status | GPIO21 active-HIGH | none | RE (`Cw2017PowerHal`) | [battery](features/battery-and-power.md) | ✅ | Charger IC part |
-| RTC BM8563 | 0x51 | none | SDK, "found and initializing" | [rtc](features/rtc.md) | ✅ | Backup power source |
-| USB-CDC | GPIO19/20 | none | SDK log transport | [usb](features/usb.md) | ⚠️ reported | — |
-| **USB-MSC** | GPIO19/20 | none | **in stock, not ported** | [usb](features/usb.md) | ❌ | Whole feature |
-| Wi-Fi | ESP32-S3 | none | inferred + sibling doc | [wifi/bt](features/wifi-and-bluetooth.md) | ❌ | Never demonstrated on this device |
-| BLE | ESP32-S3 | none | BLE page-turner forks exist | [wifi/bt](features/wifi-and-bluetooth.md) | ⚠️ reported | Reconnect reportedly fragile |
-| Deep sleep | rail polarity | none | SDK implemented | [battery](features/battery-and-power.md) | ❌ | **No current measurement** |
-| Pogo charging | magnetic | none | owner reports | [battery](features/battery-and-power.md) | ⚠️ | Pinout/voltage unknown |
-
-## Advertised but not fitted
-
-`NO_AUDIO`, `NO_LEDS`, `NO_MIC`, `ImuType::None`, no PMIC, no GPIO expander.
-**The X4 Pro has no IMU** even though the cheaper X3 and the X4 Classic do.
-
-## Combination scenarios — untested
-
-Nobody has reported, and this session did not test:
-
-| Combination | Concern |
-|---|---|
-| Display refresh **+** SD read | Both are DMA-heavy; SD uses a `MALLOC_CAP_DMA` bounce buffer |
-| Wi-Fi **+** frontlight PWM | LEDC + radio power draw on one battery |
-| Touch **+** RTC **+** gauge | All three on one `Wire` controller — a stalled bus blocks all |
-| BLE **+** Wi-Fi | One 2.4 GHz radio, shared |
-
-## Score
-
-**11 of 16** capabilities are hardware-confirmed by a citable third party.
-**0 of 16** were verified by this session.
diff --git a/devices/xteink/x4-pro/development.md b/devices/xteink/x4-pro/development.md
deleted file mode 100644
index 5fb97da..0000000
--- a/devices/xteink/x4-pro/development.md
+++ /dev/null
@@ -1,118 +0,0 @@
-# Xteink X4 Pro — development
-
-> Retrieval date **2026-09-04**. **No command in this document was executed
-> against an X4 Pro by this session — no hardware was available.** Every entry is
-> labelled `reported-working`, `inferred` or `not-tested`. Nothing here is
-> `executed-success`.
-
-## Toolchain and framework
-
-| Item | Value | Status |
-|---|---|---|
-| Framework | Arduino-ESP32 under **PlatformIO** | `reported-working` |
-| PlatformIO board | `esp32-s3-devkitc1-n16r8` — 16 MB flash + 8 MB PSRAM | `reported-working` **[SDK]** `platformio.sample.ini` |
-| MCU override | `board_build.mcu = esp32s3` | `reported-working` |
-| SDK | [FreeInk SDK](https://github.com/Free-Ink/freeink-sdk), consumed as a **git submodule** | `reported-working` |
-| Stock firmware toolchain | **ESP-IDF 6.0.1** (native, not Arduino) for 7.4.4 | **[DOC]** app descriptor |
-
-There is **no official vendor SDK, no vendor board-support package and no vendor
-documentation of any kind.** Every development path is community-built.
-
-## Required build flags
-
-```ini
-[env:x4pro]
-extends = base
-board = esp32-s3-devkitc1-n16r8   ; 16 MB flash + 8 MB PSRAM (matches the X4 Pro dump)
-board_build.mcu = esp32s3
-build_flags =
-  ${base.build_flags}
-  -DBOARD_HAS_PSRAM
-  -DFREEINK_DEVICE_X4PRO=1
-```
-
-Verbatim from `platformio.sample.ini` at commit `2400379`. `reported-working`.
-
-`-DFREEINK_DEVICE_X4PRO=1` auto-enables `FREEINK_DRIVER_SSD1677`,
-`FREEINK_DRIVER_UC8179`, `FREEINK_CAP_TOUCH` and `FREEINK_CAP_FRONTLIGHT`.
-
-**The SD path additionally needs `USE_BLOCK_DEVICE_INTERFACE=1` in the *consumer*
-build** — the `x4pro` env defines it; a hand-rolled env that forgets it will
-compile and then fail to mount the card. `reported-working` **[DOC]** line 16.
-
-## Build, flash, monitor
-
-```bash
-# not-tested by this session; the standard PlatformIO triple
-pio run -e x4pro
-pio run -e x4pro -t upload
-pio device monitor -b 115200
-```
-
-`inferred` — these are generic PlatformIO invocations, not quoted from any
-Xteink-specific source. The upload path depends entirely on whether the unit is
-**USB-locked** (below).
-
-## USB lock
-
-**This is the single most important thing to know before buying or flashing.**
-
-Many X4 Pro units — and X3/X4 units — **ship from the factory with USB flashing
-disabled**. `esptool` cannot see them. The community calls these "USB-locked"
-or "locked" units.
-
-| Path | What it does | Status |
-|---|---|---|
-| **CrossPointReader.com web flasher** | *"OTA Unlock usb locked stock devices by flashing CrossPoint and CrossInk"* | `reported-working` — [r/xteinkereader `1tl3gnn`](https://old.reddit.com/r/xteinkereader/comments/1tl3gnn/), 2026-05-23, 346 pts |
-| **SD-card update** | Drop `update.bin` on the SD root, hold **Power + Up** at boot; the **stock bootloader** picks it up and flashes it. No cable, no unlock | `reported-working` — [r/XTEINK `1ult9dy`](https://old.reddit.com/r/XTEINK/comments/1ult9dy/), 2026-07-02 |
-| **Developer-unlocked units** | Xteink sells an explicitly unlocked variant through CrossPoint's affiliate link | `reported-working` — [r/xteinkereader `1uan67g`](https://old.reddit.com/r/xteinkereader/comments/1uan67g/), 2026-06-20 |
-
-The SD path's author is candid about its risk: *"that path relies on
-stock-bootloader behavior I don't control, so confirm the button combo for your
-unit first."* Treat the button combination as **unverified per unit**.
-
-`OvermindDL1/xteink-unlocker` is a Tauri/Rust desktop application implementing the
-unlock; it carries a `com.sofriendly.crosspoint.unlocker.helper` privileged helper
-on macOS. Not inspected in depth this session.
-
-## Bricking risks
-
-| Risk | Mechanism | Mitigation |
-|---|---|---|
-| **Flashing a C3 image onto the S3** | Upstream CrossPoint release URLs point at C3 builds. CrossPlay had to repoint `OtaUpdater.cpp` specifically to avoid this | Verify the artifact names the S3 / `x4pro` |
-| **Wrong panel driver** | Newer batches carry UC8179/UC8279, not SSD1677. A firmware without those drivers leaves a blank screen | Use a firmware carrying all three; the boot probe selects |
-| **Stale fork on locked hardware** | CrossPoint 1.5 release notes: *"Other forks will need to pull the latest SDK to avoid **soft bricking locked units**"* — [r/xteinkereader `1vhvtdd`](https://old.reddit.com/r/xteinkereader/comments/1vhvtdd/), 2026-08-07 | Prefer forks synced to current SDK |
-| **OTA out-of-memory** | Reported on the X3; CrossPoint moved off GitHub releases because of it | Not X4 Pro-specific but the same OTA path |
-| **Probing GPIO19/20** | Native USB D−/D+. The C3 detect fingerprint pokes SDA20/SCL0, which here is D+ and a boot strap | `XteinkDetect` compiles that path out unless a C3 profile is in the build |
-| **Holding GPIO0 at reset** | It is the Left button *and* the boot strap | Do not power on with Left held unless you want download mode |
-
-**Being behind upstream is a brick-risk signal in this ecosystem, not a tidiness
-one** — the vendor revises hardware silently and upstream carries the fixes.
-
-## Debug access
-
-- **USB CDC** over the native USB peripheral. `FREEINK_LOG_TRANSPORT_USB_CDC_WRITE`
-  is a supported log transport **[SDK]** `InputManager.cpp:59`.
-- **No exposed UART header, no JTAG header, no test points documented.** No
-  teardown photograph of this device exists to check for pads.
-
-## Factory restore
-
-See [`factory-firmware.md`](factory-firmware.md). Short version: **make your own
-full-flash backup before you do anything**, because no X4 Pro stock image was
-located anywhere public in this session.
-
-## Known-good project starting points
-
-| Project | Why |
-|---|---|
-| [CrossPoint Reader](https://github.com/crosspoint-reader/crosspoint-reader) | Upstream; the reference |
-| [CrossInk](https://github.com/uxjulia/CrossInk) | The other major line; has an SDL simulator |
-| [CrossPlay](../../../software/applications/crossplay/README.md) | Analysed in this knowledge base; `x4pro` is its design floor |
-| [`MrStu82/crosspoint-llama-pro`](https://github.com/MrStu82/crosspoint-llama-pro) | Explicitly *"for the Xteink X4 Pro (ESP32-S3, GT911 touch, dual warm/cold frontlight)"* |
-| [`thepropm/proink-os`](https://github.com/thepropm/proink-os) | From-scratch firmware on the FreeInk SDK |
-
-## Related
-
-[`commands.md`](commands.md) · [`factory-firmware.md`](factory-firmware.md) ·
-[`pinouts-and-buses.md`](pinouts-and-buses.md)
diff --git a/devices/xteink/x4-pro/examples/best.md b/devices/xteink/x4-pro/examples/best.md
deleted file mode 100644
index 1023677..0000000
--- a/devices/xteink/x4-pro/examples/best.md
+++ /dev/null
@@ -1,145 +0,0 @@
-# Xteink X4 Pro — selected examples
-
-Snapshot **2026-09-04**. **None was built, flashed or run.** Statuses are
-`inferred` from source and repository metadata unless marked otherwise.
-
-## Why this portfolio looks unusual
-
-There is **no vendor SDK and no vendor sample code** for any Xteink device. The
-corpus is complete e-reader applications rather than per-feature demos, so this
-selection covers each **hardware path** by naming the project that best exercises
-it — plus the one project that is genuinely a minimal starting point, and two
-**negative examples** that document real failures.
-
-## The portfolio
-
-### 1. Best starting point — [`Free-Ink/freeink-sdk`](https://github.com/Free-Ink/freeink-sdk) @ `2400379`
-
-**Not an application — the HAL.** It is the correct first read for any X4 Pro work
-and the source of every hardware fact in this device record.
-
-Covers: display + three-controller auto-detect · GT911 touch · frontlight ·
-SDMMC · CW2017 · BM8563 · buttons · power rails · sleep.
-
-Why selected: `[env:x4pro]` exists and is maintained; `docs/xteink-x4pro-support.md`
-distinguishes **Confirmed on hardware / Corrected / Pending** per claim, which is
-rarer and more valuable than the code itself.
-
-Pitfall: it is a **submodule**, not a package. Consumers must also define
-`USE_BLOCK_DEVICE_INTERFACE=1` for SD.
-
-### 2. Best minimal consumer — [`Free-Ink/freeink-reader`](https://github.com/Free-Ink/freeink-reader)
-
-MIT · *"Minimal e-reader using the FreeInk SDK"* · last push 2026-07-08.
-
-The smallest thing that is a real application. Use it to see the SDK's
-initialisation contract without CrossPoint's 3,000-commit surface area.
-
-Caveat: **less actively maintained** than the mainlines, and no X4 Pro-specific
-claim is made.
-
-### 3. Best integrated application — [`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader)
-
-MIT · the reference implementation · `ROADMAP.md:40` lists X4 Pro among
-*"ESP32-S3 class hardware"* targets.
-
-Exercises every fitted capability in one program. Its **1.5 release notes** are
-also the best statement of the ecosystem's brick risks.
-
-### 4. Best distinct approach — [`uxjulia/CrossInk`](https://github.com/uxjulia/CrossInk)
-
-MIT · added an `x4pro` device type to its bug-report template on 2026-08-18 ·
-ships an **SDL simulator** ([`crossink-simulator`](https://github.com/uxjulia/crossink-simulator)).
-
-An independent lineage rather than a CrossPoint fork. **The simulator is the only
-way to exercise UI code in this ecosystem without hardware** — directly relevant
-here, where no hardware was available.
-
-### 5. Best X4 Pro-specific work — [`goodyttoor/inkback-freeink-sdk`](https://github.com/goodyttoor/inkback-freeink-sdk)
-
-MIT · *"InkMotion (PSRAM multi-buffer, damage windows, ghost budget) and **X4 Pro
-display work**"* · push 2026-08-18.
-
-The only project found that targets what actually distinguishes this device from
-the C3 models: **8 MB PSRAM**. Multi-buffering, damage windows and ghost budgeting
-are impossible on an X4/X3.
-
-### 6. Best fork-maintenance study — [`ma-r-s/crossplay`](https://github.com/ma-r-s/crossplay)
-
-MIT · [full record in this knowledge base](../../../../software/applications/crossplay/README.md).
-
-Selected for its `LOCAL_SCOPE.md`: an explicit, maintained accounting of every
-upstream file it touches and why. It names the **X4 Pro as the design floor**
-("two side keys plus touch") and documents the
-**C3-image-onto-S3 OTA hazard**.
-
-### 7. Non-reader use — [`vjFaLk/esphome-xteink`](https://github.com/vjFaLk/esphome-xteink)
-
-MIT · wraps the whole FreeInk SDK as an **ESPHome external component** under
-`components/xteink/sdk/`, for X4 / X3 / **X4 Pro**.
-
-The clearest demonstration that this is a general ESP32-S3 e-paper platform, not
-only a reader.
-
-### 8. From-scratch alternative — [`thepropm/proink-os`](https://github.com/thepropm/proink-os)
-
-*"a from-scratch e-reader firmware for the Xteink X4 Pro, built on the FreeInk
-SDK"* · push **2026-09-04** — the most recently active X4 Pro-specific project.
-
-Also relevant: [`MrStu82/crosspoint-llama-pro`](https://github.com/MrStu82/crosspoint-llama-pro),
-whose description independently corroborates the hardware profile —
-*"ESP32-S3, GT911 touch, dual warm/cold frontlight"*.
-
-### 9. **Negative example** — [`togotago/xteink-x4-escape`](https://github.com/togotago/xteink-x4-escape)
-
-MIT · *"Escape recipe for Xteink X4 e-readers stuck on CrossPoint Reader 1.2.0
-with OTA failing at `esp_ota_end()`"*.
-
-**A named, reproducible brick and its cure.** For the X4, not the Pro — but the
-OTA path is shared, and it is the only documented recovery recipe in the ecosystem.
-
-### 10. **Negative example** — [`lvturner/x4-dual-boot`](https://github.com/lvturner/x4-dual-boot)
-
-*"MicroSlate + CrossInk dual-boot for a **USB-locked** Xteink X4 (SD-card
-install)"*.
-
-Documents working around the factory USB lock — the constraint that shapes every
-first-time flashing experience in this family.
-
-### 11. Backup tooling — [`HomeAssistantPi/xteink-backup-utility`](https://github.com/HomeAssistantPi/xteink-backup-utility)
-
-MIT · *"Flash and Storage Utility for XTEINK / ESP32-S3. **Built for my XTEINK 4
-PRO**."* — the only X4 Pro-specific flash tool located. **Not inspected in depth.**
-
-## Feature coverage of the portfolio
-
-| Capability | Covered by | Gap |
-|---|---|---|
-| Display + 3-controller detect | 1, 3, 5 | — |
-| GT911 touch + Home key | 1, 3, 4 | — |
-| Frontlight warm/cool | 1, 3 | — |
-| Buttons | 1, 3 | — |
-| SDMMC | 1, 3 | — |
-| CW2017 battery | 1, 3 | — |
-| BM8563 RTC | 1, 3 | — |
-| Wi-Fi / BLE | 3, 7 | — |
-| **PSRAM multi-buffering** | **5 only** | — |
-| **USB-MSC** | **none** | **Uncovered.** In stock firmware, not ported to the SDK |
-| Deep-sleep power | 1 (implemented, unmeasured) | **No power figure exists** |
-| Flash / recovery | 9, 10, 11 | — |
-
-**Two genuine gaps: USB-MSC has no example anywhere, and no example demonstrates
-or measures sleep power.**
-
-## Nothing was vendored
-
-No example source is copied into this repository. Reasons: none is small enough to
-be a snippet; all are actively developed and a stale copy would mislead; and all
-are one `git clone` away at a pinned commit. Only the FreeInk SDK is held locally,
-in `scratch/eink-software/repos/freeink-sdk` at commit
-`24003795381a6c23630a26472ae3b06550333e71`, fetched by an earlier session.
-
-## Not validated
-
-**No example was built or statically validated.** No toolchain was installed. The
-honest status of every entry is `inferred`.
diff --git a/devices/xteink/x4-pro/examples/catalog.json b/devices/xteink/x4-pro/examples/catalog.json
deleted file mode 100644
index 82a8bca..0000000
--- a/devices/xteink/x4-pro/examples/catalog.json
+++ /dev/null
@@ -1,553 +0,0 @@
-{
-  "device": "xteink/x4-pro",
-  "generated": "2026-09-04",
-  "method": "GitHub repository search API (5 queries x 2 pages, authenticated) + code search + GraphQL discussions + 2,136 Reddit posts. NOTHING WAS BUILT, FLASHED OR RUN - no hardware was available. Every build_status is 'not-attempted' and every finding is 'inferred' from source/metadata unless stated.",
-  "examples": [
-    {
-      "id": "freeink-sdk",
-      "title": "Free-Ink/freeink-sdk",
-      "author": "Free-Ink project",
-      "source_class": "community",
-      "canonical_url": "https://github.com/Free-Ink/freeink-sdk",
-      "immutable_url": "https://github.com/Free-Ink/freeink-sdk/tree/24003795381a6c23630a26472ae3b06550333e71",
-      "commit": "24003795381a6c23630a26472ae3b06550333e71",
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-01",
-      "device": "Xteink X4 Pro (env x4pro)",
-      "hw_revision": "unknown",
-      "framework": "Arduino-ESP32 / PlatformIO",
-      "board": "esp32-s3-devkitc1-n16r8",
-      "features": [
-        "display",
-        "controller-autodetect",
-        "gt911-touch",
-        "frontlight",
-        "sdmmc",
-        "cw2017",
-        "bm8563",
-        "buttons",
-        "power-rails",
-        "sleep"
-      ],
-      "dependencies": [
-        "SdFat",
-        "Arduino-ESP32"
-      ],
-      "license": "unknown (LICENSE present, not read)",
-      "license_evidence": "LICENSE file exists in tree; contents not read this session",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Only authoritative hardware source for this device",
-        "Annotates each claim Confirmed-on-hardware / Corrected / Pending",
-        "Carries all three panel drivers plus the boot probe"
-      ],
-      "pitfalls": [
-        "Consumed as a git submodule, not a package",
-        "Consumer must define USE_BLOCK_DEVICE_INTERFACE=1 for SD"
-      ],
-      "lineage": "upstream",
-      "decision": "SELECTED - best starting point",
-      "local_path": "scratch/eink-software/repos/freeink-sdk"
-    },
-    {
-      "id": "freeink-reader",
-      "title": "Free-Ink/freeink-reader",
-      "author": "Free-Ink project",
-      "source_class": "community",
-      "canonical_url": "https://github.com/Free-Ink/freeink-reader",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-07-08",
-      "device": "Xteink family via SDK",
-      "hw_revision": "unknown",
-      "framework": "Arduino-ESP32 / PlatformIO",
-      "board": "per SDK env",
-      "features": [
-        "display",
-        "storage",
-        "reader-ui"
-      ],
-      "dependencies": [
-        "freeink-sdk"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Smallest real application on the SDK"
-      ],
-      "pitfalls": [
-        "Less actively maintained than the mainlines",
-        "Makes no X4 Pro-specific claim"
-      ],
-      "lineage": "independent",
-      "decision": "SELECTED - minimal consumer",
-      "local_path": null
-    },
-    {
-      "id": "crosspoint-reader",
-      "title": "crosspoint-reader/crosspoint-reader",
-      "author": "CrossPoint Reader project",
-      "source_class": "community",
-      "canonical_url": "https://github.com/crosspoint-reader/crosspoint-reader",
-      "immutable_url": "https://github.com/crosspoint-reader/crosspoint-reader/tree/e6139861a2a8c634aa18c333b7e214ee51a9965c",
-      "commit": "e6139861a2a8c634aa18c333b7e214ee51a9965c",
-      "tag": "1.5",
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-01",
-      "device": "X4 Pro listed in ROADMAP.md:40 as an ESP32-S3-class target",
-      "hw_revision": "unknown",
-      "framework": "Arduino-ESP32 / PlatformIO",
-      "board": "varies by env",
-      "features": [
-        "display",
-        "touch",
-        "frontlight",
-        "buttons",
-        "storage",
-        "battery",
-        "rtc",
-        "wifi",
-        "ble",
-        "ota"
-      ],
-      "dependencies": [
-        "freeink-sdk (submodule)"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Reference implementation",
-        "Exercises every fitted capability",
-        "1.5 release notes document ecosystem brick risks"
-      ],
-      "pitfalls": [
-        "ROADMAP listing is not shipped support",
-        "Upstream release URLs target C3 builds - flashing one onto an S3 is wrong"
-      ],
-      "lineage": "upstream",
-      "decision": "SELECTED - integrated application",
-      "local_path": "scratch/eink-software/repos/crosspoint-reader"
-    },
-    {
-      "id": "crossink",
-      "title": "uxjulia/CrossInk",
-      "author": "uxjulia",
-      "source_class": "community",
-      "canonical_url": "https://github.com/uxjulia/CrossInk",
-      "immutable_url": "https://github.com/uxjulia/CrossInk/tree/cab4f24922f05811e7f44be1057f62ea2d978c52",
-      "commit": "cab4f24922f05811e7f44be1057f62ea2d978c52",
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-18",
-      "device": "x4pro device type added to bug-report template 2026-08-18",
-      "hw_revision": "unknown",
-      "framework": "Arduino-ESP32 / PlatformIO",
-      "board": "varies",
-      "features": [
-        "display",
-        "touch",
-        "reader-ui",
-        "reading-stats"
-      ],
-      "dependencies": [
-        "freeink-sdk"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Independent lineage, not a CrossPoint fork",
-        "Ships an SDL simulator - the only way to exercise UI code without hardware"
-      ],
-      "pitfalls": [
-        "Less documented than CrossPoint"
-      ],
-      "lineage": "independent",
-      "decision": "SELECTED - distinct approach",
-      "local_path": "scratch/eink-software/repos/CrossInk"
-    },
-    {
-      "id": "inkback-freeink-sdk",
-      "title": "goodyttoor/inkback-freeink-sdk",
-      "author": "goodyttoor",
-      "source_class": "community",
-      "canonical_url": "https://github.com/goodyttoor/inkback-freeink-sdk",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-18",
-      "device": "Xteink X4 Pro (explicit)",
-      "hw_revision": "unknown",
-      "framework": "PlatformIO",
-      "board": "esp32-s3-devkitc1-n16r8",
-      "features": [
-        "psram-multibuffer",
-        "damage-windows",
-        "ghost-budget",
-        "display"
-      ],
-      "dependencies": [
-        "freeink-sdk (fork)"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "The ONLY project exercising what distinguishes the X4 Pro from the C3 models: 8 MB PSRAM"
-      ],
-      "pitfalls": [
-        "A fork of the SDK - carries the two-moving-upstreams problem"
-      ],
-      "lineage": "fork of Free-Ink/freeink-sdk",
-      "decision": "SELECTED - best X4 Pro-specific work",
-      "local_path": null
-    },
-    {
-      "id": "crossplay",
-      "title": "ma-r-s/crossplay",
-      "author": "Mario Alejandro Ruiz",
-      "source_class": "community",
-      "canonical_url": "https://github.com/ma-r-s/crossplay",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-02",
-      "device": "X4 Pro is the stated design floor",
-      "hw_revision": "unknown",
-      "framework": "Arduino-ESP32 / PlatformIO",
-      "board": "ESP32-S3",
-      "features": [
-        "display",
-        "touch",
-        "buttons",
-        "apps",
-        "games"
-      ],
-      "dependencies": [
-        "freeink-sdk (fork: x4pro-measured-insets)"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "LOCAL_SCOPE.md accounts for every upstream file touched",
-        "Documents the C3-image-onto-S3 OTA hazard",
-        "Already fully analysed in this knowledge base"
-      ],
-      "pitfalls": [
-        "Single author, bus factor 1",
-        "65 commits behind upstream at snapshot - a brick-risk signal in this ecosystem"
-      ],
-      "lineage": "fork of crosspoint-reader/crosspoint-reader",
-      "decision": "SELECTED - fork-maintenance study",
-      "local_path": "scratch/eink-software/crossplay",
-      "record": "software/applications/crossplay/README.md"
-    },
-    {
-      "id": "esphome-xteink",
-      "title": "vjFaLk/esphome-xteink",
-      "author": "vjFaLk",
-      "source_class": "community",
-      "canonical_url": "https://github.com/vjFaLk/esphome-xteink",
-      "immutable_url": "https://github.com/vjFaLk/esphome-xteink/tree/b36c09f2f3926c07aeb4b91ff4371db94037ef79",
-      "commit": "b36c09f2f3926c07aeb4b91ff4371db94037ef79",
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-02",
-      "device": "Xteink X4 / X3 / X4 Pro",
-      "hw_revision": "unknown",
-      "framework": "ESPHome",
-      "board": "varies",
-      "features": [
-        "display",
-        "non-reader-use",
-        "home-automation"
-      ],
-      "dependencies": [
-        "freeink-sdk (vendored under components/xteink/sdk/)"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Demonstrates the device as a general ESP32-S3 e-paper platform, not only a reader"
-      ],
-      "pitfalls": [
-        "Vendors the whole SDK - staleness risk"
-      ],
-      "lineage": "independent",
-      "decision": "SELECTED - non-reader use",
-      "local_path": null
-    },
-    {
-      "id": "proink-os",
-      "title": "thepropm/proink-os",
-      "author": "thepropm",
-      "source_class": "community",
-      "canonical_url": "https://github.com/thepropm/proink-os",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-09-04",
-      "device": "Xteink X4 Pro (explicit)",
-      "hw_revision": "unknown",
-      "framework": "PlatformIO",
-      "board": "ESP32-S3",
-      "features": [
-        "display",
-        "reader-ui"
-      ],
-      "dependencies": [
-        "freeink-sdk"
-      ],
-      "license": "unknown",
-      "license_evidence": "no license field returned by the API",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "From-scratch rather than a fork",
-        "Most recently active X4 Pro-specific project"
-      ],
-      "pitfalls": [
-        "New; maturity unknown",
-        "Licence unknown"
-      ],
-      "lineage": "independent",
-      "decision": "SELECTED - from-scratch alternative",
-      "local_path": null
-    },
-    {
-      "id": "xteink-x4-escape",
-      "title": "togotago/xteink-x4-escape",
-      "author": "togotago",
-      "source_class": "community",
-      "canonical_url": "https://github.com/togotago/xteink-x4-escape",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-05-10",
-      "device": "Xteink X4 (OTA path shared with X4 Pro)",
-      "hw_revision": "unknown",
-      "framework": "Python (host tool)",
-      "board": null,
-      "features": [
-        "recovery",
-        "ota"
-      ],
-      "dependencies": [
-        "esptool"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Documents a NAMED, reproducible brick (CrossPoint 1.2.0, OTA fails at esp_ota_end()) and its cure",
-        "The only published recovery recipe in the ecosystem"
-      ],
-      "pitfalls": [
-        "For the C3 X4, not the Pro - the OTA path is shared but the chip is not"
-      ],
-      "lineage": "independent",
-      "decision": "SELECTED - negative example",
-      "local_path": null
-    },
-    {
-      "id": "x4-dual-boot",
-      "title": "lvturner/x4-dual-boot",
-      "author": "lvturner",
-      "source_class": "community",
-      "canonical_url": "https://github.com/lvturner/x4-dual-boot",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-17",
-      "device": "USB-locked Xteink X4",
-      "hw_revision": "unknown",
-      "framework": "Shell + submodules",
-      "board": null,
-      "features": [
-        "sd-install",
-        "dual-boot",
-        "usb-lock-workaround"
-      ],
-      "dependencies": [
-        "MicroSlate",
-        "CrossInk"
-      ],
-      "license": "unknown",
-      "license_evidence": "no license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Documents working around the factory USB lock, the constraint shaping every first flash"
-      ],
-      "pitfalls": [
-        "Meta-repo of submodules; relies on stock-bootloader behaviour the author does not control"
-      ],
-      "lineage": "independent",
-      "decision": "SELECTED - negative example",
-      "local_path": null
-    },
-    {
-      "id": "xteink-backup-utility",
-      "title": "HomeAssistantPi/xteink-backup-utility",
-      "author": "HomeAssistantPi",
-      "source_class": "community",
-      "canonical_url": "https://github.com/HomeAssistantPi/xteink-backup-utility",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-10",
-      "device": "XTEINK 4 PRO (explicit, author's own)",
-      "hw_revision": "unknown",
-      "framework": "Shell (host tool)",
-      "board": null,
-      "features": [
-        "flash-backup",
-        "storage"
-      ],
-      "dependencies": [
-        "esptool"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "The only X4 Pro-specific flash/backup tool located"
-      ],
-      "pitfalls": [
-        "Not inspected in depth this session"
-      ],
-      "lineage": "independent",
-      "decision": "SELECTED - backup tooling",
-      "local_path": null
-    },
-    {
-      "id": "crosspoint-llama-pro",
-      "title": "MrStu82/crosspoint-llama-pro",
-      "author": "MrStu82",
-      "source_class": "community",
-      "canonical_url": "https://github.com/MrStu82/crosspoint-llama-pro",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-08-31",
-      "device": "Xteink X4 Pro (ESP32-S3, GT911 touch, dual warm/cold frontlight)",
-      "hw_revision": "unknown",
-      "framework": "Arduino-ESP32",
-      "board": "ESP32-S3",
-      "features": [
-        "display",
-        "touch",
-        "frontlight",
-        "reader-ui"
-      ],
-      "dependencies": [
-        "crosspoint-reader"
-      ],
-      "license": "MIT",
-      "license_evidence": "GitHub API license field",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Its description independently corroborates the hardware profile"
-      ],
-      "pitfalls": [
-        "A personal fork; no distinct technical contribution identified"
-      ],
-      "lineage": "fork of crosspoint-reader",
-      "decision": "CATALOGED - corroboration only",
-      "local_path": null
-    },
-    {
-      "id": "community-sdk",
-      "title": "crosspoint-reader/community-sdk",
-      "author": "CrossPoint Reader project",
-      "source_class": "community",
-      "canonical_url": "https://github.com/crosspoint-reader/community-sdk",
-      "immutable_url": "https://github.com/crosspoint-reader/community-sdk/tree/198ad267219c25c8ab84418b806c66f1fb5216a3",
-      "commit": "198ad267219c25c8ab84418b806c66f1fb5216a3",
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2026-06-24",
-      "device": "X3 grayscale preconditioning",
-      "hw_revision": "unknown",
-      "framework": "PlatformIO",
-      "board": null,
-      "features": [
-        "display",
-        "grayscale"
-      ],
-      "dependencies": [],
-      "license": "unknown",
-      "license_evidence": "LICENSE present, not read",
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [
-        "Grayscale preconditioning work"
-      ],
-      "pitfalls": [
-        "X3-focused, not X4 Pro"
-      ],
-      "lineage": "independent",
-      "decision": "CATALOGED - adjacent",
-      "local_path": "scratch/eink-software/repos/community-sdk"
-    },
-    {
-      "id": "os2world-openxp",
-      "title": "OS2World/APP-INTERNET-OpenXP",
-      "author": "OS2World",
-      "source_class": "community",
-      "canonical_url": "https://github.com/OS2World/APP-INTERNET-OpenXP",
-      "immutable_url": null,
-      "commit": null,
-      "tag": null,
-      "retrieved": "2026-09-04",
-      "last_activity": "2013-07-04",
-      "device": null,
-      "hw_revision": null,
-      "framework": null,
-      "board": null,
-      "features": [],
-      "dependencies": [],
-      "license": "unknown",
-      "license_evidence": null,
-      "build_status": "not-attempted",
-      "test_env": null,
-      "strengths": [],
-      "pitfalls": [
-        "NAME COLLISION: a 2013 OS/2 mail and news reader also called 'CrossPoint'. Unrelated to this ecosystem."
-      ],
-      "lineage": null,
-      "decision": "REJECTED - name collision",
-      "local_path": null
-    }
-  ],
-  "uncovered_features": [
-    "USB-MSC - present in stock firmware, not ported to the SDK, no example anywhere",
-    "Deep-sleep power measurement - implemented but never measured by any project"
-  ],
-  "vendored": [],
-  "vendoring_rationale": "No example source is copied into this repository. None is small enough to be a snippet; all are actively developed and a stale copy would mislead; all are one pinned-commit clone away. Only the FreeInk SDK is held locally, in scratch/eink-software/repos/freeink-sdk at 24003795381a6c23630a26472ae3b06550333e71 (fetched by an earlier session)."
-}
\ No newline at end of file
diff --git a/devices/xteink/x4-pro/examples/search-log.md b/devices/xteink/x4-pro/examples/search-log.md
deleted file mode 100644
index 6fa7e53..0000000
--- a/devices/xteink/x4-pro/examples/search-log.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# Xteink X4 Pro — example search log
-
-Snapshot **2026-09-04**. **No example was built, flashed or run** — no hardware.
-Every entry is cataloged from repository metadata and, where fetched, source text.
-
-## Where "examples" live for this device
-
-There is **no vendor SDK and no vendor example set.** Xteink publishes nothing:
-no datasheet, no board-support package, no sample code, no documentation.
-
-So the example corpus is entirely **community firmware**, and it has an unusual
-shape: instead of many small per-feature demos, it is a handful of **large,
-complete e-reader applications** plus a very long tail of forks that change UI
-details. Per-feature minimal examples barely exist.
-
-That shapes selection: [`best.md`](best.md) picks by **which project best
-demonstrates a given hardware path**, not by "smallest runnable demo".
-
-## Searches performed
-
-| Service | Query | Depth | Useful | Rejected |
-|---|---|---|---|---|
-| GitHub repo search | `xteink` | 2 pages / 378 total | many | forks, wallpaper tools |
-| GitHub repo search | `xteink x4` | 2 pages / 198 total | many | duplicates |
-| GitHub repo search | `crosspoint reader` | 2 pages / 105 total | many | non-Xteink `CrossPoint` (an OS/2 mail reader) |
-| GitHub repo search | `freeink` | 2 pages / 17 total | 4 | unrelated "FreeInk" web projects |
-| GitHub repo search | `crossink` | 2 pages | ~15 | simulators, wallpapers |
-| GitHub code search | `FREEINK_DEVICE_X4PRO`, `XTEINK_X4_PRO`, `xteink_x4_classic` | 100 each | board-profile consumers | — |
-| GitHub GraphQL | `crosspoint-reader` discussion #2259 | 1 | **1 — decisive on NFC** | — |
-| Reddit | 22 term queries + 6 subreddit sweeps + 8 full threads | 2,136 posts | project announcements | — |
-
-## Filtering
-
-~200 repositories mention the family. Of those:
-
-| Category | Count (approx) | Disposition |
-|---|---|---|
-| Complete firmware (mainline or substantial fork) | ~40 | **candidates** |
-| Personal/cosmetic forks | ~60 | rejected — no new hardware coverage |
-| Wallpaper / sleep-screen generators | ~25 | rejected — host-side, no device code |
-| Format converters (`.XTC`, EPUB, PDF) | ~20 | rejected — host-side |
-| Font tooling | ~10 | rejected — host-side |
-| Sync servers / OPDS / companion apps | ~20 | rejected — host-side |
-| Flashers and recovery tools | ~6 | **cataloged** — they exercise the flash path |
-| **X4 Pro-specific** | **6** | **all cataloged** |
-
-## Rejected candidates worth naming
-
-| Repo | Why rejected |
-|---|---|
-| `OS2World/APP-INTERNET-OpenXP` | A 2013 OS/2 mail reader also called "CrossPoint". **Name collision**, not this ecosystem |
-| `daviddivinefavour/freeInks`, `ranya-alhosan/FreeInk-React`, `hp-freeink/*` | Unrelated projects sharing the word "FreeInk" |
-| `Dirinkbottle/freeink` (2025-01) | Predates this ecosystem; unrelated |
-| Dozens of `crosspoint-reader` forks with no description and no divergence | No additional hardware coverage |
-
-## Inaccessible / not inspected
-
-| Item | Reason |
-|---|---|
-| `crossplay.ma-r-s.com`, `crosspointreader.com`, `crossink.uxj.io`, `brickclub.pages.dev`, `readme.club` | Community sites; **not fetched** this session |
-| `spokenlikeageek.com` Tong Card write-up | Not fetched |
-| Any binary release asset | Not downloaded — no hardware to flash |
-
-## Declared limits
-
-- **Nothing was built.** No toolchain was installed, no `pio run` was attempted.
-- Selection is by **source reading and repository metadata**, so every status
-  below is `inferred` unless the project itself claims otherwise.
-- Fork lineage is recorded where the API reports a parent; several personal forks
-  are standalone re-uploads and their lineage is stated as `unknown`.
diff --git a/devices/xteink/x4-pro/factory-firmware.md b/devices/xteink/x4-pro/factory-firmware.md
deleted file mode 100644
index 1cadd43..0000000
--- a/devices/xteink/x4-pro/factory-firmware.md
+++ /dev/null
@@ -1,224 +0,0 @@
-# Xteink X4 Pro — factory firmware
-
-> Retrieval date **2026-09-04**. **No X4 Pro stock image was located for
-> download.** Everything below about the stock firmware is read from the FreeInk
-> SDK's reverse-engineering notes, which were made against dumps the SDK authors
-> held privately.
-
-## Partition layout (16 MB, dual-OTA)
-
-| Label | Type | Subtype | Offset | Size |
-|---|---|---|---:|---:|
-| `nvs` | data | nvs | `0x009000` | `0x005000` (20 KiB) |
-| `otadata` | data | ota | `0x00E000` | `0x002000` (8 KiB) |
-| `app0` | app | ota_0 | `0x010000` | `0x7E0000` (8064 KiB) |
-| `app1` | app | ota_1 | `0x7F0000` | `0x7E0000` (8064 KiB) |
-| `spiffs` | data | spiffs | `0xFD0000` | `0x014000` (80 KiB) |
-| `coredump` | data | coredump | `0xFE4000` | `0x01C000` (112 KiB) |
-
-**[SDK]** `docs/xteink-x4pro-support.md` §Partitions.
-
-**This layout differs from the C3 X4's**, which uses 6400 KiB app slots and a
-3456 KiB spiffs. Do not assume one from the other — see
-[`../x4/factory-firmware.md`](../x4/factory-firmware.md).
-
-## The two-image trap
-
-The dump carries **two application images, and they are for different devices**:
-
-| Slot | Board tag | What it is |
-|---|---|---|
-| `app0` @ `0x10000` | `ESP32S3_X4_TL` | **A different variant.** Arduino-era, hardcoded pins |
-| `app1` @ `0x7F0000` | `XTEink X4 Pro` / `ESP32S3_X4_TL_SSD1677` | **The real firmware.** Native `esp_driver_sdmmc`, `XTEink::SSD1677_800x480`, `XTEink::GT911Driver`, `XTEink::EPDPanelInterface` |
-
-`otadata` selects **app1**.
-
-**Every early reverse-engineering pass read app0 and got a wrong pin map** — CS and
-DC swapped, SCLK/MOSI in the wrong order — which produced months of false
-conclusions about a nonexistent EPD power-management IC. If you dump an X4 Pro,
-**read otadata first and analyse the slot it actually selects.**
-
-## Known stock firmware versions
-
-| Version | Build date | Toolchain | Evidence |
-|---|---|---|---|
-| **7.0.8** | not recorded | — | Frontlight init passes 25 kHz / 10-bit **[SDK]** |
-| **7.0.11** | not recorded | — | The X4 **Classic** dump's app0 version, for comparison |
-| **7.4.4** | **2026-08-27** | **ESP-IDF 6.0.1** | App descriptor. OTA package labels itself `V7.4.5`; **the embedded app descriptor is authoritative** |
-
-**Conflict, recorded:** OTA package metadata says `V7.4.5` while the app descriptor
-inside says `7.4.4`. The SDK states the descriptor wins. Do not report the
-package label as the firmware version.
-
-The 7.4.4 OTA package filename is
-**`xteink_app_update_x4pro_7.4.4_20260827_133901.xota`**. The `.xota` extension
-implies a vendor-specific (probably encrypted) container — the SDK refers to *"the
-decrypted ESP32-S3 app"*, so decryption is required before analysis and the
-mechanism is **not documented anywhere found**.
-
-## OTA and network endpoints
-
-Recovered from the **X4 (C3)** dump, and reasonably assumed shared brand-wide but
-**not verified on an X4 Pro image**:
-
-| Endpoint | Role |
-|---|---|
-| `http://gotaserver.xteink.com/api/check-update` | OTA update check. **Plain HTTP** |
-| `http://bofi.xteink.cn/index.html` | On-device web file manager |
-
-Both are `inferred` for this device.
-
-## How to dump the stock firmware
-
-`inferred` — not executed. Requires a **USB-unlocked** unit (see
-[`development.md`](development.md#usb-lock)); a locked unit cannot be read at all.
-
-```bash
-# inferred — standard esptool full-flash read for a 16 MB ESP32-S3
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-           read_flash 0 0x1000000 x4pro-stock-full.bin
-sha256sum x4pro-stock-full.bin
-```
-
-Then parse it:
-
-```bash
-# inferred; the repo already ships a helper
-python3 tools/esp_image_info.py x4pro-stock-full.bin
-```
-
-Community tools that automate this:
-
-| Tool | Scope | Note |
-|---|---|---|
-| [`HomeAssistantPi/xteink-backup-utility`](https://github.com/HomeAssistantPi/xteink-backup-utility) | *"Flash and Storage Utility for XTEINK / ESP32-S3. Built for my XTEINK 4 PRO."* | The only X4 Pro-specific backup tool found |
-| [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher) | X3/X4 only — **not** the Pro | 1:1 full-flash backup & restore, ~2 min |
-
-## How to restore
-
-```bash
-# inferred — write a full-flash image back at offset 0
-esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 921600 \
-           write_flash 0 x4pro-stock-full.bin
-```
-
-**There is no public X4 Pro stock image to fall back on.** For the X3 and X4 there
-are community-hosted stock images; for the Pro there are none. **Your own backup
-is the only restore path.** Make one first.
-
-## Artifacts held
-
-**None.** Recorded honestly:
-
-| Wanted | Status |
-|---|---|
-| X4 Pro full-flash dump | **not located** — reacquisition `blocked` (nobody has published one) |
-| `xteink_app_update_x4pro_7.4.4_20260827_133901.xota` | **not located** — named in the SDK docs only; no download URL found |
-| Vendor OTA feed contents | **not fetched** — `gotaserver.xteink.com` not queried this session |
-
-Querying the OTA endpoint directly is the obvious next step and was **not done**;
-see [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-By contrast the **X4 (C3)** full-flash dump *was* obtained and is archived —
-see [`../x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md`](../x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md).
-It is a **different device** and cannot be flashed here, but it is useful for
-understanding the vendor's firmware conventions.
-
-## Recovered OEM display command streams
-
-Version-scoped, because the refresh sequence changed between releases:
-
-| Mode | X4 Pro 7.4.4 | Earlier X4 Pro image | X4 default | Sticky |
-|---|---|---|---|---|
-| Full | `0xF7` | `0xF7` | `0xF7` | `0xF7` |
-| Fast | **`0xFC`** | **`0xC7`** | `0xFC` | `0xFF` |
-
-7.4.4 routines: FULL at IROM `0x421e36ac`, FAST at `0x421e37b8`. Both set border
-`0x3C = 0xC0`, then update control `0x22`, then master activation `0x20`, then
-wait BUSY. **Neither touches the LEDC/frontlight path** — so the visible
-whole-panel light-then-dark flash during a FAST refresh is the electrophoretic
-waveform, not a frontlight change. That distinction has confused people.
-
-Earlier image, INIT at `0x4201a568`: SW RESET `0x12`, then a **fixed `delay(10)` —
-not a BUSY-wait**; temp sensor `0x18 = 0x80` (internal); booster
-`0x0C = AE C7 C3 C0 80`; driver output control `0x01 = DF 01 02` (gate lines
-`0x01DF` = 479 → MUX 480, `SM=1`); border `0x3C = 0x80`; RAM window via
-`0x11/0x44/0x45/0x4E/0x4F`, width `0x320` = 800, height `0x1E0` = 480.
-
-There is **no external EPD PMIC and no external charge pump.** The controller
-drives its high-voltage rails from its **internal booster** (`0x0C` soft-start).
-
-## Vendor-driver audit findings
-
-Reading the OEM code against the datasheets surfaced these, all recorded by the
-FreeInk maintainers:
-
-| Finding | Consequence | Severity |
-|---|---|---|
-| OEM clocks the panel at **5 MHz** when the SSD1677 is rated **20 MHz** for writes | ~4× slower RAM writes than necessary | Performance, not correctness |
-| OEM INIT uses a **fixed 10 ms delay instead of a BUSY-wait** after SW RESET | Works, but is a timing assumption rather than a handshake | Latent |
-| OEM ships a **4-threshold ADC button ladder matcher** (`0x4201f734`, BACK≈3580 / OK≈2728 / UP≈1514 / DOWN≈0, ±319) that **is not wired on this variant** | Dead code; misled RE into proposing an ADC ladder input that does not exist | Inert, but actively misleading |
-| **No GT911 config table anywhere** in app0, app1, spiffs or nvs | Confirms the OEM also relies on GT911 self-load; a firmware that uploads a config is doing something the vendor does not | Informational |
-| CW2017 reports 0% until an 80-byte BATINFO profile is loaded | Battery percentage silently wrong if the profile is missing | **Active** |
-
-## Related
-
-[`development.md`](development.md) ·
-[`features/display.md`](features/display.md) ·
-[`../x4/factory-firmware.md`](../x4/factory-firmware.md)
-
----
-
-## Round 2 — 2026-09-11: a hardware witness
-
-**No line above was altered.**
-
-A third party dumped a **physical retail X4 Pro** on 2026-09-06 and published the
-analysis (not the image — it is proprietary and contains the owner's Wi-Fi
-credentials). [`kycube/x4pro-emu`](https://github.com/kycube/x4pro-emu/tree/bf4b86ae0471012d4d07c0bb3042f3f561c9c302) @ `bf4b86a`.
-
-| Field | Value |
-|---|---|
-| Dump integrity | **two dumps, identical SHA-256** `90734554798da8dbe1961bf876a7bf44f2ea66a572ae2ed9b7ed395c9a0143fe` |
-| A later dump, post-CrossPoint | `326f3c8f066a8db7857d56d80eab755bba903eb3566245a985833b09e4c5bb20` |
-| Bootloader | ESP-IDF **v6.0.1** second-stage, built **2026-08-14 19:24:53**, entry `0x403c8870`, min rev v0.0 / max v0.99 |
-| `app0` @ `0x10000` | **`xteink_app` 7.2.4**, ESP-IDF v6.0.1, compiled **2026-08-14 19:25:05**, 8 segments, entry `0x40379908`, ELF SHA-256 `5e6f90d4…`, **hash valid** |
-| `app1` @ `0x7F0000` | **erased** (`0xFF`) |
-| `otadata` @ `0xE000` | entry 0 `seq=1 state=2 (VALID) crc=0x4743989a`; entry 1 erased → **`app0` boots** |
-| `spiffs` @ `0xFD0000` | 135 non-`0xFF` bytes in 80 KB — effectively empty |
-| `coredump` @ `0xFE4000` | erased |
-| **eFuse BLOCK3** | ASCII **`X4CB02EN26082416646`** — a factory serial |
-
-### Version conflict — now four numbers
-
-| Version | Where | Note |
-|---|---|---|
-| **7.2.4** | **a physical desk unit**, ESP-IDF v6.0.1, built 2026-08-14 | the only **hardware-read** version |
-| 7.4.4 | app descriptor | pre-existing, recorded above |
-| V7.4.5 | package metadata | pre-existing, recorded above |
-| 7.5.4 | a third-party analysis doc `docs/stock-7.5.4.md` | — |
-
-**Not reconcilable from public evidence.** The vendor publishes no changelog and
-ships regional (`hw_calib/region` 1 = CN, 2 = overseas) and OTA-staged builds.
-Recorded as a conflict, not resolved by preference.
-
-### NVS on a retail unit
-
-`xteink_sys` · `hw_calib` (**`screenType=2` → UC8279**, `region`, `lightDS`) ·
-`user_config` (`sta_ssid`, `sta_pwd`, `wifi_creds`, `cfg_init`, `fbLangDone`,
-`net_en`, `cloud_bind_st`, `otaPromptDay`, `pwrTimingVer`, `lightBri=100`,
-`lightCT=100`) · `misc` · `nvs.net80211` · `phy` (`cal_data`).
-
-`lightBri` and `lightCT` are direct evidence of a **dual-channel** frontlight
-with a colour-temperature control — corroborating the warm/cool pair from a
-completely different direction than the board profile.
-
-### Community install method, restated with its hazard
-
-The community installs CrossPoint by **writing only the app at `0x10000`** over
-the stock bootloader and stock partition table. That works precisely because the
-stock table already has an `otadata` partition and because `nvs` at `0x9000`
-survives — and `nvs` is where `hw_calib/screenType` lives. **Any procedure that
-erases the whole chip loses the panel identity.** On the X4 Pro the boot-time bus
-probe repairs that automatically; on the [X4 Classic](../x4-classic/factory-firmware.md)
-it cannot, because that board has no MISO.
diff --git a/devices/xteink/x4-pro/features/README.md b/devices/xteink/x4-pro/features/README.md
deleted file mode 100644
index 1e0cf64..0000000
--- a/devices/xteink/x4-pro/features/README.md
+++ /dev/null
@@ -1,20 +0,0 @@
-# Xteink X4 Pro — feature guides
-
-Task-oriented guides, one per fitted capability. Each answers "how do I use X on
-this device" and states its evidence status.
-
-| Guide | Capability | Evidence status |
-|---|---|---|
-| [`display.md`](display.md) | 800×480 e-ink, three possible controllers | hardware-confirmed (SDK) |
-| [`touch.md`](touch.md) | GT911 capacitive touch + capacitive Home key | hardware-confirmed (SDK) |
-| [`buttons.md`](buttons.md) | Two side keys + power | hardware-confirmed (SDK) |
-| [`frontlight.md`](frontlight.md) | Dual warm/cool PWM | hardware-confirmed (SDK) |
-| [`storage.md`](storage.md) | microSD via native SDMMC | hardware-confirmed (SDK) |
-| [`battery-and-power.md`](battery-and-power.md) | CW2017 gauge, charge STAT, rails, sleep | hardware-confirmed (SDK) |
-| [`rtc.md`](rtc.md) | BM8563 real-time clock | hardware-confirmed (SDK) |
-| [`usb.md`](usb.md) | Native USB-OTG, CDC, MSC | partial — MSC not ported |
-| [`wifi-and-bluetooth.md`](wifi-and-bluetooth.md) | ESP32-S3 Wi-Fi + BLE | inferred from SoC |
-
-**Not fitted, so no guide exists:** audio (no codec, no buzzer), LEDs, IMU,
-GPIO expander, PMIC, LoRa, camera, IR. The X4 Pro's `BoardProfile` sets
-`NO_AUDIO`, `NO_LEDS`, `NO_MIC` and `ImuType::None`.
diff --git a/devices/xteink/x4-pro/features/battery-and-power.md b/devices/xteink/x4-pro/features/battery-and-power.md
deleted file mode 100644
index 5e88f41..0000000
--- a/devices/xteink/x4-pro/features/battery-and-power.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# X4 Pro — battery and power
-
-> CW2017 I²C fuel gauge, a GPIO charge-status line, three power rails and a
-> pogo-pin charge connector. Evidence: hardware-confirmed except capacity.
-> Last verified 2026-09-04.
-
-## Capability summary
-
-| Item | Value |
-|---|---|
-| Fuel gauge | **CW2017** @ I²C **0x63** — [`cellwise/cw2017`](../../../../components/cellwise/cw2017/README.md) |
-| Charge status | **GPIO21**, **active-HIGH** = charging |
-| Battery ADC | **none** (`batteryAdc = PIN_UNASSIGNED`) |
-| VBUS / USB detect | **not conclusively identified** |
-| Charge connector | **magnetic pogo pins** — no USB-C charge port |
-| Capacity | **UNKNOWN** — no teardown, no vendor spec |
-| Charger IC | **not on the I²C bus**; part unidentified |
-
-## The CW2017 needs a battery profile or it lies
-
-**The CW2017 reports 0 % until an 80-byte BATINFO battery profile is loaded**
-into registers `0x10`–`0x5F`. `BatteryMonitor` verifies the resident profile and
-re-uploads the OEM table — recovered from app1's `Cw2017PowerHal` via Ghidra — if
-it is missing.
-
-Then:
-- **SoC** from register `0x04`
-- **VCELL** from registers `0x02`/`0x03`, 14-bit, `mV = (raw·5 + 8) >> 4`
-
-This is the highest-consequence software fact on this device's power path: a
-firmware that talks to the gauge without the profile shows a permanently flat
-battery.
-
-## Charging state is not observable from the gauge
-
-The CW2017 has **no current register**, and there is **no charger IC on the gauge
-bus**. Stock instead reads a **charger `STAT` line on GPIO21**, configured
-input/no-pull and read **active-HIGH** (raw level = charging).
-
-Evidence: `Cw2017PowerHal` vtable slot 3 → GPIO getter at IROM `0x4214f67c`,
-pin `0x15` (= 21) set in board init `0x4214eeb0`.
-
-`BatteryMonitor` falls back to this pin when the gauge reports charging as
-unobservable. Carried as `batteryChargeStatus = 21` +
-`batteryChargeStatusActiveHigh = true`.
-
-**The VBUS/USB-detect pin remains unidentified** — stock's battery icon uses the
-GPIO21 charge state, not a USB-presence signal.
-
-## Power rails and boot order
-
-| Rail | GPIO | Level | Role |
-|---|---:|---|---|
-| Master peripheral | **1** | HIGH | Asserted **first**. Panel + SD + touch depend on it |
-| Touch | **2** | **LOW** | Active-low. GT911 unpowered until LOW |
-| SD | **5** | **LOW** | Active-low. Pulse HIGH→LOW, hold LOW |
-
-Carried as `power.latch0 = {1}` so `holdPowerRails()` asserts GPIO1 early.
-Without it: *"EPD BUSY never asserts, SD returns 0xFF."*
-
-## Deep sleep
-
-The sleep path drives each enable to its **off level by polarity**, which on this
-board means driving GPIO2 and GPIO5 **HIGH**. Implemented, but the SDK notes a
-power-draw check is still **pending** — no measured sleep current exists.
-
-## The pogo connector
-
-The X4 Pro charges over a **magnetic pogo-pin connector**, not USB-C. Required
-accessories, both sold separately:
-
-| Accessory | Price (2026-09-04) |
-|---|---|
-| Magnetic Pogo Pin Charging Cable for X3 & X4 Pro | $4.99 |
-| Magnetic Charging Adapter for X3 & X4 Pro | $5.99 |
-
-This is the most-contested design decision in the product's community reception —
-71 comments on [r/xteinkereader `1v2txxe`](https://old.reddit.com/r/xteinkereader/comments/1v2txxe/).
-The native USB peripheral (GPIO19/20) still exists for data.
-
-## Unknowns
-
-- **Battery capacity.** The X3 is 650 mAh by teardown; the X4 Pro is unmeasured.
-- **Charger IC part number.** Not on I²C; the X3 uses a "TP4056-class" part per
-  its Chinese teardown, but that is a different board.
-- **Sleep current.** Never measured.
-- **Runtime.** No figure from any source.
-
-## Status
-
-`hardware-confirmed` for gauge, STAT pin and rails. `unknown` for capacity,
-charger part, current draw and runtime.
diff --git a/devices/xteink/x4-pro/features/buttons.md b/devices/xteink/x4-pro/features/buttons.md
deleted file mode 100644
index e494992..0000000
--- a/devices/xteink/x4-pro/features/buttons.md
+++ /dev/null
@@ -1,55 +0,0 @@
-# X4 Pro — buttons
-
-> Two physical navigation keys plus power. Everything else is touch.
-> Evidence: hardware-confirmed by a pull-up edge test. Last verified 2026-09-04.
-
-## Capability summary
-
-| Button | GPIO | Logical action | Polarity |
-|---|---:|---|---|
-| **Left** (side) | 0 | Up / previous page | active-LOW, `INPUT_PULLUP` |
-| **Right** (side) | 7 | Down / next page | active-LOW, `INPUT_PULLUP` |
-| **Power** | 3 | power | active-LOW (`powerActiveHigh = false`) |
-| **Home** | — | home | **GT911 capacitive key**, see [`touch.md`](touch.md) |
-
-`InputStyle::DigitalButtons`. Back and Confirm come from touch.
-
-## The corrected record
-
-An earlier revision of the FreeInk documentation described this device as having
-an **ADC resistor ladder** on GPIO10 with thresholds
-BACK ≈ 3580 / OK ≈ 2728 / UP ≈ 1514 / DOWN ≈ 0 (±319, raw 12-bit).
-
-**Hardware disproved it.** The ladder matcher at IROM `0x4201f734` is real code
-in the dump but is **vestigial firmware — not wired on this variant**. The device
-uses plain digital buttons. GPIO7 reads `INPUT_PULLUP`, which also confirms it is
-the Right button and **not** a display enable, another earlier hypothesis.
-
-This is recorded rather than deleted because the ladder *is* the input path on the
-[X3](../../x3/pinouts-and-buses.md) and [X4](../../x4/features/buttons.md), and
-somebody reading the shared firmware will meet it again.
-
-## Boot-strap warning
-
-**GPIO0 is the ESP32-S3 boot strap.** It works fine as a button provided it is not
-held during reset. Holding Left while powering on enters download mode.
-
-## Minimal use
-
-```c
-pinMode(0, INPUT_PULLUP);   // Left  -> up/prev
-pinMode(7, INPUT_PULLUP);   // Right -> down/next
-pinMode(3, INPUT_PULLUP);   // Power
-// pressed == LOW
-```
-`inferred` from the profile; the SDK's `InputManager` does this for you.
-
-## Why only two nav keys
-
-CrossPlay's `LOCAL_SCOPE.md` names the X4 Pro's "two side keys plus touch" as the
-ecosystem's **minimum viable input**, i.e. the design floor. A firmware that needs
-four nav keys will not work here without touch.
-
-## Status
-
-`hardware-confirmed`.
diff --git a/devices/xteink/x4-pro/features/display.md b/devices/xteink/x4-pro/features/display.md
deleted file mode 100644
index c0482f2..0000000
--- a/devices/xteink/x4-pro/features/display.md
+++ /dev/null
@@ -1,104 +0,0 @@
-# X4 Pro — display
-
-> 800×480 monochrome e-ink, 4.26″, ~219 PPI. **Three possible controllers.**
-> Evidence: hardware-confirmed via the FreeInk SDK. Last verified 2026-09-04.
-
-## Capability summary
-
-| Property | Value |
-|---|---|
-| Resolution | 800 × 480, native landscape scan |
-| Depth | **1 bpp black/white.** No grayscale path on this board |
-| Controller | **SSD1677** or **UC8179** or **UC8279**, batch-dependent |
-| Bus | 4-wire SPI, write-only (no MISO on the normal path) |
-| Clock | 20 MHz (FreeInk) · 5 MHz (OEM) |
-| Orientation | `NO_FLIP` — pending hardware confirmation |
-| Power | Controller's **internal booster** (`0x0C` soft-start). No PMIC, no charge pump |
-
-## Hardware path
-
-`ESP32-S3` → SCLK 12 / MOSI 11 / CS 13 / DC 18 / RST 14 / BUSY 6 → controller →
-glass. GPIO1 must be HIGH for the panel rail.
-
-Components: [`solomon-systech/ssd1677`](../../../../components/solomon-systech/ssd1677/README.md) ·
-[`ultrachip/uc8179`](../../../../components/ultrachip/uc8179/README.md) ·
-[`ultrachip/uc8279`](../../../../components/ultrachip/uc8279/README.md)
-
-## The controller lottery — and how to survive it
-
-**You cannot tell which controller a unit has without powering it on.** There is
-no external marking. The SDK solves this at boot:
-
-1. Bit-bang a half-duplex 4-wire SPI read on the display pins after a reset pulse.
-2. Issue `VER (0x70)` — 5 bytes — and `FLG (0x71)` — 1 byte.
-3. **The SSD-family does not answer these commands at all**, so a released SDA
-   line floats to a uniform `0x00` or `0xFF` through the pull-up.
-4. Match = `FLG` is neither `0x00` nor `0xFF`, has `BUSY_N` (bit0) set, **and**
-   `VER` is non-uniform. → UltraChip.
-5. Then `VER` byte 2 (`LUT_VER`) discriminates: `0x02`/`0x68`/`0x69` → **UC8279**;
-   anything else → **UC8179**.
-
-```c
-// freeink-sdk XteinkDetect.cpp:113-119, commit 2400379
-bool matchUc81xx(const uint8_t ver[5], uint8_t flg) {
-  if (flg == 0x00 || flg == 0xFF) return false;
-  if ((flg & 0x01) != 0x01) return false;
-  return !verIsFloating(ver);
-}
-```
-
-**A negative result worth keeping:** an earlier matcher required
-`ver[1] != 0`. A shipping X4 Pro UC8179 was then observed returning
-`VER = 00 00 01 FF FF` — `CHIP_VER` byte **`0x00`** — and was wrongly rejected.
-The matcher deliberately **does not pin any specific `CHIP_VER` value** now.
-Do not reintroduce that check.
-
-NVS `hw_calib/screenType` also records the panel type, **but the SDK reads it for
-diagnostics only** and never decides on it: a full-flash from another unit
-overwrites it, so it can name the wrong panel. (The X4 **Classic** is the
-exception — it has no MISO at all and NVS is its only source of truth.)
-
-## Refresh modes
-
-| Mode | Update-control byte (7.4.4) |
-|---|---|
-| Full | `0x22 = 0xF7` |
-| Fast / partial (DU) | `0x22 = 0xFC` |
-
-Both then issue master activation `0x20` and wait BUSY. Border is set
-`0x3C = 0xC0` first.
-
-**A visible whole-panel light-then-dark transition during FAST is the
-electrophoretic waveform, not the frontlight.** The refresh routines never call
-the LEDC path.
-
-## Minimal procedure
-
-Use the SDK; do not hand-roll. `-DFREEINK_DEVICE_X4PRO=1` links all three drivers
-and `applyXteinkDisplayController()` selects at boot.
-
-## Limits and pitfalls
-
-| Limit | Kind | Note |
-|---|---|---|
-| 20 MHz SPI write | **silicon** | SSD1677 datasheet max for write mode |
-| 40 MHz | **out of spec** | The `Ssd1677Driver` 0-default is 40 MHz; boards leaving `displaySpiHz = 0` run out of spec |
-| ~38 ms/refresh plane write @20 MHz | **measured, on the X4** | Same controller; treat as indicative here |
-| 1 bpp only | **board** | No grayscale banks tuned for this device |
-| Bezel insets `{9,7,3,7}` | **board** | Without them, screens draw under the glass |
-
-**Pitfall — the app0 pin map.** If you derive pins from a dump, confirm which
-app slot `otadata` selects. app0 is a *different variant* and its map is wrong
-here. See [`../factory-firmware.md`](../factory-firmware.md).
-
-## Debugging
-
-The probe logs `[XTDET] bus probe VER=… FLG=… -> UltraChip|default|inconclusive`
-over serial, plus the MTP header (`RMTP 0xA2`) when the status line was driven —
-`0xA5` at byte 0 means a UC part with a programmed MTP.
-
-## Status
-
-`hardware-confirmed` — *"the panel WORKS… it paints normally using the plain X4
-OTP waveform, no custom LUT, no explicit voltages, no PMIC, no GPIO
-power-enable."* **Open:** panel mount orientation.
diff --git a/devices/xteink/x4-pro/features/frontlight.md b/devices/xteink/x4-pro/features/frontlight.md
deleted file mode 100644
index 4026b26..0000000
--- a/devices/xteink/x4-pro/features/frontlight.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# X4 Pro — frontlight (dual warm/cool)
-
-> Two-channel colour-temperature LED frontlight. **Unique to the X4 Pro** in the
-> ESP32 Xteink family. Evidence: hardware-confirmed. Last verified 2026-09-04.
-
-## Capability summary
-
-| Channel | GPIO | Colour | LEDC channel |
-|---|---:|---|---:|
-| `frontlight.gpio` | **8** | cool / white | 4 |
-| `frontlight.gpioWarm` | **9** | warm | 5 |
-
-Both **active-HIGH** — driving a pin high lights that LED; init drives it LOW
-(off) and brightness raises duty.
-
-Config: `FrontlightConfig{8, 25000, 10, true, 9}` — **25 kHz, 10-bit**.
-
-## API
-
-`FrontlightManager` mixes the two channels:
-- `setBrightness()` — total level
-- `setColorTemperature()` — warm/cool split
-
-Stock persists the state in NVS as `lightWarmValue`, `lightColdValue`, `lightCT`,
-`lightBri`, `lightOn`.
-
-## A version conflict, resolved
-
-| Source | Frequency | Resolution |
-|---|---|---|
-| Original board bring-up dump | **10 kHz** | — |
-| Stock **7.0.8** | **25 kHz** | 10-bit |
-
-Same GPIO pair, same active-high polarity. The SDK follows the **directly
-recovered 7.0.8 value (25 kHz / 10-bit)**. This PWM change is independent of the
-panel-waveform change between firmware versions — do not conflate them.
-
-## Resource conflicts
-
-LEDC channels 4 and 5 are reserved. On the **X4 Classic**, GPIO8 and GPIO9 are
-**button inputs**, so code that unconditionally configures them as PWM outputs
-will break that device — always gate on `FREEINK_CAP_FRONTLIGHT`.
-
-## Pitfall
-
-A whole-panel light-then-dark flash during a fast page turn is **the e-ink
-waveform, not the frontlight**. The refresh routines never touch LEDC. See
-[`display.md`](display.md).
-
-## Status
-
-`hardware-confirmed` — *"driving each pin high lights that LED"*, identities
-"nailed down".
diff --git a/devices/xteink/x4-pro/features/rtc.md b/devices/xteink/x4-pro/features/rtc.md
deleted file mode 100644
index ec74150..0000000
--- a/devices/xteink/x4-pro/features/rtc.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# X4 Pro — real-time clock
-
-> BM8563 on the shared I²C bus. Evidence: hardware-confirmed. 2026-09-04.
-
-| Property | Value |
-|---|---|
-| Part | **BM8563** — PCF8563 **register-compatible** |
-| Component | [`generic/bm8563`](../../../../components/generic/bm8563/README.md) |
-| Address | **0x51** |
-| Bus | SDA 39 / SCL 38 @ 400 kHz, controller 0 (`Wire`) |
-| SDK type | `RtcType::Pcf8563` |
-| Class in OEM dump | `XTEink::BM8563Driver` |
-| Driver init | IROM `0x420a2834` — adds device 0x51; bus object configured `{39, 38, 400000}` |
-
-Confirmed **found and initializing on hardware**.
-
-**BM8563 is not PCF8563.** It is a separate part (originally Holtek/BesTek
-lineage, widely used by M5Stack) that is register-compatible with the PCF8563.
-Driving it with a PCF8563 driver works; calling it a PCF8563 in a bill of
-materials does not.
-
-Note the family split: the X4 Pro and X4 Classic use the **BM8563 at 0x51**,
-while the [X3](../../x3/features/rtc.md) uses a **DS-series RTC at 0x68** and the
-[X4](../../x4/README.md) has **no RTC at all**. Four devices, three different
-answers.
-
-## Backup power
-
-Not established. No teardown exists to check for a supercap or coin cell, and the
-firmware does not reveal it.
-
-## Status
-
-`hardware-confirmed` for presence, address and initialisation.
diff --git a/devices/xteink/x4-pro/features/storage.md b/devices/xteink/x4-pro/features/storage.md
deleted file mode 100644
index 029670f..0000000
--- a/devices/xteink/x4-pro/features/storage.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# X4 Pro — microSD storage
-
-> Native SDMMC, 1-bit. **Not SPI** — an SPI card path can never work on this
-> board. Evidence: hardware-confirmed. Last verified 2026-09-04.
-
-## Capability summary
-
-| Signal | GPIO |
-|---|---:|
-| CLK | **41** |
-| CMD | **42** |
-| DAT0 | **40** |
-| power enable | **5** — **ACTIVE-LOW** |
-
-Slot 1, 1-bit, internal pull-ups, 40 MHz. DAT1/2/3 unused.
-Driver: `esp_driver_sdmmc` via `SdmmcBlockDevice`.
-Component: [`generic/micro-sd-sdmmc`](../../../../components/generic/micro-sd-sdmmc/)
-
-## Build requirement
-
-`FREEINK_SD_SDMMC` auto-enables with `-DFREEINK_DEVICE_X4PRO=1`, **but the
-consumer build must also define `USE_BLOCK_DEVICE_INTERFACE=1`** — SdFat needs its
-generic block-device interface for the `FsVolume` mount. The `x4pro` env defines
-it; a hand-rolled env that omits it compiles and then fails to mount.
-
-## The mount sequence — both steps are required
-
-From the OEM `mountSD`, reproduced in `SdmmcBlockDevice::begin`:
-
-1. **Power-cycle GPIO5 and retry the WHOLE mount.** Before each attempt, pulse
-   GPIO5 HIGH (80 ms) → LOW (120 ms), then run `sdmmc_card_init` **and a real
-   sector-0 read**.
-   *Why:* retrying only `card_init` leaves SdFat's first, un-retried block read to
-   hit a still-marginal data path and fail with
-   `sdmmc_read_sectors_dma … 0x107`. Validating a real read before publishing the
-   card means the retry actually covers block I/O.
-2. **Leave GPIO5 LOW.** Driving it HIGH after init — an earlier misreading of the
-   OEM — breaks **every** subsequent read with `0x107`. It must stay in the state
-   the validated read succeeded under.
-
-## DMA buffering
-
-Reads and writes bounce through a `MALLOC_CAP_DMA` buffer, because SdFat's caches
-may live in **PSRAM** or be unaligned. This is a real constraint on an 8 MB-PSRAM
-board and is easy to get wrong.
-
-## Sleep
-
-The enable is active-LOW, so the sleep path drives GPIO5 **HIGH** to cut the card.
-`powerActiveHigh = false` makes `powerDownRailsForSleep()` do this by polarity.
-
-## Pitfalls
-
-| Symptom | Cause |
-|---|---|
-| Card silent to CMD0 | You are trying SPI mode. Use SDMMC |
-| Every read fails `0x107` | GPIO5 held HIGH |
-| First read after mount fails | Retrying `card_init` only, not the full mount |
-| Mounts but data corrupt | Missing the DMA bounce buffer |
-
-## Status
-
-`hardware-confirmed` — *"CONFIRMED WORKING on hardware."*
diff --git a/devices/xteink/x4-pro/features/touch.md b/devices/xteink/x4-pro/features/touch.md
deleted file mode 100644
index d58b7fb..0000000
--- a/devices/xteink/x4-pro/features/touch.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# X4 Pro — touch (GT911)
-
-> Capacitive digitizer plus a capacitive Home key. **The only Xteink ESP32 device
-> with touch.** Evidence: hardware-confirmed. Last verified 2026-09-04.
-
-## Capability summary
-
-| Property | Value |
-|---|---|
-| Controller | **GT911** — [`goodix/gt911`](../../../../components/goodix/gt911/README.md) |
-| Bus | I²C SDA 39 / SCL 38 @ 400 kHz, shared with RTC + gauge |
-| Address | **0x5D** (alt 0x14) |
-| INT | GPIO **10** |
-| RST | GPIO **4** |
-| Power enable | GPIO **2**, **ACTIVE-LOW** |
-| Mounting | **Portrait sensor on a landscape panel** → `swapXY = true` |
-| Home key | GT911 key bit, status `0x814E & 0x10` |
-
-## Three non-obvious things, each of which leaves the controller totally silent
-
-The FreeInk bring-up notes are unusually explicit that **each of these
-independently produced "no ACK on the bus"**:
-
-1. **The rail is gated by GPIO2 and it is ACTIVE-LOW.** The OEM drives GPIO2
-   **LOW** (with GPIO1 HIGH) at boot. Driving GPIO2 *high* — the naive "enable" —
-   keeps the GT911 unpowered. An idle scan then shows only 0x51 and 0x63.
-2. **RST = GPIO4, INT = GPIO10.** An earlier RE had these two reversed, which is
-   why the first hardware attempt failed.
-3. **The reset must be long enough.** The GT911 loads its own internal config on
-   the standard reset dance; a too-short reset skips the load and the config
-   registers read back all-zero. The SDK uses 10 ms / 10 ms / 50 ms / 50 ms with
-   INT→INPUT.
-
-**There is no GT911 config table anywhere in the OEM dump** (app0, app1, spiffs
-or nvs), so the vendor relies on self-load too. Do not upload a config.
-
-## Reset dance and addressing
-
-```
-RST LOW, INT driven to select level      → 2 ms
-RST HIGH                                  → 8 ms
-INT to INPUT + pull                       → 60 ms
-probe
-```
-
-INT level as RST rises selects the address: **LOW → 0x5D**.
-
-## Reading points
-
-| Register | Meaning |
-|---|---|
-| `0x814E` | bit7 = data ready; low nibble = point count; **bit4 (`0x10`) = Home key** |
-| `0x8150` | first point, 8 bytes per point |
-
-**`gt911CoordsAtByte0 = true`** — coordinates start at **byte 0**, not byte 1.
-The datasheet-standard layout puts a track-id first; this panel does not. Getting
-this wrong shifts every coordinate by one byte and produces garbage.
-
-## Orientation
-
-The digitizer reports **X: 0–480, Y: 0–800** on an 800×480 landscape panel.
-`swapXY` is applied first, then per-axis flip; `rawMinX/rawMaxX` describe the
-**post-swap** axes.
-
-**Unresolved:** the board profile sets `flipY = true` and comments *"confirmed by
-corner-tap"*, while `docs/xteink-x4pro-support.md` says in two places that
-`flipX`/`flipY` are still **pending** a corner-tap test. See
-[`../gaps-and-conflicts.md`](../gaps-and-conflicts.md). Taps register and
-navigate either way; only mirroring is at stake.
-
-## Home key
-
-Surfaced as `InputManager::wasHomeKeyPressed()` when
-`touch.hasHomeKey = true`. RE-confirmed that the OEM keys off exactly
-`0x814E & 0x10`. It is **not a GPIO** — do not look for one.
-
-## Resource conflicts
-
-Shares one Arduino `Wire` controller with the BM8563 and CW2017. Also note GPIO10
-is listed elsewhere as a *candidate* for `usbDetect`; it is already the touch INT,
-so that candidacy should be treated as almost certainly wrong.
-
-## Status
-
-`hardware-confirmed` — *"Touch wiring in the SDK profile: touch.powerEnable =
-GPIO2 (active-low), INT=10/RST=4, swapXY = true, gt911CoordsAtByte0 = true, no
-config upload."* **Open:** axis flip (documentation conflict).
diff --git a/devices/xteink/x4-pro/features/usb.md b/devices/xteink/x4-pro/features/usb.md
deleted file mode 100644
index e704b5f..0000000
--- a/devices/xteink/x4-pro/features/usb.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# X4 Pro — USB
-
-> ESP32-S3 native USB-OTG. Data only — **charging is over pogo pins.**
-> Evidence: SDK-stated; MSC not ported. 2026-09-04.
-
-| Signal | GPIO |
-|---|---:|
-| D− | **19** |
-| D+ | **20** |
-
-Native ESP32-S3 USB peripheral, no external bridge IC.
-
-## What stock does
-
-- **USB-CDC** serial.
-- **USB-MSC** — "USB Transfer", exposing the SD card as a mass-storage device.
-
-## What FreeInk does
-
-CDC yes; **USB-MSC is present in stock firmware but has not been ported** to the
-SDK. Listed as pending/optional. If you need SD-over-USB, you are writing it.
-
-`FREEINK_LOG_TRANSPORT_USB_CDC_WRITE` is a supported log transport.
-
-## Hard warning
-
-**Never run an I²C or GPIO probe across GPIO19/20 at boot.**
-
-The Xteink **C3** X3/X4 detect fingerprint pokes SDA 20 / SCL 0. On this **S3**
-those land on **D+ and a boot strap**. This is precisely why `XteinkDetect`
-compiles the C3 fingerprint to a no-op unless a C3 profile is in the build:
-
-```c
-// XteinkDetect.cpp:19, commit 2400379
-#define FREEINK_XTEINK_C3 (FREEINK_DEVICE_X4 || FREEINK_DEVICE_X3)
-```
-
-A build that defines both a C3 and the X4 Pro profile would be dangerous.
-
-## USB detect
-
-`usbDetect = PIN_UNASSIGNED`. GPIO10 is floated in the SDK as a candidate but is
-**unconfirmed** — and GPIO10 is already the GT911 INT, so treat that candidacy as
-almost certainly wrong. Stock's battery icon uses the GPIO21 charge state instead.
-
-## Status
-
-`reported-working` for CDC. `not-ported` for MSC. `unknown` for VBUS detect.
diff --git a/devices/xteink/x4-pro/features/wifi-and-bluetooth.md b/devices/xteink/x4-pro/features/wifi-and-bluetooth.md
deleted file mode 100644
index 57db81e..0000000
--- a/devices/xteink/x4-pro/features/wifi-and-bluetooth.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# X4 Pro — Wi-Fi and Bluetooth
-
-> ESP32-S3 integrated radios. **This is the weakest-evidenced guide in this
-> device record** — see status. 2026-09-04.
-
-## Capability summary
-
-| Radio | Status |
-|---|---|
-| Wi-Fi 2.4 GHz b/g/n | Present (ESP32-S3 integrated) |
-| Bluetooth LE 5 | Present (ESP32-S3 integrated) |
-| Bluetooth Classic | **Not available** — the ESP32-S3 has no BR/EDR radio |
-| Antenna | **Not characterised.** No teardown, no FCC filing |
-
-## Evidence status — read this first
-
-The X4 Pro `BoardProfile` says nothing about radios; the SDK simply relies on the
-SoC. The **X4 Classic** doc states plainly *"WiFi and BLE radios are present"*,
-and the X4 Classic shares this board. That is the strongest statement located.
-
-So: radio presence is **`inferred` from the SoC and from a sibling's
-documentation**, not directly confirmed on an X4 Pro. It is not seriously in
-doubt — the stock firmware performs OTA over HTTP and hosts a web file manager —
-but it has not been demonstrated here.
-
-## What stock uses the radio for
-
-Recovered from the **X4 (C3)** dump and assumed shared:
-
-| Endpoint | Role |
-|---|---|
-| `http://gotaserver.xteink.com/api/check-update` | OTA check — **plain HTTP, not HTTPS** |
-| `http://bofi.xteink.cn/index.html` | On-device web file manager |
-
-Also present in that dump: the string `XT-EPD`, plausibly an AP SSID or BLE
-device name — **not confirmed**.
-
-## BLE in the community firmware
-
-The FreeInk SDK ships `libs/network/BleKeyboardHost`, i.e. **BLE HID host**
-support for Bluetooth page-turner remotes. There is an established accessory
-ecosystem around this (`CrazyCoder/free2-updater-patch` exists to fix a broken
-VID check in a JieLi page-turner's updater so it pairs with Xteink devices).
-
-`hannah-nula/crosspoint-x3-ble-page-turner` is a fork specifically for *"validated
-BLE page-turner reconnect support"* — implying reconnect is fragile by default.
-
-## Resource notes
-
-Wi-Fi and BLE share one 2.4 GHz radio on the ESP32-S3; concurrent use costs
-throughput and power. **No coexistence testing on this device was found.**
-
-## Status
-
-`inferred` for presence. `reported-working` for BLE page-turners.
-`not-tested` for throughput, range, coexistence and power.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 13:* | Antenna | **Not characterised.** No teardown, no FCC filing |
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](../certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-pro/gaps-and-conflicts.md b/devices/xteink/x4-pro/gaps-and-conflicts.md
deleted file mode 100644
index 077866b..0000000
--- a/devices/xteink/x4-pro/gaps-and-conflicts.md
+++ /dev/null
@@ -1,149 +0,0 @@
-# Xteink X4 Pro — gaps and conflicts
-
-> Snapshot **2026-09-04**.
-
-## Active conflicts
-
-### 1. Touch axis flip: the SDK contradicts itself
-
-| Source | Claim |
-|---|---|
-| `BoardConfig.h:1567` | `flipY = true`, comment: *"swapXY + flipY **(confirmed by corner-tap)**"* |
-| `docs/xteink-x4pro-support.md:154` | *"`flipX`/`flipY` **pending** a corner-tap test"* |
-| same doc, `:351–353` | *"**Pending** — Touch flip — `flipX`/`flipY` still to confirm with a corner-tap test"* |
-
-Same repository, same commit `2400379`. One says confirmed, two say pending.
-
-**Not resolved here.** The likeliest reading is that the header was updated when
-the test was done and the prose doc was not — but that is a hypothesis, not a
-finding. **What would settle it:** a corner-tap test on hardware, or the commit
-history of `BoardConfig.h:1567` versus the doc.
-
-**Practical impact:** low. Taps register and navigation works either way; only
-mirroring is at stake.
-
-### 2. Stock firmware version: 7.4.4 vs V7.4.5
-
-The OTA package `xteink_app_update_x4pro_7.4.4_20260827_133901.xota` has metadata
-labelling it **`V7.4.5`** while the embedded app descriptor says **`7.4.4`**.
-The SDK states the **descriptor is authoritative**. Recorded so nobody "fixes" a
-version string to match packaging.
-
-### 3. Resolved: the "EPD PMIC at 0x63"
-
-An earlier narrative held that I²C `0x63` was a display power-management IC and
-that the panel had dead rails needing an external supply. **Refuted.** `0x63` is a
-**CW2017 battery fuel gauge** — an I²C register dump showed the classic BATINFO
-battery-model curve at `0x10`–`0x3F`. The panel runs off the controller's internal
-booster. Recorded because the refuted version is more memorable than the correct
-one and keeps resurfacing.
-
-### 4. Resolved: the ADC button ladder
-
-Earlier RE proposed an ADC resistor ladder on GPIO10. **Refuted on hardware** —
-this variant has plain digital buttons. The ladder matcher at IROM `0x4201f734`
-is real but **vestigial**. It *is* live on the X3 and X4.
-
-### 5. Resolved: GPIO7 as a display enable
-
-Proposed, then refuted: GPIO7 reads `INPUT_PULLUP` and is the **Right button**.
-
-## Gaps — physical
-
-| Unknown | Why it matters | What would close it |
-|---|---|---|
-| **Battery capacity** | No runtime estimate is possible | A teardown photo of the cell label |
-| **Device mass and dimensions** | Only a 250 g *packaged* weight exists | A vendor spec sheet or an owner measurement |
-| **Charger IC part** | Not on I²C; unidentified | Teardown |
-| **Panel module part number** | Only the controller is known, not the glass/module | Teardown or FPC marking |
-| **Antenna type** | Not characterised | Teardown or an FCC internal-photos exhibit |
-| **Debug pads / test points** | No known UART or JTAG access | Teardown |
-| **PCB revision markings** | No revision scheme is known for this device | Teardown |
-
-**All seven would be closed by one teardown. There is no X4 Pro teardown
-anywhere public** — this is the largest single gap in the record.
-
-## Gaps — regulatory
-
-**No FCC ID, CE marking or SRRC certificate has been read for any Xteink device.**
-No board photo exists to read one from, so there is no ID to query. Not searched
-to completion. An FCC filing would supply internal photographs, antenna details
-and RF test data in one document — the highest-value unexplored source.
-
-## Gaps — firmware
-
-| Unknown | Note |
-|---|---|
-| **No public X4 Pro stock image** | Unlike the X3/X4, no dump or OTA package is downloadable. Your own backup is the only restore path |
-| **`.xota` container format** | The SDK refers to *"the decrypted"* app; the encryption is undocumented |
-| **OTA feed contents** | `gotaserver.xteink.com/api/check-update` was **not queried** this session — an obvious and cheap next step |
-| **USB-MSC** | In stock, not ported to the SDK |
-| **`usbDetect` pin** | GPIO10 floated as a candidate but is already the touch INT — treat as wrong |
-| **`batteryAdc` pin** | Not isolated |
-
-## Gaps — measurement
-
-**Nothing about this device was measured by this session.** No power draw, no
-sleep current, no refresh timing, no runtime, no throughput. The one refresh
-figure quoted (~38 ms/plane write @20 MHz) is from the **X4**, same controller,
-different board.
-
-## Gaps — market
-
-- **Chinese-market pricing** for the X4 Pro was never captured; only the $99 USD
-  store price.
-- **The delisted X4 product page** could not be recovered — the Wayback CDX query
-  timed out and was not retried.
-
----
-
-## Round 2 — 2026-09-11
-
-**No line above was altered.**
-
-### Resolved
-
-| Was | Now | By |
-|---|---|---|
-| No regulatory filing known | **FCC ID `2BTR9-X4PRO`, granted 2026-06-16**; internal photos public **2026-12-12** | fccid.io |
-| Manufacturer's legal identity unknown | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, FRN `0037772233`, `chuchen@xteink.cn` | FCC grantee record |
-| No teardown, no stock dump, no price-independent corroboration | **A third party dumped a physical unit twice (identical hashes), read its eFuses, decoded its partitions and traced its I²C and LEDC** | [`kycube/x4pro-emu`](https://github.com/kycube/x4pro-emu/tree/bf4b86ae0471012d4d07c0bb3042f3f561c9c302) |
-| Which panel controller ships | **One retail unit: `hw_calib/screenType = 2` → UC8279, and `VER=00 0F 68 00 00 FLG=13` → LUT_VER `0x68` → UC8279.** One unit, not a distribution | same |
-| `0x63` identity | **CW2017 fuel gauge**, confirmed on the live bus. The earlier "display PMIC" hypothesis stays refuted | same |
-| GPIO7 is the Right button, not a display enable | **Confirmed independently** | same |
-| FreeInk support-doc I²C paragraph | **Stale — INT and RST are swapped in the doc.** The struct is correct | same |
-
-### New conflict — X4 Pro touch orientation
-
-| # | Source | Claim | Basis |
-|---|---|---|---|
-| R2-P1a | FreeInk `BoardConfig.h` | `swapXY=true, flipX=false, flipY=true`, annotated *"confirmed by corner-tap"* | reverse engineering + the author's own corner-tap |
-| R2-P1b | `kycube/x4pro-emu` `docs/hardware.md` | repeats FreeInk's values; models them in the emulator | repetition, not an independent test |
-| R2-P1c | **`clackups/draftling` `HARDWARE.md`** | FreeInk's values *"had touches landing **180 degrees opposite** of where the finger was"*; corrected to `TOUCH_MIRROR_X`/`TOUCH_MIRROR_Y` = `1`/`0` **against a physical unit** | **on-hardware** |
-
-**Unresolved.** R2-P1c is the only on-hardware claim, but the two projects use
-different rendering stacks with different orientation conventions, so a mapping
-that is "180° wrong" in one may be correct in the other. **What would settle it:**
-one person, one device, both firmwares, four corner taps, reported with the raw
-`0x8150` values alongside the rendered coordinates.
-
-This supersedes nothing: the pre-existing conflict — the SDK header says
-"confirmed" while its own doc says "pending", **twice** — remains, and now has a
-third position.
-
-### New conflict — stock firmware version
-
-**Four numbers, one device.** `7.2.4` (desk unit, ESP-IDF v6.0.1, built
-2026-08-14, hardware-read), `7.4.4` (app descriptor), `V7.4.5` (package
-metadata), `7.5.4` (a third-party analysis document). Not reconcilable from
-public evidence; the vendor publishes no changelog and ships regional and
-OTA-staged builds. **Recorded, not resolved.**
-
-### Still open
-
-| # | Gap | What would settle it |
-|---|---|---|
-| R2-P2 | **The panel pinout is still single-source.** SCLK 12 / MOSI 11 / CS 13 / DC 18 / RST 14 / BUSY 6 traces only to FreeInk; both new firmware custodians cite FreeInk rather than deriving it | **FCC internal photos, 2026-12-12**, or a continuity measurement |
-| R2-P3 | Charge-`STAT` polarity on GPIO21 | a multimeter on a charging unit |
-| R2-P4 | Refresh timings (~1800 ms full / ~500 ms fast) are inherited from FreeInk's docs; the desk unit's author marks the measurement **pending** | `micros()` around DRF → BUSY on the device |
-| R2-P5 | The `XteinkDetect` bit-banged probe **algorithm** has never been independently re-derived | a second reverse engineering, or the permanently-confidential schematic |
diff --git a/devices/xteink/x4-pro/market-and-pricing.md b/devices/xteink/x4-pro/market-and-pricing.md
deleted file mode 100644
index c151efd..0000000
--- a/devices/xteink/x4-pro/market-and-pricing.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Xteink X4 Pro — market and pricing
-
-> All observations dated. Currency USD unless stated. **Vendor-direct only —
-> there is no distributor network.**
-
-## Current pricing — observed 2026-09-04
-
-Source: `https://www.xteink.com/products.json?limit=250`, retrieved 2026-09-04,
-worldwide shipping from Shenzhen. Prices are **item price only**, excluding
-shipping (a separate `shipping-fee` SKU exists) and excluding any import duty.
-
-| Item | Variant | Price | Stock |
-|---|---|---|---|
-| **Xteink X4 Pro Pocket eReader** | Space Black (only) | **$99.00** | ✅ available |
-| X4 Pro Magnetic Case | 6 colours | $8.99 | 5/6 available; **Space Black sold out** |
-| XTEINK X4 Pro Protective Case | Mist White / Mist Gray | $3.99 | ✅ |
-| X4 Pro Tempered Glass Screen Protector | 1-pack | $4.99 | ✅ |
-| " | 2-pack / 3-pack | $7.99 / $9.99 | ❌ both sold out |
-| X4 Pro Matte Screen Protector | 2/4/6-pack | $3.99 / $5.99 / $8.39 | ❌ **all sold out** |
-| Magnetic Pogo Pin Charging Cable (X3 & X4 Pro) | — | $4.99 | ✅ |
-| Magnetic Charging Adapter (X3 & X4 Pro) | — | $5.99 | ✅ |
-
-**The real entry price is not $99.** The device charges only over pogo pins, so a
-first-time buyer who wants a spare cable and any screen protection is at
-**$99 + $4.99 + $4.99 ≈ $109**, and matte protectors are entirely out of stock.
-
-## Launch pricing
-
-$99.00, listed **2026-07-21**, described in the product body as *"currently
-available for pre-order. The next restock is officially scheduled for the date of
-August 6."* Same price at launch and at snapshot — **no discount observed in six
-weeks**.
-
-## Family price ladder — 2026-09-04
-
-| Device | Vendor price | Note |
-|---|---|---|
-| X3 | **$69.00** | Mist Gray + Space Black, both available |
-| X4 | **delisted** | Only accessories remain, and **every X4 accessory is sold out** |
-| **X4 Pro** | **$99.00** | Current flagship |
-| X4 Classic | **not listed** | A `x4-classic` collection exists but contains **no device** |
-| S4 | not on the .com store | ¥299 preorder / ¥339 regular ≈ **US$50** (China, 2026-04) |
-
-## Community-reported prices
-
-| Date | Claim | Source | Status |
-|---|---|---|---|
-| 2026-07-24 | *"Price ($69 X4, $79 X3, $99 X4 Pro)"* | [r/XTEINK `1v5gh6x`](https://old.reddit.com/r/XTEINK/comments/1v5gh6x/) | **Conflicts with the vendor API**, which shows X3 at $69 not $79. Community figure, uncorroborated |
-| 2026-06-20 | **20% off sale**, *"the best deal I've seen so far"*, via the CrossPoint affiliate link | [r/xteinkereader `1uan67g`](https://old.reddit.com/r/xteinkereader/comments/1uan67g/) | Sales do happen; a coupon code was promised after |
-| 2026-08-18 | **X3 acquired for $16** | [r/XTEINK `1vrnxnq`](https://old.reddit.com/r/XTEINK/comments/1vrnxnq/) | Channel not stated. **Do not merge this into a price range** — condition and channel unknown |
-| 2026-04-23 | S4 **¥299** (limited to existing X3/X4 owners) / **¥339** regular | [r/XTEINK `1stni9p`](https://old.reddit.com/r/XTEINK/comments/1stni9p/) | Reported from a Chinese announcement |
-
-## Availability and channel
-
-- **Vendor-direct only.** No authorised distributor, no Amazon storefront, no
-  retail presence located.
-- **China-first.** The S4 launched domestically months ahead of any international
-  availability; the X4 Classic still has no international listing.
-- One community claim that the X4 *"Cracked Amazon's e-reader top 10"*
-  ([r/XTEINK `1v5gh6x`](https://old.reddit.com/r/XTEINK/comments/1v5gh6x/)) —
-  **unverified, no listing was found.**
-
-## Warranty and after-sales
-
-Three revealing SKUs in the catalogue:
-`$50 After-sale` (added 2026-08-12), `After-sales Fees`, `Exchange Handling Fees`,
-`Handling Fees`, `Shipping fee`. **After-sales service is charged for as a
-product.** Buyers should assume repair is a paid transaction, not a warranty.
-
-## Caveats
-
-- Prices are **item price only** — shipping, tax and duty are extra and were not
-  captured.
-- Stock state is a **single-instant snapshot**.
-- The $16 used observation is a **single anecdote** with unknown channel and
-  condition, deliberately not merged with new pricing.
-- **No Chinese-market price for the X4 Pro was captured at all.**
-
----
-
-## Dated observation — 2026-09-11, vendor store
-
-Source: **`https://xteink.com/products.json?limit=250&page=1`**, retrieved **2026-09-11**. Full
-catalogue enumerated: **25 products**. Currency USD as served. Condition: new, genuine
-(manufacturer store). Item price only.
-
-| Product | Published | Variant | SKU | Price | In stock |
-|---|---|---|---|---|---|
-| Xteink X4 Pro Pocket eReader | 2026-07-21 | Space Black | `X4Pro-Black` | **USD 99.00** | ✅ |
-| Xteink X4 Pro Pocket eReader | 2026-07-21 | + Mist Sage Base | `X4PB+BW` | **USD 115.00** | ❌ out of stock |
-| Xteink X4 Pro Pocket eReader | 2026-07-21 | + Space Black Base | — | **USD 115.00** | ❌ out of stock |
-
-> *USD 99.00, 1 unit, retrieved 2026-09-11, `https://xteink.com/products/xteink-x4-pro-pocket-ereader`, ships from CN (origin not stated by vendor)*
-
-### ✅ This closes a parked correction
-
-**USD 99.00 observed 2026-09-11 independently confirms USD 99.00 observed 2026-09-04** from the
-same endpoint — two observations, one week apart, identical. That settles claim 2 of correction
-#4 in
-[`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
-⚠ The PaperMono record's assertion that *"the XTEINK X4 Pro … was never priced"* is **wrong on
-both dates**. That record is owned by a live session and was **not edited**; the item is parked in
-[`scratch/index-merge/deferred-round2.md`](../../../scratch/index-merge/deferred-round2.md).
-
-### Family context as of 2026-09-11
-
-The X4 Pro is now the **top** of a three-device live line-up, not the middle of four:
-
-| Device | Vendor price, 2026-09-11 | Status |
-|---|---|---|
-| X3 | USD 69.00 | on sale |
-| **X4 Classic (X4 V2)** | **USD 79.00** | on sale, listed **2026-09-06** |
-| **X4 Pro** | **USD 99.00** | on sale |
-| X4 | — | **withdrawn**, with all four of its accessories |
-| X4 Light | — | **FCC-granted 2026-08-13, never listed** |
-
-⚠ **Not obtained:** no marketplace, clone or used-market price. **No Chinese-market price for the
-X4 Pro was captured** — that gap, recorded above, is still open.
diff --git a/devices/xteink/x4-pro/media.md b/devices/xteink/x4-pro/media.md
deleted file mode 100644
index 31a741b..0000000
--- a/devices/xteink/x4-pro/media.md
+++ /dev/null
@@ -1,80 +0,0 @@
-# Xteink X4 Pro — images and media
-
-**No image of this device — external, internal or PCB — is held in this
-repository.** This page records what was sought and what exists, so the search is
-not repeated blindly.
-
-## What was searched
-
-| Target | Where | Result |
-|---|---|---|
-| Teardown / PCB photography | Reddit `xteink teardown`, `xteink teardown chip` across 1,798 posts | **None for the X4 Pro.** Two X3 teardowns exist |
-| Vendor product imagery | `xteink.com` Shopify product record | Images exist in `products.json` but were **not downloaded** — see below |
-| FCC internal photos | not searched — **no FCC ID is known** | — |
-| YouTube teardowns | only via Reddit-surfaced links | none found for the Pro |
-
-## Why no vendor images were retained
-
-The Shopify product record carries image URLs on the Shopify CDN. They were not
-downloaded because:
-
-1. They are **marketing renders and lifestyle shots**, not identification or
-   mechanical references — they show a black slab.
-2. Their **rights status is clearly the vendor's** and redistribution here would
-   be unexamined.
-3. They establish **nothing not already in the text record**.
-
-If wanted later, they are in `scratch/xteink/vendor/products-p1.json` under
-`products[].images[].src`, retrieved 2026-09-04.
-
-## What exists elsewhere in this tree
-
-The [X3 record](../x3/media.md) holds **two independent teardowns**, both
-archived with placeholders:
-
-- a 13-image English-captioned Imgur album
-- a 10-image Chinese set **including a hand-drawn schematic**
-
-The X3 is a **different board** (ESP32-C3, different panel, different peripherals)
-so those images are **not** a substitute for X4 Pro photography. They do
-establish the vendor's general construction style: glued battery, glued pogo
-magnets, glass back.
-
-## The gap, stated plainly
-
-Seven separate unknowns in [`gaps-and-conflicts.md`](gaps-and-conflicts.md) —
-battery capacity, mass, dimensions, charger IC, panel module part, antenna, debug
-pads — **would all be closed by one X4 Pro teardown.** Producing or finding one is
-the single highest-value next action for this device.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 13:* | FCC internal photos | not searched — **no FCC ID is known** | — |
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-pro/performance.md b/devices/xteink/x4-pro/performance.md
deleted file mode 100644
index b1b07a9..0000000
--- a/devices/xteink/x4-pro/performance.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# Xteink X4 Pro — performance
-
-> **Nothing was measured.** Not by this session, and not by anyone whose results
-> were published. Retrieved **2026-09-04**.
-
-## The only quantitative figures that exist
-
-| Quantity | Value | Status |
-|---|---:|---|
-| **OEM display SPI clock** | **5 MHz** (`SPISettings 0x4C4B40`) | **[DUMP]** recovered constant — a hard fact about the stock firmware |
-| FreeInk display SPI clock | **20 MHz** | developer-chosen; SSD1677 datasheet write maximum |
-| Frontlight PWM (stock 7.0.8) | **25 kHz, 10-bit**, LEDC ch4/ch5 | **[DUMP]** recovered |
-| Frontlight PWM (bring-up dump) | 10 kHz | **[DUMP]** — an older image |
-| SDMMC | 1-bit, slot 1, **40 MHz** | board profile |
-| I²C | 400 kHz | board profile |
-
-## The most actionable performance finding in the subject
-
-**The OEM clocks its own panel at 5 MHz when the controller is rated for 20.**
-
-That is a **4× margin left on the table** for RAM writes, in the vendor's own
-shipping firmware, on the flagship model. The FreeInk SDK's comment is
-matter-of-fact about it:
-
-> "displaySpiHz: 20 MHz, matching the X4's default. **The OEM clocks the panel at
-> only 5 MHz** (`SPISettings 0x4C4B40`), but the SSD1677 handles far more (X4 runs
-> 20, de-link 40), so 20 MHz is well in spec and gives noticeably faster RAM
-> writes. Drop back to 5 MHz if artifacts appear."
-
-**"Noticeably faster" is not a measurement.** No before/after timing was published.
-The escape hatch in the last sentence is worth taking seriously: nobody has
-characterised whether every X4 Pro panel is stable at 20 MHz.
-
-## A second OEM inefficiency
-
-The stock `INIT` routine issues SW RESET `0x12` and then a **fixed `delay(10)` —
-not a BUSY-wait** (**[DUMP]**, IROM `0x4201a568`). It works, but it is a timing
-assumption rather than a handshake: on a slow-starting controller it is a race,
-and on a fast one it wastes time. Latent rather than active.
-
-## Borrowed figures — and why they are borrowed
-
-The only plane-write timings in this tree are for the **[X4](../x4/performance.md)**:
-~**38 ms** at 20 MHz, ~**19 ms** at 40 MHz. Same controller family, **same
-resolution (800×480)**, different SoC and different board.
-
-They are **indicative for the X4 Pro, not measurements of it.** The X4 Pro runs
-the same 20 MHz clock on the same pixel count, so ~38 ms is a reasonable
-expectation — but the S3's DMA and PSRAM behaviour differ, and nobody has checked.
-
-## What has never been measured
-
-| Quantity | Note |
-|---|---|
-| **Battery capacity** | **Unknown.** No teardown exists. The X3 is 650 mAh; the Pro is unmeasured |
-| **Runtime** | No figure anywhere |
-| **Sleep current** | Never measured. The SDK explicitly flags it: the sleep path drives the active-low enables to their off level, and *"worth a power-draw check"* |
-| Active current | Never measured |
-| Page-turn latency, end to end | Never measured — waveform time dominates and is unquantified |
-| Frontlight brightness / CCT range | Never measured |
-| SDMMC throughput | Never measured |
-| Wi-Fi / BLE throughput, range, coexistence | Never measured |
-| Touch latency or report rate | Never measured |
-| Boot time | Never measured |
-
-## The measurement attempt that produced nothing
-
-The only person known to have set out to instrument this board family attached a
-**Nordic Power Profiler Kit II** to an **X3** in July 2026 and **never published
-results** ([r/xteinkereader `1uksv6s`](https://old.reddit.com/r/xteinkereader/comments/1uksv6s/)).
-Nobody has attempted it on an X4 Pro.
-
-## Where the X4 Pro should be structurally faster than the C3 models
-
-Reasoning, not measurement:
-
-| Advantage | Why |
-|---|---|
-| **8 MB PSRAM** | Multi-buffer rendering and damage-window partial refresh become possible. [`goodyttoor/inkback-freeink-sdk`](https://github.com/goodyttoor/inkback-freeink-sdk) implements exactly this — *"InkMotion (PSRAM multi-buffer, damage windows, ghost budget) and X4 Pro display work"* |
-| **Native SDMMC, dedicated pins** | The card does not contend with the display bus, unlike the C3 devices where both share SCLK/MOSI |
-| **Dual-core Xtensa LX7 at up to 240 MHz** | vs a single RISC-V core at 160 MHz |
-| **No OTA out-of-memory** | The documented C3 failure mode does not apply |
-
-**None of this is quantified.** It is the reason the X4 Pro is the ecosystem's
-"design floor", but no benchmark supports it.
-
-## Honest summary
-
-**Two recovered firmware constants and one borrowed timing.** Every figure a buyer
-or developer would want — battery life, refresh latency, sleep current — is
-**unmeasured by anyone**, on the family's flagship.
diff --git a/devices/xteink/x4-pro/pinouts-and-buses.md b/devices/xteink/x4-pro/pinouts-and-buses.md
deleted file mode 100644
index 1d69862..0000000
--- a/devices/xteink/x4-pro/pinouts-and-buses.md
+++ /dev/null
@@ -1,165 +0,0 @@
-# Xteink X4 Pro — pinouts and buses
-
-> Reconstructed from the FreeInk SDK board profile and its bring-up document,
-> both of which are explicit about which lines were **probed on hardware** and
-> which remain inferred from a firmware dump. Retrieved **2026-09-04**.
-
-## Primary evidence
-
-| Tag | Source | Pin |
-|---|---|---|
-| **[SDK]** | `Free-Ink/freeink-sdk` @ `24003795381a6c23630a26472ae3b06550333e71`, `libs/hardware/BoardConfig/include/BoardConfig.h`, `constexpr BoardProfile XTEINK_X4_PRO` at **lines 1495–1613** | commit-pinned |
-| **[DOC]** | same commit, `docs/xteink-x4pro-support.md` | commit-pinned |
-| **[HW]** | Marked *"Confirmed on hardware"* in **[DOC]** — bit-banged pin sweep, pull-up edge test, live I²C scan | — |
-| **[RE]** | Ghidra analysis of the OEM flash dump, IROM offsets quoted in **[DOC]** | — |
-
-Permalink to the profile:
-`https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L1495-L1613`
-
-## Complete GPIO map
-
-| GPIO | Signal | Dir | Bus / role | Notes | Evidence |
-|---:|---|---|---|---|---|
-| 0 | Button **Left** → Up / prev page | in | digital, active-LOW | **Boot strap** — fine as a button if not held at reset | **[HW]** `:1528` |
-| 1 | **Master peripheral rail enable** | out | power | Driven HIGH **first** in board-init; panel + SD depend on it | **[RE]** `board_begin` IROM `0x420a23dc`; `:1606` |
-| 2 | **Touch power enable** | out | power | **ACTIVE-LOW.** GT911 is unpowered and silent until this is LOW | **[HW]** `:1562, 1567` |
-| 3 | Button **Power** | in | digital, active-LOW | `powerActiveHigh = false` | **[HW]** `:1528` |
-| 4 | GT911 **RST** | out | touch | Earlier RE had 4/10 reversed; **corrected** | **[HW]** `:1552` |
-| 5 | **SD power enable** | out | power | **ACTIVE-LOW.** Pulse HIGH 80 ms → LOW 120 ms, then hold LOW | **[HW]** `:1521` |
-| 6 | EPD **BUSY** | in | display | Busy = **HIGH** | **[HW]** `:1509` |
-| 7 | Button **Right** → Down / next page | in | digital, active-LOW | Reads `INPUT_PULLUP` — **not** a display enable | **[HW]** `:1528` |
-| 8 | Frontlight **cool/white** | out | LEDC ch4 | active-HIGH | **[HW]** `:1577` |
-| 9 | Frontlight **warm** | out | LEDC ch5 | active-HIGH | **[HW]** `:1577` |
-| 10 | GT911 **INT** / address select | i/o | touch | Driven at reset to select address, then floated to input | **[HW]** `:1551` |
-| 11 | EPD **MOSI** | out | display SPI | write-only, no MISO | **[HW]** `:1509` |
-| 12 | EPD **SCLK** | out | display SPI | | **[HW]** `:1509` |
-| 13 | EPD **CS** | out | display SPI | | **[HW]** `:1509` |
-| 14 | EPD **RST** | out | display | | **[HW]** `:1509` |
-| 18 | EPD **DC** | out | display | driven only for commands | **[HW]** `:1509` |
-| 19 | USB **D−** | i/o | native USB-OTG | do not repurpose | **[DOC]** §RTC/USB/battery |
-| 20 | USB **D+** | i/o | native USB-OTG | do not repurpose | **[DOC]** §RTC/USB/battery |
-| 21 | Charger **STAT** | in | battery | **active-HIGH** = charging; input, no pull | **[RE]** `Cw2017PowerHal` vtable slot 3 → IROM `0x4214f67c`; `:1535, 1613` |
-| 38 | I²C **SCL** | out | shared bus | 400 kHz | **[HW]** `:1550` |
-| 39 | I²C **SDA** | i/o | shared bus | 400 kHz | **[HW]** `:1549` |
-| 40 | SDMMC **DAT0** | i/o | storage | | **[HW]** `:1586` |
-| 41 | SDMMC **CLK** | out | storage | | **[HW]** `:1586` |
-| 42 | SDMMC **CMD** | i/o | storage | | **[HW]** `:1586` |
-| 45 | (SD SPI CS, vestigial) | — | — | Retained in the SPI view only; unused once `busWidth != 0` | **[SDK]** `:1521` |
-
-**Unassigned / unknown:** `batteryAdc` and `usbDetect` are both
-`PIN_UNASSIGNED`. Battery monitoring exists in stock firmware but no ADC pin was
-isolated, and no VBUS-presence signal was conclusively identified — stock derives
-its battery icon from the GPIO21 charge state instead **[SDK]** `:1529, 1537`.
-
-## Display bus
-
-| Signal | GPIO | Notes |
-|---|---:|---|
-| SCLK | 12 | |
-| MOSI | 11 | **write-only — there is no MISO** |
-| CS | 13 | driven every byte in `writeCommand`/`writeData` |
-| DC | 18 | LOW = command, HIGH = data |
-| RST | 14 | |
-| BUSY | 6 | input, busy = HIGH |
-
-Clock: OEM uses **5 MHz**; FreeInk uses **20 MHz** (SSD1677 datasheet write max).
-Native scan is 800×480 landscape, `NO_FLIP`.
-
-**Because there is no MISO on the write path, the controller-ID probe releases
-MOSI to input mid-transaction** and clocks the reply back on the same wire — a
-half-duplex read. That is why the probe can work at all on a "write-only" bus
-**[SDK]** `XteinkDetect.cpp:79–91`.
-
-### The pin-map trap
-
-Every early reverse-engineering pass read **app0**, which is a *different device
-variant* (`ESP32S3_X4_TL`, Arduino-era, hardcoded pins). App0 gives **CS and DC
-swapped, and SCLK/MOSI in the wrong order**. The device actually boots **app1**.
-With the app0 map, the controller resets and runs full-length waveforms but never
-develops an image — a failure mode that looks like a dead panel or a missing
-power rail, and generated a long false "EPD PMIC / dead rails" investigation
-before the pins were swept on hardware **[DOC]** §Root cause.
-
-## I²C bus — SDA 39 / SCL 38 @ 400 kHz
-
-| Address | Device | Component | Notes |
-|---|---|---|---|
-| **0x51** | BM8563 RTC (PCF8563-compatible) | [`generic/bm8563`](../../../components/generic/bm8563/README.md) | Class `XTEink::BM8563Driver` in the dump; init at IROM `0x420a2834` |
-| **0x5D** (alt 0x14) | GT911 touch | [`goodix/gt911`](../../../components/goodix/gt911/README.md) | Only ACKs once GPIO2 is LOW **and** GPIO1 is HIGH |
-| **0x63** | CW2017 fuel gauge | [`cellwise/cw2017`](../../../components/cellwise/cw2017/README.md) | **Not** a display PMIC — an early hypothesis said it was |
-
-An idle scan of this bus with GPIO2 high shows **only 0x51 and 0x63**. The missing
-GT911 is the diagnostic signature of an unpowered touch rail.
-
-## Touch — GT911 details
-
-| Property | Value |
-|---|---|
-| Reset dance | RST LOW + INT at select level, 2 ms → RST HIGH, 8 ms → INT to INPUT+pull, 60 ms, probe |
-| Address select | INT level as RST rises: LOW → 0x5D |
-| Config upload | **None.** The GT911 self-loads its internal config |
-| Status register | `0x814E` — bit7 ready, low nibble = point count |
-| Point data | from `0x8150`, 8 bytes each, **X-lo at byte 0** (`gt911CoordsAtByte0 = true`) |
-| Mounting | **Portrait sensor on a landscape panel** — reports X:0–480, Y:0–800 → `swapXY = true` |
-| Home key | GT911 capacitive key bit, status `0x814E & 0x10` — **not a GPIO** |
-
-An earlier failure had the config registers reading back all-zero: the cause was a
-**too-short reset** that never triggered the internal config load, not a missing
-config table. The SDK's 10/10/50/50 ms sequence fixes it **[DOC]** §Touch.
-
-## Storage — native SDMMC
-
-| Signal | GPIO |
-|---|---:|
-| CLK | 41 |
-| CMD | 42 |
-| DAT0 | 40 |
-| power enable | 5 (**active-LOW**) |
-
-1-bit, slot 1, internal pull-ups, 40 MHz. DAT1/2/3 unused.
-**SPI-mode CMD0 is silent on this slot** — an SPI card path can never work.
-
-Mount sequence, both steps required:
-1. Pulse GPIO5 HIGH (80 ms) → LOW (120 ms), then run `sdmmc_card_init`
-   **and a real sector-0 read**, retrying the *whole* thing. Retrying only
-   `card_init` leaves the first un-retried block read to fail with
-   `sdmmc_read_sectors_dma … 0x107`.
-2. **Leave GPIO5 LOW.** Driving it HIGH after init breaks every subsequent read.
-
-Transfers bounce through a `MALLOC_CAP_DMA` buffer because SdFat caches may live
-in PSRAM or be unaligned.
-
-## Power rails and boot order
-
-1. **GPIO1 HIGH** — master peripheral rail. First action in board-init.
-2. **GPIO2 LOW** — touch rail on (active-low).
-3. **GPIO5** pulsed HIGH→LOW — SD rail, held LOW.
-4. Display reset and controller probe.
-
-The sleep path drives each enable to its *off* level **by polarity**, so on this
-board that means driving GPIO2 and GPIO5 **HIGH**.
-
-## Resource conflicts and shared buses
-
-| Resource | Shared by | Arbitration |
-|---|---|---|
-| I²C 39/38 | GT911, BM8563, CW2017 | One Arduino `Wire` controller (`i2cBus = 0`) for all three. No conflict, but all three stall if the bus is held |
-| LEDC ch4/ch5 | frontlight only | Reserved; do not reuse for PWM elsewhere |
-| GPIO0 | Button Left **and** the ESP32-S3 boot strap | Holding Left at reset enters download mode |
-| GPIO19/20 | native USB only | **Never probe these.** The C3 X3/X4 detect fingerprint pokes SDA20/SCL0, which on this S3 lands on D+ and a boot strap — which is why `XteinkDetect` compiles the C3 fingerprint to a no-op unless a C3 profile is in the build **[SDK]** `XteinkDetect.cpp:13–19` |
-
-## Bezel / viewable insets
-
-`viewableInsets = {9, 7, 3, 7}` (top, right, bottom, left) **[SDK]** `:1612`.
-7 px side inset is empirically tuned so an edge-hugging scrollbar stays visible;
-top/bottom are **carried over from the X4 and are not measured**. Without these,
-upstream firmware draws under the glass on this device.
-
-## What is still unconfirmed
-
-- **Panel mount orientation** — ships `NO_FLIP`, pending hardware.
-- **`usbDetect`** — GPIO10 floated as a candidate, unconfirmed (and GPIO10 is
-  already the GT911 INT, so this is unlikely and should be treated sceptically).
-- **`batteryAdc`** — not isolated.
-- **Touch `flipX`/`flipY`** — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md);
-  the SDK contradicts itself.
diff --git a/devices/xteink/x4-pro/product-history-and-family.md b/devices/xteink/x4-pro/product-history-and-family.md
deleted file mode 100644
index ae44ab4..0000000
--- a/devices/xteink/x4-pro/product-history-and-family.md
+++ /dev/null
@@ -1,76 +0,0 @@
-# Xteink X4 Pro — product history and family
-
-Full family context: [`../README.md`](../README.md).
-
-## Timeline
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2026-06-13 | An S4 promotional video also shows unannounced hardware | **[COMM]** [r/XTEINK `1u4ty4q`](https://old.reddit.com/r/XTEINK/comments/1u4ty4q/) |
-| **2026-06-22** | Community spots **a new X4 variant** in a vendor video — *"Physical buttons + frontlight but no touchscreen"*, **300 pts**. They were describing what became the [X4 Classic](../x4-classic/README.md) | **[COMM]** [`1ud0d9c`](https://old.reddit.com/r/XTEINK/comments/1ud0d9c/) |
-| 2026-07-07 | X4 Pro Shopify product record **created** | **[VENDOR]** |
-| 2026-07-17 | Pre-launch poll: *"are you going to buy the X4 Pro? Or the S4?"*, 89 comments | **[COMM]** [`1uz9mtg`](https://old.reddit.com/r/xteinkereader/comments/1uz9mtg/) |
-| **2026-07-21** | **Launch**, $99, Space Black only. Listed as pre-order with restock 6 Aug | **[VENDOR]** |
-| 2026-07-21 | **Pogo-pin backlash** begins — 71 + 46 comments across two subreddits | **[COMM]** [`1v2txxe`](https://old.reddit.com/r/xteinkereader/comments/1v2txxe/) |
-| 2026-07-22 | First unboxings — *"XTEINK X4 Pro Unboxing & First Look - Is It Any Good?"* (31 + 38 pts) | **[COMM]** |
-| 2026-07-22 | *"X4 Pro **pogo pin charging loose?**"* — an early quality report | **[COMM]** [`1v3d…`](https://old.reddit.com/r/XTEINK/) |
-| 2026-07-24 | *"xteink x4 pro on crosspoint: dark mode"* — community firmware running within 3 days of launch | **[COMM]** r/eink |
-| 2026-07-26 / 07-28 | Matte, then tempered-glass screen protectors listed | **[VENDOR]** |
-| 2026-07-30 | *"Official X4 Pro Shipping Updates"*, 100 pts | **[COMM]** |
-| **2026-08-16** | *"**Easy fix for X4 Pro's magsafe alignment**"*, 44 pts — a second mechanical complaint | **[COMM]** |
-| 2026-08-18 | CrossInk adds an `x4pro` device type to its bug-report template | **[SRC]** `uxjulia/CrossInk` commit |
-| 2026-08-20 | *"can we install crosspoint on XTEINK X4 PRO **CHINA FIRMWARE**"* — a China/international firmware split becomes visible | **[COMM]** |
-| **2026-08-27** | **Stock firmware 7.4.4 built**, ESP-IDF 6.0.1 | **[DUMP]** app descriptor |
-| 2026-08-23 | Owners of all three models: *"the pro makes the other two feel obsolete"* | **[COMM]** [`1vw6haq`](https://old.reddit.com/r/XTEINK/comments/1vw6haq/) |
-| 2026-09-04 | **$99, in stock.** Matte protectors and 2/3-packs of glass **sold out** | **[VENDOR]** |
-
-## Position in the family
-
-The X4 Pro is the **fourth ESP32 device and the current flagship**. It is the first
-Xteink to move from ESP32-C3 to **ESP32-S3 with 8 MB PSRAM**, and the first — and
-still only — with **touch** and a **frontlight**.
-
-| Relationship | Device |
-|---|---|
-| Namesake predecessor | [X4](../x4/README.md) — **a completely different computer.** Same screen size and brand; different SoC architecture, flash layout, input hardware and charging connector |
-| Board sibling | [X4 Classic](../x4-classic/README.md) — the same S3 board minus touch and frontlight, plus four buttons and an IMU |
-| Cheaper sibling | [X3](../x3/README.md) — sharper screen, more sensors, no PSRAM |
-| Android sibling | [S4](../s4/README.md) — half the price, more consumer features, **no programmability** |
-| Accessory line | [Nano / Tong Card](../nano/README.md) |
-
-**The naming is genuinely misleading.** "X4 Pro" implies an enhanced X4. It shares
-a screen size and nothing else — and it is **not a superset**: the X4 Pro has **no
-IMU**, while both the cheaper X3 and its own board sibling do.
-
-## Its role in the software ecosystem
-
-The X4 Pro is the **design floor** for CrossPlay, whose `LOCAL_SCOPE.md` defines
-minimum viable input as *"two side keys plus touch"* — see the
-[CrossPlay record](../../../software/applications/crossplay/README.md).
-
-It is also the reason a specific porting hazard exists: CrossPlay had to repoint
-`OtaUpdater.cpp` because **upstream's release URL would flash a C3 build onto an
-S3**. The X4/X4-Pro naming collision has real consequences in firmware.
-
-## The two design decisions that define its reception
-
-**1. Magnetic pogo charging, no USB-C charge port.** The single most-contested
-choice in the family. It generated the largest X4 Pro-specific thread, drove
-owners to keep their X4s, and produced two separate mechanical complaints
-(*"pogo pin charging loose?"*, *"magsafe alignment"*). The counter-view — *"the
-pogo charger is really a non-issue"* — is also firsthand and also common.
-
-**2. A touchscreen on a distraction-free reader.** Contested for a different
-reason: *"Additional points of failure… a touch screen adds another layer on top
-of the eink display dimming it."* The rebuttal, from an owner: *"I can tell you
-it's imperceptible… You can set it so the touchscreen is active in menus, but not
-in a book."* Both firsthand.
-
-## What comes next
-
-An **"X4 version 2"** was confirmed by the vendor via Instagram on **2026-08-25**
-for September 2026 ([`1vxsr0x`](https://old.reddit.com/r/xteinkereader/comments/1vxsr0x/)).
-Nothing about it is established. Comment-level rumour claims leaks show two
-devices with pogo pins, one with *"backlight and no touch"* — **hearsay**, and if
-true it is not the X4 Classic, whose firmware is unambiguous that it has no
-frontlight.
diff --git a/devices/xteink/x4-pro/projects-and-community.md b/devices/xteink/x4-pro/projects-and-community.md
deleted file mode 100644
index 9338879..0000000
--- a/devices/xteink/x4-pro/projects-and-community.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Xteink X4 Pro — projects and community
-
-> Census **2026-09-04** via the GitHub repository search API (5 queries × 2 pages,
-> authenticated) plus 1,798 Reddit posts. **~200 relevant repositories.** This
-> page covers the whole family where the ecosystem is shared, and marks what is
-> X4 Pro-specific.
-
-## The ecosystem in one paragraph
-
-Two independent firmware lineages dominate — **CrossPoint Reader** and
-**CrossInk** — both sitting on the **FreeInk SDK**, which is the shared hardware
-abstraction layer and the source of every board fact in this record. Around them
-is an unusually large tail of personal forks, converters, wallpaper generators,
-sync servers and Calibre plugins. The tail exists because the devices are cheap,
-the SDK is good, and the stock firmware is poor.
-
-## The load-bearing projects
-
-| Project | What | Licence | Relevance to X4 Pro |
-|---|---|---|---|
-| [`Free-Ink/freeink-sdk`](https://github.com/Free-Ink/freeink-sdk) | **The HAL.** Board profiles, drivers, display/touch/battery/SD managers | — | **The authoritative hardware source.** `BoardConfig::XTEINK_X4_PRO` |
-| [`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader) | Upstream reader firmware | MIT | The reference implementation |
-| [`uxjulia/CrossInk`](https://github.com/uxjulia/CrossInk) | The other major lineage | MIT | `x4pro` device type added to bug reports 2026-08-18 |
-| [`ma-r-s/crossplay`](https://github.com/ma-r-s/crossplay) | CrossPoint fork adding ~26 games/apps | MIT | **The X4 Pro is its stated design floor.** [Full record](../../../software/applications/crossplay/README.md) |
-| [`crosspoint-reader/community-sdk`](https://github.com/crosspoint-reader/community-sdk) | Community HAL | — | X3 grayscale preconditioning |
-
-## X4 Pro-specific projects
-
-| Repo | What |
-|---|---|
-| [`MrStu82/crosspoint-llama-pro`](https://github.com/MrStu82/crosspoint-llama-pro) | *"CrossPoint Reader llama edition for the Xteink X4 Pro (ESP32-S3, GT911 touch, dual warm/cold frontlight)"* — third-party corroboration of the hardware profile |
-| [`thepropm/proink-os`](https://github.com/thepropm/proink-os) | *"a from-scratch e-reader firmware for the Xteink X4 Pro, built on the FreeInk SDK"* — pushed 2026-09-04 |
-| [`dito94/CrossDiTo`](https://github.com/dito94/CrossDiTo) | Personal X4 Pro fork of CrossInk 1.5 |
-| [`HomeAssistantPi/xteink-backup-utility`](https://github.com/HomeAssistantPi/xteink-backup-utility) | *"Flash and Storage Utility for XTEINK / ESP32-S3. Built for my XTEINK 4 PRO."* The **only** X4 Pro backup tool |
-| [`goodyttoor/inkback-freeink-sdk`](https://github.com/goodyttoor/inkback-freeink-sdk) | FreeInk SDK fork — *"InkMotion (PSRAM multi-buffer, damage windows, ghost budget) and **X4 Pro display work**"* |
-| [`hiroshi/freeink-x4pro-app`](https://github.com/hiroshi/freeink-x4pro-app) | Links the vendor product page directly |
-| [`parsimo2010/xteink-ft8`](https://github.com/parsimo2010/xteink-ft8) | *"Field FT8 from a Raspberry Pi + Xteink X4 Pro e-ink"* |
-| [`mylatestwork/crossink-wallpapers`](https://github.com/mylatestwork/crossink-wallpapers) | Sleep screens for X4 **and X4 Pro** |
-| [`Paatricious/Andrra`](https://github.com/Paatricious/Andrra) | Wikimedia-sourced sleep screens for X4 Pro |
-| [`vjFaLk/esphome-xteink`](https://github.com/vjFaLk/esphome-xteink) | ESPHome components for **X4 / X3 / X4 Pro**, wrapping the FreeInk SDK |
-
-## Community service sites
-
-Named together in [r/XTEINK `1uz8yiz`](https://old.reddit.com/r/XTEINK/comments/1uz8yiz/) (2026-07-17, 723 pts):
-
-| Site | Purpose |
-|---|---|
-| `crosspointreader.com` | **Device unlock**, web flasher, flash-back-to-stock, nightly builds, font builder |
-| `crossink.uxj.io` | CrossInk documentation |
-| `brickclub.pages.dev` | *"to choose an appropriate firmware"* — a firmware chooser. The name is a joke about bricking |
-
-## Non-firmware tooling (family-wide)
-
-| Category | Examples |
-|---|---|
-| Flashers | `bigbag/papyrix-flasher` (Go), `zocs/eink-quick-flasher` (**1:1 full-flash backup/restore, ~2 min**), `OvermindDL1/xteink-unlocker` (Tauri/Rust) |
-| Calibre plugins | `thirteen37/calibre-xtc`, `yemM/crosspoint-reader-sd-calibre-plugins`, `ElendilDrac01/xteink-x3-calibre-stock` |
-| XTC format converters | `jonasdiemer/epub2xtc`, `alf-arv/epub-to-xtc-util`, `domschl/PDF2XTEink`, `smalltomatowater-boop/xtmaker` — **the stock firmware uses a proprietary `.XTC` book format**, which is why so many of these exist |
-| Font tooling | `SamLinBIT/XTEink-ttf2bin`, `iwalton3/cpfont-editor`, `enfance-prog/Xteink-Fontbuilder-mac`, `Driftrabbinate714/crossglyph` |
-| Sync / servers | `rcarmo/bun-opds-server`, `LowFlowIO/x4m`, `sroberts/shelf`, `datojulien/crosspoint-cwa-bridge` |
-| Companion apps | `lukataylo/crosspoint-mac` (Swift), `duplexer/crosspoint-companion-pro` (Kotlin), `AirBook-for-CrossPoint` (iOS) |
-| Home Assistant | `clintonmarshall/xteink-flexdisplay-ha`, `CraigBell/xteink-x3-home-assistant-dashboard`, `wiltodelta/xteink-sugartv` (CGM display) |
-| Novelty | `davidpavlicek36/doom-xt4` (**Doom**), `CidVonHighwind/xteink-bad-apple`, `cassidoo/xteink-4-in-a-row`, `HenryBaby/TamaInk` (Tamagotchi P1) |
-
-## Localisation forks — an indicator of reach
-
-The device has been localised by independent developers into at least:
-Chinese (`anki630/crossmosa` 繁體中文, `ZYFDroid`, `TrissElan/xteink-minimized-reader-cjk`),
-Japanese (`lranslot/crosspoint-reader-jp`, `iori7295/crosspoint-jp`, `feeeeeeen/XTeinkToolkit_jp`),
-Korean (`crosspoint-reader-ko`, `YMO1215/crosspoint-reader-ko-ai`),
-Arabic (`sfoulad/midad-by-foulad`),
-Russian/Ukrainian (`alpzoloto-sudo/inkmod`, `klanva/BookPoint`),
-Myanmar (`bhonemyinthtoo999-pixel/CrossPoint-Myanmar-Edition`),
-Persian, Gujarati (`monk-blade/xteink-gujarati-font-crosspoint`),
-Vietnamese (`leductho911/crossVy`), Portuguese (`carlo-z-duardo/xteink-br`).
-
-**Roughly a dozen languages ported by unrelated individuals** is a strong signal
-of install base for a device with no distributor network.
-
-## Cross-device: what the SDK also targets
-
-The same SDK carries profiles for M5Stack PaperS3 / PaperMono / PaperColor,
-LilyGo T5-S3, Seeed reTerminal Sticky, EEGO A4, OnePage C61 (ESP32-C61) and
-Murphy M3/M4. So **firmware written for the X4 Pro is portable**, and the X4 Pro
-is one node in a wider e-paper firmware ecosystem rather than an island. See
-[`../../m5stack/papermono/projects-and-community.md`](../../m5stack/papermono/projects-and-community.md).
-
-## Evidence caveat
-
-This is a **repository census**, not an audit. Repository existence proves someone
-started something; it does not prove the code builds, runs, or was ever flashed to
-an X4 Pro. Only the FreeInk SDK's own claims are marked hardware-confirmed, and
-only those are used as evidence elsewhere in this record.
diff --git a/devices/xteink/x4-pro/research-log.md b/devices/xteink/x4-pro/research-log.md
deleted file mode 100644
index 9f821a8..0000000
--- a/devices/xteink/x4-pro/research-log.md
+++ /dev/null
@@ -1,127 +0,0 @@
-# Xteink X4 Pro — research log
-
-Session **2026-09-04**. Searcher: automated agent, no hardware available.
-This log covers the whole Xteink family; device-specific results are marked.
-
-## Declared scope and cutoff
-
-- **Cutoff:** 2026-09-04.
-- **Languages:** English throughout; Chinese for brand-name and repo searches.
-- **Not searched:** FCC/CE/SRRC databases, JD.com, Taobao, AliExpress, Bilibili,
-  Zhihu, 52pojie, Baidu Tieba, YouTube (beyond links surfaced in Reddit posts).
-  These are **declared exclusions**, not "nothing found".
-
-## Source classes searched
-
-| Class | Searched | Result |
-|---|---|---|
-| Manufacturer product pages | ✅ `xteink.com` (Shopify JSON APIs) | **Useful** — the only primary source that exists |
-| Manufacturer support / wiki / manual | ✅ | **None exists.** No datasheet, no manual, no dev docs, no schematic |
-| Component-manufacturer datasheets | ⚪ deferred to component records | — |
-| Standards / certification bodies | ❌ **not searched** | No FCC ID known to query |
-| Framework / SDK documentation | ✅ FreeInk SDK, CrossPoint | **Highest-value source in the subject** |
-| Authorized distributors | ✅ none exist — vendor-direct only | — |
-| Community repositories | ✅ GitHub, 5 queries × 2 pages | ~200 relevant repos |
-| Forums | ✅ Reddit, 23 queries | 1,798 unique posts |
-| Teardowns | ✅ | 2 found — **both X3**, none for X4 Pro |
-| Archives | ⚠️ attempted, timed out | Wayback CDX |
-
-## Query ledger
-
-### Vendor store — `xteink.com`
-
-| Query | Depth | Result |
-|---|---|---|
-| `/products.json?limit=250&page=1..3` | 3 pages | 23 products; p2/p3 empty → complete |
-| `/collections.json?limit=250` | 1 | 11 collections |
-| `/collections/{machine,x4-classic,x4-series,x3-series,x4-pro-series,homepage-display,x3-edm,x4-edm,x4-proedm}/products.json` | 9 | **Established the X4 is delisted and the X4 Classic has no listed device** |
-| `https://xteink.net/`, `https://xteink.cn/` | — | **Dead** (HTTP 000). `.cn` apex unreachable *but* `bofi.xteink.cn` is embedded in the X4 firmware |
-
-### Reddit — `old.reddit.com`, UA `WhatsApp/2.23.20.0`
-
-All 23 requests returned **200**.
-
-| Query | Result |
-|---|---|
-| `search.json?q=xteink` and 12 further term queries | see below |
-| `r/xteinkereader/{new,top}`, `r/XTEINK/{new,top}`, `r/xteinkHax/{new,top}`, `r/CrossPointReader/{new,top}` | 100 each |
-| Terms used | `xteink`, `xteink x4 pro`, `xteink x3`, `xteink teardown`, `crosspoint reader`, `xteink x4c`, `xteink classic`, `xteink teardown chip`, `xteink esp32`, `xteink x5`, `xteink x2`, `xteink mini`, `xteink brand`, `xteink aliexpress`, `xteink unlock`, `xteink firmware flash`, `crossink`, `crossmux`, `xteink s4 android`, `xteink battery mah`, `xteink x4 pro chip`, `xteink brick` |
-
-**Yield: 1,798 unique posts** across `_merged-posts.json`.
-
-**Discovery worth recording:** the community is spread over **three** subreddits
-with confusingly similar names — r/XTEINK (416 posts), r/xteinkereader (406),
-r/xteinkHax (180) — plus r/CrossPointReader. Searching only one misses most of it.
-
-**Negative results, deliberately preserved:**
-- `x5` → 8 hits, **all speculation**; one self-corrected ("EDIT: It's X4 not X5")
-- `x4 mini` → 6 hits, **all colloquial**, one video body names "the XTEINK X4"
-- `x2` → 3 hits, **all false positives** ("quantity ×2")
-- `xteink teardown` → **no X4 Pro teardown exists**
-
-### GitHub — authenticated API
-
-| Query | Pages | Result |
-|---|---|---|
-| `repositories?q=xteink` | 2 | 378 total, 100/page |
-| `repositories?q=crosspoint+reader` | 2 | 105 total |
-| `repositories?q=freeink` | 2 | 17 total |
-| `repositories?q=xteink+x4` | 2 | 198 total |
-| `repositories?q=crossink` | 2 | — |
-| `code?q=FREEINK_DEVICE_X4PRO` / `XTEINK_X4_PRO` / `xteink_x4_classic` | 1 each | — |
-| Repo metadata + recursive trees | 5 repos | `XTEINK-OEM-BIN-`, `Xteink-X3`, `xteink-unlocker`, `xteink-x4`, `eink-quick-flasher` |
-
-### Dead / failed / inaccessible
-
-| Target | Outcome |
-|---|---|
-| `web.archive.org/cdx/search/cdx?url=xteink.com*` | **Timed out at 60 s, 0 bytes.** Not retried. The delisted X4 product page remains unrecovered |
-| `https://xteink.net/`, `https://xteink.cn/` | Connection failure |
-| `imgur.com/a/<id>` HTML | Returns 2 of 13 images — JS shell. **Recovered** via `imgur.com/ajaxalbums/getimages/<id>/hit.json` |
-| X4 Pro stock firmware image | **Does not exist publicly.** Searched GitHub repo names and the flasher projects; only X3/X4 images are published |
-| `xteink_app_update_x4pro_7.4.4_…xota` | Named in SDK docs; **no download URL found anywhere** |
-
-## Stopping criterion
-
-Reached the point where two consecutive broad passes returned only duplicates for
-the X4 Pro specifically: the FreeInk SDK is the sole source of board-level fact,
-and no independent corroboration (teardown, schematic, regulatory filing) exists
-to find. Remaining sources require **hardware**, **a teardown**, or **regulatory
-database access** — the first two unavailable, the third not attempted.
-
-This is a **reproducible broad-coverage snapshot dated 2026-09-04**, not proof
-that no other resource exists.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 10:* - **Not searched:** FCC/CE/SRRC databases, JD.com, Taobao, AliExpress, Bilibili,
->
-> *line 21:* | Standards / certification bodies | ❌ **not searched** | No FCC ID known to query |
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4-pro/resources-and-conflicts.md b/devices/xteink/x4-pro/resources-and-conflicts.md
deleted file mode 100644
index 64aca75..0000000
--- a/devices/xteink/x4-pro/resources-and-conflicts.md
+++ /dev/null
@@ -1,120 +0,0 @@
-# Xteink X4 Pro — resources and conflicts
-
-ESP32-S3, 16 MB flash, **8 MB PSRAM**. Snapshot **2026-09-04**.
-
-## GPIO allocation
-
-| GPIO | Owner | Exclusive? | Note |
-|---:|---|---|---|
-| 0 | Button Left → up/prev | ⚠ | **also the S3 boot strap** |
-| 1 | **Master peripheral rail**, HIGH | ✅ | asserted **first** at boot |
-| 2 | **Touch power enable, ACTIVE-LOW** | ✅ | buttons on the X4 Classic |
-| 3 | Button Power | ✅ | active-LOW |
-| 4 | GT911 RST | ✅ | |
-| 5 | **SD power enable, ACTIVE-LOW** | ✅ | buttons on the X4 Classic |
-| 6 | EPD BUSY | ✅ | busy = HIGH |
-| 7 | Button Right → down/next | ✅ | *not* a display enable — an earlier hypothesis, refuted |
-| 8 | Frontlight **cool**, LEDC ch4 | ✅ | buttons on the X4 Classic |
-| 9 | Frontlight **warm**, LEDC ch5 | ✅ | buttons on the X4 Classic |
-| 10 | GT911 INT / address select | ⚠ | **also floated as a `usbDetect` candidate — almost certainly wrong** |
-| 11 / 12 / 13 | EPD MOSI / SCLK / CS | ✅ | |
-| 14 | EPD RST | ✅ | |
-| 18 | EPD DC | ✅ | |
-| 19 / 20 | USB D− / D+ | ✅ | **never probe** |
-| 21 | Charger STAT, active-HIGH | ✅ | |
-| 38 / 39 | I²C SCL / SDA @400 kHz | ❌ **three devices** | |
-| 40 / 41 / 42 | SDMMC DAT0 / CLK / CMD | ✅ | |
-| 45 | (SD SPI CS, vestigial) | — | unused once `busWidth != 0` |
-
-**Unassigned:** `batteryAdc`, `usbDetect`, `display.powerEnable`.
-
-## Boot ordering — this is load-bearing
-
-1. **GPIO1 HIGH** — master peripheral rail. First action in board-init.
-2. **GPIO2 LOW** — touch rail on (active-low).
-3. **GPIO5** pulsed HIGH 80 ms → LOW 120 ms — SD rail, then **held LOW**.
-4. Display reset, then the controller-ID probe, then `EpdBus::begin()`.
-
-**Omitting step 1:** *"EPD BUSY never asserts, SD returns 0xFF."*
-**Getting step 2's polarity wrong:** the GT911 never ACKs; an I²C scan shows only
-0x51 and 0x63.
-**Getting step 3 wrong:** every SD block read fails with `0x107`.
-
-**Two active-LOW enables on one board is the opposite of the usual convention**
-and is the single most common source of bring-up failure here.
-
-## Shared buses
-
-| Bus | Devices | Arbitration |
-|---|---|---|
-| **I²C 39/38 @400 kHz** | [GT911](../../../components/goodix/gt911/README.md) 0x5D · [BM8563](../../../components/generic/bm8563/README.md) 0x51 · [CW2017](../../../components/cellwise/cw2017/README.md) 0x63 | **One Arduino `Wire` controller** (`i2cBus = 0`). A stalled bus blocks touch, clock **and** battery |
-| Display SPI 12/11/13 | EPD only | Dedicated. **Unlike the C3 models, the SD card does not share it** |
-| SDMMC 41/42/40 | microSD only | Dedicated, 1-bit |
-
-**The display and storage buses being independent is the X4 Pro's main structural
-advantage over the [X4](../x4/resources-and-conflicts.md) and
-[X3](../x3/resources-and-conflicts.md)**, where a card read stalls the panel.
-
-## Peripheral resources reserved
-
-| Resource | Owner |
-|---|---|
-| **LEDC channels 4 and 5** | Frontlight cool/warm. Do not reuse for other PWM |
-| **SDMMC slot 1** | microSD |
-| Native USB peripheral | CDC (and MSC in stock, unported) |
-| DMA | **Both** the display path and SDMMC. Reads/writes bounce through a `MALLOC_CAP_DMA` buffer because SdFat's caches may sit in **PSRAM** or be unaligned |
-
-## Memory
-
-| Resource | Value |
-|---|---|
-| SRAM | 512 KB (ESP32-S3) |
-| **PSRAM** | **8 MB, octal** |
-| Flash | 16 MB |
-| App partitions | 2 × 8064 KiB (dual-OTA) |
-| SPIFFS | **80 KiB** — 40× smaller than the X4's |
-
-PSRAM is why multi-buffer rendering and damage-window partial refresh are viable
-here and not on the C3 models. It is also why the **DMA bounce buffer is
-mandatory**: an SdFat cache allocated in PSRAM is not DMA-capable.
-
-## Strap and USB hazards
-
-| Pin | Hazard |
-|---|---|
-| **GPIO0** | Boot strap **and** the Left button. Powering on with Left held enters download mode |
-| **GPIO19/20** | Native USB D−/D+. The **C3 Xteink device fingerprint pokes SDA 20 / SCL 0**, which on this S3 lands on **D+ and a boot strap**. `XteinkDetect` compiles that path out unless a C3 profile is in the build — **a build defining both a C3 and this profile would be dangerous** |
-
-## Cross-model porting hazards
-
-| Pin | X4 Pro | X4 Classic | Consequence of porting blindly |
-|---:|---|---|---|
-| 2 | Touch power (out, active-LOW) | **Button** (in) | Driving a button pin as an output |
-| 5 | SD power (out, active-LOW) | **Button** (in) | Same |
-| 8 / 9 | **Frontlight PWM** (out) | **Buttons** (in) | LEDC configured on button inputs |
-| 6 | **EPD BUSY** (in) | **SD power** (out) | Panel never appears ready |
-| 14 | **EPD RST** | **EPD DC** | Panel resets and never develops an image |
-| 18 | **EPD DC** | **EPD BUSY** | Same |
-| 10 | **GT911 INT** | **EPD RST** | Same |
-
-**Seven pins change meaning between two boards that share a chassis, a panel and
-an SoC.** Always gate on `FREEINK_CAP_TOUCH` / `FREEINK_CAP_FRONTLIGHT` and take
-pins from the active `BoardProfile`, never from a constant.
-
-## Realistic concurrent-use scenarios
-
-| Scenario | Assessment | Status |
-|---|---|---|
-| Display refresh **+** SD read | Independent buses, but **both DMA-heavy**; SD adds a bounce copy | **Not benchmarked** |
-| Touch poll **+** RTC read **+** gauge read | One `Wire` controller, sequential | **Not benchmarked** |
-| Frontlight PWM **+** Wi-Fi | LEDC + radio on one battery of **unknown capacity** | **Not benchmarked** |
-| BLE **+** Wi-Fi | One 2.4 GHz radio, shared | **Not benchmarked** |
-| Deep sleep | Enables driven to off level **by polarity** (GPIO2/5 → HIGH) | Implemented; **power draw never checked** |
-
-## Unresolved
-
-- **`usbDetect`** — unassigned; GPIO10 floated as a candidate but it is already
-  the GT911 INT. Treat that candidacy as wrong.
-- **`batteryAdc`** — not isolated. Battery percentage comes from the CW2017.
-- **Touch `flipX`/`flipY`** — the SDK's header and its own device document
-  disagree. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
diff --git a/devices/xteink/x4-pro/sources.md b/devices/xteink/x4-pro/sources.md
deleted file mode 100644
index 082b8ae..0000000
--- a/devices/xteink/x4-pro/sources.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Xteink X4 Pro — sources
-
-All retrievals **2026-09-04** unless stated. Class ∈ {primary, authorized mirror,
-credible mirror, standard, community}.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published/updated | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **XP01** | `freeink-sdk` `BoardConfig.h`, `XTEINK_X4_PRO` profile L1495–1613 | Free-Ink project | community | source file (commit-pinned) | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L1495-L1613> | 2026-09-04 | commit `2400379`, 2026-09-01 | **Every pin, bus, address and fitted part.** The single most important source | Third-party RE, not vendor documentation. Distinguishes hardware-confirmed from inferred, which is why it is trusted | `scratch/eink-software/repos/freeink-sdk/` |
-| **XP02** | `docs/xteink-x4pro-support.md` | Free-Ink project | community | technical note | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/docs/xteink-x4pro-support.md> | 2026-09-04 | same commit | Bring-up narrative, OEM command streams, IROM offsets, partition table, corrections | Explicitly marks Confirmed / Corrected / Pending — **use those labels** | same clone |
-| **XP03** | `XteinkDetect.cpp` | Free-Ink project | community | source file | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/XteinkDetect/src/XteinkDetect.cpp> | 2026-09-04 | same commit | The three-controller boot probe, the `VER`/`FLG` matcher, and the negative result about `CHIP_VER = 0x00` | — | same clone |
-| **XP04** | `platformio.sample.ini` `[env:x4pro]` | Free-Ink project | community | build config | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/platformio.sample.ini> | 2026-09-04 | same commit | Board target `esp32-s3-devkitc1-n16r8`, build flags | — | same clone |
-| **XP05** | Shopify product record `xteink-x4-pro-pocket-ereader` | Xteink | **primary** | store API | <https://www.xteink.com/products.json?limit=250> | 2026-09-04 | created 2026-07-07, published 2026-07-21 | SKU, single Space Black variant, **$99.00**, in stock, packaged weight 250 g | **Body prose is AI/SEO boilerplate and is not evidence.** Structured fields only | `scratch/xteink/vendor/products-p1.json` |
-| **XP06** | Shopify collections | Xteink | **primary** | store API | <https://www.xteink.com/collections.json?limit=250> | 2026-09-04 | — | The vendor's own product-line list, incl. `x4-pro-series` and `x4-classic` | — | `scratch/xteink/vendor/collections.json` |
-| **XP07** | `x4-pro-series` collection contents | Xteink | **primary** | store API | <https://www.xteink.com/collections/x4-pro-series/products.json?limit=250> | 2026-09-04 | — | Accessory pricing and per-variant stock; matte protectors sold out | — | `scratch/xteink/vendor/coll-x4-pro-series.json` |
-| **XP08** | "X4 Pro doesn't use USB-C for charging—it uses the magnetic pogo adapter" | r/xteinkereader | community | forum thread | <https://old.reddit.com/r/xteinkereader/comments/1v2txxe/> | 2026-09-04 | 2026-07-21, 9 pts, **71 comments** | Firsthand ownership: the charge path is pogo-only | Opinion-heavy. Establishes the fact, not its prevalence | `scratch/xteink/reddit/_merged-posts.json` |
-| **XP09** | "Did we just spot a new X4 model? Physical buttons + frontlight but no touchscreen" | r/XTEINK | community | forum thread | <https://old.reddit.com/r/XTEINK/comments/1ud0d9c/> | 2026-09-04 | 2026-06-22, **300 pts**, 53 comments | Community identified unannounced hardware in a vendor video ~1 month before launch | Interpretation of a video, not a teardown | same |
-| **XP10** | "CrossPoint 1.5 has officially been released!" | r/xteinkereader | community | forum thread | <https://old.reddit.com/r/xteinkereader/comments/1vhvtdd/> | 2026-09-04 | 2026-08-07, **763 pts**, 305 comments | *"Other forks will need to pull the latest SDK to avoid soft bricking locked units"* | Developer statement; not independently verified | same |
-| **XP11** | "To everyone who has donated to CrossPoint" | r/xteinkereader | community | forum thread | <https://old.reddit.com/r/xteinkereader/comments/1tl3gnn/> | 2026-09-04 | 2026-05-23, 346 pts | **OTA unlock for USB-locked stock devices** exists at crosspointreader.com | Project self-description | same |
-| **XP12** | "Tips after 1 Week and 2 Books" | r/XTEINK | community | forum thread | <https://old.reddit.com/r/XTEINK/comments/1uz8yiz/> | 2026-09-04 | 2026-07-17, **723 pts** | The three community service sites: brickclub.pages.dev, crossink.uxj.io, crosspointreader.com | Owner report | same |
-| **XP13** | GitHub repository census | GitHub | community | API search | `api.github.com/search/repositories` ×5 queries ×2 pages | 2026-09-04 | — | ~200 repos targeting the family | Search-ranked, not exhaustive | `scratch/xteink/github/_all-repos.json` |
-| **XP14** | `MrStu82/crosspoint-llama-pro` | community dev | community | repository | <https://github.com/MrStu82/crosspoint-llama-pro> | 2026-09-04 | pushed 2026-08-31 | An X4 Pro-specific firmware fork naming *"ESP32-S3, GT911 touch, dual warm/cold frontlight"* — third-party corroboration of the hardware profile | Personal fork | — |
-| **XP15** | `HomeAssistantPi/xteink-backup-utility` | community dev | community | repository | <https://github.com/HomeAssistantPi/xteink-backup-utility> | 2026-09-04 | pushed 2026-08-10 | The only X4 Pro-specific flash/backup tool located | Not inspected in depth | — |
-| **XP16** | CrossPlay record (this knowledge base) | this repo | — | internal | [`software/applications/crossplay/README.md`](../../../software/applications/crossplay/README.md) | 2026-09-04 | written 2026-09-02 | X4 Pro is the ecosystem "design floor"; the C3-image-onto-S3 OTA hazard | Internal cross-reference | in repo |
-
-## Sources deliberately **not** used as evidence
-
-| Source | Why rejected |
-|---|---|
-| `xteink.com` product description prose | AI/SEO-generated. Demonstrably wrong elsewhere in the catalogue (the X3 listing advertises a frontlight and cloud sync it does not have) |
-| `aimindseye/xteink-x4` wiki | Self-labelled "clawbot-managed", AI-generated, contains no primary measurement. Retained in scratch as evidence of community understanding, not of hardware |
-
-## Not searched to completion
-
-FCC / CE / SRRC databases; JD.com, Taobao and AliExpress listings; Bilibili,
-Zhihu, 52pojie and Tieba. See [`research-log.md`](research-log.md).
-
----
-
-## Round 2 — sources added 2026-09-11
-
-**No row above was altered.**
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published | Establishes | Scope/limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **XP-R2-01** | FCC ID `2BTR9-X4PRO` record | US FCC via fccid.io | **primary (regulatory)** | regulatory record | <https://fccid.io/2BTR9-X4PRO> | 2026-09-11 | granted **2026-06-16** | Legal applicant, FRN, DTS 2412–2462 MHz, exhibit list, **internal photos public 2026-12-12**, schematics permanently confidential | Mirror of the FCC EAS; `apps.fcc.gov` 403. Requires UA `WhatsApp/2.23.20.0` | `scratch/xteink/fcc/fccid-io-2BTR9-X4PRO.html` |
-| **XP-R2-02** | X4 Pro External Photos | applicant, filed with the FCC | **primary** | photographs | <https://fccid.io/2BTR9-X4PRO/External-Photos/External-Photos-9386963.pdf> | 2026-09-11 | 2026-06-16 | 7 exterior images to 5712×4284 @ 1107 ppi against a rule | Exterior only | `artifacts/certification/2BTR9-X4PRO-external-photos.pdf` |
-| **XP-R2-03** | X4 Pro Label and Information | applicant | primary | photographs | <https://fccid.io/2BTR9-X4PRO/Label/Label-and-Information-9386964.pdf> | 2026-09-11 | 2026-06-16 | Label artwork and placement | — | `artifacts/certification/2BTR9-X4PRO-label.pdf` |
-| **XP-R2-04** | `x4pro-emu` — device inventory | kycube | **community, firsthand hardware** | repository doc | <https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/inventory.md> | 2026-09-11 | captured 2026-09-06 | `esptool chip-id` on a physical unit: ESP32-S3 QFN56 rev v0.2, 8 MB embedded PSRAM AP_3v3, 40 MHz crystal, USB-Serial/JTAG, MAC `98:c3:77:be:ea:30` | **One unit.** Repo has **no licence** → redistribution `unknown`; referenced, not vendored | `scratch/xteink/github-2026-09-11/x4pro-emu/` |
-| **XP-R2-05** | `x4pro-emu` — `chip_id.txt`, `efuse-summary.txt`, `efuse-dump.txt` | kycube | community, firsthand hardware | tool output | <https://github.com/kycube/x4pro-emu/tree/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device> | 2026-09-11 | 2026-09-06 | eFuse state: **no secure boot, no flash encryption**, all key purposes USER, USB-JTAG enabled; BLOCK3 serial `X4CB02EN26082416646` | same | same |
-| **XP-R2-06** | `x4pro-emu` — `partitions.md` | kycube | community, firsthand hardware | analysis of a flash dump | <https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/partitions.md> | 2026-09-11 | dump 2026-09-06 | Full partition table, `otadata` state, **`xteink_app` 7.2.4 / ESP-IDF v6.0.1 built 2026-08-14**, NVS namespaces, `hw_calib/screenType=2` → UC8279, and the four board tags in one binary | The dump itself is **not published** (proprietary, contains Wi-Fi credentials) — only its analysis | same |
-| **XP-R2-07** | `x4pro-emu` — `flash-backup-sha256.txt` | kycube | community, firsthand hardware | checksums | <https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/device/flash-backup-sha256.txt> | 2026-09-11 | 2026-09-06/07 | **Two dumps of the same device hashing identically** — `9073455479…0143fe` | The images are gitignored; only hashes are public | same |
-| **XP-R2-08** | `x4pro-emu` — `docs/hardware.md` | kycube | community, firsthand hardware | repository doc | <https://github.com/kycube/x4pro-emu/blob/bf4b86ae0471012d4d07c0bb3042f3f561c9c302/docs/hardware.md> | 2026-09-11 | 2026-09-07 | I²C map on the live bus, GT911 Home-pad mechanism, LEDC frontlight fade behaviour, the stock UC8279 command stream, SPI2 at 10 MHz / 38 ms per plane, and the finding that the **support doc's INT/RST are swapped** | Cites FreeInk for the **pin assignment**, so the pinout is *not* independently corroborated | same |
-| **XP-R2-09** | Draftling `HARDWARE.md`, X4 Pro chapter | clackups | **community, on-hardware** | repository doc | <https://github.com/clackups/draftling/blob/92ba7e514f66bbe42a7fea6d38eff45eed82617b/HARDWARE.md> | 2026-09-11 | 2026-09-11 | *"tested on physical hardware"*; a real async-DMA bug in the UC8179/UC8279 full-refresh path; a **touch-orientation correction contradicting FreeInk's "confirmed" annotation**; the OEM 5 MHz SPI choice; the dual-OTA rationale | MIT. Pin data still derived from FreeInk | `scratch/xteink/github-2026-09-11/draftling/HARDWARE.md` |
-| **XP-R2-10** | `BoardConfig.h` at SDK HEAD | Free-Ink | community | source (commit-pinned) | <https://github.com/Free-Ink/freeink-sdk/blob/9f4d3f9ca675e64cc9d616081f39a33cdefce57e/libs/hardware/BoardConfig/include/BoardConfig.h> | 2026-09-11 | commit 2026-09-10 | `displaySpiHz` 20 → **10 MHz** for every Xteink profile | Same lineage as the existing rows | `scratch/xteink/sdk-2026-09-11/BoardConfig-9f4d3f9.h` |
diff --git a/devices/xteink/x4/README.md b/devices/xteink/x4/README.md
deleted file mode 100644
index ca65521..0000000
--- a/devices/xteink/x4/README.md
+++ /dev/null
@@ -1,307 +0,0 @@
-# Xteink X4
-
-> **Delisted from the vendor store as of 2026-09-04** — accessories only, and
-> every X4 accessory is sold out. Was $69. ESP32-C3, 4.26″ 800×480.
-> Research retrieval date **2026-09-04**.
-
-## Identity and variants
-
-| Field | Value | Evidence |
-|---|---|---|
-| Marketed name | **Xteink X4** (community nickname "X4 mini" — **not a SKU**) | **[VENDOR]**, **[COMM]** |
-| Chinese name | **星瞳 X4** ("Star Pupil") | **[COMM]** [r/ereader `1n5kmpc`](https://old.reddit.com/r/ereader/comments/1n5kmpc/) |
-| FreeInk profile | `BoardConfig::XTEINK_X4`, name string `xteink_x4` | **[SDK]** `BoardConfig.h:844–874` |
-| Build flag | `-DFREEINK_DEVICE_X4=1` | **[SDK]** |
-| Board tag in a sibling dump | `ESP32S3_X4_TL` appears in the **X4 Pro's** app0 — that is an *S3* variant string and is **not** this C3 device | **[SDK]** |
-| Colours | at least **Space Black** and a white/grey; the magnetic case shipped in 7 colours | **[VENDOR]** accessory variants |
-| Lifecycle | Launched ~Sept 2025 · **delisted before 2026-09-04** | **[VENDOR]** |
-
-### Physical (community-measured, single source)
-
-| Property | Value | Evidence |
-|---|---|---|
-| Dimensions | ≈ **114 × 70 × 7 mm** (4.5 × 2.75 × 0.25 in) | **[COMM]** [r/Ultralight `1r1jfny`](https://old.reddit.com/r/Ultralight/comments/1r1jfny/), 2026-02-11 |
-| Mass | **80 g** including screen protector | same |
-| Display | **220 PPI** | same |
-| Controls | **4 front-facing buttons + 3 on the right side** | same |
-
-The vendor calls it a **4.3-inch** model (founder, [r/ereader `1o2203h`](https://old.reddit.com/r/ereader/comments/1o2203h/));
-the panel is a 4.26″ class part. 800×480 across 4.26″ diagonal = **219 PPI**,
-which agrees with the owner's 220 — the two independent figures corroborate.
-
-**Single-source caveat:** the dimensions and mass come from **one** owner post.
-No vendor spec sheet was found.
-
-## What it is and visual identification
-
-The original Xteink: a pocket e-reader roughly the size of a large phone, with
-**four buttons on the front face and three on the right edge**, a **USB-C port**,
-and a magnetic back designed to stick to the back of a phone (MagSafe-style).
-It has **no touchscreen, no frontlight and no RTC**.
-
-The MagSafe-on-your-phone use case is how it was marketed and how owners describe
-it: *"meant to be attached on the backside of your phone using MagSafe so you can
-just flip your phone around and just read"*
-([r/eink `1sba4am`](https://old.reddit.com/r/eink/comments/1sba4am/)).
-
-## Product history, family and culture
-
-| Date | Event | Evidence |
-|---|---|---|
-| 2025-09-01 | First English-language impressions post, titled "Xteink Star Pupil X4 (星瞳X4)" | **[COMM]** [r/ereader `1n5kmpc`](https://old.reddit.com/r/ereader/comments/1n5kmpc/) |
-| 2025-10-09 | Founder "Crusoe" introduces the company on Reddit, 1,477 pts, describing the X4 as their 4.3-inch model | **[COMM]** [r/ereader `1o2203h`](https://old.reddit.com/r/ereader/comments/1o2203h/) |
-| 2025-10-21/23 | X4 magnetic case and tempered-glass protector listed | **[VENDOR]** |
-| 2025-12-09/11 | X3 announced as the smaller successor — *"builds on everything we learned from building the X4"* | **[COMM]** [`1pi6ezd`](https://old.reddit.com/r/xteinkereader/comments/1pi6ezd/) |
-| 2025-12 | CrossPoint custom firmware for the X4 appears | **[COMM]** community digest |
-| 2026-01-21 | X4 protective case listed | **[VENDOR]** |
-| 2026-07-08 | X4 matte screen protector listed — **the last X4 accessory added** | **[VENDOR]** |
-| 2026-07-21 | X4 Pro launches | **[VENDOR]** |
-| **2026-09-04** | **X4 device absent from the catalogue. All 4 X4 accessory SKUs sold out** | **[VENDOR]** |
-
-**The X4 is the device that created the ecosystem.** Nearly every firmware project
-in the family started as "firmware for the Xteink X4" and grew to cover the X3 and
-the S3 devices afterwards.
-
-## Key specifications
-
-| Item | Value | Component record | Evidence |
-|---|---|---|---|
-| SoC | **ESP32-C3** (RISC-V), 16 MB external flash, **no PSRAM** | [`espressif/esp32-c3`](../../../components/espressif/esp32-c3/README.md) | **[SDK]**, **[DUMP]** chip-id 5, **[TD]** X3 sibling |
-| Flash | **128 Mbit (16 MB)** SPI NOR, **Puya** | [`unidentified/xteink-x3-x4/spi-nor-flash-128mbit-puya`](../../../components/unidentified/xteink-x3-x4/spi-nor-flash-128mbit-puya/README.md) | **[TD]** (X3 board; assumed shared) |
-| Display | 800×480 mono e-ink, 4.26″, ~219 PPI | — | **[SDK]** `:848–849` |
-| Controller | **SSD1677**, or **UC8179**/**UC8279** on newer batches | [`solomon-systech/ssd1677`](../../../components/solomon-systech/ssd1677/README.md) · [`ultrachip/uc8179`](../../../components/ultrachip/uc8179/README.md) · [`ultrachip/uc8279`](../../../components/ultrachip/uc8279/README.md) | **[SDK]** |
-| Touch | **none** (`NO_TOUCH`) | — | **[SDK]** |
-| Frontlight | **none** (`NO_FRONTLIGHT`) | — | **[SDK]** |
-| **RTC** | **NONE** — `sensors = NO_SENSORS` | — | **[SDK]** `:866` |
-| **Fuel gauge** | **NONE** — `NO_GAUGE`; battery read by **ADC on GPIO0**, ×2.0 divider | — | **[SDK]** `:854–856, 864` |
-| Storage | microSD over **SPI, sharing the display bus** | — | **[SDK]** `:852` |
-| USB | USB-C, ESP32-C3 USB-serial-JTAG; `usbDetect = GPIO20` | — | **[SDK]** `:855`… see note |
-| Charging | **USB-C** — unlike the X3 and X4 Pro | — | **[COMM]** |
-| Battery latch | **GPIO13** gates the battery MOSFET | — | **[SDK]** `:868–874` |
-| IMU / NFC | **none** | — | **[SDK]** |
-| Radios | Wi-Fi + BLE (ESP32-C3 integrated) | — | inferred |
-
-**The X4 is the most stripped-down member of the family.** No RTC, no fuel gauge,
-no IMU, no NFC, no touch, no frontlight — the X3, which is *cheaper*, has four of
-those six.
-
-## Architecture and components
-
-```
-ESP32-C3 ── SPI ──┬── EPD controller (SSD1677│UC8179│UC8279) ── 800×480 glass
-                  │      SCLK 8 / MOSI 10 / CS 21 / DC 4 / RST 5 / BUSY 6
-                  └── microSD  (SAME bus: SCLK 8 / MOSI 10, MISO 7, CS 12)
-         ├─ ADC ladder ── GPIO1 (Back/Confirm/Left/Right) + GPIO2 (Up/Down)
-         ├─ GPIO3 ─────── Power button (active-LOW)
-         ├─ GPIO0 ─────── Battery voltage ADC (÷2 divider)
-         └─ GPIO13 ────── Battery MOSFET latch
-```
-
-**One SPI bus serves both the panel and the SD card.** They are not independent:
-`sd.separateSpi = false`. Any long card transfer blocks display updates and vice
-versa. This is the structural difference from the S3 devices, which have a
-dedicated SDMMC slot.
-
-**Six buttons on two ADC pins**, not six GPIOs. See
-[`features/buttons.md`](features/buttons.md).
-
-Full tables: [`pinouts-and-buses.md`](pinouts-and-buses.md).
-
-## Distinctive strengths
-
-- **USB-C charging** — the only member of the family with it, and the reason
-  several owners refuse to upgrade to the X4 Pro.
-- **The largest firmware ecosystem** of any device here; most projects target it
-  first.
-- **A complete 16 MB factory flash dump is publicly available and archived here** —
-  uniquely among Xteink devices.
-- Cheap and, latterly, very cheap secondhand.
-
-## Shortcomings and constraints
-
-- **Discontinued.** No new stock from the vendor; accessories exhausted.
-- **No RTC and no fuel gauge.** Battery percentage is an ADC estimate; the clock
-  is lost on power loss.
-- **SD shares the display SPI bus.**
-- **No PSRAM.** CrossPoint moved off GitHub releases partly because of
-  out-of-memory problems on the C3 devices.
-- **Ships USB-locked** on many units.
-- **A hardware revision exists that does not self-latch** — see below.
-
-### The self-latch revision, a genuine field hazard
-
-> "GPIO13 gates the battery MOSFET. Known units self-latch through a pull once the
-> power button bridges the rail, so firmware never had to assert it — but **at
-> least one hardware revision in the field does not self-latch and stays powered
-> only while the button is held.** Asserting the latch is a no-op on self-latching
-> units. Driving it LOW is the battery power-off."
-> — **[SDK]** `BoardConfig.h:868–874`
-
-So there are **at least two X4 board revisions**, they are **not externally
-distinguishable**, and firmware that does not assert GPIO13 will appear to work on
-one and be unusable on the other. Always assert the latch.
-
-## Performance summary
-
-| Figure | Value | Status |
-|---|---|---|
-| Display SPI, FreeInk default | **20 MHz** = SSD1677 datasheet write max | in-spec |
-| Plane write @20 MHz | **~38 ms/refresh** | **[SDK]** measured comment |
-| Optional overclock | **40 MHz** via `-DFREEINK_X4_OVERCLOCK_SPI` | **out of spec (2× datasheet)** |
-| Plane write @40 MHz | **~19 ms** — saves ~17–20 ms/refresh | **[SDK]** |
-
-The 40 MHz mode is what the **CrossPoint / Witch Reader** fork used. The SDK
-makes it opt-in and warns it "can glitch plane writes on marginal wiring". This is
-the clearest performance/reliability trade-off documented anywhere in the family.
-
-## Pricing and availability
-
-**Delisted.** Last vendor price **$69.00** (community-reported 2026-07-24).
-Every X4 accessory shows sold out on 2026-09-04. Secondhand is now the only
-channel; one X3 was reported at **$16**, which suggests the used market for these
-is very soft. See [`market-and-pricing.md`](market-and-pricing.md).
-
-## When to use / when not to use
-
-**Use it** if you find one cheap and want the best-supported target in the
-ecosystem with USB-C charging. **Do not use it** if you need PSRAM, an RTC, a real
-fuel gauge, or a device you can still buy new.
-
-## Alternatives by tier
-
-| Tier | Alternative |
-|---|---|
-| Still purchasable, same class | [X3](../x3/README.md) $69 — sharper screen, IMU, NFC, RTC, real gauge, but pogo charging |
-| More powerful, still a reader | [X4 Pro](../x4-pro/README.md) $99 — S3, PSRAM, touch, frontlight; **pogo charging** |
-| Development platform | [M5Stack PaperMono](../../m5stack/papermono/README.md) — schematic, headers, USB-C |
-
-## Images and teardown/PCB views
-
-**No X4 teardown was located.** The [X3 teardowns](../x3/media.md) show a related
-but different board. See [`media.md`](media.md).
-
-## Common tasks / How do I…?
-
-| Task | Guide |
-|---|---|
-| Drive the display, handle the controller variants | [`features/display.md`](features/display.md) |
-| Read the 6-button ADC ladder | [`features/buttons.md`](features/buttons.md) |
-| Mount the microSD on the shared SPI bus | [`features/storage.md`](features/storage.md) |
-| Read battery voltage, hold the power latch | [`features/battery-and-power.md`](features/battery-and-power.md) |
-| Use USB-C | [`features/usb.md`](features/usb.md) |
-| Use Wi-Fi / BLE | [`features/wifi-and-bluetooth.md`](features/wifi-and-bluetooth.md) |
-| Build and flash | [`development.md`](development.md) |
-| **Dump / restore stock firmware** | [`factory-firmware.md`](factory-firmware.md) |
-
-## Documentation map
-
-[`pinouts-and-buses.md`](pinouts-and-buses.md) ·
-[`development.md`](development.md) ·
-[`factory-firmware.md`](factory-firmware.md) ·
-[`sources.md`](sources.md) ·
-[`coverage.md`](coverage.md) ·
-[`compatibility-and-status.md`](compatibility-and-status.md) ·
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md) ·
-[`market-and-pricing.md`](market-and-pricing.md) ·
-[`media.md`](media.md) ·
-[research log](../x4-pro/research-log.md) and
-[commands](../x4-pro/commands.md) are family-wide and kept once, under the X4 Pro.
-
-## Artifact layout
-
-```
-artifacts/firmware/
-└── xteink-x4-oem-full-flash-16mb.bin          → archived (symlink)
-    xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md
-```
-
-**The only Xteink factory firmware image obtained by this session.**
-16,777,216 B · SHA-256 `b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245`
-· retrieved 2026-09-04. Full analysis in
-[`factory-firmware.md`](factory-firmware.md); recovery instructions in the
-[placeholder](artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md).
-
-## Known conflicts and unresolved identities
-
-See [`gaps-and-conflicts.md`](gaps-and-conflicts.md). Headline: **the exact
-ESP32-C3 package variant and the exact Puya flash part number have never been
-read** — both are family-level identifications from a photograph caption, not part
-numbers. And the stock firmware's on-screen version (V5.x) **cannot be recovered
-from the app descriptor**, which reports the Arduino lib-builder identity instead.
-
----
-
-## Round 2 — appended 2026-09-11: FCC internal photographs, and the X4 is withdrawn
-
-**No line above was altered.**
-
-### Withdrawn, completely
-
-On 2026-09-04 the X4's product record was already absent from the vendor API and
-its four dedicated accessories were listed but sold out. On **2026-09-11** those
-four accessory records are **gone from the catalogue entirely**:
-`xteink-x4-matte-screen-protector`, `xteink-x4-protective-case`,
-`xteink-x4-screen-protector`, `xteink-x4-magnetic-case`.
-
-The `x4-series` collection now contains **two generic items** — a magnetic
-reading light and an adhesive metal ring — both of which fit any device in the
-family. The vendor's device-only `machine` collection contains **X3, X4 Classic,
-X4 Pro** and no X4.
-
-**Its successor is the [X4 Classic](../x4-classic/README.md)**, listed
-2026-09-06 at US$79, marketed by the vendor as "X4 V2". It keeps the buttons-only
-reading model and the four bottom keys, moves to an ESP32-S3 with 8 MB PSRAM and
-native SDMMC — and **drops USB-C for a pogo connector**, which is the single most
-complained-about change in the family's history
-([r/xteinkereader `1wagbmu`](https://old.reddit.com/r/xteinkereader/comments/1wagbmu/),
-2026-09-08, **616 points / 730 comments**).
-
-**The X4 is the only Xteink reader that ever had USB-C.** That is now a
-historical fact rather than a purchasing option.
-
-### A regulatory teardown, public since 2026-07-04
-
-| Field | Value |
-|---|---|
-| **FCC ID** | **`2BTR9-XTEINKX4`** |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd., FRN `0037772233` |
-| Granted | **2026-01-05** |
-| Equipment class | DTS, 2412–2462 MHz |
-| **Internal Photos** | **public since 2026-07-04** |
-| Users Manual | **public since 2026-07-04** |
-| Schematics · Block Diagram · Operational Description | **permanently confidential** |
-| Source | <https://fccid.io/2BTR9-XTEINKX4> |
-
-Retained: `artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf`,
-770,254 B, SHA-256
-`fd1623a7c9df42ba8140cea6d2618722726c1f442209c02f8229c1b50658f370`,
-**15 embedded images**, from
-<https://fccid.io/2BTR9-XTEINKX4/Internal-Photos/Internal-Photos-8956380.pdf>,
-retrieved 2026-09-11 with UA `WhatsApp/2.23.20.0`. Validated `%PDF`.
-
-**One image was inspected; the set was not systematically read.** What was seen,
-stated as an observation and not as an identification:
-
-- A green PCB carrying a **meandering PCB trace antenna**, a shielded module area
-  with an Espressif-logo QFN part, a **40.000 MHz crystal** and an 8-pin SOIC
-  flash package.
-- A separate board section carrying a **USB-C receptacle**.
-- A wide FPC connector (display) and a second smaller FPC connector.
-
-This is consistent with everything this record already says — ESP32-C3, 16 MB
-SPI flash, USB-C — and **corroborates it from a regulatory photograph rather than
-from a firmware image for the first time**. It is not a component identification:
-no top marking was transcribed, because the resolution and angle do not support
-it without careful work that this pass did not do.
-
-**Next session:** read all 15 images against
-[`pinouts-and-buses.md`](pinouts-and-buses.md) and
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md), and against
-[`components/unidentified/xteink-x3-x4/`](../../../components/unidentified/xteink-x3-x4/README.md) —
-**the four unidentified parts in that record are exactly what these photographs
-are for.**
-
-The public `Users Manual`
-(<https://fccid.io/2BTR9-XTEINKX4/User-Manual/Users-Manual-8956383.pdf>) was
-**not fetched** and is the vendor's own documentation for a device whose store
-page no longer exists.
diff --git a/devices/xteink/x4/acquisition/README.md b/devices/xteink/x4/acquisition/README.md
deleted file mode 100644
index f91d43a..0000000
--- a/devices/xteink/x4/acquisition/README.md
+++ /dev/null
@@ -1,52 +0,0 @@
-# Xteink X4 — acquisition
-
-## Clean-clone commands, in execution order
-
-The one tracked artifact for this device is **archived**, so a clean clone sees a
-placeholder plus a symlink. To reacquire it:
-
-```bash
-# 1. The 16 MB OEM full-flash dump. No auth needed.
-mkdir -p devices/xteink/x4/artifacts/firmware
-curl -fsSL "https://raw.githubusercontent.com/abhishek-nerella/XTEINK-OEM-BIN-/main/flash.bin" \
-     -o devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin
-
-# 2. Verify before trusting it.
-sha256sum devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin
-# expect: b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245
-stat -c%s devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin
-# expect: 16777216
-```
-
-**Expected failure mode:** the upstream repository is a single person's
-re-upload of proprietary vendor firmware with no licence and no mirror. If it
-disappears, the fallbacks in the
-[placeholder](../artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md)
-are the only route, and one of them (`zocs/eink-quick-flasher`) offers a
-**different, non-identical** artifact — OTA app images, not a full flash.
-
-## Licensing and disposition
-
-| Artifact | Licence | Redistribution | Disposition |
-|---|---|---|---|
-| `xteink-x4-oem-full-flash-16mb.bin` | **None declared.** Vendor firmware re-uploaded by a third party | **unknown, probably prohibited** | `local-cache` (archived), **unstaged pending user review** |
-
-The upstream repository has **no LICENSE file** and a 55-byte README. This is
-proprietary firmware; treat it as all-rights-reserved.
-
-## Not downloaded, and why
-
-| Artifact | Status | Reacquisition |
-|---|---|---|
-| `x4_en_v5.1.6_ota.bin`, `x4_cn_v5.2.13_ota.bin` | **Git LFS pointers** in `zocs/eink-quick-flasher`; the ~130-byte pointers were seen, the blobs were not fetched | **`manual`** — needs `git lfs` or the LFS batch API. **Cheap to close** |
-| X4 SPIFFS contents (3.4 MB, `0xC90000`) | Present *inside* the archived dump but never extracted | **`automatic`** — extract from the held image |
-| Vendor OTA feed response | `http://gotaserver.xteink.com/api/check-update` | **`manual`** — request format unknown; contacting a vendor server was out of scope |
-| Delisted X4 product page + imagery | Wayback CDX **timed out** | **`blocked`** — retry with a longer timeout or `matchType=prefix` |
-| Any X4 teardown photograph | **Does not exist** | **`lost`** |
-
-## Verification
-
-```bash
-python3 tools/archive_artifact.py --repo-root . --manifest <manifest> --verify
-python3 tools/audit_archive.py
-```
diff --git a/devices/xteink/x4/acquisition/manifest.json b/devices/xteink/x4/acquisition/manifest.json
deleted file mode 100644
index e42a74f..0000000
--- a/devices/xteink/x4/acquisition/manifest.json
+++ /dev/null
@@ -1,349 +0,0 @@
-{
-  "device": "xteink/x4",
-  "generated": "2026-09-04",
-  "artifacts": [
-   {
-     "id": "fcc-2BTR9-XTEINKX4-8956374",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX4/Test-Report/ANT-Test-Report-8956374.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956374",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956374.pdf",
-      "https://fccid.io/2BTR9-XTEINKX4",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/Test-Report/ANT-Test-Report-8956374.pdf"
-     ],
-     "sha256": "b873e75cdbdd8594e6e81328a42fc0f4dd1321c581c46bab9a41f183575dd105",
-     "bytes": 2034400,
-     "destination": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-01-05",
-     "fcc_id": "2BTR9-XTEINKX4",
-     "fcc_document_id": "8956374",
-     "exhibit_type": "Test Report",
-     "exhibit_title_as_filed": "ANT Test Report",
-     "grant_date": "2026-01-05",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf",
-     "placeholder": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x4",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX4-8956379",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX4/External-Photos/External-Photos-8956379.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956379",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956379.pdf",
-      "https://fccid.io/2BTR9-XTEINKX4",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/External-Photos/External-Photos-8956379.pdf"
-     ],
-     "sha256": "7bae5132f43bab0d4c2cc55e876b0974f4445b7d73ba7677219abca52d55e9bd",
-     "bytes": 381099,
-     "destination": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-01-05",
-     "fcc_id": "2BTR9-XTEINKX4",
-     "fcc_document_id": "8956379",
-     "exhibit_type": "External Photos",
-     "exhibit_title_as_filed": "External Photos",
-     "grant_date": "2026-01-05",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf",
-     "placeholder": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x4",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX4-8956382",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX4/Label/ID-Label-Location-Info-8956382.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956382",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956382.pdf",
-      "https://fccid.io/2BTR9-XTEINKX4",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/Label/ID-Label-Location-Info-8956382.pdf"
-     ],
-     "sha256": "c56a7f80a9c4c99e1762c9b0fa6dc8334a892ae982451b634f98a1f3c00702ca",
-     "bytes": 253042,
-     "destination": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-id-label-location-info.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-01-05",
-     "fcc_id": "2BTR9-XTEINKX4",
-     "fcc_document_id": "8956382",
-     "exhibit_type": "ID Label/Location Info",
-     "exhibit_title_as_filed": "ID Label/Location Info",
-     "grant_date": "2026-01-05",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/xteink/x4",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX4-8956380",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX4/Internal-Photos/Internal-Photos-8956380.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956380",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956380.pdf",
-      "https://fccid.io/2BTR9-XTEINKX4",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/Internal-Photos/Internal-Photos-8956380.pdf"
-     ],
-     "sha256": "fd1623a7c9df42ba8140cea6d2618722726c1f442209c02f8229c1b50658f370",
-     "bytes": 770254,
-     "destination": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-07-04",
-     "fcc_id": "2BTR9-XTEINKX4",
-     "fcc_document_id": "8956380",
-     "exhibit_type": "Internal Photos",
-     "exhibit_title_as_filed": "Internal Photos",
-     "grant_date": "2026-01-05",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "repository",
-     "repo_state": "untracked",
-     "archived_to": null,
-     "placeholder": null,
-     "extraction": null,
-     "target_hardware": "devices/xteink/x4",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX4-8956378",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX4/RF-Exposure-Info/RF-Exposure-Info-8956378.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956378",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956378.pdf",
-      "https://fccid.io/2BTR9-XTEINKX4",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/RF-Exposure-Info/RF-Exposure-Info-8956378.pdf"
-     ],
-     "sha256": "4e1ee8ae5227ec5513c219335e061e6d26a80b8697da5eea780796dea1a2c5d2",
-     "bytes": 76885,
-     "destination": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-01-05",
-     "fcc_id": "2BTR9-XTEINKX4",
-     "fcc_document_id": "8956378",
-     "exhibit_type": "RF Exposure Info",
-     "exhibit_title_as_filed": "RF Exposure Info",
-     "grant_date": "2026-01-05",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf",
-     "placeholder": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x4",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-     "id": "fcc-2BTR9-XTEINKX4-8956383",
-     "kind": "regulatory-exhibit",
-     "canonical_url": "https://fccid.io/2BTR9-XTEINKX4/User-Manual/Users-Manual-8956383.pdf",
-     "fallback_urls": [
-      "https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956383",
-      "https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956383.pdf",
-      "https://fccid.io/2BTR9-XTEINKX4",
-      "https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/User-Manual/Users-Manual-8956383.pdf"
-     ],
-     "sha256": "7329a83131ad1ed913833316b6225415feee97392fabb240913db69e81b0c100",
-     "bytes": 1417715,
-     "destination": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf",
-     "retrieved": "2026-09-11",
-     "upstream_version_or_date": "2026-07-04",
-     "fcc_id": "2BTR9-XTEINKX4",
-     "fcc_document_id": "8956383",
-     "exhibit_type": "Users Manual",
-     "exhibit_title_as_filed": "Users Manual",
-     "grant_date": "2026-01-05",
-     "applicant": "Shenzhen Xiaohu Xingtong Technology Co., Ltd. \ud83c\udde8\ud83c\uddf3",
-     "test_firm": "Shenzhen CTB Testing Technology Co., Ltd.",
-     "license": "US Government public record (47 CFR 2.1033); no agency copyright claim",
-     "license_evidence": "FCC Equipment Authorization System publication",
-     "redistribution_status": "allowed",
-     "disposition": "archive",
-     "repo_state": "placeholder-only",
-     "archived_to": "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf",
-     "placeholder": "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md",
-     "extraction": null,
-     "target_hardware": "devices/xteink/x4",
-     "reacquisition": "automatic",
-     "reacquisition_note": "fccid.io requires a non-browser User-Agent; a Chrome UA receives a Cloudflare 403. The `.pdf` suffix is mandatory.",
-     "last_verified": "2026-09-11",
-     "notes": "Filed by the round-2 index merge, 2026-09-11."
-    },
-    {
-      "id": "x4-oem-full-flash",
-      "kind": "firmware-image",
-      "canonical_url": "https://raw.githubusercontent.com/abhishek-nerella/XTEINK-OEM-BIN-/main/flash.bin",
-      "fallback_urls": [
-        "https://github.com/abhishek-nerella/XTEINK-OEM-BIN-/raw/main/flash.bin",
-        "https://github.com/abhishek-nerella/XTEINK-OEM-BIN-/blob/main/flash.bin"
-      ],
-      "sha256": "b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245",
-      "bytes": 16777216,
-      "destination": "devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin",
-      "retrieved": "2026-09-04",
-      "upstream_version": null,
-      "upstream_repo": "abhishek-nerella/XTEINK-OEM-BIN-",
-      "path_in_repo": "flash.bin",
-      "license": "none declared (no LICENSE file); proprietary vendor firmware re-uploaded by a third party",
-      "license_evidence": "absence of LICENSE in the upstream repository tree, checked 2026-09-04",
-      "license_scope": "whole file",
-      "obligations": null,
-      "redistribution_status": "unknown",
-      "disposition": "local-cache",
-      "repo_state": "untracked-symlink-with-placeholder",
-      "archived_to": "archive/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin",
-      "placeholder": "devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md",
-      "reacquisition": "automatic",
-      "target_hardware": "Xteink X4, ESP32-C3, 16 MB flash",
-      "firmware": {
-        "target_mcu": "ESP32-C3 (bootloader chip-id 5)",
-        "image_role": "merged full-flash image (bootloader + partition table + nvs + otadata + app0 + app1 + spiffs + coredump)",
-        "flash_offset": "0x0",
-        "boots": "app0 (otadata seq0=1, seq1=0); app1 erased 0xFF",
-        "app_descriptor": {
-          "project_name": "arduino-lib-builder",
-          "version": "esp-idf: v4.4.7 38eeba213a",
-          "idf_ver": "v4.4.7-dirty",
-          "build_date": "2024-03-05 12:29:20",
-          "elf_sha256": "8b41832ff60a0ffa1cfb9f810a569a3b6237c34bc4ce81e5d280069f8f76d438",
-          "secure_version": 0
-        },
-        "partitions": [
-          [
-            "nvs",
-            "0x009000",
-            "0x005000"
-          ],
-          [
-            "otadata",
-            "0x00E000",
-            "0x002000"
-          ],
-          [
-            "app0",
-            "0x010000",
-            "0x640000"
-          ],
-          [
-            "app1",
-            "0x650000",
-            "0x640000"
-          ],
-          [
-            "spiffs",
-            "0xC90000",
-            "0x360000"
-          ],
-          [
-            "coredump",
-            "0xFF0000",
-            "0x010000"
-          ]
-        ],
-        "flash_instructions": "esptool.py --chip esp32c3 --port <port> --baud 921600 write_flash 0 <file>  [INFERRED, not executed]",
-        "notes": "App descriptor reports the Arduino lib-builder identity, NOT a vendor product version. On-screen versions are V5.1.6 / V5.2.13."
-      },
-      "notes": "Provenance of the dump itself is undocumented upstream (which unit, which stock version). Contains OTA endpoint http://gotaserver.xteink.com/api/check-update and web file manager http://bofi.xteink.cn/index.html ."
-    }
-  ],
-  "wanted": [
-    {
-      "id": "x4-stock-ota-images",
-      "kind": "firmware-image",
-      "canonical_url": "https://github.com/zocs/eink-quick-flasher/tree/main/firmware",
-      "sha256": null,
-      "bytes": null,
-      "destination": "devices/xteink/x4/artifacts/firmware/",
-      "retrieved": null,
-      "upstream_version": "x4_en_v5.1.6 / x4_cn_v5.2.13",
-      "license": "none declared",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "manual",
-      "reason": "Files are Git LFS pointers (~130 bytes each in the tree). Needs git-lfs or the LFS batch API.",
-      "notes": "CN/EN differ only by default UI language per the upstream README; firmware content is stated to be identical."
-    },
-    {
-      "id": "x4-spiffs-extract",
-      "kind": "filesystem-image",
-      "canonical_url": null,
-      "sha256": null,
-      "bytes": 3538944,
-      "destination": "devices/xteink/x4/artifacts/firmware/spiffs.bin",
-      "retrieved": null,
-      "license": "none declared",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "automatic",
-      "reason": "Present inside the held dump at 0xC90000, length 0x360000. Never extracted.",
-      "notes": "Expected to contain the on-device web file-manager UI, explaining the unusually large SPIFFS partition."
-    },
-    {
-      "id": "x4-product-page-archive",
-      "kind": "web-page",
-      "canonical_url": "https://www.xteink.com/products/xteink-x4",
-      "sha256": null,
-      "bytes": null,
-      "destination": "scratch/xteink/web/",
-      "retrieved": null,
-      "license": "unknown",
-      "redistribution_status": "unknown",
-      "disposition": "not-downloaded",
-      "repo_state": "not-downloaded",
-      "reacquisition": "blocked",
-      "reason": "Product delisted before capture. Wayback CDX query for xteink.com* timed out at 60 s with 0 bytes and was not retried.",
-      "notes": "Would recover the vendor's own X4 specification and product imagery, of which this repository holds none."
-    }
-  ]
-}
\ No newline at end of file
diff --git a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md b/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md
deleted file mode 100644
index 6657a8a..0000000
--- a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX4-ant-test-report.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — test report, 2,034,400 B (1.94 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 2,034,400 B (1.94 MiB) |
-| SHA-256 | `b873e75cdbdd8594e6e81328a42fc0f4dd1321c581c46bab9a41f183575dd105` |
-| FCC ID | **`2BTR9-XTEINKX4`** |
-| Exhibit type | **Test Report** |
-| Exhibit title, as filed | ANT Test Report |
-| FCC document id | 8956374 |
-| Upstream publication date | 2026-01-05 |
-| Grant date | 2026-01-05 |
-| Equipment class | XTEINK X4, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX4/Test-Report/ANT-Test-Report-8956374.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956374>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956374.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX4>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/Test-Report/ANT-Test-Report-8956374.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf" \
-   "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX4/Test-Report/ANT-Test-Report-8956374.pdf" -o "2BTR9-XTEINKX4-ant-test-report.pdf"
-echo "b873e75cdbdd8594e6e81328a42fc0f4dd1321c581c46bab9a41f183575dd105  2BTR9-XTEINKX4-ant-test-report.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md b/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md
deleted file mode 100644
index a40930b..0000000
--- a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX4-external-photos.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — external photos, 381,099 B (0.36 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 381,099 B (0.36 MiB) |
-| SHA-256 | `7bae5132f43bab0d4c2cc55e876b0974f4445b7d73ba7677219abca52d55e9bd` |
-| FCC ID | **`2BTR9-XTEINKX4`** |
-| Exhibit type | **External Photos** |
-| Exhibit title, as filed | External Photos |
-| FCC document id | 8956379 |
-| Upstream publication date | 2026-01-05 |
-| Grant date | 2026-01-05 |
-| Equipment class | XTEINK X4, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX4/External-Photos/External-Photos-8956379.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956379>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956379.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX4>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/External-Photos/External-Photos-8956379.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf" \
-   "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX4/External-Photos/External-Photos-8956379.pdf" -o "2BTR9-XTEINKX4-external-photos.pdf"
-echo "7bae5132f43bab0d4c2cc55e876b0974f4445b7d73ba7677219abca52d55e9bd  2BTR9-XTEINKX4-external-photos.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-id-label-location-info.pdf b/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-id-label-location-info.pdf
deleted file mode 100644
index 03d07b3..0000000
Binary files a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-id-label-location-info.pdf and /dev/null differ
diff --git a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf b/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf
deleted file mode 100644
index a6a1d0e..0000000
Binary files a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf and /dev/null differ
diff --git a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md b/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md
deleted file mode 100644
index c138099..0000000
--- a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX4-rf-exposure-info.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — rf exposure info, 76,885 B (0.07 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 76,885 B (0.07 MiB) |
-| SHA-256 | `4e1ee8ae5227ec5513c219335e061e6d26a80b8697da5eea780796dea1a2c5d2` |
-| FCC ID | **`2BTR9-XTEINKX4`** |
-| Exhibit type | **RF Exposure Info** |
-| Exhibit title, as filed | RF Exposure Info |
-| FCC document id | 8956378 |
-| Upstream publication date | 2026-01-05 |
-| Grant date | 2026-01-05 |
-| Equipment class | XTEINK X4, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX4/RF-Exposure-Info/RF-Exposure-Info-8956378.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956378>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956378.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX4>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/RF-Exposure-Info/RF-Exposure-Info-8956378.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf" \
-   "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX4/RF-Exposure-Info/RF-Exposure-Info-8956378.pdf" -o "2BTR9-XTEINKX4-rf-exposure-info.pdf"
-echo "4e1ee8ae5227ec5513c219335e061e6d26a80b8697da5eea780796dea1a2c5d2  2BTR9-XTEINKX4-rf-exposure-info.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md b/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md
deleted file mode 100644
index e5ff118..0000000
--- a/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# ARCHIVED: `2BTR9-XTEINKX4-users-manual.pdf`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-11** by the round-2 index merge.
-
-**Reason:** bulk FCC exhibit — users manual, 1,417,715 B (1.35 MiB). The round-2 artifact split keeps internal photographs and ID-label exhibits in the repository (they are the identification and teardown evidence) and archives the full test reports, RF-exposure annexes, users manuals and external-photo sets, which are bulky and repetitive.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf` |
-| Type | file (PDF, magic-byte validated `%PDF`) |
-| Size | 1,417,715 B (1.35 MiB) |
-| SHA-256 | `7329a83131ad1ed913833316b6225415feee97392fabb240913db69e81b0c100` |
-| FCC ID | **`2BTR9-XTEINKX4`** |
-| Exhibit type | **Users Manual** |
-| Exhibit title, as filed | Users Manual |
-| FCC document id | 8956383 |
-| Upstream publication date | 2026-07-04 |
-| Grant date | 2026-01-05 |
-| Equipment class | XTEINK X4, 2402-2480 MHz, 2412-2462 MHz |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Retrieved | 2026-09-11 |
-| Licence | **US Government public record.** FCC equipment-authorisation exhibits are published by a federal agency under 47 CFR §2.1033 and carry no copyright claim by the agency. |
-| Redistribution status | **`allowed`** |
-| Disposition | `archive`, placeholder in repository |
-
-## How to get it back
-
-Independent reacquisition URLs, most reliable first:
-
-- <https://fccid.io/2BTR9-XTEINKX4/User-Manual/Users-Manual-8956383.pdf>  
-  fccid.io mirror — **200**, but only to a non-browser UA (`curl/8.5.0`, `WhatsApp/2.23.20.0`, `ChatGPT-User/1.0`, `ClaudeBot/1.0`). A Chrome UA gets a Cloudflare 403. The `.pdf` suffix is required.
-
-- <https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=8956383>  
-  official FCC Equipment Authorization System attachment — the primary record. **403 to all five UAs tried from this host on 2026-09-11**; try from another network.
-
-- <https://fcc.report/FCC-ID/2BTR9-XTEINKX4/8956383.pdf>  
-  fcc.report mirror. **403 to all five UAs tried on 2026-09-11.**
-
-- <https://fccid.io/2BTR9-XTEINKX4>  
-  the filing's exhibit index — re-read the row to recover a changed document slug.
-
-- <https://web.archive.org/web/2/https://fccid.io/2BTR9-XTEINKX4/User-Manual/Users-Manual-8956383.pdf>  
-  Wayback Machine, if every live route is dead.
-
-Restore from the local archive, if you have one:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf" \
-   "devices/xteink/x4/artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf"
-```
-
-Or re-download and verify — note the User-Agent, which is not optional:
-
-```bash
-curl -fsSL -A "curl/8.5.0" "https://fccid.io/2BTR9-XTEINKX4/User-Manual/Users-Manual-8956383.pdf" -o "2BTR9-XTEINKX4-users-manual.pdf"
-echo "7329a83131ad1ed913833316b6225415feee97392fabb240913db69e81b0c100  2BTR9-XTEINKX4-users-manual.pdf" | sha256sum -c -
-```
-
-The archive path above is a **convenience**. Everything needed to recover this file without the archive — hash, byte size, FCC ID, exhibit type, document id, publication date and 5 URLs — is in this file.
diff --git a/devices/xteink/x4/artifacts/certification/README.md b/devices/xteink/x4/artifacts/certification/README.md
deleted file mode 100644
index 0ada618..0000000
--- a/devices/xteink/x4/artifacts/certification/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# FCC equipment-authorization exhibits — `2BTR9-XTEINKX4`
-
-Retrieved **2026-09-11** from `fccid.io` with a non-browser User-Agent (`curl/8.5.0`); every file magic-byte validated (`%PDF`). Filed here by the round-2 index merge on 2026-09-11.
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-XTEINKX4`** |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Granted | **2026-01-05** |
-| Equipment class | XTEINK X4, 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Source page | <https://fccid.io/2BTR9-XTEINKX4> |
-
-## Retained in the repository
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| `2BTR9-XTEINKX4-id-label-location-info.pdf` | 253,042 | `c56a7f80a9c4c99e1762c9b0fa6dc8334a892ae982451b634f98a1f3c00702ca` | ID Label/Location Info |
-| `2BTR9-XTEINKX4-internal-photos.pdf` | 770,254 | `fd1623a7c9df42ba8140cea6d2618722726c1f442209c02f8229c1b50658f370` | Internal Photos |
-
-**Internal Photos** and **ID Label / Location Info** are kept in the repository because they are the identification and teardown evidence: for several of these boards the internal photographs are the only public imagery of the PCB that exists anywhere.
-
-## Archived out of the repository
-
-Each has a self-sufficient placeholder beside it carrying its hash, byte size, FCC document id, publication date and five reacquisition URLs. A reader without the archive can recover any of them from the placeholder alone.
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md`](2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md) | 2,034,400 | Test Report |
-| [`2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md`](2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md) | 381,099 | External Photos |
-| [`2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md`](2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md) | 76,885 | RF Exposure Info |
-| [`2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md`](2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md) | 1,417,715 | Users Manual |
-
-Archived total: **4 files, 3.73 MiB**.
-
-## Licensing and disposition
-
-| Field | Value |
-|---|---|
-| Redistribution status | **`allowed`** — FCC equipment-authorisation exhibits are **US Government public records**, published by a federal agency under 47 CFR §2.1033. Redistribution **`allowed`**. |
-| Disposition | `repository` (retained files, **unstaged**) / `archive` (placeholders) |
-| Retained in repo | **2 files, 0.98 MiB** |
-| Archived | **4 files, 3.73 MiB** |
-
-Method, URL templates and the measured user-agent matrix: [`guides/research/finding-certification-records.md`](../../../../../guides/research/finding-certification-records.md).
diff --git a/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin b/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin
deleted file mode 120000
index 3ab87d1..0000000
--- a/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../archive/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin
\ No newline at end of file
diff --git a/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md b/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md
deleted file mode 100644
index c8cda76..0000000
--- a/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# ARCHIVED: `xteink-x4-oem-full-flash-16mb.bin`
-
-> This file was **moved out of the repository**, not deleted.
-> Archived **2026-09-04**.
-
-**Reason:** 16 MiB opaque factory flash image — large, binary, licence unknown, and re-fetchable from a public repository.
-
-An identical copy was already present in the archive (content fingerprint `b9cf27cc254c737c…`, 1 file(s)), so this pass did not create a second copy.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Original repo path | `devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin` |
-| Archived to | `/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin` |
-| Type | file |
-| Size | 16,777,216 B (16.00 MiB) |
-| SHA-256 | `b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245` |
-| Last modified (mtime) | 2026-09-04 07:38:49Z |
-| Upstream repository | abhishek-nerella/XTEINK-OEM-BIN- |
-| Author / committer | abhishek-nerella (GitHub user; the origin of the dump itself — which unit, which stock version — is NOT documented upstream) |
-| Retrieved | 2026-09-04 |
-| License | None declared (no LICENSE file). Vendor firmware; treat as all-rights-reserved. |
-| Path within upstream repo | `flash.bin` |
-| Difficulty to re-obtain | Easy today — a single unauthenticated raw fetch. But it is a one-person re-upload of proprietary firmware with no provenance and no mirror, so it is exactly the kind of artifact that vanishes. |
-| Access notes | No authentication needed. A GitHub token was used only to avoid API rate limits; raw.githubusercontent.com needs none. |
-
-## How to get it back
-
-Independent recovery URLs, most reliable first:
-
-- current default branch (may have changed):  
-  <https://github.com/abhishek-nerella/XTEINK-OEM-BIN-/raw/HEAD/flash.bin>
-- original download URL:  
-  <https://raw.githubusercontent.com/abhishek-nerella/XTEINK-OEM-BIN-/main/flash.bin>
-- same blob via the github.com raw redirect (different host path):  
-  <https://github.com/abhishek-nerella/XTEINK-OEM-BIN-/raw/main/flash.bin>
-- repository web view — use to confirm the blob still exists and read its size:  
-  <https://github.com/abhishek-nerella/XTEINK-OEM-BIN-/blob/main/flash.bin>
-- NOT byte-identical — an independent stock-firmware set (Git LFS) carrying x4_en_v5.1.6_ota.bin and x4_cn_v5.2.13_ota.bin, which are ~6 MB OTA app-only images rather than a full flash. Use if this dump is lost and an app image will do.:  
-  <https://github.com/zocs/eink-quick-flasher/tree/main/firmware>
-
-Restore from the local archive:
-
-```bash
-mv "/home/user/repo-archive/hardware-doc/devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin" \
-   "devices/xteink/x4/artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin"
-```
-
-Or re-download and verify:
-
-```bash
-curl -fsSL "https://github.com/abhishek-nerella/XTEINK-OEM-BIN-/raw/HEAD/flash.bin" -o "xteink-x4-oem-full-flash-16mb.bin"
-echo "b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245  xteink-x4-oem-full-flash-16mb.bin" | sha256sum -c -
-```
-
-If every URL above is dead, try the Wayback Machine:
-
-    https://web.archive.org/web/2/https://github.com/abhishek-nerella/XTEINK-OEM-BIN-/raw/HEAD/flash.bin
-
diff --git a/devices/xteink/x4/certification-and-compliance.md b/devices/xteink/x4/certification-and-compliance.md
deleted file mode 100644
index 0082eb9..0000000
--- a/devices/xteink/x4/certification-and-compliance.md
+++ /dev/null
@@ -1,254 +0,0 @@
-# Certification and compliance — x4
-
-Compiled **2026-09-11** by the round-2 index merge, from the certification pass's findings in [`scratch/market-and-certification/xteink-certification-and-pricing.md`](../../../scratch/market-and-certification/xteink-certification-and-pricing.md). Method and URL templates: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-> **Evidence status.** Everything here is `executed-success` **retrieval** of public regulatory records. **Nothing was verified against a physical device**, no board was inspected, and no label was read off real hardware.
-
-> **Why this arrived late.** These findings were produced on 2026-09-11 but written into `scratch/` because a sibling agent held `devices/xteink/` at the time. That conflict is over; this file is the properly-filed result.
-
----
-
-## 1. Summary
-
-**FCC: granted.** `2BTR9-XTEINKX4`, 2026-01-05.
-
-| Regime | Status |
-|---|---|
-| **FCC (US)** | ✅ `2BTR9-XTEINKX4` — granted **2026-01-05** |
-| **CE / RED (EU)** | ⚠ no published DoC located; no database exists to search (§4) |
-| **UKCA** | ⚠ not determined (§4) |
-| **SRRC / CCC (CN)** | ⚠ **not searched** — database unreachable (§4) |
-| **MIC 技適 (JP)** | ⚠ **not searched** — reachable, not queried (§4) |
-| **ISED (CA)** | ⚠ **not searched** — 503 (§4) |
-
-⚠ **This reverses the 2026-09-04 finding of *no FCC/CE filings*.** See §5.
-
----
-
-## 2. Controls — why the results below mean anything
-
-An absence is only evidence if the method demonstrably finds things that are present. Every
-probe below ran on **2026-09-11**, in one session, against one host, with one tool.
-
-| ID probed | HTTP | Verdict | Role |
-|---|---|---|---|
-| `2BTR9-XTEINKX4` | **200** | granted | **positive** — a real Xteink grant |
-| `2AC7Z-ESPS3WROOM1` | **200** | granted | **positive** — ESP32-S3-WROOM-1 (Espressif), a module known to be certified |
-| `2AN3WM5CARDPUTER` | **200** | granted | **positive** — M5Stack Cardputer |
-| `2AN3WM5CARDPUTERZERO` | **404** | absent | **negative** — invented, plausible form |
-| `2ASYE-T-DISPLAY-K230` | **404** | absent | **negative** — invented, exact LilyGO house style |
-| `2ZZZZNOSUCHGRANTEE` | **404** | absent | **negative** — invented grantee |
-
-**Positives → 200. Negatives → 404.** Raw run:
-`scratch/market-and-certification/logs/fcc-controls.txt`.
-
-These controls are the whole basis on which the absence findings below may be read as evidence.
-They are reproduced in each of the five Xteink records rather than referenced once, because a
-reader arriving at one device record must be able to judge that record's evidence without
-chasing a link.
-
-Beyond the ID probes, **the grantee was enumerated in full rather than guessed**: `2BTR9`
-yields **five** FCC IDs and no more. A product absent from a complete grantee listing is
-*absent*, not merely *un-found* — which is exactly the distinction the 2026-09-04 sweep could
-not make, because it had no grantee code to enumerate.
-
-⚠ **A counter-trap worth recording.** `https://fccid.io/2BTR9` prints **"6 FCC IDs"** in its
-page header, but the applications table lists **five**, and exactly five `href="/2BTR9…"` links
-exist in the HTML. The headline counter and the table disagree. **Trust the table.**
-
----
-
-## 3. The whole grantee — `2BTR9`
-
-| Field | Value |
-|---|---|
-| Applicant | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** |
-| Grantee code | **`2BTR9`** |
-| Registered | **2025-12-21** |
-| Contact | Chen Chu |
-| Address | Room 1209, Yichuang International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community, Guanlan Street, Longhua District, Shenzhen, China |
-| FCC IDs | **5** |
-
-| FCC ID | Granted | Device | Purpose | Record |
-|---|---|---|---|---|
-| `2BTR9-X4L` | **2026-08-13** | XTEINK X4 Light | Original Equipment | [`x4-light`](../x4-light/README.md) |
-| `2BTR9-X4C` | **2026-07-20** | XTEINK X4 Classic | Original Equipment | [`x4-classic`](../x4-classic/README.md) |
-| `2BTR9-X4PRO` | **2026-06-16** | XTEINK X4 Pro | Original Equipment | [`x4-pro`](../x4-pro/README.md) |
-| `2BTR9-XTEINKX4` | **2026-01-05** | XTEINK X4 | Original Equipment | [`x4`](../x4/README.md) |
-| `2BTR9-XTEINKX3` | **2025-12-26** | XTEINK X3 | Original Equipment | [`x3`](../x3/README.md) |
-
-All five: 2402–2480 MHz (BLE) and 2412–2462 MHz (Wi-Fi, US channels 1–11). Long-term
-confidentiality granted on all five for Schematics, Block Diagram and Operational Description.
-
-**Not granted:** no FCC ID under `2BTR9` corresponds to the [**Xteink S4**](../s4/README.md) or
-the [**Xteink Nano**](../nano/README.md). Against a complete enumeration with passing controls,
-those two devices are **not FCC-authorised as of 2026-09-11**.
-
-Xteink filed **Original Equipment** authorisations, not module-based ones. The internal
-photographs show why: the X4 main PCB carries a **bare QFN SoC with a PCB meander antenna etched
-into the board**, not a drop-in pre-certified Espressif module. A design like that cannot
-inherit a module grant, so the vendor had to certify the whole device. That is consistent with,
-and corroborates, the grant record.
-
-
-### The `2BTR9-XTEINKX4` filing
-
-| Field | Value |
-|---|---|
-| FCC ID | **`2BTR9-XTEINKX4`** |
-| Device description | XTEINK X4 |
-| Applicant | Shenzhen Xiaohu Xingtong Technology Co., Ltd. 🇨🇳 |
-| Granted | **2026-01-05** |
-| Frequency ranges | 2402-2480 MHz, 2412-2462 MHz |
-| Test firm | Shenzhen CTB Testing Technology Co., Ltd. |
-| Long-term confidentiality | Yes |
-| Short-term confidentiality | Yes |
-| Exhibit rows | 13 |
-| Filing page | <https://fccid.io/2BTR9-XTEINKX4> — HTTP 200, retrieved 2026-09-11 |
-
-**Withheld:**
-
-- Block Diagram [Block Diagram]
-- Schematics [Schematics]
-- Operational Description [Operational Description]
-
-Internal photographs are **public** and held in this record. They are the **first public teardown of the Xteink X4** — no community teardown of this device exists.
-
-**Exhibits obtained** — US Government public records, redistribution **`allowed`**. Downloaded 2026-09-11, magic bytes validated (`%PDF`).
-
-Retained in this record, at [`artifacts/certification/`](artifacts/certification/README.md):
-
-| File | Bytes | SHA-256 | Exhibit type |
-|---|---:|---|---|
-| [`2BTR9-XTEINKX4-id-label-location-info.pdf`](artifacts/certification/2BTR9-XTEINKX4-id-label-location-info.pdf) | 253,042 | `c56a7f80a9c4c99e1762c9b0fa6dc833…` | ID Label/Location Info |
-| [`2BTR9-XTEINKX4-internal-photos.pdf`](artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf) | 770,254 | `fd1623a7c9df42ba8140cea6d2618722…` | Internal Photos |
-
-Archived out of the repository, each with a self-sufficient placeholder beside it carrying hash, size, FCC document id and five reacquisition URLs:
-
-| Placeholder | Bytes | Exhibit type |
-|---|---:|---|
-| [`2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX4-ant-test-report.pdf.ARCHIVED.md) | 2,034,400 | Test Report |
-| [`2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX4-external-photos.pdf.ARCHIVED.md) | 381,099 | External Photos |
-| [`2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX4-rf-exposure-info.pdf.ARCHIVED.md) | 76,885 | RF Exposure Info |
-| [`2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md`](artifacts/certification/2BTR9-XTEINKX4-users-manual.pdf.ARCHIVED.md) | 1,417,715 | Users Manual |
-
----
-
-## 4. Other jurisdictions
-
-| Regime | Result |
-|---|---|
-| **FCC (US)** | ✅ **granted** — see §1 |
-| **CE / RED (EU)** | ⚠ No published DoC located; no `xteink.com` certification page exists. CE is self-declared; **there is no database to search** |
-| **CE mark on product** | ⚠ **Not determined** — the `ID Label` exhibits were downloaded but not visually inspected for secondary marks. **Open work** |
-| **UKCA** | ⚠ Not determined; no database exists |
-| **SRRC / CCC (CN)** | ❌ **Not searched** — `wireless.miit.gov.cn` and `srrccn.org` both failed to connect. **Not an absence finding** |
-| **MIC 技適 (JP)** | ⚠ **Not searched** — endpoint reachable, not queried |
-| **ISED (CA)** | ⚠ **Not searched** — `sms-sgs.ic.gc.ca` returned 503 |
-
----
-
-## 5. ⚠ Correction — this supersedes the 2026-09-04 finding
-
-[`VERIFICATION-sweep-2026-09-04.md`](../../../VERIFICATION-sweep-2026-09-04.md) §6 recorded:
-
-> **Certification and regulatory records** were checked only for Xteink (where the finding was
-> that no external CE/FCC marking exists on the devices at all). No positive control was run, so
-> the absence is weaker evidence than it looks.
-
-That self-doubt was justified. The original finding confused **"no mark visible in a product
-photograph"** with **"no grant exists"**. They are different claims and only the first was ever
-tested.
-
-- ✅ **Survives:** "no FCC ID is printed on the exterior of the units we photographed." Not
-  re-tested here, and may well still be true.
-- ❌ **Refuted:** any reading that Xteink devices are uncertified or unauthorised for the US.
-  **Xteink holds five granted Original Equipment authorisations.**
-
-47 CFR §2.935 permits an **e-label** displayed in software instead of a printed mark, which is
-the ordinary arrangement for a device with a screen. **That is a likely explanation and it was
-not verified.**
-
-The original sentences in the sweep report and in the Xteink records have **not been edited**.
-Dated corrections sit beneath them, and every one is listed in
-[`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
-
----
-
-## 6. What this does **not** establish
-
-- **No hardware was inspected.** No Xteink unit was obtained, opened or powered.
-- **A grant is not a mark.** A granted FCC ID does not prove the ID is printed on the unit.
-- **CE is not established.** No published Declaration of Conformity was located and **there is
-  no CE database to search** — CE is a self-declaration regime. Absence of a published DoC is
-  not absence of conformity.
-- **The `ID Label` exhibits were downloaded but not visually inspected for secondary marks.**
-  Whether a CE mark appears on Xteink label artwork is **open work**, and cheap to close.
-- **SRRC / CCC (CN) did not run.** `wireless.miit.gov.cn` and `srrccn.org` both failed to
-  connect (`000`) on 2026-09-11. That is a method failure, **not** an absence finding.
-- **MIC 技適 (JP) did not run.** The endpoint is reachable (200) but form-driven; not queried.
-- **ISED (CA) did not run.** `sms-sgs.ic.gc.ca` returned 503.
-- **Schematics are permanently withheld** on all five filings, along with block diagrams and
-  operational descriptions. **The FCC is not a route to an Xteink schematic.**
-
-
-## 7. Sources
-
-| ID | Title | Publisher | Class | Medium | URL | Retrieved | Establishes |
-|---|---|---|---|---|---|---|---|
-| XC-1 | FCC ID `2BTR9-XTEINKX4` record | US FCC via fccid.io | **primary (regulatory)**, via mirror | regulatory record | <https://fccid.io/2BTR9-XTEINKX4> | 2026-09-11 | Grant existence, date, frequencies, exhibit list, embargo dates |
-| XC-2 | FCC grantee index `2BTR9` | US FCC via fccid.io | primary via mirror | regulatory record | <https://fccid.io/2BTR9> | 2026-09-11 | The complete five-device Xteink certification history |
-| XC-3 | Control run | this pass | — | executed probe | `scratch/market-and-certification/logs/fcc-controls.txt` | 2026-09-11 | That the method separates present from absent |
-
-⚠ `fccid.io` is a **mirror**, not the FCC. The official endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to all five user agents tried** on 2026-09-11, so no independent confirmation against the primary host was possible. Exhibit PDFs are served with FCC document IDs and lab letterheads, which is corroborating but not dispositive.
-
-⚠ Deep `fccid.io` paths serve **403 to a Chrome User-Agent** and **200 to `curl/8.5.0`** — an *inverted* block. The honest UA works; the disguised one does not. The **root** `https://fccid.io/` returns 200 to everything, so a reachability probe against the root reports a false success. **Probe a deep path.**
----
-
-## 8. The first public teardown of the Xteink X4
-
-The `2BTR9-XTEINKX4` filing includes **Internal Photos** (4 pages, 15 embedded images, lab
-*Shenzhen CTB Testing Technology Co., Ltd.*), and they were **not** withheld. The 2026-09-04
-sweep recorded that no teardown of any Xteink device existed. One does, it has existed since
-2026-01-05, and it is a US Government public record.
-
-Retrieved 2026-09-11; rendered with `pdfimages -png`; images up to 944×708.
-Held at [`artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf`](artifacts/certification/2BTR9-XTEINKX4-internal-photos.pdf).
-
-| Finding | Confidence |
-|---|---|
-| Battery is **`SZA303759`, 3.7 V, 650 mAh, 2.405 Wh**, cell date-coded **2025/07/07** | ✅ **legible directly**, printed on the cell label, confirmed at two zoom levels |
-| Single main PCB, roughly square, with a large **circular cut-out region** | ✅ clear |
-| **Capacitive touch-wheel electrodes** — a ring of arc-shaped copper segments around that circle | ✅ clear; this is how the X4's rotary control is implemented |
-| **Bare QFN SoC** (~5 × 5 mm, centre dimple) inside a silkscreened keep-out rectangle, beside an **etched meander / inverted-F PCB antenna** | ✅ clear that it is a bare SoC + PCB antenna; ❌ **the part marking is not legible** |
-| **SOIC-8** package adjacent to the SoC, in the position a serial NOR flash normally occupies | ⚠ **inferred from package and placement only.** Marking not legible |
-| **microSD / TF socket** (hinged metal tray) at the board edge | ✅ clear |
-| USB receptacle at the opposite edge | ⚠ shape is **consistent with USB-C**; at this resolution micro-USB cannot be firmly excluded. **Not established** |
-| Two further SOIC-8 parts, plausibly charger and EPD boost | ⚠ **inferred from count and placement.** Markings not legible |
-| E-ink panel with FPC, separate from the main PCB | ✅ clear |
-
-**What the photographs did not resolve: every IC marking.** The images are 944×708 for a
-~70 mm board; a 2 mm package does not carry legible text at that scale. **No part number was
-identified.** Reporting otherwise would be invention.
-
-The bare-QFN-plus-etched-antenna construction is also *why* Xteink had to file Original
-Equipment authorisations rather than inherit a module grant — see §3.
-
-### ⏰ Diary — the X4 Pro teardown becomes public on 2026-12-12
-
-Three Xteink filings withhold photographs under **short-term** confidentiality, which expires:
-
-| Filing | Withheld exhibits | Becomes public |
-|---|---|---|
-| **`2BTR9-X4PRO`** | Internal Photos, Test Setup Photos, Users Manual | **2026-12-12** |
-| `2BTR9-X4C` (X4 Classic) | Internal **and External** Photos, Test Setup Photos, Users Manual | **2027-01-16** |
-| `2BTR9-X4L` (X4 Light) | Internal Photos, Test Setup Photos, Users Manual | **2027-02-09** |
-
-On 2026-12-12, fetch — with a `curl` UA, **not** a browser UA:
-
-```
-https://fccid.io/2BTR9-X4PRO/Internal-Photos/<slug>.pdf
-```
-
-That is the cheapest available route to closing the X4 Pro's single-source panel pinout gap
-(`R2-P2`), and the earliest of the three to unlock.
diff --git a/devices/xteink/x4/commands.md b/devices/xteink/x4/commands.md
deleted file mode 100644
index 6805024..0000000
--- a/devices/xteink/x4/commands.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Xteink X4 — command ledger
-
-Family-wide research commands are in [`../x4-pro/commands.md`](../x4-pro/commands.md).
-This page holds X4-specific commands. Retrieved **2026-09-04**.
-
-## Executed successfully by this session
-
-| # | Command | Purpose | Status |
-|---|---|---|---|
-| 1 | `curl -sSL -H "Authorization: Bearer $(gh auth token)" "https://raw.githubusercontent.com/abhishek-nerella/XTEINK-OEM-BIN-/main/flash.bin" -o x4-oem-flash.bin` | Fetch the **16 MB factory dump**. HTTP 200, 16,777,216 B | `executed-success` |
-| 2 | `sha256sum x4-oem-flash.bin` → `b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245` | Hash before doing anything else | `executed-success` |
-| 3 | Partition-table parse at `0x8000` (see below) | Recovered the full 6-partition layout | `executed-success` |
-| 4 | `esp_app_desc_t` parse at `app0 + 0x20` | Recovered `arduino-lib-builder` / IDF v4.4.7 / 2024-03-05 / `elf_sha256` | `executed-success` |
-| 5 | Printable-string extraction over `app0` | Recovered the OTA endpoint, the web file-manager URL and `XT-EPD` | `executed-success` |
-| 6 | `python3 tools/archive_artifact.py --repo-root . --manifest …` | Archived the dump with a placeholder | `executed-success` |
-
-### The parsing recipe, verbatim
-
-```python
-# executed-success 2026-09-04
-import struct, re
-d = open('x4-oem-flash.bin','rb').read()
-assert len(d) == 16777216 and d[0] == 0xE9              # image magic
-print("chip id", struct.unpack('<H', d[0x0c:0x0e])[0])  # 5 = ESP32-C3
-
-pt = d[0x8000:0x9000]                                   # partition table
-for i in range(0, 0x1000, 32):
-    e = pt[i:i+32]
-    if e[:2] != b'\xAA\x50': break
-    off, size = struct.unpack('<II', e[4:12])
-    print(e[12:28].rstrip(b'\0').decode(), hex(off), hex(size))
-
-p = 0x10000 + 0x20                                      # esp_app_desc_t
-assert struct.unpack('<I', d[p:p+4])[0] == 0xABCD5432
-print(d[p+48:p+80].rstrip(b'\0'))    # project_name
-print(d[p+96:p+112].rstrip(b'\0'))   # build date
-print(d[p+112:p+144].rstrip(b'\0'))  # idf_ver
-print(d[p+144:p+176].hex())          # elf_sha256
-
-# otadata: which slot boots
-print(struct.unpack('<I', d[0xE000:0xE004])[0],
-      struct.unpack('<I', d[0xF000:0xF004])[0])
-```
-
-**Reusable on any Xteink image** — it is how the X4 Pro and X4 Classic layouts in
-this tree could be verified if their dumps were ever obtained.
-
-## Reported working (community, not executed here)
-
-| # | Command / procedure | Source | Status |
-|---|---|---|---|
-| 7 | `esptool.py --chip esp32c3 --port /dev/ttyUSB0 --baud 921600 read_flash 0 0x1000000 x4-stock-full.bin` | What `eink-quick-flasher` automates (~2 min for 16 MB) | `reported-working` |
-| 8 | `esptool.py --chip esp32c3 … write_flash 0 x4-stock-full.bin` | Full restore | `reported-working` |
-| 9 | SD-card install on a **locked** unit: drop `update.bin` on the card root, **hold Power + Up at boot** | [r/XTEINK `1ult9dy`](https://old.reddit.com/r/XTEINK/comments/1ult9dy/) | `reported-working` — **author warns the combo is unverified per unit** |
-| 10 | OTA-unlock a USB-locked stock device via `crosspointreader.com` | [r/xteinkereader `1tl3gnn`](https://old.reddit.com/r/xteinkereader/comments/1tl3gnn/) | `reported-working` |
-| 11 | Recover from a 1.2.0 OTA brick (`esp_ota_end()` failure) | [`togotago/xteink-x4-escape`](https://github.com/togotago/xteink-x4-escape) | `reported-working` |
-
-## Inferred — never executed, never reported
-
-| # | Command | Note |
-|---|---|---|
-| 12 | `esptool.py --chip esp32c3 --port /dev/ttyUSB0 flash_id` | **Would identify the Puya flash part number** from its JEDEC ID — the cheapest open identification in the subject |
-| 13 | `pio run -e x4 [-t upload]` | Standard PlatformIO |
-| 14 | `python3 tools/esp_image_info.py x4-stock-full.bin` | Helper already in this repo |
-| 15 | `esptool.py --chip esp32c3 … read_flash 0xC90000 0x360000 spiffs.bin` then a SPIFFS extractor | **Would recover the on-device web UI.** Not attempted |
-
-## Build configuration
-
-```ini
-board_build.mcu = esp32c3
-build_flags = -DFREEINK_DEVICE_X4=1
-              ; optional, OUT OF SPEC (2x datasheet):
-              ; -DFREEINK_X4_OVERCLOCK_SPI
-```
-
-## Commands deliberately not run
-
-| Command | Why not |
-|---|---|
-| Any `write_flash` | No hardware |
-| `curl http://gotaserver.xteink.com/api/check-update` | Recovered from the dump but **not queried** — request format unknown and it would contact a vendor server. Recorded as an open action |
diff --git a/devices/xteink/x4/community.md b/devices/xteink/x4/community.md
deleted file mode 100644
index 79ee072..0000000
--- a/devices/xteink/x4/community.md
+++ /dev/null
@@ -1,207 +0,0 @@
-# Xteink X4 — community reception
-
-From **2,136** deduplicated Reddit posts retrieved **2026-09-04**. Evidence types:
-**O** firsthand ownership · **M** firsthand measurement · **P** demonstrable
-project · **I** informed interpretation · **Op** opinion · **H** hearsay.
-
-**The X4 is the device that built this community.** It has more owner reports,
-more projects and more cross-subreddit spillover than the rest of the family
-combined.
-
-## Where it began — a Chinese group buy, not a product launch
-
-The earliest English-language sighting predates the vendor's international store
-by **four months**:
-
-> "**Xteink Star Pupil X4 (星瞳X4), 4.3" display, 74g, 5.9mm thin, strong magnetic
-> back, it was €30 on a group-buy** … It's from group-buy. Search 星瞳X4"
-> — [r/ereader `1leohjp`](https://old.reddit.com/r/ereader/comments/1leohjp/), **2025-06-18, 295 pts, 62 c** · **O**
-
-Two things in that title are **not** what later sources say. It gives **74 g and
-5.9 mm**; a February 2026 owner measured **80 g and ~7 mm**
-([r/Ultralight `1r1jfny`](https://old.reddit.com/r/Ultralight/comments/1r1jfny/) · **M**).
-Either two different builds exist, or one measurement includes a screen protector
-(the later one says it does) and a case. **Unresolved** — see
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-The same thread explains the distribution model:
-
-> "Group buying is a way that people use to buy small batch produced niche stuff
-> as a group. … There's no link to buy because it's not available for sale to
-> people outside the group yet. **The group is made up of mandarin speaking
-> ereader fans from mainland China and Taiwan mostly.**" · **I**
-
-and contains a claim that is **wrong** and worth flagging:
-
-> "No, it also reads epubs and **it's running Linux**." · **H — incorrect**
-
-It is not. The factory dump is an **Arduino-framework ESP-IDF 4.4.7 build** on an
-ESP32-C3 with no MMU-capable OS. A confident, upvoted, false technical claim in
-the single earliest thread — a good reason this tree treats forum technical
-assertions as hearsay until they meet firmware.
-
-## Reach
-
-The X4 escaped the e-reader subreddits entirely:
-
-| Subreddit | Notable |
-|---|---|
-| r/kindle | *"Eink combo with button. Basic 4th vs Xteink X4. 2011 vs 2025"* (45 pts); *"Funny size comparison picture of my two e-readers"* (**1,156 pts**) |
-| r/EDC | *"EDC as 18M student who hates the way tech has manifested in our lives"* (**287 pts**) |
-| r/writerDeck | Someone built a two-screen writing deck from **two X4s** and a TMKB T63 keyboard (**230 pts**) |
-| r/Ultralight | 80 g mattered enough to review it there |
-| r/PaperRepublic | An X4 magnet-mounted **inside an A6 leather portfolio** (88 pts) |
-| r/PHBookClub, r/deinfluencingPH, r/kindleindia, r/Livros, r/pirataria, r/NepalBookClub | Genuinely global reach for a vendor with no distributor |
-| r/koreader | Multiple KOReader-sync threads |
-
-## What owners actually say
-
-**Positive, and consistently about the same thing — size and focus:**
-
-> "This little guy singlehandedly got me out of my reading slump! … I'd say the X4
-> is the perfect size for my big hands. **My phone screen time has probably
-> dropped by like 40%**"
-> — [r/XTEINK `1tsvz03`](https://old.reddit.com/r/XTEINK/comments/1tsvz03/), 581 pts · **O + Op**
-
-Also: *"Very happy with my Xteink X4"* (181 pts), *"Absolutely loving my Xteink
-X4"* (120 pts), *"After 2 weeks of use, I love it!"* (107 pts), *"My Xteink X4
-finally arrived, and it's fantastic"* (83 pts).
-
-**The USB-C loyalty**, which is the single most consistent X4-specific opinion:
-
-> "Call me stubborn, but I'm **sticking with my X4 just because of the usb c
-> port**. If it dies, I'm looking elsewhere. In the 8/9 months of me owning and
-> using it extensively, I basically already got my money's worth and then some."
-> — [r/XTEINK `1vw6haq`](https://old.reddit.com/r/XTEINK/comments/1vw6haq/), 2026-08-23 · **O + Op**
-
-**And the counterweight**, from an owner of all three:
-
-> "As someone with all 3, **the pro makes the other two feel obsolete.**"
-> — same thread, 15 pts · **O**
->
-> "I also have all 3. **The regular X4 definitely feels obsolete (and also
-> literally discontinued).** The x3 is still a better form factor for carrying on
-> the back of the phone… I do use the X4 Pro almost exclusively now"
-> — same thread, 7 pts · **O**
-
-## Reliability and failure
-
-Three distinct signals, none of which supports a rate:
-
-| Report | Date | Type |
-|---|---|---|
-| *"**Do not step full body weight on your new XTEINK**"* — r/ereader, **144 pts** | 2026-05-02 | **O**, self-explanatory |
-| *"**Received defective Xteink X4**"* — r/ereader, 40 pts, 19 c | 2026-05-15 | **O** |
-| *"**XTEINK 4 died: What's next?**"* — r/ereader | 2026-06-22 | **O** |
-| *"micro SD card stuck in Xteink X4"* — r/eink | 2025-11-19 | **O** |
-| *"After less than 3 months, the device decided to self-destruct"* — r/XTEINK, 81 pts, 50 c | 2026-07-11 | **O** |
-
-**Five failure anecdotes across 2,136 posts establishes that failures occur.** It
-does not establish a failure rate, and this record does not claim one.
-
-## Vendor relations — genuinely mixed
-
-The founder's own introduction is the community's most-upvoted Xteink post:
-
-> "I'm Crusoe, founder of Xteink, **a small team based in Shenzhen**."
-> — [r/ereader `1o2203h`](https://old.reddit.com/r/ereader/comments/1o2203h/), **1,477 pts** · **O**
-
-Xteink also entered a **commercial affiliate relationship with the third-party
-firmware project** that replaces its own software — an unusual posture:
-
-> "xteink has a 20% off sale happening right now and… you can now support
-> CrossPoint by buying the **developer unlocked version** via crosspointreader.com.
-> **We've been working with xteink for the past couple of weeks** to get an
-> official link from our site where every purchase helps us fund development"
-> — [r/xteinkereader `1uan67g`](https://old.reddit.com/r/xteinkereader/comments/1uan67g/), 338 pts · **P**
-
-But not all of it is warm — *"Xteink appears to be all-in on corporate
-self-immolation"* (r/eink, 2026-04-30, 31 pts, 25 c · **Op**),
-*"Xteink rip off?"* (r/ereader, 23 pts, 35 c),
-*"Don't leave them a review for a coupon, it doesn't work."*
-(r/xteinkereader, 2026-08-13, 28 pts, 20 c · **O**).
-
-**Weighting note:** one of the three subreddits is **vendor-operated**.
-*"r/xteinkreader is the main sub and **it's run by the company**; there's another
-one r/XTEINK which is opened by supporters"* — and r/xteinkHax exists partly
-because a post was **removed from the official sub**
-([r/xteinkHax `1sbjsr3`](https://old.reddit.com/r/xteinkHax/comments/1sbjsr3/) · **I**).
-
-## Third-party sales channels — contradicting "vendor-direct only"
-
-Owners report buying X3/X4 units from **Amazon.ca**, **Amazon**, **AliExpress**
-and **Xianyu** (Chinese eBay), with **different USB-lock states by channel**:
-
-> "X3 from **Amazon**, light grey text, **unlocked** / X3 from their **official
-> website**, light grey text but **locked** for some reason / X4 from
-> **Aliexpress**, dark text, **locked**"
-> — [r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/), 2026-08-10 · **O**
-
-That is a **firsthand, three-unit observation that lock state does not correlate
-with channel in the obvious way**, and it directly contradicts any assumption that
-"official = locked, marketplace = unlocked". Recorded because it is actionable:
-**you cannot predict lock state before purchase.**
-
-## An X4 v2 is coming
-
-> "**Xteink told me the new X4 version 2 is coming in September.** I asked their
-> Instagram and they were kind enough to answer me. No exact date though."
-> — [r/xteinkereader `1vxsr0x`](https://old.reddit.com/r/xteinkereader/comments/1vxsr0x/), **2026-08-25**, 52 pts, 42 c · **I** (vendor-relayed)
-
-Wishlist and rumour in that thread, all **H**: *"I think this is the rumored pogo,
-no frontlight, larger battery model?"*; *"Leaked versions shows the X4 v2 with
-pogos and another X4 with pogos, backlight and no touch."* The most-upvoted reply
-(32 pts) is a plea for exactly what the X4 already is, plus a light:
-
-> "The only way I'd buy the X4 V2 is if it has: **1. USB-C 2. Front light 3. No
-> touchscreen**. Basically, keep everything I like about the current X4, just add
-> a front light. … I have a feeling they might switch to a pogo charger though,
-> and if they do, **that would be a dealbreaker for me**." · **Op**
-
-**Nothing about the X4 v2 is confirmed** beyond the vendor saying one is coming.
-
-## Regulatory — an explanation for a gap
-
-> "With the XTEink **lacking CE and FCC labels**, can they even legally sell it in
-> the EU and US? Is this the reason we're not seeing any regional resellers?"
-> — [r/xteinkereader `1rcjtb4`](https://old.reddit.com/r/xteinkereader/comments/1rcjtb4/), 2026-02-23 · **O**
-
-and, from an X3 owner:
-
-> "**Regulatory info is in software on mine, back is clean.**"
-> — [r/XTEINK `1vkuhbi`](https://old.reddit.com/r/XTEINK/comments/1vkuhbi/) · **O**
-
-**This explains why no FCC ID could be found for any Xteink device**: there is
-apparently no external marking to read. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 174:* **This explains why no FCC ID could be found for any Xteink device**: there is
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4/comparisons-and-recommendations.md b/devices/xteink/x4/comparisons-and-recommendations.md
deleted file mode 100644
index 0fab269..0000000
--- a/devices/xteink/x4/comparisons-and-recommendations.md
+++ /dev/null
@@ -1,133 +0,0 @@
-# Xteink X4 — comparisons and recommendations
-
-Dated **2026-09-04**. The full cross-model table lives in the
-[family index](../README.md#cross-model-comparison); this page covers the X4's
-own position and the platform comparison.
-
-## The headline: it is discontinued, and that changes every recommendation
-
-The X4 is **delisted**, and every X4-specific accessory is **sold out**. A
-recommendation to buy one is a recommendation to buy **used, without spare cases
-or screen protectors**.
-
-Owners of all three models are blunt about it:
-
-> "As someone with all 3, **the pro makes the other two feel obsolete.**"
-> "The regular X4 definitely feels obsolete (**and also literally discontinued**)."
-> — [r/XTEINK `1vw6haq`](https://old.reddit.com/r/XTEINK/comments/1vw6haq/), 2026-08-23 · firsthand owners
-
-## The one thing that keeps it alive: USB-C
-
-The X4 is **the only Xteink that charges over USB-C**. The X3 and X4 Pro use a
-proprietary magnetic pogo connector with a $4.99 cable and a $5.99 adapter sold
-separately.
-
-> "Call me stubborn, but I'm **sticking with my X4 just because of the usb c
-> port**. If it dies, I'm looking elsewhere."
-> — same thread · firsthand owner
-
-> "It's enough that I'll **happily keep using my original X4 instead of
-> upgrading**."
-> — [r/xteinkereader `1v2txxe`](https://old.reddit.com/r/xteinkereader/comments/1v2txxe/), 2026-07-21 · firsthand owner
-
-And the counter-view, also from owners: *"the pogo charger is really a non-issue"*
-(2 separate commenters). **The community is genuinely split**; this record does not
-adjudicate it.
-
-## Within the family
-
-| | **X4** | [X3](../x3/README.md) | [X4 Pro](../x4-pro/README.md) | [X4 Classic](../x4-classic/README.md) |
-|---|---|---|---|---|
-| Price 2026-09-04 | **delisted** (~$69) | **$69** | **$99** | never priced |
-| SoC / PSRAM | C3 / none | C3 / none | **S3 / 8 MB** | **S3 / 8 MB** |
-| Panel | 4.26″ 800×480, ~219 PPI | 3.7″ 792×528, **~257 PPI** | 4.26″ 800×480 | 4.26″ 800×480 |
-| Charging | **USB-C** | pogo | pogo | unknown |
-| Touch / frontlight | ✗ / ✗ | ✗ / ✗ | **✅ / ✅** | ✗ / ✗ |
-| RTC | **none** | DS-series 0x68 | BM8563 0x51 | BM8563 0x51 |
-| Fuel gauge | **none — bare ADC** | **BQ27220** (best) | CW2017 | CW2017 |
-| IMU / NFC | ✗ / ✗ | **✅ / ✅** | ✗ / ✗ | ✅ / ✗ |
-| SD | SPI, **shared with display, no power enable** | SPI shared, **with** power enable | **native SDMMC** | **native SDMMC** |
-| Buttons | 6 (ADC ladder) + power | 6 (ADC ladder) + power | 2 + power | **6 discrete** + power |
-
-**The X4 is the most stripped-down member.** The cheaper X3 has four things it
-lacks (RTC, real gauge, IMU, NFC) and a sharper screen. What the X4 has is USB-C,
-the largest firmware ecosystem, and — uniquely — **a publicly available factory
-flash dump**.
-
-## Against development platforms in this repository
-
-| Device | Class | Schematic | USB-C | Headers | Unlock needed | Verdict vs X4 |
-|---|---|---|---|---|---|---|
-| **Xteink X4** | sealed reader | ✗ | ✅ | ✗ | often | — |
-| [M5Stack PaperMono](../../m5stack/papermono/README.md) | dev board | **✅ published** | ✅ | ✅ | ✗ | **Better for development**; worse as a pocket reader — no enclosure, no case ecosystem, and *"It's thicccccc tho"* per an r/xteinkereader commenter |
-| [Waveshare ESP32-S3-ePaper-3.97](../../waveshare/esp32-s3-epaper-3.97/README.md) | dev board | partial | ✅ | ✅ | ✗ | ESP32-**S3** with PSRAM and a 3.97″ SSD1677 panel — strictly more capable silicon, no enclosure or battery management |
-| [ZeroWriter](../../zerowriter/) | DIY appliance | ✅ open | ✅ | ✅ | ✗ | **Different purpose** — a keyboard-first writing appliance, not a pocket reader |
-
-**These are partial substitutes, not equivalents.** They share "ESP32 driving
-e-paper" and nothing else: no enclosure, no battery, no case ecosystem, no
-pocketability. A dev board is the right answer if you want to *build* something; a
-sealed X4 is the right answer if you want to *read* on something you can also
-reflash.
-
-The comparison is sharpened by a community datapoint: someone **built their own
-open-source ESP32-S3 e-paper dev kit** with KiCad files, a 650 mAh cell,
-**USB-C with OTG, no pogo pins**, 4-bit SDMMC and hand-solderable parts — at a
-*"full unit BOM around $60 including display and battery"*
-([r/XTEINK `1s3osv3`](https://old.reddit.com/r/XTEINK/comments/1s3osv3/), 2026-03-25,
-104 pts · demonstrable project). **A DIY equivalent costs about what the X4 cost**,
-which tells you the X4's margin was in manufacturing scale, not components.
-
-## Direct competitors named by owners
-
-| Device | Community verdict |
-|---|---|
-| **Murphy M3 / M4 (HamGeek, 墨菲)** 3.7″/4.26″ | *"texts on the X4 is 'sharper' and better software supports"*; the M4 claims a 2500 mAh battery that the reviewer **doubts**; M4 **has** a warm frontlight. [r/ereader `1uh14ww`](https://old.reddit.com/r/ereader/comments/1uh14ww/) · firsthand |
-| **OBOOK5** | 219 PPI, 1200 mAh, ~23 GB usable — *"smaller than the boox palmas, and cheaper too"* |
-| **Boox Palma / Go 7 / Picco** | Repeatedly raised; Android, much more expensive |
-| **Kobo Clara BW / Libra 2** | The "grown-up" comparison; owners keep both |
-| **Kindle Basic (2011!)** | An actual r/kindle thread compares them: *"Basic 4th vs Xteink X4. 2011 vs 2025"* |
-
-## Recommendations
-
-| Scenario | Recommendation | Confidence |
-|---|---|---|
-| **You want USB-C and a pocket e-reader you will reflash** | **X4, used** — and buy any case/protector you want *with* it, because they are gone | high |
-| You want to buy new, today | **X3 ($69)** or **X4 Pro ($99)**. The X4 is not purchasable | high |
-| You want the sharpest screen | **X3** (~257 PPI) | high |
-| You want touch + frontlight | **X4 Pro** | high |
-| **You want to build a product** | **PaperMono** or a **Waveshare** board — published schematic, headers, no unlock dance | high |
-| You want an IMU or NFC | **X3** | high |
-| You are waiting | **X4 v2 was confirmed by the vendor for September 2026** — spec unknown, and comment rumour suggests it may move to pogo charging | **low — hearsay** |
-
-## Honest limits
-
-- **No X4 was measured.** The only figures are two developer-reported plane-write
-  timings and a three-unit ADC sample. See [`performance.md`](performance.md).
-- **Battery capacity is unknown**, so battery life cannot be compared at all.
-- Competitor prices and specs above are **community-reported**, not verified.
-- PaperMono / Waveshare / ZeroWriter figures are dated differently — follow the
-  links.
-
----
-
-## Cross-references added 2026-09-07
-
-Append-only, from a cross-cutting synthesis pass. Nothing above was changed and no
-new evidence was gathered.
-
-- [**Handheld and e-ink device landscape, 2026-09**](../../../guides/markets/handheld-and-eink-device-landscape-2026-09.md)
-  — the X4 placed in the pocket-reader group, including the point that it is the
-  **only member of the family with USB-C charging** and that this is now only
-  available secondhand.
-- [**Xteink firmware ecosystem**](../firmware-ecosystem.md) — why the X4 is *"the
-  device that created the ecosystem"*, and the concrete hazard that follows from
-  "X4" being a C3 while "X4 Pro" is an S3: **CrossPlay had to repoint
-  `OtaUpdater.cpp` because upstream's release URL would flash a C3 image onto an
-  S3.**
-- [**SoC choice for battery e-ink devices**](../../../guides/hardware/soc-choice-for-battery-eink-devices.md)
-  — the C3 memory ceiling, and the observation that an ESP32-S3 **with** 8 MB PSRAM
-  is available on a $9.04 board, so PSRAM is not what makes a device expensive.
-- [**Adding LoRa, NFC and an RGB sidelight to e-ink firmware**](../../../guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-  — why adding a radio to an X4 is a hardware project rather than a firmware one:
-  the panel and the SD card **share one SPI bus**, and there is no free interrupt
-  line, no antenna and no RF path.
diff --git a/devices/xteink/x4/compatibility-and-status.md b/devices/xteink/x4/compatibility-and-status.md
deleted file mode 100644
index 087cb69..0000000
--- a/devices/xteink/x4/compatibility-and-status.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Xteink X4 — compatibility and status
-
-Snapshot **2026-09-04**.
-
-## Working
-
-Display (both clock modes), ADC ladder buttons, power button, microSD over shared
-SPI, battery ADC, USB-C flashing, Wi-Fi, BLE. This is the **most-exercised device
-in the family** — ~200 repositories, most of which target it first.
-
-## Partial / risky
-
-| Item | State |
-|---|---|
-| **40 MHz panel overclock** | Works, is **2× datasheet**, and *"can glitch plane writes on marginal wiring"*. Per-unit validation required |
-| **GPIO13 power latch** | Behaviour depends on an **unmarked board revision**. Firmware that omits the assert works on most units and is unusable on others |
-| **Deep sleep** | The SD card **cannot be powered down** — there is no enable pin |
-| **OTA** | Documented to fail with out-of-memory on this SoC class |
-
-## Known failures with named cures
-
-| Failure | Version | Cure |
-|---|---|---|
-| Stuck after OTA fails at `esp_ota_end()` | CrossPoint **1.2.0** | [`togotago/xteink-x4-escape`](https://github.com/togotago/xteink-x4-escape) |
-| OTA update problems | CrossPoint **1.4.0** | *"reflash from the website if you're unlocked or SD flash if you're locked"* — [r/XTEINK `1uek163`](https://old.reddit.com/r/XTEINK/comments/1uek163/) |
-| Soft-brick on locked units | Forks on a stale SDK | Pull the latest SDK — CrossPoint 1.5 release note |
-| Blank display on a newer unit | Firmware without UC8179/UC8279 drivers | Use a firmware carrying the boot probe |
-
-## Not implemented
-
-USB-MSC (not documented for this device), grayscale (1 bpp only).
-
-## Hardware-revision keyed
-
-Two known axes of variation, **neither externally visible**:
-
-1. **Power latch:** self-latching vs not (at least two revisions).
-2. **Panel controller:** SSD1677 vs UC8179 vs UC8279.
-
-**No revision marking scheme is known for either.** Compatibility statements
-cannot be keyed to a revision, only to firmware behaviour that handles both.
-
-## Lifecycle status
-
-**Discontinued.** Delisted from the vendor store; all accessories sold out as of
-2026-09-04. Firmware support remains **very active** — this is a case where
-community support outlives vendor availability.
diff --git a/devices/xteink/x4/coverage.md b/devices/xteink/x4/coverage.md
deleted file mode 100644
index 355b97d..0000000
--- a/devices/xteink/x4/coverage.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Xteink X4 — feature coverage
-
-| Feature | Hardware | Official docs | Community evidence | Guide | Tested | Gaps |
-|---|---|---|---|---|---|---|
-| Display 800×480 | SSD1677/UC8179/UC8279 | none | SDK + timing measurements | [display](features/display.md) | ✅ | Panel module part |
-| Controller detect | boot VER/FLG probe | none | SDK | [display](features/display.md) | ✅ | — |
-| 40 MHz overclock | — | none | SDK + Witch Reader fork shipped it | [display](features/display.md) | ⚠️ out of spec | Per-unit reliability |
-| Buttons (6, ADC ladder) | GPIO1 + GPIO2 | none | **SDK, 3 physical devices** | [buttons](features/buttons.md) | ✅ | — |
-| Power button | GPIO3 | none | SDK | [buttons](features/buttons.md) | ✅ | — |
-| microSD (SPI, shared) | GPIO 8/10/7/12 | none | SDK | [storage](features/storage.md) | ✅ | Max card size |
-| Battery ADC | GPIO0, ÷2 | none | SDK | [battery](features/battery-and-power.md) | ⚠️ | **Capacity unknown**; accuracy unquantified |
-| Power latch | GPIO13 | none | SDK, two revisions | [battery](features/battery-and-power.md) | ✅ | **No revision marking known** |
-| USB-C / flashing | USB-serial-JTAG | none | Owner reports; flasher tools | [usb](features/usb.md) | ✅ | `usbDetect` pin unverified |
-| Wi-Fi | ESP32-C3 | none | **Firmware strings + many projects** | [wifi/bt](features/wifi-and-bluetooth.md) | ✅ | No throughput data |
-| BLE | ESP32-C3 | none | BLE page-turner ecosystem | [wifi/bt](features/wifi-and-bluetooth.md) | ✅ | Reconnect reportedly fragile |
-| Deep sleep | — | none | SDK | [battery](features/battery-and-power.md) | ❌ | **Card cannot be powered down**; no current figure |
-
-## Not fitted
-
-Touch, frontlight, **RTC**, **fuel gauge**, IMU, NFC, audio, LEDs, SDMMC,
-GPIO expander, PMIC.
-
-## Combination scenarios
-
-| Combination | Status |
-|---|---|
-| Display refresh **+** SD read | **Structurally serialised** — one SPI bus. Not benchmarked |
-| Wi-Fi **+** display refresh | Untested; no PSRAM makes memory pressure likely |
-| OTA **+** low free memory | **Known to fail** — CrossPoint moved off GitHub releases over C3 OOM |
-
-## Score
-
-**9 of 12** capabilities have citable third-party confirmation.
-**0 of 12** were verified by this session.
diff --git a/devices/xteink/x4/development.md b/devices/xteink/x4/development.md
deleted file mode 100644
index e566a89..0000000
--- a/devices/xteink/x4/development.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# Xteink X4 — development
-
-> ESP32-C3. Retrieval **2026-09-04**. **Nothing executed against hardware.**
-
-## Toolchain
-
-| Item | Value | Status |
-|---|---|---|
-| Framework | Arduino-ESP32 under PlatformIO | `reported-working` |
-| Build flag | `-DFREEINK_DEVICE_X4=1` | `reported-working` **[SDK]** |
-| SDK | [FreeInk SDK](https://github.com/Free-Ink/freeink-sdk), git submodule | `reported-working` |
-| Optional | `-DFREEINK_X4_OVERCLOCK_SPI` → 40 MHz panel clock, **out of spec** | `reported-working`, opt-in |
-| esptool chip | `esp32c3` | `inferred` |
-| Stock toolchain | **Arduino core, ESP-IDF 4.4.7** | **[DUMP]** app descriptor |
-
-`-DFREEINK_DEVICE_X4=1` links both the SSD1677 driver and the UltraChip
-siblings, and enables the C3 `XteinkDetect` I²C fingerprint.
-
-**No PSRAM.** Memory pressure is real on this device: CrossPoint moved off GitHub
-releases because OTA caused *"out of memory issues on the x3"*, the same SoC.
-
-## Build / flash / monitor
-
-```bash
-pio run -e x4                # inferred
-pio run -e x4 -t upload      # inferred
-pio device monitor -b 115200 # inferred
-```
-
-## USB lock
-
-Many units **ship with USB flashing disabled**. Identical situation to the
-[X4 Pro](../x4-pro/development.md#usb-lock):
-
-| Path | Status |
-|---|---|
-| `crosspointreader.com` OTA unlock | `reported-working` — [r/xteinkereader `1tl3gnn`](https://old.reddit.com/r/xteinkereader/comments/1tl3gnn/) |
-| SD-card install: `update.bin` on card root, **hold Power + Up at boot** | `reported-working` — [r/XTEINK `1ult9dy`](https://old.reddit.com/r/XTEINK/comments/1ult9dy/). Author warns the combo is unverified per unit |
-| Buy the vendor's **developer-unlocked** variant | `reported-working` — [r/xteinkereader `1uan67g`](https://old.reddit.com/r/xteinkereader/comments/1uan67g/) |
-| [`OvermindDL1/xteink-unlocker`](https://github.com/OvermindDL1/xteink-unlocker) | Tauri/Rust desktop unlocker, not inspected |
-
-Community firmware authors shout about it: *"If you have an unlocked X4
-(!!!UNLOCKED!!!)"* — [r/XTEINK `1tqbcgu`](https://old.reddit.com/r/XTEINK/comments/1tqbcgu/), 514 pts.
-
-There is a documented dual-boot workflow for locked units:
-[`lvturner/x4-dual-boot`](https://github.com/lvturner/x4-dual-boot) —
-*"MicroSlate + CrossInk dual-boot for a USB-locked Xteink X4 (SD-card install)"*.
-
-## Bricking risks
-
-| Risk | Note |
-|---|---|
-| **Not asserting the GPIO13 latch** | On the non-self-latching board revision the device only stays on while the button is held. Always assert it |
-| **Driving GPIO13 LOW unintentionally** | That is the battery power-off |
-| **40 MHz panel overclock** | 2× datasheet. *"can glitch plane writes on marginal wiring"* — validate per unit |
-| **Wrong panel driver on a newer batch** | UC8179/UC8279 units need the boot probe |
-| **Stale fork on a locked unit** | CrossPoint 1.5: *"Other forks will need to pull the latest SDK to avoid soft bricking locked units"* |
-| **OTA failure at `esp_ota_end()`** | A real, named brick on CrossPoint 1.2.0 with a published escape recipe ([`togotago/xteink-x4-escape`](https://github.com/togotago/xteink-x4-escape)) |
-| **Out-of-memory during OTA** | No PSRAM; documented on the sibling C3 |
-
-## Debug access
-
-ESP32-C3 **USB-serial-JTAG** over the USB-C port. No exposed header documented; no
-teardown of this device exists to check for pads. The X3 teardowns show the same
-board family and no obvious debug header was captioned.
-
-## The best starting points
-
-| Project | Why |
-|---|---|
-| [CrossPoint Reader](https://github.com/crosspoint-reader/crosspoint-reader) | Upstream; the X4 is its original target |
-| [`ngxson/pluspoint-reader`](https://github.com/ngxson/pluspoint-reader) | *"Yet another alternative firmware for Xteink X4"* |
-| [`CidVonHighwind/microreader`](https://github.com/CidVonHighwind/microreader) | Independent, GPLv2, actively discussed |
-| [`Jon-Vii/marigold-os`](https://github.com/Jon-Vii/marigold-os) | **Rust** firmware for X4 and X3 |
-| [`HookedBehemoth/TrustyReader`](https://github.com/HookedBehemoth/TrustyReader) | Rust, GPL-2.0 |
-| [`adafruit/Adafruit_CircuitPython_Xteink_X4`](https://github.com/adafruit/Adafruit_CircuitPython_Xteink_X4) | **Adafruit** published a CircuitPython helper — a notable third-party endorsement |
-
-Rust appears at least four times (`marigold-os`, `TrustyReader`,
-`aimindseye/rustmix-x4-firmware`, `h0rv/rust-xteink-x4`, `h0rv/slint-xteink-backend`),
-which is unusual for an ESP32-C3 consumer device and reflects the RISC-V core.
-
-## Related
-
-[`factory-firmware.md`](factory-firmware.md) · [`pinouts-and-buses.md`](pinouts-and-buses.md) ·
-[family command ledger](../x4-pro/commands.md)
diff --git a/devices/xteink/x4/factory-firmware.md b/devices/xteink/x4/factory-firmware.md
deleted file mode 100644
index e25da0b..0000000
--- a/devices/xteink/x4/factory-firmware.md
+++ /dev/null
@@ -1,162 +0,0 @@
-# Xteink X4 — factory firmware
-
-> **A complete 16 MB factory flash dump was obtained and analysed.** It is the
-> only Xteink factory image this session acquired. Retrieved **2026-09-04**.
-
-## The artifact
-
-| Field | Value |
-|---|---|
-| File | `artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin` (archived; symlink + placeholder in place) |
-| Size | **16,777,216 B** exactly |
-| SHA-256 | `b9cf27cc254c737c901f81e7fcf0c48308e29bd979848ab0ac0bf6c6f5e8c245` |
-| Source | [`abhishek-nerella/XTEINK-OEM-BIN-`](https://github.com/abhishek-nerella/XTEINK-OEM-BIN-) `flash.bin`, branch `main` |
-| Retrieved | 2026-09-04 |
-| Licence | **None declared.** Vendor firmware re-uploaded by a third party. Redistribution **unknown, probably prohibited**. Disposition: archived, **unstaged** |
-| Provenance of the dump itself | **Unknown.** The upstream README is 55 bytes and does not say which unit or which stock version |
-
-Recovery instructions and alternate URLs:
-[`artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md`](artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md).
-
-## Partition table — parsed from offset `0x8000`
-
-| Label | Type | Subtype | Offset | Size |
-|---|---|---|---:|---:|
-| `nvs` | data (0x01) | nvs (0x02) | `0x009000` | `0x005000` — 20 KiB |
-| `otadata` | data (0x01) | ota (0x00) | `0x00E000` | `0x002000` — 8 KiB |
-| `app0` | app (0x00) | ota_0 (0x10) | `0x010000` | `0x640000` — **6400 KiB** |
-| `app1` | app (0x00) | ota_1 (0x11) | `0x650000` | `0x640000` — **6400 KiB** |
-| `spiffs` | data (0x01) | spiffs (0x82) | `0xC90000` | `0x360000` — **3456 KiB** |
-| `coredump` | data (0x01) | coredump (0x03) | `0xFF0000` | `0x010000` — 64 KiB |
-
-`executed-success` — parsed by this session directly from the image.
-
-**This differs from the X4 Pro's layout** (`0x7E0000` app slots, `0x14000` spiffs).
-The X4 devotes **3.4 MB to SPIFFS**, ten times the Pro's, which is consistent with
-the stock firmware serving a web file-manager UI from flash.
-
-## Boot state of this particular dump
-
-| Field | Value |
-|---|---|
-| Image magic @ `0x0` | `0xE9` ✓ |
-| Bootloader chip-id | **5 = ESP32-C3** — independent confirmation of the SoC |
-| `otadata` seq | slot 0 = 1, slot 1 = 0 → **boots app0** |
-| `app1` | **erased (all `0xFF`)** — this unit had never taken an OTA |
-
-## The app descriptor — and why it does not give you a version
-
-`esp_app_desc_t` at `app0 + 0x20` (magic `0xABCD5432`):
-
-| Field | Value |
-|---|---|
-| `project_name` | **`arduino-lib-builder`** |
-| `version` | `esp-idf: v4.4.7 38eeba213a` |
-| `idf_ver` | `v4.4.7-dirty` |
-| build date/time | **2024-03-05 12:29:20** |
-| `elf_sha256` | `8b41832ff60a0ffa1cfb9f810a569a3b6237c34bc4ce81e5d280069f8f76d438` |
-| `secure_version` | 0 |
-
-**Finding: the stock X4 firmware is an Arduino-framework build, and its app
-descriptor carries the Arduino `lib-builder` identity rather than a product
-version.** The on-screen version numbers users see (V5.1.6, V5.2.13) are **not
-recoverable from the descriptor**, and the 2024-03-05 date is the Arduino core's
-build date, **not the firmware's**.
-
-This matters for anyone identifying a dump: do not report `arduino-lib-builder /
-2024-03-05` as "the firmware version". It is a toolchain fingerprint.
-
-By contrast the **X4 Pro's** 7.4.4 image is a **native ESP-IDF 6.0.1** build whose
-descriptor *does* self-identify as `xteink_app 7.4.4`. **Xteink changed framework
-between the C3 and S3 generations.**
-
-## Network endpoints recovered by string extraction
-
-| String | Role |
-|---|---|
-| `http://gotaserver.xteink.com/api/check-update` | OTA update check — **plain HTTP** |
-| `http://bofi.xteink.cn/index.html` | On-device web file manager |
-| `http://bofi.xteink.cn/index.html?ip=` | same, with the device IP passed in |
-| `XT-EPD` | Probable AP SSID or BLE name — **not confirmed** |
-| `192.168.3.3` | An address literal, role unestablished |
-
-`bofi.xteink.cn` is the **only evidence that the `.cn` domain is in service** —
-the apex `xteink.cn` does not answer.
-
-**Security observation, stated without alarm:** OTA is checked over **plain HTTP**
-and `secure_version` is 0, so there is no anti-rollback. Whether the payload is
-signed or encrypted was **not determined** — the X4 Pro's OTA container uses a
-`.xota` extension and the SDK refers to *"the decrypted"* app, implying some
-protection exists at the package level.
-
-## Known stock firmware versions
-
-From [`zocs/eink-quick-flasher/firmware/README.md`](https://github.com/zocs/eink-quick-flasher/blob/main/firmware/README.md),
-retrieved 2026-09-04:
-
-| File | Device | Language | Version | Type |
-|---|---|---|---|---|
-| `x4_en_v5.1.6_ota.bin` | X4 | EN | **V5.1.6** | OTA, ~6 MB |
-| `x4_cn_v5.2.13_ota.bin` | X4 | CN | **V5.2.13** | OTA, ~6 MB |
-| `x3_en_v1.0.7_full.bin` | X3 | EN | V1.0.7 | full 16 MB |
-| `x3_en_v5.2.13_full.bin` | X3 | EN | V5.2.13 | full 16 MB |
-| `x3_cn_v5.2.13_full.bin` | X3 | CN | V5.2.13 | full 16 MB |
-| `x3_cn_v5.2.13_ota.bin` | X3 | CN | V5.2.13 | OTA |
-
-**Useful fact from that README:** *"CN/EN designation only indicates the default
-UI language. Firmware content is identical; language can be switched in settings
-after flashing."* So there is **no CN/EN hardware or firmware split** — only a
-default setting.
-
-**Not downloaded.** Those files are **Git LFS pointers** (~130 bytes each in the
-tree); fetching the real blobs requires an LFS-aware client. Recorded as a gap.
-
-## How to dump
-
-```bash
-# reported-working (zocs/eink-quick-flasher does this; ~2 minutes for 16 MB)
-esptool.py --chip esp32c3 --port /dev/ttyUSB0 --baud 921600 \
-           read_flash 0 0x1000000 x4-stock-full.bin
-sha256sum x4-stock-full.bin
-```
-Requires a **USB-unlocked** unit. See [`development.md`](development.md).
-
-## How to restore
-
-```bash
-# reported-working
-esptool.py --chip esp32c3 --port /dev/ttyUSB0 --baud 921600 \
-           write_flash 0 x4-stock-full.bin
-```
-
-Community tooling, in order of usefulness:
-
-| Tool | What |
-|---|---|
-| [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher) | GUI, auto COM detection, **1:1 full-flash backup & restore in ~2 min**, and ships stock images. Includes an `X3-FLASHER-GUIDE` in EN and CN |
-| [`bigbag/papyrix-flasher`](https://github.com/bigbag/papyrix-flasher) | Go CLI, auto-detection, embedded bootloader, MD5 verification |
-| `crosspointreader.com` | Web flasher including "flash back to stock" |
-| [`togotago/xteink-x4-escape`](https://github.com/togotago/xteink-x4-escape) | *"Escape recipe for Xteink X4 e-readers stuck on CrossPoint Reader 1.2.0 with OTA failing at `esp_ota_end()`"* — a named, documented brick and its cure |
-
-## Parsing recipe (reusable)
-
-```python
-# executed-success 2026-09-04
-d = open('flash.bin','rb').read()
-pt = d[0x8000:0x9000]                       # partition table
-for i in range(0, 0x1000, 32):
-    e = pt[i:i+32]
-    if e[:2] != b'\xAA\x50': break
-    off, size = struct.unpack('<II', e[4:12])
-    label = e[12:28].rstrip(b'\x00').decode()
-
-p = APP_OFFSET + 0x20                       # esp_app_desc_t, magic 0xABCD5432
-version = d[p+16 :p+48 ].rstrip(b'\0')
-project = d[p+48 :p+80 ].rstrip(b'\0')
-date    = d[p+96 :p+112].rstrip(b'\0')
-idf     = d[p+112:p+144].rstrip(b'\0')
-```
-
-## Related
-
-[`development.md`](development.md) · [`../x4-pro/factory-firmware.md`](../x4-pro/factory-firmware.md)
diff --git a/devices/xteink/x4/features/README.md b/devices/xteink/x4/features/README.md
deleted file mode 100644
index a254014..0000000
--- a/devices/xteink/x4/features/README.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# Xteink X4 — feature guides
-
-| Guide | Capability | Evidence |
-|---|---|---|
-| [`display.md`](display.md) | 800×480 e-ink, SSD1677/UC8179/UC8279 | SDK + measured refresh timing |
-| [`buttons.md`](buttons.md) | Six buttons on a two-pin ADC ladder | SDK, with raw values from three real units |
-| [`storage.md`](storage.md) | microSD over the **shared** display SPI bus | SDK |
-| [`battery-and-power.md`](battery-and-power.md) | ADC sense, MOSFET latch, two board revisions | SDK |
-| [`usb.md`](usb.md) | USB-C, USB-serial-JTAG | SDK + owner reports |
-| [`wifi-and-bluetooth.md`](wifi-and-bluetooth.md) | ESP32-C3 Wi-Fi + BLE | inferred + firmware strings |
-
-**Not fitted:** touch, frontlight, RTC, fuel gauge, IMU, NFC, audio, LEDs, SDMMC.
diff --git a/devices/xteink/x4/features/battery-and-power.md b/devices/xteink/x4/features/battery-and-power.md
deleted file mode 100644
index 3ad8b4b..0000000
--- a/devices/xteink/x4/features/battery-and-power.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# X4 — battery and power
-
-> ADC voltage sense, a MOSFET power latch, **and two board revisions that behave
-> differently**. 2026-09-04.
-
-| Item | Value |
-|---|---|
-| Battery sense | **ADC on GPIO0**, `batteryDividerMultiplier = 2.0` |
-| Fuel gauge | **NONE** (`NO_GAUGE`) — unlike the X3 (BQ27220) and X4 Pro (CW2017) |
-| Charge status pin | **none** (`batteryChargeStatus = PIN_UNASSIGNED`) |
-| Power latch | **GPIO13** — battery MOSFET gate |
-| Charging | **USB-C** |
-| Capacity | **unknown** — the X3 is 650 mAh by teardown; the X4 is unmeasured |
-| Charger IC | unidentified; the X3 uses a *"TP4056-class"* part per its Chinese teardown |
-
-**Battery percentage on the X4 is a voltage estimate through a divider**, with no
-coulomb counting and no charge-state signal. It will be less accurate than the X3's
-or the Pro's, particularly near the ends of the curve, and it cannot tell you
-whether the device is charging.
-
-## The two board revisions — read this before writing power code
-
-Quoted in full because the consequence is severe:
-
-> "GPIO13 gates the battery MOSFET. **Known units self-latch through a pull once
-> the power button bridges the rail, so firmware never had to assert it — but at
-> least one hardware revision in the field does not self-latch and stays powered
-> only while the button is held.** Asserting the latch is a no-op on self-latching
-> units. Driving it LOW is the battery power-off."
-> — **[SDK]** `BoardConfig.h:868–874`
-
-| | Self-latching revision | Non-self-latching revision |
-|---|---|---|
-| Firmware never asserts GPIO13 | works | **device powers off when you release the button** |
-| Firmware asserts GPIO13 HIGH early | works (no-op) | works |
-
-The revisions are **not externally distinguishable** and no revision marking is
-known. **Always assert GPIO13 HIGH in early boot.** It costs nothing on the
-majority of units and is the difference between working and unusable on the rest.
-
-To power off: drive GPIO13 **LOW**.
-
-## Sleep
-
-Carried as `power.latch0 = {13}`, driven by the consumer's sleep path. Note the
-**same GPIO13 is the SD power enable on the X3** — the X4 explicitly leaves it
-alone in SD code. Do not port sleep logic between the two without checking.
-
-The X4 has no SD power enable, so **the card stays powered through sleep**. No
-sleep-current measurement exists for this device.
-
-## Related
-
-[`storage.md`](storage.md) · [`../pinouts-and-buses.md`](../pinouts-and-buses.md)
diff --git a/devices/xteink/x4/features/buttons.md b/devices/xteink/x4/features/buttons.md
deleted file mode 100644
index 01cc913..0000000
--- a/devices/xteink/x4/features/buttons.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# X4 — buttons (ADC resistor ladder)
-
-> **Six buttons on two ADC pins.** Four on the front face, three on the right
-> edge (one of which is power). 2026-09-04.
-
-| Group | GPIO | Buttons |
-|---|---:|---|
-| 1 | **1** | Back · Confirm · Left · Right |
-| 2 | **2** | Up · Down |
-| power | **3** | digital, active-LOW |
-
-`InputStyle::XteinkAdcLadder`, `analogSetAttenuation(ADC_11db)`.
-
-## Calibration data — from three real devices
-
-The SDK records the raw 12-bit readings it derived the thresholds from
-(**[SDK]** `InputManager.cpp:29–45`). This is **firsthand measurement**, the only
-such data in the family:
-
-| | BACK | CONFIRM | LEFT | RIGHT |
-|---|---:|---:|---:|---:|
-| unit 1 | 3597 | 2760 | 1530 | 6 |
-| unit 2 | 3470 | 2666 | 1480 | 6 |
-| unit 3 | 3470 | 2655 | 1470 | 3 |
-| **avg** | **3512** | **2694** | **1493** | **5** |
-
-Unit-to-unit spread is ~3.6 % at the top of the ladder — small, but the SDK
-deliberately uses **midpoints between adjacent averages** rather than fixed
-thresholds because they are *"much more tolerant of different devices"*:
-
-```c
-const int InputManager::ADC_RANGES_1[] = {ADC_NO_BUTTON, 3100, 2090, 750, INT32_MIN};
-const int InputManager::ADC_RANGES_2[] = {ADC_NO_BUTTON, 1120, INT32_MIN};
-```
-
-Group 2's local index is remapped by `+4` to `BTN_UP`/`BTN_DOWN`.
-
-## Limits
-
-- **One button per group at a time.** A ladder yields one voltage; two buttons in
-  the same group produce a third, wrong reading. Cross-group chords are fine.
-- **No interrupts.** The ladder must be polled, unlike the X4 Classic's discrete
-  interrupt-driven keys.
-- ADC1 also carries the battery sense on GPIO0 — three channels, read sequentially.
-
-## The struct trap
-
-`input = {0, 1, 2, 3, 4, 5, 3, false}` — the first six values are **logical button
-indices, not GPIO numbers**. Only `power` (7th field, GPIO3) is a pin. Reading
-them as pins gives a plausible-looking but entirely wrong map.
-
-## Feel
-
-*"the buttons on the X4 are clickier and louder. The X3's buttons are somewhat
-mushy and quieter."* — [r/xteinkereader `1syav96`](https://old.reddit.com/r/xteinkereader/comments/1syav96/),
-2026-04-28, 412 pts. Firsthand comparative ownership report.
-
-## Status
-
-`hardware-confirmed` — thresholds derived from three physical devices.
diff --git a/devices/xteink/x4/features/display.md b/devices/xteink/x4/features/display.md
deleted file mode 100644
index c6a084e..0000000
--- a/devices/xteink/x4/features/display.md
+++ /dev/null
@@ -1,50 +0,0 @@
-# X4 — display
-
-> 800×480 mono e-ink, ~219 PPI, 4.26″. Same panel family as the X4 Pro and X4C.
-> 2026-09-04.
-
-| Property | Value |
-|---|---|
-| Resolution | 800 × 480, native landscape (`NO_FLIP`) |
-| Depth | 1 bpp |
-| Controller | **SSD1677** default; **UC8179 / UC8279** on newer batches |
-| Bus | SPI **shared with the microSD card** — SCLK 8 / MOSI 10 |
-| CS / DC / RST / BUSY | 21 / 4 / 5 / 6 |
-| Clock | **20 MHz** default; 40 MHz opt-in |
-
-## The clock decision — the clearest trade-off in the family
-
-| Clock | Plane write | Spec status |
-|---|---|---|
-| **20 MHz** (default) | **~38 ms/refresh** | SSD1677 datasheet write maximum |
-| **40 MHz** (`-DFREEINK_X4_OVERCLOCK_SPI`) | **~19 ms** — saves ~17–20 ms | **2× datasheet. Out of spec** |
-
-40 MHz is what the **CrossPoint / Witch Reader** fork shipped. The SDK made it
-opt-in and warns it *"can glitch plane writes on marginal wiring"*. Validate on
-your own unit; a glitched plane write is a visibly corrupt page, not a crash.
-
-**Trap:** `Ssd1677Driver`'s internal default is 40 MHz, so a board profile that
-leaves `displaySpiHz = 0` runs out of spec **silently**. The X4 profile sets it
-explicitly for exactly this reason.
-
-## Controller detection
-
-Identical mechanism to the [X4 Pro](../../x4-pro/features/display.md): a
-bit-banged half-duplex read of `VER (0x70)` and `FLG (0x71)`, which the SSD-family
-does not answer. `LUT_VER` (VER byte 2) then separates UC8279 (`0x02`/`0x68`/`0x69`)
-from UC8179.
-
-Because the X4 shares the bus with the SD card, the probe runs **before**
-`EpdBus::begin()` and must release any retained GPIO hold from the sleep path
-first (`gpio_hold_dis` on RST) — otherwise every `digitalWrite` bounces off the
-latch and the probe selects the wrong driver. **[SDK]** `XteinkDetect.cpp:141–150`.
-
-## Bus contention
-
-There is no arbitration beyond chip select. A large SD read stalls the panel.
-Firmware that streams a book page from the card while refreshing will serialise.
-
-## Status
-
-`reported-working` — the X4 is the ecosystem's most-exercised target. Refresh
-timings are the only quantitative performance figures in this whole device family.
diff --git a/devices/xteink/x4/features/storage.md b/devices/xteink/x4/features/storage.md
deleted file mode 100644
index ef74d27..0000000
--- a/devices/xteink/x4/features/storage.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# X4 — microSD storage
-
-> SPI, **sharing the display bus**. No power enable. 2026-09-04.
-
-| Signal | GPIO | Note |
-|---|---:|---|
-| SCLK | **8** | **shared with the EPD** |
-| MOSI | **10** | **shared with the EPD** |
-| MISO | **7** | SD-only |
-| CS | **12** | |
-| powerEnable | **none** | **The card cannot be powered down** |
-
-`separateSpi = false`; `spiHz = 0` → SD manager default (40 MHz). Driver: SdFat.
-
-## Consequences of sharing the bus
-
-1. **Panel and card contend.** Only chip select separates them; a long card
-   transfer stalls display refresh and vice versa.
-2. **Clock rates differ.** The panel wants ≤20 MHz (or 40 MHz overclocked); the SD
-   manager defaults to 40 MHz. The bus is reconfigured per transaction.
-3. **No sleep power-down.** Unlike the [X3](../../x3/features/storage.md), which
-   gates its card on GPIO13, the X4 has no SD enable. The card stays powered.
-
-That last point is a real battery consideration and the X3's profile calls it out
-explicitly for its own board: *"Without declaring it, `powerDownRailsForSleep()`
-has no X3 SD enable to cut, so the card stays powered through sleep → battery
-drain."* **On the X4 there is nothing to declare** — the drain is structural.
-
-## Contrast with the S3 devices
-
-The [X4 Pro](../../x4-pro/features/storage.md) and X4 Classic use **native SDMMC**
-on dedicated pins with an active-low power enable. That is faster, independent of
-the display, and sleeps properly. It is the single biggest architectural
-improvement between the C3 and S3 generations.
-
-## Status
-
-`reported-working`. Max card capacity and filesystem limits: **not tested, not
-reported anywhere found**.
diff --git a/devices/xteink/x4/features/usb.md b/devices/xteink/x4/features/usb.md
deleted file mode 100644
index 1f87000..0000000
--- a/devices/xteink/x4/features/usb.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# X4 — USB
-
-> **USB-C, and it charges over it.** The only member of the family that does.
-> 2026-09-04.
-
-| Property | Value |
-|---|---|
-| Connector | **USB-C** |
-| Peripheral | ESP32-C3 **USB-serial-JTAG** (no external bridge) |
-| `usbDetect` | **GPIO20** — but see the conflict below |
-| Charging | **over USB-C** |
-| USB-MSC | not documented for this device |
-
-## Why USB-C matters here
-
-The X3 and X4 Pro both charge over a **magnetic pogo connector** requiring a
-proprietary cable. Owners cite USB-C as a reason to keep an X4 rather than
-upgrade:
-
-> "It's enough that I'll happily keep using my original X4 instead of upgrading."
-> — [r/xteinkereader `1v2txxe`](https://old.reddit.com/r/xteinkereader/comments/1v2txxe/), 2026-07-21
-
-## The GPIO20 conflict
-
-`usbDetect = 20` in the X4 profile. On the **X3** — same board family —
-**GPIO20 is the I²C SDA line**. The X4 has no I²C peripherals so the pin is free,
-but neither assignment is marked hardware-confirmed and they cannot both describe
-the same silicon function.
-
-Most likely: the X4 uses GPIO20 for USB presence, and the X3 repurposed it when
-the RTC, gauge and IMU were added. **Unverified.** See
-[`../gaps-and-conflicts.md`](../gaps-and-conflicts.md).
-
-## Flashing over USB
-
-The C3's USB-serial-JTAG is the flash path — **when the unit is not USB-locked**.
-See [`../development.md`](../development.md).
-
-## Status
-
-`reported-working` for charging and flashing. `unverified` for the `usbDetect` pin.
diff --git a/devices/xteink/x4/features/wifi-and-bluetooth.md b/devices/xteink/x4/features/wifi-and-bluetooth.md
deleted file mode 100644
index 16c21dd..0000000
--- a/devices/xteink/x4/features/wifi-and-bluetooth.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# X4 — Wi-Fi and Bluetooth
-
-> ESP32-C3 integrated radios. 2026-09-04.
-
-| Radio | Status |
-|---|---|
-| Wi-Fi 2.4 GHz b/g/n | Present (SoC) |
-| Bluetooth **LE 5** | Present (SoC) |
-| Bluetooth Classic | **Not available** — the ESP32-C3 has no BR/EDR radio |
-| Antenna | **not characterised** — no teardown of this device, no FCC filing |
-
-## Direct evidence the radio is used
-
-Unlike the X4 Pro, the X4's radio use is **demonstrated from its own firmware**.
-Strings extracted from the factory dump
-([`../factory-firmware.md`](../factory-firmware.md)):
-
-| String | Meaning |
-|---|---|
-| `http://gotaserver.xteink.com/api/check-update` | Wi-Fi OTA check — **plain HTTP** |
-| `http://bofi.xteink.cn/index.html` | On-device **web file manager** — the device runs an HTTP server |
-| `http://bofi.xteink.cn/index.html?ip=` | same, with device IP |
-| `XT-EPD` | Probable AP SSID or BLE name — **not confirmed** |
-
-So the stock firmware both **fetches over HTTP** and **serves a web UI** — the
-latter explains the unusually large 3.4 MB SPIFFS partition.
-
-## BLE page turners
-
-The FreeInk SDK ships `libs/network/BleKeyboardHost` (BLE HID host). There is a
-real accessory ecosystem: [`CrazyCoder/free2-updater-patch`](https://github.com/CrazyCoder/free2-updater-patch)
-exists purely to *"bypass broken VID check"* in a JieLi/hanlinyue page-turner's
-updater *"for Free2 Bluetooth page turners (working with Xteink X4 and similar
-devices)"*.
-
-## Community projects using the radio
-
-`maddiedreese/xteink-terminal` (*"tmux bridge for using an XTeInk X4 as a small
-Wi-Fi e-ink terminal display"*), `keithwithAI/xteink-agenda` (Google Calendar via
-FastAPI), `fsocietyipa/WienerLinien-XteinkX4` (departure board),
-`pocmaker42/xteink-todo`, `Wferr/xteink-sync`.
-
-## Not established
-
-Throughput, range, coexistence, power cost, and whether `XT-EPD` is an SSID.
-No measurement exists.
-
-## Status
-
-`reported-working` — demonstrated by firmware strings and many working projects.
-`not-tested` for any quantitative property.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 10:* | Antenna | **not characterised** — no teardown of this device, no FCC filing |
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](../certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4/gaps-and-conflicts.md b/devices/xteink/x4/gaps-and-conflicts.md
deleted file mode 100644
index b6f2061..0000000
--- a/devices/xteink/x4/gaps-and-conflicts.md
+++ /dev/null
@@ -1,110 +0,0 @@
-# Xteink X4 — gaps and conflicts
-
-Snapshot **2026-09-04**.
-
-## Conflicts
-
-### 1. GPIO20 — `usbDetect` or I²C SDA?
-
-| Profile | GPIO20 role |
-|---|---|
-| `XTEINK_X4` | `usbDetect = 20` |
-| `XTEINK_X3` (same board family) | `usbDetect = 20` **and** `X3_I2C_SDA = 20` for the BQ27220/DS3231/QMI8658 bus |
-
-The X3 assigns GPIO20 **twice**, to two different functions, in the same SDK.
-On the X4 there is no I²C bus so the conflict is latent — but it means
-**neither assignment has been verified**, and the X4's `usbDetect` is plausibly
-just copied from a template.
-
-**What would settle it:** an oscilloscope on GPIO20 during USB plug/unplug, or a
-continuity check to the USB-C connector.
-
-### 2. Stock firmware version is not recoverable from the app descriptor
-
-The dump's `esp_app_desc_t` reports `arduino-lib-builder` / ESP-IDF v4.4.7 /
-2024-03-05, which is the **Arduino core's** identity, not the product's. Users see
-V5.1.6 / V5.2.13 on screen. **Recorded so nobody reports "2024-03-05" as the
-firmware date.**
-
-### 3. Community price vs vendor API
-
-A community post lists *"$69 X4, $79 X3, $99 X4 Pro"*
-([r/XTEINK `1v5gh6x`](https://old.reddit.com/r/XTEINK/comments/1v5gh6x/), 2026-07-24)
-while the vendor API shows the **X3 at $69**, not $79. The X4 figure could not be
-checked because the product is delisted. Community figure not corroborated.
-
-## Unresolved identities
-
-| Part | What is known | What is missing |
-|---|---|---|
-| **ESP32-C3 variant** | Family-level: a teardown photo captioned *"ESP32-C3 main CPU"* and an independent Chinese BOM saying `ESP32-C3` | **The exact package/suffix has never been read.** With external flash it is likely a bare `ESP32-C3` QFN32, but that is inference. **No part number is asserted anywhere in this record** |
-| **Puya SPI NOR flash** | *"PUYA 128Mbit Flash"* (CN BOM), *"128MBit (16MB) flash for firmware"* (EN teardown) | **No part number.** Puya's 16 MB parts include `P25Q128H`-series; **not asserted** |
-| **Charger IC** | *"类似TP4056的电池管理芯片"* — TP4056-**class** (X3 board) | Actual part; and whether the X4 uses the same |
-| **Panel module** | Controller only | Glass/module part number, supplier |
-
-Per the skill's rule, none of these has been promoted from candidate to finding.
-A guessed part number would be worse than "unidentified".
-
-## Gaps — physical
-
-**No X4 teardown was located.** The two teardowns that exist are of the **X3**, a
-related but different board. Unknown: PCB layout, revision markings, antenna,
-debug pads, battery capacity, connector types.
-
-**The two board revisions** (self-latching vs not) have **no known distinguishing
-marking**. This is the most operationally important unknown about the device.
-
-## Gaps — regulatory
-
-No FCC ID, CE or SRRC record read. No board photo exists to read one from.
-Not searched.
-
-## Gaps — firmware
-
-| Item | Status |
-|---|---|
-| Stock V5.1.6 / V5.2.13 OTA images | Known to exist as **Git LFS blobs** in `zocs/eink-quick-flasher`; **not fetched** (needs an LFS-aware client). Cheap to close |
-| SPIFFS contents (3.4 MB) | **Not extracted.** Should contain the web file-manager UI |
-| OTA feed | `gotaserver.xteink.com/api/check-update` **not queried** |
-| Payload signing/encryption | Undetermined. `secure_version = 0` means no anti-rollback |
-| The dumped unit's identity | Unknown — which colour, which revision, which stock version |
-
-## Gaps — measurement
-
-The only quantitative figures in this record are the SDK's **~38 ms / ~19 ms**
-plane-write timings and the **three-unit ADC ladder readings**. There is no power
-measurement, no runtime, no sleep current, no Wi-Fi throughput. The one person who
-set out to measure power on this board family
-([X3 teardown](../x3/media.md), Nordic PPK II) never published results.
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 59:* No FCC ID, CE or SRRC record read. No board photo exists to read one from.
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4/market-and-pricing.md b/devices/xteink/x4/market-and-pricing.md
deleted file mode 100644
index d8e6fb2..0000000
--- a/devices/xteink/x4/market-and-pricing.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Xteink X4 — market and pricing
-
-## Status: delisted
-
-Observed **2026-09-04** from `xteink.com` Shopify APIs:
-
-- The **X4 device does not appear** in `/products.json` (23 products) or in the
-  `x4-series` collection.
-- The `x4-series` collection contains **only accessories**.
-- **Every X4-specific accessory is sold out**, across every variant:
-
-| Accessory | Variants | Status |
-|---|---|---|
-| X4 Magnetic Case | 7 colours | **all sold out** |
-| X4 Protective Case | Mist White, Mist Gray | **both sold out** |
-| X4 Tempered Glass Screen Protector | 1/2/3-pack | **all sold out** |
-| X4 Matte Screen Protector | 2/4/6-pack | **all sold out** |
-
-Only cross-model accessories (reading light, metal ring) remain available in the
-X4 collection.
-
-That is a **complete, unambiguous end-of-life signature**: no device, no
-device-specific accessory, no restock.
-
-## Historical pricing
-
-| Date | Price | Source | Confidence |
-|---|---|---|---|
-| 2026-07-24 | **$69** | [r/XTEINK `1v5gh6x`](https://old.reddit.com/r/XTEINK/comments/1v5gh6x/) | Community list; the same list gives the X3 at $79, which the vendor API contradicts. **Treat as approximate** |
-| 2026-06-20 | **20 % off sale** on X3/X4, via the CrossPoint affiliate link | [r/xteinkereader `1uan67g`](https://old.reddit.com/r/xteinkereader/comments/1uan67g/) | Firsthand announcement |
-| 2025-12-26 | *"X4 Restocking"* community digest | [r/xteinkereader `1pw0r4y`](https://old.reddit.com/r/xteinkereader/comments/1pw0r4y/) | Stock was constrained even at peak |
-
-**The delisted product page could not be recovered.** The Wayback CDX query for
-`xteink.com*` timed out at 60 s and was not retried — the single cheapest
-outstanding action for this record. See [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-## Secondhand
-
-The only concrete used-market datapoint is for the **X3**, not the X4: one unit
-acquired for **$16** ([r/XTEINK `1vrnxnq`](https://old.reddit.com/r/XTEINK/comments/1vrnxnq/),
-2026-08-18), channel not stated.
-
-**This is one anecdote about a different model.** It is recorded, not generalised.
-No used X4 price was observed.
-
-## Channel
-
-Vendor-direct only; no distributor, no Amazon storefront located. One community
-claim that the X4 *"Cracked Amazon's e-reader top 10"* is **unverified** — no
-listing was found.
-
-## What this means for a buyer today
-
-You cannot buy a new X4 from the vendor. If you want this specific device — for
-USB-C charging or for the ecosystem's best-supported target — the secondhand market
-is the only channel, and **replacement cases and screen protectors are also gone**.
-Buy the accessories with the device or not at all.
-
-For a new purchase, see
-[`../x4-pro/comparisons-and-recommendations.md`](../x4-pro/comparisons-and-recommendations.md).
-
----
-
-## Dated observation — 2026-09-11: withdrawn, and its successor is named
-
-Source: **`https://xteink.com/products.json?limit=250&page=1`**, retrieved **2026-09-11**. Full
-catalogue enumerated: **25 products**.
-
-**The X4 is still gone, and the picture is now complete rather than merely negative.**
-
-- Of the 25 products, **none is a bare "Xteink X4"** — confirming the 2026-09-04 delisting.
-- **All four X4-specific accessories have also been withdrawn** from the catalogue, not merely
-  sold out as they were on 2026-09-04.
-- A successor appeared on **2026-09-06**: **"XTEINK X4 Classic (X4 V2)"** at **USD 79.00**
-  (USD 95.00 with base). **The vendor's own product title states that the Classic *is* the second
-  version of the X4.**
-
-| Fact | Evidence |
-|---|---|
-| X4 withdrawn | absent from `/products.json`, 25/25 products enumerated, 2026-09-11 |
-| X4 accessories withdrawn | absent from the catalogue on 2026-09-11 (they were present-but-sold-out on 2026-09-04) |
-| Successor is the X4 Classic | vendor store title **"XTEINK X4 Classic (X4 V2)"**, published **2026-09-06**, **USD 79.00** |
-| The FCC record agrees | `2BTR9-XTEINKX4` granted 2026-01-05, then `2BTR9-X4C` granted 2026-07-20 — see [`certification-and-compliance.md`](certification-and-compliance.md) |
-
-**This record therefore documents a withdrawn product**, and
-[`x4-classic`](../x4-classic/README.md) documents its successor. Nothing above this line has been
-edited; the delisting evidence recorded on 2026-09-04 stands and is now corroborated by a second
-independent signal (the FCC succession) and a named replacement.
-
-⚠ The X4's last observed vendor price was **USD 69.00**. The X4 Classic is **USD 79.00** — a
-**USD 10 increase** across the generation. Both figures are vendor-direct item prices, so they
-are comparable.
-
-⚠ **Not obtained:** no marketplace, clone or used-market X4 price. AliExpress, Amazon, eBay,
-Taobao and JD were all bot-walled or JS-shelled on 2026-09-11.
diff --git a/devices/xteink/x4/media.md b/devices/xteink/x4/media.md
deleted file mode 100644
index 5c6d668..0000000
--- a/devices/xteink/x4/media.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Xteink X4 — images and media
-
-**No X4 teardown, PCB photo or board image is held.**
-
-## What was searched
-
-| Target | Where | Result |
-|---|---|---|
-| X4 teardown | Reddit, 1,798 posts, terms `xteink teardown`, `xteink teardown chip` | **None.** The two teardowns found are both **X3** |
-| X4 PCB photos | GitHub repo census (~200 repos) | None |
-| Vendor imagery | Shopify product record | **Product delisted** — the device's own images are gone with it |
-| FCC internal photos | not searched | No FCC ID known |
-
-## The nearest available evidence
-
-The [X3 teardowns](../x3/media.md) — one 13-image English-captioned album, one
-10-image Chinese set **with a hand-drawn schematic** — are of the **same board
-family**: ESP32-C3, Puya 128 Mbit flash, the same shared-SPI architecture, the
-same construction style.
-
-They are **not a substitute**. The X3 has a different panel (792×528, UC8253), an
-RTC, a fuel gauge, an IMU and an NFC tag, none of which the X4 has. Use them for
-construction style and for the C3/flash identification only.
-
-## What is lost
-
-Because the X4 was delisted before any image of it was captured here, this record
-has **no photograph of the device at all** — not even a marketing render. Vendor
-imagery was not archived while the listing was live.
-
-**Lesson for this knowledge base:** capture vendor product imagery at the time of
-first observation, because delisting removes it. The X4 Pro and X3 listings are
-live *now* and their images are enumerable from
-`scratch/xteink/vendor/products-p1.json` (`products[].images[].src`).
-
-## Recovery options
-
-| Route | Status |
-|---|---|
-| Wayback Machine snapshot of the X4 product page | **Attempted and failed** — CDX timed out. Worth retrying with a longer timeout or `matchType=prefix` |
-| Community photos in Reddit posts | Many exist as Reddit-hosted images; **not enumerated** this session |
-| A new teardown | Nobody has posted one |
-
----
-
-## ⚠ Correction, 2026-09-11 — Xteink FCC grants exist
-
-The line(s) below, still present above and deliberately unedited, are **refuted**:
-
-> *line 12:* | FCC internal photos | not searched | No FCC ID known |
->
-
-**Xteink is an FCC grantee.** Applicant **Shenzhen Xiaohu Xingtong Technology Co., Ltd.**, grantee code **`2BTR9`**, registered 2025-12-21, holding **five granted Original Equipment authorisations**:
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-The original finding confused **"no mark visible in a product photograph"** with **"no grant exists"**. Those are different claims, and only the first was tested.
-
-- ✅ **Survives:** no FCC ID was legible on the exteriors photographed. Not re-tested.
-- ❌ **Refuted:** any reading that these devices are uncertified or unauthorised for the US.
-
-47 CFR §2.935 permits an **e-label** in software instead of a printed mark, which is ordinary for a device with a screen. **That is a likely explanation and it was not verified.**
-
-The absence was never re-searched in 2026-09-04 because **no FCC ID was known and the grantee code had not been found**. Enumerating the grantee — not searching the product name — is what resolved it. Method: [`guides/research/finding-certification-records.md`](../../../guides/research/finding-certification-records.md).
-
-Full record, with controls: [`certification-and-compliance.md`](certification-and-compliance.md).
-
-Listed in [`scratch/index-merge/corrections-requiring-review.md`](../../../scratch/index-merge/corrections-requiring-review.md).
diff --git a/devices/xteink/x4/performance.md b/devices/xteink/x4/performance.md
deleted file mode 100644
index 067d7eb..0000000
--- a/devices/xteink/x4/performance.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Xteink X4 — performance
-
-> **Nothing was measured by this session.** The figures below are the only
-> quantitative performance data that exists for any Xteink device, and all of it
-> comes from one source. Retrieved **2026-09-04**.
-
-## Display plane-write timing
-
-| Configuration | Plane write | Spec status | Source |
-|---|---:|---|---|
-| **20 MHz** — FreeInk default | **~38 ms / refresh** | SSD1677 datasheet write maximum | **[SDK]** `BoardConfig.h:830–843` |
-| **40 MHz** — `-DFREEINK_X4_OVERCLOCK_SPI` | **~19 ms** (saves ~17–20 ms) | **2× datasheet. Out of spec** | same |
-
-Method, environment, sample count and instrumentation are **not stated** by the
-source. Treat these as **developer-reported indicative figures**, not measurements
-with error bars. They are recorded because they are the only numbers in the
-subject and because the trade-off they describe is real and actionable.
-
-The 40 MHz mode is what the **CrossPoint / Witch Reader** fork shipped. The SDK
-made it opt-in and warns it *"can glitch plane writes on marginal wiring"* — a
-glitched plane write is a visibly corrupt page, not a crash.
-
-**A trap in the same code:** `Ssd1677Driver`'s internal default is **40 MHz**, so
-any board profile leaving `displaySpiHz = 0` runs **out of spec silently**. The X4
-profile sets it explicitly for exactly this reason.
-
-## Button ADC — the only multi-unit data in the family
-
-Raw 12-bit readings from **three physical devices** (**[SDK]** `InputManager.cpp:29–45`):
-
-| | BACK | CONFIRM | LEFT | RIGHT |
-|---|---:|---:|---:|---:|
-| unit 1 | 3597 | 2760 | 1530 | 6 |
-| unit 2 | 3470 | 2666 | 1480 | 6 |
-| unit 3 | 3470 | 2655 | 1470 | 3 |
-| **mean** | **3512** | **2694** | **1493** | **5** |
-| spread | 3.6 % | 3.9 % | 4.0 % | — |
-
-**n = 3.** Unit-to-unit spread is ~4 % at the top of the ladder — small, but the
-SDK deliberately derives thresholds as **midpoints between adjacent means** rather
-than fixed values because they are *"much more tolerant of different devices"*.
-
-This is the only place in the Xteink subject where anyone sampled more than one
-physical unit.
-
-## What has never been measured
-
-| Quantity | Status |
-|---|---|
-| **Battery capacity** | **Unknown.** The X3 is 650 mAh by teardown; the X4 is unmeasured |
-| **Runtime** | No figure from any source |
-| **Active current** | Never measured |
-| **Sleep current** | Never measured — and the X4 **cannot power down its SD card**, so it is structurally worse than the X3 here |
-| **Boot time** | Never measured |
-| **Wi-Fi throughput / range** | Never measured |
-| **SD read/write rate** | Never measured. The card **shares the display SPI bus**, so any figure would be workload-dependent |
-| **Page-turn latency, end to end** | Never measured — the ~38/19 ms figures are *plane writes*, not full refreshes including waveform time |
-
-## The measurement that was attempted and abandoned
-
-The author of the [X3 teardown](../x3/media.md) stated their purpose plainly:
-
-> "…so I can attach a **Nordic Power Profiler Kit II** to it to see if I can make
-> any power optimizations to crosspoint firmware."
-> — [r/xteinkereader `1uksv6s`](https://old.reddit.com/r/xteinkereader/comments/1uksv6s/), 2026-07-01
-
-**No results were ever posted.** That is the closest anyone has come to
-instrumenting this board family, and it produced nothing. Recorded so the next
-person knows the attempt was made.
-
-## Known performance failure
-
-**Out-of-memory during OTA** on the C3 devices. CrossPoint abandoned GitHub
-releases as an update channel because *"it causes out of memory issues on the x3"*
-([r/XTEINK `1uek163`](https://old.reddit.com/r/XTEINK/comments/1uek163/), 2026-06-24).
-The X4 shares the SoC and the **absence of PSRAM**, which is the root cause.
-
-This is the clearest practical performance difference between the C3 and S3
-generations: the [X4 Pro](../x4-pro/README.md) and X4 Classic have **8 MB PSRAM**
-and support multi-buffer rendering and damage-window partial refresh; the X4
-cannot.
-
-## Honest summary
-
-**Two indicative timing figures and one three-unit ADC sample.** Everything a
-buyer or developer would actually want to know — battery life, sleep current,
-refresh latency — is **unmeasured by anyone**.
diff --git a/devices/xteink/x4/pinouts-and-buses.md b/devices/xteink/x4/pinouts-and-buses.md
deleted file mode 100644
index ffaf090..0000000
--- a/devices/xteink/x4/pinouts-and-buses.md
+++ /dev/null
@@ -1,172 +0,0 @@
-# Xteink X4 — pinouts and buses
-
-> ESP32-C3. Reconstructed from `BoardConfig::XTEINK_X4`
-> (**[SDK]** `BoardConfig.h:844–874`, commit `24003795381a6c23630a26472ae3b06550333e71`)
-> and `InputManager` for the ADC ladder. Retrieved **2026-09-04**.
-
-Permalink:
-`https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L844-L874`
-
-Corroboration: the [X3 teardowns](../x3/media.md) are of the **same board family**
-and their author states the main pins were *"measured with a multimeter and
-cross-checked against the CrossPoint project source"*.
-
-## Complete GPIO map
-
-| GPIO | Signal | Dir | Bus / role | Notes |
-|---:|---|---|---|---|
-| **0** | **Battery voltage ADC** | in | ADC1_CH0 | `batteryDividerMultiplier = 2.0` |
-| **1** | **Button ADC ladder group 1** | in | ADC1_CH1 | Back / Confirm / Left / Right |
-| **2** | **Button ADC ladder group 2** | in | ADC1_CH2 | Up / Down |
-| **3** | **Power button** | in | digital | active-LOW (`INPUT_PULLUP`) |
-| **4** | EPD **DC** | out | display | |
-| **5** | EPD **RST** | out | display | |
-| **6** | EPD **BUSY** | in | display | |
-| **7** | SD **MISO** | in | shared SPI | the only SD-specific data line |
-| **8** | **SCLK** | out | **shared SPI** | display **and** SD |
-| **10** | **MOSI** | out | **shared SPI** | display **and** SD |
-| **12** | SD **CS** | out | shared SPI | |
-| **13** | **Battery MOSFET latch** | out | power | HIGH = hold; **LOW = power off** |
-| **20** | `usbDetect` | in | USB | **see the conflict note below** |
-| **21** | EPD **CS** | out | display | |
-
-`batteryChargeStatus`, `sd.powerEnable`, `display.powerEnable`: **unassigned**.
-
-### GPIO20 — an unresolved conflict
-
-The X4 profile sets `usbDetect = 20`. On the **X3**, which shares this board
-layout, **GPIO20 is the I²C SDA line** (`X3_I2C_SDA = 20`,
-**[SDK]** `XteinkDetect.cpp`). The X4 has no I²C peripherals, so the pin is free
-here — but the two profiles assign the same physical pin two different roles, and
-**neither assignment is marked hardware-confirmed**.
-
-Most likely reading: the X4 genuinely uses GPIO20 for USB presence and the X3
-repurposed it for I²C when the RTC/gauge/IMU were added. **Not verified.** See
-[`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-
-## Display bus
-
-| Signal | GPIO |
-|---|---:|
-| SCLK | **8** |
-| MOSI | **10** |
-| CS | **21** |
-| DC | **4** |
-| RST | **5** |
-| BUSY | **6** |
-| powerEnable | — |
-
-**Clock policy, quoted from the source:**
-
-```c
-// BoardConfig.h:830-843
-// Default 20 MHz = SSD1677 datasheet max for write mode … The plane writes are
-// ~38 ms/refresh at 20 MHz. Define -DFREEINK_X4_OVERCLOCK_SPI to run 40 MHz — the
-// (out-of-spec, 2x datasheet) clock the CrossPoint / Witch Reader fork used, which
-// halves that to ~19 ms … but can glitch plane writes on marginal wiring.
-```
-
-The SDK cites the SSD1677 datasheet directly:
-`https://files.waveshare.com/upload/2/2a/SSD1677_1.0.pdf` — *"MCU interface: SPI
-serial peripheral, Maximum 20 MHz for write"*.
-
-**Note a trap:** `Ssd1677Driver`'s own 0-default is **40 MHz**, so any board that
-leaves `displaySpiHz = 0` silently runs out of spec.
-
-## SD card — shares the display SPI bus
-
-| Signal | GPIO |
-|---|---:|
-| SCLK | **8** (shared) |
-| MOSI | **10** (shared) |
-| MISO | **7** |
-| CS | **12** |
-| powerEnable | **none** |
-
-`separateSpi = false`, `spiHz = 0` (SD manager default, 40 MHz).
-
-**Consequence:** the panel and the card contend for one bus. There is no
-arbitration beyond chip select, so a large card read stalls display updates.
-Unlike the [X3](../x3/pinouts-and-buses.md), the X4 has **no SD power enable**, so
-the card cannot be powered down for sleep.
-
-## Input — the ADC resistor ladder
-
-`InputStyle::XteinkAdcLadder`. Six buttons on **two** ADC pins.
-
-**[SDK]** `InputManager.h:73–74, 411–414` and `InputManager.cpp:29–45`.
-
-### Group 1 — GPIO1, four buttons
-
-Recorded raw 12-bit values from three real devices:
-
-| | BACK | CONFIRM | LEFT | RIGHT |
-|---|---:|---:|---:|---:|
-| unit 1 | 3597 | 2760 | 1530 | 6 |
-| unit 2 | 3470 | 2666 | 1480 | 6 |
-| unit 3 | 3470 | 2655 | 1470 | 3 |
-| **average** | **3512** | **2694** | **1493** | **5** |
-
-Decision thresholds are the midpoints of adjacent averages:
-
-```c
-const int InputManager::ADC_RANGES_1[] = {ADC_NO_BUTTON, 3100, 2090, 750, INT32_MIN};
-```
-Button `i` is pressed when `ranges[i+1] < adc <= ranges[i]`.
-
-### Group 2 — GPIO2, two buttons
-
-```c
-const int InputManager::ADC_RANGES_2[] = {ADC_NO_BUTTON, 1120, INT32_MIN};
-// local index 0/1 is remapped to BTN_UP / BTN_DOWN by adding 4
-```
-
-### Setup
-
-```c
-pinMode(1, INPUT); pinMode(2, INPUT);
-pinMode(3, INPUT_PULLUP);          // power, active-LOW
-analogSetAttenuation(ADC_11db);
-```
-
-**Only one button per group is detectable at a time** — a resistor ladder produces
-one voltage. Chords across the two groups work; chords within a group do not.
-
-The `InputPins` struct values `{0,1,2,3,4,5,3,false}` are **logical button indices,
-not GPIOs**, for every field except `power` (GPIO3). Reading them as pin numbers is
-an easy and serious mistake.
-
-## Power
-
-| Rail | GPIO | Note |
-|---|---:|---|
-| Battery MOSFET latch | **13** | Assert HIGH to hold power. **Drive LOW to power off** |
-| Battery sense | 0 | ADC, ÷2 divider |
-
-**Two board revisions exist.** Most units self-latch through a pull once the power
-button bridges the rail, so firmware never needed to assert GPIO13. **At least one
-field revision does not self-latch and stays powered only while the button is
-held.** Asserting the latch is harmless on self-latching units — always do it.
-
-Note the same GPIO13 is the **SD power enable on the X3**. The X4 keeps it as
-`power.latch0`, driven by the consumer's sleep path, and it is *"left unchanged"*
-by the SD code.
-
-## Resource conflicts
-
-| Resource | Contenders | Note |
-|---|---|---|
-| SPI bus (8/10) | EPD **and** microSD | Only CS separates them |
-| GPIO13 | Power latch (X4) vs SD rail (X3) | **Same pin, different meaning per model** — do not port blindly |
-| GPIO20 | `usbDetect` (X4) vs I²C SDA (X3) | Unresolved |
-| ADC1 | GPIO0 battery + GPIO1/2 buttons | Three channels of one ADC; sequential reads |
-
-## Absent
-
-No I²C bus, no RTC, no fuel gauge, no IMU, no touch, no frontlight, no SDMMC, no
-audio, no LEDs, no NFC. `NO_SENSORS`, `NO_GAUGE`, `NO_TOUCH`, `NO_FRONTLIGHT`,
-`NO_AUDIO`, `NO_LEDS`, `NO_SDMMC`, `NO_MIC`.
-
-**This absence is itself the X3/X4 runtime discriminator**: `XteinkDetect` probes
-SDA20/SCL0 for a BQ27220 (0x55), DS3231 (0x68) and QMI8658 (0x6B). Finding them
-means X3; finding nothing means X4.
diff --git a/devices/xteink/x4/product-history-and-family.md b/devices/xteink/x4/product-history-and-family.md
deleted file mode 100644
index 6f93f2e..0000000
--- a/devices/xteink/x4/product-history-and-family.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# Xteink X4 — product history and family
-
-Dated timeline. Full family context: [`../README.md`](../README.md).
-
-## Timeline
-
-| Date | Event | Evidence |
-|---|---|---|
-| **2025-06-18** | **Earliest English sighting.** A Chinese **group buy**, ~**€30**, described as *"星瞳X4, 4.3″ display, 74 g, 5.9 mm thin, strong magnetic back"* | **[COMM]** [r/ereader `1leohjp`](https://old.reddit.com/r/ereader/comments/1leohjp/), 295 pts |
-| 2025-09-01 | First detailed English owner report, titled *"Xteink Star Pupil X4 (星瞳X4) first impressions"* | **[COMM]** [r/ereader `1n5kmpc`](https://old.reddit.com/r/ereader/comments/1n5kmpc/), 191 pts |
-| **2025-10-09** | **Founder "Crusoe" introduces the company on Reddit** — *"a small team based in Shenzhen"*, X4 described as their *"4.3-inch model"* | **[COMM]** [r/ereader `1o2203h`](https://old.reddit.com/r/ereader/comments/1o2203h/), **1,477 pts** |
-| 2025-10-20/21 | First r/eink unboxings; *"the smallest e-reader so far"* | **[COMM]** |
-| 2025-10-21 / 10-23 | X4 magnetic case and tempered-glass protector listed on `xteink.com` | **[VENDOR]** |
-| 2025-11 – 12 | CrossPoint custom firmware for the X4 appears; community digests report restocking pressure | **[COMM]** |
-| 2025-12-09/11 | **X3 announced** as the smaller successor — *"builds on everything we learned from building the X4"* | **[COMM]** |
-| 2026-01-21 | X4 protective case listed | **[VENDOR]** |
-| 2026-02-11 | Owner measures **114 × 70 × 7 mm, 80 g, 220 PPI, 4 front + 3 side buttons** | **[COMM]** [r/Ultralight `1r1jfny`](https://old.reddit.com/r/Ultralight/comments/1r1jfny/) |
-| 2026-02-23 | Community notes the device **carries no CE or FCC label** | **[COMM]** [r/xteinkereader `1rcjtb4`](https://old.reddit.com/r/xteinkereader/comments/1rcjtb4/) |
-| 2026-06-20 | **20 % off** sale, run jointly with the CrossPoint project via an affiliate link; vendor sells a **developer-unlocked variant** | **[COMM]** [`1uan67g`](https://old.reddit.com/r/xteinkereader/comments/1uan67g/), 338 pts |
-| **2026-07-08** | **X4 matte screen protector listed — the last X4 accessory ever added** | **[VENDOR]** |
-| 2026-07-21 | **X4 Pro launches** at $99 | **[VENDOR]** |
-| 2026-08-23 | Owners of all three call the X4 *"obsolete… and also literally discontinued"* | **[COMM]** [`1vw6haq`](https://old.reddit.com/r/XTEINK/comments/1vw6haq/) |
-| **2026-08-25** | **Vendor confirms via Instagram that an "X4 version 2" is coming in September** | **[COMM]** [`1vxsr0x`](https://old.reddit.com/r/xteinkereader/comments/1vxsr0x/), 52 pts |
-| **2026-09-04** | **Delisted.** Device absent from the catalogue; **all four X4-specific accessory SKUs sold out** | **[VENDOR]** |
-
-## The launch model is unusual and worth recording
-
-The X4 did **not** launch as a retail product. It launched as a **Chinese
-group buy** — a batch pre-order organised among *"mandarin speaking ereader fans
-from mainland China and Taiwan"* — at roughly **€30**, roughly four months before
-`xteink.com` existed as an international storefront.
-
-That explains several otherwise-odd facts about this family:
-
-- **No CE/FCC marking**, because the first units were never intended for export.
-- **No distributor network**, because the model was direct-to-community.
-- **A proprietary `.XTC` book format** and a Chinese-first UI.
-- **A vendor that talks to Reddit and Xiaohongshu rather than to press.**
-
-## Position in the family
-
-| | X4 | Successors |
-|---|---|---|
-| Role | **The original.** The device the whole firmware ecosystem was written for | — |
-| Direct successor | none, yet — **X4 v2 announced for Sept 2026** | unconfirmed spec |
-| Smaller sibling | [X3](../x3/README.md) — 3.7″, 55 g, sharper, more sensors, pogo charging | current |
-| Upmarket sibling | [X4 Pro](../x4-pro/README.md) — ESP32-S3, PSRAM, touch, frontlight, pogo | current |
-| Buttons-only S3 sibling | [X4 Classic](../x4-classic/README.md) | not internationally listed |
-| Android sibling | [S4](../s4/README.md) | China-first |
-| Accessory line | [Nano / Tong Card](../nano/README.md) — NFC-powered e-paper card | China-first |
-
-**The X4 is the only member with USB-C charging**, which is precisely why several
-owners refuse to move to its successors.
-
-## Unresolved: 74 g / 5.9 mm versus 80 g / 7 mm
-
-| Source | Date | Figures |
-|---|---|---|
-| Group-buy post title | 2025-06-18 | **74 g, 5.9 mm** |
-| Owner review | 2026-02-11 | **80 g** *"including the screen protector"*, ~**7 mm** |
-
-Either two builds exist, or the difference is a screen protector plus measurement
-technique. **Unresolved** — see [`gaps-and-conflicts.md`](gaps-and-conflicts.md).
-It matters because **two undistinguishable board revisions are already known to
-exist** (the power-latch difference), so a physical difference is not implausible.
diff --git a/devices/xteink/x4/projects-and-community.md b/devices/xteink/x4/projects-and-community.md
deleted file mode 100644
index 1662446..0000000
--- a/devices/xteink/x4/projects-and-community.md
+++ /dev/null
@@ -1,128 +0,0 @@
-# Xteink X4 — projects
-
-> Census **2026-09-04**: GitHub repository search API, 5 queries × 2 pages,
-> authenticated. **~200 relevant repositories**, of which the clear majority name
-> the X4 specifically. Owner-report material is in [`community.md`](community.md).
-
-## Why the X4 has the biggest ecosystem
-
-It was **first**, it was **cheap**, and it was **the target every firmware started
-on**. CrossPoint Reader, CrossInk, Microreader, marigold-os, TrustyReader,
-pluspoint-reader and AALU were all written for the X4 and grew to cover the X3 and
-the S3 devices afterwards. Even now, records that describe the family usually say
-*"for the Xteink X3 and X4"* — in that order only because X3 sorts first.
-
-## Firmware targeting the X4
-
-### The two mainlines
-
-| Project | Licence | Note |
-|---|---|---|
-| [`crosspoint-reader/crosspoint-reader`](https://github.com/crosspoint-reader/crosspoint-reader) | MIT | Upstream. The X4 is its original target |
-| [`uxjulia/CrossInk`](https://github.com/uxjulia/CrossInk) | MIT | The other lineage. Ships an [SDL simulator](https://github.com/uxjulia/crossink-simulator) |
-| [`Free-Ink/freeink-sdk`](https://github.com/Free-Ink/freeink-sdk) | — | **The HAL under both**, and the source of every board fact in this record |
-
-### Independent firmware — not CrossPoint forks
-
-Unusually for a cheap device, several people wrote firmware **from scratch or in
-other languages**:
-
-| Project | Language | Note |
-|---|---|---|
-| [`CidVonHighwind/microreader`](https://github.com/CidVonHighwind/microreader) | C++ | GPLv2. *"If you have an unlocked X4 (**!!!UNLOCKED!!!**)"* — 514 pts on announcement |
-| [`ngxson/pluspoint-reader`](https://github.com/ngxson/pluspoint-reader) | C | *"Yet another alternative firmware for Xteink X4"* |
-| [`Jon-Vii/marigold-os`](https://github.com/Jon-Vii/marigold-os) | **Rust** | MIT. X4 and X3 |
-| [`HookedBehemoth/TrustyReader`](https://github.com/HookedBehemoth/TrustyReader) | **Rust** | GPL-2.0 |
-| [`aimindseye/rustmix-x4-firmware`](https://github.com/aimindseye/rustmix-x4-firmware), [`h0rv/rust-xteink-x4`](https://github.com/h0rv/rust-xteink-x4), [`yanganto/xteink-x4`](https://github.com/yanganto/xteink-x4) | **Rust** | Three more |
-| [`h0rv/slint-xteink-backend`](https://github.com/h0rv/slint-xteink-backend) | Rust | A **Slint UI backend** for Xteink devices |
-| [`evanstoddard/xteink_x3_zephyr`](https://github.com/evanstoddard/xteink_x3_zephyr) | — | **Zephyr RTOS** (X3, same board family) |
-| [`adafruit/Adafruit_CircuitPython_Xteink_X4`](https://github.com/adafruit/Adafruit_CircuitPython_Xteink_X4) | Python | **Adafruit** published a CircuitPython helper — a notable third-party endorsement |
-
-**Six independent Rust efforts** on one $69 consumer device is remarkable, and is
-a direct consequence of the ESP32-C3's RISC-V core having good Rust support.
-
-### Notable forks and applications
-
-`AALU` (installs on locked devices via SD), `Flowe` (focus firmware + iOS BLE app,
-303 pts), `Duet` ([`lauren-alexandra/duet-xteink`](https://github.com/lauren-alexandra/duet-xteink)),
-`inkMOD` (Russian/Ukrainian, FB2), `BookPoint` (Russian), `crossmosa` (繁體中文),
-`CrossPlant`, `SkyPoint`, `casper`, `crossfade`, `InkWyrm`, `CipherCodex OS`,
-`Lector`, `PocketBook`, `CrossMux` (a Chinese fork adding **WeChat Read** support).
-
-### Novelty and games
-
-[`davidpavlicek36/doom-xt4`](https://github.com/davidpavlicek36/doom-xt4) — **Doom
-on the X4** · [`CidVonHighwind/xteink-bad-apple`](https://github.com/CidVonHighwind/xteink-bad-apple)
-· [`cassidoo/xteink-4-in-a-row`](https://github.com/cassidoo/xteink-4-in-a-row)
-· [`HenryBaby/TamaInk`](https://github.com/HenryBaby/TamaInk) (Tamagotchi P1)
-· [`lodyb/crosspoint-reader`](https://github.com/lodyb/crosspoint-reader) (MTG life tracker)
-· [`padge01/xteink-pokemon-game`](https://github.com/padge01/xteink-pokemon-game).
-
-### Non-reader uses of the hardware
-
-| Project | What |
-|---|---|
-| [`maddiedreese/xteink-terminal`](https://github.com/maddiedreese/xteink-terminal) | ★32 — *"tmux bridge for using an XTeInk X4 as a small Wi-Fi e-ink terminal display"* |
-| [`keithwithAI/xteink-agenda`](https://github.com/keithwithAI/xteink-agenda) | Google Calendar via a FastAPI server |
-| [`fsocietyipa/WienerLinien-XteinkX4`](https://github.com/fsocietyipa/WienerLinien-XteinkX4) | Vienna transit departure board |
-| [`pocmaker42/xteink-todo`](https://github.com/pocmaker42/xteink-todo) | Web UI + PHP API + firmware |
-| [`t0nyz0/crosspoint-reader-lockscreens`](https://github.com/t0nyz0/crosspoint-reader-lockscreens) | GitHub / Weather / Tempest dashboards |
-| [`vjFaLk/esphome-xteink`](https://github.com/vjFaLk/esphome-xteink) | **ESPHome** components wrapping the FreeInk SDK |
-
-## Flashing, backup and recovery tooling
-
-| Tool | Language | Note |
-|---|---|---|
-| [`zocs/eink-quick-flasher`](https://github.com/zocs/eink-quick-flasher) | Python | **1:1 full-flash backup & restore in ~2 min**, auto COM detect, ships stock images |
-| [`bigbag/papyrix-flasher`](https://github.com/bigbag/papyrix-flasher) | Go | ★25. Auto-detection, embedded bootloader, MD5 verification |
-| [`OvermindDL1/xteink-unlocker`](https://github.com/OvermindDL1/xteink-unlocker) | Rust/Tauri | Desktop unlocker with a privileged macOS helper |
-| [`togotago/xteink-x4-escape`](https://github.com/togotago/xteink-x4-escape) | Python | **A named brick and its cure** — CrossPoint 1.2.0 OTA failing at `esp_ota_end()` |
-| [`lvturner/x4-dual-boot`](https://github.com/lvturner/x4-dual-boot) | Shell | MicroSlate + CrossInk **dual-boot on a USB-locked X4** via SD |
-| [`abhishek-nerella/XTEINK-OEM-BIN-`](https://github.com/abhishek-nerella/XTEINK-OEM-BIN-) | — | The **16 MB factory dump** archived in this record |
-
-## The `.XTC` format problem
-
-Stock firmware uses a proprietary **`.XTC`** book format, which spawned an entire
-converter cottage industry: [`thirteen37/calibre-xtc`](https://github.com/thirteen37/calibre-xtc)
-(★19), [`jonasdiemer/epub2xtc`](https://github.com/jonasdiemer/epub2xtc),
-[`alf-arv/epub-to-xtc-util`](https://github.com/alf-arv/epub-to-xtc-util),
-[`domschl/PDF2XTEink`](https://github.com/domschl/PDF2XTEink),
-[`smalltomatowater-boop/xtmaker`](https://github.com/smalltomatowater-boop/xtmaker).
-
-**Its existence is one of the strongest arguments for reflashing**: community
-firmware reads EPUB directly.
-
-## Fonts, wallpapers, sync
-
-Font tooling ([`SamLinBIT/XTEink-ttf2bin`](https://github.com/SamLinBIT/XTEink-ttf2bin),
-[`iwalton3/cpfont-editor`](https://github.com/iwalton3/cpfont-editor),
-[`enfance-prog/Xteink-Fontbuilder-mac`](https://github.com/enfance-prog/Xteink-Fontbuilder-mac),
-`crossglyph`); wallpaper generators (XKCD, Pokédex, Truchet, Wikimedia,
-countries); OPDS and sync servers ([`rcarmo/bun-opds-server`](https://github.com/rcarmo/bun-opds-server),
-[`sroberts/shelf`](https://github.com/sroberts/shelf),
-[`LowFlowIO/x4m`](https://github.com/LowFlowIO/x4m)); companion apps for
-[macOS](https://github.com/lukataylo/crosspoint-mac),
-[Android](https://github.com/duplexer/crosspoint-companion-pro) and
-[iOS](https://github.com/AirBook-for-CrossPoint).
-
-## Localisation
-
-Independent ports into **~12 languages**: Chinese (simplified + 繁體), Japanese,
-Korean, Arabic, Russian, Ukrainian, Myanmar, Persian, Gujarati, Vietnamese,
-Portuguese, Spanish. For a device with no distributor network, that is a strong
-install-base signal.
-
-## Community services
-
-| Site | Purpose |
-|---|---|
-| `crosspointreader.com` | **Device unlock**, web flasher, flash-back-to-stock, nightly builds |
-| `crossink.uxj.io` | CrossInk documentation |
-| `brickclub.pages.dev` | Firmware chooser — the name is a joke about bricking |
-| `readme.club` | Community hub with a model-selection quiz and spec comparisons; **linked by an r/XTEINK automoderator rule** |
-
-## Evidence caveat
-
-This is a **census, not an audit.** A repository proves someone started something.
-It does not prove the code builds, runs, or was flashed to an X4. Only the FreeInk
-SDK's claims are treated as hardware-confirmed elsewhere in this record.
diff --git a/devices/xteink/x4/research-log.md b/devices/xteink/x4/research-log.md
deleted file mode 100644
index f573eb6..0000000
--- a/devices/xteink/x4/research-log.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Xteink X4 — research log
-
-The **family-wide** log — source classes, query ledger, Reddit and GitHub search
-depth, dead links and the stopping criterion — is at
-[`../x4-pro/research-log.md`](../x4-pro/research-log.md) and covers all six
-Xteink products. This page records only what was **X4-specific**, plus the
-second sweep performed after the first pass.
-
-## X4-specific queries and outcomes
-
-| Query / target | Depth | Outcome |
-|---|---|---|
-| `xteink x4` (GitHub repos) | 2 pages, 198 total | Most of the ~200-repo census names this device |
-| `abhishek-nerella/XTEINK-OEM-BIN-` repo + tree | full | **Found and retrieved a 16 MB factory dump** — the only Xteink firmware image obtained |
-| `zocs/eink-quick-flasher` tree + `firmware/README.md` | full | Stock versions **V5.1.6 (EN)** and **V5.2.13 (CN)**; the `.bin` files are **Git LFS pointers** and were **not** fetched |
-| `xteink teardown`, `xteink teardown chip` | 100 results each | **No X4 teardown exists.** Both teardowns found are X3 |
-| `/collections/x4-series/products.json` | full | **Device absent; all 4 accessory SKUs sold out** → delisted |
-| Wayback CDX for the delisted X4 product page | 1 attempt | **Timed out at 60 s, 0 bytes. Not retried.** Still unrecovered |
-
-## Second sweep — 2026-09-04, after the first pass
-
-The first pass covered the three dedicated subreddits. A second sweep added
-**topic subreddits** and **Chinese-language terms**, and materially changed the
-record.
-
-| Added | Queries | New posts |
-|---|---|---|
-| `r/{eink,ereader,esp32,ebookreaders,Kindle,koreader}` with `restrict_sr=1` | 6 | — |
-| `xteink nfc`, `xteink ppi`, `xteink x4 pro review`, `xteink x4 classic`, `xteink s4 specs`, `xteink schematic`, `xteink fcc` | 7 | — |
-| **`阅星瞳`**, **`星瞳 电纸书`** | 2 | — |
-| **Total** | 15 | **+338 → 2,136 unique posts** |
-
-### What the second sweep found that the first missed
-
-| Finding | Why it was missed first time |
-|---|---|
-| **The earliest X4 evidence is a 2025-06-18 Chinese group buy at €30, 74 g, 5.9 mm** | It is in r/ereader, not a dedicated sub, and predates the brand's English presence |
-| **A fifth product: the "Nano" / Tong Card (瞳卡)** | Discussed in r/xteinkHax and r/microreaders only |
-| **A sixth subreddit, r/microreaders** | Not in the first sub census |
-| **The X3's NFC purpose — resolved** | Required a GitHub *discussion*, not a repository |
-| **An "X4 version 2" confirmed by the vendor for Sept 2026** | Posted 2026-08-25, in the vendor-run sub |
-| **Xteink devices carry no external CE/FCC marking** | A low-scoring (4 pt) thread that only a targeted `fcc` query surfaced |
-| **Amazon.ca / Amazon / Xianyu / AliExpress are real channels, with unpredictable USB-lock state** | Buried in a comment thread about back-casing variants |
-| **One of the three subreddits is vendor-operated** | Stated in a comment on a post that had been *removed from that sub* |
-
-**Method note worth keeping:** searching a product's *dedicated* subreddits finds
-the enthusiast core and misses the origin story, the adjacent products and the
-regulatory reality. The `restrict_sr=1` sweep across topic subreddits cost 6
-requests and changed several conclusions.
-
-## Targeted thread retrievals (with comments)
-
-Eight threads were fetched with full comment trees, not just listings —
-`old.reddit.com/<permalink>.json?limit=200`, UA `WhatsApp/2.23.20.0`, all 200:
-
-`cefcc` · `tongcard` · `nano` · `x4v2` · `x3newer` · `nfc` · `compare` ·
-`starpupil`.
-
-**Comments carried most of the value.** The regulatory finding, the channel/lock
-correlation, the vendor-operated-subreddit statement and the NFC use cases were
-all in comment bodies, invisible in the listing JSON.
-
-## GitHub discussions — a source class the first pass missed entirely
-
-`gh api graphql` against
-`crosspoint-reader/crosspoint-reader` **discussion #2259** returned the
-authoritative statement on the X3's NFC tag. **Repository search does not index
-discussions**; they must be queried through GraphQL. Recorded as a reusable
-technique.
-
-## Dead / failed for this device
-
-| Target | Outcome |
-|---|---|
-| Wayback CDX, `xteink.com*` | **Timed out, 0 bytes.** The delisted X4 product page and its imagery remain unrecovered |
-| `x4_en_v5.1.6_ota.bin`, `x4_cn_v5.2.13_ota.bin` | **Git LFS pointers, not fetched.** Needs an LFS-aware client — cheap to close |
-| X4 SPIFFS contents (3.4 MB) | **Not extracted** from the dump |
-| `gotaserver.xteink.com/api/check-update` | **Not queried** |
-| Any X4 teardown | **Does not exist** |
-
-## Stopping criterion
-
-Two consecutive passes returned only duplicates for X4 *hardware* facts. The
-remaining sources are: a teardown (nobody has done one), an LFS fetch (cheap,
-deferred), a SPIFFS extraction (cheap, deferred), and Chinese marketplaces
-(declared exclusion).
-
-**Reproducible broad-coverage snapshot dated 2026-09-04.** Not proof that no other
-resource exists.
diff --git a/devices/xteink/x4/resources-and-conflicts.md b/devices/xteink/x4/resources-and-conflicts.md
deleted file mode 100644
index 199b1b7..0000000
--- a/devices/xteink/x4/resources-and-conflicts.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# Xteink X4 — resources and conflicts
-
-ESP32-C3, 16 MB flash, **no PSRAM**. Snapshot **2026-09-04**.
-
-## GPIO allocation — every pin accounted for
-
-| GPIO | Owner | Exclusive? | Notes |
-|---:|---|---|---|
-| 0 | Battery voltage ADC (ADC1_CH0) | shared with ADC1 timing | ÷2 divider |
-| 1 | Button ladder group 1 (ADC1_CH1) | shared with ADC1 timing | Back/Confirm/Left/Right |
-| 2 | Button ladder group 2 (ADC1_CH2) | shared with ADC1 timing | Up/Down |
-| 3 | Power button | ✅ | active-LOW |
-| 4 | EPD DC | ✅ | |
-| 5 | EPD RST | ✅ | |
-| 6 | EPD BUSY | ✅ | |
-| 7 | SD MISO | ✅ | the only SD-exclusive data line |
-| **8** | **SPI SCLK** | ❌ **display + SD** | |
-| **10** | **SPI MOSI** | ❌ **display + SD** | also released to input for the controller-ID probe |
-| 12 | SD CS | ✅ | |
-| 13 | Battery MOSFET latch | ✅ | **LOW = power off** |
-| 20 | `usbDetect` | ⚠ **contested** — see below | |
-| 21 | EPD CS | ✅ | |
-
-**No free GPIOs are identified.** Anyone wanting to add hardware to an X4 is
-taking a pin away from something.
-
-## The one real bus conflict
-
-**The e-paper controller and the microSD card share SCLK 8 and MOSI 10**, separated
-only by chip select (`sd.separateSpi = false`).
-
-| Consequence | Detail |
-|---|---|
-| **Serialisation** | A large card read stalls display refresh and vice versa. There is no arbitration beyond CS |
-| **Clock renegotiation** | The panel wants ≤20 MHz (or 40 MHz overclocked); the SD manager defaults to 40 MHz. The bus is reconfigured per transaction |
-| **Probe timing** | The controller-ID probe releases MOSI to **input** mid-transaction for a half-duplex read. It must run **before** `EpdBus::begin()` and must first `gpio_hold_dis()` the RST pin, or a retained sleep-path latch makes every `digitalWrite` silently bounce and the probe selects the wrong driver |
-
-The [X3](../x3/pinouts-and-buses.md) shares this design. The S3 devices moved the
-card to **native SDMMC on dedicated pins**, which is the single biggest
-architectural improvement between generations.
-
-## ADC1 contention
-
-Three functions on one ADC: battery sense (GPIO0) and both button ladder groups
-(GPIO1, GPIO2). Reads are sequential. `analogSetAttenuation(ADC_11db)` is set
-globally, so **the battery divider and the button ladder share an attenuation
-setting** — you cannot tune one without the other.
-
-**Only one button per ladder group is detectable at a time.** A resistor ladder
-produces one voltage; two simultaneous presses in the same group yield a third,
-wrong reading. Cross-group chords (e.g. Left + Up) work.
-
-## Memory
-
-| Resource | Value |
-|---|---|
-| SRAM | ~400 KB (ESP32-C3) |
-| **PSRAM** | **None** |
-| Flash | 16 MB |
-| App partitions | 2 × 6400 KiB (dual-OTA) |
-| SPIFFS | 3456 KiB |
-
-**The absence of PSRAM is the binding constraint.** It is the documented cause of
-OTA out-of-memory failures on this SoC class, and it is why the S3 devices can do
-multi-buffer rendering and damage-window partial refresh and this one cannot.
-
-## Flash partition map
-
-`nvs` `0x009000` (20 KiB) · `otadata` `0x00E000` (8 KiB) ·
-`app0` `0x010000` (6400 KiB) · `app1` `0x650000` (6400 KiB) ·
-`spiffs` `0xC90000` (3456 KiB) · `coredump` `0xFF0000` (64 KiB).
-
-Parsed directly from the factory dump. **Different from the X4 Pro's**
-(`0x7E0000` app slots, 80 KiB SPIFFS) — the X4 devotes ~40× more space to SPIFFS,
-consistent with serving a web file-manager UI from flash.
-
-## Power domains
-
-| Domain | Control | Note |
-|---|---|---|
-| Battery → system | **GPIO13 MOSFET latch** | **Two board revisions behave differently** — see below |
-| SD card | **none** | **The card cannot be powered down.** Structural sleep drain |
-| Display | none — controller's internal booster (`0x0C` soft-start) | No external PMIC, no charge pump |
-
-## Unresolved conflicts
-
-### GPIO20 — `usbDetect` or I²C SDA?
-
-`XTEINK_X4` sets `usbDetect = 20`. The X3 profile — same board family — sets
-**both** `usbDetect = 20` **and** `X3_I2C_SDA = 20`. The X4 has no I²C
-peripherals so the pin is free here, but **neither assignment is marked
-hardware-confirmed**, and the X4's may simply be inherited from a template.
-
-**Resolution:** scope GPIO20 during USB plug/unplug, or continuity-check it to the
-USB-C connector.
-
-### GPIO13 means three different things across the family
-
-| Device | GPIO13 |
-|---|---|
-| **X4** | **Battery MOSFET latch.** Drive LOW to power off |
-| [X3](../x3/pinouts-and-buses.md) | **SD power enable, active-HIGH** |
-| X4 Pro / X4 Classic | unused (their SD enables are GPIO5 / GPIO6, **active-LOW**) |
-
-**Never port power or sleep code between these devices without re-checking.**
-
-### Two X4 board revisions, indistinguishable
-
-Most units **self-latch** through a pull once the power button bridges the rail,
-so firmware never needed to assert GPIO13. **At least one field revision does not
-self-latch and stays powered only while the button is held.** Asserting the latch
-is a no-op on self-latching units — **always assert it**.
-
-**There is no known revision marking.** This is the most operationally important
-unknown about the device.
-
-## Realistic concurrent-use scenarios
-
-| Scenario | Assessment | Status |
-|---|---|---|
-| Page turn while streaming from SD | **Serialised** — one SPI bus | Not benchmarked |
-| Wi-Fi download + display refresh | Memory pressure likely (no PSRAM) | Not benchmarked |
-| OTA while low on heap | **Known to fail** on this SoC class | Reported |
-| Battery read during button poll | Sequential ADC1 reads; shared attenuation | Not benchmarked |
-| Deep sleep with an SD card inserted | **Card stays powered — no enable pin** | Never measured |
diff --git a/devices/xteink/x4/sources.md b/devices/xteink/x4/sources.md
deleted file mode 100644
index 212e90b..0000000
--- a/devices/xteink/x4/sources.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Xteink X4 — sources
-
-Retrieved **2026-09-04** unless stated.
-
-| ID | Title | Publisher/author | Class | Medium | URL | Retrieved | Published | Establishes | Limitations | Local path |
-|---|---|---|---|---|---|---|---|---|---|---|
-| **X401** | `freeink-sdk` `BoardConfig.h` `XTEINK_X4` L844–874 | Free-Ink | community | source (commit-pinned) | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/BoardConfig/include/BoardConfig.h#L844-L874> | 2026-09-04 | commit 2026-09-01 | **Every pin.** SPI clock policy, the GPIO13 latch and the two board revisions | Third-party RE; not vendor documentation | `scratch/eink-software/repos/freeink-sdk/` |
-| **X402** | `InputManager.cpp` L29–45, `InputManager.h` L73–74 | Free-Ink | community | source | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/InputManager/src/InputManager.cpp> | 2026-09-04 | same | **ADC ladder pins and raw readings from three physical devices** | — | same |
-| **X403** | `XteinkDetect.cpp` | Free-Ink | community | source | <https://github.com/Free-Ink/freeink-sdk/blob/24003795381a6c23630a26472ae3b06550333e71/libs/hardware/XteinkDetect/src/XteinkDetect.cpp> | 2026-09-04 | same | X3-vs-X4 I²C fingerprint; controller probe | — | same |
-| **X404** | **OEM full-flash dump, 16 MB** | re-uploaded by `abhishek-nerella` | community | firmware binary | <https://raw.githubusercontent.com/abhishek-nerella/XTEINK-OEM-BIN-/main/flash.bin> | 2026-09-04 | unknown | **Partition table, chip-id 5 = C3, app descriptor, OTA + web-manager endpoints** | **Provenance of the dump is undocumented.** Licence none declared | [archived](artifacts/firmware/xteink-x4-oem-full-flash-16mb.bin.ARCHIVED.md) |
-| **X405** | `zocs/eink-quick-flasher` firmware README | community dev | community | repository doc | <https://github.com/zocs/eink-quick-flasher/blob/main/firmware/README.md> | 2026-09-04 | — | Stock versions **V5.1.6 (EN)** and **V5.2.13 (CN)**; that **CN/EN differ only by default UI language** | The .bin files are Git LFS pointers; blobs **not fetched** | `scratch/xteink/firmware/zocs-firmware-README.md` |
-| **X406** | "The Xteink X4 - A Pocket-Sized E-Reader Gem" | r/Ultralight | community | forum, owner report | <https://old.reddit.com/r/Ultralight/comments/1r1jfny/> | 2026-09-04 | 2026-02-11, 51 pts | **114×70×7 mm, 80 g, 220 PPI, 4 front + 3 side buttons** | **Single source** for the physical dimensions | `scratch/xteink/reddit/_merged-posts.json` |
-| **X407** | "Hi everyone, I'm Crusoe from Xteink" | Xteink founder | **primary** (self-published) | forum post | <https://old.reddit.com/r/ereader/comments/1o2203h/> | 2026-09-04 | 2025-10-09, **1,477 pts** | Company is *"a small team based in Shenzhen"*; the X4 is their *"4.3-inch model"* | Founder marketing statement | same |
-| **X408** | "Xteink Star Pupil X4 (星瞳X4) first impressions" | r/ereader | community | forum, owner report | <https://old.reddit.com/r/ereader/comments/1n5kmpc/> | 2026-09-04 | 2025-09-01, 191 pts | **Chinese product name 星瞳 = "Star Pupil"**; earliest English owner report found | — | same |
-| **X409** | "X3 vs X4 - actual experience comparison" | r/xteinkereader | community | forum, comparative ownership | <https://old.reddit.com/r/xteinkereader/comments/1syav96/> | 2026-09-04 | 2026-04-28, **412 pts** | Button feel: X4 *"clickier and louder"*, X3 *"mushy and quieter"* | Subjective, firsthand | same |
-| **X410** | X4 accessory collection | Xteink | **primary** | store API | <https://www.xteink.com/collections/x4-series/products.json?limit=250> | 2026-09-04 | — | **The X4 device is absent; all 4 accessory SKUs sold out** → delisted | Snapshot | `scratch/xteink/vendor/coll-x4-series.json` |
-| **X411** | `togotago/xteink-x4-escape` | community dev | community | repository | <https://github.com/togotago/xteink-x4-escape> | 2026-09-04 | pushed 2026-05-10 | A named, reproducible brick (CrossPoint 1.2.0, OTA fails at `esp_ota_end()`) and its escape recipe | Not tested here | — |
-| **X412** | `adafruit/Adafruit_CircuitPython_Xteink_X4` | **Adafruit** | credible mirror | repository | <https://github.com/adafruit/Adafruit_CircuitPython_Xteink_X4> | 2026-09-04 | pushed 2026-04-23 | A major vendor published a CircuitPython helper for this device | Not inspected | — |
-
-## Corroboration map
-
-| Claim | Independent sources |
-|---|---|
-| SoC is ESP32-C3 | **[SDK]** profile · **[DUMP]** bootloader chip-id 5 · **[TD]** X3 photo caption · **[CN-TD]** Chinese BOM |
-| 16 MB flash | **[SDK]** · **[DUMP]** image length · **[TD]** *"128 MBit (16 MB) flash"* |
-| ~220 PPI | **[COMM]** owner report (220) · **arithmetic** from 800×480 / 4.26″ = 219 |
-| Delisted | **[VENDOR]** absent from catalogue · accessories sold out |
-
-## Not used as evidence
-
-`xteink.com` product prose (AI/SEO-generated); `aimindseye/xteink-x4` wiki
-(self-labelled AI-generated, no primary measurement).
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper
deleted file mode 120000
index 409080f..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper.ARCHIVED.link b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper.ARCHIVED.link
deleted file mode 120000
index dd44fcc..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper.ARCHIVED.link
+++ /dev/null
@@ -1 +0,0 @@
-e-Paper
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper.ARCHIVED.md
index e03e312..cf144af 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper.ARCHIVED.md
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper.ARCHIVED.md
@@ -25,7 +25,7 @@ repository** as patches plus a written analysis:
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper` |
 | Type | directory |
 | Size | **32,575,902 B (31.07 MiB)** |
 | File count | **272** (in 16 directories) |
@@ -54,21 +54,6 @@ Everything else is pure add/remove: 48 unused `examples/epd_*_test.py` and 5 `re
 by ZeroWriter; `build/`, `dist/`, `*.egg-info/`, `examples/waveshare_epd/`, `__pycache__/`,
 `.DS_Store` and `._.DS_Store` added locally by an in-place `pip install .` on macOS.
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter1`](https://github.com/zerowriter/zerowriter1) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter1`](https://github.com/zerowriter/zerowriter1) |
-| Base commit | [`e476d0567ac89104df62815f7bd2c807b8a3e140`](https://github.com/zerowriter/zerowriter1/tree/e476d0567ac89104df62815f7bd2c807b8a3e140) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter1/tree/e476d0567ac89104df62815f7bd2c807b8a3e140> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter1
-git -C zerowriter1 checkout e476d0567ac89104df62815f7bd2c807b8a3e140
-```
-
 ## How to get it back
 
 Verified **2026-08-24**.
@@ -125,7 +110,7 @@ differently under a UTF-8 locale, producing a different (and non-portable) diges
 ## Restore from the local archive
 
 ```bash
-mv archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper \
+mv ../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper \
    devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md
index ee8efca..6c6c647 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL` |
 | Type | directory |
 | Size | 6,099,031 B (5.82 MiB) |
 | File count | 5 |
@@ -32,33 +32,6 @@
 | `Zerowriter Inkplate 5 Gen2.kicad_pro` | 8,183 | `25009ad8a3e3cfd5db094696c680d4cf064619f4db812ebb7e54eb5d2d0717f2` |
 | `fp-info-cache` | 2 | `9a271f2a916b0b6ee6cecb2426f0b3206ef074578be55d9bc94f6f3fe3ab86aa` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -74,11 +47,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/zerowriter/zerowriter_ink>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL" \
+mv "../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md
index 6760b6c..ad0519d 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md	
@@ -31,7 +31,7 @@ and 3D-printable outputs all remain in place.
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups` |
-| Archived to | `scratch/zerowriter-provenance-2026-08-30/upstream/zerowriter_ink-996207aca0677300ed5f1fdf762d9c9ec79f516e/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups` |
+| Archived to | `../hardware-doc-archive/scratch/zerowriter-provenance-2026-08-30/upstream/zerowriter_ink-996207aca0677300ed5f1fdf762d9c9ec79f516e/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups` |
 | Type | directory of ZIP archives |
 | Size | **18449694 B** |
 | File count | **7** ZIP files |
@@ -63,39 +63,12 @@ uncompressed in the parent directory. Inspect on demand with `unzip -l` / `unzip
 
 
 > ⚠ **Path corrected 2026-08-30.** This placeholder originally pointed at
-> `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups`.
+> `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups`.
 > A later archiving pass moved the whole parent `PANEL/` directory onto that same archive path, which
 > replaced it. **The content was not lost** — it survives in full inside the upstream tarball
 > extraction under `scratch/zerowriter-provenance-2026-08-30/`, and the path above now points there.
 > Verified present ✅.
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../../../Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../../Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../../../../Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../../../Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 All statuses verified **2026-08-24**.
@@ -134,7 +107,7 @@ differently under a UTF-8 locale.
 ## Restore from the local archive
 
 ```bash
-mv "$HOME/repo-archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups" \
+mv "$HOME/hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pcb b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pcb
deleted file mode 120000
index 215433e..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pcb	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pcb
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_prl b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_prl
deleted file mode 120000
index 8d78a71..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_prl	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_prl
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pro b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pro
deleted file mode 120000
index f193c93..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pro	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2.kicad_pro
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/fp-info-cache b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/fp-info-cache
deleted file mode 120000
index 36ff724..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/fp-info-cache	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/fp-info-cache
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step
deleted file mode 120000
index fba7797..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.link b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.link
deleted file mode 120000
index eef3b4b..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Soldered Inkplate 5 Gen2 3D.step
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md
index 10edce3..4047d01 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step` |
 | Type | file |
 | Size | 14,189,797 B (13.53 MiB) |
 | SHA-256 | `6b03def0d0063e81f1002c0fd9959e3c6acddc1a31b99599e3eeb107fbd169d7` |
@@ -22,33 +22,6 @@
 | License | GPL-3.0 |
 | Path within upstream repo | `design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -66,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/zerowriter/zerowriter_ink>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step" \
+mv "../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md
index ab68fa7..e118528 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL` |
 | Type | directory |
 | Size | 3,518,422 B (3.36 MiB) |
 | File count | 5 |
@@ -32,33 +32,6 @@
 | `Zerowriter Keyboard.kicad_pro` | 7,982 | `3f3470ad9c7e933d5db86be03f537f6244fca94270ee1f43550b35bd3d03cb64` |
 | `fp-info-cache` | 2 | `9a271f2a916b0b6ee6cecb2426f0b3206ef074578be55d9bc94f6f3fe3ab86aa` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -74,11 +47,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/zerowriter/zerowriter_ink>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL" \
+mv "../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md
index 693a102..10e48ac 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md	
@@ -31,7 +31,7 @@ and 3D-printable outputs all remain in place.
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups` |
-| Archived to | `scratch/zerowriter-provenance-2026-08-30/upstream/zerowriter_ink-996207aca0677300ed5f1fdf762d9c9ec79f516e/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups` |
+| Archived to | `../hardware-doc-archive/scratch/zerowriter-provenance-2026-08-30/upstream/zerowriter_ink-996207aca0677300ed5f1fdf762d9c9ec79f516e/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups` |
 | Type | directory of ZIP archives |
 | Size | **2659337 B** |
 | File count | **3** ZIP files |
@@ -59,39 +59,12 @@ uncompressed in the parent directory. Inspect on demand with `unzip -l` / `unzip
 
 
 > ⚠ **Path corrected 2026-08-30.** This placeholder originally pointed at
-> `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups`.
+> `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups`.
 > A later archiving pass moved the whole parent `PANEL/` directory onto that same archive path, which
 > replaced it. **The content was not lost** — it survives in full inside the upstream tarball
 > extraction under `scratch/zerowriter-provenance-2026-08-30/`, and the path above now points there.
 > Verified present ✅.
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../../../Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../../Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../../../../Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../../../Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 All statuses verified **2026-08-24**.
@@ -130,7 +103,7 @@ differently under a UTF-8 locale.
 ## Restore from the local archive
 
 ```bash
-mv "$HOME/repo-archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups" \
+mv "$HOME/hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pcb b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pcb
deleted file mode 120000
index d6611b5..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pcb	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pcb
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_prl b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_prl
deleted file mode 120000
index 6738e55..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_prl	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_prl
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pro b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pro
deleted file mode 120000
index 516e367..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pro	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard.kicad_pro
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/fp-info-cache b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/fp-info-cache
deleted file mode 120000
index 6766c17..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/fp-info-cache	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/fp-info-cache
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step
deleted file mode 120000
index 8093f09..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.link b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.link
deleted file mode 120000
index 86fefb6..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Zerowriter Keyboard 3D.step
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md
index 2199e67..49b6c96 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step` |
 | Type | file |
 | Size | 4,502,629 B (4.29 MiB) |
 | SHA-256 | `a6a11311707ed4ee1d1e17308d2e8877d8e7d84ec0abbc21321a457757ed5758` |
@@ -22,33 +22,6 @@
 | License | GPL-3.0 |
 | Path within upstream repo | `design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../../Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -66,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/zerowriter/zerowriter_ink>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step" \
+mv "../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md
index 88bfed3..cf92302 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL` |
 | Type | directory |
 | Size | 8,514,350 B (8.12 MiB) |
 | File count | 5 |
@@ -32,33 +32,6 @@
 | `Zerowriter breakout board.kicad_pro` | 7,988 | `365a0314e79e870a786d75236f35cd5ab0cd6f1504947a937b9514fa67ea68f9` |
 | `fp-info-cache` | 2 | `9a271f2a916b0b6ee6cecb2426f0b3206ef074578be55d9bc94f6f3fe3ab86aa` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -74,11 +47,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/zerowriter/zerowriter_ink>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL" \
+mv "../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md
index ab28dc7..1c8c27e 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md	
@@ -31,7 +31,7 @@ and 3D-printable outputs all remain in place.
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups` |
-| Archived to | `scratch/zerowriter-provenance-2026-08-30/upstream/zerowriter_ink-996207aca0677300ed5f1fdf762d9c9ec79f516e/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups` |
+| Archived to | `../hardware-doc-archive/scratch/zerowriter-provenance-2026-08-30/upstream/zerowriter_ink-996207aca0677300ed5f1fdf762d9c9ec79f516e/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups` |
 | Type | directory of ZIP archives |
 | Size | **6159721 B** |
 | File count | **3** ZIP files |
@@ -59,39 +59,12 @@ uncompressed in the parent directory. Inspect on demand with `unzip -l` / `unzip
 
 
 > ⚠ **Path corrected 2026-08-30.** This placeholder originally pointed at
-> `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups`.
+> `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups`.
 > A later archiving pass moved the whole parent `PANEL/` directory onto that same archive path, which
 > replaced it. **The content was not lost** — it survives in full inside the upstream tarball
 > extraction under `scratch/zerowriter-provenance-2026-08-30/`, and the path above now points there.
 > Verified present ✅.
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../../../Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../../../Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 All statuses verified **2026-08-24**.
@@ -130,7 +103,7 @@ differently under a UTF-8 locale.
 ## Restore from the local archive
 
 ```bash
-mv "$HOME/repo-archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups" \
+mv "$HOME/hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pcb b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pcb
deleted file mode 120000
index 29644ae..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pcb	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pcb
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_prl b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_prl
deleted file mode 120000
index 21aebc3..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_prl	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_prl
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pro b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pro
deleted file mode 120000
index 697d2bd..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pro	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board.kicad_pro
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/fp-info-cache b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/fp-info-cache
deleted file mode 120000
index 39a6a76..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/fp-info-cache	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/fp-info-cache
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step
deleted file mode 120000
index 65b2e93..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.link b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.link
deleted file mode 120000
index 250f402..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Zerowriter breakout board 3D.step
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md
index 2c9a98d..4640d80 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md	
@@ -10,7 +10,7 @@
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step` |
 | Type | file |
 | Size | 5,785,156 B (5.52 MiB) |
 | SHA-256 | `b0b4d4bf157a42395efd0e0f383609e5ee2743cd7fc63196ce8360ed4885c94c` |
@@ -22,33 +22,6 @@
 | License | GPL-3.0 |
 | Path within upstream repo | `design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step` |
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../../Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../../Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../../zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md)
-
 ## How to get it back
 
 Independent recovery URLs, most reliable first:
@@ -66,11 +39,17 @@ Independent recovery URLs, most reliable first:
 - additional mirror:  
   <https://github.com/zerowriter/zerowriter_ink>
 
+> **Resolving `../hardware-doc-archive`** — it is a sibling of the **real repository root**,
+> not of your working directory. Under a git worktree, resolve it with the *common* dir:
+>
+> ```bash
+> ARCHIVE="$(dirname "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")/hardware-doc-archive"
+> ```
 
 Restore from the local archive:
 
 ```bash
-mv "archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step" \
+mv "../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups
deleted file mode 120000
index 21a59e0..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups	
+++ /dev/null
@@ -1 +0,0 @@
-../../../../../../../../../../archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.link b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.link
deleted file mode 120000
index e284329..0000000
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.link	
+++ /dev/null
@@ -1 +0,0 @@
-Zerowriter Keyboard-backups
\ No newline at end of file
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md
index fb735f6..b9d1462 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md	
+++ b/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups.ARCHIVED.md	
@@ -31,7 +31,7 @@ and 3D-printable outputs all remain in place.
 | Field | Value |
 |---|---|
 | Original repo path | `devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups` |
 | Type | directory of ZIP archives |
 | Size | **1327732 B** |
 | File count | **2** ZIP files |
@@ -56,33 +56,6 @@ and 3D-printable outputs all remain in place.
 Post-extraction sizes are not recorded: each ZIP is a snapshot of files that already exist
 uncompressed in the parent directory. Inspect on demand with `unzip -l` / `unzip -d`.
 
-## Derived from a common base
-
-This material is **not standalone**. It is part of a snapshot of [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) taken at a single pinned commit; re-acquiring it means fetching that commit, not hunting the file individually.
-
-| Field | Value |
-| --- | --- |
-| Base repository | [`zerowriter/zerowriter_ink`](https://github.com/zerowriter/zerowriter_ink) |
-| Base commit | [`996207aca0677300ed5f1fdf762d9c9ec79f516e`](https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e) |
-| Tree at that commit | <https://github.com/zerowriter/zerowriter_ink/tree/996207aca0677300ed5f1fdf762d9c9ec79f516e> |
-
-```bash
-git clone https://github.com/zerowriter/zerowriter_ink
-git -C zerowriter_ink checkout 996207aca0677300ed5f1fdf762d9c9ec79f516e
-```
-
-**10 archive records in this repository share this exact base.** Re-obtaining the commit once satisfies all of them, and any correction to the base details above belongs in every one:
-
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md`](../../../src/Zerowriter Inkplate 5 Gen2/v1.2.0/CAD/PANEL/Zerowriter Inkplate 5 Gen2-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md`](../../../src/Zerowriter Inkplate 5 Gen2/v1.2.0/OUTPUTS/Soldered Inkplate 5 Gen2 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../src/Zerowriter Keyboard/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md`](../../../src/Zerowriter Keyboard/v1.2.0/CAD/PANEL/Zerowriter Keyboard-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md`](../../../src/Zerowriter Keyboard/v1.2.0/OUTPUTS/Zerowriter Keyboard 3D.step.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md`](../../../src/Zerowriter breakout board/v1.2.0/CAD/PANEL.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md`](../../../src/Zerowriter breakout board/v1.2.0/CAD/PANEL/Zerowriter breakout board-backups.ARCHIVED.md)
-- [`devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md`](../../../src/Zerowriter breakout board/v1.2.0/OUTPUTS/Zerowriter breakout board 3D.step.ARCHIVED.md)
-
 ## How to get it back
 
 All statuses verified **2026-08-24**.
@@ -121,7 +94,7 @@ differently under a UTF-8 locale.
 ## Restore from the local archive
 
 ```bash
-mv "$HOME/repo-archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups" \
+mv "$HOME/hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups" \
    "devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter_ink/design/zw_keyboard/Kicad/CAD/Zerowriter Keyboard-backups"
 ```
 
diff --git a/devices/zerowriter/zerowriter-ink/artifacts/vendored-deps/README.md b/devices/zerowriter/zerowriter-ink/artifacts/vendored-deps/README.md
index 6da8861..bc81f22 100644
--- a/devices/zerowriter/zerowriter-ink/artifacts/vendored-deps/README.md
+++ b/devices/zerowriter/zerowriter-ink/artifacts/vendored-deps/README.md
@@ -15,7 +15,7 @@ and analysed in [`../../zerowriter1-epaper-driver-notes.md`](../../zerowriter1-e
 | Field | Value |
 |---|---|
 | Removed path | `artifacts/source-snapshots/zerowriter1/e-Paper/` |
-| Archived to | `archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper/` |
+| Archived to | `../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper/` |
 | What it is | Waveshare's official Python driver library + demo images for their whole e-paper module range, as vendored into the **ZeroWriter 1** (Raspberry Pi) project |
 | Why it was here | ZeroWriter 1 is the Raspberry-Pi-based predecessor of ZeroWriter Ink. Its repository vendors this library wholesale; the snapshot was taken as-is. |
 | Removed tree size | **32,575,902 B (31.07 MiB)** across **272 files** in 16 directories |
@@ -163,7 +163,7 @@ find e-Paper -type f -printf '%s\n' | awk '{s+=$1}END{print s}'   # expect 32575
 ### Restore from the local archive
 
 ```bash
-mv archive/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper \
+mv ../hardware-doc-archive/doc/hardware/devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper \
    devices/zerowriter/zerowriter-ink/artifacts/source-snapshots/zerowriter1/e-Paper
 ```
 
diff --git a/guides/README.md b/guides/README.md
index cfc0672..6afb7c5 100644
--- a/guides/README.md
+++ b/guides/README.md
@@ -6,11 +6,7 @@ Cross-cutting notes that do not belong to a single chip or board. Per-part recor
 |---|---|
 | [Espressif](espressif/README.md) | **Ecosystem and product lines** (the family map: which chip, which radio, which ISA) · **SoC peripheral reference** (the numeric ESP32 / S3 / P4 tables, extracted from the TRMs) · **Practical errata** · **Memory and boot** · ESP-IDF cross-target peripheral capabilities · ESP-ADF audio pipelines and memory budget · ESP-IoT-Solution display/touch/knob/USB components |
 | [**Hardware subsystems**](hardware/README.md) | **E-paper displays** (waveforms, bias rails, VCOM, ghosting, temperature, the NDA boundary) · **Display interfaces** (SPI / QSPI / parallel / MIPI-DSI / e-paper, bandwidth and framebuffer arithmetic, TE lines, LVGL, every documented controller) |
-| [**Serial device access**](serial-access/README.md) | Getting a board to appear as a usable serial port: bridge chips vs native USB-CDC, `dialout` vs **`uucp` on Arch**, udev rules, and the two processes that silently steal the port — **`brltty`** (CH340) and **ModemManager** (intermittent flash failures). Plus macOS `cu.*` vs `tty.*` and Windows COM |
-| [**NFC**](nfc/README.md) | Device-independent NFC: the 14443-A/B / FeliCa / 15693 standards landscape and which tags are which, **antenna matching and the Q trade-off** (where the real difficulty is), reader silicon comparison, RFAL and the library options, and symptom-to-cause debugging |
-| [**LoRa**](lora/README.md) | Device-independent LoRa: **LoRa vs LoRaWAN vs Meshtastic**, the SF/airtime/duty-cycle trade, **regional band plans as a legal constraint**, SX1261 vs SX1262, `BUSY`/TCXO/DIO and the LDO-vs-DC-DC current cost, RadioLib, and honest range estimation |
 | [Reverse engineering](reverse-engineering/netlists-from-vendor-eda-files.md) | **Recovering netlists from vendor EDA files** — KiCad PCB/schematic and EAGLE XML, and what a recovered netlist reliably reveals |
-| [**Research technique**](research/finding-projects-that-use-a-board.md) | **Finding projects that use a board** (search by dependency, not product name) · **Finding certification records** (FCC grantee-code enumeration, which regulatory databases are actually reachable, and the positive/negative controls that make an absence finding mean anything) |
 | [Markets and sourcing](markets/README.md) | **Device comparison matrix** (every documented device, side by side) · **Vendor and marketplace comparison** (where to buy, and whether the documentation will still exist later) · **Clones, siblings and variants** (identifying and working with copies) |
 | [NixOS as a development host](nixos/README.md) | Running embedded toolchains — ESP-IDF, Arduino, PlatformIO, mesh/LoRa/SDR tooling, proprietary UI editors — on NixOS, where "download the installer and run it" does not apply |
 
@@ -36,20 +32,6 @@ Cross-cutting notes that do not belong to a single chip or board. Per-part recor
 |---|---|
 | [E-paper displays](hardware/e-paper-displays.md) | How e-paper works and how to drive it: waveforms and LUTs, why a multi-rail PMIC and a hardware sequencer are unavoidable, **VCOM and why it is per-panel**, update-mode trade-offs with real timings, temperature dependence, burn-in, and **exactly what the E Ink NDA does and does not put out of reach** |
 | [Display interfaces](hardware/display-interfaces.md) | Every display transport in the library compared — **who owns the frame**, bandwidth arithmetic, the ESP32 family's LCD peripherals per chip, **framebuffer/PSRAM sizing**, TE lines and tearing, LVGL buffer patterns, init tables, and a table of **every documented display controller** |
-| [Parallel Intel-8080 LCD buses on ESP32](hardware/parallel-8080-lcd-buses.md) | Why the display-library choice matters more than the board — 8080 vs RGB vs QSPI, the `TFT_eSPI`/`Arduino_GFX`/`LovyanGFX` decision, the `User_Setup_Select.h` trap, GRAM offsets, and a black-screen debugging checklist |
-| [LoRa radio generations](hardware/lora-radio-generations.md) | The four generations of Semtech LoRa transceiver silicon, where the numbering comes from, a like-for-like matrix across SX127x / SX126x / SX128x / LR11xx / LR20xx, and **what breaks when you migrate** |
-
-### NFC — [`nfc/`](nfc/README.md)
-
-| Page | One line |
-|---|---|
-| [**NFC — a device-independent guide**](nfc/README.md) | The four physical layers (14443-A/B, FeliCa, 15693) and which real tags are which · NFC Forum types 1–5 and why **MIFARE Classic is none of them** · reader / card-emulation / P2P and which are realistic · **antenna matching, the Q-versus-bandwidth trade and why range is capped by coil size** · the operation-byte pattern, banked registers, IRQ and FIFO · **RFAL's structure and what porting it actually means** · a maintenance-checked library table · symptom-to-cause debugging |
-
-### LoRa — [`lora/`](lora/README.md)
-
-| Page | One line |
-|---|---|
-| [**LoRa — a device-independent guide**](lora/README.md) | **SF/BW/CR against airtime, battery and legality**, with the arithmetic shown — one SF step buys 2.5 dB and costs 2× airtime · **LoRa vs LoRaWAN vs Meshtastic** · a sourced **regional band table**, and why EU duty cycle and US dwell time forbid opposite things · **SX1261 vs SX1262 vs SX1268** precisely · `BUSY`, TCXO on `DIO3`, RF switch on `DIO2`, **LDO vs DC-DC and why receive current dominates** · RadioLib, and the finding that it implements **all four** of Semtech's mandatory errata workarounds · **honest range estimation**, and why 2 450 km is the wrong answer |
 
 ### Markets and sourcing — [`markets/`](markets/README.md)
 
@@ -64,21 +46,18 @@ Cross-cutting notes that do not belong to a single chip or board. Per-part recor
 | Page | One line |
 |---|---|
 | [Recovering netlists from vendor EDA files](reverse-engineering/netlists-from-vendor-eda-files.md) | Parse the `.kicad_pcb`, not the `.kicad_sch` — how to extract authoritative connectivity from KiCad and EAGLE sources, and what it reliably reveals |
-| [Tracing nets from schematic PDFs](reverse-engineering/tracing-nets-from-schematic-pdfs.md) | **When the vendor published a PDF and nothing else.** Altium exports embed invisible `CO` / `PI` / `NL` marker tokens at item coordinates, which is what makes a net list recoverable from the text layer with poppler alone; the geometric fallback for non-Altium exports; and ⚠ **the outlined-text trap** — KiCad and EAGLE routinely convert schematic text to vector paths, yielding zero extractable words and a permanently untraceable file. Companion to [`netlists-from-vendor-eda-files.md`](reverse-engineering/netlists-from-vendor-eda-files.md), which is preferred whenever EDA sources exist. *Added 2026-09-11* |
 
 ### Research technique — [`research/`](research/finding-projects-that-use-a-board.md)
 
 | Page | One line |
 |---|---|
 | [Finding projects that use a board or component](research/finding-projects-that-use-a-board.md) | Search by **dependency**, not product name; authenticated GitHub code search — the technique that took one board's known projects from two to a dozen |
-| [**Finding certification records**](research/finding-certification-records.md) | FCC OET equipment-authorisation lookup and **the grantee-code enumeration trick** — enumerate the vendor's grantee code, not the product name, and you get every device it has certified, **including ones it never announced**. Which regulatory databases are reachable without a login (measured, with the failures named); the **inverted Cloudflare block on `fccid.io`**, which serves 403 to a Chrome UA and 200 to `curl`; exhibit download templates; a worked **positive/negative control pair**; and why CE and UKCA have no database to search at all. *Added 2026-09-11* |
 
 ### Host platform — [`nixos/`](nixos/README.md)
 
 | Page | One line |
 |---|---|
 | [NixOS as an embedded development host](nixos/README.md) | ESP-IDF, Arduino, PlatformIO and proprietary UI editors on NixOS — including why installing the `esp-idf-full` *package* alone yields no `idf.py`, package availability in the locked nixpkgs with dated absences, and why LVGL and sensor libraries are project dependencies rather than system packages |
-| [RISC-V and vendor-SDK toolchains](nixos/riscv-and-vendor-sdk-toolchains.md) | Why `pkgsCross.riscv64-*` does not substitute for XuanTie GCC (`-mcpu=c908v` is XuanTie-specific and unknown to mainline GCC; the shipped userspace targets **draft RVV 0.10** on silicon that implements ratified RVV 1.0), three ways around a hard-coded `/opt/toolchain`, and the nRF Connect SDK case. Companion to [`nixos/README.md`](nixos/README.md), which is unmodified. *Added 2026-09-04* |
 
 ---
 
diff --git a/guides/hardware/README.md b/guides/hardware/README.md
index 4666fa3..701a6f9 100644
--- a/guides/hardware/README.md
+++ b/guides/hardware/README.md
@@ -8,10 +8,6 @@ and [device](../../devices/README.md) records into a single treatment of the sub
 |---|---|
 | [**E-paper displays**](e-paper-displays.md) | How electrophoretic displays work — waveforms, LUTs, greyscale, ghosting and why periodic full refreshes are forced. Why a bare panel needs a multi-rail PMIC and a hardware power sequencer. **VCOM and why it is per-panel-lot.** Partial vs full vs greyscale trade-offs with real timings. Temperature dependence, and the gap between the sensor that exists and the sensor that is used. Burn-in and lifetime. **The NDA problem: exactly what is and is not publicly establishable about an E Ink panel.** Practical guidance for driving one |
 | [**Display interfaces**](display-interfaces.md) | SPI vs QSPI vs i80/RGB parallel vs MIPI-DSI vs e-paper parallel — when each is used, who owns the frame, and bandwidth arithmetic from real figures. The ESP32 family's LCD peripheral support per chip. **Framebuffer and PSRAM sizing with worked cases.** Tearing, TE lines and what happens when TE is not routed. LVGL integration and buffer sizing. **A table of every display controller in the library**, with and without a component record |
-| [**Parallel Intel-8080 LCD buses on ESP32**](parallel-8080-lcd-buses.md) | Why the display-library choice matters more than the board: 8080 vs RGB vs QSPI, the `TFT_eSPI`/`Arduino_GFX`/`LovyanGFX` decision, the `User_Setup_Select.h` trap, GRAM offsets, and a black-screen debugging checklist. Companion to [`display-interfaces.md`](display-interfaces.md). *Added 2026-09-07* |
-| [**LoRa radio generations**](lora-radio-generations.md) | **The four generations of Semtech LoRa transceiver silicon.** What "the 4th generation LoRa chip" is and where the numbering comes from (Semtech's own `DS.LR20xx` §23.8); a like-for-like feature/electrical/host-interface matrix across SX127x, SX126x, SX128x, LR11xx and LR20xx; and **what breaks when you migrate**, at the level of "here is what your driver has to change". *Added 2026-09-04* |
-| [**Adding LoRa, NFC and an RGB sidelight to e-ink firmware**](adding-lora-nfc-and-sidelight-to-eink-firmware.md) | What it actually takes to bolt a radio, an NFC front-end or an addressable light onto an existing e-ink reader firmware. Per capability: free-pin and interrupt prerequisites, what an e-paper refresh does to the power rail, the driver options (RadioLib, Semtech `sx126x_driver`/`lr20xx_driver`, Meshtastic, ST25R3916, PN532/RC522, RMT/`led_strip`) with licence and footprint, and flash/RAM cost. **Ends with a plugin-versus-fork verdict per capability** for CrossPoint Reader, FreeInk and CrossPlay, cited to the plugin ABI's exported-symbol list. **Nothing here was built or flashed.** *Added 2026-09-07* |
-| [**SoC choice for battery e-ink devices**](soc-choice-for-battery-eink-devices.md) | Why these boards pick what they pick — ESP32-C3 vs ESP32-S3 vs ESP32-P4 vs Kendryte K230 vs nRF52/nRF9151 for a battery-powered e-ink handheld. PSRAM against framebuffer size, deep-sleep current, radio duty cycle, toolchain maturity and the price consequence. Every figure is cited to the component record it came from; missing figures are named as missing rather than estimated. *Added 2026-09-07* |
 
 ---
 
@@ -34,32 +30,3 @@ board.
 - [Guides index](../README.md) · [Espressif guides](../espressif/README.md) · [Markets and sourcing](../markets/README.md)
 - [Device comparison matrix](../markets/device-comparison-matrix.md) — the display, power and input columns across every documented device
 - [Component index](../../components/README.md) · [Device index](../../devices/README.md)
-
----
-
-## Recovering the facts these guides rely on — *added 2026-09-11*
-
-Every guide here cites pinouts, bus widths and controller choices that came out of a **schematic**.
-Two companion guides cover how those schematics get read when the vendor publishes no netlist:
-
-- [**Recovering netlists from vendor EDA files**](../reverse-engineering/netlists-from-vendor-eda-files.md)
-  — the preferred route whenever KiCad or EAGLE sources exist. Parse the `.kicad_pcb`, not the
-  `.kicad_sch`.
-- [**Tracing nets from schematic PDFs**](../reverse-engineering/tracing-nets-from-schematic-pdfs.md)
-  — **when a PDF is all there is.** Altium exports embed invisible `CO` / `PI` / `NL` marker
-  tokens at item coordinates, which makes a net list recoverable from the text layer alone.
-  ⚠ **KiCad and EAGLE exports frequently outline their text to vector paths**, yielding zero
-  extractable words and a permanently untraceable file — check before concluding a design is
-  undocumented, because a usable second export often sits in the same directory.
-
-The display and e-paper claims in these guides are exactly the kind that method settles: the
-[**parallel Intel-8080**](parallel-8080-lcd-buses.md) bus widths and the panel-controller
-identifications in [**display interfaces**](display-interfaces.md) are schematic facts, and five
-device records now carry a `schematic-netlist.md` derived this way — see
-[`devices/README.md`](../../devices/README.md#two-new-per-record-file-types--added-2026-09-11).
-
-A third guide covers the *other* non-vendor evidence route these pages increasingly depend on:
-[**finding certification records**](../research/finding-certification-records.md). FCC internal
-photographs establish antenna type, battery capacity and package-level construction for boards
-whose vendors publish nothing — which is where the
-[KH3216-A35 antenna record](../../components/generic/kh3216-a35-chip-antenna/README.md) came from.
diff --git a/guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md b/guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md
deleted file mode 100644
index a18704b..0000000
--- a/guides/hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md
+++ /dev/null
@@ -1,660 +0,0 @@
-# Adding LoRa, NFC and an RGB sidelight to an existing e-ink reader firmware
-
-> **Nothing in this pass was built, compiled, flashed or measured.** No hardware
-> was in hand. Every claim below is read out of a record already in this
-> repository, and carries that record's evidence label. Where a number would be a
-> guess, it says so instead of guessing.
->
-> Snapshot **2026-09-07**. Device-independent companions:
-> [`guides/lora`](../lora/README.md) · [`guides/nfc`](../nfc/README.md) ·
-> [`guides/hardware/e-paper-displays.md`](e-paper-displays.md).
-
-## Evidence labels used throughout
-
-| Label | Meaning here |
-|---|---|
-| `executed-success` | Someone in this repository read the cited file/API and recorded the result. **Not** "it ran on hardware" |
-| `reported-working` | A third party states it works; not reproduced here |
-| `inferred` | Derived from wiring, source or arithmetic; not observed |
-| `not-tested` | Nobody has tried it, or nobody has published trying it |
-
----
-
-## 0. The short answer
-
-| Capability | Is there working hardware evidence? | Plugin, or fork? |
-|---|---|---|
-| **LoRa** | Hardware exists and is fully wired on the PaperMono; the vendor's own factory firmware initialises it. **No third party has ever driven LoRa on that board** | **Firmware change required.** Not reachable from either plugin system |
-| **NFC read/write** | **Demonstrated on real hardware by a third party** ([`ciniml/paper_name_plate`](https://github.com/ciniml/paper_name_plate), Rust, 2026-09-06) | **Firmware change required**, but a *small, structured* one |
-| **RGB sidelight / frontlight** | Both exist on the PaperMono and are driven by stock firmware. On the Xteink X4 Pro a dual warm/cool frontlight exists. **Neither is an addressable LED string** | **Firmware change required.** Frontlight is not even on a host GPIO |
-
-Every one of the three needs a firmware change. **None of them can be a plugin
-under either CrossPoint plugin system**, and §4 shows exactly why — the boundary
-is a link-time symbol allow-list that contains no bus, no pin and no filesystem
-access. The good news buried in that: the gap between "plugin" and "fork of the
-reader" is much narrower than it sounds.
-
----
-
-## 1. The three things this is grounded in
-
-### 1.1 The M5Stack PaperMono ships LoRa **and** NFC in its stock firmware
-
-This is the load-bearing fact, and it is why the question is answerable at all
-rather than speculative. The
-[PaperMono](../../devices/m5stack/papermono/README.md) (SKU C153, USD 65) fits an
-ST25R3916 NFC front end and a `Stamp-LoRa-1262-mini` (Semtech SX1262) module, and
-M5Stack's `M5PaperMono-UserDemo` drives both. The
-[PaperMono-Lite](../../devices/m5stack/papermono-lite/README.md) at USD 55 is the
-same board with both radios depopulated — **the USD 10 delta is exactly NFC + LoRa
-and nothing else.**
-
-What the stock firmware actually does, read from vendor source at cited
-`file:line` (`executed-success` on the read, `not-tested` on hardware):
-
-| | LoRa | NFC |
-|---|---|---|
-| Driver | **RadioLib**, pinned **7.2.1** commit `b91c6af1…`, and **patched** to remove `idf_component.yml` | **`M5Unit-NFC` 0.1.0** commit `93745b54…` + **`M5UnitUnified` 0.5.5**, both **patched** |
-| Host glue | `hal_lora.cpp` — a thin `RadioLibHal` over ESP-IDF SPI/GPIO, handing RadioLib six pin numbers | `M5UnitUnified` hub; the app adds `NFCLayerA/B/F/V` objects |
-| Bus | **`SPI3_HOST`**, 8 MHz, GPIO38 MOSI / 39 SCK / 40 MISO / 41 NSS | **Shared system I²C**, GPIO47/48 @ 400 kHz, address `0x50` |
-| Handshake | `BUSY` GPIO21, `DIO1` GPIO5 (`GPIO_INTR_POSEDGE`) | `IRQ` GPIO6 — **and the vendor app sets `using_irq = false` and polls** |
-| Reset | **not on an ESP32 GPIO** — M5IOE1 `IO10`. RadioLib is passed `RADIOLIB_NC` | ST25R3916 **has no reset pin**; `PYB_RFID_RST` is a load-switch enable |
-| Power enable | **M5PM1 `G2`** → `3V3_L2_LoRa` rail (SSP7615-33DFR LDO, 400 mA) | **M5IOE1 `IO4`** → NFC sub-board |
-| Vendor radio config | 868.0 MHz · BW 62.5 kHz · **SF12** · CR 4/8 · sync `0x34` · **22 dBm** · TCXO **3.0 V** · **LDO regulation** · current limit 140 mA | mode A/B/F/V cycled; identity probe reads register `0x7F`, expects `0x05` |
-
-Two of those rows are the whole shape of the problem:
-
-- **The reset and the power rail are both behind I²C.** No I²C, no LoRa reset. No
-  I²C, no LoRa power. No I²C, no NFC at all.
-- **The vendor picked LDO regulation**, which on an SX1262 roughly doubles receive
-  current — 4.6 mA → 8.8 mA for LoRa at 125 kHz — presumably because the module
-  omits the DC-DC inductors.
-  ([SX1262 record §5.4](../../components/semtech/sx1262/README.md).)
-
-The bring-up **order** is not optional and is not stated in any vendor document;
-it follows from the wiring and is what `hal_lora.cpp:299–319` does:
-
-1. M5PM1 `G2` high — power the module.
-2. M5IOE1 `IO2` (antenna switch) → output, push-pull, HIGH.
-3. M5IOE1 `IO10` (`SX_NRST`) → LOW → 100 ms → HIGH → 20 ms.
-4. *Then* open SPI and call RadioLib.
-
-Skip step 1 or 3 and the radio looks absent.
-
-**NFC is now demonstrated by a third party, LoRa is not.**
-[`ciniml/paper_name_plate`](https://github.com/ciniml/paper_name_plate) is
-bare-metal `no_std` Rust for this board carrying its own ST25R3916 driver
-(`src/st25r3916.rs`, 28,899 B of source), NFC Forum Type 2 Tag emulation
-(`src/t2t_emu.rs`, 19,784 B), ISO-DEP and NDEF — plus its own `pm1.rs` and
-`ioe1.rs`, because it concluded independently that the FreeInk SDK abstraction is
-optional. It lists the SX1262 pins and **explicitly scopes LoRa out**. `⚠ It has
-no LICENSE file — all rights reserved. Read it for technique; do not copy.`
-Details: [new PaperMono projects, 2026-09](../../software/ecosystems/crosspoint-freeink/new-papermono-projects-2026-09.md).
-
-### 1.2 The M5Stack Caps are the reference implementation, with published pinouts
-
-Two [Cardputer](../../devices/m5stack/cardputer-adv/README.md) expansion boards do
-the same jobs as *attachable* modules with schematics in this repository. If you
-are designing a new board or reasoning about a port, read these before the
-PaperMono, because their wiring is simpler and published.
-
-**[Cap LoRa-1262 (U214), USD 14.50](../../devices/m5stack/cap-lora-1262/README.md)** —
-SX1262 in a `Stamp LoRa-1262 Mini` plus an ATGM336H GNSS. Host pin map, verbatim
-from the vendor (identical on the `[EOL]` [U201](../../devices/m5stack/cap-lora868/README.md)):
-
-| Cap signal | Cardputer-Adv GPIO |
-|---|---|
-| `LoRa_NSS` | **G5** |
-| `LoRa_RST` | **G3** |
-| `LoRa_IRQ` (DIO1) | **G4** |
-| `LoRa_BUSY` | **G6** |
-| `LoRa_SCK` / `MOSI` / `MISO` | **G40 / G14 / G39** — *shared with the microSD card* |
-| `GPS_TX` → host RX / `GPS_RX` ← host TX | **G15 / G13** |
-| `SCL` / `SDA` | **G9 / G8** — the host's *internal* bus |
-
-Plus a `PI4IOE5V6408` I/O expander at **`0x43`** whose **P0 drives the RF antenna
-switch**. M5Stack states plainly that initialising the radio requires *"set P0 of
-the PI4IOE I/O expander to HIGH"*. Omit it and the SX1262 transmits into a
-disconnected antenna.
-
-**[Cap CC1101 & NFC (U219), USD 18.95](../../devices/m5stack/cap-cc1101/README.md)** —
-a TI CC1101 multi-band sub-GHz transceiver **and** an ST25R3916 NFC front end
-**on a shared SPI bus**, behind a host-gated rail, with three antennas in the box.
-That is the closest published analogue of "add both radios to an existing device"
-that exists anywhere in this repository, and its
-[`features/nfc.md` §10](../../devices/m5stack/cap-cc1101/features/nfc.md) and
-[`features/sub-ghz.md` §9](../../devices/m5stack/cap-cc1101/features/sub-ghz.md)
-are written as portability checklists.
-
-Two ideas from it are worth stealing:
-
-- **Band switching that costs one host GPIO instead of two.** Two SP3T switches
-  select one of three matched LC paths to a single antenna port. `RF_SW0` is a host
-  GPIO (`G13` on Cardputer-Adv, `G14` on CardputerZero); **`RF_SW1` is the
-  CC1101's own `GDO2` pin, set over SPI.** Cost: you cannot select a band before
-  the transceiver is talking.
-- **The same ST25R3916 appears on both boards with a different host interface** —
-  **SPI** on the Cap, **I²C** on the PaperMono. The part is strapped by `I2C_EN`.
-  A driver written against one is not a driver against the other at the bus layer,
-  though everything above `rfal_rf.h`
-  ([`guides/nfc` §6.1](../nfc/README.md#61-rfals-structure-and-the-one-thing-to-know-before-porting-it))
-  is portable by construction.
-
-⚠ **The CC1101 cannot do LoRa.** The frequencies overlap so people keep asking.
-LoRa is chirp spread spectrum, the patents are Semtech's, TI does not make LoRa
-silicon. If you want LoRa on a Cardputer that is the Cap LoRa-1262, and there is
-**one Cap slot**.
-
-### 1.3 ⚠ The Xteink X3 carries a passive NFC **tag**, which is not an NFC reader
-
-**Read this before you plan anything around "the X3 has NFC".** It is the
-confusion that wastes weeks, and it has already produced one wrong product
-identification in this repository's own community sources.
-
-| | **NFC reader/writer** (PaperMono, Cap CC1101) | **Passive NFC tag** (Xteink X3) |
-|---|---|---|
-| What it is | An active front end — ST25R3916 | An **ISO/IEC 14443A tag**, part number unknown |
-| Who energises the field | **The device** | **Someone else's phone** |
-| Host bus | I²C `0x50` or SPI | **None. It is on no host bus at all** |
-| Firmware can use it | Yes — read, write, emulate | **No. It is invisible to firmware** |
-| Appears in a board profile | Yes | **No** — no board profile, no firmware string, no driver, anywhere in the FreeInk SDK |
-| Power cost | rail + polling | **Zero. It is not powered** |
-| What you can build | tag reading, card emulation, access control | **Nothing in firmware** |
-
-The X3's tag is fitted (two independent sources: the Chinese BOM lists
-`***ISO/IEC 14443a NFC Tag`, and Xteink advertised "NFC support" at launch) and
-**its function is entirely unknown** — see
-[`x3/features/nfc.md`](../../devices/xteink/x3/features/nfc.md), which records four
-candidate explanations and endorses none. Resolving it costs five minutes and an
-Android phone, and nobody has done it.
-
-**Adding NFC *reading* to an X3 is not a firmware task at all — it is a hardware
-modification**, because there is no reader on the board and no free SPI/I²C
-front end to attach one to without a redesign. Any plan that starts "the X3
-already has NFC" is starting from a false premise.
-
-A third confusion worth killing at the same time: the
-[Xteink Nano / "Tong Card"](../../devices/xteink/nano/README.md) is a **separate
-product** — a battery-less, NFC-powered four-colour e-paper card that a phone
-writes an image to. It is not the X3's tag and it is not a reader either.
-
----
-
-## 2. What the e-ink refresh does to the power rail
-
-This is the question that gets skipped and then bites during the first field test.
-**No measurement of it exists anywhere in this repository**, so what follows is
-sourced parts arithmetic, labelled `inferred`, and should be treated as a reason
-to instrument rather than as a budget.
-
-Sourced current figures, each cited to its record:
-
-| Load | Figure | Source |
-|---|---|---|
-| E-paper refresh, 3.97″ 800×480 | **< 40 mW** claimed; panel manual **36 mW typical @ 3.0 V**, **120 mA peak**, 0.003 mW deep sleep | [Waveshare 3.97 record](../../devices/waveshare/esp32-s3-epaper-3.97/README.md) |
-| SX1262 TX @ **+22 dBm**, 868/915 MHz | **118 mA** | [SX1262 §5](../../components/semtech/sx1262/README.md) |
-| SX1262 TX @ +14 dBm, PA re-matched | **45 mA** — but that needs a *different matching network*, not a software change | idem |
-| SX1262 RX, LoRa 125 kHz, **LDO** (what the PaperMono selects) | **8.8 mA** | idem |
-| SX1262 RX, LoRa 125 kHz, DC-DC | 4.6 mA | idem |
-| SX1262 sleep, config retained | **600 nA** | idem |
-| PaperMono LoRa rail | SSP7615-33DFR LDO, **400 mA** rating; firmware sets a **140 mA** software current limit | [PaperMono `features/lora.md` §3](../../devices/m5stack/papermono/features/lora.md) |
-| Cap LoRa868 board, GPS sleep / LoRa TX max | **129.72 mA @ 5 V** | [Cap LoRa868 §3](../../devices/m5stack/cap-lora868/README.md) |
-| PaperMono frontlight LED current | **~11 mA** `inferred` from the fitted `R29 = 18 Ω`; the schematic's own annotation claiming 15 mA is **stale** | [PaperMono `features/frontlight.md` §5.3](../../devices/m5stack/papermono/features/frontlight.md) |
-| PaperMono battery | 1150 mAh | device record |
-
-**What actually matters** (`inferred` throughout):
-
-1. **A panel refresh and a LoRa transmission are each ~120 mA-class events on a
-   1150 mAh cell.** On the PaperMono they are on *different rails* — the panel on
-   `3V3_L2` behind M5IOE1 `IO3`, the radio on `3V3_L2_LoRa` behind M5PM1 `G2` —
-   so the LDOs are not fighting, but the **cell and its ESR are shared**. The
-   obvious failure mode is a brown-out when a transmit lands inside a refresh
-   window. Nobody has tested this.
-2. **Do not transmit during a refresh, as a firmware rule.** An e-paper refresh is
-   a fixed-duration waveform the panel must complete; a mid-refresh supply
-   disturbance is the classic cause of ghosting and incomplete development. The
-   cheap mitigation is to serialise them — the panel is already blocking on `BUSY`,
-   so there is a natural place to gate the radio.
-3. **The frontlight is the one continuous load.** ~11 mA held for a whole reading
-   session dwarfs a duty-cycled radio. It is also the one nobody has measured:
-   *"No power figure exists. Nobody has published frontlight current draw or its
-   effect on battery life."*
-4. **Receive, not transmit, is what kills a mesh node's battery**, and the
-   PaperMono's LDO choice doubles it. See
-   [`guides/lora` §1.5](../lora/README.md#15-the-battery-consequence-which-is-not-the-one-people-expect).
-5. **On the Xteink devices none of this can be computed at all** — only the X3 has
-   a published battery capacity (650 mAh), and none of them has a radio beyond the
-   SoC's own.
-
----
-
-## 3. Capability by capability
-
-### 3.1 LoRa
-
-#### Hardware prerequisites
-
-| Requirement | Why | On the PaperMono | On an Xteink |
-|---|---|---|---|
-| A free SPI host + 4 pins | SX126x is SPI-only | ✅ `SPI3_HOST`, GPIO38/39/40/41 | ❌ **The C3 devices share one SPI bus between the panel and the SD card**; the S3 devices have SDMMC free but no spare CS/IRQ pins documented |
-| **`BUSY` line** | **Mandatory handshake**, not optional. Every command must wait for it | ✅ GPIO21 | ❌ |
-| **`DIO1` interrupt** | RX-done / TX-done. Polling works but wastes the sleep budget | ✅ GPIO5 | ❌ |
-| A reset you can drive | The module needs a hard reset in the bring-up sequence | ⚠ **behind M5IOE1 `IO10`** — RadioLib gets `RADIOLIB_NC` | ❌ |
-| A switchable power rail | The radio must be off in sleep or it dominates the budget | ✅ M5PM1 `G2` | ❌ |
-| **An antenna and an RF path** | Not optional and not free | ✅ FPC antenna, `SX_ANT_SW` on M5IOE1 `IO2` | ❌ no antenna, no matching, no connector |
-| Current headroom at TX | 118 mA @ +22 dBm | ⚠ 400 mA LDO, 140 mA software limit | ❌ unknown battery |
-
-**On any Xteink device this is a hardware project, not a firmware project.** There
-is no radio, no antenna, no RF path, no free interrupt line and — on the C3
-devices — not even a spare SPI bus. Do not let the "add LoRa to my e-reader"
-framing hide that.
-
-#### Driver options
-
-| Option | Licence | Footprint | RTOS assumptions | SoCs | Verdict |
-|---|---|---|---|---|---|
-| **RadioLib** `jgromes/RadioLib` | **MIT** (declared on `master`; ⚠ an older note in this repo said LGPL-3.0 — [unresolved discrepancy](../lora/README.md#72--pinning-is-not-optional-and-nobody-does-it-the-same-way), and the licence of the *pinned 7.2.1 tree* was never checked) | Not measured. The porting surface is two headers — `Hal.h`, `Module.h` | **None.** Blocking API; you supply a `RadioLibHal` over your own SPI/GPIO | Anything with SPI + 4 GPIO. Arduino **and** ESP-IDF | ⭐ **The default.** It is what M5Stack's own PaperMono firmware uses, at 7.2.1, and it implements **all four** of Semtech's mandatory SX126x errata workarounds |
-| Semtech **`sx126x_driver`** / LoRaMac-node | `NOASSERTION` | not measured | none, but LoRaMac-node's timing assumptions are strict | any | The authoritative reference and the certification lineage. Heavy. Last push 2024-07-03 |
-| Semtech **LoRa Basics Modem** (`SWL2001`) | BSD-3-Clause-Clear | not measured | own scheduler | any | The live Semtech stack; the successor to LoRaMac-node |
-| Semtech **`lr20xx_driver`** (inside **USP**) | BSD-3-Clause-Clear | not measured | none | LR2021/22/12, with claimed back-compat to SX126x/LR11xx | ⚠ **Explicitly pre-production**: *"not intended for production use."* Only relevant if you fit an [LR2021](../../components/semtech/lr2021/README.md) |
-| **Meshtastic** (whole stack) | **GPL-3.0** | A complete application, not a library | FreeRTOS + its own scheduler | many | Off-grid messaging out of the box. ⚠ **GPL-3.0 will infect an MIT reader firmware.** This is the licence decision, not a technical one |
-| Raw SPI | — | smallest | none | any | Feasible — the command interface is small — but §5.6 of the LoRa guide lists exactly the four errata workarounds a hand-rolled driver silently omits |
-
-**Pin the driver.** M5Stack's own published PlatformIO snippet pins nothing and
-pulls `master`; its shipped firmware pins 7.2.1 *and patches it*. Meshtastic pins a
-raw commit archive. Building from the documentation does not reproduce the shipped
-firmware.
-
-#### Flash and RAM cost
-
-**`inferred`, and weakly — nothing here was measured.** What is actually known:
-
-- RadioLib is 409 files, but a build links only `src/modules/SX126x/` plus
-  `Module`/`Hal`. **No size for that subset was measured by anyone in this
-  repository.**
-- The upstream CrossPoint project's stated current focus is *"DRAM/heap footprint
-  (the C3 sets the ceiling), then flash footprint"* — i.e. the memory budget is
-  already the binding constraint on the ecosystem's tightest target.
-- The realistic added cost is a driver plus a protocol plus a UI, and on a
-  **C3 with no PSRAM** the UI is likely to dominate.
-
-**Anyone who needs a real number should build `[env:papermono]` twice, with and
-without the radio, and diff the `pio run` size report.** That is a ten-minute job
-that nobody has done, and it would replace this whole paragraph.
-
-#### Plugin, or fork?
-
-**Firmware change required.** See §4 — LoRa needs SPI and expander-controlled
-enables, and neither is on the plugin ABI.
-
-### 3.2 NFC read/write
-
-#### Hardware prerequisites
-
-| Requirement | Why | PaperMono | Cap CC1101 |
-|---|---|---|---|
-| A free I²C **or** SPI attachment | The ST25R3916 is strapped by `I2C_EN` to either | ✅ I²C `0x50` @ 400 kHz on the **shared** system bus | ✅ SPI, shared with the CC1101 |
-| An **IRQ line** | The chip signals through a single IRQ; the transaction shape is IRQ-driven | ⚠ GPIO6 exists and **no vendor code uses it** — the app polls | present |
-| A power enable | The front end idles expensively; you want it off | ✅ M5IOE1 `IO4` | host-gated rail |
-| **A tuned antenna** | An NFC reader is *a tuned transformer, not a transmitter* | ⚠ present — but **schematic sheet 1 of 2, containing the matching network, antenna and crystal, is unpublished** | ✅ full differential match + EMC filter on the schematic |
-| A 27.12 MHz reference | 13.56 MHz carrier = 27.12/2 | on the unpublished sheet | ✅ `Y1`, C19/C20 = 6.0 pF |
-| Current headroom | field generation is bursty | no figure published | vendor: **96 mA** for CC1101 continuous TX *and* NFC continuously reading; **140.87 µA** with both asleep |
-
-**The antenna is the hard part and it is not a software problem.** A correct
-driver on a badly matched antenna reads nothing and looks exactly like a driver
-bug. RFAL even ships **`rfal_rfst25r3916_analogConfigTbl.h` — analog register
-settings per technology, per bit rate, per direction — matched to a reference
-antenna**, so a different antenna may need a different table. See
-[`guides/nfc` §4](../nfc/README.md#4-antenna-and-matching--the-part-people-get-wrong).
-
-#### Driver options
-
-| Option | Licence | Footprint | RTOS assumptions | Silicon | Verdict |
-|---|---|---|---|---|---|
-| **ST RFAL** (`stm32duino/NFC-RFAL` 2.0.2 + `stm32duino/ST25R3916` 2.1.0) | `NOASSERTION` on the stm32duino packaging | not measured; full stack RF → technology layers → ISO-DEP/NFC-DEP → tag types → NDEF | none inherent; needs a timer and a bus layer | **ST25R only** | ⭐ **The reference implementation**, and the only 2026-maintained line with a vendor behind it. **Porting = implementing `st25r3916_com.cpp` + `st25r3916_timer.cpp` + interrupts.** Everything above `rfal_rf.h` is portable by construction |
-| **`M5Unit-NFC`** | — | not measured; reaches *higher* than RFAL (Crypto1, AES, DESFire helpers, ISO-DEP, NDEF, APDU) | M5UnitUnified hub | ST25R3916, **SPI and I²C** | What the PaperMono actually ships. ⚠ It is **not** an RFAL wrapper — 301 entries in the pinned tree, **no ST source, no ST licence header**. Correspondingly less provenance |
-| **PN532** (`adafruit/Adafruit-PN532`, `elechouse/PN532`) | `NOASSERTION` / none declared | small | none | PN532 | Only if you are *choosing* the front end. ⚠ **No ISO 15693** — it will never read an ICODE tag |
-| **MFRC522 / "RC522"** (`miguelbalboa/rfid`) | Unlicense | smallest | none | MFRC522 | ⚠ **Frozen** — *"development by owner miguelbalboa has ended"*, badge `no/2019`. **Type A only.** Successor: `OSSLibraries/Arduino_MFRC522v2`, LGPL-2.1 |
-| PN5180 (`ATrappmann/PN5180-Library`) | LGPL-2.1 | — | none | PN5180 | ⚠ **archived**, last push 2022-06 |
-| A hand-written driver | yours | `paper_name_plate`: **28.9 KB of Rust source** for the ST25R3916 + **19.8 KB** for Type-2 tag emulation | `no_std`, blocking | ST25R3916 | **Proven on this exact board.** Those are *source* sizes, not compiled footprint |
-
-**The selection axis is which technologies you must support, not price.** An RC522
-that cannot see an ISO 15693 tag is not cheap, it is wrong.
-
-#### ⚠ What has actually been read on a PaperMono: nothing that anyone published
-
-M5Stack advertises ISO14443A, ISO14443B, FeliCa and ISO15693. The library exposes
-four matching layer classes and the demo cycles all four. **That the code path
-exists is not evidence that a card was read.** No vendor test report, no
-compatibility list, no community report and no read-range figure exists. The only
-indirect hint is the scan-window asymmetry (3500 ms for type A vs 900 ms for the
-others), and that is an inference from a constant. `not-tested`.
-
-#### Flash and RAM cost
-
-`inferred`. RFAL is a full protocol stack and is the larger of the two realistic
-options; `M5Unit-NFC` goes further up the stack still (Crypto1, DESFire). The
-vendor's own scan app runs in a **16 KB stack task at priority 4**, which is the
-only concrete resource figure anyone publishes. Nothing else was measured.
-
-#### Plugin, or fork?
-
-**Firmware change required — but the smallest of the three.** NFC needs one I²C
-transfer service, one expander pin and one IRQ. §4.4 argues this is the capability
-worth exporting as a *capability service* rather than as raw bus access.
-
-### 3.3 RGB frontlight / sidelight
-
-⚠ **Terminology first, because three different things get called this.**
-
-| Thing | What it is | On which device |
-|---|---|---|
-| **Frontlight** | An LED string edge-lit into the e-paper stack so you can read in the dark. **Not** RGB — warm/cool at best | PaperMono (white, AW9967 boost, 15 V rail) · Xteink X4 Pro (**dual warm/cool**) · ZeroWriter Fold (claimed, 10 levels) |
-| **RGB status indicator** | A single side-mounted RGB LED that shows state | PaperMono (`RS-C1415MBAR`) |
-| **Addressable RGB string** (WS2812 &c.) | A chain of self-clocked smart LEDs | **No e-ink device in this repository has one.** The Cardputers and the Unit C6L do |
-
-If the goal is "a coloured glow along the edge of my reader", that is the third
-row, and **nothing in this repository does it today** — you are adding a part, not
-enabling one.
-
-#### Hardware prerequisites
-
-| Requirement | Frontlight (PaperMono) | RGB indicator (PaperMono) | Addressable string (hypothetical) |
-|---|---|---|---|
-| Host GPIO | **none — costs you zero host pins** | **none** | **one**, and it must reach RMT or an equivalent |
-| Control path | M5PM1 `G3` → **PWM0** → AW9967 boost → 15 V rail | red = M5PM1 `LED_EN_PP`; green = M5IOE1 `IO8` PWM2; blue = M5IOE1 `IO9` PWM1 | direct |
-| Power state | **L3B only.** There is no way to light it from L0/L1/L2 | red survives on the M5PM1; **green/blue die with L3B** | rail-dependent |
-| Current | **~11 mA** `inferred` from `R29 = 18 Ω` | not published | ~20 mA per LED at full white, ×N |
-| Timing | 5 kHz PWM (see below) | 5 kHz | **~800 kbit/s self-clocked, tight enough that bit-banging is unreliable under interrupts** |
-
-#### Three things that will surprise you on the PaperMono
-
-All three are software or documentation issues, fixable without touching the board:
-
-1. **The brightness curve is squared.** `M5GFX.cpp:849` does
-   `br = brightness * brightness`. `setBrightness(128)` is roughly a **quarter** of
-   full output, not half. A linear UI slider is lying to the user. A commented-out
-   linear write sits directly above it at `:847`.
-2. **The PWM frequency is below the driver's rated range.** M5GFX programs 5 kHz;
-   the AW9967 datasheet specifies **10–100 kHz**. A 5 kHz square wave into an
-   inductor-based boost converter is inside the audible band. Rewriting registers
-   `0x34`/`0x35` to 20–50 kHz after `M5.begin()` is a one-line change. **Nobody has
-   reported whether the board audibly whines.**
-3. **The red die has no PWM at all** — it is on `LED_EN_PP`, which is not a PWM
-   output. This is a **board** limit and cannot be worked around. Any colour needing
-   partial red — orange, pink, warm white, most pastels — is unreachable. M5Unified
-   is more limited still: it writes blue as a *binary* level, so through `M5.Led`
-   you get red on/off × blue on/off × green graded. The factory firmware PWMs both
-   green and blue by driving M5IOE1 directly, and **nothing documents why M5Unified
-   does not.**
-
-⚠ **`PYG3` is the most dangerous token in the PaperMono's documentation.** On the
-**M5PM1** it is the frontlight PWM net. On the **M5IOE1** it is the **e-paper 3.3 V
-rail enable**. Write to the wrong one and you cut the display's power, with no
-error reported. Read
-[`pin-naming-and-the-pyg-ambiguity.md`](../../devices/m5stack/papermono/pin-naming-and-the-pyg-ambiguity.md)
-before touching either.
-
-#### Driver options for an addressable string
-
-| Option | Licence | Footprint | RTOS assumptions | SoCs | Verdict |
-|---|---|---|---|---|---|
-| **ESP-IDF `led_strip`** | Apache-2.0 | small | ESP-IDF | ESP32 family | The idiomatic ESP-IDF answer. Uses RMT or SPI backend |
-| **RMT directly** | (IDF) | smallest | ESP-IDF | ESP32 family | Full control. Note the **ESP32-S3 has 4 TX + 4 RX RMT channels, fixed, sharing a 384×32-bit RAM** — the RX half is *not* repurposable, so more than four simultaneous strings needs SPI, I2S/LCD or PARLIO. The plain ESP32 has 8 flexible channels |
-| **FastLED** | MIT | larger — it carries colour maths, palettes and effects | none | wide | Good if you want the animation library. Overkill for a status indicator |
-
-⚠ **On an ESP32-S3 the GDMA pool is already crowded.** SPI2, SPI3, I2S0, I2S1,
-SDMMC, AES, SHA, UHCI, RMT ch3/ch7 and LCD_CAM all draw from ten shared channels; a
-design running QSPI display + I2S audio + SD concurrently is already using six.
-`ESP_ERR_NOT_FOUND` from a driver's DMA init is the symptom of exhaustion.
-
-#### One real-world lesson from the Cardputers, worth importing
-
-The Cardputer v1.1 and ADV put the WS2812's supply on **`BL_3V3`**, the *switched
-backlight rail*, where the v1.0 had it on always-on `VDD_3V3`. Consequence, in
-M5Stack's own words: *"when the LCD backlight brightness is below 100%, RGB will
-not be powered properly."* **PWM-dimming the display browns out the indicator.**
-That is a regression introduced to buy lower sleep current, and it is exactly the
-mistake to avoid when adding an LED to a device whose frontlight you also intend
-to dim.
-
-#### Flash and RAM cost
-
-`inferred`, small in all three cases — an LED driver is a handful of kilobytes.
-The cost of an addressable string is **RMT channels and DMA**, not flash.
-
-#### Plugin, or fork?
-
-**Firmware change required.** GPIO, ADC, PWM and LEDC are all absent from the
-plugin ABI (§4), and on the PaperMono the frontlight is not on a host GPIO at all —
-it is two I²C writes to a power-management MCU.
-
----
-
-## 4. The crux: what the plugin surface can and cannot reach
-
-**This is the section to read if you read only one.** The authoritative document is
-[`software/applications/crosspoint-reader/plugins/README.md`](../../software/applications/crosspoint-reader/plugins/README.md),
-and its central finding is that **there is no single "CrossPoint plugin system" —
-there are two, of completely different kinds**, and confusing them produces wrong
-answers.
-
-| System | Where code runs | Can it reach GPIO / I²C / SPI? | Enforcement |
-|---|---|---|---|
-| **Upstream CrossPoint** (roadmap, unmerged branches) | **Browser only** — JavaScript + JSON manifests | **No.** No code executes on the MCU at all | Absolute. There is nothing to work with |
-| **`mekhontsev` fork** — native SD plugins | **On the MCU** — native C++ ELF modules loaded from `/plugins` against a versioned host ABI (v3) | **No** — but only because the host symbol allow-list omits them | **Hard: the link fails** |
-| **Firmware source** (any fork) | on the MCU | **Yes.** `#include <Wire.h>` and go | **None** |
-
-### 4.1 The allow-list, read at source
-
-`mekhontsev/crosspoint-reader:main/src/plugins/PluginHostSymbols.inc` — 81 lines,
-5,201 bytes — was **read directly** on 2026-09-04 (`executed-success`). Census:
-
-| Category | In the allow-list? |
-|---|---|
-| **I²C** | **absent** |
-| **SPI** | **absent** |
-| **GPIO** (`pinMode`, `digitalWrite`) | **absent** |
-| **ADC / PWM / LEDC** | **absent** |
-| **Wi-Fi** | **absent** |
-| **Storage / file** | **absent** |
-| BLE (`ble_terminal::*`) | **present, 15 symbols** |
-
-What *is* exported: `logPrintf`; `GfxRenderer` (fonts, clear, text width, buffer);
-`UITheme` centred/wrapped text; `Activity` lifecycle; `I18n::getInstance`;
-`EspClass::getFreeHeap` / `getFreePsram`; the `ble_terminal` transport.
-
-**A plugin gets UI, input, BLE, i18n and heap introspection — and nothing that
-touches a bus, a pin or a filesystem.** That is not a documentation gap; it is the
-contract, in the file, and the build enforces it.
-
-### 4.2 Therefore, per capability
-
-| Capability | Upstream JS plugin | Native ELF plugin | Firmware source |
-|---|---|---|---|
-| **LoRa** | ❌ impossible — no MCU execution | ❌ needs SPI + expander enables → **link-time failure by design** | ✅ |
-| **NFC read/write** | ❌ impossible | ❌ needs I²C + expander enable | ✅ **demonstrated** by `paper_name_plate` |
-| **RGB sidelight** | ❌ impossible | ❌ needs GPIO/RMT, or I²C for the PaperMono's LED | ✅ |
-| A *UI* for any of the above | ⚠ partial — a web page talking to the firmware's HTTP server | ✅ | ✅ |
-
-### 4.3 But the gap is smaller than "fork the reader"
-
-The native-plugin documentation states the escape hatch itself: *"When a genuinely
-reusable host service is missing, add the smallest stable entry point to the
-firmware ABI, add it to the allow-list, and increment the ABI if the change is
-incompatible."*
-
-So the honest verdict is **a firmware change is required, but a small, structured
-one** — an `i2cTransfer` / `spiTransfer` host service plus expander-pin control,
-added to `PluginHostSymbols.inc` with an ABI bump. The radio driver itself
-(RadioLib, an ST25R3916 stack) could then live entirely in the plugin.
-
-Two caveats before treating that as a plan:
-
-- **The native plugin ABI is Xteink X4 Pro-only today.** The PaperMono is not a
-  target of that fork, and its peripherals sit behind an M5IOE1 expander and an
-  M5PM1 power manager the fork has never seen. The port comes first.
-- **Exporting raw bus access weakens the containment story.** The plugin host is
-  explicitly *not* a sandbox — *"a bad plugin can crash and restart the reader"* —
-  and a plugin that can drive I²C can wedge the bus that the RTC, touch, IMU,
-  expander and power manager all share. The IP2315 charger on that bus already has
-  a documented wedge failure mode.
-
-### 4.4 The design recommendation
-
-**Export *capability* services, not raw buses.** "Read an NFC tag", "send a LoRa
-packet", "set the indicator colour" — keeping bus arbitration inside the firmware
-where it belongs. That is a firmware feature with a plugin-facing API, which is
-arguably the right architecture anyway, and it is the only version that survives
-the shared-I²C-bus hazard.
-
-### 4.5 And note: the *SDK* boundary is not a barrier at all
-
-Do not confuse the plugin boundary with the FreeInk SDK boundary. **Firmware source
-can call `Wire`, `SPI` and RadioLib directly, and CrossInk already does exactly
-this for ESP-NOW** — `NearbyBookPositionSyncActivity.cpp` and
-`NearbyStatsSyncActivity.cpp` `#include <esp_now.h>` and call `esp_now_init()`
-straight from an Activity, with no `FREEINK_CAP_ESPNOW`, no SDK manager and no
-board-profile field. The abstraction was simply bypassed, and it shipped.
-
-The SDK *does* already carry `M5Ioe1.h` (160 lines) and `M5Pm1.h` (213 lines) with
-full register maps and PaperMono-aware bus init. **What is missing is four pin
-constants**, and they are precisely the radio pins:
-
-| Expander pin | Net | Function | In the SDK? |
-|---|---|---|---|
-| M5IOE1 `IO2` | `PYB_LoRa_ANT_SW` | LoRa antenna switch | **no** |
-| M5IOE1 `IO4` | `PYB_NFC_EN` | **NFC power enable** | **no** |
-| M5IOE1 `IO10` | `PYB_LoRa_RST` | **LoRa reset** | **no** |
-| M5PM1 `G2` | `PYG2_LoRa_EN` | **LoRa 3V3 rail** | **no** |
-
-⚠ Bit positions for those masks are **`inferred`** from the device record's pin
-table (IO*n* → bit *n*−1), not read from a datasheet. Verify against the schematic
-before use. Independent corroboration that the three expander assignments are
-right comes from `paper_name_plate`, which derived them from its own reading of the
-hardware and matched exactly.
-
----
-
-## 5. Difficulty and conflict-risk, per capability per target firmware
-
-Ratings are **`inferred`** — no port was attempted. The reasoning is shown so you
-can disagree with it.
-
-### 5.1 CrossPoint Reader (MIT, upstream, ★7,538)
-
-| Capability | Difficulty | Conflict risk | Reasoning |
-|---|---|---|---|
-| **LoRa** | **High** | **Medium** | Driver work is easy (RadioLib, a `RadioLibHal`, six pin numbers). The hard parts are: upstream's `SCOPE.md` says the project is *"a dedicated e-reader"* and is explicitly not kitchen-sink, so this is out of scope by policy; the C3 sets a **DRAM/heap ceiling** that upstream is actively trying to reduce; and any UI lands in files upstream develops. Conflict risk is *medium* not *high* only because a radio Activity is a new file |
-| **NFC** | **Medium** | **Low** | Smallest hardware surface: one I²C address, one enable, one IRQ. `paper_name_plate` proves the chip works. Same scope objection applies |
-| **RGB sidelight** | **Low** | **Medium** | Trivially small code. But the frontlight already has an `ActivityManager` gesture and a `Frontlight.present()` guard, so a second light source lands in files upstream touches |
-
-**Upstream will probably not take any of these**, and its acceptance test says so
-politely: *"Is another popular CrossPoint fork already solving this well? If yes,
-defer to that fork."* Upstream deliberately delegates non-core features to its own
-fork network. That is a feature of the ecosystem's design, not an obstacle.
-
-### 5.2 FreeInk SDK (MIT, the framework beneath CrossPoint)
-
-| Capability | Difficulty | Conflict risk | Reasoning |
-|---|---|---|---|
-| **LoRa** | **High** | **Low** | Doing it *properly* means new board-profile struct fields (there is **nowhere to put SPI radio pins today** — grepping the SDK for GPIO 38/39/40/41/21/5 returns nothing), a `LoRaManager` peer to `Rtc`/`Imu`, and a `FREEINK_CAP_LORA` gate. Weeks, plus review. **But there is a real argument for it**: the SDK already carries `T5S3_LORA_CS/IRQ/RST/BUSY` for the LilyGO T5S3, so a *second* LoRa board exists to justify the abstraction |
-| **NFC** | **Medium** | **Low** | Same shape, smaller. `FREEINK_CAP_NFC` |
-| **RGB sidelight** | **Low** | **Low** | The SDK already has an LED manager and capability gates; `PIN_LED_GREEN (IO8)` / `PIN_LED_BLUE (IO9)` are already defined for the PaperMono |
-| **The four missing pin constants** | **Trivial** | **Very low** | Four `constexpr uint16_t` masks, one `GPIO2` constant, extend `OUTPUT_MASK`. This is the single highest-value small change available |
-
-⚠ **The SDK has no CI validation for device ports**, so a port can break without
-its own tests noticing. And **forks pin different SDK commits**, so a fork's
-behaviour can differ from upstream's *without a single line of fork-owned code
-differing*.
-
-Also recorded for whoever picks this up: **the SDK declares `ImuType::None` for
-the PaperMono despite a BMI270 being fitted and wired.** Whether that is
-deliberate or simply unported is **not established**.
-
-### 5.3 CrossPlay (MIT, `ma-r-s/crossplay`, ★15/17)
-
-| Capability | Difficulty | Conflict risk | Reasoning |
-|---|---|---|---|
-| **LoRa** | **Medium** | **Very low** | CrossPlay's quarantine pattern — everything new lives in `src/apps_local/`, `assets_local/`, `host-tests/`, paths that **do not exist upstream** — means a radio app is a new-file addition that cannot conflict. Its fork is ~90 % new files with about a dozen small, mostly append-only seams |
-| **NFC** | **Medium** | **Very low** | idem |
-| **RGB sidelight** | **Low** | **Low** | idem, though it already touches `ActivityManager.cpp` for the frontlight gesture |
-| **Any of them, as an upstreamable change** | **High** | — | CrossPlay's own `LOCAL_SCOPE.md` says *"anything that makes reading better belongs upstream, so send it there"* — a radio is not that |
-
-⚠ **CrossPlay's PaperMono support is unverified.** The `papermono` envs are in
-`platformio.ini`, **absent from `LOCAL_SCOPE.md`**, and nobody has reported running
-it on that board. Do not start here assuming the target works.
-
-### 5.4 Summary matrix
-
-| | CrossPoint Reader | FreeInk SDK | CrossPlay |
-|---|---|---|---|
-| **LoRa** | High / Medium — **blocked by scope policy** | High / Low — *the right home, eventually* | Medium / **Very low** — ⭐ **start here** |
-| **NFC** | Medium / Low | Medium / Low | Medium / **Very low** |
-| **RGB sidelight** | Low / Medium | **Low / Low** — ⭐ | Low / Low |
-
----
-
-## 6. The order of work, if you are actually going to do this
-
-`inferred` — a plan, not a report.
-
-1. **Prototype in a fork, hardcoding pins in an Activity.** Exactly as CrossInk
-   hardcodes its ESP-NOW setup. This answers the only question that matters — does
-   the hardware work, are the rails right, does the antenna switch behave — without
-   committing to an API design. **Effort: days.**
-2. **Start from upstream CrossPoint, not CrossInk.** Upstream already has
-   `[env:papermono]` and pins an SDK commit containing PaperMono support. CrossInk
-   would cost a **136-commit SDK bump plus a 294-commit merge into 224 modified
-   `lib/` files**, for no benefit, and it has no PaperMono support at all.
-3. **Do NFC before LoRa.** Smaller hardware surface, a working third-party
-   implementation to compare against, no antenna design, no regional legality
-   question, and the failure modes are well characterised.
-4. **Measure the two things nobody has measured** while you have it on a bench:
-   frontlight current, and what a LoRa transmit does to a panel refresh. Both are
-   cheap and both are currently blank in this repository.
-5. **Then upstream to the SDK if it proves out** — the four pin constants first,
-   then `FREEINK_CAP_LORA` / `FREEINK_CAP_NFC` and a manager, using the LilyGO
-   T5S3's existing LoRa pins as the second board that justifies the abstraction.
-   **Effort: weeks, plus review.**
-6. **Only then think about the plugin ABI**, and export capability services rather
-   than raw buses (§4.4).
-
-⚠ **Regional band configuration becomes your legal responsibility the moment you
-transmit.** The PaperMono, the Cap LoRa-1262 and the Cap CC1101 are all **single
-wideband SKUs spanning EU 868, US 915 and JP 920 allocations with no published
-certification of any kind**, and there is **no module datasheet for the
-`Stamp-LoRa-1262` in any form located** — so RF output at the connector, antenna
-gain and the internal matching network are all unknown. See
-[`guides/lora` §3](../lora/README.md#3-regional-band-plans-and-duty-cycle).
-
----
-
-## 7. Evidence boundary
-
-- **Nothing was built, compiled, flashed, transmitted or measured in this pass.**
-- Every "vendor firmware does X" claim is `executed-success` **on the read of the
-  source**, and `not-tested` on hardware.
-- Every flash/RAM figure is `inferred` or explicitly absent. **No binary size for
-  any of these capabilities exists anywhere in this repository.**
-- Every current figure is a datasheet or vendor number under conditions that are
-  often unstated. The one board-level state-resolved table that exists
-  (Cap LoRa868) is for a *different board* at a *different TX power*.
-- **NFC on the PaperMono is `reported-working` by exactly one third party**
-  (`paper_name_plate`); **LoRa on the PaperMono is `not-tested` by anyone,
-  anywhere.**
-- The plugin ABI census is `executed-success` — the file was read — but **no plugin
-  was built and the ABI-v3 contract is untested here.**
-- The M5IOE1 bit positions in §4.5 are **derived, not read from a datasheet**.
-
-## Related
-
-- [`guides/lora`](../lora/README.md) · [`guides/nfc`](../nfc/README.md) · [`guides/hardware/e-paper-displays.md`](e-paper-displays.md)
-- [PaperMono LoRa](../../devices/m5stack/papermono/features/lora.md) · [NFC](../../devices/m5stack/papermono/features/nfc.md) · [frontlight](../../devices/m5stack/papermono/features/frontlight.md) · [buttons and RGB LED](../../devices/m5stack/papermono/features/buttons-and-rgb-led.md) · [I/O expander](../../devices/m5stack/papermono/features/io-expander.md) · [power and sleep](../../devices/m5stack/papermono/features/power-and-sleep.md)
-- [Cap LoRa-1262](../../devices/m5stack/cap-lora-1262/README.md) · [Cap CC1101 & NFC](../../devices/m5stack/cap-cc1101/README.md) · [Cap LoRa868](../../devices/m5stack/cap-lora868/README.md)
-- [Xteink X3 NFC tag](../../devices/xteink/x3/features/nfc.md) — **the thing that is not a reader** · [Xteink Nano](../../devices/xteink/nano/README.md)
-- [Radios on the PaperMono](../../software/ecosystems/crosspoint-freeink/radios-on-papermono.md) — the feasibility assessment this guide generalises
-- [CrossPoint plugin systems](../../software/applications/crosspoint-reader/plugins/README.md) — **the plugin ABI, read at source**
-- [CrossPoint Reader](../../software/applications/crosspoint-reader/README.md) · [FreeInk SDK](../../software/frameworks/freeink-sdk/README.md) · [CrossPlay](../../software/applications/crossplay/README.md) · [fork network](../../software/ecosystems/crosspoint-freeink/fork-network.md)
-- [Xteink firmware ecosystem](../../devices/xteink/firmware-ecosystem.md) — which firmware supports which board, and what a new board must provide
-- [Components: SX1262](../../components/semtech/sx1262/README.md) · [LR2021](../../components/semtech/lr2021/README.md) · [ST25R3916](../../components/stmicroelectronics/st25r3916/README.md) · [CC1101](../../components/texas-instruments/cc1101/README.md) · [AW9967](../../components/awinic/aw9967/README.md) · [WS2812](../../components/worldsemi/ws2812/README.md) · [M5IOE1](../../components/m5stack/m5ioe1/README.md) · [M5PM1](../../components/m5stack/m5pm1/README.md)
diff --git a/guides/hardware/lora-radio-generations.md b/guides/hardware/lora-radio-generations.md
deleted file mode 100644
index 3105456..0000000
--- a/guides/hardware/lora-radio-generations.md
+++ /dev/null
@@ -1,511 +0,0 @@
-# The four generations of Semtech LoRa transceiver silicon
-
-**What "the 4th gen LoRa chip" is, where the generation numbering comes from, what changed at each
-step, and — the part that costs you weeks — what breaks when you move between them.**
-
-Written 2026-09-04. Every claim carries a source marker; §0.1 defines them.
-
-> **Scope.** This guide covers **end-node transceivers**. Semtech's gateway/concentrator silicon
-> (SX1301/SX1302/SX1303/SX1308 and the SX125x/SX1250 radio front ends) is a separate product line
-> — `lora-core` rather than `lora-connect`/`lora-edge`/`lora-plus` — and is not generation-numbered
-> alongside the transceivers. **[SM]**
->
-> **Related.** [`guides/lora`](../lora/README.md) is the device-independent LoRa domain guide —
-> modulation arithmetic, airtime, duty cycle, band plans, antenna and debugging. This guide is
-> about the *silicon lineage*. Read that one to understand LoRa; read this one to choose or migrate
-> a part.
-
----
-
-## 0. The short answer
-
-**The "4th generation LoRa chip" is the Semtech LR2021**, and the label is Semtech's own — printed
-on page 1 of its datasheet as **"Generation 4 LoRa® IP"** and used in the product page's own HTML
-title. It is the first member of a new family, **LoRa Plus™**, which also contains the **LR2022**
-and **LR2012**. **[DS20]**, **[PP]**
-
-The full lineage is not inferred. Semtech states it in **§23.8 of the LR20xx datasheet**, headed
-*"Compatibility of Generation 1-4 LoRa Radios"*, verbatim:
-
-> Semtech has developed four generations of LoRa radios:
-> • **Generation 1 (Gen 1): SX1272, SX1276** - First LoRa chips (2013)
-> • **Generation 2 (Gen 2): SX1261, SX1262, SX1280** - Enhanced performance and efficiency
-> • **Generation 3 (Gen 3): LR1110, LR1120, LR1121** - LoRa Edge™ - Added geolocation
-> • **Generation 4 (Gen 4): LR2021 LoRa Plus™** Multi-band, and multi-protocol
-
-The identical paragraph appears in **[DS20-1.1]** §23.7, six months earlier — so it is corroborated
-across two document revisions, not an editorial one-off. Two further primary confirmations:
-the **LR1121** product page opens *"The LR1121 is Semtech's **third generation** ultra-low power
-LoRa transceiver"* **[PP]**, and Waveshare's `Core2021` listing independently calls the LR2021
-*"the **fourth-generation** LoRa multi-band transceiver"* **[3P]**.
-
-### 0.1 One line per generation
-
-| Gen | Parts Semtech names | Also in the family | Introduced | Defining change | Host interface |
-|---|---|---|---|---|---|
-| **1** | **SX1272, SX1276** | SX1273, SX1277, SX1278, SX1279 | **2013** **[DS20]** | LoRa exists | **Register-mapped SPI**, no `BUSY` |
-| **2** | **SX1261, SX1262, SX1280** | SX1268, LLCC68; STM32WL (SX126x core on-die) | **2018** (SX1280 2017) **[WB]** | "Enhanced performance and efficiency" — 2× lower RX current, +22 dBm, SF5, LR-FHSS, 2.4 GHz | **Command-based SPI + mandatory `BUSY`** |
-| **3** | **LR1110, LR1120, LR1121** | — | **2020** (LR1110) **[WB]** | "Added geolocation" — GNSS + Wi-Fi passive scanning, **AES-128 crypto engine and secure key store** | Command-based, **LR11xx** command set |
-| **4** | **LR2021** | LR2022, LR2012 | announced **2025-03-12** **[COM]**; datasheet Rev 0.2 **June 2025** **[DS20]** | "Multi-band, and multi-protocol" — dual-band single-SKU, FLRC to 2.6 Mbps, multi-SF receive, BLE/802.15.4/Z-Wave/Sigfox PHYs, SATCOM | Command-based, **16-bit opcodes**, LR20xx command set |
-
-### 0.2 Three things this rules out
-
-| Common claim | Verdict |
-|---|---|
-| *"SX1280 / LoRa at 2.4 GHz is its own generation"* | ❌ **No.** Semtech puts SX1280 in the **Gen 2** bullet beside the SX1261 and SX1262. 2.4 GHz is a band, not a generation |
-| *"LR-FHSS is a generation"* | ❌ **No.** It is a modulation, present on SX126x (Gen 2), LR11xx (Gen 3) and LR20xx (Gen 4). The LR-FHSS patent notice **[DS20]** p. 3 names `SX1261, SX1262, SX1268, LR1110, LR1120, LR1121, LR2012, LR2021, LR2022` as the parts whose purchase conveys rights — a neat cross-generation list |
-| *"'4th generation' is community shorthand"* | ❌ **No.** It is on the datasheet cover, in the general description, in the product page title, and in §23.8's heading |
-
-⚠ **§23.8 names one or two representatives per generation, not every part.** SX1268 and LLCC68 are
-absent but are SX1262 siblings (Gen 2); SX1273/77/78/79 are absent but are SX1272/76 siblings
-(Gen 1); LR2022 and LR2012 are absent because §23.8 was written when the LR2021 was alone.
-Assigning those by family is **[INF]**, and marked as such wherever it matters.
-
----
-
-## 0.3 Evidence markers
-
-| Marker | Source |
-|---|---|
-| **[DS20]** | `DS.LR20xx` LR2021/LR2022/LR2012 datasheet **Rev 2.1**, 13/04/26, 243 pp — [held here](../../components/semtech/lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) |
-| **[DS20-1.1]** | The same document at **Rev 1.1**, 10/14/25 — [archived](../../components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md) |
-| **[DS12]** | `DS.SX1261-2` **Rev 2.2**, Dec 2024 — read by the [SX1262 record](../../components/semtech/sx1262/README.md), not re-read here; figures attributed to it are that record's transcription |
-| **[DS76]** | `SX1276/77/78/79` datasheet **Rev. 5, August 2016** — [held here](../../components/semtech/sx1276/artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf) |
-| **[PP]** | Semtech product pages, retrieved 2026-09-04 |
-| **[SM]** | `www.semtech.com/sitemap-products.xml`, retrieved 2026-09-04 |
-| **[DRV]** | Semtech `lr20xx_driver` v2.0.2 in `LoRa-Net/usp` @ `512a095e…` |
-| **[RL]** | RadioLib source, read live at named tags |
-| **[MT]** | Meshtastic firmware source, read live |
-| **[3P]** | Third-party vendor page (Waveshare, Seeed) |
-| **[WB]** | Secondary/date evidence — first appearance in an artifact or archive capture; see §7 |
-| **[COM]** | Community — catalogued in [`lr2021/projects-and-community.md`](../../components/semtech/lr2021/projects-and-community.md) |
-| **[INF]** | Inference |
-
-⚠ **Nothing in this guide was measured.** Every electrical figure is a manufacturer specification,
-reproduced. Where two generations' numbers are compared, they come from two different documents
-written years apart under **different measurement conditions** — see §3.1's warning before drawing
-a conclusion from a 1 dB difference.
-
----
-
-## 1. The product families, and why the URL matters
-
-Semtech's own catalogue splits the transceivers into families that map onto generations, and
-knowing this is the fastest way to tell what you are looking at. **[SM]**
-
-| URL family | Marketing name | Contains | Generation |
-|---|---|---|---|
-| `/products/wireless-rf/lora-connect/` | **LoRa Connect™** | SX1272, SX1276, SX1278, SX1261, SX1262, SX1268, LLCC68, SX1280, SX1281, **LR1121** | Gen 1 **and** Gen 2 **and** part of Gen 3 |
-| `/products/wireless-rf/lora-edge/` | **LoRa Edge™** | **LR1110, LR1120** | Gen 3 |
-| `/products/wireless-rf/lora-plus/` | **LoRa Plus™** | **LR2012, LR2021, LR2022** | **Gen 4** |
-| `/products/wireless-rf/lora-core/` | LoRa Core™ | SX1250, SX125x, SX1301/2/3/8 | Gateway silicon — outside this guide |
-
-⚠ **Two traps here, both cost real time.**
-
-1. **`/lora-connect/lr2021` returns a hard HTTP 404.** The LR2021 lives under `lora-plus`. Guessing
-   the family from the part number's prefix does not work — `LR1121` is under `lora-connect` while
-   its own siblings `LR1110`/`LR1120` are under `lora-edge`. Verified 2026-09-04, `executed-success`.
-2. **The `lora-connect` index page does not list the LR2021 at all**, and lists `LR1121` but neither
-   `LR1110` nor `LR1120`. **The only complete enumeration is `sitemap-products.xml`.** **[SM]**
-
-**The LR1121 sitting in `lora-connect` rather than `lora-edge` is a real signal, not a filing
-error**: alone in Gen 3, the LR1121 has **no GNSS and no Wi-Fi scanner**. It is the LR1120 with the
-geolocation front end removed — a communications part in a geolocation family, so Semtech shelved
-it with the communications parts. §4.2.
-
----
-
-## 2. Feature matrix
-
-### 2.1 Modulation and PHY
-
-✅ present · ❌ absent · ⚠ present with a caveat spelled out below.
-
-| | **Gen 1** SX1276 | **Gen 2** SX1262 | **Gen 2** SX1280 | **Gen 3** LR1121 | **Gen 4** LR2021 |
-|---|:--:|:--:|:--:|:--:|:--:|
-| LoRa | ✅ SF6–SF12 | ✅ **SF5**–SF12 | ✅ SF5–SF12 | ✅ SF5–SF12 | ✅ SF5–SF12 |
-| **LR-FHSS** | ❌ | ✅ | ❌ | ✅ | ✅ (incl. **SATCOM**) |
-| (G)FSK | ✅ | ✅ | ✅ | ✅ | ✅ |
-| MSK / GMSK | ✅ | ✅ | ✅ | ✅ | ✅ |
-| OOK | ✅ | ❌ | ❌ | ❌ | ✅ (Rx to **2 Mbps**) |
-| **FLRC** | ❌ | ❌ | ✅ | ❌ | ✅ **to 2.6 Mbps** |
-| (D)BPSK — Sigfox uplink | ❌ | ⚠ via `AN1200.73` | ❌ | ⚠ via `AN1200.73` | ✅ native modem |
-| **BLE PHY** | ❌ | ❌ | ✅ "PHY layer compatibility" | ❌ | ✅ 1M/2M/Coded 500k/125k |
-| **O-QPSK 802.15.4** | ❌ | ❌ | ❌ | ❌ | ✅ Thread/Zigbee |
-| **Z-Wave / Z-Wave LR** | ❌ | ❌ | ❌ | ❌ | ✅ + HomeID & beam filtering |
-| **Wi-SUN FSK / WM-Bus** | ⚠ generic FSK | ⚠ generic FSK | ❌ | ⚠ generic FSK | ✅ **dedicated packet handlers** |
-| **Multi-SF receive** | ❌ | ❌ | ❌ | ❌ | ✅ |
-| **Multi-SF CAD, Fast CAD** | ❌ | ❌ | ❌ | ❌ | ✅ |
-| **Convolutional CR8/CR9** | ❌ | ❌ | ❌ | ❌ | ✅ |
-| **Long interleaver** | ❌ | ❌ | ✅ | ✅ | ✅ |
-| **Intra-packet freq. hopping** | ✅ | ❌ | ❌ | ❌ | ✅ (with an SX1276-compat mode) |
-| **Ranging / ToF** | ❌ | ❌ | ✅ ranging engine | ⚠ RTToF on LR1110/20 | ✅ **RTToF** §10 |
-| **GNSS scanning** | ❌ | ❌ | ❌ | ❌ **(LR1110/LR1120 only)** | ❌ |
-| **Wi-Fi passive scanning** | ❌ | ❌ | ❌ | ❌ **(LR1110/LR1120 only)** | ❌ |
-| **AES-128 crypto + key store** | ❌ | ❌ | ❌ | ✅ | ❌ **regression** |
-
-Rows sourced: LoRa/LR-FHSS/CAD/hopping/interleaver/CR from **[DS20]** §23.8 and §9; Gen-4 PHYs from
-**[DS20]** §11–§20; Gen-1/2/3 features from **[PP]** and **[DS76]**; crypto from **[PP]** LR1121 and
-a whole-document search of **[DS20]** returning no `AES` (§5.3).
-
-### 2.2 Radio and electrical
-
-| | **SX1276** (G1) | **SX1262** (G2) | **SX1280** (G2) | **LR1121** (G3) | **LR2021** (G4) |
-|---|---|---|---|---|---|
-| Frequency | **137–1020 MHz** | 150–960 MHz | 2.4 GHz ISM | 150–960 MHz **+ 2.4 GHz + 2 GHz S-band + 1.55 GHz L-band** | **150–960 MHz + 1.5–2.5 GHz** |
-| Max Tx | +20 dBm (+14 high-eff PA) | **+22 dBm** | +12.5 dBm | +22 dBm sub-GHz / **+11.5 dBm** 2.4 GHz | **+22 dBm** sub-GHz / **+12 dBm** HF |
-| Tx power step | — | 1 dB | 1 dB | 1 dB | **0.5 dB, 63 steps** |
-| Best LoRa sensitivity | **−148 dBm** | −148 dBm | −132 dBm | ≈−148 dBm class | **−143 dBm @SF12/62 kHz**, **−141.5 @SF12/125 kHz** |
-| Max link budget | 168 dB | 170 dB | — | — | not quoted as a single figure |
-| Rx current | **9.9 mA** | **4.6 mA** (4.2 mA quoted elsewhere) | "low, on-chip DC-DC" | ≈SX126x class | **5.7 mA** (LoRa SF7/125 kHz) |
-| Tx current @max | ~120 mA @+20 dBm | **118 mA @+22 dBm** | — | — | **105 mA @+22 dBm** |
-| Sleep / retention | **200 nA** register retention | ~600 nA–1.2 µA | — | — | **470 nA**; ⚠ **+80 nA with PRAM loaded** |
-| Supply | 1.8–3.7 V | 1.8–3.7 V | — | — | 1.8–3.7 V |
-| Regulator | LDO only | LDO **or DC-DC (core only — PA runs from `VBAT`)** | on-chip DC-DC | LDO or DC-DC | **SIMO buck feeding core *and* PA**, or LDO |
-| Package | **QFN 28** | **QFN 24, 4 × 4 mm** | QFN 4 × 4 | **QFN 32, 5 × 5 mm** | **QFN 32, 5 × 5 mm** |
-| Order code | `SX1276IMLTRT` | `SX1262IMLTRT` | `SX1280IMLTRT` | `LR1121IMLTRT` | `LR2021IMLTRT` |
-| Max LoRa bit rate | 300 kbps (FSK); ~37.5 kbps LoRa | 62.5 kbps LoRa | — | — | **125 kbps LoRa**, 2.6 Mbps FLRC |
-
-⚠ **Do not read the sensitivity row as a ranking.** SX1276's "−148 dBm" and SX1262's "−148 dBm" are
-headline figures at very narrow bandwidth; LR2021's "−141.5 dBm" is at **SF12/125 kHz with a 64-byte
-payload**, and the same part reaches **−143 dBm at 62 kHz**. **The three numbers come from three
-documents with different measurement conditions.** Compare like for like or not at all — the LR20xx
-datasheet's Table 3-17 is the only per-SF/per-BW grid transcribed anywhere in this knowledge base
-([LR2021 §5.3](../../components/semtech/lr2021/README.md)).
-
-### 2.3 Host interface — the migration-relevant row set
-
-| | **Gen 1** SX127x | **Gen 2** SX126x | **Gen 3** LR11xx | **Gen 4** LR20xx |
-|---|---|---|---|---|
-| Model | **Register-mapped** — read/write addresses | **Command/opcode** | Command/opcode | Command/opcode |
-| SPI mode | 0 | 0 | 0 | 0 |
-| Max SCK | 10 MHz | 16 MHz | 16 MHz | **16 MHz** |
-| **`BUSY` line** | ❌ **none** | ✅ **mandatory handshake** | ✅ | ✅ |
-| **Opcode width** | n/a (address byte) | **8-bit** | 8-bit + sub-opcode (16-bit group/op) | **16-bit** |
-| Register addressing | 8-bit address, 8-bit data | 16-bit address, 8-bit data | 32-bit address | **24-bit address, 32-bit data**, with read-modify-write |
-| Status on MISO | address echo | **1 status byte** | status word | **2 status bytes + 4 IrqStatus bytes, every command** |
-| IRQ status width | 8-bit (`IrqFlags`) | **16-bit** | 32-bit | **32-bit**, *plus a second FIFO-IRQ domain* |
-| Data buffer | **FIFO with paged access** | **one 256 B buffer**, `SetBufferBaseAddress` | one 256 B buffer | **two independent 256 B FIFOs** with thresholds, level readback, streaming > 256 B |
-| DIO pins | DIO0–DIO5, `DioMapping1/2` registers | DIO1–DIO3; **DIO2 = RF switch, DIO3 = TCXO by convention** | DIO5–DIO11 | **DIO5–DIO11, all fully general** |
-| RF-switch control | host GPIO | `SetDio2AsRfSwitchCtrl` — 1 pin, 2 states | `SetDioAsRfSwitch` | **`SetDioRfSwitchConfig`, any DIO, 5 states** (`tx_hf`,`rx_hf`,`tx_lf`,`rx_lf`,`standby`) |
-| TCXO | host-supplied | **`SetDio3AsTcxoCtrl`** — steals a DIO | `SetTcxoMode` | **`SetTcxoMode` → dedicated `VTCXO` pin** |
-| Reference | XTAL or TCXO | XTAL or TCXO | XTAL or TCXO | XTAL, TCXO, **or XTAL + on-chip NTC temperature compensation** |
-| Antenna-switch states needed | 2 | 2 | 4 (dual band) | 4 (dual band), **driven by the chip** |
-| Mandatory boot blob | ❌ | ❌ | ⚠ **firmware image, updatable** (`AN1200.57 LR11xx Program Memory Update`) | ✅ **PRAM patch, re-uploaded every cold start** |
-| Errata handling | datasheet notes | **4 register pokes** (`DS.SX1261-2` §15) | driver-applied | **PRAM + named workaround functions**, some needing retention-memory parking |
-
----
-
-## 3. What breaks, generation by generation
-
-### 3.1 Gen 1 → Gen 2: total register-model change
-
-The canonical break, and the one everyone has heard about.
-
-- **Register-mapped becomes command-based.** On an SX1276 you write `RegOpMode`; on an SX1262 you
-  issue `SetStandby(0x80)`. No address, no constant, no initialisation sequence survives.
-- **`BUSY` appears and is mandatory.** An SX127x driver has no concept of it. Ignore it on an
-  SX126x and you get silent command loss — the single most common Gen-2 bring-up failure, covered
-  at length in [`guides/lora` §5.2](../lora/README.md).
-- **`DIO2`/`DIO3` acquire hidden meanings.** `SetDio2AsRfSwitchCtrl` and `SetDio3AsTcxoCtrl` turn
-  two "GPIOs" into a switch driver and a regulator. Nothing analogous exists on Gen 1.
-- **`XOSC_START_ERR` is expected at power-on with a TCXO** and must not be treated as fatal.
-- **SF6 is not interoperable**, and SF5 arrives (Gen 2 only). **[DS20]** §23.8
-- **Intra-packet frequency hopping disappears.** A Gen-1 feature Gen 2 simply does not have.
-- Four **mandatory register workarounds** appear (`DS.SX1261-2` §15) with no Gen-1 equivalent.
-
-**Driver reality:** RadioLib keeps `SX127x` and `SX126x` as entirely separate modules; Semtech ships
-separate `sx126x_driver`; nothing is shared. **[RL]**
-
-### 3.2 Gen 2 → Gen 3: same shape, different command set
-
-The gentlest step, and the only one Semtech advertises as compatible.
-
-- The LR1110/1120/1121 product pages all claim ***"Fully compatible with SX1261/2/8 devices and the
-  LoRaWAN standard"*** **[PP]** — read that as **air-interface and LoRaWAN-profile** compatibility.
-  It is **not** a claim of pin or register compatibility, and the parts are not pin-compatible
-  (QFN32 5 × 5 vs QFN24 4 × 4).
-- **The command set is different.** RadioLib has a separate `LR11x0` module; Semtech ships `SWDR001`
-  as a separate driver from `sx126x_driver`. **[RL]**
-- **A firmware image enters the picture.** LR11xx carries updatable program memory —
-  `AN1200.57 LR11xx Program Memory Update` and the `SWTL001` "reference implementation of the LR11xx
-  firmware update procedure" exist for exactly this. A Gen-2 driver has no such concept.
-- **Long interleaver arrives** (Gen 3 and 4 only) — a LoRa PHY option a Gen-2 peer cannot decode.
-  **[DS20]** §23.8
-- **Package and pinout change**: QFN32 5 × 5, and the GNSS/Wi-Fi parts need an extra antenna path.
-
-**What you gain:** GNSS + Wi-Fi passive scanning (LR1110/LR1120), 2.4 GHz and satellite bands
-(LR1120/LR1121), and an **AES-128 crypto engine with secure key storage and DevEUI/JoinEUI/NwkKey/AppKey
-handling** — a genuine security-architecture change, not a checkbox.
-
-### 3.3 Gen 3/2 → Gen 4: the second big break
-
-**Verdict up front: SX126x → LR2021 is a break of the same magnitude as SX127x → SX126x, and
-migrating from Gen 3 is only slightly easier than from Gen 2.** The command *model* survives; its
-encoding, addressing, buffering and initialisation do not.
-
-Here is what your driver has to change, concretely. Sourced from **[DS20]** §5–§7, §22 and **[DRV]**.
-
-| # | Change | What you rewrite |
-|---|---|---|
-| 1 | **Opcodes go 8-bit → 16-bit** | Every opcode constant; the framing helper; the unit tests. `MOSI` is now `Op(15:8), Op(7:0), Arg0…` |
-| 2 | **Every command returns 6 status bytes**, not 1: `Stat(15:8), Stat(7:0), IrqStat(31:24)…IrqStat(7:0)` | Read helpers, offsets, and the "did that work?" path. Upside: you get IRQ state free with every transaction |
-| 3 | **Registers: 16-bit addr / 8-bit data → 24-bit addr / 32-bit data** (`WriteRegMem32 0x0104`, `ReadRegMem32 0x0106`, `WriteRegMemMask32 0x0105`) | The entire register layer, and every constant in it. Nothing ports |
-| 4 | **One shared 256 B buffer → two independent 256 B FIFOs** with high/low thresholds, level readback, explicit clear and overflow/underflow flags | The whole payload path. ⚠ And it is a **capability change**: >256 B payloads are now supported by streaming, which Gen 2 could not do at all |
-| 5 | **A second IRQ domain.** `ConfigFifoIrq`/`GetFifoIrqFlags`/`ClearFifoIrqFlags` are separate from `SetDioIrqConfig`/`ClearIrq`/`GetAndClearIrqStatus` | Your ISR. A "one IRQ register" model is now wrong |
-| 6 | **`SetDio2AsRfSwitchCtrl` → `SetDioRfSwitchConfig(Dio, tx_hf, rx_hf, tx_lf, rx_lf, standby)`** | Antenna-switch handling. A dual-band front end needs four states; the chip drives them, but you must describe them |
-| 7 | **`SetDio3AsTcxoCtrl` → `SetTcxoMode` on the dedicated `VTCXO` pin** | Clock bring-up, and one DIO handed back to you |
-| 8 | **⚠ A firmware Patch RAM (PRAM) must be uploaded at every cold start** and after every sleep-without-retention. Per-part images (`lr20xx_pram_load_pram_lr2021` vs `…_lr20x2`). Costs +80 nA retention current | **A new mandatory boot stage with no Gen-2 equivalent.** Skip it and the part *appears* to work while BLE Coded PHY, RTToF and sub-GHz SIMO sensitivity are all degraded |
-| 9 | **⚠ Retention-memory parking.** SX1276 compatibility mode, SX1276 hopping compatibility and the RTToF deviation fix are **lost across sleep-with-retention** unless explicitly stored in a retention slot | Your sleep/wake path. A brand-new bug class |
-| 10 | **SIMO supply topology.** `VDCC1`→`VDCC2` and `VPAX1`→`VPAX2` are **external PCB connections**; the buck feeds the PA as well as the core | **The board, not just the driver.** Also a new trade: Semtech's own driver docs say SIMO **costs sub-GHz sensitivity** for LoRa, FSK, FLRC, OOK and Z-Wave **[DRV]** |
-| 11 | **⚠ `SetPaConfig` can damage the part.** **[DS20]** §7.4.1 lists "PA damage" and "Regulatory non-compliance" among the consequences of wrong parameters; `pa_hf_duty_cycle` is restricted to 16–31 "to avoid risk of aging" | Take PA tables from `lr20xx_pa_pwr_cfg.h`, not from arithmetic. ⚠ The CN 490 MHz variant needs a **different** table from 868/915 **[DRV]** |
-| 12 | **DIO Rx/Tx hardware triggers**, where **`BUSY` is not raised** | Any `BUSY`-polling state machine written for Gen 2 reads this state wrong |
-| 13 | **No AES engine, no secure key store** (if coming from Gen 3) | Move LoRaWAN key handling to the MCU or an external secure element |
-| 14 | **`LoRaMac-node` has no Gen-4 support** and has not been pushed since 2024-07-03 | If that is your LoRaWAN stack, you are changing stack as well as driver — to LoRa Basics Modem / USP |
-
-**Corroboration from two independent implementations**, which is the strongest evidence that this
-is a real break rather than a documentation style change:
-
-- **Semtech** ships `lr20xx_driver` as a **new tree**, not a shim over `sx126x_driver` **[DRV]**.
-- **RadioLib** created a **new base class** for the LR2021 — commit
-  `d696fed842bc77c6699ac83d9611a7d6e1c838d6`, *"[LRxxxx] Create base class for common LR11xx and
-  LR20xx commands"*, 2025-10-13 **[RL]**. Note what it shares with: **LR11xx**, not SX126x.
-- **Meshtastic** likewise added `LR20x0Interface` *"based on the LR11x0 and LR1110"* — PR #10401
-  body, 2026-05-06 **[MT]**.
-
-**All three chose Gen 3 as the ancestor. None of them could reuse Gen 2.**
-
-### 3.4 The reassuring half: the air interface is compatible
-
-**[DS20]** §23.8:
-
-> LoRa radios across the different generations can communicate with each other when properly
-> configured with identical parameters (frequency, spreading factor, bandwidth, and coding rate).
-> … Note that **all the LoRaWAN configurations are fully compatible between all four generations**.
-
-The exceptions, in full:
-
-| Feature | Gen 1 | Gen 2 | Gen 3 | Gen 4 | Practical effect |
-|---|:--:|:--:|:--:|:--:|---|
-| **SF5** | ❌ | ✅ | ✅ | ✅ | An SF5 network excludes Gen 1 |
-| **SF6** | ⚠ | ⚠ | ⚠ | ⚠ | *"requires additional configuration for backwards compatibility"*. Gen 4 has `SetLoraSF6Compat` and driver `lr20xx_workarounds_lora_*_sx1276_compatibility_mode` |
-| **Long interleaver** | ❌ | ❌ | ✅ | ✅ | Gen 3/4 only; invisible to Gen 1/2 peers |
-| **Intra-packet hopping** | ✅ | ❌ | ❌ | ✅ | Skipped two generations and came back |
-| **Multi-SF CAD / Fast CAD** | ❌ | ❌ | ❌ | ✅ | Receiver-side; does not break peers |
-| **Convolutional CR8/CR9** | ❌ | ❌ | ❌ | ✅ | Gen-4-only coding rates — turning these on splits your mesh |
-
-**So an LR2021 drops into an existing SX1262 Meshtastic or LoRaWAN network and works — provided you
-do not enable anything that makes it worth having.** That is the central tension of this migration,
-and it is worth saying out loud before anyone budgets for it.
-
----
-
-## 4. Generation notes
-
-### 4.1 Gen 1 — SX1272/SX1276 (2013)
-
-Two sub-families, and **they are not the same silicon**: SX1272/73 cover **860–1020 MHz** with a
-157 dB link budget and −137 dBm sensitivity; SX1276/77/78/79 cover **137–1020 MHz** with a 168 dB
-budget and −148 dBm. **[PP]** Register-mapped, QFN28, no `BUSY`, `+20 dBm` PA, RX 9.9 mA (SX1276) /
-10 mA (SX1272), packet engine to 256 bytes, 61 Hz synthesiser resolution, built-in temperature
-sensor and low-battery indicator. Both are still orderable and both still ship in vast quantity as
-`RFM95`-class modules. Record: [`components/semtech/sx1276`](../../components/semtech/sx1276/README.md).
-
-### 4.2 Gen 2 — SX1261/62/68, LLCC68, SX1280 (2017–2018)
-
-The generation every board in this knowledge base actually has. The step change is **receive
-current**: 9.9 mA → **4.6 mA**, achieved with an integrated DC-DC. ⚠ **That DC-DC does not help
-transmit on an SX1262** — its PA is fed from `VBAT`, which is exactly the constraint the LR2021's
-SIMO removes ([SX1262 record](../../components/semtech/sx1262/README.md) and §5.2 below).
-
-Within the generation, four parts that are easy to confuse and are documented separately here:
-[SX1262](../../components/semtech/sx1262/README.md) (+22 dBm, 150–960 MHz),
-[SX1268](../../components/semtech/sx1268/README.md) (+22 dBm, **410–810 MHz** for Chinese bands),
-[LLCC68](../../components/semtech/llcc68/README.md) (**restricted SF/BW combinations** — a genuine
-substitution trap), and SX1261 (+15 dBm, PA from `VREG`, DC-DC covers the whole IC).
-**SX1280/SX1281** sit in the same generation at 2.4 GHz with FLRC and a ranging engine.
-
-### 4.3 Gen 3 — LoRa Edge, LR1110/LR1120/LR1121 (2020–)
-
-Semtech's own summary is *"Added geolocation"*, and the family is best understood as three points on
-a scanner spectrum. **[PP]**
-
-| | **LR1110** | **LR1120** | **LR1121** |
-|---|---|---|---|
-| Sub-GHz 150–960 MHz | ✅ | ✅ | ✅ |
-| 2.4 GHz ISM | ❌ | ✅ | ✅ |
-| Satellite bands | ❌ | 1.9–2.1 GHz S-band | **2 GHz S-band + 1.55 GHz L-band** |
-| **GNSS (GPS/BeiDou) scanning** | ✅ | ✅ | ❌ |
-| **Wi-Fi passive AP-MAC scanning** | ✅ | ✅ | ❌ |
-| **AES-128 crypto + key store** | ✅ | ✅ | ✅ |
-| Synthesiser range | **150–2700 MHz continuous** | — | — |
-| Semtech catalogue family | LoRa Edge | LoRa Edge | **LoRa Connect** |
-| Order code | `LR1110IMLTRT` | `LR1120IMLRT` ⚠ | `LR1121IMLTRT` |
-
-⚠ **`LR1120IMLRT` on Semtech's own page is missing the `T`** that `LR1110IMLTRT` and `LR1121IMLTRT`
-both carry. Almost certainly a typo on the product page, but **do not order from this table** —
-confirm against the datasheet or the distributor. Recorded because it is exactly the kind of thing
-that gets copied. **[PP]**, `unresolved`.
-
-The crypto engine is the under-appreciated part: hardware AES-128, DevEUI/JoinEUI handling, and
-storage of `NwkKey`/`AppKey` "against unauthorized access". **Gen 4 drops all of it.** If you chose
-Gen 3 for that, Gen 4 is a step backwards and you should say so in your migration paperwork.
-Records: [`lr1121`](../../components/semtech/lr1121/README.md),
-[`lr11x0`](../../components/semtech/lr11x0/README.md).
-
-### 4.4 Gen 4 — LoRa Plus, LR2021/LR2022/LR2012 (2025–)
-
-Full dossier: [`components/semtech/lr2021`](../../components/semtech/lr2021/README.md). The
-three-part split, since one datasheet covers all three and mixing them up is the standard error:
-
-| | **LR2021** | **LR2022** | **LR2012** |
-|---|---|---|---|
-| Sub-GHz + HF (1.5–2.5 GHz) | ✅ + ✅ | ✅ + ✅ | ✅ + ❌ (`RFI_HF`/`RFO_HF` are NC) |
-| FLRC · O-QPSK · Z-Wave | ✅ | ❌ | ❌ |
-| Bluetooth LE PHY | ✅ | ✅ | ❌ |
-| LoRa · LR-FHSS · (G)FSK · OOK · BPSK · WM-Bus · Wi-SUN | ✅ | ✅ | ✅ |
-
-⚠ **No LR2022 or LR2012 silicon, module or firmware was found in the wild** as of 2026-09-04.
-Every product located — Waveshare `Core2021`, Seeed `Wio-LR2021`, NiceRF `LoRa2021F33-2G4`, Seeed
-MeshTracker X1, Meshnology W12 — uses the **LR2021**. Negative result.
-
----
-
-## 5. Three cross-generation themes worth understanding
-
-### 5.1 The reference clock, and how the TCXO requirement melted away
-
-| Gen | Situation |
-|---|---|
-| 1 | XTAL is fine for most work; sensitivity is high but frequency tolerance is the designer's problem |
-| 2 | ⚠ TCXO effectively required at high SF, and it is bolted on by **stealing `DIO3` as its power supply**. `XOSC_START_ERR` at power-on is normal and must be ignored |
-| 3 | `SetTcxoMode`; the DIO-stealing hack is gone |
-| 4 | **`VTCXO` is a dedicated pin.** More importantly: *"Increased frequency offset tolerance obviating TCXO and large thermal relief"* **[PP]**, plus an **on-chip NTC temperature-compensation path** that measures crystal temperature and corrects for it — explicitly aimed at PA self-heating on small boards **[DS20]** §1.9.2 |
-
-**This is a real BOM and power win, not marketing.** A TCXO is a part, a footprint, and 1.5–4 mA
-whenever the radio is awake. Gen 4 lets a well-designed board delete it — and a community poster
-planning a TDMA schedule was already relying on it in mid-2026: *"You can rely on the crystal
-oscillator of the LR2021, which should be less than ±30 ppm, which can also be improved with the API
-`set_xosc_trim`"* **[COM]**.
-
-⚠ Meshtastic's Gen-4 variants still carry `LR2021_DIO3_TCXO_VOLTAGE` **[MT]** — a constant name
-inherited from RadioLib's SX126x API. It does **not** mean DIO3 supplies the TCXO on this part.
-
-### 5.2 Transmit efficiency is a supply-topology story
-
-| Gen | Regulator | PA supply | Tx @ max |
-|---|---|---|---|
-| 1 | LDO only | `VBAT` | ~120 mA @ +20 dBm |
-| 2 (SX1262) | LDO **or** DC-DC | ⚠ **`VBAT` — the DC-DC covers the core only** | **118 mA @ +22 dBm** |
-| 2 (SX1261) | LDO or DC-DC | `VREG` — DC-DC covers the whole IC | 25.5 mA @ +14 dBm |
-| 4 (LR2021) | **SIMO buck** or LDO | **`VPAX` from the SIMO** | **105 mA @ +22 dBm** |
-
-**~11 % less transmit current at the same output power, from supply topology alone.** For a
-duty-cycled node whose energy budget is dominated by transmit bursts, that is the most directly
-useful number in this whole guide.
-
-⚠ **But SIMO is not free.** Semtech's own driver documentation says the SIMO converter *"may
-negatively impact RF sensitivity for sub-GHz operations"* for FSK, FLRC, OOK, LoRa **and** Z-Wave
-**[DRV]**, and **[DS20]** §23.1–23.2 adds a further degradation for SIMO under a metallic RF shield.
-The datasheet's electrical tables are specified *"no shield, SIMO"*. **The current-versus-sensitivity
-trade is a live design decision on Gen 4 in a way it was not on Gen 2.**
-
-### 5.3 Security went backwards
-
-| Gen | AES-128 engine | Secure key storage | DevEUI/JoinEUI handling |
-|---|:--:|:--:|:--:|
-| 1 | ❌ | ❌ | ❌ |
-| 2 | ❌ | ❌ | ❌ |
-| **3** | **✅** | **✅** | **✅** |
-| **4** | **❌** | **❌** | **❌** |
-
-Evidence for the Gen-4 row is a **negative result and worth stating as such**: the string `AES` does
-not appear anywhere in the 243-page **[DS20]**; there is no crypto section in the table of contents;
-and the only crypto-adjacent sentence is a *warning* that `GetRandomNumber` *"should not be used for
-cryptographic purposes"* (§6.6.2). Independently, Waveshare's own `Core2021` vs `Core1121`
-comparison table marks AES-128 and secure key storage as present on the LR1121 and absent on the
-LR2021 **[3P]**.
-
-**If your LoRaWAN root keys currently live in an LR11xx, Gen 4 has nowhere to put them.** Plan for
-MCU-side storage or an external secure element, and price that in.
-
----
-
-## 6. Software support across the lineage
-
-| Stack | Gen 1 | Gen 2 | Gen 3 | Gen 4 | Note |
-|---|:--:|:--:|:--:|:--:|---|
-| **RadioLib** (MIT) | ✅ `SX127x` | ✅ `SX126x`, `LLCC68`, `SX128x`, `STM32WLx` | ✅ `LR11x0` | ✅ **`LR2021`, from release 7.6.0 (2026-02-19)** | Four separate modules; the LR2021 shares a base class with LR11x0 |
-| **Semtech driver** | in `LoRaMac-node` | `sx126x_driver`, `llcc68_driver` (BSD-3-Clause-Clear) | `SWDR001` | ⚠ **no standalone repo** — `lr20xx_driver` lives inside `LoRa-Net/usp` | Every other generation has a standalone driver |
-| **LoRa Basics Modem** (`SWL2001`) | ❌ | ✅ | ✅ | ✅ bundled as 4.9.0 inside USP | The current LoRaWAN path |
-| **USP** (Unified Software Platform) | ❌ | ✅ "buildable" | ✅ "buildable" | ✅ **"validated"** | ⚠ *"not intended for production use"* at v1.1.2 |
-| **LoRaMac-node** | ✅ | ✅ | ✅ | ❌ | ⚠ **last push 2024-07-03**; predates Gen 4 |
-| **Meshtastic** | ✅ `RF95_RADIO` | ✅ `SX1262/1268/LLCC68/SX1280`, `STM32WLx` | ✅ `LR1110/1120/1121` | ✅ `LR2021_RADIO` — **2.8.x only, not in v2.7.26** | `LoRaRadioType` enum, read 2026-09-04 |
-| **Zephyr** | — | ✅ | ✅ | ✅ via `usp_zephyr` | Not evaluated here |
-| **Linux kernel** | ❌ | ❌ | ❌ | ❌ | **No in-tree driver for any Semtech LoRa transceiver.** Everything is userspace SPI (USP on Linux, Meshtastic Portduino). Negative result, 2026-09-04 |
-
-**The single most useful software fact for a migration plan:** RadioLib 7.5.0 (2026-01-10) has
-nothing; **7.6.0 (2026-02-19) is the floor**. And Meshtastic's stable 2.7 line has nothing —
-LR2021 is a 2.8 feature.
-
----
-
-## 7. Dating the generations — and where the dates are soft
-
-| Gen | Date | Evidence strength |
-|---|---|---|
-| **1** | **2013** | **Strong.** **[DS20]** §23.8 states it; independently, the earliest Wayback capture of `semtech.com/images/datasheet/sx1272.pdf` is **2013-05-10** and of `sx1276.pdf` **2013-05-01** **[WB]** |
-| **2** | SX1280 **2017**, SX1261/62 **2018** | ⚠ **Moderate.** Semtech gives no date in §23.8. Earliest Wayback captures: `sx1280-1.pdf` **2017-03-29**, `DS_SX1261-2_V1.1.pdf` **2019-01-08** **[WB]**. A first-capture date is a *latest-possible* introduction date, not the announcement. `inferred` |
-| **3** | LR1110 **2020** | ⚠ **Weak in this pass.** No Semtech-dated source was retrieved; no LR11xx PDF exists in the Wayback index for `semtech.com`. **Not established here** — treat "2020" as the commonly-repeated figure, `unresolved` |
-| **4** | Announced **2025-03-12**; datasheet Rev 0.2 **June 2025**; Rev 1.1 **Oct 2025**; Rev 2.1 **Apr 2026**; Rev 2.2 **2026-08-08** | **Strong.** The revision history is in **[DS20]**; the announcement date is fixed by the official Meshtastic account's post **[COM]** and by RadioLib issue #1457, opened **2025-03-13** — the next day |
-
-⚠ **Gen 2 and Gen 3 introduction dates are the weakest claims in this guide.** They are marked
-`inferred`/`unresolved` rather than dressed up. What would settle them: a Semtech press release, or
-a datasheet Rev 1.0 with a printed date — neither of which was obtainable through the document gate
-described in [`vendors/semtech/README.md`](../../vendors/semtech/README.md).
-
----
-
-## 8. Which generation should you actually use?
-
-| Situation | Choose | Why |
-|---|---|---|
-| **New plain sub-GHz LoRa or LoRaWAN node, cost matters** | **Gen 2 — SX1262** | Mature, cheap, ubiquitous, best-documented part in this library. Gen 4 buys you nothing if you only run stock LoRa |
-| **433 MHz or Chinese 470 MHz** | Gen 2 — **SX1268** | 410–810 MHz |
-| **High volume, restricted SF/BW acceptable** | Gen 2 — **LLCC68** | ⚠ Read the [substitution trap](../../components/semtech/llcc68/README.md) first |
-| **2.4 GHz only, FLRC, bulk transfer** | Gen 2 — **SX1280** | Cheaper and far better supported than Gen 4 for this specific job — a recommendation made repeatedly by experienced posters **[COM]** |
-| **Asset tracking, "where is it" beats "how far"** | Gen 3 — **LR1110/LR1120** | GNSS + Wi-Fi scanning. Nothing in Gen 4 replaces this |
-| **LoRaWAN with keys that must not leave the radio** | Gen 3 — **LR1121** | The crypto engine and key store. **Gen 4 has neither** |
-| **Dual-band single-SKU, one antenna path, no external RF switch** | **Gen 4 — LR2021** | The multi-region front end is the actual BOM argument |
-| **You need >125 kbps over ISM** | **Gen 4 — LR2021** (or Gen 2 SX1280 at 2.4 GHz) | FLRC. ⚠ Expect ~50 % of nominal after framing and FEC **[COM]** |
-| **Mesh efficiency: asymmetric links, better CAD** | **Gen 4 — LR2021** | Multi-SF receive is the standout, and is Gen-4-only |
-| **Deleting the TCXO matters** | **Gen 4** | §5.1 |
-| **A PHY the SX126x cannot make at all** — Z-Wave, BLE, 802.15.4, Sigfox BPSK | **Gen 4** | Dedicated packet handlers, ⚠ third-party stacks required |
-| **Interoperating with an existing Gen-1 deployment** | Gen 1 — **SX127x** | Or Gen 4 with its SX1276 compatibility modes, which is now a genuine third option |
-
-**And the honest caution.** Gen 4 is ~18 months old. Its reference driver says *"not intended for
-production use"*; RadioLib support is ~7 months old and was still receiving datasheet-conformance
-fixes in August 2026; Meshtastic support is not in a stable release; and **no independent,
-method-stated sensitivity or range comparison against an SX1262 exists anywhere this pass could
-find** ([community survey](../../components/semtech/lr2021/projects-and-community.md)). Every
-performance advantage claimed above is a Semtech specification. That is not a reason to avoid the
-part — it is a reason to prototype before committing a BOM.
-
----
-
-## 9. Sources
-
-| ID | Title | Publisher | Class | Medium | URL / path | Retrieved | Version / date | Establishes |
-|---|---|---|---|---|---|---|---|---|
-| G-1 | LR2021/LR2022/LR2012 Datasheet | Semtech, via Digi-Key | authorized mirror | datasheet | [`components/semtech/lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf`](../../components/semtech/lr2021/artifacts/lr20xx-datasheet-v2.1-digikey-mirror.pdf) | 2026-09-04 | **`DS.LR20xx` Rev 2.1, 13/04/26** | **§0 — the generation list (§23.8)**; §2, §3.3, §5 |
-| G-2 | LR2021 Datasheet Rev 1.1 | Semtech, via Mouser | authorized mirror | datasheet | [archived](../../components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md) | 2026-09-04 | `DS.LR2021` Rev 1.1, 10/14/25 | §0 — independent corroboration of §23.8 |
-| G-3 | SX1276/77/78/79 Datasheet | Semtech, via Wayback | credible mirror | datasheet | [`components/semtech/sx1276/artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf`](../../components/semtech/sx1276/artifacts/sx1276-77-78-79-datasheet-v5-wayback.pdf) | 2026-09-04 | **Rev. 5, August 2016** | §2, §4.1 |
-| G-4 | Product pages: LR2021, LR1121, LR1110, LR1120, SX1276, SX1272, SX1262, SX1268, LLCC68, SX1280 | Semtech | primary | vendor page | `www.semtech.com/products/wireless-rf/{lora-plus,lora-connect,lora-edge}/…` | 2026-09-04 | undated | §1, §2, §4 |
-| G-5 | Product sitemap | Semtech | primary | sitemap | `www.semtech.com/sitemap-products.xml` | 2026-09-04 | — | §1 — the only complete family enumeration |
-| G-6 | `lr20xx_driver` v2.0.2 in `LoRa-Net/usp` | Semtech | primary | source | @ `512a095e303872f900021361a619b7b1e6e29469`; [snapshot](../../components/semtech/lr2021/artifacts/usp-lr20xx_driver-v2.0.2-512a095.tar.gz) | 2026-09-04 | driver v2.0.2, 2026-04-07; BSD-3-Clause-Clear | §3.3, §5.2, §6 |
-| G-7 | RadioLib | jgromes | community | source | `github.com/jgromes/RadioLib` | 2026-09-04 | LR2021 first in **7.6.0**, 2026-02-19 | §3.1, §3.3, §6 |
-| G-8 | Meshtastic firmware | Meshtastic | community | source | `github.com/meshtastic/firmware` | 2026-09-04 | PR #10401 merged 2026-05-08 | §3.3, §5.1, §6 |
-| G-9 | `Core2021-XF` product page and comparison table | Waveshare | primary | store listing | `www.waveshare.com/Core2021-XF.htm` | 2026-09-04 | — | §0, §5.3 |
-| G-10 | Wayback CDX index for `semtech.com` PDFs (6 000 rows) | Internet Archive | archive | index | `web.archive.org/cdx/search/cdx?url=semtech.com/*&matchType=domain&filter=mimetype:application/pdf` | 2026-09-04 | captures 2011–2019 | §7 — **and a negative result: zero LR11xx or LR20xx PDFs are indexed under `semtech.com`** |
-| G-11 | Community corpus | various | community | forum | catalogued in [`lr2021/projects-and-community.md`](../../components/semtech/lr2021/projects-and-community.md) | 2026-09-04 | 2025-03-12 … 2026-09-02 | §7 announcement date; §8 caution |
-| G-12 | SX1262 component record | this repository | derived | record | [`components/semtech/sx1262/README.md`](../../components/semtech/sx1262/README.md) | 2026-09-04 | — | Gen-2 rows in §2 and §5.2 |
diff --git a/guides/hardware/parallel-8080-lcd-buses.md b/guides/hardware/parallel-8080-lcd-buses.md
deleted file mode 100644
index 9954709..0000000
--- a/guides/hardware/parallel-8080-lcd-buses.md
+++ /dev/null
@@ -1,196 +0,0 @@
-# Parallel Intel-8080 LCD buses on ESP32 — and why your display library matters more than your board
-
-> Device-independent guide. Written 2026-09-07 while documenting the
-> [LilyGO T-Display-S3 family](../../devices/lilygo/t-display-s3-shared/README.md), which
-> contains boards using **all three** of the buses compared here, and is therefore an unusually
-> good worked example.
->
-> Companion to [`display-interfaces.md`](display-interfaces.md), which covers the interface
-> landscape generally (SPI, QSPI, RGB/parallel, MIPI-DSI, e-paper). **This page is narrower:**
-> it is about the *software* consequences of picking a bus, and specifically about the
-> `TFT_eSPI` / `Arduino_GFX` / `LovyanGFX` decision that trips people up.
-
-## 1. The three buses, and what each costs you in software
-
-"Parallel" is ambiguous in this space and the ambiguity causes real errors. Three distinct
-things get called it:
-
-| Bus | Also called | Wires (typical) | What the controller receives | ESP32 peripheral used |
-|---|---|---|---|---|
-| **Intel 8080 (i80), 8-bit** | MCU parallel, DBI Type B, "8080-8" | `D0..D7`, `WR`, `RD`, `DC`, `CS`, `RST` = 13 | commands **and** pixels, byte at a time, strobed by `WR` | ESP32-S3 **LCD_CAM** peripheral, or bit-banged GPIO |
-| **RGB parallel** | DPI, "RGB666/565" | `R0..5,G0..5,B0..5`, `PCLK`, `HSYNC`, `VSYNC`, `DE` ≈ 22 | a **continuous video signal**; there is no GRAM in the controller | ESP32-S3 LCD_CAM in RGB mode + PSRAM framebuffer |
-| **QSPI (DSPI/QSPI DBI)** | "4-line SPI", quad-SPI display | `CS`, `CLK`, `D0..D3` = 6 | commands and pixels in a `0x02`/`0x32`-framed protocol | generic SPI peripheral in quad mode |
-
-The T-Display-S3 family uses the **first and third**, plus plain 4-wire SPI on the Pro. It uses
-no RGB-parallel panel at all. If you take away one thing: **8080 and RGB are not the same
-thing, and a library that supports one may not support the other.**
-
-## 2. Why 8080 is fast, and why that is not free
-
-An ST7789V on an 8-bit 8080 bus moves one byte per `WR` strobe, so an RGB565 pixel takes two
-strobes. At LilyGO's chosen 16 MHz pixel clock that is nominally ~8 M pixel/s — a 170 × 320
-full-screen redraw in roughly 7 ms of bus time, against ~35 ms for the same panel on a 40 MHz
-1-bit SPI link. That gap is the entire reason to accept a 13-wire bus.
-
-What it costs:
-
-- **Thirteen GPIOs.** On a board whose SoC already loses GPIO26–37 to in-package octal PSRAM,
-  that is most of the pin budget. This is why the T-Display-S3 has so few free pins for a
-  45-GPIO part.
-- **No read-back in practice.** `RD` is wired but essentially unused; most drivers never read
-  the controller.
-- **A hard dependency on the ESP32-S3's LCD_CAM peripheral** for the fast path. On plain
-  ESP32 (no LCD_CAM) an 8080 bus must be bit-banged, which is why 8-bit parallel boards are an
-  S3-era phenomenon.
-- **Pixel-clock sensitivity.** LilyGO's own header carries the comment
-  *"Too low or too high pixel clock may cause screen mosaic"* beside
-  `#define EXAMPLE_LCD_PIXEL_CLOCK_HZ (16 * 1000 * 1000)`. ESPHome independently chose
-  **10 MHz** for the same board. Neither is wrong; the panel FPC and the bonded flex set the
-  real limit, and it varies between production runs of nominally identical boards.
-
-## 3. The library decision
-
-This is the part that costs people evenings.
-
-| Library | 8080 8-bit | QSPI | 4-wire SPI | RGB | Configured by |
-|---|---|---|---|---|---|
-| **`TFT_eSPI`** (Bodmer) | **yes**, via `TFT_PARALLEL_8_BIT` | **no** | yes | no | editing a header **inside the installed library** |
-| **`Arduino_GFX`** (moononournation) | **yes**, `Arduino_ESP32LCD8` | **yes**, `Arduino_ESP32QSPI` | yes | yes | constructor arguments in your sketch |
-| **`LovyanGFX`** (lovyan03) | **yes** | yes | yes | yes | a C++ config class in your sketch |
-| **ESP-IDF `esp_lcd`** | **yes**, `esp_lcd_new_panel_io_i80()` | yes | yes | yes | struct initialisers |
-| **ESPHome `mipi_spi`** | **yes** (`bus_mode: octal`) | yes (`quad`) | yes | — | YAML, with a named board model |
-
-### `TFT_eSPI`: fast, ubiquitous, and configured in the worst possible place
-
-`TFT_eSPI` does not take pin assignments as constructor arguments. It reads them from
-`User_Setup.h` / `User_Setups/SetupNNN_*.h`, selected by editing
-**`User_Setup_Select.h` inside the library installation directory**. That single design
-decision produces a specific, extremely repetitive failure:
-
-> **Symptom:** the sketch compiles and uploads, and the screen stays black — or shows garbage,
-> or half a screen of noise.
-> **Cause:** the library was updated (or reinstalled, or the IDE did it for you) and your edit
-> to `User_Setup_Select.h` was overwritten.
-
-For the LilyGO T-Display-S3 the required edit is:
-
-```c
-// TFT_eSPI/User_Setup_Select.h
-//#include <User_Setup.h>                                   // <- comment this out
-#include <User_Setups/Setup206_LilyGo_T_Display_S3.h>        // <- uncomment this
-```
-
-Newer `TFT_eSPI` refuses to build silently and emits
-`#error "Error! Please make sure <User_Setups/Setup206_LilyGo_T_Display_S3.h> is selected in <TFT_eSPI/User_Setup_Select.h>"`
-— which is an improvement, and is exactly what
-[LilyGO issue #326](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/326) (2026-02-23,
-11 comments) is about.
-
-Two further `TFT_eSPI` facts worth knowing before you choose it:
-
-- **It has no QSPI transport at all.** On the AMOLED boards, LilyGO's "TFT_eSPI examples" are
-  really `TFT_eSPI` **Sprites** (off-screen buffers) that a vendor QSPI routine pushes to the
-  panel. You get TFT_eSPI's drawing API and none of its display driver. Do not expect
-  `tft.init()` to talk to an RM67162.
-- **It is version-coupled to the Arduino core.** LilyGO's README, dated 2024-08-02: *"As of
-  2024/08/02, TFT_eSPI does not work on versions higher than 2.0.14"*, citing
-  [TFT_eSPI#3329](https://github.com/Bodmer/TFT_eSPI/issues/3329).
-
-**The diagnostic that separates hardware faults from configuration faults**, and LilyGO's own
-recommended first move: run an `Arduino_GFX` example. It needs no library-internal
-configuration, so if `Arduino_GFX` draws and `TFT_eSPI` does not, the board is fine and
-`User_Setup_Select.h` is not.
-
-### `Arduino_GFX`: configuration lives in your sketch
-
-```cpp
-// 8-bit 8080, LilyGO T-Display-S3 pin assignment
-Arduino_DataBus *bus = new Arduino_ESP32LCD8(
-    7 /* DC */, 6 /* CS */, 8 /* WR */, 9 /* RD */,
-    39, 40, 41, 42, 45, 46, 47, 48 /* D0..D7 */);
-Arduino_GFX *gfx = new Arduino_ST7789(bus, 5 /* RST */, 0 /* rotation */,
-                                      true /* IPS */, 170, 320, 35, 0, 35, 0);
-```
-
-The two trailing `35`s are the **column offset** into the ST7789's 240-wide GRAM. A 170-pixel
-panel on a 240-wide controller must be offset, or the image sits 35 columns to the left with a
-band of garbage. `TFT_eSPI` does the same thing through `#define CGRAM_OFFSET`; ESPHome calls
-it `offset_width: 35`. **Three libraries, three names, one hardware fact** — and the single
-most common "half the display shows garbage" cause
-([LilyGO issue #128](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/128)).
-
-Because everything is a constructor argument, `Arduino_GFX` survives library updates. Its
-drawing API is smaller than `TFT_eSPI`'s and its font handling is less pleasant; that is the
-trade.
-
-### `LovyanGFX`: the compromise
-
-Config lives in your project as a `lgfx::LGFX_Device` subclass, so it survives updates, and it
-supports every bus here including QSPI and RGB. It has `TFT_eSPI`-compatible API shims. It is
-the right default for a project that must run on more than one of these boards. The cost is a
-noticeably steeper first hour — you write ~40 lines of config class before you draw a pixel.
-
-### ESPHome: none of the above, and it already knows your board
-
-Since the `mipi_spi` component landed, ESPHome carries **named models** with pins and offsets
-baked in. From `esphome/components/mipi_spi/models/lilygo.py` (`dev`, fetched 2026-09-07):
-
-```python
-ST7789V.extend(
-    "T-DISPLAY-S3",
-    height=320, width=170,
-    offset_width=35,
-    color_order=MODE_BGR, invert_colors=True,
-    dc_pin=7, cs_pin=6, reset_pin=5,
-    enable_pin=[9, 15],
-    data_rate="10MHz",
-    bus_mode=TYPE_OCTAL,
-    requires={"psram"},
-)
-```
-
-Note `enable_pin=[9, 15]` — ESPHome drives both `LCD_RD` **and the board's GPIO15 power gate**
-as enables. That is the kind of board-specific knowledge a named model buys you, and the reason
-ESPHome "just works" on this board where a hand-written `st7789v:` block usually does not.
-
-## 4. Recommendation by bus
-
-| You have | Use | Second choice | Avoid |
-|---|---|---|---|
-| 8-bit 8080 (T-Display-S3, T-Display-S3 Touch) | **`TFT_eSPI` + `Setup206`** if you want the richest 2D API and are on core ≤ 2.0.14 | **`Arduino_GFX`** if you are on core 3.x, or want config in your sketch | hand-rolled `esp_lcd` unless you need DMA control |
-| QSPI AMOLED (all T-Display-S3 AMOLED, T4-S3, Lite) | **LilyGO's `LilyGo-AMOLED-Series`** — it wraps the panel init tables you would otherwise have to transcribe from the RM67162/RM690B0 datasheets | `Arduino_GFX` `Arduino_ESP32QSPI` | `TFT_eSPI` as a *driver* — it cannot do it |
-| QSPI with integrated touch (T-Display-S3 Long, AXS15231B) | `Arduino_GFX` + the vendor's AXS15231B init | LovyanGFX | anything that assumes a separate touch chip |
-| 4-wire SPI (T-Display-S3 Pro, ST7796S) | `Arduino_GFX` (LilyGO's choice) | `TFT_eSPI` | — |
-| Any of the above, in Home Assistant | **ESPHome `mipi_spi` with the named model** | — | writing pins by hand |
-| One codebase across several of them | **LovyanGFX** | ESP-IDF `esp_lcd` | `TFT_eSPI` |
-
-## 5. Debugging checklist for a black screen on an 8080 board
-
-In the order that resolves the most cases first:
-
-1. **Is the panel powered?** Many boards gate the panel rail behind a GPIO — GPIO15 on the
-   T-Display-S3. A backlight that is on proves the *backlight* rail, not the panel rail.
-2. **Is the backlight on?** Separate pin (GPIO38 here), separate driver chip.
-3. **Run an `Arduino_GFX` example.** If it works, your problem is `User_Setup_Select.h`.
-4. **Check the column/row offset** if you get an image but it is shifted or has a garbage band.
-5. **Halve the pixel clock.** Mosaic, tearing and speckle on an otherwise-correct image is
-   almost always the bus running faster than the flex will carry.
-6. **Check `PSRAM = OPI`** if you are using a full-screen framebuffer and it crashes rather
-   than draws.
-7. **Only then** suspect hardware.
-
-## 6. Boards in this repository using each bus
-
-| Bus | Boards documented here |
-|---|---|
-| 8-bit 8080 | [LilyGO T-Display-S3](../../devices/lilygo/t-display-s3/README.md), [T-Display-S3 Touch](../../devices/lilygo/t-display-s3-touch/README.md) |
-| QSPI | [T-Display-S3 AMOLED](../../devices/lilygo/t-display-s3-amoled/README.md), [AMOLED Plus](../../devices/lilygo/t-display-s3-amoled-plus/README.md), [1.64″](../../devices/lilygo/t-display-s3-amoled-1-64/README.md), [1.43/1.75″](../../devices/lilygo/t-display-s3-amoled-1-43-1-75/README.md), [T4-S3](../../devices/lilygo/t4-s3/README.md), [AMOLED Lite](../../devices/lilygo/t-display-amoled-lite/README.md), [T-Display-S3 Long](../../devices/lilygo/t-display-s3-long/README.md) |
-| 4-wire SPI | [T-Display-S3 Pro](../../devices/lilygo/t-display-s3-pro/README.md) |
-| MIPI-DSI | [Waveshare ESP32-P4-WIFI6-Touch-LCD-XC](../../devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md) |
-
-## See also
-
-- [`display-interfaces.md`](display-interfaces.md) — the broader interface landscape
-- [`e-paper-displays.md`](e-paper-displays.md)
-- [`components/sitronix/st7789v`](../../components/sitronix/st7789v/README.md) — the controller
-  behind the 8080 examples above
diff --git a/guides/hardware/soc-choice-for-battery-eink-devices.md b/guides/hardware/soc-choice-for-battery-eink-devices.md
deleted file mode 100644
index 2f2645b..0000000
--- a/guides/hardware/soc-choice-for-battery-eink-devices.md
+++ /dev/null
@@ -1,342 +0,0 @@
-# SoC choice for a battery-powered e-ink device
-
-> Why the devices in this repository pick what they pick — **ESP32-C3 vs ESP32-S3
-> vs ESP32-P4 vs Kendryte K230 vs nRF52840/nRF9151** — and what each choice costs
-> in memory, sleep current, radio complexity, toolchain effort and price.
->
-> **Every number below is cited to a record already in this repository. Nothing was
-> retrieved, measured or benchmarked for this page.** Where a figure does not exist
-> here, it is marked **`no figure in this repository`** rather than filled in from
-> memory. §2 is a list of those gaps and it is longer than anyone would like.
-
-## 0. The short answer
-
-| If your device is… | Pick | Because |
-|---|---|---|
-| A **1-bit e-ink reader** that must be cheap and small | **ESP32-C3** | 400 KB SRAM holds a 1 bpp 800×480 plane with room to spare, and the radio is integrated. **But it will be the thing that limits your firmware** |
-| An e-ink reader with **greyscale, partial refresh, a big font set or a large library index** | **ESP32-S3 with PSRAM (`R8`)** | 8 MB in-package PSRAM is the difference between multi-buffer rendering and not. This is the default choice, and the one four of the six documented e-ink devices made |
-| A **colour GUI handheld** with a camera or a DSI panel | **ESP32-P4** | 16–32 MB PSRAM, MIPI-DSI/CSI, a pixel-processing accelerator — **and no radio at all**, so budget a companion chip |
-| A device that must run **Linux, Python, SSH** or a neural network | **Kendryte K230** | 1 GB LPDDR4, an NPU, H.265 encode *and* decode. And **no radio, no Ethernet MAC, and nothing from the ESP32 ecosystem applies** |
-| A **BLE companion** or a **cellular/GNSS** link | **nRF52840 / nRF9151** | In this repository both appear only as companions to a bigger SoC, never as the application processor |
-
-**The single most consequential decision is PSRAM, and it is made when you pick the
-part number, not later.** `ESP32-S3FN8` and `ESP32-S3R8` are both "an ESP32-S3" and
-they are opposite choices: `FN8` = 8 MB flash in package, **no PSRAM**; `R8` =
-8 MB PSRAM in package, **no flash** (you add an external chip). Every Cardputer is
-`FN8`, and that is *"the single most consequential fact about every Cardputer"*
-([`esp32-s3fn8`](../../components/espressif/esp32-s3fn8/README.md)).
-
----
-
-## 1. The candidates, side by side
-
-Only cells with a citable source are filled. Everything else says so.
-
-| | [**ESP32-C3**](../../components/espressif/esp32-c3/README.md) | [**ESP32-S3R8**](../../components/espressif/esp32-s3r8/README.md) | [**ESP32-S3FN8**](../../components/espressif/esp32-s3fn8/README.md) | [**ESP32-P4**](../../components/espressif/esp32-p4/README.md) | [**Kendryte K230**](../../components/canaan/k230/README.md) | [**nRF52840**](../../components/nordic-semiconductor/nrf52840/README.md) | [**nRF9151**](../../components/nordic-semiconductor/nrf9151/README.md) |
-|---|---|---|---|---|---|---|---|
-| **Core(s)** | 1 × RISC‑V RV32IMC, ≤160 MHz | 2 × Xtensa LX7, ≤240 MHz | same as S3R8 | **2 × RISC‑V HP ≤400 MHz + 1 × RISC‑V LP ≤40 MHz** | **2 × RV64 XuanTie C908 — CPU1 1.6 GHz with RVV 1.0, CPU0 800 MHz RV64GCB** | *not in this record* | *not in this record* |
-| **On-chip SRAM** | **400 KB** | **512 KB** | 512 KB | **768 KB L2MEM** (SRAM *or* L2 cache for PSRAM) + 8 KB SPM + **32 KB LP SRAM, retained in deep sleep** | *not stated in the record* | — | — |
-| **PSRAM / DRAM** | **none** on the documented boards | **8 MB octal, in package** | **none** | **16 MB (`NRW16`) or 32 MB (`NRW32`), in package** | **external LPDDR4, up to 2 GB** (1 GB fitted on the T‑Display K230) | — | — |
-| **Flash** | external (16 MB on the Xteinks) | **none in package** — external required | **8 MB in package** | **none on any variant** — external required | **none on die** — boots from microSD on the documented board | — | — |
-| **Radio** | Wi‑Fi 2.4 GHz b/g/n + **BLE 5**. **No Bluetooth Classic** | Wi‑Fi 4 + **BLE 5 + Mesh**. **No Bluetooth Classic** (silicon-level) | same | **None of any kind** | **None.** Also **no Ethernet MAC** | BLE | **LTE‑M / NB‑IoT + GNSS** |
-| **USB** | USB Serial/JTAG — no bridge IC needed | USB 2.0 OTG + Serial/JTAG | same | USB 2.0 **High-Speed** OTG | — | **USB 2.0 full-speed device** (this is what makes UF2 drag-and-drop bootloaders possible) | — |
-| **Display path** | SPI | SPI / QSPI / parallel-8080 (LCD_CAM) | same | **MIPI-DSI + MIPI-CSI + ISP + H.264 enc + JPEG + PPA + 2D-DMA** | **MIPI DSI/CSI + KPU/NPU + DPU + 2.5D GPU + H.264/H.265 VPU + ISP** | — | — |
-| **Deep-sleep current** | **no figure in this repository** | **no figure in this repository** | **no figure in this repository** | **no µA figure**; the record establishes the *architecture* (LP domain retained, HP gated) | **≤ 20 µW standby** — vendor figure | **no figure** — the datasheet was **not downloaded** | **no figure** |
-| **Vendor perf claim** | — | — | — | **6.92 CoreMark/MHz dual-core** → ≈2 768 CoreMark at 400 MHz. Espressif's own build; no independent reproduction found | ⚠ the TOPS number is *"a marketing figure, not a datasheet figure"* | — | — |
-| **Documentation maturity** | ⚠ **the datasheet was never retrieved** into this repository (`not-attempted`) | datasheet + TRM v1.8 held locally | derived from M5Stack schematics + vendor BSP | ⚠ the datasheet is a **pre-release** document | datasheet + brief datasheet from Canaan's own `k230_docs` repo | ⚠ **product specification not downloaded** | ⚠ **AT command reference behind a restricted path, not retrieved** |
-| **Documented in this repo as** | Xteink X3, X4 | PaperMono, Waveshare 3.97, all 11 LilyGO T‑Display‑S3 boards, Waveshare knob, XIAO Sense | every Cardputer, DinMeter | Tanmatsu, Waveshare P4 boards, Espressif P4 boards | LilyGO T‑Display K230 | **companion** on the K230 base board | **companion** on the K230 keyboard base |
-
----
-
-## 2. ⚠ The numbers this repository does not have
-
-State these first, because the rest of the page is shaped by them.
-
-**There is no deep-sleep current figure for the ESP32-C3, ESP32-S3 or ESP32-P4
-anywhere in this repository.** The C3 component record has no power table at all
-and its datasheet is recorded as `not-attempted`. The S3R8 record covers the radio,
-PSRAM, PIE/SIMD and package pins but no sleep figures. The P4 record describes the
-*architecture* of the low-power domain — the LP core runs on a retained domain
-doing sensor polling and wake decisions while the two HP cores stay powered down —
-but gives no current.
-
-**So this page cannot rank these parts on sleep current, and does not.** Anyone who
-needs that must fetch the datasheets; note the repository's own precedent that
-three agents once fetched three ESP32-S3 datasheets from three portals and got
-**three different SHA-256 values and three different sizes**.
-
-What *does* exist here is **board-level** sleep and idle claims, which are a
-different quantity — they include regulators, load switches, an expander, a PMIC
-and whatever the vendor left powered — and every one of them is a vendor claim
-under **unstated conditions**:
-
-| Board figure | Value | Source record |
-|---|---|---|
-| Cardputer v1.0 / v1.1 / ADV, **power switch OFF** | 0.26 / 0.15 / **0.23 µA** at 4.2 V | [Cardputer ADV](../../devices/m5stack/cardputer-adv/README.md) |
-| M5Stack **Stamp-S3 → Stamp-S3A**, `VIN_5V` sleep | **310.89 µA → 6.84 µA** | [Cardputer v1.1](../../devices/m5stack/cardputer-v1.1/README.md) |
-| Stamp-S3 → Stamp-S3A, standby | 33.5 mA → **25.5 mA** | idem |
-| Cardputer ADV operating, 4.2 V | **120.2 mA** idle · 132.3 mA Wi-Fi · **154.6 mA BLE** | [Cardputer ADV](../../devices/m5stack/cardputer-adv/README.md) |
-| Cap CC1101 & NFC, both radios asleep | **140.87 µA @ 5 V** | [Cap CC1101](../../devices/m5stack/cap-cc1101/README.md) |
-| Unit C6L (ESP32-C6 + SX1262), sleep | **696.86 µA** (Grove) / 866.42 µA (USB-C) | [Unit C6L](../../devices/m5stack/unit-c6l/README.md) |
-| LoRaWAN Unit (STM32WLE5), sleep | **28.61 µA @ 5 V** | [LoRaWAN Unit](../../devices/m5stack/unit-lorawan-stm32wle5/README.md) |
-| T-Display K230, **idle** | **2.5 W** | [T-Display K230](../../devices/lilygo/t-display-k230/README.md) |
-
-**Read the last row against the others.** 2.5 W at *idle* is roughly three orders
-of magnitude above every MCU-class board here. That single figure is the whole
-Linux-vs-MCU trade, and it is why the community reaction to the K230 as a
-Meshtastic node was *"the battery life on this would be less than it would be with
-just a phone and a regular nRF node"* — an opinion, and nobody has published a
-measurement either way.
-
-**And note the Stamp-S3 → Stamp-S3A row: a 45× improvement in board sleep current
-that came from swapping a µPOL power module for a discrete buck and moving the
-WS2812 onto a switched rail** — and which cost the RGB LED its always-on supply,
-so PWM-dimming the backlight now browns out the LED. **On a battery device, sleep
-current is usually a power-tree property, not a SoC property.**
-
-Two further absences worth stating:
-
-- **No device in this repository has a measured e-paper refresh energy, frontlight
-  current or battery runtime, from anyone.** The one panel-level figure is
-  Waveshare's *"< 40 mW"* refresh claim, with the panel manual saying **36 mW
-  typical at 3.0 V and 120 mA peak**.
-- **No independent benchmark of the K230 exists**, even though its own BSP builds
-  **CoreMark and CoreMark-PRO into the shipped image**. The tools to produce the
-  number ship on the device and nobody has published one.
-
----
-
-## 3. PSRAM and framebuffer size — the decision that actually gets made
-
-### 3.1 The arithmetic
-
-Framebuffer sizes computed from resolutions sourced in the device records
-(`inferred` — it is arithmetic, but the inputs are cited):
-
-| Panel | Depth | One plane | Two planes (old + new) |
-|---|---|---|---|
-| Xteink X4 / X4 Pro / X4C · Waveshare 3.97 — **800 × 480** | 1 bpp | **46.9 KiB** | 93.8 KiB |
-| Xteink X3 — **792 × 528** | 1 bpp | **51.0 KiB** | 102.1 KiB |
-| PaperMono — **480 × 800, 4-grey** | 2 bpp | **93.8 KiB** | 187.5 KiB |
-| Cardputer — 240 × 135 | RGB565 | 63.3 KiB | — |
-| T-Display-S3 — 170 × 320 | RGB565 | 106.3 KiB | — |
-| Waveshare P4 reference — 1024 × 600 | RGB565 | **1.2 MB** (stated in the [P4 record](../../components/espressif/esp32-p4/README.md)) | 2.4 MB |
-| T-Display K230 — 568 × 1232 AMOLED | RGB565 | **1.33 MiB** | 2.67 MiB |
-
-### 3.2 What that means per SoC
-
-**On a C3 (400 KB SRAM) a 1-bit e-paper framebuffer fits — and is not the
-problem.** One 800×480 plane is ~47 KB, two are ~94 KB. That leaves ~300 KB for
-everything else, and *everything else* is where a reader firmware actually lives:
-an EPUB parser, a CSS engine, UAX #14 line breaking with hyphenation, a glyph
-cache, a page cache with position anchors, and a TLS stack for sync.
-
-The evidence that this is the binding constraint, not a theoretical concern:
-
-- **CrossPoint's current development focus, in priority order, is "DRAM/heap
-  footprint (the C3 sets the ceiling), flash footprint, code cleanup, then reading
-  experience."** The *tightest target sets the ceiling for every device*.
-- **OTA out-of-memory was observed on the X3**, and CrossPoint stopped using
-  GitHub releases because of it.
-- The C3 component record states it plainly: *"The absence of PSRAM is the single
-  most consequential fact for anyone writing firmware for the X3 or X4."*
-
-**On an S3R8 (8 MB PSRAM) the constraint moves somewhere else entirely.** Multi-buffer
-rendering, damage-window partial refresh and large book indices become possible.
-The cost is not memory, it is **pins**: the octal PSRAM consumes **GPIO33–GPIO37
-and `SPICS1` inside the package**, which the boards' own schematics mark `NC`.
-Driving them raises no error — *"it corrupts PSRAM access, typically surfacing as a
-cache-access panic far from the offending code."* That is *"the most important
-practical consequence of choosing the R8 variant"*, and it is why the LilyGO
-T-Display-S3 boards have so few free pins.
-
-⚠ **Arduino must be told `PSRAM = OPI PSRAM`, or `ps_malloc()` silently fails.**
-
-**On an S3FN8 (no PSRAM) you are back in C3 territory with a faster CPU.** The
-Cardputer worked example is instructive: an author memory-mapped a **2.16 MB
-Unicode font out of its own flash partition** *"so rendering Cyrillic, CJK or Greek
-costs no heap at all"* — because there is nowhere else for it to live.
-
-**On a P4 the question inverts: how much of the 768 KB L2MEM do you give to
-cache?** The record is explicit that this is *"a tradeoff you configure, not a
-fixed budget"* — more cache raises effective PSRAM bandwidth for framebuffer work,
-more directly-addressed SRAM gives deterministic low-latency working memory. A
-1024×600 RGB565 single buffer already lives in PSRAM and depends on cache
-behaviour; double buffering is 2.4 MB. **This is why the 32 MB variant exists.**
-
-**On a K230, 1 GB of LPDDR4 makes the framebuffer question disappear** and
-replaces it with a different one: the two cores are **separate subsystems, not a
-coherent cluster**, each with its own L2 and its own PLIC, and Canaan's own SDK
-runs **two different operating systems simultaneously** — RT-Smart on CPU1, Linux
-on CPU0 — with an explicit IPC API and a `sharefs`. *You do not schedule a Linux
-thread onto CPU1.* (The LilyGO board's BSP builds a Linux-only image, which
-sidesteps this.)
-
----
-
-## 4. Radio duty cycle, and the cost of not having one
-
-For an e-ink reader the radio duty cycle is usually near-zero — Wi-Fi comes up to
-sync a library or pull an OTA, then goes away for hours. That makes **integration**
-matter far more than radio performance.
-
-| SoC | Radio situation | What it costs a battery e-ink design |
-|---|---|---|
-| **ESP32-C3** | Wi-Fi + BLE 5 on die | Nothing extra. **No Bluetooth Classic** — any project expecting A2DP or SPP is on the wrong SoC |
-| **ESP32-S3** | Wi-Fi + BLE 5 + Mesh on die | Nothing extra. **No Bluetooth Classic, at silicon level** — the record spends a full section on this because it is the part's *"single most consequential architectural constraint"*, and treats **LE Audio as unavailable** too (an argument from documented absence, marked *uncertain*) |
-| **ESP32-P4** | **None** | A companion SoC over SDIO — ESP32-C6-MINI-1 or ESP32-C5-MINI-1 on every documented P4 board. A second crystal, a second antenna, a second flash, a second firmware image |
-| **Kendryte K230** | **None, and no Ethernet MAC either** | **Five external devices doing what an integrated SoC does internally**: RTL8189FS Wi-Fi over SDIO, Bluetooth **via a USB dongle only**, SPI LoRa, UART cellular, UART BLE, USB Ethernet. The record calls this *"the defining architectural fact of the board"* |
-| **nRF52840** | BLE | On the K230 board it is a **companion** running LilyGO's AT-command BLE-central firmware, and it also drives the 21700 5 V boost on `P0.04` |
-| **nRF9151** | LTE-M / NB-IoT + GNSS | A **10 × 16 mm SiP** and a second toolchain (§5) |
-
-**The Bluetooth-Classic worked example is the one to internalise**, because it
-shows what a late-discovered radio requirement actually costs. The
-[Waveshare ESP32-S3-Knob-Touch-LCD-1.8](../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md)
-needed A2DP, so Waveshare soldered an **original ESP32 (`ESP32-U4WDH`)** next to
-the S3 purely to do Bluetooth Classic. The result: a second 40 MHz crystal, a
-second antenna, an inter-MCU UART with a private protocol, the audio hardware
-**split across both chips** so neither can produce sound alone, and a flashing
-procedure where **the USB-C plug's orientation selects which MCU you are talking
-to**. As the component record puts it: *"It is far cheaper to check this
-constraint at part-selection time."*
-
-**And for what it is worth, the radio is rarely the sleep problem.** An SX1262
-sleeps at **600 nA with its configuration retained**
-([SX1262 §5](../../components/semtech/sx1262/README.md)); the whole Cap CC1101
-board sleeps at 140.87 µA. The two-order-of-magnitude difference is the board, not
-the radio.
-
----
-
-## 5. Toolchain maturity
-
-| SoC | Toolchain | Maturity notes from the records |
-|---|---|---|
-| **ESP32-C3 / S3** | ESP-IDF, Arduino-ESP32, PlatformIO | The mature end. But two real traps are documented: LilyGO **pins its test matrix at Arduino core 2.0.14** and says higher versions may not work (corroborated — the newest factory binary is built on ESP-IDF v4.4.6, the base of 2.0.14); and the **`USB CDC On Boot` trap**, where a board that runs fine on USB **blocks before `setup()` finishes on battery** because the Arduino core waits for a host to open the port |
-| **ESP32-P4** | ESP-IDF, target `esp32p4` | ⚠ **the datasheet is a pre-release document**. Also a board-level constraint that looks like a silicon one: Espressif states the onboard flash on both Function-EV boards *"operates at a maximum clock frequency of 80 MHz and does not support the auto suspend feature"*, with 120 MHz gated behind contacting Espressif |
-| **Kendryte K230** | **Canaan K230 SDK only** | ⚠ *"Nothing in the ESP32 ecosystem applies. No Arduino, no PlatformIO for the main SoC, no ESP-IDF"* — LilyGO's own FAQ says so. Build host must be Ubuntu 20.04/22.04/24.04, WSL2 or Docker, with a vendor toolchain at a **hard-coded `/opt/toolchain`** path. **17 months** elapsed between the board going on sale (2025-03-21) and its BSP repository existing (2026-08-13). **A verified owner bricked one and there is no recovery section in any LilyGO document.** On NixOS this needs deliberate work — [`guides/nixos/riscv-and-vendor-sdk-toolchains.md`](../nixos/riscv-and-vendor-sdk-toolchains.md) |
-| **nRF52840** | Zephyr / nRF Connect SDK, **or** the Adafruit nRF52 bootloader with **UF2** (family ID `0xADA52840`) — double-tap reset, drag a `.uf2` onto a mass-storage device | The UF2 route is the friendliest flashing story of any part on this page. LilyGO also exposes a **UART DFU** path so the K230 can field-update its companion with no PC |
-| **nRF9151** | **NCS v3.4.0** | ⚠ **Every nRF91 application is really two images**: TF-M (secure) plus the non-secure application. That is a permanent build-system fact, not a one-off. ⚠ The **AT Commands Reference is behind a restricted path** and was not retrieved here |
-
-**Two toolchain observations that are really about maintenance, not tooling:**
-
-- **The K230's 17-month documentation gap is the honest measure of its
-  maturity**, and it is the single best explanation for the early-owner
-  experience: *"I've also been completely unable to figure out how to even get an
-  OS installed."* The BSP is now three weeks old and already at v0.2.4 — moving
-  fast, from a standing start.
-- **On the ESP32 side the risk is not the toolchain, it is version pinning.**
-  Vendor firmware pins libraries *and patches them*, while the vendor's own
-  published PlatformIO snippets pin nothing. Building from the documentation does
-  not reproduce the shipped firmware.
-
----
-
-## 6. The price consequence
-
-Every figure is item-only, vendor-direct, from the record's own dated observation.
-Note that these are **device** prices, not chip prices — this repository holds no
-component-level pricing for any of these SoCs.
-
-| SoC | Cheapest documented board carrying it | Price | Date |
-|---|---|---|---|
-| **ESP32-S3R8** | [LilyGO T-Display-S3](../../devices/lilygo/t-display-s3/README.md) — 16 MB flash **+ 8 MB OPI PSRAM + a 1.9″ colour LCD** | **$9.04** | 2026-09-07 |
-| **ESP32-S3R8** (module) | [Waveshare ESP32-S3-ePaper-3.97](../../devices/waveshare/esp32-s3-epaper-3.97/README.md) — the same memory, plus e-paper, AXP2101, RTC, IMU, audio | **$34.99** | 2026-09-01 |
-| **ESP32-S3R8** | [M5Stack PaperMono](../../devices/m5stack/papermono/README.md) — e-paper + frontlight + NFC + LoRa | **$65.00** | 2026-09-01 |
-| **ESP32-S3FN8** (no PSRAM) | [Cardputer ADV](../../devices/m5stack/cardputer-adv/README.md); the bare Stamp-S3A module is **$7.50** | **$29.90** / $7.50 | 2026-09-04 |
-| **ESP32-C3** | [Xteink X3](../../devices/xteink/x3/README.md) — a complete sealed reader with battery, enclosure and 3.7″ 257 PPI panel | **$69.00** | 2026-09-04 |
-| **ESP32-P4** | [Tanmatsu](../../devices/nicolai-electronics/tanmatsu/README.md) — 32 MB PSRAM, MIPI DSI, keyboard, LoRa, **full KiCad under CERN-OHL-P** | **€99.17 ex VAT / €119.99 inc** | 2026-08-24 |
-| **Kendryte K230** | [LilyGO T-Display K230](../../devices/lilygo/t-display-k230/README.md) bare board | **$98.79** | 2026-09-04 |
-| **K230 + keyboard + cellular** | T-Display K230 Kit, **two separate SKUs** | **$263.56** | 2026-09-04 |
-| **nRF9151** | **the cleanest price signal available**: $113.25 with it, $70.94 without, same keyboard base | **$42.31 delta** | 2026-09-04 |
-| **nRF52840** | no standalone price observed | **no figure in this repository** | — |
-
-### Reading the price table
-
-**The S3-with-PSRAM row is the anomaly, and it is the strongest argument in this
-whole guide.** A T-Display-S3 at **$9.04** carries the same memory configuration —
-16 MB flash, 8 MB OPI PSRAM — as a $65 PaperMono and a $99 Xteink X4 Pro. **PSRAM
-is not what makes those devices expensive.** The enclosure, the battery, the
-e-paper glass, the frontlight and the radios are.
-
-**Therefore: on a new design, choosing an `R8` over an `FN8`, or an S3 over a C3,
-is close to free at the silicon level, and the C3's memory ceiling is the most
-expensive constraint in this repository measured in developer time.** It is the
-reason CrossPoint's number-one development priority is heap footprint; it is why
-OTA had to move off GitHub releases; it is why an author had to memory-map a font
-out of flash. None of that would exist on an S3R8 at the same board price.
-
-**The K230 costs ~11× a T-Display-S3 and ~1.5× a Tanmatsu for the bare board**, and
-what it buys is Linux, 1 GB of DRAM, an NPU and H.265. It also buys ~2.5 W of idle
-draw and no radio of any kind. That is a legitimate purchase for a specific job and
-a bad default.
-
-**The nRF9151's $42.31 delta is the only clean per-chip price signal in this
-repository**, because LilyGO sells the identical keyboard base with and without it.
-Cellular is expensive.
-
----
-
-## 7. Recommendation, restated as a decision
-
-For a **battery-powered e-ink handheld** specifically:
-
-1. **Start from ESP32-S3 with PSRAM (`R8`).** It is what the PaperMono, the
-   Waveshare 3.97, the Xteink X4 Pro and the X4 Classic all use, the ecosystem's S3
-   targets all share one `esp32-s3-devkitc1-n16r8` board definition, and the memory
-   headroom is nearly free. Accept that **GPIO33–37 are gone** and plan the pin
-   budget around it.
-2. **Choose C3 only if the device is genuinely 1-bit, genuinely small, and you
-   accept that it will set your firmware's memory ceiling forever.** It works — the
-   X3 and X4 are shipping products with a large firmware ecosystem — but every
-   downstream project inherits the limit.
-3. **Do not choose P4 for an e-ink reader.** No radio, a pre-release datasheet, and
-   the features you would be paying for (MIPI-DSI, ISP, H.264, a pixel-processing
-   accelerator) are irrelevant to a monochrome panel that updates in hundreds of
-   milliseconds. Choose it for a **colour GUI or camera handheld**, as Tanmatsu
-   and the Waveshare P4 boards do.
-4. **Do not choose K230 for an e-ink reader either.** 2.5 W idle against a
-   battery, five bolt-on radio devices, a vendor-only toolchain and no documented
-   recovery path. Choose it when *"Linux with an NPU"* is the requirement.
-5. **Treat nRF parts as companions, not application processors** — which is the
-   only way this repository has ever seen them used. If you need BLE alongside a
-   non-radio SoC, the nRF52840's UF2 story is the least painful; if you need
-   cellular, budget the money *and* the TF-M dual-image build.
-6. **Whatever you pick, measure the sleep current yourself.** This repository
-   cannot tell you what it will be (§2), and the Stamp-S3 → Stamp-S3A jump from
-   310.89 µA to 6.84 µA shows the answer is dominated by the power tree, not the
-   part number.
-
----
-
-## 8. Evidence boundary
-
-- **Nothing on this page was retrieved, built, measured or benchmarked.**
-- **Every deep-sleep figure quoted is a board-level vendor claim under unstated
-  conditions**, except the K230's ≤20 µW, which is a vendor figure at the SoC
-  level. **No independent power measurement of any device or SoC in this
-  repository exists.**
-- **Framebuffer sizes in §3.1 are arithmetic** on resolutions cited in the device
-  records — `inferred`, not measured, and they exclude driver working buffers.
-- **The ESP32-C3 datasheet has never been retrieved into this repository**, so the
-  C3 column is the weakest one on this page and is family-level throughout. The
-  exact C3 package variant on the Xteink boards has **never been read**.
-- The ESP32-P4 datasheet is **pre-release**; the nRF52840 product specification and
-  the nRF91 AT command reference were **not downloaded**.
-- The P4's CoreMark figure is Espressif's own, under Espressif's own build and
-  configuration, and **says nothing about the memory-bound graphics and camera
-  workloads most P4 designs actually run**.
-- Prices are single-storefront, single-date, single-currency observations. They
-  exclude shipping, tax and duty, and for a $9 board international shipping can
-  exceed the item price.
-
-## Related
-
-- [E-paper displays](e-paper-displays.md) — waveforms, bias rails, VCOM, update-mode trade-offs
-- [Display interfaces](display-interfaces.md) — bandwidth arithmetic and framebuffer sizing
-- [Parallel 8080 LCD buses](parallel-8080-lcd-buses.md)
-- [Adding LoRa, NFC and an RGB sidelight to e-ink firmware](adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-- [Handheld and e-ink device landscape, 2026-09](../markets/handheld-and-eink-device-landscape-2026-09.md) · [Device comparison matrix](../markets/device-comparison-matrix.md)
-- [Xteink firmware ecosystem](../../devices/xteink/firmware-ecosystem.md) — what a board must provide to be supported
-- [Espressif ecosystem and product lines](../espressif/ecosystem-and-product-lines.md) · [SoC peripheral reference](../espressif/soc-peripheral-reference.md) · [Memory and boot](../espressif/memory-and-boot.md) · [Practical errata](../espressif/errata-practical.md)
-- Components: [ESP32-C3](../../components/espressif/esp32-c3/README.md) · [ESP32-S3R8](../../components/espressif/esp32-s3r8/README.md) · [ESP32-S3FN8](../../components/espressif/esp32-s3fn8/README.md) · [ESP32-P4](../../components/espressif/esp32-p4/README.md) · [K230](../../components/canaan/k230/README.md) · [nRF52840](../../components/nordic-semiconductor/nrf52840/README.md) · [nRF9151](../../components/nordic-semiconductor/nrf9151/README.md)
diff --git a/guides/lora/README.md b/guides/lora/README.md
deleted file mode 100644
index d666f1f..0000000
--- a/guides/lora/README.md
+++ /dev/null
@@ -1,783 +0,0 @@
-# LoRa — a device-independent guide
-
-> **How does LoRa actually work, what does LoRaWAN add, and how do I bring an SX126x up?**
-> A cross-cutting guide compiled from the LoRa knowledge in this library — principally the
-> [Semtech SX1262 record](../../components/semtech/sx1262/README.md) (662 lines, built on
-> `DS.SX1261-2.W.APP` Rev 2.2 held locally), the
-> [M5Stack Stamp-LoRa-1262 module record](../../components/m5stack/stamp-lora-1262/README.md),
-> the [Ebyte E22-900M22S record](../../components/ebyte/e22-900m22s/README.md) and the
-> [PaperMono LoRa feature guide](../../devices/m5stack/papermono/features/lora.md).
-> Compiled **2026-09-02**. **No radio has been keyed by anyone whose report could be located.**
-
-## 0. What this guide is, and what it is not
-
-This is the **common** layer the research method asks for in step 13: reusable concepts, APIs,
-alternatives, validation and generic pitfalls, **without unqualified device pin assignments**. Where
-a concrete example is needed the device is named and its record linked.
-
-It does **not** duplicate the deep records. The
-[SX1262 record](../../components/semtech/sx1262/README.md) owns the opcode table, the electrical
-tables, the DIO2/DIO3 mechanics and Semtech's four mandatory errata workarounds. **Where this guide
-and a deep record disagree, the deep record wins.**
-
-What this page adds: the **arithmetic** that connects SF/BW/CR to airtime, battery and legality —
-which is the part that is always described qualitatively and always bites quantitatively — plus the
-LoRa/LoRaWAN/Meshtastic distinction, a sourced regional band table, and a set of failure signatures.
-
-### Evidence labels
-
-| Label | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | Datasheet claim, inherited from a component record citing a section or table of a locally-held document (`DS.SX1261-2.W.APP` Rev 2.2) | `not-tested` |
-| **[SRC]** | Read out of source at a cited `file:line` — either from a repo record, or from a live read of upstream on **2026-09-02** | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | Vendor documentation or repository metadata, retrieved 2026-09-02 | `not-tested` |
-| **[PCB]** · **[BOM]** · **[GAP]** | Inherited labels from the [Ebyte E22-900M22S record](../../components/ebyte/e22-900m22s/README.md): a parsed KiCad netlist, a production BOM, and that record's marker for a claim that would normally be datasheet-backed and is not | `executed-success` for [PCB]/[BOM] extraction; **[GAP] is an explicit absence of evidence** |
-| **[STD]** | A claim about a standard or regulation (ETSI, FCC, ARIB, LoRa Alliance). ⚠ **This repository holds none of these documents** | `not-tested`, **unverified against the primary document** |
-| **[REC]** | Recalled general knowledge with no document behind it here | **`not-tested` and unsourced** |
-| **[INF]** | Derived here, with the arithmetic shown | `inferred` |
-
-⚠ **No figure in this guide was measured.** §12 lists what could not be sourced.
-
----
-
-## 1. LoRa modulation, and the arithmetic that follows from it
-
-### 1.1 Chirp spread spectrum
-
-LoRa modulates by sweeping the carrier linearly across the channel bandwidth. A symbol is a chirp
-whose *starting point* in the cycle encodes the data; the receiver de-chirps by multiplying with a
-conjugate sweep and takes an FFT, so the symbol becomes a peak in a bin **[REC]**.
-
-Two properties fall out, and they are the whole of LoRa's value:
-
-- **Processing gain.** Each symbol spans `2^SF` chips **[DS]** ([SX1262 §3.1, Table 6-1](../../components/semtech/sx1262/README.md#31-lora)),
-  so the receiver integrates over many chips per bit and can demodulate **below the noise floor**.
-- **Orthogonality between spreading factors.** Signals at different SF are largely invisible to each
-  other, which is why a gateway can hear several rates at once — **and why both ends of a
-  point-to-point link must be configured identically in advance** **[REC]**.
-
-The datasheet gives the demodulator's SNR floor per spreading factor **[DS]**:
-
-| SF | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
-|---|---|---|---|---|---|---|---|---|
-| chips/symbol | 32 | 64 | 128 | 256 | 512 | 1024 | 2048 | 4096 |
-| typical SNR (dB) | −2.5 | −5 | −7.5 | −10 | −12.5 | −15 | −17.5 | **−20** |
-
-**Read the pattern, not the row.** From SF5 to SF12 the SNR floor improves by 17.5 dB across seven
-steps: **exactly 2.5 dB per spreading factor step** **[INF]**, arithmetic on the table above. And
-because a symbol spans `2^SF` chips, **each step also doubles the time on air.** That single sentence
-is the entire SF trade-off:
-
-> **One spreading-factor step buys 2.5 dB of link budget and costs exactly 2× airtime.**
-
-### 1.2 Bandwidth
-
-`BW_L` runs **7.81 – 500 kHz** **[DS]**. Halving the bandwidth halves the noise power in the
-receiver, so it should buy ~3 dB. The datasheet's own sensitivity table mostly agrees **[DS]**
-([SX1262 §6.3](../../components/semtech/sx1262/README.md#63-sensitivity)):
-
-| LoRa, RX-boosted, split RF paths | SF7 | SF12 |
-|---|---:|---:|
-| BW 10.4 kHz | −134 dBm | **−148 dBm** |
-| BW 125 kHz | −124 dBm | −137 dBm |
-| BW 250 kHz | −121 dBm | −134 dBm |
-| BW 500 kHz | −117 dBm | −129 dBm |
-
-500 → 250 kHz buys 5 dB and 250 → 125 kHz buys 3 dB **[INF]** — the 500 kHz step is *worse* than
-theory, and 500 kHz is also the exact case Semtech's **known limitation §15.1** exists to patch
-**[DS]** ([SX1262 §8](../../components/semtech/sx1262/README.md#8-register-level-workarounds-you-must-implement)).
-Those two facts are probably the same fact.
-
-⚠ **Two gaps in Semtech's own document.** Table 6-1 states "not all SF are available for any
-bandwidth" **without enumerating which** **[DS]**
-([G9](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata)) — an unresolved
-documentation gap. And **62.5 kHz does not appear in the sensitivity table at all**, despite being a
-perfectly legal setting and the one a shipping product in this library actually uses (§4.4). Its
-sensitivity has to be interpolated at roughly **−140 dBm at SF12** **[INF]**, which is an estimate,
-not a specification.
-
-### 1.3 Coding rate
-
-`CR` runs **4/5 to 4/8** **[DS]** — forward error correction overhead. Going from 4/5 to 4/8 multiplies
-the payload symbol count by **8/5 = 1.6×** **[INF]**. It buys robustness against burst interference,
-not against thermal noise; SF and BW own the noise floor.
-
-### 1.4 Symbol time and airtime — the consequence that bites
-
-The datasheet gives the symbol rate as `Rs = BW / 2^SF` **[DS]**, so the **symbol time** is:
-
-```
-Ts = 2^SF / BW                                      [DS] for Rs; [INF] for the inversion
-```
-
-| Ts (ms) | SF7 | SF8 | SF9 | SF10 | SF11 | SF12 |
-|---|---:|---:|---:|---:|---:|---:|
-| BW 500 kHz | 0.256 | 0.512 | 1.024 | 2.048 | 4.096 | 8.192 |
-| BW 250 kHz | 0.512 | 1.024 | 2.048 | 4.096 | 8.192 | 16.384 |
-| **BW 125 kHz** | **1.024** | 2.048 | 4.096 | 8.192 | 16.384 | **32.768** |
-| BW 62.5 kHz | 2.048 | 4.096 | 8.192 | 16.384 | 32.768 | **65.536** |
-
-All **[INF]** — arithmetic on the datasheet's own definition.
-
-A LoRa symbol carries `SF` raw bits **[REC]**, so the nominal bit rate is
-`Rb = SF · (BW / 2^SF) · 4/(4 + n)` for `CR = 4/(4+n)`:
-
-| Nominal Rb, BW 125 kHz, CR 4/5 | SF7 | SF8 | SF9 | SF10 | SF11 | SF12 |
-|---|---:|---:|---:|---:|---:|---:|
-| **[INF]** bit/s | 5469 | 3125 | 1758 | 977 | 537 | 293 |
-
-**Sanity check, and it passes.** LoRaWAN's EU868 data rates DR5…DR0 are commonly quoted as
-5470 / 3125 / 1760 / 980 / 440 / 250 bit/s **[REC]**. The first four match the derivation exactly.
-SF11 and SF12 come out high until you apply **LDRO** — low-data-rate optimisation, which reserves two
-bits per symbol: `537 × 9/11 = 439` and `293 × 10/12 = 244` **[INF]**. That agreement is itself
-evidence the derivation is right, and it is why LDRO is not optional at long symbol times.
-
-**Now the part that bites.** Take the configuration the
-[PaperMono factory firmware actually programs](../../devices/m5stack/papermono/features/lora.md) —
-**SF12, BW 62.5 kHz, CR 4/8** **[SRC]**:
-
-```
-Ts  = 4096 / 62 500          =  65.536 ms per symbol            [INF]
-Rb  = 12 / 0.065536 × 4/8    =  91.6 bit/s   (76 bit/s with LDRO) [INF]
-preamble alone, 10 symbols   =  0.66 s                          [INF]
-a 16-byte payload            =  128 bits ≈ 1.4 s of payload      [INF]
-⇒ a single small frame is on the order of 2–3 seconds on air.
-```
-
-The SX1262 record independently characterises this configuration as "on the order of tens of bits per
-second… a maximum-range demonstration, not a sensible throughput default"
-([§12](../../components/semtech/sx1262/README.md#12-used-by)) — **the derivation agrees with the
-record**, which is the point of showing it.
-
-⚠ **Do not hand-roll the exact figure.** The closed-form airtime expression (with its header,
-sync-word, CRC and ceiling terms) lives in Semtech application notes **this repository does not
-hold**. Use the library: RadioLib exposes **`SX126x::getTimeOnAir(size_t len)`** — declared
-`src/modules/SX126x/SX126x.h:634`, implemented `SX126x.cpp:812`, and it reads SF, BW, CR, preamble
-length, CRC, implicit-header mode and LDRO out of the current configuration
-(`SX126x.cpp:817-832`) **[SRC]**, read live 2026-09-02. RadioLib itself uses it internally to
-compute transmit timeouts (`SX126x.cpp:236`, `:286`).
-
-### 1.5 The battery consequence, which is not the one people expect
-
-Semtech's figures at 3.3 V, 25 °C, TCXO and RF-switch consumption excluded **[DS]**
-([SX1262 §5.4, §6.1](../../components/semtech/sx1262/README.md#54-regulator-choice-and-what-the-papermono-firmware-gives-up)):
-
-| Mode | DC-DC | **LDO** |
-|---|---:|---:|
-| RX, LoRa 125 kHz | 4.6 mA | **8.8 mA** |
-| RX boosted, LoRa 125 kHz | 5.3 mA | **10.1 mA** |
-| `STDBY_RC` | 0.6 mA | 0.6 mA |
-| Sleep, config retained | 600 nA | 600 nA |
-| Sleep, cold (no retention) | 160 nA | 160 nA |
-| **TX +22 dBm (SX1262)** | **118 mA** | **118 mA** — the PA runs from `VBAT` either way |
-
-Now put airtime against it **[INF]**:
-
-```
-one 3 s frame at +22 dBm   = 118 mA × 3 s     = 0.098 mA·h
-ten frames per hour                            ≈ 1 mA average
-continuous receive, LDO                        = 8.8 mA
-continuous receive, DC-DC                      = 4.6 mA
-```
-
-**Transmitting at full legal power ten times an hour costs about a ninth of what listening costs.**
-For any node that is not asleep, **receive current dominates**, and therefore the **LDO-versus-DC-DC
-decision matters more than the transmit power decision**. On the SX1262 the DC-DC covers the IC core
-only — the PA is fed from `VBAT` either way — so DC-DC does **nothing** for transmit current and
-roughly **halves** receive current **[DS]**.
-
-This is why the SX1262 record calls the LDO choice
-"[the single most consequential unverified fact about the radio on this board](../../components/semtech/sx1262/README.md#54-regulator-choice-and-what-the-papermono-firmware-gives-up)"
-(G5). The arithmetic above is why that judgement is right. DC-DC needs two external inductors — 47 nH
-before pin 1 and 15 µH between the regulator pins — which is exactly the BOM a small module omits
-**[DS]**.
-
-Two more numbers for a duty-cycled design **[DS]**: sleep→standby is **3500 µs cold-start** versus
-**340 µs warm-start with retention**. **Ten to one** — which is the entire reason `SetSleep` has a
-retention flag, and it must be paid *plus* the TCXO delay (§5.4) on every wake.
-
----
-
-## 2. LoRa is not LoRaWAN, and Meshtastic is neither
-
-The single most common confusion in this subject.
-
-| Layer | What it is | What you get | What you must build |
-|---|---|---|---|
-| **LoRa** | A **physical layer**. Semtech's proprietary chirp modulation, in silicon | A radio that sends and receives framed bytes at a chosen SF/BW/CR with a CRC and a sync word | **Everything**: addressing, retries, encryption, key management, channel policy, duty-cycle accounting |
-| **LoRaWAN** | A **MAC layer and network architecture** specified by the LoRa Alliance, on top of LoRa | Device classes A/B/C, join procedure (OTAA/ABP), two AES-128 key hierarchies, adaptive data rate, regional channel plans, and a star-of-stars topology through gateways to a network server | An account with a network server, gateway coverage, and acceptance that **downlink is scarce** |
-| **Meshtastic** | An **application and mesh protocol** using raw LoRa — **not** LoRaWAN | A flooding mesh of peer nodes, phone apps, position and text messaging, per-region presets | Nothing, if you use its firmware. But you are on **its** channel plan and **its** airtime budget |
-
-**Raw LoRa point-to-point** is entirely reasonable and is what the SX126x drivers give you by
-default. It is the right answer for a private link between devices you own. It is the wrong answer
-the moment you want many nodes, roaming, or someone else's infrastructure.
-
-**LoRaWAN's real cost is asymmetry.** A Class A device can only receive in two short windows after it
-transmits **[REC]**; that is what makes the battery numbers work and it is also why LoRaWAN is a poor
-fit for anything needing prompt downlink. Class C listens continuously — and §1.5 says what that
-costs.
-
-**Meshtastic is a flood mesh**, so every node's airtime is consumed by every other node's traffic.
-That interacts badly with §3's duty-cycle limits at scale, and it is why Meshtastic ships
-conservative presets rather than the fastest settings the radio supports **[REC]**.
-
-The library layering mirrors this exactly. RadioLib keeps the PHY in `src/modules/` and puts LoRaWAN
-in `src/protocols/LoRaWAN/` alongside APRS, AX.25, RTTY and a dozen other protocols **[SRC]** — the
-radio and the network stack are separate concerns in the code as well as on paper.
-
----
-
-## 3. Regional band plans and duty cycle
-
-⚠ **This is a legal constraint, not a firmware preference.** A wideband module is *capable* of
-transmitting outside your allocation. You are not permitted to.
-
-The clearest machine-readable statement of the band plans in this library is RadioLib's own table,
-read live from `src/protocols/LoRaWAN/LoRaWANBands.cpp` @ `master`, 2026-09-02 **[SRC]**. Frequencies
-are stored in units of 100 Hz; `dutyCycle` is **milliseconds of transmit permitted per hour**;
-`dwellTime` is a per-transmission cap in ms (`RADIOLIB_LORAWAN_DWELL_TIME` = **400**,
-`LoRaWAN.h:148`).
-
-| Band | Type | Range (MHz) | Max power | Steps | **Duty cycle** | Dwell-time cap |
-|---|---|---|---:|---:|---|---|
-| **EU868** | dynamic | 863.0 – 870.0 | 16 dBm | 7 | **36 000 ms/h = 1 %** | — |
-| **US915** | fixed | 902.0 – 928.0 | 30 dBm | 14 | **none** | **400 ms** |
-| EU433 | dynamic | 433.0 – 434.0 | 12 dBm | 5 | **36 000 ms/h = 1 %** | — |
-| **AU915** | fixed | 915.0 – 928.0 | 30 dBm | 10 | none | **400 ms** |
-| CN470 | fixed | 470.0 – 510.0 | 19 dBm | 7 | none | — |
-| **AS923** (+ `_2`, `_3`) | dynamic | 915.0 – 928.0 | 16 dBm | 7 | **36 000 ms/h = 1 %** | **400 ms** |
-| AS923_4 | dynamic | 917.0 – 920.0 | 16 dBm | 7 | 36 000 ms/h | 400 ms |
-| KR920 | dynamic | 920.9 – 923.3 | 14 dBm | 7 | none | — |
-| **IN865** | dynamic | 865.0 – 867.0 | 30 dBm | 10 | none | — |
-
-Eleven bands total (`LoRaWANBands.cpp:6-18`). EU868's three default join channels are **868.1,
-868.3, 868.5 MHz** **[SRC]** (`LoRaWANBands.cpp:32-34`).
-
-**What this table means in practice.**
-
-- **`dutyCycle = 36000` is the 1 % rule made concrete: 36 seconds of transmission per hour.** Put
-  §1.4's arithmetic beside it — a single SF12/62.5 kHz frame is **2–3 seconds** — and you get
-  **roughly a dozen frames per hour, for the whole device** **[INF]**. That is not a tuning
-  parameter; it is the design envelope. People discover it after building the product.
-- **The two regimes are structurally different, not just numerically.** EU and AS923 are
-  *duty-cycle* regimes: transmit rarely, at any length. US915 and AU915 are *dwell-time* regimes: no
-  hourly budget, but **no single transmission may exceed 400 ms** — which **forbids SF12 at 125 kHz
-  outright**, since §1.4 shows a bare 12-symbol preamble already costs 393 ms **[INF]**. A
-  configuration that is legal in Europe can be illegal in the United States for the opposite reason.
-- **AS923 has four sub-variants** in the same nominal band, and the frequency offsets differ. "AS923"
-  alone is not a configuration.
-- **Max power in the table is EIRP at the network layer**, not the chip's `SetTxParams` value.
-  EU868's 16 dBm against the SX1262's +22 dBm capability means **the radio can trivially exceed the
-  band's limit**, and antenna gain counts against you.
-
-The Ebyte record makes the underlying point bluntly for raw LoRa, outside LoRaWAN entirely
-([E22-900M22S §5](../../components/ebyte/e22-900m22s/README.md#5-regulatory-notes)) **[INF]** in that
-record: **22 dBm is 158 mW, above the 25 mW (14 dBm) e.r.p. ceiling of the most common EU
-sub-bands**, some of which additionally require Listen-Before-Talk / Adaptive Frequency Agility; and
-US 915 MHz operation under **FCC Part 15.247** expects frequency hopping or wideband operation, with
-fixed-channel use potentially falling under **15.249**'s much lower limits instead **[STD]**.
-
-Semtech states compliance *intent* for **ETSI EN 300 220**, **FCC CFR 47 Part 15**, Chinese
-regulations and Japanese **ARIB T-108** **[DS]** — intent for the chip, which is not approval for
-your board.
-
-⚠ **A wideband SKU is a regulatory liability, not a feature.** The
-[Stamp-LoRa-1262 is a single 868–923 MHz part with no per-region variant and no published
-certification of any kind](../../components/m5stack/stamp-lora-1262/README.md#5-caveats-and-gaps)
-(G5, a verified negative) — one module spanning EU 868, US 915 and JP 920 allocations. The
-[Tanmatsu takes the opposite approach](../../components/ebyte/e22-900m22s/README.md#11-the-family-and-the-one-substitution-that-matters-here):
-**a different module is fitted on 433 MHz units** (E22-400M22S instead of E22-900M22S), same
-footprint, same digital interface, **different antenna, matching and legal regime** **[BOM]** — and
-that record's warning generalises perfectly:
-
-> **Read the band from a configuration source, not from a constant.** Firmware that hardcodes
-> 868 MHz will transmit out of band on a 433 MHz unit.
-
----
-
-## 4. SX1261 vs SX1262 vs SX1268 — precisely
-
-One datasheet covers the SX1261 and SX1262 together, and **a claim copied from the wrong column is
-the most common error made with this document** **[DS]**
-([SX1262, opening section](../../components/semtech/sx1262/README.md)).
-
-| | **SX1261** | **SX1262** | **SX1268** |
-|---|---|---|---|
-| Max RF output | **+14 dBm** nominal, +15 dBm with special settings **[DS]** | **+22 dBm** **[DS]** | **+22 dBm class** **[SRC]** |
-| `SetTxParams` range | **−17 … +14 dBm** (`0xEF`…`0x0E`) **[DS]** | **−9 … +22 dBm** (`0xF7`…`0x16`) **[DS]** | −9 … +22 dBm **[SRC]** |
-| RadioLib's enforced range | −17 … **+15** (`SX1261.cpp:42`) **[SRC]** | −9 … +22 (`SX1262.cpp:212`) **[SRC]** | −9 … +22 (`SX1268.cpp:213`) **[SRC]** |
-| RadioLib's enforced frequency range | — | **150 – 960 MHz** (`SX1262.cpp:179`) **[SRC]** | **410 – 810 MHz** (`SX1268.cpp:180`) **[SRC]** |
-| **PA supply** | `VDD_IN` tied to **`VREG`** **[DS]** | `VDD_IN` tied to **`VBAT`** **[DS]** | as SX1262 **[REC]** |
-| `SetPaConfig` `deviceSel` | **`0x01`** **[DS]** | **`0x00`** **[DS]** | own constant **[SRC]** |
-| `hpMax` | **no effect** **[DS]** | selects PA size; **`0x07`** for +22 dBm **[DS]** | as SX1262 **[REC]** |
-| OCP after `SetPaConfig` | **60 mA** (`0x18`) **[DS]** | **140 mA** (`0x38`) **[DS]** | — |
-| TX current at 868/915 MHz, full power | **25.5 mA @ +14 dBm** **[DS]** | **118 mA @ +22 dBm** **[DS]** | — |
-| **DC-DC scope** | **whole IC** **[DS]** | **IC core only — PA runs from `VBAT`** **[DS]** | as SX1262 **[REC]** |
-| Errata §15.2 PA clamp fix | **not applicable** | **required** | required |
-
-**The PA difference is a supply-topology difference, not a setting.** The SX1261's PA is fed from the
-internal regulator; the SX1262's is fed straight from the battery rail. That is why the SX1262's
-DC-DC cannot help transmit current (§1.5), why its over-current limit is more than twice as high, and
-why the two parts are **not** interchangeable on a board even though they share a pinout, a command
-set and a register map.
-
-**RadioLib encodes the distinction structurally, and that is itself confirmation** **[SRC]**, read
-live 2026-09-02: separate `SX1261`, `SX1262` and `SX1268` classes over a shared `SX126x` base, each
-with its own `checkOutputPower()` range — and **`fixPaClamping()` is called from every `SX1262` and
-`SX1268` `begin`/`beginFSK` variant (`SX1262.cpp:62,94,125,153`; `SX1268.cpp:62,94,125,153`) and from
-no `SX1261` path at all**, exactly matching the datasheet's "SX1262 only" note on errata §15.2
-**[DS]**.
-
-**How to tell which you have when the schematic will not say.** The
-[SX1262 record's method](../../components/semtech/sx1262/README.md) is worth generalising: the
-firmware asked for **22 dBm**, and +22 dBm is unreachable on an SX1261 — its `SetTxParams` range stops
-at +14 and RadioLib would reject it. **A power request above +15 dBm that a driver accepts is
-evidence of a 62.** Circumstantial, but strong, and much easier than a teardown.
-
-⚠ **The chip's frequency range is not the module's.** The SX1262 synthesiser covers **150 – 960 MHz
-continuously** **[DS]**; the Stamp module is sold as **868 – 923 MHz** **[DOC]**. The narrowing is
-imposed by a matching network and antenna nobody outside the vendor has seen
-([G6](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata)). Read the datasheet's
-floor as silicon capability, never as a usable setting.
-
----
-
-## 5. The host interface, and the five things that go wrong
-
-### 5.1 Commands, not registers
-
-The SX126x is driven by an **opcode-based command set** over SPI mode 0 (CPOL 0, CPHA 0), MSB first,
-**up to 16 MHz** **[DS]**. There is no flat register file in the usual sense: registers are reached
-through `WriteRegister` (`0x0D`) / `ReadRegister` (`0x1D`) with a 16-bit address, and the packet
-buffer through `WriteBuffer` (`0x0E`) / `ReadBuffer` (`0x1E`) **[DS]**. The full opcode table is in
-the [SX1262 record §4.2](../../components/semtech/sx1262/README.md#42-command-structure).
-
-Two ordering rules that are not incidental **[DS]**:
-
-- **`SetPacketType` must precede `SetModulationParams` and `SetPacketParams`**, because the parameter
-  encodings differ per modem.
-- **`SetRegulatorMode` is valid only in `STDBY_RC`.**
-
-Semtech devotes an entire section (§14.5) to "Issuing Commands in the Right Order" **[DS]**. Treat the
-command set as a state machine, not as a bag of setters.
-
-### 5.2 `BUSY` is a mandatory handshake
-
-**The single most important behavioural fact about this family** **[DS]**
-([SX1262 §4.3](../../components/semtech/sx1262/README.md#43-busy--a-mandatory-handshake-not-a-status-led)):
-
-- **Every "write" command raises `BUSY`** within `T_SW ≤ 600 ns` of the NSS rising edge. The host must
-  wait for it to fall.
-- **"Read" commands do not raise it** — but Semtech still says "it is essential to wait for the BUSY
-  line to go low before sending an SPI command (either a 'read' or a 'write' command)", **because
-  `BUSY` also rises to service the chip's own internal interrupts.**
-- **In sleep, `BUSY` is held high through a 20 kΩ resistor** and falls when the chip leaves sleep —
-  which is the correct, timing-independent way to satisfy `t10`, the **100 µs** minimum from NSS
-  falling to the first SCK when leaving sleep **[DS]**.
-- **`BUSY` falls at different moments per mode:** in FS when the PLL locks, in RX when the receiver is
-  up, in TX **when the PA has ramped and preamble transmission starts**.
-
-The [Ebyte record puts the practical consequence best](../../components/ebyte/e22-900m22s/README.md#2-the-sx1262-inside):
-**drivers ported from the SX127x — which has no `BUSY` — omit `WaitOnBusy()` and produce intermittent,
-timing-dependent failures that look like SPI corruption.** It is the number-one SX126x integration
-bug.
-
-**Verification test for any SX126x driver:** does it wait on `BUSY` before *every* transaction, and
-does it call `SetDio2AsRfSwitchCtrl`? A driver failing either was probably ported from the SX127x
-([E22 §6](../../components/ebyte/e22-900m22s/README.md#6-drivers-and-libraries)).
-
-### 5.3 `DIO1`, and why modules bring out only that one
-
-Ten interrupt sources, each maskable and each mappable to any of `DIO1`/`DIO2`/`DIO3` via
-`SetDioIrqParams` (`0x08`) **[DS]**: `TxDone`, `RxDone`, `PreambleDetected`, `SyncWordValid` (FSK),
-`HeaderValid`/`HeaderErr` (LoRa), `CrcErr`, `CadDone`, `CadDetected`, `Timeout`.
-
-`DIO1` is documented as "the generic IRQ line, any interrupt can be mapped to DIO1" **[DS]** — which
-is exactly why a module that exposes one DIO exposes that one
-([Stamp-LoRa-1262 §3.3](../../components/m5stack/stamp-lora-1262/README.md#33-lora_irq-is-the-sx1262s-dio1)).
-
-⚠ **In Reset, Start-up and Sleep all three DIOs are pulled down (50 kΩ) and `BUSY` is pulled up**
-**[DS]**. Only from `STDBY_RC` upward are they driven. **A DIO used for an external function is not
-driven while the chip sleeps** — which matters for both of the next two sections.
-
-### 5.4 `DIO3` as a TCXO supply — and the error you are supposed to ignore
-
-`SetDIO3AsTcxoCtrl(tcxoVoltage, delay[23:0])` (opcode `0x97`) hands `DIO3` to the state machine, which
-drives it to a programmed voltage whenever the reference is needed and power-cycles the TCXO
-otherwise **[DS]**. Settings run 1.6 / 1.7 / 1.8 / 2.2 / 2.4 / 2.7 / **3.0** / 3.3 V (`0x00`…`0x07`),
-±50 mV **[DS]**.
-
-Four things catch people, all **[DS]**
-([SX1262 §5.2](../../components/semtech/sx1262/README.md#52-dio3-as-a-tcxo-supply)):
-
-1. ⚠ **`VDDop > VTCXO + 200 mV`.** The regulator targets 200 mV below its supply. A 3.3 V rail with a
-   3.0 V setting leaves exactly 100 mV of margin over the rule — on a rail that also feeds the PA.
-2. **`delay` is in units of 15.625 µs** and gates the 32 MHz clock until the TCXO settles. **It is
-   added to every `STDBY_RC` → TX/RX transition.** Go to `STDBY_XOSC` once and wait there, rather
-   than paying it per packet.
-3. ⚠ **`XOSC_START_ERR` is *expected* at POR and at every cold-start sleep wake when a TCXO is used**,
-   because the chip does not yet know it is TCXO-clocked. Semtech: *"It is an expected behaviour…
-   The user should simply clear this flag with the ClearDeviceErrors command."* **An error handler
-   that treats it as fatal will refuse to start a perfectly good radio**
-   ([G8](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata)).
-4. **Issuing the command forces the `XTA` trimming cap register to `0x2F` (33.4 pF)**, unconditionally.
-
-**Why a TCXO at all?** Because frequency drift across a packet must stay inside `Freq_drift_max`, and
-at long symbol times that gets hard **[DS]**. Semtech is explicit about the mechanism: an SX1262
-transmitting +22 dBm from a 4 × 4 mm package heats up, "careful PCB design using thermal isolation
-techniques must be applied between the circuit and the crystal resonator", and where that isolation
-is impossible **the recommendation is a TCXO** **[DS]**. LoRaWAN system guidance expects **±30 ppm**
-overall across initial error, temperature and ageing **[DS]**.
-
-⚠ **On a module you usually cannot see whether a TCXO is fitted.** The
-[Stamp-LoRa-1262 record's G3](../../components/m5stack/stamp-lora-1262/README.md#5-caveats-and-gaps)
-is the general warning: getting this wrong yields a radio that **appears to initialise and then fails
-to transmit or receive** — the hardest class of fault to diagnose. **The evidence you can get is what
-the working vendor firmware configures.** Treat that as the known-good starting point and change it
-only with a spectrum analyser to hand.
-
-### 5.5 `DIO2` as RF switch control
-
-`SetDIO2AsRfSwitchCtrl(enable)` (opcode `0x9D`) makes `DIO2` **high during TX and low in every other
-mode** **[DS]** — a one-line antenna-path selector with exactly the right timing, which is the point:
-getting TX/RX switching right in host software is error-prone.
-
-**This is the expected topology, not an exotic one.** Semtech devotes two application-schematic
-sections to it, and omitting the switch costs measurable sensitivity: with a direct Rx/Tx tie instead
-of a switch, LoRa at BW 125 kHz / SF12 falls from **−137 to −133 dBm**, and 2-FSK at 4.8 kb/s from
-−118 to −115 dBm **[DS]**. **A 4 dB link-budget penalty** for saving a part. Note also that the
-headline sensitivity figures **exclude RF switch insertion loss**, so the real number sits below them
-either way.
-
-The [Ebyte E22 record documents the canonical implementation](../../components/ebyte/e22-900m22s/README.md#42--the-rf-switch-is-driven-by-dio2-inverted--an-elegant-detail-worth-documenting)
-**[PCB]** — `DIO2` drives `TXEN` directly and a `74LVC1GU04` unbuffered inverter generates the
-complementary `RXEN`, with a **100 kΩ pull-down** holding the front end in **receive** whenever the
-radio is unpowered, in reset, or has `DIO2` high-impedance (§5.3). Read it as the reference pattern:
-
-- the two enables can never be asserted together;
-- the safe default is receive, never transmit;
-- and **if the driver forgets `SetDio2AsRfSwitchCtrl`, the module receives but never transmits, with
-  no error anywhere.**
-
-⚠ **A module-level "antenna switch" pin is not the same signal.** A board can have **two** switch
-controls — one automatic and internal on `DIO2`, one manual and external — and conflating them is an
-easy and expensive mistake
-([SX1262 §5.3.1](../../components/semtech/sx1262/README.md#531-the-papermono-evidence-and-the-two-switches-that-are-not-the-same-thing),
-[Stamp G4](../../components/m5stack/stamp-lora-1262/README.md#5-caveats-and-gaps)).
-
-### 5.6 Semtech's four mandatory workarounds — and a resolved open question
-
-Semtech publishes four **Known Limitations** in datasheet §15. **All four are register writes the
-datasheet says to make; none is optional; a driver that omits them is subtly wrong rather than
-obviously broken** **[DS]**
-([SX1262 §8](../../components/semtech/sx1262/README.md#8-register-level-workarounds-you-must-implement)).
-
-The SX1262 record leaves as an explicit gap
-([G4](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata)) whether RadioLib applies
-them. **Read live from `jgromes/RadioLib` @ `master` on 2026-09-02, it applies all four** **[SRC]**:
-
-| Datasheet | Symptom | RadioLib | Called from |
-|---|---|---|---|
-| **15.1** | Sensitivity loss on any LoRa receiver hearing a 500 kHz signal from an SX126x | `SX126x::fixSensitivity()` — `SX126x.cpp:1277`, register `0x0889` | `SX126x.cpp:1095` |
-| **15.2** | PA over-voltage clamp over-protective; **5–6 dB** loss on a reasonable mismatch. **SX1262 only** | `SX126x::fixPaClamping(bool)` — `SX126x.cpp:1295`, register `0x08D8` | `SX1262.cpp:62,94,125,153`; `SX1268.cpp:62,94,125,153`; **never from `SX1261`** |
-| **15.3** | Implicit-header RX timeout timer not stopped on `RxDone`; fires spuriously later | `SX126x::fixImplicitTimeout()` — `SX126x.cpp:1313`, registers `0x0902` / `0x0944` | `SX126x.cpp:468` |
-| **15.4** | Packet loss on longer packets with inverted IQ | `SX126x::fixInvertedIQ(uint8_t)` — `SX126x.cpp:1338`, register `0x0736` | IQ-polarity path |
-
-Each function carries a source comment naming the datasheet section it implements **[SRC]**.
-
-⚠ **Scope of this resolution.** It was verified on **`master`, `library.properties` version 7.7.1**.
-The [PaperMono firmware pins **7.2.1**](../../devices/m5stack/papermono/features/lora.md) and the
-vendor **patches** it; **7.2.1 was not read**. So G4 is resolved for current RadioLib and **remains
-open for the pinned version**. This finding should be folded back into the
-[SX1262 record](../../components/semtech/sx1262/README.md) by whoever next edits it.
-
-Note also that **`SetPaConfig` silently reprograms over-current protection** — `0x18` (60 mA) after
-POR, `0x38` (**140 mA**) once `deviceSel` selects the SX1262 **[DS]**. Any manual OCP change must come
-*after* `SetPaConfig` or it is overwritten. Firmware calling `setCurrentLimit(140.0f)` is re-applying
-the default, not tuning anything **[SRC]**.
-
----
-
-## 6. Antenna and RF
-
-Unlike NFC (see the [NFC guide §4](../nfc/README.md)), sub-GHz LoRa is a genuine **far-field, 50 Ω**
-problem. **[REC]** throughout this section except where marked.
-
-- **Everything is 50 Ω**: the PA output match, the transmission line to the connector, the connector,
-  the antenna. A mismatch anywhere reflects power back into the PA.
-- ⚠ **Never transmit without an antenna or a 50 Ω load.** "A 22 dBm PA into an open circuit can
-  damage itself" ([E22 §5](../../components/ebyte/e22-900m22s/README.md#5-regulatory-notes)) **[INF]**
-  in that record. The SX1262 does have a **PA over-voltage clamp** — which is precisely the
-  over-protective mechanism errata §15.2 relaxes **[DS]**. Note what that means: **applying the §15.2
-  workaround makes the chip less eager to protect itself into a mismatch.** Semtech says the
-  workaround "improves chip functionality, but is not required to ensure long-term reliability", so
-  it is safe — but do not read it as "mismatch no longer matters".
-- **The PA settings and the matching network are coupled.** `paDutyCycle` "will affect the
-  distribution of the power in the harmonics and should thus be selected to work in conjunction of a
-  given matching network" **[DS]**. **Changing `paDutyCycle` on a module you did not design is not a
-  software-only decision** ([SX1262 §1.1](../../components/semtech/sx1262/README.md#11-150960-mhz-silicon-versus-an-868923-mhz-module)).
-- **Re-matching for lower power is a real efficiency win, and it is a hardware change.** With the PA
-  re-optimised for a lower target — a different `paDutyCycle`/`hpMax` **and** a different matching
-  network — +14 dBm costs **45 mA** instead of the 90 mA it costs on a +22 dBm match **[DS]**. Half
-  the current, but only with the network to match.
-- **Ground plane and layout.** A monopole or chip antenna works against the board's ground plane,
-  which is part of the antenna; shortening it detunes the radio. Keep the RF trace short, on a
-  controlled-impedance layer, over unbroken ground, with the antenna's keep-out honoured. **[REC]**
-- **A battery-supply fact worth designing around** **[DS]**: at +22 dBm the SX1262's output falls
-  **2 dB at 2.7 V, 3 dB at 2.4 V and 6 dB at 1.8 V**. **A radio asked for +22 dBm delivers +16 dBm on
-  a nearly-flat cell.** Regulating the radio rail avoids it; running straight from a cell does not.
-- **`CalibrateImage` matters.** The SX126x uses a low-IF architecture, so the RX frequency is the TX
-  frequency minus the IF; `CalibrateImage` exists for this and **should be run for the band in use**
-  **[DS]**.
-
----
-
-## 7. Software
-
-| Option | Scope | Licence **[DOC]** | Maintenance, checked 2026-09-02 **[DOC]** | Reach for it when |
-|---|---|---|---|---|
-| **RadioLib** (`jgromes/RadioLib`) | PHY for **12 radio families** plus LoRaWAN, APRS, AX.25, RTTY, SSTV, ADS-B, pagers | **MIT** | ✅ **7.7.1**, released 2026-05-31, pushed **2026-08-22** | ⭐ **The default.** Arduino and ESP-IDF; first-class `SX1262`; explicit `BUSY` handling; all four errata workarounds (§5.6) |
-| Semtech **`LoRaMac-node`** (`Lora-net/LoRaMac-node`) | Reference LoRaWAN node + SX126x HAL | `NOASSERTION` | ⚠ last push **2024-07-03** | Authoritative reference, and certification lineage. Heavy |
-| Semtech **LoRa Basics Modem** (`Lora-net/SWL2001`) | Current LoRaWAN stack | BSD-3-Clause-Clear | last push **2025-10-15** | Semtech's live stack — the successor path to LoRaMac-node |
-| **`mcci-catena/arduino-lmic`** | Arduino LoRaWAN (LMIC lineage) | MIT | last push **2026-08-05** | Existing LMIC codebases. ⚠ LMIC is memory-hungry and its timing assumptions are strict |
-| **Meshtastic** (`meshtastic/firmware`) | A whole application: mesh, phone apps, region presets | **GPL-3.0** | ✅ pushed **2026-09-02**; 8 200+ stars | Off-grid messaging out of the box — and a good reference for per-region tables |
-| Zephyr `drivers/lora/sx126x.c` | In-tree Zephyr driver | Apache-2.0 | mainline **[REC]** | Zephyr targets |
-| Raw SPI | — | — | — | Feasible — §5 is the whole interface — but §5.6's four workarounds are exactly what a hand-rolled driver silently omits |
-
-### 7.1 RadioLib's structure
-
-Read live from the repository tree, 2026-09-02 **[SRC]** — 409 files:
-
-```
-src/Module.h  src/Hal.h            the porting boundary: implement a Hal, pass a Module
-src/modules/                       CC1101 · LLCC68 · LR11x0 · LR2021 · RF69 · RFM2x ·
-                                   SX123x · SX126x · SX127x · SX128x · Si443x · nRF24
-src/modules/SX126x/
-   SX126x.{cpp,h}                  shared base: BUSY, commands, the four errata fixes
-   SX126x_commands.{cpp,h}         opcode layer
-   SX126x_registers.h              the 16-bit register addresses
-   SX1261.{cpp,h}  SX1262.{cpp,h}  SX1268.{cpp,h}   per-part PA and range limits
-   STM32WLx.{cpp,h}               the SX126x core inside an STM32WL
-   SX126x_LR_FHSS.cpp
-src/protocols/LoRaWAN/             LoRaWAN.cpp · LoRaWANBands.cpp (§3) · package managers
-src/protocols/                     APRS · AX25 · RTTY · SSTV · Morse · Pager · ADSB · …
-```
-
-**The porting story is `Hal.h` and `Module.h`.** A platform integration implements a hardware
-abstraction and hands the library a `Module` — which is precisely what the
-[PaperMono vendor firmware does](../../devices/m5stack/papermono/features/lora.md): a thin
-`RadioLibHal` over the SoC's SPI and GPIO, six pin numbers handed over, and then it gets out of the
-way **[SRC]**. That is the shape to copy.
-
-**`STM32WLx` in the same directory is worth noticing**: the STM32WL is an SX126x core on the same die
-as a Cortex-M, so the same driver serves it. If you are choosing between a discrete radio and an
-integrated SoC, the software cost of that decision is nearly zero with this library. **[INF]**
-
-### 7.2 ⚠ Pinning is not optional, and nobody does it the same way
-
-- **The PaperMono firmware pins RadioLib at `7.2.1`, commit `b91c6af1…`, and *patches* it** to remove
-  `idf_component.yml` so it builds as a plain ESP-IDF component **[SRC]**.
-- **M5Stack's own published PlatformIO snippet pins nothing** — `RadioLib = https://github.com/jgromes/RadioLib`
-  pulls `master` **[DOC]**. Building from the documentation does **not** reproduce the shipped
-  firmware ([Stamp §4](../../components/m5stack/stamp-lora-1262/README.md#4-software)).
-- **Meshtastic pins a raw commit archive**: `[radiolib_base]` in `platformio.ini:121-124` points at
-  `https://github.com/jgromes/RadioLib/archive/510e00cf….zip` **[SRC]**, read live 2026-09-02. That
-  is what "pinned in practice" looks like for a project that must ship.
-- ⚠ **Licence mismatch, flagged not confirmed.** The
-  [Stamp record notes RadioLib as LGPL-3.0 upstream while the M5Stack demo carrying it is MIT](../../components/m5stack/stamp-lora-1262/README.md#4-software),
-  "not verified in this pass". **`library.properties` on `master` today declares `MIT`** and the
-  GitHub API reports `MIT` **[DOC]**, 2026-09-02 — so either the licence changed or the earlier note
-  was mistaken. **Recorded as an unresolved discrepancy, not silently corrected**; the licensing of
-  the *pinned 7.2.1 tree* was not checked and is what would actually matter.
-
----
-
-## 8. Link budget and range, honestly
-
-**Marketing range figures for LoRa are meaningless**, and it is easy to show why with the datasheet's
-own numbers.
-
-```
-TX power (SX1262, max)                       +22 dBm      [DS]
-RX sensitivity, SF12 / BW 125 kHz, boosted   −137 dBm     [DS]
-                                             ─────────
-link budget                                   159 dB      [INF]
-
-Free-space path loss at 868 MHz, 1 km:
-  FSPL = 32.44 + 20·log10(868) + 20·log10(1) = 91.2 dB    [INF]
-Distance for 159 dB, 0 dBi antennas both ends:
-  20·log10(d_km) = 159 − 91.2 = 67.8  ⇒  d ≈ 2 450 km     [INF]
-```
-
-**Nobody gets 2 450 km on the ground.** That gap — between a genuine 159 dB budget and a real result
-of a few kilometres in a town — *is* what "range" means in practice. Everything in it is the
-environment: terrain, buildings, foliage, antenna height, polarisation, body loss, and the fact that
-free-space propagation does not exist near the ground.
-
-**What actually determines range, in descending order of leverage [REC]:**
-
-1. **Antenna height and line of sight.** Dominates everything else. This is why the spectacular LoRa
-   records are balloons and satellites — where the free-space calculation nearly *does* apply.
-2. **Antenna quality and matching**, at both ends. A 4 dB error here is a 60 % distance change in
-   free space and often more in clutter.
-3. **Spreading factor.** 2.5 dB per step (§1.1) — and 2× airtime, and therefore duty-cycle cost.
-4. **Bandwidth.** ~3 dB per halving (§1.2), same airtime cost.
-5. **Transmit power.** The *least* leverage per unit of cost: +8 dB from +14 to +22 dBm costs ~2.6×
-   the transmit current (§4) and is capped by regulation (§3) long before it is capped by silicon.
-
-**Honest estimation procedure [INF]:**
-
-- Compute the budget: `TX dBm − RX sensitivity dBm`, using the sensitivity row for **your** SF *and*
-  BW (interpolating if your BW is not in the table — see §1.2's 62.5 kHz gap).
-- **Subtract 4 dB if the front end has no TX/RX switch** (§5.5) **[DS]**, plus the real switch's
-  insertion loss if it has one, plus connector and cable loss.
-- **Subtract antenna inefficiency at both ends.** A small internal FPC antenna is not 0 dBi.
-- Then **do not convert the remainder to a distance**. Use it comparatively: as a budget to spend on
-  SF, on a better antenna, or on height — and **measure the actual link**, because the propagation
-  term is the only one you cannot compute.
-
-⚠ **The honest state of the evidence in this library:** for the two LoRa devices documented here,
-**no range, throughput, sensitivity, TX current or battery-impact figure exists from the vendor or
-from anyone in the community**
-([G15](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata),
-[E22 §9](../../components/ebyte/e22-900m22s/README.md#9-open-questions)) — verified negatives, not
-oversights.
-
----
-
-## 9. Debugging
-
-### 9.1 Failure signatures
-
-| Symptom | Cause class | Discriminator |
-|---|---|---|
-| `begin()` fails immediately | **Power or reset** | Is the radio's rail actually enabled? Is reset released? On modules with an expander-driven reset, **no I²C means no reset** |
-| Intermittent, timing-dependent SPI corruption | ⚠ **`BUSY` ignored** | §5.2. Driver ported from SX127x. **Check first** |
-| `BUSY` stuck **high** forever | **Never left sleep, or no reference clock** | In sleep `BUSY` is held high through 20 kΩ **[DS]**. If it never falls: the chip is not waking (check `t10`, 100 µs after NSS falls), or the 32 MHz reference never started — see the next row |
-| Initialises cleanly, then **never transmits or receives** | ⚠ **TCXO misconfiguration** | The classic. TCXO configured on a crystal-only design, or a crystal design given no TCXO configuration. §5.4. The [device record calls this out by name](../../devices/m5stack/papermono/features/lora.md) |
-| Init aborts on a device error at every cold start | **`XOSC_START_ERR` treated as fatal** | It is **expected** with a TCXO. Clear it with `ClearDeviceErrors` **[DS]**. §5.4 |
-| Receives fine, **never transmits**, no error anywhere | ⚠ **`SetDio2AsRfSwitchCtrl` not called** | §5.5. On an inverter-based front end the switch sits in RX forever. **Predictable and silent** |
-| Transmits, receives nothing from a known-good peer | **Configuration mismatch** | Sync word, SF, BW, CR, preamble length, header mode, IQ polarity, CRC — **all must match**. SF is orthogonal, so a mismatch is total, not degraded |
-| Works against a new radio, fails against an old one at SF6 | ⚠ **SF6 is not interoperable with SF6 on an SX1276** **[DS]** | SF5/SF6 were redefined in the SX1261/2. Also use **12 preamble symbols** at SF5/SF6 ([G10](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata)) |
-| Sensitivity worse than the datasheet, only at 500 kHz | **Errata §15.1 not applied** | §5.6 |
-| Output power 5–6 dB low | **Errata §15.2 not applied**, or antenna mismatch | §5.6, §6 |
-| Spurious timeouts after an implicit-header receive | **Errata §15.3** | §5.6 |
-| Range collapses as the battery drains | **PA supply droop** | −2 dB at 2.7 V, −6 dB at 1.8 V **[DS]**. §6 |
-| Battery life far worse than expected | **Receive current, not transmit** | §1.5. Check the LDO/DC-DC selection before optimising the transmit path |
-| Radio disappears after a sleep cycle | **Rail was cut** | If the module's supply is gated externally, re-run the entire bring-up; the chip's own sleep modes are a different mechanism |
-| Everything works, throughput is glacial | **SF12 was the default** | §1.4. Change it deliberately |
-
-### 9.2 Two diagnostics worth wiring in early
-
-- **`GetDeviceErrors` (`0x17`) / `ClearDeviceErrors` (`0x18`)** **[DS]**. Read and log them at every
-  init. This is where `XOSC_START_ERR` and PLL/PA problems surface, and most integrations never look.
-- **`GetPacketStatus` (`0x15`) and `GetRssiInst` (`0x14`)** **[DS]**. RSSI *and* SNR on every received
-  packet turn "the link is bad" into a number. SNR against the §1.1 table tells you directly how many
-  spreading-factor steps of margin you have — which is the most actionable diagnostic in LoRa.
-
----
-
-## 10. Choosing a radio
-
-⚠ Rows for parts without a record in this repository are **[REC]**; RadioLib support is **[SRC]**.
-
-| Option | vs SX1262 | Choose when |
-|---|---|---|
-| **Semtech SX1262** | The baseline here: 150–960 MHz, +22 dBm, LoRa + LR-FHSS + (G)FSK, `BUSY` handshake, command interface **[DS]** | Default for new sub-GHz work. Best-documented option in this library |
-| Semtech SX1261 | +14/+15 dBm, PA from `VREG`, DC-DC covers the whole IC **[DS]** | Duty-cycle-limited regions where +22 dBm is illegal anyway, and receive-heavy nodes — its DC-DC helps everywhere |
-| Semtech SX1268 | +22 dBm class, **410–810 MHz** **[SRC]** | 433 MHz and Chinese 470 MHz allocations |
-| **SX1276 / SX1278 (SX127x)** | ⚠ **Not a drop-in.** No `BUSY`, register-based rather than command-based, **entirely different driver** **[REC]**; RadioLib has a separate `SX127x` module **[SRC]** | Only for compatibility with an existing SX127x deployment. ⚠ **SF6 is not interoperable across the generations** **[DS]** |
-| LLCC68 | Cost-reduced SX1262 sibling; **restricted SF/BW combinations** **[REC]**; own RadioLib module **[SRC]** | High volume where the restrictions are acceptable |
-| **Semtech LR1110 / LR11xx** | Adds multi-constellation **GNSS** and **Wi-Fi passive scanning** for geolocation **[REC]**; RadioLib `LR11x0` module **[SRC]** | Asset tracking, where "where is it" beats "how far does it reach" |
-| **STM32WL** | SX126x core **on the same die** as a Cortex-M **[REC]**; RadioLib `STM32WLx` in the SX126x directory **[SRC]** | One chip instead of two, and the same driver |
-| **Ebyte E22-900M22S** (module) | SX1262 **plus external PA/LNA and RF switch**; needs explicit `RXEN`/`TXEN` handling a bare SX1262 does not — [documented here](../../components/ebyte/e22-900m22s/README.md) | More output than a bare chip, with a stamp footprint. ⚠ **worse regulatory headroom**; ⚠ **`E22-...T` variants are a completely different UART product** |
-| **M5Stack Stamp-LoRa-1262** (module) | SX1262 in a 13-pin stamp with an FPC antenna — [documented here](../../components/m5stack/stamp-lora-1262/README.md) | M5Stack ecosystem. ⚠ **no module datasheet exists**; RF output, antenna gain, matching, TCXO and internal DIO use are all undocumented (G1) |
-| **RAK3172 / RAK4630** (module) | SX1262 **plus an MCU** running the stack inside the module **[REC]** | When you want the LoRaWAN stack to be someone else's problem |
-
-**The selection question that actually matters** is not which radio — the SX126x family answers that
-for most sub-GHz work — but **where the stack runs and who owns certification**. A bare chip gives
-maximum control and maximum obligation. A module with an MCU inside gives you a stack and possibly a
-modular approval. A module without one, like both documented here, gives you neither, plus an
-undocumented matching network.
-
-⚠ **Module-level certification does not transfer automatically** into your product with your antenna
-([E22 §5](../../components/ebyte/e22-900m22s/README.md#5-regulatory-notes)) **[GAP]** in that record —
-and for both modules documented here, **no certification of any kind is published at all** **[DOC]**.
-
----
-
-## 11. Device-specific pages
-
-| Device | Radio | Applicability |
-|---|---|---|
-| [**M5Stack PaperMono**](../../devices/m5stack/papermono/features/lora.md) | SX1262 inside a `Stamp-LoRa-1262` module | **Applies with deltas** — RadioLib is not given the reset pin (it is behind an expander), the module's rail is gated externally, `DIO2`/`DIO3` are consumed inside the module, and the vendor default is a maximum-range SF12 configuration |
-| [Nicolai Electronics Tanmatsu](../../devices/nicolai-electronics/tanmatsu/README.md) | SX1262 inside an [Ebyte E22-900M22S](../../components/ebyte/e22-900m22s/README.md) | **Applies with deltas** — external PA/LNA with inverter-generated `RXEN`, the radio belongs to a companion SoC rather than the application processor, and a **different module is fitted on 433 MHz units** |
-| [M5Stack PaperMono-Lite](../../devices/m5stack/papermono-lite/README.md) | **none fitted** | Not applicable |
-
----
-
-## 12. Evidence boundary — and what could not be sourced
-
-**No measurement anywhere in this guide.** Inherited claims come from the
-[SX1262](../../components/semtech/sx1262/README.md),
-[Stamp-LoRa-1262](../../components/m5stack/stamp-lora-1262/README.md) and
-[Ebyte E22-900M22S](../../components/ebyte/e22-900m22s/README.md) records and the
-[PaperMono LoRa feature guide](../../devices/m5stack/papermono/features/lora.md) as they stood on
-**2026-09-02**, carrying their labels transitively.
-
-**New to this page, live-verified 2026-09-02 [SRC]/[DOC]:** the RadioLib module and protocol layout;
-the per-part power and frequency ranges at `SX1261.cpp:42`, `SX1262.cpp:179,212`,
-`SX1268.cpp:180,213`; **all four errata workarounds and their call sites** (§5.6, resolving
-[G4](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata) for current RadioLib);
-`getTimeOnAir` at `SX126x.h:634` / `SX126x.cpp:812`; the **entire §3 band table** from
-`LoRaWANBands.cpp`; Meshtastic's pinned RadioLib commit at `platformio.ini:121-124`; and every
-maintenance and licence status in §7.
-
-**New and derived here [INF]:** the §1.1 "2.5 dB per SF step" reading; the §1.4 symbol-time and
-bit-rate tables and their cross-check against the recalled LoRaWAN DR table; the §1.4 airtime
-estimate for the vendor configuration; the §1.5 receive-dominates-transmit arithmetic; the §3
-"a dozen frames per hour" and "US915's 400 ms dwell cap forbids SF12/125 kHz" conclusions; the §8
-link-budget and free-space calculation.
-
-### Claims I could not source
-
-| Claim | Why it is unsourced | Risk if wrong |
-|---|---|---|
-| **"A LoRa symbol carries `SF` raw bits" (§1.4)** | The datasheet gives `2^SF` **chips** per symbol and `Rs = BW/2^SF`; the bits-per-symbol step is standard CSS theory with no document here | **Low** — the derived rates reproduce the recalled LoRaWAN DR table to within rounding, which is a strong check |
-| **The LoRaWAN DR0–DR5 rates used as a cross-check (§1.4)** | LoRa Alliance **RP002 Regional Parameters** is not held | Low; it is a check, not a load-bearing claim |
-| **The exact closed-form airtime formula** | Semtech application notes (`AN1200.13` and relatives) are **not held** — and [Semtech's document portal is `blocked`](../../components/semtech/sx1262/README.md#11-sourcing) | **Low, because it is avoided**: §1.4 gives an order-of-magnitude estimate and points at `getTimeOnAir()` for the real number |
-| **All regional/legal detail beyond RadioLib's table (§3)** | ETSI EN 300 220, FCC Part 15.247/15.249, ARIB T-108 and RP002 are **all** unheld. RadioLib's table is a *library's* encoding of them, which is evidence about the library first and the law second | **High if relied upon.** Read the regulation. The 1 % / 36 s and 400 ms figures are sourced *as RadioLib constants* |
-| **LoRaWAN device-class behaviour (§2)** | Recalled; the specification is not held | Low for the architectural point |
-| **Meshtastic's mesh and preset behaviour (§2)** | Only the RadioLib pin was read from its repository; the protocol was not | Low |
-| **SX1268 PA topology, LLCC68 restrictions, SX127x architecture, LR11xx and STM32WL capability (§4, §10)** | No datasheet held for any of them. RadioLib's enforced ranges *are* sourced and are the strongest evidence in those rows | **Moderate** — the table decides part selection |
-| **50 Ω / ground-plane / layout guidance (§6)** | General RF practice; no document behind it here. `AN1200.37` "Recommendations for Best Performance" is cited by the datasheet itself and **was not located at all** | Moderate for a real design review |
-| **Zephyr's `sx126x.c` status (§7)** | Not checked live this pass, unlike every other row | Low |
-| **Whether the *pinned* RadioLib 7.2.1 applies the four workarounds (§5.6)** | Only `master` was read | **Moderate** — it is the version actually shipping on a documented device |
-
-### Where this guide sits relative to the deep records
-
-**No contradiction was found.** Three things to feed back:
-
-1. **§5.6 resolves [SX1262 G4](../../components/semtech/sx1262/README.md#10-caveats-gaps-and-errata)
-   for current RadioLib** — all four §15 workarounds are implemented, and `fixPaClamping` is
-   correctly SX1262/SX1268-only. The gap remains open for the pinned 7.2.1.
-2. **§7.2 records a discrepancy on RadioLib's licence.** The
-   [Stamp record flags LGPL-3.0 upstream, "not verified"](../../components/m5stack/stamp-lora-1262/README.md#4-software);
-   `master` today declares **MIT**. Recorded as unresolved rather than corrected — the pinned tree
-   was not checked, and that is the one that matters.
-3. **§1.4's derived rate for the vendor configuration (≈92 bit/s, ≈76 with LDRO) agrees with the
-   SX1262 record's "tens of bits per second"** characterisation. Agreement, not conflict — noted so
-   the arithmetic is available if anyone needs the number rather than the adjective.
-
----
-
-## Related
-
-- [**Semtech SX1262**](../../components/semtech/sx1262/README.md) — the deep record: opcodes, `BUSY` timing, DIO2/DIO3, LDO vs DC-DC, sensitivity and current tables, the four errata
-- [**M5Stack Stamp-LoRa-1262**](../../components/m5stack/stamp-lora-1262/README.md) — a module with **no datasheet**, and what that costs
-- [**Ebyte E22-900M22S**](../../components/ebyte/e22-900m22s/README.md) — SX1262 with an external PA/LNA; the canonical `DIO2`-plus-inverter RF-switch pattern, and the band-variant trap
-- [M5Stack PaperMono — LoRa feature guide](../../devices/m5stack/papermono/features/lora.md) — the device-specific companion to this page
-- [Nicolai Electronics Tanmatsu](../../devices/nicolai-electronics/tanmatsu/README.md) — the other documented LoRa device
-- [**NFC — a device-independent guide**](../nfc/README.md) — the other radio on the PaperMono; the same command-byte, mandatory-errata and undocumented-module patterns recur there
-- [Guides index](../README.md) · [Components index](../../components/README.md) · [Devices index](../../devices/README.md)
-- [Vendor sourcing guides](../../vendors/README.md) — ⚠ **no Semtech and no Ebyte guide exists yet**; [SX1262 §11](../../components/semtech/sx1262/README.md#11-sourcing) and [E22 §8](../../components/ebyte/e22-900m22s/README.md#8--documentation-gaps--both-primary-documents-are-missing) are what one would open with
diff --git a/guides/markets/README.md b/guides/markets/README.md
index 575a3a7..f080ce2 100644
--- a/guides/markets/README.md
+++ b/guides/markets/README.md
@@ -12,7 +12,6 @@ be hosting the schematic next year.
 |---|---|
 | [**Vendor and marketplace comparison**](vendor-comparison.md) | Waveshare, Seeed Studio, M5Stack, Adafruit, SparkFun, DFRobot, LilyGO, Espressif official, AliExpress/Taobao, Amazon/eBay, Guition, HAOYU, and the component distributors (LCSC, Mouser, Digi-Key). What each actually sells (own designs vs resale vs clones), documentation quality, schematic and EDA-source availability, licensing posture, shipping origin, and **long-term file-hosting reliability** |
 | [**Clones, siblings and variants**](clones-and-variants.md) | Spotting a clone from a listing photo; what actually differs (swapped GPIO, substituted display and touch controllers, different flash/PSRAM sizes, omitted regulators and discretes, re-marked parts); a five-minute triage procedure; how to trace an unlabelled board back to a documented design; and a worked example — the **Guition JC3636K518** as a sibling of the [Waveshare ESP32-S3-Knob-Touch-LCD-1.8](../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) |
-| [**Handheld and e-ink device landscape, 2026-09**](handheld-and-eink-device-landscape-2026-09.md) | Every device record in this library, grouped the way somebody actually shops: **pocket e-ink readers** (Xteink X3/X4/X4 Pro/X4 Classic, M5Stack PaperMono and PaperMono Lite, ZeroWriter Ink/Fold, Waveshare ESP32-S3-ePaper-3.97), **keyboard handhelds** (Cardputer v1.1 and ADV, LilyGO T-Display K230 Kit, Tanmatsu), **display dev boards** (the LilyGO T-Display-S3 family, the Waveshare knob board, XIAO ESP32S3 Sense) and **LoRa/mesh add-ons** (Cap LoRa-1262, Cap LoRa868, Cap CC1101, Unit C6L, Stamp-C6LoRa, the E220 and STM32WLE5 units). Like-for-like tables **with dated prices**, then prose on who should buy which — and explicit statements of where the evidence does not support a comparison. Complements the per-feature [device comparison matrix](device-comparison-matrix.md). *Added 2026-09-07* |
 
 ---
 
@@ -23,14 +22,6 @@ invented figure is worse than none. Relative positioning claims are labelled **[
 [vendor-comparison.md § A note on prices](vendor-comparison.md#a-note-on-prices) for the citation
 format to use if you add one.
 
-> **Scope correction, 2026-09-07.** Point 1 above describes the three guides written in the
-> 2026-08-24 pass and is still accurate for them. It does **not** apply to
-> [handheld-and-eink-device-landscape-2026-09.md](handheld-and-eink-device-landscape-2026-09.md),
-> which carries **dated, sourced observed prices** gathered in the 2026-09-04/07 pass, each with
-> seller, date, region and configuration in the format `vendor-comparison.md` prescribes. Read
-> that guide's own evidence-boundary section for its sampling limits — in particular that no
-> marketplace or used-market sampling was done for most devices.
-
 **2. We have not handled a clone board.** The identification methodology in
 [clones-and-variants.md](clones-and-variants.md) is derived from documented failure modes, not from
 validated practice. Its one well-evidenced section is the Guition/Waveshare comparison, which rests
diff --git a/guides/markets/handheld-and-eink-device-landscape-2026-09.md b/guides/markets/handheld-and-eink-device-landscape-2026-09.md
deleted file mode 100644
index 5872a9a..0000000
--- a/guides/markets/handheld-and-eink-device-landscape-2026-09.md
+++ /dev/null
@@ -1,583 +0,0 @@
-# Handheld and e-ink device landscape — September 2026
-
-> **What to buy, for what, as of 2026-09-07.** Every device record in this
-> repository, grouped by the thing a buyer is actually shopping for rather than by
-> vendor.
->
-> **Nothing here is a new measurement or a new retrieval.** Every cell is read out
-> of the linked device or component record. Where a record marks something
-> `unknown`, this page marks it `unknown` too — it does not fill the gap.
-
-## How to read this page
-
-This is an **aggregation**, not a source. Where a cell disagrees with the record
-it links to, **the record wins** — the standing rule from
-[the guides index](../README.md#conventions).
-
-**"—" means the device does not have the thing. "unknown" means no record
-establishes it.** The distinction is load-bearing throughout: an absent frontlight
-is a design decision, an absent battery capacity is a research gap.
-
-Prices are **item-only, vendor-direct, before shipping and duty**, on the date
-given in each table. They are not normalised across currencies or tax regimes;
-[the PaperMono pricing record](../../devices/m5stack/papermono/market-and-pricing.md)
-explains why a GBP-inclusive figure and a USD-exclusive figure are not the same
-kind of number even before an exchange rate is applied.
-
-### Relationship to the existing comparison matrix
-
-[`device-comparison-matrix.md`](device-comparison-matrix.md) already compares
-fourteen devices column-by-column and is the better page if you want raw
-specification cells for the Waveshare/Espressif P4 boards, the Inkplates, the
-XIAO, ZeroWriter and Tanmatsu. **It was compiled 2026-08-30 and predates the
-Xteink, M5Stack Cardputer/PaperMono/Cap and LilyGO research passes**, so it does
-not contain them.
-
-This page is complementary and differently shaped:
-
-| | [Comparison matrix](device-comparison-matrix.md) | This page |
-|---|---|---|
-| Organised by | Specification axis (processors, memory, display…) | **What you are shopping for** |
-| Covers | 14 devices, as of 2026-08-30 | **Every device record**, as of 2026-09-07 |
-| Ends in | Conflicts between records | **Prose recommendations, and where a comparison is not supportable** |
-
-Read the matrix for cells; read this for decisions. Neither is a substitute for
-the device record.
-
----
-
-## Group 1 — Pocket e-ink readers
-
-The question this group answers: *I want a small, battery-powered, e-ink thing to
-read on, and I want to be able to reflash it.*
-
-### 1.1 The table
-
-Prices dated **2026-09-04** (Xteink, from the vendor store API) and **2026-09-01**
-(M5Stack, Waveshare) and **2026-08-24** (ZeroWriter).
-
-| | [Xteink X3](../../devices/xteink/x3/README.md) | [Xteink X4](../../devices/xteink/x4/README.md) | [Xteink X4 Pro](../../devices/xteink/x4-pro/README.md) | [Xteink X4 Classic](../../devices/xteink/x4-classic/README.md) | [M5Stack PaperMono](../../devices/m5stack/papermono/README.md) | [PaperMono-Lite](../../devices/m5stack/papermono-lite/README.md) | [Waveshare ESP32‑S3‑ePaper‑3.97](../../devices/waveshare/esp32-s3-epaper-3.97/README.md) | [ZeroWriter Ink](../../devices/zerowriter/zerowriter-ink/README.md) | [ZeroWriter Fold](../../devices/zerowriter/zerowriter-fold/README.md) |
-|---|---|---|---|---|---|---|---|---|---|
-| **SoC** | ESP32‑C3 (RISC‑V) | ESP32‑C3 | **ESP32‑S3** (Xtensa) | **ESP32‑S3** | ESP32‑S3R8 | ESP32‑S3R8 | ESP32‑S3R8 (`WROOM‑1‑N16R8`) | **ESP32‑WROVER ×1 + ESP32‑WROOM‑32U ×1** | unknown ("in‑house") |
-| **SRAM / PSRAM / flash** | 400 KB / **none** / 16 MB | 400 KB / **none** / 16 MB | 512 KB / **8 MB** / 16 MB | 512 KB / **8 MB** / 16 MB | 512 KB / **8 MB OPI** / 16 MB | same | 512 KB / **8 MB octal** / 16 MB | WROVER (PSRAM in module) / unknown | unknown |
-| **Panel** | 3.7″ **792×528, ~257 PPI**, UC8253 *or* UC8279d | 4.26″ 800×480, ~219 PPI, SSD1677/UC8179/UC8279 | 4.26″ 800×480, same three | 4.26″ 800×480, same three | 3.97″ 480×800, **235 DPI**, DKE panel + SSD1677 | same | 3.97″ 800×480, 235 DPI, SSD1677 | 5.2″ **1280×720** `ED052TC4` | 6″, resolution unknown |
-| **Greyscale** | 1 bpp | 1 bpp | 1 bpp | 1 bpp | **4 levels** (vendor claim; panel manual says 2 — unresolved) | same | **4 levels** | unknown | unknown |
-| **Frontlight** | — | — | **dual warm/cool** | — | **yes**, AW9967 boost | **yes** | — | — | **yes, 10 levels** (claim) |
-| **Touch** | — | — | **GT911** | — | **FT6336G** | **FT6336G** | — | — | unknown |
-| **Other input** | 6 buttons on a **2‑pin ADC ladder** + power | same | **2 side keys** + capacitive Home pad | **7 discrete ISR GPIOs** | 2 keys + power | 2 keys + power | **3‑way rotary nav** + PWR + BOOT | **60 % hot‑swap mechanical keyboard** | Choc v1 hot‑swap keyboard |
-| **Radios** | Wi‑Fi + BLE | Wi‑Fi + BLE | Wi‑Fi + BLE | Wi‑Fi + BLE | Wi‑Fi + BLE **+ NFC (ST25R3916) + LoRa (SX1262)** | Wi‑Fi + BLE | Wi‑Fi + BLE | Wi‑Fi/BT present, **off by default** | claims "no Wi‑Fi required" |
-| **Other sensors** | **BQ27220 gauge**, DS‑series RTC, **QMI8658 IMU**, **passive NFC tag** | none | BM8563 RTC, CW2017 gauge | BM8563, CW2017, **QMI8658 IMU** | BMI270, RX8130CE RTC, PDM mic, buzzer | same | QMI8658A, PCF85063ATL, **SHTC3**, ES8311 + NS4150B audio | RTC | unknown |
-| **Battery** | **650 mAh** | unknown | unknown | unknown | **1150 mAh** | 1150 mAh | header only, **capacity unknown** | claim ~100 h | claim 50–100 h |
-| **Storage** | microSD on the **display SPI bus** | same, **no power enable** | **native SDMMC** | **native SDMMC** | microSD, 4‑bit SDMMC | same | microSD | microSD | microSD |
-| **Expansion** | — (sealed) | — | — | — | **none — no Grove, no M‑Bus** | none | **none** (vendor claim of expansion is [refuted](../../devices/waveshare/esp32-s3-epaper-3.97/gaps-and-conflicts.md)) | — | — |
-| **Price** | **$69** | **delisted**, last $69 | **$99** | **never priced** | **$65** *(out of stock 2026‑09‑01)* | **$55** *(out of stock)* | **$34.99–47.99**, 3 SKUs | **$285** | ~$239 first wave / ~$329 |
-| **Vendor's own material** | **Nothing.** No schematic, no SDK, no datasheet; product copy demonstrably false | same | same | same | **6‑sheet schematic**, MIT UserDemo, pinned libraries — but [NFC sheet 1 of 2 unpublished](../../devices/m5stack/papermono/features/nfc.md) | 4‑sheet `PRJ`, not retrieved | Schematic published; sample repo **has no `LICENSE`** → `unknown` | KiCad design published; **application firmware binaries only** | none yet; "open source in the coming months" |
-| **Record depth here** | deep | deep | deep | medium | **deepest in the repo** | variant record | full | full | vendor-claims overview |
-
-### 1.2 What the table hides
-
-**"X4 Pro" is not an enhanced X4, and the naming is actively misleading.** They
-share a screen size and a brand. Different ISA (Xtensa LX7 vs RISC-V), different
-flash layout, different input hardware, different charging connector.
-[CrossPlay had to repoint its OTA URL](../../software/applications/crossplay/README.md)
-specifically because upstream's release would flash a C3 image onto an S3. Treat
-them as unrelated computers that happen to be sold by the same shop.
-
-**The cheapest Xteink has the sharpest screen and the most sensors.** The X3 at
-$69 is ~257 PPI against ~219 for the 4.26″ models, is 55 g against ~80 g, and is
-the only one with a proper TI impedance-track fuel gauge, an IMU and an NFC tag.
-The "Pro" has none of the last three. A price-ordered reading of that family is
-wrong in three separate places.
-
-**The frontlight/touch premium is $30 and it costs you the USB-C port.** The X4
-Pro charges over a proprietary magnetic pogo connector and ships needing a $4.99
-cable. This is the single most-complained-about design decision in that community
-([community record](../../devices/xteink/x4-pro/community.md)). The X4 — the only
-Xteink with USB-C charging — is delisted and its accessories are exhausted.
-
-**The PaperMono is not competing with the Xteinks on price and should not be
-compared to them on it.** At $65 it is roughly an X3 plus $0, but it is a
-*development board*: published schematic, USB-C, a documented power architecture,
-and no USB lock. It also has NFC and LoRa fitted, which nothing else in this group
-does. What it does not have is an expansion connector of any kind, an enclosure
-ecosystem, or stock. It was out of stock at the official store on 2026-09-01 and
-listed by no reseller anywhere.
-
-**Two boards in this group carry a "3.97-inch 4-greyscale SSD1677" panel with the
-same active area to 0.01 mm, transposed** — the PaperMono (480×800) and the
-Waveshare (800×480). The Waveshare record asks whether they are the same glass and
-[does not resolve it](../../devices/waveshare/esp32-s3-epaper-3.97/README.md). Do
-not assume waveforms transfer.
-
-**ZeroWriter is in this group because the brief put it here, and it does not
-belong.** The Ink is a 300 × 195 × 15 mm slab with a mechanical keyboard, and the
-Fold is 900 g and opens like a laptop. Neither is pocketable and neither is a
-reader — they are writing appliances with a text editor and no browser, and the
-Fold's marketing is explicit that refusing features is the product. If you want to
-*read*, they are the wrong purchase at four times the price.
-
-### 1.3 ⚠ Comparisons this group does **not** support
-
-State these plainly rather than inventing precision:
-
-- **Battery life cannot be compared for any device here.** Only the X3
-  (650 mAh) and the PaperMono (1150 mAh) have a published capacity, the Waveshare
-  publishes none at all, and **no device in this repository has a measured
-  runtime, refresh-power figure or frontlight current from anyone**. The X3
-  teardown author explicitly planned to attach a Nordic Power Profiler Kit II and
-  never posted results.
-- **Refresh speed cannot be compared across vendors.** The Xteink figure
-  (~38 ms plane write at 20 MHz) is an SDK source comment for a *plane write*; the
-  Waveshare figures (3.5 s full / 0.6 s partial) are whole-refresh vendor claims
-  and its own panel manual disagrees with its board page; M5Stack publishes four
-  refresh timings with no method. These are three different quantities.
-- **"4-level greyscale" is not established on the PaperMono.** M5Stack claims it
-  and the vendor demo implements it, but the DKE panel manual's own optical table
-  reads `GN — 2Grey Level`. Recorded unresolved.
-- **Price-per-pixel comparisons are meaningless here** because the Xteink price
-  includes an enclosure, a battery, a case ecosystem and a charging accessory
-  market, and the Waveshare and PaperMono prices do not include an enclosure at
-  all in the Waveshare's case. A community member's open-source ESP32-S3 e-paper
-  dev kit came out at a *"full unit BOM around $60 including display and battery"*
-  — roughly the price of a finished X4.
-
-### 1.4 Who should buy which
-
-**Buy an [Xteink X3](../../devices/xteink/x3/README.md) at $69** if you want the
-sharpest, lightest pocket reader that has a large live firmware ecosystem, and you
-can live with pogo-pin charging and mushy buttons. It is also the best of the
-family as a *sensor* platform — gauge, RTC, IMU and an NFC tag — if you are
-building something rather than only reading.
-
-**Buy an [Xteink X4 Pro](../../devices/xteink/x4-pro/README.md) at $99** only if
-you specifically want touch *and* a frontlight in a sealed pocket device. You are
-paying $30 for those two things and losing an IMU and USB-C charging. It is also
-the ecosystem's design floor — CrossPlay names it as the reference target — so it
-is the best-supported S3 target.
-
-**Buy a [PaperMono](../../devices/m5stack/papermono/README.md) at $65** if you
-intend to *develop*. You get a published schematic, a documented five-state power
-architecture, USB-C, no unlock dance, and NFC and LoRa hardware nobody else in this
-group fits. Accept that you get no enclosure ecosystem, no expansion header, and —
-at the snapshot — no stock.
-
-**Buy the [Waveshare ESP32-S3-ePaper-3.97](../../devices/waveshare/esp32-s3-epaper-3.97/README.md)
-at $34.99** if you want the cheapest credible ESP32-S3 + PSRAM + e-paper platform
-and you do not need a case, a frontlight or touch. Note two corrections that record
-makes to its own vendor's marketing: **the PMIC is an AXP2101, not the "TG28" the
-storefront names**, and **the board has no expansion header of any kind**.
-
-**Do not buy an [X4](../../devices/xteink/x4/README.md) new** — you cannot; it is
-delisted. Buy one used only if USB-C charging matters more to you than everything
-else, and note that **at least two X4 board revisions exist that are not externally
-distinguishable**, one of which does not self-latch its battery MOSFET.
-
-**Do not buy an [X4 Classic](../../devices/xteink/x4-classic/README.md)** — not
-because it is bad (S3 + PSRAM + six real buttons + an IMU is the best silicon
-combination in the family) but because it has never been listed internationally,
-has no published price, and no photograph of it exists anywhere.
-
-**One warning that applies to every Xteink purchase:** USB-lock state is **not
-predictable from the sales channel**. One owner reported an Amazon X3 unlocked, an
-official-store X3 locked and an AliExpress X4 locked. Assume you will need the
-unlock procedure; see [`firmware-ecosystem.md`](../../devices/xteink/firmware-ecosystem.md).
-
----
-
-## Group 2 — Keyboard handhelds
-
-The question: *I want a pocket computer with a real keyboard.*
-
-### 2.1 The table
-
-| | [Cardputer v1.1](../../devices/m5stack/cardputer-v1.1/README.md) | [Cardputer ADV](../../devices/m5stack/cardputer-adv/README.md) | [T-Display K230 Kit](../../devices/lilygo/t-display-k230/README.md) | [Tanmatsu](../../devices/nicolai-electronics/tanmatsu/README.md) | [CardputerZero](../../devices/m5stack/cardputer-zero/README.md) |
-|---|---|---|---|---|---|
-| **Class** | MCU | MCU | **Linux** | MCU | **Linux** |
-| **SoC** | ESP32‑S3FN8 | ESP32‑S3FN8 | **Canaan Kendryte K230**, 2× RV64 C908 (1.6 GHz + 0.8 GHz) | **ESP32‑P4NRW32**, 2× RISC‑V | **Raspberry Pi CM0** (RP3A0, 4× Cortex‑A53) |
-| **RAM / PSRAM / flash** | 512 KB / **none** / 8 MB in‑package | 512 KB / **none** / 8 MB in‑package | **1 GB LPDDR4** / — / microSD boot | **32 MB in‑package PSRAM** / 16 MB flash | **512 MB LPDDR2** / microSD only |
-| **Display** | 1.14″ 240×135 IPS, ST7789V2 | same | **4.1″ 568×1232 AMOLED**, RM69A10, MIPI DSI | 3.97″ 480×800 IPS, ST7701S, **MIPI DSI 2‑lane** | 1.9″ 320×170, ST7789v3 |
-| **Keyboard** | 56 keys, **74HC138 GPIO matrix (10 GPIOs)** | 56 keys, **TCA8418 over I²C (3 GPIOs)** | **QWERTY on a separate base board**, TCA8418 7×10 | **69‑key QWERTY** + 6 function keys, backlit, by Solder Party | 46 keys, TCA8418 |
-| **Other input** | — | **BMI270 IMU** | GT9895 touch, GC2093 camera | — | touch, IMX219 camera, BMI270 + BMM150 |
-| **Radios** | Wi‑Fi + BLE | Wi‑Fi + BLE | **RTL8189FS Wi‑Fi (SDIO)**, BT **via USB dongle only**, SX1262 *or* **LR2021** LoRa, nRF9151 LTE‑M/NB‑IoT + GNSS, nRF52840 BLE | ESP32‑C6 (Wi‑Fi 6 / BLE 5.3 / 802.15.4) + **Ebyte E22 SX1262 LoRa** | Wi‑Fi + **10/100 Ethernet** (SR9900A) |
-| **Audio** | NS4168 + SPM1423 PDM mic | **ES8311 codec** + NS4150B + 3.5 mm jack | MAX98357A + mic | yes | ES8389 + AW8737A + **3.5 mm TRRS** |
-| **Battery** | 120 mAh + **1400 mAh base** | **1750 mAh** | 21700 pack (base‑dependent) | unknown here | **1750 mAh** |
-| **Expansion** | Grove only | Grove + **EXT 2.54‑14P "Cap" socket** | **2×20 header** + two base boards + RJ45 | **36‑pin expansion port** | **EXT 2.54‑14P (not Cap‑compatible)** + Grove |
-| **Price** | **$29.90, `[EOL]`** | **$29.90** | main unit **$150.31** (SX1262) / **$153.01** (LR2021) · keyboard base **$113.25** with nRF9151 / **$70.94** without → **$263.56 complete** | **€99.17 ex VAT / €119.99 inc** | **not established** |
-| **Openness** | Schematics published; `M5Cardputer` MIT | Schematics published; MIT libs; **no certification published** | **BSP published 17 months after launch**; **no schematic at all** | **Full KiCad under CERN‑OHL‑P, firmware MIT** — the most open device in this repository | Schematic published, **not fetched**; vendor says features subject to change |
-| **Depth here** | medium | **full** | **full** | full | light — product unfinished |
-
-### 2.2 What the table hides
-
-**The ADV is not "a faster Cardputer" — it is the same SoC with a different
-keyboard controller, and that is the entire point.** Moving the 56-key matrix from
-a 74HC138 (10 GPIOs) to a TCA8418 on I²C (3 GPIOs) frees **seven pins**, and those
-seven pins *are* the Cap header. The compute is identical. If someone tells you the
-ADV is faster, they have not read the schematic — both are ESP32-S3FN8, both have
-**no PSRAM**, both are 8 MB flash.
-
-**No Cardputer has PSRAM, and this shapes every ambitious project on the
-platform.** The Meshtastic-client author memory-mapped a 2.16 MB Unicode font out
-of a flash partition because it cannot live in RAM. If your application needs a
-framebuffer or a large working set, this family is the wrong answer at any price.
-
-**"T-Display K230 Kit" is two purchases and the store does not say so.** "Main
-Unit" and "Keyboard Only" are separate SKUs. A complete keyboard handheld with
-cellular is **$263.56** before shipping — 2.6× the sticker price a casual reader
-takes away, and 8.8× a Cardputer ADV. A Reddit user on the launch thread asked
-exactly which SKU to buy and got no answer.
-
-**The K230 is the only device in this group where "nothing in the ESP32 ecosystem
-applies"** — no Arduino, no PlatformIO for the main SoC, no ESP-IDF, a vendor
-toolchain at a hard-coded `/opt/toolchain`, and a documented case of a board
-bricked with **no recovery section in any LilyGO document**. It is also the only
-one with a real NPU, H.265 encode *and* decode, and a Linux userspace.
-
-**Tanmatsu is a different class of machine and priced accordingly.** ESP32-P4 with
-**32 MB of in-package PSRAM**, MIPI DSI, a 69-key backlit keyboard designed by
-Solder Party, a 36-pin expansion port, and — uniquely here — the complete KiCad
-design published under CERN-OHL-P with MIT firmware. At ~€120 it is 4× a Cardputer
-ADV and buys you compute, openness and a much better keyboard.
-
-**CardputerZero is the same shape as a Cardputer and is not one.** It is a
-Raspberry Pi CM0 running Linux. Its EXT header is physically identical to the
-ADV's and **electrically different** — the left column and the UART pair are not
-the same, so a Cap that uses `RESET`/`INT`/`BUSY` (i.e. both M5Stack Caps) will not
-work on it. M5Stack's own page carries a "work in progress" banner.
-
-### 2.3 ⚠ Comparisons this group does **not** support
-
-- **No performance comparison is possible between the K230 and the P4.** No
-  independent benchmark of the T-Display K230 exists — the BSP *builds CoreMark
-  and CoreMark-PRO into the image* and nobody has published a number. The P4's
-  6.92 CoreMark/MHz is Espressif's own figure under Espressif's own build. These
-  cannot be put in the same table.
-- **Battery life is unmeasured on all five.** The Cardputer ADV's ~13–14 h Wi-Fi
-  figure is arithmetic on vendor current claims and **ignores backlight**, which
-  the record says is likely to dominate. K230 battery life is unmeasured and the
-  only community input is scepticism.
-- **Keyboard quality cannot be compared from records.** Nobody in this repository
-  has typed on more than one of these.
-
-### 2.4 Who should buy which
-
-**Buy a [Cardputer ADV](../../devices/m5stack/cardputer-adv/README.md) at $29.90**
-unless you have a concrete reason not to. It is the cheapest keyboard computer here
-by a factor of four, it has the broadest community firmware support, its Cap socket
-is a genuine expansion bus in the exact shape an SX1262 or CC1101 wants, and board
-autodetect means one binary serves both generations. Do not buy the
-[v1.1](../../devices/m5stack/cardputer-v1.1/README.md) at the same price — it is
-`[EOL]` and strictly worse — **unless** you need a firmware that has not been
-ported (Evil-M5Project's ADV support is unconfirmed; NEMO has no ADV config).
-
-**Buy the [Cardputer Mesh Kit](../../devices/m5stack/cardputer-mesh-kit/README.md)
-at $48** instead of the parts if you want the Meshtastic licensed-device
-registration; the bundle premium over ADV + Cap is $3.60 and registration is
-**restricted to the kit**. If the badge does not matter, buy the parts.
-
-**Buy a [Tanmatsu](../../devices/nicolai-electronics/tanmatsu/README.md) at ~€120**
-if you need compute, a proper keyboard, or openness. It is the only device in this
-repository whose full hardware design you can read, modify and rebuild.
-
-**Buy a [T-Display K230](../../devices/lilygo/t-display-k230/README.md)** only if
-you specifically need on-device Linux with an NPU and a MIPI camera, or specifically
-want RISC-V, and you are comfortable building an image on Ubuntu with a vendor
-toolchain and no documented recovery path. Do not buy it as a Meshtastic node — a
-$30 dedicated node does that better and lasts far longer on a charge.
-
-**Do not buy a [CardputerZero](../../devices/m5stack/cardputer-zero/README.md)
-yet.** The vendor says its features are subject to change.
-
----
-
-## Group 3 — Display development boards
-
-The question: *I want an MCU with a screen on it that I can program.*
-
-### 3.1 The table
-
-The [T-Display-S3 family](../../devices/lilygo/t-display-s3-shared/README.md) is
-**eleven electrically distinct boards sharing a marketing prefix**, so it is
-summarised as a family with the reference board broken out. Prices dated
-**2026-09-07** (LilyGO), **2026-08-21** (Waveshare knob), **2026-08-24** (XIAO).
-
-| | [T-Display-S3](../../devices/lilygo/t-display-s3/README.md) (reference) | T-Display-S3 family (10 others) | [Waveshare Knob-Touch-LCD-1.8](../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) | [XIAO ESP32S3 Sense](../../devices/seeed-studio/xiao-esp32s3-sense/README.md) |
-|---|---|---|---|---|
-| **SoC** | ESP32‑S3R8 **bare die** | ESP32‑S3R8 on every board | ESP32‑S3R8 **+ a second full SoC, ESP32‑U4WDH** | ESP32‑S3R8 |
-| **RAM / PSRAM / flash** | 512 KB / 8 MB OPI / 16 MB W25Q128JV | same throughout | 512 KB / 8 MB / 16 MB (+ 4 MB on the U4WDH) | 512 KB / 8 MB / 8 MB |
-| **Display** | 1.9″ 170×320 ST7789V on an **8‑bit Intel‑8080 parallel** bus | **eight different controllers** across QSPI, parallel and 4‑wire SPI | 1.8″ **round 360×360**, ST77916 *or* SH8601 (unresolved) | **none** |
-| **Touch** | — | CST816S · CST328 · CST226SE · CST3530 · CST9217 · FT3168 · CHSC5816 · AXS15231B | CST816D | — |
-| **Other input** | BOOT + GPIO14 | not portable between boards | **two directional knobs, one per MCU** | — |
-| **Radios** | Wi‑Fi + BLE | Wi‑Fi + BLE | Wi‑Fi + BLE **+ Bluetooth Classic (on the U4WDH only)** | Wi‑Fi + BLE |
-| **Notable** | — | **PMIC differs per board**: TP4065 / SY6970 / BQ25896 / AXP2101 | DRV2605L haptics, PCM5100A DAC, PDM mic, **USB‑C plug orientation selects which MCU you talk to** | **camera + PDM mic + microSD daughterboard**, 21 × 17.8 mm |
-| **Expansion** | header pins | varies | two PH1.27 10‑pin headers, **pinout not published** | castellated + B2B |
-| **Price** | **$9.04** bare / $12.61 Touch / $13.22 with shell | varies | not captured in the record | **$13.99** (+ $11.99 OV5640 option) |
-| **Openness** | MIT for `T-Display-S3`, `T-Display-S3-AMOLED`, `LilyGo-AMOLED-Series`; **none declared** for Long and Pro; **GPL‑3.0** for the 1.64 / 1.43‑1.75 repos | as left | wiki + firmware | schematic + **FCC exhibits** published |
-| **Depth here** | full | 4 full, 5 medium, 1 stub | full | full |
-
-### 3.2 What the table hides
-
-**"T-Display-S3" is a marketing prefix, not a platform.** The family record is
-blunt about it: code written for the base board will not run on any AMOLED board
-without changing the display driver, the bus type, the button pins *and* the power
-sequence. The only thing that ports unchanged is the Arduino board configuration.
-Three traps recur family-wide and catch nearly everyone:
-
-1. **The `USB CDC On Boot` trap.** With `ARDUINO_USB_CDC_ON_BOOT=1` — which
-   LilyGO's own instructions require — the Arduino core blocks at startup waiting
-   for a host to open the port. Run the same firmware from a battery and it hangs
-   before `setup()` finishes, looking like a dead board.
-2. **The Arduino-core version pin.** LilyGO tests at **2.0.14** and says versions
-   above it may not work; TFT_eSPI is named specifically. Corroborated
-   independently: the newest factory binary in the repo is built on ESP-IDF v4.4.6,
-   the base of arduino-esp32 2.0.14.
-3. **The display-bus split.** `TFT_eSPI` has no QSPI transport at all. Which
-   graphics library works depends on the *bus*, not the board name.
-
-**The Waveshare knob board has two full ESP32-class SoCs on it, not a helper
-chip.** The ESP32-S3 has no Bluetooth Classic radio — a silicon-level omission no
-library can fix — so Waveshare soldered an original ESP32 next to it purely to do
-A2DP/AVRCP/HFP/SPP. Consequence: Classic Bluetooth on that board means flashing a
-second, separate firmware image **over a differently-oriented USB-C connection**.
-
-**The XIAO ESP32S3 Sense has no display and is in this group only because it is the
-other "small ESP32-S3 you develop on" record.** Its two most expensive gotchas are
-that **the user LED and the SD chip select are the same pin (GPIO21)** and that
-**the camera and microphone occupy all four JTAG pins**.
-
-### 3.3 ⚠ Comparisons this group does **not** support
-
-- **The Waveshare knob board has no captured price**, so it cannot be placed on a
-  value axis against the $9.04 T-Display-S3 or the $13.99 XIAO.
-- **The knob board's display controller is genuinely unresolved** — marketed
-  ST77916, driven by an SH8601 compatibility driver. Do not assume either.
-- **Two LilyGO boards have no declared licence at all** (Long, Pro). "MIT
-  family" is wrong as a blanket statement.
-
-### 3.4 Who should buy which
-
-**Buy a [T-Display-S3](../../devices/lilygo/t-display-s3/README.md) at $9.04** for
-almost any "ESP32-S3 with a screen" job. Nothing else in this repository puts an
-ESP32-S3 with 16 MB flash *and* 8 MB OPI PSRAM *and* a colour display at under
-ten dollars. Read the family record's three traps first; each of them costs an
-evening otherwise.
-
-**Buy a [XIAO ESP32S3 Sense](../../devices/seeed-studio/xiao-esp32s3-sense/README.md)
-at $13.99** when the job is a networked camera you need to hide inside something.
-It is 21 × 17.8 mm and is the cheapest credible route to one. Do not buy the OV5640
-upgrade reflexively — at $11.99 it is 86 % of the board.
-
-**Buy the [Waveshare knob board](../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md)**
-if you specifically need Bluetooth Classic audio *and* a rotary UI in a CNC metal
-enclosure, and you accept a two-image flashing procedure and an undocumented
-inter-MCU protocol. Otherwise its dual-MCU architecture is a cost, not a feature.
-
----
-
-## Group 4 — LoRa, sub-GHz and mesh add-ons
-
-The question: *I want to add a radio to something I already have.*
-
-### 4.1 The table
-
-All prices from `shop.m5stack.com`, retrieved **2026-09-04**.
-
-| | [Cap LoRa-1262](../../devices/m5stack/cap-lora-1262/README.md) | [Cap LoRa868](../../devices/m5stack/cap-lora868/README.md) | [Cap CC1101 & NFC](../../devices/m5stack/cap-cc1101/README.md) | [Unit C6L](../../devices/m5stack/unit-c6l/README.md) | [Stamp C6LoRa](../../devices/m5stack/stamp-c6lora/README.md) | [LoRa Unit E220](../../devices/m5stack/unit-lora-e220/README.md) | [LoRaWAN Unit](../../devices/m5stack/unit-lorawan-stm32wle5/README.md) |
-|---|---|---|---|---|---|---|---|
-| **SKU** | U214 | U201 **`[EOL]`** | **U219** | U202 | S012 | U170 / U170‑433 | U184‑\* |
-| **Published** | 2025‑12‑30 | 2025‑09‑05 | **2026‑08‑28** | 2025‑10‑10 | 2026‑03‑13 | 2023‑10‑20 / 2024‑07‑12 | 2024‑12‑20 |
-| **Radio** | **SX1262** + ATGM336H GNSS | SX1262 + ATGM336H | **CC1101** (4 bands) + **ST25R3916 NFC** | SX1262 | SX1262 | **LLCC68** behind an AT modem | **STM32WLE5** (RAK3172) |
-| **Host interface** | **SPI** | SPI | **SPI**, both chips | **none — it is its own node** | SPI (module) | **UART, AT commands** | **UART, AT commands** |
-| **Attaches to** | Cardputer‑Adv, CardputerZero | same | same | **any Grove host** | solder‑down SMD | **any Grove host** | any Grove host |
-| **Bands** | 868–923 MHz, **one wideband SKU** | 868–923 MHz | **315 / 433 / 868 / 915**, switched | 868–923 MHz | 850–960 MHz | 920.6–928 (JP) / 410–493 | **region per SKU** |
-| **TX power** | +22 dBm | +20 dBm | **+10 dBm** | +22 dBm | +22 dBm | 13 dBm / 22 dBm | 22 dBm |
-| **Certification published** | **none** | **none** | **none** | none | none | **Telec `001-P01730`** (U170 only) | **RAK3172 module cert linked** |
-| **Meshtastic** | ✅ upstream variant | ✅ (same variant, degrades gracefully) | ❌ — CC1101 cannot do LoRa | ✅ **own upstream variant**, `M5STACK_C6L = 111` | ❌ no variant | ❌ and cannot have one | ❌ different protocol universe |
-| **Price** | **$14.50** | $14.50 | **$18.95** | **$22.90** | $12.95 | $33.00 / $12.95 | $21.50 / $18.95 (CN470) |
-| **Depth here** | full, **schematic held** | medium, schematic **not fetched** | full, **schematic held** | light | light | light | light |
-
-### 4.2 What the table hides
-
-**The most useful power data in this whole family is on the discontinued
-product.** The `[EOL]` Cap LoRa868's page breaks current into four named states —
-GPS on/LoRa standby 29.24 mA, GPS sleep/LoRa standby **3.16 mA**, GPS sleep/LoRa TX
-max 129.72 mA, GPS on/LoRa TX max 155.03 mA. Its successor replaces all four with a
-single unconditioned "163.4 mA". Read across: **the GNSS dominates idle draw and
-sleeping it is worth almost an order of magnitude.** Those numbers are for a
-+20 dBm board with no shield can and **must not be transplanted** into a U214 table
-— but the *shape* of the tradeoff carries.
-
-**CC1101 cannot do LoRa, and the frequencies overlapping is why people keep
-asking.** LoRa is chirp spread spectrum, Semtech owns the patents, TI does not make
-LoRa silicon. The Cap CC1101 is a Flipper-Zero-class sub-GHz capture/replay radio
-plus an NFC front end. There is **one Cap slot**, so the two Caps are mutually
-exclusive — a limitation owners complain about explicitly.
-
-**A house pattern runs through three M5Stack LoRa products: put the SX1262's RF
-switch behind an I²C I/O expander rather than spending a host GPIO on it.** Cap
-LoRa-1262 uses a PI4IOE5V6408; Stamp C6LoRa uses one and puts the *LNA enable*
-there too; the PaperMono uses M5Stack's own M5IOE1. The recurring consequence is
-**no I²C, no radio** — an I²C fault takes the RF path down even though SPI is fine.
-Anyone porting M5Stack LoRa hardware should look for the expander before concluding
-a radio is dead.
-
-**The Cap CC1101's band switching is the single most portable idea in this
-group.** One antenna port, four bands, two SP3T switches — and only *one* of the
-two control lines is a host GPIO. The other is the **CC1101's own GDO2 pin**, set
-over SPI. It costs one host pin instead of two; the price is that you cannot set
-the band before the transceiver is talking.
-
-**"Which LoRa for a Cardputer" has a different answer depending on which
-Cardputer.** The original K132/K132-V11 has **no expansion bus** — only a Grove
-port — so no Cap can attach at any price. Its answers are a Grove/UART modem
-(E220, LoRaWAN Unit) or the **Unit C6L, which is its own complete Meshtastic node**
-with its own MCU, screen, flash and antenna, cabled to the Cardputer as a
-companion.
-
-**Only two products in this family have any regulatory paperwork at all.** The
-E220 JP unit carries a Telec number printed in its specification table, and the
-LoRaWAN Unit splits by region per SKU and points at RAK3172 module certification.
-Every Cap — U201, U214, U219 — is a single wideband SKU spanning EU 868, US 915 and
-JP 920 allocations with **no published certification identifier of any kind**.
-
-### 4.3 ⚠ Comparisons this group does **not** support
-
-- **No RF measurement of any kind exists for any product here.** No range, no
-  throughput, no sensitivity, no current, from any party. The vendor's
-  "435 m / 441 m" for the CC1101 names a modulation and an air rate but no antenna,
-  height, terrain or link-margin criterion.
-- **The Unit C6L's own vendor table says receive standby draws *more* than
-  continuous transmit** (85.18 mA vs 80.02 mA) with no stated conditions. That is
-  not impossible — SX1262 receive in LDO mode is expensive and the TX figure may be
-  duty-cycled — but do not build a power budget on it.
-- **Whether the Cap LoRa868 has an I/O expander is unresolved.** Meshtastic's
-  `variant.cpp` says it does; M5Stack's own comparison table says "RF Switch
-  Control: None". The U201 schematic is published and would settle it; it was not
-  fetched.
-- **U201 and U214 current figures must not be merged.** Different TX power,
-  different shielding.
-
-### 4.4 Who should buy which
-
-**Cardputer-Adv or CardputerZero, want LoRa/Meshtastic:** the
-[Cap LoRa-1262 at $14.50](../../devices/m5stack/cap-lora-1262/README.md). It
-supersedes the U201 and is what ships in the Mesh Kit.
-
-**Cardputer-Adv, want sub-GHz capture/replay and NFC:** the
-[Cap CC1101 at $18.95](../../devices/m5stack/cap-cc1101/README.md) — and accept
-that you cannot have LoRa at the same time. It is also, for anyone reading this
-repository for the e-ink firmware work, **the cleanest published example of
-"NFC + sub-GHz on one SPI bus with a shared antenna"**; see
-[the LoRa/NFC/sidelight guide](../hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md).
-
-**Original Cardputer (K132/V11), want Meshtastic:** the
-[Unit C6L at $22.90](../../devices/m5stack/unit-c6l/README.md). It is a complete
-node, it has its own upstream Meshtastic variant, and the Grove cable is a link to
-a companion, not a peripheral bus. ⚠ The exact Cardputer↔C6L transport was **not
-verified** — check before promising it works.
-
-**You need a point-to-point serial link and do not care about mesh:** the
-[E220 unit](../../devices/m5stack/unit-lora-e220/README.md) at $12.95 for 433 MHz.
-A DIP switch gets you a working link with no configuration code. It can never run
-Meshtastic — the host cannot reach the radio's registers.
-
-**You need something deployable rather than benchtop:** the
-[LoRaWAN Unit](../../devices/m5stack/unit-lorawan-stm32wle5/README.md). Region is
-baked into the SKU and there is certification to point at, at the cost of giving up
-direct radio control.
-
-**Do not buy a [Stamp C6LoRa](../../devices/m5stack/stamp-c6lora/README.md)
-expecting a Cardputer accessory.** It is a solder-down SMD module for your own
-carrier PCB.
-
----
-
-## Group 5 — Everything else in `devices/`
-
-Included so this page genuinely covers every record. These are documented
-elsewhere and are not re-tabulated.
-
-| Record | One line |
-|---|---|
-| [Cardputer v1.0](../../devices/m5stack/cardputer-v1.0/README.md) | The original. Same mainboard schematic file as the v1.1, **byte-identical** — every published difference is in the Stamp module |
-| [Cardputer Mesh Kit](../../devices/m5stack/cardputer-mesh-kit/README.md) | ADV + Cap LoRa-1262 + antenna, $48, **the only route to Meshtastic device registration** |
-| [DinMeter](../../devices/m5stack/dinmeter/README.md) · [v1.1](../../devices/m5stack/dinmeter-v1.1/README.md) | 1/32-DIN panel-cutout instrument head, orange knob, 6–36 V input, $24.50. v1.1 is a **core-module swap only** — M5Stack re-served the v1.0 schematic and STL under v1.1 filenames, byte-identical |
-| [Xteink S4](../../devices/xteink/s4/README.md) | Android 11 reader, ~¥339. **Stub — no SoC, no chip, no board fact is established.** Outside the ESP32 firmware ecosystem entirely |
-| [Xteink Nano / Tong Card](../../devices/xteink/nano/README.md) | Battery-less **NFC-powered** four-colour e-paper card. Not a reader. Routinely confused with the X3's embedded NFC tag |
-| [Inkplate 5](../../devices/soldered-electronics/inkplate-5/README.md) · [Gen 2](../../devices/soldered-electronics/inkplate-5-gen2/README.md) | Soldered Electronics e-paper dev boards; **the Gen 2 is the board ZeroWriter Ink respun** |
-| [Waveshare ESP32-S3-ePaper-1.54](../../devices/waveshare/esp32-s3-epaper-1.54/README.md) · [ESP32-C6-ePaper-1.54](../../devices/waveshare/esp32-c6-epaper-1.54/README.md) · [PhotoPainter](../../devices/waveshare/esp32-s3-photopainter/README.md) · [e-Paper ESP32 Driver Board](../../devices/waveshare/e-paper-esp32-driver-board/README.md) | The rest of Waveshare's ESP32 e-paper line |
-| [Waveshare ESP32-P4 3.4C](../../devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/README.md) · [4C](../../devices/waveshare/esp32-p4-wifi6-touch-lcd-4c/README.md) · [shared](../../devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md) | ESP32-P4 + C6 radio touch panels; see the [comparison matrix](device-comparison-matrix.md) |
-| [Espressif P4X-Function-EV](../../devices/espressif/esp32-p4x-function-ev-board/README.md) · [P4X-C5](../../devices/espressif/esp32-p4x-c5-function-ev-board/README.md) · [P4X-EYE](../../devices/espressif/esp32-p4x-eye/README.md) · [P4-Function-EV `EOL`](../../devices/espressif/esp32-p4-function-ev-board/README.md) · [P4-EYE `EOL`](../../devices/espressif/esp32-p4-eye/README.md) | Espressif's own P4 evaluation boards |
-| [LilyGO T-Display TTGO](../../devices/lilygo/t-display-ttgo/README.md) · [T-QT](../../devices/lilygo/t-qt/README.md) · [T-Dongle-S3](../../devices/lilygo/t-dongle-s3/README.md) | Lineage stubs — predecessors and cousins of the T-Display-S3 line, **not variants of it** |
-
----
-
-## Cross-cutting observations
-
-Five things fall out of looking at all of these together that are invisible from
-any single record.
-
-**1. Certification is absent almost everywhere, and it is not evenly absent.** No
-Xteink device, no Cardputer, no PaperMono, no Cap and no LilyGO K230 has a
-published FCC/CE/TELEC identifier. The two exceptions in the whole repository are
-the E220-JP unit (a printed Telec number) and the LoRaWAN Unit (a linked RAK3172
-module certification). If you are building a product rather than a project, that
-narrows the shortlist to almost nothing — and note that
-[module-level certification does not transfer automatically](../lora/README.md#10-choosing-a-radio)
-into your product with your antenna.
-
-**2. The most open device is also the most expensive, and the relationship is not
-a coincidence.** Tanmatsu publishes complete KiCad under CERN-OHL-P at ~€120.
-Xteink publishes nothing at $69–99 and its product copy is
-[demonstrably false](../../devices/xteink/x3/gaps-and-conflicts.md). M5Stack and
-Waveshare publish schematics but no certification. The middle of the market
-publishes a schematic and hopes you do not ask about the rest.
-
-**3. Runtime documentation is systematically better than product documentation
-for reverse-engineered hardware, and systematically worse for vendor hardware.**
-The Xteink X4 Classic's *pinout* is documented to HIGH confidence pin by pin from a
-firmware dump, while its price, dimensions, mass, battery and photograph are all
-unknown — an inversion the record calls out explicitly. The DinMeter is the
-opposite: full vendor documentation, and a v1.1 whose only published evidence of
-change is a filename.
-
-**4. Two vendors reuse product names across incompatible hardware, and it costs
-real time.** "T-Display-S3" spans eleven boards with eight display controllers and
-four different PMICs; LilyGO's stock code `K230` is **a transparent-shell T-Embed
-CC1101 with no Kendryte silicon in it at all**, and is the top hit when you search
-their store for "K230". "Cardputer" spans an ESP32-S3 MCU and a Raspberry Pi CM0
-Linux machine with a physically identical, electrically different expansion header.
-
-**5. Shared-bus architecture is the recurring hazard class.** The Xteink C3
-devices share one SPI bus between the panel and the SD card. The Cardputer ADV
-shares one SPI bus between the microSD and the Cap header. The PaperMono puts
-seven devices on one I²C bus, one of which (the IP2315 charger) has a documented
-bus-wedge failure mode. M5Stack's three LoRa products put the RF switch behind
-I²C. In every case the failure looks like a dead peripheral and is actually
-contention or a missing enable.
-
----
-
-## Evidence boundary
-
-- **Nothing on this page was retrieved, measured, built or flashed.** It is a
-  synthesis of records dated between 2026-08-21 and 2026-09-07.
-- Each group's price row carries its own observation date. **Prices move**; the
-  Xteink X4 went from listed to delisted inside this repository's own snapshot
-  window, and both PaperMono SKUs were out of stock on the day they were priced.
-- Where two records disagree with each other, the disagreement is stated rather
-  than resolved. The comparison matrix's
-  [§10](device-comparison-matrix.md#10-conflicts-between-records) holds the
-  equivalent list for the fourteen devices it covers.
-- **Record depth is not product quality.** The Xteink family is documented in
-  depth because its firmware was reverse-engineered by a large community, not
-  because the vendor helped.
-
-## Related
-
-- [Device comparison matrix](device-comparison-matrix.md) — specification-axis view of fourteen devices
-- [Vendor and marketplace comparison](vendor-comparison.md) — who to buy from and whether the files will still be hosted next year
-- [Clones, siblings and variants](clones-and-variants.md)
-- [Adding LoRa, NFC and an RGB sidelight to e-ink firmware](../hardware/adding-lora-nfc-and-sidelight-to-eink-firmware.md)
-- [SoC choice for battery e-ink devices](../hardware/soc-choice-for-battery-eink-devices.md)
-- [Xteink firmware ecosystem](../../devices/xteink/firmware-ecosystem.md)
-- [`guides/lora`](../lora/README.md) · [`guides/nfc`](../nfc/README.md) · [`guides/hardware/e-paper-displays.md`](../hardware/e-paper-displays.md)
diff --git a/guides/nfc/README.md b/guides/nfc/README.md
deleted file mode 100644
index 7049adb..0000000
--- a/guides/nfc/README.md
+++ /dev/null
@@ -1,758 +0,0 @@
-# NFC — a device-independent guide
-
-> **How does 13.56 MHz NFC actually work, and how do I bring a reader up on an MCU?**
-> A cross-cutting guide compiled from the NFC knowledge in this library — principally the
-> [ST ST25R3916 record](../../components/stmicroelectronics/st25r3916/README.md) (555 lines,
-> built on `DS12484 Rev 8` held locally) and the
-> [M5Stack PaperMono NFC feature guide](../../devices/m5stack/papermono/features/nfc.md).
-> Compiled **2026-09-02**. **No hardware. No tag has been read by anyone whose report could be
-> located.**
-
-## 0. What this guide is, and what it is not
-
-This is the **common** layer the research method asks for in step 13: reusable concepts, APIs,
-alternatives, validation and generic pitfalls, **without unqualified device pin assignments**. Where
-a concrete example is needed, the device is named and its record linked; no pin number here stands
-alone.
-
-It does **not** duplicate the deep records. The
-[ST25R3916 record](../../components/stmicroelectronics/st25r3916/README.md) is the authority on that
-chip's registers, mode byte, power states and the PaperMono's front end. **Where this guide and a
-deep record disagree, the deep record wins.**
-
-Three things this guide does that no single record can:
-
-1. Explains the **standards landscape** once, so component records need not re-derive which ISO
-   number corresponds to which real-world card.
-2. Treats **antenna and matching** as a subject, because it is the part that most often turns a
-   correct driver into a reader that finds nothing.
-3. States, in one place, **what is and is not establishable** about NFC read range from documents
-   alone — which is the honest answer to the open question in the PaperMono record.
-
-### Evidence labels
-
-| Label | Meaning | Evidence status |
-|---|---|---|
-| **[DS]** | Datasheet claim, inherited from a component record that cites a section or table of a locally-held document | `not-tested` |
-| **[SRC]** | Read out of source at a cited `file:line`, either from a repo record or from a live read on 2026-09-02 | `executed-success` for the read; `not-tested` on hardware |
-| **[DOC]** | Vendor documentation or repository metadata, retrieved 2026-09-02 | `not-tested` |
-| **[SCH]** | Inherited label: read out of a schematic by the linked component record | `executed-success` for that record's extraction; `not-tested` electrically |
-| **[STD]** | A claim about a formal standard (ISO/IEC, JIS, NFC Forum, ETSI, FCC). ⚠ **This repository holds none of these documents.** Cited by number so it can be checked; the text was not read in this pass | `not-tested`, **unverified against the primary document** |
-| **[REC]** | Recalled general engineering knowledge with no document behind it in this repository | **`not-tested` and unsourced** — treat as a lead, not a fact |
-| **[INF]** | Derived here, with the reasoning shown | `inferred` |
-
-⚠ **[STD] and [REC] claims are the weak part of this guide and are marked on every occurrence.**
-§11 lists what could not be sourced.
-
----
-
-## 1. The standards landscape
-
-### 1.1 The four physical layers
-
-"NFC" is a marketing umbrella over four mutually unintelligible radio protocols that happen to share
-a 13.56 MHz carrier. A reader supports each one separately, and a tag answers exactly one of them.
-
-| NFC Forum name | Standard | Origin | PCD→PICC | PICC→PCD | Typical bit rate |
-|---|---|---|---|---|---|
-| **NFC-A** | **ISO/IEC 14443** Type A | Philips/NXP MIFARE lineage | 100 % ASK, modified Miller **[STD]** | load modulation, **fc/16 = 847.5 kHz** subcarrier, Manchester **[STD]** | 106 kbit/s, up to 848 **[STD]** |
-| **NFC-B** | **ISO/IEC 14443** Type B | Innovatron/ASK lineage | ~10 % ASK, NRZ **[STD]** | BPSK on the same fc/16 subcarrier **[STD]** | 106 kbit/s, up to 848 **[STD]** |
-| **NFC-F** | **JIS X 6319-4** (FeliCa), also reachable via **ISO/IEC 18092** | Sony | ~10 % ASK, Manchester **[STD]** | load modulation, **no subcarrier**, Manchester **[STD]** | **212 / 424 kbit/s** **[STD]** |
-| **NFC-V** | **ISO/IEC 15693** ("vicinity") | Philips/TI lineage | 10 % or 100 % ASK, 1-of-4 or 1-of-256 pulse position **[STD]** | fc/32 = 423.75 kHz single or dual subcarrier **[STD]** | ~26.5 kbit/s high rate **[STD]** |
-
-The carrier itself is the one thing they genuinely share: **13.56 MHz**, which is why an ST25R3916
-runs from a **27.12 MHz** crystal — twice the carrier **[DS]**
-([ST25R3916 §1](../../components/stmicroelectronics/st25r3916/README.md)).
-
-**What this means in practice.** Support for one of these tells you nothing about the others. A
-chip's marketing sheet listing "ISO14443A/B, FeliCa, ISO15693" is four separate framing engines,
-four separate anticollision procedures and — in a library — usually four separate code paths. The
-[`M5Unit-NFC` tree carries exactly that shape](../../components/stmicroelectronics/st25r3916/README.md):
-`unit_ST25R3916_nfc{a,b,f,v}.cpp` and `src/nfc/layer/{a,b,f,v}/` **[SRC]**. ST's RFAL does the same
-with `rfal_nfca.cpp` / `rfal_nfcb.cpp` / `rfal_nfcf.cpp` / `rfal_nfcv.cpp` **[SRC]**
-(`stm32duino/NFC-RFAL` @ `main`, read 2026-09-02).
-
-The ST25R3916 supports all four in silicon, plus **NFC tag types 1–5 read** — stated in the
-datasheet's own feature table **[DS]**
-([§1.1](../../components/stmicroelectronics/st25r3916/README.md#11-st25r3916-vs-st25r3917--the-fitted-part-is-the-full-one)).
-Its cut-down sibling the ST25R3917 keeps all four *reader* technologies and loses card emulation,
-peer-to-peer target mode, automatic antenna tuning and the capacitive sensor **[DS]**. **The identity
-register cannot distinguish them** — both report `ic_type = 0x05` **[DS]**, a trap documented as
-[C2](../../components/stmicroelectronics/st25r3916/README.md#9-caveats-and-gaps).
-
-### 1.2 NFC Forum tag types 1–5 and what they are in the shop
-
-The NFC Forum's tag types are an **application-layer** classification layered on the physical
-protocols above. They exist so that an NDEF reader can work without knowing the silicon.
-
-| Tag type | Runs on | Real products **[REC]** | Memory, roughly **[REC]** |
-|---|---|---|---|
-| **Type 1** | NFC-A (ISO 14443-3A, no part 4) | Broadcom/Innovision **Topaz** / Jewel | 96 B – 2 kB |
-| **Type 2** | NFC-A (ISO 14443-3A, no part 4) | **NTAG213/215/216**, **MIFARE Ultralight**, MIFARE Ultralight C/EV1 | 48 B – 888 B |
-| **Type 3** | NFC-F (FeliCa) | **Sony FeliCa Lite / Lite-S**, FeliCa Standard | 1 – 9 kB |
-| **Type 4** | NFC-A **or** NFC-B with ISO 14443-4 (ISO-DEP) and APDUs | **MIFARE DESFire EV1/2/3**, JCOP and other JavaCards, phone HCE | 2 – 8 kB+ |
-| **Type 5** | NFC-V (ISO 15693) | **NXP ICODE SLIX/SLIX2**, **ST ST25TV**, TI Tag-it | 112 B – 2 kB |
-
-The **[REC]** label on the product column is deliberate: this repository holds no NXP, Sony or
-Broadcom tag datasheet. The mapping is engineering-common-knowledge, it is very unlikely to be
-wrong, and it is still not sourced here. Verify against the tag vendor's datasheet before you design
-around a specific memory layout.
-
-**Structural consequence.** Types 1, 2 and 5 are *memory* tags — you address blocks or pages
-directly. Type 4 is a *smartcard* — you open a logical channel with ISO-DEP and exchange APDUs, and
-the tag decides what to answer. That is why a library that reads NTAG fine may not touch DESFire at
-all: the latter needs an entire extra protocol layer. RFAL splits them exactly on that line:
-`rfal_t1t.cpp`, `rfal_t2t.cpp`, `rfal_t4t.cpp` for the tag operations, and a separate
-`rfal_isoDep.cpp` for the ISO 14443-4 transport underneath Type 4 **[SRC]**.
-
-### 1.3 ⚠ MIFARE Classic is not an NFC Forum tag type
-
-This catches people constantly. **MIFARE Classic** is ISO 14443-3A for anticollision and selection,
-and then a **proprietary NXP protocol secured by Crypto1** instead of ISO 14443-4. It is not any of
-tag types 1–5, NDEF on it is a vendor mapping rather than a Forum specification, and a reader stack
-that implements the Forum types will select a MIFARE Classic card and then be unable to read a byte
-of it. **[REC]**
-
-Practically, a stack either has Crypto1 or it does not. `M5Unit-NFC` does — its tree carries
-`src/nfc/a/mifare` and `src/nfc/crypto/`, and the record notes "MIFARE Classic Crypto1, AES, DESFire
-file-system helpers, ISO-DEP, NDEF and APDU are all in-tree" **[SRC]**
-([ST25R3916 §7.1](../../components/stmicroelectronics/st25r3916/README.md#71-m5unit-nfc-is-a-from-scratch-driver-not-an-rfal-wrapper)).
-ST's RFAL, as packaged for Arduino, does **not**: there is no `mifare` or `crypto` file anywhere in
-the 85-file `stm32duino/NFC-RFAL` tree **[SRC]**, a **verified negative** from a full tree
-enumeration on 2026-09-02.
-
-That is a real capability difference between the two stacks and it is invisible from either
-project's description.
-
-### 1.4 Where NDEF sits
-
-**NDEF** (NFC Data Exchange Format) is a container — a message of typed records — defined by the NFC
-Forum above all five tag types **[STD]**. Each tag type has its own *Type n Tag Operation*
-specification saying how an NDEF message is stored in that tag's memory model **[STD]**. So "does it
-support NDEF" is really five questions.
-
-RFAL's NDEF layer makes the structure legible without reading a single specification **[SRC]**:
-
-```
-ndef_message.cpp / ndef_record.cpp     the container format itself
-ndef_poller.cpp / ndef_poller_rf.cpp   the read/write state machine over RFAL
-ndef_t2t.cpp  ndef_t3t.cpp             per-tag-type memory mapping —
-ndef_t4t.cpp  ndef_t5t.cpp             note there is no ndef_t1t.cpp
-ndef_type_text.cpp  ndef_type_uri.cpp  the well-known record types
-ndef_type_wifi.cpp  ndef_type_bluetooth.cpp   ← handover records
-ndef_type_vcard.cpp ndef_type_aar.cpp  ← Android Application Record
-```
-
-Two readings worth taking from that listing. **Type 1 tag NDEF mapping is absent** from this package
-even though `rfal_t1t.cpp` exists at the protocol layer — so RFAL can talk to a Topaz but this NDEF
-layer will not parse one **[SRC]**, `inferred` from the file list, not from a stated limitation.
-And **`ndef_type_wifi` and `ndef_type_bluetooth` are the connection-handover records** — the
-mechanism behind "tap to pair", which is the single most common real use of NFC beyond identity.
-
----
-
-## 2. Reader/writer, card emulation, peer-to-peer
-
-| Mode | What the chip is | Realistic on an MCU? |
-|---|---|---|
-| **Reader/writer** (initiator, poller) | Generates the field; powers and talks to a passive tag | ✅ **Yes.** This is the case every library, every example and every vendor demo covers |
-| **Card emulation** (passive target) | Sits in someone else's field and load-modulates a reply | ⚠ **Silicon says yes; evidence says nobody does it.** See below |
-| **Peer-to-peer** (NFC-DEP / ISO 18092 active mode) | Two powered devices alternate field generation | ⚠ Technically supported; **strategically dead**. See below |
-
-**Card emulation** is a full ST25R3916 feature — the datasheet's own comparison table lists it as one
-of the four things the 3917 loses **[DS]**. But on the one device in this library that fits the part,
-the [PaperMono feature guide records](../../devices/m5stack/papermono/features/nfc.md) that
-`cfg.emulation` exists and is **set `false` everywhere in vendor code and never demonstrated**
-**[SRC]**. The gap between "the silicon can" and "someone has" is the whole of §8 below.
-
-Emulation also has a hardware dimension that is easy to miss: the chip provides an **`EXT_LM`**
-external load-modulation gate driver pin and a **PT_memory** (passive target) region reached by its
-own mode-byte operations — `0xA0` / `0xA8` / `0xAC` to load the A-config, F-config and TSN, `0xBF` to
-read back **[DS]**
-([ST25R3916 §3.3](../../components/stmicroelectronics/st25r3916/README.md#33-the-mode-byte-why-the-firmware-reads-register-0x7f)).
-If a board leaves `EXT_LM` unpopulated, strong emulation may not be available even though the
-register path is.
-
-**Peer-to-peer** deserves a blunt note. The chip supports ISO 18092 active initiator *and* target
-**[DS]**, and RFAL ships `rfal_nfcDep.cpp` **[SRC]**. But Android removed Android Beam in Android 10
-and the SNEP/LLCP peer-to-peer stack with it **[REC]** — so an MCU implementing P2P has essentially
-nothing to talk to. **Card emulation (HCE on the phone side, reader on yours) is the modern
-phone-to-device path**, not P2P. Treat any tutorial that opens with peer-to-peer as dated.
-
----
-
-## 3. Choosing a front end
-
-⚠ **This repository holds a datasheet for exactly one of these parts.** Everything in the
-ST25R3916 row is **[DS]**-grade. Every other row is **[REC]** — recalled, unverified, and included
-because a decision table with one row is useless. Library-maintenance columns *are* sourced: they
-were checked live against the GitHub API on 2026-09-02 **[DOC]**.
-
-| Part | Technologies | Modes | Host | Library reality **[DOC]** | Reach for it when |
-|---|---|---|---|---|---|
-| **ST ST25R3916** | A, B, F, V; tag types 1–5 **[DS]** | reader + **card emulation** + P2P + AAT + cap sense **[DS]** | **SPI or I²C, strapped by `I2C_EN`** **[DS]** | ST **RFAL** — `stm32duino/NFC-RFAL` 2.0.2 + `stm32duino/ST25R3916` 2.1.0, pushed **2026-08-31**, actively maintained | You want every technology, EMVCo-grade analog, or emulation. The best-documented option in this library |
-| ST ST25R3917 | A, B, F, V **[DS]** | reader only — **no** emulation, AAT or cap sense **[DS]** | same **[DS]** | same RFAL | Cost-down reader-only. ⚠ shares `ic_type` with the 3916 — you cannot probe which you have **[DS]** |
-| ST ST25R3911B | A, B, F, V **[REC]** | reader + emulation **[REC]** | SPI **[REC]** | `stm32duino/ST25R3911B`, pushed 2025-04-02 | The previous generation. Choose the 3916 for new work — same stack, newer silicon |
-| ST ST25R200 / R100 / R500 / R300 | reduced sets **[REC]** | reader **[REC]** | SPI **[REC]** | `stm32duino/ST25R200` (2025-04), `ST25R500` (2025-12) | ST's newer low-cost line. **Same RFAL**, so the porting cost from a 3916 design is small |
-| **NXP PN532** | A, B, F; **no** ISO 15693 **[REC]** | reader + emulation + P2P **[REC]** | I²C, SPI, **HSU/UART** **[REC]** | `adafruit/Adafruit-PN532` (2025-02), `elechouse/PN532` (2026-07); **`libnfc` supports it** | Hobby ubiquity, three host interfaces, huge example base. ⚠ **no NFC-V** — it will not read ICODE |
-| NXP PN5180 | A, B, F, **V** **[REC]** | reader + emulation **[REC]** | SPI **[REC]** | ⚠ `ATrappmann/PN5180-Library` is **archived** (last push 2022-06) | Full technology coverage in the NXP ecosystem — but the popular Arduino library is abandoned |
-| NXP MFRC522 ("RC522") | **A only** **[REC]** | reader **[REC]** | SPI, I²C, UART **[REC]** | ⚠ `miguelbalboa/rfid` README: *"The development by owner miguelbalboa has ended"*, maintenance badge **`no/2019`**; successor `OSSLibraries/Arduino_MFRC522v2` (LGPL-2.1, 2026-04) | The €2 blue board. Fine for MIFARE Classic/NTAG toys. **Not** for FeliCa, ISO 15693 or anything you must certify |
-
-**How to read this table.** The dominant selection axis is not price — it is **which technologies you
-must support**, and the second is **whether a maintained stack exists for your MCU**. An RC522 that
-cannot see an ISO 15693 tag is not cheap, it is wrong. Conversely the ST25R3916 costs you a
-harder bring-up (§5) and an antenna you must actually design (§4) in exchange for the full technology
-set and ST's own analog configuration tables.
-
-**Uncertainty.** Every [REC] cell should be checked against the part's datasheet before it decides
-anything. The technology-coverage claims are the ones most likely to be subtly wrong — vendors
-sometimes list a technology that is supported only at one bit rate, or only in one mode.
-
----
-
-## 4. Antenna and matching — the part people get wrong
-
-A correct driver on a badly matched antenna reads nothing, reports nothing, and looks exactly like a
-software bug. This section is why.
-
-### 4.1 An NFC reader is a tuned transformer, not a transmitter
-
-At 13.56 MHz a wavelength is ~22 m and every practical antenna is a small loop operating in the
-**magnetic near field**. The reader coil and the tag coil form a loosely coupled air transformer.
-Nothing radiates usefully; the tag is *powered* by the field and replies by **load modulation** —
-changing its own impedance so the reader sees its own field perturbed **[REC]**.
-
-Three consequences follow, and they explain most NFC field behaviour:
-
-1. **The field falls off very fast.** On the axis of a circular loop the classic result is
-   `H = N·I·a² / (2·(a² + r²)^{3/2})` — asymptotically **1/r³** **[REC]**. Doubling the distance
-   costs 18 dB, not 6.
-2. **Range is capped by antenna size, not by power.** That same expression is maximised, for a given
-   distance, by making `a` comparable to `r`. The practical rule of thumb is that usable read
-   distance is on the order of the **antenna radius** **[REC]**. You cannot brute-force a small coil
-   with more current.
-3. **Both sides must be tuned to the same frequency**, and a detuned tag pulls the reader too.
-
-### 4.2 The matching chain
-
-Between the driver pins and the coil sits a chain that every 13.56 MHz reader design has in some
-form **[REC]**:
-
-```
-driver output ─► EMC low-pass filter ─► matching network ─► damping ─► antenna coil
-   (RFO1/RFO2)      (series L, shunt C)    (series/shunt C)    (series R)   (loop)
-
-receiver input ◄── attenuation / DC-bias network ◄── tap off the antenna
-   (RFI1/RFI2)
-```
-
-- **The EMC filter** is a low-pass placed *above* the carrier. It exists to keep the driver's square
-  wave from radiating its harmonics — the driver is a switching push-pull stage, not a linear
-  amplifier.
-- **The matching network** transforms the coil's impedance to the driver's target load, which is what
-  actually determines how much current flows in the coil.
-- **The damping resistor** deliberately lowers Q (§4.3).
-- **The receiver path** is separate and is *not* a power path — it taps the antenna and attenuates it
-  down to something the receiver front end can handle. On the ST25R3916 that front end is specified
-  at **V<sub>RFI</sub> typ. 0.5 mV<sub>rms</sub>** with 12–16 kΩ input resistance **[DS]** — and the
-  datasheet marks it "specified by design, not tested in production"
-  ([§5.4](../../components/stmicroelectronics/st25r3916/README.md#54-driver-architecture-the-network-implies)).
-
-The ST25R3916's transmitter is **two identical push-pull drivers** (`RFO1`, `RFO2`) normally driving
-the tank **differentially**, with `IO configuration register 1` bit 7 (`single`) switching to
-single-ended and bit 6 (`rfo2`) then selecting which driver and which receiver input are used
-**[DS]**. Differential doubles the voltage swing across the coil for the same supply, and it is the
-default for a reason.
-
-### 4.3 Q versus bandwidth — the actual trade
-
-The tank's quality factor `Q = ω₀L / R_total`, and its −3 dB bandwidth is `B = f₀ / Q`. High Q means
-a strong field and a narrow bandwidth; that is the whole tension.
-
-The bandwidth you need is set by the **subcarrier**, not by the data rate. NFC-A and NFC-B put the
-tag's reply on a subcarrier at **fc/16 = 847.5 kHz** **[STD]**, so the reply occupies sidebands at
-roughly ±0.85 MHz around 13.56 MHz. To pass both sidebands without severe attenuation you need
-`B ≳ 1.7 MHz`, i.e. `Q ≲ 8` **[INF]** — arithmetic on `B = f₀/Q` with `f₀ = 13.56 MHz`. Real reader
-designs do not go that low; they run higher Q, accept sideband attenuation, and rely on the
-receiver's gain. Published reader-antenna Q targets are typically in the tens **[REC]** — the exact
-number is vendor application-note territory and **this repository holds no NFC antenna application
-note**.
-
-Higher bit rates make it worse: 424 and 848 kbit/s widen the modulation, and FeliCa at 212/424 kbit/s
-uses **no subcarrier at all** **[STD]**, changing the spectral shape entirely. A design tuned by ear
-for 106 kbit/s type A can fail at 424 kbit/s FeliCa.
-
-**This is what damping resistors are for.** In the
-[PaperMono's front end the record identifies `R3`, `R5` = 2 Ω in the antenna branches](../../components/stmicroelectronics/st25r3916/README.md#53-the-parts-that-are-there)
-**[SCH]**. Two ohms in series with a coil of a few hundred nH at 13.56 MHz is a substantial, and
-deliberate, Q reduction.
-
-### 4.4 A worked component census — and one number that does not add up
-
-The [ST25R3916 record §5.3](../../components/stmicroelectronics/st25r3916/README.md#53-the-parts-that-are-there)
-carries a **complete component census of a real, shipping NFC front end**, recovered from the
-PaperMono schematic: two 270 nH inductors, 680 pF, 160 pF, 150 pF, 220 pF and 10 pF capacitor groups,
-2 Ω damping resistors, and an `NC` position in the AAT/`CSI` branch. **Read it there rather than
-here** — it is the best worked example in this library, and it is device-specific by nature.
-
-Two things about it belong in a general guide.
-
-**First, the record is explicit that the topology was not recovered.** Its §5.2 says the extraction
-"recovers text adjacency, not electrical connectivity", and the "Almost certainly" column heading is
-doing real work. That honesty matters for anyone tempted to copy the values.
-
-**Second, a sanity check on the inferred pairing does not come out right — and that is a useful
-lesson about reviewing someone else's matching network.** If `L1`/`L2` (270 nH) and `C6`/`C8`
-(680 pF) form the EMC filter in the conventional per-branch arrangement, the corner sits at
-
-```
-f = 1 / (2π·√(L·C)) = 1 / (2π·√(270 nH × 680 pF)) ≈ 11.7 MHz     [INF]
-```
-
-**below the 13.56 MHz carrier**, which is the wrong side for a filter whose job is to suppress
-harmonics while passing the carrier. Pair the same inductor with the 220 pF group instead and it
-lands at **≈ 20.6 MHz** **[INF]** — a thoroughly conventional place for an NFC EMC filter corner.
-
-That is not a claim that the record is wrong. The differential topology, the coil's own inductance
-and any series capacitance all move the answer, and none of them is known. It *is* a demonstration
-of the review technique: **compute the corner frequency implied by every plausible L–C pairing, and
-treat any result below the carrier as a signal that you have mis-read the topology.** Recorded as an
-open observation for whoever next reads that schematic sheet graphically.
-
-### 4.5 Layout dominates, and the numbers are small
-
-The same record captures the vendor's own antenna specification, printed on the schematic
-**[SCH]**: **4 turns, 25 × 25 mm, 0.25 mm line width, 0.3 mm spacing, 17 µm (0.5 oz) copper**. Two
-general points from it:
-
-- **That is a small reader antenna.** By §4.1's rule of thumb, an equivalent radius of ~14 mm bounds
-  usable range at **centimetres, not tens of centimetres** **[INF]**. This does **not** produce a
-  read-range figure, and the ST25R3916 record is right to refuse one — "no range figure follows from
-  geometry alone". What geometry establishes is the *order of magnitude*, and therefore what a
-  reasonable test expectation looks like.
-- **The specification is on the schematic, in the copper, at a stated thickness.** Turn count, track
-  width, spacing and copper weight all set the coil's inductance and its series resistance, so they
-  set both the tuning and the Q. **An NFC antenna is a component with a tolerance, drawn in the
-  stackup.** Change the stackup and you have detuned the radio.
-
-Everything nearby matters too: ground pours, metal enclosures, batteries and displays behind the coil
-all load it and shift its resonance **[REC]**. This is why a design that works on a bench coupon can
-fail in the case.
-
-### 4.6 Automatic antenna tuning, and why it may not be populated
-
-The ST25R3916 offers **AAT** — `AAT_A` and `AAT_B` pins driving variable capacitors, with the tuning
-procedure run at start-up **[DS]**. RFAL ships the driver for it: `st25r3916_aat.cpp` /
-`st25r3916_aat.h` **[SRC]**. AAT compensates for exactly the detuning §4.5 describes.
-
-It needs **external parts**, and a board can provision the branch without populating it. The
-PaperMono appears to be such a board — the record's
-[C3](../../components/stmicroelectronics/st25r3916/README.md#9-caveats-and-gaps) reads the `NC`
-capacitor in that branch as AAT and the capacitive sensor being laid out but unfitted, `inferred` and
-explicitly unconfirmed. **Generalise the check, not the conclusion:** if you are selecting a part
-for AAT, confirm the variable-capacitor network is actually on the BOM, because the silicon feature
-and the board feature are different things.
-
-### 4.7 Reviewing an NFC antenna design — a checklist
-
-1. **Is there an EMC filter, and is its corner above 13.56 MHz?** (§4.4.)
-2. **Is the drive differential or single-ended, and does the register configuration agree with the
-   populated branches?** On the ST25R3916 this is `IO configuration register 1` bits 7 and 6 **[DS]**
-   — a mismatch between a differential board and a single-ended register setting is silent.
-3. **Is there a damping resistor?** No damping usually means Q was never considered.
-4. **Is the receiver path separate from the driver path**, with its own attenuation and DC bias?
-5. **Does the coil's copper specification appear anywhere in the design files** — turns, width,
-   spacing, thickness? If not, it is not specified, it is whatever the fab did.
-6. **What is behind the coil?** Ground pour, battery, display, metal case.
-7. **Are the driver current and dissipation limits respected?** For the ST25R3916: **350 mA** max
-   driver current from the internal regulator, **500 mA** peak with the regulator bypassed, against a
-   **300 mW** total dissipation ceiling **[DS]**
-   ([§6](../../components/stmicroelectronics/st25r3916/README.md#6-electrical)). Those two numbers
-   are in tension by design and it is why ST mandates the overheat-protection frame (§5.7).
-8. **Does the stack's analog configuration match this antenna?** See §6.1 — RFAL ships a table of
-   per-technology analog register settings and it is antenna-dependent.
-
----
-
-## 5. Host interface, interrupts, FIFO, and the shape of a transaction
-
-Everything in this section is **[DS]** from the ST25R3916 record. The *patterns* generalise across
-NFC front ends; the specific values do not.
-
-### 5.1 SPI or I²C, and how the chip is told which
-
-The ST25R3916 selects its interface with a **strap pin**, `I2C_EN`: pulled to `GND` it is SPI, pulled
-to `VDD_D` it is I²C **[DS]**
-([§3.1](../../components/stmicroelectronics/st25r3916/README.md#31-the-interface-is-chosen-by-a-strap-and-this-board-straps-it-to-i²c)).
-I²C is available at 100 kHz, **400 kHz**, 1 MHz Fast-mode Plus and 3.4 MHz high-speed **[DS]**.
-
-Choosing between them is a system decision, not a driver one:
-
-| | SPI | I²C |
-|---|---|---|
-| Pins | 4 dedicated | 2, **shared** |
-| Throughput | higher; no address or ACK overhead | capped by the bus, and by everything else on it |
-| Bus contention | none | ⚠ **the real risk** |
-| FIFO streaming | clean | works, but every byte costs an ACK slot |
-
-⚠ **The trap is naming.** In I²C mode the ST25R3916's data line is the pin *called* `MISO` and its
-clock is the pin *called* `SCLK` — the datasheet names them `MISO (SDA)` and `SCLK (SCL)` **[DS]**.
-A schematic symbol showing SPI pin names will read as an SPI design at a glance when it is not
-([C5](../../components/stmicroelectronics/st25r3916/README.md#9-caveats-and-gaps)).
-
-⚠ **The second trap is contention, and it is not hypothetical.** NFC polling is chatty. The
-PaperMono's vendor scan app issues **180 ms detect calls at 60 ms intervals for seconds at a time**
-**[SRC]**, and the device record names NFC-polling-versus-charger-gate as **the one documented
-bus-stability hazard on that board**
-([features/nfc.md §9](../../devices/m5stack/papermono/features/nfc.md)). **General rule: if the NFC
-front end shares an I²C bus with anything latency-sensitive, schedule around the scan windows rather
-than hoping.**
-
-### 5.2 The operation byte, and why a driver seems to read a register that does not exist
-
-The ST25R3916 puts an **operation byte** in front of every transaction — top two bits select the
-operation, bottom six carry an address or command **[DS]** (full table at
-[§3.3](../../components/stmicroelectronics/st25r3916/README.md#33-the-mode-byte-why-the-firmware-reads-register-0x7f)).
-Register read is `0x40 | addr`; the IC identity register is at `0x3F`; therefore firmware that reads
-identity sends `0x7F`, and **there is no register `0x7F`** **[DS]** + **[SRC]**, two independent
-sources agreeing exactly.
-
-This pattern — a command/address byte rather than a flat register file — recurs across radio front
-ends. The SX126x does the same thing more aggressively ([LoRa guide §5](../lora/README.md)). **When a
-driver constant does not appear in the register map, check whether it is an operation byte before
-concluding the documentation is wrong.**
-
-Two further behaviours generalise as habits:
-
-- **Auto-increment.** All read and write modes auto-increment, so a burst is one operation byte, one
-  address and then a stream **[DS]**.
-- ⚠ **A non-existent register reads back as all zeros, not a NACK** **[DS]**. **A successful zero
-  read proves nothing about the bus.** Probe with a register whose reset value is documented and
-  non-zero.
-
-### 5.3 Register banks
-
-The ST25R3916 has two 64-register spaces, **A** (everything ordinary) and **B** (sparse: EMD
-suppression, correlator, squelch, TX driver timing, overshoot/undershoot protection), with space B
-reached by prefixing the transaction with direct command **`0xFB`** **[DS]**. RFAL and `M5Unit-NFC`
-both encode this — the latter as `PREFIX_SPACE_B = 0xFB << 8` **[SRC]**.
-
-**Generic hazard:** a banked register map means an address is ambiguous without its bank, and a
-half-finished bank switch corrupts every subsequent access. If you hand-roll, make the bank part of
-the address type, not a mode flag.
-
-### 5.4 Interrupts
-
-The ST25R3916's `IRQ` is **active high** and **push-pull — not open-drain, and therefore not
-shareable** **[DS]**. Four interrupt status registers (main, timer-and-NFC, error-and-wake-up,
-passive-target) each have a mask register, and **reading a status register clears it** **[DS]**.
-
-Three general points:
-
-- **Read-to-clear status registers must be read once and cached.** Reading twice loses events.
-- **A push-pull IRQ cannot be wire-ORed** with another device's interrupt. This constrains the board,
-  not the firmware.
-- ⚠ **Polling instead of using the IRQ is common and usually undocumented.** The PaperMono's vendor
-  firmware sets `cfg.using_irq = false` and polls, leaving the interrupt path **unexercised by any
-  vendor code** **[SRC]**
-  ([features/nfc.md §7](../../devices/m5stack/papermono/features/nfc.md)). If you switch a working
-  polled design to interrupts, you are the first person to test that path.
-
-### 5.5 FIFO
-
-512 bytes on the ST25R3916, reached through its own operation-byte codes — `0x80` to load, `0x9F` to
-read **[DS]**. FIFO status lives in two registers at `1Eh`–`1Fh` **[DS]**.
-
-The generic discipline: **a framing engine with a FIFO wants to be fed and drained on watermark
-interrupts, not on completion.** For short NFC frames this rarely bites; for a long ISO-DEP exchange
-or a 255-byte Type 4 APDU it does.
-
-### 5.6 The shape of a poll cycle
-
-Assembled from the ST25R3916 direct-command table **[DS]** and the vendor demo's call sequence
-**[SRC]**. **Not run on hardware.**
-
-```
-power/enable the front end                (board-specific — see the device record)
-send the mandatory post-POR frame          FCh / 04h / 10h              §5.7
-Set default                     C0/C1     → then re-send the frame above
-configure IO config 1 and 2               00h, 01h
-Adjust regulators               D6h        (ST: "to improve the system PSRR")
-[if AAT is fitted] run the tuning procedure
-
-per technology:
-  select technology + bit rate            mode definition 03h, bit rate 04h
-  NFC initial field ON            C8      performs RF collision avoidance, then field on
-                                          → raises an interrupt on completion
-  poll                            C6/C7   Transmit REQA / WUPA  (ISO 14443A only)
-  anticollision + select                  (framing engine + protocol layer)
-  transceive                      C4/C5   Transmit with / without CRC
-  halt                            CD/CE   Go to sense (Idle) / sleep (Halt)
-  field off                               before switching technology
-```
-
-⚠ **Commands marked "interrupt after termination" must be waited on.** The datasheet warns that on
-I²C **no bus access may be made while such a command runs** — completion is signalled by interrupt
-precisely so the host knows the bus is free again **[DS]**. A driver that polls a status register
-during a running direct command is violating the interface.
-
-The "field off before switching technology" step is real and is what the vendor app does —
-`disableField()` between modes, with a settling delay **[SRC]**
-([features/nfc.md §5](../../devices/m5stack/papermono/features/nfc.md)).
-
-### 5.7 Power states, and one mandatory magic write
-
-The ST25R3916's operation control register drives everything, and the mode ladder is steep **[DS]**
-([§4](../../components/stmicroelectronics/st25r3916/README.md#4-operating-modes-power-states-and-wake-up)):
-**0.8 µA** power-down · **3.0 µA** wake-up · **4.5 mA** ready · **16 mA** fully active.
-
-Three things generalise:
-
-- **Wake-up mode is the feature to know about.** A low-power RC oscillator takes periodic amplitude,
-  phase or capacitance measurements and interrupts only on a departure from a stored reference
-  **[DS]**. **This is how a reader detects a card without keeping the field on** — the difference
-  between a battery device that lasts days and one that lasts hours. On the PaperMono **no vendor
-  code touches it** and the board cuts the chip's supply instead **[SRC]**.
-- ⚠ **Power-down current is temperature-dependent by an order of magnitude.** The PaperMono
-  schematic annotates "2.5 µA"; that is the datasheet **maximum at ≤25 °C**. At 85 °C the maximum is
-  **20 µA**, at 125 °C **60 µA** **[DS]**
-  ([C4](../../components/stmicroelectronics/st25r3916/README.md#9-caveats-and-gaps)). **A sleep
-  budget built from a room-temperature maximum is wrong in a warm enclosure.**
-- ⚠ **There is a mandatory undocumented-looking write.** ST requires the 3-byte frame
-  **`FCh / 04h / 10h`** after power-on *and* after every `Set default`, "to prevent the internal
-  overheat protection to trigger below the junction temperature" **[DS]**. `FCh` is the *Test access*
-  direct command, so this is a write into test register space and it looks like a magic number
-  because it is one. Whether `M5Unit-NFC` issues it **was not traced** and is a live open question
-  ([C6](../../components/stmicroelectronics/st25r3916/README.md#9-caveats-and-gaps)). **If you are
-  evaluating any ST25R3916 driver, grep for `0xFC` first.**
-
-Note also that the ST25R3916 **has no reset pin in any package** **[DS]**. Anything on a board named
-"NFC reset" is a supply gate — on the PaperMono, demonstrably so
-([§10.2](../../components/stmicroelectronics/st25r3916/README.md#102-pyb_nfc_en-and-pyb_rfid_rst-are-the-same-wire-and-it-is-a-rail-enable)).
-Cycling it is a cold start, and the `FCh/04h/10h` frame must be re-sent afterwards.
-
----
-
-## 6. Software stacks
-
-| Stack | Scope | Silicon | Licence **[DOC]** | Maintenance, checked 2026-09-02 **[DOC]** | Good for |
-|---|---|---|---|---|---|
-| **ST RFAL** | Full: RF abstraction → technology layers → ISO-DEP/NFC-DEP → tag types → NDEF | ST25R only | `NOASSERTION` on the stm32duino packaging | ✅ `stm32duino/ST25R3916` pushed **2026-08-31**; `NFC-RFAL` 2.0.2, "based on version 3.0.0 of the RFAL Middlewares from STM32Cube" | Anything serious on ST silicon. The reference implementation |
-| **`M5Unit-NFC`** | Full, and reaches higher: Crypto1, AES, DESFire helpers, ISO-DEP, NDEF, APDU | ST25R3916 (SPI **and** I²C) | — | Pinned by PaperMono firmware at **0.1.0** and **vendor-patched** **[SRC]** | M5Stack hardware. It is what ships |
-| **`libnfc`** | Host-side reader abstraction | ⚠ **PN53x family and readers, not ST25R** **[REC]** | LGPL-3.0 | Alive but slow: last push **2025-03-05** | Linux/PC with a PN532 or ACR122. **Irrelevant to an ST25R3916** |
-| `adafruit/Adafruit-PN532` | Reader, NDEF basics | PN532 | `NOASSERTION` | last push 2025-02-18 | Arduino PN532 |
-| `elechouse/PN532` | Reader, some P2P | PN532 | ⚠ none declared | last push 2026-07-28 | Arduino PN532 |
-| `miguelbalboa/rfid` | Reader, MIFARE Classic | MFRC522 | Unlicense | ⚠ **frozen**: *"development by owner miguelbalboa has ended"*, maintenance badge `no/2019` | Legacy projects only |
-| `OSSLibraries/Arduino_MFRC522v2` | Successor to the above | MFRC522 | LGPL-2.1 | last push 2026-04-01 | New MFRC522 work |
-| `ATrappmann/PN5180-Library` | Reader | PN5180 | LGPL-2.1 | ⚠ **archived**, last push 2022-06 | Nothing new |
-| `pguyot/st25r391x` | Linux kernel driver | ST25R3916/7 | GPL-2.0 | last push 2024-05 | Linux hosts |
-| `vouch-opensource/zephyr-st25r` | Zephyr driver | ST25R | Apache-2.0 | last push 2023-05 | Zephyr, with caution |
-
-**What the maintenance column actually tells you.** Two of the most-linked Arduino NFC libraries are
-frozen or archived, and neither says so on its front page in a way a search result surfaces. That is
-the practical reason to prefer the ST + RFAL path for new work on this class of part: it is the one
-line in the table with a 2026 commit *and* a vendor behind it.
-
-### 6.1 RFAL's structure, and the one thing to know before porting it
-
-Read live from `stm32duino/NFC-RFAL` @ `main` and `stm32duino/ST25R3916` @ `main`, 2026-09-02
-**[SRC]**. The split across two packages *is* the portability story:
-
-```
-NFC-RFAL  (silicon-independent)          ST25R3916  (silicon-specific)
-  rfal_rf.h            the RF interface    rfal_rfst25r3916.cpp      implements rfal_rf.h
-  rfal_nfc.cpp         discovery loop      rfal_rfst25r3916_analogConfig.cpp
-  rfal_nfca/b/f/v.cpp  technologies        rfal_rfst25r3916_analogConfigTbl.h
-  rfal_isoDep.cpp      ISO 14443-4         rfal_rfst25r3916_iso15693_2.cpp
-  rfal_nfcDep.cpp      NFC-DEP / P2P       st25r3916_com.cpp         bus layer
-  rfal_t1t/t2t/t4t.cpp tag operations      st25r3916_interrupt.cpp
-  rfal_st25tb/st25xv   ST tag families     st25r3916_aat.cpp         AAT (§4.6)
-  ndef_*.cpp           NDEF (§1.4)         st25r3916_timer.cpp
-  st_errno.h                               st25r3916_{,default_}config.h
-```
-
-**Porting means implementing the bus and timer layer**, not the protocols: `st25r3916_com.cpp`,
-`st25r3916_timer.cpp` and the interrupt plumbing are the files that touch a platform. Everything
-above `rfal_rf.h` is portable by construction. **[INF]** from the file layout; ST does not state it
-in this packaging.
-
-⚠ **`rfal_rfst25r3916_analogConfigTbl.h` is the file people do not expect.** RFAL ships a table of
-**analog register settings per technology, per bit rate, per direction** — receiver gain, modulation
-depth, thresholds. Those values are matched to a reference antenna. **A design with a different
-antenna may need a different table**, which is precisely the coupling §4 warns about: the "software"
-and the "antenna" are not separable on this class of part. **[INF]** from the file's existence and
-naming; the tuning procedure itself is ST application-note material this repository does not hold.
-
-### 6.2 `M5Unit-NFC` is not an RFAL wrapper
-
-Worth stating because the assumption is natural and wrong. The
-[ST25R3916 record §7.1](../../components/stmicroelectronics/st25r3916/README.md#71-m5unit-nfc-is-a-from-scratch-driver-not-an-rfal-wrapper)
-enumerated the pinned tree — 301 entries — and found **no RFAL directory, no ST source file and no ST
-licence header** **[SRC]**. It is M5Stack's own implementation, it goes further up the stack than
-RFAL's Arduino packaging does (Crypto1, DESFire helpers), and it has correspondingly less provenance
-behind it.
-
-⚠ **Every M5Stack dependency in that firmware is pinned *and patched*.** A library-manager install
-gives you neither the pinned commit nor the vendor's patch **[SRC]**.
-
----
-
-## 7. Regulatory and safety context
-
-⚠ **Not legal advice. This repository holds none of the standards cited here.** [STD] and [REC]
-throughout; check with someone qualified before shipping.
-
-- **13.56 MHz inductive readers are regulated by field strength, not by transmit power.** The
-  European standard is **ETSI EN 300 330** (9 kHz – 25 MHz, inductive loop systems) and the US rule
-  is **47 CFR §15.225**, which carves out 13.553–13.567 MHz with a field-strength limit measured at a
-  specified distance **[STD]**. The limit is on **H-field at a distance**, which is why a bigger coil
-  is a legitimate way to get more range and more drive current often is not.
-- **Read range is fundamentally capped, and not by your firmware.** §4.1's 1/r³ roll-off plus a
-  field-strength ceiling is the reason NFC is a *proximity* technology by design. Vicinity
-  (ISO 15693) reaches further because it tolerates a much weaker field, not because it is allowed
-  more of one **[REC]**.
-- **Thermal and electrical limits are real.** The ST25R3916 can push **350 mA** into an antenna
-  against a **300 mW** dissipation ceiling **[DS]**, and ST's mandatory overheat-protection frame
-  (§5.7) exists because of exactly that gap.
-- **Collision handling is part of the protocol, not an optimisation.** Each technology defines its
-  own anticollision, and the field-on commands `C8`/`C9` perform **RF collision avoidance** before
-  switching the field on — i.e. the chip checks for an existing external field first **[DS]**. That
-  matters when two readers are near each other; also see the external field detector bits in the
-  operation control register **[DS]**.
-- **Certification does not come for free with a chip.** The
-  [PaperMono has no published certification of any kind, including for its 13.56 MHz emitter](../../components/stmicroelectronics/st25r3916/README.md#9-caveats-and-gaps)
-  — a **verified negative** **[DOC]**. A front-end IC with EMVCo-compliant analog says nothing about
-  *your* board with *your* antenna.
-
----
-
-## 8. Debugging and diagnostics
-
-### 8.1 Telling the four common failures apart
-
-| Symptom | Likely class | How to discriminate |
-|---|---|---|
-| Chip not on the bus at all | **Power or enable** | Is the front end's rail actually up? On many designs the chip is behind a load switch controlled by an expander — no I²C, no NFC. Also: is this the SKU that has NFC? |
-| Bus responds, identity read returns `0x00` | **Bus or address, not silicon** | ⚠ Zeros are the documented response to a non-existent register **[DS]**; they are also what a floating bus looks like. Read a register with a documented non-zero reset value |
-| Identity correct, **no tag ever detected in any technology** | **Field, matching, or antenna** | Field never enabled; matching wrong; coil detuned by its surroundings. Check the field-on command actually completed (it interrupts on completion **[DS]**) before blaming the tag |
-| Detects in one technology, never in another | **Protocol / configuration**, not RF | Wrong layer for the card; bit rate mismatch; analog configuration wrong for that technology (§6.1). Try NFC-A first — it is the best-tested path everywhere |
-| Detects at 0 mm, nothing at 10 mm | **Matching or Q** | Classic under-coupled/detuned signature. Field exists but is weak, or the reply sidebands are being filtered out (§4.3) |
-| Works on the bench coupon, fails in the enclosure | **Antenna environment** | Metal, battery or display behind the coil (§4.5) |
-| Intermittent, correlated with other bus traffic | **Contention** | §5.1. Correlate against the other device's transaction windows |
-| Initialises, then misbehaves after a while, warm | **Thermal / the missing `FCh/04h/10h` frame** | §5.7 |
-| Interrupt never fires but polling works | **Untested IRQ path** | On at least one documented board no vendor code ever enables it **[SRC]** |
-
-### 8.2 What actually distinguishes "no tag" from "wrong protocol" from "bad matching"
-
-The single most useful discriminator on an ST25R3916 is that the chip can **measure its own front
-end** without a tag present. Direct commands **`D3` Measure amplitude**, **`D9` Measure phase** and
-**`DF` Measure power supply** put results into readable registers **[DS]**, and there is an RSSI
-register at `2Dh` **[DS]**.
-
-Consequently:
-
-- **Amplitude/phase stable and plausible with no tag, changing when a tag approaches** → the antenna
-  works and the field exists. A detection failure after that is a **protocol** problem.
-- **Amplitude implausible or unchanging with a tag on the coil** → **matching or antenna**. No amount
-  of protocol work will help.
-- **Amplitude fine, tag changes it, but no technology completes anticollision** → **configuration**:
-  bit rate, analog table, or the wrong technology for the card.
-
-`not-tested` — this is the documented capability of the measurement commands applied as a procedure,
-**[INF]**. It is, however, the reason to prefer a front end that exposes these measurements at all.
-
-### 8.3 Test-tag discipline
-
-**Keep one known tag of each technology and label them.** NFC-A (an NTAG21x), NFC-B (harder to source
-— many bank cards are Type B), NFC-F (a Japanese transit card or FeliCa Lite), NFC-V (an ICODE SLIX
-label). Debugging a reader with an unknown card confounds every diagnosis in §8.1. **[REC]**
-
-And a caution that this library earned honestly: on the one documented device fitting this chip,
-**nobody has reported reading any tag at all** — no vendor test report, no compatibility list, no
-community account, after two independent broad passes
-([features/nfc.md §8](../../devices/m5stack/papermono/features/nfc.md), a **verified negative**).
-**Do not assume a technology works because a chip advertises it and a library exposes a class for
-it.** The existence of a code path is not a read.
-
----
-
-## 9. Validation checklist
-
-Nothing below was executed. This is the sequence the evidence implies, in dependency order.
-
-1. **Confirm the part is fitted at all.** On dual-SKU products this is a real question, and on at
-   least one it is how the firmware itself distinguishes variants **[SRC]**.
-2. **Bring the rail up before touching the bus**, in the board's documented order.
-3. **Probe identity with a documented non-zero value** (§5.2, §8.1).
-4. **Send the vendor-mandated post-POR frame** if the part has one (§5.7).
-5. **Enable the field and confirm completion by interrupt or status**, not by delay.
-6. **Measure amplitude/phase with no tag, then with a tag** (§8.2). Record both. This is your
-   baseline for every future regression.
-7. **Detect NFC-A first**, with a known NTAG.
-8. **Then each other technology in turn**, with a known tag each, field disabled between changes.
-9. **Then read NDEF**, then anything proprietary.
-10. **Then measure read range** at each technology, and **record the antenna environment** — coupon
-    or enclosure — because the number is meaningless without it.
-11. **Then re-run everything at temperature**, if the product has a sleep budget (§5.7).
-
----
-
-## 10. Device-specific pages
-
-| Device | Front end | Applicability |
-|---|---|---|
-| [**M5Stack PaperMono**](../../devices/m5stack/papermono/features/nfc.md) | ST25R3916, I²C, on a sub-board | **Applies with deltas** — I²C strap rather than SPI, no chip reset (the "reset" is a rail gate), interrupt unused by vendor code, `M5Unit-NFC` rather than RFAL |
-| [M5Stack PaperMono-Lite](../../devices/m5stack/papermono-lite/README.md) | **none fitted** | Not applicable — no NFC hardware |
-
----
-
-## 11. Evidence boundary — and what could not be sourced
-
-**This guide contains no new hardware research and no measurements.** Its inherited claims come from
-the [ST25R3916 record](../../components/stmicroelectronics/st25r3916/README.md) and the
-[PaperMono NFC feature guide](../../devices/m5stack/papermono/features/nfc.md) as they stood on
-**2026-09-02**, and carry their labels transitively.
-
-**New to this page, live-verified on 2026-09-02 [SRC]/[DOC]:** the RFAL and NFC-RFAL file layouts and
-versions (2.1.0 / 2.0.2), the absence of MIFARE/Crypto1 from RFAL's Arduino packaging, the absence of
-a Type 1 NDEF mapping, and every library maintenance status in §3 and §6 — including the
-`miguelbalboa/rfid` freeze notice quoted verbatim and the `ATrappmann/PN5180-Library` archived flag.
-
-**New and derived here [INF]:** the §4.4 EMC-corner arithmetic and the observation that the record's
-inferred L–C pairing lands below the carrier; the §4.3 `Q ≲ 8` bound; the §4.5 order-of-magnitude
-range bound from antenna geometry; the §6.1 porting-boundary reading; the §8.2 diagnostic procedure.
-
-### Claims I could not source
-
-| Claim | Why it is unsourced | Risk if wrong |
-|---|---|---|
-| **Every ISO/IEC and JIS modulation, coding and subcarrier detail in §1.1** | This repository holds **no** ISO/IEC 14443, 15693 or 18092 document, and none is freely obtainable | Low for the structure, moderate for specific numbers. `fc/16` and `fc/32` are the ones a design would actually depend on |
-| **The tag-product mapping in §1.2** | No NXP, Sony, Broadcom or TI tag datasheet is held | Low. Verify memory sizes before designing to them |
-| **MIFARE Classic's Crypto1 layering (§1.3)** | Proprietary; no document | Low — the practical consequence (a stack either has Crypto1 or does not) is confirmed by the two trees actually enumerated |
-| **Reader-antenna Q targets (§4.3)** | This repository holds **no NFC antenna application note** from ST or NXP. The `B = f₀/Q` arithmetic is sound; the *target* is not stated | **Moderate.** This is a real gap for anyone doing a design review |
-| **The 1/r³ near-field roll-off and the "range ≈ coil radius" rule (§4.1, §4.5)** | Standard magnetostatics, but no document behind it here | Low as an order-of-magnitude bound; **do not quote it as a specification** |
-| **ETSI EN 300 330 and 47 CFR §15.225 (§7)** | Neither document is held; cited by number only | **High if relied upon.** Get the actual limits from the actual regulation |
-| **Everything about PN532, PN5180, MFRC522 and ST25R3911B capability in §3** | No datasheet for any of them | **Moderate** — the table decides part selection. Library-maintenance cells in the same table *are* sourced |
-| **Android's removal of Beam/P2P (§2)** | Recalled; no citation retrieved | Low; the conclusion (prefer card emulation) is robust either way |
-| **Whether RFAL's analog configuration table must be retuned per antenna (§6.1)** | Inferred from the file's existence and name. ST's tuning procedure was not located | **Moderate.** It is the right question to ask a vendor, not yet an established fact |
-
-### Where this guide sits relative to the deep records
-
-**No contradiction was found** with the ST25R3916 record or the PaperMono feature guide. One point of
-**tension**, recorded rather than resolved: §4.4's corner-frequency arithmetic sits uneasily with the
-"Almost certainly" component attribution in
-[ST25R3916 §5.3](../../components/stmicroelectronics/st25r3916/README.md#53-the-parts-that-are-there).
-That column is already labelled as inference and its §5.2 already states the topology was not
-traced, so this is a **new open observation, not a conflict** — and the deep record's own caution is
-what makes it visible.
-
----
-
-## Related
-
-- [**ST STMicroelectronics ST25R3916**](../../components/stmicroelectronics/st25r3916/README.md) — the deep record: register spaces, operation byte, power states, the real front end, the mandatory `FCh/04h/10h` frame
-- [M5Stack PaperMono — NFC feature guide](../../devices/m5stack/papermono/features/nfc.md) — the device-specific companion to this page
-- [M5Stack PaperMono — device record](../../devices/m5stack/papermono/README.md) · [gaps and conflicts](../../devices/m5stack/papermono/gaps-and-conflicts.md)
-- [**LoRa — a device-independent guide**](../lora/README.md) — the other radio on the same board, and the same `BUSY`/command-byte/errata patterns in a different key
-- [Guides index](../README.md) · [Components index](../../components/README.md) · [Devices index](../../devices/README.md)
-- [Vendor sourcing guides](../../vendors/README.md) — ⚠ **no STMicroelectronics guide exists yet**; the retrieval findings in [ST25R3916 §8](../../components/stmicroelectronics/st25r3916/README.md#8-sourcing-and-documentation) are what one would open with
diff --git a/guides/nixos/riscv-and-vendor-sdk-toolchains.md b/guides/nixos/riscv-and-vendor-sdk-toolchains.md
deleted file mode 100644
index c0a5c34..0000000
--- a/guides/nixos/riscv-and-vendor-sdk-toolchains.md
+++ /dev/null
@@ -1,129 +0,0 @@
-# RISC-V and vendor-SDK toolchains on NixOS
-
-Companion to [`guides/nixos/README.md`](README.md), which covers ESP-IDF, Arduino, PlatformIO
-and the SDR/mesh tooling. **This file is new (2026-09-04) and adds a case that guide does not
-cover: a vendor SoC SDK that is not ESP-IDF, is not Arduino, is not upstream RISC-V GCC, and is
-built by Buildroot against a hard-coded absolute path.**
-
-The worked example is the [Canaan Kendryte K230](../../components/canaan/k230/README.md) as
-built by [LilyGO's T-Display K230 BSP](../../devices/lilygo/t-display-k230/README.md), which is
-the first RISC-V Linux target in this repository.
-
-> **Evidence boundary, stated up front.** Nothing here has been built. **No `nix build`, no
-> `nixos-rebuild`, no Buildroot run, no flash.** Every claim is either read directly out of the
-> vendor's committed build configuration (labelled *read from source*) or is reasoning about how
-> NixOS behaves (labelled *inferred*). Treat build success as unverified.
-
----
-
-## 1. Why `guides/nixos/README.md` does not already answer this
-
-That guide's §2 lists `pkgsCross.riscv64-embedded` and `pkgsCross.riscv32-embedded` as present
-in the locked nixpkgs. Both exist. **Neither is usable for this target**, for three independent
-reasons, all *read from source* in the vendor Buildroot defconfig:
-
-```
-BR2_TOOLCHAIN_EXTERNAL=y
-BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
-BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/toolchain/Xuantie-900-gcc-linux-6.6.0-glibc-x86_64-V3.0.2/"
-BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX="riscv64-unknown-linux-gnu"
-BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
-BR2_TARGET_OPTIMIZATION="-mcpu=c908v -mtune=c908 -mrvv-v0p10-compatible -mrvv-auto-vectorize"
-```
-
-1. **`-mcpu=c908v` is not a mainline GCC option value.** It is a T-Head/XuanTie extension.
-   Mainline `riscv64-unknown-linux-gnu-gcc` rejects it. There is no flag translation that
-   preserves the vendor's intent, because the vendor compiler also carries T-Head-specific
-   scheduling and extension support.
-2. **`-mrvv-v0p10-compatible` targets the *draft* RVV 0.10 encoding**, not ratified RVV 1.0.
-   The C908 implements RVV 1.0, but the shipped userspace is deliberately built in the
-   compatibility mode. A mainline RVV-1.0 GCC produces a different, non-interchangeable ABI.
-3. **`riscv64-embedded` is a bare-metal (`-elf`) cross, not `-linux-gnu`.** Wrong libc, wrong
-   target triple, wrong sysroot model. `pkgsCross.riscv64-linux` would be the right *shape*, but
-   see (1) and (2).
-
-**Conclusion (inferred):** for the K230 Linux SDK there is no nixpkgs substitute. The vendor
-compiler must be obtained and used as a binary.
-
-## 2. The `/opt/toolchain` problem, and the three ways out
-
-`BR2_TOOLCHAIN_EXTERNAL_PATH` is an **absolute path baked into a committed config file**. On a
-normal distribution you untar the XuanTie release into `/opt/toolchain/` and it works. NixOS has
-no `/opt`, and even if you create one, the toolchain binaries are dynamically linked against a
-standard-FHS `ld-linux-x86-64.so.2` and glibc that do not exist at those paths.
-
-| Route | What it is | Assessment |
-|---|---|---|
-| **A. Docker** | Canaan publishes `ghcr.io/kendryte/k230_sdk` and documents it as the supported build environment. `virtualisation.docker.enable = true;` and build inside. | **Recommended.** It is the vendor's own supported path, it sidesteps every FHS issue, and it is what LilyGO's wiki tells you to do on Windows too. The one cost is that the container is opaque and unpinned by digest in the vendor's instructions — pin it yourself. |
-| **B. `buildFHSEnv`** | Wrap the whole Buildroot invocation in an FHS sandbox that provides `/opt/toolchain`, glibc, and the usual `/usr/lib` shape. | Workable and is the same pattern this repository already uses for [SquareLine Studio](README.md#5-squareline-studio). More work than Docker for a build that runs once. |
-| **C. `autoPatchelfHook` + a store path** | `fetchurl` the XuanTie tarball, patch its ELF interpreters, then either symlink it to `/opt/toolchain/...` or override `BR2_TOOLCHAIN_EXTERNAL_PATH`. | The most "Nix-native" answer and the most fragile. Buildroot also wants a *writable* tree in places and will fight a read-only store path. |
-
-**Whichever route you take, override the path rather than creating `/opt`.** Buildroot reads
-the variable from `.config`, so `make BR2_TOOLCHAIN_EXTERNAL_PATH=... ` or a `defconfig` fragment
-is cleaner than an impure filesystem mutation. *(Inferred — not executed.)*
-
-## 3. The rest of the build is ordinary Buildroot, with ordinary Buildroot NixOS problems
-
-Read from the same defconfig:
-
-- The kernel is **not mainline**: `BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/ruyisdk/linux-xuantie-kernel.git"`
-  pinned at commit `7d4e1f444f461dbe3833bd99a4640e7b6c2cd529`, defconfig `k230`.
-- Buildroot **downloads during the build** (`BR2_DL_DIR="$(TOPDIR)/../../dl"`). A pure Nix
-  derivation cannot do that. Either pre-populate `dl/` and run outside Nix, or accept an impure
-  build. This is the standard Buildroot-on-Nix conflict and it is not K230-specific.
-- Buildroot's own host tooling wants `/usr/bin/env`-style assumptions in a number of packages.
-  `nix-shell -p` with the usual set (`git`, `gnumake`, `rsync`, `python3`, `bc`, `ncurses`,
-  `perl`, `wget`, `cpio`, `unzip`, `file`, `which`, `openssl`) plus an FHS wrapper is the
-  pragmatic combination.
-
-**Host requirement stated by the vendors:** Canaan documents Ubuntu 20.04; LilyGO documents
-Ubuntu 22.04 or 24.04 and runs `./scripts/setup_ubuntu.sh` to install host dependencies. That
-script is `apt`-based and will not run on NixOS. Read it for the dependency list, then translate.
-
-## 4. The other three toolchains this board needs
-
-The K230 board is the extreme case where **one product needs four unrelated toolchains**. Only
-one of them is a problem on NixOS.
-
-| Target | Toolchain | NixOS status |
-|---|---|---|
-| K230 (RISC-V Linux) | XuanTie GCC + Buildroot | **Hard** — §2 above |
-| nRF52840 companion | **PlatformIO**, `platform = nordicnrf52`, board `nrf52840_dk_adafruit` | **Fine.** `platformio` is present in the locked nixpkgs, and `platformio-core.udev` is already in this repository's `services.udev.packages`. |
-| nRF9151 companion | **nRF Connect SDK v3.4.0** via `nrfutil sdk-manager` | **Mixed.** `nrfutil` is present in the locked nixpkgs. But `guides/nixos/README.md` §2 records `west` and `zephyr` as **absent** — and NCS *is* a Zephyr/west workspace. `nrfutil sdk-manager install --install-dir "$PWD/ncs" v3.4.0` downloads its own SDK and toolchain into a repository-relative directory, which is exactly the "downloaded binary toolchain" pattern from §2 and needs the same FHS treatment. |
-| Flashing the SD image | `dd` | Trivial. |
-
-The nRF9151 case is the interesting one because it **installs into `$PWD/ncs` rather than a
-system path**, and honours `NCS_ROOT`. That is materially friendlier than `/opt/toolchain`: a
-`buildFHSEnv` shell with a project-local `ncs/` directory is enough, with no path override
-needed. *(Inferred from LilyGO's documented commands; not executed.)*
-
-## 5. Device access
-
-Nothing new is needed for the K230 itself — its normal workflow is **write an SD card and boot**,
-plus SSH over Wi-Fi/Ethernet for iteration (`./scripts/deploy_launcher.sh <ip>`). No custom udev
-rule, no vendor programmer.
-
-The companions do need rules, and this repository already ships them:
-
-- **nRF52840 UF2 bootloader** enumerates as USB **mass storage** — no udev rule required, but the
-  device must be mountable by the user. Also enumerates as a USB CDC serial port for logs.
-- **nRF52840 / nRF9151 serial** → `dialout` group, already configured.
-- **PlatformIO** → `platformio-core.udev`, already in `services.udev.packages`.
-
-## 6. What would make this verifiable
-
-In order of value:
-
-1. Run `./scripts/setup_ubuntu.sh` under `strace`/read it, and produce the exact host dependency
-   list as a Nix package set.
-2. Build once inside `ghcr.io/kendryte/k230_sdk` on this host and record the image digest.
-3. Attempt route C (`autoPatchelfHook` on the XuanTie tarball) and record whether Buildroot's
-   writability assumptions break it, and where.
-
-None of the three were attempted on 2026-09-04.
-
-## 7. Cross-references
-
-- [`guides/nixos/README.md`](README.md) — the parent guide (ESP-IDF, PlatformIO, device access, package availability)
-- [`components/canaan/k230`](../../components/canaan/k230/README.md) §14 — the toolchain facts, at the chip level
-- [`devices/lilygo/t-display-k230/development.md`](../../devices/lilygo/t-display-k230/development.md) — the board's full build and flash procedure
diff --git a/guides/research/finding-certification-records.md b/guides/research/finding-certification-records.md
deleted file mode 100644
index a721be8..0000000
--- a/guides/research/finding-certification-records.md
+++ /dev/null
@@ -1,344 +0,0 @@
-# Finding certification and regulatory records
-
-**Created 2026-09-11.** Method guide for source class **3** in
-[`.agents/skills/hardware-device-research/SKILL.md`](../../.agents/skills/hardware-device-research/SKILL.md)
-§3 — *standards bodies and certification/regulatory databases*.
-
-Everything below was **live-probed on 2026-09-11** from this host. Every URL template carries a
-measured status code. Two controls — one positive, one negative — are run and recorded, because
-**without them an "absent" result is not evidence.**
-
----
-
-## 0. Why this guide exists
-
-A seven-session sweep searched for Xteink certification records, found none, and wrote that
-"no external CE/FCC marking exists on the devices at all". It then honestly added: *"No positive
-control was run, so the absence is weaker evidence than it looks."*
-
-It was right to worry. **Xteink holds FCC grantee code `2BTR9` with five granted FCC IDs.**
-The search method, not the world, was at fault.
-
-Two distinct failures produced that result, and both are common:
-
-1. **No control.** If your search returns nothing for a device that *is* certified, you cannot
-   tell "not certified" from "search broken". You must prove the method finds a known-good
-   record *in the same run*.
-2. **Conflating two claims.** "No mark visible in a product photo" and "no certification grant
-   exists" are different propositions with different evidence. A device may legally carry an
-   **e-label** in software instead of a printed mark (47 CFR §2.935). Never let one stand in for
-   the other.
-
----
-
-## 1. Run the controls first. Always.
-
-Before believing any absence, run both in the same session and record the status codes.
-
-```bash
-UA='curl/8.5.0'
-probe(){ printf '%-24s %s\n' "$1" "$(curl -sL -A "$UA" --max-time 30 \
-        -o /dev/null -w '%{http_code}' "https://fccid.io/$1")"; }
-
-# POSITIVE — must return 200. Pick something you are certain is certified.
-probe 2AC7Z-ESPS3WROOM1      # ESP32-S3-WROOM-1, Espressif. The module inside half these boards.
-probe 2AN3WM5CARDPUTER       # a device you already enumerated from its grantee page
-
-# NEGATIVE — must return 404. Invent IDs that look completely plausible.
-probe 2AN3WM5CARDPUTERZERO   # right grantee, plausible product code, does not exist
-probe 2ASYE-T-DISPLAY-K230   # matches LilyGO's hyphenated house style exactly
-probe 2ZZZZNOSUCHGRANTEE     # invented grantee
-```
-
-Measured 2026-09-11 (`logs/fcc-controls.txt` in the scratch dir; status: `executed-success`):
-
-| ID probed | HTTP | Bytes | Verdict | Role |
-|---|---|---|---|---|
-| `2AC7Z-ESPS3WROOM1` | **200** | 75 066 | granted | **positive** — ESP32-S3-WROOM-1 |
-| `2AC7Z-ESPS3WROOM1U` | **200** | 31 810 | granted | **positive** — U.FL variant |
-| `2AN3WM5CARDPUTER` | **200** | 30 445 | granted | **positive** |
-| `2BTR9-XTEINKX4` | **200** | 22 648 | granted | **positive** |
-| `2AN3WM5CARDPUTERZERO` | **404** | 8 981 | absent | **negative** — invented |
-| `2ASYE-T-DISPLAY-K230` | **404** | 9 005 | absent | **negative** — invented |
-| `2AN3WM5CAPLORA868` | **404** | 8 930 | absent | **negative** — invented sibling of a real ID |
-| `2AC7Z-ESPZZ9NOTREAL` | **404** | 8 965 | absent | **negative** — invented under a real grantee |
-| `2ZZZZNOSUCHGRANTEE` | **404** | 8 599 | absent | **negative** — invented grantee |
-
-4/4 positive → 200. 5/5 negative → 404. **The discriminator is the HTTP status code, cleanly
-separated.** Now — and only now — a 404 means something.
-
-> Do **not** use body text as the discriminator. A first attempt here grepped for the word
-> `Exhibits` and scored all nine probes "found", because the string appears in site navigation
-> on the 404 page too. Status code, not page text.
-
----
-
-## 2. The grantee-code trick
-
-This is the core technique and it inverts the obvious approach.
-
-**Do not guess FCC IDs one at a time.** An FCC ID is `<grantee code><product code>`. The grantee
-code is a stable 3–5 character identifier assigned once per company; the product code is chosen
-freely by the applicant and is unguessable (`2AN3WSTAMPLORA1262` has no `M5` prefix while
-`2AN3WM5CAPLORA1262` does — same company, same year, same product family).
-
-So: **find the grantee code once, then enumerate everything under it.**
-
-```bash
-# Step 1 — company search finds the grantee code
-curl -s -A 'curl/8.5.0' 'https://fccid.io/search?q=LilyGO'
-#   → Shenzhen Xin Yuan Electronic Technology Co., Ltd. (2ASYE)
-
-# Step 2 — the grantee page lists every ID, with dates and product names, on one page
-curl -sL -A 'curl/8.5.0' 'https://fccid.io/2ASYE' -o grantee.html
-```
-
-Search the **legal entity name**, not the brand. LilyGO's filings are all under *Shenzhen Xin
-Yuan Electronic Technology Co., Ltd.*; Xteink's are under *Shenzhen Xiaohu Xingtong Technology
-Co., Ltd.* A brand-name search happened to work for both here, but only because fccid.io indexes
-product names as well.
-
-Grantee codes established 2026-09-11:
-
-| Brand | Legal applicant | Grantee | Registered | IDs |
-|---|---|---|---|---|
-| **M5Stack** | M5Stack Technology Co.,Ltd | **`2AN3W`** | 2017-10-23 | 59 |
-| **LilyGO** | Shenzhen Xin Yuan Electronic Technology Co., Ltd. | **`2ASYE`** | 2019-04-05 | 33 |
-| **Espressif** | ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD | **`2AC7Z`** | 2014-09-15 | 78–80 |
-| **Xteink** | Shenzhen Xiaohu Xingtong Technology Co., Ltd. | **`2BTR9`** | 2025-12-21 | 5 |
-
-Parse the grantee page with:
-
-```python
-pat = re.compile(
-  r'<tr><td data-label="FCC ID / Date"><b><a href="/([^"]+)">[^<]+</a></b><br>([\d-]+)</td>'
-  r'<td data-label="Product / Type">(.*?)<br>(.*?)</td></tr>', re.S)
-```
-
-**Trap:** the grantee page header for `2BTR9` says *"6 FCC IDs"* but the table lists **5**, and
-only 5 `href`s exist. The headline count and the table disagree. Trust the table; report the
-discrepancy.
-
-**Trap:** `?page=N` on a grantee URL returns **302** and drops you. Fetch the bare
-`https://fccid.io/<GRANTEE>` and read `Page N of M` from the panel heading instead. All four
-grantees above fit on one page.
-
----
-
-## 3. Which databases are reachable without login
-
-Measured 2026-09-11, browser UA unless noted.
-
-| Database | URL | HTTP | Login? | Verdict |
-|---|---|---|---|---|
-| **fccid.io** (FCC mirror) | `https://fccid.io/<ID>` | **200** *(with `curl` UA — see §4)* | no | ✅ **the workhorse** |
-| FCC official EA search | `https://apps.fcc.gov/oetcf/eas/reports/GenericSearch.cfm` | **403** | n/a | ❌ blocked to all 5 UAs |
-| FCC official EA landing | `https://www.fcc.gov/oet/ea/fccid` | **403** | n/a | ❌ blocked to all 5 UAs |
-| FCC attachment endpoint | `https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=N` | **403** | n/a | ❌ blocked |
-| FCC open data | `https://opendata.fcc.gov/resource/kfc9-pnvf.json` | **404** | no | ❌ EAS is not published there under that ID |
-| fcc.report (mirror) | `https://fcc.report/FCC-ID/<ID>` | **403** | n/a | ❌ blocked to all 5 UAs |
-| **Japan MIC 技適** | `https://www.tele.soumu.go.jp/giteki/SearchServlet?pageID=js01` | **200** | no | ✅ reachable; form-driven, not probed further |
-| Japan MIC (English) | `https://www.tele.soumu.go.jp/e/index.htm` | **200** | no | ✅ reachable |
-| China CCC (CNCA) | `https://www.cnca.gov.cn/` | **200** | no | ⚠ portal reachable; the searchable CCC register was not reached |
-| China MIIT | `https://www.miit.gov.cn/` | **200** | no | ⚠ portal only |
-| **China SRRC** | `https://wireless.miit.gov.cn/`, `https://www.srrccn.org/` | **000** | n/a | ❌ **connection failed** — no SRRC lookup achieved |
-| ISED Canada REL | `https://sms-sgs.ic.gc.ca/equipmentSearch/searchRadioEquipments?lang=en` | **503** | no | ❌ service unavailable at probe time; retry |
-| ISED CEB | `https://ised-isde.canada.ca/site/certification-engineering-bureau/en` | **200** | no | ✅ landing only |
-| UKCA | `https://www.gov.uk/guidance/using-the-ukca-marking` | **200** | no | ℹ️ **guidance only. There is no UKCA database.** |
-
-### On UKCA and CE: there is no database to search
-
-This trips people up. **CE/UKCA are self-declaration regimes.** No public register of conformity
-exists for either. The only primary artifact is the manufacturer's own **Declaration of
-Conformity (DoC)**, published at the vendor's discretion. If the vendor does not publish one,
-there is nothing to find and *that is the finding*.
-
-Checked 2026-09-11, all **404**:
-
-- `shop.m5stack.com/pages/certificate`
-- `docs.m5stack.com/en/certificate`
-- `www.lilygo.cc/pages/certification`
-
-So for these vendors: **no published DoC was located.** State it that way — not "not CE marked".
-The Cardputer ADV label photograph (§5) shows a **CE mark is printed on the product**, which
-means a DoC legally exists; it simply is not published.
-
----
-
-## 4. ⚠ The inverted user-agent block on fccid.io
-
-`AGENTS.md` teaches: plain request first, then a browser UA, then bot UAs. **On fccid.io that
-ladder is backwards.**
-
-| UA | `fccid.io/` | `fccid.io/2AN3W` | `fccid.io/search?q=…` |
-|---|---|---|---|
-| `Chrome/131.0.0.0` (browser) | 200 | **403** | **403** |
-| `WhatsApp/2.23.20.0` | 200 | **200** | **200** |
-| `ChatGPT-User/1.0` | 200 | **200** | **200** |
-| `ClaudeBot/1.0` | 200 | **200** | **200** |
-| `curl/8.5.0` | 200 | **200** | **200** |
-
-The 403 is a **Cloudflare managed challenge** (`Security check`, `cType: 'managed'`,
-`cZone: 'fccid.io'`) requiring JS and cookies. Cookie jars and `Accept`/`Accept-Language` headers
-do not help. The honest `curl/8.5.0` UA passes.
-
-Note also that the **root** page returns 200 to everything, so a reachability probe against
-`https://fccid.io/` alone reports "site is up" and tells you nothing. **Probe a deep path.**
-
-Per `AGENTS.md` rule 6: a 200 obtained this way is a *retrieval* result only. It is not evidence
-that the resource behaves this way for ordinary clients, and it must not be used to bypass
-authentication or access control. These are public records with no access control; the block is
-anti-scraping, not authorisation.
-
----
-
-## 5. Mining the exhibits — often the only public teardown
-
-FCC filings are **US Government public records**. For a board with no published schematic, the
-filing is frequently the only internal photography that exists anywhere.
-
-### Verified download template
-
-```
-https://fccid.io/<FCC-ID>/<Type-Slug>/<Document-Slug>-<exhibit-id>.pdf
-```
-
-The **`.pdf` suffix is what matters.** The same URL without it returns a 16 KB HTML viewer page.
-
-```bash
-# verified 2026-09-11: 200, application/pdf, 1 848 880 bytes
-curl -sL -A 'curl/8.5.0' \
-  'https://fccid.io/2AN3WM5CARDPUTERADV/Internal-Photos/Internal-Photos-8755029.pdf' \
-  -o internal.pdf
-```
-
-Scrape the exhibit table from the filing page:
-
-```python
-EXH = re.compile(
-  r'<tr><td data-label="Document"><a href="(?P<href>[^"]+)">(?P<doc>.*?)</a></td>'
-  r'<td data-label="Type">(?P<type>.*?)</td>'
-  r'<td data-label="Available">(?P<avail>.*?)</td>'
-  r'<td data-label="File">(?P<file>.*?)</td></tr>', re.S)
-# then: url = 'https://fccid.io' + href + '.pdf'
-```
-
-A reusable harvester is at `scratch/market-and-certification/fcc/harvest.py`.
-Run 2026-09-11 over 26 filings: **~170 PDFs, 198 MB, 0 failures, 0 type mismatches.**
-
-### Which exhibit types are worth the bytes
-
-| Type | Value | Note |
-|---|---|---|
-| **Internal Photos** | ⭐⭐⭐ | The teardown. Board top/bottom, shields off, connectors, battery labels |
-| **ID Label/Location Info** | ⭐⭐⭐ | **Shows other jurisdictions' marks** — CE, UKCA, WEEE, IC, 技適 |
-| External Photos | ⭐⭐ | Enclosure, ports, dimensions against a ruler |
-| Test Report | ⭐⭐ | Antenna gain, conducted power, exact frequency edges |
-| RF Exposure Info | ⭐ | Separation distance, SAR/MPE |
-| Users Manual | ⭐ | Sometimes a pre-release manual not on the vendor site |
-| **Schematics** | — | **Essentially always withheld.** See below |
-| **Block Diagram** | — | Essentially always withheld |
-| **Operational Description** | — | Essentially always withheld |
-
-### Confidentiality: what you will and will not get
-
-**Long-term confidentiality was requested and granted on 26 of 26 filings examined.** In every
-single case the withheld set was the same three: **Schematics, Block Diagram, Operational
-Description.** Do not plan on getting a schematic out of the FCC. Plan on getting photographs.
-
-**Short-term confidentiality is different and it expires.** Three Xteink filings withhold
-photographs until a stated date:
-
-| Filing | Withheld | Released on |
-|---|---|---|
-| `2BTR9-X4PRO` | Internal Photos, Test Setup Photos, Users Manual | **2026-12-12** |
-| `2BTR9-X4C` | Internal + **External** Photos, Test Setup Photos, Users Manual | **2027-01-16** |
-| `2BTR9-X4L` | Internal Photos, Test Setup Photos, Users Manual | **2027-02-09** |
-
-**These dates are diary entries.** The Xteink X4 Pro currently has no public teardown anywhere;
-on 2026-12-12 it will have one. Record the date in the device record rather than concluding "no
-teardown exists".
-
-### ⚠ The exhibit trap that will bite you: labels are photographs
-
-A tempting one-liner: extract the text layer of every `ID Label` exhibit and grep for `CE`,
-`IC:`, `CMIIT`, `UKCA`.
-
-Run over 26 filings on 2026-09-11 it reported **"no secondary marks" on 26 of 26.** That result
-is **entirely false**, and it is a perfect miniature of the mistake this guide exists to prevent.
-
-`pdfimages -list` on the Cardputer ADV label:
-
-```
-page num type  width height color comp bpc enc  ... size ratio
-   1   0 image   947   705 rgb      3   8 jpeg  ... 140K  7.2%
-```
-
-The whole label is **one JPEG photograph**. The PDF text layer contains exactly two things: the
-word `Label` and the string `FCC ID: 2AN3WM5CARDPUTERADV`. There is nothing to grep.
-
-Rendering and looking at that same image shows, on the StampS3A module label: the **FCC logo**,
-a **CE mark**, a **crossed-out wheelie bin (WEEE)**, a recycling mark, Bluetooth and USB logos.
-
-**You must render and look.**
-
-```bash
-nix-shell -p poppler-utils imagemagick --run '
-  pdfimages -png ID-Label-*.pdf out
-  magick "$(ls -S out*.png | head -1)" -crop 150x80+435+245 +repage -resize 700% -sharpen 0x1 zoom.png'
-```
-
-Same caveat for internal photos: they resolve **large** markings well (a 650 mAh battery label
-was legible at 944×708) but a 2 × 2 mm DFN regulator marking was **not** legible even at
-2835×2126 upscaled 300%. Say which parts the photos did and did not resolve.
-
----
-
-## 6. Per-product checklist
-
-1. **Controls.** One positive, one negative, same session, record both status codes.
-2. **Grantee code** via company search on the *legal entity* name.
-3. **Enumerate the whole grantee** — dump every ID, date and product name to a file.
-4. **Match products to IDs by name and date**, not by guessing product codes.
-   A missing product is now a real absence, because step 1 proved the method works.
-5. **Fetch each filing page**; record frequencies, equipment class, test firm, TCB,
-   confidentiality status, and the full exhibit table including withheld rows and release dates.
-6. **Download exhibits** with the `.pdf` template. Validate magic bytes (`%PDF-`), not the
-   extension.
-7. **Render the label and the internal photos and actually look at them.** Record what you could
-   and could not resolve.
-8. **CE/UKCA:** look for a DoC PDF on the vendor site. If none, say "no published DoC located",
-   never "not CE marked" — check the label photograph for the mark itself.
-9. **Module vs. device.** If the board carries a pre-certified module, the module's grant may be
-   what matters. If the board has a bare SoC and a PCB antenna, the vendor needed their own
-   Original Equipment grant — which is why Xteink has one.
-10. **Record absences with the controls attached.** An absence without a control is not a finding.
-
----
-
-## 7. Reading an FCC ID
-
-```
-2AN3W  M5CARDPUTERADV
-└─┬─┘  └──────┬──────┘
-  │           └─ product code — applicant's free choice, unguessable
-  └───────────── grantee code — stable per company, the thing to search for
-```
-
-Grantee codes beginning with `2` are post-2013 assignments. A hyphen may or may not appear
-between the two halves and **is part of the ID**: `2AN3WM5DINMETER` has none,
-`2BTR9-X4PRO` does, and the same grantee uses both styles
-(`2AN3WM5STAMP-C3` vs `2AN3WM5STAMPS3A`). If a lookup 404s, try it both ways before concluding
-absence.
-
----
-
-## 8. Cross-references
-
-- Scratch, raw data and the full failure log:
-  [`scratch/market-and-certification/README.md`](../../scratch/market-and-certification/README.md)
-- UA/site access matrix, repo-wide:
-  [`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md)
-- Vendor documentation-sourcing guides: [`vendors/`](../../vendors/)
-- Sibling method guide:
-  [`finding-projects-that-use-a-board.md`](finding-projects-that-use-a-board.md)
diff --git a/guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md b/guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md
deleted file mode 100644
index 36f4eb5..0000000
--- a/guides/reverse-engineering/tracing-nets-from-schematic-pdfs.md
+++ /dev/null
@@ -1,290 +0,0 @@
-# Tracing nets from schematic PDFs
-
-**Created:** 2026-09-07. **Status:** technique verified on 15 vendor schematics this session.
-**Tooling verified:** poppler **26.06.0**, ImageMagick 7, on Linux via `nix-shell -p`.
-
-A vendor schematic PDF is usually treated as a picture to be squinted at. For the large majority
-of them that is wrong: they are **vector documents with a complete, coordinate-accurate text
-layer**, and several EDA tools additionally emit *invisible* helper tokens that name every pin
-and every net. Once you know that, a schematic becomes a database you can query, and a net list
-can be recovered without opening a viewer.
-
-This guide documents the method used to trace the LilyGO T-Display-S3, M5Stack Cardputer ADV,
-DinMeter, Stamp-S3A and Cap-Bus sheets in this repository.
-
----
-
-## 1. First, decide whether the file is traceable at all
-
-Spend thirty seconds on this. It saves hours.
-
-```bash
-nix-shell -p poppler-utils --run 'pdfinfo   in.pdf'   # producer, page count, page size
-nix-shell -p poppler-utils --run 'pdfimages -list in.pdf'   # embedded rasters
-nix-shell -p poppler-utils --run 'pdftotext -layout in.pdf - | wc -w'
-```
-
-Read the three results together:
-
-| Signature | Verdict |
-|---|---|
-| `Creator: Altium Designer` / `KiCad` / `OrCAD`, **0** rows from `pdfimages -list`, thousands of words | **Vector, fully traceable.** The best case, and by far the most common for hobbyist-market vendor schematics. |
-| **1** full-page image the size of the page, `pdftotext` yields 0 words | **Raster scan. Not traceable by text.** Say so and stop. OCR is a different job with different error characteristics, and an OCR'd net name is not evidence. |
-| 0 words but 0 images either | **Vector paths with no text**, i.e. the net labels were converted to outlined glyphs. Not traceable. Rare but real. |
-| Healthy word count, but the words are all part values and no net names | Partly traceable: you can census designators and values, not connectivity. |
-
-`pdfimages -list` printing only its two header lines means **zero** embedded images. That is a
-positive signal, not a failure.
-
-> **Do not reach for `pdfimages` to "extract the component drawings".** On 14 of the 15
-> schematics traced for this guide it returned nothing at all, because there is nothing raster
-> in them to return. The drawings are vector. To get a picture out, rasterise the page yourself
-> with `pdftoppm` and crop (§7).
-
-## 2. Why `-bbox-layout` beats `-layout`
-
-`pdftotext -layout` tries to reconstruct one global column grid for the whole page. On a letter,
-A3 or tabloid schematic sheet that is hopeless: a pin number at x=157 and a net label at x=110
-belong together, but `-layout` has to reconcile them against every other object across 800
-points of page width, and the result interleaves unrelated symbols. The word count looks
-healthy and the output is unusable.
-
-```bash
-nix-shell -p poppler-utils --run 'pdftotext -bbox-layout in.pdf out.xhtml'
-```
-
-`-bbox-layout` abandons the grid and emits, for every word, its exact bounding box:
-
-```xml
-<word xMin="309.790967" yMin="533.008497" xMax="313.650077" yMax="543.319663">IBAT</word>
-```
-
-That is the whole trick. **A net label can be associated with the pin it sits beside only if you
-know where both of them are**, and `-bbox-layout` is the only poppler mode that tells you.
-
-Coordinates are PDF points (1/72 inch) with **y increasing downwards** — poppler normalises to a
-top-left origin, which is the opposite of PDF user space. Get this backwards and every
-above/below test inverts.
-
-Note also: a *rotated* word has a small x-extent and a large y-extent. Comparing `xMax-xMin`
-against `yMax-yMin` is a reliable rotation detector, and you will need it (§8).
-
-## 3. The invisible token layer — the part nobody uses
-
-Altium Designer's PDF export writes three families of helper tokens into the text layer. They
-are invisible on screen (they are drawn in the same colour as the background, or clipped), but
-`pdftotext` extracts them, and **each is placed at the exact schematic coordinate of the thing
-it names**:
-
-| Token | Meaning | Placed at |
-|---|---|---|
-| `CO<designator>` | component outline | the symbol's origin |
-| `PI<designator><pin>` | pin instance | the pin's **electrical end point** |
-| `NL<netname>` | net label | the label's anchor |
-
-So `PIU7014` is U7 pin 14, `COR13` is R13's body, `NLG8` is the net label `G8`.
-
-Two decoding rules that are not obvious and will silently corrupt a net list:
-
-1. **The designator/pin split is ambiguous without context.** `PIU7014` could be `U7` pin `14`
-   or `U701` pin `4`. Resolve it by first harvesting the real designator set from the
-   `CO<designator>` tokens, then splitting `PI` tokens against that set, longest match wins.
-   Altium zero-pads the pin number to two digits, so strip one leading `0` afterwards.
-2. **`NL` tokens substitute `0` for every non-alphanumeric character.** `NLLCD0RS` is the net
-   `LCD_RS`; `NLESP0EN` is `ESP_EN`; `NL05VIN` is `+5VIN`. If you read those literally you will
-   invent nets that do not exist. Cross-check against the *visible* text at the same coordinate,
-   which is unmangled.
-
-**Not every export carries them.** Of the 19 sheets bboxed for this guide, 9 had `NL` tokens and
-10 had none — the same vendor, the same tool, different export settings. Where `NL` is absent
-the visible net-label text is still there at the right coordinate, so the method still works;
-you just lose the ability to distinguish a net label from an ordinary annotation by token class,
-and must do it geometrically or by rendering a crop.
-
-## 4. Binding a label to a pin — and calibrating the sign of `dy`
-
-Altium anchors a net label at the lower-left of its text and floats it **just above** the wire
-it names. In poppler's top-left coordinates that means the label's y is a few points **less**
-than the wire's y.
-
-This matters more than it sounds. Pins on a symbol are typically 7 pt apart and the label floats
-~3.2–4.2 pt above its wire — so a label is *nearly equidistant* from the pin above it and the
-pin below it. Picking the nearest one gives you a net list that is plausible and off by one row.
-
-Worked example, Cardputer ADV sheet 3, the BMI270 at `U7`:
-
-```
-NLG8 at y=142.20     U7.1  (SDO) at y=138.37   -> dy = +3.83
-                     U7.14 (SDX) at y=145.37   -> dy = -3.17
-NLG9 at y=149.20     U7.14 (SDX) at y=145.37   -> dy = +3.83
-                     U7.13 (SCX) at y=152.91   -> dy = -3.71
-```
-
-Both readings are self-consistent. "Labels sit above" gives SDX=G8, SCX=G9; "labels sit below"
-gives SDO=G8, SDX=G9 and leaves SCX unlabelled.
-
-**Do not resolve this by preference — find a known answer on the same sheet and calibrate.**
-Here, pin 1 (`SDO`) turned out to carry a 3.3 kΩ resistor `R43` up to `+3.3V`, and the sheet
-prints `7-bit Address 69H` beside the symbol. A BMI270's SDO pin selects the I²C address, so
-SDO *must* be strapped, not driven by a GPIO. That settles it: labels sit **above**, and the
-correct binding is SDX=G8 (SDA), SCX=G9 (SCL). Every other net on the sheet then followed.
-
-A second, independent confirmation arrived two sheets later: the same board's TCA8418 keyboard
-controller has SDA and SCL on the same `G8`/`G9` pair, which only works under the "above"
-reading.
-
-**Always find and state your calibration case.** A strapped address pin, a crystal, a
-regulator's own output, a connector whose pinout is published elsewhere — anything whose answer
-you already know.
-
-For vertical wires the same rule rotates: the label sits just **left** of the wire, so `dx` is
-slightly negative.
-
-## 5. Multi-sheet documents and off-sheet connectors
-
-Three practical rules.
-
-**Bbox the whole document at once, not page by page.** `pdftotext -bbox-layout` emits one
-`<page>` element per sheet in a single XHTML, and you need cross-sheet lookups constantly:
-a net labelled on sheet 1 is consumed on sheet 3, and the `CO` designator set you use to split
-`PI` tokens must be harvested from *all* pages or pins on a sheet whose symbol origin fell
-elsewhere will fail to parse.
-
-**Off-sheet connectivity is by name, not by geometry.** A net that appears exactly once in the
-whole document is a red flag: either it is genuinely unterminated, or the other end is a *port*
-or *power port* symbol whose text you have classified as something else. Count occurrences of
-every net name across all pages as a sanity pass. On the Cap CC1101 sheets, `CC1101_RF_SW0`
-appears on pages 1 and 3 — that is the off-sheet link, and it is the only evidence of it.
-
-**Power ports are not net labels.** `GND`, `+3.3V`, `VBUS`, `+5VIN` are drawn as symbols with
-the text *inline with* the wire (dy ≈ 0) rather than floating above it, and on many exports they
-get no `NL` token at all. Treat them as a separate class with their own geometry, or you will
-report dozens of pins as unconnected when they are simply grounded.
-
-## 6. A worked example end to end — the LilyGO T-Display-S3 charger
-
-The question: an owner tracing a physical board reported the charger position `U6` carried a
-**5-lead TSOT-23**, while this repository's records said the schematic specified a **SOP-8
-`TP4065`**. One of the two had to be wrong, and it mattered, because the published procedure for
-changing the board's charge current derives from an 8-pin part's datasheet.
-
-```bash
-nix-shell -p poppler-utils --run '
-  pdfinfo T_Display_S3.pdf
-  pdfimages -list T_Display_S3.pdf
-  pdftotext -bbox-layout T_Display_S3.pdf tds3.xhtml'
-```
-
-`pdfinfo` reports `Creator: Altium Designer`, 1 page, 792×612 pt. `pdfimages -list` prints its
-header and nothing else — **zero raster, fully vector**. Traceable.
-
-Locate the part string, then enumerate the pin tokens for its designator:
-
-```bash
-python3 trace.py grep bbox/tds3.xhtml 'TP40'     # -> TP4065 at x=273.09 y=484.09
-python3 trace.py grep bbox/tds3.xhtml '^PIU6'
-```
-
-```
-p1 x=  264.50 y=  483.48  PIU604
-p1 x=  283.50 y=  496.46  PIU603
-p1 x=  241.50 y=  499.46  PIU601
-p1 x=  283.50 y=  503.46  PIU605
-p1 x=  264.50 y=  518.48  PIU602
-```
-
-**Five pin tokens. There is no `PIU606`, `PIU607` or `PIU608`.** The symbol is a 5-pin device.
-Reading the pin-function text at each coordinate gives 1 `CHRG`, 2 `GND`, 3 `BAT`, 4 `VCC`,
-5 `PROG` — the LTC4054/TP4054 SOT-23-5 arrangement.
-
-The same check on two further LilyGO sheets (`T-DISPLAY-S3-AMOLED.pdf` `U5`,
-`T-Display-S3-AMOLED-Touch.pdf` `U6`) returns five pins and the same five function names. Three
-independent sheets agree.
-
-Verdict: **the schematic never said SOP-8.** The owner's physical observation and the schematic
-agree, and the repository's record of the schematic was wrong. That is a finding you can reach
-in about four minutes, and could not reach at all without `-bbox-layout`.
-
-Finally, render a crop as the durable artifact (§7) so the next reader does not have to trust
-the transcription.
-
-## 7. Getting pictures out of a vector schematic
-
-`pdfimages` cannot help — there is no raster to extract. Rasterise the page and crop:
-
-```bash
-# 300 dpi => 1 PDF point = 300/72 = 4.1667 px
-nix-shell -p poppler-utils --run 'pdftoppm -f 3 -l 3 -r 300 -png in.pdf /tmp/page'
-nix-shell -p imagemagick   --run 'magick /tmp/page-3.png -crop WxH+X+Y +repage \
-                                    -bordercolor white -border 12 out.png'
-```
-
-Convert a bbox coordinate to a crop offset by multiplying by `dpi/72`. Because you already know
-the coordinates of the symbol you care about, the crop is exact rather than hunted for.
-
-Rendering is also the **tie-breaker of last resort** when the text layer is ambiguous, and it
-earned its place twice in this session:
-
-- On the Cardputer ADV, two net labels extracted as the strings `GI` and `GO`. Both `G0` and
-  `G1` exist elsewhere on the same sheet and extract correctly, so this was not a font-mapping
-  fault. A 300 dpi crop showed the module symbol's own pin names beside them — `G1` and `G2`,
-  in an unmistakable digit glyph. The net *names* really are the letters `GI`/`GO`: a vendor
-  typo. The electrical answer (Grove SCL = GPIO1, SDA = GPIO2) was only obtainable by looking.
-- On the Cap-Bus connector, two red labels sit on each wire. Only the render shows that **both**
-  are net labels — a functional alias and a host-GPIO alias on the same net — rather than one
-  label plus one annotation.
-
-## 8. Failure modes actually hit
-
-**Poppler merges independent rotated text objects that share an x-column.** On the T-Display-S3
-sheet, poppler emitted a single `<line>` reading `R13 IBAT (mA) = 580`. No such string exists.
-It is a vertical resistor designator `R13` and a separate rotated note `IBAT (mA) = 580`, drawn
-in the same narrow x-band and glued together by poppler's line grouping. Detect this by checking
-the inter-word gaps — genuine spaces within a rotated line are uniform (~1.2 pt here), and the
-merge point often is too, so gap analysis alone is *not* sufficient. Render the crop.
-
-**Greedy designator/pin splitting.** Covered in §3. `PIU7014` parsed naively as `U701` pin `4`
-produced a plausible-looking but entirely fictional symbol.
-
-**Symmetric proximity tolerance.** Covered in §4. A `±5 pt` window around a pin catches the
-label belonging to the neighbouring pin. Rank by the sign of the offset, not by distance.
-
-**`-layout` word counts as a proxy for tracing effort.** A sheet can yield 1 120 words of
-perfectly extracted text and still be unreadable as `-layout` output. Judge traceability from
-`pdfimages -list` and the producer string, not from word count.
-
-**Absence of a label is not proof of no connection** — but absence of *anything* is close to it.
-On the Cardputer ADV, BMI270 `INT1` (pin 4) and `INT2` (pin 9) have no net label. The stronger
-statement available is that a row query across the *entire* sheet at those two y coordinates
-returns **only** U7's own pin tokens: no other component pin, no label, no power port lies at
-that height anywhere on the page. Combined with the same being true of the unused OIS pins on
-the same symbol, that supports "not routed". State the query you ran, not just the conclusion.
-
-## 9. Recommended order of work
-
-1. `pdfinfo` + `pdfimages -list` + word count → traceable or not. **Record the negative result
-   if not; it stops the next agent repeating the attempt.**
-2. `pdftotext -bbox-layout` the whole document.
-3. Harvest `CO` designators; build the designator set.
-4. Split `PI` tokens against it; you now have every pin's coordinate.
-5. Harvest `NL` tokens and visible label text.
-6. **Find a calibration case with a known answer and fix the sign of `dy`.**
-7. Bind labels to pins; classify power ports separately.
-8. Census net names across all pages; investigate every net that appears exactly once.
-9. Render crops for anything ambiguous, and for anything you want a future reader to be able to
-   check without re-running any of this.
-
-## 10. Limits
-
-This recovers **labelled connectivity**. It does not recover wire geometry, so two pins joined by
-an unlabelled wire are only detectable by exact row/column alignment, and a wire with a bend is
-invisible. For full connectivity you need the source EDA files, a netlist export, or Gerbers —
-none of which these vendors publish. Where a claim rests on alignment rather than on a label,
-say so.
-
----
-
-### See also
-
-- [`scratch/schematic-tracing/`](../../scratch/schematic-tracing/README.md) — the tools
-  (`trace.py`, `render.py`, `netlist.py`) and the per-file traceability census.
diff --git a/guides/serial-access/README.md b/guides/serial-access/README.md
deleted file mode 100644
index e0f88b9..0000000
--- a/guides/serial-access/README.md
+++ /dev/null
@@ -1,288 +0,0 @@
-# Serial device access for embedded development
-
-> Getting `/dev/ttyUSB0` or `/dev/ttyACM0` to appear, be writable, and stay put
-> long enough to flash a board. Device-independent; Linux-first, with macOS and
-> Windows notes.
->
-> Written 2026-09-04. **No board was attached to a host while writing this**, so
-> commands are `reported-working` from documentation and long-standing practice,
-> not `executed-success`. The failure modes described are well-attested; the
-> exact output on your machine will differ.
-
-Related: [`guides/nixos`](../nixos/README.md) §4 covers how *this project's*
-NixOS host is configured. This guide is the general version.
-
-## The short diagnostic
-
-Three questions, in order. Most problems are answered by the first two.
-
-```bash
-lsusb                    # 1. Is the device enumerating at all?
-dmesg --follow           # 2. Which driver bound it, and to which node?
-ls -l /dev/ttyUSB* /dev/ttyACM*   # 3. What owns the node, and can you write it?
-```
-
-If `lsusb` shows nothing, it is cable or power — a startling share of "driver
-problems" are **charge-only USB cables**. If `dmesg` shows the device attaching
-and immediately detaching, jump to [ModemManager and brltty](#the-two-processes-that-steal-your-port).
-
-## Which node you get, and why it matters
-
-| Bridge chip | Kernel driver | Node | Seen on |
-|---|---|---|---|
-| WCH CH340 / CH341 | `ch341` | `/dev/ttyUSB*` | Cheap ESP32/Arduino clones |
-| WCH CH9102 / CH343 | `ch341` (newer kernels) | `/dev/ttyUSB*` | Newer M5Stack, many ESP32-S3 boards |
-| Silicon Labs CP2102 / CP2104 | `cp210x` | `/dev/ttyUSB*` | ESP32 devkits, many vendor boards |
-| FTDI FT232R / FT2232 | `ftdi_sio` | `/dev/ttyUSB*` | Older/professional boards, JTAG adapters |
-| **Native USB (no bridge)** | `cdc_acm` | **`/dev/ttyACM*`** | ESP32-S3, ESP32-C3, ESP32-S2, RP2040 |
-
-**The `ttyUSB` vs `ttyACM` split is the single most useful thing to internalise.**
-A board with a USB-serial bridge chip appears as `ttyUSB*`; a board whose MCU
-implements USB itself appears as `ttyACM*`. They behave differently:
-
-- **`ttyUSB*` (bridge)** — the bridge stays enumerated regardless of what the MCU
-  does. Reset the MCU and the port persists. DTR/RTS drive the auto-reset circuit.
-- **`ttyACM*` (native USB)** — the USB device *is* the MCU. **Reset it and the
-  port vanishes and re-enumerates**, often with a different number. This is
-  normal, not a fault, and it is why `esptool` sometimes reports the port
-  disappearing mid-operation on an ESP32-S3.
-
-Some boards, including several documented in this knowledge base, expose **both**:
-a bridge for the UART console and native USB for JTAG/CDC. You may see
-`ttyUSB0` and `ttyACM0` from one cable.
-
-## Permissions — and the Arch trap
-
-The node exists but you get `Permission denied`. Check ownership:
-
-```bash
-ls -l /dev/ttyUSB0
-# crw-rw---- 1 root dialout 188, 0 ...   <- Debian/Ubuntu/Fedora
-# crw-rw---- 1 root uucp    188, 0 ...   <- Arch
-```
-
-**The group differs by distribution, and this is the most common wasted hour:**
-
-| Distribution | Group |
-|---|---|
-| Debian, Ubuntu, Linux Mint, Raspberry Pi OS | `dialout` |
-| Fedora, RHEL | `dialout` |
-| **Arch, Manjaro, EndeavourOS** | **`uucp`** |
-| openSUSE | `dialout` |
-
-Every "add yourself to `dialout`" tutorial is wrong on Arch. Add yourself to the
-group that actually owns the node:
-
-```bash
-sudo usermod -aG uucp "$USER"     # Arch
-sudo usermod -aG dialout "$USER"  # most others
-```
-
-**Then log out and back in.** Group membership is established at login;
-`newgrp uucp` works in the current shell as a stopgap. `id` should list the group
-before you retry.
-
-Arch additionally has a `lock` group used by some tools for `/var/lock`
-serial lockfiles; add it if a tool complains about lockfiles specifically.
-
-### The `chmod 666` shortcut
-
-`sudo chmod 666 /dev/ttyUSB0` works and is reset on every replug. It is fine for
-a one-off. It is not a fix, and on a shared machine it grants every user access
-to the port.
-
-## udev rules
-
-Group membership is enough for most boards. Write a rule when you want a
-**stable name**, non-standard permissions, or to exempt a device from an
-interfering service.
-
-`/etc/udev/rules.d/99-embedded.rules`:
-
-```
-# CH340
-SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"
-# CH9102 / CH343
-SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="55d4", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"
-# CP210x
-SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"
-# FTDI
-SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"
-# Espressif native USB (ESP32-S2/S3/C3 USB-JTAG/serial)
-SUBSYSTEM=="tty", ATTRS{idVendor}=="303a", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"
-```
-
-Reload without rebooting:
-
-```bash
-sudo udevadm control --reload-rules && sudo udevadm trigger
-```
-
-Confirm the vendor/product IDs for *your* board rather than trusting the table —
-`lsusb` gives them as `ID vvvv:pppp`.
-
-### Stable names for multi-board setups
-
-If you have several boards attached, `ttyUSB0` is whichever enumerated first.
-Pin a symlink by serial number:
-
-```
-SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{serial}=="0001", SYMLINK+="esp32-devkit"
-```
-
-Then use `/dev/esp32-devkit`. Devices whose bridge has no unique serial (many
-CH340s ship with an identical or absent serial) cannot be distinguished this way
-— pin them by physical USB port path (`KERNELS=="1-1.2"`) instead.
-
-## The two processes that steal your port
-
-Both present as "the port appears then disappears", or "flashing fails only in
-the first few seconds after plugging in".
-
-### ModemManager
-
-ModemManager probes new serial devices to see whether they are cellular modems,
-sending AT commands for several seconds. On a freshly plugged board this collides
-with `esptool` and looks like a flaky bridge.
-
-- **Per-device fix (preferred):** `ENV{ID_MM_DEVICE_IGNORE}="1"` in a udev rule,
-  as above.
-- **Blunt fix:** `sudo systemctl disable --now ModemManager` — fine on a
-  development machine with no cellular modem.
-
-### brltty
-
-`brltty`, the braille display daemon, claims **CH341 devices** because some braille
-displays use the same USB IDs. It grabs the device and the tty node never
-appears. This is a long-standing, widely reported issue on Ubuntu and Arch, and
-it is baffling if you do not know about it — the symptom is a device that
-enumerates in `lsusb` but produces no `/dev/ttyUSB*`.
-
-```bash
-sudo systemctl stop brltty-udev.service
-sudo systemctl mask brltty-udev.service
-# or, if you do not use a braille display at all:
-sudo apt remove brltty     # Debian/Ubuntu
-sudo pacman -Rns brltty    # Arch
-```
-
-If `dmesg` shows `ch341-uart converter now attached to ttyUSB0` immediately
-followed by a detach, this is almost certainly the cause.
-
-## NixOS
-
-NixOS ignores `/etc/udev/rules.d` edits across rebuilds — configure declaratively.
-
-```nix
-{
-  # Ship vendor udev rules from packages
-  services.udev.packages = with pkgs; [
-    platformio-core.udev   # covers most ESP32/Arduino bridges
-    openocd
-  ];
-
-  # Or write rules inline
-  services.udev.extraRules = ''
-    SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"
-    SUBSYSTEM=="tty", ATTRS{idVendor}=="303a", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"
-  '';
-
-  users.users.<you>.extraGroups = [ "dialout" "plugdev" ];
-}
-```
-
-Two NixOS-specific gotchas:
-
-- **`plugdev` does not exist by default.** Rules referencing it are silently inert
-  until you create the group. This project's host creates it explicitly — see
-  [`guides/nixos`](../nixos/README.md) §4.
-- `platformio-core.udev` is a separate output; `pkgs.platformio` alone does not
-  install the rules.
-
-Apply with `sudo nixos-rebuild switch`, then replug.
-
-## macOS
-
-Native USB CDC (`ttyACM`-class) devices need **no driver** — they appear as
-`/dev/cu.usbmodem*`.
-
-Bridges vary:
-
-- **CP210x, FTDI** — drivers have shipped in macOS since 10.11ish; usually
-  `/dev/cu.usbserial-*` with no install.
-- **CH340/CH341** — historically needed WCH's kext, and on Apple Silicon the
-  situation has changed across releases. Modern macOS generally enumerates them,
-  but a vendor driver is still sometimes required.
-
-**Use `/dev/cu.*`, not `/dev/tty.*`.** Both appear for the same device. The
-`tty.*` node blocks on carrier detect (DCD) and will hang; `cu.*` ("call-up")
-does not. This trips up almost everyone once.
-
-```bash
-ls /dev/cu.*
-```
-
-## Windows
-
-- **Native USB CDC** — enumerates as a COM port with no driver on Windows 10/11.
-- **CP210x, FTDI** — Windows Update usually supplies drivers; vendor installers
-  exist if not.
-- **CH340** — very often needs WCH's driver installed manually. Counterfeit
-  FTDI chips have historically been bricked by official FTDI drivers; genuine
-  parts are unaffected.
-
-Find the port in Device Manager under **Ports (COM & LPT)**; use `COM3`-style
-names. Nothing analogous to the permissions problem exists — if the port is
-listed, you can open it, though **only one application at a time**. A serial
-monitor left open in an IDE is the usual cause of "access denied" on Windows.
-
-## ESP32-specific behaviour
-
-Relevant to most boards in this knowledge base.
-
-**Auto-reset.** Bridges wire DTR and RTS to `EN` and `GPIO0` so the flasher can
-reset the chip into download mode. Boards without that circuit need a manual
-button sequence — typically hold BOOT, tap RESET, release BOOT.
-
-**Native USB and disappearing ports.** On ESP32-S3/C3 the CDC device is the MCU.
-Flashing resets it, so the port disappears and returns. `esptool` handles this,
-but a serial monitor holding the old node will fail. Close monitors before
-flashing.
-
-**Some boards have a firmware-controlled port.** Where the USB peripheral is
-implemented by application firmware rather than a bridge, **flashing broken
-firmware removes the port**, and recovery needs the hardware download-mode
-sequence. Boards whose reset and boot straps are driven by a separate
-power-management MCU — the
-[M5Stack PaperMono](../../devices/m5stack/papermono/README.md) is one — put that
-sequence under that MCU's control rather than a physical button.
-
-**Verify before blaming permissions:**
-
-```bash
-esptool.py --port /dev/ttyUSB0 chip_id
-```
-
-A successful chip ID means enumeration, driver, permissions and the reset circuit
-are all working, and any remaining problem is in the build or the flash command.
-
-## Failure-mode summary
-
-| Symptom | Most likely cause |
-|---|---|
-| Nothing in `lsusb` | Charge-only cable, dead port, unpowered board |
-| In `lsusb`, no `/dev/tty*` | **brltty** (CH341), or no driver for the bridge |
-| Node appears then vanishes | **ModemManager** probing, or native-USB reset (normal) |
-| `Permission denied` | Wrong group — **`uucp` on Arch**, `dialout` elsewhere; or not re-logged-in |
-| `Device or resource busy` | A serial monitor or another flasher holds the port |
-| Port number changes each replug | No stable symlink — pin by serial or USB path |
-| Works as root only | Group membership not applied to the current session |
-| Flash starts then fails partway | Auto-reset circuit, cable quality, or an underpowered board |
-
-## Evidence boundary
-
-Nothing here was executed against attached hardware in this pass. The USB IDs,
-group names and driver names are stable, long-documented facts, but **confirm the
-IDs for your own board with `lsusb`** rather than copying the table. The NixOS
-snippets follow the same structure as this project's working host configuration
-([`guides/nixos`](../nixos/README.md)) but were not rebuilt to verify.
diff --git a/renovate.json b/renovate.json
new file mode 100644
index 0000000..5db72dd
--- /dev/null
+++ b/renovate.json
@@ -0,0 +1,6 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": [
+    "config:recommended"
+  ]
+}
diff --git a/research/preprint-repositories/README.md b/research/preprint-repositories/README.md
deleted file mode 100644
index 173cf95..0000000
--- a/research/preprint-repositories/README.md
+++ /dev/null
@@ -1,294 +0,0 @@
-# Preprint repositories — a source-traceable survey
-
-A record of every repository listed on Wikipedia's [List of preprint repositories][wp], written for
-engineers rather than for librarians. The question this pass answers is not "what preprint servers
-exist" but:
-
-> **If I find a paper on this server, how much should I believe it, and will the link still work in
-> five years?**
-
-- **Compiled:** 2026-09-01 / 2026-09-02. Every figure below was measured on those dates.
-- **Scope:** the 65 entries on the Wikipedia list, plus a handful of successors and spin-offs
-  discovered while probing (openRxiv, Open Research Africa, VeriXiv, Law Archive, Open Research
-  Europe).
-- **Bias, stated up front:** this knowledge base is about **hardware, firmware, software and
-  systems**. Repositories that carry such work are documented in depth and individually.
-  Repositories that carry none are grouped and documented compactly. That is a deliberate
-  allocation of effort, not a judgement of their scholarly worth.
-
-[wp]: https://en.wikipedia.org/wiki/List_of_preprint_repositories
-
----
-
-## Evidence and method
-
-Every record in this directory uses the same labels. They are load-bearing — a claim without one
-has not been checked.
-
-| Label | Means |
-|---|---|
-| **[API]** | A machine-readable API response actually retrieved on the stated date. Strongest evidence here. |
-| **[WEB]** | A live web page actually loaded. |
-| **[DOC]** | The operator's own published policy, About or FAQ document. |
-| **[LIT]** | Scholarly literature *about* the repository. |
-| **[COM]** | Press, blog or community report. |
-| **[INF]** | Our inference from the above, marked as inference. |
-| **[NOT-VERIFIED]** | Could not confirm. The record says what was tried and why it failed. |
-
-Five rules were applied throughout, and they are why this survey disagrees with its own source
-material in a dozen places:
-
-1. **An unsourced number is worse than no number.** Where a count could not be obtained, the record
-   says `not verified` and describes the attempt. No figure in this directory was written from
-   memory.
-2. **Prefer machine-readable primary evidence.** Counts come from the operator's own API
-   (`api.osf.io`, `api.crossref.org`, `api.biorxiv.org`, `api.archives-ouvertes.fr`,
-   `export.arxiv.org`, `zenodo.org/api`, OAI-PMH) rather than from prose. Several findings below
-   exist *only* because an API was harvested instead of a page being read.
-3. **HTTP 200 does not mean the document exists.** Every probe was paired with a **negative
-   control** — a deliberately bogus path. This caught real traps; see [§ Probing traps](#6-probing-traps).
-4. **Record conflicts rather than resolving them by preference.** Where Wikipedia, the operator and
-   the API disagree, all three are reported with dates. Six such conflicts are listed in
-   [§ Where this survey contradicts its source](#5-where-this-survey-contradicts-its-source).
-5. **Landmark papers must resolve.** Every identifier in
-   [`landmark-papers.md`](landmark-papers.md) was individually fetched and its title machine-checked
-   against the response. Papers that could not be confirmed were dropped, not softened.
-
-**Verification.** This corpus was re-probed on **2026-09-11**; five findings required correction
-and one dating error was found. See **[`VERIFICATION.md`](VERIFICATION.md)**.
-
-Cross-cutting companion documents:
-
-- **[`landmark-papers.md`](landmark-papers.md)** — the verified papers in software, distributed
-  systems, databases, electronics and security, and which server they landed on.
-- **[`reliability-and-durability.md`](reliability-and-durability.md)** — how much to trust each
-  server, and how long its links last.
-- **[`VERIFICATION.md`](VERIFICATION.md)** — the 2026-09-11 re-probe: what drifted, what was corrected.
-- **[`retrieval-notes.md`](retrieval-notes.md)** — bot-blocking, user-agent and API findings from
-  this pass, staged for merging into the repository's
-  [crawler access table](../../ai-crawler-site-access-table.md).
-
----
-
-## Start here
-
-| If you want to… | Read |
-|---|---|
-| **Get the PDF of any paper, legally** | **[`open-access-full-text-sources.md`](open-access-full-text-sources.md)** — the ordered lookup ladder |
-| Find MapReduce, GFS, Raft, Spark, ZooKeeper | **USENIX and the ACM DL** — they are on no preprint server ([why](landmark-papers.md#1-the-single-most-important-finding)) |
-| Find the RISC-V specifications | [Berkeley EECS technical reports](government-and-institutional-technical-reports.md) — **not** arXiv, and **currently only via Wayback** |
-| **Get the long version of a paper — schematics, bring-up, negative results** | **[`theses-and-dissertations.md`](theses-and-dissertations.md)** |
-| Find a UK doctoral thesis | [EThOS is metadata-only since the 2023 cyberattack](theses-and-dissertations.md) — go to the university repository |
-| Read the *reviews* of an ICLR/NeurIPS paper | [OpenReview](additional-preprint-servers.md) |
-| Find complexity-theory results | [ECCC](additional-preprint-servers.md) — absent from Wikipedia's list |
-| Find the preprint of a paywalled IEEE paper | [TechRxiv § the Crossref route](techrxiv.md) |
-| Understand what an arXiv ID actually guarantees | [arXiv §5](arxiv.md) |
-| Find embedded/side-channel security work before it hits a conference | [Cryptology ePrint §7.6](cryptology-eprint-archive.md) |
-| Make your own code or firmware citable | [Zenodo § GitHub integration](zenodo.md) |
-| Find the CRDT papers, CompCert, or Coq's original manuals | [HAL §7](hal.md) |
-| Recover a dead vendor doc portal or datasheet host | [`recovering-dead-technical-sites.md`](recovering-dead-technical-sites.md) |
-| Find spacecraft, radiation-hardening or national-lab electronics work | [NTRS and OSTI](government-and-institutional-technical-reports.md) |
-| Know whether a small server's links will survive | [`closed-and-defunct-servers.md`](closed-and-defunct-servers.md) |
-| Judge a paper from a server you have never heard of | [`reliability-and-durability.md`](reliability-and-durability.md) |
-| Understand why a host is 403-ing you | [`retrieval-notes.md`](retrieval-notes.md) |
-| Find battery, MEMS or semiconductor-process work | [ECSarXiv](ecsarxiv.md) · [ChemRxiv](chemrxiv.md) |
-
----
-
-## 1. The technically relevant servers
-
-These carry electronics, hardware, software, distributed-systems or database work. Each has its own
-record.
-
-| Server | Operator | Since | Measured size | Technical relevance |
-|---|---|---|---|---|
-| **[arXiv](arxiv.md)** | independent non-profit (ex-Cornell) | 1991 | **3,152,666** submissions; `cs` alone **931,100** [API] | **The** venue for CS/EE. 40 `cs.*` + 4 `eess.*` categories |
-| **[Cryptology ePrint](cryptology-eprint-archive.md)** | IACR | 1999 | **27,552** reports [API] | Dominant for crypto; **primary** for side-channel and embedded security |
-| **[HAL](hal.md)** | CCSD / CNRS | 2002 | 2,827,378 notices + **1,788,688 with files** [API] | INRIA/CEA/LIRMM: CRDTs, CompCert, Coq, Frama-C, robotics |
-| **[Zenodo](zenodo.md)** | CERN + OpenAIRE | 2013 | **7,231,589** records; **284,518** software concepts [API] | How research code, firmware and datasets become citable |
-| **[TechRxiv](techrxiv.md)** | IEEE | 2019 | **18,890** items [API] | The open copy of IEEE-bound work |
-| **[Optimization Online](optimization-online.md)** | Math. Optimization Society | 2000 | **9,843** eprints [API] | Solvers, MILP, scheduling — IPOPT, JuMP, SCIP |
-| **[engrXiv](engrxiv.md)** | Open Engineering Inc | 2016 | **5,871** records [API] | Broad engineering; mostly civil/mechanical |
-| **[ECSarXiv](ecsarxiv.md)** | Electrochemical Society | 2018 | **323** preprints [API] | Batteries, MEMS, gas sensors, semiconductor process |
-| **[ChemRxiv](chemrxiv.md)** | ACS-led consortium | 2017 | **53,678** preprints [API] | Battery/electrolyte chemistry, semiconductor materials |
-| **[figshare](figshare.md)** | Digital Science / Springer Nature | 2011 | **4,106,613** DOIs (figshare.com) [API] | Generalist; **infrastructure** under other servers |
-| **[BioHackrXiv](biohackrxiv.md)** | OSF / DBCLS / ELIXIR | 2020 | **163** unique works [API] | Workflow engines, FAIR tooling, hackathon software reports |
-| **[ChinaXiv](chinaxiv.md)** | CAS National Science Library | 2016 | **47,362** native (CS 2,052) [API] | Chinese-language CS; small but real |
-| **[SSRN](ssrn.md)** | Elsevier | 1994 | ~1.5 M papers; CS network 108,252 [WEB] | Thin for CS; authoritative for law/econ |
-
-### Marginal or misrepresented
-
-| Server | Verdict |
-|---|---|
-| **[Synthical](synthical.md)** | **Not a repository.** An AI reader over arXiv/bioRxiv/medRxiv/ChemRxiv. Registered with neither Crossref nor DataCite — mints nothing. Unreachable on 2026-09-01 |
-| **[ScienceOpen](scienceopen.md)** | **A discovery layer.** Hosts ~3,584 preprints, *indexes* ~100 M. Wikipedia's ">1,000,000" is wrong as a hosting figure by ~2 orders of magnitude |
-| **[Authorea](authorea.md)** | A writing tool that became a preprint host, then a Wiley asset. **Direct submissions suspended May 2026** |
-| **[Qeios](qeios.md)** | 95% of its DOIs are wiki-style definitions and reviews. **The computing corpus is 63 papers** |
-| **[Preprints.org](preprints-org.md)** | Real screening, real DOIs, 137,380 preprints — but operated by MDPI, and 230 of its 232 "friendly journals" are MDPI titles |
-| **[Research Square](research-square.md)** | The largest preprint server on earth (468,390) because Springer Nature auto-posts submissions. **On rejection the journal branding is stripped and the preprint stays** |
-| **[viXra](vixra.md)** | 46,051 e-prints, **zero** endorsement or review. Computing categories total 2,740. **Do not cite as evidence for anything** |
-| **[OSF Preprints](osf-preprints.md)** | Infrastructure under 32 branded servers, **14 open / 18 closed**. Wikipedia's ">1,000,000" was federated *metadata*, never hosted content |
-
----
-
-## 2. Grouped records
-
-Servers with little or no hardware/software content, documented compactly.
-
-| Record | Covers |
-|---|---|
-| [`biorxiv-and-medrxiv.md`](biorxiv-and-medrxiv.md) | bioRxiv (**347,954**) and medRxiv (**88,194**) — deep, because `Bioinformatics` is **30,363** preprints of scientific software |
-| [`life-science-and-medical-platforms.md`](life-science-and-medical-platforms.md) | F1000Research and its five funder clones, PeerJ Preprints, Lancet, Cell Sneak Peek, Nature Precedings, JMIR, ARPHA, Beilstein, agriRxiv |
-| [`regional-and-national-servers.md`](regional-and-national-servers.md) | Jxiv, SciELO Preprints, AfricArXiv, Arabixiv, IndiaRxiv, INArxiv, LatArXiv, Preprints.ru, AIJR |
-| [`repec-and-econstor.md`](repec-and-econstor.md) | RePEc (a federation, **not** a repository) and EconStor |
-| [`library-science-and-cognitive-archives.md`](library-science-and-cognitive-archives.md) | CogPrints, E-LIS, LISSA |
-| [`social-sciences-and-humanities.md`](social-sciences-and-humanities.md) | SocArXiv, PsyArXiv, EdArXiv, APSA, LawArXiv, CrimRxiv, MediArXiv, BodoArXiv, hprints, MetaArXiv, MindRxiv, PhilArchive, PhilSci-Archive, LingBuzz, Rutgers Optimality Archive |
-| [`natural-sciences-and-niche-servers.md`](natural-sciences-and-niche-servers.md) | EarthArXiv, ESSOAr, EcoEvoRxiv, PaleorXiv, MarXiv, NutriXiv, SportRxiv, FocUS, Eyexiv, mp_arc, Frenxiv, WikiJournal Preprints |
-| [`closed-and-defunct-servers.md`](closed-and-defunct-servers.md) | Every server that closed, froze, or lost its front door — and whether the content survived |
-
----
-
-## 3. Beyond preprints — where the rest of the literature lives
-
-A preprint server is only one of several places a technical paper can legitimately be free. These
-records were added because the first round made it obvious that **the literature this knowledge base
-actually depends on is mostly not on any preprint server at all.**
-
-| Record | Covers | Why it matters here |
-|---|---|---|
-| **[`additional-preprint-servers.md`](additional-preprint-servers.md)** | **ECCC** (4,832 reports since 1994) · **OpenReview** (4,634 venues) · **ACL Anthology** (131,040 entries) · **INSPIRE-HEP** (1,882,844) · **CERN Document Server** (578,928) · SciPost · Open Research Europe · PCI · VeriXiv · Cambridge Open Engage · **dblp** (8,748,412) | Wikipedia's list **omits the two most important computing servers**: ECCC is the theoretical-CS analogue of Cryptology ePrint, and OpenReview publishes ICLR/NeurIPS **reviews and rebuttals**, not just papers |
-| **[`open-access-full-text-sources.md`](open-access-full-text-sources.md)** | Unpaywall · OpenAlex · Semantic Scholar/S2ORC · CORE · BASE · OpenAIRE · DOAJ · dblp · **USENIX** · ACM OPEN · PMC/Europe PMC · HathiTrust · CiteSeerX | **USENIX made every proceedings paper free in 2008.** Given that MapReduce, GFS, Raft, Spark and ZooKeeper are on no preprint server, USENIX *is* the answer for much of the systems literature |
-| **[`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md)** | **NASA NTRS** (646,950 records, 358,213 with documents) · **OSTI/DOE PAGES** · DTIC · NIST · **Berkeley EECS** · Cambridge Computer Lab · MIT · **DEC SRC/WRL/CRL** · IETF RFCs | Grey literature is where real electronics engineering lives. **The RISC-V ISA specifications are Berkeley technical reports** — verified here, closing a gap `arxiv.md` had flagged |
-| **[`theses-and-dissertations.md`](theses-and-dissertations.md)** | NDLTD · OATD · DART-Europe · **EThOS** · theses.fr/TEL · Shodhganga · DiVA · MIT DSpace · Caltech THESIS · **ETH Research Collection** · Cambridge · ProQuest · **26 verified landmark theses** | **A thesis is often the only complete writeup of a hardware design that exists.** The paper is 8 pages; the dissertation behind it is 150–300, with the schematics, bring-up, measurement setup and negative results the paper had to cut |
-
-**The RISC-V result is the clearest vindication of the whole exercise.** `arxiv.md` recorded that no
-canonical RISC-V paper is on arXiv and marked it unresolved. It is resolved now — six Berkeley EECS
-technical reports, verified with magic-byte-checked PDFs:
-
-| Report | Title | Date |
-|---|---|---|
-| **UCB/EECS-2011-62** | The RISC-V Instruction Set Manual, Volume I: Base User-Level ISA | 2011-05-13 |
-| **UCB/EECS-2011-63** | Improving Energy Efficiency and Reducing Code Size with RISC-V Compressed | 2011-05-13 |
-| **UCB/EECS-2014-54** | …Volume I: User-Level ISA, Version 2.0 | 2014-05-06 |
-| **UCB/EECS-2016-1** | Design of the RISC-V Instruction Set Architecture (Waterman PhD) | 2016-01-03 |
-| **UCB/EECS-2016-118** | …Volume I: User-Level ISA, Version 2.1 | 2016-05-31 |
-| **UCB/EECS-2016-161** | …Volume II: Privileged Architecture Version 1.9.1 | 2016-11-04 |
-
-> ⚠ **Berkeley took these offline mid-survey, then restored them at a new path.**
-> During the original pass (2026-09-04) `www2.eecs.berkeley.edu/Pubs/TechRpts/*` 302-redirected to
-> `iris.eecs.berkeley.edu`, which served a 58,829-byte themed 404 for every path including the
-> series index. **On re-probe 2026-09-11 the series is back on its original host**, at a new
-> `/Archive/` path segment:
->
-> `https://www2.eecs.berkeley.edu/Pubs/TechRpts/<year>/Archive/<report>.pdf`
->
-> All six re-verified HTTP 200 with `%PDF-` magic; `EECS-2016-1` is **959,927 bytes**, exactly
-> matching both the pre-outage size and the Wayback capture. Wayback also holds all six
-> independently (`2016-1` → `20260409151000`).
->
-> For roughly three weeks the canonical RISC-V specifications were unreachable at every published
-> URL. The corrected reading is the one this survey reaches everywhere else: **the URLs moved, the
-> content was never lost.** See [`VERIFICATION.md §1.1`](VERIFICATION.md#11--berkeley-eecs-is-restored-the-went-dark-finding-was-a-migration-transient).
-
----
-
-## 4. Recovery, bulk archives and copyright
-
-| Record | Covers |
-|---|---|
-| **[`recovering-dead-technical-sites.md`](recovering-dead-technical-sites.md)** | Wayback + the CDX API + `save/` · archive.org collection APIs · **bitsavers** · Software Heritage · archive.today Memento · datasheet archives · a decision tree for "the page is gone" |
-| **[`bulk-libraries-and-shadow-archives.md`](bulk-libraries-and-shadow-archives.md)** | Sci-Hub · Library Genesis · Anna's Archive · Z-Library · lawful curated collections · the metadata-vs-full-text distinction |
-
-Two things to know before opening either.
-
-**Dead technical sites usually are recoverable.** The DEC SRC/WRL/CRL research-report series —
-521 reports across six series — survives **only** because someone mirrored it to bitsavers in 2007.
-`hpl.hp.com` still resolves in DNS but its TCP port is dead. The mirror is the archive.
-
-**On shadow libraries, this survey's position is explicit.** They are documented factually — history,
-scale, legal status, reliability — and they are documented **last**, after the lawful ladder, because
-for technical literature the lawful copy nearly always exists. **No mirror domains, proxy hosts or
-access workarounds are recorded anywhere in this directory**: they rotate faster than any document can
-track, and they are the circumvention part rather than the reference part. Sci-Hub in particular has
-been **frozen since roughly December 2020 – 2021** and is not a route to current research regardless.
-
-The reliability rule matters more than the legal one for our purposes: **a PDF from an unprovenanced
-bulk library cannot be verified as the version of record, the correct edition, or unaltered.** Under
-[§ Evidence and method](#evidence-and-method) such a file cannot carry an evidence label at all — the
-strongest honest label is `[NOT-VERIFIED]`. Resolve the DOI and confirm the record against Crossref,
-DataCite or dblp before relying on anything.
-
----
-
-## 5. Where this survey contradicts its source
-
-Wikipedia's list was the starting point, not the evidence. Six of its claims did not survive
-measurement. In each case both readings are recorded in the relevant file.
-
-| Wikipedia says | Measurement says | Record |
-|---|---|---|
-| OSF Preprints `>1,000,000` | **200,519** hosted across 32 providers. The million was SHARE-federated metadata harvested from six *external* sources | [osf-preprints.md](osf-preprints.md) |
-| ScienceOpen `>1,000,000` | **~3,584** hosted preprints; 7,620 DOIs across all prefixes. The rest is an index | [scienceopen.md](scienceopen.md) |
-| Synthical `>1,000,000`, "preprint repository" | Hosts **nothing**; zero Crossref and zero DataCite registrations. It is a reader over other servers | [synthical.md](synthical.md) |
-| Zenodo created **2011** | Operator's own About page and BibTeX say **May 2013**; Wikipedia's *own Zenodo article* says 2013. The 2011 date probably belongs to a predecessor whose launch we could not confirm | [zenodo.md](zenodo.md) |
-| HAL created **2001** | CCSD attributes 2001 to **TEL**, not HAL. HAL's OAI `earliestDatestamp` is **2002-09-23** | [hal.md](hal.md) |
-| RePEc provider = "Federal Reserve Bank of St. Louis" | RePEc "has no central expenses" and no operator. Zimmermann runs *IDEAS* and is an AVP there — a half-truth | [repec-and-econstor.md](repec-and-econstor.md) |
-
-Two more, smaller: mp_arc is listed as `>10,000` but its own index yields **6,152** (both recorded,
-unresolved); Cell Sneak Peek and Preprints with The Lancet are listed at `>1,000` each but measure
-**12,404** and **25,550**.
-
----
-
-## 6. Probing traps
-
-Findings that will corrupt anyone else's harvest of these servers. All were hit during this pass.
-
-- **`osf.io` returns HTTP 200 and an identical 4,207-byte SPA shell for providers that do not
-  exist.** Status code *and* byte size are both uninformative. Use
-  `api.osf.io/v2/preprints/?filter[provider]=<slug>` and read `meta.total`. This affects every
-  OSF-hosted server on the list.
-- **The arXiv API's `max_results=0` is broken** — it returns HTTP 200 with `totalResults=1` and a
-  fake entry titled "Error". A harvester using it records **1 for every category**. Use
-  `max_results=1`.
-- **HAL's subject field is `domainAllCode_s`, not `domain_s`.** The wrong field returns a confident,
-  silent `numFound: 0` — the most likely route to a fabricated HAL statistic.
-- **Zenodo's API returns HTTP 200 with `total: 0` for invalid facet values**, indistinguishable
-  from a genuine zero. Separately, unquoted `RISC-V` returns 422,778 hits against 495 quoted — an
-  ~850× inflation from hyphen tokenisation.
-- **SSRN networks must never be summed.** The 68 networks total 4,569,102 against ~1.5 M actual
-  papers: ≈3.0 cross-listings each.
-- **ChinaXiv returns the same 403 for bogus and real IDs** under `/abs/`, so status codes cannot
-  test existence there. A bogus `.htm` path does give a true 404.
-- **Zenodo, OSF and TechRxiv all count *versions*, not works.** Measured inflation ranged from
-  +1.6% to +50% depending on provider; TechRxiv is 30,954 DOI records for 18,890 items.
-- **`doi.org` is a usable existence oracle behind a bot wall**: it returns 404 for unregistered DOIs
-  but passes through the target's 403 for registered ones. A 403 therefore *confirms* existence.
-  **`hdl.handle.net/api/handles/<prefix>/<suffix>` is better still** — it returns JSON
-  (`responseCode: 1` vs `100`) from the Handle System rather than the target host, so it works
-  straight through Cloudflare and Anubis.
-- **`archive.org/wayback/available` returns false negatives.** It reported `archived_snapshots: {}`
-  for a URL the CDX API shows continuously archived since 2018. **Confirm absence with CDX**, never
-  with `wayback/available` alone — this one fails *toward* phantom link rot.
-- **The CDX `length` field is the WARC record length, not the payload size.** Compare the `digest`
-  (base32 SHA-1 of the payload) against a local copy instead.
-
----
-
-## 7. What this pass did not do
-
-Stated so the gaps are visible rather than silent.
-
-- **Nothing here was peer-reviewed, benchmarked or reproduced by us.** This survey documents
-  repositories, not the correctness of their contents.
-- **No eventual-publication rate was obtained for most servers.** Only bioRxiv/medRxiv publish the
-  data (69–78% for mature cohorts), and we derived one for Cryptology ePrint by sampling
-  (61.7%, n=60, 95% CI 49.0–72.9%). For arXiv, OSF, SSRN, TechRxiv, engrXiv and ECSarXiv it is
-  **[NOT-VERIFIED]** — no citable measurement was found.
-- **Eyexiv could not be located at all.** Four TLDs are NXDOMAIN and it is not an OSF provider. It
-  is the only entry on the Wikipedia list this pass considers genuinely lost.
-- **Moderation rejection rates are unpublished nearly everywhere.** arXiv, ePrint, TechRxiv and
-  ChinaXiv all decline to state them. engrXiv is the striking exception — it disclosed that roughly
-  **half of 2025 submissions were declined** as AI-generated.
-- **No artifact was archived into `archive/`.** This pass produced records, not retained binaries.
-  Raw probe output is under [`../../scratch/preprint-repositories/`](../../scratch/preprint-repositories/).
diff --git a/research/preprint-repositories/VERIFICATION.md b/research/preprint-repositories/VERIFICATION.md
deleted file mode 100644
index f474541..0000000
--- a/research/preprint-repositories/VERIFICATION.md
+++ /dev/null
@@ -1,230 +0,0 @@
-# Verification report — preprint and scholarly-literature repositories
-
-Research pass **2026-09-01 → 2026-09-07**. Verification re-probe **2026-09-11**.
-All figures below were re-measured on 2026-09-11 against the values recorded in the corpus.
-
-> **Purpose.** This corpus is entirely built on dated, sourced observations of live hosts. Several
-> of those hosts are volatile — three changed state *during* the original pass. This report
-> re-probes everything volatile, records drift, and **corrects the record where the original
-> finding no longer holds.**
-
-## Inventory
-
-| Metric | Value |
-|---|---|
-| Records in `research/preprint-repositories/` | **40** Markdown documents |
-| Total lines | **~22,900** |
-| Wikipedia-list entries covered | **78 / 78** (verified by name search) |
-| Landmark identifiers individually verified | **160** (79 arXiv · 41 ePrint · 26 theses · 14 HAL) |
-| Broken relative links | **0** |
-| Broken heading anchors | **0** |
-| `[NOT-VERIFIED]` flags | **221** — each naming what was tried |
-| Files staged in git index by this pass | **0** |
-| Raw probe evidence retained | **234 MB** in `scratch/preprint-repositories/` |
-
-## Automated checks
-
-| Check | Result |
-|---|---|
-| Broken relative Markdown links | ✅ **0** |
-| Broken heading anchors (GitHub slug rules) | ✅ **0** |
-| Wikipedia-list coverage (78 names) | ✅ **0 missing** |
-| Landmark PDF magic bytes (Berkeley set) | ✅ 6/6 `%PDF-` |
-| Torvalds thesis digest vs Wayback | ✅ **identical** (`ZVCIUY5JU6PJW3CN37K277F2Z4HLXYPV`) |
-| Staged deletions/additions from this pass | ✅ **0** (unrelated concurrent Nix work is staged; left untouched) |
-
----
-
-## 1. Corrections — findings that no longer hold
-
-### 1.1 ⚠ Berkeley EECS is **restored**. The "went dark" finding was a migration transient.
-
-**This was a headline claim and it is now wrong.** The original pass found
-`www2.eecs.berkeley.edu/Pubs/TechRpts/*` 302-redirecting to `iris.eecs.berkeley.edu`, which served
-a themed 404 for every path.
-
-On 2026-09-11 the series is **back on its original host, at a new `/Archive/` path segment**:
-
-```
-https://www2.eecs.berkeley.edu/Pubs/TechRpts/<year>/Archive/<report>.pdf
-```
-
-All six RISC-V reports re-verified, HTTP 200, `%PDF-` magic:
-
-| Report | Bytes | Note |
-|---|---|---|
-| UCB/EECS-2011-62 | 376,630 | matches the size recorded pre-outage |
-| UCB/EECS-2011-63 | 472,741 | |
-| UCB/EECS-2014-54 | 847,494 | |
-| **UCB/EECS-2016-1** | **959,927** | **exactly** the pre-outage size *and* the Wayback capture size |
-| UCB/EECS-2016-118 | 777,931 | |
-| UCB/EECS-2016-161 | 625,668 | |
-
-The TR index is also back (HTTP 200, 122,784 B). `iris.eecs.berkeley.edu` still serves the
-58,829-byte themed 404 — confirmed by negative control — so that host was a staging artefact of a
-migration in progress, not a new home.
-
-**What this changes:** the durability alarm was overstated. What it does *not* change is the
-lesson — for roughly three weeks the canonical RISC-V specifications were unreachable at every
-published URL, and only Wayback had them. The corrected reading is *"URLs moved, content was never
-lost"*, which is the same conclusion the corpus reaches everywhere else.
-
-### 1.2 Anubis returns **HTTP 200**, not 403. Reclassified.
-
-The corpus recorded Anubis proof-of-work walls as a ~4.6 kB **403** fingerprint. **That is wrong.**
-Re-probed with body inspection:
-
-| Host | Code | Bytes | `<title>` |
-|---|---|---|---|
-| `rcaap.pt` | **200** | 4,511 | *Making sure you're not a bot!* |
-| `portal.dnb.de` | **200** | 4,475 | *Making sure you're not a bot!* |
-| `base-search.net` | **200** | 7,846 | *Making sure you're not a bot!* |
-| `scipost.org` | **200** | 3,903 | *Making sure you're not a bot!* |
-| `helda.helsinki.fi` | **200** | 2,123 | *Oh noes!* (Anubis error page) |
-
-**Anubis belongs in the soft-200 trap category, not the 403-fingerprint table** — it is strictly
-more dangerous than a 403, because a status-code check reads it as success. The reliable
-discriminator is the title string, not the byte size.
-
-### 1.3 Two hosts are no longer walled
-
-- **`cds.cern.ch`** — HTTP 200, **41,946 B**, `<title>CERN Document Server</title>`. A real page.
-  The corpus records it as "HTML and REST behind Anubis"; that is no longer true.
-- **`research-collection.ethz.ch`** — HTTP 200, 782 B real page. The 1,337-byte custom 403 is gone,
-  **confirming the original finding that ETH's block is IP/provider-scoped rather than UA-scoped.**
-
-### 1.4 OpenReview's API block was transient
-
-`api2.openreview.net/groups?id=venues` answers again: **4,653 venues** (recorded 4,634, +19). The
-`ChallengeRequiredError` that defeated six user agents during the original pass has lifted. The
-recorded venue figure is confirmed; the per-venue submission counts remain `[NOT-VERIFIED]` because
-of the `10000` cap documented in `additional-preprint-servers.md`.
-
-### 1.5 CogPrints' recovery route has degraded
-
-The corpus records that CogPrints fails over HTTPS (TLS SAN mismatch) but that **plain HTTP 301s to
-Southampton's archive and returns 200**. On 2026-09-11 that redirect now lands on **HTTP 401**
-(7,493 B) — the Southampton BotStopper wall documented elsewhere in the corpus has been extended to
-the archive path. **The documented recovery route no longer works for scripted clients.**
-
-### 1.6 ⚠ Dating error in the theses record
-
-`theses-and-dissertations.md` is stamped **2026-09-04** throughout. Its actual write time is
-**2026-09-07** (filesystem mtime), because a stale "today" was carried forward into the research
-brief. Its server-supplied dates (e.g. the EThOS ResourceSync `at=2026-09-06`) are genuine.
-
-**Read every `2026-09-04` in that file as "2026-09-06/07".** The dates in all other records match
-their mtimes and are correct. Not silently rewritten, because the exact probe date per claim cannot
-be reconstructed and false precision would be worse than a flagged approximation.
-
----
-
-## 2. Confirmed unchanged
-
-Re-probed 2026-09-11; all matched the recorded values.
-
-| Finding | Recorded | Now |
-|---|---|---|
-| NDLTD Global ETD Search dead | 503, 505 B | ✅ 503, 505 B |
-| DART-Europe closed | closed 2025-02-03 | ✅ redirects to UCL closure notice |
-| OATD blocks all clients | 403 Cloudflare | ✅ 403 (5,442 B; `robots.txt` 5,493 B) |
-| EThOS metadata-only | 200, 62,214 B | ✅ 200, 62,214 B |
-| EThOS bogus-`uin` trap | 200 + home page | ✅ reproduces exactly |
-| `bodoarxiv.org` is a casino | 200 | ✅ 200, 83,368 B |
-| `lawarxiv.org` parking stub | 114 B | ✅ 114 B |
-| `mediarxiv.org` stranger's redirect | → unrelated site | ✅ → `afterdispatch.com` |
-| `frenxiv.org` frozen zombie | 200 | ✅ 200, 44,186 B |
-| `latarxiv` · `inarxiv.id` · `marxiv` · `nutrixiv` · `africarxiv.ubuntunet` · `rinarxiv` | dead / TLS-broken | ✅ all `000` |
-| `hpl.hp.com` TCP-dead | timeout | ✅ timeout |
-| CiteSeerX dead | 301 → fixed Wayback ts | ✅ `20251230112235` |
-| Cloudflare 5.6 kB family | 5,583–5,623 B | ✅ techrxiv 5,620 · authorea 5,620 · chemrxiv 5,595 · scienceopen 5,602 · essopenarchive 5,622 · advance 5,623 · **ssrn 5,731** |
-| `preprints.org` minimal 403 | 369 B | ✅ 369 B |
-| CORE theses | 7,921,188 | ✅ **7,921,188** — exact |
-
-**`synthical.com` is still TCP-unreachable**, ten days after first observation. The corpus
-deliberately recorded it as *unreachable*, not *defunct*, on the grounds that one host on one day
-proves nothing. Three observations across ten days now support the stronger reading, but the record
-is left as-is — that caution was correct and the distinction still matters.
-
----
-
-## 3. Growth — confirms the records
-
-Drift consistent with ordinary accumulation over 7–10 days. No record needs changing.
-
-| Metric | Recorded | 2026-09-11 | Δ |
-|---|---|---|---|
-| Zenodo records | 7,231,589 | **7,267,019** | +35,430 |
-| arXiv `cs.AR` | 8,932 | **9,019** | +87 |
-| bioRxiv `count_new_papers` | 347,954 | **348,506** | +552 |
-| ECCC newest report | TR26-163 | **TR26-173** | +10 |
-| OpenReview venues | 4,634 | **4,653** | +19 |
-
-### A methodology check that vindicated the record
-
-An initial re-probe read bioRxiv at **479,561** against a recorded 347,954 — an apparent 38%
-discrepancy. It was not drift. The bioRxiv API exposes **both** `total` (479,561, counting every
-version) and `count_new_papers` (348,506, distinct preprints). **The original record used the
-correct field; the verification query used the wrong one.**
-
-Worth propagating as a trap: `api.biorxiv.org` returns two plausible totals in the same object, and
-the obvious one is wrong for counting preprints.
-
----
-
-## 4. Open items closed
-
-| Item | Resolution |
-|---|---|
-| **Stanford CS/CSL technical-report index** — the last unchecked archival candidate | **CLOSED.** Live at HTTP 200 / **1,332 B** (matching the recorded size) **and archived** — CDX shows `i.stanford.edu/TR/` captured `20241119002302`, with individual report pages back to 2015. No submission needed |
-| **Torvalds thesis "unarchived"** | **CLOSED — the original alarm was false.** Continuously archived 2018-05-11 → 2026-08-07, digest identical to the live file. Cause: `archive.org/wayback/available` returns false negatives (see below) |
-| **Berkeley series unreachable** | **CLOSED** — restored at `/Archive/`, §1.1 |
-
----
-
-## 5. Standing methodological findings
-
-Produced or hardened by this verification pass; all are in
-[`retrieval-notes.md`](retrieval-notes.md).
-
-1. **`archive.org/wayback/available` returns false negatives.** It reported no captures for a URL
-   CDX shows continuously archived since 2018. It fails *toward* phantom link rot. **Confirm absence
-   with the CDX API.**
-2. **The CDX `length` field is the WARC record length, not the payload size.** Compare the `digest`
-   (base32 SHA-1) against a local file instead — done here for the Torvalds thesis.
-3. **Anubis answers HTTP 200.** Detect it by `<title>Making sure you're not a bot!</title>`.
-4. **`hdl.handle.net/api/handles/<prefix>/<suffix>`** is the best existence oracle found — served by
-   the Handle System, so it works straight through the target's bot wall.
-5. **Follow redirects when probing APIs.** `zenodo.org/api/*` and `export.arxiv.org` over HTTP both
-   301; omitting `-L` yields empty bodies that look like blocks. Two false "rate-limited"
-   conclusions in this pass traced to exactly that.
-6. **Empty or wildcard queries mean "nothing", not "everything"** on NTRS, OSTI **and** CiNii —
-   three independent implementations.
-
----
-
-## 6. Not re-derived
-
-Honest gaps in this verification, not in the original records.
-
-- **Cryptology ePrint total** (27,552) — the per-year page structure defeated a quick scrape; not
-  re-derived. The original figure was cross-checked five independent ways at the time.
-- **OSF Preprints total** (200,519) — `api.osf.io` timed out on three attempts.
-- **arXiv `cs.DC`, `cs.OS`** — arXiv's one-request-per-three-seconds limit; probing stopped rather
-  than pushed, consistent with this corpus's own guidance.
-- ~~**`ai-crawler-site-access-table.md` merge**~~ — **DONE 2026-09-20.** Merged as a new
-  *Scholarly / preprint / archival* section, seven *General retrieval tips* additions, and a dated
-  correction to that file's existing `archive.org/wayback/available` advice, which this pass
-  disproved. Append-only; concurrent unstaged work in that file was preserved.
-
----
-
-## 7. Verdict
-
-**The corpus survives verification.** Of ~40 volatile findings re-probed, **five required
-correction** (§1) and **one dating error** was found and flagged. Everything else either matched
-exactly or drifted by an amount consistent with normal accumulation.
-
-The two most consequential corrections — Berkeley restored, and Anubis returning 200 — both make
-the corpus *more* accurate about the thing it is actually measuring: **content is rarely lost;
-addresses and access paths change constantly, and status codes lie.**
diff --git a/research/preprint-repositories/additional-preprint-servers.md b/research/preprint-repositories/additional-preprint-servers.md
deleted file mode 100644
index 080a292..0000000
--- a/research/preprint-repositories/additional-preprint-servers.md
+++ /dev/null
@@ -1,1346 +0,0 @@
-# Additional preprint servers — what Wikipedia's list leaves out
-
-- **Compiled:** 2026-09-02. Every figure below was measured on that date unless stated otherwise.
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-- **Scope:** repositories, overlay platforms and open-review venues that are **absent from**
-  [Wikipedia's *List of preprint repositories*][wp] but that a working engineer will hit anyway.
-
-[wp]: https://en.wikipedia.org/wiki/List_of_preprint_repositories
-
----
-
-## Premise
-
-**Wikipedia's list has significant omissions, and several of them matter more to computing than
-most of the entries it does include.**
-
-The list's composition is not random. It over-represents two things:
-
-1. **COS/OSF-branded servers.** A large block of its entries are OSF Preprints providers —
-   SocArXiv, PsyArXiv, EdArXiv, MetaArXiv, MindRxiv, PaleorXiv, MarXiv, NutriXiv, SportRxiv,
-   LawArXiv, BodoArXiv, Frenxiv, AfricArXiv, Arabixiv, IndiaRxiv, INArxiv, LatArXiv, EcoEvoRxiv,
-   BioHackrXiv, ECSarXiv, engrXiv, agriRxiv and more. Eighteen of the thirty-two OSF providers are
-   **closed to new submissions** (see [`osf-preprints.md`](osf-preprints.md)), yet each still gets a
-   line of its own. The `-Xiv`/`-Rxiv` naming convention is doing a lot of the work of *looking
-   like* a category.
-2. **Life sciences and social sciences.** bioRxiv, medRxiv, F1000Research and its five funder
-   clones, PeerJ Preprints, Lancet, Cell Sneak Peek, JMIR, ARPHA, Beilstein, agriRxiv, NutriXiv,
-   Nature Precedings.
-
-What it under-represents is **computing**. arXiv, Cryptology ePrint and TechRxiv are on the list.
-The following are not, and every one of them is a place where computing research is *first*
-published, permanently archived, or bulk-retrievable:
-
-| Omission | Why it matters | Section |
-|---|---|---|
-| **ECCC** | The theoretical-CS analogue of Cryptology ePrint. Running since 1994. **4,832** reports. Reingold's `SL=L`, Dinur's PCP proof, Williams's ACC lower bound all landed here first | [§1](#1-eccc--electronic-colloquium-on-computational-complexity) |
-| **OpenReview** | Where ICLR and NeurIPS actually run peer review, in public. Submissions, reviews, rebuttals, scores and decisions are all fetchable | [§2](#2-openreview) |
-| **ACL Anthology** | Every ACL/EMNLP/NAACL/COLING paper since 1979, free full text, no paywall, bulk BibTeX | [§3](#3-acl-anthology) |
-| **CERN Document Server** / **INSPIRE-HEP** | Detector electronics, FPGA triggers, radiation-hard ASICs, CERN technical reports and theses that exist nowhere else | [§4](#4-cern-document-server-and-inspire-hep) |
-| **dblp** | Metadata only, but *the* canonical CS bibliography, with a full XML dump | [§14](#14-overlays-indexes-and-one-shutdown) |
-
-A defensible reading is that the list is a **library-science artifact**: it enumerates things that
-self-identify as "preprint repositories" and were catalogued as such. ECCC calls itself a
-*colloquium*, OpenReview calls itself a *review platform*, the ACL Anthology calls itself an
-*anthology*, CDS calls itself a *document server*, and dblp calls itself a *bibliography*. None of
-them applied for the label. All of them are, functionally, where you go to read the paper before or
-instead of paying a publisher. [INF]
-
-This record documents them to the same standard as the rest of this directory. Where a claim could
-not be checked it says so.
-
----
-
-## Note on dates
-
-The bulk harvest behind this record was taken on **2026-09-02**. Every figure that this record
-leans on was **re-verified with a fresh live query on 2026-09-04**. Where the two passes disagree,
-both are given — the disagreements are small and are themselves evidence that the server is live.
-
----
-
-# TIER 1 — the major computing omissions
-
-## 1. ECCC — Electronic Colloquium on Computational Complexity
-
-- **URL:** https://eccc.weizmann.ac.il/
-- **Operator:** Weizmann Institute of Science, "under the auspices of the Computational Complexity
-  Foundation (CCF)" [WEB, masthead on every page, 2026-09-04]
-- **Editor-in-chief:** Oded Goldreich [WEB, `/colloquium/scientific_board/`, 2026-09-04]
-- **ISSN:** 1433-8092 [WEB, page footer, 2026-09-04]
-- **Discipline scope:** computational complexity theory, strictly
-- **Launched:** 1994 · **Status:** active — 163 reports posted in 2026 alone
-- **On Wikipedia's list:** **no.** Not under ECCC, not under "Electronic Colloquium", not under
-  Weizmann.
-
-### 1.1 What it is
-
-ECCC is what Cryptology ePrint is to cryptography, for computational complexity: the place a
-complexity theorist posts a result the week it is finished, months to years before a conference or
-journal version exists. It has been doing this continuously since **December 1994**, which makes it
-older than every server on Wikipedia's list except arXiv (1991) and SSRN (1994).
-
-It is *not* a general-purpose preprint server and does not want to be. Its call for papers demands
-submissions with "relevance to computational complexity, clear mathematical profile, and strictly
-mathematical format", and requires that a submission "be in scope, look somewhat new and
-interesting, **contain all proofs**, and be in a readable form" [DOC,
-`https://eccc.weizmann.ac.il/colloquium/call_for_papers/`, 2026-09-04]. The "contain all proofs"
-clause is the important one: an ECCC report is expected to be a *complete* technical report, not an
-extended abstract. This is the opposite of the conference culture the same community operates in.
-
-The institutional history is documented in the scholarly literature by its own founders. ECCC began
-at the University of Trier under Christoph Meinel; the operator's own reading list cites Bern, Damm
-& Meinel, *"The Electronic Colloquium on Computational Complexity (ECCC): A Digital Library in
-Use"*, ECDL 1997, pp. 405–421; Bern, Meinel & Sack, *"Electronic colloquia: idea and practice"*,
-ACM SIGDOC 1998, pp. 113–119; and Meinel & Klotz, *"The first 10 years of the ECCC digital
-library"*, **Communications of the ACM 49(1):131–134, 2006** [DOC,
-`https://eccc.weizmann.ac.il/static/colloquium/read_more/`, 2026-09-04]. It is now hosted at
-Weizmann. Two retrospective PDFs are served from the site itself:
-`/resources/pdf/eccc_10_years.pdf` and `/resources/pdf/eccc_digital_library.pdf` [WEB, links
-present in the homepage HTML, 2026-09-02].
-
-### 1.2 Identifiers — `TRYY-NNN`
-
-Every report gets an identifier of the form **`TRYY-NNN`**: `TR` for *technical report*, a
-two-digit year, a hyphen, and a **three-digit sequence number within that year**, zero-padded,
-starting at `001`. `TR94-001` is the first report ever posted. `TR26-163` is the 163rd of 2026.
-
-The canonical URL rewrites the identifier into a path with the **four-digit** year:
-
-```
-TR04-094  ->  https://eccc.weizmann.ac.il/report/2004/094/
-TR94-001  ->  https://eccc.weizmann.ac.il/report/1994/001/
-```
-
-The PDF hangs off the same path: `https://eccc.weizmann.ac.il/report/2004/094/download/` returns
-`application/pdf`, 187,575 bytes, PDF 1.2, 19 pages [API/probe, 2026-09-04]. Note the trailing
-slash — without it a `HEAD` returns HTTP 200 with `Content-Length: 0`, which will silently defeat a
-size-based existence check.
-
-There is **no DOI**. No report page inspected in this pass carried one, and there is no Crossref or
-DataCite registration visible for ECCC content. Citations to ECCC are by `TRYY-NNN` and URL only.
-[INF from WEB inspection of eleven report pages, 2026-09-04] — the negative is asserted only for
-the pages actually inspected.
-
-### 1.3 Size and growth — per-year counts
-
-Counted by extracting unique `TRYY-NNN` identifiers from each year index page
-(`https://eccc.weizmann.ac.il/year/<YYYY>/`). Harvest 2026-09-02; 2026 re-verified live 2026-09-04.
-
-| Year | Reports | Year | Reports | Year | Reports |
-|---:|---:|---:|---:|---:|---:|
-| 1994 | 27 | 2005 | 163 | 2016 | 206 |
-| 1995 | 62 | 2006 | 160 | 2017 | 193 |
-| 1996 | 66 | 2007 | 137 | 2018 | 213 |
-| 1997 | 58 | 2008 | 110 | 2019 | 187 |
-| 1998 | 76 | 2009 | 148 | 2020 | 193 |
-| 1999 | 48 | 2010 | 203 | 2021 | 182 |
-| 2000 | 91 | 2011 | 175 | 2022 | 186 |
-| 2001 | 103 | 2012 | 186 | 2023 | 213 |
-| 2002 | 74 | 2013 | 191 | 2024 | 202 |
-| 2003 | 87 | 2014 | 184 | 2025 | 215 |
-| 2004 | 121 | 2015 | 209 | **2026 (part)** | **163** |
-
-- **Total 1994 – 2026-09-04: 4,832 reports** [API/probe — 33 year-index pages parsed, 2026-09-02;
-  2026 re-verified live 2026-09-04]
-- The 2026-09-02 harvest gave **162** for 2026 and a total of **4,831**. The 2026-09-04 re-probe
-  gives **163** and **4,832**. One report was posted in between. Both figures are recorded rather
-  than reconciled.
-- **Shape of the curve:** ~27 in the first (partial) year, crossing 100/yr in 2001, crossing 200/yr
-  in 2010, and then **flat at roughly 180–215 reports a year for fifteen straight years**. ECCC is
-  not growing. That is a real and slightly unusual finding: almost every other server in this
-  survey shows compounding growth. [INF from the table above]
-- 2025's **215** is the highest annual figure in the archive's history, by two reports over 2018's
-  and 2023's 213.
-
-For scale: **4,832 reports in 32 years** against Cryptology ePrint's **27,552** in 27 years
-(see [`cryptology-eprint-archive.md`](cryptology-eprint-archive.md)) and arXiv's `cs` at
-**931,100** (see [`arxiv.md`](arxiv.md)). ECCC is *small on purpose*. It is a filter, not a firehose.
-
-### 1.4 The editorial gate — what does not get in
-
-This is the sharpest difference from arXiv and from every OSF-branded server on Wikipedia's list.
-ECCC screens **editorially**, not for plausibility, and it says so in writing.
-
-Published criteria [DOC, `/colloquium/call_for_papers/`, 2026-09-04]:
-
-> To be posted on ECCC, a submission should meet the following criteria: be in scope (see below),
-> look somewhat new and interesting, contain all proofs, and be in a readable form.
-
-And, in a sentence with no analogue on any other server in this survey:
-
-> **Submissions claiming to resolve a grand challenge, such as the P vs. NP problem, may be
-> rejected without further consideration.**
-
-That single line is why ECCC does not have a viXra problem. It is an explicit, published, prior
-refusal to spend reviewer attention on the highest-volume category of crank submission in the
-field. Compare [`vixra.md`](vixra.md), where the same category is the *house speciality*.
-
-The scope statement is likewise narrowing rather than welcoming. It lists sixteen topics
-— algebraic and arithmetic complexity; average-case complexity; circuit complexity; coding theory
-*(complexity aspects only)*; communication complexity; cryptography *(complexity aspects only)*;
-data structure lower bounds; game theory *(complexity aspects only)*; inapproximability;
-interactive and probabilistic proof systems; Kolmogorov complexity; learning *(complexity aspects
-only)*; proof complexity; property testing *(complexity aspects only)*; pseudorandomness and
-derandomization; quantum computation *(complexity aspects only)*; structural complexity — and then
-excludes most of algorithms research outright:
-
-> typically, **algorithmic improvements are not in scope of ECCC**, except in cases where either
-> the improved complexity bounds are closely related to a conjectured lower bound or the techniques
-> are of natural interest to complexity-theoretic studies.
-
-The gate is staffed by a **named scientific board of ~60 researchers** with public email addresses,
-Oded Goldreich as editor-in-chief. The list includes Scott Aaronson, Noga Alon, Boaz Barak, Paul
-Beame, Irit Dinur, Venkatesan Guruswami, Johan Håstad, Yuval Ishai, Subhash Khot, Kurt Mehlhorn,
-Christoph Meinel, Ryan O'Donnell, Toniann Pitassi, Ran Raz, Alexander Razborov, Oded Regev, Omer
-Reingold, Peter Shor, Madhu Sudan, Salil Vadhan, Virginia Vassilevska Williams and others [WEB,
-`/colloquium/scientific_board/`, 2026-09-04]. **The rejection rate is not published** —
-[NOT-VERIFIED]; no figure was found on the site or in the cited literature.
-
-There is a **registration requirement**: submission is by registered author account only, with
-name, email and affiliation, and email activation. Submitted files must be PDF. Abstracts accept
-LaTeX and are rendered to MathML [DOC, `/static/colloquium/how_to_use/`, 2026-09-04].
-
-### 1.5 Revision and comment semantics — the part that matters for citing
-
-ECCC's versioning model is materially different from arXiv's and is the reason an ECCC citation
-needs care.
-
-- **A report is never removed.** The operator's own words: *"once a report has been posted on ECCC
-  its record cannot be removed"* [DOC, `/static/colloquium/how_to_use/`, 2026-09-04]. There is no
-  withdrawal mechanism at all.
-- **Withdrawal is performed by revision, not deletion.** *"the authors may withdraw its claims by
-  posting a revision with the adequate contents. It is recommended to write a short description
-  that details which parts of the original report are withdrawn and which remain valid, and the
-  reasons for the withdrawal."* [DOC, same source] **Consequence: a retracted ECCC result looks
-  exactly like a live one at the identifier level.** You must open the report page and read the
-  revision list. `TRYY-NNN` alone tells you nothing about whether the claim still stands.
-- **Revisions are numbered and separately dated**, and the report page presents the *latest*
-  revision by default while retaining the original. `TR05-046` (Dinur, PCP by gap amplification)
-  displays as *"Revision #1 to TR05-046, 26th September 2005"* with the base report of 2005 still
-  present [WEB, 2026-09-04]. `TR15-119` (Chattopadhyay–Zuckerman) is on **Revision #5, accepted 11
-  February 2019** — nearly four years after the original posting [WEB, 2026-09-04]. Citing
-  "TR15-119" without a revision number is ambiguous across a four-year span.
-- **Comments are a first-class object.** ECCC advertises *"the feature of an ongoing public
-  scientific discussion. Corrections, improvements, remarks etc. concerning an existing report"*
-  [DOC, `/colloquium/call_for_papers/`, 2026-09-04]. `TR05-046` carries **six** comment blocks
-  alongside its revisions [WEB, 2026-09-04]. This is post-publication review, in public, twenty
-  years before the term was fashionable — and it long predates OpenReview (§2).
-- **There is a caveat in the copyright notice that cuts the other way:** *"The author may withdraw
-  the paper from the digital library of ECCC iff the paper is accepted for publication elsewhere.
-  In particular, it is the responsibility of the author to do this if he/she signs a copyright
-  agreement which does not allow electronic distribution by ECCC"* [DOC,
-  `/static/colloquium/copyright_notice/`, 2026-09-04]. This **directly contradicts** the "cannot be
-  removed" statement in the how-to-use page. Both are live on the site on the same date. Recorded
-  as a conflict, not resolved. [WEB ×2, 2026-09-04]
-
-Every report page also shows a **public download counter** — `TR04-094` reads 11,435 downloads,
-`TR94-010` reads 10,511, `TR94-001` reads 4,803 [WEB, 2026-09-04]. No other server in this survey
-exposes per-item usage this plainly. Treat it as an unaudited operator-supplied number, not a
-metric.
-
-### 1.6 Landmark results, with verified identifiers
-
-Every row below was fetched individually on **2026-09-04** and the title and author list read off
-the live report page. Rows that could not be confirmed were dropped (see the note after the table).
-
-| Paper | Identifier | Posted | Authors (as shown on ECCC) | Why it matters | Preprint first? |
-|---|---|---|---|---|---|
-| On Rank vs. Communication Complexity | **TR94-001** | 1994-12-12 | Noam Nisan, Avi Wigderson | The first report in the archive. Log-rank conjecture gap | Yes — ECCC's report #1 |
-| Natural Proofs | **TR94-010** | 1994-12-12 | Alexander Razborov, Steven Rudich | *The* barrier result: why the circuit-lower-bound programme stalled. Gödel Prize 2007 | ECCC copy contemporaneous with STOC'94/JCSS'97 |
-| Entropy Waves, the Zig-Zag Graph Product, and New Constant-Degree Expanders and Extractors | **TR01-018** | 2001-02-23 | Omer Reingold, Salil Vadhan, Avi Wigderson | The zig-zag product. Gödel Prize 2009. Underpins modern expander and extractor constructions | Yes — Feb 2001, before FOCS'00/Annals 2002 print |
-| Undirected ST-Connectivity in Log-Space | **TR04-094** | 2004-11-10 | Omer Reingold | **SL = L.** Gödel Prize 2009. One of the cleanest derandomization results ever proved | Yes — Nov 2004, before STOC'05 |
-| The PCP Theorem by gap amplification | **TR05-046** | 2005 (Rev #1 2005-09-26) | Irit Dinur | The combinatorial reproof of the PCP theorem. Gödel Prize 2019 | Yes — ECCC, then STOC'06/JACM 2007 |
-| Optimal Inapproximability Results for MAX-CUT and Other 2-Variable CSPs? | **TR05-101** | 2005-09-20 | Guy Kindler, Ryan O'Donnell, Subhash Khot, Elchanan Mossel | Unique Games ⇒ Goemans–Williamson is optimal for MAX-CUT. Gödel Prize 2018 | ECCC copy Sept 2005; FOCS'04 preceded it |
-| Delegating Computation: Interactive Proofs for Muggles | **TR17-108** | 2017 (Rev #1 2017-12-24) | Shafi Goldwasser, Yael Tauman Kalai, Guy Rothblum | **GKR.** The doubly-efficient interactive proof that verifiable-computation and zk-rollup systems are built on | ECCC copy postdates STOC'08; this is the canonical open full version |
-| Pseudorandom Sets in Grassmann Graph have Near-Perfect Expansion | **TR18-006** | 2018 (Rev #2 2018-05-19) | Subhash Khot, Dor Minzer, Muli Safra | Completed the proof of the **2-to-2 Games Theorem** | Yes — ECCC first |
-| Explicit Two-Source Extractors and Resilient Functions | **TR15-119** | 2015 (Rev #5 2019-02-11) | Eshan Chattopadhyay, David Zuckerman | Two-source extraction at polylog min-entropy — a 30-year open problem. Directly relevant to hardware RNG post-processing | Yes — ECCC, then STOC'16/Annals |
-| Locally testable codes via high-dimensional expanders | **TR20-072** | 2020-05-05 | Yotam Dikstein, Irit Dinur, Prahladh Harsha, Noga Ron-Zewi | On the road to c³-LTCs; the coding-theory side of HDX | Yes |
-| A VLSI Circuit Model Accounting For Wire Delay | **TR23-186** | 2023-11-28 | Ce Jin, Ryan Williams, Nathaniel Young | Keywords: *circuit complexity, systolic arrays, VLSI, wire delay*. The closest thing to hardware on ECCC | Yes |
-
-**Explicitly not claimed.** Ryan Williams's *"Non-Uniform ACC Circuit Lower Bounds"* (CCC 2011,
-JACM 2014) is frequently assumed to be an ECCC report. **It is not one** — a title scan across all
-33 year-index pages found no matching entry. What *does* exist is **TR11-017**, *"NEXP does not
-have non-uniform quasi-polynomial-size ACC circuits of o(loglog n) depth"* by **Fengming Wang**, a
-different paper by a different author [WEB, 2026-09-04]. This is exactly the kind of error the
-"landmark papers must resolve" rule exists to catch.
-
-### 1.7 What an engineer actually finds there
-
-ECCC is a lower-bounds archive, and lower bounds are about what hardware *cannot* be made to do.
-Concretely useful strands, all present in the harvested year indexes:
-
-- **Randomness extraction** — TR15-119, TR16-088, TR21-075, TR24-176 and dozens more. This is the
-  theory under TRNG post-processing: how much entropy you can extract from a biased, correlated
-  physical noise source. If you are designing a ring-oscillator RNG, the extractor literature here
-  is the thing that tells you whether your conditioning is sound.
-- **Circuit complexity and VLSI** — TR23-186 explicitly models wire delay and systolic arrays;
-  TR21-023 gives `3.1n − o(n)` circuit lower bounds for explicit functions.
-- **Expander graphs** — TR01-018, TR23-089 (*New Explicit Constant-Degree Lossless Expanders*),
-  TR23-160. Expanders are the construction behind LDPC-adjacent codes and interconnect topologies.
-- **Error-correcting and locally testable codes** — TR20-072, TR23-127, TR25-132 (*Time and Space
-  Efficient Deterministic List Decoding*), TR25-170 (Reed–Solomon list decoding).
-- **Interactive proofs / verifiable computation** — TR17-108 (GKR), TR17-102 (RRR overview),
-  TR22-014. This is the theory layer under zk-SNARK and rollup engineering.
-- **Matrix multiplication** — TR14-154 (*Fast Matrix Multiplication: Limitations of the Laser
-  Method*), TR20-029, TR20-030 (*Barriers for Rectangular Matrix Multiplication*), TR25-031 and
-  TR25-066 on error-correcting matrix-multiplication algorithms.
-- **Communication complexity** — the whole TR94-001 lineage. This is where distributed-system and
-  memory-hierarchy lower bounds come from.
-
-What you will **not** find: systems papers, measurement studies, algorithm engineering, benchmarks,
-anything with an implementation section. The scope statement excludes them by design (§1.4).
-
-### 1.8 Access, APIs and bulk retrieval
-
-| Facility | Status | Evidence |
-|---|---|---|
-| Year index `/year/<YYYY>/` | **Works.** Full list of that year's reports with titles and authors, one HTML page. This is the practical bulk-harvest route | [probe] HTTP 200, 159,555 B for 2026, 2026-09-04 |
-| Report page `/report/<YYYY>/<NNN>/` | Works. Title, authors, date, keywords, abstract, revisions, comments, download count | [probe] 2026-09-04 |
-| PDF `/report/<YYYY>/<NNN>/download/` | Works, `application/pdf`. **Trailing slash required** | [probe] 187,575 B for TR04-094, 2026-09-04 |
-| RSS `/feeds/reports/` | **Works.** `application/rss+xml`, 13,841 B, latest reports | [probe] 2026-09-04 |
-| RSS `/feeds/latestReports` | Linked from homepage | [WEB] 2026-09-02 |
-| Keyword index `/keywords/` | Works — **382 distinct keyword pages** under `/keyword/<id>` | [probe] 45,380 B, 2026-09-04 |
-| **OAI-PMH** | **Absent.** `/oai2d?verb=Identify` returns the soft-404 body | [probe] 2026-09-04 |
-| **REST/JSON API** | **None found.** [NOT-VERIFIED] — no documented API endpoint located | 2026-09-04 |
-| **Bulk dump** | **None found.** [NOT-VERIFIED] | 2026-09-04 |
-| `robots.txt` | Disallows `/submit/paper/`, `/search`, `/password`, `/register`. **`/report/`, `/year/` and `/keyword/` are not disallowed** | [probe] 97 B, 2026-09-04 |
-| Bot blocking | **None observed.** Plain `curl` with a default UA succeeded throughout. No Cloudflare, no Anubis, no rate limiting hit at ~35 requests | [probe] 2026-09-02 and 2026-09-04 |
-
-**Probing trap — ECCC serves HTTP 200 for things that do not exist.** This is the most important
-operational finding in this section, and it will corrupt any harvest that trusts status codes:
-
-| Request | HTTP | Bytes | Reality |
-|---|---:|---:|---|
-| `/year/2026/` | 200 | 159,555 | Real, 163 reports |
-| `/year/2099/` | **200** | **17,032** | **Does not exist** — empty year shell |
-| `/year/1900/` | 200 | 17,032 | Does not exist — byte-identical to 2099 |
-| `/report/1994/001/` | 200 | 19,714 | Real (Nisan–Wigderson) |
-| `/report/1994/999/` | **200** | **17,041** | **Does not exist** |
-| `/about/`, `/faq/`, `/imprint/`, `/oai2d?verb=Identify` | **200** | **17,041** | All soft-404s |
-
-The 17,041-byte body renders the literal text *"404 page not found — The page you requested is not
-available!"* while returning HTTP 200. The 17,032-byte body is the empty-year variant. **Use body
-size or a title-string check, never the status code.** This is the same class of trap as
-`osf.io`'s 4,207-byte SPA shell and `unpaywall.org`'s 1,421-byte shell, and it is worth adding to
-the index's [§ Probing traps](README.md#6-probing-traps).
-
-### 1.9 Licensing and reuse — the restrictive surprise
-
-ECCC does **not** use Creative Commons. Its copyright notice [DOC,
-`/static/colloquium/copyright_notice/`, 2026-09-04] states:
-
-- *"There is no copyright transfere from the Author to the Colloquium... all rights are held by the
-  authors, their institutions, or their designees."*
-- *"use of the ECCC reports for commercial purpose is strictly forbidden; no one may sell copies of
-  reports without explicitely written permission of the copyright holders."*
-- *"Access to ECCC reports is limited to **interactive viewing and/or printing for personal
-  use**."*
-
-Read literally, that last clause forbids bulk text mining and forbids redistribution — a
-**stricter** licence than arXiv's default and far stricter than the CC-BY that most servers on
-Wikipedia's list default to. The metadata is open in practice (no `robots.txt` block on `/report/`)
-but the full texts are not licensed for corpus construction. Anyone building an LLM training set or
-a citation corpus from ECCC PDFs should read that sentence first. [DOC, 2026-09-04]
-
-### 1.10 Reliability — what a `TRYY-NNN` actually guarantees
-
-**What it does guarantee:** a dated timestamp; a stable URL that has survived an institutional move
-from Trier to Weizmann; that a named board with a published scope statement let it through; that
-the document contains complete proofs *as claimed by the author*; and that the record can be found
-forever, because nothing is deleted.
-
-**What it does not guarantee:** correctness. ECCC screening is a **scope-and-seriousness gate, not
-peer review.** No referee verifies the proofs. The eventual-publication rate is **[NOT-VERIFIED]**
-— no measurement was found in the literature or on the site, and this pass did not sample for one.
-
-**How to sanity-check an individual ECCC report:**
-
-1. Open the report page and **read the revision list**. A late revision usually means an error was
-   found. Withdrawals are performed *as* revisions (§1.5).
-2. **Read the comments.** ECCC comments are where the community records refutations.
-3. Check whether a conference/journal version exists (dblp — §14 — is the right tool).
-4. If the report claims a grand-challenge resolution and it is *on* ECCC, that is mildly
-   informative, because the call for papers says such submissions may be rejected outright. It is
-   not a guarantee.
-
----
-
-## 2. OpenReview
-
-- **URL:** https://openreview.net/ · **API:** `https://api2.openreview.net` (v2),
-  `https://api.openreview.net` (v1, legacy)
-- **Operator:** OpenReview.net, a project of the **Allen Institute for Artificial Intelligence
-  (AI2)** and UMass Amherst's IESL [COM — widely reported; not independently re-verified in this
-  pass, see §2.6]
-- **What it is:** a **peer-review platform**, not a preprint server — but functionally the largest
-  open archive of *machine-learning submissions and their reviews* in existence
-- **On Wikipedia's list:** **no.**
-
-### 2.1 Why it belongs in this survey
-
-Every other entry in this directory archives a *paper*. OpenReview archives the **paper, its
-reviews, the reviewer scores and confidences, the author rebuttals, the reviewer replies to the
-rebuttals, the area chair's meta-review, and the final decision** — for the largest conferences in
-machine learning, permanently, publicly, and behind an API.
-
-For a working engineer this inverts the usual value proposition. **The reviews are frequently worth
-more than the paper.** A paper tells you what worked. Four signed-by-number reviews plus a rebuttal
-thread tell you: which baselines the authors were forced to add, which ablation a reviewer did not
-believe, what the failure modes are, whether the claimed speed-up survived contact with someone
-who read the appendix, and — uniquely — *how confident the experts were*. Nothing in the published
-PDF carries that. `arXiv` does not have it. `dblp` does not have it. The publisher's version of
-record deliberately deletes it.
-
-### 2.2 Which venues actually use it
-
-The `venues` group is the operator's own registry of venues hosted on the platform.
-
-- **4,621 venue members** [API] `https://api2.openreview.net/groups?id=venues`, retrieved
-  **2026-09-02**
-- **4,634 venue members** [API] same endpoint, re-verified live **2026-09-04**. Thirteen venues
-  added in two days.
-
-Distribution by hosting organisation, from the 2026-09-02 snapshot (a "venue" here is a specific
-conference *or workshop* instance, so ICLR contributes one main-conference entry plus dozens of
-workshops per year):
-
-| Org prefix | Venue entries | Includes |
-|---|---:|---|
-| `thecvf.com` | 476 | CVPR, ICCV, ECCV and their workshops |
-| `NeurIPS.cc` | 423 | NeurIPS main track, datasets & benchmarks track, workshops |
-| `aclweb.org` | 339 | ACL, ARR (ACL Rolling Review) |
-| `IEEE.org` | 273 | assorted IEEE conferences |
-| `ICLR.cc` | 180 | ICLR main conference + workshops, 2013 onward |
-| `ICML.cc` | 176 | ICML + workshops |
-| `ACM.org` / `acmmm.org` | 142 / 132 | ACM venues, ACM Multimedia |
-| `AAAI.org` | 127 | AAAI |
-| `EMNLP` | 121 | EMNLP |
-| `MICCAI.org` | 116 | medical imaging |
-| `KDD.org` | 72 | data mining |
-| `robot-learning.org` / `roboticsfoundation.org` | 73 / 74 | CoRL, RSS |
-| `colmweb.org` | 42 | COLM (LLM conference) |
-| `auai.org` | 22 | UAI |
-| `automl.cc` | 22 | AutoML |
-| `JSYS` | 44 | **Journal of Systems Research** — an open systems journal |
-
-[API] `groups?id=venues`, 2026-09-02, counted by prefix.
-
-**ICLR is the flagship case.** ICLR has run its entire review process in public on OpenReview since
-2013 — reviews visible during the process, not after. **NeurIPS** moved its review data onto the
-platform later and publishes reviews for accepted papers. **TMLR** (Transactions on Machine
-Learning Research) is an OpenReview-native journal with no conference deadline at all.
-
-### 2.3 Counts — and an important caveat
-
-The 2026-09-02 harvest queried per-venue note counts through both API versions. Those numbers are
-reproduced here **with a warning**, because the exact query string was not recorded alongside them
-and the endpoint could not be re-queried on 2026-09-04 (§2.5):
-
-| Venue | v1 `count` | v2 `count` |
-|---|---:|---:|
-| ICLR 2018 | 1,007 | — |
-| ICLR 2019 | 1,562 | — |
-| ICLR 2020 | 2,579 | — |
-| ICLR 2021 | 3,002 | — |
-| ICLR 2022 | 3,412 | — |
-| ICLR 2023 | 4,946 | — |
-| ICLR 2024 | — | 7,382 |
-| ICLR 2025 | — | **10,000** |
-| ICLR 2026 | — | **10,000** |
-| NeurIPS 2021 | 2,767 | — |
-| NeurIPS 2022 | 2,816 | — |
-| NeurIPS 2023 | — | 3,385 |
-| NeurIPS 2024 | — | 4,230 |
-| NeurIPS 2025 | — | 5,493 |
-
-[API] `api.openreview.net` / `api2.openreview.net` note queries, 2026-09-02.
-
-**The two `10,000` values are a cap, not a measurement.** Two consecutive years returning the same
-round number, immediately after a year returning 7,382, is the signature of a server-side result
-limit. **Do not cite ICLR 2025 or ICLR 2026 submission counts from this table.** Marked
-**[NOT-VERIFIED]**. The pre-2024 v1 figures rise monotonically and are not round, which is
-consistent with real counts — but because the filter semantics (all submissions vs. accepted only
-vs. non-withdrawn) could not be re-established, **every number in this table should be treated as
-an order-of-magnitude indication only**. The one figure in this section that is solid is the venue
-count in §2.2, which was re-verified live.
-
-### 2.4 How to fetch a paper *and its reviews*
-
-The data model is uniform: everything is a **Note**. A submission is a note; each review is a note
-whose `forum` field points at the submission's note id; so is each rebuttal, each reply, the
-meta-review and the decision. A forum id is a short opaque string like `AL1fq05o7H`.
-
-```
-# the submission itself
-GET https://api2.openreview.net/notes?forum=<FORUM_ID>&limit=1000
-# every note in the thread — submission + reviews + rebuttals + meta-review + decision
-GET https://api2.openreview.net/notes?forum=<FORUM_ID>&details=replies
-# all submissions to a venue
-GET https://api2.openreview.net/notes?content.venueid=ICLR.cc/2025/Conference&limit=1000&offset=0
-# the venue registry
-GET https://api2.openreview.net/groups?id=venues
-# human-readable
-https://openreview.net/forum?id=<FORUM_ID>
-https://openreview.net/pdf?id=<FORUM_ID>
-```
-
-There is an official Python client (`pip install openreview-py`, `openreview.api.OpenReviewClient`)
-which handles v1/v2 differences and pagination.
-
-**Fields worth knowing.** `content.venueid` carries the *outcome*, not just the venue —
-`ICLR.cc/2024/Conference` for accepted, `ICLR.cc/2024/Conference/Rejected_Submission` for rejected,
-`.../Withdrawn_Submission` and `.../Desk_Rejected_Submission` for the rest. Review notes carry
-`content.rating`, `content.soundness`, `content.confidence`, `content.strengths`,
-`content.weaknesses`, `content.questions`. That means the outcome and the numeric scores are
-machine-readable, at scale, for hundreds of thousands of papers.
-
-### 2.5 A worked example — and why the reviews beat the paper
-
-The single best demonstration is **Mamba**. Retrieved on 2026-09-02 [API]:
-
-```
-FORUM AL1fq05o7H
-title:   Mamba: Linear-Time Sequence Modeling with Selective State Spaces
-authors: Albert Gu, Tri Dao
-venue:   Submitted to ICLR 2024
-venueid: ICLR.cc/2024/Conference/Rejected_Submission
-```
-
-Four reviews are attached, and the API returns their scores verbatim:
-
-| Review id | Rating | Soundness | Confidence | Sample of the recorded objection |
-|---|---|---|---|---|
-| `eIarHE3vGs` | **3: reject, not good enough** | 2 fair | 5: absolutely certain | "The motivation of Mamba is to address the drawbacks of recurrent models… There are many works following the same direction: S4-diagonal, SGConv, MEGA, SPADE…" |
-| `bq8XeiBhwY` | 6: marginally above threshold | 3 good | 2: quite likely did not understand central parts | "The model still has a quadratic memory requirement during training like Transformers." |
-| `ZJCXkIMKQY` | 8: accept, good paper | 4 excellent | 4: confident | "I do not identify any major weaknesses of the paper." |
-| `t7w5AlzJfq` | 8: accept, good paper | 4 excellent | 5: absolutely certain | missing citations to linear-attention and LongConv work |
-
-[API] `api2.openreview.net`, forum `AL1fq05o7H`, retrieved 2026-09-02.
-
-Mamba was **rejected from ICLR 2024**. It went on to become one of the most-cited architecture
-papers of the following two years, and the state-space-model line of work it anchors now runs on
-production accelerators. The permanent, public, timestamped record of a **confidence-5 reviewer
-scoring it 3/reject** is not available anywhere else, and it is exactly the kind of evidence you
-want when deciding how much weight a conference decision deserves. It is also a genuine data point
-about review reliability: two confidence-5 reviewers on the same paper gave it 3 and 8.
-
-Note the second row as well — a reviewer self-reporting confidence 2 ("quite likely that you did
-not understand the central parts of the submission") whose stated weakness is factually wrong about
-the architecture. That is on the record forever. On arXiv there is no such record at all.
-
-### 2.6 Access, reachability and the 2026-09-04 blackout
-
-**This is the durability finding of this section.** OpenReview's state changed between the two
-probe dates in this pass.
-
-| Endpoint | 2026-09-02 | 2026-09-04 |
-|---|---|---|
-| `api2.openreview.net/groups?id=venues` | works, 4,621 members | **works**, 4,634 members |
-| `api2.openreview.net/notes?...` | works, JSON returned | **HTTP 403 `ChallengeRequiredError`** |
-| `api.openreview.net/notes?...` (v1) | works | **HTTP 403 `ChallengeRequiredError`** |
-| `openreview.net/forum?id=AL1fq05o7H` | works | **HTTP 200, 4,787-byte challenge shell** |
-| `openreview.net/pdf?id=AL1fq05o7H` | works | **HTTP 403, 12,692-byte HTML** (not a PDF) |
-| `openreview.net/group?id=ICLR.cc/2025/Conference` | — | works, 164,976 B |
-
-The 403 body is JSON:
-
-```json
-{"name":"ChallengeRequiredError","message":"Challenge verification required (2026-09-04-…)",
- "status":403,"details":{"challengeUrl":"https://openreview.net/challenge?redirect=…"}}
-```
-
-**User-agent rotation does not help.** Chrome 131, `curl/8.21.0`, `python-requests/2.31.0`,
-`WhatsApp/2.23.20.0`, `ChatGPT-User/1.0` and `ClaudeBot/1.0` all received the identical 403 on
-2026-09-04 [probe ×6]. This is a JS browser-verification interstitial ("Verifying your
-browser | OpenReview"), not a UA filter — the AGENTS.md fallback ladder is the wrong tool for it.
-
-**Probing trap.** `https://openreview.net/forum?id=<anything>` returns **HTTP 200 and a
-4,787-byte challenge shell for a real forum id and for the deliberately bogus `ZZZZZZZZZZ`
-alike** [probe, negative control, 2026-09-04]. Byte-identical. Same failure class as `osf.io`'s
-4,207-byte shell. Under the challenge regime, **neither the status code nor the body size can test
-whether a paper exists.**
-
-**Practical guidance:** use `openreview-py` with an authenticated account, or expect to solve the
-interstitial. The `groups` endpoint remained open on both dates, so venue enumeration still works
-unauthenticated.
-
-### 2.7 Reliability, licensing, caveats
-
-- **A note on OpenReview is not a preprint deposit.** There is no DOI, no independent archive, no
-  guarantee of persistence beyond the platform. Compare arXiv, which has an institutional
-  preservation commitment.
-- **Withdrawn and desk-rejected submissions may be hidden.** Visibility is set per venue by the
-  organisers. Mamba's rejection is visible because ICLR publishes rejected submissions; most
-  venues do not. **Absence of a paper from OpenReview is not evidence it was not submitted.**
-- **Licensing is per-venue and inconsistent.** Some venues attach CC-BY, many attach nothing. There
-  is no site-wide default. Treat bulk reuse of OpenReview PDFs as unlicensed unless you check the
-  specific note.
-- **The operator attribution above is [COM], not [DOC].** The AI2/UMass-IESL provenance is widely
-  reported and matches the platform's own history, but the About page could not be loaded on
-  2026-09-04 because of the challenge, so it is not carried here as [DOC].
-- **Reviews are not signed.** Reviewer identities are pseudonymous (`Reviewer_xY3z`). You get the
-  argument and the self-reported confidence, not the person.
-
----
-
-## 3. ACL Anthology
-
-- **URL:** https://aclanthology.org/ · **Operator:** Association for Computational Linguistics
-- **Scope:** computational linguistics and NLP · **Coverage from:** 1952 (entries), the modern
-  ACL series from 1979 · **On Wikipedia's list:** **no.**
-
-### 3.1 What it is
-
-The complete, free, full-text archive of everything the ACL publishes: **ACL, EMNLP, NAACL, EACL,
-AACL, COLING, CoNLL, *SEM, SemEval, TACL, CL** and every workshop attached to them. No paywall, no
-membership, no embargo — the PDF is up the day the proceedings appear, and it has been that way for
-decades. In a field where the top venues are conferences, this means **the entire canon of NLP is
-open access by default**. Nothing else in this survey has that property.
-
-Given that the last five years of ACL-venue work is the intellectual substrate of every deployed
-language model, an archive that is 100% open and bulk-downloadable is not a niche resource.
-
-### 3.2 Size — measured from the bulk BibTeX
-
-The operator publishes **the whole bibliography as one gzipped BibTeX file**:
-`https://aclanthology.org/anthology.bib.gz`.
-
-| Measurement | Value | Evidence |
-|---|---:|---|
-| File size | **12,647,756 bytes** | [API] 2026-09-02 |
-| File size (re-fetch) | **12,648,737 bytes** | [API] 2026-09-04, `application/x-gzip` |
-| BibTeX entries | **131,027** | [API] parsed, 2026-09-02 |
-| BibTeX entries (re-fetch) | **131,040** | [API] parsed live, 2026-09-04 — 13 added in two days |
-| `@inproceedings` | 124,477 | [API] 2026-09-02 |
-| `@article` (TACL, CL) | 3,362 | [API] 2026-09-02 |
-| `@proceedings` (volume records) | 2,968 | [API] 2026-09-02 |
-| `@book` | 220 | [API] 2026-09-02 |
-| Year range | **1952 – 2026** | [API] 2026-09-02 |
-
-**Growth, by year of publication** [API] parsed from the 2026-09-02 dump:
-
-| 1979 | 1990 | 2000 | 2010 | 2015 | 2020 | 2023 | 2024 | 2025 | 2026 (part) |
-|---:|---:|---:|---:|---:|---:|---:|---:|---:|---:|
-| 50 | 515 | 1,254 | 3,072 | 2,911 | 7,330 | 9,094 | 12,135 | **14,919** | 10,413 |
-
-The curve is the LLM boom rendered as bibliography: roughly flat 2010–2015, then a 5× increase to
-2025. 2026 is at 10,413 by early September and on track to exceed 2025. Note that ~2,968 of the
-131,027 entries are *volume* records rather than papers, so the paper count is ≈128,000. [INF]
-
-### 3.3 Access and bulk retrieval
-
-| Facility | Result |
-|---|---|
-| `https://aclanthology.org/anthology.bib.gz` | **Works**, 12.6 MB, whole corpus [API] 2026-09-04 |
-| Landing page `https://aclanthology.org/N19-1423/` | HTTP 200, 42,299 B, title *"BERT: Pre-training of Deep Bidirectional Transformers…"* [WEB] 2026-09-04 |
-| PDF `https://aclanthology.org/N19-1423.pdf` | HTTP 200, 786,279 B, PDF 1.3, 16 pages [API] 2026-09-04 |
-| **Negative control** `https://aclanthology.org/Z99-9999/` | **HTTP 404**, 9,185 B — an *honest* 404 [probe] 2026-09-04 |
-| Bot blocking | **None.** No challenge, no UA filtering, no rate limit hit |
-| Other bulk formats | Per-volume BibTeX/MODS/Endnote; the site is generated from a public GitHub repo of XML |
-
-**The ACL Anthology is the best-behaved server in this entire survey.** It returns a real 404 for a
-nonexistent identifier — which ECCC (§1.8), OpenReview (§2.6), CDS (§4.4), `osf.io` and
-`unpaywall.org` all fail to do — it serves a complete bulk dump over plain HTTP with no
-registration, and it does not challenge scripted clients. If you need a reference implementation of
-how an open archive should behave, this is it.
-
-**Licensing:** most modern ACL papers carry **CC-BY 4.0**, stated on the landing page. Older
-material predates the policy and is not uniformly licensed. Check per paper before bulk reuse.
-[WEB]
-
-### 3.4 Why the arXiv and Anthology versions differ
-
-Almost every ACL-venue paper also exists on arXiv under `cs.CL`, and they are **not the same
-document**. Which one you should read depends on what you want:
-
-- **The Anthology version is the version of record.** It is camera-ready, page-limit-compliant,
-  post-review, and it is what the DOI and the citation point at.
-- **The arXiv version is usually the *later* one.** Authors commonly post the submission before the
-  deadline and then update after acceptance — but they update *inconsistently*. An arXiv `v3` may
-  contain an extra appendix, extra ablations added during rebuttal, corrected numbers, or the
-  reviewer-demanded baseline that would not fit in the camera-ready page limit.
-- **The arXiv version can also be the *earlier*, worse one.** A `v1` posted before review may
-  contain results the reviewers rejected. There is no automatic propagation from the Anthology back
-  to arXiv.
-- **Consequence:** if you are reproducing a numeric result, take the Anthology PDF and treat the
-  arXiv PDF as a possible superset. If you are citing, cite the Anthology. If a number does not
-  reproduce, check whether the other version reports a different one. [INF]
-- Three-way triangulation is available and cheap: Anthology (record) + arXiv (extended) +
-  OpenReview (§2, for ARR/ACL-Rolling-Review venues — the reviews that caused the difference).
-
----
-
-## 4. CERN Document Server and INSPIRE-HEP
-
-Two CERN-adjacent systems, both absent from Wikipedia's list, both of direct interest to hardware
-engineers for a reason that has nothing to do with particle physics: **the LHC experiments are the
-largest sustained real-time-electronics programme on earth**, and they publish their engineering.
-
-### 4.1 Why a hardware engineer cares
-
-The material that lives in these two systems and nowhere else:
-
-- **Trigger systems** — Level-1 trigger designs are hard-real-time FPGA pipelines with fixed
-  microsecond latency budgets processing terabits per second. The ATLAS and CMS trigger technical
-  design reports are the most detailed public documents of their kind.
-- **Front-end ASICs** — custom readout chips (Timepix, VeloPix, RD53, the ALICE and LHCb front
-  ends), with process-node choices, power budgets, and measured noise.
-- **Radiation-hardened design** — total-ionising-dose and single-event-upset behaviour of
-  commercial and custom parts, characterised on real beamlines. **1,932 INSPIRE records** match
-  `"radiation hard"` [API, 2026-09-04].
-- **High-speed optical links, clock distribution, timing** — GBT/lpGBT, sub-picosecond distribution
-  over kilometres.
-- **Silicon detector technology** — the semiconductor-device physics behind pixel and strip sensors.
-- **CERN technical reports, notes and theses** — CERN doctoral theses are deposited in CDS and are
-  frequently the *only* complete write-up of a subsystem's electronics.
-
-Search counts on INSPIRE, all [API] 2026-09-04: `FPGA` **5,380**, `trigger electronics` **5,430**,
-`ASIC` **2,869**, `"radiation hard"` **1,932**, `ATLAS FPGA` **526**.
-
-### 4.2 INSPIRE-HEP — the API works and is pleasant
-
-- **URL:** https://inspirehep.net/ · **API base:** `https://inspirehep.net/api/`
-- **Operator:** a collaboration of CERN, DESY, Fermilab, IHEP, IN2P3, SLAC and others
-- **Lineage:** successor to **SPIRES** (SLAC, 1974) — the database that the *first web server
-  outside Europe* was built to serve. Predates arXiv by seventeen years.
-
-| Collection | Records | Evidence |
-|---|---:|---|
-| `literature` | **1,882,221** | [API] `/api/literature/?q=&size=1`, 2026-09-02 |
-| `literature` (re-verified) | **1,882,844** | [API] same, live 2026-09-04 — **+623 in two days** |
-| `conferences` | 31,706 | [API] 2026-09-04 |
-| `jobs` | 31,675 | [API] 2026-09-04 |
-| `institutions` | 12,315 | [API] 2026-09-04 |
-| `data` | 11,615 | [API] 2026-09-04 |
-| `experiments` | 4,002 | [API] 2026-09-04 |
-
-**Negative control:** `?q=zzqqxx_nonexistent_term_9999` returns HTTP 200 with `hits.total: 0` and an
-empty `hits.hits` array — a **truthful** empty result, verified on both dates. INSPIRE does not
-inflate and does not fake. [API]
-
-Usage:
-
-```
-GET https://inspirehep.net/api/literature?q=<query>&size=<n>&page=<n>&fields=titles,authors
-GET https://inspirehep.net/api/literature/1483465                       # single record
-GET https://inspirehep.net/api/literature/1483465?format=bibtex         # also latex-eu, latex-us, cv, json-expanded
-GET https://inspirehep.net/api/literature/?q=refersto%3Arecid%3A1483465 # citations to a record
-GET https://inspirehep.net/api/doi/<doi>   /api/arxiv/<id>              # resolve by external id
-```
-
-Every record carries a `links` object with those alternate formats pre-built, plus a
-`fields=` projection parameter to keep responses small. No authentication, no challenge, no UA
-filtering observed on either probe date. The `q` syntax supports the legacy SPIRES operators
-(`t `, `a `, `refersto:`, `citedby:`) as well as plain full text.
-
-An arbitrary record retrieved as a sanity check on 2026-09-02: **id 1483465, "The Silicon-Tungsten
-Tracker of the DAMPE Mission"** — i.e. a detector-instrumentation paper, which is representative of
-what the collection is full of. [API]
-
-### 4.3 CERN Document Server (CDS)
-
-- **URL:** https://cds.cern.ch/ · **Operator:** CERN
-- **Scope:** CERN's institutional repository — papers, preprints, **technical reports, internal
-  notes, theses, talks, scanned historical documents, photos, video**
-- **OAI-PMH base:** `http://cds.cern.ch/oai2d` · **`earliestDatestamp`: 2003-06-02T08:06:23Z**
-  [API] `verb=Identify`, 2026-09-02 **and** re-verified 2026-09-04
-- **Deleted-record policy:** `persistent` · **granularity:** `YYYY-MM-DDThh:mm:ssZ` [API]
-- **Submission policy, in CDS's own words:** *"Submission restricted."* **Metadata policy:** *"Free
-  and unlimited use by anybody with obligation to refer to original record."* **Data policy:**
-  *"Refer to the copyright and license statement of each specific record."* [DOC, embedded in the
-  OAI `Identify` response, 2026-09-02]
-
-That "submission restricted" line is the key structural fact: **CDS is not a preprint server anyone
-can post to.** It is an institutional repository. Deposits come from CERN members and CERN
-processes. That is precisely why it holds material — internal notes, engineering reports — that
-would never be submitted to arXiv.
-
-**Set sizes**, measured via `ListIdentifiers` and reading `completeListSize` from the
-`resumptionToken` [API, all 2026-09-04]:
-
-| Set | Records | What it is |
-|---|---:|---|
-| *(no set — whole repository)* | **578,928** | Everything harvestable over OAI |
-| `cerncds:BOOK` | 172,038 | CERN library book records |
-| `cerncds:CERN` | 158,072 | CERN-authored documents |
-| `cerncds:FULLTEXT` | **316,404** | **Records that actually have full text attached** |
-| `cerncds:CONF` | 34,467 | Conference contributions |
-| `cerncds:REPORT` | 28,956 | **Technical reports** |
-| `cerncds:THESES` | 11,992 | **Theses** |
-| `cerncds:SCAN` | 10,391 | Scanned historical documents |
-| `cerncds:pauli-archive` | 3,821 | The Pauli archive |
-| `cerncds:atlas-conf` | 1,295 | ATLAS conference notes |
-| `cerncds:cms-notes` | 932 | CMS internal notes |
-| **`zzz:bogus`** *(negative control)* | — | `noRecordsMatch` error — **correct behaviour** |
-
-**578,928 total against 316,404 with full text** is the number to carry: **just over half of CDS is
-full text**; the rest is catalogue metadata (books, photos, talks). Do not quote 578,928 as a
-document count.
-
-Other sets present but not sized here: `cerncds:TALK`, `cerncds:TALK:FULLTEXT`,
-`cerncds:CERN:FULLTEXT`, `cerncds:CONF:FULLTEXT`, `cerncds:SCAN:FULLTEXT`, `cerncds:alice-pub`,
-`cerncds:atlas-pub`, `cerncds:cms-pas`, `cerncds:lhcb-conf`, `cerncds:lhcb-pub`, `cerncds:EuCARD`,
-`cerncds:MEMORIAV`, `DOI`, `INSPIRE`, `INSPIRE:HEP`, `forINSPIRE`, `forSciTalks`, `ForCDS`,
-`openaire`, `INIS`, and arXiv-style subject sets `cerncds:hep-ex|hep-ph|hep-th|hep-lat|nucl-ex|
-nucl-th|astro-ph|gr-qc|quant-ph|math|math-ph|physics|cs` [API, `verb=ListSets`, 2026-09-02].
-Note that **`cerncds:cs` exists but returned no `completeListSize`** on 2026-09-04 —
-[NOT-VERIFIED], not sized.
-
-CDS names its OAI *friends*: `http://cds.cern.ch/oai2d`, `http://openaire.cern.ch/oai2d`,
-`http://export.arxiv.org/oai2` [API, `Identify`, 2026-09-02].
-
-### 4.4 CDS probing trap — Anubis, and the way past it
-
-**`cds.cern.ch` is behind an Anubis proof-of-work bot wall on its HTML and REST interfaces, but its
-OAI-PMH endpoint is wide open.** This is the single most useful retrieval finding in this record.
-
-| Endpoint | 2026-09-02 | 2026-09-04 |
-|---|---|---|
-| `cds.cern.ch/api/records?q=&size=1` | **HTTP 200, 7,519-byte Anubis challenge** | **HTTP 200, 7,619-byte Anubis challenge** |
-| `cds.cern.ch/search?p=FPGA&of=hx` | — | **HTTP 200, 7,619-byte Anubis challenge** |
-| `cds.cern.ch/oai2d?verb=Identify` | **HTTP 200, real XML, 2,384 B** | **HTTP 200, real XML, 2,384 B** |
-| `cds.cern.ch/oai2d?verb=ListSets` | **HTTP 200, real XML, 4,260 B** | works |
-| `cds.cern.ch/oai2d?verb=ListIdentifiers&…` | works | works |
-
-Two things make this a *trap* rather than a mere block:
-
-1. **The challenge is served with HTTP 200, not 403.** A harvester checking status codes records a
-   success and stores the challenge page as if it were data. The tell is the `<title>Making sure
-   you're not a bot!</title>` and the `anubis_challenge` JSON block, and the ~7.5 kB body size.
-   (Note: this is a *different* signature from the ~5.6 kB Cloudflare 403 body documented in the
-   index — same idea, different vendor, and Anubis uses 200 where Cloudflare uses 403.)
-2. **User-agent rotation does not defeat it.** The challenge body from 2026-09-02 embeds the
-   metadata it saw: `"User-Agent":"curl/8.21.0"`, `"X-Real-Ip":"…"`, `"algorithm":"fast"`,
-   `"difficulty":4`. It is a JavaScript SHA proof-of-work, not a UA filter. Chrome-UA requests on
-   2026-09-04 received the same challenge.
-
-**Use OAI-PMH.** `verb=ListRecords&metadataPrefix=marcxml&set=cerncds:REPORT` (or `oai_dc`) gets you
-the CERN technical-report corpus with no challenge at all. Add this to the crawler access table.
-
----
-
-# TIER 2 — smaller omissions, compact records
-
-Measured 2026-09-02, re-verified 2026-09-04. Crossref DOI-prefix counts use
-`https://api.crossref.org/prefixes/<prefix>/works?rows=0` and read `message.total-results`.
-A deliberately bogus prefix (`10.99999`) returns an **error, not a zero** — so a numeric answer from
-that endpoint is meaningful. [API, negative control, 2026-09-04]
-
-## 5. SciPost
-
-- **URL:** https://scipost.org/ · **Operator:** SciPost Foundation (Netherlands) · **DOI prefix:**
-  `10.21468`
-- **Model:** genuine diamond open access — no author charges, no reader charges, **public referee
-  reports with named or anonymous referees, and public author replies**. Physics-dominant, with
-  chemistry, astronomy and computational-science sections.
-- **Size: 12,558 registered DOIs** [API] Crossref prefix `10.21468`, 2026-09-04. That figure
-  includes journal articles, reports and versions, so it is an upper bound on articles.
-- **Reachability [WEB, 2026-09-04]: `scipost.org` is behind an Anubis proof-of-work challenge.**
-  `https://scipost.org/` and `https://scipost.org/api/` both return **HTTP 200 with a 3,903-byte
-  Anubis body** (`<title>Making sure you're not a bot!</title>`, `anubis_challenge` JSON,
-  `algorithm: fast, difficulty: 4`). Same vendor as CDS (§4.4), different body size. The Crossref
-  route above is therefore the only unauthenticated way to size SciPost from a script.
-- **Relevance here:** the closest thing to a working *diamond OA + open referee report* journal.
-  Almost no direct hardware content, but the governance model is the one every "reform scholarly
-  publishing" argument points at.
-
-## 6. Open Research Europe (ORE)
-
-- **URL:** https://open-research-europe.ec.europa.eu/ · **Operator:** European Commission, published
-  on F1000Research's platform (**DOI prefix `10.12688`**, shared with all F1000 properties)
-- **Model:** publish-then-review. Horizon Europe / Horizon 2020 grantees post; open peer review
-  follows; the article is indexed once it passes.
-- **Size — and a conflict this pass could not resolve:**
-
-  | Measurement | Value | Evidence |
-  |---|---:|---|
-  | Crossref `container-title:"Open Research Europe"` | **2,437** | [API] 2026-09-04 |
-  | Crossref, restricted to `type:journal-article` | **2,437** | [API] 2026-09-04 |
-  | DOIs harvested under `10.12688/openreseurope` | **2,430** | [API] 2026-09-02 |
-  | Figure reported by a sibling record in this pass | **1,513** | [see caveat] |
-
-  **The 1,513 does not reproduce.** Two independent 2026-09-02/04 measurements land at 2,430–2,437.
-  The most likely explanation is that 1,513 counted *indexed/approved* articles while the Crossref
-  figures count every registered DOI including awaiting-peer-review versions and revisions — but
-  that explanation was **not confirmed**. Both readings are recorded; **1,513 is [NOT-VERIFIED]**
-  and should not be carried forward without re-measurement.
-- **Reachability:** front page HTTP 200, **55,677 bytes** [WEB, 2026-09-04]. See the trap in §8.
-- **Relevance:** small but growing; EU-funded engineering and computing does appear. The Europe PMC
-  route (`PUBLISHER:"Open Research Europe"`) returned **hitCount 0**, so Europe PMC is *not* a valid
-  index for ORE — a live negative worth recording [API, 2026-09-04].
-
-## 7. Peer Community In (PCI) and PCI Registered Reports — the *overlay* model
-
-- **URL:** https://peercommunityin.org/ · **DOI prefix:** `10.24072` · **Size: 3,975 registered
-  DOIs** [API] Crossref, 2026-09-04 · front page HTTP 200, 225,655 B [WEB, 2026-09-04]
-
-**PCI is not a preprint server, and this is the single most commonly misunderstood entry in this
-whole document.** It hosts nothing. It is an **overlay**: a network of ~20 thematic communities
-(PCI Evolutionary Biology, PCI Ecology, PCI Registered Reports, PCI Math & Comp Sci, …) that
-organise peer review of preprints **that live somewhere else** — on bioRxiv, on OSF, on Zenodo, on
-arXiv.
-
-The mechanism:
-
-1. An author deposits the preprint on a real server and gets a real DOI there.
-2. The author submits *the DOI*, not the file, to a PCI community.
-3. A PCI recommender (an editor) organises real referee reports.
-4. If it passes, PCI publishes a **Recommendation** — a short, citable, DOI'd editorial endorsement
-   under `10.24072` — plus the full referee reports and author replies, all public.
-5. **The preprint never moves.** It stays on bioRxiv/Zenodo/arXiv, now carrying a badge that says a
-   named editor and named referees signed off.
-
-**Why this matters structurally:** it decouples *hosting* from *certification*. A server gives you a
-timestamp; PCI gives you the peer-review layer, separately, on top, without a journal. **PCI
-Registered Reports** goes further: it reviews the *protocol* before the data are collected — in-
-principle acceptance — which is the strongest available defence against p-hacking and HARKing, and
-it applies equally well to a benchmarking methodology as to a clinical trial.
-
-Consequences for anyone counting things: **3,975 PCI DOIs do not represent 3,975 hosted documents.**
-They represent recommendations and reviews *about* documents held elsewhere. Adding PCI's count to a
-sum of preprint-server sizes double-counts. This is the same error as summing SSRN networks, or
-treating ScienceOpen's index as its holdings. [INF]
-
-## 8. VeriXiv
-
-- **URL:** https://verixiv.org/ · **Operator:** on the F1000Research/Gates Foundation platform,
-  DOI prefix `10.12688/verixiv` · **Focus:** Gates-funded global-health research, with an explicit
-  **integrity-check gate** before posting (image forensics, plagiarism, data availability).
-- **Size: 812 records** [API] Europe PMC `PUBLISHER:"VeriXiv"`, 2026-09-04. Europe PMC's negative
-  control (`PUBLISHER:"ZZQQNotAPublisher"`) returns `hitCount 0`, so the endpoint is truthful.
-- Sample record from the 2026-09-02 harvest [API]: `PPR1310064`,
-  `10.12688/verixiv.3676.1`, *"Extrusion Cooking Enhances the Shelf Life of Grain Amaranth…"*,
-  `pubYear 2026`, `firstPublicationDate 2026-09-01`, `versionNumber 1`, **`isOpenAccess: "N"`,
-  `hasPDF: "N"`** — i.e. Europe PMC indexes the metadata but does not hold the full text.
-- **Probing trap — the identical-shell problem, again.** `https://verixiv.org/` and
-  `https://open-research-europe.ec.europa.eu/` both return **HTTP 200 and exactly 55,677 bytes**
-  [probe ×2, 2026-09-04]. They are the same F1000/ARPHA SPA shell rendered under two brands. **Byte
-  size cannot distinguish these two sites, let alone distinguish a real page from a missing one.**
-  Add to the family that already contains `osf.io` (4,207 B) and `unpaywall.org` (1,421 B).
-- **Relevance to computing: essentially nil.** Listed because it is a recent, real, *missing* entry
-  and because of the shell trap.
-
-## 9. Advance (SAGE) — probably moribund, and here is why that is hard to prove
-
-- **URL:** https://advance.sagepub.com/ · **Operator:** SAGE Publishing · **DOI prefix:** `10.31124`
-  · social sciences and humanities.
-- **Front door: HTTP 403.** Body sizes **5,388 bytes** (`curl/8.21.0`), **5,623 bytes** (Chrome UA),
-  **5,388 bytes** (`WhatsApp/2.23.20.0`) [probe ×3, 2026-09-04]. **This is the ~5.6 kB Cloudflare
-  challenge signature.** Per this repository's own rule: **blocked, not broken.** A 403 here is
-  evidence about Cloudflare, not about SAGE.
-- **So go around it.** Crossref knows what SAGE has registered:
-
-  | Measurement | Value | Evidence |
-  |---|---|---|
-  | Total DOIs under `10.31124` | **4,417** | [API] Crossref, 2026-09-04 |
-  | **Most recent deposit** | **2026-04-21T16:11:19Z** | [API] Crossref `sort=created&order=desc`, 2026-09-04 |
-  | Titles of the three newest | *"Geopolitical Tightrope in Taiwan…"*, *"Political Change and Smallholder farming…"*, *"Gender Equality in Cambodian Higher Education…"* | [API] 2026-09-04 |
-
-- **Verdict: dormant, not confirmed dead.** All three newest DOIs were created in the *same
-  second*, which is a batch deposit, and **nothing has been registered in the four and a half
-  months since**. That is a strong signal for a server that was posting continuously. But a
-  Cloudflare-blocked front door plus a deposit gap is not a closure announcement. **Status:
-  [NOT-VERIFIED] as closed; recorded as dormant with the evidence above.** Anyone with a browser
-  should check the front page and, if it is live, correct this line.
-
-## 10. Cambridge Open Engage — alive, and busier than before
-
-- **URL:** https://www.cambridge.org/engage/coe/ · **Operator:** Cambridge University Press ·
-  **DOI prefix:** `10.33774`
-- **Size: 5,738 registered DOIs** [API] Crossref, 2026-09-04.
-- **Most recent deposit: 2026-09-04T05:50:58Z** — *hours* before the probe [API]. The three newest:
-  `10.33774/coe-2026-zl7cd`, `10.33774/coe-2026-0bntp`, `10.33774/apsa-2025-l4d92-v4` [API].
-- **This settles a question raised elsewhere in this directory.** Per
-  [`chemrxiv.md`](chemrxiv.md), **ChemRxiv left the Cambridge Open Engage platform again in January
-  2026.** The obvious worry was that COE would collapse without its largest tenant. It did not:
-  COE was registering new DOIs on the morning of the probe, and the `apsa-` slug in the third row
-  shows it is still hosting partner communities (APSA Preprints). **Alive.**
-- Note the platform's public REST path is *not* the ChemRxiv one:
-  `…/engage/api-gateway/coe/public-api/v1/items` returns `Cannot GET` [probe, 2026-09-04], and the
-  equivalent ChemRxiv endpoint now returns a **Cloudflare "Just a moment…" interstitial**
-  [probe, 2026-09-04]. Crossref remains the reliable measurement route for both.
-- **Relevance to computing:** low. Listed because it is platform infrastructure under several
-  branded servers, and because its survival after ChemRxiv's exit is a durability data point.
-
-## 11. J-STAGE
-
-- **URL:** https://www.jstage.jst.go.jp/ · **Operator:** Japan Science and Technology Agency (JST)
-- **What it is:** the national electronic platform for Japanese scholarly societies — well over
-  3,000 journals, including the **IEICE Transactions** (Electronics / Communications / Information
-  and Systems) and **IPSJ** titles. Much of it is free to read; a lot of it is **in Japanese only**
-  and is invisible to English-language search.
-- **Why it is here:** for anyone doing device physics, semiconductor process, communications or
-  signal processing, J-STAGE holds a large body of work that has **no arXiv copy and no Western
-  mirror**. It is the single biggest blind spot in an English-only literature search in electronics.
-- **Reachability:** browse page HTTP 200, 86,304 B [WEB, 2026-09-04]. **The OAI-PMH handler at
-  `/oai/OAIHandler?verb=Identify` returned HTML, not XML** [probe, 2026-09-04] — so the endpoint
-  either moved or is gated. **No total record count was obtained: [NOT-VERIFIED].** J-STAGE does
-  publish a WebAPI requiring registration, which this pass did not use.
-- **Honest caveat:** J-STAGE is a *journal* platform, not a preprint server. It is included because
-  the omission that matters is not "preprints" but "where the electronics literature actually is".
-
-## 12. KISTI ScienceON
-
-- **URL:** https://scienceon.kisti.re.kr/ · **Operator:** Korea Institute of Science and Technology
-  Information (KISTI), a government research institute
-- **What it is:** Korea's national aggregator — journal articles, **patents**, reports, theses,
-  research data and Korean-language technical literature, over a domestic corpus that is largely
-  absent from Scopus and Web of Science.
-- **Reachability:** the bare root returns **HTTP 200 with a 217-byte body** — a JS bootstrap, not
-  content. `https://scienceon.kisti.re.kr/main/mainForm.do` returns **HTTP 200, 336,305 B**, an
-  `lang="KO"` page [probe ×2, 2026-09-04]. **Another 200-means-nothing case: 217 bytes of shell.**
-- **Size: [NOT-VERIFIED].** No unauthenticated count endpoint was found. KISTI operates an OpenAPI
-  behind a key.
-- **Honest caveat:** most content is Korean-language and a meaningful share is **abstract-only or
-  paywalled** to non-Korean users. Useful for *knowing a paper exists*; frequently not useful for
-  reading it.
-
-## 13. SSOAR
-
-- **URL:** https://www.ssoar.info/ · **Operator:** GESIS – Leibniz Institute for the Social Sciences
-- **What it is:** Social Science Open Access Repository. Green OA, mostly German-language social
-  science, DSpace-based.
-- **Size: 101,200 records** [API] OAI-PMH `verb=ListIdentifiers&metadataPrefix=oai_dc`,
-  `completeListSize` read from the `resumptionToken`, harvested 2026-09-02. The 2026-09-04 re-probe
-  of the same endpoint returned no `completeListSize` on the first page, so the figure is carried
-  from the 2026-09-02 harvest only.
-- Sets are DSpace community/collection ids (`com_community_1`, `com_community_10000`, …) [API].
-- **Reachability:** front page HTTP 200, 24,461 B [WEB, 2026-09-04]. No bot wall observed.
-- **Relevance to computing: none.** Listed for completeness — it is a large, well-run, genuinely
-  open repository that Wikipedia's list omits while listing much smaller social-science servers.
-
----
-
-# TIER 3 — layers, indexes, and things that look like servers
-
-## 14. Overlays, indexes and one shutdown
-
-None of these hosts original literature. All of them will be mistaken for a repository by someone.
-
-### 14.1 alphaXiv
-
-- `https://alphaxiv.org/` **301 → `https://www.alphaxiv.org/`**, HTTP 200, 627,924 B, title
-  *"Explore | alphaXiv"* [probe, 2026-09-04].
-- `https://www.alphaxiv.org/abs/2312.00752` → HTTP 200, 239,067 B, title *"Mamba: Linear-Time
-  Sequence Modeling with Selective State Spaces | alphaXiv"* [probe, 2026-09-04].
-- **What it is:** a discussion and annotation layer over arXiv — swap `arxiv.org` for `alphaxiv.org`
-  in a URL and you get the same paper with a comment thread and AI tooling attached. **Hosts
-  nothing.** Same category error as Synthical (see [`synthical.md`](synthical.md)); the difference
-  is that alphaXiv was reachable and functioning on the probe date and Synthical was not.
-
-### 14.2 ar5iv
-
-- `https://ar5iv.labs.arxiv.org/html/1706.03762` → HTTP 200, **167,302 B**, title
-  *"[1706.03762] Attention Is All You Need"* [probe, 2026-09-04].
-- **Negative control:** `…/html/9999.99999` → **HTTP 404, 2,475 B**. Honest 404 [probe, 2026-09-04].
-- **What it is:** an arXiv Labs service that renders arXiv LaTeX source to **HTML5**. Not a
-  repository — a *format converter* over arXiv's own holdings. It is genuinely useful for two
-  things: reading papers on a phone, and **machine-parsing equations and tables** without going
-  through PDF extraction. If you are building a pipeline over arXiv content, ar5iv HTML beats PDF.
-
-### 14.3 Hugging Face Papers
-
-- `https://huggingface.co/papers` → HTTP 200, 314,513 B [probe, 2026-09-04].
-- `…/papers/1706.03762` → HTTP 200, 292,900 B, *"Paper page - Attention Is All You Need"*.
-- `…/papers/2312.00752` → HTTP 200, 285,472 B, *"Paper page - Mamba: …"*.
-- **Negative control:** `…/papers/9999.99999` → **HTTP 404, 52,935 B**. Honest 404 [probe ×3,
-  2026-09-04].
-- **What it is:** a curated daily feed and discussion page over arXiv ML papers, cross-linked to
-  models, datasets and Spaces on the same platform. **Hosts no papers.** Its real value is the
-  **link from paper to running artifact** — the weights and the demo, not the PDF.
-
-### 14.4 Papers with Code — **shut down; the data survived**
-
-This is the durability finding of Tier 3, and it is verified.
-
-| Probe | Result | Date |
-|---|---|---|
-| `https://paperswithcode.com/` | **HTTP 302 → `https://huggingface.co/papers/trending`**, final 200, 1,507,368 B, title *"Trending Papers - Hugging Face"* | 2026-09-04 |
-| `https://huggingface.co/api/datasets/pwc-archive/papers-with-abstracts` | **HTTP 200**, `lastModified 2026-08-17T10:40:27Z`, 690 downloads, `private: false` | 2026-09-04 |
-| `https://huggingface.co/api/datasets/pwc-archive/links-between-paper-and-code` | **HTTP 200**, `lastModified 2025-09-10T12:20:22Z` | 2026-09-04 |
-| `…/pwc-archive/evaluation-tables` | HTTP 200 | 2026-09-04 |
-| `…/pwc-archive/methods` | HTTP 200 | 2026-09-04 |
-| `…/pwc-archive/datasets` | HTTP 200 | 2026-09-04 |
-
-**What happened.** Papers with Code — the paper↔code↔leaderboard index that a decade of ML work was
-navigated through — **no longer exists as an independent site.** Its domain now redirects to
-Hugging Face's trending-papers page. Meta had acquired it via Facebook AI Research; Hugging Face
-absorbed the front-end function.
-
-**Where the data went.** The project's own dataset README, harvested 2026-09-02 [DOC], now points
-all five bulk dumps at the **`pwc-archive` organisation on Hugging Face**:
-
-- `pwc-archive/papers-with-abstracts`
-- `pwc-archive/links-between-paper-and-code`
-- `pwc-archive/evaluation-tables`
-- `pwc-archive/methods`
-- `pwc-archive/datasets`
-
-All five resolve HTTP 200 and are public [API, 2026-09-04]. Licence is stated as **CC-BY-SA 4.0**
-[DOC]. The same README still says *"At the moment, data is regenerated daily"* — **that sentence is
-now false**: `links-between-paper-and-code` was last modified **2025-09-10**, a year before the
-probe. It is an **archive**, not a live feed.
-
-**The lesson, which is the reason this record exists.** A widely-used, well-funded, corporate-backed
-research index disappeared, and the *only* reason its corpus is still retrievable is that somebody
-deliberately mirrored the bulk dumps to a third-party platform under an open licence. The website
-died; the CC-BY-SA dumps did not. **Bulk dumps under an open licence are what durability actually
-looks like** — which is precisely why the presence or absence of a bulk dump is a column in the
-table in §15.
-
-### 14.5 Semantic Scholar / S2ORC
-
-- **URL:** https://www.semanticscholar.org/ · API `https://api.semanticscholar.org/graph/v1/`
-- **What it is:** AI2's corpus and citation graph over ~200 M papers, with **S2ORC** (the Semantic
-  Scholar Open Research Corpus) as the full-text-and-parsed-references bulk product used for
-  training and for citation-context analysis. Not a repository — an *index with parsed full text
-  where licensing permits*.
-- **Probe result: HTTP 429 `Too Many Requests`** on `graph/v1/paper/search`, and **HTTP 500** on
-  `graph/v1/paper/search/bulk`, both unauthenticated [probe ×2, 2026-09-04]. **Blocked/broken, not
-  absent — no count obtained: [NOT-VERIFIED].** The documented fix is a free API key; this pass did
-  not apply for one. The 429 body links the key request form, which is a well-behaved way to be
-  refused.
-
-### 14.6 NASA ADS
-
-- **URL:** https://ui.adsabs.harvard.edu/ (HTTP **202**, empty body [probe, 2026-09-04]) · API
-  `https://api.adsabs.harvard.edu/v1/`
-- **Probe result:** `v1/search/query?q=FPGA` returns **HTTP 401 `Missing "Authorization" in
-  headers`** [probe, 2026-09-04]. **An API token is mandatory.** No count obtained:
-  **[NOT-VERIFIED]**.
-- **Why it is here anyway:** ADS is the astrophysics literature system, and astrophysics is a
-  *hardware* discipline — detector arrays, cryogenic readout, CCD/CMOS sensor characterisation,
-  radio-telescope DSP and correlator design, spaceflight electronics. ADS indexes instrumentation
-  papers and observatory technical reports that INSPIRE does not.
-
-### 14.7 dblp — metadata only, and the canonical CS bibliography
-
-- **URL:** https://dblp.org/ · **Operator:** Schloss Dagstuhl – Leibniz-Zentrum für Informatik
-- **What it is:** the computer-science bibliography. **No abstracts, no full text, no PDFs** — just
-  author-disambiguated, editorially curated bibliographic records for essentially every CS
-  conference and journal that matters. It is the tool for answering *"did this preprint ever get
-  published, and where?"*, which is step 3 of the ECCC sanity-check in §1.10.
-
-**Size, by publication type** [API] parsed from the operator's own *Records in DBLP* statistics
-export (`dblp.org/statistics/recordsindblp.html`, CSV download), harvested 2026-09-02, page
-regenerated `03/09/2026 05:24:20`:
-
-| Type | Records |
-|---|---:|
-| `INPROCEEDINGS` (conference papers) | **3,949,286** |
-| `ARTICLE` (journal papers) | **3,482,111** |
-| `INFORMAL` (**preprints — mostly arXiv**) | **974,897** |
-| `BOOK` | 177,401 |
-| `EDITOR` | 67,532 |
-| `INCOLLECTION` | 55,879 |
-| `DATA` | 26,738 |
-| `REFERENCE` | 14,279 |
-| `WITHDRAWN` | **289** |
-| **Total** | **8,748,412** |
-
-Two things to notice. **`INFORMAL` = 974,897** is dblp counting *preprints* as a first-class
-publication type — that is dblp's own measure of how large the CS preprint literature has become,
-and it is broadly consistent with arXiv's `cs` count of 931,100 in [`arxiv.md`](arxiv.md).
-**`WITHDRAWN` = 289** is dblp tracking retractions explicitly, which almost nothing else in this
-survey does.
-
-**Bulk retrieval.** dblp publishes the entire database as **one gzipped XML file**,
-`https://dblp.org/xml/dblp.xml.gz`, with its DTD alongside, under **CC0** — no registration, no
-rate limit, no API key. That single file is the reason dblp is durable in the sense §14.4 defines:
-thousands of independent copies exist. There is also an **RDF dump**, a **SPARQL endpoint**, and a
-REST search API (`https://dblp.org/search/publ/api?q=<query>&format=json&h=<n>`).
-
-**Reachability on the probe date — dblp was in trouble** [probe, 2026-09-04]:
-
-| Probe | Result |
-|---|---|
-| `dblp.org/search/publ/api?q=RISC-V` | Failed twice with a non-JSON body, **succeeded on the third attempt: `@total` = 2,313** |
-| `dblp.org/xml/dblp.xml.gz` | **HTTP 503**, 107-byte body |
-| `dblp.uni-trier.de/search/publ/api` | **HTTP 500** (30,521 B error page) |
-| `dblp.dagstuhl.de/search/publ/api` | **HTTP 503**, "No server is available to handle this request" |
-| `dblp.uni-trier.de/xml/dblp.xml.gz` | **HTTP 503** |
-| `dblp.dagstuhl.de/xml/dblp.xml.gz` | **HTTP 503** |
-
-The operator's own statistics page carries two banners that explain it: *"Due to maintenance work,
-this server will become temporarily unavailable during the next hour(s)"* and *"Over the past few
-days, you may have noticed significant server instability across all dblp servers… there may still
-be extended downtime on all dblp servers in the coming days."* [DOC, 2026-09-02].
-
-**This is a transient outage, not a closure — and it is a nice illustration of the difference.**
-All three mirrors were down for the XML dump simultaneously; the API answered on retry. Anyone
-harvesting dblp should **retry with backoff and treat 503 as transient**, and should not conclude
-anything from a single failed request. The `RISC-V` query result also shows dblp normalising the
-query to `RISC* V` — hyphen handling again, the same class of issue flagged for Zenodo in the index.
-
----
-
-## 15. Status and size table, with probe dates
-
-Every row below was probed on the stated date(s). "Bulk dump" is called out because §14.4 shows it
-is the single best predictor of whether a corpus survives its host.
-
-| # | Server | Kind | Measured size | Metric | Evidence | Probe date(s) | Status | Open bulk dump? |
-|---|---|---|---:|---|---|---|---|---|
-| 1 | **ECCC** | repository | **4,832** | reports, 1994→ | [API] 33 year-index pages | 2026-09-02, 2026-09-04 | **active** | ✗ (no OAI, no API, no dump) |
-| 2 | **OpenReview** | review platform | **4,634** | venue entries | [API] `groups?id=venues` | 2026-09-02 (4,621), 2026-09-04 (4,634) | **active, API challenge-gated** | ✗ |
-| 3 | **ACL Anthology** | archive | **131,040** | BibTeX entries, 1952→ | [API] `anthology.bib.gz` parsed | 2026-09-02 (131,027), 2026-09-04 | **active** | ✓ **12.6 MB, one file** |
-| 4 | **INSPIRE-HEP** | index + repository | **1,882,844** | literature records | [API] `/api/literature` | 2026-09-02 (1,882,221), 2026-09-04 | **active** | ✓ (API, unrestricted) |
-| 5 | **CERN Document Server** | institutional repo | **578,928** total / **316,404** full text | OAI records | [API] OAI `completeListSize` | 2026-09-04 | **active; HTML+REST behind Anubis, OAI open** | ✓ (OAI-PMH) |
-| 6 | **SciPost** | diamond OA journal | **12,558** | Crossref DOIs, prefix `10.21468` | [API] Crossref | 2026-09-04 | **active; site behind Anubis** | ✗ (site gated) |
-| 7 | **Open Research Europe** | publish-then-review | **2,437** (Crossref) / 2,430 (DOI harvest) | works | [API] Crossref | 2026-09-02, 2026-09-04 | **active** | ✗ |
-| 8 | **Peer Community In** | **overlay, hosts nothing** | **3,975** | Crossref DOIs, prefix `10.24072` | [API] Crossref | 2026-09-04 | **active** | ✗ |
-| 9 | **VeriXiv** | repository | **812** | Europe PMC records | [API] Europe PMC | 2026-09-02, 2026-09-04 | **active** | ✗ |
-| 10 | **Advance (SAGE)** | repository | **4,417** | Crossref DOIs, prefix `10.31124` | [API] Crossref | 2026-09-04 | **dormant** — no deposit since **2026-04-21**; front door Cloudflare 403 | ✗ |
-| 11 | **Cambridge Open Engage** | platform | **5,738** | Crossref DOIs, prefix `10.33774` | [API] Crossref | 2026-09-04 | **active** — newest DOI **2026-09-04 05:50Z** | ✗ |
-| 12 | **J-STAGE** | journal platform | *not measured* | — | [WEB] front page 200, 86,304 B | 2026-09-04 | **active**; OAI handler returned HTML | ✗ (WebAPI needs registration) |
-| 13 | **KISTI ScienceON** | national aggregator | *not measured* | — | [WEB] `mainForm.do` 200, 336,305 B | 2026-09-04 | **active**; root is a 217-byte JS shell | ✗ (OpenAPI needs key) |
-| 14 | **SSOAR** | repository | **101,200** | OAI records | [API] OAI `completeListSize` | 2026-09-02 | **active** | ✓ (OAI-PMH) |
-| 15 | **alphaXiv** | **overlay on arXiv** | hosts nothing | — | [WEB] 200, 627,924 B | 2026-09-04 | **active** | n/a |
-| 16 | **ar5iv** | **LaTeX→HTML renderer** | hosts nothing | — | [WEB] 200, 167,302 B; bogus id → true 404 | 2026-09-04 | **active** | n/a |
-| 17 | **Hugging Face Papers** | **feed over arXiv** | hosts nothing | — | [WEB] 200, 314,513 B; bogus id → true 404 | 2026-09-04 | **active** | n/a |
-| 18 | **Papers with Code** | index | — | — | [probe] 302 → `huggingface.co/papers/trending` | 2026-09-04 | **SHUT DOWN**; data at `hf.co/datasets/pwc-archive/*` (5 datasets, all HTTP 200) | ✓ **CC-BY-SA, mirrored** |
-| 19 | **Semantic Scholar / S2ORC** | index + corpus | *not measured* | — | [probe] HTTP **429** / **500** unauthenticated | 2026-09-04 | **active, rate-limited** | ✓ (S2ORC, needs key) |
-| 20 | **NASA ADS** | index | *not measured* | — | [probe] HTTP **401**, token mandatory | 2026-09-04 | **active, token-gated** | ✓ (API, needs token) |
-| 21 | **dblp** | **bibliography, metadata only** | **8,748,412** (incl. **974,897** preprints, **289** withdrawn) | records | [API] operator statistics export | 2026-09-02 (page built 2026-09-03) | **active but unstable** — all 3 mirrors 503 on the dump; API OK on 3rd retry | ✓ **`dblp.xml.gz`, CC0** — when it serves |
-
-### Probing-trap summary for these servers
-
-Additions to the index's [§ Probing traps](README.md#6-probing-traps):
-
-| Server | Trap | Correct test |
-|---|---|---|
-| **ECCC** | Soft-404: **HTTP 200** + **17,041 B** for any nonexistent path (`/about/`, `/report/1994/999/`); **17,032 B** for a nonexistent year | Body size, or grep the title for `404 page not found` |
-| **OpenReview** | Under the challenge regime, `forum?id=<real>` and `forum?id=ZZZZZZZZZZ` both return **HTTP 200, 4,787 B** | Authenticate (`openreview-py`), or do not test existence at all |
-| **OpenReview** | Per-venue `count` **caps at 10,000** — ICLR 2025 and 2026 both read exactly `10000` | Paginate with `offset`; never trust a round `count` |
-| **CDS** | **Anubis** challenge served with **HTTP 200**, ~7.5 kB body, on HTML *and* REST. UA rotation does not help | Use OAI-PMH at `/oai2d` — completely open |
-| **SciPost** | Same Anubis wall, **HTTP 200**, **3,903 B**, on the site *and* `/api/` | Crossref prefix `10.21468` |
-| **Advance (SAGE)** | **HTTP 403**, 5,388–5,623 B = Cloudflare. **Blocked, not broken** | Crossref prefix `10.31124` + `sort=created&order=desc` for liveness |
-| **VeriXiv / ORE** | Return **HTTP 200 and byte-identical 55,677 B** — same F1000 SPA shell under two brands | Crossref / Europe PMC |
-| **KISTI ScienceON** | Root returns **HTTP 200, 217 B** — a JS bootstrap, not content | Request `/main/mainForm.do` |
-| **dblp** | All three mirrors returned **503** for `dblp.xml.gz` simultaneously; the API failed twice then worked | Retry with backoff; 503 here is transient, not closure |
-| **Crossref prefix endpoint** | *Positive* note: a bogus prefix (`10.99999`) returns an **error, not `0`** — so a number from `/prefixes/<p>/works?rows=0` is trustworthy | — |
-| **Well-behaved (use as controls)** | **ACL Anthology** (true 404), **INSPIRE** (`total: 0`), **ar5iv** (true 404), **Hugging Face Papers** (true 404), **CDS OAI** (`noRecordsMatch`), **Europe PMC** (`hitCount: 0`) | — |
-
----
-
-## 16. What is still missing
-
-Stated so the gaps are visible rather than silent. This section is the honest counterpart to §15.
-
-### 16.1 Numbers this pass could not obtain
-
-| Wanted | Why not |
-|---|---|
-| **ICLR / NeurIPS true submission counts** | The API went behind a browser challenge between probe dates, and the harvested `count` values cap at 10,000. **The entire table in §2.3 is order-of-magnitude only.** |
-| **OpenReview total note count** | Same cause. Never measured. |
-| **ECCC rejection rate** | Unpublished. Not on the site, not in the three papers the operator cites about itself. |
-| **ECCC eventual-publication rate** | No measurement found in the literature; this pass did not sample for one. |
-| **J-STAGE record count** | OAI handler returned HTML; the WebAPI requires registration. |
-| **KISTI ScienceON record count** | OpenAPI requires a key. |
-| **Semantic Scholar / S2ORC corpus size** | HTTP 429 unauthenticated; needs a free API key not obtained. |
-| **NASA ADS record count and `FPGA` hit count** | HTTP 401; token mandatory. |
-| **CDS `cerncds:cs` set size** | The set is listed by `ListSets` but returned no `completeListSize`. |
-| **SSOAR re-verification** | The 101,200 figure is from 2026-09-02 only; the 2026-09-04 re-probe did not return `completeListSize` on the first page. |
-| **ECCC keyword→report counts** | 382 keyword pages exist; none were individually sized. |
-| **Whether Advance (SAGE) is formally closed** | Front door is Cloudflare-blocked. Dormancy is evidenced (§9); closure is not. |
-
-### 16.2 Conflicts recorded but not resolved
-
-- **ORE: 1,513 vs 2,437.** A sibling record in this pass reports 1,513; two independent
-  measurements here give 2,430–2,437. The likely explanation (approved articles vs all registered
-  DOIs) was **not confirmed**. Both stand.
-- **ECCC's own two removal policies contradict each other.** `/static/colloquium/how_to_use/` says
-  a posted report *"cannot be removed"*; `/static/colloquium/copyright_notice/` says the author
-  *"may withdraw the paper… iff the paper is accepted for publication elsewhere"*. Both live on
-  2026-09-04.
-- **ECCC total: 4,831 (2026-09-02) vs 4,832 (2026-09-04).** Recorded, not reconciled — the
-  difference is one new report.
-- **Papers with Code's README says data is "regenerated daily".** The dataset `lastModified`
-  timestamps (2025-09-10, 2026-08-17) say otherwise. The README is stale.
-
-### 16.3 Things not attempted at all
-
-- **No landmark-paper verification outside ECCC.** §1.6 fetched and title-checked eleven ECCC
-  reports individually. Nothing comparable was done for OpenReview, the ACL Anthology, CDS or
-  INSPIRE. The Mamba example in §2.5 is verified [API] but is one paper.
-- **No CDS or INSPIRE bulk harvest.** Set sizes were read from `completeListSize`; no records were
-  actually pulled, so no claim is made about record quality or full-text availability per set.
-- **No hardware-specific corpus analysis.** The INSPIRE keyword counts in §4.1 (`FPGA` 5,380,
-  `ASIC` 2,869, `"radiation hard"` 1,932) are raw full-text search hits with **no de-duplication,
-  no false-positive check and no negative control on the query terms themselves**. Treat them as
-  evidence that the material exists, not as measurements of how much.
-- **No eventual-publication rate for anything in this record.**
-- **No licence audit.** Licensing statements in §1.9, §3.3, §14.4 are from operator pages; no
-  per-record sampling was done.
-- **Wikipedia's list was not re-read during this pass.** The "absent from Wikipedia's list" claims
-  rest on the [index](README.md)'s enumeration of the 65 entries, not on a fresh check of the live
-  article. Marked **[INF]**.
-
-### 16.4 Servers deliberately not covered
-
-Named so the next pass knows they were considered:
-
-- **arXiv-adjacent overlay journals** (Discrete Analysis, SIGMA, Quantum) — real journals over
-  arXiv, but journals, not repositories.
-- **PubPeer** — post-publication comment layer; adjacent to §7's overlay logic but not a host.
-- **CiteSeerX, CORE, BASE, OpenAIRE, OpenAlex** — aggregators/indexes. OpenAlex in particular is
-  large enough to deserve its own record and did not get one.
-- **National repositories** other than the three here (SSOAR, KISTI, J-STAGE): CNKI, Wanfang,
-  CiNii, RePEc-adjacent national systems.
-- **Institutional repositories generally** — DSpace/EPrints installations number in the thousands
-  and are out of scope.
-- **GitHub, GitLab, Zenodo software records** — covered in [`zenodo.md`](zenodo.md).
-
----
-
-## 17. Sources
-
-Primary evidence for this record is machine-readable and was retrieved on 2026-09-02 and
-re-verified on 2026-09-04. Raw output is under
-[`../../scratch/preprint-repositories/missing-servers/`](../../scratch/preprint-repositories/missing-servers/).
-
-| # | URL | Retrieved | Supports |
-|---|---|---|---|
-| S1 | `https://eccc.weizmann.ac.il/year/<1994..2026>/` | 2026-09-02, 2026 re-verified 2026-09-04 | §1.3 per-year counts, §1.6 title scan |
-| S2 | `https://eccc.weizmann.ac.il/report/<YYYY>/<NNN>/` (×11) | 2026-09-04 | §1.6 landmark verification, §1.5 revisions |
-| S3 | `https://eccc.weizmann.ac.il/colloquium/call_for_papers/` | 2026-09-04 | §1.4 scope and editorial criteria |
-| S4 | `https://eccc.weizmann.ac.il/colloquium/scientific_board/` | 2026-09-04 | §1.4 editorial board |
-| S5 | `https://eccc.weizmann.ac.il/static/colloquium/how_to_use/` | 2026-09-04 | §1.5 revision/withdrawal semantics |
-| S6 | `https://eccc.weizmann.ac.il/static/colloquium/copyright_notice/` | 2026-09-04 | §1.9 licensing |
-| S7 | `https://eccc.weizmann.ac.il/static/colloquium/read_more/` | 2026-09-04 | §1.1 institutional history and [LIT] citations |
-| S8 | `https://eccc.weizmann.ac.il/robots.txt`, `/feeds/reports/`, `/keywords/` | 2026-09-04 | §1.8 access surface |
-| S9 | `https://api2.openreview.net/groups?id=venues` | 2026-09-02, 2026-09-04 | §2.2 venue counts |
-| S10 | `https://api2.openreview.net/notes?forum=AL1fq05o7H` | 2026-09-02 | §2.5 Mamba reviews and scores |
-| S11 | `https://api2.openreview.net/notes?...` (v1 and v2) | 2026-09-02 | §2.3 per-venue counts (caveated) |
-| S12 | `https://openreview.net/forum?id=…`, `/pdf?id=…`, UA rotation ×6 | 2026-09-04 | §2.6 challenge blackout |
-| S13 | `https://aclanthology.org/anthology.bib.gz` | 2026-09-02, 2026-09-04 | §3.2 size, types, per-year growth |
-| S14 | `https://aclanthology.org/N19-1423/`, `.pdf`, `Z99-9999/` | 2026-09-04 | §3.3 access + negative control |
-| S15 | `https://inspirehep.net/api/literature/…` and `/api/{conferences,jobs,institutions,data,experiments}` | 2026-09-02, 2026-09-04 | §4.1, §4.2 counts + negative control |
-| S16 | `http://cds.cern.ch/oai2d?verb=Identify` | 2026-09-02, 2026-09-04 | §4.3 policies, `earliestDatestamp` |
-| S17 | `http://cds.cern.ch/oai2d?verb=ListSets` | 2026-09-02 | §4.3 set inventory |
-| S18 | `http://cds.cern.ch/oai2d?verb=ListIdentifiers&set=…` (×9 + bogus) | 2026-09-04 | §4.3 set sizes + negative control |
-| S19 | `https://cds.cern.ch/api/records`, `/search` | 2026-09-02, 2026-09-04 | §4.4 Anubis trap |
-| S20 | `https://api.crossref.org/prefixes/{10.21468,10.31124,10.33774,10.24072,10.12688,10.99999}/works` | 2026-09-04 | §5–§11 sizes + negative control |
-| S21 | `https://api.crossref.org/prefixes/10.31124/works?sort=created&order=desc` | 2026-09-04 | §9 Advance dormancy |
-| S22 | `https://api.crossref.org/prefixes/10.33774/works?sort=created&order=desc` | 2026-09-04 | §10 Cambridge Open Engage liveness |
-| S23 | `https://api.crossref.org/works?filter=container-title:Open+Research+Europe` | 2026-09-04 | §6 ORE size conflict |
-| S24 | `https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=PUBLISHER:…` (×3) | 2026-09-04 | §6, §8 VeriXiv/ORE + negative control |
-| S25 | `https://www.ssoar.info/OAIHandler/request?verb=ListIdentifiers` | 2026-09-02 | §13 size |
-| S26 | `https://scipost.org/`, `/api/` | 2026-09-04 | §5 Anubis wall |
-| S27 | `https://advance.sagepub.com/` with UA ×3 | 2026-09-04 | §9 Cloudflare 403 |
-| S28 | `https://scienceon.kisti.re.kr/`, `/main/mainForm.do` | 2026-09-04 | §12 shell trap |
-| S29 | `https://www.jstage.jst.go.jp/browse/-char/en`, `/oai/OAIHandler` | 2026-09-04 | §11 reachability |
-| S30 | `https://paperswithcode.com/` (redirect chain) | 2026-09-04 | §14.4 shutdown |
-| S31 | `https://huggingface.co/api/datasets/pwc-archive/*` (×5) | 2026-09-04 | §14.4 data survival + staleness |
-| S32 | Papers with Code dataset README | 2026-09-02 | §14.4 dump list, CC-BY-SA licence |
-| S33 | `https://dblp.org/statistics/recordsindblp.html` + CSV export | 2026-09-02 (page built 2026-09-03) | §14.7 record counts |
-| S34 | `https://dblp.org/xml/dblp.xml.gz`, `dblp.uni-trier.de`, `dblp.dagstuhl.de` | 2026-09-04 | §14.7 outage |
-| S35 | `https://dblp.org/search/publ/api?q=RISC-V` | 2026-09-04 | §14.7 retry behaviour, query normalisation |
-| S36 | `https://ar5iv.labs.arxiv.org/html/{1706.03762,9999.99999}` | 2026-09-04 | §14.2 |
-| S37 | `https://huggingface.co/papers/{1706.03762,2312.00752,9999.99999}` | 2026-09-04 | §14.3 |
-| S38 | `https://www.alphaxiv.org/`, `/abs/2312.00752` | 2026-09-04 | §14.1 |
-| S39 | `https://api.semanticscholar.org/graph/v1/paper/search*` | 2026-09-04 | §14.5 rate limit |
-| S40 | `https://api.adsabs.harvard.edu/v1/search/query` | 2026-09-04 | §14.6 token requirement |
-| S41 | [LIT] Meinel & Klotz, *"The first 10 years of the ECCC digital library"*, CACM 49(1):131–134, 2006; Bern, Meinel & Sack, SIGDOC 1998:113–119; Bern, Damm & Meinel, ECDL 1997:405–421 | cited by S7 | §1.1 — **citations taken from the operator's page; the papers themselves were not retrieved** |
diff --git a/research/preprint-repositories/arxiv.md b/research/preprint-repositories/arxiv.md
deleted file mode 100644
index fdf1a90..0000000
--- a/research/preprint-repositories/arxiv.md
+++ /dev/null
@@ -1,1363 +0,0 @@
-# arXiv — preprint repository record
-
-- **URL:** https://arxiv.org/
-- **Operator:** arXiv (transitioning to an independent non-profit; hosted at Cornell Tech since 2001)
-- **Discipline scope:** physics, mathematics, computer science, quantitative biology, quantitative finance, statistics, electrical engineering & systems science, economics
-- **Launched:** 1991 · **Status:** active
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-arXiv is the oldest and largest open-access preprint server in the physical and
-computational sciences. A paper deposited here is world-readable, permanently, within
-about one business day, at no cost to the author or the reader. It is not a journal: it
-performs no peer review, confers no imprimatur of correctness, and makes no claim that
-what it hosts is right. What it does provide is a **timestamped, immutable, permanently
-addressable public record** that a specific document existed on a specific date under
-specific authorship. For large parts of physics, mathematics and computer science, that
-record — not the eventual journal version — is the object the field actually reads and
-cites.
-
-The server was created in August 1991 by physicist Paul Ginsparg, then at Los Alamos
-National Laboratory, as an automated e-print distribution system for high-energy theory
-(S3). It ran for a decade at Los Alamos, reachable at the address `xxx.lanl.gov` that a
-generation of physicists typed from memory. When Ginsparg moved to Cornell as a professor
-in 2001, he brought arXiv with him (S3), and it remained under Cornell's stewardship —
-latterly at Cornell Tech — for the next 25 years.
-
-That arrangement ended during the compilation window for this record. **On 1 July 2026
-arXiv spun out of Cornell University to become an independent non-profit organisation**
-(S4, S5, S3). arXiv's own announcement frames the goal as "greater organizational
-flexibility, faster technological development, the ability to enter into expanded
-partnerships, and creating a foundation for long-term financial sustainability" (S4).
-Headquarters remain physically in Cornell Tech's Tata Innovation Center (S3). Dr. Penelope
-Lewis, previously Chief Publishing Officer at AIP Publishing, took office as arXiv's
-**inaugural CEO effective 17 August 2026** — two weeks before this record was compiled —
-alongside a first Board of Directors (S6). Anyone reading this record should treat arXiv's
-governance as *actively in transition*: the operator changed legal form ten weeks ago and
-appointed its first chief executive two weeks ago.
-
-Funding is philanthropic and institutional rather than transactional. The Simons
-Foundation is the long-standing major funder and financed the cloud migration and code
-modernisation project begun in 2023; in November 2025 arXiv announced **$7 million in
-gifts and grants from Schmidt Sciences and NASA** to complete that migration and to build
-discovery tooling (S7). Beyond that, arXiv is supported by **230 member institutions** plus
-sponsors, affiliates and individual donors (S8). Submission and reading are free, and
-arXiv's spinout announcement reiterated a commitment to remain "free to read and to submit
-to" (S5).
-
-> **Note on the Google Cloud claim.** arXiv publicly documents a "cloud migration and code
-> modernization project" started in 2023 with Simons Foundation support and continued with
-> Schmidt Sciences money (S7). I could **not** verify from any arXiv-published source that
-> the target platform is specifically Google Cloud, nor that a CY2026 cutover occurred. The
-> only "Google Cloud" string found anywhere in the harvested corpus was on the Kaggle
-> dataset page, which refers to where the *metadata dump* is stored, not to arXiv's
-> production infrastructure. **[NOT-VERIFIED]** — see §10.
-
-## 2. Scope and subject taxonomy
-
-arXiv is organised into archives (`cs`, `math`, `eess`, `quant-ph`, …), each divided into
-categories with codes like `cs.DC`. Every paper has exactly one **primary** category and
-may carry any number of **cross-lists**. The canonical enumeration is the category taxonomy
-page (S9). What follows is the complete `cs.*` and `eess.*` listing as retrieved
-2026-09-01, with the counts harvested in §3 folded in so the taxonomy and the volume data
-can be read together.
-
-### 2.1 Computer science — all 40 `cs.*` categories
-
-Categories flagged ★ are the ones this knowledge base leans on most.
-
-| Code | Name | Notes |
-|---|---|---|
-| `cs.AI` | Artificial Intelligence | Excludes vision, robotics, ML, multiagent, NLP — those have their own categories |
-| ★ `cs.AR` | **Hardware Architecture** | Systems organisation and hardware architecture; ACM C.0, C.1, C.5 |
-| `cs.CC` | Computational Complexity | Models of computation, complexity classes, bounds |
-| `cs.CE` | Computational Engineering, Finance, and Science | Applications-oriented modelling of complex systems |
-| `cs.CG` | Computational Geometry | ACM I.3.5, F.2.2 |
-| `cs.CL` | Computation and Language | Natural language processing |
-| ★ `cs.CR` | **Cryptography and Security** | All cryptography and security; ACM D.4.6, E.3 |
-| `cs.CV` | Computer Vision and Pattern Recognition | Image processing, vision, scene understanding |
-| `cs.CY` | Computers and Society | Ethics, IT policy, legal aspects, computing education |
-| ★ `cs.DB` | **Databases** | Database management, data mining, data processing; ACM E.2, E.5, H.0, H.2, J.1 |
-| ★ `cs.DC` | **Distributed, Parallel, and Cluster Computing** | Fault tolerance, distributed algorithms, parallel computation, clusters |
-| `cs.DL` | Digital Libraries | Digital library design, document and text creation |
-| `cs.DM` | Discrete Mathematics | Combinatorics, graph theory, applied probability |
-| `cs.DS` | Data Structures and Algorithms | ACM E.1, E.2, F.2.1, F.2.2 |
-| ★ `cs.ET` | **Emerging Technologies** | Information processing based on alternatives to silicon CMOS — nanoelectronics, photonics, bio-chemical |
-| `cs.FL` | Formal Languages and Automata Theory | Automata, formal languages, grammars |
-| `cs.GL` | General Literature | Introductory/survey material, biographies, miscellany |
-| `cs.GR` | Graphics | All of ACM I.3 except I.3.5 |
-| `cs.GT` | Computer Science and Game Theory | Mechanism design, learning in games |
-| `cs.HC` | Human-Computer Interaction | Human factors, UIs, collaborative computing |
-| `cs.IR` | Information Retrieval | Indexing, retrieval, content analysis |
-| `cs.IT` | Information Theory | Alias-linked with `math.IT`; coding theory |
-| `cs.LG` | Machine Learning | All aspects of ML research incl. robustness, fairness, methodology |
-| `cs.LO` | Logic in Computer Science | Finite model theory, logics of programs, program verification |
-| `cs.MA` | Multiagent Systems | Distributed AI, intelligent agents |
-| `cs.MM` | Multimedia | ACM H.5.1 |
-| `cs.MS` | Mathematical Software | ACM G.4 |
-| `cs.NA` | Numerical Analysis | **Alias for `math.NA`** — carries no independent count |
-| `cs.NE` | Neural and Evolutionary Computing | Neural nets, connectionism, genetic algorithms, artificial life |
-| ★ `cs.NI` | **Networking and Internet Architecture** | Network architecture, protocols, internetwork standards, web caching |
-| `cs.OH` | Other Computer Science | Catch-all for documents that fit nowhere else |
-| ★ `cs.OS` | **Operating Systems** | ACM D.4.1–D.4.5, D.4.7, D.4.9 |
-| `cs.PF` | Performance | Performance measurement and evaluation, queueing, simulation |
-| ★ `cs.PL` | **Programming Languages** | Language semantics, features, paradigms; also compilers |
-| `cs.RO` | Robotics | ACM I.2.9 |
-| `cs.SC` | Symbolic Computation | ACM I.1 |
-| `cs.SD` | Sound | Computing with sound, audio UIs, sonification, computer music |
-| ★ `cs.SE` | **Software Engineering** | Design tools, metrics, testing, debugging, programming environments |
-| `cs.SI` | Social and Information Networks | Design, analysis, modelling of social/information networks |
-| `cs.SY` | Systems and Control | **Alias for `eess.SY`** — carries no independent count |
-
-**The two aliases matter operationally.** `cs.NA` and `cs.SY` are not independent
-categories: `cs.NA` is an alias for `math.NA` and `cs.SY` an alias for `eess.SY` (S9).
-An API query on `cat:cs.NA` or `cat:cs.SY` returns **0** (S1) — not because nothing is
-filed there, but because the canonical category string stored on the record is the
-`math.NA` / `eess.SY` form. Anyone building a per-category harvest will silently lose
-numerical-analysis and control-systems papers if they do not know this. **[API]**
-
-### 2.2 Electrical engineering and systems science — all 4 `eess.*` categories
-
-| Code | Name | Scope |
-|---|---|---|
-| `eess.AS` | Audio and Speech Processing | Analysis, synthesis, enhancement, transformation, classification of audio/speech signals |
-| `eess.IV` | Image and Video Processing | Formation, capture, processing, communication, analysis, display of images/video |
-| ★ `eess.SP` | **Signal Processing** | Theory, algorithms, performance analysis of signal and data analysis; physical modelling, detection, parameter estimation |
-| ★ `eess.SY` | **Systems and Control** | All facets of automatic control systems; analysis and design using modern control tooling |
-
-`eess` is a young archive relative to `cs` — it was carved out to give electrical
-engineers a home that was neither `cs` nor `physics`. For a hardware-oriented knowledge
-base, `eess.SP` and `eess.SY` are where communications PHY, radar, sensing, estimation
-and control work lands, and they are frequently cross-listed with `cs.IT` and `math.OC`.
-
-### 2.3 Adjacent categories worth knowing
-
-| Code | Name | Why it matters here |
-|---|---|---|
-| `math.OC` | Optimization and Control | Operations research, LP, control theory, optimal control, game theory. Heavily cross-listed from `eess.SY` and `cs.LG` |
-| `stat.ML` | Machine Learning (statistics) | ML with a statistical/theoretical emphasis; the standard cross-list partner of `cs.LG` |
-| `quant-ph` | Quantum Physics | Where quantum algorithms, error correction, superconducting-qubit hardware and NISQ-era architecture papers live |
-| `math.NA` | Numerical Analysis | Numerical algorithms for analysis and algebra; target of the `cs.NA` alias |
-| `math.IT` | Information Theory | Alias for `cs.IT` |
-| `physics.app-ph` | Applied Physics | Electronic devices, optics, photonics, microwaves, spintronics, metamaterials, nanotechnology |
-| `cond-mat.mtrl-sci` | Materials Science | Synthesis, characterisation, defects, interfaces — the substrate layer under device papers |
-
-## 3. Size and growth
-
-This section is built from two independent primary sources that agree with each other:
-arXiv's published monthly-submission series (S10), and a per-category harvest against the
-arXiv API (S1). Where arXiv's blog states a milestone, I recompute it from the raw series
-rather than repeating it.
-
-### 3.1 Headline totals
-
-| Quantity | Value | Source | Retrieved |
-|---|---|---|---|
-| Cumulative submissions, all time, through 2026-08 | **3,152,666** | computed from S10 monthly series | 2026-09-01 **[WEB]** |
-| Cumulative submissions through 2026-06 | 3,091,806 | computed from S10 | 2026-09-01 **[WEB]** |
-| arXiv's own statement, June 2026 | "cumulative submission count exceeds 3.08 million" | S3 | 2026-09-01 **[COM]** |
-| arXiv's own statement, July 2026 | "now hosts over 3 million articles"; passed 3M in **April 2026** | S8 | 2026-09-01 **[DOC]** |
-| Member institutions | 230 | S8 | 2026-09-01 **[DOC]** |
-| Monthly active users | "over 5 million" visiting arxiv.org monthly | S8 | 2026-09-01 **[DOC]** |
-
-**The recomputation matches the operator's claim.** My cumulative-through-June-2026 figure
-of 3,091,806, derived by summing arXiv's own monthly CSV, sits exactly inside the Cornell
-Chronicle's "exceeds 3.08 million" as of June 2026 (S3). Two independently published arXiv
-artifacts agree to three significant figures. **[INF]**
-
-### 3.2 Milestone cross-check — every claim recomputed from the raw series
-
-arXiv's 3-million announcement (S8) makes four historical claims. All four survive
-recomputation from the monthly CSV (S10):
-
-| arXiv's claim (S8) | Recomputed cumulative (S10) | Verdict |
-|---|---|---|
-| "reached 500,000 papers hosted" in 2008 | 515,501 at end of 2008 | ✅ consistent |
-| "1 million article mark just after Christmas in 2014" | 1,001,018 at end of 2014 | ✅ strikingly exact |
-| "2 million mark in early 2022" | 1,999,642 at end of 2021 | ✅ crosses 2M in Jan 2022 |
-| "In the year leading up to … 2 million … 181,630 new submissions" | 181,630 in calendar 2021 | ✅ exact match |
-
-This is a rare case where an operator's promotional numbers are fully reproducible from
-its own published data. It raises confidence in the rest of arXiv's self-reported figures.
-
-### 3.3 Annual submission volume
-
-| Year | Submissions | Cumulative |
-|---|---|---|
-| 1991 (from Aug) | 306 | 306 |
-| 1995 | 13,014 | 33,423 |
-| 2000 | 30,601 | 151,390 |
-| 2005 | 46,855 | 350,721 |
-| 2010 | 70,131 | 649,679 |
-| 2014 | 97,517 | 1,001,018 |
-| 2015 | 105,280 | 1,106,298 |
-| 2016 | 113,380 | 1,219,678 |
-| 2017 | 123,523 | 1,343,201 |
-| 2018 | 140,616 | 1,483,817 |
-| 2019 | 155,866 | 1,639,683 |
-| 2020 | 178,329 | 1,818,012 |
-| 2021 | 181,630 | 1,999,642 |
-| 2022 | 185,692 | 2,185,334 |
-| 2023 | 208,493 | 2,393,827 |
-| 2024 | 244,031 | 2,637,858 |
-| 2025 | 284,486 | 2,922,344 |
-| 2026 (Jan–Aug, partial) | 231,929 | 3,154,273 |
-
-Computed from S10, retrieved 2026-09-01. **[WEB]** Note the acceleration: 2022→2025
-added 98,794 submissions/year of *additional annual throughput*, a ~53% increase in
-three years. The 2026 partial year is already running above 2025's full-year pace.
-
-### 3.4 Record months
-
-arXiv's monthly record was broken three times in the first half of 2026:
-
-| Month | Submissions | Note |
-|---|---|---|
-| 2026-03 | **30,045** | first month above 30,000 |
-| 2026-05 | **31,604** | |
-| 2026-06 | **32,040** | current all-time record |
-| 2026-07 | 29,687 | seasonal dip |
-| 2026-08 | 31,173 | |
-| 2026-09 | 1,607 | partial — 1 September only |
-
-All figures from S10, retrieved 2026-09-01 **[WEB]**, and independently confirmed in
-arXiv's own narrative for March/May/June (S8) **[DOC]**. The `2026-09` row is a partial
-month and must not be read as a monthly total; its presence is a useful sanity check that
-the series was retrieved on 2026-09-01.
-
-### 3.5 Is `cs` now arXiv's largest archive? — VERIFIED YES
-
-Harvested against the arXiv API on 2026-09-01 using `search_query=cat:<archive>.*`, which
-matches papers carrying that archive as **primary or cross-list**:
-
-| Rank | Archive | Papers |
-|---|---|---|
-| 1 | **`cs.*`** | **931,100** |
-| 2 | `math.*` | 682,304 |
-| 3 | `cond-mat.*` | 413,036 |
-| 4 | `physics.*` | 313,422 |
-| 5 | `astro-ph.*` | 286,297 |
-| 6 | `hep-ph` | 198,858 |
-| 7 | `quant-ph` | 185,584 |
-| 8 | `hep-th` | 185,241 |
-| 9 | `eess.*` | 138,247 |
-| 10 | `stat.*` | 132,573 |
-| 11 | `gr-qc` | 124,304 |
-| 12 | `math-ph` | 91,943 |
-| 13 | `nucl-th` | 63,420 |
-| 14 | `hep-ex` | 61,194 |
-| 15 | `q-bio.*` | 55,103 |
-| 16 | `nlin.*` | 47,668 |
-| 17 | `hep-lat` | 30,729 |
-| 18 | `nucl-ex` | 28,870 |
-| 19 | `q-fin.*` | 18,931 |
-| 20 | `econ.*` | 17,253 |
-
-**[API]** — retrieved 2026-09-01.
-
-**Verdict: the claim is confirmed.** `cs.*` at 931,100 is the largest archive on arXiv by
-a margin of ~249,000 papers over `math.*`, and roughly 3× the `physics.*` archive that
-arXiv was founded to serve. A server built in 1991 for high-energy theory is now, by
-volume, a computer science server. **[API]**
-
-Two caveats on interpretation. (a) These are *cross-list-inclusive* counts, so a paper
-that is primary `cs.LG` and cross-listed to `stat.ML` is counted in both `cs.*` and
-`stat.*`; the columns do not sum to the archive total. (b) The count is of papers, not of
-submissions/versions, so it is not directly comparable to the 3.15M submission figure in
-§3.1. **[INF]**
-
-### 3.6 Per-category counts — all 40 `cs.*`, ranked
-
-The single most useful machine-readable artifact in this record. Harvested 2026-09-01 via
-`https://export.arxiv.org/api/query?search_query=cat:<CODE>&max_results=1`, reading
-`opensearch:totalResults`. **[API]**
-
-| Rank | Code | Name | Papers |
-|---|---|---|---|
-| 1 | `cs.LG` | Machine Learning | 283,807 |
-| 2 | `cs.CV` | Computer Vision and Pattern Recognition | 204,123 |
-| 3 | `cs.AI` | Artificial Intelligence | 197,852 |
-| 4 | `cs.CL` | Computation and Language | 117,997 |
-| 5 | `cs.RO` | Robotics | 57,451 |
-| 6 | `cs.IT` | Information Theory | 55,845 |
-| 7 | ★ `cs.CR` | Cryptography and Security | 51,581 |
-| 8 | `cs.HC` | Human-Computer Interaction | 32,545 |
-| 9 | `cs.CY` | Computers and Society | 30,192 |
-| 10 | ★ `cs.DC` | Distributed, Parallel, and Cluster Computing | 29,886 |
-| 11 | `cs.DS` | Data Structures and Algorithms | 29,806 |
-| 12 | ★ `cs.SE` | Software Engineering | 29,164 |
-| 13 | ★ `cs.NI` | Networking and Internet Architecture | 28,226 |
-| 14 | `cs.IR` | Information Retrieval | 26,920 |
-| 15 | `cs.SI` | Social and Information Networks | 23,845 |
-| 16 | `cs.SD` | Sound | 21,863 |
-| 17 | `cs.LO` | Logic in Computer Science | 20,089 |
-| 18 | `cs.NE` | Neural and Evolutionary Computing | 18,206 |
-| 19 | `cs.DM` | Discrete Mathematics | 16,052 |
-| 20 | `cs.GT` | Computer Science and Game Theory | 15,406 |
-| 21 | `cs.MA` | Multiagent Systems | 13,485 |
-| 22 | `cs.CC` | Computational Complexity | 13,309 |
-| 23 | ★ `cs.DB` | Databases | 12,304 |
-| 24 | `cs.CE` | Computational Engineering, Finance, and Science | 11,162 |
-| 25 | ★ `cs.PL` | Programming Languages | 10,261 |
-| 26 | `cs.MM` | Multimedia | 10,010 |
-| 27 | `cs.GR` | Graphics | 9,689 |
-| 28 | ★ `cs.AR` | **Hardware Architecture** | 8,932 |
-| 29 | `cs.CG` | Computational Geometry | 8,317 |
-| 30 | ★ `cs.ET` | **Emerging Technologies** | 7,815 |
-| 31 | `cs.DL` | Digital Libraries | 6,294 |
-| 32 | `cs.FL` | Formal Languages and Automata Theory | 6,186 |
-| 33 | `cs.PF` | Performance | 5,536 |
-| 34 | `cs.SC` | Symbolic Computation | 3,231 |
-| 35 | `cs.MS` | Mathematical Software | 2,741 |
-| 36 | `cs.OH` | Other Computer Science | 2,321 |
-| 37 | ★ `cs.OS` | **Operating Systems** | 1,455 |
-| 38 | `cs.GL` | General Literature | 245 |
-| 39 | `cs.NA` | Numerical Analysis | 0 — *alias for `math.NA`* |
-| 40 | `cs.SY` | Systems and Control | 0 — *alias for `eess.SY`* |
-
-### 3.7 `eess.*` and adjacent categories
-
-| Code | Name | Papers |
-|---|---|---|
-| ★ `eess.SY` | Systems and Control | 47,937 |
-| ★ `eess.SP` | Signal Processing | 41,815 |
-| `eess.IV` | Image and Video Processing | 31,534 |
-| `eess.AS` | Audio and Speech Processing | 22,281 |
-| | | |
-| `quant-ph` | Quantum Physics | 185,584 |
-| `stat.ML` | Machine Learning (statistics) | 79,758 |
-| `math.OC` | Optimization and Control | 63,892 |
-| `cond-mat.mtrl-sci` | Materials Science | 111,931 |
-| `physics.app-ph` | Applied Physics | 24,140 |
-
-**[API]** — retrieved 2026-09-01.
-
-### 3.8 What these numbers do and do not mean
-
-- **The `cs.*` per-category counts sum to 1,424,149**, against an archive total of 931,100.
-  The 1.53× ratio is the average number of `cs` categories per `cs` paper. Cross-listing is
-  the norm, not the exception, and **you must never sum category counts** to get a total.
-  **[INF]**
-- **`cs.LG` alone (283,807) exceeds the entire `eess.*` archive (138,247) twofold**, and is
-  roughly 32× the size of `cs.AR`. The ML categories dominate arXiv computer science so
-  heavily that generic `cs` volume statistics are effectively ML statistics. **[INF]**
-- **The hardware-relevant categories are small.** `cs.AR` (8,932), `cs.ET` (7,815) and
-  especially `cs.OS` (1,455) are among the smallest on the server. `cs.OS` is smaller than
-  `cs.GL`+`cs.OH`+`cs.MS` combined. For an operating-systems or architecture literature
-  search, arXiv is a **thin** source and must be supplemented — see §7.8 on what is
-  missing. **[INF]**
-- **Counts are of current papers, not submissions.** Withdrawn papers remain addressable
-  (§5), and a paper with nine versions counts once.
-
-## 4. Screening and moderation — what gets in
-
-arXiv's gate has three independent stages: **endorsement** (who may submit at all),
-**moderation** (whether a given submission is announced), and **post-announcement
-moderation** (reclassification and withdrawal). None of them is peer review, and arXiv
-says so explicitly: *"Please note that the arXiv moderation process is not a peer-review
-process. arXiv staff and moderators cannot give feedback on the submission."* (S11)
-**[DOC]**
-
-### 4.1 Endorsement — the author-side gate
-
-arXiv requires that users **be endorsed before submitting their first paper to arXiv or a
-new category** (S12). The endorsement graph works like this:
-
-- **Endorsement is per-domain, not global.** Endorsement is granted within an
-  *endorsement domain* — a high-level subject area. Most archives (`hep-th`, `cond-mat`,
-  `q-bio`) are single endorsement domains; `physics` is the notable exception, where
-  individual subject classes are separate domains (S12, S13). Being endorsed in `cs` does
-  not endorse you in `math`.
-- **Who may endorse.** An endorser must have authored a threshold number of papers within
-  that endorsement domain. arXiv does not publish the per-domain number, saying only that
-  it "has been set so that any active scientist who has been working in their field for a
-  few years should be able to endorse." Crucially, **only papers submitted between three
-  months and five years ago count** — a recency window that keeps the endorser pool
-  active, and that silently strips endorsement power from researchers who have stopped
-  posting (S12). **[DOC]**
-- **The endorser must themselves be endorsed.** "You must also have an active positive
-  endorsement to that area yourself before you may endorse for that subject
-  classification" (S12). The graph is therefore rooted and transitively closed —
-  endorsement power propagates only from existing endorsed authors.
-- **One positive endorsement suffices.** "At least one positive endorsement is required
-  per endorsement category to be considered endorsed for that category" (S12).
-- **Endorsers are anonymous, and negatives are recorded.** Whether you endorsed is
-  "private between you and the arXiv administrators." A declined endorsement is "recorded
-  as a negative vote of endorsement" (S12). Neither the requester nor the public sees it.
-- **Endorsement is revocable** — arXiv "reserves the right to revoke any submitter's
-  endorsement if that submitter has violated arXiv policies" (S12).
-- **Endorsement is explicitly not review.** "We do not expect you to read the paper in
-  detail, or verify that the work is correct, but you should check that the paper is
-  appropriate for the subject area" (S12). An endorsement is a statement about
-  *community membership*, not correctness.
-
-#### 4.1.1 The January 2026 endorsement tightening — a material change
-
-This is recent and it changes who can publish on arXiv. **As of 21 January 2026, arXiv no
-longer accepts an institutional email address as the sole qualifier for endorsement**
-(S14). New submitters now face two paths:
-
-1. **Automatic**: an institutional email address from an academic/research institution
-   **AND** previous authorship on an existing arXiv paper in the target endorsement domain.
-2. **Personal**: direct endorsement from an established arXiv author in the same domain.
-
-arXiv's stated reason is blunt: *"in recent years, arXiv has received an unsustainable
-increase in the number of non-scientific submissions, increasing the rejection rate and
-requiring excessive moderation and staff effort. Because of this, we have determined that
-institutional email addresses are no longer a sufficient credential for determining
-minimum research competence"* (S14). **[DOC]**
-
-The change was piloted in arXiv Mathematics in **December 2025** before the
-all-categories rollout (S14, S15). Existing endorsements were grandfathered: "Authors who
-were previously endorsed to submit to a particular category will still be endorsed in that
-category" (S14).
-
-**Who is effectively exempt.** There is no formal exemption list, but three groups pass
-the gate without friction: (a) anyone already endorsed in the domain, (b) anyone who has
-claimed authorship on a prior arXiv paper in the domain *and* holds an institutional
-address, and (c) co-authors submitting through an already-endorsed submitting author —
-endorsement attaches to the *submitter*, so a student's paper submitted by their advisor
-requires no endorsement of the student. **[INF from S12, S14]**
-
-**Who is now excluded.** Independent researchers without institutional affiliation,
-industry researchers on corporate email, and researchers changing fields all now require
-a personal endorsement they must solicit by cold email. arXiv states flatly that "arXiv
-staff cannot waive endorsement requirements or provide a personal endorsement" (S14).
-This is a real and widening barrier — see §10.
-
-### 4.2 Moderation — the submission-side gate
-
-Moderation happens **after submission and before public announcement** (S11). Grounds for
-declining, per arXiv's own published list (S11) **[DOC]**:
-
-| Ground | Substance |
-|---|---|
-| Scholarly standards | Form: "appropriate and carefully prepared sections, figures, tables, references"; professional language; "sufficiently neutral tone"; "general scrupulousness and care of preparation" |
-| Scholarly interest | May be declined if it "lacks originality, novelty, significance, and/or contains falsified, plagiarized content or serious misrepresentations of data, affiliation, or content" |
-| Not research | "course projects, research proposals, news, or information about political causes" |
-| Content type | Research articles are "the primary content-type"; other types are governed by specific policies |
-| Out of scope | "Submissions may be declined if they do not fit into our current classification scheme or we do not currently serve the community" |
-| Duplicated content | Multiple similar submissions may be required to be "consolidated or versioned" |
-| Rights | Must be the author's original work, no verbatim referee comments, no third-party-barred material |
-| Excessive submission rate | **"we ask that they submit no more than three papers per day"** |
-| Images | Images "likely to cause egregious offense may be declined or removed" — arXiv names the "Lena" image explicitly as a problem case |
-
-**Generative AI policy** (S11): arXiv requires authors "to report in their work any
-significant use of sophisticated tools … we now include in particular text-to-text
-generative AI"; reminds authors that they "take full responsibility for all its contents,
-irrespective of how the contents were generated"; and rules that "generative AI language
-tools should not be listed as an author."
-
-**Prior publication is neither necessary nor sufficient.** "arXiv moderation decisions may
-be influenced by the publication status of the submission, but prior publication does not
-guarantee acceptance in arXiv" (S11). And there is an escalating-scrutiny rule: "Submitters
-who have had works previously delayed or declined by arXiv should anticipate closer
-scrutiny on future submissions. In some cases, authors may be required to establish a
-conventional publication record and limit their submissions to works that are published in
-conventional journals" (S11). **[DOC]**
-
-**Who the moderators are.** "arXiv moderators are volunteer subject matter experts with
-terminal degrees in their field … approved by their discipline-level advisory committees
-and by arXiv staff" (S11). arXiv reports "hundreds of volunteer moderators" (S8).
-Moderation is confidential — moderators "consider the submissions to arXiv as privileged
-information, as they would with a paper being refereed for a journal" (S11). **It is
-"inappropriate to contact any moderator directly regarding your submission"** (S11).
-
-**Holds.** A submission that is neither announced nor declined sits *on hold*. arXiv does
-not publish hold durations or a hold-rate statistic. Its own stated rationale for the
-October 2025 review-article change includes the goal to "reduce submission hold times"
-(S16), which is an implicit admission that hold times had become a problem, but **I could
-not find any published figure for mean or median hold time, nor a published
-accept/decline/hold rate. [NOT-VERIFIED]**
-
-### 4.3 The October 2025 `cs.*` review-article and position-paper policy — VERIFIED
-
-The user asked me to verify a recent policy change requiring prior peer review for surveys
-in `cs.*`. **It exists.** Announced 31 October 2025 (S16). Direct quote:
-
-> "arXiv's computer science (CS) category has updated its moderation practice with respect
-> to review (or survey) articles and position papers. **Before being considered for
-> submission to arXiv's CS category, review articles and position papers must now be
-> accepted at a journal or a conference and complete successful peer review.** When
-> submitting review articles or position papers, authors must include documentation of
-> successful peer review to receive full consideration. Review/survey articles or position
-> papers submitted to arXiv without this documentation will be likely to be rejected and
-> not appear on arXiv." (S16) **[DOC]**
-
-Key details, all quoted from S16:
-
-- **Scope: `cs.*` only.** Other archives were unaffected at announcement. arXiv said other
-  categories "may choose to change their moderation practices in a similar manner" if they
-  see a similar rise, and "We will make these updates public if and when they do occur."
-- **arXiv denies it is a policy change**: *"Technically, no! … review articles and position
-  papers are not (and have never been) listed as part of the accepted content types."*
-  They had previously been accepted "only at moderator discretion."
-- **The stated cause is LLM-generated volume**: *"arXiv has been flooded with papers.
-  Generative AI / large language models have added to this flood by making papers –
-  especially papers not introducing new research results – fast and easy to write."*
-- **The scale**: arXiv "now receive[s] hundreds of review articles every month," and "the
-  majority of the review articles we receive are little more than annotated bibliographies,
-  with no substantial discussion of open research issues."
-- **Workshop review does not count**: *"the review conducted at conference workshops
-  generally does not meet the same standard of rigor of traditional peer review and is not
-  enough."*
-- **Evidence required**: "include the peer reviewed journal reference and DOI metadata. If
-  you do not provide this, your review article or position paper will likely be rejected."
-- **Carve-out**: scientific research papers *studying* the societal impact of technology
-  are unaffected — "arXiv has always released these types of scientific papers, for example
-  in `cs.CY` or `physics.soc-ph`."
-- **Appeals**: a rejected survey may be resubmitted only after an accepted appeal following
-  successful peer review; "Do not resubmit … without an accepted appeal."
-
-**Practical consequence for this knowledge base.** Any `cs.*` survey or benchmark-review
-posted to arXiv **after 31 October 2025** should carry a journal/conference reference and
-DOI. A `cs.*` survey from that period *without* one is anomalous and worth a second look.
-Conversely, the huge stock of pre-2025 `cs` surveys on arXiv was never subject to this bar
-and carries no such implied vetting. **[INF]**
-
-### 4.4 After announcement — reclassification, withdrawal, permanence
-
-**Once announced, a paper is permanent.** "Once a paper is announced it becomes part of the
-permanent scholarly record. arXiv will only consider requests for removal if the submitter
-did not have the legal right to agree to the license" (S11). **[DOC]**
-
-**Reclassification** happens both before and after announcement: "arXiv may reclassify
-already announced papers if the moderators determine there is a more appropriate category,"
-and cross-lists "may be removed by moderators when the classification is deemed
-inappropriate" (S11).
-
-**Withdrawal semantics — the critical detail.** A withdrawal does **not** remove the paper.
-Per arXiv's own withdrawal page (S17) **[DOC]**:
-
-> "Articles that have been announced and made public cannot be completely removed. **A
-> withdrawal creates a new version of the paper marked as withdrawn.** That new version
-> displays the reason for the withdrawal and does not link directly to the full text.
-> **Previous versions will still be accessible, including the full text.**"
-
-So a withdrawn paper's v1 PDF remains publicly retrievable forever at
-`arxiv.org/abs/<id>v1`. Retraction on arXiv is a *labelling* operation layered on top of an
-append-only store, not a deletion. This is the single most important thing to understand
-about arXiv's error model — see §5.4.
-
-arXiv further constrains *why* you may withdraw (S17): it is "not appropriate to withdraw a
-paper because it is published or submitted to a journal" (add a `journal-ref` instead), nor
-"because it is being updated" (submit a replacement instead), nor for copyright infringement
-(a separate process). Withdrawal reasons "will be displayed publicly."
-
-Before announcement the picture is different: an unannounced submission can be genuinely
-**deleted** or **unsubmitted** back to incomplete status (S17). The permanence rule attaches
-at announcement, not at submission.
-
-## 5. Reliability — what you can and cannot trust
-
-### 5.1 What an arXiv ID guarantees
-
-An arXiv identifier is a strong claim about **provenance and time**, and a null claim about
-**correctness**.
-
-| Guaranteed | Not guaranteed |
-|---|---|
-| The document existed in that exact form on that date (per-version timestamps to the second, exposed via the API `published`/`updated` fields) **[API]** | That it is correct |
-| The version is immutable — v1 never changes; edits create v2, v3, … (S18) | That it was peer reviewed |
-| Every prior version stays retrievable, including for withdrawn papers (S17) | That the claimed affiliations are real |
-| Permanent addressability: `arxiv.org/abs/<id>` and `arxiv.org/abs/<id>vN` | That the results replicate |
-| The submitter passed the endorsement gate in that domain (§4.1) | That the submitter is the author (endorsement checks community membership, not authorship) |
-| A moderator judged it in-scope and minimally scholarly (§4.2) | That a moderator read it carefully — arXiv says they cannot give feedback (S11) |
-
-The timestamp is the product. Everything else is a by-product.
-
-### 5.2 Versioning and priority claims
-
-Version numbers are the mechanism by which arXiv supports priority claims. A useful
-worked example from the verified landmark set: **`1706.03762` (*Attention Is All You Need*)
-was published 2017-06-12 and last updated 2023-08-02, at v7** (S1) **[API]**. Six years of
-revisions to a paper that was "finished" in 2017, all publicly diffable by fetching each
-`v1`…`v7`. Similarly `1412.6980` (*Adam*) sits at **v9** and `1409.0473` (Bahdanau
-attention) at **v7** (S1).
-
-Practical consequences:
-
-- **Always cite a version if the claim matters.** "As shown in 1706.03762" is ambiguous
-  across seven documents. `1706.03762v1` is not.
-- **The v1 date, not the paper date, is the priority date.** The API `published` field is
-  the v1 timestamp; `updated` is the latest version. Reading `updated` as the publication
-  date is a common and serious error in automated bibliometrics. **[INF]**
-- **A high version count is not a quality signal in either direction.** It can mean
-  sustained community engagement (Adam, v9) or repeated correction.
-
-### 5.3 The eventual-publication rate — what I could and could not establish
-
-The template asks for measured eventual-publication rates from the scientometric
-literature. **I could not verify a specific rate from a source I actually retrieved.**
-**[NOT-VERIFIED]**
-
-What I tried, all on 2026-09-01 against the arXiv API (S1):
-
-| Query | Result |
-|---|---|
-| `abs:"fraction of arXiv preprints" AND abs:"published"` | 0 results |
-| `ti:"preprint" AND ti:"publication rate" AND cat:cs.DL` | 0 results |
-
-I am aware of commonly-cited figures in the region of 60–75% for arXiv-wide eventual
-journal publication, but **I did not retrieve a primary source for any of them during this
-pass and will not launder a remembered number into this record.** Anyone extending this
-record should look at the `cs.DL` literature and at Cornell/arXiv's own annual reports.
-
-**What can be measured directly, and is more useful anyway:** arXiv exposes `journal_ref`
-and `doi` metadata fields via the API, so the "has it been published" question is
-answerable per-paper and in bulk without relying on any literature estimate. In the
-71-paper verified landmark harvest (§7), **only 6 carry a `journal_ref`** — Shor
-(`quant-ph/9508027`), the transmon paper (`cond-mat/0703002`), surface codes (`1208.0928`),
-Preskill's NISQ paper (`1801.00862`), the Google quantum-supremacy supplement
-(`1910.11333`), the LSM survey (`1812.07527`), and DeepSeek-R1 (`2501.12948`) carries a
-*Nature* reference. **[API]** That is a striking result and it is the subject of §5.5:
-almost none of the most influential CS papers on arXiv have journal metadata attached, even
-when they were in fact published.
-
-> **Caveat on that measurement.** A missing `journal_ref` means *the author never added
-> one*, not that the paper was never published. `1706.03762` was published at NeurIPS 2017
-> and has no `journal_ref`. So `journal_ref` coverage is a **lower bound** on publication
-> and a poor proxy for it. Do not invert it. **[INF]**
-
-### 5.4 Failure modes
-
-**Permanence of error.** Because withdrawal is a labelling operation over an append-only
-store (§4.4), a wrong result posted to arXiv is retrievable forever. The v1 PDF of a
-withdrawn paper stays at `arxiv.org/abs/<id>v1`. Citation managers, scrapers, LLM training
-corpora and the S3 bulk buckets (§8) all captured it. Retraction propagates weakly: the
-abstract page shows the withdrawal notice, but a cached PDF, a `ar5iv` HTML rendering or a
-third-party mirror generally does not.
-
-**LLM-generated submissions.** This is not speculative — it is arXiv's own stated reason
-for two policy changes inside twelve months. The October 2025 review-article rule cites
-LLMs "making papers … fast and easy to write" and characterises the majority of incoming
-surveys as "little more than annotated bibliographies" (S16). The January 2026 endorsement
-change cites an "unsustainable increase in the number of non-scientific submissions" (S14).
-arXiv's incoming CEO named "the rise of AI-generated preprints" as one of three challenges
-she was appointed to address (S6). **[DOC]**
-
-**Salami slicing.** arXiv's countermeasure is the explicit rate limit — "we ask that they
-submit no more than three papers per day" — plus the duplicated-content rule under which
-moderators "may request that the submissions be consolidated or versioned" (S11). Both are
-requests backed by discretion, not hard technical limits.
-
-**Unreviewed claims propagating via press.** arXiv IDs look like citations and are treated
-as such by journalists and by downstream automated systems. Nothing in an arXiv ID
-distinguishes a NeurIPS best-paper from a submission that a volunteer moderator waved
-through as in-scope. The endorsement gate filters *who*, the moderation gate filters
-*whether it is science*; neither filters *whether it is right*.
-
-**Category gaming.** Because cross-listing is free and near-universal (§3.8: 1.53 `cs`
-categories per `cs` paper), authors can and do cross-list into high-traffic categories for
-visibility. Moderators may remove inappropriate cross-lists (S11), but this is reactive.
-
-### 5.5 The ML/systems dynamic — when arXiv *is* the version of record
-
-In machine learning and increasingly in ML systems, the arXiv version is not a preprint of
-the real paper; **it is the real paper**. The evidence from the verified landmark harvest
-(§7) is direct:
-
-- **Of 71 verified landmark papers, 65 carry no `journal_ref` at all** (S1) **[API]**,
-  including *Attention Is All You Need*, ResNet, Adam, BERT, GPT-3, ViT, CLIP, LLaMA,
-  FlashAttention, vLLM and Mamba. These are among the most-cited papers in modern computing
-  and their arXiv records are bare of publication metadata.
-- Several were **never conventionally published at all**. `1603.04467` (TensorFlow) is a
-  whitepaper. `2302.13971` (LLaMA) and `2005.14165` (GPT-3, though it appeared at NeurIPS)
-  were consumed by the field as arXiv documents on the day they appeared.
-- arXiv itself makes the claim: "arXiv is such a foundational infrastructure for sharing
-  research that **many papers appear *only* on arXiv**" (S8). **[DOC]**
-- The `1512.03385` (ResNet) record carries the author comment **"Tech report"** (S1) — the
-  authors' own framing of a paper that won CVPR 2016 and became one of the most-cited works
-  in the history of computer science.
-
-The practical upshot: in these fields, "is it peer reviewed?" is close to the wrong
-question, because the community's actual quality signal is post-hoc — reproduction,
-citation, and whether the code runs. But the corollary is that **the reader inherits the
-entire burden of evaluation**, with none of the (imperfect) filtering a venue would supply.
-
-### 5.6 How to sanity-check an individual arXiv paper
-
-A concrete procedure, all steps machine-executable against the API (S1):
-
-1. **Resolve the ID and confirm the title matches your citation.** Mismatch means a
-   transposed digit — see the negative control in §8.6.
-2. **Check `published` vs `updated`.** A large gap means substantive revision; diff v1
-   against vN if the claim is load-bearing.
-3. **Check for a withdrawal notice** on the abstract page. Remember the full text is still
-   there, so absence of a broken link is not absence of a retraction.
-4. **Read `journal_ref` and `doi` if present** — but treat absence as uninformative (§5.3).
-5. **Check the primary category against the content.** A hardware claim filed primary
-   `cs.GL` or `cs.OH` is a signal.
-6. **Check the author comment field**, which conventionally carries venue acceptance
-   ("Accepted at NeurIPS 2024"), page counts, and errata notes.
-7. **For post-2025-10-31 `cs.*` surveys, require a journal-ref/DOI** — arXiv now does
-   (§4.3).
-8. **Check whether the endorsement path is plausible**: a paper by authors with no other
-   arXiv presence in that domain, posted after January 2026, went through a personal
-   endorsement.
-
-## 6. What you actually find there — examples
-
-Concrete document types a systems or electronics engineer will actually encounter:
-
-- **Model and system release papers that never go to a venue.** `1603.04467` —
-  *TensorFlow: Large-Scale Machine Learning on Heterogeneous Distributed Systems*
-  (2016-03-14, primary `cs.DC`) is a whitepaper. `1912.01703` — *PyTorch: An Imperative
-  Style, High-Performance Deep Learning Library* (2019-12-03). `2302.13971` — *LLaMA*
-  (2023-02-27). These are the primary technical documentation for infrastructure that
-  millions of people run. **[API]**
-- **Simulator and toolchain papers.** `2007.03152` — *The gem5 Simulator: Version 20.0+*
-  (2020-07-07, `cs.AR`), the citable reference for the standard computer-architecture
-  simulator. `2002.11054` — *MLIR: A Compiler Infrastructure for the End of Moore's Law*
-  (2020-02-25, `cs.PL`). **[API]**
-- **Vulnerability disclosures.** `1801.01203` (*Spectre*) and `1801.01207` (*Meltdown*)
-  were both posted 2018-01-03 — the coordinated-disclosure day. arXiv served as the
-  publication channel for two of the most consequential hardware security findings ever
-  made. **[API]**
-- **Retrospectives and "selected papers" reissues.** `1904.09724` *RowHammer: A
-  Retrospective* and `2306.16093` *Retrospective: Flipping Bits in Memory Without Accessing
-  Them*. Note the second one: the **original** RowHammer paper (ISCA 2014) is not on arXiv
-  — only its 2023 retrospective is. A title search for "Flipping Bits in Memory Without
-  Accessing Them" returns exactly **1** hit, and it is the retrospective (S1). **[API]**
-- **Industrial hardware measurement papers.** `1704.04760` — *In-Datacenter Performance
-  Analysis of a Tensor Processing Unit* (2017-04-16, `cs.AR`), Google's TPUv1 paper.
-- **Blockchain and consensus protocol specifications.** `1607.01341` (*Algorand*, at v9),
-  `1803.05069` (*HotStuff*), `1807.04938` (*The latest gossip on BFT consensus* — the
-  Tendermint paper), `1710.09437` (*Casper the Friendly Finality Gadget*). For this
-  subfield arXiv, alongside IACR ePrint, is the primary venue.
-- **Communications theory that became standards.** `0807.3917` — Arıkan's *Channel
-  polarization* (2008-07-24, `cs.IT`), the paper behind the polar codes adopted for 5G NR
-  control channels.
-- **Category-defining surveys** — from before the October 2025 rule (§4.3). `1703.09039`
-  *Efficient Processing of Deep Neural Networks: A Tutorial and Survey*; `1812.07527`
-  *LSM-based Storage Techniques: A Survey* (with a VLDB Journal reference attached).
-- **Benchmarks as papers.** `2310.06770` *SWE-bench*, `2107.03374` *Evaluating Large
-  Language Models Trained on Code* (the HumanEval/Codex paper).
-- **Foundational quantum results.** `quant-ph/9508027` (Shor, 1995) and `quant-ph/9605043`
-  (Grover, 1996) are on arXiv, in the original archive, with 30-year-old identifiers that
-  still resolve.
-
-## 7. Landmark papers
-
-This is the core deliverable. **Every row below was verified on 2026-09-01 by querying the
-arXiv API and confirming that the identifier resolves to an entry whose title matches**
-(S1). Dates are the **v1 `published` timestamp** from the API — the priority date, not the
-last-updated date. **[API]** for every identifier, date, primary category and `journal_ref`
-in these tables.
-
-**Method note on the "arXiv first?" column.** I do not assert venue publication dates I
-did not retrieve. The column reports one of:
-
-- **✅ proven** — the record carries a `journal_ref` or `doi` whose year is *later* than the
-  arXiv v1 date, so arXiv demonstrably came first. Provable from the API alone.
-- **✅ de facto** — no venue metadata is attached at all. arXiv is the only citable record
-  the authors ever supplied; whatever happened at a venue, the arXiv document is what the
-  field reads and cites. (See §5.3 — absence of `journal_ref` does **not** prove absence of
-  publication.)
-- **≈ same-year** — venue metadata exists with the same year as v1; ordering within the year
-  is not provable from the metadata I retrieved.
-
-### 7.1 Machine learning — foundational
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| Improving neural networks by preventing co-adaptation of feature detectors (Dropout) | [1207.0580](https://arxiv.org/abs/1207.0580) | 2012-07-03 | `cs.NE` | Introduced dropout regularisation | ✅ de facto |
-| Efficient Estimation of Word Representations in Vector Space (word2vec) | [1301.3781](https://arxiv.org/abs/1301.3781) | 2013-01-16 | `cs.CL` | Made dense word embeddings standard | ✅ de facto |
-| Playing Atari with Deep Reinforcement Learning (DQN) | [1312.5602](https://arxiv.org/abs/1312.5602) | 2013-12-19 | `cs.LG` | Launched deep reinforcement learning | ✅ de facto |
-| Generative Adversarial Networks | [1406.2661](https://arxiv.org/abs/1406.2661) | 2014-06-10 | `stat.ML` | Created the GAN research programme | ✅ de facto |
-| Neural Machine Translation by Jointly Learning to Align and Translate | [1409.0473](https://arxiv.org/abs/1409.0473) | 2014-09-01 | `cs.CL` | The attention mechanism itself; now at v7 | ✅ de facto |
-| Very Deep Convolutional Networks for Large-Scale Image Recognition (VGG) | [1409.1556](https://arxiv.org/abs/1409.1556) | 2014-09-04 | `cs.CV` | Depth-scaling of CNNs; standard backbone for years | ✅ de facto |
-| Sequence to Sequence Learning with Neural Networks | [1409.3215](https://arxiv.org/abs/1409.3215) | 2014-09-10 | `cs.CL` | Encoder–decoder framing of translation | ✅ de facto |
-| Adam: A Method for Stochastic Optimization | [1412.6980](https://arxiv.org/abs/1412.6980) | 2014-12-22 | `cs.LG` | The default optimiser of deep learning; now at **v9** | ✅ de facto |
-| Batch Normalization: Accelerating Deep Network Training by Reducing Internal Covariate Shift | [1502.03167](https://arxiv.org/abs/1502.03167) | 2015-02-11 | `cs.LG` | Made very deep networks trainable | ✅ de facto |
-| Distilling the Knowledge in a Neural Network | [1503.02531](https://arxiv.org/abs/1503.02531) | 2015-03-09 | `stat.ML` | Knowledge distillation; basis of modern model compression | ✅ de facto |
-| Deep Residual Learning for Image Recognition (ResNet) | [1512.03385](https://arxiv.org/abs/1512.03385) | 2015-12-10 | `cs.CV` | Residual connections; author comment reads **"Tech report"** | ✅ de facto |
-| Concrete Problems in AI Safety | [1606.06565](https://arxiv.org/abs/1606.06565) | 2016-06-21 | `cs.AI` | Framed the empirical AI-safety agenda | ✅ de facto |
-| Outrageously Large Neural Networks: The Sparsely-Gated Mixture-of-Experts Layer | [1701.06538](https://arxiv.org/abs/1701.06538) | 2017-01-23 | `cs.LG` | Sparse MoE — the basis of today's frontier-model scaling | ✅ de facto |
-| **Attention Is All You Need** | [1706.03762](https://arxiv.org/abs/1706.03762) | 2017-06-12 | `cs.CL` | The Transformer. Now at **v7**, last updated 2023-08-02 | ✅ de facto |
-| Proximal Policy Optimization Algorithms (PPO) | [1707.06347](https://arxiv.org/abs/1707.06347) | 2017-07-20 | `cs.LG` | Default policy-gradient method; underpins RLHF | ✅ de facto |
-| UMAP: Uniform Manifold Approximation and Projection | [1802.03426](https://arxiv.org/abs/1802.03426) | 2018-02-09 | `stat.ML` | Standard high-dimensional embedding/visualisation tool | ✅ de facto |
-| Loss Surfaces, Mode Connectivity, and Fast Ensembling of DNNs | [1802.10026](https://arxiv.org/abs/1802.10026) | 2018-02-27 | `stat.ML` | Mode connectivity of loss landscapes | ✅ de facto |
-| BERT: Pre-training of Deep Bidirectional Transformers | [1810.04805](https://arxiv.org/abs/1810.04805) | 2018-10-11 | `cs.CL` | Made pretrain-then-finetune the NLP default | ✅ de facto |
-| Massively Multilingual Neural Machine Translation in the Wild | [1907.05019](https://arxiv.org/abs/1907.05019) | 2019-07-11 | `cs.CL` | Scaling limits of multilingual translation | ✅ de facto |
-| Scaling Laws for Neural Language Models | [2001.08361](https://arxiv.org/abs/2001.08361) | 2020-01-23 | `cs.LG` | Power-law scaling; made compute budgeting predictive | ✅ de facto |
-| Language Models are Few-Shot Learners (GPT-3) | [2005.14165](https://arxiv.org/abs/2005.14165) | 2020-05-28 | `cs.CL` | In-context learning at 175B parameters | ✅ de facto |
-| An Image is Worth 16x16 Words (ViT) | [2010.11929](https://arxiv.org/abs/2010.11929) | 2020-10-22 | `cs.CV` | Transformers displace CNNs in vision | ✅ de facto |
-| Learning Transferable Visual Models From Natural Language Supervision (CLIP) | [2103.00020](https://arxiv.org/abs/2103.00020) | 2021-02-26 | `cs.CV` | Contrastive image–text pretraining; basis of multimodal models | ✅ de facto |
-| On the Opportunities and Risks of Foundation Models | [2108.07258](https://arxiv.org/abs/2108.07258) | 2021-08-16 | `cs.LG` | Named and framed the "foundation model" category | ✅ de facto |
-| High-Resolution Image Synthesis with Latent Diffusion Models | [2112.10752](https://arxiv.org/abs/2112.10752) | 2021-12-20 | `cs.CV` | Latent diffusion — the Stable Diffusion architecture | ✅ de facto |
-| Training Compute-Optimal Large Language Models (Chinchilla) | [2203.15556](https://arxiv.org/abs/2203.15556) | 2022-03-29 | `cs.CL` | Corrected the scaling laws; reset industry training budgets | ✅ de facto |
-| LLaMA: Open and Efficient Foundation Language Models | [2302.13971](https://arxiv.org/abs/2302.13971) | 2023-02-27 | `cs.CL` | Opened the open-weights ecosystem | ✅ de facto |
-| Mamba: Linear-Time Sequence Modeling with Selective State Spaces | [2312.00752](https://arxiv.org/abs/2312.00752) | 2023-12-01 | `cs.LG` | Selective SSMs as a Transformer alternative | ✅ de facto |
-| KAN: Kolmogorov-Arnold Networks | [2404.19756](https://arxiv.org/abs/2404.19756) | 2024-04-30 | `cs.LG` | Learnable-activation alternative to MLPs; now at v5 | ✅ de facto |
-| DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via RL | [2501.12948](https://arxiv.org/abs/2501.12948) | 2025-01-22 | `cs.CL` | RL-trained reasoning; `journal_ref` = *Nature* 645:633–638 (2025) | **✅ proven** |
-
-### 7.2 ML systems, training and inference infrastructure
-
-This is the subgroup most relevant to a hardware/systems knowledge base — and it lives on
-arXiv almost exclusively.
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| Deep Compression: Compressing Deep Neural Networks with Pruning, Trained Quantization and Huffman Coding | [1510.00149](https://arxiv.org/abs/1510.00149) | 2015-10-01 | `cs.CV` | Model compression pipeline that drove accelerator design | ✅ de facto |
-| TensorFlow: Large-Scale Machine Learning on Heterogeneous Distributed Systems | [1603.04467](https://arxiv.org/abs/1603.04467) | 2016-03-14 | `cs.DC` | The TensorFlow whitepaper — never a venue paper | ✅ de facto |
-| Ray: A Distributed Framework for Emerging AI Applications | [1712.05889](https://arxiv.org/abs/1712.05889) | 2017-12-16 | `cs.DC` | Task+actor model for distributed ML | ✅ de facto |
-| Horovod: fast and easy distributed deep learning in TensorFlow | [1802.05799](https://arxiv.org/abs/1802.05799) | 2018-02-15 | `cs.LG` | Ring-allreduce data-parallel training | ✅ de facto |
-| Megatron-LM: Training Multi-Billion Parameter Models Using Model Parallelism | [1909.08053](https://arxiv.org/abs/1909.08053) | 2019-09-17 | `cs.CL` | Tensor/model parallelism for LLM training | ✅ de facto |
-| ZeRO: Memory Optimizations Toward Training Trillion Parameter Models | [1910.02054](https://arxiv.org/abs/1910.02054) | 2019-10-04 | `cs.LG` | Sharded optimiser/gradient/parameter state; DeepSpeed's core | ✅ de facto |
-| Fast Transformer Decoding: One Write-Head is All You Need (MQA) | [1911.02150](https://arxiv.org/abs/1911.02150) | 2019-11-06 | `cs.NE` | Multi-query attention — the KV-cache bandwidth fix | ✅ de facto |
-| PyTorch: An Imperative Style, High-Performance DL Library | [1912.01703](https://arxiv.org/abs/1912.01703) | 2019-12-03 | `cs.LG` | The PyTorch reference paper | ✅ de facto |
-| Reformer: The Efficient Transformer | [2001.04451](https://arxiv.org/abs/2001.04451) | 2020-01-13 | `cs.LG` | LSH attention + reversible layers for long context | ✅ de facto |
-| Automatic Cross-Replica Sharding of Weight Update in Data-Parallel Training | [2004.13336](https://arxiv.org/abs/2004.13336) | 2020-04-28 | `cs.DC` | Weight-update sharding (ZeRO-1-style) on TPU pods | ✅ de facto |
-| LoRA: Low-Rank Adaptation of Large Language Models | [2106.09685](https://arxiv.org/abs/2106.09685) | 2021-06-17 | `cs.CL` | Made fine-tuning cheap; now ubiquitous | ✅ de facto |
-| Evaluating Large Language Models Trained on Code (Codex / HumanEval) | [2107.03374](https://arxiv.org/abs/2107.03374) | 2021-07-07 | `cs.LG` | Code LLMs and the HumanEval benchmark | ✅ de facto |
-| FlashAttention: Fast and Memory-Efficient Exact Attention with IO-Awareness | [2205.14135](https://arxiv.org/abs/2205.14135) | 2022-05-27 | `cs.LG` | IO-aware attention kernel; a hardware-architecture result | ✅ de facto |
-| GPTQ: Accurate Post-Training Quantization for GPT | [2210.17323](https://arxiv.org/abs/2210.17323) | 2022-10-31 | `cs.LG` | Practical 3–4 bit post-training quantisation | ✅ de facto |
-| FlashAttention-2: Faster Attention with Better Parallelism and Work Partitioning | [2307.08691](https://arxiv.org/abs/2307.08691) | 2023-07-17 | `cs.LG` | Better parallelism and work partitioning | ✅ de facto |
-| Efficient Memory Management for LLM Serving with PagedAttention (vLLM) | [2309.06180](https://arxiv.org/abs/2309.06180) | 2023-09-12 | `cs.LG` | Virtual-memory paging applied to the KV cache | ✅ de facto |
-| SWE-bench: Can Language Models Resolve Real-World GitHub Issues? | [2310.06770](https://arxiv.org/abs/2310.06770) | 2023-10-10 | `cs.CL` | The dominant agentic software-engineering benchmark | ✅ de facto |
-
-### 7.3 Distributed systems and consensus
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| Majority is not Enough: Bitcoin Mining is Vulnerable (selfish mining) | [1311.0243](https://arxiv.org/abs/1311.0243) | 2013-11-01 | `cs.CR` | Showed <50% attacks on Bitcoin; now at v5 | ✅ de facto |
-| Lightweight Asynchronous Snapshots for Distributed Dataflows | [1506.08603](https://arxiv.org/abs/1506.08603) | 2015-06-29 | `cs.DC` | Apache Flink's checkpointing algorithm | ✅ de facto |
-| Algorand | [1607.01341](https://arxiv.org/abs/1607.01341) | 2016-07-05 | `cs.CR` | Byzantine agreement via verifiable random functions; at **v9** | ✅ de facto |
-| Casper the Friendly Finality Gadget | [1710.09437](https://arxiv.org/abs/1710.09437) | 2017-10-25 | `cs.CR` | PoS finality overlay; the basis of Ethereum's transition | ✅ de facto |
-| HotStuff: BFT Consensus in the Lens of Blockchain | [1803.05069](https://arxiv.org/abs/1803.05069) | 2018-03-13 | `cs.DC` | Linear-communication, pipelined BFT; basis of DiemBFT | ✅ de facto |
-| Conflict-free Replicated Data Types (CRDTs) — encyclopedia entry | [1805.06358](https://arxiv.org/abs/1805.06358) | 2018-05-16 | `cs.DC` | Shapiro/Preguiça reference entry; `doi` 10.1007/978-3-319-63962-8_185 | ≈ same-year |
-| Conflict-free Replicated Data Types: An Overview | [1806.10254](https://arxiv.org/abs/1806.10254) | 2018-06-27 | `cs.DC` | Widely used CRDT tutorial/overview | ✅ de facto |
-| The latest gossip on BFT consensus (Tendermint) | [1807.04938](https://arxiv.org/abs/1807.04938) | 2018-07-13 | `cs.DC` | The Tendermint consensus specification | ✅ de facto |
-| Study of Firecracker MicroVM | [2005.12821](https://arxiv.org/abs/2005.12821) | 2020-05-26 | `cs.OS` | One of only 1,455 papers in all of `cs.OS`; microVM isolation | ✅ de facto |
-
-> **Important caveat on CRDTs.** The two CRDT entries above are a 2018 encyclopedia entry
-> and a 2018 overview. The **original** CRDT work (Shapiro, Preguiça, Baquero, Zawirski,
-> 2011 — INRIA technical report and SSS 2011) is **not** on arXiv. A title search for
-> "Conflict-free Replicated Data Types" returns 11 hits, none of them the 2011 original
-> (S1). **[API]** Cite the INRIA report for priority, not `1805.06358`.
-
-### 7.4 Databases and data management
-
-`cs.DB` is small (12,304 papers, rank 23 of 40 — §3.6) and most canonical database systems
-work is *not* here (§7.8). What is here is mostly the learned-systems line of work.
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| The Missing Piece in Complex Analytics: Low Latency, Scalable Model Management | [1409.3809](https://arxiv.org/abs/1409.3809) | 2014-09-12 | `cs.DB` | Early framing of model management as a DB problem (CIDR line) | ✅ de facto |
-| **The Case for Learned Index Structures** | [1712.01208](https://arxiv.org/abs/1712.01208) | 2017-12-04 | `cs.DB` | Launched the learned-index/learned-systems research programme | ✅ de facto |
-| LSM-based Storage Techniques: A Survey | [1812.07527](https://arxiv.org/abs/1812.07527) | 2018-12-18 | `cs.DB` | The reference survey for LSM engines; `journal_ref` = VLDB Journal **2019** | **✅ proven** |
-| Neo: A Learned Query Optimizer | [1904.03711](https://arxiv.org/abs/1904.03711) | 2019-04-07 | `cs.DB` | Learned query optimisation; `doi` 10.14778/3342263.3342644 (PVLDB 2019) | **✅ proven** |
-
-### 7.5 Computer architecture, hardware and accelerators
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| EIE: Efficient Inference Engine on Compressed Deep Neural Network | [1602.01528](https://arxiv.org/abs/1602.01528) | 2016-02-04 | `cs.CV` | Sparse-weight inference accelerator; ISCA-line work | ✅ de facto |
-| Efficient Processing of Deep Neural Networks: A Tutorial and Survey | [1703.09039](https://arxiv.org/abs/1703.09039) | 2017-03-27 | `cs.CV` | The standard tutorial on DNN accelerator design (Sze et al.) | ✅ de facto |
-| **In-Datacenter Performance Analysis of a Tensor Processing Unit** | [1704.04760](https://arxiv.org/abs/1704.04760) | 2017-04-16 | `cs.AR` | Google's TPUv1 — the defining industrial DSA measurement paper | ✅ de facto |
-| Eyeriss v2: A Flexible Accelerator for Emerging DNNs on Mobile Devices | [1807.07928](https://arxiv.org/abs/1807.07928) | 2018-07-10 | `cs.DC` | Flexible NoC dataflow accelerator for sparse/compact DNNs | ✅ de facto |
-| **The gem5 Simulator: Version 20.0+** | [2007.03152](https://arxiv.org/abs/2007.03152) | 2020-07-07 | `cs.AR` | The citable reference for the standard architecture simulator | ✅ de facto |
-
-**On RISC-V, chiplets, HLS and EDA.** These topics are *present* but as a long tail of
-ordinary papers, not landmarks. Counts from title searches on 2026-09-01 (S1) **[API]**:
-`ti:"RISC-V" AND cat:cs.AR` → **250**; `ti:"chiplet"` → **111**; `ti:"High-Level
-Synthesis" AND cat:cs.AR` → **81**; `ti:"gem5"` → **16**; `ti:"MLIR"` → **58**. The
-foundational RISC-V documents are **UC Berkeley EECS technical reports and RISC-V
-International specifications, not arXiv preprints**, and I found no arXiv-hosted canonical
-RISC-V ISA paper. **[API / NOT-VERIFIED for any canonical RISC-V arXiv landmark]**
-
-### 7.6 Security, cryptography and hardware security
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| **Spectre Attacks: Exploiting Speculative Execution** | [1801.01203](https://arxiv.org/abs/1801.01203) | 2018-01-03 | `cs.CR` | Speculative-execution side channels; broke the CPU security model | ✅ de facto |
-| **Meltdown** | [1801.01207](https://arxiv.org/abs/1801.01207) | 2018-01-03 | `cs.CR` | Out-of-order execution reads kernel memory; forced KPTI worldwide | ✅ de facto |
-| RowHammer: A Retrospective | [1904.09724](https://arxiv.org/abs/1904.09724) | 2019-04-22 | `cs.CR` | Mutlu & Kim's synthesis of DRAM disturbance research | ✅ de facto |
-| Retrospective: Flipping Bits in Memory Without Accessing Them | [2306.16093](https://arxiv.org/abs/2306.16093) | 2023-06-28 | `cs.CR` | Retrospective on the 2014 RowHammer paper (original not on arXiv) | ✅ de facto |
-
-Spectre and Meltdown are worth dwelling on: **both were posted on the same day,
-2018-01-03**, which was the coordinated disclosure date. arXiv functioned as the
-disclosure channel for an industry-wide embargoed vulnerability — a role no journal could
-have played on that timescale.
-
-### 7.7 Programming languages, compilers and networking
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| **MLIR: A Compiler Infrastructure for the End of Moore's Law** | [2002.11054](https://arxiv.org/abs/2002.11054) | 2020-02-25 | `cs.PL` | Multi-level IR; now the substrate for ML compilers and much EDA tooling | ✅ de facto |
-| **Programming Protocol-Independent Packet Processors (P4)** | [1312.1719](https://arxiv.org/abs/1312.1719) | 2013-12-05 | `cs.NI` | Defined programmable data planes; the P4 language | ✅ de facto |
-| Channel polarization: A method for constructing capacity-achieving codes | [0807.3917](https://arxiv.org/abs/0807.3917) | 2008-07-24 | `cs.IT` | Arıkan's polar codes — adopted for 5G NR control channels; at v5 | ✅ de facto |
-| What Will 5G Be? | [1405.2957](https://arxiv.org/abs/1405.2957) | 2014-05-12 | `cs.IT` | The agenda-setting 5G survey; `journal_ref` = IEEE JSAC | ≈ same-year |
-
-### 7.8 Quantum computing and quantum hardware
-
-`quant-ph` is arXiv's 7th-largest archive (185,584 papers, §3.5) and unlike `cs.OS` or
-`cs.DB`, the field's **canonical** results really are here.
-
-| Paper | arXiv ID | v1 date | Primary | Why it matters | arXiv first? |
-|---|---|---|---|---|---|
-| Polynomial-Time Algorithms for Prime Factorization and Discrete Logarithms (Shor) | [quant-ph/9508027](https://arxiv.org/abs/quant-ph/9508027) | 1995-08-30 | `quant-ph` | Shor's algorithm; `journal_ref` SIAM **1997**, doi 10.1137/S0097539795293172 | **✅ proven** |
-| A fast quantum mechanical algorithm for database search (Grover) | [quant-ph/9605043](https://arxiv.org/abs/quant-ph/9605043) | 1996-05-29 | `quant-ph` | Grover's algorithm; quadratic search speedup | ✅ de facto |
-| Charge insensitive qubit design derived from the Cooper pair box (transmon) | [cond-mat/0703002](https://arxiv.org/abs/cond-mat/0703002) | 2007-02-28 | `cond-mat.mes-hall` | **The transmon** — the qubit in essentially every superconducting QC today | ≈ same-year |
-| Surface codes: Towards practical large-scale quantum computation | [1208.0928](https://arxiv.org/abs/1208.0928) | 2012-08-04 | `quant-ph` | The reference surface-code QEC architecture paper | ≈ same-year |
-| Quantum Computing in the NISQ era and beyond | [1801.00862](https://arxiv.org/abs/1801.00862) | 2018-01-02 | `quant-ph` | Preskill's NISQ framing; `journal_ref` Quantum 2, 79 (2018) | ≈ same-year |
-| Supplementary information for "Quantum supremacy using a programmable superconducting processor" | [1910.11333](https://arxiv.org/abs/1910.11333) | 2019-10-23 | `quant-ph` | The Sycamore supremacy supplement; `journal_ref` Nature 574:505 (2019) | ≈ same-year |
-
-### 7.9 Verified-row count and the honest summary
-
-| Group | Verified rows |
-|---|---|
-| 7.1 Machine learning — foundational | 30 |
-| 7.2 ML systems and infrastructure | 17 |
-| 7.3 Distributed systems and consensus | 9 |
-| 7.4 Databases | 4 |
-| 7.5 Architecture and accelerators | 5 |
-| 7.6 Security and hardware security | 4 |
-| 7.7 PL, compilers, networking, comms | 4 |
-| 7.8 Quantum | 6 |
-| **Total** | **79** |
-
-All 79 identifiers were resolved against the arXiv API on 2026-09-01 and their titles
-confirmed to match (S1). **[API]**
-
-The distribution is itself the finding: **47 of 79 rows (59%) are machine learning or ML
-infrastructure.** That is not an artifact of my selection — it tracks §3.6, where `cs.LG`
-+ `cs.CV` + `cs.AI` + `cs.CL` account for 803,779 of the 1,424,149 category-assignments in
-`cs.*`. arXiv is, in computing, overwhelmingly an ML archive with other subfields attached.
-
-### 7.10 What is NOT on arXiv — the most useful negative result in this record
-
-Anyone treating arXiv as *the* systems literature will silently miss most of the canon.
-I ran explicit title searches against the API on 2026-09-01 (S1). **[API]**
-
-| Canonical paper | Actual venue | arXiv title-search result |
-|---|---|---|
-| **MapReduce: Simplified Data Processing on Large Clusters** | OSDI 2004 | **0 hits** |
-| **The Google File System** | SOSP 2003 | **0 hits** |
-| **Bigtable: A Distributed Storage System for Structured Data** | OSDI 2006 | 2 hits, **neither is the paper** (a compaction paper and a Graphulo paper) |
-| **Dynamo: Amazon's Highly Available Key-value Store** | SOSP 2007 | **0 hits** |
-| **In Search of an Understandable Consensus Algorithm (Raft)** | USENIX ATC 2014 | **0 hits** |
-| **Paxos Made Simple** | ACM SIGACT News 2001 | 1 hit, and it is *"Moderately Complex Paxos Made Simple"* (1704.00082), a different 2017 paper |
-| **ZooKeeper: Wait-free coordination for internet-scale systems** | USENIX ATC 2010 | 2 hits, **neither is the paper** (a TLA+ verification paper and FaaSKeeper) |
-| **Spanner: Google's Globally-Distributed Database** | OSDI 2012 | 291 hits — **all of them about graph spanners**, an unrelated combinatorics object |
-| **Resilient Distributed Datasets (Spark)** | NSDI 2012 | **0 hits** |
-| **RAMCloud** | SOSP/TOCS | **0 hits** |
-| **Bitcoin: A Peer-to-Peer Electronic Cash System** | self-published, bitcoin.org | **0 hits** |
-| **Flipping Bits in Memory Without Accessing Them (RowHammer)** | ISCA 2014 | 1 hit, and it is the **2023 retrospective** (2306.16093), not the original |
-| **The Chubby lock service** | OSDI 2006 | not separately probed — **[NOT-VERIFIED]**, but no arXiv record surfaced in any adjacent query |
-| **seL4: Formal verification of an OS kernel** | SOSP 2009 | 5 hits, **none is the original** — all are later derivative works |
-| **CompCert (formally verified C compiler)** | POPL 2006 / CACM 2009 | 4 hits, **none is the original** — all are later derivative works |
-| **BBR: Congestion-Based Congestion Control** | ACM Queue 2016 | 34 hits, **none is the original** — all are third-party evaluations |
-
-**The `Spanner` case is the instructive one.** A naive keyword search returns 291 results
-and a careless reader concludes the paper is there. It is not — every hit is about *graph
-spanners*. **HTTP 200 and a non-empty result set do not mean the document exists.**
-
-**Why this pattern exists.** The systems community (SOSP, OSDI, NSDI, ATC, ISCA, VLDB,
-SIGMOD) publishes through venue proceedings and the ACM/USENIX digital libraries. USENIX
-in particular makes proceedings open access at no charge, so there was never a paywall
-pressure driving authors to arXiv. The ML community, which had no comparable open venue
-culture and moves faster than any review cycle, went to arXiv instead. **The result is a
-sharp disciplinary split that maps almost exactly onto the category-size data in §3.6:
-`cs.LG` has 283,807 papers and `cs.OS` has 1,455.** **[INF]**
-
-**Practical rule.** Use arXiv as a *primary* source for machine learning, ML systems,
-consensus/blockchain protocols, information theory, and quantum computing. Use it as a
-*supplementary* source for operating systems, databases, computer architecture and
-networking — and always check ACM DL, USENIX, IEEE Xplore and DBLP before concluding a
-systems paper does not exist.
-
-## 8. Access, APIs and bulk retrieval
-
-arXiv is unusually generous and unusually well documented for scripted access. All probes
-below were run 2026-09-01.
-
-### 8.1 The legacy arXiv API (Atom over HTTP)
-
-Base URL: `https://export.arxiv.org/api/query` (S1). Returns Atom XML with an
-`opensearch:totalResults` count and `<entry>` elements carrying `id`, `title`, `published`,
-`updated`, `summary`, `author`, `arxiv:primary_category`, `arxiv:journal_ref`, `arxiv:doi`
-and `arxiv:comment`.
-
-Two query modes:
-
-```
-# by category, count only
-https://export.arxiv.org/api/query?search_query=cat:cs.AR&max_results=1
-# by identifier, batched (comma-separated)
-https://export.arxiv.org/api/query?id_list=1706.03762,2312.00752&max_results=40
-```
-
-> **⚠ Gotcha found during this pass — `max_results=0` is broken.** The obvious way to ask
-> for a count without payload is `max_results=0`. On 2026-09-01 this returned **HTTP 200
-> with a fake result**: `totalResults` = **1**, and a single `<entry>` whose title is
-> "Error" and whose summary reads *"The server encountered an internal error and was unable
-> to complete your request."* The same query with `max_results=1` returned the correct
-> `totalResults` = **8932** for `cs.AR`. **A naive harvester using `max_results=0` will
-> silently record 1 for every category.** Use `max_results=1`. **[API]**
-
-Reproducibility check: cat counts for `cs.AR`, `cs.OS`, `eess.SP` and `cs.ET` were
-harvested twice, hours apart, and returned identical values (8932 / 1455 / 41815 / 7815),
-confirming the §3.6 table is stable and not a transient. **[API]**
-
-### 8.2 Rate limits — quoted exactly
-
-From arXiv's Terms of Use for arXiv APIs (S19) **[DOC]**:
-
-> "When using the legacy APIs (including OAI-PMH, RSS, and the arXiv API), **make no more
-> than one request every three seconds, and limit requests to a single connection at a
-> time.**"
-
-And, importantly:
-
-> "Please note that the following rate limits apply to **all of the machines under your
-> control as a whole**. You should not attempt to overcome these limits by increasing the
-> number of machines used to make requests."
-
-Explicit prohibitions from the same document: do not "Store and serve arXiv e-prints
-(PDFs, source files, or other content) from your servers, unless you have the permission of
-the copyright holder"; do not "Attempt to circumvent rate limits"; do not represent your
-project as arXiv-endorsed. Explicitly permitted: "Retrieve, store, transform, and share
-descriptive metadata"; "Retrieve, store, and use the content of arXiv e-prints for your own
-personal use, or for research purposes"; build search interfaces, notification apps,
-visualisations and citation graphs. (S19)
-
-All harvesting for this record used a 3.5 s inter-request delay and a single connection.
-
-### 8.3 OAI-PMH
-
-Endpoint: `https://oaipmh.arxiv.org/oai`. An `Identify` request returned (S20) **[API]**:
-
-| Field | Value |
-|---|---|
-| `repositoryName` | arXiv |
-| `protocolVersion` | 2.0 |
-| `adminEmail` | help@arxiv.org |
-| `earliestDatestamp` | **2005-09-16** |
-| `deletedRecord` | **persistent** |
-| `granularity` | YYYY-MM-DD |
-| metadataPolicy | "Metadata harvesting permitted through OAI interface" |
-| **dataPolicy** | **"Full-content harvesting not permitted (except by special arrangement)"** |
-| submissionPolicy | "Author self-submission preferred, submissions screened for appropriateness." |
-
-Two things matter here. **`earliestDatestamp` is 2005-09-16, not 1991** — the OAI-PMH
-datestamp reflects arXiv's record-keeping epoch, not the corpus start. Incremental
-harvesting from OAI-PMH will not walk you back to Shor 1995; use the bulk buckets or the
-Kaggle dump for full history. And **`deletedRecord=persistent`** is the machine-readable
-statement of the permanence rule in §4.4.
-
-**The `arXivRaw` metadata prefix is the useful one** because it carries the licence:
-
-```
-https://oaipmh.arxiv.org/oai?verb=GetRecord&identifier=oai:arXiv.org:1706.03762&metadataPrefix=arXivRaw
-```
-
-returned HTTP 200, 4,099 bytes, with `<title>Attention Is All You Need</title>`,
-`<categories>cs.CL cs.LG</categories>` and
-`<license>http://arxiv.org/licenses/nonexclusive-distrib/1.0/</license>` (S20). **[API]**
-This is the programmatic licence check referenced in §9.3.
-
-### 8.4 S3 bulk source and PDF buckets
-
-arXiv publishes the full corpus in **requester-pays** S3 buckets in `us-east-1` (N.
-Virginia) — the downloader pays AWS for bandwidth, arXiv pays nothing (S21) **[DOC]**.
-
-| Item | Value | Source |
-|---|---|---|
-| Bucket | `s3://arxiv` | S21 |
-| PDF key pattern | `pdf/arXiv_pdf_YYMM_NNN.tar` (~500 MB chunks) | S21 |
-| PDF manifest | `pdf/arXiv_pdf_manifest.xml` — includes `md5sum`, `content_md5sum`, `num_items`, `size`, `first_item`, `last_item` per chunk | S21 |
-| Complete PDF set size | **~2.7 TB as of March 2023** | S21 |
-| Complete set (PDF + source) | **~9.2 TB as of April 2025**, growing ~100 GB/month | S21 |
-| Region | Eastern US (N. Virginia) | S21 |
-
-The manifest carrying per-chunk MD5s is what makes this a serious archival source rather
-than a scrape: you can verify integrity offline.
-
-**Negative control on the bucket.** An unauthenticated anonymous GET against the bucket
-returned `<Error><Code>AccessDenied</Code><Message>Access Denied</Message>` (S21 probe).
-Requester-pays means you need credentials and must pass the requester-pays header; there is
-no anonymous path. **[API]**
-
-**Licence constraint on bulk data.** arXiv states plainly on the same page: *"Most articles
-submitted to arXiv are submitted with the default arXiv license, which grants arXiv a
-perpetual, non-exclusive license to distribute the article, but does not assign copyright
-to arXiv, nor grant arXiv the right to grant any specific rights to others. **We are thus
-unable to grant others the right to distribute arXiv articles.** If you build indexes or
-tools based on the full-text, you must link back to arXiv for downloads."* (S21) You may
-download 9.2 TB; you may not rehost it. See §9.
-
-### 8.5 Other access paths — all probed live 2026-09-01
-
-| Path | URL pattern | Probe result | Notes |
-|---|---|---|---|
-| Abstract page | `arxiv.org/abs/<id>` | HTTP **200**, 43,644 bytes for `1706.03762` | Canonical landing page |
-| Native HTML | `arxiv.org/html/<id>v<n>` | HTTP **200**, 668,209 bytes for `2312.00752v2` | arXiv's own LaTeX→HTML, newer papers only |
-| **ar5iv** | `ar5iv.labs.arxiv.org/html/<id>` | HTTP **200**, 167,302 bytes | Title confirmed *"[1706.03762] Attention Is All You Need"*. Covers older papers native HTML does not |
-| **alphaXiv** | `alphaxiv.org/abs/<id>` | HTTP **200**, 367,300 bytes | Title *"Attention Is All You Need \| alphaXiv"*. Third-party discussion/annotation layer |
-| **HuggingFace Papers** | `huggingface.co/papers/<id>` | HTTP **200**, 292,855 bytes | Third-party curation + model/dataset links |
-| **Kaggle metadata dump** | `kaggle.com/datasets/Cornell-University/arxiv` | HTTP 200, page title *"arXiv Dataset \| Kaggle"* | JSON metadata for the whole corpus; the only "Google Cloud" reference found anywhere in the corpus refers to *this dataset's* storage |
-| OAI-PMH | `oaipmh.arxiv.org/oai` | HTTP 200 | §8.3 |
-| S3 | `s3://arxiv` | AccessDenied anonymous | §8.4 |
-
-**[WEB]** / **[API]** as marked. Note that ar5iv, alphaXiv and HuggingFace Papers are
-**third-party or labs services, not core arXiv infrastructure**, and none carries arXiv's
-permanence guarantee.
-
-### 8.6 Negative control — bogus identifiers
-
-Per the house rule that HTTP 200 does not mean a document exists, I probed two deliberately
-invalid identifiers alongside a real one:
-
-| URL | HTTP | Bytes | Body |
-|---|---|---|---|
-| `arxiv.org/abs/1706.03762` (real) | **200** | 43,644 | Full abstract page |
-| `arxiv.org/abs/9999.99999` (bogus) | **404** | 7,229 | *"Article identifier '9999.99999' not recognized"* |
-| `arxiv.org/abs/2599.88888` (bogus) | **404** | 7,229 | Identical error page — byte-identical size confirms a constant template |
-| **API** `?id_list=9999.99999` | **200** ⚠ | — | Valid Atom feed, `totalResults` = **0**, zero `<entry>` elements |
-
-**[WEB]** / **[API]**
-
-**Two distinct behaviours, and the second is the trap.** The web front end returns a proper
-**404** for a bad ID. **The API returns HTTP 200** with a well-formed, entirely valid Atom
-document containing no entries. Any harvester that checks only the HTTP status code will
-treat a nonexistent paper as a successful retrieval. **You must check
-`opensearch:totalResults` or count `<entry>` elements, not the status code.** The
-byte-identical 7,229-byte 404 pages for two different bogus IDs also confirm that the web
-error page is a fixed template and cannot be mistaken for a short real record.
-
-## 9. Licensing and reuse
-
-### 9.1 The default is restrictive, and this surprises people
-
-arXiv is open *access*, not open *licence*. The default and most common choice is the
-**arXiv.org perpetual, non-exclusive license 1.0**, which arXiv describes as giving
-"limited rights to arXiv to distribute the article, and also **limits re-use of any type
-from other entities or individuals**" (S22) **[DOC]**. arXiv's API Terms of Use put it
-bluntly: *"The vast majority of e-prints are submitted under the arXiv.org non-exclusive
-right to distribute"* and *"a very small subset of arXiv e-prints are submitted with
-licenses that permit redistribution"* (S19).
-
-So: you may read and download anything on arXiv. You generally may **not** rehost the PDFs.
-
-### 9.2 The full licence menu
-
-From arXiv's licence page (S22) **[DOC]**:
-
-| Licence | Commercial use | Derivatives | Redistribution by third parties | Notes |
-|---|---|---|---|---|
-| **arXiv.org perpetual, non-exclusive 1.0** (default) | — | — | **No** | Grants arXiv distribution rights only; author keeps copyright |
-| **CC BY 4.0** | ✅ | ✅ | ✅ with attribution | arXiv's recommended liberal option |
-| **CC BY-SA 4.0** | ✅ | ✅ (share-alike) | ✅ with attribution + identical terms | |
-| **CC BY-NC-SA 4.0** | ❌ | ✅ (share-alike) | ✅ non-commercial only | |
-| **CC BY-NC-ND 4.0** | ❌ | ❌ (unadapted only) | ✅ non-commercial, verbatim | Common for publisher "accepted manuscripts", often with embargo |
-| **CC0 1.0** (public domain) | ✅ | ✅ | ✅ no conditions | **Author gives up copyright**; "conflicts with many publishers' requirements" |
-
-Critical operational rules from the same page:
-
-- **"The license chosen is irrevocable and cannot be changed."**
-- **"different versions of the work can have different licenses"** — so a licence check must
-  be *per version*, not per paper.
-- For all licences except CC0, "the original copyright holder retains ownership."
-- If an author needs a licence not on the menu, they select the arXiv licence and state the
-  desired licence on the first page of the article.
-
-### 9.3 Metadata is CC0 — and that is the important carve-out
-
-**"A Creative Commons CC0 1.0 Universal Public Domain Dedication will apply to all
-metadata."** (S22) The API Terms of Use repeat this: you are "free to use descriptive
-metadata about arXiv e-prints under the terms of the Creative Commons Universal (CC0 1.0)
-Public Domain Declaration" (S19). Descriptive metadata is defined there as "title,
-abstract, authors, identifier…".
-
-**For a knowledge base like this one, that is the whole ballgame.** Titles, abstracts,
-authors, IDs, categories, dates, `journal_ref` and `doi` — everything in the §7 tables and
-the §3.6 counts — is CC0 and freely redistributable. The full-text PDFs generally are not.
-
-### 9.4 How to check a paper's licence programmatically
-
-Use OAI-PMH with `metadataPrefix=arXivRaw` and read the `<license>` element (§8.3):
-
-```
-https://oaipmh.arxiv.org/oai?verb=GetRecord&identifier=oai:arXiv.org:<ID>&metadataPrefix=arXivRaw
-```
-
-I sampled ten landmark papers from §7 on 2026-09-01 (S20) **[API]**:
-
-| Paper | arXiv ID | Licence |
-|---|---|---|
-| Attention Is All You Need | 1706.03762 | `arxiv.org/licenses/nonexclusive-distrib/1.0/` |
-| ResNet | 1512.03385 | `arxiv.org/licenses/nonexclusive-distrib/1.0/` |
-| GPT-3 | 2005.14165 | `arxiv.org/licenses/nonexclusive-distrib/1.0/` |
-| TPU (In-Datacenter Performance Analysis) | 1704.04760 | `arxiv.org/licenses/nonexclusive-distrib/1.0/` |
-| DeepSeek-R1 | 2501.12948 | `arxiv.org/licenses/nonexclusive-distrib/1.0/` |
-| LLaMA | 2302.13971 | **CC BY 4.0** |
-| vLLM / PagedAttention | 2309.06180 | **CC BY 4.0** |
-| Mamba | 2312.00752 | **CC BY 4.0** |
-| gem5 v20.0+ | 2007.03152 | **CC BY 4.0** |
-| MLIR | 2002.11054 | **CC BY 4.0** |
-
-**6 of 10 restrictive, 4 of 10 CC BY.** There is a rough temporal trend toward CC BY in
-papers from 2020 onward, but it is not reliable — DeepSeek-R1 (2025) is under the
-restrictive default. **Never assume; always query.** In particular, *Attention Is All You
-Need*, *ResNet* and the TPU paper — three of the most reproduced papers in computing —
-cannot lawfully be rehosted from your own server. **[API]**
-
-## 10. Caveats and controversies
-
-**1. Volume growth in `cs.*` is straining the system, and arXiv says so.** Submissions rose
-from 185,692 (2022) to 284,486 (2025), a 53% increase in three years (§3.3), with three
-consecutive monthly records in 2026 (§3.4). arXiv's own language is not neutral: "arXiv has
-been flooded with papers" (S16), "an unsustainable increase in the number of non-scientific
-submissions" (S14). Two significant gates were tightened within twelve months as a direct
-result (§4.1.1, §4.3).
-
-**2. The October 2025 `cs.*` review-article rule is a genuine departure.** Requiring prior
-peer review before a preprint may be posted inverts the purpose of a preprint server for
-one content type in one archive. arXiv's framing — that surveys "are not (and have never
-been) listed as part of the accepted content types" (S16) — is technically defensible but
-the practical effect is new. The published comments on arXiv's own announcement include the
-substantive objection that "surveys become outdated quickly. Requiring full peer review
-before posting risks making them obsolete by the time they appear" (S16). **[COM]** Note
-also that the rule is **archive-specific**: a survey rejected from `cs.*` may still be
-acceptable in another archive, which creates an incentive to mis-file.
-
-**3. Endorsement is a real and now higher barrier.** The January 2026 change removed
-institutional email as a sufficient credential (§4.1.1). The people affected are precisely
-those without institutional backing: independent researchers, industry practitioners on
-corporate email, and researchers from institutions with weak arXiv presence. arXiv states
-it "cannot waive endorsement requirements" (S14). A commenter on arXiv's own spinout
-announcement raised exactly this: hoping "arXiv will consider improving the endorsement
-system, since requiring new authors to obtain approval from previous authors" is a barrier
-(S5). **[COM]**
-
-**4. Moderation opacity — sourced criticism.** arXiv publishes criteria (§4.2) but not
-outcomes. There is no published accept/decline/hold rate, no published hold-time
-distribution, and **[NOT-VERIFIED]** on my attempts to find any. The process is structurally
-opaque by design: moderators are anonymous to submitters, contacting them is
-"inappropriate", "decisions upon appeal are final", and "no feedback will be provided with
-the decision" (S11). Endorsement refusals are likewise invisible — a negative endorsement is
-"recorded as a negative vote" but never disclosed (S12).
-
-The main *published* critique I could verify is Silagadze, **"On arXiv moderation system"**,
-[2307.11791](https://arxiv.org/abs/2307.11791), 2023-07-23 (S23) **[LIT]**. Its argument, in
-the author's words: arXiv "gave a powerful impetus to the democratization of science,
-freeing young scientists … especially from totalitarian countries, from authoritarian
-oppression," but "many of arXiv's innovative features have been blurred by the introduction
-of a moderation system." The author accepts that "a moderation system is essential to
-maintain the quality of arXiv content" and proposes reform modelled on MathOverflow's
-transparent moderation rather than abolition.
-
-> Note the reflexivity: the most accessible published critique of arXiv moderation is itself
-> an arXiv preprint that passed arXiv moderation. A title search for `arXiv` AND
-> `moderation` returns exactly **1** result (S1) — the scholarly literature specifically on
-> arXiv moderation is essentially a single paper. **[API]**
-
-**5. The permanence-of-error problem.** Withdrawal is a labelling operation, not a deletion
-(§4.4): "Previous versions will still be accessible, including the full text" (S17), and
-OAI-PMH advertises `deletedRecord=persistent` (S20). A wrong or fabricated result posted to
-arXiv is permanently retrievable. Retraction does not propagate to the S3 bulk tarballs, to
-ar5iv renderings, to third-party layers like alphaXiv or HuggingFace Papers, or to any LLM
-corpus already trained on it. **arXiv's error model is append-only and its retraction
-mechanism is advisory.**
-
-**6. LLM-generated content is now a first-order operational problem.** Not speculation:
-arXiv cites it as the cause of the review-article rule (S16), implies it in the endorsement
-change (S14), and the incoming CEO named "the rise of AI-generated preprints" as a defining
-challenge (S6). arXiv's response so far is disclosure-based — authors must report
-"significant use of … text-to-text generative AI" and AI "should not be listed as an
-author" (S11) — which is unenforceable at 32,000 submissions/month.
-
-**7. Mirrors are gone.** The historical arXiv mirror network **shut down after 15 September
-2024** (S24) **[DOC]**. arXiv's reasoning: "arXiv has updated to a fully cloud-centric
-architecture," most mirrors "have shut down on their own or stopped accepting updates," and
-the Fastly CDN now provides global delivery. Practical consequence: **any `xxx.lanl.gov`-era
-or national-mirror URL you find in an old citation is dead**, and there is no longer an
-independent geographic replica of the corpus operated by third parties.
-
-**8. Preservation is now handled by dark archives instead.** In February 2026 arXiv
-announced agreements with **Portico** and **TIB (Leibniz Information Centre for Science and
-Technology)** to hold the corpus as *dark* archives — "preserved but not available for use"
-until a catastrophic-failure scenario (S25) **[DOC]**. This partially replaces what mirrors
-once provided, but it is disaster recovery, not distributed availability.
-
-**9. Governance is in flux — treat 2026 statements as provisional.** arXiv changed legal
-form on 1 July 2026, seated its first Board, and installed its first CEO on 17 August 2026
-(§1, S4–S6). Two Simons Foundation figures sit on the eight-person Board (S6), alongside two
-Cornell/Cornell Tech representatives. arXiv is now formally independent of Cornell while
-remaining physically headquartered in a Cornell Tech building (S3) and structurally close to
-both its former host and its largest funder. That is not an accusation of anything; it is a
-statement that the independence is ten weeks old and its practical meaning is untested.
-
-**10. The Google Cloud migration claim.** **[NOT-VERIFIED]** — see §1. arXiv documents a
-cloud migration but names no provider in any source I retrieved.
-
-**11. `cs` volume statistics are ML statistics.** Any claim of the form "computer science
-research is growing at X%" derived from arXiv is dominated by four ML categories holding
-803,779 of 1,424,149 `cs` category-assignments (§3.6, §7.9). `cs.OS` has grown to 1,455
-papers in 35 years. Do not generalise from the archive to the discipline.
-
-**12. Absence of a paper on arXiv means nothing.** §7.10 is the evidence: MapReduce, GFS,
-Dynamo, Raft, Spark RDDs, ZooKeeper, Spanner, seL4, CompCert and BBR are all absent. arXiv
-is a *sample* of the computing literature with a strong and non-random disciplinary bias,
-not a census.
-
-## 11. Sources
-
-| ID | Source | URL | Retrieved | Supports |
-|---|---|---|---|---|
-| **S1** | arXiv legacy API (Atom), incl. `search_query`, `id_list`, `opensearch:totalResults` | `https://export.arxiv.org/api/query` | 2026-09-01 | §3.5–3.7 counts; all 79 landmark verifications (§7); §7.10 negative title searches; §8.1 gotcha; §10 note 4 |
-| **S2** | arXiv category taxonomy | https://arxiv.org/category_taxonomy | 2026-09-01 | §2 full `cs.*`/`eess.*` enumeration, names, descriptions, alias notes |
-| **S3** | Cornell Chronicle, "Digital research repository arXiv to start new chapter as nonprofit" | https://news.cornell.edu/stories/2026/06/digital-research-repository-arxiv-start-new-chapter-nonprofit | 2026-09-01 | §1 LANL/Ginsparg founding Aug 1991, HEP origin, 2001 Cornell move, HQ at Tata Innovation Center, ">3.08 million" June 2026 |
-| **S4** | arXiv blog, "arXiv is becoming an independent nonprofit" (2026-04-02) | https://blog.arxiv.org/2026/04/02/arxiv-is-becoming-an-independent-nonprofit/ | 2026-09-01 | §1 spinout announcement, 1 July 2026 date, Simons Foundation + Cornell roles, rationale |
-| **S5** | arXiv blog, "arXiv's next chapter: Updates on our spin out from Cornell University" (2026-06-30) | https://blog.arxiv.org/2026/06/30/arxivs-next-chapter/ | 2026-09-01 | §1 spinout confirmation, "free to read and to submit to"; §10 note 3 endorsement comment |
-| **S6** | arXiv blog, "arXiv welcomes inaugural CEO and Board of Directors" (2026-07-30) | https://blog.arxiv.org/2026/07/30/arxiv-welcomes-inaugural-ceo-and-board-of-directors/ | 2026-09-01 | §1 Penelope Lewis CEO eff. 2026-08-17, full Board roster; §5.4, §10 AI-preprint challenge |
-| **S7** | arXiv blog, "arXiv receives $7 million in gifts and grants from Schmidt Sciences and NASA" (2025-11-24) | https://blog.arxiv.org/2025/11/24/arxiv-receives-7-million-in-gifts-and-grants-from-schmidt-sciences-and-nasa/ | 2026-09-01 | §1 funding; cloud migration begun 2023 with Simons support |
-| **S8** | arXiv blog, "arXiv now hosts over 3 million articles" (2026-07-09) | https://blog.arxiv.org/2026/07/09/arxiv-now-hosts-over-3-million-articles/ | 2026-09-01 | §3.1–3.4 milestones, 230 members, 5M monthly users, record months, "many papers appear only on arXiv" |
-| **S9** | arXiv category taxonomy (same page as S2, cited separately for alias statements) | https://arxiv.org/category_taxonomy | 2026-09-01 | §2.1 `cs.NA`→`math.NA`, `cs.SY`→`eess.SY` aliases |
-| **S10** | arXiv monthly submission statistics (CSV export) | https://arxiv.org/stats/monthly_submissions | 2026-09-01 | §3.1–3.4 all computed totals, annual series, record months, milestone recomputation |
-| **S11** | arXiv moderation policy | https://info.arxiv.org/help/moderation/ | 2026-09-01 | §4.2 decline grounds, 3/day rate limit, GenAI policy, moderator identity, appeals; §4.4 permanence and reclassification |
-| **S12** | arXiv endorsement help | https://info.arxiv.org/help/endorsement.html | 2026-09-01 | §4.1 endorsement graph, domains, 3-month–5-year window, anonymity, revocability, "not peer review" |
-| **S13** | arXiv endorsement domains note (within S12/S14) | https://info.arxiv.org/help/endorsement.html | 2026-09-01 | §4.1 physics-as-exception domain structure |
-| **S14** | arXiv blog, "Attention Authors: updated endorsement policy" (2026-01-21) | https://blog.arxiv.org/2026/01/21/attention-authors-updated-endorsement-policy/ | 2026-09-01 | §4.1.1 two-path endorsement, institutional email no longer sufficient, rationale, grandfathering |
-| **S15** | arXiv blog, "Updated endorsement policy for arXiv Mathematics" (2025-12-10) | https://blog.arxiv.org/2025/12/10/updated-endorsement-policy-for-arxiv-mathematics/ | 2026-09-01 | §4.1.1 December 2025 math pilot |
-| **S16** | arXiv blog, "Attention Authors: Updated Practice for Review Articles and Position Papers in arXiv CS Category" (2025-10-31) | https://blog.arxiv.org/2025/10/31/attention-authors-updated-practice-for-review-articles-and-position-papers-in-arxiv-cs-category/ | 2026-09-01 | §4.3 the verified `cs.*` survey/position-paper policy, all quotes; §10 notes 1–2 |
-| **S17** | arXiv withdrawal help | https://info.arxiv.org/help/withdraw.html | 2026-09-01 | §4.4 withdrawal creates a new version; prior versions incl. full text remain; valid/invalid reasons |
-| **S18** | arXiv version availability help | https://info.arxiv.org/help/versions.html | 2026-09-01 | §5.1 version immutability |
-| **S19** | Terms of Use for arXiv APIs | https://info.arxiv.org/help/api/tou.html | 2026-09-01 | §8.2 rate limits (exact quote), permitted/prohibited uses; §9.1, §9.3 metadata CC0 and default-licence statements |
-| **S20** | arXiv OAI-PMH endpoint (`Identify`, `GetRecord`/`arXivRaw`) | https://oaipmh.arxiv.org/oai | 2026-09-01 | §8.3 Identify fields, `earliestDatestamp` 2005-09-16, `deletedRecord=persistent`, data policy; §9.4 licence sampling |
-| **S21** | arXiv Bulk Data Access — Amazon S3 | https://info.arxiv.org/help/bulk_data_s3.html | 2026-09-01 | §8.4 bucket layout, manifest fields, 2.7 TB / 9.2 TB sizes, requester-pays, no-redistribution statement |
-| **S22** | arXiv License Information | https://info.arxiv.org/help/license/ | 2026-09-01 | §9.1–9.3 full licence menu, irrevocability, per-version licences, metadata CC0 |
-| **S23** | Z. K. Silagadze, "On arXiv moderation system" | https://arxiv.org/abs/2307.11791 | 2026-09-01 | §10 note 4 sourced moderation critique (abstract retrieved via S1) |
-| **S24** | arXiv blog, "Attention arXiv users: arXiv mirrors to shut down September 15th, 2024" (2024-09-13) | https://blog.arxiv.org/2024/09/13/attention-arxiv-users-arxiv-mirrors-to-shut-down-september-15th-2024/ | 2026-09-01 | §10 note 7 mirror shutdown, Fastly CDN, cloud-centric architecture |
-| **S25** | arXiv blog, "arXiv future proofs access to research with third-party digital preservation" (2026-02-03) | https://blog.arxiv.org/2026/02/03/arxiv-future-proofs-access-to-research-with-third-party-digital-preservation/ | 2026-09-01 | §10 note 8 Portico and TIB dark-archive agreements |
-| **S26** | *Science*, "ArXiv, the pioneering preprint server, declares independence from Cornell" | https://www.science.org/content/article/arxiv-pioneering-preprint-server-declares-independence-cornell | 2026-09-01 — **retrieval FAILED** | §1 — **[NOT-VERIFIED]**, see note below |
-| **S27** | arXiv blog, "A Year in Review: arXiv's 2025 Annual Report" (2026-06-26) | https://blog.arxiv.org/2026/06/26/a-year-in-review-arxivs-2025-annual-report/ | 2026-09-01 | §1 — annual report PDF retrieved but text extraction failed; not relied upon for any figure |
-
-### Note on S26 — the *Science* article
-
-The URL is **confirmed to exist**: arXiv's own blog post of 2026-04-02 links to it directly
-as "this article in Science, where both Paul Ginsparg, arXiv's founder, and Greg Morrisett,
-dean and vice provost of Cornell Tech … discuss some of the challenges arXiv has faced as it
-grows" (S4). **I could not load it.** `science.org` returned an interstitial
-Cloudflare challenge page ("Just a moment… Enable JavaScript and cookies to continue") on
-every attempt. Following the user-agent ladder in `AGENTS.md`, I tried: default `curl`,
-Chrome 131 desktop, `WhatsApp/2.23.20.0`, and `ChatGPT-User/1.0` — **HTTP 403 on all**. The
-Wayback availability API reports **no archived snapshot** for that URL. The 2026-03-18
-publication date given in the assignment brief is therefore **[NOT-VERIFIED]**.
-
-**However, the substance is fully covered by better primary sources**: the Cornell Chronicle
-article (S3) carries direct quotes from both Ginsparg and Morrisett on the same subject, and
-arXiv's own announcements (S4, S5, S6) document the transition authoritatively. Nothing in
-§1 depends on S26.
-
-### Method note
-
-Category counts, landmark verifications and negative-control title searches were performed
-with a 3.5-second inter-request delay against a single connection, in compliance with S19.
-Working scripts and raw responses are retained in
-`doc/hardware/scratch/preprint-repositories/arxiv/`.
diff --git a/research/preprint-repositories/authorea.md b/research/preprint-repositories/authorea.md
deleted file mode 100644
index 7176497..0000000
--- a/research/preprint-repositories/authorea.md
+++ /dev/null
@@ -1,271 +0,0 @@
-# Authorea — preprint repository record
-
-- **URL:** https://www.authorea.com/
-- **Operator:** **Wiley** (John Wiley & Sons). Originally Authorea, Inc.; acquired by
-  **Atypon** in 2018; Atypon has been Wiley-owned since 2016 (S3, S4) [WEB]. Crossref still
-  records the DOI prefix owner as "Authorea, Inc." while listing the publisher as "Wiley"
-  (S1) [API].
-- **Discipline scope:** multidisciplinary. In practice: Wiley journal submissions plus
-  Earth/space science (§4).
-- **Launched:** **February 2013** (S3) [WEB] · **Status:** active as a corpus, but
-  **direct submissions suspended since May 2026** (S3) [WEB] — see §5.
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-Authorea began as a **collaborative writing tool**, not a repository. Alberto Pepe and
-Nathan Jenkins — who met at CERN — built a web-based real-time collaborative editor for
-scientific manuscripts, with support for embedding data and executable code (S3) [WEB]. The
-preprint-hosting function was a consequence of the editor: if the manuscript already lives
-on the web at a stable URL, giving it a DOI is a small step.
-
-That origin explains most of what is strange about Authorea. It is a **writing platform
-that emits preprints**, so its corpus contains things no curated preprint server would
-carry — including editor demonstration documents (§5.1). It also explains why Authorea
-became attractive to publishers: it is a manuscript pipeline, and a manuscript pipeline can
-be pointed at a journal.
-
-Authorea's second life is as **white-label preprint infrastructure**. Wikipedia records
-that it "expanded as a platform to host branded partner preprint archives, such as the
-Earth Space Science Open Archive and TechRxiv" (S3) [WEB] — a claim this record confirms
-independently from DOI and URL evidence (§4).
-
-Its third life began in **2026**, and is the reason this record is a cautionary tale (§5).
-
-## 2. Scope and content types
-
-Crossref work types under prefix `10.22541`, retrieved 2026-09-01 (S1) [API]:
-
-| Type | Works |
-|---|---|
-| Posted Content (i.e. preprints) | **80,496** |
-| Dataset | 103 |
-| **Total** | **80,599** |
-
-There is no subject taxonomy comparable to arXiv's. Content is organised by *which branded
-archive* it belongs to, which is expressed in the **DOI infix** (§4).
-
-## 3. Size and growth
-
-**80,599 works** under prefix `10.22541` (Crossref, 2026-09-01, S1) [API].
-
-By publication year (S1) [API]:
-
-| Year | Works | | Year | Works |
-|---|---|---|---|---|
-| 2017 | 81 | | 2022 | 9,345 |
-| 2018 | 87 | | 2023 | 12,744 |
-| 2019 | 317 | | 2024 | **17,508** |
-| 2020 | **11,076** | | 2025 | 16,229 |
-| 2021 | 7,426 | | 2026 | **5,683** |
-
-Two inflection points matter.
-
-**The 2020 jump** (317 → 11,076, a 35× increase) is when Authorea stopped being a niche
-writing tool and became publisher infrastructure — consistent with the ESSOAr migration and
-the launch of Wiley's "Under Review" service, under which a submission to a participating
-Wiley journal is automatically posted as an Authorea preprint (S3) [WEB]. Most of this
-corpus is therefore **not** author-initiated preprinting; it is journal submissions
-mirrored into a preprint archive. [INF]
-
-**The 2026 collapse** (16,229 → 5,683, with the year two-thirds elapsed) is the migration
-and submission suspension described in §5. My Crossref counts and Wikipedia's account were
-obtained independently and agree.
-
-**Wikipedia conflict:** the *List of preprint repositories* records Authorea's size as
-**">10,000"** and its operator as **Atypon** (S5) [WEB]. The size is technically true but
-understates by 8×; the operator is one corporate layer out of date (Atypon is the
-subsidiary; Wiley is the owner, S3/S4). Both entries are stale rather than wrong.
-
-## 4. The branded-archive structure — and ESSOAr
-
-**One DOI prefix, multiple archives, distinguished by infix.** From a random sample of 100
-works under `10.22541` (S1) [API]:
-
-| Resource host | Share of sample |
-|---|---|
-| `www.authorea.com` | 83 |
-| `essopenarchive.org` | 17 |
-
-The DOI patterns map onto those hosts:
-
-- `10.22541/au.<digits>.<digits>/v1` → Authorea proper, e.g.
-  `10.22541/au.175225950.03002018/v1`
-- `10.22541/essoar.<digits>.<digits>/v1` → **ESS Open Archive**, e.g.
-  `10.22541/essoar.174708101.14406736/v1`, served from
-  `https://essopenarchive.org/doi/full/…`
-
-**This confirms the ESSOAr relationship directly.** AGU's Earth and Space Science Open
-Archive is not merely "similar to" Authorea — its DOIs are **minted under Authorea's own
-Crossref prefix**, registered to Authorea, Inc. ESSOAr runs on Authorea infrastructure with
-its own domain and branding. [API]
-
-The same pattern independently identifies **TechRxiv** as a migrant onto this stack: current
-TechRxiv DOIs resolve to `www.techrxiv.org/doi/full/10.36227/techrxiv.176281113.30584908/v1`
-(S2) [API] — the identical `/doi/full/<doi>/v<n>` grammar and paired-numeric suffix, differing
-only in that IEEE kept its own prefix. Wikipedia's Authorea article states the same thing in
-prose (S3) [WEB]. Two independent lines of evidence, one inferred from data and one
-documentary, agree.
-
-> **Practical note:** the version suffix is **load-bearing** for ESSOAr DOIs.
-> `https://doi.org/10.22541/essoar.174708101.14406736` returns **HTTP 404**, while the same
-> DOI with `/v1` resolves (S2) [API]. Strip the version from an ESSOAr DOI and you break it.
-
-## 5. Reliability, durability and the 2026 migration
-
-### 5.1 Screening — effectively none, historically
-
-Authorea applied no meaningful screening as a writing platform. The clearest evidence is a
-record that survives in Crossref with a registered DOI (S1) [API]:
-
-> **"This is an example of an interactive Carto graph in Authorea"** —
-> `10.22541/au.155612609.93435564`
-
-That is a **product demonstration page** carrying a permanent scholarly identifier. If a
-demo document is indistinguishable, at the identifier layer, from a research preprint, the
-identifier is telling you nothing about content.
-
-Note that Wiley's own stated reason for suspending submissions in 2026 is in part to
-"improve editorial and integrity screening processes" (S3) [WEB] — an implicit
-acknowledgement that the prior screening was inadequate. [INF]
-
-### 5.2 The durability finding — this is the cautionary tale
-
-**What happened.** Per Wikipedia (S3) [WEB], Authorea "now exists as Wiley's own preprint
-archive following migration of the Authorea and all partner preprint archives to Wiley's own
-**Research Exchange Preprints** platform, launched in **2026**". Further: "Wiley have
-temporarily suspended direct submissions following the migration to Research Exchange
-Preprints in **May 2026**, in order to 'assess new workflows, improve editorial and
-integrity screening processes, and upgrade user support'."
-
-**What I verified independently:**
-
-- Deposits collapsed in 2026 to 5,683 from 16,229 (§3) (S1) [API] — consistent with
-  submissions stopping partway through the year.
-- The corpus itself is **still identified and still resolving**: DOI
-  `10.22541/au.164141365.55966776/v1` resolves through `doi.org` to a live Authorea article
-  URL (S2) [API].
-
-**What this means for anyone who deposited on Authorea.** In under a decade the platform
-went Authorea, Inc. → Atypon (2018) → Wiley → Research Exchange Preprints (2026), with
-submissions suspended at the last step. **The corpus survived each transition; author
-control did not.** A researcher who chose Authorea in 2015 for its collaborative editor is
-now a Wiley platform customer with submissions frozen, and had no say in any of it.
-
-The generalisable lesson: **a preprint that lives inside a product is hostage to that
-product's roadmap.** Zenodo's retention promise is tied to an institution with a 20-year
-research programme; Authorea's was tied to a startup that was acquired twice. Both preserved
-the bits. Only one of them made a commitment about it.
-
-### 5.3 Are the preprints still reachable and citable?
-
-**Citable: yes.** 80,599 DOIs remain registered in Crossref with resolvable targets (S1,
-S2) [API].
-
-**Reachable by a machine: not reliably.** `www.authorea.com` and `essopenarchive.org`
-returned **HTTP 403 to every User-Agent tried** — default, Chrome 131, WhatsApp,
-ChatGPT-User, ClaudeBot, Googlebot 2.1 and Firefox 128 (S2) [WEB]. Body sizes were
-near-identical per agent (5,385–5,622 bytes), indicating a uniform edge bot-block rather
-than agent-specific filtering. I could not read a single Authorea page.
-
-**Reachable by a human: [NOT-VERIFIED].** A 403 to automated clients does not establish
-that a browser is blocked, and per this repository's method I must not claim otherwise. But
-it does mean Authorea content is **effectively invisible to text mining, automated
-citation checking and archival crawlers**, which is itself a durability defect.
-
-A useful discriminator emerged: `doi.org` returns **404** for an unregistered DOI
-(`10.36227/techrxiv.999999999` → 404) but passes through to the target's **403** for a
-registered one. So a 403 here *confirms* the record exists even though it cannot be read
-(S2) [API].
-
-### 5.4 How to sanity-check an Authorea record
-
-1. **Read the DOI infix**: `/au.` = Authorea proper; `/essoar.` = ESS Open Archive. These
-   are different editorial contexts.
-2. **Keep the `/vN` suffix** — required for resolution (§4).
-3. **Ask whether it is a Wiley "Under Review" auto-post**, in which case it is a journal
-   submission under consideration, not an author's deliberate preprint. [INF]
-4. **Do not assume a human curated it** (§5.1).
-5. Query Crossref (`api.crossref.org/works/<doi>`) rather than scraping — the site will
-   refuse you (§5.3).
-
-## 6. Access, APIs and bulk retrieval
-
-- **No public repository API was reachable.** Authorea exposes no documented REST or
-  OAI-PMH endpoint that I could retrieve, and the website is bot-blocked (§5.3).
-- **Use Crossref instead.** Everything quantitative in this record came from
-  `https://api.crossref.org/prefixes/10.22541/works`, which supports `rows`, `sample` and
-  `facet=published` / `facet=type-name` (S1) [API]. This is the practical bulk-access path
-  for Authorea and ESSOAr metadata.
-- **DataCite returns nothing:** `prefix:10.22541` gives `total: 0` in DataCite (S1) [API].
-  Authorea registers with **Crossref**, not DataCite. A zero in one registry is not absence
-  — Crossref's own negative control (`10.99999`) correctly returns **HTTP 404**, so the
-  Crossref counts above are trustworthy while the DataCite zero is merely uninformative.
-- **Full text is not bulk-retrievable** by any route I found. [NOT-VERIFIED]
-
-## 7. Landmark papers
-
-None verified. Authorea is a general-purpose host whose corpus is dominated by Wiley
-journal submissions and Earth/space science; I found no landmark software, systems or
-electronics work that originated here, and I am not going to nominate one on the strength
-of a title search. No table.
-
-## 8. Licensing and reuse
-
-**[NOT-VERIFIED].** I could not retrieve Authorea's licensing policy, its default licence,
-or its text-and-data-mining terms, because every page request was refused with HTTP 403
-(§5.3) and no policy document was reachable by any other route.
-
-What can be said: Crossref metadata for the prefix is available under Crossref's normal
-terms, and the works are typed `Posted Content`. **Assume nothing about reuse rights for
-Authorea full text.** Given Wiley ownership, the prudent default is to treat individual
-items as all-rights-reserved unless the item itself states otherwise.
-
-## 9. Caveats and controversies
-
-1. **Ownership is three layers deep and the public record lags.** Crossref says "Authorea,
-   Inc."; Wikipedia's list says "Atypon"; the actual owner is Wiley (S1, S3, S4, S5).
-2. **Much of the corpus is not voluntary preprinting** but Wiley "Under Review" auto-posting
-   (§3) [INF]. Treating Authorea deposit counts as evidence of preprint culture would be a
-   mistake.
-3. **Submissions are suspended** as of May 2026 (S3) [WEB]. Anyone planning to deposit
-   should verify current status first.
-4. **Demo content carries DOIs** (§5.1).
-5. **The platform is closed to machines** (§5.3), which compromises independent verification
-   — including this record's. Every claim here about Authorea's *content* is mediated through
-   Crossref, not through reading the site.
-6. **Wikipedia is load-bearing for the 2026 migration narrative.** The Research Exchange
-   Preprints migration, the May 2026 suspension date and the quoted Wiley rationale all rest
-   on S3, since the primary notice sits on a page I cannot load. My independent Crossref
-   evidence corroborates the *timing and magnitude* of a submission stoppage but not the
-   stated reasons. Flagged as partially **[NOT-VERIFIED]**.
-
-## 10. Sources
-
-- **S1** — Crossref API: `https://api.crossref.org/prefixes/10.22541`,
-  `/prefixes/10.22541/works` with `rows`, `sample=100`, `facet=published:30` and
-  `facet=type-name:20`; plus DataCite `https://api.datacite.org/dois?query=prefix:10.22541`
-  and the Crossref negative control `/prefixes/10.99999` (HTTP 404). Retrieved
-  **2026-09-01**. Supports: 80,599 total, 80,496 Posted Content / 103 Dataset, the
-  year-by-year table, prefix owner "Authorea, Inc." with publisher "Wiley", the
-  authorea.com/essopenarchive.org host split, the Carto demo record, DataCite absence.
-- **S2** — DOI resolution and HTTP probes: `https://doi.org/10.22541/au.164141365.55966776/v1`,
-  `https://doi.org/10.22541/essoar.174708101.14406736` (404 without version suffix),
-  `https://doi.org/10.36227/techrxiv.176281113.30584908/v1`,
-  `https://doi.org/10.36227/techrxiv.999999999` (negative control, 404); direct requests to
-  `https://www.authorea.com/` and `https://essopenarchive.org/` under seven User-Agents.
-  Retrieved 2026-09-01. Supports: §4 version-suffix requirement, §5.3 bot-block findings and
-  the 403-vs-404 discriminator.
-- **S3** — Wikipedia, *Authorea*, retrieved via the MediaWiki API 2026-09-01. Supports:
-  February 2013 launch by Alberto Pepe and Nathan Jenkins with Matteo Cantiello (met at
-  CERN), 2018 Atypon acquisition, Wiley ownership, branded partner archives including ESSOAr
-  and TechRxiv, Wiley "Under Review" auto-posting, the 2026 migration to Research Exchange
-  Preprints, and the May 2026 suspension of direct submissions with the quoted rationale.
-- **S4** — Wikipedia, *Atypon*, retrieved via the MediaWiki API 2026-09-01. Supports:
-  Atypon founded 1996, Literatum platform, **owned by John Wiley & Sons since October 2016**
-  — the link that makes Authorea a Wiley property.
-- **S5** — Wikipedia, *List of preprint repositories*, wikitext via MediaWiki API,
-  2026-09-01. Supports: the ">10,000" size entry, 2013 launch year, and "Atypon" as listed
-  operator, all compared against measured values in §3.
diff --git a/research/preprint-repositories/biohackrxiv.md b/research/preprint-repositories/biohackrxiv.md
deleted file mode 100644
index 1bc0a48..0000000
--- a/research/preprint-repositories/biohackrxiv.md
+++ /dev/null
@@ -1,330 +0,0 @@
-# BioHackrXiv — preprint repository record
-
-- **URL:** https://biohackrxiv.org/ (redirects to `https://osf.io/preprints/biohackrxiv/`)
-- **Operator:** Hosted on **OSF Preprints**, infrastructure run by the **Center for Open
-  Science**. Editorially steered by a community committee drawn from DBCLS, ZB MED, ELIXIR
-  Europe and UTHSC (§4).
-- **Discipline scope:** advertised as "Preprints for BioHackathons" (S2) [API] — in
-  practice, **bioinformatics tooling, workflow systems, semantic-web infrastructure and
-  FAIR data engineering** (§2, §6).
-- **Launched:** 2020 (earliest deposits date from 2020, S1) [API] · **Status:** active,
-  accepting submissions (S2) [API]
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-BioHackrXiv exists to solve a specific and under-served problem: **hackathons produce real
-technical work that has no publication venue.** A week-long BioHackathon or CodeFest sprint
-yields working code, schema mappings, API bridges, container recipes and workflow modules —
-outputs that are too small, too incremental or too infrastructural for a journal, but which
-represent genuine engineering effort that should be citable and creditable.
-
-BioHackrXiv gives those outputs a **DOI-bearing project report**. Its own strapline is
-"Preprints for BioHackathons" (S2) [API], and its scope covers "works done during
-BioHackathons, CodeFests, Sprints or similar events" (S5) [WEB].
-
-For this knowledge base the relevance is direct: **this is a preprint server where the
-subject matter is software and data infrastructure**, not laboratory results. If you work on
-workflow engines, data standards, ontologies or research-software plumbing, BioHackrXiv is
-where the ELIXIR/Galaxy/Nextflow community writes down what it built and why.
-
-It is small — 163 works — and that is the point. It is a **narrow, high-signal corpus**,
-not a general repository.
-
-## 2. Scope and taxonomy
-
-BioHackrXiv uses OSF's subject taxonomy. A retrieved record carries
-`Life Sciences → Bioinformatics` (S1) [API], plus free-text tags (e.g. `bioinformatics`,
-`computational biology`, `federated learning`, `hackathon`).
-
-The corpus's real subject structure is better shown by what the text actually contains.
-Keyword occurrence across **all 173 records** (title + description), 2026-09-01 (S1) [API]:
-
-| Term | Records | Term | Records |
-|---|---|---|---|
-| workflow | **43** | ontology | 19 |
-| FAIR | **42** | Galaxy | 16 |
-| ELIXIR | **39** | SPARQL | 16 |
-| RDF | 25 | Bioschemas | 15 |
-| API | 20 | container | 8 |
-| Nextflow | 4 | Docker | 2 |
-| Snakemake | 4 | WDL | 0 |
-| CWL | 4 | | |
-
-**A quarter of the corpus mentions workflows; a quarter mentions FAIR; 39 of 163 works
-mention ELIXIR.** That is an unusually concentrated infrastructure focus for a preprint
-server.
-
-Note the named workflow engines individually score low (Nextflow 4, Snakemake 4, CWL 4,
-WDL 0) while generic "workflow" scores 43. The corpus talks about workflows *as a class* —
-portability, provenance, registries, execution — more than it advocates particular engines.
-[INF]
-
-## 3. Size and growth
-
-Retrieved from the OSF API, 2026-09-01 (S1) [API]. The complete corpus was paginated in
-full, not sampled:
-
-- **173 version-records** (`filter[provider]=biohackrxiv`)
-- **163 unique works** after stripping `_vN` suffixes
-- **9 works have more than one version**
-- **172 published**, 1 withdrawn, 0 orphaned
-
-By publication year (version-records):
-
-| Year | Records |
-|---|---|
-| 2020 | 10 |
-| 2021 | 11 |
-| 2022 | 10 |
-| 2023 | 29 |
-| 2024 | 35 |
-| 2025 | **44** |
-| 2026 | 34 (year incomplete at retrieval) |
-
-Flat at ~10/year for three years, then a step change from 2023 and sustained growth. With
-34 records by 1 September 2026, the year is tracking near the 2025 level. This is a small
-but **healthy and growing** venue, not a stalled experiment.
-
-> **Distinguish these two numbers.** "173" is version-records; "163" is distinct works.
-> The difference matters at this scale — quoting 173 as the number of reports overstates by
-> 6%. Wikipedia's *List of preprint repositories* gives **">100"** with a 2020 year and
-> "Center for Open Science" as operator (S4) [WEB]; that is **correct but coarse**, and it
-> is the only entry among the five platforms in this batch whose Wikipedia size claim I
-> found to be accurate.
-
-## 4. Screening and moderation — what gets in
-
-**BioHackrXiv is moderated.** The OSF provider metadata declares
-`reviews_workflow: pre-moderation` (S2) [API] — submissions are reviewed **before** they
-appear, which is a stronger gate than Zenodo, figshare or Authorea apply.
-
-Corroborated by the records themselves: every record carries a `reviews_state`, distributed
-as **`accepted` 172, `withdrawn` 1** (S1) [API]. A moderation state machine is genuinely
-in use.
-
-Provider settings also show `allow_submissions: true` and `assertions_enabled: true`
-(S2) [API] — the latter meaning OSF's conflict-of-interest and data-availability assertions
-are required. Those assertions are populated in practice: `has_data_links` is
-`available` for **53** records, `not_applicable` for 108, `no` for 4 (S1) [API]. So a third
-of reports link to the data or code they describe, in a structured, machine-readable field.
-
-**Steering Committee**, from the provider's advisory board metadata (S2) [API]:
-
-| Member | Affiliation |
-|---|---|
-| Toshiaki Katayama | DBCLS |
-| Leyla Garcia | ZB MED |
-| Jennifer Harrow | ELIXIR Europe |
-| Pjotr Prins | UTHSC |
-| Alexander Garcia | (affiliation truncated in retrieved metadata) |
-
-That is a genuine bioinformatics-infrastructure committee, not a nominal board.
-
-**What pre-moderation does and does not mean:** it is a scope-and-suitability check, not
-peer review. It establishes that a report is a real hackathon output rather than spam. It
-does **not** establish that the software works, the benchmarks are sound, or the approach is
-novel.
-
-## 5. Reliability — what you can and cannot trust
-
-**What a BioHackrXiv DOI gives you:** a timestamp, a Crossref-resolvable DOI under the
-`10.37044` prefix, OSF hosting, a moderation pass (§4), structured COI and data-availability
-assertions, and version history where versions exist.
-
-**What it does not give you:** peer review, reproducibility validation, or any guarantee the
-described tool still exists. Hackathon reports describe software at a moment of maximum
-optimism; a report from a 2021 CodeFest may describe a prototype that was never maintained.
-**Check the linked repository's commit history before relying on anything described here.**
-[INF]
-
-**Verified resolution behaviour** (S3) [API]:
-
-- `https://doi.org/10.37044/osf.io/h6zqj_v2` → **HTTP 200**, resolving to
-  `https://osf.io/h6zqj_v2`.
-- Negative control `https://doi.org/10.37044/osf.io/zzzzz_v9` → **HTTP 404**.
-
-So **DOIs discriminate correctly**. Web URLs do not — see the warning below.
-
-> ### ⚠ Negative control: OSF web URLs return 200 for records that do not exist
->
-> Probed 2026-09-01 (S3) [WEB]:
->
-> | URL | Result |
-> |---|---|
-> | `https://biohackrxiv.org/` | HTTP 200, **4,207 bytes** |
-> | `https://biohackrxiv.org/h6zqj_v2` (real) | HTTP 200, **4,207 bytes** |
-> | `https://biohackrxiv.org/ZZZNOTREAL999` (bogus) | HTTP 200, **4,207 bytes** |
->
-> All three return **byte-identical** responses, because OSF is a JavaScript
-> single-page application that serves the same shell for every path and resolves content
-> client-side.
->
-> **Consequence:** for OSF-hosted preprint servers, an HTTP 200 — and even a byte-size
-> check, which this repository's method normally recommends — proves **nothing**. Link
-> checkers will report broken preprints as healthy. **Verify via the OSF API or via DOI
-> resolution, never via the web URL.**
-
-## 6. What you actually find there — examples
-
-All verified present in the corpus on 2026-09-01 (S1) [API]. DOIs use the `10.37044/osf.io/`
-prefix; the landing page is `https://biohackrxiv.org/<id>`.
-
-**Workflow systems and execution**
-
-| Report | DOI suffix | Date |
-|---|---|---|
-| Snakemake Hackathon 2026 | `h6zqj_v2` | 2026-04-29 |
-| BiocExecute: Make package functions or workflows executable from the command line | `ywsmq_v1` | 2026-06-19 |
-| Eurobioc2026 BiocContainer Report | `acxky_v1` | 2026-06-15 |
-| Evolving FAIR Image Analysis in Galaxy for Cross-domain and AI-ready Applications | `tsxby_v1` | 2026-03-31 |
-
-**Semantic web, RDF and data standards**
-
-| Report | DOI suffix | Date |
-|---|---|---|
-| Variant representation in RDF | `jazsb_v1` | 2026-08-09 |
-| Variant annotation in RDF for clinical trials matching | `2hbqf_v1` | 2026-08-09 |
-| Schema-Driven Generation of Synthetic HL7 FHIR RDF Data from Shape Expressions (ShEx) | `3gak2_v2` | 2026-08-06 |
-| Rendering SSSOM ontology mappings as RDF named graphs and RDF 1.2 triple terms | `auhzg_v1` | 2026-06-14 |
-| Leveraging RDF and CURIE metadata resolution with identifiers.org | `xza73_v1` | 2025-06-02 |
-
-**Research-software ecosystem and registries**
-
-| Report | DOI suffix | Date |
-|---|---|---|
-| Bidirectional bridge: GitHub ⇄ bio.tools | `8ktd6_v1` | 2026-02-24 |
-| Enhancing bio.tools by Semantic Literature Mining | `8m5ey_v1` | 2025-05-04 |
-| Software Quality Indicators: extraction, categorisation and recommendations from canonical sources | `etp3g_v1` | 2025-06-11 |
-| METRICS — Monitoring of Key Performance Indicators for ELIXIR Services | `2jgk4_v1` | 2026-01-22 |
-| BioHackEU24 report: Integrating Bioconductor packages with the ELIXIR Research Software Ecosystem | `dsgnw_v1` | 2025-04-08 |
-
-**Newer machine-learning and LLM infrastructure**
-
-| Report | DOI suffix | Date |
-|---|---|---|
-| Towards Federated Learning Across Biobanks: Prototype Software from the 2026 CMU–NVIDIA Hackathon | `5psfj_v2` | 2026-08-27 |
-| MCP server tools with RDF shapes | `8qeh5_v1` | 2025-12-16 |
-| Measure before you rewrite: ablation-driven redesign of LLM-facing RDF schema documentation in TogoMCP | `6v5ra_v1` | 2026-07-26 |
-
-Note `Bidirectional bridge: GitHub ⇄ bio.tools` and the two MCP/LLM entries: this corpus
-tracks current tooling practice closely, and the reports are often the **only written record**
-of an integration that exists as a few hundred lines of glue code.
-
-## 7. Landmark papers
-
-None, and the concept does not apply. BioHackrXiv publishes **project reports**, not
-field-defining results. Its value is documentary and archaeological — it records how
-bioinformatics infrastructure actually got built, by whom, and at which event. No table.
-
-## 8. Who should care
-
-- **Workflow and pipeline engineers** — Nextflow, Snakemake, CWL, Galaxy: design
-  discussions and integration reports that never reach a journal.
-- **Data-standards and semantic-web practitioners** — RDF/SPARQL/ShEx/SSSOM/Bioschemas work
-  is disproportionately represented (§2).
-- **Research-software engineers** — software quality indicators, registries (bio.tools),
-  packaging and container practice.
-- **FAIR / open-science infrastructure people** — 42 of 163 works mention FAIR.
-- **Anyone tracing provenance of a bioinformatics tool** — hackathon reports frequently
-  document the origin of a component whose repository history alone does not explain it.
-
-Not useful for: electronics, firmware, or hardware design. Despite being software-centric,
-BioHackrXiv is **life-sciences software** throughout. [INF]
-
-## 9. Access, APIs and bulk retrieval
-
-**OSF API v2 — fully open, no key required for public reads** (S1) [API]:
-
-```
-https://api.osf.io/v2/preprints/?filter[provider]=biohackrxiv&page[size]=100
-```
-
-- Returns JSON:API with `links.meta.total` (**173**) and `links.next` for pagination.
-- **The entire corpus paginates in two requests** at `page[size]=100`. Bulk retrieval is
-  trivial at this scale; there is no excuse for sampling.
-- Provider metadata: `https://api.osf.io/v2/preprint_providers/biohackrxiv/`
-- Licence vocabulary: `https://api.osf.io/v2/preprint_providers/biohackrxiv/licenses/`
-- Useful per-record attributes: `date_published`, `doi`, `reviews_state`, `date_withdrawn`,
-  `is_latest_version`, `version`, `has_data_links`, `data_links`, `has_coi`, `subjects`,
-  `tags`, `license_record`.
-
-**Rate limits:** not observed in headers during retrieval; the full corpus was fetched
-without throttling. **[NOT-VERIFIED]** as to published limits — be considerate regardless.
-
-**OAI-PMH:** OSF's endpoint for provider-scoped harvesting was **not verified** in this
-pass. The REST API is sufficient at this corpus size.
-
-**Community entry points** (S2, S5) [WEB]: `https://guide.biohackrxiv.org/` (about and
-submission guidelines) and `https://index.biohackrxiv.org/` (hackathon preprint index).
-**[NOT-VERIFIED]** — referenced in provider metadata but not independently loaded.
-
-**Negative controls:** see the boxed warning in §5 — the DOI-level control behaves
-correctly (404), the web-URL control does not (false 200). A Zenodo community lookup for
-`biohackrxiv` returns **HTTP 404**, confirming BioHackrXiv has no Zenodo presence and lives
-solely on OSF (S1) [API].
-
-## 10. Licensing and reuse
-
-**Author-chosen from three options**, retrieved from the provider's licence endpoint,
-2026-09-01 (S1) [API]:
-
-| Licence |
-|---|
-| CC-BY Attribution 4.0 International |
-| CC0 1.0 Universal |
-| CC-BY Attribution-NonCommercial-NoDerivatives 4.0 International |
-
-Two of the three are fully open; **CC-BY-NC-ND is available and does restrict reuse and
-derivative work**, so check `license_record` per item rather than assuming the corpus is
-uniformly open. Records carry a `default_license_id` field.
-
-Metadata is served openly through the OSF API, making **metadata mining unproblematic**.
-Full-text mining depends on the per-item licence. [INF]
-
-## 11. Caveats and controversies
-
-1. **Small corpus.** 163 works. Do not draw statistical conclusions from keyword counts in
-   §2 — they are descriptive, not inferential.
-2. **Reports describe software at peak optimism.** Verify the tool still exists (§5).
-3. **The OSF SPA false-200 problem** (§5) is the single most important operational caveat,
-   and it affects *every* OSF-hosted preprint server, not just this one.
-4. **Version-records vs works** — 173 vs 163 (§3).
-5. **Platform dependency.** BioHackrXiv has no independent infrastructure; it is a branded
-   view of OSF Preprints. Its continuity is the Center for Open Science's continuity. That
-   is a considerably better position than a commercial platform, but it is a
-   single-point dependency and should be named as one. [INF]
-6. **One withdrawn record** exists (§3, §4) — withdrawals do happen and are tracked in
-   `date_withdrawn` / `reviews_state`.
-
-## 12. Sources
-
-- **S1** — OSF API v2: `https://api.osf.io/v2/preprints/?filter[provider]=biohackrxiv`
-  (full corpus paginated at `page[size]=100`), plus
-  `https://api.osf.io/v2/preprint_providers/biohackrxiv/licenses/` and a Zenodo
-  communities control (`/api/communities/biohackrxiv` → HTTP 404). Retrieved
-  **2026-09-01**. Supports: 173 version-records / 163 unique works / 9 multi-version works,
-  the year table, `reviews_state` distribution (172 accepted, 1 withdrawn),
-  `has_data_links` distribution, subject and tag structure, the licence vocabulary, and all
-  titles, DOI suffixes and dates in §6.
-- **S2** — OSF API v2 provider record,
-  `https://api.osf.io/v2/preprint_providers/biohackrxiv/`. Retrieved 2026-09-01. Supports:
-  provider name and description ("Preprints for BioHackathons"),
-  `reviews_workflow: pre-moderation`, `allow_submissions: true`, `assertions_enabled: true`,
-  `domain: https://biohackrxiv.org/`, the Steering Committee membership, and the
-  `guide.biohackrxiv.org` / `index.biohackrxiv.org` links.
-- **S3** — Resolution and negative-control probes, 2026-09-01:
-  `https://doi.org/10.37044/osf.io/h6zqj_v2` (HTTP 200 → `osf.io/h6zqj_v2`);
-  `https://doi.org/10.37044/osf.io/zzzzz_v9` (HTTP 404); and HTTP probes of
-  `https://biohackrxiv.org/`, `https://biohackrxiv.org/h6zqj_v2` and
-  `https://biohackrxiv.org/ZZZNOTREAL999`, all returning HTTP 200 at 4,207 bytes.
-  Supports: §5 resolution behaviour and the SPA false-200 finding.
-- **S4** — Wikipedia, *List of preprint repositories*, wikitext via the MediaWiki API,
-  2026-09-01. Supports: the ">100" size claim, 2020 year, and "Center for Open Science"
-  operator, as compared against measured values in §3.
-- **S5** — BioHackrXiv description and submission-guideline links as published in the OSF
-  provider metadata (S2), pointing to `http://guide.biohackrxiv.org/about.html` and
-  `http://guide.biohackrxiv.org/submission_guidelines.html`. Retrieved 2026-09-01 via the
-  provider record; the guide pages themselves were **not independently loaded**.
diff --git a/research/preprint-repositories/biorxiv-and-medrxiv.md b/research/preprint-repositories/biorxiv-and-medrxiv.md
deleted file mode 100644
index b576ac7..0000000
--- a/research/preprint-repositories/biorxiv-and-medrxiv.md
+++ /dev/null
@@ -1,626 +0,0 @@
-# bioRxiv and medRxiv — preprint repository record
-
-- **URLs:** https://www.biorxiv.org/ · https://www.medrxiv.org/
-  · operator: https://openrxiv.org/ · API: https://api.biorxiv.org/
-- **Operator:** **openRxiv**, an independent US non-profit (OPENRXIV CORP, 417 Mace Blvd
-  STE J110, Davis, CA 95618), since **2025-03-11** (S1, S6). Before that both were run by
-  **Cold Spring Harbor Laboratory** (CSHL); medRxiv under a management partnership of
-  CSHL + **Yale University School of Medicine** + **BMJ Group** (S2). Principal funder
-  throughout: the **Chan Zuckerberg Initiative** (S2, S3, S6).
-- **Discipline scope:** bioRxiv — all of the biological sciences, *excluding* clinical
-  work. medRxiv — health sciences, clinical and public-health research. The two are
-  co-managed but have **separate scope and screening policies**, and cross-posting is
-  forbidden (S6, S7).
-- **Launched:** bioRxiv **2013**, medRxiv **2019** (S2) · **Status:** both **active** and
-  at record volume (§4).
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What they are
-
-bioRxiv is the arXiv of biology, and it worked. Founded at Cold Spring Harbor Laboratory
-in 2013 by John Inglis and Richard Sever with the stated goal of "establishing the use of
-preprints as a journal-independent method of distributing life science research results"
-(S2), it took a discipline with essentially no preprint culture — biology in 2013 posted
-almost nothing ahead of review — and made preprinting normal within about six years.
-**347,954 new preprints** through 2026-09-01 (S4). medRxiv, launched 2019 for health and
-clinical science, adds **88,194** (S5). openRxiv's own summary — "over 430,000 preprints
-… 5,000 new research articles are posted each month" (S2) — matches the API totals to
-within rounding, which is a good sign for a self-reported figure.
-
-For a knowledge base about hardware and systems these are mostly out of scope, and this
-record is deliberately shorter than the arXiv one. But two things make them worth a
-proper entry. First, **bioRxiv's `Bioinformatics` category is one of the largest venues
-in the world for announcing scientific software** — Bioconda, Kraken 2, Scanpy, Salmon,
-ColabFold and Nextstrain all appeared here before their journal versions (§6). Second,
-bioRxiv and medRxiv are the **only major preprint servers that publish a measured,
-machine-readable preprint-to-publication rate** (§5). Almost every other record in this
-collection has to say "eventual publication rate: not measured". Here you can compute it
-yourself, and that number is the single most useful reliability statistic in this pass.
-
-Both are free to post and free to read, carry no article-processing charge, assign
-Crossref DOIs under the `10.1101/` prefix, are archived at **Portico**, and are indexed
-by Crossref, Google Scholar, Semantic Scholar, Europe PMC and the Web of Science Preprint
-Citation Index; NIH-funded preprints are additionally indexed in PubMed (S6, S7).
-
-## 2. Governance — the 2025 move to openRxiv
-
-**Verified.** On **2025-03-11** openRxiv was announced as "an independent nonprofit to
-oversee bioRxiv and medRxiv" (S1, dated post). A second post the same day advertised for
-its inaugural CEO (S8). What actually changed:
-
-| Before (to 2025-03) | After (openRxiv) |
-|---|---|
-| Services *of* CSHL, with Yale/BMJ partnership for medRxiv | Separate 501(c)-style non-profit corporation, `OPENRXIV CORP`, Davis CA (S6 DMCA agent address) |
-| Governance inside a host laboratory | **6-member board of directors**: Scott Fraser (chair), Edith Heard, Jeff Huber, Harlan Krumholz, Bruce Stillman, Shirley Tilghman (S9) |
-| Advisory input ad hoc | **Scientific and Medical Advisory Board (SMAB)**, chaired by John Inglis, deputy chair Theodora Bloom; ~15 members (S2). Inaugural meeting reported **2025-07-22** (S10) |
-| CZI grants to CSHL (PI: John Inglis, "sequential major grants … since 2017") (S2) | **CZI provided three years of seed funding** to launch the organisation; one of six board seats has a CZI affiliation (S9) |
-
-The substance, per openRxiv's own Q&A (S9): the board "approves key policies, provides
-strategic guidance, and oversees executive leadership"; board members serve "as individual
-supporters of its mission, not institutional representatives"; and "funding agreements do
-not include stipulations that impact editorial independence". openRxiv is explicit that it
-**is not itself a preprint server** and that **no server policies changed** as a result of
-the transition — bioRxiv and medRxiv "continue operating as separate platforms but with
-common technologies, complementary policies, and a single team" (S2, FAQ).
-
-Personnel since: **Tracy Teal** appointed inaugural CEO **2025-08-18** (S10); Gabriel Stein
-Head of Product **2026-06-30** (S11). Inglis and Sever received the Royal Society's 2025
-Research Culture Award (S10, dated 2025-08-28) — [COM], as reported by openRxiv itself.
-
-**Honest read [INF]:** the governance change is real and is the right kind of move
-(single-institution dependency → dedicated non-profit with an external board), but the
-funding concentration did not change much. CZI remains the dominant funder and holds a
-board seat. openRxiv says it is "pursuing diversified funding models" (S9); as of
-2026-09-01 the published supporter list is still CZI + CSHL + Sergey Brin Family
-Foundation + Robert Lourie Foundation + a dozen universities (S2). Treat "sustainable"
-as an aspiration with a three-year runway, not an accomplished fact.
-
-## 3. Scope and subject taxonomy
-
-**bioRxiv: ~25 author-selected categories, one per preprint** (S6). Verified exhaustive
-against the API: the 27 category names below sum to exactly the server-wide 2025 total of
-49,318 (§4), so the list is complete.
-
-Two of them are **closed to new submissions** — `Clinical Trials` and `Epidemiology` were
-retired when medRxiv launched in 2019 and now accept only revisions to existing papers
-(S6). Note the API's behaviour here (§10): querying those categories silently returns
-*all* categories rather than an error.
-
-**medRxiv: ~50 categories** (S7), health-specialty oriented (Cardiovascular Medicine,
-Infectious Diseases, Oncology, Public and Global Health, Health Informatics, …).
-
-Both servers are explicit about what is **out of scope** (S6, S7): no narrative reviews,
-no editorials/opinion, no hypothesis-only articles, no theses or teaching material, no
-protocols or "tool announcements" on their own, no product advertisements, no standalone
-figures or datasets. medRxiv additionally excludes case reports and series, preclinical
-work, veterinary studies and rebuttals. **The tool-announcement exclusion matters for the
-software reader**: bioRxiv will not take a bare software paper. Its own wording — "software
-announcements that do not include detailed methods and research data produced by their
-output/application" are not sufficient (S6). A bioinformatics preprint here therefore
-tends to come with a benchmark, not just a repository link.
-
-## 4. Size and growth
-
-All figures **[API]**, retrieved **2026-09-01**.
-
-**bioRxiv**, from `https://api.biorxiv.org/sum/y` (S4) — note this endpoint counts *new
-papers* separately from *revisions*:
-
-| Year | New preprints | Cumulative | Revisions |
-|---|---|---|---|
-| 2013 | 109 | 109 | 34 |
-| 2014 | 886 | 995 | 372 |
-| 2015 | 1,774 | 2,769 | 776 |
-| 2016 | 4,718 | 7,487 | 1,903 |
-| 2017 | 11,339 | 18,826 | 4,625 |
-| 2018 | 20,778 | 39,604 | 7,786 |
-| 2019 | 29,179 | 68,783 | 10,683 |
-| 2020 | 38,717 | 107,500 | 14,323 |
-| 2021 | 36,866 | 144,366 | 14,424 |
-| 2022 | 35,750 | 180,116 | 12,838 |
-| 2023 | 39,155 | 219,271 | 14,804 |
-| 2024 | 43,632 | 262,903 | 16,936 |
-| 2025 | 49,318 | 312,221 | 17,893 |
-| 2026 (to 09-01) | 35,733 | **347,954** | 13,432 |
-
-**medRxiv**, from `count_new_papers` on `details/medrxiv/<year>` (S5):
-
-| Year | New preprints | Cumulative |
-|---|---|---|
-| 2019 (from Jun) | 913 | 913 |
-| 2020 | 14,070 | 14,983 |
-| 2021 | 12,738 | 27,721 |
-| 2022 | 10,527 | 38,248 |
-| 2023 | 11,046 | 49,294 |
-| 2024 | 12,863 | 62,157 |
-| 2025 | 15,000 | 77,157 |
-| 2026 (to 09-01) | 11,037 | **88,194** |
-
-**Combined: 436,148 preprints.** Growth is *not* flattening: 2025 was bioRxiv's largest
-year ever and 2026 is on pace to beat it. The COVID bump is visible as a 2020 spike
-followed by a 2021–22 dip on both servers, then recovery.
-
-**Recorded conflict.** The openRxiv homepage on 2026-09-01 displays "**273,956** articles"
-for bioRxiv and "**65,414** articles" for medRxiv (S3) [WEB]. Both are far below the API
-totals. Cross-referencing the cumulative tables above places 273,956 in bioRxiv's early
-2025 and 65,414 in medRxiv's early 2025 — i.e. **the homepage counters appear frozen at
-the March-2025 openRxiv launch and have not been updated since** [INF]. The About page on
-the same site says "over 430,000", which agrees with the API. Use the API.
-
-**Usage**, from `api.biorxiv.org/usage/y/<server>` (S12): bioRxiv 2025 saw 8,842,153
-abstract views, 2,350,894 full-text views and 4,864,664 PDF downloads; cumulative PDF
-downloads reached 21,963,655 by end-2025. medRxiv cumulative abstract views 26,052,977.
-(medRxiv's series carries a blank-year bucket of 3.28M views, presumably pre-2019
-backfill or unattributed — treat the medRxiv year-splits as approximate.)
-
-## 5. The measured preprint-to-publication rate
-
-This is the section to steal for other records. bioRxiv/medRxiv link each preprint to its
-journal version automatically (usually within ~2 weeks of publication, S6), and expose
-that link in the API. So the rate is *measurable*, not estimated.
-
-**Server-wide, all time** [API], 2026-09-01, from `api.biorxiv.org/pubs/<server>/<range>`
-which reports a `total` of preprint→publication links (S13):
-
-| Server | Preprints | With a linked journal publication | Raw rate |
-|---|---|---|---|
-| bioRxiv | 347,954 | **177,932** | **51.1 %** |
-| medRxiv | 88,194 | **39,885** | **45.2 %** |
-
-That raw rate is a **lower bound** and badly censored: a third of bioRxiv's corpus was
-posted in the last two years and has not had time to be published.
-
-**Cohort measurement** is the honest version. I sampled fixed calendar windows, deduped
-by DOI across versions, and counted records whose `published` field is not `NA`
-[API, 2026-09-01, script `scratch/preprint-repositories/lifesci/cohort.py`]:
-
-| Server | Cohort window | Unique preprints | Published | Rate |
-|---|---|---|---|---|
-| bioRxiv | 2016-05-01 … 05-07 | 108 | 84 | **77.8 %** |
-| bioRxiv | 2018-05-01 … 05-07 | 467 | 332 | **71.1 %** |
-| bioRxiv | 2019-05-01 … 05-07 | 661 | 457 | **69.1 %** |
-| bioRxiv | 2020-05-01 … 05-07 | 1,137 | 817 | **71.9 %** |
-| bioRxiv | 2022-05-01 … 05-07 | 951 | 560 | 58.9 % (censored) |
-| bioRxiv | 2024-05-01 … 05-07 | 1,077 | 546 | 50.7 % (censored) |
-| bioRxiv | 2025-05-01 … 05-07 | 1,080 | 511 | 47.3 % (heavily censored) |
-| medRxiv | 2019-10-01 … 10-31 | 189 | 151 | **79.9 %** |
-| medRxiv | 2020-05-01 … 05-07 | 575 | 371 | **64.5 %** |
-| medRxiv | 2022-05-01 … 05-07 | 246 | 133 | 54.1 % (censored) |
-| medRxiv | 2024-05-01 … 05-07 | 330 | 144 | 43.6 % (censored) |
-
-**Headline number: for mature bioRxiv cohorts (2016–2020, ≥6 years elapsed), 69–78 % of
-preprints have a linked peer-reviewed journal publication.** medRxiv's small 2019 cohort
-is comparable at 80 %; its 2020 COVID cohort is lower at 64.5 %, consistent with a large
-volume of pandemic-era material that never cleared review.
-
-This **agrees with the operator's own claim** — openRxiv states "75 % of bioRxiv and
-medRxiv preprints go on to be published in peer-reviewed journals" (S9) [DOC] — and with
-the published literature: Abdill & Blekhman's *eLife* 2019 study of the whole bioRxiv
-corpus found a comparable outcome rate (S14; itself posted as bioRxiv `10.1101/515643`,
-2019-01-13, before *eLife* `10.7554/eLife.45133`).
-
-**Caveats on the rate.** (a) The link is Crossref-matched and openRxiv itself admits "on
-rare occasions a match is not made for technical reasons" (S6) — so it slightly
-*under*-counts. (b) "Published" says nothing about *where*; the linked venue ranges from
-*Nature* to predatory. (c) The complement is not "rejected": it mixes rejected work,
-abandoned work, work published without a detected link, and work whose authors never
-submitted. (d) The trend across cohorts is downward even allowing for censoring — the
-2016 cohort is 78 % after 10 years, the 2018 cohort 71 % after 8. [INF] Worth watching,
-but do not over-read it from these sample sizes.
-
-## 6. The software angle — bioinformatics and computational biology
-
-`Bioinformatics` is bioRxiv's second-largest category and a first-class venue for
-scientific software. Counts [API], year-by-year query of
-`details/biorxiv/<year>?category=bioinformatics`, retrieved 2026-09-01 (S15):
-
-| Year | Bioinformatics preprints | | Year | Bioinformatics preprints |
-|---|---|---|---|---|
-| 2013 | 14 | | 2020 | 3,089 |
-| 2014 | 159 | | 2021 | 2,918 |
-| 2015 | 313 | | 2022 | 3,003 |
-| 2016 | 707 | | 2023 | 3,245 |
-| 2017 | 1,286 | | 2024 | 3,609 |
-| 2018 | 1,929 | | 2025 | 4,235 |
-| 2019 | 2,347 | | 2026 (to 09-01) | 3,509 |
-
-**Total: 30,363 preprints**, 8.7 % of bioRxiv.
-
-Full 2025 category ranking [API] (sums to 49,318 = the server total, so this is complete):
-
-| Rank | Category | 2025 | Rank | Category | 2025 |
-|---|---|---|---|---|---|
-| 1 | Neuroscience | 9,071 | 15 | Physiology | 1,027 |
-| 2 | **Microbiology** | 4,651 | 16 | **Systems Biology** | 892 |
-| 3 | **Bioinformatics** | 4,235 | 17 | Animal Behavior & Cognition | 758 |
-| 4 | Cell Biology | 2,921 | 18 | Pharmacology & Toxicology | 626 |
-| 5 | Cancer Biology | 2,487 | 19 | **Synthetic Biology** | 525 |
-| 6 | **Biophysics** | 2,283 | 20 | Pathology | 385 |
-| 7 | Immunology | 2,280 | 21 | Zoology | 265 |
-| 8 | Biochemistry | 2,261 | 22 | Sci. Communication & Education | 127 |
-| 9 | Molecular Biology | 2,118 | 23 | Paleontology | 74 |
-| 10 | Ecology | 2,103 | — | Clinical Trials | closed |
-| 11 | Genomics | 2,038 | — | Epidemiology | closed |
-| 12 | **Bioengineering** | 1,967 | | | |
-| 13 | Evolutionary Biology | 1,880 | | | |
-| 14 | Plant Biology | 1,789 | | | |
-
-The five bolded computational/physical categories — Bioinformatics, Biophysics,
-Bioengineering, Systems Biology, Synthetic Biology — total **9,902 in 2025, 20.1 % of the
-server**. `Biophysics` and `Bioengineering` are where the instrumentation lives: cryo-EM
-detector and reconstruction work, super-resolution and light-sheet microscopy, patch-clamp
-and multi-electrode array electrophysiology, microfluidics, biosensors and lab-on-chip.
-`Bioengineering` in particular reads more like an EE/mechatronics section than a biology
-one. If you build imaging or sensing hardware, these are the two feeds to subscribe to.
-
-**Named examples, every one verified against the bioRxiv API** (server, first-version
-posting date, category, linked publication) — all of these are **preprint-first**, i.e.
-the bioRxiv version predates the journal article (S16):
-
-| Tool / paper | bioRxiv DOI | Posted | Category | Journal version |
-|---|---|---|---|---|
-| **Salmon** (transcript quantification) | `10.1101/021592` | 2015-06-27 | Bioinformatics | *Nat Methods* `10.1038/nmeth.4197` |
-| **DeepVariant** (deep-learning variant caller) | `10.1101/092890` | 2016-12-14 | Genomics | *Nat Biotechnol* `10.1038/nbt.4235` |
-| **Scanpy** (single-cell analysis) | `10.1101/174029` | 2017-08-09 | Bioinformatics | *Genome Biol* `10.1186/s13059-017-1382-0` |
-| **Bioconda** (package distribution) | `10.1101/207092` | 2017-10-21 | Bioinformatics | *Nat Methods* `10.1038/s41592-018-0046-7` |
-| **Nextstrain** (real-time pathogen phylogenetics) | `10.1101/224048` | 2017-11-22 | Evolutionary Biology | *Bioinformatics* `10.1093/bioinformatics/bty407` |
-| **DeepLabCut 3D** (markerless pose tracking) | `10.1101/476531` | 2018-11-24 | Neuroscience | *Nat Protoc* `10.1038/s41596-019-0176-0` |
-| **Kraken 2** (metagenomic classification) | `10.1101/762302` | 2019-09-07 | Bioinformatics | *Genome Biol* `10.1186/s13059-019-1891-0` |
-| **ColabFold** (accessible protein folding) | `10.1101/2021.08.15.456425` | 2021-08-15 | Bioinformatics | *Nat Methods* `10.1038/s41592-022-01488-1` |
-| **ESM-2 / ESMFold** (protein language model) | `10.1101/2022.07.20.500902` | 2022-07-21 | Synthetic Biology | *Science* `10.1126/science.ade2574` |
-| **RFdiffusion** (generative protein design) | `10.1101/2022.12.09.519842` | 2022-12-10 | Biochemistry | *Nature* `10.1038/s41586-023-06415-8` |
-
-Bioconda, Nextstrain, ColabFold and DeepLabCut are ordinary open-source projects whose
-canonical citation is a bioRxiv-first paper. If you consume any of that stack, you are
-already downstream of this server.
-
-## 7. Screening and moderation — what gets in
-
-Neither server peer-reviews. Both run a **real, staffed, multi-step screen**, and it is
-stricter than most preprint servers in this collection.
-
-**Shared process** (S9, S6, S7): "All submissions are screened by the in-house Content
-Team. **Affiliate scientists**, who are listed on each server site, must approve each
-manuscript before it goes live. For articles in challenging areas, e.g. dual use research
-of concern, advice is solicited from subject matter experts. Only a small minority of
-submissions are declined. The authors are told why and appeals are always considered."
-(S9) [DOC]. So there are two gates: paid staff, then a volunteer domain scientist.
-
-**bioRxiv screens for** (S6): plagiarism; non-scientific content; inappropriate article
-types (§3); "material that could potentially endanger the health of individual patients or
-the public … including … **dual-use research of concern** and works that challenge or
-could compromise accepted public health measures and advice regarding infectious disease
-transmission, immunization, and therapy"; and any image or information that could identify
-an individual (blurring or pixelation is explicitly **not** accepted). English only,
-because "we are only able to screen for inappropriate or dangerous content in English".
-Typical turnaround **~72 hours**.
-
-**medRxiv is materially stricter**, and the reason is clinical harm — a wrong dose or a
-bogus efficacy claim can kill someone before review would have caught it. On top of
-everything bioRxiv checks, medRxiv requires (S7) [DOC]:
-
-- **Ethical oversight statement** from a named IRB / Ethics Committee "for all cases in
-  which human subjects, samples or data were used". The FAQ explicitly *rejects* decisions
-  from online tools, audit bodies, Caldicott Guardians, biosafety or data-protection
-  committees, HR, or R&D departments. Oversight must cover the whole study.
-- **Clinical trial registration** — a trial ID from an ICMJE-recognised registry for any
-  prospective interventional study "regardless of the cohort size"; unregistered studies
-  are sent back to register retrospectively.
-- **A hard identifiability rule** with an enumerated list: direct identifiers (names,
-  document numbers, patient/sample IDs, photographs, biometrics, precise ages, exact
-  dates/locations) are banned outright, and there must be **fewer than three indirect
-  identifiers** (age range, ethnicity, religion, occupation, family details, medical
-  history). If the data cannot be de-identified, medRxiv tells the authors to go to a
-  journal instead.
-- **A causal-language rule**: "We strongly recommend that authors avoid using causal
-  language, unless justified by a robust causal inference framework. Papers with
-  inappropriate causal language may be declined."
-- Screening takes **2–4 days**, versus ~72 h on bioRxiv.
-- Every medRxiv posting carries a stamp that it "**should not be used to directly inform
-  clinical decision-making**" (S7) — bioRxiv's stamp has no such clause.
-
-Manuscripts submitted to the wrong server are *not* forwarded automatically: the
-submission is closed and the author must resubmit, "to ensure that manuscripts are
-screened by the appropriate screening team" (S6, S7).
-
-Also worth knowing: **commercial submissions are accepted** but must be research, not
-product description; author affiliations are mandatory so company authorship is visible;
-on medRxiv, company associations must be disclosed as conflicts (S9).
-
-## 8. Reliability — what you can and cannot trust
-
-**What a deposit here guarantees:** a Crossref DOI under `10.1101/`; a timestamp; a
-plagiarism scan; a staff + affiliate-scientist eligibility screen; a Portico archival
-copy; full-text XML; permanence (posted preprints are *never* removed — only withdrawn,
-with a watermark and a public reason, the original still reachable via Info/History)
-(S6, S7). That is a stronger floor than most servers in this collection.
-
-**What it does not guarantee:** correctness, reproducibility, statistical competence, or
-that anyone qualified read the results section. The servers say so themselves, in the
-banner on every page: articles "might contain errors and report information that has not
-yet been accepted or endorsed in any way by the scientific or medical community" (S6).
-
-**How to sanity-check an individual preprint — the API method.** For any `10.1101/` DOI:
-
-```bash
-curl -s https://api.biorxiv.org/details/biorxiv/10.1101/207092/na/json
-```
-
-Read three fields on the **last** element of `collection`:
-
-- `published` — a journal DOI, or `NA`. Not `NA` means it survived peer review somewhere.
-  Then check *where*: resolve the DOI and look at the venue.
-- `version` — how many revisions. A v1 from 2019 that was never revised and has
-  `published: NA` is a dead preprint; weight accordingly.
-- `type` — one of `new results`, `confirmatory results`, `contradictory results`, or
-  **`withdrawn`**. A withdrawn preprint is still served by the API and still resolves;
-  the flag is the only signal.
-
-`type: withdrawn` is rare. In a 2026-06-01…06-14 census [API]: 2 withdrawn out of 2,843
-bioRxiv preprints (0.07 %), 1 of 777 on medRxiv (S17). **Do not treat 0.07 % as a
-correctness rate** — it is a self-reporting rate, and it is the floor of the error rate,
-not an estimate of it.
-
-**Known failure modes.** (a) Preprints that are wrong and travel anyway — see §9.
-(b) The screen is for *danger and eligibility*, not quality: methodologically weak work
-posts routinely and the servers do not claim otherwise. (c) Category assignment is
-author-chosen, single-valued, and openRxiv calls it "not a formal ontology" (S6) — do not
-use it as a taxonomy. (d) The published-link matcher occasionally misses (S6), so `NA` is
-weak evidence of non-publication for very recent journal articles. (e) Cross-posting to
-another server is forbidden and results in withdrawal (S6) — so unlike arXiv/HAL you will
-not find bioRxiv content mirrored elsewhere, which is a single-point-of-failure argument
-that Portico only partly answers.
-
-## 9. COVID-19: the stress test
-
-The pandemic is the reason most people outside biology have heard of medRxiv, and it cuts
-both ways.
-
-**The surge is measurable** [API, §4]: medRxiv went from **913** preprints in its
-half-year of 2019 to **14,070** in 2020 — a 15× jump in a server barely six months old.
-bioRxiv rose from 29,179 to 38,717 over the same period.
-
-**The good case.** The first SARS-CoV-2 genome papers went up here days after sequencing.
-Wu et al., *"Discovery of a novel coronavirus associated with the recent pneumonia
-outbreak in humans and its potential bat origin"*, bioRxiv `10.1101/2020.01.22.914952`,
-**posted 2020-01-23**, published in *Nature* `10.1038/s41586-020-2012-7` (S16) [API].
-Hoffmann et al. on ACE2/TMPRSS2 entry — the paper that pointed the whole field at
-TMPRSS2 inhibitors — bioRxiv `10.1101/2020.01.31.929042`, **posted 2020-01-31**, *Cell*
-`10.1016/j.cell.2020.02.052` (S16) [API]. Both are preprint-first by weeks, in a period
-when weeks mattered.
-
-**The bad case.** Pradhan et al., *"Uncanny similarity of unique inserts in the 2019-nCoV
-spike protein to HIV-1 gp120 and Gag"*, bioRxiv `10.1101/2020.01.30.927871`, posted
-2020-01-31, `published: NA` (S16) [API]. It claimed engineered HIV inserts in the
-SARS-CoV-2 spike, was demolished in the comments within about 48 hours, and was withdrawn
-by the authors — but not before it became foundational material for lab-leak and bioweapon
-narratives that outlived the withdrawal by years. This is the canonical demonstration that
-**withdrawal does not recall a preprint**; the DOI still resolves, and it should, but the
-claim is loose.
-
-The other well-documented policy case is Bendavid et al., *"COVID-19 Antibody
-Seroprevalence in Santa Clara County, California"*, medRxiv
-`10.1101/2020.04.14.20062463`, posted 2020-04-17 (S16) [API]. It was covered worldwide
-within 24 hours and used to argue that infection fatality rates — and therefore the case
-for lockdowns — had been overstated; its assay-specificity and weighting assumptions were
-contested immediately and publicly. It *was* eventually published (*Int J Epidemiol*
-`10.1093/ije/dyab010`, 2021), a year after the policy argument had moved on. The lesson is
-not that the preprint was worthless; it is that **the press and policy cycle is faster
-than the correction cycle**, and preprint servers widen that gap.
-
-For the scholarly account, see Fraser et al., *"The evolving role of preprints in the
-dissemination of COVID-19 research and their impact on the science communication
-landscape"*, *PLOS Biology* 2021, `10.1371/journal.pbio.3000959` — itself preprint-first
-as bioRxiv `10.1101/2020.05.22.111294`, posted 2020-05-23 (S18) [API/LIT].
-
-openRxiv's own position on all of this is unusually candid and worth quoting: the public
-"should regard preprints as conversations among scientists"; science is "less the parade
-of decisive blockbuster discoveries that the press often portrays, and more a slow,
-erratic stumble toward ever less uncertainty"; "but as we keep saying, preprints should be
-treated with caution" (S9) [DOC].
-
-## 10. Access, APIs and bulk retrieval
-
-**The API is one of the best in this collection.** `https://api.biorxiv.org/`, no key, no
-registration, JSON/XML/CSV, documented on one page (S19).
-
-| Endpoint | What it gives | Page size |
-|---|---|---|
-| `/details/{server}/{from}/{to}/{cursor}` | Full metadata per version; `?category=` filter | 30 |
-| `/details/{server}/{doi}/na/json` | Single manuscript, all versions | — |
-| `/pubs/{server}/{from}/{to}/{cursor}` | **preprint → journal publication links** | 100 |
-| `/pub/{from}/{to}/{cursor}` | published-article view, bioRxiv only | 100 |
-| `/publisher/{prefix}/{from}/{to}/{cursor}` | preprints published by a given DOI prefix | 100 |
-| `/funder/{server}/{from}/{to}/{ror}/{cursor}` | funder-filtered; **data only from 2025-04-10** | 100 |
-| `/sum/{m\|y}` | new + revised counts, interval and cumulative | — |
-| `/usage/{m\|y}/{server}` | abstract views, full-text views, PDF downloads | — |
-
-`messages[0]` carries `count_new_papers` (distinct preprints) *and* `total` (rows,
-i.e. **versions**). Use `count_new_papers` for sizes; `total` will overcount by ~40 %.
-
-**Probe results, all 2026-09-01:**
-
-| Probe | Result |
-|---|---|
-| `GET /pubs/biorxiv/2013-01-01/2026-09-01/0` | 200, 207,412 B, `total: 177932` ✅ |
-| `GET /pubs/medrxiv/2019-01-01/2026-09-01/0` | 200, 257,683 B, `total: 39885` ✅ |
-| `GET /sum/y` | 200, 1,759 B, full yearly series ✅ |
-| `GET /details/biorxiv/2013-01-01/2026-09-01/0` | 200 but **0 bytes** — full-range `details` queries never complete. Chunk by year. |
-| **Negative control** — `/details/notaserver/2025-06-01/2025-06-30/0` | 200, 74 B, `{"status":"Server not recognized"}`, empty collection ✅ correct rejection |
-| **Negative control** — `/details/biorxiv/10.1101/999999.999999/na/json` | 200, 67 B, `{"status":"no posts found"}` ✅ correct rejection |
-| **Negative control** — `/details/biorxiv/2025-06-01/2025-06-30?category=quantum_gravity` | 200, **82,363 B**, `"category":"all"`, 3,948 papers ❌ **silently falls back to all categories** |
-
-**That last one is a trap.** A misspelled or retired category (e.g. `epidemiology`,
-`clinical_trials` on bioRxiv) returns the *entire server* rather than an error — I hit it
-first with `epidemiology` and `clinical trials`, both of which returned exactly 49,318,
-the 2025 server-wide total. **Always assert `messages[0].category` equals what you asked
-for.** My 2025 table (§6) is validated by the sum-to-total check for exactly this reason.
-
-**Bulk full text — the AWS S3 requester-pays buckets. Verified** from both operators'
-own TDM pages (S20, S21) [DOC]:
-
-- `s3://biorxiv-src-monthly` — us-east-1
-- `s3://medrxiv-src-monthly` — us-east-1
-
-Both are **requester-pays**: `s3cmd ls s3://biorxiv-src-monthly --requester-pays`. An AWS
-account is required. The operators are explicit that the charges "are not a source of
-revenue" but exist so the servers "cannot incur unpredictable expense as a consequence of
-errant or abusive access". Layout: `Back_Content/Batch_[nn]/` (historical, loaded late
-2020) and `Current Content/<Month>_<Year>/`. Files are named `.meca` but are **zip
-archives** containing `manifest.xml` plus a `content/` folder with PDF, full-text XML,
-figures and supplementary files. Monthly deposit, completing a few days into each month.
-
-**Rate limiting / blocking.** `api.biorxiv.org` is open and did not rate-limit across
-several hundred requests on 2026-09-01. The **web** front ends do: `www.biorxiv.org/tdm`
-returned **HTTP 429 (17 bytes)** to a Chrome UA, to `curl/8.5.0` and to a ClaudeBot UA,
-and **200 (28,613 bytes)** to `WhatsApp/2.23.20.0`. `www.medrxiv.org` served the same page
-type fine to Chrome. Per the house rule this is noted only as a retrieval observation and
-not as evidence that the page works normally for ordinary clients (S20).
-
-Also available: per-subject RSS/Atom feeds, and `https://connect.biorxiv.org/biorxiv_xml.php?subject=all`
-(200, 76,570 B, `application/xml`, 2026-09-01).
-
-## 11. Licensing and reuse
-
-**Authors retain copyright** and pick from six options at submission (S6, S7) [DOC]:
-all-rights-reserved ("no reuse/adaptation without permission"), CC-BY-NC-ND, CC-BY-ND,
-CC-BY-NC, CC-BY, or CC0.
-
-There is **no default open licence**, and the actual mix matters. Census of every preprint
-posted 2026-06-01…06-14 [API] (S17):
-
-| Licence | bioRxiv (n=2,843) | medRxiv (n=777) |
-|---|---|---|
-| CC-BY | 996 (35.0 %) | 228 (29.3 %) |
-| CC-BY-NC-ND | 804 (28.3 %) | 181 (23.3 %) |
-| **all rights reserved** (`cc_no`) | **553 (19.5 %)** | **115 (14.8 %)** |
-| CC-BY-NC | 350 (12.3 %) | 58 (7.5 %) |
-| CC-BY-ND | 100 (3.5 %) | 24 (3.1 %) |
-| CC0 (incl. `cc0_ng`) | 40 (1.4 %) | 20 (2.6 %) |
-| *(blank / unrecorded)* | 0 | 151 (19.4 %) |
-
-**Roughly one preprint in five on bioRxiv is all-rights-reserved, and only ~36 % carry a
-fully open CC-BY/CC0 licence.** If you are building a corpus, you must read the
-per-record `license` field — there is no blanket permission. The TDM buckets do not change
-this: both TDM pages state the bucket "is *not* intended as a source for further
-redistribution … nor does it grant others permission to re-host content", that indexing
-services "must link back to the text hosted at bioRxiv rather than re-host content", and
-that reuse of individual articles is governed by the author's chosen licence — "in most
-cases, this will require you to contact the copyright holder in advance" (S20, S21).
-
-Bulk TDM itself is permitted: authors "explicitly consent to [it] during submission" and
-the operators consider it "consistent with fair use doctrine applied to US copyright law"
-(S20, S21). Note that is a **US fair-use** argument, not a licence grant.
-
-openRxiv posted "Preprint licensing updates" on **2026-05-20** (S11); I did not retrieve
-the post body, so **what changed in that update is [NOT-VERIFIED]** — the six options
-above are what the two FAQs listed on 2026-09-01.
-
-## 12. Caveats
-
-1. **The openRxiv homepage article counters are stale by roughly 18 months** (§4). Use
-   the API for any size claim.
-2. **A bad `category` parameter returns the whole server, not an error** (§10). Every
-   category-conditioned number anyone quotes from this API should be checked.
-3. **`total` in the `details` response counts versions, not papers.** ~40 % inflation.
-4. **medRxiv's `type` field is not comparable to bioRxiv's.** bioRxiv returns
-   `new results` / `confirmatory results` / `contradictory results` / `withdrawn`;
-   medRxiv returned `PUBLISHAHEADOFPRINT` for 776 of 777 records in the June-2026 census
-   (S17) — an artefact, not a content type. Only `WITHDRAWN` is informative there.
-5. **19 % of medRxiv records in that census had an empty `license` field.** Absent ≠ open.
-6. **`published: NA` is not proof of non-publication** (matcher misses, S6).
-7. **Withdrawal is not retraction and not removal.** The DOI still resolves, and the
-   original PDF is still reachable under Info/History (S6, S7).
-8. **No cross-posting**, so no independent mirror. Portico is the only preservation
-   backstop named by the operators (S6, S7).
-9. **English only**, by explicit policy, because screening capacity is English-only (S6).
-10. **Funding concentration.** CZI is the dominant funder and holds one of six board seats;
-    the seed grant to openRxiv is three years (S9). [INF] The governance risk is lower
-    than it was in 2024, but it is not gone.
-
-## 13. Sources
-
-- **S1** https://openrxiv.org/introducing-openrxiv/ · retrieved 2026-09-01 · openRxiv
-  launch announcement, dated **March 11, 2025**; CZI as "major early funding"; independent
-  non-profit framing. [DOC]
-- **S2** https://openrxiv.org/about/ · retrieved 2026-09-01 · founding history (bioRxiv
-  2013 CSHL / Inglis & Sever; medRxiv 2019 CSHL + Yale + BMJ; named founders), "over
-  430,000 preprints", "5,000 new research articles … each month", funder list, board and
-  SMAB rosters, embedded FAQ ("openRxiv is not a preprint server", "policies are not
-  changing"). [DOC]
-- **S3** https://openrxiv.org/ · retrieved 2026-09-01 · homepage counters "273,956
-  articles" (bioRxiv) and "65,414 articles" (medRxiv) — the stale figures in §4. [WEB]
-- **S4** https://api.biorxiv.org/sum/y · retrieved 2026-09-01 · bioRxiv yearly new and
-  revised counts, cumulative to 347,954. [API]
-- **S5** `https://api.biorxiv.org/details/medrxiv/<year>-01-01/<year>-12-31/0`, 2019–2026 ·
-  retrieved 2026-09-01 · `count_new_papers` per year; total 88,194. Local log:
-  `scratch/preprint-repositories/lifesci/medrxiv-by-year.txt`. [API]
-- **S6** https://www.biorxiv.org/about/FAQ · retrieved 2026-09-01 · bioRxiv screening
-  criteria, out-of-scope list, ~25 categories, closed Clinical Trials/Epidemiology,
-  licence options, withdrawal policy, Portico, indexing, DMCA agent (OPENRXIV CORP,
-  Davis CA), 249 integrated journals, bioinformatics/computational-paper policy. [DOC]
-- **S7** https://www.medrxiv.org/about/FAQ · retrieved 2026-09-01 · medRxiv screening,
-  ethical-oversight requirement, trial-registration requirement, direct/indirect
-  identifier rules, causal-language rule, 2–4 day screening, ~50 categories, "should not
-  be used to directly inform clinical decision-making". [DOC]
-- **S8** https://openrxiv.org/seeking-inaugural-ceo/ (listed on
-  https://openrxiv.org/news/page/2/) · retrieved 2026-09-01 · dated March 11, 2025. [DOC]
-- **S9** https://openrxiv.org/qa-governance-funding-future/ · retrieved 2026-09-01 ·
-  dated May 21, 2025 · named six-member board; "CZI provided three years of seed funding";
-  "One person on the six-member board has a CZI affiliation"; screening description
-  (in-house Content Team + affiliate scientists + subject-matter experts); **"75% of
-  bioRxiv and medRxiv preprints go on to be published in peer-reviewed journals"**;
-  commercial-submission policy; the "conversations among scientists" quote. [DOC]
-- **S10** https://openrxiv.org/news/page/2/ · retrieved 2026-09-01 · dated index: CEO
-  appointment 2025-08-18, Royal Society award 2025-08-28, Dryad partnership 2025-09-18,
-  DOI policy post 2025-11-18. [DOC]
-- **S11** https://openrxiv.org/news/ · retrieved 2026-09-01 · dated index: "Preprint
-  licensing updates" 2026-05-20, "Launching openRxiv Labs" 2026-06-01, Hypothesis
-  commenting 2026-04-07, SMAB inaugural meeting 2026-07-22, Head of Product 2026-06-30,
-  "openRxiv 2025 year in review" 2025-12-31 ("In March we launched openRxiv"). [DOC]
-- **S12** https://api.biorxiv.org/usage/y/biorxiv and `/usage/y/medrxiv` · retrieved
-  2026-09-01 · view and download series. [API]
-- **S13** `https://api.biorxiv.org/pubs/biorxiv/2013-01-01/2026-09-01/0` and
-  `.../medrxiv/2019-01-01/2026-09-01/0` · retrieved 2026-09-01 · `total` = 177932 and
-  39885 preprint→publication links. [API]
-- **S14** Abdill RJ, Blekhman R. "Tracking the popularity and outcomes of all bioRxiv
-  preprints." *eLife* 8:e45133 (2019-04-24), `10.7554/eLife.45133`; preprint bioRxiv
-  `10.1101/515643`, posted 2019-01-13. Both verified 2026-09-01 (Crossref + bioRxiv API).
-  [LIT]
-- **S15** `https://api.biorxiv.org/details/biorxiv/<year>?category=bioinformatics` and the
-  27-category 2025 sweep · retrieved 2026-09-01 · local logs
-  `scratch/preprint-repositories/lifesci/bioinformatics-by-year.txt`, `cats-2025.txt`,
-  `cats-2025b.txt`. Category counts sum exactly to 49,318. [API]
-- **S16** `https://api.biorxiv.org/details/{server}/{doi}/na/json` for each DOI in §6 and
-  §9 · retrieved 2026-09-01 · confirms server, first-version date, category and linked
-  publication DOI. Local logs `landmarks1.txt`, `landmarks2.txt`. [API]
-- **S17** Census of `details/{server}/2026-06-01/2026-06-14` (all pages, deduped by DOI) ·
-  retrieved 2026-09-01 · licence and `type` distributions; 2 withdrawn / 2,843 on bioRxiv,
-  1 / 777 on medRxiv. Local log `licence-dist.txt`. [API]
-- **S18** Fraser N, et al. "The evolving role of preprints in the dissemination of COVID-19
-  research and their impact on the science communication landscape." *PLOS Biology* 19(4):
-  e3000959 (2021-04-02), `10.1371/journal.pbio.3000959`; preprint bioRxiv
-  `10.1101/2020.05.22.111294`, posted 2020-05-23 as "Preprinting a pandemic". Both verified
-  2026-09-01. [LIT]
-- **S19** https://api.biorxiv.org/ · retrieved 2026-09-01 · full endpoint documentation,
-  page sizes, `count_new_papers` vs `total` semantics, funder-metadata inception date
-  2025-04-10. [DOC]
-- **S20** https://www.biorxiv.org/tdm · retrieved 2026-09-01 (HTTP 429 to a Chrome UA and
-  to `curl/8.5.0`; HTTP 200, 28,613 B with `WhatsApp/2.23.20.0`) · `s3://biorxiv-src-monthly`,
-  us-east-1, requester-pays, `.meca` = zip, Back_Content/Current Content layout, no
-  re-hosting permission. [DOC]
-- **S21** https://www.medrxiv.org/tdm · retrieved 2026-09-01 (HTTP 200, 28,748 B, default
-  Chrome UA) · `s3://medrxiv-src-monthly`, identical terms. [DOC]
-
-### Not verified
-
-- The exact **calendar date medRxiv opened for submissions in 2019** — openRxiv says only
-  "2019" (S2) and bioRxiv's FAQ says the clinical pilot completed "In June 2019" (S6).
-  Recorded as **2019** only.
-- The **content of the 2026-05-20 "Preprint licensing updates" post** (§11).
-- **`api.biorxiv.org/covid19/{cursor}`** is documented but returned 200 / 0 bytes on
-  2026-09-01. Non-functional at time of retrieval.
-- Any **claim about acceptance/decline rates**: openRxiv says only "a small minority of
-  submissions are declined" (S9). No numeric decline rate is published.
diff --git a/research/preprint-repositories/bulk-libraries-and-shadow-archives.md b/research/preprint-repositories/bulk-libraries-and-shadow-archives.md
deleted file mode 100644
index 755830c..0000000
--- a/research/preprint-repositories/bulk-libraries-and-shadow-archives.md
+++ /dev/null
@@ -1,602 +0,0 @@
-# Bulk libraries and shadow archives — what they are, and why this repository does not cite them
-
-- **Compiled:** 2026-09-02. Every figure carries a source and a date.
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-- **Method statement, up front and non-negotiable:** **no shadow-library service was accessed in
-  producing this record.** Everything in §§3–6 comes from Wikipedia's referenced articles,
-  Crossref-verified scholarly literature, court reporting, and the operators' own statements as
-  relayed by third parties. Operator figures are labelled as *claims*, never as measurements. Raw
-  probe log:
-  [`../../scratch/preprint-repositories/bulk-archives/probe-log-2026-09-02.txt`](../../scratch/preprint-repositories/bulk-archives/probe-log-2026-09-02.txt).
-- **This record contains no mirror domains, no proxy hosts, no onion addresses and no instructions
-  for reaching a blocked service.** Those rotate too fast to capture, are the operational-
-  circumvention part, and would make this document wrong within a month. Services are named and
-  historicised only. That is a deliberate editorial decision, stated so nobody reads it as an
-  oversight.
-
----
-
-## 1. Read this first: the lawful copy almost certainly exists
-
-**For the overwhelming majority of the technical literature this knowledge base cares about there is
-a free, lawful, publisher- or funder-sanctioned copy, and the ladder in
-[`open-access-full-text-sources.md`](open-access-full-text-sources.md) finds it.** That is not a
-platitude — it is a property of this specific field, which is unusually well served by open access:
-
-| Body of work | Where the lawful free copy is | Record |
-|---|---|---|
-| Operating systems, storage, networking, systems security | **USENIX** — OSDI, NSDI, ATC, FAST, USENIX Security. *All of it, all years, free by policy*, including full-proceedings PDFs | [`open-access-full-text-sources.md` §3.1](open-access-full-text-sources.md) |
-| Cryptography, side-channel and embedded security | **IACR Cryptology ePrint** (27,552 reports) and TCHES — diamond OA | [`cryptology-eprint-archive.md`](cryptology-eprint-archive.md) |
-| Almost anything in CS or EE with an arXiv ID | **arXiv** — 3,152,666 submissions, `cs` alone 931,100 | [`arxiv.md`](arxiv.md) |
-| Computational linguistics / NLP | **ACL Anthology** — the entire proceedings corpus, free | [`open-access-full-text-sources.md`](open-access-full-text-sources.md) |
-| IEEE-published work | The author's copy on **TechRxiv**, found via Crossref's `is-preprint-of` relation | [`techrxiv.md`](techrxiv.md) |
-| Aerospace, energy, national-lab engineering | **NTRS**, **OSTI**, agency technical-report servers | [`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md) |
-| Protocol specifications | **RFC Editor** — entirely free, always has been | [`open-access-full-text-sources.md` §5](open-access-full-text-sources.md) |
-| Life-science and bioinformatics software papers | **PMC / Europe PMC** | [`open-access-full-text-sources.md` §3.5](open-access-full-text-sources.md) |
-| Historical vendor manuals, data books, corporate tech reports | **bitsavers**, **archive.org**, **Arquivo.pt**, the Wayback Machine | [`recovering-dead-technical-sites.md`](recovering-dead-technical-sites.md) |
-
-The companion record's own summary is that **rungs 1–3 of its ladder (Unpaywall → Semantic Scholar
-`externalIds.ArXiv` → OpenAlex `locations[]`) resolve the large majority of computing and
-electronics citations**, and rung 4 — "is it a USENIX paper?" — resolves much of the remainder.
-Rung 9, *email the author*, is slow, legitimate, and works. **Shadow libraries are a last resort,
-not a first one, and this file is not a shortcut around the ladder.** They are documented here
-because they are the largest bodies of technical text in existence and therefore constantly
-discussed, because they sit at the centre of current AI-training litigation, and because an engineer
-handed a PDF of unknown provenance needs a way to judge it (§7).
-
----
-
-## 2. Definitions, and the distinction that runs through this whole file
-
-**"Shadow library"** — also *pirate library*, also *black open access* — is the term used in the
-scholarly literature for an online repository of works that are normally paywalled or otherwise
-access-controlled [COM] (S2). The category is old; what changed in the 2010s was scale. The single
-most useful distinction, and one that maps closely onto the legal line:
-
-| | Indexing **metadata** | Redistributing **full text** |
-|---|---|---|
-| What it is | Titles, authors, DOIs, ISBNs, checksums — "this work exists, and a file of it is N bytes" | The bytes of the copyrighted work |
-| Legal status | **Generally lawful.** Facts are not copyrightable in most jurisdictions, and bibliographic databases are routinely published openly | **The contested part.** This is what the injunctions and judgments are about |
-| Examples | Crossref public data file, OpenAlex snapshot, dblp, Open Library dumps, `awesome-*` link lists, arXiv OAI-PMH | Sci-Hub, LibGen, Z-Library file corpora |
-| Useful to this repository? | **Yes, heavily** — see §8 | Only as an object of study |
-
-Keep that line in view: several things below sit on the lawful side of it and are used in mainstream
-research, several do not — and §5.4 shows the line is not absolute, because *how* metadata was
-acquired can itself be unlawful.
-
----
-
-## 3. Sci-Hub
-
-### 3.1 What it is, and the one fact that matters most
-
-Founded in **Kazakhstan by Alexandra Elbakyan in 2011** in response to paywall pricing. Unlike
-Library Genesis it deals in **papers, not books**. It worked by using institutional credentials to
-fetch articles on demand and caching what it fetched; until the end of 2014 it used LibGen as its
-storage back end [COM] (S1).
-
-**The operationally decisive fact: Sci-Hub has been effectively frozen since December 2020.**
-
-Verbatim from the retrieved extract [COM] (S1): *"On 15 July 2022, Sci-Hub reported that its
-collection comprised 88,343,822 files. In December 2020, the site paused uploads due to legal
-troubles. Since then, the site has archived a much lower fraction of new articles."* The mechanism
-was the **Delhi High Court** case (§3.3) — the court restricted uploading until 6 January 2021, and
-Elbakyan *"complied with a preliminary injunction issued by an Indian court, and suspended in 2021
-upload of new publications, except for some batch releases of content"*. One such batch was the
-tenth-anniversary release of **over 2.3 million articles in a single day in September 2021**.
-
-So the verified position is a **two-step freeze**: uploads paused **December 2020**; new-publication
-uploads formally **suspended during 2021** under the Indian injunction, with occasional batches
-since. The 88,343,822-file figure is an **operator self-report dated 2022-07-15**, not a measurement.
-
-**Consequence for technical literature work in 2026: Sci-Hub does not have the last five years.** It
-is functionally a 2011–2020 snapshot with sporadic additions, so anything published since roughly
-2021 has to come from the lawful ladder regardless.
-
-### 3.2 The coverage literature — legitimate, citable, and worth reading
-
-Studies *about* Sci-Hub are ordinary peer-reviewed scholarship and are cited here as such. **Every
-DOI below was fetched from `api.crossref.org` and its title machine-checked against the response on
-2026-09-02** [API] (S7):
-| Study | Identifier | What it found |
-|---|---|---|
-| Himmelstein, Romero, Levernier, Munro, McLaughlin, Greshake Tzovaras & Greene, **"Sci-Hub provides access to nearly all scholarly literature"**, *eLife*, 2018 | [`10.7554/eLife.32822`](https://doi.org/10.7554/eLife.32822) | The canonical coverage study. Establishes scale empirically rather than from operator claims |
-| Bohannon, **"Who's downloading pirated papers? Everyone"**, *Science*, 2016 | [`10.1126/science.352.6285.508`](https://doi.org/10.1126/science.352.6285.508) | The 28-million-request download-log analysis; showed heavy use from high-income countries too |
-| Greshake, **"Looking into Pandora's Box: The Content of Sci-Hub and its Usage"**, *F1000Research*, 2017 | [`10.12688/f1000research.11366.1`](https://doi.org/10.12688/f1000research.11366.1) | Content composition and usage patterns |
-| Correa, Laverde-Rojas, Tejada & Marmolejo-Ramos, **"The Sci-Hub effect on papers' citations"**, *Scientometrics*, 2021 | [`10.1007/s11192-020-03806-w`](https://doi.org/10.1007/s11192-020-03806-w) | Reports a citation differential; **contested** — see below |
-| Maddi & Sapinho, **"On the culture of open access: the Sci-hub paradox"**, *Scientometrics*, 2023 | [`10.1007/s11192-023-04792-5`](https://doi.org/10.1007/s11192-023-04792-5) | Finds Sci-Hub use is not confined to, nor explained by, lack of legal access |
-| Walters, **"Comparing conventional and alternative mechanisms of discovering and accessing the scientific literature"**, *PNAS*, 2025 | [`10.1073/pnas.2503051122`](https://doi.org/10.1073/pnas.2503051122) | A recent mainstream-venue comparison of discovery and access routes |
-
-**Two caveats, stated rather than glossed.** The **citation-advantage** result (Correa et al.) is
-disputed — *"the study's methods and conclusions were disputed by Phil Davis in a Scholarly Kitchen
-article"* [COM] (S1); report it as contested, not established. And the often-quoted coverage
-percentages (85% of paywalled-journal articles as of March 2017; ~96% of requests successful) come
-from that 2017–2018 window [COM] (S1) — **given the freeze they are historical figures and must never
-be presented as current coverage.**
-
-**A discipline note.** Four plausible-looking DOIs guessed while assembling this table resolved to
-entirely unrelated papers — `10.1007/s11192-021-04068-w` is about letters to the editor in
-exercise-science journals; `10.1002/leap.1205` is "ALPSP Awards 2018" [API] (S7). **A DOI that looks
-right is not a citation.** This is [README rule 5](README.md#evidence-and-method) in miniature.
-
-### 3.3 Legal status — stated without minimising
-
-Sci-Hub distributes copyrighted works without authorisation, and has been found unlawful repeatedly:
-
-| Case | Court | Outcome |
-|---|---|---|
-| **Elsevier et al. v. Sci-Hub et al.** (filed 2015; LibGen a co-defendant) | S.D.N.Y. | **June 2017: default judgment, US$15 million**, plus an injunction that cost the original `.org` domain [COM] |
-| **ACS v. Sci-Hub** (filed June 2017) | E.D. Va. | **6 November 2017: default judgment, US$4.8 million**, plus a permanent injunction binding *"any Internet search engines, web hosting and Internet service providers, domain name registrars, and domain name registries"*. Four domains went inactive and its Cloudflare account was terminated within weeks [COM] |
-| **Elsevier, Wiley & ACS v. Sci-Hub and LibGen** (filed December 2020) | **Delhi High Court** | Sought a *dynamic* injunction — future domains/IPs covered without returning to court. Uploads restricted from the outset; Elbakyan complied and froze new uploads (§3.1). Her defence rested on India's fair-dealing exception. **19 August 2025: the Delhi High Court banned Sci-Hub and Library Genesis** [COM] |
-
-Both US judgments were **defaults** — Sci-Hub did not appear — which is legally significant: they
-establish liability of record but were not adversarially tested on the merits. That nuance does not
-make the conduct lawful.
-
-Beyond the courts: in **February 2021** Elsevier and Springer Nature obtained a UK blocking
-injunction against an ISP, and in **March 2021 the City of London Police's Intellectual Property
-Crime Unit warned universities and students** that the site *"could steal credentials"* and that
-users could *"inadvertently download potentially dangerous content"* [COM] (S1). Institutions
-routinely block it, and **access may itself be unlawful where the reader is.** In 2025 Elbakyan
-launched **Sci-Net**, described as a social network for requesting and uploading papers [COM] (S1);
-its legal position is **[NOT-VERIFIED]** here.
-
----
-
-## 4. Library Genesis
-
-### 4.1 History, forks and splits
-
-LibGen's lineage is Russian: Soviet-era **samizdat** hand-copying culture, which moved onto RuNet in
-the 1990s as uncoordinated collections and was consolidated into a single system **around 2008**. It
-absorbed the contents of **library.nu** after that site was closed by legal action in 2012, and had
-**1.2 million records by 2014** [COM] (S3). It describes itself as a *"links aggregator"* of items
-*"collected from publicly available public Internet resources"* plus user uploads — a
-characterisation no court has accepted.
-
-In **2020 the project forked** over internal conflict, producing a separate domain whose database
-was maintained independently; *"as a consequence, the works available differed"* between the two
-[COM] (S3). That fork's domain had been seized by 2025. By **August 2024** the main project
-*"appeared to no longer be actively managed"* and its lead programmer was reported *"inactive"*
-[COM] (S3).
-
-**So "LibGen" is not one thing.** It is a family of divergent databases of uncertain currency, under
-uncertain maintenance, reachable through domains that change under legal pressure. A file "from
-LibGen" carries no information about which database, which fork, or which era produced it — which is
-the root of the reliability problem in §7.
-
-### 4.2 What the collections actually contain
-
-This is the part people get wrong. LibGen is **overwhelmingly a book library**, and the composition
-matters if you are hunting a technical paper. Self-reported as of **4 February 2024** [COM] (S3):
-
-| Category | Claimed count |
-|---|---|
-| Science journal articles | **80 million** |
-| Non-fiction books | 2.4 million |
-| Fiction books | 2.2 million |
-| **Comics files** | **2 million** |
-| Magazine issues | 0.4 million |
-
-Note what is *not* there: **standards**. IEEE, JEDEC, IEC and ISO documents are not a LibGen
-strength — and for standards the lawful picture is far better than most engineers assume. IETF,
-RISC-V International and USB-IF publish free; JEDEC is free behind registration; only IEEE SA is
-mostly paid ([`government-and-institutional-technical-reports.md` §5](government-and-institutional-technical-reports.md)).
-
-### 4.3 Legal status
-
-- **Elsevier v. LibGen** (S.D.N.Y., filed 3 June 2015): October 2015 shutdown order for the then-main
-  domain [COM].
-- **Pearson Education, McGraw Hill, Macmillan and Cengage v. LibGen** (S.D.N.Y., filed 14 September
-  2023): **26 September 2024, US$30 million judgment**; in December 2024 the publishers seized the
-  then-primary domain and took most others offline [COM] (S3).
-- **Germany, December 2024:** the **CUII** (*Clearingstelle Urheberrecht im Internet*, a
-  rightsholder/ISP body) instituted a **country-wide ISP block without court authorisation** — the
-  Federal Network Agency was consulted only on net-neutrality compliance [COM] (S3).
-- Blocked by ISPs in the UK, France, Germany, Greece, Italy, Belgium, the Netherlands and Russia;
-  registered in **both Russia and the Netherlands**, part of why jurisdiction has been so contested;
-  and **banned alongside Sci-Hub by the Delhi High Court on 19 August 2025** [COM] (S1, S3).
-
-### 4.4 AI-training litigation — why this is now front-page law
-
-LibGen is the corpus at the centre of the generative-AI copyright cases. **Anthropic:** court
-documents unsealed June 2025 indicated LibGen material was used in training, and in **September 2025
-Anthropic settled for US$1.5 billion** over knowingly using pirated sources, reportedly including
-**at least 5 million books** from LibGen (*Bartz, Graeber & Johnson v. Anthropic*) [COM] (S3).
-**Meta:** documents unsealed March 2025 in *Kadrey, Silverman & Golden v. Meta* indicated LibGen use,
-and separately that Meta downloaded **over 81 terabytes** through Anna's Archive torrents; in **June
-2025 the court partially ruled for Meta**, finding the training *"highly transformative"* and
-therefore fair use — while Judge Vince Chhabria expressly said the ruling *"did not mean that Meta's
-actions were in fact legitimate"* and identified **"market dilution"** as the strong argument the
-plaintiffs had failed to develop [COM] (S4).
-
-**Do not read the Meta ruling as a general licence.** One district judge, on one record, on
-arguments the plaintiffs conceded — decided the same year another AI company paid US$1.5 billion over
-the same corpus. This record draws **no legal conclusion** from the two beyond the obvious one: the
-law here is unsettled and moving.
-
----
-
-## 5. Anna's Archive
-
-### 5.1 What it is
-
-A **search and aggregation layer**, not primarily a host. Launched by a pseudonymous operator
-("Anna") days after the November 2022 Z-Library enforcement action, out of the **Pirate Library
-Mirror (PiLiMi)** project — which had completed a full copy of Z-Library in September 2022 and which
-openly stated it *"deliberately violated the copyright law in most countries"* [COM] (S4). Its source
-libraries are LibGen, Sci-Hub, Z-Library, the Internet Archive, DuXiu, MagzDB, Nexus/STC and
-HathiTrust; Open Library, WorldCat and Google Books are listed as **metadata-only** sources; its own
-source code is dedicated to the public domain under **CC0** [COM] (S4).
-
-**Self-reported scale as of 20 August 2026: 71,400,751 books and 157,010,964 papers, with a unified
-torrent list of roughly 1.1 petabytes** [COM] (S4). **These are the operator's claims, reported as
-claims.** No independent verification exists in this record, and by policy this pass did not attempt
-one.
-
-### 5.2 Its own framing, reported as framing
-
-The operator describes the project as **preservation**: the stated objectives are *"to catalog all
-the books in existence"* and *"track humanity's progress toward making all these books easily
-available in digital form"*, and it calls itself *"the largest truly open library in human history"*
-[COM] (S4). Anna has defended the position on ethical grounds — *"we believe that preserving and
-hosting these files is morally right"* — has argued that Western countries should create **legal
-carveouts for text and data mining** to stay competitive in AI, and cites Aaron Swartz as an
-influence [COM] (S4). Its legal-liability theory is that it hosts nothing and merely indexes
-metadata and links to third-party downloads. **That theory has not survived contact with any court
-that has examined it** — §5.3.
-
-A commercial dimension sits awkwardly beside the preservation framing, and both belong in the record:
-it **sells bulk SFTP access to LLM trainers** for money or data, and said it had provided such access
-to about **30 companies (primarily Chinese) as of January 2025**, including data brokers; DeepSeek's
-VL model was reported as partly trained on its ebook data [COM] (S4).
-
-### 5.3 Legal status
-
-| Action | Court / body | Outcome |
-|---|---|---|
-| **OCLC v. Anna's Archive** — over a scrape of **WorldCat**, the world's largest bibliographic database | S.D. Ohio (filed January 2024) | Damages demand dropped November 2025; **January 2026: default judgment (Judge Michael H. Watson)**, ordering deletion of the WorldCat data and barring further scraping or sharing [COM] |
-| **Spotify + Universal, Sony, Warner v. Anna's Archive** — after a reported ~300 TB Spotify scrape publishing 256 million metadata rows | S.D.N.Y. (filed December 2025, under seal) | TRO January 2026; **preliminary injunction 16 January 2026 (Judge Jed Rakoff)** reaching domain registries, hosts and Cloudflare, with several domains suspended; **default judgment 15 April 2026: US$322 million** plus a permanent injunction directed at service providers [COM] |
-| **13 publishers v. Anna's Archive** | S.D.N.Y. (filed March 2026) | **19 May 2026: default judgment, US$19.5 million**, plus an order for a **global domain takedown** [COM] |
-| ISP blocking | Rotterdam District Court, March 2024 (dynamic order, via BREIN); **UK High Court, December 2024** under s.97A CDPA; **Germany, October 2025** via CUII | The UK Publishers Association said it had identified **over one million records** of copyrighted books and journal articles on the site's domains [COM] |
-
-Note the pattern across §§3–6: these are almost all **default judgments**. The operators do not
-appear. Liability is established of record; the merits are largely untested.
-
-### 5.4 The genuinely useful part: the metadata releases — and their limit
-
-Anna's Archive publishes **openly downloadable metadata datasets and torrent lists**, standardised
-since August 2023 in a format it calls **AAC (Anna's Archive Containers)**: line-delimited JSON
-compressed with **Zstandard**, with optional binary payloads alongside, designed for incremental
-release over torrents and ingestion into a MariaDB/Elasticsearch/Python stack [COM] (S4).
-**Metadata about books — titles, authors, ISBNs, editions, file checksums — is not the copyrighted
-work**, and corpora of it are used in ordinary bibliometric and preservation research. Measured
-2026-09-02: **OpenAlex indexes 56 works matching `"Anna's Archive"`** [API] (S8), including Walters,
-*PNAS* 2025, [`10.1073/pnas.2503051122`](https://doi.org/10.1073/pnas.2503051122) — a comparison of
-conventional and alternative discovery/access mechanisms in a top-tier venue — and a 2026 figshare
-dataset, [`10.6084/m9.figshare.32454042`](https://doi.org/10.6084/m9.figshare.32454042), comparing a
-university library's course-textbook holdings against availability on the site: a
-*collection-development* study, exactly the kind of legitimate work metadata enables.
-
-**However**, and this is why the WorldCat judgment matters: some of those datasets were **obtained by
-scraping a third party's proprietary database**, and a US federal court has ordered them deleted
-(§5.3). *"It is only metadata"* is a sound general principle and a poor blanket defence — lawfulness
-turns on **how the metadata was acquired**, not only on what it contains. §8.1 lists metadata corpora
-whose provenance is not in question, and they are the ones to use.
-
----
-
-## 6. Z-Library
-
-Began life as a **mirror of Library Genesis** and grew far beyond it. Self-reported February 2023:
-**over 13.35 million books and over 84.8 million articles**, a database **over 220 TB** [COM] (S5).
-It never opened its full database publicly; the copy that circulates was taken by PiLiMi in 2022
-(§5.1).
-
-**The 2022 US enforcement action.** On **3 November 2022** the US Department of Justice and FBI
-seized **over 240 domain names** under court order, and two Russian nationals — **Anton Napolsky**
-and **Valeriia Ermakova** — were arrested in **Argentina**. The **E.D.N.Y. indictment was unsealed
-on 16 November 2022**, charging **criminal copyright infringement, wire fraud and money laundering**
-for conduct alleged between 2018 and 2022; the FBI identified the operators using search warrants
-served on Google and Amazon among others. **The pair escaped house arrest in July 2024**; an
-Interpol notice was issued and their whereabouts are unknown [COM] (S5). This is the point at which
-the category stops being a civil-litigation story: **criminal charges, not just damages awards.**
-
-Further seizure rounds followed in May 2023, November 2023 (US and Austria), January 2024 and May
-2024. France's *Tribunal Judiciaire de Paris* ordered ISP blocks against 209 domains in September
-2022 and 98 more in September 2024; India blocked it in August 2022 via the Tis Hazari district
-court [COM] (S5).
-
-**The malware and phishing risk is documented, not hypothetical.** From the retrieved article:
-*"Some phishing scams have attempted to impersonate Z-Library by using similar domain names and an
-identical visual design in order to extract login credentials and ask for donations. In June 2024,
-the news outlet Cybernews reported the discovery of a leaked database containing the personal data
-of nearly 10 million users, which had been collected by the scam clone site […]"* [COM] (S5) — the
-clone's domain is named in the source and is deliberately elided here, per the policy in the header.
-
-**That is the concrete reason this file lists no domains.** When a service is under a global
-domain-takedown order, *every* plausible-looking domain is a coin flip, and the documented downside
-is a credential-harvesting clone holding ten million user records. Combine that with the City of
-London Police's credential-theft warning about Sci-Hub (§3.3) and the pattern is consistent across
-the whole category: **the imitation sites are a bigger practical hazard to the reader than the
-originals ever were.**
-
----
-
-## 7. Reliability — the section that actually matters here
-
-Everything above is context. **This is the operative part**, and it applies to *any* unprovenanced
-bulk source, lawful or not.
-
-### 7.1 What a PDF from an unprovenanced bulk library does not tell you
-
-You have a file with a plausible title page. From the file alone you cannot establish:
-
-| You cannot verify | Why it bites |
-|---|---|
-| **That it is the version of record** | Preprint, accepted manuscript and published version differ. [`open-access-full-text-sources.md` §5](open-access-full-text-sources.md) makes the point precisely: an accepted manuscript is scientifically equivalent to the VoR but **its page and line numbers are not.** Quote a page number from the wrong version and the citation is wrong |
-| **Which edition or printing** | These collections hold multiple editions of the same textbook under the same title with no reliable edition field. For a standard, an errata-corrected reprint or a datasheet revision, this is the difference between a working design and a dead board |
-| **That the scan is complete** | Silently truncated scans, missing appendices and missing plate sections are a known failure mode of bulk-uploaded material. Nothing in the file announces the omission |
-| **That it is unaltered** | No checksum against a publisher master, no signature, no chain of custody |
-| **That the metadata is right** | Bulk collections inherit metadata from whatever scraped them. Not speculative: **archive.org's own catalogue** — a *lawful, curated* collection — lists a Tektronix oscilloscope manual as *"Tektronix Fish Finder 465 AND DM44 User Guide"* and a TAS455/465 as *"Tektronix Hunting Equipment"* [API], measured 2026-09-02. If a curated archive does that, an unprovenanced one does worse |
-| **That the OCR is usable** | Also measured: the OCR layer of that same real Tektronix manual degrades to `r'\|'“ , p ■ '"I E. : . J" 51` within a page. See [`recovering-dead-technical-sites.md` §3.3](recovering-dead-technical-sites.md) |
-
-Note that none of these failure modes is a *legal* objection. They apply just as much to a PDF found
-on a dead lab web page or in a forum attachment. **Provenance, not legality, is what makes a
-document citable.**
-
-### 7.2 The rule
-
-> **Never cite from an unprovenanced bulk library without resolving the DOI and confirming the
-> bibliographic record against Crossref, DataCite or dblp. For anything load-bearing — a design
-> decision, a specification, a number that goes into this repository — obtain the publisher or
-> repository copy.**
-
-This is not an extra hurdle invented for this file. It is
-[`README.md § Evidence and method`](README.md#evidence-and-method) applied to full text: rule 1
-(*an unsourced number is worse than no number*), rule 2 (*prefer machine-readable primary
-evidence*), and rule 5 (*landmark papers must resolve*) together mean a file with no resolvable
-identifier **cannot carry an evidence label at all** — the strongest thing you could honestly write
-next to it is **[NOT-VERIFIED]**.
-
-The check is three cheap API calls, all verified working on 2026-09-02 [API] (S7, S9):
-
-```bash
-# 1. Does the identifier exist, and is the title what you think it is? (DataCite for data/software)
-curl -s "https://api.crossref.org/works/<DOI>" | jq -r '.message.title[0], .message."container-title"[0]'
-# 2. Is there a lawful free copy?  -> open-access-full-text-sources.md rungs 1-3
-curl -s "https://api.unpaywall.org/v2/<DOI>?email=you@your.org" | jq '.best_oa_location.url_for_pdf'
-curl -s "https://api.semanticscholar.org/graph/v1/paper/DOI:<DOI>?fields=externalIds" | jq '.externalIds.ArXiv'
-# 3. For CS, dblp is the best title -> canonical-citation resolver there is. No key needed.
-curl -s "https://dblp.org/search/publ/api?q=<title>&format=json" | jq '.result.hits.hit[]?.info'
-```
-
-Worked example, 2026-09-02 [API] (S9): querying dblp for *"In Search of an Understandable Consensus
-Algorithm"* returns `@total: 1` — **USENIX ATC 2014**, with `ee` pointing at usenix.org. One call
-gives the canonical venue, the year, *and* the lawful full text. That is the whole argument for the
-ladder in one line. **If step 1 fails, you do not have a citation — you have a file.**
-
-### 7.3 Why this matters more for hardware than for most fields
-
-The rest of this directory is about papers, where being one version out is embarrassing. In hardware
-documentation it is expensive: **datasheet revisions change absolute maximum ratings** (the
-repository's crawler table already records Espressif *withdrawing* documents for EOL parts, and a
-distributor-adjacent site publishing AI-generated prose that **misstated an operating temperature by
-20 °C** against the manufacturer datasheet); **a single mis-OCR'd digit is invisible and
-catastrophic** — 3.3 V and 8.3 V differ by one glyph; and **bulk libraries do not carry the revision
-string in their metadata**, so you cannot tell what you have without opening the cover page, at which
-point you may as well have gone to the vendor or to bitsavers, where the directory path *is* the
-attribution.
-
-**Practical rule for this repository:** record the **byte size**, the **magic bytes**, the
-**revision string from the cover page**, and the **URL and retrieval date** for every document you
-rely on — exactly as the existing records do (`SRC-RR-1.pdf` → 200, 2,239,056 B, `%PDF-1.2`).
-Provenance you wrote down is worth more than provenance you assumed.
-
----
-
-## 8. The lawful things that do most of what people want from bulk libraries
-
-### 8.1 Openly published metadata corpora
-
-The "indexing" side of the §2 line — large, free, redistributable, provenance-clean. Probed
-2026-09-02 with a browser UA and `-L` [WEB] (S6):
-
-| Corpus | What it is | Probe |
-|---|---|---|
-| **Crossref public data file** | The full Crossref metadata corpus, released annually, free | HTTP 200; the landing page is a redirect stub of 403 *bytes* — not an HTTP 403 |
-| **OpenAlex snapshot** | The whole OpenAlex graph — works, authors, institutions, venues — **CC0**, S3-hosted | 200, 19,226 B. See [`open-access-full-text-sources.md` §2.2](open-access-full-text-sources.md) |
-| **dblp** | The canonical CS bibliography. Daily XML dump, **CC0**, ~1.10 GB gzipped | 200, 2,512 B index. Fetch the DTD too or it will not parse |
-| **Open Library data dumps** | Internet Archive's open bibliographic database of books | 200, 30,187 B |
-| **Unpaywall data snapshot** | OA-location data for tens of millions of DOIs | 200, 1,421 B |
-| **arXiv / HAL / Zenodo OAI-PMH** | Per-repository harvest interfaces | See the individual records in this directory |
-| **HathiTrust Hathifiles** | Item-level metadata for the HathiTrust corpus | **200, 45,607 B** on the deep Hathifiles path with a browser UA. A **403 against the bare hostname** was recorded earlier in this pass — worth carrying into [`retrieval-notes.md`](retrieval-notes.md): the shallow URL is not a reliable test of the deep one |
-| **DOAB** (Directory of Open Access Books) | Metadata for openly licensed scholarly books | **403, 5,556 B** (Cloudflare) to scripts on the probe date |
-
-Between them these answer nearly every question people actually take to a shadow library's search
-box — *does this work exist, who wrote it, what is its canonical citation, is there a free copy* —
-without touching a copyrighted byte.
-
-### 8.2 "Private collections": personal, lab and course collections
-
-The grey middle: personal paper stashes, lab collections, Zotero/Mendeley group libraries,
-university course-page PDF directories, curated GitHub reading lists. Many are **lawful** — author
-copies posted under a publisher's self-archiving allowance, materials used under fair use / fair
-dealing in teaching, or explicitly licensed works — and they are genuinely useful, because a human
-curated them and wrote down why each item is on the list.
-
-Named examples, each measured on **2026-09-02** [WEB] [API] (S6):
-
-| Collection | What it is | Measured |
-|---|---|---|
-| **MIT 6.5840 / 6.824 Distributed Systems** — `pdos.csail.mit.edu/6.824/schedule.html` | Course reading list: MapReduce, GFS, "Paxos Made Simple", the extended Raft paper, Spanner, ZooKeeper, FaRM | 200, 17,414 B, **20 linked PDFs**. `6.5840` and `6.824` serve the identical document. Stable for years; the best curated entry point to the distributed-systems canon |
-| **Readings in Database Systems, 5th ed. ("the Red Book")** — `redbook.io` | Bailis, Hellerstein & Stonebraker (eds). Free HTML and PDF chapters with editorial commentary | 200 (redirects to `www.`), 5,594 B, 15 PDF links. **Published free by its own editors** — the model of what a curated collection should be |
-| **CMU 15-721 Advanced Database Systems** — `15721.courses.cs.cmu.edu/spring2024/schedule.html` | Andy Pavlo's per-lecture reading list, with slides and notes | 200, 117,066 B, **166 paper links**. Companion `15445.courses.cs.cmu.edu` 200, 32,181 B |
-| **SAFARI / ETH Zürich Computer Architecture** — `safari.ethz.ch/architecture/fall2023/doku.php` | Onur Mutlu's course: openly published lecture materials and per-topic reading lists across memory systems, DRAM, processing-in-memory | 200, 32,717 B (`<title>start [Computer Architecture - Fall 2023]</title>`). Faculty page `people.inf.ethz.ch/omutlu/` 200, 19,912 B |
-| **`0xor0ne/awesome-list`** — "Awesome Cybersecurity List" | Curated links to blog posts, write-ups and papers, heavy on embedded/IoT/firmware security — directly relevant to this knowledge base | **CC-BY-SA-4.0**, 4,089★, pushed 2026-08-30. Contents are `README.md` + `topics/` — **links, not files** |
-| **`secfigo/Awesome-Fuzzing`** · **`sbilly/awesome-security`** | Curated fuzzing papers/tools; broad security resource list | **CC0-1.0**, 5,910★, 163 KB · **MIT**, 14,827★, 781 KB. Both explicitly licensed and links-only |
-| **`theanalyst/awesome-distributed-systems`** · **`dgryski/awesome-consensus`** | Distributed-systems and consensus bibliographies | 12,359★ / 96 KB and 2,146★ / 37 KB, both **`license: null`** — links-only, so squarely lawful, but nothing is declared |
-| **USENIX proceedings** · **IACR ePrint** | Every USENIX paper free by policy; 27,552 ePrint reports, CC-BY, full OAI-PMH | The two largest *lawful* bulk corpora in systems and crypto. [`open-access-full-text-sources.md` §3.1](open-access-full-text-sources.md) · [`cryptology-eprint-archive.md`](cryptology-eprint-archive.md) |
-| **Zenodo communities** | Curated, DOI-minted, explicitly licensed collections of papers, datasets and firmware. `q="RISC-V"` → **496 records** [API] (S9) | [`zenodo.md`](zenodo.md). **This is how to make your own curated collection citable and lawful** |
-
-**And now the counter-examples**, because "curated by a nice person on GitHub" is not a legal status.
-GitHub API, 2026-09-02 [API] (S6):
-
-| Repo | Measured | The problem |
-|---|---|---|
-| **`papers-we-love/papers-we-love`** | **109,438★, ~225 MB**, pushed 2026-08-31, ~50 topic dirs (`computer_architecture`, `distributed_systems`, `datastores`, `concurrency`, `garbage_collection`, `cryptography`, …) | One of the best-known curated CS paper collections in existence — and **`license: null`, no `LICENSE` file in the root.** It redistributes PDFs whose individual copyright status is mixed and undeclared |
-| **`wcventure/FuzzingPaper`** | 2,768★, **~224 MB**, **MIT**, with a `Paper/` directory of PDFs | The MIT licence covers the *repository*, not the third-party papers inside it. A declared licence on a repo that redistributes others' work tells you nothing about the work |
-| **`larsbrinkhoff/awesome-cpus`** | 2,003★, **~461 MB**, **CC0-1.0** | An "awesome list" that also stores documents. Same caution |
-| **`rxin/db-readings`** · **`aphyr/distsys-class`** | 8,138★ / ~29 MB / `null`; 9,881★ / 96 KB / `null` (its `README.markdown` states no licence) | Excellent curation, undeclared terms |
-
-**The pattern:** a link list is almost always fine; a repository that ships the PDFs is a
-redistribution question no matter how good the curation or how permissive the repo's own licence.
-Use all of them to *find* the paper, then run §7.2 and fetch the copy whose provenance you can state.
-
-### 8.3 Trackers and preservation projects — where the line falls
-
-- **Bibliographic and coverage trackers** — the scientometric studies in §3.2, OpenAlex's OA-status
-  fields, Unpaywall's location data, dblp. These *measure* what exists and what is open. **Lawful,
-  useful, citable**, and the reason anyone can discuss shadow-library coverage in numbers at all
-  without redistributing anything.
-- **Web and code archives** — the Internet Archive, Arquivo.pt, Software Heritage, bitsavers, Common
-  Crawl. These *do* redistribute full text, but under statutory exceptions, rightsholder tolerance,
-  explicit permission, or the operator's own ownership of the physical originals (bitsavers, where
-  Al Kossow scanned his own collection). See
-  [`recovering-dead-technical-sites.md`](recovering-dead-technical-sites.md).
-- **Community torrent-seeding of shadow-library dumps** — the 2019 LibGen seeding effort and the
-  2021 r/DataHoarder Sci-Hub backup organised in response to the Delhi filing [COM] (S1, S3).
-  Sincerely motivated by preservation; **still redistribution of copyrighted works**, and no court in
-  §§3–6 treated preservation motive as a defence.
-
-The distinction is not about intent. It is about whether the bytes being moved are the copyrighted
-work.
-
----
-
-## 9. Decision table
-
-| What you are looking for | Where to look | Lawful? | Reliable? |
-|---|---|---|---|
-| A systems / OS / networking / storage / security **conference paper** | **USENIX**, then dblp → publisher | ✅ | ✅ version of record |
-| A **crypto or embedded-security** paper | **IACR ePrint**, TCHES | ✅ | ✅ |
-| An **NLP / computational-linguistics** paper | **ACL Anthology** | ✅ | ✅ |
-| Anything with an **arXiv ID** | arXiv, via Semantic Scholar `externalIds.ArXiv` (Unpaywall misses these) | ✅ | ⚠️ check whether the arXiv version is the published one |
-| A **paywalled IEEE** paper | TechRxiv via Crossref `is-preprint-of`; then the author's page; then email the author | ✅ | ⚠️ author's version, not the VoR |
-| The **canonical citation** for a half-remembered CS paper | **dblp** | ✅ | ✅ best in class |
-| Whether a **free copy exists anywhere** | Unpaywall → OpenAlex `locations[]` → CORE / BASE / OpenAIRE | ✅ | ✅ |
-| A **reading list** in distributed systems, databases, architecture or security | MIT 6.5840 · CMU 15-721 · SAFARI/ETH · the Red Book · `0xor0ne/awesome-list` · `secfigo/Awesome-Fuzzing` (§8.2) | ✅ (link lists and course pages) | ✅ for discovery — then resolve the DOI |
-| A **historical vendor manual, data book or corporate tech report** | **bitsavers**, then archive.org, then Wayback / Arquivo.pt | ✅ | ✅ scan is sound; **catalogue metadata often is not** (§7.1) |
-| A **dead vendor documentation URL** | Wayback `id_` → Arquivo.pt → Common Crawl WARC range-GET | ✅ | ✅ byte-exact if you use `id_` / range-GET |
-| A **deleted source repository** | **Software Heritage** | ✅ | ✅ content-addressed, verifiable offline |
-| **Bibliographic metadata at scale** | Crossref public data file, OpenAlex snapshot, dblp, Open Library dumps, Hathifiles | ✅ | ✅ |
-| A **current (post-2021) paper** | The ladder above. **Sci-Hub is frozen and does not have it** (§3.1) | — | — |
-| A **textbook** | Your library, the publisher's OA programme, DOAB, HathiTrust, Open Library controlled digital lending | ✅ | ✅ |
-| A **standard** | IETF/RFC free · RISC-V free · USB-IF free · JEDEC free w/ registration · IEEE SA ⚠️ mostly paid, partial GET Program | ✅ | ✅ |
-| A **GitHub repo that ships PDFs** (`papers-we-love`, `FuzzingPaper`, `awesome-cpus`) | Use it to find the citation, not as the source | ⚠️ repo licence ≠ paper licence (§8.2) | ⚠️ unstated version and edition |
-| Anything, from a **shadow library** | — | ❌ **Distributes copyrighted works without authorisation; found unlawful in multiple jurisdictions; may be unlawful where you are; commonly institution-blocked; documented credential-phishing and cloned-site risk** | ❌ **Version, edition, completeness and integrity all unverifiable** |
-
-**The short version:** for technical literature the lawful route is not a compromise — it is usually
-*better*, because it arrives with a resolvable identifier, a stated version and a URL you can cite.
-That is exactly what an unprovenanced PDF cannot give you, and exactly what this repository's
-evidence discipline requires.
-
----
-
-## 10. What this record could not verify
-
-- **Every operator-reported collection size** — Sci-Hub's 88,343,822 files (2022-07-15), Anna's
-  Archive's 71,400,751 books / 157,010,964 papers / ~1.1 PB (2026-08-20), Z-Library's 13.35 M books /
-  84.8 M articles / 220 TB (2023-02), LibGen's 80 M articles (2024-02-04) — is a **self-report relayed
-  by a third party**. **[NOT-VERIFIED]**; by policy this pass did not attempt to verify them, and the
-  current operational state of these services was likewise not probed, deliberately.
-- **Sci-Hub's freeze at primary-source level.** "Uploads paused December 2020; new-publication uploads
-  suspended during 2021 under the Indian injunction, except for batch releases" is consistently
-  reported [COM] and quoted verbatim in §3.1, but **no primary operator statement or court order was
-  retrieved** — **[NOT-VERIFIED]** as to the exact date and mechanism. Likewise the legal status of
-  **Sci-Net** (2025), and whether Anna's Archive metadata releases are lawfully sourced in the general
-  case (the WorldCat portion is now under a deletion order; the rest is unknown).
-- **Court documents were not read directly.** Every case in §§3–6 is sourced from Wikipedia's
-  referenced articles and the press reporting they cite — not from PACER, the Delhi High Court, or any
-  court's own docket. **Case numbers are therefore deliberately omitted.** Courts, dates, outcomes and
-  amounts are consistently reported across those sources, but the primary record was not consulted.
-  **No legal conclusion in this file is the author's own; each is a report of a court's or a source's
-  statement.**
-- **Licence status of the *contents* of any collection in §8.2.** What was measured is the repository-
-  or page-level licence field, not the copyright status of individual PDFs. That distinction is the
-  point of the counter-examples, and it is **[NOT-VERIFIED]** item by item.
-- **Three probes that failed, so nothing is claimed from them:** `doabooks.org` **403** (5,556 B,
-  Cloudflare), so DOAB's bulk-metadata terms were not read; `people.eecs.berkeley.edu/~kubitron/cs262/`
-  (Berkeley CS262A reading list) **failed to connect** (curl `000`); and `blog.acolyer.org` ("The
-  Morning Paper") answered **200 / 104,126 B** but could not be shown to be still updated, so it is not
-  listed as a live collection. All **[NOT-VERIFIED]**.
-- **Length note.** This record is longer than the 300–400 lines targeted for files in this directory.
-  The eleven subjects it was scoped to cover, each with the house evidence labels and a full sources
-  block, did not compress below this without dropping sourced content. Recorded rather than hidden.
-
----
-
-## 11. Sources
-
-Retrieval date **2026-09-02** throughout. Raw output:
-[`../../scratch/preprint-repositories/bulk-archives/`](../../scratch/preprint-repositories/bulk-archives/).
-
-Wikipedia extracts were taken via `en.wikipedia.org/w/api.php?action=query&prop=extracts&explaintext=1`
-and saved to the scratch directory. All are **[COM]** — press and community reporting, once removed.
-
-- **S1** *Sci-Hub* (32,354 chars, `wp-Sci-Hub.txt`) — founding and Elbakyan; the December 2020 upload
-  pause and 2021 suspension (quoted verbatim in §3.1); the 2022-07-15 file count; the September 2021
-  2.3 M batch; the US$15 M and US$4.8 M default judgments; the Delhi High Court case and the
-  2025-08-19 ban; the 2021 UK injunction and City of London Police warning; Sci-Net; the coverage
-  percentages; the Scholarly Kitchen dispute; the r/DataHoarder backup effort.
-- **S2** *Shadow library* (REST summary, 1,977 B) — the definition and the synonyms *pirate library* /
-  *black open access* in §2.
-- **S3** *Library Genesis* (9,020 chars) — the samizdat/RuNet lineage; ~2008 consolidation; library.nu
-  absorption; the 2024-02-04 composition table; the 2020 fork and its divergence; the August 2024
-  abandonment reports; the 2015 Elsevier and 2023–24 Pearson et al. litigation and the US$30 M
-  judgment; the CUII block; dual Russia/Netherlands registration; the Anthropic US$1.5 bn settlement.
-- **S4** *Anna's Archive* (19,649 chars) — the PiLiMi origin; CC0 source code; the source-library list;
-  the 2026-08-20 self-reported scale; the AAC format; the LLM SFTP-access programme; the OCLC,
-  Spotify/labels and 13-publisher matters; the Netherlands/UK/Germany blocking orders; the Meta ruling
-  and Chhabria's caveat.
-- **S5** *Z-Library* (10,964 chars) — the LibGen-mirror origin; the February 2023 self-reported scale
-  and 220 TB figure; the 2022-11-03 seizure of >240 domains; the E.D.N.Y. indictment of Napolsky and
-  Ermakova unsealed 2022-11-16; the July 2024 escape and Interpol notice; the later seizure rounds;
-  the French and Indian blocking orders; the Cybernews report of the ~10-million-user clone-site data
-  leak (quoted verbatim in §6).
-- **S6** Direct probes of lawful collections and corpora. **Full response codes and byte sizes are in
-  `probe-log-2026-09-02.txt`; the figures cited inline in §8 come from it.** [API] [WEB] Covers:
-  GitHub `/repos/…` for the ten curated repos named in §8.2 (stars, size, `license.spdx_id`,
-  `pushed_at`); the course and collection pages MIT `6.824`/`6.5840`, `redbook.io`, CMU `15-721` and
-  `15-445`, SAFARI/ETH `architecture/fall2023`, `people.inf.ethz.ch/omutlu/`; and the metadata
-  corpora Crossref public data file, OpenAlex snapshot docs, Open Library dumps, `dblp.org/xml/`,
-  Unpaywall snapshot, HathiTrust Hathifiles (**200 / 45,607 B**), `doabooks.org` (**403 / 5,556 B**)
-  and Berkeley CS262A (**connect failure**). Chrome UA with `-L` throughout, per
-  [`AGENTS.md`](../../AGENTS.md) step 2.
-- **S7** `api.crossref.org/works/<DOI>` for every identifier in §3.2, each title machine-checked
-  against the response — all six confirmed with venue and creation date. Also records the four
-  wrong-guess DOIs noted in §3.2. **[API]**
-- **S8** `api.openalex.org/works?search="Anna's Archive"` → `meta.count` **56**, including
-  `10.1073/pnas.2503051122` and `10.6084/m9.figshare.32454042`. **[API]**
-- **S9** `dblp.org/search/publ/api` for *"In Search of an Understandable Consensus Algorithm"* →
-  `@total: 1`, USENIX ATC 2014, `ee` = usenix.org. `zenodo.org/api/records?q="RISC-V"&size=1` →
-  `hits.total` **496**, consistent with [`README.md §4`](README.md#6-probing-traps)'s
-  quoted-vs-unquoted finding. **[API]**
-- **S10** Companion records: [`open-access-full-text-sources.md`](open-access-full-text-sources.md)
-  (the ladder, §3.1 USENIX, §5 green OA and version terminology),
-  [`recovering-dead-technical-sites.md`](recovering-dead-technical-sites.md) (§3.3 the archive.org
-  metadata and OCR failures, §4 bitsavers, §6 Software Heritage),
-  [`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md)
-  (§5 standards bodies), [`cryptology-eprint-archive.md`](cryptology-eprint-archive.md),
-  [`techrxiv.md`](techrxiv.md), [`zenodo.md`](zenodo.md), [`arxiv.md`](arxiv.md), and
-  [`README.md § Evidence and method`](README.md#evidence-and-method).
-- **S11** [`ai-crawler-site-access-table.md` § General retrieval tips](../../ai-crawler-site-access-table.md#general-retrieval-tips) —
-  the existing entry under *Alternate hosting of papers/PDFs* names Library Genesis and Anna's Archive
-  as places that "*may* hold what you're looking for when the original host is gone". **This record
-  does not contradict that framing; it qualifies it.** That entry already puts arXiv, ar5iv and author
-  self-archiving first, and treats bulk libraries as a fallback for material whose original host is
-  *gone*. This file supplies what that entry has no room for: for the technical literature in scope
-  the lawful copy nearly always exists (§1); the binding constraint on an unprovenanced copy is
-  reliability, not convenience (§7); and the legal and security position is as set out in §§3–6.
-
diff --git a/research/preprint-repositories/chemrxiv.md b/research/preprint-repositories/chemrxiv.md
deleted file mode 100644
index 5d937d4..0000000
--- a/research/preprint-repositories/chemrxiv.md
+++ /dev/null
@@ -1,430 +0,0 @@
-# ChemRxiv — preprint repository record
-
-- **URL:** https://chemrxiv.org/ · article URLs `https://chemrxiv.org/doi/full/<DOI>`
-- **Operator:** owned by the **American Chemical Society (ACS)** and operated as a
-  multi-society partnership. Crossref lists every deposit under the prefix `10.26434` with
-  publisher **"American Chemical Society (ACS)"** (S1) [API]. Partner co-owners, verified
-  only to 2019: **Royal Society of Chemistry** (joined 2018), **Gesellschaft Deutscher
-  Chemiker / German Chemical Society**, and the **Chinese Chemical Society** and
-  **Chemical Society of Japan** (both 2019) (S2) [COM/LIT].
-- **Discipline scope:** all of chemistry, plus the large chemistry/materials/computational
-  overlap (§3).
-- **Launched:** announced 2016, opened **2017**; earliest Crossref-registered deposits
-  **2017**, 173 that year (S1, S2) · **Status:** **active**, ~10,000 preprints/year, and
-  **on its third platform in nine years** (§2).
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-- **Access warning:** `chemrxiv.org` returned **HTTP 403 with a Cloudflare
-  `cf-mitigated: challenge` interstitial to every user-agent tried** on 2026-09-01
-  (default `curl`, Chrome, WhatsApp, ChatGPT-User) — see §9. **Everything below that is
-  labelled [API] comes from Crossref, not from ChemRxiv**, and the [WEB] items come from
-  the Internet Archive.
-
-## 1. What it is
-
-ChemRxiv is chemistry's answer to arXiv and bioRxiv: a free, non-profit-society-run
-preprint server, launched by ACS in 2017 after a 2016 announcement. Its name is
-pronounced "chem-archive"; the X is a chi (S2). Unlike bioRxiv it was born inside a
-publisher — the largest chemistry publisher in the world — and its early history is
-largely the story of that publisher's own journals deciding whether they would accept
-preprinted manuscripts. *Angewandte Chemie* said yes in March 2018; **JACS not until
-August 2018** (S2) [COM]. That reluctance is why ChemRxiv's first-year volume was tiny
-(173 deposits in 2017) and why it took until 2020 to pass 5,000/year.
-
-It is now firmly established: **53,678 distinct preprints** through 2026-09-01, growing
-~10,000/year (§4). For this knowledge base it is the single most relevant *chemistry*
-server, because chemistry is where your materials come from — see §7.
-
-## 2. Platform history — three platforms in nine years
-
-This is the most consequential operational fact about ChemRxiv and it is not in
-Wikipedia. The DOI grammar under prefix `10.26434` changes cleanly at each migration,
-which makes the history verifiable from Crossref alone (S1) [API]:
-
-| Era | DOI pattern | Example (verified) | Platform |
-|---|---|---|---|
-| 2017 – mid-2021 | `10.26434/chemrxiv.<numeric>.v<N>` | `10.26434/chemrxiv.6406505.v1` (2018-06) | **figshare** (Digital Science) |
-| mid-2021 – 2025 | `10.26434/chemrxiv-<year>-<slug>[-v<N>]` | `10.26434/chemrxiv-2024-glhqn` (2024-06) | **Cambridge Open Engage** (Cambridge University Press) |
-| 2026 – | `10.26434/chemrxiv.<numeric>/v<N>` | `10.26434/chemrxiv.15004130/v1` (2026-06) | **new platform**, provider not stated (§9) |
-
-**figshare → Cambridge Open Engage.** A Wayback capture of `https://chemrxiv.org/` from
-**2021-02-10** still carries `<meta name="application-name" content="figshare">` and
-loads its assets from `figstatic.com`, with the title "ChemRxiv: the Preprint Server for
-Chemistry" (S3) [WEB]. Article URLs of that era were figshare's
-`chemrxiv.org/articles/<slug>/<numeric-id>` (S4). The first `chemrxiv.org/engage/…`
-captures are from 2021, and the Wayback capture index for
-`chemrxiv.org/engage/chemrxiv/public-dashboard` begins **2021-06-20** (S5). So the move
-to Cambridge Open Engage happened **between February and June 2021**; I could not pin an
-exact announcement date — **[NOT-VERIFIED]**.
-
-**Cambridge Open Engage → new platform, January 2026.** The last useful capture of the
-Engage-era dashboard, **2026-01-21**, is titled "Homepage | ChemRxiv | **Cambridge Open
-Engage**" and carries a site notice reading: *"ChemRxiv is no longer accepting new
-submissions or versions as we process our queue and prepare to transfer all content to
-our new platform on January 21. New submissions will be welcome on the new site when it
-launches."* (S6) [WEB]. Three independent signals confirm the migration actually
-happened:
-
-1. The DOI grammar changes on schedule — every 2026-posted DOI uses the new
-   `chemrxiv.<numeric>/v<N>` form, and **all 6,579 `/v1` and 1,725 `/v2+` DOIs in the
-   corpus are 2026 records** (S1) [API].
-2. `chemrxiv.org/engage/chemrxiv/public-dashboard` returns **403** in the Wayback index
-   from 2026-03-21 onward (S5).
-3. **Every** ChemRxiv DOI — figshare-era, Engage-era and new — now has Crossref
-   `resource.primary.URL` of the form `https://chemrxiv.org/doi/full/<DOI>` (S7) [API].
-   The whole corpus was re-pointed at a single new URL grammar.
-
-**[INF] on who the new provider is:** `/doi/full/<DOI>` is the URL grammar of **Atypon
-Literatum**, and it is exactly what ACS uses on `pubs.acs.org/doi/full/10.1021/…`. That,
-plus the Cloudflare posture, is consistent with ChemRxiv having been moved onto ACS's own
-publishing platform. **This is an inference from URL shape, not a statement from the
-operator, and I could not confirm it** — the site is unreachable (§9). Treat as
-**[NOT-VERIFIED]**.
-
-**Why it matters.** Two full-corpus migrations in five years, with the DOI *suffix
-grammar changing each time*, is a real durability signal. The DOIs do still resolve — that
-is the point of DOIs, and ChemRxiv has done it correctly — but any local cache of
-ChemRxiv landing-page URLs built before 2026 is now stale, and any scraper written
-against the Engage `public-api` is dead.
-
-## 3. Scope and subject taxonomy
-
-Seventeen categories, with article counts as displayed on the ChemRxiv dashboard on
-**2026-01-21** (S6) [WEB]. Unlike bioRxiv, **categories are multi-select** — these sum to
-70,544 assignments over 36,917 items shown live, ~1.9 categories each [INF]:
-
-| Category | Articles | Category | Articles |
-|---|---|---|---|
-| **Theoretical and Computational Chemistry** | 10,411 | **Nanoscience** | 3,033 |
-| Organic Chemistry | 8,519 | **Energy** | 2,755 |
-| **Physical Chemistry** | 7,401 | **Polymer Science** | 2,358 |
-| **Catalysis** | 6,373 | **Chemical Engineering and Industrial Chemistry** | 1,944 |
-| Biological and Medicinal Chemistry | 6,072 | Organometallic Chemistry | 1,858 |
-| **Materials Science** | 5,627 | Earth, Space, and Environmental Chemistry | 1,241 |
-| **Materials Chemistry** | 4,957 | Chemical Education | 476 |
-| **Inorganic Chemistry** | 3,856 | Agriculture and Food Chemistry | 396 |
-| **Analytical Chemistry** | 3,267 | | |
-
-The bolded categories are the ones a hardware person should care about. **Theoretical and
-Computational Chemistry is the single largest category on the server** — ChemRxiv is, in
-practice, a major venue for computational-methods and machine-learning-for-chemistry work.
-
-## 4. Size and growth
-
-Derived by paginating **every** Crossref record under prefix `10.26434` on **2026-09-01**
-(S1) [API]; script and log in
-`scratch/preprint-repositories/lifesci/chemrxiv-crossref-scan.txt`.
-
-- **Total registered DOIs: 55,403.** All of type `posted-content` / subtype `preprint`.
-- Of those, **1,725 are version-2-or-higher DOIs**, all posted in 2026 (the new platform
-  registers each version separately; the two earlier platforms did not).
-- **Distinct preprints: 53,678.**
-
-| Year posted | DOIs | Distinct preprints |
-|---|---|---|
-| 2017 | 173 | 173 |
-| 2018 | 1,088 | 1,088 |
-| 2019 | 2,873 | 2,873 |
-| 2020 | 4,985 | 4,985 |
-| 2021 | 5,240 | 5,240 |
-| 2022 | 6,029 | 6,029 |
-| 2023 | 7,277 | 7,277 |
-| 2024 | 8,824 | 8,824 |
-| 2025 | 10,085 | 10,085 |
-| 2026 (to 09-01) | 8,829 | 7,104 |
-
-Growth is steady and monotonic since 2019 — no COVID whipsaw of the kind bioRxiv shows,
-and no flattening.
-
-**Recorded conflict.** The ChemRxiv dashboard on **2026-01-21** advertised **"36,917 Live
-Content"**, alongside 75,455,050 abstract views, 29,462,885 content downloads and 12,460
-citations (S6) [WEB]. Crossref's cumulative count at end-2025 is **46,574**. The two do
-not reconcile. Possible explanations [INF]: the dashboard counter was stale (openRxiv's
-is, see the sibling record); or "Live Content" excludes withdrawn/removed items and
-items whose full text never posted; or the metric was scoped differently. I cannot
-resolve it because the live site is unreachable. **Report both, dated.**
-
-Wikipedia's figures are stale and much smaller ("more than 1,000 submissions in the first
-eighteen months"; "2,314 in 2019", the latter attributed to Coudert 2020) (S2). Note the
-Wikipedia/Coudert 2019 figure of 2,314 is close to but below Crossref's 2,873 for 2019 —
-plausibly a submissions-vs-postings or cut-off-date difference.
-
-## 5. Screening and moderation
-
-**Poorly verified, and I want to be explicit about that.** ChemRxiv's policy pages are
-behind the Cloudflare challenge (§9) and the Wayback captures I could reach are dashboard
-pages, not policy pages.
-
-What is directly attested (S6) [WEB], from the site's own standing notices:
-
-- "Content on ChemRxiv is early research and has not been peer reviewed prior to posting."
-- "These are preliminary reports which have not been peer-reviewed. They should not be
-  regarded as conclusive, guide clinical practice/health related behaviour, or be reported
-  in news media as established information."
-
-The presence of a moderation queue is attested indirectly: the January 2026 migration
-notice speaks of "process[ing] our queue", and an older standing notice warns that
-"during the holiday season, submission processing times may increase slightly. We will
-review all submissions as quickly as possible" (S6) — i.e. human screening with a
-turnaround, not instant posting.
-
-Contemporary reporting during COVID-19 describes ChemRxiv among the preprint servers that
-tightened screening against low-quality coronavirus submissions (Kwon, *Nature* 581:130–131,
-2020, `10.1038/d41586-020-01394-6`) (S8) [COM/LIT] — but I did not retrieve that article's
-text, so the specifics of ChemRxiv's screen are **[NOT-VERIFIED]**.
-
-**Do not assume ChemRxiv screening is comparable to bioRxiv's**, which is documented in
-detail. It may be; I could not check.
-
-## 6. Reliability — what you can and cannot trust
-
-A ChemRxiv deposit guarantees a Crossref DOI, a timestamp, a version history, and that
-*someone* looked at it before posting. It does not guarantee peer review, and the server
-says so on every page.
-
-- **Eventual-publication rate: not measured.** Unlike bioRxiv/medRxiv, ChemRxiv exposes no
-  machine-readable preprint→publication link, and I found no study measuring it. This is
-  the single biggest gap relative to the sibling
-  [bioRxiv/medRxiv record](biorxiv-and-medrxiv.md).
-- **Checking an individual preprint:** resolve the DOI via Crossref
-  (`https://api.crossref.org/works/<doi>`) to confirm it is a real registered deposit and
-  read `posted`, `license` and `resource.primary.URL`. Then search Crossref for the same
-  title as a `journal-article` to see whether it was ever published — you must do manually
-  what the bioRxiv API does for you.
-- **Version count is visible in the DOI suffix** on both the figshare-era (`.vN`) and
-  post-2026 (`/vN`) records, and often on Engage-era ones (`-vN`). A `-v3` or `/v4` is a
-  paper that has been reworked; a bare v1 from 2019 has not.
-- **ACS ownership is a structural conflict worth naming.** The server is owned by the
-  largest commercial-scale chemistry publisher, whose journals are the most likely
-  destination for the content. Nothing observed suggests misuse, but it is a materially
-  different governance position from openRxiv's independent non-profit or arXiv's
-  university host. The multi-society partnership (RSC, GDCh, CCS, CSJ) exists partly to
-  answer exactly that objection (S2).
-
-## 7. Why an electronics or hardware person should care
-
-Chemistry is upstream of every component you buy. ChemRxiv is where the pre-review version
-of that work appears. Concrete examples, **each verified as a real ChemRxiv deposit via
-Crossref** (DOI, posted date) (S9) [API]:
-
-**Semiconductor process chemistry and photoresists**
-
-- *Synthesis of End-Cap Enabled Self-Immolative Photoresists for Extreme Ultraviolet
-  Lithography* — `10.26434/chemrxiv-2022-1ps85`, 2022-07-04
-- *Extreme Ultraviolet and Beyond Extreme Ultraviolet Lithography using Amorphous Zeolitic
-  Imidazolate frameworks* — `10.26434/chemrxiv-2025-s1n4s`, 2025-06-18
-- *On the limitations of thermal atomic layer deposition of InN using ammonia* —
-  `10.26434/chemrxiv-2022-s9dvr`, 2022-12-06
-- *In0.5Ga0.5N Layers by Atomic Layer Deposition* — `10.26434/chemrxiv.14671575.v1`,
-  2021-05-25
-- *Opportunities and Challenges of Machine Learning in Atomic Layer Deposition* —
-  `10.26434/chemrxiv-2025-v35x7`, 2025-12-10
-- *Chemical Vapor Deposition of Uniform and Large-Scale MoS2 Using Heterogeneous
-  Precursors* — `10.26434/chemrxiv-2025-tz2gv`, 2025-10-08
-
-**Batteries and electrolytes**
-
-- *Reactive molecular dynamics simulations of Lithium-ion battery electrolyte degradation*
-  — `10.26434/chemrxiv-2024-bd6mh`, 2024-04-29
-- *Lithium-Ion Battery Electrolyte Structural Transport Mechanism: Attempt Frequencies and
-  Activation Free energies* — `10.26434/chemrxiv.15004288/v1`, 2026-06-04 (v2 2026-07-16)
-- *Synergistic Effects of Solid Electrolyte Mild Sintering and Lithium Surface Passivation*
-  — `10.26434/chemrxiv-2025-cdks6`, 2025-09-29 (v2 2025-12-16)
-- *High-Throughput Ionic Conductivity Trend Predictions of Lithium Argyrodites and Garnets
-  as Solid State electrolytes* — `10.26434/chemrxiv.15006536/v1`, 2026-07-24
-
-**Conductive polymers, displays and photovoltaics**
-
-- *Transparent conductive PEDOT–graphene films from large-flake graphite* —
-  `10.26434/chemrxiv-2024-rbc36`, 2024-10-03
-- *Efficient Orange Organic Light-Emitting Diodes Employing a Central Aniline Bridged
-  Multiresonant TADF emitter* — `10.26434/chemrxiv-2023-wk0nc`, 2023-12-07
-- *Understanding the full zoo of perovskite solar cell impedance spectra with the standard
-  drift-diffusion model* — `10.26434/chemrxiv-2024-rfv0n`, 2024-02-04
-
-**Analytical instrumentation and lab automation** — the `Analytical Chemistry` (3,267) and
-`Chemical Engineering` (1,944) categories carry spectrometer, chromatography and detector
-methodology, and increasingly robotics:
-
-- *A Self-Driving Lab for Nano- and Advanced Materials Synthesis* —
-  `10.26434/chemrxiv-2024-f13l1`, 2024-12-08
-- *Human–Robot Collaborative Reaction Development with a Self-Driving Laboratory* —
-  `10.26434/chemrxiv.15008166/v1`, 2026-09-01
-- *New Self-supporting Polymer Thin Film for Nanoparticle Analysis in STEM/TEM* —
-  `10.26434/chemrxiv-2025-50x35`, 2025-07-29
-
-If you want one sentence: **ChemRxiv is where EUV resist chemistry, ALD precursor
-chemistry, electrolyte formulation and TADF emitter design show up six to eighteen months
-before the ACS/RSC/Wiley paper.**
-
-## 8. Boundary with ECSarXiv
-
-There is a real overlap with **[ECSarXiv](ecsarxiv.md)**, the Electrochemical Society's
-OSF-hosted server, and the boundary is worth stating because you will otherwise miss half
-the literature:
-
-| | ChemRxiv | [ECSarXiv](ecsarxiv.md) |
-|---|---|---|
-| Size | 53,678 preprints (§4) | ~323 deposits total |
-| Owner | ACS + partner societies | The Electrochemical Society |
-| Platform | own/Atypon-style (2026–) | OSF Preprints (white-label) |
-| Centre of mass | synthesis, computation, materials chemistry | electrochemistry + **solid state science and technology** |
-| Overlap | batteries, electrolytes, electrodeposition, corrosion, sensors | same |
-
-ChemRxiv is ~165× larger and is where almost all of the battery- and
-materials-chemistry volume actually goes. ECSarXiv is worth checking anyway for two
-reasons: ECS's remit explicitly includes *Dielectric Science and Materials*, *Electronic
-Materials and Processing* and *Electronic and Photonic Devices and Systems*, which
-ChemRxiv's taxonomy does not name; and ECSarXiv content is on OSF, so it is trivially
-machine-accessible while ChemRxiv currently is not (§9). **Search both; expect ChemRxiv
-to have 99 % of the hits and ECSarXiv to occasionally have the device-oriented one.**
-
-## 9. Access, APIs and bulk retrieval
-
-**The live site is not machine-accessible as of 2026-09-01.** Probe results:
-
-| Probe | UA | Result |
-|---|---|---|
-| `https://chemrxiv.org/` | `curl/8.5.0` | **403**, 5,360 B |
-| `https://chemrxiv.org/` | Chrome 131 | **403**, 5,595 B |
-| `https://chemrxiv.org/` | `WhatsApp/2.23.20.0` | **403**, 5,381 B |
-| `https://chemrxiv.org/` | `ChatGPT-User/1.0` | **403**, 5,616 B |
-| `https://chemrxiv.org/engage/chemrxiv/public-api/v1/items?limit=1` | Chrome 131 | **403**, 5,803 B |
-
-Response headers show `server: cloudflare`, **`cf-mitigated: challenge`**, and a
-`Just a moment…` JS-challenge body. This is a browser-integrity challenge, not an
-IP block and not a robots policy. Per house rules I am recording this as a retrieval
-observation only; it says nothing about whether a normal browser can read the site, and I
-did not attempt to defeat it. **A sibling agent reached the same result independently.**
-
-**The Engage-era public API existed** at
-`https://chemrxiv.org/engage/chemrxiv/public-api/v1/items` — the Wayback Machine holds a
-**HTTP 200, 14,978-byte** JSON capture from **2024-03-21**, plus captures of
-`…/public-api/documentation` (200, 2,531 B, 2025-12-25; **404** by 2026-05-19) (S5) [WEB].
-That API went away with the platform. **Whether the 2026 platform exposes any API is
-[NOT-VERIFIED].**
-
-**The route that does work: Crossref.**
-
-```bash
-# every ChemRxiv deposit, paginated
-curl -s 'https://api.crossref.org/prefixes/10.26434/works?rows=1000&cursor=*&select=DOI,posted,license,title&mailto=you@example.org'
-# a single record
-curl -s 'https://api.crossref.org/works/10.26434/chemrxiv-2022-1ps85'
-```
-
-Full-text is **not** in Crossref — you get metadata, DOI, posted date, licence URL and the
-landing-page URL only. **There is no verified bulk full-text dump for ChemRxiv**
-(contrast the bioRxiv/medRxiv S3 requester-pays buckets). [NOT-VERIFIED]
-
-**Negative controls, 2026-09-01** [API]:
-
-- `https://api.crossref.org/prefixes/10.99999/works?rows=0` → **HTTP 404**, 19 bytes,
-  `Resource not found.` — Crossref rejects an unregistered prefix outright. ✅
-- `https://api.crossref.org/prefixes/10.26434/works?rows=0&query.bibliographic=zzzqqqxxnotarealthing`
-  → **HTTP 200**, 186 bytes, `total-results: 0` — a real 200 with an empty result set, so a
-  200 alone proves nothing; always read the count. ✅
-- `https://api.crossref.org/prefixes/10.26434/works?rows=0` → `total-results: 55403`,
-  facet `type-name` = **`Posted Content: 55403`**, i.e. the prefix contains nothing but
-  preprints. Good: the prefix is not shared with ACS journal content.
-
-ISSN **2573-2293 (Online)** is registered to ChemRxiv (S6).
-
-## 10. Licensing and reuse
-
-Authors choose. Distribution over all 53,678 distinct preprints, from the Crossref
-`license` field (S1) [API], 2026-09-01:
-
-| Licence | Preprints | Share |
-|---|---|---|
-| **CC BY-NC-ND 4.0** | 31,711 | 59.1 % |
-| **CC BY 4.0** | 10,215 | 19.0 % |
-| **CC BY-NC 4.0** | 5,127 | 9.6 % |
-| *no licence recorded in Crossref* | 6,612 | 12.3 % |
-| ChemRxiv terms-of-use URL | 13 | <0.1 % |
-
-**Three-fifths of ChemRxiv is CC BY-NC-ND** — no derivatives, no commercial use. Only
-19 % is CC BY. That is a markedly more restrictive corpus than bioRxiv (~36 % CC-BY/CC0)
-and much more restrictive than arXiv-plus-CC. If you intend to build a derivative dataset,
-this matters.
-
-The 12.3 % with no licence in Crossref is **entirely a 2026 phenomenon** — every one of the
-500 most recent records sampled had `license: none` (S1). Either the new platform is not
-depositing licence metadata to Crossref, or it has changed the model. **[NOT-VERIFIED];
-do not assume "no licence recorded" means "openly licensed".**
-
-## 11. Caveats
-
-1. **The site is Cloudflare-challenged to automated clients.** Plan on Crossref, not
-   scraping (§9).
-2. **Two full-corpus platform migrations (2021, 2026)** with three different DOI suffix
-   grammars. Old landing-page URLs and the old public API are dead; only the DOIs survive.
-3. **No published preprint-to-publication rate.** Unlike bioRxiv, you cannot ask the
-   server whether a preprint made it through review.
-4. **Screening policy could not be retrieved** (§5). Treat the gate as "unknown but
-   non-zero".
-5. **The dashboard "Live Content" figure (36,917 at 2026-01-21) disagrees badly with
-   Crossref (46,574 at end-2025).** Unresolved (§4).
-6. **Licence field went blank in 2026** (§10).
-7. **Wikipedia's article is materially out of date** — it does not mention either platform
-   migration and its size figures stop in 2019 (S2).
-8. **Owned by a publisher.** Not a fatal objection — the society partnership exists to
-   dilute it — but it is not the openRxiv model.
-
-## 12. Sources
-
-- **S1** Crossref REST API, prefix `10.26434` — `https://api.crossref.org/prefixes/10.26434/works`
-  (full cursor pagination, 55,403 records, `select=DOI,posted,license`) · retrieved
-  **2026-09-01** · totals, per-year counts, version-suffix analysis, licence distribution,
-  publisher string "American Chemical Society (ACS)", facet `type-name: Posted Content`.
-  Script and log: `scratch/preprint-repositories/lifesci/chemrxiv-scan.py`,
-  `chemrxiv-crossref-scan.txt`. [API]
-- **S2** https://en.wikipedia.org/wiki/ChemRxiv (raw wikitext) · retrieved 2026-09-01 ·
-  launch history (announced 2016, opened 2017), ACS/RSC/GDCh ownership, CCS and CSJ
-  joining 2019, *Angewandte* March 2018 / JACS August 2018, early size figures. Its own
-  cited sources are Chemistry World, C&EN, *Nature* and Coudert, *Nat Chem* 12:499–502
-  (2020) `10.1038/s41557-020-0477-5`. **Stale**: no mention of either platform migration.
-  [COM/LIT]
-- **S3** Wayback Machine capture of `https://chemrxiv.org/` at **20210210095447** ·
-  retrieved 2026-09-01 · `<meta name="application-name" content="figshare">`,
-  `figstatic.com` asset host — proof the server was still on figshare in Feb 2021. [WEB]
-- **S4** Wayback CDX index, `chemrxiv.org/articles*` · retrieved 2026-09-01 · figshare-style
-  article URLs (`/articles/<slug>/12440012`) captured 200 through mid-2020, 301 by 2025.
-  [WEB]
-- **S5** Wayback CDX index, `chemrxiv.org/engage*` and
-  `chemrxiv.org/engage/chemrxiv/public-api*` · retrieved 2026-09-01 · dashboard captures
-  2021-06-20 → 2026-03-21 (403 from 2026-03-21); `public-api/v1/items` 200/14,978 B at
-  2024-03-21; `public-api/documentation` 200 at 2025-12-25, 404 at 2026-05-19. [WEB]
-- **S6** Wayback capture of `https://chemrxiv.org/engage/chemrxiv/public-dashboard` at
-  **20260121073522** · retrieved 2026-09-01 · title "Homepage | ChemRxiv | Cambridge Open
-  Engage"; the migration notice quoted in §2; the 17 category counts in §3; key metrics
-  "36,917 Live Content / 75,455,050 Abstract Views / 29,462,885 Content Downloads / 12,460
-  Citations"; ISSN 2573-2293; the "not peer reviewed" standing notices. [WEB]
-- **S7** Crossref `resource.primary.URL` for `10.26434/chemrxiv.15004130/v1`,
-  `10.26434/chemrxiv-2024-glhqn`, `10.26434/chemrxiv.6406505.v1` · retrieved 2026-09-01 ·
-  all three now resolve to `https://chemrxiv.org/doi/full/<DOI>`. [API]
-- **S8** Kwon D. "How swamped preprint servers are blocking bad coronavirus research."
-  *Nature* 581:130–131 (2020-05-07), `10.1038/d41586-020-01394-6`. Cited via S2; **article
-  text not retrieved**. [COM]
-- **S9** Crossref `query.bibliographic` searches restricted to prefix `10.26434` ·
-  retrieved 2026-09-01 · every DOI, title and posted date listed in §7. [API]
-- **S10** Direct probes of `https://chemrxiv.org/` and
-  `https://chemrxiv.org/engage/chemrxiv/public-api/v1/items` with four user-agents, plus
-  `curl -I` response headers (`server: cloudflare`, `cf-mitigated: challenge`) · 2026-09-01.
-  [WEB]
-
-### Not verified
-
-- **Current consortium membership.** Verified to 2019 via S2 only. Whether RSC, GDCh, CCS
-  and CSJ are all still partners in 2026, and whether **CAS** (Chemical Abstracts Service,
-  a division of ACS) is a named partner, could not be confirmed — the About page is behind
-  the Cloudflare challenge.
-- **Exact date of the figshare → Cambridge Open Engage migration** (narrowed to
-  Feb–Jun 2021).
-- **Identity of the 2026 platform provider.** The `/doi/full/` URL grammar is
-  Atypon-Literatum-shaped and matches `pubs.acs.org`, but this is inference only.
-- **Screening policy and criteria** (§5).
-- **Any preprint-to-publication rate** for ChemRxiv.
-- **Whether the 2026 platform exposes a public API or any bulk full-text route.**
-- **Why 12.3 % of records (all 2026) carry no Crossref licence.**
diff --git a/research/preprint-repositories/chinaxiv.md b/research/preprint-repositories/chinaxiv.md
deleted file mode 100644
index 1101b10..0000000
--- a/research/preprint-repositories/chinaxiv.md
+++ /dev/null
@@ -1,336 +0,0 @@
-# ChinaXiv — preprint repository record
-
-- **URL:** https://chinaxiv.org/ · global index at https://global.chinaxiv.org/
-- **Operator:** National Science Library, Chinese Academy of Sciences
-  (中国科学院文献情报中心), built under CAS direction with support from the CAS Bureau of Science
-  Communication (中国科学院科学传播局) (S2)
-- **Discipline scope:** all disciplines — *as actually used*, dominated by astronomy, biology,
-  psychology, physics, library/information science and medicine; computer science is present but
-  small (§2, §3)
-- **Launched:** **2016** — stated in ChinaXiv's own help document (S2) [DOC]
-- **Status:** active. Home page and help pages served on 2026-09-01; newest listed submissions
-  dated 2026-08-30 (S1) [WEB]
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-ChinaXiv is the Chinese Academy of Sciences' national preprint platform. Its own help text
-describes it as built "按照中国科学院部署" (per CAS deployment) by the CAS National Science Library
-in **2016**, and states the ambition of being a "国家级预印本交流基础设施" — a *national-level*
-preprint exchange infrastructure — operated "按国际通行规范" (according to internationally
-accepted norms) (S2) [DOC].
-
-Two things about it surprise Western readers.
-
-First, **it is much smaller than its front page suggests.** The headline counter reads
-4,110,127, but that is an aggregate: ChinaXiv's *own* holdings are **47,362**, and the remaining
-**4,062,765** are an index of *international* preprints harvested from elsewhere (§3). If you cite
-"ChinaXiv has 4.1 million papers" you have cited the wrong number by a factor of ~87.
-
-Second, **it moderates, and it says so plainly** — including a screen that has no analogue on
-arXiv. ChinaXiv's help document states that a submission is publishable so long as it contains no
-"较大的政治问题或学术问题" — *major political or academic problems* (§4). That is an unusually
-candid statement of a political-scope check, published by the operator itself.
-
-Since **2022** ChinaXiv has run a "2.0" release: bilingual interface, the ChinaXiv-Global preprint
-index, open commenting/review features, **CSTR** identifier registration for all preprints, and
-interconnection with CAS platforms SciEngine, ScienceDB and CSCD (S2) [DOC].
-
-## 2. Scope and subject taxonomy
-
-ChinaXiv uses a Chinese national discipline classification, not arXiv-style category codes. The
-computing- and electronics-relevant classes, with live counts from the home page browse panel
-(2026-09-01) (S1) [WEB]:
-
-| Class (Chinese) | English | Records |
-|---|---|---|
-| 计算机科学 | **Computer science** | **2,052** |
-| 图书馆学、情报学 | Library & information science | 3,496 |
-| 数字出版 | Digital publishing | 3,223 |
-| 光学 | Optics | 1,590 |
-| 材料科学 | Materials science | 1,234 |
-| 核科学技术 | Nuclear science & technology | 930 |
-| 动力与电气工程 | Power & electrical engineering | 599 |
-| 土木建筑工程 | Civil & architectural engineering | 251 |
-| 工程与技术科学 | Engineering & technology (general) | 224 |
-| 统计学 | Statistics | 218 |
-| 数学 | Mathematics | 222 |
-| 矿山工程技术 | Mining engineering | 166 |
-| 信息科学与系统科学 | **Information & systems science** | **85** |
-| 能源科学 | Energy science | 60 |
-| 航空、航天科学技术 | Aeronautics & astronautics | 55 |
-| 机械工程 | Mechanical engineering | 46 |
-| 电子与通信技术 | **Electronics & communications** | **40** |
-| 交通运输工程 | Transport engineering | 18 |
-| 水利工程 | Hydraulic engineering | 16 |
-| 测绘科学技术 | Surveying & mapping | 11 |
-| 安全科学技术 | Safety science | 6 |
-| 食品科学技术 | Food science | 4 |
-| 化学工程 | Chemical engineering | 2 |
-
-The large non-computing classes for context: 天文学 (astronomy) 7,554 · 生物学 (biology) 5,485 ·
-物理学 (physics) 3,823 · 心理学 (psychology) 3,712 · 地球科学 3,268 · 医学、药学 3,232 ·
-其他 (other) 1,774.
-
-**The engineering and electronics numbers are tiny.** Electronics & communications has **40**
-records in a decade. This is the central practical fact for a hardware or systems engineer.
-
-## 3. Size and growth
-
-Headline counters, read from the ChinaXiv home page on **2026-09-01**, default curl UA
-(S1) [WEB]. Verbatim source string:
-
-> `搜全球 4110127 论文总量 47362 ChinaXiv论文量 4062765 国际预印本论文量 202860565 论文访问量 62412214 论文下载量`
-
-| Counter | Chinese | Value |
-|---|---|---|
-| Total indexed | 论文总量 | 4,110,127 |
-| **ChinaXiv's own preprints** | **ChinaXiv论文量** | **47,362** |
-| International preprints indexed | 国际预印本论文量 | 4,062,765 |
-| Cumulative views | 论文访问量 | 202,860,565 |
-| Cumulative downloads | 论文下载量 | 62,412,214 |
-
-**Internal consistency check (passed):** 47,362 + 4,062,765 = 4,110,127 exactly. The two
-components sum to the headline, which supports reading 47,362 as native holdings and the balance
-as an external index [API-style arithmetic on WEB figures] [INF].
-
-**Second consistency check (near-miss, recorded not resolved):** the per-discipline browse counts
-in §2 sum to **46,427**, against the 47,362 native figure — a shortfall of **935** (~2.0%).
-Probable causes are uncategorised records or a differing refresh time between the two page
-widgets. Not investigated further. [WEB] [INF]
-
-The international index is surfaced separately at `global.chinaxiv.org`, whose links reveal
-harvested records from other servers with composite IDs such as `eartharxiv_1287251` and
-`psyarxiv_1287871` (S1) [WEB]. So ChinaXiv-Global is a **discovery layer over other people's
-preprints**, not content ChinaXiv hosts.
-
-**Growth is real but modest**: the home page's "最新提交" (latest submissions) listed items dated
-2026-08-29 and 2026-08-30 at retrieval, i.e. the platform was taking deposits the day before the
-probe (S1) [WEB].
-
-**Not verified:** any year-by-year deposit series, and any independent scientometric measurement
-of ChinaXiv's size or growth. I found no machine-readable API and did not locate a published
-statistics page. **[NOT-VERIFIED]**
-
-## 4. Screening and moderation — what gets in
-
-ChinaXiv runs a genuine gate, documented in its own help file (S2) [DOC]. It calls this
-**形式审查** — *formal examination*, explicitly a form/eligibility check rather than peer review.
-
-Verbatim, §3.8 of the help document:
-
-> 用户提交的论文，将经系统与管理员的**形式审查**，包括：系统自动执行**格式、重复性、剽窃性、研究性**
-> 四项检验；管理员对论文详细页面进行检查，检查各字段填写是否准确、PDF打开是否正常、格式是否准确、
-> **学者的身份证明**是否符合要求、学科分类是否准确。通过审查后，论文即在平台发布。
-
-Which is, in operational terms:
-
-1. **Four automated checks**: 格式 format · 重复性 duplication · 剽窃性 plagiarism ·
-   研究性 whether it is actually research.
-2. **A human administrator check**: metadata field accuracy, that the PDF opens, formatting,
-   **whether the author's identity credentials meet requirements**, and correctness of the subject
-   classification.
-3. Only after passing does it publish.
-
-Rejection grounds are enumerated at §4.2 (S2) [DOC]: 格式不规范 (non-conforming format) ·
-重复性论文 (duplicate) · 剽窃性论文 (plagiarised) · 非研究性论文 (non-research). The author may
-fix and resubmit.
-
-**The political screen.** ChinaXiv's explanation of how preprints differ from journals says a
-submission may be published so long as (S2) [DOC]:
-
-> 只要作者提交至预印本平台的文章不存在**较大的政治问题**或学术问题，只要作者的文章具有一定的学术亮点，
-> 具有学术交流的价值，便可以在预印本平台上得到发布。
-
-— i.e. *provided the article has no major political problem or academic problem*, and has some
-academic merit and exchange value. This is stated by the operator, not inferred. Record it as
-such: **ChinaXiv applies a political-content criterion that arXiv, HAL and bioRxiv do not.**
-
-**Author identity.** Depositors may optionally (and are advised to) upload
-**研究身份识别材料** — research-identity credentials — including a list of their prior
-peer-reviewed publications, to speed identification and release (S2) [DOC].
-
-**Identifiers and withdrawal.** On submission a *temporary* ID is issued; the formal **ChinaXivID**
-is granted only after the review passes (S2) [DOC]. Withdrawal is deliberately hard: users cannot
-delete or retract an approved preprint themselves, and
-
-> 由于预发布论文是首发证明，所以平台**理论上不执行"撤销"操作**
-
-— because a preprint is proof of priority, the platform *in principle does not perform withdrawal*,
-except in special cases with reasoned author request and platform agreement, via an administrator
-(S2) [DOC]. Versions are updated in place through 版本更新 (version update) instead.
-
-## 5. Reliability — what you can and cannot trust
-
-What a ChinaXiv deposit **does** guarantee:
-
-- A timestamp and priority claim (首发权), which is the platform's stated purpose (S2) [DOC].
-- That an automated plagiarism/duplication check and a human formal review were passed (§4).
-- A **CSTR** identifier — since the 2.0 release ChinaXiv registers CSTR for all preprints (S2)
-  [DOC]. (CSTR resolution behaviour **not verified** here.)
-
-What it **does not** guarantee:
-
-- **No peer review.** The help text is explicit that preprints are "未经严格同行评议" — not
-  rigorously peer-reviewed — and characterises quality as lower than journal articles, with
-  post-hoc open review offered as the compensating mechanism (S2) [DOC].
-- **No guarantee of retractability.** The near-refusal to withdraw (§4) means an erroneous or
-  superseded preprint tends to stay up with a new version appended. When citing, pin the version.
-- **No independent quality signal you can read from outside.** Because article pages are not
-  retrievable by script (§8), you cannot cheaply audit a ChinaXiv record the way you can a HAL or
-  arXiv one.
-
-**Eventual-publication rate: not verified.** I found no measurement of what fraction of ChinaXiv
-preprints later appear in journals, and did not locate scientometric literature on ChinaXiv during
-this pass. **[NOT-VERIFIED]** — do not repeat any figure for this without a source.
-
-**Known-adjacent oddity worth flagging.** The home page's "最新活动" (latest activities) panel
-promotes a series of updates about a self-named "韬（τ）定律" ("Tao (τ) law"), including
-*"韬（τ）定律" V2版本在ChinaXiv更新发布* (2026-07-07) and a claim of a new result in the
-semiconductor field (2026-05-25) (S1) [WEB]. A named personal "law" being promoted on the
-operator's own front page is the kind of thing a reader should notice; I make no judgement on its
-content, which I did not read (article pages being unreachable, §8).
-
-## 6. What you actually find there — examples
-
-Concrete items listed on the home page's "最新提交" and related panels, **2026-09-01** (S1) [WEB].
-Note these are titles-as-displayed; **I could not open the article pages** (§8), so I do not
-present authors' affiliations or abstracts.
-
-- *Freshness-Aware Robust Cooperative Task Offloading in Dynamic SAGINs* — [计算机科学], 2026-08-30,
-  Lei Tao, Shihe Xu, Xinming Zhang. Space–air–ground integrated network task offloading; squarely
-  a distributed-systems/networking paper, in English.
-- *Proof-Valid Benchmarking for Approximate LLM Caching* — 2026-08-30. English.
-- *A Time Scaling Theory for Multi-Layer Electronic Syst…* — 2026-07-03. English.
-- *AMWNN: Auxiliary Multiresolution Wavelet-based Neural Networks for Solving Radiative Transfer
-  Problems* — [数学], 2026-08-30, Feng Han. English.
-- *Theoretical investigation of hydrogen bonding network …* — 2026-08-30, multi-author.
-- Chinese-language items dominate psychology and education, e.g.
-  *减负成效为何易反弹：执行功能视域下作业负担的生成机理与治理启示* — [心理学], 2026-08-30, 张海.
-
-Most-downloaded list (热门论文排行) is overwhelmingly Chinese-language psychology, e.g.
-*孤独症人群会话障碍的研究进展和展望* (15,936 views) (S1) [WEB].
-
-**The realistic take for a Western engineer.** The computer-science stream is small (2,052 items)
-but **a meaningful share of recent CS submissions are written in English** — of the CS/maths items
-visible on the front page on 2026-09-01, the majority carried English titles. So ChinaXiv is not a
-language-locked resource for CS the way it is for psychology. What it is *not* is a place where
-you will find work you cannot find elsewhere: there is no ChinaXiv equivalent of HAL's INRIA
-report series. Treat it as a **supplementary discovery surface for recent Chinese CS/ML
-preprints**, not a primary literature source, and expect to be unable to fetch the PDFs
-programmatically.
-
-## 7. Landmark papers
-
-**None identified.** I found no paper on ChinaXiv in software, distributed systems, databases,
-electronics or security that has become a landmark in the sense used elsewhere in this collection.
-This is consistent with the size figures (§2: 2,052 CS records, 40 electronics records) and with
-the fact that Chinese CS groups overwhelmingly preprint to arXiv. Combined with the inability to
-open article pages (§8), I decline to construct a landmark table. **[NOT-VERIFIED]** — absence of
-evidence here is partly an artefact of my access limits, and should be re-checked by someone who
-can render the site in a browser.
-
-## 8. Access, APIs and bulk retrieval
-
-Probed **2026-09-01**. This section is the main practical warning in this record.
-
-**Reachability from outside China: partial.** The site *is* reachable — the home page returned
-HTTP 200 with **the default curl user-agent**, no UA substitution required, in ~2.6 s
-(104,948 bytes). No geoblock, no CAPTCHA, no bot-interstitial (S1).
-
-| Target | Result (2026-09-01) | UA needed |
-|---|---|---|
-| `https://chinaxiv.org/home.htm` | **HTTP 200**, 104,948 B | default curl |
-| `https://chinaxiv.org/user/help.htm` | **HTTP 200**, 64,223 B | default curl |
-| `https://global.chinaxiv.org/` | HTTP 200, but only **2,027 B** — JS shell, no content | default curl |
-| `https://chinaxiv.org/abs/202605.00224` (real ID) | **HTTP 403** | **all five UAs failed** |
-| `https://chinaxiv.org/abs/202606.00108` (real ID) | **HTTP 403** | **all five UAs failed** |
-| `https://chinaxiv.org/user/download.htm?id=61234` | HTTP 405 | — |
-| `https://chinaxiv.org/user/about.htm` | HTTP 404 | — |
-
-**Article pages are blocked at the route level, not by user-agent.** Every `/abs/` request returned
-HTTP **403** with a page titled **系统正在维护中** ("system under maintenance", 4,729 bytes), and
-this was identical across the full fallback ladder: default curl, Chrome 131, WhatsApp/2.23.20.0,
-ChatGPT-User/1.0 and ClaudeBot/1.0. **Rotating user-agents does not help here** — record that, so
-nobody burns time on it.
-
-**Negative controls** (essential, because 403 and 404 mean different things here):
-
-| Probe | Result | Reading |
-|---|---|---|
-| `/this-page-does-not-exist-zzz.htm` (bogus) | HTTP **404**, title 您访问的页面不存在 ("the page you visited does not exist") | Genuine 404 path exists and is distinguishable |
-| `/abs/999999.99999` (bogus ID) | HTTP **403**, title 系统正在维护中 | Same as a *real* ID — so 403 carries **no** information about whether the record exists |
-| `/abs/202605.00224` (real ID from home page) | HTTP **403**, title 系统正在维护中 | Confirms the block is route-wide |
-
-The consequence: **you cannot verify the existence of an individual ChinaXiv record by HTTP status
-from outside.** A 403 is returned for real and fabricated identifiers alike. Any claim in this file
-about a specific paper rests on the home-page listing only.
-
-- **URL scheme:** article pages are `https://chinaxiv.org/abs/YYYYMM.NNNNN` (e.g.
-  `/abs/202606.00108`); discipline browse is
-  `/user/search.htm?field=domain&value=<n>`; news is `/newsdetail.htm?id=<n>` (S1) [WEB].
-- **API:** no public REST or OAI-PMH endpoint found. **[NOT-VERIFIED]**
-- **Bulk retrieval:** not offered as far as I could establish. **[NOT-VERIFIED]**
-
-## 9. Licensing and reuse
-
-**Not verified.** I did not locate a licence statement for ChinaXiv deposits. `/user/about.htm`
-returns HTTP 404 and the help page (§4 source) covers submission workflow rather than rights.
-Because article pages are unreachable (§8) I could not read a per-record licence field either.
-**[NOT-VERIFIED]** — do not assume CC BY, and do not assume redistribution is permitted.
-
-## 10. Caveats and controversies
-
-1. **The 4.1M headline is not ChinaXiv's size.** Native holdings are 47,362; the rest is a
-   harvested index of other servers (§3). This is the single most likely misquotation.
-2. **Article pages are unfetchable by script** — HTTP 403 for every user-agent tried, and the same
-   403 for bogus IDs, so status codes prove nothing (§8).
-3. **A political-scope criterion is applied and published** (§4). This is a real difference in
-   kind from arXiv/HAL screening, and readers citing ChinaXiv content should know the corpus is
-   shaped by it.
-4. **Withdrawal is close to impossible by design** (§4) — errors are superseded, not removed.
-5. **Computing and electronics coverage is thin**: 2,052 CS and 40 electronics records (§2).
-6. **Licensing is undetermined** (§9).
-7. **Relationship to Chinese national open-access policy: not verified.** ChinaXiv self-describes
-   as national-level infrastructure under CAS (S2), and its help text references a CAS notice,
-   *"中国科学院科技论文预发布平台（ChinaXiv）关于规范开展预印本学术交流的几点说明"* (S1) [WEB],
-   which I did not retrieve. I found **no** evidence of a national deposit mandate.
-   **[NOT-VERIFIED]**
-8. **Partnerships are advertised but unverified in substance.** The home page announces a pilot
-   with **Taylor & Francis / F1000** for open peer review and publishing, and a
-   **SMBU China–Russia** platform accepting Chinese, English and Russian (S1, S2) [WEB] [DOC].
-   Existence of the announcements is verified; their operation is not.
-
-## 11. Sources
-
-- **S1** — ChinaXiv home page, https://chinaxiv.org/home.htm · retrieved **2026-09-01**
-  (HTTP 200, 104,948 B, **default curl UA**, UTF-8). Supports: all §3 headline counters (verbatim
-  string quoted), the full §2 discipline table, §6 example titles and dates, the
-  ChinaXiv-Global/`eartharxiv_`/`psyarxiv_` composite IDs, the 韬（τ）定律 activity items, the
-  Taylor & Francis/F1000 announcement, and the §8 URL scheme. Local copy of the fetched body
-  retained at
-  `doc/hardware/scratch/preprint-repositories/regional/body_chinaxiv_home__default-curl.html`.
-- **S2** — ChinaXiv help / user guide, https://chinaxiv.org/user/help.htm · retrieved
-  **2026-09-01** (HTTP 200, 64,223 B, default curl UA). Supports: 2016 founding and CAS National
-  Science Library operatorship, the "国家级预印本交流基础设施" self-description, the 2022 "2.0"
-  release with ChinaXiv-Global/CSTR/SciEngine/ScienceDB/CSCD, the §4 moderation text (§3.8), the
-  §4.2 rejection grounds, the political-and-academic-problems criterion, the research-identity
-  credentials provision, temporary-vs-formal ChinaXivID, and the non-withdrawal policy.
-- **S3** — Live HTTP probes of `chinaxiv.org` and `global.chinaxiv.org` · **2026-09-01**. The §8
-  access table and negative controls. UA ladder per `AGENTS.md`: default curl → Chrome 131 →
-  WhatsApp/2.23.20.0 → ChatGPT-User/1.0 → ClaudeBot/1.0. Probe script and raw results in
-  `doc/hardware/scratch/preprint-repositories/regional/`.
-
-### Retrieval / crawler note
-
-**chinaxiv.org — default curl UA works for site pages; nothing works for article pages.**
-Home page and `/user/help.htm` return HTTP 200 to plain `curl` with no UA header, from outside
-China, with no geoblock or interstitial. But `/abs/*` returns **HTTP 403** with the page title
-**系统正在维护中** under *all five* user-agents in the standard ladder (default, Chrome 131,
-WhatsApp, ChatGPT-User, ClaudeBot). Because a deliberately bogus `/abs/999999.99999` returns the
-**same** 403, the status code cannot be used to test record existence. A bogus `.htm` path by
-contrast returns a normal HTTP 404 (您访问的页面不存在), confirming the 403 is specific to the
-`/abs/` route rather than a site-wide block. `global.chinaxiv.org` returns 200 but is a
-client-rendered shell (2,027 B) and yields no content to a non-JS client.
diff --git a/research/preprint-repositories/closed-and-defunct-servers.md b/research/preprint-repositories/closed-and-defunct-servers.md
deleted file mode 100644
index 7ca8870..0000000
--- a/research/preprint-repositories/closed-and-defunct-servers.md
+++ /dev/null
@@ -1,333 +0,0 @@
-# Closed, frozen and defunct preprint servers — cross-cutting record
-
-- **Compiled:** 2026-09-01 · **All reachability, TLS and count probes run:** 2026-09-01 /
-  2026-09-02 UTC
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Why this file exists.** Everything else in this directory documents a *living* service.
-> This documents the dead ones, because **durability is the property this knowledge base
-> actually cares about**. A preprint server is a promise that a document will still be
-> there in ten years. This record measures how often that promise is kept, exactly how it
-> fails, and what a citing author should do about it.
-
-## 1. The dead/alive table
-
-Every row was probed on **2026-09-02** using the `AGENTS.md` UA ladder (default `curl` →
-Chrome 131 → WhatsApp/2.23.20.0 → ChatGPT-User/1.0 → ClaudeBot/1.0). "Retrievable **today**"
-means *I downloaded a record, and where possible a full-text file, during this pass*.
-
-| Server | Span | Operator | What happened | Retrievable today? | Where |
-|---|---|---|---|---|---|
-| **Nature Precedings** | 2007–2012 | Nature Publishing Group | Publisher discontinued it. Original host **`precedings.nature.com` refuses TCP connections** | **YES — fully, incl. full text** | `nature.com/npre`; DOIs `10.1038/npre.*` resolve HTTP 200; `npre.2012.7141.1.pdf` downloaded as a valid **5-page, 177,957-byte PDF** [API] |
-| **PeerJ Preprints** | 2013–2019 | PeerJ | Publisher stopped accepting new preprints **30 Sep 2019** (S1) | **YES via DOI — but bot-blocked** | `doi.org/10.7287/peerj.preprints.27311v1` → HTTP **302** → `peerj.com/preprints/27311v1`. Every direct `peerj.com` fetch returned **403 on all five UAs**. Prefix `10.7287` holds **65,760** registered works [API] |
-| **CogPrints** | 1997–2017 | University of Southampton | Founder (Stevan Harnad) retired; service retired with him. **`https://cogprints.org` fails TLS**; `http://` redirects to a Southampton web archive | **YES — static mirror, full text works** | `web-archive.southampton.ac.uk/cogprints.org/`. Record 1 (Shizgal 1997) PDF downloaded: **174,167 bytes, 6 pages, PDF 1.2** [API] |
-| **INArxiv** | 2017–2020 | Center for Open Science | Closed 2020-10-07; successor `rinarxiv.lipi.go.id` **never had a valid certificate** (`CN=linux`) | **YES — 15,987 preprints** | OSF API. See [regional-and-national-servers.md](regional-and-national-servers.md) |
-| **LawArXiv** | 2017–2020 | Center for Open Science | Closed; superseded by **Law Archive** (1,664 records). **`lawarxiv.org` lapsed to a domain-parking stub (114 bytes → `/lander`)** | **YES — 165 preprints** | OSF API. See [social-sciences-and-humanities.md](social-sciences-and-humanities.md#7-lawarxiv--law-archive) |
-| **MarXiv** | 2017–2020 | Center for Open Science | Closed. **`marxiv.org` refuses TCP on 443** | **YES — 454 preprints** | OSF API. See [natural-sciences-and-niche-servers.md](natural-sciences-and-niche-servers.md#7-marxiv) |
-| **Frenxiv** | 2018–2022 | Center for Open Science | Closed on OSF. Separate **`frenxiv.org` still renders but is frozen at Oct 2020** | **YES — 128 preprints on OSF**; `frenxiv.org` count not verified | OSF API + zombie site. See [natural-sciences-and-niche-servers.md](natural-sciences-and-niche-servers.md#13-frenxiv) |
-| **mp_arc** | **Jul 1991 – Dec 2023** | UT Austin | Closed deliberately, with a published preservation promise | **YES — best-preserved dead archive measured.** 1991 PostScript and 2023 PDF both downloaded | `web.ma.utexas.edu/mp_arc/`, **6,152 records**. See [natural-sciences-and-niche-servers.md](natural-sciences-and-niche-servers.md#12-mp_arc) |
-| **AAS Open Research** | 2018–? | African Academy of Sciences + F1000 | **Rebranded, not killed** — `aasopenresearch.org` **redirects (HTTP 200) to `openresearchafrica.org`** | **YES — redirect works** | `openresearchafrica.org` (55,677 B) [WEB]. Record count **[NOT-VERIFIED]** |
-| **NutriXiv** | 2018–? | Center for Open Science | Closed. **`nutrixiv.org` is DNS NXDOMAIN** on all five UAs | **YES — 85 preprints** | OSF API |
-| **MindRxiv** | 2018–? | COS + Mind & Life Institute | Closed. Vanity domain **still redirects correctly** — a clean shutdown | **YES — 288 preprints** | OSF API |
-| **SportRxiv (OSF instance)** | 2017–**2021-08-27** | Center for Open Science | **Migrated**, not closed — moved to self-hosted OPS at `sportrxiv.org` | **YES — 377 legacy + 761 current** | OSF API + OAI-PMH |
-| **EarthArXiv (OSF instance)** | 2017–? | Center for Open Science | **Migrated** to CDL/Janeway; DOIs redirect | **YES — 1,649 legacy + 7,525 current** | OSF API + `eartharxiv.org` |
-| **EcoEvoRxiv (OSF instance)** | 2018–? | Center for Open Science | **Migrated** to CDL/Janeway | **YES — 909 legacy + 3,604 current** | OSF API + `ecoevorxiv.org` |
-| **AfricArXiv (OSF instance)** | 2018–? | Center for Open Science | Frozen; designated successor **`africarxiv.ubuntunet.net` certificate expired 2026-07-25** | **YES — 479 preprints** | OSF API. See [regional-and-national-servers.md](regional-and-national-servers.md) |
-| **Arabixiv**, **IndiaRxiv**, **AgriXiv**, **LISSA**, **Thesis Commons** | various | Center for Open Science | Frozen (`allow_submissions: false`) but retained | **YES — 298 / 121 / 397 / 335 / 2,866** | OSF API [API] |
-| **Rutgers Optimality Archive** | 1993–**2022** (deposits) | Rutgers SAS | Ingest stopped; **site still maintained** (index `Last-Modified` 2024-10-17) | **YES — 20-page PDF downloaded; complete XLSX manifest of ~1,463 rows** | `roa.rutgers.edu`. See [social-sciences-and-humanities.md](social-sciences-and-humanities.md#16-rutgers-optimality-archive-roa) |
-| **Eyexiv** | 2022–? | Intl. Virtual Ophthalmic Research Center (S2) | **Never resolved for me.** `.org`/`.com`/`.net`/`.io` all DNS NXDOMAIN; **not an OSF provider** | **NO — nothing found** | **[NOT-VERIFIED]** — the only genuinely lost server in this table |
-
-### The headline number
-
-**Of the 18 closed, frozen, migrated or rebranded services in this table, exactly one —
-Eyexiv — has no retrievable content that I could find.** Seventeen out of eighteen still
-serve their corpus in 2026, several of them a decade or more after shutdown.
-
-**Preprint servers do not lose data. They lose front doors.**
-
-## 2. Failure modes
-
-Six distinct mechanisms, all observed directly in this pass. They are ordered by how
-*deceptive* they are, not by how common.
-
-### 2.1 Publisher strategy change
-
-Nature Precedings and PeerJ Preprints both died because a commercial publisher decided
-preprints no longer fitted the business. Neither deleted anything: NPG kept Precedings at
-`nature.com/npre` with working DOIs and PDFs fourteen years on; PeerJ kept its preprint DOIs
-resolving seven years on.
-
-**But note the asymmetry.** NPG killed the *hostname* `precedings.nature.com` — it now
-refuses TCP connections — while retaining the content under the main brand. Every 2007–2012
-citation that used the hostname is broken; every citation that used the DOI works. This is
-the whole argument for DOIs in a single example.
-
-### 2.2 Founder retirement / single-maintainer dependency
-
-**CogPrints** is the canonical case: an EPrints archive at Southampton covering
-*"Psychology, Neuroscience, Linguistics, **Computer Science** (e.g. artificial intelligence,
-robotics, vision, learning, speech, neural networks), Philosophy…"* (its own front page,
-still served) [DOC]. It ran 1997–2017 and stopped when its founder did.
-
-What Southampton did next is the model: they froze it into a **static mirror** at
-`web-archive.southampton.ac.uk/cogprints.org/`. The metadata pages, abstracts and full-text
-files survive — I downloaded record 1's PDF. What did *not* survive is everything dynamic:
-search is a dead link, and `view/year/` now returns an **Apache directory index** of
-year HTML files rather than a browse interface [WEB].
-
-**The lesson for anyone freezing a repository: flattening to static preserves the
-documents and destroys the finding aids.** Budget for that. Deep links keep working; the
-ability to *discover* what is there does not.
-
-The same dependency exists right now, unmitigated, at **LingBuzz** (one person, no DOIs, no
-dark archive) and to a lesser degree at **RoA**.
-
-### 2.3 Platform migration breaking URLs — and how to do it right
-
-Migration is now the most common life-cycle event, and it is the one that is **usually done
-well**. EarthArXiv, EcoEvoRxiv and SportRxiv all moved off OSF; all three left the old
-provider record in place with an explanatory notice, kept the legacy records readable, and
-either redirected DOIs or ran the platforms in overlap. EarthArXiv's OSF description states
-it outright: *"All article DOIs will redirect to CDL"* (S3) [DOC]. SportRxiv's names the
-exact cutover date, **2021-08-27**, and its new OAI `earliestDatestamp` is 2021-08-12 — a
-deliberate two-week overlap (S3, S4) [DOC] [API].
-
-Contrast **AAS Open Research → Open Research Africa**, where the redirect works but nothing
-at the destination explains the rename to a reader arriving from a 2019 citation.
-
-### 2.4 Domain lapse, parking, and hijack — the dangerous one
-
-This is where content is *not* lost but readers are actively misled. All observed
-2026-09-02 [WEB]:
-
-| Domain | What it serves now |
-|---|---|
-| `lawarxiv.org` | **114-byte parking stub**: `window.location.href="/lander"` |
-| `mediarxiv.org` | **redirects to `afterdispatch.com`**, an unrelated site (the live archive is at `mediarxiv.**com**`) |
-| `bodoarxiv.org` | **"Mostbet Bangladesh — Online Casino & Sports Betting"** |
-| `nutrixiv.org` | DNS NXDOMAIN |
-| `hprints.org` | DNS NXDOMAIN (live archive is `hprints.hal.science`) |
-| `marxiv.org` | TCP connection refused |
-
-**And the operators still point at them.** BodoArXiv's live OSF description, served by the
-Center for Open Science on the day of this probe, says *"Visit BodoArXiv.org to learn
-more"* (S3) [DOC]. It is now a gambling site. **A repository's own outbound link is not
-evidence that the destination is still theirs.**
-
-### 2.5 TLS certificate state — refining the abandonment signal
-
-A sibling agent working on the regional servers reported that **expired TLS certificates are
-a reliable abandonment signal**. I verified that with `openssl s_client` and it holds — but
-the finding needs tightening in *both* directions.
-
-**Verified expired / never-valid (all 2026-09-02, S5) [API]:**
-
-| Host | Certificate | Diagnosis |
-|---|---|---|
-| `africarxiv.ubuntunet.net` | `CN=africarxiv.ubuntunet.net`, notAfter **2026-07-25** | **Expired 39 days ago.** AfricArXiv's designated successor |
-| `latarxiv.org` | `CN=latarxiv.org`, notAfter **2026-08-20 19:26:19** | **Expired 12 days ago** — confirms the sibling's finding to the second |
-| `rinarxiv.lipi.go.id` | **`CN=linux`, SAN `DNS:linux`**, valid 2023-07-31 → 2033-07-28 | **Not expired — never configured.** A self-signed default cert from the OS install, unnoticed for three years. INArxiv's designated successor |
-| `cogprints.org` | serves `CN=web-archive.southampton.ac.uk`, **freshly renewed**, valid to 2026-10-17 | **A healthy certificate that breaks the old front door.** The archive host is well maintained; it just never claimed the legacy hostname, so `https://cogprints.org` fails and only `http://` works |
-
-**Now the counter-evidence, which is the more important half.** I pulled certificates for
-every dead-or-zombie domain in §2.4 and they are **all fine**:
-
-| Host | Certificate valid | Actual state |
-|---|---|---|
-| `bodoarxiv.org` | 2026-08-20 → 2026-11-18 | **casino site** |
-| `lawarxiv.org` | 2026-08-30 → 2027-03-16 | **domain-parking stub** |
-| `mediarxiv.org` | 2026-07-29 → 2026-10-27 | **redirects to a stranger's site** |
-| `frenxiv.org` | 2026-07-25 → 2026-10-23 | **frozen since October 2020** |
-
-> **Refined rule.** *An expired or never-issued certificate is a high-precision signal of
-> abandonment — but a valid certificate is worth nothing as evidence of liveness.* Domain
-> parking services, squatters and hosting platforms all run automated ACME issuance.
-> `frenxiv.org` has renewed its certificate every 90 days without interruption for six years
-> while serving a page frozen in October 2020.
-
-**Corollary, and this one is genuinely counter-intuitive:** the presence of automated
-certificate renewal proves only that *something* is automated, and the absence of it proves
-a human stopped watching. In this dataset, **TLS automation outlived editorial staffing in
-every case where the two diverged.**
-
-### 2.6 The zombie — a rendering front page with no pulse
-
-`frenxiv.org` is the most deceptive artefact found in this whole survey: HTTP 200, 44,186
-bytes, title *"Frenxiv Papers"*, working subject browse, named steering committee including
-Björn Brembs and Sophien Kamoun. It looks completely alive. The tells:
-
-- a stuck banner: *"Notice: The site will undergo maintenance between **Oct 28, 2020**
-  9:19 AM and Oct 28, 2020 9:19 AM (+0000 UTC)"* — a **zero-length** maintenance window from
-  six years ago, still rendering;
-- a footer reading *"Copyright © **2011-2020**"*.
-
-**A site that refuses connections is safer than one that renders.** `marxiv.org` cannot
-mislead anyone.
-
-### 2.7 The two failure modes that did *not* appear
-
-Recorded because negative results matter:
-
-- **Grant expiry as a direct cause of data loss: not observed.** Several servers here were
-  grant-funded and several stopped, but in every case the content was absorbed by a larger
-  host (OSF, HAL, Wikimedia, a university web archive) rather than deleted.
-- **Deliberate deletion of a corpus: not observed at all.** Not once in 18 services.
-
-## 3. Synthesis — what actually determines survival
-
-The pattern across this file, [regional-and-national-servers.md](regional-and-national-servers.md),
-[social-sciences-and-humanities.md](social-sciences-and-humanities.md) and
-[natural-sciences-and-niche-servers.md](natural-sciences-and-niche-servers.md) is
-consistent enough to state as a rule:
-
-> **Content survives in proportion to the size and institutional depth of the host it sits
-> on. Front doors fail in proportion to how bespoke they are.**
-
-Ranked by observed durability:
-
-1. **Large shared scholarly hosts — OSF, HAL, Zenodo, Wikimedia, `nature.com`.** Zero
-   observed losses. Content from services shut down in 2020 is still API-addressable in
-   2026. Twelve of the eighteen rows in §1 are alive because of this.
-2. **University-operated static file trees.** mp_arc (Apache at UT Austin, 1991 PostScript
-   still byte-identical and served — the gzip header still records a 1997-04-26 mtime),
-   RoA (Rutgers SAS), CogPrints (Southampton's web archive). Slightly worse than (1) in that
-   finding aids get lost, far better in that the *bytes* are untouched for decades.
-3. **Commercial-publisher platforms.** Fine until the publisher's strategy changes, then
-   fine anyway because publishers maintain DOI resolution — but you must have used the DOI.
-   Increasingly guarded by Cloudflare, which breaks scripted access without breaking
-   citation (PeerJ, ESS Open Archive, Authorea, TechRxiv, ScienceOpen).
-4. **Self-hosted community successors.** The single worst category. Every failure in §2.4
-   and §2.5 is one of these. They are launched to escape platform dependence and then die of
-   the operational overhead that dependence was paying for.
-5. **One-person archives.** LingBuzz has outlived most of category 4, which is an argument
-   for simplicity — and has no succession plan at all, which is an argument against relying
-   on it.
-
-## 4. Practical guidance — citing defensibly from a small preprint server
-
-Do these in order. Each is cheap.
-
-1. **Cite the DOI, never the vanity URL.** This is the highest-value habit in the entire
-   file. `10.1038/npre.2012.7141.1` resolves; `precedings.nature.com` does not.
-   `10.7287/peerj.preprints.27311v1` resolves; `peerj.com` 403s every automated client. The
-   OSF DOI for a LawArXiv paper resolves; `lawarxiv.org` is a parking page. **Every broken
-   citation observed in this pass was a hostname; not one was a DOI.**
-2. **If there is no DOI, treat the item as ephemeral.** LingBuzz, RoA and mp_arc mint no
-   DOIs. Their content is currently well served, but a citation to `lingbuzz/009120` has no
-   redirection layer behind it at all.
-3. **Deposit-mirror to Zenodo.** For anything you author or depend on, put a copy in Zenodo:
-   it mints a DOI, is CERN-operated, and has an explicit long-term commitment. See
-   [zenodo.md](zenodo.md). Concept-DOI versioning means later revisions do not orphan the
-   citation.
-4. **Submit the URL to `https://web.archive.org/save/<url>` at the moment you cite it.**
-   Per [`AGENTS.md`](../../AGENTS.md) §9, this is free, unauthenticated and
-   rate-limited to a few per minute. This pass used the Wayback availability API to confirm
-   that `peerj.com/preprints/` had a capture from **2026-08-31** even though live retrieval
-   returned 403 on all five user-agents (S6) [API] — the archive was the *only* way to see
-   what the page says. **Do this especially for anything on a self-hosted community
-   successor**, which §3 identifies as the most failure-prone category.
-5. **Prefer servers with a named dark archive.** Portico and CLOCKSS/LOCKSS agreements are
-   the only *contractual* preservation guarantees in this landscape; everything else is a
-   promise by an institution. Of the servers in this record I found **no** explicit dark-archive
-   statement for mp_arc, RoA, LingBuzz or any OSF-hosted provider — COS's own language is
-   *"as part of COS's ongoing commitment to Open Science"* (S3) [DOC], which is a commitment,
-   not a contract. **[NOT-VERIFIED]:** whether OSF preprints are covered by any third-party
-   dark archive. Treat this as an open question, not as a gap.
-6. **Sanity-check liveness properly, because the obvious signals lie.** In this dataset:
-   HTTP 200 did not mean alive (OSF's 4,207-byte SPA shell for non-existent providers;
-   mp_arc's 174-byte "Found no abstract" at status 200); a valid TLS certificate did not
-   mean alive (§2.5); and a professionally rendering front page did not mean alive (§2.6).
-   What *did* work: **an API or OAI-PMH count**, and **the date of the newest item**.
-7. **When the HTML is defended, try the machine interface.** Repeatedly true here: hprints'
-   web front is behind an Anubis proof-of-work wall while the HAL Solr API answers a bare
-   `curl`; ESS Open Archive 403s every user-agent while Crossref serves its whole corpus;
-   CrimRxiv 403s while its DOIs resolve. Bot-blocking is applied to browsers' endpoints,
-   rarely to APIs.
-
-### How this ties to this repository's own practice
-
-The habits above are the same ones `doc/hardware/` already applies to datasheets, and the
-correspondence is exact:
-
-- **Local artifact copies with SHA-256 checksums**, listed in
-  [`artifact-manifest.md`](../../artifact-manifest.md) — the repository does not rely on a
-  vendor URL staying up, and it should not rely on a preprint server staying up either. If a
-  preprint is load-bearing for a hardware claim, **keep the PDF and hash it**, exactly as
-  the ESP32-P4 and WCH datasheet passes did.
-- **`ARCHIVED-…md` reacquisition records** — where a large file is archived out of the tree,
-  the repository keeps a record with the verified download URL and checksum. The equivalent
-  for a preprint is: DOI, retrieval date, byte size, page count.
-- **Negative controls on every URL pattern.** The repository already documents that WCH's
-  `downloads/<PART>DS1_PDF.html` returns *"an identical 4,305-byte SPA shell for every path,
-  existing or not"*, and that SquareLine's CDN *"returns HTTP 206 for non-existent paths"*.
-  **OSF's 4,207-byte shell is the same phenomenon in the scholarly domain**, and this pass
-  caught it live at `osf.io/preprints/eyexiv/` — a provider that does not exist.
-- **Dated retrieval, always.** Every probe in this file carries 2026-09-01 or 2026-09-02.
-  Given §2.5, a liveness claim without a date is worthless within about 90 days.
-
-## 5. Sources
-
-- **S1** — Wikipedia, *List of preprint repositories*, and the PeerJ blog post it cites
-  (*"PeerJ Preprints to stop accepting new preprints Sep 30th 2019"*).
-  `https://en.wikipedia.org/wiki/List_of_preprint_repositories` · retrieved 2026-09-02 ·
-  spans, operators and size buckets throughout §1. [COM]
-- **S2** — same page, Eyexiv row: *"The Eye Open Repository, Preprints founded by Dr. F.
-  Heidary … International Virtual Ophthalmic Research Center"*, `>100`, 2022 · retrieved
-  2026-09-02. [COM]
-- **S3** — OSF API. `https://api.osf.io/v2/preprint_providers/?page[size]=100`,
-  `https://api.osf.io/v2/preprint_providers/<slug>/` and
-  `https://api.osf.io/v2/preprints/?filter[provider]=<slug>&page[size]=1` · retrieved
-  2026-09-02 · all OSF counts, and verbatim closure/migration notices for LawArXiv, MarXiv,
-  NutriXiv, Frenxiv, MindRxiv, SportRxiv, EarthArXiv, EcoEvoRxiv, plus the BodoArXiv
-  description that links the hijacked domain. Negative control:
-  `filter[provider]=bogusprovider12345` → `total: 0`. [API] [DOC]
-- **S4** — SportRxiv OAI-PMH. `https://sportrxiv.org/index.php/server/oai?verb=Identify`
-  and `?verb=ListIdentifiers&metadataPrefix=oai_dc` (`completeListSize="761"`,
-  earliestDatestamp 2021-08-12) · retrieved 2026-09-02. [API]
-- **S5** — TLS certificate probes.
-  `openssl s_client -connect <host>:443 -servername <host> | openssl x509 -noout -subject
-  -dates -ext subjectAltName`, run 2026-09-02 against `cogprints.org`,
-  `africarxiv.ubuntunet.net`, `rinarxiv.lipi.go.id`, `latarxiv.org`, `marxiv.org`,
-  `lingbuzz.net`, `roa.rutgers.edu`, `bodoarxiv.org`, `lawarxiv.org`, `frenxiv.org`,
-  `mediarxiv.org`, `peerj.com`, `essopenarchive.org`. Supports every claim in §2.5. [API]
-- **S6** — Wayback availability API.
-  `http://archive.org/wayback/available?url=peerj.com/preprints/&timestamp=20260901` →
-  capture `20260831083405`; and `…?url=peerj.com/preprints/27311/` → capture
-  `20250324000250` · retrieved 2026-09-02. [API]
-- **S7** — Nature Precedings. `https://www.nature.com/npre` (title *"Nature Precedings"*;
-  *"Pre-publication research and preliminary findings for the Life Science community from
-  2007 until 2012"*; newest items dated 04 Apr 2012),
-  `https://www.nature.com/articles/npre.2012.7141.1`,
-  `https://www.nature.com/articles/npre.2012.7141.1.pdf` (200, 177,957 B, valid 5-page PDF),
-  `https://doi.org/10.1038/npre.2012.7141.1` (resolves 200) · retrieved 2026-09-02. [WEB] [API]
-- **S8** — CogPrints. `http://cogprints.org/` → redirects to
-  `https://web-archive.southampton.ac.uk/cogprints.org/` (front page with the CS/AI scope
-  statement), `…/cogprints.org/1/` (Shizgal 1997 record page),
-  `…/cogprints.org/1/4/cur_op_e-print_version.PDF` (200, 174,167 B, valid 6-page PDF 1.2),
-  `…/cogprints.org/view/year/` (Apache directory index — search and browse are gone) ·
-  retrieved 2026-09-02. [WEB] [API]
-- **S9** — Crossref REST API. `https://api.crossref.org/prefixes/10.7287` (owner: PeerJ)
-  and `/prefixes/10.7287/works?rows=0` (65,760 works),
-  `/works/10.7287/peerj.preprints.27311v1` · plus `https://doi.org/10.7287/peerj.preprints.27311v1`
-  → HTTP 302 to `peerj.com/preprints/27311v1` · retrieved 2026-09-02. [API]
-- **S10** — mp_arc. `https://web.ma.utexas.edu/mp_arc/` (the verbatim 1991–2023 statement
-  and preservation promise), `index-91.html`…`index-23.html` (6,152 records),
-  `mp_arc/c/91/91-1.ps.gz` (200, 120,018 B; gzip header mtime **1997-04-26**),
-  `mp_arc/c/23/23-1.pdf` (200, valid 6-page PDF), negative controls
-  `mp_arc-bin/mpa?yn=99-99999` (200 / 174 B "Found no abstract") and `index-77.html` (404) ·
-  retrieved 2026-09-02. Detail in
-  [natural-sciences-and-niche-servers.md](natural-sciences-and-niche-servers.md#12-mp_arc). [WEB] [DOC] [API]
-- **S11** — Reachability sweeps. Directory-wide
-  `doc/hardware/scratch/preprint-repositories/reachability-2026-09-01.txt` (2026-09-01) and
-  the UA-ladder log in `doc/hardware/scratch/preprint-repositories/humanities/` (2026-09-02)
-  · supports every 403 / NXDOMAIN / connection-refused / parking-stub / redirect claim in
-  §1 and §2.4, including the `frenxiv.org` banner and copyright text, the `bodoarxiv.org`
-  casino title, `mediarxiv.org` → `afterdispatch.com`, `lawarxiv.org` → `/lander`, and
-  `aasopenresearch.org` → `openresearchafrica.org`. [WEB]
-- **S12** — This repository's own archival practice, for §4:
-  [`doc/hardware/artifact-manifest.md`](../../artifact-manifest.md) (SHA-256 checksummed
-  local artifacts), [`doc/hardware/README.md`](../../README.md) change log (the
-  `ARCHIVED-…md` reacquisition-record pattern; the WCH 4,305-byte SPA shell and SquareLine
-  HTTP 206 negative controls), and [`AGENTS.md`](../../AGENTS.md) §9 (the
-  `web.archive.org/save` rule). [DOC]
diff --git a/research/preprint-repositories/cryptology-eprint-archive.md b/research/preprint-repositories/cryptology-eprint-archive.md
deleted file mode 100644
index 4f616ed..0000000
--- a/research/preprint-repositories/cryptology-eprint-archive.md
+++ /dev/null
@@ -1,622 +0,0 @@
-# Cryptology ePrint Archive — preprint repository record
-
-- **URL:** https://eprint.iacr.org/ · short-URL alias `https://ia.cr/YYYY/NNNN` (302 → canonical, S27)
-- **Operator:** International Association for Cryptologic Research (IACR), a non-profit incorporated
-  in Nevada, USA (S18). Run by a small volunteer editorial board — as of 2026-09-01: Joppe W. Bos,
-  Sofía Celi, Matthias J. Kannwischer (S1). **Funding:** IACR income is membership dues and
-  conference registration; the Treasurer "publishes the annual Financial Report of the IACR in the
-  first quarter of each calendar year" (S19) [DOC]. No ePrint-specific budget line was located
-  [NOT-VERIFIED].
-- **Discipline scope:** cryptology and related fields, as advertised — in practice also cache and
-  microarchitectural attacks, hardware side-channel and fault injection, distributed consensus,
-  blockchain, ORAM, MPC and formal protocol verification.
-- **Launched:** ePrint debuted **fall 1999** (S2). Its predecessor, the Theory of Cryptography
-  Library, was founded **1996** by Oded Goldreich at MIT and migrated in — which is why records
-  dated 1996–1999 exist (S2, S5). · **Status:** active (1999–2026)
-- **Compiled:** 2026-09-01 (retrievals 2026-09-01/02 UTC)
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Correction.** IACR was *not* founded in 1996. Wikipedia states IACR "was organized at the
-> initiative of David Chaum at the CRYPTO '82 conference" (S22) [COM]. 1996 is the founding year of
-> the *Theory of Cryptography Library*, ePrint's ancestor (S2) [DOC]. No founding year appears
-> anywhere on iacr.org itself — `iacr.org/about/`, `iacr.org/docs/` and the bylaws PDF were all
-> checked [NOT-VERIFIED].
-
-## 1. What it is
-
-ePrint is the field-wide preprint server for cryptography. It solves a discipline-specific problem:
-cryptography's results are frequently *destructive* — a break of a deployed or standards-track
-scheme — and a break that waits nine months for a conference cycle leaves systems exploitable in
-the interim. ePrint makes a cryptanalytic result public and timestamped within hours.
-
-Its self-description is modest: papers "did not undergo any refereeing process other than verifying
-that the work seems to be within the scope of cryptology and meets some minimal acceptance criteria
-and publishing conditions" (S1) [DOC]. IACR's publications page is blunter: "Papers published there
-undergo no scientific reviewing process. Some papers may be published there long before they appear
-in a peer-reviewed publication venue" (S20) [DOC].
-
-What makes ePrint unusual is its tight coupling to a society that also owns the field's venues. The
-IACR bylaws (approved 2025-12-20) enumerate General Conferences (Asiacrypt, Crypto, Eurocrypt), Area
-Conferences (CHES, FSE, PKC, TCC), Symposia (Real World Cryptography), and journals: *Journal of
-Cryptology*, *IACR Communications in Cryptology*, and Area Journals *ToSC* and *TCHES* (S19) [DOC] —
-the same eight events are listed on IACR's conferences index (S21) [WEB].
-ToSC and TCHES are diamond-open-access journal/conference hybrids that *are* FSE and CHES (S20)
-[DOC]. The same body owns preprint server, conferences and journals — and explicitly encourages
-posting to ePrint (S3) [DOC]. That removes the preprint-versus-venue friction seen elsewhere.
-
-## 2. Scope and subject taxonomy
-
-Exactly **seven** author-selected categories plus an uncategorised legacy bucket. Whole-archive
-totals from the `categoryData` variable on the statistics page (S4) [WEB], retrieved 2026-09-01:
-
-| Category | Form/feed code | Papers |
-|---|---|---:|
-| Cryptographic protocols | `PROTOCOLS` | 6,452 |
-| Public-key cryptography | `PUBLICKEY` | 5,011 |
-| Foundations | `FOUNDATIONS` | 3,205 |
-| Secret-key cryptography | `SECRETKEY` | 2,961 |
-| **Implementation** | `IMPLEMENTATION` | **2,417** |
-| Applications | `APPLICATIONS` | 2,122 |
-| Attacks and cryptanalysis | `ATTACKS` | 1,363 |
-| *(uncategorised)* | — | 4,021 |
-| **Total** | | **27,552** |
-
-Codes confirmed twice: as `<option>` values on the submission form (S12) [DOC] and as the
-`?category=NAME` selector for per-category RSS feeds (S9) [DOC]. For this knowledge base the
-load-bearing categories are **Implementation** (hardware, microcontroller, countermeasures, FPGA/ASIC)
-and **Attacks and cryptanalysis**. The taxonomy is coarse by design — there is no side-channel,
-fault-injection or lightweight-crypto code, so category filtering alone will not isolate embedded
-work; keyword search is required.
-
-## 3. Size and growth
-
-**27,552 papers archive-wide as of 2026-09-01/02**, confirmed by **five independent paths that agree
-exactly**: sum of `/byyear` HTML counts [WEB]; sum of the `byyear` JS array on `/stats` [WEB]; sum of
-the `byday` weekday array on `/stats` [WEB]; sum of `categoryData` on `/stats` [WEB]; and
-`count(<identifier>)` in the OAI-PMH `ListIdentifiers` dump [API] (S4, S5, S7).
-
-**Method.** `/byyear` publishes an explicit per-year count. I cross-checked *all 31 years* against an
-independent count derived from OAI-PMH `ListIdentifiers` (`metadataPrefix=oai_dc`; a single 3.34 MB
-response, no resumption token), parsing `YYYY` out of each `oai:eprint.iacr.org:YYYY/NNNN` identifier.
-**Zero mismatches.** "Max #" is the highest sequence number present that year; "Gap" is `max − count`,
-i.e. numbers allocated but never publicly resolvable (§4, §8).
-
-| Year | Papers | Max # | Gap | Year | Papers | Max # | Gap |
-|---|---:|---:|---:|---|---:|---:|---:|
-| 1996 | 16 | 16 | 0 | 2012 | 733 | 733 | 0 |
-| 1997 | 15 | 15 | 0 | 2013 | 881 | 882 | 1 |
-| 1998 | 26 | 26 | 0 | 2014 | 1,029 | 1,029 | 0 |
-| 1999 | 24 | 24 | 0 | 2015 | 1,255 | 1,257 | 2 |
-| 2000 | 69 | 69 | 0 | 2016 | 1,195 | 1,196 | 1 |
-| 2001 | 113 | 113 | 0 | 2017 | 1,262 | 1,262 | 0 |
-| 2002 | 195 | 195 | 0 | 2018 | 1,249 | 1,251 | 2 |
-| 2003 | 265 | 265 | 0 | 2019 | 1,498 | 1,499 | 1 |
-| 2004 | 375 | 377 | 2 | 2020 | 1,620 | 1,620 | 0 |
-| 2005 | 469 | 469 | 0 | 2021 | 1,705 | 1,705 | 0 |
-| 2006 | 485 | 486 | 1 | 2022 | 1,781 | 1,781 | 0 |
-| 2007 | 482 | 482 | 0 | 2023 | 1,971 | 1,973 | 2 |
-| 2008 | 545 | 545 | 0 | 2024 | 2,100 | 2,100 | 0 |
-| 2009 | 638 | 638 | 0 | 2025 | 2,337 | 2,340 | 3 |
-| 2010 | 660 | 661 | 1 | **2026** (partial) | **1,845** | 1,846 | 1 |
-| 2011 | 714 | 714 | 0 | **TOTAL** | **27,552** | — | **17** |
-
-Sources: S5, S4 [WEB]; S7 [API]. 2026 is partial — 1,845 by 2026-09-01, already above every year
-before 2023; straight-lining eight months gives ≈2,770 for the full year [INF].
-
-Every year except 2004 begins at sequence number 001; 2004 starts at 002 and its two gaps are
-`2004/001` and `2004/056` (S7) [API]. Shape of the curve: ~1,500 papers in the first five years,
-"more than doubled" by year ten, 10,000 passed in 2016, over 15,000 by end of year twenty (S2) [DOC]
-— my cumulative sums are consistent with all three milestones [INF].
-
-Other archive-wide statistics from `/stats` (S4) [WEB], computed by me from the raw histograms:
-
-- **Mean authors per paper 3.09**; 20.5% single-author; most-authored paper has 32 authors
-  (`authorData` sums to 27,552, so this covers the whole archive).
-- **Weekday deposits:** Tue 5,016 > Mon 4,986 > Wed 4,767 > Thu 4,413 > Fri 4,348 ≫ Sun 2,167 >
-  Sat 1,855. Weekends are ~15% of deposits — a professional, working-hours archive [INF].
-- **Version churn:** within the 19,672 records covered by `versionData`, 47.4% have exactly one
-  version and 52.6% have been revised at least once; 2,084 have ≥5 versions, 291 have ≥10, and one
-  paper has **125 versions**. ⚠️ `versionData` sums to 19,672, **not** 27,552 — it covers only ~71%
-  of the archive and the page does not document the subset basis. Do not quote 47.4% as
-  archive-wide [NOT-VERIFIED for the full archive].
-
-**Conflict check.** The English Wikipedia article on the Cryptology ePrint Archive publishes **no
-size figure at all** (full extract via the MediaWiki API, S23) [WEB]. Recorded as an absence — there
-is no Wikipedia-versus-operator conflict here, unlike arXiv.
-
-## 4. Screening and moderation — what gets in
-
-Not peer review, but not nothing. The gate is **editorial screening by the named editors** against
-four published criteria. Verbatim (S3) [DOC], submissions must be deemed by the editors to:
-(1) "address research in cryptology and related fields"; (2) "be clear, readable, and
-self-contained"; (3) "look somewhat new and interesting"; (4) "contain proofs or convincing
-arguments for any claims". Plus a hard formal rule: submissions "must not be anonymous and state
-title, author name(s), and a contact address or affiliation(s) on the first page" (S3) [DOC].
-
-The submission form additionally enforces machine-checkable constraints: UTF-8 (not TeX escapes or
-HTML entities) for names and abstracts, abstract ≥64 characters, keyword phrases ≤40 characters, PDF
-only, A4/Letter geometry, and a mandatory licence selection (S12) [DOC].
-
-Criteria 3 and 4 are genuine editorial judgement, which makes this *more* than arXiv-style scope
-screening — but the operators immediately disclaim what it means: **"If a paper is accepted, this
-does not mean that the editors have verified any claims or arguments. Authors are solely responsible
-for the content and the correctness of the published work."** (S3) [DOC].
-
-Editorial turnover is public (Sofía Celi joined 2024-12-10; Matthias J. Kannwischer joined
-2023-10-19 replacing Tancrède Lepoint) and `/about.html` lists every past editor since 2000 (S1, S2)
-[DOC]. **No rejection rate is published** — `/about.html`, `/operations.html`, `/stats` and
-`/news.html` all checked [NOT-VERIFIED].
-
-The 17 numbering gaps in §3 are the only observable trace of records allocated a number that never
-became public: 17 of 27,569 allocated numbers, **99.94% dense** [INF from API+WEB]. These are not
-rejections — rejected submissions never receive a number, since numbering is assigned at acceptance
-[INF].
-
-## 5. Reliability — what you can and cannot trust
-
-### What a deposit guarantees
-
-(a) A **priority timestamp** to the second, publicly visible as `YYYYMMDD:HHMMSS` in the version
-archive (S14) [WEB]; (b) **permanence** of the identifier; (c) **named, non-anonymous authorship with
-a contact address** (S3) [DOC]; (d) that a human editor thought it was cryptology and looked
-plausible. It guarantees **nothing about correctness**, and the operators say so (S3, S20) [DOC].
-
-It does **not** give you a DOI. ePrint mints none; the `doi` field in the recommended BibTeX is for
-the *externally published* version, and the citation page tells authors to "cite the original work if
-it is published elsewhere" and to "use the DOI for the paper to identify it uniquely" (S13) [DOC].
-Paper pages carry no ePrint DOI — verified on 2017/1066, whose metadata block lists only
-"Short URL https://ia.cr/2017/1066" (S28) [WEB].
-
-### Why cryptography treats ePrint as authoritative for priority
-
-1. **The venue owner endorses it.** IACR's copyright policy "permits and encourages that authors
-   submit their work to the Cryptology ePrint Archive"; all author versions of IACR proceedings
-   papers from 2013 onward may be posted (S3) [DOC].
-2. **Anonymous-submission conflicts resolve in ePrint's favour.** IACR's position, traced to a Board
-   decision of **1999-05-02 in Prague**, is that posting to ePrint while under anonymous review "is
-   permitted and that authors should not be penalized by conference program committees for having
-   made such a posting" (S3) [DOC]. This single policy is why ePrint-first is the field default.
-3. **The ePrint version is usually the *better* version.** Conference page limits push proofs into
-   appendices Springer does not print, and IACR concedes ePrint "contains different versions of
-   papers published elsewhere (including corrected or full versions containing details not found)"
-   (S20) [DOC]. My sample bears this out — 2010/441 ("Full version of a paper published in the
-   proceedings of CHES 2010"), 2012/300 ("an extended version of the paper … at CHES 2012") and
-   2013/279 ("the full version of the IEEE Symposium on Security & Privacy 2013 paper") (S28) [WEB].
-   **For these the ePrint report is canonical and the proceedings version is the abridgement.**
-
-### Measured eventual-publication rate — derived here
-
-No scientometric study of ePrint was located. I queried the Crossref API twice (`query.bibliographic`
-= "Cryptology ePrint Archive scientometric analysis", and a publication-rate variant); all hits
-concerned unrelated "eprint" archives (Bioline, law schools, The Lancet) (S30) [NOT-VERIFIED for
-[LIT]]. So I measured it.
-
-**Method:** systematic sample of the 2017 cohort (1,262 papers — old enough that outcomes have
-settled). Every 21st sequence number from 001, n = 60, fetching each paper page and parsing the
-"Publication info" field, throttled to ~3.4 s/request.
-
-| Publication info state | n | % |
-|---|---:|---:|
-| `Published by` / `revision of an IACR publication` | 16 | 26.7% |
-| `Published elsewhere` | 21 | 35.0% |
-| `Preprint…` (no publication recorded) | 23 | 38.3% |
-| **Records a subsequent publication** | **37 / 60** | **61.7%** |
-
-95% Wilson score interval **[49.0%, 72.9%]** [INF from a [WEB] sample].
-
-⚠️ **A lower bound, not an estimate.** The publication-info field is *self-reported* and must be
-updated by the author using their retained submission password (S3) [DOC]; authors who publish and
-never return are counted as "Preprint". Read it as "at least three in five 2017 ePrint reports are
-known to have been published elsewhere."
-
-### The real failure mode: unreviewed breaks and unreviewed schemes
-
-- **Attacks appear here first, unreviewed, and are frequently correct** — but a report titled
-  "Cryptanalysis of X" carries *no* editorial verification that the attack works.
-- **"Provably secure" is a claim about a model, not an implementation.** Criterion 4 requires "proofs
-  or convincing arguments", not correct ones. Broken proofs of broken schemes get posted, cited and
-  sometimes deployed before anyone checks.
-- **Post-quantum submissions are the highest-risk zone.** The NIST PQC process pushed a large volume
-  of structurally unfamiliar schemes onto ePrint against a standards deadline. Several §7 landmarks
-  are breaks of exactly such schemes.
-
-### Case study: the SIKE / SIDH break (verified end to end)
-
-| When | What | Evidence |
-|---|---|---|
-| **2022-07-05** | NIST announces four algorithms to be standardized plus four **Round 4** candidates; SIKE is Round 4 | S24 [WEB] |
-| **2022-07-30 07:20:07 UTC** | Castryck & Decru (KU Leuven) post ePrint **2022/975**, "An efficient key recovery attack on SIDH" — v1 | S25 [WEB] |
-| 2022-07-30 14:32:35 UTC | v2, the *same day* | S25 [WEB] |
-| 2022-08-05 · 2023-02-22 · 2023-05-15 | v3 · v4 · v5 | S25 [WEB] |
-| — | Record now reads "Published by the IACR in EUROCRYPT 2023" | S28 [WEB] |
-
-The abstract states the attack "breaks SIKEp434, which aims at security level 1, in about ten minutes
-on a single core", and names SIKE as the instantiation that "recently advanced to the fourth round of
-NIST's standardization effort" (S25) [WEB]. **25 days elapsed between NIST advancing SIKE and an
-unreviewed ePrint report destroying it**; formal peer-reviewed publication followed ~9 months later.
-Any process that waited for peer review would have been nine months wrong.
-
-### How to sanity-check an individual ePrint report
-
-1. **Read "Publication info".** `Published by the IACR in <venue>` or `A minor/major revision of an
-   IACR publication in <venue>` means it passed IACR peer review; `Preprint.` means it has not —
-   38% of my 2017 sample (S28) [WEB].
-2. **Read "History"** — `received` date plus `last of N revisions`. A 2019 report still at v1 in 2026
-   is either perfect or abandoned; v14 (Bulletproofs) or v44 (PLONK) means actively maintained.
-3. **Open `/archive/versions/YYYY/NNNN`.** Bulletproofs v1 (`20171110:151138`) is titled *"…Efficient
-   Range Proofs for Confidential Transactions"*; the current version is *"…Short Proofs for
-   Confidential Transactions and More"* (S14, S15) [WEB]. **The title changed** — citing by remembered
-   title may cite a version that no longer exists.
-4. **Read the `Note:` field**, where corrections live. Bulletproofs' current note: *"This version
-   fixes an earlier mistake in the Fiat-Shamir section (Section 4.4) reported by TrailOfBits."*
-   (S28) [WEB] — a real soundness bug in a widely deployed proof system, disclosed only in free text.
-5. **Check authors and affiliations.** Non-anonymity is mandatory (S3) [DOC]; newer records carry
-   per-author institutions (2022/975 shows "KU Leuven" for both) [WEB].
-6. **Check whether anything on ePrint attacks it** — `title:` search the scheme name. The archive is
-   its own adversarial review layer.
-7. **Prefer the ePrint text for technical detail, cite the proceedings DOI for the record** — exactly
-   what S13 instructs.
-
-## 6. What you actually find there — examples
-
-Concrete documents a systems or electronics engineer would recognise, all verified to resolve
-(details and links in §7): the **reference specs of algorithms now in your TLS stack and your MCU**
-(CRYSTALS-Kyber 2017/634, CRYSTALS-Dilithium 2017/633 — NIST's ML-KEM and ML-DSA); the **benchmark
-suite embedded PQC is measured against** (`pqm4` 2019/844); **working microcontroller implementation
-papers** (2026/235, Keccak/Kyber/Dilithium on the MSP430, TCHES 2026); **cache and microarchitectural
-attacks** (Flush+Reload 2013/448, CacheBleed 2016/224); **physical key extraction from consumer
-devices** (2016/230, ECDSA from phones by non-intrusive EM/power measurement); **hardware RNG
-certification guidance** (2024/301, released CC0); **secure-boot engineering** (2022/1198 and
-2022/602); and **withdrawn records left standing as historical evidence** (2017/1065, 2019/1410 —
-§10).
-
-## 7. Landmark papers (software · distributed systems · databases · electronics · security)
-
-**41 entries, every one verified by fetching its ePrint page on 2026-09-01/02** and confirming title,
-authors, receipt date, version count, licence and publication-info string (S28) [WEB]. "v" = total
-versions. `n/a (companion)` means the record itself declares it the full/extended version of a paper
-at the named venue, so it is a companion rather than a precedence claim.
-
-### 7.1 Zero-knowledge proofs, verifiable computation, privacy
-
-| Paper | ID | Recv | v | Publication info (as recorded) | Preprint first? |
-|---|---|---|---:|---|---|
-| Pinocchio: Nearly Practical Verifiable Computation | [2013/279](https://eprint.iacr.org/2013/279) | 2013-05-16 | 1 | full version of IEEE S&P 2013 | n/a (companion) |
-| Path ORAM: An Extremely Simple Oblivious RAM Protocol | [2013/280](https://eprint.iacr.org/2013/280) | 2013-05-16 | 2 | Published elsewhere, CCS 2013 | yes |
-| Zerocash: Decentralized Anonymous Payments from Bitcoin | [2014/349](https://eprint.iacr.org/2014/349) | 2014-05-19 | 1 | Published elsewhere, IEEE S&P 2014 | n/a (companion) |
-| On the Size of Pairing-based Non-interactive Arguments (**Groth16**) | [2016/260](https://eprint.iacr.org/2016/260) | 2016-03-08 | 2 | IACR publication, EUROCRYPT 2016 | yes |
-| Bulletproofs: Short Proofs for Confidential Transactions and More | [2017/1066](https://eprint.iacr.org/2017/1066) | 2017-11-10 | 14 | Published elsewhere, IEEE S&P 2018 | **yes** |
-| Scalable, transparent, and post-quantum secure computational integrity (**STARK**) | [2018/046](https://eprint.iacr.org/2018/046) | 2018-01-10 | 4 | Preprint. MINOR revision. | **yes — never formally published** |
-| **PLONK** | [2019/953](https://eprint.iacr.org/2019/953) | 2019-08-21 | **44** | Preprint. | **yes — never formally published** |
-
-### 7.2 Fully homomorphic encryption
-
-| Paper | ID | Recv | v | Publication info | Preprint first? |
-|---|---|---|---:|---|---|
-| Fully Homomorphic Encryption without Bootstrapping (**BGV**) | [2011/277](https://eprint.iacr.org/2011/277) | 2011-05-28 | 3 | "Published elsewhere. Unknown where it was published" | **yes** |
-| Somewhat Practical Fully Homomorphic Encryption (**BFV**) | [2012/144](https://eprint.iacr.org/2012/144) | 2012-03-22 | 1 | "Published elsewhere. Unknown where it was published" | **yes** |
-| Homomorphic Encryption for Arithmetic of Approximate Numbers (**CKKS**) | [2016/421](https://eprint.iacr.org/2016/421) | 2016-05-01 | 5 | IACR publication, ASIACRYPT 2017 | **yes (~18 months)** |
-
-BGV and BFV — two of the three FHE schemes the whole homomorphic-encryption industry implements —
-have publication metadata reading literally "Unknown where it was published". The ePrint report is in
-practice the citable artifact [INF].
-
-### 7.3 Post-quantum cryptography and its breaks
-
-| Paper | ID | Recv | v | Publication info | Preprint first? |
-|---|---|---|---:|---|---|
-| Towards quantum-resistant cryptosystems from supersingular elliptic curve isogenies (**SIDH**) | [2011/506](https://eprint.iacr.org/2011/506) | 2011-09-18 | 2 | Published elsewhere, PQCrypto 2011 | n/a (companion) |
-| SPHINCS: practical stateless hash-based signatures | [2014/795](https://eprint.iacr.org/2014/795) | 2014-10-10 | 2 | IACR publication, EUROCRYPT 2015 | **yes** |
-| Post-quantum key exchange — a new hope (**NewHope**) | [2015/1092](https://eprint.iacr.org/2015/1092) | 2015-11-10 | 9 | Published elsewhere, USENIX Security 2016 | **yes** |
-| CRYSTALS — Dilithium: Digital Signatures from Module Lattices (**→ ML-DSA**) | [2017/633](https://eprint.iacr.org/2017/633) | 2017-06-27 | 2 | IACR publication, **TCHES 2018** | **yes** |
-| CRYSTALS — Kyber: a CCA-secure module-lattice-based KEM (**→ ML-KEM**) | [2017/634](https://eprint.iacr.org/2017/634) | 2017-06-27 | 2 | Published elsewhere, EuroS&P 2018 | **yes** |
-| **An efficient key recovery attack on SIDH** (Castryck–Decru; killed SIKE) | [2022/975](https://eprint.iacr.org/2022/975) | 2022-07-30 | 4 | Published by the IACR in EUROCRYPT 2023 | **yes — ~9 months** |
-
-### 7.4 Distributed systems, consensus, blockchain
-
-| Paper | ID | Recv | v | Publication info | Preprint first? |
-|---|---|---|---:|---|---|
-| The Bitcoin Backbone Protocol: Analysis and Applications | [2014/765](https://eprint.iacr.org/2014/765) | 2014-09-30 | **17** | IACR publication, EUROCRYPT 2015 | **yes** |
-| Ouroboros: A Provably Secure Proof-of-Stake Blockchain Protocol | [2016/889](https://eprint.iacr.org/2016/889) | 2016-09-14 | 8 | IACR publication, CRYPTO 2017 | **yes (~10 months)** |
-| ALGORAND AGREEMENT: Super Fast and Partition Resilient Byzantine Agreement | [2018/377](https://eprint.iacr.org/2018/377) | 2018-04-30 | 2 | Preprint. MINOR revision. | **yes — never formally published** |
-| Compact Multi-Signatures for Smaller Blockchains (**BLS aggregate sigs**) | [2018/483](https://eprint.iacr.org/2018/483) | 2018-05-23 | 2 | Preprint. MINOR revision. | **yes — never formally published** |
-| Sync HotStuff: Simple and Practical Synchronous State Machine Replication | [2019/270](https://eprint.iacr.org/2019/270) | 2019-03-12 | 6 | Preprint. MINOR revision. | **yes** |
-
-### 7.5 Protocol security analysis (TLS, Signal)
-
-| Paper | ID | Recv | v | Publication info | Preprint first? |
-|---|---|---|---:|---|---|
-| A Cryptographic Analysis of the TLS 1.3 Handshake Protocol **Candidates** | [2015/914](https://eprint.iacr.org/2015/914) | 2015-09-22 | 2 | Published elsewhere, ACM CCS 2015 | **yes — analysed drafts pre-RFC** |
-| A Formal Security Analysis of the **Signal** Messaging Protocol | [2016/1013](https://eprint.iacr.org/2016/1013) | 2016-10-27 | 5 | Published elsewhere, IEEE EuroS&P 2017 | **yes** |
-| A Cryptographic Analysis of the TLS 1.3 Handshake Protocol (journal version) | [2020/1044](https://eprint.iacr.org/2020/1044) | 2020-08-28 | 2 | IACR publication, **JoC 2021** | **yes** |
-
-### 7.6 Hardware, embedded and side-channel
-
-| Paper | ID | Recv | v | Publication info | Preprint first? |
-|---|---|---|---:|---|---|
-| Provably Secure Higher-Order Masking of AES | [2010/441](https://eprint.iacr.org/2010/441) | 2010-08-17 | 1 | full version, **CHES 2010** | n/a (companion) |
-| High-speed high-security signatures (**Ed25519**) | [2011/368](https://eprint.iacr.org/2011/368) | 2011-07-10 | 2 | full version, **CHES** | n/a (companion) |
-| Threshold Implementations of all 3x3 and 4x4 S-boxes | [2012/300](https://eprint.iacr.org/2012/300) | 2012-06-03 | 2 | extended version, **CHES 2012** | **yes (posted pre-CHES)** |
-| Flush+Reload: a High Resolution, Low Noise, L3 Cache Side-Channel Attack | [2013/448](https://eprint.iacr.org/2013/448) | 2013-07-22 | 2 | Published elsewhere, USENIX Security 2014 | **yes (~1 year)** |
-| CacheBleed: A Timing Attack on OpenSSL Constant Time RSA | [2016/224](https://eprint.iacr.org/2016/224) | 2016-03-01 | 1 | Preprint. MINOR revision. | **yes** |
-| ECDSA Key Extraction from Mobile Devices via Nonintrusive Physical Side Channels | [2016/230](https://eprint.iacr.org/2016/230) | 2016-03-02 | 2 | Published elsewhere, ACM CCS 2016 | **yes** |
-| Number "Not Used" Once — Practical fault attack on **pqm4** implementations of NIST candidates | [2018/211](https://eprint.iacr.org/2018/211) | 2018-02-26 | 3 | Preprint. | **yes — never formally published** |
-| Differential Power Analysis of XMSS and SPHINCS | [2018/673](https://eprint.iacr.org/2018/673) | 2018-07-13 | 1 | Published elsewhere, COSADE 2018 | n/a (companion) |
-| **pqm4**: Testing and Benchmarking NIST PQC on ARM Cortex-M4 | [2019/844](https://eprint.iacr.org/2019/844) | 2019-07-19 | 2 | Preprint. MINOR revision. | **yes — never formally published** |
-| LadderLeak: Breaking ECDSA With Less Than One Bit Of Nonce Leakage | [2020/615](https://eprint.iacr.org/2020/615) | 2020-05-25 | 2 | Published elsewhere, ACM CCS 2020 | **yes** |
-| Minerva: The curse of ECDSA nonces (smartcards / secure elements) | [2020/728](https://eprint.iacr.org/2020/728) | 2020-06-17 | 1 | IACR publication, **TCHES 2020** | **yes** |
-| Ascon PRF, MAC, and Short-Input MAC (**NIST lightweight-crypto winner family**) | [2021/1574](https://eprint.iacr.org/2021/1574) | 2021-12-03 | 2 | Published elsewhere, CT-RSA 2024 | **yes — ~2.5 years** |
-| Combined Fault Injection and Real-Time Side-Channel Analysis for **Android Secure-Boot Bypassing** | [2022/602](https://eprint.iacr.org/2022/602) | 2022-05-17 | 2 | Published elsewhere, CARDIS 2022 | **yes** |
-| When Frodo Flips: End-to-End Key Recovery on FrodoKEM via **Rowhammer** | [2022/952](https://eprint.iacr.org/2022/952) | 2022-07-23 | 2 | Published elsewhere, ACM CCS 2022 | **yes** |
-| To Be, or Not to Be Stateful: **Post-Quantum Secure Boot** using Hash-Based Signatures | [2022/1198](https://eprint.iacr.org/2022/1198) | 2022-09-11 | 2 | Published elsewhere, ASHES 2022 | **yes** |
-| Recommendations for the Design and Validation of a Physical **TRNG** Integrated in a Cryptographic System | [2024/301](https://eprint.iacr.org/2024/301) | 2024-02-22 | 2 | Preprint. (licence **CC0**) | **yes — never formally published** |
-| Optimized Implementations of Keccak, Kyber, and Dilithium on the **MSP430 Microcontroller** | [2026/235](https://eprint.iacr.org/2026/235) | 2026-02-12 | 2 | IACR publication, **TCHES 2026** | **yes** |
-
-### 7.7 Special emphasis — ePrint as primary literature for embedded and hardware security
-
-For embedded work ePrint is not a supplement to the literature; for large stretches it *is* the
-literature. **Why:** CHES is an IACR Area Conference whose publication venue is **TCHES**, a
-diamond-OA journal operating as a journal/conference hybrid; the same holds for FSE→ToSC, which
-carries lightweight and symmetric-cipher work (S19, S20) [DOC]. Because IACR encourages ePrint
-posting of author versions from 2013 onward (S3) [DOC], the CHES/TCHES and FSE/ToSC pipelines flow
-through ePrint by default. `Implementation` alone holds **2,417 papers** (S4) [WEB]. CHES/TCHES-linked
-landmarks above: 2010/441, 2011/368, 2012/300, 2017/633, 2020/728, 2026/235.
-
-- **Side-channel countermeasure theory** — higher-order masking with security proofs (2010/441,
-  CHES 2010) and threshold implementations for glitch-resistant hardware (2012/300, CHES 2012): the
-  two foundations of essentially every masked AES core shipped since, both present as the *extended*
-  versions.
-- **Microarchitectural / cache attacks** — Flush+Reload (2013/448) appeared a full year before USENIX
-  Security 2014; CacheBleed (2016/224) has *never* left preprint status. These are the primitives
-  under the whole Spectre-adjacent literature.
-- **Physical key extraction and nonce leakage in deployed parts** — 2016/230 recovers ECDSA keys from
-  phones by non-intrusive physical measurement; Minerva (2020/728, TCHES 2020) and LadderLeak
-  (2020/615, CCS 2020) together establish that sub-one-bit ECDSA nonce leakage is key-recovering.
-  Directly relevant to smartcards, TPM-class parts and HSMs.
-- **Fault injection against MCU firmware** — 2018/211 mounts practical fault attacks on the `pqm4`
-  Cortex-M4 implementations of NIST PQC candidates and has never been formally published, so ePrint
-  is the only citable source; 2022/602 combines fault injection with real-time side-channel analysis
-  to bypass Android secure boot; 2022/952 turns Rowhammer bit flips into end-to-end FrodoKEM key
-  recovery. (The *original* Rowhammer paper is not on ePrint — §10.)
-- **Hardware RNG / TRNG design and certification** — 2024/301 (CC0) gives design and validation
-  recommendations for a physical TRNG in a cryptographic system. ePrint also carries AIS-20/31
-  compliant PLL-based TRNG designs and critiques of specific published TRNG constructions [WEB,
-  title-search results retained in scratch].
-- **Secure boot and lightweight crypto for constrained parts** — 2022/1198 works through the
-  stateful-versus-stateless hash-based-signature tradeoff, i.e. the LMS/XMSS-versus-SPHINCS+ decision
-  an MCU vendor faces now. Ascon, NIST's selected lightweight standard family, has its PRF/MAC modes
-  on ePrint (2021/1574) ~2.5 years before CT-RSA 2024; masked Ascon hardware implementations are also
-  present [WEB].
-- **Benchmark infrastructure** — `pqm4` (2019/844) is the de facto Cortex-M4 PQC benchmark and exists
-  as an ePrint preprint only.
-
-**Consequence for this knowledge base:** for claims about side-channel resistance, fault tolerance,
-TRNG entropy, secure boot or PQC performance on a microcontroller, ePrint is the first place to look
-and frequently the only place. But apply §5's checklist rigorously — a large share of the most-cited
-embedded results above carry `Preprint.` and have never been peer-reviewed at all.
-
-## 8. Access, APIs and bulk retrieval
-
-**There is no REST/JSON API.** Confirmed 404 on 2026-09-01: `/api`, `/api/`, `/api/search?q=…`,
-`/2017/1066.json`, `/json/2017/1066`. `/search?q=…&format=json` returns `text/html`, not JSON
-(S27) [API/WEB].
-
-**OAI-PMH is the real machine interface**, at `https://eprint.iacr.org/oai` (S6) [API]:
-
-| Property | Value |
-|---|---|
-| `repositoryName` / `repositoryIdentifier` | Cryptology ePrint Archive / `eprint.iacr.org` |
-| `protocolVersion` · `adminEmail` | 2.0 · eprint-editor@iacr.org |
-| `earliestDatestamp` | **1996-01-01T00:00:00Z** |
-| `deletedRecord` | **`persistent`** (machine-readable form of the never-remove policy) |
-| `granularity` · sample id | `YYYY-MM-DDThh:mm:ssZ` · `oai:eprint.iacr.org:2022/252` |
-| Metadata formats | **`oai_dc` only** |
-| Sets | **none** — `<error code="noSetHierarchy">We do not support sets yet.</error>` |
-| Declared friends | `tosc.iacr.org/…/oai`, `tches.iacr.org/…/oai` |
-
-**Bulk retrieval works and is easy.** `verb=ListIdentifiers&metadataPrefix=oai_dc` returned **all
-27,552 identifiers in a single 3.34 MB response with no resumption token** (S7) [API] — the cheapest
-reliable way to enumerate the archive. `GetRecord` returns Dublin Core with a separate `<dc:creator>`
-per author, both original and last-modified dates as `<dc:date>`, `<dc:publisher>International
-Association for Cryptologic Research (IACR)`, `<dc:type>e-print`, and a per-record `<dc:rights>`
-licence URL (S7) [API].
-
-*Minor spec deviation:* the `<request>` element in `GetRecord` responses contains
-`http://arXiv.org/oai2` rather than ePrint's own base URL — a leftover template artifact. Harmless,
-but it will confuse a strict harvester (S7) [API].
-
-**HTML listing endpoints** paginate at **100 items per page** via `?offset=N`: `/complete/` (298 KB),
-`/YYYY/` (note the trailing slash — `/2026` returns HTTP 308 → `/2026/`), `/days/{7,31,183,365}`,
-`/curr/`, `/complete/compact` (S27, S29) [WEB].
-
-**RSS/Atom feeds** at `/rss/` (S9) [DOC]: RSS 2.0 with authors in separate fields; a variant ordered
-by publication date rather than last-modified; a non-standard RSS 2.0 joining authors into one
-`<dc:creator>` (for Feedly-class readers); Atom; and Atom ordered by publication date. All accept
-`?category=NAME`. `/rss/rss.xml` returned 243 KB with 100 items (S27) [API]. Operators ask that
-"users should set their readers to refresh no more than once a day" (S9) [DOC]. News subscription:
-`https://www.iacr.org/news/subscribe` (S1) [WEB].
-
-**Rate limiting is real, Cloudflare-enforced, and self-documenting.** I tripped it during this
-compilation: HTTP **429**, `server: cloudflare`, rendered page reading *"Rate limit exceeded — You
-have exceeded the rate of **"20 per 1 minute"** on this path. Your IP address has been recorded as
-<ip>. If you are an actual human instead of a crawler, then you may contact us at
-eprint-abuse@iacr.org."* (S26) [WEB]. **No `Retry-After` header.** Budget ≥3.5 s between paper-page
-fetches; use OAI-PMH for anything bulk.
-
-**robots.txt is unusually restrictive and unusually candid** (S10) [DOC]. `User-agent: *` gets
-`Disallow: /` — general crawling forbidden, because "Crawlers must be whitelisted and confirmed to be
-following rules, which many do not." Named allowances for Googlebot, Claude-User, Claude-SearchBot
-(with published IP ranges checked), bingbot and DuckDuckBot (both `Crawl-delay: 5`). AI crawlers
-(GPTBot, ChatGPT-User, OAI-SearchBot, Google-Extended, ClaudeBot) get metadata/abstract paths but
-**`Disallow: *.pdf`** — no full text. All agents are blocked from `/archive`, `/versions`, `/submit`,
-`/search`. The file comments: *"Most AI crawlers willfully ignore the intent of the CC-BY license."*
-The OAI `dataPolicy` says the same formally: "current versions of papers may be crawled, but older
-versions must not be crawled" (S6) [API].
-
-### Negative controls (2026-09-01/02)
-
-| Probe | Result | Reads as |
-|---|---|---|
-| `/2017/1066` | HTTP 200, 16,690 B, text/html | real record |
-| `/2017/1066.pdf` | HTTP 200, 697,807 B, `application/pdf` | real full text |
-| `/2017/99999` · `/2017/9999` · `/2026/9999` | **HTTP 404**, 6,755 B (styled "Unknown paper") | nonexistent |
-| `/1995/001` | **HTTP 404**, 6,755 B | pre-archive year |
-| `/2017/99999.pdf` | **HTTP 404**, 309 B, `iso-8859-1` | bare server 404 — different shape |
-| `/2026/023` (the real 2026 gap) | **HTTP 404**, 6,755 B "Unknown paper" | allocated-but-absent |
-| `/2026/022`, `/2026/024` (neighbours) | HTTP 200 | gap is genuine, not a parse artifact |
-| `oai?verb=GetRecord&…:2026/023` and `…:2017/99999` | `<error code="idDoesNotExist">` | gap + 404 confirmed via API |
-| `/oai2`, `/harvest.html`, `/metadata.html`, `/api` | HTTP 404, 207 B | no such endpoints |
-
-**Two distinct 404 shapes exist** (6,755 B styled vs 207/309 B bare); a byte-size check distinguishes
-"the routing layer knows this pattern but the record is absent" from "no route". HTTP status alone
-suffices here — ePrint does not serve 200 for missing records.
-
-### Identifier scheme `YYYY/NNNN` — verified behaviour
-
-- **Zero-padded to exactly three digits** below 1000, four above. `/2026/022` → 200; **`/2026/22` →
-  404; `/2026/0022` → 404** (S27) [WEB]. Padding is mandatory in OAI identifiers too: `…:2026/22` →
-  `idDoesNotExist`, `…:2026/022` → the record (S27) [API].
-- **Sequential per calendar year, assigned at acceptance**, and essentially dense — 17 gaps in
-  27,569 allocated numbers, 99.94% dense (§3) [INF from API+WEB].
-- **Numbers are never reused.** 2017/1065 is a *withdrawn* paper sitting immediately below
-  Bulletproofs at 2017/1066; the number was not recycled (S16) [WEB].
-- Trailing slash redirects: `/2017/1066/` → HTTP 301 → `/2017/1066` (S27) [WEB].
-- Specific versions are addressable as `/archive/YYYY/NNNN/YYYYMMDD:HHMMSS` — the operators document
-  this exact form (S13) [DOC] and it resolves (S15) [WEB].
-
-## 9. Licensing and reuse
-
-**Authors choose from a fixed six-item menu** on the submission form (S12) [DOC]: `CC BY` · `CC BY-SA`
-· `CC BY-NC` · `CC BY-NC-SA` · `CC BY-NC-ND` · `CC0`. (Note the absence of plain `CC BY-ND`.)
-Submission grants IACR "a non-exclusive **and irrevocable** license to distribute the paper"; authors
-certify they may grant it and acknowledge "publications cannot be completely removed once accepted"
-(S3) [DOC].
-
-**Observed in my landmark sample: 40 of 41 are CC BY; one (2024/301, the TRNG recommendations paper)
-is CC0** (S28) [WEB]. I did not measure the archive-wide licence distribution — the per-record
-`<dc:rights>` field in OAI would allow it, but I did not run a full `ListRecords` harvest
-[NOT-VERIFIED].
-
-**Metadata is CC0.** "Metadata on this site is offered under a Creative Commons CC0 license. Full text
-in the PDFs of each paper is covered under a license that is specified with each paper, and you must
-obey these licenses." (S9) [DOC]. Harvesting is permitted "subject to the licensing conditions above.
-In particular this means attribution must be given to IACR and to authors" (S3) [DOC].
-
-**⚠️ Text and data mining is explicitly reserved — and this cuts against the CC-BY surface.** ePrint
-asserts a W3C TDMRep reservation two ways (S11) [API/WEB]: `<meta name="tdm-reservation" content="1">`
-on every page checked (home, paper pages, advanced search), and
-`https://eprint.iacr.org/.well-known/tdmrep.json` → `{"tdm-reservation": 1}` (HTTP 200). There is no
-accompanying `tdm-policy` URL, so no opt-in route is advertised. Combined with `Disallow: /` in
-robots.txt and the comment that "Most AI crawlers willfully ignore the intent of the CC-BY license"
-(S10) [DOC], the intent is unambiguous: a CC-BY licence on individual PDFs is not blanket permission
-to bulk-mine the corpus. `/ai.txt`, `/llms.txt`, `/.well-known/ai.txt` all 404 (S27) [WEB]. If you
-need the corpus, use OAI-PMH for metadata and ask — the harvesting page states "We can also provide
-other formats upon request" (S9) [DOC].
-
-## 10. Caveats and controversies
-
-**1. Nothing is ever removed — including things authors wish were.** "for papers that have been
-withdrawn, the previous versions remain accessible. The aim … is to create transparency and an
-accurate historical record … if removals or retrospective changes were implemented, then the archive
-would not be considered a publication." Withdrawal is one-way: "Once withdrawn, a paper cannot be
-restored; re-submissions of withdrawn papers will not be accepted." (S3) [DOC]. Verified (title-search
-`withdrawn` returns 15 such records):
-
-- **2017/1065** — current page shows title `--Withdrawn--`, abstract `---`, "Available format(s):
-  `-- withdrawn --`", history `2018-09-22: withdrawn / 2017-11-09: received`. **`/2017/1065.pdf` →
-  HTTP 404.** But `/archive/versions/2017/1065` still lists both updates and
-  `/archive/2017/1065/20171109:164544` still serves the **original title and full abstract**: *"On the
-  Security of a Lightweight Cloud Data Auditing Scheme"* (S16) [WEB].
-- **2019/1410** — everything replaced with the literal string `Withdrawn`, but the Note preserves the
-  reason: *"Based on several feedback with respect to constant time issues, we have withdrawn the
-  paper."* (S17) [WEB].
-
-⚠️ **Recorded conflict.** Policy says the archive "will keep the title and abstract of the paper"
-(S3) [DOC]. In practice the *current* record's title and abstract are overwritten with placeholders;
-the originals survive only in the version archive — which robots.txt forbids crawlers from indexing
-(S10) [DOC]. The PDF is genuinely gone. So "nothing is removed" is true of metadata-in-the-archive and
-**false of the current record and the full text**. Both statements sourced; not resolved here.
-
-**2. The "ePrint says X is broken" problem.** A cryptanalysis report has been read by an editor for
-plausibility, not correctness (§4). Because breaks are newsworthy, they propagate to press and
-procurement *before* any review. SIKE (§5) shows the system working — the break was real. The failure
-in the other direction (a widely reported ePrint "break" later shown wrong) is a known hazard of the
-design; **I did not verify a specific instance in this pass** [NOT-VERIFIED].
-
-**3. Duplicate and superseded versions.** The archive "actively discourages … posting different
-versions of essentially the same material as multiple entries" and asks authors to revise instead
-(S3) [DOC] — an admission that it happens. Over half of covered records have been revised at least
-once, one 44 times (PLONK) and one 125 times (§3). **Cite a specific version timestamp** via
-`/archive/YYYY/NNNN/YYYYMMDD:HHMMSS` (S13) [DOC] when the claim is version-sensitive.
-
-**4. Titles change under a stable identifier.** 2017/1066 v1 was *"Bulletproofs: Efficient Range Proofs
-for Confidential Transactions"*; it is now *"…: Short Proofs for Confidential Transactions and More"*
-(S14, S15) [WEB]. The number is stable; the title is not. Title-keyed bibliographies rot silently.
-
-**5. Corrections hide in a free-text `Note:` field.** Bulletproofs' note discloses a fix to "an earlier
-mistake in the Fiat-Shamir section (Section 4.4) reported by TrailOfBits" (S28) [WEB]. There is no
-structured erratum field, no machine-readable correction flag, and the note is **not exposed in the
-OAI `oai_dc` record**. A harvester will not see corrections — arguably ePrint's most serious metadata
-gap for automated consumers [INF].
-
-**6. Publication metadata is author-maintained and decays.** BGV (2011/277) and BFV (2012/144) both
-read "Published elsewhere. Unknown where it was published" (S28) [WEB]. My 2017 sample put 38.3% at
-`Preprint.`, an unknown share of which *are* published but never updated (§5).
-
-**7. No DOI, no versioned DOI.** Unlike arXiv or Zenodo, ePrint mints no DOI (§5). Citation managers
-keyed on DOI will not resolve an ePrint-only work.
-
-**8. No sets, one metadata format.** OAI exposes only `oai_dc` and no set hierarchy (S6, S8) [API], so
-category-scoped harvesting must go via the RSS `?category=` feeds or HTML.
-
-**9. Scope has a hard boundary.** Consensus protocols, ORAM, cache attacks and Rowhammer variants all
-appear under a "cryptology" banner — but the *originating* systems papers in adjacent fields generally
-do **not**. Searches on 2026-09-01 found **no ePrint record** for: the original HotStuff (Yin et al.),
-the original Algorand (Chen–Micali), ROCA / "The Return of Coppersmith's Attack", the original
-Rowhammer paper, Spectre/Meltdown, the PRESENT cipher paper, the Keccak/SHA-3 specification, "Short
-Signatures from the Weil Pairing", Dwork et al.'s differential-privacy paper, TPM-FAIL, Logjam and
-DROWN. Those live on arXiv, in ACM/IEEE/USENIX proceedings, or on project sites. **ePrint is dominant
-for cryptology, not for systems security generally** [WEB, negative searches].
-
-**10. Reader-privacy posture (a positive one).** Every page footer: "In order to protect the privacy of
-readers, eprint.iacr.org does not use cookies or embedded third party content." (S1) [DOC], consistent
-with the absence of third-party asset hosts in the fetched HTML [INF]. Rate-limit pages do, however,
-record and display your IP (S26) [WEB].
-
-## 11. Sources
-
-All retrieved **2026-09-01 / 2026-09-02 UTC**. Plain `curl` with a default/`curl` User-Agent succeeded
-on every eprint.iacr.org and iacr.org URL below — **no AGENTS.md User-Agent fallback was needed**; the
-only failures were HTTP 429 rate limits, resolved by backing off.
-
-- **S1** https://eprint.iacr.org/ — mission statement, current editors, news items, privacy footer.
-- **S2** https://eprint.iacr.org/about.html — goals, "Behind the Name", full history (Theory of Cryptography Library 1996 MIT → UCSD 1998 → ePrint fall 1999), size milestones, complete past-editor list.
-- **S3** https://eprint.iacr.org/operations.html — **the policy document**: acceptance criteria, licensing, further publication, revised/withdrawn papers, anonymous-submission position, harvesting.
-- **S4** https://eprint.iacr.org/stats — JS data variables `byyear`, `byday`, `categoryData`, `authorData`, `versionData`, `counters`.
-- **S5** https://eprint.iacr.org/byyear — per-year paper counts and category index.
-- **S6** https://eprint.iacr.org/oai?verb=Identify — repository identity, `deletedRecord: persistent`, `earliestDatestamp`, data/metadata/submission policies, friends.
-- **S7** https://eprint.iacr.org/oai?verb=ListIdentifiers&metadataPrefix=oai_dc (3.34 MB, 27,552 identifiers) and `verb=GetRecord` for individual records.
-- **S8** https://eprint.iacr.org/oai?verb=ListMetadataFormats and `verb=ListSets`.
-- **S9** https://eprint.iacr.org/rss/ — harvesting page: feed inventory, per-category feeds, CC0 metadata statement, refresh guidance.
-- **S10** https://eprint.iacr.org/robots.txt — crawler whitelist, AI-bot PDF ban, `Disallow: /` default.
-- **S11** https://eprint.iacr.org/.well-known/tdmrep.json and the `tdm-reservation` meta tag.
-- **S12** https://eprint.iacr.org/submit — category values, field constraints, six-licence menu, confirmation text.
-- **S13** https://eprint.iacr.org/citation.html — recommended BibTeX, version-specific URL form, DOI guidance.
-- **S14** https://eprint.iacr.org/archive/versions/2017/1066 — 15-entry version history with `YYYYMMDD:HHMMSS` timestamps.
-- **S15** https://eprint.iacr.org/archive/2017/1066/20171110:151138 — Bulletproofs v1, showing the original title.
-- **S16** https://eprint.iacr.org/2017/1065 + /archive/versions/2017/1065 + /archive/2017/1065/20171109:164544 — withdrawal semantics.
-- **S17** https://eprint.iacr.org/2019/1410 — second withdrawal example, reason preserved.
-- **S18** https://iacr.org/docs/ — Nevada non-profit, bylaws, articles of incorporation, committee policies, copyright policy.
-- **S19** https://iacr.org/docs/bylaws.pdf — bylaws approved 2025-12-20: purposes, conference/journal taxonomy, officers, Treasurer's financial-report duty.
-- **S20** https://iacr.org/publications/ — IACR publication inventory; ToSC/TCHES diamond OA; ePrint's role and "no scientific reviewing process".
-- **S21** https://iacr.org/conferences/ — Asiacrypt, Crypto, Eurocrypt, CHES, FSE, PKC, TCC, RWC.
-- **S22** https://en.wikipedia.org/api/rest_v1/page/summary/International_Association_for_Cryptologic_Research — IACR organised at David Chaum's initiative at CRYPTO '82.
-- **S23** https://en.wikipedia.org/w/api.php?action=query&prop=extracts&titles=Cryptology%20ePrint%20Archive — full extract; contains no size figures.
-- **S24** https://csrc.nist.gov/News/2022/pqc-candidates-to-be-standardized-and-round-4 — dated **July 05, 2022**. (Fetched with the Chrome UA from AGENTS.md step 2; default curl was not tried first on this host.)
-- **S25** https://eprint.iacr.org/2022/975 + /archive/versions/2022/975 — SIKE break abstract and five version timestamps from 20220730:072007.
-- **S26** HTTP 429 from https://eprint.iacr.org/2016/889 — Cloudflare rate-limit page stating `"20 per 1 minute"` on this path; no `Retry-After`.
-- **S27** Probe set (negative controls, identifier padding, endpoint discovery, `ia.cr` redirect, RSS/`/complete/` pagination) — curl transcripts in `doc/hardware/scratch/preprint-repositories/cryptology-eprint/`.
-- **S28** The 41 landmark pages `https://eprint.iacr.org/<ID>` in §7, each fetched and parsed for title, authors, receipt date, version count, licence and publication info. Machine-readable: `scratch/preprint-repositories/cryptology-eprint/all_landmarks.json`.
-- **S29** https://eprint.iacr.org/2026/?offset=N (19-page full sweep) — 2026 contains 1,845 records, max number 1846, exactly one gap at `2026/023`.
-- **S30** https://api.crossref.org/works?query.bibliographic=… (two queries) — no scientometric literature on ePrint located; basis for the [NOT-VERIFIED] [LIT] entry in §5.
diff --git a/research/preprint-repositories/ecsarxiv.md b/research/preprint-repositories/ecsarxiv.md
deleted file mode 100644
index 74e33d5..0000000
--- a/research/preprint-repositories/ecsarxiv.md
+++ /dev/null
@@ -1,408 +0,0 @@
-# ECSarXiv — preprint repository record
-
-- **URL:** https://ecsarxiv.org/ (302 → `https://osf.io/preprints/ecsarxiv/`)
-- **Operator:** **The Electrochemical Society (ECS)**, a non-profit scholarly society
-  ("more than 8,000 individual members and 48,000 other constituents"), as part of its
-  *Free the Science* open-access programme (S1). Hosted on the **Center for Open Science's
-  Open Science Framework (OSF) Preprints** platform (S1, S2). Free to submit, free to read.
-- **Discipline scope:** "a free preprint service for **electrochemistry and solid state
-  science and technology**" (S2, provider `description` field). That second half is the part
-  hardware people miss — it covers semiconductor processing, dielectrics, deposition and
-  device work, not just wet chemistry (§2).
-- **Launched:** earliest deposit **2018-05-11** (S3). ECS's own announcement date is
-  **[NOT-VERIFIED]** — the About page carries no launch date.
-- **Status:** active but **very small and flat** — ~20–27 deposits/year since 2021 (§3).
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-ECSarXiv is the Electrochemical Society's preprint server. ECS's own framing is worth
-quoting because it explains why a society this size bothered: "ECS is a very broad and
-diverse community, and has needs that are different from those using preprint services such
-as arXiv, bioRxiv, ChemArxiv" — the goal was "faster, more relevant search results for the
-field" (S1). It is deliberately cheap to run: ECS did not build a platform, it took a
-white-labelled OSF Preprints instance, which it says "has made our service
-cost-effective… and provides a robust search interface across other scholarly resources"
-(S1).
-
-For someone building embedded hardware, ECSarXiv matters for one reason: **ECS's remit is
-the chemistry and physics underneath your components**. The Society's divisions include
-Battery, Corrosion, Electrodeposition, Dielectric Science and Technology, Electronics and
-Photonics, Luminescence and Display Materials, and Sensor (S1). Its two flagship journals
-are the *Journal of The Electrochemical Society* and the *ECS Journal of Solid State
-Science and Technology*. ECSarXiv is the preprint front-end to that world: cell ageing,
-impedance spectroscopy, electrodeposition, wafer processing, gas and glucose sensors, MEMS.
-
-It is, however, **tiny** — 323 deposits in eight years (§3). Set your expectations
-accordingly: this is a place to find a specific well-made document, not a corpus to survey.
-
-## 2. Scope and subject taxonomy
-
-Two taxonomies apply, and they differ.
-
-**(a) ECS's own Topical Interest Areas**, the editorially meaningful list, used across all
-ECS publications (S1):
-
-Batteries and Energy Storage · Carbon Nanostructures and Devices · Corrosion Science and
-Technology · **Dielectric Science and Materials** · Electrochemical/Electroless Deposition ·
-Electrochemical Engineering · **Electronic Materials and Processing** · **Electronic and
-Photonic Devices and Systems** · Fuel Cells, Electrolyzers, and Energy Conversion ·
-Luminescence and Display Materials, Devices, and Processing · Organic and
-Bioelectrochemistry · Physical and Analytical Electrochemistry, Electrocatalysis, and
-Photoelectrochemistry · **Sensors**
-
-**(b) The OSF subject tree**, which is what the API actually returns: **270 subject terms**
-(S4). It is the standard OSF/bepress tree with an ECS-specific graft, and the graft is where
-the hardware relevance lives. Selected leaves, verbatim (S4):
-
-- under **Electronic Materials and Processing**: `2D Materials`, `Atomic Layer Deposition`,
-  `Atomic Layer Etching`, `Barrier Layers`, `Chemical Etching`, `Chemical Vapor Deposition`,
-  `Cleaning`, `Electronic Devices and Semiconductor Manufacturing`,
-  `Group II-VI Semiconductors`, `Group III-V Semiconductors`, `Group IV Semiconductors`,
-  `High-k Dielectrics`, `Interconnects`, `Low-k Dielectrics`
-- under **Materials Science and Engineering**: `Aqueous Batteries`,
-  `Batteries and Energy Storage`, `Ceramic Materials`, `Coatings`, `Corrosion`,
-  `Dielectric Science and Materials`, `Electrochemical Capacitors`, `Electrodeposition`,
-  `Electroless Deposition`, `Films`, `Flow Batteries`, `LeClanche Batteries`,
-  `Lead Acid Batteries`, `Lithium Batteries`, `Metal Carbides`, `NiCd Batteries`,
-  `NiMH Batteries`, `Oxides`, `Polymer Fuel Cells`, `Semiconductor and Optical Materials`,
-  `Solid Oxide Fuel Cells`
-- under **Electrical and Computer Engineering**: `Electronic and Photonic Devices and
-  Systems`, `Power and Energy`, `Signal Processing`, `Systems and Communications`,
-  **`VLSI and Circuits, Embedded and Hardware Systems`**
-- under **Energy**: `Electrolyzers`, `Energy Efficient Electronic Devices`, `Fuel Cells`,
-  `Solar Cells`
-- under **Physics**: `Plasma Deposition`, `Plasma Etching`, `Plasma Polymerization`,
-  `Luminescence and Display Materials and Processing`, `Condensed Matter Physics`
-- under **Chemistry**: `Electroanalytical`, `Electrocatalysis`, `Electrodes`,
-  `Electrolytes`, `Interfaces`, `Nitrides`, `Semiconductors`, `Sensors`, `Sulfides`,
-  `Carbides`
-- under **Nanoscience and Nanotechnology**: `Nanofabrication`,
-  `Nanocharacterization: Electron Microscopy / Optical Microscopy / Surface Probe Microscopy`,
-  `Plasmonics`, `Carbon Nanostructures and Devices`
-
-**Actual subject usage** across all 323 deposits (multi-label; counts are term assignments,
-S3):
-
-| Term | Uses | | Term | Uses |
-|---|---|---|---|---|
-| Engineering | 461 | | Batteries and Energy Storage | 30 |
-| Physical Sciences and Mathematics | 218 | | Other Electrochemical Engineering | 24 |
-| Chemistry | 143 | | Materials Chemistry | 20 |
-| Materials Science and Engineering | 106 | | Mechanical Engineering | 17 |
-| Electrochemical Engineering | 105 | | Electronic Materials and Processing | 13 |
-| Electrochemistry | 56 | | Electrodes / Electrocatalysis / Corrosion | 13 each |
-| Chemical Engineering | 56 | | Nanoscience and Nanotechnology | 12 |
-| Energy | 51 | | Electrolyzers | 10 |
-| Mathematical Modeling | 35 | | Electrical and Electronics | 10 |
-| Physics | 32 | | Sensors / Energy Systems / Fuel Cells | 8 each |
-| Electrical and Computer Engineering | 31 | | Polymer Fuel Cells | 8 |
-
-The honest read: batteries, electrochemical engineering and modelling dominate;
-semiconductor-processing terms exist in the taxonomy but are lightly used
-(`Electronic Materials and Processing`, 13 uses).
-
-## 3. Size and growth
-
-| Measure | Value | Date | Source |
-|---|---|---|---|
-| OSF JSON:API `links.meta.total` for `filter[provider]=ecsarxiv` | **323** | 2026-09-01 | [API] S3 |
-| Records actually harvested by paging that endpoint | **323** (matches) | 2026-09-01 | [API] S3 |
-| Records carrying a journal DOI in the `doi` field | **25** (7.7%) | 2026-09-01 | [API] S3 |
-| OpenAlex source `ECSarXiv (OSF Preprints)` `works_count` | **17** | 2026-09-01 | [API] S6 |
-
-The OpenAlex figure (17) conflicts violently with the operator's own registry (323). Record
-both; **use the OSF API number.** As with engrXiv, OpenAlex has essentially not indexed this
-server (S6).
-
-**Deposits by year of publication** (S3):
-
-| 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 (to 09-01) |
-|---|---|---|---|---|---|---|---|---|
-| 31 | 66 | 74 | 23 | 42 | 20 | 20 | 20 | 27 |
-
-This is the shape of a server that launched with society enthusiasm (2018–2020, including
-batches of ECS meeting slide decks — several titles literally begin "(ECS 236th)" or
-"235th ECS Meeting:", S3), then settled into a trickle of ~20/year. It has not grown, and it
-has **not** been hit by the generative-AI submission wave that engrXiv reports — the 2026
-partial-year figure of 27 is the highest since 2020, but from a base so small the number is
-noise [INF].
-
-**323 deposits is the whole thing.** For context, that is about one twentieth of engrXiv and
-about 0.5% of arXiv's `cond-mat` output. Absence from ECSarXiv means nothing whatsoever.
-
-Note also that ECSarXiv accepts **non-article content by policy** — "articles, slide
-presentations, datasets, software, etc." (S1) — so the 323 is not 323 papers. Several are
-conference slide decks and at least one is a software announcement (§5).
-
-## 4. Screening and moderation — what gets in
-
-**Pre-moderation.** The OSF provider record reports `reviews_workflow: pre-moderation` and
-`allow_submissions: true` (S2). ECS's published posting policy states the gate precisely
-(S1, verbatim, emphasis original to the source):
-
-> - Preprints may be articles, slide presentations, datasets, software, etc.
-> - **PREPRINTS MAY NOT BE ARTICLES THAT HAVE ALREADY BEEN PUBLISHED IN ANY PEER-REVIEWED
->   JOURNAL.**
-> - Preprints undergo a screening process to reject offensive and/or nonscientific content
->   and/or content not relevant to the fields ECS covers.
-> - Preprints are not peer-reviewed, edited, or typeset before being posted online.
-> - Preprints must be in English.
-> - Authors must have sufficient rights to post any material submitted to ECSarXiv.
-> - Authors may submit a revised version of a preprint to ECSarXiv at any time (prior to
->   publication in a journal).
-> - **No endorsement of a preprint's methods, assumptions, conclusions, or scientific
->   quality by ECS is implied by its appearance in ECSarXiv.**
-
-So the gate is: relevance + not-offensive + not-already-published + English. There is no
-quality check, no endorsement requirement, no affiliation requirement. Elsewhere the About
-page describes it as "quick moderation" (S1). **Who performs the screening, and the
-turnaround time, are [NOT-VERIFIED]** — ECS names an Advisory Board section on the page but
-the OSF `advisory_board` field is empty (S2).
-
-ECS also gives concrete, correct advice about the ecosystem: "Always check the policies of
-the journals where you plan to submit… Some journals allow the author to submit subsequent
-revised preprints after submitting to journals, some do not" (S1).
-
-## 5. Reliability — what you can and cannot trust
-
-**A deposit guarantees:** a DOI (ECS states this explicitly — "preprints in ECSarXiv carry a
-DOI", S1), a timestamp, a version chain, an explicit licence, and that a human confirmed the
-work is in-scope and not obviously nonsense. Nothing more, and ECS says so ("no endorsement…
-is implied").
-
-**Publication linkage is weak.** Only **25 of 323** records carry a journal DOI in the OSF
-`doi` field (S3). Where they point is informative: `10.1149/...` (ECS's own journals, via
-IOP) and `10.1149/MA...` (ECS Meeting Abstracts) dominate, with occasional
-`10.1016/j.jpowsour...`, `10.1021/acsaem...` and one `10.1109/TCST...`. This is a **floor,
-not a rate** — the field is author-populated and mostly left blank [INF]. Treat "no journal
-DOI" as "unknown", not "unpublished".
-
-**Known failure modes.** (a) A meaningful fraction of the corpus is **conference slide
-decks and posters**, not manuscripts — useful, but not a paper, and easy to mis-cite.
-(b) Because the corpus is so small and quiet, **stale content is normal**: a 2019 preprint
-with no journal DOI has probably been published somewhere without the record being updated.
-(c) There is no peer review of any kind, in a field where a single mis-specified impedance
-model or an unreported C-rate makes results meaningless. (d) Duplicate/versioned entries
-appear in listings (e.g. `rfwug_v1` and `rfwug_v5` both surface as separate dated records,
-S3) — deduplicate on the base GUID.
-
-**How to sanity-check an ECSarXiv item.** Read the `is_published` and
-`original_publication_date` attributes from the API; search the title in the ECS Digital
-Library and Crossref for a journal version; and for battery/impedance work, check the
-document actually reports cell chemistry, temperature, C-rate and cycle count — the ECS
-community's own reviewers would.
-
-## 6. What you actually find there — and why an embedded engineer should care
-
-Every item below was confirmed present in the 2026-09-01 API harvest, with its OSF GUID
-(resolve as `https://osf.io/<guid>/`) (S3).
-
-**Battery modelling and ageing — the strongest cluster on the server:**
-
-- **PyBaMM — *Python Battery Mathematical Modelling*** — `67ckj`, 2020-02-07. The
-  announcement of what is now a widely used open-source battery simulation package. If you
-  are writing a BMS state estimator, this is the single most directly useful item on
-  ECSarXiv.
-- *Nonlinear electrochemical impedance spectroscopy of lithium-ion batteries: Experimental
-  approach, analysis…* — `t635x`, 2018-06-25. This is the item ECS itself designates as its
-  `example` preprint in the provider record (S2).
-- *One law to rule them all: Stretched exponential master curve of capacity fade for Li-ion
-  batteries* — `zxkbu`, 2019-02-14.
-- *Review and performance comparison of mechanical-chemical degradation models for
-  lithium-ion batteries* — `zdwsu`, 2019-05-28.
-- *Lithium Plating Detection Methods in Lithium-ion Batteries* — `bj9gr`, 2020-08-17.
-- *Reversible and Irreversible Expansion of Lithium-ion Batteries Under a Wide Range of
-  Stress Factors* — `f79ey`, 2021-08-24 — directly relevant to pack mechanical design.
-- *Investigation and modeling of cyclic aging using a design of experiment with automotive
-  grade lithium-ion cells* — `vdajp`, 2021-09-22 → `10.1016/j.jpowsour.2021.230952`.
-- *A Composite Single Particle Lithium-ion Battery Model through System Identification* —
-  `ynufg`, 2019-12-03 → `10.1109/TCST.2020.3047776` (*IEEE Trans. Control Systems
-  Technology*) — the clearest preprint→IEEE path on this server.
-- *Battery Lifecycle Framework: A Flexible Repository and Visualization Tool for Battery
-  Data* — `h7c24`, 2021-03-13.
-- *Extending a Multi-physics Li-ion Battery Model from Normal Operation to Short Circuit and
-  Venting* — `j6xmv`, 2024-05-26 — thermal-runaway-adjacent.
-- *Relevance of classical models/approaches for Battery Digital Twins* — `sxtjw`, 2025-07-19.
-
-**Sensors and MEMS:**
-
-- *Distributed Bridge Circuit for High-Temperature Silicon MEMS Pressure Sensors* — `rfwug`,
-  2026-08-06 (revised to `v5`, 2026-08-22). Piezoresistive bridge design — genuinely a
-  circuits paper.
-- *Enhancing Potentiometric Response of Electrochemical Sensor Using Modified Ion-Sensitive
-  Transistor* — `7bukj`, 2019-03-15. ISFET work.
-- *Functional Iron Oxide (Fe₂O₃) Nanoparticles Based Gas Sensor Operating at High
-  Temperature* — `s9ykg`, 2019-05-29.
-- *Determination of the working temperature of the MOS sensors used for the detection of
-  ethanol and methanol* — `qmt78`, 2021-06-03. Metal-oxide gas sensor heater calibration.
-- *Facile Sensors for Humidity Measurement of Indoor Environment* — `ruwb6`, 2023-01-31;
-  *Temperature Sensing of Indoor Environment Using Resistive and Capacitive Sensors* —
-  `9teu3`, 2023-02-06.
-- *Cost-effective 316L-based glucose sensor architectures* — `zaygq`, 2025-06-13.
-
-**Semiconductor and interconnect processing:**
-
-- *On the roughness analysis of high-index silicon wafers using KOH-IPA solutions* — `d2a6z`,
-  2020-08-17. Bulk-micromachining etch chemistry.
-- *Homogeneous backside porosification of standard silicon wafers for post-fab process
-  integration of porous silicon* — `sfyux`, 2025-05-20.
-- *(ECS PRiME 2020) High TEC copper to connect copper bond pads for low temperature wafer
-  bonding* — `ns3kf`, 2020-08-28. 3D-integration / hybrid bonding.
-- *Examination of Reducing Agents Used for Aluminum Electroless Deposition* — `xsuja`,
-  2020-08-17.
-- *NaCl-Assisted Chemical Vapor Deposition of Monolayer MoS₂: A Review* — `r4hj6`, 2026-05-14.
-- *A study on corrosion resistance of electroplated Gold over Nanocrystalline Ni-W for
-  contact applications* — `s5pgz`, 2019-03-15 — connector/contact plating reliability.
-- *Comparative evaluation of corrosion effects between nanocrystalline silver alloy and
-  traditional gold stack* — `hnpwe`, 2019-03-15.
-
-**Supercapacitors:**
-
-- *High Energy-Density Supercapacitor, Enabled by Carbon Nanostructures* — `b3ec4`, 2020-08-12.
-- *Electrochemical Study of the Effect of Prussian Blue as a Mediator in a Solid-state
-  Supercapacitor* — `3wnbh`, 2020-08-12.
-- *Simultaneous Electrochemical Exfoliation and Chemical Functionalization of Graphene for
-  Supercapacitor Electrodes* — `ycbj8`, 2020-05-05.
-- *Next Generation Transparent Supercapacitor Materials* (poster) — `pg9y7`, 2019-10-11.
-- *Perovskite and Polymer Composites for High-Performance Supercapacitor Electrodes: A
-  Review* — `wrpt7`, 2025-10-12.
-
-**Instrumentation and measurement technique** — the category most likely to save you time:
-
-- *Use and misuse of electrochemical impedance spectroscopy in PEFC research* — `hr6nf`,
-  2019-11-05.
-- *Rapid analytical instrumentation for electrochemical impedance spectroscopy measurements*
-  — `w94xh`, 2019-12-03.
-- *Real-Time Under Load Electrochemical Impedance Spectroscopy (EIS) Analysis and Modeling* —
-  `chmwk`, 2020-08-12.
-- *Respirometric In-Situ Methods for Real-Time Monitoring of Corrosion Rates*, Parts I and II
-  — `t69j3` (2019-11-22 → `10.1149/1945-7111/ab6c61`) and `g3vaz` (2020-12-01).
-
-## 7. Landmark papers
-
-**ECSarXiv hosts no field-defining papers in software, distributed systems, databases,
-electronics or security.** The closest thing to a landmark artifact is the **PyBaMM**
-announcement (`67ckj`, §6), which is significant as *software* rather than as a paper. Cited
-impact across the server is negligible — ECSarXiv is a small society service, not a priority
-venue. Table deleted.
-
-## 8. Access, APIs and bulk retrieval
-
-**Use the OSF JSON:API. Do not scrape osf.io HTML.**
-
-```bash
-# total count
-curl 'https://api.osf.io/v2/preprints/?filter%5Bprovider%5D=ecsarxiv&meta%5B%5D=total'
-# full harvest (page through links.next)
-curl 'https://api.osf.io/v2/preprints/?filter%5Bprovider%5D=ecsarxiv&page%5Bsize%5D=100'
-# provider metadata: name, description, reviews_workflow, domain, example
-curl 'https://api.osf.io/v2/providers/preprints/ecsarxiv/'
-# 270-term subject tree
-curl 'https://api.osf.io/v2/providers/preprints/ecsarxiv/subjects/?page%5Bsize%5D=100'
-```
-
-The whole corpus paged out in seconds; no rate limiting was hit; no user-agent substitution
-was needed. Square brackets in the query string **must be percent-encoded** or `curl` fails
-with "bad range in position" (S3).
-
-### Negative control — and it is an important one
-
-**`https://osf.io/preprints/zzzznotreal/` returns HTTP 200 with 4,207 bytes — byte-for-byte
-the same length as the real `https://osf.io/preprints/ecsarxiv/` page** (S5). osf.io is an
-Angular single-page application: *every* path returns the same 200 shell, and the router
-decides afterwards whether the content exists. The same applies to `https://osf.io/oai` and
-`https://osf.io/oai/?verb=Identify`, which return `Content-Type: text/html` and the SPA
-shell rather than an OAI-PMH response (S5).
-
-**Consequences:** (1) on osf.io, HTTP 200 carries **zero** information; (2) `ecsarxiv.org`
-resolving with a 200 proves nothing about the archive existing; (3) there is **no working
-OAI-PMH endpoint** found for ECSarXiv — `[NOT-VERIFIED]` whether one exists elsewhere.
-
-By contrast the **API** behaves correctly: `https://api.osf.io/v2/providers/preprints/zzzznotreal/`
-returns **404, 61 bytes** (S5). That is the discriminator to build tooling on.
-
-**Redirect chain:** `https://ecsarxiv.org/` → 200 at `https://osf.io/preprints/ecsarxiv/`
-(S5). Cite OSF GUIDs (`https://osf.io/<guid>/`) or DOIs, never the `ecsarxiv.org` vanity
-domain, which is a redirect that ECS could retire.
-
-**Crossref** is a viable secondary route for the 25 items with journal DOIs, but ECSarXiv's
-own preprint DOIs are OSF-issued and not consistently exposed in the JSON:API `doi` field
-(that field holds the *journal* DOI). Extracting preprint DOIs requires following each
-record's `preprint_doi` relationship — not attempted in this pass, **[NOT-VERIFIED]**.
-
-## 9. Licensing and reuse
-
-Authors choose from the OSF licence list. Distribution across all 323 deposits (S3, licence
-IDs resolved via `https://api.osf.io/v2/licenses/<id>/`):
-
-| Licence | Records |
-|---|---|
-| CC BY 4.0 | 180 |
-| CC BY-NC-ND 4.0 | 56 |
-| GNU LGPL 3.0 | 44 |
-| CC BY-SA 4.0 | 14 |
-| CC0 1.0 | 14 |
-| others (CC BY-NC, MIT, …) | ~15 |
-
-Two things worth flagging. **CC BY is a bare majority (56%), not the norm** — 17% is
-CC BY-NC-ND, which forbids derivative works, so you cannot legally re-plot someone's ageing
-curves from those. And **44 records are licensed LGPL-3.0**, which is a software licence: a
-direct consequence of ECS's policy of accepting software and datasets as first-class
-deposits (§4). Check the licence per item; do not assume.
-
-ECS publishes a dedicated "Licensing" section on the About page (S1). Text and data mining
-of the metadata via the OSF API is unrestricted in practice.
-
-## 10. Caveats and controversies
-
-- **Size is the dominant caveat.** 323 items. Nothing you fail to find here tells you
-  anything.
-- **Growth has flatlined** at ~20/year since 2021 (§3). A society preprint server with this
-  little traffic is a candidate for quiet discontinuation; archive anything you rely on.
-- **It is not a hardware-design venue.** It is a *materials and electrochemistry* venue
-  whose output happens to constrain hardware. You will find why your cell fades, not how to
-  lay out the BMS.
-- **osf.io's 200-for-everything behaviour** (§8) has burned automated pipelines before;
-  it is the single most important operational fact in this record.
-- **Mixed content types** — slide decks, posters, datasets, software — are policy, not
-  accident (§4). Cite accordingly.
-- **The "no previously published articles" rule** (§4) means ECSarXiv is *not* a green-OA
-  route for already-published ECS papers, unlike engrXiv which explicitly accepts those.
-- **OpenAlex records 17 works against a true 323** (§3).
-- **ECS's launch announcement and the identity of its moderators are not documented here**
-  — [NOT-VERIFIED].
-
-## 11. Sources
-
-- **S1** — `https://www.electrochem.org/ecsarxiv` — ECS's own "About ECSarXiv" page,
-  including *Why another preprint service?*, *Benefits of ECSarXiv*, *Technical areas covered
-  by ECSarXiv* (the 13 Topical Interest Areas), *Posting policy* (quoted verbatim in §4), and
-  *Definition of ECSarXiv preprints*. Also the ECS divisional list. Retrieved 2026-09-01
-  (browser UA required; the site returns full HTML). **[DOC]**
-- **S2** — OSF JSON:API provider record,
-  `https://api.osf.io/v2/providers/preprints/ecsarxiv/` — `name: ECSarXiv`;
-  `description: "a free preprint service for electrochemistry and solid state science and
-  technology"`; `domain: https://ecsarxiv.org/`; `reviews_workflow: pre-moderation`;
-  `allow_submissions: true`; `example: t635x`; `email_support: support+ecsarxiv@osf.io`;
-  `advisory_board` empty. Retrieved 2026-09-01. **[API]**
-- **S3** — OSF JSON:API preprint harvest,
-  `https://api.osf.io/v2/preprints/?filter[provider]=ecsarxiv&meta[]=total&page[size]=100`,
-  paged to completion (323 records; dumped to scratch as `osf_ecsarxiv.json`), plus
-  `https://api.osf.io/v2/licenses/<id>/` lookups. Retrieved 2026-09-01. **[API]** — supports
-  the total, the per-year table, the subject-usage table, the licence table, the
-  journal-DOI count, and every example title/GUID/date in §6.
-- **S4** — OSF JSON:API subject tree,
-  `https://api.osf.io/v2/providers/preprints/ecsarxiv/subjects/?page[size]=100`, paged to
-  completion (270 terms). Retrieved 2026-09-01. **[API]**
-- **S5** — Live HTTP probes, 2026-09-01: `https://ecsarxiv.org/` (200, 4,207 B, redirected to
-  `https://osf.io/preprints/ecsarxiv/`); `https://osf.io/preprints/ecsarxiv/discover` (200,
-  4,207 B); **negative control** `https://osf.io/preprints/zzzznotreal/` (**200, 4,207 B**);
-  **API negative control** `https://api.osf.io/v2/providers/preprints/zzzznotreal/` (**404,
-  61 B**); `https://osf.io/oai?verb=Identify` and `https://osf.io/oai/?verb=Identify` (200,
-  `text/html`, SPA shell). **[WEB]**
-- **S6** — `https://api.openalex.org/sources?filter=display_name.search:ecsarxiv` →
-  `https://openalex.org/S4306402531`, `ECSarXiv (OSF Preprints)`, `works_count: 17`.
-  Retrieved 2026-09-01. **[API]**
diff --git a/research/preprint-repositories/engrxiv.md b/research/preprint-repositories/engrxiv.md
deleted file mode 100644
index 9533f1b..0000000
--- a/research/preprint-repositories/engrxiv.md
+++ /dev/null
@@ -1,400 +0,0 @@
-# engrXiv (Engineering Archive) — preprint repository record
-
-- **URL:** https://engrxiv.org/ (OAI base `https://engrxiv.org/oai`)
-- **Operator:** **Open Engineering Inc.** ("openENGR"), a US 501(c)(3) non-profit, which
-  also operates *The Journal of Open Engineering* (S1, S7). Directed since launch by
-  **Devin R. Berg**, professor of mechanical engineering, University of Wisconsin–Stout
-  (S1). Funded by the "Engineering Archive Membership Circle" — institutional/library
-  subscriptions at **$500/year** (S3).
-- **Discipline scope:** *as advertised* — the broad spectrum of engineering disciplines
-  (civil, mechanical, electrical, aerospace, materials, chemical, engineering education).
-  *As actually used* — mechanical/civil/structural and applied-ML-in-engineering dominate;
-  electrical/electronic content exists but is thin (§2, §6).
-- **Launched:** **July 2016** (beta) (S1); earliest deposit dated **2016-07-27** (S5).
-  **Status:** active.
-- **Platform history:** OSF Preprints (Center for Open Science), 2016 → **19 January 2022**;
-  self-hosted **PKP Open Preprint Systems** since (§1).
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-engrXiv is a small, volunteer-moderated, community-run preprint server for engineering. It
-was set up in 2016 by engineering academics and engineering librarians who wanted the
-discipline to have the thing physics had had since 1991 and biology had just got. It is
-explicitly modelled on arXiv — engrXiv states it uses the arXiv name **under trademark
-licence from Cornell University**, and warns that the licence "should not be understood to
-indicate endorsement of content on engrXiv by Cornell University or arXiv" (S1).
-
-**The migration off OSF is confirmed and dated.** engrXiv originally ran on the Center for
-Open Science's OSF Preprints platform (its legacy DOIs still read
-`10.31224/osf.io/xjpcm`). The OSF provider record for `engrxiv` is *still live* and its
-description field now reads, verbatim:
-
-> "The Engineering Archive will be closed to new preprint submissions temporarily and moved
-> to https://engrxiv.org/ beginning Wednesday, January 19th." — `allow_submissions: false` (S6)
-
-The year is **2022**: 19 January 2022 was a Wednesday, and the new PKP instance reports an
-OAI-PMH `earliestDatestamp` of **2022-01-21T14:36:57Z** (S5) — the moment the migrated
-corpus was written into the new database. The current site runs **Open Preprint Systems
-3.3.0.13** (from the `<meta name="generator">` tag, S2). The old OSF landing page
-`https://osf.io/preprints/engrxiv/` still returns HTTP 200 but is a redirect target of the
-`engrxiv.org` domain only in the API sense — the *domain* `engrxiv.org` now serves OPS
-directly, not OSF (S2, S6).
-
-**Reason for the move: [NOT-VERIFIED] in the operator's own words.** I could not retrieve a
-statement from engrXiv explaining *why* they left OSF. The engrXiv blog index (S3) lists
-posts from 2024–2025 only; older posts announcing the move were not reachable in this pass.
-What is verifiable is that they moved to software they control (PKP OPS is open source and
-self-hostable) and away from a platform whose preprint service COS has since de-emphasised
-[INF]. Do not repeat a funding-crisis or platform-shutdown story without a source.
-
-The corpus was **carried across, not abandoned**: the OPS instance holds records dated back
-to 2016 with their original OSF-issued DOIs (§3).
-
-## 2. Scope and subject taxonomy
-
-engrXiv does **not** publish a compact category-code taxonomy the way arXiv does. Its
-OAI-PMH `ListSets` exposes exactly two sets — `engrxiv` (Engineering Archive) and
-`engrxiv:PRE` (Preprints) (S5) — so there is no machine-readable subject partition to
-enumerate. Authors "select their own categories from our subject taxonomy" and moderators
-check the choice is "plausible" (S1), but the taxonomy is not exposed via OAI.
-
-What *is* exposed is free-text `dc:subject` keywords. Harvesting all 5,871 records
-(2026-09-01, S5), the most common author keywords are:
-
-| Keyword | Records | | Keyword | Records |
-|---|---|---|---|---|
-| machine learning | 211 | | sustainability | 35 |
-| deep learning | 97 | | uncertainty quantification | 35 |
-| artificial intelligence | 82 | | finite element analysis | 34 |
-| additive manufacturing | 81 | | reinforcement learning | 32 |
-| optimization | 53 | | internet of things | 32 |
-| 3D printing | 50 | | structural health monitoring | 32 |
-| simulation | 44 | | civil engineering | 31 |
-| CFD | 42 | | mechanical engineering | 30 |
-| renewable energy | 41 | | aerodynamics | 30 |
-| robotics | 39 | | biomechanics | 29 |
-
-**What the scope explicitly excludes** is as informative as what it includes. The stated
-moderation policy rejects (S1):
-
-- works claiming **free energy or perpetual motion**;
-- works in **mathematics, theoretical physics, computer science, information technology or
-  cybersecurity without a strong engineering connection**;
-- work whose only "engineering" content is applying an LLM to something — "the application
-  of AI or LLM tools to a particular situation does not necessarily constitute engineering."
-
-So an engineer looking for `cs.AR`-style computer-architecture preprints is in the wrong
-place by policy, not just by accident.
-
-## 3. Size and growth
-
-| Measure | Value | Date | Source |
-|---|---|---|---|
-| OAI-PMH `completeListSize` (all records, live server) | **5,871** | 2026-09-01 | [API] S5 |
-| Crossref `prefixes/10.31224/works` total | 5,857 | 2026-09-01 | [API] S8 |
-| Preprints remaining on the legacy OSF provider | 2,033 | 2026-09-01 | [API] S6 |
-| OpenAlex source `EngrXiv (OSF Preprints)` `works_count` | **28** | 2026-09-01 | [API] S9 |
-
-**Record the conflicts rather than resolving them.**
-
-- *5,871 vs 5,857*: the Crossref `/prefixes/` endpoint filters by DOI-**owner** prefix, and
-  it returned some records with `10.31235/...` (SocArXiv) DOIs — both prefixes belong to
-  Crossref member 15934, Center for Open Science (S8). Every one of the 5,871 identifiers in
-  the OAI dump does start with `10.31224` (S5), so **5,871 is the number to use** and the
-  Crossref prefix figure should not be quoted for engrXiv.
-- *2,033 on OSF*: this is the legacy corpus that COS still serves. It matches the pre-2022
-  OAI records almost exactly (2016–2021 sums to 2,063, S5) [INF]. Content was **copied**,
-  not moved — both copies exist, with the same DOIs.
-- *OpenAlex 28*: OpenAlex's `EngrXiv (OSF Preprints)` source
-  (`https://openalex.org/S4306401210`) records 28 works. That is a catastrophic
-  under-count, presumably because OpenAlex still models engrXiv as an OSF sub-provider and
-  never picked up the OPS instance (S9). **Do not use OpenAlex to size or search engrXiv.**
-
-**Deposits by year** (from `dc:date` in the OAI harvest, S5):
-
-| 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 (to 09-01) |
-|---|---|---|---|---|---|---|---|---|---|---|
-| 38 | 112 | 227 | 409 | 657 | 620 | 447 | 497 | 635 | 1,151 | 1,078 |
-
-**DOI syntax splits the corpus cleanly**: 2,111 records carry legacy
-`10.31224/osf.io/XXXXX` DOIs and 3,760 carry OPS-era `10.31224/NNNN` DOIs (S5). Both
-resolve (§8).
-
-**Scale check against arXiv.** engrXiv's *entire lifetime output* is 5,871 items. arXiv's
-electrical-engineering-and-systems-science categories alone, queried the same day (S10):
-
-| arXiv category | Items |
-|---|---|
-| `eess.SY` (Systems and Control) | 47,937 |
-| `eess.SP` (Signal Processing) | 41,815 |
-| `cs.AR` (Hardware Architecture) | 8,932 |
-
-**engrXiv is roughly one eighth the size of `eess.SY` alone, and smaller than `cs.AR`.**
-Be blunt about this: for electrical, electronic, signal-processing, control or
-computer-architecture work, arXiv is the primary venue and engrXiv is a distant secondary.
-engrXiv's genuine constituency is the parts of engineering arXiv never absorbed — civil,
-structural, mechanical, manufacturing, engineering education — where it is one of very few
-options.
-
-## 4. Screening and moderation — what gets in
-
-engrXiv runs **pre-moderation by volunteer moderators**, and unusually for a small server it
-publishes a detailed, honest policy (S1, S4). Quoting the substance:
-
-- **Turnaround target:** "Subject to volume demands, we expect to review each paper
-  submitted for moderation within 3 business days" (S1).
-- **What moderation is not:** "We do not assess the quality of the work or verify copyright
-  status… acceptance is not a statement about research quality or copyright status" (S1).
-- **Grounds for acceptance:** scholarly content; in a supported research area; plausibly
-  categorised; compliant with copyright law (author asserts rights at submission); in a
-  language they can moderate (non-English submissions must carry an English title and
-  abstract) (S1).
-- **Rejection is appealable** to `director@engrxiv.org`, but "submissions may be rejected by
-  the moderator for any reason" (S1).
-- **Deposits are permanent.** The submission checklist requires the author to confirm: "I
-  understand that once it has been posted publicly, my submission is permanent and cannot be
-  withdrawn" (S4).
-
-### The AI policy — the most substantive thing on this server
-
-engrXiv publishes a detailed **AI Policy** (S11) that is worth reading in full if you care
-about preprint hygiene anywhere. Acceptable LLM use: translation, literature search and
-idea organisation *with human supervision*, copy-editing, machine-assisted data analysis,
-dictation — all of which **must be disclosed**. Unacceptable: verbatim generated text, fake
-data, LLMs as co-authors or as "interviewees", fabricated information to mislead
-moderators, and "entire papers produced by AI generation with no human-generated components
-beyond prompts." They also list explicit red flags — "unsubstantiated grand theories" with
-"fanciful equations", "integration of multiple major theories into definitive new
-'paradigms'… without substantive engagement", papers "written in many short sections, often
-including bullet-point lists and numbered paragraphs" (S11).
-
-**And they publish the consequences.** From the operator's own blog (S3):
-
-- 2025-08-26, *The challenge of AI slop for preprint servers*: submissions grew "from an
-  average of 60 submissions per month to closer to 200"; often from "so-called 'independent
-  researchers' with no institutional affiliation… They may or may not be real people."
-- 2025-12-31, *Wrap of 2025*: posted preprints rose "to nearly 1200, up from about 640 in
-  2024"; "this has resulted in **roughly half of submissions being declined** as the
-  moderation team has had to become more aggressive."
-
-Those numbers **cross-check against the registry**: the OAI harvest gives 1,151 for 2025 and
-635 for 2024 (S5) against the blog's "nearly 1200" and "about 640". The operator's public
-statements and the machine-readable record agree — a good sign for this server's honesty
-[INF].
-
-## 5. Reliability — what you can and cannot trust
-
-**A deposit guarantees:** a Crossref DOI, a datestamp, a permanent record (no withdrawal),
-and that a human moderator glanced at it within a few days. That is all.
-
-**It does not guarantee** peer review, correctness, or copyright cleanliness — the operator
-says so explicitly (§4).
-
-**Eventual-publication rate: [NOT-VERIFIED].** engrXiv's OAI `oai_dc` output carries no
-`dc:relation` linking to a published version, and unlike TechRxiv, Crossref
-`is-preprint-of` relations are not systematically populated for `10.31224` records. I found
-no scientometric study measuring engrXiv's publication rate.
-
-**Known failure modes, ranked by how much they should worry you:**
-
-1. **Generative-AI slop is the dominant present risk**, on the operator's own account
-   (§4) — half of 2025 submissions declined, and by implication some fraction of the
-   accepted 1,151 slipped through. Deposits from 2025 onward warrant more scepticism than
-   deposits from 2019.
-2. **No withdrawal.** Bad or plagiarised work stays up.
-3. **Author-chosen categories** with only a plausibility check.
-4. **Citation gaming** — the operator names this as the *historic* spam motive: "attempts
-   to artificially exploit Google Scholar indexing to make one's academic profile look more
-   prestigious than is deserved" (S3).
-
-**How to sanity-check an individual engrXiv paper.** Look at the deposit date (pre-2023 is
-lower-risk); check whether the author has an institutional affiliation and an ORCID
-(engrXiv names ORCID identity as a moderation criterion, S11); search the exact title for a
-journal version; and read the reference list for hallucinated citations — the specific
-failure mode engrXiv's own policy tells you to look for.
-
-## 6. What you actually find there — examples
-
-Titles verified present in the 2026-09-01 OAI harvest, with their DOIs (S5). This is a
-deliberately hardware-leaning selection; it is *not* representative of the corpus, which is
-mostly mechanical/civil.
-
-- *A Review of Tunable Inductors for Power Electronics: Techniques and Applications*,
-  2024-06-30 — `10.31224/3786`
-- *Power Circuit AI: Designing Power Electronic Circuits for Motor Drives with Generative
-  Artificial Intelligence*, 2026-04-02 — `10.31224/6706`
-- *A Power and Area Efficient CMOS Bandgap Reference Circuit with an Integrated
-  Voltage-Reference Branch*, 2019-08-08 — `10.31224/osf.io/4x9g8`
-- *EMF Inspector: An Open-Source Physics-Based Electromagnetic Interference Estimation Tool
-  for KiCad*, 2026-06-01 — `10.31224/7226` — a genuinely useful open-hardware EDA artifact
-- *Dry Film Photoresist Application to a Printed Circuit Board (PCB) Using a Maskless
-  Photolithography Process*, 2020-07-28 — `10.31224/osf.io/27f49`
-- *Backscatter Ex-Nihilo: Single-component, Fully-passive Backscattering for
-  Microcontrollers*, 2020-10-09 — `10.31224/osf.io/p57sr`
-- *Modelling Gene-Protein-Reaction Associations on an FPGA*, 2019-06-03 —
-  `10.31224/osf.io/u48bc`
-- *Study of FPGA logic reconfiguration during operation*, 2022-10-20 — `10.31224/2632`
-- *Reinforcement Learning based Intelligent Semiconductor Manufacturing Applied to Laser
-  Annealing*, 2022-07-05 — `10.31224/2449`
-- *Understanding Stability of Low-Inertia Systems*, 2019-02-18 — `10.31224/osf.io/jwzrq` —
-  grid-stability work, one of the more-cited electrical items (19 Crossref citations, S8)
-- *Fracture Toughness of Li\_xSi Alloys in Lithium Ion Battery*, 2019-04-15 —
-  `10.31224/osf.io/zqadm`
-
-**Hardware-adjacent keyword frequencies across all 5,871 titles** (S5), which is the
-clearest statement of how thin the electronics layer is: `sensor` 95, `robot` 85,
-`battery` 43, `circuit` 38, `embedded` 22, `antenna` 17, `FPGA` 11, `Arduino` 6, `PCB` 4,
-`microcontroller` 4, `semiconductor` 4, `power electronic` 3, `inverter` 2, `Raspberry` 1.
-Against that: `structural` 96, `concrete` 88, `finite element` 50, `additive manufactur` 43.
-
-## 7. Landmark papers
-
-**engrXiv hosts no landmark software, distributed-systems, database, electronics or
-security papers.** No paper on this server changed a field. Its most-cited deposits (S8)
-are a 2020 COVID X-ray CNN paper (`10.31224/osf.io/wx89s`, 55 Crossref citations), a
-COVID computer-vision survey (`10.31224/osf.io/yt9sx`, 43), a deep-learning activation
-function survey (`10.31224/2245`, 26), a cultured-meat techno-economic analysis
-(`10.31224/osf.io/795su`, 23) and a material-point-method simulation paper
-(`10.31224/osf.io/e24rb`, 23). Respectable, ordinary engineering literature; nothing
-field-defining. The table this section normally carries is deleted.
-
-## 8. Access, APIs and bulk retrieval
-
-**Fully open and pleasant to script.** No Cloudflare challenge, no rate-limit encountered,
-no user-agent games needed (a plain `curl` with a research UA worked throughout).
-
-**OAI-PMH** — the primary bulk interface, base URL `https://engrxiv.org/oai`:
-
-```bash
-curl 'https://engrxiv.org/oai?verb=Identify'
-curl 'https://engrxiv.org/oai?verb=ListSets'
-curl 'https://engrxiv.org/oai?verb=ListRecords&metadataPrefix=oai_dc'   # then follow resumptionToken
-```
-
-`Identify` (2026-09-01, S5) reports: `repositoryName` **Engineering Archive**;
-`adminEmail` `director@engrxiv.org`; `earliestDatestamp` **2022-01-21T14:36:57Z**;
-`deletedRecord` **persistent**; `granularity` `YYYY-MM-DDThh:mm:ssZ`; gzip/deflate
-compression supported. A full `ListRecords` harvest of 5,871 records completed in well
-under a minute. Note the `dc:title` elements carry an `xml:lang` attribute — naive
-`<dc:title>` regexes return nothing.
-
-**HTTP probes and the negative control** (2026-09-01, S2):
-
-| Path | Code | Bytes |
-|---|---|---|
-| `/` | 200 | 22,323 |
-| `/about` | 200 | 17,815 |
-| `/about/submissions` | 200 | 10,579 |
-| `/preprints` | 200 | 42,575 |
-| `/ai-policy` | 200 | 11,954 |
-| `/oai?verb=Identify` | 200 | 1,887 |
-| **`/definitely-not-a-real-page-zzz9999`** (negative control) | **404** | **22** |
-| `/index/preprints` (plausible-looking but wrong) | 404 | 22 |
-
-A 22-byte 404 body is unmistakable, so on this host HTTP status is trustworthy — unlike
-osf.io (see the ECSarXiv record) or techrxiv.org.
-
-**DOI resolution, both syntaxes, plus negative control** (S12):
-
-| Probe | Result |
-|---|---|
-| `https://doi.org/10.31224/osf.io/xjpcm` (legacy) | 302 → `https://engrxiv.org/index.php/engrxiv/preprint/view/1` |
-| `https://doi.org/10.31224/3786` (OPS-era) | 302 → `https://engrxiv.org/preprint/view/3786/version/5229` |
-| **`https://doi.org/10.31224/9999999999`** | **404** |
-
-Legacy OSF-issued DOIs survived the migration and now point at the OPS instance — a clean
-result, and better than most platform migrations manage.
-
-**Crossref** works too, with the owner-prefix caveat in §3:
-`https://api.crossref.org/prefixes/10.31224/works?rows=1000&cursor=*`. Crossref records
-show `publisher: Center for Open Science`, `member: 15934`, `group-title: engrXiv` (S8).
-
-**OpenAlex is unusable here** — see §3.
-
-## 9. Licensing and reuse
-
-Authors choose. Licence URLs recorded in Crossref for a 3,000-record sample of prefix
-`10.31224` (2026-09-01, S8):
-
-| Licence | Records in sample |
-|---|---|
-| CC BY 4.0 (two URL spellings combined) | 2,023 |
-| *(no licence recorded)* | 633 |
-| CC0 1.0 | 212 |
-| CC BY-NC 4.0 | 114 |
-| CC BY-NC-ND 4.0 | 11 |
-| CC BY-NC-SA 4.0 | 3 |
-
-≈67% CC BY, but note that **21% of records carry no licence statement at all** [INF] — for
-those, you have no reuse permission beyond fair dealing, whatever the site's general tone.
-
-The author agreement grants engrXiv "the irrevocable, non-exclusive rights to reproduce,
-publicly display and publish my article… in perpetuity" (S1, S4) — non-exclusive, so authors
-retain the right to publish elsewhere, which is the whole point of a preprint server.
-
-Text and data mining: not restricted by any robots directive encountered, and the OAI
-endpoint is explicitly there for harvesting.
-
-## 10. Caveats and controversies
-
-- **It is small.** 5,871 lifetime deposits against ~48,000 in `eess.SY` alone (§3). Absence
-  from engrXiv means nothing.
-- **The corpus exists in two places** with the same DOIs — 5,871 records on OPS, 2,033 on
-  OSF. Deduplicate if you aggregate.
-- **Discovery infrastructure has not caught up**: OpenAlex sees 28 works (§3). If you build
-  on third-party indexes you will silently miss this server.
-- **Generative-AI submissions are an active, acknowledged crisis** (§4). The operator is
-  candid and is tightening moderation, but volunteer capacity is the binding constraint —
-  they explicitly say they are "looking to expand our volunteer moderation team in 2026" (S3).
-- **Nothing can be withdrawn** (§4). A retracted-elsewhere paper stays on engrXiv.
-- **Funding is thin**: $500/year institutional memberships (S3). This is a server that
-  could disappear; archive anything you depend on.
-- **The reason for the OSF exit is not documented here** (§1) — [NOT-VERIFIED].
-
-## 11. Sources
-
-- **S1** — `https://engrxiv.org/about` ("About the Server", including General Information,
-  Purpose of Moderation, Moderation Policy, Moderation Procedure, Author Agreement, and the
-  arXiv trademark-licence notice). Retrieved 2026-09-01. **[DOC]**
-- **S2** — Live HTTP probes of `https://engrxiv.org/`: `/`, `/about`, `/about/submissions`,
-  `/about/editorialTeam`, `/preprints`, `/search/search`, `/ai-policy`, `/announcement`,
-  `/index/preprints`, `/oai?verb=Identify`, and the negative control
-  `/definitely-not-a-real-page-zzz9999`. Includes the `<meta name="generator"
-  content="Open Preprint Systems 3.3.0.13">` tag. Retrieved 2026-09-01. **[WEB]**
-- **S3** — `https://blog.engrxiv.org/` — posts *Wrap of 2025* (2025-12-31) and *The
-  challenge of AI slop for preprint servers* (2025-08-26). Retrieved 2026-09-01. **[DOC]** —
-  supports the submission-rate figures, the ~50% decline rate, the $500 Membership Circle,
-  and the citation-gaming remark.
-- **S4** — `https://engrxiv.org/about/submissions` (Submission Preparation Checklist,
-  Copyright Notice, Privacy Statement). Retrieved 2026-09-01. **[DOC]**
-- **S5** — engrXiv OAI-PMH, `https://engrxiv.org/oai`: `verb=Identify`, `verb=ListSets`, and
-  a complete `verb=ListRecords&metadataPrefix=oai_dc` harvest (5,871 records; dumped to
-  scratch as `engrxiv_recs.json`). Retrieved 2026-09-01. **[API]** — supports the total,
-  the per-year table, the DOI-syntax split, the keyword frequencies, the example titles and
-  the `Identify` parameters.
-- **S6** — OSF JSON:API: `https://api.osf.io/v2/providers/preprints/engrxiv/` (the migration
-  notice in `description`, `allow_submissions: false`, `reviews_workflow: pre-moderation`,
-  steering-committee list) and
-  `https://api.osf.io/v2/preprints/?filter[provider]=engrxiv&meta[]=total` (`total: 2033`).
-  Retrieved 2026-09-01. **[API]**
-- **S7** — Wikipedia REST summary, `https://en.wikipedia.org/api/rest_v1/page/summary/EngrXiv`.
-  Retrieved 2026-09-01. **[COM]** — supports "launched July 2016", the 2019 incorporation
-  into Open Engineering Inc, and the Menomonie, Wisconsin base. (Wikipedia gives no size
-  figure to conflict with §3.)
-- **S8** — Crossref REST API: `https://api.crossref.org/prefixes/10.31224/works`
-  (`rows=0&facet=…`; `sort=is-referenced-by-count`; a 3,000-record `select=DOI,license`
-  sample) and `https://api.crossref.org/works/10.31224/osf.io/xjpcm`. Retrieved 2026-09-01.
-  **[API]** — supports the 5,857 conflict, the owner-prefix contamination, the licence
-  table, and the most-cited list.
-- **S9** — `https://api.openalex.org/sources?filter=display_name.search:engrxiv` →
-  `S4306401210`, `EngrXiv (OSF Preprints)`, `works_count: 28`. Retrieved 2026-09-01. **[API]**
-- **S10** — arXiv API, `https://export.arxiv.org/api/query?search_query=cat:<cat>&max_results=1`,
-  reading `<opensearch:totalResults>` for `eess.SY` (47,937), `eess.SP` (41,815),
-  `cs.AR` (8,932). Retrieved 2026-09-01. **[API]** — note this endpoint only works over
-  **https**; the `http://export.arxiv.org` form returned an unparseable response.
-- **S11** — `https://engrxiv.org/ai-policy`. Retrieved 2026-09-01. **[DOC]**
-- **S12** — `doi.org` HEAD probes: `10.31224/osf.io/xjpcm`, `10.31224/3786`, and the
-  negative control `10.31224/9999999999` (404). Retrieved 2026-09-01. **[WEB]**
diff --git a/research/preprint-repositories/figshare.md b/research/preprint-repositories/figshare.md
deleted file mode 100644
index 7a88f8d..0000000
--- a/research/preprint-repositories/figshare.md
+++ /dev/null
@@ -1,345 +0,0 @@
-# figshare — preprint repository record
-
-- **URL:** https://figshare.com/
-- **Operator:** figshare, a portfolio company of **Digital Science**, which is a subsidiary
-  of **Holtzbrinck / Springer Nature** (S6) [WEB]. Founded by Mark Hahnel.
-- **Discipline scope:** generalist / multidisciplinary. All output types, no subject gate.
-- **Launched:** **January 2011**; relaunched with Digital Science backing January 2012
-  (S6) [WEB] · **Status:** active
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-figshare is a **generalist repository** in the same category as Zenodo: upload anything,
-get a DOI, no review. It began as a personal tool Mark Hahnel built to publish the figures,
-videos and negative results generated during his stem-cell PhD that no journal would take
-(S6) [WEB]. That origin still shows in the product — figshare's native unit is the
-*figure*, *dataset* or *media object*, not the paper.
-
-The more consequential fact, and the reason this record exists, is that **figshare is
-infrastructure**. Far more figshare exists than figshare.com. The same platform is sold as:
-
-- **figshare for Institutions** — white-labelled institutional repositories, frequently on
-  the university's *own domain* so the figshare branding is invisible.
-- **figshare for Publishers** — supplementary-data hosting behind journals.
-- **the substrate under whole preprint servers** — IEEE's TechRxiv, ACS's ChemRxiv and
-  SAGE's Advance were all built on it (§4).
-
-That last role makes figshare a systemic dependency of the preprint ecosystem, and makes
-its churn a durability question rather than a commercial one (§5.2).
-
-## 2. Scope and item taxonomy
-
-figshare's OAI-PMH `ListSets` exposes **30 sets**, of which 25 are "Article type" sets —
-this is the authoritative item vocabulary (S3) [API], retrieved 2026-09-01:
-
-`figure` · `media` · `dataset` · `poster` · `journal contribution` · `presentation` ·
-`thesis` · `software` · `online resource` · **`preprint`** · `book` ·
-`conference contribution` · `chapter` · `peer review` · `educational resource` · `report` ·
-`standard` · `composition` · `funding` · `physical object` · `data management plan` ·
-`workflow` · `monograph` · `performance` · `event`
-
-Note that `preprint` is **one of twenty-five types**, and `software`, `workflow` and
-`data management plan` are first-class alongside it. Like Zenodo, figshare is not a
-preprint server that also does other things; it is a general repository in which preprints
-are a minority type.
-
-Distribution of the 100 most recently published items (S1) [API], as a rough indicator
-only — this is a single snapshot of the newest items, not the corpus:
-
-| Type | Count (of 100) |
-|---|---|
-| journal contribution | 49 |
-| dataset | 28 |
-| report | 5 |
-| conference contribution | 4 |
-| thesis | 4 |
-| figure | 4 |
-| preprint | 2 |
-| chapter | 2 |
-| software | 1 |
-| poster | 1 |
-
-## 3. Size and growth
-
-**figshare does not publish a machine-readable total, and its own APIs will not give you
-one.** Two independent attempts failed (§6):
-
-- The REST search API uses **opaque cursor pagination** (`x-cursor` header) with no total
-  in the response (S1) [API].
-- OAI-PMH `ListIdentifiers` returns a `resumptionToken` **without a `completeListSize`
-  attribute** (S3) [API], so the standard OAI counting trick is unavailable.
-
-So I obtained counts from **DataCite**, where figshare registers its DOIs. Retrieved
-2026-09-01 (S2) [API]:
-
-| DataCite client | DOIs | What it is |
-|---|---|---|
-| `figshare.ars` | **4,106,613** | figshare Academic Research System — the main figshare.com |
-| `si.figshare` | 5,481 | Figshare for Institutions |
-| `figshare.asha` | 4,315 | ASHA Publications instance |
-| `figshare.orcid` | 2,015 | ORCID integration |
-| `figshare.plus` | 762 | Figshare+ |
-| `figshare.sage` | **0** | SAGE instance — see §5.2 |
-| `figshare.test` | 17 | test datacentre |
-
-A prefix query for `10.6084` (figshare's main prefix) independently returned
-**4,106,628** at a slightly later moment (S2) [API] — the ~15-record difference across a
-few minutes is live growth, not disagreement.
-
-**The federation is larger than figshare.com.** A DataCite client search for "figshare"
-returns **33 clients** (S2) [API]. Summing the 25 retrieved gives **4,244,934** DOIs.
-Institutional instances carry their own prefixes and client IDs, and several do not have
-"figshare" in the repository name at all:
-
-| Client | DOIs | Institution |
-|---|---|---|
-| `swin.repo2` | 37,062 | Swinburne University of Technology |
-| `au.ir` | 33,882 | American University Research Archive |
-| `bl.lboro` | 25,789 | Loughborough University Research Repository |
-| `dk.dtic` | 6,369 | DTU Data |
-| `bl.shef` | 5,378 | ORDA — University of Sheffield |
-| `ardcx.deakin` | 4,776 | Deakin University |
-| `mmu.fig` | 4,179 | Manchester Metropolitan University |
-| `snd.su` | 2,029 | Stockholm University Figshare Repository |
-
-> **Total corpus size: [NOT-VERIFIED].** ~4.1M for figshare.com proper is well evidenced;
-> the true federation total is unknown because (a) the client list is not exhaustively
-> enumerable by name-matching, and (b) publisher instances mint DOIs under *the publisher's*
-> prefix, not figshare's, and are therefore invisible to any figshare-centric count. Do not
-> quote a single "figshare size" figure.
-
-**Evidence for (b):** among 100 newest items the DOI prefixes included `10.1021` (ACS, 11
-items), `10.3389` (Frontiers, 4), `10.1016` (Elsevier, 2), `10.1038` (Springer Nature, 1)
-and `10.1177` (SAGE, 1) alongside `10.6084` (33) and institutional prefixes `10.26187`
-(17), `10.25439` (4), `10.26181` (3), `10.25447` (1), `10.25909` (1) (S1) [API]. Public
-URLs in the same sample included `https://dro.deakin.edu.au/...` and
-`https://frontiersin.figshare.com/...` — a figshare-powered repository on a university's
-own domain, and a publisher-branded subdomain, both served by the same API.
-
-**Wikipedia conflict:** the *List of preprint repositories* records figshare's size as
-*"unknown"* (S7) [WEB]. That is at least honest, and consistent with my finding — but the
-figshare.com figure of ~4.1M *is* obtainable via DataCite and can now be cited.
-
-## 4. Screening and moderation — what gets in
-
-**No peer review and no subject screening.** figshare is a self-deposit generalist
-repository; items are published by the depositor and receive a DOI immediately.
-
-**[NOT-VERIFIED]** I did not retrieve figshare's own published moderation/curation policy
-document. figshare.com was reachable via its API throughout, but I did not locate and load
-a policy page equivalent to Zenodo's General Policies. **Do not assume figshare's terms
-match Zenodo's** — treat the specifics of its takedown, curation and retention rules as
-unverified in this record.
-
-One structural point *is* verifiable: on **institutional** instances the customer
-institution, not figshare, controls curation policy. So "deposited on figshare" does not
-denote a single screening regime — it denotes a software platform that may sit behind
-anything from an uncurated public upload to a librarian-mediated institutional deposit.
-[INF]
-
-## 5. Reliability — what you can and cannot trust
-
-### 5.1 What a figshare DOI means
-
-A DOI, a timestamp, and hosting. **Not review, not validation, not curation** (§4). The
-same warning that applies to Zenodo applies here: the identifier is plumbing.
-
-An additional figshare-specific caution: because the platform is white-labelled, **you
-often cannot tell from the URL that you are looking at figshare**. `dro.deakin.edu.au` is
-figshare. Assessing "who stands behind this record" requires identifying the operator of
-the *instance*, not the platform.
-
-### 5.2 The infrastructure-churn finding — the durability point
-
-figshare has powered several major publisher preprint servers. Their subsequent movement
-is the most useful durability evidence in this record. All figures retrieved from Crossref
-2026-09-01 (S4) [API]:
-
-| Server | Prefix | Crossref owner | Works | Status found |
-|---|---|---|---|---|
-| **TechRxiv** | 10.36227 | Institute of Electrical and Electronics Engineers (IEEE) | 30,954 | **migrated off figshare** |
-| **ChemRxiv** | 10.26434 | American Chemical Society (ACS) | 55,400 | migrated off figshare |
-| **SAGE Advance** | 10.31124 | SAGE Publications | 4,417 | still on figshare URLs; no 2026 deposits |
-
-**How the TechRxiv migration is visible in the data.** Resolving two TechRxiv DOIs
-2026-09-01 (S5) [API]:
-
-- Old: `10.36227/techrxiv.14420315` →
-  `www.techrxiv.org/articles/preprint/Smart_Assistant_for_Accident_Prevention_and_Rescue/14420315`
-  — the **figshare URL grammar** (`/articles/<type>/<title-slug>/<numeric-id>`), with a
-  bare 8-digit figshare item ID.
-- New: `10.36227/techrxiv.176281113.30584908/v1` →
-  `www.techrxiv.org/doi/full/10.36227/techrxiv.176281113.30584908/v1`
-  — a **completely different grammar** (`/doi/full/…/v1`) with a paired-numeric DOI suffix.
-
-That second pattern is byte-for-byte the pattern used by Authorea
-(`www.authorea.com/doi/full/10.22541/au.175225950.03002018/v1`, S4) [API]. TechRxiv also
-returns the *same* Cloudflare-style 403 body size as authorea.com and essopenarchive.org
-(5,620 / 5,620 / 5,622 bytes, S5) [WEB]. The combined evidence is that **TechRxiv moved
-from figshare onto the Atypon/Wiley "Authorea" stack**. [INF]
-
-ChemRxiv shows the same `/doi/full/` grammar
-(`chemrxiv.org/doi/full/10.26434/chemrxiv-2025-g5cqm-v2`, S4) [API] and is likewise no
-longer on figshare URLs. [INF]
-
-**The good news for durability:** the *old* figshare-era TechRxiv DOI still resolves, and
-still resolves to a figshare-shaped path on the new host. Legacy identifiers were carried
-across rather than broken. That is the outcome you want, and it did not happen by accident.
-
-**SAGE Advance** is the counter-case worth watching: its DOIs still resolve to
-`advance.sagepub.com/articles/preprint/…` (figshare grammar), and Crossref shows deposits
-2018–2025 (167 / 641 / 982 / 819 / 494 / 410 / 517 / 387) with **zero works dated 2026** as
-of 2026-09-01 (S4) [API]. That is consistent with a server that has stopped accepting new
-material, though I did not obtain a closure announcement — **[NOT-VERIFIED]** as to whether
-Advance is formally discontinued.
-
-> **A correction I had to make mid-research, recorded as a method note.** The DataCite
-> client `figshare.sage` shows **0** DOIs, which looks like evidence that SAGE's instance is
-> dead. It is not: SAGE Advance registers with **Crossref** (4,417 works), not DataCite.
-> A zero in one registry is not absence. Always check both registries before concluding a
-> platform has no content.
-
-### 5.3 How to sanity-check a figshare item
-
-1. Identify the **instance** (public figshare.com, institutional, or publisher) from the
-   host and DOI prefix — these have different curation regimes.
-2. Check `defined_type_name`: a `preprint` and a `journal contribution` are different
-   claims.
-3. Check the licence field per item (§8) — it varies, including non-commercial terms.
-4. If the item is a supplement, find the parent article; the supplement inherits none of
-   the parent's peer review by being adjacent to it.
-
-## 6. Access, APIs and bulk retrieval
-
-**REST API** — `https://api.figshare.com/v2/`, no key needed for public reads (S1) [API]:
-
-- `POST /v2/articles/search` with a JSON body (`{"page_size":100}`) — **works**, HTTP 200.
-- `GET /v2/articles/<id>` — full item record including `license`, `defined_type_name`,
-  `doi`, `is_public`.
-- `GET /v2/licenses` — the licence vocabulary (§8).
-- **No total count is returned anywhere.** Pagination is by opaque `x-cursor` header.
-
-**OAI-PMH** — `https://api.figshare.com/v2/oai` (S3) [API]. `Identify` returns:
-
-```xml
-<repositoryName>figshare</repositoryName>
-<earliestDatestamp>1800-01-01T00:00:00Z</earliestDatestamp>
-<deletedRecord>transient</deletedRecord>
-<granularity>YYYY-MM-DDThh:mm:ssZ</granularity>
-```
-
-Two observations. `earliestDatestamp` of **1800-01-01** is a placeholder, not a real
-date — do not use it for anything. `deletedRecord: transient` means figshare **may** report
-deletions but does not guarantee their persistence, so an OAI-based mirror can silently
-drift out of sync. (Contrast Zenodo, which declares `no`.)
-
-`ListSets` returns 30 sets (§2). `ListIdentifiers` returns a resumption token but,
-as noted, **no `completeListSize`**.
-
-**Negative controls** (S1, S3) [API]:
-
-| Probe | Result |
-|---|---|
-| `stats.figshare.com/total/views/article` | HTTP **400**, `{"code":"InvalidParams"…"Unknown or usupported item type"}` — endpoint rejects bad params properly |
-| `oai?verb=Identify` vs a real fetch | valid XML, correct structure |
-| DataCite client-name search for a real vs absent term | see §5.2 method note |
-
-## 7. Landmark papers
-
-figshare hosts no landmark software, systems or electronics *papers* that I could verify as
-originating there. Its significance to this knowledge base is **as infrastructure**
-(§1, §5.2), not as a venue. No table.
-
-## 8. Licensing and reuse
-
-**Author-chosen from a controlled list.** The `GET /v2/licenses` endpoint returns the
-global vocabulary (S1) [API], retrieved 2026-09-01:
-
-| Licence | URL |
-|---|---|
-| CC BY 4.0 | creativecommons.org/licenses/by/4.0/ |
-| CC0 | creativecommons.org/publicdomain/zero/1.0/ |
-| MIT | opensource.org/licenses/MIT |
-| GPL | gnu.org/copyleft/gpl.html |
-| GPL 2.0+ | gnu.org/licenses/gpl-2.0.html |
-| GPL 3.0+ | gnu.org/licenses/gpl-3.0.html |
-| Apache 2.0 | apache.org/licenses/LICENSE-2.0.html |
-
-Note that this list includes **software licences as first-class options**, which is
-consistent with `software` being a supported item type.
-
-**Instances extend the list.** A retrieved institutional item
-(`10.25447/sit.33412894.v2`) carries licence value **12, "CC BY-NC-ND 4.0"** (S1) [API] —
-a licence absent from the global vocabulary above. So:
-
-- The seven-item list is **not** exhaustive across the federation.
-- **Non-commercial and no-derivatives terms occur in practice.** You cannot assume figshare
-  content is openly reusable, and you certainly cannot assume it is TDM-friendly. Check
-  `license` per item.
-
-**[NOT-VERIFIED]:** figshare's default licence for new deposits, and its text-and-data-mining
-policy, were not confirmed from an operator policy document.
-
-## 9. Caveats and controversies
-
-1. **No single "figshare".** The name covers figshare.com, dozens of white-labelled
-   institutional repositories on their own domains, and publisher data instances. Claims
-   about "figshare policy" are usually claims about one instance. [INF]
-2. **Size is not honestly summarisable in one number** (§3). ~4.1M for figshare.com is
-   defensible; a federation total is not available.
-3. **Commercial ownership.** figshare sits inside Digital Science / Springer Nature (S6)
-   [WEB]. A repository whose continuity depends on a commercial parent's product strategy
-   carries a different risk profile from CERN-hosted Zenodo — and the preprint-server
-   migrations in §5.2 are exactly what that risk looks like in practice, even though in
-   those cases the *customers* left rather than the platform failing.
-4. **Registry split.** figshare content is registered across **both** DataCite and Crossref
-   depending on instance and customer. Any bibliometric study that queries one registry
-   will undercount (§5.2 method note).
-5. **Operator policy documents not verified** (§4, §8). This is the weakest part of this
-   record and is flagged rather than papered over.
-
-## 10. Sources
-
-- **S1** — figshare REST API: `POST https://api.figshare.com/v2/articles/search`,
-  `GET /v2/articles/33412894`, `GET /v2/licenses`, and
-  `https://stats.figshare.com/total/views/article` (negative control). Retrieved
-  **2026-09-01**. Supports: item-type distribution, DOI-prefix and host diversity,
-  cursor pagination with no totals, licence vocabulary, CC BY-NC-ND instance licence.
-- **S2** — DataCite API: `https://api.datacite.org/clients?query=figshare` and
-  `https://api.datacite.org/dois?query=prefix:10.6084`, plus per-client DOI counts.
-  Retrieved 2026-09-01. Supports: 33 matching clients, `figshare.ars` = 4,106,613,
-  prefix `10.6084` = 4,106,628, institutional client counts, the 4,244,934 partial sum.
-- **S3** — figshare OAI-PMH: `https://api.figshare.com/v2/oai?verb=Identify`,
-  `?verb=ListSets`, `?verb=ListIdentifiers&metadataPrefix=oai_dc`. Retrieved 2026-09-01.
-  Supports: 30 sets and the 25 article types, placeholder `earliestDatestamp`,
-  `deletedRecord: transient`, absence of `completeListSize`.
-- **S4** — Crossref API: `https://api.crossref.org/prefixes/{10.36227,10.26434,10.31124,
-  10.22541}` and `/works` with `facet=published`. Retrieved 2026-09-01. Supports: TechRxiv
-  30,954 works (IEEE), ChemRxiv 55,400 (ACS), SAGE Advance 4,417 with per-year breakdown
-  2018–2025 and no 2026 works, current resource URLs and their grammars.
-- **S5** — DOI resolution probes via `https://doi.org/` for
-  `10.36227/techrxiv.14420315`, `10.36227/techrxiv.176281113.30584908/v1`,
-  `10.6084/m9.figshare.33412879.v1`, and `10.36227/techrxiv.999999999` (negative control,
-  HTTP 404); plus direct HTTP probes of `www.techrxiv.org`, `chemrxiv.org`,
-  `advance.sagepub.com`. Retrieved 2026-09-01. Supports: §5.2 migration evidence and the
-  403-fingerprint observation.
-- **S6** — Wikipedia, *Figshare*, retrieved via the MediaWiki API 2026-09-01. Supports:
-  January 2011 launch by Mark Hahnel, January 2012 Digital Science relaunch, Digital
-  Science / Springer Nature ownership, PLOS and ImpactStory integrations, hosted
-  institutional repository service from September 2013.
-- **S7** — Wikipedia, *List of preprint repositories*, wikitext via MediaWiki API,
-  2026-09-01. Supports: the "unknown" size entry, 2011 year, Springer Nature operator.
-
-## 11. Retrieval note
-
-`www.techrxiv.org`, `chemrxiv.org` and `advance.sagepub.com` returned **HTTP 403 to every
-User-Agent tried** — default, Chrome 131, WhatsApp, ChatGPT-User, ClaudeBot, Googlebot and
-Firefox 128 — with near-identical body sizes per agent, indicating an edge bot-block rather
-than agent-specific filtering. All substantive claims about those servers in this record
-were therefore obtained from **Crossref and DOI resolution behaviour instead of page
-scraping**. A useful discriminator emerged: `doi.org` returns **404** for an unregistered
-DOI but passes through to the target's **403** for a registered one, so a 403 confirms the
-DOI exists even when the page cannot be read.
diff --git a/research/preprint-repositories/government-and-institutional-technical-reports.md b/research/preprint-repositories/government-and-institutional-technical-reports.md
deleted file mode 100644
index 4bdd3a4..0000000
--- a/research/preprint-repositories/government-and-institutional-technical-reports.md
+++ /dev/null
@@ -1,931 +0,0 @@
-# Government and institutional technical reports — the grey literature of electronics
-
-- **Compiled:** 2026-09-02. Every figure was measured on that date unless stated otherwise.
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-- **Companion record:** [`open-access-full-text-sources.md`](open-access-full-text-sources.md) —
-  the decision ladder for finding a *published paper* for free. This file is the rung-8 fallback
-  in that ladder: **what to do when the thing you are looking for was never a paper.**
-
-> **The claim this record makes.** An enormous fraction of real electronics, firmware and systems
-> engineering knowledge was never published as a journal article and was never posted to a preprint
-> server. It exists as a **technical report** — a numbered, institutionally-published document from
-> a government laboratory, a university department or a corporate research division. None of the
-> resolvers in the companion record will find it, because most of it has no DOI. **The RISC-V
-> instruction set specification is the cleanest example: it is a Berkeley EECS technical report,
-> and [`arxiv.md` §7.5](arxiv.md) already established it is not on arXiv.**
-
----
-
-## 1. Why grey literature matters for hardware
-
-Three structural reasons, and they compound.
-
-**Reason one: the work was funded to produce a report, not a paper.** A NASA radiation-effects
-qualification campaign, a DOE national-laboratory detector build, a DARPA-funded prototype — the
-contractual deliverable is a report with a number on it. A conference paper, if one appears at all,
-is a compressed summary written afterwards for career reasons. **The report has the data; the paper
-has the story.** For anyone actually building hardware, the report is the more useful document: it
-contains the test matrix, the part numbers, the failure modes and the appendices.
-
-**Reason two: some documents are constitutionally not papers.** An instruction-set specification, a
-calibration procedure, a reliability handbook and a design manual are not research contributions
-and no journal would take them. They are still the primary sources for their fields. RISC-V, the
-Bell System Technical Journal's device physics, the MIT AI Memo series and the DEC SRC research
-reports are all in this category.
-
-**Reason three: this material is disproportionately free, and disproportionately fragile.**
-US federal reports are largely public-domain government works — no paywall, no licence, bulk APIs.
-But corporate report series depend on one company continuing to host one directory, and companies
-get acquired. §4 documents two collections whose original hosts are gone.
-
-**Practical consequence for the ladder:** if Unpaywall, Semantic Scholar and OpenAlex all return
-nothing for something that plainly exists, stop searching the article layer and ask *which
-institution produced this, and does it run a report series?*
-
----
-
-## 2. US federal report servers
-
-### 2.1 NASA NTRS — the NASA Technical Reports Server
-
-- **URL:** https://ntrs.nasa.gov/ · **API:** `https://ntrs.nasa.gov/api/citations/search`
-- **Coverage:** NASA and NACA output. The `published` facet returns **117 distinct year buckets**
-  [API], reaching back through the NACA era. (It also contains obvious date-entry corruption —
-  the lowest bucket key is `0202` — so do not build a time series without cleaning.)
-
-NTRS is the single best free source of **spacecraft and avionics electronics engineering** in
-existence. Not because NASA is unusually generous, but because NASA's engineering culture produces
-documents: radiation-hardness assurance, single-event-effect test campaigns on named commercial
-parts, EMC and grounding practice, connector and solder-joint reliability, materials outgassing,
-power-system design, FPGA and processor qualification.
-
-**Measured size, 2026-09-02** [API] (S1):
-
-| Measure | Count |
-|---|---|
-| Total records | **646,950** |
-| `disseminated: DOCUMENT_AND_METADATA` (**the PDF is there**) | **358,213** (55.4%) |
-| `disseminated: METADATA_ONLY` (citation only) | **288,737** (44.6%) |
-| `distribution: PUBLIC` | 646,950 — i.e. **everything the public API returns is public** |
-
-**Read that second row before you rely on NTRS.** Nearly half of NTRS records are citations with
-no attached document. The `disseminated` field tells you which, and you can filter on it. A
-harvester that assumes every hit has a PDF will be wrong 44.6% of the time.
-
-**Document-type mix** [API] (S1):
-
-| `stiType` | Count |
-|---|---|
-| `CONFERENCE_PAPER` | 150,828 |
-| `REPRINT` (the published version of a journal article) | 150,204 |
-| `OTHER` | 99,466 |
-| **`CONTRACTOR_REPORT`** | **71,868** |
-| `PRESENTATION` | 44,776 |
-| **`TECHNICAL_MEMORANDUM`** | **29,425** |
-| `PREPRINT` | 22,767 |
-| `ABSTRACT` | 22,547 |
-
-`CONTRACTOR_REPORT` and `TECHNICAL_MEMORANDUM` — 101,293 documents between them — are the classic
-grey literature: work done under contract by Lockheed, Boeing, Jet Propulsion Lab subcontractors
-and universities, that exists nowhere else.
-
-**By centre**: `CDMS` 381,853 (the bulk legacy load), `GSFC` 42,105, `JPL` 41,531, `LaRC` 28,285,
-`MSFC` 23,047, `ARC` 22,576, `JSC` 21,051, `GRC` 18,551 [API] (S1).
-
-#### The API
-
-```bash
-# search — no key, no UA fallback needed, plain curl works
-curl -s "https://ntrs.nasa.gov/api/citations/search?q=radiation%20hardened&size=10"
-
-# single record
-curl -s "https://ntrs.nasa.gov/api/citations/20150022446"
-
-# the PDF, straight out of the record's downloads[] array
-curl -sL -o out.pdf "https://ntrs.nasa.gov/api/citations/20150022446/downloads/20150022446.pdf"
-```
-
-The search response is Elasticsearch-shaped and **the aggregations are the good part**. Every
-query returns facet buckets for `author`, `center`, `reportNumber`, `fundingNumber`,
-`subjectCategory`, `stiType`, `stiTypeDetails`, `keyword`, `organization`, `distribution`,
-`disseminated`, `created`, `modified` and `published` — so one call gives you both the results
-*and* a map of who works on the topic and under which contract numbers. `fundingNumber` in
-particular lets you walk an entire programme.
-
-**Two traps** [API] (S1, S2):
-
-- **`q=` with an empty value returns `total: 0`.** `?q=&size=1` → 0 records. Omitting `q`
-  entirely, or `q=*`, both return the true 646,950. A harvester that builds its URL by string
-  concatenation and leaves `q=` empty will silently record zero for everything.
-- **Negative control is clean:** `GET /api/citations/99999999999` → **HTTP 404, 40-byte body**.
-  NTRS status codes can be trusted, unlike several hosts in
-  [`retrieval-notes.md`](retrieval-notes.md).
-
-#### What an electronics engineer actually finds there
-
-Measured hit counts, 2026-09-02 [API] (S1, S3):
-
-| Query | Hits | Sample first result |
-|---|---|---|
-| `radiation hardened` | **304** | *Decline in Radiation Hardened Microcircuit Infrastructure* (`20150022446`, GSFC) |
-| `FPGA single event upset` | **55** | *Single event upset susceptibility testing of the Xilinx Virtex II FPGA* |
-| `SpaceCube` | **47** | *Adapting the SpaceCube v2.0 Data Processing System for Mission-Unique…* |
-
-Drill into the `radiation hardened` result set and the shape of NASA's electronics literature is
-immediately visible [API] (S1):
-
-- **Subject categories:** *Electronics And Electrical Engineering* 96 · *Space Radiation* 29 ·
-  *Computer Operations And Hardware* 14 · *Spacecraft Instrumentation And Astrionics* 14 ·
-  *Quality Assurance And Reliability* 9 · *Solid-State Physics* 7
-- **Top authors:** Kenneth A. LaBel (21), Andrew S. Keys (12), James H. Adams (8),
-  John D. Cressler (7), Melanie D. Berg, Jean-Marie Lauenstein — i.e. the actual NEPP
-  (NASA Electronic Parts and Packaging) community, findable by name
-- **Keywords** include `single-event effect (SEE)`, `NASA Electronic Parts and Packaging (NEPP)
-  Program`, `Radiation Hardness Assurance`, `Shields-1`, `SpaceCube`
-- **Contributing organisations** include commercial part vendors — *Celis Semiconductor
-  Corporation*, *Linear Technology Corp.*, *National Semiconductor Corp.* — which means **NTRS
-  contains vendor radiation data that never appeared on a datasheet**
-
-**Use `reportNumber` as a facet.** It surfaces the real identifier series — `JPL-Publ-`, `E-`
-(Glenn), `ARC-E-DAA-TN`, `AED-R-`, and NEPP's own `NNNN-NNN-NEPP` — which is how you find the rest
-of a programme once you have one document from it.
-
-### 2.2 OSTI.GOV and DOE PAGES — the US Department of Energy
-
-- **URL:** https://www.osti.gov/ · **API:** `https://www.osti.gov/api/v1/records`
-- **DOE PAGES:** https://www.osti.gov/pages/ (200, 125,342 B [WEB])
-
-OSTI is the DOE's Office of Scientific and Technical Information. What is in it, from an
-electronics point of view: **national-laboratory instrumentation** (Argonne, Brookhaven, Fermilab,
-Oak Ridge, Sandia, Los Alamos, LLNL, PNNL, NREL, SLAC), particle and photon **detectors** and their
-readout ASICs, **power electronics** and grid hardware, **battery and energy-storage** work,
-**semiconductor materials and process**, pulsed-power and high-voltage engineering, and the
-control-system software that runs all of it.
-
-**DOE PAGES** (Public Access Gateway for Energy and Science) is the DOE's public-access mandate
-layer: accepted manuscripts of DOE-funded journal articles, free after any embargo. It is to DOE
-what PMC is to NIH.
-
-**Measured, 2026-09-02** — OSTI returns totals in an **`x-total-count` response header**, not in
-the body, which is easy to miss [API] (S4):
-
-```bash
-curl -sD - -o /dev/null "https://www.osti.gov/api/v1/records?rows=1&q=power+electronics" | grep -i x-total-count
-```
-
-| Query | `x-total-count` |
-|---|---|
-| `power electronics` | **377,043** |
-| `detector` | **258,839** |
-| `battery` | **234,889** |
-| `semiconductor` | **90,818** |
-| `riscv` | **34** |
-
-**Record shape and the full-text link** [API] (S4, S5) — this is the field that matters:
-
-```json
-{ "osti_id": "2584705",
-  "title": "Development and Optimization of a 10-Stage Solid-State Linear Transformer Driver",
-  "report_number": "DOE/NV/03624-2234",
-  "contract_number": "NA0003624",
-  "publication_date": "2025-08-25T00:00:00Z",
-  "product_type": "Program Document",
-  "links": [ {"rel":"citation","href":"https://www.osti.gov/biblio/2584705"},
-             {"rel":"fulltext","href":"https://www.osti.gov/servlets/purl/2584705"} ] }
-```
-
-**`links[].rel == "fulltext"` → `https://www.osti.gov/servlets/purl/<osti_id>` is a stable direct
-PDF route.** Verified: that URL for `2584705` returned **HTTP 200, 6,066,387 bytes, magic
-`%PDF-`** (S5). Records without a `fulltext` link are metadata-only.
-
-Note that `doi` was `null` on this record. **This is the whole point of the file.** A DOE report
-with a report number and no DOI is invisible to every resolver in the companion record.
-
-**Traps and negative controls** [API] (S4):
-
-- **`q=` empty returns `x-total-count: 0`** — the *same* trap as NTRS. Two independent federal
-  services share it; assume it is the default behaviour of this class of API.
-- A nonsense search term → `x-total-count: 0` (correct).
-- `GET /api/v1/records/999999999999` → **HTTP 404, 105-byte body** (clean).
-
-Other useful query fields on the API: `report_number`, `contract_number` (walk a whole contract),
-`research_org`, `sponsor_org`, `product_type`.
-
-### 2.3 DTIC — Defense Technical Information Center
-
-- **URL:** https://discover.dtic.mil/ · Probed 2026-09-02: home **HTTP 200, 466,561 B**;
-  `?q=radiation` **HTTP 200, 386,731 B** [WEB] (S6). Chrome-131 UA; no fallback needed.
-
-DTIC is the US defense department's report repository, and it is the deepest single source for
-**military electronics, EMC/EMI, RF and antenna engineering, materials, human factors, and
-reliability physics** — including a very large body of 1950s–1980s work that predates and
-underpins much of the commercial state of the art.
-
-**What is public and what is not — be precise about this:**
-
-- The public `discover.dtic.mil` interface serves documents cleared for **public release with
-  unlimited distribution** (the "Distribution Statement A" marking). These are free, full-text
-  PDFs, no account.
-- **Everything else is not there.** Distribution Statements B–F (limited to government agencies,
-  contractors, DoD components) and anything classified are held on a **registered** side that
-  requires DoD, federal-agency or approved-contractor credentials. Access is by eligibility, not by
-  payment.
-- **Do not read absence as non-existence.** A DTIC accession number that returns nothing publicly
-  usually means the document exists under a limiting distribution statement. Conversely, do not try
-  to route around it — that is an explicit access control, and `AGENTS.md` rule 7 applies.
-
-**Practical note:** DTIC's public site and its own disclaimer text now refer to the
-"Department of War" [WEB], reflecting the department's renaming — worth knowing when matching
-older citations that say "Department of Defense".
-
-**Historical caution:** an enormous number of scanned DTIC PDFs are OCR of poor microfiche. Search
-will miss documents whose OCR failed. Browse by accession-number range around a document you
-already have.
-
-### 2.4 NIST — measurement, standards, cryptography, metrology
-
-- **URLs:** https://www.nist.gov/publications (200, 116,978 B) ·
-  https://csrc.nist.gov/publications/fips (200, 140,880 B) · full-text host
-  `https://nvlpubs.nist.gov/` [WEB] (S7)
-
-NIST publications are **US government works, free, and generally in the public domain**. For this
-knowledge base the relevant series are:
-
-| Series | What it is | Hardware relevance |
-|---|---|---|
-| **FIPS** | Federal Information Processing Standards | FIPS 140-3 (crypto module security), FIPS 197 (AES), FIPS 202 (SHA-3), FIPS 203/204/205 (post-quantum) |
-| **SP 800-** | Computer security | Firmware resilience, supply-chain, key management |
-| **SP 500-** | Computer systems technology | |
-| **NISTIR / NIST TN** | Internal reports and technical notes | Electronics metrology, EMC, calibration, materials |
-| **JRes NIST** | *Journal of Research of NIST* | Measurement science, fully free |
-
-**Verified retrieval and negative control** [WEB] (S7), 2026-09-02:
-
-| URL | Result |
-|---|---|
-| `https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-193.pdf` | **200, 516,802 B, `%PDF-`** |
-| `https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-99999.pdf` *(control)* | **404, 1,380 B** |
-
-The `nvlpubs.nist.gov` URL pattern is predictable and the status codes are honest — one of the
-cleanest hosts probed across this whole survey. `NIST.SP.800-193` is *Platform Firmware Resiliency
-Guidelines*, which is squarely a hardware/firmware document and a good illustration of why NIST
-belongs in a hardware knowledge base.
-
-**Cryptography cross-reference:** NIST runs the standardisation process (AES, SHA-3, the
-post-quantum competition) whose *research* literature lives in the IACR Cryptology ePrint Archive.
-The two are complements: ePrint has the cryptanalysis, NIST has the ratified specification. See
-[`cryptology-eprint-archive.md`](cryptology-eprint-archive.md).
-
-### 2.5 NTIS, GAO and CRS
-
-**NTIS / NTRL** — the National Technical Reports Library, https://ntrl.ntis.gov/NTRL/
-(200, 115,425 B [WEB]). In NTIS's own words (S8):
-
-> "The National Technical Information Service acquires, indexes, abstracts, and archives the
-> **largest collection of U.S. government-sponsored technical reports in existence**. The NTRL
-> offers online, **free and open access** to these authenticated government technical reports."
-
-NTIS's historical role was selling reports; the free-access position is comparatively recent and is
-the reason NTRL is worth checking. It is the broadest federal net — it catches agencies that have
-no NTRS/OSTI-equivalent of their own. **Item count: [NOT-VERIFIED]** — no machine-readable total
-was obtained on the probe date.
-
-**GAO** (Government Accountability Office) — **blocked on the probe date.** `https://www.gao.gov/`
-→ **HTTP 403, 363-byte body**; `https://www.gao.gov/reports-testimonies` → **HTTP 403, 386 bytes**,
-both with the Chrome-131 UA (S9). This is a *third* distinct 403 fingerprint in this survey:
-neither the ~5.6 kB Cloudflare challenge nor the ~651 kB SHERPA body documented in the
-[companion record §7](open-access-full-text-sources.md#7-probe-status-table). GAO reports are free
-in principle; **not verified on this date.**
-
-**CRS** (Congressional Research Service) — `https://crsreports.congress.gov/` → **HTTP 200,
-345,391 B** [WEB] (S10). Since 2018 CRS reports have been published officially and free. They are
-policy analysis, not engineering, but they are unusually good at *context*: semiconductor supply
-chain, export controls, critical minerals, spectrum allocation, defense acquisition. Cite them for
-"why is this the way it is", never for a measurement.
-
----
-
-## 3. University technical-report series
-
-**The key insight: many foundational computing documents are technical reports, not papers.**
-Departments assign report numbers, host PDFs, and never submit the document anywhere. The
-following are the series that a systems or hardware reader will actually need.
-
-### 3.1 UC Berkeley EECS — where RISC-V actually lives
-
-- **URL:** https://www2.eecs.berkeley.edu/Pubs/TechRpts/
-- **Identifier form:** `UCB/EECS-<year>-<n>`
-- **URL pattern:** `https://www2.eecs.berkeley.edu/Pubs/TechRpts/<year>/EECS-<year>-<n>.{html,pdf}`
-
-> **Access caveat, stated first.** `www2.eecs.berkeley.edu` (128.32.139.28) was **TCP-unreachable
-> from this environment** on 2026-09-02 — raw connections to both port 443 and port 80 timed out,
-> and `curl` returned `http=000` after 25 s with every user agent tried (S11). This is *not* the
-> same as a 403 or a 404; nothing answered at all. **It is recorded as "unreachable from here", not
-> as "dead"** — one host on one day from one network is not evidence of a global outage, and the
-> site is widely used. **Every record below was therefore verified from Internet Archive replays,
-> which serve the department's own generated report pages verbatim, including their BibTeX and
-> EndNote blocks** (S12).
-
-**The RISC-V technical reports — verified, with exact numbers** [WEB via Wayback] (S12):
-
-| Report number | Title | Authors | Date |
-|---|---|---|---|
-| **UCB/EECS-2011-62** | **The RISC-V Instruction Set Manual, Volume I: Base User-Level ISA** | Andrew Waterman, Yunsup Lee, David A. Patterson, Krste Asanović | **2011-05-13** |
-| **UCB/EECS-2011-63** | Improving Energy Efficiency and Reducing Code Size with RISC-V Compressed | Andrew Waterman (MS thesis; advisors Patterson & Asanović) | 2011-05-13 |
-| **UCB/EECS-2014-54** | The RISC-V Instruction Set Manual, Volume I: User-Level ISA, **Version 2.0** | Waterman, Lee, Patterson, Asanović | 2014-05-06 |
-| **UCB/EECS-2016-1** | **Design of the RISC-V Instruction Set Architecture** | Andrew Waterman (PhD dissertation) | 2016-01-03 |
-| **UCB/EECS-2016-118** | The RISC-V Instruction Set Manual, Volume I: User-Level ISA, **Version 2.1** | Waterman, Lee, Patterson, Asanović | 2016-05-31 |
-| **UCB/EECS-2016-161** | The RISC-V Instruction Set Manual **Volume II: Privileged Architecture Version 1.9.1** | Waterman, Lee, **Rimas Avizienis**, Patterson, Asanović | 2016-11-04 |
-
-Canonical URLs (from the department's own BibTeX `URL` field, quoted in the archived pages):
-
-```
-https://www2.eecs.berkeley.edu/Pubs/TechRpts/2011/EECS-2011-62.pdf   # ISA v1, May 2011
-https://www2.eecs.berkeley.edu/Pubs/TechRpts/2011/EECS-2011-63.pdf   # RVC / compressed
-https://www2.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-54.pdf   # User-Level ISA 2.0
-https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-1.pdf    # Waterman PhD
-https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-118.pdf  # User-Level ISA 2.1
-https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-161.pdf  # Privileged 1.9.1
-```
-
-Two of the PDFs were retrieved through the Wayback replay and checked for magic bytes (S12):
-`EECS-2011-62.pdf` → **376,630 B, `%PDF-1.4`**; `EECS-2016-1.pdf` → **959,927 B, `%PDF-1.4`**.
-
-**Citation form.** The department generates BibTeX for every report. UCB/EECS-2011-62 is a
-`@techreport` with `Institution = {EECS Department, University of California, Berkeley}` and
-`Number = {UCB/EECS-2011-62}`; UCB/EECS-2011-63 is a `@mastersthesis`. Use those, not an invented
-`@misc`.
-
-**Why this matters.** [`arxiv.md` §7.5](arxiv.md) recorded, after searching, that
-*"the foundational RISC-V documents are UC Berkeley EECS technical reports and RISC-V International
-specifications, not arXiv preprints"*, and marked any canonical RISC-V arXiv landmark
-**[NOT-VERIFIED]**. **This record closes that loop with the exact identifiers.** The 250 arXiv
-papers matching `ti:"RISC-V" AND cat:cs.AR` are downstream work; the specification itself is
-`UCB/EECS-2011-62` and its successors. For the *current* ISA specifications, see §5 — they moved to
-RISC-V International in 2015.
-
-**The series is much larger than RISC-V.** Berkeley EECS technical reports include the department's
-PhD dissertations and MS theses, which is where a great deal of Chisel, Rocket, BOOM, Hwacha, gem5-
-adjacent and BAR/ASPIRE-lab work is documented in far more detail than the conference papers.
-**[NOT-VERIFIED]** for specific additional report numbers: further Wayback probes for candidate
-numbers returned `http=000`, which is the Internet Archive rate-limiting already recorded in
-[`retrieval-notes.md`](retrieval-notes.md), not evidence of absence.
-
-### 3.2 MIT
-
-- **DSpace@MIT:** https://dspace.mit.edu/ — the institutional repository, handle-based
-- **CSAIL publications:** https://publications.csail.mit.edu/
-
-Verified 2026-09-02 [WEB] (S13):
-
-| Resource | Result |
-|---|---|
-| `https://dspace.mit.edu/handle/1721.1/5460` | 200, 460,148 B — collection titled **"AI Memos (1959 – 2004)"** |
-| `https://dspace.mit.edu/handle/1721.1/6453` | 200, 558,625 B — an individual memo, *Simplifying Decision Trees* |
-| `https://publications.csail.mit.edu/ai/` | 200 — "historical collection of the former Artificial Intelligence Laboratory Publications Series" |
-
-**The AI Memo series (1959–2004) is the single most historically important university report series
-in computing**, and it is free. CSAIL's own framing [DOC]: the AI Lab and the Laboratory for
-Computer Science merged on **1 July 2003** to form CSAIL, and the AI Memos and AI Technical Reports
-are browsable "by number (older documents) or by year (newer documents)".
-
-DSpace@MIT is also where MIT theses live, and MIT theses are frequently the only full description
-of a piece of hardware. Handles (`1721.1/nnnn`) are persistent identifiers — prefer them to
-`dspace.mit.edu` URLs in citations.
-
-### 3.3 CMU
-
-- **SCS Technical Report Collection:** http://reports-archive.adm.cs.cmu.edu/ — **HTTP 200,
-  2,820 B** [WEB] (S14)
-
-A plain, old, working index. Its own sub-collections, quoted from the page (S14):
-
-> "Computer Science Technical Reports · Robotics Institute Technical Reports · Center for Automated
-> Learning and Discovery Reports · Machine Learning Department Reports · Language Technologies
-> Institute · Human-Computer Interaction Institute · Institute for Software Research · Lane Center
-> for Computational Biology · Information Technology Center · **Special Collections: Mach
-> Publications, Real-Time Mach Publications, Fox Publications, Parallel Data Laboratory (PDL)
-> Publications, Software Engineering Institute (SEI) Publications**"
-
-Those special collections are the reason to care. **Mach** (the microkernel under macOS and iOS),
-**Fox** (the Standard ML compiler and networking work) and the **PDL** (RAID, storage systems,
-NASD) are documented here at a level of detail the conference papers do not reach. The SEI
-collection is the source for CMMI, architecture-tradeoff methods and a large body of software
-safety/reliability practice.
-
-**Note the newer host:** `https://kilthub.cmu.edu/` — CMU's figshare-backed repository — returned
-**HTTP 202 with a zero-byte body** to a plain GET (S15). That is exactly the figshare behaviour
-already recorded in [`retrieval-notes.md` §5](retrieval-notes.md): *"`figshare.com` returned HTTP
-202 with a zero-byte body — neither success nor a usable error."* Confirmed on a second figshare
-tenant.
-
-### 3.4 Stanford
-
-- **Historical index:** http://i.stanford.edu/TR/ — **HTTP 200, 1,332 bytes** [WEB] (S16)
-
-A 1,332-byte hand-written HTML page, and it is genuinely the map. Its contents, verbatim:
-
-- CS Department technical reports, by decade: `cstr6x.html`, `cstr7x.html`, `cstr8x.html`,
-  `cstr9x.html` (**1960s through 1990s**)
-- CS Department **Technical Notes**: `cstn.html`
-- **Computer Systems Laboratory** technical reports: `csltr6x7x.html`, `csltr8x.html`,
-  `csltr9x.html`
-- And an explicit pointer: *"For CS technical reports 2000-present, see
-  http://hci.stanford.edu/cstr"*
-
-The 1960s–1970s Stanford CS reports are the AI-lab-era documents (SAIL); the Computer Systems
-Laboratory series is the hardware side. **This is a good example of the general pattern: the
-authoritative index for a 40-year report series is a static page nobody has touched in years, and
-it works.** It is also a good candidate for `web.archive.org/save/` under `AGENTS.md` rule 9 —
-a single unmaintained page holding the only map of a major series.
-
-### 3.5 Cambridge Computer Laboratory
-
-- **URL:** https://www.cl.cam.ac.uk/techreports/ — **HTTP 200, 10,247 B** [WEB] (S17)
-- **ISSN 1476-2986**, published continuously **since 1974** [DOC]
-
-The best-organised university report series probed in this pass. From the department's own page
-(S17):
-
-> "The Department of Computer Science and Technology (formerly the Computer Laboratory) has
-> published a Technical Report series (ISSN 1476-2986) since **1974**. Technical reports are
-> intended primarily for the long-term archival of results and descriptions that are not suitable
-> for publication elsewhere, due to their length or nature. Technical reports are also a common way
-> to make a departmental PhD thesis widely available. **Most newer technical reports, in particular
-> all published since 2002, are available online in PDF.** Older reports can be scanned on request."
-
-**URL pattern and verification** [WEB] (S17, S18):
-
-```
-https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-<n>.html   # abstract page
-https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-<n>.pdf    # full text
-```
-
-| Probe | Result |
-|---|---|
-| `UCAM-CL-TR-630.pdf` | **200, 11,754,717 B, `%PDF-`** |
-| `UCAM-CL-TR-630.html` | 200, 8,215 B |
-| `UCAM-CL-TR-99999.pdf` *(negative control)* | **404, 279 B** |
-| Highest report number linked from the index on 2026-09-02 | **1009** |
-
-**Note the trailing-slash trap:** `.../techreports/UCAM-CL-TR-630/` (with a slash) returns **404**.
-The identifier is a filename, not a directory.
-
-**A worked hardware example.** `UCAM-CL-TR-630` is **Sergei P. Skorobogatov, *Semi-invasive
-attacks – A new approach to hardware security analysis*, April 2005, 144 pages** — his PhD
-dissertation, issued as a technical report, **with DOI `10.48456/tr-630`** (S18). It is a
-foundational document for optical fault injection and chip-level attack methodology, and it is
-free. Note that Cambridge **now mints DOIs for its technical reports** (`10.48456/tr-<n>`), which
-makes them resolvable by the tools in the companion record — most university series do not.
-
-**Machine access** — Cambridge publishes the catalogue in seven formats (S17):
-
-| Format | File |
-|---|---|
-| BibTeX | `UCAM-CL-TR.bib` |
-| **OAI-PMH** | `UCAM-CL-TR-OAI-SR.xml` (static repository + PMH gateway) |
-| Simple Dublin Core in RDF/XML | linked from the index |
-| **DBLP XML** | linked from the index |
-| RFC 1807 | linked from the index |
-| Plain-text abstracts | `tr-abstracts.txt` |
-| RSS, HTML table, PDF catalogue with abstracts | linked from the index |
-
-That is more machine-readable surface than most national repositories offer. If you want a clean
-corpus of 50 years of one department's output, this is the easiest one to take.
-
-### 3.6 INRIA and HAL
-
-French public research — INRIA, CNRS, CEA, LIRMM — deposits into **HAL**, which this directory
-already documents in depth: [`hal.md`](hal.md) records **2,827,378 notices of which 1,788,688 have
-files attached** [API], and §7 there covers the CRDT papers, CompCert, Coq and Frama-C.
-
-The point for *this* record is that **HAL is a technical-report repository as much as a preprint
-server.** INRIA's `RR-` research-report series and `RT-` technical-report series are deposited
-there, and for a lot of INRIA work the research report is the long version with the proofs while
-the conference paper is the abstract. If a French systems or formal-methods paper says "see the
-extended version", the extended version is an INRIA RR in HAL.
-
-Recall the HAL trap from [README §4](README.md#6-probing-traps): **the subject field is
-`domainAllCode_s`, not `domain_s`** — the wrong field returns a silent `numFound: 0`.
-
----
-
-## 4. Corporate research archives
-
-The most valuable and the most fragile category. A corporate report series survives exactly as
-long as somebody at the company keeps paying for a web server, and the *research value* of the
-series has no bearing on that decision.
-
-### 4.1 Bell Labs — the Bell System Technical Journal
-
-The **BSTJ (1922–1983)** is arguably the most important single corpus in the history of
-electronics: transistor physics, information theory, transmission-line and filter design, the
-UNIX papers, switching systems, semiconductor process.
-
-**Where it actually is, verified 2026-09-02** [API] (S19):
-
-| Location | Measured |
-|---|---|
-| `archive.org` item `bstj-archives`, titled **"The Bell System Technical Journal (1922-1983)"** | metadata API 200; 6 files |
-| `archive.org` collection query `collection:"bstj-archives"` | **4,425 items** |
-| `archive.org` title search `title:("Bell System Technical Journal")` | 577 items |
-
-```bash
-curl -s 'https://archive.org/advancedsearch.php?q=collection%3A%22bstj-archives%22&rows=0&output=json'
-# → "numFound": 4425
-curl -s 'https://archive.org/metadata/bstj-archives'
-```
-
-**4,425 items on the Internet Archive is the durable copy.** Alcatel-Lucent hosted a free BSTJ
-archive at `bell-labs.com` for some years after 2008; that route is **[NOT-VERIFIED]** here and
-should not be relied on. **The Internet Archive collection is the answer to give.**
-
-**Bell Labs Technical Journal** (the 1996–2020 successor, Lucent/Alcatel-Lucent/Nokia era) was
-published through Wiley and then IEEE and is **not** free. Do not conflate the two titles — BSTJ is
-free, BLTJ largely is not. **[NOT-VERIFIED]** for any free BLTJ route.
-
-### 4.2 DEC / Compaq — SRC, WRL, CRL, PRL, NSL
-
-This is the case study in corporate archive fragility, and it has a happy ending.
-
-DEC's research labs — **SRC** (Systems Research Center, Palo Alto), **WRL** (Western Research
-Lab), **CRL** (Cambridge Research Lab), **PRL** (Paris Research Lab) and **NSL** (Network Systems
-Lab) — produced a report series that includes some of the most-cited work in distributed systems,
-compilers and computer architecture. After Compaq acquired DEC and HP acquired Compaq, the
-collection was hosted at `hpl.hp.com/techreports/Compaq-DEC/`.
-
-**Status of the original host, probed 2026-09-02** [WEB] (S20):
-
-- `www.hpl.hp.com` resolves (15.73.144.188) but **raw TCP to port 443 fails**; `curl` returned
-  `http=000` for both `/techreports/Compaq-DEC/` and `/hpjournal/journal.html`.
-- The Internet Archive's **last three captures** of `hpl.hp.com/techreports/Compaq-DEC/` are
-  **2022-05-17 (302)**, **2022-05-17 (301)** and **2022-12-22 (301)** — i.e. **by 2022 the URL was
-  already only a redirect**, not the collection. The directory was gone before the host was.
-
-**Where the collection survives: bitsavers** [WEB] (S21).
-`https://www.bitsavers.org/pdf/dec/tech_reports/` — HTTP 200, 68,014 B, an Apache directory index.
-Measured file counts by prefix:
-
-| Prefix | Files | Series |
-|---|---|---|
-| `SRC-RR-` | **170** | SRC Research Reports |
-| `SRC-TN-` | **67** | SRC Technical Notes |
-| `WRL-` | **108** | Western Research Lab reports |
-| `WRL-TN-` | **42** | WRL Technical Notes |
-| `CRL-` | **91** | Cambridge Research Lab |
-| `PRL-RR-` | **35** | Paris Research Lab |
-| `NSL-TN-` / `NSL-NN-` / `NSL-RR-` | 4 / 2 / 1 | Network Systems Lab |
-| **`Compaq-DEC_TRs_HPL_mirror_2007.zip`** | 1 | **236,085,636 B (≈236 MB)** — a complete mirror of the HPL-hosted collection taken in **2007**, `Last-Modified: 2023-09-04` |
-
-Negative control: `SRC-RR-99999.pdf` → **HTTP 404, 280 B** (S21). Clean.
-
-**The lesson, and it generalises:** somebody mirrored a corporate research archive in 2007, and
-that ZIP is now the reason the collection exists at all. The original host stopped serving it
-between 2007 and 2022 and nobody at HP announced it. **When you find a corporate report series that
-matters to you, take a copy.**
-
-### 4.3 HP Journal
-
-*Hewlett-Packard Journal* (1949–1998) is the primary source for a great deal of test-and-
-measurement instrument design — the internals of HP counters, spectrum analysers, logic analysers
-and calculators, written by the engineers who built them.
-
-**Status: [NOT-VERIFIED] / at risk.** `https://www.hpl.hp.com/hpjournal/journal.html` returned
-`http=000` (TCP failure) on 2026-09-02 (S20), from the same unreachable host as §4.2. Given that
-the adjacent Compaq-DEC directory was already a redirect by 2022, **assume the HP Journal archive
-at that URL is gone.** Third-party scans circulate (HP Memory Project, bitsavers' HP tree,
-Internet Archive) but **no specific surviving canonical location was verified in this pass.**
-
-### 4.4 IBM Journal of Research and Development
-
-- `https://research.ibm.com/journal` → **302 → `https://research.ibm.com/publications?source=19971`,
-  HTTP 200, 80,241 B** [WEB] (S22)
-
-The *IBM Journal of Research and Development* (1957–) and the *IBM Systems Journal* are the primary
-sources for System/360 architecture, DRAM and magnetic-recording physics, CMOS process
-development, mainframe RAS engineering and a great deal of early database work.
-
-**Access is mixed and this record will not pretend otherwise.** Recent IBM JRD volumes are
-published through **IEEE Xplore** and are paywalled. IBM's own `research.ibm.com/publications`
-front end is free for abstracts and hosts many full texts. IBM historically ran a public
-"DomainoWeb"/`domino.research.ibm.com` report server; `dominoweb.draco.res.ibm.com` returned
-`http=000` on the probe date (S22). **A comprehensive free route to the full JRD back file is
-[NOT-VERIFIED].**
-
-### 4.5 Xerox PARC
-
-**The host is gone, and the redirect tells the story.** `https://www.parc.com/publications/`
-**redirects to `https://www.sri.com/research/future-concepts-division/`** (HTTP 200, 137,588 B)
-[WEB] (S23) — PARC having been acquired by SRI International. **The publications index no longer
-exists at that address**; you land on a corporate division page.
-
-PARC's foundational work — Ethernet, Smalltalk, the Alto, InterPress, laser printing,
-bitmap displays, ubiquitous computing — was published as **Xerox PARC technical reports** with
-`CSL-`, `SSL-` and `ISL-` prefixes. Those documents survive, but **scattered**: bitsavers' `xerox`
-tree, the Computer History Museum, `worrydream.com`-style curated collections, individual authors'
-pages and the Internet Archive. **No single authoritative index was located in this pass —
-[NOT-VERIFIED].** This is the most serious unresolved gap in this record and a legitimate
-`web.archive.org/save/` target list for future work.
-
-### 4.6 Microsoft Research
-
-- `https://www.microsoft.com/en-us/research/publications/` → **HTTP 200, 1,237,346 B** [WEB] (S24)
-
-MSR maintains a large, live, free publications index — Dryad, Naiad, Orleans, F*, Z3, Project
-Catapult (FPGA acceleration in Azure), Farview, silicon photonics, holographic and DNA storage.
-Most entries link a free PDF. It is the healthiest corporate research archive probed here.
-
-**Caveat:** the URL slugs are not stable. A deep link built from a paper title
-(`.../publication/the-chubby-lock-service-for-loosely-coupled-distributed-systems/`) returned
-**HTTP 404** (S24). **Search the index; do not construct URLs from titles.** And, as with all
-corporate archives, if a document matters, keep a copy — Microsoft Academic's shutdown at the end
-of 2021 (see [companion record §2.2](open-access-full-text-sources.md)) is a reminder that
-Microsoft does retire research infrastructure.
-
----
-
-## 5. Standards bodies — what is free and what is not
-
-Precision matters here because the differences are large and people guess wrong in both directions.
-
-| Body | Free? | Verified |
-|---|---|---|
-| **IETF / RFC Editor** | **Entirely free. Always has been.** | ✅ [WEB] |
-| **RISC-V International** | **Free** — ratified specs published openly | ✅ [WEB] |
-| **USB-IF** | **Free** — specifications downloadable from the Document Library | ✅ [WEB] |
-| **JEDEC** | **Free of charge, but registration-walled** | ⚠️ partial |
-| **IEEE SA** | **Mostly paid.** A subsidised subset is free via the GET Program | ⚠️ partial |
-
-### IETF — the model everyone else should copy
-
-- `https://www.rfc-editor.org/rfc-index.txt` → **HTTP 200, 2,024,501 bytes** — the complete index
-  of every RFC ever published, as a single plain-text file (S25).
-- `https://www.rfc-editor.org/rfc/rfc9000.txt` → **HTTP 200, 403,442 bytes** — RFC 9000 (QUIC),
-  full text, no account, no cookie banner, no paywall (S25).
-
-**Every RFC, from RFC 1 (1969) to today, is free, permanent and machine-readable**, in `.txt`,
-`.html`, `.xml` and `.pdf`, plus Internet-Drafts and the working-group mailing-list archives. There
-is no other standards body in this table of which that is true. When a protocol is specified in an
-RFC, you have the complete authoritative source at zero cost — which is a large part of why the
-Internet protocol stack has the implementation diversity it has.
-
-### RISC-V International
-
-- `https://riscv.org/technical/specifications/` → **301 →
-  `https://riscv.org/specifications/ratified/`, HTTP 200, 212,511 B** [WEB] (S26)
-
-**RISC-V specifications are free.** The site separates **Ratified Specs** from **Under
-Development**, and the specification sources are additionally developed in public on GitHub.
-
-**The historical handoff matters for citation.** The Berkeley technical reports in §3.1 are the
-*original* documents (2011–2016). Stewardship moved to the RISC-V Foundation (2015), which became
-**RISC-V International**. So:
-
-- Citing the **origin** of RISC-V → `UCB/EECS-2011-62` (and `UCB/EECS-2016-1` for the design
-  rationale).
-- Citing the **current** ISA → the ratified specification from riscv.org, with its version and
-  ratification date.
-- Citing "the RISC-V spec" without saying which → ambiguous across a decade of revisions. Don't.
-
-### USB-IF
-
-- `https://www.usb.org/documents` → **HTTP 200, 144,183 B** [WEB] (S27)
-
-A public **Document Library**, filterable by Category (Legal, Presentations, Specification, Tools,
-White Paper) and Type (Cable and Connector Specification, etc.). Specifications are downloadable
-without membership, under a prominent "AS IS", all-warranties-disclaimed legal notice. There is a
-separate **Member Login** for member business, but the specs themselves are public. Note that
-specific ZIP filenames are versioned and change — a guessed filename returned **404, 37,583 B**
-(S27) — so navigate the library rather than constructing URLs.
-
-### JEDEC
-
-- `https://www.jedec.org/standards-documents` → **HTTP 200, 60,155 B**;
-  `https://www.jedec.org/standards-documents/docs/jesd79-5c` → **HTTP 200, 48,268 B** [WEB] (S28)
-
-JEDEC is where the memory standards live — **DDR SDRAM, HBM, LPDDR, UFS, e.MMC, JESD21-C module
-configurations, JEP95 registered outlines, JEP30 part-model guidelines, ESD, lead-free
-manufacturing, and the GaN/SiC wide-bandgap power semiconductor documents** (all confirmed as
-navigation categories on the standards page).
-
-**The access model: documents are free of charge but not anonymous.** Downloading requires a free
-registered JEDEC account, which is why an unauthenticated scripted fetch of a document gets you the
-landing page and not the PDF. Some items are genuinely commercial — the page also advertises
-"Order JEDEC Standard Manufacturer's ID Code", a paid registration service. **The precise
-free-account download mechanics were not exercised in this pass — [NOT-VERIFIED] beyond the
-landing pages.** Do not describe JEDEC as "paywalled" (it mostly is not) or as "open" (it is not
-that either); **registration-walled** is the accurate word.
-
-### IEEE standards
-
-- `https://standards.ieee.org/products-programs/ieee-get-program/` → **HTTP 200, 92,930 B**
-  [WEB] (S29)
-
-**IEEE standards are, by default, paid.** IEEE 802.3 (Ethernet), 802.11 (Wi-Fi), 1149.1 (JTAG),
-1076 (VHDL), 1364 (Verilog), 1800 (SystemVerilog), 754 (floating point) are sold individually or
-through subscription.
-
-The **IEEE GET Program** is the exception. In IEEE SA's own words (S29):
-
-> "The subsidized sponsorship of standards via the IEEE GET Program helps expand the global reach
-> of technical knowledge developed by industry, accelerates adoption of IEEE standards, contributes
-> to an open knowledge community…"
-
-The mechanism is that **a sponsor pays so that a particular standard can be given away**. The 802
-family has historically been the flagship of this (the "Get IEEE 802" programme). **Which specific
-standards are currently free is [NOT-VERIFIED]** — the list is dynamic and the page did not yield a
-machine-readable enumeration. **Check the GET Program page before assuming you must pay, and before
-assuming you need not.**
-
-*(For IEEE **papers**, as opposed to standards, see
-[companion record §3.3](open-access-full-text-sources.md#33-ieee) and
-[`techrxiv.md`](techrxiv.md).)*
-
----
-
-## 6. Status table
-
-All probes **2026-09-02**. "Chrome 131" = the rung-2 user agent from
-[`AGENTS.md`](../../AGENTS.md); everything else was default `curl`.
-
-| Source | Endpoint | Status | Size / count | Notes |
-|---|---|---|---|---|
-| **NASA NTRS** | `ntrs.nasa.gov/api/citations/search` | **200** | **646,950** records | 358,213 with document. Bogus id → 404 (40 B). **`q=` empty → 0** |
-| **OSTI** | `osti.gov/api/v1/records` | **200** | via `x-total-count` | `links[rel=fulltext]` → `/servlets/purl/<id>`; verified 6,066,387 B PDF. **`q=` empty → 0** |
-| DOE PAGES | `osti.gov/pages/` | 200 | 125,342 B | |
-| **DTIC** | `discover.dtic.mil/` · `/results/?q=radiation` | **200** | 466,561 B · 386,731 B | Chrome 131. Public = Distribution Statement A only |
-| **NIST** | `nvlpubs.nist.gov/.../NIST.SP.800-193.pdf` | **200** | 516,802 B, `%PDF-` | Bogus → **404**, 1,380 B. Clean host |
-| NIST | `nist.gov/publications` · `csrc.nist.gov/publications/fips` | 200 | 116,978 B · 140,880 B | |
-| NTIS / NTRL | `ntrl.ntis.gov/NTRL/` | 200 | 115,425 B | "free and open access". Count NOT-VERIFIED |
-| **GAO** | `gao.gov/` · `/reports-testimonies` | **403** | **363 B · 386 B** | **Third distinct 403 fingerprint.** Blocked |
-| CRS | `crsreports.congress.gov/` | 200 | 345,391 B | |
-| **UC Berkeley EECS** | `www2.eecs.berkeley.edu` (128.32.139.28) | **000** | — | **Raw TCP timeout on :443 and :80.** All records via Wayback |
-| Berkeley via Wayback | `web.archive.org/web/2020id_/…EECS-2011-62.html` etc. | 200 | 6.1–8.0 kB pages | 6 RISC-V reports verified with BibTeX |
-| Berkeley PDFs via Wayback | `…EECS-2011-62.pdf` · `…EECS-2016-1.pdf` | 200 | 376,630 B · 959,927 B, `%PDF-1.4` | Further probes → 000 (IA rate limit) |
-| **MIT DSpace** | `dspace.mit.edu/handle/1721.1/5460` | **200** | 460,148 B | "AI Memos (1959 – 2004)" |
-| MIT CSAIL | `publications.csail.mit.edu/ai/` | 200 | 5,244 B | AI Lab historical series |
-| **CMU SCS** | `reports-archive.adm.cs.cmu.edu/` | **200** | 2,820 B | Mach, Fox, PDL, SEI special collections |
-| CMU KiltHub | `kilthub.cmu.edu/` | **202** | **0 B** | figshare zero-byte-202 trap, confirmed on a 2nd tenant |
-| **Stanford** | `i.stanford.edu/TR/` | **200** | 1,332 B | Decade indexes 1960s–1990s + CSL series |
-| Stanford | `i.stanford.edu/TR/CS-TR-listing.html` *(control)* | 404 | 197 B | |
-| **Cambridge CL** | `cl.cam.ac.uk/techreports/` | **200** | 10,247 B | ISSN 1476-2986; since 1974; highest TR seen **1009** |
-| Cambridge PDF | `UCAM-CL-TR-630.pdf` | **200** | **11,754,717 B**, `%PDF-` | Skorobogatov; DOI `10.48456/tr-630` |
-| Cambridge control | `UCAM-CL-TR-99999.pdf` · `UCAM-CL-TR-630/` | 404 | 279 B | Trailing slash also 404s |
-| **BSTJ** | `archive.org` `collection:"bstj-archives"` | **200** | **4,425 items** | Item titled "The Bell System Technical Journal (1922-1983)" |
-| **DEC/Compaq (original)** | `hpl.hp.com/techreports/Compaq-DEC/` | **000** | — | Wayback's last 3 captures (2022) are 301/302 — gone before the host died |
-| **DEC/Compaq (survivor)** | `bitsavers.org/pdf/dec/tech_reports/` | **200** | 68,014 B index | 170 SRC-RR · 67 SRC-TN · 108 WRL · 42 WRL-TN · 91 CRL · 35 PRL-RR |
-| bitsavers mirror zip | `Compaq-DEC_TRs_HPL_mirror_2007.zip` | 200 | **236,085,636 B** | Mirror taken 2007 |
-| bitsavers control | `SRC-RR-99999.pdf` | 404 | 280 B | Clean |
-| **HP Journal** | `hpl.hp.com/hpjournal/journal.html` | **000** | — | **Assume gone.** No canonical survivor verified |
-| IBM JRD | `research.ibm.com/journal` | 200 (after 302) | 80,241 B | Recent volumes on IEEE Xplore, paywalled |
-| IBM (legacy) | `dominoweb.draco.res.ibm.com/` | **000** | — | |
-| **Xerox PARC** | `parc.com/publications/` | 200 | 137,588 B | **Redirects to `sri.com/research/future-concepts-division/`** — index gone |
-| Microsoft Research | `microsoft.com/en-us/research/publications/` | 200 | 1,237,346 B | Title-derived deep link → 404; slugs unstable |
-| **IETF** | `rfc-editor.org/rfc-index.txt` · `/rfc/rfc9000.txt` | **200** | 2,024,501 B · 403,442 B | Entirely free |
-| **RISC-V Intl** | `riscv.org/specifications/ratified/` | **200** | 212,511 B | Free; 301 from `/technical/specifications/` |
-| **USB-IF** | `usb.org/documents` | **200** | 144,183 B | Free; guessed ZIP filename → 404 |
-| **JEDEC** | `jedec.org/standards-documents` · `/docs/jesd79-5c` | **200** | 60,155 B · 48,268 B | Free but **registration-walled**; mechanics NOT-VERIFIED |
-| **IEEE SA GET** | `standards.ieee.org/products-programs/ieee-get-program/` | **200** | 92,930 B | Which standards are free: **NOT-VERIFIED** |
-
-### Explicitly not verified
-
-Listed so the gaps are visible rather than silent.
-
-1. **UC Berkeley EECS was never reached directly.** TCP timed out from this environment. All six
-   RISC-V records come from Internet Archive replays of the department's own pages. The *content*
-   is first-hand from Berkeley's generator; the *transport* was not.
-2. **No Berkeley report numbers beyond the six RISC-V documents were confirmed.** Candidate probes
-   for Rocket Chip / Chisel / BOOM reports returned `http=000` from Wayback rate-limiting, which is
-   not evidence of absence.
-3. **NTIS/NTRL holdings count** — no machine-readable total obtained.
-4. **GAO** — 403 on both paths tried; nothing about GAO's holdings was verified first-hand.
-5. **HP Journal** — no surviving canonical location verified.
-6. **Xerox PARC report series** — no authoritative index located anywhere. The most serious gap.
-7. **IBM JRD** — no comprehensive free route to the back file verified.
-8. **Bell Labs Technical Journal** (1996–2020, as distinct from BSTJ) — no free route verified.
-9. **JEDEC download mechanics** — the free-registration flow was not exercised.
-10. **IEEE GET Program contents** — no machine-readable list of currently-free standards.
-11. **DTIC's public/restricted split was not quantified.** The distinction is documented from
-    policy, not measured.
-
-### Retrieval notes for the crawler access table
-
-Staged for [`retrieval-notes.md`](retrieval-notes.md) and thence
-[`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md):
-
-- **Federal report APIs are open and need no user-agent fallback.** `ntrs.nasa.gov`,
-  `www.osti.gov` and `eutils.ncbi.nlm.nih.gov` all answered default `curl`. `discover.dtic.mil`,
-  `nist.gov` and `nvlpubs.nist.gov` answered the Chrome-131 UA.
-- **New shared trap: `q=` with an empty value returns zero, not everything**, on *both* NTRS and
-  OSTI. Two independent agencies, same failure. Omit the parameter or use `q=*`.
-- **OSTI puts its result total in the `x-total-count` response header, not the body.** A body-only
-  parser sees no count at all.
-- **New 403 fingerprint: `www.gao.gov` returns a ~363–386-byte 403.** Distinct from the ~5.6 kB
-  Cloudflare challenge and the ~651 kB SHERPA 403 recorded in the
-  [companion record §7](open-access-full-text-sources.md#7-probe-status-table).
-- **`http=000` (TCP timeout) is a genuinely different signal from 403/404** and appeared for
-  `www2.eecs.berkeley.edu`, `www.hpl.hp.com` and `dominoweb.draco.res.ibm.com`. Record it as
-  *unreachable*, never as *defunct*, unless corroborated — the same discipline this survey applied
-  to `synthical.com` in [`retrieval-notes.md`](retrieval-notes.md).
-- **figshare's HTTP-202-with-zero-bytes behaviour is reproducible on institutional tenants**
-  (`kilthub.cmu.edu`), not just `figshare.com`.
-- **Internet Archive rate-limiting is the binding constraint on grey-literature verification.**
-  Roughly a dozen Wayback replay fetches in quick succession degraded to `http=000`, while the
-  **CDX API stayed responsive throughout** — corroborating the existing note in
-  [`retrieval-notes.md`](retrieval-notes.md). **Use CDX for existence, replay sparingly.**
-
-### Archival candidates (`AGENTS.md` rule 9)
-
-Not submitted in this pass; recommended. All are scarce, unmirrored, and hold the only map of a
-significant collection:
-
-- `http://i.stanford.edu/TR/` and its seven decade indexes — a 1,332-byte unmaintained page that is
-  the only index of 40 years of Stanford CS/CSL reports.
-- `https://www.bitsavers.org/pdf/dec/tech_reports/` — the only surviving index of the DEC
-  SRC/WRL/CRL/PRL/NSL collection now that the HPL host is gone.
-- `http://reports-archive.adm.cs.cmu.edu/` — the CMU SCS index, including the Mach and PDL special
-  collections.
-- Any Xerox PARC report index that a future pass manages to locate (§4.5).
-
----
-
-## 7. Sources
-
-Retrieved **2026-09-02** unless stated. Raw probe output is under
-[`../../scratch/preprint-repositories/oa-fulltext/`](../../scratch/preprint-repositories/oa-fulltext/).
-
-- **S1** `https://ntrs.nasa.gov/api/citations/search?size=0` and `…?q=radiation%20hardened&size=1` —
-  totals, `disseminated`/`distribution`/`stiType`/`center`/`subjectCategory`/`author`/`keyword`/
-  `organization`/`reportNumber` aggregations. Supports §2.1 tables. [API]
-- **S2** `https://ntrs.nasa.gov/api/citations/search?q=&size=1` → `total: 0` vs `?size=1` and
-  `?q=*&size=1` → 646,950; `https://ntrs.nasa.gov/api/citations/99999999999` → 404, 40 B. Supports
-  the NTRS traps and negative control. [API]
-- **S3** `https://ntrs.nasa.gov/api/citations/search?q=SpaceCube|FPGA+single+event+upset&size=1`
-  and `https://ntrs.nasa.gov/api/citations/20150022446` (record + `downloads[]`). [API]
-- **S4** `https://www.osti.gov/api/v1/records?rows=1&q=…` for `power+electronics`, `semiconductor`,
-  `battery`, `detector`, `riscv`, an empty `q`, a nonsense term, and
-  `/api/v1/records/999999999999`; totals read from the `x-total-count` header. [API]
-- **S5** `https://www.osti.gov/servlets/purl/2584705` → 200, 6,066,387 B, `%PDF-`. Supports the
-  full-text route. [API/WEB]
-- **S6** `https://discover.dtic.mil/` (200, 466,561 B) and `/results/?q=radiation` (200,
-  386,731 B), Chrome 131. [WEB]
-- **S7** `https://www.nist.gov/publications` (200, 116,978 B);
-  `https://csrc.nist.gov/publications/fips` (200, 140,880 B);
-  `https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-193.pdf` (200, 516,802 B,
-  `%PDF-`); `…NIST.SP.800-99999.pdf` (404, 1,380 B). [WEB]
-- **S8** `https://ntrl.ntis.gov/NTRL/` (200, 115,425 B) — the "largest collection… free and open
-  access" statement quoted in §2.5. [DOC]
-- **S9** `https://www.gao.gov/` → 403, 363 B; `https://www.gao.gov/reports-testimonies` → 403,
-  386 B; Chrome 131. [WEB]
-- **S10** `https://crsreports.congress.gov/` → 200, 345,391 B. [WEB]
-- **S11** `getent hosts www2.eecs.berkeley.edu` → 128.32.139.28; raw TCP to :443 and :80 both time
-  out; `curl` `http=000` at 25 s with default and Chrome-131 UAs, HTTP/2 and HTTP/1.1. [WEB]
-- **S12** Internet Archive replays `http://web.archive.org/web/2020id_/http://www.eecs.berkeley.edu/
-  Pubs/TechRpts/{2011/EECS-2011-62, 2011/EECS-2011-63, 2014/EECS-2014-54, 2016/EECS-2016-1,
-  2016/EECS-2016-118, 2016/EECS-2016-161}.html` — titles, author lists, dates, canonical PDF URLs,
-  BibTeX and EndNote blocks read directly from the department's generated pages. PDFs for
-  `EECS-2011-62` (376,630 B) and `EECS-2016-1` (959,927 B), both `%PDF-1.4`. Supports the §3.1
-  table. [WEB]
-- **S13** `https://dspace.mit.edu/handle/1721.1/5460` → "AI Memos (1959 - 2004)", 200, 460,148 B;
-  `/handle/1721.1/6453` → 200, 558,625 B; `https://publications.csail.mit.edu/ai/` → 200, quoted in
-  §3.2. [WEB]
-- **S14** `http://reports-archive.adm.cs.cmu.edu/` → 200, 2,820 B; sub-collection list quoted
-  verbatim. [WEB]
-- **S15** `https://kilthub.cmu.edu/` → HTTP 202, 0 bytes. [WEB]
-- **S16** `http://i.stanford.edu/TR/` → 200, 1,332 B; full contents transcribed in §3.4. [WEB]
-- **S17** `https://www.cl.cam.ac.uk/techreports/` → 200, 10,247 B — ISSN, 1974 start date, the
-  "all published since 2002 are available online in PDF" statement, and the seven catalogue
-  formats. [DOC]
-- **S18** `https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-630.pdf` (200, 11,754,717 B, `%PDF-`);
-  `…-630.html` (200, 8,215 B) giving title, author, April 2005, 144 pages and DOI
-  `10.48456/tr-630`; `…-99999.pdf` and `…-630/` both 404 (279 B). [WEB]
-- **S19** `https://archive.org/advancedsearch.php?q=collection:"bstj-archives"&rows=0&output=json`
-  → `numFound: 4425`; `https://archive.org/metadata/bstj-archives` → item title "The Bell System
-  Technical Journal (1922-1983)"; `title:("Bell System Technical Journal")` → 577. [API]
-- **S20** `https://www.hpl.hp.com/techreports/Compaq-DEC/` and `/hpjournal/journal.html` →
-  `http=000`; `http://web.archive.org/cdx/search/cdx?url=hpl.hp.com/techreports/Compaq-DEC/` → last
-  three captures 2022-05-17 (302), 2022-05-17 (301), 2022-12-22 (301). [WEB/API]
-- **S21** `https://www.bitsavers.org/pdf/dec/tech_reports/` → 200, 68,014 B; prefix counts by
-  `grep`; `HEAD Compaq-DEC_TRs_HPL_mirror_2007.zip` → 236,085,636 B, Last-Modified 2023-09-04;
-  `SRC-RR-99999.pdf` → 404, 280 B. [WEB]
-- **S22** `https://research.ibm.com/journal` → 302 → `?source=19971`, 200, 80,241 B;
-  `https://dominoweb.draco.res.ibm.com/` → `http=000`. [WEB]
-- **S23** `https://www.parc.com/publications/` → 200, 137,588 B, final URL
-  `https://www.sri.com/research/future-concepts-division/`. [WEB]
-- **S24** `https://www.microsoft.com/en-us/research/publications/` → 200, 1,237,346 B; a
-  title-derived publication slug → 404, 168,984 B. [WEB]
-- **S25** `https://www.rfc-editor.org/rfc-index.txt` → 200, 2,024,501 B;
-  `https://www.rfc-editor.org/rfc/rfc9000.txt` → 200, 403,442 B;
-  `https://www.rfc-editor.org/about/` → 200, 83,352 B. [WEB]
-- **S26** `https://riscv.org/technical/specifications/` → 301 → `/specifications/ratified/`, 200,
-  212,511 B. [WEB]
-- **S27** `https://www.usb.org/documents` → 200, 144,183 B, Document Library and legal disclaimer;
-  a guessed spec ZIP filename → 404, 37,583 B. [WEB]
-- **S28** `https://www.jedec.org/standards-documents` → 200, 60,155 B (technology focus areas
-  quoted); `https://www.jedec.org/standards-documents/docs/jesd79-5c` → 200, 48,268 B. [WEB]
-- **S29** `https://standards.ieee.org/products-programs/ieee-get-program/` → 200, 92,930 B; the
-  "subsidized sponsorship of standards" statement quoted in §5. [DOC]
-- **S30** [`arxiv.md` §7.5](arxiv.md) — the prior finding that the foundational RISC-V documents are
-  Berkeley technical reports and RISC-V International specifications, not arXiv preprints, marked
-  [NOT-VERIFIED] there. This record supplies the identifiers. [internal]
diff --git a/research/preprint-repositories/hal.md b/research/preprint-repositories/hal.md
deleted file mode 100644
index c54d3da..0000000
--- a/research/preprint-repositories/hal.md
+++ /dev/null
@@ -1,404 +0,0 @@
-# HAL (Hyper Articles en Ligne) — preprint repository record
-
-- **URL:** https://hal.science/ · API `https://api.archives-ouvertes.fr/search/`
-- **Operator:** Centre pour la communication scientifique directe (CCSD), a CNRS service unit
-  (CNRS / INRIA / Université de Lyon). Funded as French public research infrastructure. (S1)
-- **Discipline scope:** all disciplines — *as actually used*, dominated by SHS (humanities and
-  social sciences) and life sciences by volume, but with a large and internationally important
-  computer-science and engineering core (S2)
-- **Launched:** see §3 — the "2001" date is **contested**; CCSD's own page attributes 2001 to
-  **TEL/HAL theses**, and HAL's OAI-PMH `earliestDatestamp` is **2002-09-23** (S3, S4)
-- **Status:** active (heavy daily deposit traffic observed 2026-09-01)
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-HAL is France's **national open archive**. It is not a preprint server in the arXiv sense and
-reading it as one will mislead you. HAL is a deposit-and-dissemination platform for the *whole*
-output of French public research: journal articles (usually author-accepted manuscripts),
-conference papers, book chapters, monographs, theses, habilitations, technical/research reports,
-patents, software, images and video. A large fraction of its records are **bibliographic notices
-with no file attached at all** (§3).
-
-For an anglophone engineer the important consequence is this: **a great deal of foundational
-French computer-science work was published as an INRIA *research report* and deposited in HAL,
-and never went to arXiv.** If you search only arXiv you will miss it. The INRIA research-report
-series (`RR-NNNN`, `RT-NNNN`) is the closest French equivalent to a preprint series, and it is
-archived in HAL with stable identifiers and full text.
-
-HAL is operated by the CCSD, a CNRS unit. It is multi-tenant: institutions run **portals**
-(`inria.hal.science`, `cea.hal.science`, `theses.hal.science`, …) that are views onto one shared
-database, not separate repositories. A document deposited through the INRIA portal is the same
-record as the one on `hal.science`, with the same identifier. (S1, S5)
-
-## 2. Scope and subject taxonomy
-
-HAL's domain codes are exposed in the API as `domainAllCode_s`. **Note the schema trap:** the
-field is `domainAllCode_s`, *not* `domain_s`; querying `domain_s:info` returns
-`numFound: 0` and will silently give you a wrong answer (verified 2026-09-01, [API]).
-
-Top-level domains, whole archive, 2026-09-01 [API] (S2):
-
-| Code | Domain | Records |
-|---|---|---|
-| `shs` | Humanities & social sciences | 483,057 |
-| `sdv` | Life sciences | 420,391 |
-| `sde` | Environmental sciences | 152,084 |
-| `info` | **Computer science** | **125,067** |
-| `spi` | **Engineering sciences** | **120,084** |
-| `chim` | Chemistry | 93,930 |
-| `phys` | Physics | 84,694 |
-| `math` | Mathematics | 53,470 |
-
-**Caveat, and it is a large one:** these facet counts sum to roughly 1.5M against a total of
-4,648,085 records. The majority of HAL records carry **no domain code at all**. Domain-filtered
-counts are therefore *lower bounds*, not shares. [API] [INF]
-
-Computing subdomains (`info.*`), 2026-09-01 [API] (S2) — the ones a systems/electronics reader
-cares about:
-
-| Code | Area | Records |
-|---|---|---|
-| `info.info-ai` | Artificial intelligence | 42,722 |
-| `info.info-im` | Medical imaging | 41,425 |
-| `info.info-mo` | Modelling & simulation | 28,635 |
-| `info.info-ts` | Signal & image processing | 27,860 |
-| `info.info-ni` | Networking & internet architecture | 26,054 |
-| `info.info-oh` | Other computer science | 19,048 |
-| `info.info-lg` | Machine learning | 15,198 |
-| `info.info-ro` | Robotics | 13,517 |
-| **`info.info-dc`** | **Distributed, parallel & cluster computing** | **13,058** |
-| `info.info-hc` | Human–computer interaction | 12,930 |
-| `info.info-cr` | Cryptography & security | 11,969 |
-| `info.info-se` | Software engineering | 11,145 |
-| `info.info-au` | Automatic control | 10,858 |
-| `info.info-rb` | Robotics (alt.) | 10,348 |
-| `info.info-lo` | Logic in computer science | 8,380 |
-| `info.info-db` | Databases | 8,098 |
-| `info.info-es` | Embedded systems | 7,528 |
-| `info.info-ar` | Hardware architecture | 5,554 |
-| `info.info-pl` | Programming languages | 5,281 |
-
-Engineering subdomains (`spi.*`) relevant to electronics, 2026-09-01 [API] (S2):
-`spi.signal` 37,799 · `spi.mat` 36,710 · `spi.nano` 31,954 · `spi.auto` 31,875 ·
-`spi.nrj` 23,719 · `spi.opti` 20,789 · **`spi.tron` (electronics) 20,471** ·
-`spi.elec` 16,946 · `spi.acou` 13,532.
-
-## 3. Size and growth
-
-All figures retrieved **2026-09-01** from the Solr-style search API, `rows=0`, reading
-`response.numFound` (S2).
-
-- **Total records: 4,648,085** — `?q=*:*&rows=0&wt=json` [API]
-
-Document-type breakdown (`docType_s` facet), top of list [API]:
-
-| Type | Meaning | Count |
-|---|---|---|
-| `ART` | Journal article | 2,237,436 |
-| `COMM` | Conference paper | 1,056,763 |
-| `COUV` | Book chapter | 410,247 |
-| `THESE` | Doctoral thesis | 188,835 |
-| `OUV` | Book | 125,591 |
-| `MEM` | Student dissertation | 96,645 |
-| `UNDEFINED` | — | 93,551 |
-| `POSTER` | Poster | 82,398 |
-| `OTHER` | Other | 80,914 |
-| **`REPORT`** | **Research/technical report** | **80,046** |
-| `HDR` | Habilitation | 10,356 |
-| `PATENT` | Patent / software registration | 8,742 |
-| `SOFTWARE` | Software | 2,119 |
-
-(The facet sums to 4,648,030 against `numFound` 4,648,085 — a 55-record discrepancy, i.e. a
-handful of records carry no `docType_s`. [API] [INF])
-
-**Full text vs. notice** — the single most important number in this record
-(`submitType_s` facet) [API]:
-
-| `submitType_s` | Count | Share |
-|---|---|---|
-| `notice` (metadata only, **no file**) | 2,827,378 | ~60.8% |
-| `file` (full text deposited) | 1,788,688 | ~38.5% |
-| `annex` | 32,019 | ~0.7% |
-
-**Roughly three fifths of HAL is a bibliographic catalogue, not a document archive.** Within
-computer science the ratio is better but still only about half: `domainAllCode_s:info AND
-submitType_s:file` = **62,573** of 125,067 (~50.0%) [API].
-
-Computer-science cross-cuts, 2026-09-01 [API]:
-`info AND COMM` = 71,428 · `info AND THESE` = 2,958 · `info AND REPORT` = 2,927 ·
-`info AND SOFTWARE` = 479.
-
-Language mix (`language_s` facet) [API] — note English *outnumbers* French:
-`en` 2,696,159 · `fr` 1,791,359 · `und` 73,958 · `es` 31,864 · `it` 18,475 · `de` 12,080 ·
-`pt` 9,597 · `ru` 2,518.
-
-**Age.** OAI-PMH `Identify` reports `earliestDatestamp` **2002-09-23** (S4) [API]. CCSD's own
-HAL page says "Créée en 2001, HAL theses (anciennement TEL)…" — that 2001 refers to **TEL**, the
-theses archive, not to HAL itself (S3) [DOC]. The widely repeated "HAL since 2001" claim is
-therefore **not confirmed by a primary source in this pass** — recorded as a conflict, not
-resolved. [NOT-VERIFIED]
-
-## 4. Screening and moderation — what gets in
-
-HAL **does** moderate, and CCSD publishes what the check is. Verbatim from CCSD's own
-documentation (S5) [DOC]:
-
-> « Depuis la création de HAL, on appelle « modération » l'étape de vérification d'un dépôt avant
-> sa mise en ligne : **seuls les dépôts avec un fichier sont vérifiés.** Les références
-> bibliographiques sont quant à elles mises en ligne immédiatement. »
->
-> « Cette étape garantit que les fichiers et les métadonnées qui les décrivent, librement
-> accessibles sur internet, sont exploitables par tout utilisateur. L'utilisateur doit, en effet,
-> pouvoir **ouvrir et/ou télécharger le fichier, lire le texte intégral** du document déposé,
-> **l'utiliser dans le respect de la propriété intellectuelle** et disposer des **informations
-> bibliographiques exactes**. »
-
-So the gate is, precisely:
-
-1. **Only file deposits are moderated.** Metadata-only notices go online immediately, unchecked.
-2. The check is **completeness and usability**: does the PDF open, is it the full text, are the
-   bibliographic metadata correct, are the intellectual-property terms respected (i.e. is the
-   depositor allowed to post this version).
-3. **It is explicitly not peer review**, and it is not a scientific-merit judgement. The published
-   criteria say nothing about whether the result is correct or novel.
-
-Affiliation matters operationally rather than as an admission gate: HAL runs automatic affiliation
-matching and portal administrators "patrol" their portal's deposits (S5) [DOC]. Deposit is open to
-researchers generally; an author who defended a thesis at any university may deposit to HAL theses
-(S3) [DOC].
-
-**A claim I could not confirm:** that deposit in HAL is *mandatory* for French public research.
-Institutional and funder mandates of varying force are widely described, but I did not locate a
-primary CCSD or ministerial document establishing a general legal deposit obligation in this pass.
-**[NOT-VERIFIED]** — treat "mandatory-ish" as folklore until sourced.
-
-## 5. Reliability — what you can and cannot trust
-
-What a HAL deposit **does** guarantee:
-
-- A **stable identifier and a timestamped, immutable version** (`v1`, `v2`, …). Old versions stay
-  reachable; they are not overwritten. Verified: `inria-00609399v1` → HTTP 200 (104,253 B) and
-  `v2` → HTTP 200 (106,610 B), both live, while `v9` → HTTP 404 (S6) [WEB].
-- For file deposits, that a human confirmed the PDF opens and the metadata match it (§4).
-- Long-term hosting by a CNRS national infrastructure — institutionally about as durable as
-  scholarly hosting gets outside arXiv.
-
-What it **does not** guarantee:
-
-- **Nothing about correctness.** No peer review, no scientific-scope screen on merit.
-- **Nothing about whether it is a preprint.** A HAL record is more often a *postprint* — the
-  accepted manuscript of an already-published paper. `ART` (2.2M) dwarfs `REPORT` (80k). If you
-  need to know whether the HAL copy preceded the journal, you must check the record's version
-  dates and the `citationRef_s` field yourself.
-- **Nothing about full text existing.** ~61% of records are notices (§3). A `hal-` identifier in a
-  citation is *not* a promise that you can read the paper.
-
-How to sanity-check a single HAL record: hit
-`https://api.archives-ouvertes.fr/search/?q=halId_s:<id>&fl=*&wt=json` and read `submitType_s`
-(is there a file?), `version_i` (how many revisions?), `docType_s` (report or postprint?) and
-`citationRef_s` (which venue, if any). The `fileMain_s` field gives the canonical PDF URL, which
-follows the pattern `https://<portal>.hal.science/<halId>/document`.
-
-## 6. What you actually find there — examples
-
-- **INRIA research reports** — the real prize. `RR-`/`RT-` numbered technical reports, full text,
-  often the *first* public form of work that later appeared at a conference. Example:
-  `inria-00069994`, *The Coq Proof Assistant, Reference Manual, Version 5.10*, RT-0177, INRIA,
-  **1995** (S7) [API].
-- **Theses** via `theses.hal.science` (formerly TEL): 188,835 `THESE` records archive-wide, 2,958
-  in computer science [API].
-- **Software and formal-methods artefacts**, including software registered through the French IDDN
-  scheme and filed under `docType_s:PATENT` — e.g. `hal-03136256`, *Why3 version 1.0*, IDDN
-  reference `IDDN.FR.001.420003.000.S.P.2019.000.20600` (S7) [API]. This is a HAL-specific quirk
-  worth knowing: **software registrations show up as `PATENT`, not `SOFTWARE`.**
-- **CEA-Leti / CEA work** under the `cea-` prefix (19,582 records) — e.g. `cea-05312386`,
-  *Typestates specification and verification in Frama-C*, FormaliSE 2025 (S7) [API].
-- **LIRMM** robotics and microelectronics under `lirmm-` (8,984 records) — e.g. `lirmm-00798676`,
-  Mansard, Khatib & Kheddar, *A unified approach to integrate unilateral constraints in the stack
-  of tasks*, IEEE Transactions on Robotics, 2009 (S7) [API].
-- **LAAS-CNRS humanoid robotics** — the "Stack of Tasks" line, e.g. `hal-00600959` and
-  `hal-00738243`, both IEEE-RAS Humanoids papers (2011, 2012) (S7) [API].
-
-## 7. Landmark papers (software · distributed systems · databases · electronics · security)
-
-Every row below was confirmed by direct API lookup on **2026-09-01** (S7) [API]. `Preprint first?`
-is answered conservatively; where I could not establish deposit-versus-publication ordering from
-the API fields available, I say so rather than guess.
-
-| Paper | Identifier | Year | Why it matters | Preprint first? |
-|---|---|---|---|---|
-| Shapiro, Preguiça, Baquero, Zawirski, *A comprehensive study of Convergent and Commutative Replicated Data Types* | `inria-00555588` v1 · [link](https://inria.hal.science/inria-00555588v1) | 2011 | **The** CRDT reference text. INRIA Research Report **RR-7506**, 50 pp. Foundation of every modern eventually-consistent store, Automerge/Yjs, collaborative editors | Yes — research report, `docType_s:REPORT`; predates the Oct 2011 SSS paper [INF] |
-| Shapiro, Preguiça, Baquero, Zawirski, *Conflict-free Replicated Data Types* | `inria-00609399` v2 · [link](https://inria.hal.science/inria-00609399v2) | 2011 | INRIA **RR-7687**, 18 pp. The condensed statement of the CRDT result | Yes — report form [INF] |
-| Shapiro, Preguiça, Baquero, Zawirski, *Conflict-free Replicated Data Types* (SSS 2011) | `hal-00932836` v1 · [link](https://inria.hal.science/hal-00932836v1) | 2011 | The peer-reviewed SSS 2011 (Grenoble) paper — the canonical citation | No — this is the conference version; deposit date not verified [NOT-VERIFIED] |
-| Preguiça, Baquero, Shapiro, *Conflict-free Replicated Data Types (CRDTs)* | `hal-01793586` v1 | 2019 | Encyclopedia of Big Data Technologies entry; the readable modern summary | No — book chapter |
-| Leroy, *Formal verification of a realistic compiler* | `inria-00415861` v1 · [link](https://inria.hal.science/inria-00415861v1) | 2009 | **CompCert.** CACM 52(7):107–115. Proof that an optimising C compiler can be machine-verified | No — `ART`, mirrors CACM [INF] |
-| Leroy, *A formally verified compiler back-end* | `inria-00360768` v3 | 2009 | The full CompCert back-end paper, J. Automated Reasoning 43(4):363–446 | No — `ART`; 3 versions on HAL |
-| Cornes, Courant, Filliâtre, Huet, Manoury et al., *The Coq Proof Assistant, Reference Manual, Version 5.10* | `inria-00069994` v1 | **1995** | Primary-source Coq documentation, INRIA **RT-0177**. Underpins CompCert, Iris, seL4-adjacent work | Yes — INRIA report, no journal version |
-| Barras, Boutin, Cornes, Courant, Filliâtre et al., *The Coq Proof Assistant Reference Manual: Version 6.1* | `inria-00069968` v1 | 1997 | INRIA **RT-0203**; the Coq 6.x lineage | Yes — INRIA report |
-| Pedregosa, Varoquaux, Gramfort, Michel, Thirion et al., *Scikit-learn: Machine Learning in Python* | `hal-00650905` v2 · [link](https://inria.hal.science/hal-00650905) | 2011 | JMLR. One of the most-cited software papers in existence; INRIA Parietal origin | No — `ART`, mirrors JMLR [INF] |
-| Duprat, Moya Lamiel, Kirchner, Correnson, Delmas, *Spreading Static Analysis with Frama-C in Industrial Contexts* | `hal-01260276` v1 | 2016 | ERTS 2016. Frama-C in real embedded/avionics practice | No — conference paper |
-| Patte, Prevosto, *Typestates specification and verification in Frama-C* | `cea-05312386` v1 | 2025 | Current CEA formal-methods work; shows the `cea-` portal is live | No — FormaliSE 2025 |
-| Filliâtre, Paskevich, Melquiond, Marché, Bobot, *Why3 version 1.0* | `hal-03136256` v1 | 2018 | Deductive program verification platform, filed as an IDDN software registration | n/a — software registration |
-| Mansard, Khatib, Kheddar, *A unified approach to integrate unilateral constraints in the stack of tasks* | `lirmm-00798676` v1 | 2009 | IEEE Trans. Robotics. Whole-body control; ancestor of modern ROS-adjacent task-priority stacks | No — `ART` |
-| Ramos Ponce, Saab, Hak, Mansard, *Dynamic Motion Capture and Edition using a Stack of Tasks* | `hal-00600959` v1 | 2011 | IEEE-RAS Humanoids 2011, LAAS-CNRS | No — conference paper |
-
-**Searched for and NOT found**, recorded so the next reader does not repeat the work:
-`title_t:"Pinocchio"` restricted to `domainAllCode_s:info` returned `numFound: 0` on 2026-09-01
-[API]. The LAAS *Pinocchio* rigid-body-dynamics library may be in HAL under a different title
-form; **not verified** here — do not cite it from this record.
-
-## 8. Access, APIs and bulk retrieval
-
-All probed **2026-09-01** with **default curl UA — no user-agent substitution was needed anywhere
-on `*.hal.science` or `*.archives-ouvertes.fr`.** [API] [WEB]
-
-- **Search API (Solr-style):** `https://api.archives-ouvertes.fr/search/`
-  Parameters behave like Solr: `q`, `rows`, `wt=json`, `fl`, `facet=true`, `facet.field`,
-  `facet.prefix`, `sort`. `rows=0` + `response.numFound` is the counting idiom. Field schema is
-  published at `https://api.archives-ouvertes.fr/docs/search/schema/fields` (HTTP 200, 631,727 B)
-  (S8). No authentication, no rate-limit refusal encountered across ~60 queries.
-- **OAI-PMH:** `http://api.archives-ouvertes.fr/oai/hal/` — `Identify` returns
-  `repositoryName: HAL`, `earliestDatestamp: 2002-09-23`, `granularity: YYYY-MM-DD`,
-  `deletedRecord: no`. Metadata formats: `oai_dc`, `oai_dcterms`, `oai_openaire`, `oai_datacite`,
-  `xml-tei` (S4) [API]. The TEI format is unusually rich for a repository and is the one to use
-  for structured harvesting.
-- **SWORD deposit:** documented at `https://api.archives-ouvertes.fr/docs/sword` (HTTP 200,
-  31,139 B, title "Import SWORD") (S8) [WEB]. Endpoint *documentation* verified to exist; I did
-  not attempt an authenticated deposit. Behaviour **[NOT-VERIFIED]**.
-- **X2HAL** bulk import from BibTeX is documented (S5) [DOC].
-- **TripleStore / SPARQL** is listed in CCSD's documentation navigation (S5) [DOC]; endpoint not
-  probed. **[NOT-VERIFIED]**
-
-**arXiv bridge — verified, and it is one-directional.** CCSD documents a
-**HAL → arXiv transfer** (S9) [DOC]. Verbatim conditions: offered only if the deposit has files;
-the document type is arXiv-compatible ("all HAL types except: patent, thesis, HDR, image, video,
-map, audio"); no arXiv identifier already in the metadata for a v1. The submission must have an
-English abstract, a chosen domain that is an **arXiv sub**domain (a root domain is rejected), each
-file < 3 MB and ≤ 10 MB total, and LaTeX sources (plus `.bbl`) if the PDF was LaTeX-generated.
-And critically: *"The transfer is carried out when the deposit is put online in HAL. The repository
-is then moderated by the teams of arXiv before it is put online on the archive."*
-**The reverse direction (arXiv → HAL as an automatic bridge) was not confirmed.** HAL records
-*store* arXiv identifiers (S10), and X2HAL imports bibliographic data, but I found no documented
-automatic arXiv-to-HAL push. **[NOT-VERIFIED]**
-
-**Negative controls** (all 2026-09-01) — these matter because HTTP 200 proves nothing:
-
-| Probe | Result | Reading |
-|---|---|---|
-| `q=halId_s:hal-99999999` | `numFound: 0` | API does not invent hits |
-| `q=domainAllCode_s:zzzz` | `numFound: 0` | Bogus facet value returns empty, not everything |
-| `q=domain_s:info` (**wrong field**) | `numFound: 0` | Silent wrong answer — the schema trap of §2 |
-| `https://hal.science/hal-99999999` | HTTP **404** (47,875 B) | Bogus record 404s properly |
-| `https://hal.science/inria-00555588` | HTTP **200** (91,062 B) | Real record resolves |
-| `https://inria.hal.science/inria-00609399v9` | HTTP **404** | Bogus *version* 404s |
-| `https://inria.hal.science/inria-00555588v1/file/RR-7506.pdf` | HTTP **404** | **Guessed** PDF filenames fail — use `fileMain_s` from the API, not a constructed path |
-
-Identifier-prefix census via `halId_s:<prefix>*` wildcard, 2026-09-01 [API] (S2):
-`hal-` 3,621,611 · `tel-` 193,911 · `in2p3-` 47,493 · `medihal-` 42,038 · **`inria-` 29,882** ·
-**`cea-` 19,582** · **`lirmm-` 8,984** · `pastel-` 3,720 · `sic_` 2,571 · `ijn_` 1,147 ·
-`hprints-` 390 · **`irisa-` 0**.
-
-> **Correction to a common assumption:** there is **no `irisa-` identifier prefix** — the wildcard
-> returns 0. IRISA work is present in HAL, but under `hal-` and portal collections, not a legacy
-> prefix. Do not cite an `irisa-` ID. [API]
-
-## 9. Identifiers, versioning and legacy prefixes
-
-- Current form: **`hal-NNNNNNNN`** (8 digits), resolving at `https://hal.science/hal-NNNNNNNN`.
-- **Versions are part of the identifier**: `hal-XXXXXXXXv1`, `v2`, … Every version stays
-  addressable and byte-distinct (§5). Citing without a version number resolves to the latest.
-- **Legacy prefixes** are permanent, not rewritten. `inria-`, `lirmm-`, `cea-`, `in2p3-`,
-  `pastel-`, `sic_`, `ijn_`, `hprints-`, `medihal-` are historical deposit-channel prefixes that
-  remain the record's canonical ID forever. This is why the CRDT paper is **`inria-00555588`** and
-  not a `hal-` number — and why searching only for `hal-*` misses INRIA's back catalogue.
-- **`tel-`** (193,911 records) is the theses archive. `tel.archives-ouvertes.fr` now **redirects to
-  `https://theses.hal.science/`** (verified, HTTP 200 after redirect, 2026-09-01) (S6) [WEB].
-- **Portal subdomains** (`inria.hal.science`, `cea.hal.science`) serve the same record; the API's
-  `uri_s` field tells you the canonical portal URL.
-- HAL also stores **external** identifiers alongside its own: DOI, arXiv ID, PMID, PMCID,
-  **SWHID (Software Heritage)**, PPN (Sudoc), ADS bibcode, and bioRxiv/medRxiv/ChemRxiv DOIs
-  (S10) [DOC]. The SWHID linkage is genuinely useful for software-artefact provenance.
-
-## 10. Licensing and reuse
-
-- **Authors choose the file licence** at deposit time; HAL presents a licence selector, and the
-  licence is a first-class metadata field ("La licence du fichier (uniquement si le fichier est le
-  fichier principal)") (S5) [DOC]. There is **no single default licence** across HAL content — you
-  must read each record.
-- Depositing grants CCSD a distribution licence ("En déposant ce document, le contributeur (je)
-  accorde la licence suivante à HAL") (S5) [DOC]. Exact terms not transcribed here.
-- Publisher-produced files (typeset PDFs) may be deposited only "sous certaines conditions"
-  (S5) [DOC] — this is the publisher-policy question, and HAL's moderation checks it (§4).
-- **Metadata** are openly harvestable via OAI-PMH without restriction encountered; CCSD's own
-  documentation site is published **CC BY 4.0** (footer, S5) [DOC].
-- Embargo is supported (`acces-a-un-fichier-sous-embargo` in the documentation sitemap) (S5) [DOC].
-- I did not find an explicit TDM (text-and-data-mining) policy document. **[NOT-VERIFIED]**
-
-## 11. Caveats and controversies
-
-1. **HAL is not a preprint server, and citing it as one is an error.** ~48% of records are `ART`
-   and ~61% have no file. Check `docType_s` and `submitType_s` before describing a HAL record as a
-   preprint.
-2. **The 2001 founding date is unconfirmed.** CCSD's own text ties 2001 to TEL; the OAI earliest
-   datestamp is 2002-09-23. Report both (§3).
-3. **Domain facets undercount badly** (§2) — most records have no domain code. Never compute a
-   "share of HAL that is computer science" from these numbers.
-4. **The `domain_s` vs `domainAllCode_s` trap** returns a confident, wrong `0`. This is the single
-   most likely way to produce a fabricated-looking statistic about HAL.
-5. **Language.** English (2.70M) exceeds French (1.79M) archive-wide, so the "it's all in French"
-   assumption is wrong — but French-language technical reports are a real and under-indexed part
-   of the CS corpus, and Google Scholar surfaces them poorly.
-6. **Software appears as `PATENT`.** French IDDN software registrations are filed under
-   `docType_s:PATENT` (§6), so a naive `SOFTWARE`-only query (2,119 records) undercounts.
-7. **Moderation covers only file deposits.** Metadata-only notices are unreviewed and go online
-   immediately (§4) — the majority of the archive.
-8. **arXiv transfer is HAL→arXiv only** as documented; the reverse is not established (§8).
-
-## 12. Sources
-
-- **S1** — HAL home page, https://hal.science/ · retrieved 2026-09-01 (HTTP 200, 31,509 B,
-  default UA). Establishes operator and live status.
-- **S2** — HAL search API, `https://api.archives-ouvertes.fr/search/` · retrieved 2026-09-01.
-  All counts in §2, §3 and the prefix census in §8: `?q=*:*&rows=0&wt=json` (total);
-  `&facet=true&facet.field=docType_s|submitType_s|language_s|domainAllCode_s`;
-  `&facet.prefix=info|spi`; `q=halId_s:<prefix>*`.
-- **S3** — CCSD, "Archive ouverte nationale" (HAL), https://www.ccsd.cnrs.fr/hal/ · retrieved
-  2026-09-01 (HTTP 200, 188,614 B). Source of "Créée en 2001, HAL theses (anciennement TEL)" and
-  of the HAL-SHS 2005 date. Supports the §3 date conflict.
-- **S4** — HAL OAI-PMH `Identify` and `ListMetadataFormats`,
-  `https://api.archives-ouvertes.fr/oai/hal/?verb=Identify` · retrieved 2026-09-01.
-  `earliestDatestamp` 2002-09-23, formats list.
-- **S5** — CCSD HAL documentation, https://documentation.hal.science/ · retrieved 2026-09-01.
-  Moderation text quoted in §4 from
-  `https://documentation.hal.science/administrer-un-portail/verification-des-depots-avant-leur-mise-en-ligne/`
-  (HTTP 200, 57,398 B). Deposit/licence text from
-  `https://documentation.hal.science/deposer/`. Sitemap (217 URLs) used to locate pages.
-  **Retrieval note:** `doc.archives-ouvertes.fr` is a stale host — most paths return HTTP 404 with
-  the notice *"La documentation HAL a fait peau neuve en migrant vers un nouveau site."* Use
-  `documentation.hal.science`.
-- **S6** — Live URL probes on `hal.science` / `inria.hal.science` / `tel.archives-ouvertes.fr` ·
-  2026-09-01. Version and negative-control results in §5, §8, §9.
-- **S7** — HAL search API record lookups by title and `halId_s` · 2026-09-01. Every row of the §7
-  table and the §6 examples, with `halId_s`, `version_i`, `docType_s`, `producedDateY_i`,
-  `domainAllCode_s`, `uri_s`, `fileMain_s`.
-- **S8** — HAL API documentation, `https://api.archives-ouvertes.fr/docs`,
-  `/docs/search`, `/docs/search/schema/fields`, `/docs/sword` · retrieved 2026-09-01 (all HTTP
-  200). Supports §8.
-- **S9** — CCSD, "Arxiv transfert", https://documentation.hal.science/en/arxiv-transfer/ ·
-  retrieved 2026-09-01. All HAL→arXiv conditions quoted in §8.
-- **S10** — CCSD, "Identifiants utilisés dans HAL",
-  https://documentation.hal.science/en/identifiants-utilises-dans-hal/ · retrieved 2026-09-01.
-  External identifier list in §9 (DOI, arXiv, PMID, PMCID, SWHID, PPN, ADS bibcode, bioRxiv,
-  ChemRxiv, medRxiv, InSPIRE).
-
-### Retrieval / crawler note
-
-**No user-agent substitution was required for any HAL host.** Default `curl` obtained HTTP 200
-from `hal.science`, `inria.hal.science`, `theses.hal.science`, `api.archives-ouvertes.fr`,
-`documentation.hal.science` and `www.ccsd.cnrs.fr`, across roughly 60 API calls and 30 page
-fetches on 2026-09-01, with no rate limiting, no CAPTCHA and no bot-block page. HAL is one of the
-most scripting-friendly scholarly hosts in this survey. The only failing host was the deprecated
-`doc.archives-ouvertes.fr`, which fails for content-migration reasons, not bot filtering.
diff --git a/research/preprint-repositories/landmark-papers.md b/research/preprint-repositories/landmark-papers.md
deleted file mode 100644
index b6870e0..0000000
--- a/research/preprint-repositories/landmark-papers.md
+++ /dev/null
@@ -1,369 +0,0 @@
-# Landmark papers, by field and by server
-
-Which preprint server did the work you actually depend on land on? This document collects the
-**verified** entries across the whole pass, reorganised by *field* rather than by repository, and
-answers the practical question: **when I go looking for foundational systems, hardware or software
-work, where is it?**
-
-- **Compiled:** 2026-09-01 / 2026-09-02.
-- **Verification standard:** every identifier below was individually fetched from its server's API
-  or abstract page and its title machine-checked against the response. Entries that could not be
-  confirmed were **dropped**, not hedged. See [`README.md § Evidence and method`](README.md#evidence-and-method).
-- **Totals verified in this pass:** **79** on [arXiv](arxiv.md), **41** on
-  [Cryptology ePrint](cryptology-eprint-archive.md), **14** on [HAL](hal.md), plus entries on
-  [Optimization Online](optimization-online.md), [ECSarXiv](ecsarxiv.md), [Zenodo](zenodo.md) and
-  [bioRxiv](biorxiv-and-medrxiv.md).
-- This file is a **curated cross-section**. The complete per-server tables live in each record's §7.
-
-## How to read the "preprint first?" column
-
-Taken from the arXiv record's method note, and applied consistently:
-
-- **proven** — the record carries venue metadata dated *later* than v1. Provable from metadata alone.
-- **de facto** — no venue metadata exists at all. The preprint is the only citable record the
-  authors ever supplied, and it is what the field cites.
-- **companion** — the record declares itself the full or extended version of a paper at a named
-  venue. Not a precedence claim.
-
----
-
-## 1. The single most important finding
-
-**The canonical distributed-systems and database papers are not on any preprint server.**
-
-This is not a gap in our search; it is a property of the field. Systems research published through
-OSDI, SOSP, NSDI, VLDB and SIGMOD in the 2000s and early 2010s went to the ACM and USENIX digital
-libraries and nowhere else. Verified absent from arXiv by title search (arXiv §7.10):
-
-| Paper | Venue | arXiv title search |
-|---|---|---|
-| MapReduce: Simplified Data Processing on Large Clusters | OSDI 2004 | **0 hits** |
-| The Google File System | SOSP 2003 | **0 hits** |
-| Bigtable: A Distributed Storage System for Structured Data | OSDI 2006 | 2 hits, **neither is the paper** |
-| Dynamo: Amazon's Highly Available Key-value Store | SOSP 2007 | **0 hits** |
-| In Search of an Understandable Consensus Algorithm (**Raft**) | USENIX ATC 2014 | **0 hits** |
-| Paxos Made Simple | SIGACT News 2001 | 1 hit — *"Moderately Complex Paxos Made Simple"*, a different 2017 paper |
-| ZooKeeper: Wait-free coordination for internet-scale systems | USENIX ATC 2010 | 2 hits, **neither is the paper** |
-| Spanner: Google's Globally-Distributed Database | OSDI 2012 | 291 hits — **all about *graph* spanners**, an unrelated combinatorics object |
-| Resilient Distributed Datasets (**Spark**) | NSDI 2012 | **0 hits** |
-| RAMCloud | SOSP / TOCS | **0 hits** |
-| Bitcoin: A Peer-to-Peer Electronic Cash System | self-published | **0 hits** |
-| Flipping Bits in Memory Without Accessing Them (**RowHammer**) | ISCA 2014 | 1 hit — the **2023 retrospective**, not the original |
-| seL4: Formal verification of an OS kernel | SOSP 2009 | 5 hits, **none is the original** |
-| CompCert (formally verified C compiler) | POPL 2006 / CACM 2009 | 4 hits, **none is the original** — but see §5, it is on **HAL** |
-| BBR: Congestion-Based Congestion Control | ACM Queue 2016 | 34 hits, **none is the original** |
-| The Chubby lock service | OSDI 2006 | **[NOT-VERIFIED]** — not separately probed; nothing surfaced adjacently |
-
-The `Spanner` case is the trap worth remembering: a title search returns **291 confident hits**, and
-every one of them is about a different object. A keyword count is not a literature search.
-
-The equivalent boundary exists on Cryptology ePrint. Verified **absent** there: the original
-HotStuff, the original Algorand, ROCA, the original RowHammer paper, Spectre/Meltdown, the PRESENT
-cipher paper, the Keccak/SHA-3 specification, "Short Signatures from the Weil Pairing", Dwork et
-al.'s differential-privacy paper, TPM-FAIL, Logjam and DROWN. **ePrint is dominant for cryptology,
-not for systems security generally.**
-
----
-
-## 2. Distributed systems and consensus
-
-Split across three servers, and the split is systematic: **protocol designs with security proofs go
-to ePrint; systems papers go to arXiv; the French contributions go to HAL.**
-
-### On arXiv
-
-| Paper | arXiv ID | v1 | Why it matters | First? |
-|---|---|---|---|---|
-| Majority is not Enough: Bitcoin Mining is Vulnerable | [1311.0243](https://arxiv.org/abs/1311.0243) | 2013-11-01 | Selfish mining: <50% attacks on Bitcoin | de facto |
-| Lightweight Asynchronous Snapshots for Distributed Dataflows | [1506.08603](https://arxiv.org/abs/1506.08603) | 2015-06-29 | **Apache Flink's checkpointing algorithm** | de facto |
-| Algorand | [1607.01341](https://arxiv.org/abs/1607.01341) | 2016-07-05 | Byzantine agreement via VRFs; now at v9 | de facto |
-| Casper the Friendly Finality Gadget | [1710.09437](https://arxiv.org/abs/1710.09437) | 2017-10-25 | PoS finality; basis of Ethereum's transition | de facto |
-| HotStuff: BFT Consensus in the Lens of Blockchain | [1803.05069](https://arxiv.org/abs/1803.05069) | 2018-03-13 | Linear-communication pipelined BFT; basis of DiemBFT | de facto |
-| The latest gossip on BFT consensus (**Tendermint**) | [1807.04938](https://arxiv.org/abs/1807.04938) | 2018-07-13 | The Tendermint consensus specification | de facto |
-| Study of Firecracker MicroVM | [2005.12821](https://arxiv.org/abs/2005.12821) | 2020-05-26 | microVM isolation — one of only **1,455 papers in all of `cs.OS`** | de facto |
-| TensorFlow: Large-Scale ML on Heterogeneous Distributed Systems | [1603.04467](https://arxiv.org/abs/1603.04467) | 2016-03-14 | The TensorFlow whitepaper — **never a venue paper** | de facto |
-| Ray: A Distributed Framework for Emerging AI Applications | [1712.05889](https://arxiv.org/abs/1712.05889) | 2017-12-16 | Task+actor model for distributed ML | de facto |
-
-### On Cryptology ePrint
-
-| Paper | ID | Recv | v | Publication info | First? |
-|---|---|---|---|---|---|
-| The Bitcoin Backbone Protocol: Analysis and Applications | [2014/765](https://eprint.iacr.org/2014/765) | 2014-09-30 | **17** | EUROCRYPT 2015 | **yes** |
-| Ouroboros: A Provably Secure Proof-of-Stake Blockchain Protocol | [2016/889](https://eprint.iacr.org/2016/889) | 2016-09-14 | 8 | CRYPTO 2017 | **yes, ~10 months** |
-| ALGORAND AGREEMENT: Super Fast and Partition Resilient BA | [2018/377](https://eprint.iacr.org/2018/377) | 2018-04-30 | 2 | Preprint | **never formally published** |
-| Compact Multi-Signatures for Smaller Blockchains (**BLS aggregation**) | [2018/483](https://eprint.iacr.org/2018/483) | 2018-05-23 | 2 | Preprint | **never formally published** |
-| Sync HotStuff: Simple and Practical Synchronous SMR | [2019/270](https://eprint.iacr.org/2019/270) | 2019-03-12 | 6 | Preprint | **yes** |
-
-> Two of the five above were **never formally published anywhere**. If you cite BLS aggregate
-> signatures or Algorand Agreement, the ePrint report *is* the paper.
-
-### CRDTs — the case where the preprint server matters most
-
-The conflict-free replicated data type literature is the clearest example in this whole survey of
-why knowing the right server matters. **The originals are on HAL, not arXiv.**
-
-| Paper | HAL identifier | Year | Why it matters |
-|---|---|---|---|
-| Shapiro, Preguiça, Baquero, Zawirski — *A comprehensive study of Convergent and Commutative Replicated Data Types* | [`inria-00555588`](https://inria.hal.science/inria-00555588v1) | 2011 | **The** CRDT reference text. INRIA **RR-7506**, 50 pp. Foundation of Automerge, Yjs, Riak, Redis CRDTs and every modern eventually-consistent store |
-| Shapiro et al. — *Conflict-free Replicated Data Types* | [`inria-00609399`](https://inria.hal.science/inria-00609399v2) | 2011 | INRIA **RR-7687**, 18 pp. The condensed statement of the result |
-| Shapiro et al. — *Conflict-free Replicated Data Types* (SSS 2011) | [`hal-00932836`](https://inria.hal.science/hal-00932836v1) | 2011 | The peer-reviewed SSS 2011 conference version — the canonical citation |
-
-arXiv carries only a **2018 encyclopedia entry** ([1805.06358](https://arxiv.org/abs/1805.06358))
-and a **2018 overview** ([1806.10254](https://arxiv.org/abs/1806.10254)). A title search on arXiv
-for "Conflict-free Replicated Data Types" returns 11 hits and **none is the 2011 original**.
-**Cite `inria-00555588` for priority.**
-
----
-
-## 3. Databases
-
-The thinnest category in the entire survey — four verified arXiv entries, and nothing meaningful
-anywhere else. Database research is a conference-proceedings field that never adopted preprinting.
-
-| Paper | arXiv ID | v1 | Why it matters | First? |
-|---|---|---|---|---|
-| The Missing Piece in Complex Analytics: Low Latency, Scalable Model Management | [1409.3809](https://arxiv.org/abs/1409.3809) | 2014-09-12 | Early framing of model management as a DB problem (CIDR line) | de facto |
-| **The Case for Learned Index Structures** | [1712.01208](https://arxiv.org/abs/1712.01208) | 2017-12-04 | Launched the entire learned-index / learned-systems programme | de facto |
-| LSM-based Storage Techniques: A Survey | [1812.07527](https://arxiv.org/abs/1812.07527) | 2018-12-18 | The reference survey for LSM engines | **proven** (VLDBJ 2019) |
-| Neo: A Learned Query Optimizer | [1904.03711](https://arxiv.org/abs/1904.03711) | 2019-04-07 | Learned query optimisation | **proven** (PVLDB 2019) |
-
-Relevant adjacent work sits under privacy rather than data management — **Path ORAM**
-([2013/280](https://eprint.iacr.org/2013/280), ePrint, 2013-05-16, posted before CCS 2013) is the
-oblivious-storage result that encrypted-database designs build on.
-
----
-
-## 4. Computer architecture, hardware and accelerators
-
-| Paper | arXiv ID | v1 | Why it matters | First? |
-|---|---|---|---|---|
-| EIE: Efficient Inference Engine on Compressed Deep Neural Network | [1602.01528](https://arxiv.org/abs/1602.01528) | 2016-02-04 | Sparse-weight inference accelerator; ISCA-line work | de facto |
-| Efficient Processing of Deep Neural Networks: A Tutorial and Survey | [1703.09039](https://arxiv.org/abs/1703.09039) | 2017-03-27 | Sze et al. — the standard tutorial on DNN accelerator design | de facto |
-| **In-Datacenter Performance Analysis of a Tensor Processing Unit** | [1704.04760](https://arxiv.org/abs/1704.04760) | 2017-04-16 | Google's TPUv1 — the defining industrial domain-specific-architecture measurement paper | de facto |
-| Eyeriss v2: A Flexible Accelerator for Emerging DNNs on Mobile Devices | [1807.07928](https://arxiv.org/abs/1807.07928) | 2018-07-10 | Flexible NoC dataflow accelerator for sparse/compact DNNs | de facto |
-| **The gem5 Simulator: Version 20.0+** | [2007.03152](https://arxiv.org/abs/2007.03152) | 2020-07-07 | The citable reference for the standard architecture simulator | de facto |
-| Deep Compression (pruning + quantisation + Huffman coding) | [1510.00149](https://arxiv.org/abs/1510.00149) | 2015-10-01 | Model compression pipeline that drove a generation of accelerator design | de facto |
-| FlashAttention: IO-Awareness | [2205.14135](https://arxiv.org/abs/2205.14135) | 2022-05-27 | An attention kernel that is really a memory-hierarchy result | de facto |
-
-**A caution about volume.** `cs.AR` (Hardware Architecture) holds **8,932** papers and `cs.ET`
-(Emerging Technologies) **7,815**, against `cs.LG`'s **283,807**. Computer architecture is a
-*small* presence on arXiv. Its principal venues — ISCA, MICRO, HPCA, ASPLOS, DAC — remain
-proceedings-first.
-
-**No canonical RISC-V paper is on arXiv.** 250 hits for `ti:"RISC-V" AND cat:cs.AR`, but the
-foundational documents are Berkeley EECS technical reports and RISC-V International specifications,
-neither of which is a preprint deposit.
-
----
-
-## 5. Embedded, side-channel and hardware security
-
-**This is the section where Cryptology ePrint is irreplaceable**, and it is the strongest reason for
-an embedded engineer to know the server exists. The CHES → TCHES and FSE → ToSC diamond-open-access
-pipelines mean ePrint functions as *primary* literature for hardware security, not as a shadow copy.
-
-| Paper | ID | Recv | Publication info | First? |
-|---|---|---|---|---|
-| Provably Secure Higher-Order Masking of AES | [2010/441](https://eprint.iacr.org/2010/441) | 2010-08-17 | full version, **CHES 2010** | companion |
-| High-speed high-security signatures (**Ed25519**) | [2011/368](https://eprint.iacr.org/2011/368) | 2011-07-10 | full version, **CHES** | companion |
-| Threshold Implementations of all 3x3 and 4x4 S-boxes | [2012/300](https://eprint.iacr.org/2012/300) | 2012-06-03 | extended version, **CHES 2012** | **yes, pre-CHES** |
-| **Flush+Reload**: a High Resolution, Low Noise, L3 Cache Side-Channel Attack | [2013/448](https://eprint.iacr.org/2013/448) | 2013-07-22 | USENIX Security 2014 | **yes, ~1 year** |
-| CacheBleed: A Timing Attack on OpenSSL Constant Time RSA | [2016/224](https://eprint.iacr.org/2016/224) | 2016-03-01 | Preprint | **yes** |
-| ECDSA Key Extraction from Mobile Devices via Nonintrusive Physical Side Channels | [2016/230](https://eprint.iacr.org/2016/230) | 2016-03-02 | ACM CCS 2016 | **yes** |
-| Number "Not Used" Once — practical fault attack on **pqm4** NIST candidates | [2018/211](https://eprint.iacr.org/2018/211) | 2018-02-26 | Preprint | **never formally published** |
-| Differential Power Analysis of XMSS and SPHINCS | [2018/673](https://eprint.iacr.org/2018/673) | 2018-07-13 | COSADE 2018 | companion |
-| **pqm4**: Testing and Benchmarking NIST PQC on **ARM Cortex-M4** | [2019/844](https://eprint.iacr.org/2019/844) | 2019-07-19 | Preprint | **never formally published** |
-| LadderLeak: Breaking ECDSA With Less Than One Bit Of Nonce Leakage | [2020/615](https://eprint.iacr.org/2020/615) | 2020-05-25 | ACM CCS 2020 | **yes** |
-| **Minerva**: The curse of ECDSA nonces (smartcards / secure elements) | [2020/728](https://eprint.iacr.org/2020/728) | 2020-06-17 | **TCHES 2020** | **yes** |
-| **Ascon** PRF, MAC, and Short-Input MAC (NIST lightweight-crypto winner family) | [2021/1574](https://eprint.iacr.org/2021/1574) | 2021-12-03 | CT-RSA 2024 | **yes, ~2.5 years** |
-| Combined Fault Injection + Side-Channel for **Android Secure-Boot Bypassing** | [2022/602](https://eprint.iacr.org/2022/602) | 2022-05-17 | CARDIS 2022 | **yes** |
-| When Frodo Flips: End-to-End Key Recovery on FrodoKEM via **Rowhammer** | [2022/952](https://eprint.iacr.org/2022/952) | 2022-07-23 | ACM CCS 2022 | **yes** |
-| To Be, or Not to Be Stateful: **Post-Quantum Secure Boot** using Hash-Based Signatures | [2022/1198](https://eprint.iacr.org/2022/1198) | 2022-09-11 | ASHES 2022 | **yes** |
-| Recommendations for the Design and Validation of a Physical **TRNG** in a Cryptographic System | [2024/301](https://eprint.iacr.org/2024/301) | 2024-02-22 | Preprint (**CC0**) | **never formally published** |
-| Optimized Implementations of Keccak, Kyber, and Dilithium on the **MSP430** | [2026/235](https://eprint.iacr.org/2026/235) | 2026-02-12 | **TCHES 2026** | **yes** |
-
-Four of the seventeen were **never formally published** — including `pqm4`, which is the de facto
-benchmark suite for post-quantum crypto on Cortex-M, and the TRNG design-and-validation
-recommendations. For microcontroller cryptography, ePrint is not a preview of the literature; it
-*is* the literature.
-
-### The microarchitectural attacks are on arXiv, not ePrint
-
-| Paper | arXiv ID | v1 | Why it matters |
-|---|---|---|---|
-| **Spectre Attacks: Exploiting Speculative Execution** | [1801.01203](https://arxiv.org/abs/1801.01203) | 2018-01-03 | Broke the CPU security model industry-wide |
-| **Meltdown** | [1801.01207](https://arxiv.org/abs/1801.01207) | 2018-01-03 | Out-of-order execution reads kernel memory; forced KPTI worldwide |
-| RowHammer: A Retrospective | [1904.09724](https://arxiv.org/abs/1904.09724) | 2019-04-22 | Mutlu & Kim's synthesis of DRAM disturbance research |
-| Retrospective: Flipping Bits in Memory Without Accessing Them | [2306.16093](https://arxiv.org/abs/2306.16093) | 2023-06-28 | Retrospective on the 2014 original, **which is not on arXiv** |
-
-### The one break that defines the server
-
-**SIKE.** NIST advanced SIKE to the fourth round of its post-quantum standardisation process on
-**2022-07-05**. Castryck and Decru posted *An efficient key recovery attack on SIDH* as
-[**2022/975**](https://eprint.iacr.org/2022/975) at **2022-07-30 07:20:07 UTC** — twenty-five days
-later, and roughly **nine months before** the EUROCRYPT 2023 paper existed. A NIST candidate was
-killed by an unreviewed ePrint report. This is simultaneously the best argument for reading ePrint
-and the clearest illustration that its contents are not reviewed.
-
----
-
-## 6. Programming languages, compilers, formal methods and networking
-
-The strongest HAL cluster after CRDTs, plus a thin arXiv presence.
-
-### On HAL
-
-| Paper | HAL identifier | Year | Why it matters |
-|---|---|---|---|
-| Leroy — *Formal verification of a realistic compiler* | `inria-00415861` | 2009 | **CompCert.** CACM 52(7). Proof that an optimising C compiler can be machine-verified |
-| Leroy — *A formally verified compiler back-end* | `inria-00360768` | 2009 | The full CompCert back-end, J. Automated Reasoning 43(4):363–446 |
-| Cornes, Courant, Filliâtre, Huet, Manoury et al. — *The Coq Proof Assistant, Reference Manual, Version 5.10* | `inria-00069994` | **1995** | Primary-source Coq documentation, INRIA **RT-0177** |
-| Barras, Boutin, Cornes, Courant, Filliâtre et al. — *Coq Reference Manual: Version 6.1* | `inria-00069968` | 1997 | The Coq 6.x lineage |
-| Filliâtre, Paskevich, Melquiond, Marché, Bobot — *Why3 version 1.0* | `hal-03136256` | 2018 | Deductive program verification platform |
-| Duprat, Moya Lamiel, Kirchner, Correnson, Delmas — *Spreading Static Analysis with Frama-C in Industrial Contexts* | `hal-01260276` | 2016 | **Frama-C in real embedded/avionics practice** |
-| Patte, Prevosto — *Typestates specification and verification in Frama-C* | `cea-05312386` | 2025 | Current CEA formal-methods work |
-| Pedregosa, Varoquaux, Gramfort, Michel, Thirion et al. — *Scikit-learn: Machine Learning in Python* | `hal-00650905` | 2011 | One of the most-cited software papers in existence |
-| Mansard, Khatib, Kheddar — *A unified approach to integrate unilateral constraints in the stack of tasks* | `lirmm-00798676` | 2009 | IEEE T-RO. Whole-body control; ancestor of modern task-priority stacks |
-
-Note the dates: **Coq's 1995 reference manual is on HAL and nowhere else in this survey.** If you
-need primary sources for the French formal-methods and verified-compiler tradition, HAL is the only
-server that has them.
-
-### On arXiv
-
-| Paper | arXiv ID | v1 | Why it matters | First? |
-|---|---|---|---|---|
-| **MLIR: A Compiler Infrastructure for the End of Moore's Law** | [2002.11054](https://arxiv.org/abs/2002.11054) | 2020-02-25 | Multi-level IR; now the substrate for ML compilers and much EDA tooling | de facto |
-| **Programming Protocol-Independent Packet Processors (P4)** | [1312.1719](https://arxiv.org/abs/1312.1719) | 2013-12-05 | Defined programmable data planes | de facto |
-| Channel polarization: capacity-achieving codes for symmetric binary-input memoryless channels | [0807.3917](https://arxiv.org/abs/0807.3917) | 2008-07-24 | **Arıkan's polar codes — adopted for 5G NR control channels**; at v5 | de facto |
-| What Will 5G Be? | [1405.2957](https://arxiv.org/abs/1405.2957) | 2014-05-12 | The agenda-setting 5G survey | ≈ same-year |
-
----
-
-## 7. Protocol security — TLS and Signal
-
-| Paper | ID | Recv | Publication info | First? |
-|---|---|---|---|---|
-| A Cryptographic Analysis of the **TLS 1.3** Handshake Protocol Candidates | [2015/914](https://eprint.iacr.org/2015/914) | 2015-09-22 | ACM CCS 2015 | **yes — analysed drafts pre-RFC** |
-| A Formal Security Analysis of the **Signal** Messaging Protocol | [2016/1013](https://eprint.iacr.org/2016/1013) | 2016-10-27 | IEEE EuroS&P 2017 | **yes** |
-| A Cryptographic Analysis of the TLS 1.3 Handshake Protocol (journal version) | [2020/1044](https://eprint.iacr.org/2020/1044) | 2020-08-28 | **JoC 2021** | **yes** |
-
-The TLS 1.3 entry is the interesting one: the analysis was posted **while the RFC was still in
-draft**, and fed back into the standard. That is the mechanism by which an unreviewed preprint
-server does load-bearing work in protocol design.
-
----
-
-## 8. Zero-knowledge, FHE and post-quantum — all ePrint
-
-These fields preprint on ePrint essentially universally. Two entries below have **never been
-formally published** and are nonetheless deployed in production systems worldwide.
-
-| Paper | ID | Recv | v | Publication info | First? |
-|---|---|---|---|---|---|
-| Pinocchio: Nearly Practical Verifiable Computation | [2013/279](https://eprint.iacr.org/2013/279) | 2013-05-16 | 1 | full version of IEEE S&P 2013 | companion |
-| Zerocash: Decentralized Anonymous Payments from Bitcoin | [2014/349](https://eprint.iacr.org/2014/349) | 2014-05-19 | 1 | IEEE S&P 2014 | companion |
-| On the Size of Pairing-based Non-interactive Arguments (**Groth16**) | [2016/260](https://eprint.iacr.org/2016/260) | 2016-03-08 | 2 | EUROCRYPT 2016 | **yes** |
-| Bulletproofs: Short Proofs for Confidential Transactions and More | [2017/1066](https://eprint.iacr.org/2017/1066) | 2017-11-10 | **14** | IEEE S&P 2018 | **yes** |
-| Scalable, transparent, post-quantum secure computational integrity (**STARK**) | [2018/046](https://eprint.iacr.org/2018/046) | 2018-01-10 | 4 | Preprint | **never formally published** |
-| **PLONK** | [2019/953](https://eprint.iacr.org/2019/953) | 2019-08-21 | **44** | Preprint | **never formally published** |
-| Fully Homomorphic Encryption without Bootstrapping (**BGV**) | [2011/277](https://eprint.iacr.org/2011/277) | 2011-05-28 | 3 | "Unknown where it was published" | **yes** |
-| Somewhat Practical Fully Homomorphic Encryption (**BFV**) | [2012/144](https://eprint.iacr.org/2012/144) | 2012-03-22 | 1 | "Unknown where it was published" | **yes** |
-| Homomorphic Encryption for Arithmetic of Approximate Numbers (**CKKS**) | [2016/421](https://eprint.iacr.org/2016/421) | 2016-05-01 | 5 | ASIACRYPT 2017 | **yes, ~18 months** |
-| Towards quantum-resistant cryptosystems from supersingular isogenies (**SIDH**) | [2011/506](https://eprint.iacr.org/2011/506) | 2011-09-18 | 2 | PQCrypto 2011 | companion |
-| SPHINCS: practical stateless hash-based signatures | [2014/795](https://eprint.iacr.org/2014/795) | 2014-10-10 | 2 | EUROCRYPT 2015 | **yes** |
-| Post-quantum key exchange — a new hope (**NewHope**) | [2015/1092](https://eprint.iacr.org/2015/1092) | 2015-11-10 | 9 | USENIX Security 2016 | **yes** |
-| CRYSTALS-Dilithium (**→ NIST ML-DSA**) | [2017/633](https://eprint.iacr.org/2017/633) | 2017-06-27 | 2 | **TCHES 2018** | **yes** |
-| CRYSTALS-Kyber (**→ NIST ML-KEM**) | [2017/634](https://eprint.iacr.org/2017/634) | 2017-06-27 | 2 | EuroS&P 2018 | **yes** |
-| **An efficient key recovery attack on SIDH** (killed SIKE) | [2022/975](https://eprint.iacr.org/2022/975) | 2022-07-30 | 4 | EUROCRYPT 2023 | **yes, ~9 months** |
-
-**PLONK is at version 44 and was never published.** Both NIST post-quantum standards — ML-KEM and
-ML-DSA — were on ePrint years before standardisation.
-
----
-
-## 9. Machine learning and ML systems — arXiv, effectively exclusively
-
-Thirty foundational and seventeen systems entries were verified; the complete tables are in
-[arXiv §7.1 and §7.2](arxiv.md). The pattern is uniform and worth stating once rather than
-reproducing: **almost every one is marked "de facto"** — no venue metadata at all. For this
-field the arXiv document *is* the version of record, permanently.
-
-A representative slice:
-
-| Paper | arXiv ID | v1 | Note |
-|---|---|---|---|
-| **Attention Is All You Need** | [1706.03762](https://arxiv.org/abs/1706.03762) | 2017-06-12 | The Transformer. Now at **v7**, last updated 2023-08-02 |
-| Adam: A Method for Stochastic Optimization | [1412.6980](https://arxiv.org/abs/1412.6980) | 2014-12-22 | The default optimiser of deep learning; now at **v9** |
-| Deep Residual Learning for Image Recognition (**ResNet**) | [1512.03385](https://arxiv.org/abs/1512.03385) | 2015-12-10 | The author comment reads **"Tech report"** |
-| Language Models are Few-Shot Learners (**GPT-3**) | [2005.14165](https://arxiv.org/abs/2005.14165) | 2020-05-28 | In-context learning at 175B parameters |
-| Training Compute-Optimal LLMs (**Chinchilla**) | [2203.15556](https://arxiv.org/abs/2203.15556) | 2022-03-29 | Reset industry training budgets |
-| ZeRO: Memory Optimizations Toward Trillion Parameter Models | [1910.02054](https://arxiv.org/abs/1910.02054) | 2019-10-04 | Sharded optimiser state; DeepSpeed's core |
-| Efficient Memory Management for LLM Serving with **PagedAttention** (vLLM) | [2309.06180](https://arxiv.org/abs/2309.06180) | 2023-09-12 | Virtual-memory paging applied to the KV cache |
-| PyTorch: An Imperative Style, High-Performance DL Library | [1912.01703](https://arxiv.org/abs/1912.01703) | 2019-12-03 | The PyTorch reference paper |
-| **DeepSeek-R1** | [2501.12948](https://arxiv.org/abs/2501.12948) | 2025-01-22 | `journal_ref` = *Nature* 645:633–638 (2025) — **proven** arXiv-first |
-
-Only **6 of the 79** verified arXiv landmarks carry a `journal_ref` at all.
-
----
-
-## 10. Optimisation, solvers and scientific software
-
-Not glamorous, but these are the entries a working engineer is most likely to actually depend on.
-
-### Optimization Online
-
-| Eprint | Why it matters |
-|---|---|
-| **IPOPT** (`2004/03/836`) | The interior-point NLP solver embedded in a generation of engineering tooling |
-| **Computing in Operations Research using Julia** (`2013/05/3883`) | JuMP's ancestor |
-| **QUBO tutorial** (`2019/01/7014`) | The reference introduction for quantum-annealing and Ising-machine formulations |
-| SCIP Optimization Suite 9.0 / 10.0 | The release documentation for the standard academic MILP solver |
-
-The durability result matters as much as the content: `DB_HTML/2004/03/836.html` **still resolves
-22 years later**. The caveat is that old `DB_FILE/*.pdf` links now land on the HTML abstract page.
-
-### ECSarXiv — batteries, MEMS and semiconductor process
-
-Only 323 preprints exist, but the subject graft includes *Atomic Layer Deposition/Etching*,
-*High-k / Low-k Dielectrics*, *Interconnects*, *Group III-V Semiconductors* and *VLSI and Circuits,
-Embedded and Hardware Systems*. Verified content includes the **PyBaMM** announcement, nonlinear
-EIS of Li-ion cells, a stretched-exponential capacity-fade master curve, lithium-plating detection,
-a high-temperature silicon **MEMS pressure-sensor bridge circuit**, MOS gas sensors, KOH-IPA wafer
-etching and low-temperature Cu-Cu wafer bonding. **44 records are deposited under LGPL-3.0** —
-i.e. they are software.
-
-### Zenodo — where the software itself lives
-
-Zenodo hosts few preprints (3.4% of records) but **284,518 software concept records across 712,318
-versions** — a 2.5× version-to-concept ratio against 1.14× corpus-wide, which is direct quantitative
-evidence that the GitHub-release-to-DOI pipeline is being used at scale. This is where conference
-artifact-evaluation packages, firmware releases and KiCad projects get citable identifiers. See
-[Zenodo § concept vs version DOI](zenodo.md) — **cite the version DOI**, not the concept DOI.
-
-### bioRxiv — the scientific-software channel nobody expects
-
-`Bioinformatics` is **30,363** preprints, 8.7% of bioRxiv and its #3 category in 2025. Combined
-with a **69–78% eventual-publication rate** for mature cohorts, it is measurably the most reliable
-large server in this survey — and a great deal of widely used scientific software was announced
-there first.
-
----
-
-## 11. Summary — where to look, by field
-
-| If you are looking for… | Go to | Do **not** rely on |
-|---|---|---|
-| Classic distributed systems / databases (pre-2015) | **ACM DL, USENIX** — not a preprint server | arXiv (verified absent) |
-| Modern consensus protocols with proofs | **Cryptology ePrint** | arXiv alone |
-| Modern distributed systems / dataflow | **arXiv `cs.DC`** | — |
-| CRDTs, CompCert, Coq, Frama-C | **HAL** | arXiv (only later derivatives) |
-| ML, ML systems, inference infrastructure | **arXiv** | anywhere else |
-| Side-channel, fault injection, MCU crypto | **Cryptology ePrint** | arXiv |
-| Speculative-execution and DRAM attacks | **arXiv `cs.CR`** | ePrint (verified absent) |
-| Computer architecture | **ISCA/MICRO/HPCA proceedings**; arXiv `cs.AR` is thin (8,932) | — |
-| Solvers, MILP, scheduling | **Optimization Online** + arXiv `math.OC` | — |
-| Batteries, MEMS, semiconductor process | **ECSarXiv**, **ChemRxiv** | arXiv |
-| The open copy of an IEEE paper | **TechRxiv** via the Crossref `is-preprint-of` link | — |
-| Research code, firmware, datasets, artifacts | **Zenodo** | any preprint server |
-| Scientific software announcements | **bioRxiv `Bioinformatics`** | — |
diff --git a/research/preprint-repositories/library-science-and-cognitive-archives.md b/research/preprint-repositories/library-science-and-cognitive-archives.md
deleted file mode 100644
index 3e4e00d..0000000
--- a/research/preprint-repositories/library-science-and-cognitive-archives.md
+++ /dev/null
@@ -1,585 +0,0 @@
-# CogPrints, E-LIS and LISSA — library-science and cognitive-archive record
-
-A grouped record for three small subject repositories: **CogPrints** (cognitive science,
-1997–2017), **E-LIS** (library and information science, 2003–) and **LISSA** (LIS, 2017–).
-
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
----
-
-## 0. Why these three are worth a record
-
-None of them is important by size. Together they are **the best case study available in
-what happens to a subject repository when its founder retires, its grant ends, or its
-volunteers move on** — which is the question you should ask before trusting any link into
-any small preprint server, including the ones that look healthy today.
-
-Three outcomes, three mechanisms, all verifiable in 2026:
-
-| | Mechanism | Outcome 2026 |
-|---|---|---|
-| **CogPrints** | founder/host wound it down; university took custody | **Frozen but preserved.** Content survives as an explicitly "permanently archived" static copy at a different hostname. The original HTTPS URL is **broken**, and the failure looks like the site is dead |
-| **E-LIS** | distributed volunteer editorial board, institutional host, no single founder | **Alive and depositing.** 27,455 records, 882 with 2026 datestamps |
-| **LISSA** | community announced a migration and never executed it | **Stranded.** Announced departure from COS "at the end of December 2020"; six years later it is still on COS, its own website has not been updated since 2020, and COS has closed it to submissions |
-
-The generalisable lesson is in the middle column, not the right one. **A repository's
-survival tracks whether its labour is distributed, not whether its content is valuable.**
-CogPrints had the most famous founder in open access and died with his retirement from it;
-E-LIS has no famous anybody and 22 languages' worth of volunteer editors and is still
-running. And LISSA shows the third and most dangerous outcome: a live-looking website
-describing a plan that was abandoned.
-
-**Practical consequence for citation.** Two of these three currently present a URL that
-either fails outright (CogPrints over HTTPS) or misrepresents its own status (LISSA's
-`lissarchive.org`). If you have a citation into a small subject repository, **check it now,
-not when you need it**, and archive the PDF.
-
----
-
-# 1. CogPrints
-
-- **URL (historical):** `http://cogprints.org/` — **now 301-redirects** to
-  `https://web-archive.southampton.ac.uk/cogprints.org/`
-- **URL (HTTPS):** `https://cogprints.org/` — **fails with a TLS certificate error**, see §1.2
-- **Operator:** **University of Southampton**, School of Electronics and Computer Science.
-  Founded and moderated by **Stevan Harnad** (S6) [LIT].
-- **Discipline scope:** "Psychology, Neuroscience, and Linguistics, and many areas of
-  Computer Science (e.g., artificial intelligence, robotics, vision, learning, speech,
-  neural networks), Philosophy (e.g., mind, language, knowledge, science, logic), Biology
-  … Medicine … Anthropology … as well as any other portions of the physical, social and
-  mathematical sciences that are pertinent to the study of cognition." (S1, the site's own
-  front page) [DOC]
-- **Span:** **1997–2017** per Wikipedia's list (S7); Wikipedia's CogPrints article says
-  "launched in 1997" (S6).
-- **Status:** **frozen, preserved, and misleadingly unreachable.** The site itself says:
-  "**This site has been permanently archived. This is a static copy provided by the
-  University of Southampton.**" (S1) [DOC]
-- **Size:** "As of 2025, it contains **over 4,000** freely downloadable articles" (S6)
-  [LIT]. Wikipedia's list gives ">1,000" (S7). **A live count is [NOT-VERIFIED]** — see
-  §1.3 for why I could not obtain one.
-
-## 1.1 What it was
-
-CogPrints was the cognitive-science answer to arXiv, and it was built by the person who
-spent the following two decades arguing that everyone should have one. It carried
-**Computer Science as a first-class subject alongside psychology, neuroscience, linguistics
-and philosophy** — its subject browse had a `comp` branch, and the front page named
-"artificial intelligence, robotics, vision, learning, speech, neural networks" explicitly
-(S1) [DOC]. For a while in the early 2000s it was the canonical example, next to arXiv, of
-what author self-archiving looked like.
-
-Wikipedia's assessment of why it stopped mattering is worth quoting because it is a
-structural argument rather than a story about one person: "Over time, under the influence of
-the Open Archives Initiative and its OAI-PMH, the focus of self-archiving has shifted from
-centralized repositories like CogPrints to distributed self-archiving in institutional
-repositories." (S6) [LIT] CogPrints did not fail; the model it embodied was superseded by
-one in which every university runs its own repository and a harvester federates them —
-which is, incidentally, the same model [RePEc](repec-and-econstor.md) adopted in 1997 and
-never abandoned.
-
-## 1.2 The software-history detail — CogPrints *became* EPrints
-
-This is the part worth stating properly, and it is better than "EPrints came out of
-Southampton".
-
-CogPrints ran on **EPrints**, and the page footer says so: "Cogprints is powered by EPrints
-3 which is developed by the School of Electronics and Computer Science at the University of
-Southampton." (S1) [DOC] But the direction of causation is the interesting bit: **CogPrints'
-own software was generalised into EPrints.** Per Wikipedia: "CogPrints was among the first
-repositories to adopt OAI compliance. **Its software was later converted into EPrints at the
-University of Southampton by Rob Tansley, who later contributed to the development of
-DSpace.** EPrints is currently maintained by Christopher Gutteridge at Southampton." (S6)
-[LIT]
-
-So the lineage runs: one cognitive-science preprint archive → EPrints, the first widely
-deployed open-source institutional-repository platform → and, through the same developer,
-into **DSpace**, which is what [EconStor](repec-and-econstor.md) runs on today. **E-LIS
-(§2) still runs EPrints 3.4.6** (S3) [WEB]. A single 1997 subject archive is the common
-ancestor of two of the three repository platforms in this record. That is a genuine piece of
-software history and it is barely documented anywhere.
-
-CogPrints also advertised **SWORD** deposit (`/sword-app/servicedocument`) and **OAI 2.0**
-with base URL `http://cogprints.org/cgi/oai2` (S1) [DOC] — early adoption of both, entirely
-consistent with Harnad's advocacy.
-
-## 1.3 Its fate — probed, and the failure mode is a trap
-
-**The reported symptom.** A probe of `https://cogprints.org/` on 2026-09-01 fails. This
-record's assignment noted a connection failure with no HTTP status. **Independently
-reproduced and diagnosed here.**
-
-**What is actually happening** (all probes 2026-09-01, S2) [WEB]:
-
-| Probe | Result |
-|---|---|
-| `https://cogprints.org/` | **curl exit 60** — `SSL: no alternative certificate subject name matches target hostname 'cogprints.org'`. No HTTP status is ever returned |
-| — certificate served | `subject: CN=web-archive.southampton.ac.uk`, `issuer: C=US, O=Let's Encrypt, CN=YR1`, `subjectAltName does not match hostname cogprints.org` |
-| `http://cogprints.org/` | **HTTP 200**, 7,419 bytes, after redirect to `https://web-archive.southampton.ac.uk/cogprints.org/` |
-
-**Diagnosis:** the `cogprints.org` DNS record now points at Southampton's web-archive host,
-but **no certificate was issued for the `cogprints.org` name**. Southampton preserved the
-content and forgot the certificate. The result is that:
-
-- **Plain HTTP works and returns the archive.**
-- **HTTPS fails at the TLS layer, before any HTTP status exists** — which is exactly what a
-  dead server looks like to a naive probe, and to a browser that upgrades to HTTPS.
-- Anyone with an `https://cogprints.org/...` citation — which is what modern link-rewriting
-  produces — gets a security error, not a redirect.
-
-**This is a preservation success presenting as a preservation failure**, and it is worth
-generalising: **a TLS error is not evidence that content is gone.** Always retry over plain
-HTTP and follow the redirect before concluding a small repository is dead.
-
-**Corroboration from the Internet Archive CDX index** (S5) [API], which is not rate-limited
-the way the Wayback replay service is:
-
-- `cogprints.org` has captures from **2004-12-09** to **2026-08-31**.
-- The **last capture with HTTP status 200** at the root is **2024-08-03**.
-- The **first 301** appears **2020-05-10**; from late 2024 onward captures are **301 only**
-  (e.g. 2024-12-16, 2025-01-05 … 2026-08-31), consistent with the permanent redirect to the
-  Southampton archive host being in place and stable.
-
-**Live counts are [NOT-VERIFIED], and here is why.** The Southampton archive host is itself
-behind **Anubis / BotStopper**, a JavaScript proof-of-work anti-scraper gate. The front page
-came through (HTTP 200), but every sub-page tested returned **HTTP 401 with a 4,397-byte
-challenge page** headed "Ensuring the security of your connection … the administrator of
-this website has set up Anubis to protect the server against the scourge of AI companies
-aggressively scraping websites" (S2) [WEB]:
-
-| Path | Result |
-|---|---|
-| `/cogprints.org/` (index) | 200, 7,419 B |
-| `/cogprints.org/information.html` | **401**, 4,397 B (Anubis) |
-| `/cogprints.org/view/subjects.html` | **401** |
-| `/cogprints.org/view/subjects/comp.html` | **401** |
-| `/cogprints.org/cgi/oai2?verb=Identify` | **401** |
-| **Negative control** `/cogprints.org/definitely-not-real-xyzzy.html` | **401** — *identical to a real page* |
-
-Note the negative control: on this host **a 401 tells you nothing about whether the
-document exists.** The user-agent ladder in [AGENTS.md](../../AGENTS.md) is the wrong
-tool here — Anubis is a JavaScript proof-of-work challenge, not UA filtering, and rotating
-agents will not help. The Internet Archive's replay service (`web.archive.org/web/...`) was
-returning **HTTP 429** ("suspected abusive bot traffic") throughout this session, so the
-archived 2017 subject-browse pages could not be read either. **The subject-level breakdown,
-including how many CogPrints items were Computer Science, is therefore not verified.**
-
-The OAI-PMH endpoint at `http://cogprints.org/cgi/oai2` is advertised on the front page but
-sits behind the same gate; whether it still answers is **[NOT-VERIFIED]**.
-
-## 1.4 What a computing person would find
-
-Historical AI, robotics, vision, machine learning, speech and neural-network work from the
-late 1990s and 2000s, filed under the `comp` subject branch, alongside the
-philosophy-of-mind and cognitive-science literature it was in conversation with (S1) [DOC].
-The archive is frozen at 2017, so nothing after that. Its practical value today is
-**historical**: it is a snapshot of what the AI/cognitive-science boundary looked like
-before deep learning, deposited by people who were arguing about symbol grounding.
-
-**No landmark-papers table.** I could not enumerate the holdings (§1.3), and listing papers
-I could not confirm are actually there would violate this collection's evidence rules.
-
----
-
-# 2. E-LIS — E-prints in Library and Information Science
-
-- **URL:** https://eprints.rclis.org/ · OAI-PMH https://eprints.rclis.org/cgi/oai2
-- **Operator:** **E-LIS Governance** and **CIEPI**; *hosted* by the **Library System (CAB)
-  of the University of Naples Federico II** (S3) [DOC]. Run by "a team of volunteer editors
-  that support 22 languages" (S3) [DOC], with a named Administrative Board, Executive Board
-  and per-country Editorial Board. Pro-bono legal support from D&P Studio Legale, Milan
-  (S3) [DOC].
-- **Discipline scope:** "Library and Information Science (LIS), including Communication"
-  (S3). Classified with the **JITA Classification Scheme**, maintained by Christophe Dupriez
-  (S3) [DOC].
-- **Launched:** **2003** — "Established in 2003, e-LIS is an international digital
-  repository" (S3) [DOC]; Wikipedia's article says January 2003 (S8); Wikipedia's list says
-  2003 (S7). All agree.
-- **Status:** **active** — 882 records carry 2026 datestamps (§2.2).
-- **Software:** **EPrints 3.4.6** (S3) [WEB] — a current release, which is itself a
-  reassuring maintenance signal.
-
-## 2.1 What it is
-
-E-LIS is the librarians' own repository, and it is the healthiest of the three archives in
-this record for a reason that is visible in its governance page rather than its statistics:
-**the labour is spread across dozens of named volunteer editors in dozens of countries**,
-with an institutional host that supplies servers and a legal firm that supplies advice for
-free. Nobody's retirement can end it.
-
-Its self-description is unusually reflective about *why* librarians in particular built one:
-"Because librarians are so involved in open access advocacy, e-LIS is a key to encourage
-open access for all repositories, by giving librarians the experience they need to speak
-with confidence when talking with researchers … and the experience to provide the best
-possible assistance to self-archiving faculty." (S3) [DOC] The repository is partly a
-training exercise in running a repository. That is a good reason for it to exist and a good
-reason for it to be well run.
-
-## 2.2 Size — measured
-
-All from the OAI-PMH interface, `completeListSize` in the `resumptionToken`, retrieved
-**2026-09-01** (S4) [API]:
-
-- **Total records: 27,455.**
-- `Identify`: `repositoryName` E-LIS repository · `protocolVersion` 2.0 ·
-  `deletedRecord` **persistent** (deletions are tracked, not silently dropped — good) ·
-  `granularity` `YYYY-MM-DDThh:mm:ssZ` · `sampleIdentifier` `oai:eprints.rclis.org:14248`.
-- **`earliestDatestamp`: 2013-02-13T10:59:30Z.** **Note the conflict:** E-LIS launched in
-  2003, but its OAI datestamps begin in 2013. That is a **platform migration artefact**, not
-  a content boundary — a bulk re-index resets every record's modification date. **Do not
-  read an OAI `earliestDatestamp` as a founding date.** This is a general trap and E-LIS is
-  a clean example of it.
-- **406 OAI sets**, mixing publication status (`Status = Published`, `Unpublished`,
-  `Submitted`, `In Press`) with the full JITA subject hierarchy.
-
-**Activity, by records with a datestamp in each window** (S4) [API] — note these count
-*modifications*, so they overstate new deposits, but they do establish the repository is
-being worked on:
-
-| Window | Records |
-|---|---|
-| 2026-01-01 → 2026-09-01 | **882** |
-| 2025 | 736 |
-| 2024 | 571 |
-| 2023 | 955 |
-
-**27,455 against Wikipedia's ">10,000"** (S7) — the bucket is right but low. Wikipedia's
-E-LIS *article* says "Over 12,000 papers have been archived to date", sourced to a 2011
-retrieval (S8) [LIT] — a stale figure that has more than doubled since.
-
-## 2.3 Screening — a real editorial board with a real queue
-
-E-LIS is moderated, and its policy is specific (S9, *e-LIS Policies*) [DOC]:
-
-> "Submitted documents will be placed into the **submission buffer**, where they may be
-> approved by the e-LIS Editorial Board, rejected, or returned to the author for
-> modifications in the metadata or if there are problems with the electronic file. Documents
-> in the submission buffer are **manually reviewed** to confirm they fit our policy before
-> adding them to e-LIS. e-LIS Editorial Board checks the metadata quality of the document
-> and is allowed to make changes if the metadata are incorrect. **Two business days** is the
-> allowable time period between when a paper is deposited to e-LIS and when it becomes
-> accessible."
-
-Scope: "any scientific or technical document, published or unpublished, in Librarianship,
-Information Science and Technology, and related application activities. The criteria for
-acceptance is that the eprints are relevant to research in LIS fields and that they have the
-form of a finished document that is ready to be entered into a process of communication."
-Accepted types include preprints, postprints, conference papers and posters, presentations,
-books, chapters, technical reports and working papers, theses, and newspaper/magazine
-articles (S9) [DOC].
-
-Multilingual by design: "All languages are supported … If the document is in a language
-other than English, it must include an English abstract and keywords in English." (S9) [DOC]
-
-**Copyright is the author's problem, explicitly:** "Authors submitting documents are
-responsible for confirming there aren't any restrictions on the electronic distribution of
-the submitted document. Copyright issues will be the authors' responsibility. e-LIS is not
-responsible for contents submitted by the authors." The deposit agreement grants E-LIS "the
-right to store them and make them permanently available publicly for free on-line" (S9)
-[DOC]. There is a **Preservation Policy** and a **Bibliographic Data Policy** on the same
-page.
-
-Metadata quality is checked and corrected by editors — a stronger commitment than most
-preprint servers make, and consistent with the population depositing being professional
-cataloguers.
-
-## 2.4 What a computing person would find — and it is more than you would guess
-
-E-LIS's JITA scheme has a **whole computing class, `L. Information technology and library
-technology`, with 21 subclasses**. Counts by OAI set, 2026-09-01 (S4) [API]:
-
-| JITA code | Subject | Records |
-|---|---|---|
-| **L.** | **Information technology and library technology (whole class)** | **4,998** |
-| LC | Internet, including WWW | 1,154 |
-| LJ | Software | 500 |
-| LS | **Search engines** | 465 |
-| LZ | None of these, but in this section | 404 |
-| LQ | Library automation systems | 395 |
-| LR | OPAC systems | 260 |
-| LB | **Computer networking** | 258 |
-| LN | **Data base management systems** | 212 |
-| LK | **Software methodologies and engineering** | 191 |
-| LM | **Automatic text retrieval** | 167 |
-| LA | Telecommunications | 156 |
-| LL | Automated language processing | 155 |
-| LP | Intelligent agents | 130 |
-| LH | **Computer and network security** | 92 |
-| LD | Computers | 90 |
-| LT | Mobile devices | 64 |
-| LI | Authentication, and access control | 47 |
-| LF | Digital cameras | 18 |
-| LO | Object-oriented DBMS | 13 |
-| LE | Scanners | 12 |
-| LG | Photocopiers | 9 |
-
-**4,998 records — 18.2% of the whole repository — are classified as information
-technology** [INF, from S4]. That is a far higher computing share than
-[EconStor](repec-and-econstor.md) (36 records, 0.011%) or the social-science end of
-[OSF Preprints](osf-preprints.md).
-
-The genuinely useful areas for this knowledge base, in order:
-
-1. **Information retrieval** — `LM. Automatic text retrieval` (167) and `LS. Search engines`
-   (465). The LIS literature on retrieval is the older sibling of the CS IR literature and
-   frequently addresses evaluation methodology that CS papers assume.
-2. **Repository software** — `LQ. Library automation systems` (395) and `LR. OPAC systems`
-   (260). If you need to know how DSpace, EPrints, Koha or Fedora behave in production,
-   this is where the operators write it up. Note the recursion: **E-LIS is an EPrints
-   instance containing papers about running EPrints instances.**
-3. **Metadata standards** — spread across the `I. Information treatment` class. Dublin Core,
-   MARC, OAI-PMH, RDA. If you are implementing a harvester, this is the primary literature.
-4. **Bibliometrics** — the LIS side of citation analysis, which is the field that produces
-   the studies other records in this collection cite as [LIT].
-5. `LK. Software methodologies and engineering` (191) and `LH. Computer and network
-   security` (92) — small, and mostly library-systems-flavoured.
-
-The subject vocabulary is dated in an endearing way — `LG. Photocopiers` (9 records),
-`LE. Scanners` (12), `LF. Digital cameras` (18) — which is itself a reminder that the
-scheme was designed in the early 2000s.
-
-## 2.5 Access
-
-**OAI-PMH is open, standard and unrestricted.** `https://eprints.rclis.org/cgi/oai2`
-answered `Identify`, `ListSets`, and `ListIdentifiers` (whole repository and per set) with no
-authentication, no UA requirement and no rate limiting across ~30 sequential calls
-(S4) [API]. EPrints also exposes `RDFXML` and `RDFN3` full-repository exports
-(`/cgi/export/repository/RDFXML/devel.rdf`), a **SWORD** deposit endpoint, OpenSearch, and
-RSS/Atom feeds (S3) [WEB]. This is what a well-behaved repository looks like, and it is a
-sharp contrast with [SSRN](ssrn.md), which offers none of it.
-
-**Negative control** (S4) [API]: `verb=ListIdentifiers&metadataPrefix=oai_dc&set=notarealsetxyzzy`
-returns **HTTP 500 Internal Server Error**, 539 bytes — *not* an OAI `<error>` element. That
-is a bug rather than protocol-conformant behaviour, but it is at least unmistakably
-distinguishable from a valid response. Contrast [EconStor](repec-and-econstor.md), which
-returns HTTP 200 with `<error code="noRecordsMatch">` for the same mistake.
-
-**Licensing.** Per-record; the deposit agreement grants E-LIS a permanent right to
-distribute, and copyright remains the author's responsibility (§2.3). There is no single
-repository-wide licence. Check each record.
-
----
-
-# 3. LISSA — LIS Scholarship Archive
-
-- **URLs:** community site https://lissarchive.org/ · content
-  https://osf.io/preprints/lissa
-- **Operator:** the **LISSA Steering Committee** (community); infrastructure by the
-  **Center for Open Science**. Site source on GitLab at `gitlab.com/VickySteeves/lissarchive`
-  (S10) [WEB].
-- **Discipline scope:** "A free, open scholarly platform for library and information
-  science" (S11) [API].
-- **Launched:** **soft launch 2017-07-19**, full launch announced 2017-10-26 (S10) [DOC].
-  Earliest record 2017-07-12 (S11) [API]. Wikipedia's list says 2018 (S7) — **off by a
-  year**.
-- **Status:** **stranded.** Closed to new submissions by COS; announced migration never
-  happened; community site frozen since 2020.
-- **Size:** **335 records**, of which **325 distinct works** (10 are later versions) and
-  **321 carry a minted preprint DOI**, by full enumeration of the OSF API, 2026-09-01 (S11)
-  [API]. Wikipedia says ">100" (S7).
-- **Moderation:** `reviews_workflow: post-moderation` (S11) [API] — one of only three
-  OSF providers that is not pre-moderated.
-- **Record span:** first 2017-07-12, most recent **2025-12-04** (S11) [API].
-
-## 3.1 What it was meant to be
-
-LISSA's ambition was broader than "preprints", and deliberately so. From its own About page:
-"Librarians, archivists, and other information professionals engage in a broad range of
-scholarship, from creating metadata to writing manuscripts. We acknowledge that much of this
-scholarship happens outside the traditional realms of academia, including work that goes
-beyond the standard article or book chapter to **oral histories, community works, code,
-data, and more**." (S10) [DOC]
-
-Its submission guidelines accept "Articles · Reports · **Metadata** · Oral histories ·
-Manuscripts · Pre-/post-prints · **Data** · **Code** · Promotion packets · Student work ·
-Posters · Book Chapters" (S10) [DOC] — an unusually inclusive list that treats a metadata
-record or a promotion packet as a legitimate scholarly output.
-
-It also had a **code of conduct as an acceptance criterion**, which is rare: "We reserve the
-right to remove any content that could reasonably be construed as offensive or harassing to
-people or groups … Submissions will be reviewed periodically to check for conformation with
-these guidelines. Submissions that do not meet these guidelines will be removed, and the
-authors notified. If you wish to appeal any decisions … notify the LISSA board." (S10)
-[DOC] The guidelines credit "the paleorxiv submission guidelines, the SocArXiv FAQ, and …
-the open code of conduct" as sources — a small piece of evidence for how norms propagated
-across the OSF provider population.
-
-## 3.2 What actually happened — the stranding, verified
-
-**2020-11-30.** The LISSA Steering Committee published *"LISSA is migrating off COS
-infrastructure"* (S10) [DOC]:
-
-> "The Library & Information Science Scholarly Archive (LISSA) will **transition away from
-> being hosted by the Center for Open Science (COS) at the end of December 2020**. Materials
-> currently hosted by the COS on https://osf.io/preprints/lissa will remain accessible.
-> Please read our statement regarding why this decision is necessary, as well as the
-> timeline of events that led to this decision."
-
-The post lists three options put to the community — self-host; bring in a technical partner;
-bring in a partner handling both technical and legal infrastructure — with a **survey
-closing 2020-12-20**.
-
-**2026-09-01 — none of it happened.** Measured:
-
-- LISSA's content is **still on OSF**: 335 records under provider slug `lissa`, with deposits
-  continuing to **2025-12-04** (S11) [API].
-- **`lissarchive.org` is still live** and still displays the November 2020 migration notice
-  as its most recent update. Its "Updates" page contains four posts, the newest dated
-  **2020-11-30** and the rest from 2017 (S10) [WEB]. The footer reads "Original contents
-  licensed 2020". The site links to `osf.io/preprints/lissa/submit` as though submission
-  were open.
-- **COS has closed it.** The OSF provider record's `allow_submissions` is **`false`** and its
-  description reads: "LISSA is no longer able to accept new submissions. Existing content
-  will remain accessible as part of COS's ongoing commitment to Open Science." (S11) [API] —
-  the same verbatim boilerplate COS applied to Frenxiv, IndiaRxiv, MindRxiv, NutriXiv,
-  SportRxiv and LawArXiv (see [osf-preprints.md](osf-preprints.md) §3.3).
-- **`www.lissarchive.org` returns HTTP 525** (Cloudflare SSL handshake failure) while the
-  apex `lissarchive.org` returns 200 (S12) [WEB] — a second, smaller certificate defect in
-  the same record. Compare CogPrints (§1.2): **abandoned sites decay first at the TLS
-  layer.**
-
-**A conflict I am recording rather than resolving.** The API says
-`allow_submissions: false`, but records with **`_v1` GUIDs** — genuinely new deposits, not
-revisions — appear as recently as **2025-08-17** (`mw67v_v1`), **2025-08-11** (`qy7de_v1`)
-and **2025-08-08** (`xz6gq_v1`) (S11) [API]. The most plausible reading is that the flag was
-flipped some time between August and December 2025, i.e. **COS closed LISSA roughly five
-years after LISSA announced it was leaving, and did so from the other side.** I could find
-no COS or LISSA announcement of that closure and its date is **[NOT-VERIFIED]**.
-
-**Content drift.** The ten most recent LISSA records include *"Baptism Without a Pool:
-Collaborative Information Behavior Among Storefront Church…"*, *"Browsing the Spirit:
-Applying Library Browsing Theory to Storefront Church…"*, *"No Longer Divided: Merging Mega
-and Storefront Churches…"* and *"Preserving the Narrative: What Storefront Churches Lose
-When Overshadowed…"* (S11) [API] — six of the last ten records are one author's series on
-storefront churches. **This is what an unattended post-moderated repository looks like near
-the end**: a single depositor becomes most of the recent corpus, and nobody is checking
-scope. It is a useful, concrete diagnostic to know about.
-
-## 3.3 What a computing person would find
-
-Very little, and less than E-LIS. LISSA is a third the size, covers the same field, and
-skews toward professional-practice outputs (promotion packets, oral histories, student work)
-rather than technical LIS. It is worth knowing about for **repository-community history** —
-LISSA's 2020 statement is a primary document about the strains of running a community server
-on someone else's infrastructure — rather than for its contents.
-
-One thing it did do well and is worth borrowing: **321 of 335 records (95.8%) carry a minted
-preprint DOI** (S11) [API], a much better rate than recent deposits elsewhere on OSF, where
-newly accepted preprints are currently being published with no identifier at all (see
-[osf-preprints.md](osf-preprints.md) §6). LISSA's content is, ironically, more citable than
-the live servers around it.
-
----
-
-# 4. Cross-cutting caveats
-
-1. **A TLS error is not evidence of deletion.** CogPrints' content is fully preserved and
-   HTTPS to its historical hostname still fails (§1.3). Retry over HTTP, follow the
-   redirect, and check the certificate's `CN` before writing anything off.
-2. **Anti-scraper gates now sit in front of preserved archives.** Southampton's web-archive
-   host runs **Anubis/BotStopper** and returns **HTTP 401 for real and bogus paths alike**
-   (§1.3); ZBW runs Anubis in front of EconStor (see
-   [repec-and-econstor.md](repec-and-econstor.md) §7.2); the Internet Archive was returning
-   **429** to replay requests throughout this session. Three independent anti-bot walls
-   encountered in one afternoon of ordinary archival probing. **Expect this to get worse and
-   budget for it.** Where a repository exposes OAI-PMH, use it — that path was open in every
-   case where it existed.
-3. **An OAI `earliestDatestamp` is a migration date, not a founding date.** E-LIS launched
-   in 2003 and its OAI datestamps begin in 2013 (§2.2).
-4. **A live community website can describe a plan that was abandoned six years ago.** LISSA's
-   `lissarchive.org` still fronts a November 2020 migration announcement and links to a
-   submission form that COS has disabled (§3.2). **Check the content endpoint, not the
-   community site.**
-5. **Wikipedia's dates and sizes for all three are wrong or stale**: LISSA 2018 (actually
-   2017); E-LIS ">10,000" (actually 27,455) and its article's "over 12,000" is a 2011
-   figure; CogPrints ">1,000" against "over 4,000" in Wikipedia's own CogPrints article
-   (S6, S7, S8).
-6. **Post-moderation degrades silently.** LISSA's recent corpus is dominated by one
-   depositor on a single topic (§3.2). Where a repository's `reviews_workflow` is
-   `post-moderation` or unset, check *who deposited the recent records* before trusting the
-   collection's stated scope.
-7. **Survival correlates with distributed labour, not with content quality.** E-LIS survives
-   on volunteer editors across 22 languages plus a university host; CogPrints and LISSA both
-   depended on small groups and both stopped. If you are assessing whether a small
-   repository will still be there in ten years, count the maintainers, not the papers.
-
----
-
-# 5. Sources
-
-- **S1** — CogPrints front page, retrieved via `http://cogprints.org/` which redirects to
-  `https://web-archive.southampton.ac.uk/cogprints.org/`. Retrieved 2026-09-01, HTTP 200,
-  7,419 bytes. Supports: the full scope statement, the "This site has been permanently
-  archived. This is a static copy provided by the University of Southampton." notice, the
-  "powered by EPrints 3 which is developed by the School of Electronics and Computer Science
-  at the University of Southampton" footer, the advertised OAI 2.0 base URL
-  `http://cogprints.org/cgi/oai2`, the SWORD service document, and the six subject branches
-  (`psyc`, `neuro`, `ling`, `comp`, `phil`, `bio`).
-- **S2** — CogPrints access probes, 2026-09-01: `https://cogprints.org/` (curl exit 60, TLS
-  SAN mismatch, certificate `CN=web-archive.southampton.ac.uk` issued by Let's Encrypt
-  `CN=YR1`); `http://cogprints.org/` (200 via redirect); and
-  `https://web-archive.southampton.ac.uk/cogprints.org/{information.html,view/subjects.html,view/subjects/comp.html,cgi/oai2?verb=Identify,definitely-not-real-xyzzy.html}`
-  (all HTTP 401, ~4,397 bytes, Anubis/BotStopper challenge page). Supports §1.3 in full.
-- **S3** — E-LIS front page `https://eprints.rclis.org/` (200, 13,476 B) and About page
-  `https://eprints.rclis.org/information.html` (200, 19,626 B). Retrieved 2026-09-01.
-  Supports: "Established in 2003", the 22-language volunteer editor claim, hosting by the
-  Library System (CAB) of the University of Naples Federico II, the named Administrative /
-  Executive / Editorial boards, the JITA Classification Scheme and its maintainer, the
-  pro-bono legal support, the EPrints 3.4.6 version string, the OAI base URL, and the
-  RDFXML/RDFN3/SWORD/OpenSearch endpoints.
-- **S4** — E-LIS OAI-PMH, `https://eprints.rclis.org/cgi/oai2`, verbs `Identify`,
-  `ListSets`, `ListIdentifiers` (whole repository, per `from`/`until` window, and per set for
-  all 22 `L.` subject sets). Retrieved 2026-09-01. Supports: 27,455 total records, the
-  `Identify` fields including `earliestDatestamp` 2013-02-13T10:59:30Z and
-  `deletedRecord: persistent`, the 406 sets, the activity-by-year table, the entire §2.4
-  JITA `L.` table, and the HTTP 500 negative control.
-- **S5** — Internet Archive CDX API,
-  `https://web.archive.org/cdx/search/cdx?url=cogprints.org&output=json&…`. Retrieved
-  2026-09-01. Supports: first capture 2004-12-09, last capture 2026-08-31, last HTTP 200 at
-  the root 2024-08-03, first 301 2020-05-10, 301-only from late 2024 onward. (The Wayback
-  *replay* service `web.archive.org/web/…` returned HTTP 429 throughout this session and
-  could not be used.)
-- **S6** — Wikipedia, *CogPrints*, wikitext via
-  `https://en.wikipedia.org/w/index.php?title=CogPrints&action=raw`. Retrieved 2026-09-01.
-  Supports: launch 1997, moderation by Stevan Harnad, "As of 2025, it contains over 4,000
-  freely downloadable articles", early OAI compliance, the conversion of its software into
-  EPrints by Rob Tansley (later a DSpace contributor), current EPrints maintenance by
-  Christopher Gutteridge, and the analysis of the shift from centralised subject archives to
-  institutional repositories. [LIT]
-- **S7** — Wikipedia, *List of preprint repositories*, wikitext via
-  `https://en.wikipedia.org/w/index.php?title=List_of_preprint_repositories&action=raw`.
-  Retrieved 2026-09-01. Supports: the CogPrints row (Multidisciplinary; "Psychology,
-  Neuroscience, Linguistics, Computer Science, Philosophy, and Biology"; ">1,000"; span
-  1997–2017; University of Southampton), the E-LIS row (Library science; "Eprints in Library
-  and Information Science"; ">10,000"; 2003; E-LIS Governance & CIEPI), and the LISSA row
-  (Library science; ">100"; 2018; Center for Open Science).
-- **S8** — Wikipedia, *E-LIS*, wikitext via
-  `https://en.wikipedia.org/w/index.php?title=E-LIS&action=raw`. Retrieved 2026-09-01.
-  Supports: launch date January 2003, "22 languages", ownership by E-LIS Governance and
-  CIEPI, and the stale "Over 12,000 papers have been archived to date" claim sourced to a
-  2011-08-02 retrieval. [LIT]
-- **S9** — *e-LIS Policies: Check before submitting your papers*,
-  `https://eprints.rclis.org/policies.html`. Retrieved 2026-09-01, HTTP 200, 21,453 bytes.
-  Supports: the submission policy, the submission-buffer/manual-review process, the two
-  business day turnaround, the accepted document types, the all-languages/English-abstract
-  rule, the deposit agreement text, the author-bears-copyright-responsibility clause, and
-  the existence of the preservation and bibliographic-data policies.
-- **S10** — LISSA community site: `https://lissarchive.org/` (200, 8,648 B),
-  `/updates/lissa-cos/` (200, 8,039 B), `/updates/` (200, 13,788 B), `/about/` (200,
-  6,386 B), `/guidelines/` (200, 8,621 B). All retrieved 2026-09-01. Supports: the
-  2020-11-30 migration announcement and its three options and 2020-12-20 survey deadline,
-  the 2017-07-19 soft launch and 2017-10-26 full-launch posts, the accepted-content list,
-  the code-of-conduct acceptance criterion and its attribution to PaleorXiv/SocArXiv, the
-  GitLab source location, and the fact that the newest update is dated 2020-11-30.
-- **S11** — OSF REST API v2, `https://api.osf.io/v2/preprints/?filter[provider]=lissa` (full
-  enumeration, 4 pages) and `https://api.osf.io/v2/preprint_providers/`. Retrieved
-  2026-09-01. Supports: 335 records / 325 distinct base GUIDs / 321 with
-  `preprint_doi_created`, `reviews_workflow: post-moderation`, `allow_submissions: false`,
-  the provider description boilerplate, the 2017-07-12 earliest and 2025-12-04 latest record
-  dates, the `_v1` deposits in August 2025, and the ten most recent titles.
-- **S12** — LISSA reachability probes, 2026-09-01: `https://lissarchive.org/` → 200;
-  `https://www.lissarchive.org/` → **HTTP 525** (SSL handshake failed), 16 bytes;
-  `https://osf.io/preprints/lissa` → 200 with the 4,207-byte OSF SPA shell (which, per
-  [osf-preprints.md](osf-preprints.md) §8, is byte-identical to the response for a
-  nonexistent provider and therefore carries no information).
diff --git a/research/preprint-repositories/life-science-and-medical-platforms.md b/research/preprint-repositories/life-science-and-medical-platforms.md
deleted file mode 100644
index bd4bd26..0000000
--- a/research/preprint-repositories/life-science-and-medical-platforms.md
+++ /dev/null
@@ -1,494 +0,0 @@
-# Life-science and medical preprint platforms — grouped record
-
-Covers eleven venues that are **not** general-purpose preprint servers: publisher-owned
-preview services, funder-restricted publishing platforms, and one genuinely defunct
-pioneer. The two big general life-science servers have their own record —
-see [bioRxiv and medRxiv](biorxiv-and-medrxiv.md). ChemRxiv is at
-[chemrxiv.md](chemrxiv.md); BioHackrXiv and AIJR Preprints are covered elsewhere.
-
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 0. The shared pattern — publisher-tied and funder-tied venues
-
-Almost everything in this record shares one structural property that makes it different
-from arXiv, bioRxiv or Zenodo: **you cannot just deposit there.** Access is gated on a
-relationship with the sponsor.
-
-| Gate type | Examples |
-|---|---|
-| **You must be funded by the sponsor** | Wellcome Open Research, Gates Open Research, HRB Open Research, AMRC Open Research, Open Research Africa, Open Research Europe |
-| **You must be submitting to the sponsor's journals** | Cell Press Sneak Peek, Preprints with The Lancet, JMIR Preprints, ARPHA Preprints, Beilstein Archives |
-| **Open, but publisher-run and now closed** | PeerJ Preprints, Nature Precedings |
-
-Three consequences follow, and they are the reason this record exists:
-
-1. **They are not archives, they are shop windows.** A "preprint server" whose corpus is
-   defined by "manuscripts on their way into *our* journals" cannot be used to survey a
-   field. Coverage is a function of the sponsor's market share, not of the science. When
-   you search Cell Press Sneak Peek you are searching Cell Press's review queue.
-2. **The eligibility gate suppresses volume by one to three orders of magnitude.**
-   AMRC Open Research has **27 articles in its entire existence** (§3). Beilstein Archives
-   has 726 in seven years (§10). Compare bioRxiv's 49,318 in 2025 alone.
-3. **Durability is poor, and the failure modes are specific.** Of the eleven venues here,
-   one is fully defunct (Nature Precedings), one is closed to new deposits (PeerJ
-   Preprints), one has lost its domain entirely (agriRxiv), one has been renamed and
-   re-hosted (AAS Open Research → Open Research Africa), one is being drained by a
-   successor platform (Gates Open Research → VeriXiv), and one has posted nothing for four
-   years (AMRC Open Research). That is **six of eleven** with a discontinuity, against a
-   median age of about eight years.
-
-The redeeming detail, and it is a real one: **DOIs held up**. Every dead or moved service
-in this record still resolves its DOIs to live content, including Nature Precedings, dead
-since 2012 (§7), and agriRxiv, whose own domain is now a Namecheap parking page (§11).
-Persistent identifiers plus a publisher with an archival obligation turned out to be a
-better preservation strategy than the domain name. That is the single transferable lesson
-here.
-
-## 1. Status table — probed 2026-09-01
-
-| Platform | URL | Operator | Launched | **Status** | Size (source) |
-|---|---|---|---|---|---|
-| **F1000Research** | f1000research.com | F1000 Research Ltd | 2012 | **ALIVE**, ~2,000 articles/yr | **12,442** distinct articles (18,667 versioned DOIs) [API] |
-| **Wellcome Open Research** | wellcomeopenresearch.org | Wellcome + F1000 | 2016/17 | **ALIVE**, growing | **4,009** [API] |
-| **Gates Open Research** | gatesopenresearch.org | Gates Foundation + F1000 | 2017 | **ALIVE but draining** → new work routes via **VeriXiv** since Aug 2024 | **563** [API] |
-| **AAS Open Research** | aasopenresearch.org | AAS + F1000 | 2018 | **RENAMED** — 301 → openresearchafrica.org; no records after 2022 | **114** [API] |
-| **Open Research Africa** | openresearchafrica.org | (AAS successor) + F1000 | 2019 | **ALIVE**, small but reviving | **138** [API] |
-| **AMRC Open Research** | amrcopenresearch.org | AMRC + F1000 | 2019 | **MORIBUND** — nothing registered since 2022 | **27** [API] |
-| **HRB Open Research** | hrbopenresearch.org | Health Research Board (IE) + F1000 | 2018 | **ALIVE** | **731** [API] |
-| **PeerJ Preprints** | peerj.com/preprints | PeerJ | 2013 | **CLOSED to new deposits (2019)**; content live, DOIs resolve | **5,068** distinct (6,446 versioned) [API] |
-| **Preprints with The Lancet** | ssrn.com/…/the-lancet | Elsevier / SSRN | [NOT-VERIFIED] | **ALIVE** — contrary to expectation | **25,550** papers displayed [WEB] |
-| **Cell Press Sneak Peek** | ssrn.com/…/cell-press-sneak-peek | Elsevier / SSRN | [NOT-VERIFIED] | **ALIVE** | **12,404** papers displayed [WEB] |
-| **Nature Precedings** | ~~precedings.nature.com~~ → nature.com/npre | Nature Publishing Group | 2007 | **DEFUNCT since 2012**; original host **refuses connections**; **content preserved** | **3,449** records [WEB] |
-| **JMIR Preprints** | preprints.jmir.org | JMIR Publications | 2009 (claimed) | **ALIVE**, very large | **41,766** `posted-content` DOIs [API] |
-| **ARPHA Preprints** | preprints.arphahub.com | Pensoft | 2020 | **ALIVE**, growing | **1,058** [API] |
-| **Beilstein Archives** | beilstein-archives.org | Beilstein-Institut | 2019 | **ALIVE but declining** | **726** [API] |
-| **agriRxiv** | ~~agrirxiv.org~~ → cabidigitallibrary.org | CABI (+ Open Access India) | 2017 | **DOMAIN DEAD** (parked); **service migrated**, DOIs resolve | **1,054** DOIs under `10.31220` [API] |
-
-*Bonus finds not in the brief but part of the same family:* **Open Research Europe**
-(European Commission, F1000-powered, 2021–) — **1,513** distinct articles, growing fast
-(628 in 2025) [API]; **VeriXiv** (verixiv.org, Gates + F1000, 2024–) — live, size not
-measured.
-
-## 2. F1000Research
-
-- **URL:** https://f1000research.com/ · **HTTP 200**, 114,761 B, 2026-09-01
-- **Operator:** Crossref registers prefix `10.12688` to **"F1000 Research Ltd"**, member
-  2560 (S1) [API]. Corporate parent commonly reported as **Taylor & Francis / Informa**
-  (acquisition 2020) — **[NOT-VERIFIED]**, no statement to that effect on the pages I
-  retrieved.
-- **Launched 2012**; the `container-title: F1000Research` activity window in Crossref runs
-  **2012–2026** (S1).
-- **Size: 12,442 distinct articles** from 18,667 versioned DOIs (S1) [API]. Steady at
-  ~2,000/year: 1,898 (2022), 2,063 (2023), 2,195 (2024), 2,031 (2025), 1,868 to 2026-09-01.
-
-**The model, properly.** F1000Research is not a preprint server bolted onto a journal; it
-is a *publish-then-review platform*, and the mechanism is worth understanding because
-several other entries here are literally the same software (§3). From F1000's own
-documentation (S2) [DOC]:
-
-1. **Submission → in-house check only.** An editorial team runs "prepublication checks" for
-   policy and ethics compliance. There is **"no Editor (or Editor-in-Chief) to make a
-   decision on whether to accept or reject the article, or to oversee the peer-review
-   process."** That sentence is the whole design.
-2. **Publication within about a week**, with the status **"Awaiting Peer Review"**. The
-   article is live, citable, DOI'd, and indexed by Google Scholar from that moment.
-3. **Open, invited, named peer review, after publication.** Reviewers are invited; their
-   **reports and their names** are published on the article page alongside author
-   responses and registered-user comments.
-4. **Each reviewer picks one of three statuses**: **Approved** ("no or only minor changes
-   required"), **Approved with Reservations** ("academic merit, but … a number of small
-   changes … or specific, sometimes more significant revisions"), **Not Approved** ("very
-   poor quality … fundamental flaws … that seriously undermine the findings").
-5. **Versioned articles.** Authors publish revised versions; **every version is separately
-   DOI'd and independently citable**, all versions stay public, the latest is the default,
-   and invited reviewers are re-invited to re-review each new version. Articles are
-   explicitly "living" — updatable even after review completes.
-6. **A hard, published indexing threshold.** An article is indexed in PubMed, PubMed
-   Central, MEDLINE, Europe PMC, Scopus, CAS, DOAJ and Embase **only** once it has
-   received "at least two 'Approved' statuses, or one 'Approved' and two 'Approved with
-   Reservations' statuses from independent and invited peer reviewers" (S2). Posters,
-   slides and "documents" are never peer reviewed and never indexed.
-
-**Why this is genuinely distinctive.** The reviewer's identity, verdict and full report
-are attached to the object permanently, and the *object's own indexing status* encodes
-whether it passed. So — unlike every conventional preprint server in this collection — an
-F1000Research article carries its own machine-readable review outcome. You can look at an
-article and see three named people saying "Approved" or one saying "Not Approved". The
-cost is that you must actually look: **the "Awaiting Peer Review" and "Not Approved"
-articles sit at the same URL, with the same DOI, under the same brand as the approved
-ones.** Citing "an F1000Research paper" without checking the reviewer statuses is a
-mistake, and it is a mistake people make.
-
-**Scope** is far broader than the name suggests: "basic scientific, scholarly,
-translational and clinical research across the physical and life sciences, engineering,
-medicine, social sciences and humanities", explicitly including **software tools and
-method articles**, and explicitly welcoming "confirmatory and negative results, as well as
-null studies" (S2). At least one author must be "a qualified researcher, scholar or
-clinician actively working in their speciality".
-
-**Licensing:** overwhelmingly **CC BY 4.0** — 30,379 of 31,780 journal-article records
-under prefix `10.12688` carry a CC BY 4.0 licence URL, plus 567 CC BY 3.0; only 760 have
-none (S1) [API]. That is a far more open corpus than bioRxiv or ChemRxiv. It is not free
-to publish, though — F1000Research levies **article processing charges** (S2).
-
-## 3. The F1000-powered funder platforms — one platform, many badges
-
-Wikipedia lists these as separate entities. They are not separate software: they are
-**white-labelled instances of the F1000Research platform**, all minting DOIs under the
-**same Crossref prefix `10.12688`, registered to F1000 Research Ltd** (S1) [API]. Same
-submission flow, same in-house checks, same open named post-publication review, same
-three approval statuses, same versioned DOIs, same CC BY default, same indexing threshold
-(§2). What differs is the **eligibility gate** and the branding.
-
-Gates Open Research states its gate plainly: an article requires "**at least one author
-who has been, or still is, a recipient of a Gates Foundation grant**" (S3) [DOC]. Every
-sibling has the equivalent rule for its own funder. Publication costs are met by the
-funder rather than the author.
-
-Sizes and activity windows, all from Crossref facets on prefix `10.12688`, retrieved
-**2026-09-01** (S1) [API]:
-
-| Platform | Sponsor | Records | Distinct articles | Active years | Recent volume |
-|---|---|---|---|---|---|
-| Wellcome Open Research | Wellcome Trust | 5,468 | **4,009** | 2016–2026 | 908 (2024), 822 (2025), 702 (2026 ytd) |
-| Open Research Europe | European Commission | 2,429 | **1,513** | 2021–2026 | 463 (2024), 628 (2025), 532 (2026 ytd) |
-| HRB Open Research | Health Research Board (Ireland) | 1,134 | **731** | 2018–2026 | 128 (2024), 192 (2025), 115 (2026 ytd) |
-| Gates Open Research | Gates Foundation | 887 | **563** | 2017–2026 | 87 (2024), **42 (2025), 25 (2026 ytd)** |
-| Open Research Africa | (AAS successor) | 181 | **138** | 2019–2026 | 13 (2024), 36 (2025), 62 (2026 ytd) |
-| **AAS Open Research** | African Academy of Sciences | 172 | **114** | **2018–2022** | 38 (2021), **3 (2022), then nothing** |
-| **AMRC Open Research** | Assoc. of Medical Research Charities | 38 | **27** | **2019–2022** | 16 (2021), **4 (2022), then nothing** |
-
-Three status findings, each independently probed:
-
-- **AAS Open Research → Open Research Africa. Confirmed.** `https://aasopenresearch.org/`
-  returns **HTTP 200 after a redirect to `https://openresearchafrica.org/`** (S4) [WEB],
-  and the Crossref record shows AAS Open Research stopping in 2022 while Open Research
-  Africa continues (S1). This was a rename/rehome, not a closure, and the successor is
-  actually growing again (62 records in 2026 to date, its best year).
-- **AMRC Open Research is effectively dead.** **27 distinct articles ever**, none
-  registered since 2022 (S1). The site itself could not be evaluated:
-  `https://amrcopenresearch.org/` returned **HTTP 403 with `cf-mitigated: challenge`,
-  `server: cloudflare`** to all four user-agents tried (S4) — a bot challenge, *not* a
-  404, so the site is probably still served to browsers. **The Crossref record is the
-  evidence, not the HTTP status.** Same 403-challenge situation for
-  `https://hrbopenresearch.org/`, which is clearly alive from its Crossref activity.
-- **Gates Open Research is being superseded from inside.** Gates' own about page states
-  that "**for papers submitted after August 2024, all articles are first published as
-  preprints on our associated preprint server, VeriXiv**", with peer review happening on
-  VeriXiv and only the final version of record landing on Gates Open Research (S3) [DOC].
-  That explains the collapse from 87 records in 2024 to 42 in 2025 and 25 in 2026.
-  `https://verixiv.org/` returns HTTP 200 (a 55,677-byte F1000-platform SPA shell, byte-
-  identical in size to the Open Research Africa and Wellcome shells — the same software
-  again) (S4) [WEB/INF].
-
-**Assessment.** These are good platforms — open named review, CC BY, funder-paid, fast —
-and Wellcome Open Research at 4,009 articles is a real body of work. But as *archives*
-they are useless: the corpus of Wellcome Open Research is, by construction, "things
-Wellcome paid for". And the family's durability record over eight years is one rename, one
-abandonment and one internal succession out of seven instances.
-
-## 4. PeerJ Preprints (2013–2019) — closed, content intact
-
-- **URL:** https://peerj.com/preprints/ · Crossref prefix `10.7287`
-- **Status: CLOSED to new deposits.** Crossref shows `posted-content` under `10.7287`
-  running **2013–2019 and stopping dead**: 220 (2013), 730, 1,067, 1,352, 1,042, 1,297,
-  **738 (2019), then zero** (S5) [API].
-- **Size: 6,446 preprint DOIs → 5,068 distinct preprints** (versions are separate DOIs,
-  suffix `v1`, `v2`, …) (S5) [API].
-
-**What happened to the content — probed, and the answer is good.** All 6,446 records still
-carry a Crossref landing URL of the form `https://peerj.com/preprints/<id>v<n>` (S5).
-Resolution test, 2026-09-01 (S6) [WEB]:
-
-- `https://doi.org/10.7287/peerj.preprints.27295v2` → **302 → `https://peerj.com/preprints/27295v2`**
-- `https://doi.org/10.7287/peerj.preprints.1097v2` → **302 → `https://peerj.com/preprints/1097v2`**
-- **Negative control:** `https://doi.org/10.7287/peerj.preprints.99999999v1` → **HTTP 404
-  at doi.org**, no redirect at all. ✅ The DOI system distinguishes real from fabricated
-  PeerJ preprint DOIs.
-
-The final fetch of the real landing pages returns **HTTP 403 with `cf-mitigated: challenge`,
-`server: cloudflare`** — peerj.com bot-challenges automated clients (S6). So: **the DOIs
-resolve and the pages exist; only scripted access is blocked.** Treat PeerJ Preprints as a
-frozen but intact archive.
-
-**Licensing is the best in this record: essentially the whole corpus is CC BY.** 6,088 of
-6,446 records carry CC BY 4.0, 325 CC BY 3.0, 30 CC0 (S5) [API].
-
-**Why it matters to a software reader:** PeerJ Preprints is where **QIIME 2** was
-announced. *"QIIME 2: Reproducible, interactive, scalable, and extensible microbiome data
-science"*, `10.7287/peerj.preprints.27295v2`, posted **2018-12-03**, later *Nature
-Biotechnology* 2019 (S6) [API]. One of the most-used pieces of scientific software in
-microbiology has its preprint of record on a server that no longer accepts submissions.
-
-## 5. Preprints with The Lancet (Elsevier / SSRN) — alive
-
-- **URL:** https://www.ssrn.com/index.cfm/en/the-lancet/ · **HTTP 200**, 20,451 B,
-  2026-09-01 (S7) [WEB]
-- **Status: ALIVE.** I expected to find this discontinued; it is not. The page renders a
-  live series with **"All Journals (25550)"** papers listed.
-- **Launch year: [NOT-VERIFIED].**
-
-Self-description, verbatim (S7) [DOC]: "a collaboration between The Lancet Group of
-journals and SSRN to facilitate the open sharing of preprints for early engagement,
-community comment, and collaboration. **Preprints available here are not *Lancet*
-publications or necessarily under review with a *Lancet* journal.** … **The usual SSRN
-checks and a *Lancet*-specific check for appropriateness and transparency have been
-applied.** The findings should not be used for clinical or public health decision-making
-or presented without highlighting these facts."
-
-Two things to note. The disclaimer that a posting is not necessarily under *Lancet* review
-makes this closer to a genuine open preprint server than Cell Sneak Peek (§6). And SSRN's
-footer asserts "**All rights are reserved, including those for text and data mining, AI
-training, and similar technologies**" (S7) — SSRN is an Elsevier property and its default
-posture is restrictive, per-paper licences notwithstanding. **Do not plan on bulk TDM
-here.**
-
-*(Caveat: I report "25550" as the figure the page displayed under the heading "Preprints
-with The Lancet Papers". Whether that counter is scoped to this series or to a wider SSRN
-grouping is [NOT-VERIFIED].)*
-
-## 6. Cell Press Sneak Peek (Elsevier / SSRN) — alive
-
-- **URL:** https://www.ssrn.com/index.cfm/en/cell-press-sneak-peek/ · **HTTP 200**,
-  23,986 B, 2026-09-01 (S8) [WEB]. Note `…/en/cell-sneak-peek/` and `…/en/sneak-peek/`
-  both **404** — the working slug is `cell-press-sneak-peek`, and the 404 page carries the
-  notice "SSRN is no longer supporting commercial products such as Research Paper Series",
-  which is easy to mistake for a closure notice for this service. It is not.
-- **Status: ALIVE.** **12,404 papers**, with a live per-journal breakdown.
-- **Launch year: [NOT-VERIFIED].**
-
-Self-description (S8) [DOC]: "**an author opt-in preview of the papers under review in our
-primary research journals.** An invitation to submit to Sneak Peek is provided to all
-authors of primary research articles at the time they are first sent for peer review."
-
-That is the purest example of the shop-window pattern in §0: **the inclusion criterion is
-"currently under review at a Cell Press journal"**. Per-journal counts as displayed
-2026-09-01: Cell Reports 2,545 · Cell 778 · Cell Reports Medicine 328 · Cell Reports
-Physical Science 300 · Cell Reports Methods 242 · Chem 210 · Cell Host & Microbe 203 ·
-Cell Stem Cell 189 · Cell Metabolism 173 · Cell Chemical Biology 169 · Cancer Cell 144 ·
-Cell Systems 126 · Cell Genomics 66 · Cell Biomaterials 3 · Chem Catalysis 0 · Cell
-Reports Sustainability 0 (S8).
-
-**Assessment:** useful for one narrow purpose — seeing a specific paper months before Cell
-publishes it — and useless for anything else. Not an archive, not comprehensive, and the
-selection is doubly filtered (Cell Press sent it for review *and* the author opted in).
-
-## 7. Nature Precedings (2007–2012) — defunct, but the content survived
-
-**The cautionary tale of this group, and the good news is better than expected.**
-
-- **Original host is gone.** `https://precedings.nature.com/` and
-  `http://precedings.nature.com/`: DNS resolves (192.129.25.40) but **both ports refuse
-  the connection** — `curl: (7) Failed to connect … Could not connect to server`,
-  2026-09-01 (S9) [WEB]. A live DNS record pointing at a dead host is the worst
-  combination: link checkers see a name that resolves, users see nothing.
-- **The content is alive at a different URL.** `https://www.nature.com/npre` returns
-  **HTTP 200, 126,578 B**, headed *"Welcome to Nature Precedings — Pre-publication
-  research and preliminary findings for the Life Science community **from 2007 until
-  2012**"*, with a browsable, dated article listing (S9) [WEB].
-- **Size: 3,449 records** — 2,837 "Research" plus 612 "Multimedia" — from the
-  nature.com search facet `journal=npre`, 2026-09-01 (S9) [WEB].
-- **DOIs still resolve.** `https://doi.org/10.1038/npre.2012.7027.1` → **HTTP 200** at
-  `https://www.nature.com/articles/npre.2012.7027.1` (S9) [WEB].
-  **Negative control:** `https://doi.org/10.1038/npre.1999.99999.1` → **HTTP 404 at
-  doi.org**. ✅
-
-**The lesson.** Nature Publishing Group shut a preprint server after five years — this is
-the canonical case of a major publisher closing one — and yet, fourteen years on, every
-citation to a Precedings DOI still lands on the paper. What broke was the *hostname*.
-What held was the *DOI* plus the publisher's willingness to keep serving the objects under
-its main domain. If you are choosing where to deposit, note carefully which of those two
-things you are actually relying on. Note also the asymmetry of luck: Nature is still in
-business. A publisher that had folded would have taken the content with it.
-
-Content skews to 2007–2012 life science, and includes instrumentation work — the
-2012-04-04 listing alone includes *"A novel apparatus/protocol designed for optogenetic
-manipulation and recording of individual neurons during a motivation and working memory
-task in the rodent"* (S9).
-
-## 8. JMIR Preprints (JMIR Publications)
-
-- **URL:** https://preprints.jmir.org/ · **HTTP 200**, 2,113,332 B, 2026-09-01 (S4) [WEB]
-- **Status: ALIVE and, by volume, the largest thing in this record.**
-- **Size: 41,766 `posted-content` DOIs under prefix `10.2196`**, 2013–2026 (S10) [API].
-  Yearly: 1 (2013), 1, 5, 48, 1,235 (2017), 2,599, 2,663, **5,634 (2020)**, 5,024, 4,653,
-  5,564, 5,354, 5,437 (2025), 3,548 (2026 ytd).
-- **Launch year:** JMIR's own claim is **2009**; Crossref shows essentially nothing before
-  2016 and the service only becomes substantial in **2017**. Report the discrepancy rather
-  than resolving it — **the 2009 date is [NOT-VERIFIED]**, and a 2016/2017 effective start
-  is what the DOI record supports [INF].
-
-**The model:** JMIR Preprints is the *open-peer-review-of-submissions* variant. Manuscripts
-submitted to a JMIR journal are, at the author's option, posted immediately as preprints
-and opened to public review while the formal editorial process runs. So it sits between
-Cell Sneak Peek (pure preview, no public review) and F1000Research (publish-then-review as
-the actual publication route): the preprint is a real, citable, DOI'd object that anyone
-can review, but the journal decision is still made conventionally behind it.
-
-**Assessment.** The volume is startling — roughly 5,000/year, comparable to medRxiv — but
-remember what it is: **the submission stream of one publisher's journal portfolio**, in
-one field (digital health / medical informatics). It is not a field-wide archive. Within
-digital health it is close to comprehensive for JMIR-bound work and worth searching. The
-41,766 figure should not be compared with bioRxiv's 347,954 as though they measured the
-same thing.
-
-## 9. ARPHA Preprints (Pensoft)
-
-- **URL:** https://preprints.arphahub.com/ · **HTTP 200**, 91,498 B, 2026-09-01 (S4) [WEB]
-- **Operator:** **Pensoft Publishers**, on its own ARPHA publishing platform.
-- **Launched 2020** (first Crossref `posted-content` records under `10.3897`: 16 in 2020).
-- **Status: ALIVE and growing**: 119 (2021), 158, 193, 185, **221 (2025)**, 166 (2026 ytd);
-  **1,058 total** (S10) [API].
-- **Licence:** the site states content is under **CC BY 4.0** (S4) [WEB].
-
-**Gate:** limited to manuscripts being submitted to ARPHA/Pensoft journals — the same
-publisher-tied pattern. Content reflects Pensoft's specialisms: biodiversity, taxonomy,
-ecology, natural-history collections and their data infrastructure. The front page on
-2026-09-01 was showing, among others, *"From collection trays to AI-ready data: An
-operational framework…"* and EU-project deliverables *"D3.1 Availability of image & sound
-datasets for training…"* and *"D5.1 Strategy for establishing a European-wide
-consortium…"* (S4). That last pair is worth noting: **ARPHA Preprints is used as a
-citable home for EU project deliverables**, which is a genuinely useful niche and not
-something bioRxiv would accept.
-
-**Assessment:** small, healthy, narrow. Relevant to this knowledge base only for
-biodiversity-informatics data infrastructure.
-
-## 10. Beilstein Archives (Beilstein-Institut)
-
-- **URL:** https://www.beilstein-archives.org/ → 200 at `/xiv/`, 85,673 B, 2026-09-01
-  (S4) [WEB]
-- **Operator:** the **Beilstein-Institut**, a German non-profit foundation; the same body
-  that publishes the *Beilstein Journal of Organic Chemistry* and *Beilstein Journal of
-  Nanotechnology*, both fully open access and free to authors.
-- **Launched 2019.** **Size: 726 preprints** (Crossref `posted-content` under prefix
-  `10.3762`) (S10) [API].
-- **Status: ALIVE but shrinking** — 161 (2019), 145, 93, 92, 68, 73, **66 (2025)**, 28
-  (2026 ytd). The trend is down by roughly 60 % from its first year.
-
-**Gate:** deposits are limited to manuscripts submitted to a Beilstein journal. Subject
-areas advertised on the site include **Nanotechnology**, organic chemistry, bioorganic
-chemistry/chemical biology, catalysis and supramolecular chemistry (S4).
-
-**Relevance:** the Nanotechnology stream is the only part likely to matter here — SPM,
-nanofabrication, self-assembly, surface chemistry. But at ~70 deposits a year across all
-subjects, expect a handful of relevant items annually. See [chemrxiv.md](chemrxiv.md) for
-the large chemistry server, and [ecsarxiv.md](ecsarxiv.md) for the electrochemistry one.
-
-## 11. agriRxiv — the domain is dead, the service moved
-
-The most instructive failure in this record, because the two halves came apart.
-
-- **`https://agrirxiv.org/` times out** (connection timed out after 30 s, 2026-09-01).
-  `http://agrirxiv.org/` redirects to `https://www.agrirxiv.org/`, which returns **HTTP
-  200, 2,963 bytes** — and the body is a **Namecheap domain-parking page**: *"has been
-  recently registered with namecheap.com … Want a domain name like this? Discover domains
-  on auction now."* DNS confirms it: `www.agrirxiv.org` resolves to
-  `parkingpage.namecheap.com` (S11) [WEB]. **The agriRxiv domain has lapsed and been
-  re-registered by a parking service.**
-- **But the DOIs are fine.** Crossref prefix `10.31220` (CABI) holds **1,054 records**,
-  1,051 of them `posted-content`, spanning **2017–2026 and still receiving deposits**: 10
-  (2017), 230 (2018), 190, 178, 88, 46, 58, 71, **94 (2025), 89 (2026 ytd)** (S12) [API].
-- **Two hosting eras, visible in the DOI suffixes** (S12) [API]:
-  - **2017–~2020: OSF Preprints.** Records like `10.31220/osf.io/k6d8f` with landing URL
-    `https://osf.io/k6d8f` — agriRxiv began as a white-labelled OSF Preprints instance,
-    like [ECSarXiv](ecsarxiv.md).
-  - **~2021–present: CABI Digital Library.** Records like
-    `10.31220/agriRxiv.2024.00270` with landing URL
-    `http://www.cabidigitallibrary.org/doi/10.31220/agriRxiv.2024.00270`.
-- **Resolution test:** `https://doi.org/10.31220/agriRxiv.2021.00061` → redirects to
-  `https://www.cabidigitallibrary.org/doi/10.31220/agriRxiv.2021.00061`, which returns
-  **403 with a Cloudflare challenge** (S12) [WEB] — same bot-challenge situation as PeerJ;
-  the record exists, scripted access is blocked.
-
-So: **agriRxiv is not dead, but every human-facing entry point to it is broken.** The
-brand domain is a parking page, the OSF-era landing pages are orphaned from the current
-service, and the current host bot-challenges. Anyone Googling "agriRxiv" in 2026 lands on
-a domain auction. This is a governance failure, not a technical one — nobody renewed the
-domain. **The DOIs saved it, again.**
-
-*(Operator note: the brief lists agriRxiv as CABI + Open Access India, 2017. The 2017 start
-and CABI's DOI prefix are confirmed (S12); the Open Access India co-founding role is
-**[NOT-VERIFIED]** here.)*
-
-## 12. Sources
-
-- **S1** Crossref REST API, prefix `10.12688` — full cursor pagination of all 33,289
-  records (`select=DOI,container-title,license,type`) plus `container-title` and
-  `published` facets · retrieved **2026-09-01** · per-platform record and distinct-article
-  counts, activity windows, licence distribution; prefix registered to **"F1000 Research
-  Ltd"**, Crossref member 2560. Log:
-  `scratch/preprint-repositories/lifesci/f1000-scan.txt`. [API]
-- **S2** https://f1000research.com/about (How It Works) · retrieved 2026-09-01 ·
-  publishing model, "no Editor (or Editor-in-Chief)…", the three reviewer statuses and
-  their verbatim definitions, versioning policy, the two-Approved indexing threshold and
-  the list of indexes, scope statement, posters/slides exclusion. [DOC]
-- **S3** https://gatesopenresearch.org/about · retrieved 2026-09-01 · the Gates-grant
-  eligibility rule; the August-2024 switch to first-publication on **VeriXiv**; CC BY
-  statement. [DOC]
-- **S4** Live reachability probes, 2026-09-01, Chrome-131 UA unless noted:
-  `f1000research.com` 200/114,761 · `wellcomeopenresearch.org` 200/56,615 ·
-  `gatesopenresearch.org` 200/111,640 · `aasopenresearch.org` **200 after 301 →
-  openresearchafrica.org**/55,677 · `openresearchafrica.org` 200/55,677 ·
-  `verixiv.org` 200/55,677 · `amrcopenresearch.org` **403** (also 403 to
-  `curl/8.5.0`, `WhatsApp/2.23.20.0`, ClaudeBot) · `hrbopenresearch.org` **403** (same
-  four UAs) · `preprints.jmir.org` 200/2,113,332 · `preprints.arphahub.com` 200/91,498 ·
-  `beilstein-archives.org` 200 → `/xiv/` /85,673. Response headers for the 403s:
-  `server: cloudflare`, `cf-mitigated: challenge`. [WEB]
-- **S5** Crossref REST API, prefix `10.7287`, `filter=type:posted-content`, full
-  pagination of 6,446 records · retrieved 2026-09-01 · 5,068 distinct base DOIs, year
-  distribution 2013–2019, landing-URL shape, licence distribution. [API]
-- **S6** DOI resolution probes 2026-09-01: `10.7287/peerj.preprints.27295v2` and
-  `…1097v2` → 302 to `peerj.com/preprints/…` then 403 Cloudflare challenge;
-  `10.7287/peerj.preprints.99999999v1` → **404 at doi.org** (negative control). Crossref
-  record for `10.7287/peerj.preprints.27295v2`: type `posted-content`, title "QIIME 2:
-  Reproducible, interactive, scalable, and extensible microbiome data science", posted
-  2018-12-03. [API/WEB]
-- **S7** https://www.ssrn.com/index.cfm/en/the-lancet/ · retrieved 2026-09-01 · HTTP 200,
-  20,451 B · self-description quoted in §5; "All Journals (25550)"; the Elsevier
-  all-rights-reserved / no-TDM footer. [WEB/DOC]
-- **S8** https://www.ssrn.com/index.cfm/en/cell-press-sneak-peek/ · retrieved 2026-09-01 ·
-  HTTP 200, 23,986 B · self-description quoted in §6; "All Journals (12404)" and the
-  per-journal breakdown. Also probed `…/en/cell-sneak-peek/` and `…/en/sneak-peek/`, both
-  **404** with the "SSRN is no longer supporting commercial products" text. [WEB/DOC]
-- **S9** Nature Precedings probes, 2026-09-01: `precedings.nature.com` — DNS resolves to
-  192.129.25.40, **connection refused on both 80 and 443**; `https://www.nature.com/npre`
-  — HTTP 200, 126,578 B, "from 2007 until 2012"; `https://www.nature.com/search?journal=npre`
-  — facet "Nature Precedings (3449)", "Showing 1–50 of 3449 results", article types
-  Research 2,837 / Multimedia 612; `https://doi.org/10.1038/npre.2012.7027.1` → 200 at
-  `nature.com/articles/npre.2012.7027.1`; `https://doi.org/10.1038/npre.1999.99999.1` →
-  **404 at doi.org** (negative control). [WEB]
-- **S10** Crossref REST API, `filter=type:posted-content` with `published` facet on
-  prefixes `10.2196` (JMIR, 41,766), `10.3897` (Pensoft/ARPHA, 1,058) and `10.3762`
-  (Beilstein, 726) · retrieved 2026-09-01. [API]
-- **S11** agriRxiv domain probes, 2026-09-01: `https://agrirxiv.org/` connection timeout;
-  `http://agrirxiv.org/` → 200 at `https://www.agrirxiv.org/`, 2,963 B, Namecheap parking
-  page; `getent hosts www.agrirxiv.org` → `parkingpage.namecheap.com`. [WEB]
-- **S12** Crossref REST API, prefix `10.31220` · retrieved 2026-09-01 · 1,054 records
-  (1,051 `posted-content`, 3 `journal-article`), year distribution 2017–2026, the two DOI
-  suffix families (`10.31220/osf.io/<id>` → `osf.io`, `10.31220/agriRxiv.<year>.<n>` →
-  `cabidigitallibrary.org`); plus DOI-resolution probe of
-  `10.31220/agriRxiv.2021.00061` → CABI Digital Library, 403 Cloudflare challenge. [API/WEB]
-
-### Not verified
-
-- **F1000Research's corporate parent.** Crossref says "F1000 Research Ltd" (S1). The
-  Taylor & Francis / Informa acquisition is not stated on any page I retrieved.
-- **Launch years for Preprints with The Lancet and Cell Press Sneak Peek.**
-- **JMIR Preprints' claimed 2009 launch** — the Crossref record supports 2016/2017 as the
-  effective start (§8).
-- **Whether SSRN's "25550" counter is scoped to Preprints with The Lancet** or to a wider
-  grouping (§5).
-- **Open Access India's role in agriRxiv** (§11).
-- **Whether `amrcopenresearch.org` and `hrbopenresearch.org` render for a real browser** —
-  both returned Cloudflare challenges to every automated client tried (S4). The
-  alive/dead calls for those two rest on Crossref activity, not on HTTP status.
-- **VeriXiv's size, launch date and exact relationship to Gates Open Research** beyond the
-  August-2024 statement in S3.
-- **Eligibility-gate wording for Wellcome, HRB, AMRC and Open Research Africa** — those
-  About pages are JavaScript-rendered SPA shells and returned no readable policy text to
-  a scripted fetch. The Gates wording (S3) is quoted as representative of the family;
-  that generalisation is **[INF]**.
-- **Whether any of these platforms publishes a preprint-to-publication rate.** None found.
diff --git a/research/preprint-repositories/natural-sciences-and-niche-servers.md b/research/preprint-repositories/natural-sciences-and-niche-servers.md
deleted file mode 100644
index 11ebdef..0000000
--- a/research/preprint-repositories/natural-sciences-and-niche-servers.md
+++ /dev/null
@@ -1,499 +0,0 @@
-# Natural-science and niche preprint servers — grouped record
-
-- **Compiled:** 2026-09-01 · **All reachability and count probes run:** 2026-09-01 / 2026-09-02 UTC
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Scope note.** These are the small, single-discipline preprint servers of the natural
-> sciences. Almost none carry electronics, software or systems content, so — as instructed —
-> they are covered compactly and the weight is carried by the **measured status table**
-> plus the durability evidence. Two entries get more room:
-> - **[FocUS Archive](#10-focus-archive)** — focused-ultrasound therapy: the only entry in
->   this file with genuine **hardware** content (phased-array transducers, drive
->   electronics, MR-guided targeting).
-> - **[mp_arc](#12-mp_arc)** — **opened July 1991**, contemporaneous with arXiv, one of the
->   oldest preprint archives in existence. Frozen since December 2023, still fully served,
->   and the best-preserved dead archive measured anywhere in this directory.
-
-## 0. Method, and the OSF status trap
-
-Nine servers here are or were hosted by the **Center for Open Science (COS)** on OSF, whose
-web pages are a JavaScript SPA:
-
-> **`https://osf.io/preprints/<anything>` returns HTTP 200 and an identical 4,207-byte
-> shell even for providers that do not exist.**
-
-Verified as a negative control: `https://osf.io/preprints/eyexiv/` returned **HTTP 200,
-4,207 bytes** on 2026-09-02, yet `eyexiv` does not appear in the authoritative provider list
-at `https://api.osf.io/v2/preprint_providers/?page[size]=100` (32 providers) (S1) [API]. All
-OSF figures below therefore come from `api.osf.io/v2/preprints/?filter[provider]=<slug>` →
-`links.meta.total`, and status claims from `api.osf.io/v2/preprint_providers/<slug>/`, whose
-`description` carries the operator's own closure notice (S2) [API] [DOC]. Count-endpoint
-negative control: `filter[provider]=bogusprovider12345` → `total: 0`, not an error [API].
-Full discussion of the method in
-[social-sciences-and-humanities.md §0](social-sciences-and-humanities.md#0-method-and-the-osf-status-trap).
-
-Web reachability used the `AGENTS.md` UA ladder: default `curl` → Chrome 131 →
-WhatsApp/2.23.20.0 → ChatGPT-User/1.0 → ClaudeBot/1.0.
-
-## 1. Status and size table
-
-| Server | URL probed 2026-09-02 | Operator | Launched | Status 2026-09-02 | Records | Source of count |
-|---|---|---|---|---|---|---|
-| **EarthArXiv** | `eartharxiv.org` | **California Digital Library**, on **Janeway 1.8.0** — moved off OSF | 2017 | **ALIVE**, submissions open | **7,525** live | operator's own listing [WEB] |
-| ↳ legacy on OSF | `osf.io/preprints/eartharxiv` | COS | 2017 | **FROZEN**, submissions off, content retained | **1,649** | OSF API [API] |
-| ↳ Crossref | prefix `10.31223` (CDL) | — | — | — | **8,171** | Crossref [API] |
-| **ESS Open Archive** (ex-**ESSOAr**) | `essopenarchive.org` (`essoar.org` redirects here) | **AGU + Wiley**, on **Authorea** infrastructure | 2018 | **ALIVE** — but **HTTP 403 on all five UAs** | **≈23,000–27,000** (estimate, see §4) | Crossref [API] + [INF] |
-| **EcoEvoRxiv** | `ecoevorxiv.org` | **California Digital Library**, Janeway — moved off OSF | 2018 | **ALIVE**, submissions open | **3,604** live | operator's own listing [WEB] |
-| ↳ legacy on OSF | `osf.io/preprints/ecoevorxiv` | COS | 2018 | **FROZEN**, submissions off | **909** | OSF API [API] |
-| **PaleorXiv** | `paleorxiv.org` → `osf.io/preprints/paleorxiv` | COS | 2017 | **ALIVE — submissions OPEN.** *Not frozen; see §6* | **282** | OSF API [API] |
-| **MarXiv** | `osf.io/preprints/marxiv` | COS | 2017–2020 | **CLOSED**, content retained | **454** | OSF API [API] |
-| ↳ own domain | `marxiv.org` | — | — | **DEAD** — TCP connection refused, port 443 | — | probe [WEB] |
-| **NutriXiv** | `osf.io/preprints/nutrixiv` | COS | 2018 | **CLOSED**, content retained | **85** | OSF API [API] |
-| ↳ own domain | `nutrixiv.org` | — | — | **DEAD** — DNS NXDOMAIN, all five UAs | — | probe [WEB] |
-| **SportRxiv** | `sportrxiv.org` | **STORK** (Society for Transparency, Openness and Replication in Kinesiology); DOIs registered via **University of Ottawa Library** | 2017 | **ALIVE** on **Open Preprint Systems 3.3.0.22** | **761** | OAI `completeListSize` [API] |
-| ↳ legacy on OSF | `osf.io/preprints/sportrxiv` | COS | 2017 | **CLOSED 2021-08-27**, content retained | **377** | OSF API [API] [DOC] |
-| **FocUS Archive** | `osf.io/preprints/focusarchive` | **Focused Ultrasound Foundation** | 2018 | **ALIVE**, submissions open, pre-moderation | **84** | OSF API [API] |
-| **Eyexiv** | `eyexiv.org`, `.com`, `.net`, `.io` | International Virtual Ophthalmic Research Center (S3) | 2022 (S3) | **DEAD or NEVER-RESOLVING** — DNS NXDOMAIN on every domain tried, all five UAs; **not an OSF provider** | **[NOT-VERIFIED]** | — |
-| **mp_arc** | `web.ma.utexas.edu/mp_arc/` | **UT Austin** (with Università Roma Tre, Universitat de Barcelona) (S3) | **July 1991** | **FROZEN Dec 2023 — fully served, full text intact** | **6,152** | counted from operator's year indices [API] |
-| **Frenxiv** | `osf.io/preprints/frenxiv` | COS | 2018–2022 | **CLOSED**, content retained | **128** | OSF API [API] |
-| ↳ own domain | `frenxiv.org` | — | 2018 | **ZOMBIE** — HTTP 200, but frozen at Oct 2020 with a stale maintenance banner | not verified | probe [WEB] |
-| **WikiJournal Preprints** | `en.wikiversity.org/wiki/WikiJournal_Preprints` | **WikiJournal User Group** on Wikiversity (**MediaWiki**) | 2017 (S3) | **ALIVE** | **421 pages** under the `WikiJournal Preprints/` prefix | MediaWiki API [API] |
-
-**Conflicts recorded, not resolved.** Wikipedia's buckets (S3) give mp_arc `>10,000` against
-my measured **6,152**; EarthArXiv `>1,000` against **7,525**; ESSOAr `>1,000`; SportRxiv,
-NutriXiv, FocUS Archive and WikiJournal `<100` or `>100`. Where the two disagree, the
-measured figure is stated with its method and Wikipedia's bucket is recorded alongside.
-
-## 2. What the probe evidence shows
-
-**(a) "Moved off OSF" is now the dominant life-cycle event, and it works.** EarthArXiv and
-EcoEvoRxiv both migrated to **Janeway at the California Digital Library**, and both did it
-*correctly*: the OSF record still exists, the vanity domain resolves to the new host, and the
-operator's own OSF description explains the move and promises DOI redirection. EarthArXiv's:
-*"EarthArXiv.org is now hosted by the California Digital Library (CDL). The EarthArXiv.org
-URL now redirects to the CDL Janeway platform. **All article DOIs will redirect to CDL**"*
-(S2) [DOC]. EcoEvoRxiv's is near-identical. **This is the reference example of a
-well-executed repository migration** — contrast the vanity-domain losses documented in
-[social-sciences-and-humanities.md](social-sciences-and-humanities.md) and
-[closed-and-defunct-servers.md](closed-and-defunct-servers.md).
-
-**(b) The self-hosted vanity domain is the component that dies.** `marxiv.org` refuses TCP
-connections; `nutrixiv.org` is NXDOMAIN; `frenxiv.org` serves a page frozen in October 2020.
-In all three cases the OSF-held content is intact and countable. Same finding as the
-regional servers file — see
-[regional-and-national-servers.md](regional-and-national-servers.md).
-
-**(c) Bot-defence is now a first-order retrieval problem, and the byte size is a
-fingerprint.** `essopenarchive.org` returned **HTTP 403 / 5,622 bytes** on all five UAs.
-`www.authorea.com` returned **HTTP 403 / 5,620 bytes**. `www.techrxiv.org` and
-`www.scienceopen.com` returned 403 at 5,620 and 5,602 bytes. These are all the same
-Cloudflare managed-challenge page; the ~5.6 kB body is a reliable signature of "blocked, not
-broken". **Crossref and OAI-PMH remain open in every one of these cases**, which is why every
-ESSOAr figure below comes from Crossref.
-
----
-
-## 3. EarthArXiv
-
-- `eartharxiv.org` · California Digital Library · 2017 · **ALIVE** · **7,525 preprints** [WEB]
-
-The Earth-science preprint server, founded 2017 on OSF and since migrated to **Janeway**, the
-open-source journal/repository platform from Birkbeck, University of London.
-
-The migration is verifiable from the machine interface rather than from press releases.
-`https://eartharxiv.org/api/oai?verb=Identify`, retrieved 2026-09-02, returns
-`repositoryName: EarthArXiv`, `adminEmail: no-reply@escholarship.org`, `earliestDatestamp:
-2017-10-23T14:36:42Z`, and a `toolkit` block naming **Janeway 1.8.0**, Birkbeck, and
-`http://janeway.systems/` (S4) [API]. The `escholarship.org` admin address and the site
-footer — *"Powered by the California Digital Library and Janeway"* — establish the host [WEB].
-The earliestDatestamp independently confirms the 2017 launch.
-
-**Counts, three of them, all different and all defensible:** 7,525 on the live site,
-1,649 still listed under the frozen OSF provider, and 8,171 works registered to CDL's
-Crossref prefix `10.31223` (which mixes native `10.31223/X5…` DOIs with migrated
-`10.31223/osf.io/…` ones) (S5) [API]. The Crossref figure is the superset; it includes
-withdrawn and superseded deposits.
-
-**Computing content: negligible**, though remote-sensing, geospatial ML and
-methane-detection work appears — the live front page on 2026-09-02 led with *"Intelligent
-National Map: A Vision for Distributed and Agentic Geospatial Intelligence"* and satellite
-methane quantification [WEB].
-
-## 4. ESS Open Archive (formerly ESSOAr)
-
-- `essopenarchive.org` · **American Geophysical Union + Wiley** · 2018 · **ALIVE** ·
-  **≈23,000–27,000 records (estimate)** [API] [INF]
-
-Earth and space science preprints *and conference posters* — the poster mandate is unusual
-and makes it the main durable home for AGU meeting material.
-
-**It runs on Authorea infrastructure**, and Authorea is Wiley-owned. A sibling record covers
-the platform in detail: see **[authorea.md](authorea.md)**. The evidence for the coupling is
-direct: DOIs minted for ESS Open Archive today live under Authorea's Crossref prefix
-**10.22541** in the `essoar` namespace (e.g. `10.22541/essoar.169290541.19921945/v1`), and
-every one of 100 sampled `posted-content` records under that prefix reports
-`publisher: Wiley` (S5) [API]. Legacy deposits use Wiley's own prefix in the form
-`10.1002/essoar.*` — and a spot-check of `10.1002/essoar.10500599.1` returns
-`institution: [{name: "Earth and Space Science Open Archive", acronym: ["ESSOAr"]}]` (S5)
-[API].
-
-**Why the count is an estimate, stated honestly.** The website returned **HTTP 403 on all
-five user-agents** (5,622-byte Cloudflare challenge), so no operator-published total was
-obtainable. Reconstructing from Crossref:
-
-- `filter=prefix:10.1002,type:posted-content` → **13,033** works; a random sample of 100
-  found **99 with DOIs of the form `/essoar.*`** (the hundredth was `/oarr.*`) (S5) [API].
-  So the legacy corpus is ~12,900.
-- `filter=prefix:10.22541,type:posted-content` → **80,496** works; four independent random
-  samples of 100 found **17, 16, 12 and 17** `essoar`-namespace DOIs, the rest being generic
-  Authorea `au.*` preprints (S5) [API]. At ~15.5% that implies **≈12,500** ESS Open Archive
-  records on the Authorea prefix, with sampling error of a couple of thousand.
-
-**Total ≈ 23,000–27,000 [INF from API].** Treat this as an order-of-magnitude figure, not a
-count. **[NOT-VERIFIED]:** the operator's own published total.
-
-**Computing content: negligible.** Instrumentation and data-system papers appear
-(satellite payloads, sensor networks), but there is no software or electronics category.
-
-## 5. EcoEvoRxiv
-
-- `ecoevorxiv.org` · California Digital Library, Janeway · 2018 · **ALIVE** ·
-  **3,604 preprints** [WEB]
-
-Ecology, evolution and conservation. Same story as EarthArXiv and executed the same way: the
-OSF description reads *"Submissions are currently suspended. EcoEvoRXiv.org is moving to the
-Janeway platform hosted by the California Digital Library (CDL) … All article DOIs will
-redirect"* (S2) [DOC]. Live site: 3,604; frozen OSF provider: 909; CDL Crossref prefix
-`10.32942`: 3,675 (S5) [API]. The near-agreement between the live count and the Crossref
-count (a 2% gap) is a good sign — the migration carried the DOIs across.
-
-**Computing content: none.**
-
-## 6. PaleorXiv
-
-- `paleorxiv.org` → `osf.io/preprints/paleorxiv` · COS · 2017 · **ALIVE** · **282
-  preprints** [API]
-
-**Correction to the working assumption.** PaleorXiv was expected to be frozen. It is not:
-the OSF provider record on 2026-09-02 reports `allow_submissions: true` and
-`reviews_workflow: pre-moderation`, with the plain description *"A preprint archive for
-Paleontology"* — **no closure notice** (S2) [API] [DOC]. Compare the four servers in this
-file that *do* carry one (MarXiv, NutriXiv, SportRxiv, Frenxiv); the text is boilerplate and
-its absence is meaningful. `paleorxiv.org` redirects correctly to OSF.
-
-It is small and slow-moving, but open. **Computing content: none.**
-
-## 7. MarXiv
-
-- `osf.io/preprints/marxiv` · COS · **2017–2020, CLOSED** · **454 preprints retained** [API]
-
-Ocean and marine-climate science. The operator's closure notice is unusually explicit about
-preservation: *"Submissions for Marxiv are now closed. **Existing preprints will be
-maintained by COS as part of the long-term data preservation plan.**"* (S2) [DOC] — and the
-API confirms all 454 are still served, six years on.
-
-`marxiv.org` **refuses TCP connections on port 443** under all five user-agents [WEB]. This
-is a cleaner failure than a parking page or a hijack: nothing is served, so nothing
-misleading is served. Cite the OSF DOI. See
-[closed-and-defunct-servers.md](closed-and-defunct-servers.md).
-
-## 8. NutriXiv
-
-- `osf.io/preprints/nutrixiv` · COS · 2018 · **CLOSED** · **85 preprints retained** [API]
-
-Nutritional sciences, and the smallest server documented in this directory. Standard COS
-closure notice: *"NutriXiv is no longer able to accept new submissions. Existing content in
-this repository will remain accessible as part of COS's ongoing commitment to Open
-Science."* (S2) [DOC]. `nutrixiv.org` is **DNS NXDOMAIN** on all five UAs [WEB].
-
-Worth one line of reflection: 85 records is below the threshold at which a repository is
-doing anything a general server would not do better. The COS closure programme was, in
-substance, a rational consolidation.
-
-## 9. SportRxiv
-
-- `sportrxiv.org` · **STORK** — Society for Transparency, Openness and Replication in
-  Kinesiology · 2017 · **ALIVE on Open Preprint Systems 3.3.0.22** · **761 records** [API]
-
-Sport, exercise, performance and health research, and the one server here that migrated
-**off OSF onto self-hosted PKP software** and made it work.
-
-- **Exact migration date, first-party.** The frozen OSF provider says: *"SportRxiv is no
-  longer accepting submissions as of **8/27/2021**, and all new submissions can be posted to
-  the new platform SportRxiv OPS (sportrxiv.org)"* (S2) [DOC]. 377 legacy records remain on
-  OSF.
-- **Software and size.** The front page declares `generator: Open Preprint Systems 3.3.0.22`
-  (PKP's preprint variant of OJS). OAI-PMH at `sportrxiv.org/index.php/server/oai` reports
-  `repositoryName: SportRxiv`, `adminEmail: layan.fessler@storkinesiology.org`,
-  `earliestDatestamp: 2021-08-12` — i.e. two weeks before the OSF cutoff, so the two
-  overlapped deliberately — and `ListIdentifiers` returns
-  **`completeListSize="761"`** (S6) [API].
-- **It is genuinely active.** Two of the newest items on the front page carried
-  `Submitted 2026-09-01 · Posted 2026-09-01`, DOIs `10.51224/SportRxiv.1053` and `.1052`
-  [WEB] — same-day posting on the day of this survey.
-- **DOI ownership is a small puzzle worth recording.** Prefix `10.51224` is registered to
-  *"Society for Transparency, Openness, and Replication in Kinesiology"* and holds **779**
-  works, but sampled records report `publisher: University of Ottawa Library` with DOIs in
-  the older `10.51224/srxiv.NNN` form, while the live site mints `10.51224/SportRxiv.NNNN`
-  (S5) [API]. Two DOI generations under one prefix, with library hosting behind it. **The
-  exact hosting arrangement with uOttawa Library: [NOT-VERIFIED].**
-
-**Computing content: none.** But as a *systems* case study SportRxiv is the positive control
-for §2(b): a small community that moved to its own infrastructure, kept the DOIs, kept the
-old records readable, ran OAI-PMH, and is still posting five years later.
-
-## 10. FocUS Archive
-
-- `osf.io/preprints/focusarchive` · **Focused Ultrasound Foundation (FUSF)** · 2018 ·
-  **ALIVE**, pre-moderation · **84 preprints** [API]
-
-**The only hardware content in this file.** Focused ultrasound is a therapeutic-device
-field: hemispherical **phased-array transducers** of 128–1024 elements, per-channel drive
-electronics and phase control, **skull-aberration correction** computed from CT, MR
-thermometry for closed-loop targeting, cavitation-detection receivers, and — the part a
-systems reader will recognise — hard real-time control loops with patient-safety interlocks.
-Papers here are as likely to be about array calibration and beamforming as about biology.
-
-The provider is unusually well-specified for its size. The OSF description reads: *"Focus
-Archive is an OSF-hosted preprint space for rapid sharing of reports, data, notes, and
-methods from **Focused Ultrasound Foundation (FUSF) funded projects**"*, and links a
-first-party policy document, *Focus Archive Publication Policies 2025*, at
-`https://cdn.fusfoundation.org/2025/11/20165255/Focus-Archive-Publication-Policies-2025.pdf`;
-the advisory board is named as **Frederic Padilla** and **Joe Killroy** (S2) [DOC].
-
-**Read the scope restriction carefully before citing.** This is a **funder's** archive for
-**its own grantees' outputs**, including "reports, data, notes, and methods" — i.e. grey
-literature, not just preprints. A deposit here is evidence that FUSF funded the work and a
-moderator passed it; it is not evidence of peer review, and the corpus is *not* a
-representative sample of the focused-ultrasound literature. At 84 records it is browsable in
-full, which is the right way to use it.
-
-**[NOT-VERIFIED]:** the contents of the 2025 policy PDF — I recorded the URL from the
-operator's own metadata but did not retrieve and read the document.
-
-## 11. Eyexiv
-
-- `eyexiv.org` / `.com` / `.net` / `.io` · **all DNS NXDOMAIN** on all five UAs, 2026-09-02 ·
-  **status: unreachable** · **count [NOT-VERIFIED]**
-
-Vision science — ophthalmology, optometry. Wikipedia describes it as *"The Eye Open
-Repository, Preprints founded by Dr. F. Heidary for ophthalmology, optometry, and vision
-science"*, bucket `>100`, launched **2022**, operator **International Virtual Ophthalmic
-Research Center** (S3) [COM].
-
-**Everything I could probe failed.** Four TLDs, five user-agents each: NXDOMAIN throughout.
-It is **not** in the OSF provider list, and — this is the useful part —
-`https://osf.io/preprints/eyexiv/` nonetheless returns **HTTP 200 with the standard
-4,207-byte OSF SPA shell**, exactly as a real provider would [API] [WEB]. Eyexiv is
-therefore the cleanest available demonstration of why OSF status codes must never be trusted:
-had I probed only that URL, I would have "confirmed" a repository that does not exist there.
-
-I could not establish where, if anywhere, Eyexiv's content now lives. **[NOT-VERIFIED]:**
-launch, size, current host, and whether it ever served content at a resolvable domain.
-
-## 12. mp_arc
-
-- `https://web.ma.utexas.edu/mp_arc/` · **University of Texas at Austin** (with Università
-  Roma Tre and Universitat de Barcelona, per S3) · **July 1991 – December 2023** ·
-  **FROZEN, fully served** · **6,152 records** [API]
-
-**Flagged. This is the oldest server in this file by fourteen years and one of the oldest
-preprint archives anywhere** — arXiv's first deposit was in August 1991; mp_arc's first
-was in **July 1991**.
-
-**Its own front page states the fate, unambiguously** (retrieved 2026-09-02) (S7) [DOC]:
-
-> *"mp_arc is an electronic archive for research papers in Mathematical Physics and related
-> areas. It **accepted and posted preprints from July 1991 until December 2023**. Those
-> preprints will **stay posted here indefinitely**. But no new submissions will be
-> processed. At this point in time, there are enough alternative ways to disseminate
-> preprints."*
-
-That is the healthiest shutdown notice in this entire directory: a stated span, a stated
-preservation commitment, and a stated reason. Compare the servers that simply stopped
-answering.
-
-**Is the content still served? Yes — verified end to end.**
-
-| Probe (2026-09-02) | Result |
-|---|---|
-| `web.ma.utexas.edu/mp_arc/` | HTTP 200, `Server: Apache/2.4.58 (Ubuntu)` — a **current, maintained** OS release [API] |
-| Year index `index-91.html` … `index-23.html` | all 200; **33 index files, 1991–2023** [API] |
-| Record CGI `mp_arc-bin/mpa?yn=91-1` | 200 — Koch & Wittwer, *"On the Renormalization Group Transformation for Scalar Hierarchical Models"*, Jul 10 1991 [API] |
-| Oldest full text `mp_arc/c/91/91-1.ps.gz` | **200, 120,018 bytes, `application/postscript`.** `file` reports *gzip compressed data, last modified **Sat Apr 26 1997**, original size 426,991* [API] |
-| Newest full text `mp_arc/c/23/23-1.pdf` | **200, 351,086 bytes, valid PDF 1.5, 6 pages** [API] |
-| **Negative control** `mp_arc-bin/mpa?yn=99-99999` | HTTP **200** but 174 bytes: *"Found no abstract for 99-99999."* — a 200 does **not** mean a record exists |
-| **Negative control** `mp_arc/index-77.html` | HTTP **404**, 280 bytes — static paths do 404 correctly |
-
-**The gzip mtime is the detail to take away.** The bytes of mp_arc's first paper were last
-written in **April 1997** and are still being served, unaltered, in **2026** — 29 years of
-untouched file custody, across at least one operating-system generation (the server is now
-Ubuntu with Apache 2.4.58). No CMS, no database, no migration. Static files under a web
-server, maintained by a mathematics department.
-
-**Size — and a conflict.** Counting `<dt>YY-` entries across all 33 year indices gives
-**6,152 records** (S7) [API]. Wikipedia's bucket is `>10,000` (S3) [COM]. **Both are
-recorded; I did not resolve the discrepancy**, and note that my method counts index entries,
-which may undercount multi-version submissions. The per-year distribution is itself the
-story of the field's migration to arXiv:
-
-```
-1991  47   1996 296   2001 359   2006 286   2011 123   2016  59   2021  40
-1992  80   1997 331   2002 382   2007 236   2012 118   2017  48   2022  45
-1993 171   1998 386   2003 391   2008 172   2013  76   2018  52   2023  34
-1994 202   1999 353   2004 326   2009 169   2014  68   2019  47
-1995 249   2000 387   2005 341   2010 141   2015  76   2020  61
-```
-
-Peak ~391/year in 2003, decaying to 34 in the final year. The archive did not fail; **its
-users left for arXiv**, and it closed with dignity.
-
-**Access:** no OAI-PMH, no REST API, no DOIs. Retrieval is by predictable static path —
-`mp_arc/index-YY.html` for indices, `mp_arc/c/YY/YY-N.{pdf,ps.gz}` for full text — which is
-about as scrape-friendly as an archive gets. **Preservation: [NOT-VERIFIED]** — I found no
-statement of a dark archive or successor custodian, and "indefinitely" is a promise from a
-university department, not a contract with Portico or CLOCKSS.
-
-## 13. Frenxiv
-
-- `osf.io/preprints/frenxiv` · COS · **2018–2022, CLOSED** · **128 preprints retained** [API]
-- `frenxiv.org` · **ZOMBIE — HTTP 200, frozen at October 2020**
-
-The French multidisciplinary server, founded by Khaled Moustafa. Closed on OSF with the
-standard notice: *"Frenxiv is no longer able to accept new submissions. Existing content in
-this repository will remain accessible as part of COS's ongoing commitment to Open
-Science."* (S2) [DOC].
-
-**The interesting artefact is the second, non-OSF instance.** `frenxiv.org` returns HTTP 200
-with a 44,186-byte page titled *"Frenxiv Papers"*, with working navigation, a subject
-browse, and a steering committee listing Björn Brembs, Sophien Kamoun, Mario Pagliaro and
-others. It looks alive. It is not:
-
-- It displays a stuck banner reading *"Notice: The site will undergo maintenance between
-  **Oct 28, 2020** 9:19 AM and Oct 28, 2020 9:19 AM (+0000 UTC). Thank you for your
-  patience."* — a zero-length maintenance window from six years ago, still rendering [WEB].
-- The footer reads *"Copyright © **2011-2020**"* [WEB].
-
-**This is the most deceptive failure state observed in this survey**: a fully-rendering,
-professional-looking repository front end that has been frozen for six years and gives a
-casual reader no reason to doubt it. A dead site that refuses connections (MarXiv) is
-*safer* than one that renders. **Check the copyright year and the newest item date before
-trusting any small repository's front page.**
-
-## 14. WikiJournal Preprints
-
-- `en.wikiversity.org/wiki/WikiJournal_Preprints` · **WikiJournal User Group** · 2017 (S3) ·
-  **ALIVE** · **421 pages** under the `WikiJournal Preprints/` prefix [API]
-
-The structurally strangest entry in this directory: preprints as **MediaWiki pages** on
-English Wikiversity, not as PDFs in a repository. Each submission is a wiki page under
-`WikiJournal Preprints/<Title>`, edited, versioned and discussed with the same machinery as
-a Wikipedia article, then routed through public peer review into one of the WikiJournals
-(*Medicine*, *Science*, *Humanities*, *PPB*).
-
-The self-description on 2026-09-02: *"WikiJournal is an emerging publishing house
-specialized in running **open-access, free-to-publish, Wikipedia-integrated** academic
-journals"*, with the banner *"Open access • Publication charge free • Public peer review"*
-(S8) [WEB].
-
-**The Wikipedia-integration angle is the point.** The model is that a reviewed WikiJournal
-article can be merged back into the corresponding Wikipedia article — an attempt to make
-peer-reviewed scholarship and the encyclopedia the same artefact. Whatever one thinks of it,
-it inverts the usual relationship, in which Wikipedia cites the literature and the
-literature ignores Wikipedia.
-
-**Count method:** `https://en.wikiversity.org/w/api.php?action=query&list=allpages&
-apprefix=WikiJournal_Preprints/&aplimit=500&format=json` returned **421 pages** with no
-continuation token (S8) [API]. This counts *pages*, including drafts and a
-`preload draft` template — treat it as an upper bound on genuine submissions.
-
-**Durability profile — quietly excellent.** WikiJournal Preprints inherits **Wikimedia
-Foundation** hosting, full public revision history for every item, the MediaWiki API, and
-Wikimedia's public database dumps. Of everything in this file, only mp_arc and the
-CDL-hosted servers have a comparably credible answer to "will this be readable in 2040". A
-wiki page is not a PDF and has no DOI, but it is versioned, mirrored and dumped.
-
-**Computing content: negligible** in practice, though the corpus is genuinely
-multidisciplinary (the 421 pages include mathematics, physics and phonology titles).
-
-## 15. Adjacent servers covered elsewhere
-
-- **Optimization Online** — mathematical optimisation, founded 2000, operated by the
-  Mathematical Optimization Society. Formally a mathematics server, so it might have landed
-  in this file, but it is **computationally relevant** — solver design, integer-programming
-  algorithms, convex-optimisation methods that underpin practical scheduling, routing,
-  compiler and ML-training work — and it therefore has its own full record:
-  **[optimization-online.md](optimization-online.md)**. Wikipedia's bucket is `>10,000`
-  since 2000 (S3); it was reachable at HTTP 200 / 98,725 bytes in the 2026-09-01 sweep (S9)
-  [WEB].
-- **ESS Open Archive's platform** — see **[authorea.md](authorea.md)**.
-- **hprints**, the Nordic humanities server on HAL infrastructure, is in
-  **[social-sciences-and-humanities.md](social-sciences-and-humanities.md)**; the platform is
-  in **[hal.md](hal.md)**.
-- **Closed servers** listed here in brief — MarXiv, NutriXiv, Frenxiv, mp_arc — are also
-  entered in the cross-cutting
-  **[closed-and-defunct-servers.md](closed-and-defunct-servers.md)**.
-
-## 16. Access, APIs and bulk retrieval — summary
-
-| Server | Machine interface | Works from scripts? |
-|---|---|---|
-| OSF-hosted (PaleorXiv, MarXiv, NutriXiv, FocUS, Frenxiv, legacy EarthArXiv/EcoEvoRxiv/SportRxiv) | `api.osf.io/v2/` JSON:API | **Yes**, no key. URL-encode `filter%5Bprovider%5D=` |
-| EarthArXiv, EcoEvoRxiv | **OAI-PMH** at `/api/oai` (Janeway 1.8.0) | **Yes**, plain `curl` |
-| SportRxiv | **OAI-PMH** at `/index.php/server/oai` (OPS 3.3.0.22), gives `completeListSize` | **Yes**, plain `curl` |
-| ESS Open Archive | none reachable — site 403s on all five UAs | **No.** Use **Crossref** (`prefix:10.22541`, `prefix:10.1002`) |
-| mp_arc | none — but fully predictable static paths | **Yes**, trivially |
-| WikiJournal Preprints | **MediaWiki API** `en.wikiversity.org/w/api.php` + Wikimedia dumps | **Yes**, excellent |
-| Eyexiv | — | **No** — does not resolve |
-
-**Negative controls used:** `osf.io/preprints/eyexiv/` → HTTP 200 / 4,207 B for a
-non-existent provider; `filter[provider]=bogusprovider12345` → `total: 0`;
-`mp_arc-bin/mpa?yn=99-99999` → HTTP 200 / 174 B "Found no abstract";
-`mp_arc/index-77.html` → HTTP 404.
-
-## 17. Sources
-
-- **S1** — OSF preprint-provider list.
-  `https://api.osf.io/v2/preprint_providers/?page[size]=100` · retrieved 2026-09-02 · 32
-  providers; establishes that `eyexiv` is not among them. [API]
-- **S2** — OSF counts and provider records.
-  `https://api.osf.io/v2/preprints/?filter[provider]=<slug>&page[size]=1` (`links.meta.total`)
-  and `https://api.osf.io/v2/preprint_providers/<slug>/` · retrieved 2026-09-02 · every OSF
-  count, and the verbatim closure/migration notices for MarXiv, NutriXiv, Frenxiv,
-  SportRxiv, EarthArXiv, EcoEvoRxiv, plus the FocUS Archive description, policy-PDF URL and
-  advisory board. [API] [DOC]
-- **S3** — Wikipedia, *List of preprint repositories*.
-  `https://en.wikipedia.org/wiki/List_of_preprint_repositories` · retrieved 2026-09-02 ·
-  launch years, operators, size buckets. Used only where no first-party source existed, and
-  always flagged. [COM]
-- **S4** — EarthArXiv OAI-PMH. `https://eartharxiv.org/api/oai?verb=Identify` · retrieved
-  2026-09-02 · Janeway 1.8.0, `no-reply@escholarship.org`, earliestDatestamp 2017-10-23.
-  Live counts from `https://eartharxiv.org/repository/search/` and
-  `https://ecoevorxiv.org/repository/search/` ("There are N Preprints listed"). [API] [WEB]
-- **S5** — Crossref REST API. `https://api.crossref.org/prefixes/<prefix>`,
-  `/prefixes/<prefix>/works?rows=0`, `/works?filter=prefix:…,type:posted-content&sample=100`,
-  and `/works/10.1002/essoar.10500599.1` · retrieved 2026-09-02 · prefix ownership
-  (10.31223 & 10.32942 → California Digital Library; 10.22541 → Authorea, Inc.; 10.51224 →
-  STORK), prefix totals, and the ESSOAr namespace sampling. [API]
-- **S6** — SportRxiv. `https://sportrxiv.org/` (generator: Open Preprint Systems 3.3.0.22;
-  DOIs and same-day 2026-09-01 postings) and
-  `https://sportrxiv.org/index.php/server/oai?verb=Identify` /
-  `?verb=ListIdentifiers&metadataPrefix=oai_dc` (`completeListSize="761"`,
-  earliestDatestamp 2021-08-12, adminEmail `layan.fessler@storkinesiology.org`) · retrieved
-  2026-09-02. [WEB] [API]
-- **S7** — mp_arc. `https://web.ma.utexas.edu/mp_arc/` (the 1991–2023 statement, verbatim),
-  `index-91.html` … `index-23.html` (per-year counts summing to 6,152),
-  `mp_arc-bin/mpa?yn=91-1` and `?yn=23-1`, `mp_arc/c/91/91-1.ps.gz` (gzip mtime 1997-04-26),
-  `mp_arc/c/23/23-1.pdf` (valid 6-page PDF), plus the two negative controls · all retrieved
-  2026-09-02. [WEB] [DOC] [API]
-- **S8** — WikiJournal Preprints.
-  `https://en.wikiversity.org/wiki/WikiJournal_Preprints` (self-description, banner) and
-  `https://en.wikiversity.org/w/api.php?action=query&list=allpages&apprefix=WikiJournal_Preprints/&aplimit=500&format=json`
-  (421 pages, no continuation) · retrieved 2026-09-02. [WEB] [API]
-- **S9** — Directory-wide reachability sweep.
-  `doc/hardware/scratch/preprint-repositories/reachability-2026-09-01.txt` (run 2026-09-01)
-  and the per-URL UA-ladder log in
-  `doc/hardware/scratch/preprint-repositories/humanities/` (run 2026-09-02) · supports the
-  403/NXDOMAIN/connection-refused claims for `essopenarchive.org`, `www.authorea.com`,
-  `marxiv.org`, `nutrixiv.org`, `eyexiv.*` and `frenxiv.org`. [WEB]
diff --git a/research/preprint-repositories/open-access-full-text-sources.md b/research/preprint-repositories/open-access-full-text-sources.md
deleted file mode 100644
index 65132b0..0000000
--- a/research/preprint-repositories/open-access-full-text-sources.md
+++ /dev/null
@@ -1,1009 +0,0 @@
-# Open-access full text after the preprint — where the published paper is legally free
-
-- **Compiled:** 2026-09-02. Every figure below was measured on that date unless stated otherwise.
-- **The question:** *I have a citation. I want the published paper as a PDF, legally, without
-  paying.* The rest of this directory is about **preprints** — the author's copy, before or
-  alongside peer review. This record is about the other half of the problem: **where the version
-  of record, or a legitimate copy of it, is openly available**, and the exact order in which to
-  look.
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-- **Companion records:** [`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md)
-  (grey literature, which this file deliberately excludes), [`techrxiv.md`](techrxiv.md) (the IEEE
-  route), [`cryptology-eprint-archive.md`](cryptology-eprint-archive.md) (the IACR route),
-  [`arxiv.md`](arxiv.md), [`hal.md`](hal.md).
-
-> **Scope note, stated up front.** Nothing in this record involves Sci-Hub, Library Genesis, or any
-> other infringing source. Every route documented here is either (a) the publisher giving the paper
-> away, (b) an author exercising a self-archiving right the publisher granted, or (c) a public
-> funder mandating deposit. Where a route is legally grey — ResearchGate is the obvious case —
-> that is said plainly in §5.
-
----
-
-## 1. The decision ladder
-
-Run these in order. Each rung is cheap; the expensive rungs are at the bottom. In practice
-**rungs 1–3 resolve the large majority of computing and electronics citations**, and rung 4 —
-"is this a USENIX paper?" — resolves a large part of what rungs 1–3 miss.
-
-| # | Rung | Cost | What it catches |
-|---|---|---|---|
-| **1** | **Unpaywall** on the DOI (§2.1) | one HTTP call | Anything with a DOI-linked OA copy anywhere |
-| **2** | **Semantic Scholar** `externalIds.ArXiv` (§2.3) | one HTTP call | **The arXiv copy Unpaywall misses.** See the trap in §2.1 |
-| **3** | **OpenAlex** `locations[]` (§2.2) | one HTTP call | Repository copies, and the venue's own OA status |
-| **4** | **Is the venue free by policy?** (§3) | zero, if you know | USENIX (all of it), IACR, PMC, DOAJ journals |
-| **5** | **CORE / BASE / OpenAIRE** full-text search (§2.4–2.6) | one call each | Institutional-repository copies with no DOI link |
-| **6** | **dblp** → conference/journal page → publisher (§2.8) | two calls | Half-remembered CS citations; canonical bibliographic form |
-| **7** | **Author's page / institutional repository** (§4) | manual | Everything above missed, especially pre-2000 work |
-| **8** | **Grey literature** — is it a tech report, not a paper? | manual | RISC-V, Xerox PARC, DEC SRC — see the [companion record](government-and-institutional-technical-reports.md) |
-| **9** | **Email the author** | slow | Genuinely the last legal rung, and it works |
-
-**The single most common mistake** is stopping at rung 1. §2.1 documents a measured case where
-Unpaywall *and* OpenAlex both return `closed` for a paper whose full text has been on arXiv since
-2017.
-
----
-
-## 2. Discovery and resolver layer
-
-### 2.1 Unpaywall — the first call you should make
-
-- **URL:** https://unpaywall.org/ · **API:** `https://api.unpaywall.org/v2/<doi>?email=<you>`
-- **Operator:** OurResearch (formerly Impactstory), a US 501(c)(3).
-
-Unpaywall answers exactly one question — *for this DOI, is there a legal free copy, and where?* —
-and it answers it in one unauthenticated HTTP call. It is the backbone under a large amount of
-other infrastructure: OpenAlex's OA fields are Unpaywall's (§2.2), and browser extensions and
-library link resolvers consume the same endpoint.
-
-**Corpus size: [NOT-VERIFIED].** `unpaywall.org` serves a **1,421-byte SPA shell for every path
-tried** — `/`, `/products/api`, `/products/data-feed`, `/faq` all returned HTTP 200 with exactly
-1,421 bytes (S1). This is the same failure mode as the `osf.io` trap recorded in
-[README §4](README.md#6-probing-traps): status code *and* byte size are both uninformative. No
-claimed corpus figure could be read from the operator's own site. What *can* be measured is the
-data snapshot (below) and the OA totals in OpenAlex (§2.2), which are derived from Unpaywall.
-
-**The `oa_status` colour taxonomy.** This is the vocabulary the whole field uses, and the
-distinctions are load-bearing:
-
-| Value | Means | Durability |
-|---|---|---|
-| `gold` | Published in a fully-OA journal. The version of record is free at the publisher | High — the journal's business model depends on it |
-| `hybrid` | A subscription journal, but this article was made OA (usually by an APC) | High |
-| `bronze` | **Free to read at the publisher, but with no open licence.** A promotional or discretionary decision | **Low — this can be revoked at any time** |
-| `green` | Free copy in a repository (arXiv, PMC, an institutional repo), not at the publisher | Medium–high; depends on the repository |
-| `closed` | No free copy known to Unpaywall | — |
-
-**`bronze` is the one to be suspicious of.** It means the publisher is currently choosing to let
-you read it and has granted no licence to redistribute or mine it. If a `bronze` link matters to
-your work, save a copy.
-
-**`best_oa_location`** is Unpaywall's own pick among `oa_locations[]`. It prefers the
-`publishedVersion` at the publisher over an `acceptedVersion` in a repository. The fields that
-matter on it are `url_for_pdf` (direct PDF, may be null), `url_for_landing_page`, `version`
-(`publishedVersion` / `acceptedVersion` / `submittedVersion`), `host_type`
-(`publisher` / `repository`), and `license`.
-
-#### Worked examples [API], all retrieved 2026-09-02 (S2)
-
-```bash
-curl -s "https://api.unpaywall.org/v2/10.1109/SP.2019.00002?email=you@your.org" | jq '{
-  title, oa_status, is_oa,
-  best: .best_oa_location | {host_type, version, url_for_pdf},
-  n: (.oa_locations | length) }'
-```
-
-| DOI | Paper | `oa_status` | `best_oa_location` | n locations |
-|---|---|---|---|---|
-| `10.1038/nature12373` | (control, a Nature article) | *see note* | publisher, `publishedVersion`, `nature.com/articles/nature12373.pdf` | — |
-| `10.1109/SP.2019.00002` | **Spectre Attacks** | **gold** | `publishedVersion`, `ieeexplore.ieee.org/ielx7/8826229/8835208/08835233.pdf` | 4 |
-| `10.1145/2517349.2522738` | **Naiad** | **gold** | `publishedVersion`, `dl.acm.org/ft_gateway.cfm?id=2522738&type=pdf` | 1 |
-| `10.1109/ISCA.2014.6853210` | **RowHammer** (Kim et al. 2014) | **closed** | `null` | 0 |
-| `10.1109/JPROC.2017.2761740` | Sze et al., *Efficient Processing of DNNs* | **closed** | `null` | 0 |
-| `10.1145/3079856.3080246` | **In-Datacenter Performance Analysis of a TPU** | **closed** | `null` | 0 |
-
-#### The trap that matters most in this whole file
-
-The last two rows are **wrong in practice**. Both papers have been openly readable on arXiv for
-years — [`1703.09039`](https://arxiv.org/abs/1703.09039) and
-[`1704.04760`](https://arxiv.org/abs/1704.04760), both verified in
-[`arxiv.md` §7.5](arxiv.md). Unpaywall reports `closed`, `oa_locations: []`, for both.
-
-The reason is structural, not a bug: **Unpaywall is a DOI-keyed index.** If the arXiv record does
-not carry the publisher DOI, and the publisher's Crossref record does not carry a relation to the
-arXiv ID, there is no edge for Unpaywall to follow. Most authors never add the DOI to their arXiv
-metadata after acceptance.
-
-**Consequence for the ladder: a `closed` from Unpaywall is not an answer, it is a prompt to check
-arXiv.** Rung 2 exists entirely because of this. Measured cross-check on the TPU paper, same day
-(S3, S4):
-
-| Service | Verdict |
-|---|---|
-| Unpaywall | `oa_status: closed`, 0 locations |
-| OpenAlex | `open_access.is_oa: false`, `oa_status: closed`, `best_oa_location: null`, `any_repository_has_fulltext: false` |
-| **Semantic Scholar** | `externalIds.ArXiv: "1704.04760"` — **the answer, sitting in a metadata field** |
-
-Note also that Semantic Scholar contradicts *itself* on this record: `isOpenAccess: true` while
-`openAccessPdf.status: "CLOSED"` and `openAccessPdf.url` points at an ACM gateway. Do not trust
-`isOpenAccess`; read `externalIds`.
-
-#### Access, limits and negative controls (S1, S2)
-
-- **The `email` parameter is mandatory and is filtered.** No email → HTTP **422**, 142-byte JSON,
-  `"Email address required in API call"`. Using the obvious shared placeholder
-  `research@example.com` → HTTP **422**, 154 bytes, `"Please use your own email address in API
-  calls."` A distinct address on the same domain worked. **Use a real address you control.**
-- **Negative control:** `10.1109/ZZZZ.9999.9999999` → HTTP **404** with a 207-byte Flask HTML
-  body. Unpaywall's status codes are trustworthy, unlike several hosts in
-  [`retrieval-notes.md`](retrieval-notes.md).
-- **No published numeric rate limit was found** (the FAQ is inside the unreadable SPA).
-  **[NOT-VERIFIED]** — treat 100k/day as folklore, not fact, and throttle.
-
-#### Bulk data
-
-The full snapshot bucket is **listable anonymously** [API] (S5):
-
-```bash
-curl -s "https://unpaywall-data-snapshots.s3.us-west-2.amazonaws.com/?list-type=2" | less
-```
-
-| Snapshot | Size (gzipped JSONL) |
-|---|---|
-| `unpaywall_snapshot_2018-03-29T113154.jsonl.gz` (oldest) | 16,291,678,484 B (≈16.3 GB) |
-| `unpaywall_snapshot_2022-03-09T083001.jsonl.gz` | 29,470,830,470 B (≈29.5 GB) |
-| **`unpaywall_snapshot_2024-11-27T031702.jsonl.gz` (newest in the bucket)** | **39,234,162,157 B (≈39.2 GB)** |
-
-**Flag:** the newest public snapshot in that bucket is dated **2024-11-27**, i.e. ~21 months stale
-as of this record's compile date. The live API is current; the free bulk drop is not. Current bulk
-data moved to a paid "Data Feed" product [INF, from the product URL existing]. If you need
-up-to-date OA status in bulk, use **OpenAlex's snapshot** (§2.2), which is free and current.
-
-### 2.2 OpenAlex — the graph around the paper
-
-- **URL:** https://openalex.org/ · **API:** `https://api.openalex.org` · **Operator:** OurResearch
-  (the same non-profit as Unpaywall).
-- **Lineage:** the declared successor to **Microsoft Academic Graph**, which Microsoft shut down at
-  the end of 2021. The MAG identifiers survive inside OpenAlex and Semantic Scholar records — the
-  TPU paper above still carries `MAG: 2953212265` in S2 (S4).
-
-**Measured size, 2026-09-02** [API] (S6):
-
-| Entity | Count |
-|---|---|
-| `works` | **321,988,823** |
-| `authors` | 126,403,013 |
-| `sources` (journals, conference series, repositories) | 256,025 |
-| `institutions` | 136,136 |
-| `publishers` | 10,708 |
-
-**OA breakdown of all 321,988,823 works** — `GET /works?group_by=open_access.oa_status` (S7).
-The buckets sum **exactly** to the total, so nothing is double-counted:
-
-| `oa_status` | Works | Share |
-|---|---|---|
-| closed | 199,957,917 | 62.1% |
-| **green** | **66,803,663** | **20.7%** |
-| diamond | 17,714,822 | 5.5% |
-| gold | 15,248,052 | 4.7% |
-| bronze | 13,156,096 | 4.1% |
-| hybrid | 9,108,273 | 2.8% |
-| **Total OA** | **122,030,906** | **37.9%** [INF, summed] |
-
-Two things worth noticing. First, **OpenAlex has added a `diamond` bucket that Unpaywall's classic
-five-colour taxonomy does not have** — gold-without-an-APC, split out of `gold`. If you are
-comparing an OpenAlex figure to a pre-2023 Unpaywall figure, they are not the same denominators.
-Second, **`green` is by far the largest OA category**: repository self-archiving, not publisher
-generosity, is what makes most of the literature readable.
-
-**Fields to read on a work:**
-
-- `open_access` → `{is_oa, oa_status, oa_url, any_repository_has_fulltext}`. The last flag is the
-  useful one for rung 3 — it tells you a repository copy exists even when `best_oa_location` is a
-  publisher.
-- `best_oa_location` → same shape as Unpaywall's, plus a nested `source` object naming the host.
-- **`locations[]`** → *every* known copy, each with `version`, `pdf_url`, `license`, `source`.
-  This is the field to iterate when you are hunting; `best_oa_location` is the field to read when
-  you just want one link.
-
-**Rate limits — these changed, and the change is not folklore.** OpenAlex now returns credit- and
-cost-denominated headers [API] (S8):
-
-```
-x-ratelimit-limit: 1000          x-ratelimit-limit-usd: 0.1
-x-ratelimit-remaining: 742       x-ratelimit-remaining-usd: 0.0742
-x-ratelimit-cost-usd: 0.0001     x-ratelimit-credits-used: 1
-x-ratelimit-reset: 63043
-```
-
-and the JSON body carries `meta.cost_usd: 0.0001` per call. Anonymous access is metered at
-**1,000 credits / $0.10 per reset window** (reset counter observed at 63,043 s ≈ 17.5 h).
-A `db_response_time_ms` is also returned. **Read these headers in your harvester** — a scraper
-written against the old "polite pool, 100k/day, add your email" documentation will silently start
-failing.
-
-**Bulk snapshot** — free, anonymous, and current [API] (S9):
-
-```bash
-curl -s "https://openalex.s3.amazonaws.com/?list-type=2&delimiter=/"
-# → LICENSE.txt, README.txt, RELEASE_NOTES.txt, browse.html
-#   data/ , legacy-data/
-curl -s "https://openalex.s3.amazonaws.com/?list-type=2&delimiter=/&prefix=data/"
-# → data/jsonl/ , data/parquet/
-```
-
-The **parquet** layout is new relative to the widely-cited jsonl-only descriptions; both are
-present. Note the `legacy-data/` prefix — an older layout is retained, so scripts written against
-the old paths will still work but will get stale data. `data/works/` — the path many older
-tutorials use — returned `KeyCount 0`.
-
-### 2.3 Semantic Scholar and S2ORC
-
-- **API:** `https://api.semanticscholar.org/graph/v1` · **Operator:** Allen Institute for AI (AI2).
-
-Semantic Scholar earns its place at **rung 2** for one reason: `externalIds`. A single call gives
-you the DOI, the arXiv ID, the DBLP key, the legacy MAG ID, the PubMed IDs and the S2 CorpusId —
-which means one call converts *any* identifier you happen to have into all the others. Measured
-example (S4):
-
-```bash
-curl -s "https://api.semanticscholar.org/graph/v1/paper/DOI:10.1145/3079856.3080246\
-?fields=title,isOpenAccess,openAccessPdf,externalIds"
-```
-```json
-{"paperId":"2dfeb5a90abc49ab2a80a492a01a4e2c8e92ec22",
- "externalIds":{"DBLP":"conf/isca/JouppiYPPABBBBB17","MAG":"2953212265",
-                "ArXiv":"1704.04760","DOI":"10.1145/3079856.3080246","CorpusId":4202768},
- "title":"In-datacenter performance analysis of a tensor processing unit",
- "isOpenAccess":true,
- "openAccessPdf":{"url":"http://dl.acm.org/ft_gateway.cfm?id=3080246&type=pdf","status":"CLOSED","license":null}}
-```
-
-`openAccessPdf` gives `{url, status, license}` where `status` reuses the Unpaywall colour
-vocabulary. **As shown, `isOpenAccess` and `openAccessPdf.status` can disagree inside one record.**
-Prefer `openAccessPdf.status` and, above all, `externalIds.ArXiv`.
-
-- **Auth:** the `graph/v1` endpoint answered unauthenticated. Bogus DOI → HTTP **404** (clean).
-- **Rate limits without a key are real but unpublished in the response headers**
-  **[NOT-VERIFIED]**; AI2 issues free API keys on application.
-
-**S2ORC — the full-text corpus.** Semantic Scholar's differentiator is that it parses open-access
-PDFs into structured full text. The bulk datasets API is public even though the downloads are not
-(S10, release `2026-08-25`):
-
-```bash
-curl -s https://api.semanticscholar.org/datasets/v1/release/latest   # public, no key
-curl -s https://api.semanticscholar.org/datasets/v1/release/latest/dataset/s2orc
-# → 401 {"error":"A valid API key is required"}      (40 bytes)
-```
-
-Datasets in release `2026-08-25`: `abstracts`, `authors`, `citations`,
-`embeddings-specter_v1`, `embeddings-specter_v2`, `paper-ids`, `papers`, `publication-venues`,
-`s2orc`, `s2orc_v2`, `tldrs`. Sizes from the operator's own descriptors [API]:
-
-| Dataset | Contents |
-|---|---|
-| `papers` | "The core attributes of a paper… **200M records in 30 1.5 GB files**" |
-| `s2orc` | "Full-body paper text parsed from open-access PDFs… **10M records in 30 4 GB files**" |
-| **`s2orc_v2`** | "…structural elements such as sentences and paragraphs, and bibliographic references. **16M records in 30 6 GB files**" |
-
-**How to get bulk access:** request a free API key from AI2 (the `/datasets/` endpoints return
-`401 {"error":"A valid API key is required"}` until you attach one as `x-api-key`). The
-*listing* is open; the *payload* is not.
-
-### 2.4 CORE — the largest aggregator of open-access full text
-
-- **URL:** https://core.ac.uk/ · **Operator:** The Open University (UK), community-governed,
-  not-for-profit.
-
-CORE is the one to reach for at rung 5, because it is the only service in this section that
-**harvests and stores the full text** at scale rather than linking to it. Its own home page, as
-served on 2026-09-02, states **"Search 452M papers from around the world"** and describes itself
-as "The world's largest collection of open access research papers" [WEB] (S11). That 452 M is a
-*paper* count across ~thousands of harvested repositories; it is not 452 M distinct full texts,
-and CORE does not, on that page, separate the two. Recorded as stated, with the caveat.
-
-**API.** `https://api.core.ac.uk/v3/search/works` — **requires a key**. An unauthenticated call
-returned HTTP **301** (776-byte body), not a 401, which is a mildly misleading signal (S12).
-Keys are free on registration.
-
-**Bulk dataset** [DOC] (S13) — CORE's differentiator, and genuinely large:
-
-| Release | Compressed | Extracted |
-|---|---|---|
-| **2024-07-12** (latest listed) | **749 GB** | ~2.7 TB |
-| 2023-03-18 | 393 GB | 3.5 TB |
-| 2022 | 393 GB | 3.5 TB |
-
-The 2024 release is split into per-batch archives indexed by a credentialed
-`dataset_index.xml`; access is by registration, and CORE's documentation explicitly recommends
-`aria2`/`wget -c` because of the size.
-
-Other CORE services worth knowing: **FastSync** (incremental sync rather than a full re-download),
-the **OAI Resolver** (maps OAI identifiers to records), and a **Recommender** widget.
-
-### 2.5 BASE — Bielefeld Academic Search Engine
-
-- **URL:** https://www.base-search.net/ · **Operator:** Bielefeld University Library.
-
-BASE is the other classic repository aggregator and is a major upstream source for Unpaywall.
-
-**Probe result, 2026-09-02: blocked.** `https://www.base-search.net/` returned HTTP 200 with a
-**7,846-byte Anubis proof-of-work challenge page**, `Anubis version v1.27.0+dirty`, footer "This
-website is hosted by Bielefeld University Library" [WEB] (S14). This is the *third* scholarly host
-in this survey behind Anubis — see [`retrieval-notes.md` §3](retrieval-notes.md), which records
-the same wall on `econstor.eu` and `hprints`. **The user-agent ladder in
-[`AGENTS.md`](../../AGENTS.md) does not defeat a JS proof-of-work.**
-
-**Size: [NOT-VERIFIED] on this date** — the counter is behind the wall. BASE's documented
-machine interface is an IP-whitelisted OAI-style API granted on written application, consistent
-with the general rule from `retrieval-notes.md`: *when the web front end is walled, look for the
-machine interface.*
-
-### 2.6 OpenAIRE Explore
-
-- **URL:** https://explore.openaire.eu/ (200, 66,171 B) · **API:** `https://api.openaire.eu`
-- **Operator:** the OpenAIRE AMKE, EU-funded; the research-output layer of the European Open
-  Science Cloud.
-
-**Measured size, 2026-09-02** [API] (S15):
-
-```bash
-curl -s "https://api.openaire.eu/search/publications?size=0"
-# <total>238449827</total>
-```
-
-**238,449,827 publications** for the query `(oaftype exact result) and (resulttypeid exact
-publication)`. JSON is available with `&format=json`. Note that `https://v3.openaire.eu/api/...`
-— the endpoint some documentation points at — **timed out entirely** (`http=000`) on the probe
-date; the `api.openaire.eu` host is the one that answers.
-
-OpenAIRE's distinctive value is **funder linkage**: it connects publications to EU grant numbers,
-so it answers "what came out of this project" in a way that Unpaywall and CORE cannot.
-
-### 2.7 DOAJ — Directory of Open Access Journals
-
-- **URL:** https://doaj.org/ · **API:** `https://doaj.org/api/search/{journals,articles}/<q>`
-
-DOAJ operates one level up: it curates **journals**, not articles, against a published set of
-criteria. It is the answer to *"is this journal actually open access, or is it a predatory
-lookalike?"* — inclusion is a positive quality signal, and DOAJ removes titles that stop meeting
-its criteria.
-
-**Measured, 2026-09-02** [API] (S16):
-
-```bash
-curl -s "https://doaj.org/api/search/journals/*?pageSize=1" | jq .total   # 23384
-curl -s "https://doaj.org/api/search/articles/*?pageSize=1" | jq .total   # 13535801
-```
-
-| | Count |
-|---|---|
-| Journals indexed | **23,384** |
-| Article records indexed | **13,535,801** |
-
-The API answered unauthenticated with no fallback UA needed. Practical use: before citing a
-journal you have not heard of, look it up in DOAJ. Absence is not proof of anything, but presence
-means a human checked the licence, the peer-review statement and the editorial board.
-
-Cross-reference: [`preprints-org.md`](preprints-org.md) documents why "is it in DOAJ" is a weaker
-test than it looks when one publisher operates both the preprint server and the journals.
-
-### 2.8 dblp — the canonical CS bibliography
-
-- **URL:** https://dblp.org/ · **Operator:** Schloss Dagstuhl – Leibniz-Zentrum für Informatik.
-
-**dblp hosts no full text at all.** It is in this file anyway, because it solves the *other* half
-of the problem: **it is where you resolve a half-remembered CS citation into a canonical one.**
-"That Jouppi TPU paper, ISCA, around 2017" is not a query Unpaywall can answer — it needs a DOI.
-dblp will take the fragment and give you the exact title, the full author list, the venue, the
-year, the DOI and the arXiv ID, and *then* rungs 1–3 become possible.
-
-dblp's discipline is its real product: author-name disambiguation, one record per publication with
-its journal/conference versions linked, and stable `conf/isca/JouppiYPPABBBBB17`-style keys —
-which, as §2.3 showed, Semantic Scholar carries in `externalIds.DBLP`.
-
-**API** [API] (S17), no key, no UA fallback needed:
-
-```bash
-curl -s "https://dblp.org/search/publ/api?q=RISC-V&format=json&h=1" | jq '.result.hits."@total"'
-# 2313
-curl -s "https://dblp.org/search/publ/api?q=<title words>&format=json&h=10"   # publications
-curl -s "https://dblp.org/search/author/api?q=<name>&format=json"             # authors
-curl -s "https://dblp.org/search/venue/api?q=<venue>&format=json"             # venues
-```
-
-`RISC-V` returns **2,313** publication hits — worth comparing with the 250 `ti:"RISC-V" AND
-cat:cs.AR` arXiv hits recorded in [`arxiv.md` §7.5](arxiv.md). dblp indexes the *published*
-literature; arXiv indexes what authors posted.
-
-**Bulk XML dump** [API] (S18):
-
-```
-https://dblp.org/xml/dblp.xml.gz
-  HTTP/2 200 · content-length: 1,099,942,370 (≈1.10 GB gzipped)
-  last-modified: Tue, 01 Sep 2026 23:47:15 GMT
-```
-
-Rebuilt daily — the dump measured here was **less than 24 hours old**. The accompanying
-`dblp.dtd` must be fetched alongside it or the XML will not parse. The dump is released under
-**CC0**, which makes dblp the least legally encumbered bibliographic dataset in this file.
-
----
-
-## 3. Publisher-side venues that are genuinely free
-
-### 3.1 USENIX — the single most important entry in this file
-
-- **URL:** https://www.usenix.org/
-
-**Every paper in every USENIX proceedings is free to download, with no registration, no
-membership and no paywall.** This covers **OSDI, NSDI, ATC (USENIX Annual Technical Conference),
-FAST, USENIX Security, SOUPS, HotOS, LISA, OSDI/EuroSys-adjacent workshops** and the rest of the
-USENIX programme.
-
-**Why this is the headline.** A sibling record in this directory established that the canonical
-systems literature is largely **absent from preprint servers** —
-[`arxiv.md`](arxiv.md) and [`landmark-papers.md`](landmark-papers.md) both record that the
-foundational OSDI/NSDI/FAST-line papers were never posted to arXiv. If you have been looking for
-those papers on a preprint server, you have been looking in the wrong place for a decade.
-**USENIX is where they actually are, and they have been free the entire time.**
-
-**The policy, in USENIX's own words** [DOC], retrieved 2026-09-02 from `usenix.org/about` and
-`usenix.org/conferences/open-access` (S19, S20):
-
-> "We banished paywalls in **2008** for both conference authors and readers, providing conference
-> proceedings and recordings free of charge under our open access policy."
-
-> "USENIX compiles and publishes accepted research papers as proceedings for each of these
-> conferences, making them freely available on [our website]."
-
-USENIX also states it relies on **sponsor support** to fund this, and notes that "recorded
-presentations of our events are publicly available after each event" — so the *talks* are free
-too, which is unusual and frequently more useful than the paper for a systems result.
-
-**Verified retrieval** [WEB] (S21), 2026-09-02, plain Chrome-131 UA, no auth:
-
-| URL | Result |
-|---|---|
-| `https://www.usenix.org/conference/osdi24/technical-sessions` | HTTP 200, 259,550 B |
-| `https://www.usenix.org/system/files/osdi24_full_proceedings.pdf` | **HTTP 200, 83,779,378 B, magic `%PDF-`** |
-| `https://www.usenix.org/system/files/osdi24_proceedings_interior.pdf` | HTTP 200, 82,578,353 B, `%PDF-` |
-| *negative control* `.../osdi24-nonexistent-author-xyz.pdf` | HTTP **404**, 16,889-byte themed body |
-
-The negative control matters: USENIX returns a **correct 404 status** but with a large themed HTML
-body, so a harvester must check the status code or the magic bytes, not the content length.
-
-**Practical shortcuts.**
-
-- Every conference has a `/conference/<venue><yy>/technical-sessions` page listing every paper
-  with a direct PDF link, a BibTeX entry, the slides and usually the video.
-- The whole proceedings ship as one PDF (`<venue><yy>_full_proceedings.pdf`) — 84 MB for OSDI '24.
-  Grab it once rather than 60 individual files.
-- Papers also appear in ACM DL and IEEE Xplore for some co-sponsored events. **Always take the
-  USENIX copy** — same content, no paywall, no login.
-
-**Caveat, stated honestly:** URLs under `/system/files/` and `/sites/default/files/` are Drupal
-paths and are not obviously permanent identifiers. Conference landing pages have been stable for
-many years [INF], but the file paths carry no DOI. If a USENIX paper is load-bearing for your
-work, keep a local copy.
-
-### 3.2 ACM Digital Library
-
-More complicated than USENIX, and the honest summary is **"partly, and it depends".**
-
-- **ACM OPEN** is ACM's transformative read-and-publish agreement. From ACM's own library-facing
-  page, retrieved 2026-09-02 [DOC] (S22): *"ACM OPEN is our transformative read and publish model,
-  offering participating institutions unlimited open access publishing in the Digital Library and
-  unlimited read access to its full text contents."* The mechanism is **institutional**: if the
-  corresponding author's institution is an ACM OPEN participant, that paper is published OA in the
-  DL at no cost to the author. If not, it is not. ACM maintains a public **Participant List** and a
-  **FAQ** off `libraries.acm.org/acmopen`.
-- **Consequence you can act on:** whether an ACM paper is free depends on *who wrote it*, not on
-  which conference it appeared at. Two papers in the same SIGCOMM proceedings can differ. This is
-  why Naiad (SOSP '13) resolves `gold` with a working `dl.acm.org/ft_gateway.cfm` PDF (§2.1) while
-  the TPU paper (ISCA '17, ACM-published) resolves `closed`.
-- **OpenTOC** is the older mechanism: ACM grants a SIG the right to host a free table of contents
-  with working full-text links for a conference, usually for a limited period around the event.
-  **Probe result:** `https://dl.acm.org/opentoc` returned HTTP **403 with a 5,635-byte body** —
-  the Cloudflare challenge fingerprint documented in
-  [`retrieval-notes.md` §1](retrieval-notes.md). Blocked, not broken; the current per-conference
-  OpenTOC list is **[NOT-VERIFIED]** (S23).
-- **Author-izer** was ACM's older per-author free-link generator, embedded on author home pages.
-  Links minted through it still circulate. **[NOT-VERIFIED]** whether new links can still be
-  created.
-- `www.acm.org/publications/openaccess` and `libraries.acm.org/acmopen` both served HTTP 200
-  (76,905 B and 43,294 B) to the Chrome-131 UA; `libraries.acm.org/acmopen/faq` returned **404**
-  (S22, S24) — ACM had recently relaunched that site and invites feedback on broken paths in the
-  page footer.
-
-**Practical rule for ACM:** check Unpaywall first (`gold` on an ACM DOI usually means a working
-`ft_gateway.cfm` link); if `closed`, check arXiv via Semantic Scholar; if still nothing, check
-whether the same paper appeared at a USENIX venue or as an institutional tech report.
-
-### 3.3 IEEE
-
-**Mostly paywalled, and there is no way to soften that.** Xplore is a subscription product. Three
-legitimate routes:
-
-1. **TechRxiv, via the Crossref `is-preprint-of` relation.** This is the highest-yield route for
-   IEEE-bound work and it is documented in detail in the sibling record
-   **[`techrxiv.md`](techrxiv.md)** — including the fact that `www.techrxiv.org` is behind a
-   Cloudflare challenge (403, 5,620 B) so the *Crossref* API, not the site, is how you query it.
-   IEEE sanctions posting to TechRxiv, so the copy is legitimate.
-2. **IEEE's own OA journals** — *IEEE Access* is the large one (fully gold OA, APC-funded), plus a
-   growing set of topical OA titles and hybrid OA articles in the classic transactions. When an
-   IEEE article *is* OA, Unpaywall picks it up cleanly: Spectre (`10.1109/SP.2019.00002`) resolved
-   `gold` with a direct `ieeexplore.ieee.org/ielx7/.../08835233.pdf` PDF (§2.1).
-3. **Author self-archiving.** IEEE permits authors to post the accepted version to their own
-   site, their institutional repository and arXiv/TechRxiv. This is why so much IEEE-published
-   work is reachable as `green` OA — recall that `green` is 66.8 M works, 20.7% of OpenAlex (§2.2).
-
-**IEEE *standards* are a separate and worse problem** — see the
-[companion record §5](government-and-institutional-technical-reports.md).
-
-### 3.4 IACR — diamond open access done properly
-
-The International Association for Cryptologic Research runs what is, for this survey's purposes,
-the cleanest publishing pipeline in computing:
-
-- **Cryptology ePrint Archive** — the preprint layer. Fully documented in
-  **[`cryptology-eprint-archive.md`](cryptology-eprint-archive.md)** (27,552 reports [API]),
-  which also records the practical access details: no UA fallback needed, but a hard Cloudflare
-  **"20 requests per 1 minute" per-path limit with no `Retry-After`**, and an OAI-PMH endpoint
-  that returns all identifiers in a single 3.34 MB response.
-- **TCHES** (*Transactions on Cryptographic Hardware and Embedded Systems*), **ToSC**
-  (*Symmetric Cryptology*) and the **Journal of Cryptology** — the journal layer, published by
-  IACR as **diamond OA**: free to read *and* free to publish.
-
-**Why an electronics engineer should care:** TCHES *is* the venue for side-channel analysis, fault
-injection, hardware masking, PUFs and post-quantum hardware implementations, and every issue of it
-is free. See [`cryptology-eprint-archive.md` §7.6](cryptology-eprint-archive.md).
-
-### 3.5 PMC and Europe PMC
-
-- **PMC:** https://pmc.ncbi.nlm.nih.gov/ (US National Library of Medicine)
-- **Europe PMC:** https://europepmc.org/ (EMBL-EBI + Wellcome + a funder consortium)
-
-**Relevant even if you have never touched biology**, for one reason: the **NIH Public Access
-Policy** requires deposit of the accepted manuscript of anything NIH funded. That mandate sweeps in
-a large amount of **instrumentation, imaging, signal processing, embedded-device and
-biomedical-electronics engineering** that was published in paywalled engineering journals. If a
-paper had any NIH money behind it, PMC probably has it.
-
-**Measured sizes, 2026-09-02:**
-
-| Measure | Count | Source |
-|---|---|---|
-| PMC records (`db=pmc`, `all[sb]`) | **12,570,099** | E-utilities [API] (S25) |
-| PMC `"open access"[filter]` | **8,192,003** | E-utilities [API] (S25) |
-| Europe PMC, all (`*:*`) | **48,813,426** | REST [API] (S26) |
-| Europe PMC `SRC:MED` (MEDLINE-sourced) | 41,029,618 | REST [API] (S26) |
-| Europe PMC `HAS_FT:Y` (has full text) | **12,106,121** | REST [API] (S26) |
-| Europe PMC `OPEN_ACCESS:Y` | **8,056,165** | REST [API] (S26) |
-
-The two OA figures — 8,192,003 (PMC) and 8,056,165 (Europe PMC) — agree to within 1.7%, which is
-reassuring given they are computed by different organisations from partly different pipelines
-[INF].
-
-**APIs.**
-
-```bash
-# Europe PMC — no key, no UA fallback needed, JSON or XML
-curl -s "https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=OPEN_ACCESS:Y&format=json&pageSize=1"
-
-# NCBI E-utilities — counts and ID lists
-curl -s "https://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=pmc&term=all%5Bsb%5D&retmax=0"
-```
-
-Europe PMC's query language is the one to learn: `HAS_FT:Y`, `OPEN_ACCESS:Y`, `SRC:PPR`
-(preprints), `GRANT_AGENCY:"..."`, `METHODS:"..."` (searches inside the methods section — genuinely
-useful for finding instrument descriptions).
-
-**Bulk.** The **PMC Open Access Subset** is distributed as bulk packages over FTP/HTTPS and on
-AWS S3 (`pmc-oa-opendata`), split into a **Commercial Use** collection (CC0/CC-BY/CC-BY-SA) and a
-**Non-Commercial Use** collection (CC-BY-NC variants) — read the licence split before mining.
-**Caveat from the probe:** the classic OA web service `.../pmc/utils/oa/oa.fcgi?id=PMCnnnnn`
-returned **HTTP 404** on both `www.ncbi.nlm.nih.gov` and `pmc.ncbi.nlm.nih.gov` on 2026-09-02
-(S27) — PMC moved to a new domain and the legacy endpoint path in most tutorials is dead. The
-exact current OA-service path is **[NOT-VERIFIED]**; the E-utilities and Europe PMC endpoints
-above both work and are the safer dependency.
-
-### 3.6 Fully open-access publishers
-
-One paragraph, because the rule is simple: **at a fully-OA publisher every article is free at the
-publisher, permanently, under a named Creative Commons licence.** Unpaywall reports them as `gold`
-(or `diamond`, in OpenAlex's finer taxonomy). The ones a technical reader meets most:
-**PLOS** (non-profit, CC-BY, *PLOS ONE* is a large multidisciplinary venue that carries a lot of
-instrumentation and methods work); **Frontiers** (large, fast, CC-BY, uneven — judge the specialty
-section, not the brand); **eLife** (non-profit; since 2023 it publishes *reviewed preprints* with
-public review reports and no accept/reject decision, which makes it structurally closer to a
-preprint server than to a journal — read the reviews, they are the point); and **MDPI**.
-
-**MDPI carries a specific caveat that this directory has already documented.** MDPI is fully OA and
-its articles are genuinely free — but see [`preprints-org.md`](preprints-org.md), which records
-that MDPI operates **Preprints.org** and that **230 of its 232 "friendly journals" are MDPI
-titles**. That is a closed loop between a preprint server and a publisher, and it should inform how
-much independent signal you read into an MDPI acceptance. The *access* is real; the *filtering* is
-what is in question.
-
-### 3.7 HathiTrust and JSTOR Open Content — older material
-
-Both matter for pre-1990 engineering literature, and both need precision about what is actually
-*downloadable* versus merely *readable*.
-
-**HathiTrust** (https://www.hathitrust.org/) — a not-for-profit collaborative of academic and
-research libraries, **founded 2008**, "now preserving **19+ million digitized items**" [WEB],
-retrieved 2026-09-02 (S28).
-
-- **What you can actually get:** items determined to be **public domain** (in the US, broadly
-  pre-1930 plus US government works plus rights-cleared material) are **full-view and downloadable
-  as PDF**. Everything else is **search-only** — HathiTrust will tell you the page numbers your
-  term appears on and show you nothing else.
-- **Full-book PDF download of public-domain items is generally gated on login via a member
-  institution**; page-at-a-time viewing is open. Practically: if you are not at a member
-  institution, expect to read, not to download.
-- Its strength is **serial runs and monographs** — old handbooks, IRE/AIEE-era volumes,
-  manufacturer references — not journal articles.
-
-**JSTOR Open Content** (https://about.jstor.org/oa-and-free/) [WEB], retrieved 2026-09-02 (S29):
-
-- **"more than 80,000 open access research reports from 187 think tanks"** — freely downloadable,
-  no account. This is a genuine grey-literature collection and overlaps the
-  [companion record](government-and-institutional-technical-reports.md).
-- **Open Access ebooks** and **open images** collections, also free.
-- **"Registered users can read online for free… and access up to 100 free articles every 30
-  days."** Note the wording: **read online**, not download. The free tier is a reading room, not a
-  file service.
-- Everything else on JSTOR is subscription.
-
-**Blunt summary:** HathiTrust and JSTOR are where you *find* old material and often where you
-*read* it. Neither is reliably where you *download* it without an institutional affiliation.
-
-### 3.8 CiteSeerX — probed, and the news is bad
-
-- **Historic URL:** https://citeseerx.ist.psu.edu/ (Penn State)
-
-CiteSeerX was, from 1998 onward, the first system to do automated citation indexing over crawled
-CS PDFs — the direct ancestor of Google Scholar and Semantic Scholar. For years it was the only
-place some 1990s CS papers were indexed in full text.
-
-**Probe result, 2026-09-02 — CiteSeerX has been retired and replaced with a blanket redirect to a
-single Internet Archive capture** [WEB] (S30).
-
-Every path tested returned **HTTP 301** to
-`https://web.archive.org/web/20251230112235/https://citeseerx.ist.psu.edu//<path>`:
-
-| Path requested | Response |
-|---|---|
-| `https://citeseerx.ist.psu.edu/` | 301 → Wayback `20251230112235` |
-| `https://citeseerx.ist.psu.edu/search?q=raft` | 301 → Wayback, same timestamp |
-| `https://citeseerx.ist.psu.edu/robots.txt` | 301 → Wayback, same timestamp |
-| `https://citeseerx.ist.psu.edu/bogus-nonexistent-path-xyz` *(negative control)* | 301 → Wayback, same timestamp |
-| `http://citeseerx.ist.psu.edu/` (plain HTTP) | 301 → Wayback, same timestamp |
-
-**The negative control is the finding.** A bogus path redirects identically to a real one, and
-even `robots.txt` is redirected — meaning nothing is being served from Penn State any more. The
-redirect target is a **fixed timestamp, 2025-12-30 11:22:35 UTC**, not a "latest capture" URL. And
-following it once returned **HTTP 429** from `web.archive.org` (620-byte body), the Wayback
-rate-limit already recorded in [`retrieval-notes.md`](retrieval-notes.md).
-
-**What this means in practice:**
-
-- CiteSeerX is **defunct as a service**. Treat any `citeseerx.ist.psu.edu/viewdoc/...` link in an
-  old bibliography as dead, and expect the Wayback replay of it to be slow and rate-limited.
-- Its **unique value — cached PDFs of 1990s/2000s CS papers whose original hosts are gone** — is
-  not obviously preserved anywhere queryable. The Wayback capture is a *page*, not the index.
-- **Substitute:** Semantic Scholar absorbed much of CiteSeerX's role and considerably more of its
-  corpus; **CORE** (§2.4) is the right place to search for old repository-held full text.
-- This belongs in [`closed-and-defunct-servers.md`](closed-and-defunct-servers.md)'s frame of
-  reference even though CiteSeerX was never a preprint server.
-
----
-
-## 4. Institutional and repository layer
-
-When rungs 1–5 fail, the copy usually still exists — in the author's institutional repository,
-where a mandate put it and where no DOI-level link points at it.
-
-**How to find it, in order:**
-
-1. **OpenAlex `locations[]`** (§2.2) already lists repository copies with a `source.display_name`.
-   Check this before anything manual.
-2. **Search the author's institution directly.** Most universities run EPrints, DSpace or Pure at a
-   predictable host (`eprints.<uni>`, `dspace.<uni>`, `research-information.<uni>`,
-   `<uni>.figshare.com`). Google site-search works: `site:eprints.example.ac.uk "<title>"`.
-3. **CORE** (§2.4) indexes the full text of most of these repositories, which is exactly why it is
-   rung 5 rather than rung 8.
-4. **National aggregators** where relevant — **HAL** for anything French
-   ([`hal.md`](hal.md): 1,788,688 notices **with files** [API]), **NARCIS**-successor services for
-   the Netherlands, **CONICET Digital** for Argentina, etc.
-
-**Registries of repositories** — use these to find *which* repository to search:
-
-| Registry | URL | Probe, 2026-09-02 |
-|---|---|---|
-| **OpenDOAR** | https://v2.sherpa.ac.uk/opendoar/ | **HTTP 403**, **651,922-byte** body (S31) |
-| **ROAR** | https://roar.eprints.org/ | **HTTP 200**, 8,593 B (S32) |
-
-**Counts for both are [NOT-VERIFIED].** OpenDOAR's 403 is *not* the ~5.6 kB Cloudflare fingerprint
-from [`retrieval-notes.md` §1](retrieval-notes.md) — a 651,922-byte 403 body is a different and
-undocumented mechanism, and the same 403 was returned for both `/opendoar/` and
-`/view/repository_by_country/`. Jisc's SHERPA v2 API requires a registered `api-key`; the
-key-less call returned the same 403 page. ROAR (University of Southampton, EPrints-based) *is*
-reachable and is the usable registry of the two today.
-
-Related SHERPA services worth naming even though they were unreachable on the probe date:
-**SHERPA RoMEO** (per-journal self-archiving policy — "may I post the accepted version?") and
-**SHERPA Juliet** (funder OA mandates). Both live behind the same `v2.sherpa.ac.uk` host.
-
----
-
-## 5. Green OA and self-archiving — including the parts that are not archives
-
-**Green OA is the largest source of free full text there is** — 66,803,663 works, 20.7% of
-OpenAlex, versus 15,248,052 gold and 17,714,822 diamond (§2.2). Most publishers, including IEEE,
-ACM, Elsevier and Springer, permit authors to post *some* version somewhere. Which version and
-where is the whole game:
-
-| Version | Typical name | Usually allowed |
-|---|---|---|
-| `submittedVersion` | preprint, as submitted | Almost always |
-| `acceptedVersion` | AAM / post-print — peer-reviewed content, publisher's typesetting absent | Usually, often after an embargo |
-| `publishedVersion` | version of record, publisher PDF | Only if the article is OA |
-
-An `acceptedVersion` is scientifically equivalent to the version of record. **Its page and line
-numbers are not.** If you are quoting or citing a page number, say which version you read.
-
-**Author home pages** remain the single highest-yield manual route, especially for pre-2005 work
-and for systems researchers who keep a `publications.html`. Many papers that Unpaywall calls
-`closed` are one click from the author's name.
-
-### ResearchGate and Academia.edu — use with your eyes open
-
-Both are **for-profit social networks**, not archives, and this record will not soften that:
-
-- **They are not preservation infrastructure.** No commitment to persistence, no DOIs of their own,
-  no succession plan. A link to a ResearchGate PDF is a link to a company's product page.
-- **A large share of the full texts were uploaded by authors who did not hold the right to upload
-  them.** Publishers have litigated over exactly this; takedowns happen in bulk and the file you
-  linked last year may be gone.
-- **Access is gated and degrading.** Probed 2026-09-02 with the Chrome-131 UA: `researchgate.net`
-  → **HTTP 403** (1,714-byte body); `academia.edu` → **HTTP 403** (5,599 B) (S33). Both refuse
-  scripted access; Academia.edu additionally gates much content behind a paid tier.
-- **The "Request full-text" button is fine.** It is a mechanised version of emailing the author,
-  which is rung 9 and entirely legitimate.
-
-**Recommendation:** treat a ResearchGate hit as evidence the paper exists in reachable form, then
-go find a copy in a repository that will still be there in five years. If the ResearchGate copy is
-the only one, save it locally and record where it came from.
-
----
-
-## 6. Practical recipes
-
-Copy-pasteable. `jq` assumed; substitute your own address for `you@your.org` — Unpaywall rejects
-shared placeholders (§2.1).
-
-### 6.1 You have a DOI
-
-```bash
-DOI="10.1145/3079856.3080246"
-EMAIL="you@your.org"
-
-# Rung 1 — Unpaywall
-curl -s "https://api.unpaywall.org/v2/${DOI}?email=${EMAIL}" \
-  | jq '{title, oa_status, is_oa,
-         best: .best_oa_location | {host_type, version, license, url_for_pdf},
-         all: [.oa_locations[] | {host_type, version, url_for_pdf}]}'
-
-# Rung 2 — the arXiv ID Unpaywall does not know about   <-- do not skip this
-curl -s "https://api.semanticscholar.org/graph/v1/paper/DOI:${DOI}?fields=title,externalIds,openAccessPdf" \
-  | jq '{title, arxiv: .externalIds.ArXiv, dblp: .externalIds.DBLP, pdf: .openAccessPdf}'
-# if .externalIds.ArXiv is non-null:  https://arxiv.org/pdf/<that id>
-
-# Rung 3 — every location OpenAlex knows
-curl -s "https://api.openalex.org/works/doi:${DOI}" \
-  | jq '{oa: .open_access,
-         locs: [.locations[] | {src: .source.display_name, version, pdf_url, license}]}'
-
-# Rung 5 — full-text aggregators (CORE needs a free key)
-curl -s -H "Authorization: Bearer $CORE_KEY" \
-  "https://api.core.ac.uk/v3/search/works?q=doi:%22${DOI}%22&limit=5"
-curl -s "https://api.openaire.eu/search/publications?doi=${DOI}&format=json" | jq '.response.results'
-```
-
-### 6.2 You have only a title (or a fragment of one)
-
-```bash
-T="In-Datacenter Performance Analysis of a Tensor Processing Unit"
-
-# Rung 6 first — dblp is the best title->citation resolver in CS. No key.
-curl -s -G "https://dblp.org/search/publ/api" \
-     --data-urlencode "q=${T}" --data "format=json&h=5" \
-  | jq -r '.result.hits.hit[]?.info | "\(.year)  \(.venue)  \(.title)  DOI=\(.doi // "-")  \(.ee // "-")"'
-
-# Then Semantic Scholar's title search, which also gives you the arXiv ID
-curl -s -G "https://api.semanticscholar.org/graph/v1/paper/search" \
-     --data-urlencode "query=${T}" \
-     --data "fields=title,year,venue,externalIds,openAccessPdf&limit=5" | jq '.data'
-
-# Then OpenAlex full-text-ish search, filtered to things that are actually free
-curl -s -G "https://api.openalex.org/works" \
-     --data-urlencode "filter=title.search:${T},open_access.is_oa:true" \
-     --data "per-page=5" \
-  | jq -r '.results[] | "\(.publication_year)  \(.display_name)  \(.open_access.oa_url // "-")"'
-
-# feed the DOI you just found back into 6.1
-```
-
-### 6.3 You suspect it is a systems paper
-
-```bash
-# 1. Is it USENIX? If yes you are already done.
-#    https://www.usenix.org/conference/<venue><yy>/technical-sessions
-#    e.g. osdi24, nsdi24, atc24, fast24, usenixsecurity24
-#    Whole proceedings: https://www.usenix.org/system/files/<venue><yy>_full_proceedings.pdf
-
-# 2. dblp's venue index tells you which venue it was, and dblp links the free copy in `ee`
-curl -s "https://dblp.org/search/venue/api?q=OSDI&format=json" | jq -r '.result.hits.hit[]?.info.url'
-
-# 3. If IEEE-published: check TechRxiv via Crossref, not via the (Cloudflare-blocked) site.
-#    See techrxiv.md for the is-preprint-of relation query.
-
-# 4. If it is crypto/embedded-security: IACR ePrint + TCHES are both free.
-#    See cryptology-eprint-archive.md.
-
-# 5. If it is architecture/ISA-level and nothing above worked, it is probably a
-#    TECHNICAL REPORT, not a paper. Go to:
-#    government-and-institutional-technical-reports.md
-```
-
-### 6.4 Bulk / offline work
-
-```bash
-# OpenAlex — free, anonymous, current
-curl -s "https://openalex.s3.amazonaws.com/?list-type=2&delimiter=/&prefix=data/"   # jsonl/ , parquet/
-
-# Unpaywall — free but the newest public snapshot is 2024-11-27 (~39.2 GB)
-curl -s "https://unpaywall-data-snapshots.s3.us-west-2.amazonaws.com/?list-type=2"
-
-# dblp — daily, CC0, ~1.10 GB gzipped. Fetch the DTD too or it will not parse.
-curl -O https://dblp.org/xml/dblp.xml.gz
-curl -O https://dblp.org/xml/dblp.dtd
-
-# Semantic Scholar / S2ORC — listing is public, downloads need a free API key
-curl -s https://api.semanticscholar.org/datasets/v1/release/latest | jq '.release_id, [.datasets[].name]'
-
-# CORE — 749 GB compressed (2024-07-12), by registration
-# PMC OA subset — FTP/HTTPS packages + AWS S3 `pmc-oa-opendata`; check the commercial/
-#   non-commercial licence split before mining
-```
-
----
-
-## 7. Probe status table
-
-All probes 2026-09-02 unless noted. UA = default `curl` unless "Chrome 131" is stated
-(Chrome 131 = the `AGENTS.md` rung-2 agent).
-
-| Service | Endpoint probed | Status | Notes |
-|---|---|---|---|
-| Unpaywall API | `api.unpaywall.org/v2/<doi>` | **200** | 422 without email; 422 for shared placeholder address; **404** for bogus DOI (207 B) |
-| Unpaywall site | `unpaywall.org/*` | 200 | **1,421 B SPA shell for every path** — size carries no information |
-| Unpaywall S3 | `unpaywall-data-snapshots.s3...` | 200 | Anonymous listing OK; newest snapshot **2024-11-27** |
-| OpenAlex | `api.openalex.org/works` | **200** | Credit+USD rate-limit headers; `meta.cost_usd` |
-| OpenAlex S3 | `openalex.s3.amazonaws.com` | 200 | `data/jsonl/`, `data/parquet/`, `legacy-data/`. `data/works/` → KeyCount 0 |
-| Semantic Scholar | `api.semanticscholar.org/graph/v1` | **200** | No key needed; 404 for bogus DOI |
-| S2 datasets | `.../datasets/v1/release/latest` | 200 | Listing public; `/dataset/s2orc` → **401**, 40 B |
-| CORE | `api.core.ac.uk/v3/...` | **301** (776 B) | Key required; misleading status |
-| CORE site | `core.ac.uk` | 200, 91,189 B | "452M papers" on home page |
-| **BASE** | `base-search.net` | 200 | **Anubis PoW wall v1.27.0+dirty** — size unmeasurable |
-| OpenAIRE | `api.openaire.eu/search/publications` | **200** | 238,449,827. `v3.openaire.eu` → **timeout (000)** |
-| DOAJ | `doaj.org/api/search/...` | **200** | 23,384 journals · 13,535,801 articles |
-| dblp API | `dblp.org/search/publ/api` | **200** | No key, no UA fallback |
-| dblp dump | `dblp.org/xml/dblp.xml.gz` | 200 | 1,099,942,370 B, last-modified 2026-09-01 |
-| **USENIX** | `usenix.org/system/files/osdi24_full_proceedings.pdf` | **200** | 83,779,378 B, `%PDF-`. Chrome 131. Bogus → 404 (16,889 B themed) |
-| USENIX policy | `usenix.org/about`, `/conferences/open-access` | 200 | "banished paywalls in 2008" |
-| ACM | `acm.org/publications/openaccess` | 200 | |
-| ACM OPEN | `libraries.acm.org/acmopen` | 200 | `/acmopen/faq` → 404 |
-| **ACM OpenTOC** | `dl.acm.org/opentoc` | **403, 5,635 B** | Cloudflare fingerprint — blocked, not broken |
-| PMC | `eutils.ncbi.nlm.nih.gov/.../esearch.fcgi?db=pmc` | 200 | 12,570,099 / 8,192,003 OA |
-| PMC OA service | `.../pmc/utils/oa/oa.fcgi` | **404** | Legacy path dead on both hosts |
-| Europe PMC | `ebi.ac.uk/europepmc/webservices/rest/search` | **200** | 48,813,426 total |
-| HathiTrust | `hathitrust.org`, `/about/` | 200 | "19+ million digitized items" |
-| JSTOR open | `about.jstor.org/oa-and-free/` | 200 | 80,000+ reports, 187 think tanks |
-| **CiteSeerX** | every path incl. `robots.txt` and a bogus path | **301 → Wayback** | **Retired.** Fixed target `20251230112235`; following it → 429 |
-| **OpenDOAR** | `v2.sherpa.ac.uk/opendoar/` | **403, 651,922 B** | Not the Cloudflare fingerprint. Count NOT-VERIFIED |
-| ROAR | `roar.eprints.org` | 200, 8,593 B | Reachable; count not extracted |
-| ResearchGate | `researchgate.net` | **403**, 1,714 B | Chrome 131 |
-| Academia.edu | `academia.edu` | **403**, 5,599 B | Chrome 131 |
-
-**User-agent findings for [`retrieval-notes.md`](retrieval-notes.md) / the
-[crawler access table](../../ai-crawler-site-access-table.md):**
-
-- **No UA fallback was needed** for any API in §2 — Unpaywall, OpenAlex, Semantic Scholar,
-  OpenAIRE, DOAJ, dblp, E-utilities and Europe PMC all answered default `curl`.
-- **Chrome 131 was used for all HTML pages** and sufficed for `usenix.org`, `core.ac.uk`,
-  `acm.org`, `libraries.acm.org`, `hathitrust.org`, `about.jstor.org`, `roar.eprints.org`.
-- **Chrome 131 did not help** against `dl.acm.org/opentoc` (Cloudflare), `base-search.net`
-  (Anubis PoW), `v2.sherpa.ac.uk` (403 with a 651 kB body), `researchgate.net`, `academia.edu`.
-- **New fingerprint to record: a ~651 kB HTTP 403 from `v2.sherpa.ac.uk`.** It is neither the
-  ~5.6 kB Cloudflare challenge nor the Anubis PoW page. Worth adding to the table alongside them.
-- **New trap to record: `unpaywall.org` serves a byte-identical 1,421-byte SPA shell for every
-  path**, exactly like the `osf.io` 4,207-byte shell already in
-  [README §4](README.md#6-probing-traps).
-
----
-
-## 8. Sources
-
-All retrieved **2026-09-02** unless stated. Raw probe output is under
-[`../../scratch/preprint-repositories/oa-fulltext/`](../../scratch/preprint-repositories/oa-fulltext/).
-
-- **S1** `https://unpaywall.org/`, `/products/api`, `/products/data-feed`, `/faq` — all HTTP 200,
-  all exactly 1,421 bytes. Supports: SPA-shell trap; corpus size NOT-VERIFIED. [WEB]
-- **S2** `https://api.unpaywall.org/v2/<doi>?email=…` for `10.1038/nature12373`,
-  `10.1109/ISCA.2014.6853210`, `10.1109/SP.2019.00002`, `10.1145/2517349.2522738`,
-  `10.1109/JPROC.2017.2761740`, `10.1145/3079856.3080246`; plus 422/404 controls. Supports: §2.1
-  worked-example table, taxonomy, negative controls. [API]
-- **S3** `https://api.openalex.org/works/doi:10.1145/3079856.3080246` — `oa_status: closed`,
-  `any_repository_has_fulltext: false`. Supports: the three-way arXiv blind-spot comparison. [API]
-- **S4** `https://api.semanticscholar.org/graph/v1/paper/DOI:10.1145/3079856.3080246` —
-  `externalIds.ArXiv: 1704.04760`, `isOpenAccess: true` vs `openAccessPdf.status: CLOSED`.
-  Supports: rung 2, the self-contradiction note. [API]
-- **S5** `https://unpaywall-data-snapshots.s3.us-west-2.amazonaws.com/?list-type=2` — snapshot
-  keys, sizes and `LastModified`. Supports: the bulk table and the staleness flag. [API]
-- **S6** `https://api.openalex.org/{works,authors,sources,institutions,publishers}?per-page=1` →
-  `meta.count`. Supports: the entity-count table. [API]
-- **S7** `https://api.openalex.org/works?group_by=open_access.oa_status`. Supports: the OA
-  breakdown; buckets sum exactly to 321,988,823. [API]
-- **S8** Response headers from `https://api.openalex.org/works?per-page=1` —
-  `x-ratelimit-limit: 1000`, `x-ratelimit-limit-usd: 0.1`, `x-ratelimit-cost-usd: 0.0001`,
-  `x-ratelimit-reset: 63043`. Supports: §2.2 rate limits. [API]
-- **S9** `https://openalex.s3.amazonaws.com/?list-type=2&delimiter=/` and `&prefix=data/`.
-  Supports: snapshot layout. [API]
-- **S10** `https://api.semanticscholar.org/datasets/v1/release/latest` (release `2026-08-25`) and
-  `/dataset/s2orc` → 401. Supports: S2ORC sizes and access route. [API]
-- **S11** `https://core.ac.uk/` — "Search 452M papers from around the world". [WEB]
-- **S12** `https://api.core.ac.uk/v3/search/works?q=test&limit=1` → HTTP 301, 776 B. [API]
-- **S13** `https://core.ac.uk/documentation/dataset` — 2024-07-12 749 GB / ~2.7 TB; 2023-03-18 and
-  2022 393 GB / 3.5 TB. [DOC]
-- **S14** `https://www.base-search.net/` — Anubis `v1.27.0+dirty` challenge page, 7,846 B, hosted
-  by Bielefeld University Library. [WEB]
-- **S15** `https://api.openaire.eu/search/publications?size=0` → `<total>238449827</total>`;
-  `https://v3.openaire.eu/api/publications/count` → timeout. [API]
-- **S16** `https://doaj.org/api/search/{journals,articles}/*?pageSize=1` → 23,384 / 13,535,801. [API]
-- **S17** `https://dblp.org/search/publ/api?q=RISC-V&format=json&h=1` → `@total: 2313`. [API]
-- **S18** `HEAD https://dblp.org/xml/dblp.xml.gz` → 1,099,942,370 B, last-modified
-  2026-09-01 23:47:15 GMT. [API]
-- **S19** `https://www.usenix.org/about` — "We banished paywalls in 2008…". [DOC]
-- **S20** `https://www.usenix.org/conferences/open-access` — the fuller statement quoted in §3.1. [DOC]
-- **S21** `https://www.usenix.org/conference/osdi24/technical-sessions` (200, 259,550 B);
-  `osdi24_full_proceedings.pdf` (200, 83,779,378 B, `%PDF-`); `osdi24_proceedings_interior.pdf`
-  (200, 82,578,353 B); bogus filename → 404, 16,889 B. [WEB]
-- **S22** `https://libraries.acm.org/acmopen` — ACM OPEN description quoted in §3.2. [DOC]
-- **S23** `https://dl.acm.org/opentoc` → HTTP 403, 5,635 B (Cloudflare fingerprint). [WEB]
-- **S24** `https://www.acm.org/publications/openaccess` (200, 76,905 B);
-  `https://libraries.acm.org/acmopen/faq` (404). [WEB]
-- **S25** `https://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=pmc&term=all%5Bsb%5D` →
-  12,570,099; `term="open access"[filter]` → 8,192,003. [API]
-- **S26** `https://www.ebi.ac.uk/europepmc/webservices/rest/search` for `*:*`, `SRC:MED`,
-  `HAS_FT:Y`, `OPEN_ACCESS:Y`. [API]
-- **S27** `https://www.ncbi.nlm.nih.gov/pmc/utils/oa/oa.fcgi?id=PMC5334499` → 404 (1,584 B);
-  `https://pmc.ncbi.nlm.nih.gov/utils/oa/oa.fcgi?id=PMC5334499` → 404 (48,716 B). [WEB]
-- **S28** `https://www.hathitrust.org/about/` — "founded in 2008… now preserving 19+ million
-  digitized items". [WEB]
-- **S29** `https://about.jstor.org/oa-and-free/` — "more than 80,000 open access research reports
-  from 187 think tanks"; "up to 100 free articles every 30 days". [WEB]
-- **S30** `citeseerx.ist.psu.edu` — five paths incl. `robots.txt` and a deliberately bogus path,
-  all HTTP 301 → `web.archive.org/web/20251230112235/…`; following → 429. [WEB]
-- **S31** `https://v2.sherpa.ac.uk/opendoar/` and `/view/repository_by_country/` → HTTP 403,
-  651,922 B, Chrome 131. [WEB]
-- **S32** `https://roar.eprints.org/` → HTTP 200, 8,593 B. [WEB]
-- **S33** `https://www.researchgate.net/` → 403, 1,714 B; `https://www.academia.edu/` → 403,
-  5,599 B; both Chrome 131. [WEB]
-- **S34** [`arxiv.md` §7.5](arxiv.md) — arXiv IDs `1703.09039` and `1704.04760`, previously
-  verified in this directory; used as the ground truth against which Unpaywall's `closed` verdicts
-  are judged wrong in practice. [internal]
diff --git a/research/preprint-repositories/optimization-online.md b/research/preprint-repositories/optimization-online.md
deleted file mode 100644
index 2951018..0000000
--- a/research/preprint-repositories/optimization-online.md
+++ /dev/null
@@ -1,398 +0,0 @@
-# Optimization Online — eprint repository record
-
-- **URL:** https://optimization-online.org/
-- **Operator:** Volunteer editorial team — a **Principal Coordinator** (Andreas Wächter,
-  Gurobi Organization), a **Deputy Principal Coordinator** (Stephen Wright, University of
-  Wisconsin–Madison) and ~17 **Area Coordinators** (S1). **Supported by the Mathematical
-  Optimization Society and the Wisconsin Institute for Discovery** at UW–Madison, and
-  physically hosted "on the servers within the Discovery Building" (S1).
-- **Discipline scope:** "a repository of Eprints about optimization and related topics"
-  (S1) — linear, integer, conic/semidefinite, nonlinear, global, stochastic, robust and
-  bilevel optimization, plus applications and **optimization software** (§2).
-- **Launched:** **2000** — "conceived in 2000 by Jean-Pierre Goux, Sanjay Mehrotra, and Steve
-  Wright as an initiative of the **Optimization Technology Center** at Argonne and
-  Northwestern" (S1). Oldest eprint on the site: **2000-08-08** (S4). **Status:** active,
-  26 years continuous.
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-Optimization Online is the mathematical-optimization community's own eprint archive. It
-predates almost every server in this collection except arXiv and the IACR ePrint archive,
-and it has run continuously since August 2000 under three generations of custodians: Goux
-built the original site; **Steve Wright "maintained the site as lead moderator, and mailed
-the monthly digests from 2000–2021"**; Andreas Wächter is the current lead moderator (S1).
-The "monthly digest" is not incidental — an email announcement list
-(`https://groups.google.com/a/g-groups.wisc.edu/g/optimization-online/`) is linked from the
-front page (S2) and is how much of the field actually consumes the archive.
-
-It is a **repository, not a journal**: submission is free, there is no peer review, and the
-service explicitly disclaims quality judgement (§4). What it is not is a general
-mathematics server — that is arXiv `math.OC` — and the relationship between the two is
-discussed in §5.
-
-**The 2022 relaunch.** The site was rebuilt on WordPress and the migration is documented in
-the operator's own credits: "Em Craft at the Wisconsin Institute for Discovery has provided
-technical support starting in 2011. She conceived and developed the **new WordPress-based
-site that went live in 2022**" (S1). Note that this is **2022, not 2023** — if you have seen
-"2023 relaunch" written elsewhere, the operator's own About page contradicts it. The live
-site reports `<meta name="generator" content="WordPress 6.5.10">` on the GeneratePress
-theme (S2). Old URLs survived the rebuild; see §8, which is the durability question this
-knowledge base cares about.
-
-## 2. Scope and subject taxonomy
-
-Every eprint carries **between 1 and 3 categories** from a two-level taxonomy (S3). The
-counts below are the site's own per-category counters, read from
-`https://optimization-online.org/categories/` on **2026-09-01** (S3). Because items carry up
-to three, the column sums well above the 9,843 total.
-
-| Top-level category (count) | Sub-categories (counts) |
-|---|---|
-| **Nonlinear Optimization** (2,554) | Constrained Nonlinear Optimization (799), Unconstrained (392), Quadratic Programming (309), Systems governed by Differential Equations (135), Nonlinear Systems and Least-Squares (117), Bound-constrained (97) |
-| **Convex and Nonsmooth Optimization** (2,177) | Convex Optimization (1,073), Nonsmooth Optimization (684), Generalized Convexity/Monoticity (63) |
-| **Integer Programming** (2,088) | (Mixed) Integer Linear Programming (766), (Mixed) Integer Nonlinear Programming (588), Cutting Plane Approaches (306), 0-1 Programming (303) |
-| **Applications – OR and Management Sciences** (1,797) | Transportation (368), Scheduling (243), Finance and Economics (196), Production and Logistics (184), **Telecommunications (112)**, Supply Chain Management (98), Airline Optimization (35), Yield Management (20), Marketing (14) |
-| **Linear, Cone and Semidefinite Programming** (1,616) | Semi-definite Programming (658), Linear Programming (340), Second-Order Cone Programming (117), Cone Programming (39) |
-| **Combinatorial Optimization** (1,412) | Branch and Cut Algorithms (232), Polyhedra (227), Approximation Algorithms (181), Meta Heuristics (172), Graphs and Matroids (160) |
-| **Applications – Science and Engineering** (1,350) | Statistics (188), Data-Mining (160), **Control Applications (156)**, Biomedical (106), **Energy (93)**, Facility Planning and Design (89), Basic Sciences (86), Optimization of Systems modeled by PDEs (71), Mechanical Engineering (46), Multidisciplinary Design Optimization (35), Chemical Engineering (33), Civil and Environmental Engineering (30), **VLSI layout (13)** |
-| **Stochastic Programming** (1,137) | — |
-| **Other Topics** (832) | Multi-Criteria Optimization (300), Dynamic Programming (212), Game Theory (172), Optimization of Simulated Systems (51) |
-| **Global Optimization** (768) | Global Optimization Theory (237), Applications (124), Stochastic Approaches (77) |
-| **Robust Optimization** (729) | — |
-| **Optimization Software and Modeling Systems** (435) | **Parallel Algorithms (137)**, **Optimization Software Benchmark (71)**, **Optimization Software Design Principles (44)**, **Modeling Languages and Systems (39)**, **Problem Solving Environments (22)** |
-| **Network Optimization** (320) | — |
-| **Complementarity and Variational Inequalities** (297) | — |
-| **Optimization in Data Science** (160) | Data Science Algorithms (43), Data Science Applications (14), Data Science Theory (12) |
-| **Infinite Dimensional Optimization** (167) | Semi-infinite Programming (66), Distributed Control (11) |
-| **Bilevel Optimization** (47) | — |
-
-Free-text **tags** exist alongside categories; the front page surfaces a tag cloud including
-`branch-and-bound`, `branch-and-cut`, `column-generation`, `cutting-planes`,
-`interior-point-methods`, `mixed-integer-linear-programming`, `benders-decomposition`,
-`distributionally-robust-optimization`, `derivative-free-optimization` (S2).
-
-## 3. Why a systems or hardware engineer should care
-
-This is a mathematics repository, so the connection needs stating plainly. Almost every
-hard resource-allocation problem in computing systems is an optimization model, and the
-people who write the solvers you would use publish their solver papers **here**, not on
-arXiv:
-
-- **Solvers you actually link against.** The SCIP Optimization Suite release reports —
-  `The SCIP Optimization Suite 9.0` (2024-02-26) and `10.0` (2025-11-24) — are posted here
-  (S4). SCIP 10.0's abstract lists "a new solving mode for exactly solving rational
-  mixed-integer linear programs", conflict analysis, symmetry handling — the kind of detail
-  that only appears in the release report. **IPOPT**'s definitive implementation paper is
-  here (§7). `PaPILO: A Parallel Presolving Library for Integer and Linear Optimization with
-  Multiprecision Support` (2023-08-04) is here.
-- **ILP/MILP formulations.** `Integer Programming` (2,088) plus `(Mixed) Integer Linear
-  Programming` (766) is where you find formulations for the problems that show up as
-  scheduling, placement, partitioning and register allocation.
-- **Compiler and EDA-adjacent work.** The `VLSI layout` sub-category is small (13) but
-  real, and includes both classic and current work — `Global Routing in VLSI Design:
-  Algorithms, Theory, and Computational Practice` (2010) and `Sequential Nonlinear-Programming
-  Approach to Thermal-Aware VLSI Floorplanning using Multi-boundary Shapes` (2026-04-01) (§7).
-- **Scheduling and routing.** `Scheduling` (243), `Transportation` (368),
-  `Production and Logistics` (184), `Network Optimization` (320).
-- **Benchmarks and reproducibility.** `Optimization Software Benchmark` (71) — this is where
-  MIPLIB-style benchmark methodology and solver comparisons live.
-- **Parallel and HPC solver engineering.** `Parallel Algorithms` (137).
-- **Energy and control.** `Energy` (93), `Control Applications` (156) — grid dispatch, unit
-  commitment, MPC formulations.
-- **QUBO / quantum annealing.** The most-used practical tutorial on encoding constrained
-  problems as QUBO — the format D-Wave and Ising-machine hardware consume — is here (§7).
-
-## 4. Screening and moderation — there *is* an editorial check, and it is documented
-
-Unlike arXiv (endorsement-based) or engrXiv (volunteer pre-moderation), Optimization Online
-runs a **coordinator-based editorial screen**, and unusually it publishes both the
-submitter-facing policy *and* the internal instructions given to coordinators.
-
-**Submitter-facing policy** (S5, verbatim):
-
-> "Papers can be submitted to Optimization Online only in pdf format. Papers are screened to
-> ensure their relevance **by one of the coordinators for the category selected by the
-> submitting author as the principal category**. The acceptance/rejection decision of a
-> coordinator is **final**. Coordinators check that the submission details given by the
-> authors are all present and correct and that the submitted files are readable. They **do
-> not usually evaluate the report for quality or mathematical correctness**. Consequently,
-> we make no claim about quality or correctness of the reports on the site. Optimization
-> Online reserves the right in its sole discretion to remove accepted papers from the
-> repository if complaints are received regarding their accuracy or authenticity."
-
-**Coordinator-facing instructions**, published openly on the Help page (S3, verbatim):
-
-> "To approve the EPrint: Verify the following: … The title should not be in ALL CAPS. This
-> messes up the uniform look of our pages and digests. **The EPrint should not be obviously
-> crazy or wrong (e.g. P=NP papers). But otherwise, be fairly permissive and generous with
-> accepts. The EPrint has not already appeared. If the author gives a journal, volume number,
-> page number, etc, the work is deemed to have appeared and you should reject it.**"
-
-Three consequences worth internalising:
-
-1. **There is a crank filter.** "Not obviously crazy or wrong (e.g. P=NP papers)" is an
-   explicit, named exclusion. This is more of a gate than arXiv's `math.GM` provides.
-2. **Already-published work is rejected.** Optimization Online is a *pre*print archive in
-   the strict sense. This is why the archive is not a green-OA mirror of the literature —
-   and why post-publication the site encourages replacing the full text with a reference:
-   "We encourage authors to provide a reference to the paper in place of the full text, once
-   it has been published in a journal" (S5).
-3. **Authors are responsible for copyright compliance after transfer**: "Authors are
-   responsible for removing a paper from the site once copyright for the paper has been
-   transferred to a publisher" (S5).
-
-Authors can also self-edit and self-delete: the Help page documents "Move to Trash",
-"Update", PDF replacement and restoration from trash, with the note "EPrints in the trash
-longer than a week may be permanently removed" (S3).
-
-## 5. Reliability — what you can and cannot trust
-
-**A posting guarantees:** a stable URL under `optimization-online.org/YYYY/MM/ID/`, a
-`Published:` date and an `Updated:` date, a category assignment, a coordinator's judgement
-that the work is in scope and not obvious crankery, and a hosted PDF. It does **not**
-guarantee correctness — the operator says so ("we make no claim about quality or
-correctness", S5).
-
-**No DOIs.** Optimization Online assigns no persistent identifiers. Items are cited by URL,
-and the site provides two URL forms (a dated permalink and a `?p=NNNNN` short URL, §8). If
-you need a DOI for an optimization preprint, the author has to post to arXiv as well.
-
-**Relationship to arXiv `math.OC` — overlap is large and deliberate.** Scale first (S6, S4):
-
-| Archive | Items | Date |
-|---|---|---|
-| arXiv `math.OC` | **63,892** | 2026-09-01 |
-| Optimization Online | **9,843** | 2026-09-01 |
-
-arXiv `math.OC` is 6.5× larger. So why do authors use Optimization Online at all, and often
-*both*?
-
-- **Audience targeting.** Optimization Online's monthly digest goes to the optimization
-  community specifically (S1, S2). arXiv `math.OC` is a firehose shared with control theory,
-  calculus of variations and machine-learning theory.
-- **A curated, single-discipline category tree** (§2) that maps onto how the field actually
-  divides itself — you can browse "Cutting Plane Approaches" or "Semi-definite Programming"
-  directly, which no arXiv category supports.
-- **The "Citation" field.** Every Optimization Online record carries a free-text `Citation`
-  line where authors record the eventual journal reference or the originating tech-report
-  number. On the IPOPT record it reads "IBM Research Report RC 23149, IBM T.J. Watson
-  Research Center…"; on the Julia record it reads "Published in INFORMS Journal on Computing:
-  http://dx.doi.org/10.1287/ijoc.2014.0623" (S4). This is a human-maintained
-  preprint→publication link, and it is often present where Crossref has nothing.
-- **The crank filter** (§4) — a real, if modest, quality signal that arXiv `math.OC` does
-  not provide.
-
-Authors who want both the DOI-less community channel *and* arXiv's indexing and permanence
-simply post twice. **The fraction that do is [NOT-VERIFIED]** — no cross-matching study was
-run in this pass, and Optimization Online exposes no arXiv-ID field to match on.
-
-**Known failure modes.** (a) Authors are supposed to remove full text after copyright
-transfer (§4), so **a record can lose its PDF over time** — the archive is not designed to
-be permanent full text. (b) No DOI means link rot is a live risk, mitigated but not
-eliminated by the redirect layer (§8). (c) `Updated:` dates can be many years after
-`Published:` (the IPOPT record shows "Published: 2004/03/15, Updated: 2022/08/04", S4), so
-the document you download may not be the one that was posted. (d) No versioning UI — an
-update overwrites.
-
-**How to sanity-check an item.** Read the `Citation` field first; if it names a journal,
-read the journal version. Compare `Published:` and `Updated:`. Confirm the PDF is still
-attached (some records have no "View PDF" link at all — the Julia record is one, S4).
-
-## 6. Size and growth
-
-| Measure | Value | Date | Source |
-|---|---|---|---|
-| WordPress REST API `X-WP-Total` header on `/wp/v2/posts` | **9,843** | 2026-09-01 | [API] S4 |
-| Sum of the site's own month-archive counters (314 months) | **9,843** | 2026-09-01 | [WEB] S1 |
-
-**Two independent counters agree exactly.** That is the strongest size evidence in this
-whole collection, and it is worth stating: the WordPress post count and the front-end
-archive widget were computed by different code paths and returned the same number.
-
-**Eprints by year** (from the month-archive counters, S1):
-
-| Year | N | | Year | N | | Year | N |
-|---|---|---|---|---|---|---|---|
-| 2000 | 34 | | 2009 | 312 | | 2018 | 561 |
-| 2001 | 167 | | 2010 | 340 | | 2019 | 497 |
-| 2002 | 165 | | 2011 | 415 | | 2020 | **601** |
-| 2003 | 200 | | 2012 | 393 | | 2021 | 535 |
-| 2004 | 219 | | 2013 | 435 | | 2022 | 400 |
-| 2005 | 220 | | 2014 | 491 | | 2023 | 370 |
-| 2006 | 238 | | 2015 | 515 | | 2024 | 379 |
-| 2007 | 284 | | 2016 | 484 | | 2025 | 410 |
-| 2008 | 296 | | 2017 | 557 | | 2026 (to 09-01) | 325 |
-
-The shape is a 20-year climb peaking in 2020 (601), a dip to 370 in 2023, and a partial
-recovery. 2026 at 325 by 1 September annualises to ~490 [INF] — the highest since 2019.
-Notably, **there is no generative-AI submission spike** of the kind engrXiv reports; the
-combination of a specialised field, a required PDF and a coordinator screen appears to have
-held [INF].
-
-## 7. Landmark and representative entries
-
-All verified live on 2026-09-01 (S4). "Preprint first?" is judged from the record's own
-`Published:` date versus the journal version's year.
-
-| Eprint | URL | Published | Why it matters | Preprint first? |
-|---|---|---|---|---|
-| Wächter & Biegler, *On the Implementation of an Interior-Point Filter Line-Search Algorithm for Large-Scale Nonlinear Programming* | https://optimization-online.org/2004/03/836/ | 2004-03-15 (updated 2022-08-04) | **The IPOPT paper.** The definitive description of the algorithm behind the open-source IPOPT solver, benchmarked on 954 CUTEr problems. One of the most-cited papers in nonlinear optimization. `Citation:` "IBM Research Report RC 23149" | **Yes** — posted March 2004; the journal version is *Math. Program.* 106(1), 2006 |
-| Dunning & Lubin, *Computing in Operations Research using Julia* | https://optimization-online.org/2013/05/3883/ | 2013-05-19 (updated 2015-03-18) | The paper that established Julia as a viable language for mathematical optimization; the direct ancestor of **JuMP**. Explicitly about JIT compilation and cross-language benchmarks | **Yes** — `Citation:` "Published in INFORMS Journal on Computing: 10.1287/ijoc.2014.0623" (2015) |
-| Du, Glover & Kochenberger, *A Tutorial on Formulating and Using QUBO Models* | https://optimization-online.org/2019/01/7014/ | 2019-01-05 (updated 2019-06-14) | The standard practical reference for encoding constrained combinatorial problems as QUBO — the input format for D-Wave quantum annealers and neuromorphic Ising hardware. Tags: `quantum computing`, `quadratic binary programming` | **Yes** — widely circulated from this posting |
-| Hojny, Besançon, Bestuzheva et al., *The SCIP Optimization Suite 10.0* | https://optimization-online.org/2025/11/the-scip-optimization-suite-10-0/ | 2025-11-24 | Release report for the leading open-source MILP/MINLP/CIP solver; 28 authors. Includes exact rational MILP solving, implied-integrality presolve, flower-inequality separation | **Yes** — this *is* the report; SCIP release reports are canonically published here |
-| Bestuzheva et al., *The SCIP Optimization Suite 9.0* | https://optimization-online.org/2024/02/the-scip-optimization-suite-9-0/ | 2024-02-26 | Previous SCIP release report | Yes |
-| *PaPILO: A Parallel Presolving Library for Integer and Linear Optimization with Multiprecision Support* | https://optimization-online.org/2023/08/papilo-a-parallel-presolving-library-for-integer-and-linear-optimization-with-multiprecision-support/ | 2023-08-04 | The presolver used by SCIP; parallel + multiprecision | Yes |
-| Deza, Terlaky, Vannelli, Dickson & Zhang, *Global Routing in VLSI Design: Algorithms, Theory, and Computational Practice* | https://optimization-online.org/2010/12/2852/ | 2010-12-14 | Polynomial-time approximation algorithm for VLSI global routing from an IP formulation, with serial and parallel implementations, on standard benchmarks. Categories: Integer Programming, **VLSI layout** | Yes |
-| Morton, *Sequential Nonlinear-Programming Approach to Thermal-Aware VLSI Floorplanning using Multi-boundary Shapes* | https://optimization-online.org/2026/04/sequential-nonlinear-programming-approach-to-thermal-aware-vlsi-floorplanning-using-multi-boundary-shapes/ | 2026-04-01 | Current EDA-adjacent work: thermal-aware soft-macro floorplanning with IO-block placement | Yes |
-| *Optimization as an Internet Resource* | https://optimization-online.org/2000/08/190/ | 2000-08-08 | **The oldest eprint on the server** — the Optimization Technology Center's own manifesto, and a nice historical marker | Yes |
-
-Two more worth knowing about, verified present (S4): *Template-based Minor Embedding for
-Adiabatic Quantum Optimization* (2019-10-09,
-https://optimization-online.org/2019/10/7418/), which is about mapping problems onto D-Wave
-Chimera/Pegasus hardware graphs; and *Smoothie: Mixing the strongest MIP solvers to solve
-hard MIP instances on supercomputers* (2025-10-27) for HPC-scale solver portfolios.
-
-## 8. Access, APIs, bulk retrieval — and URL durability
-
-**No OAI-PMH, no DOIs.** `/oai` and `/oai2` both return **404** (S7). There is no
-machine-readable identifier scheme.
-
-**The WordPress REST API is fully open and is the right bulk interface:**
-
-```bash
-curl -I 'https://optimization-online.org/wp-json/wp/v2/posts?per_page=1'   # X-WP-Total: 9843
-curl 'https://optimization-online.org/wp-json/wp/v2/posts?per_page=100&page=2&_fields=id,date,link,title'
-curl 'https://optimization-online.org/wp-json/wp/v2/posts?search=SCIP&per_page=5&_fields=id,date,link,title'
-curl 'https://optimization-online.org/wp-json/'                            # route discovery
-```
-
-`X-WP-Total` gives the exact corpus size in a single HEAD request. There is also an RSS feed
-(`/feed/`) and a sitemap. `robots.txt` is permissive — it disallows only `/wp-admin/` and
-publishes `Sitemap: https://optimization-online.org/wp-sitemap.xml` (S7); no crawl-delay, no
-AI-crawler exclusions, no Cloudflare challenge, and no user-agent substitution was needed at
-any point.
-
-### URL durability across the 2022 rebuild — probed
-
-This is the question this knowledge base cares about, and the answer is **good**. The
-pre-2022 site used `DB_HTML/YYYY/MM/ID.html` for abstracts and `DB_FILE/YYYY/MM/ID.pdf` for
-full text. Probed 2026-09-01 (S7):
-
-| Old-style URL | Result | Final location |
-|---|---|---|
-| `http://www.optimization-online.org/DB_HTML/2005/03/1078.html` | 301 → … → **200** (3 hops) | `https://optimization-online.org/2005/03/1078/` |
-| `http://www.optimization-online.org/DB_HTML/2004/03/836.html` (IPOPT) | 301 → … → **200** (3 hops) | `https://optimization-online.org/2004/03/836/` |
-| `http://www.optimization-online.org/DB_HTML/2001/12/420.html` | 301 → … → **200** | `https://optimization-online.org/2001/12/420/` |
-| `http://www.optimization-online.org/DB_FILE/2004/03/836.pdf` | 301 → … → **200** (3 hops) | `https://optimization-online.org/2004/03/836/` — **the landing page, not the PDF** |
-| `https://optimization-online.org/?p=9506` (short URL) | **301** (1 hop) | `https://optimization-online.org/2004/03/836/` |
-
-**Verdict:** old abstract URLs from 2001, 2004 and 2005 all still resolve to the correct
-current record, including the `http://` and `www.` forms. That is 20+ year link stability
-across a full platform change — better than most publishers manage. **One caveat:** old
-direct-PDF links (`DB_FILE/.../ID.pdf`) redirect to the *landing page*, not to a PDF. Any
-crawler that stored `DB_FILE` URLs and expects `application/pdf` will now receive HTML with
-a 200 status. Current PDFs live at `https://optimization-online.org/wp-content/uploads/YYYY/MM/ID.pdf`.
-
-### Negative controls — three of them
-
-| Probe | Result |
-|---|---|
-| `https://optimization-online.org/this-page-does-not-exist-zzz9999/` | **404**, 93,532 bytes |
-| `http://www.optimization-online.org/DB_HTML/1999/99/999999.html` (bogus old-style) | **404**, 93,528 bytes — *no* redirect issued |
-| `http://www.optimization-online.org/DB_HTML/2000/09/1.html` (plausible but non-existent old ID) | **404** after 2 redirect hops |
-| `https://optimization-online.org/wp-content/uploads/2004/03/999999.pdf` (bogus PDF) | **404**, 93,551 bytes |
-| *Control:* `https://optimization-online.org/wp-content/uploads/2004/03/836.pdf` (real PDF) | **200**, **333,438 bytes**, `Content-Type: application/pdf` |
-
-So the redirect layer is **selective** — it rewrites only IDs that exist, and returns a real
-404 otherwise. And a 404 body here is ~93 KB of themed error page, so **content-length is
-useless as an existence test; you must read the status code or the Content-Type** (S7).
-
-## 9. Licensing and reuse
-
-**There is no licence.** Optimization Online applies no Creative Commons or other open
-licence. The copyright terms are (S5, verbatim):
-
-> "By submitting a paper, all authors of the paper represent and warrant that: (i) the paper
-> constitutes an original work of authorship and that any necessary permissions have been
-> obtained…; and (ii) **other users of Optimization Online are granted permission to download
-> the paper for personal use.**"
-
-"Download for personal use" is the *entire* grant. That means: **no redistribution, no
-inclusion in a derived corpus, no text-and-data-mining of the full text under an open
-licence.** Metadata harvesting via the WordPress API is a different matter and is not
-restricted by robots.txt, but the PDFs themselves are all-rights-reserved-with-a-reading-
-permission. Anyone building a mining pipeline should treat this repository differently from
-arXiv or TechRxiv.
-
-The site also disclaims liability for copyright violations and requires authors to indemnify
-the coordinators, sponsors and hosts (S5).
-
-## 10. Caveats and controversies
-
-- **No DOIs, no OAI-PMH, no versioning.** For a 26-year-old archive this is the biggest
-  structural weakness. Cite the dated permalink (`/YYYY/MM/ID/`), which is what the redirect
-  layer preserves; the `?p=NNNNN` short URL also works but is opaque.
-- **Full text is expected to be withdrawn after journal publication** (§4). The archive is
-  explicitly *not* a permanent open-access record; treat it as a preprint announcement
-  service. Archive PDFs you depend on.
-- **The restrictive licence** (§9) is the strictest in this collection and is easy to miss
-  because the site otherwise feels like an open repository.
-- **`Updated:` can lag `Published:` by nearly two decades** (§5) — pin what you downloaded.
-- **Rejection decisions are final and unappealable** (§4), and coordinators may reject "for
-  any reason"; there is no published rejection rate. **[NOT-VERIFIED]**.
-- **Relaunch year:** the operator's About page says **2022** (S1). Any secondary source
-  claiming 2023 is contradicted by the primary document; this record follows the primary.
-- **Overlap with arXiv `math.OC` is unquantified** (§5) — **[NOT-VERIFIED]**.
-- **Not indexed as a source in OpenAlex.**
-  `https://api.openalex.org/sources?filter=display_name.search:Optimization%20Online` returns
-  `meta.count = 0` (S8) — unsurprising given the absence of DOIs, but a real gap for anyone
-  doing bibliometrics.
-- **Wikipedia has no retrievable article**: the REST summary endpoint for
-  `Optimization_Online` returned an internal error on 2026-09-01 (S8), so no independent
-  size or history cross-check is recorded here.
-
-## 11. Sources
-
-- **S1** — `https://optimization-online.org/about/` — coordinator roster (Principal, Deputy
-  and 17 Area Coordinators with their areas), the *Development* section (conceived in 2000 by
-  Goux, Mehrotra and Wright at the Optimization Technology Center, Argonne/Northwestern;
-  Wright as lead moderator and digest mailer 2000–2021; Wächter current lead), *Support*
-  (Mathematical Optimization Society + Wisconsin Institute for Discovery), *Hosting*
-  (Discovery Building), and *Special Credits* ("the new WordPress-based site that went live
-  in 2022"). The page also carries the full month-archive widget used for the per-year
-  table. Retrieved 2026-09-01. **[DOC]**
-- **S2** — `https://optimization-online.org/` — front page; `<meta name="generator"
-  content="WordPress 6.5.10">`; GeneratePress theme; tag cloud; link to the announcement
-  list `https://groups.google.com/a/g-groups.wisc.edu/g/optimization-online/`. Retrieved
-  2026-09-01. **[WEB]**
-- **S3** — `https://optimization-online.org/categories/` (the full two-level taxonomy with
-  per-category counters, "Each Eprint may have between 1 and 3 categories") and
-  `https://optimization-online.org/help/` (the coordinator approval instructions quoted in
-  §4, plus the eprint edit/trash lifecycle). Retrieved 2026-09-01. **[DOC]**
-- **S4** — WordPress REST API, `https://optimization-online.org/wp-json/wp/v2/posts`
-  (`X-WP-Total: 9843`; `?search=` queries for SCIP, MIPLIB, IPOPT, VLSI, compiler, quantum
-  annealing, benchmark, scheduling; `?order=asc&orderby=date` for the oldest records) and
-  `https://optimization-online.org/wp-json/` for route discovery; plus direct retrieval of
-  the individual eprint pages `2004/03/836/`, `2013/05/3883/`, `2019/01/7014/`,
-  `2010/12/2852/`, `2025/11/the-scip-optimization-suite-10-0/` and
-  `2026/04/sequential-nonlinear-programming-approach-to-thermal-aware-vlsi-floorplanning-using-multi-boundary-shapes/`
-  for their `Published:`/`Updated:`/`Categories`/`Citation`/`Short URL` fields. Retrieved
-  2026-09-01. **[API]/[WEB]**
-- **S5** — `https://optimization-online.org/submit/` — the *Moderation* and *Copyright*
-  sections quoted verbatim in §4 and §9. Retrieved 2026-09-01. **[DOC]**
-- **S6** — arXiv API,
-  `https://export.arxiv.org/api/query?search_query=cat:math.OC&start=0&max_results=1`,
-  reading `<opensearch:totalResults>` = **63,892**. Retrieved 2026-09-01. **[API]**
-- **S7** — Live HTTP probes, 2026-09-01: `/robots.txt` (200, 124 B, quoted); `/wp-sitemap.xml`
-  (200); `/oai` and `/oai2` (both 404); the five old-style URL redirect chains and the
-  `?p=9506` short URL in §8; the real PDF `wp-content/uploads/2004/03/836.pdf` (200,
-  333,438 B, `application/pdf`); and the four negative controls
-  (`/this-page-does-not-exist-zzz9999/`, `DB_HTML/1999/99/999999.html`,
-  `DB_HTML/2000/09/1.html`, `wp-content/uploads/2004/03/999999.pdf`). **[WEB]**
-- **S8** — `https://api.openalex.org/sources?filter=display_name.search:Optimization%20Online`
-  (`meta.count = 0`); Wikipedia REST
-  `https://en.wikipedia.org/api/rest_v1/page/summary/Optimization_Online` (internal error).
-  Retrieved 2026-09-01. **[API]**
diff --git a/research/preprint-repositories/osf-preprints.md b/research/preprint-repositories/osf-preprints.md
deleted file mode 100644
index 3181e6a..0000000
--- a/research/preprint-repositories/osf-preprints.md
+++ /dev/null
@@ -1,598 +0,0 @@
-# OSF Preprints — preprint repository record
-
-- **URL:** https://osf.io/preprints/ · API root https://api.osf.io/v2/
-- **Operator:** Center for Open Science (COS), Charlottesville, Virginia — a US 501(c)(3)
-  non-profit. COS builds and runs the infrastructure; the individual *preprint services*
-  are branded and moderated by outside research communities (S6, S9).
-- **Discipline scope:** advertised as multidisciplinary — *as actually used*, overwhelmingly
-  psychology, sociology, education and the social sciences (§2, §3). Engineering and
-  computing presence is marginal and shrinking (§7).
-- **Launched:** **2016** — COS's own retrospective dates the OSF Preprints service to 2016
-  (S6) [DOC]; the oldest live record on the platform is 2016-07-13 (S1) [API]. Wikipedia
-  gives 2017 (S10).
-- **Status:** **active, but contracting.** The generalist server has been **closed to new
-  submissions since 2025-08-25** (S6, S7) and Thesis Commons since **2026-06-03** (S1).
-  18 of 32 providers no longer accept submissions (§3.2).
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Why this record exists.** A large fraction of the entries in Wikipedia's *List of
-> preprint repositories* — AfricArXiv, AgriXiv, Arabixiv, BioHackrXiv, BodoArXiv,
-> EarthArXiv, EcoEvoRxiv, ECSarXiv, EdArXiv, engrXiv, Frenxiv, INA-Rxiv, IndiaRxiv,
-> LawArXiv, LISSA, MarXiv, MediArXiv, MetaArXiv, MindRxiv, NutriXiv, PaleorXiv, PsyArXiv,
-> SocArXiv, SportRxiv, Thesis Commons — are or were **the same piece of software with
-> different logos**. They are not independent repositories. This record documents the
-> substrate once, with measured numbers, so the other records can point here instead of
-> repeating themselves. §3.2 is the payload.
-
----
-
-## 1. What it is
-
-The **Open Science Framework (OSF)** is a research-workflow platform: project pages, file
-storage, version control, preregistrations, registrations and — since 2016 — preprints. It
-is free at the point of use and funded by philanthropy, grants, and institutional/community
-memberships. **OSF Preprints** is the preprint module of that platform.
-
-The design idea is *white-labelling*. COS wrote one preprint service and then let outside
-communities rent a branded instance of it. In COS's own words the service "was built in two
-parts": **community-run preprint servers**, where "COS developed infrastructure that can be
-customized and operated by research communities themselves … [allowing] research
-communities to set their own standards, build norms for open sharing, and reduce redundant
-development costs"; and a **generalist server**, "a multidisciplinary venue that accepts
-submissions from any domain of scholarship … managed and moderated directly by COS staff"
-(S6) [DOC].
-
-That is why `psyarxiv.com`, `engrxiv.org` and `ecsarxiv.org` all looked identical in 2019:
-they were the same Ember front end reading the same Django API, with a different logo,
-colour scheme and moderator pool. Each got a slug — `psyarxiv`, `engrxiv`, `ecsarxiv` — and
-a landing page at `osf.io/preprints/<slug>`. The community supplied volunteer moderators and
-an advisory board; COS supplied everything else.
-
-For a reader of this knowledge base the consequences are practical and mostly unwelcome:
-
-- **A citation to `osf.io/preprints/<slug>/<guid>` has a single point of failure.** If COS
-  changes strategy — and it has (§4) — every server on the platform is affected at once.
-- **The branded vanity domains are the fragile part.** `engrxiv.org`, `eartharxiv.org`,
-  `arabixiv.org` and others now point somewhere else entirely, because the *community*
-  moved and took the domain with it while the *content* stayed on OSF (§3.3).
-- **"OSF Preprints" is not one repository with 200,000 papers.** It is 32 separate
-  collections, of which two (PsyArXiv and the generalist server) hold **70.6%** of
-  everything (§3.1) [API].
-
-## 2. Scope and subject taxonomy
-
-OSF has no arXiv-style category codes. There is no `cs.DC` equivalent. The only structural
-axes are:
-
-**(a) Provider.** The 32 slugs in §3.2. This is the real taxonomy, and it is a taxonomy of
-*communities*, not of subjects.
-
-**(b) `subjects`** — a bibliographic subject tree (bepress-derived) attached per preprint.
-It is coarse and optional-in-practice; it is not usable as a discipline filter with any
-precision. `/v2/preprints/?filter[provider]=X` is reliable; subject filtering is not, and
-this record does not use it.
-
-**(c) Free-text tags** — uncontrolled.
-
-For computing and electronics, the honest statement is: **OSF Preprints has no computing
-taxonomy and essentially no computing community.** ECSarXiv (electrochemistry/solid-state)
-and the frozen engrXiv archive are the only two providers with any engineering content at
-all, and between them they hold 2,356 records — 1.2% of the platform (§3.2, §7) [API].
-
-## 3. Size and growth
-
-### 3.1 Headline
-
-Retrieved 2026-09-01 from `https://api.osf.io/v2/preprints/?page[size]=1` (S1) [API]:
-
-- **200,519** preprint records across all providers.
-- Summing the 32 per-provider counts in §3.2 gives **exactly 200,519** — the per-provider
-  filter partitions the corpus with no overlap and no unassigned remainder. That is a
-  useful internal consistency check and it passed.
-- The two largest providers — the generalist `osf` server (78,195) and PsyArXiv (63,368) —
-  hold **141,563 records, 70.6% of the total** [INF, from S1].
-
-**Counting caveat — records are versions, not works.** Since OSF added preprint versioning,
-each revision becomes its own record with its own GUID suffix (`qa4sz_v2`, `qa4sz_v3`) and
-each is counted separately by `meta.total`. Measured by full enumeration, 2026-09-01 (S1)
-[API]:
-
-| Provider | Records (`meta.total`) | Distinct base GUIDs | Inflation |
-|---|---|---|---|
-| ECSarXiv | 323 | 318 | +1.6% |
-| LISSA | 335 | 325 | +3.1% |
-| BioHackrXiv | 173 | 163 | +6.1% |
-| Accounting Research & Thought | 6 | 4 | +50% |
-
-The effect is small in aggregate because versioning is recent: of the **300 oldest** records
-on each of PsyArXiv, SocArXiv and the generalist server, **300/300 were `_v1`** — but of the
-**100 newest** generalist-server records, only **6 were `_v1`** and the rest were revisions
-up to `_v30` (S1) [API]. Treat every count in §3.2 as *records*, an upper bound on *works*,
-with a few percent of slack.
-
-### 3.2 The provider table — every COS-hosted preprint service, measured
-
-Authoritative provider list from `https://api.osf.io/v2/preprint_providers/?page[size]=100`
-(`meta.total = 32`, one page, no pagination needed) (S2) [API]. Counts, earliest and latest
-record dates from `https://api.osf.io/v2/preprints/?filter[provider]=<slug>` with
-`sort=date_created` / `sort=-date_created`, all retrieved **2026-09-01** (S1) [API].
-"Open?" is the API's own `allow_submissions` flag.
-
-| # | Slug | Display name | Discipline (operator's own words, S2) | Records | Earliest | Latest | Moderation | Open? |
-|---|---|---|---|---|---|---|---|---|
-| 1 | `osf` | Open Science Framework (generalist) | any domain of scholarship | **78,195** | 2016-08-29 | 2026-09-01 | COS staff | **no** (susp. 2025-08-25) |
-| 2 | `psyarxiv` | PsyArXiv | psychological sciences | **63,368** | 2016-08-15 | 2026-09-01 | pre | yes |
-| 3 | `socarxiv` | SocArXiv | social sciences | **24,670** | 2016-07-13 | 2026-08-31 | pre | yes |
-| 4 | `inarxiv` | INA-Rxiv | Indonesian research (all fields) | **15,987** | 2017-08-20 | 2020-08-17 | pre | no (closed 2020-10-07) |
-| 5 | `edarxiv` | EdArXiv | education research | **3,506** | 2019-02-18 | 2026-08-29 | pre | yes |
-| 6 | `thesiscommons` | Thesis Commons | theses and dissertations | **2,866** | 2017-04-21 | 2026-08-27 | none set | no (susp. 2026-06-03) |
-| 7 | `engrxiv` | engrXiv (Engineering Archive) | engineering | **2,033** | 2016-07-27 | 2022-01-19 | pre | no (moved 2022-01-19) |
-| 8 | `lawarchive` | Law Archive | legal scholarship | **1,664** | 2016-07-28 | 2026-08-27 | pre | yes |
-| 9 | `eartharxiv` | EarthArXiv | earth science | **1,649** | 2017-10-23 | 2020-09-01 | pre | no (moved to CDL) |
-| 10 | `metaarxiv` | MetaArXiv | research transparency & reproducibility | **1,014** | 2017-03-03 | 2026-08-31 | pre | yes |
-| 11 | `ecoevorxiv` | EcoEvoRxiv | ecology & evolutionary biology | **909** | 2018-03-21 | 2022-09-30 | pre | no (moved to CDL) |
-| 12 | `africarxiv` | AfricArXiv | African research | **479** | 2018-06-22 | 2024-04-07 | pre | no |
-| 13 | `marxiv` | MarXiv | marine & conservation science | **454** | 2017-11-09 | 2025-08-12 | post | no |
-| 14 | `mediarxiv` | MediArXiv | media, film & communication studies | **443** | 2019-02-02 | 2026-08-19 | pre | yes |
-| 15 | `agrixiv` | AgriXiv | agriculture & allied sciences | **397** | 2017-02-15 | 2020-05-18 | pre | no (moved to agriRxiv) |
-| 16 | `sportrxiv` | SportRxiv | sport, exercise, performance, health | **377** | 2017-08-18 | 2021-08-18 | pre | no |
-| 17 | `lissa` | LIS Scholarship Archive | library & information science | **335** | 2017-07-12 | 2025-12-04 | post | no |
-| 18 | `ecsarxiv` | ECSarXiv | electrochemistry & solid state science | **323** | 2018-05-09 | 2026-08-22 | pre | yes |
-| 19 | `arabixiv` | Arabixiv | Arabic-language research | **298** | 2018-01-14 | 2020-12-11 | pre | no (moved to Zenodo) |
-| 20 | `mindrxiv` | MindRxiv | mind & contemplative practices | **288** | 2017-07-07 | 2024-12-20 | pre | no |
-| 21 | `paleorxiv` | PaleorXiv | paleontology | **282** | 2017-08-18 | 2026-08-30 | pre | yes |
-| 22 | `biohackrxiv` | BioHackrXiv | biohackathon reports | **173** | 2020-02-17 | 2026-08-26 | pre | yes |
-| 23 | `bodoarxiv` | BodoArXiv | medieval studies | **165** | 2019-03-19 | 2026-08-22 | pre | yes |
-| 24 | `lawarxiv` | LawArXiv | legal scholarship (superseded) | **165** | 2016-07-16 | 2025-05-14 | none set | no |
-| 25 | `frenxiv` | Frenxiv | French-language research | **128** | 2018-07-06 | 2020-12-31 | pre | no |
-| 26 | `indiarxiv` | IndiaRxiv | Indian research | **121** | 2019-06-10 | 2020-12-28 | pre | no |
-| 27 | `nutrixiv` | NutriXiv | nutritional sciences | **85** | 2017-08-24 | 2024-11-29 | post | no |
-| 28 | `focusarchive` | FocUS Archive | focused-ultrasound research | **84** | 2017-09-20 | 2026-08-07 | pre | yes |
-| 29 | `coppreprints` | CoP (College of Phlebology) | venous diseases | **48** | 2022-10-24 | 2026-08-04 | pre | yes |
-| 30 | `newaddictionsx` | NewAddictionsX | new & emerging addictions | **7** | 2024-08-16 | 2025-11-17 | pre | yes |
-| 31 | `acctrt` | Accounting Research & Thought | accounting research | **6** | 2026-03-27 | 2026-06-10 | pre | yes |
-| 32 | `livedata` | Research AZ | Arizona institutions | **0** | — | — | none set | no |
-
-**32 rows. Total 200,519 records.**
-
-Derived facts [INF, from S1/S2]:
-
-- **14 providers accept submissions; 18 do not.** The 14 open ones match exactly the count
-  COS gave in its August 2025 announcement — "the 14 community-run preprint servers running
-  on the OSF Preprints service" (S6) [DOC]. Independent confirmation of a documented figure
-  by API measurement; this is as good as evidence gets here.
-- COS's own help page *Preprint services hosted by OSF* lists **13** (S8, last updated
-  2026-07-23) [DOC] — it omits `acctrt`, which was created 2026-03-27 and has 6 records.
-  The help page lags the API. Prefer the API.
-- **9 providers have received nothing since 2022** (`agrixiv`, `arabixiv`, `eartharxiv`,
-  `ecoevorxiv`, `engrxiv`, `frenxiv`, `inarxiv`, `indiarxiv`, `sportrxiv`) [INF].
-- **`livedata` / "Research AZ" is an empty branded shell** — HTTP 200 landing page, zero
-  records. A live demonstration of why "N preprint servers exist" is a meaningless statistic
-  (§8 negative controls) [API].
-- The median provider holds **~300 records**. Wikipedia's ">100" and ">1,000" buckets for
-  these servers are technically true and informationally worthless.
-
-### 3.3 Providers that left the platform (content stayed, community went)
-
-Read from each provider's `description` field in the API, 2026-09-01 (S2) [DOC via API]:
-
-| Provider | What the OSF landing page now says | Destination |
-|---|---|---|
-| engrXiv | "will be closed to new preprint submissions temporarily and moved to https://engrxiv.org/ beginning Wednesday, January 19th" | self-hosted Janeway at `engrxiv.org` |
-| EarthArXiv | "is now hosted by the California Digital Library (CDL). The EarthArXiv.org URL now redirects to the CDL Janeway platform. All article DOIs will redirect to CDL" | CDL Janeway |
-| EcoEvoRxiv | "Submissions are currently suspended. EcoEvoRxiv.org is moving to the Janeway platform hosted by the California Digital Library (CDL)" | CDL Janeway |
-| AgriXiv | "is moving to agriRxiv and is no longer accepting submissions" | `agrirxiv.org` |
-| Arabixiv | "has moved to a new address and accepts submissions through its new platform at: zenodo.org/communities/arabixiv" | Zenodo community |
-| INA-Rxiv | "With a heavy heart, we close the INArxiv service starting October 7, 2020" | closed outright |
-| Frenxiv, IndiaRxiv, LawArXiv, LISSA, MindRxiv, NutriXiv, SportRxiv | "no longer able to accept new submissions. Existing content … will remain accessible as part of COS's ongoing commitment to Open Science" | nowhere — frozen in place |
-
-The last row is the important one. Seven servers share **verbatim identical wind-down
-boilerplate**, which tells you the decision was made centrally by COS, not by seven
-independent communities. The `latest` dates in §3.2 cluster in **December 2020** for four
-of them (`frenxiv` 2020-12-31, `indiarxiv` 2020-12-28, `arabixiv` 2020-12-11) — a single
-coordinated cut, not seven separate community deaths [INF].
-
-## 4. The 2025–2026 COS strategy change — verified
-
-This is current and it is the most consequential thing in this record.
-
-**What actually happened, in order:**
-
-1. **2024** — COS introduced preprint moderation across the service. Stated in COS's own
-   2025 announcement: "COS introduced preprint moderation in 2024" (S6) [DOC].
-2. **2025-08-21** — COS published *"Suspension of Submissions to Generalist Preprint Server
-   for Review and Next Steps — Community Servers Hosted by OSF Preprints Remain Active"*
-   (S6) [DOC].
-3. **2025-08-25** — effective date. Submissions to the **generalist server only** were
-   suspended. The help-centre article confirms: "Effective 8/25/2025, we will be temporarily
-   suspending submissions to the generalist server hosted on OSF Preprints" (S7) [DOC].
-4. **2026-04-21** — the help-centre article's last-updated date. Still described as a
-   suspension; **no resumption and no closure has been announced as of 2026-09-01** (S7)
-   [DOC]. Thirteen months of "temporary".
-5. **2026-06-03** — separately, **Thesis Commons** suspended submissions: "Effective June 3,
-   2026, we will suspend submissions to the Thesis Commons paper service. This does not
-   affect the other community-run preprint services hosted by OSF Preprints." (S2, provider
-   description) [DOC].
-
-**COS's stated reasons** (S6, quoted) [DOC]:
-
-- *Volume and quality*: "The generalist server has seen increasing numbers of suspicious or
-  low-quality submissions … trends such as generative AI and paper mills have introduced new
-  risks to research integrity. We hypothesize that this server is a particularly attractive
-  target for misuse because of its broad acceptance guidelines."
-- *Moderation breadth and sustainability*: "moderating a generalist server requires expertise
-  across every field of research, a scale beyond our current capacity."
-- *Strategic alignment*: "COS is reviewing how the generalist server fits into the long-term
-  vision for OSF."
-
-**What was explicitly NOT affected** (S6, S7) [DOC]: existing preprints remain available;
-authors can still revise them; the 14 community servers remain open. This is corroborated by
-measurement — the generalist server's most recent records are dated 2026-09-01, but of the
-100 newest, only 6 have `_v1` GUIDs; the rest are revisions (`_v2` … `_v30`) of preprints
-deposited before the cut (S1) [API]. **The API's `latest` date for `osf` is a revision date,
-not a submission date.** Anyone reading that column without checking GUID suffixes would
-wrongly conclude the generalist server is still accepting work.
-
-**Correcting the framing in the assignment.** The premise that "COS announced it was winding
-down or handing off hosting for community preprint servers" is **not what the record shows**.
-COS's 2025 announcement says the opposite in its own headline: *"Community Servers Hosted by
-OSF Preprints Remain Active"* (S6) [DOC]. What is verifiable is:
-
-- COS suspended **its own** generalist server, and later Thesis Commons.
-- Separately and *earlier* (2020–2022), a wave of **communities** left the platform of their
-  own accord — engrXiv and EcoEvoRxiv to CDL's Janeway, EarthArXiv to CDL, AgriXiv to
-  agriRxiv, Arabixiv to Zenodo (§3.3) [DOC via API].
-- Separately again, COS froze a group of small servers with identical boilerplate (§3.3).
-
-Three distinct phenomena over six years, with different causes. Conflating them into "COS is
-winding down preprint hosting" would be wrong. The defensible summary is: **the platform is
-contracting at both ends — COS shed the hardest-to-moderate service it owned, and the
-best-resourced communities took their servers elsewhere — while a stable core of ~14
-social-science-flavoured servers continues.** [INF]
-
-**Not verified:** whether COS has an internal end-date for the generalist server; whether
-the review announced in August 2025 has concluded; whether any further servers are scheduled
-to close. No public document dated after 2026-07-23 was found.
-
-## 5. Screening and moderation — what gets in
-
-**The model.** Each provider independently sets `reviews_workflow` to one of three values,
-readable from the API (S2) [API]:
-
-| `reviews_workflow` | Meaning | Providers |
-|---|---|---|
-| `pre-moderation` | submission sits **private and pending** until a moderator accepts or rejects | 26 of 32 |
-| `post-moderation` | appears immediately, may be withdrawn afterwards | 3 — `lissa`, `marxiv`, `nutrixiv` |
-| `null` (none set) | no moderation workflow configured | 4 — `osf`, `lawarxiv`, `livedata`, `thesiscommons` |
-
-**How to tell which applies to a given server — the reliable method.** Do not trust the
-landing page. Query:
-
-```
-https://api.osf.io/v2/preprint_providers/<slug>/
-```
-
-and read `data.attributes.reviews_workflow`. This is the value the software actually
-enforces. (The deprecated `/v2/preprint_providers/` route still works and is what §3.2 was
-built from; the current route is `/v2/providers/preprints/`, which returns the identical
-32-item list — verified 2026-09-01, both `meta.total = 32` (S2, S3) [API].)
-
-**The published policy.** COS's help centre states: "Preprint servers are pre-moderation
-services, where submissions are in a private, pending state until a moderator accepts or
-rejects them. Authors are given notice of reasoning behind any preprints that are rejected."
-(S9, last updated 2026-08-14) [DOC]. Note this is a generalisation that the API contradicts
-for 6 of 32 providers — another reason to read the API rather than the prose.
-
-**Platform-wide rules** (S9, verbatim) [DOC]:
-
-- "Content completely or mostly generated by large language model (LLM) tools or other
-  artificial intelligence (AI) tools is not appropriate for OSF Preprints."
-- "Content should be original content created by the user, or posted with explicit
-  permission and appropriate attribution of the content creator."
-- "Organizations should not use OSF user accounts to act as publication aggregates,
-  clearinghouses, or DOI minting services."
-
-The anti-LLM clause is dated — the help page's last-updated stamp is 2026-08-14 — and is
-directly downstream of the paper-mill problem that killed the generalist server (§4).
-
-**Provider-specific policies** exist for PsyArXiv, SocArXiv and MetaArXiv and are linked
-from S9. SocArXiv's is the most developed: its landing page says "SocArXiv papers are
-moderated before appearing. Please read the moderation policy before submitting"
-(S2) [DOC].
-
-**What moderation is not.** It is a screen for scope, plausibility, plagiarism and
-obvious junk, applied by volunteers from the relevant community. It is not peer review, it
-does not check methods, and it does not check numbers. COS says so itself in describing the
-generalist server's failure: moderation "requires expertise across every field of research"
-and COS did not have it (S6) [DOC].
-
-## 6. Reliability — what you can and cannot trust
-
-**What a deposit here guarantees:**
-
-- A stable OSF GUID and a resolvable URL at `osf.io/preprints/<slug>/<guid>`.
-- Usually, but **not always**, a DOI (see below).
-- That *a* human looked at it, on 26 of 32 providers.
-- Nothing about correctness.
-
-**DOI coverage is materially incomplete, and getting worse.** Measured by full enumeration
-and by sampling, 2026-09-01, reading `attributes.preprint_doi_created` (S1) [API]:
-
-| Provider | Records with a minted preprint DOI |
-|---|---|
-| ECSarXiv (all 323) | 281 (87.0%) |
-| LISSA (all 335) | 321 (95.8%) |
-| BioHackrXiv (all 173) | 138 (79.8%) |
-| Accounting Research & Thought (all 6) | **0** |
-| PsyArXiv — 50 oldest | 50/50 |
-| PsyArXiv — 50 newest | **0/50** |
-| SocArXiv — 50 oldest | 50/50 |
-| SocArXiv — 50 newest | **0/50** |
-| generalist `osf` — 50 oldest | 50/50 |
-| generalist `osf` — 50 newest | **0/50** |
-| engrXiv — 50 oldest **and** 50 newest | **0/50 and 0/50** |
-
-Two separate effects, and they should not be confused:
-
-1. **Recent records have no DOI yet.** Every "50 newest" sample returned zero. Spot check:
-   ECSarXiv preprint `nbjcm_v1`, deposited 2026-08-22, published 2026-08-23,
-   `reviews_state: accepted`, `is_published: true` — and
-   `https://api.osf.io/v2/preprints/nbjcm/identifiers/` returns `{"data": []}`. **A live,
-   accepted, published OSF preprint with no identifier of any kind** (S1) [API]. Whether
-   this is a minting backlog or a policy change is **[NOT-VERIFIED]** — I found no COS
-   statement either way. Either reading is bad for citation durability.
-2. **engrXiv never had OSF DOIs at all**, at either end of its life — consistent with its
-   DOIs having been minted and now redirected elsewhere, as EarthArXiv's landing page
-   explicitly says happened for that server (§3.3) [INF].
-
-**Practical rule: do not assume an OSF preprint has a DOI. Check
-`/v2/preprints/<guid>/identifiers/` before you cite one, and if it is empty, cite the GUID
-URL and archive the PDF yourself.**
-
-**Known failure modes:**
-
-- **Paper-mill and LLM-generated content on the generalist server.** Not a rumour — COS
-  named it as the reason for suspension (S6) [DOC]. Any generalist-server preprint deposited
-  before 2025-08-25 comes from a corpus its own operator judged to be under sustained
-  abuse.
-- **Fringe physics and metaphysics.** Visible in the raw feed: the newest generalist-server
-  records on 2026-09-01 include "The Ontological Origin of the Universe and Maximal
-  Existence" (`ms7rp_v2`), "The Single Pole Battery: a Relativistic Understanding …"
-  (`skphf_v8`, on its **eighth** revision) and "CMB, Cosmological Redshift, and Wien's Law"
-  (`qa4sz_v3`) (S1) [API]. These are revisions, so the suspension does not stop them
-  accumulating.
-- **Revision churn as a signal.** `_v8`, `_v21`, `_v28`, `_v30` suffixes appear in the
-  newest-100 sample of the generalist server (S1) [API]. A preprint on its thirtieth version
-  with no journal outcome is not a manuscript under improvement.
-- **Community abandonment.** Nine providers have taken nothing since 2022 (§3.2). Their
-  moderator pools are gone; nobody is watching the content that is already there.
-
-**How to sanity-check an individual OSF preprint:**
-
-1. `GET https://api.osf.io/v2/preprints/<guid>/` — check `provider` (which community?),
-   `reviews_state` (should be `accepted`), `is_published`.
-2. `GET .../identifiers/` — is there a DOI at all?
-3. Check the provider's `reviews_workflow` (§5). `null` or `post-moderation` means nothing
-   necessarily blocked it.
-4. Check `original_publication_date` / `custom_publication_citation` — if populated, the
-   work exists elsewhere and you should cite that.
-5. Check the GUID suffix. `_v1` is an original deposit; `_v14` is something else.
-
-**Eventual-publication rate: [NOT-VERIFIED].** I found no measurement of OSF-Preprints
-publication rates in the time available. Do not assume the arXiv or bioRxiv figures
-transfer.
-
-## 7. Computing and engineering relevance — very little, and say so
-
-**There is almost nothing here for a hardware or software engineer.** Concretely:
-
-- **ECSarXiv** (`ecsarxiv`, 323 records, still open) — electrochemistry and solid-state
-  science, run in association with The Electrochemical Society. Battery, fuel-cell,
-  electrodeposition and semiconductor-materials work. The single OSF provider with genuine
-  electronics-adjacent content. It has its own record in this collection
-  ([ecsarxiv.md](ecsarxiv.md)); this record supplies the platform context.
-- **engrXiv** (`engrxiv`, 2,033 records, **frozen since 2022-01-19**) — the Engineering
-  Archive. The OSF-hosted archive is a historical snapshot; the live service moved to
-  `engrxiv.org` on Janeway. See [engrxiv.md](engrxiv.md).
-- **BioHackrXiv** (`biohackrxiv`, 173 records, open) — biohackathon project reports.
-  Bioinformatics tooling, workflow languages, data-format work. Software, but life-science
-  software. See [biohackrxiv.md](biohackrxiv.md).
-- **MetaArXiv** (`metaarxiv`, 1,014 records, open) — reproducibility and research
-  transparency, run by the Berkeley Initiative for Transparency in the Social Sciences.
-  Occasionally relevant to research-software engineering practice.
-- **LISSA** (`lissa`, 335 records, frozen) — library and information science; information
-  retrieval and repository software at the margins. Covered in
-  [library-science-and-cognitive-archives.md](library-science-and-cognitive-archives.md).
-
-That is the whole of it: **2,356 records across ECSarXiv and engrXiv, 1.2% of the
-platform**, and 86% of that is a frozen archive [INF, from S1].
-
-The generalist server does receive occasional engineering-flavoured deposits — the ECSarXiv
-example above, `nbjcm`, is a solar-PV/BESS/EVSE sizing framework citing NEC 690.7, IEEE
-Std 485 and NREL PVWatts (S1) [API] — but these are isolated, unmoderated-by-domain-experts,
-and now cut off at the source.
-
-**If you are looking for computing preprints, this is the wrong platform.** Use arXiv
-(`cs.*`, `eess.*`), the [Cryptology ePrint Archive](cryptology-eprint-archive.md), or
-[TechRxiv](techrxiv.md).
-
-**No landmark-papers table.** OSF Preprints does not host foundational work in software,
-distributed systems, databases, electronics or security. I could not identify a single
-paper in these areas that appeared on OSF Preprints first and became significant. Stating
-that plainly is more useful than padding a table.
-
-## 8. Access, APIs and bulk retrieval
-
-**The REST API is the reason this record has real numbers.** It is public, unauthenticated
-for reads, JSON:API-formatted, and it was not rate-limited during roughly 200 sequential
-requests on 2026-09-01.
-
-| Endpoint | Purpose | Verified 2026-09-01 |
-|---|---|---|
-| `https://api.osf.io/v2/providers/preprints/?page[size]=100` | current provider list | 200, `meta.total = 32` (S3) [API] |
-| `https://api.osf.io/v2/preprint_providers/?page[size]=100` | **deprecated** provider list | 200, `meta.total = 32`, warns "This route is deprecated and will be unavailable after version 2.7" (S2) [API] |
-| `https://api.osf.io/v2/preprints/?filter[provider]=<slug>&page[size]=1` | per-provider count in `links.meta.total` | 200 for all 32 (S1) [API] |
-| `https://api.osf.io/v2/preprints/?filter[provider]=<slug>&sort=date_created` | oldest first | 200 (S1) [API] |
-| `https://api.osf.io/v2/preprints/<guid>/identifiers/` | DOI, if any | 200, `data: []` when none (S1) [API] |
-| `https://api.osf.io/v2/preprint_providers/<slug>/licenses/` | permitted licences | 200 (S1) [API] |
-| `https://api.osf.io/v2/search/preprints/?q=…` | — | **404** — does not exist (S1) [API] |
-
-Square brackets must be percent-encoded or curl must be given `-g`; unencoded `[` produces
-`curl: (3) bad range in position …`, which is a client error, not a server response.
-
-**Negative controls — read this before trusting any OSF probe.**
-
-| Probe | Result | Lesson |
-|---|---|---|
-| `https://osf.io/preprints/` | HTTP 200, **4,207 bytes** | the SPA shell |
-| `https://osf.io/preprints/ecsarxiv` (real) | HTTP 200, **4,207 bytes** | identical to the shell |
-| `https://osf.io/preprints/notarealslugxyzzy999` (bogus) | HTTP 200, **4,207 bytes** | **byte-identical to the real provider — web URLs cannot distinguish a real provider from a fake one.** Directly verified here, 2026-09-01 (S1) [WEB] |
-| `https://api.osf.io/v2/preprints/?filter[provider]=notarealprovider999` | HTTP **200**, body 127 bytes, `{"data":[],"links":{"meta":{"total":0}}}` | **an invalid provider slug returns a clean zero, indistinguishable from a genuinely empty provider** |
-| `https://help.osf.io/article/999999-this-does-not-exist-xyzzy` | HTTP **404**, 15,028 bytes | the help centre, at least, 404s honestly |
-
-The middle two are the trap. `livedata` returns `total: 0` and so does `notarealprovider999`.
-The **only** way to know a slug is real is that it appears in the provider list (S2/S3) —
-which is why §3.2 was built from the provider list first and counts second, not the other
-way round.
-
-**OAI-PMH:** OSF does not advertise an OAI-PMH endpoint for preprints. **[NOT-VERIFIED]** —
-I did not exhaustively probe candidate paths.
-
-**SHARE / trove.** `https://share.osf.io/` returns HTTP 200 and is alive, but is no longer
-the preprint aggregator it was. It now serves a linked-data "trove" index-card search
-(`/trove/index-card-search`, `/trove/browse`, `/trove/docs`) returning JSON-LD; a filtered
-query for `resourceType=Preprint` returned `totalResultCount: {"@id":
-"trove:ten-thousands-and-more"}` — a *bucketed* answer, not a number (S4) [API]. The old
-faceted discovery UI is gone: `https://osf.io/preprints/discover` now **302s to
-`https://osf.io/search?q=&resourceType=Preprint`** (S1) [WEB], OSF's own search, scoped to
-OSF's own content. Note that every Wikipedia citation for OSF-hosted server sizes points at
-`osf.io/preprints/<slug>/discover` URLs (S10) — **those URLs no longer resolve to what the
-citation claims they showed.**
-
-**Bulk:** no dump. Paginate at `page[size]=100` (the maximum honoured); full enumeration of a
-300-record provider takes 4 requests and a couple of seconds.
-
-## 9. Licensing and reuse
-
-`https://api.osf.io/v2/preprint_providers/osf/licenses/` returns `meta.total = 2`
-(S1, 2026-09-01) [API]:
-
-- **CC-BY 4.0**
-- **CC0 1.0**
-
-Two options, both open, author's choice, no all-rights-reserved default. This is materially
-better than SSRN (see [ssrn.md](ssrn.md)) and better than most commercial hosts. Note that
-the licence list is *per provider* — the endpoint above is for the generalist server; a
-given community server may offer a different set, so query the endpoint for the slug you
-care about.
-
-Text and data mining of the API is not blocked and is evidently tolerated (§8).
-
-## 10. Caveats and controversies
-
-1. **The Wikipedia numbers do not survive contact with the API — and the conflict is
-   structural, not a typo.** Wikipedia's list gives OSF Preprints ">1,000,000", with the
-   prose "Aggregates over 30 preprint servers (all from COS plus other like arXiv, bioRxiv,
-   etc.). Number of native OSF Preprints documents: 25,114." (S10) [WEB]. Unpacking that:
-
-   - **(a) Natively deposited on COS-hosted providers: 200,519 records** across 32
-     providers, 2026-09-01 (S1) [API]. This is the only number in the vicinity that is both
-     meaningful and measurable.
-   - **(b) Merely indexed/harvested from elsewhere:** the ">1,000,000" figure came from the
-     **SHARE-backed `osf.io/preprints/discover` search**, which used to federate metadata
-     from arXiv, bioRxiv, PeerJ, Preprints.org, RePEc and Cogprints alongside OSF's own
-     content. The evidence that this is what the number meant is still in the API: the
-     deprecated `/v2/preprint_providers/` route returns a `meta.whitelisted_providers` array
-     containing exactly **`["arXiv", "bioRxiv", "Preprints.org", "PeerJ", "Cogprints",
-     "Research Papers in Economics"]`** (S2) [API] — six external sources, harvested, never
-     hosted. **Those records were never on OSF.** A million-strong "OSF Preprints" was
-     always mostly arXiv wearing an OSF search box.
-   - **(c) "Over 30 preprint servers"** is coincidentally close to right for the wrong
-     reason: there are **32 COS-hosted providers** (S2) [API], not "30 servers including
-     arXiv and bioRxiv". Wikipedia conflates the hosted set with the harvested set.
-   - **(d) "25,114 native documents"** is undated in the source and I could not reproduce it
-     from any current endpoint. It is plausibly a snapshot of the generalist `osf` provider
-     alone circa 2020–2021 (now 78,195) [INF, NOT-VERIFIED].
-   - **Conclusion, stated plainly:** the ">1,000,000" and the "25,114" are not two views of
-     the same thing and neither is currently true. The defensible 2026 figure is **200,519
-     records natively hosted across 32 COS providers**, of which 70.6% sit in two of them,
-     and 18 of which are closed. I am recording the conflict rather than resolving it in
-     Wikipedia's favour; the harvested-vs-hosted distinction is the actual finding.
-
-2. **Wikipedia lists the same infrastructure ~25 times.** Reading the list, OSF-hosted
-   servers look like two dozen independent institutions. They are one Django application.
-   Diversity of logos is not diversity of infrastructure, and the correlated-failure risk is
-   exactly as bad as it sounds — §4 shows two services closing on one operator's decision.
-
-3. **Vanity-domain rot.** `engrxiv.org`, `eartharxiv.org`, `arabixiv.org`, `psyarxiv.com`
-   and others are community-controlled, not COS-controlled. When a community leaves, the
-   domain leaves with it and the OSF content stays behind. **A link to a vanity domain and a
-   link to `osf.io/preprints/<slug>` can point at different corpora.** Always record the
-   `osf.io` GUID.
-
-4. **Wikipedia's own citations are dead URLs.** Every OSF-server size claim in the list cites
-   `osf.io/preprints/<slug>/discover` (S10); those paths now redirect to a generic OSF search
-   (§8). The citations cannot be checked as written.
-
-5. **The generalist server is a corpus under acknowledged abuse.** COS says so (S6). Treat
-   pre-2025 generalist-server deposits accordingly, and note that revisions to them continue
-   to appear with 2026 dates.
-
-6. **DOI minting has stopped, or stalled, on recent deposits** (§6). Unexplained, and it is
-   the single most citation-relevant thing on this page.
-
-7. **The API route you are using is deprecated.** `/v2/preprint_providers/` warns it "will be
-   unavailable after version 2.7" (S2) [API]. Scripts built on it — including the one that
-   produced §3.2 — will break. `/v2/providers/preprints/` is the replacement and returns the
-   same 32 (S3) [API].
-
-## 11. Sources
-
-- **S1** — OSF REST API v2, `https://api.osf.io/v2/preprints/` with `filter[provider]`,
-  `sort`, `page[size]` parameters; plus `/v2/preprints/<guid>/identifiers/`,
-  `/v2/preprint_providers/osf/licenses/`. Retrieved 2026-09-01. Supports: all counts,
-  earliest/latest dates, DOI coverage, version-inflation measurements, licence list,
-  negative controls, the `osf.io/preprints/discover` redirect.
-- **S2** — `https://api.osf.io/v2/preprint_providers/?page[size]=100`. Retrieved 2026-09-01.
-  `meta.total = 32`. Supports: the provider list, display names, descriptions,
-  `reviews_workflow`, `allow_submissions`, the deprecation warning, and the
-  `meta.whitelisted_providers` array naming the six externally harvested sources.
-- **S3** — `https://api.osf.io/v2/providers/preprints/?page[size]=100` (current route).
-  Retrieved 2026-09-01. `meta.total = 32`. Corroborates S2.
-- **S4** — `https://share.osf.io/` and
-  `https://share.osf.io/trove/index-card-search?cardSearchFilter[resourceType]=Preprint`.
-  Retrieved 2026-09-01. Supports: SHARE's survival as "trove" and its bucketed result count.
-- **S5** — `https://www.cos.io/products/osf-preprints`. Retrieved 2026-09-01 (HTTP 200,
-  62,612 bytes). Supports: "OSF Preprints is open source infrastructure for communities to
-  advance open scholarship dissemination. It is built using the core OSF platform"; the
-  stated goal to "Provide a single search interface to access preprints and papers from
-  many disciplinary services"; and "Contact us for more information about setting up an OSF
-  Preprint service." [DOC]
-- **S6** — Center for Open Science blog, *"Suspension of Submissions to Generalist Preprint
-  Server for Review and Next Steps — Community Servers Hosted by OSF Preprints Remain
-  Active"*, dated **August 21st, 2025**.
-  `https://www.cos.io/blog/suspension-of-submissions-to-generalist-preprint-server-for-review-and-next-steps-community-servers-hosted-by-osf-preprints-remain-active`
-  Retrieved 2026-09-01. Supports: the 2025-08-25 effective date, the two-part architecture,
-  the "14 community-run preprint servers" figure, the paper-mill/LLM reasoning, the 2024
-  introduction of moderation, and the service's 2016 origin.
-- **S7** — OSF Support, *"OSF Preprints Generalist Server Suspension"*,
-  `https://help.osf.io/category/689-osf-preprints-generalist-server-suspension`. Retrieved
-  2026-09-01; page states "Last updated on April 21, 2026". Supports: the suspension's
-  status as of 2026 and the "existing preprints remain available / authors can revise"
-  guarantee.
-- **S8** — OSF Support, *"Preprint services hosted by OSF"*,
-  `https://help.osf.io/article/686-preprint-services`. Retrieved 2026-09-01; page states
-  "Last updated on July 23, 2026". Supports: the 13-service list and its divergence from
-  the API's 14.
-- **S9** — OSF Support, *"Preprint moderation policies"*,
-  `https://help.osf.io/category/693-preprint-moderation-policies`. Retrieved 2026-09-01;
-  "Last updated on August 14, 2026". Supports: the pre-moderation statement, the anti-LLM
-  clause, the anti-aggregator clause, provider-specific policy links.
-- **S10** — Wikipedia, *List of preprint repositories*, wikitext via
-  `https://en.wikipedia.org/w/index.php?title=List_of_preprint_repositories&action=raw`.
-  Retrieved 2026-09-01. Supports: the ">1,000,000" / "over 30 preprint servers" / "25,114
-  native documents" claims, the 2017 launch year, and the `…/discover` citation URLs.
-- **S11** — Negative control: `https://help.osf.io/article/999999-this-does-not-exist-xyzzy`
-  → HTTP 404, 15,028 bytes. Retrieved 2026-09-01.
diff --git a/research/preprint-repositories/preprints-org.md b/research/preprint-repositories/preprints-org.md
deleted file mode 100644
index d0275c7..0000000
--- a/research/preprint-repositories/preprints-org.md
+++ /dev/null
@@ -1,430 +0,0 @@
-# Preprints.org — preprint repository record
-
-- **URL:** https://www.preprints.org/
-- **Operator:** MDPI AG, Grosspeteranlage 5, 4052 Basel, Switzerland — the platform's own footer
-  reads "Preprints.org is a free preprint server supported by MDPI in Basel, Switzerland" and the
-  copyright line is "© 2026 MDPI (Basel, Switzerland)" (S1). Funded by MDPI; free to authors.
-- **Discipline scope:** advertised as fully multidisciplinary (11 top-level subjects) — as actually
-  used it is dominated by Biology/Life Sciences, Medicine and **Engineering**, with a genuinely
-  large Computer Science & Mathematics section (S5).
-- **Launched:** 2016 · **Status:** active (10 years; the site runs a "10th Anniversary" banner) (S1)
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-Preprints.org is a general-purpose, all-fields preprint server launched by the open-access publisher
-MDPI in 2016. It does what the mainstream servers do: you upload a PDF or Word/LaTeX manuscript, a
-staff editor screens it within roughly a day, and it goes live under CC BY 4.0 with a Crossref DOI.
-There are no fees. Content is archived with Portico. (S2, S3)
-
-Two things make it structurally different from arXiv or TechRxiv. First, it is operated by a
-commercial journal publisher rather than a university, library consortium or learned society, and it
-is wired directly into that publisher's submission pipeline — you can tick a box during an MDPI
-journal submission to also deposit the preprint, and there is a "Preprints Friendly Journals"
-transfer service pointing outward from the server into (almost entirely) MDPI journals (S8). Second,
-it runs a real screening step with published criteria, which is more than several larger servers do.
-
-The practical consequence for an engineer is that Preprints.org is a big, fast, well-indexed
-repository whose parent company carries a contested reputation. Those are separable questions and
-§5 treats them separately.
-
-## 2. Scope and subject taxonomy
-
-Eleven top-level subjects, each with a subcategory list. The full taxonomy was extracted from the
-server-rendered Nuxt payload of the subject pages on 2026-09-01 (S5, S6). The two branches a
-systems/electronics engineer cares about:
-
-**Computer Science and Mathematics** (subject id 71) — 22 subcategories:
-
-| Subcategory | Subcategory |
-|---|---|
-| Algebra and Number Theory | Hardware and Architecture |
-| Analysis | Information Systems |
-| Applied Mathematics | Logic |
-| Artificial Intelligence and Machine Learning | Mathematical and Computational Biology |
-| Computational Mathematics | Mathematics |
-| Computer Networks and Communications | Probability and Statistics |
-| Computer Science | Robotics |
-| Computer Vision and Graphics | Security Systems |
-| Data Structures, Algorithms and Complexity | Signal Processing |
-| Discrete Mathematics and Combinatorics | Software |
-| Geometry and Topology | Other |
-
-**Engineering** (subject id 94) — 19 subcategories: Aerospace; Architecture, Building and
-Construction; Automotive; Bioengineering; Chemical; Civil; Control and Systems; **Electrical and
-Electronic**; Energy and Fuel Technology; Industrial and Manufacturing; Marine; Mechanical;
-Metallurgy and Metallurgical; Mining and Mineral Processing; Safety, Risk, Reliability and Quality;
-**Telecommunications**; Textile; Transportation Science and Technology; Other. (S6)
-
-There is also a **Chemistry and Materials Science** branch containing *Electronic, Optical and
-Magnetic Materials*, *Nanotechnology*, *Ceramics and Composites* and *Metals, Alloys and Metallurgy*
-— relevant if you are chasing device-materials work (S6).
-
-Unlike arXiv there are no short category codes (`cs.DC`); subjects are addressed by slug, e.g.
-`/subject/browse/computer-science-and-mathematics/hardware-and-architecture`.
-
-## 3. Size and growth
-
-The operator publishes a counter. All figures retrieved 2026-09-01.
-
-| Measure | Value | Source |
-|---|---|---|
-| Preprints announced to date | **137,380** | statistics page [WEB] (S4) |
-| Total downloads | 109,819,246 | statistics page [WEB] (S4) |
-| Total views | 26,832,694 | statistics page [WEB] (S4) |
-| Registered authors | 461,413 | home page [WEB] (S1) |
-| Median hours to announcement | 25.65 h | statistics page [WEB] (S4) |
-| Advisory board members | 322 | statistics page [WEB] (S4) |
-| Records in the browse index | 126,194 | browse page Nuxt payload [WEB] (S5) |
-| Crossref DOIs under prefix 10.20944 | **135,961** (100% type `posted-content`) | Crossref API [API] (S9) |
-| Works in OpenAlex source S6309402219 | 135,032 | OpenAlex API [API] (S10) |
-| Records in Europe PMC (`PUBLISHER:"Preprints"`) | 62,604 | Europe PMC API [API] (S11) |
-
-**Conflicts, recorded rather than resolved.** The site's own headline count (137,380) exceeds the
-count returned by its own browse index (126,194) by ~11,200 — Preprints.org does not explain the
-difference and I did not verify a cause [NOT-VERIFIED]. Crossref sits between the two at 135,961,
-which is consistent with the headline number minus a small registration lag. Wikipedia's *List of
-preprint repositories* row says ">124,000" with an access date of 2026-03-19 (S12) — plausible for
-that date given the growth rate, and now stale.
-
-Per-subject totals (each retrieved individually from `/subject/browse/<slug>`, 2026-09-01) (S5):
-
-| Subject | Preprints |
-|---|---|
-| Biology and Life Sciences | 24,867 |
-| Medicine and Pharmacology | 22,428 |
-| **Engineering** | **17,844** |
-| **Computer Science and Mathematics** | **15,672** |
-| Environmental and Earth Sciences | 9,382 |
-| Chemistry and Materials Science | 8,949 |
-| Physical Sciences | 7,154 |
-| Public Health and Healthcare | 6,959 |
-| Social Sciences | 6,780 |
-| Business, Economics and Management | 5,167 |
-| Arts and Humanities | 1,377 |
-
-These sum to 126,579, marginally above the 126,194 browse total, i.e. a small number of preprints
-carry more than one subject [INF].
-
-Selected subcategory counts (2026-09-01) (S5): AI & Machine Learning 5,505; Electrical and Electronic
-Engineering 3,147; Mechanical Engineering 2,137; Energy and Fuel Technology 1,630; Computer Science
-1,431; Control and Systems Engineering 1,110; Industrial and Manufacturing 1,063; Information Systems
-785; Computer Vision and Graphics 778; Computer Networks and Communications 527; Security Systems
-451; Telecommunications 332; Software 279; Data Structures, Algorithms and Complexity 247; Robotics
-247; Signal Processing 153; **Hardware and Architecture 77**.
-
-Growth by year of record creation, from OpenAlex (S10): 2016 950 · 2017 2,124 · 2018 6,040 · 2019
-3,886 · 2020 7,015 · 2021 7,857 · 2022 6,273 · 2023 21,776 · 2024 28,567 · 2025 31,468 · 2026 (part
-year) 19,075. The step change in 2023 is stark and unexplained by the operator [NOT-VERIFIED as to
-cause].
-
-Published versions **stay**. Each new version receives a different DOI; if a journal version appears
-later, Preprints.org links it from the preprint page rather than removing the preprint (S3).
-
-## 4. Screening and moderation — what gets in
-
-Preprints.org does screen, and publishes the criteria. This is the operator's own text.
-
-From the About page (S2): *"All preprints undergo a short screening before being uploaded online…
-Screening includes checks for basic scientific content, author background, and compliance with
-ethical standards. It is carried out by the Preprints.org staff, with the support of active
-researchers and the Preprints.org advisory board."*
-
-From the Instructions for Authors, §Screening (S3), the manuscript is checked to ensure:
-
-- the content is in English;
-- it has not been previously published;
-- it adheres to basic publishing ethics and international research-ethics regulation;
-- the author has not made excessive submissions in a short period (*"excessive submissions within a
-  short period may require justification and could be rejected"*);
-- all authors are genuine scholars (*"submissions with fake names or email addresses may be
-  rejected"*);
-- conflicts of interest are disclosed;
-- all figures, references and other critical components are present;
-- **the content does not contain "harmful, provocative, controversial, or pseudoscientific
-  statements"**, and manuscripts *"drawing strong conclusions without fully accessible supporting
-  data may also be rejected"*;
-- any AI use is disclosed and conforms to the COPE-aligned policy.
-
-Preprints.org *"reserves the right to decline posting a preprint for reasons not explicitly stated
-above"*, and screening *"typically takes 24 hours … by our trained editors"* (S3). Institutional
-email addresses are recommended for author identification, and screeners are recruited from
-"scholars with a track record of published and cited articles" (S2).
-
-Editorials, discussion papers and coursework are *"typically"* not permitted; conference papers are
-accepted only if unreviewed and DOI-less; abstracts are refused (S3).
-
-Withdrawal is discretionary and narrow: misconduct, uncorrectable serious error, or serious reader
-concern. Outright *removal* happens only under court order, illegality, privacy/legal risk, or
-public danger (S3). A withdrawn preprint's DOI persists.
-
-**Assessment.** This is a real gate — comparable in stringency to what Kirkham et al. (BMJ Open 2020)
-found across biomedical preprint platforms, where screening ranged from none to full editorial
-triage (S13). It is not peer review, and Preprints.org says so plainly: *"Content on Preprints.org
-is not peer-reviewed"* (S2).
-
-## 5. Reliability — what you can and cannot trust
-
-### What a deposit here does and does not guarantee
-
-**Does:** a timestamp; a Crossref DOI; a CC BY 4.0 licence; Portico archiving; passage through a
-staff screen that checks language, ethics statements, author identity, completeness, and screens out
-overt pseudoscience. **Does not:** any assessment of correctness, novelty, statistics, or
-reproducibility.
-
-### The operator's own conversion claim
-
-The statistics page states a *"Rate of preprints converted to a peer reviewed article: 58.44%"*
-(S4). Treat this as an **operator claim [DOC], not an independent measurement** — Preprints.org does
-not publish the method, the denominator, the cohort window, or whether "peer reviewed article"
-includes MDPI journals only. I found no independent scientometric replication of that figure
-[NOT-VERIFIED].
-
-### The MDPI question — stated fairly
-
-MDPI's standing is genuinely contested, and the contest is documented on both sides.
-
-**The criticisms.**
-
-1. *Special-issue volume.* Paolo Crosetto (INRAE-GAEL) documented in 2021 that MDPI special issues
-   grew from ~388 in 2013 to nearly 40,000 in 2021, ~500 per journal, and that at MDPI it is the
-   *publisher* rather than the editorial board that solicits them (S14, via S15). Oviedo-García
-   (2021) reported that in 2020 *Sustainability* ran 788 special issues, *Applied Sciences* 830 and
-   *Materials* 846, with ~95% of MDPI journals publishing more than one special issue per week
-   (S16, via S15). *Inside Higher Ed* reported 3,514 special issues with 2023 closing dates for
-   *IJMS* alone (S17, via S15). The stated concern is whether peer review can be conducted
-   effectively at that scale.
-2. *The 2023 Clarivate delistings.* Clarivate discontinued Web of Science coverage of two MDPI
-   journals — *International Journal of Environmental Research and Public Health* (IJERPH,
-   effective 13 February 2023) and *Journal of Risk and Financial Management* (JRFM, effective 22
-   February 2023) (S18). This sat inside a wider Clarivate purge: their SVP/Editor-in-Chief wrote
-   that *"more than 500 journals were flagged"* at the start of 2023 and *"more than 50 … have
-   subsequently been de-listed"*, spanning *"both major commercial publishing houses and smaller or
-   society publishers"* (S19).
-
-**MDPI's published responses.**
-
-1. On the delistings, MDPI's own announcement (S18) states that Clarivate found both journals failed
-   the **Content Relevance** criterion — *"highlighting publications that were deemed outside the
-   scope of the journal, and not to do with quality of the publications"* — that MDPI *"formally
-   appealed the decision to discontinue IJERPH"* on 31 March 2023, and that *"close to 90% of MDPI
-   published content is going to be covered by the Web of Science Core Collection going forward."*
-   Whether the IJERPH appeal succeeded is **[NOT-VERIFIED]** here.
-2. On the Oviedo-García paper, MDPI's objections had editorial effect: *Research Evaluation* issued
-   an **Expression of Concern** on the article in 2021 (doi 10.1093/reseval/rvab030) and a formal
-   **Correction** in 2023 (doi 10.1093/reseval/rvad014) (S20, S21, S22). A reader weighing the
-   "predatory" framing should note that the flagship paper making it was itself flagged and
-   corrected.
-
-### Does that reputation transfer to the preprint server?
-
-**Mostly not, and it is important to be precise about why.** The criticisms above are about *journal
-peer review at scale* — special-issue guest-editor quality, scope drift, reviewer load. A preprint
-server performs none of those functions. Preprints.org states it does not peer review; nothing on it
-carries a peer-review claim that could be inflated. On the specific axes that matter for a preprint
-server — screening criteria, transparency of policy, DOI assignment, licensing, archiving — its
-published policies (§4, §9) are unremarkable and in places stricter than peers'.
-
-**Where the entanglement is real and should worry you** is the *funnel*, not the quality gate. See
-§10.
-
-### Known failure modes
-
-- **Prolific single-author revision streams.** The Data Structures, Algorithms and Complexity listing
-  on 2026-09-01 was topped by `10.20944/preprints202511.2197.v9` — a **ninth version** of the same
-  claimed combinatorial-triangle-detection result (S23). Version churn on hard-open-problem-adjacent
-  claims is a well-known preprint pathology and it is present here.
-- **Soft 404s.** See §8 — the site returns HTTP 200 for non-existent manuscripts and non-existent
-  subject slugs. Do not treat a 200 as proof a record exists.
-- **No independent quality measurement.** I found no peer-reviewed scientometric study measuring
-  retraction, error or paper-mill rates specific to Preprints.org [NOT-VERIFIED].
-
-### How to sanity-check an individual paper from here
-
-1. Check whether the article page links a peer-reviewed version; if yes, cite that instead.
-2. Check the version number — `.v6`+ on a short paper is a warning sign.
-3. Check the author's institutional email/ORCID presence (screening nominally requires this).
-4. For CS/EE work, check whether the same authors also posted to arXiv; Preprints.org explicitly
-   *recommends against* multi-server posting (S3), so a duplicate is worth a second look.
-5. Verify claimed numbers independently. A screen for "harmful, provocative, controversial, or
-   pseudoscientific statements" is not a screen for *wrong*.
-
-## 6. What you actually find there — examples
-
-Real records, retrieved 2026-09-01 from the Hardware and Architecture, Electrical and Electronic
-Engineering, and Data Structures/Algorithms listings (S23):
-
-**Hardware and architecture**
-
-- *nSim-RV: A Configurable RISC-V Framework for Scheduler-Aware Timing-Scalability Evaluation* —
-  `10.20944/preprints202606.0599.v1`
-- *An Open-Hardware ML-KEM Polynomial Ring Accelerator on Chipyard RISC-V SoC: System-Level
-  Integration…* — `10.20944/preprints202605.1405.v1`
-- *TALOS: An Ultra-Efficient Area-Space 6G CryptoProcessor Leveraging Reusable Hardware Security
-  Modules* — `10.20944/preprints202605.1914.v1`
-- *Backlog Metastability in Windowed Quantum Error Correction Decoding* —
-  `10.20944/preprints202608.1425.v2`
-
-**Electrical and electronic engineering**
-
-- *A Time-Multiplexed Q16.16 Fixed-Point Neural Network Accelerator for Resource-Efficient FPGA
-  Inference* — `10.20944/preprints202608.2059.v1`
-- *On Eddy Current Brakes with Anisotropic Material Structures: Electromagnetic Model and Its
-  Detailed…* — `10.20944/preprints202608.2206.v1`
-
-**Algorithms / complexity**
-
-- *Parallel Repetition for Entangled Games with Gap Exponent Three* — `10.20944/preprints202608.0830.v1`
-- *Hardness of Euclidean Closest Vector Within n^(1/8−ε) and Binary Near…* — `10.20944/preprints202608.0796.v1`
-- *Reachable Globally Pareto-Efficient Allocations on Trees Are NP-Complete* — `10.20944/preprints202608.2133.v1`
-
-**Honest quality read.** This is recognisable, ordinary engineering-conference-grade work — RISC-V
-simulation frameworks, post-quantum accelerators, FPGA inference. It is *not* the venue where the
-field's landmark results appear, and the complexity-theory items sit next to repeatedly-revised
-open-problem claims. Treat it as a place to *find* work-in-progress from groups that publish in
-MDPI's *Electronics*, *Sensors*, *Micromachines* and *Cryptography*, not as a source of record.
-
-A revealing data point on what actually gets read: the server's own all-time top-5 most-viewed list
-is four COVID-19 papers plus *"Raspberry PI for Kill Mosquitoes by Laser"* (02 August 2021, 133,692
-views) (S4).
-
-## 7. Landmark papers (software · distributed systems · databases · electronics · security)
-
-Preprints.org hosts no landmark work in these areas. It began in 2016, long after the foundational
-CS/EE literature was established, and its CS/EE deposits are overwhelmingly incremental applied
-papers destined for mid-tier journals. No table.
-
-## 8. Access, APIs and bulk retrieval
-
-- **No OAI-PMH.** `/oai` and `/oai2` return HTTP 404 (2026-09-01) (S24).
-- **No documented public REST API.** `/api` returns 404. The Nuxt SSR payload
-  (`<script id="__NUXT_DATA__">`) on browse and subject pages is machine-parseable and is how the
-  per-subject counts in §3 were obtained — undocumented and liable to change without notice [INF].
-- **RSS:** `https://www.preprints.org/rss` returns HTTP 200, `application/rss+xml`, 127,714 bytes
-  (S25).
-- **Sitemaps:** `robots.txt` advertises `https://www.preprints.org/sitemap_index.xml`, which chains
-  to `/__sitemap__/general.xml` and `/sitemap/index.xml`. `robots.txt` disallows `/search*` (S24).
-- **Bulk metadata is best taken from Crossref** (prefix `10.20944`, 135,961 `posted-content`
-  records) or OpenAlex (source `S6309402219`) rather than scraped (S9, S10).
-- **User-agent gating is real.** As of 2026-09-01 `https://www.preprints.org/` returns **HTTP 403**
-  (369-byte body) to `curl`'s default UA *and* to a normal desktop Chrome UA, but **HTTP 200** to
-  `WhatsApp/2.23.20.0`. All retrievals here used the WhatsApp UA (S26). Per AGENTS.md rule 6, this
-  does **not** mean the site works normally for ordinary clients.
-- **Rate limiting is real.** Sequential subject-page requests without delay produced HTTP 429 after
-  ~6 requests; ≥4 s spacing was needed (S5).
-
-### Negative controls (2026-09-01) (S27)
-
-| Probe | Result | Interpretation |
-|---|---|---|
-| `/subject/browse/engineering/quantum-basket-weaving-xyz` | **HTTP 200**, 570,854 bytes, `total = 17844` | Bogus subcategory silently falls back to the **parent Engineering listing**. A 200 proves nothing. |
-| `/manuscript/999912.9999/v1` | **HTTP 200**, 289,595 bytes | Renders an empty article shell with `Posted: Invalid Date`, blank abstract, blank keywords. Soft 404. |
-| `/help` | HTTP 404 (real) | Some routes do 404 correctly; behaviour is inconsistent. |
-| `/subject/browse/computer-science-and-mathematics/hardware-and-architecture` | HTTP 200, `total = 77` | Valid path returns a distinct, plausible count. |
-
-**Rule for this server: verify by DOI at Crossref, never by HTTP status.**
-
-## 9. Licensing and reuse
-
-- **CC BY 4.0, mandatory, no author choice.** *"All preprints are posted using an open access
-  Creative Commons CC BY 4.0 license"* (S3). Authors grant Preprints.org "a perpetual, non-exclusive
-  license to distribute."
-- Authors retain copyright (S2).
-- Text and data mining are therefore permitted by licence; the practical obstacle is the UA gating
-  above, not the licence.
-- **Preservation:** *"All preprints on Preprints.org are permanently archived at Portico"* (S3).
-- Manuscripts appear first as PDF; full-text HTML *"typically becomes available within one week"*
-  (S3).
-
-## 10. Caveats and controversies
-
-1. **The funnel is real and quantifiable.** The "Preprints Friendly Journals" page lists **232**
-   journals offering direct manuscript transfer from Preprints.org. **230 of the 232 are MDPI
-   journals** (`www.mdpi.com` URLs); the only two exceptions are `ahr-journal.org` and
-   `revistaalergia.mx` (S8). The server also runs "MDPI Topics … offered to authors who want to
-   submit to a MDPI journal after posting their paper" (S1), and the About page notes authors *"can
-   also choose to submit their manuscripts to Preprints.org when submitting to any MDPI journal"*
-   (S2). Depositing does not *oblige* you to submit to MDPI, but every affordance on the site points
-   there. The CS/EE targets include *Electronics*, *Sensors*, *Algorithms*, *Cryptography*,
-   *Computers*, *Micromachines*, *Drones*, *Journal of Low Power Electronics and Applications* and
-   *Machine Learning and Knowledge Extraction* (S8).
-2. **Parent-company reputation ≠ server reputation, but disclose the link.** If you cite a
-   Preprints.org record in work that will be scrutinised, say who runs it. The MDPI controversies of
-   §5 are about journal peer review, not preprint hosting, but a reader is entitled to know.
-3. **The 58.44% conversion figure is unaudited** (§5).
-4. **The 2023 volume step change** (7× year-on-year in OpenAlex counts) is undocumented by the
-   operator (S10).
-5. **Soft 404s make automated verification hazardous** (§8).
-6. **Multi-posting is discouraged**, which slightly reduces the chance of finding an arXiv mirror to
-   cross-check against (S3).
-7. **Bot gating.** Retrieval required a non-standard UA (§8) — record this if you build tooling.
-
-## 11. Sources
-
-- **S1** — https://www.preprints.org/ · retrieved 2026-09-01 [WEB] · homepage: author count 461,413,
-  "137K+ Total Preprints", MDPI footer, MDPI Topics, 10th Anniversary banner, top-of-page listings.
-- **S2** — https://www.preprints.org/about · retrieved 2026-09-01 [DOC] · screening description,
-  advisory board and screener roles, CC BY, Crossref DOI, "not peer-reviewed", MDPI address.
-- **S3** — https://www.preprints.org/instructions-for-authors · retrieved 2026-09-01 [DOC] · full
-  Screening criteria list, accepted article types, withdrawal/removal policy, versioning, Portico,
-  CC BY licence grant, multi-posting recommendation.
-- **S4** — https://www.preprints.org/statistics · retrieved 2026-09-01 [WEB] · 137,380 announced;
-  109,819,246 downloads; 26,832,694 views; 25.65 h median to announcement; 58.44% conversion claim;
-  322 advisory board members; all-time top-5 viewed list.
-- **S5** — https://www.preprints.org/subject/browse and `/subject/browse/<subject>[/<subcat>]` ·
-  retrieved 2026-09-01 [WEB] · per-subject and per-subcategory totals from the `__NUXT_DATA__`
-  payload; browse total 126,194; HTTP 429 observed on rapid sequential requests.
-- **S6** — https://www.preprints.org/subject · retrieved 2026-09-01 [WEB/DOC] · 11 top-level
-  subjects; full subcategory tree with ids extracted from `__NUXT_DATA__`.
-- **S8** — https://www.preprints.org/friendly-journals · retrieved 2026-09-01 [DOC] · 232 friendly
-  journals, 230 on www.mdpi.com; per-journal impact factor / CiteScore / first-decision days.
-- **S9** — https://api.crossref.org/prefixes/10.20944/works?rows=0&facet=type-name:* · retrieved
-  2026-09-01 [API] · 135,961 works, all `posted-content`.
-- **S10** — https://api.openalex.org/sources/S6309402219 · retrieved 2026-09-01 [API] · 135,032
-  works; 279,413 citations; counts_by_year 2016–2026.
-- **S11** — https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=PUBLISHER:"Preprints" ·
-  retrieved 2026-09-01 [API] · hitCount 62,604.
-- **S12** — https://en.wikipedia.org/wiki/List_of_preprint_repositories (wikitext via MediaWiki API)
-  · retrieved 2026-09-01 [COM] · row: ">124,000", 2016, MDPI, access-date 2026-03-19.
-- **S13** — Kirkham JJ, Penfold NC, Murphy F, Boutron I, Ioannidis JP, Polka J, Moher D.
-  "Systematic examination of preprint platforms for use in the medical and biomedical sciences
-  setting." *BMJ Open* 2020;10:e041849 · https://doi.org/10.1136/bmjopen-2020-041849 · metadata
-  retrieved 2026-09-01 [LIT] · comparative survey of preprint-platform screening practice.
-- **S14** — Crosetto P., blog analysis of MDPI special issues, April 2021, as cited and summarised in
-  S15 [COM, secondary].
-- **S15** — https://en.wikipedia.org/wiki/MDPI (wikitext via MediaWiki API) · retrieved 2026-09-01
-  [COM] · "2023 Clarivate delistings" and "Proliferation of special issues" sections with citations.
-- **S16** — Oviedo-García MÁ. "Journal citation reports and the definition of a predatory journal:
-  The case of the Multidisciplinary Digital Publishing Institute (MDPI)." *Research Evaluation*
-  2021 · https://doi.org/10.1093/reseval/rvab020 · metadata retrieved 2026-09-01 [LIT].
-- **S17** — Grove J. "3,514 Special Issues a Year?" *Inside Higher Ed*, 15 March 2023, as cited in
-  S15 [COM, secondary].
-- **S18** — https://www.mdpi.com/about/announcements/5536 · "Clarivate Discontinues IJERPH and JRFM
-  Coverage in Web of Science" · retrieved 2026-09-01 [DOC] · MDPI's own statement: dates 13/22
-  February 2023, Content Relevance criterion, appeal filed 31 March 2023, "close to 90% of MDPI
-  published content" still covered. Retrieved with UA `WhatsApp/2.23.20.0` (default and Chrome UAs
-  return 403).
-- **S19** — https://clarivate.com/blog/supporting-integrity-of-the-scholarly-record-our-commitment-to-curation-and-selectivity-in-the-web-of-science/
-  · Quaderi N., Clarivate · retrieved 2026-09-01 [DOC] · ">500 journals flagged", ">50 de-listed",
-  "<15% of journals pass our quality criteria". Does not name MDPI.
-- **S20** — https://doi.org/10.1093/reseval/rvab030 · "Expression of concern: Journal citation
-  reports and the definition of a predatory journal…" *Research Evaluation* 2021 · metadata
-  retrieved 2026-09-01 [LIT].
-- **S21** — https://doi.org/10.1093/reseval/rvad014 · "Correction to: …" *Research Evaluation* 2023 ·
-  metadata retrieved 2026-09-01 [LIT].
-- **S22** — https://api.openalex.org/works?search=MDPI+predatory+journal+citation+reports · retrieved
-  2026-09-01 [API] · surfaced S16/S20/S21 and their citation counts (174 / 5 / 5).
-- **S23** — https://www.preprints.org/subject/browse/computer-science-and-mathematics/hardware-and-architecture
-  , `/…/data-structures-algorithms-and-complexity`, `/subject/browse/engineering/electrical-and-electronic-engineering`
-  · retrieved 2026-09-01 [WEB] · titles and DOIs listed in §6; `…202511.2197.v9` observed.
-- **S24** — https://www.preprints.org/robots.txt , `/oai` , `/oai2` , `/api` , `/sitemap_index.xml` ·
-  probed 2026-09-01 [WEB] · 404s for OAI and API; sitemap chain; `Disallow: /search*`; sitemap
-  generation timestamp `2026-09-01T21:39:04.761Z` confirms live retrieval.
-- **S25** — https://www.preprints.org/rss · probed 2026-09-01 [WEB] · HTTP 200,
-  `application/rss+xml`, 127,714 bytes.
-- **S26** — UA matrix probe, 2026-09-01 [WEB] · `curl/8.5.0` → 403/369 B; Chrome 131 desktop UA →
-  403/369 B; `WhatsApp/2.23.20.0` → 200/334,859 B; ChatGPT-User and ClaudeBot UAs → 403.
-- **S27** — negative-control probes, 2026-09-01 [WEB] · bogus subcategory → 200 with parent total
-  17,844; bogus manuscript id → 200 with "Invalid Date" shell.
diff --git a/research/preprint-repositories/qeios.md b/research/preprint-repositories/qeios.md
deleted file mode 100644
index 345c526..0000000
--- a/research/preprint-repositories/qeios.md
+++ /dev/null
@@ -1,355 +0,0 @@
-# Qeios — preprint repository record
-
-- **URL:** https://www.qeios.com/
-- **Operator:** Qeios (UK-based; ISSN 2632-3834, online). Commercially funded: free tier plus a
-  **Pro** subscription at **USD 24.99/month** (S3). Editorial team chaired by Giorgio Bedogni
-  (Bologna) with a managing/editorial board drawn largely from UCL and European institutions (S9).
-- **Discipline scope:** multidisciplinary, organised by Scopus ASJC into four domains — Physical,
-  Health, Social and Life Sciences (S2, S4). In practice heavily social/health-sciences and
-  philosophy-of-science; a genuine but thin computing stream exists (§6).
-- **Launched:** 2019 (Wikipedia's repository list and the platform's own Volume 1 = 2019; Crossref
-  shows first DOIs registered September 2018) · **Status:** active
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-Qeios inverts the usual order. You post a paper as a preprint within one business day; **peer review
-happens afterwards, in public, under the reviewers' real names, with numeric scores**; and if the
-paper accumulates enough positive reviews the author may *elect* to convert it into a "Version of
-Record" carrying a **peer-approved** label. Editors never accept or reject: *"reviewers alone decide
-on the validity of the papers"* (S9), and the editorial team's remit is limited to disputes and
-misconduct.
-
-Two features distinguish it from other open-review platforms. First, **AI is woven through the
-pipeline** — for submission pre-checks, for identifying and inviting reviewers, for vetting the
-identities and suitability of spontaneous reviewers, for grammar correction, and for the
-language/best-practice checks that gate the peer-approved label (§4). Second, Qeios carries a huge
-body of short **"Definitions"** — encyclopaedia-style entries, each with its own DOI — alongside
-its research papers. Numerically the definitions *are* Qeios: they outnumber the research articles
-roughly 25:1 (§3).
-
-## 2. Scope and content types
-
-Four Scopus ASJC domains and their fields; the browse interface offers **Computer Science**,
-**Engineering**, **Mathematics**, **Chemical Engineering**, **Materials Science**, **Energy** and
-**Physics and Astronomy** among 26 field filters (S5).
-
-The archive exposes four object types (S6):
-
-| Type | `?type=` value | Count (2026-09-01) |
-|---|---|---|
-| Definitions (wiki/encyclopaedia entries) | `definition` | **106,486** |
-| Peer reviews | `peer_review` | **49,803** |
-| Preprints | `article.preprint` | **3,979** |
-| Peer-approved articles (Version of Record) | `article.peer_approved` | **392** |
-| All articles | `article` | 4,372 |
-
-Article sub-genres seen in the live archive include Research Article, Review Article, Commentary
-(S6, S7).
-
-## 3. Size and growth
-
-| Measure | Value | Source |
-|---|---|---|
-| Qeios archive: definitions | 106,486 | own archive counter [WEB] (S6) |
-| Qeios archive: peer reviews | 49,803 | own archive counter [WEB] (S6) |
-| Qeios archive: preprints | 3,979 | own archive counter [WEB] (S6) |
-| Qeios archive: peer-approved articles | 392 | own archive counter [WEB] (S6) |
-| **Crossref DOIs, prefix 10.32388 — total** | **175,165** | Crossref API [API] (S8) |
-|  · `Entry` (reference-entry = definitions) | 109,765 | Crossref [API] (S8) |
-|  · `Peer Review` | 57,288 | Crossref [API] (S8) |
-|  · `Posted Content` (preprints) | 6,111 | Crossref [API] (S8) |
-|  · `Journal Article` | 2,000 | Crossref [API] (S8) |
-| Works in OpenAlex source S4210177074 | 6,879 (28,061 citations) | OpenAlex [API] (S10) |
-| Records in Europe PMC (`PUBLISHER:"Qeios"`) | 4,554 | Europe PMC [API] (S11) |
-| Registered researchers (operator claim) | "100,000+" (was "90,000+" in Dec 2024) | own about page [DOC] (S2, S12) |
-| Monthly readers (operator claim) | "200,000+" | own about page [DOC] (S2) |
-
-**The number that matters.** Qeios's *research corpus* is roughly **8,100 objects** (6,111
-preprints + 2,000 journal articles at Crossref), matching OpenAlex's 6,879 and Europe PMC's 4,554
-within the usual coverage variation. **Everything else — 95% of Qeios's DOIs — is definitions and
-reviews.** Wikipedia's repository-list row gives ">1000" for Qeios (S13); that is stale but, unlike
-the ScienceOpen row, at least the right order of magnitude for the article corpus.
-
-**Conflicts, recorded.** Qeios's own archive counts (4,371 articles, 106,486 definitions, 49,803
-reviews = 160,660) are consistently below Crossref's (8,111 / 109,765 / 57,288 = 175,164). The most
-likely cause is that the archive counts current versions while Crossref counts version DOIs [INF];
-Qeios does not explain the gap [NOT-VERIFIED].
-
-Growth by year (OpenAlex, articles only, S10): 2016 1 · 2018 16 · 2019 96 · 2020 157 · 2021 70 ·
-2022 146 · **2023 1,852 · 2024 2,791 · 2025 1,323** · 2026 (part) 427. The 2023–24 surge and the
-subsequent ~50% fall are both large and unexplained by the operator.
-
-## 4. Screening, moderation and the peer-approval gate
-
-**At submission (pre-posting).** *"Submit your paper, and we'll perform AI-assisted pre-checks for
-non-scientific content and plagiarism. Your paper will be posted on Qeios as a preprint within 1
-business day."* (S2) The ethics page elaborates: the custom AI *"assists with pre-checks at
-submission to filter out non-scientific content and detect plagiarism"* (S9).
-
-**Review invitation.** *"Our custom-built AI identifies potential reviewers among qualified
-researchers with field expertise. Potential reviewers are contacted and invited to publicly review
-the article."* Spontaneous reviewers may also self-select, but *"all identities and reviews undergo
-an AI-assisted suitability check."* (S4) On the Pro plan, *"These experts provide over 98% of Qeios
-reviews"* (S3) — i.e. the AI-driven Reviewer Recruitment Service is the dominant source of reviews,
-and it is a **paid feature** after your first paper.
-
-**The peer-approved gate.** A paper needs *"at least 4 peer reviews with average ratings of 3 out of
-5 or higher for overall, clarity, and impact, and 2.5 or higher for novelty"*, after which the author
-*may opt* to publish a Version of Record. That version *"has passed further AI-assisted checks for
-language quality and adherence to field-specific best practices, such as the WMA Declaration of
-Helsinki … and ARRIVE guidelines"* (S2, S4, S9).
-
-**Continuous scrutiny.** If later reviews drag the overall average below 2.5/5, *"the paper will no
-longer be considered peer-approved"* (S2, S9). This is a genuinely unusual and, on its face, a good
-property: approval is revocable.
-
-**Reviews are never anonymous**, carry 1–5 star ratings for overall/clarity/novelty/impact, require
-a competing-interests declaration, get their own DOI and CC BY licence, and can themselves be
-upvoted, downvoted and commented on (S4).
-
-**Generative-AI authorship policy** (S4, last updated 2025-04-29): GenAI *"do[es] not qualify for
-authorship and must not be listed as an author"*; language/readability use must be disclosed;
-GenAI image creation/alteration is **not permitted** unless integral to the methodology.
-
-### On "AI reviewers" — what is and is not verified
-
-**Verified [DOC]:** Qeios uses custom AI to (a) pre-screen submissions for non-scientific content
-and plagiarism, (b) identify and invite reviewers, (c) check the identity and suitability of
-spontaneous reviewers and their reviews, (d) grammar-correct reviews (the API exposes a
-`pre_grammar_correction_contents` field on review objects, S14), and (e) run language and
-field-best-practice checks before granting the peer-approved label (S2, S3, S4, S9).
-
-**NOT VERIFIED:** that Qeios publishes reviews *authored* by an AI. What I did to check:
-(1) read the current publishing policy, about page and ethics page in full — all describe AI as
-assisting reviewer *selection and vetting*, never as writing reviews (S2, S4, S9); (2) read the
-archived 2023 about page — same (S15); (3) sampled **3,000 Crossref-registered Qeios peer-review
-records** and inspected every author name: **all 3,000 had named human authors, none matching
-`AI|GPT|Chat|Bot|Qeios|Artificial|Machine|Assistant|Anonymous`** (S16); (4) pulled a live review
-object from the Qeios JSON API — signed by a named researcher with an institutional affiliation
-(S14); (5) searched Mojeek for "Qeios AI-generated review", "Qeios review written by AI", "Qeios
-artificial intelligence reviewer" — no substantive result (S17). **Anyone repeating the claim that
-Qeios posts AI-written reviews should produce a source; I could not.** Note the endorsement Qeios
-itself displays from Robert West (UCL): *"It uses AI to find and invite reviewers"* — find and
-invite, not write (S12).
-
-## 5. Reliability — what you can and cannot trust
-
-**A Qeios *preprint* guarantees:** a DOI, CC BY 4.0, and passage through an automated
-non-scientific-content/plagiarism screen within one business day. Nothing more.
-
-**A Qeios *peer-approved* article guarantees:** ≥4 signed public reviews above stated numeric
-thresholds, plus automated language/guideline checks. That is more transparent than a conventional
-journal — you can read every review — but note the structural weaknesses:
-
-1. **Reviewer supply is a paid product.** Pro ($24.99/mo) buys the Reviewer Recruitment Service that
-   generates >98% of reviews (S3). Free-tier authors depend on spontaneous reviewers. An author who
-   pays gets reviewed; an author who doesn't may not. This is not "reviewers are paid to be
-   positive", but it does couple *review availability* to *payment*.
-2. **No editor can reject.** By design (S9). The upside is no editorial bias; the downside is no
-   backstop when four lenient reviewers all give 3/5.
-3. **The threshold is low.** 3/5 average on overall/clarity/impact and 2.5/5 on novelty is a modest
-   bar for a "Version of Record".
-4. **"Median of 10 peer reviews … the most peer-reviewed publishing venue globally"** (S2, S9) is an
-   **operator claim** with no published method or dataset [DOC, unaudited]. Crossref's ratio —
-   57,288 reviews against 8,111 research objects — is consistent with a high *mean* (~7) but does
-   not establish the median [INF].
-
-### Documented incident: conflict with journal dual-submission rules
-
-In December 2024, **Ethan Vishniac, Editor-in-Chief of *The Astrophysical Journal***, posted a
-six-part public thread describing a case where an AAS journal referee reported being asked to review
-the same manuscript elsewhere. The author had agreed to let Qeios post his preprint and solicit
-reviews, *"the issue of peer review was never raised."* Vishniac's position: *"Qeios.com takes the
-position that they are not a journal, but a website that vets papers through peer review. The AAS
-journals (and as far as I know, all other professional journals) does not regard this as a meaningful
-distinction."* AAS bans simultaneous submission *"in order to avoid over-burdening the community with
-review requests and because we do not want to encourage people to shop for a referee."* (S18, quoted
-in full by Peter Coles, S18)
-
-Coles's own assessment: *"to all intents and purposes Qeios is a journal. It has an ISSN that says as
-much too."* A commenter on that post points at Qeios's own wording: *"Once your paper secures at
-least 4 peer reviews (…) you can opt to publish it as a regular journal article—known as the Version
-of Record—on Qeios."* (S18)
-
-**Practical consequence:** posting to Qeios and letting it recruit reviewers **while your paper is
-under review elsewhere may put you in breach of the other journal's dual-submission rule**, and — as
-Coles notes — some institutional research-integrity policies treat "artificially proliferating
-publications" as misconduct. Qeios's own policy has a "Preprint Posting" section but the platform
-does not, on the pages retrieved, warn authors about this specific collision [NOT-VERIFIED that no
-such warning exists anywhere on the site].
-
-### Low-quality content
-
-The definitions corpus (106k+ entries) is encyclopaedia-style and not research. Among research
-items, the archive shows the usual prolific-single-author pattern — e.g. two separate physics-adjacent
-research articles by the same author posted on the same day, 2026-08-31 (S7). I found **no documented
-retraction scandal or paper-mill incident specific to Qeios** [NOT-VERIFIED].
-
-### How to sanity-check an item from here
-
-1. Check whether it is `peer-approved` or a bare preprint. Bare preprint = screened by software only.
-2. **Read the reviews.** They are signed, public, dated, scored and DOI'd — this is Qeios's genuine
-   advantage. Check whether reviewers are in-field.
-3. Check the review count and score spread, not just the label.
-4. Check whether the same work is under review at a journal (see the incident above).
-5. Distinguish `Definition` objects from research articles — they share the DOI prefix.
-
-## 6. What you actually find there — examples
-
-Computing/engineering preprints, retrieved via Crossref prefix `10.32388` (S19) and the live archive
-(S7):
-
-- *MVD: A Multi-Lingual Software Vulnerability Detection Framework* — `10.32388/4ahqy3` (2025-01-08)
-- *A Generalized Space-Efficient Algorithm for Quantum Bit String Comparators* — `10.32388/nrq6w1` (2024-03-14)
-- *Quantum Meets SAR: A Novel Range-Doppler Algorithm for Next-Gen Earth Observation* — `10.32388/8q5ow6` (2025-04-10)
-- *New Adaptive Numerical Algorithm for Solving Partial Integro-Differential Equations* — `10.32388/r4546k` (2023-11-13)
-- *Machine-Checked Bell-Violating Correlations with Deterministic Outcomes and Local Measurement Dynamics: A Lean 4 Formalisation* — live archive, 2026-08-31
-- *Beyond Suspicion Scores: Competing-Explanation Inference for Fraud-Shaped Legitimate Activity* — live archive, 2026-08-31
-
-Also present: *Review of: "Evaluating the Application of SOLID Principles in Modern A…"* —
-`10.32388/kyv073` (2025-04-17), a signed software-engineering review with its own DOI (S20).
-
-**Honest quality read.** A Crossref bibliographic query for *software / algorithm / network /
-hardware / FPGA* across all Qeios preprints returns **63 records total** (S19). That is the size of
-the computing corpus: essentially nothing. Alongside the credible items above sit things like
-*"Research on Travel Route Planing Problem Based on Greedy Algorithm"* and *"The Algorithm; Mind of a
-Virtual Era – Our Code of Codes"*. A systems or electronics engineer will not find a working corpus
-here. What Qeios *is* useful for is reading open, signed peer reviews of individual papers — a
-genuinely scarce resource.
-
-## 7. Landmark papers
-
-None in software, distributed systems, databases, electronics or security. The computing corpus is
-~63 papers (§6).
-
-## 8. Access, APIs and bulk retrieval
-
-- **An undocumented but working public JSON API exists.** `https://www.qeios.com/api/publications/<QEIOS_ID>/published-reviews-of-any-versions`
-  returns HTTP 200 `application/json` with the full review objects — body HTML, ratings
-  (`borne_rating`, `borne_subrating_for_clarity|novelty|impact`), `declarations.coi`, DOI, view and
-  download counts, author records with ORCID, and `pre_grammar_correction_contents` (S14).
-  `https://www.qeios.com/api/notable-reviewer-users` also returns 200 with a paginated user list.
-  There is **no published documentation, no stated rate limit, and no terms of use for the API** —
-  treat it as unstable.
-- **Archive faceting is a usable count API:** `https://www.qeios.com/archive?type=<value>` returns an
-  "N items" figure. Valid values found by probing: `article`, `article.preprint`,
-  `article.peer_approved`, `article.review`, `peer_review`, `definition`, `definition.definition`
-  (S6).
-- **No OAI-PMH.** `/api/publications`, `/api/stats`, `/api/search`, `/policies`, `/how-it-works` all
-  404 (S6).
-- **Bulk metadata: use Crossref prefix `10.32388`** (175,165 records, including 57,288 peer reviews
-  with their own DOIs — an unusually rich open-review dataset) or OpenAlex source S4210177074
-  (S8, S10).
-- **Indexing:** the operator claims Europe PMC, Google Scholar and the NIH COVID-19 portfolio
-  (S12); Europe PMC independently returns 4,554 records (S11).
-- **No user-agent gating observed** — default `curl` returned HTTP 200 throughout (S6).
-
-### Negative controls (2026-09-01)
-
-| Probe | Result | Interpretation |
-|---|---|---|
-| `/api/publications/ZZZZZZ/published-reviews-of-any-versions` | **HTTP 404**, 6,603 B, `text/html` | Correct hard 404 — the API does not soft-fail. Good. |
-| `/api/publications/0DHKFR/published-reviews-of-any-versions` | HTTP 200, 10,742 B, `application/json` | Valid id returns real JSON. |
-| `/archive?type=bogus.type` | HTTP 200, **995 B**, no item count | Invalid facet returns a distinct 995-byte error body. |
-| `/archive?type=review` | HTTP 200, **995 B**, no item count | Byte-identical to the bogus probe ⇒ `review` is *not* a valid facet value; the correct value is `peer_review`. **This is exactly why negative controls matter** — without the bogus probe, "no count" would have looked like "zero reviews". |
-| `/archive?type=definition` | HTTP 200, 73,818 B, "106,486 items" | Valid facet. |
-
-## 9. Licensing and reuse
-
-- **CC BY 4.0 on everything** — articles, preprints, definitions and **peer reviews** (S4).
-  Copyright stays with authors and reviewers; Qeios takes a reproduction licence only.
-- **Data: CC0** under the Data Sharing policy (S4).
-- Qeios is a Crossref member and a **DORA signatory** (S4).
-- No paywalls, no registration required to read (S4).
-- **Preservation: not established.** The publishing policy has an "Archiving and Preservation"
-  section heading, but I did not retrieve its body text and found no named dark archive (Portico,
-  CLOCKSS, LOCKSS) on any page retrieved [NOT-VERIFIED]. Contrast Preprints.org and Research Square,
-  which both name Portico explicitly. **Treat durability as unproven.**
-
-## 10. Caveats and controversies
-
-1. **Qeios is mostly a dictionary.** 106,486 definitions vs ~4,400 articles. Do not infer research
-   scale from headline DOI counts (§3).
-2. **The dual-submission collision is real and documented** — see the Vishniac/AAS incident in §5.
-   If your paper is under review at a professional-society journal, letting Qeios recruit reviewers
-   may breach that journal's rules.
-3. **Reviewer supply is coupled to a paid subscription** (>98% of reviews come from the Pro
-   recruitment service) (S3).
-4. **No editorial reject power** — by design, but it means the only filter is four reviewers'
-   average scores at a low threshold.
-5. **The "median of 10 reviews / most peer-reviewed venue globally" claim is unaudited** (§5).
-6. **AI is pervasive in the pipeline; AI *authorship of reviews* is unverified** (§4). State the
-   distinction accurately.
-7. **Preservation arrangements unverified** (§9) — the highest durability risk of the five platforms
-   in this cluster after ScienceOpen.
-8. **The public API is undocumented** and may be withdrawn without notice (§8).
-
-## 11. Sources
-
-- **S1** — https://www.qeios.com/ · retrieved 2026-09-01 [WEB] · "Research you can trust", ISSN
-  2632-3834, four-domain layout, indexing claim, "Over 100,000 researchers already use Qeios".
-- **S2** — https://www.qeios.com/about · retrieved 2026-09-01 [DOC] · 100,000+/150+/200,000+ claims;
-  three-step model (AI pre-checks → AI-invited reviewers → peer-approved in 4 weeks); the ≥4 reviews
-  at ≥3/5 (≥2.5 novelty) threshold; revocable approval; "median of 10 peer reviews".
-- **S3** — https://www.qeios.com/plans · retrieved 2026-09-01 [DOC] · Free vs **Pro USD 24.99/mo**;
-  Reviewer Recruitment Service — *"These experts provide over 98% of Qeios reviews"*; unlimited
-  revisions; grammar correction; cover images; social promotion.
-- **S4** — https://www.qeios.com/publishing-policy · last updated 29 April 2025, retrieved 2026-09-01
-  [DOC] · aims and scope (Scopus ASJC), CC BY 4.0 + CC0 data, DORA, Crossref, authorship, **Use of
-  Generative AI**, competing interests, "How the Reviewing Process Works" (AI reviewer
-  identification; AI-assisted suitability check on spontaneous reviewers), rating mechanics,
-  evaluation standards, publication criteria and continuous scrutiny.
-- **S5** — https://www.qeios.com/preprints · retrieved 2026-09-01 [WEB] · domain and field filters
-  including Computer Science, Engineering, Mathematics, Materials Science, Energy.
-- **S6** — https://www.qeios.com/archive and `?type=` facet probes · retrieved 2026-09-01 [WEB] ·
-  counts for `definition` 106,486, `peer_review` 49,803, `article.preprint` 3,979,
-  `article.peer_approved` 392, `article` 4,372, `article.review` 393; negative controls
-  `bogus.type` and `review` both 995 B; 404s for `/policies`, `/how-it-works`, `/api/publications`,
-  `/api/stats`, `/api/search`.
-- **S7** — https://www.qeios.com/archive?type=article.preprint · retrieved 2026-09-01 [WEB] · live
-  listing incl. the Lean 4 formalisation and fraud-inference items, and same-author same-day posting.
-- **S8** — https://api.crossref.org/prefixes/10.32388/works?rows=0&facet=type-name:* · retrieved
-  2026-09-01 [API] · 175,165 total; Entry 109,765 · Peer Review 57,288 · Posted Content 6,111 ·
-  Journal Article 2,000 · Journal 1. Oldest records sampled: `10.32388/942977` ("Definition",
-  created 2018-09-07).
-- **S9** — https://www.qeios.com/ethics · retrieved 2026-09-01 [DOC] · separation of roles;
-  continuous scrutiny; misconduct monitoring; the AI / reviewers / editorial-team triad and the
-  explicit list of what the custom AI does.
-- **S10** — https://api.openalex.org/sources/S4210177074 · retrieved 2026-09-01 [API] · 6,879 works,
-  28,061 citations, ISSN-L 2632-3834, counts_by_year 2016–2026.
-- **S11** — https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=PUBLISHER:"Qeios" ·
-  retrieved 2026-09-01 [API] · hitCount 4,554.
-- **S12** — https://web.archive.org/web/20241227174226/https://www.qeios.com/about · snapshot
-  2024-12-27, retrieved 2026-09-01 [DOC] · "90,000+" researchers (vs 100,000+ now); identical
-  three-step AI description; Robert West endorsement *"It uses AI to find and invite reviewers"*
-  (also on the live home page, S1).
-- **S13** — https://en.wikipedia.org/wiki/List_of_preprint_repositories (wikitext via MediaWiki API)
-  · retrieved 2026-09-01 [COM] · Qeios row: ">1000", 2019, operator Qeios, cited to Coy P., *New
-  York Times*, 28 January 2022.
-- **S14** — https://www.qeios.com/api/publications/0DHKFR/published-reviews-of-any-versions ·
-  retrieved 2026-09-01 [API] · full review object schema incl. `borne_rating`,
-  `borne_subrating_for_*`, `declarations.coi`, `pre_grammar_correction_contents`, DOI
-  `10.32388/6JWF94`, named human reviewer with ORCID and institution.
-- **S15** — https://web.archive.org/web/20230206083212/https://www.qeios.com/about · snapshot
-  2023-02-06, retrieved 2026-09-01 [DOC] · 2023-era manifesto and ethics statement referring to
-  *"articles and definitions published on Qeios"*; editorial team list; no mention of AI-authored
-  reviews.
-- **S16** — https://api.crossref.org/prefixes/10.32388/works?filter=type:peer-review (cursor-paged,
-  3,000 records sampled) · retrieved 2026-09-01 [API] · zero records without an author; zero author
-  names matching AI/GPT/Chat/Bot/Qeios/Artificial/Machine/Assistant/Anonymous; top reviewers are
-  named researchers (Changqing Sun 10, Robert West 8, Clive Bates 7…).
-- **S17** — Mojeek searches for "Qeios AI-generated review ChatGPT", "Qeios review written by AI",
-  "Qeios artificial intelligence reviewer" · 2026-09-01 [COM] · no substantive result. (DuckDuckGo
-  HTML endpoint returned empty result sets to scripted clients on this date.)
-- **S18** — https://telescoper.blog/2024/12/15/qeios-and-the-nature-of-a-journal/ · Coles P., "Qeios
-  and the Nature of a Journal", 15 December 2024 · retrieved 2026-09-01 [COM] · reproduces in full
-  the six-part Bluesky thread by Ethan Vishniac (@ethan-vishniac.bsky.social, 2024-12-06) quoted in
-  §5, plus Coles's own analysis and a reader comment quoting Qeios's Version-of-Record wording.
-- **S19** — https://api.crossref.org/prefixes/10.32388/works?filter=type:posted-content&query.bibliographic=software+algorithm+network+hardware+FPGA
-  · retrieved 2026-09-01 [API] · **63 matching records total**; titles and DOIs listed in §6.
-- **S20** — https://api.crossref.org/prefixes/10.32388/works?filter=type:peer-review (sample) ·
-  retrieved 2026-09-01 [API] · e.g. `10.32388/kyv073`, *Review of: "Evaluating the Application of
-  SOLID Principles in Modern A…"*, Abdul Qayum, 2025-04-17.
diff --git a/research/preprint-repositories/recovering-dead-technical-sites.md b/research/preprint-repositories/recovering-dead-technical-sites.md
deleted file mode 100644
index 5bb6e9a..0000000
--- a/research/preprint-repositories/recovering-dead-technical-sites.md
+++ /dev/null
@@ -1,1107 +0,0 @@
-# Recovering dead technical sites — archives, mirrors and the order to try them
-
-- **Compiled:** 2026-09-02. Every figure below was measured on that date unless stated otherwise.
-- **Re-verified independently 2026-09-04** by a second pass that re-ran the load-bearing probes. Most
-  values reproduced **byte-for-byte** (see §12 S25); three findings were **corrected** and are marked
-  inline: the Wayback throttle ceiling and failure mode (§2.2), the CDX-vs-availability host split
-  (§2.3, strengthened), and archive.today's `/timemap/` endpoint (§7.4, previously recorded as
-  CAPTCHA-walled — it is not).
-- **The question:** *the datasheet / manual / tech report / forum thread I need is gone. Where is
-  the copy, and how do I get at it without being blocked?*
-- **Why this file is here.** The rest of this directory is about *preprint servers* — places that
-  are alive and want to be read. This file is about the opposite case, which is the more common one
-  in hardware work: `hpl.hp.com` is TCP-dead, `datasheetcatalog.com` is NXDOMAIN, Espressif has
-  silently withdrawn a datasheet, `parc.com/publications/` now redirects to a corporate division
-  page. Those are all *measured* facts from this repository, not hypotheticals — see
-  [`government-and-institutional-technical-reports.md` §4](government-and-institutional-technical-reports.md)
-  and the repository's [crawler access table](../../ai-crawler-site-access-table.md)
-  (§ Vendor documentation portals, § Electronics distributors).
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-- **Raw probe output:** [`../../scratch/preprint-repositories/bulk-archives/probe-log-2026-09-02.txt`](../../scratch/preprint-repositories/bulk-archives/probe-log-2026-09-02.txt)
-  and `waybackratelimit.txt` in the same directory; re-verification logs in
-  [`../../scratch/preprint-repositories/dead-sites/`](../../scratch/preprint-repositories/dead-sites/)
-  (`VERIFY-SUMMARY.md` plus `verify-01`…`verify-13`).
-
-> **Two corrections to this repository's own guidance are recorded here.** The
-> [crawler access table](../../ai-crawler-site-access-table.md#general-retrieval-tips) currently
-> recommends the **Memento Aggregator** (`timetravel.mementoweb.org`) — that host is **NXDOMAIN as
-> of 2026-09-02** and the service was shut down at the end of 2025 (§7.2). And
-> [`retrieval-notes.md`](retrieval-notes.md#6-rate-limits-and-terms) records "`web.archive.org/web/`
-> 429-blocks while the CDX API stays open"; that is **wrong in the way that costs you data**. The CDX
-> API is on the *same host* as replay and degrades with it — confirmed on two independent runs, in
-> both failure modes (§2.3). What stays open is `archive.org` (availability, metadata,
-> `advancedsearch.php`), which is a **different host**.
-
----
-
-## 1. The decision tree — the page is gone, do this in this order
-
-Run top to bottom. Stop when you have bytes with the right magic number.
-
-| # | Step | Cost | Catches |
-|---|---|---|---|
-| **0** | **Confirm it is actually gone.** Probe a deliberately bogus sibling path. A 200 with an SPA shell, a soft-404, or a UA-inverted block all look like "deleted" | one request | Most false alarms. See the three failure classes in the [crawler table](../../ai-crawler-site-access-table.md#vendor-documentation-portals) |
-| **1** | **`archive.org/wayback/available?url=<url>`** | one request, ~0.7–2.5 s | Is there *any* IA snapshot? Fast, on a **different host** to the replay service, and it survived every rate-limit window measured here (§2.2) |
-| **2** | **Wayback CDX** — `web.archive.org/cdx/search/cdx?url=…&output=json` | one request | The full capture list with status codes; `matchType=prefix` enumerates a whole dead directory (§2.3) |
-| **3** | **Replay with `id_`** — `web.archive.org/web/<ts>id_/<url>` | one request, **paced ≥1.5 s** | The original unmodified bytes. Mandatory for PDFs and binaries (§2.4) |
-| **4** | **Is it a *vendor manual or historical computing document*? → bitsavers** (§4) | grep one text file | DEC, IBM, HP, CDC, Data General, Xerox, plus 8,297 component datasheets. Wayback will not have these; bitsavers will |
-| **5** | **Is it an *archive.org item* rather than a web page?** `advancedsearch.php` + `metadata/<id>` (§3) | two requests | Scanned manuals, ROM dumps, CD-ROMs, magazines — 3.04 M items in `collection:"manuals"` alone |
-| **6** | **Is it *source code*? → Software Heritage** (§6) | one request | Whole repositories, including deleted GitHub/GitLab/Gitorious origins. 439 M origins |
-| **7** | **A different web archive** — Arquivo.pt first, then archive.today (§7) | one request | Arquivo.pt has captures IA lacks and a working CDX API. It replayed the dead HP Labs Compaq/DEC index for us |
-| **8** | **Common Crawl** — index + WARC byte-range (§7.5) | two requests | Machine-friendly, no rate limit hit here, and it holds **PDFs** — we pulled a 722 KB TI datasheet out of a WARC |
-| **9** | **Exact-string search** — a unique phrase, error message or part number, quoted | manual | Forks, mirrors, course pages, GitHub copies. Still the highest-yield manual step |
-| **10** | **A mirror of the *whole site*** — vendors' downstream partners, university mirrors, `mirrorservice.org`, `ftpmirror.your.org` | manual | Frequently the only route once the origin starts blocking bots (§4.4) |
-
-**Not on this list, deliberately:** Google cache and Bing cache. Both are dead as recovery routes
-in 2026 and §8 shows the measurements.
-
----
-
-## 2. The Internet Archive Wayback Machine
-
-### 2.1 The four endpoints, and which host each lives on
-
-This distinction is the single most operationally useful thing in this file, because the two hosts
-fail independently.
-
-| Endpoint | Host | Purpose |
-|---|---|---|
-| `archive.org/wayback/available?url=<url>` | **`archive.org`** | "Is there a snapshot, and which is closest?" JSON, tiny |
-| `web.archive.org/cdx/search/cdx?url=…` | `web.archive.org` | Enumerate **every** capture, with status codes |
-| `web.archive.org/web/<timestamp>/<url>` | `web.archive.org` | Replay, **rewritten** for browser display |
-| `web.archive.org/web/<timestamp>id_/<url>` | `web.archive.org` | Replay, **original bytes**, no rewriting |
-| `web.archive.org/save/<url>` | `web.archive.org` | Submit a capture (unauthenticated, heavily throttled) |
-
-Measured 2026-09-02 [API]:
-
-```
-archive.org/wayback/available?url=hpl.hp.com/techreports/Compaq-DEC/
-  -> 200, 246 B  {"archived_snapshots":{"closest":{"status":"200","available":true,
-                   "url":"http://web.archive.org/web/20190213111131/http://hpl.hp.com:80/techreports/Compaq-DEC/",
-                   "timestamp":"20190213111131"}}}
-
-archive.org/wayback/available?url=this-domain-does-not-exist-zzq9.example/
-  -> 200,  77 B  {"url":"...","archived_snapshots":{}}          <- clean negative control
-```
-
-**The availability API is scheme- and path-literal.** `roa.rutgers.edu/info.html` returns
-`{}` while `roa.rutgers.edu/` returns a 2026-07-11 snapshot. Query the exact URL you want, and if
-that is empty, fall back to a CDX prefix query before concluding anything.
-
-### 2.2 Rate limits, measured honestly
-
-This was probed deliberately because a sibling record left it half-documented, and **re-probed
-independently on 2026-09-04**, which changed the conclusion in three ways. All figures Chrome-131 UA,
-sequential `curl`, single IP [WEB]:
-
-| Pattern | 2026-09-02 run | 2026-09-04 re-probe |
-|---|---|---|
-| Rapid `/web/` replay GETs before the first failure | #1–3 → 200, then blocked | **#1–16 → 200**, blocked from #17 |
-| Mode of the block | **HTTP 429**, 620-byte body, `server: nginx`, `x-rl: 0`, `x-na: 0` — *"Your request is being blocked because our system has flagged it as suspected abusive bot traffic that is degrading the performance of the Wayback Machine."* | **TCP connection refused** (`curl` exit 7, `http_code` 000) in ~80–480 ms. **No 429 was seen once in ~60 requests** |
-| Recovery | still 000 at **+20 s**; 200 at **+60 s** | requests **flap** 200/000 within seconds (below) |
-| **6 GETs paced 1.5 s apart** | **6/6 → 200** | not re-run |
-| UA rotation during a block | Useless | Useless — and demonstrably so (below) |
-
-**Three corrections, and the third is the one that will corrupt a harvest:**
-
-1. **There is no fixed low quota.** "About three requests" was measured *inside an
-   already-throttled window* and is too pessimistic; the re-probe got **16 consecutive 200s** before
-   the block engaged. **Do not calibrate a scraper against either number** — the ceiling is a moving
-   server-side judgement, not a published quota.
-2. **429 and TCP-refusal are alternative modes, not an ordered escalation.** The first run saw only
-   429s then refusal; the second saw only refusal, never a 429. Handle both, and treat
-   `http_code == 000` on `web.archive.org` as *throttling*, not as *the Internet Archive is down*.
-3. **⚠ The throttled state flaps, so a partial success does not mean you are clear.** Identical
-   Chrome-131 requests, 1 s apart, on 2026-09-04:
-
-   ```
-   200 200 000 000 000 200 200 000 000 000
-   ```
-
-   **A bulk fetch running through a throttle window therefore yields a silent mixture of retrieved
-   and missing files, with no error that distinguishes "not archived" from "refused".** Verify every
-   file by magic bytes and re-drive the whole list until it is clean; never treat one 000 as a final
-   answer about a URL.
-
-**On UA rotation — the 2026-09-04 data settles it.** While blocked, `curl/8.5.0` and `ClaudeBot`
-returned 200 in the same second that `Googlebot/2.1`, `WhatsApp/2.23.20.0` and *no UA header at all*
-returned 000. That is not a UA policy, it is the flapping above sampled by different requests.
-**The Wayback throttle is not UA-gated — do not waste the `AGENTS.md` UA ladder on it.** (A UA table
-built from a single pass through a flapping service is exactly how a spurious "working user agent"
-gets recorded; this one nearly was.)
-
-> **Byte sizes on IA drift between days and are not stable fingerprints.** The same replay capture
-> measured **16,004 B** on 2026-09-02 and **16,006 B** on 2026-09-04; `metadata/tektronix_465` went
-> 4,438 → 4,437 B. Sizes quoted in this file are good for recognising a *class* of response (the
-> 620-byte 429, the 11,832-byte 503, the 283-byte bitsavers 403), not for equality tests.
-
-**Where `retrieval-notes.md` goes wrong:** it records that "`/web/` 429-blocks while the CDX API
-stays open." The CDX API lives on `web.archive.org` — the *same host as replay* — so when the replay
-service is throttled the CDX API degrades **with it**. This is why it is worth knowing which endpoint
-sits on which host, and it was confirmed on two independent runs, in both failure modes [WEB]:
-
-```
-                                              2026-09-02 (429 mode)   2026-09-04 (TCP-refusal mode)
-web.archive.org/cdx/search/cdx?url=bitsavers.org   000 (refused)          503, 11,832 B
-archive.org/wayback/available?url=hpl.hp.com/...   200,  246 B            200,    246 B
-archive.org/metadata/tektronix_465                 —                      200,  4,437 B
-archive.org/advancedsearch.php?q=…&rows=0          —                      200,    227 B
-```
-
-**Rule, now confirmed on two independent runs: everything on `web.archive.org` fails together, and
-everything on `archive.org` keeps working.** The availability API, the item metadata API and
-`advancedsearch.php` all survived a block that had `web.archive.org` refusing TCP connections.
-**Make `archive.org/wayback/available` your first call** — it answers in ~0.5 s, it is a clean
-existence oracle, and it is on the host that stays up.
-
-**A separate, unrelated failure to know about:** the CDX API intermittently returns
-**HTTP 503 with an 11,832-byte "Internet Archive: Temporarily Offline" page**. Frequency is high and
-variable — **1 of 3** identical requests on 2026-09-02, **2 of 3** on a cold 2026-09-04 run (the
-third succeeded in 16.7 s). It is a service-wide condition, **not** a statement about your URL.
-**Always retry a CDX 503 at least twice before concluding a URL has no captures**, or you will
-record "never archived" for a page that is archived. Response times for CDX were poor throughout:
-**5.2–16.7 s** for a 20-row query.
-
-### 2.3 The CDX API — the enumeration tool
-
-Base form, plus the parameters that actually earn their keep:
-
-```
-https://web.archive.org/cdx/search/cdx?url=<url>
-    &output=json                       # otherwise you get whitespace-separated text
-    &matchType=exact|prefix|host|domain
-    &filter=statuscode:200             # skip the 301/302/404 captures
-    &collapse=urlkey                   # one row per distinct URL, not per capture
-    &from=2004&to=2008                 # YYYY[MM[DD[hh[mm[ss]]]]]
-    &limit=500                         # and paginate; do not ask for everything
-    &fl=timestamp,original,statuscode,digest,length
-```
-
-Rows are `[urlkey, timestamp, original, mimetype, statuscode, digest, length]`. Worked example, the
-DEC/Compaq technical report index that this repository already established is dead at source [API]:
-
-```
-url=hpl.hp.com/techreports/Compaq-DEC/&output=json&limit=20   -> 200, 3,444 B
-  earliest  20021214042738  200  text/html  19,816 B
-  ...       20040102135157  301                406 B   <- note the 301s interleaved throughout
-  latest measured by the sibling record: 2022-05-17 (302), 2022-05-17 (301), 2022-12-22 (301)
-```
-
-Three things that CDX gives you and nothing else does:
-
-1. **`digest` is a SHA-1 of the payload.** Identical digests across timestamps mean the page did not
-   change — pick any one of them, and you can prove a capture is byte-identical to another without
-   downloading both. Five consecutive 2005 captures of the DEC index share digest
-   `YHLG3MDTKGZWUXHEZJZZUY3JOOTGORHI`.
-2. **`statuscode` lets you skip the redirect era.** The DEC index above was *already only a
-   redirect* by 2022. Without `filter=statuscode:200` you will happily replay a 301 and report the
-   collection as recovered.
-3. **`matchType=prefix` enumerates a directory you can no longer list.** This is how you rebuild a
-   dead vendor's `/docs/` tree: query the prefix, collapse on urlkey, and you get every path IA ever
-   saw — including ones you did not know existed.
-
-**Negative control:** `url=this-domain-does-not-exist-zzq9.example/` → **HTTP 200 with body `[]`
-(3 bytes)**. Clean. Status code is *not* the signal here; body length is.
-
-### 2.4 `id_` — the suffix you need for anything that is not HTML
-
-Wayback rewrites replayed HTML: it injects its own JavaScript, a toolbar, and rewrites every link to
-point back into the archive. For reading, that is fine. For **recovering a file**, it corrupts the
-bytes.
-
-| Suffix | Meaning | Measured on the same capture |
-|---|---|---|
-| *(none)* | Rewritten for display | 200, **16,004 B** |
-| `id_` | **`id`entity — original bytes, no rewriting** | 200, **13,237 B** |
-| `if_` | Framed replay (toolbar in an iframe) | — |
-
-The 2,767-byte difference is the injected `web-static.archive.org/_static/js/bundle-playback.js`
-machinery [WEB]. **For a PDF, a firmware image, a `.zip`, a CSV or a datasheet, always use `id_`,
-then check the magic bytes.** This repository has already been burnt by `.pdf` URLs returning HTML
-(LCSC, `documentation.espressif.com`) — a rewritten Wayback replay is the same hazard with a
-friendlier face.
-
-The existing note in the crawler table uses `if_` and it worked (a 470,491-byte ESP32-WROVER
-datasheet). `id_` is the stricter choice; prefer it.
-
-**Caveat measured here:** `id_` and `if_` are rate-limited exactly like plain replay. Our first two
-`id_` attempts returned the 620-byte 429 page *while a plain replay of the same capture succeeded*,
-purely because the plain one was requested first. From a cold start, `id_` returned 200 immediately.
-**Do not conclude that `id_` is blocked; conclude that you are throttled.**
-
-### 2.5 `web.archive.org/save/`
-
-Unauthenticated, works, and is the mechanism `AGENTS.md` rule 9 refers to. Known behaviour, carried
-forward from this repository's existing measurement rather than re-probed here [WEB]:
-
-- It has **timed out at 120 s and then returned HTTP 503** on retry — which reads as failure but may
-  not be. (Recorded in the crawler table, 2026-08-24.)
-- Anonymous submissions are throttled to roughly a few per minute.
-- **Query `archive.org/wayback/available` first.** In this pass, *every* archival candidate that was
-  still live turned out to be captured already (§10) — four checks, zero saves needed.
-
----
-
-## 3. archive.org at item level — a different archive that shares a domain
-
-The Wayback Machine and the archive.org *item* store are separate systems. Wayback holds web
-captures; the item store holds uploaded, catalogued objects: scanned manuals, magazines, ROM images,
-CD-ROMs, software. For hardware documentation the item store is frequently the better hit.
-
-### 3.1 Sizes, measured [API]
-
-`https://archive.org/advancedsearch.php?q=<query>&rows=0&output=json` → `response.numFound`:
-
-| Query | numFound |
-|---|---|
-| `mediatype:texts` | **52,096,704** |
-| `collection:"manuals"` | **3,040,530** |
-| `collection:"vintagesoftware"` | 335,219 |
-| `collection:"softwarelibrary"` | 273,718 |
-| `collection:"bitsavers"` | **91,398** |
-| `collection:"cd-roms"` | 86,584 |
-| `collection:"texts"` | **39,535** |
-| `collection:"folkscanomy_computer"` | 23,940 |
-| `collection:"computermanuals"` | 18,255 |
-| `title:(datasheet)` | 12,636 |
-| `collection:"bitsavers" AND subject:"DEC"` | 487 |
-
-> **Probing trap — `collection:"texts"` is not `mediatype:texts`.** They differ by a factor of
-> **~1,317** (39,535 vs 52,096,704). `texts` is a *mediatype*; there also happens to be a small
-> collection with the same name. Getting this wrong understates the archive by three orders of
-> magnitude.
->
-> **Probing trap — silent zeros.** `collection:"zzq9nosuchcollection"` returns **HTTP 200 with
-> `numFound: 0`**, indistinguishable from a genuinely empty real collection. Same class as the
-> Zenodo facet trap in [`README.md §4`](README.md#6-probing-traps). Always run a known-good query
-> alongside.
-
-### 3.2 The `metadata/<id>` endpoint
-
-`https://archive.org/metadata/<identifier>` returns the complete file manifest with no
-authentication. Worked example [API]:
-
-```
-archive.org/metadata/tektronix_465    -> 200, 4,438 B
-  metadata.title      "Tektronix Manual: 465"
-  metadata.mediatype  texts
-  metadata.collection ["manuals_tektronix", "manuals"]
-  metadata.addeddate  2016-01-02
-  metadata.uploader   sketch@cow.net          <- note: a private individual, not Tektronix
-  files (14):  465.pdf                31,597,373 B   Image Container PDF
-               465_text.pdf           87,710,344 B   Additional Text PDF
-               465_djvu.txt              695,458 B   <- the OCR layer, as plain text
-               465_jp2.zip           392,156,276 B   page images
-               tektronix_465_archive.torrent  24,994 B
-```
-
-**Negative control:** `archive.org/metadata/zzq9-no-such-item-exists-here` → **HTTP 200 with body
-`{}` (2 bytes)**. Status code carries no information; test for the empty object.
-
-Files come from `https://archive.org/download/<id>/<file>` (302s to a regional node such as
-`dn760005.eu.archive.org`). A missing filename returns a **real 404** (548 B) — that endpoint at
-least is honest.
-
-### 3.3 Worked example: finding a vendor manual, and why you must read the metadata
-
-`advancedsearch.php?q=title:(tektronix 465)&fl[]=identifier&fl[]=title&fl[]=collection&rows=8&output=json`
-→ 14 hits [API]. Four of the eight returned rows are 3D-printer models from `thingiverse`. Two more:
-
-```
-manualsonline-id-3d483d5c-…   "Tektronix Fish Finder 465 AND DM44 User Guide"
-manualsbase-id-660252          "Tektronix Hunting Equipment TAS 465 user manual"
-```
-
-Those are the **Tektronix 465 oscilloscope** and the **TAS455/465**, bulk-imported from
-manuals-aggregator sites that guessed the product category. The documents are real; the metadata is
-fiction. This is the single most important thing to understand about bulk manual collections:
-**the scan is usually trustworthy, the catalogue record often is not.**
-
-The OCR is worse. The first 400 characters of `465_djvu.txt`, a real Tektronix service manual:
-
-```
-BEFORE READING  PLEASE CHECK FOR CHANGE INFORMATION AT THE REAR OF THIS MANUAL.
-THIS MANUAL REPRINTED JULY 1975
-:: V [-vlj.ln r L -  i"a K x-;-.-  r'|'“ , p ■ '"I E. : . J" 51  1!7 ‘■vi:
-```
-
-Headings survive; body text collapses into noise wherever the scan hit a schematic or a halftone.
-**Never quote a figure from an archive.org OCR layer without opening the page image.**
-
----
-
-## 4. bitsavers.org — the one that matters most
-
-- **URL:** `https://www.bitsavers.org/` (apex `bitsavers.org` serves identically, 9,377 B)
-- **Operator:** **Al Kossow**, personally. Not an institution, not a foundation, not a company.
-- **Status:** active, continuously updated — most recent file in the PDF tree on the probe date was
-  **2026-08-27** [WEB]
-- **Self-declared size (home page, dated 2026-05-10):** *"There are over 188000 files including over
-  8.86 million text pages in the 1.86tb archive."* [DOC]
-
-If you work on hardware older than about fifteen years, bitsavers is not *an* archive, it is *the*
-archive. DEC, IBM, HP, CDC, Data General, Burroughs, Univac, Honeywell, Xerox, Apple, Tektronix,
-Intel, National Semiconductor, Motorola — manuals, schematics, field-service documentation, ISA
-references, component data books, program listings. This repository has already had one case where
-bitsavers was **the only surviving copy** of a corporate research collection (§4.5).
-
-### 4.1 Layout
-
-Six top-level trees, each independently indexed:
-
-| Tree | `IndexByDate.txt` | Files listed | What it is |
-|---|---|---|---|
-| `/pdf/` | 8,578,234 B | **93,668** | Manuals, tech reports, schematics — the main archive |
-| `/bits/` | 4,978,120 B | **70,762** | Software: tape images, disk images, source listings, OS distributions |
-| `/components/` | 620,925 B | **8,297** | **Semiconductor data books and datasheets** |
-| `/test_equipment/` | 243,303 B | 3,210 | Instrument service manuals |
-| `/magazines/` | 195,210 B | 2,996 | Trade press |
-| `/communications/` | 141,265 B | 1,808 | Telecom / networking |
-| | | **180,741** | total lines across the six indexes [API] |
-
-`/pdf/` alone contains **1,132 vendor directories** (`3M/` … `zilog/`), served as plain Apache
-directory indexes. File-type mix in the PDF tree: 68,941 `.pdf`, 13,532 `.jpg`, 3,041 `.tif`,
-2,378 `.bin` (ROM dumps), 1,734 `.dat`, 969 `.txt`, 469 `.zip`. The date range in
-`pdf/IndexByDate.txt` runs **1997-05-14 → 2026-08-27** — twenty-nine years of continuous scanning.
-
-Largest vendor directories in `/pdf/`, by file count [API]:
-
-| dec | ibm | mit | hp | cdc | xerox | stanford | apple | burroughs | datapro | univac | honeywell |
-|---|---|---|---|---|---|---|---|---|---|---|---|
-| 22,089 | 15,860 | 3,622 | 2,473 | 2,291 | 1,998 | 1,822 | 1,802 | 1,658 | 1,476 | 1,362 | 965 |
-
-And in `/components/` — this is the part people miss:
-
-| national | motorola | ti | intel | amd | xilinx | westernDigital | nec | fairchild | signetics |
-|---|---|---|---|---|---|---|---|---|---|
-| 909 | 751 | 658 | 460 | 236 | 179 | 172 | 147 | 141 | 127 |
-
-**If you need a 1980s National Semiconductor or Signetics part, look here before you look anywhere
-else.** The commercial datasheet aggregators (§5) have largely dropped pre-1995 parts.
-
-### 4.2 How to search it — there is no search box
-
-Kossow says so himself on the home page: *"I have been disappointed in how poorly bitsavers is
-indexed in the modern web. So it goes."* [DOC] There is no search form, no database, no JavaScript.
-The site is deliberately a static tree so that it can be mirrored byte-for-byte.
-
-**The technique is to download the index and grep it locally.** This is the single most useful
-practical fact in this file:
-
-```bash
-# One 8.5 MB download gives you the complete manifest of the PDF tree.
-curl -A "$BROWSER_UA" -o idx-pdf.txt        https://www.bitsavers.org/pdf/IndexByDate.txt
-curl -A "$BROWSER_UA" -o idx-components.txt https://www.bitsavers.org/components/IndexByDate.txt
-
-# Format: "YYYY-MM-DD HH:MM:SS <path-relative-to-tree-root>"
-grep -i 'signetics.*8x30' idx-components.txt
-grep -i 'dec/tech_reports/SRC-RR' idx-pdf.txt | wc -l      # 170
-
-# Path -> URL is a straight concatenation:
-#   https://www.bitsavers.org/pdf/<path>
-```
-
-`IndexByDate.txt` is regenerated on every addition and is what drives the RSS feeds
-(`bitsavers.org/rss/{pdf,bits,comp,mags,comms,te}.xml`; the PDF feed was 185,936 B, `pubDate`
-2026-08-27) [WEB]. Sorting by date also means the *top* of the file is the newest material, which is
-how you monitor the archive without polling directory listings.
-
-Two supplementary techniques:
-
-- **`rsync --list-only`** gives a directory listing with sizes and mtimes without transferring
-  anything: `rsync --list-only rsync://bitsavers.org/bitsavers/pdf/dec/tech_reports/` returned
-  **522 entries** [API]. Cheaper and more informative than scraping the Apache index.
-- **Some directories carry embedded Adobe Acrobat index files** for full-text search across their
-  OCR layers — Kossow mentions this for "directories with large numbers of OCRed pdf files" [DOC].
-  Not machine-probed here: **[NOT-VERIFIED]** which directories have them.
-
-### 4.3 The retrieval trap: bitsavers 403s `curl` and `Wget`
-
-Measured 2026-09-02, and it is an inverted ladder [WEB]:
-
-| User-Agent | `/pdf/dec/tech_reports/` |
-|---|---|
-| `Wget/1.21.4` | **403**, 283-byte Apache "Forbidden" |
-| `curl/8.21.0` (default) | **403**, 283 B |
-| Chrome 131 | **200** |
-
-`robots.txt` is **HTTP 200 with a zero-byte body** — it expresses no restriction at all, so a naive
-crawler sees an open invitation and then gets a 403 on the first fetch.
-
-**This is not a bot-wall to be routed around; it is a stated policy.** The home page, dated
-2026-05-10 [DOC]:
-
-> *"As of April, 2026 due to the level of web traffic, Wget is no longer permitted here. […] People
-> are downloading the ENTIRE site through the web interface. The situation has gotten much worse
-> since the LLM web scrapers have appeared. USE ANONYMOUS RSYNC.. That's what it's there for!"*
-
-`AGENTS.md` rule 7 forbids UA substitution to bypass access controls, and rule 5 warns against
-masking genuine behaviour. **The correct reading here: a browser UA is fine for fetching the handful
-of documents a human would fetch; it is not a licence to bulk-download.** For anything at volume,
-the operator has provided two better routes and asks you to use them.
-
-### 4.4 Mirrors and rsync — the sanctioned bulk routes
-
-`rsync://bitsavers.org/` advertises six modules [API]:
-
-```
-bitsavers    The bitsavers.org archive
-vtda-bits    The vtda.org software archive     vtda-books   The vtda.org book archive
-vtda-docs    The vtda.org document archive     vtda-pics    The vtda.org image archive
-vtda-pubs    The vtda.org publications archive
-```
-
-Full clone, as documented by the operator: `rsync -av --delete rsync://bitsavers.org:/bitsavers/ bitsavers/`.
-`--delete` is required because, in Kossow's words, *"file names, dates and their location in the
-hierarchy change (these aren't permalinks)"* [DOC]. **Treat every bitsavers URL you cite as
-potentially unstable** and record the file name and size, not just the path.
-
-All seven advertised web mirrors were reachable on the probe date [WEB]:
-
-| Mirror | Root page |
-|---|---|
-| `bitsavers.computerhistory.org` (Computer History Museum) | 200, 9,377 B |
-| `bitsavers.informatik.uni-stuttgart.de` | 200, 9,377 B |
-| `bitsavers.trailing-edge.com` | 200, 9,377 B |
-| `www.mirrorservice.org/sites/www.bitsavers.org/` (University of Kent) | 200, 9,377 B |
-| `www.bighole.nl/pub/mirror/www.bitsavers.org/` | 200, 9,377 B |
-| `archive.decromancer.ca/bitsavers.org/` | 200, 9,377 B |
-| `ftpmirror.your.org/pub/misc/bitsavers/` | 200, **7,584 B** (different index page, not the origin's) |
-
-Plus rsync mirrors at `eldanna.ocaml.nl`, `ftpmirror.your.org` and `ftpmirror.infania.net`, and FTP
-at Stuttgart, Kent and your.org.
-
-**The finding that matters:** the mirrors do **not** apply the origin's `curl`/`Wget` 403.
-`mirrorservice.org`, `trailing-edge.com` and `uni-stuttgart.de` all returned **200 to the default
-`curl` UA** on `/pdf/dec/tech_reports/` [WEB]. And `ftpmirror.your.org`'s `pdf/IndexByDate.txt` was
-**byte-identical to the origin's** (8,578,234 B, 93,668 lines, same first line). **So the answer to
-the bitsavers bot-block is a mirror, not a user-agent — and that is also what the operator wants.**
-
-### 4.5 Case study: the DEC SRC/WRL/CRL series exists only here
-
-The companion record
-[`government-and-institutional-technical-reports.md` §4.2](government-and-institutional-technical-reports.md)
-established that DEC's research-lab report series — SRC (Systems Research Center), WRL (Western
-Research Lab), CRL (Cambridge), PRL (Paris), NSL (Network Systems Lab) — lost its host when
-`hpl.hp.com/techreports/Compaq-DEC/` went TCP-dead, and that the directory was **already only a
-redirect by 2022**. That is confirmed independently above (§2.3): every CDX capture from 2004 onward
-includes 301s, and the last three captures are 302/301/301.
-
-**This pass re-derived the bitsavers holdings by a different method** — counting prefixes in
-`pdf/IndexByDate.txt` rather than parsing the Apache directory listing — and got the same numbers
-[API]:
-
-| Prefix | This pass (index) | Sibling record (dir listing) | Series |
-|---|---|---|---|
-| `SRC-RR-` | **170** | 170 | SRC Research Reports |
-| `SRC-TN-` | **67** | 67 | SRC Technical Notes |
-| `WRL-` (excl. TN) | **108** | 108 | Western Research Lab |
-| `WRL-TN-` | **42** | 42 | WRL Technical Notes |
-| `CRL-` | **91** | 91 | Cambridge Research Lab |
-| `PRL-RR-` | **35** | 35 | Paris Research Lab |
-| `NSL-*` | **7** | 7 (4+2+1) | Network Systems Lab |
-| | 521 lines total in `dec/tech_reports/` | | |
-
-Two independent methods agreeing is worth more than either alone; **treat these counts as
-confirmed.**
-
-And the object that makes the whole thing safe:
-
-```
-dec/tech_reports/Compaq-DEC_TRs_HPL_mirror_2007.zip     236,085,636 B   indexed 2023-09-04
-```
-
-**Somebody took a copy of HP Labs' hosted collection in 2007. That ZIP is now the reason the
-collection exists.** HP never announced the removal; the directory quietly degraded to a redirect
-some time before 2022 and then the host stopped answering entirely.
-
-Spot check, with a negative control [WEB]:
-
-```
-/pdf/dec/tech_reports/SRC-RR-1.pdf       -> 200, 2,239,056 B, magic "%PDF-1.2"
-/pdf/dec/tech_reports/SRC-RR-99999.pdf   -> 404, 280 B
-```
-
-bitsavers returns **honest 404s** — class (a) in the crawler table's three-class taxonomy. A 200
-from this host really does mean the file exists. That is rarer than it should be.
-
-### 4.6 Bitsavers on archive.org, and what it is not
-
-`collection:"bitsavers"` on archive.org holds **91,398 items** (§3.1) — a partial, item-ised mirror,
-useful because it is full-text searchable and IA-hosted, but **it is not the same corpus** as the
-188,000-file live tree and there is no guarantee of currency. Use it for discovery; fetch from
-bitsavers or a mirror.
-
-Two limitations to state plainly:
-
-- **Scans, not text.** Kossow's format is *"a minimal subset of PDF […] just using it as a container
-  for lossless Group 4 fax compression (ITU-T T.6) images"*, scanned at 400 dpi (600 dpi since the
-  2010s), with OCR *"slowly being applied to older pdf files […] it will take many years to
-  complete"* [DOC]. **Many bitsavers PDFs have no text layer at all.** Grep will not find them.
-- **The originals are destroyed.** *"The scanning process I use is destructive. Bindings are removed
-  and paper is recycled."* Documents in good condition may go to the Computer History Museum (lot
-  `X6512.2012`) [DOC]. This is a one-shot archive: what was scanned is what survives.
-
----
-
-## 5. Component and datasheet archives — reliability assessment
-
-Measured 2026-09-02, Chrome-131 UA [WEB]:
-
-| Site | Result | Verdict |
-|---|---|---|
-| **`bitsavers.org/components/`** | 200 (browser UA), **8,297 files** | **First choice for pre-1995 parts.** Provenance is a named archivist and a scan; the vendor is the directory name |
-| **`datasheetarchive.com`** | 200, 41,998 B; `/?q=lm317` → 200, 239,746 B of real results | Open to scripts. Results carry manufacturer + description + ECAD model. **Zero direct `.pdf` hrefs in the HTML** — downloads are JS-driven, so you cannot enumerate PDFs by scraping |
-| **`alldatasheet.com`** | **403**, 5,603 B (search page 5,714 B) | Cloudflare. The **~5.6 kB 403 fingerprint** documented in [`retrieval-notes.md §1`](retrieval-notes.md) — alive, refusing robots. UA rotation did not defeat it there and there is no reason to expect it to here |
-| **`datasheets.com`** | **403**, 5,601 B | Same fingerprint |
-| **`datasheets360.com`** | **403**, 5,625 B | Same fingerprint |
-| **`octopart.com`** | **403**, 51,989 B | Already recorded in the crawler table: *"a 52 KB 403 body that superficially looks like content"* |
-| **`datasheetcatalog.com`** | **NXDOMAIN** (apex and `www`) | **Dead.** A widely-cited datasheet host that no longer resolves at all |
-| **`chipdb.org`** | 200, 71,622 B | **Not a datasheet site.** A die/package *photograph* database — *"6392 images in 1222 categories"* — attached to the cpu-world.com forum. Excellent for identifying an unmarked or remarked chip; useless for electrical specifications |
-
-### 5.1 Why an aggregator datasheet is weaker evidence than it looks
-
-Four failure modes, all of which this repository has hit:
-
-1. **Mis-OCR.** §3.3 shows what an OCR layer does to a scanned instrument manual. A single-character
-   error in a scanned datasheet turns 3.3 V into 8.3 V and nothing flags it.
-2. **Mislabelling.** archive.org's own catalogue calls a Tektronix oscilloscope manual a *"Fish
-   Finder"* user guide (§3.3). Aggregators that bulk-import from other aggregators inherit and
-   compound this.
-3. **Wrong revision, silently.** A part is documented across revisions A/B/C with different absolute
-   maximum ratings; the aggregator keeps whichever it scraped and rarely says which.
-4. **AI-generated prose presented as specification.** Already recorded in the crawler table:
-   `digi-electronics.com` *"misstated a chip's operating temperature by 20 °C against the
-   manufacturer datasheet."* Use the tables, discard the paragraphs.
-
-**Rule for this knowledge base:** an aggregator datasheet is a *lead*, not a source. Resolve it to
-(a) the manufacturer's own file, (b) a distributor mirror with a traceable part code — the crawler
-table's LCSC finding, `datasheet.lcsc.com/lcsc/<id>_<Manufacturer>-<Part>_C<NNNNN>.pdf`, is
-unusually good on this because the filename carries the provenance — or (c) bitsavers, where the
-directory *is* the vendor attribution. Record the byte size and the revision string from the cover
-page.
-
----
-
-## 6. Software Heritage — the archive of source code
-
-- **URL:** `https://archive.softwareheritage.org/` · API base `/api/1/`
-- **Operator:** Inria, with UNESCO under a formal agreement; a public-interest, non-profit archive
-- **What it archives:** *source code with its full development history* — not web pages, not
-  binaries, not releases-as-tarballs. Git, Mercurial, SVN, Debian source packages, and more.
-
-### 6.1 Scale, measured [API]
-
-`GET /api/1/stat/counters/`, 2026-09-02:
-
-| Counter | Value |
-|---|---|
-| `origin` (distinct repository URLs ever ingested) | **439,088,634** |
-| `origin_visit` | 2,002,159,594 |
-| `content` (unique file blobs) | **29,475,358,773** |
-| `directory` | 22,958,659,572 |
-| `revision` (commits) | **6,103,072,139** |
-| `release` | 183,390,908 |
-| `snapshot` | 402,766,238 |
-| `skipped_content` | 637,206 |
-
-It is actively crawling: `https://github.com/torvalds/linux` was on **visit #478, 2026-09-02
-03:44:11 UTC, status `full`** — a few hours before this probe [API].
-
-### 6.2 SWHIDs
-
-A **SWHID** (SoftWare Heritage persistent IDentifier) is an intrinsic, content-addressed
-identifier: `swh:1:<type>:<hex>` where type is `cnt` (file), `dir`, `rev`, `rel`, `snp` or `ori`.
-Because the hash is computed *from the content*, a SWHID does not depend on the archive continuing
-to exist — anyone with the bytes can recompute it. That is a categorically stronger citation than a
-DOI, which is a promise by a registry. `swhid.org` records the identifier as **standardised as
-ISO/IEC 18670**, on top of two earlier Publicly Available Specifications [DOC] (S24).
-
-```
-GET /api/1/resolve/swh:1:cnt:94a9ed024d3859793618152ea559a168bbcbb5e2/
-  -> 200  {"object_type":"content", "browse_url":".../browse/content/sha1_git:94a9ed…/"}
-GET /api/1/resolve/swh:1:cnt:0000000000000000000000000000000000000000/
-  -> 404, 131 B  {"exception":"NotFoundExc","reason":"Content with sha1_git … not found!"}
-```
-
-The negative control 404s properly, so `/resolve/` **is** an existence oracle [API]. Other useful
-endpoints: `/api/1/origin/search/<query>/`, `/api/1/origin/<url>/get/`, `/api/1/origin/<url>/visits/`,
-`/api/1/snapshot/<id>/`, and `/api/1/vault/` for reconstructing a whole directory as a tarball.
-
-**Trap:** `origin/search/torvalds%2Flinux/?limit=5` did **not** return `github.com/torvalds/linux`
-in its top five — it returned two dead Gitorious mirrors and three unrelated forks [API]. The search
-ranking is poor. If you know the URL, use `origin/<url>/get/`, which resolved instantly. A bogus
-search returns `[]` (2 bytes) with HTTP 200.
-
-### 6.3 The access trap — the UA ladder runs backwards here
-
-Software Heritage sits behind **Anubis**, a JavaScript proof-of-work wall (the same class of
-obstacle recorded for EconStor and hprints in
-[`retrieval-notes.md §3`](retrieval-notes.md#3-proof-of-work-walls-defeat-the-ua-ladder-entirely)).
-Measured against `/api/1/origin/search/torvalds%2Flinux/?limit=3` [WEB]:
-
-| User-Agent | Result |
-|---|---|
-| Chrome 131 | **200, 4,667 B — Anubis challenge page** (`<title>Making sure you're not a bot!</title>`) |
-| Firefox 128 | 200, 4,626 B — Anubis challenge |
-| ClaudeBot | **403**, 508 B |
-| `curl/8.21.0` (default) | **200, 1,643 B — real JSON** |
-| `WhatsApp/2.23.20.0` | **200 — real JSON** |
-| `Googlebot/2.1` | **200 — real JSON** |
-| *(no `User-Agent` header at all)* | **200 — real JSON** |
-
-**Escalating to a browser UA breaks the SWH API.** This is the second confirmed inversion in this
-repository after `nxp.com`, and it is worth a line in the crawler table: *when a site serves a
-proof-of-work interstitial, the browser UA is what triggers it.* Send nothing, or send `curl`.
-
-Note also that the challenge arrives with **HTTP 200**, so a status-code check reports success. Test
-for the string `not a bot` or parse the JSON and fail loudly.
-
-*(`www.softwareheritage.org` — the organisation's marketing site, distinct from the archive — failed
-TLS verification in this environment: "unable to get local issuer certificate". The same happened on
-`webarchive.org.uk`, whose certificate is a valid DigiCert chain expiring 2027-02-24. **That is a
-gap in this machine's CA store, not a site fault.** Recorded so nobody repeats the misdiagnosis.)*
-
-### 6.4 Relationship to Zenodo
-
-Zenodo pushes eligible software deposits into Software Heritage — see
-[`zenodo.md` § Software Heritage](zenodo.md). The division of labour is worth stating because people
-routinely pick the wrong one:
-
-| You want | Use |
-|---|---|
-| A **citable DOI** for a release of your firmware, with a version and authors | **Zenodo** |
-| The **complete history** of a repository, including the commits nobody released | **Software Heritage** |
-| Proof that a specific *file* existed with specific *content* | **SWHID** — intrinsic, verifiable offline |
-| A repository that has been **deleted from GitHub** | **Software Heritage** (Zenodo only has what was deposited) |
-
-For hardware work the last row is the important one: firmware, board-support packages and vendor SDKs
-disappear from GitHub constantly, and SWH is usually the only place the history survives.
-
----
-
-## 7. Other web archives
-
-### 7.1 Summary, measured 2026-09-02
-
-| Archive | Reachable? | API | Accepts save requests? |
-|---|---|---|---|
-| **Internet Archive** | ✅ (throttled, §2.2) | CDX + availability + item APIs | **Yes** — `web.archive.org/save/<url>`, unauthenticated |
-| **Arquivo.pt** (Portuguese Web Archive) | ✅ **best-behaved of the lot** | Memento TimeMap, CDX (`/wayback/cdx`), `/textsearch` | **Yes** — `arquivo.pt/services/savepagenow` **302s to `/services/archivepagenow`**, a working "ArchivePage Now" form (200, 18,183 B). Verified as *present*; not exercised |
-| **archive.today** (`.ph` / `.is`) | ⚠️ partial | **`/timemap/` works** (Memento, 5/5); `/newest/` is CAPTCHA-walled (§7.4) | Yes, but interactively only |
-| **Common Crawl** | ✅ | CDX index + WARC byte-range on S3 | **No.** Crawl-only, no submission |
-| **UK Web Archive** (British Library) | ❌ **service down** | — | No |
-| **Library of Congress web archives** | ❌ 403 Cloudflare | — | **[NOT-VERIFIED]** |
-| **Bibliotheca Alexandrina IA mirror** | ❌ TCP timeout | — | No |
-| **Memento Aggregator** (`timetravel.mementoweb.org`) | ❌ **NXDOMAIN — service shut down 2025** | — | — |
-
-### 7.2 The Memento Aggregator is gone — correct your notes
-
-`timetravel.mementoweb.org` is **NXDOMAIN**, as are `www.`, `labs.` and `aggregator.mementoweb.org`
-[WEB]. The apex `mementoweb.org` resolves and serves a 2,826-byte static stub. Its `/about/` page
-(8,269 B) says why [DOC]:
-
-> *"This website launched in 2009 and was operated and funded by the Research Library of the Los
-> Alamos National Laboratory. As a result of a managerial decision, the site was taken down towards
-> the end of 2025. The current static site, brought online in 2026, contains resources resurrected
-> from the original site […] It is operated on a volunteer basis and is hosted as Github Pages. The
-> site used to provide two services that were necessarily discontinued as a result of the forced
-> migration: The **Time Travel** service was a Memento aggregator that allowed searching across a
-> wide range of public web archives, providing both a user interface and an API. It operated between
-> 2015 and 2025 […] The **Robust Links** service […]"*
-
-**Consequences:**
-
-- The recommendation in
-  [`ai-crawler-site-access-table.md` § General retrieval tips](../../ai-crawler-site-access-table.md#general-retrieval-tips)
-  to use `http://timetravel.mementoweb.org/api/json/<timestamp>/<url>` **no longer works and should
-  be removed or annotated.** It is staged for that in §10.
-- **The Memento *protocol* is unaffected.** RFC 7089 datetime negotiation is implemented by the
-  individual archives, and per-archive TimeMaps still work — Arquivo.pt's did, below. What is gone
-  is the one service that queried them all at once. Until something replaces it, **cross-archive
-  search is a manual loop over a list of archives.**
-- This is itself a textbook instance of what this file is about: a decade-old piece of public
-  research infrastructure removed by an internal management decision, with no successor and no
-  notice.
-
-### 7.3 Arquivo.pt — the underrated one
-
-The Portuguese national web archive. Nominally national in scope, in practice it crawled a great deal
-of the international web and it holds captures the Internet Archive's replay throttle makes awkward
-to reach. It also has **the most script-friendly interface of any archive probed here** — no UA
-games, no CAPTCHA, fast.
-
-Worked example, on the exact resource this repository lost [API]:
-
-```
-GET /wayback/cdx?url=hpl.hp.com/techreports/Compaq-DEC/&output=json&limit=5   -> 200, 1,590 B
-  {"urlkey":"com,hp,hpl)/techreports/compaq-dec","timestamp":"20081022115306",
-   "status":"200","length":"24883","filename":"IAH-20081022114828-07684-T1.arc.gz",
-   "collection":"AWP3", ...}
-
-GET /wayback/20081022115306mp_/http://www.hpl.hp.com/techreports/Compaq-DEC/  -> 200, 97,670 B
-  "HP Labs : Compaq & DEC … Compaq & DEC Technical Reports » 2008 » 2007 » … » 1990 - 1999
-   Heritage Technical Reports » Compaq & DEC Technical Reports » Tandem Technical Reports
-   The Technical Reports appearing on this page were published by Compaq & DEC from 1981-2002."
-```
-
-**That is the dead HP Labs index, recovered from a Portuguese archive.** Note the replay suffix is
-`mp_`, not `id_`. Negative control: a TimeMap for a nonexistent domain → **HTTP 404, 0 bytes** —
-clean. There is also `/textsearch?q=<query>&maxItems=N`, a JSON full-text search over archived
-content with an `estimated_nr_results` field.
-
-**Also note:** Arquivo.pt holds captures of `hpl.hp.com` from **2008 and 2009**, when the collection
-was live and complete. IA's captures of the same path degrade to redirects from 2004 onward. For a
-resource that died slowly, *a second archive is not redundancy — it is a different point in time.*
-
-### 7.4 archive.today
-
-Reachable at `archive.today`, `archive.ph` and `archive.is` — all three returned an identical
-16,590-byte root page [WEB]. It is genuinely valuable for JavaScript-heavy pages, which the Wayback
-Machine captures poorly, because it stores a rendered snapshot.
-
-**Correction (re-probed 2026-09-04): it *does* have a machine-usable discovery endpoint.** The
-2026-09-02 pass recorded "every lookup path CAPTCHA-walled / no API". That is wrong for
-`/timemap/`, which is a standard RFC 7089 Memento TimeMap and answered cleanly **5 times out of 5**,
-no CAPTCHA, plain Chrome UA [API]:
-
-```
-GET https://archive.ph/timemap/https://www.bitsavers.org/     -> 200, 1,497 B, 5/5 attempts
-  <https://www.bitsavers.org/>; rel="original",
-  <http://archive.md/timegate/https://www.bitsavers.org/>; rel="timegate",
-  <http://archive.md/20120731064623/http://www.bitsavers.org/>; rel="first memento";
-      datetime="Tue, 31 Jul 2012 06:46:23 GMT",
-  <http://archive.md/20180514014300/…>; rel="memento"; …   (and so on)
-```
-
-**So the split is discovery vs retrieval:**
-
-| Path | Result 2026-09-04 | Usable from a script? |
-|---|---|---|
-| `/timemap/<url>` | **200, 1,497 B, real Memento TimeMap** | **Yes** |
-| `/newest/<url>` | **429 + 63,290-byte CAPTCHA** (*"One more step — Please complete the security check"*; 55,512 B on 2026-09-02) | No |
-
-**This matters more than it looks.** With the Memento Aggregator dead (§7.2), `/timemap/` is the one
-remaining way to ask archive.today *"do you have this, and from when?"* without a browser — which is
-exactly the question you need answered before deciding whether it is worth opening one. Enumerate
-with `/timemap/`, then fetch the specific memento by hand. Operator identity and funding remain
-undisclosed, there is still no documented API, and the endpoint is undocumented and could go at any
-time — **do not build an unattended pipeline on it**, but do use it interactively.
-
-### 7.5 Common Crawl — the one that holds PDFs
-
-Not a web archive in the preservation sense — a crawl corpus published for research — but it is
-**the best machine-accessible route to a recently-dead URL**, and unlike the Wayback Machine it did
-not throttle at all here.
-
-`https://index.commoncrawl.org/collinfo.json` → 200, 34,947 B, **127 collections** from
-**CC-MAIN-2026-34 (August 2026)** back to **CC-MAIN-2008-2009** [API].
-
-The full recovery, end to end, verified on a TI datasheet [API]:
-
-```bash
-# 1. Query the index for the crawl you want.
-curl "https://index.commoncrawl.org/CC-MAIN-2026-34-index?url=www.ti.com%2Flit%2Fds%2F*&output=json&limit=3"
-# -> {"url":"https://www.ti.com/lit/ds/sbos264a/sbos264a.pdf","mime":"application/pdf",
-#     "status":"200","length":"660220","offset":"905907244",
-#     "filename":"crawl-data/CC-MAIN-2026-34/segments/…/CC-MAIN-…-00755.warc.gz"}
-
-# 2. Range-GET exactly that record out of the WARC. No S3 credentials needed.
-curl -r 905907244-906567463 -o rec.warc.gz "https://data.commoncrawl.org/crawl-data/…-00755.warc.gz"
-# -> HTTP 206, 660,220 bytes
-
-# 3. Decompress: WARC header, then the HTTP response, then the payload.
-python3 -c "import gzip; d=gzip.open('rec.warc.gz','rb').read(); i=d.find(b'%PDF'); \
-            print(len(d), i, len(d)-i)"
-# -> 724237  2285  721952        <- a real 722 KB PDF
-```
-
-`mime-detected` is more trustworthy than `mime` (one row showed `"mime":"unk"` with
-`"mime-detected":"application/pdf"`). A URL with no captures returns **HTTP 404 with JSON
-`{"message": "No Captures found for: …"}`** — honest, for both a real domain and a bogus one.
-
-**Limitation:** Common Crawl obeys `robots.txt` and gets blocked like any other crawler. A query for
-`bitsavers.org/pdf/dec/tech_reports/*` returned no captures — consistent with bitsavers' 403 to
-non-browser agents. **Absence from Common Crawl is evidence about the crawler, not about the site.**
-
-### 7.6 UK Web Archive, Library of Congress, Bibliotheca Alexandrina
-
-- **UK Web Archive** (`webarchive.org.uk`): the certificate is valid (British Library / DigiCert,
-  expires 2027-02-24); the failure in this environment was a local CA-store gap. Fetched with
-  verification relaxed, it returns a 5,611-byte page titled **"UK Web Archive currently
-  unavailable"**: *"The British Library is continuing to experience disruption following a
-  cyber-attack and are working hard to restore services."* [WEB] **They are still crawling under UK
-  legal deposit; access is what is down.** Do not record it as defunct.
-- **`webarchive.loc.gov`**: **HTTP 403** with a 5,740-byte Cloudflare "Just a moment…" interstitial
-  to a Chrome 131 UA [WEB]. Alive, closed to scripts. Its collections (e.g. legislative and
-  government-agency web captures) are reachable through a browser. Whether an API exists is
-  **[NOT-VERIFIED]**.
-- **Bibliotheca Alexandrina's Internet Archive mirror** (`web.archive.bibalex.org`): DNS resolves to
-  `196.204.180.101` but **TCP times out on both :80 and :443** after 25 s [WEB]. This was the
-  celebrated 2002 full mirror of the Internet Archive; it appears no longer to serve. Recorded as
-  **unreachable on one day from one host**, not as defunct — the discipline this repository applied
-  to Synthical applies here too.
-
----
-
-## 8. Search-engine caches — dead, in both directions
-
-Both were probed because people still reach for them first [WEB]:
-
-| Route | Result 2026-09-02 |
-|---|---|
-| `webcache.googleusercontent.com/search?q=cache:<url>` | **HTTP 200, ~92 KB** — but the body is a generic *"Google Search — If you're having trouble accessing Google Search, please click here"* page. **No cached content, for any URL tried.** The host still resolves; the service does not exist |
-| `cc.bingj.com/cache.aspx?…` | **HTTP 400**, 194-byte Edge error: *"Our services aren't available right now"* |
-
-Google removed the `cache:` operator and the cache link from search results during 2024, publicly
-framing it as no longer needed now that the Wayback Machine is linked from the "About this result"
-panel [COM]. The endpoint's continued 200 response is the dangerous part: **a naive
-`%{http_code}` check reports success and you save 92 KB of Google chrome as your recovered
-document.**
-
-Combine this with the existing finding in the crawler table that DuckDuckGo's HTML endpoints return
-**HTTP 202 + a CAPTCHA** and that Bing returned *wrong* results (German CRM software) for a quoted
-part number, and the conclusion for this knowledge base is blunt: **search engines are not a
-recovery mechanism in 2026. Enumerate archives directly.**
-
----
-
-## 9. This repository's archival practice (`AGENTS.md` rule 9)
-
-Rule 9 says: preserve scarce sources by submitting them to `https://web.archive.org/save/<url>`, but
-only things that are genuinely hard to acquire and unlikely to persist — not widely-mirrored content.
-The crawler table adds the crucial refinement: **check `archive.org/wayback/available` first**,
-because `save/` is slow and rate-limited while the availability API is neither.
-
-### 9.1 Candidates checked this pass
-
-| Candidate | Source of the nomination | Availability check | Action |
-|---|---|---|---|
-| `https://mementoweb.org/about/` | this pass — sole record of the Time Travel shutdown | captured **2026-08-19** | none needed |
-| `https://www.bitsavers.org/` | this pass — the operator's policy + mirror list, hand-maintained | captured **2026-08-31** | none needed |
-| `https://www.bitsavers.org/pdf/dec/tech_reports/` | [`government-…-reports.md` §7](government-and-institutional-technical-reports.md) | captured **2025-09-19** | none needed |
-| `https://www.bitsavers.org/pdf/IndexByDate.txt` | this pass — the archive's own manifest | captured **2025-07-11** | none needed |
-| `https://web.ma.utexas.edu/mp_arc/` | [`retrieval-notes.md §6`](retrieval-notes.md#9-archival-candidates) | captured **2026-04-12** | none needed |
-| `https://roa.rutgers.edu/` | [`retrieval-notes.md §6`](retrieval-notes.md#9-archival-candidates) | captured **2026-07-11** | none needed |
-| `https://roa.rutgers.edu/info.html` | [`retrieval-notes.md §6`](retrieval-notes.md#9-archival-candidates) | **no snapshot** (`{}` and CDX `[]`) | **too late — the live URL now returns HTTP 404, 196 B** |
-
-**No `web.archive.org/save/` submissions were made in this pass**, because every still-live candidate
-was already held. That is the correct outcome of rule 9 applied properly rather than reflexively.
-
-### 9.2 The ROA lesson
-
-The Rutgers Optimality Archive `info.html` — described in `retrieval-notes.md` as *"a hand-written
-30-year systems history that exists nowhere else"* and nominated for archival on 2026-09-01/02 — is
-**already gone**, one day later, with **zero Wayback captures ever** [WEB]. The site has been
-restructured to `article/browse.html` plus a downloadable `article/ROA.xlsx` index of ~1,400 papers.
-
-Three things follow, and they generalise well beyond ROA:
-
-1. **"Identify archival candidates" is not archival.** The gap between nominating a URL and capturing
-   it is exactly where documents are lost. If a page is worth nominating, submit it in the same
-   session.
-2. **A domain having captures tells you nothing about a page having captures.** `roa.rutgers.edu/`
-   is captured back to 2002; `roa.rutgers.edu/info.html` never was.
-3. **Restructures look like deaths and vice versa.** The content may survive under a new path. Run a
-   CDX `matchType=prefix` query over the old directory before writing anything off.
-
-### 9.3 Still-open archival candidates
-
-Carried forward from [`retrieval-notes.md §6`](retrieval-notes.md#9-archival-candidates),
-[`optimization-online.md`](optimization-online.md) and
-[`government-and-institutional-technical-reports.md` §4.5](government-and-institutional-technical-reports.md):
-
-- **`optimization-online.org` old-style `DB_HTML/YYYY/MM/NNN.html` records.** Durable for 22 years,
-  but the operator has already migrated once and old `DB_FILE/*.pdf` links have degraded to abstract
-  pages. Enumerate via the month-archive widget, then CDX-check before saving.
-- **Xerox PARC technical reports** (`CSL-`, `SSL-`, `ISL-` prefixes). The companion record calls this
-  *"the most serious unresolved gap"*: `parc.com/publications/` now redirects to an SRI division
-  page, and the surviving scans are scattered across bitsavers' `xerox` tree (1,998 files), the
-  Computer History Museum, and individual authors' pages. **No authoritative index exists.** Building
-  one from bitsavers' `IndexByDate.txt` plus CDX prefix queries over `parc.com/publications/` is the
-  obvious next piece of work.
-- **HP Journal (1949–1998).** `hpl.hp.com/hpjournal/journal.html` is TCP-dead. bitsavers' `hp` tree
-  has 2,473 files; whether the Journal run is complete there is **[NOT-VERIFIED]**.
-
----
-
-## 10. Findings staged for the crawler access table
-
-Per `AGENTS.md` rule 8 these belong in
-[`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md). That file was being
-modified by concurrent work when this pass ran, so **nothing was written into it.** Merge when safe.
-
-**§ General retrieval tips — one correction and one addition:**
-
-- ❗ **Remove or annotate the Memento Aggregator recommendation.**
-  `http://timetravel.mementoweb.org/api/json/<timestamp>/<url>` is **NXDOMAIN**; the service was shut
-  down at the end of 2025 (§7.2). Replace it with a manual loop over Wayback → Arquivo.pt →
-  Common Crawl.
-- ➕ **Wayback throttling is volume-based, not UA-based, and has two failure modes.** The ceiling is a
-  moving server-side judgement, **not a fixed quota** — measured at ~3 back-to-back `/web/` requests
-  on 2026-09-02 and at **16** on 2026-09-04. It fails *either* with **HTTP 429** (620-byte body,
-  `x-rl: 0`) *or* with outright **TCP refusal** (`curl` exit 7, `http_code` 000) — the two are
-  alternatives, not an escalation; the 2026-09-04 run never once saw a 429. Pace at ≥1.5 s.
-  ⚠ **While throttled, responses flap** — identical requests 1 s apart gave `200 200 000 000 000 200
-  200 000 000 000`, so a bulk fetch yields a *silent mixture* of retrieved and missing files.
-  **Everything on `web.archive.org` (replay *and* CDX) fails together; everything on `archive.org`
-  (`wayback/available`, `metadata/<id>`, `advancedsearch.php`) keeps working.** Rotating user agents
-  is a waste of time — during a block `curl` and ClaudeBot got 200 in the same second that Googlebot
-  and no-UA got 000, which is the flapping, not a policy.
-- ➕ **`web.archive.org/cdx/` intermittently 503s** with an 11,832-byte "Temporarily Offline" page —
-  **1 in 3** identical requests on 2026-09-02, **2 in 3** on 2026-09-04. Not a per-URL signal.
-  **Retry at least twice before recording "no captures"**, or you will write down that a page was
-  never archived when it was.
-- ➕ **Use the `id_` replay suffix for any non-HTML file.** Plain replay injects
-  `bundle-playback.js` and rewrites links (16,004 B vs 13,237 B for the same capture).
-- ➕ **Google and Bing caches are gone** (§8). `webcache.googleusercontent.com` returns **HTTP 200
-  with a Google Search shell** — a silent-corruption hazard of exactly the LCSC class.
-- ➕ **Common Crawl byte-range recovery works and is not rate-limited**; recipe in §7.5.
-
-**§ Sites — new entries:**
-
-| Site | Finding |
-|---|---|
-| `www.bitsavers.org` | **403 (283 B Apache) to `curl` and `Wget`; 200 to a browser UA.** `robots.txt` is a **zero-byte 200**. This is deliberate policy, not an accident — the operator asks for **anonymous rsync** (`rsync://bitsavers.org/bitsavers/`) or a mirror. **The mirrors do not apply the block** (`mirrorservice.org`, `bitsavers.trailing-edge.com`, `bitsavers.informatik.uni-stuttgart.de` all 200 to default `curl`), and `ftpmirror.your.org`'s index was byte-identical to the origin's. **Use a mirror, not a UA.** Honest 404s (280 B) — status codes are trustworthy |
-| `archive.softwareheritage.org` | **Inverted ladder — Anubis proof-of-work.** Chrome 131 and Firefox 128 get a **200 with a 4,667-byte "Making sure you're not a bot!" page**; ClaudeBot gets 403; **default `curl`, WhatsApp, Googlebot and no-UA-at-all get real JSON.** Second confirmed inversion after `nxp.com`. The challenge arrives with HTTP **200** — test for the string, not the status |
-| `archive.ph` / `archive.today` / `archive.is` | Root 200 (16,590 B). **`/timemap/<url>` returns a real Memento TimeMap — 200, ~1.5 kB, 5/5 attempts, plain Chrome UA, no CAPTCHA** (re-probed 2026-09-04, correcting an earlier "no API" note). **`/newest/<url>` returns HTTP 429 + a 55–63 kB CAPTCHA.** Discovery is scriptable; retrieval is browser-only |
-| `arquivo.pt` | **Open, fast, no UA games.** `/wayback/cdx?url=…&output=json`, `/wayback/timemap/link/<url>`, `/wayback/<ts>mp_/<url>` replay, `/textsearch?q=`. Clean 404/0-byte negative control. Holds captures IA lacks. **Also accepts save requests** at `/services/archivepagenow` — a second place to preserve a scarce URL when `web.archive.org/save/` is throttled |
-| `index.commoncrawl.org` / `data.commoncrawl.org` | Open. 127 crawls back to 2008. Range-GET into WARCs works unauthenticated (HTTP 206) |
-| `webarchive.loc.gov` | 403 Cloudflare "Just a moment…" (5,740 B) |
-| `webarchive.org.uk` | Service **down** (British Library cyber-attack); still crawling. Valid cert — a TLS verify failure here is a **local CA-store gap** |
-| `web.archive.bibalex.org` | Resolves (196.204.180.101), **TCP timeout** on :80 and :443 |
-| `timetravel.mementoweb.org` | **NXDOMAIN.** Shut down end of 2025 |
-| `alldatasheet.com`, `datasheets.com`, `datasheets360.com` | Cloudflare **403, ~5.6 kB** — the fingerprint from [`retrieval-notes.md §1`](retrieval-notes.md) |
-| `datasheetcatalog.com` | **NXDOMAIN** — dead |
-| `datasheetarchive.com` | Open (200, real results) but **no `.pdf` hrefs in the HTML** — downloads are JS-driven |
-| `chipdb.org` | Open. **Chip *photograph* database, not datasheets** — 6,392 images / 1,222 categories |
-
----
-
-## 11. What this pass could not verify
-
-- **Arquivo.pt's ArchivePage Now form** was located (302 from `/services/savepagenow`, 200 on
-  `/services/archivepagenow`) but **not exercised** — its behaviour, quotas and success rate are
-  **[NOT-VERIFIED]**.
-- **Whether `webarchive.loc.gov` exposes a CDX or Memento API** — blocked at the front door,
-  **[NOT-VERIFIED]**.
-- **Which bitsavers directories carry embedded Acrobat full-text indexes.** The operator says some do;
-  none were located — **[NOT-VERIFIED]**.
-- **Whether `bitsavers`' 91,398-item archive.org collection is current or complete** relative to the
-  188,000-file live tree — **[NOT-VERIFIED]**. Assume it is neither.
-- **Whether the HP Journal run survives completely on bitsavers** — **[NOT-VERIFIED]**.
-- **Whether `web.archive.bibalex.org` is permanently dead** — one host, one day. **[NOT-VERIFIED]**.
-- **The Wayback throttle's exact window and quota — and after two passes we now believe there is no
-  fixed one to find.** The unpaced ceiling measured **~3** on 2026-09-02 and **16** on 2026-09-04,
-  and the failure mode differed between the runs (429 vs TCP refusal). The archive publishes no
-  figure. **[NOT-VERIFIED]**, and treated here as unknowable from outside: pace at ≥1.5 s, retry, and
-  validate every file rather than trusting a request budget.
-- **Whether the flapping seen on 2026-09-04 is a load balancer with per-node state, a decaying token
-  bucket, or something else.** Only the *symptom* is measured. **[NOT-VERIFIED]**.
-- **Whether `archive.ph/timemap/` is reliable or was merely open on the day.** It answered 5/5 on
-  2026-09-04 against a 0/2 reading on 2026-09-02 for the sibling `/newest/` path. It is undocumented,
-  so its stability is **[NOT-VERIFIED]** — use it, but do not depend on it unattended.
-- **Google's cache-removal date.** Widely reported as 2024 [COM]; no primary Google announcement was
-  retrieved here — **[NOT-VERIFIED]** as to the exact date. The *current* state is measured.
-
----
-
-## 12. Sources
-
-Retrieval date **2026-09-02** for all of the following unless stated.
-
-- **S1** `https://web.archive.org/cdx/search/cdx?url=hpl.hp.com/techreports/Compaq-DEC/&output=json&limit=20`
-  → 200, 3,444 B. Capture timeline and 301 interleaving. Negative control
-  `this-domain-does-not-exist-zzq9.example/` → 200, `[]`. [API]
-- **S2** `https://archive.org/wayback/available?url=…` → 200, 246 B (positive) / 77 B (`{}`, negative).
-  Host-independence during throttling. [API]
-- **S3** Wayback rate-limit experiment (runs A–E), full log in
-  [`../../scratch/preprint-repositories/bulk-archives/waybackratelimit.txt`](../../scratch/preprint-repositories/bulk-archives/waybackratelimit.txt).
-  429 body, `x-rl: 0`, TCP refusal, 60-s recovery, 8-UA rotation. [WEB]
-- **S4** `https://web.archive.org/web/20190213111131{,id_}/http://hpl.hp.com:80/techreports/Compaq-DEC/`
-  → 16,004 B vs 13,237 B. [WEB]
-- **S5** `https://archive.org/advancedsearch.php?q=…&rows=0&output=json` — all `numFound` values in
-  §3.1, incl. the `mediatype:texts` (52,096,704) vs `collection:"texts"` (39,535) trap and the
-  silent-zero negative control. [API]
-- **S6** `https://archive.org/metadata/tektronix_465` → 200, 4,438 B, 14-file manifest.
-  Negative control `…/zzq9-no-such-item-exists-here` → 200, `{}`. `…/download/tektronix_465/465_djvu.txt`
-  → 695,458 B (OCR sample quoted in §3.3); missing file → 404. [API]
-- **S7** `https://archive.org/advancedsearch.php?q=title%3A%28tektronix+465%29…` → 14 hits, incl. the
-  "Fish Finder" and "Hunting Equipment" mislabels. [API]
-- **S8** `https://www.bitsavers.org/` → 200, 9,377 B. Operator's own statements: 188,000 files /
-  8.86 M text pages / 1.86 TB; Wget ban dated 2026-05-10; rsync instruction; mirror and snapshot
-  lists; scanning workflow (Group 4 T.6, 400→600 dpi, `tumble`, Acrobat OCR); destructive scanning;
-  CHM lot `X6512.2012`. [DOC]
-- **S9** `https://www.bitsavers.org/{pdf,bits,components,test_equipment,magazines,communications}/IndexByDate.txt`
-  → 180,741 lines total; per-tree sizes, vendor counts, extension mix, DEC report prefix counts,
-  `Compaq-DEC_TRs_HPL_mirror_2007.zip` (236,085,636 B, 2023-09-04). [API]
-- **S10** bitsavers UA matrix: `Wget/1.21.4` → 403/283 B; `curl/8.21.0` → 403/283 B; Chrome 131 → 200.
-  `robots.txt` → 200/0 B. `SRC-RR-1.pdf` → 200/2,239,056 B/`%PDF-1.2`; `SRC-RR-99999.pdf` → 404/280 B. [WEB]
-- **S11** `rsync://bitsavers.org/` module list; `rsync --list-only rsync://bitsavers.org/bitsavers/pdf/dec/tech_reports/`
-  → 522 entries. Seven web mirrors, all 200; three tested with default `curl` → 200;
-  `ftpmirror.your.org` `pdf/IndexByDate.txt` byte-identical to origin. [API]
-- **S12** `https://archive.softwareheritage.org/api/1/stat/counters/` → the eight counters in §6.1;
-  `/api/1/origin/https://github.com/torvalds/linux/visits/` → visit 478, 2026-09-02T03:44:11Z;
-  `/api/1/resolve/…` positive and 404 negative control; `/api/1/origin/search/` ranking trap. [API]
-- **S13** Software Heritage UA matrix (Chrome 131, Firefox 128, ClaudeBot, `curl`, WhatsApp,
-  Googlebot, no-UA) against `/api/1/origin/search/`. Anubis page title
-  `Making sure you're not a bot!`. [WEB]
-- **S14** `https://mementoweb.org/` → 200, 2,826 B stub; `https://mementoweb.org/about/` → 200,
-  8,269 B, quoted in §7.2. `timetravel|www|labs|aggregator.mementoweb.org` → NXDOMAIN. [DOC] [WEB]
-- **S15** `https://arquivo.pt/wayback/{timemap/link,cdx}` and
-  `https://arquivo.pt/wayback/20081022115306mp_/http://www.hpl.hp.com/techreports/Compaq-DEC/`
-  → 200, 97,670 B, recovered HP Labs index. Negative control → 404/0 B. `/textsearch` → 200 JSON. [API]
-- **S16** `https://index.commoncrawl.org/collinfo.json` → 127 collections; `CC-MAIN-2026-34-index`
-  query; `https://data.commoncrawl.org/<warc>` range GET → 206/660,220 B → gunzip 724,237 B, `%PDF`
-  at offset 2,285. [API]
-- **S17** `archive.today|.ph|.is` roots → 200/16,590 B; `/newest/` → 429 (55,512 B on 2026-09-02, 63,290 B on 2026-09-04) CAPTCHA. **`/timemap/https://www.bitsavers.org/` → 200/1,497 B, a valid RFC 7089 TimeMap, 5/5 attempts (2026-09-04)** — corrects the 2026-09-02 reading. [WEB] [API]
-- **S18** `https://www.webarchive.org.uk/` → cert valid to 2027-02-24, local verify failure;
-  with verification relaxed, 200/5,611 B "UK Web Archive currently unavailable" (British Library
-  cyber-attack). `https://webarchive.loc.gov/all/*/…` → 403/5,740 B Cloudflare.
-  `web.archive.bibalex.org` → DNS 196.204.180.101, TCP timeout. [WEB]
-- **S19** `https://webcache.googleusercontent.com/search?q=cache:…` → 200/~92 KB Google Search shell,
-  for two different targets. `https://cc.bingj.com/cache.aspx?…` → 400/194 B. [WEB]
-- **S20** Datasheet aggregator matrix (§5): alldatasheet 403/5,603 B, datasheets.com 403/5,601 B,
-  datasheets360 403/5,625 B, octopart 403/51,989 B, datasheetarchive 200/41,998 B and
-  200/239,746 B for `?q=lm317` with zero PDF hrefs, datasheetcatalog NXDOMAIN, chipdb.org
-  200/71,622 B ("6392 images in 1222 categories"). [WEB]
-- **S21** Archival-candidate availability checks (§9.1), incl. `roa.rutgers.edu/info.html` → `{}` +
-  CDX `[]` + live **404/196 B**, and `roa.rutgers.edu/` → 200/6,278 B with the restructured
-  `article/browse.html` + `article/ROA.xlsx` layout. [API] [WEB]
-- **S22** Companion records in this directory:
-  [`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md)
-  §4.2/§4.3/§4.5 and S20–S21 therein;
-  [`retrieval-notes.md`](retrieval-notes.md) §1, §3, §6;
-  [`open-access-full-text-sources.md`](open-access-full-text-sources.md) §1;
-  [`zenodo.md`](zenodo.md) § Software Heritage;
-  [`optimization-online.md`](optimization-online.md) §4.
-- **S23** [`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md) —
-  § General retrieval tips (Memento recommendation, `save/` 503 + availability-API-first rule,
-  DuckDuckGo/Bing search findings), § Vendor documentation portals (the three failure classes, the
-  Espressif WROVER `if_` recovery), § Electronics distributors (LCSC filename provenance,
-  `digi-electronics.com` AI-generated errors). Prior work, dated 2026-08-21/24.
-- **S25** **Independent re-verification pass, 2026-09-04.** Logs in
-  [`../../scratch/preprint-repositories/dead-sites/`](../../scratch/preprint-repositories/dead-sites/)
-  (`VERIFY-SUMMARY.md`, `verify-01`…`verify-13`). **Reproduced byte-for-byte:**
-  `wayback/available` 200/246 B and negative control 200/77 B; CDX success 200/3,444 B, negative
-  control `[]`/3 B, "Temporarily Offline" 503/11,832 B; bitsavers `Wget`→403/283 B,
-  default `curl`→403/283 B, Chrome→200, `robots.txt`→200/**0 B**, `SRC-RR-1.pdf`→200/2,239,056 B/
-  `%PDF-1.2`, `SRC-RR-99999.pdf`→404/280 B; `pdf/IndexByDate.txt`→8,578,234 B/93,668 lines;
-  the DEC prefix counts (170/67/108/42/91/35/7, 521 total) by a **third** method — fresh index
-  download plus `grep`; `Compaq-DEC_TRs_HPL_mirror_2007.zip` = 236,085,636 B confirmed with its size
-  via `rsync --list-only` (522 entries, 6 rsync modules); Software Heritage Chrome→200/4,667 B Anubis,
-  default `curl`→200/1,643 B JSON, ClaudeBot→403/508 B, bogus SWHID→404/131 B, plus the Gitorious
-  search-ranking trap; Google cache→200/91,694 B titled `Google Search`; `cc.bingj.com`→400/194 B;
-  `timetravel|labs|aggregator.mementoweb.org`→NXDOMAIN with the apex resolving; `archive.ph` root
-  200/16,590 B; Arquivo.pt CDX→200/1,590 B recovering the 2008 `hpl.hp.com` capture; Common Crawl
-  127 collections, `CC-MAIN-2026-34`…`CC-MAIN-2008-2009`, bogus query→honest 404/77 B;
-  alldatasheet 403/5,603 B, datasheets.com 403/5,601 B, `datasheetcatalog.com` NXDOMAIN;
-  `hpl.hp.com` DNS-resolves to 15.73.144.188 but **TCP times out** (`curl` exit 28) — still dead.
-  **Corrected:** §2.2 throttle ceiling/mode/flapping, §2.3 host split, §7.4 `archive.ph/timemap/`.
-  **Drifted (so not usable as equality fingerprints):** replay 16,004→16,006 B,
-  `metadata/tektronix_465` 4,438→4,437 B, `datasheetarchive.com` 41,998→42,632 B,
-  `chipdb.org` 71,622→71,623 B. [API] [WEB]
-- **S24** `https://arquivo.pt/services/savepagenow` → 302 → `/services/archivepagenow` → 200,
-  18,183 B ("ArchivePage Now" form). `https://www.swhid.org/` → 200, 50,398 B; news index carries
-  *"SWHID standardized as ISO/IEC 18670"*. [DOC] [WEB]
diff --git a/research/preprint-repositories/regional-and-national-servers.md b/research/preprint-repositories/regional-and-national-servers.md
deleted file mode 100644
index ddf981e..0000000
--- a/research/preprint-repositories/regional-and-national-servers.md
+++ /dev/null
@@ -1,496 +0,0 @@
-# Regional and national preprint servers — grouped record
-
-- **Scope:** the smaller national/regional *multidisciplinary* preprint servers — Jxiv,
-  SciELO Preprints, AfricArXiv, Arabixiv, IndiaRxiv, INArxiv, LatArXiv, Preprints.ru,
-  AIJR Preprints
-- **Compiled:** 2026-09-01 · **All reachability probes run:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 0. The shared pattern — read this before the individual entries
-
-The folklore is that regional preprint servers launch with fanfare, run on one or two volunteers,
-and go dark within five years. The probe evidence collected here **partly confirms that and
-partly corrects it**, and the correction is the more useful finding.
-
-**What actually happens is not data loss. It is loss of the front door.**
-
-Of the nine servers below, four are in good health (Jxiv, SciELO Preprints, Preprints.ru, AIJR)
-and five are in some state of failure. But in every failing case where the content sat on a **large
-shared host** — OSF or Zenodo — *the content survived*, including for a server that formally shut
-down six years ago:
-
-| Server | Formal status | Content still readable? | Where |
-|---|---|---|---|
-| INArxiv | Closed 2020-10-07 | **Yes — 15,987 preprints** | OSF |
-| AfricArXiv | Submissions closed | **Yes — 479** | OSF |
-| Arabixiv | Submissions closed | **Yes — 298** | OSF |
-| IndiaRxiv | Submissions closed | **Yes — 121** | OSF |
-
-What broke, without exception, was the **independently hosted successor or vanity domain**:
-
-| Independent host | State on 2026-09-01 | Failure |
-|---|---|---|
-| `africarxiv.ubuntunet.net` (AfricArXiv's own designated successor) | unreachable | **TLS certificate expired** |
-| `rinarxiv.lipi.go.id` (INArxiv's designated successor) | unreachable | **TLS hostname mismatch** |
-| `latarxiv.org` (live server, 2024 vintage) | reachable only with `curl -k` | **TLS certificate expired 2026-08-20** |
-| `www.inarxiv.id` | unreachable | **DNS NXDOMAIN** |
-| `indiarxiv.org` (relaunch on OJS) | reachable | **OAI reports zero records** |
-
-**An expired TLS certificate is the reliable early warning sign of an abandoned scholarly
-service.** Three of the nine servers here failed on certificate management alone — a task that is
-automated and free, and which therefore fails only when nobody is left watching the alerts. All
-three were reachable, with intact content, behind the broken certificate. A browser would refuse
-them; a reader would conclude the site was gone.
-
-**What this means for citing regional-server content:**
-
-1. **Cite the OSF or Zenodo record and its DOI, never the vanity domain.** `africarxiv.org`,
-   `arabixiv.org`, `indiarxiv.in` and `inarxiv.id` have all either redirected, changed host or
-   evaporated; the OSF records behind them have not.
-2. **Verify the record still resolves at the time you cite it**, and record your retrieval date.
-   Two of these servers actively signpost readers to successors that do not work (§3, §6).
-3. **Distrust "moved to" notices.** Arabixiv's OSF page says it moved to Zenodo; `arabixiv.org`
-   redirects back to the frozen OSF instance; the Zenodo community holds 78 records against OSF's
-   298 (§4). The operator's own signposting is mutually contradictory.
-4. **Expect the front page to lie about liveness in both directions** — a dead-looking site may
-   have intact content behind a bad certificate, and a live-looking relaunch may be empty (§5).
-
-## 1. Status table
-
-All probed **2026-09-01** using the `AGENTS.md` UA ladder: default `curl` → Chrome 131 →
-WhatsApp/2.23.20.0 → ChatGPT-User/1.0 → ClaudeBot/1.0. "UA that worked" names the *first*
-successful agent.
-
-| Server | URL probed | Operator | Launch | Status 2026-09-01 | Size | UA that worked |
-|---|---|---|---|---|---|---|
-| **Jxiv** | `jxiv.jst.go.jp` | Japan Science & Technology Agency (JST) | 2022 | **ALIVE** | **1,221** [API] | default curl |
-| **SciELO Preprints** | `preprints.scielo.org` | SciELO / FAPESP network | 2020 | **ALIVE** | **5,689** [API] | default curl |
-| **AfricArXiv (OSF)** | `osf.io/preprints/africarxiv` | Center for Open Science | 2018 | **FROZEN** — submissions off | **479** [API] | default curl |
-| ↳ successor | `africarxiv.ubuntunet.net` | UbuntuNet Alliance | 2023 | **BROKEN** | n/v | **none — TLS expired** |
-| ↳ org site | `africarxiv.org` | AfricArXiv | — | ALIVE (167,413 B) | n/a | default curl |
-| **Arabixiv (OSF)** | `osf.io/preprints/arabixiv` | Center for Open Science | 2018 | **FROZEN** — submissions off | **298** [API] | default curl |
-| ↳ successor | Zenodo community `arabixiv` | Zenodo/CERN | created **2025-09-17** | ALIVE | **78** [API] | default curl |
-| **IndiaRxiv (OSF)** | `osf.io/preprints/indiarxiv` | Center for Open Science | 2019 | **FROZEN** — submissions off | **121** [API] | default curl |
-| ↳ relaunch | `indiarxiv.org` | Society for Promotion of Horticulture | — | **ALIVE BUT EMPTY** | **0 via OAI** [API] | default curl |
-| ↳ old domain | `indiarxiv.in` | — | — | redirects → `indiarxiv.wordpress.com` (blog) | n/a | default curl |
-| **INArxiv (OSF)** | `osf.io/preprints/inarxiv` | Center for Open Science | 2017 | **CLOSED 2020-10-07**, content retained | **15,987** [API] | default curl |
-| ↳ own domain | `www.inarxiv.id` | — | — | **DEAD** | — | **none — DNS NXDOMAIN** |
-| ↳ successor | `rinarxiv.lipi.go.id` | LIPI (Indonesia) | — | **BROKEN** | n/v | **none — TLS hostname mismatch** |
-| **LatArXiv** | `latarxiv.org` → `preprints.latarxiv.org` | Paideia Publishing Services | 2024 [INF] | **ALIVE, TLS BROKEN** | not verified | **`curl -k` only — cert expired 2026-08-20** |
-| **Preprints.ru** | `preprints.ru` | NEICON (НЭИКОН) | autumn **2019** | **ALIVE** | **3,063** [WEB] | default curl |
-| **AIJR Preprints** | `preprints.aijr.org` | AIJR Publisher (India) | 2020 | **ALIVE** | **188** [API] | default curl |
-
-**Negative control for the whole sweep:** `www.inarxiv.id` failed with DNS NXDOMAIN on all five
-user-agents, and `africarxiv.pubpub.org` returned HTTP **403 on all five** — confirming the ladder
-distinguishes real failures from UA filtering, and that a "success" above is not an artefact of
-retrying.
-
----
-
-## 2. Jxiv (Japan Science and Technology Agency)
-
-- **URL:** https://jxiv.jst.go.jp/ (resolves to `/index.php/jxiv`) · **Operator:** JST ·
-  **Launched:** 2022 · **Status: ALIVE**
-
-Japan's national preprint server, run by JST, the country's principal research funding agency.
-Built on PKP's Open Journal/Preprint Systems. OAI-PMH `Identify` gives `repositoryName`
-**"Jxiv, JSTプレプリントサーバ"**, `adminEmail` `info-jxiv@jst.go.jp`, and `earliestDatestamp`
-**2022-03-24T01:21:10Z** — which independently confirms the 2022 launch (S1) [API].
-
-**Size: 1,221 records**, from OAI `ListIdentifiers` `completeListSize` (S1) [API].
-
-**Computing/engineering content: yes, structurally.** OAI `ListSets` exposes discipline sets
-including **情報科学** (information science), **電気電子工学** (electrical & electronic
-engineering), **一般工学・総合工学** (general engineering), **機械工学** (mechanical engineering),
-**ナノ・材料科学** (nano/materials) and **建築学・土木工学** (S1) [API]. Per-set counts not
-retrieved. Language sample from the first OAI page: **eng 56 / jpn 44** — majority English (S1)
-[API].
-
-**Moderation: real, and JST holds the power.** The submission checklist requires authors to accept
-that *"JSTが、投稿するプレプリントの公開の可否を決定する権限をもつこと"* — **JST has the authority
-to decide whether a submitted preprint is published**; that published preprints **cannot be
-withdrawn or deleted** by the author; and that **JST may retract** a published preprint. Authors
-must register country of residence, affiliation and email, used for **本人確認** (identity
-verification). Manuscripts already posted to another preprint server (or already carrying a DOI)
-**cannot in principle be submitted** (S2) [DOC].
-
-**Assessment.** The healthiest server in this group after SciELO. It has a national funding agency
-behind it, working OAI-PMH, a documented moderation policy with named accountability, and real
-engineering categories. Its weakness is simply scale: 1,221 records in four years is small, and
-Japanese CS researchers preprint to arXiv. Use it for Japanese-language engineering work that has
-no arXiv counterpart; do not expect to find landmark systems papers.
-
-## 3. SciELO Preprints
-
-- **URL:** https://preprints.scielo.org/ · **Operator:** SciELO network ·
-  **Launched:** 2020 · **Status: ALIVE**
-
-The preprint arm of SciELO, the Latin American / Iberian / South African open-access publishing
-network. Runs on **OPS (Open Preprint Systems)** from PKP. OAI `earliestDatestamp`
-**2020-04-06T23:01:54Z**, `adminEmail` `scielo.submission@scielo.org` (S3) [API], confirming the
-2020 launch. Its own about page is versioned **21 May 2025** (S4) [DOC].
-
-**Size: 5,689 records** (OAI `completeListSize`, S3) [API] — the largest *active* server in this
-group.
-
-**Genuinely multilingual, and measurably so.** Language tags in the first 100 OAI records:
-**Portuguese 45, English 39, Spanish 17** (S3) [API]. This is not a monolingual server with a
-translated interface; it is trilingual in substance.
-
-**Computing/engineering content: yes.** OAI `ListSets` includes **Engenharias** (engineering) and
-**Ciências Exatas e da Terra** (exact and earth sciences) alongside the health/humanities sets
-(S3) [API]. Per-set counts not retrieved. **[NOT-VERIFIED]**
-
-**Moderation: the most interesting policy in this group.** SciELO operates a **reputation-gated
-auto-post**, documented verbatim (S4) [DOC]:
-
-> Um manuscrito será postado automaticamente quando o autor da submissão tiver **pelo menos três
-> artigos** de qualquer data **ou dois artigos recentes dos últimos dois anos** com DOIs ativos no
-> repositório Crossref. Em outros casos, uma **triagem básica** será feita para identificar se é um
-> manuscrito relacionado à pesquisa.
-
-So: an author with ≥3 Crossref-indexed articles (any date), or 2 within the last two years,
-**bypasses screening entirely**; everyone else gets a basic triage checking that the submission is
-research. Registration requires **ORCID**. A manuscript **will not be posted if it has already
-been accepted, published, or posted elsewhere**. Authors must confirm ethics-committee approval
-where applicable, and SciELO reserves the right to apply area-specific screening criteria and to
-reject (S4) [DOC]. The server also layers **Hypothesis annotation** and a preprint-evaluation
-workflow on top (S4) [DOC].
-
-**Assessment.** The strongest governance model here, and the one worth copying: it spends
-moderator effort only on unknown authors. Institutionally backed by an established publishing
-network rather than volunteers, which is why it has not exhibited the failure mode of §0. For an
-engineer it is a plausible source of Latin American engineering work, but you should expect
-Portuguese and Spanish full texts.
-
-## 4. AfricArXiv and Arabixiv — the two COS-hosted 2018 cohort
-
-### AfricArXiv
-
-- **OSF:** https://osf.io/preprints/africarxiv · **Launched:** 2018 with the Center for Open
-  Science · **Status: FROZEN** (`allow_submissions: false`) · **Size: 479 preprints** (S5) [API]
-
-The OSF provider record's own description states AfricArXiv launched with COS in 2018 and that
-"In 2023, we reached our key milestone to establish AfricArXiv as a central repository at
-**UbuntuNet Alliance** For Research & Education Networking. Please submit your research items via
-**https://africarxiv.ubuntunet.net/**" (S5) [API/DOC]. Review workflow is recorded as
-`pre-moderation` (S5) [API].
-
-**The designated successor does not work.** `https://africarxiv.ubuntunet.net/` failed on **all
-five user-agents** with `curl: (60) SSL certificate ... certificate has expired` (S6). The
-organisational site `https://africarxiv.org/` is alive (HTTP 200, 167,413 B, default UA), and the
-older `africarxiv.pubpub.org` returns **HTTP 403 on all five UAs** (S6).
-
-**Assessment.** The 479 preprints on OSF are safe and citable. The 2023 "central repository"
-migration is, as of 2026-09-01, not reachable by an ordinary client. Cite OSF. Do not send anyone
-to the ubuntunet address. Whether content was ever migrated there is **not verified**.
-
-### Arabixiv
-
-- **OSF:** https://osf.io/preprints/arabixiv · **Launched:** 2018 with COS ·
-  **Status: FROZEN** (`allow_submissions: false`) · **Size: 298 preprints** (S5) [API]
-
-Founded by Dr Khaled Moustafa, with a listed steering committee including academics at Cairo
-University and Paris-Sud (S5) [API]. Review workflow `pre-moderation`.
-
-**Three mutually inconsistent signposts**, all retrieved 2026-09-01:
-
-1. The OSF description says: *"ArabiXiv has moved to a new address and accepts submissions through
-   its new platform at: https://zenodo.org/communities/arabixiv/about. All previously published
-   articles remain accessible and their links are preserved."* (S5) [API/DOC]
-2. The OSF `domain` field still points to `https://arabixiv.org/` (S5) [API] — and
-   `arabixiv.org` **redirects back to `osf.io/preprints/arabixiv`** (S6) [WEB], i.e. back to the
-   frozen instance it supposedly left.
-3. The Zenodo community `arabixiv` exists, titled **"ArabiXiv الأرشيف العربي العلمي"**, but was
-   **created 2025-09-17** and holds **78 records** (S7) [API] — against 298 on OSF.
-
-**Assessment.** The migration is real but partial and recent, and the signposting is broken in a
-loop. 298 records on OSF, 78 on Zenodo, and a vanity domain that points at the old home. Cite the
-OSF DOI for anything pre-2025 and check Zenodo separately. Do not assume the Zenodo community is a
-complete mirror — on the numbers, it is not.
-
-## 5. IndiaRxiv — moved hosts, twice, and the relaunch is empty
-
-- **OSF:** https://osf.io/preprints/indiarxiv · **Launched:** 2019 ·
-  **Status: FROZEN** · **Size: 121 preprints** (S5) [API]
-
-The OSF record states: *"IndiaRxiv is no longer able to accept new submissions. Existing content in
-this repository will remain accessible as part of COS's ongoing commitment to Open Science. If it
-is important to you that free author submissions to this site continue, please consider contacting
-**Sridhar Gutam**…"* (S5) [API/DOC]. The advisory board lists academics from Panjabi University,
-LV Prasad Eye Institute, DOAJ, ICAR-IVRI and IIT Indore (S5) [API].
-
-**Three addresses, three different things** (all 2026-09-01):
-
-- `indiarxiv.in` → **redirects to `indiarxiv.wordpress.com`**, a WordPress *blog* (HTTP 200,
-  97,976 B) (S6) [WEB]. The blog explains the history: the repository was launched by
-  **Open Access India** with COS support, but *"due to some reasons, IndiaRxiv could not be with
-  COS but had got a new host, **Society for Promotion of Horticulture (SPH), Bengaluru** which is
-  hosting IndiaRxiv.org"* (S8) [WEB].
-- `indiarxiv.org` → **live OJS/OPS instance**, titled "IndiaRxiv - Preprints Repository of India",
-  **eISSN 2583-0007**, CC BY 4.0, stating preprints are moderated (S9) [WEB]. Admin contact
-  `gutam2000@gmail.com` — the same Sridhar Gutam named on OSF.
-- The OSF instance retains the original 121 preprints.
-
-**But the relaunch has no content.** OAI-PMH on the new instance returns
-`ListIdentifiers` with **zero `<identifier>` elements**, and `Identify` reports an
-`earliestDatestamp` of **2026-09-02** — i.e. essentially *now* (S9) [API]. The archives page
-returned 7,188 bytes with no listed items.
-
-**Assessment.** IndiaRxiv is the clearest single illustration of §0: a real community, a real
-volunteer (named, contactable), a legitimate ISSN — and a relaunched platform that is an empty
-shell while the actual corpus sits frozen on someone else's infrastructure. **Cite the OSF
-records. The `.org` site currently holds nothing you can cite.** Whether the 121 OSF preprints will
-be migrated is **not verified**.
-
-## 6. INArxiv — the one that genuinely closed
-
-- **OSF:** https://osf.io/preprints/inarxiv · **Launched:** 2017 · **Closed: 2020-10-07** ·
-  **Size: 15,987 preprints, still online** (S5) [API]
-
-The OSF description is a farewell notice, quoted here because it is the primary record of the
-closure (S5) [API/DOC]:
-
-> With a heavy heart, we close the INArxiv service starting **October 7, 2020**. Thank you for your
-> participation and support as users until now. […] For your next preprint document, we recommend
-> uploading it to **RINarxiv**.
-
-Steering committee members are listed at Institut Teknologi Bandung (S5) [API].
-
-**What happened to the content: nothing. It is all still there.** 15,987 preprints — **by far the
-largest holding in this entire group**, thirteen times SciELO Preprints — remain served by OSF six
-years after closure (S5) [API].
-
-**What died was everything else.** `www.inarxiv.id` returns **DNS NXDOMAIN on all five
-user-agents** (S6). The recommended successor `rinarxiv.lipi.go.id` fails TLS on all five UAs with
-`no alternative certificate subject name matches target hostname` (S6). (LIPI, the Indonesian
-Institute of Sciences, was reorganised into BRIN in 2021, which is a plausible explanation for a
-stale `lipi.go.id` host — **[INF]**, not verified.)
-
-**Assessment.** The strongest evidence for the §0 thesis in both directions: a server that
-*formally shut down* has better-preserved, more-citable content than three servers that never
-announced a closure. The lesson is entirely about hosting, not about governance or funding.
-
-## 7. LatArXiv — new, real, and already failing at TLS
-
-- **URL:** `https://latarxiv.org/` → redirects to
-  `https://preprints.latarxiv.org/index.php/latarxiv/es/` · **Operator: Paideia Publishing
-  Services** · **Launched: 2024** [INF] · **Status: ALIVE but TLS BROKEN**
-
-**It exists.** The assignment asked whether it exists at all; it does. It is an OJS/OPS instance
-in Spanish, with subject sections including **Ingenierías y Tecnología** (engineering &
-technology), Ciencias Naturales y Exactas, Ciencias Médicas y de la Salud, Ciencias Agrarias,
-Ciencias Sociales y Economía, Artes y Humanidades, and Ciencias Ambientales y de la Tierra
-(S10) [WEB].
-
-**Operator confirmed from its own about page** (S10) [DOC]:
-
-> LatArXiv es una plataforma multidisciplinar que ofrece servicios preprints **a cargo de Paideia
-> Publishing Services**.
-
-**Its TLS certificate expired 12 days before the probe.** `openssl s_client` on 2026-09-01 returned
-`subject=CN=latarxiv.org`, `issuer=C=US, O=Let's Encrypt, CN=R13`, `notBefore=May 22 2026`,
-**`notAfter=Aug 20 19:26:19 2026 GMT`** (S6). All five user-agents failed with
-`curl: (60) certificate has expired`; the site was reachable **only** with `curl -k`
-(HTTP 200, 47,681 B). A Let's Encrypt certificate expiring means automated renewal stopped and
-nobody noticed — on a platform under two years old.
-
-**Business model.** Two intake routes: an **Open** section where any author may upload freely, and
-per-journal sections where **member journals' editors** submit on behalf of their journal, under a
-**membership** scheme (S10) [WEB]. Default licence **CC BY 4.0**, with authors and editors free to
-choose others (S10) [DOC].
-
-**Moderation** (S10) [DOC]: *"Todas las preimpresiones serán **moderadas** para determinar si se
-ajustan a los objetivos y alcance de este servidor"* — a scope check, not peer review. Authors are
-responsible for permissions, all authors must consent, and ethics-committee approval is required
-where applicable.
-
-**Size: not verified.** The OAI-PMH endpoint at
-`preprints.latarxiv.org/index.php/latarxiv/oai?verb=Identify` returned an **empty body** and
-`ListIdentifiers` returned zero identifiers (S6) [API]. Visible content on the front page is dated
-**2024-12-30** and **2025-07-15**, which supports a 2024 launch but does not prove it — the launch
-year is **[INF]**, not verified. The editorial-team page `es/about/editorialTeam` returns **404**
-(S6) [WEB].
-
-**Assessment.** Honest verdict: a commercially operated, genuinely functioning Spanish-language
-server with real engineering scope — displaying, at two years old, three of the classic
-abandonment signals simultaneously (expired certificate, non-functional OAI, missing editorial
-team page). It is too new and too under-maintained to cite with confidence. Check it again before
-relying on it.
-
-## 8. Preprints.ru (NEICON)
-
-- **URL:** https://preprints.ru/ · **Operator: NEICON (НЭИКОН)** · **Launched: autumn 2019** ·
-  **Status: ALIVE** · **Size: 3,063 preprints**
-
-Reachable on the **default curl UA** (HTTP 200, 27,658 B) — no UA substitution needed, and no
-geoblock encountered from this vantage point (S6) [WEB].
-
-**Operator and funding, from its own about page** (S11) [DOC]:
-
-> PREPRINTS.RU – открытый мультидисциплинарный онлайн-архив и сервис для препринтов. Он
-> **управляется и финансируется некоммерческим партнерством НЭИКОН**, одной из ведущих российских
-> организаций в области распространения, издания и обеспечения доступа к научной информации.
-
-— managed and funded by the non-profit partnership NEICON. "Начал работу **осенью 2019 г.**"
-(began operation in autumn 2019) (S11) [DOC].
-
-**Size: 3,063**, read from the search page's result counter (`найдено: 3063`) with an empty query
-(S12) [WEB]. No OAI-PMH endpoint was found at the conventional paths (`/oai`, `/index.php/oai`
-both HTTP 404) (S6) [API].
-
-**Moderation: pre-moderation by literal volunteers.** The about page states *"Контент на
-PREPRINTS.RU проходит **предварительную модерацию, но не рецензируется**"* (content undergoes
-preliminary moderation but is not peer reviewed), and — the detail that matters for §0 —
-openly recruits them (S11) [DOC]:
-
-> Если вы хотите присоединиться к **волонтерскому сообществу модераторов** и модерировать
-> поступающие на рассмотрение препринты, напишите нам письмо (info@preprints.ru).
-
-This is the "one or two volunteers" pattern stated by the operator itself, not inferred.
-
-**Computing/engineering content: nominally yes.** Rubrics include
-**Математика, информатика, кибернетика** (mathematics, informatics, cybernetics),
-**Промышленность, технологии** (industry, technologies) and **Энергетика** (energy). Per-rubric
-counts **not verified** — I could not establish the category-filter URL scheme (S6)
-**[NOT-VERIFIED]**.
-
-**An honest observation about content quality.** The three most recent preprints on the front page
-on 2026-09-01 were: *"A Rheological Approach to the Viscous Fermionic Vacuum Condensate. VII.
-Universal Rheological Limit of Macro-Solitons…"* framed within a self-named "PROJECT OCEAN
-paradigm" and "Fermionic Universe Hypothesis"; *"Recalibration of the UAT/UCP Acoustic Horizon…"*;
-and *"Новая трактовка гравитации"* (a new interpretation of gravity) (S6) [WEB]. That is three out
-of three front-page items in fringe cosmology. A single snapshot is not a survey, and I present it
-as exactly that — but it is what the front page showed, and volunteer pre-moderation for scope is
-a weak filter against determined fringe submitters.
-
-**Assessment.** Live, honestly documented, and technically unremarkable. Durability risk is
-structural rather than technical: a single national non-profit, volunteer moderation, no OAI-PMH
-for third-party harvesting or mirroring, and — **[INF]**, flagged as inference — a geopolitical
-environment in which international infrastructure links to Russian scholarly services have proved
-fragile. The absence of OAI-PMH is the concrete problem: nothing else can mirror it.
-
-## 9. AIJR Preprints
-
-- **URL:** https://preprints.aijr.org/ (resolves to `/index.php/ap`) · **Operator: AIJR
-  Publisher**, India · **Launched: 2020** · **Status: ALIVE** · **Size: 188 records**
-
-OAI-PMH `Identify` returns `repositoryName` **"AIJR Preprints"**, `adminEmail`
-`preprints@aijr.org`, `earliestDatestamp` **2020-03-22T15:51:39Z**, confirming the 2020 launch
-(S13) [API]. `ListSets` gives four sets: **Working Paper, Coronavirus, Preprints, Under Review**
-(S13) [API].
-
-**Size: 188.** The endpoint does not emit `completeListSize`, so I counted `<identifier>` elements
-across `ListIdentifiers` with resumption-token paging; it completed in a single page of **188**
-with no resumption token (S13) [API]. This is a very small server.
-
-**Self-description** (S14) [DOC]: *"AIJR preprint server is dedicated to publishing early research
-work (**without Peer Reviewing**)…"*. The **Working Paper** section is for work not yet submitted
-anywhere, updatable with a DOI once published; there is also an **Under Review** section.
-
-### Is AIJR on a predatory-publisher watchlist? — checked, and the answer is no
-
-This needs care because a near-identical acronym *is* listed, and conflating them would be a
-serious and unfair error.
-
-- **AIJR Publisher does *not* appear on the Beall's List successor's publishers list.** Searching
-  `https://beallslist.net/` for "aijr" and for "american international" returned **no matches**
-  (S15) [WEB].
-- **The standalone-journals list contains one "AIJR"-like hit, and it is a different
-  organisation.** The entry is *"**Ahead International Journal of Recent Research Review**
-  (AIJRRR)"*, linked to `http://www.aijrrr.com/` (S15) [WEB]. That is a journal title beginning
-  "Ahead International…", not AIJR Publisher of `aijr.org`. For completeness, `www.aijrrr.com`
-  **does not resolve** (DNS NXDOMAIN, 2026-09-01) (S6).
-- `https://aijr.org/` is live (HTTP 200, 158,968 B), titled "AIJR Publisher: Scholarly Journals &
-  Books Publishing Solutions" (S6) [WEB].
-
-**So: no watchlist finding against AIJR Publisher, and the superficially similar AIJRRR entry is a
-different, now-defunct entity.** State it that way; do not let the acronym collision propagate.
-
-**What I did *not* check, and will not imply:** membership of DOAJ, COPE or OASPA; APC structure;
-editorial-board verification; any of the other independent quality signals one would want for a
-small commercial publisher. **[NOT-VERIFIED]**
-
-**Assessment.** A small commercial publisher's preprint server, technically well-behaved — working
-OAI-PMH, clear sections, honest "no peer review" statement, and no adverse watchlist finding. The
-reservations are structural rather than reputational: 188 records in six years is barely a
-repository, there is no institutional or national backing, and the durability of a preprint archive
-attached to a single small commercial publisher depends entirely on that firm's continued
-existence. There is no obvious reason to *avoid* it and little reason to *use* it.
-
-## 10. Sources
-
-- **S1** — Jxiv OAI-PMH, `https://jxiv.jst.go.jp/index.php/jxiv/oai` (`Identify`,
-  `ListIdentifiers`, `ListSets`, `ListRecords`) · retrieved 2026-09-01. Size 1,221,
-  `earliestDatestamp` 2022-03-24, discipline sets, language sample.
-- **S2** — Jxiv submission requirements,
-  `https://jxiv.jst.go.jp/index.php/jxiv/about/submissions` · retrieved 2026-09-01. JST publication
-  authority, no-withdrawal clause, identity registration, prior-posting exclusion.
-- **S3** — SciELO Preprints OAI-PMH,
-  `https://preprints.scielo.org/index.php/scielo/oai` · retrieved 2026-09-01.
-  `completeListSize` 5,689, `earliestDatestamp` 2020-04-06, sets, language distribution.
-- **S4** — SciELO Preprints "Sobre o Servidor",
-  `https://preprints.scielo.org/index.php/scielo/about` · retrieved 2026-09-01. Crossref auto-post
-  rule, triagem básica, ORCID requirement, prior-publication exclusion, OPS/PKP basis, page version
-  dated 21 May 2025.
-- **S5** — OSF API v2, `https://api.osf.io/v2/providers/preprints/{africarxiv,arabixiv,indiarxiv,
-  inarxiv}/` and `…/preprints/?page[size]=1` · retrieved 2026-09-01. Provider descriptions,
-  `allow_submissions`, `reviews_workflow`, advisory boards, and `links.meta.total` counts
-  (479 / 298 / 121 / 15,987).
-- **S6** — Live reachability probes with the `AGENTS.md` UA ladder, plus `openssl s_client` ·
-  2026-09-01. All rows of the §1 table, TLS failures, DNS NXDOMAIN results, negative controls.
-  Probe script and raw per-host logs in
-  `doc/hardware/scratch/preprint-repositories/regional/` (`ua-ladder-probe.sh`, `res_*.txt`).
-- **S7** — Zenodo API, `https://zenodo.org/api/communities/arabixiv` and
-  `https://zenodo.org/api/records?communities=arabixiv&size=1` · retrieved 2026-09-01. Community
-  created 2025-09-17; 78 records.
-- **S8** — IndiaRxiv blog, `https://indiarxiv.wordpress.com/` (via redirect from
-  `indiarxiv.in`) · retrieved 2026-09-01. Open Access India origin, COS departure, SPH Bengaluru
-  hosting.
-- **S9** — IndiaRxiv OJS instance, `https://indiarxiv.org/index.php/ops` and its OAI-PMH endpoint ·
-  retrieved 2026-09-01. eISSN 2583-0007, CC BY 4.0, moderation statement, and the zero-record
-  `ListIdentifiers` result with `earliestDatestamp` 2026-09-02.
-- **S10** — LatArXiv, `https://preprints.latarxiv.org/index.php/latarxiv/es/`, `…/es/about` and
-  `…/es/about/submissions` · retrieved 2026-09-01 **with `curl -k` (expired certificate)**.
-  Paideia Publishing Services operatorship, sections, membership model, CC BY 4.0, moderation
-  statement.
-- **S11** — Preprints.ru "О проекте", `https://preprints.ru/about` · retrieved 2026-09-01. NEICON
-  operatorship and funding, autumn 2019 start, pre-moderation-not-peer-review, volunteer moderator
-  recruitment.
-- **S12** — Preprints.ru search, `https://preprints.ru/search?q=` · retrieved 2026-09-01. Result
-  counter `найдено: 3063`.
-- **S13** — AIJR Preprints OAI-PMH, `https://preprints.aijr.org/index.php/ap/oai` · retrieved
-  2026-09-01. `earliestDatestamp` 2020-03-22, four sets, 188 identifiers counted with
-  resumption-token paging.
-- **S14** — AIJR Preprints about page, `https://preprints.aijr.org/index.php/ap/about` · retrieved
-  2026-09-01. "without Peer Reviewing", section definitions.
-- **S15** — Beall's List successor, `https://beallslist.net/` and
-  `https://beallslist.net/standalone-journals/` · retrieved 2026-09-01 **with the Chrome 131 UA**.
-  No AIJR Publisher entry; the sole acronym-adjacent entry is "Ahead International Journal of
-  Recent Research Review (AIJRRR)", `aijrrr.com`.
-
-### Retrieval / crawler notes
-
-Findings for the repository's crawler access table, all **2026-09-01**:
-
-- **Default `curl` UA sufficed** for: `jxiv.jst.go.jp`, `preprints.scielo.org`, `preprints.ru`,
-  `preprints.aijr.org`, `aijr.org`, `osf.io`, `api.osf.io`, `zenodo.org`, `africarxiv.org`,
-  `indiarxiv.in`/`indiarxiv.wordpress.com`, `indiarxiv.org`, `global.chinaxiv.org`. No rate
-  limiting or bot-block observed.
-- **Chrome 131 UA needed** for: `beallslist.net` (used pre-emptively; default UA not separately
-  tested — so this is **not** evidence that the default is blocked there).
-- **All five UAs failed — not a UA problem:**
-  - `africarxiv.pubpub.org` — HTTP **403** on default, Chrome 131, WhatsApp, ChatGPT-User and
-    ClaudeBot. A genuine block; note the ChatGPT-User response was only 25 bytes while the others
-    were ~5.5 kB, i.e. the block page differs by agent.
-  - `www.inarxiv.id` — DNS **NXDOMAIN**.
-  - `africarxiv.ubuntunet.net` — TLS **certificate expired**.
-  - `rinarxiv.lipi.go.id` — TLS **hostname mismatch**.
-  - `latarxiv.org` / `preprints.latarxiv.org` — TLS **certificate expired 2026-08-20**;
-    retrievable **only** with `curl -k`.
-- **General tip:** for OJS/OPS-based servers (Jxiv, SciELO, AIJR, LatArXiv, IndiaRxiv), the
-  `/oai?verb=Identify` and `/oai?verb=ListIdentifiers&metadataPrefix=oai_dc` endpoints are far more
-  reliable and cheaper than scraping, and `completeListSize` gives an exact count in one request —
-  **except** on AIJR (no `completeListSize`; count identifiers instead) and LatArXiv (endpoint
-  returns an empty body).
diff --git a/research/preprint-repositories/reliability-and-durability.md b/research/preprint-repositories/reliability-and-durability.md
deleted file mode 100644
index ec04466..0000000
--- a/research/preprint-repositories/reliability-and-durability.md
+++ /dev/null
@@ -1,222 +0,0 @@
-# Reliability and durability — a cross-server assessment
-
-The two questions worth asking about any preprint server, answered comparatively:
-
-1. **What does a deposit here actually guarantee?** (reliability)
-2. **Will the link still resolve in five years?** (durability)
-
-- **Compiled:** 2026-09-01 / 2026-09-02 from the 29 records in this directory.
-- Evidence labels as defined in [`README.md`](README.md#evidence-and-method).
-- **Nothing here is a judgement of any individual paper.** These are properties of *servers*.
-
----
-
-## 1. Reliability is a question about the gate, not about the badge
-
-Every server on the Wikipedia list describes itself in roughly the same language. They differ
-enormously in what actually happens to a submission. Sorting by the **gate** rather than by the
-marketing is the single most useful thing in this survey.
-
-| Gate type | Servers | What a deposit proves |
-|---|---|---|
-| **Endorsement + subject moderation** | [arXiv](arxiv.md) | An endorsed author, a plausible subject fit, and a permanent timestamp. **Not** correctness |
-| **Named editorial screening** | [Cryptology ePrint](cryptology-eprint-archive.md) (4 published criteria, 3 named editors) · [Optimization Online](optimization-online.md) (coordinators; explicitly instructed to reject work that "should not be obviously crazy or wrong (e.g. P=NP papers)") | Relevance and non-obvious-crackpottery. Both operators **explicitly disclaim** verifying anything further |
-| **Staff screening against published criteria** | [bioRxiv/medRxiv](biorxiv-and-medrxiv.md) (incl. dual-use/biosecurity) · [Preprints.org](preprints-org.md) (24 h screen with an explicit pseudoscience filter) | Non-scientific content, plagiarism and harm were checked for. Not the science |
-| **Pre-moderation** | [BioHackrXiv](biohackrxiv.md) (`reviews_workflow: pre-moderation`; 172 accepted / 1 withdrawn) | A human looked before it went live |
-| **Completeness / scope moderation** | [HAL](hal.md) · [ChinaXiv](chinaxiv.md) (four automated checks + admin review, incl. an explicit **political-content** criterion stated by the operator) | Metadata and institutional fit. Note the ChinaXiv criterion is *not* a scientific one |
-| **Affiliation or funder gate** | Wellcome / Gates / HRB / AMRC / Open Research Africa ([life-sciences record](life-science-and-medical-platforms.md)) | The author is funded by the sponsor. That is all |
-| **Journal-submission gate** | [Research Square](research-square.md) *In Review* · ARPHA · Beilstein · JMIR | A named journal accepted it **for review**. Nothing about the verdict |
-| **Post-hoc open review** | [F1000Research](life-science-and-medical-platforms.md) · [Qeios](qeios.md) · [ScienceOpen](scienceopen.md) | Read the reviews themselves; the label means little |
-| **None whatsoever** | [Zenodo](zenodo.md) · [figshare](figshare.md) · [viXra](vixra.md) | A DOI and a timestamp. Zenodo and figshare are honest about this; **viXra is too** — see below |
-
-### The two honest extremes
-
-**Zenodo** accepts anything and says so. That is a *feature* — it is a general-purpose archive, not
-a preprint server, and treating a Zenodo DOI as a quality signal is a category error made by the
-citer, not by CERN.
-
-**viXra** is more candid than most of the platforms above it. Its own text: *"acceptance in viXra
-may not confer scientific credibility"* and *"viXra may contains some work of low value or
-usefulness."* It has no endorsement, no correctness review, no DOIs, no licence and no dark archive.
-**Do not cite viXra as evidence for anything.** The only defensible uses are a priority timestamp
-and studying viXra itself.
-
----
-
-## 2. Measured outcomes, where they exist
-
-Almost no server publishes what fraction of its deposits are eventually peer-reviewed. Two figures
-in this pass are real measurements rather than claims.
-
-| Server | Cohort | Publication rate | Method |
-|---|---|---|---|
-| **bioRxiv** | 2016 week | **77.8%** (n=108) | API `published` field, deduped by DOI |
-| **bioRxiv** | 2018 week | **71.1%** (n=467) | as above |
-| **bioRxiv** | 2019 week | **69.1%** (n=661) | as above |
-| **bioRxiv** | 2020 week | **71.9%** (n=1,137) | as above |
-| **medRxiv** | Oct 2019 | **79.9%** (n=189) | as above |
-| **medRxiv** | 2020 week | **64.5%** (n=575) | as above |
-| **Cryptology ePrint** | 2017 | **61.7%** (95% Wilson CI 49.0–72.9%, n=60) | systematic sample; a **lower bound**, since the field is author-maintained |
-
-bioRxiv's 69–78% for mature cohorts agrees with the operator's own "75%" claim and with Abdill &
-Blekhman (*eLife* 2019). Recent cohorts (2022: 58.9%, 2024: 50.7%, 2025: 47.3%) are **censored, not
-declining** — they have not had time to publish.
-
-For **arXiv, OSF Preprints, SSRN, TechRxiv, engrXiv, ECSarXiv, ChinaXiv, Preprints.org and Research
-Square** the rate is **[NOT-VERIFIED]** — no citable measurement was found. Preprints.org claims
-58.44% "converted to peer-reviewed article" but publishes no method and we found no independent
-replication.
-
-A useful negative result on arXiv: **only 6 of the 79 verified landmark papers carry a `journal_ref`
-at all.** In machine learning the arXiv document is frequently the permanent version of record, and
-absence of venue metadata is therefore *not* evidence of low quality — it is the field's norm.
-
----
-
-## 3. The AI-slop inflection, 2025
-
-Three independent operators changed policy in the same window, which is worth reading as one event
-rather than three.
-
-- **arXiv, October 2025** — surveys and position papers in `cs.*` must now **complete peer review
-  before** arXiv will accept them, documented with a DOI or journal reference. Verified and quoted
-  in [arXiv §4](arxiv.md). A January 2026 tightening also removed institutional email as sufficient
-  grounds for endorsement.
-- **Center for Open Science, 2025-08-25** — closed its **generalist** OSF Preprints server to new
-  submissions, citing *"suspicious or low-quality submissions … generative AI and paper mills"*.
-  Still suspended as of 2026-04-21. Thesis Commons separately suspended 2026-06-03. Note that COS's
-  own headline was *"Community Servers Hosted by OSF Preprints Remain Active"* — the community
-  servers were **not** wound down.
-- **engrXiv, 2025** — the only operator in this survey to publish a rejection rate: submissions rose
-  from 60 to 200/month and **roughly half of 2025 submissions were declined**. Their figure
-  cross-checks exactly against the registry (1,151 posted in 2025 vs their "nearly 1200").
-
-**Implication.** A deposit dated before ~2024 was screened under a materially weaker filter for
-machine-generated text than one dated after. That cuts both ways: older deposits predate the flood,
-newer ones passed a stricter gate.
-
----
-
-## 4. Commercial entanglement — three cases to disclose when citing
-
-Not accusations. Structural facts a reader should know.
-
-**[Preprints.org](preprints-org.md) is operated by MDPI.** MDPI's contested standing concerns
-*journal peer review at scale* — special-issue volume, and Clarivate's February 2023 delisting of
-IJERPH and JRFM. That does **not** transfer cleanly to a server which makes no peer-review claim,
-and MDPI's rebuttals had teeth (the Oviedo-García paper drew an Expression of Concern and a
-Correction). What *does* transfer is the funnel: **230 of the 232 "Preprints Friendly Journals" are
-MDPI titles.**
-
-**[Research Square](research-square.md) is wholly owned by Springer Nature**, auto-posts manuscripts
-from 1,503 Springer Nature/BMC journals via *In Review*, and sells the same authors AJE editing
-services. **This ownership is stated nowhere on the preprint site.** The critical mechanic: **on
-rejection the preprint stays but the journal branding and review timeline are stripped**, so an
-unbranded Research Square preprint is indistinguishable from a rejected one.
-
-**[SSRN](ssrn.md) is owned by Elsevier** (acquired 2016). In 2016–2017 SSRN removed papers over
-copyright claims — documented from Inside Higher Ed, including the verbatim revision comment and
-Gordon's "about 20 papers". A commercial host can and did delete deposits. Contrast with
-[Cryptology ePrint](cryptology-eprint-archive.md), where reports are never removed, and arXiv, where
-withdrawal creates a *new version* and prior versions including full text remain accessible
-permanently (`deletedRecord=persistent` in OAI-PMH).
-
----
-
-## 5. Durability — the headline result
-
-**Preprint servers do not lose data. They lose front doors.**
-
-Of eighteen closed, frozen or migrated servers probed in this pass, **seventeen still serve their
-corpus**. Full table in [`closed-and-defunct-servers.md`](closed-and-defunct-servers.md); the
-representative cases:
-
-| Server | Fate | Retrievable 2026-09-02? |
-|---|---|---|
-| **Nature Precedings** (2007–2012) | Publisher discontinued it; `precedings.nature.com` refuses TCP | **Yes, incl. full text** at `nature.com/npre`; a `10.1038/npre.*` DOI resolves 200 |
-| **CogPrints** (1997–2017) | Founder retired; HTTPS fails on a cert **SAN mismatch** | **Yes** — over plain HTTP it 301s to a Southampton static archive. A preservation *success* presenting as a failure |
-| **mp_arc** (Jul 1991 – Dec 2023) | Closed deliberately, with a published preservation promise | **Yes — the best-preserved dead archive measured.** Its 1991 PostScript file still carries a **gzip mtime of 1997-04-26** and downloads intact |
-| **INArxiv** (2017–2020) | Closed; successor `rinarxiv.lipi.go.id` serves a self-signed `CN=linux` default | **Yes — 15,987 preprints** via the OSF API |
-| **PeerJ Preprints** (2013–2019) | Stopped accepting deposits | **Yes** via DOI; direct fetches 403 on all five UAs |
-| **agriRxiv** | **Domain is a Namecheap parking page** | **Yes** — service migrated OSF → CABI Digital Library; DOIs resolve |
-| **Eyexiv** (2022) | Four TLDs NXDOMAIN; not an OSF provider | **No.** The only genuinely lost entry on the list |
-
-Six of eleven platforms in the life-sciences group had a discontinuity. **DOIs survived every one of
-them. Hostnames survived none.**
-
-### The TLS signal, and its limit
-
-An expired or never-issued certificate is a **high-precision** abandonment signal. Verified:
-`africarxiv.ubuntunet.net` expired 2026-07-25; `latarxiv.org` expired 2026-08-20 19:26:19;
-`rinarxiv.lipi.go.id` runs a self-signed `CN=linux` default from 2023.
-
-**But the converse is false.** `bodoarxiv.org` (now an **online-casino page**), `lawarxiv.org` (a
-114-byte parking stub), `mediarxiv.org` (redirects to an unrelated site) and `frenxiv.org` (frozen
-since October 2020) all hold **fresh, auto-renewed certificates**. Parking services run ACME too.
-In this dataset, **TLS automation outlived editorial staffing in every divergent case.** A valid
-certificate proves nothing.
-
-Worse, COS's own live provider description for BodoArXiv still directs readers to the casino domain.
-
-### What actually breaks
-
-| Failure mode | Example | Content lost? |
-|---|---|---|
-| Grant expiry / founder retirement | CogPrints, LISSA | No |
-| Publisher strategy change | Nature Precedings, PeerJ Preprints | No |
-| Platform migration breaking URL grammar | TechRxiv (figshare → Authorea, Dec 2023); ChemRxiv (figshare → Cambridge Open Engage → **a third platform, Jan 2026**) | No — DOIs held |
-| Self-hosted successor never configured | INArxiv → rinarxiv, AfricArXiv → ubuntunet | No — original survived on OSF |
-| Domain lapse to a squatter | BodoArXiv, agriRxiv, LawArXiv | No |
-| Everything at once | **Eyexiv** | **Yes** |
-
----
-
-## 6. Practical rules
-
-**Citing.**
-1. **Cite the DOI or the server-native identifier, never the URL.** DOIs survived every
-   discontinuity measured here; hostnames survived almost none.
-2. **On Zenodo, cite the *version* DOI, not the concept DOI** — the concept DOI silently moves to
-   the next release.
-3. **Check whether the preprint was later published.** bioRxiv/medRxiv expose this in the API;
-   ePrint carries a publication-info string; arXiv has `journal_ref` (but absence proves nothing —
-   see §2).
-4. **Disclose operator entanglement** when citing Preprints.org, Research Square or SSRN.
-5. **Never cite viXra as evidence.**
-
-**Depositing.**
-1. Prefer a server with a **named dark archive**. Preprints.org states Portico. **We found no
-   Portico/CLOCKSS/LOCKSS statement for ScienceOpen, Qeios, viXra, mp_arc, Rutgers Optimality
-   Archive, LingBuzz or any OSF provider** — recorded as unverified, not as "none".
-2. **Mirror to Zenodo.** It is CERN-backed, versioned, never deletes, and is the closest thing to a
-   durability floor available.
-3. **Submit valuable, hard-to-find URLs to `web.archive.org/save/`** — consistent with this
-   repository's [existing archival practice](../../AGENTS.md).
-4. For research **software**, the deposit that matters is the Zenodo/GitHub release DOI, not a
-   paper.
-
-**Judging an unfamiliar server, in order.**
-1. Find its gate in §1. If you cannot determine the gate, treat it as "none".
-2. Check whether it mints DOIs and with which registrar (Crossref `posted-content`, DataCite).
-   [Synthical](synthical.md) is registered with **neither** — it hosts nothing.
-3. Compare its *hosted* count with its *advertised* count. ScienceOpen advertises ~100 M and hosts
-   ~3,584; OSF's ">1,000,000" was federated metadata.
-4. Probe a **bogus path**. If it returns 200, no status-code check on that host means anything —
-   see [`README.md § Probing traps`](README.md#6-probing-traps).
-5. Check the operator's most recent deposit date, not its launch date.
-
----
-
-## 7. Ranked summary
-
-Combining gate strength, measured outcomes, technical relevance and durability. **Reliability here
-means "how much does a deposit tell you", not "how good is the science".**
-
-| Tier | Servers | Rationale |
-|---|---|---|
-| **Use with confidence** | [arXiv](arxiv.md) · [Cryptology ePrint](cryptology-eprint-archive.md) · [HAL](hal.md) · [bioRxiv/medRxiv](biorxiv-and-medrxiv.md) | Real gates, institutional backing, permanent versioning, measured or structurally sound outcomes. In their fields the deposit is frequently the version of record |
-| **Use, with the operator disclosed** | [Zenodo](zenodo.md) · [TechRxiv](techrxiv.md) · [ChemRxiv](chemrxiv.md) · [Optimization Online](optimization-online.md) · [ECSarXiv](ecsarxiv.md) · [engrXiv](engrxiv.md) · [BioHackrXiv](biohackrxiv.md) · [SSRN](ssrn.md) | Sound but each has a specific caveat — no review (Zenodo), commercial owner (SSRN, TechRxiv), tiny corpus (ECSarXiv), or a restrictive licence (Optimization Online: **download for personal use only, no CC licence at all**) |
-| **Verify independently before relying** | [Preprints.org](preprints-org.md) · [Research Square](research-square.md) · [ChinaXiv](chinaxiv.md) · [figshare](figshare.md) · [OSF providers](osf-preprints.md) · [Qeios](qeios.md) | Usable for discovery. The gate is weak, absent, or measures something other than quality |
-| **Discovery only — hosts little or nothing** | [ScienceOpen](scienceopen.md) · [Synthical](synthical.md) · [RePEc](repec-and-econstor.md) | Index or aggregation layers. RePEc is explicit that it stores nothing; Synthical mints nothing |
-| **Do not cite as evidence** | [viXra](vixra.md) | No gate of any kind, by design and by the operator's own statement |
-| **Durability risk regardless of content** | [Authorea](authorea.md) (submissions suspended May 2026) · [ScienceOpen](scienceopen.md) (no preservation arrangement found) · the frozen [regional servers](regional-and-national-servers.md) · [Eyexiv](natural-sciences-and-niche-servers.md) (lost) | Cite the DOI, and archive a copy yourself |
diff --git a/research/preprint-repositories/repec-and-econstor.md b/research/preprint-repositories/repec-and-econstor.md
deleted file mode 100644
index 13c1b9f..0000000
--- a/research/preprint-repositories/repec-and-econstor.md
+++ /dev/null
@@ -1,554 +0,0 @@
-# RePEc and EconStor — economics working-paper infrastructure record
-
-A **combined record**, because the two interlock: RePEc is a metadata federation that owns
-no documents, and EconStor is one of the full-text repositories whose documents RePEc
-indexes. Reading either alone produces a wrong mental model.
-
-- **RePEc URL:** http://repec.org/ (the initiative) · https://ideas.repec.org/ (largest
-  front end) · https://econpapers.repec.org/ (second front end)
-- **RePEc operator:** a **volunteer federation**, not an institution. "RePEc is a
-  crowd-sourced effort: a) thousands of people and organizations contribute the underlying
-  data, b) a core team of contributors manage the system, and c) sponsor organizations
-  provide the infrastructure. As such, the RePEc initiative has no central expenses" (S1)
-  [DOC].
-- **RePEc launched:** **1997-05-12**, at a meeting in Guildford, UK (S6) [DOC].
-- **EconStor URL:** https://www.econstor.eu/ · OAI-PMH
-  https://www.econstor.eu/oai/request
-- **EconStor operator:** **ZBW – Leibniz Information Centre for Economics**, Kiel/Hamburg,
-  Germany. DSpace-based (S9) [API].
-- **EconStor launched:** **2009** — earliest OAI datestamp **2009-01-28T14:13:20Z** (S9)
-  [API], corroborating Wikipedia's 2009 (S11).
-- **Status:** both active.
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Relevance warning, stated up front.** A hardware or software engineer will almost never
-> need either of these. EconStor's entire *Data processing / Computer science* holding is
-> **36 records** out of 320,533 (§5.2) [API]. They are in this collection because Wikipedia
-> lists them as preprint repositories, because RePEc is the best working example of an
-> architecture (federated metadata, no central store) that the rest of scholarly publishing
-> never adopted, and because the *econ.\** / `cs.GT` overlap with arXiv is real if narrow
-> (§6).
-
----
-
-## 1. What RePEc is — and the key finding
-
-**RePEc is not a repository.** It stores no papers. It is a **decentralised metadata
-federation** with a shared file format and a shared naming convention, on top of which
-several independent websites are built.
-
-The mechanism, in the initiative's own words: "Every publisher or provider puts text files
-describing their publications on their own server. These files follow a simple but rigorous
-machine-readable syntax. They are then automatically mirrored and made available to the
-public on the various RePEc websites. … **RePEc is thus a facilitator that organizes the
-data for others to use.**" (S1) [DOC]
-
-So when a central bank, a university department or a commercial publisher "joins RePEc", it
-does not upload anything. It puts a directory of plain-text metadata files on its own web or
-FTP server, structured according to the **Guildford Protocol**, with fields defined by
-**ReDIF** (Research Documents Information Format). RePEc's scripts walk the archives
-nightly. The PDF stays wherever the publisher put it.
-
-This has three consequences that matter:
-
-1. **No single point of failure for content, but no guarantee of it either.** If a
-   department reorganises its website, its RePEc links rot and RePEc cannot fix them —
-   it never had the file.
-2. **"RePEc has N papers" is a federation-wide count of *metadata records*, not of
-   documents held.** See §3.
-3. **RePEc long predates and structurally out-performs OAI-PMH for its purpose.** ReDIF
-   dates from 1997; it is a domain-specific format with entity types RePEc actually needs
-   (working paper, article, book, chapter, **software component**, person, institution)
-   rather than generic Dublin Core.
-
-### 1.1 The architecture — who does what
-
-| Component | Role | Where it runs |
-|---|---|---|
-| **RePEc** (`repec.org`) | the initiative, protocols, the data itself | Kit Baum (Boston College) is "proprietor of the repec.org domain" (S5) [DOC] |
-| **ReDIF / Guildford Protocol** | the metadata format and the archive-discovery convention | specs at `ideas.repec.org/p/rpc/rdfdoc/` (S1) |
-| **IDEAS** (`ideas.repec.org`) | the largest front end; browse, search, rankings, author profiles | run by **Christian Zimmermann** (S2, S5) |
-| **EconPapers** (`econpapers.repec.org`) | the second front end, same data, different UI | hosted by the **School of Business at Örebro University**, Sweden; run by Sune Karlsson (S3, S5) [WEB] |
-| **NEP** (`nep.repec.org`) | *New Economics Papers* — human-edited email/RSS current-awareness reports by field | Thomas Krichel maintains the software; Marco Novarese directs it (S5) |
-| **RAS / RePEc Author Service** (`authors.repec.org`) | author registration and profile linking | Krichel/Zimmermann (S5) |
-| **EDIRC** (`edirc.repec.org`) | directory of economics institutions | Zimmermann; started 1996-03-07 with 350 entries (S6) |
-| **CitEc** (`citec.repec.org`) | citation extraction and analysis | José Manuel Barrueco Cruz, University of Valencia (S5) |
-| **LogEc** (`logec.repec.org`) | download/access statistics | Sune Karlsson (S5) |
-| **MPRA** (`mpra.ub.uni-muenchen.de`) | Munich Personal RePEc Archive — the deposit-of-last-resort for authors whose institution has no archive | University of Munich library (S1, S5) |
-| **CollEc**, **RePEc Genealogy**, **RePEc Biblio**, **EconAcademics**, **SocioRePEc** | co-authorship centrality, academic family tree, curated bibliography, blog aggregator, PDF annotation | various (S1) |
-| **RePEc Plagiarism Committee** (`plagiarism.repec.org`) | publishes adjudicated plagiarism cases | volunteer committee (S7) |
-
-### 1.2 The Federal Reserve Bank of St. Louis relationship — precisely stated
-
-Wikipedia's list names the **Federal Reserve Bank of St. Louis** as RePEc's operator (S11).
-**That is a half-truth and worth correcting.** What is verifiable: IDEAS is run by
-**Christian Zimmermann**, who "is Assistant Vice President at the Federal Reserve Bank of St.
-Louis" and "is in charge of the IDEAS, EDIRC, RePEc Genealogy and RePEc Biblio sites" (S5)
-[DOC]. The Fed therefore hosts and effectively underwrites **IDEAS**, the largest RePEc front
-end. It does not operate RePEc. RePEc "has no central expenses" and no central operator at
-all (S1) [DOC]; EconPapers runs at Örebro; MPRA at Munich; the metadata sits on 2,400+
-publishers' own servers.
-
-The RePEc origin story is worth one line because it is genuine internet history: **Thomas
-Krichel**, then a Lecturer in Economics at the University of Surrey, "set up NetEc" on
-**gopher** in **February 1993** — a consortium including WoPEc (online papers), BibEc,
-CodEc (software), WebEc, BizEc, HoPEc and JokEc. NetEc moved to the web in 1994. RePEc
-proper was founded at the Guildford meeting on **1997-05-12**; the LSE Financial Markets
-Group was the first archive to join, on 1997-05-27; IDEAS launched in September 1997 with
-**40,000 items** (S6) [DOC].
-
-## 2. What EconStor is
-
-**EconStor is an actual repository** — ZBW's DSpace instance, holding full text. It exists
-because German economics research institutes, and later a wide international set, needed a
-place to put working papers with a persistent handle. Every EconStor record carries a
-handle in the `10419/…` namespace (sample identifier `oai:econstor.eu:10419/1234`, S9)
-[API].
-
-EconStor is also **a RePEc archive**: it appears on RePEc's own list of "Additional websites
-using RePEc" (S1) [DOC], and its holdings surface through IDEAS and EconPapers. This is
-exactly the relationship the combined record exists to make visible: **EconStor holds the
-PDFs; RePEc indexes the metadata; IDEAS displays it.** Three layers, three operators, one
-document.
-
-## 3. Size — RePEc
-
-### 3.1 EconPapers' live counter (the best single source)
-
-`https://econpapers.repec.org/`, retrieved 2026-09-01; the page footer reads "Page updated
-2026-09-02" (S3) [WEB]:
-
-| Item type | Count | of which downloadable | in |
-|---|---|---|---|
-| Working Papers | **1,316,031** | 1,111,325 | 5,915 series |
-| Journal Articles | **3,759,295** | 3,681,849 | 4,681 journals |
-| Software Items | **6,039** | 6,025 | 37 series |
-| Books | **69,352** | 33,618 | 680 series |
-| Chapters | **338,841** | 104,243 | 365 series |
-| **Total searchable** | **5,489,558** | **4,937,060 available online** | |
-
-Plus "74,118 Authors and 14,568 individuals have registered in the RePEc Author Service".
-
-### 3.2 IDEAS' own holdings page (same federation, independently counted)
-
-`https://ideas.repec.org/stats.html`, retrieved 2026-09-01 (S2) [WEB]:
-
-| | Journals & series | Items | of which online | JEL coded | with abstracts | with references | with citations |
-|---|---|---|---|---|---|---|---|
-| Working papers | 5,906 | **1,325,878** | 1,121,021 | 572,853 | 1,115,887 | 640,349 | 643,859 |
-| Articles | 4,658 | 3,770,404 | 3,692,447 | 580,423 | 3,085,554 | 1,572,075 | 1,721,335 |
-| Software components | 37 | 6,039 | 6,025 | 964 | 5,927 | 0 | 336 |
-| Books | 657 | 70,609 | 34,438 | 11,950 | 39,507 | 6,697 | 26,110 |
-| Chapters | 360 | 332,227 | 97,814 | 30,433 | 308,419 | 14,915 | 46,741 |
-| **Total** | **11,618** | **5,505,157** | **4,951,745** | 1,196,623 | 4,555,294 | 2,234,036 | 2,438,381 |
-
-Also: **15,803 economics institutions** in EDIRC, **73,978 registered authors** (who have
-authored 2,351,877 indexed items), and **101,367 NEP reports in 106 fields**.
-
-**IDEAS and EconPapers disagree slightly** — 5,505,157 vs 5,489,558 total; 1,325,878 vs
-1,316,031 working papers. Both were retrieved on 2026-09-01. The gap (~0.3%) is mirror lag:
-the two services harvest the same publisher archives on their own schedules. **Recorded, not
-resolved.** It is a useful reminder that in a federation there is no canonical count, only
-snapshots taken by different harvesters.
-
-RePEc's own front page rounds it: "Over 2,400 archives from 106 countries have contributed
-over 5.5 million research items from 4,600 journals and 5,900 working paper series. Over
-74,000 authors have registered in the RePEc Author Service and 75,000 email subscriptions
-are served every week." (S1) [DOC]
-
-### 3.3 Reconciling Wikipedia's ">1,000,000"
-
-Wikipedia gives RePEc ">1,000,000" (S11). **The number is defensible only if you read it as
-working papers specifically**, which is 1,316,031 (S3) or 1,325,878 (S2). As a total it is
-off by a factor of five: the federation indexes **5.49–5.51 million items**.
-
-More importantly, the figure is the wrong *kind* of number. Of that 5.5 million, **3.77
-million are journal articles** — not preprints, not working papers, and mostly not open.
-Only **1,111,325 working papers are downloadable** (S3). Listing RePEc in a table of
-"preprint repositories" alongside arXiv invites the reader to compare 5.5 M against arXiv's
-holdings, which is meaningless: RePEc is an *index*, and most of what it indexes is the
-published literature. The comparable number is the downloadable-working-paper count, and
-even that lives on 2,400 other people's servers.
-
-## 4. Size — EconStor
-
-All figures from EconStor's OAI-PMH interface, `completeListSize` in the `resumptionToken`,
-retrieved **2026-09-01** (S9) [API]:
-
-| Set | Records |
-|---|---|
-| **All records** (`ListIdentifiers`, `oai_dc`) | **320,533** |
-| `doc-type:workingPaper` | **166,147** |
-| `doc-type:article` | 103,777 |
-| `doc-type:report` | 28,252 |
-| `doc-type:conferenceObject` | 12,976 |
-| `doc-type:book` | 3,707 |
-| `doc-type:doctoralThesis` | 675 |
-| `doc-type:preprint` | **661** |
-| `ddc:330` (Economics) | 275,034 |
-| `ddc:000` (Generalities, Science) | 864 |
-| `ddc:600` (Technology / Applied sciences) | **43** |
-| `ddc:004` (Data processing / Computer science) | **36** |
-
-**320,533 against Wikipedia's ">100,000" (S11)** — the bucket is right but three times too
-coarse. Note that **"working paper" (166,147) and "preprint" (661) are different doc-types
-in EconStor's own taxonomy**: in economics the working paper *is* the preprint, and the
-`preprint` set is a rounding error. Wikipedia's description — "A subject based repository
-with a high share of working papers (preprints)" (S11) — is accurate, and the parenthesis
-is doing exactly the right work.
-
-EconStor's OAI interface declares **100 sets** in total (S9) [API], mixing Dewey classes
-(`ddc:*`) with document types (`doc-type:*`).
-
-## 5. Screening, moderation and reliability
-
-### 5.1 There is no moderation, and that is not a defect
-
-Neither RePEc nor EconStor peer-reviews anything, and **in economics this is the norm rather
-than a compromise.** The working paper — an NBER paper, a Fed staff report, a CEPR
-discussion paper, a university department's WP series — is a first-class, citable object
-that circulates for years, sometimes forever, without a journal version. It carries the
-institution's imprimatur, not a reviewer's. A reader who expects arXiv-style moderation, or
-who treats "unreviewed" as "unvetted", has the wrong model of the field.
-
-**What actually gates content:**
-
-- **RePEc:** the *archive* gates, not RePEc. Anyone can create a RePEc archive, but in
-  practice archives are run by institutions — departments, central banks, publishers — that
-  have their own series editors. RePEc checks metadata syntax, not content. **Any
-  reliability signal you get from RePEc comes from the series, not from RePEc.**
-- **MPRA** is the deliberate exception: the Munich Personal RePEc Archive exists precisely
-  so authors "in institutions lacking a participating RePEc archive can submit their papers"
-  (S1) [DOC]. It has no institutional filter. **An MPRA-only paper carries no series
-  warrant; treat MPRA the way you would treat a generalist preprint server.**
-- **EconStor:** ZBW curates which series it hosts; the depositing institution vouches for
-  the content.
-
-### 5.2 The one genuine integrity mechanism — the Plagiarism Committee
-
-RePEc runs a **standing plagiarism committee** with a public register of adjudicated cases
-(S7) [DOC]. Its stated rationale is unusually blunt:
-
-> "Plagiarism is a serious offense of scientific ethics, yet detected plagiarism too often
-> results in consequences that have little bite. Indeed, an offender may be punished by
-> his/her current employer, and then move on to another job without further consequences.
-> Sometimes, even the employer may not even care and in some rare cases sponsor plagiarism.
-> The goal of this page is to highlight cases of plagiarism in Economics. All cases have been
-> evaluated by a committee. Each case provides a full description, so that the reader can
-> judge by him/herself whether plagiarism occurred. The response of the accused plagiariser
-> is also published." (S7)
-
-A named, public offender list with right of reply, run by volunteers, is a stronger
-integrity mechanism than most preprint servers in this collection have. It is worth knowing
-about even if you never read an economics paper. (I did not enumerate the case list; **the
-number of listed offenders is [NOT-VERIFIED]**.)
-
-### 5.3 How to sanity-check an item
-
-1. **Identify the series, not the repository.** `RePEc:nbr:nberwo:…` (NBER Working Papers)
-   and `RePEc:pra:mprapa:…` (MPRA) are not the same kind of object. The RePEc handle encodes
-   the archive.
-2. **Check whether it was ever published.** IDEAS and EconPapers both link working papers to
-   their published versions where CitEc or the author has established the link. RePEc's own
-   documentation lists "tracking how working papers get published" as a standard use of its
-   data (S1) [DOC].
-3. **Check the author's RAS profile.** 73,978 authors are registered (S2); an unregistered
-   author with a single MPRA deposit is a different proposition from a registered one with a
-   department series.
-4. **Search the plagiarism register** (S7).
-5. **For EconStor, check `dc:rights`.** Licences vary per record (§7).
-
-## 6. Relevance to computing and electronics — limited but non-zero
-
-Be honest: **this is thin, and the numbers are unforgiving.**
-
-- EconStor's whole *Data processing / Computer science* class is **36 records**; *Technology
-  (Applied sciences)* is **43** (S9) [API]. To make the point concretely, those 36 records
-  include *"Die geschichtliche Entwicklung des V-Modells"* (the historical development of
-  the V-Model), *"Learning to play Sokoban from videos"*, *"ChatGPT — A critical view"*,
-  *"Machine learning in demand planning: Cross-industry overview"* and *"The BabelNEG System
-  — A Protocol-generic Infrastructure for Electronic SLA Negotiations in the Internet of
-  Services"* (S9) [API]. Genuinely computing, genuinely obscure, and thirty-six of them.
-- RePEc's **6,039 software components in 37 series** (S2, S3) are almost entirely **Stata,
-  MATLAB, Gauss and R code for econometrics** — the largest such archive is maintained by
-  Kit Baum, who "proposed the inclusion of software components in RePEc" and "often
-  contributes Stata components for time series econometrics" (S5) [DOC]. This is a real,
-  early, and under-appreciated piece of research-software infrastructure: **RePEc has been
-  indexing citable research software since 1997-09-08** (S6) [DOC], twenty years before
-  Zenodo's GitHub integration made it fashionable. It has 0 items with references and only
-  336 with citations (S2) — the citation graph never reached the software.
-
-**Where the overlap with your world is real:**
-
-The interesting economics for a systems person is classified by **JEL code**, and IDEAS lets
-you browse by it at `https://ideas.repec.org/j/<CODE>.html`. The relevant codes, all
-confirmed live 2026-09-01 (S8) [WEB]:
-
-| JEL code | Title | Why you might care |
-|---|---|---|
-| **L86** | Information and Internet Services; **Computer Software** | economics of software, platforms, open source |
-| **L63** | **Microelectronics; Computers; Communications Equipment** | semiconductor industry economics, Moore's-law productivity studies |
-| **D82** | Asymmetric and Private Information; **Mechanism Design** | auction and market design — the direct overlap with `cs.GT` |
-| **C63** | **Computational Techniques** | numerical methods, simulation |
-| **C45** | **Neural Networks and Related Topics** | ML in econometrics |
-| **C81** | Methodology for Collecting, Estimating, and Organizing Microeconomic Data | data infrastructure |
-| **O33** | Technological Change: Choices and Consequences; Diffusion Processes | technology adoption |
-
-**Per-code item counts: [NOT-VERIFIED].** The IDEAS JEL browse pages paginate at 200 items
-and expose no total; I did not enumerate them.
-
-**The arXiv overlap.** arXiv's `econ.EM` (econometrics), `econ.TH` (theoretical economics)
-and `econ.GN` (general economics) exist since 2017 and overlap RePEc's `C` and `D` codes
-directly; `cs.GT` (computer science and game theory) overlaps `D82` almost exactly, with
-mechanism-design and auction papers routinely appearing in both literatures. **If a
-mechanism-design or market-design result matters to you, it is more likely to be on arXiv
-`cs.GT` than reachable through RePEc**, and RePEc will index the *published* version
-afterwards. See [arxiv.md](arxiv.md).
-
-**Blunt summary: a hardware or software engineer will essentially never need RePEc or
-EconStor.** The exceptions are narrow and identifiable: you are reading about auction/market
-design and want the economics-side literature; you are chasing semiconductor-industry or
-open-source economics (L63, L86); or you want econometric software with a citable handle.
-Everything else in these systems is somebody else's field.
-
-## 7. Access, APIs and bulk retrieval
-
-### 7.1 RePEc — the standard method, and the discouraged one
-
-RePEc's own guidance is explicit and worth quoting because it is the opposite of what most
-repositories say (S4, *"RePEc: getting the metadata"*) [DOC]:
-
-> "**We want to discourage you strongly to scrape the data from the websites.** This puts
-> unnecessary strain on our servers, and we have repeatedly noticed misconfigured scraping
-> scripts running amok. And you [are] very unlikely to get complete data that way."
-
-**The sanctioned route** is to harvest the publisher archives directly: "Each publisher holds
-its RePEc metadata on its web or anonymous ftp server. The addresses are listed in their
-archive templates. All those templates are listed at the **RePEc:all** archive. This is the
-standard way to acquire the core RePEc data." Tooling: **`remi`** to acquire, **`ReDIF-perl`**
-to parse (S4) [DOC].
-
-**A consolidated copy** is also offered, with a caveat — "One can also access all the data in
-one place. There is, however, no guarantee that this is accurate or up-to-date. Only the
-publisher archives can guarantee that" — in these formats (S4) [DOC]:
-
-- **ReDIF** (native)
-- **AMF** (Academic Metadata Format)
-- **OAI-PMH** — described by RePEc itself as "**sometimes flaky**"
-- **rsync**
-
-**Person data** is available through the `RePEc:per` archive. "Email addresses are released
-under no circumstances." (S4) [DOC]
-
-**The API is application-gated, not open** (S10) [DOC]: "the API is currently not openly
-available, as we have yet to understand the demand for it and how much it could be taxing our
-servers." To get access you must email Christian Zimmermann with your identity, purpose,
-required data, why the standard method is not usable, source IP, project end date, and
-expected call frequency. Approved users get a time-limited access code; "We reserve the right
-to throttle the API if needed." Metadata is JSON. **There is no search function in the API.**
-Example functions: `getref`, `getrecentpapers`, `getpubsfromwpseries`, `getauthorshortid`.
-CitEc has its own separate API.
-
-**Reachability probes, 2026-09-01** (S8) [WEB] — all with a browser User-Agent; no UA
-fallback was needed for any RePEc host:
-
-| URL | Result |
-|---|---|
-| `http://repec.org/` | 200, 14,991 B |
-| `https://ideas.repec.org/` | 200, 29,872 B |
-| `https://econpapers.repec.org/` | 200, 6,790 B |
-| `http://nep.repec.org/` | 200 → `https://nep.repec.org/`, 284,295 B |
-| `https://authors.repec.org/` | 200, 5,247 B |
-| `http://logec.repec.org/` | 200 → https, 6,337 B |
-| `https://edirc.repec.org/` | 200, 13,672 B |
-| `https://ideas.repec.org/stats.html` | 200, 19,453 B |
-| **Negative control** `https://ideas.repec.org/j/notarealcode999.html` | **404**, 17,657 B |
-| **Negative control** `http://repec.org/aboutrepec.html` (invented) | **404**, 408 B |
-| `http://repec.org/docs/` (directory listing) | **403** — indexing disabled, as expected |
-
-Both negative controls return genuine 404s. **RePEc's front ends 404 honestly**, unlike
-[OSF](osf-preprints.md) (200 + SPA shell) and [SSRN](ssrn.md) (200 + "Page Cannot be Found").
-That is worth stating: it makes RePEc scriptable in a way the others are not — which sits
-oddly beside its request that you not script it.
-
-### 7.2 EconStor — open OAI-PMH behind a closed web front end
-
-This is the most interesting access finding in the record.
-
-**The web front end is behind a proof-of-work anti-scraper gate.** `https://www.econstor.eu/`
-returns HTTP 200 with a 4,807-byte challenge page titled **"Making sure you're not a bot!"**,
-served by **[Anubis](https://github.com/TecharoHQ/anubis)**. The page states EconStor's
-reasoning verbatim (S9) [WEB]:
-
-> "You are seeing this because EconStor has set up Anubis to protect the server against the
-> scourge of AI companies aggressively scraping websites. This can and does cause downtime
-> for the websites, which makes their resources inaccessible for everyone. Anubis is a
-> compromise. Anubis uses a Proof-of-Work scheme in the vein of Hashcash … at individual
-> scales the additional load is ignorable, but at mass scraper levels it adds up and makes
-> scraping much more expensive. … This is required because **AI companies have changed the
-> social contract around how website hosting works.**"
-
-Running Anubis version `v1.25.0-38-g0134fc2-dirty`, hosted by ZBW. `https://www.econstor.eu/`
-and `https://www.econstor.eu/server/…` both hit it. **A browser User-Agent does not get past
-it** — it is a JavaScript proof-of-work challenge, not UA filtering, so the
-[AGENTS.md](../../AGENTS.md) user-agent ladder is the wrong tool and rotating agents will
-waste your time.
-
-**And yet the OAI-PMH endpoint is completely open.** `https://www.econstor.eu/oai/request`
-answered every verb immediately, with no challenge, no UA requirement and no rate limiting,
-across ~15 sequential calls (S9) [API]:
-
-```
-verb=Identify        → repositoryName EconStor · baseURL https://www.econstor.eu/oai/request
-                       protocolVersion 2.0 · adminEmail w.riese@zbw.eu
-                       earliestDatestamp 2009-01-28T14:13:20Z · deletedRecord transient
-                       granularity YYYY-MM-DDThh:mm:ssZ
-                       repositoryIdentifier econstor.eu · sample oai:econstor.eu:10419/1234
-verb=ListSets        → 100 sets (ddc:* and doc-type:*)
-verb=ListIdentifiers → completeListSize in the resumptionToken (§4)
-verb=ListRecords     → oai_dc records with dc:rights
-```
-
-**That combination is the finding.** ZBW's position is coherent and worth understanding: the
-*metadata* is deliberately, unconditionally open through the standard protocol (and is CC0,
-§8); the *website* is defended because bulk HTML scraping is expensive and unnecessary when a
-harvesting protocol exists. **If you want EconStor data, use OAI-PMH. That is what it is
-for, and using it is the polite path, not a workaround.**
-
-**Negative control** (S9) [API]: `verb=ListIdentifiers&set=notarealset:xyzzy` returns
-**HTTP 200** with `<error code="noRecordsMatch">`. A 200 from an OAI endpoint means nothing;
-you must parse for `<error>`. Note also that small sets (`ddc:004` at 36 records, `ddc:600`
-at 43) return **no `resumptionToken` and therefore no `completeListSize`** — you must count
-`<identifier>` elements yourself. A missing `completeListSize` is not an error and not a
-zero.
-
-## 8. Licensing and reuse
-
-**RePEc metadata — effectively public domain, with a non-commercial expectation.** The
-official policy, dated 12 October 2017 (S12) [DOC]:
-
-> "The RePEc metadata have been contributed by individual RePEc archives for the benefit of
-> the research community. **You are free to do whatever you want with metadata from RePEc
-> archives** provided that you do not contravene any copyright or license in any of the
-> participating archives. You are encouraged to attribute RePEc as the source of the
-> metadata."
-
-RePEc's own front page likewise states "The RePEc bibliographic data is in the public
-domain" (S1) [DOC]. **But** the data-acquisition page adds a condition the licence page does
-not: "the archives participating in RePEc as well as the people volunteering with RePEc do so
-with the understanding that the collected data will be put to good use. **This does not
-include commercial use.** If you want to use RePEc data for commercial use, please first
-contact RePEc. Typically, we would require substantial contributions of data to RePEc for a
-commercial use to have a chance of being tolerated." (S4) [DOC] Two RePEc documents, two
-different positions. **Recorded, not resolved** — if your use is commercial, ask.
-
-**Full text on RePEc: whatever the publisher says.** RePEc has no licence to grant; the PDF
-is on the publisher's server under the publisher's terms. Of 1,325,878 working papers,
-1,121,021 are online at all (S2).
-
-**EconStor metadata: CC0 1.0.** The OAI `Identify` response carries an explicit
-`<dc:rights>` description: "Creative Commons License CC0 1.0
-(https://creativecommons.org/publicdomain/zero/1.0/)" (S9) [API]. Unambiguous, machine-
-readable, and about as good as repository metadata licensing gets.
-
-**EconStor full text: mixed, declared per record.** `dc:rights` values observed in a single
-`ListRecords` page (S9) [API]: `https://creativecommons.org/licenses/by/4.0/`,
-`.../by/4.0/de/legalcode`, `.../by-sa/4.0/`, `http://creativecommons.org/licenses/by-nc-nd/3.0/de/`,
-and — crucially — `https://www.econstor.eu/dspace/Nutzungsbedingungen`, EconStor's own
-non-CC terms of use. **Check `dc:rights` on the individual record before reusing a PDF.** A
-CC0 metadata licence does not make the documents CC0.
-
-## 9. Caveats and controversies
-
-1. **RePEc is not a repository and does not host papers.** This is the headline. Every
-   "size" statement about RePEc is a statement about metadata records pointing at other
-   people's servers.
-2. **Wikipedia's ">1,000,000"** is right only for working papers and wrong for the
-   federation, which indexes 5.49–5.51 M items — of which 3.77 M are journal articles, not
-   preprints (§3.3).
-3. **Wikipedia's "Federal Reserve Bank of St. Louis"** as operator is a half-truth: the Fed
-   employs the person who runs IDEAS. RePEc has no operator (§1.2).
-4. **IDEAS and EconPapers give different totals on the same day** (§3.2). In a federation
-   there is no canonical count.
-5. **Link rot is structural.** RePEc points at publishers' own servers. A departmental
-   reorganisation breaks links RePEc cannot repair. 204,857 working papers are indexed but
-   **not** online (1,325,878 minus 1,121,021, S2) [INF].
-6. **MPRA is the soft underbelly.** It is the one RePEc archive with no institutional filter
-   (§5.1). Papers that exist only in MPRA deserve the scepticism you would apply to a
-   generalist preprint server.
-7. **RePEc asks you not to scrape it** and gates its API behind a written application (§7.1)
-   — unusual among the repositories in this collection, and a direct consequence of having
-   no central budget.
-8. **EconStor's website is behind Anubis proof-of-work** and its OAI-PMH is wide open (§7.2).
-   Anyone probing EconStor with HTTP tooling will conclude it is down. It is not.
-9. **RePEc's own OAI-PMH is self-described as "sometimes flaky"** (S4). Prefer ReDIF or
-   rsync for RePEc; prefer OAI-PMH for EconStor.
-10. **`doc-type:preprint` on EconStor returns 661 records** and is a red herring; the working
-    papers (166,147) are the preprints (§4).
-
-## 10. Sources
-
-- **S1** — RePEc home, `http://repec.org/`. Retrieved 2026-09-01, HTTP 200, 14,991 bytes.
-  Supports: the "crowd-sourced effort / no central expenses" description, the operating
-  model ("Every publisher or provider puts text files describing their publications on their
-  own server"), the full RePEc service list, the "Over 2,400 archives from 106 countries …
-  over 5.5 million research items" summary, the "bibliographic data is in the public domain"
-  statement, the list of additional services using RePEc (including EconStor), and the
-  Guildford Protocol / ReDIF references.
-- **S2** — IDEAS holdings statistics, `https://ideas.repec.org/stats.html`, and the IDEAS
-  home page `https://ideas.repec.org/`. Retrieved 2026-09-01, HTTP 200. Supports: the §3.2
-  holdings table (5,505,157 items, 11,618 serials, 4,951,745 online, JEL/abstract/reference/
-  citation coverage), 15,803 institutions, 73,978 registered authors, 101,367 NEP reports in
-  106 fields, and IDEAS' "over 5,400,000 items … over 2,000 participating archives" blurb.
-- **S3** — EconPapers home, `https://econpapers.repec.org/`. Retrieved 2026-09-01, HTTP 200,
-  6,790 bytes; page footer "Page updated 2026-09-02". Supports: the §3.1 breakdown
-  (1,316,031 working papers in 5,915 series; 3,759,295 articles; 6,039 software items;
-  69,352 books; 338,841 chapters; 5,489,558 total) and EconPapers' hosting by the School of
-  Business at Örebro University.
-- **S4** — *"RePEc: getting the metadata"*, `https://ideas.repec.org/getdata.html`.
-  Retrieved 2026-09-01, HTTP 200, 23,050 bytes. Supports: the anti-scraping request, the
-  `RePEc:all` archive and `remi`/`ReDIF-perl` tooling, the ReDIF/AMF/OAI-PMH/rsync bulk
-  formats, the "OAI/PMH (sometimes flaky)" characterisation, the `RePEc:per` person archive,
-  the email-address policy, and the non-commercial-use condition.
-- **S5** — *"The RePEc team"*, `https://ideas.repec.org/team.html`. Retrieved 2026-09-01,
-  HTTP 200, 26,356 bytes. Supports: Christian Zimmermann as Assistant Vice President at the
-  Federal Reserve Bank of St. Louis and head of IDEAS/EDIRC/Genealogy/Biblio; Kit Baum as
-  proprietor of repec.org and originator of RePEc software components; Sune Karlsson running
-  EconPapers, LogEc and SWoPEc; Thomas Krichel as founder and maintainer of NEP and the
-  Author Service; José Manuel Barrueco Cruz and CitEc; MPRA at the University of Munich.
-- **S6** — *"RePEc history"*, `https://ideas.repec.org/history.html`. Retrieved 2026-09-01,
-  HTTP 200, 25,671 bytes. Supports: NetEc on gopher, February 1993, by Thomas Krichel at the
-  University of Surrey; NetEc's move to the web in 1994; the Guildford meeting of
-  1997-05-12 and the named participants; LSE FMG as first archive (1997-05-27); IDEAS launch
-  September 1997 with 40,000 items; software components added 1997-09-08; NEP's first
-  mailing 1998-05-04; EDIRC's start 1996-03-07 with 350 entries.
-- **S7** — RePEc plagiarism page, `https://plagiarism.repec.org/`. Retrieved 2026-09-01,
-  HTTP 200, 2,503 bytes. Supports: the existence, rationale and procedure of the RePEc
-  Plagiarism Committee and its public offenders register with right of reply.
-- **S8** — Reachability and negative-control probes across RePEc hosts, plus IDEAS JEL browse
-  pages `https://ideas.repec.org/j/{L86,L63,D82,C63,C45,C81,O33}.html`. All 2026-09-01.
-  Supports §6's JEL code titles and §7.1's probe table including the two 404 negative
-  controls.
-- **S9** — EconStor. OAI-PMH at `https://www.econstor.eu/oai/request` with verbs `Identify`,
-  `ListSets`, `ListIdentifiers` (whole repository and per set), `ListRecords`; plus the web
-  front page `https://www.econstor.eu/` and `https://www.econstor.eu/server/oai/request`.
-  All retrieved 2026-09-01/02 (the endpoint's own `responseDate` was `2026-09-02T04:56:28Z`,
-  UTC). Supports: §4's entire size table, the 2009-01-28 earliest datestamp, the 100 sets,
-  the `10419/…` handle namespace, the CC0 metadata licence, the per-record `dc:rights`
-  variety, the sample `ddc:004` titles, the `noRecordsMatch` negative control, and the Anubis
-  proof-of-work block page with its verbatim justification.
-- **S10** — *"RePEc API"*, `https://ideas.repec.org/api.html`. Retrieved 2026-09-01, HTTP
-  200, 21,999 bytes. Supports: the API's application-gated status, the information required
-  of applicants, the JSON delivery, the absence of a search function, the named example
-  functions, and the throttling reservation.
-- **S11** — Wikipedia, *List of preprint repositories*, wikitext via
-  `https://en.wikipedia.org/w/index.php?title=List_of_preprint_repositories&action=raw`.
-  Retrieved 2026-09-01. Supports: the RePEc row (Economics, ">1,000,000", 1997, Federal
-  Reserve Bank of St. Louis) and the EconStor row ("Economics and Business Studies", "A
-  subject based repository with a high share of working papers (preprints)", ">100,000",
-  2009, ZBW).
-- **S12** — *"Use of RePEc data"*, `http://repec.org/docs/RePEcDataUse.html`, dated
-  12 October 2017. Retrieved 2026-09-01, HTTP 200, 1,067 bytes. Supports: the metadata reuse
-  policy in full.
diff --git a/research/preprint-repositories/research-square.md b/research/preprint-repositories/research-square.md
deleted file mode 100644
index 867c93a..0000000
--- a/research/preprint-repositories/research-square.md
+++ /dev/null
@@ -1,374 +0,0 @@
-# Research Square — preprint repository record
-
-- **URL:** https://www.researchsquare.com/
-- **Operator:** Research Square (a division of Research Square Company). Research Square Company was
-  **fully acquired by Springer Nature**: *The Bookseller*, 1 December 2022 — *"After a period of
-  partial ownership Springer Nature has increased its investment in Research Square Company (RSC) to
-  take full ownership."* (S12). Research Square Company also owns **American Journal Experts (AJE)**,
-  a paid author-services business (S6, S13). ISSN 2693-5015 (online) (S1).
-- **Discipline scope:** advertised as multidisciplinary — *"physical, biomedical, and social
-  sciences"* (S4) — in practice heavily biomedical/life-sciences, tracking the Springer Nature and
-  BMC journal portfolio that feeds it.
-- **Launched:** 2018 for the preprint platform (Springer Nature dates *In Review* to October 2018,
-  S11; OpenAlex records first works in 2018, S9). Wikipedia's article says the *platform* was
-  established 2013 and its repository-list row says 2018 — see §3. · **Status:** active
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-Research Square is the largest preprint server in the world by deposit count, and it got there by a
-mechanism no other server uses at scale: **it is plumbed directly into a major publisher's
-manuscript-tracking systems.** When you submit to one of ~1,500 participating Springer Nature/BMC
-journals, the submission form offers an opt-in called **In Review**. Tick it (with all co-authors'
-agreement) and, once the journal's own quality checks pass, your manuscript is converted to HTML,
-given a DOI, licensed CC BY 4.0, and posted publicly on Research Square with a live, updating
-peer-review status timeline — *while it is still under review at the journal*. (S3, S11)
-
-The rest of the site is a conventional direct-submission preprint server: upload a PDF/Word file,
-staff screen it, it posts within ~72 hours (S4).
-
-Around the preprint platform sits a commercial author-services business — AJE English editing,
-translation, presubmission review, Rubriq independent peer review, video abstracts, research
-promotion — all reachable from the preprint site's own navigation bar (S1, S13). That adjacency is
-the source of the conflict-of-interest question in §10.
-
-## 2. Scope and subject taxonomy
-
-There is no formal, code-based taxonomy comparable to arXiv's. The home page advertises 15 "Featured
-Subjects", all biomedical/behavioural: Anesthesiology & Pain Medicine, Cancer Biology, Computational
-Biology, Dentistry, Developmental Biology, Epigenetics & Genomics, General Microbiology, Infectious
-Diseases, Internal Medicine, Neurology, Oncology, Pediatrics, Physiology, Psychology, Structural
-Biology (S1). Computer science and electronics appear only via the participating-journal list, not
-as a promoted browse facet.
-
-**Accepted content types** are explicitly restricted (S4, §1.2): Research Article, Systematic
-Review, Method Article (incl. protocols), Short Report, Case Report, Data Note. And, importantly:
-*"Only systematic reviews and research articles with complete methods and results sections will be
-considered for posting. Theories, commentaries, and non-systematic reviews are not eligible for
-preprinting."* Negative results are explicitly welcome.
-
-**Where the CS/EE content comes in.** The *In Review* participating-journal list contains **1,503
-journals and platforms** (extracted 2026-09-01, S5). Of those, ~134 have computing/electronics-facing
-titles, including titles a systems or hardware engineer would recognise:
-
-*Algorithmica* · *Distributed Computing* · *Acta Informatica* · *Cryptography and Communications* ·
-*International Journal of Information Security* · *EURASIP Journal on Information Security* ·
-*EURASIP Journal on Advances in Signal Processing* · *EURASIP Journal on Wireless Communications and
-Networking* · *Design Automation for Embedded Systems* · *Analog Integrated Circuits and Signal
-Processing* · *Automated Software Engineering* · *Innovations in Systems and Software Engineering* ·
-*Cluster Computing* · *Computing and Software for Big Science* · *Computer Supported Cooperative Work
-(CSCW)* · *Genetic Programming and Evolvable Machines* · *Information Retrieval Journal* ·
-*GeoInformatica* · *Applied Network Science* · *EPJ Data Science* · *Autonomous Robots* ·
-*International Journal of Machine Learning and Cybernetics* · *International Journal on Document
-Analysis and Recognition (IJDAR)* · *Discover Computing* · *Discover Electronics* · *Discover
-Networks* · *Discover Robotics* · *International Cybersecurity Law Review* (S5).
-
-So: if a paper was submitted to *Algorithmica* or *Distributed Computing* and the authors opted in,
-its preprint is on Research Square. That is a genuinely useful early-access channel for
-theory/systems work.
-
-## 3. Size and growth
-
-| Measure | Value | Source |
-|---|---|---|
-| Preprints in the platform's own browse index | **468,390** | `/browse` `__NEXT_DATA__` `result.total`, 2026-09-01 [WEB] (S2) |
-| Crossref DOIs under prefix 10.21203 | **514,618** (512,417 `posted-content` + 2,201 `component`) | Crossref API [API] (S8) |
-| Works in OpenAlex source S4306525896 | 484,792 (281,027 citations) | OpenAlex API [API] (S9) |
-| Records in Europe PMC (`PUBLISHER:"Research Square"`) | **470,988** | Europe PMC API [API] (S10) |
-| Participating *In Review* journals/platforms | **1,503** | `/journals`, 2026-09-01 [WEB] (S5) |
-| Manuscripts supported by AJE (parent company) | "over 775,000 … from researchers in 192 countries" | `/about` [DOC] (S6) |
-
-**Conflicts, recorded.** Crossref's 514,618 exceeds the site's own 468,390 by ~46k; the most likely
-explanation is version DOIs and `component` records, since Research Square mints a DOI per version
-(`10.21203/rs.3.rs-XXXXXXXX/v1`) [INF]. Europe PMC's 470,988 is within 0.6% of the site counter,
-which is a good independent corroboration. Wikipedia's *List of preprint repositories* row still says
-">100,000" (access date 2023-05-22) and the article body says ">223,000 as of May 2023" (S14) — both
-badly stale by a factor of 2–4.
-
-**Launch-year conflict.** Wikipedia's article says the platform "was established in 2013"; its own
-repository-list row says 2018 (S14). Springer Nature dates *In Review* to October 2018 (S11).
-OpenAlex shows 147 works in 2018, then 11,360 in 2019 (S9). The 2013 date corresponds to Research
-Square Company (the AJE parent), not the preprint platform [INF].
-
-Growth by year (OpenAlex, S9): 2018 147 · 2019 11,360 · 2020 49,657 · 2021 74,421 · 2022 75,635 ·
-2023 82,330 · 2024 73,144 · 2025 57,101 · 2026 (part year) 60,997. Peak deposit year was 2023;
-volume has since declined ~30%.
-
-Published versions **stay**, permanently: *"Once preprints receive a DOI, we cannot remove these
-without cause"* (S3).
-
-## 4. Screening and moderation — what gets in
-
-Research Square screens; it does not review. From the Editorial Policies, §6 Screening (S4), verbatim
-substance:
-
-> *"Research Square does not conduct peer review on preprints prior to posting. Content submitted to
-> Research Square is checked for appropriate ethics and consent statements; disclosure of competing
-> interests; absence of patient identifiers; and inappropriate, alarming, highly controversial, or
-> pseudoscientific claims. Articles with strong conclusions, especially in the absence of fully
-> accessible data, may also be screened out. A submission that has already been published at a
-> journal will not be posted as a preprint. Additionally, submissions with missing figures, reference
-> lists, or other critical components may be rejected. … Checks at Research Square are carried out by
-> our trained editorial staff."*
-
-Two further points from the same policy:
-
-- **In Review submissions carry the journal's checks *plus* the Research Square checks.** *"Preprints
-  that are posted to the platform as part of the Springer Nature In Review service indicate the set of
-  checks that have been carried out by the journal. They will include any checks the journal performs
-  in addition to the above-mentioned Research Square checks."* (S4 §6)
-- **Screening rejections cannot be appealed.** *"If we make a decision not to post a manuscript … due
-  to concerns identified at the screening step … that decision cannot be appealed."* (S4 §11)
-
-Data availability is a live screening criterion for medical work: *"We may decide not to post certain
-preprints on the basis of unavailable or inaccessible data."* (S4 §4)
-
-**Time to post:** direct submissions typically within 72 business hours (S4 §7). In Review preprints
-post within **72 hours** of passing the journal's checks, or **48 hours** if the author elects to post
-before review begins (journal branding then added later) (S3).
-
-**Withdrawal and removal** (S4 §8, §9): withdrawal posts a *new version* explaining the withdrawal
-while previous versions remain; removal is rare and replaces the text with a removal notice, keeping
-title and authors "wherever possible". Research Square may itself initiate a withdrawal on research
-conduct/ethics grounds or if a downstream journal version is retracted, and may attach **editorial
-notes** to preprints at its discretion.
-
-## 5. Reliability — what you can and cannot trust
-
-### What the "In Review" badge actually tells you
-
-This is the crux, and it is more informative than any other preprint badge in existence — *and also
-more easily over-read*.
-
-**It does tell you:**
-
-1. The manuscript **was submitted to a specific named journal**, and that journal is identified on the
-   preprint page.
-2. It **passed that journal's submission/quality checks** — not peer review, the pre-review triage.
-3. The status label is one of **Under Review**, **Under Revision**, or **Published** (S3).
-4. If the journal shares the data, a **timestamped peer-review event timeline** is displayed, fed by a
-   direct integration with the journal's manuscript-tracking system (S3).
-
-A live example retrieved 2026-09-01 — *CMTD: Cascaded Multi-Token Disambiguation Model for Lip
-Reading*, `10.21203/rs.3.rs-10510743/v1`, journal *Multimedia Systems*, status **Under Review** (S7):
-
-```
-First submitted to journal          28 Jul 2026
-Submission checks completed         31 Jul 2026
-Editor assigned by journal          21 Aug 2026
-Reviewers invited by journal        25 Aug 2026
-Reviewers agreed at journal         26 Aug 2026
-Reviewers agreed at journal         27 Aug 2026
-Reviews received at journal         29 Aug 2026
-Reviews received at journal         30 Aug 2026
-```
-
-That is a genuinely valuable transparency artefact: you can see that two referees have reported.
-
-**It does NOT tell you:**
-
-1. **Anything about the reviews' content or verdict.** "Reviews received" ≠ "reviews positive."
-2. **That the paper will be accepted.** The page carries the banner *"This is a preprint; it has not
-   been peer reviewed by a journal."* (S7)
-3. **That the journal is prestigious.** The 1,503-title list spans *Algorithmica* to
-   *Zoomorphology*, including a large number of low-selectivity *Discover* and *BMC* titles (S5).
-4. **That a timeline exists at all.** *"Journals can participate in In Review with varying levels of
-   transparency … some journals opt to not share those details publicly on our preprints."* (S3)
-
-### What happens on rejection — the important asymmetry
-
-From the operator's own In Review page (S3), verbatim:
-
-> *"If the submission is rejected by the journal, the preprint will remain on Research Square, with
-> the journal branding and peer review timeline removed."*
-
-Springer Nature states the same from the other side: the preprint *"will permanently remain publicly
-available, regardless of whether the journal you submitted it to accepts it or not."* (S11)
-
-**Consequence for a reader:** a Research Square preprint with **no** journal branding and **no**
-timeline is ambiguous. It is either (a) a direct submission that never went through In Review, or
-(b) an In Review manuscript that was **rejected** and had its branding stripped. **The page does not
-distinguish these two cases.** This is the single most important reliability fact about the platform,
-and it cuts against the naive reading that "no badge = ordinary preprint". You cannot tell a fresh
-preprint from a rejected one.
-
-### Other reliability observations
-
-- **Post-hoc versions after rejection are gated.** New-version posting via the journal route is
-  *"only available for manuscripts that are actively under consideration at an open access In Review
-  journal"*; rejected authors must post revisions through their own account (S3).
-- **Indexing is real:** Crossref, Europe PMC, Google Scholar, Researcher, Meta; PubMed Central
-  indexes only a *"limited subset"* (S4 §10). Europe PMC's 470,988 records confirm the depth (S10).
-- **No independent conversion-rate measurement found.** Research Square does not publish a
-  preprint-to-publication rate, and I found no scientometric study measuring one specifically for
-  this platform [NOT-VERIFIED]. Kirkham et al. (BMJ Open 2020) surveyed platform characteristics
-  including Research Square but is now five years stale on size and policy (S15).
-
-### How to sanity-check an individual paper from here
-
-1. Read the **status** field and look for journal branding. No branding = unknown provenance (above).
-2. If a timeline exists, read the *last* event, not the first.
-3. Check whether a `nonDraftVersions[].status == "published"` version exists and follow it.
-4. Check the DOI at Crossref; look for a `is-preprint-of` relation to a journal DOI.
-5. Remember the content-type gate: theories and commentaries are *not* accepted (S4 §1.2), so a
-   speculative essay here is anomalous.
-
-## 6. What you actually find there — examples
-
-Retrieved from `/browse` on 2026-09-01 (S2, S7):
-
-| Title | URL | Journal / status |
-|---|---|---|
-| CMTD: Cascaded Multi-Token Disambiguation Model for Lip Reading | `/article/rs-10510743/v1` | *Multimedia Systems* · Under Review |
-| Corrective Retrieval-Augmented Generation Adaptation in Closed Domains for Development… | `/article/rs-10574280/v1` | *Discover Artificial Intelligence* · Under Review |
-| Auditing longitudinal data across institutional regimes: a graph-based compatibility protocol… | `/article/rs-10455680/v1` | Research Square (direct) · Posted |
-| Inferential Analysis and Predictive Modeling of Wages in Brazil… | `/article/rs-10530787/v1` | Research Square (direct) · Posted |
-
-DOI form is `10.21203/rs.3.rs-<id>/v<n>`, licence CC BY 4.0 (S7).
-
-**Honest quality read.** The In Review-branded CS items are exactly what you would expect from the
-mid-tier Springer computing portfolio: competent, incremental, benchmark-driven papers. The
-unbranded direct submissions are a mixed bag and include material that reads as ambiguous in
-provenance. The platform's centre of mass is biomedical, not computing.
-
-## 7. Landmark papers (software · distributed systems · databases · electronics · security)
-
-Research Square hosts no landmark work in these areas. It has existed only since 2018, its CS/EE
-share is a small slice of a biomedical-dominated corpus, and the CS communities that would produce
-landmark preprints use arXiv and IACR ePrint. No table.
-
-## 8. Access, APIs and bulk retrieval
-
-- **A JSON API exists but is gated.** The site's own API Access page (S16) states: *"We also provide
-  a JSON API of the content on our platform with additional metadata if the Crossref or Europe PMC
-  APIs do not satisfy your needs. Please fill out the below form to be granted an access token that
-  will allow you to bypass our rate-limits."* There is no open, documented endpoint; access is by
-  request form only.
-- **The operator explicitly recommends Crossref or Europe PMC for bulk work.** *"Our preprints are
-  also available at Europe PMC and Crossref under DOI prefix 10.21203. Researchers looking to analyze
-  our preprints would be best served using one of those sources."* (S16) That is unusually helpful
-  guidance and you should take it: prefix `10.21203` at Crossref (514,618 records) and
-  `PUBLISHER:"Research Square"` at Europe PMC (470,988 records) (S8, S10).
-- **No OAI-PMH endpoint found.** `/api`, `/api-access` return 404 (S17).
-- **RSS:** `https://www.researchsquare.com/rss.xml` — HTTP 200, valid RSS 2.0 (S18).
-- **Sitemap:** `https://www.researchsquare.com/sitemap.xml` — HTTP 200, 5,136 bytes (S17).
-- **SSR payload:** `<script id="__NEXT_DATA__">` on `/browse` and `/article/...` carries structured
-  metadata (total counts, licence, status, version list). Undocumented; may change [INF].
-- **robots.txt** is Cloudflare-managed with content signals: `search=yes, ai-train=no, use=reference`,
-  and explicit `Disallow: /` for Amazonbot, Applebot-Extended, Bytespider and others (S19). **A
-  general-purpose crawl for AI training is expressly refused by the operator.**
-- **No UA gating observed.** Default `curl` UA returned HTTP 200 on all pages tested (S17).
-
-### Negative controls (2026-09-01) (S20)
-
-| Probe | Result | Interpretation |
-|---|---|---|
-| `/article/rs-99999999/v1` | **HTTP 200**, 16,824 bytes | Soft 404 — non-existent id renders a stub page. |
-| `/article/rs-10510743/v9` (real id, absent version) | **HTTP 200**, 16,824 bytes | Same stub. Byte-identical size to the bogus id, which is the tell. |
-| `/browse?q=FPGA` , `/browse?subject=computer-science` | HTTP 200, `result.total` = **468,390** in every case | **Query parameters are ignored server-side.** Filtering is client-side only; the SSR total is always the global count. Do not scrape faceted counts from this site. |
-| `/in-review`, `/editorial-policies`, `/help` | HTTP 404 (real, 5,028 B) | Correct 404s exist; the canonical paths are `/researchers/in-review` and `/legal/editorial`. |
-
-## 9. Licensing and reuse
-
-- **CC BY 4.0, mandatory, no author choice.** *"All preprints on the platform are published under a
-  CC-BY 4.0 license."* (S4 §14). In Review requires all co-authors to agree to CC BY before posting
-  (S3).
-- Wikipedia flags a real downstream trap: if the manuscript was previously posted elsewhere under a
-  more restrictive licence (e.g. CC BY-SA), re-posting it here under CC BY would violate the original
-  licence (S14) — the burden is on the author.
-- **Preservation:** *"Preprints are held in an archive run by Portico, who will post the full Research
-  Square content repository in the event of the site ceasing to exist."* (S4 §13)
-- Text/data mining is permitted by licence; the operator's robots.txt nonetheless signals `ai-train=no`
-  (S19). Those are different instruments and they point in different directions — use the Crossref /
-  Europe PMC mirrors, which is what the operator recommends anyway.
-
-## 10. Caveats and controversies
-
-1. **Publisher ownership is not disclosed on the preprint site.** Research Square Company is wholly
-   owned by Springer Nature (S12). The word "Springer" appears **zero times** on the platform home
-   page and zero times on the In Review page; it appears twice on the buried Editorial Policies page
-   (as "the Springer Nature In Review service") (S1, S3, S4 — grep counts 2026-09-01). The `/about`
-   page describes Research Square as *"a division of Research Square Company"* and a *"mission-driven
-   business"* without naming the parent (S6). A reader assessing independence has to go and find that
-   out.
-2. **The conflict-of-interest structure, stated plainly.** One corporate group (a) publishes the
-   journal, (b) runs the preprint server the manuscript is auto-posted to, and (c) sells the author
-   paid English editing, translation, presubmission review, independent peer review (Rubriq), video
-   abstracts and "research promotion" — with those services linked from the top navigation of the
-   preprint site itself (S1, S13). AJE advertises that it is *"Nature's preferred provider of author
-   services"* (S13). Nothing here is hidden or unlawful, and language editing is a legitimate need;
-   but an author who opts into In Review at a Springer Nature journal is inside a single commercial
-   funnel at every stage, and the preprint server has a commercial interest in that author becoming
-   an AJE customer. **Disclose this if you rely on the platform in an assessment context.**
-   *AJE list prices were not retrieved: the pricing page loads figures via JavaScript and rendered as
-   "Loading…" to a plain HTTP client* [NOT-VERIFIED] (S13).
-3. **The rejection-erasure asymmetry** (§5) — an unbranded preprint may be a rejected manuscript.
-   This is the single most consequential caveat.
-4. **Screening decisions are unappealable** (S4 §11).
-5. **Wikipedia's size and launch-year figures are badly out of date** (§3) — do not propagate them.
-6. **The browse endpoint ignores query parameters server-side** (§8) — a tooling trap that silently
-   returns the global total.
-7. **Editorial notes are at the operator's discretion**: *"Research Square maintains discretion over
-   the content of the note"*, though authors are informed (S4 §9).
-
-## 11. Sources
-
-- **S1** — https://www.researchsquare.com/ · retrieved 2026-09-01 [WEB] · navigation (Browse, In
-  Review, Journals, AJE Video Bytes, AJE Professional Editing, AJE Rubriq, API Access), 15 featured
-  subjects, ISSN 2693-5015, "division of Research Square Company".
-- **S2** — https://www.researchsquare.com/browse · retrieved 2026-09-01 [WEB] ·
-  `props.pageProps.initialProps.result.total = 468390`; item records with `article_identity`,
-  `journal_title`, `status`, `posted_at`, `url`.
-- **S3** — https://www.researchsquare.com/researchers/in-review · retrieved 2026-09-01 [DOC] ·
-  In Review mechanism, opt-in, CC BY, 72 h / 48 h posting, Under Review / Under Revision / Published
-  statuses, **rejection behaviour**, versioning restriction, indexing, Portico.
-- **S4** — https://www.researchsquare.com/legal/editorial · retrieved 2026-09-01 [DOC] · Editorial
-  Policies §§1–15: content types, LLM authorship, screening criteria, time to post, withdrawal and
-  removal, Research Square-initiated withdrawals and editorial notes, indexing, no-appeal rule,
-  commenting policy, Portico archiving, CC BY 4.0.
-- **S5** — https://www.researchsquare.com/journals · retrieved 2026-09-01 [WEB] · 1,503 participating
-  journals/platforms extracted from the rendered list; CS/EE titles enumerated in §2. Full list saved
-  to `scratch/preprint-repositories/contested/rs-journals-list.txt`.
-- **S6** — https://www.researchsquare.com/about · retrieved 2026-09-01 [DOC] · "largest author
-  services company, American Journal Experts (AJE)"; "over 775,000 manuscripts from researchers in
-  192 countries".
-- **S7** — https://www.researchsquare.com/article/rs-10510743/v1 · retrieved 2026-09-01 [WEB] ·
-  live In Review example: banner text, DOI `10.21203/rs.3.rs-10510743/v1`, licence CC BY 4.0,
-  status `under-review`, full peer-review event timeline quoted in §5.
-- **S8** — https://api.crossref.org/prefixes/10.21203/works?rows=0&facet=type-name:* · retrieved
-  2026-09-01 [API] · 514,618 total; 512,417 `posted-content`, 2,201 `component`.
-- **S9** — https://api.openalex.org/sources/S4306525896 · retrieved 2026-09-01 [API] · 484,792 works,
-  281,027 citations, counts_by_year 2018–2026.
-- **S10** — https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=PUBLISHER:"Research Square"
-  · retrieved 2026-09-01 [API] · hitCount 470,988.
-- **S11** — https://www.springernature.com/gp/authors/campaigns/in-review · retrieved 2026-09-01
-  [DOC] · Springer Nature's own In Review page: launched October 2018, "brought to you by our
-  partners at Research Square", opt-in flow, and the permanence statement quoted in §5.
-- **S12** — https://www.thebookseller.com/news/springer-nature-completes-acquisition-of-research-square-company
-  · Brown L., *The Bookseller*, 1 December 2022 · retrieved 2026-09-01 [COM] · headline and lede
-  visible without subscription: full ownership after partial ownership. Body behind a soft paywall.
-- **S13** — https://www.aje.com/services/editing/ and https://www.aje.com/pricing/ · retrieved
-  2026-09-01 [DOC] · AJE service tiers (Standard / Premium / VIP / Scientific Editing, translation,
-  presubmission review, Rubriq, plagiarism check, Video Bytes); "We're also Nature's preferred
-  provider of author services"; "1 million+ authors served in 192 countries". Prices render via JS
-  and were not retrieved.
-- **S14** — https://en.wikipedia.org/wiki/Research_Square and
-  https://en.wikipedia.org/wiki/List_of_preprint_repositories (wikitext via MediaWiki API) ·
-  retrieved 2026-09-01 [COM] · owner "Springer Nature", launch 2013 (article) vs 2018 (list),
-  ">223,000 as of May 2023" and ">100,000" size claims, CC BY licence-conflict warning.
-- **S15** — Kirkham JJ, Penfold NC, Murphy F, Boutron I, Ioannidis JP, Polka J, Moher D. *BMJ Open*
-  2020;10:e041849 · https://doi.org/10.1136/bmjopen-2020-041849 · metadata retrieved 2026-09-01
-  [LIT] · comparative survey of preprint-platform screening including Research Square.
-- **S16** — https://www.researchsquare.com/request-api · retrieved 2026-09-01 [DOC] · token-gated
-  JSON API; explicit recommendation to use Crossref prefix 10.21203 or Europe PMC for analysis.
-- **S17** — path probes on www.researchsquare.com (`/api`, `/api-access`, `/in-review`,
-  `/editorial-policies`, `/help`, `/sitemap.xml`) · 2026-09-01 [WEB] · 404/200 codes and byte sizes
-  as tabulated.
-- **S18** — https://www.researchsquare.com/rss.xml · probed 2026-09-01 [WEB] · HTTP 200, RSS 2.0,
-  channel title "Preprints".
-- **S19** — https://www.researchsquare.com/robots.txt · retrieved 2026-09-01 [DOC] · Cloudflare
-  content signals `search=yes,ai-train=no,use=reference`; per-agent `Disallow: /` blocks.
-- **S20** — negative-control probes, 2026-09-01 [WEB] · `/article/rs-99999999/v1` → 200/16,824 B;
-  `/article/rs-10510743/v9` → 200/16,824 B; `/browse?q=…` → `total` unchanged at 468,390.
diff --git a/research/preprint-repositories/retrieval-notes.md b/research/preprint-repositories/retrieval-notes.md
deleted file mode 100644
index 1956d8b..0000000
--- a/research/preprint-repositories/retrieval-notes.md
+++ /dev/null
@@ -1,397 +0,0 @@
-# Retrieval notes — scholarly and archival hosts
-
-Findings from probing ~120 scholarly, archival and repository hosts on **2026-09-01 → 2026-09-04**.
-
-> **Status: MERGED into the shared crawler table on 2026-09-20.**
-> Per [`AGENTS.md`](../../AGENTS.md) rule 8, these findings now live in
-> [`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md) under a new
-> **Scholarly / preprint / archival** section, plus seven additions to *General retrieval tips* and
-> a **dated correction** to that file's existing `archive.org/wayback/available` guidance, which
-> this pass disproved (see §9). The merge appended only — no existing content was restructured, and
-> concurrent unstaged work in that file was left intact.
->
-> **This file remains the fuller record**, with per-host byte sizes, probe dates and the reasoning
-> behind each finding. The crawler table carries the operational summary.
->
-> Nothing below was obtained by bypassing authentication or access control — only public pages, and
-> only with the user-agent ladder already documented in `AGENTS.md`. No shadow-library service was
-> probed; see [`bulk-libraries-and-shadow-archives.md`](bulk-libraries-and-shadow-archives.md).
-
----
-
-## 1. Block fingerprints — telling "blocked" from "broken"
-
-The single most reusable output of this pass. **A 403 with a characteristic body size identifies the
-blocking product**, which tells you whether to retry, switch route, or give up.
-
-| Body size | Product | Hosts observed |
-|---|---|---|
-| **~5.2–6.1 kB** | Cloudflare managed challenge (`cf-mitigated: challenge`) | `techrxiv.org` 5,620 · `authorea.com` 5,620 · `essopenarchive.org` 5,622 · `scienceopen.com` 5,602 · `chemrxiv.org` 5,595 · `africarxiv.pubpub.org` 5,583 · `alldatasheet` 5,603 · Advance/SAGE 5,388–5,623 · **`oatd.org`** (incl. `robots.txt`) · `tdx.cat` · `ethos.bl.uk/catalog*` · `graz.elsevierpure.com` |
-| ~2.1–7.8 kB | ⚠ **Anubis — but it answers HTTP 200, not 403.** See the soft-200 table below and §3 | `archive.softwareheritage.org` · `rcaap.pt` · `portal.dnb.de` · `base-search.net` · `scipost.org` · `helda.helsinki.fi` |
-| **~651 kB** | SHERPA/OpenDOAR block page | `v2.sherpa.ac.uk` 651,922 |
-| **1,337 B** | **ETH Zürich custom "Access Restricted"** — self-documenting, gives a contact address, and is **IP/provider-scoped, not UA-scoped** | `research-collection.ethz.ch`. OAI-PMH is open behind it |
-| **1,697 B** | Oasisbr "Verificando conexão" interstitial | `bdtd.ibict.br` |
-| **~370 B** | minimal 403 (not Cloudflare) | `gao.gov` |
-| **369 B** | minimal 403 | `preprints.org` |
-| **283 B** | origin UA filter | `bitsavers.org` (to `Wget/1.21.4` and default `curl`) |
-
-**Rule: record the byte size, not just the status.** A ~5.6 kB 403 means the host is alive and
-refusing a robot; it does not mean the resource is absent.
-
-### The complement: soft-200s
-
-Worse than a 403, because they look like success.
-
-| Host | Behaviour |
-|---|---|
-| `osf.io` | **HTTP 200, identical 4,207-byte SPA shell for providers that do not exist.** Confirmed independently — `ecsarxiv.org`, `biohackrxiv.org`, `arabixiv.org`, `psyarxiv.com`, `osf.io/preprints/` all returned exactly 4,207 bytes |
-| `unpaywall.org` | **HTTP 200, byte-identical 1,421-byte SPA shell for every path** |
-| `eccc.weizmann.ac.il` | **HTTP 200 + 17,041 bytes** for any nonexistent path (17,032 for a bogus year) |
-| `openreview.net` | `forum?id=<real>` and `forum?id=ZZZZZZZZZZ` **both** return HTTP 200, 4,787 bytes |
-| `papers.ssrn.com/oai` | HTTP 200 "Page Cannot be Found", byte-identical to a bogus path. **SSRN has no OAI-PMH** |
-| `optimization-online.org` | ~93,500-byte themed 404 bodies — content-length useless as an existence test |
-| `iris.eecs.berkeley.edu` | **58,829-byte themed 404 for every path**, including the technical-report index. See §5 |
-| `figshare.com`, `kilthub.cmu.edu` | **HTTP 202 with a zero-byte body** to a plain GET — neither success nor a usable error |
-| `escholarship.org` | **HTTP 202 / 0 bytes** — the same non-answer on a third independent tenant |
-| `ethos.bl.uk` | **`OrderDetails.do?uin=<bogus>` returns HTTP 200 and the home page.** A link-checker reports 100% success on any legacy EThOS bibliography |
-| Google cache | **HTTP 200 with a 91,694-byte Google Search shell.** Silent-corruption hazard — the cache route is gone but returns 200 |
-| **Anubis proof-of-work** (`rcaap.pt` 4,511 · `portal.dnb.de` 4,475 · `base-search.net` 7,846 · `scipost.org` 3,903) | **HTTP 200 with a challenge body.** Re-verified 2026-09-11. Detect by `<title>Making sure you're not a bot!</title>` — *not* by status or size. `helda.helsinki.fi` serves Anubis's error page, `<title>Oh noes!</title>`, also at 200 |
-| `chinaxiv.org/abs/*` | Same 403 for real and bogus identifiers. Existence untestable. A bogus `.htm` path *does* give a true 404 |
-
-**Clean, trustworthy status codes** — rare enough to be worth naming: `engrxiv.org` (22-byte 404s),
-`bitsavers.org` (280-byte 404s), `vixra.org`, and the `api.osf.io` JSON API (61-byte 404s).
-
----
-
-## 2. The Internet Archive — the most important operational section
-
-Sibling passes measured this twice, two days apart, and **the two runs disagree on both the ceiling
-and the failure mode.** The corrected picture:
-
-1. **There is no fixed quota.** One run blocked after ~3 requests; the other made **16 consecutive
-   200s and blocked at #17**. The low figure was measured inside an already-throttled window.
-2. **429 and TCP-refusal are alternative modes, not an escalation.** One run went straight to
-   connection refusal and **never emitted a single 429 in ~60 requests**.
-3. **⚠ The throttled state flaps.** Identical Chrome requests one second apart:
-   `200 200 000 000 000 200 200 000 000 000`. **A bulk fetch through a throttle window yields a
-   silent mixture of retrieved and missing files, with nothing distinguishing "not archived" from
-   "refused".** This is the finding most likely to corrupt a harvest.
-4. **CDX does *not* stay open.** It lives on `web.archive.org`, the same host as replay, and
-   degraded in both runs (`000` in refusal-mode, `503` in 429-mode). The earlier note claiming CDX
-   survives while replay blocks is **wrong**.
-5. **What actually survives is the `archive.org` host.** During a live block, `wayback/available`,
-   `metadata/<id>` and `advancedsearch.php` all returned 200. **Route around by host, not by agent.**
-6. **UA rotation is useless here and actively dangerous.** While blocked, `curl` and ClaudeBot
-   returned 200 in the same second that Googlebot and no-UA returned `000`. Sampling once would
-   record a spurious "working user agent" that is really just the flapping.
-7. **Byte sizes drift day-to-day** (replay 16,004→16,006; metadata 4,438→4,437). Good for
-   recognising a *class* of response; useless for equality tests.
-
-**Practical rule: retry a CDX query at least twice before recording "no captures".**
-
-### archive.today
-
-**Correction to an earlier note.** `archive.ph/timemap/<url>` **works** — a valid RFC 7089 Memento
-TimeMap, HTTP 200 / 1,497 B, 5/5 attempts, plain Chrome UA, no CAPTCHA. Only `/newest/` is walled
-(429, 63,290 B). With the Memento Aggregator dead this is the one remaining scriptable way to ask
-archive.today what it holds. The previous "no API, everything CAPTCHA-walled" claim was costing a
-recovery route. Caveat: undocumented endpoint, verified on one day only.
-
----
-
-## 3. Proof-of-work walls defeat the UA ladder entirely
-
-A newer obstacle than Cloudflare. **Anubis / BotStopper** issue a JS proof-of-work challenge, and
-rotating user agents cannot help — there is no agent that is exempt.
-
-| Host | Behaviour | Way around it |
-|---|---|---|
-| `www.econstor.eu` | Website behind Anubis | **OAI-PMH wide open.** Probing only over HTTP wrongly concludes EconStor is down |
-| `cds.cern.ch` | ~~HTML and REST behind Anubis~~ — **no longer walled** as of 2026-09-11: HTTP 200, 41,946 B, real page | OAI-PMH open — 578,928 records |
-| `scipost.org` | Anubis — **HTTP 200** challenge, 3,903 B (re-verified 2026-09-11) | Crossref prefix `10.21468` — 12,558 works |
-| `base-search.net` | Anubis v1.27.0+dirty | None found. BASE's size is unverified as a result |
-| `archive.softwareheritage.org` | Anubis interstitial (4,667 B) to a browser UA | **A `curl`-style request gets JSON (1,643 B).** The ladder runs *backwards* here |
-| `web-archive.southampton.ac.uk` | HTTP **401** for real *and* bogus paths | None found. CogPrints' item count stays unverified |
-| `hprints` | Anubis wall | Open API behind it |
-| **`theses.hal.science`** (`devel`) · **`portal.dnb.de`** (1.25.0) · **`trove.nla.gov.au`** (v1.26.2) · **`helda.helsinki.fi`** (1.23.0) · **`dans.knaw.nl`** (1.25.0) | Anubis, national-library layer | Protocol change — OAI-PMH / REST |
-| **`rcaap.pt`** (v1.26.0-pre2) | Anubis — **HTTP 200** challenge, 4,511 B (re-verified 2026-09-11) | **None — the first host where the OAI-PMH escape hatch is *also* behind the wall.** The general rule below has an exception |
-
-**Anubis has spread from a handful of sites to the national-library layer during this survey** — nine hosts now, versions 1.23.0 through 1.27.0. Treat it as the emerging default, not an oddity.
-
-**General rule worth promoting to the main table: when a scholarly site blocks you, look for OAI-PMH, Crossref, Handle.net or a REST API before concluding it is unreachable.** In eight of nine cases here the machine-readable interface was open while the human-facing one was walled — `rcaap.pt` is the sole counter-example.
-
-**The UA ladder solved nothing in the thesis pass.** What worked was **changing protocol**: DSpace 7 REST, DataCite, OAI-PMH, Handle.net. Record that alongside the ladder, because rotating agents against a proof-of-work wall is wasted effort by construction.
-
----
-
-## 4. Existence oracles that work behind a bot wall
-
-### `hdl.handle.net` — the best one found
-
-`https://hdl.handle.net/api/handles/<prefix>/<suffix>` returns JSON with `responseCode: 1` for a
-handle that exists and `100` for one that does not. It is **served by the Handle System, not by the
-target repository, so it is immune to the target's bot wall.** Verified against Cloudflare-walled
-TDX (prefix `10803`) and MIT DSpace (prefix `1721.1`).
-
-**Strictly better than the `doi.org` trick below** wherever a handle exists — it gives a positive
-JSON answer rather than an inference from a status code. Most DSpace and EPrints repositories mint
-handles, so this covers most institutional repositories and nearly all ETD systems.
-
-### `doi.org` — the fallback
-
-- `doi.org` returns **404 for an unregistered DOI**.
-- For a **registered** DOI it redirects and **passes through the target host's 403**.
-
-**A 403 from a `doi.org` redirect therefore confirms the record exists**, even when the landing page
-cannot be read. This made it possible to measure PeerJ Preprints, ChemRxiv and TechRxiv while all
-three were unreadable.
-
----
-
-## 5. Per-host reachability
-
-Measured directly on **2026-09-01**, following redirects, Chrome 131 UA. `bytes` is the body size.
-
-| Host | Code | Bytes | Note |
-|---|---|---|---|
-| `arxiv.org` | 200 | 38,051 | |
-| `eprint.iacr.org` | 200 | 14,117 | 20/min per-path limit, see §6 |
-| `zenodo.org` | 200 | 69,556 | |
-| `hal.science` | 200 | 12,606 | default `curl` sufficient |
-| `optimization-online.org` | 200 | 98,725 | 404 bodies ~93.5 kB |
-| `engrxiv.org` | 200 | 22,323 | honest 404s |
-| `chinaxiv.org` | 200 | 104,948 | but `/abs/*` 403s all agents |
-| `jxiv.jst.go.jp` | 200 | 44,900 | |
-| `preprints.scielo.org` | 200 | 39,311 | |
-| `preprints.ru` | 200 | 27,658 | |
-| `preprints.aijr.org` | 200 | 31,101 | |
-| `researchsquare.com` | 200 | 22,147 | |
-| `qeios.com` | 200 | 411,206 | |
-| `vixra.org` | 200 | 10,486 | correct hard 404s |
-| `ssrn.com` | 200 | 70,049 | but `papers.ssrn.com` 403s everything |
-| `ideas.repec.org` | 200 | 29,872 | asks you not to scrape |
-| `econstor.eu` | 200 | 4,806 | Anubis; OAI open |
-| `biorxiv.org` | 200 | 31,863 | **429 to Chrome/curl/ClaudeBot; 200 to `WhatsApp/2.23.20.0`** |
-| `medrxiv.org` | 200 | 39,119 | |
-| `philarchive.org` | 200 | 635,810 | |
-| `philsci-archive.pitt.edu` | 200 | 45,028 | **ladder runs backwards — default `curl` beats Chrome** |
-| `lingbuzz.net` | 200 | 16,418 | **HTTP 502 for out-of-range IDs; no `HEAD`** |
-| `roa.rutgers.edu` | 200 | 6,278 | "API" is a 1,463-row XLSX |
-| `eprints.rclis.org` | 200 | 13,476 | EPrints 3.4.6 |
-| `web.ma.utexas.edu/mp_arc/` | 200 | 5,516 | frozen archive, intact |
-| `eartharxiv.org` | 200 | 11,141 | |
-| `socopen.org` | 200 | 82,394 | |
-| `indiarxiv.in` | 200 | 97,976 | relaunch, 0 records |
-| `osf.io/preprints/` · `ecsarxiv.org` · `biohackrxiv.org` · `arabixiv.org` · `psyarxiv.com` | 200 | **4,207** | identical SPA shell — meaningless |
-| `figshare.com` | **202** | **0** | zero-byte body |
-| `techrxiv.org` | 403 | 5,620 | every path except `/robots.txt` |
-| `authorea.com` | 403 | 5,620 | |
-| `scienceopen.com` | 403 | 5,602 | |
-| `chemrxiv.org` | 403 | 5,595 | |
-| `essopenarchive.org` | 403 | 5,622 | |
-| `africarxiv.pubpub.org` | 403 | 5,583 | block page **differs by agent** — ChatGPT-User got 25 B |
-| `preprints.org` | 403 | 369 | |
-| `synthical.com` | **000** | 0 | DNS resolves `162.55.17.19`; TCP :443 and :80 both time out |
-| `cogprints.org` | **000** | 0 | **TLS SAN mismatch** (cert is `CN=web-archive.southampton.ac.uk`). ⚠ **The plain-HTTP recovery route has since degraded** — on 2026-09-11 it 301s to Southampton and returns **HTTP 401** (7,493 B, BotStopper), not 200 |
-
-**Blocking all agents tried:** `papers.ssrn.com` (including Googlebot) · `peerj.com` ·
-`hrbopenresearch.org` · `amrcopenresearch.org` · `cell.com` · `cabidigitallibrary.org` ·
-`dl.acm.org/opentoc` · `doabooks.org` · `science.org` (no Wayback snapshot either) ·
-`crimrxiv` (apex + WhatsApp UA succeeded exactly once, then reverted).
-
-**Unreachable by TCP, not by policy:** `hpl.hp.com` (DNS resolves `15.73.144.188`, TCP times out) ·
-`datasheetcatalog.com` (NXDOMAIN) · Berkeley CS262A reading list (connect failure) ·
-`catalogodeteses.capes.gov.br` (`getent hosts` returns **only AAAA**; an A record exists via
-`ahostsv4` — an IPv6-only resolution path that looks like a dead host).
-
-### Berkeley EECS went dark mid-survey, then came back at a new path
-
-**Corrected on re-probe 2026-09-11.** During the original pass `www2.eecs.berkeley.edu` 302-redirected
-to `iris.eecs.berkeley.edu`, which served a 58,829-byte themed 404 for every path including the
-technical-report index.
-
-**The series is now restored on its original host**, at a new `/Archive/` path segment:
-`https://www2.eecs.berkeley.edu/Pubs/TechRpts/<year>/Archive/<report>.pdf`. All six RISC-V reports
-return HTTP 200 with `%PDF-` magic; `EECS-2016-1` is **959,927 bytes**, matching both the pre-outage
-size and the Wayback capture. The index is back at 200 / 122,784 B.
-
-`iris.eecs.berkeley.edu` still serves the 58,829-byte themed 404 (negative control confirmed), so it
-was a staging artefact of a migration in progress rather than a new home. The earlier note in this
-file recording `www2.eecs.berkeley.edu` as *TCP-dead* was a transient and is withdrawn.
-
-
----
-
-## 6. Rate limits and terms
-
-- **`eprint.iacr.org`** — no UA fallback needed, but a hard Cloudflare **"20 per 1 minute" per-path
-  limit with no `Retry-After`**. `robots.txt` is `Disallow: /` by default while whitelisting
-  `Claude-User`/`Claude-SearchBot` for metadata and banning all PDFs. **TDM explicitly reserved
-  despite the PDFs being CC-BY.** OAI-PMH returns all 27,552 identifiers in one 3.34 MB response.
-- **arXiv** — "no more than one request every three seconds." Honour it.
-- **OpenAlex** — **rate limiting is now credit/USD denominated**: `x-ratelimit-limit: 1000`,
-  `x-ratelimit-limit-usd: 0.1`, `meta.cost_usd: 0.0001`. **Harvesters written against the old
-  "polite pool, 100k/day" documentation fail silently.**
-- **RePEc** — asks you not to scrape; API behind a written application. Two RePEc documents
-  disagree on commercial use.
-- **ECCC** — no OAI-PMH, no API, no dump; licence permits only "interactive viewing and/or printing
-  for personal use", i.e. **TDM forbidden**.
-- **Semantic Scholar** — HTTP 429 unauthenticated; HTTP 500 on bulk. Needs a key.
-- **NASA ADS** — HTTP 401; token mandatory.
-- **`bitsavers.org`** — blocks `Wget` and default `curl` (403/283 B) but serves Chrome. **Its
-  `robots.txt` is HTTP 200 with zero bytes**, so a naive crawler reads an open invitation and then
-  gets 403. Correct route is the operator-sanctioned `rsync://bitsavers.org/`, or a mirror —
-  **mirrors do not apply the origin's block**, which is the right answer rather than UA substitution
-  (`AGENTS.md` rule 7).
-- **`dblp`** — all three mirrors returned 503 on the bulk `dblp.xml.gz` dump. Retry later; the data
-  is CC0.
-
----
-
-## 7. API traps that silently corrupt a harvest
-
-Not access control, but they will poison a dataset without erroring. Cross-referenced in
-[`README.md § Probing traps`](README.md#6-probing-traps).
-
-- **arXiv API `max_results=0` is broken** — HTTP 200, `totalResults=1`, and a fake entry titled
-  "Error". A harvester using it records **1 for every category**. Use `max_results=1`. The API also
-  returns 200 with an empty feed for nonexistent papers, while the web front end 404s.
-- **arXiv aliases `cs.NA` and `cs.SY` return 0** on API queries — silent data loss.
-- **HAL's subject field is `domainAllCode_s`, not `domain_s`** — the wrong field returns a
-  confident, silent `numFound: 0`.
-- **Zenodo returns HTTP 200 with `total: 0` for invalid facet values.** Separately, unquoted
-  `RISC-V` returns 422,778 hits against 495 quoted — an **~850× inflation** from hyphen
-  tokenisation.
-- **NTRS and OSTI both treat an empty `q=` as "match nothing", not "match everything"** — two
-  independent federal agencies, same trap. **CiNii Dissertations makes it three** (no parameters →
-  `totalResults: 0`; `q=*` → 0). **Promote this to a general rule: never trust an empty or wildcard
-  query to mean "everything" — always cross-check against a known-populated facet.** NTRS holds
-  646,950 records but **only 358,213 (55.4%) actually have a document attached**. OSTI puts its
-  total in the `x-total-count` **header**, and `links[rel=fulltext]` → `/servlets/purl/<id>` is a
-  verified direct-PDF route.
-- **OAI-PMH signals errors in the body with HTTP 200.** An invalid verb against ETH's endpoint
-  returns 200 with a 488-byte error document. **Never status-check an OAI-PMH endpoint** — parse it.
-- **`api.core.ac.uk/v3/search/works` without the trailing slash returns HTTP 200 and a Cloudflare
-  `cdn-cgi/content` HTML redirect**, not JSON.
-- **`theses.fr/api/v1/theses/these/<bogus>` returns HTTP 200 with a zero-byte body.**
-- **Shodhganga carries a stale count inside an HTML comment** — `597316` in `<!-- -->` beside the
-  live `697675`. A tag-stripper that ignores comments reads **100,359 too low**.
-- **`web.archive.org/cdx` returned a negative `length` field**: `20250926194305 403 -6693296525`.
-  Validate numeric fields from CDX before arithmetic.
-- **OpenReview's per-venue counts cap at 10000.** ICLR 2025 and 2026 both read exactly `10000` —
-  that is a ceiling, not a count. Between 2026-09-02 and 09-04 all `/notes` endpoints moved behind
-  `ChallengeRequiredError` (403) to **six different user agents**, so the figures could not be
-  re-derived.
-- **SSRN networks must never be summed** — 68 networks total 4,569,102 against ~1.5 M actual papers
-  (≈3.0 cross-listings each).
-- **Zenodo, OSF and TechRxiv count *versions*, not works.** Measured inflation +1.6% to +50%;
-  TechRxiv is 30,954 DOI records for 18,890 items.
-- **Unpaywall is DOI-keyed and has a measurable arXiv blind spot.** `10.1145/3079856.3080246` (the
-  TPU paper) returns `oa_status: closed` with zero locations; OpenAlex agrees because it inherits
-  Unpaywall. **Semantic Scholar returns `externalIds.ArXiv: "1704.04760"`.** If the author never
-  added the DOI to the arXiv record, no edge exists. Always cross-check Semantic Scholar.
-- **Unpaywall's free bulk snapshot is ~21 months stale** (newest 2024-11-27, 39.2 GB). OpenAlex's S3
-  snapshot is free and current.
-- **`CiteSeerX` is dead, and its negative control proves it**: every path — including `robots.txt`
-  and a deliberately bogus path — 301s to a *fixed* Wayback timestamp `20251230112235`. Following it
-  returns 429.
-- **`api.biorxiv.org` returns two plausible totals in one object** — `total` (479,561, every
-  version) and `count_new_papers` (348,506, distinct preprints). The obvious field is the wrong one
-  for counting preprints. Verified 2026-09-11.
-- **Follow redirects when probing APIs.** `zenodo.org/api/*` and `export.arxiv.org` over HTTP both
-  301; omitting `-L` yields an empty body that reads as a block. Two false "rate-limited"
-  conclusions in this pass traced to exactly this.
-- **PMC's legacy `oa.fcgi` endpoint 404s** on both `ncbi.nlm.nih.gov` and `pmc.ncbi.nlm.nih.gov`.
-
----
-
-## 8. TLS state as an abandonment signal
-
-Expired or never-issued certificates found: `africarxiv.ubuntunet.net` (expired 2026-07-25),
-`latarxiv.org` (expired 2026-08-20 19:26:19), `rinarxiv.lipi.go.id` (self-signed `CN=linux`, 2023).
-`www.inarxiv.id` is **NXDOMAIN**.
-
-**The converse does not hold.** `bodoarxiv.org`, `lawarxiv.org`, `mediarxiv.org` and `frenxiv.org`
-all carry fresh auto-renewed certificates while being, respectively, an online casino, a 114-byte
-parking stub, a stranger's redirect and a six-year-frozen zombie. **Parking services run ACME.**
-In this dataset TLS automation outlived editorial staffing in every divergent case. See
-[`reliability-and-durability.md` §5](reliability-and-durability.md#5-durability--the-headline-result).
-
----
-
-## 9. Archival candidates
-
-**Every candidate examined in this pass turned out to be already archived.** That conclusion was
-reached twice — the first time wrongly, in the opposite direction — and the reason is important
-enough to lead with.
-
-### ⚠ `archive.org/wayback/available` returns false negatives. Use CDX.
-
-The canonical "is this URL archived?" endpoint **reported no captures for a URL that has been
-continuously archived since 2018.**
-
-```
-archive.org/wayback/available?url=cs.helsinki.fi/u/kutvonen/index_files/linus.pdf
-  → {"archived_snapshots": {}}          # 2026-09-04, repeated, two separate sessions
-
-web.archive.org/cdx/search/cdx?url=...&output=json
-  → captures 2018-05-11 … 2026-08-07, HTTP 200        # same URL, same minute
-```
-
-**This is the worst failure mode in the whole survey**, because it fails *toward* unnecessary work
-and false alarm: it tells you a document is unpreserved when it is safe. Anyone auditing link rot
-with `wayback/available` will manufacture phantom losses.
-
-**Rule: `wayback/available` is advisory only. Confirm absence with the CDX API before declaring
-anything unarchived.** Note this compounds with the throttling in §2 — CDX itself degrades under
-load, so retry twice before trusting a negative from *either*.
-
-### Resolved: the Torvalds thesis was never at risk
-
-Recorded in an earlier revision of this file as unarchived and needing urgent rescue. **It is fully
-preserved and byte-identical.**
-
-| Property | Value |
-|---|---|
-| URL | `cs.helsinki.fi/u/kutvonen/index_files/linus.pdf` |
-| Live size / type | **470,861 B**, `%PDF-1.3`, `Last-Modified: 2019-04-10` |
-| Live SHA-256 | `9fc48f477a9edc9592c52e912b3924da4595056b858486631d26f0f996b85714` |
-| Live SHA-1 (base32) | `ZVCIUY5JU6PJW3CN37K277F2Z4HLXYPV` |
-| Wayback CDX digest | `ZVCIUY5JU6PJW3CN37K277F2Z4HLXYPV` — **identical** |
-| Coverage | 2018-05-11 → **2026-08-07**, one digest throughout: the file has never changed |
-
-The **CDX `length` field is the WARC record length, not the payload size** (422,587 / 418,490 /
-438,660 across captures of the same bytes). **Never compare `length` to a file size** — compare the
-digest, which is a base32 SHA-1 of the payload and is directly checkable against a local copy, as
-above.
-
-### Berkeley EECS — the whole RISC-V set is recoverable
-
-Despite the live series being down (§5), **all six reports have HTTP 200 Wayback captures**:
-
-| Report | Newest 200 capture |
-|---|---|
-| UCB/EECS-2011-62 | `20260505221228` |
-| UCB/EECS-2011-63 | `20250521085055` |
-| UCB/EECS-2014-54 | `20251231214818` |
-| UCB/EECS-2016-1 | `20260409151000` |
-| UCB/EECS-2016-118 | `20251115022521` |
-| UCB/EECS-2016-161 | `20220621081911` |
-
-Durable form: `https://web.archive.org/web/<timestamp>/https://www2.eecs.berkeley.edu/Pubs/TechRpts/<year>/<report>.pdf`
-
-### Remaining candidates
-
-| Candidate | Status |
-|---|---|
-| **Stanford CS/CSL technical-report index** (1,332 bytes) | **OPEN** — the only genuinely unchecked item. Verify with CDX, not `wayback/available` |
-| `web.ma.utexas.edu/mp_arc/` · `roa.rutgers.edu/info.html` · `optimization-online.org` old `DB_HTML` | Already captured |
-
-**Note on `save/` semantics:** HTTP **523** means the job was refused (throttling) and nothing was
-saved; HTTP **302** means it was accepted. Neither confirms a capture — **re-check via CDX**.
-
-**Standing finding worth propagating:** the DEC SRC/WRL/CRL research-report series survives *only*
-because someone mirrored it to bitsavers in 2007 — 521 reports plus a 236,085,636-byte
-`Compaq-DEC_TRs_HPL_mirror_2007.zip`, while `hpl.hp.com` is TCP-dead. See
-[`recovering-dead-technical-sites.md`](recovering-dead-technical-sites.md). Berkeley is the same
-story caught earlier, and with a better outcome.
diff --git a/research/preprint-repositories/scienceopen.md b/research/preprint-repositories/scienceopen.md
deleted file mode 100644
index 0a43c68..0000000
--- a/research/preprint-repositories/scienceopen.md
+++ /dev/null
@@ -1,301 +0,0 @@
-# ScienceOpen — preprint repository record
-
-- **URL:** https://www.scienceopen.com/
-- **Operator:** ScienceOpen, Inc. — headquarters Pappelallee 78–79, 10437 Berlin, Germany; technical
-  office 131 Hartwell Ave., Suite 210, Lexington, MA 02421, USA (S1, S8). Co-founded 2013 by
-  Alexander Grossmann (Leipzig Univ. of Applied Sciences, ex-De Gruyter) and Tibor Tscheke (Ovitas);
-  the platform technology is provided by Ovitas (S8). Commercially funded by publisher services, not
-  by grants or a university.
-- **Discipline scope:** the *index* is all-discipline; the *hosted* content is a small,
-  heterogeneous multidisciplinary trickle with a visible skew to applied/engineering and
-  meta-research topics (§6).
-- **Launched:** 2013 (beta November 2013, v1.0 May 2014) · **Status:** active
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-## 1. What it is
-
-**ScienceOpen is primarily a discovery and post-publication-review layer over other people's
-content, with a small hosting operation bolted on.** It aggregates bibliographic records from
-Crossref, PubMed, PubMed Central, arXiv, SciELO and hundreds of publisher feeds into a searchable
-citation index, lets researchers curate those records into thematic *Collections*, and lets
-qualifying researchers attach signed, DOI-bearing peer reviews to any record in the index.
-
-Alongside that it operates three small first-party publication venues: **ScienceOpen Preprints**
-(free), **ScienceOpen Posters** (free), and **ScienceOpen Research** (a journal; USD 400 to publish
-after two positive reviews) (S3). Its commercial revenue comes from selling publishers and
-institutions branded discovery, metadata enrichment, hosting and journal-publishing services (S8).
-
-The homepage strapline is worth quoting because it is the source of most confusion about the
-platform: *"100+ million Publications · 500+ Partner Journals · 1,000+ Research Collections"* (S1).
-
-## 2. Scope and subject taxonomy
-
-There is no arXiv-style category scheme for hosted content. Submissions are tagged with free-choice
-disciplines and keywords by the author, and the search interface exposes a `preprint` filter plus
-discipline and keyword facets applied across the whole aggregated index (S3).
-
-The distinction that matters is not subject but **provenance**: search results mix (a) records
-ScienceOpen hosts, (b) records it has ingested from publishers, and (c) preprints it has ingested
-from other preprint servers. See §3.
-
-## 3. Size and growth — critically evaluating the ">1,000,000" figure
-
-**Wikipedia's *List of preprint repositories* gives ScienceOpen a size of ">1,000,000"** with the
-description *"A research and discovery network allowing scholars with at least 5 publications to
-freely review preprints"* (S9). The figure is **unsourced in that table**, and the current Wikipedia
-*article* on ScienceOpen contains no such number (S8).
-
-**That figure is wrong as a statement about hosted preprints, by roughly two orders of magnitude.**
-The evidence:
-
-| Measure | Value | Source |
-|---|---|---|
-| Records **indexed / aggregated** (homepage claim) | "100+ million Publications" | homepage, 2026-08-04 snapshot [WEB] (S1) |
-| Records aggregated (operator, 2023) | "over 86 million research articles and records" | own peer-review guidelines [DOC] (S2) |
-| Preprints **in the index** (operator, 2023) | "over 90 million records – **2 million of which are preprints**" — explicitly *"ScienceOpen aggregates preprints by integrating arXiv, BioRxiv, Preprints.org, PeerJ Preprints, ChemRxiv, and Open Science Framework repositories"* | own publish page [DOC] (S3) |
-| DOIs **actually minted by ScienceOpen**, all 7 prefixes | **7,620** total (3,249 "current") | Crossref member 5403 [API] (S4) |
-| Prefix 10.14293 (`posted-content` = **hosted preprints**) | **3,584** | Crossref [API] (S5) |
-| Prefix 10.14293, conference papers (posters) | 1,118 | Crossref [API] (S5) |
-| Prefix 10.14293, peer reviews | 893 | Crossref [API] (S5) |
-| Prefix 10.14293, journal articles | 272 | Crossref [API] (S5) |
-| *ScienceOpen Research* journal, works in OpenAlex | 143 (1,176 citations) | OpenAlex S2736351211 [API] (S6) |
-| *ScienceOpen Posters*, works in OpenAlex | 16 | OpenAlex S2764464541 [API] (S6) |
-| Records in Europe PMC (`PUBLISHER:"ScienceOpen"`) | 2,404 | Europe PMC [API] (S7) |
-
-Full Crossref breakdown across all seven ScienceOpen prefixes (2026-09-01) (S5):
-`10.14293` 6,994 · `10.58647` 311 (228 conference papers, 45 posted-content, 31 articles, 7 reports)
-· `10.54081` 197 · `10.59081` 64 · `10.54947` 34 (books/chapters) · `10.47959` 14 · `10.55914` 7.
-
-**Plain statement.** ScienceOpen hosts on the order of **3,600 original preprints** and under
-**8,000 original objects of all kinds**. The million-plus and hundred-million figures describe an
-*index of other people's records*, not a repository. Wikipedia's ">1,000,000" is not a hosting
-figure, and citing it as one — as the repository-list table implicitly does — is misleading. The
-correct comparator column value would be roughly **">3,500"**.
-
-The operator is not being deceptive about this; its own 2023 publish page says outright that the two
-million preprints are aggregated from arXiv, bioRxiv, Preprints.org, PeerJ, ChemRxiv and OSF (S3).
-The conflation happens downstream.
-
-**Growth is anaemic.** *ScienceOpen Research* has published 143 works since 2014, with per-year
-counts of 61 (2014), 35 (2015), 16 (2016), 2, 0, 1, 3, 2, 3, 16 (2024), 1 (2025), 3 (2026) (S6). The
-preprint stream is more active — 10 of the most recent `10.14293/pr2199.*` records were created
-27–29 August 2026 (S10) — but the whole first-party operation remains tiny.
-
-## 4. Screening and moderation — what gets in
-
-**Preprints:** *"After submission your preprint will undergo an editorial review to check for
-completeness and basic scholarly integrity in line with our general publication guidelines."* (S3)
-Those General Publication Requirements (S11) cover COPE-aligned publication ethics, originality
-("the same manuscript should not have been published elsewhere to avoid DOI duplication"),
-authorship criteria, completeness (single PDF with all figures/tables embedded), reference
-formatting, data citation, and SI units. **English is required for articles but explicitly not for
-preprints** — *"Preprints in all languages are welcome."*
-
-Explicitly: *"When a manuscript is submitted, it is initially checked only in terms of integrity, as
-well as formal and ethical criteria. The public peer review process starts **after** the manuscript
-has been approved by the editorial office and made public."* (S11)
-
-**The "5 publications" review gate.** To post a peer review you must have **five records linked to
-your ORCID**: *"To perform a peer review, all you need are 5 records associated with your ORCID to
-demonstrate that you are an active and professional researcher."* … *"Reviewers are required to have
-published at least five scientific manuscripts. To ensure that this condition is met, ScienceOpen has
-partnered with the non-profit ORCID."* Exceptions are granted on request for early-career
-researchers. Commenting (as opposed to reviewing) requires one or more items. (S2, S8)
-
-Reviews are **signed, public, CC BY 4.0 licensed and Crossref-DOI'd**, and integrate with
-ORCID/Publons/ImpactStory (S2).
-
-**Volume reality check.** The same operator page that describes the gate states: *"At the moment we
-have more than 86 million research articles and records on our platform… and we have more than 180
-post-publication peer reviews to date."* (S2, page dated 26 June 2023). Crossref now records 893
-peer-review DOIs under prefix 10.14293 (S5). Either way, the review network's throughput is
-negligible relative to the index it sits on. Wikipedia's business-model section records a similar
-audit: *"on 2022-08-01 ScienceOpen lists 115 reviews (with only 2 negative) and 77 publications"*
-for ScienceOpen Research (S8).
-
-## 5. Reliability — what you can and cannot trust
-
-**What a ScienceOpen *preprint* deposit guarantees:** a Crossref DOI, CC BY 4.0, an editorial
-completeness/integrity check, and inclusion in the platform's own index. Nothing about correctness.
-
-**What a ScienceOpen *search result* guarantees: nothing at all about hosting.** The overwhelming
-majority of what you see on ScienceOpen is ingested metadata for content hosted elsewhere. Always
-resolve the DOI and see where it lands. A record surfacing "on ScienceOpen" is not published by
-ScienceOpen.
-
-**What a ScienceOpen *review* guarantees:** that the reviewer had ≥5 ORCID-linked records, signed
-their name, and declared competing interests. That is a real, if low, bar — meaningfully better than
-anonymous comment sections. But the sample is tiny (§4) and, per the Wikipedia audit, historically
-almost never negative (S8) [COM].
-
-**The commercial-collections question.** Collections are curated by volunteer Collection Editors from
-the aggregated index and are free to create (S12). *Separately*, ScienceOpen sells publishers
-"advanced indexing and promotional services that showcase customer content within the discovery
-platform" (S8). So a record's prominence on the platform can reflect a paid promotional
-relationship rather than merit. The platform does not, on the pages retrieved, distinguish promoted
-from organic content in search results [NOT-VERIFIED as to current practice — the live search UI
-could not be retrieved, see §8].
-
-**The USD 400 step.** Publishing to *ScienceOpen Research* after ≥2 positive reviews costs
-USD 400 (S3). That is an author-pays journal fee attached to a review process whose reviewers were
-invited by the author. Wikipedia's summary of the workflow is blunt: *"the authors need to invite
-potential reviewers … After having received at least 2 independent reviews with recommendation for
-acceptance, the authors have an option to publish their work on ScienceOpen Research for 400 US$"*
-(S8). Author-selected reviewers plus an author-paid publication step is a weak filter; the 115
-reviews / 2 negative figure is consistent with that [INF].
-
-### How to sanity-check an item from here
-
-1. Resolve the DOI. Prefix `10.14293` (or `10.58647`, `10.54081`, `10.59081`, `10.54947`, `10.47959`,
-   `10.55914`) = ScienceOpen-hosted. Anything else = indexed from elsewhere; go to the real host.
-2. Check the object type at Crossref: `posted-content` (preprint), `conference-paper` (poster),
-   `journal-article` (ScienceOpen Research), `peer-review`.
-3. If reviews are attached, read them — they are signed and public, so they are checkable.
-4. Do not treat the search index's coverage claims as a quality signal for any individual record.
-
-## 6. What you actually find there — examples
-
-Most recent hosted preprints, Crossref prefix `10.14293`, created 27–29 August 2026 (S10):
-
-- *Edge-Enabled Autonomous UAV Systems for Disaster Management: Integrating Social…* — `10.14293/pr2199.004356.v1`
-- *Advanced Social Drone Networks for Real-Time Disaster Monitoring, Damage Assessment…* — `10.14293/pr2199.004348.v1`
-- *PubPeer Reviewing Its Critics: Questioning Qualification, Authority, Moderation…* — `10.14293/pr2199.004278.v1`
-- *"Unlocking Pharma's Potential: The AI-aided NLP Revolution"* — `10.14293/pr2199.004344.v1`
-- *Waste management as an integrated urban system: a comparative study of infrastructure…* — `10.14293/pr2199.004326.v1`
-
-Computing/software items retrieved by bibliographic query (S13):
-
-- *Quality Assessment of Scalable Software Systems in Production Environments* — `10.14293/pr2199.002759.v1` (2026)
-- *Hybrid Quantum Algorithms and Quantum Software Development Frameworks* — `10.14293/pr2199.000298.v1` (2023)
-- *Advancing Network Securing Strategies with Network Algorithms for Integrated Air Defense S…* — `10.14293/pr2199.000010.v1`/`.v2` (2023)
-- *Minimizing The Number Of Tardy Jobs Algorithm* — `10.14293/pr2199.000488.v1` (2023)
-- *AES Algorithm* — `10.14293/s2199-1006.1.sor-.ppoyrim.v1` (2020)
-- *Parallelize DSW Algorithm* — `10.14293/s2199-1006.1.sor-.ppvowys.v1` (2019)
-- *ADMINISTRATION SYSTEM FOR END TO END LUXURY APARTMENT MANAGEMENT SOFTWARE* — `10.14293/s2199-1006.1.sor-.ppr0hq1.v1` (2021)
-
-**Honest quality read.** The computing content is student-project- to workshop-grade. Titles like
-"AES Algorithm" and "Parallelize DSW Algorithm" are not the output of an active research community.
-A systems or electronics engineer will find essentially nothing of professional value in
-ScienceOpen's *hosted* corpus; the platform's utility, if any, is as a free federated search over
-records you could also reach via Crossref, OpenAlex or Europe PMC.
-
-## 7. Landmark papers
-
-None. ScienceOpen hosts no landmark work in software, distributed systems, databases, electronics or
-security, and the hosted corpus is too small and too junior for any to be plausible.
-
-## 8. Access, APIs and bulk retrieval
-
-- **The live site is behind a Cloudflare JavaScript challenge and could not be retrieved directly.**
-  `https://www.scienceopen.com/` returned **HTTP 403** with a `Just a moment…` Cloudflare interstitial
-  to *every* user agent tried on 2026-09-01: default `curl`, Chrome 131 desktop, `WhatsApp/2.23.20.0`,
-  ChatGPT-User, ClaudeBot, and a Linux Chrome UA (S14). `sitemap.xml`, `api.scienceopen.com` and
-  `blog.scienceopen.com` are likewise 403. Only `robots.txt` is served (200).
-- **Everything in this record for the live site therefore comes from (a) the Wayback Machine
-  snapshot of 2026-08-04 (S1), (b) archived `about.scienceopen.com` policy pages (S2, S3, S11, S12),
-  and (c) third-party APIs (Crossref, OpenAlex, Europe PMC).** Per AGENTS.md rule 6, a successful
-  archive retrieval is not evidence the live site is reachable for ordinary clients.
-- **No public API found.** `api.scienceopen.com` is 403; no OAI-PMH endpoint is advertised. **No
-  documented bulk dump.**
-- **robots.txt** (retrievable, S15) advertises five sitemaps — `/sitemap.xml`, `/sitemap-index.xml`,
-  `/sitemap-index-featured.xml`, `/sodocs_sitemap.xml`, `/soreviews_sitemap.xml` — all of which are
-  themselves 403 to scripted clients. It sets `Crawl-delay: 10`, Cloudflare content signals
-  `search=yes, ai-train=no, use=reference`, and `Disallow: /` for CCBot, ClaudeBot, GPTBot,
-  Google-Extended, Applebot-Extended, Amazonbot, Bytespider, meta-externalagent, SemrushBot, PetalBot
-  and Sogou. It also disallows `/review`, `/discussion`, `/advanced_search`, `/group(s)`,
-  `/discipline` and `/external`.
-- **Practical route for bulk work: Crossref member 5403** (all seven prefixes) — this is the only
-  reliable machine-readable path to ScienceOpen-hosted content (S4).
-
-### Negative controls (2026-09-01)
-
-| Probe | Result | Interpretation |
-|---|---|---|
-| `https://www.scienceopen.com/about-scienceopen` (invented path) | **HTTP 404**, 18,968 B | Real 404s exist behind the challenge for some routes. |
-| `https://www.scienceopen.com/` (valid path) | **HTTP 403**, 5,367–5,656 B, body = Cloudflare `Just a moment…` | A 403 here means *bot challenge*, not *absent*. |
-| `https://api.scienceopen.com/`, `blog.scienceopen.com` | HTTP 403, ~5.6 kB Cloudflare page | Same challenge; existence unconfirmed [NOT-VERIFIED]. |
-| Crossref prefix `10.14293` | 6,994 records | Independent confirmation the hosting operation is real and small. |
-
-## 9. Licensing and reuse
-
-- **Preprints, posters and journal articles: CC BY 4.0**, applied by the platform; authors retain
-  copyright (S3).
-- **Peer reviews: CC BY 4.0 with their own Crossref DOI** — reusable, citable, permanent records of
-  reviewing activity (S2).
-- Submission of preprints and posters is **free of charge**; only the *ScienceOpen Research* journal
-  step costs USD 400 (S3).
-- Text and data mining are permitted by licence but obstructed in practice by the Cloudflare
-  challenge and by robots.txt `ai-train=no` (S15). Use Crossref.
-
-## 10. Caveats and controversies
-
-1. **The size figure is the headline problem.** Any statement that ScienceOpen "has over a million
-   preprints" conflates an aggregated citation index with a repository. Hosted preprints ≈ 3,584
-   (§3). Correct the record wherever you see it.
-2. **Durability risk is material.** ScienceOpen, Inc. is a small commercial company; the hosted
-   corpus is ~7,600 DOIs; the technology stack is supplied by a third party (Ovitas); and **no
-   preservation arrangement (Portico, CLOCKSS, LOCKSS) is stated on any page retrieved**
-   [NOT-VERIFIED — I looked at the publish page, the general publication requirements and the
-   archived homepage and found none]. Contrast Preprints.org and Research Square, both of which
-   state Portico archiving explicitly. If ScienceOpen ceases operations, the DOIs survive at
-   Crossref but the content may not. **Do not treat this as an archival repository.**
-3. **Commercial promotion inside the discovery layer.** Publishers pay for "promotional services that
-   showcase customer content within the discovery platform" (S8). Prominence ≠ quality here.
-4. **Author-invited reviewers plus a USD 400 publication step** is a structurally weak filter (§5).
-5. **Bot-hostile.** The live site cannot be retrieved by scripted clients at all; this record depends
-   on archives (§8). Anyone verifying claims here should expect the same obstruction.
-6. **Wikipedia's article carries maintenance tags** for notability and citation quality dating to
-   February 2016 (S8) — treat it as a weak source, which is exactly the problem with the ">1,000,000"
-   table entry.
-
-## 11. Sources
-
-- **S1** — https://web.archive.org/web/20260804085502/https://www.scienceopen.com/ · Wayback snapshot
-  of 2026-08-04, retrieved 2026-09-01 [WEB] · homepage: "100+ million Publications", "500+ Partner
-  Journals", "1,000+ Research Collections"; ScienceOpen Preprints / Posters / Partner Journals
-  product structure; Grossmann quotation; Berlin/Lexington addresses.
-- **S2** — https://web.archive.org/web/20251204075650/https://about.scienceopen.com/peer-review-guidelines/
-  · page dated 26 June 2023, snapshot 2025-12-04, retrieved 2026-09-01 [DOC] · the 5-ORCID-record
-  review gate; ORCID moderation; CC BY + DOI on reviews; "more than 86 million research articles and
-  records"; "more than 180 post-publication peer reviews to date"; reviewer checklist.
-- **S3** — https://web.archive.org/web/20240128080242/https://about.scienceopen.com/publish/ · page
-  dated 2 August 2023, snapshot 2024-01-28, retrieved 2026-09-01 [DOC] · free preprint/poster
-  submission; CC BY 4.0 + Crossref DOI; two-step BASIC model; **USD 400** ScienceOpen Research fee
-  after ≥2 positive reviews; *"over 90 million records – 2 million of which are preprints"* and the
-  explicit list of aggregated sources (arXiv, bioRxiv, Preprints.org, PeerJ, ChemRxiv, OSF).
-- **S4** — https://api.crossref.org/members?query=scienceopen · retrieved 2026-09-01 [API] · member
-  5403 "ScienceOpen", prefixes 10.47959 · 10.14293 · 10.54947 · 10.55914 · 10.54081 · 10.58647 ·
-  10.59081; total-dois 7,620; current-dois 3,249.
-- **S5** — https://api.crossref.org/prefixes/{10.14293,10.47959,10.54947,10.55914,10.54081,10.58647,10.59081}/works?rows=0&facet=type-name:*
-  · retrieved 2026-09-01 [API] · per-prefix totals and type breakdowns quoted in §3.
-- **S6** — https://api.openalex.org/sources/S2736351211 and /S2764464541 · retrieved 2026-09-01 [API]
-  · ScienceOpen Research 143 works / 1,176 citations / ISSN-L 2199-1006 / counts_by_year;
-  ScienceOpen Posters 16 works.
-- **S7** — https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=PUBLISHER:"ScienceOpen" ·
-  retrieved 2026-09-01 [API] · hitCount 2,404.
-- **S8** — https://en.wikipedia.org/wiki/ScienceOpen (wikitext via MediaWiki API) · retrieved
-  2026-09-01 [COM] · founders, history, Ovitas technology, business model, promotional services, the
-  5-publication gate, the "115 reviews (only 2 negative) and 77 publications" audit of 2022-08-01,
-  Berlin/Lexington addresses, February 2016 notability and citation maintenance tags.
-- **S9** — https://en.wikipedia.org/wiki/List_of_preprint_repositories (wikitext via MediaWiki API) ·
-  retrieved 2026-09-01 [COM] · the ">1,000,000" row, unsourced, with the "at least 5 publications"
-  description and 2013 launch year.
-- **S10** — https://api.crossref.org/prefixes/10.14293/works?filter=type:posted-content&sort=created&order=desc
-  · retrieved 2026-09-01 [API] · ten most recent hosted preprints with DOIs and creation dates.
-- **S11** — https://web.archive.org/web/20240421184946/https://about.scienceopen.com/general-publication-requirements/
-  · page dated 25 July 2019, snapshot 2024-04-21, retrieved 2026-09-01 [DOC] · editorial-office
-  integrity/formal/ethical check before publication; COPE alignment; originality; completeness;
-  "Preprints in all languages are welcome"; rejection/EoC/retraction reservation.
-- **S12** — https://web.archive.org/web/20240128080245/https://about.scienceopen.com/collections/ ·
-  page dated 26 June 2023, snapshot 2024-01-28, retrieved 2026-09-01 [DOC] · Collections model,
-  Collection Editor role, "over 86 million articles and article records" available to add.
-- **S13** — https://api.crossref.org/prefixes/10.14293/works?filter=type:posted-content&query.bibliographic=algorithm+software+network
-  · retrieved 2026-09-01 [API] · the computing titles listed in §6.
-- **S14** — user-agent matrix probe against https://www.scienceopen.com/ , 2026-09-01 [WEB] ·
-  HTTP 403 with Cloudflare `Just a moment…` body for default curl, Chrome 131, WhatsApp/2.23.20.0,
-  ChatGPT-User/1.0, ClaudeBot/1.0 and Linux Chrome 125 UAs.
-- **S15** — https://www.scienceopen.com/robots.txt · retrieved 2026-09-01 [DOC] · the only
-  scriptable-client-accessible resource on the domain; sitemap list, `Crawl-delay: 10`, Cloudflare
-  content signals, per-agent blocks, disallowed paths.
diff --git a/research/preprint-repositories/social-sciences-and-humanities.md b/research/preprint-repositories/social-sciences-and-humanities.md
deleted file mode 100644
index f0a699c..0000000
--- a/research/preprint-repositories/social-sciences-and-humanities.md
+++ /dev/null
@@ -1,505 +0,0 @@
-# Social science and humanities preprint servers — grouped record
-
-- **Compiled:** 2026-09-01 · **All reachability and count probes run:** 2026-09-01 / 2026-09-02 UTC
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Scope note — why these are here at all.** This knowledge base is about hardware,
-> software and systems. Most of the servers below have **no electronics or systems
-> content**, and the user's instruction was explicit: group them, document them simply,
-> and let a measured table carry the weight rather than prose. That is what this file does.
->
-> **Four entries are flagged for slightly deeper treatment**, because there is a real
-> computing connection:
-> - **[Rutgers Optimality Archive](#16-rutgers-optimality-archive-roa)** and
->   **[LingBuzz](#15-lingbuzz)** — computational linguistics, formal grammar, phonology and
->   Optimality Theory: part of NLP's intellectual prehistory. They are also the two most
->   instructive **software-durability case studies** in this entire directory. RoA has run
->   continuously since **1993**.
-> - **[PhilSci-Archive](#14-philsci-archive)** and **[PhilArchive](#13-philarchive)** —
->   philosophy of computation, philosophy of AI, AI ethics. PhilSci-Archive runs on
->   **EPrints** at the University of Pittsburgh.
-> - **[MetaArXiv](#11-metaarxiv)** — metascience. More relevant than it looks: this is where
->   research-software reproducibility and open-science-tooling work is deposited.
->
-> **E-LIS and LISSA are covered elsewhere and are deliberately omitted here.**
-
-## 0. Method, and the OSF status trap
-
-Sixteen of the servers in this file are or were hosted by the **Center for Open Science
-(COS)** on the OSF preprints platform. OSF web pages are a JavaScript single-page app:
-
-> **`https://osf.io/preprints/<anything>` returns HTTP 200 and an identical 4,207-byte
-> shell even for providers that do not exist.** Status code and byte size are worthless
-> signals on that host.
-
-Confirmed here as a live negative control: `https://osf.io/preprints/eyexiv/` returned
-**HTTP 200, 4,207 bytes** on 2026-09-02, while the authoritative provider list at
-`https://api.osf.io/v2/preprint_providers/?page[size]=100` contains **no `eyexiv` entry at
-all** (S1) [API]. Every OSF figure below therefore comes from
-`https://api.osf.io/v2/preprints/?filter[provider]=<slug>` → `links.meta.total`, and every
-status claim from `https://api.osf.io/v2/preprint_providers/<slug>/` →
-`attributes.allow_submissions` and `attributes.description`, which carries the operator's
-own closure notice (S2) [API] [DOC].
-
-**Negative control on the count endpoint:** `filter[provider]=bogusprovider12345` returned
-`total = 0`, not an error (S2) [API] — so a non-zero total is meaningful, but a zero is
-ambiguous.
-
-The OSF provider list contained **32 providers** on 2026-09-02 (S1) [API].
-
-Web reachability used the `AGENTS.md` UA ladder: default `curl` → Chrome 131 →
-WhatsApp/2.23.20.0 → ChatGPT-User/1.0 → ClaudeBot/1.0.
-
-## 1. Status and size table
-
-| Server | URL probed 2026-09-02 | Operator | Launched | Status 2026-09-02 | Records | Source of count |
-|---|---|---|---|---|---|---|
-| **SocArXiv** | `osf.io/preprints/socarxiv` · `socopen.org` | Center for Open Science | 2016 (S3) | **ALIVE**, submissions open, pre-moderation | **24,670** | OSF API [API] |
-| **PsyArXiv** | `psyarxiv.com` → `osf.io/preprints/psyarxiv` | Society for the Improvement of Psychological Science (SIPS) + COS | 2016 (S3) | **ALIVE**, submissions open, pre-moderation — **still on OSF** | **63,368** | OSF API [API] |
-| **EdArXiv** | `edarxiv.org` → `osf.io/preprints/edarxiv` | COS | 2019 (S3) | **ALIVE**, submissions open | **3,506** | OSF API [API] |
-| **APSA Preprints** | `preprints.apsanet.org` | American Political Science Association + Cambridge University Press | 2019 (S3) | **ALIVE** | **1,326** | Cambridge Engage public API [API] |
-| **LawArXiv** | `osf.io/preprints/lawarxiv` | COS | 2017–2020 | **CLOSED**, content retained | **165** | OSF API [API] |
-| ↳ successor **Law Archive** | `osf.io/preprints/lawarchive` | COS | — | **ALIVE**, submissions open | **1,664** | OSF API [API] |
-| ↳ old domain | `lawarxiv.org` | — | — | **DOMAIN LOST** — 114-byte parking redirect to `/lander` | — | probe [WEB] |
-| **CrimRxiv** | `crimrxiv.com` | University of Manchester, on **PubPub** | 2020 (S3) | **ALIVE** — but Cloudflare-blocked to most agents | **not verified** | see §8 |
-| **MediArXiv** | `mediarxiv.com` · `osf.io/preprints/mediarxiv` | COS | 2019 (S3) | **ALIVE**, submissions open | **443** | OSF API [API] |
-| ↳ old domain | `mediarxiv.org` | — | — | **DOMAIN LOST** — redirects to unrelated `afterdispatch.com` | — | probe [WEB] |
-| **BodoArXiv** | `osf.io/preprints/bodoarxiv` | ScholarlyHub + COS (S3) | 2019 (S3) | **ALIVE**, submissions open | **165** | OSF API [API] |
-| ↳ vanity domain | `bodoarxiv.org` | — | — | **DOMAIN HIJACKED** — now an online-casino page | — | probe [WEB] |
-| **hprints** | `hprints.hal.science` · HAL API | CCSD (CNRS) / Nordbib | 2008 (S3) | **ALIVE** — HAL infrastructure | **397** | HAL API [API] |
-| **MetaArXiv** | `osf.io/preprints/metaarxiv` | BITSS, UC Berkeley + COS | 2018 (S3) | **ALIVE**, submissions open | **1,014** | OSF API [API] |
-| **MindRxiv** | `mindrxiv.org` → `osf.io/preprints/mindrxiv` | COS + Mind & Life Institute | 2018 (S3) | **FROZEN** — submissions closed, content retained | **288** | OSF API [API] |
-| **PhilArchive** | `philarchive.org` | PhilPapers Foundation; developed and operated by the **Centre for Digital Philosophy, Western University** | 2009 (S3) | **ALIVE** | **143,707 works** across **6,155 topics** | operator's own front page [WEB] |
-| **PhilSci-Archive** | `philsci-archive.pitt.edu` | University of Pittsburgh (D-Scribe Digital Publishing) | 2001 (S3) | **ALIVE** — **EPrints 3.3.15** | **12,586** | sum of operator's browse-by-year [WEB] |
-| **LingBuzz** | `lingbuzz.net` (= `ling.auf.net/lingbuzz`) | Michal Starke (Univ. of Tromsø) | ~2004 (S3) | **ALIVE** | **≥9,200** (highest live ID between 009200 and 009300) | ID probing [API] |
-| **RoA** | `roa.rutgers.edu` | Rutgers School of Arts and Sciences | **1993** (S3, S9) | **ALIVE but not accepting new deposits since 2022** | operator says **"ca. 1400 … 1993–2022"**; operator's XLSX export has **1,463 rows** | operator front page + export [WEB] [API] |
-
-**Conflicts recorded, not resolved.** Wikipedia's size buckets (S3) put SocArXiv and
-PsyArXiv at `>10,000`, PhilArchive and PhilSci-Archive at `>10,000`, LingBuzz at `>10,000`,
-and RoA at `>1,000`. The measured OSF/operator numbers above are all consistent with those
-buckets except **LingBuzz**, where my ID-space probe supports ~9.2k rather than >10k — but
-ID probing measures the *identifier space*, not live records, so treat both as approximate.
-
-## 2. What the probe evidence shows
-
-Three findings are worth more than the individual entries.
-
-**(a) The OSF content survives; the vanity domain does not.** Every closed or frozen
-server in this file still serves its full content from OSF, with DOIs, years after
-shutdown. What breaks is the branded domain the community was told to use:
-
-| Vanity domain | State on 2026-09-02 | Content still readable? |
-|---|---|---|
-| `lawarxiv.org` | 114-byte domain-parking stub redirecting to `/lander` | Yes — OSF, 165 records |
-| `mediarxiv.org` | redirects to `afterdispatch.com`, an unrelated site | Yes — OSF, 443 records, and `mediarxiv.com` still works |
-| `bodoarxiv.org` | **"Mostbet Bangladesh — Online Casino & Sports Betting"** | Yes — OSF, 165 records |
-
-**(b) An operator's own signposting can point at a hijacked domain.** BodoArXiv's OSF
-provider description — served live by the Center for Open Science on 2026-09-02 — reads
-*"Open Repository for Medieval Studies **Visit BodoArXiv.org** to learn more"* (S2) [DOC].
-That domain is now a gambling site. The medieval-studies community's own project blog
-survives separately at `bodoarxiv.wordpress.com` (HTTP 200, 65,449 bytes) [WEB]. **Do not
-trust a repository's own "visit our website" link as evidence the website is still theirs.**
-
-**(c) PsyArXiv did *not* leave OSF — correcting a common belief.** The OSF API on
-2026-09-02 lists `psyarxiv` with `allow_submissions = true`, `reviews_workflow =
-pre-moderation`, `domain = https://psyarxiv.com/`, and a description naming SIPS as
-maintainer (S2) [API] [DOC]. `psyarxiv.com` returns HTTP 200 and redirects to
-`https://osf.io/preprints/psyarxiv/`. What happened is a **platform-side URL
-consolidation**: OSF retired branded per-provider front doors in favour of
-`osf.io/preprints/<slug>` paths, and the custom domains became redirects. The *service* did
-not migrate; the *URL* did. At 63,368 records it is by a wide margin the largest server in
-this file. **Exact date of the URL consolidation: [NOT-VERIFIED]** — I could not find a
-dated COS announcement.
-
----
-
-## 3. SocArXiv
-
-- `osf.io/preprints/socarxiv` · blog at `socopen.org` (HTTP 200, 82,394 B) · COS · 2016 ·
-  **ALIVE** · **24,670 records** [API]
-
-Founded as an explicitly political alternative to SSRN after Elsevier acquired it. Runs
-pre-moderation: the OSF description says *"SocArXiv papers are moderated before appearing.
-Please read the moderation policy before submitting"* (S2) [DOC]. Moderation is a
-scope-and-plausibility screen, not peer review — a deposit here guarantees a timestamp, a
-DOI and that a human glanced at it, nothing more. **Computing content: negligible.**
-
-## 4. PsyArXiv
-
-- `psyarxiv.com` → `osf.io/preprints/psyarxiv` · SIPS + COS · 2016 · **ALIVE** ·
-  **63,368 records** [API]
-
-See §2(c) — it is still on OSF. Pre-moderated. The largest single-discipline social-science
-preprint server measured in this directory. Relevant to systems work only obliquely: it is
-the main venue for the psychology replication-crisis literature, which is the sociological
-origin of the reproducibility norms that MetaArXiv (§11) formalises. **Computing content:
-negligible**, beyond method/statistics tooling papers.
-
-## 5. EdArXiv
-
-- `edarxiv.org` → `osf.io/preprints/edarxiv` · COS · 2019 · **ALIVE** · **3,506 records** [API]
-
-Education research. Submissions open, pre-moderation. Vanity domain still redirects
-correctly — one of the few in this file that does. **Computing content: negligible**
-(occasional educational-technology and CS-education work; not enumerated here).
-
-## 6. APSA Preprints
-
-- `preprints.apsanet.org` · American Political Science Association + **Cambridge University
-  Press** · 2019 · **ALIVE** · **1,326 items** [API]
-
-The only server in this file on a **commercial publisher's platform** — Cambridge Open
-Engage, which is the same ChemRxiv-derived Atypon/Engage stack. That has a concrete
-consequence for retrieval: it exposes a genuinely open REST API,
-`/engage/apsa/public-api/v1/items`, which returned `totalCount: 1326` with full item records
-on 2026-09-02 (S4) [API]. DOIs are minted under Cambridge's prefix **10.33774** (the
-`apsa-` namespace; the prefix as a whole held 5,720 works across all Engage servers on
-2026-09-02) (S5) [API]. **Computing content: negligible.**
-
-Durability read: publisher-operated is a mixed signal. It is well-run and well-funded
-*while the publisher wants it* — and PeerJ Preprints and Nature Precedings show what
-happens when a publisher stops wanting it (see
-[closed-and-defunct-servers.md](closed-and-defunct-servers.md)).
-
-## 7. LawArXiv / Law Archive
-
-- LawArXiv `osf.io/preprints/lawarxiv` · COS · **2017–2020, CLOSED** · **165 records
-  retained** [API]
-- Law Archive `osf.io/preprints/lawarchive` · COS · **ALIVE**, pre-moderation ·
-  **1,664 records** [API]
-
-**What happened to the content: nothing bad.** The OSF provider record for `lawarxiv` says,
-verbatim, *"LawArXiv is no longer able to accept new submissions. Thank you to everyone who
-contributed their work to this repository. Existing content in LawArXiv will remain
-accessible…"* (S2) [DOC], and the API confirms 165 preprints are still served. A successor,
-**Law Archive**, runs on the same platform and is nearly ten times larger.
-
-**What did break: `lawarxiv.org`.** On 2026-09-02 it returned a **114-byte** page whose
-entire body is `<script>window.onload=function(){window.location.href="/lander"}</script>`
-— the signature of a lapsed domain sitting on a parking service [WEB]. A reader following a
-2019 citation to `lawarxiv.org` finds a parking page; the same paper is one API call away on
-OSF. **This is the single most compressible lesson in this file: cite the DOI.**
-
-## 8. CrimRxiv
-
-- `crimrxiv.com` · University of Manchester · 2020 (S3) · runs on **PubPub** ·
-  **ALIVE** · **count [NOT-VERIFIED]**
-
-Criminology's open archive, and the only server in this file on **PubPub** — the
-MIT-Press-originated, open-source community publishing platform. That is a genuine
-technical distinction: PubPub is a full CMS with versioning and inline annotation rather
-than a deposit-and-serve repository, and it gives each community a **shared DOI prefix**
-(`10.21428`, registered to *PubPub*), so DOI-prefix counting cannot isolate CrimRxiv. The
-whole prefix held **13,852 works** on 2026-09-02, spanning unrelated publishers including
-Vanderbilt University conference proceedings (S5) [API].
-
-**Retrieval is hostile.** `https://www.crimrxiv.com/` returned **HTTP 403 on all five
-user-agents** in the ladder; so did `crimrxiv.pubpub.org` and `www.crimrxiv.com/pub/`. The
-**apex domain without `www`** succeeded exactly once, under the **WhatsApp/2.23.20.0**
-user-agent, returning a 1,029,205-byte page — and three subsequent identical requests
-returned Cloudflare's 5,578-byte "Just a moment…" interstitial [WEB]. This is
-**intermittent Cloudflare bot-management, not a stable UA whitelist**, and I did not obtain
-a record count from it. `mcp_fff`/scripted access to CrimRxiv should be assumed unreliable.
-
-**Computing content: negligible**, beyond computational criminology and predictive-policing
-critique.
-
-## 9. MediArXiv
-
-- `mediarxiv.com` (**not** `.org`) · `osf.io/preprints/mediarxiv` · COS · 2019 · **ALIVE**,
-  submissions open · **443 records** [API]
-
-Media, film and communication studies. Small but genuinely live. Its interest here is
-entirely the **domain split**: the OSF description says *"Visit mediarxiv.com for more
-information"* (S2) [DOC] and `mediarxiv.com` does work (HTTP 200, 153,238 B, title
-*"MediArXiv | The Open Archive for Media, Film, and Communication Studies"*), while
-`mediarxiv.org` now redirects to `afterdispatch.com`, an unrelated site with an empty
-`<title>` [WEB]. One character of TLD separates the live archive from a stranger's domain.
-
-## 10. BodoArXiv
-
-- `osf.io/preprints/bodoarxiv` · ScholarlyHub + COS (S3) · 2019 · **ALIVE**, submissions
-  open · **165 records** [API]
-
-Medieval studies — manuscript studies, palaeography, medieval Latin. Notable for having
-been a **ScholarlyHub** initiative, i.e. one of the few servers here born from a
-scholar-owned-infrastructure movement rather than from COS or a publisher.
-
-**The cautionary finding is §2(b): `bodoarxiv.org` is now an online-casino page** ("Mostbet
-Bangladesh"), and the operator's own OSF description still tells readers to go there
-[WEB] [DOC]. The project's surviving non-OSF presence is `bodoarxiv.wordpress.com`. Cite the
-OSF DOI. **Computing content: none.**
-
-## 11. MetaArXiv
-
-- `osf.io/preprints/metaarxiv` · **BITSS — Berkeley Initiative for Transparency in the
-  Social Sciences** + COS · 2018 · **ALIVE**, pre-moderation · **1,014 records** [API]
-
-**Flagged as more relevant than it looks.** The OSF description is explicit: *"An
-interdisciplinary archive of articles focused on improving research transparency and
-reproducibility. Maintained by The Berkeley Initiative for Transparency in the Social
-Sciences (BITSS)"* (S2) [DOC].
-
-Why a hardware/software knowledge base should care: **reproducibility is a software
-problem** and much of the literature that defines it lands here rather than in CS venues —
-preregistration and registered-report mechanics, computational-workflow and
-container-based reproducibility, code- and data-availability-policy audits, research-software
-sustainability, and meta-analysis of open-science tooling adoption. If you are looking for
-the empirical evidence base behind "ship the container, pin the versions, publish the
-analysis code", MetaArXiv is one of the places it is deposited. At 1,014 records it is
-small enough to browse exhaustively.
-
-Caveat: it is pre-moderated but **not peer-reviewed**, and metascience preprints are
-frequently cited in policy argument long before review. Check for a journal version.
-
-## 12. MindRxiv
-
-- `mindrxiv.org` → `osf.io/preprints/mindrxiv` · COS + Mind & Life Institute · 2018 ·
-  **FROZEN** · **288 records** [API]
-
-Mind and contemplative-practice research. Closed to new submissions; the OSF description
-states *"MindRxiv is no longer able to accept new submissions. Existing content will remain
-accessible as part of the Center for Open Science and Mind & Life's ongoing
-commitment…"* (S2) [DOC]. The vanity domain still redirects correctly to OSF — a rare
-well-behaved shutdown. **Computing content: none.**
-
-## 13. PhilArchive
-
-- `philarchive.org` · PhilPapers Foundation; **developed and operated by the Centre for
-  Digital Philosophy, Western University** · 2009 (as the PhilPapers Archive) · **ALIVE** ·
-  **143,707 works**, **6,155 topics** [WEB]
-
-**Flagged: philosophy of computing and AI ethics.** PhilArchive is the deposit arm of
-PhilPapers, and inherits PhilPapers' unusually fine-grained subject taxonomy. Its top-level
-category list, retrieved 2026-09-02, includes **"Philosophy of Computing and Information"**
-as a first-class sibling of philosophy of physics and philosophy of biology, alongside
-**Philosophy of Cognitive Science**, **Logic and Philosophy of Logic**, **Formal Sciences**
-and **Philosophy of Mind** (S6) [WEB]. Between those categories sits essentially the whole
-analytic literature on computation, machine consciousness, AI alignment and machine ethics.
-
-It is by a very large margin the biggest archive in this file — larger than every other
-entry combined. Retrieval is straightforward: it exposes **OAI-PMH 2.0 at
-`https://philarchive.org/oai.pl`**, with `earliestDatestamp 2008-01-01`,
-`deletedRecord: transient` and deflate compression advertised (S7) [API]. Access note: the
-HTML front page **403s under a bare `curl` UA and succeeds under Chrome 131**; the OAI
-endpoint behaves the same way.
-
-**Editorial gate:** none in the peer-review sense. The site states *"PhilArchive consists
-entirely of articles submitted by users"* [WEB], with per-item peer-review-status tags
-declared by the depositor. Treat a PhilArchive item as self-archived unless the tag says
-otherwise.
-
-## 14. PhilSci-Archive
-
-- `philsci-archive.pitt.edu` · **University of Pittsburgh**, D-Scribe Digital Publishing ·
-  **2001** · **ALIVE** · **12,586 records** [WEB]
-
-**Flagged: philosophy of science, including philosophy of computation and AI.** Founded
-2001 and still running on the same institutional footing 25 years later, which makes it one
-of the more durable services documented anywhere in this directory.
-
-**Software: EPrints 3.3.15**, declared in the page's own `generator` meta tag on 2026-09-02
-(S8) [WEB]. EPrints is the University of Southampton's Perl repository platform, first
-released in 2000 — the same lineage as CogPrints (see
-[closed-and-defunct-servers.md](closed-and-defunct-servers.md)), and a useful contrast:
-identical software, one survived because a university library kept operating it and one did
-not.
-
-**Size, and a metadata caveat worth noting.** Summing the operator's own browse-by-year
-index across **51 year buckets spanning 1926–2027** gives **12,586 records** (S8) [WEB].
-The distribution is informative: ~638 for 2026 and 789 for 2025 against 175 for 2003 — the
-archive is growing, not coasting. The buckets are *work* dates, not deposit dates: 1926,
-1956, 1958 and 1962 each hold one item. Independently, OAI-PMH `Identify` reports
-`earliestDatestamp 2010-10-07`, `deletedRecord: persistent`, `adminEmail
-philsciarchive@groups.pitt.edu` (S8) [API] — i.e. the OAI datestamps begin at a 2010
-platform migration and **cannot** be used to date the archive's founding. Conflict recorded.
-
-`ListIdentifiers` paginates 100 at a time with a `resumptionToken` that carries **no
-`completeListSize`**, so a full harvest is required for an exact figure — that is why the
-count above comes from the browse index rather than the API.
-
-The archive also hosts the **PhilMath Archive** as a sub-collection, and browse views for
-open-access journals and books.
-
-## 15. LingBuzz
-
-- `lingbuzz.net` (identical content at `ling.auf.net/lingbuzz`) · **run and hosted
-  personally by Michal Starke** · ~2004 · **ALIVE** · **≥9,200 deposits** [API]
-
-**Flagged: computational linguistics and formal grammar.** LingBuzz is the de-facto
-preprint venue for theoretical syntax, semantics, phonology and morphology. Its front page
-on 2026-09-02 states plainly: *"LingBuzz is run and hosted by Michal Starke"* [WEB]. That
-sentence is the entire governance model.
-
-**Why a systems reader should care — the minimalism is the point.** LingBuzz is a
-hand-written application behind `nginx/1.14.2` with essentially no modern repository
-furniture, and it has outlived roughly half the professionally-run servers in this
-directory. Measured characteristics, all 2026-09-02:
-
-- **Flat sequential identifiers.** `lingbuzz/000100` is Noam Chomsky, *"Three factors in
-  Language Design"*, June 2004 — which both dates the archive and shows the numbering has
-  never been rebased. Live IDs confirmed at 000100, 004000, 008000, 008500, 008800, 009000,
-  009100, 009110, 009120, 009150, 009200 [API].
-- **No 404 handling.** IDs above the live range (009300, 009400, 009450, 009470, 009480,
-  009490, 009999) all return **HTTP 502 Bad Gateway from nginx/1.14.2**, i.e. the backend
-  process dies rather than returning "not found" [API]. This is a *useful* negative control
-  — 502 means "past the end", 200 means "exists" — but it is not what a maintained
-  repository stack does.
-- **No HEAD support.** `curl -I https://lingbuzz.net/` returns *"Empty reply from server"*
-  [API].
-- **No DOIs, no OAI-PMH, no versioned identifiers**, no formal preservation arrangement
-  that I could find. **[NOT-VERIFIED]:** whether any dark archive holds LingBuzz content.
-- **nginx 1.14.2** is the Debian 10 "buster" stock package, out of upstream support.
-
-**The durability lesson, stated honestly.** LingBuzz demonstrates that a single motivated
-maintainer with a flat file store can outlast institutions — and simultaneously that this
-model has **exactly one point of failure**, with no succession plan and no dark archive.
-Compare `bodoarxiv.org` (§10): the difference between LingBuzz and a casino page is one
-person continuing to renew a domain. Content here is AI-adjacent in places — ID 008000 is
-*"Speaking_Brains: Recent Papers on AI Neuro"* — but **do not cite LingBuzz as a durable
-locus**; find the DOI'd version or archive the PDF yourself.
-
-## 16. Rutgers Optimality Archive (RoA)
-
-- `roa.rutgers.edu` · Rutgers University **School of Arts and Sciences** · **1993** ·
-  **ALIVE but not accepting new deposits** · operator says **"ca. 1400 papers uploaded from
-  1993–2022"**; operator's own XLSX export contains **1,463 rows** [WEB] [API]
-
-**Flagged, and the most historically important entry in this file.** RoA is the
-distribution point for Optimality Theory — Prince & Smolensky's constraint-ranking framework,
-which is *the* bridge between generative phonology and constraint-satisfaction computation,
-and a direct ancestor of the optimisation framing that pervades computational linguistics.
-It began the same year as the first web browsers and **two years after arXiv**.
-
-**Its self-documented systems history is a genuine artefact.** The archive's own `info.html`,
-retrieved 2026-09-02, records the full 30-year operational lineage in one paragraph (S9)
-[DOC] — reproduced here because nothing else in this directory is comparable:
-
-- **1993** — begins as *"a command-line anonymous ftp server constructed by Alan Prince"*.
-- **1996** — a web interface added *"with the help of Mike Strickland (then a high-energy
-  graduate student, now a high-energy physicist), who wrote the original search, delivery,
-  and upload scripts."*
-- **2000–2014** — day-to-day management by Eric Bakovic. Files held *"in the server-cluster
-  of the Rutgers University Cognitive Science Center (RuCCS)"*, scripts hosted by
-  **webslingerZ**, a commercial provider.
-- **2001** — first major overhaul, *"spurred on by difficulties in the RuCCS system"*.
-- **2002** — hardware replaced. **2003** — software rewritten by Paul de Lacy.
-- **2011** — *"A mild hacking incursion … forced the temporary shutdown of the Archive. It
-  was replaced for a year with an html-only site that kept all files available and allowed
-  upload via email request."*
-- **2012** — rewritten again and moved onto Rutgers SAS's secure servers, where it still is.
-- **Today** — Administrator Natalie DelBusso, consultant Eric Bakovic, and Alan Prince
-  credited as *"Capo di tutti i capi"*.
-
-**Read that 2011 line again.** Compromised, and the recovery was *to fall back to static
-HTML that kept every file downloadable and accept submissions by email for a year*. That is
-the correct failure mode for an archive, and it is the opposite of what happened to
-`lawarxiv.org` or `bodoarxiv.org`. RoA survived three rewrites, a hardware replacement, a
-hosting-provider change, an intrusion and four administrators, because at every step the
-**files stayed served**.
-
-**Measured state, 2026-09-02:**
-
-- `Server: Apache`; the index page's `Last-Modified` is **2024-10-17**, while the newest
-  paper listed is **ROA 1394, April 2022** [API]. Maintained, but not ingesting.
-- Full text verified live: `content/article/files/1922_hideo_kobayashi_1.pdf` downloads as a
-  **837,797-byte, 20-page PDF 1.7** [API].
-- **The "API" is a spreadsheet.** `article/ROA.xlsx` is a 320,860-byte XLSX offered on the
-  front page as *"a fully linked Excel table suitable for search and annotation"*; it parses
-  to **1,463 rows** [API]. There is no OAI-PMH, no REST API and no DOI minting.
-- Front-page self-description: *"ROA contains ca. 1400 papers uploaded from 1993-2022"* [WEB].
-  Wikipedia's bucket is `>1,000` (S3). Conflict recorded; all three figures are consistent
-  in magnitude.
-
-**Durability verdict.** RoA is the best argument in this directory for the thesis that
-**simplicity, an institutional host and a bulk export beat features**. Static files under
-Apache at a university, plus a downloadable manifest of the entire holdings, is a design a
-future archivist can rescue. Its risk is not technical — it is that nobody has committed to
-operating it now that deposits have stopped, and there is **no named dark archive**
-[NOT-VERIFIED].
-
-## 17. hprints
-
-- `hprints.hal.science` · **CCSD (CNRS)** with Nordbib funding · 2008 (S3) · **ALIVE** ·
-  **397 records** [API]
-
-The Nordic arts, humanities and social sciences open archive. Its only structural interest
-is that it is **not an independent server at all**: it is a *portal view* onto **HAL**, the
-French national repository. See [hal.md](hal.md) for the platform, the OAI-PMH and Solr
-APIs, deposit moderation and preservation arrangements — all of which hprints inherits, and
-which is why an archive with fewer than 400 records has better durability guarantees than
-several servers here that are twenty times larger.
-
-**Retrieval note, 2026-09-02.** `hprints.org` is **DNS NXDOMAIN** on all five user-agents —
-the original front door is gone [WEB]. `hprints.hal.science` returns HTTP 200 but serves an
-**Anubis proof-of-work anti-scraper interstitial** ("Making sure you're not a bot!… This
-website is running Anubis version devel") to non-JavaScript clients [WEB]. The **API is
-unaffected**: `https://api.archives-ouvertes.fr/search/hprints/?q=*:*&rows=0&wt=json`
-returned `numFound: 397` immediately with a plain `curl` (S10) [API]. This is a clean
-example of a pattern worth internalising — *when the HTML is defended, the machine interface
-usually is not*.
-
-## 18. Access, APIs and bulk retrieval — summary
-
-| Server(s) | Machine interface | Works from scripts? |
-|---|---|---|
-| All OSF-hosted (SocArXiv, PsyArXiv, EdArXiv, LawArXiv/Law Archive, MediArXiv, BodoArXiv, MetaArXiv, MindRxiv) | JSON:API at `api.osf.io/v2/` | **Yes** — plain `curl`, no key. Use `filter[provider]=` + `links.meta.total`. URL-encode the brackets (`%5B`/`%5D`) or the shell will eat them. |
-| APSA Preprints | `preprints.apsanet.org/engage/apsa/public-api/v1/items` | **Yes** — plain `curl`, returns `totalCount` + full records |
-| PhilArchive | OAI-PMH at `philarchive.org/oai.pl` | **Yes**, but needs a browser UA |
-| PhilSci-Archive | OAI-PMH at `philsci-archive.pitt.edu/cgi/oai2` | **Yes** with default `curl`; **blocked (BIG-IP ASM captcha) under a Chrome UA** — the ladder runs *backwards* here. No `completeListSize`. |
-| hprints | HAL Solr API `api.archives-ouvertes.fr/search/hprints/` | **Yes** — HTML front end is behind Anubis PoW |
-| RoA | none — but a complete **XLSX manifest** at `article/ROA.xlsx` | **Yes**, effectively |
-| LingBuzz | none; sequential IDs, 502 past the end, no HEAD | Scrape-only |
-| CrimRxiv | PubPub; no isolable DOI prefix | **No** — Cloudflare 403, intermittent |
-
-**Negative controls used:** `filter[provider]=bogusprovider12345` → `total: 0`;
-`osf.io/preprints/eyexiv/` → HTTP 200 / 4,207 B for a provider absent from the API list;
-`lingbuzz/009999` → HTTP 502.
-
-## 19. Sources
-
-- **S1** — OSF preprint-provider list. `https://api.osf.io/v2/preprint_providers/?page[size]=100`
-  · retrieved 2026-09-02 · authoritative list of 32 providers, with `domain` and
-  `allow_submissions` per provider. [API]
-- **S2** — OSF preprint counts and provider records.
-  `https://api.osf.io/v2/preprints/?filter[provider]=<slug>&page[size]=1` (`links.meta.total`)
-  and `https://api.osf.io/v2/preprint_providers/<slug>/` (`attributes.description`,
-  `allow_submissions`, `reviews_workflow`) · retrieved 2026-09-02 · every OSF count and every
-  operator closure notice quoted above. [API] [DOC]
-- **S3** — Wikipedia, *List of preprint repositories*.
-  `https://en.wikipedia.org/wiki/List_of_preprint_repositories` · retrieved 2026-09-02 ·
-  launch years, operators and order-of-magnitude size buckets. Used only where no
-  first-party source was obtainable, and always flagged. [COM]
-- **S4** — APSA Preprints public API.
-  `https://preprints.apsanet.org/engage/apsa/public-api/v1/items?limit=1` · retrieved
-  2026-09-02 · `totalCount: 1326`. [API]
-- **S5** — Crossref REST API. `https://api.crossref.org/prefixes/<prefix>` and
-  `/prefixes/<prefix>/works?rows=0` · retrieved 2026-09-02 · prefix ownership (10.33774 →
-  Cambridge University Press; 10.21428 → PubPub) and prefix-wide work counts. [API]
-- **S6** — PhilArchive front page. `https://philarchive.org/` (Chrome 131 UA) · retrieved
-  2026-09-02 · "There are currently 143,707 works in the archive. These works fall under
-  6,155 topics"; operator statement naming the Centre for Digital Philosophy, Western
-  University; full top-level category list including *Philosophy of Computing and
-  Information*. [WEB]
-- **S7** — PhilArchive OAI-PMH. `https://philarchive.org/oai.pl?verb=Identify` · retrieved
-  2026-09-02 · `earliestDatestamp 2008-01-01`, `deletedRecord: transient`. [API]
-- **S8** — PhilSci-Archive. `https://philsci-archive.pitt.edu/` (generator meta tag:
-  `EPrints 3.3.15`), `https://philsci-archive.pitt.edu/view/year/` (51 year buckets, sum
-  12,586), `https://philsci-archive.pitt.edu/cgi/oai2?verb=Identify` (earliestDatestamp
-  2010-10-07, adminEmail `philsciarchive@groups.pitt.edu`) · all retrieved 2026-09-02.
-  [WEB] [API]
-- **S9** — Rutgers Optimality Archive. `https://roa.rutgers.edu/` (front page: "ca. 1400
-  papers uploaded from 1993-2022"; newest ROA 1394, Apr/2022) and
-  `https://roa.rutgers.edu/static/info.html` (full operational history 1993–2012, named
-  staff, the 2011 intrusion, the RuCCS/webslingerZ/SAS hosting chain) ·
-  `https://roa.rutgers.edu/article/ROA.xlsx` (320,860 B, 1,463 rows) · retrieved 2026-09-02.
-  [WEB] [DOC] [API]
-- **S10** — HAL search API. `https://api.archives-ouvertes.fr/search/hprints/?q=*:*&rows=0&wt=json`
-  · retrieved 2026-09-02 · `numFound: 397`. [API]
-- **S11** — Reachability probes. Raw log in
-  `doc/hardware/scratch/preprint-repositories/humanities/` and the directory-wide
-  `scratch/preprint-repositories/reachability-2026-09-01.txt` · run 2026-09-01/02 with the
-  `AGENTS.md` UA ladder. Supports every `lawarxiv.org`, `mediarxiv.org`, `bodoarxiv.org`,
-  `hprints.org`, `crimrxiv.com` and `lingbuzz.net` status claim. [WEB]
diff --git a/research/preprint-repositories/ssrn.md b/research/preprint-repositories/ssrn.md
deleted file mode 100644
index b2b253c..0000000
--- a/research/preprint-repositories/ssrn.md
+++ /dev/null
@@ -1,721 +0,0 @@
-# SSRN — preprint repository record
-
-- **URL:** https://www.ssrn.com/ (browse/landing) · https://papers.ssrn.com/ (abstracts,
-  full text — **returns HTTP 403 to every scripted client**, §8)
-- **Operator:** **Elsevier** (RELX plc). Acquired from Social Science Electronic Publishing
-  Inc. in **May 2016** (S9, S10). Every page footer reads "Copyright © 2026 Elsevier Inc.,
-  its licensors, and contributors" (S2) [WEB].
-- **Discipline scope:** advertised as **69 disciplines** across six top-level areas —
-  applied, health, humanities, life, physical and social sciences (S1) [WEB]. *As actually
-  used*: overwhelmingly economics, law, finance and political science; **the Economics
-  Research Network alone holds 694,156 papers** against 108,252 in the Computer Science
-  Research Network (S3) [API].
-- **Launched:** **1994**, by financial economists **Michael C. Jensen** and **Wayne Marr**
-  (S10) [LIT/COM].
-- **Status:** active, large, growing.
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **This record folds in two Wikipedia entries.** *Preprints with The Lancet* and *Cell
-> Sneak Peek* are listed by Wikipedia as separate repositories. They are **not**. Both are
-> SSRN **First Look** channels running on SSRN infrastructure — verified below with SSRN's
-> own participant list and live counts (§3.3). Wikipedia's ">1,000" for each is wrong by
-> more than an order of magnitude in both cases.
-
----
-
-## 1. What it is
-
-SSRN began in 1994 as the **Social Science Research Network**, an email-distribution service
-for economics and finance working papers. That origin explains almost everything about its
-present shape. In economics and law, the *working paper* — circulated, cited and often
-career-decisive years before any journal touches it — is the primary unit of scholarly
-communication, not a stopgap. SSRN industrialised that habit.
-
-The architecture is a **network of networks**. Papers are not filed into a subject tree;
-they are *distributed* to subscriber lists. An author submits once; SSRN classifies the
-paper into one or more **Research Networks** (68 of them), and within each network into one
-or more **eJournals** (subject-area alert feeds). Subscribers get email digests. In SSRN's
-own words, this is the differentiator: "While many preprint servers operate as content
-repositories, SSRN maximizes usage and discoverability by classifying papers into
-topic-based email alerts that are distributed to subscribers. This results in downloads and
-citations that SSRN aggregates into meaningful metrics that authors use for promotion and
-tenure purposes and that institutions use in their hiring and ranking activities." (S6)
-[DOC].
-
-Read that last sentence carefully. SSRN is explicit that its product is **metrics for
-career advancement**, not just archiving. The download counter is the point. This is why
-SSRN top-ten download lists appear on law-school faculty pages, and it is also why SSRN's
-incentive structure differs sharply from arXiv's.
-
-Since **May 2016** SSRN has been owned by **Elsevier** (S9, S10). It sits alongside Mendeley
-and, since then, has been wired into Elsevier's journal workflow: the **First Look**
-programme lets authors post a preprint with one click during submission to a participating
-Elsevier journal (§3.3). SSRN is now, functionally, Elsevier's preprint server — its own
-support hub says so in a headline: *"Welcome to SSRN, Elsevier's Preprint Server"* (S6)
-[DOC].
-
-For this knowledge base the summary is: **SSRN is a genuinely important repository that is
-mostly not about anything you work on**, plus a real cautionary tale about commercial
-ownership of preprint infrastructure (§10).
-
-## 2. Scope and subject taxonomy — the parts that matter here
-
-**Top level:** six discipline groups (Applied / Health / Humanities / Life / Physical /
-Social Sciences) (S1) [WEB].
-
-**Second level:** **68 Research Networks**, enumerated exhaustively from the network
-selector present on every network page (S2) [WEB]. Note the conflict: the homepage counter
-says "**69** Disciplines" (S1); the selector lists **68** (S2). Both retrieved 2026-09-01.
-Recorded, not resolved. Wikipedia's "More than 55 disciplines" (S11) is stale on both
-counts.
-
-**Third level:** **eJournals** — subject-area feeds within each network. These are the real
-categories, closest in function to arXiv's `cs.*` codes, and they are the level at which you
-should search.
-
-**The computing and engineering networks, with their eJournals:**
-
-*Computer Science Research Network* (`compscirn`) — 14 subject eJournals (S4) [API]:
-
-| eJournal | Binding ID | Papers (2026-09-01) |
-|---|---|---|
-| Artificial Intelligence | 3178495 | **56,562** |
-| Applied Computing | 3191581 | 21,443 |
-| Information Systems | 3178509 | 14,160 |
-| Cybersecurity, Privacy, & Networks | 3178533 | 12,247 |
-| Computation Theory | 3176750 | 8,624 |
-| Human-Computer Interaction | 3177962 | 6,310 |
-| **Software Engineering** | 3178522 | **6,122** |
-| Robotics | 3178493 | 5,838 |
-| Computer Science Education | 3216966 | 5,726 |
-| Computing Methodology | 3191574 | 4,253 |
-| High Performance Computing | 3191612 | 2,484 |
-| Other Computer Science Research | 4578131 | 2,300 |
-| Web Technology | 3191618 | 2,105 |
-| Computer Science Negative Results | 3216949 | 541 |
-| **Sum** | | **148,715** |
-
-*Engineering Research Network* (`engrn`) — 15 eJournals (S4) [WEB]: Aerospace, Automotive,
-Bioengineering, Chemical, Civil, Computational Fluid Dynamics, **Electrical Engineering**,
-Energy, Engineering Education, Engineering Negative Results, Environmental, Industrial &
-Manufacturing, Materials, Mechanical, and a hidden "z-Other Engineering Research".
-
-*Information Systems & eBusiness Network* (`isn`) — 9 eJournals including Information
-Technology & Systems, eBusiness & eCommerce, and Emerging Legal Issues in Information
-Systems (S4) [WEB].
-
-*Materials Science Research Network* (`matscirn`) — 13 eJournals including **Electronic,
-Optical & Magnetic Materials**, Computational Materials Science, Nanomaterials, Corrosion
-(S4) [WEB].
-
-Three observations a reader should take away:
-
-1. **"Software Engineering" holds 6,122 papers.** For comparison, arXiv's `cs.SE` is an
-   order of magnitude larger and vastly better known. SSRN is not where software
-   engineering happens.
-2. **"Artificial Intelligence" (56,562) is 38% of the whole CS network** and is the only
-   SSRN computing category with real mass. Much of it is AI-and-*something* —
-   AI-and-law, AI-and-management, AI-and-policy — which is exactly what you would expect
-   from SSRN's social-science centre of gravity. The newest CompSciRN paper on 2026-09-01
-   was *"Should We Allow AI to Police Itself? Assessing the Technical Feasibility and Legal
-   Implications of LLM-Based Agent Evaluation"* by authors at Oxford Saïd Business School
-   and European University Viadrina (S4) [API]. That is the house style.
-3. **The eJournal sums exceed the network totals** (148,715 across CS eJournals vs 108,252
-   in the CS network) because **papers are multiply classified**. See §3.2 — this is the
-   single most important thing to understand before quoting any SSRN number.
-
-## 3. Size and growth
-
-### 3.1 SSRN's own headline counters
-
-From the SSRN homepage, "SSRN by the numbers", retrieved **2026-09-01** (S1) [WEB]:
-
-| Counter | Value |
-|---|---|
-| Full text papers | **over 1.5 million** |
-| Authors | **over 1.9 million** |
-| Paper downloads | **over 300 million** |
-| Total references | **over 47 million** |
-| Total citations | **over 2 million** |
-| Disciplines | **69** |
-
-These are rounded marketing figures, not live counts. A dated growth anchor: Inside Higher
-Ed, reporting in July 2016, stated "SSRN's database contains more than 557,000 full-text
-papers" (S9) [COM]. **1.5 M in 2026 against 557 k in mid-2016 — roughly 2.7× in ten years**
-[INF].
-
-### 3.2 The network table — measured, not advertised
-
-Retrieved 2026-09-01 from SSRN's own (undocumented) statistics endpoint
-`https://www.ssrn.com/rest/rn/statistics/<network-id>`, one call per network, ids scraped
-from each network's landing page (S3) [API]. All 68 networks; sorted by papers.
-
-| # | Slug | Network | Papers | Authors | Downloads |
-|---|---|---|---|---|---|
-| 1 | `ern` | Economics Research Network | **694,156** | 483,483 | 176,127,090 |
-| 2 | `lsn` | Legal Scholarship Network | **424,464** | 195,316 | 123,661,781 |
-| 3 | `psn` | Political Science Network | **346,704** | 280,140 | 80,043,922 |
-| 4 | `fen` | Financial Economics Network | **269,931** | 170,120 | 108,617,336 |
-| 5 | `engrn` | **Engineering Research Network** | **194,984** | 642,236 | 12,842,427 |
-| 6 | `srpn` | Sustainability Research & Policy | 162,463 | 336,089 | 32,930,506 |
-| 7 | `mrn` | Management Research Network | 152,716 | 188,377 | 55,268,367 |
-| 8 | `chemrn` | Chemistry Research Network | 140,072 | 505,586 | 7,620,137 |
-| 9 | `matscirn` | **Materials Science Research Network** | 123,100 | 457,254 | 6,698,460 |
-| 10 | `environscirn` | Environmental Science Research Network | 115,379 | 383,741 | 11,249,765 |
-| 11 | `irpn` | Innovation Research & Policy Network | 115,367 | 132,868 | 38,005,166 |
-| 12 | `aarn` | Anthropology & Archaeology Research Network | 114,524 | 104,273 | 26,265,644 |
-| 13 | `medrn` | Medical Research Network | 109,129 | 619,963 | 10,577,432 |
-| 14 | `compscirn` | **Computer Science Research Network** | **108,252** | 261,370 | 18,572,774 |
-| 15 | `energyrn` | Energy Research Network | 91,506 | 278,672 | 7,486,730 |
-| 16 | `psychrn` | Psychology Research Network | 77,551 | 170,962 | 16,162,640 |
-| 17 | `biorn` | Biology Research Network | 75,303 | 398,103 | 6,416,967 |
-| 18 | `physicsrn` | Physics Research Network | 70,929 | 251,986 | 3,044,477 |
-| 19 | `cgn` | Corporate Governance Network | 70,405 | 68,712 | 29,784,448 |
-| 20 | `erpn` | Entrepreneurship Research & Policy Network | 63,310 | 72,875 | 21,901,238 |
-| 21 | `edurn` | Education Research Network | 60,477 | 79,573 | 15,182,463 |
-| 22 | `isn` | **Information Systems & eBusiness Network** | **58,848** | 69,961 | 19,563,242 |
-| 23 | `arn` | Accounting Research Network | 57,948 | 49,684 | 27,002,726 |
-| 24 | `prn` | Philosophy Research Network | 57,293 | 47,084 | 15,827,142 |
-| 25 | `sociologyrn` | Sociology Research Network | 42,559 | 61,896 | 7,269,580 |
-| 26 | `wgsrn` | Women's & Gender Studies Research Network | 41,056 | 50,217 | 10,048,288 |
-| 27 | `agriscirn` | Agricultural Science Research Network | 41,000 | 165,242 | 3,498,387 |
-| 28 | `decisionscirn` | Decision Science Research Network | 40,464 | 62,214 | 10,638,834 |
-| 29 | `csn` | Cognitive Science Network | 35,870 | 59,384 | 11,624,936 |
-| 30 | `mathrn` | Mathematics Research Network | 33,655 | 80,224 | 2,400,434 |
-| 31 | `finplanrn` | Financial & Investment Planning Research Network | 31,953 | 34,531 | 10,565,445 |
-| 32 | `foodscirn` | Food Science Research Network | 31,883 | 115,185 | 3,215,190 |
-| 33 | `earthscirn` | Earth Science Research Network | 29,022 | 98,882 | 2,135,716 |
-| 34 | `ecorn` | Ecology Research Network | 28,328 | 115,881 | 2,413,121 |
-| 35 | `org` | Organizational Behavior | 26,295 | 43,255 | 9,052,943 |
-| 36 | `infoscirn` | Information & Library Science Research Network | 26,055 | 49,710 | 6,752,516 |
-| 37 | `oper` | Operations Research Network | 25,468 | 52,401 | 5,752,028 |
-| 38 | `transportrn` | Transportation Research Network | 24,620 | 50,745 | 4,076,409 |
-| 39 | `biochemrn` | Biochemistry Research Network | 24,429 | 159,987 | 1,313,072 |
-| 40 | `publichealthrn` | Public Health Research Network | 23,851 | 81,781 | 2,553,061 |
-| 41 | `geographyrn` | Geography Research Network | 23,151 | 58,278 | 3,607,023 |
-| 42 | `cjrn` | Criminal Justice Research Network | 21,978 | 21,166 | 5,664,723 |
-| 43 | `commrn` | Communication Studies Research Network | 21,038 | 37,552 | 5,768,652 |
-| 44 | `pol` | Corporate Strategy & Business Policy Research Network | 17,438 | 31,826 | 6,751,462 |
-| 45 | `sirn` | Social Insurance Research Network | 22,506 | 14,248 | 2,468,924 |
-| 46 | `mkt` | Marketing Research Network | 19,931 | 25,352 | 7,868,413 |
-| 47 | `pharmscirn` | Pharmaceutical Science Research Network | 17,969 | 105,780 | 1,528,327 |
-| 48 | `intl` | International Business & Management Research Network | 17,947 | 29,930 | 6,280,369 |
-| 49 | `neuroscirn` | Neuroscience Research Network | 16,899 | 77,829 | 1,870,735 |
-| 50 | `hen` | Health Economics Network | 16,624 | 27,678 | 4,641,154 |
-| 51 | `geologyrn` | Geology Research Network | 15,081 | 63,132 | 1,024,147 |
-| 52 | `lingrn` | Linguistics Research Network | 12,217 | 17,682 | 1,760,233 |
-| 53 | `historyrn` | History Research Network | 9,778 | 9,160 | 1,539,795 |
-| 54 | `lit` | Literature Research Network | 8,871 | 7,488 | 2,347,034 |
-| 55 | `bhnp` | Business History & Nonprofit Organizations Research Network | 7,942 | 10,511 | 1,962,619 |
-| 56 | `forensicscirn` | Forensic Science Research Network | 6,977 | 12,820 | 2,307,798 |
-| 57 | `archrn` | Architecture Research Network | 6,875 | 20,295 | 694,096 |
-| 58 | `vetscirn` | Veterinary Science Research Network | 6,526 | 35,738 | 504,962 |
-| 59 | `lrn` | Leadership Research Network | 6,423 | 9,924 | 2,244,606 |
-| 60 | `rwrn` | Rhetoric & Writing Research Network | 6,153 | 9,538 | 2,466,519 |
-| 61 | `neg` | Negotiations & Dispute Resolution Network | 4,879 | 6,090 | 2,912,105 |
-| 62 | `artsrn` | Visual, Performing & Fine Arts Research Network | 4,865 | 6,933 | 1,209,691 |
-| 63 | `planetscirn` | Space & Planetary Science Research Network | 3,947 | 7,775 | 321,222 |
-| 64 | `nursingrn` | Nursing Research Network | 3,642 | 12,092 | 646,406 |
-| 65 | `hrn` | Hebrew Research Network | 3,359 | 1,849 | 607,233 |
-| 66 | `crn` | Classics Research Network | 1,951 | 2,074 | 641,495 |
-| 67 | `dentistryrn` | Dentistry Research Network | 1,754 | 9,235 | 205,948 |
-| 68 | `mrcn` | Music Research & Composition Network | 1,062 | 1,689 | 245,784 |
-
-**Sum of the "papers" column: 4,569,102.** Against a stated corpus of ~1.5 million full-text
-papers, that implies **every paper sits in ~3.0 networks on average** [INF]. Any statement
-of the form "SSRN has N papers in field X" is therefore an over-count of the same corpus
-seen from a different angle, and network figures **must not be added**. The same applies at
-eJournal level (§2).
-
-**Downloads column sum: 1,034,254,315** against a stated ~300 million downloads (S1) — the
-same ~3.4× multiple, from the same cause [INF].
-
-### 3.3 First Look — where "Preprints with The Lancet" and "Cell Sneak Peek" actually live
-
-**First Look** is SSRN's journal-integration programme: "a partnership between SSRN and some
-of the world's most influential journals … With one click during the submission process to
-the journal, authors choose to post a preprint of their paper on SSRN" (S5) [DOC]. The
-participant list (S5, retrieved 2026-09-01) includes **Cell Press** and **The Lancet**
-alongside Acta Materialia, Heliyon, *Journal of Web Semantics*, *Materials Today*,
-*NeuroImage: Clinical*, *Journal of Economic Dynamics and Control*, *Scientific African*,
-*Surgery Open Science*, *Ultrasonics Sonochemistry* and others.
-
-**Verified: both Wikipedia "repositories" are SSRN channels.**
-
-| Channel | SSRN URL | SSRN binding ID | Papers (2026-09-01) | Wikipedia says |
-|---|---|---|---|---|
-| **Preprints with The Lancet** | `ssrn.com/index.cfm/en/the-lancet/` | 3184962 | **25,561** (S4) [API]; page counter shows 25,550 (S5) [WEB] | ">1,000" (S11) |
-| **Cell Press Sneak Peek** | `ssrn.com/index.cfm/en/cell-press-sneak-peek/` | 3184889 | **12,414** (S4) [API]; page counter shows 12,404 (S5) [WEB] | ">1,000" (S11) |
-
-The Lancet channel's own description states its screening explicitly: "Preprints available
-here are not Lancet publications or necessarily under review with a Lancet journal. These
-preprints are early-stage research papers that have not been peer-reviewed. **The usual SSRN
-checks and a Lancet-specific check for appropriateness and transparency have been applied.**
-The findings should not be used for clinical or public health decision-making" (S5) [DOC].
-
-Cell Sneak Peek is different in kind — it is *not* an open preprint server but "an author
-opt-in preview of the papers under review in our primary research journals" (S5) [DOC], with
-a per-journal breakdown on its landing page (Cell 778, Cell Reports 2,545, iScience 3,283,
-Current Biology 883, Neuron 488, Joule 395 …). **A Sneak Peek posting means the paper is
-under review at a specific Cell Press journal.** That is a meaningfully different signal
-from a preprint deposit and Wikipedia's flat listing loses it.
-
-**Consequence for the Wikipedia list:** SSRN's own row claims it "Aggregates over 30 preprint
-servers (Preprints with *The Lancet*, Cell Sneak Peek, etc.)" (S11). That is the wrong verb.
-SSRN does not aggregate anything; it **hosts** journal-branded channels on one database.
-There is no federation and no harvesting. Compare [osf-preprints.md](osf-preprints.md) §10,
-where "aggregates" was literally true and is now obsolete — two different errors that happen
-to look alike in a table.
-
-## 4. Screening and moderation — what gets in
-
-**SSRN does screen, and it screens harder than most preprint servers.** This is documented,
-current, and worth reading in full because it is unusually specific.
-
-**Submission requirements** (S6, *"How do I submit a paper to SSRN?"*, last updated
-2026-08-03) [DOC]:
-
-- Free SSRN account with a complete author profile.
-- Title and abstract **in English**; full-text **PDF in English** displaying title and all
-  authors with affiliations.
-- "Names, current affiliations, and valid email addresses of all authors — **Organizations
-  cannot be listed as authors** (exceptions are government- or academic-related
-  organizations)."
-- Copyright-holder permission where applicable.
-- "**An AI disclosure statement (if using AI)** — must be included with the abstract and
-  display on the PDF. NOTE: AI features used solely for accessibility via disability
-  assistive technology are exempt."
-- Medical/health papers additionally require patient confidentiality, patient consent, and
-  conflict-of-interest/funding disclosures, per SSRN's *Medical or Health Care Preprint
-  Checklist*.
-
-**Explicit exclusion list** — "Content types that are typically NOT accepted" (S6, verbatim)
-[DOC]:
-
-> Abstract-only submissions · Books / book chapters · Calls for papers · Class assignments /
-> course projects · **Conference proceedings** · Frameworks · Guides and how-to's · News
-> articles · Non-English content · Non-scholarly articles (including, but not limited to:
-> articles with no references, some commercial/marketing material) · **Presentation slides**
-> · Published papers in certain disciplines · **Research written by high school students and
-> faculty**
-
-Two of those matter for an engineering reader: **conference proceedings are excluded**
-(so SSRN is structurally unable to be a systems/architecture venue, where the conference
-paper *is* the publication), and **"frameworks"** are excluded — apparently an
-anti-content-mill measure.
-
-**And even eligible content may be refused:** "Submissions may be rejected for missing
-information, failure to meet Research Integrity standards and editorial policies, or
-non-compliance with our Terms of Use." (S6) [DOC]
-
-**Turnaround:** "Most submissions are processed quickly, though some may take up to 10
-business days." Named causes of delay include "**Verification Processes**: Verify any
-competing interests and confirm author identities" and "**Legal or Rights Clearance**:
-Confirming permissions for copyrighted material" (S6, last updated 2026-07-20) [DOC].
-SSRN's support site carries a whole help category titled **"Preprint Rejections"** (S6)
-[DOC] — a category no other server in this collection has.
-
-**What it is not.** SSRN states it plainly: "SSRN is a platform for the dissemination of
-early-stage research. **We are not a peer-reviewed journal**, and we do not publish or
-distribute hard copies. Posting a paper to SSRN and/or distributing it in one of SSRN's
-email alerts does not make it Accepted or Published" (S6) [DOC].
-
-**Assessment.** The screen is real — identity verification, rights clearance, an AI
-disclosure mandate, an explicit exclusion list, a rejections help category. It is closer to
-a journal's desk-check than to arXiv's moderation, and much stronger than
-[OSF Preprints](osf-preprints.md) or [Zenodo](zenodo.md). It is still **not** a check on
-whether the research is correct.
-
-## 5. Reliability — what you can and cannot trust
-
-**Where SSRN is genuinely authoritative:** law, economics, finance, accounting, corporate
-governance. In these fields the SSRN working paper is a **primary literature object**.
-Central-bank and NBER-style working papers, law-review preprints, and finance research
-circulate here first and are cited here for years. A citation to an SSRN abstract ID in a
-law-review footnote is unremarkable and appropriate. The download and citation counters,
-whatever their distortions, are used in real hiring and tenure decisions (S6) [DOC] — that
-is an unusual degree of institutional embedding for a preprint server.
-
-**Where it is thin — be honest about computing.** SSRN's computing content is weak compared
-with arXiv, and the numbers say so:
-
-- Software Engineering: **6,122** papers, ever, across the whole life of the server (S4)
-  [API].
-- High Performance Computing: **2,484**. Web Technology: **2,105**. Computation Theory:
-  **8,624**.
-- Conference proceedings — the dominant publication form in systems, architecture,
-  networking, PL and security — are **explicitly not accepted** (§4) [DOC].
-- The corpus skews to *AI-and-policy*, *AI-and-law*, information-systems-as-business-school-
-  discipline, and management-of-technology. Real systems work is essentially absent.
-
-**Practical rule: if you are looking for a computing preprint, check arXiv first, the
-[Cryptology ePrint Archive](cryptology-eprint-archive.md) for crypto, and
-[TechRxiv](techrxiv.md) for IEEE-adjacent engineering. Check SSRN only when the paper has a
-law, economics, policy or business-school angle — and then check it seriously, because for
-those angles SSRN is where the work is.**
-
-**What a deposit guarantees:**
-
-- A stable abstract ID and URL (`ssrn.com/abstract=NNNNNNN`).
-- **A Crossref DOI** in the `10.2139/ssrn.<id>` namespace — "SSRN, as a registered Crossref
-  member, pays for this DOI assignment, and automatically assigns a preprint DOI to
-  qualifying papers at no cost to authors." Assigned to "posted preprint submissions that
-  have completed the SSRN review process and include a full-text PDF", typically "within a
-  few business days after the review process has been completed" (S6) [DOC].
-- **DOIs are not removable**: "Once a DOI is assigned, it becomes a permanent record of that
-  preprint … neither the DOI string nor the assignment itself can be changed or deleted
-  after registration. If a paper is retracted or withdrawn, its DOI will redirect to a
-  retraction or withdrawal notice on SSRN's website." (S6) [DOC] This is a materially
-  stronger persistence commitment than OSF currently honours (see
-  [osf-preprints.md](osf-preprints.md) §6, where recent deposits have no DOI at all).
-- That a human checked identity, rights, language and content type (§4).
-- Nothing about correctness.
-
-**Known failure modes:**
-
-1. **Author self-removal is one click.** SSRN's own instructions: My Papers → Modify →
-   "Make it Inactive — Remove it from SSRN's eLibrary … The status will change to REMOVED"
-   and the paper becomes unavailable to SSRN and external search engines (S6) [DOC]. The
-   DOI survives and redirects to a notice; the PDF does not. **If an SSRN paper matters to
-   you, keep your own copy.**
-2. **Publisher lock-in on some records.** "Why does my submission not have a Modify button,
-   and why is it Restricted by Publisher? The publisher, journal, or series does not allow
-   changes to submissions." (S6) [DOC] — for First Look records, the journal, not the
-   author, controls the object.
-3. **Operator-initiated removal over copyright.** This has actually happened. §10.2.
-4. **Download-count gaming.** SSRN's rankings are career-relevant (§1), which creates the
-   obvious incentive. SSRN has published rank-manipulation countermeasures; I did not
-   retrieve a current policy document. **[NOT-VERIFIED].**
-5. **Under-review ≠ preprint.** A Cell Sneak Peek record means "under review at journal X"
-   (§3.3). Do not cite it as a stable preprint; it may vanish into a paywalled version of
-   record.
-
-**How to sanity-check an individual SSRN paper:**
-
-1. Resolve `https://doi.org/10.2139/ssrn.<abstract_id>` — a DOI redirecting to a withdrawal
-   notice is the loudest available signal. (Note: the resolution itself will land on a 403
-   for a scripted client; use a browser — §8.)
-2. Look at which network(s) and eJournal(s) it is filed under. A "computer science" paper
-   filed only in Legal Scholarship Network is telling you something.
-3. Check `publication_status` — SSRN records carry values such as `UNDER REVIEW` and
-   `Working Paper Series` (S4) [API].
-4. Search for a journal version. In economics and law, the SSRN version is often the *only*
-   version and that is normal; in CS it usually means the work went nowhere.
-5. Archive the PDF. See failure mode 1.
-
-**Eventual-publication rate: [NOT-VERIFIED].** I found no measurement I could cite within
-this pass. It would in any case be misleading to quote a single figure across a corpus where
-law and economics working papers are frequently terminal by design.
-
-## 6. What you actually find there — examples
-
-Retrieved live from the CompSciRN paper feed, 2026-09-01 (S4) [API]:
-
-- *"Should We Allow AI to Police Itself? Assessing the Technical Feasibility and Legal
-  Implications of LLM-Based Agent Evaluation"* — Matthias Holweg (Oxford, Saïd Business
-  School) and Philipp Hacker (European University Viadrina, European New School of Digital
-  Studies). Abstract ID 7378338, `Working Paper Series`, `publication_status: UNDER REVIEW`,
-  35 pages, approved 2026-09-02.
-
-That single record is a fair sample of SSRN computing content: a technically literate paper
-about computing, written from a law/business-school vantage, by authors who would never
-consider arXiv `cs.SE`. It is good work in its own frame. It is not a systems paper.
-
-Structurally, what you find on SSRN is:
-
-- **Law-and-technology**: platform regulation, AI liability, data protection, algorithmic
-  accountability — Legal Scholarship Network, 424,464 papers, the second-largest network.
-- **Economics of technology**: innovation, IP, network effects, digital markets —
-  Innovation Research & Policy Network, 115,367 papers.
-- **Information systems as a business-school discipline** — 58,848 papers.
-- **Applied engineering and materials** — Engineering Research Network 194,984 and
-  Materials Science 123,100, which are *larger* than CompSciRN, and are the parts of SSRN
-  a hardware engineer is most likely to touch.
-- **Medical preprints via The Lancet channel** — 25,561.
-
-**No landmark-papers table.** SSRN hosts nothing foundational in software, distributed
-systems, databases, electronics or security; those literatures live on arXiv, in ACM/IEEE
-proceedings, and in the [Cryptology ePrint Archive](cryptology-eprint-archive.md). SSRN
-*is* foundational in law and financial economics, which is outside this collection's scope.
-Listing a table would be padding.
-
-## 7. Access, APIs and bulk retrieval — SSRN is hostile to scripted access
-
-**Verified 2026-09-01. This section is the practical one.**
-
-### 7.1 What is blocked
-
-| Target | Default UA | Browser UA | Verdict |
-|---|---|---|---|
-| `https://www.ssrn.com/index.cfm/en/` | **403** (5,421 B) | **200** (70,049 B) | UA-gated; browser UA works |
-| `https://papers.ssrn.com/sol3/papers.cfm?abstract_id=7378338` | **403** | **403** | **hard-blocked** |
-| `https://papers.ssrn.com/sol3/DisplayAbstractSearch.cfm` | — | **403** | **hard-blocked** |
-| `https://doi.org/10.2139/ssrn.7378338` (follows redirect) | — | **403** at `papers.ssrn.com` | **the DOI resolver lands on a block page** |
-| `https://api.ssrn.com/` (root) | **403** (23 B) | — | root is closed |
-
-**Full user-agent ladder against a `papers.ssrn.com` abstract page** (per
-[AGENTS.md](../../AGENTS.md) §Web retrieval fallback), all 2026-09-01:
-
-| User-Agent | Result |
-|---|---|
-| curl default | 403, 5,526 B |
-| Chrome 131 desktop | 403, 5,761 B |
-| `WhatsApp/2.23.20.0` | 403, 5,526 B |
-| `ChatGPT-User/1.0` | 403, **896,437 B** |
-| `ClaudeBot/1.0` | 403, **896,437 B** |
-| `Googlebot/2.1` | 403, 5,589 B |
-
-**Every agent is refused.** The two AI-crawler agents get a 403 with a ~900 kB body — an
-interstitial/challenge page rather than the short block page. The ladder does not open this
-door; **`papers.ssrn.com` requires a real browser session and there is no polite workaround.
-Do not spend time rotating agents against it.**
-
-`robots.txt` (identical on `www.` and `papers.`, 2026-09-01) (S7) [DOC]:
-
-```
-User-agent: GPTBot          Disallow: /
-User-agent: ChatGPT-User    Disallow: /
-User-agent: Google-Extended Disallow: /
-User-agent: *               Crawl-Delay: 5
-                            Disallow: /admin/ /tasks/ /config/
-Sitemap: https://papers.ssrn.com/sitemap/sitemaps.cfm
-Sitemap: https://papers.ssrn.com/sitemap/sitemaps.cfm?dir=authors
-```
-
-Named AI crawlers are banned outright; everything else is nominally allowed at a 5-second
-crawl delay, which the 403s on `papers.ssrn.com` contradict in practice.
-
-### 7.2 What works
-
-**There is no documented public API. There is an undocumented one, and it is how every
-number in §2 and §3.2 was obtained.** Both endpoints are the JSON backends of SSRN's own
-web widgets, discovered from `data-url` attributes in the network page HTML:
-
-| Endpoint | Returns |
-|---|---|
-| `https://www.ssrn.com/rest/rn/statistics/<network-id>` | `{"statistics":[{"number":…,"name":"authors"},{…"papers"},{…"downloads"},{…"abstractviews"}]}` |
-| `https://www.ssrn.com/rest/rn/subject-areas/<network-id>` | the network's eJournal list with `journal_id`s |
-| `https://www.ssrn.com/rest/rn/recent-papers/<network-id>?limit=N` | recent items |
-| `https://api.ssrn.com/content/v1/bindings/<binding-id>/papers` | `{"total": N, "papers":[…]}` with title, authors, affiliations, page count, `publication_status`, download counts, approval date |
-
-Caveats: undocumented, unversioned in any published contract, subject to change without
-notice, and served with HTML whitespace prepended to the JSON on the `/rest/rn/` paths (parse
-from the first `{`). No authentication was required and no rate limit was hit across ~150
-sequential calls. Use `Crawl-Delay: 5` as your conscience dictates; I did not.
-
-### 7.3 Negative controls
-
-| Probe | Result | Lesson |
-|---|---|---|
-| `https://api.ssrn.com/content/v1/bindings/999999999/papers?size=1` | **HTTP 200**, `{"total": 0, "papers": []}` | **a bogus binding ID returns a clean zero.** Identical to a genuinely empty eJournal. Only IDs harvested from a real subject-areas response can be trusted |
-| `https://www.ssrn.com/index.cfm/en/networks/` (invented path) | **404**, 19,267 B | www.ssrn.com 404s honestly — good |
-| `https://www.ssrn.com/index.cfm/en/cspn/` (invented slug) | **404**, 19,267 B | same |
-| `https://papers.ssrn.com/oai` | **HTTP 200**, 19,157 B, `<title>Page Cannot be Found</title>` | **soft-404.** A 200 here means nothing |
-| `https://papers.ssrn.com/definitely-not-a-real-path-xyzzy` | **HTTP 200**, 19,157 B, same "Page Cannot be Found" | confirms the soft-404 |
-| `https://papers.ssrn.com/sol3/oai` | **HTTP 200**, 19,157 B, same | confirms |
-
-### 7.4 OAI-PMH — verified absent
-
-**SSRN has no OAI-PMH endpoint.** `papers.ssrn.com/oai`, `papers.ssrn.com/sol3/oai` and
-`www.ssrn.com/oai/request?verb=Identify` were all probed 2026-09-01: the first two return the
-soft-404 "Page Cannot be Found" page with HTTP 200 (byte-identical to a deliberately bogus
-path), and the third returns a genuine 404 (S8) [WEB]. No OAI-PMH base URL is advertised
-anywhere on SSRN's site or support hub. This is a real structural difference from
-[EconStor](repec-and-econstor.md), [E-LIS](library-science-and-cognitive-archives.md) and
-essentially every repository built on DSpace or EPrints, and it means SSRN's metadata is not
-harvestable by BASE, CORE or OpenAIRE through the standard route.
-
-**Bulk dumps:** none offered. **Sitemaps** are advertised in `robots.txt` and are the only
-sanctioned enumeration path; they live on the 403-blocked host.
-
-## 8. Licensing and reuse
-
-**Copyright stays with the author.** SSRN: "You do not transfer copyright for any papers (or
-other documents) you post on SSRN. When you upload a paper, you give SSRN the **non-exclusive
-right** to post and distribute your paper. You retain the right to remove your paper from
-SSRN at any time." (S6) [DOC]
-
-**There is no default open licence.** Unlike [OSF Preprints](osf-preprints.md) (CC-BY or CC0,
-enforced) or [Zenodo](zenodo.md), SSRN does not require or offer a standard Creative Commons
-selection at deposit. The author's own rights position governs, and SSRN puts the burden of
-verifying it on the author: "Each publisher has their own rights and self-archiving policies
-regarding what version of your article you can make available … you should review your
-publishing agreement, the publisher's copyright policies … prior to posting" (S6) [DOC]. SSRN
-maintains a *Copyright Reference Guide* for this.
-
-**Not everything is free to read.** "The vast majority of papers can be downloaded free of
-charge as well. **The only exceptions are papers whose copyright is held by third parties
-that request a download fee.**" (S6) [DOC] There are paywalled items in an "open access
-research platform".
-
-**Text and data mining is explicitly reserved.** Every SSRN page footer, 2026-09-01: "All
-content on this site: Copyright © 2026 Elsevier Inc., its licensors, and contributors. **All
-rights are reserved, including those for text and data mining, AI training, and similar
-technologies.** For all open access content, the relevant licensing terms apply." (S2) [WEB]
-
-Combined with §7, the position is unambiguous: **SSRN does not want you to mine it, says so
-in the footer, blocks the attempt at the CDN, and bans the named AI crawlers in
-`robots.txt`.** Treat everything in §2–§3 of this record as manually-obtained reference
-figures, not as a licence to scrape.
-
-## 9. Caveats and controversies
-
-### 9.1 The Elsevier acquisition (May 2016)
-
-SSRN was bought from Social Science Electronic Publishing Inc. by **Elsevier in May 2016**
-(S10) [LIT]. Founder and chairman **Michael C. Jensen** wrote to the community on 17 May
-2016, acknowledging the obvious objection in advance: "We realize that this change may create
-some concerns about the intentions of a legacy publisher acquiring an open-access working
-paper repository. **I shared this concern.** But after much discussion … I am convinced that
-they would be good stewards of our mission." CEO **Gregg Gordon** wrote that users should feel
-"assured that our ethos will remain intact" and that "existing and future SSRN content will
-be largely unaffected" (S9, quoting both) [COM].
-
-The **Authors Alliance** issued an 11-point list of principles it asked SSRN to adopt to
-reassure users; SSRN "offered more general reassurances" but "would not commit to adopting
-even one of our principles" (S9, quoting the Authors Alliance) [COM].
-
-### 9.2 The July 2016 takedowns — the cautionary tale
-
-**What happened.** In mid-July 2016, two months after the acquisition, Stephen E. Henderson
-(Professor of Law, University of Oklahoma) found that a PDF he had uploaded to SSRN had been
-removed. The revision comment read: *"It appears that you do not retain copyright to the
-paper, and the PDF has been removed from public view. Please provide us with the copyright
-holder's written permission to post. Alternatively, you may replace this version with a
-working paper or preprint version, if you so desire."* (S9) [COM]
-
-Henderson emailed a law-professor listserv — "It appears that the corporate takeover of SSRN
-is already having a real impact" — the message was picked up by *PrawfsBlawg* and spread. Other
-authors reported the same. Techdirt covered it under the headline *"Just As Open Competitor
-To Elsevier's SSRN Launches, SSRN Accused Of Copyright Crackdown"* (S12) [COM].
-
-**SSRN's response.** On Twitter, 15 July 2016: "To be clear, we haven't changed any policies
-about copyright. A couple of processing emails were sent incorrectly and in the wrong order.
-… There isn't some big conspiracy happening." Gordon's follow-up statement on Monday 18 July:
-a staff member had reviewed Henderson's PDF and removed it **by mistake**; the paper was
-reposted once SSRN was made aware. "Some have taken this mistake to suggest there has been a
-copyright policy change resulting from our recent acquisition by Elsevier. This is not true …
-While we worked to improve our compliance part of our submission process, we fell short in
-thinking through the communications with the authors." Gordon estimated **about 20 papers**
-were affected, out of a corpus then numbering more than 557,000 (S9) [COM].
-
-**What followed.** Authors publicly deleted their SSRN accounts ("I am depublishing every
-single article from #SSRN immediately"). Others migrated to the newly launched **SocArXiv**
-— which is the same SocArXiv now holding 24,670 records on
-[OSF Preprints](osf-preprints.md). The Authors Alliance told members "it may be time to leave
-SSRN and adopt more author-friendly alternatives" (S9) [COM]. Henderson himself did not
-withdraw his papers, but his verdict is the fairest summary anyone offered: "overall I believe
-SSRN has done much good … Unfortunately, to date their actions often don't mirror those
-words, as in this latest takedown craze" (S9) [COM].
-
-**What it actually demonstrates — read carefully.** The strong version of the story (Elsevier
-purged papers to protect journal revenue) is **not supported by the sources**; the contemporary
-reporting supports a staff error affecting ~20 papers, compounded by bad automated emails
-(S9) [COM]. The *real* lesson is structural and survives the debunking intact:
-
-- **A commercial host has both the technical ability and the legal motivation to remove your
-  paper unilaterally**, and it does not need a conspiracy to do so — a compliance workflow
-  and an ordinary mistake are sufficient.
-- **Authors found out by accident.** There was no notice; Henderson discovered it by checking
-  a revision comment.
-- **The reaction was disproportionate to the incident and proportionate to the risk.** Twenty
-  papers is a rounding error; the *possibility* was what moved people, and moving to
-  community-run infrastructure was the rational response.
-- **SSRN's rights-clearance screen (§4) is exactly the mechanism that misfired.** The same
-  policy that makes SSRN's screening better than its peers' is the one that removes papers.
-  You cannot have one without the other.
-
-Compare the failure modes across this collection: OSF Preprints' risk is **operator strategy
-change** ([osf-preprints.md](osf-preprints.md) §4); CogPrints' risk was **founder retirement**
-([library-science-and-cognitive-archives.md](library-science-and-cognitive-archives.md));
-SSRN's risk is **rightsholder compliance under commercial ownership**. All three are real and
-all three are different.
-
-### 9.3 Other caveats
-
-1. **Network paper counts must never be summed** (§3.2). The 68 networks total 4.57 M against
-   ~1.5 M actual papers.
-2. **Wikipedia lists SSRN's channels as separate repositories** and undercounts both by 20×
-   (§3.3).
-3. **Wikipedia's "more than 55 disciplines"** (S11) is stale — SSRN says 69, the selector
-   shows 68 (§2).
-4. **`papers.ssrn.com` cannot be reached by any script**, including via the DOI resolver
-   (§7). Any pipeline that resolves SSRN DOIs will fail, and it will fail with a 403 that
-   looks like an error in your code.
-5. **No OAI-PMH, no bulk dump, no documented API** (§7.4). SSRN is absent from harvester-based
-   discovery in a way that arXiv, EconStor and E-LIS are not.
-6. **TDM and AI training rights are reserved in the footer** (§8).
-7. **Papers can be removed by their authors in three clicks**, and some records are locked by
-   the publisher rather than the author (§5).
-
-## 10. Sources
-
-- **S1** — SSRN homepage, `https://www.ssrn.com/index.cfm/en/`. Retrieved 2026-09-01 with a
-  Chrome 131 User-Agent (default UA returns 403 — see §7). HTTP 200, 70,049 bytes. Supports:
-  the "SSRN by the numbers" counters (1.5 M papers, 1.9 M authors, 300 M downloads, 47 M
-  references, 2 M citations, 69 disciplines), the six top-level discipline groups, and the
-  Economics/Medical/Computer Science network blurbs.
-- **S2** — SSRN Computer Science Research Network landing page,
-  `https://www.ssrn.com/index.cfm/en/compscirn/`. Retrieved 2026-09-01, HTTP 200, 27,393
-  bytes. Supports: the 68-entry network selector (the exhaustive network list and slugs), the
-  CompSciRN description, and the Elsevier copyright/TDM footer text.
-- **S3** — SSRN internal statistics endpoint,
-  `https://www.ssrn.com/rest/rn/statistics/<network-id>`, one call per network with ids
-  scraped from each network landing page. Retrieved 2026-09-01. Supports: the entire
-  68-network table in §3.2 (papers, authors, downloads).
-- **S4** — SSRN internal content API, `https://api.ssrn.com/content/v1/bindings/<id>/papers`
-  and `https://www.ssrn.com/rest/rn/subject-areas/<network-id>`. Retrieved 2026-09-01.
-  Supports: the CS eJournal table and binding IDs, the engrn/isn/matscirn eJournal lists,
-  the Lancet (25,561) and Cell Sneak Peek (12,414) totals, the sample CompSciRN record
-  (abstract ID 7378338), and the bogus-binding negative control.
-- **S5** — SSRN First Look `https://www.ssrn.com/index.cfm/en/first-look/`; Preprints with
-  The Lancet `https://www.ssrn.com/index.cfm/en/the-lancet/`; Cell Press Sneak Peek
-  `https://www.ssrn.com/index.cfm/en/cell-press-sneak-peek/`. All retrieved 2026-09-01,
-  HTTP 200. Supports: the First Look participant list including Cell Press and The Lancet,
-  the Lancet screening statement, the Cell Sneak Peek per-journal breakdown, and the on-page
-  counters.
-- **S6** — SSRN Support Center on Elsevier's support hub, `https://www.elsevier.support/ssrn`
-  and the answer pages `/ssrn/answer/what-is-ssrn` (updated 2026-08-03),
-  `/ssrn/answer/get-started` (2026-08-03), `/ssrn/answer/ssrn-review-process` (2026-07-20),
-  `/ssrn/answer/copyright-policy` (2026-08-03), `/ssrn/answer/doi` (2026-08-03),
-  `/ssrn/answer/is-ssrn-a-publisher` (2026-08-03), `/ssrn/answer/remove-my-paper`
-  (2026-08-03), `/ssrn/answer/why-am-i-getting-a-firewall-alert` (2026-08-03), and the
-  category `/ssrn/category/19203` ("Preprint Rejections"). All retrieved 2026-09-01.
-  Supports: §4 in full, the DOI policy, the copyright/non-exclusive-licence position, the
-  paper-removal mechanism, the "not a peer-reviewed journal" statement, and the
-  metrics-for-tenure framing.
-- **S7** — `https://www.ssrn.com/robots.txt` and `https://papers.ssrn.com/robots.txt`.
-  Retrieved 2026-09-01, HTTP 200, 209 and 333 bytes. Supports: the GPTBot / ChatGPT-User /
-  Google-Extended bans, `Crawl-Delay: 5`, and the sitemap URLs.
-- **S8** — Access probes: `https://papers.ssrn.com/sol3/papers.cfm?abstract_id=7378338`
-  against six user-agents; `https://papers.ssrn.com/oai`; `https://papers.ssrn.com/sol3/oai`;
-  `https://www.ssrn.com/oai/request?verb=Identify`;
-  `https://papers.ssrn.com/definitely-not-a-real-path-xyzzy`;
-  `https://doi.org/10.2139/ssrn.7378338`; `https://api.ssrn.com/`. All 2026-09-01. Supports
-  §7 in full, including the OAI-PMH absence and the soft-404 finding.
-- **S9** — Carl Straumsheim, *"'There Isn't Some Big Conspiracy Happening'"*, **Inside Higher
-  Ed**, 18–19 July 2016.
-  `https://www.insidehighered.com/news/2016/07/19/social-science-research-network-confusion-leads-calls-boycott`
-  Retrieved 2026-09-01 (HTTP 200 with default curl UA — no fallback needed). Supports: the
-  Henderson takedown, the verbatim revision comment, SSRN's tweet and Gordon's statement,
-  the "about 20 papers" figure, the **557,000 full-text papers** size anchor for July 2016,
-  Jensen's and Gordon's acquisition-day statements, the Authors Alliance 11-point episode,
-  and the author migration to SocArXiv.
-- **S10** — Wikipedia, *Social Science Research Network*, wikitext via
-  `https://en.wikipedia.org/w/index.php?title=Social_Science_Research_Network&action=raw`.
-  Retrieved 2026-09-01. Supports: founding in 1994 by Michael C. Jensen and Wayne Marr, the
-  May 2016 Elsevier acquisition, and the pointers to S9 and S12. [LIT — used as a citation
-  index; the underlying primary sources were retrieved independently where possible.]
-- **S11** — Wikipedia, *List of preprint repositories*, wikitext via
-  `https://en.wikipedia.org/w/index.php?title=List_of_preprint_repositories&action=raw`.
-  Retrieved 2026-09-01. Supports: the SSRN row (">1,000,000", "Aggregates over 30 preprint
-  servers", "More than 55 disciplines", 1994, Elsevier) and the separate ">1,000" rows for
-  *Preprints with The Lancet* (2018, Elsevier) and *Cell Sneak Peek* (2018, Cell
-  Press/Elsevier).
-- **S12** — Mike Masnick, *"Just As Open Competitor To Elsevier's SSRN Launches, SSRN Accused
-  Of Copyright Crackdown"*, **Techdirt**, 18 July 2016.
-  `https://www.techdirt.com/2016/07/18/just-as-open-competitor-to-elseviers-ssrn-launches-ssrn-accused-copyright-crackdown/`
-  Retrieved 2026-09-01, HTTP 200 with default curl UA. Supports: contemporaneous community
-  reaction to the takedowns. [COM]
diff --git a/research/preprint-repositories/synthical.md b/research/preprint-repositories/synthical.md
deleted file mode 100644
index c7addc4..0000000
--- a/research/preprint-repositories/synthical.md
+++ /dev/null
@@ -1,242 +0,0 @@
-# Synthical — preprint repository record
-
-- **URL:** https://synthical.com/
-- **Operator:** **Fast Flash Corporation** ("Made in France and the US", per the site's own
-  footer, S1) [WEB]
-- **Discipline scope:** *as advertised by Wikipedia* — computer science, mathematics,
-  economics, physics, cryptography, biology, chemistry. *As actually operated* — a reader
-  interface over arXiv, bioRxiv, medRxiv and ChemRxiv (§1).
-- **Launched:** 2023 (first Wayback capture 2023-07-25, S2; site footer "at 2023", S1)
-  [WEB] · **Status:** **unreachable from this host on 2026-09-01** (§5)
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Headline finding: Synthical is not a preprint repository.** It is an AI-assisted
-> reader and aggregator over other people's preprint servers. It hosts no original
-> deposits, mints no identifiers, and is not registered with any DOI agency. The Wikipedia
-> characterisation is **misleading** and its ">1,000,000" figure counts *harvested
-> third-party articles*, not deposits. Detail and evidence below.
-
-## 1. What it actually is
-
-The decisive evidence is Synthical's own homepage, captured 2023-07-26 (S1) [WEB]. Quoted
-verbatim:
-
-> "Synthical: Science, Simplified"
->
-> "Discover, learn, and share research, made easy with our AI."
->
-> **"3 million articles and growing — We've assembled all articles from Arxiv, Biorxiv,
-> Medrxiv, and Chemrxiv, continually updating with fresh content."**
->
-> "Make complex concepts simple with our AI"
-
-The page shows a **Simple / Original** toggle applied to an article labelled **"From
-arXiv"**, alongside "Collaborate with your team", a pricing block ("Free for everyone /
-$-- for additional features"), and the footer **"© Fast Flash Corporation. Made in France
-and the US at 2023."** (S1) [WEB].
-
-That is a complete description of the product: **harvest everything from four established
-preprint servers, re-present it with an AI simplification layer and team-collaboration
-features, and monetise the premium tier.** There is no deposit workflow, no submission
-interface, no moderation policy, and no identifier minting described anywhere on the page.
-
-The listed subject areas — Mathematics, Economics, Computer Science, Statistics, Medicine,
-Quantitative Finance, Chemistry, Condensed Matter, Biology, Quantitative Biology, Physics,
-Quantum Physics, Astrophysics, Electrical Engineering (S1) [WEB] — are simply **arXiv's and
-bioRxiv's own category names**. Synthical did not define a taxonomy; it inherited one.
-
-## 2. Does it host original deposits? — the test
-
-A repository that issues citable records must register identifiers with an agency. Synthical
-does not. Retrieved 2026-09-01 (S3) [API]:
-
-| Registry probe | Result |
-|---|---|
-| Crossref members matching `synthical` | **0** |
-| DataCite clients matching `synthical` | **0** |
-| Crossref works with `synthical` in bibliographic metadata | **0** |
-
-Cross-checked against method controls used elsewhere in this collection: the Crossref prefix
-endpoint returns a clean **HTTP 404** for a nonexistent prefix (`10.99999`), and returns real
-counts for genuine preprint platforms (TechRxiv 30,954; ChemRxiv 55,400; Authorea 80,599)
-(S3) [API]. So these registry APIs *do* answer correctly for real preprint hosts — the zeros
-for Synthical are informative, not an artefact of a broken query.
-
-**Conclusion [INF, well-supported]:** Synthical issues no DOIs and therefore hosts no
-independently citable original deposits. Anything you read on Synthical is a rendering of a
-record whose canonical home, identifier and version history live on arXiv, bioRxiv, medRxiv
-or ChemRxiv.
-
-> One honest limitation: a registry name-search is a weaker instrument than a prefix lookup,
-> and I did not obtain a positive control for the exact `members?query=` endpoint. The
-> conclusion does not rest on the zeros alone — it rests primarily on Synthical's own
-> description of itself (§1), with the registry result as corroboration.
-
-## 3. Size — what the ">1,000,000" actually counts
-
-Wikipedia's *List of preprint repositories* records (S4) [WEB]:
-
-| Field | Wikipedia value |
-|---|---|
-| Description | "Open access preprint repository for computer science, mathematics, economics, physics, cryptography, biology, and chemistry" |
-| Size | **">1,000,000"** |
-| Year | 2023 |
-| Operator | "Synthical" |
-
-Three problems.
-
-1. **The size figure is self-cited.** Wikipedia's reference for ">1,000,000" is
-   `https://synthical.com/?is_viewing=true` — the vendor's own homepage (S4) [WEB]. It is
-   marketing copy, not an audited count.
-2. **It counts other servers' content.** Synthical's own claim at the same period was "3
-   million articles… assembled *from* Arxiv, Biorxiv, Medrxiv, and Chemrxiv" (S1) [WEB].
-   Whatever the number, it is a measure of **how much of arXiv et al. Synthical has
-   ingested**, not of anything deposited with Synthical. Listing it in a table beside
-   arXiv's own count double-counts the same documents.
-3. **The operator field is circular.** "Synthical" is listed as its own operator; the actual
-   corporate entity is **Fast Flash Corporation** (S1) [WEB].
-
-**Verified size of Synthical's original corpus: zero** (§2). **[NOT-VERIFIED]:** the current
-size of its harvested index — the site is unreachable (§5).
-
-## 4. Screening and moderation
-
-Not applicable in the repository sense: with no deposit pathway there is nothing to screen.
-Whatever editorial screening applies to a given article was applied by **arXiv, bioRxiv,
-medRxiv or ChemRxiv** before Synthical ingested it.
-
-The AI layer introduces a *different* risk that no upstream moderation covers: Synthical's
-"Simple" mode presents a machine-generated rewrite alongside the "Original" (S1) [WEB]. A
-simplified restatement is a derivative work that may drop hedges, conditions or scope
-limits. **Never cite a Synthical "Simple" rendering as the content of a paper.** Go to the
-original. [INF]
-
-## 5. Durability — current status
-
-**Synthical did not respond on 2026-09-01.** Probe results (S5) [WEB/API]:
-
-| Probe | Result |
-|---|---|
-| DNS `synthical.com` | resolves to **162.55.17.19** (also `www.synthical.com`) |
-| `https://synthical.com/` via curl, Chrome UA, 30 s | **connection timed out** |
-| Same, IPv4-forced, 45 s | **connection timed out**, `time_connect = 0.000000` |
-| Independent fetch tool, 60 s | **request timed out** |
-| Raw TCP to 162.55.17.19:443 | `TimeoutError` |
-| Raw TCP to 162.55.17.19:80 | `TimeoutError` |
-
-DNS still resolves, but **no TCP connection is established on either port** — packets are
-dropped rather than refused. Control comparison: `zenodo.org` resolved and served requests
-normally throughout the same session, so this is not a general network fault at my end.
-
-**Wayback history** (S2) [API]: **68 captures spanning 25 Jul 2023 – 4 Feb 2026**. The
-earliest captures return HTTP 200 with real HTML (10,656 bytes on 2023-07-25); captures
-from late 2023 onward are predominantly **307/308 redirects** rather than 200s, and the last
-capture of any kind is **2026-02-04**.
-
-**What I can and cannot conclude.** I *cannot* declare Synthical dead: an unreachable host
-from one network on one day may be a firewall, a geo-block, an outage, or a transient
-failure, and this repository's method does not permit upgrading that to "defunct". What I
-*can* say is that **the site was not reachable by any means available to me, no capture
-exists after February 2026, and no independent liveness confirmation was obtained.** Status
-is recorded as **unreachable**, not defunct. **[NOT-VERIFIED]** either way.
-
-**Why this matters regardless of the outcome.** Synthical holds nothing of its own. If it
-disappeared tomorrow, **no research record would be lost** — every document it displayed
-remains at arXiv, bioRxiv, medRxiv or ChemRxiv under its canonical identifier. That is the
-one genuinely reassuring property of a pure aggregator, and it is the direct inverse of the
-Authorea situation, where a platform migration *did* put an 80,000-work corpus at the mercy
-of a corporate roadmap.
-
-The real durability risk here is to **users, not content**: reading lists, team workspaces,
-annotations and any AI-generated summaries created inside Synthical have no external home
-and no export guarantee I could verify. [INF]
-
-## 6. Commercial model
-
-From the archived homepage (S1) [WEB]: a freemium structure — "Free for everyone" with
-"$-- for additional features" (the price was not rendered in the capture), plus
-"Collaborate with your team" and "Synthical for researchers / Try for Free" calls to
-action. Contact address `hi@synthical.com`. Operator: **Fast Flash Corporation**.
-
-This is a **venture-style SaaS product built on freely available public content**, not
-scholarly infrastructure. It has no institutional backer, no preservation mandate, no
-succession plan, and no stated retention policy — none of which it needs, given it holds no
-unique content, but all of which matter if you were considering it a repository.
-
-**[NOT-VERIFIED]:** current pricing, funding, corporate status of Fast Flash Corporation,
-and terms of service — all unobtainable while the site is unreachable.
-
-## 7. Access, APIs and bulk retrieval
-
-**None verified.** No public API, OAI-PMH endpoint, bulk dump or documented machine
-interface could be identified, and the site is unreachable (§5). `robots.txt` and
-`sitemap.xml` both timed out.
-
-For the underlying content, use the real sources, all of which have proper bulk interfaces:
-arXiv (API + OAI-PMH + S3 bulk), bioRxiv/medRxiv (APIs), ChemRxiv. Harvesting Synthical
-would be strictly worse than harvesting upstream, even if it were reachable.
-
-## 8. Landmark papers
-
-None. Synthical is not the venue of first publication for anything — by construction (§2).
-No table.
-
-## 9. Licensing and reuse
-
-**[NOT-VERIFIED]** for Synthical's own terms (§6).
-
-The material Synthical displays carries **the licences assigned by depositors on the
-originating servers** — arXiv's per-item licences (including non-commercial and
-arXiv-perpetual variants), bioRxiv/medRxiv Creative Commons selections, and ChemRxiv's
-terms. Those licences govern reuse; Synthical's presentation layer does not and cannot
-relicense them. AI-generated "Simple" renderings are derivative works whose status is
-**unclear and unverified**. [INF]
-
-## 10. Caveats and controversies
-
-1. **The Wikipedia entry should not be relied on.** It calls Synthical a "preprint
-   repository", self-cites the vendor for its size, lists the company as its own operator,
-   and places a harvested index count in the same column as genuine deposit counts (§3).
-   **This record's finding is that the characterisation is misleading on the central point.**
-2. **Aggregator ≠ repository.** The distinction is not pedantry. A repository accepts
-   deposits, assigns identifiers, and takes on preservation duty. Synthical does none of
-   these. Conflating the two inflates apparent preprint-ecosystem capacity and misdirects
-   citations away from canonical identifiers.
-3. **Cite upstream, always.** A Synthical URL is not a stable scholarly identifier. Use the
-   arXiv ID or DOI.
-4. **Do not cite AI-simplified text** as the paper's content (§4).
-5. **Currently unreachable** (§5) — with the status deliberately left open rather than
-   declared defunct.
-
-## 11. Sources
-
-- **S1** — Synthical homepage, archived snapshot
-  `http://web.archive.org/web/20230726125245/https://synthical.com/`, retrieved
-  **2026-09-01**. Supports: the "assembled all articles from Arxiv, Biorxiv, Medrxiv, and
-  Chemrxiv" statement, "3 million articles and growing", the AI Simple/Original feature and
-  "From arXiv" labelling, the inherited category list, the freemium pricing block, the
-  `hi@synthical.com` contact, and the "© Fast Flash Corporation. Made in France and the US
-  at 2023" footer. Retrieved via an alternate fetch path after direct requests to the live
-  site timed out.
-- **S2** — Internet Archive Wayback APIs:
-  `https://archive.org/wayback/available?url=synthical.com` and
-  `http://web.archive.org/cdx/search/cdx?url=synthical.com&output=json`. Retrieved
-  2026-09-01. Supports: 68 captures spanning 25 Jul 2023 – 4 Feb 2026, the 2023-07-25
-  earliest 200 capture at 10,656 bytes, and the shift to 307/308 responses in later captures.
-- **S3** — Registry probes: `https://api.crossref.org/members?query=synthical`,
-  `https://api.datacite.org/clients?query=synthical`,
-  `https://api.crossref.org/works?query.bibliographic=synthical`; controls
-  `https://api.crossref.org/prefixes/10.99999` (HTTP 404) and prefix counts for
-  `10.36227` / `10.26434` / `10.22541`. Retrieved 2026-09-01. Supports: §2, zero identifier
-  registration and the validity of the comparison.
-- **S4** — Wikipedia, *List of preprint repositories*, wikitext retrieved via the MediaWiki
-  API, 2026-09-01. Supports: the ">1,000,000" size claim and its self-citation to
-  `synthical.com/?is_viewing=true`, the 2023 year, the "Synthical" operator field, and the
-  disciplinary description quoted in §3.
-- **S5** — Live probes 2026-09-01: DNS resolution of `synthical.com` and
-  `www.synthical.com` to 162.55.17.19; HTTPS requests via curl (default and Chrome 131 UA,
-  IPv4-forced, 30–45 s timeouts); an independent fetch tool at 60 s; and raw TCP socket
-  connections to 162.55.17.19 on ports 443 and 80. All timed out. `zenodo.org` served
-  requests normally in the same session as a control.
diff --git a/research/preprint-repositories/techrxiv.md b/research/preprint-repositories/techrxiv.md
deleted file mode 100644
index b78cd23..0000000
--- a/research/preprint-repositories/techrxiv.md
+++ /dev/null
@@ -1,405 +0,0 @@
-# TechRxiv — preprint repository record
-
-- **URL:** https://www.techrxiv.org/
-- **Operator:** IEEE (Institute of Electrical and Electronics Engineers). IEEE is Crossref
-  member `263` and owns the DOI prefix `10.36227` used by every TechRxiv deposit (S1).
-  Funded by IEEE; free to deposit and to read.
-- **Discipline scope:** *as advertised* — "engineering, computer science, and related
-  technology" (S3). *As actually used* — heavily weighted toward computing/AI; the
-  circuits-and-devices core of IEEE is a minority of the corpus (§2, §3).
-- **Launched:** first content posted **2019-10-18** (S1); the server is generally described
-  as a 2020 launch and 2020 is the first full year of operation. **Status:** active.
-- **Platform history:** Figshare (2019/2020 → Dec 2023) → **Authorea** (Wiley) (Dec 2023 →
-  present) (§1, S2/S4/S1).
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Access warning up front.** As of 2026-09-01 `www.techrxiv.org` is behind a Cloudflare
-> interactive challenge and returns **HTTP 403 `cf-mitigated: challenge`** to every scripted
-> request tried (default UA, Chrome UA, WhatsApp UA, ChatGPT-User UA, HTTP/1.1) except
-> `/robots.txt` (S5). Every count in this record therefore comes from **Crossref** (the DOI
-> registry, [API]) or from **Wayback captures** ([WEB]), never from a live site scrape.
-> This is stated so the reader knows which numbers are first-hand.
-
-## 1. What it is
-
-TechRxiv is IEEE's own preprint server. Its purpose is narrow and, for an engineer, very
-useful: it lets an author post a manuscript at (or near) the moment they submit it to an
-IEEE journal or conference, so the work is citable, timestamped and — crucially —
-**openly readable** while the IEEE version is still behind the Xplore paywall. IEEE
-permits this; TechRxiv is the sanctioned channel for it.
-
-The server has moved platforms once, and the move matters for anyone writing scrapers or
-citing URLs. TechRxiv originally ran on **Figshare** infrastructure: Wayback captures of
-the 2022 home page carry a `figshare` footer (S2), and the Figshare ResourceSync manifest
-`https://www.techrxiv.org/figshareresourcesync/techrxiv/cresourcelist-0.xml` is archived
-from 2020-08-09 through 2023-12-02 (S4). It now runs on **Authorea** (a Wiley property,
-served through an Atypon-style front end): the live server emits an HTTP 103 early-hints
-`Link:` header preloading `/products/authorea/techrxiv/releasedAssets/...` (S5), the
-January 2026 Wayback capture is branded `AUTHOREA` and footers read "Powered by
-Authorea.com" (S3), and `/robots.txt` exposes Atypon path conventions (`/action/showJournal`,
-`/na101/`, `/doi/metrics/`) (S5).
-
-**The migration date is December 2023.** Two independent [API]/[WEB] signals agree. First,
-the DOI syntax changed: Figshare-era DOIs look like `10.36227/techrxiv.23589741.v1`
-(Figshare item id, `.vN` suffix), Authorea-era DOIs look like
-`10.36227/techrxiv.170244204.41850386/v1` (two numeric segments, `/vN` path suffix). The
-earliest Authorea-style DOI was posted **2023-12-13**; the monthly crossover runs
-Nov 2023 (0 new-style / 605 old-style) → Dec 2023 (120 / 371) → Jan 2024 (289 / 30) (S1).
-Second, the Figshare ResourceSync manifest stops being archived on 2023-12-02 (S4).
-Legacy items kept their Figshare-style DOI stems and still receive new versions under the
-old syntax — the newest old-style DOI in the registry was posted 2026-02-17 (S1).
-
-## 2. Scope and subject taxonomy
-
-TechRxiv classifies with the **IEEE top-level thesaurus terms**, not arXiv-style codes.
-The browse facet counts below are from the Wayback capture of the home page on
-**2026-01-04** (S3). An item may carry more than one term, so the column sums to 35,251
-against 17,549 public documents — a mean of ≈2.0 terms per item [INF].
-
-| IEEE subject term | Items (2026-01-04) [WEB] |
-|---|---|
-| computing and processing | 9,416 |
-| communication, networking and broadcast technologies | 4,741 |
-| signal processing and analysis | 3,972 |
-| power, energy and industry applications | 2,541 |
-| components, circuits, devices and systems | 2,335 |
-| robotics and control systems | 2,186 |
-| general topics for engineers | 1,951 |
-| engineering profession | 1,878 |
-| bioengineering | 1,824 |
-| fields, waves and electromagnetics | 1,577 |
-| transportation | 939 |
-| aerospace | 731 |
-| engineered materials, dielectrics and plasmas | 715 |
-| photonics and electrooptics | 610 |
-| geoscience | 549 |
-| nuclear engineering | 186 |
-
-**How much of TechRxiv is electronics/power/RF/embedded?** Summing the terms an
-electronics engineer would care about — components/circuits/devices/systems (2,335),
-power/energy/industry (2,541), fields/waves/EM (1,577), photonics (610), engineered
-materials/dielectrics/plasmas (715) — gives 7,778 term-assignments, **22% of all
-assignments**; add communications (4,741) and signal processing (3,972) and you reach 47%.
-By contrast *computing and processing* alone is 27% of assignments [INF from S3]. The
-honest summary: TechRxiv is IEEE-shaped on paper and CS/AI-shaped in practice, with a
-real but secondary hardware core of a few thousand documents.
-
-## 3. Size and growth
-
-Three different numbers, all correct, all measuring different things. Report them
-separately.
-
-| Measure | Value | Date | Source |
-|---|---|---|---|
-| Crossref DOI records under prefix `10.36227`, all type `posted-content` | **30,954** | 2026-09-01 | [API] S1 |
-| Distinct items (DOI records after stripping `.vN` / `/vN` version suffixes) | **18,890** | 2026-09-01 | [API] S1 |
-| Site's own "Public Documents" counter | **17,549** | 2026-01-04 | [WEB] S3 |
-| Site's cumulative views / downloads counter | 13,580,596 / 5,791,115 | 2026-01-04 | [WEB] S3 |
-
-The site counter (17,549 on 2026-01-04) and the Crossref distinct-item count (18,890 on
-2026-09-01) are consistent given eight months of growth [INF]. The 30,954 raw DOI count is
-the one to avoid quoting as "TechRxiv has 31,000 preprints" — it double-counts versions.
-
-**Distinct items by year of first posting** [API] S1:
-
-| 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 (to 09-01) |
-|---|---|---|---|---|---|---|---|
-| 73 | 1,009 | 1,836 | 2,429 | 3,103 | 3,528 | 5,611 | 1,301 |
-
-2019 is three months of soft launch (9 items in October, 27 in November, 37 in December).
-The 2025 jump to 5,611 is real in the registry; whether it reflects genuine growth or the
-same generative-AI submission wave that other servers report is **[NOT-VERIFIED]** here —
-IEEE has published no submission/rejection statistics I could retrieve.
-
-**Versioning.** 2,678 of 18,890 distinct items (14.2%) carry more than one numbered
-version [API] S1.
-
-## 4. Screening and moderation — what gets in
-
-TechRxiv describes itself as an "**open, moderated** preprint server for unpublished
-research" (S3, home-page About blurb, 2026-01-04). That is the only first-hand statement of
-policy I could retrieve.
-
-**I could not obtain IEEE's published screening criteria.** The live `/about`,
-`/faqs`, `/submission-guidelines` and `/terms-of-use` pages are Cloudflare-blocked (S5), and
-the Wayback captures of `https://www.techrxiv.org/about` from 2024-01 through 2025-06 are
-**JavaScript shells** — the Authorea SPA never rendered for the crawler, so the archived
-HTML contains navigation chrome and nothing else (S6). This is marked
-**[NOT-VERIFIED]**: I cannot tell you who moderates, against what checklist, in what
-turnaround, or what the rejection rate is. What I can say from evidence:
-
-- The moderation is **pre-publication** in the sense that the browse UI distinguishes
-  ordinary preprints from a "**Version of Record**" filter class (S3), so IEEE tracks
-  published status as a first-class attribute.
-- IEEE runs periodic house-organ notices soliciting deposits ("TechRxiv: Share Your
-  Preprint Research With the World!") in *IEEE Potentials* and *IEEE Network* across
-  2022–2025 (S7) — [LIT], but these are one-page promotional notices, not policy.
-- Content is clearly **not peer reviewed**; the most-cited items (§7) are unrefereed
-  survey articles.
-
-If you need the authoritative policy, the route is a browser session on techrxiv.org or an
-IEEE Author Center page — neither of which is scriptable from here.
-
-## 5. Reliability — what you can and cannot trust
-
-**What a TechRxiv deposit guarantees:** a Crossref DOI, a posting timestamp, a version
-chain, and an explicit licence (§9). Nothing about correctness.
-
-**What it does not guarantee:** peer review, novelty, or that the author has the right to
-post. There is no endorsement system and no affiliation requirement that I could verify.
-
-**Eventual-publication rate — a real measured number.** Of the 18,890 distinct items,
-**5,457 (28.9%) carry a Crossref `is-preprint-of` relation** pointing at a published
-article [API] S1. Where those links point:
-
-| Target DOI prefix | Publisher | Link records |
-|---|---|---|
-| `10.1109` | IEEE | 6,297 |
-| `10.1016` | Elsevier | 832 |
-| `10.1007` | Springer | 335 |
-| `10.2139` | SSRN | 282 |
-| `10.3390` | MDPI | 235 |
-| `10.1088` | IOP | 67 |
-| `10.1038` | Nature Portfolio | 64 |
-| `10.1080` | Taylor & Francis | 61 |
-| `10.1049` | IET | 55 |
-| `10.1002` | Wiley | 54 |
-
-Treat 28.9% as a **floor**, not the true publication rate: the relation is populated when
-the link is made, and items posted in the last 18 months have not had time to be published
-or linked [INF]. Note the 282 links to SSRN — those are not journal publications and are a
-reminder to check what a link actually points at.
-
-**Known failure modes.** (a) The citation-weighted top of the corpus is dominated by
-unrefereed LLM/AI survey articles with many co-authors (§7) — a pattern associated
-elsewhere with citation-farming; treat high TechRxiv citation counts as weak evidence of
-quality. (b) Version proliferation: one legacy item has reached `.v13` (S1), so "the
-TechRxiv version" is ambiguous unless you pin the version. (c) Because the platform
-migrated, older links and older DOI syntax coexist; both still resolve (§8) but tooling
-that assumes one syntax will break.
-
-**How to sanity-check an individual TechRxiv paper.**
-1. `curl -s https://api.crossref.org/works/<techrxiv-doi>` and read `relation.is-preprint-of`.
-   If present, the paper reached a journal — go read that instead.
-2. Read `posted.date-parts` and compare against the published version's date. A preprint
-   posted *after* the journal article is a mirror, not a priority claim.
-3. Read `license` — CC BY-NC-SA content cannot be redistributed the way CC BY content can.
-4. Check the version suffix. `/v1` and `/v4` can differ substantially.
-
-## 6. What you actually find there — examples
-
-Real deposits, each verified to exist via Crossref and to resolve through `doi.org` on
-2026-09-01 (S1, S8):
-
-- **Power devices.** *4 A / 300 V switching of lateral β-Ga₂O₃ MOSFET devices*, Tetzner et
-  al., posted 2025-06-19 — `10.36227/techrxiv.175037428.81899126/v1`. Linked as preprint of
-  *IEEE Electron Device Letters* `10.1109/LED.2025.3590836`. Genuine wide-bandgap power
-  electronics, on the server months ahead of the paywalled letter.
-- **Magnetics for converters.** *Non-Linear Inductors Characterization in Real Operating
-  Conditions for Power Density Optimization*, Scirè et al., 2021-06-04 —
-  `10.36227/techrxiv.14485221`.
-- **FPGA / on-board processing.** *CloudSatNet-1: FPGA-based Hardware-Accelerated Quantized
-  CNN for Satellite On-Board Cloud Cover Classification*, Pitoňák et al., 2022-03-17 —
-  `10.36227/techrxiv.19367825.v1`, preprint of `10.3390/rs14133180`.
-- **RISC-V microarchitecture.** *Configurable Hardware Acceleration for Hyperdimensional
-  Computing Extension on RISC-V*, Martino et al., 2024-12-05 —
-  `10.36227/techrxiv.173337827.72919533/v1`, preprint of *IEEE Trans. Computers*
-  `10.1109/TC.2025.3642250`.
-- **Cryogenic / quantum control electronics.** *Cryogenic Embedded System to Support
-  Quantum Computing: From 5nm FinFET to Full Processor*, Genßler et al., 2023-06-27 —
-  `10.36227/techrxiv.23548242.v1`, preprint of `10.1109/TQE.2023.3300833`.
-- **6G channel modelling.** *Overview of 3GPP Release 19 Study on Channel Modeling
-  Enhancements to TR 38.901 for 6G*, Poddar et al., 2025-08-03 —
-  `10.36227/techrxiv.175423889.90938399/v1`. Directly useful standards-tracking material.
-- **Analog design automation.** *LADAC: Large Language Model-driven Auto-Designer for
-  Analog Circuits*, Liu et al., 2024-01-08 — `10.36227/techrxiv.170473941.10097233/v1`.
-- **Hardware security.** *Algorithmic Security is Insufficient: A Comprehensive Survey on
-  Implementation Attacks Haunting Post-Quantum Security*, Canto et al., 2023-05-23 —
-  `10.36227/techrxiv.23071079.v1`.
-- **Neuromorphic sensing.** *Hardware, Algorithms, and Applications of the Neuromorphic
-  Vision Sensor: a Review*, Cimarelli et al., 2025-04-18 —
-  `10.36227/techrxiv.174494936.63871491/v1`, preprint of `10.3390/s25196208`.
-- **IIoT security dataset.** *Edge-IIoTset: A New Comprehensive Realistic Cyber Security
-  Dataset of IoT and IIoT Applications*, Ferrag et al., 2022-01-27 —
-  `10.36227/techrxiv.18857336.v1`, preprint of `10.1109/ACCESS.2022.3165809`. A dataset
-  paper that is actually used.
-
-## 7. Landmark papers — an honest assessment
-
-**TechRxiv has essentially no field-defining papers, and that is by design.** It is not a
-priority-claiming venue like arXiv `hep-th` or the IACR ePrint archive; it is an
-early-dissemination and green-OA channel attached to IEEE's submission pipeline. Nobody
-"scoops" a competitor on TechRxiv.
-
-The empirical proof is the citation distribution. Sorting all 30,954 records by Crossref
-`is-referenced-by-count` (S1), the top of the corpus is unrefereed AI survey literature,
-not electronics:
-
-| Paper | Identifier | Posted | Crossref citations (2026-09-01) | Preprint first? |
-|---|---|---|---|---|
-| A Survey on Large Language Models: Applications, Challenges, Limitations, and Practical Usage | `10.36227/techrxiv.23589741.v1` | 2023-07-10 | 247 | Yes — no `is-preprint-of` recorded; never linked to a journal version |
-| Engineering Education in the Era of ChatGPT: Promise and Pitfalls of Generative AI for Education | `10.36227/techrxiv.21789434.v1` | 2022-12-30 | 127 | Yes |
-| Artificial Intelligence in the Battle against Coronavirus (COVID-19): A Survey | `10.36227/techrxiv.12743933` | 2020-08-01 | 87 | Yes |
-| Prompt Engineering For ChatGPT: A Quick Guide | `10.36227/techrxiv.22683919` | 2023-05-04 | 87 | Yes |
-| A Survey on Mixture of Experts | `10.36227/techrxiv.172055626.64129172/v1` | 2024-07-09 | 71 | Yes |
-| CERT: Contrastive Self-supervised Learning for Language Understanding | `10.36227/techrxiv.12308378.v1` | 2020-05-21 | 70 | Yes |
-
-The highest-cited *electronics/communications* items are far lower: the 6G rural-connectivity
-survey `10.36227/techrxiv.10253336.v1` (2019-11-06, 13 citations) and
-`10.36227/techrxiv.11634669` (2020-01-17, 13 citations) are among the most-cited comms
-deposits, and the Edge-IIoTset dataset paper reaches 18 (S1). For genuinely landmark
-electronics preprints, look at arXiv `eess.*`/`cs.AR` or the IACR ePrint archive, not here.
-
-**What TechRxiv *is* good for is covered in §8 — finding the open version of a paywalled
-IEEE paper.**
-
-## 8. Access, APIs and bulk retrieval
-
-**The live site is not scriptable.** Every path except `/robots.txt` returned HTTP 403 with
-`cf-mitigated: challenge` and a Cloudflare "Just a moment…" body on 2026-09-01, under four
-different user agents (S5). `robots.txt` additionally sets `User-agent: GPTBot / Disallow: /`
-and `Crawl-delay: 1`, and points at a sitemap (`/sitemap-index-1.xml`) that is itself 403 (S5).
-
-**Negative control.** `https://www.techrxiv.org/robots-not-real.txt` → **403, 5,464 bytes**
-(the same challenge page), while `https://www.techrxiv.org/robots.txt` → **200, 808 bytes**
-of real text (S5). So on this host a 403 tells you nothing about whether a document exists,
-and only byte-size/content inspection distinguishes a real response.
-
-**Use Crossref instead.** It is complete, fast and unblocked:
-
-```bash
-# every TechRxiv DOI, paged
-curl 'https://api.crossref.org/prefixes/10.36227/works?rows=1000&select=DOI,title,posted,relation&cursor=*'
-# one item
-curl 'https://api.crossref.org/works/10.36227/techrxiv.19367825.v1'
-```
-
-**DOI resolution works fine** (doi.org is not behind the challenge). Both syntaxes resolve:
-
-| Probe | Result (2026-09-01) |
-|---|---|
-| `https://doi.org/10.36227/techrxiv.23589741.v1` (Figshare-era) | 302 → `https://www.techrxiv.org/doi/full/10.36227/techrxiv.23589741.v1` |
-| `https://doi.org/10.36227/techrxiv.170244204.41850386/v1` (Authorea-era) | 302 → `.../doi/full/10.36227/techrxiv.170244204.41850386/v1` |
-| **Negative control** `https://doi.org/10.36227/techrxiv.99999999999.99999999/v1` | **404** |
-
-So Figshare-era DOIs survived the migration intact — a good durability result (S8).
-
-**No OAI-PMH.** `/oai?verb=Identify` and `/api/oai?verb=Identify` both return the Cloudflare
-403 (S5); no working OAI endpoint was found. **[NOT-VERIFIED]** whether one exists behind
-the challenge.
-
-**OpenAlex does not index TechRxiv as a source.** `https://api.openalex.org/sources?search=TechRxiv`
-and `?filter=display_name.search:techrxiv` both return `meta.count = 0` on 2026-09-01 (S9).
-This conflicts with the fact that OpenAlex indexes engrXiv and ECSarXiv as sources; do not
-plan a TechRxiv pipeline around OpenAlex source filters.
-
-### The one thing TechRxiv is genuinely best at: finding the open version of a paywalled IEEE paper
-
-This is the property that justifies an engineer knowing the server exists. **6,297 Crossref
-link records point from TechRxiv preprints to `10.1109` DOIs** (S1) — and the link is
-recorded **in both directions**. Spot-checking five IEEE journal articles that are targets
-of a TechRxiv `is-preprint-of` relation, all five carried the reverse `has-preprint`
-relation on their own Crossref record (S1: `10.1109/TSG.2020.3010866`,
-`10.1109/TBCAS.2020.2982824`, `10.1109/TSTE.2020.3004630`, …).
-
-Practical recipe — you have an Xplore DOI and no subscription:
-
-```bash
-curl -s 'https://api.crossref.org/works/10.1109/TBCAS.2020.2982824' \
-  | python3 -c 'import json,sys; print(json.load(sys.stdin)["message"].get("relation",{}).get("has-preprint"))'
-# -> [{'id': '10.36227/techrxiv.10049843', 'id-type': 'doi', ...}]
-```
-
-Then resolve that DOI. This works without touching techrxiv.org's HTML, and it is more
-reliable than title-searching, because the publisher asserted the link.
-
-**Is the TechRxiv copy the accepted (post-review) version? [NOT-VERIFIED].** I could not
-confirm this. What the evidence shows: TechRxiv's browse UI has a "Version of Record"
-filter, so *some* items are flagged as VoR (S3); and **22.3% of the 5,457 journal-linked
-items carry more than one numbered version**, versus 14.2% of the corpus overall (S1) —
-consistent with a meaningful minority of authors uploading an updated (probably accepted)
-manuscript after acceptance, but consistent with several other stories too. Practically:
-**assume `/v1` is the submitted manuscript, check for a later version, and diff against the
-published abstract before relying on numbers.**
-
-## 9. Licensing and reuse
-
-Authors choose, and the default is permissive. Licence URLs recorded in Crossref for a
-3,000-record sample of prefix `10.36227` (2026-09-01, S1):
-
-| Licence | Records in sample |
-|---|---|
-| CC BY 4.0 | 2,389 |
-| CC BY-NC-SA 4.0 | 465 |
-| CC BY-SA 4.0 | 120 |
-| CC0 1.0 | 26 |
-
-≈80% CC BY [INF]. Every record in the sample carried *some* licence — unusual and welcome.
-For text/data mining this means the metadata is reusable via Crossref without restriction,
-but **bulk full-text mining of the site itself is blocked** by Cloudflare and by the
-explicit `GPTBot: Disallow` in robots.txt (S5), regardless of the per-item CC licence.
-
-## 10. Caveats and controversies
-
-- **Platform churn is the biggest risk to citations.** TechRxiv has already moved once
-  (Figshare → Authorea, Dec 2023). Old DOIs still resolve today (§8), but cite the **DOI**,
-  never a `techrxiv.org/articles/...` or `techrxiv.org/doi/full/...` URL.
-- **Scriptable access has regressed.** Wayback shows the site was crawlable through at
-  least 2026-01-04; 2026-07 captures are already 403 (S4). A knowledge base that depends on
-  scraping TechRxiv will rot.
-- **Two DOI syntaxes** (`....v1` vs `.../v1`) coexist forever. Regexes must handle both.
-- **The citation leaderboard is not a quality signal.** See §7.
-- **IEEE's own policy documents were not retrievable** (§4). Anything you read elsewhere
-  about "IEEE screens TechRxiv submissions for scope and plagiarism" is not confirmed by
-  this record.
-- **OpenAlex blind spot** (§8) — a real gap if you build discovery tooling.
-- Wikipedia's REST summary endpoint returned an internal error for `TechRxiv` on
-  2026-09-01 (S9), so no Wikipedia cross-check of size or launch date is recorded here.
-
-## 11. Sources
-
-- **S1** — Crossref REST API, prefix `10.36227`: `https://api.crossref.org/prefixes/10.36227/works`
-  (full cursor dump of 30,954 records with `DOI,posted,relation,license`; plus
-  `?rows=0&facet=type-name:*,published:30`, `?sort=is-referenced-by-count`, and individual
-  `https://api.crossref.org/works/<doi>` lookups). Retrieved 2026-09-01. **[API]** —
-  supports every deposit count, the year distribution, the version analysis, the
-  `is-preprint-of` statistics and target-prefix table, the licence table, the citation
-  ranking, all landmark/example metadata, and the December-2023 migration crossover.
-  Also `https://api.crossref.org/members?query=institute+of+electrical` (IEEE = member 263,
-  owns prefixes 10.1109, 10.36227, …), retrieved 2026-09-01.
-- **S2** — Wayback capture of the Figshare-era home page,
-  `http://web.archive.org/web/20220901140901/https://www.techrxiv.org/`, retrieved
-  2026-09-01. **[WEB]** — supports "figshare" footer branding pre-migration.
-- **S3** — Wayback capture of the Authorea-era home page,
-  `http://web.archive.org/web/20260104143925/https://www.techrxiv.org/`, retrieved
-  2026-09-01. **[WEB]** — supports the About blurb ("open, moderated preprint server…"),
-  `AUTHOREA` branding, the "Public Documents 17549" counter, the 13,580,596 views /
-  5,791,115 downloads counters, the full IEEE subject-term table, and the existence of the
-  "Version of Record" browse filter.
-- **S4** — Internet Archive CDX API,
-  `http://web.archive.org/cdx/search/cdx?url=www.techrxiv.org*`, several queries including
-  `.../figshareresourcesync*` and date-bounded home-page listings. Retrieved 2026-09-01.
-  **[WEB]** — supports the ResourceSync manifest span (2020-08-09 → 2023-12-02) and the
-  2026-07 onset of 403 responses to the crawler.
-- **S5** — Live probes of `https://www.techrxiv.org/` on 2026-09-01: `/` (403,
-  `cf-mitigated: challenge`, under 4 user agents and HTTP/1.1), `/robots.txt` (200, 808 B,
-  content quoted), `/sitemap.xml`, `/sitemaps.xml`, `/sitemap_index.xml`, `/action/sitemap.xml`,
-  `/api/docs`, `/oai?verb=Identify`, `/api/oai?verb=Identify` (all 403), and the negative
-  control `/robots-not-real.txt` (403, 5,464 B). **[WEB]**
-- **S6** — Wayback captures of `https://www.techrxiv.org/about` (20240101085028,
-  20250609162951) and `/faqs` (20240109100643), retrieved 2026-09-01. **[WEB]** — these are
-  the captures that turned out to be empty JS shells; they are the basis for the
-  **[NOT-VERIFIED]** verdict on IEEE's screening policy.
-- **S7** — Crossref search for literature about the server,
-  `https://api.crossref.org/works?query.bibliographic=TechRxiv+preprint+IEEE`, retrieved
-  2026-09-01. **[LIT]** — IEEE house notices, e.g. `10.1109/mpot.2022.3196554`,
-  `10.1109/mpot.2023.3263350`, `10.1109/mnet.2025.3540148`. Contents not read (paywalled).
-- **S8** — `doi.org` HEAD probes for `10.36227/techrxiv.23589741.v1`,
-  `10.36227/techrxiv.170244204.41850386/v1`, the ten example DOIs in §6, and the negative
-  control `10.36227/techrxiv.99999999999.99999999/v1` (404). Retrieved 2026-09-01. **[WEB]**
-- **S9** — `https://api.openalex.org/sources?search=TechRxiv` and
-  `?filter=display_name.search:techrxiv` (both `meta.count = 0`); Wikipedia REST
-  `https://en.wikipedia.org/api/rest_v1/page/summary/TechRxiv` (internal error). Retrieved
-  2026-09-01. **[API]**
diff --git a/research/preprint-repositories/theses-and-dissertations.md b/research/preprint-repositories/theses-and-dissertations.md
deleted file mode 100644
index f08eb32..0000000
--- a/research/preprint-repositories/theses-and-dissertations.md
+++ /dev/null
@@ -1,2589 +0,0 @@
-# Theses and dissertations — the long version of the paper
-
-> ⚠ **Dating correction (added 2026-09-11).** This record is stamped **2026-09-04** throughout, but
-> its actual research and write date is **2026-09-07** (filesystem mtime) — a stale "today" was
-> carried into the research brief. **Read every `2026-09-04` below as "2026-09-06/07".**
-> Server-supplied dates (e.g. the EThOS ResourceSync `at=2026-09-06`) are genuine and unaffected.
-> Dates have not been rewritten in place, because the exact probe date per claim cannot be
-> reconstructed and false precision would be worse than a flagged approximation.
-> See [`VERIFICATION.md §1.6`](VERIFICATION.md#16--dating-error-in-the-theses-record).
-
-- **Compiled:** 2026-09-04. Every figure was measured on that date unless another date is stated.
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-- **Companion record:**
-  [`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md).
-  That record covers documents that were *never* papers because an institution commissioned a
-  report. This one covers documents that were never papers because a **degree committee** demanded
-  something longer. The two overlap deliberately and in one place literally — Berkeley EECS files
-  its PhD dissertations *inside* its technical-report series, which is why `UCB/EECS-2016-1` is
-  both a technical report and the RISC-V design dissertation (§5.4, §9).
-- **Sibling records referenced throughout:**
-  [`open-access-full-text-sources.md`](open-access-full-text-sources.md) (CORE, BASE, OpenAIRE as
-  *paper* sources — this record covers only their ETD angle),
-  [`closed-and-defunct-servers.md`](closed-and-defunct-servers.md) (durability failure modes),
-  [`reliability-and-durability.md`](reliability-and-durability.md) (the gate taxonomy this record
-  extends), [`cryptology-eprint-archive.md`](cryptology-eprint-archive.md) (§7.6 side-channel and
-  embedded security — the KU Leuven and TU Graz dissertations in §5.7 are its long-form layer),
-  [`hal.md`](hal.md) (TEL runs on HAL infrastructure), and
-  [`landmark-papers.md`](landmark-papers.md) (of which §9 below is the thesis-shaped parallel).
-
-> **The claim this record makes.** For a very large amount of real hardware and systems work, **the
-> dissertation is the only complete writeup that exists.** The conference paper is 8–12 pages
-> because the CFP said so. The dissertation behind it is 150–300 pages, and it is where the
-> schematics, the board bring-up log, the measurement setup, the calibration procedure, the failed
-> iterations and the negative results ended up — because a committee required them and no page
-> limit forbade them. **This is frequently the single highest-value document in the entire
-> literature on a given piece of hardware, and it is almost never indexed alongside the papers.**
-
----
-
-## 1. Why the thesis, and not the paper
-
-### 1.1 The page-limit argument, made concretely
-
-Take the four cases this record verifies in §9 and compare the two artefacts.
-
-| Work | The paper | The thesis | What only the thesis has |
-|---|---|---|---|
-| **RISC-V** | The ISA is specified in a sequence of manuals; the *design rationale* was never a conference paper at all | **`UCB/EECS-2016-1`**, Waterman, 2016 — a full PhD dissertation (§9) | The argument for *why* the ISA is shaped the way it is: the compressed-encoding tradeoffs, the rejected alternatives, the quantitative comparisons against ARM/x86/MIPS |
-| **Semi-invasive attacks** | Scattered CHES/FDTC papers | **`UCAM-CL-TR-630`**, Skorobogatov, 2005, **144 pages** — a PhD dissertation issued as a Cambridge technical report, DOI `10.48456/tr-630` ([companion record §3.5](government-and-institutional-technical-reports.md)) | The decapsulation chemistry, the optical bench, the laser parameters, the per-chip results — i.e. everything needed to *reproduce* an optical fault injection |
-| **Switching algebra** | Shannon's 1938 AIEE paper is ~19 pages | **Shannon's 1937 MIT master's thesis** (§9) | The worked relay-circuit designs and the full development of the correspondence between Boolean algebra and contact networks |
-| **Sketchpad** | The 1963 AFIPS paper is a summary | **Sutherland's 1963 MIT PhD**, republished 2003 as **`UCAM-CL-TR-574`** (§9) | The constraint solver, the data structures, the display-file format, the light-pen tracking algorithm |
-
-The pattern is not incidental. It is what the two document types are *for*. A conference paper
-argues a contribution to a programme committee against a page budget. A dissertation demonstrates
-competence to an examining committee, and the standard evidence of competence in an experimental
-discipline is **method in enough detail that someone else could do it again.**
-
-### 1.2 Three structural reasons this matters for hardware specifically
-
-**One: hardware work has irreducible setup cost, and setup is what gets cut.** The measurement
-chain — probe, fixture, trigger, deskew, calibration, environmental controls — is a page or two in
-the paper and a chapter in the thesis. If you are trying to reproduce a side-channel result, a
-radiation test, an EM measurement or a timing attack, the chapter is the document you need and the
-paper is nearly useless.
-
-**Two: negative results survive only in theses.** No venue publishes "we built the first three
-revisions of this board and here is why they did not work". A committee, however, expects the
-candidate to account for three years, and the failed spin is part of the account. For anyone
-building the same thing, the failed spin is the most valuable page in the document.
-
-**Three: a thesis is often the *only* artefact.** A great deal of instrumentation, FPGA
-infrastructure, ASIC test chips and firmware toolchains was built by one student, described once,
-and never written up for a venue at all. See §5 for the repositories where this material is
-concentrated.
-
-### 1.3 The counter-argument, stated honestly
-
-Theses are not uniformly better than papers, and this record does not claim they are.
-
-- They are **unrefereed by the field**. The gate is a committee of three-to-six people, some of
-  whom are the supervisor. §7 works this through properly.
-- They are **stale on arrival**. Chapters written in year two are already 18 months old at
-  deposit, and the accompanying paper often carries later, better numbers.
-- They are **long**, and length is not information density. A 250-page dissertation frequently
-  contains 40 pages of literature review you do not need.
-- They are frequently **embargoed** (§8), which is precisely the failure mode that hurts most: the
-  thesis exists, the record is public, and the file is locked for three years.
-
-The practical position this record takes: **read the paper to know what was claimed, and read the
-thesis to know whether you can rebuild it.**
-
----
-
-## 2. The discovery and aggregation layer — and its 2025–2026 collapse
-
-This is the section where a reader expecting a healthy landscape gets a surprise. **Two of the
-three thesis-specific global aggregators are, as of 2026-09-04, either permanently closed or
-returning HTTP 503.** The generic open-access aggregators, which are *not* thesis-specific, are now
-the working route.
-
-### 2.1 Status table
-
-All probes **2026-09-04**, Chrome-131 user agent unless noted.
-
-| Service | Endpoint | Status | Measured | Verdict |
-|---|---|---|---|---|
-| **NDLTD** (organisation) | `https://ndltd.org/` | **200**, 135,318 B | — | Organisation alive [WEB] |
-| **NDLTD Global ETD Search** | `https://search.ndltd.org/` | **503**, 505 B (nginx default) | last known **6,534,039** ETDs (Wayback 2025-05-16) | **Down** [WEB] |
-| **NDLTD union catalogue OAI-PMH** | `https://union.ndltd.org/OAI-PMH/?verb=Identify` | **503**, 505 B | — | **Down** [API] |
-| **OATD** | `https://oatd.org/` | **403**, 5,207–5,442 B (Cloudflare "Just a moment…") to **all five** UAs incl. `robots.txt` | **7,407,210** ETDs from "over 1100" institutions (Wayback 2025-03-04) | **Alive, bot-walled** [WEB] |
-| **DART-Europe** | `https://www.dart-europe.org/` | **200** after redirect to `ucl.ac.uk` | — | **CLOSED PERMANENTLY 2025-02-03** [DOC] |
-| **CORE** | `https://api.core.ac.uk/v3/search/works/` | **200** | **7,921,188** works with `documentType:"thesis"` of **329,911,927** total | **Working, no key needed** [API] |
-| **BASE** | `https://www.base-search.net/Search/Results?…` | **200**, 7,846 B — Anubis interstitial `xess.min.css?cachebuster=v1.27.0+dirty` | — | **Proof-of-work walled** [WEB] |
-| **OpenAIRE** | `https://api.openaire.eu/search/publications?instancetype=…` | **200** | **3,158,600** Doctoral thesis · **2,661,863** Master thesis · **2,525,725** Thesis | **Working** [API] |
-
-### 2.2 NDLTD — the union catalogue is down
-
-NDLTD (the **Networked Digital Library of Theses and Dissertations**, https://ndltd.org/) is the
-international membership organisation for ETD practice: it runs the annual ETD Symposium, publishes
-the *ETD Journal*, gives the Innovative ETD Awards, and — historically — operated the **Global ETD
-Search**, the single largest thesis-specific union catalogue in the world.
-
-**The organisation is healthy. The search is not.**
-
-- `https://ndltd.org/` — HTTP 200, 135,318 B, a current WordPress site with board, committees,
-  membership and symposium pages [WEB] (S1).
-- `https://search.ndltd.org/` — **HTTP 503, a 505-byte stock nginx "503 Service Unavailable"
-  page** on 2026-09-04 [WEB] (S2). `http://search.ndltd.org/` 301s to the HTTPS form, which then
-  503s — i.e. the reverse proxy is up and the backend behind it is not.
-- `https://union.ndltd.org/OAI-PMH/?verb=Identify` — **HTTP 503, the same 505-byte nginx page**
-  [API] (S2). The OAI-PMH harvest endpoint is down with it.
-
-**When it broke, from the Wayback CDX index** [WEB] (S3):
-
-| Capture | Status |
-|---|---|
-| 2025-03-06, 2025-04-11, **2025-05-16** | **200** (2,254–2,372 B) |
-| 2025-06-13 | (no status recorded) |
-| **2025-08-07** onward — 2025-09, -10, -11, -12, 2026-01, -02, -03, -04, -06, -07, -08, **2026-09-01** | **301** (358–562 B) |
-
-So Global ETD Search served normally until at least **2025-05-16** and has been redirect-then-fail
-since **2025-08-07** — thirteen consecutive monthly captures. The `union.ndltd.org/OAI-PMH/` path
-has its own last-good capture on **2025-04-20** (S3). **This is not a transient outage; it is a
-service that has been unavailable for approximately thirteen months.**
-
-**The last measured size of the collection**, read from NDLTD's own front page in the 2025-05-16
-Wayback capture (S4):
-
-> "Search the **6,534,039** electronic theses and dissertations contained in the NDLTD archive"
-
-That figure is the best number this record can give for NDLTD, and it is **sixteen months stale**.
-Anyone quoting a current NDLTD size is quoting something they did not measure.
-
-**What NDLTD still gives you that nothing else does:** its
-[*List of Resources for Finding ETDs*](https://ndltd.org/thesis-resources/find-etds/) — HTTP 200,
-132,126 B [WEB] (S5) — is a maintained, country-by-country directory of national and regional ETD
-services, and it is the map §3 of this record is built on. It is a WordPress page on a live site
-and it is the single most useful surviving NDLTD asset. It is also, on the evidence of the search
-outage, a good `web.archive.org/save/` candidate under `AGENTS.md` rule 9.
-
-### 2.3 OATD — alive, and unreadable by a robot
-
-**OATD (Open Access Theses and Dissertations, https://oatd.org/)** is a hand-built ETD-specific
-search engine that harvests institutional repositories directly. It is the service most librarians
-recommend first, and it is **completely inaccessible to scripted retrieval on 2026-09-04.**
-
-Every path tried, including `robots.txt`, returned **HTTP 403 with a Cloudflare
-`<title>Just a moment...</title>` interstitial** [WEB] (S6):
-
-| User agent | Status | Body |
-|---|---|---|
-| Chrome 131 | 403 | 5,442 B |
-| `WhatsApp/2.23.20.0` | 403 | 5,228 B |
-| ClaudeBot | 403 | 5,442 B |
-| `curl/8.5.0` | 403 | 5,207 B |
-| Googlebot | 403 | 5,292 B |
-| Chrome 131 → `/robots.txt` | 403 | 5,493 B |
-| Chrome 131 → `/oatd/search?q=…` | 403 | 5,821 B |
-
-This is the **~5.2–5.9 kB Cloudflare managed-challenge fingerprint** already tabulated in
-[`retrieval-notes.md` §1](retrieval-notes.md). Under this survey's own rule that means **blocked,
-not broken** — OATD is running and refusing robots, and a human browser will get in.
-
-**OATD's own explanation, from its front page** [DOC] (S7) — it is candid about why:
-
-> "October 3, 2022. OATD is dealing with a number of misbehaved crawlers and robots, and is
-> currently taking some steps to minimize their impact on the system. This may require you to click
-> through some security screen. Our apologies for any inconvenience."
-
-**The count, from OATD's own counter** [WEB, via Wayback] (S7):
-
-| Date of capture | OATD's stated index size |
-|---|---|
-| 2024-04-01 | **7,421,247** |
-| 2025-01-01 | **7,206,043** |
-| **2025-03-04** (most recent readable capture) | **7,407,210** |
-
-Front-page wording at all three: *"Metadata (information about the theses) comes from over 1100
-colleges, universities, and research institutions. OATD currently indexes N theses and
-dissertations."*
-
-**Note the non-monotonicity.** The counter went 7,421,247 → 7,206,043 → 7,407,210, a ~215,000-record
-dip and partial recovery across eleven months. That is what re-harvesting an OAI-PMH federation
-looks like — a source repository that fails to answer during a harvest cycle drops out of the index
-and comes back later. **Treat any single OATD figure as ±3%, and never diff two of them to infer
-growth.** [INF]
-
-**Current OATD size: [NOT-VERIFIED].** What was tried: five user agents live (all 403), `robots.txt`
-(403), a search URL with full browser `Accept`/`Accept-Language` headers (403), and Wayback replay
-of the most recent captures (the last 200 in the CDX index is **2025-03-04**; every capture from
-2025-06-20 onward is itself a 403 of the Cloudflare page). No OAI-PMH, REST or JSON interface is
-advertised.
-
-### 2.4 DART-Europe — closed, permanently, on 2025-02-03
-
-**This is a second durability casualty and it is unambiguous.** `https://www.dart-europe.org/`
-returns HTTP 200 — but only after redirecting to a UCL Library Services page titled *"The
-DART-Europe e-theses portal has closed down"* [DOC] (S8). UCL's own words, verbatim:
-
-> "Please note that the DART-Europe e-theses portal was closed down permanently on **Monday 03
-> February 2025**.
->
-> We would like to thank all our partners and contributors over many years. Electronic research
-> theses can be found in several general open access aggregators, below, and in institutions'
-> individual open access repositories. **BASE · CORE · NDLTD (Global ETD Search and Find ETDs)**
->
-> The DART-Europe e-theses portal was a searchable database of open access electronic research
-> theses held in European repositories, with links to full text copies."
-
-Two things to draw out.
-
-**First, the successor advice is already partly wrong.** UCL points readers at three services.
-Measured on 2026-09-04: **BASE is behind an Anubis proof-of-work wall**, **NDLTD Global ETD Search
-returns 503**, and only **CORE** actually answers. A closure notice written in February 2025 has
-aged badly in nineteen months. This is exactly the pattern
-[`closed-and-defunct-servers.md` §2.4](closed-and-defunct-servers.md) documents for preprint
-servers — *the pointer outlives the thing it points at, and nobody updates it* — and it is worth
-noting that this is a **university library**, i.e. the institution most likely to maintain such a
-notice, and it still went stale.
-
-**Second, the count is unrecoverable in the ordinary way.** DART-Europe historically advertised a
-figure in the low millions of theses from several hundred European universities in tens of
-countries. **This record will not quote one**, because the portal is gone and no primary
-measurement was obtainable on the probe date. **DART-Europe record count and participating-country
-count: [NOT-VERIFIED].** What was tried: the live site (redirects to the closure notice, which
-contains no figures), and the closure notice itself. A Wayback replay of the pre-closure front page
-was not attempted within this pass's Internet Archive budget — it is the obvious next probe and is
-flagged in §13.
-
-### 2.5 CORE — the aggregator that actually works
-
-Covered as a *paper* source in
-[`open-access-full-text-sources.md`](open-access-full-text-sources.md). The ETD angle only, here.
-
-**CORE's v3 API answers unauthenticated `curl` and has a `documentType` field that includes
-`thesis`** [API] (S9), measured 2026-09-04:
-
-```bash
-# NOTE the trailing slash on /works/ — see the trap below
-curl -s -G "https://api.core.ac.uk/v3/search/works/" \
-     --data-urlencode 'q=documentType:"thesis"' --data-urlencode 'limit=1'
-```
-
-| Query | `totalHits` |
-|---|---|
-| `documentType:"thesis"` | **7,921,188** |
-| `*` (everything CORE holds) | **329,911,927** |
-
-So **theses are ~2.4% of CORE by record count**, and CORE's thesis holding is *larger than the last
-measured NDLTD union catalogue* (6.53 M) and comparable to OATD (7.41 M). Given that NDLTD is down
-and OATD is bot-walled, **CORE is currently the only large thesis index this survey could query
-programmatically.**
-
-**New API trap, worth propagating to [`retrieval-notes.md`](retrieval-notes.md):** requesting
-`https://api.core.ac.uk/v3/search/works` **without** the trailing slash returns **HTTP 200 with a
-Cloudflare `cdn-cgi/content` HTML redirect page**, not JSON — a `<meta http-equiv="refresh">`
-document pointing at the slashed URL. A JSON parser sees a parse error; a naive harvester that
-checks only the status code sees success. `.../works/` **with** the slash returns clean JSON. [API]
-
-CORE also exposes full text (it stores the PDFs it harvests), which for theses is the difference
-between a citation and a document.
-
-### 2.6 BASE — walled, and therefore unmeasured
-
-BASE (Bielefeld Academic Search Engine) indexes theses well — its advanced search has a document-type
-facet for theses, and NDLTD's own directory describes it as a *"Portal to 70 million documents in
-3000 repositories. Use Advanced Search to restrict queries to theses and dissertations."* [DOC]
-(S5).
-
-**Measured 2026-09-04:** `https://www.base-search.net/Search/Results?lookfor=riscv&type=all` →
-**HTTP 200, 7,846 bytes, `<title>Making sure you're not a bot!</title>`, stylesheet
-`/.within.website/x/xess/xess.min.css?cachebuster=v1.27.0+dirty`** [WEB] (S10). That is the
-**Anubis proof-of-work interstitial**, and [`retrieval-notes.md` §3](retrieval-notes.md) already
-records the decisive finding about it: **no user agent defeats it.** It is a JavaScript
-proof-of-work, not a UA filter.
-
-Consistent with the sibling record, **BASE's thesis count is [NOT-VERIFIED]** and its overall size
-remains unverified across this whole survey. The 70-million figure above is NDLTD quoting BASE, not
-a measurement — label it [DOC], treat it as indicative, and note that BASE publicly claims a
-substantially larger figure than that on its own front page, which we could not read.
-
-**The general rule from `retrieval-notes.md` §3 applies and is worth restating for ETDs
-specifically: when a thesis portal blocks you, go looking for OAI-PMH before concluding it is
-down.** Six of seven Anubis-walled scholarly hosts in the previous pass had an open machine
-interface behind the wall. For BASE specifically, no such interface was found.
-
-### 2.7 OpenAIRE — the best type-faceted numbers available
-
-OpenAIRE's legacy search API answers plain `curl`, needs no key, and has an `instancetype`
-parameter that distinguishes doctoral from master's work [API] (S11), measured 2026-09-04:
-
-```bash
-curl -s "https://api.openaire.eu/search/publications?instancetype=Doctoral+thesis&size=1&format=json"
-# → response.header.total.$
-```
-
-| `instancetype` | Records |
-|---|---|
-| **Doctoral thesis** | **3,158,600** |
-| **Master thesis** | **2,661,863** |
-| **Thesis** (unspecified level) | **2,525,725** |
-| *sum of the three* | *8,346,188* |
-
-**Do not sum those in a citation.** OpenAIRE deduplicates across sources but the three type buckets
-are separately assigned by contributing repositories, and a repository that labels everything
-`Thesis` contributes to the third bucket regardless of level. The sum is an upper bound. [INF]
-
-**API trap:** `?type=doctoralThesis` — the parameter name a reader would guess — returns **HTTP 400
-with a helpful exception body enumerating every supported parameter**. That is unusually good API
-behaviour and worth recording as a *positive* control: OpenAIRE tells you what it accepts. The
-supported list includes `instancetype`, `country`, `fos`, `openaireProviderID`, `peerReviewed`,
-`OA`, `green`, `openAccessColor` and `originalId`. [API]
-
-### 2.8 Google Scholar — brief and honest
-
-NDLTD's own directory entry for Google Scholar reads: *"Harvests theses and dissertations from
-virtually all registered open-access repositories."* [DOC] (S5)
-
-That is approximately true and it is why Google Scholar is, in practice, how most people find a
-thesis. **This record cannot verify anything about it.** Google Scholar has no API, forbids
-automated querying in its terms, blocks scripted access, and publishes no coverage statistics. Its
-thesis coverage, its recall, and its handling of embargoed records are all **[NOT-VERIFIED]** and
-will remain so — not because we did not try but because trying properly would mean circumventing an
-explicit access control, which `AGENTS.md` rule 7 forbids.
-
-**Two practical cautions that do not require measurement:**
-
-- Google Scholar's **"All N versions"** cluster is where a thesis usually surfaces next to its
-  papers. It is the single most useful UI affordance for this record's whole purpose, and it is
-  also the thing that most often silently merges a thesis with a *different* document by the same
-  author.
-- Scholar indexes the **repository landing page**, so an embargoed thesis appears as a normal hit
-  with a normal-looking link. §8 covers how to tell.
-
----
-
-## 3. The EThOS catastrophe — and its 2026 resolution
-
-This is the most instructive durability case study in this entire directory, because unlike the
-preprint-server failures in [`closed-and-defunct-servers.md`](closed-and-defunct-servers.md) — which
-were nearly all *front-door* failures with the corpus intact behind them — **EThOS was a genuine
-service destruction, and the recovery was partial, structural and permanent.** The service that came
-back is not the service that went away.
-
-### 3.1 What EThOS was
-
-EThOS (**E-Theses Online Service**), `https://ethos.bl.uk/`, run by the British Library, was the UK's
-national doctoral thesis service. Two functions, and it is essential to keep them apart:
-
-1. **A national union catalogue** of UK doctoral theses — metadata for every PhD awarded by a UK
-   higher-education institution, back to the eighteenth century.
-2. **A digitisation and supply service.** If a thesis existed only on paper, you could request a
-   scan through EThOS; the British Library digitised it, hosted the PDF, and delivered it. For a
-   large fraction of pre-2000 UK doctoral work **EThOS was the only digital copy in existence.**
-
-Function (1) survived. **Function (2) did not.**
-
-### 3.2 The attack
-
-The British Library's own statement, `https://www.bl.uk/cyber-incident/` → 302 →
-`https://www.bl.uk/about/cyber-attack`, HTTP 200, 133,713 B, retrieved 2026-09-04 [DOC] (S12):
-
-> "In **October 2023** the British Library experienced a significant cyber-attack that disrupted many
-> of our services. We are working to restore full functionality."
->
-> "In **November 2023** the attackers released some of our data onto the dark web including some
-> personal user information."
->
-> "The attack caused **multiple capabilities to be destroyed simultaneously** which has required a
-> **rebuild of our entire technology infrastructure**, a process of considerable complexity."
->
-> "In **March 2024** we published a paper about the attack and its impact … Its goal is to share our
-> understanding of what happened and to help others learn from our experience."
-
-Note the phrase *"destroyed simultaneously"* and *"rebuild of our entire technology infrastructure"*.
-This was not a defacement or a data breach with systems intact. This is the reason EThOS took
-**roughly two and a half years** to return.
-
-**The outage, measured from the Wayback CDX index for `ethos.bl.uk`** [WEB] (S13):
-
-| Period | CDX status |
-|---|---|
-| 2023-01 → **2023-10-08** | 301 (normal — the apex redirected to the service path) |
-| **2023-11, 2023-12, 2024-01, 2024-02** | **no captures at all** |
-| 2024-03-21 → 2026-02 | 307 / 308 (302–640 B) — a holding redirect, monthly, unchanging for ~24 months |
-| 2026-03-17, 2026-04-13 | 307 (594 B, 598 B) |
-| 2026-05-13, 2026-06-21, 2026-07-01 | 302 (589, 549, 553 B) |
-| 2026-08-24 | **403, 4,721 B** |
-| 2026-09-03 | 301, 1,165 B |
-
-The **four-month capture gap from November 2023 to February 2024** is the attack itself: the host
-was not answering at all. Everything from March 2024 to early 2026 is a stub.
-
-### 3.3 EThOS in 2026 — it is back, and it is a different thing
-
-**Verified live, 2026-09-04:** `https://ethos.bl.uk/` → **HTTP 200, 62,214 bytes** [WEB] (S14).
-
-The platform is **Hyku** (the multi-tenant Samvera/Hyrax distribution — the page title on error
-routes is literally `Hyku knap sack`), and the footer states: **"Platform provided by CoSector,
-University of London."** The British Library did not rebuild it in house.
-
-**The British Library's own statement of what changed**, from `https://ethos.bl.uk/about`, HTTP 200,
-57,645 B [DOC] (S15) — this is the single most important quotation in this record:
-
-> "EThOS (e-Theses Online Service) is an open access **discovery platform** for UK doctoral theses,
-> managed by the British Library. It aims to provide a national aggregated record of all doctoral
-> theses awarded by UK Higher Education institutions.
->
-> Following restoration work after a cyber-attack on the British Library in 2023, this platform is a
-> **metadata-only discovery service**, which we will continue to update with doctorates awarded since
-> October 2023 as part of our rolling programme of updates."
-
-And from the FAQ, `https://ethos.bl.uk/FAQs?locale=en`, HTTP 200, 84,307 B [DOC] (S16):
-
-> "**Why has EThOS been unavailable for a period?** EThOS was badly damaged by a cyber-attack on the
-> British Library in 2023 and has been unavailable since. **A new EThOS platform needed to be
-> procured, via a public tender process.** The metadata records of over 650,000 theses from UK
-> universities have been loaded onto the new platform. This includes around **14,000 additional
-> theses** that have been added to the service since the cyber-attack."
->
-> "**What is available on EThOS?** The new platform **does not hold full-text theses files to
-> download directly** but, where individual theses are available on a university repository, a link
-> is provided to access the file."
->
-> "It includes metadata records of over 650,000 theses from UK universities from the **1700s**
-> onwards. … **Over 400,000 theses are openly available for download from university repositories.**"
->
-> "**Can I request a thesis for digitisation?** You can request digitisation of some print-only
-> theses **by emailing the relevant university library**. At this stage, universities can still
-> request digitisation of theses and the files will be **returned to the university for upload to
-> their own repository**."
->
-> "**Later in 2026, we will begin the next phase of work** to assess how the restored version of
-> EThOS is being received by our users."
-
-**Read those together and the structural change is clear.** The British Library has exited the
-business of *holding* UK theses. EThOS is now a pure discovery-and-referral layer over
-**institutional repositories**, and the digitisation service has been devolved to individual
-university libraries, which now host the resulting files themselves. **The answer to "where are UK
-theses now discoverable" is: EThOS for the index, and the awarding university's own repository for
-the document.** There is no replacement national full-text store, and none is proposed.
-
-### 3.4 The size of the restored service — measured, not quoted
-
-The British Library says "over 650,000". **We measured it**, and the route is worth documenting
-because it is the only machine-readable interface the new platform exposes.
-
-Hyku publishes a **ResourceSync** capability list. `https://ethos.bl.uk/capabilitylist?locale=en` →
-HTTP 200, 457 B [API] (S17):
-
-```xml
-<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
-        xmlns:rs="http://www.openarchives.org/rs/terms/">
-  <rs:ln rel="up" href="https://ethos.bl.uk/.well-known/resourcesync"/>
-  <rs:md capability="capabilitylist"/>
-  <url><loc>https://ethos.bl.uk/resourcelist</loc><rs:md capability="resourcelist"/></url>
-  <url><loc>https://ethos.bl.uk/changelist</loc><rs:md capability="changelist"/></url>
-</urlset>
-```
-
-`https://ethos.bl.uk/resourcelist` → **HTTP 200, 88,402,587 bytes**, `capability="resourcelist"`,
-`at="2026-09-06T16:32:22Z"` [API] (S17). Counted:
-
-| Measure | Value |
-|---|---|
-| **`<loc>` entries, all `concern/thesis_or_dissertations/`** | **654,832** |
-| Lowest record id | 232,781 |
-| Highest record id | 906,226 |
-| `lastmod` 2026-03 | 47,452 |
-| **`lastmod` 2026-04** | **546,764** |
-| `lastmod` 2026-05 | 4,539 |
-| `lastmod` 2026-06 | 24,773 |
-| `lastmod` 2026-07 | 149 |
-| `lastmod` 2026-08 | 29,556 |
-| `lastmod` 2026-09 (to the 6th) | 1,599 |
-
-**654,832 records.** That is a hard number from the operator's own machine interface and it confirms
-"over 650,000" precisely.
-
-**The `lastmod` histogram is the reload signature.** 83.5% of all records were last modified in
-**April 2026**, with a further 7.2% in March 2026. That is a bulk ingest, not organic accrual — the
-metadata was loaded onto the new platform in **March–April 2026**, and the trickle since (May
-onward, ~60,000 records) is the rolling update programme the FAQ describes. [INF, from API data]
-
-Combined with the Wayback capture series (§3.2), which shows the holding redirect changing shape in
-March–April 2026 and settling to a 302 by May, the **public relaunch of EThOS falls in roughly
-2026-04 to 2026-05.** [INF] No press announcement was located within this pass — **the exact
-relaunch date is [NOT-VERIFIED].**
-
-### 3.5 Record shape, identifiers, and the legacy-URL result
-
-A live record, `https://ethos.bl.uk/concern/thesis_or_dissertations/906226` → HTTP 200, 69,494 B
-[WEB] (S18). Fields present: **Author · Qualification Name · University · Date Awarded · Awarding
-Institution · Language · Subject Discipline · Access Thesis · EThOS ID**.
-
-- **The identifier is `uk.bl.ethos.<n>`** and the numeric part is the URL path component. So
-  `uk.bl.ethos.906226` ⇒ `https://ethos.bl.uk/concern/thesis_or_dissertations/906226`. There is **no
-  DOI** on EThOS records.
-- Where the university repository holds a copy, the record carries an **"Access thesis from
-  university"** button. Where it does not, the record says so explicitly — the probed record read:
-  *"EThOS does not have a link to a university copy of this thesis. If you would like to view this
-  thesis, we recommend that you contact Royal Veterinary College."*
-- `Subject Discipline` was **"Not yet classified"** on the record probed. Subject classification is
-  visibly incomplete on the reloaded corpus. [WEB]
-
-**The finding that matters most for anyone with old citations: the legacy EThOS URL form still
-resolves.**
-
-| Probe | Result |
-|---|---|
-| `https://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.906226` | **HTTP 200 → redirects to `/concern/thesis_or_dissertations/906226`**, 69,494 B |
-| `https://ethos.bl.uk/concern/thesis_or_dissertations/99999999` *(negative control)* | **HTTP 404, 1,676 B** (`Hyku knap sack` error page) — clean |
-| `https://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.99999999` *(negative control)* | ⚠ **HTTP 200, 62,214 B — silently lands on the home page** |
-
-**Two consequences.**
-
-*Good news:* the `OrderDetails.do?uin=…` URLs embedded in a decade and a half of bibliographies,
-repository records and the EThOS CSV dataset itself **still work**. Someone deliberately built a
-compatibility shim into the new platform. Given how rarely that happens — see
-[`closed-and-defunct-servers.md` §2.3](closed-and-defunct-servers.md) on platform migrations
-breaking URL grammar — it deserves naming as good practice.
-
-*Bad news, and it is a new probing trap:* **the legacy route has no negative signal.** A bogus
-`uin` returns HTTP 200 with the 62,214-byte home page, byte-identical to a successful load of `/`.
-A link-checker walking a bibliography of `OrderDetails.do` URLs will report **100% success**
-regardless of whether the records exist. **Validate against the modern `/concern/…` path, which
-404s honestly.** [WEB]
-
-### 3.6 Did the EThOS data survive? Yes — and it is downloadable right now
-
-This was the open question, and the answer is unambiguously yes.
-
-The British Library published the **complete EThOS bibliographic metadata as a CC-BY dataset**,
-repeatedly, on its own research repository. Queried via the **DataCite API** on prefix `10.23636`
-[API] (S19):
-
-| DOI | Year | Title | Type |
-|---|---|---|---|
-| **`10.23636/rcm4-zk44`** | **2023** | **UK Doctoral Thesis Metadata from EThOS** | Dataset — **the final release** |
-| `10.23636/vtpx-we51` | 2023 | UK Doctoral Thesis Metadata from EThOS | Dataset — superseded by the above |
-| `10.23636/j278-4b96` | 2022 | UK Doctoral Thesis Metadata from EThOS | Dataset |
-| `10.23636/kvwc-ty06` | 2022 | UK Doctoral Thesis Metadata from EThOS | Dataset |
-| `10.23636/ybpt-nh33` | 2021 | UK Doctoral Thesis Metadata from EThOS | Dataset |
-| `10.23636/1344` | 2021 | UK Doctoral Thesis Metadata from EThOS | Dataset |
-| `10.23636/1188` | 2020 | UK Doctoral Thesis Metadata from EThOS | Dataset |
-| `10.23636/1156` | 2020 | EThOS metadata files augmented with identifiers | Dataset |
-| `10.23636/1137` | 2019 | UK Doctoral Thesis Metadata from EThOS | Dataset |
-| `10.23636/9h0m-3974` | 2023 | Surfacing the impact of international doctoral research: Working with the EThOS collection | Report |
-| `10.23636/1181` | 2020 | Introduction to EThOS: the British Library database of UK theses | InteractiveResource |
-| `10.23636/1162` | 2014 | Text and Data Mining in EThOS | Text |
-
-**DataCite metadata for the final release `10.23636/rcm4-zk44`** [API] (S19):
-
-- Publisher: **British Library** · Issued **2023** · DataCite record **created 2023-11-27T17:07:22Z**
-- Licence: **CC-BY 4.0** (`rightsIdentifier: cc-by-4.0`)
-- Abstract, verbatim: *"The data in this collection comprises the bibliographic metadata for all UK
-  doctoral theses listed in EThOS, the UK's national thesis service. **We estimate the data covers
-  around 98% of all PhDs ever awarded by UK Higher Education institutions, dating back to 1787.**
-  Thesis metadata from every PhD-awarding university in the UK is included."*
-
-**The DataCite record was created on 2023-11-27 — a month after the attack.** The dataset release
-was pushed out during the incident.
-
-**We verified the file is actually retrievable.** The BL Research Repository has itself migrated
-since (from Hyrax to **DSpace-CRIS**, with the old `bl.iro.bl.uk/concern/datasets/<uuid>` URLs
-302-redirecting to `bl.iro.bl.uk/entities/product/<new-uuid>`). Using the DSpace 7 REST API
-[API] (S20):
-
-```bash
-# item → bundles → bitstreams → content
-curl -s "https://bl.iro.bl.uk/server/api/core/items/ef18a65d-a839-428b-abbc-2da178007e4e"
-curl -s "https://bl.iro.bl.uk/server/api/core/items/ef18a65d-a839-428b-abbc-2da178007e4e/bundles"
-curl -sL -H 'Range: bytes=0-3000' \
-  "https://bl.iro.bl.uk/server/api/core/bitstreams/a10353df-67a5-4d47-9d33-4c764f605eb5/content"
-```
-
-| Property | Value |
-|---|---|
-| Item handle | **`britishlibrary-iro/19931`** |
-| `dc.identifier.doi` | `10.23636/rcm4-zk44` |
-| Bundles | `ORIGINAL`, `TEXT`, `TEXT` |
-| Bitstream | **`EThOS_CSV_202310.csv`** |
-| **Size** | **709,733,446 bytes (≈709.7 MB)** |
-| Range fetch | **HTTP 206**, `content-type: text/csv`, `content-range: bytes 0-3000/709733446` |
-| Delivery | 302 to a signed `cf002.cdn.4science.cloud` CloudFront URL (`Expires`/`Signature`/`Key-Pair-Id`) |
-
-**The filename is the finding.** `EThOS_CSV_202310` — **October 2023**. The final EThOS metadata
-snapshot is dated to the month of the attack, and it is a complete, open, 709 MB CSV that anyone can
-download today.
-
-**And the columns are exactly what this record needs** (first 3,001 bytes, verbatim header):
-
-```
-Title,DOI,Author,Author ISNI,ORCID,Institution,Institution ISNI,Date,Qualification,
-Abstract,Subject Discipline,Supervisor(s),Funder(s),EThOS URL,IR URL
-```
-
-Note **`Supervisor(s)`** and **`IR URL`**. This is a 709 MB, CC-BY, offline-queryable table of
-~650,000 UK doctorates with **author, supervisor, institution, abstract, funder, and a direct link
-to the institutional-repository copy.** For the advisor-lineage technique in §5.8 it is the single
-best dataset in this entire survey, and it works with no network access to any thesis portal at all.
-
-A verbatim sample row, showing the `EThOS URL` column uses the legacy `OrderDetails.do` form
-(§3.5 — which still resolves):
-
-```
-Computation and measurement of turbulent flow through idealized turbine blade passages, ,
-"Loizou, Panos A.",https://isni.org/isni/0000000136122593, ,University of Manchester,
-https://isni.org/isni/0000000121662407,1989,Thesis (Ph.D.), ,Physical Sciences, , ,
-https://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.232781,
-```
-
-### 3.7 What was actually lost
-
-Being precise, because the temptation is to over- or under-state it.
-
-| Asset | Fate |
-|---|---|
-| Bibliographic metadata for ~650,000 UK doctorates | **Survived completely.** On the new platform (654,832 records) *and* as an open 709 MB CC-BY CSV |
-| Discovery service | **Restored**, on new infrastructure, ~2.5 years later |
-| Legacy `OrderDetails.do` URLs in the literature | **Survived** — compatibility shim in place |
-| **The British Library's own digitised full-text thesis files** | **Not restored.** EThOS "does not hold full-text theses files to download directly" [DOC] |
-| **The national digitisation-on-demand service** | **Devolved.** Requests now go to the awarding university library; files go to *their* repository |
-| Personal user account data | Partly exfiltrated and released on the dark web, Nov 2023 [DOC] |
-| The ~2.5 years of UK theses awarded during the outage | Partially caught up — "around 14,000 additional theses" loaded [DOC] |
-
-**The irreplaceable loss is the pre-digital tail.** For a UK thesis from, say, 1962 that was
-digitised only because someone once paid EThOS to scan it, the British Library's copy is no longer
-served and the awarding university may never have had one. §3.3's FAQ answer is explicit that such
-records now show "only the metadata record is available … available as a paper copy in a university
-library". **[NOT-VERIFIED]:** how many previously-digitised files fall into this category, and
-whether the BL retains them internally. No public statement quantifying this was located.
-
-### 3.8 How this parallels — and departs from — [`closed-and-defunct-servers.md`](closed-and-defunct-servers.md)
-
-That record's headline finding is: **"Preprint servers do not lose data. They lose front doors."**
-Seventeen of eighteen dead servers still served their corpus.
-
-**EThOS is the counterexample that sharpens the rule.** Map it onto that record's failure taxonomy:
-
-| Failure mode from `closed-and-defunct-servers.md` §2 | EThOS |
-|---|---|
-| Publisher strategy change | No |
-| Founder retirement / single maintainer | No |
-| Platform migration breaking URL grammar | **Inverted** — a migration that *preserved* URL grammar |
-| Domain lapse to a squatter | No — `ethos.bl.uk` was held throughout |
-| TLS as an abandonment signal | **Useless here.** The domain kept valid certs and served monthly 307s for two years while the service was destroyed |
-| **Catastrophic infrastructure destruction** | **Yes — a mode that record did not observe at all** |
-
-And the durability lesson generalises cleanly to this survey's standing advice:
-
-1. **The DOI'd, CC-BY bulk dataset is what saved EThOS**, not the website. `10.23636/rcm4-zk44`
-   resolved and delivered a 709 MB file throughout the outage. This is precisely
-   [`reliability-and-durability.md` §6](reliability-and-durability.md)'s "cite the DOI, and archive a
-   copy yourself", validated by a real disaster.
-2. **A live hostname with a valid certificate answering HTTP 307 every month for 24 months looked,
-   to every automated checker, exactly like a healthy site.** Reinforces
-   [`retrieval-notes.md` §8](retrieval-notes.md): TLS and status codes are not liveness.
-3. **Metadata is cheap to preserve and full text is not.** The British Library restored the part
-   that fit in a CSV and permanently devolved the part that did not. Expect this asymmetry
-   everywhere.
-
----
-
-## 4. National and regional ETD systems
-
-The pattern below is consistent enough to state up front: **national thesis portals are more fragile
-than institutional repositories, and the good ones are the ones with an API.** Three of the fifteen
-systems probed here are dead or discontinued; four more are alive but unreadable by a robot.
-
-### 4.1 Status table
-
-All probes **2026-09-04**. "Chrome 131" = the rung-2 agent from
-[`AGENTS.md`](../../AGENTS.md). `000` = TCP/TLS failure, not an HTTP status.
-
-| System | Country/region | Endpoint probed | Status | Measured | Verdict |
-|---|---|---|---|---|---|
-| **theses.fr** | France | `theses.fr/api/v1/theses/recherche/?q=*&nombre=1` | **200** | **564,318** theses · **918,602** persons | **Best API in this table** [API] |
-| **TEL** | France | `api.archives-ouvertes.fr/search/tel/` | **200** | **180,693** = 171,839 `THESE` + 8,854 `HDR` | Works; HAL infrastructure [API] |
-| TEL (web) | France | `theses.hal.science/` | 200, 12,607 B | — | **Anubis** `xess.css?cachebuster=devel` [WEB] |
-| **DiVA** | Sweden / Nordic | `diva-portal.org/dice/oai?verb=Identify` | **200** | **800,381** records (all types) | OAI-PMH open [API] |
-| **DNB** | Germany | `services.dnb.de/oai/repository?verb=Identify` | **200**, 779 B | `earliestDatestamp` **1945-01-01** | OAI-PMH open [API] |
-| DNB (web) | Germany | `portal.dnb.de/opac.htm` | 200, 4,475 B | — | **Anubis** `xess.min.css?cachebuster=1.25.0` [WEB] |
-| **TDX / TDR** | Catalonia / Spain | `tdx.cat/` · `/oai/request` · `/handle/10803/1234` | **403** · 5,658 / 5,769 / 5,730 B | — | **Cloudflare, all paths.** Handle prefix **10803** [WEB] |
-| **RCAAP** | Portugal | `rcaap.pt/` · `/OAIHandler?verb=Identify` | 200, 4,511 B | — | **Anubis, incl. OAI** `v1.26.0-pre2` [WEB] |
-| **Trove** | Australia | `trove.nla.gov.au/` | 200, 7,745 B | — | **Anubis** `v1.26.2` [WEB] |
-| **Shodhganga** | India | `shodhganga.inflibnet.ac.in/` | **200**, 515,934 B (13–21 s; 1 of 4 attempts timed out) | **697,675** full-text theses · 21,723 synopses · **908** contributing universities | Live, slow [WEB] |
-| **CiNii Dissertations** | Japan | `cir.nii.ac.jp/opensearch/dissertations?format=json&from=1900` | **200** | **775,786** dissertations | Works; folded into CiNii Research [API] |
-| **RISS** | Korea | `riss.kr/index.do` | **200**, 390,685 B | count not extracted | Live [WEB] |
-| **CAPES Catálogo de Teses** | Brazil | `catalogodeteses.capes.gov.br/` | **000** | — | **Unreachable** (IPv4 *and* IPv6) [WEB] |
-| **BDTD** (IBICT) | Brazil | `bdtd.ibict.br/vufind/` | 200, 1,697 B | — | Challenge page *"Verificando conexão \| Oasisbr"* [WEB] |
-| **NARCIS** | Netherlands | `narcis.nl/` → `dans.knaw.nl/nl/data-diensten/narcis/` | 200 (Anubis at target) | — | **SERVICE ENDED 2023-07-03** [DOC] |
-| **Cybertesis** | Latin America | `cybertesis.net/` (http) | 200 | — | **DOMAIN PARKED / MONETISED** [WEB] |
-| **Theses Canada** | Canada | `bac-lac.gc.ca/…/theses-canada.aspx` · `library-archives.canada.ca/…` · search | **000** · **302 → canada.ca** · **403** 5,775 B | — | Old URLs dead; search Cloudflare-walled [WEB] |
-| **TESEO** | Spain | `educacion.gob.es/teseo/…` → `aplicaciones.ciencia.gob.es/teseo` | **302 → 000** | — | Migrated; new host unreachable [WEB] |
-| **Tez Merkezi** | Turkey | `tez.yok.gov.tr/UlusalTezMerkezi/giris.jsp` | **200**, 33,811 B | count not extracted | Live [WEB] |
-| **CNKI** | China | `cnki.net/` → `oversea.cnki.net/index/` | **200**, 50,542 B | — | Live, **paywalled** [WEB] |
-| **Wanfang** | China | `wanfangdata.com.cn/` | **200**, 216,413 B | — | Live, **paywalled** [WEB] |
-
-**The single most striking pattern in that table is Anubis.** Four national thesis portals —
-`theses.hal.science`, `portal.dnb.de`, `www.rcaap.pt`, `trove.nla.gov.au` — plus `base-search.net`
-are now behind **Anubis proof-of-work interstitials**, at four *different* versions (`devel`,
-`1.25.0`, `v1.26.0-pre2`, `v1.26.2`, `v1.27.0+dirty`). [`retrieval-notes.md` §3](retrieval-notes.md)
-recorded Anubis on seven scholarly hosts in the previous pass; **it has since spread to the national
-ETD layer.** Per that record's decisive finding, **no user agent defeats it** — and this pass
-confirms that on `www.rcaap.pt`, where the **OAI-PMH endpoint itself is behind the wall**, breaking
-the usual "look for OAI-PMH" escape hatch. RCAAP is the first host in this survey where that rule
-failed.
-
-### 4.2 France — theses.fr and TEL, and why there are two
-
-France is the only country in this table with **two** national thesis services, and the split is
-worth understanding because it is not redundancy.
-
-**`theses.fr`** (ABES — the Agence bibliographique de l'enseignement supérieur) is the **registry**:
-the authoritative record of every French doctorate, including theses *in preparation*. Its API is
-the best-documented and most generous encountered anywhere in this record [API] (S21):
-
-```bash
-curl -s "https://theses.fr/api/v1/theses/recherche/?q=*&nombre=1"     # → totalHits 564318
-curl -s "https://theses.fr/api/v1/personnes/recherche/?q=*&nombre=1"  # → totalHits 918602
-curl -s "https://theses.fr/api/v1/theses/these/2016PA066033"          # → one record by NNT
-```
-
-| Measure | Value |
-|---|---|
-| `theses` `totalHits` | **564,318** |
-| `personnes` `totalHits` | **918,602** |
-| `q=RISC-V` | **102** |
-
-- **The identifier is the NNT** (*Numéro National de Thèse*), e.g. `2016PA066033` — year, then an
-  establishment code, then a sequence. It is stable and it is what French bibliographies cite.
-- **theses.fr now mints DOIs.** The record for `2016PA066033` carries
-  `"doi":"10.70675/ff0868d0z67ecz4e1bzb948zaa766df489f9"` [API]. Prefix **`10.70675`**. This is new
-  and it materially improves French thesis citability — most national systems in this table mint
-  nothing.
-- **The `personnes` endpoint is the advisor-lineage tool.** A person record carries a `roles` object
-  counting the person's appearances as *Président / Présidente du jury*, *Examinateur /
-  Examinatrice*, *Rapporteur*, and (in the thesis records) `directeurs`. **You can walk a French
-  supervisor's entire student list from a public API with no key.** Nothing else in this record
-  offers that. See §5.8 and §11.
-- **API trap:** `GET /api/v1/theses/these/<bogus-NNT>` returns **HTTP 200 with a zero-byte body** —
-  not a 404. Verified with `9999ZZZZ9999`. A harvester checking status codes sees success; a JSON
-  parser gets an EOF error. **Test for a non-empty body.** [API]
-
-**TEL** (*thèses-en-ligne*, `https://theses.hal.science/`) is the **full-text archive**, and it is
-built on HAL — see [`hal.md`](hal.md), which records that CCSD attributes the year **2001** to TEL
-specifically (and 2002 to HAL itself), correcting Wikipedia. TEL is therefore queryable through
-HAL's Solr API with the `tel` portal path [API] (S22):
-
-```bash
-curl -s "https://api.archives-ouvertes.fr/search/tel/?q=*:*&rows=0&wt=json"
-```
-
-| Facet | Count |
-|---|---|
-| **Total** | **180,693** |
-| `docType_s:THESE` | **171,839** |
-| `docType_s:HDR` (*habilitation à diriger des recherches*) | **8,854** |
-
-**The HDR bucket is a French-specific bonus.** An *habilitation* is a senior researcher's synthesis
-of a decade of work written to qualify them to supervise doctorates. For a reader trying to
-understand a French lab's overall programme, an HDR is frequently a better document than any
-individual paper — it is a self-written, referenced survey by the person who ran the group. 8,854 of
-them are free.
-
-**TEL by subject** [API] (S22) — using `domainAllCode_s`, which is the correct field
-([README §6](README.md#6-probing-traps): `domain_s` silently returns zero):
-
-| Code | Subject | Theses |
-|---|---|---|
-| `spi.other` | Engineering sciences, other | **7,370** |
-| `info.info-mo` | Modelling and simulation | **3,408** |
-| `chim.mate` | Materials chemistry | 3,683 |
-| `spi` | Engineering sciences (top level) | 3,673 |
-| `info.info-oh` | Other computer science | 2,977 |
-| `spi.nano` | **Micro and nanotechnologies / microelectronics** | **2,831** |
-| `info` | Computer science (top level) | 2,813 |
-| `spi.auto` | **Automatic control / robotics** | **2,599** |
-| `info.info-ai` | Artificial intelligence | 2,574 |
-| `info.info-ni` | **Networking and internet architecture** | **2,317** |
-| `spi.signal` | **Signal and image processing** | **2,247** |
-| `spi.tron` | **Electronics** | **1,754** |
-| `info.info-cr` | **Cryptography and security** | **1,035** |
-| `spi.elec` | **Power electronics / electrical engineering** | **711** |
-| `info.info-es` | **Embedded systems** | **474** |
-| `info.info-ar` | **Computer architecture / hardware** | **275** |
-
-**That is the single most useful subject breakdown in this record.** `spi.nano` (2,831),
-`spi.tron` (1,754), `spi.signal` (2,247), `info.info-es` (474) and `info.info-ar` (275) are, between
-them, roughly **7,500 free full-text French dissertations in microelectronics, electronics, signal
-processing, embedded systems and computer architecture** — the LIRMM, TIMA, IEMN, LAAS, CEA-Leti and
-INRIA output that [`hal.md`](hal.md) documents at the paper level, in its long form.
-
-**Retrieval note:** the `theses.hal.science` *website* is behind Anubis, but
-`api.archives-ouvertes.fr` is **completely open to default `curl`**. This is the canonical instance
-of [`retrieval-notes.md` §3](retrieval-notes.md)'s rule — the human-facing site is walled and the
-machine interface is not.
-
-### 4.3 Sweden and the Nordics — DiVA
-
-**DiVA** (*Digitala Vetenskapliga Arkivet*, `https://www.diva-portal.org/`) is a shared repository
-platform used by around fifty Swedish, and some Norwegian, institutions — including **KTH**,
-**Uppsala**, **Linköping**, **Chalmers-adjacent** bodies and **Blekinge Institute of Technology**.
-
-**OAI-PMH is open and clean** [API] (S23):
-
-```bash
-curl -s "https://www.diva-portal.org/dice/oai?verb=Identify"
-curl -s "https://www.diva-portal.org/dice/oai?verb=ListIdentifiers&metadataPrefix=oai_dc"
-```
-
-| Property | Value |
-|---|---|
-| `repositoryName` | **DiVA - Academic Archive On-line** |
-| `baseURL` | `http://services.diva-portal.org/dice/oai` |
-| `earliestDatestamp` | **1900-01-01T00:00:00Z** |
-| **`deletedRecord`** | **`persistent`** |
-| `resumptionToken` **`completeListSize`** | **800,381** |
-
-**`deletedRecord="persistent"` is the good value** — the same guarantee arXiv gives
-([`reliability-and-durability.md` §4](reliability-and-durability.md)): deletions are tombstoned, not
-silently dropped, so an incremental harvester can stay consistent.
-
-**800,381 is all record types**, not theses. DiVA's set list is organised by broad subject
-(`PhysicsChemistryMaths`, `LifeEarthScience`, …) and by contributing institution
-(`SwePub-kth`, `SwePub-liu`, `SwePub-bth`, …), with **no publication-type set**, so the
-doctoral-thesis subset cannot be isolated through OAI. The `smash` web search *does* have
-`publicationTypeCode:comprehensiveDoctoralThesis` / `monographDoctoralThesis` facets, but it
-requires a JSF session (`dswid`) and returned a 4,481-byte stub to a stateless request.
-**DiVA thesis-only count: [NOT-VERIFIED].**
-
-**Why DiVA matters here:** Sweden's *sammanläggningsavhandling* (compilation thesis) convention means
-a large fraction of DiVA doctoral theses are **"kappa + papers"** — an extended synthesis chapter
-wrapped around the constituent papers. The kappa is often 40–80 pages and is frequently the only
-place the *system*-level argument, the integration work and the cross-paper measurements are written
-down. For KTH hardware and networking work specifically, the kappa is the document to read.
-
-### 4.4 Germany — DNB and the fate of DissOnline
-
-**DissOnline** was the DNB's dedicated dissertation portal. It no longer exists as a separate
-service; German dissertation records are served through the **Deutsche Nationalbibliothek** catalogue
-itself, which by statute receives a copy of every German dissertation.
-
-- `https://portal.dnb.de/opac.htm` → **HTTP 200, 4,475 B, Anubis** [WEB] (S24). The catalogue front
-  end is proof-of-work walled.
-- `https://services.dnb.de/oai/repository?verb=Identify` → **HTTP 200, 779 B, clean OAI-PMH XML**
-  [API] (S24):
-
-```xml
-<repositoryName>OAI-Repository of the German National Library V2.0.11</repositoryName>
-<baseURL>https://services.dnb.de/oai/repository</baseURL>
-<earliestDatestamp>1945-01-01T00:00:00Z</earliestDatestamp>
-<deletedRecord>transient</deletedRecord>
-<granularity>YYYY-MM-DDThh:mm:ssZ</granularity>
-```
-
-Another clean instance of the wall-the-site / open-the-API pattern. Note `deletedRecord="transient"`
-— **weaker than DiVA's `persistent`**: the DNB does not promise to keep tombstones, so an
-incremental harvester can silently drift.
-
-**German dissertation count: [NOT-VERIFIED].** What was tried: the OAI `Identify` verb (gives no
-count), and the walled portal. A `ListIdentifiers` walk over the relevant set would give it but was
-not run within this pass's budget. German university repositories are the practical route — see
-§5, and note that German doctoral regulations mandate *Veröffentlichung* (publication), which is why
-German dissertation availability is unusually good.
-
-### 4.5 Spain and Portugal — TDX/TDR and RCAAP, both walled
-
-**TDX** (*Tesis Doctorals en Xarxa*) / **TDR** (*Tesis Doctorales en Red*),
-`https://www.tdx.cat/` — the Catalan-led consortial repository covering Catalonia and much of Spain.
-**HTTP 403 with the ~5.7 kB Cloudflare interstitial on every path tried**, including
-`/oai/request?verb=Identify` and an individual `/handle/10803/1234` [WEB] (S25).
-
-**But TDX is handle-based, and Handle.net is not walled.** This is the workaround, and it
-generalises (§10):
-
-```bash
-curl -s "https://hdl.handle.net/api/handles/10803/1234"
-# {"responseCode":1,"handle":"10803/1234","values":[{"index":100,"type":"URL",
-#  "data":{"value":"https://www.tdx.cat/handle/10803/1234"}, ...}]}
-
-curl -s "https://hdl.handle.net/api/handles/10803/99999999"
-# {"responseCode":100,"handle":"10803/99999999"}          ← clean negative control
-```
-
-**`responseCode: 1` = exists; `responseCode: 100` = does not.** A JSON existence oracle for any
-handle-minting repository, immune to the target's bot wall. This is strictly better than the
-`doi.org` 403-passthrough trick in [`retrieval-notes.md` §4](retrieval-notes.md), because it returns
-structured data rather than requiring you to interpret an error. **TDX record count:
-[NOT-VERIFIED]** — no unwalled count interface found.
-
-**RCAAP** (*Repositório Científico de Acesso Aberto de Portugal*), `https://www.rcaap.pt/` —
-**Anubis on the front page and on `/OAIHandler?verb=Identify` alike** (4,511 B, `v1.26.0-pre2`)
-[WEB] (S26). `https://www.rcaap.pt/oai/?verb=Identify` returns HTTP 400 with a Thymeleaf-rendered
-*"OAI-PMH Data Provider"* error page, confirming a provider exists at some path but not telling us
-which. **RCAAP is the one host in this pass where the "go round the wall via OAI-PMH" rule failed.**
-Count: **[NOT-VERIFIED].**
-
-### 4.6 Australia — Trove, and the ADT it absorbed
-
-**Trove** (`https://trove.nla.gov.au/`, National Library of Australia) returned **HTTP 200, 7,745 B,
-Anubis `v1.26.2`** [WEB] (S27).
-
-Trove absorbed the **Australasian Digital Theses (ADT) Program**, the country's federated ETD
-programme, which ceased as a separate service; Australian theses are now discoverable through Trove
-and through the individual university repositories. **This record verified Trove's reachability
-state and nothing else.** The ADT absorption is **[NOT-VERIFIED] as to date and mechanism** — no
-primary source was retrieved for it within this pass, because the NLA's own pages are behind the
-proof-of-work wall.
-
-Trove has a well-documented **API requiring a free registered key**. No key was obtained, so no
-count was measured. This is an access control, not a bot wall, and `AGENTS.md` rule 7 applies —
-register properly rather than routing around it. **Trove thesis count: [NOT-VERIFIED].**
-
-### 4.7 India — Shodhganga, and it is genuinely large
-
-**Shodhganga@INFLIBNET** (`https://shodhganga.inflibnet.ac.in/`) is the Indian national ETD
-repository, run by the INFLIBNET Centre under the Ministry of Education, and it is mandatory: UGC
-regulations require Indian universities to deposit PhD theses. That mandate is why it is one of the
-largest single-country full-text thesis collections on earth.
-
-**Measured from its own front-page counters, 2026-09-04** [WEB] (S28):
-
-| Counter | Value |
-|---|---|
-| **Full Text Theses** | **697,675** |
-| SYNOPSES / MRPs / PDFs / Fellowships (Shodhgangotri) | **21,723** |
-| **Universities Contributing** | **908** |
-| Universities + CFTIs/INIs with signed MoU | **1,060** |
-| (navigation) MoU with Universities · MoU with CFTI | 943 · 117 |
-
-Announcements on the same page give the growth curve in Indian numbering [WEB] (S28):
-
-> "Shodhganga crossed **5,35,000** Theses on **27th May 2024**."
->
-> "Shodh ganga has crossed the remarkable milestone of **6,00,000** Theses. The Hon'ble Director,
-> INFLIBNET Centre, Prof. Devika P. Madalli, marked this occasion by uploading the 6,00,000th
-> thesis."
-
-535,000 (May 2024) → 600,000 → **697,675** (September 2026). Roughly **70,000 theses a year**, all
-full text, all free.
-
-**⚠ New probing trap, and it is a nasty one.** The Shodhganga home page contains **a stale counter
-block inside an HTML comment**:
-
-```html
-<!-- counters -->
-<!--
-<div class="sg-counts-box">
-   ... <p class="sg-p">THESES</p> <span class="sg-span">597316</span>
-   ... <p class="sg-p">SYNOPSES</p> <span class="sg-span">15274</span>
--->
-```
-
-The live counter, outside any comment, reads `<span class="counter digifont" id="theses1">697675</span>`.
-**A text extractor that strips tags but does not strip HTML comments reads 597,316 — 100,359 too
-low.** Both numbers look equally plausible. There is also a commented-out `99999` placeholder
-immediately below the live counter, which would look like a real figure to a regex. **Strip comments
-before scraping any figure from a hand-maintained institutional page.** [WEB]
-
-**Reachability.** Four sequential requests to `https://shodhganga.inflibnet.ac.in/` gave
-`200 / 200 / 200 / 000`, with successful responses taking **13.5–21.1 seconds**. An initial
-Chrome-131 attempt timed out while a `curl/8.5.0` attempt succeeded, which *looked* like a reversed
-user-agent ladder — **but it did not reproduce.** It is a slow, intermittently-overloaded origin,
-not a UA filter. Recorded here explicitly because the tempting wrong conclusion was one probe away.
-`http://` (port 80) fails outright; use HTTPS. A `/oai/request?verb=Identify` probe returned `000`
-on the one attempt made — **Shodhganga OAI-PMH: [NOT-VERIFIED].** [WEB]
-
-**What is in it, and the caveat.** Shodhganga is real and useful — Indian institute-of-technology
-and NIT dissertations in VLSI, power electronics, antennas, embedded systems and communications are
-there in quantity and in full text. The honest caveat is §7's: quality varies enormously across 908
-contributing universities, and Shodhganga applies no quality gate of its own — it is a deposit
-mandate, not an editorial process. The page itself links UGC plagiarism notices from 2018 and 2020
-and a "Self Plagiarism" public notice, which tells you what the operators consider the live risk.
-
-**Shodhganga's browse interface includes a "Researcher/Guide" index** — i.e. you can browse by
-supervisor. That is directly the §5.8 technique, exposed as a first-class navigation option, and it
-is rare.
-
-### 4.8 Japan and Korea — CiNii Dissertations, RISS
-
-**CiNii Dissertations has been folded into CiNii Research**, but the dissertation endpoint survives
-as a first-class facet. `https://ci.nii.ac.jp/d/` — the old CiNii Dissertations URL, and the one
-still listed in NDLTD's directory — **302s to `https://cir.nii.ac.jp/`** [WEB] (S29).
-
-**The OpenSearch API answers JSON with no key** [API] (S29):
-
-```bash
-curl -s "https://cir.nii.ac.jp/opensearch/dissertations?format=json&count=1&from=1900"
-# → "opensearch:totalResults": 775786
-curl -s "https://cir.nii.ac.jp/opensearch/dissertations?q=RISC-V&format=json&count=1"
-# → 6
-curl -s "https://cir.nii.ac.jp/opensearch/all?q=RISC-V&format=json&count=1"
-# → 514
-```
-
-| Query | Results |
-|---|---|
-| `dissertations`, `from=1900` (or `1800`, or `1`) | **775,786** |
-| `dissertations`, `q=RISC-V` | **6** |
-| `all`, `q=RISC-V` | 514 |
-| `dissertations`, bogus term *(negative control)* | **0** — correct |
-| **`dissertations` with no parameters at all** | ⚠ **0** |
-
-**775,786 Japanese doctoral dissertations**, covering degrees conferred by Japanese universities and
-by NIAD-QE. A named example returned by the RISC-V query: *"Trusted Execution Environment with
-Silicon Level Root-of-Trust based on RISC-V Computer System"*.
-
-**⚠ The empty-query trap again.** `?format=json&count=1` with **no** `q` and **no** date range
-returns `totalResults: 0`. This is the **third independent instance** in this survey of the
-"empty query means match nothing, not match everything" failure —
-[`retrieval-notes.md` §7](retrieval-notes.md) already records it for **NASA NTRS** and **DOE OSTI**.
-Three unrelated national services, same trap. **Promote it from "a NASA/DOE quirk" to a general
-expectation about scholarly search APIs.** The workaround here is a wide date range; `q=*` also
-returns 0, so do not use it.
-
-**RISS** (*Research Information Sharing Service*, `https://www.riss.kr/index.do`, KERIS) returned
-**HTTP 200, 390,685 B** [WEB] (S30) — alive, no bot wall on the front page. It is the Korean union
-catalogue of academic information including domestic dissertations. **No count was extracted** —
-the site is a large session-driven Korean-language portal and no unauthenticated count endpoint was
-found within budget. **RISS dissertation count: [NOT-VERIFIED].**
-
-### 4.9 Brazil and Latin America — one unreachable, one dead
-
-**CAPES Catálogo de Teses e Dissertações** (`https://catalogodeteses.capes.gov.br/`) — **`000` on
-both IPv6 and IPv4** [WEB] (S31). DNS resolves to `2001:12f0:b27:1005::38` (AAAA) and
-`200.130.18.68` (A); `curl -4` and default both time out at 30–40 s. **This is recorded as
-"unreachable from this environment", not as "dead"** — the discipline
-[`retrieval-notes.md` §5](retrieval-notes.md) applies to `www2.eecs.berkeley.edu`. A Brazilian
-government host may simply be geofenced or slow. **CAPES status and count: [NOT-VERIFIED].**
-
-**⚠ Retrieval note worth propagating:** the default `getent hosts catalogodeteses.capes.gov.br`
-returned **only the AAAA record**, which makes the host look IPv6-only and the failure look like an
-IPv6 problem. `getent ahostsv4` shows an A record exists. **Check both families before diagnosing.**
-
-**BDTD** (*Biblioteca Digital Brasileira de Teses e Dissertações*, IBICT,
-`https://bdtd.ibict.br/vufind/`) is the better-known Brazilian aggregator and is what NDLTD's
-directory lists. It returned **HTTP 200, 1,697 B, a challenge page titled *"Verificando conexão |
-Oasisbr"*** [WEB] (S31) — alive, interstitial-walled, not measurable. **[NOT-VERIFIED].**
-
-**Cybertesis is dead, and the domain has been monetised.** This is the clearest single failure in
-this section [WEB] (S32):
-
-| Probe | Result |
-|---|---|
-| `https://www.cybertesis.net/` | **`000`** — TLS/TCP failure |
-| `http://www.cybertesis.net/` | **HTTP 200 → redirects to `welcome.lkg-app.com/?clickid=…&dkw=cybertesis.net&pid=…`**, 25,725 B, `<meta name="robots" content="noindex, nofollow">` |
-| DNS | `cybertesis.net` and `www.cybertesis.net` → `208.91.196.105` |
-
-`cybertesis.net` is now a **click-monetisation parking page**. This is precisely the failure mode
-[`closed-and-defunct-servers.md` §2.4](closed-and-defunct-servers.md) documents for **BodoArXiv**
-(an online casino), **LawArXiv** (a 114-byte parking stub) and **agriRxiv** (a Namecheap parking
-page) — *"Domain lapse, parking, and hijack — the dangerous one"*. **Add Cybertesis to that table.**
-
-Note that **NDLTD's own directory still links Cybertesis**, though to `cybertesis.unmsm.edu.pe` (the
-Universidad Nacional Mayor de San Marcos instance) rather than the dead apex — so the *concept*
-survives as individual university installations of the Cyberthèses software while the shared portal
-does not. And note again the pattern from §2.4: **the directory outlived the thing it points at.**
-
-**LA Referencia** (`https://www.lareferencia.info/`), the Latin American open-access repository
-network, is what NDLTD lists as the regional successor. **Not probed in this pass —
-[NOT-VERIFIED].**
-
-### 4.10 Netherlands — NARCIS is confirmed discontinued
-
-**Verified.** `https://www.narcis.nl/` **redirects to `https://dans.knaw.nl/nl/data-diensten/narcis/`**
-[WEB]. DANS's own page, retrieved from the Internet Archive because the live DANS site is behind
-Anubis (capture **2026-05-10**) [DOC] (S33):
-
-> "As of **3 July 2023**, the NARCIS website was **taken offline and the NARCIS service ended**. The
-> content, such as metadata of publications and datasets, is of course still available in the
-> repositories of the various institutions and can be accessed or harvested there at any time.
->
-> Research information from Dutch institutions can be found via the **'Portal of Research Output
-> from the Netherlands'**. This portal was initiated by the **UKB and SURF** as a successor to
-> NARCIS."
-
-The same page adds: *"It is no longer possible to deposit data in EASY"* — DANS retired its
-long-standing archive alongside NARCIS.
-
-**The Wayback CDX series corroborates the date** [WEB] (S33): monthly 200s for `narcis.nl` through
-**2023-07-02**, a 301 on **2023-08-17**, no usable captures Oct 2023 – Jan 2024, and an unbroken run
-of 301s every month from **2024-02** to **2026-08**.
-
-**Where Dutch theses went: to the university repositories, plus a national portal.** NDLTD's
-directory lists the "Netherlands Research Portal" as **`https://netherlands.openaire.eu/`**, which
-returned **HTTP 200, 232,623 B** on 2026-09-04 [WEB] (S33) — an OpenAIRE national portal. Whether
-that is the same object as DANS's "Portal of Research Output from the Netherlands" (UKB/SURF) is
-**[NOT-VERIFIED]**; the two names may denote two different services. For actual Dutch hardware and
-systems dissertations the reliable route is the institutional repository — **TU Delft** in
-particular (§5.6).
-
-### 4.11 China — CNKI and Wanfang, and the honest answer
-
-Both are reachable and both are **commercial subscription databases**. This record will not pretend
-otherwise.
-
-| Service | Probe | Result |
-|---|---|---|
-| **CNKI** | `https://www.cnki.net/` | **200 → redirects to `https://oversea.cnki.net/`**, 50,542 B (a `gb2312` JS geo-redirect stub at the apex) [WEB] (S34) |
-| **Wanfang** | `https://www.wanfangdata.com.cn/` | **200**, 216,413 B [WEB] (S34) |
-
-- **CNKI's *China Doctoral Dissertations Full-Text Database* (CDFD)** is the largest collection of
-  Chinese doctoral dissertations in existence and is the only comprehensive route to them. It is
-  **paywalled**, sold by institutional subscription, and NDLTD's own directory annotates the
-  ProQuest entry as *"Paywalled resource"* and lists CNKI without such a note — **that annotation
-  gap is misleading; CDFD is equally paywalled.** [INF]
-- **Neither service was measured.** No count, no coverage figure, no full-text verification.
-  Attempting to characterise their holdings from outside the paywall would be guessing.
-  **CNKI and Wanfang holdings: [NOT-VERIFIED].**
-- Chinese-language *preprints* are a different and partly-open story — see
-  [`chinaxiv.md`](chinaxiv.md), which measures ChinaXiv at 47,362 native records (CS 2,052) and
-  documents its own 403 trap.
-- **Practical note:** a Chinese dissertation you cannot reach through CNKI is sometimes reachable
-  through the awarding university's own repository, and increasingly through **CORE** and
-  **OpenAIRE** (§2), which harvest some Chinese institutional repositories. Try those before
-  concluding the document is unavailable.
-
-### 4.12 Canada, Spain, Turkey — brief
-
-- **Theses Canada** (Library and Archives Canada). The URL in NDLTD's directory,
-  `collectionscanada.gc.ca/thesescanada/`, and the `bac-lac.gc.ca` form both fail (`000`);
-  `library-archives.canada.ca/eng/services/…/theses-canada.aspx` **302s to `canada.ca/en/library-archives.html`**;
-  the current search front end `recherche-collection-search.bac-lac.gc.ca` returns **HTTP 403, 5,775 B
-  Cloudflare** [WEB] (S35). The service is believed to continue under LAC's unified collection
-  search, but **nothing about it was verified** — **[NOT-VERIFIED]**. Canadian theses are, in
-  practice, best found through the university repository or ProQuest (§6), since LAC's programme has
-  long been coupled to ProQuest's Canadian dissertation intake.
-- **TESEO** (Spain, Ministry). `https://www.educacion.gob.es/teseo/irGestionarConsulta.do` **302s to
-  `https://aplicaciones.ciencia.gob.es/teseo`**, which returned **`000`** [WEB] (S36). TESEO is a
-  *metadata* registry of defended Spanish theses; the full text is in TDX/TDR (§4.5) or the
-  university repository. **[NOT-VERIFIED].**
-- **Tez Merkezi** (Turkey, YÖK National Thesis Centre),
-  `https://tez.yok.gov.tr/UlusalTezMerkezi/giris.jsp` → **HTTP 200, 33,811 B** [WEB] (S37). Alive
-  and unwalled. It is a genuinely comprehensive national full-text system (Turkish doctoral
-  regulations require deposit) and is under-known outside Turkey. **No count extracted —
-  [NOT-VERIFIED].**
-
-### 4.13 The finding that reframes §2: NDLTD has handed its search to OATD
-
-Discovered while reading NDLTD's own navigation, and it explains the 503 in §2.2.
-
-**Every "Global ETD Search" link on `ndltd.org` now points to `https://oatd.org/`** [WEB] (S38).
-Verified in three places on the site — the main navigation menu (twice) and the *List of Resources
-for Finding ETDs* table, where the row reads:
-
-```html
-<a href="https://oatd.org/" target="_blank" rel="noreferrer noopener">
-  Global ETD Search (previously: Union Catalog)</a>
-```
-
-**NDLTD is no longer operating its own union catalogue; it is pointing at OATD.** The 503 at
-`search.ndltd.org` is therefore not a broken server awaiting repair — it is a **retired service**,
-and the redirect in the navigation is the announcement. No formal deprecation notice was located;
-the link change *is* the notice. [INF, from the operator's own site]
-
-**The consequence is uncomfortable and should be stated plainly.** The world's ETD union catalogue
-has been consolidated onto **a single service that returns HTTP 403 to every automated client,
-including `robots.txt`, on every user agent tried** (§2.3). For a human with a browser this is fine.
-For anyone building a bibliography programmatically, for any downstream aggregator, and for this
-knowledge base, **the global ETD discovery layer is now effectively closed to machines.** CORE
-(§2.5) and OpenAIRE (§2.7) are the remaining open routes, and neither is thesis-specific.
-
-Two smaller stale entries in the same directory, worth flagging to NDLTD if anyone is in contact:
-its **EThOS** row links `https://bl.iro.bl.uk/` (the British Library *research repository*) rather
-than the restored `https://ethos.bl.uk/`; and its **Cybertesis** row survives only because it points
-at a university instance rather than the parked apex (§4.9).
-
----
-
-## 5. Institutional repositories — where the hardware theses actually are
-
-Given §2 and §4, the practical conclusion is unavoidable: **the institutional repository is the
-primary source and the aggregators are an increasingly unreliable index over it.** This section is
-the useful one.
-
-### 5.1 Status table
-
-All probes **2026-09-04**, Chrome-131 unless noted.
-
-| Repository | URL | Status | Machine interface | Note |
-|---|---|---|---|---|
-| **MIT DSpace** | `dspace.mit.edu` | **200** | **DSpace 7 REST: `/server/api/discover/search/objects` — open, no key** | Best-behaved repository probed. Handles `1721.1/…` |
-| **Caltech THESIS** | `thesis.library.caltech.edu` | **`000`** (both UAs) | — | TCP failure; shares `131.215.225.45` with `eprints.library.caltech.edu` |
-| **Caltech AUTHORS** | `authors.library.caltech.edu` | **200**, 17,077 B | — | Cloudflare-fronted, InvenioRDM-style. Reachable |
-| **Caltech via DataCite** | prefix **`10.7907`** | **200** | **DataCite REST — open** | **The working route to CaltechTHESIS while the site is down** |
-| **UC Berkeley EECS TRs** | `www2.eecs.berkeley.edu/Pubs/TechRpts/…` | **302 → `iris.eecs.berkeley.edu`, then 404** | — | ⚠ **BROKEN SINCE ~2026-08.** See §5.4 |
-| **CMU KiltHub** | `kilthub.cmu.edu` | 202 / 0 B (figshare trap) | **DataCite prefix `10.1184` — open** | Use DataCite, not the site |
-| **ETH Research Collection** | `research-collection.ethz.ch` | **403**, **1,337 B** custom "Access Restricted" | **OAI-PMH open** at `/server/oai/request`; **DataCite prefix `10.3929` open** | ⚠ **New block fingerprint.** See §5.5 |
-| **TU Delft** | `repository.tudelft.nl` | **200**, 925,475 B | not probed | Reachable |
-| **KTH** | via **DiVA** (§4.3) | 200 | DiVA OAI-PMH, set `SwePub-kth` | |
-| **KU Leuven Lirias** | `lirias.kuleuven.be` | **200 → `kuleuven.limo.libis.be` (Primo)**, 4,784 B | not found | SPA; no open API located |
-| **TU Graz Pure** | `graz.elsevierpure.com` | **403**, 6,102 B Cloudflare | — | Walled |
-| **TU Graz diglib** | `diglib.tugraz.at` | **200**, 12,844 B | not probed | Visual Library; digitised holdings |
-| **U. Helsinki Helda** | `helda.helsinki.fi` | 200, 4,262 B **Anubis** `1.23.0` | **DSpace 7 REST open behind the wall** | Same wall-the-site pattern |
-| **Cambridge Computer Lab** | `cl.cam.ac.uk/techreports/` | **200** | BibTeX, OAI-PMH, DBLP XML, RSS | Documented in [the companion record §3.5](government-and-institutional-technical-reports.md) |
-
-**Two cross-cutting operational findings**, both of which are the difference between "I could not
-find it" and "here it is":
-
-1. **DSpace 7's REST API is the most useful single tool in this record.** `dspace.mit.edu` and
-   `helda.helsinki.fi` both answered `GET /server/api/discover/search/objects?query=…&size=…` with
-   full JSON — **including `dc.contributor.advisor`** — with no key, and Helda did so *from behind an
-   Anubis wall*. See §10.
-2. **When a repository is walled, go to DataCite.** Caltech, CMU and ETH were all measured through
-   `api.datacite.org` while their own sites were unreachable or blocking. Any repository that mints
-   DOIs is indexable through its prefix.
-
-### 5.2 MIT DSpace
-
-`https://dspace.mit.edu/` — handles of the form `1721.1/<n>`. This is where MIT theses live, and MIT
-theses include several of the most consequential documents in the history of computing (§9).
-
-**The API, verified 2026-09-04** [API] (S39):
-
-```bash
-curl -s -G "https://dspace.mit.edu/server/api/discover/search/objects" \
-     --data-urlencode "query=symbolic analysis of relay and switching circuits" \
-     --data-urlencode "size=5"
-```
-
-The response is HAL+JSON; the useful path is
-`_embedded.searchResult._embedded.objects[]._embedded.indexableObject`, which carries `handle`,
-`uuid` and a full `metadata` map. **The `dc.contributor.advisor` field is populated on MIT theses**
-— this is the single most important field in this whole record for the §5.8 technique, and MIT
-exposes it publicly and for free.
-
-**A worked example — the Shannon record**, verbatim from the API [API] (S39):
-
-| Field | Value |
-|---|---|
-| `dc.title` | A symbolic analysis of relay and switching circuits |
-| `dc.contributor.author` | Shannon, Claude Elwood, 1916-2001. |
-| **`dc.contributor.advisor`** | **Frank L. Hitchcock.** |
-| `dc.description` | Thesis (M.S.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering, **1940**. |
-| `dc.description.degree` | M.S. |
-| `dc.format.extent` | 69 leaves |
-| `dc.date.issued` / `dc.date.copyright` | 1940 / 1940 |
-| `dc.identifier.oclc` | 34541425 |
-| `dc.identifier.uri` | `http://hdl.handle.net/1721.1/11173` |
-| `dc.date.accessioned` | 2008-05-19T16:55:43Z |
-| **`dc.rights`** | **"MIT theses are protected by copyright. They may be viewed, downloaded, or printed from this source but further reproduction or distribution in any format is prohibited without written permission."** |
-
-**Two things in that table matter well beyond Shannon.**
-
-**The date conflict.** MIT's own catalogue record says **1940**. The thesis is universally cited as
-**1937** (the year Shannon completed the work at MIT while employed at Bell Labs over the summer of
-1937), and the derived AIEE paper is **1938**. MIT's record almost certainly carries the *degree
-conferral* year — Shannon received his SM in electrical engineering and his PhD in mathematics in
-1940. **This survey records the conflict rather than resolving it** (README rule 4): if you cite the
-MIT record, the metadata says 1940; if you cite the thesis, the scholarly convention is 1937. Say
-which you mean. **[Conflict recorded; not resolved.]**
-
-**The licence.** *"further reproduction or distribution in any format is prohibited without written
-permission."* MIT theses are **free to read and not open-licensed.** That is the normal state of
-affairs for theses, and §8 develops it. It is also a reason not to mirror MIT thesis PDFs into a
-knowledge base.
-
-**MIT's AI Memo and technical-report series are in the same repository** — handle `1721.1/5460` is
-the collection "AI Memos (1959 – 2004)", verified in
-[the companion record §3.2](government-and-institutional-technical-reports.md). **Theses and reports
-sit side by side under one handle prefix**, and a search hits both. That is a feature: an MIT AI Lab
-technical report is frequently a lightly-edited chapter of a thesis, or vice versa.
-
-### 5.3 Caltech THESIS — down, and reachable anyway
-
-`https://thesis.library.caltech.edu/` returned **`000`** (TCP failure) to both Chrome-131 and
-`curl/8.5.0` on 2026-09-04. DNS resolves it to **`131.215.225.45`**, shared with
-`eprints.library.caltech.edu` — i.e. CaltechTHESIS is (or was) an **EPrints** installation, and the
-EPrints host is not answering. `authors.library.caltech.edu` — the separately-migrated CaltechAUTHORS
-service — is on Cloudflare and returns **HTTP 200, 17,077 B** [WEB] (S40). A `resolver.caltech.edu`
-probe with a plausible `CaltechTHESIS:` identifier returned **HTTP 404, 1,042 B**, so that resolver
-is alive but the identifier form was wrong.
-
-**Recorded as unreachable-from-here, not dead** — the same discipline the companion record applies to
-`www2.eecs.berkeley.edu` and `hpl.hp.com`.
-
-**The working route is DataCite prefix `10.7907`**, and it is excellent [API] (S41):
-
-```bash
-curl -s -G "https://api.datacite.org/dois" \
-  --data-urlencode 'query=creators.name:"Dally" AND concurrent' \
-  --data-urlencode 'prefix=10.7907' --data-urlencode 'page[size]=10'
-```
-
-Caltech has minted DOIs retroactively across the whole collection — **including 1985-vintage
-Computer Science technical notes** — and the `types.resourceType` field distinguishes `Dissertation`
-from `Technical note`. This is the **Carver Mead / Chuck Seitz VLSI lineage**, and §9 lists what was
-verified. Caltech is the single richest source in this record for the analog-VLSI, self-timed-logic
-and concurrent-architecture tradition.
-
-### 5.4 ⚠ UC Berkeley EECS — the technical-report series went dark between 2026-08-12 and 2026-09-04
-
-**This is a live, breaking finding, and it invalidates six canonical URLs recorded in
-[`government-and-institutional-technical-reports.md` §3.1](government-and-institutional-technical-reports.md).**
-
-Berkeley EECS files its **PhD dissertations and MS theses inside its technical-report series**. That
-is why `UCB/EECS-2016-1` is simultaneously a technical report and Andrew Waterman's RISC-V design
-dissertation, and why `UCB/EECS-2011-63` is a `@mastersthesis` in the department's own generated
-BibTeX. It is the cleanest example anywhere of the report/thesis boundary being an administrative
-fiction.
-
-**Measured 2026-09-04** [WEB] (S42):
-
-| URL | Result |
-|---|---|
-| `https://www2.eecs.berkeley.edu/Pubs/TechRpts/` | **HTTP 302 → `https://iris.eecs.berkeley.edu/Pubs/TechRpts/` → HTTP 404**, 58,829 B WordPress "Page not found \| IRIS" |
-| `https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-1.html` | **302 → 404**, 58,829 B |
-| `https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-1.pdf` | **302 → HTTP 404, 548-byte nginx page** |
-| `https://www.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-1.html` | **302 → 404** |
-| `https://eecs.berkeley.edu/research/publications/` | **HTTP 404**, 99,227 B |
-
-**The 302 is unconditional.** Chrome-131, `curl/8.5.0` and Googlebot all received the identical
-`location: https://iris.eecs.berkeley.edu/Pubs/TechRpts/`. This is not a bot wall.
-
-**DNS shows what happened** [WEB] (S42):
-
-```
-www2.eecs.berkeley.edu  → 128.32.139.28  (eecs-haproxy-vip.eecs.berkeley.edu)   ← the old origin
-iris.eecs.berkeley.edu  → 141.193.213.10/.11 (wp.wpenginepowered.com)           ← WordPress on WP Engine
-www.eecs.berkeley.edu   → 141.193.213.10/.11 (wp.wpenginepowered.com)
-```
-
-The department moved to a WP Engine-hosted WordPress site (`IRIS` — *Instructional & Research
-Information Systems*, HTTP 200, 83,508 B) and installed a **blanket catch-all redirect** from the
-old host into it. The new site has no `/Pubs/TechRpts/` route, so **every URL in the series
-resolves to a 404 with a marketing-site chrome around it.**
-
-**Dating the break, from the Wayback CDX index for the series index page** [WEB] (S42):
-
-| Capture | Status |
-|---|---|
-| 2025-02 → 2026-02 | mostly **200**, 14.5–15.1 kB |
-| 2026-04-04 | 403, 4,815 B |
-| **2026-05-04, 2026-06-03, 2026-07-11, 2026-08-12** | **200**, 15,122 / 15,264 / 15,270 / **15,267 B** |
-| 2026-09-04 (this probe) | **302 → 404** |
-
-**The index was serving normally as recently as 2026-08-12.** The break therefore falls in a
-**three-week window, 2026-08-12 to 2026-09-04**. No announcement was located.
-**[NOT-VERIFIED]:** whether a replacement location exists. `escholarship.org` — UC's system-wide
-repository, the obvious destination — returned **HTTP 202 with a zero-byte body**, the same
-figshare-style non-answer already recorded for `figshare.com` and `kilthub.cmu.edu` in
-[`retrieval-notes.md` §1](retrieval-notes.md), so it could not be searched.
-
-**The content survives in the Internet Archive, and we re-verified it.** Retrieved 2026-09-04 [WEB
-via Wayback] (S42):
-
-```
-http://web.archive.org/web/20220425162607id_/https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-1.pdf
-→ HTTP 200, 959,927 bytes, PDF version 1.4
-```
-
-**959,927 bytes exactly matches the figure recorded in
-[the companion record §3.1](government-and-institutional-technical-reports.md)** from a separate
-probe two days earlier — an independent confirmation that the archived artefact is the right one.
-The CDX index holds 200-status captures of that PDF from **2017-10-21 (778,143 B)**, **2020-08-06**,
-**2020-10-05**, **2020-11-13**, **2021-08-22**, **2021-10-19** and **2022-04-25 (776,543 B)**.
-
-**Three lessons, and they are the ones this whole directory keeps re-learning.**
-
-1. **A blanket redirect into a redesigned site is worse than a 404.** It converts a clean "gone"
-   signal into a 200-then-404 chain wrapped in unrelated chrome. A link-checker records "redirect
-   OK"; a human sees a marketing page.
-2. **`government-and-institutional-technical-reports.md`'s own recommendation was right and should
-   be acted on now.** That record said, of the DEC/Compaq series: *"When you find a corporate report
-   series that matters to you, take a copy."* The same now applies to a **university** series, and
-   to the RISC-V specifications specifically.
-3. **The Wayback copy is currently the only verified route to the origin documents of RISC-V.** That
-   is an uncomfortable sentence to write about an actively-developed, industrially-significant ISA,
-   and it is what the measurement says. See §13.
-
-### 5.5 ETH Zürich Research Collection — SAFARI, and a new block fingerprint
-
-`https://www.research-collection.ethz.ch/` is ETH's DSpace-CRIS repository, and it is directly
-relevant here because the **SAFARI group (Onur Mutlu)** deposits its memory-systems and
-RowHammer-lineage dissertations there.
-
-**⚠ New block fingerprint — record this.** The DSpace REST API returns **HTTP 403 with a 1,337-byte
-custom HTML page**, not a Cloudflare or Anubis interstitial [WEB] (S43). It is *self-documenting*,
-which is unusual and welcome:
-
-> **Access Restricted**
->
-> "Due to a high volume of automated traffic (scraping), access to the ETH Zurich Research Collection
-> is **temporarily restricted from your location / your provider**. This measure helps ensure system
-> availability for our users. If you have been blocked accidentially, please contact us at
-> `research-collection@library.ethz.ch`."
-
-Distinguishing features for a fingerprint table: **HTTP 403, ~1,337 bytes, `<title>Access
-Restricted</title>`, inline `Segoe UI` CSS, German-flavoured spelling "accidentially", a contact
-address.** It is **IP/provider-scoped**, not user-agent-scoped — the page says so — so the UA ladder
-is the wrong tool. The right response is the contact address.
-
-**Two open routes were found** [API] (S43):
-
-```bash
-# 1. OAI-PMH is completely open
-curl -s "https://www.research-collection.ethz.ch/server/oai/request?verb=Identify"
-#   repositoryName: ETH Research Collection
-#   earliestDatestamp: 2017-05-15T06:24:06Z
-#   deletedRecord: transient
-#   granularity: YYYY-MM-DDThh:mm:ssZ
-
-# 2. DataCite, prefix 10.3929
-curl -s -G "https://api.datacite.org/dois" \
-  --data-urlencode 'query=DRAM AND types.resourceType:Dissertation' \
-  --data-urlencode 'prefix=10.3929'
-```
-
-Note `earliestDatestamp: 2017-05-15` — the Research Collection replaced ETH's earlier e-collection
-platform, and the OAI datestamps start at the migration, not at the content's origin. **Do not read
-it as a coverage floor.**
-
-**The SAFARI dissertations, verified via DataCite** [API] (S43) — full table in §9:
-
-| DOI | Year | Author | Title |
-|---|---|---|---|
-| `10.3929/ethz-b-000601914` | 2022 | Hasan Hassan | Improving DRAM Performance, Reliability, and Security by Rigorously Understanding Intrinsic DRAM… |
-| `10.3929/ethz-b-000691009` | 2024 | A. Giray Yağlıkçı | Enabling Efficient and Scalable DRAM Read Disturbance Mitigation via New Experimental Insights… |
-| `10.3929/ethz-b-000698237` | 2024 | Michele Marazzi | Principled DRAM Security against Rowhammer Attacks |
-| `10.3929/ethz-b-000542542` | 2021 | Minesh Patel | Enabling Effective Error Mitigation in Memory Chips That Use On-Die Error-Correcting Codes |
-
-**Why this matters concretely.** [`landmark-papers.md` §1](landmark-papers.md) records that the
-original RowHammer paper (*Flipping Bits in Memory Without Accessing Them*, ISCA 2014) is **not on
-arXiv** — the only hit is the 2023 retrospective. The conference papers in this lineage are 12–13
-pages each. **These four dissertations are 150–300 pages each and they contain the actual DRAM
-characterisation infrastructure** — the FPGA-based memory controllers, the temperature-controlled
-test setups, the per-module scan methodology, the negative results on mitigation schemes that did
-not work. If you are trying to reproduce or extend RowHammer work, the dissertations are the
-documents. This is §1's argument in its purest form.
-
-DataCite also surfaced, in the same prefix, ETH **bachelor's** theses of real substance — e.g.
-`10.3929/ethz-b-000722911`, *"REFault: A Fault Injection Platform for Rowhammer Research on DDR5
-Memory"* (Stefan Gloor, 2023). **Do not filter out non-doctoral theses when hunting for hardware
-infrastructure.** A bachelor's or master's thesis is frequently where a specific piece of test
-apparatus is documented, because that is exactly the size of task a supervisor hands to a
-master's student.
-
-### 5.6 TU Delft and KTH
-
-**TU Delft** — `https://repository.tudelft.nl/` → **HTTP 200, 925,475 B** [WEB] (S44). Reachable and
-unwalled. TU Delft's repository is the route to Dutch hardware and systems dissertations now that
-NARCIS is gone (§4.10), and it is the natural home for the embedded-systems, quantum-hardware and
-networking work the university is known for. **No machine interface was probed and no count was
-obtained — [NOT-VERIFIED].**
-
-**KTH** deposits into **DiVA** (§4.3), set `SwePub-kth`, harvestable over the open DiVA OAI-PMH
-endpoint. The Swedish compilation-thesis convention (§4.3) makes KTH doctoral theses unusually
-information-dense: the *kappa* is a purpose-written synthesis, not a stapled bundle.
-
-### 5.7 KU Leuven COSIC and TU Graz IAIK — the hardware-security long form
-
-These two groups are named here because they are the **long-form layer under
-[`cryptology-eprint-archive.md` §7.6](cryptology-eprint-archive.md)**, which records ePrint as
-*primary* for side-channel and embedded security. The ePrint reports are 15–25 pages. The
-dissertations behind them are where the measurement setup lives.
-
-**KU Leuven COSIC.** `https://lirias.kuleuven.be/` **redirects to
-`https://kuleuven.limo.libis.be/discovery/search?vid=32KUL_KUL:Lirias`** — an Ex Libris **Primo**
-front end, HTTP 200 but a 4,784-byte Angular shell [WEB] (S45). **No open API was located** and
-**no COSIC dissertation was verified in this pass — [NOT-VERIFIED].** Primo installations generally
-expose a `pnxs` REST endpoint but it is institution-configured and was not found. The practical
-route for COSIC specifically is the **group's own publications page**, which has historically listed
-its PhD theses with direct PDFs; that was not probed here.
-
-**TU Graz IAIK** — the Spectre/Meltdown lineage (Daniel Gruss, Moritz Lipp, Michael Schwarz and
-colleagues). Two hosts:
-
-- `https://graz.elsevierpure.com/…` (the Pure CRIS) → **HTTP 403, 6,102 B Cloudflare** [WEB] (S46).
-- `https://diglib.tugraz.at/` → **HTTP 200, 12,844 B**, a Visual Library instance
-  ("digitalisierte Zeitschriften und Bücher"); `/dissertationen` returns 200, 10,815 B [WEB] (S46).
-  Not searched further.
-
-**What was verified about Gruss's dissertation is only its published summary.** Crossref [API]
-(S47):
-
-```
-10.1515/itit-2018-0034 · "Software-based microarchitectural attacks" · Gruss
-· it - Information Technology (De Gruyter) · 2018-11-20
-```
-
-That is the *dissertation abstract/summary* genre — German-speaking computer science publishes
-condensed dissertation reports in *it – Information Technology*. **It is not the thesis.** The full
-TU Graz dissertations of Gruss and Lipp were **[NOT-VERIFIED]** in this pass: the Pure front end is
-Cloudflare-walled, and no unwalled TU Graz repository search was found within budget. This is a real
-gap and it is listed in §13.
-
-**A useful generalisation from this failure.** For German, Austrian and Swiss dissertations, check
-*it – Information Technology* (De Gruyter) and the equivalent society digests: a Crossref query on
-the author's name will often surface a 4-page dissertation summary with a DOI when the full thesis is
-hard to locate. It is not a substitute — but it gives you the exact title, the year, the institution
-and the supervisor, which is what you need to find the real thing.
-
-### 5.8 How to find a thesis when you know the author and the advisor
-
-This is how it actually works in practice, and it is worth stating as a procedure because the
-obvious approach — searching for the thesis title — usually fails, since you do not know the title.
-The thesis title is almost never the paper title.
-
-**The core insight: a thesis is indexed under the *institution* and the *year*, not under the topic
-you care about.** So you work backwards from the person.
-
-**Step 1 — Establish the institution and the approximate year.**
-From any paper by the author, take the affiliation on the *earliest* paper in the line of work. That
-is where they were a student. The thesis year is typically **the year of the last first-author paper
-in that line, plus zero to one**. If the paper says "this work was performed while the author was at
-X", that is your institution.
-
-**Step 2 — Establish the advisor.** The advisor is the last author on the student's papers in most
-hardware and systems venues. If the group is one you know (SAFARI, COSIC, IAIK, ASPIRE/BAR), the
-advisor is the group head.
-
-**Step 3 — Query the institutional repository by advisor, not by title.** This is the step people
-skip. Repository metadata carries a supervisor field far more often than anyone expects:
-
-| Source | Advisor field | Verified |
-|---|---|---|
-| **MIT DSpace** | `dc.contributor.advisor` — populated, in the public REST API | ✅ (§5.2 — Shannon → "Frank L. Hitchcock.") |
-| **theses.fr** | `directeurs` on the thesis record; `roles` counts on `/personnes` | ✅ (§4.2) |
-| **Shodhganga** | a browse index literally labelled **"Researcher/Guide"** | ✅ (§4.7) |
-| **EThOS bulk CSV** | a **`Supervisor(s)`** column | ✅ (§3.6) |
-| DSpace generally | `dc.contributor.advisor` is a standard DSpace thesis field | [INF] |
-
-Concretely, on any DSpace 7 repository:
-
-```bash
-curl -s -G "https://dspace.mit.edu/server/api/discover/search/objects" \
-     --data-urlencode "query=<advisor surname>" --data-urlencode "size=50" \
-| python3 -c 'import json,sys
-d=json.load(sys.stdin)["_embedded"]["searchResult"]["_embedded"]["objects"]
-for x in d:
-    i=x["_embedded"]["indexableObject"]; m=i.get("metadata",{})
-    adv=[v["value"] for v in m.get("dc.contributor.advisor",[])]
-    if adv: print(i["handle"], adv, i.get("name")[:70])'
-```
-
-That returns the advisor's entire student list from the repository, with handles. It is how §9's
-MIT entries were found: a query for `Knight implementation of a list processing machine` returned
-Tom Knight's own 1979 thesis (advisor **Marvin L. Minsky**) *and* two later theses he supervised —
-the lineage falls out of the metadata for free.
-
-**Step 4 — If the institutional repository fails, use the bulk metadata.** For the UK, the 709 MB
-`EThOS_CSV_202310.csv` (§3.6) has `Author`, `Supervisor(s)`, `Institution`, `Date`, `Abstract` and
-**`IR URL`** in one file. `grep` on a supervisor name is faster and more reliable than any web
-search, and it works offline.
-
-**Step 5 — If you still cannot find it, look in the technical-report series.** Berkeley EECS
-(§5.4), Cambridge Computer Lab (`UCAM-CL-TR-<n>`), CMU SCS and MIT AI Memos all file dissertations
-as numbered reports. A thesis missing from a "theses" collection is often present in the "reports"
-collection of the same department. See
-[`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md).
-
-**Step 6 — Check the personal page.** This is not a joke and §9 proves it: **Linus Torvalds's
-master's thesis is not in Helda, the University of Helsinki repository — it is a PDF on a
-professor's departmental home page** (verified, §9). For pre-2005 work especially, the author's or
-advisor's `~user` page is a real and frequently the only source. It is also the most fragile one:
-these are prime `web.archive.org/save/` candidates under `AGENTS.md` rule 9.
-
----
-
-## 6. Commercial and restricted routes
-
-### 6.1 ProQuest Dissertations & Theses Global
-
-**PQDT Global** is the commercial dissertation database, and it is genuinely the largest single
-index of theses in existence. ProQuest's own product page, `https://about.proquest.com/en/products-services/pqdtglobal/`
-→ HTTP 200, 347,146 B, retrieved 2026-09-04 [DOC] (S48):
-
-> "With over **6 million metadata records** including **4 million full text documents**, ProQuest
-> Dissertations & Theses Global is the world leader in providing access to dissertation and thesis
-> research."
->
-> "…more than 6 million dissertations and theses citations from over **3,600 institutions** from more
-> than **70 countries**…"
-
-Set that against the open figures in §2 and §4:
-
-| Source | Records | Full text |
-|---|---|---|
-| **PQDT Global** | **~6,000,000** | **~4,000,000** [DOC] |
-| OATD | 7,407,210 (2025-03) | metadata-plus-link [WEB] |
-| CORE `documentType:"thesis"` | 7,921,188 | CORE stores full text [API] |
-| OpenAIRE (3 thesis types) | ≤8,346,188 | mixed [API] |
-| NDLTD Global ETD Search | 6,534,039 (2025-05, now 503) | metadata-plus-link [WEB] |
-
-**PQDT is not obviously larger than the open aggregators by record count.** What it has that they do
-not is (a) a curated, deduplicated, consistently-catalogued index, (b) **4 million full texts under
-one licence**, including a great deal of pre-1997 North American material that exists nowhere else
-digitally, and (c) subject indexing. What it does not have is anything a hardware engineer cannot
-usually reach another way, *for recent work*.
-
-**How access actually works, stated precisely:**
-
-- **PQDT Global is a subscription database.** Access is through a subscribing library. This is an
-  access control and `AGENTS.md` rule 7 applies — do not attempt to route around it.
-- **ProQuest is owned by Clarivate**, and the product page markets PQDT integration with **Web of
-  Science**. Disclose that entanglement when citing PQDT coverage figures, in the same spirit as
-  [`reliability-and-durability.md` §4](reliability-and-durability.md)'s treatment of Elsevier/SSRN
-  and Springer Nature/Research Square.
-- **ProQuest acquires the content by being the North American dissertation-deposit intermediary.**
-  Many US and Canadian universities have historically submitted every dissertation to ProQuest as
-  part of the graduation workflow. That is why its pre-web coverage is unmatched, and it is also why
-  the same document is very often *also* in the university's own repository.
-
-### 6.2 PQDT Open — gone as a standalone service
-
-**This is a finding, and it is not good news.** `https://pqdtopen.proquest.com/` — the free,
-open-access subset of PQDT — returned **HTTP 302 to `https://www.proquest.com/?defaultdiss=true`** on
-2026-09-04 [WEB] (S48). The standalone PQDT Open front door no longer exists; you land on the main
-ProQuest platform with a dissertations default filter, which for an unsubscribed visitor is not a
-free full-text service.
-
-**PQDT Open's current status and record count: [NOT-VERIFIED].** What was tried: the canonical
-hostname (302 as above) and `https://www.proquest.com/pqdtglobal` (302, zero-byte body). Whether the
-open-access subset still exists as a searchable, freely-downloadable collection under the main
-platform was not established. **Do not cite PQDT Open as a live free route without re-checking it.**
-
-This is the same pattern as §2.4 (DART-Europe) and §4.13 (NDLTD): **a free discovery layer being
-folded into, or replaced by, something less open.** Three instances in one pass is a trend worth
-naming.
-
-### 6.3 EBSCO Open Dissertations — a free alternative that is easy to miss
-
-`https://www.ebsco.com/products/research-databases/ebsco-open-dissertations` → 301 →
-`https://about.ebsco.com/…` → HTTP 200, 68,261 B [DOC] (S49). EBSCO's own words:
-
-> "EBSCO Open Dissertations makes electronic theses and dissertations (ETDs) more accessible to
-> researchers worldwide. **The free portal** is designed to benefit universities and their students
-> and make ETDs more discoverable. Content Includes: **2,000,000 electronic theses and
-> dissertations**; **325 worldwide universities** that have loaded their dissertations to date."
-
-**2 million ETDs, free, from a commercial vendor.** It descends from the old *American Doctoral
-Dissertations* index that H. W. Wilson maintained. It appears in NDLTD's directory and almost nowhere
-else, and it is a legitimate fourth option alongside CORE, OpenAIRE and OATD. **Not probed
-functionally in this pass — the count above is EBSCO's claim, not our measurement.**
-
-### 6.4 The point that makes most of §6 optional: authors self-archive
-
-**The same document is very often in three places at once**, and only one of them is behind a
-paywall:
-
-1. The **commercial database** (PQDT), because the university's graduation workflow deposited it.
-2. The **institutional repository**, because the university's open-access policy required it.
-3. The **author's own website**, because early-career researchers put their thesis on their homepage.
-
-Route (2) is free, canonical and citable. Route (3) is free, fragile and often the only route for
-pre-2005 work (§9's Torvalds entry is the proof). **Check the institutional repository before paying
-for anything**, and check the author's page before concluding the document is unavailable.
-
-**A caution that cuts the other way.** The three copies are **not necessarily the same file.** See
-§7.3 on version semantics: the copy an author put on their homepage in 2004 may be the pre-defence
-draft, and the repository copy may be the corrected final. When it matters, cite the repository.
-
----
-
-## 7. Reliability — what a thesis actually guarantees
-
-### 7.1 The gate, in the terms this survey already uses
-
-[`reliability-and-durability.md` §1](reliability-and-durability.md) sorts preprint servers by their
-**gate**, on the principle that *"reliability is a question about the gate, not about the badge"*.
-The thesis gate slots into that table, and it is a genuinely different shape from anything on it:
-
-| Gate type | Example | What it proves |
-|---|---|---|
-| None whatsoever | Zenodo, figshare, viXra | A DOI and a timestamp |
-| Endorsement + subject moderation | arXiv | An endorsed author and a plausible subject fit |
-| Named editorial screening | Cryptology ePrint, Optimization Online | Relevance and non-obvious-crackpottery |
-| Journal peer review | (off this survey's list) | 2–4 anonymous referees read it once, on a deadline, unpaid, and recommended acceptance |
-| **Examination and defence** | **a doctoral thesis** | **A named committee read the whole document, questioned the candidate live for 1–3 hours, and required revisions before signing** |
-
-**On three axes the thesis gate is genuinely stronger than journal review:**
-
-- **Completeness.** A referee checks that the claims are supported. A committee checks that the
-  *work* is a coherent, sufficient body — which is why the methods chapters exist at all.
-- **Interrogation.** The oral defence is the only point in the entire scholarly process at which
-  someone can ask a follow-up question and get an answer in real time. A referee cannot. This is
-  unusually effective at catching a candidate who does not understand their own apparatus.
-- **Accountability.** Committee members are **named** in the document. Referees are anonymous.
-  A signed thesis is a public assertion by identified senior researchers that the work is sound.
-
-**On three other axes it is weaker, and these are not small:**
-
-- **The supervisor is on the committee.** The person with the largest stake in a pass outcome is one
-  of the assessors. In some systems they chair it.
-- **There is no cross-institution standard.** None. A doctorate from two different universities in
-  the same country can represent enormously different amounts of work and scrutiny, and there is no
-  external body that normalises this. This is the single largest caveat in this section and it
-  applies globally, including within highly-regarded systems.
-- **The audience is one committee, not a field.** A journal referee is selected for topical
-  expertise. A committee is selected for availability and institutional requirements, and may
-  contain nobody who has built the thing the candidate built.
-
-### 7.2 Failure modes specific to theses
-
-- **The advisor's framing goes unchallenged.** A thesis is written to satisfy a supervisor; a
-  supervisor's idiosyncratic view of the field is therefore over-represented, particularly in the
-  literature review. Read the related-work chapter for *pointers*, not for judgement.
-- **Self-citation and group-citation are structurally high.** A thesis built on the group's prior
-  papers cites them heavily and correctly. That is not misconduct, but it means citation counts
-  within a thesis are not a signal of field consensus.
-- **Volume mandates dilute.** Systems with a national deposit mandate (§4.7 Shodhganga, Germany,
-  Turkey) contain every thesis, not the good ones. **A mandate is a coverage guarantee, not a
-  quality gate**, and this survey's standing rule applies: *if you cannot determine the gate, treat
-  it as "none"*.
-- **Plagiarism and, since ~2023, machine generation.** Shodhganga's own front page links UGC
-  plagiarism notices from 2018 and 2020 and a separate self-plagiarism notice — the operator telling
-  you what they consider the live risk. [`reliability-and-durability.md` §3](reliability-and-durability.md)
-  documents three preprint operators tightening against AI-generated text in 2025; **no equivalent
-  measurement exists for theses**, and this record makes no claim about it. **[NOT-VERIFIED].**
-- **The paper is often better than the thesis on the same result.** A chapter written in year two
-  and lightly updated for submission can carry worse numbers than the conference paper that came out
-  of it eighteen months later. **Read both; prefer the paper for the headline result and the thesis
-  for the method.**
-
-### 7.3 Version semantics — the part people get wrong
-
-A thesis exists in **at least three** distinct versions, and repositories are inconsistent about
-which one they hold.
-
-| Version | What it is | Typical marker |
-|---|---|---|
-| **Submitted / examination copy** | What went to the committee before the viva | Rare in repositories. Sometimes on the author's homepage |
-| **Accepted** | The version the committee passed, *before* required corrections | Occasionally deposited by mistake |
-| **Corrected / final / of record** | Post-viva, post-corrections, formally accepted by the graduate school | **What a repository should hold.** Usually carries a degree-conferral date |
-| **Published derivative** | A revised commercial monograph (common in some fields), or a dissertation summary such as `10.1515/itit-2018-0034` (§5.7) | A publisher DOI and a different title |
-
-**How to tell which one you have — a practical checklist:**
-
-1. **Look for a signed approval or certification page.** A final version normally carries a signature
-   page or a formal statement of acceptance with the conferral date. A submitted copy does not.
-2. **Compare the repository's `date.issued` with the degree year.** MIT's Shannon record shows
-   `dc.description: "Thesis (M.S.)--…, 1940"` alongside `dc.date.issued: 1940` — internally
-   consistent. A file dated a year *before* the recorded degree year is a pre-correction copy.
-3. **Check `dc.description.degree` / qualification fields.** EThOS records carry
-   `Qualification Name: Thesis (Ph.D.)` and `Date Awarded`; theses.fr carries `dateSoutenance` (the
-   defence date) *and* `datePremiereInscriptionDoctorat`. The defence date, not the file date, is the
-   citation year.
-4. **Beware the author's homepage copy.** It is frequently the version the author was proudest of,
-   which is not necessarily the version the university holds.
-5. **If a repository offers "Version of Record" versus "Author Accepted Manuscript" labelling for
-   theses, believe it; most do not offer it at all.**
-
-**How to cite one defensibly.** Combine four things, and the first is the one people omit:
-
-```
-Author. Title. <Degree> thesis, <Institution>, <year of award>.
-<persistent identifier>. <access date if no PID>.
-```
-
-- **Use the persistent identifier, not the URL.** For theses that means a **handle**
-  (`hdl.handle.net/1721.1/11173`), a **DOI** (`10.3929/ethz-b-000601914`,
-  `10.7907/f8d5-x741`), an **NNT** (`2016PA066033`), an **EThOS ID** (`uk.bl.ethos.906226`) or a
-  **report number** (`UCB/EECS-2016-1`). §5.4 is the argument: the Berkeley URLs died in a
-  three-week window and the report numbers did not.
-- **State the degree and the institution.** "PhD thesis, ETH Zürich" carries information that the
-  DOI alone does not, and it is what tells a reader what gate the document passed.
-- **Use the year of award**, and if it conflicts with the repository's `date.issued`, say so —
-  Shannon 1937/1940 is the canonical example (§5.2).
-- **If you are relying on a specific chapter's method, cite the chapter and page range.** The whole
-  point of using a thesis is that the detail is in one chapter; a whole-document citation makes the
-  reader find it again.
-
-### 7.4 When to trust a thesis more than the paper
-
-Stated positively, because §7.1–7.3 are all caveats. Prefer the thesis when:
-
-- You need to **reproduce** something. The setup, calibration and part numbers are there and are
-  nowhere else (§1.2).
-- You need **negative results**. "We tried X and it did not work" survives only here.
-- You need the **failure analysis of a physical artefact** — board spins, yield, thermal behaviour,
-  process variation.
-- The paper is **paywalled and the thesis is not**, which is very common: the thesis chapter
-  frequently predates and substantially overlaps the paywalled paper, and the repository copy is
-  free and legitimate.
-- The work **never became a paper at all.** A great deal of instrumentation and tooling is in this
-  category, and for it the thesis is not the long version — it is the *only* version.
-
----
-
-## 8. Embargoes and licensing
-
-This is the most widely misunderstood part of the thesis landscape, and it is where a naive
-"open access" assumption produces wrong conclusions.
-
-### 8.1 Embargoes are normal, not exceptional
-
-A thesis embargo is a period during which the **record is public and the file is not**. Typical
-lengths run from **6 months to 5 years**, and permanent restriction exists. The common reasons:
-
-| Reason | Typical length | Notes |
-|---|---|---|
-| **Patent filing** | 6–24 months | The dominant reason in hardware, materials and EE. The university's technology-transfer office requests it |
-| **Publisher / prior-publication concern** | 6–24 months | The candidate intends to turn a chapter into a paper or a monograph and fears a "prior publication" objection |
-| **Industrial sponsor or NDA** | 1–5 years, sometimes indefinite | Very common in semiconductor, defence and automotive work. The sponsor owns or restricts disclosure |
-| **Commercially sensitive data** | variable | Fab data, yield numbers, customer data |
-| **Personal safety / sensitive fieldwork** | variable to permanent | Rare in this knowledge base's fields |
-| **Third-party copyright the author could not clear** | often permanent for *part* of the document | Produces the "redacted version" pattern below |
-
-**For hardware specifically, the patent reason dominates**, and it is worth internalising why: the
-work most worth reading — a novel circuit, a novel process step, a novel architecture — is exactly
-the work most likely to be embargoed. **The embargo rate is not uniform across topics; it is highest
-precisely where this knowledge base's interest is highest.** [INF]
-
-**Embargo rates were not measured in this pass. [NOT-VERIFIED].** No repository probed publishes an
-aggregate embargo statistic, and none of the APIs used exposes a queryable embargo facet. This is a
-real gap and a good target for a future pass: DSpace's `dc.date.available` versus `dc.date.issued`
-differential is, in principle, measurable in bulk over OAI-PMH.
-
-### 8.2 How an embargo appears in metadata — and how it appears to *you*
-
-**The crucial point: an embargoed thesis looks exactly like an available one in a search result.**
-Google Scholar, CORE, OpenAIRE, OATD and EThOS all index the *record*. The wall is one click deeper.
-
-Recognisable patterns, in rough order of how often you will hit them:
-
-1. **A landing page with no file and no explanation.** Most common. The record renders normally; the
-   download section is simply absent.
-2. **An explicit availability date.** DSpace's `dc.date.available` is set to a future date; the UI
-   says "Available after 2027-06-01" or "Under embargo until…". **This is the good case** — you know
-   exactly when to come back.
-3. **"Restricted access" / "Access restricted to <institution> users".** The file exists and is
-   IP-limited. This is an access control, not a bot wall: `AGENTS.md` rule 7 applies.
-4. **A redacted version alongside a full version.** Two files, one public with chapters or figures
-   removed. Common where third-party copyright could not be cleared. Look for "redacted",
-   "public version" or a suspiciously small PDF.
-5. **A metadata-only record with a contact instruction.** EThOS does this explicitly and by design
-   now — the record probed in §3.5 read *"EThOS does not have a link to a university copy of this
-   thesis. If you would like to view this thesis, we recommend that you contact Royal Veterinary
-   College."* **Note that this is indistinguishable, from the outside, from an embargo.** It could
-   equally be a pre-digital paper-only thesis, or a repository the harvester has not reached yet —
-   the EThOS FAQ lists all three causes for the same visible state (§3.3).
-6. **The "request a copy" button.** DSpace and EPrints both ship a feature that emails the author.
-   It works more often than people expect, especially for a thesis five or more years old whose
-   embargo reason has expired but whose flag nobody cleared.
-
-**Practical consequences:**
-
-- **Absence of a file is not evidence of absence of the thesis.** Check the awarding institution
-  directly, then the author, then a later date.
-- **An embargo expires and the metadata often does not get updated.** Re-check old embargoed records;
-  the file is frequently there now.
-- **Do not report an embargoed record as a dead link.** It is neither dead nor broken; it is a
-  deliberate temporary state, and confusing the two corrupts durability statistics.
-
-### 8.3 Licensing — the genuine reuse problem
-
-**Theses are free to read and almost never openly licensed.** This is the single most important
-practical fact in §8, and it is the opposite of what people assume from the phrase "open access
-repository".
-
-**The verified example**, from MIT's own record for Shannon's thesis [API] (§5.2, S39):
-
-> `dc.rights`: "MIT theses are protected by copyright. They may be viewed, downloaded, or printed
-> from this source but **further reproduction or distribution in any format is prohibited without
-> written permission**."
-
-That is a **read-only permission grant, not an open licence.** No CC-BY, no derivative rights, no
-redistribution, and — read strictly — **no text and data mining**. This is normal. The copyright in
-a thesis is usually retained by the author; the university takes a non-exclusive licence to hold and
-display it; and nobody involved has any incentive to attach a CC licence.
-
-**The picture across the systems measured here:**
-
-| Object | Licence | Evidence |
-|---|---|---|
-| **MIT theses** | Read/download/print only; redistribution prohibited without permission | [API] `dc.rights`, §5.2 |
-| **EThOS bulk metadata dataset** (`10.23636/rcm4-zk44`) | **CC-BY 4.0** — `rightsIdentifier: cc-by-4.0` | [API] DataCite, §3.6 |
-| **Individual UK theses** | **Institution-dependent.** EThOS holds no files and asserts nothing about the university copies | [DOC] §3.3 |
-| **theses.fr records** | Metadata is public; file licensing is per-institution | [INF] |
-| Shodhganga, DiVA, TDX, ETH, Caltech, TU Delft | **Not verified individually** | **[NOT-VERIFIED]** |
-
-**Note the asymmetry, because it is the useful finding:** the **metadata** is frequently CC-BY or
-CC0 and bulk-downloadable, while the **documents** carry no licence at all. The British Library gave
-away 709 MB of thesis metadata under CC-BY and gave away no theses. That asymmetry is the norm, and
-it determines what you can legitimately build.
-
-**Operational rules for this knowledge base:**
-
-1. **Link and cite; do not mirror.** A thesis PDF in `archive/` is very likely a redistribution the
-   licence does not permit. Record the handle/DOI and the byte size instead — which is what this
-   record does throughout.
-2. **Check `dc.rights` before assuming reuse rights.** It is in the DSpace REST API for free (§5.2).
-   No `dc.rights` field means "no licence stated", which means **all rights reserved**, not "public
-   domain".
-3. **Quoting is fine; wholesale extraction may not be.** Quoting a paragraph or a figure with
-   attribution is ordinary scholarly use. Bulk-harvesting a thousand thesis PDFs to build a
-   derivative corpus is a licence question, and for most of the repositories above the answer is not
-   yes.
-4. **Metadata is the reusable layer.** OAI-PMH records, DataCite metadata and the EThOS CSV are
-   explicitly reusable. Build on those.
-5. **Where a thesis *does* carry a CC licence, it will say so** — and increasingly they do, because
-   funder open-access mandates propagate to theses. Check; do not assume in either direction.
-
----
-
-## 9. LANDMARK THESES — verified
-
-The thesis-shaped parallel to [`landmark-papers.md`](landmark-papers.md), and held to the same
-standard stated in [`README.md § Evidence and method`](README.md#evidence-and-method) rule 5:
-**every identifier below was individually retrieved from its repository's API or abstract page on
-2026-09-04, and the title machine-checked against the response. Candidates that could not be
-confirmed were dropped, not softened** — §9.4 lists them by name.
-
-**26 entries verified.**
-
-### 9.1 Foundational — the documents that made the field
-
-| # | Thesis | Author | Degree · Institution · Year | Identifier | Verified how | Why it matters |
-|---|---|---|---|---|---|---|
-| 1 | **A symbolic analysis of relay and switching circuits** | Claude Elwood Shannon | **M.S.**, MIT, Dept. of Electrical Engineering · MIT record says **1940**; universally cited as **1937** | **`hdl:1721.1/11173`** · <https://hdl.handle.net/1721.1/11173> | MIT DSpace REST [API] | **The single most consequential thesis in the history of digital electronics.** Establishes the correspondence between Boolean algebra and relay contact networks — the theoretical basis of every digital circuit since. 69 leaves. **Advisor: Frank L. Hitchcock.** OCLC 34541425. See §5.2 for the 1937/1940 date conflict |
-| 2 | **Sketchpad, a man-machine graphical communication system** | Ivan Edward Sutherland | **PhD**, MIT, **1963** (dissertation submitted January 1963) | **`hdl:1721.1/14979`** · and republished as **`UCAM-CL-TR-574`**, DOI **`10.48456/tr-574`** | MIT DSpace REST [API] + Cambridge CL abstract page [WEB] | Interactive computer graphics, constraint solving, object-instance hierarchies, the light pen. **The Cambridge Computer Laboratory republished it in September 2003 as a 149-page technical report with a new preface by Alan Blackwell and Kerry Rodden** — the report page states it "is based on a dissertation submitted January 1963 … to the Massachusetts Institute of Technology". Cross-link: [companion record §3.5](government-and-institutional-technical-reports.md) |
-| 3 | **Implementation of a list processing machine** | Thomas F. Knight | MIT, **1979** · advisor **Marvin L. Minsky** | **`hdl:1721.1/16033`** | MIT DSpace REST [API] | The MIT **Lisp Machine**. Tagged architecture, hardware type-checking, microcoded list processing — the design lineage behind Symbolics and LMI, and a primary source for hardware support of dynamic languages |
-| 4 | **RABBIT: A Compiler for SCHEME** | Guy Lewis Steele, Jr. | MIT, **1978-05-01** | **`hdl:1721.1/6913`** | MIT DSpace REST [API] | The document that established **proper tail calls, continuation-passing style as a compiler IR, and "lambda: the ultimate…"** as engineering practice rather than theory. Every functional-language compiler descends from it |
-| 5 | **The connection machine** | William Daniel Hillis | **PhD**, MIT, **1988** · advisor **Gerald Sussman** | **`hdl:1721.1/14719`** · (the 1981 AI Memo precursor is `hdl:1721.1/5679`, "The Connection Machine", 1981-09-01) | MIT DSpace REST [API] | Massively parallel SIMD architecture; the CM-1/CM-2. The thesis and the 1981 AI Memo sit **in the same repository under the same handle prefix**, which is §5.2's point about MIT filing theses and reports together |
-
-### 9.2 Computer architecture, VLSI and the Mead/Seitz lineage
-
-| # | Thesis | Author | Degree · Institution · Year | Identifier | Verified how | Why it matters |
-|---|---|---|---|---|---|---|
-| 6 | **Design of the RISC-V Instruction Set Architecture** | Andrew Waterman | **PhD**, UC Berkeley, **2016-01-03** | **`UCB/EECS-2016-1`** | Wayback replay, magic-byte-checked PDF **959,927 B, `%PDF-1.4`** [WEB via Wayback] | **The design rationale for RISC-V**, which exists in no conference paper. Already verified in [`government-and-institutional-technical-reports.md` §3.1](government-and-institutional-technical-reports.md) and re-verified here at the identical byte size. ⚠ **Its canonical URL 404s as of 2026-09-04 — see §5.4** |
-| 7 | **Improving Energy Efficiency and Reducing Code Size with RISC-V Compressed** | Andrew Waterman | **MS thesis**, UC Berkeley, **2011-05-13** (advisors Patterson & Asanović) | **`UCB/EECS-2011-63`** | [companion record §3.1](government-and-institutional-technical-reports.md), Wayback [WEB] | The RVC compressed-instruction design. **The department's own generated BibTeX types it `@mastersthesis`** — the cleanest single proof that Berkeley's report series *is* its thesis series |
-| 8 | **A VLSI Architecture for Concurrent Data Structures** | William James Dally | **PhD** (Dissertation), Caltech, **1986** | **DOI `10.7907/f8d5-x741`** | DataCite REST, prefix `10.7907` [API] | Concurrent data structures in silicon; the direct ancestry of modern **network-on-chip** and message-passing multicomputer design. Chuck Seitz's group, Mead-lineage Caltech VLSI |
-| 9 | **The Torus Routing Chip** | William J. Dally, Charles L. Seitz | Caltech technical note, **1986** | **DOI `10.7907/99gpd-5kg37`** | DataCite REST [API] | **Wormhole routing.** Listed here because it is the companion report to entry 8 and is *the* primary source for the interconnect technique used in essentially every modern many-core and HPC fabric |
-| 10 | **VLSI analogs of neuronal visual processing: a synthesis of form and function** | Misha Mahowald | **PhD** (Dissertation), Caltech, **1992** | **DOI `10.7907/4bdw-fg34`** · (a `Technical note` twin exists at `10.7907/z9cz35cd`) | DataCite REST [API] | **The silicon retina.** Carver Mead's student; the founding document of **neuromorphic engineering** and of address-event representation. One of the clearest cases in this record of a thesis being the complete work and the papers being fragments |
-| 11 | **Accurate and precise computation using analog VLSI, with applications to computer graphics and neural networks** | David B. Kirk | **PhD** (Dissertation), Caltech, **1993** | **DOI `10.7907/1ykm-yq27`** | DataCite REST [API] | Analog VLSI precision engineering, by the person who later became NVIDIA's Chief Scientist. A direct bridge from Mead-lineage analog VLSI to modern GPU computing |
-| 12 | **Performance analysis and optimization of asynchronous circuits** | Steven Morgan Burns | **PhD** (Dissertation), Caltech, **1991** | **DOI `10.7907/kez1-7q52`** | DataCite REST [API] | Alain Martin's **quasi-delay-insensitive asynchronous VLSI** programme. The performance-analysis framework for clockless design |
-| 13 | **A General Approach to Performance Analysis and Optimization of Asynchronous Circuits** | Tak Kwan Lee | **PhD** (Dissertation), Caltech, **1995** | **DOI `10.7907/ehzs-y537`** | DataCite REST [API] | Continues entry 12; the standard reference for asynchronous-circuit timing analysis |
-| 14 | **Energy-delay complexity of asynchronous circuits** | Paul Ivan Pénzes | **PhD** (Dissertation), Caltech, **2002** | **DOI `10.7907/9jpj-5s67`** | DataCite REST [API] | Energy–delay product as a first-class design objective for clockless logic — the argument that made asynchronous design an energy story rather than a timing story |
-| 15 | **The architecture and programming of a fine-grain multicomputer** | Jakov N. Seizovic | **PhD** (Dissertation), Caltech, **1994** | **DOI `10.7907/53vc-hs15`** | DataCite REST [API] | Caltech Mosaic; fine-grain message-passing multicomputers. Direct ancestry of modern manycore |
-| 16 | **Large operand division and an asynchronous approach to fault detection** | Kathleen A. Kramer | **PhD** (Dissertation), Caltech, **1991** | **DOI `10.7907/pt8p-9g83`** | DataCite REST [API] | Arithmetic hardware and self-checking logic in the same asynchronous programme |
-
-### 9.3 Hardware security, memory systems and modern systems software
-
-| # | Thesis | Author | Degree · Institution · Year | Identifier | Verified how | Why it matters |
-|---|---|---|---|---|---|---|
-| 17 | **Semi-invasive attacks – A new approach to hardware security analysis** | Sergei P. Skorobogatov | **PhD**, University of Cambridge, **Darwin College**; dissertation submitted **September 2004**, issued as a technical report **April 2005**, **144 pages** | **`UCAM-CL-TR-630`**, DOI **`10.48456/tr-630`** · PDF **11,754,717 B** | Cambridge CL abstract page [WEB] + PDF `content-type: application/pdf`, 11,754,717 B [WEB] | **The foundational document of optical fault injection and semi-invasive chip attack methodology.** Decapsulation, laser parameters, per-chip results — everything the CHES/FDTC papers had to cut. Directly relevant to [`cryptology-eprint-archive.md` §7.6](cryptology-eprint-archive.md) |
-| 18 | **Improving DRAM Performance, Reliability, and Security by Rigorously Understanding Intrinsic DRAM Operation** | Hasan Hassan | **PhD** (Dissertation), **ETH Zürich**, **2022** | **DOI `10.3929/ethz-b-000601914`** | DataCite REST, prefix `10.3929` [API] | SAFARI group (Onur Mutlu). DRAM characterisation infrastructure and intrinsic-behaviour measurement — the apparatus behind a decade of DRAM papers |
-| 19 | **Enabling Efficient and Scalable DRAM Read Disturbance Mitigation via New Experimental Insights into Modern DRAM Chips** | A. Giray Yağlıkçı | **PhD** (Dissertation), **ETH Zürich**, **2024** | **DOI `10.3929/ethz-b-000691009`** | DataCite REST [API] | The **RowHammer lineage** in long form. [`landmark-papers.md` §1](landmark-papers.md) records that the original RowHammer paper is **not on arXiv**; this is the deep version of that line of work |
-| 20 | **Principled DRAM Security against Rowhammer Attacks** | Michele Marazzi | **PhD** (Dissertation), **ETH Zürich**, **2024** | **DOI `10.3929/ethz-b-000698237`** | DataCite REST [API] | In-DRAM target-row-refresh analysis (PROTRR, REGA, ZenHammer lineage). The mitigation side of entry 19 |
-| 21 | **Enabling Effective Error Mitigation in Memory Chips That Use On-Die Error-Correcting Codes** | Minesh Patel | **PhD** (Dissertation), **ETH Zürich**, **2021** | **DOI `10.3929/ethz-b-000542542`** | DataCite REST [API] | On-die ECC and its interaction with error characterisation — the reason modern DRAM reliability measurements are hard to interpret |
-| 22 | **REFault: A Fault Injection Platform for Rowhammer Research on DDR5 Memory** | Stefan Gloor | **Bachelor Thesis**, **ETH Zürich**, **2023** | **DOI `10.3929/ethz-b-000722911`** | DataCite REST [API] | Included deliberately. **A bachelor's thesis documenting a DDR5 fault-injection platform is a more useful engineering document than most conference papers on the topic** — §5.5's point about not filtering by degree level |
-| 23 | **Improving DRAM Performance, Security, and Reliability by Understanding and Exploiting DRAM Timing Parameter Margins** | Jeremie Kim | **PhD** (Thesis), **Carnegie Mellon University**, **2020** | **DOI `10.1184/r1/13318703`** (version DOI `…13318703.v1`) | DataCite REST, prefix `10.1184` [API] | The CMU half of the same DRAM programme. **Note the concept/version DOI pair** — the figshare version-counting trap recorded in [`retrieval-notes.md` §7](retrieval-notes.md) applies to KiltHub |
-| 24 | **Techniques for Shared Resource Management in Systems with Throughput Processors** | Rachata Ausavarungnirun | **PhD** (Thesis), **Carnegie Mellon University**, **2017** | **DOI `10.1184/r1/6723512`** | DataCite REST [API] | GPU memory-system and shared-resource management; the long form of a body of MICRO/ISCA work |
-| 25 | **Linux: a Portable Operating System** | **Linus Torvalds** | **Master of Science thesis**, **University of Helsinki**, Department of Computer Science, **31 January 1997**, **52 pages** | **No repository identifier.** PDF at `https://www.cs.helsinki.fi/u/kutvonen/index_files/linus.pdf` — **HTTP 200, 470,861 bytes, `%PDF-1.3`** | Direct PDF retrieval; **title, author, date, degree, page count and keywords extracted from the PDF's own title page and Finnish/Swedish/English abstract form** [WEB] | Torvalds's account of making Linux portable — the Alpha and SPARC ports, and the architectural abstractions that made Linux multi-architecture. Keywords on the abstract form: *"Linux, Operating System, Portability, Alpha, Sparc"*. **⚠ It is NOT in Helda, the University of Helsinki institutional repository** — two separate DSpace REST searches (`"Linux portable operating system Torvalds"`, `"Torvalds"`, 3 and 77 hits) returned it in neither. **It survives on a professor's departmental home page.** §5.8 step 6 exists because of this case, and it is the top `web.archive.org/save/` candidate in §13 |
-| 26 | **Abstraction in technical computing** | Jeffrey Werner Bezanson | **PhD**, MIT, **2015** · advisor **Alan Edelman** | **`hdl:1721.1/99811`** · (the 2012 master's, **"Julia: an efficient dynamic language for technical computing"**, is **`hdl:1721.1/74897`**, same advisor) | MIT DSpace REST [API] | **The Julia language**, documented in full. The PhD is the design argument — multiple dispatch, type inference over a dynamic language, the "two-language problem" — at a depth the papers do not reach. Two theses, one language: the master's is the implementation, the PhD is the theory |
-
-### 9.4 Dropped — could not be confirmed
-
-Listed by name, per README rule 5. **These are not claims of absence**; they are claims that this
-pass did not verify them.
-
-| Candidate | What was tried | Result |
-|---|---|---|
-| **Daniel Gruss, PhD, TU Graz** (Spectre/Meltdown lineage) | TU Graz Pure (`graz.elsevierpure.com`, **403 Cloudflare**), `diglib.tugraz.at`, CORE full-text search, DataCite by creator name | **Only the published dissertation *summary* was verified: `10.1515/itit-2018-0034`, "Software-based microarchitectural attacks", *it – Information Technology*, De Gruyter, 2018-11-20 [API Crossref].** That is a ~4-page digest, **not the thesis.** Full dissertation **[NOT-VERIFIED]** |
-| **Moritz Lipp, PhD, TU Graz** | DataCite by name, CORE | 0 hits. **[NOT-VERIFIED]** |
-| **Jo Van Bulck / KU Leuven COSIC theses** | Lirias (`lirias.kuleuven.be` → Primo SPA, no API found), CORE | CORE returned his **papers** (SGX-Step, Plundervolt, Foreshadow lineage) but no thesis record. **[NOT-VERIFIED]** |
-| **Yuval Yarom-adjacent side-channel theses** | Not systematically searched within budget | **[NOT-VERIFIED]** |
-| **Onur Mutlu's own PhD** (UT Austin, 2006) | Not probed — UT Austin's repository was not reached in this pass | **[NOT-VERIFIED]**. The ETH theses he *supervised* (entries 18–21) are verified |
-| **Yoongu Kim, PhD, CMU** (original RowHammer author) | DataCite `creators.name:"Kim, Yoongu" AND types.resourceType:Thesis`, prefix `10.1184` → **0 hits** (his *papers* are in KiltHub as "Journal contribution") | **[NOT-VERIFIED]** |
-| **David Patterson-advised Berkeley RISC theses** | Berkeley EECS TR series **404s** (§5.4); eScholarship returned **HTTP 202 / 0 bytes** | **[NOT-VERIFIED].** The only Berkeley entries here (6, 7) come from Wayback |
-| **Additional Carver Mead direct-student theses** beyond Mahowald and Kirk | DataCite prefix `10.7907` topic queries returned mostly biology-retina false positives | Not individually confirmed. **[NOT-VERIFIED]** |
-| **Jay Forrester, MIT** (magnetic core memory) | MIT DSpace query returned no plausible match in the top hits | **[NOT-VERIFIED]** |
-
-### 9.5 What the table shows
-
-**Three observations that were not obvious before assembling it.**
-
-**One: 4 of 26 entries are not in a thesis repository at all.** Entries 2 (partly), 6, 7, 9 and 17
-are **technical reports**, and entry 25 is a PDF on a personal page. That is ~20% of the most
-important theses in computing living outside the thesis infrastructure entirely. **A search
-restricted to "theses" collections misses them.** This is the strongest possible argument for
-reading this record and
-[`government-and-institutional-technical-reports.md`](government-and-institutional-technical-reports.md)
-as one document.
-
-**Two: the identifier types are completely heterogeneous.** Handles (`1721.1/…`), DataCite DOIs
-(`10.7907/…`, `10.3929/…`, `10.1184/…`), Cambridge's own DOI prefix (`10.48456/tr-…`), Berkeley
-report numbers (`UCB/EECS-…`), a French NNT, an EThOS ID, and — for Torvalds — **nothing at all**.
-There is no universal thesis identifier and there is not going to be one. Cite whatever the holding
-institution mints, and record the institution.
-
-**Three: the modern entries all have DOIs and the historical ones mostly do not.** Everything from
-2020 onward in this table (18–23) carries a DataCite DOI assigned at deposit. Everything before
-1995 is handle-based or has an identifier retrofitted decades later (Caltech's `10.7907` prefix
-covers 1985 technical notes — clearly a retrospective minting exercise, and a good one). **The
-durability outlook for theses deposited today is materially better than for the historical corpus**
-— which makes §5.4's Berkeley failure, affecting the *un*-DOI'd historical series, the more urgent
-problem.
-
----
-
-## 10. Access, APIs and bulk retrieval
-
-### 10.1 The hierarchy that actually works
-
-Ordered by how reliably each answered during this pass:
-
-| Rank | Route | Why | Verified on |
-|---|---|---|---|
-| **1** | **DSpace 7 REST** — `GET /server/api/discover/search/objects?query=…&size=…` | Full JSON, **including `dc.contributor.advisor` and `dc.rights`**. No key. Answers **from behind an Anubis wall** | `dspace.mit.edu`, `helda.helsinki.fi`, `bl.iro.bl.uk` |
-| **2** | **DataCite REST** — `api.datacite.org/dois?query=…&prefix=…` | Works when the repository does not. Filter with `types.resourceType:Dissertation` / `:Thesis` | Caltech `10.7907`, ETH `10.3929`, CMU `10.1184`, BL `10.23636` |
-| **3** | **OAI-PMH** | Open on hosts whose websites are walled. `resumptionToken/@completeListSize` gives you a count in one call | DiVA, DNB, ETH |
-| **4** | **`hdl.handle.net/api/handles/<prefix>/<suffix>`** | JSON existence oracle, **immune to the target's bot wall** | TDX `10803`, MIT `1721.1` |
-| **5** | **Purpose-built national APIs** | theses.fr, CiNii, HAL/TEL, CORE, OpenAIRE all answer plain `curl` | §2, §4 |
-| **6** | **ResourceSync** | Rare, but EThOS's `resourcelist` is a complete 654,832-URL enumeration in one 88 MB response | `ethos.bl.uk` |
-| **7** | **Bulk CC-BY dumps** | The EThOS CSV; OpenAlex's S3 snapshot | §3.6 |
-
-### 10.2 Worked invocations
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-
-# --- DSpace 7: search any repository, get advisor + rights ------------------
-curl -s -A "$UA" -G "https://dspace.mit.edu/server/api/discover/search/objects" \
-     --data-urlencode 'query=connection machine Hillis' --data-urlencode 'size=5'
-#   → _embedded.searchResult._embedded.objects[]._embedded.indexableObject
-#       .handle, .uuid, .metadata['dc.contributor.advisor'], .metadata['dc.rights']
-
-# --- DataCite: theses by prefix and type ------------------------------------
-curl -s -G "https://api.datacite.org/dois" \
-     --data-urlencode 'query=DRAM AND types.resourceType:Dissertation' \
-     --data-urlencode 'prefix=10.3929' --data-urlencode 'page[size]=10'
-
-# --- OAI-PMH: identify, then count via completeListSize ---------------------
-curl -s "https://www.diva-portal.org/dice/oai?verb=Identify"
-curl -s "https://www.diva-portal.org/dice/oai?verb=ListIdentifiers&metadataPrefix=oai_dc" \
-  | grep -o 'completeListSize="[0-9]*"'          # → 800381
-
-# --- Handle existence oracle (works through Cloudflare) ---------------------
-curl -s "https://hdl.handle.net/api/handles/10803/1234"      # responseCode 1  = exists
-curl -s "https://hdl.handle.net/api/handles/10803/99999999"  # responseCode 100 = absent
-
-# --- theses.fr (France) -----------------------------------------------------
-curl -s "https://theses.fr/api/v1/theses/recherche/?q=*&nombre=1"        # 564318
-curl -s "https://theses.fr/api/v1/personnes/recherche/?q=Asanovic&nombre=5"
-curl -s "https://theses.fr/api/v1/theses/these/2016PA066033"
-
-# --- TEL via HAL (France, full text) ---------------------------------------
-curl -s 'https://api.archives-ouvertes.fr/search/tel/?q=domainAllCode_s:"spi.tron"&rows=0&wt=json'
-
-# --- CiNii Dissertations (Japan) — NOTE the mandatory date range ------------
-curl -s "https://cir.nii.ac.jp/opensearch/dissertations?format=json&count=1&from=1900"
-
-# --- CORE (largest queryable thesis index) — NOTE the trailing slash --------
-curl -s -G "https://api.core.ac.uk/v3/search/works/" \
-     --data-urlencode 'q=documentType:"thesis" AND "RISC-V"' --data-urlencode 'limit=5'
-
-# --- OpenAIRE type facets ---------------------------------------------------
-curl -s "https://api.openaire.eu/search/publications?instancetype=Doctoral+thesis&size=1&format=json"
-
-# --- EThOS: complete record enumeration (88 MB) -----------------------------
-curl -s -A "$UA" "https://ethos.bl.uk/capabilitylist?locale=en"
-curl -s -A "$UA" "https://ethos.bl.uk/resourcelist" -o ethos-resourcelist.xml
-
-# --- EThOS: the 709 MB CC-BY bulk metadata CSV ------------------------------
-curl -s "https://api.datacite.org/dois/10.23636/rcm4-zk44"
-curl -s "https://bl.iro.bl.uk/server/api/core/items/ef18a65d-a839-428b-abbc-2da178007e4e/bundles"
-curl -sL -H 'Range: bytes=0-3000' \
-  "https://bl.iro.bl.uk/server/api/core/bitstreams/a10353df-67a5-4d47-9d33-4c764f605eb5/content"
-```
-
-### 10.3 Negative controls — every probe pattern used in this record
-
-Per [README rule 3](README.md#evidence-and-method): a 200 does not mean the document exists.
-
-| Host / pattern | Real | Bogus | Trustworthy? |
-|---|---|---|---|
-| `dspace.mit.edu/handle/1721.1/<n>` | **200**, 552,361 B | **404**, 444,910 B | ✅ **status yes, byte size no** (both are large Angular shells) |
-| MIT DSpace REST `?query=` | `totalElements` > 0 | **`totalElements: 0`** | ✅ clean |
-| `api.datacite.org/dois/<doi>` | 200 | **404, 87 B** | ✅ clean |
-| `hdl.handle.net/api/handles/<h>` | `responseCode: 1` | **`responseCode: 100`** | ✅ **best oracle in this record** |
-| `ethos.bl.uk/concern/thesis_or_dissertations/<n>` | 200, 69,494 B | **404, 1,676 B** | ✅ clean |
-| **`ethos.bl.uk/OrderDetails.do?uin=…`** | 200 → redirect to record | ⚠ **200, 62,214 B — silently the home page** | ❌ **no negative signal** |
-| **`theses.fr/api/v1/theses/these/<NNT>`** | 200, full JSON | ⚠ **200, zero-byte body** | ❌ **status useless; test body length** |
-| `cir.nii.ac.jp/opensearch/dissertations?q=` | > 0 | 0 for a bogus term — ✅ — **but also 0 with no parameters** | ⚠ **the empty-query trap** |
-| `api.core.ac.uk/v3/search/works/` | JSON | — | ⚠ **`/works` without the slash → 200 + Cloudflare HTML redirect, not JSON** |
-| `api.openaire.eu/search/publications?type=…` | — | **400 + an enumeration of valid parameters** | ✅ **exemplary** |
-| **any OAI-PMH `verb=`** | 200 + data | ⚠ **200 + an `<error>` element** (ETH: 200, 488 B) | ❌ **OAI-PMH signals errors in the body, never in the status. By design** |
-| `hdl` on Cloudflare-walled TDX | works | works | ✅ routes around the wall |
-
-### 10.4 Bulk retrieval — what is actually available
-
-| Dump | Size | Licence | Contents |
-|---|---|---|---|
-| **`EThOS_CSV_202310.csv`** (DOI `10.23636/rcm4-zk44`, handle `britishlibrary-iro/19931`) | **709,733,446 B** | **CC-BY 4.0** | ~650,000 UK doctorates: Title, DOI, Author, Author ISNI, ORCID, Institution, Institution ISNI, Date, Qualification, Abstract, **Subject Discipline**, **Supervisor(s)**, **Funder(s)**, EThOS URL, **IR URL** |
-| **EThOS ResourceSync `resourcelist`** | **88,402,587 B** | — | 654,832 record URLs + `lastmod` |
-| DiVA OAI-PMH full harvest | not measured | — | 800,381 records, `deletedRecord=persistent` |
-| DNB OAI-PMH | not measured | — | `earliestDatestamp` 1945 |
-| ETH OAI-PMH | not measured | — | `earliestDatestamp` 2017-05-15 (platform migration, **not** a coverage floor) |
-| **NDLTD union-catalogue OAI-PMH** | — | — | ❌ **HTTP 503. Gone** |
-| **OATD bulk** | — | — | ❌ **None advertised; site is Cloudflare-walled including `robots.txt`** |
-
-**The EThOS CSV deserves emphasis as the single best bulk artefact in this record.** It is the only
-large, openly-licensed, supervisor-bearing thesis dataset this survey located. It makes §5.8's
-technique work offline for an entire country, and it survived the destruction of the service that
-produced it (§3.6).
-
-### 10.5 Rate limits and courtesy
-
-- **Internet Archive is the binding constraint**, exactly as
-  [`retrieval-notes.md` §2](retrieval-notes.md) records. This pass hit `000`-flapping again on
-  replay fetches while the CDX endpoint continued to answer for a while. **Retry a CDX query at
-  least twice before recording "no captures", and use `id_` replay sparingly.**
-- **DataCite, Crossref, Handle.net, OpenAIRE, CORE, theses.fr, CiNii, HAL and the DSpace REST APIs
-  all answered plain `curl` without complaint** during this pass. None required a key. Be polite
-  anyway.
-- **`shodhganga.inflibnet.ac.in` is slow (13–21 s) and drops roughly one request in four.** Set a
-  long timeout and retry rather than concluding it is down (§4.7).
-- **ETH's block is IP/provider-scoped and self-documenting** — it names a contact address (§5.5).
-  Use it rather than rotating agents.
-- **Anubis-walled hosts cannot be persuaded.** `theses.hal.science`, `portal.dnb.de`, `rcaap.pt`,
-  `trove.nla.gov.au`, `helda.helsinki.fi`, `base-search.net`. Go to the API, and if there is no
-  API (RCAAP) accept the gap.
-
----
-
-## 11. A practical recipe
-
-Copy-pasteable. Two entry points.
-
-### 11.1 "I have a paper and I want the long version"
-
-```
- 1. Identify the student.
-    Usually the first author. Take the AFFILIATION FROM THE EARLIEST PAPER
-    in that line of work — that is where they were a student.
-
- 2. Identify the advisor.
-    Usually the last author, or the known head of the group.
-
- 3. Estimate the year.
-    Year of the last first-author paper in the line, + 0 or 1.
-
- 4. Query the institution's repository REST API by SURNAME, not by title:
-      curl -s -G "https://<repo>/server/api/discover/search/objects" \
-           --data-urlencode "query=<student surname>" --data-urlencode "size=50"
-    Look for dc.contributor.advisor to confirm you have the right person.
-    (Works on any DSpace 7 install; MIT and Helda verified.)
-
- 5. If the repository is walled or you do not know it, go to DataCite:
-      curl -s -G "https://api.datacite.org/dois" \
-           --data-urlencode 'query=creators.name:"<Surname, Given>" AND types.resourceType:Dissertation' \
-           --data-urlencode 'page[size]=20'
-    Add --data-urlencode 'prefix=10.XXXX' if you know the institution's prefix:
-      Caltech 10.7907 · ETH Zurich 10.3929 · CMU 10.1184 · British Library 10.23636
-      Cambridge CL 10.48456 · theses.fr 10.70675
-
- 6. Country-specific shortcuts:
-      France   curl -s "https://theses.fr/api/v1/theses/recherche/?q=<name>&nombre=20"
-               curl -s "https://theses.fr/api/v1/personnes/recherche/?q=<advisor>&nombre=5"
-      France (full text, incl. HDR)
-               curl -s 'https://api.archives-ouvertes.fr/search/tel/?q=authFullName_s:"<name>"&wt=json'
-      UK       grep the 709 MB EThOS CSV on Supervisor(s) or Author, then follow the IR URL column
-               (or search https://ethos.bl.uk/ ; legacy OrderDetails.do?uin=uk.bl.ethos.<n> still resolves)
-      Japan    curl -s "https://cir.nii.ac.jp/opensearch/dissertations?q=<name>&format=json&from=1900"
-      Sweden   DiVA OAI-PMH, or the diva-portal.org web search
-      India    https://shodhganga.inflibnet.ac.in/ — browse by "Researcher/Guide"
-      Germany  the university repository directly; DNB OAI at services.dnb.de/oai/repository
-
- 7. Cross-institution fallbacks, in order:
-      CORE      curl -s -G "https://api.core.ac.uk/v3/search/works/" \
-                     --data-urlencode 'q=documentType:"thesis" AND "<phrase>"' --data-urlencode 'limit=10'
-                (NOTE the trailing slash on /works/)
-      OpenAIRE  https://api.openaire.eu/search/publications?instancetype=Doctoral+thesis&title=<...>&format=json
-      OATD      https://oatd.org/  — browser only; 403s every automated client
-      BASE      https://www.base-search.net/  — browser only; Anubis proof-of-work
-
- 8. If it is not in a "theses" collection, look in the TECHNICAL REPORT series:
-      Cambridge CL   https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-<n>.pdf   (DOI 10.48456/tr-<n>)
-      CMU SCS        http://reports-archive.adm.cs.cmu.edu/
-      MIT AI Memos   dspace.mit.edu handle 1721.1/5460
-      Berkeley EECS  UCB/EECS-<year>-<n>  ⚠ URLs 404 since ~2026-08 — use the Wayback Machine:
-        http://web.archive.org/web/2022id_/https://www2.eecs.berkeley.edu/Pubs/TechRpts/<year>/EECS-<year>-<n>.pdf
-
- 9. Still nothing? Check the personal page.
-      site:<dept domain> ~<surname>   — Torvalds's thesis lives at
-      https://www.cs.helsinki.fi/u/kutvonen/index_files/linus.pdf and nowhere institutional.
-      If you find one, submit it to https://web.archive.org/save/ (AGENTS.md rule 9).
-
-10. Record has no file? It is probably an EMBARGO, not a dead link (§8.2).
-      Look for dc.date.available in the future; use the repository's "request a copy" button;
-      re-check in a year; email the author.
-```
-
-### 11.2 "I have an author name and nothing else"
-
-```
- 1. Resolve the person, not the string.
-      ORCID     https://pub.orcid.org/v3.0/expanded-search/?q=<name>   (public API)
-      France    https://theses.fr/api/v1/personnes/recherche/?q=<name>&nombre=10
-                → gives PPN, and role counts (directeur / rapporteur / examinateur)
-      dblp      https://dblp.org/search/publ/api?q=<name>&format=json  (see open-access record)
-
- 2. From any paper, take the earliest affiliation → institution.
-
- 3. Run step 4/5 of §11.1 against that institution.
-
- 4. If the person is a SUPERVISOR and you want their students:
-      MIT-style:  search dc.contributor.advisor (§5.8)
-      France:     theses.fr /personnes → the roles object counts their supervisions
-      UK:         grep the EThOS CSV Supervisor(s) column
-      India:      Shodhganga "Researcher/Guide" browse
-
- 5. Verify before citing.
-      Retrieve the record. Check degree, institution, and year of award.
-      Check dc.rights before reusing anything (§8.3).
-      Cite the handle / DOI / NNT / report number — never the URL (§5.4 is why).
-```
-
----
-
-## 12. Retrieval notes — new fingerprints and traps from this pass
-
-Staged for [`retrieval-notes.md`](retrieval-notes.md) and thence
-[`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md), per `AGENTS.md`
-rule 8. Nothing below was obtained by bypassing authentication or an access control.
-
-### 12.1 New block fingerprints
-
-| Fingerprint | Product | Hosts observed (2026-09-04) |
-|---|---|---|
-| **HTTP 403, ~1,337 B, `<title>Access Restricted</title>`, inline Segoe-UI CSS, contact `research-collection@library.ethz.ch`, text *"temporarily restricted from your location / your provider"*, spelling *"accidentially"*** | **Custom, IP/provider-scoped** — **NEW** | `www.research-collection.ethz.ch` REST API |
-| HTTP 403, **5,207–6,102 B**, `<title>Just a moment...</title>` | Cloudflare managed challenge (extends the ~5.58–5.62 kB range already recorded) | `oatd.org` (5,207–5,821, **incl. `robots.txt`**) · `tdx.cat` (5,658–5,769) · `ethos.bl.uk/catalog*` (5,757–5,905) · `recherche-collection-search.bac-lac.gc.ca` (5,775) · `graz.elsevierpure.com` (6,102) |
-| HTTP 200, **4,262–12,607 B**, `<title>Making sure you're not a bot!</title>`, `/.within.website/x/xess/xess*.css?cachebuster=<ver>` | **Anubis proof-of-work — now endemic in the ETD layer** | `theses.hal.science` (12,607, `devel`) · `portal.dnb.de` (4,475, `1.25.0`) · `rcaap.pt` (4,511, `v1.26.0-pre2`) · `trove.nla.gov.au` (7,745, `v1.26.2`) · `helda.helsinki.fi` (4,262, `1.23.0`) · `base-search.net` (7,846, `v1.27.0+dirty`) · `dans.knaw.nl` (4,437, `1.25.0`) |
-| HTTP 200, 1,697 B, `<title>Verificando conexão \| Oasisbr</title>` | Brazilian challenge page — **NEW** | `bdtd.ibict.br` |
-| HTTP 503, **505 B**, stock nginx *"503 Service Unavailable"* | Backend down behind a live proxy | `search.ndltd.org`, `union.ndltd.org` |
-| **HTTP 202, 0 bytes** | figshare/eScholarship non-answer (already recorded for `figshare.com`, `kilthub.cmu.edu`) — **now also** | `escholarship.org` |
-
-**The headline: Anubis has spread from scholarly publishers to national libraries.**
-[`retrieval-notes.md` §3](retrieval-notes.md) listed seven hosts. This pass adds seven more,
-including **three national libraries** (DNB, NLA/Trove, DANS) and **the French national thesis
-archive**. Its finding stands and hardens: **no user agent defeats it; find the API.** With one new
-exception — **`rcaap.pt` puts its OAI-PMH endpoint behind the wall too**, the first host where the
-escape hatch failed.
-
-### 12.2 New soft-200s and API traps
-
-| Host / pattern | Behaviour | Consequence |
-|---|---|---|
-| **`ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.<bogus>`** | **HTTP 200, 62,214 B — the home page**, byte-identical to a successful `GET /` | A link-checker validating legacy EThOS citations reports **100% success regardless**. Validate against `/concern/thesis_or_dissertations/<n>`, which 404s honestly (1,676 B) |
-| **`theses.fr/api/v1/theses/these/<bogus NNT>`** | **HTTP 200 with a zero-byte body** | Status code useless; JSON parser gets EOF. **Test body length** |
-| **`api.core.ac.uk/v3/search/works`** *(no trailing slash)* | **HTTP 200 + a Cloudflare `cdn-cgi/content` `<meta refresh>` HTML page**, not JSON | Silent corruption. **Always use `/works/`** |
-| **`cir.nii.ac.jp/opensearch/dissertations`** with no parameters | **`totalResults: 0`** — and `q=*` also returns 0 | **Third independent instance** of the empty-query trap after NASA NTRS and DOE OSTI. Use a wide `from=`/`until=` range |
-| **Any OAI-PMH `verb=<bogus>`** | **HTTP 200** with an `<error>` element in the body (ETH: 200, 488 B) | By design in the protocol. **Never status-check OAI-PMH; parse the body** |
-| **`shodhganga.inflibnet.ac.in` home page** | Live counter `697675` sits **beside a commented-out stale block reading `597316`** and a commented-out `99999` placeholder | **A tag-stripping extractor that does not strip HTML comments reads a figure 100,359 too low.** Strip comments first |
-| **`web.archive.org/cdx`** | Returned a **negative `length` field**: `20250926194305 403 -6693296525` | A parser doing `int(length)` and summing will produce nonsense. **Validate CDX lengths ≥ 0** |
-| `getent hosts catalogodeteses.capes.gov.br` | Returns **only the AAAA record**; an A record exists and is visible via `getent ahostsv4` | Makes an IPv4-reachable host look IPv6-only. **Check both families** |
-| KiltHub / figshare DataCite records | Concept DOI and `.v1` version DOI both returned as separate hits | The version-vs-work inflation already recorded for Zenodo/OSF/TechRxiv applies to institutional figshare tenants |
-
-### 12.3 Ladder notes
-
-- **`shodhganga.inflibnet.ac.in` initially looked like a reversed ladder** (`curl/8.5.0` succeeded,
-  Chrome-131 timed out) — **it did not reproduce.** Three subsequent Chrome requests gave
-  `200 / 200 / 000` at 13.5–21.1 s. It is a **slow, intermittently-overloaded origin**, not a UA
-  filter. Recorded because the wrong conclusion was one probe away, and it is the kind of thing that
-  ends up in a table and never gets rechecked.
-- **`www2.eecs.berkeley.edu` is no longer TCP-dead** — a change from
-  [`retrieval-notes.md` §5](retrieval-notes.md), which recorded a timeout on :443 and :80 with all
-  UAs on 2026-09-01/02. On 2026-09-04 it **answers and 302s** to `iris.eecs.berkeley.edu`. **The
-  host recovered and the content did not** (§5.4).
-- **No user-agent fallback was needed anywhere in this pass** except to confirm that fallbacks do
-  not work: OATD 403s all five rungs, Anubis hosts are agent-agnostic by construction, and ETH's
-  block is IP-scoped and says so. **The UA ladder solved nothing in this record.** What solved
-  things was **changing protocol** — OAI-PMH, DataCite, Handle.net, DSpace REST.
-
----
-
-## 13. Explicitly not verified, and what to do next
-
-Listed so the gaps are visible rather than silent.
-
-### 13.1 Could not verify
-
-1. **OATD's current record count.** Cloudflare-403 on five UAs including `robots.txt`. The 7,407,210
-   figure is from a 2025-03-04 Wayback capture and is **18 months stale**.
-2. **DART-Europe's record count and participating-country count.** Portal closed 2025-02-03; the
-   closure notice carries no figures. **A Wayback replay of the pre-closure front page is the
-   obvious next probe and was not run.**
-3. **BASE's thesis count and total size** — Anubis, no API found. Unverified across this whole
-   survey.
-4. **DiVA's doctoral-thesis-only count** — no publication-type OAI set; the web facet needs a JSF
-   session.
-5. **German dissertation count** — DNB OAI `Identify` gives no total; a `ListIdentifiers` walk was
-   not run.
-6. **TDX/TDR, RCAAP, Trove, RISS, CAPES, BDTD, TESEO, Tez Merkezi, Theses Canada counts** — all
-   walled, unreachable or session-bound.
-7. **CAPES reachability** — `000` on IPv4 and IPv6. Recorded as *unreachable from here*, **not** as
-   dead.
-8. **CNKI and Wanfang holdings** — paywalled; nothing measured.
-9. **LA Referencia** — not probed at all.
-10. **PQDT Open's current status.** The standalone host 302s into the main ProQuest platform.
-    Whether a free full-text open subset still exists is unknown. **Do not cite PQDT Open as live.**
-11. **EBSCO Open Dissertations' 2,000,000 / 325 figures** are EBSCO's claim, not a measurement.
-12. **TU Graz dissertations of Daniel Gruss and Moritz Lipp** — Pure is Cloudflare-walled; only
-    Gruss's 4-page De Gruyter dissertation *summary* (`10.1515/itit-2018-0034`) was verified.
-13. **KU Leuven COSIC theses** — Lirias is a Primo SPA; no open API located.
-14. **Onur Mutlu's own PhD** (UT Austin) and **Yoongu Kim's CMU PhD** — not found through the routes
-    tried.
-15. **Berkeley EECS reports beyond the six RISC-V documents**, and **whether the series has a new
-    home**. eScholarship returned HTTP 202 / 0 bytes.
-16. **Embargo rates anywhere.** No repository publishes one and no API exposes an embargo facet.
-    The `dc.date.available` vs `dc.date.issued` differential is measurable in bulk over OAI-PMH and
-    would be a genuinely novel contribution.
-17. **Licence distribution across thesis repositories.** Only MIT's `dc.rights` was read directly.
-18. **Google Scholar coverage of theses** — no API, terms forbid automated querying,
-    `AGENTS.md` rule 7 applies. Permanently unverifiable by this method.
-19. **The exact EThOS relaunch date.** Inferred as ~2026-04/05 from the `lastmod` histogram and the
-    Wayback capture series; no announcement located.
-20. **How many previously-digitised EThOS full texts are now unavailable anywhere.** No public
-    statement quantifies it. This is the most consequential unquantified loss in the record.
-21. **The Trove / Australasian Digital Theses absorption date and mechanism** — Trove is
-    Anubis-walled.
-22. **Whether `netherlands.openaire.eu` is the same object as DANS's "Portal of Research Output from
-    the Netherlands"** (UKB/SURF).
-
-### 13.2 Archival candidates — `AGENTS.md` rule 9
-
-**None were submitted in this pass.** All meet the "scarce, valuable, fragile" bar; the first two
-are urgent.
-
-| Candidate | Why it qualifies |
-|---|---|
-| **`https://www.cs.helsinki.fi/u/kutvonen/index_files/linus.pdf`** | **The most urgent item in this record.** Linus Torvalds's master's thesis, verified **not** to be in the University of Helsinki's institutional repository. It exists as a 470,861-byte PDF on one professor's departmental page. A staff change or a site redesign ends it |
-| **`https://www2.eecs.berkeley.edu/Pubs/TechRpts/<year>/EECS-<year>-<n>.pdf` for the six RISC-V reports** | Already 404 at origin (§5.4). Wayback holds them, but the captures date from 2017–2022 and the CDX shows patchy coverage. **Re-verify each of the six and save what is missing** |
-| `https://ndltd.org/thesis-resources/find-etds/` | The only maintained country-by-country directory of national ETD services, on a WordPress site whose sibling search service has already gone to 503 |
-| `https://ethos.bl.uk/about` and `/FAQs?locale=en` | The British Library's own account of what was lost and what was restored. Primary evidence for the most important durability case study in this directory |
-| `https://dans.knaw.nl/en/data-services/narcis/` | DANS's discontinuation notice — the only primary source for NARCIS's 2023-07-03 end date. Already captured 2026-05-10; **re-check** |
-| `https://www.ucl.ac.uk/library/dart-europe-e-theses-portal-has-closed-down` | UCL's DART-Europe closure notice. The only primary source for the 2025-02-03 date |
-
-### 13.3 Corrections owed to sibling records
-
-Not applied here — this pass wrote only its own file — but flagged for whoever next edits them.
-
-1. **[`government-and-institutional-technical-reports.md` §3.1](government-and-institutional-technical-reports.md)**
-   lists six canonical Berkeley EECS PDF URLs. **All six 404 as of 2026-09-04** (§5.4). The report
-   *numbers* remain correct and the Wayback route works. The section's "unreachable from here"
-   caveat should become "the URL grammar is gone".
-2. **[`retrieval-notes.md` §5](retrieval-notes.md)** lists `www2.eecs.berkeley.edu` under
-   "Unreachable by TCP, not by policy". **It now answers and 302s** (§12.3).
-3. **[`retrieval-notes.md` §3](retrieval-notes.md)**'s Anubis table should gain seven hosts and the
-   `rcaap.pt` exception where OAI-PMH is *also* walled (§12.1).
-4. **[`closed-and-defunct-servers.md` §2.4](closed-and-defunct-servers.md)**'s domain-parking table
-   should gain **Cybertesis** (`cybertesis.net` → a click-monetisation redirect, §4.9), and the
-   record's failure taxonomy has no row for **catastrophic infrastructure destruction**, which
-   EThOS supplies (§3.8).
-5. **[`README.md` § Probing traps](README.md#6-probing-traps)** could gain the three strongest new
-   entries: the **EThOS legacy-URL soft-200**, the **CORE trailing-slash Cloudflare redirect**, and
-   the **HTML-comment stale-counter** trap.
-
----
-
-## 14. Sources
-
-All retrieved **2026-09-04** unless another date is stated. Raw probe output is under
-[`../../scratch/preprint-repositories/theses/`](../../scratch/preprint-repositories/theses/).
-"Chrome 131" = the rung-2 user agent from [`AGENTS.md`](../../AGENTS.md).
-
-**Aggregation layer (§2)**
-
-- **S1** `https://ndltd.org/` — HTTP 200, 135,318 B. NDLTD organisation site. [WEB]
-- **S2** `https://search.ndltd.org/` and `https://union.ndltd.org/OAI-PMH/?verb=Identify` — both
-  **HTTP 503, 505-byte stock nginx page**. Supports §2.2. [WEB/API]
-- **S3** `http://web.archive.org/cdx/search/cdx?url=search.ndltd.org&…&from=2023` and
-  `…?url=union.ndltd.org*&…&from=2022` — capture series showing 200s through 2025-05-16 and 301s
-  from 2025-08-07; `union.ndltd.org/OAI-PMH/` last 200 on 2025-04-20. [WEB]
-- **S4** `http://web.archive.org/web/20250516083247id_/http://search.ndltd.org/` — *"Search the
-  **6,534,039** electronic theses and dissertations contained in the NDLTD archive"*. [WEB via Wayback]
-- **S5** `https://ndltd.org/thesis-resources/find-etds/` — HTTP 200, 132,126 B. The country-by-country
-  ETD directory; source for the §4 target list, the BASE "70 million documents in 3000 repositories"
-  quote, and the Google Scholar annotation. [DOC]
-- **S6** `https://oatd.org/` — HTTP 403 to Chrome 131 (5,442 B), `WhatsApp/2.23.20.0` (5,228 B),
-  ClaudeBot (5,442 B), `curl/8.5.0` (5,207 B), Googlebot (5,292 B); `/robots.txt` 403 (5,493 B);
-  `/oatd/search?q=…` with full browser Accept headers 403 (5,821 B). All Cloudflare
-  "Just a moment…". [WEB]
-- **S7** `http://web.archive.org/web/{20240401084504,20250101215435,20250304050453}id_/https://oatd.org/`
-  — OATD's own counter: **7,421,247** / **7,206,043** / **7,407,210**; "over 1100 colleges,
-  universities, and research institutions"; the operator's 2022-10-03 anti-crawler notice.
-  [WEB via Wayback]
-- **S8** `https://www.dart-europe.org/` → 200 after redirect to
-  `https://www.ucl.ac.uk/library/dart-europe-e-theses-portal-has-closed-down` (22,863 B) — UCL's
-  closure notice, *"closed down permanently on Monday 03 February 2025"*. [DOC]
-- **S9** `https://api.core.ac.uk/v3/search/works/?q=documentType:"thesis"&limit=1` →
-  `totalHits 7,921,188`; `?q=*` → `329,911,927`. Also the no-trailing-slash Cloudflare
-  `cdn-cgi/content` redirect trap. [API]
-- **S10** `https://www.base-search.net/Search/Results?lookfor=riscv&type=all` — HTTP 200, 7,846 B,
-  Anubis `xess.min.css?cachebuster=v1.27.0+dirty`. [WEB]
-- **S11** `https://api.openaire.eu/search/publications?instancetype={Doctoral+thesis,Master+thesis,Thesis}&size=1&format=json`
-  → 3,158,600 / 2,661,863 / 2,525,725. Plus the HTTP 400 parameter-enumeration response to
-  `?type=x`. [API]
-
-**EThOS (§3)**
-
-- **S12** `https://www.bl.uk/cyber-incident/` → 302 → `https://www.bl.uk/about/cyber-attack`,
-  HTTP 200, 133,713 B — the British Library's own cyber-attack statement (October 2023 attack;
-  November 2023 dark-web release; *"rebuild of our entire technology infrastructure"*; March 2024
-  lessons-learned paper). [DOC]
-- **S13** `http://web.archive.org/cdx/search/cdx?url=ethos.bl.uk&…&from=2023` — capture series:
-  last pre-attack 2023-10-08; **no captures Nov 2023 – Feb 2024**; 307/308 monthly through 2026-02;
-  302 from 2026-05. [WEB]
-- **S14** `https://ethos.bl.uk/` — HTTP 200, 62,214 B. Hyku platform, "Platform provided by CoSector,
-  University of London", *"now available again following restoration work"*, "over 650,000". [WEB]
-- **S15** `https://ethos.bl.uk/about` — HTTP 200, 57,645 B. *"this platform is a metadata-only
-  discovery service"*. [DOC]
-- **S16** `https://ethos.bl.uk/FAQs?locale=en` — HTTP 200, 84,307 B. Procurement via public tender;
-  ~14,000 theses added since the attack; **"Over 400,000 theses are openly available for download
-  from university repositories"**; digitisation devolved to universities; "1700s onwards"; next
-  phase later in 2026. *(Note: the site's own nav link `/faqs` lowercase returns **404, 1,676 B**;
-  the working path is `/FAQs`.)* [DOC]
-- **S17** `https://ethos.bl.uk/capabilitylist?locale=en` (200, 457 B) and
-  `https://ethos.bl.uk/resourcelist` (**200, 88,402,587 B**, `at="2026-09-06T16:32:22Z"`) —
-  **654,832** `<loc>` entries; ids 232,781–906,226; `lastmod` histogram. [API]
-- **S18** `https://ethos.bl.uk/concern/thesis_or_dissertations/906226` (200, 69,494 B) — record
-  shape, `uk.bl.ethos.906226`, the "no university copy" message. Negative controls:
-  `/concern/…/99999999` → **404, 1,676 B**; `OrderDetails.do?uin=uk.bl.ethos.906226` → **200 →
-  redirect to the record**; `OrderDetails.do?uin=uk.bl.ethos.99999999` → **200, 62,214 B home
-  page**. [WEB]
-- **S19** `https://api.datacite.org/dois?query=ethos&prefix=10.23636&page[size]=25` and
-  `https://api.datacite.org/dois/10.23636/rcm4-zk44` — 15 EThOS-related DOIs; final dataset
-  `10.23636/rcm4-zk44`, CC-BY 4.0, DataCite record created 2023-11-27T17:07:22Z, *"around 98% of all
-  PhDs ever awarded by UK Higher Education institutions, dating back to 1787"*. [API]
-- **S20** `https://bl.iro.bl.uk/server/api/core/items/ef18a65d-a839-428b-abbc-2da178007e4e`,
-  `/bundles`, and `…/bitstreams/a10353df-67a5-4d47-9d33-4c764f605eb5/content` —
-  handle `britishlibrary-iro/19931`; bitstream **`EThOS_CSV_202310.csv`, 709,733,446 B**; range
-  fetch **HTTP 206, `content-type: text/csv`, `content-range: bytes 0-3000/709733446`**, delivered
-  via a signed `cf002.cdn.4science.cloud` URL; column header and first data row quoted in §3.6.
-  Also: the old `bl.iro.bl.uk/concern/datasets/<uuid>` URLs 302 to `entities/product/<uuid>` —
-  the BL repository migrated Hyrax → DSpace-CRIS. [API]
-
-**National and regional systems (§4)**
-
-- **S21** `https://theses.fr/api/v1/theses/recherche/?q=*&nombre=1` → **564,318**;
-  `/personnes/recherche/` → **918,602**; `/theses/these/2016PA066033` → full record incl. DOI
-  `10.70675/ff0868d0z67ecz4e1bzb948zaa766df489f9`; `q=RISC-V` → 102; bogus NNT → **200, 0 bytes**.
-  [API]
-- **S22** `https://api.archives-ouvertes.fr/search/tel/?q=*:*&rows=0&wt=json` → **180,693**;
-  `facet.field=docType_s` → THESE 171,839 / HDR 8,854; `domainAllCode_s` facet and the 16
-  per-domain counts in §4.2. [API]
-- **S23** `https://www.diva-portal.org/dice/oai?verb={Identify,ListSets,ListIdentifiers}` —
-  `earliestDatestamp` 1900-01-01, `deletedRecord=persistent`,
-  `resumptionToken completeListSize="800381"`, set list. Web search attempt → 4,481-byte stub.
-  [API]
-- **S24** `https://portal.dnb.de/opac.htm` (200, 4,475 B, Anubis `1.25.0`) and
-  `https://services.dnb.de/oai/repository?verb=Identify` (200, 779 B, *"OAI-Repository of the German
-  National Library V2.0.11"*, `earliestDatestamp` 1945-01-01, `deletedRecord=transient`). [WEB/API]
-- **S25** `https://www.tdx.cat/` (403, 5,658 B), `/oai/request?verb=Identify` (403, 5,769 B),
-  `/handle/10803/1234` (403, 5,730 B) — all Cloudflare. `https://hdl.handle.net/api/handles/10803/1234`
-  → `responseCode 1`; `…/10803/99999999` → `responseCode 100`. [WEB/API]
-- **S26** `https://www.rcaap.pt/` and `/OAIHandler?verb=Identify` — 200, 4,511 B, Anubis
-  `v1.26.0-pre2`; `/oai/?verb=Identify` → HTTP 400, 8,698 B Thymeleaf "OAI-PMH Data Provider" page.
-  [WEB]
-- **S27** `https://trove.nla.gov.au/` — 200, 7,745 B, Anubis `v1.26.2`. [WEB]
-- **S28** `https://shodhganga.inflibnet.ac.in/` — 200, 515,934 B (13.5–21.1 s; 1 of 4 attempts
-  `000`). Live counters **697,675** Full Text Theses, 21,723 synopses, 908 contributing
-  universities, 1,060 MoU; nav MoU 943 + 117; announcements "5,35,000 … 27th May 2024" and
-  "6,00,000"; the commented-out stale `597316`/`15274`/`99999` block; "Researcher/Guide" browse.
-  `http://` → `000`. `/oai/request?verb=Identify` → `000`. [WEB]
-- **S29** `https://ci.nii.ac.jp/d/` → 302 → `https://cir.nii.ac.jp/`;
-  `https://cir.nii.ac.jp/opensearch/dissertations?format=json&count=1&from={1,1800,1900}` →
-  **775,786**; `?q=RISC-V` → 6; `opensearch/all?q=RISC-V` → 514; bogus term → 0;
-  **no parameters → 0**; `q=*` → 0. [API]
-- **S30** `https://www.riss.kr/index.do` — HTTP 200, 390,685 B. [WEB]
-- **S31** `https://catalogodeteses.capes.gov.br/` and `/catalogo-teses/` — `000` with default and
-  with `curl -4`; `getent hosts` returns only AAAA (`2001:12f0:b27:1005::38`) while
-  `getent ahostsv4` returns `200.130.18.68`. `https://bdtd.ibict.br/vufind/` — 200, 1,697 B,
-  *"Verificando conexão | Oasisbr"*. [WEB]
-- **S32** `https://www.cybertesis.net/` → `000`; `http://www.cybertesis.net/` → **200, redirects to
-  `https://welcome.lkg-app.com/?clickid=…&dkw=cybertesis.net&pid=…`**, 25,725 B,
-  `<meta name="robots" content="noindex, nofollow">`; DNS `208.91.196.105`. [WEB]
-- **S33** `https://www.narcis.nl/` → redirect to `https://dans.knaw.nl/nl/data-diensten/narcis/`;
-  `http://web.archive.org/web/20260510203109id_/https://dans.knaw.nl/en/data-services/narcis/` —
-  *"As of 3 July 2023, the NARCIS website was taken offline and the NARCIS service ended … 'Portal
-  of Research Output from the Netherlands' … initiated by the UKB and SURF as a successor"*; also
-  *"It is no longer possible to deposit data in EASY"*. CDX series for `narcis.nl` 2022–2026.
-  `https://netherlands.openaire.eu/` — 200, 232,623 B. [DOC/WEB]
-- **S34** `https://www.cnki.net/` → 302 → `https://oversea.cnki.net/`, 50,542 B;
-  `https://www.wanfangdata.com.cn/` — 200, 216,413 B. [WEB]
-- **S35** `https://www.bac-lac.gc.ca/eng/services/theses/Pages/theses-canada.aspx` → `000`;
-  `https://library-archives.canada.ca/eng/services/services-libraries/theses/Pages/theses-canada.aspx`
-  → 302 → `https://www.canada.ca/en/library-archives.html`;
-  `https://recherche-collection-search.bac-lac.gc.ca/eng/Home/Search?q=thesis` → 403, 5,775 B. [WEB]
-- **S36** `https://www.educacion.gob.es/teseo/irGestionarConsulta.do` → 302 →
-  `https://aplicaciones.ciencia.gob.es/teseo` → `000`. [WEB]
-- **S37** `https://tez.yok.gov.tr/UlusalTezMerkezi/giris.jsp` — HTTP 200, 33,811 B. [WEB]
-- **S38** `https://ndltd.org/` navigation and `https://ndltd.org/thesis-resources/find-etds/` —
-  three separate `<a href="https://oatd.org/">Global ETD Search</a>` links, including
-  *"Global ETD Search (previously: Union Catalog)"*. Also the stale EThOS row pointing at
-  `https://bl.iro.bl.uk/`. [WEB]
-
-**Institutional repositories (§5)**
-
-- **S39** `https://dspace.mit.edu/server/api/discover/search/objects?query=…&size=…` — DSpace 7
-  REST, no key. Shannon record (`1721.1/11173`) full metadata map quoted in §5.2, including
-  `dc.contributor.advisor: "Frank L. Hitchcock."`, `dc.description: "Thesis (M.S.)--…, 1940."`,
-  `dc.format.extent: "69 leaves"`, `dc.identifier.oclc: 34541425` and the verbatim `dc.rights`
-  statement. Also entries 2–5 and 26 of §9. Negative controls: `/handle/1721.1/999999999` → 404
-  (444,910 B) vs `/handle/1721.1/11173` → 200 (552,361 B); REST bogus query → `totalElements: 0`.
-  [API]
-- **S40** `https://thesis.library.caltech.edu/` → `000` (Chrome 131 and `curl/8.5.0`);
-  DNS `131.215.225.45` shared with `eprints.library.caltech.edu`;
-  `https://authors.library.caltech.edu/` → 200, 17,077 B (Cloudflare);
-  `https://resolver.caltech.edu/CaltechTHESIS:05282009-153426167` → 404, 1,042 B. [WEB]
-- **S41** `https://api.datacite.org/dois?prefix=10.7907&query=…` — Caltech dissertations and
-  technical notes; §9 entries 8–16. Negative control `https://api.datacite.org/dois/10.7907/zzzz-zzzz`
-  → **404, 87 B**. [API]
-- **S42** `https://www2.eecs.berkeley.edu/Pubs/TechRpts/` → **302 → `https://iris.eecs.berkeley.edu/Pubs/TechRpts/`
-  → 404, 58,829 B**, identical for Chrome 131, `curl/8.5.0` and Googlebot;
-  `…/2016/EECS-2016-1.pdf` → 302 → **404, 548-byte nginx**;
-  `https://eecs.berkeley.edu/research/publications/` → 404, 99,227 B;
-  `https://iris.eecs.berkeley.edu/` → 200, 83,508 B. DNS: `www2` → 128.32.139.28
-  (`eecs-haproxy-vip`), `iris`/`www` → 141.193.213.10/.11 (`wp.wpenginepowered.com`).
-  CDX for the index page: 200s through **2026-08-12** (15,267 B). CDX for `EECS-2016-1.pdf`:
-  200s in 2017/2020/2021/2022.
-  `http://web.archive.org/web/20220425162607id_/…/EECS-2016-1.pdf` → **200, 959,927 B, PDF 1.4**.
-  `https://escholarship.org/search/?q=…` → **HTTP 202, 0 bytes**. [WEB]
-- **S43** `https://www.research-collection.ethz.ch/server/api/discover/search/objects?query=…` →
-  **HTTP 403, 1,337 B "Access Restricted"** (full text quoted in §5.5);
-  `…/server/oai/request?verb=Identify` → 200, `earliestDatestamp` 2017-05-15T06:24:06Z,
-  `deletedRecord=transient`; bogus verb → **200, 488 B** with an `<error>` element.
-  `https://api.datacite.org/dois?prefix=10.3929&query=…` → §9 entries 18–22. [WEB/API]
-- **S44** `https://repository.tudelft.nl/` — HTTP 200, 925,475 B. [WEB]
-- **S45** `https://lirias.kuleuven.be/` → 200 → `https://kuleuven.limo.libis.be/discovery/search?vid=32KUL_KUL:Lirias`,
-  4,784-byte Primo shell. [WEB]
-- **S46** `https://graz.elsevierpure.com/en/publications/?type=…` → 403, 6,102 B Cloudflare;
-  `https://diglib.tugraz.at/` → 200, 12,844 B; `/dissertationen` → 200, 10,815 B. [WEB]
-- **S47** `https://api.crossref.org/works?query.bibliographic=Software-based+microarchitectural+attacks+Gruss&rows=3`
-  → `10.1515/itit-2018-0034`, Gruss, *it - Information Technology*, 2018-11-20. [API]
-
-**Commercial routes (§6)**
-
-- **S48** `https://about.proquest.com/en/products-services/pqdtglobal/` — HTTP 200, 347,146 B;
-  *"over 6 million metadata records including 4 million full text documents"*, *"over 3,600
-  institutions from more than 70 countries"*. `https://pqdtopen.proquest.com/` → **302 →
-  `https://www.proquest.com/?defaultdiss=true`**; `https://www.proquest.com/pqdtglobal` → 302,
-  0 bytes. [DOC/WEB]
-- **S49** `https://www.ebsco.com/products/research-databases/ebsco-open-dissertations` → 301 →
-  `https://about.ebsco.com/…`, HTTP 200, 68,261 B; *"The free portal … 2,000,000 electronic theses
-  and dissertations; 325 worldwide universities"*. [DOC]
-
-**Landmark theses (§9) — additional**
-
-- **S50** `https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-574.html` — HTTP 200, 9,007 B.
-  *"Sketchpad: A man-machine graphical communication system · Ivan Edward Sutherland · September
-  2003, 149 pages · New preface by Alan Blackwell and Kerry Rodden. This technical report is based
-  on a dissertation submitted January 1963 by the author for the degree of Doctor of Philosophy to
-  the Massachusetts Institute of Technology. · DOI https://doi.org/10.48456/tr-574"*. [WEB]
-- **S51** `https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-630.html` — *"Semi-invasive attacks – A
-  new approach to hardware security analysis · Sergei P. Skorobogatov · April 2005, 144 pages ·
-  … dissertation submitted September 2004 … Doctor of Philosophy to the University of Cambridge,
-  Darwin College · DOI https://doi.org/10.48456/tr-630"*; `UCAM-CL-TR-630.pdf` → **HTTP 200,
-  11,754,717 B, `application/pdf`** — independently reproducing the figure in
-  [the companion record §3.5](government-and-institutional-technical-reports.md). [WEB]
-- **S52** `https://www.cs.helsinki.fi/u/kutvonen/index_files/linus.pdf` — **HTTP 200, 470,861 B,
-  `%PDF-1.3`**. Title page and Finnish/Swedish/English abstract form extracted from the PDF:
-  *"Linux: a Portable Operating System · Linus Torvalds · Helsinki, January 31, 1997 · Master of
-  Science Thesis · University of Helsinki, Department of Computer Science · Master of Science
-  thesis · January 1997 · 52 p. · Linux, Operating System, Portability, Alpha, Sparc"*.
-  Absence from Helda confirmed by two DSpace REST searches against
-  `https://helda.helsinki.fi/server/api/discover/search/objects` (queries
-  `"Linux portable operating system Torvalds"` → 3 hits, `"Torvalds"` → 77 hits; the thesis is in
-  neither). `https://helda.helsinki.fi/` itself → 200, 4,262 B, Anubis `1.23.0`. [WEB/API]
-- **S53** `https://api.datacite.org/dois?prefix=10.1184&query=DRAM AND dissertation` — CMU KiltHub
-  theses, §9 entries 23–24, including the concept/`.v1` DOI pair.
-  `https://api.figshare.com/v2/articles/search` POST with `institution:320` → HTTP 200 with a
-  2-byte body (`[]`) — the figshare institutional search returned nothing usable. [API]
-- **S54** `https://hdl.handle.net/api/handles/1721.1/11173` → `responseCode: 1` with the DSpace URL —
-  demonstrating the Handle oracle on a second prefix. [API]
diff --git a/research/preprint-repositories/vixra.md b/research/preprint-repositories/vixra.md
deleted file mode 100644
index 4daf6b2..0000000
--- a/research/preprint-repositories/vixra.md
+++ /dev/null
@@ -1,398 +0,0 @@
-# viXra — preprint repository record
-
-- **URL:** https://vixra.org/ · mirror: http://rxiv.org/ · AI-assisted sibling: http://ai.vixra.org ·
-  general sibling: https://rxiverse.org
-- **Operator:** **Scientific God Inc.**, a New York not-for-profit 501(c)(3) corporation. viXra's own
-  home page: *"As of October 1, 2019, viXra.org is owned and operated by Scientific God Inc."* (S1);
-  Scientific God Inc.'s own announcement of 13 October 2019 confirms the transfer effective
-  1 October 2019 and describes viXra as *"an ancillary project"* (S9). Founded July 2009 as a
-  UK-based non-profit *"run by unpaid individuals"* (S6). Funded by donations.
-- **Discipline scope:** advertised as all of *"Science, Mathematics & Other Scholarly Areas"* — in
-  practice ~60% physics, with the physics dominated by relativity/cosmology, quantum foundations and
-  "theories of everything" (§2, §3).
-- **Launched:** 2009 · **Status:** active, still accepting submissions (most recent listings
-  2026-08-31)
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **This record exists as a CONTROL CASE.** viXra is included here not because you should use it but
-> because it shows, concretely and measurably, what a preprint server with essentially no filter
-> looks like. Read it as a calibration point for the other records in this directory.
-> **Do not cite viXra as evidence for anything.** See §5.
-
-## 1. What it is
-
-viXra ("arXiv" backwards) was created in July 2009 by the British physicist **Philip Gibbs** as an
-explicit protest against arXiv's endorsement and moderation system. The founding argument is set out
-on viXra's own *Why viXra?* page and is worth reading in the original because it is a coherent
-position, not a crank manifesto (S3):
-
-> *"In 2004 [arXiv moderation] was replaced by a system of endorsements … However many of us who had
-> successfully submitted e-prints before then found that we were no longer able to. Even those with
-> doctorates in physics and long histories of publication in scientific journals can no longer
-> contribute to the arXiv unless they can find an endorser in a suitable research institution."*
-
-> *"Some of us now feel that the time has come to start an alternative archive which will be open to
-> the whole scientific community. That is why viXra has been created. viXra will be open to anybody
-> for both reading and submitting articles. **We will not prevent anybody from submitting and will
-> only reject articles in extreme cases of abuse, e.g. where the work may be vulgar, libellous,
-> plagiaristic or dangerously misleading.**"*
-
-And, critically, the founders said in advance what the consequence would be:
-
-> *"It is inevitable that viXra will therefore contain e-prints that many scientists will consider
-> clearly wrong and unscientific. However, it will also be a repository for new ideas that the
-> scientific establishment is not currently willing to consider."* (S3)
-
-That is the whole design. Everything in §5 follows from it.
-
-## 2. Scope and subject taxonomy — including the computing categories
-
-viXra uses seven broad groups and 38 categories, each with a short slug URL (`vixra.org/<slug>`).
-Counts below are the **per-category totals published on viXra's own front page**, retrieved
-2026-09-01 (S1). This is unusually good disclosure — few servers expose per-category counts this
-plainly.
-
-**Physics (26,503)** — `hep` High Energy Particle Physics 2,198 · `qgst` Quantum Gravity and String
-Theory 2,299 · `relcos` Relativity and Cosmology 5,398 · `astro` Astrophysics 3,102 · `quant`
-Quantum Physics 5,271 · `nucl` Nuclear and Atomic Physics 927 · `condmt` Condensed Matter 1,635 ·
-`therm` Thermodynamics and Energy 472 · `class` Classical Physics 2,383 · `geop` Geophysics 360 ·
-`clim` Climate Research 162 · `mathph` Mathematical Physics 1,659 · `histph` History and Philosophy
-of Physics 637
-
-**Mathematics (10,281)** — `setlog` Set Theory and Logic 363 · `numth` Number Theory 3,720 ·
-`combgt` Combinatorics and Graph Theory 281 · `alg` Algebra 549 · `geom` Geometry 658 · `top`
-Topology 198 · `anal` Functions and Analysis 680 · `stat` Statistics 379 · `math` General
-Mathematics 3,453
-
-**Computational Science (2,740)** — the categories this repository cares about:
-
-| Category | Slug | Count | viXra's own scope note |
-|---|---|---|---|
-| **Digital Signal Processing** | `dsp` | **547** | *"including cryptography"* |
-| **Data Structures and Algorithms** | `dsalg` | **500** | *"including software generation"* |
-| **Artificial Intelligence** | `ai` | **1,693** | *"including Computational Linguistics"* |
-
-There is **no hardware, electronics, networking, operating-systems, database or security category**.
-Cryptography is folded into DSP; anything software-ish lands in `dsalg`.
-
-**Biology (2,615)** — `bioch` 475 · `phbio` 1,493 · `mind` 406 · `qbio` 241
-**Chemistry (436)** — `chem` 436
-**Humanities (1,823)** — `arch` 77 · `ling` 275 · `econ` 401 · `soc` 768 · `reli` Religion and
-Spiritualism 302 *"including mythology"*
-**Academics (1,653)** — `edu` 262 · `sci` General Science and Philosophy 1,391
-
-**Note the taxonomy itself.** A repository with a *Religion and Spiritualism* category sitting beside
-*Data Structures and Algorithms*, operated by an organisation called Scientific God Inc., is telling
-you what it is. That is not a gotcha — it is consistent with the stated mission (S6).
-
-## 3. Size and growth
-
-| Measure | Value | Source |
-|---|---|---|
-| **Total e-prints (operator counter)** | **46,051** | vixra.org front page, 2026-09-01 [WEB] (S1) |
-| Works in OpenAlex source S2883122597 | 23,704 (12,172 citations) | OpenAlex [API] (S10) |
-| Crossref DOIs | **none — viXra does not mint DOIs** | [INF] from §8 |
-| ai.viXra.org (AI-assisted sibling, launched March 2025) | 1,815 | ai.vixra.org front page [WEB] (S7) |
-| rxiVerse (sibling, launched July 2025) | 827 | rxiverse.org front page [WEB] (S8) |
-| Not listed in Wikipedia's *List of preprint repositories* | — | [COM] (S11) |
-
-**Conflicts, recorded.** OpenAlex holds 23,704 viXra works — about half the operator's count — and
-its per-year figures show OpenAlex effectively **stopped ingesting viXra after 2021**: 2015 2,128 ·
-2016 2,575 · 2017 2,779 · 2018 3,112 · 2019 3,071 · 2020 2,394 · **2021 1,446 · 2022 6 · 2023 8 ·
-2024 16 · 2025 7 · 2026 22** (S10). OpenAlex does not explain the cut-off [NOT-VERIFIED as to
-cause], but the effect is that viXra content has been largely **de-indexed from the main open
-bibliographic infrastructure** since 2022. That is itself a strong signal about how the scholarly
-record treats this server [INF].
-
-viXra also does not appear in Wikipedia's *List of preprint repositories* at all (S11), despite
-having its own Wikipedia article — another indication of how it is categorised by the community.
-
-**Per-category monthly histories** are published on each category page. `dsalg` shows a long thin
-stream: 1 submission in its first month (2009-08), a spike of 25 in 2014-05, and 1–11 per month
-since; `dsp` shows 69 in 2012-08 and 42 in 2014-05 against a baseline of 1–15 (S12). These are
-**tiny** categories — a few hundred documents accumulated over 17 years.
-
-Versions: authors may replace a paper **up to four times**; further replacements require *"a good and
-exceptional reason"*. Earlier versions are normally retained (S4).
-
-## 4. Screening and moderation — what gets in
-
-**There is no endorsement requirement, no affiliation requirement, no peer review, and no assessment
-of correctness.** The operator says so repeatedly and unambiguously. From the *Info* page (S6):
-
-> *"All scholarly papers in science, mathematics & other scholarly areas will be accepted. …
-> Submissions are subject to screening for conformity with the guidelines of viXra.org and adherence
-> to scholarly norms. Submissions may be rejected or withdrawn for being in the wrong format, not
-> scholarly, or because of legal risks/concerns (e.g., threats, defamation, copyright violations or
-> obscenities), **but they are not reviewed or rejected according to the correctness of the work.
-> Because of this policy, viXra may contains some work of low value or usefulness.**"*
-
-From the *Good practice* page (S5):
-
-> *"viXra is a repository, not a journal so we do not review papers or give feedback. … Unlike
-> journals, submissions to viXra are not reviewed or rejected according to the correctness of the
-> work. … **This means that acceptance in viXra may not confer scientific credibility, or the lack of
-> it, to your work or anyone else's.**"*
-
-**What the gate actually consists of**, from the submission and good-practice pages (S4, S5, S6):
-
-1. Format: PDF only, with title, full author name, abstract and body. No video, no source code, no
-   Word/PowerPoint/LaTeX (may be rejected or converted).
-2. Scholarly form: laid out as a scientific paper.
-3. Legal: no plagiarism, defamation, obscenity, or **journal-formatted PDFs** — viXra *"sometimes
-   proactively removes versions of documents that appear to show journal formatting"* to avoid
-   take-down notices (S4).
-4. No duplicate/near-duplicate resubmission (treated as replacements).
-5. **AI-assisted work is routed elsewhere.** Since ~2025 the front page states: *"viXra.org only
-   accepts scholarly articles written without AI assistance. Please go to ai.viXra.org to submit new
-   scholarly article written with AI assistance or rxiVerse.org."* (S1) In practice viXra admins
-   append a note to suspected records — e.g. `viXra:2604.0057` carries *"(Note by viXra Admin: Please
-   submit article written with AI assistance to ai.viXra.org)"* (S13). This is a real, if crude,
-   provenance signal, and it is more than most servers do.
-
-Every abstract page carries a standing disclaimer (S13):
-
-> *"Vixra.org is a pre-print repository rather than a journal. Articles hosted may not yet have been
-> verified by peer-review and should be treated as preliminary. In particular, anything that appears
-> to include financial or legal advice or proposed medical treatments should be treated with due
-> caution."*
-
-Comment moderation is enforced with an unusual rule: *"If you are being critical you must mention at
-least one specific error, otherwise your comment will be deleted as unhelpful."* (S13)
-
-## 5. Reliability — a blunt assessment
-
-**A viXra deposit guarantees exactly three things: a timestamp, a stable URL, and a PDF that is
-formatted like a paper.** It guarantees nothing about correctness, novelty, competence, or the
-author's identity or existence. The operator states this himself in four separate places (§4).
-
-**Do not cite viXra as evidence for anything.** Not as evidence a result is true, not as evidence a
-result is novel, not as evidence a technique works. If a viXra paper contains something you need,
-independently reproduce or verify the underlying claim and cite the verification. The only legitimate
-citation of a viXra record is as a **priority timestamp** (this idea was public on this date) or as an
-**object of study** (e.g. research about fringe science).
-
-### How it is treated in the literature and the press
-
-- **Nature News Blog** covered the launch in July 2009 under the headline *"What's arXiv spelled
-  backwards? A new place to publish"*, and characterised viXra as accepting submissions *"without
-  requiring authors to have an academic affiliation and without any threshold for quality"* (S14,
-  cited via S2).
-- **Collins, Bartlett & Reyes-Galindo, "Demarcating Fringe Science for Policy", *Perspectives on
-  Science* 25(4):411–438 (2017), doi 10.1162/POSC_a_00248** — the standard science-studies treatment
-  that uses viXra as a case in the demarcation problem (S15). 35 citations in OpenAlex.
-- **Delfanti A., "Fake archives: The search for openness in scholarly communication platforms",
-  ch. 20 in Biagioli & Lippman (eds), *Gaming the Metrics: Misconduct and Manipulation in Academic
-  Research*, MIT Press 2020, pp. 261–269** (S16, cited via S2) — note the chapter title.
-- **Yudhoatmojo S., De Cristofaro E., Blackburn J., "Understanding the Use of e-Prints on Reddit and
-  4chan's Politically Incorrect Board", *Proceedings of the 15th ACM Web Science Conference 2023*,
-  doi 10.1145/3578503.3583627** (S17) — a peer-reviewed CS-venue study of how arXiv and **viXra**
-  e-prints circulate on Reddit and 4chan's /pol/. This is the most directly relevant scientometric
-  work for a computing audience.
-- Wikipedia's lead sentence, sourced to Collins et al. and two other refs, is: *"viXra is an
-  electronic e-print archive known for unorthodox and fringe science."* (S2)
-
-That is the settled perception: viXra is used in the literature as a **byword** for unfiltered
-content, and it is the archive's own stated design that makes that fair.
-
-### The minority of legitimate work — and it does exist
-
-Being fair matters here. A real fraction of viXra content is ordinary, competent work by people
-outside the endorsement system, or archival deposits of old material. Verified examples from the
-computing categories (S12, S18):
-
-- **`viXra:2607.0056` — "Inverse of the Square Wave Matrix"**, David J. Grabiner, Warren D. Smith,
-  Sushanta Srivastava. The author comment reads: *"Based on At&T Bell Labs tech report we wrote in
-  1989, now uploaded to VIXRA for archival purposes."* The abstract describes an O(N log N)
-  signal↔square-wave transform analogous to the FFT. This is a genuine Bell Labs technical report
-  being archived by its authors. **Warren D. Smith is a real computer scientist.** PDF verified: 84,174
-  bytes, `%PDF-` magic bytes (S18).
-- **`viXra:2607.0099` — "Linear-Time Algorithms to Color Topological Graphs"**, Warren D. Smith.
-- **`viXra:2604.0005` — "Some Variations of the Secretary Problem"**, Sarthak Agrawal, Sanjeev Saxena.
-- **`viXra:2601.0110` — "Synthetic Aperture Radar Point Target Response"**, Sasan Ardalan (26 pp);
-  and `viXra:2512.0073` — "…Singular Value Decomposition (SVD) with Fixed Point CORDIC Operations
-  with Application to MIMO-OFDM", same author (33 pp). Real DSP engineering.
-- **`viXra:2601.0124` — "Notes on Automata Processing"**, Michael Leventhal, 306 pages.
-
-**And the rest.** The same `dsp` listing also contains, from a single author, a sequence titled *"New
-Wireless Technology not Covered by the Existing Ieee Standards of 2017"*, *"New Wireless Technology
-for Data Transmission in Chemical Systems"* and *"The Use of Chemical System as Transmission Medium
-in Wireless Data Communication Channel"* — 3–5 pages each. The `dsalg` listing includes *"Physical
-OS: Genetic-Resilient Deterministic Phase-Coherence for Secure DTx and AGI Humanoid Safety
-Interlocks"* and AI-flagged submissions (S12). Quantum-molecular-dynamics papers sit in the
-*Data Structures and Algorithms* category.
-
-**Honest summary of the computing categories.** ~2,740 documents across DSP, algorithms and AI,
-accumulated over 17 years. Perhaps a low-single-digit percentage is archival or competent
-independent work — the Smith/Grabiner and Ardalan items are real. The remainder ranges from
-undergraduate-project quality to word-salad. There is **no** hardware, systems, networking or
-database content of any kind. **The signal-to-noise ratio makes this useless as a search target for a
-practising engineer**, and the sheer smallness of the categories means you would find nothing here
-you could not find better elsewhere.
-
-### How to sanity-check a viXra item (if you must)
-
-1. Look up the author independently — DBLP, Google Scholar, ORCID, an institutional page. The
-   Bell Labs example above passes; most do not.
-2. Check whether the same work exists on arXiv, in a journal, or in a conference proceedings. If it
-   does, cite *that*.
-3. Check for the admin AI-assistance note in the Comments field.
-4. Check the version count and the author's total submission count in the category.
-5. **Then verify the actual claim from first principles.** There is no editorial filter standing
-   between you and an error.
-
-## 6. Landmark papers
-
-**None.** viXra hosts no landmark work in any field, and specifically none in software, distributed
-systems, databases, electronics or security. The most notable computing item is a 1989 AT&T Bell Labs
-technical report deposited for archival purposes 37 years later (§5) — notable as provenance, not as
-a landmark.
-
-## 7. Access, APIs and bulk retrieval
-
-- **No API. No OAI-PMH. No DOIs. No bulk dump.** viXra does not mint DOIs (nothing in Crossref) and
-  advertises no machine interface.
-- **RSS:** `http://viXra.org/feed/rss.xml` — HTTP 200, `application/xml`, 89,393 bytes, valid RSS
-  2.0 with `<category>` per item. This is the only structured feed (S19).
-- **Stable URL patterns** (all verified 2026-09-01, S18):
-  - abstract page: `https://vixra.org/abs/YYMM.NNNN`
-  - PDF: `https://vixra.org/pdf/YYMM.NNNNvV.pdf`
-  - category listing: `https://vixra.org/<slug>` (e.g. `/dsalg`, `/dsp`, `/ai`)
-  - policy pages: `/why`, `/submit`, `/practices`, `/info.html`, `/access`, `/faq.html`
-- **Mirror:** `http://rxiv.org/` returns a byte-identical 10,486-byte home page (S20).
-- **Submission is by web form only** (`fs23.formsite.com/viXra/form2/`); e-mail submission is
-  explicitly no longer accepted (S4).
-- **No user-agent gating and no rate limiting observed** — default `curl` returned HTTP 200
-  throughout (S18).
-- The `/access` page states flatly: *"We regret that we cannot make copies of papers available in any
-  other shape or form. Nor can we send them to you in any other way including e-mail, FTP or the
-  post."* (S21)
-
-### Negative controls (2026-09-01) (S18)
-
-| Probe | Result | Interpretation |
-|---|---|---|
-| `/abs/9999.0001` | **HTTP 404**, 746 B, `text/html` | Correct hard 404. |
-| `/pdf/9999.0001v1.pdf` | **HTTP 404**, 746 B, `text/html` | Correct hard 404 — no fake PDF. |
-| `/nosuchcategory` | **HTTP 404**, 746 B | Correct hard 404. |
-| `/abs/2607.0056` (valid) | HTTP 200, 7,100 B | Real record. |
-| `/pdf/2607.0056v1.pdf` (valid) | HTTP 200, **84,174 B**, `%PDF-` magic bytes | Real PDF, verified by magic bytes not status code. |
-
-**viXra's HTTP behaviour is, ironically, the most honest of the five platforms in this cluster** —
-static hosting, real 404s, no soft failures, no bot walls. Preprints.org and Research Square both
-return HTTP 200 for non-existent records.
-
-## 8. Licensing and reuse
-
-- **No licence is applied.** viXra states no CC licence, no author licence grant, and no reuse terms
-  on any page retrieved. Authors are simply responsible for their content: *"It is the authors'
-  responsibility to ensure that they only upload content they have the legal right to share"* is the
-  posture, and viXra "sometimes proactively removes" journal-formatted PDFs to avoid take-down
-  notices (S4). [NOT-VERIFIED that any licence statement exists anywhere on the site.]
-- **Practical consequence: default all-rights-reserved.** You cannot assume any right to
-  redistribute, mine or reuse viXra content. This is materially worse than every other server in
-  this cluster, all of which apply CC BY 4.0.
-- **No preservation arrangement.** No Portico, CLOCKSS or LOCKSS statement exists on any page
-  retrieved [NOT-VERIFIED]. The only redundancy is the `rxiv.org` mirror (S20), which is
-  same-operator and therefore not an independent archive.
-- **Durability risk: high.** A single small US non-profit, donation-funded, no DOIs, no dark archive,
-  no licence permitting third-party mirroring. If Scientific God Inc. stops paying the hosting bill,
-  46,051 documents disappear and nothing at Crossref or Portico points at them.
-
-## 9. Caveats and controversies
-
-1. **The Wikipedia "Scientific God Inc." provider claim is ACCURATE — verified against two primary
-   sources.** Wikipedia's infobox lists `owner = Scientific God Inc.` (S2). viXra's own front page
-   states: *"As of October 1, 2019, viXra.org is owned and operated by Scientific God Inc."* (S1).
-   Scientific God Inc.'s own site carries a post dated 13 October 2019, *"viXra.org Is Now an
-   Ancillary Project of Scientific God Inc."*, explaining that *"With EU legislation such as GDPR and
-   upload filters becoming more restrictive, it was decided in 2019 to move viXra under the umbrella
-   of a US-based non-profit organisation. Its ownership and operation was therefore transferred
-   effective October 1, 2019 to Scientific God Inc."* SGI describes itself as *"a New York
-   not-for-profit corporation with 501(c)(3) tax[-exempt status]"* (S9). Note that SGI is not a
-   general-purpose scientific charity: its own navigation lists *Journal*, *SG Prize*, *Sciurch*,
-   *Gcience*, *Scibible*, *Institute* — it publishes the *Scientific GOD Journal*, which viXra
-   advertises on its front page (S1, S9).
-2. **The founding grievance is worth taking seriously even if the archive is not.** arXiv's
-   endorsement system does exclude unaffiliated researchers, and viXra's *Why viXra?* page makes that
-   case with specifics (S3). The critique is legitimate; the remedy — removing the filter entirely —
-   produced exactly the corpus its founders predicted it would (§1).
-3. **AI content is now segregated but the boundary is porous.** viXra routes AI-assisted work to
-   ai.viXra.org (1,815 e-prints) and rxiVerse (827), but detection is manual admin annotation, and
-   AI-flagged items remain visible in viXra's own listings pending author action (S1, S7, S8, S13).
-4. **OpenAlex has effectively de-indexed viXra since 2022** (§3). Whatever the reason, it means
-   citation-graph tools will not see this content.
-5. **viXra maintains a public list of journals that asked authors to remove papers from viXra**, with
-   the advice *"You should therefore avoid these at all costs"* (S4). Treat that list as advocacy,
-   not as an assessment of those journals.
-6. **No licence, no DOIs, no dark archive** (§8). Anything you need from here should be saved
-   locally, and if it is genuinely scarce, submitted to `web.archive.org/save/`.
-
-## 10. Sources
-
-- **S1** — https://vixra.org/ · retrieved 2026-09-01 [WEB] · total 46,051; all 38 per-category
-  counts quoted in §2; Scientific God Inc. ownership statement; AI-routing notice to ai.viXra.org and
-  rxiVerse.org; mirror `rxiv.org`; *Scientific GOD Inc.* advertisement banner.
-- **S2** — https://en.wikipedia.org/wiki/ViXra (wikitext via MediaWiki API) · retrieved 2026-09-01
-  [COM] · infobox `owner = Scientific God Inc.`, `founder = Philip Gibbs`, `launch_date = 2009`;
-  lead sentence "known for unorthodox and fringe science"; seven-category description; references to
-  Collins et al. 2017, the Nature News Blog piece and Delfanti 2020.
-- **S3** — https://vixra.org/why · retrieved 2026-09-01 [DOC] · the founding argument against arXiv
-  endorsement, and the "we will not prevent anybody from submitting" / "it is inevitable that viXra
-  will contain e-prints that many scientists will consider clearly wrong" passages quoted in §1.
-- **S4** — https://vixra.org/submit · retrieved 2026-09-01 [DOC] · PDF-only requirement, required
-  metadata, four-replacement limit, journal-formatting removal policy, withdrawal form, no e-mail
-  submission, list of journals that requested removals.
-- **S5** — https://vixra.org/practices · retrieved 2026-09-01 [DOC] · "viXra is a repository, not a
-  journal so we do not review papers"; "acceptance in viXra may not confer scientific credibility";
-  no source code / video / file-sharing; replacement discipline.
-- **S6** — https://vixra.org/info.html · retrieved 2026-09-01 [DOC] · founding rationale, 2009
-  founding date, "All scholarly papers … will be accepted", the "not reviewed or rejected according
-  to the correctness of the work … viXra may contains some work of low value or usefulness" passage.
-- **S7** — http://ai.vixra.org · retrieved 2026-09-01 [WEB] · *"launched here in March, 2025 &
-  accepts AI assisted scholarly articles"*; 1,815 e-prints; computational-science counts DSP 7,
-  Data Structures and Algorithms 30, AI 120.
-- **S8** — https://rxiverse.org · retrieved 2026-09-01 [WEB] · *"launched here in July, 2025"*;
-  827 e-prints; same category structure; operated by Scientific God Inc.
-- **S9** — https://scigod.org · retrieved 2026-09-01 [DOC] · post of 13 October 2019, *"viXra.org Is
-  Now an Ancillary Project of Scientific God Inc."*, with the GDPR rationale and the effective date
-  of 1 October 2019; "Scientific GOD, Inc. ('SGI') is a New York not-for-profit corporation with
-  501(c)(3) tax[-exempt status]"; site navigation listing Journal / viXra / SG Prize / Sciurch /
-  Gcience / Scibible / Institute.
-- **S10** — https://api.openalex.org/sources/S2883122597 · retrieved 2026-09-01 [API] · 23,704 works,
-  12,172 citations, homepage `http://vixra.org/`; counts_by_year showing the post-2021 collapse
-  quoted in §3.
-- **S11** — https://en.wikipedia.org/wiki/List_of_preprint_repositories (wikitext via MediaWiki API)
-  · retrieved 2026-09-01 [COM] · **viXra is absent from the table** (string `[[viXra]]` not found).
-- **S12** — https://vixra.org/dsalg and https://vixra.org/dsp · retrieved 2026-09-01 [WEB] ·
-  per-month submission histories 2009–2026; 173 and 52 records parsed from the listing pages
-  respectively; the titles and authors quoted in §5.
-- **S13** — https://vixra.org/abs/2604.0057 and https://vixra.org/abs/2607.0056 · retrieved
-  2026-09-01 [WEB/DOC] · the admin AI-assistance note; the standing per-paper disclaimer quoted in
-  §4; the comment-moderation rule; unique-IP download counter.
-- **S14** — "What's arXiv spelled backwards? A new place to publish", *Nature News Blog*,
-  16 July 2009 · https://web.archive.org/web/20111201185937/http://blogs.nature.com/news/2009/07/whats_arxiv_spelled_backwards.html
-  · cited via S2 [COM, secondary — the archived URL was not independently fetched in this pass].
-- **S15** — Collins H., Bartlett A., Reyes-Galindo L., "Demarcating Fringe Science for Policy",
-  *Perspectives on Science* 25(4):411–438, July–August 2017 · https://doi.org/10.1162/posc_a_00248 ·
-  Crossref and OpenAlex metadata retrieved 2026-09-01 [LIT] · 35 citations in OpenAlex.
-- **S16** — Delfanti A., "Fake archives: The search for openness in scholarly communication
-  platforms", in Biagioli M. & Lippman A. (eds), *Gaming the Metrics: Misconduct and Manipulation in
-  Academic Research*, MIT Press, 2020, ch. 20, pp. 261–269, ISBN 978-0-262-53793-3 · cited via S2
-  [LIT, secondary — bibliographic record not independently retrieved].
-- **S17** — Yudhoatmojo S., De Cristofaro E., Blackburn J., "Understanding the Use of e-Prints on
-  Reddit and 4chan's Politically Incorrect Board", *Proceedings of the 15th ACM Web Science
-  Conference 2023* · https://doi.org/10.1145/3578503.3583627 · Crossref metadata retrieved
-  2026-09-01 [LIT] · preprint version at arXiv:2111.02455.
-- **S18** — direct probes of vixra.org, 2026-09-01 [WEB] · negative controls `/abs/9999.0001`,
-  `/pdf/9999.0001v1.pdf`, `/nosuchcategory` → HTTP 404, 746 B; positive controls `/abs/2607.0056`
-  → 200/7,100 B and `/pdf/2607.0056v1.pdf` → 200/84,174 B with `%PDF-` magic bytes.
-- **S19** — http://viXra.org/feed/rss.xml · retrieved 2026-09-01 [WEB] · HTTP 200,
-  `application/xml`, 89,393 bytes; `lastBuildDate Mon Aug 31 18:37:27 EDT 2026`; per-item
-  `<category>` element.
-- **S20** — http://rxiv.org/ · probed 2026-09-01 [WEB] · HTTP 200, 10,486 bytes — byte-identical in
-  size to the viXra home page; same-operator mirror.
-- **S21** — https://vixra.org/access · retrieved 2026-09-01 [DOC] · PDF-only distribution; no
-  alternative delivery channels; no login required.
diff --git a/research/preprint-repositories/zenodo.md b/research/preprint-repositories/zenodo.md
deleted file mode 100644
index b7a457f..0000000
--- a/research/preprint-repositories/zenodo.md
+++ /dev/null
@@ -1,697 +0,0 @@
-# Zenodo — preprint repository record
-
-- **URL:** https://zenodo.org/
-- **Operator:** CERN (European Organization for Nuclear Research), originating from the
-  OpenAIRE programme funded by the European Commission. Runs on CERN Data Centre
-  infrastructure; software stack is InvenioRDM.
-- **Discipline scope:** advertised as "All fields of research. All types of research
-  artifacts" (S3) — *as actually used*, the corpus is dominated by bulk-ingested
-  biodiversity/taxonomic literature and figures, with a substantial but minority
-  research-software and dataset population (§3).
-- **Launched:** **May 2013** (operator's own statement, S2) · **Status:** active
-- **Compiled:** 2026-09-01
-- **Evidence labels:** [API] [WEB] [DOC] [LIT] [COM] [INF] [NOT-VERIFIED] — see the
-  [index](README.md#evidence-and-method).
-
-> **Launch-year conflict — resolved, see §10.1.** Wikipedia's *List of preprint
-> repositories* gives Zenodo's year as **2011**; Zenodo's own About page and Wikipedia's
-> *own Zenodo article* both give **May 2013**. Both figures are recorded below with
-> sources; the 2011 date appears to refer to the predecessor service, not Zenodo.
-
-## 1. What it is
-
-Zenodo is a **catch-all repository**. It exists to give a citable, persistent home to any
-research output that has nowhere else to go — and, critically for this knowledge base, to
-outputs that are *not papers*: source code, firmware images, datasets, KiCad projects,
-simulation inputs, conference artifact packages, slide decks, lesson material.
-
-Its origin is a policy problem rather than a scholarly one. The European Commission
-required that EC-funded research be deposited openly, but many researchers had no
-institutional or subject repository that would take their material. OpenAIRE was tasked
-with providing a "catch-all" and CERN supplied the capability (S2). Zenodo is therefore
-designed around the removal of barriers: "Zenodo does not impose any requirements on
-format, size, access restrictions or licence. Quite literally we wish there to be no
-reason for researchers not to share!" (S2) [DOC]
-
-That design choice is the single most important fact about Zenodo, and it cuts both ways.
-It is why a firmware release or a board design can get a DOI in ninety seconds; it is also
-why **a Zenodo DOI carries no scholarly warrant whatsoever** (§5).
-
-For a hardware or software engineer, Zenodo matters mainly for one mechanism: the **GitHub
-integration** (§6), which turns a git tag into an archived, DOI-bearing, citable software
-release. This is the dominant route by which open-source research software becomes
-formally citable, and it is worth understanding precisely.
-
-Zenodo is *not* primarily a preprint server, despite being listed as one. Preprints are
-about 3.4% of its records (§3). Calling it a preprint repository is a category error that
-the Wikipedia list propagates.
-
-## 2. Scope and subject taxonomy
-
-Zenodo does not use a discipline taxonomy like arXiv's `cs.DC`. It has no subject
-categories that gate deposit. Instead it has:
-
-**(a) Resource types** — a controlled vocabulary, the real structural axis. Retrieved from
-the `resource_type` aggregation of the search API, 2026-09-01 (S1) [API]:
-
-| Resource type | Records (latest version) |
-|---|---|
-| publication | 4,760,348 |
-| image | 1,229,242 |
-| dataset | 687,267 |
-| software | 284,518 |
-| presentation | 92,470 |
-| other | 65,300 |
-| poster | 38,299 |
-| video | 21,932 |
-| lesson | 17,638 |
-| model | 16,819 |
-
-Publication subtypes (same query, S1) [API]:
-
-| Subtype | Records |
-|---|---|
-| publication-article | 2,462,351 |
-| publication-taxonomictreatment | 714,681 |
-| **publication-preprint** | **242,779** |
-| publication-conferencepaper | 240,109 |
-| publication-book | 184,941 |
-| publication-section | 151,673 |
-| publication-other | 120,480 |
-| publication-report | 91,590 |
-| publication-journal | 55,387 |
-| publication-deliverable | 39,461 |
-
-Subtypes retrieved individually (S1) [API]: `datamanagementplan` 1,636 ·
-`softwaredocumentation` 3,958 · `technicalnote` 18,847 · `workingpaper` 36,307 ·
-`patent` 3,119. Software has one subtype: `software-computationalnotebook` 8,119.
-
-> **Facet-name trap.** Querying `&type=publication&subtype=thesis` returns
-> `{"hits":{"total":0}}` with **HTTP 200**. So does `&type=notarealtype123`. An invalid
-> facet value is *indistinguishable from a genuine zero* (§8, negative controls). `thesis`
-> is simply not in Zenodo's vocabulary — the aggregation above is the authoritative list.
-> Do not infer "there are no theses on Zenodo" from that zero. [API]
-
-**(b) Communities** — see §6.3. Self-service, curator-run collections. 42,971 exist
-(S1, 2026-09-01) [API]. They are the closest thing Zenodo has to subject structure, and
-they are weak (§6.3).
-
-**(c) Free-text keywords** — uncontrolled. The `subject` aggregation is dominated by
-`Biodiversity` (2,161,233), `Taxonomy` (1,825,897), `Animalia` (1,240,408), `Arthropoda`
-(918,857), `Insecta` (664,605), and `BHL-Corpus` / `Source: Biodiversity Heritage Library`
-(310,066 each) (S1) [API].
-
-## 3. Size and growth
-
-**Headline (S1, retrieved 2026-09-01) [API]:**
-
-- **7,231,589** records, latest-version only (`/api/records/?size=1`).
-- A second identical call minutes later returned **7,231,598** — the corpus grows by
-  roughly ten records per minute during a working day. Treat any single figure as a
-  snapshot, not a constant.
-- **8,242,934** records counted with `allversions=true`.
-
-The gap between those last two numbers is the versioning model made visible: about
-1.01 million records are superseded prior versions.
-
-**Versions per type — the software signal** (S1) [API]:
-
-| Type | Latest-version | All versions | Versions per work |
-|---|---|---|---|
-| software | 284,518 | 712,318 | ≈2.50 |
-| publication/preprint | 242,779 | 357,701 | ≈1.47 |
-| all records | 7,231,598 | 8,242,934 | ≈1.14 |
-
-Software carries **2.5 versions per work** against a corpus average of 1.14. That ratio is
-direct evidence of the GitHub release integration doing its job: each tagged release
-produces a new version record under a shared concept DOI (§6.1).
-
-**Access status** (S1) [API]: open 6,976,693 (96.5%) · restricted 243,832 · embargoed
-11,071 · metadata-only 2.
-
-**File types** (S1) [API]: pdf 3,846,843 · png 767,864 · html 765,134 · jpg 556,380 ·
-**zip 487,961** · txt 188,831 · docx 120,760 · json 107,229 · xlsx 106,637 · csv 98,627.
-The zip count is the practical proxy for "packaged code or data".
-
-**Growth by publication year** (S1) [API]. Note this is the *metadata* publication date,
-which for bulk-ingested legacy literature is the original publication year, not the
-deposit date — so early years are retrospective ingest, not 2013 activity:
-
-| Year | Records | | Year | Records |
-|---|---|---|---|---|
-| 2011 | 74,334 | | 2019 | **503,221** |
-| 2013 | 99,825 | | 2020 | 276,649 |
-| 2015 | 127,316 | | 2022 | 396,082 |
-| 2017 | 193,863 | | 2024 | 660,197 |
-| 2018 | 222,575 | | 2025 | 936,029 |
-| | | | 2026 | **1,228,268** |
-
-Two anomalies worth flagging [INF]: the **2019 spike** (503,221, more than double 2018 and
-well above 2020) and the **2026 figure of 1,228,268** — already the largest year on record
-on 2026-09-01, i.e. two-thirds through the year. Both are consistent with bulk machine
-deposit rather than organic growth. The subject aggregation (§2c) points to the likely
-source: biodiversity/taxonomic pipelines. `publication-taxonomictreatment` alone is
-714,681 records — **nearly three times the entire preprint corpus**.
-
-**What this means:** Zenodo's headline "7.2 million" is not 7.2 million research papers.
-It is dominated by figures (1.23M images) and bulk taxonomic literature. Anyone quoting
-Zenodo's size as evidence of scholarly scale is misreading it. [INF]
-
-**Conflict with Wikipedia:** the *List of preprint repositories* records Zenodo's size as
-**">100,000"** (S7). Against 242,779 preprint records — or 7.23M total — that entry is
-stale by more than an order of magnitude on either reading. [API] vs [WEB]
-
-## 4. Screening and moderation — what gets in
-
-**The gate is: registration, and nothing else.**
-
-From Zenodo's General Policies v1.0 (S3) [DOC], quoted:
-
-> **Eligible depositors:** "Anyone may register as user of Zenodo. All users are allowed to
-> deposit content for which they possess the appropriate rights."
-
-> **Status of research data:** "Any status is accepted, from any stage of the research
-> lifecycle."
-
-> **Data quality:** "All information is provided 'as-is', and the user shall hold Zenodo
-> and information providers supplying data to Zenodo free and harmless in connection with
-> the use of such information."
-
-There is **no peer review, no editorial board, no subject-matter screening, no endorsement
-requirement, and no affiliation requirement.** There is no moderation queue. Content is
-live and has a DOI immediately on publish.
-
-Moderation is **reactive and post-hoc**, on a revocation model (S3) [DOC]:
-
-> **Revocation:** "Content not considered to fall under the scope of the repository will be
-> removed and associated DOIs issued by Zenodo revoked. Please signal promptly, ideally no
-> later than 24 hours from upload, any suspected policy violation. Alternatively, content
-> found to already have an external DOI will have the Zenodo DOI invalidated and the record
-> updated to indicate the original external DOI."
-
-Constraints that do exist: files must not "violate privacy or copyright, or breach
-confidentiality or non-disclosure agreements"; a licence must be specified for all publicly
-available files; total file size per record is capped at **50 GB**, with higher quotas
-case-by-case (S3) [DOC].
-
-## 5. Reliability — what you can and cannot trust
-
-### 5.1 What a Zenodo DOI *does* mean
-
-- **A timestamp.** The record existed in this form at this datetime.
-- **A fixity guarantee.** "All data files are stored along with a MD5 checksum of the file
-  content. Files are regularly checked against their checksums" (S3) [DOC].
-- **Bit preservation with replication.** "All data files are stored in CERN Data Centres,
-  primarily Geneva, with replicas in Budapest… backed up to tape on a nightly basis" (S3).
-- **Immutability of a version.** A version DOI points at files that cannot change.
-- **DataCite registration**, so the metadata propagates to aggregators (S6) [DOC].
-
-### 5.2 What a Zenodo DOI does **not** mean
-
-- **Not peer review.** Nothing was refereed.
-- **Not a correctness, novelty or originality check.** Nothing was read.
-- **Not a plagiarism scan.** None is performed or claimed.
-- **Not authorship verification.** Nobody checked that the depositor is the author, or that
-  they hold the rights they assert.
-- **Not scope screening.** "All fields of research" is enforced only reactively.
-- **Not a guarantee the software runs.** Explicitly disclaimed: "Zenodo makes no promises
-  of usability and understandability of deposited objects over time" (S3) [DOC].
-
-A concrete illustration of how low the bar is: a record titled *"This is an example of an
-interactive Carto graph in Authorea"* exists with a registered DOI on a *different*
-platform (§ see `authorea.md`), and the equivalent is trivially true here. A DOI is a
-plumbing fact, not a quality signal.
-
-### 5.3 No SLA — by stated design
-
-Zenodo's Principles page (S4) [DOC]:
-
-> "Zenodo does not sign SLAs (service-level agreements). This is not a weakness, it is by
-> design and marks a philosophy that we believe is most appropriate for Science… Service
-> failure can never be undone. Enforcing an SLA means being prepared to litigate against
-> the contract."
-
-Read that honestly: you have **no contractual recourse** if Zenodo loses your data. What
-you have instead is CERN's operational competence and published practice.
-
-### 5.4 Retention — the actual commitment, quoted
-
-This is the sustainability question, and Zenodo answers it unusually plainly (S3) [DOC]:
-
-> **Retention period:** "Items will be retained for the lifetime of the repository. This is
-> currently the lifetime of the host laboratory CERN, which currently has an experimental
-> programme defined for the next 20 years at least."
-
-> **Succession plans:** "In case of closure of the repository, best efforts will be made to
-> integrate all content into suitable alternative institutional and/or subject based
-> repositories."
-
-So the promise is: *as long as CERN exists*, bounded below by a ~20-year programme horizon,
-with a **best-efforts** (not guaranteed) succession plan. Wikipedia adds that Zenodo is
-supported by CERN "as a marginal activity", with contributions via the CERN & Society
-Foundation (S8) [WEB] — i.e. it is not separately endowed. That is a real, if
-well-managed, concentration risk.
-
-### 5.5 Records are not deleted
-
-The versioning/longevity policy (S3) [DOC]:
-
-> **Versions:** "Data files are versioned. Records are not versioned… Records can be
-> retracted from public view; however, the data files and record are preserved."
-
-> **Withdrawal:** "…the reason for the withdrawal will be indicated on a tombstone page,
-> which will henceforth be served in its place. Withdrawal is considered an exceptional
-> action… The DOI and the URL of the original object are retained."
-
-Practical consequence: **a Zenodo DOI should not rot into a 404.** A withdrawn item becomes
-a tombstone, not a dead link. Confirmed by the OAI-PMH `Identify` response, which declares
-`<deletedRecord>no</deletedRecord>` (S5) [API] — Zenodo does not emit deletion records to
-harvesters, because in its model records are not deleted.
-
-### 5.6 Spam and abuse
-
-An open-to-all repository that mints DOIs is an obvious target for SEO spam, warez and
-link-laundering. Zenodo's published countermeasures are the reactive revocation clause
-(§4) and the 24-hour reporting request (S3) [DOC]. Zenodo also publishes an "AI usage
-notice" in its policy navigation (S3) [WEB].
-
-**[NOT-VERIFIED]** I could not retrieve a Zenodo-published spam-incident report, a
-quantified abuse rate, or a documented anti-spam pipeline description. The policy text
-implies an active trust-and-safety function but does not describe it. Do not assume a
-figure; I have none.
-
-### 5.7 How to sanity-check an individual Zenodo record
-
-1. **Read the resource type and subtype.** `software` with a GitHub
-   `isSupplementTo` relation is a very different object from `publication/article`.
-2. **Follow the `related_identifiers`.** Genuine software releases link to
-   `github.com/OWNER/REPO/tree/TAG`. Genuine supplements link to a journal DOI.
-3. **Check concept vs version DOI** (§6.1). Citing the wrong one changes what you promised
-   your reader.
-4. **Check whether a peer-reviewed version exists** via the `isDocumentedBy` /
-   `isSupplementTo` relations — e.g. record 8409685 (*Scientific colour maps*) carries
-   `isDocumentedBy → 10.5194/gmd-2017-328` (S1) [API].
-5. **Treat the deposit as self-published unless a relation proves otherwise.**
-
-## 6. What you actually find there — examples
-
-### 6.1 The GitHub integration — how a release becomes citable
-
-This is the mechanism the record exists to explain. Verified against Zenodo's own docs
-(S9, S10) [DOC] and against live API records (S1) [API].
-
-**Setup, once per repository** (S9) [DOC], quoted steps:
-1. Connect your GitHub account to Zenodo (profile menu → **GitHub**).
-2. Click **Sync now**.
-3. Find the repository and **toggle the slider** to enable it.
-4. The repository is now connected; refresh to confirm.
-
-Zenodo installs a webhook. Thereafter, **"new releases from the repository will be
-automatically ingested and archived"** (S9) [DOC].
-
-**Per release:** you create a GitHub Release (a tag). Zenodo receives the webhook,
-downloads GitHub's source tarball for that tag, creates a new record, and mints a DOI.
-
-**Describing the software** — two files, with a documented precedence rule (S10) [DOC]:
-- `.zenodo.json` — Zenodo's native metadata file.
-- `CITATION.cff` — the Citation File Format, which GitHub also renders as a "Cite this
-  repository" box.
-- **Precedence, quoted:** *"If your repository also contains a `.zenodo.json` file, Zenodo
-  will only use the `.zenodo.json` metadata and ignore the `CITATION.cff` entirely."*
-  Zenodo still recommends shipping `CITATION.cff` for GitHub's benefit, and states a
-  "long-term preference for open metadata formats like CITATION.cff to eventually make the
-  `.zenodo.json` format unnecessary" (S10) [DOC].
-- Zenodo implements only **a subset** of the CITATION.cff schema (S10) [DOC].
-
-**The resulting record has a recognisable signature** (S1) [API]:
-- Title formatted `owner/repo: Release Name`
-- `related_identifiers` containing
-  `{"identifier": "https://github.com/OWNER/REPO/tree/TAG", "relation": "isSupplementTo"}`
-
-**Concept DOI vs version DOI — the part people get wrong.**
-
-Every versioned Zenodo work has *two kinds* of DOI:
-
-| | Concept DOI | Version DOI |
-|---|---|---|
-| Identifies | the software *as a whole*, across all releases | one specific release |
-| Stability of target | resolves to the **latest** version | resolves to **that** version, forever |
-| API fields | `conceptdoi`, `conceptrecid` | `doi`, `id` |
-| Cite it when | you mean "this project" | you mean "the exact code I ran" |
-
-**Verified live, 2026-09-01** (S11) [API]:
-- `https://doi.org/10.5281/zenodo.3509134` (pandas **concept** DOI) →
-  redirects to `https://zenodo.org/records/21500199`, which is pandas **v3.0.5**.
-- `https://doi.org/10.5281/zenodo.21500199` (pandas **version** DOI for v3.0.5) →
-  redirects to the same `https://zenodo.org/records/21500199`.
-
-Today those land in the same place because v3.0.5 is current. **When pandas cuts v3.0.6,
-the concept DOI will move and the version DOI will not.** For reproducibility — the entire
-reason an engineer cites software — **cite the version DOI**. Cite the concept DOI only
-when you mean the project generically.
-
-Negative control: `https://doi.org/10.5281/zenodo.999999999` → **HTTP 404**, and
-`https://zenodo.org/api/records/999999999` → `{"status": 404, "message": "The persistent
-identifier does not exist."}` (S11) [API]. So unregistered Zenodo DOIs fail cleanly.
-
-**Software Heritage.** Zenodo's GitHub/Software docs state the section "provides details on
-how software records are archived in **Software Heritage**", and that "all the software
-records with a single compressed file are considered for archival" (S12) [DOC]. So an
-eligible Zenodo software deposit is also pushed into Software Heritage's universal source
-archive, giving it a second, independent preservation copy and an SWHID.
-**[NOT-VERIFIED]** I did not confirm the coverage fraction, the latency, or the SWHID
-back-link from an individual Zenodo record — the detail sub-pages under
-`/docs/github/archive-software/` returned 404 on retrieval (§8).
-
-### 6.2 Representative and landmark deposits (all verified live)
-
-All rows below were retrieved from the Zenodo API on 2026-09-01 (S1) [API]. Concept DOIs
-given where present.
-
-| Deposit | Concept DOI | Type | Note |
-|---|---|---|---|
-| `pandas-dev/pandas` | 10.5281/zenodo.3509134 | software | v3.0.5 current at retrieval; BSD-3-Clause |
-| `ultralytics/yolov5` | 10.5281/zenodo.3908559 | software | 1,353,587 views — most-viewed software record found |
-| Scientific colour maps (Crameri) | 10.5281/zenodo.1243862 | software | MIT; `isDocumentedBy → 10.5194/gmd-2017-328` |
-| `desihub/fastspecfit` | 10.5281/zenodo.10253420 | software | BSD-3-Clause; astronomy pipeline |
-| scikit-learn | 10.5281/zenodo.591564 | software | concept record for the ML library |
-| Astropy | 10.5281/zenodo.4670728 | software | astronomy core package |
-| `yt-project/unyt` | 10.5281/zenodo.1344604 | software | units library |
-| India ISIN Database | 10.5281/zenodo.6508187 | software | CC0; v2026.9.1 — a *data* release using the software/GitHub pipeline |
-
-The last row is instructive: the GitHub-release-to-DOI pipeline is routinely used to
-version **datasets** that happen to live in a git repo, not just code. [INF]
-
-### 6.3 Conference artifact-evaluation packages
-
-ACM and USENIX artifact-evaluation committees badge reproducibility artifacts, and Zenodo
-is a common archival target. Verified by search, 2026-09-01 (S1) [API]:
-
-- Query `"USENIX" AND "artifact"` → **254** records.
-- Query `"Artifacts Available"` → **31** records.
-- Query `"artifact appendix"` → **47** records.
-- Query `"artifact evaluation"` → **945** records.
-
-Named, verified examples:
-
-| Artifact | DOI | Venue |
-|---|---|---|
-| `sqlright-artifact` | 10.5281/zenodo.6672457 | USENIX Security 2022 AE |
-| DICE* Artifact | 10.5281/zenodo.4471637 | USENIX Security '21 AE |
-| PETAL | 10.5281/zenodo.14725819 | USENIX 2025, "Artifacts Available" |
-| `congcongmiao/FlexWAN` | 10.5281/zenodo.8309931 | SIGCOMM 2023, "Artifacts Available" |
-| *Relaxing the One Definition Rule in Interpreted C++* | 10.5281/zenodo.3579302 | CC'20 AE |
-| *Optimizing Persistent Memory Transactions* | 10.5281/zenodo.3346054 | PACT19 AE |
-
-All six are resource type `software` (S1) [API]. For a systems engineer this is the most
-directly useful corner of Zenodo: badged, reviewed-for-reproducibility code from top
-systems and security venues, with permanent identifiers.
-
-> **Query caveat:** the search `"OSDI" OR "NSDI"` returned 231 records whose top hits were
-> about air-quality sensors and double ionization — the boolean was not honoured as
-> intended. Zenodo's `q` parameter is not a reliable boolean engine; verify hits by eye.
-> [API]
-
-### 6.4 Hardware and electronics content
-
-Counts by phrase search, 2026-09-01 (S1) [API], all record types:
-
-| Query | Records |
-|---|---|
-| `Arduino` | 5,337 |
-| `FPGA` | 3,334 |
-| `firmware` | 1,878 |
-| `Verilog` | 692 |
-| `"RISC-V"` (quoted) | 495 |
-| `RISCV` | 436 |
-| `"open source hardware"` | 277 |
-| `title:"RISC-V"` | 179 |
-| `KiCad` | 58 |
-
-> **Tokenisation trap — important.** The *unquoted* query `RISC-V` returns **422,778**
-> records. The quoted phrase `"RISC-V"` returns **495**. The hyphen is being treated as a
-> query operator, inflating the count roughly 850×. Negative controls
-> `zzzqqxnotaword12345` (quoted and unquoted) both return 0, so the engine is not simply
-> matching everything. **Always quote hyphenated technical terms against this API.** [API]
-
-**Honest conclusion on hardware:** Zenodo hosts real but thin electronics content. 58 KiCad
-hits is a rounding error against 7.2M records. Zenodo is not where open hardware lives; it
-is where open hardware occasionally gets archived.
-
-### 6.5 Communities — including hardware ones
-
-42,971 communities exist (S1) [API]. Communities are self-service collections with
-depositor-side curation. Verified record counts, 2026-09-01 (S1) [API]:
-
-| Community slug | Title | Records |
-|---|---|---|
-| `swcarpentry` | Software Carpentry | 49 |
-| `hardwarex` | HardwareX | 44 |
-| `sosy-lab-software` | SoSy-Lab Software Collection | 32 |
-| `artifact-evaluation` | Artifact Evaluation | 10 |
-| `openhardware_academy` | The archive of open hardware academy lessons and materials | 8 |
-| `ohresearch` | Open Hardware researchers group | 5 |
-| `hardware-fab` | Hardware-Fab | 2 |
-| `hw_security` | Hardware Security | 1 |
-
-Community *search* totals: `hardware` 652, `electronics` 702, `software` 3,382,
-`"open hardware"` 12 (S1) [API].
-
-**Read those numbers carefully.** The hardware and open-hardware communities contain
-between **one and forty-four records each**. The `artifact-evaluation` community has 10
-records while free-text search finds 945 artifact-evaluation records — i.e. **communities
-capture a negligible fraction of the relevant corpus**. Communities are a discovery
-aid at best; they are not a curation layer you can rely on, and you should not use
-community membership as a filter when surveying Zenodo. [INF]
-
-Negative control: `https://zenodo.org/api/communities/zzz-not-a-real-community-999`
-returns **HTTP 404 NOT FOUND**, so community slugs *do* fail cleanly (unlike facet
-values) (S1) [API].
-
-> **Community search is also fuzzy:** querying communities for `FPGA` returned 37 results
-> whose top hits were `fp7-bmc`, `fp7-dirtpol`, `eurofusion-fp8` — i.e. "FP7"/"FP8"
-> matches, not FPGA. [API]
-
-## 7. Landmark papers (software · distributed systems · databases · electronics · security)
-
-Zenodo is not where landmark *papers* in these fields first appear — that is arXiv and
-IACR ePrint. What Zenodo holds is the **landmark software and artifacts** behind papers.
-The genuinely notable deposits are those in §6.2 (pandas, scikit-learn, Astropy, YOLOv5,
-Scientific colour maps) and the artifact packages in §6.3.
-
-For the template's "preprint first?" question: **none of these are preprints.** They are
-software releases and supplementary artifacts, in every case deposited *alongside or after*
-a publication, not in advance of one. Where a relation exists it is
-`isSupplementTo` (to a GitHub tag) or `isDocumentedBy` (to a journal DOI) — e.g. Scientific
-colour maps → `10.5194/gmd-2017-328` (S1) [API]. I found **no** case of a field-defining
-CS/EE paper whose first public appearance was a Zenodo preprint, and I am not going to
-manufacture one.
-
-## 8. Access, APIs and bulk retrieval
-
-### 8.1 REST API
-
-- Base: `https://zenodo.org/api/records/`
-- Key parameters, all verified working (S1) [API]: `size`, `page`, `q`, `type`, `subtype`,
-  `sort` (`newest`, `mostviewed`), `allversions` (`true`/`false`).
-- `size=0` is rejected: `{"status":400,…"Must be greater than or equal to 1."}` — so the
-  cheapest count query is `size=1`.
-- Response carries `hits.total` plus `aggregations` for `resource_type`,
-  `access_status`, `subject`, `file_type`, `publication_date`. **The aggregations are the
-  best bulk-characterisation tool on the service** and cost one request.
-- No API key is required for public reads. Deposit requires OAuth.
-
-### 8.2 Rate limits
-
-Observed response headers, 2026-09-01 (S1) [API]:
-
-```
-x-ratelimit-limit: 133
-x-ratelimit-remaining: 114
-x-ratelimit-reset: 1788321021
-retry-after: 1
-access-control-expose-headers: …X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
-```
-
-So an unauthenticated client gets **133 requests per window** with the reset exposed in
-headers. Honour them; they are machine-readable, so there is no excuse for not doing so.
-
-### 8.3 OAI-PMH
-
-Endpoint `https://zenodo.org/oai2d`. `Identify` response, 2026-09-01 (S5) [API]:
-
-```xml
-<repositoryName>Zenodo</repositoryName>
-<baseURL>https://zenodo.org/oai2d</baseURL>
-<protocolVersion>2.0</protocolVersion>
-<adminEmail>info@zenodo.org</adminEmail>
-<earliestDatestamp>2014-02-03T14:41:33Z</earliestDatestamp>
-<deletedRecord>no</deletedRecord>
-<granularity>YYYY-MM-DDThh:mm:ssZ</granularity>
-```
-
-Metadata formats offered (`ListMetadataFormats`, S5) [API]: `marcxml`, `oai_dc`, `dcat`,
-`marc21`, `datacite`, `oai_datacite`, `datacite4`, `oai_datacite4`.
-
-Two things to note. First, `earliestDatestamp` is **2014-02-03**, nine months after the
-May 2013 launch — OAI-PMH does not expose the earliest deposits' original datestamps.
-Second, `deletedRecord: no` means **harvesters are never told about withdrawals**; a
-mirror built from OAI-PMH will silently retain tombstoned material. [INF]
-
-### 8.4 Negative controls (as required by house method)
-
-| Probe | Result | Lesson |
-|---|---|---|
-| `?type=notarealtype123` | **HTTP 200**, `total: 0` | Invalid facets look like empty results |
-| `?type=publication&subtype=notarealsubtype123` | **HTTP 200**, `total: 0` | Same |
-| `q=zzzqqxnotaword12345` | HTTP 200, `total: 0` | Text search behaves correctly |
-| `/api/records/999999999` | **HTTP 404** + explicit message | Record IDs fail cleanly |
-| `https://doi.org/10.5281/zenodo.999999999` | **HTTP 404** | Unregistered DOIs fail cleanly |
-| `/api/communities/zzz-not-a-real-community-999` | **HTTP 404** | Community slugs fail cleanly |
-| `oai2d?verb=NotAVerb` | `<error code="badArgument">` | OAI-PMH validates properly |
-| `help.zenodo.org/docs/<bogus>/` | HTTP 404, 9,379 bytes (consistent) | Docs 404s are identifiable by size |
-
-**The single most important row is the first.** Facet-value typos are silent on this API.
-Any count you take from a `type=`/`subtype=` filter must be cross-checked against the
-`resource_type` aggregation, which enumerates only real values.
-
-### 8.5 robots.txt
-
-`https://zenodo.org/robots.txt` (S1) [WEB] disallows `/search`, `/api`, `/uploads`,
-`/records/*/preview` and `/api/records/*/files-archive`; allows `/api/records/*/files`;
-sets `Crawl-delay: 10`. Note the tension: `/api` is *disallowed to crawlers* while
-simultaneously being the documented, rate-limit-headered public interface. Read it as "do
-not spider the API as if it were pages"; scripted API use within the published rate limits
-is the intended path. [INF]
-
-### 8.6 Reacquiring a deposit
-
-1. `GET /api/records/<id>` → JSON metadata including a `files` array with
-   `key`, `size`, `checksum` (MD5), and a download `links.self`.
-2. Fetch each file; **verify the MD5** against the `checksum` field. Zenodo stores and
-   re-checks these itself (§5.1), so this is a genuine end-to-end integrity check.
-3. For a concept DOI, resolve it first to learn the current version, or use
-   `allversions=true` with the `conceptrecid` to enumerate every version.
-4. For whole-corpus work, harvest OAI-PMH with `datacite4` rather than scraping.
-
-## 9. Licensing and reuse
-
-- **Author-chosen, and mandatory.** "Users must specify a license for all publicly
-  available files" (S3) [DOC]. There is no default licence and no blanket grant to Zenodo.
-- **Ownership is unaffected:** "By uploading content, no change of ownership is implied and
-  no property rights are transferred to CERN. All uploaded content remains the property of
-  the parties prior to submission" (S3) [DOC].
-- **Licences observed in practice** on software records (S1) [API]: `bsd-3-clause`
-  (pandas, fastspecfit), `mit-license` (Scientific colour maps), `cc-zero` (India ISIN
-  Database), `other-open` (YOLOv5).
-- **Metadata is CC0.** "Metadata is licensed under CC0, except for email addresses. All
-  metadata is exported via OAI-PMH and can be harvested" (S3) [DOC]. **Text and data
-  mining of metadata is therefore unambiguously permitted.**
-- **Full-text/file mining is *not* blanket-permitted** — it depends on each record's
-  licence, which varies per record. `other-open` on a heavily used record like YOLOv5 shows
-  you cannot assume a standard licence even for prominent software. Check per record.
-
-## 10. Caveats and controversies
-
-### 10.1 The launch-year conflict (recorded, not resolved by preference)
-
-| Source | Claim |
-|---|---|
-| Zenodo About page (S2) [DOC] | "Zenodo was launched in **May 2013**" |
-| Zenodo's own citation BibTeX (S2) [DOC] | `year = {2013}` |
-| Wikipedia, *Zenodo* article (S8) [WEB] | "launched on **8 May 2013**, as the successor of the OpenAIRE Orphan Records Repository" |
-| Wikipedia, *List of preprint repositories* (S7) [WEB] | **2011** |
-
-**Assessment [INF]:** the weight of evidence is overwhelmingly on **May 2013**, including
-from Wikipedia itself. Wikipedia's *list* is internally inconsistent with Wikipedia's own
-*article*. The most plausible explanation is that 2011 refers to the **OpenAIRE Orphan
-Records Repository**, the predecessor service Zenodo succeeded, whose content Zenodo
-inherited. **I could not verify a launch date for the Orphan Records Repository itself**,
-so I cannot confirm 2011 is even correct *for the predecessor* — that specific attribution
-remains **[NOT-VERIFIED]**. Report the record as 2013; note the list entry is unreliable.
-
-Wikipedia's article adds a further wrinkle: "It was relaunched as Zenodo in 2015 to provide
-a place for researchers to deposit datasets" (S8) [WEB]. That 2015 "relaunch" claim is
-**[NOT-VERIFIED]** against any operator source and sits oddly with the 2013 launch; treat
-with caution.
-
-### 10.2 It is not really a preprint server
-
-Preprints are 242,779 of 7,231,598 records — **3.4%** (S1) [API]. Zenodo appears on
-preprint-repository lists because it accepts preprints, not because it is one. Surveys that
-count Zenodo as a preprint server alongside arXiv are comparing different kinds of object.
-
-### 10.3 The corpus is dominated by bulk deposit
-
-`publication-taxonomictreatment` (714,681) is nearly 3× the preprint corpus; the top
-subject keywords are all biodiversity terms; 310,066 records are tagged as sourced from the
-Biodiversity Heritage Library (S1) [API]. Any statistical claim about "research on Zenodo"
-that does not control for this is measuring a taxonomic ingestion pipeline. [INF]
-
-### 10.4 Zero-cost DOIs invite abuse
-
-Anyone can register and mint DOIs at no cost with no screening (§4). The published control
-is post-hoc revocation. See §5.6 — I have **no verified figures** on abuse volume.
-
-### 10.5 Concept-DOI mis-citation
-
-Because the concept DOI silently follows the latest version (§6.1, verified), a paper that
-cites a concept DOI has *not* pinned the code it ran. This is a widespread and under-noticed
-reproducibility failure. [INF]
-
-### 10.6 Single-institution concentration
-
-Retention is explicitly tied to CERN's institutional lifetime, with no SLA and a
-best-efforts succession plan (§5.3–5.4). This is a well-run, transparently-documented risk
-— but it is a risk, and Zenodo says so itself more clearly than most.
-
-## 11. Sources
-
-- **S1** — Zenodo REST API, `https://zenodo.org/api/records/` (with `size`, `type`,
-  `subtype`, `allversions`, `q`, `sort` parameters), `https://zenodo.org/api/communities`,
-  and `https://zenodo.org/robots.txt`. Retrieved **2026-09-01** (server timestamps
-  2026-09-02T03:4x–03:5xZ). Supports: all record counts, resource-type and subtype tables,
-  access-status and file-type distributions, publication-year growth, version ratios,
-  community counts, keyword counts, rate-limit headers, landmark deposit metadata,
-  artifact-evaluation examples, negative controls.
-- **S2** — Zenodo, *About*, `https://about.zenodo.org/`. Retrieved 2026-09-01. Supports:
-  May 2013 launch, OpenAIRE/EC origin, catch-all design philosophy, InvenioRDM, the
-  Zenodotus naming, citation BibTeX with `year = {2013}`.
-- **S3** — Zenodo, *General Policies v1.0*, `https://about.zenodo.org/policies/`.
-  Retrieved 2026-09-01. Supports: eligible depositors, data-quality disclaimer, 50 GB
-  limit, licence requirement, CC0 metadata, revocation and withdrawal, versioning,
-  replicas, retention period, functional-preservation disclaimer, fixity, succession plans.
-- **S4** — Zenodo, *Principles*, `https://about.zenodo.org/principles/`. Retrieved
-  2026-09-01. Supports: the no-SLA statement and FAIR mapping.
-- **S5** — Zenodo OAI-PMH, `https://zenodo.org/oai2d?verb=Identify`,
-  `?verb=ListMetadataFormats`, `?verb=NotAVerb`. Retrieved 2026-09-01. Supports:
-  earliestDatestamp 2014-02-03, `deletedRecord: no`, eight metadata formats, error handling.
-- **S6** — Zenodo FAIR/metadata statements within S4 (DataCite schema compliance, DOI on
-  every published record).
-- **S7** — Wikipedia, *List of preprint repositories*, wikitext retrieved via the MediaWiki
-  API, 2026-09-01. Supports: the "2011" launch year and ">100,000" size claim for Zenodo,
-  and the comparison entries for figshare, Authorea, Synthical, BioHackrXiv.
-- **S8** — Wikipedia, *Zenodo*, retrieved via MediaWiki API, 2026-09-01. Supports: "8 May
-  2013", OpenAIRE Orphan Records Repository predecessor, CERN "marginal activity" and
-  CERN & Society Foundation funding, Invenio, the (unverified) 2015 relaunch claim.
-- **S9** — Zenodo Docs, *GitHub and Software → Enable a repository*,
-  `https://help.zenodo.org/docs/github/enable-repository/`. Retrieved 2026-09-01.
-  Supports: the four setup steps and automatic ingest of new releases.
-- **S10** — Zenodo Docs, *Describe software → CITATION.cff file*,
-  `https://help.zenodo.org/docs/github/describe-software/citation-file/`. Retrieved
-  2026-09-01. Supports: `.zenodo.json` precedence over `CITATION.cff`, subset-schema
-  implementation, cff-convert validation, Zenodo's stated long-term metadata direction.
-- **S11** — DOI resolution probes via `https://doi.org/…` for
-  `10.5281/zenodo.3509134` (concept), `10.5281/zenodo.21500199` (version) and
-  `10.5281/zenodo.999999999` (negative control); plus `/api/records/999999999`.
-  Retrieved 2026-09-01. Supports: §6.1 concept-vs-version resolution behaviour.
-- **S12** — Zenodo Docs, *GitHub and Software* index and *Archive software*,
-  `https://help.zenodo.org/docs/github/` and
-  `https://help.zenodo.org/docs/github/archive-software/`. Retrieved 2026-09-01.
-  Supports: the Software Heritage archival relationship and the single-compressed-file
-  eligibility rule. Sub-pages below `archive-software/` returned HTTP 404 at retrieval.
-- **S13** — Zenodo Docs, *Manage versions*,
-  `https://help.zenodo.org/docs/deposit/manage-versions/`. Retrieved 2026-09-01.
-  Supports: new-version workflow, file import between versions, "completely new record
-  with separate metadata, files and persistent identifier… linked to all previous and
-  future versions".
diff --git a/scratch b/scratch
deleted file mode 120000
index defd63f..0000000
--- a/scratch
+++ /dev/null
@@ -1 +0,0 @@
-../repo-archive/scratch/hardware-doc
\ No newline at end of file
diff --git a/scripts/check-pins.py b/scripts/check-pins.py
deleted file mode 100755
index 13ef735..0000000
--- a/scripts/check-pins.py
+++ /dev/null
@@ -1,125 +0,0 @@
-#!/usr/bin/env python3
-"""Fail if a commit SHA, content hash or URL was removed or rewritten in place.
-
-Pins are append-only (see AGENTS.md). Upstream moving is normal; *losing the old
-ref* is not, because prose elsewhere in the tree was written from it.
-
-Compares the working tree against a git ref (default HEAD) and reports any
-identifier that disappeared or changed value rather than being appended.
-
-    ./scripts/check-pins.py                 # working tree vs HEAD
-    ./scripts/check-pins.py --base origin/main
-    ./scripts/check-pins.py --staged        # index vs HEAD
-    ./scripts/check-pins.py --json
-
-Exit 0 clean, 1 if pins were lost, 2 on usage/git error.
-"""
-from __future__ import annotations
-import argparse, json, re, subprocess, sys
-from collections import defaultdict
-
-# 40- and 12-hex git SHAs, sha256 prefixes, and full sha256.
-SHA_RE = re.compile(r'\b[0-9a-f]{40}\b|\b[0-9a-f]{64}\b|\b[0-9a-f]{12}\b')
-URL_RE = re.compile(r'https?://[^\s<>()\[\]"\'`|]+')
-# Things that look like hashes but are not pins.
-NOISE = re.compile(r'^(0+|f+|deadbeef\w*)$')
-
-TEXT_SUFFIXES = ('.md', '.json', '.jsonc', '.yaml', '.yml', '.txt', '.csv', '.ini', '.toml')
-
-
-def git(*args: str) -> str:
-    r = subprocess.run(['git', *args], capture_output=True, text=True)
-    if r.returncode != 0:
-        print(f"git {' '.join(args)}: {r.stderr.strip()}", file=sys.stderr)
-        sys.exit(2)
-    return r.stdout
-
-
-def changed_files(base: str, staged: bool) -> list[str]:
-    args = ['diff', '--name-only', '--diff-filter=ACMR']
-    if staged:
-        args.append('--cached')
-    args.append(base)
-    return [f for f in git(*args).splitlines() if f.endswith(TEXT_SUFFIXES)]
-
-
-def blob_at(ref: str, path: str) -> str | None:
-    r = subprocess.run(['git', 'show', f'{ref}:{path}'], capture_output=True, text=True)
-    return r.stdout if r.returncode == 0 else None
-
-
-def working(path: str, staged: bool) -> str | None:
-    if staged:
-        r = subprocess.run(['git', 'show', f':{path}'], capture_output=True, text=True)
-        return r.stdout if r.returncode == 0 else None
-    try:
-        return open(path, encoding='utf-8', errors='replace').read()
-    except OSError:
-        return None
-
-
-def ids(text: str) -> dict[str, set[str]]:
-    shas = {s for s in SHA_RE.findall(text) if not NOISE.match(s)}
-    urls = {u.rstrip('.,;:') for u in URL_RE.findall(text)}
-    return {'sha': shas, 'url': urls}
-
-
-def main() -> int:
-    ap = argparse.ArgumentParser(description=__doc__,
-                                 formatter_class=argparse.RawDescriptionHelpFormatter)
-    ap.add_argument('--base', default='HEAD', help='ref to compare against (default HEAD)')
-    ap.add_argument('--staged', action='store_true', help='compare the index instead of the worktree')
-    ap.add_argument('--json', action='store_true', dest='as_json')
-    ap.add_argument('--quiet', '-q', action='store_true')
-    a = ap.parse_args()
-
-    lost: dict[str, dict[str, list[str]]] = defaultdict(lambda: defaultdict(list))
-    files = changed_files(a.base, a.staged)
-
-    for path in files:
-        old = blob_at(a.base, path)
-        if old is None:          # newly added file — nothing can have been lost
-            continue
-        new = working(path, a.staged)
-        if new is None:
-            continue
-        o, n = ids(old), ids(new)
-        for kind in ('sha', 'url'):
-            # A 12-hex prefix of a retained 40-hex SHA is not a loss, and vice versa.
-            gone = set()
-            for v in o[kind] - n[kind]:
-                if kind == 'sha' and any(v.startswith(x[:len(v)]) or x.startswith(v[:len(x)])
-                                         for x in n[kind]):
-                    continue
-                gone.add(v)
-            if gone:
-                lost[path][kind] = sorted(gone)
-
-    if a.as_json:
-        print(json.dumps({'base': a.base, 'files_checked': len(files),
-                          'lost': {k: dict(v) for k, v in lost.items()}}, indent=2))
-        return 1 if lost else 0
-
-    if not lost:
-        if not a.quiet:
-            print(f"check-pins: OK — {len(files)} file(s) checked against {a.base}, "
-                  f"no identifiers removed or rewritten")
-        return 0
-
-    total = sum(len(v) for f in lost.values() for v in f.values())
-    print(f"check-pins: {total} identifier(s) LOST across {len(lost)} file(s)\n")
-    for path, kinds in sorted(lost.items()):
-        print(f"  {path}")
-        for kind, vals in kinds.items():
-            for v in vals:
-                print(f"    - {kind}: {v}")
-    print("\nPins are append-only (AGENTS.md § 'Pins, hashes and identifiers are append-only').")
-    print("Upstream moving is fine — add the new ref and move the old one into prior_refs[],")
-    print("or mark it deprecated. Do not replace it in place.")
-    print("\nIf a removal is genuinely correct (e.g. the value was a typo that never resolved),")
-    print("say so in the commit message.")
-    return 1
-
-
-if __name__ == '__main__':
-    sys.exit(main())
diff --git a/scripts/init.sh b/scripts/init.sh
deleted file mode 100755
index 94c5ada..0000000
--- a/scripts/init.sh
+++ /dev/null
@@ -1,127 +0,0 @@
-#!/usr/bin/env bash
-# Point this repository's archive/ and scratch/ symlinks at the sibling artifact archive.
-#
-# Run after cloning, or any time the archive is added, moved or renamed:
-#
-#     ./scripts/init.sh
-#
-# You usually do not need to. The symlinks are committed in relative form
-# (../repo-archive/hardware-doc and ../repo-archive/scratch/hardware-doc), so a fresh
-# clone already works if the archive sits beside this repo:
-#
-#     <parent>/
-#     |- hardware-doc/     <- this repository
-#     \- repo-archive/     <- artifacts (own repo, usually unpublished)
-#
-# This script matters when the archive is somewhere else, or when this repo is checked
-# out as a linked worktree whose parent is not the archive's parent.
-#
-# It never clones and never deletes. Absent archive is fine: the symlinks stay in their
-# committed relative form and simply dangle, and every *.ARCHIVED.md placeholder still
-# carries hashes and recovery URLs.
-set -uo pipefail
-
-c_g=$'\033[32m'; c_y=$'\033[33m'; c_d=$'\033[2m'; c_0=$'\033[0m'
-[ -t 1 ] || { c_g=; c_y=; c_d=; c_0=; }
-ok()   { printf '%s✓%s %s\n' "$c_g" "$c_0" "$*"; }
-warn() { printf '%s!%s %s\n' "$c_y" "$c_0" "$*" >&2; }
-dim()  { printf '%s%s%s\n' "$c_d" "$*" "$c_0"; }
-
-command -v git >/dev/null || { echo "git not found" >&2; exit 1; }
-
-# Real repository root: --git-common-dir, not --show-toplevel, so a linked worktree
-# resolves to the main checkout's parent rather than its own.
-COMMON="$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null)" \
-  || { echo "not inside a git repository" >&2; exit 1; }
-ROOT="$(dirname "$COMMON")"
-WORKTREE="$(git rev-parse --show-toplevel)"
-NAME="$(basename "$ROOT")"
-
-ARCHIVE_ROOT="${REPO_ARCHIVE_ROOT:-$(dirname "$ROOT")/repo-archive}"
-ART="$ARCHIVE_ROOT/$NAME"
-SCR="$ARCHIVE_ROOT/scratch/$NAME"
-
-dim "repo   : $ROOT"
-dim "archive: $ARCHIVE_ROOT"
-
-if [ ! -d "$ARCHIVE_ROOT" ]; then
-  warn "no archive at $ARCHIVE_ROOT — leaving symlinks as committed"
-  dim "  Placeholders (*.ARCHIVED.md) carry hashes and recovery URLs, so the"
-  dim "  archive is optional. Clone or move it beside this repo and re-run."
-  exit 0
-fi
-
-# rel <link-path> <target> : shortest relative target, so the result stays portable
-rel() { python3 -c 'import os,sys;print(os.path.relpath(sys.argv[2],os.path.dirname(sys.argv[1])))' "$1" "$2"; }
-
-link() {
-  local name="$1" target="$2" path="$WORKTREE/$1"
-
-  if [ ! -d "$target" ]; then
-    warn "$name: $target does not exist — not touching the link"
-    return
-  fi
-  if [ -e "$path" ] && [ ! -L "$path" ]; then
-    warn "$name exists and is not a symlink — refusing to replace it"
-    return
-  fi
-
-  # Prefer the relative form; fall back to absolute only if it cannot reach.
-  local want; want="$(rel "$path" "$target")"
-  ln -sfn "$want" "$path"
-  if [ "$(cd "$path" 2>/dev/null && pwd -P)" != "$(cd "$target" && pwd -P)" ]; then
-    ln -sfn "$target" "$path"
-  fi
-
-  if [ "$(cd "$path" 2>/dev/null && pwd -P)" = "$(cd "$target" && pwd -P)" ]; then
-    ok "$name -> $(readlink "$path")"
-  else
-    warn "$name -> $(readlink "$path")  (does not resolve)"
-    return
-  fi
-
-  # If the link now differs from what HEAD records, say so rather than hiding it.
-  # .gitignore cannot suppress a tracked path; only --skip-worktree can, and doing
-  # that silently is how a stale committed target survives unnoticed.
-  if git -C "$WORKTREE" ls-files --error-unmatch "$name" >/dev/null 2>&1 \
-     && ! git -C "$WORKTREE" diff --quiet -- "$name" 2>/dev/null; then
-    warn "  $name differs from its committed value"
-    dim  "    committed: $(git -C "$WORKTREE" show ":$name" 2>/dev/null)"
-    dim  "    on disk:   $(readlink "$path")"
-    dim  "    If the new value is right for everyone: git add $name"
-    dim  "    If it is local to this checkout only:   git update-index --skip-worktree $name"
-  fi
-}
-
-link archive "$ART"
-link scratch "$SCR"
-
-# --- restore archived files in place as symlinks -------------------------------
-# Every archived artifact has a committed *.ARCHIVED.md placeholder. We additionally
-# place a symlink at the artifact's ORIGINAL path, so a checkout looks and behaves as
-# though nothing was ever moved out: relative references from KiCad projects, build
-# scripts and docs resolve again, and a user holding the archive sees one whole tree.
-#
-# These symlinks are COMMITTED, and they point through this repo's own `archive/`
-# symlink - e.g. `../../../archive/devices/foo/bar.step`, never at ../repo-archive
-# directly. That gives a single indirection point: if the archive moves, only the
-# top-level `archive` link changes and every artifact link follows. It also keeps the
-# targets expressed in this repo's own terms, so they are meaningful in git.
-#
-#     ./scripts/init.sh --link-archived     create/refresh them
-#     ./scripts/init.sh --unlink-archived   remove them
-case "${1:-}" in
-  --link-archived)
-    python3 "$ROOT/tools/link_archived.py" --apply | sed 's/^/  /'
-    dim "  Links route through ./archive/, so they follow the top-level archive symlink."
-    dim "  Run tools/audit_archive.py to check nothing was archived without a marker."
-    ;;
-  --unlink-archived)
-    python3 "$ROOT/tools/link_archived.py" --apply --remove | sed 's/^/  /'
-    ;;
-esac
-
-dim ""
-dim "Both links point into the same repository ($ARCHIVE_ROOT), which is namespaced"
-dim "per source repo. From either one, 'git add -A' stages the whole archive;"
-dim "'git add .' stages only the directory you are standing in."
diff --git a/software/README.md b/software/README.md
deleted file mode 100644
index 0d47ab8..0000000
--- a/software/README.md
+++ /dev/null
@@ -1,124 +0,0 @@
-# Software
-
-Records for **software** that runs on, or is used with, the hardware documented
-in [`devices/`](../devices/README.md) — firmware, SDKs, graphics libraries, host
-tooling and the ecosystems they form.
-
-> **Status: partial.** This tree was started 2026-09-01/02. Only the records
-> listed below exist; the directory skeleton anticipates more. Empty directories
-> are placeholders, not omissions to be treated as findings.
-
-## Taxonomy
-
-Software is filed by **what it is**, not by what hardware it happens to target —
-the same rule the device tree uses for artifacts.
-
-| Category | Definition | Test |
-|---|---|---|
-| [`libraries/`](libraries/) | Reusable code you link against. Solves one problem, no opinion about your application structure | Could you use two of these together? |
-| [`frameworks/`](frameworks/) | Provide the structure; your code fills in the gaps. Inversion of control | Does it call you, or do you call it? |
-| [`applications/`](applications/) | Complete, runnable products — firmware images, host applications | Can a user run it without writing code? |
-| [`tooling/`](tooling/) | Host-side development and content tooling — flashers, simulators, library managers, converters | Runs on your computer, not the device |
-| [`ecosystems/`](ecosystems/) | Cross-cutting analysis of how a family of related projects interrelate: fork networks, dependency graphs, patch portability | Describes relationships, not a single project |
-| [`guides/`](guides/) | Task-oriented, project-independent procedures | — |
-
-A project that genuinely spans categories is filed by its **primary** identity
-with cross-links, rather than duplicated.
-
-## Records
-
-### Applications
-
-| Record | What | Licence | Status |
-|---|---|---|---|
-| [**CrossPoint Reader**](applications/crosspoint-reader/README.md) | The ecosystem's centre of gravity — ESP32 e-reader firmware, ★7,538, **1,621 forks**. Ships `papermono` build environments | MIT | written 2026-09-04 |
-| [**CrossPlay**](applications/crossplay/README.md) | Personal fork of CrossPoint Reader adding ~26 games and tools alongside the reader. ESP32-S3; targets Xteink X4 Pro, Seeed reTerminal Sticky and **M5Stack PaperMono** | MIT | written 2026-09-02 |
-
-### Frameworks
-
-| Record | What | Licence | Status |
-|---|---|---|---|
-| [**FreeInk SDK**](frameworks/freeink-sdk/README.md) | Hardware-independent e-paper reader SDK — panel drivers (incl. **SSD1677**), board profiles, capability gates, and **FreeInkBook**, a full EPUB engine. CrossPoint's submodule | MIT | written 2026-09-04 |
-
-### Tooling and plugins
-
-| Record | What |
-|---|---|
-| [**PaperMono + plugin branch notes**](applications/crosspoint-reader/plugins/papermono-plugin-branch-notes.md) | What is verified vs unknown about running `feat-sd-plugins` on a PaperMono, and the failure modes to expect |
-| [**Plugin source snapshots (archived)**](applications/crosspoint-reader/plugins/source-snapshots.ARCHIVED.md) | 18 snapshots, ~176 MB — **15 unlicensed**, one existing on a single Railway host with no git repo and no Wayback mirror |
-| [**The Libby path**](applications/crosspoint-reader/plugins/libby-path.md) | **Complete, verified route to reading library loans** — which of three competing plugins works (one), the ByteBooks account nobody mentions, and the four fork catalogues pointing at a dead URL |
-| [**SD-card plugins & protected content**](applications/crosspoint-reader/plugins/sd-plugins-and-protected-content.md) | The browser-plugin API, hard limits, store protocol, and the ADEPT client hosted off-GitHub |
-| [**CrossPoint plugin systems**](applications/crosspoint-reader/plugins/README.md) | **There are two, and they are nothing alike.** Upstream's is browser JS with no MCU-side execution; a fork ships native C++ ELF modules with a versioned host ABI. Answers whether NFC/LoRa can be a plugin |
-| [**Simulator build notes**](tooling/crosspoint-simulator-build-notes.md) | ✅ **`executed-success`** — CrossPoint firmware built and run natively on NixOS with no hardware. The working config, and seven portability problems the sample config does not mention |
-| [**Host tooling**](tooling/README.md) | Flasher, simulator, KoSync server, the 400 KB SD recovery flasher, fonts and the pre-FreeInk `community-sdk` — nine tools, two with **no licence file** |
-| [**Calibre**](tooling/calibre/README.md) | The content pipeline: device plugins, the Libby/OverDrive path (**3 years stale**), DRM tooling status, and format guidance for e-paper |
-
-### Libraries
-
-| Record | What |
-|---|---|
-| [**Graphics and display libraries**](libraries/README.md) | LVGL, GxEPD2, u8g2, Adafruit-GFX, epdiy, bb_epaper, JPEGDEC and more — by layer, with the finding that **e-paper panel drivers skew copyleft (GPL/LGPL) while general graphics libraries skew permissive**, which constrains firmware architecture |
-
-### Ecosystems
-
-| Record | What |
-|---|---|
-| [**Using `M5Unit-NFC` in practice**](ecosystems/crosspoint-freeink/m5unit-nfc-practical.md) | Traps, default timeouts, the `config()`-doesn't-configure gotcha, FeliCa system codes, and **measured** per-stage latencies — plus why "slow NFC" turned out to be antenna coupling |
-| [**`M5Unit-NFC` stack overflow**](ecosystems/crosspoint-freeink/m5unit-nfc-overflow.md) | **RF-reachable unbounded write** in the NFC-A emulation listener: the bounds check is real but fed the FIFO length instead of the buffer capacity. Up to ~448 bytes past a 64-byte stack array. Unfixed upstream |
-| [**`paper_name_plate` code review**](ecosystems/crosspoint-freeink/paper-name-plate-review.md) | The Rust firmware held to the same standard — **it contains the same logic error**, where Rust turns memory corruption into a panic |
-| [**Asian-platform search**](ecosystems/crosspoint-freeink/asian-platform-search.md) | Closing the Japanese/Chinese gap: found a **fourth, MIT-licensed** badge project and a 24-article Qiita corpus on the very library with the overflow |
-| [**Plugin architecture**](applications/crosspoint-reader/plugins/plugin-architecture.md) | **How the plugin system actually works** — the two systems, the job queue, the six APIs, and precisely what you can add without firmware vs what forces a fork |
-| [**The ContentProtection library**](frameworks/freeink-sdk/contentprotection-library.md) | The DRM engine, read from source: **ADEPT-only (LCP is a keyword, not code)**, per-entry decrypt at read time, expiry enforced by a monotonic clock floor, **private key stored in the clear on the SD card** |
-| [**`dtsbytebooks.com` review**](applications/crosspoint-reader/plugins/dtsbytebooks-review.md) | **It is Adobe's ebook DRM platform, now run by Wipro** — `adeactivate.adobe.com` CNAMEs into it. Not a grey-market intermediary |
-| [**Plugin source survey**](applications/crosspoint-reader/plugins/plugin-source-survey.md) | `protected-content` and `libby` share **71% of their code**; both use ByteBooks; `sentry.libbyapp.com` is OverDrive's API, not telemetry |
-| [**NFC implementation comparison**](ecosystems/crosspoint-freeink/nfc-implementation-comparison.md) | Three independent NFC stacks on one board — use / patch / replace the vendor library. Includes an **RF-reachable stack overflow in `M5Unit-NFC` 0.1.0** and six other defects found via a third party's build-time patch |
-| [**New PaperMono projects (2026-09)**](ecosystems/crosspoint-freeink/new-papermono-projects-2026-09.md) | Two-week re-sweep: five new projects incl. **two in Rust**, one implementing **NFC tag emulation**. Independently confirms this KB's pin map on every contested point |
-| [**Radios on the PaperMono**](ecosystems/crosspoint-freeink/radios-on-papermono.md) | Can LoRa/NFC be added? **Yes — and not via the SDK.** CrossInk already bypasses the abstraction for ESP-NOW. The four missing pin constants, the RadioLib path, and prototype-vs-upstream effort |
-| [**CrossPoint / FreeInk fork network**](ecosystems/crosspoint-freeink/fork-network.md) | The dependency chain, measured divergence for the major forks, why **9 of 14 named forks are invisible to GitHub's `/forks`**, why "commits behind" is a brick-risk signal here, and a generalisable patch-portability classification |
-
-### Not yet written
-
-Still empty, and **not** to be read as "surveyed and found nothing":
-`applications/crosspoint-reader/plugins/`, `tooling/calibre/` (and its
-`plugins/`), `ecosystems/crosspoint-freeink/`, `libraries/`, and
-`software/guides/`. The plugin system, the Calibre integration, the Libby/DRM
-path, the fork-divergence analysis and the graphics-library survey are all
-**unwritten**.
-
-## Fork links
-
-Where a project is a fork, the parent's directory carries a `forks/`
-subdirectory of **relative symlinks** to the fork records, so the relationship is
-navigable from either end:
-
-```
-applications/crosspoint-reader/forks/crossplay -> ../../crossplay
-```
-
-The symlink resolves to a real record today even though the parent's own record
-does not yet exist — the fork was documented first because its URL was supplied
-directly.
-
-## Relationship to the hardware tree
-
-Software records cross-link device records and vice versa. The live example:
-[CrossPlay](applications/crossplay/README.md) carries `[env:papermono]` build
-targets, so it appears in the
-[M5Stack PaperMono](../devices/m5stack/papermono/projects-and-community.md)
-project population.
-
-## Method
-
-Same evidence discipline as the rest of this knowledge base — see
-[`.agents/skills/hardware-device-research/SKILL.md`](../.agents/skills/hardware-device-research/SKILL.md).
-In particular, for software records:
-
-- **Pin every repository to a full commit SHA.** Branches move.
-- Record licence as metadata. `unknown` and "no LICENSE file, therefore all
-  rights reserved" are both normal, recordable outcomes — not blockers.
-- Label evidence `executed-success` / `reported-working` / `inferred` /
-  `not-tested`. **A repository that was read but not built is `inferred`.**
-- Fork analysis should measure divergence (`ahead`/`behind`, files touched,
-  additions vs deletions) rather than describing it, and should distinguish
-  *additive* divergence from *invasive* divergence — they have completely
-  different maintenance costs.
diff --git a/software/applications/crossplay/README.md b/software/applications/crossplay/README.md
deleted file mode 100644
index c7c3b3a..0000000
--- a/software/applications/crossplay/README.md
+++ /dev/null
@@ -1,248 +0,0 @@
-# CrossPlay
-
-> A personal fork of [CrossPoint Reader](https://github.com/crosspoint-reader/crosspoint-reader)
-> that adds games and small tools alongside the reader.
-> **`ma-r-s/crossplay`** · branch **`xteink`** (default) · MIT · ★15 ·
-> created 2026-08-07 · last push 2026-09-02 · https://crossplay.ma-r-s.com
->
-> Research snapshot **2026-09-01/02**. Nothing was built, flashed or run — no
-> hardware. Every claim is read from the repository at the cited path and is
-> `inferred` unless marked otherwise.
-
-**Classification:** application (complete firmware), not a library or framework.
-Downstream fork. Single-author personal project, MIT-licensed, publicly developed.
-
-## Why this record matters here
-
-CrossPlay is the clearest worked example in this ecosystem of **how to fork a
-fast-moving upstream and stay mergeable**. Its `LOCAL_SCOPE.md` is an explicit,
-maintained accounting of every upstream file the fork touches and why — the
-question "could these changes be a patch series instead of a fork?" is answered
-in the repository itself rather than having to be reverse-engineered.
-
-It is also, relevantly to this knowledge base, **a firmware that builds for the
-[M5Stack PaperMono](../../../devices/m5stack/papermono/README.md)**.
-
-## Identity
-
-| Field | Value |
-|---|---|
-| Repository | `ma-r-s/crossplay` |
-| Upstream parent | `crosspoint-reader/crosspoint-reader` (API `parent` and `source` both) |
-| Default branch | **`xteink`** — not `main`, not `develop` |
-| Licence | MIT |
-| Language | C / C++ |
-| Author | Mario Alejandro Ruiz |
-| Homepage | `https://crossplay.ma-r-s.com` |
-| Submodule | `freeink-sdk` → **`ma-r-s/freeink-sdk`**, branch `x4pro-measured-insets` |
-
-The submodule is worth noting on its own: **CrossPoint consumes the FreeInk SDK
-as a git submodule**, and CrossPlay forks that too. So the fork is a *pair* of
-forks, and a port has two moving upstreams, not one.
-
-## Divergence from upstream
-
-Measured 2026-09-02 via `GET /repos/crosspoint-reader/crosspoint-reader/compare/develop...ma-r-s:crossplay:xteink`
-(`executed-success` — the API call was made; the numbers are GitHub's).
-
-| Metric | Value |
-|---|---|
-| Status | diverged |
-| Ahead | **2,391 commits** |
-| Behind | **65 commits** |
-| Files changed | 300 (**API caps the file list at 300 — the true count is higher**) |
-| Lines | +18,096 / −862 within that capped set |
-
-Where the churn is concentrated, by top-level path:
-
-| Path | Lines changed | Nature |
-|---|---|---|
-| `docs/` | 12,445 | new files |
-| `host-tests/` | 2,956 | new files |
-| `assets_local/` | 1,063 | new files |
-| `.github/` | 933 | fork identity |
-| `README.md`, `AGENTS.md`, `LOCAL_SCOPE.md`, `USER_GUIDE.md`, `ROADMAP.md` | ~1,250 | fork identity |
-
-**Read that table carefully: essentially all of it is new files.** The
-−862 deletions across 300 files is the real signal — this is an overwhelmingly
-*additive* fork. "2,391 commits ahead" sounds like massive divergence and is not.
-
-## The quarantine pattern
-
-Everything the fork adds lives in paths that do not exist upstream:
-
-```
-src/apps_local/     the apps themselves (36 entries: shelf machinery + ~26 apps)
-assets_local/       icons and art
-scripts_local/      fork tooling
-tools_local/
-host-tests/         tests
-docs/               fork documentation
-```
-
-New files cannot conflict. That is the whole trick, and it is applied
-consistently.
-
-### The upstream files it *does* touch
-
-`LOCAL_SCOPE.md` enumerates **28 upstream files**, of which roughly half are
-identity (README, LICENSE, GOVERNANCE, ROADMAP, `.github/` templates, funding,
-workflows) and merge trivially or not at all. The genuine **code seams** are
-these — quoted from the repository's own table:
-
-| File | Why | Size |
-|---|---|---|
-| `src/activities/home/HomeActivity.{cpp,h}` | Games and Apps rows on Home, plus `upstreamMenuRows()` | 4 hooks + 1 method |
-| `src/components/themes/BaseTheme.h` | Two values **appended** to the `UIIcon` palette | 1 appended block |
-| `src/components/themes/lyra/LyraTheme.cpp` | Two cases mapping them to bitmaps | 4 lines |
-| `src/activities/ActivityManager.cpp` | `Frontlight.present()` guard on the light-panel gesture | 1 guard |
-| `src/MappedInputManager.{h,cpp}` | `swallowCurrentTouch()` wrapper over the SDK suppression latch | 1 method |
-| `src/network/OtaUpdater.cpp` | Release URL repointed — upstream's would flash a **C3 build onto an S3** | 1 URL |
-| `lib/hal/HalStorage.{h,cpp}` | `openFileForAppend()` — upstream's write carries `O_TRUNC` | 1 method |
-| `lib/GfxRenderer/GfxRenderer.cpp` | Thick lines thicken across their direction; vertical paths drew 1 px | 1 fix |
-| `lib/PngToBmpConverter/PngToBmpConverter.*` | `…FitWithin()` — contain, not cover | 1 method |
-| `lib/KOReaderSync/KOReaderCredentialStore.cpp` | comment only | — |
-| `src/components/UITheme.cpp` | `getScreenSafeArea()` starts from bezel viewable insets | 1 block |
-| `.gitignore` | ignore `qa-artifacts/` and simulator SD cards | 3 lines, append-only |
-| `platformio.ini` | one `extra_configs` line | 1 line |
-| `.skills/SKILL.md` / `CLAUDE.md` | agent-facing banner | ~20 lines |
-| `SCOPE.md` | one-line pointer | 2 lines |
-
-## Patch portability — which of these would survive upstream churn
-
-This is the analytically interesting part, and the fork's own design makes it
-answerable.
-
-**Trivially portable (append-only, structurally stable).** The `UIIcon` palette
-addition, the `LyraTheme` switch cases, the `.gitignore` lines, the
-`platformio.ini` include. Appending a value to the end of an enum preserves every
-number below it; adding a case to a switch is a pure addition. The author states
-explicitly that **none of these grow when an app is added** — the theme edits are
-per *folder* and there are exactly two folders.
-
-**Portable, and arguably belong upstream.** Four of the seams are not
-game-specific at all — they are **bug fixes and missing primitives**:
-
-- `GfxRenderer` thick-line direction fix
-- `HalStorage::openFileForAppend()` (upstream cannot append to a file at all)
-- `PngToBmpConverter::…FitWithin()` (contain vs cover)
-- `UITheme::getScreenSafeArea()` bezel insets — without which *upstream's own
-  screens draw under the glass*
-
-Any of these could be a small upstream PR. That they live in a fork is a
-maintenance liability for both sides, and the fourth in particular is a
-correctness issue affecting stock CrossPoint on bezelled devices.
-
-**Conflict-prone.** `HomeActivity.{cpp,h}` is the one real seam: four hooks plus
-a method in a file upstream actively develops. The author mitigates this by
-appending after upstream's rows so indices never shift, but any upstream
-restructuring of the home screen lands here.
-
-**Cannot be upstreamed by design.** The `OtaUpdater` URL — pointing at upstream
-would flash a C3 image onto an S3 — and the identity files. These are inherent to
-being a fork.
-
-**Verdict:** this fork is **~90 % new files plus about a dozen small, mostly
-append-only seams**. It is much closer to "a patch series plus a large additive
-tree" than to a divergent codebase. The `SCOPE.md` disagreement — upstream says
-interactive apps are out of scope, the fork says they are the point — is a
-*policy* fork, not a technical one.
-
-## Device support
-
-Build environments in `platformio.ini`:
-
-| Env | Board | Notes |
-|---|---|---|
-| `default`, `gh_release`, `gh_release_rc`, `slim` | `esp32-c3-devkitm-1` | inherited from upstream |
-| `sticky`, `gh_release_sticky` | `esp32-s3-devkitc1-n16r8` | Seeed reTerminal Sticky, added 2026-08-25 |
-| `x4pro`, `gh_release_x4pro` | ESP32-S3 | **Xteink X4 Pro — the design floor** |
-| **`papermono`, `papermono-gh_release`, `papermono-gh_release_rc`** | `esp32-s3-devkitc1-n16r8` | **M5Stack PaperMono** |
-
-`LOCAL_SCOPE.md` names the X4 Pro (ESP32-S3, 480×800 touch, frontlight) and the
-reTerminal Sticky (same S3, same 800×480 panel, GT911 touch, three buttons, no
-frontlight) as the targets; the design floor is "two side keys plus touch".
-
-**The PaperMono envs are present in `platformio.ini` but are not described in
-`LOCAL_SCOPE.md`.** Whether they are maintained, tested, or inherited from
-upstream's PaperMono support is **not established here** — and nobody has
-reported running CrossPlay on a PaperMono. Recorded as an open question, not as
-"supported".
-
-## What it adds
-
-Roughly 26 app directories under `src/apps_local/`, described upstream-facing as
-"twenty-one apps: seventeen games, a spaced-repetition trainer, a Hacker News
-reader, an xkcd viewer and a catalog browser". Observed directory names include
-`battleship`, `bridge`, `checkers`, `chess`, `connectfour`, `connections`,
-`dungeon`, `forehead`, `insider`, `jaipur`, `knucklebones`, `minesweeper`,
-`murdle`, `seasalt`, `solitaire`, `sudoku`, plus `hackernews`, `instapaper`,
-`link`, `player`, `study`.
-
-The shelf machinery (`Shelf`, `ShelfFolderActivity`, `ShelfScreen`,
-`ShelfState`) enforces a two-level hierarchy — a folder holds items, never
-folders — capped "by the type system rather than by discipline", and no app names
-its own return destination (`shelf::leave()`).
-
-## Deliberate deviations from upstream conventions
-
-Scoped entirely to `src/apps_local/`, and documented rather than accidental:
-
-| Upstream rule | CrossPlay in local apps | Stated reason |
-|---|---|---|
-| All user-facing text uses `tr()` | Raw `const char*` | `tr()` means editing `lib/I18n/translations/*.yaml` per app — per-app churn in an upstream file |
-| Icons are `UIIcon` enum variants per app | Shelf items carry a generated `freeink::Icon` (Lucide) | An enum growing per app vs 1,735 icons resolved as assets |
-
-This is a genuinely good pattern to note: **the fork deviates from upstream style
-specifically where following it would increase the upstream-file conflict
-surface.**
-
-## Governance, maintenance and risk
-
-- **Single author.** Bus factor 1.
-- **Actively maintained** — pushed 2026-09-02, 65 commits behind upstream, with a
-  documented `sync.sh` that computes the conflict set from git rather than a
-  hand-kept list (the author notes the hand-kept list "sat at seven entries while
-  the truth grew past twenty" — a nice illustration of why the automated version
-  exists).
-- **Risk:** 65 commits behind at snapshot. In this ecosystem, being behind
-  upstream is a **brick-risk signal** rather than a tidiness one, because vendors
-  revise hardware silently and upstream carries the fixes.
-- OTA points at the fork's own releases; flashing upstream's release onto an S3
-  device would be wrong.
-
-## Artifacts held
-
-Retrieved 2026-09-01/02 into `scratch/eink-software/crossplay/`, not vendored
-into the repository: `README.md`, `LOCAL_SCOPE.md`, `SCOPE.md`, `.gitmodules`,
-`platformio.ini`, `partitions.csv`, `USER_GUIDE.md` (43,621 B),
-`THIRD-PARTY-NOTICES.md`. All fetched from
-`raw.githubusercontent.com/ma-r-s/crossplay/xteink/`.
-
-## Sources
-
-| ID | What | URL | Retrieved | Establishes |
-|---|---|---|---|---|
-| CP01 | Repository metadata | `api.github.com/repos/ma-r-s/crossplay` | 2026-09-02 | Identity, parent, licence, branch, dates |
-| CP02 | Compare vs upstream | `.../compare/develop...ma-r-s:crossplay:xteink` | 2026-09-02 | 2,391 ahead / 65 behind, +18,096/−862 |
-| CP03 | `LOCAL_SCOPE.md` | `raw.githubusercontent.com/ma-r-s/crossplay/xteink/LOCAL_SCOPE.md` | 2026-09-02 | The seam table, quarantine pattern, deviations |
-| CP04 | `platformio.ini` | same host | 2026-09-02 | Build environments incl. PaperMono |
-| CP05 | `src/apps_local/` listing | `api.github.com/.../contents/src/apps_local?ref=xteink` | 2026-09-02 | 36 entries |
-| CP06 | `.gitmodules` | same host | 2026-09-02 | FreeInk SDK submodule and its fork |
-
-## Open questions
-
-- **Are the `papermono` envs real?** Present in `platformio.ini`, absent from
-  `LOCAL_SCOPE.md`, and no report of anyone running it on that board exists.
-- **True file-change count** is unknown — the compare API caps at 300 files.
-- `docs/shelf.md` reportedly references a "previous base" with Sokoban, hinting
-  at an earlier rebase off a different fork. **Not corroborated** — recorded, not
-  asserted.
-- No build was attempted; no binary size, flash usage or runtime figure exists here.
-
-## See also
-
-- **Target hardware:** [Xteink X4 Pro](../../../devices/xteink/x4-pro/README.md) · [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md)
-
-- [M5Stack PaperMono device record](../../../devices/m5stack/papermono/README.md) — the board one env targets
-- [PaperMono third-party projects](../../../devices/m5stack/papermono/projects-and-community.md) — the wider population, including upstream CrossPoint
diff --git a/software/applications/crosspoint-reader/README.md b/software/applications/crosspoint-reader/README.md
deleted file mode 100644
index f16daf7..0000000
--- a/software/applications/crosspoint-reader/README.md
+++ /dev/null
@@ -1,186 +0,0 @@
-# CrossPoint Reader
-
-> Open-source e-reader firmware for ESP32-based devices.
-> **`crosspoint-reader/crosspoint-reader`** · branch **`develop`** · MIT · C++ ·
-> ★7,538 · **1,621 forks** · created 2025-12-03 · last push 2026-09-04 ·
-> ~100 MB · 497 open issues · https://crosspointreader.com
->
-> Snapshot **2026-09-02/04**. Nothing was built, flashed or run — no hardware.
-> Claims are read from the repository at the cited path and are `inferred` unless
-> noted.
-
-**Classification:** **application** — a complete, flashable firmware. It consumes
-the [FreeInk SDK](../../frameworks/freeink-sdk/README.md) as a framework.
-
-## Why it is in this knowledge base
-
-**Upstream CrossPoint ships M5Stack PaperMono support.** `platformio.ini` on
-`develop` carries `[env:papermono]`, `[env:papermono-gh_release]` and
-`[env:papermono-gh_release_rc]`. This is not a fork-only capability — the
-7,500-star upstream builds for the board documented at
-[`devices/m5stack/papermono`](../../../devices/m5stack/papermono/README.md).
-
-## Device support
-
-Build environments on `develop`, retrieved 2026-09-04:
-
-| Env family | Board | Device |
-|---|---|---|
-| `default`, `gh_release`, `gh_release_rc`, `slim` | `esp32-c3-devkitm-1` | Xteink X3 / C3-class — **the tightest target, and it sets the memory ceiling** |
-| `sticky`, `sticky-gh_release`, `sticky-gh_release_rc` | `esp32-s3-devkitc1-n16r8` | Seeed reTerminal Sticky |
-| `x4pro`, `x4pro-gh_release`, `x4pro-gh_release_rc` | `esp32-s3-devkitc1-n16r8` | Xteink X4 Pro |
-| `x4c`, `x4c-gh_release` | `esp32-s3-devkitc1-n16r8` | Xteink X4C |
-| **`papermono`, `papermono-gh_release`, `papermono-gh_release_rc`** | `esp32-s3-devkitc1-n16r8` | **M5Stack PaperMono** |
-
-Fifteen environments across five device families, both ESP32-C3 and ESP32-S3.
-Note every S3 target shares one `esp32-s3-devkitc1-n16r8` board definition —
-16 MB flash, 8 MB octal PSRAM — which matches the PaperMono's configuration and
-its hard OPI-PSRAM requirement.
-
-## Architecture
-
-Device-specific behaviour lives **behind the SDK boundary**, which `SCOPE.md`
-states as policy:
-
-> Device-specific code should live behind the HAL / SDK boundary so the reader
-> core stays portable.
-
-```
-crosspoint-reader  (application: activities, UI, web server, sync, OTA)
-        │  git submodule
-        ▼
-Free-Ink/freeink-sdk  (framework: panel drivers, board profiles,
-                       capability gates, device managers, FreeInkBook)
-```
-
-`.gitmodules` on `develop`:
-
-```ini
-[submodule "freeink-sdk"]
-	path = freeink-sdk
-	url = https://github.com/Free-Ink/freeink-sdk.git
-	branch = main
-```
-
-**The submodule pins a branch, not a commit, in `.gitmodules`** — the actual
-pinned SHA lives in the gitlink. Forks that pin a different SDK revision can
-therefore behave differently without any fork-owned code differing. See the
-[FreeInk record](../../frameworks/freeink-sdk/README.md#who-consumes-it).
-
-Published documentation under `docs/`: `activity-manager.md`, `comparison.md`,
-`dictionary.md`, `file-formats.md`, **`fix-bricked-xteink.md`**,
-`focus-reading.md`, `hyphenation-trie-format.md`, `i18n.md`, `sd-card-fonts.md`,
-`translators.md`, `troubleshooting.md`, `webserver.md`,
-`webserver-endpoints.md`, plus `contributing/`.
-
-That `docs/` list is itself informative: a documented **web server with an
-endpoint reference**, a **hyphenation trie format**, **i18n with a translators
-guide**, and an **unbricking procedure** describe a project considerably past
-hobby scope.
-
-## Scope and governance — unusually explicit
-
-`SCOPE.md` is worth reading in full; it is one of the clearer statements of
-project boundaries in this ecosystem.
-
-**Mission:** *"a dedicated e-reader should do one thing exceptionally well:
-facilitate focused reading."* Explicitly **not** a kitchen-sink firmware, and
-explicitly **not Xteink-only** — it is broadening across ESP32 e-reader hardware.
-
-**The acceptance test for new work** is three questions:
-
-1. Does the stock firmware already do this well? (If so, meet or beat that bar.)
-2. **Is another popular CrossPoint fork already solving this well?** If yes,
-   *defer to that fork* unless it is core reading experience — statistics is the
-   named example.
-3. Does it improve reading or long-term maintainability? If not, out of scope.
-
-Question 2 is the interesting one. **Upstream explicitly delegates
-non-core features to its own fork network** rather than absorbing them. That is a
-deliberate ecosystem design, and it explains why 1,621 forks exist and why forks
-like [CrossPlay](../../applications/crossplay/README.md) (games) and CrossInk
-(stats and reading extras) are *complementary* to upstream rather than
-competitive with it. CrossPlay's `LOCAL_SCOPE.md` — "reading stays upstream's to
-own… anything that makes reading better belongs upstream, so send it there" — is
-the downstream half of the same bargain.
-
-**Current focus** is consolidation, in priority order: DRAM/heap footprint (the
-C3 sets the ceiling), flash footprint, code cleanup, then reading experience.
-**Some areas are temporarily closed to PRs**, new themes among them, because they
-make the multi-device work harder.
-
-## Maintenance signals
-
-| Signal | Value | Reading |
-|---|---|---|
-| Stars / forks | 7,538 / **1,621** | A ~21 % fork ratio — extremely high. Consistent with a project designed to be forked |
-| Open issues | **497** | High in absolute terms; expected at this fork ratio and age |
-| Default branch | `develop`, not `main` | Contribute against `develop` |
-| Age | created 2025-12-03 | Nine months old at snapshot |
-| Activity | pushed 2026-09-04 | Actively developed |
-| Repo size | ~100 MB | Large — mostly generated font and hyphenation assets |
-
-**On the "C" language label:** GitHub reports C. A prior analysis in this project
-found this is Linguist counting ~294 generated font/hyphenation headers
-(~170,000 lines; `hyph-de.trie.h` alone is 12,908) against ~177 hand-written
-C++ files (~47,000 lines). **The project is C++20** (`-std=gnu++2a`). Recorded
-because the label misleads anyone sizing up the codebase. `reported-working`
-from that analysis, not re-derived here.
-
-## Ecosystem
-
-CrossPoint anchors a large fork network. From the earlier survey — **`reported-working`,
-not re-verified in this pass**:
-
-| Fork | ★ | Note |
-|---|---|---|
-| `uxjulia/CrossInk` | ~1,431 | The major second-tier fork; itself heavily forked |
-| `yattsu/biscuit` | ~461 | 2nd most starred, but ~596 commits behind and long untouched |
-| `franssjz/cpr-vcodex` | ~408 | |
-| `trilwu/crosspet` | ~216 | |
-| [`ma-r-s/crossplay`](../../applications/crossplay/README.md) | ~15 | Games and tools; **has `papermono` envs** |
-
-Two ecosystem findings worth carrying forward, both from that earlier survey:
-
-- **Being behind upstream is a brick-risk signal here, not a tidiness metric** —
-  vendors revise hardware silently, and upstream carries the fixes.
-- **Many named forks are "detached"** (`fork: false`, no parent), so GitHub's
-  `/forks` listing understates the network substantially.
-
-Companion first-party projects: `crosspoint-simulator` (run firmware without
-flashing), `xteink-flasher` (web-serial flasher), `crosspoint-sync` (KoSync
-server), `crosspoint-tools`, `escape-hatch` (400-byte SD-card recovery flasher),
-`calibre-plugins`.
-
-## Sources
-
-| ID | What | URL | Retrieved |
-|---|---|---|---|
-| CR01 | Repository metadata | `api.github.com/repos/crosspoint-reader/crosspoint-reader` | 2026-09-04 |
-| CR02 | `platformio.ini` — the 15 environments | `raw.githubusercontent.com/crosspoint-reader/crosspoint-reader/develop/platformio.ini` | 2026-09-04 |
-| CR03 | `.gitmodules` — the FreeInk submodule | same host | 2026-09-04 |
-| CR04 | `SCOPE.md` — mission, acceptance test, closed areas | same host | 2026-09-04 |
-| CR05 | `docs/` listing | `api.github.com/.../contents/docs?ref=develop` | 2026-09-04 |
-| CR06 | `ROADMAP.md`, `GOVERNANCE.md`, `partitions.csv` | same host | 2026-09-04 |
-
-## Open questions
-
-- **No commit SHA pinned.** Identity here is by branch. A later pass should pin
-  `develop`'s HEAD before citing specific code.
-- **The plugin system is not covered by this record.** A prior analysis reported
-  it lives on unmerged feature branches rather than `develop`, is
-  browser-JavaScript plus JSON manifests with **no code running on the MCU**, and
-  therefore **cannot reach GPIO/I²C/SPI at all**. That has direct bearing on
-  whether NFC/LoRa could ever be a plugin — but it is `reported-working` from
-  that pass and **was not re-verified here**. Treat as unconfirmed.
-- Binary size, flash/RAM usage and build time for any environment: unmeasured here.
-- Whether the `papermono` envs have been run on real hardware by anyone: **unknown**.
-  See [`papermono/projects-and-community.md`](../../../devices/m5stack/papermono/projects-and-community.md).
-
-## See also
-
-- **Target hardware:** [Xteink X3](../../../devices/xteink/x3/README.md) · [X4](../../../devices/xteink/x4/README.md) · [X4 Pro](../../../devices/xteink/x4-pro/README.md) · [X4 Classic](../../../devices/xteink/x4-classic/README.md) · [S4](../../../devices/xteink/s4/README.md) · [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md)
-
-- [FreeInk SDK](../../frameworks/freeink-sdk/README.md) — the framework beneath it
-- [CrossPlay](../crossplay/README.md) · [`forks/`](forks/) — fork records
-- [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) — a supported target
diff --git a/software/applications/crosspoint-reader/forks/crossplay b/software/applications/crosspoint-reader/forks/crossplay
deleted file mode 120000
index 8b42906..0000000
--- a/software/applications/crosspoint-reader/forks/crossplay
+++ /dev/null
@@ -1 +0,0 @@
-../../crossplay
\ No newline at end of file
diff --git a/software/applications/crosspoint-reader/plugins/README.md b/software/applications/crosspoint-reader/plugins/README.md
deleted file mode 100644
index a3e45e8..0000000
--- a/software/applications/crosspoint-reader/plugins/README.md
+++ /dev/null
@@ -1,253 +0,0 @@
-# CrossPoint plugin systems — and whether NFC/LoRa could ever be a plugin
-
-> There is no single "CrossPoint plugin system". There are **two, of completely
-> different kinds**, built by different people, and confusing them produces wrong
-> answers to the question that matters: *can a plugin reach hardware?*
->
-> Snapshot **2026-09-04**. Repository facts `executed-success` (GitHub API);
-> design descriptions read from the projects' own documentation, `inferred` for
-> behaviour. **Nothing was built or run.**
-
-## The short answer
-
-**No — not as a plugin alone, in either system. But the gap is much smaller than
-"fork the firmware".**
-
-| System | Where code runs | Can it reach GPIO / I²C / SPI? |
-|---|---|---|
-| Upstream CrossPoint (roadmap, unmerged) | **Browser only** — JavaScript + JSON manifests | **No.** No code executes on the MCU at all |
-| `mekhontsev` fork — native SD plugins | **On the MCU** — native C++ ELF modules | **No**, but only because the host ABI allow-list omits them — and it is extensible |
-
-The second is the interesting one, and it changes the answer from "impossible" to
-"requires a small, well-defined firmware change".
-
-## System 1 — upstream's JavaScript plugins
-
-Per a prior analysis in this project (`reported-working`, **not re-verified
-here**):
-
-- The plugin work lives on **two unmerged feature branches**, not `develop`, and
-  is a Phase 2 roadmap item.
-
-> **CORRECTION 2026-09-11.** The "unmerged branches" framing above understates
-> the state of this work. Measured against `develop`:
->
-> | Branch | vs `develop` | Tip | Reading |
-> |---|---|---|---|
-> | **`feat-sd-plugins`** | **66 ahead, 0 behind** | **2026-09-10** | Contains all of `develop` plus 66 commits — **a clean merge**, actively developed, and it carries **`[env:papermono]`** |
-> | `feat-sd-web-plugins` | 64 ahead, 58 behind | — | genuinely divergent |
->
-> There is also a **live plugin ecosystem** — `itsthisjustin/sd-plugins` (★36,
-> 10 forks, pushed 2026-09-10) with a store protocol, eight plugins and
-> independent third-party catalogues. See
-> [sd-plugins and protected content](sd-plugins-and-protected-content.md) and
-> [the Libby path](libby-path.md).
-- Plugins are **browser JavaScript plus declarative JSON manifests**. No
-  interpreter (Lua, WASM, QuickJS, Duktape) is vendored anywhere in the firmware.
-- The injected API is roughly five functions — relay, crypto, writeFile,
-  fetchToSd, registerAction.
-- Upstream's own docs state the on-device plane works *"without any code running
-  on the device."*
-
-**So the boundary is not "curated hardware access" — it is "no execution".** A
-plugin in this model is a web page talking to the firmware's HTTP server. It
-could no more toggle a GPIO than a browser tab could.
-
-The **plugin store** for this system is
-[`ruqqq/crosspoint-plugins`](https://github.com/ruqqq/crosspoint-plugins) —
-JavaScript, HEAD `8aa65e18`, last push 2026-08-18, ★0, **no licence file**. It
-describes itself as "a plugin-store catalog and the plugins it ships". At zero
-stars and no licence it is very early work, and its all-rights-reserved default
-matters if anyone intends to redistribute from it.
-
-A related first-party-adjacent example:
-[`samfoy/crosspoint-bookorbit-plugin`](https://github.com/samfoy/crosspoint-bookorbit-plugin)
-(JavaScript, HEAD `d5957f13`, no licence) — a reading-session sync plugin, which
-is exactly the shape this system is good at: **network and data, not hardware**.
-
-## System 2 — the `mekhontsev` native plugin host
-
-[`mekhontsev/crosspoint-plugins`](https://github.com/mekhontsev/crosspoint-plugins)
-— C/C++, **MIT**, HEAD `b503aaa7`, last push 2026-09-01.
-
-This is a genuinely different architecture and it invalidates any blanket claim
-that "CrossPoint plugins can't run on the device". It is **native C++ ELF modules
-loaded from the SD card at runtime**, against a versioned host ABI (**currently
-version 3**).
-
-```
-upstream CrossPoint Reader
-      │  small, mergeable fork delta
-      ▼
-firmware fork: Plugins entry + loader + host ABI + BLE transport
-      │  lazy native loading from /plugins
-      ▼
-manager.so ──discovers child metadata──► terminal.so, further .so modules
-      ▲
-      │  authenticated PageWire protocol (BLE)
-PageWire client (Android/Termux)
-```
-
-Design points worth recording:
-
-- **Lazy.** No plugin code runs at boot. `manager.so` loads only when the user
-  opens the Plugins menu.
-- **No firmware-side catalog.** The firmware knows one path,
-  `/plugins/manager.so`, and an ABI version. Child modules are discovered from
-  metadata embedded in their own ELF images (`.crosspoint.plugin` section).
-- **Independently updatable** — plugins rebuild and reinstall without reflashing
-  the reader.
-- **Explicitly not a sandbox.** The docs say so directly: *"This is an
-  experimental native extension mechanism, not a security sandbox. A bad plugin
-  can crash and restart the reader."* Containment is that a crashed activity
-  doesn't enter the boot path — remove the `.so` and the reader is fine.
-- **Small upstream delta** — the firmware fork is deliberately kept mergeable,
-  matching the ecosystem's general fork discipline.
-
-It is a three-repository system: the firmware fork
-(`mekhontsev/crosspoint-reader`), the plugins, and `mekhontsev/pagewire` (the
-Android/Termux client and protocol spec). **Xteink X4 Pro only**, and
-self-described as experimental.
-
-### The ABI allow-list — the actual boundary
-
-This is the load-bearing detail. The host exposes a deliberately small symbol
-allow-list, and **the plugin build fails if a module references anything outside
-it**:
-
-| Exposed | |
-|---|---|
-| Activity lifecycle | `onEnter`, `loop`, `onExit`, redraw, child activities |
-| Display and UI | screen size, text measurement/drawing, lines, rects, framebuffer, theme metrics, plugin-registered fonts |
-| Input | mapped hardware buttons, touch rectangles, long presses |
-| Text input | the firmware-owned keyboard (`crosspoint_plugin_*_keyboard_v2`) |
-| Localization | `I18n` lookup |
-| BLE | the shared authenticated PageWire GATT transport |
-| Plugin management | child discovery, streamed install, update status |
-| Diagnostics/runtime | logging, time, heap/PSRAM queries, allocation, a limited C/C++ runtime, a small FreeRTOS subset |
-
-**Explicitly *not* exported:** *"general storage, Wi-Fi, networking, and arbitrary
-NimBLE APIs"*. And notably **no GPIO, no I²C, no SPI** appears anywhere in the
-list.
-
-`PluginHostSymbols.inc` in the firmware fork is the authoritative allow-list, and
-the docs are precise that *"a declaration being present in a firmware header does
-not make its implementation part of the plugin ABI."*
-
-## What this means for NFC and LoRa on the PaperMono
-
-The [PaperMono](../../../../devices/m5stack/papermono/README.md) has an ST25R3916
-NFC reader on I²C and an SX1262 LoRa module on SPI, both behind an I/O expander
-that also gates their power rails.
-
-Working through it:
-
-1. **Upstream JS plugins — impossible.** No MCU-side execution. Not a limitation
-   to work around; there is nothing to work with.
-2. **Native ELF plugins — blocked by the allow-list, not by the architecture.**
-   Native code does run on the MCU. But NFC needs I²C, LoRa needs SPI, and both
-   need expander-controlled enables — none exported. The build would **fail at
-   link time** on the unresolved symbols, by design.
-3. **The documented escape hatch is small.** The plugin docs say: *"When a
-   genuinely reusable host service is missing, add the smallest stable entry point
-   to the firmware ABI, add it to the allow-list, and increment the ABI if the
-   change is incompatible."*
-
-**So the honest answer is a firmware change is required — but a small, structured
-one**, not a fork of the reader. Something like an `i2cTransfer` / `spiTransfer`
-host service plus expander-pin control, added to `PluginHostSymbols.inc` with an
-ABI bump. The radio driver itself (RadioLib, an ST25R3916 stack) could then live
-entirely in the plugin.
-
-Two caveats before anyone treats that as a plan:
-
-- **The ABI is X4 Pro-only today.** The PaperMono is not a target of this fork,
-  so the port work comes first — and the PaperMono's peripherals sit behind an
-  M5IOE1 expander and M5PM1 power manager that this fork has never seen.
-- **Exporting raw bus access weakens the containment story.** A plugin that can
-  drive I²C can also wedge the shared bus that the RTC, touch, IMU, expander and
-  power manager all sit on — see the PaperMono's
-  [resources-and-conflicts](../../../../devices/m5stack/papermono/resources-and-conflicts.md).
-  The charger already has a documented bus-stability hazard on that bus.
-
-**A cleaner design would export *capability* services** — "read an NFC tag",
-"send a LoRa packet" — rather than raw buses, keeping bus arbitration in the
-firmware where it belongs. That is a firmware feature with a plugin-facing API,
-which is arguably the right answer anyway.
-
-## Correction to this knowledge base
-
-An earlier pass recorded, flatly, that CrossPoint plugins *"cannot reach GPIO,
-I²C, SPI or any peripheral — the injected API is five functions"*, and that
-therefore NFC/LoRa *"would require a fork."*
-
-That was **true of upstream's system and wrong as a general claim.** A
-third-party fork has built a native ELF plugin host where plugin code genuinely
-executes on the MCU. The correct statement is:
-
-> Hardware access is gated by a **firmware-side ABI allow-list**, not by the
-> absence of on-device execution. Extending it is a documented, bounded
-> firmware change rather than a fork of the reader.
-
-Recorded here rather than silently edited, per the method's treatment of refuted
-claims. Date 2026-09-04; refuting artifacts `ARCHITECTURE.md` and
-`PLUGIN_DEVELOPMENT.md` in `mekhontsev/crosspoint-plugins` at HEAD `b503aaa7`.
-
-
-### Verified at source, not just documentation (2026-09-04)
-
-The previous section reported the allow-list from `PLUGIN_DEVELOPMENT.md`. The
-authoritative file has now been **read directly** —
-`mekhontsev/crosspoint-reader:main/src/plugins/PluginHostSymbols.inc`, 81 lines,
-5,201 bytes, retrieved 2026-09-04 (`executed-success`).
-
-It is a flat list of `PLUGIN_HOST_SYMBOL(n, "<mangled name>")` entries. Census by
-category:
-
-| Category | Present in the allow-list? |
-|---|---|
-| **I²C** | **absent** |
-| **SPI** | **absent** |
-| **GPIO** (`pinMode`, `digitalWrite`) | **absent** |
-| **ADC / PWM / LEDC** | **absent** |
-| **Wi-Fi** | **absent** |
-| **Storage / file** | **absent** |
-| BLE (`ble_terminal::*`) | **present, 15 symbols** |
-
-What *is* exported, from the demangled names: `logPrintf`; `GfxRenderer`
-(`insertFont`, `clearScreen`, `getTextWidth`, `displayBuffer`); `UITheme`
-(`drawCenteredText`, `drawCenteredWrappedText`, `instance`); `Activity`
-(`onEnter`, `onExit`, `onGoHome`, `requestUpdate`, `requestUpdateAndWait`,
-`startActivityForResult`); `I18n::getInstance`; `EspClass::getFreeHeap` and
-`getFreePsram`; and the `ble_terminal` transport surface.
-
-**The documentation was accurate.** A plugin gets UI, input, BLE, i18n and heap
-introspection — and nothing that touches a bus, a pin or a filesystem. The
-peripheral gap is not an oversight in the docs; it is the actual contract, in the
-actual file, and the build enforces it.
-
-## Sources
-
-| ID | What | Retrieved |
-|---|---|---|
-| PL01 | `ruqqq/crosspoint-plugins` metadata, HEAD `8aa65e18` | 2026-09-04 |
-| PL02 | `mekhontsev/crosspoint-plugins` metadata, HEAD `b503aaa7`, MIT | 2026-09-04 |
-| PL03 | `mekhontsev/crosspoint-plugins/ARCHITECTURE.md` | 2026-09-04 |
-| PL04 | `mekhontsev/crosspoint-plugins/PLUGIN_DEVELOPMENT.md` — the ABI allow-list | 2026-09-04 |
-| PL05 | `samfoy/crosspoint-bookorbit-plugin` metadata, HEAD `d5957f13` | 2026-09-04 |
-
-## Open questions
-
-- **Upstream's JS plugin system was not re-verified in this pass.** Its
-  description is carried over from an earlier analysis.
-- `PluginHostSymbols.inc` was **not read directly** — the allow-list above is
-  from the documentation that describes it. Read the file before designing
-  against it.
-- Whether upstream intends to adopt anything like the native ABI is unknown.
-- No plugin was built; the ABI-v3 contract is untested here.
-
-## See also
-
-- [CrossPoint Reader](../README.md) — the firmware
-- [Fork network](../../../ecosystems/crosspoint-freeink/fork-network.md) — how forks like `mekhontsev`'s relate to upstream
-- [PaperMono NFC](../../../../devices/m5stack/papermono/features/nfc.md) · [LoRa](../../../../devices/m5stack/papermono/features/lora.md)
diff --git a/software/applications/crosspoint-reader/plugins/dtsbytebooks-review.md b/software/applications/crosspoint-reader/plugins/dtsbytebooks-review.md
deleted file mode 100644
index 3061868..0000000
--- a/software/applications/crosspoint-reader/plugins/dtsbytebooks-review.md
+++ /dev/null
@@ -1,167 +0,0 @@
-# `dtsbytebooks.com` — what it is
-
-> Reviewed **2026-09-11** because two third-party plugins reference it and nobody
-> had checked what it was. The short answer inverts the concern that prompted the
-> review.
->
-> Retrievals are `executed-success`. **No account was created, nothing was logged
-> into, no credential was transmitted, and no endpoint was probed beyond ordinary
-> unauthenticated `GET`s of public pages.**
-
-## It is Adobe's ebook DRM platform, under new ownership
-
-ByteBooks is the continuation of the **Adobe eBook Platform** — Adobe Content
-Server (ACS), the Reader Mobile SDK (RMSDK), and Adobe Digital Editions (ADE).
-Adobe divested it. Adobe's own support site states:
-
-> *"Ongoing platform support and feature development for Adobe eBook Platform
-> Components … is now handled by **Wipro Engineering – Connected Services
-> (formerly HARMAN Digital Transformation Solutions (DTS))**. As of **July 2025**,
-> Adobe transitioned these responsibilities to Wipro."*
-
-**"DTS" = Digital Transformation Solutions**, Harman's former division — which is
-where the domain name comes from. End-user cutover was **2026-06-23**, when
-ByteBooks IDs replaced Adobe IDs.
-
-### The DNS is conclusive
-
-This is not a claim that rests on marketing copy. Adobe's own production hostnames
-now delegate into this domain:
-
-| Query | Result |
-|---|---|
-| `adeactivate.adobe.com` | **CNAME → `activate.dtsbytebooks.com`** |
-| `readerscert.adobe.com` | CNAME → `readerscert.dtsbytebooks.com` |
-| `nasigningservice.adobe.com` | CNAME → `nasigningservice.dtsbytebooks.com` |
-| `eusigningservice.adobe.com` | CNAME → `eusigningservice.dtsbytebooks.com` |
-| `GET contentserver.dtsbytebooks.com/` | returns `"You have reached contentserver.adobe.com"` |
-
-Only whoever controls Adobe's DNS can create those records. The TLS certificate
-carries both `adeactivate.adobe.com` and `*.dtsbytebooks.com` as SANs.
-
-## Who runs it
-
-| | |
-|---|---|
-| Operator | **Wipro Ltd** (NYSE: WIT), Bengaluru |
-| Legal entity | *"General Counsel, Wipro Ltd, Doddakannelli, Sarjapur Road, Bangalore"* (from the EULA) |
-| Contact | `ebooks-support@wipro.com`, `contentserver-support@wipro.com` |
-| Registrar | **CSC Corporate Domains** — an enterprise brand-protection registrar |
-| TLS | Sectigo **OV**, issued to `Harman International Industries, Incorporated` — a transition artefact |
-| Hosting | AWS (S3/CloudFront, ELB `us-west-2`) for the site and content server; **Oracle Cloud** for activation and signing |
-| Domain created | **2025-10-31** · Wayback first capture **2026-05-20** |
-
-No privacy shield, no anonymity, named public company, named general counsel.
-
-## Funding
-
-**Free for end users.** OverDrive's documentation: *"A ByteBooks ID is a **free**
-account…"* There is no payment step in registration.
-
-Revenue is **B2B**, exactly as Adobe's was — licensing Content Server, RMSDK and
-white-label reader apps to publishers, retailers and libraries. Adobe's notice
-says Wipro handles *"customer support, contract renewals … billing."* No public
-price list; enterprise quote-based.
-
-So the answer to *"if it's free, what pays for it?"* is: **publishers do, as they
-always did.** This is an inherited enterprise platform, not a venture-funded
-startup that needs to monetise users later.
-
-## What using it involves
-
-1. Register at `dtsbytebooks.com/register` — first/last name, country, email,
-   password. No payment, no library card, no proof of purchase.
-2. **If you have an existing Adobe ID, tick the migration box and use the exact
-   same email.** That is what preserves your existing licences.
-3. Existing authorised devices keep working. You need the account when
-   authorising a *new* device.
-
-Device limit is 10 per user, inherited from Adobe.
-
-## What it receives
-
-The published privacy text discloses processing of: user ID, device ID,
-application ID, IP address (country-level), expiry/lending data, ebook metadata
-(title, author, publisher, ISBN), and:
-
-> *"**Percentage of Content Read** — Used to support subscription or usage-based
-> access models"*
-
-**That is the most privacy-adverse item**, and it deserves to be stated plainly
-rather than buried: the platform is capable of reporting how far through a book
-you are. It was in Adobe's platform too — cf. the 2014 ADE telemetry controversy
-— so this is continuity, not a new imposition. But "it was always like this" is
-not the same as "it is fine".
-
-Also disclosed: *"If you open or read an eBook that does not include digital
-rights management (DRM), ByteBooks Digital Editions does not process user or
-device information."*
-
-`robots.txt`, `sitemap.xml` and `.well-known/security.txt` all return 403. **The
-absence of a `security.txt` is a small mark against them** for a service holding
-account credentials.
-
-## Legal posture
-
-There is no "is this an Adobe-licensed operator?" question to answer, because
-**it is the licensor**. The platform is designed to *enforce* ADEPT, not
-circumvent it. Nothing about ByteBooks is grey-market.
-
-## Reputation
-
-- **Leseratte10**, author of the leading independent ACSM/Calibre plugin, tested
-  the transition on 2026-06-24: *"the current versions of the plugin continue to
-  work as if nothing had happened … it's now downloaded from a server under
-  dtsbytebooks.com instead of an Adobe server."* No security concerns raised.
-- **MobileRead** showed mild wariness, no alarm — one poster noted *"I can't find
-  much about Bytebooks apart from their own material"*, and another immediately
-  linked Wipro's Wikipedia entry.
-- **OverDrive** and **eBooks.com** both publish official ByteBooks instructions.
-- **No fraud, phishing, scam or breach reports found.** Complaints are ordinary
-  migration friction — password resets, device-limit errors.
-
-## Where the actual risk is
-
-Not here. The genuine exposure in this stack is the **plugins**, and it is worth
-being precise:
-
-1. **`protected-content` is fetched live from a Railway URL with no repository,
-   no version pinning and no licence.** Its author can change `plugin.js` at any
-   time, and it loads into an unauthenticated page where you type a password.
-   That is the real supply-chain concern. `libby` at least lives in a public repo
-   where changes are visible.
-2. **`authURL` is discovered at runtime** from the activation service, so whoever
-   controls that DNS chooses where your RSA-wrapped password is posted. Inherent
-   to ADEPT and equally true of Adobe Digital Editions itself — but it means trust
-   ultimately rests on DNS.
-3. The RSA wrapping uses **Adobe certificates that expired in 2013/2018**; ADEPT
-   clients don't check expiry. Normal for the protocol, worth knowing.
-
-The password itself is RSA-encrypted to the service certificate before it leaves
-the device (`protected-content` ≈ lines 385–425), which is textbook ADEPT
-`SignInDirect`.
-
-## Known / inferred / unknown
-
-| | |
-|---|---|
-| **Known** | ByteBooks = Adobe's ebook DRM platform under Wipro since July 2025; user cutover 2026-06-23; free to users, B2B-funded; the Adobe→ByteBooks CNAMEs; registrar, hosting, cert, domain age. Corroborated independently by Adobe, OverDrive, eBooks.com and Leseratte10 |
-| **Inferred** | Wipro now holds the ADEPT certificate private keys — follows necessarily from operating `SignInDirect`. The Harman-named TLS cert is a transition leftover |
-| **Unknown** | Server-side logging and retention specifics; B2B pricing; independent press coverage of the Harman-DTS/Wipro transfer |
-
-**The service is not opaque** — which was the thing worth checking, and the
-opposite of what was assumed.
-
-## Method and limits
-
-Public pages and public APIs only, unauthenticated `GET` exclusively. **No
-account created, no login attempted, no credential sent, no `POST` issued, no
-vulnerability probing.** Because only `GET` was used, a method-gated API route
-cannot be *fully* excluded — though a CloudFront/S3 origin returning the SPA shell
-for every tested path makes one very unlikely.
-
-## See also
-
-- [Plugin source survey](plugin-source-survey.md) — including the **retraction** of this
-  knowledge base's earlier claim that the plugins call `dtsbytebooks.com/api/*`
-- [The Libby path](libby-path.md)
diff --git a/software/applications/crosspoint-reader/plugins/libby-path.md b/software/applications/crosspoint-reader/plugins/libby-path.md
deleted file mode 100644
index 02224ee..0000000
--- a/software/applications/crosspoint-reader/plugins/libby-path.md
+++ /dev/null
@@ -1,287 +0,0 @@
-# Reading Libby loans on a CrossPoint device — the complete path
-
-> Every step, every account, every failure mode, and which of the competing
-> implementations actually works.
->
-> Researched **2026-09-11**. Repository facts, HTTP probes and source reads are
-> `executed-success`. **Nothing was installed, activated or run** — no device, no
-> library card, no content account. Procedures are `reported-working` from the
-> plugins' own documentation.
-
-## The answer in one table
-
-There are **three** Libby plugins in circulation. Only one of them works.
-
-| Plugin | Version | Source | Status |
-|---|---|---|---|
-| **`ruqqq/crosspoint-plugins` → `libby`** | **1.0.2** | `raw.githubusercontent.com/ruqqq/crosspoint-plugins/main/libby/` | ✅ **Live** — all three files fetch (HTTP 200, `plugin.js` 64,847 B) |
-| `itsthisjustin/sd-plugins` → `libby` | 0.2.0 | `raw.githubusercontent.com/itsthisjustin/sd-plugins/main/libby/` | ❌ **Gone — HTTP 404.** Directory removed; not in upstream's catalogue |
-| Four fork catalogues listing `libby` 0.2.0 | 0.2.0 | point at the dead URL above | ❌ **Broken** — install will fail |
-
-`pagdot`, `marczykm`, `dezren39` and `josmerod` all carry a `libby` entry in
-their forked `catalog.json` whose `base` is the deleted upstream path. Their
-descriptions differ (*"Fetch Libby books via the web interface"* vs *"Link Libby,
-view your loans, and fulfill them"*) but the URL is identical and dead.
-
-**Use `ruqqq`'s.** It is a separate, self-contained implementation — it does
-**not** require the `protected-content` plugin, unlike the removed one.
-
-## Prerequisites
-
-| Requirement | Detail |
-|---|---|
-| **Firmware** | A build from **`feat-sd-plugins`** (66 commits ahead of `develop`, 0 behind, tip 2026-09-10). `develop` has **no plugin API at all** |
-| **Plugin Store** | Unzip `plugin-store.zip` at the SD root, then add `https://raw.githubusercontent.com/ruqqq/crosspoint-plugins/main/catalog.json` as a store |
-| **Network mode** | **File Transfer → Join Network** (*not* Hotspot) — the reader must actually be online |
-| **Library card** | A normal Libby/OverDrive account |
-| **Content account** | A **DTS ByteBooks** account — `dtsbytebooks.com/register`. **Separate from your library card** |
-
-That last row is the one people miss. The ByteBooks account is what authorises
-*this device* to open protected books; the library card is what lends them.
-
-## Setup, once
-
-1. Device web page → **File Manager** → the **Libby** card.
-2. Enter the **content account** email and password → **Activate device**.
-   Writes a credential to `/.crosspoint/content.key`.
-3. Tap **Link Libby** — the card shows an **8-digit code**.
-4. In the Libby app: **menu → Copy To Another Device**, enter that code.
-   The card picks it up within a minute and lists your library.
-
-## Borrowing, each time
-
-1. Borrow the title in Libby as normal.
-2. On the Libby card: **Refresh loans**, pick the title.
-3. **Send to device.** It lands in `/Libby/` and opens.
-
-## Fallback when Libby changes something
-
-The plugin's README is refreshingly direct about the risk:
-
-> *"Libby has no public API, so this can break when they change things."*
-
-Manual route, which does not depend on Libby's internals: in Libby choose
-**Read With… → Other Options → EPUB** to download an `.acsm`, upload it with the
-File Manager, then use **Fetch selected book** at the bottom of the card.
-
-## What it talks to
-
-Hosts extracted from `plugin.js`:
-
-```
-libbyapp.com · sentry.libbyapp.com · dtsbytebooks.com
-adeactivate.adobe.com · ns.adobe.com
-```
-
-Device APIs used: `api.relay` ×2, `api.crypto` ×1, `api.fetchToSd` ×3,
-`api.writeFile` ×4, `api.registerAction` ×2.
-
-So it is an **Adobe ADEPT flow brokered through ByteBooks**: ByteBooks supplies
-the account, `adeactivate.adobe.com` does the device activation, Libby supplies
-the loan, and the book streams to SD via `fetchToSd` — **book bytes never pass
-through the browser page**.
-
-## The eight-step procedure
-
-> ⚠ **This is a map, not a tested recipe.** It is reconstructed from source,
-> READMEs and catalog metadata. **Nobody in this project has a PaperMono, an
-> Adobe ID, or a library loan** — no step below has been executed. Expect to
-> debug.
-
-### 1 — build and flash the plugin branch
-
-```bash
-git clone --recurse-submodules https://github.com/crosspoint-reader/crosspoint-reader
-cd crosspoint-reader
-git checkout feat-sd-plugins          # 66 commits ahead of develop, 0 behind
-pio run -e papermono -t upload        # or x4pro / x4c / sticky / default
-```
-
-`feat-sd-plugins` @ `3657026e` (tip 2026-09-10) contains **all** of `develop`
-plus 66 commits — a clean fast-forward, not a divergent branch.
-
-**Verify before continuing:** request `GET /api/plugins` from the device web UI.
-It should return a JSON array. A 404 means you are on the wrong firmware.
-
-### 2 — install the plugin store
-
-Download `plugin-store.zip` from the `itsthisjustin/sd-plugins` releases and
-**unzip at the root of the SD card**. By hand instead, copy the folder to any of
-these — **first match wins**:
-
-```
-/.crosspoint/plugins/plugin-store/
-/plugins/plugin-store/
-/.plugins/plugin-store/
-```
-
-each containing `manifest.json`, `plugin.js`, `device.json`.
-
-The store appears under **Settings** in the web UI, and on the reader itself at
-**Settings ▸ System ▸ Plugins**. Its default catalog is preconfigured to
-`raw.githubusercontent.com/itsthisjustin/sd-plugins/refs/heads/main/catalog.json`;
-your catalog list persists at `/.crosspoint/plugin-store.json`.
-
-### 3 — prove the plumbing *before* touching DRM
-
-**Skipping this is how people end up debugging three things at once.**
-
-1. Install **`hello`** — proves the loader works end to end, no network.
-2. Install **`webdav`** or **`wallabag`** — proves `relay`, `fetchToSd` and
-   credential storage all work.
-
-Only once a non-DRM plugin has downloaded a real book should you continue.
-
-### 4 — install `protected-content`
-
-Listed as *"Protected Content — Fulfill protected content from an online
-provider"*, v1.0.4, by `Diirge`. It mounts on **`files`**, so it appears in the
-**File Manager**, not Settings.
-
-> ⚠ **Know what you are installing.** Unlike every other plugin in the catalog,
-> its files are not served from GitHub — `base` is
-> `https://protected-content-host-production.up.railway.app/`. **No git history,
-> no licence, no README, no review.** Two files: `manifest.json` (170 B) and
-> `plugin.js` (53,887 B).
->
-> The sd-plugins repo never mentions "libby" — this plugin is generic ADEPT.
-
-**Alternative worth considering:** `ruqqq/crosspoint-plugins`' `libby` bundles
-the same ADEPT engine (71 % identical code, by its own admission) and needs
-**neither** `protected-content` **nor** the Railway host. See the
-[plugin source survey](plugin-source-survey.md).
-
-### 5 — activate against Adobe
-
-Standard ADEPT device activation, entirely in the browser:
-
-| Phase | What happens | Device API |
-|---|---|---|
-| Keypair | RSA keypair generated | `crypto keygen` |
-| Sign | Activation request signed | `crypto sign` |
-| Exchange | Talks to `adeactivate.adobe.com/adept` | `relay` (CORS) |
-| Store | PKCS#12 credential written | `plugin-fs` → `/.crosspoint/content.key` |
-| State | Activation record written | `plugin-fs` → `/.crosspoint/content-activation.json` |
-
-It presents as Adobe Digital Editions **`10.0.4`** (the `HOBBES` constant).
-
-**This consumes one of your account's activation slots** — the limit is 10.
-Deactivate an old device via ADE or the vendor's site if you run out. Note the
-account is now a **ByteBooks ID**, not an Adobe ID; see the
-[ByteBooks review](dtsbytebooks-review.md).
-
-### 6 — get an ACSM out of Libby
-
-**The step most people get wrong.** When borrowing, choose the **EPUB download
-for Adobe Digital Editions** — *not* "Read in browser", "Read with Kindle" or
-"Listen". You should get a small **`.acsm`** file: a few KB of XML, a fulfilment
-*token*, not the book.
-
-**Not every title offers this.** Publishers choose formats; some are Kindle-only
-or browser-only. If there is no Adobe/EPUB option, **this path cannot work for
-that title** — and no amount of debugging will change that.
-
-### 7 — fulfil
-
-Put the `.acsm` where the plugin can reach it (the File Manager is its mount, so
-the current folder is natural) and run the fulfil action.
-
-1. ADEPT fulfilment exchange with the content server, via `relay`
-2. The real EPUB streams **straight to SD** via `fetchToSd` — the browser never
-   holds book bytes, which is also how it avoids the 32 KB relay cap
-3. A **`<book>.epub.rights`** sidecar is written beside it
-
-### 8 — read it
-
-The EPUB on disk stays **byte-identical to what the server sent**. Decryption
-happens per zip entry at read time, against `/.crosspoint/content.key`. If the
-book refuses to open, the firmware's error strings are specific and worth
-knowing: **`"loan date unverified"`** means no trustworthy clock, and
-**`"access expired"`** means the loan is over. See
-[the ContentProtection library](../../../frameworks/freeink-sdk/contentprotection-library.md).
-
-## Limits, stated by the plugin itself
-
-- **Ebooks only.** Audiobooks and magazines are unsupported. Titles Libby only
-  offers in its own web reader *"can't be sent to a device by any app"*.
-- **The book stays protected on the SD card.** It is unlocked in memory only
-  while being read, and **stops opening when the loan ends**. Returning or
-  deleting it is your job.
-- A few titles are publisher-DRM-free; those download directly with no expiry
-  beyond the loan.
-- **Both the Libby link and the content credential live on the SD card** — treat
-  the card as sensitive.
-
-**Unlink:** tap **Unlink**, or delete `/.crosspoint/libby.json`. To drop the
-content account too, delete `/.crosspoint/content.key`.
-
-## How this differs from `protected-content`
-
-Both end in an ADEPT-fulfilled book, by different routes:
-
-| | `protected-content` (Diirge) | `libby` (ruqqq) |
-|---|---|---|
-| Account | Adobe ID, direct | **DTS ByteBooks** |
-| Input | an `.acsm` you supply | **your live Libby loan list** |
-| Hosting | **off-GitHub**, Railway, unlicensed | GitHub, in-repo |
-| Scope | any ADEPT provider | Libby specifically |
-| Dependency | standalone | standalone |
-
-The removed `libby` 0.2.0 *required* `protected-content`; ruqqq's 1.0.2 does not.
-
-## Legal framing
-
-This is a **licensed ADEPT client reading a legitimately borrowed loan** — the
-role Adobe Digital Editions or a Kobo plays. The DRM is honoured, not removed:
-the file stays encrypted on disk and stops opening at loan end. That is
-categorically different from DRM *stripping* (DeDRM and similar), which is
-restricted in many jurisdictions.
-
-The plugin states it is *"not affiliated with or endorsed by Libby, OverDrive,
-Adobe, or ByteBooks."* Using an unofficial client against an API with no public
-contract may breach those services' terms — a separate question from copyright,
-and one this record does not answer.
-
-## Trust and provenance — read before installing
-
-- **`ruqqq/crosspoint-plugins` has no `LICENSE` file.** ★0, created 2026-08-17,
-  last pushed **2026-08-18** — so the working Libby plugin sits in a
-  three-week-untouched, unlicensed repository.
-- **`itsthisjustin/sd-plugins` also has no licence**, and its
-  `protected-content` is hosted **off-GitHub on Railway** with no source history.
-- **Plugins are not sandboxed.** Upstream says so plainly: they load into the
-  page, *"not an isolated iframe"*, with the full authority of the web UI — which
-  has **no authentication**. A plugin can read other plugins' credentials on SD.
-
-You are entering library-card-adjacent and Adobe-account credentials into
-unlicensed third-party JavaScript. That may well be fine; it should be a decision,
-not an accident.
-
-## Checklist
-
-1. Build and flash from **`feat-sd-plugins`** (confirm `[env:papermono]` if relevant).
-2. Verify the API is live: `GET /api/plugins` on the device web UI.
-3. Install `plugin-store` from the release zip at the SD root.
-4. Prove the loader with `hello`.
-5. Add ruqqq's catalogue URL as a store; install `libby` **1.0.2**.
-6. Register at `dtsbytebooks.com`, activate the device, link Libby.
-7. **Do not** install `libby` from `pagdot`/`marczykm`/`dezren39`/`josmerod` — dead URL.
-
-## Open questions
-
-- **Nothing was installed or run.** No device, no ByteBooks account, no loan.
-- `plugin.js` (64,847 B) was fetched; **hosts and API calls were extracted, but
-  the fulfilment logic was not audited line by line.**
-- **Why `libby` was removed from `itsthisjustin/sd-plugins` is unknown** — no
-  commit history is returned for the path. Whether it was withdrawn, rewritten
-  out, or never on `main` is unestablished.
-- What DTS ByteBooks actually is — an Adobe-licensed fulfilment reseller is the
-  obvious reading, **not verified**.
-- Whether `ContentProtection.cpp` handles loan expiry gracefully was not examined.
-
-## Sources
-
-All 2026-09-11, `executed-success`: catalogue JSON from `itsthisjustin`,
-`ruqqq`, and eight forks; HTTP probes of `itsthisjustin/.../libby/*` (404) and
-`ruqqq/.../libby/*` (200); `manifest.json`, `README.md` and `plugin.js` of
-ruqqq's libby 1.0.2; `git grep` of `feat-sd-plugins` for the API surface.
diff --git a/software/applications/crosspoint-reader/plugins/papermono-plugin-branch-notes.md b/software/applications/crosspoint-reader/plugins/papermono-plugin-branch-notes.md
deleted file mode 100644
index 94d1224..0000000
--- a/software/applications/crosspoint-reader/plugins/papermono-plugin-branch-notes.md
+++ /dev/null
@@ -1,158 +0,0 @@
-# Running the plugin branch on a PaperMono — working notes
-
-> Separate from the Libby/store documentation: this is what is known, and what is
-> unknown, about getting **`feat-sd-plugins` firmware onto an M5Stack PaperMono**.
->
-> Compiled **2026-09-11**. Branch and source facts are `executed-success`
-> (`git grep`/`git show` against the fetched branch). **Nothing was built for
-> PaperMono and nothing was flashed** — there is no hardware. Everything
-> operational below is `inferred` or `reported-working`.
-
-## The good news
-
-**`feat-sd-plugins` already carries `[env:papermono]`.** Confirmed by
-`git show origin/feat-sd-plugins:platformio.ini` — the env list is:
-
-```
-default · gh_release · gh_release_rc · slim
-sticky · sticky-gh_release · sticky-gh_release_rc
-x4pro · x4c · x4c-gh_release · x4pro-gh_release · x4pro-gh_release_rc
-papermono        ← present
-```
-
-and the file carries the comment `pio run -e papermono -t upload`.
-
-**The branch is not stale.** Against `develop`: **66 ahead, 0 behind**, tip
-**2026-09-10**. It contains everything in `develop` plus the plugin work, so it
-merges cleanly and is being actively developed.
-
-So in principle this is `pio run -e papermono` on that branch and nothing more.
-
-## What has actually been verified here
-
-| Claim | Status |
-|---|---|
-| `[env:papermono]` exists on `feat-sd-plugins` | **verified** — read from the branch |
-| Branch is 66 ahead / 0 behind `develop` | **verified** — `git rev-list --left-right --count` |
-| Plugin API endpoints exist on the branch | **verified** — `/api/plugins`, `/api/relay`, `/api/crypto`, `/api/fetch`, `/api/plugin-fs` in `CrossPointWebServer.cpp` |
-| `ContentProtection.cpp` exists (DRM read path) | **verified** — present in `lib/Epub/` |
-| **A PaperMono build of this branch compiles** | **NOT verified** |
-| **It runs on PaperMono hardware** | **NOT verified — no device** |
-| **Anyone has done this** | **no report found** |
-
-The gap between rows 4 and 5 is the whole risk.
-
-## What is known about building CrossPoint generally
-
-A **simulator** build of `develop` was completed successfully on this host —
-see [simulator build notes](../../../tooling/crosspoint-simulator-build-notes.md)
-— which establishes the toolchain works and documents seven portability fixes.
-That was `platform = native`, **not** an ESP32 target, so it does not validate a
-PaperMono firmware build.
-
-For a real device build the project ships a **Nix flake** at `nix/flake.nix`
-providing an FHS environment with PlatformIO (`pioarduino` fork, v6.1.19) and the
-runtime libraries its downloaded ESP32 toolchain needs. On NixOS that is the
-supported path:
-
-```bash
-cd crosspoint-reader
-git checkout feat-sd-plugins
-git submodule update --init --recursive        # freeink-sdk
-nix develop ./nix                               # or: nix-shell nix/shell.nix
-pio run -e papermono
-pio run -e papermono -t upload                  # per the file's own comment
-```
-
-`PLATFORMIO_CORE_DIR` is set to `$PROJECT_ROOT/.cache/platformio` by the flake,
-which keeps the toolchain download inside the checkout.
-
-**None of the above was executed.** It is read from `nix/flake.nix` and the
-`platformio.ini` comment.
-
-## Things that will probably bite, and why
-
-Drawn from the PaperMono device record and the SDK, so these are hardware facts
-rather than speculation — but their interaction with *this branch* is untested.
-
-**Octal PSRAM is mandatory.** M5GFX aborts display init with
-`"M5PaperMono need OPI-PSRAM enabled"`. A misconfigured build presents as a blank
-screen on working hardware with one easily-missed log line. Check
-`board_build.arduino.memory_type` in the papermono env before blaming hardware.
-
-**The render task stack.** The independent porter of CrossPlay to PaperMono
-(`fperuzzo72/crossplay-papermono`, 2026-09-11) needed a commit
-*"give the render task the same 16384 stack the x4pro render task uses"*. That is
-a different codebase, but it is the same panel size and the same SoC — if the
-display crashes or renders partially, stack size is the first thing to check.
-
-**Download mode is not a button.** The M5PM1 power-management MCU owns reset and
-the boot straps. Hold the power button ~2 s until the red LED blinks. Standard
-esptool auto-reset assumptions may not apply.
-
-**No OTA slot in the stock partition layout.** The vendor's factory image uses a
-single ~15 MiB `factory` app with no OTA partition. If the branch's updater
-expects OTA, the partition table needs attention — note that
-`fperuzzo72` also needed *"publish the release asset its updater asks for"* and
-*"point the update check at this fork's releases"*.
-
-**The shared I²C bus is busy.** RTC `0x32`, touch `0x38`, expander `0x4F`, IMU
-`0x68`, PMIC `0x6E`, and a charger at `0x75` that is normally gated **off** the
-bus. `ciniml/paper_name_plate` needed a commit *"Recover from a flaky I2C bus at
-boot: retry IOE1 EPD power-on"* — independent evidence that bus bring-up on this
-board needs to be defensive.
-
-## Plugin-specific considerations on this board
-
-**The web server is the plugin runtime.** Plugins are browser JavaScript served
-by the device; they need the reader on a network. Use
-**File Transfer → Join Network** (not Hotspot) or nothing with an outbound
-dependency will work.
-
-**Wi-Fi and the e-paper refresh contend for time and power.** Not measured, and
-no power figure exists for this board from any source — but a plugin doing
-`fetchToSd` of a multi-megabyte EPUB while the panel refreshes is the obvious
-first place to look for instability.
-
-**PSRAM matters here too.** The relay has a 32 KB response cap and `fetch`
-segments at 4 MB; on a 8 MB-PSRAM part that is comfortable, but it is worth
-knowing the caps exist before diagnosing a stall as a device fault. See
-[sd-plugins](sd-plugins-and-protected-content.md).
-
-## Prior art worth reading first
-
-| Project | Why |
-|---|---|
-| [`fperuzzo72/crossplay-papermono`](https://github.com/fperuzzo72/crossplay-papermono) | **The only known in-progress PaperMono bring-up of a CrossPoint-family firmware.** Branch `papermono-bringup`, started 2026-09-11. Its commits are effectively a checklist |
-| [`ciniml/paper_name_plate`](https://github.com/ciniml/paper_name_plate) | Independent Rust firmware; its `DESIGN.md` is the best third-party PaperMono hardware writeup and confirms the pin map |
-| `m5stack/M5PaperMono-UserDemo` | Vendor reference — the only artifact exercising NFC, LoRa, IMU, RTC, PDM and the power path together |
-
-## Honest summary
-
-Building `feat-sd-plugins` for PaperMono **looks like a one-line operation and
-probably is not**. The env exists, the branch is healthy, and the hardware is
-well understood — but nobody has reported doing it, nothing here was compiled for
-the target, and the one person publicly porting an adjacent CrossPoint fork to
-this board needed several non-obvious fixes (stack size, release assets, updater
-URL) within his first day.
-
-Expect a short list of small problems rather than one large one, and check the
-display path first.
-
-## Open questions
-
-- **Does `pio run -e papermono` succeed on `feat-sd-plugins` today?** Unknown.
-  This is the single cheapest thing anyone with the repo could resolve.
-- Does the papermono env on that branch differ from the one on `develop`?
-  Not diffed.
-- Does the plugin web server behave on this board's Wi-Fi + e-paper combination?
-  Untested.
-- Is there an OTA partition in the branch's papermono partition table? Not checked.
-- Has anyone run *any* CrossPoint build on a PaperMono? **No report found.**
-
-## See also
-
-- [The Libby path](libby-path.md) · [SD-card plugins](sd-plugins-and-protected-content.md)
-- [PaperMono device record](../../../../devices/m5stack/papermono/README.md) · [development](../../../../devices/m5stack/papermono/development.md)
-- [Simulator build notes](../../../tooling/crosspoint-simulator-build-notes.md) — the one build that *was* completed
-- [New PaperMono projects](../../../ecosystems/crosspoint-freeink/new-papermono-projects-2026-09.md)
diff --git a/software/applications/crosspoint-reader/plugins/plugin-architecture.md b/software/applications/crosspoint-reader/plugins/plugin-architecture.md
deleted file mode 100644
index 5da6c23..0000000
--- a/software/applications/crosspoint-reader/plugins/plugin-architecture.md
+++ /dev/null
@@ -1,369 +0,0 @@
-# CrossPoint plugin architecture — how it actually works
-
-> What the plugin system is, whether it really works, what it can and cannot do,
-> and — the practical question — **what you can add without touching firmware and
-> what forces a fork.**
->
-> Read from the plugin host source, the store, and five shipped plugins on
-> **2026-09-11**. Source reads are `executed-success`. **Nothing was installed,
-> flashed or run**; behaviour is `inferred` from source and from plugin authors'
-> reports, which are attributed where they matter.
->
-> This is a design review, **not a security audit**.
-
-## There are two plugin systems, and confusing them wastes days
-
-| | **Browser plugin** (`plugin.js`) | **On-device UI** (`device.json`) |
-|---|---|---|
-| Runs where | In a page in **your browser**, talking to the device | On the **device**, rendered on e-paper |
-| Language | JavaScript, arbitrary | **JSON only** — no code |
-| Interpreted by | The page's plugin host | The **firmware** |
-| Needs a browser? | **Yes, always** | **No** |
-| Can do crypto? | Yes, via `/api/crypto` | No |
-| Typical use | Account linking, DRM fulfilment, anything complex | Browse a feed, download a file |
-
-A plugin folder can ship **both**, and the good ones do: `readeck` uses
-`plugin.js` for setup and `device.json` for day-to-day browsing on the device.
-They are complementary, not alternatives.
-
-**Both live on the SD card. Adding either needs no firmware change** — that is
-the entire point of the design.
-
-## Part 1 — the browser plugin host
-
-### Discovery and loading
-
-```js
-// 1. host asks the device what's installed
-list = await (await fetch('/api/plugins')).json();     // [{name, mount, title}, …]
-
-// 2. for each plugin matching this page's mount, inject its script
-s.src = '/plugin?name=' + encodeURIComponent(p.name) + '&file=plugin.js';
-
-// 3. the script calls registerPlugin(fn); the host then invokes it
-CrossPoint._pending(container, { name, relay, crypto, writeFile,
-                                 fetchToSd, registerAction, pluginFile });
-```
-
-A plugin is a single file that calls `CrossPoint.registerPlugin(fn)`. The host
-hands it a DOM container and an API object **pre-bound to that plugin's name** —
-so the device knows which plugin made each call.
-
-### `mount` decides which page loads it
-
-| `mount` | Loaded by |
-|---|---|
-| `settings` (default) | the Settings page |
-| `files` | the File Manager |
-| *(null filter)* | the **headless `/plugins-run` page**, which loads **everything** |
-
-### The API surface — six functions, and that's all
-
-| Function | Endpoint | What it's for |
-|---|---|---|
-| `relay(method, url, headers, body)` | `/api/relay` | Outbound HTTP the browser can't make (CORS) |
-| `crypto(op, fields)` | `/api/crypto` | wolfSSL primitives |
-| `writeFile(path, dataB64)` | `/api/plugin-fs` | Write a small file to SD |
-| `fetchToSd(url, dest, headers)` | `/api/fetch` | Stream a URL **straight to SD** |
-| `registerAction(action, fn)` | job queue | Expose a callable action to other plugins |
-| `pluginFile(f)` | — | URL for another file in your own plugin folder |
-
-Two details that matter when writing one:
-
-**`relay` preserves duplicate headers.** It resolves to
-`{status, body, headers}` where headers is an **ordered list of `[name, value]`
-pairs** — so every `Set-Cookie` survives. Most naive relay designs lose these.
-
-**`writeFile` decodes base64 in the browser** and posts binary
-(`application/octet-stream`), specifically so embedded NULs survive. You pass
-base64; the wire carries bytes.
-
-### The job queue is the most interesting part
-
-This is how one plugin calls another, and it explains an otherwise baffling
-design choice.
-
-```js
-registerAction(pluginName, action, fn) {
-  (this._actions[pluginName] = this._actions[pluginName] || {})[action] = fn;
-  if (!this._actionTimer) this._actionTimer = setInterval(() => this._pollJobs(), 2500);
-}
-```
-
-Registering an action starts a **2.5-second poll**. Jobs are enqueued externally
-via `POST /api/plugin-jobs`, then:
-
-1. `GET /api/plugin-jobs/claim?plugin=X` — any page hosting that plugin claims it
-2. the registered `fn(job.args)` runs
-3. `POST /api/plugin-jobs/complete {id, ok, result}` — the caller polls for this
-
-**Completion is retried before new work is claimed** (`_pendingCompletion` is
-posted first on the next tick if it failed), so a dropped result isn't silently
-lost.
-
-**Why it exists:** it lets `libby` hand a fulfilment token to `protected-content`
-without either plugin importing the other. The DRM engine stays in one plugin;
-the Libby API layer stays thin. `libby`'s own header says exactly that.
-
-**Why it constrains you:** a job only runs **while some page hosting that plugin
-is open in a browser.** The `/plugins-run` page exists to be that page — but it
-is still a browser page on a computer. **There is no background execution on the
-device.**
-
-### `fetchToSd` segments at 2 MB — client-side
-
-```js
-const maxBytes = 2 * 1024 * 1024;
-let offset = 0;
-for (;;) {
-  const result = await this._post('/api/fetch', { plugin, url, dest, headers, offset, maxBytes });
-  if (result.complete !== false) return result;
-  if (!Number.isFinite(result.bytes) || result.bytes <= offset) throw new Error('/api/fetch made no progress');
-  offset = result.bytes;
-}
-```
-
-The comment gives the reason, and it is not what you'd guess: *"Mobile browsers
-may terminate a request after a few minutes even when response heartbeats are
-flowing, while the device itself is still downloading successfully."*
-
-**This resolves a discrepancy in prior research.** A firmware constant
-`FETCH_MAX_SEGMENT_SIZE = 4 MB` was recorded alongside observed 2 MB segments and
-marked unresolved. They are different things: **2 MB is what the browser
-requests; 4 MB is the firmware's ceiling on that request.** Not a contradiction.
-
-**The consequence is real though:** any file over 2 MB **always** needs a second,
-offset-based call. If the firmware issues a `Range` request for that and the
-server doesn't support ranges, the download fails deterministically — and
-retrying cannot help, because every attempt crosses the same point. Plugin
-authors have described this as a "numbers game" mitigation with retry counts;
-**if the mechanism is as described, retries are futile for that case.** The
-`/api/fetch` handler was not captured, so whether it sends `Range` on `offset > 0`
-is **unverified**.
-
-## Part 2 — `device.json`, the declarative on-device UI
-
-No JavaScript. The firmware reads this and renders a browsable list on the
-e-paper. Real example, shipped:
-
-```json
-{
-  "token":  { "file": "/.crosspoint/readeck.json", "path": "token" },
-  "config": { "file": "/.crosspoint/readeck.json" },
-  "browse": {
-    "format": "json",
-    "url": "{cfg.url}/api/bookmarks?is_archived=false&sort=-created&limit=16",
-    "headers": { "Authorization": "Bearer {token}" },
-    "items": "",
-    "fields": { "title": "title", "id": "id" },
-    "page_size": 16,
-    "lists":  [ { "title": "Unread" },
-                { "title": "Favorites", "url": "…is_marked=true…" } ],
-    "search": { "url": "…search={query}…" }
-  },
-  "download": {
-    "url": "{cfg.url}/api/bookmarks/{id}/article.epub",
-    "dest_dir": "/Readeck",
-    "filename": "{title}.epub"
-  }
-}
-```
-
-Template variables: `{cfg.*}` from the config file, `{token}`, `{id}`, `{title}`,
-`{query}`, `{page}`.
-
-### The template engine does substitution, not arithmetic
-
-`{page}` is a **counter**, and there is no way to compute `offset = page × size`.
-That single limitation shapes every `device.json` you will write.
-
-Readeck's workaround is instructive: it **hardcodes `limit=16`** rather than
-using a `{limit}` template, so the firmware's "+1 lookahead" probe never returns
-an extra row and the device concludes there is no next page. Pagination is
-effectively disabled in exchange for a list that works. That is the level of
-cleverness the engine currently demands.
-
-## The known plugin population — 11, across three stores
-
-Merged from the captured catalogs on 2026-09-11. **None of these were installed
-or run**; this is a roster from `catalog.json` plus source headers.
-
-### `itsthisjustin/sd-plugins` — 8 plugins (★36, 10 forks, pushed 2026-09-10)
-
-| Plugin | v | Mount | What it does |
-|---|---|---|---|
-| `plugin-store` | 1.1.2 | settings | **Installs other plugins from hosted catalogs** — the bootstrap |
-| `bookfusion` | 1.2.0 | settings | BookFusion library; device-code + QR sign-in; writes `<book>.meta.json` that rides KOSync progress uploads |
-| `webdav` | 1.0.0 | settings | Nextcloud / ownCloud / Seafile / Koofr; credentials in `/.crosspoint/webdav.json` |
-| `wallabag` | 1.2.0 | settings | Read-it-later articles as EPUB, OAuth2 password grant; self-hosted or `app.wallabag.it` |
-| `dictionaries` | 1.0.0 | settings | ~20 offline StarDict dictionaries (Wiktionary + Webster's 1913); sets `dictionaryName` |
-| `organize-by-author` | 1.0.0 | **files** | Sorts EPUBs into per-author folders; EPUB 2 + 3 creator sort-names; **moves progress, cache and sidecars with the book** |
-| `hello` | 1.0.0 | files | Minimal loader example — **start here** |
-| `protected-content` | 1.0.4 | files | ADEPT fulfilment |
-
-### `ruqqq/crosspoint-plugins` — a second store, 2 plugins
-
-| Plugin | v | Mount | What it does |
-|---|---|---|---|
-| `libby` | 1.0.2 | files | Libby loans, self-contained ADEPT |
-| `kopi` | 1.2.0 | **settings** | **OPDS** feed reader — lists issues newest-first, downloads to SD |
-
-### Off-catalog
-
-| Plugin | Where | Note |
-|---|---|---|
-| `readeck` | never upstream | `plugin.js` **+ `device.json` v1.4.0** — the reference for on-device UI |
-| `libby` (josmerod) | **deleted upstream**, alive in 5 forks | The independent implementation; hands `.acsm` to `protected-content` |
-
-### What the roster tells you
-
-- **`hello` is the actual starting point** for a new plugin — a minimal loader
-  example, MIT-adjacent in spirit but see the licence caveat below.
-- **`kopi` proves the OPDS path.** It is a template for Calibre-Web, Kavita or
-  Komga, not a single-vendor integration.
-- **`organize-by-author` is the only plugin that mutates the library**, and
-  notably it moves progress/cache sidecars with the book — worth reading before
-  writing anything that touches user files.
-- **A store is just a repo with a `catalog.json`.** Three exist, all on the same
-  schema, two of them built independently — which is the strongest evidence that
-  the store protocol is genuinely reusable.
-
-> ⚠ **Licensing.** `itsthisjustin/sd-plugins` has **no licence**;
-> `ruqqq/crosspoint-plugins` has **no licence**; `protected-content` has no
-> licence and lives in **no git repository**. All-rights-reserved by default.
-> Read for technique; do not copy.
-
-## Does it really work?
-
-**Yes — with the caveat that I verified none of it on hardware.** The evidence is
-that multiple independent authors have shipped non-trivial things on it:
-
-| Plugin | Author | What it proves |
-|---|---|---|
-| `protected-content` | Diirge | A **full Adobe ADEPT client** runs in this model — RSA keygen, signing, PKCS#12, AES unwrap |
-| `readeck` | Diirge | `device.json` browse+download **shipped in v1.4.0**, with on-device UI |
-| `libby` (josmerod) | — | **Cross-plugin RPC** via the job queue works as designed |
-| `libby` (ruqqq) | ruqqq | Same flow, self-contained — **and the only tested code, 26 cases** |
-| `kopi` | ruqqq | **OPDS** — so any OPDS server (Calibre-Web, Kavita, Komga) is reachable |
-
-Three plugin **stores** exist (`itsthisjustin/sd-plugins`, `ruqqq`'s, and the
-bundled one), all using the same catalog schema. A store is just a repo with a
-`catalog.json`.
-
-**The honest counterweight:** the firmware branch is `feat-sd-plugins`, which is
-**66 commits ahead of `develop` and 0 behind** as of 2026-09-10 — a clean
-fast-forward, actively developed, but **not merged**. This is not a dormant
-roadmap item; neither is it shipped to everyone.
-
-## What it can't do
-
-| Limit | Value | Notes |
-|---|---|---|
-| Relay response | **32 KB** | **Behaviour on overflow is disputed — see below** |
-| Fetch segment | 2 MB client / 4 MB firmware ceiling | Files >2 MB always need a second call |
-| Manifest | 8 KB | |
-| Redirects | **not followed** | Resolve them yourself, or relay each hop |
-| Archives | **no extraction** | No unzip on device |
-| Background work | **none** | A browser page must be open for actions to run |
-| Sandbox | **none** | Plugins share the page's full authority |
-
-### The 32 KB relay cap: four sources, four different behaviours
-
-This matters because it decides how you write every plugin, and **there is no
-captured firmware evidence for any of it**:
-
-| Source | Claimed behaviour | Basis |
-|---|---|---|
-| Prior firmware read | HTTP **413** *"response too large, use /api/fetch"* | Read of `RELAY_BODY_LIMIT` — **handler not captured** |
-| `readeck/IDEAS.md` | **`abort()`s the device** | Real-device crash; author hedges *"appears to"*; dump not captured |
-| `libby` (josmerod) | **silently truncates** | Header comment |
-| `libby` (ruqqq) | returns a **200 with an `error` body** | What their code handles |
-
-ruqqq's case deserves a note, because prior research cited it as corroboration
-for the 413: it isn't. Their only evidence is **a mock in their own test suite**,
-and the shape they handle — `if (!r.error) return r;` — can only fire on a
-resolved 2xx whose body carries `error`. A real HTTP 413 would **throw** in
-`_readResponse` before reaching it. Their code encodes a *third* belief, not
-support for the first.
-
-**Practical guidance regardless:** keep relayed responses small, page
-aggressively (`readeck` ships `PAGE_SIZE = 5`), and use `fetchToSd` for anything
-large — it has no cap.
-
-## What's easy to add, and what needs a fork
-
-This is the question worth answering, so it is worth being specific.
-
-### Easy — no firmware change, hours not weeks
-
-| You want | How |
-|---|---|
-| **Any HTTP+JSON catalogue on the device** | `device.json` alone. No JS |
-| **Any OPDS server** — Calibre-Web, Kavita, Komga | `kopi` is a working template; change the base URL |
-| **A new content source with login** | `plugin.js` for auth + `writeFile` the token; `device.json` reads it back via `token.file`/`token.path` |
-| **Serious crypto** | `/api/crypto` already exposes keygen, sign, pubencrypt, AES, PKCS#12, SHA-1/256, random — enough for a full ADEPT client, as proven |
-| **Your own plugin store** | A GitHub repo with a `catalog.json`. Two independent people have done it |
-| **Cross-plugin calls** | `registerAction` + the job queue |
-
-The gating skill is **JavaScript and an API you can reach over HTTP**, not
-embedded development. That is a genuinely low bar and it is the design's main
-achievement.
-
-### Requires a firmware fork
-
-| You want | Why it's blocked |
-|---|---|
-| **A crypto op that isn't in the list** | The op set is firmware-side |
-| **Relay responses over 32 KB** | `RELAY_BODY_LIMIT` is a firmware constant |
-| **Redirect following** | Not implemented in the relay |
-| **Unzip / archive extraction** | No extractor on device |
-| **Arithmetic in `device.json`** (real pagination) | The template engine substitutes only |
-| **Anything running with no browser open** | There is no on-device JS engine — the host *is* the browser |
-| **A new mount point** | The pages that load plugins are firmware |
-| **Sandboxing plugins from each other** | Would require an isolation model that doesn't exist |
-
-**The sharpest line:** anything expressible as *"make HTTP calls, do crypto, write
-files, render a list"* is a config or a small JS file. Anything requiring the
-**device to act on its own**, or requiring a **new capability from the firmware**,
-is a fork.
-
-### The architectural ceiling
-
-The system deliberately puts **no scheme-specific knowledge in the firmware**.
-The firmware's DRM glue comment says it outright: *"Generic path — the reader
-carries no scheme name."* All Adobe-specific logic lives in an off-repo plugin.
-
-That is a clean, consistent decision with an obvious consequence: **the device
-can only do what a browser page, connected to it, tells it to do right now.**
-Everything else is a fork.
-
-## Practical notes for writing one
-
-- **Page small.** The relay cap is the most common failure and the least
-  gracefully handled.
-- **Use `fetchToSd` for content**, always — no cap, and book bytes never pass
-  through the page.
-- **Expect files >2 MB to need a Range-capable server.**
-- **`device.json` first** if your source is a plain JSON API — it gets you an
-  on-device UI for free, and no JS to maintain.
-- **Ship both**: `plugin.js` for setup, `device.json` for daily use.
-- **Copy ruqqq's error handling.** Catching the relay error and telling the user
-  *what to do about it* is the only example of that discipline in the ecosystem.
-
-## What was not established
-
-- **No plugin was installed or run.** Every behavioural claim is from source or
-  from an author's report.
-- **The firmware handlers for `/api/relay`, `/api/fetch` and `/api/plugin-fs` were
-  not captured** — so all limits, the 413 path, and Range behaviour are
-  second-hand.
-- **Which branch upstream intends to merge is unknown.**
-- Plugin **licensing is largely absent** across the ecosystem — see the
-  [plugin source survey](plugin-source-survey.md).
-
-## See also
-
-- [Plugin source survey](plugin-source-survey.md) — what the DRM plugins are, and their shared lineage
-- [The ContentProtection library](../../../frameworks/freeink-sdk/contentprotection-library.md) — the firmware half of the DRM chain
-- [`dtsbytebooks.com` review](dtsbytebooks-review.md) — who operates ADEPT now
-- [SD plugins and protected content](sd-plugins-and-protected-content.md) — the store protocol and plugin roster
diff --git a/software/applications/crosspoint-reader/plugins/plugin-source-survey.md b/software/applications/crosspoint-reader/plugins/plugin-source-survey.md
deleted file mode 100644
index ca1fc5c..0000000
--- a/software/applications/crosspoint-reader/plugins/plugin-source-survey.md
+++ /dev/null
@@ -1,227 +0,0 @@
-# `protected-content` and `libby` — plugin source survey
-
-> A brief structural survey of the two DRM-fulfilment plugins. **Not a security
-> audit**: this establishes what they are, what they touch, and how they relate.
-> Line-by-line logic was **not** reviewed.
->
-> Surveyed **2026-09-11** from archived copies. `executed-success` for the
-> measurements below; behavioural claims are `inferred`. **Neither plugin was
-> installed or run**, and no account or loan was used.
-
-| | `protected-content` | `libby` |
-|---|---|---|
-| Author | Diirge | ruqqq |
-| Version | 1.0.4 | 1.0.2 |
-| Size | 53,887 B · 1,133 lines | 64,847 B · 1,441 lines |
-| Mount | `files` | `files` |
-| Hosting | **Railway, off-GitHub** | `raw.githubusercontent.com` |
-| Licence | **none** | **none** |
-
-## There are THREE plugins here, not two — and the lineage is now settled
-
-A third artifact changes the picture: **josmerod's `libby`**, deleted from
-upstream `sd-plugins` but alive in five forks. Measuring identical substantive
-lines (>60 chars) across all three:
-
-| Pair | Identical lines | Share |
-|---|---|---|
-| josmerod `libby` ↔ ruqqq `libby` | **4** | **~2 %** |
-| josmerod `libby` ↔ `protected-content` | **4** | **~2 %** |
-| **ruqqq `libby` ↔ `protected-content`** | **225** | **71 %** |
-
-So there are **two independent codebases**, not three:
-
-1. **josmerod's `libby`** — genuinely independent. It *deliberately excludes* the
-   DRM crypto and hands `.acsm` files to `protected-content` over the job queue.
-   Its header: *"It deliberately does NOT contain the Adobe DRM crypto… That keeps
-   the crypto in one place and this plugin a thin Libby API layer."*
-2. **`protected-content` + ruqqq's `libby`** — one ADEPT engine, two wrappers.
-
-### ruqqq's plugin states its own derivation
-
-No inference needed — line 4 of `ruqqq/libby/plugin.js`:
-
-> *"**Derived from the Protected Content plugin, whose account activation and
-> fulfillment code is reused unchanged**; this adds the half that was missing —
-> getting the authorization file."*
-
-A prior analysis concluded ruqqq was an independent implementation partly because
-`grep protected-content` returned **0 hits**. The header says **"Protected
-Content"** — capitalised, with a space. A hyphen cost the finding.
-
-The 71 % figure and that sentence agree exactly: the ADEPT half is reused, the
-Libby half is new.
-
-### What's unique to `protected-content`
-
-**94 of its 319 substantive lines are absent from ruqqq's copy** — chiefly device
-activation, legacy-credential migration, and the manual `.acsm` upload path. So
-ruqqq's repo does *not* fully subsume it.
-
-This matters for preservation: `protected-content` exists in **no git
-repository**, only on a Railway host. Its ADEPT engine now survives inside
-ruqqq's repo, but **that ~29 % does not**.
-
-### Practical consequence
-
-Two genuinely different routes exist, and the difference is architectural rather
-than cosmetic:
-
-| | josmerod `libby` | ruqqq `libby` |
-|---|---|---|
-| Plugins needed | `libby` **+** `protected-content` | **`libby` alone** |
-| DRM engine | separate plugin, **Railway-hosted, in no repo** | **in-plugin** |
-| Served from | Railway PaaS | GitHub raw |
-| Tests | none | **26 cases** |
-
-If you are choosing today, ruqqq's has no single-point-of-failure on a free-tier
-PaaS host. That argument stands independently of code quality.
-
-## Identical capability surface
-
-Both request exactly the same eight `/api/crypto` operations:
-
-```
-keygen · sign · pubencrypt · aesenc · aesdec · pkcs12 · sha1 · random
-```
-
-That is the ADEPT primitive set: RSA keygen and signing for device activation,
-PKCS#12 for the credential container, AES for content-key unwrap, SHA-1 because
-ADEPT still specifies it.
-
-Device API usage is near-identical too:
-
-| API | `protected-content` | `libby` |
-|---|---|---|
-| `api.relay` | 2 | 2 |
-| `api.crypto` | 1 | 1 |
-| `api.fetchToSd` | 1 | **3** |
-| `api.writeFile` | 3 | **4** |
-| `api.registerAction` | 3 | 2 |
-
-`libby`'s extra `fetchToSd`/`writeFile` calls are consistent with it handling
-multiple loans and persisting a loan list.
-
-## Files written to SD
-
-| Path | Written by | Contents |
-|---|---|---|
-| `/.crosspoint/content.key` | both | the ADEPT device credential (PKCS#12) |
-| `/.crosspoint/content-activation.json` | `protected-content` | activation record |
-| `/.crosspoint/libby.json` | `libby` | the Libby link |
-| `/Libby/` | `libby` | fulfilled books |
-
-**Both write the same credential path**, so the two plugins share device
-activation — installing one and then the other should not require re-activating.
-`inferred` from the path constant, not tested.
-
-## Correction — an earlier version of this page was wrong
-
-**An earlier revision of this document claimed both plugins call
-`dtsbytebooks.com/api/v1/register`, `/api/v1/login` and `/api/fulfill`, and that
-ByteBooks was "the load-bearing third party" through which fulfilment is routed.
-That was false, and it is retracted.**
-
-Re-checked directly against both archived sources on 2026-09-11:
-
-```
-$ grep -c dtsbytebooks plugin.js
-1                      # protected-content  (line 892)
-1                      # libby              (line 1173)
-
-$ grep -n dtsbytebooks plugin.js
-892:  '<a href="https://dtsbytebooks.com/register" target="_blank" …
-```
-
-**`dtsbytebooks.com` appears exactly once in each plugin, as a hyperlink in the
-UI telling the user where to create an account.** No code path fetches it. Those
-`/api/v1/*` endpoints do not exist — the paths return the site's single-page-app
-shell.
-
-Every network constant in either plugin:
-
-| Plugin | Constant | Value |
-|---|---|---|
-| both | `ACS` | `https://adeactivate.adobe.com/adept` |
-| `libby` only | `LIBBY_BASE` | `https://sentry.libbyapp.com` |
-
-That is the complete list. **All ADEPT protocol traffic goes to Adobe's
-activation host**; `libby` additionally calls OverDrive's API. The original
-distinction this page "corrected" — `protected-content` talks to Adobe directly —
-was closer to right than the correction.
-
-### And ByteBooks is not a third party at all
-
-`dtsbytebooks.com` is **the current operator of Adobe's ebook DRM platform**.
-Adobe transferred Adobe Content Server, RMSDK and Adobe Digital Editions to
-**Wipro Ltd** (via Harman's Digital Transformation Solutions division — the "DTS"
-in the name) in July 2025; ByteBooks IDs replaced Adobe IDs for end users on
-**2026-06-23**. Adobe's own support pages say so, and the DNS is conclusive:
-
-```
-adeactivate.adobe.com.  CNAME  activate.dtsbytebooks.com.
-readerscert.adobe.com.  CNAME  readerscert.dtsbytebooks.com.
-```
-
-So the `ACS` constant in both plugins *already resolves into ByteBooks
-infrastructure*. Registering a ByteBooks ID is simply how one obtains an Adobe ID
-now. A fuller review is in
-[`dtsbytebooks-review.md`](dtsbytebooks-review.md).
-
-**How the error happened, since it matters more than the fact:** the endpoint list
-was taken from a malformed intermediate tool output rather than re-read from
-source, and the plausibility of `/api/v1/login` on a domain already known to be
-present stopped the check. A one-line `grep -c` would have caught it. Host
-*presence* in a file is not evidence of a host being *called*.
-
-## `sentry.libbyapp.com` is not error telemetry
-
-Worth stating because the name invites a wrong conclusion. `libby` sets:
-
-```js
-// Libby. sentry.libbyapp.com is current; sentry-read.svc.overdrive.com is the …
-const LIBBY_BASE = 'https://sentry.libbyapp.com';
-```
-
-"Sentry" here is **OverDrive's own API service name**, not Sentry.io crash
-reporting. The plugin is not shipping telemetry to a third party — it is calling
-Libby's API. A naive host-list review would flag this as analytics; it is not.
-
-Hosts actually contacted, in full:
-
-- `protected-content`: **`adeactivate.adobe.com` only**
-- `libby`: `adeactivate.adobe.com` and `sentry.libbyapp.com`
-
-`dtsbytebooks.com` is linked in the UI of both but never fetched.
-
-## What this survey does **not** establish
-
-- **No audit of the fulfilment logic.** 1,133 and 1,441 lines respectively; only
-  constants, API calls, paths and hosts were extracted.
-- **No review of credential handling.** Both write a PKCS#12 credential to an
-  unencrypted SD card and both hold account passwords in page memory during
-  activation. Whether either does anything careless with them was **not checked**,
-  and given that plugins are explicitly **not sandboxed**, any plugin on the
-  device could read `/.crosspoint/content.key` regardless.
-- **No verification that either works.** Neither was installed.
-- **No determination of who wrote the shared core**, or under what terms it was
-  reused. Both are unlicensed.
-
-## Practical guidance
-
-Use `libby` if you want library loans; it supersedes `protected-content` for that
-purpose and is the only one that lists loans. Use `protected-content` only if you
-have `.acsm` files from elsewhere.
-
-Prefer `libby` on provenance grounds too: it is in a git repository with history,
-whereas `protected-content` is two files on a Railway host with **no repository
-and no Wayback mirror** — see
-[source-snapshots.ARCHIVED.md](source-snapshots.ARCHIVED.md).
-
-Both are unlicensed third-party JavaScript that handles credentials on an
-unauthenticated web server. That is a decision to make deliberately.
-
-## See also
-
-- [The Libby path](libby-path.md) — the complete setup procedure
-- [SD-card plugins and protected content](sd-plugins-and-protected-content.md) — the API and its limits
diff --git a/software/applications/crosspoint-reader/plugins/sd-plugins-and-protected-content.md b/software/applications/crosspoint-reader/plugins/sd-plugins-and-protected-content.md
deleted file mode 100644
index 47aaa53..0000000
--- a/software/applications/crosspoint-reader/plugins/sd-plugins-and-protected-content.md
+++ /dev/null
@@ -1,278 +0,0 @@
-# The CrossPoint SD-card plugin system — and the Libby/ADEPT path
-
-> Everything needed to approach this confidently: the firmware branch, the API
-> surface, the hard limits, the store protocol, every shipped plugin, and how
-> protected library loans actually reach the device.
->
-> Researched **2026-09-11**. Repository, branch and source facts are
-> `executed-success` (repos cloned, `git grep` against the actual branch, live
-> HTTP fetches). Behaviour is `inferred` — **nothing was built, flashed or run**,
-> and no device or library account was used.
-
-## Two corrections to this knowledge base
-
-This research overturns two things recorded earlier. Both are stated here first
-because they change what a reader should believe.
-
-**1. The plugin system is not a stale roadmap item.** An earlier pass recorded
-that "`develop` contains zero plugin files" and the work was a Phase 2 item on
-unmerged branches. The first half is still true. The second is misleading:
-
-| Branch | vs `develop` | Tip | State |
-|---|---|---|---|
-| **`feat-sd-plugins`** | **66 ahead, 0 behind** | **2026-09-10** | Strictly ahead — **a clean merge**, actively developed |
-| `feat-sd-web-plugins` | 64 ahead, 58 behind | — | Genuinely divergent |
-
-`feat-sd-plugins` contains everything in `develop` plus 66 commits. It is not
-drifting; it was touched the day before this snapshot. **And it carries
-`[env:papermono]`.**
-
-**2. CrossPoint *can* read Adobe-DRM'd EPUBs.** The Calibre record in this
-knowledge base states that "no CrossPoint-family firmware has a DRM client" and
-that protected loans "do not open". **That is wrong.**
-`lib/Epub/ContentProtection.cpp` exists on `feat-sd-plugins` and reads a
-`<book>.epub.rights` sidecar — deliberately keeping the EPUB *"byte-identical"*
-on disk — against a device credential at `/.crosspoint/content.key`.
-
-## Architecture
-
-```
- Browser (reader's web UI, same-origin)          Device firmware            SD card
- ┌──────────────────────────────┐        ┌──────────────────────┐     ┌──────────────┐
- │ plugin.js                    │──────▶ │ /api/relay   32 KB   │────▶│              │
- │  CrossPoint.registerPlugin() │        │ /api/crypto  wolfSSL │     │ /.crosspoint │
- │  mounted on Files or Settings│        │ /api/fetch   →SD     │────▶│  /plugins/   │
- └──────────────────────────────┘        │ /api/plugin-fs       │     │  content.key │
-            ▲                            │ /api/plugins         │     │  *.epub      │
-            │ injected by PluginHost.js  └──────────────────────┘     │  *.epub.rights│
-            │                                       │                 └──────────────┘
-      device.json → an on-device UI under Settings ▸ System ▸ Plugins
-```
-
-**Plugins are browser JavaScript.** No code runs on the MCU. The firmware
-provides four capabilities a browser cannot do itself, and that is the whole
-boundary.
-
-## The API surface
-
-From `src/network/html/shared/PluginHost.js.inc` on `feat-sd-plugins`. A plugin
-calls `CrossPoint.registerPlugin(async (container, api) => { … })` and receives:
-
-| Call | Backing endpoint | Purpose |
-|---|---|---|
-| `api.relay(method, url, headers, body)` | `POST /api/relay` | Outbound HTTP(S) — browsers can't, due to CORS |
-| `api.crypto(op, fields)` | `POST /api/crypto` | wolfSSL primitives |
-| `api.writeFile(path, dataB64)` | `POST /api/plugin-fs` | Write a small file to SD |
-| `api.fetchToSd(url, dest, headers)` | `POST /api/fetch` | Stream a URL straight to SD — **bytes never touch the page** |
-| `api.registerAction(action, fn)` | — | Expose an action to the host page |
-
-Discovery is `GET /api/plugins` → `[{name, title, mount}]`; files are served from
-`GET /plugin?name=<p>&file=<f>`, reading `/.crosspoint/plugins/<p>/<f>`.
-
-### `/api/crypto` operations
-
-Enumerated from the source: `keygen`, `sign`, `pubencrypt`, `aesenc`, `aesdec`,
-`pkcs12`, `cert`, `hash`, `sha1`, `random`.
-
-**That set is not incidental — it is precisely an Adobe ADEPT toolkit**: RSA
-keygen and signing for device activation, PKCS#12 for the credential container,
-AES for content-key unwrap, SHA-1 because ADEPT still uses it.
-
-### Hard limits — design around these
-
-| Limit | Value | Source |
-|---|---|---|
-| `/api/relay` response cap | **32 KB** (`RELAY_BODY_LIMIT`) | HTTP **413**, *"response too large, use /api/fetch"* |
-| `/api/fetch` segment cap | **4 MB** (`FETCH_MAX_SEGMENT_SIZE`) | supports `offset`/`maxBytes` for chunking |
-| Stalled-fetch retries | 3 (`FETCH_MAX_STALLED_ATTEMPTS`) | |
-| Manifest cap | **8 KB** | per the repo's plugin-authoring skill |
-| Redirects on `/api/fetch` | **not followed** | resolve them yourself via `relay` |
-| Archive extraction | **none on-device** | ship unpacked files |
-
-The 32 KB relay cap is the one that shapes plugin design: **metadata and API
-calls go through `relay`, book bytes go through `fetchToSd`.**
-
-## Installing
-
-Three roots are scanned, first match wins:
-
-```
-/.crosspoint/plugins/<name>/      ← where the store installs
-/plugins/<name>/                  ← easier to reach from a computer
-/.plugins/<name>/
-      manifest.json   plugin.js   device.json   …assets
-```
-
-`manifest.json` `mount` is `files` or `settings` — which page the plugin extends.
-A `device.json` additionally gives it an **on-device** UI under
-Settings ▸ System ▸ Plugins, so a plugin can be driven without a browser.
-
-**Fastest path:** download `plugin-store.zip` from the sd-plugins releases, unzip
-at the SD root, then install everything else from the store itself.
-
-## `itsthisjustin/sd-plugins`
-
-★36 · 10 forks · JavaScript · **no licence file** · HEAD `dfc0a888` · pushed **2026-09-10**
-
-| Plugin | v | What it does |
-|---|---|---|
-| `plugin-store` | 1.1.2 | Installs plugins from one or more hosted catalogs |
-| `bookfusion` | 1.2.0 | BookFusion library; device-code + QR sign-in; writes `<book>.meta.json` that rides KOSync progress uploads |
-| `webdav` | 1.0.0 | Nextcloud/ownCloud/Seafile/Koofr; creds in `/.crosspoint/webdav.json` |
-| `wallabag` | 1.2.0 | Read-it-later articles as EPUB (OAuth2 password grant) |
-| `dictionaries` | 1.0.0 | ~20 offline StarDict dictionaries from Wiktionary + Webster's 1913 |
-| `organize-by-author` | 1.0.0 | Files EPUBs into per-author folders; moves progress, cache and `.epub.rights` sidecars with the book |
-| `hello` | 1.0.0 | Minimal loader example |
-| **`protected-content`** | **1.0.4** | **See below** |
-
-Catalog format is documented in `CATALOG.md`: a JSON doc with `plugins[]`, each
-carrying `name`, `base` URL and a `files[]` list. **Anyone can host a catalog**
-— a static file or raw Git URLs — and users add multiple stores.
-
-## The Libby path: `protected-content`
-
-This is the plugin the question was really about. It is **not named Libby**, and
-it is **not in the repository**.
-
-```jsonc
-{
-  "name": "protected-content",
-  "title": "Protected Content",
-  "description": "Fulfill protected content from an online provider.",
-  "author": "Diirge",
-  "version": "1.0.4",
-  "base": "https://protected-content-host-production.up.railway.app/",
-  "files": ["manifest.json", "plugin.js"]
-}
-```
-
-**It is hosted off-GitHub on Railway** — no git history, no licence, no code
-review, no tags. Every other plugin's `base` is `raw.githubusercontent.com`. Only
-this one is elsewhere, and only this one ships no `README.md`. A grep of the
-sd-plugins repo for "libby" returns **zero hits**.
-
-Draw your own conclusion about why; the observable fact is that the DRM
-fulfilment code is deliberately kept outside the repository.
-
-### What it actually is
-
-`plugin.js` is **53,887 bytes** and its own header comment is explicit:
-
-> *Browser-side account activation and fulfillment using generic device APIs:*
-> `/api/relay` *outbound HTTP(S) (browsers can't, due to CORS)*
-> `/api/crypto` *wolfSSL primitives (keygen, sign, AES, PKCS#12, hash, random)*
-> `/api/fetch` *download a URL straight to SD (book bytes never touch the page)*
-> `/api/plugin-fs` *write a small file to SD (the credential + rights sidecar)*
-
-Constants confirm it is a full **Adobe ADEPT** client:
-
-```js
-const ADEPT_NS = 'http://ns.adobe.com/adept';
-const ACS      = 'https://adeactivate.adobe.com/adept';   // Adobe's activation server
-const ADEPT_CT = 'application/vnd.adobe.adept+xml';
-const CREDENTIAL_PATH = '/.crosspoint/content.key';
-const ACTIVATION_PATH = '/.crosspoint/content-activation.json';
-const HOBBES = '10.0.4';                                   // the ADE version it presents as
-```
-
-`mount: "files"` — it appears in the File Manager.
-
-### The end-to-end chain
-
-1. **Activate** — the plugin generates an RSA keypair via `/api/crypto keygen`,
-   signs an activation request, talks to `adeactivate.adobe.com` through
-   `/api/relay`, and stores the resulting credential at
-   `/.crosspoint/content.key` (PKCS#12) plus
-   `/.crosspoint/content-activation.json`.
-2. **Fulfil** — given an `.acsm` (what Libby/OverDrive hand you for a loan), it
-   performs the ADEPT fulfilment exchange and uses `/api/fetch` to stream the
-   EPUB **straight to SD**, then writes a `<book>.epub.rights` sidecar.
-3. **Read** — `lib/Epub/ContentProtection.cpp` in the firmware reads that sidecar
-   against the device credential. The source notes the design keeps the EPUB
-   *"byte-identical"* on disk — so the file is **not** decrypted in place; it is
-   decrypted at read time.
-
-**So the device is an ADEPT-activated reader.** It is not removing DRM — it is
-acting as a licensed endpoint, the same role Adobe Digital Editions or a Kobo
-plays.
-
-### What you need
-
-| Requirement | Detail |
-|---|---|
-| Firmware | A build from **`feat-sd-plugins`** (or `feat-sd-web-plugins`). **Not `develop`** — it has no plugin API |
-| Adobe ID | Activation consumes one of the account's device slots |
-| The plugin | Installed via the store, or by hand from the Railway URL |
-| Source | Libby/OverDrive — export the loan as an **ACSM** (the "Adobe" / EPUB download option, not "read in browser") |
-
-**Constraints worth knowing up front:** Adobe IDs have a limited number of
-activations, and deactivating requires ADE or Adobe's site. The 32 KB relay cap
-means the fulfilment negotiation is chunked while the book itself goes via
-`fetch`. And **nothing here removes DRM** — the loan still expires, and the file
-is unreadable on an unactivated device.
-
-### Legal framing
-
-This documents what exists and how it works. **Using a licensed ADEPT client to
-read a legitimately borrowed loan is the intended use of that content** — it is
-what ADE does. That is different in kind from DRM *removal* (DeDRM and friends,
-covered in the [Calibre record](../../../tooling/calibre/README.md)), which is
-restricted in many jurisdictions.
-
-None of this is legal advice, and the plugin's unlicensed, off-repository hosting
-is a fact a reader should weigh for themselves.
-
-## Security model — stated plainly by upstream
-
-The sd-plugins README does not oversell it:
-
-> *"Plugins are JavaScript loaded into the File Manager or Settings page, **not an
-> isolated iframe**. They can call the same-origin web API and any generic device
-> capability."*
-
-So a plugin has the **full authority of the web UI**, including other plugins'
-credentials on SD. Combined with the web server having **no authentication**, the
-real boundary is *network-vs-device*, not *plugin-vs-firmware*. Install plugins
-you trust, and treat the reader's Wi-Fi exposure accordingly.
-
-This is a different and weaker boundary than the
-[native ELF plugin system](README.md),
-which enforces an 81-symbol allow-list at link time — but that one cannot reach
-the network at all.
-
-## Confidence checklist
-
-To approach this with confidence, in order:
-
-1. **Build from `feat-sd-plugins`**, confirm `[env:papermono]`, flash.
-2. **Verify the API is live** — `GET /api/plugins` on the device web UI.
-3. **Install `plugin-store`** from the release zip at the SD root.
-4. **Prove the loader** with `hello` before anything else.
-5. **Try a non-DRM plugin next** — `webdav` or `wallabag` — to validate relay,
-   fetch and credentials end to end.
-6. **Only then `protected-content`**, knowing it is unlicensed, off-repo, and
-   consumes an Adobe activation slot.
-
-## Open questions
-
-- **Nothing was built, flashed or run.** No device, no Adobe ID, no loan.
-- `protected-content`'s `plugin.js` was fetched and its header and constants read;
-  **the fulfilment logic was not audited line by line.**
-- Whether `ContentProtection.cpp` covers all ADEPT variants (and what it does with
-  expired loans) was **not examined**.
-- The relationship between `feat-sd-plugins` and `feat-sd-web-plugins`, and which
-  upstream intends to merge, is unknown.
-- `itsthisjustin/sd-plugins` has **no licence** — as does the Railway-hosted
-  plugin. Redistribution status of both is therefore all-rights-reserved.
-- Ten forks exist; none was examined.
-
-## Sources
-
-All 2026-09-11, `executed-success`:
-`itsthisjustin/sd-plugins` @ `dfc0a888` (README, CATALOG.md, catalog.json) ·
-`crosspoint-reader` branches `feat-sd-plugins` @ `3657026e` and
-`feat-sd-web-plugins` @ `bdbbbef7` (`git grep`/`git show` against
-`CrossPointWebServer.cpp`, `PluginHost.js.inc`, `ContentProtection.cpp`,
-`platformio.ini`) ·
-`https://protected-content-host-production.up.railway.app/{manifest.json,plugin.js}`
-(HTTP 200, 170 B and 53,887 B).
diff --git a/software/applications/crosspoint-reader/plugins/source-snapshots.ARCHIVED.md b/software/applications/crosspoint-reader/plugins/source-snapshots.ARCHIVED.md
deleted file mode 100644
index 1f476bf..0000000
--- a/software/applications/crosspoint-reader/plugins/source-snapshots.ARCHIVED.md
+++ /dev/null
@@ -1,116 +0,0 @@
-# Plugin-ecosystem source snapshots — ARCHIVED
-
-**Archived to** `archive/software/applications/crosspoint-reader/plugins/source-snapshots/`
-**Date:** 2026-09-11 · **Total:** ~176 MB, 18 entries
-
-The archive is machine-local and absent from a fresh clone. Everything needed to
-reacquire these is below; the archive path is a convenience, not the contract.
-
-## Why these were archived
-
-The CrossPoint SD-card plugin ecosystem is **almost entirely unlicensed and
-largely unmirrored**. Of 18 snapshots, **15 carry no licence file at all**, most
-sit at ★0, and one — the ADEPT client that makes library loans work — exists on
-a single Railway host with **no git repository anywhere**.
-
-This is a documentation ecosystem with a real risk of silent disappearance, and
-the Libby path documented in [`libby-path.md`](libby-path.md) depends on it.
-
-## What is held
-
-### The store and its forks
-
-| Repository | HEAD | Licence |
-|---|---|---|
-| `itsthisjustin/sd-plugins` — **the canonical store** | `dfc0a88858d1486a2707e1c4ba61517b94646dfe` | none |
-| `marczykm/sd-plugins` | `98a92d09e9f921e2278d9c01db86a8aff6d9f34e` | none |
-| `pagdot/sd-plugins` | `98a92d09e9f921e2278d9c01db86a8aff6d9f34e` | none |
-| `Haas-Robert/sd-plugins` | `6dc90087b03cc29048a5c6aaed3a0e739afda521` | none |
-| `josmerod/sd-plugins` | `6dc90087b03cc29048a5c6aaed3a0e739afda521` | none |
-| `dezren39/sd-plugins` | `0b2989bdc9645b25398fd953fbf448a7bf316527` | none |
-| `mjonessa/sd-plugins` | `08527fe5a09906f82c05cc4a25f6ce6cbac90bba` | none |
-| `jadehawk/sd-plugins` | `b2affa12a8946284b4e27feff4f919135afee10b` | none |
-| `shelbeeely/sd-plugins` | `b2affa12a8946284b4e27feff4f919135afee10b` | none |
-| `ejoh1101/crosspoint-sd-plugins` | `b2affa12a8946284b4e27feff4f919135afee10b` | none |
-| `aluhrs13/crosspoint-readwise-plugin` | `b2affa12a8946284b4e27feff4f919135afee10b` | none |
-
-**Four forks share two HEADs** (`98a92d09` ×2, `6dc90087` ×2) and **four more sit
-on `b2affa12`** — they are stale snapshots of the store at three points in time,
-not independent work. That is itself the finding: the fork catalogues advertising
-`libby` v0.2.0 are frozen at a commit whose target URL no longer exists.
-
-### The Libby implementations
-
-| Snapshot | Contents |
-|---|---|
-| `ruqqq/crosspoint-plugins` @ `8aa65e18a4e6f8b5348ef5b29c0eb8570607bba1` | **The working `libby` 1.0.2**, plus `kopi`. No licence |
-| `_plugins__ruqqq-libby/` | Standalone copy of `libby/{manifest.json,plugin.js,README.md}` — belt and braces |
-| `_offrepo__protected-content-railway/` | **The off-repository ADEPT client** — see below |
-
-### The native-ELF plugin system (a separate design)
-
-| Repository | HEAD | Licence |
-|---|---|---|
-| `mekhontsev/crosspoint-reader` — firmware fork, the plugin **host** | `33197aad82d47410165705ad9260eca237f30229` | MIT |
-| `mekhontsev/crosspoint-plugins` — native `.so` modules | `750bbe2aff46318fb12b196334269d73c8f11a0e` | MIT |
-| `mekhontsev/pagewire` — Android/Termux client + protocol | `ee56ef3ac178a1ef42855c8e9ee6a09b66c5e14b` | MIT |
-
-Cloned `--depth 200` for the firmware fork (160 MB); the other two are full.
-These are the only MIT-licensed members of the set.
-
-### Other
-
-`samfoy/crosspoint-bookorbit-plugin` @ `d5957f13320c1e12531c0fdd2275761ed5e19fa4`, no licence.
-
-## The scarce one: `protected-content`
-
-**This is the artifact that justifies the whole archive.**
-
-| | |
-|---|---|
-| Source | `https://protected-content-host-production.up.railway.app/` |
-| `manifest.json` | 170 B · `sha256:15d72dcdcc4643be…` |
-| `plugin.js` | **53,887 B** · `sha256:e35ecc85d095882a…` |
-| Licence | **none** |
-| Git repository | **none — anywhere** |
-
-Every other plugin in `itsthisjustin/sd-plugins`' catalogue is served from
-`raw.githubusercontent.com`. Only this one is served from a third-party PaaS, and
-only this one ships no README. `README.md` and `device.json` both return **404**,
-confirming it is a two-file, web-UI-only plugin.
-
-**Wayback submission was attempted and returned HTTP 523** (origin unreachable
-through their fetcher) for both files, so **no public mirror exists**. If the
-Railway deployment lapses, the local snapshot is the only copy.
-
-## Reacquisition
-
-```bash
-# git repositories — all public, all reacquirable
-git clone https://github.com/<owner>/<repo> && git -C <repo> checkout <HEAD from the tables above>
-
-# the off-repository plugin — single host, no mirror, may vanish
-curl -O https://protected-content-host-production.up.railway.app/manifest.json
-curl -O https://protected-content-host-production.up.railway.app/plugin.js
-```
-
-Status: **`automatic`** for the 16 git repositories; **`blocked`/at-risk** for the
-Railway files — reachable today, unmirrored, no second source.
-
-## Licensing
-
-**15 of 18 snapshots carry no licence** and are therefore all-rights-reserved by
-default. They are retained as **research artifacts** — evidence of what existed
-at a date — not as redistributable code. Do not vendor from them.
-
-The three MIT exceptions are the `mekhontsev` repositories.
-
-Per this project's policy licence is recorded as metadata, not treated as a gate
-on acquisition; see the method's *"Record licensing as metadata"*.
-
-## See also
-
-- [The Libby path](libby-path.md) — what these snapshots support
-- [SD-card plugins and protected content](sd-plugins-and-protected-content.md)
-- [Plugin systems overview](README.md)
-- `MANIFEST.md` inside the archive directory carries the same table, generated.
diff --git a/software/ecosystems/crosspoint-freeink/asian-platform-search.md b/software/ecosystems/crosspoint-freeink/asian-platform-search.md
deleted file mode 100644
index 59c5f0f..0000000
--- a/software/ecosystems/crosspoint-freeink/asian-platform-search.md
+++ /dev/null
@@ -1,190 +0,0 @@
-# Asian-platform search for ESP32 / M5Stack e-paper software
-
-> Closing the gap flagged in every previous sweep: all prior searching was
-> English-language and GitHub-centric. This pass covers Japanese and Chinese
-> developer platforms.
->
-> Searched **2026-09-11**. Retrievals are `executed-success`; the absence claims
-> are qualified below — some platforms could not be searched at all, which is
-> **"no determination"**, not "nothing there".
-
-## Headline
-
-**Japanese-language sources are productive and were a real gap.** They surfaced a
-project absent from every prior sweep, and a substantial technical corpus around
-the exact NFC library this knowledge base has been analysing.
-
-**Chinese-language sources are thin for this specific device, and that is now
-partly measured rather than assumed.** CSDN — searchable on a second attempt via
-its JSON API — carries **4,301 articles on `M5Paper` and zero on `M5PaperMono`**.
-Gitee and Zhihu remain inaccessible, so the picture is still incomplete.
-
-## Platform results
-
-| Platform | Query path | Result |
-|---|---|---|
-| **Qiita** (JP) | public API `/api/v2/items` | ✅ **Productive** — see below |
-| Zenn (JP) | `/api/search` | 0 articles for `PaperMono` |
-| **Bilibili** (CN) | web search | 1 real hit — **the vendor's own product announcement only** |
-| Gitee (CN) | API `/api/v5/search/repositories` | **0 for `m5stack`, `esp32` *and* `arduino`** — control test proves the endpoint is gated, not empty. **No determination** |
-| Gitee search UI | `search.gitee.com` | 849 B — JS shell. **No determination** |
-| **CSDN** (CN) | **`so.csdn.net/api/v3/search`** | ✅ **Searchable after all** — see the correction below |
-| Zhihu (CN) | `/search` | **HTTP 403** — blocked |
-
-The Gitee API returning zero results for `m5stack` — a vendor with a large Chinese
-following — is strong evidence the endpoint is gated rather than empty. **Do not
-read these as verified absences.**
-
-
-## Correction: CSDN is searchable, and it changes two conclusions
-
-The first pass hit `so.csdn.net`'s HTML search page, got a 5,850-byte JavaScript
-shell, and recorded "no determination". **That was a tooling failure, not an
-absence.** CSDN exposes a working JSON API:
-
-```
-https://so.csdn.net/api/v3/search?q=<query>&t=blog&p=1
-```
-
-With that, two earlier statements must be revised:
-
-**1. `M5PaperMono` genuinely has no Chinese-language coverage.** CSDN returns
-**4,301 articles for `M5Paper`** but **zero for `M5PaperMono`**. That is now a
-*measured* absence on China's largest developer-blog platform, not an untested
-guess. The general M5Paper line is well covered in Chinese; the Mono is not.
-
-**2. There is a real SSD1677 corpus — 69 articles.** Two look directly relevant to
-open questions in this knowledge base:
-
-| Date | Title | Why it matters |
-|---|---|---|
-| 2023-08-08 | 高分辨率大屏墨水屏调测问题 — *"Debugging issues with high-resolution large e-paper displays"* | Predates this device; the SSD1677 drives exactly that class of panel |
-| 2026-02-13 | SSD1683墨水屏驱动电压参数优化实战 — *"Practical driver voltage parameter optimisation for SSD1683 e-paper"* | **Voltage-parameter tuning on a sibling Solomon Systech controller** — the same family as the [C25 booster question](../../../devices/m5stack/papermono/gaps-and-conflicts.md) |
-
-**Neither article was read.** They are recorded as leads, identified from titles
-and dates only. The SSD1677 result set is also noisy — it contains QNAP NAS and
-laptop-SSD articles matching on the alphanumeric fragment — so 69 is an upper
-bound on genuinely relevant material.
-
-`墨水屏 ESP32` ("e-paper ESP32") returns **1,567 articles**, including firmware
-optimisation and SPI driver write-ups. So the Chinese ESP32 e-paper community is
-substantial; it simply has not engaged with this specific board.
-
-### What this says about method
-
-The difference between "no determination" and a measured zero was **one API
-endpoint**. The first pass treated a JavaScript shell as evidence; it was only
-evidence that the wrong URL had been fetched. The Gitee control test — querying
-`arduino` and `esp32` and getting zero for both — is the pattern that should have
-been applied to CSDN immediately.
-
-Gitee and Zhihu remain genuinely unsearched.
-
-## The find: `mitsuharu/CardCase-For-M5Paper`
-
-Discovered only via a Qiita article, and **not present in any prior sweep**.
-
-| | |
-|---|---|
-| Repository | `mitsuharu/CardCase-For-M5Paper` |
-| Licence | **MIT** — unlike the other two badge projects |
-| Language | C++ · ★1 · 2.9 MB |
-| Created | **2025-03-28** — predates the PaperMono |
-| Pushed | 2026-09-07 |
-| Description | *"Display images saved on an SD card on M5Stack e-paper devices. Also displays images received via WiFi or NFC."* |
-
-Announced in [Qiita 6a764283f6f9e7ccf1b6](https://qiita.com/mitsuharu_e/items/6a764283f6f9e7ccf1b6)
-(2026-09-05, author `mitsuharu_e`): *"A name-badge solution with smartphone
-integration for M5Stack Paper v1.1 / S3 / Color / Mono."*
-
-Two things make it notable:
-
-1. **It supports four M5Paper generations** — v1.1, S3, Color and Mono — from one
-   codebase. That is the broadest device coverage of any third-party project found
-   for this board, and it arrived by extending an existing 2025 project rather
-   than starting fresh.
-2. **It is MIT.** `ciniml/paper_name_plate` and the sd-plugins ecosystem are
-   unlicensed; this is a usable reference implementation.
-
-## Four independent name-badge projects
-
-With this addition the convergence is striking:
-
-| Project | Language | Licence | Approach |
-|---|---|---|---|
-| `ciniml/paper_name_plate` | Rust | none | NFC **tag emulation**, BLE config |
-| `Corvelis/m5-touch-card` | C++ | MIT | NFC exchange + **smartphone app** |
-| `mitsuharu/CardCase-For-M5Paper` | C++ | **MIT** | Image display, **NFC/WiFi image receive**, 4 devices |
-| *(vendor demo)* | C++ | MIT | NFC identity read only |
-
-**Three independent Japanese developers built a digital name badge within weeks of
-launch.** That is not coincidence: Japanese technical-conference culture places
-heavy weight on 名札 (name badges) and 名刺交換 (business-card exchange), and a
-device that is a screen plus a tag emulator maps onto it exactly.
-
-This is the clearest "what is this hardware actually for" signal found in any
-sweep, and **it was invisible to English-language search.**
-
-## The Qiita corpus
-
-Article counts by query (API, `per_page=100`, so 100 means "at least 100"):
-
-| Query | Items |
-|---|---|
-| `M5Paper` | **100+** |
-| `電子ペーパー` (e-paper) | **100+** |
-| `ESP32 NFC` | 43 |
-| **`M5Unit-NFC`** | **24** |
-| **`ST25R3916`** | **11** |
-
-**24 articles on `M5Unit-NFC`** — the library with the
-[stack overflow documented here](m5unit-nfc-overflow.md). If community knowledge
-of that library's behaviour exists anywhere, it is here, in Japanese, and this
-project has not read it.
-
-Relevant articles spotted:
-
-- `fknaopen`, 2026-08-17 — *"Reading NFC-F (FeliCa) with Unit NFC (for the legacy
-  M5Stack library)"*. FeliCa is the Japanese transit/payment standard; the
-  ST25R3916 supports it and Western coverage of that path is thin.
-- `misoca12`, 2024-11-29 (LGTM 5) — *"Reading multiple RFID tags simultaneously
-  with M5Stack"* — anticollision, which is exactly the code path containing the
-  overflow.
-- `ksasao`, 2025-12-19 — *"Writing 'when and where' onto a paper business card on
-  the spot"* — the same problem space, pre-dating the PaperMono.
-
-## What this changes
-
-- **The project catalogue was incomplete**, and the missing entry is the only
-  MIT-licensed badge implementation.
-- **Japanese sources should be part of the standard sweep**, not an afterthought.
-  Qiita has a public, unauthenticated API and is trivial to query.
-- **The "NFC is the killer app" finding is stronger than previously stated** —
-  four implementations, three independent authors, one cultural driver.
-- **Chinese-language coverage remains genuinely unknown.** Bilibili carries the
-  vendor announcement and nothing else found; Gitee, CSDN and Zhihu could not be
-  searched.
-
-## Method and limits
-
-Qiita and Zenn were queried through public APIs. Bilibili was fetched with a
-browser user-agent and parsed from embedded JSON. Gitee's API returned an empty
-array for every query including control terms; its search UI is a JS shell. CSDN
-returned a near-empty JS shell. Zhihu returned 403.
-
-**Corrected mid-survey:** CSDN was initially recorded as unsearchable; its JSON
-API works and was used for the figures above.
-
-**Not attempted:** Weibo, Baidu Tieba, Douyin, Xiaohongshu, Taobao listings,
-Japanese `note.com`, `elchika`, Switch Science's blog, or any forum requiring
-login. Machine translation was not used — Japanese titles were read directly and
-Chinese hits were too few to need it.
-
-**No article was read in full**; titles, dates, tags and the one relevant body
-excerpt were used. Nothing was built or run.
-
-## See also
-
-- [New PaperMono projects](new-papermono-projects-2026-09.md) — the English-language sweeps
-- [NFC implementation comparison](nfc-implementation-comparison.md)
-- [`M5Unit-NFC` overflow](m5unit-nfc-overflow.md) — the library those 24 Qiita articles discuss
diff --git a/software/ecosystems/crosspoint-freeink/crossink-papermono-feasibility.md b/software/ecosystems/crosspoint-freeink/crossink-papermono-feasibility.md
deleted file mode 100644
index 59a736f..0000000
--- a/software/ecosystems/crosspoint-freeink/crossink-papermono-feasibility.md
+++ /dev/null
@@ -1,228 +0,0 @@
-# CrossInk + PaperMono + plugins + radios — a feasibility assessment
-
-> Four questions, answered against the source rather than the marketing:
-> can CrossInk run on a PaperMono, can it take the plugin store and Libby, what
-> does updating the fork cost, and what would basic LoRa/NFC take?
->
-> Measured **2026-09-04**. Repository and source facts are `executed-success`
-> (repos cloned, files read, GitHub compare API). Effort estimates are
-> `inferred`. **No hardware, and nothing was built for CrossInk.**
-
-## Short answers
-
-| Question | Answer |
-|---|---|
-| Does CrossInk support the PaperMono? | **No — and it structurally cannot today.** Its pinned SDK predates PaperMono support entirely |
-| Can it take the plugin store? | **No.** CrossInk has no on-device plugin system, and neither does upstream on `develop` |
-| Can it take Libby? | **Yes, already — and no firmware change is needed.** Libby is host-side Calibre tooling |
-| What does updating the fork cost? | **High.** 294 commits behind, with divergence concentrated in `lib/` (224 files) — the opposite of a clean additive fork |
-| What would LoRa/NFC take? | **A new capability class in the SDK.** Neither radio has *any* abstraction today |
-
-## 1. PaperMono on CrossInk
-
-**CrossInk has no PaperMono support of any kind.** Grepping the whole repository
-for `papermono`, `paper_mono` or `C153` across `.ini`, `.h`, `.cpp` and `.md`
-returns **zero matches**.
-
-Its build environments (`platformio.ini`, HEAD `cab4f249`, branch `main`):
-
-```
-default · debug · simulator · simulator-X3 · sticky-simulator
-x4-pro-simulator · sticky · sticky-debug
-```
-
-So: the C3 devices (`default`), the Seeed reTerminal Sticky, and simulator
-variants. No PaperMono, and notably no non-simulator X4 Pro env either.
-
-### The blocker is the SDK pin, not the build config
-
-This is the part that makes it more than a missing `[env:]` block.
-
-| | freeink-sdk commit | PaperMono refs in `BoardConfig.h` |
-|---|---|---|
-| **CrossInk** | `1ff020263cd2202ea79ce3eb811f5ac8489b8cde` | **0** |
-| **CrossPoint** | `68425f8eec1246a0be0c0f311540f60ad733fa76` | **37** |
-
-`GET /compare/1ff02026...68425f8e` → **ahead 136, behind 0, 103 files changed.**
-
-**PaperMono board support was added to the FreeInk SDK in those 136 commits.**
-CrossInk's pin predates it. There is nothing to switch on.
-
-In the newer SDK the support is real and structural — `FREEINK_DEVICE_PAPERMONO`,
-`BoardProfile PAPER_MONO`, `FREEINK_DRIVER_PAPER_MONO`, a `Board::PaperMono`
-case, and the device appears in the capability groupings for touch, frontlight,
-USB-MSC, **MIC** and **LED**.
-
-### So the work is, in order
-
-1. **Bump the submodule 136 commits** — 103 files of SDK change landing under a
-   fork that has diverged from upstream. This is the real cost, not the envs.
-2. Add `[env:papermono]` (and release variants), mirroring CrossPoint's.
-3. Reconcile CrossInk's own `lib/` changes against SDK API drift across 136
-   commits.
-
-Step 3 is unbounded from here — it depends on which SDK APIs CrossInk touches,
-which was not audited. **Do not read "add an env" as the estimate.**
-
-## 2. The plugin store
-
-**Not available on CrossInk, and not because of CrossInk.**
-
-CrossInk contains no on-device plugin system. Every `plugin` match in the
-repository is documentation about the **Calibre** device plugin
-(`docs/user-guide.md`, `docs/webserver.md`) — host-side, unrelated.
-
-Upstream is the same: the JavaScript plugin work lives on two unmerged branches,
-never on `develop`. The store (`ruqqq/crosspoint-plugins`, ★0, no licence)
-catalogues plugins for a system that has not shipped in either firmware.
-
-The **native** plugin host — `mekhontsev`'s ELF-module system with a versioned
-ABI — is a *different fork's* invention and is **X4 Pro only**. It is not in
-CrossInk and not in upstream.
-
-So "incorporating the plugin store into CrossInk" means first importing a plugin
-system that does not exist in either parent. See
-[plugin systems](../../applications/crosspoint-reader/plugins/README.md).
-
-## 3. Libby — already solved, at the wrong layer to worry about
-
-Libby is **not device software.** `ping/libby-calibre-plugin` runs inside Calibre
-on a computer; it fetches OverDrive loans into a Calibre library. The device
-never speaks to OverDrive.
-
-CrossInk's own `docs/user-guide.md` already documents receiving books via the
-**CrossPoint Calibre device plugin**, and its web server implements the Calibre
-Wireless path (`src/network/CrossPointWebServer.cpp`, `docs/webserver.md`).
-
-**So the Libby → Calibre → CrossInk chain works today with no firmware change.**
-
-Two caveats carried from the [Calibre record](../../tooling/calibre/README.md),
-and they are the real risks:
-
-- `libby-calibre-plugin` was **last pushed 2023-12-01** — nearly three years
-  stale against a vendor-controlled API. Whether it still works is untested here.
-- **DRM is the actual barrier.** Most commercial library loans are Adobe
-  ADEPT-protected, and no CrossPoint-family firmware has a DRM client. Unprotected
-  loans pass through; protected ones do not open, and no firmware work changes
-  that.
-
-## 4. Updating the fork — the expensive part
-
-CrossInk vs upstream `develop`, 2026-09-04:
-
-```
-ahead 616 · behind 294 · 300+ files changed (API caps the list at 300)
-top directories: lib/ 224 · docs/ 45 · .github/ 11 · include/ 5
-```
-
-**224 of the changed files are in `lib/`** — the shared library layer, not
-quarantined new directories.
-
-Contrast [CrossPlay](../../applications/crossplay/README.md), which is 2,610
-commits ahead but only **2 behind**, with its additions confined to
-`src/apps_local/` and ~15 documented seams. CrossInk is the opposite pattern:
-fewer commits, far more entanglement with code upstream is actively changing.
-
-**Consequences:**
-
-- Merging 294 upstream commits into 224 modified shared files is a genuinely hard
-  merge, not a routine sync.
-- The SDK bump in §1 (136 commits, 103 files) lands *on top of* that.
-- Prior research recorded that in this ecosystem **"commits behind" is a
-  brick-risk signal**, because vendors revise hardware silently and upstream
-  carries the fixes. 294 behind is a lot of unabsorbed hardware fixes.
-
-CrossInk is actively maintained (pushed 2026-09-03), so this is deliberate
-divergence rather than abandonment — but it is divergence that compounds.
-
-## 5. LoRa and NFC — the decisive finding
-
-**The FreeInk SDK has no radio abstraction whatsoever.** This is the answer that
-governs the whole question, for CrossInk *and* CrossPoint *and* CrossPlay.
-
-The SDK's complete capability set:
-
-```
-AUDIO · BLE_HID_HOST · BLE_KEYBOARD · BUZZER · COLOR · FRONTLIGHT
-IMU · LED · MIC · NET_TLS · RTC · TEMP_HUMIDITY · TOUCH · USB_MSC · WARMLIGHT
-```
-
-**No `FREEINK_CAP_LORA`. No `FREEINK_CAP_NFC`. No RFID.**
-
-What the greps actually found, and why neither counts:
-
-| Match | Reality |
-|---|---|
-| `T5S3_LORA_CS/IRQ/RST/BUSY` in `BoardT5S3Pins.h` | Pin *numbers* for the LilyGo T5S3 |
-| `pinMode(T5S3_LORA_CS, OUTPUT)` in `BoardT5S3.cpp` | **Deasserting chip-select** so the LoRa chip does not corrupt the shared SPI bus. Housekeeping, not a driver |
-| `0x50 (NFC on Pro)` in `InputManager.cpp` | A **comment** in an I²C-address list, so the bus scanner knows what it may see |
-
-That is the entirety of radio awareness in the SDK: know the pins exist, keep
-them quiet, and don't be surprised by an I²C address.
-
-### What adding basic LoRa/NFC actually requires
-
-Not a plugin, and not a build flag. The pattern the SDK already uses for `Rtc`
-and `Imu` would have to be repeated:
-
-1. **New capability flags** — `FREEINK_CAP_LORA`, `FREEINK_CAP_NFC` — gated per
-   board profile.
-2. **New board-profile fields** — SPI pins, NSS, BUSY, DIO/IRQ, reset, antenna
-   switch for LoRa; I²C address and IRQ for NFC. On the PaperMono these are not
-   direct GPIO: reset and antenna switch run through the **M5IOE1 expander** and
-   the LoRa rail is enabled by the **M5PM1** power manager
-   ([pinouts](../../../devices/m5stack/papermono/pinouts-and-buses.md)).
-3. **New device managers** — `LoRaManager`, `NfcManager` — alongside the existing
-   `Rtc`/`Imu`/`FrontlightManager`, wrapping **RadioLib** (MIT at the pinned
-   7.2.1) and an ST25R3916 stack such as ST's RFAL.
-4. **Application surface** — some UI, since a reader firmware has no concept of a
-   radio today.
-5. **Regional band configuration for LoRa**, which is a legal constraint the
-   firmware would then own — see [`guides/lora`](../../../guides/lora/README.md).
-
-**And a plugin cannot do this.** The native plugin ABI's authoritative allow-list
-(`PluginHostSymbols.inc`, 81 symbols, read directly) exports **no I²C, SPI, GPIO,
-ADC or PWM** — the link fails if a module references them. Radios need a firmware
-change first, exposing either raw bus access or, better, capability-level
-services.
-
-### Ordering, if someone actually wants this on a PaperMono
-
-The dependency chain is strict and worth stating plainly:
-
-```
-1. SDK gains LoRa/NFC capability + managers        (largest piece, benefits everyone)
-2. PaperMono board profile gains the radio fields   (expander + PMIC aware)
-3. CrossInk bumps its SDK pin 136+ commits          (§1)
-4. CrossInk adds a papermono env                    (small)
-5. Application UI                                   (fork's own choice)
-```
-
-**Steps 1–2 belong upstream in the SDK**, not in a fork — which is also where
-they would benefit CrossPoint, CrossPlay and every other consumer. Doing them in
-CrossInk would deepen exactly the divergence that already makes §4 expensive.
-
-## What was not checked
-
-- **CrossInk was not built.** No compile, no simulator run — unlike upstream,
-  which was [built and run successfully](../../tooling/crosspoint-simulator-build-notes.md).
-  CrossInk ships its own simulator envs, so this is doable and was simply not done.
-- **Which SDK APIs CrossInk's 224 modified `lib/` files touch** — the number that
-  would turn §1 step 3 from "unbounded" into an estimate.
-- Whether upstream or the SDK have any *stated intent* to add radio support; no
-  roadmap or issue search was done.
-- CrossInk's own release/versioning practice.
-- No commit SHA was pinned for CrossInk's `main` beyond `cab4f249` at fetch time.
-
-## Sources
-
-All 2026-09-04, `executed-success`:
-
-| What | Detail |
-|---|---|
-| `uxjulia/CrossInk` @ `cab4f2492` | cloned; `platformio.ini`, `.gitmodules`, `docs/`, `src/network/` read |
-| `crosspoint-reader/crosspoint-reader` @ `e6139861` | cloned with submodule |
-| `Free-Ink/freeink-sdk` @ `68425f8e` and `1ff02026` | `BoardConfig.h` compared; capability flags enumerated from source |
-| SDK compare | `GET /compare/1ff02026...68425f8e` → ahead 136, 103 files |
-| CrossInk compare | `GET /compare/develop...uxjulia:CrossInk:main` → ahead 616, behind 294 |
-| `PluginHostSymbols.inc` | 81 symbols, no bus access — read directly |
diff --git a/software/ecosystems/crosspoint-freeink/fork-network.md b/software/ecosystems/crosspoint-freeink/fork-network.md
deleted file mode 100644
index 5c6203c..0000000
--- a/software/ecosystems/crosspoint-freeink/fork-network.md
+++ /dev/null
@@ -1,228 +0,0 @@
-# The CrossPoint / FreeInk fork network
-
-> How ~1,600 forks of one e-reader firmware actually relate, how far each has
-> diverged, and which divergences could be patches instead of forks.
->
-> Snapshot **2026-09-04**. All figures from the GitHub API (`executed-success`
-> for retrieval). Nothing was built or run — no hardware. Divergence
-> interpretation is `inferred`.
-
-Records: [CrossPoint Reader](../../applications/crosspoint-reader/README.md) ·
-[FreeInk SDK](../../frameworks/freeink-sdk/README.md) ·
-[CrossPlay](../../applications/crossplay/README.md)
-
-## The shape of it
-
-```
-open-x4-epaper/community-sdk          MIT, CidVonHighwind et al.
-        │ code derived, re-architected
-        ▼
-Free-Ink/freeink-sdk                  ★248 · 95 forks · created 2026-06-03
-        │ git submodule
-        ▼
-crosspoint-reader/crosspoint-reader   ★7,538 · 1,621 forks · created 2025-12-03
-        ├── uxjulia/CrossInk          ★1,451 · true fork · itself heavily forked
-        │       └── CrumBLE, InkPointX, YACP, casper, CrossPlant, CrossDiTo …
-        ├── yattsu/biscuit            ★463 · true fork · stale
-        ├── trilwu/crosspet           ★216
-        ├── 0x1abin/crossmux          ★164 · true fork
-        ├── ma-r-s/crossplay          ★17  · true fork · games
-        └── MarsTechHAN/crosspoint-reader-mono  ★1 · true fork · PaperMono port
-```
-
-Note the inversion at the top: **CrossPoint predates its own SDK by six months.**
-FreeInk is a later re-architecture of the SDK CrossPoint was already using, not an
-upstream CrossPoint adopted.
-
-## Finding 1 — most "forks" are not forks
-
-Of fourteen named, actively-discussed derivatives, **only five are GitHub forks**
-(`fork: true` with a `parent`). The other nine were re-uploaded as fresh
-repositories and are **detached**: `fork: false`, `parent: null`.
-
-| Repository | ★ | GitHub fork? | Pushed |
-|---|---|---|---|
-| `uxjulia/CrossInk` | 1,451 | **yes** → crosspoint-reader | 2026-09-03 |
-| `yattsu/biscuit` | 463 | **yes** | 2026-04-08 |
-| `0x1abin/crossmux` | 164 | **yes** | 2026-09-04 |
-| `ma-r-s/crossplay` | 17 | **yes** | 2026-09-04 |
-| `MarsTechHAN/crosspoint-reader-mono` | 1 | **yes** | 2026-08-12 |
-| `imshentastic/CrumBLE` | 88 | **no — detached** | 2026-08-07 |
-| `aBER0724/crosspoint-reader-cjk` | 75 | **no — detached** | 2026-09-04 |
-| `yokki-vans/InkPointX` | 74 | **no — detached** | 2026-08-30 |
-| `juicecultus/crosspoint-reader-papers3` | 67 | **no — detached** | 2026-05-23 |
-| `Sichroteph/YACP` | 59 | **no — detached** | 2026-09-03 |
-| `tweakerinc/casper` | 25 | **no — detached** | 2026-09-03 |
-| `0xKnowles/CrossPlant` | 7 | **no — detached** | 2026-07-25 |
-| `dito94/CrossDiTo` | 5 | **no — detached** | 2026-08-21 |
-| `samfoy/CrossInk` | 1 | **no — detached** | 2026-08-24 |
-
-**Two consequences, pulling in opposite directions:**
-
-- GitHub's `/forks` listing **undercounts** the meaningful network — none of the
-  nine detached repositories appear in it, including CrumBLE and the CJK port,
-  which would rank in the top ten by stars.
-- The `1,621` figure simultaneously **overcounts**, because the overwhelming
-  majority of GitHub forks of any popular repository carry zero commits.
-
-So "1,621 forks" is close to meaningless in both directions. **Enumerate by name,
-not by API listing.** Anyone measuring this ecosystem from `/forks` alone will get
-the wrong answer twice over.
-
-Detachment also destroys the `ahead_by`/`behind_by` relationship — there is no
-shared history to compare against — which is why several rows below are blank.
-
-## Finding 2 — three distinct divergence patterns
-
-Comparing each true fork against upstream `develop`, the additions-to-deletions
-ratio separates them cleanly.
-
-| Fork | Ahead | Behind | Pattern |
-|---|---|---|---|
-| `ma-r-s/crossplay` | **+2,610** | −2 | **Additive** |
-| `0x1abin/crossmux` | +559 | −4 | **Additive** |
-| `uxjulia/CrossInk` | +616 | −285 | **Divergent** |
-| `trilwu/crosspet` | +309 | −536 | **Divergent + drifting** |
-| `yattsu/biscuit` | +52 | **−603** | **Stale** |
-
-**Additive** — thousands of commits ahead, almost nothing behind, and crucially
-**near-zero deletions**. New code lives in new files; upstream is merged
-continuously. CrossPlay is the textbook case: it is 2,610 commits ahead with
-**two** commits behind, and its measured diff was ~18,000 additions against ~860
-deletions. That is not a divergent codebase; it is upstream plus a large
-additive tree.
-
-**Divergent** — substantial deletions mean upstream-owned code was rewritten or
-removed. CrossInk at +616/−285 is a genuine second codebase, which is consistent
-with it being the only derivative that has itself become a fork parent.
-
-**Stale** — `biscuit` is the cautionary tale and worth naming. It is the
-**second-most-starred fork in the ecosystem** (463★), sits **603 commits behind**
-upstream, and has not been pushed since **2026-04-08**, five months before this
-snapshot. Star count is a popularity signal, not a maintenance signal, and here
-the two have completely decoupled.
-
-## Finding 3 — `behind_by` is a safety metric here, not tidiness
-
-In most ecosystems being behind upstream is a hygiene issue. In this one it is a
-**brick-risk signal**, for a specific reason: the target hardware is revised
-silently. Prior research in this project recorded two X3 variants and three X4 Pro
-variants appearing since July 2026 with no external versioning, and upstream
-carries the fixes as they are discovered.
-
-A fork 600 commits behind is therefore not merely missing features — it may be
-missing a panel-init change for a board revision the user actually owns. Combined
-with these devices' flashing risk (upstream ships a dedicated
-`docs/fix-bricked-xteink.md`), **currency matters more here than the star counts
-suggest**.
-
-This also cuts against detached forks specifically: without shared history there
-is no cheap way to even measure how far behind they are, and no `git merge` path
-to catch up.
-
-## Finding 4 — the fork network is upstream's stated design
-
-`SCOPE.md` in upstream contains this acceptance test for contributions:
-
-> **Is another popular CrossPoint fork already solving this well?** If yes, we
-> generally defer to that fork if it's not part of the core reading experience.
-> e.g. stats
-
-Upstream **deliberately delegates non-core features to its fork network** rather
-than absorbing them. The fork count is the governance model working, not
-fragmentation.
-
-CrossPlay states the downstream half of the same bargain in `LOCAL_SCOPE.md`:
-*"Reading stays the primary purpose… the reading experience is upstream's to own.
-We do not fork it, improve it, or diverge from it. Anything that makes reading
-better belongs upstream, so send it there."*
-
-That is a healthier arrangement than it looks from the raw fork number, and it
-explains the additive divergence pattern: forks that only add features have no
-reason to touch upstream code.
-
-## Finding 5 — patch portability, worked
-
-The interesting question is whether a fork's changes *need* to be a fork.
-CrossPlay is the only derivative that documents its own answer, so it is the one
-case that can be assessed rather than guessed. From its `LOCAL_SCOPE.md`:
-
-**28 upstream files touched**, of which roughly half are identity (README,
-LICENSE, workflows, templates) and ~15 are genuine code seams.
-
-| Class | Examples | Portability |
-|---|---|---|
-| **Append-only** | Two values appended to a `UIIcon` enum; two switch cases; 3 `.gitignore` lines; one `platformio.ini` include | **Trivial.** Appending to an enum preserves every value below it; a new switch case is a pure addition. These merge indefinitely |
-| **Bug fixes that belong upstream** | Thick-line direction fix in `GfxRenderer`; `openFileForAppend()` (upstream's write carries `O_TRUNC`, so nothing could append); `…FitWithin()` contain-vs-cover; `getScreenSafeArea()` bezel insets | **Should be PRs.** The bezel-inset one is a *correctness* issue affecting stock upstream on bezelled devices — upstream screens draw under the glass without it |
-| **Genuinely conflict-prone** | `HomeActivity.{cpp,h}` — 4 hooks plus a method in a file upstream actively develops | **The one real seam.** Mitigated by appending after upstream's rows so indices never shift |
-| **Cannot be upstreamed** | OTA release URL (pointing at upstream would flash a C3 image onto an S3); identity files | Inherent to forking |
-
-**Verdict for CrossPlay: ~90 % new files plus about a dozen small, mostly
-append-only seams.** It is far closer to "a patch series plus a large additive
-tree" than to a divergent codebase — and four of its seams arguably belong
-upstream, where both projects would benefit.
-
-**Whether this generalises is unknown.** CrossPlay is the only fork in the network
-that maintains an explicit seam inventory. The others were not analysed at file
-level in this pass, and the deletion counts above suggest CrossInk and crosspet at
-least are materially more invasive.
-
-## Finding 6 — forks of the SDK, not just the firmware
-
-CrossPlay's `.gitmodules` pins **`ma-r-s/freeink-sdk`** branch
-`x4pro-measured-insets`, not `Free-Ink/freeink-sdk`. Prior research recorded
-CrossInk pinning a different, older SDK commit.
-
-So a downstream project can have **two upstreams**, and — importantly —
-**a fork's behaviour can differ from upstream's without a single line of
-fork-owned code differing**, because the SDK underneath is a different revision.
-Any divergence analysis that reads only the firmware repository will miss this.
-
-FreeInk itself has 95 forks against 248 stars — a ~38 % ratio, far higher than
-CrossPoint's ~21 %, which is what an SDK meant to be embedded and adapted should
-look like.
-
-## Finding 7 — no licence fragmentation
-
-**All fourteen named derivatives are MIT**, matching upstream and the SDK. For an
-ecosystem this large and this informally governed, that is unusual and worth
-noting: there is no copyleft boundary anywhere in the graph, and code can move
-between forks and upstream freely.
-
-The exception is outside the fork network: `MagicCube/free-ink-on-paper-mono`, a
-FreeInk demo on the M5Stack PaperMono, has **no LICENSE file at all** and is
-therefore all-rights-reserved by default. See the
-[examples catalogue](../../../devices/m5stack/papermono/examples/best.md).
-
-## Relevance to the M5Stack PaperMono
-
-- **Upstream CrossPoint ships `[env:papermono]`** build environments — PaperMono
-  support is not fork-only.
-- **`MarsTechHAN/crosspoint-reader-mono`** is a true fork and the origin of the
-  `crosspoint-paper-mono-cjk` binary held in the
-  [PaperMono record's artifacts](../../../devices/m5stack/papermono/factory-firmware.md).
-- **CrossPlay carries `papermono` envs**, but its own scope document names only
-  the X4 Pro and reTerminal Sticky as targets, and nobody has reported running it
-  on a PaperMono.
-- **A plugin could not add NFC or LoRa.** Per carried-over analysis, the plugin
-  system runs browser JavaScript with no MCU-side execution and no peripheral
-  access — radios need a fork or an upstream feature. *Flagged for
-  re-verification; not confirmed in this pass.*
-
-## Method and limits
-
-Fork identity, stars, licences and push dates: GitHub REST API, 2026-09-04,
-authenticated. Divergence: `GET /repos/{upstream}/compare/develop...{owner}:{repo}:{branch}`.
-
-**Known limits:**
-
-- The compare endpoint **caps its file list at 300**, so per-file totals for large
-  forks are floors, not totals.
-- `sort=stargazers` on `/forks` is **unstable under pagination** — a prior pass
-  returned 1,421 rows containing only 1,001 unique repositories. Use `sort=oldest`.
-- Detached forks cannot be compared at all.
-- Only CrossPlay's changes were examined at file level; the other classifications
-  rest on aggregate add/delete ratios, which is weaker evidence.
-- Star and fork counts moved measurably *during* this research window
-  (CrossPoint 7,488 → 7,538; CrossInk 1,431 → 1,451). Figures are a snapshot, not
-  a constant.
diff --git a/software/ecosystems/crosspoint-freeink/m5unit-nfc-overflow.md b/software/ecosystems/crosspoint-freeink/m5unit-nfc-overflow.md
deleted file mode 100644
index 80068e9..0000000
--- a/software/ecosystems/crosspoint-freeink/m5unit-nfc-overflow.md
+++ /dev/null
@@ -1,381 +0,0 @@
-# `M5Unit-NFC` — stack buffer overflow in the NFC-A emulation listener
-
-> **Status: `inferred` from source. Not demonstrated, not exploited, not
-> disclosed.** No hardware was involved. This is a source-level analysis of a
-> publicly available library, written up because the finding is concrete and the
-> defective path is reachable from RF.
->
-> Analysed **2026-09-11** against `m5stack/M5Unit-NFC` @
-> `93745b547364f310cd64b5155a870103a7800a5d` (2026-06-10), archived locally at
-> `archive/software/ecosystems/crosspoint-freeink/nfc-source-snapshots/m5stack_M5Unit-NFC/`.
-
-## Summary
-
-`UnitST25R3916::readFIFO()` **does** bounds-check — but against a size its
-*caller* supplies. In the NFC-A emulation `Active` handler the caller passes the
-**FIFO length** where the function expects the **buffer capacity**, so the check
-compares a value against itself and passes. The read then proceeds into a 64-byte
-stack array.
-
-The same file gets it right ~70 lines earlier, in the `Idle` handler, using the
-correct idiom. So this is a single-call-site oversight, not a design assumption.
-
-**The bug is not "there is no bounds check". It is "the bounds check is given the
-wrong bound."** That distinction matters for anyone triaging or fixing it.
-
-## The mechanism
-
-`readFIFO` clamps correctly, given honest inputs —
-`src/unit/unit_ST25R3916.cpp:484`:
-
-```cpp
-uint32_t UnitST25R3916::readFIFO(uint16_t& actual, uint8_t* buf, const uint16_t buf_size)
-{
-    actual = 0;
-    uint16_t bytes{}; uint8_t bits{};
-    if (readFIFOSize(bytes, bits)) {
-        auto readSz = std::min<uint16_t>(bytes, buf_size);   // clamp to CAPACITY
-        if (!readSz) return false;
-        TRANSACTION_GUARD();
-        if (!readRegister(OP_READ_FIFO, buf, readSz, 0, false)) return false;
-        actual = readSz;
-        ...
-```
-
-The third parameter is named `buf_size` and is meant to be the capacity of `buf`.
-
-### The safe call site — `Idle` handler, `emulation_layer_a_ST25R3916.cpp:375`
-
-```cpp
-uint8_t rx[64]{};
-uint16_t rx_len{}, actual{};
-_u.readFIFOSize(bytes, bits);
-rx_len = std::min<uint16_t>(bytes, sizeof(rx));   // ← clamped to sizeof(rx)
-_u.readFIFO(actual, rx, rx_len);
-```
-
-Correct: `rx_len` can never exceed 64, so `min(bytes, rx_len)` ≤ 64.
-
-### The defective call site — `Active` handler, same file, line 444
-
-```cpp
-uint8_t rx[64]{};
-uint16_t rx_len{}, actual{};
-if (irq32 & I_rxe32) {
-    _u.readFIFOSize(bytes, bits);
-    rx_len = bytes;                          // ← NOT clamped. FIFO length, not capacity.
-
-    if (irq32 & (I_par32 | I_crc32 | I_err132 | I_err232) || rx_len <= 2) {
-        _u.readFIFO(actual, rx, rx_len);     // ← overflow path 1 (error branch)
-        ...
-    }
-    if (irq32 & I_rxe32) {
-        rx_len -= 2;
-        _u.readFIFO(actual, rx, rx_len);     // ← overflow path 2 (normal branch)
-        _data_flag = true;
-        auto state = _layer.receive_callback(rx, rx_len);
-        ...
-```
-
-With `rx_len = bytes`, the clamp inside `readFIFO` becomes
-`min(bytes, bytes) == bytes`. **The guard is inert.** `readRegister` then writes
-`bytes` into a 64-byte stack array.
-
-**Two distinct overflow paths** at this one site: the error branch and the normal
-receive branch.
-
-## How much can be written
-
-`readFIFOSize` reconstructs the length from the chip's FIFO status registers —
-`src/unit/unit_ST25R3916.cpp`:
-
-```cpp
-bytes = (s >> 8) | ((s & 0x00C0) << 2);
-```
-
-That is a 10-bit reconstruction (8 bits plus two high bits relocated to 8–9), and
-the ST25R3916's FIFO is **512 bytes**. So `bytes` is bounded by the hardware at
-512, against a **64-byte** destination — up to roughly **448 bytes of stack
-overwrite past the end of `rx`**, with contents taken from the RF frame.
-
-Corvelis's patch docstring gives a concrete real-world figure: their tested
-transport uses a **253-byte command (240-byte DATA payload)** — already ~189
-bytes past the buffer in normal, non-adversarial operation.
-
-## Reachability
-
-The `Active` handler runs when the device is in **NFC-A card emulation** and a
-reader is in the field. `rx_len` derives from a frame the reader sends.
-
-- **Precondition:** the device is emulating a tag, and the attacker is within NFC
-  range (centimetres).
-- **No authentication** exists at this layer — none is defined for NFC-A frame
-  reception.
-- **Not reachable in reader/poller mode**, which is why the vendor's own
-  `M5PaperMono-UserDemo` is unaffected: it probes tags rather than emulating one.
-
-So the exposure is specific to emulation firmware. Of the three PaperMono NFC
-implementations surveyed, **two emulate** — but only `Corvelis/m5-touch-card` uses
-this library, and it patches the bug before compiling.
-`ciniml/paper_name_plate` wrote its own stack in Rust and never touches this code.
-
-## Evidence that it is an oversight
-
-Three independent signals, all in the same library:
-
-1. **The correct idiom is used 70 lines earlier**, in the `Idle` handler of the
-   same file.
-2. **`nfc_layer_a.cpp:2227` declares `uint8_t rx[256]`** — a larger buffer is used
-   elsewhere for comparable work.
-3. **`readFIFO` was deliberately written to clamp.** The author built the guard;
-   one call site simply feeds it the wrong argument.
-
-Counted across the library, `uint8_t rx[64]` appears at
-`emulation_layer_a_ST25R3916.cpp:375` (safe), `:444` (defective), and
-`nfc_layer_a.cpp:2425`; `rx[256]` at `nfc_layer_a.cpp:2227`.
-
-## The third-party fix
-
-`Corvelis/m5-touch-card` ships `firmware/scripts/patch_m5unit_nfc.py` — a 374-line
-PlatformIO `pre:` script that rewrites the library in place at build time. For
-this bug it does two things:
-
-```cpp
-uint8_t rx[64]{};   →   uint8_t rx[256]{};      // both listener buffers
-```
-
-```cpp
-if (rx_len > sizeof(rx)) {                       // fail closed before the read
-    M5_LIB_LOGE("A RX oversized %u", rx_len);
-    _u.writeDirectCommand(CMD_CLEAR_FIFO);
-    _u.writeDirectCommand(CMD_UNMASK_RECEIVE_DATA);
-    return EmulationLayerA::State::Active;
-}
-```
-
-Both are needed: the resize accommodates the real 253-byte transport, and the
-guard handles anything larger. Note the patch **keeps the `rx_len` → `readFIFO`
-call shape** and adds an explicit test, rather than switching to
-`min(bytes, sizeof(rx))` as the `Idle` handler does. Either fixes it; the
-`Idle`-handler idiom is smaller and matches existing style.
-
-## Suggested upstream fix
-
-The minimal change matching the library's own existing pattern:
-
-```cpp
-// emulation_layer_a_ST25R3916.cpp, Active handler
-_u.readFIFOSize(bytes, bits);
-rx_len = std::min<uint16_t>(bytes, sizeof(rx));   // was: rx_len = bytes;
-```
-
-That alone closes both overflow paths. Enlarging `rx` to 256 is a **separate,
-also-necessary** change for correctness — at 64 bytes the listener silently
-truncates legitimate 253-byte frames even once memory-safe.
-
-Consider also auditing every other `readFIFO` call site for the same
-capacity-vs-length confusion; the API's shape invites it, and renaming the
-parameter or asserting on it would prevent recurrence.
-
-## Provenance — the clamp was dropped in porting, not merely forgotten
-
-**This is the single most important finding on the page, and it was established
-only on 2026-09-11.**
-
-`M5Unit-NFC` is a port of **STMicroelectronics' RFAL** (RF Abstraction Layer) for
-the ST25R3916. The file still carries commented-out RFAL call sites, left in as
-porting markers:
-
-```
-src/nfc/layer/a/emulation_layer_a_ST25R3916.cpp:182   //    rfalCheckDisableObsMode();
-src/nfc/layer/a/emulation_layer_a_ST25R3916.cpp:272   //       rfalCheckEnableObsModeRx();
-src/nfc/layer/a/emulation_layer_a_ST25R3916.cpp:397   // rfalCheckDisableObsMode(); …
-src/nfc/layer/f/emulation_layer_f_ST25R3916.cpp:208   //    rfalCheckDisableObsMode();
-src/unit/unit_ST25R3916.cpp:535                        //    rfalSetAnalogConfig(…)
-```
-
-**ST's original bounds every listen-mode FIFO read.** In
-`rfal_rfst25r3916.c`, all three call sites use the same clamp:
-
-```c
-st25r3916ReadFifo( gRFAL.Lm.rxBuf,
-                   MIN( *gRFAL.Lm.rxLen, rfalConvBitsToBytes(gRFAL.Lm.rxBufLen) ) );
-```
-
-— at `RFAL_LM_STATE_IDLE` (:3640), `RFAL_LM_STATE_READY_F` (:3713), and
-**`RFAL_LM_STATE_ACTIVE_A` (:3801)**. That last one is the state M5Stack's
-`update_active()` is a line-for-line port of: same IRQ mask, same `<= CRC_LEN`
-guard, same clear-FIFO/unmask pair, same `rxLen -= RFAL_CRC_LEN`. Every step
-matches **except** that `MIN(…)` is gone.
-
-So the asymmetry is not an oversight that happened to land in one of two
-handlers. **M5Stack preserved the clamp in `update_idle` (← ST's `LM_STATE_IDLE`)
-and dropped it in `update_active` (← ST's `LM_STATE_ACTIVE_A`).**
-
-Two details make the consequence worse than a simple omission:
-
-1. **ST's `st25r3916ReadFifo` does not clamp internally, and documents that**
-   (`st25r3916_com.h`: *"This function doesn't check whether `length` is really
-   the number of available bytes in FIFO"*). ST relies entirely on the call-site
-   `MIN`. M5Stack's `readFIFO` **does** clamp internally — a safer design — which
-   is exactly why passing the FIFO count as `buf_size` *silently* defeats it.
-   The safer API made the bug invisible.
-2. **In RFAL, `rxBuf`/`rxBufLen` are caller-supplied** to `rfalListenStart()`, so
-   the bound is a real parameter the application owns. M5Stack replaced that with
-   a **64-byte stack local inside the handler**. That substitution is what turns a
-   truncation into a stack write.
-
-### Attribution
-
-The repository is MIT, `Copyright (c) 2025 M5Stack Technology CO LTD`, with **no
-`NOTICE`, no `THIRD-PARTY` file, and zero mentions of ST or RFAL in the README**
-(verified). ST's RFAL ships under ST's own licence, not MIT. The maintainer has
-publicly described the M5UnitUnified libraries as
-「新規に書き起こし」 — *"newly written from scratch"*
-([Qiita, 2024-12-11](https://qiita.com/GOB/items/b96a96ff5bbc112303df)).
-
-**Precision, since that quote is load-bearing.** The article is about the
-**M5UnitUnified framework** and is dated 2024-12-11 — it **predates `M5Unit-NFC`**
-(repository created 2025-10-27), lists M5Unit-RFID as not yet released, and
-contains **no NFC content whatsoever**. The statement is therefore about the
-*family's* authoring policy, not a specific claim about this library. It is quoted
-as context for the attribution question, **not** as a denial regarding
-`M5Unit-NFC`.
-
-The discrepancy is recorded as an observation. **No legal conclusion is drawn
-here**, and none should be read into it.
-
-## It is the only unclamped handler of four
-
-The library has four emulation receive handlers. Three clamp correctly:
-
-| Layer | Handler | Buffer | Clamped? |
-|---|---|---|---|
-| NFC-A | `update_idle` (:375) | `rx[64]` | ✅ `std::min(bytes, sizeof(rx))` |
-| NFC-A | **`update_active` (:444)** | `rx[64]` | ❌ **`rx_len = bytes;`** |
-| NFC-F | `:357` | `rx[128]` | ✅ |
-| NFC-F | `:393` | `rx[128]` | ✅ |
-
-The NFC-F sibling clamps in **both** of its handlers. A single outlier among four
-is much harder to read as intentional than one-of-two.
-
-Also noted, unexplained: the `max_fifo_depth()` override that would return
-`MAX_FIFO_DEPTH` is **commented out** at `:56–61`.
-
-## The same mistake was already found — and fixed — elsewhere in this library
-
-**PR #4** (`Sped0n`, an Espressif engineer, merged 2026-05-20) fixed the
-*identical semantic confusion* in the reader path:
-
-> *"`nfcaReceive()` treated the caller-provided RX length as the expected frame
-> size. In practice that value is the RX buffer capacity."*
-
-The fix added the comment *"`rx_len_org` is the caller's buffer capacity, not an
-expected frame length."* **The audit was never generalised to the emulation
-layer.** The project has therefore already recognised this exact class of error
-once, in code written by the same author, and the emulation site survived.
-
-## Why this survived: the tested seam stops one layer above the bug
-
-The library is **much better tested than its ecosystem reputation suggests** —
-`test/` contains **17 host-test files**, including `isodep_test.cpp`,
-`nfca_test.cpp`, `nfcb_test.cpp`, `nfcf_test.cpp`, `nfcv_test.cpp`,
-`mifare_test.cpp`, `mifare_classic_crypto1_test.cpp`, `ndef_test.cpp` (21 KB),
-`aes_test.cpp` and `desfire_detail_test.cpp`.
-
-They work by mocking a single seam: `NFCLayerInterface::transceive` is pure
-virtual, and `test/isodep_test.cpp` substitutes a `ScriptedLayer` to drive ISO-DEP
-I/R/S block framing, automatic WTX extension, chaining and APDU status checking
-entirely on the host.
-
-**That seam sits immediately above the defect.** `transceive` is the boundary; the
-overflow is in the register/FIFO handling *below* it, in
-`emulation_layer_a_ST25R3916.cpp`. A developer working on this project stated the
-division precisely:
-
-> 「**プロトコルロジックは実機不要でテスト可能**」… 「実機知見が必須なのは別レイヤー:
-> ST25R3916 のレジスタ/FIFO操作」
->
-> *"The protocol logic is testable without hardware… What genuinely requires
-> hardware knowledge is a different layer: ST25R3916 register/FIFO manipulation."*
-> — [`ippoan/alc-app-s3#107`](https://github.com/ippoan/alc-app-s3/issues/107)
-
-So the mocked tests **cannot reach this code by construction**, and the layer that
-contains it has no host tests at all. That is a satisfying and unflattering
-explanation for how an unclamped FIFO read survived in a project that otherwise
-tests carefully.
-
-It also suggests the cheapest possible fix path: the bug is a pure function of
-`bytes` and `sizeof(rx)`, so a test that drives `readFIFO` with an oversized FIFO
-count would catch it **without hardware** — if the seam were pushed one layer
-down.
-
-## Nobody has reported it
-
-Searched 2026-09-11 across: the issue tracker (all 8 issues/PRs read), all 4
-forks, Qiita (15 queries, full article bodies), Zenn (0 results for every relevant
-query), and GitHub issue search. **No discussion of this inconsistency anywhere.**
-
-Two crash reports were examined and **excluded**:
-
-- `BruceDevices/firmware#2787` — *"ST25R3916 … Intermittent Freezes"*. Different
-  codebase (ST's RFAL directly, not `M5Unit-NFC`), its card-emulation path is not
-  wired in, and the reporter self-diagnosed it as an I²C bus race.
-- `ippoan/alc-app-s3#96` — an ESP-IDF `abort()` at boot from a legacy/new I²C
-  driver symbol conflict. A build-configuration fault, not a memory fault.
-
-Neither is evidence for this defect. **Absence of reports is expected** given the
-reachability analysis below, and is not reassurance.
-
-## Reachability — stated conservatively
-
-The shipped NFC-A emulation example emulates **MIFARE Ultralight / NTAG 213**,
-Type 2 tags whose *compliant* reader commands are ≤ 6 bytes plus CRC. **A
-standards-conforming reader will not produce a >64-byte frame here.** Triggering
-this requires either a non-compliant or deliberately hostile reader, or a spurious
-FIFO state.
-
-One point cuts the other way, and it matters: **the error branch at `:451` also
-reads unbounded**, and it runs on parity/CRC/framing errors — which *do* occur
-naturally with marginal antenna coupling. That path reads the FIFO purely to log
-`rx[0]`.
-
-
-
-- **Not tested.** Nothing was built, flashed, or exercised against a reader. No
-  proof-of-concept exists and none was attempted.
-- **Exploitability not assessed.** A stack overwrite on an ESP32-S3 with RF-
-  controlled data is serious on its face, but whether it is controllable enough
-  for anything beyond a crash was not analysed. **Do not cite this as
-  "exploitable"** — cite it as "unbounded write, untested".
-- **Not disclosed.** No issue filed, no contact with M5Stack. That is a decision
-  for the repository owner, not something to action unilaterally from a research
-  pass.
-- ~~Current upstream not checked~~ — **checked 2026-09-11: the defect is live on
-  both branches.** `main` is `93745b5` (2026-06-10) and still has it. **`develop`
-  is under active development *today*** — HEAD `3b6ae05`, 2026-09-11 — and
-  `rx_len = bytes;` remains, at line 453. Only 5 commits have ever touched this
-  file, none of them changing the clamp, and **no fork has modified it** (all four
-  are byte-identical, one modulo line endings).
-
-  Worth noting for tone: `develop`'s HEAD commit is itself titled *"Check that a
-  capability container fits before trusting its block count"* — the maintainer is
-  **actively hardening bounds checks in adjacent code right now**. This is a live,
-  maintained project, not an abandoned one.
-
-## Reproduction of the analysis
-
-```bash
-git clone https://github.com/m5stack/M5Unit-NFC && cd M5Unit-NFC
-git checkout 93745b547364f310cd64b5155a870103a7800a5d
-sed -n '440,470p' src/nfc/layer/a/emulation_layer_a_ST25R3916.cpp   # defective site
-sed -n '370,382p' src/nfc/layer/a/emulation_layer_a_ST25R3916.cpp   # safe site
-sed -n '484,505p' src/unit/unit_ST25R3916.cpp                       # readFIFO
-```
-
-## See also
-
-- [NFC implementation comparison](nfc-implementation-comparison.md) — the three approaches, and the other six defects the same patch fixes
-- [`components/stmicroelectronics/st25r3916`](../../../components/stmicroelectronics/st25r3916/README.md)
-- Archived source, both the defective library and the patch that fixes it:
-  `archive/software/ecosystems/crosspoint-freeink/nfc-source-snapshots/`
diff --git a/software/ecosystems/crosspoint-freeink/m5unit-nfc-practical.md b/software/ecosystems/crosspoint-freeink/m5unit-nfc-practical.md
deleted file mode 100644
index e99c5dc..0000000
--- a/software/ecosystems/crosspoint-freeink/m5unit-nfc-practical.md
+++ /dev/null
@@ -1,264 +0,0 @@
-# Using `M5Unit-NFC` in practice — traps, timings and measured numbers
-
-> Practical working knowledge of M5Stack's `M5Unit-NFC` library and the ST25R3916,
-> collected from Japanese-language sources and **cross-verified against library
-> source** on 2026-09-11.
->
-> Source verifications are `executed-success`. **The measurements are other
-> people's**, taken on their hardware, and are attributed. Nothing here was
-> reproduced by this project — no device exists.
-
-Most of the substance comes from `ippoan/alc-app-s3`, a Japanese commercial
-driver roll-call kiosk whose issue tracker is the best public bug-hunting record
-of this library. Their method is notably disciplined: they instrument, measure,
-and **retract their own hypotheses** when data contradicts them.
-
-## Get logging on before anything else
-
-Under ESP-IDF this is the highest-leverage single setting:
-
-> 「ビルドのどこにも `M5_LOG_LEVEL` / `CORE_DEBUG_LEVEL` が定義されておらず、
-> `library_log.hpp` の `logOutputLevel` が `None` に落ちて `M5_LIB_LOGE` 含む全ログが
-> コンパイル時に消えていた」
->
-> *"Neither `M5_LOG_LEVEL` nor `CORE_DEBUG_LEVEL` was defined anywhere in the
-> build, so `logOutputLevel` fell to `None` and **every log including
-> `M5_LIB_LOGE` was compiled out**."*
-
-Silently invisible without it: `CHECK_MODE`'s *"Illegal mode"*, `wait_for_FIFO`'s
-*"Timeout"*, and `detect`'s *"Detected:"*. Fix:
-
-```cmake
-target_compile_definitions(<M5Utility target> PUBLIC M5_LOG_LEVEL=4)
-```
-
-## `config()` does not configure the chip
-
-The single most costly API trap, and it is *by design*:
-
-> 「`UnitST25R3916::config()` は cfg 構造体を書き換えるだけで実チップには反映されない
-> （`configureNFCMode()` を呼んで初めて反映される、`begin()` 内で一度呼ばれるのみ）」
->
-> *"`config()` merely rewrites the cfg struct and is not reflected on the actual
-> chip — it is only applied once `configureNFCMode()` is called, which happens
-> only once inside `begin()`."*
-
-This matches the framework's documented contract: in M5UnitUnified, only
-`readFoo` / `writeFoo` are specified to touch hardware; `config()` is a settings
-accessor applied at `begin()`.
-
-**Consequence:** switching NFC-F ↔ NFC-B by calling `config()` alone leaves the
-chip in the old mode. Call `configureNFCMode()` explicitly on every mode change.
-This is also the root cause of upstream issue #1.
-
-Two related facts, both from instrumented runs:
-
-- `configureNFCMode()` **alone does not drop the RF field** (`Already tx_en`) —
-  drive the OP register directly to break it.
-- After a reconfiguration, WUPB in the first **~20 ms fails 100 %**. They run a
-  60 ms settle and note ≥100 ms would be safer.
-
-## Default timeouts are short, and asymmetric
-
-**Verified against library headers** — the single-PICC overloads are much tighter
-than the vector ones:
-
-| Layer | `detect(PICC&)` | `detect(vector&)` | Header |
-|---|---|---|---|
-| NFC-A | **100 ms** | 1000 ms | `nfc_layer_a.hpp:155,165` |
-| NFC-B | **50 ms** | 1000 ms | `nfc_layer_b.hpp:165,177` |
-| NFC-F | **100 ms** | **500 ms** | `nfc_layer_f.hpp:98,107` |
-
-Also verified: `TIMEOUT_REQ_WUP_B{5}`, **`TIMEOUT_ATTRIB{50}`**, `TIMEOUT_HLTB{5}`,
-`TIMEOUT_DESELECT{5}` (`src/nfc/b/nfcb.hpp:266-269`).
-
-> ⚠ One number in the original report is wrong: it gives NFC-F's vector default
-> as 1000 ms. The header says **500 ms**. Their conclusion — that accidentally
-> using the vector overload is why NFC-F worked — still holds.
-
-## `detect()` halts the card on NFC-B
-
-Not a passive observer. **Verified at `nfc_layer_b.cpp:112`:**
-
-```cpp
-hlt(rx);  // If you don't perform hlt, it will be detected again
-```
-
-`detect()` sends HLTB immediately after detection, dropping the card into HALT.
-`select()` then issues WUPB to wake it — and some cards **never answer WUPB from
-HALT**. A Japanese driving licence is one of them:
-
-> 「`detect()` は検出直後に内部で HLTB を送ってカードを HALT に落とし、続く `select()`
-> 内の WUPB にこの免許証は一度も応答しない」
-
-**Correct pattern for such cards: skip `detect()` and poll `select()` only.**
-WUPB also wakes IDLE cards, so it doubles as presence detection and sends no
-HLTB.
-
-## ISO-DEP framing is not optional
-
-After ATTRIB, APDUs **must** be wrapped as I-blocks (`PCB 0x02`/`0x03`). Raw
-APDUs are *silently ignored* — the card simply never answers and you burn the
-full frame-waiting time. Construct `NFCBFileSystem` (its constructor lifts
-FWI/FSC off the activated PICC into the isoDEP config) and send via
-`isoDEP()->transceiveAPDU()`.
-
-Note Type-B and Type-A share the same `IsoDEP` object. **FeliCa does not use
-ISO-DEP at all** — IDm reads only.
-
-## RF regulator voltage is the detection-margin knob
-
-The most reusable register-level finding:
-
-> 「**RF レギュレータ電圧 (reg 0x2C) が検出マージンの主因だった**。`configure_nfc_b()`
-> 固定値の `0xD0` → `0xF8`（最大）でカード位置のシビアさが大きく改善」
->
-> *"The RF regulator voltage (register `0x2C`) was the main driver of detection
-> margin. Changing the hardcoded `0xD0` to `0xF8` (maximum) massively improved how
-> fussy card positioning was."*
-
-TX driver resistance was already at minimum, so `0x2C` was the only headroom left
-in the register map.
-
-> ⚠ **Do not confuse registers named `0x2C`.** On the ST25R3916, `0x2C` is the RF
-> regulator voltage. On the SSD1677/SSD1683 e-paper controllers documented
-> elsewhere in this knowledge base, command `0x2C` writes `VCOM`. Unrelated.
-
-## The "slow NFC" investigation — and its real cause
-
-Worth reading as a method example. Measured on their production unit:
-
-| Card | Excess latency |
-|---|---|
-| Driving licence (Type-B) | **≈ 4.1 s** |
-| Suica (FeliCa) | **≈ 0.75 s** |
-
-**Four hypotheses were tested and falsified** — concurrent SPI/WebSocket load
-(129 ms difference, "noise"), PSRAM thread-stack placement (moved 8 KB, no
-effect), always-on polling (made it worse), and Type-B HALT carryover (rejected by
-code reading). Their note on why instrumentation mattered:
-
-> 「「変更は効いているが原因ではない」を分離できたのは計器のおかげ」
-> *"It was only thanks to the instrumentation that we could separate 'the change
-> took effect' from 'the change was the cause'."*
-
-**The actual cause was physical.** Mounting the NFC unit next to a PoE base
-(W5500 + LAN magnetics + metal) halved antenna amplitude:
-
-> 「アンテナ振幅が 34 → 18 に半減し、免許証 (Type-B) は WUPB に応答できず痕跡ゼロ」
-
-At amplitude 18, **112 consecutive cycles returned −2**. Moving it away restored
-34 and gave 3/3 immediately.
-
-**Operational heuristic worth keeping: `amp ≈ 34` is healthy, `≤ 20` is a dead
-field.** Read it with `CMD_MEASURE_AMPLITUDE` before blaming software.
-
-### Measured per-stage cost
-
-| Stage | Per pass |
-|---|---|
-| F (FeliCa) | **91 ms** |
-| A (NFC-A + cert check) | **140 ms** |
-| B (licence APDU session) | **200 ms** |
-| **Full F→A→B cycle** | **431–448 ms** |
-
-They explicitly corrected their own code comment claiming detection was *"a few
-ms"*: the measured figures are **10–30× higher**.
-
-A structural consequence: `ensure_mode()` does field-off (10 ms) →
-`configureNFCMode()` → 60 ms settle on every mode change, so **the card is
-power-cycled three times per cycle**. `nfc_initial_field_on()`
-(`unit_ST25R3916.cpp:364-377`) contains a **5 ms wait** — that is what satisfies
-the ISO 14443-3 guard time at the head of each poll.
-
-## FeliCa / transit cards
-
-**Chip selection trap, stated bluntly by the same author:**
-
-> 「⚠ 命名の罠: **Unit RFID (MFRC522) / Unit RFID2 (WS1850S) は FeliCa 非対応**
-> （Type-A/B のみ）。交通系IC を読むには必ず **ST25R3916 搭載の「Unit NFC」**」
->
-> *"Naming trap: Unit RFID (MFRC522) and Unit RFID2 (WS1850S) do **not** support
-> FeliCa — Type-A/B only. For transit cards you must use the ST25R3916-based
-> 'Unit NFC'."*
-
-> ⚠ A widely-linked Qiita article states that Unit NFC (SKU **U216**) carries a
-> **PN532**. **It does not** — U216 is the ST25R3916, as that article's own linked
-> product page shows. Do not propagate it.
-
-System codes:
-
-```cpp
-constexpr uint16_t jtic_system_code[] = {
-    0x0003,  // Suica, PASMO, ICOCA, PiTaPa, TOICA …
-    0x80DE,  // IruCa
-};
-```
-
-Poll `0x0003` first, fall back to `0xFFFF` (wildcard). Reading an IDm needs only
-`detect()` + `picc.idmAsString()` — `activate()`/`read16()` are for
-balance/history and unnecessary, since the IDm needs no authentication.
-
-**IDm semantics, which matter if you are tempted to use it as an identity:**
-Mobile Suica runs real FeliCa on a secure element, so the IDm is **fixed per
-device**. But one person may have several (card, phone, watch), it changes on
-handset replacement, and — decisively —
-
-> 「IDm は平文で読めリプレイ可 → **単独で本人確認にはしない**」
-> *"The IDm is readable in the clear and replayable — never use it alone for
-> identification."*
-
-### Type-A UID caution
-
-| Source | UID length | UID0 | Usable as identity? |
-|---|---|---|---|
-| Phone (HCE) | 4 | `0x08` | **No** — random UID per ISO/IEC 14443-3 §6.4.4 |
-| Employee card | 7 | `0x05` | Yes |
-
-## ESP-IDF build blockers
-
-Neither is a library bug, but both abort at boot:
-
-```
-CONFIG_I2C_SKIP_LEGACY_CONFLICT_CHECK=y
-CONFIG_RMT_SKIP_LEGACY_CONFLICT_CHECK=y
-```
-
-Legacy `driver/i2c.h` and new `driver/i2c_master.h` symbols link into one binary,
-and `check_i2c_driver_conflict` — an `__attribute__((constructor))` — calls
-`abort()` before `app_main`. The RMT equivalent bites if you also drive a WS2812.
-
-The library **does** support ESP-IDF natively (an `app_main` path), not Arduino
-only.
-
-## The library is host-testable — an under-advertised feature
-
-`test/` contains **17 host-test files** covering ISO-DEP, APDU, NFC-A/B/F/V,
-MIFARE, Crypto1, AES and NDEF, by mocking the single `NFCLayerInterface::transceive`
-seam with a `ScriptedLayer`.
-
-> 「**プロトコルロジックは実機不要でテスト可能**。「ISO14443-4 は実機 trial&error でしか
-> 検証できない」は誤りだった」
->
-> *"The protocol logic is testable without hardware. The belief that
-> 'ISO14443-4 can only be verified by trial and error on real hardware' was
-> wrong."*
-
-What genuinely needs hardware is the layer **below** that seam: register/FIFO
-handling and bit-oriented anticollision framing — which is also where
-[the unclamped FIFO read](m5unit-nfc-overflow.md) lives.
-
-## Limits of this page
-
-- **Nothing here was reproduced.** Every measurement is from `ippoan/alc-app-s3`'s
-  hardware and workload — a PoE-powered kiosk reading Japanese driving licences.
-  Timings will differ elsewhere.
-- The register and timeout values **were** verified against library source; the
-  behavioural narratives were not.
-- Their stack is Rust-over-C++-shim, so some API friction is specific to that.
-
-## See also
-
-- [`M5Unit-NFC` unclamped FIFO read](m5unit-nfc-overflow.md) — the defect in the layer below the tested seam
-- [NFC implementation comparison](nfc-implementation-comparison.md)
-- [`components/stmicroelectronics/st25r3916`](../../../components/stmicroelectronics/st25r3916/README.md)
diff --git a/software/ecosystems/crosspoint-freeink/new-papermono-projects-2026-09.md b/software/ecosystems/crosspoint-freeink/new-papermono-projects-2026-09.md
deleted file mode 100644
index bccd328..0000000
--- a/software/ecosystems/crosspoint-freeink/new-papermono-projects-2026-09.md
+++ /dev/null
@@ -1,194 +0,0 @@
-# New PaperMono projects — 2026-09-07 sweep
-
-> The PaperMono shipped **2026-08-21**. An earlier survey on 2026-09-01
-> catalogued 43 repositories. This is a re-sweep two weeks post-launch, and it
-> found **five projects that did not exist or were not visible before** —
-> including two in **Rust**, a language the earlier catalogue contained none of,
-> and one that **implements NFC on this board**.
->
-> Retrieved **2026-09-07**, `executed-success` (GitHub API + raw file reads).
-> Nothing was built or run.
-
-## What is new since 2026-09-01
-
-| Repository | Lang | Licence | Created | Pushed | What |
-|---|---|---|---|---|---|
-| **[`ciniml/paper_name_plate`](https://github.com/ciniml/paper_name_plate)** | **Rust** | none | 2026-09-05 | 2026-09-06 | **Bare-metal `no_std` firmware with a full NFC stack** |
-| [`canardleteer/papermono-rs`](https://github.com/canardleteer/papermono-rs) | **Rust** | MIT | 2026-09-01 | 2026-09-06 | Embedded Rust workspace — `crates/`, `firmware/`, `host/`, `xtask/` |
-| [`CitizenRacer/M5PaperMonoLite`](https://github.com/CitizenRacer/M5PaperMonoLite) | C++ | MIT | 2026-09-04 | 2026-09-04 | ESPHome support — **targets the Lite**, self-described *"I have no idea what I'm doing"* |
-| [`atreyap31-cell/mono-note-mini`](https://github.com/atreyap31-cell/mono-note-mini) | C | none | 2026-08-24 | 2026-09-06 | Voice-only note companion; ships a case, emulator and server |
-| [`hectorzin/M5PaperMono-HomeAssistant-ESPHome`](https://github.com/hectorzin/M5PaperMono-HomeAssistant-ESPHome) | C | none | 2026-08-27 | **2026-09-07** | In the earlier catalogue; **still actively pushed** |
-
-**Rust is the notable shift.** The 2026-09-01 catalogue was entirely C/C++ plus a
-few TypeScript host tools. Two independent embedded-Rust efforts appeared within
-a fortnight of launch, one of them from **ciniml (Kenta Ida)**, a well-known
-Japanese embedded engineer.
-
-## `ciniml/paper_name_plate` — the important one
-
-**Bare-metal `no_std` Rust on `esp-hal`, and it implements NFC on this board.**
-This is the first third-party artifact found anywhere that drives the PaperMono's
-radios.
-
-```
-src/st25r3916.rs        28,899 B   ST25R3916 NFC driver
-src/t2t_emu.rs          19,784 B   NFC Forum Type 2 Tag emulation
-src/board.rs            14,579 B   PaperMono board init
-src/pm1.rs               8,397 B   M5PM1 PMIC driver
-src/ioe1.rs              6,291 B   M5IOE1 expander driver
-src/ndef.rs              5,389 B   NDEF encoding
-src/isodep.rs            5,343 B   ISO-DEP
-src/ssd1677/             —         panel driver, 4-gray LUTs, framebuffer
-src/ft6336.rs            3,233 B   touch
-```
-
-Toolchain: `espup`/`esp` Xtensa channel, `xtensa-esp32s3-none-elf`, **esp-hal
-1.1.x**, `embedded-graphics 0.8`, `espflash`. Blocking rather than `embassy`, by
-choice, with a stated intent to reconsider when NFC/touch/button events need it.
-
-Its `DESIGN.md` explains why it writes its own drivers rather than using existing
-crates: *"4-gray, OTP waveforms, reset via IOE1 — existing crates do not
-anticipate the 800×480 4-gray + external-reset combination."*
-
-> ⚠ **No `LICENSE` file.** All-rights-reserved by default. Read it for technique;
-> do not copy code without asking.
-
-## It independently confirms this knowledge base's pin map
-
-`DESIGN.md` was written from the author's own reading of the hardware, and it
-agrees with the PaperMono device record on essentially every contested point.
-That is unusually strong corroboration — two independent derivations converging.
-
-| Finding | This knowledge base | `paper_name_plate` `DESIGN.md` |
-|---|---|---|
-| **`PYGn` is 1-based** | recorded, with the `M5IOE1_PIN_3 = 2` off-by-one warning | *"P1..P8 → L register bit0..7, P9..P14 → H register bit0..5 (**docs' `PYGn` = 1-based**)"* |
-| **Frontlight is M5PM1 GPIO3** | recorded; an earlier pass wrongly called the vendor page defective | *"Frontlight: **GPIO3** … FUNC0 → `11` (PWM0), `PWM_FREQ = 5000 Hz`"* |
-| **EPD reset = M5IOE1 IO5** | recorded | *"RST = M5IOE1 **IO5 (0-based index 4)**"* — states the off-by-one explicitly |
-| **NFC enable = M5IOE1 IO4** | identified as **missing from the FreeInk SDK** | *"NFC … power enable via **M5IOE1 IO4**"* |
-| **LoRa reset = IO10, ant switch = IO2** | identified as missing from the SDK | *"**IO10 = LoRa RST, IO2 = LoRa ANT SW**"* |
-| **LoRa SPI pins** | MOSI 38 / MISO 40 / CLK 39 / NSS 41, BUSY 21, IRQ 5 | identical |
-| **IP2315 bus hazard** | recorded from the vendor warning | *"IP2315 (0x75). **Do not keep it on the bus for long** (doc warning). Don't touch it."* |
-| **SSD1677 4-gray via OTP** | `0x1A=0x5A` + `0x22=0xD7` | identical |
-| **Deep-sleep recovery** | — | *"**hardware reset (IOE1 IO5) is required** to wake"* — new |
-| **Bus speeds** | 100 kHz for PM1/IOE1 | *"PM1/IOE1 default 100 kHz (400 selectable); **touch/NFC at 400 kHz**"* — new |
-
-**On the 20 vs 40 MHz panel-clock conflict** this record has tracked: `DESIGN.md`
-says *"reference implementations are 20–40 MHz"* — acknowledging both without
-resolving it. So the conflict is real and visible to third parties, not an
-artifact of this project's reading.
-
-## New findings from it
-
-**M5GFX's waveform LUTs are FreeBSD-licensed and reusable.** `DESIGN.md` states
-*"M5GFX's quality/text/fast/fastest LUTs are FreeBSD-licensed, so they can be
-reused"*, and `src/ssd1677/lut.rs` is annotated as being taken from M5GFX under
-that licence. That materially changes the
-[libraries licensing picture](../../libraries/README.md): the e-paper
-*driver* libraries skew copyleft, but **M5Stack's own waveform tables are
-permissive**.
-
-**A booster-parameter discrepancy.** `DESIGN.md` gives the SSD1677 init as
-`0x0C AE C7 C3 C0 40`. This project's
-[OTP-demo analysis](../../../devices/m5stack/papermono/features/epaper-display.md)
-recorded `0x0C = {0xAE, 0xC7, 0xC3, 0xC0, 0x80}` — **the fifth byte differs,
-`0x40` vs `0x80`**. One of the two is wrong, or they are from different sources.
-**Unresolved**; worth checking against the OTP demo directly before either is
-relied on.
-
-**An internal contradiction in their own doc.** The IO list reads
-*"… IO4 = NFC_EN … IO0(= P1?) = RTC INT, **IO4 = IMU INT**"* — assigning IO4
-twice. This knowledge base's schematic extraction puts **RTC INT on M5PM1 G0 and
-IMU INT on M5PM1 G4**, not on the expander. Their `IO4 = IMU INT` line is
-probably an M5PM1/M5IOE1 mix-up — the exact `PYGn` ambiguity documented in
-[`pin-naming-and-the-pyg-ambiguity.md`](../../../devices/m5stack/papermono/pin-naming-and-the-pyg-ambiguity.md),
-appearing in the wild.
-
-## What this changes
-
-**NFC on the PaperMono is proven, not theoretical.** A working third-party
-ST25R3916 driver with tag emulation exists. The
-[radios assessment](radios-on-papermono.md) argued the hardware was reachable
-from firmware source; this is the demonstration.
-
-**Two independent implementations now confirm the expander/PMIC approach.**
-`paper_name_plate` wrote its own `pm1.rs`/`ioe1.rs` rather than using the FreeInk
-SDK — the same conclusion that assessment reached: the abstraction is optional.
-
-**Rust is a viable path**, with `esp-hal 1.1.x` and `embedded-graphics 0.8`
-handling this board.
-
-**LoRa remains undemonstrated.** `paper_name_plate` lists the SX1262 pins and
-explicitly scopes it out (*"out of scope for this project for now"*). No project
-found anywhere drives LoRa on this board.
-
-
-## Second sweep — 2026-09-11
-
-Four days on, **two more projects**, one created the same day.
-
-| Repository | Lang | Licence | Created | Pushed | What |
-|---|---|---|---|---|---|
-| **[`fperuzzo72/crossplay-papermono`](https://github.com/fperuzzo72/crossplay-papermono)** | C | MIT | **2026-09-11** | **2026-09-11** | **CrossPlay ported to the PaperMono** |
-| [`Corvelis/m5-touch-card`](https://github.com/Corvelis/m5-touch-card) | C++ | MIT | 2026-09-07 | 2026-09-08 | **Second independent NFC project** — tap-to-exchange business cards |
-
-### `crossplay-papermono` — the port is happening
-
-Branch `papermono-bringup`, ~430 MB (a full CrossPlay tree), described as
-*"CrossPlay no M5Stack Paper Mono: bring-up a partir de `ma-r-s/crossplay`"*.
-Commits from 2026-09-11 are real bring-up, not scaffolding:
-
-- *"papermono: give the render task the same 16384 stack the x4pro render task uses"*
-- *"papermono: carry the stack flag into the release envs and build"*
-- *"papermono: publish the release asset its updater asks for"*
-- *"papermono: offer it on the Install button and in the install doc"*
-- *"Point the update check at this fork's releases, not upstream's"*
-
-That last commit is **exactly the seam CrossPlay's own `LOCAL_SCOPE.md` documents
-as unavoidably fork-local** — the OTA URL, which if left pointing upstream would
-flash a C3 image onto an S3. An independent porter hit it and fixed it the same
-way, which is a small validation of that fork-portability analysis.
-
-It is `fork: false`, `parent: null` — **detached**, the pattern that makes 9 of 14
-named forks invisible to GitHub's `/forks` endpoint.
-
-**This retires the "Class P" classification** applied to CrossPlay-on-PaperMono in
-the earlier catalogue: support is no longer merely present in a build config,
-someone is actively bringing it up.
-
-### `m5-touch-card` — NFC, independently, again
-
-*"PaperMonoとスタックチャンで、タッチして名刺交換。NFC対応ファームウェアとスマホ編集アプリ。"*
-— tap-to-exchange business cards using the PaperMono and Stack-chan, with NFC
-firmware **and a companion smartphone editing app**. Root layout (`firmware/`,
-`mobile/`, `protocol/`, `migration/`, `release/`, `docs/`) is a finished product
-rather than a demo, and it ships four embedded hardware demo videos. Recent work
-includes *"Improve PaperMono idle sleep and minute/hourly display refresh"*.
-
-### What the two sweeps together show
-
-**NFC is the emergent killer application.** Three independent implementations now
-exist — the vendor demo, `ciniml/paper_name_plate` (Rust) and
-`Corvelis/m5-touch-card` (C++) — and the latter two converged, without contact,
-on the same use case: *tap to exchange contact details*. For a device that is a
-screen plus a tag emulator, that is the obvious product, and the market found it
-within three weeks of launch.
-
-**LoRa remains at zero.** Across three sweeps no project drives it. Every one
-either scopes it out explicitly (`paper_name_plate`) or ignores it.
-
-**Growth rate:** 43 repositories on 2026-09-01 → 5 new by 09-07 → 2 more by
-09-11. Three weeks post-launch and still compounding.
-
-## Method and limits
-
-Searched the GitHub repository API for `papermono`, `paper+mono+esp32`,
-`C153+m5stack`, `m5papermono`, sorted by `updated desc`. **Code search was not
-used** and does not index forks, so quiet forks carrying real work remain
-invisible. Chinese-language platforms (Gitee, Bilibili, CSDN) were **again not
-searched** — still the largest known hole.
-
-Nothing here was built, flashed or run. All source claims are `inferred` from
-reading; the repository metadata is `executed-success`.
-
-Commit SHAs at retrieval: `paper_name_plate` `7eac75dfc9`, `papermono-rs`
-`67ee512024`, `M5PaperMonoLite` `dd97e91048`, `mono-note-mini` `ae84a34da7`.
diff --git a/software/ecosystems/crosspoint-freeink/nfc-implementation-comparison.md b/software/ecosystems/crosspoint-freeink/nfc-implementation-comparison.md
deleted file mode 100644
index 60c2d43..0000000
--- a/software/ecosystems/crosspoint-freeink/nfc-implementation-comparison.md
+++ /dev/null
@@ -1,175 +0,0 @@
-# Three NFC implementations on the PaperMono — a technique comparison
-
-> The same chip, the same board, three independent approaches — and one of them
-> found a remotely-reachable stack overflow in M5Stack's own NFC library.
->
-> Researched **2026-09-11**. Repository, build-config and patch-source facts are
-> `executed-success` (files fetched and read). Behavioural claims are `inferred`;
-> **nothing was built, flashed or tested against a tag.**
-
-## The three
-
-| | **Vendor UserDemo** | **`ciniml/paper_name_plate`** | **`Corvelis/m5-touch-card`** |
-|---|---|---|---|
-| Language | C++ / Arduino | **Rust, `no_std`** | C++ / Arduino |
-| Framework | ESP-IDF 5.5.1 + arduino-esp32 3.3.10 | **esp-hal 1.1.x** | PlatformIO, espressif32 6.12.0, `-std=gnu++17` |
-| NFC driver | `M5Unit-NFC`, as shipped | **written from scratch** (28.9 KB) | `M5Unit-NFC` **pinned + patched** |
-| NFC role | reader — identity probe | **tag emulation** (T2T, ISO-DEP, NDEF) | **tag emulation** (NFC-A) |
-| Graphics | M5GFX | own SSD1677 + `embedded-graphics 0.8` | M5GFX 0.2.27 |
-| Storage | — | `config_store.rs` | **LittleFS**, 16 MB OTA partition table |
-| Companion | — | Web Bluetooth page (GitHub Pages) | **smartphone app** (`mobile/`) |
-| Licence | MIT | **none** | MIT |
-
-Three positions on the same axis: **use the vendor library**, **fix the vendor
-library**, **replace it entirely**.
-
-## The headline: `M5Unit-NFC` 0.1.0 has an RF-reachable stack overflow
-
-`Corvelis` ships `firmware/scripts/patch_m5unit_nfc.py` — a 374-line PlatformIO
-**pre-build script that patches the vendor library in place** before compiling.
-Its docstring states the problem plainly:
-
-> *"M5Unit-NFC 0.1.0 uses 64-byte stack buffers in the NFC-A emulation listener.
-> PaperMono's tested transport uses a 253-byte command (240-byte DATA payload),
-> so both listener buffers are expanded to 256 bytes. The explicit length guard
-> also makes malformed RF frames fail closed before the FIFO read."*
-
-The original code reads a length from the chip's FIFO and then reads that many
-bytes into a **64-byte stack buffer with no bounds check**:
-
-```cpp
-_u.readFIFOSize(bytes, bits);
-rx_len = bytes;
-if (irq32 & (I_par32 | I_crc32 | I_err132 | I_err232) || rx_len <= 2) {
-```
-
-The patch inserts the guard the original lacks:
-
-```cpp
-if (rx_len > sizeof(rx)) {
-    M5_LIB_LOGE("A RX oversized %u", rx_len);
-    _u.writeDirectCommand(CMD_CLEAR_FIFO);
-    _u.writeDirectCommand(CMD_UNMASK_RECEIVE_DATA);
-    return EmulationLayerA::State::Active;
-}
-```
-
-**Severity.** In emulation mode the length is attacker-controlled — it comes from
-an RF frame sent by whatever is holding a reader near the device. An oversized
-frame smashes a 64-byte stack buffer. No authentication is involved because none
-exists at that layer; proximity is the only precondition.
-
-**Status: `inferred`, not demonstrated.** The missing bound is visible in the
-source and the patch author describes it as a real transport problem they hit.
-Whether it is practically exploitable versus merely a crash was **not tested**,
-and nothing was run. Recorded because the method calls for auditing vendor driver
-source, and this is exactly what that is for.
-
-Note the vendor's own UserDemo uses `M5Unit-NFC` **unpatched** — but in *reader*
-mode, where the emulation listener is not the active path.
-
-## Six more defects the same patch fixes
-
-`patch_m5unit_nfc.py` is a small vendor-library audit in its own right:
-
-| # | Fix | What it says about the library |
-|---|---|---|
-| 1 | `uint8_t rx[64]` → `rx[256]` (both listener buffers) | Sized for a protocol smaller than the one in use |
-| 2 | Length guard before `readFIFO` | **The overflow above** |
-| 3 | IRQ poll: also check `gpio_get_level(irq)` | *"The ST25R3916 IRQ output stays high until its interrupt registers are read. If the GPIO rising edge is missed, checking only the ISR flag **deadlocks NFC-A emulation in Ready forever**."* A missed edge is unrecoverable |
-| 4 | `gpio_isr_handler_remove()` before `add` | *"A failed `begin()` can leave this instance's IRQ handler installed"* — retry path leaks a handler |
-| 5 | `picc.isMifareUltralight()` instead of an explicit type pair | Library had responses for the whole Ultralight family but gated emulation to two types |
-| 6 | Field-off detect adds `is_extra_field()`; `begin()` reports *why* it failed | Field detection and diagnostics |
-
-Fix 3 is the one most likely to be mistaken for a hardware fault: emulation
-silently wedges in `Ready` and never recovers. The patch notes the library's own
-blocking `wait_for_interrupt()` already polls the pin level *for the same reason*
-— so the fix pattern was present elsewhere in the same driver and simply not
-applied here.
-
-## Why the Rust project wrote its own driver
-
-`ciniml/paper_name_plate` states its reasoning in `DESIGN.md`:
-
-> *"We implement drivers ourselves rather than relying on external crates
-> (`ssd1677` etc.). PaperMono has many device-specific circumstances — 4-gray,
-> OTP waveforms, reset via IOE1 — and existing crates do not anticipate the
-> 800×480 4-gray + external-reset combination."*
-
-That reasoning is about the **display**, but the same logic produced a
-from-scratch `st25r3916.rs` (28.9 KB) plus `t2t_emu.rs` (19.8 KB), `isodep.rs`
-and `ndef.rs`. There is no Rust ST25R3916 crate to lean on, so "write it" was the
-only option rather than a preference.
-
-**Consequence:** it is the only one of the three that owns its full NFC stack, so
-none of the `M5Unit-NFC` defects above apply to it — and any equivalent bugs it
-has are its own and undocumented.
-
-## Architecture contrasts worth noting
-
-**Peripheral access.** All three drive the M5IOE1 expander and M5PM1 PMIC
-directly rather than through an abstraction — the vendor demo via its own HAL,
-`paper_name_plate` via hand-written `ioe1.rs`/`pm1.rs`, `Corvelis` via
-`M5UnitUnified`/`M5HAL`. **None uses the FreeInk SDK**, which independently
-supports the conclusion in
-[radios-on-papermono](../../ecosystems/crosspoint-freeink/radios-on-papermono.md)
-that the SDK abstraction is optional for radio work.
-
-**Partitioning.** Only `Corvelis` ships an OTA-capable table
-(`partitions_16mb_ota_4m_littlefs_7m.csv` — 4 MB app slots, 7 MB LittleFS). The
-vendor image is a single `factory` app with **no OTA**. That is the difference
-between a demo and something intended to be updated in the field.
-
-**Configuration UX.** Three different answers to "how does a user set this up":
-vendor — none; `paper_name_plate` — **Web Bluetooth page** served from GitHub
-Pages; `Corvelis` — a **native smartphone app** with its own `protocol/`
-directory. For a device with no keyboard, this is the real design problem, and
-nobody chose the device's own web server.
-
-**Build-time patching as a technique.** `Corvelis`'s approach — pin the dependency
-to an exact commit, then patch it in a `pre:` script — is worth calling out. It
-keeps the fix reproducible and visible in-tree without forking the library, at
-the cost of breaking silently if upstream changes the matched text. The script
-carries both `_ORIGINAL` and `_LEGACY_PATCHED` variants, so the author has
-already hit that.
-
-## What this says about the ecosystem
-
-**The vendor library is the weak link and two of three projects routed around
-it.** One patched it, one replaced it. Only the vendor's own demo uses it as
-shipped, and only in the mode that avoids the defective path.
-
-**Nobody has upstreamed the fixes.** The patch lives in one project's build
-scripts. `M5Unit-NFC` at the pinned commit `93745b54` presumably still has the
-missing bound.
-
-**Two independent projects converged on tag emulation**, not tag reading — the
-PaperMono's natural NFC product is *being* a tag, not reading one.
-
-## Open questions
-
-- **Nothing was built, flashed or tested.** No tag was read, no emulation
-  exercised, no overflow attempted.
-- **The overflow is `inferred` from source.** Exploitability versus
-  crash-only was not assessed, and no responsible-disclosure step was taken from
-  here.
-- Whether `M5Unit-NFC` has since fixed any of this upstream was **not checked** —
-  `Corvelis` pins `93745b54`, and current `main` was not compared.
-- `paper_name_plate`'s own NFC stack was **not audited** for equivalent defects.
-- The vendor UserDemo's NFC path was inferred from earlier research, not re-read
-  for this comparison.
-
-## Sources
-
-All 2026-09-11: `Corvelis/m5-touch-card` `firmware/platformio.ini`,
-`firmware/src/`, `firmware/lib/`, and `firmware/scripts/patch_m5unit_nfc.py`
-(374 lines, read in full); `ciniml/paper_name_plate` `README.md`, `DESIGN.md`,
-`src/` listing; `m5stack/M5PaperMono-UserDemo` from prior research.
-Archived copies of the plugin-ecosystem repos are listed in
-[source-snapshots.ARCHIVED.md](../../applications/crosspoint-reader/plugins/source-snapshots.ARCHIVED.md);
-the NFC projects are archived at
-`archive/software/ecosystems/crosspoint-freeink/nfc-source-snapshots/`:
-`ciniml/paper_name_plate` @ `7eac75d`, `Corvelis/m5-touch-card` @ `fc20a44`,
-`m5stack/M5PaperMono-UserDemo` @ `c109910`, and **`m5stack/M5Unit-NFC` @ `93745b5`**
-— the last so the unpatched defective source is preserved alongside the patch
-that fixes it.
diff --git a/software/ecosystems/crosspoint-freeink/paper-name-plate-review.md b/software/ecosystems/crosspoint-freeink/paper-name-plate-review.md
deleted file mode 100644
index 527cc26..0000000
--- a/software/ecosystems/crosspoint-freeink/paper-name-plate-review.md
+++ /dev/null
@@ -1,239 +0,0 @@
-# `ciniml/paper_name_plate` — code review
-
-> A bare-metal Rust firmware for the M5Stack PaperMono, reviewed to the same
-> standard applied to `M5Unit-NFC` — including looking for the *same class* of
-> bug.
->
-> Reviewed **2026-09-11** at HEAD `7eac75dfc9`, 29 commits, sole author
-> **Kenta IDA (ciniml)**. Source-level review only: **nothing was built, flashed
-> or run.** Findings are `inferred`.
-
-## What it is
-
-A digital name badge. It shows your contact details on the e-paper, **emulates an
-NFC tag** so a phone tap retrieves them, and is configured over **BLE** from a Web
-Bluetooth page served via GitHub Pages.
-
-Notable as the only PaperMono firmware written in Rust, and one of only two
-third-party projects driving the board's NFC.
-
-```
-src/st25r3916.rs   28.9 KB   NFC transceiver driver, from scratch
-src/t2t_emu.rs     19.8 KB   NFC Forum Type 2 Tag emulation
-src/board.rs       14.6 KB   board bring-up: pins, PMIC, expander, EPD power
-src/pm1.rs          8.4 KB   M5PM1 PMIC
-src/ioe1.rs         6.3 KB   M5IOE1 I/O expander
-src/ndef.rs         5.4 KB   NDEF encoding
-src/isodep.rs       5.3 KB   ISO-DEP
-src/config_store.rs 4.4 KB   persistence
-src/ft6336.rs       3.2 KB   touch
-src/ssd1677/        —        panel driver, 4-gray LUTs, 2-plane framebuffer
-```
-
-Toolchain: `esp-hal 1.1.x`, `xtensa-esp32s3-none-elf`, `embedded-graphics 0.8`,
-`espflash`. Blocking, no `embassy` — a stated choice to revisit when event
-handling demands it.
-
-## The headline: it contains the *same logic error* as `M5Unit-NFC`, with a different outcome
-
-This is the most instructive thing in the review, and it is a genuinely
-apples-to-apples comparison.
-
-**`src/t2t_emu.rs:397–399`:**
-
-```rust
-let mut rx = [0u8; 64];
-let n = bytes as usize - 2;     // strip CRC — NOT clamped to rx.len()
-nfc.read_fifo(&mut rx[..n])?;
-```
-
-`bytes` is the FIFO length, read from the chip, derived from an RF frame — up to
-**512**. `rx` is **64 bytes**. This is precisely the mistake at
-`emulation_layer_a_ST25R3916.cpp:444`.
-
-**The consequence is not the same:**
-
-| | `M5Unit-NFC` (C++) | `paper_name_plate` (Rust) |
-|---|---|---|
-| `n > 64` | `readRegister` writes past `rx` — **stack overflow**, RF-controlled data | `&mut rx[..n]` **panics** — bounds-checked slice |
-| `bytes < 2` | n/a | `bytes - 2` **underflows**; debug panics, release wraps to `usize::MAX-1` → the slice index then panics anyway |
-| Class | **memory corruption** | **denial of service** |
-
-Both are bugs and both are reachable from RF. Only one is a memory-safety
-failure. The device reboots instead of having its stack rewritten — which is
-exactly the tradeoff the language is for, and it is nice to see it demonstrated
-on the same chip, the same protocol, and the same mistake.
-
-**Recommended fix**, matching the file's own idiom elsewhere:
-
-```rust
-let n = (bytes as usize).saturating_sub(2).min(rx.len());
-```
-
-## The API shape is why the C++ bug was possible and this one is bounded
-
-```rust
-pub fn read_fifo(&mut self, buf: &mut [u8]) -> Result<(), I2C::Error>
-```
-
-versus
-
-```cpp
-uint32_t readFIFO(uint16_t& actual, uint8_t* buf, const uint16_t buf_size);
-```
-
-The Rust signature **cannot be lied to**: the slice carries its own length, so
-"capacity" and "requested length" are the same value. The C++ signature separates
-pointer from size, which is the shape that invites passing the FIFO length where
-the buffer capacity belongs — and that is exactly what happened.
-
-Worth stating plainly because it is a design lesson, not a language-war point:
-**the defect was in the interface, and the caller was merely where it surfaced.**
-
-## The other three FIFO call sites are correct
-
-```rust
-// st25r3916.rs:697-699
-let (bytes, _) = self.fifo_status()?;
-let n = (bytes as usize).min(rx.len());      // clamped
-self.read_fifo(&mut rx[..n])?;
-
-// t2t_emu.rs:350, :386
-let n = (bytes as usize).min(4);             // clamped
-nfc.read_fifo(&mut peek[..n])?;
-```
-
-And the anticollision path bounds both ends of the range:
-
-```rust
-// st25r3916.rs:615-618
-let want = 5 - rbuf_offset;
-let actual = (bytes as usize).min(want);
-if actual == 0 { return Err(Error::Protocol); }
-self.read_fifo(&mut rbuf[rbuf_offset..rbuf_offset + actual])?;
-```
-
-So three of four sites are right. The defective one is an outlier — the same
-profile as the C++ library, where one of two sites was wrong.
-
-## Safety posture
-
-| Metric | Count | Assessment |
-|---|---|---|
-| `unsafe` blocks | 7 | Low for bare-metal; **not individually audited** |
-| `panic!`/`unwrap`/`expect` | **3** | All init-time invariants, all legitimate |
-| Unchecked slice ranges | 12 | One is the defect above |
-| Checked `.get()`/`.get_mut()` | 20 | Checked access outnumbers raw indexing |
-
-The three panic sites are `board.rs:143` `.expect("i2c config")`, `board.rs:203`
-`.expect("spi config")`, and `app/mod.rs:754`
-`.expect("poll_nfc only runs with NFC")`. All are boot-time configuration or
-documented preconditions — the right places to panic. **There is no
-`unwrap()` in the RF data path**, which is the discipline that matters.
-
-
-## The seven `unsafe` blocks — audited
-
-Previously counted but unread. All seven examined 2026-09-11:
-
-| # | Site | Purpose | Assessment |
-|---|---|---|---|
-| 1 | `ssd1677/framebuffer.rs:133` | In-place `MaybeUninit` init of the two-plane framebuffer via `addr_of_mut!` + `write_bytes` | **Sound.** Correct idiom — no reference to uninitialised memory is created. Avoids a large stack copy |
-| 2 | `bin/main.rs:39` | Registers a second heap region from `static mut MaybeUninit<[u8; N]>` | **Sound.** Standard `esp_alloc` pattern, one-shot at boot, `#[allow(static_mut_refs)]` acknowledged |
-| 3 | `app/mod.rs:80` | `doze_diag_set` writes a `static mut` diagnostic array | **Sound-ish.** Uses `addr_of_mut!`; `d[idx]` is a *bounds-checked* array index, so a bad index panics rather than corrupting. No synchronisation, but the path is single-threaded |
-| 4 | `app/mod.rs:92` | Reads the USB SOF frame counter via `esp32s3::USB_DEVICE::ptr()` | **Sound.** Ordinary PAC register read, used to detect a live USB host so the console stays usable |
-| 5 | `app/mod.rs:101` | Reads the diagnostic array (`addr_of!`) | **Sound** |
-| 6 | `app/mod.rs:108` | Zeroes the diagnostic array | **Sound** |
-| 7 | `board.rs:227` | **`clone_unchecked()` on four GPIOs** — all four also get live `Input` drivers | **Permanent duplicate ownership**, sound only by temporal discipline — see below |
-
-### The one worth scrutiny
-
-```rust
-// SAFETY: the clones are only used to program RTC-IO wake-up right
-// before deep sleep, when the `Input` drivers are no longer used.
-let wake_pins: [AnyPin<'static>; 4] = unsafe {
-    [ p.GPIO6.clone_unchecked().into(),   // NFC IRQ
-      p.GPIO4.clone_unchecked().into(),   // touch INT
-      p.GPIO2.clone_unchecked().into(),   // button A
-      p.GPIO3.clone_unchecked().into() ]  // button B
-};
-let tp_int   = Input::new(p.GPIO4, /* … */);   // line 235
-let nfc_irq  = Input::new(p.GPIO6, /* … */);   // line 236
-let button_a = Input::new(p.GPIO2, /* … */);   // line 270
-let button_b = Input::new(p.GPIO3, /* … */);   // line 271
-```
-
-`clone_unchecked()` deliberately duplicates pin ownership — precisely what
-esp-hal's type system exists to prevent. **All four cloned pins then receive live
-`Input` drivers within the next 45 lines**, and `Board` (`board.rs:294`) stores
-*both* sets:
-
-```rust
-Board { … tp_int, nfc_irq, button_a, button_b, …, wake_pins, … }
-```
-
-So the duplicate ownership is **structural and lasts the entire life of the
-program**, not a brief window — an earlier draft of this review said the window
-was small, which was wrong. What is small is the *use* of the clones: they are
-touched only at `app/mod.rs:376`, destructured as `[nfc, tp, btn_a, btn_b]`
-immediately before deep sleep.
-
-The soundness argument is therefore **purely temporal** — two owners of each pin
-coexist permanently, and correctness depends on never using them at overlapping
-times. This is a recognised embedded pattern (RTC wake-up needs the pin identity
-while a driver still holds it, and esp-hal offers no safe way to express that),
-and the author both documented it and named the invariant. But it is enforced by
-discipline alone, and a refactor that touched `wake_pins` outside the sleep path
-would break it silently.
-
-**Overall:** all seven are recognised embedded-Rust idioms, **none is in the RF
-data path**, and the riskiest is documented. This is careful code.
-
-## Engineering quality
-
-**Hardware bring-up is defensive.** A commit titled *"Recover from a flaky I2C bus
-at boot: retry IOE1 EPD power-on"* — independent corroboration that this board's
-shared I²C bus needs retry logic, matching what the device record says about bus
-contention.
-
-**The `DESIGN.md` is the best third-party PaperMono hardware document that
-exists.** It independently confirms this knowledge base's pin map on every
-contested point, states the `PYGn` 1-based/0-based trap explicitly, and records
-bus speeds (PM1/IOE1 100 kHz, touch/NFC 400 kHz) that no vendor document gives.
-
-**Driver decisions are justified in writing.** On writing its own drivers:
-*"existing crates do not anticipate the 800×480 4-gray + external-reset
-combination."* On licences, it notes M5GFX's LUTs are FreeBSD and reusable —
-attribution done properly.
-
-**Commit messages are precise** — *"Clear the display image over BLE (CTRL 06)"*,
-*"Report rejected plate text as STATUS state 5"*. This reads as careful work.
-
-## Risks
-
-- **No `LICENSE` file.** All-rights-reserved by default. Read for technique; do
-  not copy. This is the single biggest practical barrier to the project being
-  useful to others.
-- **Bus factor 1.** 29 commits, one author, ★0.
-- **The `t2t_emu.rs` defect is live** at HEAD.
-- ~~`unsafe` blocks not audited~~ — **all seven audited**; see above. One (`board.rs:227`, `clone_unchecked`) carries an unenforced invariant.
-- **BLE control surface not reviewed.** It accepts plate text and display
-  commands over BLE; input validation was not examined. There is a hint of
-  validation (*"Report rejected plate text"*), but it was not verified.
-- Release-mode integer overflow behaviour was not confirmed against the project's
-  `Cargo.toml` profile settings.
-
-## What was not done
-
-- **Nothing built or run.** No device, no toolchain invocation, no tag read.
-- Only the NFC and FIFO paths were reviewed closely; `ndef.rs`, `isodep.rs`,
-  `config_store.rs` and `ssd1677/` were **not** reviewed.
-
-- No fuzzing, no static analysis, no `cargo clippy` run.
-- The defect was **not reported to the author.**
-
-## See also
-
-- [The `M5Unit-NFC` overflow](m5unit-nfc-overflow.md) — the C++ counterpart
-- [NFC implementation comparison](nfc-implementation-comparison.md)
-- Archived at `archive/software/ecosystems/crosspoint-freeink/nfc-source-snapshots/ciniml_paper_name_plate/`
diff --git a/software/ecosystems/crosspoint-freeink/radios-on-papermono.md b/software/ecosystems/crosspoint-freeink/radios-on-papermono.md
deleted file mode 100644
index 121361c..0000000
--- a/software/ecosystems/crosspoint-freeink/radios-on-papermono.md
+++ /dev/null
@@ -1,255 +0,0 @@
-# Adding LoRa and NFC to CrossPoint-family firmware on the PaperMono
-
-> A feasibility assessment grounded in the actual SDK source, not in what the
-> abstraction layer implies.
->
-> Researched **2026-09-04**. Repository and source facts are `executed-success`
-> — repos cloned, headers read, GitHub compare API called. Effort estimates and
-> design suggestions are `inferred`. **No hardware; nothing was built or run for
-> this assessment.**
-
-## The headline
-
-**You do not need to extend the FreeInk SDK to reach the radios.** Firmware
-source can call `Wire`, `SPI` and RadioLib directly, and **CrossInk already does
-exactly this for ESP-NOW** — so there is a working precedent in the ecosystem for
-bypassing the capability system entirely.
-
-The SDK abstraction is a convenience layer, not a gatekeeper. That is the
-opposite of the *plugin* boundary, which is enforced at link time.
-
-| Layer | Can it reach a bus? | Enforcement |
-|---|---|---|
-| **Plugin** (native ELF, `mekhontsev`) | **No** | Hard. 81-symbol allow-list; **the link fails** |
-| **Plugin** (upstream JS) | **No** | Absolute — no MCU-side execution at all |
-| **Firmware source** (any fork) | **Yes** | None. `#include <Wire.h>` and go |
-
-## 1. Does CrossInk look receptive to radio work?
-
-**Its stated scope says no. Its shipped code says it already did it.**
-
-`README.md`: *"a **personal fork** … with a focus on **improved fonts and minimal
-reading stats**"*, and *"keeping the underlying system stable while layering in a
-few 'nice-to-have' features."*
-
-`SCOPE.md` inherits upstream's anti-kitchen-sink mission verbatim and adds:
-*"If you have a major feature request, it should first be directed at the main
-project since this is a downstream project that consumes their updates."*
-
-**But it has already shipped two radio features**, and they are the key evidence
-for this whole assessment:
-
-| File | What it does |
-|---|---|
-| `src/activities/reader/NearbyBookPositionSyncActivity.cpp` | ESP-NOW reading-position sync between two readers |
-| `src/activities/network/NearbyStatsSyncActivity.cpp` | ESP-NOW stats transfer |
-
-These `#include <esp_now.h>` and call `esp_now_init()`,
-`esp_now_register_recv_cb()`, `esp_now_send()`, `esp_wifi_set_ps()` **straight
-from an Activity**. There is no `FREEINK_CAP_ESPNOW`, no SDK manager, no
-board-profile field. The abstraction was simply bypassed.
-
-**Conclusion:** CrossInk demonstrates the technique but is a poor host for this
-work — its supported devices are **X3, X4 and Sticky only**, it has no PaperMono
-support, and its author would likely (correctly) point LoRa/NFC upstream.
-
-## 2. Powering the radios — what already exists, and the four missing lines
-
-On the PaperMono the radios are not on direct GPIO. The ST25R3916 and the LoRa
-module sit behind the **M5IOE1 expander** and the **M5PM1 power manager**
-([pinouts](../../../devices/m5stack/papermono/pinouts-and-buses.md)).
-
-**Good news: the SDK already drives both chips.** `BoardConfig/include/` contains
-`M5Ioe1.h` (160 lines) and `M5Pm1.h` (213 lines) — full register maps, bus
-init, and inline I²C read/write helpers, all PaperMono-aware.
-
-`M5Pm1.h` even handles the board difference correctly:
-
-> *"PaperColor: SDA3/SCL2. Paper Mono: SDA47/SCL48 … its GPIO2/3 are KEY1/KEY2,
-> so the PaperColor default there would put Wire on button pins and kill the
-> whole bus."*
-
-### What is missing is only the pin constants
-
-`M5Ioe1.h` defines named masks for exactly the pins the *reader* needs:
-
-```
-PIN_TF_DETECT (IO1) · PIN_EPD_POWER (IO3) · PIN_EPD_RESET (IO5)
-PIN_TOUCH_RESET (IO6) · PIN_LED_GREEN (IO8) · PIN_LED_BLUE (IO9)
-PIN_MIC_POWER (IO12) · PIN_TOUCH_POWER (IO13) · PIN_SD_POWER (IO14)
-```
-
-**Absent — and they are precisely the radio pins:**
-
-| Pin | Net | Function | In SDK? |
-|---|---|---|---|
-| IO2 | `PYB_LoRa_ANT_SW` | LoRa antenna switch | **no** |
-| IO4 | `PYB_NFC_EN` | **NFC power enable** | **no** |
-| IO10 | `PYB_LoRa_RST` | **LoRa reset** | **no** |
-| IO11 | `PYB_CHG_IIC` | charger I²C gate | no |
-
-Similarly `M5Pm1.h` names only **`GPIO0`** (EPD_EN). The PaperMono's **`G2` =
-`PYG2_LoRa_EN`**, which enables the `3V3_L2_LoRa` rail through an SSP7615 LDO, has
-no constant.
-
-So step 2 is genuinely small — add four `constexpr uint16_t` masks, extend
-`OUTPUT_MASK`, add a `GPIO2` constant:
-
-```cpp
-// M5Ioe1.h — additions
-constexpr uint16_t PIN_LORA_ANT_SW = 1u << 1;   // IO2  PYB_LoRa_ANT_SW
-constexpr uint16_t PIN_NFC_POWER   = 1u << 3;   // IO4  PYB_NFC_EN
-constexpr uint16_t PIN_LORA_RESET  = 1u << 9;   // IO10 PYB_LoRa_RST
-// extend OUTPUT_MASK with all three
-
-// M5Pm1.h — addition
-constexpr uint8_t GPIO2 = 1 << 2;               // PYG2_LoRa_EN -> 3V3_L2_LoRa
-```
-
-**Verify the bit positions against the schematic before use** — the masks above
-are derived from the device record's pin table (IO*n* → bit *n−1*, matching the
-existing entries), not read from a datasheet. `inferred`.
-
-## 3. Talking to the radios
-
-### The SPI pins are not in the board profile at all
-
-The `PAPER_MONO` profile in `BoardConfig.h` covers display, touch, SD, RTC,
-buttons, frontlight, audio, LEDs and mic. Grepping the whole SDK for the LoRa SPI
-pins — **GPIO 38/39/40/41 (MOSI/CLK/MISO/NSS), 21 (BUSY), 5 (IRQ)** — returns
-**nothing**. There is no struct field for a radio, so there is nowhere to put
-them even if you wanted to.
-
-For a prototype that does not matter: hardcode them in your Activity, exactly as
-CrossInk hardcodes its ESP-NOW setup.
-
-### LoRa — RadioLib
-
-**RadioLib 7.2.1 is MIT** (verified: `license.txt` and `library.json` both, read
-at the tag), and applies all four SX126x §15 errata workarounds at that version
-(also verified at source). It is already the pinned driver in M5Stack's own
-PaperMono demo.
-
-Sketch — `inferred`, **not compiled**:
-
-```cpp
-// bring the rail up, release reset, set the antenna switch
-m5pm1::setGpio(m5pm1::GPIO2, true);          // 3V3_L2_LoRa
-m5ioe1::setPin(m5ioe1::PIN_LORA_RESET, true);
-m5ioe1::setPin(m5ioe1::PIN_LORA_ANT_SW, /* per band */);
-
-SPIClass spi(HSPI);
-spi.begin(/*CLK*/39, /*MISO*/40, /*MOSI*/38, /*NSS*/41);
-SX1262 radio = new Module(41, /*IRQ*/5, /*RST*/RADIOLIB_NC, /*BUSY*/21, spi);
-radio.begin(868.0, 125.0, 9, 7, 0x12, 22, 8, /*tcxoVoltage*/3.0f, /*useRegulatorLDO*/true);
-```
-
-Two board facts that matter and are already established in this knowledge base:
-**reset is not on an ESP32 GPIO** (pass `RADIOLIB_NC` and drive the expander
-instead), and the vendor demo selects **LDO regulation** — roughly doubling
-receive current — presumably because the module omits the DC-DC inductors.
-
-**Regional band configuration becomes your legal responsibility** the moment you
-transmit. See [`guides/lora`](../../../guides/lora/README.md).
-
-### NFC — ST25R3916
-
-I²C `0x50` on the **shared system bus** (SDA 47 / SCL 48), IRQ on GPIO 6, power
-via M5IOE1 IO4. Driver options: ST's **RFAL** (the reference implementation) or
-`M5Unit-NFC`.
-
-**The shared-bus hazard is the real design constraint here.** That bus already
-carries the RTC (`0x32`), touch (`0x38`), the expander (`0x4F`), the IMU
-(`0x68`) and the PMIC (`0x6E`) — and the IP2315 charger has a documented
-bus-wedge failure mode. An NFC polling loop that holds the bus will interfere
-with touch responsiveness and RTC reads. See
-[resources-and-conflicts](../../../devices/m5stack/papermono/resources-and-conflicts.md).
-
-## 4. Prototype now, upstream later — and they are different jobs
-
-| | Prototype (fork) | Upstreamable (SDK) |
-|---|---|---|
-| Pin constants | hardcode in the Activity | `M5Ioe1.h` / `M5Pm1.h` additions |
-| Rail control | call the inline helpers directly | same, via named constants |
-| Driver | RadioLib in `src/activities/` | a `LoRaManager` peer to `Rtc`/`Imu` |
-| Capability gating | none | `FREEINK_CAP_LORA`, `FREEINK_CAP_NFC` |
-| Board profile | untouched | new radio struct fields |
-| Other boards | ignored | LilyGO T5S3 already has LoRa pins defined |
-| Effort | **days** | **weeks**, plus review |
-
-**Start with the prototype.** It answers the question that actually matters — does
-the hardware work, are the rails right, does the antenna switch behave — without
-committing to an SDK API design. CrossInk's ESP-NOW work is the precedent for
-shipping useful radio functionality this way indefinitely.
-
-**Then upstream if it proves out.** Note the SDK already carries LoRa pin
-definitions for the **LilyGO T5S3** (`T5S3_LORA_CS/IRQ/RST/BUSY`), so a second
-LoRa board exists to justify a real abstraction — that is the argument for
-`FREEINK_CAP_LORA` rather than a PaperMono special case.
-
-### Which fork to start from
-
-**Upstream CrossPoint, not CrossInk.** It already has `[env:papermono]` and pins
-the SDK commit containing PaperMono support. CrossInk would cost a **136-commit
-SDK bump** *plus* a **294-commit merge into 224 modified `lib/` files**, for no
-benefit — see [the fork network](fork-network.md).
-
-
-## Update 2026-09-07 — NFC is now demonstrated on this board
-
-[`ciniml/paper_name_plate`](https://github.com/ciniml/paper_name_plate) is
-bare-metal `no_std` Rust firmware for the PaperMono carrying a **28.9 KB
-ST25R3916 driver**, **19.8 KB of NFC Forum Type 2 Tag emulation**, ISO-DEP and
-NDEF — plus its own `pm1.rs` and `ioe1.rs`.
-
-Three things it settles:
-
-1. **NFC works on this hardware from third-party code.** The argument above was
-   that the radios were reachable from firmware source; this is the proof.
-2. **It wrote its own PMIC and expander drivers rather than using the FreeInk
-   SDK** — independently reaching the conclusion this assessment reached, that
-   the SDK abstraction is optional.
-3. **It confirms the three "missing" pins** — `IO4 = NFC_EN`, `IO10 = LoRa RST`,
-   `IO2 = LoRa ANT SW` — from its own reading of the hardware, matching this
-   knowledge base's schematic extraction exactly.
-
-It also states the M5GFX waveform LUTs are **FreeBSD-licensed and reusable**,
-and that recovering the panel from deep sleep **requires a hardware reset via
-IOE1 IO5**.
-
-**LoRa remains undemonstrated anywhere.** `paper_name_plate` lists the SX1262
-pins and explicitly scopes it out. No project found drives LoRa on this board.
-
-Full analysis: [new PaperMono projects, 2026-09](new-papermono-projects-2026-09.md).
-It carries **no `LICENSE` file** — all rights reserved; read for technique, do not copy.
-
-## Incidental findings
-
-Two things surfaced that belong in the device record:
-
-**FreeInk drives the panel at 20 MHz.** `PAPER_MONO`'s profile sets SPI to
-`20000000` — matching the SSD1677 datasheet maximum, and **contradicting M5GFX's
-40 MHz**, which this knowledge base recorded as an unresolved conflict. FreeInk
-chose the compliant clock. That is a second independent implementation siding
-with the datasheet.
-
-**The SDK declares `ImuType::None` for the PaperMono** despite the board having a
-BMI270 at `0x68` — and `FREEINK_CAP_IMU` therefore excludes it. The IMU is fitted,
-wired and unused. Whether that is deliberate (power, or the interrupt landing on
-the M5PM1 rather than the ESP32) or simply unported is **not established**.
-
-## What was not done
-
-- **Nothing was built.** No prototype compiled, no radio initialised, no hardware.
-- The M5IOE1 bit positions above are **derived, not read from a datasheet**.
-- `m5ioe1::setPin` / `m5pm1::setGpio` are used illustratively; the **exact helper
-  signatures were not read** — only that inline read/write primitives exist.
-- No check of whether upstream or FreeInk have stated any intent to add radios.
-- The IMU-disabled question was not chased.
-
-## See also
-
-- [CrossPoint Reader](../../applications/crosspoint-reader/README.md) · [plugin systems](../../applications/crosspoint-reader/plugins/README.md) — why a plugin cannot do this
-- [FreeInk SDK](../../frameworks/freeink-sdk/README.md) · [fork network](fork-network.md)
-- [PaperMono pinouts](../../../devices/m5stack/papermono/pinouts-and-buses.md) · [NFC](../../../devices/m5stack/papermono/features/nfc.md) · [LoRa](../../../devices/m5stack/papermono/features/lora.md)
-- [`guides/lora`](../../../guides/lora/README.md) · [`guides/nfc`](../../../guides/nfc/README.md)
diff --git a/software/frameworks/freeink-sdk/README.md b/software/frameworks/freeink-sdk/README.md
deleted file mode 100644
index 0823b86..0000000
--- a/software/frameworks/freeink-sdk/README.md
+++ /dev/null
@@ -1,169 +0,0 @@
-# FreeInk SDK
-
-> A hardware-independent SDK for building e-paper reader firmware.
-> **`Free-Ink/freeink-sdk`** · branch `main` · MIT · ★248 · 95 forks ·
-> created 2026-06-03 · last push 2026-09-03 · ~3.5 MB · https://freeink.org
->
-> Snapshot **2026-09-02/04**. Nothing was built or run — no hardware. Claims are
-> read from the repository at the cited path and are `inferred` unless noted.
-
-**Classification:** **framework** — it inverts control. Firmware calls a generic
-API; the SDK injects device behaviour. It is not a library you pick features
-from, and not an application.
-
-## What it is
-
-FreeInk abstracts every device-specific detail — display controller,
-waveforms/LUTs, GPIOs, bus speeds, input style, touch, frontlight, audio — behind
-small injectable interfaces. The project's own framing of the design goal:
-
-> Adding a new device means adding **data** (a board profile + a driver config),
-> not editing the generic code.
-
-That sentence is the whole architectural thesis, and it is what makes porting
-cheap relative to CrossPoint's older approach.
-
-### What ships in it
-
-| Layer | Contents |
-|---|---|
-| **Panel drivers** | SSD1677, UC8179, UC8253, UC8279, ED2208, IT8951, plus external-library-backed panels |
-| **Board profiles + capability gates** | display, input, touch, SD, frontlight, audio, microphone, RTC, sensors, buzzer, LEDs, TLS networking |
-| **Device managers** | input, battery, SD, frontlight, LEDs, audio, microphone, RTC, sensors, IMU |
-| **FreeInkUI** | optional immediate-mode UI layer — screens, dialogs, settings, keyboards, library views |
-| **FreeInkBook** | a complete EPUB engine: streaming parse, CSS, UAX #14 layout with hyphenation/justification/ligatures, page caching with exact position anchors, TTF with per-codepoint fallback, image dithering, links/footnotes. Freestanding, arena-allocated, host-tested |
-
-**FreeInkBook is the surprising part.** A full EPUB layout engine with UAX #14
-line breaking and hyphenation, written freestanding and arena-allocated so it can
-be host-tested off-device, is a substantial piece of engineering in its own right
-— arguably more valuable than the HAL it ships beside.
-
-**Capability gates** matter for porting: a board profile declares what exists, and
-firmware branches on capability rather than on device identity. That is why the
-same binary logic runs on a board with a frontlight and one without.
-
-### SSD1677 relevance
-
-FreeInk ships an **SSD1677** driver — the controller on both the
-[M5Stack PaperMono](../../../devices/m5stack/papermono/README.md) and the
-[Waveshare ESP32-S3-ePaper-3.97](../../../devices/waveshare/esp32-s3-epaper-3.97/README.md).
-See [`components/solomon-systech/ssd1677`](../../../components/solomon-systech/ssd1677/README.md).
-
-## Lineage — and why the "FreeInk came first" reading is wrong
-
-`NOTICE` is unusually candid, and it settles a question that was open in this
-knowledge base:
-
-> This project is based in part on, and contains code derived from, the **OpenX4
-> E-Paper Community SDK** (`open-x4-epaper/community-sdk`) and its community
-> device ports (M5Stack PaperColor, Murphy M3, and the community-sdk-de-link
-> ESP32-S3 port). In particular, the **SSD1677 and UC8253 panel initialization
-> sequences and waveform LUTs are derived from that work**. Original e-paper
-> driver authorship is credited to **CidVonHighwind**.
-
-So the dependency chain is:
-
-```
-open-x4-epaper/community-sdk  (MIT, CidVonHighwind et al.)
-        │  re-architected, code derived
-        ▼
-Free-Ink/freeink-sdk  (MIT, created 2026-06-03)
-        │  consumed as a git submodule
-        ▼
-crosspoint-reader/crosspoint-reader  (MIT, created 2025-12-03)
-```
-
-**CrossPoint predates FreeInk by six months.** FreeInk is not an upstream
-CrossPoint adopted from outside — it is a re-architecture of the SDK CrossPoint
-was already using, which CrossPoint then migrated onto. Anyone reading the star
-counts (7,538 vs 248) as "big project depends on small project it found" has the
-history backwards.
-
-The attribution also means the **panel init sequences and LUTs in FreeInk are
-third-party derived work**, which is worth knowing before treating them as
-authoritative for a given panel.
-
-## Who consumes it
-
-| Consumer | Relationship |
-|---|---|
-| [`crosspoint-reader`](../../applications/crosspoint-reader/README.md) | **git submodule** — `.gitmodules` pins `https://github.com/Free-Ink/freeink-sdk.git`, branch `main` |
-| [`CrossPlay`](../../applications/crossplay/README.md) | consumes a **fork**, `ma-r-s/freeink-sdk`, branch `x4pro-measured-insets` |
-| `Free-Ink/freeink-reader` | the SDK authors' own minimal reference reader |
-| 95 forks | see the fork discussion in the CrossPlay record |
-
-**Drop-in compatibility** is claimed with firmware written against the original
-`EInkDisplay` / `InputManager` / `BatteryMonitor` / `SDCardManager` / `BoardConfig`
-API — "switching to FreeInk is a matter of repointing the library path". That
-claim is from the README and is **`reported-working`, not verified here**.
-
-Because forks pin different SDK commits, **a fork's behaviour can differ from
-upstream CrossPoint's without a single line of fork-owned code differing** — the
-SDK underneath is a different revision. That is a real and easily-missed source
-of divergence.
-
-## Funding and governance
-
-Carries an **Open Collective** sponsorship badge (`opencollective.com/freeink`)
-and presents as "an open-source collective". That places it between a
-single-person project and a company-backed one.
-
-**Bus factor is the open risk.** An earlier analysis in this project found ~74 %
-of SDK commits from one author, who is also a CrossPoint co-maintainer and wrote
-the migration. That figure is **carried over and not re-verified in this pass** —
-treat it as `reported-working` from the prior analysis, not as measured today.
-
-## Porting a new device
-
-The SDK's design intent is that a port is *data*, not code. From the prior
-analysis in this project (`reported-working`, measured on real ports):
-
-| Port | Files touched | Lines |
-|---|---|---|
-| Xteink X4C | 7 | +295 |
-| M5Stack PaperS3 | 10 | +397 |
-| OnePage (a new MCU) | 8 | +245 |
-
-So a typical port is **7–10 files, 250–400 lines**. Order matters: the SDK port
-comes first, then the consuming firmware's build environment — CrossPoint's
-`ROADMAP.md` states this explicitly.
-
-**No CI validation** was found for device ports in the SDK, against CrossPoint's
-multi-environment build matrix. A port can therefore break without the SDK's own
-tests noticing.
-
-## Build and runtime
-
-- C++ (GitHub reports C++; CrossPoint builds it as C++20 / `-std=gnu++2a`).
-- No root `platformio.ini` or `library.json` — it ships
-  `platformio.sample.ini` and `platformio.crosspoint.sample.ini` instead, i.e.
-  it is consumed as a path/submodule dependency rather than a registry package.
-- Targets ESP32-C3 and ESP32-S3 in practice.
-- Repo ~3.5 MB, 18 open issues.
-
-## Sources
-
-| ID | What | URL | Retrieved |
-|---|---|---|---|
-| FI01 | Repository metadata | `api.github.com/repos/Free-Ink/freeink-sdk` | 2026-09-04 |
-| FI02 | `README.md` | `raw.githubusercontent.com/Free-Ink/freeink-sdk/main/README.md` | 2026-09-02 |
-| FI03 | `NOTICE` — lineage and attribution | same host | 2026-09-02 |
-| FI04 | `LICENSE` — MIT | same host | 2026-09-02 |
-| FI05 | Root tree listing | `api.github.com/.../git/trees/main` | 2026-09-04 |
-| FI06 | CrossPoint `.gitmodules` proving the submodule | `raw.githubusercontent.com/crosspoint-reader/crosspoint-reader/develop/.gitmodules` | 2026-09-04 |
-
-## Open questions
-
-- **No commit SHA pinned in this record.** Identity is by branch, which moves.
-  A later pass should pin `main`'s HEAD.
-- The drop-in-compatibility claim is untested.
-- The 74 % single-author concentration is carried over, not re-measured.
-- Which board profiles ship today was not enumerated file-by-file.
-
-## See also
-
-- **Devices with records here:** [Xteink X3](../../../devices/xteink/x3/README.md) · [X4](../../../devices/xteink/x4/README.md) · [X4 Pro](../../../devices/xteink/x4-pro/README.md) · [M5Stack PaperMono](../../../devices/m5stack/papermono/README.md)
-
-- [CrossPoint Reader](../../applications/crosspoint-reader/README.md) — the primary consumer
-- [CrossPlay](../../applications/crossplay/README.md) — consumes a fork of this SDK
-- [`guides/hardware`](../../../guides/hardware/README.md) — e-paper waveforms and bias rails
diff --git a/software/frameworks/freeink-sdk/contentprotection-library.md b/software/frameworks/freeink-sdk/contentprotection-library.md
deleted file mode 100644
index 73137b7..0000000
--- a/software/frameworks/freeink-sdk/contentprotection-library.md
+++ /dev/null
@@ -1,263 +0,0 @@
-# The ContentProtection library — how CrossPoint reads DRM'd books
-
-> The portable library behind CrossPoint's Adobe ADEPT support, read from source
-> and **validated against the captured headers and implementation** on
-> 2026-09-11.
->
-> Source reads are `executed-success`. **Nothing was built, flashed or run**, and
-> no book was decrypted. Runtime claims are `inferred` from source.
-
-## What it is
-
-`libs/book/ContentProtection` in `Free-Ink/freeink-sdk` @ `fde240fa` — a
-freestanding C++17 PlatformIO library (v0.1.0) with **storage and crypto both
-injected**, so it builds for host tests as well as the device. The firmware glue
-is `lib/Epub/ContentProtection.cpp` on branch `feat-sd-plugins`.
-
-Compiled `-fno-exceptions`, which shapes an unusual amount of the code — see
-[memory discipline](#memory-discipline), the most transferable part of it.
-
-## It is ADEPT-only. "LCP support" is a keyword, not code.
-
-This needs stating plainly because a `library.json` keyword implies otherwise:
-
-```
-library.json:5:  "keywords": "epub, ebook, decrypt, rights, protected, lcp",
-```
-
-**That is the only occurrence of `lcp` in the entire library.** There is no LCP
-implementation, no stub, no enum, and **no scheme abstraction of any kind**.
-
-The algorithm gate is a substring test (`ProtectedBook.cpp:377`):
-
-```cpp
-aes128 = tagAttr(tag, len, "Algorithm", &value) && value.find("aes128-cbc") != std::string::npos;
-```
-
-Anything not containing `aes128-cbc` is never recorded as encrypted. RSA is
-hardcoded to 1024-bit (`kRsaBlock = 128`) and `unwrapBookKey` hard-fails any
-other size. **Readium LCP requires AES-256-CBC, so this library cannot process
-LCP** — not "does not yet", *cannot*, without new code.
-
-## The public API is three virtuals
-
-```cpp
-// ContentProtection.h
-using ContentChunkSink = bool (*)(void* context, const uint8_t* data, size_t size);
-
-class ContentDecryptor {
-  virtual bool   isEncrypted(const char* itemPath) = 0;
-  virtual size_t decryptedSize(const char* itemPath) = 0;
-  virtual bool   decryptToSink(const char* itemPath, ContentChunkSink, void* context) = 0;
-};
-
-ContentDecryptor* openProtectedBook(const char* epubPath, std::string& err);
-```
-
-`openProtectedBook` has a documented **three-way return contract** that is easy
-to get wrong:
-
-| Return | Meaning |
-|---|---|
-| non-null | protected **and** readable — route item reads through it |
-| null, `err` **empty** | **plain content**, not protected — read normally |
-| null, `err` non-empty | protected but **unreadable** — no credential, or expired |
-
-## How a book is opened
-
-1. Scan the zip. **No `META-INF/encryption.xml` → plain EPUB, return null/empty.**
-2. Stream-parse the manifest, collecting FNV-1a-64 hashes of each
-   `CipherReference URI` whose algorithm contains `aes128-cbc`. The manifest is
-   **never materialised** — it measured ~60 KB on large books and was aborting
-   devices on allocation.
-3. Empty hash set → font obfuscation only, **not** treated as protected.
-4. Load rights: **sidecar `<book>.epub.rights` preferred**, in-zip
-   `META-INF/rights.xml` as fallback.
-5. Check account binding, unwrap the content key.
-
-`isEncrypted()` is a **binary search over 64-bit hashes**, not string comparison —
-a deliberate choice for a device with a slow CPU and a large manifest.
-
-## Why the sidecar exists
-
-From the firmware glue's own comment (`ContentProtection.cpp:129-131`):
-
-> *"Prefer an out-of-band rights document delivered as a sidecar next to the EPUB
-> (`<book>.epub.rights`), so the EPUB on disk stays **byte-identical to what the
-> server sent**. Falls back to a rights.xml injected into the zip."*
-
-The only file handle opened is `O_RDONLY`. **The library has no write API at
-all** — it is architecturally incapable of producing a decrypted file. A
-downstream caller could of course point a sink at one; that is the caller's
-doing, not the library's.
-
-## The read path — and the stage that is easy to miss
-
-Per zip entry, on demand. The on-disk entry is:
-
-```
-[16-byte IV][ AES-128-CBC( deflate( plaintext ) ) ]
-```
-
-So there is a **deflate stage** — the sink receives *decompressed* plaintext, not
-raw decrypted bytes:
-
-- IV = first 16 bytes of the entry
-- ciphertext decrypted in 2 KB chunks, CBC chaining carried manually across chunks
-- PKCS#7 unpad on the final chunk only
-- each decrypted chunk fed to `mz_inflate` (raw deflate, `-15`), emitted to the
-  sink in 4 KB pieces
-
-Entries failing `compressedSize < 32 || (compressedSize - 16) % 16 != 0` are
-rejected outright.
-
-`decryptedSize()` returns the zip central directory's `uncompressedSize` and is
-**not validated against actual output** — worth knowing if you rely on it.
-
-## Key unwrap
-
-An optional first pass handles newer ACS variants: AES-128-CBC with
-key = `sha256(keyType)` asymmetrically rotated by `strtol(keyType) mod 16`,
-IV = `deviceId XOR fulfillmentId XOR voucherId`. Then a raw RSA private operation
-with the credential's PKCS#8 key, followed by a **manual PKCS#1 v1.5 type-2
-padding check**; the content key is the trailing 16 bytes.
-
-### A fixed out-of-bounds write worth reading
-
-`ProtectedBook.cpp:148-151`:
-
-```cpp
-// keyType is attacker-controlled (from rights.xml); C++ % keeps the sign, so
-// a negative value would make `remainder` negative and drive the memcpys out
-// of bounds. Normalize into [0,16) — matches the reference's unsigned rotate.
-const int remainder = static_cast<int>(((nonce % 16) + 16) % 16);
-```
-
-**The fix is correct** — checked: with `remainder ∈ [0,16)`, the two reads reach
-at most offset 30 in a 32-byte digest. This is the only bug in this record
-confirmed *fixed* against source, and the comment is a model of the genre: names
-the attacker-controlled input, the language rule, and the consequence.
-
-## Credential storage — the sharp edge
-
-```cpp
-constexpr const char* kCredentialPath = "/.crosspoint/content.key";   // ContentProtection.cpp:30
-std::string privateLicenseKey;  // base64 PKCS#8 DER (clear; sensitive)  // Credential.h:31
-```
-
-A line-oriented `key: value` text file, magic `FREEINK-CONTENT-KEY 1`, on the
-**FAT32 SD card**. Consumed with a plain base64 decode — **no passphrase, no KDF,
-no device binding**:
-
-```cpp
-const std::string pkcs8 = base64Decode(identity.privateLicenseKey);   // ProtectedBook.cpp:181
-```
-
-**Base64 is an encoding, not encryption. The key is stored in the clear.**
-
-**Physical possession of the card ⇒ the private key ⇒ every book ever fulfilled
-to that device is decryptable offline, permanently.** The authors document this
-in the header rather than hiding it; it is a deliberate portability trade
-(survives a firmware reinstall).
-
-### One precision correction
-
-It is the **device's** ADEPT key — RSA-1024, registered to the account alongside
-`deviceUuid`, `fingerprint` and `serial` — **not an account master key**. The
-practical blast radius above is unchanged, but "your Adobe account's key"
-overstates it.
-
-PKCS#12 with a `base64(device key)` passphrase **does** appear in the codebase —
-but only in `pkcs12Extract`, under the header's *"client (off-device credential
-setup)"* section. It unwraps the Adobe-supplied bundle during provisioning. **It
-is never called on the read path and does not protect what sits on the card.**
-
-## Expiry is enforced in the firmware, not the library
-
-Easy to get wrong, and the handoff research did: **the portable library parses
-expiry and never checks a clock.** `finishOpen()` does exactly three checks —
-manifest present, account match, key unwrap.
-
-Enforcement lives in the glue (`ContentProtection.cpp:171-187`):
-
-```cpp
-// Loan enforcement. The clock is a persisted monotonic floor (TrustedTime):
-// it can lag real time while the device sat powered off, but can never be
-// rolled back — staying offline delays the due date at most by the
-// powered-off gap, it does not suspend it. A book carrying a due date with
-// no trustworthy clock at all fails closed rather than open.
-if (book->expiresAt() != 0) {
-  const int64_t now = trustedtime::trustedNow();
-  if (now == 0)             { err = "loan date unverified"; return nullptr; }
-  if (book->isExpired(now)) { err = "access expired";       return nullptr; }
-}
-```
-
-That is a **monotonic floor that fails closed** — materially more thought than
-"parsed and enforced". The error strings are a **UI contract** matched by the
-reader, so changing them breaks the user-facing message.
-
-Parsing detail: `expiresAt` comes from `<until>` inside a `<display>` element,
-else `fulfillmentEpoch + durationSecs`. **`expiresAt == 0` means *no expiry
-found*, not expired.**
-
-Two imprecisions in the parser, noted for anyone relying on it:
-
-- `until`/`duration` are scoped to a `<display>` element only — the code does
-  **not** verify a `permissions` parent, despite the header saying
-  "permissions/display".
-- The `duration` fallback takes `fulfillmentEpoch` from the **last `<date>`
-  element anywhere in the document**, not a sibling of `<fulfillment>` as the
-  adjacent comment implies.
-
-**Not verified:** `expiresAt()` and `isExpired()` are inline in `ProtectedBook.h`,
-which was not captured. The comparison itself is unread.
-
-## Memory discipline
-
-The most reusable engineering content here, driven by `-fno-exceptions` (a failed
-allocation `abort()`s rather than throwing):
-
-- `heapProbe()` nothrow probes **before every throwing allocation**
-- pre-reserved `carry` / `value` / hash buffers
-- SSO-sized fallback error literals for when the heap can't take a concatenation
-- cache reclaim before decrypt
-- **a documented allocation-ordering requirement**: the ~40 KB contiguous inflate
-  state must be taken *before* the 8 KB scratch, with a measured field failure
-  recorded in the comment (`maxAlloc=47092` with `41168` required)
-
-That last one is the kind of finding that only comes from a real device.
-
-## Crypto interface — ten methods, split by trust domain
-
-The header divides them explicitly:
-
-| Read path (on device) | Client (off-device setup) |
-|---|---|
-| `rsaPrivateRaw` — unwraps the book key | `rsaGenerate` |
-| `aes128CbcDecrypt` | `rsaPublicEncrypt` |
-| `sha1` | `rsaPrivateSignRaw` |
-| `sha256` | `aes128CbcEncrypt` |
-| | `pkcs12Extract` |
-| | `randomBytes` |
-
-`WolfsslCrypto` is the only captured implementation; host tests are stated to use
-OpenSSL. On ESP32, `rsaGenerate` routes to **mbedTLS** instead, because
-*"wolfSSL 5.7.2's Tom's Fast Math key-generation path is unstable on the
-ESP32-C3"* — an interesting note given keygen is nominally off-device.
-
-## What was not verified
-
-- **`ProtectedBook.h` was not captured** — so `expiresAt()`/`isExpired()` bodies
-  and the class definition are unread.
-- Also absent: `Credential.cpp` (the actual parser), `Zip.cpp`, `Xml.h`,
-  `Util.h`, and **`test/host/`** — which is what would show whether any
-  non-ADEPT scheme is exercised anywhere.
-- **Nothing was executed.** No book was opened, no credential parsed, no
-  expiry triggered.
-
-## See also
-
-- [Plugin architecture](../../applications/crosspoint-reader/plugins/plugin-architecture.md) — the other half of the chain
-- [`dtsbytebooks.com` review](../../applications/crosspoint-reader/plugins/dtsbytebooks-review.md) — who operates ADEPT now
-- [Calibre and the Libby path](../../tooling/calibre/README.md)
diff --git a/software/libraries/README.md b/software/libraries/README.md
deleted file mode 100644
index f587dff..0000000
--- a/software/libraries/README.md
+++ /dev/null
@@ -1,220 +0,0 @@
-# Graphics and display libraries for e-paper
-
-> The layer below a reader firmware: what draws pixels, what drives panels, and
-> what the licence choice costs you.
->
-> Snapshot **2026-09-04**. Repository facts `executed-success` (GitHub API).
-> **Nothing was built, linked or benchmarked** — no hardware. Capability and
-> suitability claims are `inferred`.
-
-**Classification:** libraries — you link against these and call them. Contrast
-[`frameworks/`](../frameworks/freeink-sdk/README.md), which call *you*.
-
-## The landscape
-
-| Library | ★ | Licence | HEAD | Last push | Layer |
-|---|---|---|---|---|---|
-| [`lvgl/lvgl`](https://github.com/lvgl/lvgl) | 24,586 | **MIT** | `a33757e2` | 2026-09-04 | Full widget UI toolkit |
-| [`olikraus/u8g2`](https://github.com/olikraus/u8g2) | 6,664 | BSD-2 *(see below)* | `9a93ba2e` | 2026-08-23 | Monochrome drawing + fonts |
-| [`adafruit/Adafruit-GFX-Library`](https://github.com/adafruit/Adafruit-GFX-Library) | 2,836 | BSD *(see below)* | `ac6d7c38` | 2026-04-09 | Minimal drawing primitives |
-| [`vroland/epdiy`](https://github.com/vroland/epdiy) | 1,916 | **LGPL-3.0** | `42c16127` | 2026-08-23 | Parallel e-paper driver + board |
-| [`waveshareteam/e-Paper`](https://github.com/waveshareteam/e-Paper) | 1,731 | **none** | `a794fbc3` | 2026-08-19 | Vendor panel demos |
-| [`ZinggJM/GxEPD2`](https://github.com/ZinggJM/GxEPD2) | 1,480 | **GPL-3.0** | `de82887e` | 2026-04-19 | SPI e-paper panel driver |
-| [`moononournation/Arduino_GFX`](https://github.com/moononournation/Arduino_GFX) | 1,137 | BSD *(see below)* | `b4c3cbe2` | 2026-08-30 | Fast colour display driver |
-| [`s00500/ESPUI`](https://github.com/s00500/ESPUI) | 1,124 | MIT *(see below)* | `1eb5e2ff` | 2026-04-30 | Browser-served UI, not on-device |
-| [`bitbank2/JPEGDEC`](https://github.com/bitbank2/JPEGDEC) | 625 | **Apache-2.0** | `86282979` | 2026-03-13 | JPEG decode for MCUs |
-| [`bitbank2/bb_epaper`](https://github.com/bitbank2/bb_epaper) | 207 | **GPL-3.0** | `29afe89e` | 2026-09-03 | "All 24-pin eink panels" |
-
-*"see below"* marks repositories GitHub reports as `NOASSERTION` — it cannot
-classify the licence automatically. That is **not** the same as unlicensed; it
-usually means a non-standard file or a licence header style Linguist doesn't
-match. `waveshareteam/e-Paper` is the genuinely licence-less one.
-
-## The finding that actually matters: e-paper libraries skew copyleft
-
-Sort the table by what layer it occupies and a pattern appears:
-
-| Layer | Typical licence |
-|---|---|
-| General graphics / UI (LVGL, Adafruit-GFX, u8g2, Arduino_GFX) | **permissive** — MIT / BSD |
-| **E-paper panel drivers** (GxEPD2, bb_epaper, epdiy) | **copyleft** — GPL-3.0 / LGPL-3.0 |
-
-**This is a real constraint on firmware architecture, not trivia.**
-[CrossPoint Reader](../applications/crosspoint-reader/README.md) and the
-[FreeInk SDK](../frameworks/freeink-sdk/README.md) are both **MIT**. Linking
-GxEPD2 (GPL-3.0) or `bb_epaper` (GPL-3.0) into a distributed firmware binary
-would place the combined work under the GPL. LGPL (epdiy) is more permissive but
-its dynamic-linking relief is close to meaningless on a statically-linked MCU
-image.
-
-That plausibly explains an otherwise odd choice: **FreeInk ships its own SSD1677
-and UC8253 drivers**, derived — per its `NOTICE` — from the MIT-licensed
-`open-x4-epaper/community-sdk` with authorship credited to CidVonHighwind, rather
-than adopting the far more popular GxEPD2. Writing panel drivers is real work
-that a mature GPL library had already done.
-
-**Marked `inferred`.** No maintainer has stated this motivation anywhere I found;
-it is the reading the licences and the code lineage support. But if you are
-choosing a driver for a permissively-licensed firmware, the constraint is real
-regardless of whether it motivated FreeInk.
-
-## What each is actually for
-
-### LVGL — the heavyweight
-A complete widget toolkit: objects, layouts, styles, animations, input devices,
-theming. Genuinely excellent, genuinely large, and designed for **colour,
-frequently-refreshed** panels.
-
-On e-paper it is a poor fit by default and needs deliberate work: LVGL assumes
-cheap partial redraws, e-paper does not. It supports 1-bit output and monochrome
-themes, but its animation and invalidation model fights the medium. **Nothing in
-the CrossPoint/FreeInk ecosystem uses it** — FreeInk wrote `FreeInkUI`, an
-immediate-mode layer sized for e-paper, instead.
-
-Use LVGL when you have a colour TFT and want widgets. On a 4-grey 800×480 e-paper
-reader it is usually the wrong tool.
-
-### GxEPD2 — the default Arduino e-paper driver
-The most widely used SPI e-paper library, covering an enormous panel matrix. If
-you are wiring a Waveshare or Good Display panel to an Arduino, this is what
-tutorials assume.
-
-**GPL-3.0**, which is the thing to notice before designing around it. Also last
-pushed **2026-04-19** — the least recently touched library in this table, which
-for a driver library tracking new panels is worth checking against your specific
-panel.
-
-### `bb_epaper` — the newer challenger
-"A frustration-free library for working with all 24-pin eink panels", from
-Larry Bank (`bitbank2`), who also wrote JPEGDEC. Actively pushed (2026-09-03),
-smaller and more opinionated than GxEPD2. **GPL-3.0**, same constraint.
-
-Relevant here: prior research recorded it as shipping **M5Stack PaperMono
-support**, which makes it one of the few third-party libraries that names this
-board.
-
-### `u8g2` — monochrome done properly
-The strongest option for **monochrome-only** work: a huge, well-curated font
-collection, tight memory behaviour, and support for a very wide range of
-displays including many e-paper panels. Permissively licensed (BSD-2-Clause).
-
-If your device is 1-bit and text-heavy, u8g2's font handling is better than
-anything else in this list.
-
-### Adafruit-GFX — the lowest common denominator
-Small, permissive, and the drawing API that half the Arduino ecosystem inherits.
-It is a **drawing primitive layer**, not a driver — you pair it with a
-device-specific backend. Its value is ubiquity and licence, not capability.
-
-### `epdiy` — parallel-interface panels
-For large, cheap **parallel-interface** e-paper (repurposed laptop and e-reader
-panels), which SPI libraries cannot drive at all. Different problem space to
-GxEPD2. **LGPL-3.0**.
-
-### `waveshareteam/e-Paper` — vendor demos
-Waveshare's own panel code. Broad panel coverage and **no licence file at all**,
-which makes it all-rights-reserved by default and awkward to vendor. Treat it as
-reference material for initialisation sequences rather than a dependency — which,
-in practice, is how the ecosystem uses it.
-
-### `JPEGDEC` — decode, not draw
-Apache-2.0, MCU-optimised JPEG decode. Notable because
-**`crosspoint-reader` forked it into its own org** — a small, permissively
-licensed, single-purpose library is exactly the kind of dependency that survives
-in constrained firmware.
-
-### `ESPUI` — a different axis entirely
-Serves a web UI from the ESP32 to a browser. **Nothing renders on the device.**
-It solves the same problem upstream CrossPoint's JavaScript plugin system solves
-— configuration and interaction via a phone — and is worth knowing about for that
-reason, but it is not a display library. See
-[plugin systems](../applications/crosspoint-reader/plugins/README.md).
-
-
-## Licences resolved by reading the files (2026-09-04)
-
-The table marks four repositories `NOASSERTION` — GitHub could not classify them.
-That was listed as an open question. All four have now been **read directly**
-(`executed-success`):
-
-| Library | Actual licence | Evidence |
-|---|---|---|
-| `olikraus/u8g2` | **BSD-2-Clause** (new-BSD) | `LICENSE`: *"The U8g2lib code … is licensed under the terms of the new-bsd license (two-clause bsd license)"* |
-| `adafruit/Adafruit-GFX-Library` | **BSD** | `license.txt`: *"Software License Agreement (BSD License), Copyright (c) 2012 Adafruit Industries"* |
-| `moononournation/Arduino_GFX` | **BSD** | `license.txt` — byte-for-byte Adafruit's, **including Adafruit's own copyright line** |
-| `s00500/ESPUI` | **MIT** | `LICENSE`: *"The MIT License (MIT), Copyright (c) 2017 Lukas Bachschwell"* |
-
-None is unlicensed. `NOASSERTION` meant a non-standard filename or preamble, not
-absence — as suspected, and now confirmed rather than assumed.
-
-### ⚠ The u8g2 font trap
-
-Reading the file surfaced something the licence label hides. `u8g2`'s `LICENSE`
-says, immediately after declaring the code BSD-2:
-
-> **Fonts are licensed under different conditions.**
-
-And the file **contains GPL text** further down, because some bundled fonts carry
-GPL terms while others are BSD, public-domain, or under bespoke foundry licences.
-
-**So "u8g2 is BSD" is true of the code and false of the deliverable.** A firmware
-that links u8g2 *and ships its fonts* may be taking on obligations — including
-copyleft — that the repository's headline licence does not suggest. Anyone
-shipping a permissively-licensed binary needs to check the specific fonts they
-compile in, not the library.
-
-This is exactly the shape of the copyleft problem described above, one layer
-lower: the code is permissive, the **content** is not uniformly so. Worth noting
-that the CrossPoint ecosystem keeps fonts in a **separate repository**
-(`crosspoint-reader/crosspoint-fonts`, which itself carries **no licence file**)
-and loads them from SD at runtime rather than compiling them in — which sidesteps
-the linking question entirely, whether or not that was the motivation.
-
-### `Arduino_GFX` carries Adafruit's copyright
-
-Its `license.txt` is Adafruit's BSD text verbatim, retaining *"Copyright (c) 2012
-Adafruit Industries"*. That is consistent with its API lineage — it descends from
-Adafruit-GFX — but it means the file does not name `Arduino_GFX`'s own author.
-Recorded as an observation; the practical effect is the same BSD terms either way.
-
-## Choosing, for an e-paper reader
-
-| If you need | Use | Watch out for |
-|---|---|---|
-| Widgets on a colour TFT | **LVGL** | Overkill and a poor invalidation fit on e-paper |
-| Monochrome text and fonts | **u8g2** | Not a full UI toolkit |
-| Drive an SPI e-paper panel, permissive licence not required | **GxEPD2** | **GPL-3.0**; least-recently-updated here |
-| Same, actively maintained | **bb_epaper** | **GPL-3.0** |
-| Large parallel e-paper | **epdiy** | **LGPL-3.0**; different hardware entirely |
-| Panel init sequences as reference | `waveshareteam/e-Paper` | **No licence** — read, don't vendor |
-| A permissively licensed reader firmware | **FreeInk SDK** | It is a *framework*, not a library — it takes over structure |
-
-**The licence column is the one that constrains architecture.** Everything else
-is a preference; GPL versus MIT is a decision about what you can ship.
-
-
-## Sources
-
-Repository metadata and HEAD commits for all eleven repositories, GitHub REST
-API, authenticated, retrieved **2026-09-04**. SHAs are in the table and are the
-identity to cite.
-
-## Open questions
-
-- **Nothing was built, linked, benchmarked or run.** No binary size, refresh
-  timing, or RAM figure here is measured; there is no hardware.
-- ~~The `NOASSERTION` licences were not resolved~~ — **closed 2026-09-04**: all
-  four read at source (see above). Outstanding sub-question: **u8g2's per-font
-  licences were not enumerated**, and at least some are not BSD.
-- The claim that GxEPD2's GPL motivated FreeInk's own drivers is `inferred` from
-  licences and lineage; **no maintainer statement was found**.
-- Which e-paper panels each library actually supports was not enumerated.
-- `bb_epaper`'s reported PaperMono support is carried over from earlier research
-  and was **not verified** in this pass.
-
-## See also
-
-- [FreeInk SDK](../frameworks/freeink-sdk/README.md) — ships its own SSD1677/UC8253 drivers, and why that matters
-- [`components/solomon-systech/ssd1677`](../../components/solomon-systech/ssd1677/README.md) — the controller most of this targets
-- [`guides/hardware`](../../guides/hardware/README.md) — e-paper waveforms, bias rails, ghosting
-- [PaperMono e-paper feature guide](../../devices/m5stack/papermono/features/epaper-display.md)
diff --git a/software/tooling/README.md b/software/tooling/README.md
deleted file mode 100644
index 99fad42..0000000
--- a/software/tooling/README.md
+++ /dev/null
@@ -1,157 +0,0 @@
-# CrossPoint / Xteink host tooling
-
-> The companion tools around the firmware: flashers, a simulator, a sync server,
-> a web toolbox and asset repositories. All host-side or browser-side.
->
-> Snapshot **2026-09-04**. Repository facts `executed-success` (GitHub API).
-> **Nothing was installed, built or run** — no hardware, no browser session.
-> Capability descriptions are `inferred` from repository metadata and READMEs.
-
-**Classification:** tooling — runs on your computer or in a browser, not on the
-device. For the firmware itself see
-[CrossPoint Reader](../applications/crosspoint-reader/README.md).
-
-## The set
-
-| Tool | ★ | Language | Licence | HEAD | Last push | What it does |
-|---|---|---|---|---|---|---|
-| [`xteink-flasher`](https://github.com/crosspoint-reader/xteink-flasher) | 136 | TypeScript | MIT | `2b09cb43` | 2026-05-20 | **Browser-based flasher** (Web Serial) |
-| [`xtlibre`](https://github.com/shakogegia/xtlibre) | 81 | TypeScript | MIT | `9d2c47a3` | 2026-04-07 | Self-hosted companion app — *third-party* |
-| [`crosspoint-simulator`](https://github.com/crosspoint-reader/crosspoint-simulator) | 55 | C++ | MIT | `c55f168b` | 2026-09-02 | **Run the firmware without a device** |
-| [`crosspoint-sync`](https://github.com/crosspoint-reader/crosspoint-sync) | 42 | TypeScript | MIT | `a986b3ce` | 2026-08-19 | Lightweight **KoSync** server for progress/stats |
-| [`crosspoint-tools`](https://github.com/crosspoint-reader/crosspoint-tools) | 35 | JavaScript | MIT | `a3f0abf6` | 2026-09-01 | Website and browser tools |
-| [`crosspoint-fonts`](https://github.com/crosspoint-reader/crosspoint-fonts) | 21 | — | **none** | `e435b40d` | 2026-08-20 | Prebuilt device fonts |
-| [`Murphy`](https://github.com/crosspoint-reader/Murphy) | 15 | HTML | MIT | `78ef80e6` | 2026-08-13 | Firmware dumps + support docs for Hamgeek M3/M4 |
-| [`escape-hatch`](https://github.com/crosspoint-reader/escape-hatch) | 10 | C++ | **none** | `90841adf` | 2026-08-22 | **400 kB SD-card recovery flasher** |
-| [`community-sdk`](https://github.com/crosspoint-reader/community-sdk) | 5 | C++ | MIT | `198ad267` | 2026-06-24 | The pre-FreeInk SDK — historical |
-
-All but two are MIT. `crosspoint-fonts` and **`escape-hatch` carry no licence
-file**, which for a recovery tool people are told to use when their device is
-bricked is an unfortunate gap — it is all-rights-reserved by default.
-
-## The two flashers, and why both exist
-
-**`xteink-flasher`** is the normal path: a browser page using **Web Serial** to
-talk to the device over USB. No toolchain, no `esptool` install, no driver
-wrangling beyond the OS recognising the port. Web Serial means **Chrome or Edge
-only** — Firefox and Safari have declined to implement it — and it needs HTTPS or
-localhost.
-
-**`escape-hatch`** exists for when that cannot work. It is a *firmware* — a
-minimal SD-card flasher, deliberately **400 kB** — that you flash onto the device
-so it can then flash something else from an SD card. Its reason to exist is the
-ecosystem's own recovery problem: an ecosystem finding recorded elsewhere in this
-knowledge base is that **"locked" devices block USB flashing but still accept
-SD-card `update.bin`**. `escape-hatch` is the lever for that case.
-
-Its size is the design: at 400 kB it fits where a full firmware will not.
-
-Upstream also ships `docs/fix-bricked-xteink.md`. **A project with a dedicated
-unbricking document, a recovery firmware and a locked-device workaround is
-telling you something about its risk profile** — see
-[`guides/serial-access`](../../guides/serial-access/README.md) for the host side
-of avoiding that situation.
-
-## The simulator — the most underrated tool here
-
-`crosspoint-simulator` (★55, C++, MIT, actively pushed 2026-09-02) runs the
-firmware on a desktop. `uxjulia/crossink-simulator` is the equivalent for that
-fork, using SDL.
-
-Why it matters more than its star count suggests:
-
-- **No hardware needed** to develop UI, layout, typography or EPUB rendering —
-  which is most of what this firmware does.
-- **No flash cycles**, so no wear and no bricking risk during iteration.
-- CrossPlay's fork ships `platformio.sim.ini` as a tracked file precisely so
-  every checkout can run the simulator, and it also produces a **WASM browser
-  build** of the real firmware.
-
-For anyone evaluating this ecosystem without buying a device — which describes
-this knowledge base's own position — the simulator is the only route to
-first-hand observation.
-
-> ✅ **It has now been built and run.** CrossPoint firmware compiles and executes
-> natively on NixOS/x86-64 — `[SUCCESS]`, a 6.6 MB binary, running headless under
-> `SDL_VIDEODRIVER=dummy`. Seven portability problems had to be solved, three of
-> which are general toolchain bugs rather than NixOS quirks (a **C23 `bool`**
-> breakage in QRCode, an **`#include_next` ordering** assumption, and missing
-> defines/`-lcrypto` in the sample config).
->
-> Full working configuration, commands and findings:
-> **[Building the simulator on NixOS](crosspoint-simulator-build-notes.md)**.
-
-## Sync — and a good standards decision
-
-`crosspoint-sync` is a *"Lightweight KoSync Server for Syncing
-Crosspoint/CrossInk stats & progress"*.
-
-**KoSync is KOReader's sync protocol.** Rather than inventing a format, the
-ecosystem implemented an existing one — so a CrossPoint device can share reading
-position with KOReader clients and with any existing KoSync server. That is a
-better decision than it looks: it means progress sync is not locked to one
-firmware's lifetime.
-
-Note it explicitly serves **CrossPoint *and* CrossInk**, which fits the
-[fork network's](../ecosystems/crosspoint-freeink/fork-network.md) division of
-labour — upstream defers stats to forks, and shared infrastructure serves both.
-
-`xtlibre` (★81, third-party, MIT) is a self-hosted companion app for Xteink and
-CrossPoint readers. **Last pushed 2026-04-07** — the least current tool in this
-set, five months stale at snapshot.
-
-## Assets and hardware support
-
-- **`crosspoint-fonts`** — prebuilt fonts for the device. Fonts live on the SD
-  card, not in the book; see upstream's `docs/sd-card-fonts.md`. `uxjulia` maintains
-  parallel `crossink-fonts` and `crossink-dictionaries` repositories.
-- **`Murphy`** — firmware dumps and initial support documentation for the
-  **Hamgeek M3/M4**. Evidence that this ecosystem's device reach extends past
-  Xteink hardware, consistent with upstream's stated "not Xteink-only" scope.
-- **`community-sdk`** — the **pre-FreeInk SDK**, created by Dave Allie the day
-  before CrossPoint's public release. Now historical: FreeInk's `NOTICE` credits
-  it as the work FreeInk was derived from. Kept for lineage; not a current
-  dependency. See [FreeInk SDK](../frameworks/freeink-sdk/README.md).
-
-## Practical notes
-
-**Flashing, in order of preference:** `xteink-flasher` in Chrome/Edge → `esptool`
-if you have a toolchain → `escape-hatch` + SD card if USB is blocked or the
-device is locked.
-
-**Before flashing anything, save a full flash dump.** An ecosystem finding
-recorded in this knowledge base is that most "bricks" are a short restore *if a
-dump exists* — and locked devices cannot produce one, which is exactly when you
-most want it.
-
-**Serial permissions** are a separate problem from any of these tools and are
-covered in [`guides/serial-access`](../../guides/serial-access/README.md).
-`xteink-flasher` sidesteps Linux group membership entirely by using Web Serial,
-which is a genuine advantage of the browser approach.
-
-## Sources
-
-All retrieved **2026-09-04** from the GitHub REST API, authenticated. Repository
-metadata and HEAD commit for each of the nine repositories tabulated above; SHAs
-are given in the table and are the identity to cite, since branches move.
-
-## Open questions
-
-- **Nothing was installed, built or run.** No flasher was used, no simulator
-  started, no sync server deployed.
-- `xteink-flasher`'s device coverage (which boards, which chip families) was not
-  read from its source.
-- Whether `crosspoint-simulator` supports the **PaperMono** board profile is
-  unknown, and would determine whether this knowledge base could observe that
-  device's firmware behaviour without hardware.
-- `escape-hatch`'s licence absence should be raised upstream; it is a recovery
-  tool users are directed to.
-- No tool here was checked for PaperMono-specific support.
-
-## See also
-
-- [CrossPoint Reader](../applications/crosspoint-reader/README.md) · [plugin systems](../applications/crosspoint-reader/plugins/README.md)
-- [Calibre and the content pipeline](calibre/README.md)
-- [Serial device access](../../guides/serial-access/README.md)
-- **Devices these tools flash:** [Xteink X3](../../devices/xteink/x3/README.md) · [X4](../../devices/xteink/x4/README.md) · [X4 Pro](../../devices/xteink/x4-pro/README.md)
-- [Fork network](../ecosystems/crosspoint-freeink/fork-network.md)
diff --git a/software/tooling/calibre/README.md b/software/tooling/calibre/README.md
deleted file mode 100644
index ca7e2f2..0000000
--- a/software/tooling/calibre/README.md
+++ /dev/null
@@ -1,199 +0,0 @@
-# Calibre — e-book management for e-reader workflows
-
-> The host-side half of getting books onto an ESP32 e-reader. Covers Calibre
-> itself, its device-driver model, and the plugin landscape around CrossPoint,
-> Libby/OverDrive and DRM.
->
-> Snapshot **2026-09-04**. Repository facts are `executed-success` (GitHub API).
-> **Nothing was installed, run or tested** — no Calibre instance and no e-reader
-> in this project. Procedures are `reported-working`.
-
-**Classification:** tooling — runs on your computer, not the device.
-
-## Why it matters here
-
-An ESP32 e-reader is a display for files you put on it. Calibre is how most
-people convert, tag and transfer those files, and it is the point where three
-separate problems meet: **format conversion**, **device transfer**, and **DRM**.
-Each has different tooling and very different legal and maintenance risk.
-
-## Installing Calibre
-
-| Platform | Command | Notes |
-|---|---|---|
-| Debian / Ubuntu | `sudo apt install calibre` | Distribution builds lag upstream, sometimes by a lot |
-| **Arch** | `sudo pacman -S calibre` | Well-maintained, close to upstream |
-| **NixOS** | `environment.systemPackages = [ pkgs.calibre ];` | Declarative; see caveat below |
-| Any Linux | `sudo -v && wget -nv -O- https://download.calibre-ebook.com/linux-installer.sh \| sudo sh /dev/stdin` | Upstream's own installer — newest version, but installs outside the package manager |
-| macOS | `brew install --cask calibre` | |
-| Windows | `winget install calibre.calibre` | |
-
-**NixOS caveat.** Calibre's plugin system writes into its configuration
-directory, not the Nix store, so **plugins do work** — but any plugin that
-expects to compile or vendor a native binary at install time may fail against the
-store's read-only paths and missing FHS layout. Plugins that are pure Python are
-fine. See [`guides/nixos`](../../../guides/nixos/README.md) for the general
-pattern of dealing with this.
-
-**Device access:** Calibre talks to USB mass-storage devices and to microSD cards
-mounted normally — it does **not** need serial-port permissions. Serial access is
-a flashing concern, not a Calibre one; see
-[`guides/serial-access`](../../../guides/serial-access/README.md).
-
-## How Calibre talks to devices
-
-Two mechanisms, and the distinction matters for e-readers:
-
-1. **Device drivers** — Python classes that recognise a device by USB VID/PID or
-   by filesystem layout, then define where books go and what metadata is written.
-   This is how "plug in Kindle, click Send to Device" works.
-2. **Plain folder sync** — no driver; you copy files to a mounted SD card.
-
-For ESP32 e-readers the second is the default: **there is no USB mass-storage
-mode on most of these boards.** You take the microSD out, or you use the
-firmware's web server. That is why the CrossPoint Calibre plugins exist —
-they recognise a *CrossPoint-formatted SD card* rather than a USB device.
-
-## The CrossPoint Calibre plugins
-
-| Plugin | ★ | Licence | HEAD | Last push | What |
-|---|---|---|---|---|---|
-| [`crosspoint-reader/calibre-plugins`](https://github.com/crosspoint-reader/calibre-plugins) | **222** | **MIT** | `460c5308` | 2026-08-03 | **Official.** The one to use |
-| [`ChristianVaughn/Crosspoint-Calibre-Plugin`](https://github.com/ChristianVaughn/Crosspoint-Calibre-Plugin) | 4 | GPL-3.0 | `f58c2c1b` | 2026-06-05 | Third-party; auto-recognises a CrossPoint SD card |
-| [`yemM/crosspoint-reader-sd-calibre-plugins`](https://github.com/yemM/crosspoint-reader-sd-calibre-plugins) | 2 | **none** | `087d86da` | 2026-04-18 | Third-party device plugin for CrossPoint-formatted microSD (Xteink X4) |
-
-The official plugin is actively maintained and MIT. The two third-party ones
-solve the same problem at much lower star counts; `yemM`'s has **no licence
-file**, so it is all-rights-reserved by default.
-
-**Installing a Calibre plugin:** *Preferences → Plugins → Load plugin from file*,
-pointing at the `.zip`. Calibre must be restarted. Plugins live in Calibre's
-config directory (`~/.config/calibre/plugins` on Linux), not in the package.
-
-## Libby / OverDrive
-
-[`ping/libby-calibre-plugin`](https://github.com/ping/libby-calibre-plugin) —
-★128, **GPL-3.0**, HEAD `1d115776`, **last push 2023-12-01**.
-
-It integrates library loans from OverDrive's Libby service into Calibre: browse
-loans, download, and manage holds without the Libby app.
-
-**The maintenance状況 is the headline.** Last pushed **December 2023** — close to
-three years stale at this snapshot. OverDrive's API and authentication are
-vendor-controlled and change without notice, so a three-year-old client is a
-substantial risk. Whether it currently works was **not tested here** and should
-be verified before relying on it.
-
-### What it can and cannot give you
-
-This is where people's expectations break, so it is worth being precise:
-
-- **EPUBs that Libby serves without DRM** — some publishers, and most public-domain
-  titles — come through cleanly and can go straight to a device.
-- **Most commercial library loans are DRM-protected**, typically Adobe ADEPT
-  (`.acsm` fulfilment) or OverDrive's own scheme. **The Calibre plugin downloads
-  the loan; it does not remove protection.** A protected file will not open on a
-  **stock** CrossPoint reader — but see the correction immediately below: on the
-  plugin firmware branch it **will**, via licensed ADEPT playback.
-- **Audiobooks** are a separate pipeline and not relevant to an e-paper reader.
-
-So "Libby → Calibre → e-reader" works end-to-end only for unprotected titles
-unless a DRM step is inserted — which is the next section, and it is where the
-legal picture changes.
-
-
-> ⚠ **CORRECTION 2026-09-11 — the claim below that no CrossPoint firmware has a
-> DRM client is WRONG.** The `feat-sd-plugins` branch carries
-> `lib/Epub/ContentProtection.cpp`, which reads a `<book>.epub.rights` sidecar
-> against a device credential at `/.crosspoint/content.key` and decrypts **at
-> read time**, keeping the EPUB byte-identical on disk. Combined with the
-> `protected-content` or `libby` plugins, a CrossPoint device is an
-> **ADEPT-activated reader** and opens protected library loans directly.
-> Full detail: [the Libby path](../../applications/crosspoint-reader/plugins/libby-path.md).
-> The text below is retained for history.
-
-## DRM tooling — status and honest framing
-
-**DeDRM** is the well-known Calibre plugin for stripping e-book DRM.
-
-| Repository | ★ | Licence | HEAD | Last push |
-|---|---|---|---|---|
-| [`apprenticeharper/DeDRM_tools`](https://github.com/apprenticeharper/DeDRM_tools) | **15,323** | none detected | `776f146c` | **2024-08-20** |
-| [`noDRM/DeDRM_tools`](https://github.com/noDRM/DeDRM_tools) | 10,300 | none detected | `7379b453` | **2024-11-10** |
-
-**Both are effectively dormant.** The original (`apprenticeharper`) has not been
-pushed since August 2024; the active fork (`noDRM`) since November 2024. That is
-roughly two years before this snapshot, during which Calibre has had multiple
-major releases and Amazon has changed KFX handling more than once.
-
-Neither repository has a detected licence, which for a redistributed Calibre
-plugin is its own oddity.
-
-**The legal position is jurisdiction-dependent and this record does not give
-legal advice.** Circumventing technological protection measures is unlawful in
-many jurisdictions (US DMCA §1201, EU InfoSoc Article 6) **regardless of whether
-you own or have legally borrowed the content**, with narrow and varying
-exceptions — accessibility and preservation among them in some countries. Some
-jurisdictions permit personal-use format shifting; many do not.
-
-What this knowledge base records, per its own method, is **metadata and
-observable fact**: these tools exist, at these URLs, at these commits, in this
-state of maintenance. It does not recommend a workflow, and "the maintainers
-stopped in 2024" is the practically relevant fact independent of the legal one.
-
-**Adobe ADEPT / `.acsm`.** A `.acsm` file is not a book — it is a fulfilment
-token that Adobe Digital Editions exchanges for the actual EPUB. Handling it
-requires an ADE authorisation. `libgourou` is the main open-source implementation.
-Same legal caveats apply.
-
-## What actually reaches an ESP32 e-reader
-
-Setting DRM aside, the practical pipeline is:
-
-```
-source file (EPUB) → Calibre (convert / tag / cover)
-                   → CrossPoint Calibre plugin  OR  manual copy
-                   → microSD card  OR  firmware web server
-                   → device
-```
-
-Format notes for CrossPoint-class firmware:
-
-- **EPUB is the target format.** The [FreeInk SDK](../../frameworks/freeink-sdk/README.md)
-  ships `FreeInkBook`, a full EPUB engine — streaming parse, CSS, UAX #14 line
-  breaking with hyphenation.
-- **Simplify before transferring.** Heavy CSS, embedded fonts and large images
-  cost parse time and RAM on a device where the ESP32-C3 sets the memory ceiling.
-  `uxjulia/auto-epub-optimizer` exists specifically for this.
-- **Fonts and hyphenation dictionaries are device-side**, not embedded per book —
-  see `crosspoint-reader/crosspoint-fonts` and upstream's `docs/sd-card-fonts.md`.
-
-## Related tooling
-
-| Tool | ★ | Licence | HEAD | What |
-|---|---|---|---|---|
-| [`shakogegia/xtlibre`](https://github.com/shakogegia/xtlibre) | 81 | MIT | `9d2c47a3` | Self-hosted companion app for Xteink and CrossPoint readers |
-| [`crosspoint-reader/crosspoint-sync`](https://github.com/crosspoint-reader/crosspoint-sync) | 42 | MIT | `a986b3ce` | Lightweight **KoSync** server — syncs reading progress and stats across devices |
-| `uxjulia/auto-epub-optimizer` | 25 | — | — | Pre-processes EPUBs for constrained readers |
-
-`crosspoint-sync` implementing **KoSync** is worth noting: that is KOReader's
-sync protocol, so the ecosystem deliberately reuses an existing standard rather
-than inventing one.
-
-## Sources
-
-All retrieved **2026-09-04** from the GitHub REST API, authenticated:
-repository metadata and HEAD commit for each repository named above. Commit SHAs
-are given at first mention and are the identity to cite — branch names move.
-
-## Open questions
-
-- **Nothing was installed or tested.** Whether the Libby plugin still functions
-  against OverDrive's current API is unknown and is the most consequential
-  unknown here.
-- The official CrossPoint Calibre plugin's actual capabilities were read from its
-  description, not its source.
-- **`ruqqq/crosspoint-plugins`** (the on-device plugin store) is a *different
-  thing* from Calibre plugins and is covered separately — see
-  [the CrossPoint plugin systems record](../../applications/crosspoint-reader/plugins/README.md).
-- No format-conversion benchmark or file-size guidance is measured here.
diff --git a/software/tooling/crosspoint-simulator-build-notes.md b/software/tooling/crosspoint-simulator-build-notes.md
deleted file mode 100644
index 230c6a9..0000000
--- a/software/tooling/crosspoint-simulator-build-notes.md
+++ /dev/null
@@ -1,243 +0,0 @@
-# Building and running the CrossPoint simulator on NixOS
-
-> **Result: `[SUCCESS]`.** CrossPoint Reader firmware compiled natively and ran
-> on an x86-64 NixOS host with no e-reader hardware, 2026-09-04.
->
-> Evidence status **`executed-success`** — every command below was run and the
-> stated outcome observed. This is the first hardware-free execution of this
-> firmware recorded in this knowledge base, and it converts a set of previously
-> `inferred` claims into observed fact.
-
-Related: [`crosspoint-simulator` in the tooling record](README.md) ·
-[CrossPoint Reader](../applications/crosspoint-reader/README.md) ·
-[FreeInk SDK](../frameworks/freeink-sdk/README.md)
-
-## What was built
-
-| Item | Value |
-|---|---|
-| Firmware | `crosspoint-reader/crosspoint-reader` @ **`e6139861a2a8c634aa18c333b7e214ee51a9965c`** |
-| Submodule | `Free-Ink/freeink-sdk` @ **`68425f8eec1246a0be0c0f311540f60ad733fa76`** |
-| Simulator | `crosspoint-reader/crosspoint-simulator` @ **`c55f168bc0e677fdb32312c8be4b5874469465e6`** |
-| Host | NixOS, x86-64, **GCC 15.3.0**, PlatformIO Core 6.1.19, SDL2 2.32.70 (sdl2-compat) |
-| Output | `.pio/build/simulator/program`, **6,649,712 bytes** |
-| Build time | ~51 s cold, ~8 s incremental |
-| Run | Executes; with `SDL_VIDEODRIVER=dummy` it runs to the timeout with **no errors** once its virtual SD card exists |
-
-## Seven portability problems, and their fixes
-
-The simulator README warns that platforms other than macOS and Ubuntu-under-WSL
-"may need additional libraries or platform-specific stubs". This is what that
-meant in practice. **None of these are in the sample config.**
-
-### 1. The simulator must *not* inherit the SDK's hardware libraries
-
-The single most important finding, and the one that costs the most time.
-
-The firmware's `[base]` env declares `lib_deps` pulling in fourteen `freeink-sdk`
-libraries. **The simulator provides its own stubs for those** — it ships
-`Arduino.h`, `BoardConfig.h`, `EInkDisplay.h`, `BatteryMonitor.h`, `ESP.cpp` and
-more. Inheriting `${base.lib_deps}` compiles the *real* hardware libraries, which
-then fail on `pinMode`, `digitalWrite`, `HIGH`, `LOW`, `SPISettings` — Arduino
-symbols that do not exist natively.
-
-**But two of the fourteen are not hardware and must be kept:** `FreeInkUI`
-(provides `FreeInkApp.h`) and `Icons`. Ignoring those fails with
-`fatal error: FreeInkApp.h: No such file or directory`.
-
-So the correct split is: **ignore the hardware libs, keep the UI/asset libs.**
-
-### 2. GCC 15 defaults to C23, which breaks the QRCode library
-
-`qrcode.h` contains the AVR-era idiom:
-
-```c
-#ifndef __cplusplus
-typedef unsigned char bool;
-static const bool false = 0;
-static const bool true  = 1;
-#endif
-```
-
-In **C23**, `bool`, `true` and `false` are keywords, so this is now a syntax
-error: `'bool' cannot be defined via 'typedef'`. GCC 15 defaults to `gnu23`.
-
-This will affect **anyone building this on a current toolchain**, not just NixOS.
-Passing `-std=gnu17` does not help — PlatformIO deduplicates `-std=` flags and
-the C++ standard wins. The fix used here was a local patch to the vendored
-header, guarding on `__STDC_VERSION__ < 202311L`.
-
-### 3. `char` signedness differs from the target
-
-The firmware embeds generated data tables (e.g.
-`src/network/html/js/jszip_minJs.generated.h`) containing bytes above 127. On
-ESP32 (Xtensa and RISC-V) `char` is **unsigned**; on x86-64 Linux it is
-**signed**, so those initialisers become narrowing conversions and the build
-fails with dozens of `-Wnarrowing` errors.
-
-**Fix:** `-funsigned-char`, which matches the target's convention rather than
-suppressing the diagnostic.
-
-### 4. PNGdec and JPEGDEC need `memcpy_P`
-
-Both call the AVR/ESP `pgmspace` API, which does not exist on a native host.
-Supplying it as a **`-D` macro breaks compilation** — `memcpy_P` also appears in
-function signatures, so the macro corrupts them. A forced-include header with a
-real inline function works:
-
-```c
-/* sim-compat.h */
-#pragma once
-#include <string.h>
-#include <stdint.h>
-#ifndef PROGMEM
-#define PROGMEM
-#endif
-static inline void *memcpy_P(void *d, const void *s, size_t n) { return memcpy(d, s, n); }
-#ifndef pgm_read_byte
-static inline uint8_t pgm_read_byte(const void *p) { return *(const uint8_t *)p; }
-#endif
-```
-
-added with `-include sim-compat.h`.
-
-### 5. The documented "native decoders" mode did not work
-
-The sample config offers `-DCROSSPOINT_SIM_USE_NATIVE_DECODERS`. The simulator's
-`PNGdec.h` / `JPEGDEC.h` shims implement it with **`#include_next`**, which
-requires the simulator's include directory to precede the real library's on the
-command line. PlatformIO's dependency-graph ordering puts
-`.pio/libdeps/simulator/JPEGDEC/src` **first**, so `__has_include_next` finds
-nothing and the shim raises
-`#error "CROSSPOINT_SIM_USE_NATIVE_DECODERS requires JPEGDEC in this PlatformIO environment"`.
-
-**Not used.** The ordinary Arduino PNGdec/JPEGDEC path plus the compat header
-above works instead. This looks like a genuine latent bug in the simulator for
-any environment where PlatformIO orders includes this way, rather than anything
-NixOS-specific — `inferred`, not reported upstream.
-
-### 6. Three defines the sample config omits
-
-Inherited from `[base]` on real builds and silently required:
-
-- `-DCROSSPOINT_VERSION=\"…\"` — otherwise `BootActivity.cpp` fails
-- `-DXML_CONTEXT_BYTES=1024` — expat refuses to build without it
-- `-DPNG_MAX_BUFFERED_PIXELS=16416` — `PngToFramebufferConverter.cpp` fails
-
-### 7. `-lcrypto` for MD5
-
-`KOReaderDocumentId.cpp` uses OpenSSL's `MD5_Init` / `MD5_Update` / `MD5_Final`.
-The README mentions needing OpenSSL headers but the sample config does not link
-the library, so the build compiles fully and then fails at **link** time.
-
-## The working configuration
-
-Appended to the firmware's `platformio.ini`. **Local build experiment, not
-upstream** — do not send this as a patch without cleaning it up.
-
-```ini
-[env:simulator]
-platform = native
-lib_ldf_mode = deep+
-lib_compat_mode = off
-lib_deps =
-  symlink://../crosspoint-simulator
-  bblanchon/ArduinoJson @ 7.4.2
-  ricmoo/QRCode @ 0.0.1
-  bitbank2/PNGdec @ 1.1.6
-  https://github.com/bitbank2/JPEGDEC.git#86282979224c8a32fd51e091ed5a35b0c699a52b
-  FreeInkUI=symlink://freeink-sdk/libs/ui/FreeInkUI
-  Icons=symlink://freeink-sdk/libs/assets/Icons
-lib_ignore =
-  hal
-  WebSockets
-  BoardConfig
-  EInkDisplay
-  BatteryMonitor
-  InputManager
-  SDCardManager
-  UsbMassStorage
-  XteinkDetect
-  PowerManager
-  FrontlightManager
-  Rtc
-  Imu
-  SecureNet
-build_src_filter =
-  +<*>
-  -<network/FirmwareFlasher.cpp>
-  -<network/OtaBootSwitch.cpp>
-  -<network/OtaUpdater.cpp>
-  -<platform/skip_efuse_blk_check.c>
-build_flags =
-  -std=gnu++2a
-  -funsigned-char
-  -I src
-  -include sim-compat.h
-  -DCROSSPOINT_VERSION=\"sim-local\"
-  -DEINK_DISPLAY_SINGLE_BUFFER_MODE=1
-  -DDISABLE_FS_H_WARNING=1
-  -DXML_GE=0
-  -DXML_CONTEXT_BYTES=1024
-  -DPNG_MAX_BUFFERED_PIXELS=16416
-  -DUSE_UTF8_LONG_NAMES=1
-  !sdl2-config --cflags --libs
-  -lcrypto
-```
-
-Plus the local `qrcode.h` C23 patch (§2) and `sim-compat.h` (§4).
-
-## Commands
-
-```bash
-git clone --depth 1 --recurse-submodules --shallow-submodules \
-  https://github.com/crosspoint-reader/crosspoint-reader
-git clone --depth 1 https://github.com/crosspoint-reader/crosspoint-simulator
-cd crosspoint-reader
-
-nix-shell -p SDL2 SDL2.dev pkg-config openssl openssl.dev curl gcc gnumake python3 \
-  --run 'export PLATFORMIO_CORE_DIR="$PWD/.cache/platformio"; pio run -e simulator'
-# => [SUCCESS] Took 51.03 seconds
-
-mkdir -p fs_/fonts fs_/books           # the simulator's virtual SD card
-SDL_VIDEODRIVER=dummy ./.pio/build/simulator/program
-```
-
-All `executed-success`. The clone is ~533 MB with the submodule.
-
-## What running it establishes
-
-Modest but real, and previously unavailable:
-
-- **The firmware builds and executes without an e-reader.** Every prior claim in
-  this knowledge base about CrossPoint's runtime behaviour was `inferred` from
-  source; this is the first observation.
-- **It mounts a virtual SD card at `./fs_/`.** Before that directory exists it
-  reports `[SIM] open failed: ./fs_/.fonts` and `./fs_/fonts`; afterwards it runs
-  silently. So the SD layout is inspectable and modifiable on a desktop, which is
-  the practical route to understanding the on-card format.
-- **It runs headless** under `SDL_VIDEODRIVER=dummy` — so it is usable in CI or
-  a container, not only on a desktop with a display.
-
-## Limits — what this does *not* establish
-
-- **No frame was captured.** Under the dummy video driver nothing renders to a
-  file, and no screenshot mechanism was found. Display output is unverified.
-- **Nothing about the PaperMono.** This build targets the simulator's own board
-  stubs. Whether the simulator can model the
-  [PaperMono](../../devices/m5stack/papermono/README.md)'s M5IOE1 expander and
-  M5PM1 power manager is **still unknown** — the original open question stands.
-- **No book was loaded**, no UI interaction driven, no reading path exercised.
-- The build required a **local patch to a vendored library** and a compat header;
-  it is not a clean upstream configuration.
-
-## Suggested upstream contributions
-
-Three of these are general, not NixOS-specific, and would help anyone on a
-current toolchain:
-
-1. The **C23/`bool`** breakage in QRCode (§2) — affects every GCC ≥ 14 host.
-2. The **`#include_next` ordering** assumption in the native-decoder shims (§5).
-3. The sample config's **missing defines and `-lcrypto`** (§6, §7).
-
-None has been reported upstream from here.
diff --git a/software/tooling/sim-compat.h b/software/tooling/sim-compat.h
deleted file mode 100644
index 722c02d..0000000
--- a/software/tooling/sim-compat.h
+++ /dev/null
@@ -1,12 +0,0 @@
-/* Local build-experiment shim: AVR/ESP pgmspace API on a native host.
-   NOT upstream. Provides the handful of symbols PNGdec/JPEGDEC expect. */
-#pragma once
-#include <string.h>
-#include <stdint.h>
-#ifndef PROGMEM
-#define PROGMEM
-#endif
-static inline void *memcpy_P(void *d, const void *s, size_t n) { return memcpy(d, s, n); }
-#ifndef pgm_read_byte
-static inline uint8_t pgm_read_byte(const void *p) { return *(const uint8_t *)p; }
-#endif
diff --git a/tools/altium_pdf_netlist.py b/tools/altium_pdf_netlist.py
deleted file mode 100644
index fe5b769..0000000
--- a/tools/altium_pdf_netlist.py
+++ /dev/null
@@ -1,83 +0,0 @@
-"""Parse pdftotext -bbox XML into word records, classifying Altium PDF markers.
-
-Altium Designer's PDF publisher emits invisible marker text at schematic objects:
-  CO<designator>            component outline
-  PI<designator><pin>       pin instance
-  NL<netname>               net label
-Non-alphanumerics in names are replaced by '0' in the marker, so the marker is
-lossy (G0_BOOT_OUT -> NLG00BOOT0OUT). Markers therefore locate objects; the
-human-readable text next to them supplies the real name.
-"""
-import re, sys, math, json, html
-
-WORD = re.compile(r'<word xMin="([\d.\-]+)" yMin="([\d.\-]+)" xMax="([\d.\-]+)" yMax="([\d.\-]+)">(.*?)</word>')
-
-def load(path):
-    out = []
-    for m in WORD.finditer(open(path, encoding='utf-8', errors='replace').read()):
-        x0, y0, x1, y1 = (float(m.group(i)) for i in range(1, 5))
-        t = html.unescape(m.group(5))
-        out.append({'x': (x0+x1)/2, 'y': (y0+y1)/2, 'x0': x0, 'y0': y0, 'x1': x1, 'y1': y1, 't': t})
-    return out
-
-MARKER = re.compile(r'(?<![A-Za-z])(CO|PI|NL)([A-Z0-9]+)')
-
-def split_markers(words):
-    """A single extracted 'word' may glue a marker to real text (e.g. '15PIU7015').
-
-    The negative lookbehind matters: without it 'GPIO0' parses as G + PI-marker
-    'O0' and 'SPI2_MOSI' as S + PI-marker '2', which silently eats pin names on
-    every MCU sheet. Altium emits each marker as its own text object, so a real
-    marker is never preceded by a letter.
-    """
-    plain, co, pi, nl = [], [], [], []
-    for w in words:
-        t = w['t']
-        for mm in MARKER.finditer(t):
-            kind, body = mm.group(1), mm.group(2)
-            rec = dict(w); rec['body'] = body
-            (co if kind == 'CO' else pi if kind == 'PI' else nl).append(rec)
-        rest = MARKER.sub(' ', t).strip()
-        if rest:
-            rec = dict(w); rec['t'] = rest
-            plain.append(rec)
-    return plain, co, pi, nl
-
-def designators(co):
-    """Reference designators, from CO markers. CO markers may themselves be glued
-    to a following PI marker, so take the leading letters+digits only."""
-    d = set()
-    for c in co:
-        m = re.match(r'([A-Z]+[0-9]+)', c['body'])
-        if m:
-            d.add(m.group(1))
-    return d
-
-def split_pin(body, desigs):
-    """PIU7015 is ambiguous: U7/pin015 or U70/pin15. Resolve with the known
-    designator set, longest match first; report unresolved rather than guessing."""
-    cands = [d for d in desigs if body.startswith(d) and body[len(d):].isdigit()]
-    if not cands:
-        return None, None
-    best = max(cands, key=len)
-    return best, body[len(best):].lstrip('0') or '0'
-
-def near(w, pool, r):
-    out = []
-    for p in pool:
-        d = math.hypot(p['x'] - w['x'], p['y'] - w['y'])
-        if d <= r:
-            out.append((d, p))
-    out.sort(key=lambda z: z[0])
-    return out
-
-if __name__ == '__main__':
-    allw = {}
-    for p in range(1, 7):
-        allw[p] = load(f'pdf/bbox-p{p}.xml')
-    grand = set()
-    for p, ws in allw.items():
-        plain, co, pi, nl = split_markers(ws)
-        grand |= designators(co)
-    print("total distinct designators:", len(grand))
-    print(json.dumps(sorted(grand), indent=0)[:4000])
diff --git a/tools/altium_pdf_pin_table.py b/tools/altium_pdf_pin_table.py
deleted file mode 100644
index 7a74653..0000000
--- a/tools/altium_pdf_pin_table.py
+++ /dev/null
@@ -1,45 +0,0 @@
-"""Recover a per-component pin table from an Altium schematic PDF.
-
-For each PI<desig><pin> marker, collect the human-readable words sharing its
-row band, split into what lies inside the symbol body (pin name) and what lies
-outside it (the attached net label). The symbol's horizontal extent is estimated
-from the spread of its own pin markers.
-
-This is a reading aid, not an authority: it recovers text adjacency, not
-electrical connectivity, so unlabelled wire-only connections are invisible to it
-and every row must be checked against the rendered sheet before being asserted.
-"""
-import sys, re
-sys.path.insert(0, 'tools')
-from altium_pdf_netlist import load, split_markers, designators, split_pin
-
-page, target = int(sys.argv[1]), sys.argv[2]
-band = float(sys.argv[3]) if len(sys.argv) > 3 else 3.5
-
-desig = set()
-for p in range(1, 7):
-    _, c2, _, _ = split_markers(load(f'pdf/bbox-p{p}.xml'))
-    desig |= designators(c2)
-
-ws = load(f'pdf/bbox-p{page}.xml')
-plain, co, pi, nl = split_markers(ws)
-
-mine = []
-for m in pi:
-    d, pin = split_pin(m['body'], desig)
-    if d == target:
-        mine.append((pin, m))
-if not mine:
-    print(f"no pin markers for {target} on page {page}"); sys.exit(0)
-
-xs = [m['x'] for _, m in mine]
-lo, hi = min(xs), max(xs)
-print(f"# {target} on sheet {page}: {len(mine)} pin markers, x span {lo:.0f}..{hi:.0f}")
-print(f"{'pin':>5} | {'x':>6} | inside symbol (pin name)            | outside (net / value)")
-print("-" * 110)
-for pin, m in sorted(mine, key=lambda z: (int(z[0]) if z[0].isdigit() else 999, z[1]['y'])):
-    row = [w for w in plain if abs(w['y'] - m['y']) <= band]
-    row.sort(key=lambda w: abs(w['x'] - m['x']))
-    inside = [w['t'] for w in row if lo - 2 <= w['x'] <= hi + 2][:4]
-    outside = [w['t'] for w in row if not (lo - 2 <= w['x'] <= hi + 2)][:5]
-    print(f"{pin:>5} | {m['x']:6.1f} | {' '.join(inside)[:35]:35s} | {' '.join(outside)[:45]}")
diff --git a/tools/altium_pdf_render_sheet.py b/tools/altium_pdf_render_sheet.py
deleted file mode 100644
index 9b88260..0000000
--- a/tools/altium_pdf_render_sheet.py
+++ /dev/null
@@ -1,37 +0,0 @@
-"""Render an Altium schematic PDF page as ordered text rows, markers stripped.
-
-Markers (CO/PI/NL) are dropped from the visible rendering but their designator
-and pin information is re-attached inline as [D.pin] so a reader can see which
-component a pin number belongs to without opening the PDF.
-"""
-import sys, re
-sys.path.insert(0, 'tools')
-from altium_pdf_netlist import load, split_markers, designators, split_pin
-
-page = int(sys.argv[1]); tol = float(sys.argv[2]) if len(sys.argv) > 2 else 3.0
-ws = load(f'pdf/bbox-p{page}.xml')
-plain, co, pi, nl = split_markers(ws)
-# designator set from *all* pages, since a sheet may reference parts drawn elsewhere
-desig = set()
-for p in range(1, 7):
-    _, c2, _, _ = split_markers(load(f'pdf/bbox-p{p}.xml'))
-    desig |= designators(c2)
-
-items = [(w['y'], w['x'], w['t']) for w in plain]
-for m in pi:
-    d, pin = split_pin(m['body'], desig)
-    items.append((m['y'], m['x'], f"[{d}.{pin}]" if d else f"[?{m['body']}]"))
-for m in co:
-    mm = re.match(r'([A-Z]+[0-9]+)', m['body'])
-    if mm:
-        items.append((m['y'], m['x'], f"<{mm.group(1)}>"))
-items.sort()
-rows, cur, cy = [], [], None
-for y, x, t in items:
-    if cy is None or abs(y - cy) <= tol:
-        cur.append((x, t)); cy = y if cy is None else cy
-    else:
-        rows.append((cy, sorted(cur))); cur = [(x, t)]; cy = y
-if cur: rows.append((cy, sorted(cur)))
-for y, r in rows:
-    print(f"{y:6.1f} | " + '  '.join(t for _, t in r))
diff --git a/tools/archive_artifact.py b/tools/archive_artifact.py
index 544c85e..cc72e1c 100644
--- a/tools/archive_artifact.py
+++ b/tools/archive_artifact.py
@@ -2,8 +2,7 @@
 """Relocate bulky/duplicate artifacts out of the repository without losing them.
 
 Policy (per user instruction, 2026-08-24): never delete a downloaded artifact.
-Move it into the archive (resolved from the git common dir, namespaced by repo)
-preserving its relative path, and leave a
+Move it to ../hardware-doc-archive/ preserving its relative path, and leave a
 Markdown placeholder in its place carrying everything needed to get the exact
 bytes back: size, SHA-256, mtime, upstream repo + commit + author, and several
 independent recovery URLs.
@@ -21,33 +20,7 @@
 
 import argparse, hashlib, json, os, re, shutil, subprocess, datetime, sys
 
-def _repo_root():
-    """Real repository root, worktree-safe (--git-common-dir, not --show-toplevel)."""
-    out = subprocess.run(
-        ["git", "rev-parse", "--path-format=absolute", "--git-common-dir"],
-        capture_output=True, text=True)
-    if out.returncode != 0:
-        raise SystemExit("not inside a git repository")
-    return os.path.dirname(out.stdout.strip())
-
-
-# Resolve the archive rather than hardcoding it. Layout:
-#
-#   <repo-parent>/
-#   |- <repo>/                     this repository
-#   \- repo-archive/       shared archive
-#      |- <repo>/                  <- our namespace, mirrors in-repo paths
-#      \- scratch/<repo>/          <- working files
-#
-# Namespacing by source repository means a second repo's material sits beside ours
-# instead of colliding. Overridable for testing.
-REPO_ROOT = _repo_root()
-NAMESPACE = os.path.basename(REPO_ROOT)
-ARCHIVE_ROOT = os.environ.get(
-    "REPO_ARCHIVE_ROOT",
-    os.path.join(os.path.dirname(REPO_ROOT), "repo-archive"))
-ARCHIVE = os.path.join(ARCHIVE_ROOT, NAMESPACE)
-SCRATCH = os.path.join(ARCHIVE_ROOT, "scratch", NAMESPACE)
+ARCHIVE = os.path.expanduser("../hardware-doc-archive")
 
 
 def sha256(p):
@@ -193,56 +166,10 @@ def urls(src, rel, is_dir=False):
         )
     if src.get("url"):
         out.append(("original download URL", src["url"]))
-    # First-class multi-URL list. Not everything archived is a git repo - vendor
-    # datasheets, forum attachments and archive.org captures have no commit to
-    # derive a URL from, so they must be listed explicitly. Each entry is either a
-    # bare string or {"url": ..., "desc": ...}.
-    for key in ("urls", "extra_urls"):
-        for u in src.get(key) or []:
-            if isinstance(u, dict):
-                out.append((u.get("desc") or "additional source", u["url"]))
-            else:
-                out.append(("additional source", u))
-    # De-duplicate while preserving order; the same link often arrives from two
-    # places (derived from repo+commit, and listed by hand).
-    seen, uniq = set(), []
-    for desc, link in out:
-        if link not in seen:
-            seen.add(link)
-            uniq.append((desc, link))
-    return uniq
-
-
-# Git reads these as configuration rather than content. A symlinked .gitignore makes
-# git print "Too many levels of symbolic links" on every command, and would let a
-# vendored upstream's ignore rules bleed into this repo.
-NO_LINK_NAMES = {".gitignore", ".gitattributes", ".gitmodules"}
-
-
-def stand_in(rel, full):
-    """Symlink `rel` to its archive copy, plus a matching *.ARCHIVED.link.
-
-    The target is relative and routes through this repo's own `archive/` symlink -
-    `../../../archive/devices/foo/bar` - never at the archive root directly. That
-    leaves one indirection point: relocating the archive means editing a single
-    symlink rather than every artifact link in the tree.
-    """
-    if os.path.basename(rel) in NO_LINK_NAMES:
-        return
-    depth = len(os.path.dirname(rel).split(os.sep)) if os.path.dirname(rel) else 0
-    target = os.path.join(*([".."] * depth), "archive", rel) if depth else os.path.join("archive", rel)
-    try:
-        if os.path.lexists(full):
-            if not os.path.islink(full):
-                return          # something real is there; do not clobber it
-            os.unlink(full)
-        os.symlink(target, full)
-        link = full + ".ARCHIVED.link"
-        if os.path.lexists(link):
-            os.unlink(link)
-        os.symlink(os.path.basename(full), link)
-    except OSError as e:
-        print(f"  !! could not create stand-in symlink for {rel}: {e}")
+    if src.get("extra_urls"):
+        for u in src["extra_urls"]:
+            out.append(("additional mirror", u))
+    return out
 
 
 def placeholder(rel, dest, meta, src, is_dir, files=None, collision_note=None):
@@ -275,26 +202,16 @@ def placeholder(rel, dest, meta, src, is_dir, files=None, collision_note=None):
     else:
         lines.append(f"| File count | {meta.get('nfiles', '?')} |")
     lines.append(f"| Last modified (mtime) | {meta['mtime']} |")
-    # Git-sourced material is only half of what gets archived. Vendor PDFs have a
-    # version and a publication date but no commit or author, and are usually the
-    # hard ones to re-obtain - so difficulty and access notes matter more for them
-    # than a hash does. Render whatever the manifest supplies; omit the rest.
     for k, label in (
         ("repo", "Upstream repository"),
         ("commit", "Commit"),
-        ("tag", "Tag / release"),
-        ("version", "Document version"),
         ("author", "Author / committer"),
         ("committed", "Commit date"),
-        ("published", "Published / revised"),
-        ("retrieved", "Retrieved"),
         ("license", "License"),
         ("path_in_repo", "Path within upstream repo"),
-        ("difficulty", "Difficulty to re-obtain"),
-        ("access_notes", "Access notes"),
     ):
         if src.get(k):
-            v = f"`{src[k]}`" if k in ("commit", "path_in_repo", "tag", "version") else src[k]
+            v = f"`{src[k]}`" if k in ("commit", "path_in_repo") else src[k]
             lines.append(f"| {label} | {v} |")
     lines.append("")
     if meta.get("notes"):
@@ -316,56 +233,6 @@ def placeholder(rel, dest, meta, src, is_dir, files=None, collision_note=None):
         for f, b, s in files:
             lines.append(f"| `{f}` | {b:,} | `{s}` |")
         lines.append("")
-    # A patch-over-upstream artifact is meaningless without its base. State the
-    # relationship on EVERY placeholder derived from it, not once in a README:
-    # placeholders are read one at a time, usually by someone who found only this file.
-    base = src.get("base")
-    if base:
-        lines.append("## Derived from a common base")
-        lines.append("")
-        lines.append(
-            "This artifact is **not standalone** - it is a modification of the source below. "
-            "Re-acquiring it means obtaining that base and re-applying the changes."
-        )
-        lines.append("")
-        lines.append("| Field | Value |")
-        lines.append("| --- | --- |")
-        # `repo` accepts a string or a list. Upstreams move, get forked, or are
-        # mirrored - a vendor repo that also lives on GitLab, or a project whose
-        # canonical home changed owner - and one dead URL should not strand the base.
-        repos = base.get("repo") or []
-        if isinstance(repos, str):
-            repos = [repos]
-        for i, r in enumerate(repos):
-            label = "Base repository" if i == 0 else "Mirror / fork"
-            url = r if r.startswith("http") else f"https://github.com/{r}"
-            lines.append(f"| {label} | [`{r}`]({url}) |")
-        if len(repos) > 1:
-            lines.append(f"| Repository count | {len(repos)} known locations |")
-        for k, label in (("commit", "Base commit"),
-                         ("tag", "Base tag / release"), ("url", "Base URL"),
-                         ("note", "Relationship")):
-            if base.get(k):
-                v = f"`{base[k]}`" if k in ("commit", "tag") else base[k]
-                lines.append(f"| {label} | {v} |")
-        lines.append("")
-        if base.get("patches"):
-            lines.append("Patches applied over that base, in order:")
-            lines.append("")
-            for i, pt in enumerate(base["patches"], 1):
-                if isinstance(pt, dict):
-                    lines.append(f"{i}. {pt.get('desc', '(undescribed)')}"
-                                 + (f" - `{pt['path']}`" if pt.get("path") else ""))
-                else:
-                    lines.append(f"{i}. {pt}")
-            lines.append("")
-        if base.get("siblings"):
-            lines.append("Other archived artifacts sharing this base:")
-            lines.append("")
-            for sib in base["siblings"]:
-                lines.append(f"- `{sib}`")
-            lines.append("")
-
     lines.append("## How to get it back")
     lines.append("")
     u = urls(src, rel, is_dir)
@@ -375,22 +242,6 @@ def placeholder(rel, dest, meta, src, is_dir, files=None, collision_note=None):
         for desc, link in u:
             lines.append(f"- {desc}:  \n  <{link}>")
         lines.append("")
-    # Two independent URLs is the target: one host disappearing should not strand
-    # the artifact. Sometimes only one exists, or none - say so explicitly rather
-    # than leaving a silent gap that reads like an oversight.
-    if len(u) < 2:
-        lines.append(
-            f"> **Only {len(u) or 'no'} recovery URL{'' if len(u) == 1 else 's'} "
-            "recorded.** Two or more independent sources are the target. If you find "
-            "another - a mirror, a vendor page, an archive.org capture - add it here."
-        )
-        lines.append("")
-    # Bulk archiving cannot always establish per-file provenance. That is acceptable
-    # only if the detail lives somewhere findable, and the placeholder names it.
-    if src.get("documented_in"):
-        lines.append(f"Fuller sourcing for this artifact is recorded in "
-                     f"`{src['documented_in']}`.")
-        lines.append("")
     lines.append("Restore from the local archive:")
     lines.append("")
     lines.append("```bash")
@@ -469,7 +320,6 @@ def main():
     total = 0
     verified = 0
     failures = []
-    thin_urls = []
 
     if a.verify:
         return verify_mode(a.repo_root, items)
@@ -483,8 +333,8 @@ def main():
         b = du(full)
         meta = {
             "bytes": b,
-            "mtime": datetime.datetime.fromtimestamp(
-                os.path.getmtime(full), datetime.timezone.utc
+            "mtime": datetime.datetime.utcfromtimestamp(
+                os.path.getmtime(full)
             ).strftime("%Y-%m-%d %H:%M:%SZ"),
             "reason": it.get("reason"),
         }
@@ -576,29 +426,6 @@ def main():
         with open(ph, "w") as f:
             f.write(placeholder(rel, dest, meta, it.get("source", {}), is_dir,
                                 files, collision_note))
-
-        # Leave a symlink standing in for the artifact at its original path, so a
-        # checkout holding the archive behaves as though nothing moved: relative
-        # references from KiCad projects and build scripts keep resolving, and the
-        # directory still shows that the file exists. Without this, an archived file
-        # vanishes from the tree and is discoverable only via the placeholder.
-        stand_in(rel, full)
-
-        # Two independent sources is the bar: one host going away should not strand
-        # the artifact. Warn loudly at archive time, when the person still has the
-        # context to fix it - not months later when the link has rotted.
-        nurl = len(urls(it.get("source", {}), rel, is_dir))
-        if nurl < 2:
-            thin_urls.append((rel, nurl))
-            print(f"  !! only {nurl} recovery URL(s) for {rel}\n"
-                  f"       add more to the manifest's source.urls[], or record in the "
-                  f"directory's ARCHIVED-*.md why no second source exists")
-    if thin_urls:
-        print(f"\n!! {len(thin_urls)} artifact(s) archived with fewer than two recovery URLs:")
-        for r, n in thin_urls:
-            print(f"     [{n}] {r}")
-        print("   These are the ones that go missing. Add sources before they rot.")
-
     print(f"\nTOTAL {'would be ' if a.dry_run else ''}archived: {size_str(total)}")
     if not a.dry_run:
         print(f"Verified after move: {verified}/{verified + len(failures)}")
diff --git a/tools/audit_archive.py b/tools/audit_archive.py
deleted file mode 100755
index 4c44103..0000000
--- a/tools/audit_archive.py
+++ /dev/null
@@ -1,230 +0,0 @@
-#!/usr/bin/env python3
-"""Audit archive/repo consistency.
-
-Every artifact moved into the archive is supposed to leave something behind at its
-original path: a symlink standing in for it, a `*.ARCHIVED.md` placeholder, or - for
-material archived as a set - an `ARCHIVED-<TOPIC>.md` record in the containing
-directory. Prose in a README or acquisition manifest also counts, provided it names
-the artifact.
-
-This finds the cases where nothing was left behind at all, which is the failure that
-loses things: a reader browsing the directory has no way to know the file existed.
-
-    python3 tools/audit_archive.py            # summary
-    python3 tools/audit_archive.py --verbose  # every unrepresented entry
-"""
-import os
-import re
-import subprocess
-import sys
-from collections import Counter
-
-REPO = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
-ARCHIVE = os.path.join(REPO, "archive")
-
-# Deliberately never linked - see tools/link_archived.py. Git reads these as
-# configuration, so symlinking them produces ELOOP warnings on every command.
-SKIP_NAMES = {".gitignore", ".gitattributes", ".gitmodules"}
-
-# Registrable-domain suffixes needing three labels, so vendor.co.uk is not read as
-# the party "co.uk". Not exhaustive; it only has to cover what this repo cites.
-MULTI_TLD = {"co.uk", "com.cn", "co.jp", "org.uk", "com.au", "co.nz", "com.br"}
-
-
-def mentioned_in_prose(rel):
-    """True if some committed markdown names this artifact.
-
-    Cheap and deliberately loose: we are asking 'could a reader find out this
-    existed', not 'is it documented to standard'. Basename is enough - the point is
-    to avoid flagging things that are in fact written up in an acquisition manifest
-    or a snapshot index under a slightly different path.
-    """
-    base = os.path.basename(rel.rstrip("/"))
-    if not base:
-        return False
-    try:
-        r = subprocess.run(
-            ["git", "grep", "-l", "-F", base, "--", "*.md"],
-            cwd=REPO, capture_output=True, text=True, timeout=30,
-        )
-        return bool(r.stdout.strip())
-    except (subprocess.SubprocessError, OSError):
-        return False
-
-
-def represented(rel):
-    p = os.path.join(REPO, rel)
-    if os.path.islink(p):
-        return "symlink"
-    if os.path.exists(p + ".ARCHIVED.md"):
-        return "placeholder"
-    d = os.path.dirname(p) or REPO
-    try:
-        if any(f.startswith("ARCHIVED-") and f.endswith(".md") for f in os.listdir(d)):
-            return "set record"
-    except OSError:
-        pass
-    return None
-
-
-def walk(d, gaps, covered):
-    rel = os.path.relpath(d, ARCHIVE)
-    rel = "" if rel == "." else rel
-    if rel:
-        r = represented(rel)
-        if r:                       # whole subtree accounted for
-            covered.append((rel, r))
-            return
-    try:
-        entries = sorted(os.listdir(d))
-    except OSError:
-        return
-    for e in entries:
-        full = os.path.join(d, e)
-        er = os.path.join(rel, e) if rel else e
-        if os.path.isdir(full) and not os.path.islink(full):
-            r = represented(er)
-            if r:
-                covered.append((er, r))
-            else:
-                walk(full, gaps, covered)
-        elif e not in SKIP_NAMES:
-            r = represented(er)
-            if r:
-                covered.append((er, r))
-            else:
-                gaps.append(er)
-
-
-def check_records():
-    """Placeholders and set records that fall short of two independent sources.
-
-    Distinct hosts matter more than raw URL count: five links to one vendor CDN are
-    one outage from useless. Reported separately so the weaker case is visible.
-    """
-    thin_urls, thin_hosts, no_repo, gh_only, total = [], [], [], [], 0
-    for dp, dns, fns in os.walk(REPO):
-        dns[:] = [d for d in dns if d not in (".git", "archive", "scratch")]
-        for f in fns:
-            if not (f.endswith(".ARCHIVED.md")
-                    or (f.startswith("ARCHIVED-") and f.endswith(".md"))):
-                continue
-            p = os.path.join(dp, f)
-            if os.path.islink(p):
-                continue
-            try:
-                t = open(p, encoding="utf-8", errors="replace").read()
-            except OSError:
-                continue
-            total += 1
-            u = set(re.findall(r'https?://[^\s<>)\]"]+', t))
-            rel = os.path.relpath(p, REPO)
-
-            # Count distinct PARTIES, not URLs or hostnames. github.com/X/Y and
-            # raw.githubusercontent.com/X/Y are one source, not two; so are
-            # squareline.io and static.squareline.io. Counting URLs flatters a record
-            # that cites the same place five ways, which is exactly the record most
-            # likely to go missing.
-            parties = set()
-            for pat in (r'github\.com/([\w.-]+/[\w.-]+?)(?:\.git)?(?=[/)\s`">]|$)',
-                        r'raw\.githubusercontent\.com/([\w.-]+/[\w.-]+?)(?=/)',
-                        r'api\.github\.com/repos/([\w.-]+/[\w.-]+?)(?=[/)\s`">]|$)'):
-                for m in re.findall(pat, t + " "):
-                    if m.split("/")[0] not in ("orgs", "features", "about", "sponsors",
-                                               "topics", "repos", "search"):
-                        parties.add(("gh", m.lower()))
-            for x in u:
-                host = re.sub(r'^https?://([^/]+).*', r'\1', x).lower()
-                if "github" in host:
-                    continue
-                bits = host.split(".")
-                dom = (".".join(bits[-3:])
-                       if len(bits) > 2 and ".".join(bits[-2:]) in MULTI_TLD
-                       else ".".join(bits[-2:]))
-                parties.add(("web", dom))
-
-            if len(u) < 2:
-                thin_urls.append((len(u), rel))
-            elif len(parties) < 2:
-                thin_hosts.append((len(parties), rel))
-            # A record sourced only from GitHub depends on one company's availability
-            # decision, and one sourced with no repository at all usually means the
-            # upstream was never looked for. Both are worth surfacing; neither is fatal,
-            # and for genuinely closed-source artifacts "no repository" is the right answer.
-            if not {d for kind, d in parties if kind == "gh"}:
-                no_repo.append(rel)
-            if not {d for kind, d in parties if kind == "web"}:
-                gh_only.append(rel)
-    return total, thin_urls, thin_hosts, no_repo, gh_only
-
-
-def main():
-    verbose = "--verbose" in sys.argv
-    if not os.path.isdir(ARCHIVE):
-        print("no archive/ present - run scripts/init.sh; nothing to audit")
-        return 0
-    gaps, covered = [], []
-    walk(ARCHIVE, gaps, covered)
-
-    prose = [g for g in gaps if mentioned_in_prose(g)]
-    silent = [g for g in gaps if g not in set(prose)]
-
-    def mb(paths):
-        t = 0
-        for g in paths:
-            p = os.path.join(ARCHIVE, g)
-            try:
-                t += os.path.getsize(p)
-            except OSError:
-                pass
-        return t / 1e6
-
-    print(f"represented at their original path : {len(covered)}")
-    for k, n in Counter(k for _, k in covered).most_common():
-        print(f"  {k:<14} {n}")
-    print()
-    print(f"no marker at the original path     : {len(gaps)}  ({mb(gaps):.0f} MB)")
-    print(f"  named in prose somewhere          : {len(prose)}  "
-          f"- findable, but add a symlink/placeholder")
-    print(f"  NOT MENTIONED ANYWHERE            : {len(silent)}  ({mb(silent):.0f} MB)"
-          f"  <-- these are losable")
-    if silent:
-        print()
-        print("Unmentioned, collapsed by directory:")
-        c = Counter(os.sep.join(g.split(os.sep)[:6]) for g in silent)
-        for d, n in c.most_common(20 if not verbose else 10**6):
-            print(f"  {n:5d}  {d}")
-    if verbose and prose:
-        print()
-        print("Named in prose but lacking a path-level marker:")
-        for g in prose:
-            print(f"  {g}")
-    total, thin_urls, thin_hosts, no_repo, gh_only = check_records()
-    print()
-    print(f"placeholders / set records         : {total}")
-    print(f"  fewer than 2 URLs                 : {len(thin_urls)}")
-    print(f"  2+ URLs but a single party        : {len(thin_hosts)}")
-    for n, r in thin_urls:
-        print(f"    [{n} url] {r}")
-    for n, r in thin_hosts:
-        print(f"    [1 party] {r}")
-    print(f"  no git repository cited           : {len(no_repo)}")
-    for r in no_repo:
-        print(f"    [no repo] {r}")
-    print(f"  sourced only from GitHub          : {len(gh_only)}")
-    for r in gh_only:
-        print(f"    [gh only] {r}")
-    if thin_urls or thin_hosts or no_repo or gh_only:
-        print()
-        print("  Two independent sources is the rule where it is possible, and a second")
-        print("  custodian beats a second path under the same one. Where a repository or")
-        print("  a non-GitHub source genuinely does not exist - proprietary tools, vendor")
-        print("  ZIPs with no upstream - say so in the record. An absent line should read")
-        print("  as checked and absent, not as an omission waiting to be 'fixed' with a")
-        print("  plausible-looking link.")
-
-    return 1 if silent else 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())
diff --git a/tools/dedupe_shared_assets.py b/tools/dedupe_shared_assets.py
index 3efd47c..68dc6d2 100644
--- a/tools/dedupe_shared_assets.py
+++ b/tools/dedupe_shared_assets.py
@@ -183,7 +183,7 @@ def write_manifest(entries: list[dict]) -> None:
 ```
 
 Or re-fetch from the pool's archive copy:
-`../repo-archive/doc/hardware/shared-assets/`
+`../hardware-doc-archive/doc/hardware/shared-assets/`
 
 The full set of sharing relationships, including every location that links to each
 entry, is in [`shared-assets/manifest.json`]({pool_rel}/manifest.json).
diff --git a/tools/link_archived.py b/tools/link_archived.py
deleted file mode 100755
index cf2b1ca..0000000
--- a/tools/link_archived.py
+++ /dev/null
@@ -1,103 +0,0 @@
-#!/usr/bin/env python3
-"""Place symlinks at the original paths of archived artifacts.
-
-Driven by the archive itself rather than by placeholder files, so material that was
-moved out without leaving a placeholder still gets a marker at its original path.
-
-Links are made at the SHALLOWEST path the repo is missing: an archived 1,654-file
-tree becomes one symlink to the directory, not 1,654 links to its contents. Where the
-repo still has a real directory, we descend into it, since only part of it was moved.
-
-Targets are relative and route through this repo's own `archive/` symlink, e.g.
-`../../../archive/devices/foo/bar`, never at ../repo-archive directly - so relocating
-the archive means editing one symlink instead of every link in the tree.
-
-    python3 tools/link_archived.py            # dry run
-    python3 tools/link_archived.py --apply
-    python3 tools/link_archived.py --apply --remove
-"""
-import os
-import sys
-
-REPO = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
-ARCHIVE = os.path.join(REPO, "archive")
-
-# Never symlink git's own control files. Git reads .gitignore/.gitattributes as
-# configuration rather than content: pointing them through the archive symlink makes
-# it emit "Too many levels of symbolic links" on every command, and in principle lets
-# a vendored upstream's ignore rules bleed into this repo.
-#
-# They are a few hundred bytes each, so where one would otherwise be the only thing
-# missing from a tree, commit the real file instead of linking it. That keeps "every
-# archived path resolves" true without handing git a symlinked config to interpret.
-SKIP_NAMES = {".gitignore", ".gitattributes", ".gitmodules"}
-
-
-def targets():
-    """Shallowest archive paths with no corresponding entry in the repo."""
-    out = []
-
-    def walk(d):
-        rel = os.path.relpath(d, ARCHIVE)
-        rel = "" if rel == "." else rel
-        try:
-            entries = sorted(os.listdir(d))
-        except OSError:
-            return
-        for e in entries:
-            full = os.path.join(d, e)
-            er = os.path.join(rel, e) if rel else e
-            rp = os.path.join(REPO, er)
-            if os.path.islink(rp):
-                continue                       # already stood in for
-            if os.path.isdir(full) and not os.path.islink(full):
-                if os.path.isdir(rp):
-                    walk(full)                 # partially archived - go deeper
-                else:
-                    out.append(er)             # whole tree absent - one link
-            elif not os.path.exists(rp) and e not in SKIP_NAMES:
-                out.append(er)
-    walk(ARCHIVE)
-    return out
-
-
-def main():
-    apply_ = "--apply" in sys.argv
-    remove = "--remove" in sys.argv
-    if not os.path.isdir(ARCHIVE):
-        print("no archive/ present - run scripts/init.sh first")
-        return 0
-
-    if remove:
-        n = 0
-        for dp, dns, fns in os.walk(REPO):
-            if ".git" in dp or dp.startswith(os.path.join(REPO, "archive")):
-                continue
-            for f in list(dns) + fns:
-                p = os.path.join(dp, f)
-                if os.path.islink(p) and "/archive/" in os.readlink(p):
-                    if apply_:
-                        os.unlink(p)
-                    n += 1
-        print(f"{'removed' if apply_ else 'would remove'} {n} archive symlink(s)")
-        return 0
-
-    made = 0
-    for rel in targets():
-        link = os.path.join(REPO, rel)
-        depth = len(os.path.dirname(rel).split(os.sep)) if os.path.dirname(rel) else 0
-        target = os.path.join(*([".."] * depth), "archive", rel) if depth else os.path.join("archive", rel)
-        if apply_:
-            os.makedirs(os.path.dirname(link), exist_ok=True)
-            if os.path.islink(link):
-                os.unlink(link)
-            os.symlink(target, link)
-        made += 1
-    print(f"{'linked' if apply_ else 'would link'} {made} archived path(s)")
-    if not apply_:
-        print("re-run with --apply to create them")
-    return 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())
diff --git a/vendors/README.md b/vendors/README.md
index 04a4268..2977afc 100644
--- a/vendors/README.md
+++ b/vendors/README.md
@@ -17,10 +17,7 @@ For **board vendors and marketplaces** — where to *buy* rather than where to *
 | Waveshare Electronics | [waveshare/](waveshare/README.md) | [ESP32-S3-Knob-Touch-LCD-1.8](../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md) |
 | **Soldered Electronics** (ex-*e-radionica*) | [soldered-electronics/](soldered-electronics/README.md) | [Inkplate 5](../devices/soldered-electronics/inkplate-5/README.md) · [Inkplate 5 Gen 2](../devices/soldered-electronics/inkplate-5-gen2/README.md) |
 | **Zerowriter** | [zerowriter/](zerowriter/README.md) | [ZeroWriter Ink](../devices/zerowriter/zerowriter-ink/README.md) · [Zerowriter Fold](../devices/zerowriter/zerowriter-fold/README.md) |
-| **M5Stack** | [m5stack/](m5stack/README.md) | [PaperMono](../devices/m5stack/papermono/README.md) · [DinMeter](../devices/m5stack/dinmeter/README.md) · [Cardputer family](../devices/README.md#cardputer-family--added-2026-09-04) · [Cardputer expansions](../devices/README.md#cardputer-expansions--lora-sub-ghz-and-nfc--added-2026-09-04). Updated 2026-09-04 (§11) by the DinMeter pass: the **re-served-asset trap** (byte-identical schematics/STLs under new SKU names), `sitemap.xml` as the only working enumeration route, the `id="document"` extraction recipe, shop `.js` JSON and the **`[EOL]` title prefix** as the lifecycle signal, Shopify serving **JPEG under `.webp` URLs**, the Altium **double-draw** glyph trap, and confirmation that specification rows are carried over unedited between product generations |
-| **LilyGO / TTGO** | [lilygo/](lilygo/README.md) | [T-Display-S3 family](../devices/README.md#lilygo-shenzhen-xin-yuan-electronic-technology-also-trades-as-ttgo) · [T-Display K230](../devices/lilygo/t-display-k230/README.md). ⚠ **No portal or wiki: everything is GitHub + a Shopify feed.** Covers the public `products.json` feed (the only source of launch dates and revision-bearing SKU titles), the **default branch is often not `main`** trap, inconsistent/absent repository licences, the three pin-header filenames, Altium Form-XObject PDF extraction, **offset text layers in Chinese-vendor datasheets**, and why the closed issue tracker *is* the documentation. ⚠ **LilyGO stock codes collide with chip part numbers** — `K230` is a SKU for an ESP32-S3 board |
-| **Xteink** (Shenzhen Xiaohu Xingtong Technology) | [xteink/](xteink/README.md) | [Xteink family](../devices/README.md#xteink-阅星瞳--星瞳-star-pupil) — X3 · X4 · X4 Pro · X4 Classic · [X4 Light](../devices/xteink/x4-light/README.md) · S4 · Nano. ⚠ **Publishes no datasheet, schematic, wiki or support portal — only a stock Shopify store.** Covers the unauthenticated `products.json` / `collections.json` / `<handle>.js` endpoints that are the only source of launch dates, SKUs and stock; the **empty-`body_html` trap** (the X4 Classic's spec table exists only in the rendered HTML); `compare_at_price` and `grams` being neither a former price nor the device mass; and ⭐ **enumerating the FCC grantee code `2BTR9` rather than the product name**, which returns every device the vendor has certified **including ones it never announced** — that is how the X4 Light was found. Plus the **inverted Cloudflare block on `fccid.io`** (403 to Chrome, 200 to `curl`). *Added 2026-09-11* |
-| **Solder Party** | [solder-party/](solder-party/README.md) | *none documented yet* — anticipatory guide. Small open-hardware company (Malmö, Sweden; arturo182) |
+
 ## Component vendors — parts we document
 
 | Vendor | Guide | Parts we track |
@@ -40,11 +37,7 @@ For **board vendors and marketplaces** — where to *buy* rather than where to *
 | SGMicro | [sgmicro/](sgmicro/README.md) | [SGM2036-3.3](../components/sgmicro/sgm2036-3.3/README.md) |
 | Alpha & Omega Semiconductor | [alpha-and-omega-semiconductor/](alpha-and-omega-semiconductor/README.md) | [AO3400A](../components/alpha-and-omega-semiconductor/ao3400a/README.md) |
 | Alps Alpine | [alps-alpine/](alps-alpine/README.md) | [SSCM110100](../components/alps-alpine/sscm110100/README.md) |
-| **Semtech** | [semtech/](semtech/README.md) | [SX1262](../components/semtech/sx1262/README.md) · [SX1276](../components/semtech/sx1276/README.md) · [SX1268](../components/semtech/sx1268/README.md) · [LLCC68](../components/semtech/llcc68/README.md) · [LR11x0](../components/semtech/lr11x0/README.md) · [LR1121](../components/semtech/lr1121/README.md) · [LR2021](../components/semtech/lr2021/README.md). ⚠ **Documents are not on `semtech.com`.** They are behind a Salesforce content-distribution shell that is `blocked` for automated clients — HTTP 200 for valid *and* invalid tokens. Use **Digi-Key** or **Mouser** (⚠ Mouser needs the WhatsApp UA). ⭐ A **1 984-entry JSON document catalogue** is embedded in one page and is the only complete enumeration. `www.semtech.com/uploads/documents/` **soft-404s** — 200 + HTML for every path, including invented ones |
-| **Canaan Creative (Kendryte)** | [canaan/](canaan/README.md) | [K230](../components/canaan/k230/README.md) — the repository's first RISC-V part. Documentation is **Markdown in a Git repository**, not PDFs on a portal. ⚠ Key trap: the **`en/` tree contains no binary hardware artifacts; the `zh/` tree carries every schematic, Gerber and BOM.** Three of four Canaan repositories use a non-obvious default branch (`dev`, `canmv_k230`) |
-| [DKE](dke/README.md) | e-paper display modules | [DEPG0397BBS770F3](../components/dke/depg0397bbs770f3/README.md) |
-| [Everest Semiconductor](everest-semiconductor/README.md) | audio codecs | [ES8156](../components/everest-semiconductor/es8156/README.md) · [ES8311](../components/everest-semiconductor/es8311/README.md) |
-| [OmniVision](omnivision/README.md) | CMOS image sensors | [OV2640](../components/omnivision/ov2640/README.md) · [OV3660](../components/omnivision/ov3660/README.md) · [OV5640](../components/omnivision/ov5640/README.md) |
+
 ## Component vendors — datasheets held, README record outstanding
 
 These vendors have **no `README.md` component record**, but this repository **does hold retrieved
diff --git a/vendors/canaan/README.md b/vendors/canaan/README.md
deleted file mode 100644
index 55cad92..0000000
--- a/vendors/canaan/README.md
+++ /dev/null
@@ -1,135 +0,0 @@
-# Vendor documentation sourcing — Canaan Creative (Kendryte)
-
-**Compiled 2026-09-04** while researching the [Kendryte K230](../../components/canaan/k230/README.md)
-for the [LilyGO T-Display K230](../../devices/lilygo/t-display-k230/README.md). First Canaan
-part in this repository.
-
-Canaan Creative Co., Ltd (嘉楠科技, NASDAQ: **CAN**) publishes its Kendryte SoC documentation in a
-way that is unusual enough to be worth writing down once: **as Markdown in a public Git
-repository**, not as PDFs behind a portal. Everything below is live-verified on the stated date.
-
----
-
-## 1. Which host serves what
-
-| Host | Serves | Stability |
-|---|---|---|
-| `github.com/kendryte/k230_docs` | **The canonical documentation.** Markdown sources, images, and binary EDA artifacts | High — commit-pinnable |
-| `raw.githubusercontent.com/kendryte/k230_docs/main/…` | Raw file fetch | High, but `main` moves |
-| `www.kendryte.com/k230/<lang>/<branch>/…` | Rendered HTML build of the same repository | Medium — URL shape encodes a branch name |
-| `developer.canaan-creative.com` | Developer community; **prebuilt SDK images** under *K230 → Images*; `/resource` index | Medium — SPA-ish, requires navigation |
-| `canaan-creative.com` | Corporate site | Marketing only |
-| `salesAI@canaan-creative.com` | The **only** sales channel printed in the datasheet | — |
-
-Prefer the repository. It is the source the rendered site is built from, it can be pinned to a
-commit, and it contains files the rendered site does not expose.
-
-## 2. URL templates that work
-
-```sh
-# Pinned permalink — always prefer this in citations
-https://github.com/kendryte/k230_docs/blob/<SHA>/<path>
-https://github.com/kendryte/k230_docs/raw/<SHA>/<path>
-
-# Branch-tracking raw fetch — fine for a one-off, wrong for a citation
-https://raw.githubusercontent.com/kendryte/k230_docs/main/en/00_hardware/K230_datasheet.md
-
-# Rendered HTML
-https://www.kendryte.com/k230/en/main/00_hardware/K230_datasheet.html
-https://www.kendryte.com/k230/zh/main/00_hardware/
-```
-
-**Enumerate everything published for a product in one call:**
-
-```sh
-gh api repos/kendryte/k230_docs/git/trees/main?recursive=1 \
-  | python3 -c 'import json,sys;[print(e["size"],e["path"]) for e in json.load(sys.stdin)["tree"] if e["type"]=="blob"]'
-```
-
-Use `gh api`, not anonymous `curl`. One recursive tree listing of this repository returns 837
-entries and can exhaust the 60/hour anonymous GitHub limit; the resulting 403 carries
-`X-RateLimit-Remaining: 0` and **looks exactly like a bot block**. Check that header before
-rotating User-Agents — no User-Agent helps, because `api.github.com` limits per identity.
-
-## 3. The trap that matters most: `en/` is not a translation of `zh/`
-
-**The English tree contains no binary hardware artifacts. The Chinese tree does.**
-
-Verified 2026-09-04 at commit `f8e30213963e0ed5cf995c3cd4701218a45e4793`:
-
-| | `en/00_hardware/` | `zh/00_hardware/` |
-|---|---|---|
-| Datasheet Markdown | yes | yes |
-| Hardware design guide | yes | yes |
-| **Board schematics (PDF)** | **none** | `K230-DEMO-BOARD-SCH.pdf`, `K230-SIP-EVB-…pdf`, `CanMV-K230-V1.0_2023-09-15.pdf` |
-| **OrCAD `.DSN` sources** | **none** | three, 1.7–1.85 MB each |
-| **Gerber / PCB / DXF / SMT / BOM** | **none** | full sets for LP3, LP4 and K230D SiP EVB |
-
-An agent that searches only `en/` will report "Canaan publishes no schematics". That conclusion
-is wrong, and it is an easy mistake because the two trees have parallel directory names. **Always
-list `zh/` as well**, even when you cannot read the prose. Enumerated inventory with sizes:
-[`components/canaan/k230/artifacts/CANAAN-EDA-SET.md`](../../components/canaan/k230/artifacts/CANAAN-EDA-SET.md).
-
-## 4. Document-class checklist for a Kendryte part
-
-Tick these off before declaring a sourcing pass complete. Status column is for **K230 as of
-2026-09-04**.
-
-| Class | Expected path | K230 status |
-|---|---|---|
-| Full datasheet | `en/00_hardware/K230_datasheet.md` | ✅ V1.0, 2023-07-06 |
-| Brief datasheet | `en/K230_brief_datasheet.md` | ✅ (note: **not** under `00_hardware/`) |
-| Hardware design guide | `en/00_hardware/K230_Hardware_Design_Guide.md` | ✅ |
-| **Pinout / ball map** | `《K230_PINOUT_V1.0_20230524》` | ❌ **cited by the datasheet, not published** |
-| **Errata** | — | ❌ **none published** |
-| Reference-board resource guide | `en/00_hardware/K230_DEMO_BOARD_Resource_Usage_Instructions.md` | ✅ |
-| SDK user manual | `en/01_software/board/K230_SDK_User_Manual.md` | ✅ |
-| Per-subsystem API references | `en/01_software/board/mpp/*` | ✅ — Audio, DMA, DPU, FFT, GPU, VICAP, video codec, video output, system control, non-AI 2D |
-| Driver API references | `en/01_software/board/osdrv/*` | ✅ — big-core and little-core driver APIs, DRM, PMU |
-| Boot / flashing tool guide | `en/01_software/pc/burntool/K230_SDK_Burntool_User_Guide.md` | ✅ |
-| ISP tuning | `en/01_software/pc/ISP_tuning/*` | ✅ |
-| nncase / AI toolchain | `en/01_software/board/ai/K230_nncase_Development_Guide.md` | ✅ |
-| nncase↔SDK version table | `en/03_other/K230_SDK_nncase_version_correspondence.md` | ✅ — **read this before compiling any model** |
-| Release notes | `en/03_other/K230_SDK_Release_Notes.md` | ✅ |
-| FAQ set | `en/03_other/K230_FAQ.md`, `K230_SDK_FAQ_C.md`, … | ✅ |
-
-Two of those are the ones to remember: **no pinout document and no errata document**. Both are
-absences confirmed by full recursive listing, not by a failed search.
-
-## 5. Licence conflict — expect it, record it
-
-The `k230_docs` repository is licensed **BSD-2-Clause** (GitHub's licence detection, repository
-metadata). The datasheet inside it carries:
-
-> "This document is only suitable for the development and design of K230 platform, without the
-> written permission of the company, any unit or individual shall not disseminate part or all of
-> the content of this document in any form."
-
-These cannot both be true of the same bytes. Canaan appears to have applied a standard corporate
-notice to a document it then released permissively and never reconciled the two. **Record the
-conflict; do not pick a side.** Retained copies in this repository are held **unstaged**.
-
-## 6. Repositories worth knowing
-
-| Repository | Branch | Licence | Purpose |
-|---|---|---|---|
-| `kendryte/k230_docs` | `main` | BSD-2-Clause | Documentation (above) |
-| `kendryte/k230_sdk` | `main` | BSD-2-Clause | Original dual-OS SDK (RT-Smart on CPU1 + Linux on CPU0). Docker image `ghcr.io/kendryte/k230_sdk`. Last push 2025-09-12. |
-| `kendryte/k230_linux_sdk` | **`dev`** | BSD-2-Clause | **Linux-only** SDK, actively maintained. Note the default branch is `dev`, not `main` — a `main` clone gets nothing. |
-| `kendryte/canmv_k230` | `canmv_k230` | none declared | MicroPython. **Default branch is `canmv_k230`**, another non-obvious name. |
-
-**Non-default branch names are this vendor's recurring trap.** Three of four repositories use a
-default branch that is neither `main` nor `master`. Always read `.default_branch` from the API
-rather than assuming.
-
-## 7. Getting prebuilt images
-
-`developer.canaan-creative.com` → *K230* → *Images*. LilyGO's wiki cites the same path
-(`https://developer.canaan-creative.com/resource`). This is the route for a factory-style
-recovery image when you do not want to build the SDK. Not retrieved in this pass; access
-behaviour and whether a login is required are **unverified**.
-
-## 8. Products that produced these findings
-
-- [Kendryte K230](../../components/canaan/k230/README.md) — component record
-- [LilyGO T-Display K230](../../devices/lilygo/t-display-k230/README.md) — device record
diff --git a/vendors/dke/README.md b/vendors/dke/README.md
deleted file mode 100644
index f177620..0000000
--- a/vendors/dke/README.md
+++ /dev/null
@@ -1,235 +0,0 @@
-# DKE — documentation sourcing guide
-
-**DKE Holding Company Limited** (东方科脉 / Dongfang Kemai) — e-paper (electrophoretic)
-display module manufacturer, China.
-
-Established **2026-09-01** while researching the panel fitted to the
-[M5Stack PaperMono](../../devices/m5stack/papermono/README.md). This is a **short guide**,
-because DKE's documentation surface, as encountered, is small: one manual, obtained
-indirectly, with one severe retrieval trap.
-
-Product documented with this guide:
-[**`DEPG0397BBS770F3`**](../../components/dke/depg0397bbs770f3/README.md).
-
-## 1. ⚠ The panel manual comes from the *board* vendor, not from DKE
-
-**No DKE-hosted copy of the `DEPG0397BBS770F3` manual was located, and no public DKE
-document portal was found to search.**
-
-The 30-page *EPD Module User Manual* — "Specification for 3.97 inch EPD" — was obtained
-solely as an attachment on **M5Stack's** PaperMono product page, where it is linked under
-the generic label **"3.97-inch Touchscreen"** in the *Datasheets* list. Verified
-2026-09-01:
-
-```
-https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1267/EPD_Module_User_Manual.pdf
-```
-
-8,666,208 bytes ·
-SHA-256 `6b65f56d5d549a132e5c807eef329fb3e997feab04ac06e8a107f01591618130`.
-
-Note what the URL does **not** contain: the manufacturer's name, the part number, or
-anything identifiable. `EPD_Module_User_Manual.pdf` under an M5Stack numeric product id.
-**You cannot find this file by searching for the DKE part number.**
-
-> **The general lesson, and it applies well beyond DKE:** for a display panel, the panel
-> maker's documentation is very often distributed **through whoever put the panel on a
-> board**, under a generic label, on the board vendor's CDN. **Look at the board vendor's
-> asset list before concluding the panel manual does not exist.** Enumerate every asset
-> URL on the product page — including the ones with unhelpful names — rather than
-> searching for the part number.
->
-> How to enumerate M5Stack's asset URLs, including the `zh_CN`-only ones:
-> [`vendors/m5stack`](../m5stack/README.md).
-
-### 1.1 Provenance caveats worth carrying
-
-- The manual is **undated on its cover** and carries **no revision table**. The only
-  internal date is on the embedded mechanical drawing: `REV. A0`, `FIRST ISSUE`,
-  **2024-09-29**.
-- Its PDF `Producer` is **`iLovePDF`** and its `ModDate` is **2026-08-21** — the same day
-  the PaperMono store listing went live. There is **no `Author`, `Title` or `Creator`
-  metadata at all**. The file was clearly re-processed before publication, and the
-  original authoring tool is unrecoverable.
-- Licence: DKE copyright, **no licence statement and no confidentiality footer**.
-  Mirrored by M5Stack with no stated terms. Redistribution status `unknown`.
-- ⚠ **Single-source.** Only one acquisition URL is known for this document. That is
-  recorded deliberately rather than left as a silent gap, and it is why the bytes are
-  retained in the repository rather than referenced.
-
-> **Discrepancy noted 2026-09-01.** The component record's source table gives the upstream
-> as `static-cdn.m5stack.com/resource/docs/products/core/PaperMono/…`. The URL actually
-> present in the retrieved product page is the OSS bucket path above. `static-cdn.m5stack.com`
-> is a real M5Stack host and does serve `/resource/docs/products/<category>/<Product>/…`
-> assets, but **no reference to `EPD_Module_User_Manual.pdf` on that host was found in the
-> captured pages.** Treat the OSS URL as the verified one and the `static-cdn` form as an
-> unverified alternative worth trying if the OSS bucket goes away.
-
-## 2. ⚠ The manual has no text layer — `pdftotext` returns nothing, silently
-
-**This is the trap that matters, and it fails in the worst possible way: quietly.**
-
-Every glyph in the PDF is a **vector outline**. There is no embedded text at all. So:
-
-```bash
-pdftotext depg0397bbs770f3-epd-module-user-manual.pdf -
-# -> empty. Not garbage. Not an error. Nothing.
-```
-
-An empty result is easy to misread as "extraction failed, try another tool" or, worse, as
-"this page is blank". Neither is true — the page is full of information that simply is not
-text.
-
-*(Recorded as the lesser evil: had `pdftotext` returned plausible-looking **wrong** text,
-that text would have had to be validated against a rendered page before use. Silence is at
-least unambiguous once you know to expect it. **Validate any PDF extraction against a
-render at least once**, whatever it returns.)*
-
-### The working method: rasterise and read the images
-
-```bash
-# render one page (here, page 7) at 140 dpi
-pdftoppm -r 140 -png -f 7 -l 7 \
-  artifacts/depg0397bbs770f3-epd-module-user-manual.pdf pg
-# -> pg-07.png, then read it as an image
-
-# the whole document
-pdftoppm -r 140 -png artifacts/depg0397bbs770f3-epd-module-user-manual.pdf pg
-```
-
-On a NixOS/devshell host without `poppler-utils` on the path:
-
-```bash
-nix-shell -p poppler-utils --run \
-  'pdftoppm -r 140 -png -f 7 -l 7 artifacts/depg0397bbs770f3-epd-module-user-manual.pdf pg'
-```
-
-**140 dpi was sufficient** for this document's tables and its mechanical drawing.
-Eighteen of the thirty pages were transcribed this way (1, 4–10, 15–19, 21–25); every
-figure in the component record cites its manual page number so it can be re-checked by
-rendering that one page.
-
-### Detecting the condition before you waste time
-
-```bash
-pdffonts file.pdf      # no fonts listed -> no text layer
-pdfinfo  file.pdf      # check Producer: a re-processor such as iLovePDF is a warning sign
-```
-
-A `Producer` of `iLovePDF`, `PDFill` or a similar web re-processor is a **standing warning
-sign** that a document has been through a lossy round trip. M5Stack's mirrored **SSD1677**
-PDF shows the same pattern from a different tool: 46 pages numbering themselves `n/47`,
-Producer `PDFill`. See [`vendors/m5stack` §5.5](../m5stack/README.md).
-
-## 3. Part-number pattern
-
-Observed on one part, so treat as a **hypothesis with one confirming instance**, not a
-decoder:
-
-```
-DEPG  0397   BB    S770   F3     [ HP-XM ]
- |     |     |      |      |         |
- |     |     |      |      |         └─ customer/option suffix, undocumented
- |     |     |      |      └─ revision / interface variant
- |     |     |      └─ internal variant code
- |     |     └─ variant code
- |     └─ diagonal size in hundredths of an inch: 0397 = 3.97"
- └─ DKE E-Paper Display family prefix
-```
-
-**`DEPG` + a four-digit size in hundredths of an inch is the reliable part** — the size
-field is confirmed by the manual's own title ("Specification for 3.97 inch EPD"). The rest
-is not decoded by any DKE document located, and **no part-number decoder for the `DEPG*`
-family was found**.
-
-> ⚠ **A suffix conflict is live and unresolved.** The manual cover and the mechanical
-> drawing's title block both say **`DEPG0397BBS770F3`**. M5Stack's
-> `M5PaperMono-OTP-Demo/README.md` calls the fitted panel
-> **`DEPG0397BBS770F3HP-XM`**. The M5Stack string is a strict superset, so the likeliest
-> reading is that `HP-XM` is a customisation suffix — `HP` possibly a waveform or OTP
-> option, `XM` a customer code — and that DKE supplied a customer-specific OTP under a
-> base-model manual. **That is a hypothesis, not a finding**: no DKE document in hand
-> mentions any suffix.
->
-> **Practical consequence:** when sourcing a DKE panel, the base part number may not
-> describe the OTP waveform actually programmed into the unit you receive. For this panel
-> the OTP waveform contents — how many of the 34 waveform slots are programmed, over what
-> temperature span — are **unpublished**, and running outside the programmed range is a
-> silent no-refresh failure.
-
-## 4. Known data errors in DKE material
-
-One, and it is provable:
-
-> **The mechanical drawing's note 3 reads `800 gate × 480 source`, which is backwards.**
-> 800 gate lines would exceed the bonded SSD1677 controller's **680 gate outputs**, and
-> M5Stack's own firmware configures **480 gates** via `0x01 = {0xDF, 0x01, 0x02}`. The
-> drawing note is wrong; the arithmetic is in the
-> [component record](../../components/dke/depg0397bbs770f3/README.md).
-
-Also worth flagging as an internal inconsistency rather than an error: the manual's
-overview describes the panel as *"capable to display image at **1-bit white and black**"*
-and its optical specification table reads **`GN — 2Grey Level`**, while M5Stack markets
-**4-level greyscale** and the vendor OTP demo implements a working four-grey mode.
-**Unresolved.** Three readings are possible — a stale manual template, a panel binned for
-mono with usable grey, or a marketing overstatement — and nothing in evidence chooses
-between them.
-
-## 5. Document-class checklist
-
-For a DKE panel, expect **only the first line to be obtainable**:
-
-| Class | Where to look | `DEPG0397BBS770F3` result |
-|---|---|---|
-| **Module user manual / specification** | **the board vendor's asset list**, under a generic label | ✅ 30 pp., via M5Stack `1267/EPD_Module_User_Manual.pdf` |
-| Mechanical drawing | usually **embedded in the manual** | ✅ embedded, `REV A0`, 2024-09-29 |
-| Controller datasheet | the **controller maker**, not DKE | ✅ [SSD1677](../../components/solomon-systech/ssd1677/README.md), via an M5Stack mirror |
-| **OTP waveform contents** | — | ❌ **unpublished** |
-| Errata / revision history | — | ❌ **no revision table at all** |
-| Application notes, design guidelines | — | ❌ none located |
-| Product change notices | — | ❌ none located |
-| Reliability / qualification report | — | ⚠ reliability conditions are **inside the manual** |
-| Public document portal | — | ❌ **none found** |
-| Distributor datasheets | — | ❌ none located |
-
-## 6. Per-part procedure
-
-1. **Do not start with DKE.** Start with the board or module vendor that fitted the panel.
-2. **Enumerate every asset URL on the board vendor's product page**, including generically
-   named files. The panel manual will not be named after the part.
-3. Run `pdffonts`. **No fonts means no text layer** — go straight to `pdftoppm`.
-4. Render at **140 dpi PNG** and read the pages as images. Cite manual page numbers so
-   every figure can be re-checked.
-5. **Cross-check the panel manual against the bonded controller's datasheet.** That is how
-   the reversed gate/source note was caught — the panel document contradicted the
-   controller's output count.
-6. **Cross-check against the board vendor's firmware.** Register writes such as
-   `0x01 = {0xDF,0x01,0x02}` (480 gates) settle geometry questions the drawings get wrong.
-7. Record the part-number suffix exactly as each source states it. They will disagree.
-8. Since a DKE-hosted copy is unlikely to exist, **retain the bytes** rather than the URL,
-   and record the single-source status explicitly.
-
-## 7. Rights and licensing observations
-
-- DKE copyright notice on every page footer; the mechanical drawing carries the Chinese
-  mark **东方科脉**.
-- **No licence statement and no confidentiality footer** on the manual — which is unusual
-  and, in practice, permissive by omission rather than by grant. Redistribution status
-  `unknown`.
-- Mirrored by M5Stack with no stated terms of its own. **A board vendor rehosting a panel
-  maker's manual does not relicense it.**
-
-## 8. Products documented with this guide
-
-- [**DKE `DEPG0397BBS770F3`**](../../components/dke/depg0397bbs770f3/README.md) — the
-  3.97" panel of the [M5Stack PaperMono](../../devices/m5stack/papermono/README.md); the
-  pass that produced these findings
-- Related device guide: [`features/epaper-display.md`](../../devices/m5stack/papermono/features/epaper-display.md)
-- Related vendor guide: [`vendors/m5stack`](../m5stack/README.md) — how to enumerate the
-  asset list this manual was hiding in
-
-## 9. Change log
-
-| Date | Change |
-|---|---|
-| 2026-09-01 | Guide created during the M5Stack PaperMono pass. Established: DKE panel manuals are distributed **through the board vendor**, under generic labels, with no public DKE portal located; the `DEPG<size><variant>` part-number pattern and the unresolved `HP-XM` suffix; and the critical retrieval trap that **the manual PDF has no text layer at all** (vector-outlined glyphs), so `pdftotext` silently returns nothing and pages must be rendered with `pdftoppm -r 140 -png` and read as images. Recorded the provably reversed `800 gate × 480 source` drawing note and the unresolved 1-bit/2-grey/4-grey contradiction. |
diff --git a/vendors/everest-semiconductor/README.md b/vendors/everest-semiconductor/README.md
index 2b6404b..0e2b6a7 100644
--- a/vendors/everest-semiconductor/README.md
+++ b/vendors/everest-semiconductor/README.md
@@ -135,7 +135,7 @@ Plain HTTP, no referer, no cookie. A bare `curl` User-Agent was not tested, so w
 
 Every page of the ES8156 datasheet is stamped **"Everest Semiconductor Confidential"**, yet the file is served without authentication from the manufacturer's own public web root and carries **no explicit redistribution clause**. That combination is common with this vendor.
 
-Note Everest datasheets as **`redistribution: unknown`** and keep them in the repository. Flagged for user review. The *driver* sources used to reconstruct register maps are separately and clearly licensed (ESPRESSIF MIT for esp-adf, GPL-2.0 for Linux ASoC) — attribute them correctly and do not let the codec's documentation ambiguity contaminate the licence status of the code.
+Treat Everest datasheets as **`redistribution: unknown`**, disposition `repository (unstaged)`, flagged for user review. The *driver* sources used to reconstruct register maps are separately and clearly licensed (ESPRESSIF MIT for esp-adf, GPL-2.0 for Linux ASoC) — attribute them correctly and do not let the codec's documentation ambiguity contaminate the licence status of the code.
 
 ---
 
diff --git a/vendors/lilygo/README.md b/vendors/lilygo/README.md
deleted file mode 100644
index 84f7a27..0000000
--- a/vendors/lilygo/README.md
+++ /dev/null
@@ -1,335 +0,0 @@
-# LilyGO — documentation-sourcing guide
-
-**LilyGO** (Shenzhen Xin Yuan Electronic Technology Co., Ltd.; formerly and still partly
-**TTGO**) publishes **no documentation portal, no wiki and no datasheet archive**. Everything is
-in two places: **GitHub** and a **Shopify storefront**. That is unusual enough — and the
-consequences are specific enough — to be worth writing down once.
-
-First written **2026-09-07** during the
-[T-Display-S3 family](../../devices/lilygo/t-display-s3-shared/README.md) pass.
-Other agents: **append a section rather than rewriting.**
-
----
-
-## 1. Where things actually are
-
-| Document class | Where | Reliability |
-|---|---|---|
-| Schematics (PDF) | `github.com/Xinyuan-LilyGO/<board>/schematic/` | **good** — most boards have one |
-| Chip datasheets (mirrored) | same repo, `datasheet/` or `information/` | **the only source for several parts.** Sitronix, Raydium, Hynitron, AXS, Chipone and Shenghe publish nothing openly |
-| Pin maps | `examples/*/pin_config.h`, `pins_config.h` or `utilities.h` — **the name varies by board** | **good, and authoritative** |
-| Cross-board pin maps | `Xinyuan-LilyGO/LilyGo-Display-IDF` → `main/product_pins.h` | **excellent** — nine boards in one file |
-| Factory firmware | same repo, `firmware/`, plus `firmware/README.MD` | good |
-| Mechanical (DWG/DXF/STP/STL/7z) | same repo, `dimensions/` | good |
-| Board definitions | `boards/*.json` (PlatformIO) — path is sometimes `board/` singular | good |
-| Prices, SKUs, launch dates, stock | `https://lilygo.cc/collections/all/products.json` | **excellent, and machine-readable** |
-| Revision history, changelog, ECNs, BOMs, errata | **nowhere.** None exists for any board | — |
-
-## 2. The store's product feed is the best market source there is
-
-Shopify exposes a public JSON feed. One request replaces any amount of page scraping:
-
-```bash
-curl -sS -A 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36' \
-  'https://lilygo.cc/collections/all/products.json?limit=250&page=1'
-```
-
-It returns, per product: `title`, `handle`, **`published_at`** (the launch date — obtainable
-nowhere else), `updated_at`, `product_type`, full-resolution image URLs, and per variant
-`title`, `sku`, `price`, **`available`**. 214 products came back on 2026-09-07 in six pages.
-
-**A plain request is served; a browser User-Agent is safer.** Recorded in
-[`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md).
-
-**Traps in the feed:**
-
-- **Variant titles carry hardware revisions.** `H619 "V1.0 Non-Soldered Pin"` and
-  `H713 "V2.0 Non-Soldered Pin"` are two PCB revisions in one dropdown, both in stock. This is
-  often the *only* place a revision is named.
-- **Regional SKUs are the same board at a markup** (`H577` USD 9.54 vs `USH577` USD 14.04) and
-  are frequently out of stock.
-- **Duplicate product pages exist** — `t-display-s3` and `t-display-s3-copy` both list SKU
-  `H569` one cent apart.
-- **One product page can sell several different boards.** `t-display-s3-amoled-1-64` sells
-  1.43″, 1.64″ and two 1.75″ variants with **different display and touch controllers**.
-
-## 3. GitHub: authenticate, and never assume the branch
-
-`api.github.com` limits **per identity**, so rotating User-Agents does nothing. Use the token —
-60/h becomes 5 000/h:
-
-```bash
-gh api "orgs/Xinyuan-LilyGO/repos?per_page=100&page=1" \
-  --jq '.[] | [.name,.default_branch,.pushed_at,.stargazers_count] | @tsv'
-```
-
-A 403 carrying `X-RateLimit-Remaining: 0` is the rate limit, **not** bot-blocking. Check that
-header before rotating anything.
-
-### ⚠ The default branch is often not `main`
-
-This is LilyGO's most distinctive trap, and it will silently give you the wrong file.
-
-| Repository | Default branch | What it encodes |
-|---|---|---|
-| `T-Display-S3-Long` | **`T-Display-S3-Long-cst3530`** | a **touch-controller revision** |
-| `T-Display-S3-AMOLED-1.64` | **`arduino-esp32-libs_V2.0.14`** | a pinned Arduino core |
-| `T-CameraPlus-S3`, `T-Circle-S3` | `arduino-esp32-libs_V2.0.14` | as above |
-| `T-Encoder-Pro` | `arduino-esp32-libs_V3.0.7` | a *different* pinned core |
-| `T5S3-4.7-e-paper-PRO` | `H752-01` | an SKU |
-| `LilyGo-EPD47` | `esp32s3` | a target |
-
-**Always read `.default_branch` from the API and resolve it to a commit SHA before fetching.**
-Cite the SHA, never the branch — LilyGO force-pushes.
-
-```bash
-SHA=$(gh api repos/Xinyuan-LilyGO/T-Display-S3/commits/main --jq .sha)
-gh api "repos/Xinyuan-LilyGO/T-Display-S3/git/trees/$SHA?recursive=1" \
-  --jq '.tree[] | [.type,.size//0,.path] | @tsv'
-```
-
-One recursive tree call replaces hundreds of directory listings. Repo trees run 84–5 008
-entries; the display repos are 60–300 MB and mostly image headers and vendored libraries, so
-**fetch individual files from `raw.githubusercontent.com` rather than cloning** unless you need
-the whole tree.
-
-### Naming is inconsistent between repo and product
-
-`T-Display-S3-AMOLED` is a repo *and* a product; but the S2 board's repo is
-**`LilyGo-T-Display-S3`**-style (`LilyGo-T-Display-S2`), not `T-Display-S2`. `gh api
-repos/Xinyuan-LilyGO/T-Display-S2` 404s. Search the org listing rather than guessing paths.
-
-### Licences are inconsistent, and sometimes absent
-
-| Repo | Licence |
-|---|---|
-| `T-Display-S3`, `T-Display-S3-AMOLED`, `LilyGo-AMOLED-Series`, `T-Dongle-S3`, `T-QT`, `LilyGo-Display-IDF` | MIT |
-| `T-Display-S3-AMOLED-1.64`, `T-Display-S3-Pro-MVSRBoard`, `T-Display-S3-Pro-MVSRLora` | GPL-3.0 |
-| **`T-Display-S3-Long`, `T-Display-S3-Pro`, `T-Touchbar-AMOLED`** | **none declared** |
-
-Note that MIT is a *software* licence and LilyGO applies no hardware licence at all, so **the
-redistribution status of a schematic PDF inside an MIT repository is unstated**, and inside an
-unlicensed repository it is doubly unknown. Mirrored **chip** datasheets are third-party
-copyright regardless of the repo licence, and several are marked CONFIDENTIAL — see §5.
-
-## 4. Pin maps: three filenames, one job
-
-| Filename | Boards |
-|---|---|
-| `pin_config.h` | T-Display-S3; the 1.43/1.75″ AMOLED (under `components/private_library/`) |
-| `pins_config.h` | AMOLED 1.91″, Long |
-| `utilities.h` | Pro |
-| `main/product_pins.h` | **`LilyGo-Display-IDF` — nine boards in one file, behind `CONFIG_LILYGO_*`** |
-
-**Read `product_pins.h` first.** It is the single best cross-board source in the catalogue and
-several boards' pin maps are *only* correct there.
-
-**Per-board headers contain copy-paste defects.** `T-Display-S3-Long`'s
-`examples/factory/pins_config.h` @ `37a7e83` defines `PIN_BAT_VOLT 2` while also defining
-`TP_RST 2`, and `PIN_BUTTON_2 21` while also defining `TFT_QSPI_D2 21` — both inherited from the
-AMOLED board's header, where they are correct. **Cross-check any pin map against
-`product_pins.h` and against the schematic before using it.**
-
-## 5. Reading LilyGO's PDFs — two real traps
-
-### 5.1 Altium exports hide the sheet in a Form XObject
-
-Board schematics are Altium PDF exports. Reading `/Contents` alone returns only the
-`PI…`/`CO…` pin-marker text and **none of the labels**. You must walk **every** content stream
-in the file, including Form XObjects. Then group text by `BT…ET` block — reading `Tj`/`TJ`
-operators individually shreds every label into single characters.
-
-The repository's [`tools/altium_pdf_netlist.py`](../../tools/altium_pdf_netlist.py) and
-[`altium_pdf_pin_table.py`](../../tools/altium_pdf_pin_table.py) do the real work but need
-`pdftotext -bbox` XML, i.e. **poppler**. Without it you can recover a **designator and part-name
-census** but **not net connectivity** — which is exactly the limitation stamped on every LilyGO
-schematic claim in this repository as of 2026-09-07.
-
-**One schematic is different.** `T4-S3-240719.pdf` uses **Type0/Identity-H subset fonts with
-`/ToUnicode` CMaps**, where every other LilyGO sheet uses WinAnsi TrueType. An extractor that
-works on the others returns **nothing** on it. You need a CMap decoder.
-
-### 5.2 Chinese-vendor datasheets can have offset text layers
-
-**Chipone's `CO5300_V0.01.pdf` has a uniform `+0x1D` code-point offset.** Extracted naively it
-reads `&2||2/(' … &+,321(7HFKQRORJ\`; through its `/ToUnicode` CMap it reads
-`FOD300 … FHHPONE TecOnology` — **human-legible and wrong**, the most dangerous failure mode
-there is. Both decode consistently to *CO5300 … CHIPONE Technology (Beijing) Co., Ltd.*
-
-Shenghe's `SH8501B0` and `SH8601Z` datasheets show the same pattern.
-
-**Rule:** on any LilyGO-mirrored datasheet, run **two** independent extraction routes and
-require them to agree, or validate against a rendered page, **before transcribing a single
-value**. Nothing in this repository's LilyGO records transcribes a numeric value from an
-unvalidated text layer.
-
-## 6. Chip identities recovered from LilyGO mirrors
-
-Several parts have **no public datasheet anywhere else**. Establishing who makes them is a
-recurring win from mirrors:
-
-| Part | Maker, established from the mirrored datasheet cover |
-|---|---|
-| **AXS15231(B)** | **AXS Technology Corp.** — with an explicit no-redistribution notice |
-| **CO5300** | **Chipone Technology (Beijing) Co., Ltd.** |
-| **SH8601Z**, **SH8501B** | **SHENGHE MICRO ELECTRONICS** — both marked CONFIDENTIAL |
-
-That last one settles a naming question that predates this pass: this repository's
-[`generic/sh8601-compatibility-driver`](../../components/generic/sh8601-compatibility-driver/README.md)
-record could establish that `esp_lcd_sh8601` is a generic QSPI shim, but not who would make a
-real SH8601. **Shenghe does**, and LilyGO fits one.
-
-## 7. Where LilyGO's knowledge actually lives: closed GitHub issues
-
-This is the most important practical observation in this guide.
-
-LilyGO's maintainer (`lewisxhe`) answers issues quickly, accurately, and often **with
-photographs of the PCB**. What does not happen is any of that reaching the README, a revision
-number or a changelog. So:
-
-- **The issue tracker is the documentation.** `T-Display-S3` has 318 issues, of which 1 is
-  open; the answers are in the closed ones.
-- **A stale-bot closes threads after 30 + 14 days.** "Closed as inactive" does not mean
-  resolved, and several of the most valuable findings in this repository sit in such threads.
-- **Search closed issues first**, before the README.
-
-Examples of facts that exist *only* in an issue thread:
-GPIO16/17 have fitted pull-ups on non-touch T-Display-S3 boards (with photographs,
-[#313](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/313)); there is no battery
-protection on the board ([#230](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/230),
-2025-02-06); `VBUS` is deliberately not on the header and LilyGO's suggested fix is to solder a
-wire ([#42](https://github.com/Xinyuan-LilyGO/T-Display-S3/issues/42)).
-
-And one revision is documented **only in a `//!` source comment**:
-`T-Display-S3-Pro/examples/factory/utilities.h` @ `08b8b2b` —
-*"The difference between V1.0 and V1.1 is the backlight driver"* — with a 255-vs-16 brightness
-scale behind an `#ifdef`.
-
-## 8. Per-product checklist
-
-Before declaring a LilyGO board researched:
-
-1. Resolve the repo's **`.default_branch`**, then its **commit SHA**. Cite the SHA.
-2. Pull the **recursive tree** and inventory `schematic/`, `datasheet/`, `information/`,
-   `firmware/`, `dimensions/`, `boards/` or `board/`.
-3. Read **`LilyGo-Display-IDF/main/product_pins.h`** for the board's `CONFIG_LILYGO_*` block,
-   and cross-check it against the per-board `pin_config.h` / `pins_config.h` / `utilities.h`.
-4. Pull the **store feed** and record `published_at`, every SKU, price and stock state — and
-   check whether any **variant title names a hardware revision**.
-5. Search the **issue tracker including closed issues**, sorted by comment count.
-6. Grep the vendor's own source for `V1.0`, `V1.1`, `//!`, `#ifdef USING_`, and any
-   `-DTOUCH_MODULES_*`-style build flag. **Revisions hide there.**
-7. Check whether **ESPHome** carries a named model — `esphome/components/mipi_spi/models/` has
-   pins, offsets, colour order and init sequences for several LilyGO boards, and it is an
-   **independent** source against LilyGO's own.
-8. Extract the schematic text **two ways** and require agreement before transcribing anything.
-9. Record what LilyGO does **not** publish: BOM, revision history, errata, certification.
-
-## 9. Products cross-referenced from this guide
-
-- [T-Display-S3 family (11 boards)](../../devices/lilygo/t-display-s3-shared/README.md) —
-  produced §§2–8 of this guide
-- [T-Display K230 Kit](../../devices/lilygo/t-display-k230/README.md) — documented separately
-
----
-
-## 10. Findings added by the T-Display K230 pass — 2026-09-04
-
-Appended **2026-09-07** from [`scratch/lilygo-k230/vendor-guide-additions.md`](../../scratch/lilygo-k230/vendor-guide-additions.md).
-That pass ran on 2026-09-04, when `vendors/lilygo/README.md` did **not yet exist**, and parked
-its reusable sourcing findings in scratch rather than race the sibling T-Display-S3 session that
-later wrote §§1–9. All observations below were live-verified **2026-09-04**. Where they overlap
-§§1–9 they **corroborate independently** — they were written without sight of that text.
-
-### 10.1 Hosts
-
-| Host | Serves | Notes |
-|---|---|---|
-| `lilygo.cc` | Shopify storefront | The **authoritative source of SKUs and prices** |
-| `wiki.lilygo.cc` | VitePress documentation site | Server-rendered — content **is** in the initial HTML, no JS execution needed |
-| `github.com/Xinyuan-LilyGO` | Board repositories | **The best primary evidence LilyGO produces**, better than either of the above |
-| `cdn.shopify.com/s/files/1/0617/7190/7253/files/<name>` | Product images | Stable direct URLs; `?v=<epoch>` is a cache buster and can be dropped |
-
-### 10.2 Enumeration — the Shopify JSON endpoints
-
-```sh
-# Full structured product record: every variant, SKU, price in cents, availability,
-# created_at / published_at, the complete description HTML, and every image URL
-curl -s https://lilygo.cc/products/<handle>.js | python3 -m json.tool
-
-# Search, returning handles
-curl -s 'https://lilygo.cc/search?q=<term>&type=product'
-```
-
-`.js` gives you things the HTML page does not surface at all:
-
-- `created_at` and `published_at` — **exact product launch dates**, e.g. T-Display K230 Kit
-  `created 2026-08-06`, `published 2026-08-20`.
-- Per-variant `sku` strings, which are LilyGO's internal stock codes.
-- Prices as integer cents per variant, avoiding currency-formatting ambiguity.
-- The full description HTML, which is where the specification table lives.
-
-A `curl` with the default UA is enough; no User-Agent rotation was needed on any `lilygo.cc`
-URL during this pass. `wiki.lilygo.cc` likewise returned 200 to a plain request, though a
-browser UA was used throughout as a precaution.
-
-### 10.3 ⚠ The SKU trap — LilyGO stock codes collide with chip names
-
-**`K230` is a LilyGO SKU for the transparent-case variant of the T-Embed CC1101**, which is an
-ESP32-S3 board with no Kendryte silicon in it whatsoever. Searching the store for `K230`
-returns three products and one of them is that. Meanwhile the actual Kendryte K230 board's SKUs
-are **`K256`, `K256-A`, `K256-B`, `K256-C`** (bare board, band variants) and **`K256-03`,
-`K256-04`, `K256-04-A`, `K277`** (kit variants).
-
-The general rule: **LilyGO stock codes are an opaque letter+number namespace that freely
-collides with chip part numbers.** Never infer silicon from a SKU. Other observed forms include
-region suffixes appended to the same base code — `K230DE` (Europe), `K230US` (United States),
-`K230-ADE`, `K230-AUS` — which encode *warehouse*, not hardware.
-
-### 10.4 ⚠ Wiki reliability — treat as marketing, verify against GitHub
-
-The wiki is useful for orientation and for identifying part numbers that the shop listing omits,
-but during this pass it produced three errors on one product page:
-
-1. **Claimed an ESP32-S3-R8 co-processor** on the T-Display K230 for Wi-Fi/Bluetooth, complete
-   with PlatformIO and Arduino instructions. The board's own BSP contains zero references to any
-   Espressif part; its Wi-Fi is RTL8189FS over SDIO and its Bluetooth is a USB dongle.
-2. **Inverted the K230's core roles** — "big core runs Linux, little core runs RT-Thread" —
-   where Canaan's datasheet says CPU1 (1.6 GHz, big) runs the RTOS and CPU0 (800 MHz, little)
-   runs Linux.
-3. **Headings with no content.** The page has `#schematic` and `#dimension-diagram` headings and
-   **no link or file under either**. This is a soft gap, not a 404, and it will not show up in
-   any link check.
-
-The corresponding GitHub repository (`Xinyuan-LilyGO/<Board-Name>`) was correct on every point
-where the two disagreed. **Default to the repository.**
-
-### 10.5 Repository conventions
-
-- `README.MD` **and** `README_CN.MD` — uppercase `.MD` extension, both maintained. The Chinese
-  file occasionally has content the English one lacks; diff them.
-- `CHANGELOG.MD` / `CHANGELOG_CN.MD` with dated, semantic-versioned entries — this is the best
-  available product timeline for firmware features.
-- `.github/workflows/issues.yaml` and `.github/LilyGo_logo.png` in every repository — a reliable
-  fingerprint for "this is an official LilyGO repository" versus a fork.
-- Accessory silicon gets its **own repository**, named `<Board>-<Chip>`: `T-Display-K230-nRF52840`,
-  `T-Display-K230-nRF9151`. If a board has a companion MCU, look for a sibling repository before
-  concluding the firmware is unpublished.
-- `bsp-patches/` inside the accessory repository duplicates the relevant patch from the main
-  board repository, so the two can drift. Compare them.
-- Default branches vary per repository (`main` vs `master`) even within one product family.
-  Read `.default_branch` from the API. *(Independently corroborates §3.)*
-
-### 10.6 Support channel
-
-LilyGO staff answer publicly and quickly under the account **`u/LilyGoXinyuan`** on
-**r/LilyGO**, typically within a day, and they link to the GitHub repository and wiki when
-users report problems. Observed responses on 2025-03-25, 2025-03-27, 2026-07-28, 2026-08-21 and
-2026-08-25. For a product this new, the subreddit is a better support channel than the wiki and
-is frequently where a specification is first corrected.
-
-### 10.7 Products that produced these findings
-
-- [`devices/lilygo/t-display-k230`](../../devices/lilygo/t-display-k230/README.md)
-- [`components/canaan/k230`](../../components/canaan/k230/README.md) — and its
-  [Canaan vendor guide](../canaan/README.md)
diff --git a/vendors/m5stack/README.md b/vendors/m5stack/README.md
deleted file mode 100644
index 8b5ee65..0000000
--- a/vendors/m5stack/README.md
+++ /dev/null
@@ -1,791 +0,0 @@
-# M5Stack — documentation sourcing guide
-
-Reusable patterns, URL templates and traps for obtaining official M5Stack material.
-Established **2026-09-01** during research on the
-[PaperMono (C153)](../../devices/m5stack/papermono/README.md) and its two custom chips.
-Every technique below was live-verified on that date, with negative controls where noted.
-
-**M5Stack Technology Co., Ltd** (深圳市明栈信息科技有限公司 / Shenzhen Mingzhan
-Information Technology Co., Ltd), Bao'an District, Shenzhen. Site ICP filing
-`粤ICP备16010631号` — that is a **web registration, not a product certification**.
-
-## 1. The good news: the docs site is server-rendered HTML
-
-**`docs.m5stack.com` is not a JavaScript shell.** Plain `curl` plus an HTML-to-text pass
-gets you the complete page — spec tables, pin maps, code blocks, asset URLs, everything.
-
-*Live-verified 2026-09-01:*
-
-```bash
-curl -fsSL -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 \
-  (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36' \
-  https://docs.m5stack.com/en/core/PaperMono -o page.html
-# HTTP 200, Server: nginx/1.24.0 (Ubuntu), Content-Type: text/html; charset=UTF-8
-# 153,939 bytes decoded (32,000 on the wire, brotli)
-# sha256 1f442a2295bcd4f0aa39bbd367d2b167990c4688df7f9993a0e914b34600aa15
-```
-
-**No page required a User-Agent fallback.** `docs.m5stack.com`, `shop.m5stack.com` and
-`burner.m5stack.com` all served 200 to the first request. A browser UA was used
-throughout anyway; plain `curl/8.5.0` also worked on the shop endpoints.
-
-This is worth stating because it is the opposite of several other vendors' portals — see
-[`vendors/seeed-studio`](../seeed-studio/README.md), whose wiki is a Docusaurus SPA that
-returns one link per page.
-
-### 1.1 URL template and slug behaviour
-
-```
-https://docs.m5stack.com/<lang>/<category>/<Product>
-```
-
-| Category | Example |
-|---|---|
-| `core` | `/en/core/PaperMono`, `/en/core/PaperS3`, `/en/core/PaperColor` |
-| `arduino/<product>` | `/en/arduino/papermono/program`, `/en/arduino/papermono/m5pm1_m5ioe1` |
-| `uiflow2/<product>` | `/en/uiflow2/papermono/program` |
-
-**Slugs are forgiving about case, via redirect** — verified 2026-09-01:
-
-| Request | Result |
-|---|---|
-| `/en/core/PaperMono` | **200** |
-| `/en/core/papermono` | **302 → `/en/core/PaperMono`** |
-| `/en/core/papermono-lite`, `/en/core/coreink` | **302** to the CamelCase canonical form |
-| `/en/core/papermono_lite`, `/en/core/PaperMonoLite` | **404** — underscore and concatenated forms do not exist |
-| `/en/core/Paper` | **404** — the original M5Paper has no page at this slug |
-
-So **use `curl -L`**, guess in lowercase, and expect a redirect rather than a match. But
-do **not** assume the *shape* is forgiving: only the canonical hyphenation exists.
-
-Note the inconsistency: product slugs are CamelCase (`/core/PaperMono`) while tutorial
-paths are lowercase (`/arduino/papermono/`). Both are canonical.
-
-### 1.2 Language variants — and why `zh_CN` matters
-
-Three language trees: **`/en/`**, **`/zh_CN/`**, **`/ja/`**.
-
-Verified mechanically across six PaperMono/Lite pages, 2026-09-01:
-
-| Check | Result |
-|---|---|
-| Table-row count | 89 / 89 / 89 — identical |
-| Pin and signal tokens (`G\d+`, `PYG\d+`, `0x..`) | **empty symmetric difference** in all four language pairs, both products |
-| Numeric specs | identical in all three |
-| Asset URL sets | identical **modulo the delta below** |
-
-**The three languages are complete, faithful translations of each other** — including
-faithfully translating the vendor's own factual errors, which is itself the finding.
-
-> ## ⚠ The one substantive delta: `zh_CN` links Chinese-language datasheets the EN and ja pages omit
->
-> | EN / ja page links | `zh_CN` page links instead |
-> |---|---|
-> | `1205/ST25R3916_EN.pdf` | **`1205/ST25R3916_ZH.pdf`** |
-> | `1207/M5PM1_Datasheet_EN.pdf` | **`1207/M5PM1_Datasheet_CN.pdf`** |
-> | `1210/IO_Expander_Datasheet_EN.pdf` | **`1210/IO_Expander_Datasheet_CN.pdf`** |
-> | `472/esp32-s3_datasheet_en.pdf` | `472/esp32-s3_datasheet_cn.pdf` |
->
-> **For M5Stack's own custom chips this is not a convenience, it is the primary source.**
-> The [M5PM1](../../components/m5stack/m5pm1/README.md) and
-> [M5IOE1](../../components/m5stack/m5ioe1/README.md) are M5Stack-designed parts whose
-> only vendor documentation is these datasheets. If the EN edition is ambiguous — and both
-> are internally inconsistent in places — **the CN edition is the second independent copy
-> that can resolve it**, and it may carry material the EN does not.
->
-> **The `ja` pages link the EN datasheets.** There are no JA-localised datasheets.
->
-> **Always fetch a product page in `zh_CN` as well as `en` and diff the asset URL sets.**
-> This is the single highest-value habit in this guide.
-
-*(A related non-finding, recorded so it is not re-investigated: the `zh_CN` package-size
-cell reads `113.2 x 69.6 x21.0mm` — a missing space, a typo, not a spec difference.)*
-
-### 1.3 Per-page PDF renders
-
-Every documentation page has a server-side PDF render:
-
-```
-https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/<lang>/<category>/<Product>.pdf
-```
-
-Live examples, 2026-09-01:
-
-```
-.../static/pdf/static/en/core/PaperMono.pdf
-.../static/pdf/static/zh_CN/core/PaperMono-Lite.pdf
-.../static/pdf/static/ja/core/PaperMono.pdf
-.../static/pdf/static/en/arduino/papermono/m5pm1_m5ioe1.pdf
-.../static/pdf/static/en/uiflow2/papermono/program.pdf
-```
-
-Note the doubled `static/pdf/static/` — that is genuinely the path, not a typo.
-
-These are **large** (the PaperMono one is 15.3 MB, because it embeds every product image)
-and are a *render of the page*, not additional content. Useful as an immutable snapshot of
-what the page said on a given date; not a substitute for fetching the HTML.
-
-## 2. Document hosting — two Aliyun OSS buckets
-
-M5Stack serves documents from **two different Aliyun OSS buckets in Shenzhen**, and they
-are used for different things.
-
-### 2.1 `m5stack-doc.oss-cn-shenzhen.aliyuncs.com/<numeric-product-id>/<file>`
-
-**Product-scoped assets.** The numeric folder is the **product id** in M5Stack's own CMS.
-
-| Product | id |
-|---|---|
-| PaperMono (C153) | **`1267`** |
-| PaperMono-Lite (C153-LITE) | **`1268`** |
-| ST25R3916 (as a "product") | `1205` |
-| M5PM1 | `1207` |
-| M5IOE1 / IO Expander | `1210` |
-| SX1262 | `1177` |
-| RX8130CE | `1132` |
-| ESP32-S3 | `472` |
-
-Everything under a product id, real examples from `1267`:
-
-```
-1267/PaperMono_SCH_V0.6.2_20260522.pdf          schematic, 6 sheets, 1,462,039 B
-1267/PaperMono_SCH_V0.6.2_20260522_page_0N.png  per-sheet PNG renders, N = 1..6
-1267/C153_PaperMono_model_size.pdf              mechanical drawing
-1267/C153_PaperMono_model_size_page_01.png
-1267/EPD_Module_User_Manual.pdf                 the DKE panel manual  <- see section 2.3
-1267/SSD1677.pdf                                controller datasheet (an M5Stack re-export)
-1267/C153_PaperMono_main_pictures_NN.webp       NN = 01..12
-1267/C153_PaperMono_poweron_{EN,CN}.mp4
-1267/C153_C153-Lite_reflash_mode_demo.mp4
-1267/C153_PaperMono_download.gif
-1267/C153-PaperMono-UserDemo_0x00.exe           EasyLoader
-1267/C153-weight.jpg
-```
-
-> ## ⚠ Assets for a variant may live under the *parent* product's folder
->
-> **The PaperMono-Lite's EasyLoader is at `1267/C153-PaperMono-UserDemo_0x00.exe` — under
-> `1267` (PaperMono), not `1268` (Lite).** Both product pages link the identical binary.
->
-> `1268` carries only the Lite's own images, its `PaperMono-Lite_PRJ_V0.6.2_20260522.pdf`
-> project file and its own mechanical drawing.
->
-> **So enumerating a variant's product id alone will under-collect.** Always enumerate the
-> parent product's folder too, and diff. This generalises: for any `-Lite`, `-Plus` or
-> revision variant, check the base product's id.
-
-Naming conventions observed:
-
-- `<SKU>_<Product>_<purpose>.pdf` — `C153_PaperMono_model_size.pdf`
-- `<Product>_SCH_V<x.y.z>_<YYYYMMDD>.pdf` — **`SCH`** for a full schematic
-- `<Product>_PRJ_V<x.y.z>_<YYYYMMDD>.pdf` — **`PRJ`** for a project export. The Lite's is
-  `PRJ` with **4 sheets** where the PaperMono's is `SCH` with **6**. *Different suffix,
-  different sheet count — do not assume a variant's "schematic" is equivalent.*
-- Page renders: `<basename>_page_NN.png`
-- Datasheets: `<PART>_{EN,ZH,CN}.pdf`, `<part>_datasheet_{en,cn}.pdf` — **casing is
-  inconsistent**, and `ZH` and `CN` are both used for Chinese
-
-### 2.2 `m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/...`
-
-**Site-scoped resources** rather than product-scoped:
-
-```
-/resource/docs/static/pdf/static/<lang>/<category>/<Product>.pdf     per-page renders (section 1.3)
-/resource/certification/<SKU>/{CE,FCC,MIC,RoHS,WEEE}/<file>.pdf      certification documents
-```
-
-The certification path is a **predictable template worth probing directly**, because the
-certification index page is unreliable (§5.1). Real examples:
-
-```
-/resource/certification/C123/FCC/FCC-ID.pdf
-/resource/certification/C008-B-V11/MIC/MIC-Certificate.pdf
-/resource/certification/C008-C/RoHS/RoHS-Certificate.pdf
-```
-
-Note `C008-B` and `C008-B-V11` as sibling folders: **hardware revisions get their own
-certification folders.** If a product has revisions, probe `<SKU>-V<rev>` as well.
-
-## 3. Source code and hardware design files
-
-### 3.1 GitHub is a publishing mirror, not the development repo
-
-`github.com/m5stack/*`, MIT-licensed, and consistently the richest source of pin,
-register and address evidence — richer than the documentation.
-
-For the PaperMono, five repositories mattered:
-
-| Repo | What it gives you |
-|---|---|
-| `M5PaperMono-UserDemo` | The factory firmware. A per-peripheral HAL declaring **every pin as a named constant** — the single best pin source |
-| `M5PaperMono-OTP-Demo` | Minimal driver, vendor-recommended over M5GFX |
-| `M5PM1`, `M5IOE1` | Dual Arduino/ESP-IDF drivers whose **headers are exhaustively commented bilingual register maps** — `M5PM1.h` is 136 KB and is effectively the datasheet |
-| `M5Unified`, `M5GFX` | Board autodetect, panel/touch/LED/power classes |
-
-> **Two habits that paid off here:**
->
-> 1. **Read the library header, not just the docs.** `M5PM1.h` and `M5IOE1.h` are
->    bilingual (CN/EN) annotated register maps. For M5Stack's own chips they are more
->    complete and more current than the PDF datasheets.
-> 2. **Check `repos.json` / `dependencies.lock` for pinned commits.** M5Stack's demos
->    **do not vendor** their dependencies — `repos.json` + `fetch_repos.py` clone ten
->    repos at pinned commits and apply local patches. Those pins are often *older* than
->    the current branch heads, which means the shipped firmware is not built from anything
->    you can check out. Diffing the pins against `HEAD` is how the M5GFX waveform
->    replacement was found.
->
-> Both demo repos have **squashed/imported histories (3 commits each)**; the OTP demo's
-> HEAD message is literally `Merge GitLab initial history`. **Development happens on an
-> internal GitLab; GitHub is a publishing mirror, and upstream history is not available.**
-
-Two incidental findings worth carrying forward: the published `M5IOE1` repository contains
-a committed **`.claude/` directory** (agent configuration shipped in a release library),
-and `M5PM1`'s LICENSE is dated **2025** while everything else is 2026 — suggesting the
-PMIC predates the product and is reused.
-
-### 3.2 ⚠ `M5_Hardware` does not contain everything, and absence there proves nothing
-
-`github.com/m5stack/M5_Hardware` is M5Stack's hardware design-file repository
-(`Products/<SKU>_<Name>/`, plus `KiCad` and `Common` libraries). The docs footer links it
-as "Hardware Design Files".
-
-**Verified `executed-success` at HEAD `a240115c94b19ecf647f229c47fa9a8ce46ccdc4`, pushed
-2026-08-17:**
-
-```bash
-git clone --filter=blob:none --no-checkout https://github.com/m5stack/M5_Hardware.git
-git -C M5_Hardware ls-tree -r --name-only HEAD | grep -iE 'papermono|c153'   # -> 0 matches
-git -C M5_Hardware ls-tree -r --name-only HEAD | grep -oE 'C1[0-9]{2}' | sort -u | tail
-#   ... C149 C151 C152
-```
-
-**The product tree stops at C152 (`C152_StopWatch`) and contains no C153 entry.** The only
-Paper-family entries are `C139_PaperS3`, `C151_PaperColor` and `K049-B_Paper_v1.1`.
-
-The repository was pushed **2026-08-17**, *after* the PaperMono's 2026-08-10 firmware
-commit, so this is not simply publishing lag.
-
-> **The lesson generalises: absence from `M5_Hardware` does not mean a schematic was not
-> published.** The PaperMono's schematic exists — it is linked directly from the product
-> page and served from the OSS bucket (§2.1). **Check the product page's own asset list
-> before concluding a design file does not exist.**
->
-> Consequence when it *is* absent: there is **no machine-readable netlist** to validate a
-> pin map against, and the firmware becomes the primary machine-readable evidence. Clone
-> blobless (`--filter=blob:none --no-checkout`) — the full repo is ~128 MB and you only
-> need the tree.
-
-## 4. The M5Burner firmware API
-
-Firmware pages at `burner.m5stack.com/firmware/<id>/` are **React SPA shells** with an
-empty `<div id="root">` — a plain fetch gets you ~3 KB and the `og:` meta tags, nothing
-else. The `og:` tags are still useful: they revealed that the link labelled *"PaperMono
-Factory Reset Firmware"* is actually **"PaperMono UserDemo"**.
-
-The real content is behind a **public JSON API**, recovered by reversing the SPA bundle:
-
-```js
-var Kn = `${`/api`.replace(/\/$/,``)}/v1`      // assets/http-ChO34QIa.js
-```
-
-> ## ⚠ `/api/v1/…` is public; `/api/…` is not
->
-> | Endpoint | Result (2026-09-01) |
-> |---|---|
-> | `burner.m5stack.com/api/firmwares/{id}` | **HTTP 401** `{"msg":"请先登录"}` — "please log in first" |
-> | **`burner.m5stack.com/api/v1/firmwares/{id}`** | **HTTP 200, full JSON, no auth** |
->
-> The `/v1` segment is the whole difference. Getting a 401 here does **not** mean the
-> resource is private.
-
-Working sequence:
-
-```bash
-ID=2089640807996628993                       # PaperMono UserDemo
-curl -fsSL "https://burner.m5stack.com/api/v1/firmwares/$ID"                 # detail
-curl -fsSL "https://burner.m5stack.com/api/v1/firmwares/$ID/versions"        # version list
-curl -fsSLo fw.bin "https://burner.m5stack.com/api/v1/firmwares/$ID/versions/$VID/download"
-```
-
-The detail JSON carries `firmwareName`, `firmwareDescription`, `sourceType`
-(`OFFICIAL` / `COMMUNITY`), `developer` (with `userId`), `currentVersion`,
-`supportedDevices`, `statistics.downloadCount` and `uploadedAt` — enough to tell an
-official image from a community one and to date it.
-
-> ## ⚠ The download 302s to a CDN object named by a numeric id, not by `binFileName`
->
-> ```
-> https://m5burner-cdn.m5stack.com/community/{userId}/{firmwareId}/{versionId}/bin/{versionId+1}.bin
-> ```
->
-> The API reports a human-readable `binFileName` such as
-> `C153-PaperMono-ESP32S3R8-UserDemo-V1.2-yaozhenquan-8300e309-20260806_0x00.bin`, and
-> **that string does not appear in the URL you are redirected to.** Follow the redirect
-> (`curl -L`) and rename locally from `binFileName`; do not try to construct the CDN URL
-> from the filename.
->
-> Note also that **official images live under `/community/1/…`** — `userId` 1 is
-> `m5stack` itself. The path segment says nothing about provenance; `sourceType` does.
-
-**Validate downloads by content, not by extension.** Both images retrieved this way were
-checked for HTTP 200, ≥ 4 KiB, first byte `0xE9` (ESP32 image magic) and no HTML/XML in
-the first 512 bytes before being given a `.bin` extension.
-
-Parsing the image afterwards is worth the trouble: `esp_app_desc_t` at `0x10020` yields
-`project_name`, `app_version`, `build_date`/`time` and `idf_version`. That is how the
-PaperMono factory image was found to report **`c78f6c5-dirty`** — built from an
-uncommitted tree, therefore not reproducible from any published commit.
-
-## 5. Traps
-
-### 5.1 ⚠ Soft gaps: `/en/certification` and `/en/product_i2c_addr` return 200 with zero matches
-
-These two site-wide reference pages are **incomplete**, and they fail *silently* — HTTP
-200, full valid content, other products present, your product simply absent.
-
-| Page | Bytes | PaperMono / C153 matches |
-|---|---:|---|
-| `docs.m5stack.com/en/certification` | 382,669 | **0** |
-| `docs.m5stack.com/en/product_i2c_addr` | 312,908 | **0** |
-
-The second is remarkable: the PaperMono carries **seven** documented I²C devices and
-appears in neither the table nor its index.
-
-**These are soft *gaps*, not soft 404s.** The page is real, complete and correctly served;
-the product is missing from it. Distinguish the two, because the response looks identical:
-
-- **Soft 404** → the page is a generic template standing in for something that does not
-  exist.
-- **Soft gap** → the page is genuine and other products *are* present; yours is not.
-
-The test is a **positive control**: search the same page for a product you know is listed.
-Here, `/en/product_i2c_addr` *does* list `M5PM1 (0x6e)` for **StickS3 (K150)** — which
-both proved the page was intact and independently corroborated the M5PM1's address.
-
-**Never report "no certification found" without that control.** With it, "no FCC/CE/TELEC
-identifier is published for this product" becomes a **verified negative** rather than a
-failed search — which is exactly what it is for the PaperMono.
-
-### 5.2 ⚠ Shop 404s have a different hash every time — hash-based detection fails
-
-`shop.m5stack.com` is Shopify. Guessed product handles return a **generic 404 template**:
-
-| Probe | HTTP | Bytes | SHA-256 |
-|---|---:|---:|---|
-| `/products/papermono` | 404 | **389,759** | `b363da8d68a78dd8…` |
-| `/products/m5stack-papermono` | 404 | **389,759** | `0856732748738d0a…` |
-| `/products/papermono-lite` | 404 | **389,759** | `b5e831b296344a44…` |
-
-**Exactly 389,759 bytes each — and three different hashes.** The template carries a
-per-request nonce. So:
-
-- **Hash-based 404 detection does not work here.** Neither does content-length alone, at
-  least not as a *positive* identifier without a known-404 baseline.
-- The HTTP status is correct (404), so **trust the status code** — the trap is only for
-  tooling that ignores status and fingerprints bodies.
-
-**Handles are not guessable.** The real ones bear no resemblance to the product name:
-
-```
-shop.m5stack.com/products/m5papermono-with-lora-nfc-800x480-3-97-eink-display
-shop.m5stack.com/products/papermono-lite-dev-kit-800x480-3-97-e-ink-display
-```
-
-**Use search instead of guessing:**
-
-```bash
-curl -fsSL 'https://shop.m5stack.com/search?q=papermono'
-curl -fsSL 'https://shop.m5stack.com/search/suggest.json?q=papermono&resources[type]=product&resources[limit]=10'
-```
-
-The `suggest.json` endpoint works with plain `curl/8.5.0`, returns both SKUs with prices
-and `available` flags, and is far cheaper than the 448 KB HTML search page.
-
-Once you have a handle, **append `.json`** for structured Shopify data — SKU, price,
-`created_at`, `published_at`, `updated_at`, variants, barcode, weight:
-
-```bash
-curl -fsSL 'https://shop.m5stack.com/products/<handle>.json'
-```
-
-That is how three distinct "launch" dates were disentangled for the PaperMono: Shopify
-`created_at` 2026-08-18 (internal record), `docs.m5stack.com/en/history` 2026-08-20
-(documentation release), Shopify `published_at` + blog `<time datetime>` 2026-08-21
-(public availability). **They do not mean the same thing.**
-
-### 5.3 ⚠ `community.m5stack.com` is auth-walled
-
-M5Stack's own NodeBB forum — where owner reports appear first — is **not searchable
-unauthenticated**:
-
-| Endpoint | Result (2026-09-01) |
-|---|---|
-| `/api/search?term=<q>&in=titlesposts` | **401** `{"code":"not-authorised"}` |
-| `/search?term=<q>` | **302** to login |
-| **`/api/recent`** | **200**, open — returned 198 topics |
-
-`/api/recent` is the only open window and only covers a recent slice. **A negative result
-from the vendor forum is therefore "no determination possible", not "nothing exists"** —
-say so explicitly rather than implying an absence you did not establish.
-
-### 5.4 Documentation contradicts itself; expect it and record both sides
-
-M5Stack's pages for one product routinely disagree. On the PaperMono, ten distinct
-contradictions were found *within vendor material*, including:
-
-- Prose says an interrupt is active-high; the code on the **same page** sets
-  `BMI2_INT_ACTIVE_LOW`.
-- One tutorial page names a *"reset button on the side"* that does not exist on the
-  schematic; two other pages and the spec table say power button.
-- One page requires a library the other page's build config omits.
-- A hazard note (the charger's I²C gate) appears **only** on the product page and not on
-  the dedicated power-management page most likely to be read.
-- A link labelled "Factory Reset Firmware" resolves to a record named "UserDemo".
-
-**And the contradictions are faithfully translated into all three languages** — they are
-defects in the source content, not translation errors, so a second language does not
-arbitrate them.
-
-**Practical rule:** when vendor prose and vendor code disagree, **the code and the shipped
-binary win**. Both were decisive here.
-
-### 5.5 Mirrored third-party datasheets are not necessarily current
-
-M5Stack mirrors other manufacturers' datasheets under its own product ids (§2.1). Those
-mirrors are **not** guaranteed to be the current revision, and sometimes not even a clean
-copy:
-
-- The mirrored **BMI270** datasheet is **five years behind Bosch's** current revision.
-- The mirrored **SSD1677** PDF has 46 pages but numbers itself `n/47`, its PDF Producer is
-  **`PDFill`** rather than a Solomon Systech export, and it is marked *"Advance
-  Information", Rev 1.0, Nov 2018*. Treat as a re-processed copy of a preliminary
-  document.
-- The **RX8130CE** register datasheet is mirrored **only in Chinese**.
-- The **DKE panel manual** has **no text layer at all** — see
-  [`vendors/dke`](../dke/README.md).
-
-**Always prefer the original manufacturer's copy, and hash both.** Keep the M5Stack mirror
-anyway when it is the only accessible copy, and **label it as a mirror in the filename**.
-
-## 6. Document-class checklist
-
-Work through this per product; each line names where it is likely to live.
-
-| Class | Where | PaperMono result |
-|---|---|---|
-| Product page (spec table, PinMap, precautions) | `docs.m5stack.com/<lang>/core/<Product>` | ✅ |
-| **The same page in `zh_CN`** — for CN-only datasheet links | `/zh_CN/core/<Product>` | ✅ **found 4 CN-only datasheets** |
-| Arduino quick-start | `/en/arduino/<product>/program` | ✅ |
-| Per-feature Arduino API sub-pages | linked from the quick-start | ⚠ **14 enumerated, none fetched** |
-| Product-specific tutorial pages | `/en/arduino/<product>/<topic>` | ✅ `m5pm1_m5ioe1` |
-| UiFlow2 page | `/en/uiflow2/<product>/program` | ✅ but **empty of substance** |
-| Schematic | product page asset list → OSS `<id>/…_SCH_…pdf` | ✅ |
-| Mechanical drawing | OSS `<id>/…_model_size.pdf` | ✅ |
-| Component datasheets | product page "Datasheets" section | ✅ 7 listed |
-| Hardware design files (EDA source) | `github.com/m5stack/M5_Hardware` | ❌ **no C153 entry** (§3.2) |
-| Factory firmware source | `github.com/m5stack/<Product>-UserDemo` | ✅ |
-| Factory firmware binary | M5Burner API (§4) | ✅ |
-| EasyLoader | OSS `<id>/…_0x00.exe` — **check the parent id** | ✅ under `1267` |
-| Release date | `docs.m5stack.com/en/history` | ✅ 2026-08-20 |
-| SKU / price / stock | `shop.m5stack.com/search/suggest.json` then `<handle>.json` | ✅ |
-| Product index (all SKUs, variants) | `/en/products` | ✅ confirmed exactly two SKUs |
-| **Certification** | `/en/certification` **+ positive control** (§5.1), and probe `/resource/certification/<SKU>/…` | ❌ **verified absent** |
-| **I²C address table** | `/en/product_i2c_addr` **+ positive control** | ❌ **verified absent** |
-| Launch announcement | `shop.m5stack.com/blogs/news/…` | ✅ |
-| Community reports | `community.m5stack.com` — **auth-walled** (§5.3) | ⚠ no determination |
-
-## 7. Per-product procedure
-
-1. **Fetch the product page in `en` *and* `zh_CN`** (and `ja` if you want the third
-   control). Use `curl -L`; lowercase slugs 302 to CamelCase.
-2. **Extract every absolute URL from all language variants and diff the sets.** The CN
-   delta is where vendor-only Chinese datasheets appear (§1.2).
-3. **Note the numeric product id** from the OSS asset URLs. **Also enumerate the parent
-   product's id** if this is a `-Lite` / variant SKU (§2.1).
-4. Download the schematic, mechanical drawing and every listed datasheet. **Hash
-   everything.** Label mirrors as mirrors.
-5. **Check the schematic PDF for concatenated sub-documents** — the PaperMono's six
-   "sheets" are three separate Altium projects with restarting reference designators, and
-   one sub-document is missing its sheet 1 of 2.
-6. Clone the `-UserDemo` and any `-Demo` repositories. **Read the HAL headers for pins,
-   the library headers for registers, and `repos.json`/`dependencies.lock` for pinned
-   dependency commits.**
-7. **Diff the pinned dependency commits against current branch heads.** Divergence there
-   is a real finding about what the shipped firmware actually is.
-8. Pull the firmware binary via the M5Burner **`/api/v1`** endpoint (§4). Validate by
-   content. Parse `esp_app_desc_t` and the partition table.
-9. Check `M5_Hardware` for EDA source — and **do not conclude anything from its absence**
-   (§3.2).
-10. Check `/en/certification` and `/en/product_i2c_addr` **with a positive control** (§5.1).
-11. Get SKU/price/stock from `search/suggest.json` → `<handle>.json`. Never guess handles
-    (§5.2).
-12. **Record contradictions rather than picking a value.** When prose and code disagree,
-    the code and the shipped binary win — but write down both.
-
-## 8. Rights and licensing observations
-
-| Material | Terms |
-|---|---|
-| **Source repositories** | **MIT**, "Copyright (c) 2026 M5Stack Technology CO LTD" (M5PM1's says 2025). `SPDX-License-Identifier: MIT` in file headers |
-| Schematics and mechanical drawings | **No stated licence.** Published openly on the product page; redistribution status `unknown` |
-| M5Stack-authored datasheets (M5PM1, M5IOE1) | Published by *Shenzhen Mingzhan Information Technology Co., Ltd*. No licence statement |
-| **Mirrored third-party datasheets** | **Keep their original manufacturers' terms.** Rehosting by M5Stack does not relicense them |
-| Firmware binaries | No stated terms; retrievable from a public API |
-| Product imagery | **Not licensed for redistribution.** This is why no product photograph is retained in the PaperMono record |
-| Documentation prose | Marketing copy; no stated licence |
-| ⚠ Bundled third-party code | **Check upstream licences separately.** The MIT-licensed PaperMono demo pins **RadioLib**, which is **LGPL-3.0 upstream**. Flagged, not resolved |
-
-## 9. Products documented with this guide
-
-- [**M5Stack PaperMono (C153)**](../../devices/m5stack/papermono/README.md) — the pass that
-  produced these findings
-- M5Stack PaperMono-Lite (C153-LITE) — covered inside the PaperMono record as a variant;
-  it has no record of its own at the snapshot date
-- [**M5PM1**](../../components/m5stack/m5pm1/README.md) — custom power manager; the
-  bilingual library header and the CN-only datasheet delta both came from this part
-- [**M5IOE1**](../../components/m5stack/m5ioe1/README.md) — custom I/O expander; likewise
-- [Stamp-LoRa-1262](../../components/m5stack/stamp-lora-1262/README.md) — the module for
-  which **no vendor datasheet exists at all**, a useful negative
-
-Related vendor guide: [`vendors/dke`](../dke/README.md) — for the e-paper panel manual
-M5Stack mirrors, which has its own retrieval trap.
-
-## 10. Change log
-
-| Date | Change |
-|---|---|
-| 2026-09-01 | Guide created during the PaperMono (C153) pass. Established: `docs.m5stack.com` is server-rendered HTML (not an SPA); lowercase slugs 302 to CamelCase while underscore/concatenated forms 404; the three language trees are faithful translations **except** that `zh_CN` links CN-only datasheets for M5Stack's own custom chips; the two OSS buckets and the numeric-product-id scheme (PaperMono = `1267`), including variant assets living under the parent id; the `static/pdf/static/<lang>/…` per-page renders; the M5Burner `/api/v1` public API versus the 401 on `/api`, and the numeric CDN object name that does not match `binFileName`; `M5_Hardware` stops at C152 with no C153 entry as of 2026-08-17, so absence there proves nothing; `/en/certification` and `/en/product_i2c_addr` are soft **gaps** requiring a positive control; Shopify 404s are 389,759 bytes with a **per-request hash**, defeating hash-based detection; `community.m5stack.com` search is 401 auth-walled. |
-
----
-
-## 11. Findings added by the DinMeter (K134 / K134-V11) pass — 2026-09-04
-
-*Appended 2026-09-04. Nothing above was altered. Everything below was live-probed on that date,
-with negative controls, during the pass that produced
-[`devices/m5stack/dinmeter`](../../devices/m5stack/dinmeter/README.md) and
-[`devices/m5stack/dinmeter-v1.1`](../../devices/m5stack/dinmeter-v1.1/README.md).*
-
-### 11.1 ⚠ The single biggest trap: M5Stack re-serves old assets under new product names
-
-**Hash every artifact at acquisition time. This trap is invisible any other way.**
-
-| Asset | v1.0 URL | v1.1 URL | SHA-256 |
-|---|---|---|---|
-| DinMeter schematic | `…/500/DIN_Meter_v1.0.pdf` | `…/1211/K134-V11_DIN_Meter_v1.0_2025_11_25_17_15_58.pdf` | **identical** `03ec3353…6e4c070` |
-| DinMeter structure STL | `Products/K134_DinMeter/…/DinMeter.stl` | `Products/K134-V11_DinMeter_v1.1/…/DinMeter_v1.1.stl` | **identical** `90f04d6a…` |
-| Stamp structure STL | `Products/S007_Stamp-S3/…/Stamp-S3.stl` | `Products/S007-V033_Stamp-S3A/…/Stamp-S3A.stl` | **identical** `f72c1af2…` |
-| DinMeter dimension drawing | `…/1211/K134-din_meter_asm_v1.pdf` | **the same URL** | — |
-
-Three different products, two different SKUs each, and in every case the same bytes. Note the
-v1.1 schematic's own filename contains `_v1.0_`.
-
-**What it licenses you to conclude:** the vendor has published no revision-specific
-documentation. **Not** that the hardware is unchanged.
-
-**Method:** `sha256sum` everything on download, and diff hashes across revision pairs *before*
-writing anything. Two `sha256sum` invocations produced three of that pass's central findings.
-
-### 11.2 ⚠ `m5stack-doc` bucket paths are numeric product ids — and they are not the SKU
-
-`https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/<numeric-id>/<filename>`
-
-Observed ids: DinMeter v1.0 schematic `500`; DinMeter v1.1 + dimensions `1211`; Stamp-S3
-schematic `522`; Stamp-S3A `1150`; Stamp-S3A 1.27-pin variant `686`; Stamp-S3 pin map `684`;
-ESP32-S3 datasheet mirror `472`.
-
-Consistent with §2's PaperMono `1267`. **Variant assets do not always live under the parent id**
-here: Stamp-S3A base is `1150` while its 1.27-pin variant is `686`. Read the ids off the rendered
-page rather than guessing.
-
-### 11.3 Product-page id patterns — verified, with negative controls
-
-| Probe | Result |
-|---|---|
-| `/en/core/M5DinMeter` | **200** ← the v1.0 page |
-| `/en/core/DinMeter` | **404** ← the obvious guess is wrong |
-| `/en/core/DinMeter_v1.1` | **200** ← the v1.1 page uses a *different* naming convention from v1.0 |
-| `/en/core/StampS3` | **200** |
-| `/en/stamp/StampS3` | **404** |
-| `/en/stamp/{Stamp-S3A,M5StampS3,stamps3,StampS3A}` | **404** ×4 |
-| `/en/core/Stamp-S3A` | **200** |
-
-**Two lessons.** (1) Core modules live under `/en/core/`, **not** `/en/stamp/` — despite
-`/en/stamp/` existing and hosting other Stamp products. (2) M5Stack does **not** use one naming
-convention per product family: `M5DinMeter` for v1.0 but `DinMeter_v1.1` for v1.1, `StampS3` but
-`Stamp-S3A`. **Do not guess a page id. Use the sitemap (§11.4).**
-
-### 11.4 ✅ `sitemap.xml` is the reliable enumeration route — the `/en/products` index is not
-
-| Probe | Result |
-|---|---|
-| `https://docs.m5stack.com/sitemap.xml` | **200**, 499 000 B, **5 703 `<loc>` entries** |
-| `https://docs.m5stack.com/en/sitemap.xml` | **404** |
-| `https://docs.m5stack.com/sitemap_index.xml` | **404** |
-| `https://docs.m5stack.com/en/products` | **200**, 565 615 B — but a **JavaScript shell** containing **no product links** in the served HTML |
-
-The `/en/products` index that appears to list every product is useless to a fetcher. The
-sitemap has everything.
-
-```bash
-curl -sS -A "$UA" https://docs.m5stack.com/sitemap.xml \
-| grep -o '<loc>[^<]*</loc>' | sed 's/<[^>]*>//g' | grep -i '<product-name>'
-```
-Filtering for `Din` returned **6** URLs and immediately exposed the two page-id conventions plus
-the 9 `/en/arduino/m5dinmeter/*` tutorial pages and 1 `/en/uiflow2/m5dinmeter/program`.
-
-### 11.5 ✅ Product-page content *is* in the served HTML — but only from `id="document"`
-
-Consistent with §1. The pages are Nuxt/Vue shells whose content is nonetheless server-rendered
-inside a `<div id="document">`. Naive tag-stripping over the whole document yields ~5 KB of
-navigation chrome and loses the specification table.
-
-**Slice from the anchor first**, then strip:
-```python
-i = raw.find('id="document"'); seg = raw[i:] if i > 0 else raw
-seg = re.sub(r'(?is)<script\b.*?</script>', ' ', seg)
-seg = re.sub(r'(?i)</(p|div|tr|li|h[1-6]|table|td|th)>', '\n', seg)
-seg = html.unescape(re.sub(r'(?s)<[^>]+>', '', seg))
-```
-This recovered the complete specification table, PinMap, Learn sections, datasheet list and
-product-comparison table from both DinMeter pages.
-
-### 11.6 ✅ Per-page printable renders — path template confirmed on a second product family
-
-`https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/static/pdf/static/<lang>/<section>/<PageId>.pdf`
-
-Verified: `…/static/en/core/M5DinMeter.pdf` (200, 7 459 888 B) and
-`…/static/en/core/DinMeter_v1.1.pdf` (200, 11 261 000 B). `<PageId>` is the **page id**, not the
-SKU or the product name — so §11.3's naming inconsistency propagates here.
-
-⚠ **These are re-rendered per request**, so the bytes are not stable across fetches even when the
-content is. Do not use their hash as a change detector.
-
-### 11.7 ⚠ Chip datasheets are filed under *product* paths
-
-`https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/M5DinMeter/tp4057.pdf`
-
-The TP4057 is a chip, not a DinMeter part — yet M5Stack files its datasheet under the board's
-directory. Likewise the DinMeter's DC-terminal and battery-socket datasheets are served from
-**`…/products/core/M5Dial/…`**, a *different product's* path.
-
-**Consequences for a fetcher:** (a) a chip datasheet may only exist under some unrelated board's
-directory, so search the rendered page's links rather than guessing a `datasheet/` path; (b) when
-filing locally, ignore the vendor's path and file by **what the document describes**.
-
-Also confirmed: the Stamp-S3A page links `…/datasheet/Stamp/**S007 StampS3**/MUN3CAD01-SC.pdf`
-— the *predecessor's* directory — and that part is not on the Stamp-S3A schematic at all (§11.9).
-
-### 11.8 ⚠ Shopify serves JPEG bytes under `.webp` URLs
-
-`https://cdn.shopify.com/s/files/…/1_3a27efc4-….webp?v=1769738162` returns bytes beginning
-`ff d8 ff e1 … Exif` — **JPEG**. Shopify content-negotiates the image format and ignores the
-path extension.
-
-**Validate by magic bytes, never by URL suffix**, and rename locally so the extension matches the
-content. Four of four shop images in that pass were affected.
-
-### 11.9 ⚠ Specification rows are carried over unedited between product generations
-
-The Stamp-S3A page lists `DC-DC: MUN3CAD01-SC`. The string `MUN3CAD01` **does not occur anywhere**
-in `Sch_StampS3_v0.3.3.pdf`; the designator `M2` is absent; the fitted part is an 8-ball buck with
-`SW`/`VOS`/`VSEL1-3` and an external inductor, annotated `IOUT: 0~0.6A`.
-
-Similarly, the Stamp-S3A's `26.0 × 18.0 × 4.7 mm` size contradicts a **byte-identical** STL and
-the complete absence of a new KiCad footprint.
-
-**Rule: treat M5Stack specification tables as marketing copy that lags the hardware. Where a
-schematic exists, the schematic wins.** Cross-check every consequential row.
-
-### 11.10 ✅ Shop `.js` JSON is the best source for SKU, price, lifecycle and launch date
-
-`https://shop.m5stack.com/products/<slug>.js` returns Shopify's product JSON directly — far more
-reliable than parsing the storefront, and it avoids §5's 389 kB-per-request-hash 404 problem.
-
-Gives: `title`, `variants[].sku`, `price` (integer cents), `available`, `created_at`,
-`published_at`, `tags`, `weight`, product and variant ids.
-
-**Two high-value behaviours:**
-- **M5Stack prefixes discontinued titles with `[EOL]`.** `"[EOL] M5Stack Din Meter w/ M5StampS3"`,
-  `"[EOL] M5Stamp ESP32S3 Module"`. This is the cleanest lifecycle signal the vendor emits
-  anywhere — it appears on **no documentation page**.
-- **`published_at` is a usable launch-date proxy**, and it cross-checked exactly against an
-  independent r/M5Stack announcement post for the DinMeter v1.1 (both 2026-01-30).
-
-⚠ **Slugs are not predictable.** v1.0 is `m5stack-din-meter-**w**-m5stamps3`; v1.1 is
-`m5stack-din-meter-v1-1-**with**-m5stamps3a`. `…-with-m5stamps3` **404s**. The working v1.0 slug
-was recovered from a third-party README (`bmorcelli/Launcher`), not from M5Stack.
-
-**Enumerate slugs instead of guessing**, with the brackets percent-encoded:
-```bash
-curl -sS -A "$UA" 'https://shop.m5stack.com/search/suggest.json?q=din+meter&resources%5Btype%5D=product&resources%5Blimit%5D=10'
-```
-A raw `[` makes curl fail with `curl: (3) bad range in position 70`.
-
-### 11.11 ✅ Altium marker layer in M5Stack schematics — and its double-draw trap
-
-M5Stack publishes Altium PDFs carrying an invisible marker layer (`CO<designator>`,
-`PI<designator><pin>`, `NL<netname>`), which makes a full netlist recoverable. This was already
-used for PaperMono; two additions from this pass:
-
-1. **Altium draws the marker layer twice at identical coordinates.** Without glyph deduplication
-   the two copies interleave and `PIJ10101` extracts as `PPIIJJ110011` — *human-legible and
-   wrong*, the most dangerous kind of extraction failure. **Deduplicate on rounded
-   `(x0, y0, x1, y1, char)` before grouping glyphs into words.**
-2. **On a host with no poppler**, `pdfminer.six` (pure Python) works and can emit
-   `pdftotext -bbox`-compatible XML. `pymupdf` installs but fails to import on NixOS
-   (`libstdc++.so.6` missing).
-
-Reusable parser:
-[`devices/m5stack/dinmeter/artifacts/schematic/parse_dinmeter_sch.py`](../../devices/m5stack/dinmeter/artifacts/schematic/parse_dinmeter_sch.py).
-
-### 11.12 ✅ `m5stack/M5_Hardware` — enumerate the tree; absence is informative
-
-```bash
-curl -sS -H "Authorization: Bearer $(gh auth token)" \
-  'https://api.github.com/repos/m5stack/M5_Hardware/git/trees/master?recursive=1'
-```
-931 paths, **not truncated**, one call. Directory naming is `Products/<SKU>_<ProductName>/`, e.g.
-`Products/K134_DinMeter/`, `Products/K134-V11_DinMeter_v1.1/`, `Products/S007-V033_Stamp-S3A/`.
-
-Contrary to §3's PaperMono finding that the repo stops at C152: **it does carry DinMeter and
-Stamp entries**, so its coverage is patchy by product rather than by date. Check, do not assume.
-
-Most products get **only** `Structures/*.stl`. KiCad footprints exist for a *subset*
-(`Stamp-S3-SMD`, `Stamp-S3-DIP`, `Stamp-S3_PIN1.27_Socket`, `Stamp-S3_PIN2.54_DIP`) — and
-notably **no `Stamp-S3A` footprint at all**, which is itself evidence for footprint compatibility.
-The repository has **no `LICENSE` file** (checked 2026-09-04).
-
-### 11.13 ✅ Espressif's `esp-board-manager` is a better technical source than M5Stack's own docs
-
-`espressif/esp-board-manager` → `m5stack_boards/<board>/{board_info,board_devices,board_peripherals}.yaml`.
-For the DinMeter it documented the ST7789 GRAM offset, the PCNT quadrature pattern, an
-ESP32-S3-specific build break, and resolved an ambiguity in M5Stack's own pin table by citing
-M5Unified source — none of which appears in M5Stack's documentation.
-
-**Check it for every M5Stack board.** Caveat: its headers cite M5Stack's PinMap as its source, so
-where it merely restates that table it is a *reproduction*, not independent corroboration.
-
-### 11.14 ⚠ `community.m5stack.com` remains auth-walled — confirmed again
-
-| Probe | Result |
-|---|---|
-| `…/api/search?term=<x>&in=titlesposts` | **HTTP 401** — `{"status":{"code":"not-authorised",…}}` |
-| `…/search?term=<x>&in=titlesposts` (browser UA) | **200**, but a NodeBB **JS shell** with no results in the served HTML |
-
-Independently confirms §5. **Rotating User-Agents must not be attempted** — this is
-authentication, not bot-blocking, and the repository's retrieval policy forbids UA substitution
-to bypass access controls. Treat M5Stack forum threads as a **blocked** source and say so.
-
-### 11.15 Products documented with these additions
-
-- [**M5Stack DinMeter (K134)**](../../devices/m5stack/dinmeter/README.md)
-- [**M5Stack DinMeter v1.1 (K134-V11)**](../../devices/m5stack/dinmeter-v1.1/README.md)
-- [**Stamp-S3 (S007)**](../../components/m5stack/stamp-s3/README.md) and
-  [**Stamp-S3A (S007-V033)**](../../components/m5stack/stamp-s3a/README.md) — the pair that
-  produced §11.1, §11.9 and §11.12
-
-### 11.16 Change log addendum
-
-| Date | Change |
-|---|---|
-| 2026-09-04 | Appended §11 during the DinMeter (K134 / K134-V11) pass. New: the re-served-asset trap and the hash-everything rule; `m5stack-doc` numeric ids for six more products; page-id naming is inconsistent *within* a product family, with `/en/stamp/` 404 negative controls; `sitemap.xml` works while `/en/products` is a link-free JS shell; the `id="document"` slicing recipe; per-page PDF renders confirmed on a second family and shown to be non-byte-stable; chip datasheets filed under unrelated *product* paths; Shopify serving JPEG under `.webp`; specification rows carried over unedited between generations; shop `.js` as the lifecycle source with the **`[EOL]` title prefix** and unpredictable slugs; the Altium **double-draw** glyph trap and the `pdfminer.six`-on-NixOS workaround; `M5_Hardware` coverage patchy by product, not by date, and no `Stamp-S3A` footprint; `esp-board-manager` as a superior technical source; forum 401 re-confirmed. |
diff --git a/vendors/omnivision/README.md b/vendors/omnivision/README.md
index 197b393..dcc168f 100644
--- a/vendors/omnivision/README.md
+++ b/vendors/omnivision/README.md
@@ -66,7 +66,7 @@ In practice, documents come from these sources, in rough order of reliability:
 
 **Application notes carry the interesting material.** The OV5640 *datasheet* documents the register block layout; the *Auto Focus Application Notes* documents the entire AF command protocol (`0x3022`/`0x3023`/`0x3029`) without which autofocus is unimplementable. Always search for `<PART>_Software_Application_Notes`, `<PART>_app_note`, `<PART> Camera Module Application Notes` in addition to the datasheet.
 
-**The document states a redistribution limitation.** The OV3660 and OV5640 datasheets state: *"Individuals and/or organizations are not allowed to re-distribute said information."* The OV5640 AF application note is stamped **"Company Confidential / OmniVision Confidential for BYD Only"** on every page. These documents circulate freely via module vendors, but that is not a licence. Record them as redistribution status **`restricted`/`unknown`** and flag them for user review rather than staging them casually. Extracting *facts* (register addresses, values, timings) into an authored record is a different act from redistributing the document, and is what this repository does.
+**Redistribution is explicitly restricted.** The OV3660 and OV5640 datasheets state: *"Individuals and/or organizations are not allowed to re-distribute said information."* The OV5640 AF application note is stamped **"Company Confidential / OmniVision Confidential for BYD Only"** on every page. These documents circulate freely via module vendors, but that is not a licence. Record them as redistribution status **`prohibited`/`unknown`** and flag them for user review rather than staging them casually. Extracting *facts* (register addresses, values, timings) into an authored record is a different act from redistributing the document, and is what this repository does.
 
 **Typos propagate.** OmniVision's own OV5640 AF application note refers to *"the built-in micro-controller of OV5647"* — a different sensor. Downstream, Seeed's OV5640 autofocus library unpacks to a directory named `OV5647_AF-main`. Do not conclude you fetched the wrong part; check the file contents.
 
@@ -118,7 +118,7 @@ Recurring across OmniVision material:
 - No licence file, no permissive grant, no public terms of use
 - Module-vendor mirrors do not add a licence; hosting is not permission
 
-Note OmniVision PDFs as `redistribution: restricted` or `unknown` and keep them in the repository. The documents are scarce and several of their source URLs already 404, so having a copy is the point. Facts extracted into authored records are fine; wholesale reproduction is not.
+Treat every OmniVision PDF as **`redistribution: prohibited` or `unknown`**, disposition `repository (unstaged)` pending user review. Facts extracted into authored records are fine; wholesale reproduction is not.
 
 ---
 
diff --git a/vendors/semtech/README.md b/vendors/semtech/README.md
deleted file mode 100644
index c1b1c85..0000000
--- a/vendors/semtech/README.md
+++ /dev/null
@@ -1,663 +0,0 @@
-# Semtech — documentation sourcing guide
-
-Reusable, cross-device knowledge for obtaining official Semtech documentation for **any** Semtech
-part. Written and verified **2026-09-04** while researching the
-[LR2021](../../components/semtech/lr2021/README.md) and the
-[LoRa generation lineage](../../guides/hardware/lora-radio-generations.md), building on the
-unresolved sourcing notes left in [`components/semtech/sx1262/README.md` §11](../../components/semtech/sx1262/README.md).
-
-Every URL pattern and every claim about what does and does not resolve was checked live with `curl`
-on the date given, **including negative controls** — a path that should not exist, probed alongside
-one that should, so that "200" can be distinguished from "200 that means nothing". Where behaviour
-is stated as "404" or "soft 404", that is an observed HTTP result.
-
-**The one-paragraph summary.** Semtech's documents are not on `semtech.com`. They are on a
-**Salesforce content-distribution front end** that no non-browser client has been shown to get bytes
-out of. Everything you need to *find* a document is machine-readable and easy (§3); everything you
-need to *download* one is hard (§4). **The practical answer is distributor mirrors** (§6), and the
-practical enumeration tool is a **1 984-entry JSON catalogue embedded in one page** (§3.2).
-
----
-
-## 1. The hosts
-
-| Host | Owns | Stability |
-|---|---|---|
-| `www.semtech.com` | Product pages, the **document portal index**, `/uploads/*` marketing PDFs, sitemaps. **No datasheets.** | Stable. Returns a genuine **HTTP 404** (103 374 B HTML) for missing pages — pleasantly probeable. ⚠ One legacy subtree soft-404s (§2.3) |
-| **`semtech.my.salesforce.com`** | **Almost every technical document** — datasheets, application notes, user guides, reference designs, errata, test reports. **1 726 of 1 984 catalogue entries.** No login required | ⚠ **JavaScript/Lightning content-distribution shell.** HTTP 200 for valid *and* invalid tokens. See §4 |
-| **`semtech.my.site.com`** | **mySemtech Document Portal** — the **registration-walled** tier. 120 catalogue entries | Live. Serves a login page, HTTP 200, for valid and invalid `docId` alike |
-| ⚠ `semtech.force.com` | The **former** host of the same portal. **103 catalogue entries still point here** | ❌ **Dead.** HTTP **404 "URL No Longer Exists"** for every `docId`, valid or not. Recoverable — §5 |
-| `github.com/LoRa-Net` (= `Lora-net`) | Drivers, SDKs, stacks, LoRa Studio installer, firmware images. **30 catalogue entries link here directly** | The most reliable Semtech source there is. Prefer it for anything software |
-
-Two hosts referenced by the catalogue but not worth a row: `apps.apple.com` (2) and
-`play.google.com` (1), for companion apps.
-
-**`www.semtech.com/robots.txt`**, retrieved 2026-09-04 — worth reading before scripting, because it
-tells you which subtrees Semtech considers app-like rather than content:
-
-```
-User-agent: *
-Disallow: /form_request/          Disallow: /mysemtech/
-Disallow: /quality_search_result/ Disallow: /selector/
-Disallow: /cross-reference-search/ Disallow: /uploads/*.html
-Disallow: /sfdc/client/           Disallow: /quality/search-pb-lead-free-rohs-green
-Disallow: /netcomponent/          Disallow: /hubfs/
-Sitemap: https://www.semtech.com/sitemap.xml
-```
-
-⚠ Note `Disallow: /uploads/*.html` — **not** `/uploads/*.pdf`. The PDF subtree is fair game; the
-HTML under it is not.
-
----
-
-## 2. URL templates
-
-### 2.1 Product pages
-
-```
-https://www.semtech.com/products/wireless-rf/<family>/<part-lowercase>
-```
-
-`<family>` is **not** derivable from the part number, and this is the first thing that wastes an
-hour:
-
-| `<family>` | Marketing name | Contains |
-|---|---|---|
-| `lora-connect` | LoRa Connect™ | `sx1272 sx1276 sx1278 sx1261 sx1262 sx1268 llcc68 sx1280 sx1281` **and `lr1121`** |
-| `lora-edge` | LoRa Edge™ | `lr1110 lr1120` |
-| **`lora-plus`** | LoRa Plus™ | **`lr2012 lr2021 lr2022`** |
-| `lora-core` | LoRa Core™ | `sx1250 sx1255 sx1257 sx1258 sx1301 sx1302 sx1303 sx1308` |
-| `frequency-shift-keying-fsk` | — | `sx1211 sx1231 sx1276`-era FSK parts |
-
-Verified 2026-09-04, with negative controls:
-
-| URL | Result |
-|---|---|
-| `…/lora-plus/lr2021` | **200**, 224 120 B |
-| `…/lora-connect/lr2021` | **404**, 106 118 B — the family is wrong, and this is the exact mistake to expect |
-| `…/lora-plus/lr9999` (**negative control**) | **404**, 106 118 B |
-| `…/lora-connect/sx1262` | **200**, 237 397 B |
-
-**Evaluation-kit and shield part numbers get their own product pages** under the same family, e.g.
-`…/lora-plus/lr2021evk2xbs1`, `…/lora-connect/sx1262dvk1cas`. They are enumerated in the sitemap.
-
-### 2.2 Sitemaps — the only complete enumeration
-
-```
-https://www.semtech.com/sitemap.xml            → index of the six below
-https://www.semtech.com/sitemap-products.xml   ← the one you want (319 016 B)
-https://www.semtech.com/sitemap-general.xml    (77 650 B)
-https://www.semtech.com/sitemap-applications.xml (13 583 B)
-https://www.semtech.com/sitemap-lora.xml       (6 804 B)
-https://www.semtech.com/sitemap-page.xml       (2 288 B)
-https://www.semtech.com/sitemap-videos.xml     (70 179 B)
-```
-
-All 200 `text/xml` on 2026-09-04. **Negative control:** `sitemap-DOESNOTEXIST.xml` → **404**,
-103 374 B HTML. So the sitemap namespace is honestly probeable.
-
-⚠ **Use the sitemap, not the family index page.** The rendered `…/lora-connect` index page lists
-`lr1121` but **not** `lr1110`/`lr1120`, and does not list the LR2021 at all. The
-`lora-plus` family is invisible from `lora-connect`. `sitemap-products.xml` is the only place all
-of them appear together.
-
-```bash
-curl -sS -A "$UA_CHROME" https://www.semtech.com/sitemap-products.xml \
-  | grep -oE '<loc>[^<]+</loc>' | sed 's/<[^>]*>//g' | grep -Ei 'lora|lr[0-9]{4}|sx1[0-9]{3}'
-```
-
-### 2.3 ⚠ `/uploads/` — one live subtree, one **soft-404** subtree
-
-This is the trap that produces HTML files with `.pdf` names in someone's artifact directory.
-
-| Path | Behaviour (verified 2026-09-04) |
-|---|---|
-| `/uploads/common/<file>.pdf` | ✅ Live. `PerSe_One_Pager.pdf` → **200**, 345 151 B, `application/pdf`, `%PDF` |
-| `/uploads/technology/**` | ✅ Live. `flood-prediction-112210.pdf` → **200**, 188 784 B, `%PDF` |
-| `/uploads/quality/<file>.pdf` | ✅ Live |
-| `/uploads/common/NEGATIVE_CONTROL_nope.pdf` | ✅ Honest **404**, 103 375 B HTML |
-| ⚠ **`/uploads/documents/<anything>.pdf`** | ❌ **HTTP 200 with 21 149 B of HTML titled *"Find Product Documentation"* — for every path, real or invented** |
-
-The `/uploads/documents/` subtree is the **retired legacy datasheet store**, now replaced by a
-search page that answers 200 to everything. Every one of these was tried and all four returned the
-identical 21 149-byte HTML:
-
-```
-DS_SX1276-7-8-9_W_APP_V7.pdf   DS_SX1261-2_V1.2.pdf
-DS_SX1280-1_V3.2.pdf           DOESNOTEXIST_negative_control.pdf   ← negative control
-```
-
-**Consequence.** Thousands of blog posts, README files, forum answers and vendored `docs/` folders
-link `https://www.semtech.com/uploads/documents/DS_*.pdf`. **Every one of them is now dead, and
-none of them looks dead.** If you are following an old citation, expect this. Recovery: §5.2.
-
-### 2.4 The technical-document endpoint (Salesforce)
-
-```
-https://semtech.my.salesforce.com/sfc/p/E0000000JelG/a/<recordId>/<token>
-```
-
-`E0000000JelG` is Semtech's org id (the 15-char form of `00DE0000000JelG`) and is constant.
-`<recordId>` looks like `RQ00000EZ5fu`, `2R000000HSNz`, `3n000000v6rK`, `44000000MDqf` — the prefix
-varies by the era the document was uploaded. `<token>` is a 43-character opaque string.
-
-**Neither part is derivable.** You must harvest the pair from a product page or from the catalogue
-(§3). See §4 for what happens when you fetch one.
-
-### 2.5 The registration-walled endpoint
-
-```
-https://semtech.my.site.com/DP/DP_CommunityLogin?docId=<18-char Salesforce Id>
-https://semtech.force.com/DP/DP_CommunityLogin?docId=<...>     ← DEAD, see §5.1
-```
-
----
-
-## 3. How to enumerate everything Semtech publishes
-
-### 3.1 Per product — the product page
-
-Each product page carries a *Documents* table rendered server-side, so `curl` + `grep` works. Every
-row is an `<a href>` to a `semtech.my.salesforce.com/sfc/p/…` URL, with a human title and a release
-date in the adjacent cells.
-
-```bash
-UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-curl -sS -A "$UA" 'https://www.semtech.com/products/wireless-rf/lora-plus/lr2021' \
-  | grep -oE '<a[^>]+href="https://semtech\.my\.salesforce\.com/sfc/p/[^"]+"[^>]*>[^<]*</a>'
-```
-`executed-success`, 2026-09-04 — 21 document links recovered for the LR2021 this way.
-
-The **Dev Kits & Shields**, **Software** and **Resources** tabs are in the same HTML, so one fetch
-gets the lot. ⚠ The **inventory/pricing widget is JavaScript-only** and renders as `$ 0` to `curl`.
-
-### 3.2 ⭐ Across the whole company — the embedded JSON catalogue
-
-**This is the single most useful thing in this guide.**
-
-```
-https://www.semtech.com/design-support/development-support-documents/
-```
-
-That page (805 220 B) contains an inline `<script>` declaring:
-
-```js
-var doc_portal = {"0":{"document_entry_id":1,
-                       "SemtechWebsitePlatform":"LoRa Connect",
-                       "SemtechWebsiteCategory":"Wireless RF",
-                       "URL":"https:\/\/semtech.my.salesforce.com\/sfc\/p\/E0000000JelG\/a\/...",
-                       "Category":"Application Notes",
-                       "Description":"AN1200.44: Bluetooth Immunity of LoRa at 2.4 GHz",
-                       "DatePosted":"2019-07-04"}, "1":{...}, ... };
-```
-
-**1 984 entries**, covering **every product line Semtech sells**, with publication dates spanning
-**2018-11-14 → 2026-08-25**. Extract it with a JSON raw-decoder (there is trailing JavaScript after
-the object, so a plain `json.loads` of a naive regex capture fails):
-
-```python
-import json, urllib.request
-UA = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-req = urllib.request.Request(
-    'https://www.semtech.com/design-support/development-support-documents/',
-    headers={'User-Agent': UA})
-s = urllib.request.urlopen(req).read().decode('utf-8', 'replace')
-i = s.index('var doc_portal = ') + len('var doc_portal = ')
-catalogue, _ = json.JSONDecoder().raw_decode(s[i:])     # 1984 entries
-```
-`executed-success`, 2026-09-04.
-
-**Category counts** (the document-class checklist you should run against any part):
-
-| Category | Entries |
-|---|---:|
-| Datasheets | 1 005 |
-| Application Notes | 346 |
-| User Guides | 224 |
-| Software Releases (Firmware) | 116 |
-| Reference Designs | 110 |
-| Reliability Report | 54 |
-| Product Briefs | 54 |
-| Tools & Software | 33 |
-| User Manual Hardware | 20 |
-| Design Guides | 7 |
-| *(blank)* | 7 |
-| **Errata** | **5** |
-| Technical articles/White papers | 3 |
-
-⚠ **Only five Errata entries exist in the entire catalogue** — `SX1276-7-8 Errata Note` (×2),
-`SX1272 Errata Note`, `Corecell Reference design V1 … Errata note`, and one behind the login wall.
-**Do not conclude a part has no errata because none is listed.** Semtech's Gen-2 and Gen-4 errata
-live *inside the datasheet* — `DS.SX1261-2` §15 "Known Limitations" and `DS.LR20xx` §22 "Known
-Limitations and Workarounds" — and Gen-4 workarounds additionally live in the **driver README** on
-GitHub. **The errata checklist item is satisfied by reading the datasheet's last chapters and the
-driver repo, not by looking for an errata PDF.**
-
-`SemtechWebsitePlatform` gives you a per-line filter — the LoRa-relevant values are
-`LoRa® Transceivers` (271), `LoRa Core` (136), `LoRa® Gateways` (40), `LoRa Connect` (18),
-`2.4 GHz Transceivers` (14), `LoRa Edge` (4).
-
-⚠ **Three data-quality caveats**, all observed 2026-09-04:
-1. **Duplicate rows are normal.** `LR2021/22/12 Datasheet v2.2` appears **three times** with three
-   *different* `<recordId>/<token>` pairs — one per platform tag. Deduplicate on `Description`.
-2. **One row is malformed:** `document_entry_id: 1773` has a *description string* in its `URL`
-   field (`"LR1121 Module w 1x Johanson IPD fliter for 868/915 MHz…"` — Semtech's typo, not mine).
-   Validate `URL.startswith('http')`.
-3. **103 rows point at the dead `semtech.force.com`** (§5.1).
-
-### 3.3 Per-product checklist
-
-For any Semtech part, work this list. It is derived from the catalogue's own categories plus the
-things that are *not* in the catalogue.
-
-- [ ] **Product page** under the right `<family>` (§2.1) — confirm via `sitemap-products.xml`
-- [ ] **Datasheet** — note that one datasheet often covers several parts (`DS.SX1261-2` = two parts;
-      `DS.LR20xx` = **three**). Check the ordering table before quoting anything
-- [ ] **Revision history inside the datasheet**, usually p. 3. This is where silent spec changes are
-      confessed
-- [ ] **Errata** → ⚠ read the datasheet's *Known Limitations* chapter **and** the driver README on
-      GitHub, not just the Errata category
-- [ ] **Application notes** — `AN1200.<nn>`; 63 distinct AN numbers appear in the catalogue.
-      ⚠ Some ANs a datasheet cites are **not on the product page** (`AN1200.37` is cited by
-      `DS.SX1261-2` §4.1.2 and appears nowhere on the SX1262 page)
-- [ ] **Reference designs** — ZIPs, per region (`EU868`, `US915`, `CN490`)
-- [ ] **Regulatory test reports** — ETSI / FCC prescan ZIPs, where published
-- [ ] **User guide / user manual hardware** for the EVK
-- [ ] **Product brief**, **reliability report** (⚠ usually login-walled — §4.3)
-- [ ] **Driver / SDK** on `github.com/LoRa-Net` — and check for a **standalone** driver repo; its
-      absence is itself a finding (the LR20xx has none)
-- [ ] **Module and EVK part numbers** — they have their own product pages and their own documents
-
----
-
-## 4. ⚠ The download problem
-
-### 4.1 What happens when you fetch a `/sfc/p/` URL
-
-`GET https://semtech.my.salesforce.com/sfc/p/E0000000JelG/a/RQ00000EZ5fu/<token>` returns **HTTP
-200** and **1 359 bytes** of HTML containing nothing but a self-submitting form:
-
-```html
-<form id="postBack" name="postBack" action="/sfc/p/#E0000000JelG/a/RQ00000EZ5fu/<token>" method="POST">
-   <input type="hidden" name="compositePageName" value="E0000000JelG/a/RQ00000EZ5fu/<token>">
-</form>
-<script>document.postBack.submit()</script>
-```
-
-⚠ **Note the `#` in the form action.** Everything after it is a URL fragment, so a browser actually
-POSTs to bare **`/sfc/p/`** carrying `compositePageName`. Reproducing that exactly:
-
-```bash
-CPN='E0000000JelG/a/RQ00000EZ5fu/L1sOvqDN_QMyCWYAAychIL5ygPsQw1AEq7xzcvpGNZg'
-curl -sS -A "$UA_CHROME" -b cookies.txt -c cookies.txt \
-     --data-urlencode "compositePageName=$CPN" \
-     'https://semtech.my.salesforce.com/sfc/p/'
-```
-
-…returns **53 747 bytes** — and it is not the document. It is a **Lightning Out bootstrap**:
-
-```js
-var lightningDistUri = '/sfc/ld/' + 'E0000000JelG' + '/a/RQ00000EZ5fu/<token>';
-var distributionId = '05DRQ00000EZ5fu';
-$Lightning.use('forceContent:contentDistributionApp', function() {
-    $Lightning.createComponent('forceContent:contentDistributionViewer',
-        { recordId:'05DRQ00000EZ5fu', distSuffix:'/a/RQ00000EZ5fu/<token>',
-          orgId:'00DE0000000JelG', ... }, 'wrapper', function(cmp) {});
-}, this.location.origin + lightningDistUri);
-```
-
-The real download URL is built **client-side by an Aura component** after an authenticated
-framework round-trip. Everything tried against it, `executed-failed` 2026-09-04:
-
-| Attempt | Result |
-|---|---|
-| `GET /sfc/ld/E0000000JelG/a/<rec>/<token>` | 200, **550 B**, *"Unable to Process Request — We couldn't access the content delivery"* |
-| `POST` the same with `compositePageName` | identical 550 B |
-| `…/app.js`, `…/app.js?aura.format=JSON&…`, `…/aura?r=1` under `/sfc/ld/` | identical 550 B |
-| `GET /sfc/dist/version/download/?oid=00DE0000000JelG&d=/a/<rec>/<token>&asPdf=false` | **200 `application/json`, zero bytes** — the endpoint exists but wants an `ids=<ContentVersionId>` that only the Aura round-trip yields |
-| `GET /sfc/servlet.shepherd/document/download/05DRQ00000EZ5fu` | 200, 787 B of HTML |
-| `GET /sfc/p/<...>/<token>?download=1` | 200, the same 1 359 B shell |
-
-**Verdict: `blocked` for automated clients.** A real browser is required. This corroborates and
-extends the finding first recorded in
-[`components/semtech/sx1262/README.md` §11](../../components/semtech/sx1262/README.md), and adds the
-`/sfc/ld/` and `/sfc/dist/version/download/` legs that were not previously traced.
-
-### 4.2 ⚠ The negative control that matters most
-
-```bash
-curl -sS -A "$UA_CHROME" -o /dev/null -w '%{http_code} %{size_download}\n' \
-  'https://semtech.my.salesforce.com/sfc/p/E0000000JelG/a/RQ00000EZ5fu/THIS_TOKEN_DOES_NOT_EXIST_0000000000000000000'
-# 200 1363
-```
-
-**An invented token returns HTTP 200 and a 1 363-byte shell — four bytes different from the valid
-one.** So:
-
-- **The `/sfc/p/` endpoint tells you nothing about whether a document exists.** You cannot probe it,
-  you cannot validate a harvested URL with it, and a 200 from it is not evidence of anything.
-- Any script that treats "HTTP 200 from Semtech" as success will happily write 1 359 bytes of HTML
-  into `datasheet.pdf`. **Validate by magic bytes** (`%PDF`), never by status code or URL suffix.
-
-### 4.3 What actually requires registration, exactly
-
-Two different gates, and they are frequently conflated. **The Salesforce `/sfc/p/` shell is *not* a
-login wall** — it needs no account, only a browser. The genuine login wall is the **mySemtech
-Document Portal** on `semtech.my.site.com`, and it covers a specific, measurable slice:
-
-| Document class | Public `/sfc/p/` | **Login-walled** |
-|---|---:|---:|
-| Datasheets | 970 | **35** |
-| Application Notes | 311 | **35** |
-| User Guides | 183 | **41** |
-| Software Releases (Firmware) | 47 | **35** *(+34 direct GitHub links)* |
-| Reference Designs | 102 | **8** |
-| **Reliability Report** | 6 | **48** ← the most-gated class by far |
-| Product Briefs | 44 | **10** |
-| User Manual Hardware | 10 | **10** |
-| Errata | 4 | **1** |
-| Tools & Software · Design Guides · White papers | 32 · 7 · 3 | 0 |
-
-**And the finding that matters for anyone reading this guide for LoRa work:**
-
-> **Zero LoRa documents are login-walled.** All 271 `LoRa® Transceivers`, 136 `LoRa Core`, 40
-> `LoRa® Gateways`, 18 `LoRa Connect`, 14 `2.4 GHz Transceivers` and 4 `LoRa Edge` entries resolve
-> either to the public `/sfc/p/` endpoint or straight to GitHub. **Not one points at
-> `DP_CommunityLogin`.**
-
-The login wall is overwhelmingly **Signal Integrity, Crosspoints, Clocks and reliability
-qualification reports** — Semtech's non-LoRa businesses.
-
-**How the gate behaves**, verified 2026-09-04:
-
-```bash
-curl -sSL -A "$UA_CHROME" 'https://semtech.my.site.com/DP/DP_CommunityLogin?docId=a0G2R00000zilgEUAQ'
-# 200  322 432 B  text/html   <title>mySemtech Document Portal | Semtech</title>   (login form)
-
-curl -sSL -A "$UA_CHROME" 'https://semtech.my.site.com/DP/DP_CommunityLogin?docId=a0GBOGUS'
-# 200  322 006 B  ← also a login page
-```
-
-⚠ **Both return HTTP 200 and a login page.** The two bodies differ slightly (322 432 vs 322 006 B),
-so a valid `docId` leaks *something*, but neither response distinguishes "needs login" from "does
-not exist". **Do not treat a 200 here as document existence either.**
-
-Registration is free but is an account-creation flow; **this pass did not create one**, so what lies
-beyond the wall is `not-tested`.
-
----
-
-## 5. Known migrations and how to recover from them
-
-### 5.1 `semtech.force.com` → `semtech.my.site.com`
-
-The classic Salesforce Communities → Experience Cloud domain move. Semtech did it and **did not
-rewrite its own catalogue**: 103 of 1 984 entries still point at `semtech.force.com`.
-
-**Detection.** Every `semtech.force.com/DP/DP_CommunityLogin?docId=…` returns:
-
-```
-HTTP 404, 1 972 B
-<span ...>URL No Longer Exists</span>
-You have attempted to reach a URL that no longer exists on salesforce.com.
-```
-
-⚠ **Identical for a valid `docId` and an invented one** — verified with both. So the 404 is the
-host, not the document.
-
-**Recovery: swap the host, keep the `docId`.** `executed-success` 2026-09-04 —
-`docId=a0G2R00000q7EOCUA2` (an errata note, dead on `force.com`) returns **200** and the mySemtech
-login page on `semtech.my.site.com`:
-
-```bash
-sed 's|semtech\.force\.com|semtech.my.site.com|' <<< "$URL"
-```
-
-### 5.2 The two dead `semtech.com` document stores
-
-| Old path | Era | Now | Recovery |
-|---|---|---|---|
-| `www.semtech.com/images/datasheet/<file>.pdf` | ~2011–2016 | ❌ gone | **Wayback.** The CDX index has hundreds of them |
-| `www.semtech.com/uploads/documents/<file>.pdf` | ~2017–2020 | ⚠ **soft 404** (§2.3) | **Wayback**, then the catalogue for the current revision |
-
-```bash
-# what was ever published under those paths, as PDFs
-curl -sS "https://web.archive.org/cdx/search/cdx?url=semtech.com/*&matchType=domain\
-&output=text&fl=timestamp,original,statuscode,length&filter=mimetype:application/pdf&limit=6000"
-```
-`executed-success` 2026-09-04 — 6 000 rows, including `sx1276_77_78_79.pdf` (2015-07-31, 2 378 028 B),
-`DS_SX1276-7-8-9_W_APP_V5.pdf` (2018-09-03, 1 983 317 B), `sx1276_77_78-errata.pdf`,
-`sx1272_73_errata.pdf`, `DS_SX1261-2_V1.1.pdf`, `sx1280-1.pdf`. Fetch with the `if_` modifier so
-Wayback serves the original bytes rather than a framed page:
-
-```bash
-curl -sSL -A "$UA_CHROME" -o out.pdf \
-  'https://web.archive.org/web/20180903190247if_/https://www.semtech.com/uploads/documents/DS_SX1276-7-8-9_W_APP_V5.pdf'
-head -c5 out.pdf   # %PDF-
-```
-
-⚠ **Wayback gives you an old revision, not the current one.** Use it for Gen-1/Gen-2 history and for
-recovering a dead citation — not as a substitute for §6.
-
-⚠ **And a hard negative result:** the Wayback CDX index for `semtech.com` contains **zero LR11xx and
-zero LR20xx PDFs**, because those documents have only ever lived behind the Salesforce shell, which
-Wayback cannot crawl. `semtech.my.salesforce.com` has captures only of the bare host root, all
-redirects. **There is no archive route to a Gen-3 or Gen-4 document.**
-
----
-
-## 6. ⭐ The route that works: distributor mirrors
-
-Since §4 is `blocked` and §5.2 only reaches pre-2020 documents, **authorised distributors are the
-practical source for any current Semtech datasheet.** Both were verified 2026-09-04.
-
-### 6.1 Digi-Key — the good one
-
-```
-https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/<dir>/<num>_<Filename>.pdf
-```
-
-| Probe | Result |
-|---|---|
-| `…/docus/8924/600_62785538.LR20xxDatasheet_V2_1.pdf` | **200**, 5 809 234 B, `application/pdf`, `%PDF` |
-| `…/docus/8924/600_00000000.NEGATIVE_CONTROL.pdf` | **404**, 3 340 B HTML |
-
-**No User-Agent games needed; honest 404s; correct content type.** This is the best-behaved Semtech
-mirror found. ⚠ The `<dir>` and `<num>` components are Digi-Key's opaque internal ids and are **not
-derivable** — harvest the full URL from a search engine or from the Digi-Key product page.
-
-### 6.2 Mouser — works, but only with an unusual User-Agent
-
-```
-https://www.mouser.com/pdfDocs/<opaque-id><Filename>.pdf
-```
-
-⚠ **Mouser blocks the ordinary browser agent on this path and serves the WhatsApp link-preview
-agent.** This is the reverse of the usual pattern:
-
-| UA | Result for `61979758LR2021_V1_1_datasheet.pdf` |
-|---|---|
-| `Mozilla/5.0 … Chrome/131.0.0.0 …` | **200**, 13 895 B, `text/html` — an *"Access Denied / captcha"* page. ⚠ **HTTP 200**, so a naive script saves it as a PDF |
-| **`WhatsApp/2.23.20.0`** | **200**, **5 158 757 B**, `application/pdf`, `%PDF` ✅ |
-
-**Negative control:** guessed filenames (`LR2021_datasheet.pdf`, `DS_LR2021_V1.0.pdf`) return
-**403**, 1 140 B. And `https://www.mouser.com/c/?q=<part>` returns the 13 895 B Access-Denied page to
-**every** agent tried — so Mouser is usable as a fetcher, not as a search engine.
-
-### 6.3 ⚠ Mirrors are revision-frozen, and that is a feature
-
-Three sources, three revisions of the same document, on the same day:
-
-| Source | Revision | Bytes | SHA-256 (first 16) |
-|---|---|---:|---|
-| **Semtech** (canonical, `blocked`) | **v2.2, 2026-08-08** | — | — |
-| **Digi-Key** | **Rev 2.1, 13/04/26**, 243 pp | 5 809 234 | `0d9051db78b243bf` |
-| **Mouser** | **Rev 1.1, 10/14/25**, 236 pp | 5 158 757 | `926b88cbfb6434e3` |
-
-**A distributor mirror tells you which revision that distributor's customers were designing
-against.** Keep both, name each for its source, and record which is current — the reasoning is in
-[`components/semtech/lr2021/README.md` §14.2](../../components/semtech/lr2021/README.md) and the
-[archive placeholder](../../components/semtech/lr2021/artifacts/lr2021-datasheet-v1.1-mouser-mirror.pdf.ARCHIVED.md).
-
-### 6.4 Vendor mirrors
-
-Board vendors sometimes mirror the chip datasheet openly, and those mirrors are the fastest route of
-all when they exist. Known-good, recorded by the SX1262 pass:
-
-```
-https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/1177/DS_SX1261_2_V2-2.pdf   # open, 200, application/pdf
-```
-
-⚠ **Vendor mirrors serve the revision the board was designed against**, which may be years old.
-File them under the **component**, name them `…-<vendor>-mirror.pdf`, and hash them.
-
----
-
-## 7. User-Agent behaviour, measured
-
-`www.semtech.com/products/wireless-rf/lora-connect/sx1262`, 2026-09-04:
-
-| User-Agent | Result |
-|---|---|
-| `Mozilla/5.0 … Chrome/131.0.0.0 …` | **200**, 237 397 B |
-| **`curl/8.0.1` (default)** | **200**, 237 397 B — ⚠ **no UA spoofing is needed for `semtech.com`** |
-| `…ClaudeBot/1.0; +claudebot@anthropic.com` | **200**, 237 397 B |
-| ⚠ **`WhatsApp/2.23.20.0`** | ❌ **403**, 919 B |
-
-**So `semtech.com` is the exact inverse of `mouser.com`**, and the inverse of `www.st.com` (which
-serves the WhatsApp agent and resets Chrome). There is no single agent that works everywhere. The
-rule for this vendor:
-
-| Host | Use |
-|---|---|
-| `www.semtech.com` | anything **except** WhatsApp. Default `curl` is fine |
-| `semtech.my.salesforce.com` | Chrome UA + cookie jar — and it still will not give you bytes (§4) |
-| `mm.digikey.com` | any UA |
-| **`www.mouser.com/pdfDocs/`** | **`WhatsApp/2.23.20.0`** — Chrome is blocked |
-| `api.github.com` | authenticate with `gh auth token`; UA is irrelevant |
-
-Recorded in [`ai-crawler-site-access-table.md`](../../ai-crawler-site-access-table.md).
-
----
-
-## 8. Validation requirements
-
-Non-negotiable for this vendor, because **three separate Semtech-adjacent paths return HTTP 200 with
-HTML for a document request**: the `/sfc/p/` shell (1 359 B), the `/uploads/documents/` soft-404
-(21 149 B), and Mouser's Access-Denied page (13 895 B).
-
-```bash
-# after every download
-head -c 5 "$f" | grep -q '%PDF' || { echo "NOT A PDF: $f"; exit 1; }
-sha256sum "$f"; stat -c%s "$f"
-```
-
-Then record, for every artifact:
-
-- **Document number and revision** — Semtech prints both in the running footer of every page, e.g.
-  `LR2021/LR2022/LR2012 · Final Datasheet Rev. 2.1 · DS.LR20xx 13/04/26 · N of 243`. **Use the
-  footer, not the filename** — the Digi-Key filename says `V2_1` but the footer says `Rev. 2.1`
-  *and* gives the date and the document number
-- **The revision history table**, usually page 3, which is where silent spec changes are confessed
-- SHA-256, byte size, retrieval date, canonical URL **and** mirror URL
-
-⚠ **Text-layer defects are common in Semtech PDFs and they are the quiet kind.** Two observed:
-
-| Document | Defect |
-|---|---|
-| `DS.SX1261-2` Rev 2.2 | **Figure fonts carry a uniform +31 code-point offset** — block-diagram labels extract as human-legible but *wrong* text (`-P3B¥` for `LoRa®`, `41*` for `SPI`). Body text and tables are clean |
-| `DS.LR20xx` Rev 2.1 | The **micro sign is dropped** — sleep currents extract as `A` where the page says `µA`, PA ramp times as `s` where the page says `µs`. Figures are **vector art with no text layer at all**, so pin-out diagrams and the package-marking drawing extract as bare word lists or as nothing |
-
-**Cross-check every extracted value against the running footer and page numbering before
-transcribing, and never transcribe a figure label.**
-
----
-
-## 9. Rights and licensing observations
-
-- Semtech datasheets carry **"Semtech Proprietary & Confidential" in the footer of every page** —
-  on documents that Digi-Key and Mouser mirror openly and that Semtech itself links from a public
-  product page. ⚠ **That is a genuine conflict, not an oversight.** Record redistribution status as
-  `unknown`, keep the artifact unstaged, and say so. Do not resolve it by preference.
-- **LR-FHSS is patent-encumbered.** Every datasheet covering an LR-FHSS-capable part carries a
-  notice that using Semtech's LR-FHSS software grants **no** patent rights; rights come *"by
-  purchasing Semtech SX1261, SX1262, SX1268, LR1110, LR1120, LR1121, LR2012, LR2021 or LR2022
-  semiconductor devices, or their authorized counterparts"*.
-- **Bluetooth:** parts with a BLE PHY carry *"not certified or qualified Bluetooth products"*.
-- **Software is far more permissive than documents.** `LoRa-Net` driver repos are
-  **BSD-3-Clause-Clear** (`sx126x_driver`, `llcc68_driver`, `SWDR001`, `SWL2001`, and the
-  `lr20xx_driver` subtree inside `usp`), some are Apache-2.0 or MIT. ⚠ **GitHub's repo-level label
-  is often `NOASSERTION`** for monorepos — check the subtree's own `LICENSE.txt`, which is where
-  `usp`'s BSD-3-Clause-Clear text actually lives.
-- Preserve `LICENSE.txt` / `LICENSES.txt` when snapshotting a driver; the Clear BSD disclaimer is
-  part of the obligation.
-
----
-
-## 10. Working command examples
-
-```bash
-UA_CHROME='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
-UA_WA='WhatsApp/2.23.20.0'
-
-# 1. Find the family a part lives in
-curl -sS -A "$UA_CHROME" https://www.semtech.com/sitemap-products.xml \
-  | grep -oE '<loc>[^<]+</loc>' | sed 's/<[^>]*>//g' | grep -i 'lr2021'
-
-# 2. Enumerate one product's documents
-curl -sS -A "$UA_CHROME" 'https://www.semtech.com/products/wireless-rf/lora-plus/lr2021' \
-  | grep -oE '<a[^>]+href="https://semtech\.my\.salesforce\.com/sfc/p/[^"]+"[^>]*>[^<]*</a>'
-
-# 3. Enumerate EVERYTHING (§3.2) — see the Python snippet there
-
-# 4. Fetch a datasheet, Digi-Key (preferred)
-curl -sSL -A "$UA_CHROME" -o ds.pdf \
-  'https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/8924/600_62785538.LR20xxDatasheet_V2_1.pdf'
-
-# 5. Fetch a datasheet, Mouser (⚠ WhatsApp UA)
-curl -sSL -A "$UA_WA" -o ds.pdf 'https://www.mouser.com/pdfDocs/61979758LR2021_V1_1_datasheet.pdf'
-
-# 6. Validate — ALWAYS
-head -c 5 ds.pdf | grep -q '%PDF' && sha256sum ds.pdf && stat -c%s ds.pdf
-
-# 7. Recover a dead force.com portal link
-echo "$URL" | sed 's|semtech\.force\.com|semtech.my.site.com|'
-
-# 8. Recover a dead semtech.com/uploads/documents/ link
-curl -sS "https://web.archive.org/cdx/search/cdx?url=semtech.com/*&matchType=domain\
-&output=text&fl=timestamp,original,statuscode,length&filter=mimetype:application/pdf&limit=6000" \
-  | grep -i 'sx1276'
-
-# 9. Software — always prefer GitHub, always authenticate
-gh api repos/LoRa-Net/usp/git/trees/<sha>?recursive=1
-curl -fsSL -H "Authorization: Bearer $(gh auth token)" \
-  "https://raw.githubusercontent.com/LoRa-Net/usp/<sha>/<path>"
-```
-
-⚠ **`github.com/LoRa-Net` and `github.com/Lora-net` are the same organisation** (GitHub org names
-are case-insensitive) and return identical repository lists. Semtech's own pages use both spellings
-— the LR2021 product page links `github.com/LoRa-Net` while `DS.LR20xx` §22 cites
-`https://github.com/lora-net/usp`. Neither is wrong.
-
----
-
-## 11. Parts documented using this guide
-
-| Part / family | Record |
-|---|---|
-| **LR2021** (Gen 4) | [`components/semtech/lr2021`](../../components/semtech/lr2021/README.md) |
-| LR1121 (Gen 3) | [`components/semtech/lr1121`](../../components/semtech/lr1121/README.md) |
-| LR1110 / LR1120 (Gen 3) | [`components/semtech/lr11x0`](../../components/semtech/lr11x0/README.md) |
-| SX1262 (Gen 2) | [`components/semtech/sx1262`](../../components/semtech/sx1262/README.md) — §11 of that record is what prompted this guide |
-| SX1268 (Gen 2) | [`components/semtech/sx1268`](../../components/semtech/sx1268/README.md) |
-| LLCC68 (Gen 2) | [`components/semtech/llcc68`](../../components/semtech/llcc68/README.md) |
-| SX1276 / SX127x (Gen 1) | [`components/semtech/sx1276`](../../components/semtech/sx1276/README.md) |
-| Cross-cutting | [`guides/hardware/lora-radio-generations.md`](../../guides/hardware/lora-radio-generations.md) |
-
----
-
-## 12. Change log for this guide
-
-| Date | Change |
-|---|---|
-| **2026-09-04** | Created, during the LoRa generation-lineage pass. Everything above live-verified on this date with negative controls. New findings not previously recorded anywhere in this repository: the **embedded 1 984-entry JSON document catalogue** (§3.2); the **`/uploads/documents/` soft-404** (§2.3); the **`semtech.force.com` → `semtech.my.site.com` migration and its 103 stale catalogue rows** (§5.1); the **exact scope of the registration wall**, and the finding that **no LoRa document is behind it** (§4.3); the **`/sfc/ld/` and `/sfc/dist/version/download/` legs** of the Salesforce shell (§4.1); the **invalid-token negative control returning 200** (§4.2); **Digi-Key and Mouser URL templates with negative controls**, and Mouser's **inverted User-Agent requirement** (§6); and the measured **UA matrix** showing default `curl` is fine on `semtech.com` while WhatsApp is 403'd (§7) |
diff --git a/vendors/squareline/README.md b/vendors/squareline/README.md
index da44cba..9760be8 100644
--- a/vendors/squareline/README.md
+++ b/vendors/squareline/README.md
@@ -114,7 +114,7 @@ Missing the `micropython` servers or `lv_font_conv-linux` yields an application
 | **Tiers** | Free tier with limits; 30-day full-featured trial requiring no account [S1] |
 | **Account required to download** | No |
 | **Account/internet required to activate** | Yes, at first launch [S6] |
-| **Redistribution status** | **restricted** — no evidence of any redistribution grant, and no licence file ships in the archive |
+| **Redistribution status** | **prohibited** — no evidence of any redistribution grant, and no licence file ships in the archive |
 | **Disposition** | **local-cache** — archived outside the repository; never staged |
 
 ## 8. Sources
diff --git a/vendors/squareline/artifacts/ARCHIVED-SQUARELINE-STUDIO-LINUX.md b/vendors/squareline/artifacts/ARCHIVED-SQUARELINE-STUDIO-LINUX.md
index 1474764..8fa6f1a 100644
--- a/vendors/squareline/artifacts/ARCHIVED-SQUARELINE-STUDIO-LINUX.md
+++ b/vendors/squareline/artifacts/ARCHIVED-SQUARELINE-STUDIO-LINUX.md
@@ -3,9 +3,9 @@
 The SquareLine Studio Linux ZIP that this directory would otherwise hold has been kept **outside the repository**. It is 172 MiB of proprietary, all-rights-reserved binaries with no redistribution grant, so it is neither committed nor staged.
 
 - **Archived:** 2026-08-30
-- **Moved to:** `archive/vendors/squareline/artifacts/` (same relative path)
+- **Moved to:** `../hardware-doc-archive/doc/hardware/vendors/squareline/artifacts/` (same relative path)
 - **Kept out of the repository:** 180 438 276 bytes (~172.1 MiB)
-- **Redistribution status:** **restricted** · **Disposition:** **local-cache**
+- **Redistribution status:** **prohibited** · **Disposition:** **local-cache**
 
 Nothing was lost. Everything this repository needs from the archive was extracted into Markdown before it was set aside — see [What was extracted](#what-was-extracted-and-where-it-now-lives).
 
@@ -26,40 +26,7 @@ Nothing was lost. Everything this repository needs from the archive was extracte
 | **Licence** | Proprietary, all rights reserved — **no licence file ships inside the archive** |
 | **Why it is not in the repository** | Size combined with an explicit all-rights-reserved licence and no redistribution permission |
 
-### Source repository — none, by design
-
-SquareLine Studio is proprietary and closed-source, distributed only as a vendor download. There
-is **no upstream repository to pin and no commit**, and this is recorded explicitly so the absent
-line reads as *checked and absent* rather than an omission someone later "fixes" with a
-plausible-looking link.
-
-### Second source — deliberately not sought for the binary
-
-Two independent sources is the standing rule. **This artifact is the documented exception, and
-the exception is on purpose.** The ZIP is 172 MiB of all-rights-reserved binaries with no
-redistribution grant — the same reason it is not committed here. A second custodian for the
-binary would necessarily be an unauthorised mirror, so citing one would recommend a route this
-record's own reasoning rejects. **Do not add one.**
-
-What is legitimately available is a third-party record of *the download page*, which preserves
-what existed and where, without redistributing anything:
-
-- Wayback capture of the downloads page, **2026-08-11**:
-  <http://web.archive.org/web/20260811204105/https://squareline.io/downloads>
-- Wayback capture of the site root, same date:
-  <http://web.archive.org/web/20260811204050/https://squareline.io/>
-
-> ⚠ **Existence confirmed, contents not.** These snapshots were reported by the Wayback
-> availability API on 2026-08-30, but fetching them that day returned *"Internet Archive:
-> Temporarily Offline"* rather than the page. **Nobody has confirmed the capture actually shows
-> the 1.6.1 Linux link.** Treat it as a lead to check, not a verified recovery path, and update
-> this line once someone has looked.
-
-So the honest position for this artifact: **one custodian for the bytes, and the SHA-256 above
-is doing more work than usual.** If you hold a copy that matches that hash, it is more valuable
-than the usual archived duplicate.
-
-## Reacquisition
+### Reacquisition
 
 **Verified 2026-08-30.** This host returns **HTTP 206 for non-existent paths too**, so check `Content-Type`: `application/x-zip-compressed` means a real file, `text/html` is a soft 404.
 
diff --git a/vendors/squareline/artifacts/SquareLine_Studio_Linux_v1_6_1.zip b/vendors/squareline/artifacts/SquareLine_Studio_Linux_v1_6_1.zip
deleted file mode 120000
index a97b871..0000000
--- a/vendors/squareline/artifacts/SquareLine_Studio_Linux_v1_6_1.zip
+++ /dev/null
@@ -1 +0,0 @@
-../../../archive/vendors/squareline/artifacts/SquareLine_Studio_Linux_v1_6_1.zip
\ No newline at end of file
diff --git a/vendors/waveshare/README.md b/vendors/waveshare/README.md
index 6a576c2..308f380 100644
--- a/vendors/waveshare/README.md
+++ b/vendors/waveshare/README.md
@@ -371,186 +371,7 @@ Render and read visually; use `pdftotext -bbox-layout` only to locate regions.
 Also: for the XC schematic, **page 2 is the PCB layout, not circuitry**. All circuit detail is on
 page 1.
 
-## 9. Findings added 2026-09-01 (ESP32-S3-ePaper-3.97)
-
-Source: [`ESP32-S3-ePaper-3.97`](../../devices/waveshare/esp32-s3-epaper-3.97/README.md).
-Two of these **correct earlier sections of this guide**; they are dated rather than
-silently overwritten.
-
-### 9.1 ⚠ The two documentation hosts are *disjoint*, not layered — and this cost a whole pass
-
-§8.2 already says to check `docs.waveshare.com` first. **That is not strong enough.**
-The observed rule is:
-
-| Product era | `docs.waveshare.com/<PRODUCT>` | `waveshare.com/wiki/<Product>` |
-|---|---|---|
-| Newer (e.g. `ESP32-S3-ePaper-3.97`, `ESP32-S3-ePaper-1.54`, `ESP32-C6-ePaper-1.54`) | **200** | **404** |
-| Older (e.g. `E-Paper_ESP32_Driver_Board`) | **404** | **200** |
-
-**A 404 on one host says nothing about the product.** In this pass a first attempt
-tested only the legacy wiki, got a 404, and concluded the vendor publishes *no
-documentation, no schematic, no pinout, no sample code and no panel controller* for
-the board. **All of those were false** — the docs site carried a schematic, a panel
-manual, four IC datasheets and a link to an official example repository.
-
-**Always probe both hosts before recording an absence.**
-
-```bash
-for h in "https://docs.waveshare.com/$P" "https://www.waveshare.com/wiki/$P"; do
-  printf '%-70s ' "$h"; curl -sSL -A "$UA" -o /dev/null -w '%{http_code}\n' "$h"
-done
-```
-
-The new platform is Docusaurus and **server-renders its text**, so `curl` + strip-tags
-is sufficient; no browser needed. Sub-pages follow
-`docs.waveshare.com/<PRODUCT>/<Section>`, discoverable with:
-
-```bash
-grep -oE "$P/[A-Za-z0-9\-]+" docs.html | sort -u
-# -> Arduino, ESP-IDF, FAQ, Firmware-Flashing, Resources-And-Documents, Technical-Support …
-```
-
-**`Resources-And-Documents` is the single highest-yield page per product** — it is the
-new equivalent of the old wiki's Resources section, and it lists the schematic, the
-panel datasheet, the onboard-IC datasheets, the GitHub repo and community projects.
-
-### 9.2 ⚠ Correction to §8.7 — schematic PDFs *do* have a usable text layer
-
-§8.7 states Waveshare schematics "have no usable text layer" and must be read
-visually. **For the ESP32-S3-ePaper-3.97 schematic that is wrong**, and the reason a
-naive attempt fails is worth knowing:
-
-1. **The sheet lives in a Form XObject, not in `/Contents`.** A page-content walker
-   returns **zero** text and looks exactly like "no text layer". The content was in
-   one object: 62 KB compressed → 448 KB inflated → 1 158 `BT` blocks.
-2. **Altium emits one glyph per `Tj`, each with its own `Tm`.** Raw extraction gives
-   4 318 single characters and 170 distinct strings — useless to `grep`, which is
-   presumably how the original "no usable text layer" conclusion was reached.
-3. **Reflowing by baseline recovers real tokens.** Grouping by `y`, sorting by `x` and
-   joining runs under a gap threshold produced **1 150 tokens / 628 distinct**,
-   including every net label, part label and — critically — an entire **GPIO
-   allocation table** drawn on the sheet.
-
-Tools that do this, kept beside the device record and reusable for any Waveshare
-Altium export:
-
-- [`pdftext.py`](../../devices/waveshare/esp32-s3-epaper-3.97/tools/pdftext.py) — inflates every stream **including Form XObjects**, interprets `BT`/`Tm`/`Td`/`Tj`/`TJ`
-- [`reflow.py`](../../devices/waveshare/esp32-s3-epaper-3.97/tools/reflow.py) — glyph → word reassembly
-
-These need no poppler, no `pypdf`, no `pip` — which mattered, because none was
-available. The repo's own `tools/altium_pdf_netlist.py` is better where
-`pdftotext -bbox` **is** available; these are the fallback.
-
-**§8.7 still holds in one respect:** the result is **text adjacency, not connectivity**.
-0 Ω series resistors still break the GPIO-to-net pairing, and unlabelled wire-only
-connections are invisible. Treat the output as a reading aid and confirm anything
-load-bearing against the rendered sheet.
-
-### 9.3 Panel manuals may have offset-encoded text layers
-
-The `3.97inch_e-Paper.pdf` panel manual embeds **two subset fonts whose code points
-are uniformly displaced** — `+29` for one, `+26` for the other. Naive extraction
-yields `LQFKH 3DSHU` where the document reads `inch e-Paper`.
-
-This is the dangerous variant: after a shift the text is **human-legible but wrong**,
-so it does not look like a failure.
-
-```bash
-# Recover the offset from a KNOWN heading, never by guessing:
-python3 -c "print({ord(w)-ord(e) for e,w in zip('LQFKH','inche')})"   # -> {29}
-```
-
-**Validate against a known heading before transcribing any value.** Doing so is what
-recovered `Driver IC: SSD1677` — a fact available nowhere else in Waveshare's material
-for that board. Decoder:
-[`deshift.py`](../../devices/waveshare/esp32-s3-epaper-3.97/tools/deshift.py).
-
-### 9.4 Storefront: category pages are JS-rendered; use `catalogsearch`
-
-```bash
-curl -sS -A "$UA" 'https://www.waveshare.com/product/displays/e-paper.htm' | grep -c 'product-item'
-# -> 0     (HTTP 200, 244 758 bytes, and no products)
-```
-
-**Enumerate with `/catalogsearch/result/?q=<terms>&limit=200`**, which returns real
-product URLs. Run several query families — the index is literal:
-
-| Query | Result |
-|---|---|
-| `e-paper esp32` | 7 products |
-| `e-paper driver board` | 6, partly different set |
-| `esp32 e-ink` | **zero** — "e-ink" is not indexed as a synonym for "e-Paper" |
-
-### 9.5 Extension to §8.6 — the SKU JSON key has a **trailing space**
-
-§8.6's regex misses the current markup. The listing embeds:
-
-```javascript
-var waveshare_sku_attributes = [{"sku ":"33552","attributes":["With Lithium Batt"],"unsaleable":false}, …];
-var waveshare_attributes2sku  = {"With Lithium Batt":"33552", …};
-```
-
-Note **`"sku "`, not `"sku"`**. A search for `"sku"` returns nothing, which in this
-pass caused a price to be recorded as "not established" when it was plainly on the
-page. Use:
-
-```bash
-python3 -c "import re,html,sys; s=open(sys.argv[1],encoding='utf-8',errors='replace').read(); \
-m=re.search(r'waveshare_sku_attributes\s*=\s*(\[.*?\]);',s,re.S); print(html.unescape(m.group(1)))" product.html
-```
-
-Prices come from `class="price"` and are a **range** across variants:
-
-```bash
-grep -oE 'class="price"[^>]*>\s*\$?([\d,.]+)' product.html | sort -u
-```
-
-`"unsaleable":false` on every variant is the availability signal.
-
-### 9.6 Third confirmation: `files.waveshare.com/wiki/common/` mirrors run stale
-
-Already warned about in §4. Now quantified for a third part:
-
-| Document | Waveshare mirror | Manufacturer |
-|---|---|---|
-| ESP32-S3 datasheet | v1.6 | v2.x (Espressif) |
-| **PCF85063A** | **Rev. 6, 2015** (535 722 B) | **Rev. 7, 2018** (726 288 B) |
-
-**Always hash a `common/` mirror against the manufacturer's copy and record both.**
-The mirror documents what Waveshare ships its customers; the manufacturer's copy is
-what you design against.
-
-### 9.7 Correction to §8.4 — `waveshareteam` repos are **not** reliably licensed
-
-§8.4 records that Waveshare's GitHub repositories are "**Apache-2.0** licensed, where
-the demo ZIP ships no `LICENSE` at all". That was true of the ESP32-P4 repositories.
-It is **not a vendor-wide guarantee**:
-
-```
-github.com/waveshareteam/ESP32-S3-ePaper-3.97   ->  license: null,  no LICENSE file
-```
-
-**Check per repository.** The finding that repos *exist* and are strictly better than
-the demo ZIP still holds — this one carries Arduino and ESP-IDF examples, factory
-firmware and a docs link that the storefront does not mention.
-
-Also note this repo vendors third-party libraries (`XPowersLib`, `SensorLib`) with no
-version pin and no upstream commit recorded, so their modification status cannot be
-assessed without diffing.
-
-### 9.8 Marketing part names may not match the silicon
-
-The storefront **and** the official docs name this board's PMIC **"TG28"**. The
-schematic labels it **`AXP2101`** with X-Powers pin names throughout, and Waveshare's
-own firmware drives it through XPowersLib's AXP2101 path.
-
-§4's trust order (**schematic > demo source > wiki > storefront**) resolved it
-correctly — but note that here **the docs site was wrong too**, so "it is on the
-official documentation platform" is not a promotion in that order. Treat
-`docs.waveshare.com` as equivalent to the wiki, not as design data.
-
 ## Devices sourced with this guide
 
 - [`ESP32-S3-Knob-Touch-LCD-1.8`](../../devices/waveshare/esp32-s3-knob-touch-lcd-1.8/README.md)
 - [`ESP32-P4-WIFI6-Touch-LCD-3.4C`](../../devices/waveshare/esp32-p4-wifi6-touch-lcd-3.4c/README.md) and [`-4C`](../../devices/waveshare/esp32-p4-wifi6-touch-lcd-4c/README.md), sharing [`-XC`](../../devices/waveshare/esp32-p4-wifi6-touch-lcd-xc-shared/README.md) — source of findings §8
-- [`ESP32-S3-ePaper-3.97`](../../devices/waveshare/esp32-s3-epaper-3.97/README.md) — source of findings §9, plus stubs for [`e-Paper ESP32 Driver Board`](../../devices/waveshare/e-paper-esp32-driver-board/README.md), [`ESP32-S3-ePaper-1.54`](../../devices/waveshare/esp32-s3-epaper-1.54/README.md), [`ESP32-C6-ePaper-1.54`](../../devices/waveshare/esp32-c6-epaper-1.54/README.md) and [`ESP32-S3-PhotoPainter`](../../devices/waveshare/esp32-s3-photopainter/README.md)
diff --git a/vendors/xteink/README.md b/vendors/xteink/README.md
deleted file mode 100644
index af2e1ff..0000000
--- a/vendors/xteink/README.md
+++ /dev/null
@@ -1,174 +0,0 @@
-# Xteink (Shenzhen Xiaohu Xingtong Technology Co., Ltd. · 深圳市小虎星瞳科技有限公司)
-
-*Written 2026-09-11 by the round-two index merge, from the sourcing findings of the Xteink
-round-two and certification/market passes. Everything below was **observed**, not recalled;
-every claim carries the date it was observed on.*
-
-Shenzhen maker of low-cost pocket e-ink readers — the [Xteink family](../../devices/README.md#xteink-阅星瞳--星瞳-star-pupil),
-and the hardware target of the CrossPoint Reader / FreeInk firmware ecosystem.
-
-> **Why this guide exists.** Xteink publishes **no datasheet, no schematic, no wiki and no
-> support portal**. There is a Shopify storefront and nothing else. That sounds like a dead end
-> and is not: the storefront's JSON endpoints and the company's **FCC grantee record** between
-> them yield launch dates, SKUs, stock, prices, the legal entity, and the complete list of
-> products — *including ones the vendor has never announced*. This guide is about those two
-> routes.
-
----
-
-## 1. Identity
-
-| Field | Value | Evidence |
-|---|---|---|
-| Legal name | **Shenzhen Xiaohu Xingtong Technology Co., Ltd.** | FCC grantee record, 2026-09-11 |
-| Brand names | Xteink · 阅星瞳 · 星瞳 ("Star Pupil") | vendor site, community |
-| **FCC grantee code** | **`2BTR9`**, registered **2025-12-21** | <https://fccid.io/2BTR9> |
-| FCC contact | Chen Chu, `chuchen@xteink.cn` | FCC grantee record |
-| Address | Room 1209, Yichuang International Center, Building 2B, No. 8 Golf Avenue, Guangpei Community, Guanlan Street, Longhua District, Shenzhen | FCC grantee record |
-| Storefront | `xteink.com` — **stock Shopify** | measured 2026-09-11 |
-| Chinese domain | `xteink.cn` — **confirmed theirs by the FCC filing**, but the apex was unreachable from the research host. `bofi.xteink.cn` is referenced inside X4 firmware | 2026-09-11 |
-
----
-
-## 2. The storefront is Shopify, and its JSON is far better evidence than its prose
-
-`xteink.com` is an unmodified Shopify install. Every standard endpoint works **unauthenticated**:
-
-```bash
-curl -s 'https://xteink.com/products.json?limit=250&page=1'      # whole catalogue
-curl -s 'https://xteink.com/collections.json'                    # collection handles
-curl -s 'https://xteink.com/collections/<handle>/products.json'  # one product line
-curl -s 'https://xteink.com/products/<handle>.js'                # one product, richer
-```
-
-These carry **`published_at`, per-variant SKU, price, `compare_at_price`, stock state and
-grams** — which is how launch dates and withdrawals in this repository are dated at all.
-
-**Paginate to exhaustion.** `?limit=250&page=1` returned the entire catalogue on 2026-09-11
-(25 products), but confirm pages 2+ are empty rather than assuming.
-
-### Traps, all measured
-
-- ⚠ **`body_html` can be empty.** The X4 Classic's entire specification table exists **only in
-  the rendered product-page HTML**, not in the JSON. **Fetch both**, always.
-- ⚠ **The product prose is SEO-generated and demonstrably wrong.** Where the prose and the JSON
-  disagree, the JSON is evidence and the prose is marketing. Where the prose and the *hardware*
-  disagree, both lose.
-- ⚠ **`compare_at_price` is not a former selling price.** It is a Shopify "was" anchor. The X4
-  Classic was published at 79.00 and has never been listed at the 89.00 it is compared against.
-- ⚠ **`grams` is shipping weight, not device mass.** The X4 Classic reports `250`; the vendor's
-  own spec block says the device is **68 g**.
-- ⚠ **Six catalogue line-items are services, not products** — handling fees, shipping fee,
-  after-sale charges. Exclude them from any price range, or "cheapest item in the store" returns
-  **USD 1.00**.
-- **An empty collection is a pre-launch signal.** A `x4-classic` collection handle existed with
-  zero devices in it days before the device was listed. A collection whose *device* is gone but
-  whose accessories remain is the opposite — an end-of-life signature.
-- Reviews are **Judge.me**, embedded as JSON inside the product page rather than fetched
-  separately.
-
----
-
-## 3. ⭐ The FCC grantee code is the real product catalogue
-
-**This is the most valuable finding about this vendor, and it generalises to every vendor in
-this repository.**
-
-```
-https://fccid.io/2BTR9          # every device Xteink has ever certified for the US
-https://fccid.io/<FCC-ID>       # one filing: dates, frequencies, exhibit list, embargoes
-https://fccid.io/<FCC-ID>/<Type-Slug>/<Doc-Slug>.pdf    # an exhibit
-```
-
-Searching for *"Xteink"* by **product name** finds little. Enumerating the **grantee code**
-returned five devices on 2026-09-11 — **one of which the vendor has never announced, listed or
-priced**: the [X4 Light](../../devices/xteink/x4-light/README.md), `2BTR9-X4L`, granted
-2026-08-13.
-
-| FCC ID | Granted | Device |
-|---|---|---|
-| `2BTR9-X4L` | 2026-08-13 | XTEINK X4 Light — **never announced** |
-| `2BTR9-X4C` | 2026-07-20 | XTEINK X4 Classic |
-| `2BTR9-X4PRO` | 2026-06-16 | XTEINK X4 Pro |
-| `2BTR9-XTEINKX4` | 2026-01-05 | XTEINK X4 |
-| `2BTR9-XTEINKX3` | 2025-12-26 | XTEINK X3 |
-
-**Grant dates lead store listings by weeks to months** — `2BTR9-X4C` was granted 2026-07-20 and
-the X4 Classic appeared in the store on 2026-09-06. The grantee index is therefore a **forward
-indicator**, not just a record.
-
-### What the exhibits give you that the vendor does not
-
-- **Internal photographs** — the X3's and the X4's were never withheld, and the X4's are the
-  **first public teardown of that device**.
-- Antenna part numbers, gains and VSWR. The
-  [KH3216-A35](../../components/generic/kh3216-a35-chip-antenna/README.md) record exists only
-  because of an antenna report.
-- Battery part number, capacity and cell date code, read off a label in a photograph.
-- The legal entity, address and contact.
-
-### What they never will
-
-⚠ **Schematics, block diagrams and operational descriptions are under *long-term*
-confidentiality on all five filings.** That is permanent. **The FCC is not a route to an Xteink
-schematic.** Photographs, users manuals and test setup photos are withheld under *short-term*
-confidentiality and **do** unlock — X4 Pro **2026-12-12**, X4 Classic **2027-01-16**, X4 Light
-**2027-02-09**.
-
-### Access traps
-
-- ⚠ **`fccid.io` serves an inverted block.** Deep paths return **403** to a Chrome User-Agent
-  (Cloudflare managed challenge) and **200** to `curl/8.5.0`, `WhatsApp/2.23.20.0`,
-  `ChatGPT-User/1.0` and `ClaudeBot/1.0`. **The honest UA works; the disguised one does not.**
-- ⚠ **The root `https://fccid.io/` returns 200 to everything**, so a reachability probe against
-  the root reports a false success. **Probe a deep path.**
-- ⚠ **The `.pdf` suffix is mandatory** on exhibit URLs. Without it you get a 16 KB HTML viewer.
-- ⚠ **`https://fccid.io/2BTR9` prints "6 FCC IDs" and lists five.** Exactly five
-  `href="/2BTR9…"` links exist in the HTML. **Trust the table, not the counter.**
-- The **official** FCC endpoints (`apps.fcc.gov`, `www.fcc.gov/oet/ea/fccid`) returned **403 to
-  all five user agents tried** on 2026-09-11. `fccid.io` is a **mirror** — label it as one.
-
-Full method, with the measured user-agent matrix and the control procedure:
-[`guides/research/finding-certification-records.md`](../../guides/research/finding-certification-records.md).
-
----
-
-## 4. What Xteink does not publish
-
-| Class | Status |
-|---|---|
-| Datasheet, schematic, BOM, EDA sources | ❌ **none, for any product** |
-| Wiki, support portal, docs site | ❌ none |
-| Firmware downloads, OTA URLs | ❌ none official. Community dumps exist for the X3 and X4 |
-| Certification page | ❌ none — despite holding five FCC grants |
-| Declaration of Conformity (CE) | ❌ none located. CE is self-declared and **has no database to search** |
-
-**Consequence:** essentially every technical claim about an Xteink device in this repository
-traces to third-party reverse engineering (`Free-Ink/freeink-sdk`, CrossPoint Reader), community
-teardowns, or the FCC record. Treat vendor prose as the weakest source available.
-
----
-
-## 5. Per-product checklist
-
-1. `products.json` **and** the rendered product page — the spec table may exist only in the HTML.
-2. `collections.json` — an empty collection handle predicts a launch; a device-less collection
-   with live accessories signals withdrawal.
-3. `https://fccid.io/2BTR9` — re-enumerate; new grants appear before products do.
-4. For each FCC ID: grant date, frequencies, test firm, **exhibit list and embargo dates**.
-5. Download the exhibits with a `curl` UA and the `.pdf` suffix. Validate magic bytes.
-6. Diary the short-term confidentiality expiry dates. They are the cheapest future evidence.
-7. Reddit `r/XTEINK` and `r/xteinkereader` for prices, channels and firsthand ownership.
-
----
-
-## 6. Evidence boundary
-
-Written **2026-09-11** from two research passes. **No Xteink hardware was handled**, no store
-purchase was made, and no claim here was tested against a physical device. Every endpoint,
-status code and user-agent result above was executed from one host on 2026-09-11 and may differ
-from yours — the Cloudflare behaviour in particular is likely to change.
-
-`xteink.cn` was **not reachable** from the research host, so the Chinese-market channel is
-documented only through community reports. Chinese marketplaces (Taobao, JD, Xianyu) were
-**bot-walled or JS-shelled** and were not sampled.